Limbo repositories status update

[Ettore Di Giacinto]

Dear users and devs,

I'm writing you about a recent package upgrade introduced in the Sabayon Limbo repositories, which has been reported to cause massive breakage on multiple systems. 

The Limbo repository contains testing packages, the main repositories are not affected (sabayonlinux.org)

If you have that repository enabled in your system, we strongly advice to disable the Limbo repositories as for now and the time being, we are deeply sorry  for the inconvenience caused. 

We are already investigating the issue, stay tuned.

Ettore, on behalf of the Sabayon team

[Sławomir Nizio]

It's deliberately locked though in a way that equo refuses updating from
it, so you should be safe.

Hopefully nobody updated in the short period when it was unlocked.

> which has been reported to cause massive breakage on multiple systems.

In the same way I hope it was only my VM, Joost's system and perhaps
some devel ones.

[Joost Ruis]

Attached is the log.

I can't chroot into the system no more, but I was able to readelf and found something interesting.

sabayon /run/media/sabayonuser/d10519b1-2430-4dbe-9c46-75b301855b0a/lib64 # readelf libc.so.6 -h
ELF Header:
  Magic:   7f 45 4c 46 01 01 01 03 00 00 00 00 00 00 00 00 
  Class:                             ELF32
  Data:                              2's complement, little endian
  Version:                           1 (current)
  OS/ABI:                            UNIX - GNU
  ABI Version:                       0
  Type:                              DYN (Shared object file)
  Machine:                           Intel 80386
  Version:                           0x1
  Entry point address:               0x1aa80
  Start of program headers:          52 (bytes into file)
  Start of section headers:          2009872 (bytes into file)
  Flags:                             0x0
  Size of this header:               52 (bytes)
  Size of program headers:           32 (bytes)
  Number of program headers:         12
  Size of section headers:           40 (bytes)
  Number of section headers:         62
  Section header string table index: 61

--
You received this message because you are subscribed to the Google Groups "Sabayon Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sabayon-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sabayon-dev/f7134f84-09fd-58a2-e4c1-593127fbbb57%40sabayon.org.

[Sławomir Nizio]

I introduced an automatic migration using app-portage/unsymlink-lib from
Gentoo, it worked so I unlocked the repository.

Tested configurations:
- installation with old layout that actually needed the migration - one
tested VM,
- plus test on some (new?) configuration done by Joost.

[Not to mention "synthetic" checks.]

Still to check:
- update with Rigo, preferably when the distribution is on the old
layout and needs migration,
- test on a system that already uses the new layout (installed from a
-dev ISO; not sure if recent non-dev apply too).

I don't expect any problems but the more testing on various
configurations, the better.



What to pay attention to:
when update starts, first three packages to install or update must be
these, in this order:
- app-portage/unsymlink-lib,
- sys-apps/sabayon-lib-migration,
- sys-apps/sabayon-lib-migration-check.

If it's any different, please report it, and include output of equo
upgrade! In this case glibc wouldn't be broken this time due to the
added checks, but something else might break causing from none to a lot
of breakage. I don't expect it to happen but it's good to have an eye on
it during initial testing.


How to check whether you are on the new layout or not (I avoid using the
word "profile" here because one that's printed by eselect does not
really apply unless you use Portage):
- if /lib and /usr/lib are symlinks to lib64, you are likely on the old
layout,
- if they are real directories, you are likely on the new layout.

Quality reports should include the information whether it's the former
or latter. Include just output of the command: ls -ld /lib /usr/lib.


Oh and look at the notice board, message with title "Profile change."


Looking ahead for your feedback!


[for repo maintainers, see in build.git the TODO list in a commit
message to remember about the notice and settings needed in the other
repositories when it's ready]

[Stuart Rose]

> What to pay attention to:
when update starts, first three packages to install or update must be
these, in this order:
- app-portage/unsymlink-lib,
- sys-apps/sabayon-lib-migration,

- sys-apps/sabayon-lib-migration-check.

Is the order something you can tell from from an equo up --pretend ?  Just so I can double check that before proceeding.

--
You received this message because you are subscribed to the Google Groups "Sabayon Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sabayon-dev...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/sabayon-dev/376a1772-71bc-491c-959c-5a3c7c653d65%40sabayon.org.

[Sławomir Nizio]

> Is the order something you can tell from from an equo up --pretend ?
> Just so I can double check that before proceeding.

Probably yes, but I'm not sure (applies also to --ask).

[Sławomir Nizio]

> Still to check:
> - update with Rigo, preferably when the distribution is on the old
> layout and needs migration,

Tested (starting point was old layout).

> - test on a system that already uses the new layout (installed from a
> -dev ISO; not sure if recent non-dev apply too).

Tested using recent Sabayon_Linux_DAILY_amd64_Xfce.iso (the layout was new).

So according to my checks, it's ready to reach main repository but

> (…) the more testing on various
> configurations, the better.

And a reminder:

> [for repo maintainers, see in build.git the TODO list in a commit
> message to remember about the notice and settings needed in the other
> repositories when it's ready]

I'll paste it below.

> Checklist when it is done in main and weekly:
> - copy the 'news' notice,
> - copy packages.db.critical.