Your message dated Fri, 12 Aug 2011 18:36:40 +0200 with message-id <[email protected]> and subject line Re: Bug#637465: liblockfile: package liblockfile1 in control file but not in files list 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 [email protected] immediately.) -- 637465: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637465 Debian Bug Tracking System Contact [email protected] 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 On 2011-08-12 10:02 +0200, Miquel van Smoorenburg wrote: > On 11-08-11 8:31 PM, Sven Joachim wrote: >> This upload dropped the liblockfile{1,-bin} packages, making >> liblockfile-dev uninstallable. From my debuild log: >> > > Thanks, sorry about that. I fixed it, but: > > Your package contains new components which requires manual editing of > the override file. It is ok otherwise, so please be patient. New > packages are usually added to the override file about once a week. > > .. so it might take a few days before it becomes visible. It's already been accepted. Note that you need to use "closes:" in debian/changelog rather than "fixes:" to close a bug. Cheers, Sven
--- End Message ---
