Processed: Re: dh_installinit: don't force upstart when both .init and .upstart exist.

2011-01-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 577040 patch Bug #577040 [debhelper] dh_installinit: don't force upstart when both .init and .upstart exist. Added tag(s) patch. > block 577040 by 591791 Bug #577040 [debhelper] dh_installinit: don't force upstart when both .init and .upsta

Bug#610083: Remove requirement to document upstream source location in debian/copyright ?

2011-01-16 Thread Charles Plessy
Le Sun, Jan 16, 2011 at 03:01:08PM +0100, Thijs Kinkhorst a écrit : > On Sun, January 16, 2011 10:39, Charles Plessy wrote: > > > > In a recent discussion about DEP-5, it was noted that often the Homepage > > field > > is redundant with the information in debian/copyright: > > > > http://lists.debi

Re: Bug#609160: DEP5: CANDIDATE and ready for use in squeeze+1

2011-01-16 Thread Steve Langasek
On Mon, Jan 17, 2011 at 09:21:25AM +1100, Ben Finney wrote: > Charles Plessy writes: > > There is another reason why I would not support an alignment on the > > Policy's version number: from the begining we promised that DEP-5 was > > not an attempt to modify the Policy. > I don't recall that pr

Bug#609160: DEP5: CANDIDATE and ready for use in squeeze+1

2011-01-16 Thread Ben Finney
Charles Plessy writes: > There is another reason why I would not support an alignment on the > Policy's version number: from the begining we promised that DEP-5 was > not an attempt to modify the Policy. I don't recall that promise ever being made. Where did you see it? The promise in the first

Re: Bug#609160: DEP5: CANDIDATE and ready for use in squeeze+1

2011-01-16 Thread Ben Finney
Charles Plessy writes: > There is another reason why I would not support an alignment on the > Policy's version number: from the begining we promised that DEP-5 was > not an attempt to modify the Policy. I don't recall that promise ever being made. Rather, the promise in the first revision of th

Re: Bug#610083: Remove requirement to document upstream source location in debian/copyright ?

2011-01-16 Thread Simon McVittie
On Sun, 16 Jan 2011 at 18:39:15 +0900, Charles Plessy wrote: > The URL of the web site for this package, preferably (when applicable) the > site > from which the original source can be obtained and any additional upstream > documentation or information may be found. I'd always interpreted t

Re: Bug#610083: Remove requirement to document upstream source location in debian/copyright ?

2011-01-16 Thread Thijs Kinkhorst
On Sun, January 16, 2011 10:39, Charles Plessy wrote: > Le Sun, Jan 16, 2011 at 09:38:51AM +0100, Thijs Kinkhorst a écrit : >> I'm not enthousiastic yet either, because the proposal lacks the >> information about what cost is associated with the current sitiuation. >> Really, it's just a few keyst

Bug#609160: DEP5: CANDIDATE and ready for use in squeeze+1

2011-01-16 Thread Charles Plessy
Le Sat, Jan 15, 2011 at 11:38:12PM +0100, Stefano Zacchiroli a écrit : > > Well, I was assuming that DEP5 was going to become an "associated text" > under policy §5.6.11 and, as such, subject to Standards-Version. That > would bring IMHO various benefits such as: 1) the possibility of > dropping F

Bug#610083: Remove requirement to document upstream source location in debian/copyright ?

2011-01-16 Thread gregor herrmann
On Sun, 16 Jan 2011 08:14:06 +, Julian Gilbey wrote: > > maybe also "if uscan just works and d/watch is > > sufficiently clear" (not a proper wording for Policy but as a rough > > idea). > Not the latter please: it is not useful if you only have the binary > package installed but not the sourc

Re: Bug#610083: Remove requirement to document upstream source location in debian/copyright ?

2011-01-16 Thread Charles Plessy
Le Sun, Jan 16, 2011 at 09:38:51AM +0100, Thijs Kinkhorst a écrit : > On Sun, January 16, 2011 03:17, Russ Allbery wrote: > > > > I'm opposed to this change as proposed because it means that we can have > > packages without any hint as to where the upstream source came from (since > > Homepage is n

Bug#588014: Correction of syntax error introduced in 45cbe74 and preventing policy to be built.

2011-01-16 Thread Charles Plessy
Dear all, I attached here a patch that corrects a syntax error introduced by one of my previous patches, applied last September (45cbe74). The policy in the current master branch (9b45eca) currently does not build for that reason. Sorry for the mess, -- Charles Plessy Tsurumi, Kanagawa, Japan >

Re: Bug#610083: Remove requirement to document upstream source location in debian/copyright ?

2011-01-16 Thread Thijs Kinkhorst
On Sun, January 16, 2011 03:17, Russ Allbery wrote: > Charles Plessy writes: >> I support Joey's comment and propose to simply remove the requirement >> from the Policy. I do not think that people will remove the information >> from debian/copyright without having a Homepage field if they do not >

Bug#610083: Remove requirement to document upstream source location in debian/copyright ?

2011-01-16 Thread Ben Finney
Russ Allbery writes: > I'm opposed to this change as proposed because it means that we can > have packages without any hint as to where the upstream source came > from (since Homepage is not required). I'm opposed to the change having anything to do with the Homepage field, since even when Homep

Bug#610083: Remove requirement to document upstream source location in debian/copyright ?

2011-01-16 Thread Julian Gilbey
On Sun, Jan 16, 2011 at 03:31:41AM +0100, gregor herrmann wrote: > What is boring (like for all CPAN modules) is to have the very same > information in 3 places (copyright, control, watch), therefore I'd > support a change like you sketched above ("may be skipped if Homepage > is clear enough") or