Created attachment 2192 [details]
report.bug.zip

First thing I notice is that guile1.8 needs have a provides added for guiel.

* promoting guile1.8-1.8.8-11.mga2.x86_64 because of conflict above
* installed lib64guile17-1.8.7-5.mga1.x86_64 is conflicting because of unsatisfied guile[== 1.8.7]
* promoting lib64guile17-1.8.8-11.mga2.x86_64 because of conflict above
* installed aisleriot-2.32.1-2.mga1.x86_64 is conflicting because of unsatisfied guile
* installed gnucash-2.4.5-1.mga1.x86_64 is conflicting because of unsatisfied guile[>= 1.6]

It then selects guile-2.0.5-4.mga2.x86_64 to satisfy the libraries required
for aislerot, but guile coflicts with guile1.8.

Either guile1.8 needs to have a provides added, so it provides guile,
or guile1.8 needs to be removed so that guile will be used.

CC: (none) => davidwhodgins
Source RPM: (none) => guile1.8-1.8.8-11.mga2.src.rpm

In addition, the package bsf needs to be added to the iso imaage,
as the lack of it is causing a chain of packages to be unselected,
starting with bsh.

mitya, please see comment 2

CC: (none) => mitya

The guile and guile1.8 packages do indeed conflict; they contain a command-line interpreter and corresponding man pages. For applications using Guile as a scripting engine, these should not be required anymore. What should be really required is guile[1.8]-runtime and libguile{17,2.0_22} - these are fully parallel installable. guile[1.8]-runtime has been recently split off the main guile[1.8] package, just to allow parallel installation of packages that require different versions of Guile. In fact, requiring libguile{...} is enough, because it will pull guile{...}-runtime package itself.

Is there any progress for this? 

Sorry to ping so soon but we are short of time.

Still present in RC release - http://dl.dropbox.com/u/4147101/DSC01048.JPG

Created attachment 2231 [details]
report.bug.gz

This resulted in over 1000 packages not being upgraded.

Removing guile before upgrading removes aisleriot, gnome-games, gnucash, lib64gnucash0 along with lib64guile17 and guile itself.

Doing so allowed the upgrade to complete.

OK, after I added a "Provides: guile = %{version}-%{release}" to guile1.8, build and upgraded it (building it failed in a non-up-to-date Mageia Cauldron release at the installation stage, and required some packages in Cauldron), I am getting this when trying to upgrade it with gnucash and GNOME AiselRiot installed:

<SHELL>

[root@localhost ~]# urpmi --auto-select
The following packages have to be removed for others to be upgraded:
aisleriot-3.4.1-1.mga2.i586
 (due to missing libguile-2.0.so.22)
guile-2.0.5-4.mga2.i586
 (due to conflicts with guile1.8[>= 1.8.8-7])
guile-runtime-2.0.5-4.mga2.i586
 (due to conflicts with guile[< 2.0.5-2])
libcdio_cdda0-0.82-3.mga1.i586
 (due to conflicts with libudf0-0.83-1.mga2.i586)
libguile2.0_22-2.0.5-4.mga2.i586
 (due to unsatisfied guile-runtime == 2.0.5-4.mga2)
libmesaglut3-devel-7.10.2-4.mga1.i586
 (due to unsatisfied libmesaglut3 == 7.10.2-4.mga1)
libpoppler-glib6-0.16.5-1.mga1.i586
 (due to unsatisfied poppler-gir0.16 >= 0.16.5) (y/N) n

</SHELL>

This is in a i586 Virtual Box virtual machine that was upgrade from 1 to Cauldron with --keep. So it seems that aisleriot cannot be installed along with gnucash in this case. Should we rebuild it against guile-2.0? 

Regards,

-- Shlomi Fish

CC: (none) => shlomif

Shlomi,

Beginning with guile-2.0.5-2 and guile1.8-1.8.8-10, it is not longer needed for gnucash, lilypond, aisleriot etc. to require "guile" or "guile1.8" (these packages do conflict with each other). It is only needed to require libguile2.0_22 or libguile17, usually it's an automatic dependency, and these packages do not conflict. Corresponding guile-runtime (also nonconflicting packages) will be pulled automatically.

Hence, it is safe to remove guile1.8 from Requires: of gnucash and lilypond.

(In reply to comment #11)
> Shlomi,
> 
> Beginning with guile-2.0.5-2 and guile1.8-1.8.8-10, it is not longer needed for
> gnucash, lilypond, aisleriot etc. to require "guile" or "guile1.8" (these
> packages do conflict with each other). It is only needed to require
> libguile2.0_22 or libguile17, usually it's an automatic dependency, and these
> packages do not conflict. Corresponding guile-runtime (also nonconflicting
> packages) will be pulled automatically.
> 
> Hence, it is safe to remove guile1.8 from Requires: of gnucash and lilypond.

Thanks, I'll look into preparing updated packages of those.

Regards,

-- Shlomi Fish

(In reply to comment #12)
> (In reply to comment #11)
> > Shlomi,
> > 
> > Beginning with guile-2.0.5-2 and guile1.8-1.8.8-10, it is not longer needed for
> > gnucash, lilypond, aisleriot etc. to require "guile" or "guile1.8" (these
> > packages do conflict with each other). It is only needed to require
> > libguile2.0_22 or libguile17, usually it's an automatic dependency, and these
> > packages do not conflict. Corresponding guile-runtime (also nonconflicting
> > packages) will be pulled automatically.
> > 
> > Hence, it is safe to remove guile1.8 from Requires: of gnucash and lilypond.
> 
> Thanks, I'll look into preparing updated packages of those.
> 
> Regards,
> 
> -- Shlomi Fish

OK: bad news. Apparently, the %triggerin -- slib of the guile-1.8 package assumes that guile is in /usr/bin/guile which is guile-2.0 in my case. Therefore, slib is not available there for gnucash to use. When I tried adding a symbolic link manually, I got this crash:

<<<<
shlomif@telaviv1:~$ gnucash
Backtrace:
In unknown file:
   ?: 0* [primitive-load-path "slib/guile.init"]
In /usr/share/guile/1.8/slib/guile.init:
 902: 1* [slib:load "/usr/share/require"]
 554: 2  [save-module-excursion #<procedure #f ()>]
In unknown file:
   ...
   ?: 3  [dynamic-wind #<procedure #f ()> #<procedure #f ()> #<procedure #f ()>]
   ?: 4* [#<procedure #f ()>]
In /usr/share/guile/1.8/slib/guile.init:
 557: 5* (let* ((errinfo #)) (if (and errinfo #) (apply throw errinfo)))
 560: 6  (if (and errinfo (catch # # #)) (apply throw errinfo))
In unknown file:
   ...
   ?: 7  [throw]

/usr/share/guile/1.8/slib/guile.init:560:10: In procedure open-file in expression (if (and errinfo #) (apply throw errinfo)):
/usr/share/guile/1.8/slib/guile.init:560:10: No such file or directory: "/usr/share/require"
shlomif@telaviv1:~$ 
>>>>

So I don't know what to do in order to make gnucash, lilypond and GNOME AisleRiot play nicely together. If anyone has any suggestions or leads, they will be appreciated. But it seems the guile developers are making life hell on the downstream packagers by breaking backward compatibility that way.

Regards,

-- Shlomi Fish

Shlomi,

I'll see two solutions here, both quite viable:

1) we can force slib build during guile RPM build. This assumes BuildRequires: slib for guile and guile1.8. The result will be guile-slib and guile1.8-slib packages, and gnucash will have to require guile1.8-slib instead of slib. It's a hack but it's an easier way;
2) we can make guile and guile1.8 fully parallel installable with the help of alternatives mechanism. This will solve all our problems in one, but will cause us more PITA now.

I'll ask everyone to assess all the pros and cons of each scenario.

Hi Dimitri,

(In reply to comment #14)
> Shlomi,
> 
> I'll see two solutions here, both quite viable:
> 
> 1) we can force slib build during guile RPM build. This assumes BuildRequires:
> slib for guile and guile1.8. The result will be guile-slib and guile1.8-slib
> packages, and gnucash will have to require guile1.8-slib instead of slib. It's
> a hack but it's an easier way;

Like I said on IRC I'm in favour of solution #1.

Regards,

-- Shlomi Fish

(In reply to comment #13)
> (In reply to comment #12)
> > (In reply to comment #11)
> > > Shlomi,
> > > 
> > > Beginning with guile-2.0.5-2 and guile1.8-1.8.8-10, it is not longer needed for
> > > gnucash, lilypond, aisleriot etc. to require "guile" or "guile1.8" (these
> > > packages do conflict with each other). It is only needed to require
> > > libguile2.0_22 or libguile17, usually it's an automatic dependency, and these
> > > packages do not conflict. Corresponding guile-runtime (also nonconflicting
> > > packages) will be pulled automatically.
> > > 
> > > Hence, it is safe to remove guile1.8 from Requires: of gnucash and lilypond.
> > 
> > Thanks, I'll look into preparing updated packages of those.
> > 
> > Regards,
> > 
> > -- Shlomi Fish
> 
> OK: bad news. Apparently, the %triggerin -- slib of the guile-1.8 package
> assumes that guile is in /usr/bin/guile which is guile-2.0 in my case.
> Therefore, slib is not available there for gnucash to use. When I tried adding
> a symbolic link manually, I got this crash:
> 
> <<<<
> shlomif@telaviv1:~$ gnucash
> Backtrace:
> In unknown file:
>    ?: 0* [primitive-load-path "slib/guile.init"]
> In /usr/share/guile/1.8/slib/guile.init:
>  902: 1* [slib:load "/usr/share/require"]
>  554: 2  [save-module-excursion #<procedure #f ()>]
> In unknown file:
>    ...
>    ?: 3  [dynamic-wind #<procedure #f ()> #<procedure #f ()> #<procedure #f
> ()>]
>    ?: 4* [#<procedure #f ()>]
> In /usr/share/guile/1.8/slib/guile.init:
>  557: 5* (let* ((errinfo #)) (if (and errinfo #) (apply throw errinfo)))
>  560: 6  (if (and errinfo (catch # # #)) (apply throw errinfo))
> In unknown file:
>    ...
>    ?: 7  [throw]
> 
> /usr/share/guile/1.8/slib/guile.init:560:10: In procedure open-file in
> expression (if (and errinfo #) (apply throw errinfo)):
> /usr/share/guile/1.8/slib/guile.init:560:10: No such file or directory:
> "/usr/share/require"
> shlomif@telaviv1:~$ 
> >>>>
> 
> So I don't know what to do in order to make gnucash, lilypond and GNOME
> AisleRiot play nicely together. If anyone has any suggestions or leads, they
> will be appreciated. But it seems the guile developers are making life hell on
> the downstream packagers by breaking backward compatibility that way.
> 
> Regards,
> 
> -- Shlomi Fish

libguile1.8 is needed to build lilypond.

CC: (none) => thomas

guile1.8 isn't needed by lilypond. I deleted all packages that have the name guile in it and the attachment shows what lilypond automatically pulls in. Guile1.8 isn't among them, only the libraries and runtime.

Created attachment 2294 [details]
lilypond automatically pull-ins

Upgrade completed with gnome-games and aisleriot so closing as fixed, thanks.

$ rpm -qa | grep guile
guile-runtime-2.0.5-4.mga2
guile-2.0.5-4.mga2
lib64guile2.0_22-2.0.5-4.mga2
guile1.8-runtime-1.8.8-11.mga2
lib64guile17-1.8.8-11.mga2

$ rpm -q gnome-games
gnome-games-3.4.1-1.mga2

$ rpm -q aisleriot
aisleriot-3.4.1-1.mga2

Status: NEW => RESOLVED
Resolution: (none) => FIXED

So I guess not quite fixed in prerelease 2 DVD (2nd set)

https://bugs.mageia.org/show_bug.cgi?id=5942#c6

Status: RESOLVED => REOPENED
Resolution: FIXED => (none)

Please use 3rd set

Please see bug 5969

Appears to still be current using 3rd set. See bug 5969

yep still valid, but the upgrade continue here, without windows errors (only in the ddebug)

Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

*** Bug 5969 has been marked as a duplicate of this bug. ***

I think, in its more minor form as seen in bug 5969 this is still valid.

I'm not sure we should keep it open though.

WDYT?

I think this problem may be the cause of bug#7283

Add one more user stuck on this one.  I want to install both lilypond and gnucash.  Because my wife is a composer, I need lilypond more than I need gnucash.

CC: (none) => rmriches

Closing. More precise bug reports have been opened since about those problems.

Status: REOPENED => RESOLVED
CC: (none) => stormi
Resolution: (none) => OLD