Bug#390590: /etc/cups/cups-pdf.conf is updated for every new release
reassign 390590 cups-pdf retitle 390590 cups-pdf: /etc/cups/cups-pdf.conf is updated for every new release thanks Please when reassigning, Cc the maintainer address of the package you are reassingning to. On Mon, 2 Oct 2006 11:25:02 +0300, Martin-Éric Racine wrote: On Mon, October 2, 2006 04:12, Jonas Meurer wrote: Package: cups-pdf Version: 2.4.2-1 Severity: normal unfortunately, a version information in /etc/cups/cups-pdf.conf is updated every new upstream release. i consider this as a bug as it causes dpkg to ask for a configfile update even if no content changed. Sorry, your bug report has nothing to do with CUPS-PDF. Rather, it is an expression of a disagreement with the way DPKG handles configurations. No, it has everything to do with how you handle your conffiles. If you don't want to annoy your users, then do not include the version there. maybe you can convince upstream to remove the release version from the configuration file. The release version is there for a reason so, no, we're not removing it. Well then you'll have to cope with the bugs from your users. ;) regards, guillem -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#390590: /etc/cups/cups-pdf.conf is updated for every new release
On Tue, 2006-10-03 at 05:22, Jonas Meurer wrote: On 02/10/2006 Volker Christian Behr wrote: unfortunately, a version information in /etc/cups/cups-pdf.conf is updated every new upstream release. i consider this as a bug as it causes dpkg to ask for a configfile update even if no content changed. if you have local changes in the configuration, this is very annoying. maybe you can convince upstream to remove the release version from the configuration file. Is there a way to make dpkg ignore this comment in the configuration file? unfortunately not. the only solution i can think of now, is that the debian package strips the version line from the config at build time. For some other installations/distributions I depend on the version number being part of the config file could you explain in which situations a version number in the config is required? Anytime people do not use the pre-packaged versions (i.e. Debian packages, rpms and so on) but compile and install from the sources. They tend to forget to update the configuration along with binary. So I have to check each config-file they send to me by comparing with my sources whether it matches the version they are using and they cannot check it by themselves easily. This is - as I had to learn the hard way - a lot of extra work when debugging installation issues. -- Volker Christian Behr Experimentelle Physik V (Biophysik), Physikalisches Institut Universitaet Wuerzburg, Am Hubland, 97074 Wuerzburg, Germany Office: Room F-069a +49-931-888-5766 (phone) +49-931-888-5851 (fax) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#390590: /etc/cups/cups-pdf.conf is updated for every new release
On 03/10/2006 Volker Christian Behr wrote: For some other installations/distributions I depend on the version number being part of the config file could you explain in which situations a version number in the config is required? Anytime people do not use the pre-packaged versions (i.e. Debian packages, rpms and so on) but compile and install from the sources. They tend to forget to update the configuration along with binary. So I have to check each config-file they send to me by comparing with my sources whether it matches the version they are using and they cannot check it by themselves easily. This is - as I had to learn the hard way - a lot of extra work when debugging installation issues. sounds reasonable. i suggest that the debian maintainer (i guess you are upstrem) strips the version line from the config file at build time. something like the following should work in debian/rules: sed -e '/^# *cups-pdf.conf -- CUPS Backend Configuration/s/ (version [0-9a-zA-Z.]*, [0-9-]*)//g' extra/cups-pdf.conf you could even do the regex without limiting it to the first line: sed -e 's/ (version [0-9a-zA-Z.]*, [0-9-]*)//g' extra/cups-pdf.conf but the first one is better because it really only strips the first line containing '# *cups-pdf.conf -- CUPS Backend Configuration'. ... jonas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#390590: /etc/cups/cups-pdf.conf is updated for every new release
On Mon, 2006-10-02 at 03:12, Jonas Meurer wrote: Package: cups-pdf Version: 2.4.2-1 Severity: normal hello, unfortunately, a version information in /etc/cups/cups-pdf.conf is updated every new upstream release. i consider this as a bug as it causes dpkg to ask for a configfile update even if no content changed. if you have local changes in the configuration, this is very annoying. maybe you can convince upstream to remove the release version from the configuration file. Hi! Is there a way to make dpkg ignore this comment in the configuration file? For some other installations/distributions I depend on the version number being part of the config file Volker ... jonas -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-1-amd64-resivo Locale: LANG=C, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Versions of packages cups-pdf depends on: ii cupsys 1.2.4-2 Common UNIX Printing System(tm) - ii gs-esp 8.15.3.dfsg.1-1 The Ghostscript PostScript interpr ii libc62.3.6.ds1-5 GNU C Library: Shared libraries cups-pdf recommends no packages. -- no debconf information -- Volker Christian Behr Experimentelle Physik V (Biophysik), Physikalisches Institut Universitaet Wuerzburg, Am Hubland, 97074 Wuerzburg, Germany Office: Room F-069a +49-931-888-5766 (phone) +49-931-888-5851 (fax) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#390590: /etc/cups/cups-pdf.conf is updated for every new release
reassign 390590 dpkg retitle 390590 dpkg: asking permission to upgrade a config is annoying thanks On Mon, October 2, 2006 04:12, Jonas Meurer wrote: Package: cups-pdf Version: 2.4.2-1 Severity: normal unfortunately, a version information in /etc/cups/cups-pdf.conf is updated every new upstream release. i consider this as a bug as it causes dpkg to ask for a configfile update even if no content changed. Sorry, your bug report has nothing to do with CUPS-PDF. Rather, it is an expression of a disagreement with the way DPKG handles configurations. I'm thus reassigning this to the DPKG maintainers. Please take your concerns to them. maybe you can convince upstream to remove the release version from the configuration file. The release version is there for a reason so, no, we're not removing it. -- Martin-Éric Racine http://q-funk.iki.fi
Bug#390590: /etc/cups/cups-pdf.conf is updated for every new release
On 02/10/2006 Volker Christian Behr wrote: unfortunately, a version information in /etc/cups/cups-pdf.conf is updated every new upstream release. i consider this as a bug as it causes dpkg to ask for a configfile update even if no content changed. if you have local changes in the configuration, this is very annoying. maybe you can convince upstream to remove the release version from the configuration file. Is there a way to make dpkg ignore this comment in the configuration file? unfortunately not. the only solution i can think of now, is that the debian package strips the version line from the config at build time. For some other installations/distributions I depend on the version number being part of the config file could you explain in which situations a version number in the config is required? ... jonas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#390590: /etc/cups/cups-pdf.conf is updated for every new release
Package: cups-pdf Version: 2.4.2-1 Severity: normal hello, unfortunately, a version information in /etc/cups/cups-pdf.conf is updated every new upstream release. i consider this as a bug as it causes dpkg to ask for a configfile update even if no content changed. if you have local changes in the configuration, this is very annoying. maybe you can convince upstream to remove the release version from the configuration file. ... jonas -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-1-amd64-resivo Locale: LANG=C, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Versions of packages cups-pdf depends on: ii cupsys 1.2.4-2 Common UNIX Printing System(tm) - ii gs-esp 8.15.3.dfsg.1-1 The Ghostscript PostScript interpr ii libc62.3.6.ds1-5 GNU C Library: Shared libraries cups-pdf recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
