-3736 is in place.
+Closes: #572920
+
+ -- Daniel Kobras Mon, 29 Mar 2010 11:56:52 +0200
+
mpg123 (1.4.3-4) unstable; urgency=medium
* src/wav.c: Backport upstream patch for writing WAV output to stdout
only in patch2:
unchanged:
--- mpg123-1.4.3.orig/src/module.c
+++ mpg123-1.4.3/src/mod
Hi!
According to http://qa.debian.org/excuses.php?package=graphicsmagick,
graphicsmagick 1.3.12-1 won't transition to testing because it would introduce
new bug #559811. However, this bug was closed by the current version in
testing, and also doesn't affect the unstable version. This is correctly
is in place.
+Closes: #572920
+
+ -- Daniel Kobras Mon, 29 Mar 2010 11:56:52 +0200
+
mpg123 (1.4.3-4) unstable; urgency=medium
* src/wav.c: Backport upstream patch for writing WAV output to stdout
only in patch2:
unchanged:
--- mpg123-1.4.3.orig/src/module.c
+++ mpg123-1.4.3/src/mod
=low
+
+ * src/libmpg123/readers.c: Fix fast reading of ICY streams via http.
+Patch from upstream version 1.12.3.
+
+ -- Daniel Kobras Mon, 30 Aug 2010 20:05:09 +0200
+
mpg123 (1.12.1-2) unstable; urgency=low
* configure.ac, src/libmpg123/frame.c: Apply backport of upstream patch
only in
Hi!
First of all: my apologies. I seem to have messed up the latest upload
of graphicsmagick, which involves a SONAME bump and was therefore
intended to go to experimental first, and indeed that's what the
changelog entry lists. I didn't note, however, that the Distribution
line in the changes fil
On Sat, Feb 24, 2007 at 07:32:39PM -0800, Steve Langasek wrote:
> * Rebuild with --without-dv1394 instead of --with-dv1394 (closes: 406670)
>
> This is obviously a change with non-local effects. Is this going to break
> anything else?
>
> Should I understand that the effect of --without-dv1394
On Thu, Jun 21, 2007 at 09:10:58PM +0100, Lior Kaplan wrote:
> I'd like to do a mass-bug reporting about packages not being binNMU safe.
>
> That's 1419 source packages that produce 2527 binary packages [1].
Please see the followup discussion to the mail you originally cited,
http://lists.debian.
Dear release team!
An intermittent upload of liblash2 (0.5.3-1) contained an incorrect
soname. This error was fixed in 0.5.3-2, but glashctl and muse had been
rebuilt in the meantime and picked up a bogus dependency on
liblash.so.1. A simple rebuild should get things straight. Could you
please sch
ules: Only include ALSA dependencies when respective plugin has
+been built. Original patch thanks to Petr Salinger. Fixes build failure
+on GNU/kFreeBSD. Closes: #493423
+
+ -- Daniel Kobras <[EMAIL PROTECTED]> Sun, 07 Sep 2008 17:02:54 +0200
+
mpg123 (1.4.3-3) unstable; urgency=m
On Wed, Mar 30, 2005 at 08:10:25PM -0800, Steve Langasek wrote:
> On Thu, Mar 31, 2005 at 01:31:40PM +1000, Hamish Moffatt wrote:
> > When the final freeze for sarge occurs, will time will be allowed for
> > the buildd queues to empty?
>
> I think the standard is likely to be "reasonably under co
s reads as follows:
gramofile (1.6-7) unstable; urgency=high
* 40-fast-swap-and-buffer.dpatch: Lower optimisation level to the
standard -O2. On arm, the assembler chokes on -O3.
-- Daniel Kobras <[EMAIL PROTECTED]> Fri, 29 Apr 2005 13:20:02 +0200
gramofile (1.6-6) unstable; urgency
New upstream release.
+- Do not fail with raid devices on 2.6 kernels. Closes: #308230
+- Do not mess up startup messages when monitorring interrupts.
+
+ -- Daniel Kobras <[EMAIL PROTECTED]> Mon, 9 May 2005 00:22:53 +0200
+
noflushd (2.7.4-1) unstable; urgency=low
* New
e.
Thanks,
Daniel.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Tue, 17 May 2005 13:36:54 +0200
Source: muse
Binary: muse
Architecture: source i386
Version: 0.6.3-3
Distribution: unstable
Urgency: medium
Maintainer: Daniel Kobras <[EMAIL PROTECTED]>
Changed-By: Daniel Kobras &
On Fri, Jun 17, 2005 at 09:30:43AM +0200, Josselin Mouette wrote:
> the GNOME team is facing a dillema regarding the migration of GNOME 2.10
> to sarge. The issue comes from #313219 : basically, gnomeVFS 2.10
> crashes when running over a 2.4 kernel. This comes from a bug in glibc,
> which is solve
On Tue, Jan 27, 2004 at 08:20:58AM +0900, Junichi Uekawa wrote:
> muse,libjack0.71.2-0 0.71.2 -- 228788
>
> Please feel free to NMU these packages, or they are removed from testing.
Muse is ready but waiting on fluidsynth (#229056) and ladcca to build on
all archs. Neither muse, nor fluidsynth
On Sat, Mar 27, 2004 at 01:39:44PM +0100, Frank Lichtenheld wrote:
> imagemagick
> #235712 is this really RC?
I doubt it is RC, as I already noted in my followup to the bug report.
The submitter has not provided the requested additional information so
far, either. Nothing but silence from the imag
On Tue, Aug 03, 2004 at 02:36:56AM +0200, Jeroen van Wolffelaar wrote:
> The bug was originally filed on another package, hence the weird version
> number. Because of that, I'm not 100% sure the bug is also present in
> the version currently in sarge, but since other imagemagick bugs on the
> list
On Tue, Aug 03, 2004 at 10:46:30AM +0100, Paul Martin wrote:
> On Tue, Aug 03, 2004 at 09:50:03AM +0200, Wouter Verhelst wrote:
>
> > Hm. It didn't build, but that's probably because it doesn't use whatever
> > I specify as CC:
> >
> > cc -Wall -D_GNU_SOURCE -DLinux -DVERSION=\"3.7\" -Wall -g -O2
reopen 264055 =
tag 264055 + sarge
tag 264055 + security
severity 264055 grave
thanks
On Sun, Aug 08, 2004 at 08:20:44AM -0700, Robert Woodcock wrote:
> I can reproduce this, although I'm pretty sure that we've already dropped
> privileges by this time. Any thoughts on the patch below?
When the b
Package: imagemagick
Version: 5:6.0.5.2-1
Severity: grave
Tags: security sarge
Justification: potential user security hole
Moi!
Imagemagick version 6.0.6.2 (in incoming at the moment) includes a
couple of security-related fixes for buffer overflows in several coders
(AVI, BMP, DIB, and gray). Fil
On Wed, Sep 08, 2004 at 03:39:53PM +0200, Frank Lichtenheld wrote:
> I've seen that the last imagemagick was uploaded with urgency=low
> even though it introduced some security fixes.
The last upload did not contain any security fixes, so the urgency
setting was correct. Unfortunately I had messed
tag 271673 + sid
thanks
On Wed, Sep 15, 2004 at 07:06:32PM +0200, Daniel Kobras wrote:
> [ABI breakage in imagemagick] needs to be addressed urgently.
> Otherwise we end up with packages compiled against binary incompatible
> versions of imagemagick in the archive. I have therefore pr
On Tue, Sep 13, 2005 at 02:47:26AM +0200, Frank Lichtenheld wrote:
> I plan to send the following mail about removing non-free
> documentation to d-d-a tomorrow. I would welcome if people would
> check it for factual mistakes before I do so.
Did you intentionally limit the scope to documentation,
ED]>
php3
Benjamin Drieu <[EMAIL PROTECTED]>
prestimel
Helen Faulkner <[EMAIL PROTECTED]>
labplot
Debian QA Group <[EMAIL PROTECTED]>
php4-imagick
Francois Gurin <[EMAIL PROTECTED]>
kismet
Adam Heath <[EMAIL PROTECTED]>
jmagick
Teemu Ikonen <[EMAIL
>
timidity
Matt Hope <[EMAIL PROTECTED]>
fbdesk
Falk Hueffner <[EMAIL PROTECTED]>
craft
qvwm
xskat
Teemu Hukkanen <[EMAIL PROTECTED]>
bclock
John H. Robinson, IV <[EMAIL PROTECTED]>
wmcdplay
Alberto Gonzalez Iniesta <[EMAIL PROTECTED]>
gqcam
Moi!
Current lesstif2 was built on arm with an old version of xft installed
that still shipped an .la file and therefore picked it up in its own .la
files. xft version 2.1.8.2-1 no longer ship this file, though, which
leads to FTBFS errors on arm for packages that use libtool and depend on
lesstif
On Sun, Feb 05, 2006 at 03:56:01AM -0800, Steve Langasek wrote:
> On Wed, Feb 01, 2006 at 06:41:24PM +0100, Daniel Kobras wrote:
> > Current lesstif2 was built on arm with an old version of xft installed
> > that still shipped an .la file and therefore picked it up in its own .la
o a binNMU. Can you please put them in the queue?
Helen Faulkner <[EMAIL PROTECTED]>
labplot
Peter S Galbraith <[EMAIL PROTECTED]>
gri
Ionut Georgescu <[EMAIL PROTECTED]>
grace
grace6
Debian QA Group <[EMAIL PROTECTED]>
nco
Matthias Klose <[EMAIL PROTECTED]
On Wed, Feb 08, 2006 at 08:48:57PM -0800, Steve Langasek wrote:
> On Wed, Feb 08, 2006 at 05:10:28PM +0100, Daniel Kobras wrote:
>
> > Peter S Galbraith <[EMAIL PROTECTED]>
> >gri
>
> Only needed on i386, it seems.
Not (automatically) binNMUable because
On Sun, Mar 12, 2006 at 06:40:42PM -0500, Nathanael Nerode wrote:
> I went through the RC bugs which apply to etch and are older than one year.
> This is a rather disturbing list, as you would expect from the age of the
> bugs.
> In most cases I don't think you can expect the maintainers to deal w
Hi!
The libgcc ABI breakage on hppa (#364231) is currently causing testsuite
failures in a package of mine (graphicsmagick), and therefore prevents
progression to testing. The bug log suggests that it'll take at least
another month to resolve. Is there an interim solution like forcing
affected pac
On Thu, Oct 05, 2006 at 10:43:43PM +0200, Frank Küster wrote:
> Moritz Muehlenhoff <[EMAIL PROTECTED]> wrote:
> > Frank Küster wrote:
> > > It's completely inacceptable for pdftex to acquire a dependency on gtk
> > > or qt. If using plain libpoppler turns out to be impossible, we'd
> >
> > Nearly
On Sun, Oct 22, 2006 at 12:54:34PM +0200, Moritz Muehlenhoff wrote:
> - Imagemagick needs a co-maintainer. The current maintainer seems
> really busy and hasn't replied to mail with patches since about
> a month. It also needs a fix for #393025, it anyone wants to NMU
> please ping me for a p
ation. Closes: #400847
-- Daniel Kobras <[EMAIL PROTECTED]> Wed, 13 Dec 2006 22:08:36 +0100
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Moi!
Unstable contains an updated version of manpages-de that violates just
about every rule for granting freeze exceptions, but then it's an
arch-all, documentation-only package with hardly any risk of breakage.
The source diff is quite big because of a new upstream version and
packaging changes
Moi!
The gramofile version 1.6-8 in unstable includes a patch to follow the
cdrecord -> wodim name change in Suggests, documentation files, and the
program's main menu. Two more trivial changes address lintian warnings,
and that's all the changes I'm responsible for. Unfortunately, the
package use
Hi!
The current version of graphicsmagick in unstable reinstates support for
raw images from digital cameras. This is due to a change in the
command-line interface of dcraw. The version in etch no longer groks
option -2, as it is the default behaviour now, and incidentially was the
default behavio
Moi!
Please consider the following versions currently in unstable for
inclusion in etch:
# Security fix for CVE-2007-0578
mpg123/2.7.5-6
# Debconf translation updates
noflushd/2.7.5-6
# Debconf translation updates
# (Not yet uploaded on S/390, not yet aged)
muse/0.8.1a-4
Thanks,
Daniel.
--
Hi Alessio!
Am 18.01.2012 um 19:28 schrieb Alessio Treglia:
> On Wed, Jan 18, 2012 at 3:38 PM, Niels Thykier wrote:
>> I am okay with starting the transition if you are ready to NMU glame (if
>> needed) and you (as its maintainer) don't mind beast being uninstallable
>> in sid for a while (if the
39 matches
Mail list logo
