GNU bug report logs - #28398
Xfburn

Previous Next

Package: guix-patches;

Reported by: ng0 <ng0 <at> infotropique.org>

Date: Sat, 9 Sep 2017 14:16:01 UTC

Severity: normal

Done: Christopher Baines <mail <at> cbaines.net>

Bug is archived. No further changes may be made.

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 28398 in the body.
You can then email your comments to 28398 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to guix-patches <at> gnu.org:
bug#28398; Package guix-patches. (Sat, 09 Sep 2017 14:16:01 GMT) Full text and rfc822 format available.

Acknowledgement sent to ng0 <ng0 <at> infotropique.org>:
New bug report received and forwarded. Copy sent to guix-patches <at> gnu.org. (Sat, 09 Sep 2017 14:16:01 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: ng0 <ng0 <at> infotropique.org>
To: guix-patches <at> gnu.org
Subject: Xfburn
Date: Sat, 9 Sep 2017 14:15:04 +0000
[Message part 1 (text/plain, inline)]
This adds Xfburn + 2 libburnia packages it depends on.

What I could not test was actually burning a disk,
as I can't afford to buy new optical disks at the moment.

It builds.
-- 
ng0
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://n0is.noblogs.org/my-keys
https://www.infotropique.org https://krosos.org
[0001-gnu-Add-libburn.patch (text/plain, attachment)]
[0002-gnu-Add-libisofs.patch (text/plain, attachment)]
[0003-gnu-Add-xfburn.patch (text/plain, attachment)]
[signature.asc (application/pgp-signature, inline)]

Information forwarded to guix-patches <at> gnu.org:
bug#28398; Package guix-patches. (Fri, 15 Sep 2017 11:43:01 GMT) Full text and rfc822 format available.

Message #8 received at 28398 <at> debbugs.gnu.org (full text, mbox):

From: ng0 <ng0 <at> infotropique.org>
To: 28398 <at> debbugs.gnu.org
Subject: Re: [bug#28398] Xfburn
Date: Fri, 15 Sep 2017 11:41:53 +0000
[Message part 1 (text/plain, inline)]
ng0 transcribed 8.5K bytes:
> This adds Xfburn + 2 libburnia packages it depends on.
> 
> What I could not test was actually burning a disk,
> as I can't afford to buy new optical disks at the moment.
> 
> It builds.

Update: I just found some disks, I could test functionality
this weekend.
-- 
ng0
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://krosos.org/dist/keys/
https://www.infotropique.org https://www.krosos.org
[signature.asc (application/pgp-signature, inline)]

Information forwarded to guix-patches <at> gnu.org:
bug#28398; Package guix-patches. (Sat, 30 Sep 2017 15:15:02 GMT) Full text and rfc822 format available.

Message #11 received at 28398 <at> debbugs.gnu.org (full text, mbox):

From: Christopher Baines <mail <at> cbaines.net>
To: ng0 <ng0 <at> infotropique.org>
Cc: 28398 <at> debbugs.gnu.org
Subject: Re: [bug#28398] Xfburn
Date: Sat, 30 Sep 2017 16:14:23 +0100
[Message part 1 (text/plain, inline)]
On Sat, 9 Sep 2017 14:15:04 +0000
ng0 <ng0 <at> infotropique.org> wrote:

> This adds Xfburn + 2 libburnia packages it depends on.
> 
> What I could not test was actually burning a disk,
> as I can't afford to buy new optical disks at the moment.
> 
> It builds.

It builds for me too :)

Looking at the libburn package.

> +    (synopsis "library for reading, mastering and writing optical
> discs")

guix lint says:

gnu/packages/cdrom.scm:717:14: libburn <at> 1.4.6: synopsis should start
with an upper-case letter or digit

> +    (description
> +     "libburn is the library by which preformatted data get onto optical media.
> +It uses either @file{/dev/sgN} (e.g. on kernel 2.4 with ide-scsi) or @file{/dev/srM}
> +or @file{/dev/hdX} (e.g. on kernel 2.6).  libburn is the foundation of the
> +libburnia-project cdrecord emulation.  Its code is independent of cdrecord.")

I'm unsure about the first sentence, "libburn is the library" makes it
sounds like there is only one library (this one) that does this. Would
something like "libburn is a library to write preformatted data to
optical media" work?

Also, I don't get the cdrecord reference at the end.

Looking at the libisofs package.

> +    (synopsis "library for reading, mastering and writing optical discs")

guix lint says:

gnu/packages/cdrom.scm:742:14: libisofs <at> 1.4.6: synopsis should start
with an upper-case letter or digit

Also, this is the same as the libburn package, which probably means
they need tweaking to be more useful.

> +    (description
> +     "libisofs is a library to create an ISO-9660 filesystem, supports extensions

I think this would read better split in to two sentences, as in "...
filesystem.  It supports"

> +like RockRidge or Joliet, and introduces an own extension AAIP.  It is a full

I think this would read better if you swap out "an" for "its".

> +featured ISO-9660 editor which composes and changes the directory tree of an
> +ISO image.  This tree and its newly imported data file contents get then

I think this would read better if you swap the order of "get" and
"then", as in "imported data file contents then get".

Looking finally at the xfburn package.

The description seems a bit odd to me, as things like blanking CDs, or
compositions are not terms I've heard commonly, but I think this is ok.

I had some broken icons when I tried running this, and got some
corresponding warnings, but this could be because I'm using Gnome and
not XFCE.

(xfburn:15797): Gtk-WARNING **: Error loading theme icon
'stock_xfburn-audio-cd' for stock: Icon 'stock_xfburn-audio-cd' not
present in theme


Thanks for the patches, and let me know if the proofreading the
descriptions is helpful?	
[Message part 2 (application/pgp-signature, inline)]

Information forwarded to guix-patches <at> gnu.org:
bug#28398; Package guix-patches. (Sat, 30 Sep 2017 15:34:01 GMT) Full text and rfc822 format available.

Message #14 received at 28398 <at> debbugs.gnu.org (full text, mbox):

From: ng0 <ng0 <at> infotropique.org>
To: Christopher Baines <mail <at> cbaines.net>
Cc: 28398 <at> debbugs.gnu.org, ng0 <ng0 <at> infotropique.org>
Subject: Re: [bug#28398] Xfburn
Date: Sat, 30 Sep 2017 15:33:05 +0000
[Message part 1 (text/plain, inline)]
Christopher Baines transcribed 3.8K bytes:
> On Sat, 9 Sep 2017 14:15:04 +0000
> ng0 <ng0 <at> infotropique.org> wrote:
> 
> > This adds Xfburn + 2 libburnia packages it depends on.
> > 
> > What I could not test was actually burning a disk,
> > as I can't afford to buy new optical disks at the moment.
> > 
> > It builds.
> 
> It builds for me too :)
> 
> Looking at the libburn package.
> 
> > +    (synopsis "library for reading, mastering and writing optical
> > discs")
> 
> guix lint says:
> 
> gnu/packages/cdrom.scm:717:14: libburn <at> 1.4.6: synopsis should start
> with an upper-case letter or digit

Ok.

> > +    (description
> > +     "libburn is the library by which preformatted data get onto optical media.
> > +It uses either @file{/dev/sgN} (e.g. on kernel 2.4 with ide-scsi) or @file{/dev/srM}
> > +or @file{/dev/hdX} (e.g. on kernel 2.6).  libburn is the foundation of the
> > +libburnia-project cdrecord emulation.  Its code is independent of cdrecord.")
> 
> I'm unsure about the first sentence, "libburn is the library" makes it
> sounds like there is only one library (this one) that does this. Would
> something like "libburn is a library to write preformatted data to
> optical media" work?
> 
> Also, I don't get the cdrecord reference at the end.

Tbh I took this 1:1 from upstream. They don't really provide a good insight into
what's what as far as I remember.

> Looking at the libisofs package.
> 
> > +    (synopsis "library for reading, mastering and writing optical discs")
> 
> guix lint says:
> 
> gnu/packages/cdrom.scm:742:14: libisofs <at> 1.4.6: synopsis should start
> with an upper-case letter or digit
> 
> Also, this is the same as the libburn package, which probably means
> they need tweaking to be more useful.
> 
> > +    (description
> > +     "libisofs is a library to create an ISO-9660 filesystem, supports extensions
> 
> I think this would read better split in to two sentences, as in "...
> filesystem.  It supports"
> 
> > +like RockRidge or Joliet, and introduces an own extension AAIP.  It is a full
> 
> I think this would read better if you swap out "an" for "its".
> 
> > +featured ISO-9660 editor which composes and changes the directory tree of an
> > +ISO image.  This tree and its newly imported data file contents get then
> 
> I think this would read better if you swap the order of "get" and
> "then", as in "imported data file contents then get".
> 
> Looking finally at the xfburn package.
> 
> The description seems a bit odd to me, as things like blanking CDs, or
> compositions are not terms I've heard commonly, but I think this is ok.
> 
> I had some broken icons when I tried running this, and got some
> corresponding warnings, but this could be because I'm using Gnome and
> not XFCE.
> 
> (xfburn:15797): Gtk-WARNING **: Error loading theme icon
> 'stock_xfburn-audio-cd' for stock: Icon 'stock_xfburn-audio-cd' not
> present in theme

Not a blocking issue (the icons) but Xfburn is not limited to Xfce,
so we should figure out which icon-set is needed.

> 
> Thanks for the patches, and let me know if the proofreading the
> descriptions is helpful?	

Well I still don't know more about burning disk application interiors.
Can you come up with better descriptions?
It is hard for me to take https://dev.lovelyhq.com/libburnia/web/wikis/home
and the descriptions linked in there and to decide what is useful.
-- 
ng0
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://krosos.org/dist/keys/
https://www.infotropique.org https://krosos.org
[signature.asc (application/pgp-signature, inline)]

Information forwarded to guix-patches <at> gnu.org:
bug#28398; Package guix-patches. (Sat, 30 Sep 2017 17:34:02 GMT) Full text and rfc822 format available.

Message #17 received at 28398 <at> debbugs.gnu.org (full text, mbox):

From: Christopher Baines <mail <at> cbaines.net>
To: ng0 <ng0 <at> infotropique.org>
Cc: 28398 <at> debbugs.gnu.org
Subject: Re: [bug#28398] Xfburn
Date: Sat, 30 Sep 2017 18:33:35 +0100
[Message part 1 (text/plain, inline)]
On Sat, 30 Sep 2017 15:33:05 +0000
ng0 <ng0 <at> infotropique.org> wrote:

> Christopher Baines transcribed 3.8K bytes:
> > On Sat, 9 Sep 2017 14:15:04 +0000
> > ng0 <ng0 <at> infotropique.org> wrote:
> >   
> > Looking at the libburn package.
> >   
> > > +    (synopsis "library for reading, mastering and writing optical
> > > discs")

I think this description better fits libburnia, rather than the
specific libburn library.

Maybe something like this would be more specific:
  "The libburn library is used to write preformatted data to optical
  media"

> > > +    (description
> > > +     "libburn is the library by which preformatted data get onto
> > > optical media. +It uses either @file{/dev/sgN} (e.g. on kernel
> > > 2.4 with ide-scsi) or @file{/dev/srM} +or @file{/dev/hdX} (e.g.
> > > on kernel 2.6).  libburn is the foundation of the
> > > +libburnia-project cdrecord emulation.  Its code is independent
> > > of cdrecord.")  
> > 
> > I'm unsure about the first sentence, "libburn is the library" makes
> > it sounds like there is only one library (this one) that does this.
> > Would something like "libburn is a library to write preformatted
> > data to optical media" work?
> > 
> > Also, I don't get the cdrecord reference at the end.  
> 
> Tbh I took this 1:1 from upstream. They don't really provide a good
> insight into what's what as far as I remember.

For the description, how about:

libburn is a C library for writing to optical media, and has support
for multiple different types of media (e.g. CD, DVD and BR).

Included is the @command{cdrskin} command to burn data to CD or DVD.
@command{cdrskin} emulates the behaviour of the @{cdrecord} command,
but using the libburn library.

> > Looking at the libisofs package.
> >   
> > > +    (synopsis "library for reading, mastering and writing
> > > optical discs")  
> > 
> > guix lint says:
> > 
> > gnu/packages/cdrom.scm:742:14: libisofs <at> 1.4.6: synopsis should start
> > with an upper-case letter or digit
> > 
> > Also, this is the same as the libburn package, which probably means
> > they need tweaking to be more useful.

For the libisofs synopsis, how about:

Library for creating ISO 9660 filesystem images

> > > +    (description
> > > +     "libisofs is a library to create an ISO-9660 filesystem,
> > > supports extensions  
> > 
> > I think this would read better split in to two sentences, as in "...
> > filesystem.  It supports"
> >   
> > > +like RockRidge or Joliet, and introduces an own extension AAIP.
> > > It is a full  
> > 
> > I think this would read better if you swap out "an" for "its".
> >   
> > > +featured ISO-9660 editor which composes and changes the
> > > directory tree of an +ISO image.  This tree and its newly
> > > imported data file contents get then  
> > 
> > I think this would read better if you swap the order of "get" and
> > "then", as in "imported data file contents then get".
> > 
> > Looking finally at the xfburn package.
> > 
> > The description seems a bit odd to me, as things like blanking CDs,
> > or compositions are not terms I've heard commonly, but I think this
> > is ok.
> > 
> > I had some broken icons when I tried running this, and got some
> > corresponding warnings, but this could be because I'm using Gnome
> > and not XFCE.
> > 
> > (xfburn:15797): Gtk-WARNING **: Error loading theme icon
> > 'stock_xfburn-audio-cd' for stock: Icon 'stock_xfburn-audio-cd' not
> > present in theme  
> 
> Not a blocking issue (the icons) but Xfburn is not limited to Xfce,
> so we should figure out which icon-set is needed.

I agree.

> > Thanks for the patches, and let me know if the proofreading the
> > descriptions is helpful?	  
> 
> Well I still don't know more about burning disk application interiors.
> Can you come up with better descriptions?
> It is hard for me to take
> https://dev.lovelyhq.com/libburnia/web/wikis/home and the
> descriptions linked in there and to decide what is useful.

Most of the comments I made were about the use of English. I've now
written some suggestions above where I commented on the content.
[Message part 2 (application/pgp-signature, inline)]

Information forwarded to guix-patches <at> gnu.org:
bug#28398; Package guix-patches. (Sun, 01 Oct 2017 16:38:01 GMT) Full text and rfc822 format available.

Message #20 received at 28398 <at> debbugs.gnu.org (full text, mbox):

From: "Thomas Schmitt" <scdbackup <at> gmx.net>
To: 28398 <at> debbugs.gnu.org
Cc: mail <at> cbaines.net, ng0 <at> infotropique.org
Subject: Re: [bug#28398] Xfburn
Date: Sun, 01 Oct 2017 10:34:23 +0200
Hi,

i'm the current developer of libburn and libisof.
Please Cc me with replies.

Be invited to re-use the descriptions of the Debian packages:

 Package: libburn4
 Description: library to provide CD/DVD writing functions
  libburn is a library for reading, mastering and writing optical discs.
  Supported media are: CD-R, CD-RW, DVD-RAM, DVD+RW, DVD+R, DVD+R/DL,
  DVD-RW, DVD-R, DVD-R/DL, BD-R, BD-RE.

 Package: libisofs6
 Description: library to create ISO 9660 images
  libisofs creates ISO 9660 (aka ECMA-119) filesystem images which can either
  be written to POSIX file objects or handed over to libburn for being written
  directly to optical media.
  It can read metadata of ISO 9660 filesystems, manipulate them, and use them
  to produce new complete filesystem images or add-on images to be appended
  to the read filesystem image.
  Supported extensions to ISO 9660 are Rock Ridge, Joliet, AAIP, zisofs.

Well, the synopsis of libburn could need a "/BD" added to "CD/DVD".

The current cdrskin description of Debian is too technical and too historical.
I will change it to:

 Package: cdrskin
 Description: command line CD/DVD/BD writing tool
  cdrskin strives to be a second source for the services traditionally
  provided by cdrecord. It writes data sessions to CD, DVD, or BD media.
  To CD media it may also write audio sessions.
  Multi-session is possible on all media types except DVD-R DL and
  fastly blanked DVD-RW.
  .
  This is a burner-only application. If you want a burner and ISO 9660 image
  manipulation application, please install the xorriso package.


ng0 wrote:
> Tbh I took this 1:1 from upstream. They don't really provide a good
> insight into what's what as far as I remember.

Hrm, yes, the wiki pages are too verbous for the purpose of a package
description.


> It is hard for me to take https://dev.lovelyhq.com/libburnia/web/wikis/home
> and the descriptions linked in there and to decide what is useful.

Just ask your friendly upstream. :))


Christopher Baines wrote:
> I don't get the cdrecord reference at the end.

It's historic. 10 years ago, the world was full of cdrecord forks.
The author of cdrecord accused the forkers of stealing his work.
cdrskin is not a fork but rather an emulation. I stole only the
option names and their help text lines.


Have a nice day :)

Thomas





Information forwarded to guix-patches <at> gnu.org:
bug#28398; Package guix-patches. (Sun, 01 Oct 2017 16:38:02 GMT) Full text and rfc822 format available.

Message #23 received at 28398 <at> debbugs.gnu.org (full text, mbox):

From: "Thomas Schmitt" <scdbackup <at> gmx.net>
To: 28398 <at> debbugs.gnu.org
Cc: mail <at> cbaines.net, ng0 <at> infotropique.org
Subject: Re: [bug#28398] Xfburn
Date: Sun, 01 Oct 2017 12:20:39 +0200
Hi,

ng0 wrote:
> > (synopsis "library for reading, mastering and writing optical discs)

Christopher Baines wrote:
> I think this description better fits libburnia, rather than the
> specific libburn library.

Indeed "mastering" is inappropriate. libisofs masters images.
I will change the Debian description to

 Description: library to provide CD/DVD/BD writing functions
- libburn is a library for reading, mastering and writing optical discs.
+ libburn is a library for reading and writing optical discs.


Have a nice day :)

Thomas





Information forwarded to guix-patches <at> gnu.org:
bug#28398; Package guix-patches. (Wed, 29 Nov 2017 09:15:02 GMT) Full text and rfc822 format available.

Message #26 received at 28398 <at> debbugs.gnu.org (full text, mbox):

From: ng0 <ng0 <at> n0.is>
To: Thomas Schmitt <scdbackup <at> gmx.net>
Cc: 28398 <at> debbugs.gnu.org, mail <at> cbaines.net, ng0 <at> n0.is
Subject: Re: [bug#28398] Xfburn
Date: Wed, 29 Nov 2017 09:14:21 +0000
[Message part 1 (text/plain, inline)]
Hi Thomas,

sorry for the delayed answer. I've applied your suggestions
and the ones Christopher had a while back in this new version
of the patches.

Thanks again for you input.

Thomas Schmitt transcribed 0.5K bytes:
> Hi,
> 
> ng0 wrote:
> > > (synopsis "library for reading, mastering and writing optical discs)
> 
> Christopher Baines wrote:
> > I think this description better fits libburnia, rather than the
> > specific libburn library.
> 
> Indeed "mastering" is inappropriate. libisofs masters images.
> I will change the Debian description to
> 
>  Description: library to provide CD/DVD/BD writing functions
> - libburn is a library for reading, mastering and writing optical discs.
> + libburn is a library for reading and writing optical discs.
> 
> 
> Have a nice day :)
> 
> Thomas
> 
> 

-- 
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://c.n0.is/ng0_pubkeys/tree/keys
  WWW: https://n0.is
[0001-gnu-Add-libburn.patch (text/plain, attachment)]
[0002-gnu-Add-libisofs.patch (text/plain, attachment)]
[0003-gnu-Add-xfburn.patch (text/plain, attachment)]
[signature.asc (application/pgp-signature, inline)]

Information forwarded to guix-patches <at> gnu.org:
bug#28398; Package guix-patches. (Wed, 29 Nov 2017 11:41:01 GMT) Full text and rfc822 format available.

Message #29 received at 28398 <at> debbugs.gnu.org (full text, mbox):

From: "Thomas Schmitt" <scdbackup <at> gmx.net>
To: ng0 <at> n0.is
Cc: 28398 <at> debbugs.gnu.org, mail <at> cbaines.net
Subject: Re: [bug#28398] Xfburn
Date: Wed, 29 Nov 2017 12:40:43 +0100
Hi,

ng0 wrote:
> I've applied your suggestions
> and the ones Christopher had a while back in this new version
> of the patches.

The inappropriate word "mastering" is still in one of the two description
texts in the libburn patch

> +    (synopsis "Library for reading and writing optical discs")
> +    (description
> +     "Libburn is a library for reading, mastering and writing optical discs.


(It is also still in the description of the current Debian package. But
 that's only due to the long release cycle. The next Debian package will
 state what is committed by
   https://anonscm.debian.org/viewvc/pkg-libburnia/trunk/libburn/debian/control?r1=428&r2=430
)

------------------------------------------------------------------------

With Xfburn, consider to mention BD (Blu-ray) media additionally to CD and
DVD media. 

> +    (synopsis "GTK+ based CD and DVD burning application")
> +    (description
> +     "Xfburn is a simple CD/DVD burning tool based on libburnia
> +libraries.  It can blank CD/DVD(-RW)s, burn and create iso images,
> +audio CDs, as well as burn personal compositions of data to either
> +CD or DVD.")

I can confirm that "xfburn version 0.5.2 for Xfce 4.10" recognizes and
burns single layer BD-RE and BD-R media. Users of libburn report success
with multi-layer BD-RE and BD-R media.

------------------------------------------------------------------------

Did we already talk about these lines in the libburn patch ?

> +     `(#:configure-flags (list "--enable-libcdio")))
> +    (inputs
> +     `(("libcdio" ,libcdio)))

If they shall by default let libburn use the SCSI transport mechanism of
libcdio, then better don't do this.

Without wanting to badmouth libcdio, it turned out that its SCSI/MMC layer
is needy of modernization and that it does not provide usable SCSI transport
on operating systems which libburn cannot handle by its own system adapters.
libburn has SCSI-capable adapters for Linux The Kernel, FreeBSD, Solaris,
NetBSD, OpenBSD.

In Hurd/Mach The Kernel we have no SCSI transport facility from userland to
optical drives, i fear. There, libburn can only operate on data files and
read-write block devices. Useful mainly as foundation for xorriso to make
ISO 9660 filesystem images.

The shortcommings of libcdio towards libburn's sg-linux.c adapter are mainly
with receiving SCSI error conditions (aka Sense Data) from the drive and
forwarding them to libburn.

So my advise is not to configure libburn with --enable-libcdio and not to
declare libcdio a dependency of libburn.

------------------------------------------------------------------------

I also looked at the libisofs related patch:

> +    (inputs
> +     `(("zlib" ,zlib)))

If ./configure sees libacl and libattr on GNU/Linux, then libisofs will link
to it and enable recording of ACL and extended file attributes.

Looking for "acl" in Guix, i found
  https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/acl.scm?id=v0.13.0-5000-gd2bdee8a6#n33
which looks like what Debian packages as "libacl1" and is used by Debian's
libisofs package.

So consider to add for libisofs
      ("acl" ,acl)

----------------------------------------------------------------------------

GNU xorriso versus libisoburn's xorriso:

The only known application of libisofs' ACL capabilities is xorriso. It can
record ACLs as part of backups and restore them back to disk. Operating
systems are supposed to ignore the ACL info when mounting and reading
libisofs made filesystems.

Guix currently packages GNU xorriso, which brings own source copies of
libburn, libisofs, libisoburn, and libjte.

When libburn and libisofs are established as Guix packages and the decision
is made that Debian's Jigdo ISO download mechanism is not desired, one should
consider to package libisoburn and to install its dynamically linked xorriso
binary.

The source code and functionality of both xorrisos is the same, except that
Guix offers no libjte for Debian's Jigdo format. Both are maintained by me.
libisoburn is GPLv2+, but by using libreadline it will become GPLv3+.
GNU xorriso is always GPLv3+.

Reason for the existence of GNU xorriso is mainly that it can be compiled
and installed by a normal user without interfering with system-wide installed
libburn and libisofs. This provides freedom from distro decisions and delays.

Guix's xorriso package has at
  https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/cdrom.scm?id=v0.13.0-2323-g35131babc#n148
>     (inputs
>      `(("acl" ,acl)
>        ("readline" ,readline)
>        ("bzip2" ,bzip2)
>        ("zlib" ,zlib)
>        ("libcdio" ,libcdio)))

The use of "bzip2" seems wrong. libjte optionally uses libbz2 which i don't
find in Guix. "bzip2" does not promise the library but rather the standalone
binary.

The use of "libcdio" would have the disadvantage described above. But
it seems that it is not enabled at configure time of GNU xorriso.
So one should remove it from the xorriso input list, too. 

------------------------------------------------------------------------

Whew. I did not plan to write such a long mail.


Have a nice day :)

Thomas





Information forwarded to guix-patches <at> gnu.org:
bug#28398; Package guix-patches. (Wed, 29 Nov 2017 14:38:02 GMT) Full text and rfc822 format available.

Message #32 received at 28398 <at> debbugs.gnu.org (full text, mbox):

From: ng0 <ng0 <at> n0.is>
To: Thomas Schmitt <scdbackup <at> gmx.net>
Cc: 28398 <at> debbugs.gnu.org, mail <at> cbaines.net, ng0 <at> n0.is
Subject: Re: [bug#28398] Xfburn
Date: Wed, 29 Nov 2017 14:37:23 +0000
[Message part 1 (text/plain, inline)]
Hi,

Many thanks for the in-depth review and hints! I don't
have the time for immediate questions or patching, so
I'll followup later. I just wanted to express my thanks.

Thomas Schmitt transcribed 5.0K bytes:
> Hi,
> 
> ng0 wrote:
> > I've applied your suggestions
> > and the ones Christopher had a while back in this new version
> > of the patches.
> 
> The inappropriate word "mastering" is still in one of the two description
> texts in the libburn patch
> 
> > +    (synopsis "Library for reading and writing optical discs")
> > +    (description
> > +     "Libburn is a library for reading, mastering and writing optical discs.
> 
> 
> (It is also still in the description of the current Debian package. But
>  that's only due to the long release cycle. The next Debian package will
>  state what is committed by
>    https://anonscm.debian.org/viewvc/pkg-libburnia/trunk/libburn/debian/control?r1=428&r2=430
> )
> 
> ------------------------------------------------------------------------
> 
> With Xfburn, consider to mention BD (Blu-ray) media additionally to CD and
> DVD media. 
> 
> > +    (synopsis "GTK+ based CD and DVD burning application")
> > +    (description
> > +     "Xfburn is a simple CD/DVD burning tool based on libburnia
> > +libraries.  It can blank CD/DVD(-RW)s, burn and create iso images,
> > +audio CDs, as well as burn personal compositions of data to either
> > +CD or DVD.")
> 
> I can confirm that "xfburn version 0.5.2 for Xfce 4.10" recognizes and
> burns single layer BD-RE and BD-R media. Users of libburn report success
> with multi-layer BD-RE and BD-R media.
> 
> ------------------------------------------------------------------------
> 
> Did we already talk about these lines in the libburn patch ?
> 
> > +     `(#:configure-flags (list "--enable-libcdio")))
> > +    (inputs
> > +     `(("libcdio" ,libcdio)))
> 
> If they shall by default let libburn use the SCSI transport mechanism of
> libcdio, then better don't do this.
> 
> Without wanting to badmouth libcdio, it turned out that its SCSI/MMC layer
> is needy of modernization and that it does not provide usable SCSI transport
> on operating systems which libburn cannot handle by its own system adapters.
> libburn has SCSI-capable adapters for Linux The Kernel, FreeBSD, Solaris,
> NetBSD, OpenBSD.
> 
> In Hurd/Mach The Kernel we have no SCSI transport facility from userland to
> optical drives, i fear. There, libburn can only operate on data files and
> read-write block devices. Useful mainly as foundation for xorriso to make
> ISO 9660 filesystem images.
> 
> The shortcommings of libcdio towards libburn's sg-linux.c adapter are mainly
> with receiving SCSI error conditions (aka Sense Data) from the drive and
> forwarding them to libburn.
> 
> So my advise is not to configure libburn with --enable-libcdio and not to
> declare libcdio a dependency of libburn.
> 
> ------------------------------------------------------------------------
> 
> I also looked at the libisofs related patch:
> 
> > +    (inputs
> > +     `(("zlib" ,zlib)))
> 
> If ./configure sees libacl and libattr on GNU/Linux, then libisofs will link
> to it and enable recording of ACL and extended file attributes.
> 
> Looking for "acl" in Guix, i found
>   https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/acl.scm?id=v0.13.0-5000-gd2bdee8a6#n33
> which looks like what Debian packages as "libacl1" and is used by Debian's
> libisofs package.
> 
> So consider to add for libisofs
>       ("acl" ,acl)
> 
> ----------------------------------------------------------------------------
> 
> GNU xorriso versus libisoburn's xorriso:
> 
> The only known application of libisofs' ACL capabilities is xorriso. It can
> record ACLs as part of backups and restore them back to disk. Operating
> systems are supposed to ignore the ACL info when mounting and reading
> libisofs made filesystems.
> 
> Guix currently packages GNU xorriso, which brings own source copies of
> libburn, libisofs, libisoburn, and libjte.
> 
> When libburn and libisofs are established as Guix packages and the decision
> is made that Debian's Jigdo ISO download mechanism is not desired, one should
> consider to package libisoburn and to install its dynamically linked xorriso
> binary.
> 
> The source code and functionality of both xorrisos is the same, except that
> Guix offers no libjte for Debian's Jigdo format. Both are maintained by me.
> libisoburn is GPLv2+, but by using libreadline it will become GPLv3+.
> GNU xorriso is always GPLv3+.
> 
> Reason for the existence of GNU xorriso is mainly that it can be compiled
> and installed by a normal user without interfering with system-wide installed
> libburn and libisofs. This provides freedom from distro decisions and delays.
> 
> Guix's xorriso package has at
>   https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/cdrom.scm?id=v0.13.0-2323-g35131babc#n148
> >     (inputs
> >      `(("acl" ,acl)
> >        ("readline" ,readline)
> >        ("bzip2" ,bzip2)
> >        ("zlib" ,zlib)
> >        ("libcdio" ,libcdio)))
> 
> The use of "bzip2" seems wrong. libjte optionally uses libbz2 which i don't
> find in Guix. "bzip2" does not promise the library but rather the standalone
> binary.
> 
> The use of "libcdio" would have the disadvantage described above. But
> it seems that it is not enabled at configure time of GNU xorriso.
> So one should remove it from the xorriso input list, too. 
> 
> ------------------------------------------------------------------------
> 
> Whew. I did not plan to write such a long mail.
> 
> 
> Have a nice day :)
> 
> Thomas
> 
> 

-- 
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://c.n0.is/ng0_pubkeys/tree/keys
  WWW: https://n0.is
[signature.asc (application/pgp-signature, inline)]

Information forwarded to guix-patches <at> gnu.org:
bug#28398; Package guix-patches. (Fri, 01 Dec 2017 14:14:02 GMT) Full text and rfc822 format available.

Message #35 received at 28398 <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: "Thomas Schmitt" <scdbackup <at> gmx.net>
Cc: 28398 <at> debbugs.gnu.org, ng0 <at> n0.is
Subject: Re: [bug#28398] Xfburn
Date: Fri, 01 Dec 2017 15:13:21 +0100
Hi Thomas,

"Thomas Schmitt" <scdbackup <at> gmx.net> skribis:

> ng0 wrote:
>> I've applied your suggestions
>> and the ones Christopher had a while back in this new version
>> of the patches.
>
> The inappropriate word "mastering" is still in one of the two description
> texts in the libburn patch
>
>> +    (synopsis "Library for reading and writing optical discs")
>> +    (description
>> +     "Libburn is a library for reading, mastering and writing optical discs.
>
>
> (It is also still in the description of the current Debian package. But
>  that's only due to the long release cycle. The next Debian package will
>  state what is committed by
>    https://anonscm.debian.org/viewvc/pkg-libburnia/trunk/libburn/debian/control?r1=428&r2=430
> )

For the record, for GNU packages we stick to the GNU description as
maintained in the Womb and ‘guix lint’ makes sure we do:

  http://cvs.savannah.gnu.org/viewvc/*checkout*/womb/gnumaint/pkgblurbs.txt

However in this case our Xorriso description seems to differ.  Are you
OK with the one in pkgblurbs.txt above?  If not, can you provide a
suggestion?

> GNU xorriso versus libisoburn's xorriso:
>
> The only known application of libisofs' ACL capabilities is xorriso. It can
> record ACLs as part of backups and restore them back to disk. Operating
> systems are supposed to ignore the ACL info when mounting and reading
> libisofs made filesystems.
>
> Guix currently packages GNU xorriso, which brings own source copies of
> libburn, libisofs, libisoburn, and libjte.
>
> When libburn and libisofs are established as Guix packages and the decision
> is made that Debian's Jigdo ISO download mechanism is not desired, one should
> consider to package libisoburn and to install its dynamically linked xorriso
> binary.

Indeed, we should do that.

> Reason for the existence of GNU xorriso is mainly that it can be compiled
> and installed by a normal user without interfering with system-wide installed
> libburn and libisofs. This provides freedom from distro decisions and delays.

As package maintainers our choice is to *not* use bundled software in
such cases, though.  Is it the only difference between the two xorrisos?

Thanks for your feedback, it’s useful guidance!

Ludo’.




Information forwarded to guix-patches <at> gnu.org:
bug#28398; Package guix-patches. (Fri, 01 Dec 2017 16:07:01 GMT) Full text and rfc822 format available.

Message #38 received at 28398 <at> debbugs.gnu.org (full text, mbox):

From: "Thomas Schmitt" <scdbackup <at> gmx.net>
To: ng0 <at> n0.is
Cc: 28398 <at> debbugs.gnu.org, ng0 <at> n0.is
Subject: Re: [bug#28398] Xfburn
Date: Fri, 01 Dec 2017 17:06:08 +0100
Hi,

Ludovic Courtès wrote:
> http://cvs.savannah.gnu.org/viewvc/*checkout*/womb/gnumaint/pkgblurbs.txt
> However in this case our Xorriso description seems to differ.
> Are you OK with the one in pkgblurbs.txt above?

I'm not sure whether the last sentence could be misleading:
  "xorriso can then be used to copy files directly into or out of ISO files."

"ISO files" should be "ISO filesystems", in any case.

"copy files directly into" might suggest usual read-write capabilities.
But as mentioned by "session-wise manipulation", the write capability is
not the usual one.

It works like this:
- The directory tree and metadata of an ISO filesystem get loaded into
  the object model of libisofs,
- libisofs applies manipulations to this model,
- finally a new directory tree based on the model gets written to the
  medium, together with any new data file content.
Old directory trees and the data file content of outdated files stays
unchanged. Only the superblock of the filesystem will get overwritten,
if the medium is overwritable. On non-overwritable media, the Linux kernel
will look for a superblock in the first track of the last recorded session.

To get an idea how sessions are arranged on a BD-R medium, see
  https://screenshots.debian.net/package/xorriso
On GNU/Linux, mount option -o sbsector= can mount any of the 10 sessions
to show the ~4 GB backup state of the day when the session was made.
Although the add-on sessions only introduced content of changed data files,
they still impose substantial overhead by each having a tree of 60,000+
file names. (But hey, it's already worth 40 GB of backup and will take
about 200 more daily sessions.)


> As package maintainers our choice is to *not* use bundled software in
> such cases, though.  Is it the only difference between the two xorrisos?

Feature- and bug-wise: yes.
There is the built-in copy of libjte in GNU xorriso, which one would have
to offer libisoburn at configure-, build-, and run-time, in order to get
the same capability of creating Debian .jigdo and .template files.
See also  https://www.debian.org/CD/jigdo-cd/

Name-wise there are problems with some from-source distros which have
a 1:1 relationship between source package and installed set of binaries.
They are unable to offer a package named "xorriso" but only its upstream
package "libisoburn".
(I could have changed this by splitting up the three upstream tarballs
 into six, some years ago. But i did not like the idea much and my then
 Debian Developer hated it thoroughly. Meanwhile it would cause work in
 too many distros.)
Afaik, the FreeBSD port of libisoburn is named "xorriso".
Archlinux has a "Provides:" header where its "libisoburn" package
advertises "xorriso, xorriso-tcltk".

Any difference results from automatic creation of GNU xorriso from the
library sources by
  https://dev.lovelyhq.com/libburnia/libisoburn/raw/master/xorriso/make_xorriso_standalone.sh
It makes changes about:
- Build system files: bootstrap, configure.ac, Makefile.am, version.h.in
- Documentation files: CONTRIBUTORS, README, COPYRIGHT, COPYING, AUTHORS
- Program id message and license statement control macro in xorriso/xorriso.h


Have a nice day :)

Thomas





Information forwarded to guix-patches <at> gnu.org:
bug#28398; Package guix-patches. (Mon, 04 Dec 2017 14:07:01 GMT) Full text and rfc822 format available.

Message #41 received at 28398 <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: "Thomas Schmitt" <scdbackup <at> gmx.net>
Cc: 28398 <at> debbugs.gnu.org, ng0 <at> n0.is
Subject: Re: [bug#28398] Xfburn
Date: Mon, 04 Dec 2017 15:06:37 +0100
"Thomas Schmitt" <scdbackup <at> gmx.net> skribis:

> Ludovic Courtès wrote:
>> http://cvs.savannah.gnu.org/viewvc/*checkout*/womb/gnumaint/pkgblurbs.txt
>> However in this case our Xorriso description seems to differ.
>> Are you OK with the one in pkgblurbs.txt above?
>
> I'm not sure whether the last sentence could be misleading:
>   "xorriso can then be used to copy files directly into or out of ISO files."
>
> "ISO files" should be "ISO filesystems", in any case.

Indeed, fixed.

[...]

>> As package maintainers our choice is to *not* use bundled software in
>> such cases, though.  Is it the only difference between the two xorrisos?
>
> Feature- and bug-wise: yes.
> There is the built-in copy of libjte in GNU xorriso, which one would have
> to offer libisoburn at configure-, build-, and run-time, in order to get
> the same capability of creating Debian .jigdo and .template files.
> See also  https://www.debian.org/CD/jigdo-cd/
>
> Name-wise there are problems with some from-source distros which have
> a 1:1 relationship between source package and installed set of binaries.
> They are unable to offer a package named "xorriso" but only its upstream
> package "libisoburn".
> (I could have changed this by splitting up the three upstream tarballs
>  into six, some years ago. But i did not like the idea much and my then
>  Debian Developer hated it thoroughly. Meanwhile it would cause work in
>  too many distros.)
> Afaik, the FreeBSD port of libisoburn is named "xorriso".
> Archlinux has a "Provides:" header where its "libisoburn" package
> advertises "xorriso, xorriso-tcltk".
>
> Any difference results from automatic creation of GNU xorriso from the
> library sources by
>   https://dev.lovelyhq.com/libburnia/libisoburn/raw/master/xorriso/make_xorriso_standalone.sh
> It makes changes about:
> - Build system files: bootstrap, configure.ac, Makefile.am, version.h.in
> - Documentation files: CONTRIBUTORS, README, COPYRIGHT, COPYING, AUTHORS
> - Program id message and license statement control macro in xorriso/xorriso.h

I see.

Thanks for explaining!

Ludo’.




Information forwarded to guix-patches <at> gnu.org:
bug#28398; Package guix-patches. (Mon, 11 Dec 2017 10:00:02 GMT) Full text and rfc822 format available.

Message #44 received at 28398 <at> debbugs.gnu.org (full text, mbox):

From: ng0 <ng0 <at> n0.is>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 28398 <at> debbugs.gnu.org, ng0 <at> n0.is, Thomas Schmitt <scdbackup <at> gmx.net>
Subject: Re: [bug#28398] Xfburn
Date: Mon, 11 Dec 2017 09:58:37 +0000
[Message part 1 (text/plain, inline)]
Alright, here's the next revision. I've included a new patch to
work in your comments on xorriso (dropping the 2 inputs).

The compiled Xfburn gives me 2 error messages so far:
1. No Drive found (thanks Cpt. Obvious, I have no optical drive here).
2. More concerning:
   Failed to initialize gstreamer transcoder: An error occurred setting gstreamer up for transcoding
   (falling back to basic implementation)

Keep in mind that I've tested this from within guile-wm, so
this might be different in XFCE or other environments. I'll
test this later today. I expect XFCE to work in MATE at the
very least, but XFCE-only would be good for starters.

The application itself starts.

Session output on terminal can not be copied right now, I'll
send it in later today if necessary.

Ludovic Courtès transcribed 2.1K bytes:
> "Thomas Schmitt" <scdbackup <at> gmx.net> skribis:
> 
> > Ludovic Courtès wrote:
> >> http://cvs.savannah.gnu.org/viewvc/*checkout*/womb/gnumaint/pkgblurbs.txt
> >> However in this case our Xorriso description seems to differ.
> >> Are you OK with the one in pkgblurbs.txt above?
> >
> > I'm not sure whether the last sentence could be misleading:
> >   "xorriso can then be used to copy files directly into or out of ISO files."
> >
> > "ISO files" should be "ISO filesystems", in any case.
> 
> Indeed, fixed.
> 
> [...]
> 
> >> As package maintainers our choice is to *not* use bundled software in
> >> such cases, though.  Is it the only difference between the two xorrisos?
> >
> > Feature- and bug-wise: yes.
> > There is the built-in copy of libjte in GNU xorriso, which one would have
> > to offer libisoburn at configure-, build-, and run-time, in order to get
> > the same capability of creating Debian .jigdo and .template files.
> > See also  https://www.debian.org/CD/jigdo-cd/
> >
> > Name-wise there are problems with some from-source distros which have
> > a 1:1 relationship between source package and installed set of binaries.
> > They are unable to offer a package named "xorriso" but only its upstream
> > package "libisoburn".
> > (I could have changed this by splitting up the three upstream tarballs
> >  into six, some years ago. But i did not like the idea much and my then
> >  Debian Developer hated it thoroughly. Meanwhile it would cause work in
> >  too many distros.)
> > Afaik, the FreeBSD port of libisoburn is named "xorriso".
> > Archlinux has a "Provides:" header where its "libisoburn" package
> > advertises "xorriso, xorriso-tcltk".
> >
> > Any difference results from automatic creation of GNU xorriso from the
> > library sources by
> >   https://dev.lovelyhq.com/libburnia/libisoburn/raw/master/xorriso/make_xorriso_standalone.sh
> > It makes changes about:
> > - Build system files: bootstrap, configure.ac, Makefile.am, version.h.in
> > - Documentation files: CONTRIBUTORS, README, COPYRIGHT, COPYING, AUTHORS
> > - Program id message and license statement control macro in xorriso/xorriso.h
> 
> I see.
> 
> Thanks for explaining!
> 
> Ludo’.
> 

-- 
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://c.n0.is/ng0_pubkeys/tree/keys
  WWW: https://n0.is
[0001-gnu-Add-libburn.patch (text/plain, attachment)]
[0002-gnu-Add-libisofs.patch (text/plain, attachment)]
[0003-gnu-Add-xfburn.patch (text/plain, attachment)]
[0004-gnu-xorriso-Remove-bzip2-and-libcdio-from-inputs.patch (text/plain, attachment)]
[signature.asc (application/pgp-signature, inline)]

Information forwarded to guix-patches <at> gnu.org:
bug#28398; Package guix-patches. (Mon, 11 Dec 2017 11:03:01 GMT) Full text and rfc822 format available.

Message #47 received at 28398 <at> debbugs.gnu.org (full text, mbox):

From: "Thomas Schmitt" <scdbackup <at> gmx.net>
To: ng0 <at> n0.is
Cc: 28398 <at> debbugs.gnu.org, ludo <at> gnu.org
Subject: Re: [bug#28398] Xfburn
Date: Mon, 11 Dec 2017 12:02:40 +0100
Hi,

the patches look good to me (which does not have to mean much),
About the Xfburn 

ng0 wrote:
> 1. No Drive found (thanks Cpt. Obvious, I have no optical drive here).

You may at least try creating an ISO image file instead of burning.
Choose "New Data Composition", click the "+ Add" button, choose some
file by single click (double click crashes my local Xfburn), click
the "Add" button at the lower left, click "Proceed to Burn" at the
lower left, check "Only create ISO" and choose a file name for the ISO
image file.

There is a software emulator for some combinations of optical drives
and media types:
  http://cdemu.sourceforge.net/about
It is quite a poor surrogate to a real DVD or BD drive, but at least
the current bug carer of K3B uses it with some success.


> 2. More concerning:
>    Failed to initialize gstreamer transcoder: An error occurred setting
> gstreamer up for transcoding
>   (falling back to basic implementation)

In
  https://forums.bunsenlabs.org/viewtopic.php?id=102
i see the advise to do
  sudo apt-get install --no-install-recommends gstreamer0.10-plugins-good gstreamer0.10-plugins-ugly
and a comment saying that installing of "qtstreamer-plugins,
gstreamer1.0-libav, libgstreamer-perl, ruby-clutter-gstreamer" did the
trick, too.

So it seems to be about finding the packages which contain the desired
software. Looking at the dependencies list of
  https://packages.debian.org/oldstable/gstreamer0.10-plugins-good
  https://packages.debian.org/oldstable/gstreamer0.10-plugins-ugly
i'd say that this might become a lengthy adventure, if not these lines
in 0003-gnu-Add-xfburn.patch already pull in most of it:
+       ("gstreamer" ,gstreamer)
+       ("gst-plugins-base" ,gst-plugins-base)

gstreamer should not be necessary for the tasks of "New Data Composition",
"Burn Image", and "Blank Disc".
I expect no need for it in the task of "Audio CD" if the input files are
already converted to .wav with the properties "uncompressed headerless PCM,
44100 Hz, 16 bit, stereo".


Have a nice day :)

Thomas





Information forwarded to guix-patches <at> gnu.org:
bug#28398; Package guix-patches. (Fri, 29 Dec 2017 16:41:02 GMT) Full text and rfc822 format available.

Message #50 received at 28398 <at> debbugs.gnu.org (full text, mbox):

From: ng0 <ng0 <at> n0.is>
To: Thomas Schmitt <scdbackup <at> gmx.net>
Cc: 28398 <at> debbugs.gnu.org, ludo <at> gnu.org, ng0 <at> n0.is
Subject: Re: [bug#28398] Xfburn
Date: Fri, 29 Dec 2017 16:39:42 +0000
[Message part 1 (text/plain, inline)]
Thomas Schmitt transcribed 2.0K bytes:
> Hi,
> 
> the patches look good to me (which does not have to mean much),
> About the Xfburn 
> 
> ng0 wrote:
> > 1. No Drive found (thanks Cpt. Obvious, I have no optical drive here).
> 
> You may at least try creating an ISO image file instead of burning.
> Choose "New Data Composition", click the "+ Add" button, choose some
> file by single click (double click crashes my local Xfburn), click
> the "Add" button at the lower left, click "Proceed to Burn" at the
> lower left, check "Only create ISO" and choose a file name for the ISO
> image file.
> 
> There is a software emulator for some combinations of optical drives
> and media types:
>   http://cdemu.sourceforge.net/about
> It is quite a poor surrogate to a real DVD or BD drive, but at least
> the current bug carer of K3B uses it with some success.

I didn't use cdemu - I would need to package that - but I mounted the data
collection type .iso I recorded into an ISO file. From what I can tell, it works.

I have issues with the icons, but that's just my personal WM/DM (which is pretty sminimal)
and can be addressed later on (this is trivial and you just need the right icon set).

I'll attach the latest patches.
Let's just merge this now and address the rest later, okay?
I have other issues I need to work on, and from where I stand this
is done - all the basic issues have been fixed.
I appreciate the help Thomas, thanks for what you have done. It's
extraordinary, we usually don't get it like this.

Thanks!
> 
> > 2. More concerning:
> >    Failed to initialize gstreamer transcoder: An error occurred setting
> > gstreamer up for transcoding
> >   (falling back to basic implementation)
> 
> In
>   https://forums.bunsenlabs.org/viewtopic.php?id=102
> i see the advise to do
>   sudo apt-get install --no-install-recommends gstreamer0.10-plugins-good gstreamer0.10-plugins-ugly
> and a comment saying that installing of "qtstreamer-plugins,
> gstreamer1.0-libav, libgstreamer-perl, ruby-clutter-gstreamer" did the
> trick, too.
> 
> So it seems to be about finding the packages which contain the desired
> software. Looking at the dependencies list of
>   https://packages.debian.org/oldstable/gstreamer0.10-plugins-good
>   https://packages.debian.org/oldstable/gstreamer0.10-plugins-ugly
> i'd say that this might become a lengthy adventure, if not these lines
> in 0003-gnu-Add-xfburn.patch already pull in most of it:
> +       ("gstreamer" ,gstreamer)
> +       ("gst-plugins-base" ,gst-plugins-base)
> 
> gstreamer should not be necessary for the tasks of "New Data Composition",
> "Burn Image", and "Blank Disc".
> I expect no need for it in the task of "Audio CD" if the input files are
> already converted to .wav with the properties "uncompressed headerless PCM,
> 44100 Hz, 16 bit, stereo".
> 
> 
> Have a nice day :)
> 
> Thomas
> 
> 

-- 
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://c.n0.is/ng0_pubkeys/tree/keys
  WWW: https://n0.is
[0001-gnu-Add-libburn.patch (text/plain, attachment)]
[0002-gnu-Add-libisofs.patch (text/plain, attachment)]
[0003-gnu-Add-xfburn.patch (text/plain, attachment)]
[0004-gnu-xorriso-Remove-bzip2-and-libcdio-from-inputs.patch (text/plain, attachment)]
[signature.asc (application/pgp-signature, inline)]

Reply sent to Christopher Baines <mail <at> cbaines.net>:
You have taken responsibility. (Thu, 01 Feb 2018 23:05:01 GMT) Full text and rfc822 format available.

Notification sent to ng0 <ng0 <at> infotropique.org>:
bug acknowledged by developer. (Thu, 01 Feb 2018 23:05:02 GMT) Full text and rfc822 format available.

Message #55 received at 28398-done <at> debbugs.gnu.org (full text, mbox):

From: Christopher Baines <mail <at> cbaines.net>
To: ng0 <ng0 <at> n0.is>
Cc: 28398-done <at> debbugs.gnu.org, Thomas Schmitt <scdbackup <at> gmx.net>
Subject: Re: [bug#28398] Xfburn
Date: Thu, 01 Feb 2018 23:04:01 +0000
[Message part 1 (text/plain, inline)]
ng0 <ng0 <at> n0.is> writes:

> Thomas Schmitt transcribed 2.0K bytes:
>> Hi,
>> 
>> the patches look good to me (which does not have to mean much),
>> About the Xfburn 
>> 
>> ng0 wrote:
>> > 1. No Drive found (thanks Cpt. Obvious, I have no optical drive here).
>> 
>> You may at least try creating an ISO image file instead of burning.
>> Choose "New Data Composition", click the "+ Add" button, choose some
>> file by single click (double click crashes my local Xfburn), click
>> the "Add" button at the lower left, click "Proceed to Burn" at the
>> lower left, check "Only create ISO" and choose a file name for the ISO
>> image file.
>> 
>> There is a software emulator for some combinations of optical drives
>> and media types:
>>   http://cdemu.sourceforge.net/about
>> It is quite a poor surrogate to a real DVD or BD drive, but at least
>> the current bug carer of K3B uses it with some success.
>
> I didn't use cdemu - I would need to package that - but I mounted the data
> collection type .iso I recorded into an ISO file. From what I can tell, it works.
>
> I have issues with the icons, but that's just my personal WM/DM (which is pretty sminimal)
> and can be addressed later on (this is trivial and you just need the right icon set).
>
> I'll attach the latest patches.
> Let's just merge this now and address the rest later, okay?
> I have other issues I need to work on, and from where I stand this
> is done - all the basic issues have been fixed.
> I appreciate the help Thomas, thanks for what you have done. It's
> extraordinary, we usually don't get it like this.

Thanks for following up on this ng0. I've finally got around to looking
at Xfburn again and I've now pushed these 4 patches.

I ammended the commit message for the last one to add that the removed
inputs are not referenced by the output (before removing them), which
makes me more confident that something isn't breaking. As xorriso was
changed, I also ran the iso-image-installer test, and that passed.

Thanks again,

Chris
[signature.asc (application/pgp-signature, inline)]

bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Fri, 02 Mar 2018 12:24:05 GMT) Full text and rfc822 format available.

This bug report was last modified 6 years and 28 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.