[ATrpms-users] Tux on ice

[Matthias Hensler]

Hi!

On Wed, Aug 01, 2007 at 09:28:08PM +0200, Axel Thimm wrote:
> On Wed, Aug 01, 2007 at 09:19:15PM +0200, Tako Schotanus wrote:
> > I just tried to upgrade and saw a lot of "tuxonice" packages that
> > look remarkably like "suspend2" packages.
> 
> The project was renamed.

Unfortunately not only the project was renamed, but most of the API
calls too. I struggled a bit and thought about continuing with
"suspend2" although "tuxonice" was inside. In the end I thought is was
cleaner to rename the packages as well.

> > And smart is trying to install all of them without touching the
> > suspend2 versions, is that okay?
> 
> I think the tuxonice package will automatically upgrade the old ones.
> Maybe you just need to allow smart to finish up the upgrade and the
> *-suspend2 packages will have been replaced by *-tuxonice?

I am not sure about smart. With "yum update" it should migrate to the
new packages automatically (at least it did for me):

kernel-suspend2 -> kernel-tuxonice
mkinitrd-suspend2 -> mkinitrd-tuxonice
hibernate-suspend2 -> hibernate-tuxonice
userui-suspend2 -> userui-tuxonice

As usual yum won't remove the old kernel if it is the one currently
running, but that's pretty ok. All new packages are fully backward
compatible to the old ones. You will still be able to install an older
kernel-suspend2 release if there is any need to.

> > It is also trying to install a kernel-PAE package, I imagine because it
> > can't understand why I don't have a kernel package? (I only have
> > kernel-suspend2 packages)
> 
> On the kernel-PAE issue I don't know, maybe upgrading bit by bit will
> show which package casues this?

That is one thing I never tried, always having the recent Fedora kernel
installed too. However kernel-tuxonice should provide all dependencies
the Fedora kernel does, but I will have a look at that.

> > Anyway, I was wondering what the "official" upgrade path is here.
> 
> The upgrade path should be that tuxonice replaces suspend2 whenever
> applicable. E.g. some packages didn't have to be touched yet (themes
> for example), so they were not renamed yet. But the new packages have
> compatibility hooks for the old naming, so the transitions shoiuld be
> smooth. If not, please file a bug :)

Only the themes-packages are untouched, everything else should
automatically upgrade. If not, do just like Axel suggests and file a bug
;)

Regards,
Matthias
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 307 bytes
Desc: not available
Url : http://lists.atrpms.net/pipermail/atrpms-users/attachments/20070802/76f737de/attachment.bin