Package: general
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Starting with the last beta, ifupdown calls run-parts for if-*.d scripts
with --exit-on-error, so if the script fails, interface isn't marked as
configured (see #547587).
However, it's been reported that some scrip
Processing commands for cont...@bugs.debian.org:
> affects 661591 avahi-autoipd avahi-daemon bind9 bridge-utils clamav-freshclam
> controlaula epoptes-client ethtool firestarter gogoc hostapd hostap-utils
> ifenslave-2.6 ifmetric ifupdown-extra ifupdown-scripts-zg2 initscripts
> isatapd linux-w
On Mon, Feb 27, 2012 at 10:12:07AM -0800, Steve Langasek wrote:
> No disagreement with any of that. But how high is that price, in point of
> fact? If no one's measured it, then converting scripts to C programs to
> avoid the added exec() calls is premature optimization.
If it were just blindl
On 28/02/12 11:08, Riku Voipio wrote:
> What is more important is to provide the
> infrastructure to avoid the need of scripting in first place. Like in upstart
> where there are handy stanzas like umask, env, nice, limit, and so on.
This is the reason I like systemd and Upstart better than sysvin
Package: wnpp
Owner: intrigeri
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org,debian-p...@lists.debian.org
* Package name: libcairo-gobject-perl
Version : 1.001-1
Upstream Author : Torsten Schoenfeld
* URL : http://search.cpan.org/dist/Cairo-GObject/
*
Jonathan McCrohan wrote:
>Package: wnpp
>Severity: wishlist
>Owner: Jonathan McCrohan
>
>* Package name: nyancat
> Version : 0.1
> Upstream Author : Kevin Lange
>* URL : http://miku.acm.uiuc.edu/
>* License : NCSA
> Programming Lang: C
> Description : Termi
In the "humorless jerks complaining" department:
On Tue, Feb 28, 2012 at 01:23:15AM +, Jonathan McCrohan wrote:
> * Package name: nyancat
> * URL : http://miku.acm.uiuc.edu/
>
> Nyancat is an animated, color, ANSI-text telnet server that renders a loop of
> the classic Nyan Cat
* Lars Wirzenius , 2012-02-28, 12:58:
Nyancat is an animated, color, ANSI-text telnet server that renders a
loop of the classic Nyan Cat animation. Nyancat can also be run as a
standalone program in a local terminal if telnet functionality is not
required.
Is this worth including in Debian? I
Josselin Mouette writes:
> This feature was in squeeze and so far we didn’t reinstate it in 3.x on
> upstream request. This is because they complained people used this
> feature to shoot themselves in the foot and then accused gdm of being
> broken.
So they choose to break gdm and ignore all th
On 28/02/12 09:08 AM, Jakub Wilk wrote:
> * Lars Wirzenius , 2012-02-28, 12:58:
>> Is this worth including in Debian? It's funny for several
>> microfortnights, but how many people really need to install this?
>
> Completely agreed. We should not accept any new packages in section
> games and then
Package: wnpp
Severity: wishlist
Owner: Dennis van Dok
* Package name: lcas
Version : 1.3.17
Upstream Author : Nikhef Grid MW Security
* URL :
http://www.nikhef.nl/pub/projects/grid/gridwiki/index.php/Site_Access_Control
* License : Apache-2.0
Programming
Package: wnpp
Severity: wishlist
Owner: Dennis van Dok
* Package name: lcas-plugins-basic
Version : 1.3.6
Upstream Author : The Nikhef Grid Security Middleware Team
* URL :
http://www.nikhef.nl/pub/projects/grid/gridwiki/index.php/Site_Access_Control
* License
I suggest a compromise. Include the nyancat program into
the existing robotfindskitten package.
--
see shy jo
signature.asc
Description: Digital signature
Josselin Mouette writes ("Re: upstart: please update to latest upstream
version"):
> Or, as has been said countless times otherwise: kFreeBSD should not
> hinder the improvement of the Linux ports.
It's not just kFreeBSD. Accepting systemd, in the current state,
means permanently tying ourselves
On Tue, 2012-02-28 at 14:36 +, Ian Jackson wrote:
> Josselin Mouette writes ("Re: upstart: please update to latest upstream
> version"):
> > Or, as has been said countless times otherwise: kFreeBSD should not
> > hinder the improvement of the Linux ports.
>
> It's not just kFreeBSD. Acceptin
Jelmer Vernooij writes ("Re: source-contains-waf-binary tag added to nonfatal
lintian autoreject list"):
> On 02/26/2012 03:00 PM, Luca Falavigna wrote:
> > lintian 2.5.5, recently uploaded in unstable, introduced a new tag
> > called "source-contains-waf-binary", which checks whether waf "binary"
On Tue, 2012-02-28 at 11:52 +, Steve McIntyre wrote:
> Jonathan McCrohan wrote:
> >Package: wnpp
> >Severity: wishlist
> >Owner: Jonathan McCrohan
> >
> >* Package name: nyancat
> > Version : 0.1
> > Upstream Author : Kevin Lange
> >* URL : http://miku.acm.uiuc.edu/
On Sunday 26 February 2012 21:12:09 Jerome BENOIT wrote:
> > The easiest way to do this is to run
> >
> > cme fix dpkg-copyright
> >
> > (and check the results, of course.)
>
> is lintian check not enough ?
lintian will tell you what's wrong. Then you will have to fix the issue with
your fa
Le mardi 28 février 2012 à 14:36 +, Ian Jackson a écrit :
> It's not just kFreeBSD. Accepting systemd, in the current state,
> means permanently tying ourselves to the Linux kernel.
>
> The Linux kernel project has some serious and ongoing structural
> problems and I think it's very importan
On Tue, Feb 28, 2012 at 04:05:12PM +, Ben Hutchings wrote:
>On Tue, 2012-02-28 at 11:52 +, Steve McIntyre wrote:
>> Jonathan McCrohan wrote:
>> >Package: wnpp
>> >Severity: wishlist
>> >Owner: Jonathan McCrohan
>> >
>> >* Package name: nyancat
>> > Version : 0.1
>> > Upstream
On Sat, Feb 25, 2012 at 12:17:43AM +0200, Uoti Urpala wrote:
> Roger Leigh wrote:
> > On Fri, Feb 24, 2012 at 04:20:47PM +0200, Uoti Urpala wrote:
> > > > [note: it's somewhat desirable for them to be optional on Linux
> > > > too, to prevent feature lock-in and future compatibility problems].
> >
On Tue, 2012-02-28 at 17:25 +0100, Josselin Mouette wrote:
> Le mardi 28 février 2012 à 14:36 +, Ian Jackson a écrit :
> > It's not just kFreeBSD. Accepting systemd, in the current state,
> > means permanently tying ourselves to the Linux kernel.
> >
> > The Linux kernel project has some ser
On Tue, Feb 28, 2012 at 04:51:18PM +, Roger Leigh wrote:
> Excuse me, but what you're implying here is that systemd can dictate
> the development of kernel interfaces. Sorry, but that's too far.
> Can't you see the massive problem here? You are now preventing
> cgroups being removed from the
* Uoti Urpala [120227 22:02]:
> Bernhard R. Link wrote:
> > While there might be some problems originating from some architecture,
> > but most problems you will see and people claim to be "problems specific
> > to fringe architectures" are actual bugs in the program you just do not
> > *yet* see
Svante Signell writes:
> There are alternatives to systemd and upstart available: runit and GNU
> DMD ("Daemon managing Daemons") as well as links to other OS init
> systems at http://smarden.org/runit/. The DMD looks a little
> unmaintained though, latest release in 2003, but at least this is a
Uoti Urpala writes:
> I think it's quite arrogant of BSD users to expect others to work to
> support their systems.
There's qute a difference between parts of debian expecting upstream to
do the work and upstream hostily denying existing patches I'd say
Regards
Christoph
--
To UNSUBSCRI
Le 28/02/2012 09:44, Ben Armstrong a écrit :
>> * Lars Wirzenius , 2012-02-28, 12:58:
>>> Debian already has 35 thousand binary packages. Do we really need to
>>> package everything? Even a tiny software toy brings a bit of burden to
>>> the entire project:
> ...
>>> translators need to translate
On Tue, Feb 28, 2012 at 12:22 PM, Russ Allbery wrote:
> I, for one, have even more of a problem
> contributing to FSF projects that require copyright assignment than I
> would contributing to upstart.
Hi Russ,
Would you comment on why you have issues with the FSF contributor agreement?
Thanks,
Matt Zagrabelny writes:
> On Tue, Feb 28, 2012 at 12:22 PM, Russ Allbery wrote:
>> I, for one, have even more of a problem contributing to FSF projects
>> that require copyright assignment than I would contributing to upstart.
> Would you comment on why you have issues with the FSF contributor
On Tue, 28 Feb 2012, Russ Allbery wrote:
> When people are complaining about Canonical's contributor licensing
> agreement, saying that something is appealing because it's a GNU
> project is kind of amusing. I, for one, have even more of a problem
> contributing to FSF projects that require copyrig
* Ben Armstrong , 2012-02-28, 09:44:
Debian already has 35 thousand binary packages. Do we really need to
package everything? Even a tiny software toy brings a bit of burden
to the entire project:
...
translators need to translate the description, etc.
New translations increase amount of data
* Steve McIntyre , 2012-02-28, 16:20:
I've just done lots of QA work tracking down build failures while
bootstrapping a new architecture, typically in pet packages that have
gone largely unmaintained after a small number of uploads.
Out of curiosity, why are pet packages important for bootstra
Hi Andrew,
On Tue, Feb 28, 2012 at 11:24:43AM +0100, Andrew O. Shadura wrote:
> Starting with the last beta, ifupdown calls run-parts for if-*.d scripts
> with --exit-on-error, so if the script fails, interface isn't marked as
> configured (see #547587).
> However, it's been reported that some sc
On 28.02.2012 20:27, Steve Langasek wrote:
> subsequent hooks. OTOH, there might be cases where that's beneficial
> because it lets a critical hook declare that an interface bring-up hasn't
> succeeded and the interface bring-up should be rolled back so the admin can
> try again.
If that is the
On Tue, Feb 28, 2012 at 08:25:31PM +0100, Jakub Wilk wrote:
> * Steve McIntyre , 2012-02-28, 16:20:
> >I've just done lots of QA work tracking down build failures while
> >bootstrapping a new architecture, typically in pet packages that
> >have gone largely unmaintained after a small number of uplo
Le 28/02/2012 15:22, Jakub Wilk a écrit :
> Are translators held in a labor camp and forced to translate
> descriptions of every single package? I thought that they are
> volunteers, and that they translate stuff because it's fun for them.
I thought translations were useful for our users, and tha
On Tue, Feb 28, 2012 at 04:51:18PM +, Roger Leigh wrote:
> On Sat, Feb 25, 2012 at 12:17:43AM +0200, Uoti Urpala wrote:
> > Roger Leigh wrote:
> > > On Fri, Feb 24, 2012 at 04:20:47PM +0200, Uoti Urpala wrote:
> > > > > [note: it's somewhat desirable for them to be optional on Linux
> > > > > t
]] Ian Jackson
> Josselin Mouette writes ("Re: upstart: please update to latest upstream
> version"):
> > Or, as has been said countless times otherwise: kFreeBSD should not
> > hinder the improvement of the Linux ports.
>
> It's not just kFreeBSD. Accepting systemd, in the current state,
> me
Ben Hutchings writes:
> On Tue, Feb 28, 2012 at 04:51:18PM +, Roger Leigh wrote:
>> On Sat, Feb 25, 2012 at 12:17:43AM +0200, Uoti Urpala wrote:
>> > Roger Leigh wrote:
>> > > On Fri, Feb 24, 2012 at 04:20:47PM +0200, Uoti Urpala wrote:
>> > > > > [note: it's somewhat desirable for them to be
> And since, after seven months, nothing happened, it means no one is
> interested enough,
The conclusion seems rather hasty to me. I'm not able to write that script
but would gladly open pdf files from mutt.
As Adreas Tille, I would like to voice my astonishment by this decision to
intentionaly
On Tue, Feb 28, 2012 at 09:58:01PM +0100, Goswin von Brederlow wrote:
> Ben Hutchings writes:
>
> > On Tue, Feb 28, 2012 at 04:51:18PM +, Roger Leigh wrote:
> >> On Sat, Feb 25, 2012 at 12:17:43AM +0200, Uoti Urpala wrote:
> >> > Roger Leigh wrote:
> >> > > On Fri, Feb 24, 2012 at 04:20:47PM
reassign 661591 ifupdown
thanks
Hi,
just from what I've read in those two replies to this bug yet, I think I agree
that this change should be reverted.
And if you really want/need/do this change which needs changes in 30 (or so)
other packages, then please file 30 bugs against those package an
Processing commands for cont...@bugs.debian.org:
> reassign 661591 ifupdown
Bug #661591 [general] packages providing ifupdown scripts must have those
scripts fixed if needed
Bug reassigned from package 'general' to 'ifupdown'.
> thanks
Stopping processing here.
Please contact me if you need assi
Hello,
On Tue, 28 Feb 2012 22:37:29 +0100
Holger Levsen wrote:
> just from what I've read in those two replies to this bug yet, I
> think I agree that this change should be reverted.
> And if you really want/need/do this change which needs changes in 30
> (or so) other packages, then please fil
Hello,
On Tue, 28 Feb 2012 22:37:29 +0100
Holger Levsen wrote:
> (And I'd prefer this bug to be one against ifupdown and not
> general, but YMMV.) But, definitly, filing a bug against general
> saying these and these package need to be fixed wont do it.
Also, I find it fits general perfectly,
On Tue, Feb 28, 2012 at 09:09:22PM +0100, Andrew Shadura wrote:
> On Tue, 28 Feb 2012 11:27:37 -0800
> Steve Langasek wrote:
> > > However, it's been reported that some scripts return wrong exit
> > > codes sometimes, causing failure during network configuration.
> > My doubt here is: what is th
On Tue, Feb 28, 2012 at 08:47:16PM +0100, Michael Biebl wrote:
> > subsequent hooks. OTOH, there might be cases where that's beneficial
> > because it lets a critical hook declare that an interface bring-up hasn't
> > succeeded and the interface bring-up should be rolled back so the admin can
> >
Hello,
On Tue, 28 Feb 2012 14:27:15 -0800
Steve Langasek wrote:
> > When failure to execute a hook leads to interface being
> > non-operational.
> Yes, that's probably a reasonable threshold. What should packages
> like miredo and wide-dhcpv6-client do? Both of these hooks have to
> do with r
On Tue, Feb 28, 2012 at 10:59:42PM +0100, Andrew Shadura wrote:
> Hello,
>
> On Tue, 28 Feb 2012 22:37:29 +0100
> Holger Levsen wrote:
>
> > (And I'd prefer this bug to be one against ifupdown and not
> > general, but YMMV.) But, definitly, filing a bug against general
> > saying these and these
Humm. I didn't expect that this ITP would generate so much discussion. :-/
On 28/02/12 16:20, Steve McIntyre wrote:
> On Tue, Feb 28, 2012 at 04:05:12PM +, Ben Hutchings wrote:
>> On Tue, 2012-02-28 at 11:52 +, Steve McIntyre wrote:
>>> And what value does this bring to Debian?
>>
>> Are s
On Feb 28, Ian Jackson wrote:
> The Linux kernel project has some serious and ongoing structural
> problems and I think it's very important that as a project we keep our
> options open.
Even if I were willing to accept this argument as valid[1], it's worth
remembering that switching to a new (an
On Feb 28, Svante Signell wrote:
> > means permanently tying ourselves to the Linux kernel.
> Definitely, and this is not in line with Debian goals.
Says who?
--
ciao,
Marco
signature.asc
Description: Digital signature
On 28.02.2012 23:29, Steve Langasek wrote:
> On Tue, Feb 28, 2012 at 08:47:16PM +0100, Michael Biebl wrote:
>>> subsequent hooks. OTOH, there might be cases where that's beneficial
>>> because it lets a critical hook declare that an interface bring-up hasn't
>>> succeeded and the interface bring-u
On Feb 28, Steve Langasek wrote:
> Yes, that's probably a reasonable threshold. What should packages like
> miredo and wide-dhcpv6-client do? Both of these hooks have to do with
Maybe they could stop pretending that the ifupdown configuration model
can properly support multiple address familie
Le Tue, Feb 28, 2012 at 08:16:03PM +, Ben Hutchings a écrit :
> On Tue, Feb 28, 2012 at 08:25:31PM +0100, Jakub Wilk wrote:
> > * Steve McIntyre , 2012-02-28, 16:20:
> > >I've just done lots of QA work tracking down build failures while
> > >bootstrapping a new architecture, typically in pet pa
On Wed, Feb 29, 2012 at 8:07 AM, Charles Plessy wrote:
> if a couple of gag programs can not upgraded. Couldn't we keep a place in our
> namespace and our mirrors for such programs, in a section where best effort is
> the rule ? I do understand it is not that easy; security comes to mind
> immed
On Wed, Feb 29, 2012 at 7:30 AM, Jonathan McCrohan wrote:
> I certainly don't plan on uploading and abandoning this package, but
> given the high level of opposition to this ITP, guess there is little
> point pursuing it.
I would suggest joining the Debian games team, we might sponsor this,
since
On Feb 26, Goswin von Brederlow wrote:
> By that reasonsing we should not support bsd, hurd, mips, arm, ppc,
> ia64, s390 either. Hell lets drop i386 too.
Indeed. The reason we support niche architectures and toy ports is that
some people are interested in doing the work, and that these do not
I demand that Steve Langasek may or may not have written...
[snip]
> One of the worst contributors to the use of 'script' in upstart jobs
> instead of 'exec' is the need for backwards-compatibility with pre-upstart
> /etc/default/* files. The options here are all fairly poor:
>
> - ignore the a
Hello,
On Wed, 29 Feb 2012 00:47:57 +0100
m...@linux.it (Marco d'Itri) wrote:
> > Yes, that's probably a reasonable threshold. What should packages
> > like miredo and wide-dhcpv6-client do? Both of these hooks have to
> > do with
> Maybe they could stop pretending that the ifupdown configurat
David Prévot writes:
> So no, “translators [are not] held in a labor camp”, but undervaluing
> their work (“because it's fun for them”) seems rude, at least.
I would find it rude if someone asserted that what I do for Debian is
not something I find fun.
I do not see how it's undervaluing one's
61 matches
Mail list logo
