Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#696679: unblock: libmikmod/3.1.12-5
1 view
Skip to first unread message
Gergely Nagy
Dec 25, 2012, 12:40:01 PM12/25/12
to
Package: release.debian.org
User: release.d...@packages.debian.org
Usertags: unblock
Severity: normal
Please unblock package libmikmod
The current package in testing suffers from a serious issue (not
reported though, only observed while preparing -5): in certain cases,
applications that rely on libmikmod will not see any driver but the
nosound one, effectively rendering them useless. As it turns out,
enabling the fortify hardening flags breaks libmikmod's module loading,
so -5 turns that off, as a temporary measure until I figure out what the
underlying problem really is.
It also rearranges the order of sound drivers, so nosound is preferred
over saving to music.raw, as to not pollute the filesystem with huge
music files. With this change in place, the pulseaudio-esound-compat |
oss-compat recommendation could be lowered to suggests.
All of these are fairly trivial changes, but nevertheless, would make
the libmikmod version in wheezy much more useful, so I'd like to request
an unblock for it.
A debdiff between -4.1 (currently in wheezy) and -5 (in unstable) has
been attached. Some parts of the diff have been omitted, as they're just
noise (timestamp changes under debian/patches, and other noops like
that).
Thanks in advance!
unblock libmikmod/3.1.12-5
--
|8]
User: release.d...@packages.debian.org
Usertags: unblock
Severity: normal
Please unblock package libmikmod
The current package in testing suffers from a serious issue (not
reported though, only observed while preparing -5): in certain cases,
applications that rely on libmikmod will not see any driver but the
nosound one, effectively rendering them useless. As it turns out,
enabling the fortify hardening flags breaks libmikmod's module loading,
so -5 turns that off, as a temporary measure until I figure out what the
underlying problem really is.
It also rearranges the order of sound drivers, so nosound is preferred
over saving to music.raw, as to not pollute the filesystem with huge
music files. With this change in place, the pulseaudio-esound-compat |
oss-compat recommendation could be lowered to suggests.
All of these are fairly trivial changes, but nevertheless, would make
the libmikmod version in wheezy much more useful, so I'd like to request
an unblock for it.
A debdiff between -4.1 (currently in wheezy) and -5 (in unstable) has
been attached. Some parts of the diff have been omitted, as they're just
noise (timestamp changes under debian/patches, and other noops like
that).
Thanks in advance!
unblock libmikmod/3.1.12-5
--
|8]
Julien Cristau
Dec 30, 2012, 3:20:02 PM12/30/12
to
On Tue, Dec 25, 2012 at 18:18:48 +0100, Gergely Nagy wrote:
> A debdiff between -4.1 (currently in wheezy) and -5 (in unstable) has
> been attached. Some parts of the diff have been omitted, as they're just
> noise (timestamp changes under debian/patches, and other noops like
> that).
>
It would've been nice if the noise had been avoided.
> A debdiff between -4.1 (currently in wheezy) and -5 (in unstable) has
> been attached. Some parts of the diff have been omitted, as they're just
> noise (timestamp changes under debian/patches, and other noops like
> that).
>
Cheers,
Julien
Julien Cristau
Dec 30, 2012, 3:20:02 PM12/30/12
to
On Tue, Dec 25, 2012 at 18:18:48 +0100, Gergely Nagy wrote:
> libmikmod (3.1.12-4.1) unstable; urgency=low
>
> - * Non-maintainer upload (acknowledged by maintainer).
> + * Non-maintainer upload.
> * Apply patches from Hans de Goede and Pantelis Koukousoulas to enable
> the ESD driver, so we can interoperate with PulseAudio (Closes: #385844)
> * Recommend pulseaudio-esound-compat | oss-compat because if we don't have
> one of those, the fallback path is to write output to ./music.raw, which
> is unlikely to be what you want!
>
> - -- Simon McVittie <sm...@debian.org> Fri, 19 Oct 2012 22:05:18 +0100
> + -- Simon McVittie <sm...@debian.org> Fri, 19 Oct 2012 09:12:08 +0100
>
Why is this entry modified?
Cheers,
Julien
Debian Bug Tracking System
Dec 30, 2012, 3:30:01 PM12/30/12
to
Your message dated Sun, 30 Dec 2012 21:18:57 +0100
with message-id <2012123020...@radis.cristau.org>
and subject line Re: Bug#696679: unblock: libmikmod/3.1.12-5
has caused the Debian Bug report #696679,
regarding unblock: libmikmod/3.1.12-5
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
696679: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696679
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
with message-id <2012123020...@radis.cristau.org>
and subject line Re: Bug#696679: unblock: libmikmod/3.1.12-5
has caused the Debian Bug report #696679,
regarding unblock: libmikmod/3.1.12-5
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
696679: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696679
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Gergely Nagy
Dec 30, 2012, 3:30:01 PM12/30/12
to
latest changes (which, by the way, are all accounted for, the change
that wasn't in his git is reverted by -5) that were uploaded, and I
only noticed that when preparing the debdiff. Sorry about that.
--
|8]
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
0 new messages