Your message dated Sat, 13 Aug 2011 00:39:38 +0200
with message-id <20110812223933.ga18...@xs4all.net>
and subject line bug fixed in liblockfile 1.09-2
has caused the Debian Bug report #637465,
regarding liblockfile: package liblockfile1 in control file but not in files
list
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 ow...@bugs.debian.org
immediately.)
--
637465: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637465
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: liblockfile
Version: 1.09-1
Severity: grave
This upload dropped the liblockfile{1,-bin} packages, making
liblockfile-dev uninstallable. From my debuild log:
,----
| dpkg-genchanges >../liblockfile_1.09-1_i386.changes
| dpkg-genchanges: warning: package liblockfile1 in control file but not in
files list
| dpkg-genchanges: warning: package liblockfile-bin in control file but not in
files list
`----
Same on all the buildds and the maintainer uploaded packages(!).
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (101, 'experimental')
Architecture: i386 (x86_64)
Kernel: Linux 3.0.1-nouveau (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
Package: liblockfile
Version: 1.09-2
The bug you filed has been fixed in 1.09-2, but I misspelled the closes:
line in the changeslog, so I'm closing manually now.1.09-2 had some
other small problems, 1.09-3 has just been uploaded
and should fix all remaining issues. Thanks.
--- End Message ---
