Control: tags -1 - moreinfo On Wed, 19 Sep 2018 at 11:36:28 +0000, Holger Levsen wrote: > On Wed, Sep 19, 2018 at 10:53:58AM +0100, Simon McVittie wrote: > > Since apt 1.7.x fixed > > <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869546>, apt will > > create /var/lib/dpkg/lock-frontend when run. This causes a piuparts > > false positive when testing an otherwise piuparts-clean package (I tried > > src:libepoxy): > > > > > 0m31.7s ERROR: FAIL: Package purging left files on system: > > > /var/lib/dpkg/lock-frontend not owned > > > > Please add this file to the default list of ignored files alongside > > /var/lib/dpkg/lock. > > thanks for your bug report, but I cannot find any package with that > failure in sid* on piuparts.d.o and I've also just let it retest > src:libepoxy and it tested fine (while using apt 1.7.0~rc1). > > what am I missing?
piuparts.debian.org uses --warn-on-others and --warn-on-leftovers-after-purge. It is reporting this for libepoxy, just not as a failure: https://piuparts.debian.org/sid/pass/libepoxy-dev_1.5.2-0.1.log > 0m49.2s INFO: Warning: Package purging left files on system: > /var/lib/dpkg/lock-frontend not owned > These files seem to have been left by dependencies rather than by packages > being explicitly tested. The piuparts runs in https://salsa.debian.org/smcv/vectis that I use before uploading packages are for all the binaries from a source as a single batch (on the assumption that they have lockstep dependencies on each other more often than not), and the piuparts man page says "--warn-on-others: ... Behavior with multiple packages given on the command-line could be problematic", so I've avoided using --warn-on-others. Was that wrong? Should I be using --warn-on-leftovers-after-purge when testing packages to be uploaded, or is that just a workaround? Thanks, smcv
