also sprach martin f krafft [EMAIL PROTECTED] [2006.06.15.1832 +0200]:
Have you talked to the stable release team? Maybe they'd be willing
to let it into the next update?
I am sorry, I accidentally replied to this as if it had come in via
a different mailing list.
--
Please do not send copies
Christoph Biedl wrote...
Package: libtiff-tools
Version: 3.7.2-5
Severity: important
Let me elaborate on that.
How to repeat:
Use tiffsplit to split an arbitrary .tiff file:
| tiffsplit foo.tif foo.
This should result in a file name foo.aaa.tif (and foo.aab.tif and so on
if the .tiff
Hi,
I am unceratin whether a particular packaging bug warrants an upload
to stable.
We currently have the following files in firebird2-dev/stable:
usr/include/*.h
usr/lib/firebird2/include/include - a symlink to /usr/include
usr/share/doc/firebird2-dev/ - the usual stuff
As you can see, no
Now, I have a couple IMHO suggestions, let's hear what you think; I'm
not that sure about the first one, but here it goes anyway:
Oh, forgot a nice one:
- change the default for newer means newer than from 14 to 7 (as per
the RC 0-day NMU policy).
--
Adeodato Simó
I'll be happy to just filter the page locally
In fact I had been doing that for a while, since I like it a bit more
compact, and ordered per bug number instead of per package. In case
somebody else fancies it like that, these are the ones I like to look:
Le ven 16 juin 2006 14:34, Adeodato Simó a écrit :
I'll be happy to just filter the page locally
In fact I had been doing that for a while, since I like it a bit more
compact, and ordered per bug number instead of per package. In case
somebody else fancies it like that, these are the ones I
* Pierre Habouzit ([EMAIL PROTECTED]) [060616 14:58]:
Le ven 16 juin 2006 14:34, Adeodato Simó a écrit :
I'll be happy to just filter the page locally
In fact I had been doing that for a while, since I like it a bit more
compact, and ordered per bug number instead of per package. In case
Hi,
I just wanted the release team now about the plans to update ia32-libs
in sarge. The updates will just bring the ia64/amd64 packages back in
sync with the actual i386 sarge versions. So all this (hoepfully)
includes is stuff already accepted for sarge updates.
For the reasons for the
Steve Langasek wrote:
On Thu, Jun 15, 2006 at 08:20:34PM +0200, Luk Claes wrote:
Only #311188 (debian-edu-config) remained. After some discussion with
the Debian Edu Team I started filing wishlist bugs to the packages where
debian-edu-config would gain by having a way to change the conffiles
Andi requested I forward this pair of emails to debian-release;
if you wish to reply to anything in here, please keep
[EMAIL PROTECTED] in the cc as I don't read
debian-release (and was sadly unaware of it, or I would have cc'd it in
the first place).
- Forwarded message from Matthew Wilcox
On Thu, Jun 15, 2006 at 08:58:15PM +0200, Laszlo Boszormenyi [EMAIL
PROTECTED] wrote:
Hi,
This bug is open for almost two months. As Mozilla version 1.7.13 fixes
several security bugs, please package it. If you don't have time, can I
NMU it?
Please do. Nobody cares enough for mozilla
On Fri, Jun 16, 2006 at 08:37:08PM +0200, Andreas Barth wrote:
Hi,
* Matthew Wilcox ([EMAIL PROTECTED]) [060616 20:20]:
Some people want to update pci.ids on a regular basis. However, I think
these people are misguided for a number of reasons. If we have a cronjob
that goes and fetches
Matthew Wilcox wrote:
Some misc facts:
- pci.ids is currently 404k of the 660k pciutils binary package
- The pciutils udeb contains a stripped-down pci.ids file which is a mere
236k
- pci.ids is updated regularly upstream and can be retrieved from
pciids.sf.net with a script
Hello!
I also wonder if stripping down the pci.ids file in pciutils-udeb
further so it only covers NICs might be worthwhile to save space in d-i.
230k is still a lot of space for the above functionality.
Maybe we could reduce pci.ids in d-i only to devices recognized by the
kernel?
Goswin von Brederlow [EMAIL PROTECTED] writes:
Hi,
I just wanted the release team now about the plans to update ia32-libs
to know
in sarge. The updates will just bring the ia64/amd64 packages back in
sync with the actual i386 sarge versions. So all this
15 matches
Mail list logo