Bug#970907: SourceRecords: Please expose release attributes

2020-09-30 Thread Christian Kastner
On 2020-09-28 08:21, Christian Kastner wrote: >> On 2020-09-25 11:33, Julian Andres Klode wrote: >>> Patches to add the expose those attributes in the MetaIndex >>> bindings are of course welcome. > > So this seemed straightforward enough and I gave it a try [3], but that > didn't work

Bug#970907: SourceRecords: Please expose release attributes

2020-09-28 Thread Christian Kastner
On 2020-09-25 13:39, Christian Kastner wrote: > On 2020-09-25 11:33, Julian Andres Klode wrote: > >> Patches to add the expose those attributes in the MetaIndex >> bindings are of course welcome. So this seemed straightforward enough and I gave it a try [3], but that didn't work unfortunately:

Bug#970907: SourceRecords: Please expose release attributes

2020-09-25 Thread Christian Kastner
Thanks for the quick reply! On 2020-09-25 11:33, Julian Andres Klode wrote: >> I would greatly appreciate it if you would consider exposing the origin, >> component, archive, codename and label attributes for SourceRecords as >> well. > > They are not there in the C++ object, so they can't be

Bug#970907: SourceRecords: Please expose release attributes

2020-09-25 Thread Julian Andres Klode
On Fri, Sep 25, 2020 at 11:18:51AM +0200, Christian Kastner wrote: > Package: python3-apt > Version: 2.1.3 > Severity: wishlist > > For binary packages, it's possible to determine the releases a package > is in, together with its versions, etc. Based on the example from [1]: > > (1) a package

Bug#970907: SourceRecords: Please expose release attributes

2020-09-25 Thread Christian Kastner
Package: python3-apt Version: 2.1.3 Severity: wishlist For binary packages, it's possible to determine the releases a package is in, together with its versions, etc. Based on the example from [1]: (1) a package exposes "version_list" (2) a version exposes "file_list" (3) a file as