Mailinglist Archive: opensuse-factory (661 mails)

< Previous Next >
Re: [opensuse-factory] Builds not against current perl 5.10.1
  • From: Ladislav Slezak <lslezak@xxxxxxx>
  • Date: Thu, 17 Dec 2009 10:28:46 +0100
  • Message-id: <4B29F9CE.5060002@xxxxxxx>
On 17.12.2009 09:55, Ludwig Nussel wrote:
Gerald Pfeifer wrote:
[...]
Why do we, in general, have so many strict version dependencies, as
opposed to at least >= ? Looking at the troubles with factory updates
in the last half year, this has been constantly hitting us across the
board.

The strict dependency requires the same perl version which was used
at the yast2-core build time, this is safer. Using >= could cause problems when
new perl is not binary compatible with old version.

yast2-core has files in /usr/lib/perl5/vendor_perl/5.10.0. I suppose
perl 5.10.1 does not load files from the 5.10.0 directory.

Um, in which version? Here it is OK (I'm running Factory + Yast:HEAD):

# rpm -ql yast2-core | grep perl
/usr/lib/perl5/vendor_perl/5.10.1/YaST
/usr/lib/perl5/vendor_perl/5.10.1/YaST/SCRAgent.pm
/usr/lib/perl5/vendor_perl/5.10.1/x86_64-linux-thread-multi/auto/ycp
/usr/lib/perl5/vendor_perl/5.10.1/x86_64-linux-thread-multi/auto/ycp/.packlist
/usr/lib/perl5/vendor_perl/5.10.1/ycp.pm
/var/adm/perl-modules/yast2-core
# rpm -q yast2-core perl
yast2-core-2.18.19-22.6.x86_64
perl-5.10.1-2.9.x86_64

Anyway, as Gerald has written, if yast2-core has files in 5.10.0
directory is should require perl = 5.10.0 so the problem should
not happen (unless you manually break the package dependency).

The problem was in yast2-perl-bindings package, but has been fixed already.

--

Best Regards

Ladislav Slez√°k
Yast Developer
------------------------------------------------------------------------
SUSE LINUX, s.r.o. e-mail: lslezak@xxxxxxx
Lihovarsk√° 1060/12 tel: +420 284 028 960
190 00 Prague 9 fax: +420 284 028 951
Czech Republic http://www.suse.cz/
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx

< Previous Next >