Gentoo / Baselayout rollback / fails due to Immutable

[glowworm]

The latest sync has rolled back baselayout-vserver, it's details are now:

* sys-apps/baselayout-vserver
Available versions: 1.11.14-r4 ~1.11.15 ~1.12.1
Installed: 1.11.14-r5
Homepage: http://www.gentoo.org/
Description: Filesystem baselayout and init scripts

Unfortunately the original version wasn't emerged as a --oneshot or with an =1.11-rn in package.keywords in my VPS so today's emerge -puDv world has tried to roll the VPS's baselayout back.

Almost right through the emerge, during the install phase, the emerge fails with;

OSError: [Errno 1] Operation not permitted: '/etc/init.d/shutdown.sh'

Looking at the file I see;

# lsattr shutdown.sh
----ia------- shutdown.sh

Which explains the failure.

I'm sort of wondering what I will do now. Sure I could copy the file, remove the immutable bit and run the emerge again then put the original shutdown back and reset the immutable bit, but would that then cause my VPS to fail it's boot sequence like the ~86 version are known to do.

Anyone have any thoughts? Anyone running -r4 and rebooting without problems?

As it stands my VPS is halfway between two versions so I can't say for sure what will happen should it need to reboot.

Edit: Looking in genlop I see I have run the -r4 version before at the start of April. The -r5 version was emerged on May 26th. Based on this I feel happy about going back to the -r4 version using the steps I mention above, but still would like peoples opinions before I do (and lock the version into place in keywords)

[Rick]

contact support and we will un-chattr this file for you. this is one of the gentoo modifications we had to do in order for the os to operate under the vps architecture. if you look in the shutdown script you will see a command "touch",. This is how the vps is restarted after a reboot. Once your emerge is done we will re-chattr the file. If this becomes a big problem, I'll add a button in the web interface for this to be done on the gentoo admin's end.

[glowworm]

contact support and we will un-chattr this file for you. this is one of the gentoo modifications we had to do in order for the os to operate under the vps architecture. if you look in the shutdown script you will see a command "touch",. This is how the vps is restarted after a reboot. Once your emerge is done we will re-chattr the file. If this becomes a big problem, I'll add a button in the web interface for this to be done on the gentoo admin's end.

Hey Rick;

removing the immutable flag is a trivial thing. I had noticed the vps touches /reboot (from memory) rather than the normal methods when I looked at why it was turned immutable. A smart move by the way, even if unexpected!

I've done the change on all the files and put back the rapid versions. I was going to write how, but I'll leave it to support as a mistake could be messy if not done right.

As a hint to other Gentoo'ers -r4 is a known good version and recommended by the developer herd members I spoke to, the ~x86 versions are very flakey at the moment, born out by my recent testing on my home machine.