Package: usbmount
Version: 0.0.21
Severity: normal

Just to keep this recorded: the .21 version will leave the oldstyle 
/etc/udev/ files around after upgrades. They should be removed after 
checking that the files were not altered. The symlink should be removed 
in that case as well.

There are patches in git.katzien.de/usbmount.git (not yet cleaned up) 
which do this. The problem ist, that they are based on .20 and not .21, 
which has teh conffile already removed. I migt be the case that the hash 
for the files is no longer in the dpkg database and so needs to be manualy
checked if updated from .21.

As it is only a "may" in policy 10.7.3, I haven't set the Severity:
to serious but only to normal. IMO the .21 should no go into testing,
as this would mean that stable users would have that problem when
updating to squeeze+1.

Kind regards,

Jan


-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (900, 'unstable'), (500, 'experimental'), (99, 
'maverick-updates'), (99, 'maverick')
Architecture: i386 (i586)

Kernel: Linux 2.6.32-5-486
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages usbmount depends on:
ii  dpkg                          1.15.8.3   Debian package management system
ii  lockfile-progs                0.1.15     Programs for locking and unlocking
ii  udev                          160-1      /dev/ and hotplug management daemo
ii  util-linux                    2.17.2-3.1 Miscellaneous system utilities

Versions of packages usbmount recommends:
ii  ntfs-3g                     1:2010.3.6-1 read-write NTFS driver for FUSE
pn  pmount                      <none>       (no description available)

usbmount suggests no packages.

-- Configuration Files:
/etc/usbmount/usbmount.conf changed [not included]

-- no debconf information

-- debsums errors found:
debsums: changed file /usr/share/usbmount/usbmount (from usbmount package)



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to