7:25 a.m.
I'm looking into the possibility of generating deltaisos directly on alt.fp.o,
which runs RHEL 5.6, rather than downloading the ISOs, creating the disos, then
uploading them. This would make it possible to post the disos much sooner as my
connection is 3/768 DSL and most of the time involved is in the download/upload.
In addition, alt.fp.o has 8 cores, so it would be possible to use 2 of them
simultaneously. (The programs I need, makedeltaiso and applydeltaiso, are
single-threaded.)
The possibilities I'm aware of are either creating static executables or using a
chroot environment (the first seems preferable, if possible). Can anyone give
any pointers? Thanks.
8:46 a.m.
-----Original Message-----
From: test-bounces(a)lists.fedoraproject.org [mailto:test-
bounces(a)lists.fedoraproject.org] On Behalf Of Andre Robatino
Sent: Friday, April 01, 2011 8:25
To: test(a)lists.fedoraproject.org
Subject: running F15 programs on a RHEL 5.6 box
I'm looking into the possibility of generating deltaisos directly on
alt.fp.o,
which runs RHEL 5.6, rather than downloading the ISOs, creating the
disos, then
uploading them. This would make it possible to post the disos much
sooner as my
connection is 3/768 DSL and most of the time involved is in the
download/upload.
In addition, alt.fp.o has 8 cores, so it would be possible to use 2 of
them
simultaneously. (The programs I need, makedeltaiso and applydeltaiso,
are
single-threaded.)
The possibilities I'm aware of are either creating static executables
or using a
chroot environment (the first seems preferable, if possible). Can
anyone give
any pointers? Thanks.
If EPEL[1] is installed, then a yum install deltaiso should get them
for the admin.
[1] http://fedoraproject.org/wiki/EPEL
8:54 a.m.
Denniston, Todd A CIV NAVSURFWARCENDIV Crane <todd.denniston <at> navy.mil>
writes:
If EPEL[1] is installed, then a yum install deltaiso should get
them
for the admin.
[1] http://fedoraproject.org/wiki/EPEL
The machine only has the old xz compression library (liblzma.so.0). The F15
versions of {make,apply}deltaiso require the new library (liblzma.so.5) to
rebuild F15 ISOs, so I can't use the EPEL version. It would have worked for
disos for F14 and below.
9:01 a.m.
On Friday, April 01, 2011 07:25:09 AM Andre Robatino wrote:
I'm looking into the possibility of generating deltaisos directly
on
alt.fp.o, which runs RHEL 5.6, rather than downloading the ISOs, creating
the disos, then uploading them. This would make it possible to post the
disos much sooner as my connection is 3/768 DSL and most of the time
involved is in the download/upload. In addition, alt.fp.o has 8 cores, so
it would be possible to use 2 of them simultaneously. (The programs I
need, makedeltaiso and applydeltaiso, are single-threaded.)
The possibilities I'm aware of are either creating static executables or
using a chroot environment (the first seems preferable, if possible). Can
anyone give any pointers? Thanks.
Its not at all possible, glibc in f15 requires that the host be running 2.6.32
or newer kernel, and its running 2.6.18.
Dennis
9:35 a.m.
Dennis Gilmore <dennis <at> ausil.us> writes:
On Friday, April 01, 2011 07:25:09 AM Andre Robatino wrote:
> I'm looking into the possibility of generating deltaisos directly on
> alt.fp.o, which runs RHEL 5.6, rather than downloading the ISOs, creating
> the disos, then uploading them. This would make it possible to post the
> disos much sooner as my connection is 3/768 DSL and most of the time
> involved is in the download/upload. In addition, alt.fp.o has 8 cores, so
> it would be possible to use 2 of them simultaneously. (The programs I
> need, makedeltaiso and applydeltaiso, are single-threaded.)
>
> The possibilities I'm aware of are either creating static executables or
> using a chroot environment (the first seems preferable, if possible). Can
> anyone give any pointers? Thanks.
Its not at all possible, glibc in f15 requires that the host be running 2.6.32
or newer kernel, and its running 2.6.18.
I've found by just attempting to run the F14 and F15 {make,apply}deltaiso
executables that the F14 version of makedeltaiso seems to work normally, though
F14's applydeltaiso complains:
applydeltaiso_f14: /lib64/libc.so.6: version `GLIBC_2.7' not found (required by
applydeltaiso_f14)
The F15 versions both fail due to the missing liblzma.so.5, as expected. Would
the difference between F14's
glibc-2.13-1 and F15's glibc-2.13.90-8 make F15's makedeltaiso fail even if
liblzma.so.5 was installed? Just getting that to work would save quite a bit of
time. Ideally, I'd like to find a way to make this work without any such outside
support, though.
5:01 p.m.
On Fri, 1 Apr 2011, Andre Robatino wrote:
I'm looking into the possibility of generating deltaisos directly
on alt.fp.o,
which runs RHEL 5.6, rather than downloading the ISOs, creating the disos, then
uploading them. This would make it possible to post the disos much sooner as my
connection is 3/768 DSL and most of the time involved is in the download/upload.
In addition, alt.fp.o has 8 cores, so it would be possible to use 2 of them
simultaneously. (The programs I need, makedeltaiso and applydeltaiso, are
single-threaded.)
The possibilities I'm aware of are either creating static executables or using a
chroot environment (the first seems preferable, if possible). Can anyone give
any pointers? Thanks.
You only need the liblzma bits to be static. I think the following should
work
1. Install the F15 xz-5 source rpm and prepare it for building (rpmbuild
-bp)
2. Go into the xz-5 build directory and run make
3. Install the F15 deltarpm source rpm and prepare it for building
(rpmbuild -bp)
4. Go into the deltarpm build directory and edit the Makefile to use the
lzma headers and archive you just built - with something like the patch
below
5. make
6. Test the applydeltaiao and makdeltaiso files to see if they work.
Michael Young
--- Makefile 2011-01-21 09:45:12.000000000 +0000
+++ Makefile 2011-04-01 22:41:03.000000000 +0100
@@ -5,12 +5,12 @@
rpmdumpheader=$(bindir)/rpmdumpheader
zlibdir=zlib-1.2.2.f-rsyncable
zlibbundled=$(zlibdir)/libz.a
-zlibldflags=$(zlibbundled)
-zlibcppflags=-I$(zlibdir)
+zlibldflags=$(zlibbundled) ../xz-5.0.1/src/liblzma/.libs/liblzma.a
+zlibcppflags=-I$(zlibdir) -I../xz-5.0.1/src/liblzma/api/
pylibprefix=/
CFLAGS = -fPIC -O2 -Wall -g
CPPFLAGS = -fPIC -DDELTARPM_64BIT -DBSDIFF_NO_SUF
-DRPMDUMPHEADER=\"$(rpmdumpheader)\" $(zlibcppflags)
-LDLIBS = -lbz2 $(zlibldflags) -llzma
+LDLIBS = -lbz2 $(zlibldflags)
LDFLAGS =
all: makedeltarpm applydeltarpm rpmdumpheader makedeltaiso applydeltaiso combinedeltarpm
fragiso
6:03 a.m.
M A Young <m.a.young <at> durham.ac.uk> writes:
You only need the liblzma bits to be static. I think the following
should
work
I did what you described on a F15 machine, and it works! Thank you. These could
also be used in place of the F14 compression upgrade hack, so I'll probably post
them
on my fedorapeople site. I don't understand why they both work, though - the F14
version of applydeltaiso failed with
applydeltaiso_f14: /lib64/libc.so.6: version `GLIBC_2.7' not found (required by
applydeltaiso_f14)
so why does this version work, given that it was built on F15, without libc.so.6
being static?
I'm working now on trying to get a version of metalink that will run on
alt.fp.o. There is no metalink package in the RHEL repos, and running F14's
metalink gives the error
metalink_f14: error while loading shared libraries: libglibmm-2.4.so.1: cannot
open shared object file: No such file or directory
and this library is included in the glibmm24 package, which IS in the EPEL repo,
but not installed. I'm trying to use your procedure with xz -> glibmm24 and
deltarpm -> metalink, but unfortunately metalink's Makefile is much more
complicated than deltarpm's (being generated by ./configure) so it's difficult
to figure out the proper edit. But this is much less important than the deltaiso
executables anyway.
4824
days inactive
4825
days old
6 comments
4 participants
participants (4)
-
Andre Robatino -
Dennis Gilmore -
Denniston, Todd A CIV NAVSURFWARCENDIV Crane -
M A Young