Hi,
> get the source package (apt-get source) and just edit
> plugins/libburnia/burn-libburn.c
Does it still have that name ?
Are there other occasions of burn_write_opts_set_write_type() in 3.4 ?
(Meanwhile i stirred up the system enough to get this:
Message from syslogd@debian2 at Jul 7 21:32:25 ...
kernel:[34537.006023] Oops: 0000 [#1] SMP
Now brasero starts as dull grey window. I better reboot.
Ok. It lives again. The re-start plague spreads from GUI to kernel.
Owee !
)
-------------------------------------------------------------------------
I try to exercise the procedure in my squeeze:
$ vi ./plugins/libburnia/burn-libburn.c
There are two occasions of burn_write_opts_set_write_typ() with three
calls. Strangely the porcessing path with erasing of CD-RW does not
obey (flags & BRASERO_BURN_FLAG_DAO) but sets TAO unconditionally.
$ dpkg-source --commit
dpkg-source: need a command (-x, -b, --before-build, --after-build,
--print-format)
... usage instructions ...
$
I make a backup of the altered source file and try
$ dpkg-buildpackage
...
dpkg-source: info: local changes stored in
brasero-2.30.3/debian/patches/debian-changes-2.30.3-2, the modified files are:
brasero-2.30.3/libbrasero-burn/burn-process.c
brasero-2.30.3/plugins/libburnia/burn-libburn.c
dpkg-source: info: building brasero in brasero_2.30.3-2.debian.tar.gz
...
It is addicted to my upstream installation in /usr/local/lib now.
Refuses to link if there is no /usr/local/lib/libburn.so.
# dpkg -i brasero_2.30.3-2_amd64.deb
But brasero still produces TAO. Grrrrr ...
I added
fprintf(stderr, "Brasero libburn-plugin: Write type is SAO\n");
and
fprintf(stderr, "Brasero libburn-plugin: Write type is TAO\n");
but none of them show up in the terminal.
I doubt that i really installed my change.
What am i doing wrong ?
Have a nice day :)
Thomas
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
