Re: Add Debian revision number standards to policy?

2005-11-21 Thread Steve Langasek
On Mon, Nov 21, 2005 at 03:23:17PM +0100, Goswin von Brederlow wrote: > Nathanael Nerode <[EMAIL PROTECTED]> writes: > > I was surprised to discover that the standard rules for Debian > > revision numbers > > (maintainer revisions contain no dots; > > source NMUs contain one dots; > > binary NMU

Bug#340189: debian-policy: gzipped fhs-2.3 documentation is corrupt

2005-11-21 Thread Gabor Gombas
Package: debian-policy Version: 3.6.2.1 Severity: normal Hi, It seems the gzipped FHS-2.3 documentation is corrupt: $ cd /usr/share/doc/debian-policy/fhs $ gzip -t fhs-2.3.pdf.gz gzip: fhs-2.3.pdf.gz: unexpected end of file $ gzip -t fhs-2.3.ps.gz gzip: fhs-2.3.ps.gz: unexpected end of file $

Re: Add Debian revision number standards to policy?

2005-11-21 Thread Bill Allombert
On Mon, Nov 21, 2005 at 03:23:17PM +0100, Goswin von Brederlow wrote: > Nathanael Nerode <[EMAIL PROTECTED]> writes: > The other scheme would be to declare a special char '#' that sorts > lower than everything but \000 and '~'. > > 1.2-3~pre1 > 1.2-3 > 1.2-3#1 > 1.2-3sarge1 > 1.2-3.1 > > This wou

Re: Add Debian revision number standards to policy?

2005-11-21 Thread Loïc Minier
On Mon, Nov 21, 2005, Goswin von Brederlow wrote: > Since common practice for NMU, binNMU and security versions are > flawed, as in they don't sort right with dpkg --compare-versions, I > would rather see a new scheme be made policy. > Currently versions sort the following way: > 1.2-3 > 1.2-3sarge

Re: Add Debian revision number standards to policy?

2005-11-21 Thread Goswin von Brederlow
Nathanael Nerode <[EMAIL PROTECTED]> writes: > I was surprised to discover that the standard rules for Debian > revision numbers > (maintainer revisions contain no dots; > source NMUs contain one dots; > binary NMUs contain two) > are not in Policy, but only in the Developer's Reference. > > Thi

Re: Bug#339955: sysv-rc: /etc/init.d/*.sh should be sourced in runlevel S

2005-11-21 Thread Brendan O'Dea
On Mon, Nov 21, 2005 at 09:34:11AM +0100, Thomas Hood wrote: >Brendan O'Dea wrote: >> Note: I believe that "return" should work to exit from a script both >> when sourced and when executed but perhaps someone with a copy of POSIX >> could confirm. > > >Disconfirmation: > >$ cat /tmp/s >#!/bin/bash

Re: Bug#339955: sysv-rc: /etc/init.d/*.sh should be sourced in runlevel S

2005-11-21 Thread Brendan O'Dea
On Mon, Nov 21, 2005 at 09:55:22AM +0100, Thomas Hood wrote: >Brendan O'Dea wrote: >> there are quite a few instances in /etc/init.d/*.sh scripts where "exit" is >> called. > >All the exit commands are either (1) at the end of usage exception sections, >or (2) preceded by colons ':'. Testing sugge

Re: [Pkg-sysvinit-devel] Bug#339955: sysv-rc: /etc/init.d/*.sh should be sourced in runlevel S

2005-11-21 Thread Petter Reinholdtsen
I'm not sure how this could happen, but when I enabled sourcing of the .sh scripts in rcS.d/, the boot failed because /etc/rcS.d/S01glibc.sh uses 'exit 0' at the end of the script, and thus terminates the S runlevel. This script was added in glibc version 2.3.5-5 uploaded 2005-08-27. The strange