Raphael Hertzog <[EMAIL PROTECTED]> writes:
> Yes, it means that packages not using quilt and without upstream
> changes in the .diff.gz have an empty quilt series.
Thanks for that clarification.
Nevertheless, an obviously useful exercise, leading to some concrete
guidelines. Thank you!
--
\
On Thu, Jul 03, 2008 at 10:40:53PM +0200, Raphael Hertzog wrote:
> > The option "--oknodo" changes the behaviour to the LSB recomendations but
> > many services in Debian don't use this option and return 1 in the case
> > I've quotted. This is very problematic for me when I try to use a Debian
> >
Right, expanding on my previous comments:
On Thu, Jul 03, 2008 at 11:02:13PM +0200, Iñaki Baz Castillo wrote:
> > The alternative is to change policy and/or lintian to ensure that packages
> > are using --oknodo unless they have a good reason not to.
> > > [1] LSB specifications about init script
Reply-To:
In-Reply-To: <[EMAIL PROTECTED]>
reassign 426877 debian-policy 3.8.0.1
retitle 426877 Clarify what "sensible behaviour" is for init scripts
thanks
Ok, this confirms my initial feeling. Changing this in dpkg would require
a wide-scale testing and much effort for little gains since the p
Package: wnpp
Severity: wishlist
Owner: Edi Stojicevic <[EMAIL PROTECTED]>
* Package name: libsvn-dump-perl
Version : 0.04
Upstream Author : Philippe Bruhat (BooK)
* URL : http://search.cpan.org/dist/SVN-Dump-0.04/lib/SVN/Dump.pm
* License : GPL
Programming L
Package: wnpp
Severity: wishlist
Owner: Stefan Potyra <[EMAIL PROTECTED]>
* Package name: faumachine
Version : 0.2008.1
Upstream Author : FAUmachine Team <[EMAIL PROTECTED]>
* URL : http://www.faumachine.org/
* License : GPL
Programming Lang: C
Descript
On Fri, 04 Jul 2008, Raphael Hertzog wrote:
> Here's a try (against current master branch):
> diff --git a/policy.sgml b/policy.sgml
> index c9bd84f..772afce 100644
> --- a/policy.sgml
> +++ b/policy.sgml
> @@ -5946,9 +5946,11 @@ rmdir /usr/local/share/emacs 2>/dev/null || true
> The init
On Fri, Jul 04, 2008 at 01:15:19PM +0800, Paul Wise wrote:
> On Fri, Jul 4, 2008 at 11:05 AM, Ryan Kavanagh <[EMAIL PROTECTED]> wrote:
>
> > * Package name: password
> > Description : Compact ruby random password generator
> >
> > Little random password generator which generates a random
Raphael Hertzog <[EMAIL PROTECTED]> writes:
> diff --git a/policy.sgml b/policy.sgml
> index c9bd84f..772afce 100644
> --- a/policy.sgml
> +++ b/policy.sgml
> @@ -5946,9 +5946,11 @@ rmdir /usr/local/share/emacs 2>/dev/null || true
> The init.d scripts must ensure that they will
>
El Viernes, 4 de Julio de 2008, Raphael Hertzog escribió:
> Ok, this confirms my initial feeling. Changing this in dpkg would require
> a wide-scale testing and much effort for little gains since the policy
> already require packages to behave sensibly.
It seems that some services return 0 and oth
(please respect Mail-Followup-To:, as I'm not subscribed to this list)
Hi,
I've worked on some improvements to the tinyproxy package, and I'm
looking for reviewers before I upload this to unstable.
My main interest in NMUing this was enabling transparent proxy support
to the package, but after s
On Thu, Jul 03, 2008 at 11:02:13PM +0200, Iñaki Baz Castillo wrote:
> I think being LSB compliant is good for Debian.
That may be so; but changing a long-standing interface with no migration
is /not/ good for Debian.
--
Home is where you have to wash the dishes.
-- #debian-devel, Freenode, 20
Package: wnpp
Severity: wishlist
Owner: Patrick Schoenfeld <[EMAIL PROTECTED]>
* Package name: ratproxy
Version : 1.51
Upstream Author : Michal Zalewski <[EMAIL PROTECTED]>
(Copyright: 2007, 2008 by Google)
* URL : http://code.google.com/p/ratproxy/
Package: wnpp
Severity: wishlist
Owner: Iustin Pop <[EMAIL PROTECTED]>
* Package name: ratproxy
Version : 1.51
Upstream Author : Michal Zalewski <[EMAIL PROTECTED]>
* URL : http://code.google.com/p/ratproxy/
* License : Apache-2.0
Programming Lang: C
Descrip
On Wed, Apr 16, 2008 at 4:53 PM, Romain Beauxis <[EMAIL PROTECTED]> wrote:
> Le Wednesday 16 April 2008 15:44:56 Neil Williams, vous avez écrit :
>> An upload of a new application is nowhere near as complex as the upload
>> to start a library SONAME transition. Even uploading a new library never
>>
On Fri, 04 Jul 2008, Iñaki Baz Castillo wrote:
> # lighttpd running:
> ~# /etc/init.d/lighttpd start ; echo $?
> * Starting web server lighttpd
> [fail]
> 1
[...]
> > Iñaki, if you ever encounter
> > bad init scripts, please report bugs against the offending packages.
>
> In the above case which
Hi,
On Fri, 2008-07-04 at 01:47:39 -0700, Steve Langasek wrote:
> > I think being LSB compliant is good for Debian.
>
> The LSB init script specification *is a specification for the init scripts
> of LSB packages*. It has NOTHING to do with LSB compliance of LSB
> implementations. Debian is an
Steve Langasek wrote:
>> I'm reluctant to change the default behaviour of start-stop-daemon at this
>> point. What do other people think of making --oknodo the default behaviour
>> and adding a new option to force the current default behaviour (exit with
>> failure if nothing had to be done)?
>
>
Jordi Mallach dijo [Fri, Jul 04, 2008 at 06:25:58PM +0200]:
> (please respect Mail-Followup-To:, as I'm not subscribed to this list)
>
> Hi,
>
> I've worked on some improvements to the tinyproxy package, and I'm
> looking for reviewers before I upload this to unstable.
>
> My main interest in NM
Hi,
On Fri, Jul 04, 2008 at 02:08:23PM -0500, Gunnar Wolf wrote:
> Given the above mentioned factors (mainly, you are adding
> functionality and not just fixing a bug, and the maintainer is not at
> all active), I'm sure you have tried to ping Ed Boraas on this
> regard. Why don't you take over th
A little while ago on debian-python, we discussed the location of
system files that are executable bytecode, created by package
management tools at install time, and how to comply with th FHS.
Ben Finney <[EMAIL PROTECTED]> writes:
> Josselin Mouette <[EMAIL PROTECTED]> writes:
>
> > As for the
[Marvin Renich]
> If the package does need to save state, don't enable the "quick halt"
> option! The maintainer definitely ought to know this.
Why are all of you talking as though sending SIGTERM were not the
standard way to tell a process to save its state and exit gracefully?
It's certainly t
22 matches
Mail list logo
