Re: Conffiles

2010-01-04 Thread Matthew Johnson
On Sun Jan 03 19:57, Russ Allbery wrote: Symlinks in /etc pointing to files not in /etc are used now, so I'm not sure they should be Policy violations. /etc/nologin is the canonical example. Depending on how and whether Debian adopts upstart, we may have other cases. Shouldn't they be files

Re: dpkg 3.0 (quilt) packages not being accepted?

2010-01-04 Thread Gunnar Wolf
[ Following up to my earlier mail sent to debian-devel - Quoting in full for context sake ] Gunnar Wolf dijo [Mon, Jan 04, 2010 at 03:27:49PM -0600]: Archive Administrator dijo [Mon, Jan 04, 2010 at 06:03:24PM +]: Reject Reasons: 'dpkg-source -x' failed for

Re: dpkg 3.0 (quilt) packages not being accepted?

2010-01-04 Thread Cyril Brulebois
Gunnar Wolf gw...@gwolf.org (04/01/2010): It seems the problem is reproducible on all Lenny hosts - And it is quite likely to be a proper bug, as the file is for some reason recognized as a v2.0 source package. My previous (accepted) upload was done on 2009-11-25, and dpkg-dev dies the same

Re: Conffiles

2010-01-04 Thread Manoj Srivastava
On Sun, Jan 03 2010, Russ Allbery wrote: Manoj Srivastava sriva...@ieee.org writes: On Sun, Jan 03 2010, Russ Allbery wrote: I don't believe that listing symlinks as conffiles works properly at the moment. See #421344. It doesn't make any sense to list a directory as a conffile. I think

Re: Conffiles

2010-01-04 Thread Russ Allbery
Manoj Srivastava sriva...@ieee.org writes: On Sun, Jan 03 2010, Russ Allbery wrote: Symlinks in /etc pointing to files not in /etc are used now, so I'm not sure they should be Policy violations. /etc/nologin is the canonical example. Depending on how and whether Debian adopts upstart, we

Re: dpkg 3.0 (quilt) packages not being accepted?

2010-01-04 Thread Raphael Hertzog
Hi, On Tue, 05 Jan 2010, Cyril Brulebois wrote: Open questions AFAICT: - why was the previous upload accepted? Maybe less checks being run at the time, e.g. not involving dpkg-source? At one point, dak was ignoring any unpack failure reported by dpkg-source. That was the case until some

Bug#563658: dpkg: triggers are run when nothing has changed

2010-01-04 Thread Robert Lemmen
Package: dpkg Version: 1.14.25 Severity: minor hi folks, i ran a dpkg -i *.deb against a deb that i could not install on my system, which of course fails. the triggers however get processed anyway, which seems excessive: Preparing to replace mnemosyne 1.2.1-1 (using mnemosyne_1.2.1-2_all.deb)

Bug#563658: marked as done (dpkg: triggers are run when nothing has changed)

2010-01-04 Thread Debian Bug Tracking System
Your message dated Mon, 4 Jan 2010 14:56:01 +0100 with message-id 20100104135601.gc25...@rivendell and subject line Re: Bug#563658: dpkg: triggers are run when nothing has changed has caused the Debian Bug report #563658, regarding dpkg: triggers are run when nothing has changed to be marked as

Bug#563752: dpkg-dev: implementation of symbol patterns framework as well as c++, wildcard, regexp patterns

2010-01-04 Thread Modestas Vainius
Package: dpkg-dev Version: 1.15.5.5 Severity: wishlist Tags: patch Hello, This bug is more like a follow up of the message #61 [1] in bug #533916. I have finally finished implementing symbol patterns to full extent, i.e. the code has undergone clean up and it is as nice as I can write it. What