[zypp-devel] a more recent zypper for openSUSE 10.2
Hello, I really love the way ypper works in current factory. I have a VPS (Virtual Private Server), based on 10.2 (yes.. some of them have such a new one.. most still run 9.3 or max 10.1) I would like to upgrade to a more recent zypper there (I don't care much about the yast modules; most of my things I configure in the config files.. so if I break YaST, bad luck ;) the problem I have, though is: In my OBS project home:dimstar, I linked in zypper, libzypp, libsatsolver (and cmake and hicolor-icon-theme) from openSUSE:Factory, to have them built against 10.2 (the factory RPM does not work because of glibc dependencies not bein satisfied) The issue there seems to be that libsatsolver does not compile. Errors: [ 93%] Building C object bindings/ruby/CMakeFiles/satsolverx.dir/libsatsolver_wrap.o /usr/bin/gcc -Dsatsolverx_EXPORTS -Werror -Wall -Wall -Werror -Wall -g -O3 -fPIC -I/usr/src/packages/BUILD/satsolver-0.0.22 -I/usr/src/packages/BUILD/satsolver-0.0.22/src -I/usr/lib/ruby/1.8/i586-linux -I/usr/src/packages/BUILD/satsolver-0.0.22/applayer -I/usr/src/packages/BUILD/satsolver-0.0.22/tools -D_FILE_OFFSET_BITS=64 -DVERSION=\"0.0.22\" -o bindings/ruby/CMakeFiles/satsolverx.dir/libsatsolver_wrap.o -c /usr/src/packages/BUILD/satsolver-0.0.22/bindings/ruby/libsatsolver_wrap.c /usr/src/packages/BUILD/satsolver-0.0.22/bindings/ruby/libsatsolver_wrap.c: In function 'Repo_size': /usr/src/packages/BUILD/satsolver-0.0.22/bindings/ruby/libsatsolver_wrap.c:1793: error: '$self' undeclared (first use in this function) /usr/src/packages/BUILD/satsolver-0.0.22/bindings/ruby/libsatsolver_wrap.c:1793: error: (Each undeclared identifier is reported only once /usr/src/packages/BUILD/satsolver-0.0.22/bindings/ruby/libsatsolver_wrap.c:1793: error: for each function it appears in.) and it continues on like this. You can see the full log at https://build.opensuse.org/package/live_build_log?arch=i586&package=libsatsolver&project=home%3Adimstar&repository=openSUSE_10.2 Any other ideas how else I could get a newer zypper as my preferred PM on 10.2 to run? Dominique -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
On Thu, Mar 20, Dominique Leuenberger wrote:
Hello,
I really love the way ypper works in current factory. I have a VPS (Virtual Private Server), based on 10.2 (yes.. some of them have such a new one.. most still run 9.3 or max 10.1)
I would like to upgrade to a more recent zypper there (I don't care much about the yast modules; most of my things I configure in the config files.. so if I break YaST, bad luck ;)
the problem I have, though is: In my OBS project home:dimstar, I linked in zypper, libzypp, libsatsolver (and cmake and hicolor-icon-theme) from openSUSE:Factory, to have them built against 10.2 (the factory RPM does not work because of glibc dependencies not bein satisfied)
The issue there seems to be that libsatsolver does not compile.
Errors: [ 93%] Building C object bindings/ruby/CMakeFiles/satsolverx.dir/libsatsolver_wrap.o /usr/bin/gcc -Dsatsolverx_EXPORTS -Werror -Wall -Wall -Werror -Wall -g -O3 -fPIC -I/usr/src/packages/BUILD/satsolver-0.0.22 -I/usr/src/packages/BUILD/satsolver-0.0.22/src -I/usr/lib/ruby/1.8/i586-linux -I/usr/src/packages/BUILD/satsolver-0.0.22/applayer -I/usr/src/packages/BUILD/satsolver-0.0.22/tools -D_FILE_OFFSET_BITS=64 -DVERSION=\"0.0.22\" -o bindings/ruby/CMakeFiles/satsolverx.dir/libsatsolver_wrap.o -c /usr/src/packages/BUILD/satsolver-0.0.22/bindings/ruby/libsatsolver_wrap.c /usr/src/packages/BUILD/satsolver-0.0.22/bindings/ruby/libsatsolver_wrap.c: In function 'Repo_size': /usr/src/packages/BUILD/satsolver-0.0.22/bindings/ruby/libsatsolver_wrap.c:1793: error: '$self' undeclared (first use in this function) /usr/src/packages/BUILD/satsolver-0.0.22/bindings/ruby/libsatsolver_wrap.c:1793: error: (Each undeclared identifier is reported only once /usr/src/packages/BUILD/satsolver-0.0.22/bindings/ruby/libsatsolver_wrap.c:1793: error: for each function it appears in.)
and it continues on like this. You can see the full log at https://build.opensuse.org/package/live_build_log?arch=i586&package=libsatsolver&project=home%3Adimstar&repository=openSUSE_10.2
Any other ideas how else I could get a newer zypper as my preferred PM on 10.2 to run?
AFAIR you need a newer swig version. But if you don't need the bindings you can as well disable them. -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres YaST Development ma@novell.com SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0 +------------------------------------------------------------------+ -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
Dominique Leuenberger wrote:
Hello,
I really love the way ypper works in current factory. I have a VPS (Virtual Private Server), based on 10.2 (yes.. some of them have such a new one.. most still run 9.3 or max 10.1)
I would like to upgrade to a more recent zypper there (I don't care much about the yast modules; most of my things I configure in the config files.. so if I break YaST, bad luck ;)
the problem I have, though is: In my OBS project home:dimstar, I linked in zypper, libzypp, libsatsolver (and cmake and hicolor-icon-theme) from openSUSE:Factory, to have them built against 10.2 (the factory RPM does not work because of glibc dependencies not bein satisfied)
The issue there seems to be that libsatsolver does not compile.
Errors: [ 93%] Building C object bindings/ruby/CMakeFiles/satsolverx.dir/libsatsolver_wrap.o /usr/bin/gcc -Dsatsolverx_EXPORTS -Werror -Wall -Wall -Werror -Wall -g -O3 -fPIC -I/usr/src/packages/BUILD/satsolver-0.0.22 -I/usr/src/packages/BUILD/satsolver-0.0.22/src -I/usr/lib/ruby/1.8/i586-linux -I/usr/src/packages/BUILD/satsolver-0.0.22/applayer -I/usr/src/packages/BUILD/satsolver-0.0.22/tools -D_FILE_OFFSET_BITS=64 -DVERSION=\"0.0.22\" -o bindings/ruby/CMakeFiles/satsolverx.dir/libsatsolver_wrap.o -c /usr/src/packages/BUILD/satsolver-0.0.22/bindings/ruby/libsatsolver_wrap.c /usr/src/packages/BUILD/satsolver-0.0.22/bindings/ruby/libsatsolver_wrap.c: In function 'Repo_size': /usr/src/packages/BUILD/satsolver-0.0.22/bindings/ruby/libsatsolver_wrap.c:1793: error: '$self' undeclared (first use in this function) /usr/src/packages/BUILD/satsolver-0.0.22/bindings/ruby/libsatsolver_wrap.c:1793: error: (Each undeclared identifier is reported only once /usr/src/packages/BUILD/satsolver-0.0.22/bindings/ruby/libsatsolver_wrap.c:1793: error: for each function it appears in.)
and it continues on like this. You can see the full log at https://build.opensuse.org/package/live_build_log?arch=i586&package=libsatsolver&project=home%3Adimstar&repository=openSUSE_10.2
Any other ideas how else I could get a newer zypper as my preferred PM on 10.2 to run?
Dominique
Dominique, I am trying to backport libzypp for older distros in zypp:Backport. You can help me there!. For that error, the problem is 10.2 has a old swig, in OBS I solve this by backporting swig only for building.Actually there is a 10.2 satsolver there. But libzypp is another story ;-) What is your obs login? Duncan -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
On 3/20/2008 at 14:59, Duncan Mac-Vicar Prett
wrote: Dominique, I am trying to backport libzypp for older distros in zypp:Backport. You can help me there!. For that error, the problem is 10.2 has a old swig, in OBS I solve this by backporting swig only for building.Actually there is a 10.2 satsolver there. But libzypp is another story ;-)
Duncan, in my own playground (home:dimstar) I just compiled (so far only for openSUSE 10.2) libsatsolver (works indeed with a later swig) and libzypp compiled fine too. There is just a very awkward thing in the spec file, which I fail to understand: # %if 0%{?suse_version} # BuildRequires: hicolor-icon-theme rpm-devel update-desktop-files # %endif On what ground should any package require hicolor-icon-theme as a BuildRequires? Maybe somebody has an idea.. I did not find anything useful in this file rpm. anyhow, at the moment zypper for 10.2/x86_64 is being built and I should soon see the result of that... for i586 it's still scheduled... and if this works, I can soon start to fire up a VM and make some tests... for sure I will kill yast with it (as yast depends on libzypp.so.215 on a 10.2 installation... but as I wrote in my first mail, this is not a big issue (yet) for me... but of course if we want to offer it publically, this should be solved somehow to... so we'd need to update the whole yast stack on such a machine. Dominique -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
Dominique Leuenberger wrote:
On 3/20/2008 at 14:59, Duncan Mac-Vicar Prett
wrote: Dominique, I am trying to backport libzypp for older distros in zypp:Backport.
You can help me there!. For that error, the problem is 10.2 has a old swig, in OBS I solve this by backporting swig only for building.Actually there is a 10.2 satsolver there. But libzypp is another story ;-)
Duncan,
in my own playground (home:dimstar) I just compiled (so far only for openSUSE 10.2) libsatsolver (works indeed with a later swig) and libzypp compiled fine too.
Well, it was already compiling in zypp:Backport :-)
There is just a very awkward thing in the spec file, which I fail to understand:
# %if 0%{?suse_version} # BuildRequires: hicolor-icon-theme rpm-devel update-desktop-files # %endif
On what ground should any package require hicolor-icon-theme as a BuildRequires? Maybe somebody has an idea.. I did not find anything useful in this file rpm.
I think the package manager .desktop file.
anyhow, at the moment zypper for 10.2/x86_64 is being built and I should soon see the result of that... for i586 it's still scheduled... and if this works, I can soon start to fire up a VM and make some tests... for sure I will kill yast with it (as yast depends on libzypp.so.215 on a 10.2 installation... but as I wrote in my first mail, this is not a big issue (yet) for me...
but of course if we want to offer it publically, this should be solved somehow to... so we'd need to update the whole yast stack on such a machine.
Dominique
Thats why I have YaST:Backport as a repo that builds Factory packages on top of zypp:Backport. Once zypp:Backport compiles on 10.2, we can try to get YaST:Backport to compile too. Duncan -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
duncan,
On 3/21/2008 at 16:29, "Duncan Mac-Vicar P."
wrote: in my own playground (home:dimstar) I just compiled (so far only for openSUSE 10.2) libsatsolver (works indeed with a later swig) and libzypp compiled fine too. Well, it was already compiling in zypp:Backport :-)
Not quiet.. only libsatsolver was there.. libzypp (as stated above by me being built in my home: was not compiling successful..)
On what ground should any package require hicolor-icon-theme as a BuildRequires? Maybe somebody has an idea.. I did not find anything useful in this file rpm.
I think the package manager .desktop file.
Ok, anyhow it's a small rpm being added as build dependency at probably not worth to find out if it's really needed or not.
Thats why I have YaST:Backport as a repo that builds Factory packages on top of zypp:Backport. Once zypp:Backport compiles on 10.2, we can try to get YaST:Backport to compile too.
as you might have seen, zypper, libzypp and all the tools in zypp:backport are now succesfully compiled ;) (on Fedora 8, openSUSE 10.2 and 10.3; for SLE it's an issue with ruby vendor directory.. on SLE, it seems to install in site directory... I'll add a patch on the weekend for this). I'm already playing in yast:backport, some more progress is going on (slowly, as not to many workers are alive.. most seem to be on holiday). One thing we will have to adjust in the project configfile is to ignore yast2-devel and use yast2-devel-doc instead (or patch the spec to not make this difference for openSUSE < 1030. as it's set now) Dominique -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
On 3/20/2008 at 14:59, Duncan Mac-Vicar Prett
wrote: Dominique, I am trying to backport libzypp for older distros in zypp:Backport. You can help me there!. For that error, the problem is 10.2 has a old swig, in OBS I solve this by backporting swig only for building.Actually there is a 10.2 satsolver there. But libzypp is another story ;-)
What is your obs login?
Whoa... can't tell you how great zypper in newest version is... on the VPS (256MB) the zypper from 10.2 (0.6.5) always crashed me down, ran out of memory, was crazy slow... now I have a zypper 0.10.4 installed and I can install packages in a breeze... I commited my change to zypp:backport (but it's failing there.. so it can only be the older version of cmake that is missing... I'll try it out later this evening). Dominique -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
Gave the backport for 10.3 a try, but: Folgende Auswahl von Paket werden aktualisiert werden: zypper libzypp Paket wird installiert (neu): satsolver-tools Paket werden GELÖSCHT: yast2-ncurses lsb xorg-x11-libX11-ccache yast2-samba-server unclutter yast2-samba-client yast2-ntp-client x11-tools yast2-slp yast2-support yast2-storage yast2-iscsi-client yast2-online-update MozillaFirefox yast2-perl-bindings yast2-nis-client yast2-tv sax2-gui xtermset yast2-ldap-client yast2-users autoyast2 yast2-qt yast2 yast2-scanner yast2-sudo x11-input-synaptics nspluginwrapper numlockx xdmbgrd yast2-restore xlockmore yast2-pkg-bindings yast2-printer yast2-packager yast2-metapackage-handler yast2-country Schema werden GELÖSCHT: x11 x11_opt yast2_basis Gesamtgröße des Downloads: 18,8 M. Nach dem Vorgang wird 6,0 M freigegeben. Fortfahren? [ja/nein]: ^C Couldn't that be less "breaking" ? (just asking) Best regards Jan-Simon -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
Hello,
On 3/21/2008 at 14:12, Jan-Simon Möller
wrote:
Gave the backport for 10.3 a try, but:
Folgende Auswahl von Paket werden aktualisiert werden: zypper libzypp
Paket wird installiert (neu): satsolver-tools
Paket werden GELÖSCHT: yast2-ncurses lsb xorg-x11-libX11-ccache yast2-samba-server unclutter yast2-samba-client yast2-ntp-client x11-tools yast2-slp yast2-support yast2-storage yast2-iscsi-client yast2-online-update MozillaFirefox yast2-perl-bindings yast2-nis-client yast2-tv sax2-gui xtermset yast2-ldap-client yast2-users autoyast2 yast2-qt yast2 yast2-scanner yast2-sudo x11-input-synaptics nspluginwrapper numlockx xdmbgrd yast2-restore xlockmore yast2-pkg-bindings yast2-printer yast2-packager yast2-metapackage-handler yast2-country
Schema werden GELÖSCHT: x11 x11_opt yast2_basis
Gesamtgröße des Downloads: 18,8 M. Nach dem Vorgang wird 6,0 M freigegeben. Fortfahren? [ja/nein]: ^C
Couldn't that be less "breaking" ? (just asking)
A good question.. for now I guess we can only deal without yast in this case (to not loose all of yast I installed zypper and libzypp with --nodeps.. that leaves most of the yast modules running, except the package manager). To have it completely safe, we're also working on yast:backport. This repository bases on zypp:backport, which we now have in a state that it builds for 10.2 and 10.3. So the fun continues in those repositories. (zypp:backport for SLE will require a small patch which I'll probably add this weekend) Dominique -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
Tnx, for the good answer ;). Will check yast:backport. best regards Jan-Simon -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
participants (5)
-
Dominique Leuenberger
-
Duncan Mac-Vicar P.
-
Duncan Mac-Vicar Prett
-
Jan-Simon Möller
-
Michael Andres