On 29/11/13 at 14:54 +0100, Axel Beckert wrote:
> Package: how-can-i-help
> Version: 0.9
> Severity: normal
> 
> Dear Lucas,
> 
> how-can-i-help claimed a bunch of new orphaned packages today on
> multiple of my machines:
> 
> ======  How can you help?  (doc: http://wiki.debian.org/how-can-i-help ) 
> ======
> New orphaned packages:
>  - debtags - http://bugs.debian.org/567954 -
>  - libisoburn - http://bugs.debian.org/679265 -
>  - xml-core - http://bugs.debian.org/660687 -
>  - openssl - http://bugs.debian.org/332498 -
>  - cups - http://bugs.debian.org/532097 -
>  - libburn - http://bugs.debian.org/679249 -
>  - ppp - http://bugs.debian.org/589632 -
>  - gnokii - http://bugs.debian.org/677750 -
>  - grub2 - http://bugs.debian.org/248397 -
>  - irssi-scripts - http://bugs.debian.org/663577 -
>  - chromium-browser - http://bugs.debian.org/583826 -
>  - libcap2 - http://bugs.debian.org/534999 -
>  - openldap - http://bugs.debian.org/512360 -
>  - libisofs - http://bugs.debian.org/679254 -
>  - gnupg - http://bugs.debian.org/660685 -
>  - screen - http://bugs.debian.org/654116 -
>  - iproute - http://bugs.debian.org/705169 -
>  - libreoffice - http://bugs.debian.org/419523 -
> ------  Show all opportunities, not just new ones: how-can-i-help --all  
> ------
> 
> As screen's package maintainer I'm sure that screen is not
> orphaned. Looking at a few of these bug reports showed that they were
> all "RFH", but not "O".
> 
> Not sure if this is related to the fixing of
> http://bugs.debian.org/730293 -- but I still have 0.9 here, so maybe 0.9
> is incompatible with server-side changes for 1? (In that case the bug
> should be fixed with 1 anyway. :-)

Hi Axel,

Yes, it's due to this change, and fixed in version 1.

The problem is the client-side does not ignore wnpp types it doesn't
know (RFH in that case).

I've reverted the server-side change to avoid outputting RFH lines, and
will re-enable it when how-can-i-help v1 reaches testing.

Lucas


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to