Mailinglist Archive: opensuse-buildservice (306 mails)

< Previous Next >
[opensuse-buildservice] Trying to contact maintainer of OpenSUSE package xorriso
  • From: "Thomas Schmitt" <scdbackup@xxxxxxx>
  • Date: Mon, 21 Jun 2010 09:53:36 +0200
  • Message-id: <9517265245353@xxxxxxxxxxxx>
Hi,

yesterday i tried to contact pascal.bleser@xxxxxxxxxxxx
whom i assume to be the maintainer of the
xorriso package

https://build.opensuse.org/package/show?package=xorriso&project=Archiving%3ABackup
but got blocked out by blacklister www.openspf.org
who is bviously at odds with my mail provider.

Could the build service community please help
to bring the following mail to Pascal's
attention ?

------------------------------------------------
Date: Sun, 20 Jun 2010 16:48:03 +0200
From: Thomas Schmitt <scdbackup@xxxxxxx>
To: <pascal.bleser@xxxxxxxxxxxx>
Subject: openSUSE package xorriso with zlib, ACL, xattr

Hi,

thanks for covering GNU xorriso.

I see on

https://build.opensuse.org/package/rawlog?arch=x86_64&package=xorriso&project=Archiving%3ABackup&repository=openSUSE_11.2

that the development stuff for zlib, ACL and
xattr is not installed at build time:
...
checking sys/acl.h usability... no
checking sys/acl.h presence... no
checking for sys/acl.h... no
checking attr/xattr.h usability... no
checking attr/xattr.h presence... no
checking for attr/xattr.h... no
checking zlib.h usability... no
checking zlib.h presence... no
checking for zlib.h... no
...

This restricts xorriso's backup capabilities.

Run time libraries are supposed to be libacl
and libz.
I see before the configure run:
...
installing zlib-1.2.3-140.2
...
installing libacl-2.2.48-2.2
...
So it seems to be a matter of development header
packages missing.
I developed according to
man 2 getxattr
man 3 acl_get_file
/usr/include/zlib.h


If ACL and xattr features are available, then
xorriso can record them, produce output as of
getfacl and getfattr, and extract files with
ACL and xattr from ISO to disk.
If zlib is available, then file content can be
compressed on-the-fly to gzip format or to
zisofs format. The latter is readable by Linux
kernels and gets uncompressed transparently
(if CONFIG_ZISOFS is defined).

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

Further i see that xorriso is also built and
installed by the package "libburnia"
https://build.opensuse.org/package/show?package=libburnia&project=X11%3Axfce

Is this intersection intentional ?
xorriso from libburnia and GNU xorriso are
functionally identical. Only linking and
license differ.

Package libburnia is about 3 revisions behind,
currently. Released are
libburn-0.8.2
libisofs-0.6.32
libisoburn-0.5.8 (which contains xorriso)
GNU xorriso-0.5.8 consists of 0.8.3, 0.6.33,
and 0.5.8.

The same lack of zlib, ACL, and xattr can be
observed in

https://build.opensuse.org/package/rawlog?arch=x86_64&package=libburnia&project=X11%3Axfce&repository=openSUSE_11.2
where i also see
/bin/sh ./libtool --silent --mode=install /usr/bin/install -c
'xorriso/xorriso' '/tmp/tmp.z6FNs65lXb/usr/bin/xorriso'
libtool: install: warning: `libisoburn/libisoburn.la' has not been installed
in `/usr/lib64'

So possibly the installed xorriso will not
start ?

Will it nevertheless overwrite GNU xorriso ?

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

I checked the compiler warnings about
GNU xorriso 0.5.8.
Hopefully they are silenced now for the next
release. They are all harmless. I.e. the
ignorance for return values is intended because
there is no fallback action anyway.


Have a nice day :)

Thomas

--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups