[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Checking reverse dependencies



Pirate Praveen <praveen@onenetbeyond.org> writes:

> 2024, ഡിസം 1 6:37:23 AM Otto Kekäläinen <otto@debian.org>:
>
>> Hi!
>>
>> I am planning to upload new versions of some Go libraries, and before
>> doing it I wanted to test that the reverse dependencies don't break.
>> However, for these two I can't find any:
>>
>> # apt-cache rdepends golang-github-caarlos0-env
>> E: No packages found
>> # apt-cache rdepends golang-github-caarlos0-env-dev
>> golang-github-caarlos0-env-dev
>> Reverse Depends:
>>
>> # apt-cache rdepends golang-github-muesli-gitcha
>> E: No packages found
>> # apt-cache rdepends golang-github-muesli-gitcha-dev
>> golang-github-muesli-gitcha-dev
>> Reverse Depends:
>>
>> Why can't I find any?
>>
>> Why would somebody have put these libraries in Debian if nothing uses them?
>
> Check reverse build depends. reverse-depends -b

I usually use UDD or dak like this:

ssh jas@mirror.ftp-master.debian.org
dak rm -Rn -b golang-github-caarlos0-env-dev

These two didn't seem to have any reverse build depends, lucky you!

Packages like this may be in Debian because 1) something in NEW queue
depends on them, or 2) someone plans to upload something into NEW queue
that depends on them, or 3) someone planned to upload X into NEW queue
that depends on them but X migrated to avoiding that dependency during
packaging work, or 4) someone has managed to avoid the reverse build
dependency on that package over time, or 5) something else.

It's not ideal to ship packages like this, but doing so probably hurts
less than removing them from the archive and later realize they were
needed after all.

/Simon

Attachment: signature.asc
Description: PGP signature


Reply to: