Debian Bug report logs - #679254
RFH: libisofs -- library to create ISO9660 images

Package: wnpp; Maintainer for wnpp is wnpp@debian.org;

Reported by: George Danchev <danchev@spnet.net>

Date: Wed, 27 Jun 2012 13:02:20 UTC

Severity: normal

Reply or subscribe to this bug.

Toggle useless messages

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


Report forwarded to debian-bugs-dist@lists.debian.org, danchev@spnet.net, debian-devel@lists.debian.org, wnpp@debian.org:
Bug#679254; Package wnpp. (Wed, 27 Jun 2012 13:02:23 GMT) Full text and rfc822 format available.

Acknowledgement sent to George Danchev <danchev@spnet.net>:
New Bug report received and forwarded. Copy sent to danchev@spnet.net, debian-devel@lists.debian.org, wnpp@debian.org. (Wed, 27 Jun 2012 13:02:26 GMT) Full text and rfc822 format available.

Message #5 received at submit@bugs.debian.org (full text, mbox):

From: George Danchev <danchev@spnet.net>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: RFH: libisofs -- library to create ISO9660 images
Date: Wed, 27 Jun 2012 15:01:39 +0200
Package: wnpp
Severity: normal

I request assistance with maintaining the libisofs package.

I currently lack the time to maintain this package alone.
The major drain of time is following various image specs, following
the upstream VCS, and further discussions. One interesting aspect is
that libisofs links with libjte in order to produce jigdo representation
at the same time while producing the iso image itself (state stable).
Further developments are ongoing to produce ISO9660/HFS(+) hybrids,
see #630351 for some details, which is also of interest of debian-cd
task (currently performed by genisoimage for Debian PowerPC images offered)
This would take quite some effort in testing and proving it correct.

Upstream is responsive. The alioth project could be reached at:
pkg-libburnia-devel@lists.alioth.debian.org
Co-maintainers welcome.

The package description is:
 libisofs creates ISO images which can then be burnt with cdrskin or other
 software.




Information forwarded to debian-bugs-dist@lists.debian.org, wnpp@debian.org:
Bug#679254; Package wnpp. (Mon, 30 Jul 2012 20:21:05 GMT) Full text and rfc822 format available.

Acknowledgement sent to "bash.d" <bash.d@bashd.org>:
Extra info received and forwarded to list. Copy sent to wnpp@debian.org. (Mon, 30 Jul 2012 20:21:05 GMT) Full text and rfc822 format available.

Message #10 received at 679254@bugs.debian.org (full text, mbox):

From: "bash.d" <bash.d@bashd.org>
To: 679254@bugs.debian.org
Subject: RFH: libisofs -- library to create ISO9660 images
Date: Mon, 30 Jul 2012 21:50:35 +0200
Hello,

I am offering my help to support the libisofs package.
What specific tasks are there? I don't yet have much experience
in library-development but am eager to learn.
Please tell me how I can help.

Thank you and regards,

Sebastian




Information forwarded to debian-bugs-dist@lists.debian.org, wnpp@debian.org:
Bug#679254; Package wnpp. (Thu, 02 Aug 2012 10:39:03 GMT) Full text and rfc822 format available.

Acknowledgement sent to George Danchev <danchev@spnet.net>:
Extra info received and forwarded to list. Copy sent to wnpp@debian.org. (Thu, 02 Aug 2012 10:39:03 GMT) Full text and rfc822 format available.

Message #15 received at 679254@bugs.debian.org (full text, mbox):

From: George Danchev <danchev@spnet.net>
To: 679254@bugs.debian.org
Subject: Re: [Pkg-libburnia-devel] libisofs
Date: Thu, 2 Aug 2012 12:28:58 +0200
Just bouncing this one to serve as a reference, since I forgot to do it in the 
first place when replying. Further discissions will take plane in the pkg- 
list.

On Wednesday 01 August 2012 21:28:22 bash.d wrote:
> Hello, George Danchev,
> 
> I would like to help you maintaining the libisofs-package.
> I already replied to the BTS entry, but have not yet received any
> response. If you are interested, please answer me.
> Thank you and regards,

Hi Sebastian, [I added pkg-libburnia-devel@ in CC, where Thomas Schmitt is 
also subscribed]

Thank you for your offer to help, it is really appreciated. It is of course my 
fault of not paying attention close to RFH#679254, but you did it right 
pinging my on private. Thanks!

The three libraries of libburn (RFH#679249), libisofs, and libisoburn 
(RFH#679265) are best to be maintained together, and involve quite some 
interaction with upstream, which is fortunately very responsive and helpful. 
See http://libburnia-project.org for details, and the upstream list is 
libburn-hackers@pykix.org.

For libisofs in particular, there is an effort to complete the hybrid fs part, 
which involves HFS+ (see libisofs/hfsplus*.c|h in bzr) and HFS (no plus) - no 
code yet. ISO9660/HFS hybrid is used for the production of Debian PowerPC 
images, and in order to replace the old and almost unmaintained genisoimage, 
it would be nice to have this one properly implemented, verified and deployed.
(actually these are HFS#630351 and UDF#630863, the latter being a goal in the 
distant future).

The libburnia libraries are covered by in-house test suite called 'releng':
See, README, TODO and CHECKLIST, as well as the code at:
http://libburnia-project.org/browser/libisoburn/trunk/releng

Extending and running this test suite is a good way to build trust that no or 
less regressions would occur.

Then comes the debian-cd task, which is the largest "stress-test suite" for 
xorriso (and resp. libisofs in particular) currently known to us, so it is 
also nice to pay attention to debian-cd BTS record for relevant bugs, the 
debian-cd mailing list for relevant complaints, and debian-cd live logs as 
well: http://cdbuilder.debian.org/cdimage-log/ (also see analysis.html)

Last, but not least, it is also nice to try to help applications which are 
trying to make proper use (or resp. abuse) of libburnia libraries to find their 
way. For instance, see brasero BTS record.

To summarize: there is a plenty of code work, thrice as much testing and bug 
triaging and sorting out (coupled and decoupled) issues or non-issues... and 
I'm pretty sure Thomas can add some more points as well. While it is true that 
libburn/libisofs/libisoburn currently bear almost perfectly clean BTS log 
record, it took, takes, and will take a fair amount of time to preserve this 
state as it is.

So, feel free to pick your niche to contribute to the project :)

-- 
pub 4096R/0E4BD0AB <people.fccf.net/danchev/key pgp.mit.edu>



Information forwarded to debian-bugs-dist@lists.debian.org, wnpp@debian.org:
Bug#679254; Package wnpp. (Fri, 03 Aug 2012 20:06:05 GMT) Full text and rfc822 format available.

Acknowledgement sent to "bash.d" <bash.d@bashd.org>:
Extra info received and forwarded to list. Copy sent to wnpp@debian.org. (Fri, 03 Aug 2012 20:06:05 GMT) Full text and rfc822 format available.

Message #20 received at 679254@bugs.debian.org (full text, mbox):

From: "bash.d" <bash.d@bashd.org>
To: George Danchev <danchev@spnet.net>, 679254@bugs.debian.org
Subject: Re: Bug#679254: [Pkg-libburnia-devel] libisofs
Date: Fri, 03 Aug 2012 22:02:38 +0200
Hello, George,

thank you for your response.
I just took a look and I am quite overwhelmed by the mass
of code and stuff to do.
I was about to find an implementation for the comparison
of the Iso1999Nodes.
Unfortunately I have not found reliable specs for ISO9660:1999, 9.3.
Do you have a document or source I could use, please?
Thank you very much and regards,

Sebastian

Am Donnerstag, den 02.08.2012, 12:28 +0200 schrieb George Danchev:
> Just bouncing this one to serve as a reference, since I forgot to do it in the 
> first place when replying. Further discissions will take plane in the pkg- 
> list.
> 
> On Wednesday 01 August 2012 21:28:22 bash.d wrote:
> > Hello, George Danchev,
> > 
> > I would like to help you maintaining the libisofs-package.
> > I already replied to the BTS entry, but have not yet received any
> > response. If you are interested, please answer me.
> > Thank you and regards,
> 
> Hi Sebastian, [I added pkg-libburnia-devel@ in CC, where Thomas Schmitt is 
> also subscribed]
> 
> Thank you for your offer to help, it is really appreciated. It is of course my 
> fault of not paying attention close to RFH#679254, but you did it right 
> pinging my on private. Thanks!
> 
> The three libraries of libburn (RFH#679249), libisofs, and libisoburn 
> (RFH#679265) are best to be maintained together, and involve quite some 
> interaction with upstream, which is fortunately very responsive and helpful. 
> See http://libburnia-project.org for details, and the upstream list is 
> libburn-hackers@pykix.org.
> 
> For libisofs in particular, there is an effort to complete the hybrid fs part, 
> which involves HFS+ (see libisofs/hfsplus*.c|h in bzr) and HFS (no plus) - no 
> code yet. ISO9660/HFS hybrid is used for the production of Debian PowerPC 
> images, and in order to replace the old and almost unmaintained genisoimage, 
> it would be nice to have this one properly implemented, verified and deployed.
> (actually these are HFS#630351 and UDF#630863, the latter being a goal in the 
> distant future).
> 
> The libburnia libraries are covered by in-house test suite called 'releng':
> See, README, TODO and CHECKLIST, as well as the code at:
> http://libburnia-project.org/browser/libisoburn/trunk/releng
> 
> Extending and running this test suite is a good way to build trust that no or 
> less regressions would occur.
> 
> Then comes the debian-cd task, which is the largest "stress-test suite" for 
> xorriso (and resp. libisofs in particular) currently known to us, so it is 
> also nice to pay attention to debian-cd BTS record for relevant bugs, the 
> debian-cd mailing list for relevant complaints, and debian-cd live logs as 
> well: http://cdbuilder.debian.org/cdimage-log/ (also see analysis.html)
> 
> Last, but not least, it is also nice to try to help applications which are 
> trying to make proper use (or resp. abuse) of libburnia libraries to find their 
> way. For instance, see brasero BTS record.
> 
> To summarize: there is a plenty of code work, thrice as much testing and bug 
> triaging and sorting out (coupled and decoupled) issues or non-issues... and 
> I'm pretty sure Thomas can add some more points as well. While it is true that 
> libburn/libisofs/libisoburn currently bear almost perfectly clean BTS log 
> record, it took, takes, and will take a fair amount of time to preserve this 
> state as it is.
> 
> So, feel free to pick your niche to contribute to the project :)
> 
> -- 
> pub 4096R/0E4BD0AB <people.fccf.net/danchev/key pgp.mit.edu>
> 






Send a report that this bug log contains spam.


Debian bug tracking system administrator <owner@bugs.debian.org>. Last modified: Sun Apr 20 06:12:14 2014; Machine Name: buxtehude.debian.org

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