Dependency loop: pwdutils (%post) -> libcom_err -> pwdutils
Hello, # poldek -r some_empty_dir -i install libcom_err-1.41.5-1.i686 (...) 50:pwdutils ### [ 77%] /usr/sbin/pwconv: error while loading shared libraries: libcom_err.so.2: cannot open shared object file: No such file or directory error: %post(pwdutils-3.1.3-5.i686) scriptlet failed, exit status 127 How to fix it? Drop this %post scriplet? Or modify some dependencies? -- Paweł ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: xz vs. lzma
On Thu, 18 Jun 2009, Pawel Golaszewski wrote: > On Wed, 17 Jun 2009, Paweł Zuzelski wrote: > > xz has replaced lzma, "Provides/Obsoletes" it and install symlink lzma > > that points to xz. Unfortunatelly these programs are not compatibile. xz > > is unable to decompress file compressed with lzma. > > First of all - ask xz developers what they will do. Maybe it's just a bug. > If not - we should do something about that. #tukaani 09:23 < pawelz> Hello 09:24 < pawelz> New xz is unable to decompress file compressed using lzma. Is it a bug or feature? :) 09:26 < pawelz> Are you going to fix it? Or just file format has changed and new versions won't be compatibile with older ones?? 11:00 <@Larhzu> Hello 11:00 <@Larhzu> You got luck, I've been away over a week. 11:01 <@Larhzu> pawelz: How was that .lzma file created? XZ Utils supports all .lzma files that the lzma tool from LZMA Utils 4.32.x can create. 11:02 <@Larhzu> But there are types of .lzma files that are not supported by XZ Utils but are supported by LZMA Utils. Such files should be very rare. 11:03 < pawelz> Larhzu: I've created it using: tar acvf file.tar.lzma directory 11:04 <@Larhzu> What does lzma --version say? 11:04 < pawelz> Larhzu: ftp://distfiles.pld-linux.org/distfiles/by-md5/6/4/64c8be7214ca41b98180e7e81844cf10/telak-0.5.tar.lzma 11:06 <@Larhzu> pawelz: That's in an old development version of the new file format. You can decompress it only if you know what *exact* version the development code was used to create the file. 11:06 <@Larhzu> pawelz: In other words, someone made a major mistake by using unstable file format. (...) 11:10 <@Larhzu> They are easy to detect, the first byte is 0xFF. So it was our mistake, that this version was available in PLD. -- Regards, Paweł Zuzelski ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
rpm --root is broken (?)
WTF?
[r...@davabel ~]# mkdir /root/test
[r...@davabel ~]# rpm --root=/root/test --initdb
[r...@davabel ~]# poldek -nth --noask --root=/root/test -i rpm
(...)
[r...@davabel ~]# chroot /root/test
/bin/sh: No controlling tty (open /dev/tty: No such file or directory)
/bin/sh: warning: won't have full job control
/bin/sh: /etc/kshrc[22]: id: not found
/bin/sh: /etc/kshrc[22]: [: 0: unexpected operator/operand
And now rpm database is not available
[r...@davabel /]$ rpm -qa
error: cannot open Packages index using db3 - No such file or directory (2)
error: cannot open Packages database in /var/lib/rpm
[r...@davabel /]$ ^D
Outside chroot everything is OK
[r...@davabel ~]# rpm --root=/root/test -qa | head -n1
ldconfig-2.10.1-5.i686
But lets try to rename chroot dir:
[r...@davabel ~]# mv test test2
[r...@davabel ~]# rpm --root=/root/test -qa
Freeing read locks for locker 0x21: 4927/3082521200
Freeing read locks for locker 0x23: 4927/3082521200
error: cannot open Packages index using db3 - No such file or directory (2)
error: cannot open Packages database in /root/test2/var/lib/rpm
[r...@davabel ~]# ^D
[r...@davabel ~]# strace -eopen -f rpm --root=/root/test2 -qa
(...)
open("/root/test2/var/lib/rpm/Packages", O_RDONLY|O_LARGEFILE) = 3
open("/root/test/var/lib/rpm/Packages", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No
such file or directory)
error: cannot open Packages index using db3 - No such file or directory (2)
error: cannot open Packages database in /root/test2/var/lib/rpm
My system is PLD th i686
[r...@davabel ~]# rpm -qa | grep rpm
rpm-4.5-21.i686
rpm-debuginfo-4.5-16.i686
rpm-php-pearprov-4.5-21.i686
rpm-build-4.5-21.i686
rpm-lib-4.5-21.i686
rpm-pythonprov-4.5-21.i686
rpm-debuginfo-4.5-14.i686
rpm-build-tools-4.4.9-17.noarch
rpm-whiteout-1.26-1.noarch
rpm-specdump-0.3-6.i686
python-rpm-4.5-21.i686
rpm-perlprov-4.5-21.i686
rpmorphan-1.4-1.noarch
rpm-base-4.5-21.i686
rpm-utils-4.5-21.i686
rpmlist-1.5-1.noarch
rpm-build-macros-1.520-2.noarch
rpm-utils-perl-4.5-21.i686
rpm-devel-4.5-21.i686
rpm-static-4.5-21.i686
rpm-javaprov-4.5-21.i686
[r...@davabel ~]# rpm -qa | grep poldek
poldek-libs-0.30-0.20080820.23.30.i686
poldek-0.30-0.20080820.23.30.i686
python-poldek-0.30-0.20080820.23.30.i686
[r...@davabel ~]# rpm -qa | grep db4.7
db4.7-4.7.25-5.i686
db4.7-static-4.7.25-5.i686
db4.7-devel-4.7.25-5.i686
--
Paweł Zuzelski
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: xz vs. lzma
On Thu, 18 Jun 2009, Paweł Zuzelski wrote: > > > xz has replaced lzma, "Provides/Obsoletes" it and install symlink > > > lzma that points to xz. Unfortunatelly these programs are not > > > compatibile. xz is unable to decompress file compressed with lzma. > > First of all - ask xz developers what they will do. Maybe it's just a > > bug. If not - we should do something about that. > #tukaani > > 09:23 < pawelz> Hello > 09:24 < pawelz> New xz is unable to decompress file compressed using lzma. Is > it a bug or feature? :) > 09:26 < pawelz> Are you going to fix it? Or just file format has changed and > new versions won't be compatibile with older ones?? > 11:00 <@Larhzu> Hello > 11:00 <@Larhzu> You got luck, I've been away over a week. > 11:01 <@Larhzu> pawelz: How was that .lzma file created? XZ Utils supports > all .lzma files that the lzma tool from LZMA Utils 4.32.x can create. > 11:02 <@Larhzu> But there are types of .lzma files that are not supported by > XZ Utils but are supported by LZMA Utils. Such files should be very rare. > 11:03 < pawelz> Larhzu: I've created it using: tar acvf file.tar.lzma > directory > 11:04 <@Larhzu> What does lzma --version say? > 11:04 < pawelz> Larhzu: > ftp://distfiles.pld-linux.org/distfiles/by-md5/6/4/64c8be7214ca41b98180e7e81844cf10/telak-0.5.tar.lzma > 11:06 <@Larhzu> pawelz: That's in an old development version of the new file > format. You can decompress it only if you know what *exact* version the > development code was used to create the file. > 11:06 <@Larhzu> pawelz: In other words, someone made a major mistake by using > unstable file format. > (...) > 11:10 <@Larhzu> They are easy to detect, the first byte is 0xFF. > > So it was our mistake, that this version was available in PLD. major pita... So... I think we should leave xz in current state. Old lzma should be placed in "supported" or so. With binary executable name changed (lzma_old_broken_format ?). even... lzma should be some script that tries to detect format and uses proper version. -- pozdr. Paweł Gołaszewski jid:bluesjabbergdapl -- If you think of MS-DOS as mono, and Windows as stereo, then Linux is Dolby Pro-Logic Surround Sound with Bass Boost and all the music is free.___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: xz vs. lzma
On Thu, 18 Jun 2009, Pawel Golaszewski wrote: > even... lzma should be some script that tries to detect format and uses > proper version. and makes sure that old version is never used for compression. -- Paweł ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: xz vs. lzma
On Thursday 18 June 2009 13:32:25 Paweł Zuzelski wrote: > On Thu, 18 Jun 2009, Pawel Golaszewski wrote: > > even... lzma should be some script that tries to detect format and uses > > proper version. > > and makes sure that old version is never used for compression. patch it to not support compression? :) and release such version in all distro series (ac, ti, th) -- glen ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: xz vs. lzma
On Wednesday 17 of June 2009, Paweł Zuzelski wrote: > xz has replaced lzma, "Provides/Obsoletes" it and install symlink > lzma that points to xz. Unfortunatelly these programs are not > compatibile. xz is unable to decompress file compressed with lzma. > > It breaks build process of some packages (see > http://buildlogs.pld-linux.org/index.php?dist=th&arch=athlon&ok=0&name=tela >k&id=eae6a73b-58d5-4567-8085-18102acbaa87) > > Is it bug in xz that can be easily fixed? If no (imo) xz must not > Obsoletes/Provides lzma and it should be possible to install xz and > lzma on the same system. That had to be "user fault". We used lzma but with old compression format mode in rpm for example. IMO just repackage that tarball and be done with it. -- Arkadiusz MiśkiewiczPLD/Linux Team arekm / maven.plhttp://ftp.pld-linux.org/ ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
PPC: libmpeg2.spec
Hi, mpeg2dec.spec is now obsolete due to libmpeg2.spec superseding it. The problem is libmpeg2 won't build on PPC due to some AltiVec problems. Could any PPC owner look into and fix it so we can release updated gstreamer plugins? -- Patryk Zawadzki ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
