Holi Special [1]Shop Now!
If you are having trouble viewing this email, click here to [2]view it
online.
To ensure emails are delivered, please add promo_speci...@johareez.com
to your address book.
[3]Johareez
Other Featured Promotions:
- Refer a Friend and SAVE 10% on your order! [4]Learn more.
Hi,
I've just seen an (ugly) instance of many quilt patches in
debian/patches that are patching things inside the debian/ folder. I am
wondering if it would be wise to forbid this entirely, and write about
it in the policy (maybe it is there already?). There's no sane reason
why this would happen:
On Tue, Mar 06, 2012 at 02:46:44PM -0800, Josh Triplett wrote:
> Wouter Verhelst wrote:
> > On Tue, Mar 06, 2012 at 02:08:00PM +, Jon Dowland wrote:
> > > On Tue, Mar 06, 2012 at 10:12:43AM +0100, Wouter Verhelst wrote:
> > > > But I do think that writing portable software isn't that hard, and
Paul Wise writes:
> I would suggest asking the FSF licensing folks and debian-legal.
Good point about debian-legal, I'll repost the question there. I have
talked to the FSF and they suggest LGPLv3+ but will live with
dual-GPLv2+|LGPLv3+ if there are significant GPLv2-only applications in
the fr
On 07.03.2012 00:21, Fernando Lemos wrote:
> Hi,
>
> On Tue, Mar 6, 2012 at 7:46 PM, Josh Triplett wrote:
>> To give one particular example: systemd uses Linux-specific features to
>> accurately track all the processes started by a service, which allows
>> accurate monitoring and shutdown of proc
Florian Weimer writes:
> * Simon Josefsson:
>
>> I co-maintain the libidn package. As upstream, I recently relicensed it
>> from LGPLv2+ to GPLv2+|LGPLv3+. I'd like to upload the latest version
>> into Debian before Wheezy since a pretty nasty inifinte-loop bug has
>> been fixed.
>
> Should we
On Wed, 07 Mar 2012 16:53:00 +0800
Thomas Goirand wrote:
> I've just seen an (ugly) instance of many quilt patches in
> debian/patches that are patching things inside the debian/ folder. I am
> wondering if it would be wise to forbid this entirely, and write about
> it in the policy (maybe it is
Hi,
On Wed, 07 Mar 2012, Thomas Goirand wrote:
> I've just seen an (ugly) instance of many quilt patches in
> debian/patches that are patching things inside the debian/ folder. I am
> wondering if it would be wise to forbid this entirely, and write about
> it in the policy (maybe it is there alrea
On Wed, Mar 07, 2012 at 10:52:57AM +0100, Raphael Hertzog wrote:
> It's already caught by lintian as an error:
> http://lintian.debian.org/tags/patch-modifying-debian-files.html
>
> In any case it's definitely not a good idea and it breaks when you use 3.0
> (quilt).
>
> I don't know of any valid
On 07/03/12 09:34, Neil Williams wrote:
> Turn the problem around - if someone (me) comes to you about one
> of your packages with a set of changes which are necessary to be
> able to rebuild your package, say, without perl or without SSL or
> without LDAP support - how would you prefer that to be
On Wed, 7 Mar 2012 10:52:57 +0100
Raphael Hertzog wrote:
> On Wed, 07 Mar 2012, Thomas Goirand wrote:
> > I've just seen an (ugly) instance of many quilt patches in
> > debian/patches that are patching things inside the debian/ folder. I am
> > wondering if it would be wise to forbid this entirel
Raphael Hertzog writes:
> Hi,
>
> On Wed, 07 Mar 2012, Thomas Goirand wrote:
>> I've just seen an (ugly) instance of many quilt patches in
>> debian/patches that are patching things inside the debian/ folder. I am
>> wondering if it would be wise to forbid this entirely, and write about
>> it in
Michael Biebl writes:
> On 07.03.2012 00:21, Fernando Lemos wrote:
>> Hi,
>>
>> On Tue, Mar 6, 2012 at 7:46 PM, Josh Triplett wrote:
>>> To give one particular example: systemd uses Linux-specific features to
>>> accurately track all the processes started by a service, which allows
>>> accurate
On Wed, Mar 7, 2012 at 4:53 PM, Thomas Goirand wrote:
> I've just seen an (ugly) instance of many quilt patches in
> debian/patches that are patching things inside the debian/ folder. I am
> wondering if it would be wise to forbid this entirely, and write about
> it in the policy (maybe it is ther
On Wed, 07 Mar 2012, Neil Williams wrote:
> Quick question, therefore, what is the method of using dpkg-vendor to
> modify a postinst which uses a grep option which is not supported by
> busybox?
>
> Or a method for removing a single line from a .install file?
Like you want. One possible approach
Detailed replies below, but first of all, a quick top-level response,
because in my previous mail I missed mentioning an obvious point:
systemd can easily become the default for Debian GNU/*Linux* without
necessarily becoming the default for Debian GNU/kFreeBSD. This seems
like the most likely sce
* Neil Williams [120307 10:35]:
> Not within Debian uploads and buildd's, true, but there are good reasons
> for this to remain technically possible for derivatives. The ability for
> someone downstream of Debian to patch debian/control[.in] and [...]
On the other hand that is also a very good re
On Wed, 07 Mar 2012 10:27:27 +
Simon McVittie wrote:
> On 07/03/12 09:34, Neil Williams wrote:
> > Turn the problem around - if someone (me) comes to you about one
> > of your packages with a set of changes which are necessary to be
> > able to rebuild your package, say, without perl or witho
Package: general
Severity: important
Dear Maintainer,
I have some problem with USB, mass storage devices and printer (it detect some
component as storage device), sometimes it send a lot of logs to
/var/log/syslog, like these:
Mar 7 08:02:20 dacer kernel: [668285.604061] usb 1-8: reset high-spee
On Wed, Mar 07, 2012 at 11:17:44AM +0100, Michael Hanke wrote:
>
> Not exactly the same thing, but for backporting for various releases we
> (NeuroDebian) quite often have to adjust the Debian packaging itself,
> but still want to have everything stored in a single source package.
> And we do stor
Peter Samuelson wrote:
> [Josh Triplett]
> > To give one particular example: systemd uses Linux-specific features
> > to accurately track all the processes started by a service, which
> > allows accurate monitoring and shutdown of processes which could
> > otherwise disassociate themselves from the
Package: wnpp
Severity: wishlist
Owner: "Kai Wasserbäch"
* Package name: libimager-qrcode-perl
Version : 0.033
Upstream Author : Yoshiki KURIHARA
* URL : http://search.cpan.org/dist/Imager-QRCode/
* License : GPL-1+ or Artistic (same as Perl 5.8.8 or later)
On Wed, 7 Mar 2012, dacer wrote:
Dear Maintainer,
I have some problem with USB, mass storage devices and printer (it detect some
component as storage device), sometimes it send a lot of logs to
/var/log/syslog, like these:
Mar 7 08:02:20 dacer kernel: [668285.604061] usb 1-8: reset high-speed
On Wed, Mar 07, 2012 at 12:52:53PM +0100, Andreas Tille wrote:
> On Wed, Mar 07, 2012 at 11:17:44AM +0100, Michael Hanke wrote:
> >
> > Not exactly the same thing, but for backporting for various releases we
> > (NeuroDebian) quite often have to adjust the Debian packaging itself,
> > but still wa
Package: wnpp
Severity: wishlist
Owner: Dennis van Dok
* Package name: ees
Version : 0.1.2
Upstream Author : MW security developers at Nikhef
* URL :
https://twiki.cern.ch/twiki/bin/view/EGEE/AuthorizationFramework
* License : Apache 2
Programming Lang: C
On 03/07/2012 06:33 PM, Neil Williams wrote:
> Even with such calls, I don't see how to remove a single line from
> a .install file using dpkg-vendor. (Typically this is necessary when
> the line in question contains a wildcard but the modified build means
> that no files can exist which match said
Thomas Goirand writes:
> On 03/07/2012 06:33 PM, Neil Williams wrote:
>> Even with such calls, I don't see how to remove a single line from
>> a .install file using dpkg-vendor. (Typically this is necessary when
>> the line in question contains a wildcard but the modified build means
>> that no f
On 03/07/2012 07:15 PM, Bernhard R. Link wrote:
> Whether it might make sense for derivatives to mangle upstream with
> packaging changes in other files might be a matter of opinion
> (I'm personally quite happy that is no longer possible), but
> debian/control should really be something you should
Le Wed, Mar 07, 2012 at 01:05:50AM +0100, Arno Töll a écrit :
>
> On 07.03.2012 00:58, Charles Plessy wrote:
> > Would it be possible to pass -D_FORTIFY_SOURCE=2 in CFLAGS in
> > addition to CPPFLAGS ?
>
> Actually dpkg did in 1.16.1 which was reverted later (for good
> reasons). See #643632 for
On 03/07/2012 05:34 PM, Neil Williams wrote:
> Not within Debian uploads and buildd's, true, but there are good reasons
> for this to remain technically possible for derivatives. The ability for
> someone downstream of Debian to patch debian/control[.in]
Our policy doesn't apply to derivatives (th
On 2012-03-06 19:43, Georges Khaznadar wrote:
> Programming Lang: Java
> Description : applets for modules used by the WIMS server
> This package was formerly made from the source package for wims.
> However, wims cannot be built completely on architectures which have
> no JVM available,
python-poppler bindings are incomplete, I am missing one for
ps_file_new. I feel that I have to patch it myself, but am at a loss for
understanding how it works. The build system has a poppler.defs file
which gets compiled to C code using a badly documented format. (The
documentation I could find d
On Wed, Mar 7, 2012 at 1:28 PM, Jens Stimpfle wrote:
> python-poppler bindings are incomplete, I am missing one for
> ps_file_new. I feel that I have to patch it myself, but am at a loss for
> understanding how it works. The build system has a poppler.defs file
> which gets compiled to C code usin
Le dimanche 04 mars 2012 à 00:31 +0100, Timo Weingärtner a écrit :
> Advantages over other hardlinking tools:
> * predictability: arguments are scanned in order, each first version is kept
> * much lower CPU and memory consumption
> * hashing option: speedup on many equal-sized, mostly iden
also sprach Jean-Christophe Dubacq [2012.03.07.1825 +0100]:
> I, for one, would like a program that (starting from some paths on same
> harddrive), would find all identical files (not considering mtime and
> mode, this is for backups and I do not care), hardlink them (choosing
> whatever comes fir
Charles Plessy schrieb:
> Le Wed, Feb 29, 2012 at 10:52:10PM +0100, Moritz Muehlenhoff a écrit :
>> -BEGIN PGP SIGNED MESSAGE-
>>
>> Since it will be almost impossible to convert all packages before
>> Wheezy freezes, a specific sub-group of packages receives targeted
>> attention:
>>
>
Le mercredi 07 mars 2012 à 18:46 +0100, martin f krafft a écrit :
> also sprach Jean-Christophe Dubacq [2012.03.07.1825
> +0100]:
> > I, for one, would like a program that (starting from some paths on same
> > harddrive), would find all identical files (not considering mtime and
> > mode, this is
* Simon Josefsson:
> It wouldn't hurt, but I'm also not sure if it is worth the work. If any
> significant application triggered this particular code path, people
> should have noticed the problem a long time ago. It is at worst an
> easily diagnozed DoS causing the library to busy-loop forever.
* Charles Plessy [120307 16:27]:
> Thanks (and thanks Cyril) for the hint. Still there are two things
> I do not understand:
>
> - Why and when it is a problem to add preprocessor flags in CFLAGS.
Becuase CFLAGS is not meant for preprocessor flags. Adding stuff in
unexpected places might break
On Tue, Mar 6, 2012 at 20:35:53 +0100, Simon Josefsson wrote:
> I co-maintain the libidn package. As upstream, I recently relicensed it
> from LGPLv2+ to GPLv2+|LGPLv3+.
So maybe that's a stupid question, but... Why? You didn't have enough
license headaches?
Cheers,
Julien
signature.asc
Des
* Simon Josefsson:
> Florian Weimer writes:
>
> (GPLv2-only and LGPLv3+ are incompatible.)
Nowadays, almost all GPLv2-only programs link to library code licensed
under the GPLv3 (with a linking exception on the library side), so we
pretend that they are, at least to some d
Florian Weimer writes:
(GPLv2-only and LGPLv3+ are incompatible.)
>>>
>>> Nowadays, almost all GPLv2-only programs link to library code licensed
>>> under the GPLv3 (with a linking exception on the library side), so we
>>> pretend that they are, at least to some degree.
>>
>> How does that l
Julien Cristau writes:
> On Tue, Mar 6, 2012 at 20:35:53 +0100, Simon Josefsson wrote:
>
>> I co-maintain the libidn package. As upstream, I recently relicensed it
>> from LGPLv2+ to GPLv2+|LGPLv3+.
>
> So maybe that's a stupid question, but... Why? You didn't have enough
> license headaches?
On Wed, Mar 7, 2012 at 21:03:25 +0100, Simon Josefsson wrote:
> Julien Cristau writes:
>
> > On Tue, Mar 6, 2012 at 20:35:53 +0100, Simon Josefsson wrote:
> >
> >> I co-maintain the libidn package. As upstream, I recently relicensed it
> >> from LGPLv2+ to GPLv2+|LGPLv3+.
> >
> > So maybe tha
On 12-03-07 at 09:25pm, Julien Cristau wrote:
> On Wed, Mar 7, 2012 at 21:03:25 +0100, Simon Josefsson wrote:
>
> > Julien Cristau writes:
> >
> > > On Tue, Mar 6, 2012 at 20:35:53 +0100, Simon Josefsson wrote:
> > >
> > >> I co-maintain the libidn package. As upstream, I recently
> > >> reli
On Wed, Mar 07, 2012 at 10:24:39AM +0100, Michael Biebl wrote:
> > By the way, upstart uses ptrace for this:
> > http://netsplit.com/2007/12/07/how-to-and-why-supervise-forking-processes/
> > It's an interesting trick, and probably more portable too.
> It's an ugly hack, even Scott didn't like t
On 07.03.2012 22:46, Steve Langasek wrote:
> On Wed, Mar 07, 2012 at 10:24:39AM +0100, Michael Biebl wrote:
>
>> It's rather easy to confuse upstart's process tracking. You
>> explicitly have to tell upstart if a daemon forks once or twice
>> (expect daemon, expect fork) and if the daemon forks mu
Package: wnpp
Severity: wishlist
Owner: Oxan van Leeuwen
* Package name: libnfc
Version : 1.6.0~rc1
Upstream Author : multiple people
* URL : http://www.libnfc.org/
* License : LGPL-3
Programming Lang: C
Description : Near Field Communication (NFC) libr
Steve Langasek wrote:
> There are also complications to using cgroups, in that suddenly any service
> that needs to be able to spawn long-running processes that outlive the
> service has to start caring about cgroups - both so that they survive the
> service being shut down from the outside, and so
Package: wnpp
Severity: wishlist
Owner: Jonathan McCrohan
* Package name: transmission-remote-cli
Version : 1.1
Upstream Author : Ben Thompson
* URL : https://github.com/fagga/transmission-remote-cli
* License : GPLv3
Programming Lang: Python
Description
Am 07.03.2012 23:34, schrieb Michael Biebl:
On 07.03.2012 22:46, Steve Langasek wrote:
On Wed, Mar 07, 2012 at 10:24:39AM +0100, Michael Biebl wrote:
It's rather easy to confuse upstart's process tracking. You
explicitly have to tell upstart if a daemon forks once or twice
(expect daemon, expe
On Mar 06, Wouter Verhelst wrote:
> > Should Debian reject using > component> just to support toy ports which are used by a dozen of people?
> Except that kFreeBSD is not a toy port.
>
> FreeBSD is a serious operating system that is used by many people in
> system-critical applications, which r
On Thu, 8 Mar 2012 02:25:52 +0100
m...@linux.it (Marco d'Itri) wrote:
I'm not taking a stance on the wider issue, just wanted to comment on
these two points.
> On Mar 06, Wouter Verhelst wrote:
>
> > > Should Debian reject using > > system
> > > component> just to support toy ports which are
Michael Biebl writes:
> Am 07.03.2012 23:34, schrieb Michael Biebl:
>> On 07.03.2012 22:46, Steve Langasek wrote:
>>> On Wed, Mar 07, 2012 at 10:24:39AM +0100, Michael Biebl wrote:
>>>
It's rather easy to confuse upstart's process tracking. You
explicitly have to tell upstart if a daemo
On Wed, Mar 7, 2012 at 2:32 PM, Michael Hanke wrote:
> On Wed, Mar 07, 2012 at 12:52:53PM +0100, Andreas Tille wrote:
>> On Wed, Mar 07, 2012 at 11:17:44AM +0100, Michael Hanke wrote:
>> >
>> > Not exactly the same thing, but for backporting for various releases we
>> > (NeuroDebian) quite often h
]] Steve Langasek
> There are also complications to using cgroups, in that suddenly any service
> that needs to be able to spawn long-running processes that outlive the
> service has to start caring about cgroups - both so that they survive the
> service being shut down from the outside, and so t
On Thu, Mar 08, 2012 at 07:52:11AM +0100, Reinhard Tartler wrote:
> On Wed, Mar 7, 2012 at 2:32 PM, Michael Hanke wrote:
> > On Wed, Mar 07, 2012 at 12:52:53PM +0100, Andreas Tille wrote:
> >> Was you aware about dpkg-vendor at the time of writing this script?
> >
> > Yes, but AFAIK it was neither
Tollef Fog Heen writes:
> ]] Steve Langasek
>> ssh is going to be the first problem in this regard, though I'm sure
>> there will be others. Has someone patched openssh to be cgroup-aware?
> This is most of what libpam-systemd does. No need to patch sshd itself.
Er, "UsePAM no"?
sshd has a
58 matches
Mail list logo
