Package: wnpp
Severity: normal
Description-en: RFC 822/2068 header and unheader functions
This module provides two new functions, header and unheader,
which provide general-purpose RFC 822 header construction and parsing.
They do not provide any intelligent defaults of HTTP-specific methods.
T
On 09/21/2015 06:12 PM, Raphael Hertzog wrote:
> Hi,
>
> On Sun, 20 Sep 2015, Joerg Jaspert wrote:
>>> (It seems they are implicitly considered a master when updating the
>>> bikeshed's ACLs) I would have thought "Owner:" would make more sense
>>> than "Master:" fwiw.
>>
>> Then you end up having
Package: wnpp
Owner: Andy Beverley
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org, debian-p...@lists.debian.org
* Package name: libdpkg-parse-perl
Version : 0.03
Upstream Author : Adam Jacob
* URL : https://metacpan.org/release/DPKG-Parse
* License
On Wed, Sep 23, 2015 at 12:20 PM, Mattia Rizzolo wrote:
> On Wed, Sep 23, 2015 at 11:30:55AM -0430, PICCORO McKAY Lenz wrote:
>> There's any consensus around quakeworld packagin?
>
> I don't hold a clue. Also you removed debian-devel@ from CC, so it's
> quite improbable somebody will reply to you.
On Sat, Sep 26, 2015 at 03:30:39PM +0200, Ole Streicher wrote:
> Jakub Wilk writes:
> > Instead, you should use something like this:
> >
> > Depends: ${astrometry-data}, ${misc:Depends}
> >
> > and generate substitution for ${astrometry-data} appropriate for the
> > host architecture in debian/rul
On Sat, 2015-09-26 at 14:35 +0200, Wouter Verhelst wrote:
> On Thu, Sep 24, 2015 at 11:56:56AM +0100, Colin Watson wrote:
> > On Thu, Sep 24, 2015 at 12:29:59PM +0200, Santiago Vila wrote:
> > > But once we are able to trigger a rebuild with sourceful NMUs, as
> > > Ubuntu does, binNMUs will hopefu
Jakub Wilk writes:
> Also, the syntax is wrong. Architectures between square brackets
> should be separated by spaces.
OK. I diddn't find this in the docs.
> But more importantly, every time you hardcode architecture list in
> debian/control, you make architecture bootstrappers cry.
>
> Instead,
At Thu, 24 Sep 2015 08:11:48 -0400,
Marvin Renich wrote:
>
> * Jeroen Dekkers [150924 07:23]:
> > At Wed, 23 Sep 2015 13:53:11 -0400,
> > Marvin Renich wrote:
> > > I think it should be documented in the developers reference that if you
> > > attempt to start or restart a service in postinst, you
On Sat, Sep 26, 2015 at 03:04:47PM +0200, Jakub Wilk wrote:
> But more importantly, every time you hardcode architecture list in
> debian/control, you make architecture bootstrappers cry.
>
> Instead, you should use something like this:
>
> Depends: ${astrometry-data}, ${misc:Depends}
>
> and ge
On Sat, Sep 26, 2015 at 03:04:47PM +0200, Jakub Wilk wrote:
> * Rene Engelhard , 2015-09-26, 14:30:
> >>Just to make it sure: for the architectures that currently built
> >>on Debian (officially or inofficially), I should then use
> >>someting like the following in d/control:
> >>
> >>Depends: astr
* Rene Engelhard , 2015-09-26, 14:30:
Just to make it sure: for the architectures that currently built on
Debian (officially or inofficially), I should then use someting like
the following in d/control:
Depends: astrometry-data-tycho2-07-bigendian [any-amd64 | any-i386 | armel |
mipsel | ppc6
Package: wnpp
Severity: wishlist
Owner: Stephen Kitt
* Package name: miller
Version : 2.2.1
Upstream Author : John Kerl
* URL : https://github.com/johnkerl/miller
* License : BSD-2-Clause
Programming Lang: C
Description : name-indexed data processing t
On Thu, Sep 24, 2015 at 11:56:56AM +0100, Colin Watson wrote:
> On Thu, Sep 24, 2015 at 12:29:59PM +0200, Santiago Vila wrote:
> > But once we are able to trigger a rebuild with sourceful NMUs, as
> > Ubuntu does, binNMUs will hopefully be a thing of the past.
>
> Amusingly, the way we do it in Ub
Hi,
On Sat, Sep 26, 2015 at 02:05:41PM +0200, Ole Streicher wrote:
> Just to make it sure: for the architectures that currently built on
> Debian (officially or inofficially), I should then use someting like the
> following in d/control:
>
> Depends: astrometry-data-tycho2-07-bigendian [any-amd64
Gert Wollny writes:
> How about creating one package -bigendian and one -lowendian and a
> virtual package that depends on one or the other based on the
> architecture?
Just to make it sure: for the architectures that currently built on
Debian (officially or inofficially), I should then use some
Gert Wollny writes:
> On Sat, 2015-09-26 at 10:28 +0200, Ole Streicher wrote:
>> Hi all,
>>
>> I need to package some large (~80MB) data files with a machine
>> dependent byte order.
>>
>> How should I do this?
>>
> How about creating one package -bigendian and one -lowendian and a
> virtual pa
Hello,
On Sat, 2015-09-26 at 10:28 +0200, Ole Streicher wrote:
> Hi all,
>
> I need to package some large (~80MB) data files with a machine
> dependent byte order.
>
> How should I do this?
>
How about creating one package -bigendian and one -lowendian and a
virtual package that depends on one
Hallo,
* Marvin Renich [Fri, Sep 25 2015, 08:26:34AM]:
> > > Still, that would need some proper design work, and a reasonable amount of
> > > code to be written and tested. Some of it will hook into the package
> > > system, some of it needs to interface to the services subsystem (systemd,
> > >
* Ole Streicher , 2015-09-26, 10:28:
How should I do this?
* Creating machine dependent data files (arch=ANY) is obviously wasting
Debian server space. Also, all big endian archs would share the same
files.
* Putting files for all endianesses into the same package would also
waste Debian se
Hi all,
again a question for large data files (and still the same packages [1] :-) )
I need to package some large (~80MB) data files with a machine dependent
byte order.
How should I do this?
* Creating machine dependent data files (arch=ANY) is obviously wasting
Debian server space. Also, al
20 matches
Mail list logo
