15 Oct
2013
15 Oct
'13
11:43 p.m.
Come on, building xz requires xz ?
I used to build xz on a bunch of old targets so that OTHER packages that
required xz would find it, but now they all fail because the
Base:build/xz I branched from changed to use xz-<version>.tar.xz as it's
source file.
xz itself cannot sanely buildrequires xz!
(wasn't any explicit buildrequires either, just an assumption that tar
would handle a .tar.xz, because the failure was only in the build logs
"tar: file does not appear to be a tar archive", not a
requires/buildrequires resolver message.)
--
bkw
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
16 Oct
16 Oct
10:57 a.m.
On Tuesday 15 October 2013, Brian K. White wrote:
Come on, building xz requires xz ?
I used to build xz on a bunch of old targets so that OTHER packages
that required xz would find it, but now they all fail because the
Base:build/xz I branched from changed to use xz-<version>.tar.xz as
it's source file.
I maintain a project for many targets where xz and tar is only built if
it's needed to let it work with xz compressed sources. You could
aggregate the packages from there
https://build.opensuse.org/project/monitor/home:rudi_m:bldchn
xz itself cannot sanely buildrequires xz!
You also need gcc to build gcc, or coreutils for coreutils.
Of course in this case I also find it pity that xz sources were not
fixed generally for all standard distros on OBS.
(wasn't any explicit buildrequires either, just an
assumption that
tar would handle a .tar.xz, because the failure was only in the build
logs "tar: file does not appear to be a tar archive", not a
requires/buildrequires resolver message.)
It depends whether
tar -xf bla.tar.xz
or
xz -dc bla.tar.gz | tar -xf -
which is AFAIR not the same on all distro.
On some distros (e.g. CentOS_CentOS-5) you only need to update tar and
not xz, as you see in my home:rudi_m:bldchn project.
cu,
Rudi
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
11:59 a.m.
Am Mittwoch, 16. Oktober 2013, 10:57:03 schrieb Ruediger Meier:
On Tuesday 15 October 2013, Brian K. White wrote:
I think the difference here is that the very old gcc of the oldest
distribution is still enough to start to bootstrap gcc.
While xz just does not exist at all in the old distros.
Yes, bootstraping is needed for many packages, but it is good when
it can be avoided.
--
Adrian Schroeter
email: adrian(a)suse.de
SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284
(AG Nürnberg)
Maxfeldstraße 5
90409 Nürnberg
Germany
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Come on, building xz requires xz ?
I used to build xz on a bunch of old targets so that OTHER packages
that required xz would find it, but now they all fail because the
Base:build/xz I branched from changed to use xz-<version>.tar.xz as
it's source file.
I maintain a project for many targets where xz and tar is only built if
it's needed to let it work with xz compressed sources. You could
aggregate the packages from there
https://build.opensuse.org/project/monitor/home:rudi_m:bldchn
xz itself cannot sanely buildrequires xz!
You also need gcc to build gcc, or coreutils for coreutils.
Of course in this case I also find it pity that xz sources were not
fixed generally for all standard distros on OBS.
12:49 p.m.
On Oct 16, 13 11:59:01 +0200, Adrian Schröter wrote:
Am Mittwoch, 16. Oktober 2013, 10:57:03 schrieb
Ruediger Meier:
> On Tuesday 15 October 2013, Brian K. White wrote:
> > Come on, building xz requires xz ?
> >
> I maintain a project for many targets where xz and tar is only built if
> it's needed to let it work with xz compressed sources. You could
> aggregate the packages from there
> https://build.opensuse.org/project/monitor/home:rudi_m:bldchn
>
> > xz itself cannot sanely buildrequires xz!
The self-dependency is quite obvious:
xz upstream choose to compress their tar ball with xz itself.
Not sure how user friendly that is. (Good for testing, maybe.)
OBS cannot unpack this, unless xz is installed.
Yes, bootstraping is needed for many packages, but it
is good when
it can be avoided.
Their idea is not to require installation of exactly 'itself', but to
require any older (hopefully existing) version.
I'd suggest, to recompress the xz-tarball in gz format, just like we
do with the bzip2 tarball.
That should help with most bootstrap issues.
It might not help with a full source bootstrap, as the gzip2-tarball is
then again xz compressed, thus entering a cyclic dependency.
cheers,
JW-
--
o \ Juergen Weigert paint it green! __/ _=======.=======_
<V> | jw(a)suse.de back to ascii! __/ _---|____________\/
\ | 0911 74053-508 say #263A!__/ (____/ /\
(/) | _____________________________/ _/ \_ vim:set sw=2 wm=8
SUSE LINUX Products GmbH, GF: Jeff Hawn, J.Guild, F.Imendoerffer, HRB 16746
(AG Nuernberg), Maxfeldstrasse 5, 90409 Nuernberg, Germany
SuSE. Supporting Linux since 1992. ☺
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
3:25 p.m.
On Wed, Oct 16, 2013 at 12:49:14PM +0200, Juergen Weigert wrote:
On Oct 16, 13 11:59:01 +0200, Adrian Schröter wrote:
Why do you claim that? Upstream does provide gzipped, bzip2ped and
xzipped tarballs, so it was pure maintainer's decision to pickup xz
archive.
BTW: I have already submitted request for a change, which uses
http://tukaani.org/xz/xz-5.0.5.tar.gz, just not yet accepted.
Regards
Michal Vyskocil
Am Mittwoch, 16. Oktober 2013, 10:57:03 schrieb
Ruediger Meier:
> On Tuesday 15 October 2013, Brian K. White wrote:
> > Come on, building xz requires xz ?
> >
> I maintain a project for many targets where xz and tar is only built if
> it's needed to let it work with xz compressed sources. You could
> aggregate the packages from there
> https://build.opensuse.org/project/monitor/home:rudi_m:bldchn
>
> > xz itself cannot sanely buildrequires xz!
The self-dependency is quite obvious:
xz upstream choose to compress their tar ball with xz itself.
3 Nov
3 Nov
8:53 a.m.
On 10/16/2013 9:25 AM, Michal Vyskocil wrote:
BTW: I have already submitted request for a change,
which uses
http://tukaani.org/xz/xz-5.0.5.tar.gz, just not yet accepted.
Thanks, My stuff is all building again.
--
bkw
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
16 Oct
16 Oct
11:01 a.m.
On Tue, Oct 15, 2013 at 05:43:54PM -0400, Brian K. White wrote:
Come on, building xz requires xz ?
I used to build xz on a bunch of old targets so that OTHER packages
that required xz would find it, but now they all fail because the
Base:build/xz I branched from changed to use xz-<version>.tar.xz as
it's source file.
xz itself cannot sanely buildrequires xz!
(wasn't any explicit buildrequires either, just an assumption that
tar would handle a .tar.xz, because the failure was only in the
build logs "tar: file does not appear to be a tar archive", not a
requires/buildrequires resolver message.)
See https://build.opensuse.org/request/show/203465 - hope it will be
accepted.
Regards
Michal Vyskocil
--
bkw
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
2639
days inactive
2658
days old
buildservice@lists.opensuse.org
6 comments
5 participants
participants (5)
-
Adrian Schröter -
Brian K. White -
Juergen Weigert -
Michal Vyskocil -
Ruediger Meier