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

Re: not a member of ‘pkgTagSection::Key’



So I  started checking commits between 2.4.5 and 2.5.0 to find where things broke for me.

701a501fb1c84296d2003c0092e4308742079591
This is the offending commit that breaks things when I am cross-compiling. I can compile HEAD in git if I reverse this commit. Any way that this could be refactored so it doesn't break for cross-compiling?

Lance

On 7/9/2022 4:35 AM, David Kalnischkies wrote:
Hi,

On Fri, Jul 08, 2022 at 09:22:14AM -0600, Lance Fredrickson wrote:
I've been using apt for a little project of mine and starting with version
2.5.0 I've run into issues building with the following errors.  There's a
bunch of these variations, but I've only included 3.

error: ‘Filename’ is not a member of ‘pkgTagSection::Key’
error: ‘Package’ is not a member of ‘pkgTagSection::Key’
error: ‘Description’ is not a member of ‘pkgTagSection::Key’

I'm building for arm & mipsel using uclibc-ng.
There is a "bug" of sorts in the semi-public headers which generate
these errors. The best advice here is usually to not include a deb*
header aka a line matching "#include <apt-pkg/deb*.h>". The interfaces
they implement are usually provided in similar named files without the
deb-prefix.

There are some methods which are not and for those you really need to
access the deb-headers, but can't ATM, that is a bug as hinted above,
but really special interest (python-apt is the only legitime user I
know of).


That is NOT your issue though as Filename and Description are not used
in these headers. Is you little project perhaps using pkgTagSection::Key
interfaces directly? You aren't supposed to if you aren't APT yourself
as the (binary) interface isn't stable…

Can you give us a code example?


Best regards

David Kalnischkies


Reply to: