Bug#418393: Upgrade problem: lpr tries to overwrite logcheck-database files
Frédéric Brière wrote: severity 418393 serious thanks On Mon, Apr 09, 2007 at 01:49:01PM -0500, Adam Majer wrote: Yes, definitely. The fix is just to remove the conffile from lpr. No Seems to me like these two files should at least be merged, as they have different rules. Since logcheck ships lots and lots of files, it may be best for lpr to either rename the file to something like, like lpr.package, or just drop the file altogether. I'll take a look at the rules today and get this done.. As for which package should inherit from the other, I'm a strong proponent of having individual packages ship their own rules, but it's really up to you. Ideally, logcheck shipping its files named package.logcheck or package.lc or similar would have been more compatible with packages providing their own rules. But I guess that can't really be done now.. - Adam PS. Sorry, I guess I've forgotten about this bug :) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#418393: [Logcheck-devel] Bug#418393: Upgrade problem: lpr tries to overwrite logcheck-database files
martin f krafft wrote: logcheck-database exists as a bag for rules that are not in the packages. If a package provides its own rule files, the logcheck-database must not. Yes, that makes very good sense. I've just added the missing rule from 1.2.63 logcheck-database to lpr package. Does this mean the bug should be reassigned to logcheck-database? - Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#418393: [Logcheck-devel] Bug#418393: Upgrade problem: lpr tries to overwrite logcheck-database files
On Mon, Mar 17, 2008 at 12:33:48PM -0500, Adam Majer wrote: Does this mean the bug should be reassigned to logcheck-database? The appropriate action, IMO, would be to Replace: logcheck-database; we can then remove that file at our leisure. (I for one am using l-d from backports.org on my servers, so I'd favor waiting until after lenny's release.) -- Being overloaded is the sign of a true Debian maintainer. -- JHM on #Debian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#418393: [Logcheck-devel] Bug#418393: Upgrade problem: lpr tries to overwrite logcheck-database files
also sprach Adam Majer [EMAIL PROTECTED] [2008.03.17.1748 +0100]: Since logcheck ships lots and lots of files, it may be best for lpr to either rename the file to something like, like lpr.package, or just drop the file altogether. I'll take a look at the rules today and get this done.. The rules should just be merged into one file and distributed as part of the lpr package. Ideally, logcheck shipping its files named package.logcheck or package.lc or similar would have been more compatible with packages providing their own rules. But I guess that can't really be done now.. logcheck-database exists as a bag for rules that are not in the packages. If a package provides its own rule files, the logcheck-database must not. -- .''`. martin f. krafft [EMAIL PROTECTED] : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems man soll nicht in kirchen gehn, wenn man reine luft atmen will. - friedrich nietzsche digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Bug#418393: Upgrade problem: lpr tries to overwrite logcheck-database files
severity 418393 serious thanks On Mon, Apr 09, 2007 at 01:49:01PM -0500, Adam Majer wrote: Yes, definitely. The fix is just to remove the conffile from lpr. No Seems to me like these two files should at least be merged, as they have different rules. As for which package should inherit from the other, I'm a strong proponent of having individual packages ship their own rules, but it's really up to you. -- nobse bleh... last night I had a dream... someone NMU'ed vim... nightmare -- in #debian-devel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#418393: Upgrade problem: lpr tries to overwrite logcheck-database files
Package: lpr Version: 2006.11.04-1 Severity: normal While upgrading from sarge to etch: Unpacking replacement logcheck-database ... Preparing to replace lpr 1:2003.09.23-7 (using .../lpr_1%3a2006.11.04_i386.deb) ... Stopping printer spooler: lpd . Unpacking replacement lpr ... dpkg: error processing /var/cache/apt/archives/lpr_1%3a2006.11.04_i386.deb (--unpack): trying to overwrite `/etc/logcheck/ignore.d.server/lpr', which is also in package logcheck-database dpkg-deb: subprocess paste killed by signal (Broken pipe) Starting printer spooler: lpd . Preparing to replace lsscsi 0.14-1 (using .../lsscsi_0.17-1_i386.deb) ... Maybe lpr should have a Replace: logcheck-database header? bye, -christian- -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-amd64 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) (ignored: LC_ALL set to [EMAIL PROTECTED]) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#418393: Upgrade problem: lpr tries to overwrite logcheck-database files
Christian Hammers wrote: While upgrading from sarge to etch: dpkg: error processing /var/cache/apt/archives/lpr_1%3a2006.11.04_i386.deb (--unpack): trying to overwrite `/etc/logcheck/ignore.d.server/lpr', which is also in package logcheck-database Maybe lpr should have a Replace: logcheck-database header? No, it should not conflict or there would be no logcheck-database (or printer!) For Etch, I guess the best way is to delete the offending file during installation. The two files are probably the same. I'm a little surprised no one noticed this problem beforehand. - Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#418393: Upgrade problem: lpr tries to overwrite logcheck-database files
On 2007-04-09 Adam Majer wrote: Christian Hammers wrote: While upgrading from sarge to etch: dpkg: error processing /var/cache/apt/archives/lpr_1%3a2006.11.04_i386.deb (--unpack): trying to overwrite `/etc/logcheck/ignore.d.server/lpr', which is also in package logcheck-database Maybe lpr should have a Replace: logcheck-database header? No, it should not conflict or there would be no logcheck-database (or printer!) Not Conflicts: but Replaces:, that's a different thing in the debian/control file. Replace just means that one package overwrites files from another package. Only if it also conflicts, the other one is removed. For Etch, I guess the best way is to delete the offending file during installation. The two files are probably the same. This would be possible during lpr.preinst. Maybe a candidate for 4.0r1. bye, -christian- signature.asc Description: PGP signature
Bug#418393: Upgrade problem: lpr tries to overwrite logcheck-database files
Christian Hammers wrote: On 2007-04-09 Adam Majer wrote: Christian Hammers wrote: While upgrading from sarge to etch: dpkg: error processing /var/cache/apt/archives/lpr_1%3a2006.11.04_i386.deb (--unpack): trying to overwrite `/etc/logcheck/ignore.d.server/lpr', which is also in package logcheck-database Maybe lpr should have a Replace: logcheck-database header? No, it should not conflict or there would be no logcheck-database (or printer!) Not Conflicts: but Replaces:, that's a different thing in the debian/control file. Replace just means that one package overwrites files from another package. Only if it also conflicts, the other one is removed. Opps.. I read Replace as Conflict. :) For Etch, I guess the best way is to delete the offending file during installation. The two files are probably the same. This would be possible during lpr.preinst. Maybe a candidate for 4.0r1. Yes, definitely. The fix is just to remove the conffile from lpr. No need to duplicate the effort. And no need to change the lpr.preinst either as the conffile is not needed if it is in the logcheck-database already. - Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
