Your message dated Mon, 07 Jul 2003 09:10:45 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#200268: general: .dpkg-dist and .dpkg-old files in cron.* and modutils dirs has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -------------------------------------- Received: (at submit) by bugs.debian.org; 6 Jul 2003 21:55:39 +0000 >From [EMAIL PROTECTED] Sun Jul 06 16:55:37 2003 Return-path: <[EMAIL PROTECTED]> Received: from gprs35.vodafone.hu (notebook) [80.244.97.85] by master.debian.org with esmtp (Exim 3.35 1 (Debian)) id 19ZHTr-0007GG-00; Sun, 06 Jul 2003 16:55:37 -0500 Received: from cstamas by notebook with local (Exim 3.36 #1 (Debian)) id 19ZHSL-0000Si-00; Sun, 06 Jul 2003 23:54:01 +0200 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: Csillag Tamas <[EMAIL PROTECTED]> To: Debian Bug Tracking System <[EMAIL PROTECTED]> Subject: general: .dpkg-dist and .dpkg-old files in cron.* and modutils dirs X-Mailer: reportbug 2.10.1 Date: Sun, 06 Jul 2003 23:53:59 +0200 Message-Id: <[EMAIL PROTECTED]> Sender: Csillag Tamas <[EMAIL PROTECTED]> X-BadReturnPath: [EMAIL PROTECTED] rewritten as [EMAIL PROTECTED] using "From" header Delivered-To: [EMAIL PROTECTED] X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_01,HAS_PACKAGE version=2.53-bugs.debian.org_2003_06_27 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_06_27 (1.174.2.15-2003-03-30-exp) Package: general Version: unavailable; reported 2003-07-06 Severity: normal Hi! Problem: I have a laptop system, I recently upgraded to sarge (from woody) and I noticed the following problem: I moved some script from /etc/cron.daily to /etc/cron.weekly (to save power) But when dpkg asked me whether I want to install the new version of it's config file I answered no. Now a new file package.dpkg-dist appears and if i answered yes the old one will be renamed to package.dpkg-old (This is fine for normal dirs but not for these which are parsed by *simple* scripts) This is not the expected behaviour because now I have scripts which I already removed, and the same applies to /etc/modutils, if a new package makes an upgrade here, there can be duplicated entries in /etc/modules.conf How to solve: If you move a new config file to a new directory it will be harder find those files. So dpkg should explicitly tell the user that this directory must be checked after the upgrade or you should tell that the original/new files will be moved to this and this directory. -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux notebook 2.4.21-rc2-laptopmode2 #2 2003. máj. 23., péntek, 12.20.04 CEST i586 Locale: LANG=hu_HU, LC_CTYPE=hu_HU --------------------------------------- Received: (at 200268-done) by bugs.debian.org; 7 Jul 2003 07:11:44 +0000 >From [EMAIL PROTECTED] Mon Jul 07 02:11:35 2003 Return-path: <[EMAIL PROTECTED]> Received: from mailbox.surfeu.at (surfeu.at) [212.197.128.120] by master.debian.org with esmtp (Exim 3.35 1 (Debian)) id 19ZQ9s-00074M-00; Mon, 07 Jul 2003 02:11:32 -0500 Received: from [81.5.252.8] (HELO downhill.univie.ac.at) by surfeu.at (CommuniGate Pro SMTP 3.5.9) with ESMTP id 54479609 for [EMAIL PROTECTED]; Mon, 07 Jul 2003 09:11:30 +0200 Received: from ametzler by downhill.univie.ac.at with local (Exim 4.20) id 19ZQ97-0001J5-H8; Mon, 07 Jul 2003 09:10:45 +0200 From: Andreas Metzler <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Re: Bug#200268: general: .dpkg-dist and .dpkg-old files in cron.* and modutils dirs In-Reply-To: <[EMAIL PROTECTED]> X-Newsgroups: local.debian-devel Mail-Followup-To: <debian-devel@lists.debian.org> X-Archive: encrypt X-GPG-Fingerprint: BCF7 1345 BE42 B5B8 1A57 EE09 1D33 9C65 8B8D 7663 X-Face: &b=<Cp*r&PZn.xNlsF}#g*I1ZyC/E%^zD!$M57SU<0:[s0(~_{3{7AXn/`FO'z!!3`8'$Gr .%Hy: [EMAIL PROTECTED]&CuC>,[EMAIL PROTECTED]<7362+W"u<cA.DpE=Q!;+*,Y)2 User-Agent: tin/1.5.19-20030626 ("Darts") (UNIX) (Linux/2.4.21acpi (i686)) Message-Id: <[EMAIL PROTECTED]> Date: Mon, 07 Jul 2003 09:10:45 +0200 Delivered-To: [EMAIL PROTECTED] X-Spam-Status: No, hits=-13.0 required=4.0 tests=BAYES_30,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT, REPLY_WITH_QUOTES,USER_AGENT autolearn=ham version=2.53-bugs.debian.org_2003_06_27 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_06_27 (1.174.2.15-2003-03-30-exp) In article <[EMAIL PROTECTED]> (local.debian-devel) you wrote: > I have a laptop system, I recently upgraded to sarge (from woody) > and I noticed the following problem: > I moved some script from /etc/cron.daily to /etc/cron.weekly (to save > power) > But when dpkg asked me whether I want to install the new version of it's > config file I answered no. Now a new file package.dpkg-dist appears and > if i answered yes the old one will be renamed to package.dpkg-old > (This is fine for normal dirs but not for these which are parsed by > *simple* scripts) No, there is no problem, because Debian's scripts are not _that_ simple. The files in /etc/cron.(daily|weekly) are executed (by crond or anacron) using "run-parts --report /etc/cron.daily", which will ignore these files (because of the period in the filename) run-parts(8) | Filenames should consist entirely of upper and lower case letters, | digits, underscores, and hyphens. Subdirectories of directory and | files with other names will be silently ignored. > This is not the expected behaviour because now I have scripts which I > already removed, and the same applies to /etc/modutils, if a new package > makes an upgrade here, there can be duplicated entries in > /etc/modules.conf [...] No, there won't be duplicated entries update-modules(8) | update-modules will ignore files that match the following regular | expression: *\(\.dpkg-[a-z]*\|~\)$ | (ie files with the extension .dpkg-new, .dpkg-orig, .dpkg-dist, | .dpkg-old, or whose filename end with a ~). > So dpkg should explicitly tell the user that this directory must be > checked after the upgrade or you should tell that the original/new > files will be moved to this and this directory. All configuration files rest in /etc, you can list them using find /etc -name '*.dpkg-*' cu andreas