* Cristian Rodríguez [11-25-09 11:10]:

On 25/11/09 12:55, Patrick Shanahan wrote:

...

My need for spamassassin is crippling my Factory system.

Wait until packages get fixed and built.

11:03 wahoo:~ > rpm -qi perl-spamassassin Name : perl-spamassassin Relocations: (not relocatable) Version : 3.2.5 Vendor: openSUSE Release : 29.1 Build Date: Mon 26 Oct 2009 03:17:01 AM EDT 26 October ??? -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

I am running 11.2, and it exhibits the same problem. On 11/25/09 11:09 AM, Dave Plater wrote:

On 11/25/2009 05:55 PM, Patrick Shanahan wrote:

...

I am currently unable to upgrade to perl-5.10.1 because current Factory builds of perl-spamassassin and apache2-mod_perl require perl-5.10.0.

perl-5.10.0-72.5.x86_64 spamassassin-3.2.5-29.1.x86_64 perl-spamassassin-3.2.5-29.1.x86_64 apache2-mod_perl-2.0.4-40.92.x86_64

current yast2 requires perl-5.10.1 yast2-2.18.25-2.5.x86_64 yast2-core-2.18.19-2.3.x86_64

10:50 wahoo:~ > yast2 users Error loading language plugin /usr/lib64/YaST2/plugin/libpy2lang_perl.so: libperl.so: cannot open shared object file: No such file or directory Error while creating client module users

My need for spamassassin is crippling my Factory system.

Solution?

tks,

I see apache2-mod_perl has failed it's build in factory standard and spamassasin as well, so I suppose you'll have to wait until someone fixes them or try 11.2. Regards Dave P

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

On 25/11/09 13:12, Patrick Shanahan wrote:

It doesn't work :^(

Yeah, it may not work, patience is a virtue, several packages fail to build due to perl upgrade, it will take some time to fix them. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

On 25.11.2009 21:38, Patrick Shanahan wrote:

* Cristian Rodríguez [11-25-09 15:26]:

...

On 25/11/09 13:12, Patrick Shanahan wrote:

...

It doesn't work :^(

Yeah, it may not work, patience is a virtue, several packages fail to build due to perl upgrade, it will take some time to fix them.

Patience will persevere, but explanation softens the hurt :^)

tks for that.

Still wondering the argument that yast is not broken, itself, with its failure to execute having the correct requirements present. Namely that yast2-core requires perl = 5.10.0, which is present and yast fails.

I guess it fails because of yast2-perl-bindings, this package doesn't have versioned dependency (as yast2-core): # rpm -q --requires yast2-core | grep perl perl = 5.10.1 /usr/bin/perl # rpm -q --requires yast2-perl-bindings | grep perl perl perl(Locale::gettext) libperl.so()(64bit) # rpm -q yast2-core yast2-perl-bindings yast2-core-2.18.19-22.3.x86_64 yast2-perl-bindings-2.18.0-4.2.x86_64 I'll fix that... -- Best Regards Ladislav Slezák Yast Developer ------------------------------------------------------------------------ SUSE LINUX, s.r.o. e-mail: lslezak@suse.cz 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@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

On Thu, 26 Nov 2009, Ladislav Slezak wrote:

I guess it fails because of yast2-perl-bindings, this package doesn't have versioned dependency (as yast2-core):

# rpm -q --requires yast2-core | grep perl perl = 5.10.1 /usr/bin/perl # rpm -q --requires yast2-perl-bindings | grep perl perl perl(Locale::gettext) libperl.so()(64bit)

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. Gerald -- Dr. Gerald Pfeifer gp@novell.com | SUSE Linux Products GmbH Director Product Management | HRB 16746 (AG Nuremberg) SUSE Linux Enterprise, openSUSE, Appliances | GF Markus Rex -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

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@suse.cz 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@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org