[Aptitude-devel] Bug#892984: Bug#892983 + Bug#892984: please allow filtering on/displaying the release 'label'/'suite'

[Tomas Pospisek]

Hi Manuel,

I want to ping you on this wishlist ticket.

I do not want to stress you out: you have your own life and priorities, 
just as everybody else, full respect for that.

However sometimes stuff falls through the cracks, that's why I'm pinging 
you on this.

Do you have any further insight on that wishlist bug? Did you get stuck 
reviewing it? Is there anything that's missing (yeah, I guess the tests 
should be fixed, right?), that you'd maybe appreciate if anybody could 
take care of?

As said, no stress, however I *would* appreciate it very much if this 
patch could make it in eventually... :-o

Thanks a lot for taking care of aptitude :-)!!! Best greetings,
*t

On Fri, 16 Mar 2018, Manuel A. Fernandez Montecelo wrote:

> Hi,
>
> 2018-03-15 10:56 Axel Beckert:
>> Control: tag -1 + confirmed
>> 
>> Hi Tomas,
>> 
>> Tomas Pospisek wrote in #892983:
>>> The attached patch implement filtering for the 'Label' field in the
>>> "Release" file. I.e. it allows to filter packages according to the
>>> 'Label' of the release they belong to.
>>> 
>>> It adds a search expression/filter '?label()' to aptitude.
>
> Thanks for the patch.
>
>
>> Yay!
>> 
>> Actually I could have needed that (and looked for it) yesterday on
>> Raspbian to figure our which packages come from Rasbian (i.e. are in
>> sync with Debian) and which come from the Raspberry Pi Foundation's
>> APT repo (which seems rather topsy-turvy).
>> 
>> In the end ?origin() worked for that case, too, but having ?label() …
>> [...]
>> … and ?suite() would be indeed a very nice addition. So thanks for the
>> patch (and patch template)!
>
> IIRC I implemented ?origin a few years back, and again IIRC, there was
> some trouble with ?label or some of the other fields coming from the
> repo, I think that it's the reason why they are missing.
>
> Over the next week or so I will try to remember or do some tests to find
> out why I didn't do that... unfortunately that might require digging
> into bug reports or mailing list archives, if that was even documented
> publicly at all, which maybe not.
>
>
> Cheers.
> -- 
> Manuel A. Fernandez Montecelo <manuel.montezelo at gmail.com>
>