On Sun, 26 Feb 2012 01:19:14 +0100
Matthias Klumpp wrote:
> 2012/2/26 Uoti Urpala :
> > Cyril Brulebois wrote:
> >> Uoti Urpala (26/02/2012):
> >> > Is there reason to believe this would be a particular problem
> >> > with systemd? Most of the controversy I've seen surrounding
> >> > Poettering
2012/2/26 Uoti Urpala :
> Cyril Brulebois wrote:
>> Uoti Urpala (26/02/2012):
>> > Is there reason to believe this would be a particular problem with
>> > systemd? Most of the controversy I've seen surrounding Poettering has
>> > been due to people resisting the kind of change he has championed. I
Package: wnpp
Severity: wishlist
Owner: Samuel Thibault
* Package name: netdde
Version : 0.0.20120225
Upstream Author : GNU/Hurd maintainers
* URL : http://www.gnu.org/software/hurd/
* License : GPLv2
Programming Lang: C
Description : Linux network driv
On 02/22/2012 10:40 AM, Elena Grandi wrote:
> * Package name: python-gnupg
> Version : 0.2.8
> Upstream Author : Vinay Sajip
> * URL : http://code.google.com/p/python-gnupg/
> * License : BSD
> Programming Lang: Python
> Description : python wrapper for
Cyril Brulebois wrote:
> Uoti Urpala (26/02/2012):
> > Is there reason to believe this would be a particular problem with
> > systemd? Most of the controversy I've seen surrounding Poettering has
> > been due to people resisting the kind of change he has championed. I
> > don't remember seeing muc
Package: wnpp
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've been approached by someone who is willing to update this package
for the new upstream MIBs bundle, and would like them to help out.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAk9J
Uoti Urpala (26/02/2012):
> Is there reason to believe this would be a particular problem with
> systemd? Most of the controversy I've seen surrounding Poettering has
> been due to people resisting the kind of change he has championed. I
> don't remember seeing much about him being "difficult to w
Russ Allbery wrote:
> While this is true, note that the main objection to CLAs is that it limits
> the potential field of contributors. One of the other things that *also*
> substantially limits the field of contributors is an upstream who is
> confrontational and difficult to work with. I'm not
Package: wnpp
Severity: wishlist
Owner: Ryan Tandy
* Package name: meh
Version : 0.3
Upstream Author : John Hawthorn
* URL : http://www.johnhawthorn.com/meh/
* License : MIT
Programming Lang: C
Description : a simple, minimalist, super fast image viewe
On Sat, Feb 25, 2012 at 11:36:04AM -0800, Steve Langasek wrote:
> On Thu, Feb 23, 2012 at 08:08:18PM +, Tzafrir Cohen wrote:
> > On Thu, Feb 23, 2012 at 07:24:20AM +0100, Tollef Fog Heen wrote:
> > > ]] Tzafrir Cohen
>
> > > > In sysv init scripts the daemon forks into the background. In upst
On Thu, Feb 23, 2012 at 08:08:18PM +, Tzafrir Cohen wrote:
> On Thu, Feb 23, 2012 at 07:24:20AM +0100, Tollef Fog Heen wrote:
> > ]] Tzafrir Cohen
> > > In sysv init scripts the daemon forks into the background. In upstrart
> > > and systemd it doesn't have to (or shouldn't). (not) forking re
Josselin Mouette writes:
> So it should not be a blocker, but it is certainly something to take
> into consideration before choosing software, when alternative exists
> that is not encumbered in such a way.
While this is true, note that the main objection to CLAs is that it limits
the potential
* Giovanni Mascellani , 2012-02-25, 18:39:
Package name: fstransform
Version: 0.9.1
Upstream Author: Massimiliano Ghilardi
URL: http://sourceforge.net/projects/fstransform/
License: GPL-3+
Description: Tool for in-place filesystem conversion
fstransform is a tool to
Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org
Package name: fstransform
Version: 0.9.1
Upstream Author: Massimiliano Ghilardi
URL: http://sourceforge.net/projects/fstransform/
License: GPL-3+
Description: Tool for in-place filesyst
Package: wnpp
Severity: wishlist
Owner: Kees de Jong
* Package name: raintpl
Version : 2.7.1.2
Upstream Author : Federico Ulfo
The Rain Team
* URL : http://www.raintpl.com/
* License : (LGPL-3+)
Programming Lang: (PHP)
Package: wnpp
Severity: wishlist
Owner: Alessandro Ghedini
* Package name: libaudio-tagger-perl
Version : 0.08
Upstream Author : Alessandro Ghedini
* URL : http://search.cpan.org/dist/Audio-Tagger/
* License : GPL-1+ or Artistic
Programming Lang: C++, Perl
Processing commands for cont...@bugs.debian.org:
> retitle 661241 description of "general" pseudo-package is misleading (sounds
> too much like a catch-all)
Bug #661241 [general] general: Sounds gets quiet, problem uncontrolable
Changed Bug title to 'description of "general" pseudo-package is mi
retitle 661241 description of "general" pseudo-package is misleading (sounds
too much like a catch-all)
reassign 661241 reportbug 6.3.1
submitter 661241 !
quit
Hi,
Mikko Koho wrote:
> Sometimes I switch sounds off from panel, when I'm trying get them back
> machine
> is still quiet. VLC-mediap
Package: general
Severity: important
Tags: l10n
LXDE desktop, package sources are wheezy and squeeze (both because Wine doesn't
found from wheezy-archive).
Sometimes I switch sounds off from panel, when I'm trying get them back machine
is still quiet. VLC-mediaplayer and Iceweasel-browser aren't
Le vendredi 24 février 2012 à 18:18 -0800, Steve Langasek a écrit :
> I can well understand why some Free Software developers would decide not to
> contribute to a project that requires copyright assignment or a copyright
> license agreement such as this one. But it would be historical revisionis
On 2012-02-25, Ben Hutchings wrote:
> Of the others, I've never got the impression that they're actively
> soliciting contributions from outside the company, though I could be
> wrong. I think free software developers rarely quibble over licences if
Qt is now actively trying to get contributions
On Sat, 2012-02-25 at 10:54 +, Adam D. Barratt wrote:
> You're expected to send mails to a technical list in a manner such that
> it shouldn't matter who any of the participants may or may not be
> employed by or what other interests they may have. That was the primary
> point of both my and R
On Sat, 2012-02-25 at 11:36 +0100, Svante Signell wrote:
> On Sat, 2012-02-25 at 09:37 +, Adam D. Barratt wrote:
> > On Sat, 2012-02-25 at 00:51 +0100, Svante Signell wrote:
> > > On Fri, 2012-02-24 at 15:42 -0800, Steve Langasek wrote:
> > > Are you really committed to Debian? Maybe you should
On Sat, 2012-02-25 at 09:37 +, Adam D. Barratt wrote:
> On Sat, 2012-02-25 at 00:51 +0100, Svante Signell wrote:
> > On Fri, 2012-02-24 at 15:42 -0800, Steve Langasek wrote:
> [...]
> > Why not simply implement the early boot event driven parts in init as
> > proposed earlier, and get rid of th
On Sat, Feb 25, 2012 at 5:33 PM, Lars Wirzenius wrote:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=621833 and its merged
> bugs are a discussion about changing or setting the policy on this.
> The consensus is that packages should never remove the users they
> create.
I tend to think it sh
On Sat, 2012-02-25 at 00:51 +0100, Svante Signell wrote:
> On Fri, 2012-02-24 at 15:42 -0800, Steve Langasek wrote:
[...]
> Why not simply implement the early boot event driven parts in init as
> proposed earlier, and get rid of these non-portable commercial stuff.
> Are you really committed to Deb
On Sat, Feb 25, 2012 at 01:02:14PM +0400, Alexander GQ Gerasiov wrote:
> I have the question about user removal in package's postrm script.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=621833 and its merged
bugs are a discussion about changing or setting the policy on this.
The consensus is th
Hi there.
I have the question about user removal in package's postrm script.
Is this correct?
I see the following scenario:
Package creates user for internal use only, and there will be no files
owned by this user left after package removal. In this case there will
be no problem if we remove us
28 matches
Mail list logo
