Your message dated Fri, 15 Nov 2013 10:27:15 -0500
with message-id <[email protected]>
and subject line [libmount1] tries to overwrite existing libmount
has caused the Debian Bug report #630921,
regarding [libmount1] tries to overwrite existing libmount
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
630921: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630921
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libmount1
Version: 2.19.1-2
Severity: grave
--- Please enter the report below this line. ---
When upgrading from util-linux-2.19.1-1 et al, libmount1 install tries
to overwrite previous util-linux libmount. Bypassed here by holding
mount and libmount1 while upgrading the rest, then proceeded with mount
and libmount1. I'm not a packaging guru, but would setting a Conflicts:
or Breaks: line in the debian/control do the trick?
--- System information. ---
Architecture: amd64
Kernel: Linux 2.6.39-2-amd64
Debian Release: wheezy/sid
500 unstable localhost
500 testing localhost
500 experimental localhost
1 experimental localhost
--- Package information. ---
Depends (Version) | Installed
===========================-+-============
libblkid1 (>= 2.17.2) | 2.19.1-2
libc6 (>= 2.4) | 2.13-7
libselinux1 (>= 1.32) | 2.0.98-1+b1
libsepol1 (>= 1.14) | 2.0.42-1
Package's Recommends field is empty.
Package's Suggests field is empty.
--- End Message ---
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
It would have been nice if this were done promptly but since it only
affected people upgrading from experimental 2.5 years ago, I think it
is safe to say it is no longer relevant so I'm closing this bug
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJShj1TAAoJEJrBOlT6nu759GIH/0X9YRaBem0pcznE5n/jNRJb
EIK0EtMc4UY5OpoKUq/a80BaLJxWOG9zrTAPaJzdBG2b13/1c76kya9GicK9jL8C
8VKfsybQRYlDNEyrKDCNT+fudR8O42DYGX5uTKvNTHwuYBCAh8W8Sl3PjarqaLKx
Mw3xWmQS26EADrgF45iECQw4LocLjeg8x0zQPycG0IN6/PtMaa9hRNQ9ulUesZ57
A4LQr1wI7bPB78eJblCiufgJRj/imbn27f4tdzaL5hRkRzrk0zgSGiSWbIiqREIj
zA6WGn1U+aPwOYuxqr6bY9ITUGlmq5Mq8x2SMRAYQNuwqO/Qs65AfL2eAspS8KU=
=iWES
-----END PGP SIGNATURE-----
--- End Message ---
