Bug#701150: debsums falsing

2013-02-22 Thread Andreas Beckmann
Control: block -1 by 689508 689202

On 2013-02-22 05:19, Dave Steele wrote:
 While looking at the piatti piuparts report Andreas pointed to today,
 I noticed that failures are racking up for debsums modifications.

 http://piuparts.debian.org/sid/fail/binutils-multiarch_2.22-7.1.log
 
   /org/piuparts.debian.org/tmp/tmpEXGvJj/usr/bin/strings
   /org/piuparts.debian.org/tmp/tmpEXGvJj/usr/bin/gprof

these are diverted

debsums (2.0.49) unstable; urgency=low
  * when querying dpkg-divert include the user specified root filesystem
in --admindir (Closes: #632463)

piatti is running 2.0.48+nmu3

 I believe that debsums should not report failures for modified files
 which are owned by multiple packages, or are subject to diversion.

Why not?

I'm running a locally modified debsums from wheezy here with two patches
applied:
* correct symlink lookup (debsums --root escapes the chroot and looks up
files in the host system which may have different content ... #689202)
* ignore obsolete conffiles (#689508, local HACK)
and that solved the debsums issues for me

For #689202 I could do a NMU, but unfortunately for #689508 I cant offer
a nice clean solution. Then we could get debsums unblocked, into wheezy
and backport it and finally install it on piatti.

Or we could add a modified copy of debsums to piuparts, only to be used
when running from git as on piatti ...


Andreas


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#701150: debsums falsing

2013-02-22 Thread Holger Levsen
Hi,

On Freitag, 22. Februar 2013, Andreas Beckmann wrote:
 For #689202 I could do a NMU, but unfortunately for #689508 I cant offer
 a nice clean solution. Then we could get debsums unblocked, into wheezy
 and backport it and finally install it on piatti.
 
 Or we could add a modified copy of debsums to piuparts, only to be used
 when running from git as on piatti ...

Or upload the wheezy version to backports.org and install that on piatti.

I've also asked #debian-admin what they think about using wheezy for the new 
piatti VM (piatti will be moved in a VM sometime in future.) and they think 
its a good idea. 2-3 months is my guess for that.


cheers,
Holger



Bug#701150: debsums falsing

2013-02-22 Thread Andreas Beckmann
On 2013-02-22 18:27, Holger Levsen wrote:
 Or upload the wheezy version to backports.org and install that on piatti.

Not perfect, but still better than debsums/squeeze.

Andreas


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#701150: [Piuparts-devel] Bug#701150: debsums falsing

2013-02-22 Thread Dave Steele
On Fri, Feb 22, 2013 at 8:35 AM, Andreas Beckmann a...@debian.org wrote:
 Control: block -1 by 689508 689202

 debsums (2.0.49) unstable; urgency=low
   * when querying dpkg-divert include the user specified root filesystem
 in --admindir (Closes: #632463)

 piatti is running 2.0.48+nmu3

Perhaps this is why I don't have any problems with debsums in my setup.


 I believe that debsums should not report failures for modified files
 which are owned by multiple packages, or are subject to diversion.

 Why not?


personally, I don't want to see gnome-gmail failed for modifying
/usr/sbin/update-icon-caches


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#701150: debsums falsing

2013-02-21 Thread Dave Steele
package: piuparts
severity: normal

While looking at the piatti piuparts report Andreas pointed to today,
I noticed that failures are racking up for debsums modifications.

The debsums man page, under Caveats, says that files which have been
replaced by another package may be erroneously reported as changed.
Multiple ownership can cause a false. It seems that a significant
portion of new failures are for debsums, and a significant portion of
these fall in this case.

http://piuparts.debian.org/sid/fail/binutils-multiarch_2.22-7.1.log

  /org/piuparts.debian.org/tmp/tmpEXGvJj/usr/bin/strings
  /org/piuparts.debian.org/tmp/tmpEXGvJj/usr/bin/gprof
  /org/piuparts.debian.org/tmp/tmpEXGvJj/usr/bin/readelf
  /org/piuparts.debian.org/tmp/tmpEXGvJj/usr/bin/size
  /org/piuparts.debian.org/tmp/tmpEXGvJj/usr/bin/nm
  /org/piuparts.debian.org/tmp/tmpEXGvJj/usr/bin/strip
  /org/piuparts.debian.org/tmp/tmpEXGvJj/usr/bin/ranlib
  /org/piuparts.debian.org/tmp/tmpEXGvJj/usr/bin/ar
  /org/piuparts.debian.org/tmp/tmpEXGvJj/usr/bin/addr2line
  /org/piuparts.debian.org/tmp/tmpEXGvJj/usr/bin/objcopy
  /org/piuparts.debian.org/tmp/tmpEXGvJj/usr/bin/objdump
0m27.1s DEBUG: Command failed (status=2), but ignoring error:
['debsums', '--root', '/org/piuparts.debian.org/tmp/tmpEXGvJj', '-ac']
0m27.1s ERROR: FAIL: debsums reports modifications inside the chroot:

$ apt-file search /usr/bin/strings
binutils: /usr/bin/strings
binutils-multiarch: /usr/bin/strings



I've seen this with dpkg diversions as well:

http://piuparts.debian.org/squeeze2wheezy/fail/gnome-icon-theme_3.4.0-2.log

  /org/piuparts.debian.org/tmp/tmplq_ENa/usr/sbin/update-icon-caches
2m56.0s DEBUG: Command failed (status=2), but ignoring error:
['debsums', '--root', '/org/piuparts.debian.org/tmp/tmplq_ENa', '-ac']
2m56.0s ERROR: FAIL: debsums reports modifications inside the chroot:

http://piuparts.debian.org/sid/fail/gnome-gmail_1.8.2-1.log

  /org/piuparts.debian.org/tmp/tmp_JcjF7/usr/sbin/update-icon-caches
2m17.6s DEBUG: Command failed (status=2), but ignoring error:
['debsums', '--root', '/org/piuparts.debian.org/tmp/tmp_JcjF7', '-ac']
2m17.6s ERROR: FAIL: debsums reports modifications inside the chroot:


$ dpkg --search /usr/sbin/update-icon-caches
diversion by libgtk-3-bin from: /usr/sbin/update-icon-caches
diversion by libgtk-3-bin to: /usr/sbin/update-icon-caches.gtk2
libgtk-3-bin, libgtk2.0-bin: /usr/sbin/update-icon-caches


I believe that debsums should not report failures for modified files
which are owned by multiple packages, or are subject to diversion.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org