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

Re: dpkg-checkbuilddeps and apt-get at odds over libacl1-dev



On 07/03/2016 06:46 PM, Thomas Schmitt wrote:
> Christian Seiler wrote:
>> You are using an older version of lintian (probably the one from Jessie).
> 
> It is what apt-get "update" and "dist-upgrade" gave me on Sid.
> It was downloaded during "dist-upgrade":
> 
>   Get:611 http://ftp.de.debian.org/debian unstable/main amd64 lintian all 2.5.45 [1,036 kB]
> 
> No messages about "Unpacking" or "Setting up" of lintian are to see, though.

Your dist-upgrade then didn't go through completely, so other
packages are potentially also not upgraded completely. I
would highly recommend you doing an apt-get dist-upgrade
again to make sure you have a sane state of your system.

> I intend to build for Sid on a Sid qemu-system-x86_64 VM (hosted by Jessie).
> That's why i wonder why lintian still expects 3.9.6.

Btw. why qemu-system? A chroot (see e.g. pbuilder or sbuild)
is perfectly fine for building packages (Debian's autobuilders
use sbuild chroots, for example), and probably quite a bit
faster than a full VM.

>  ii  lintian        2.5.40.2     all          Debian package checker
> But dpkg --configure --pending does not do anything.

Yes, because it's already configured. 2.5.40 is newer than
Jessie (Jessie has 2.5.30), but older than current sid, so
it's likely from an older Stretch installation.

dpkg --configure --pending cleans up dpkg's state, so that all
packages that were unpacked-but-not-yet-configured are now in
a sane state on your system, but that doesn't mean that the
original dist-upgrade went through fine. You probably need to
do a dist-upgrade again to upgrade all of your system.

> So i try
> 
>  # apt-get install lintian
>  ...
>  Preparing to unpack .../lintian_2.5.45_all.deb ...
>  Unpacking lintian (2.5.45) over (2.5.40.2) ...
>  Processing triggers for man-db (2.7.5-1) ...
>  Setting up lintian (2.5.45) ...

Yes, apt-get install $pkgname will upgrade the package if a
newer version is available (and an installation candidate, cf.
priorities and pinning).

> But nevertheless now debuild -S does not complain about the freshly
> changed  "Standards-Version: 3.9.8"  as it did before i installed
> lintian manually.

Because now you upgraded lintian to the newest version in sid.

Parts of your system might still not be upgraded though, and
you could have therefore missed some library transitions that
happened in the mean time. I would therefore really recommend
to re-do the dist-upgrade to make sure your system is
completely up to date, before you work on packaging things.

Regards,
Christian


Reply to: