Your message dated Mon, 15 Feb 2010 10:39:40 +0100
with message-id <[email protected]>
and subject line please enable libburnia support in brasero
has caused the Debian Bug report #494697,
regarding please enable libburnia support in brasero
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 [email protected]
immediately.)
--
494697: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=494697
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: brasero
Version: 0.8.0-2
Severity: wishlist
Hi,
now that all libburnia packages in Debian are in the latest upstream
version, support for these libraries should be enabled in the brasero
package.
Cheers,
Fabian
--
Dipl.-Phys. Fabian Greffrath
Ruhr-Universität Bochum
Lehrstuhl für Energieanlagen und Energieprozesstechnik (LEAT)
Universitätsstr. 150, IB 3/134
D-44780 Bochum
Telefon: +49 (0)234 / 32-26334
Fax: +49 (0)234 / 32-14227
E-Mail: [email protected]
--- End Message ---
--- Begin Message ---
Version: 2.28.3-2
brasero (2.28.3-2) unstable; urgency=low
* Enable libburnia plugins, adding corresponding build-dependencies.
* Entirely disable cdrtools and cdrkit plugins. This will remove any
reference to schilyware.
* Rename 011_* patch to 11_.
* 01_pkglibdir.patch: use $(pkglibdir) instead of $(libdir)/brasero so
that it can be overriden.
* 90_relibtoolize.patch: re-apply the autotools on top of it.
* Pass pkglibdir= argument to make invocation, with a versioned
directory.
* Install the plugins in libbrasero-media0 instead of brasero.
* Force strict dependency for brasero on libbrasero-media0.
* Move some dependencies/recommends to libbrasero-media0 as well.
-- Josselin Mouette <[email protected]> Wed, 13 Jan 2010 20:51:03 +0100
--- End Message ---
