baselayout and openrc issues from inside a vserver
I've been putting off the openrc upgrade on my vserver account for some
time and think it's finally come around to bite me.
Here's the info.
I don't run the host OS only the vserver. The latest changes to profiles
depreciated my old profile last night so I updated. I'm now using
/usr/portage/profiles/default/linux/x86/vserver as eic-sync suggested.
The issue appears to be that baselayout-vserver has been masked by
/usr/portage/profiles/package.mask with this message.
- sys-apps/baselayout-vserver-1.11.14-r4 (masked by: package.mask)
/usr/portage/profiles/package.mask:
# mask pending removal
# Benedikt Böhm <hollow@gentoo.org> (10 Jan 2009)
# baselayout-vserver is unmaintained and obsoleted by
# baselayout-2/openrc. please upgrade. removal in 30 days.
That makes sense, but my vserver profile has masked baselayout-2.
!!! One of the following masked packages is required to complete your
request:
- sys-apps/baselayout-2.0.0 (masked by: package.mask)
/usr/portage/profiles/targets/vserver/package.mask:
# Benedikt Boehm <hollow@gentoo.org>
# Mask baselayout in vservers. Use baselayout-vserver instead!
I suspect I need to change my profile to something that isn't vserver,
but I haven't been able to find any docs or post of how to proceed.
kashani
01-19-2009, 06:00 PM
Nick Cunningham
baselayout and openrc issues from inside a vserver
2009/1/19 kashani <kashani-list@badapple.net>
* * * *I've been putting off the openrc upgrade on my vserver account for some time and think it's finally come around to bite me.
Here's the info.
I don't run the host OS only the vserver. The latest changes to profiles depreciated my old profile last night so I updated. I'm now using /usr/portage/profiles/default/linux/x86/vserver as eic-sync suggested. The issue appears to be that baselayout-vserver has been masked by /usr/portage/profiles/package.mask with this message.
# Mask baselayout in vservers. Use baselayout-vserver instead!
I suspect I need to change my profile to something that isn't vserver, but I haven't been able to find any docs or post of how to proceed.
kashani
Or, you can just unmask the baselayout package and stay with the vserver profile. Add the packages needed to /etc/portage/package.unmask. You will probably have to add them to /etc/portage/package.keywords aswell as i think they are still ~ARCH only.
If you not sure whats needed then emerge the program autounmask and that will add all the entries (including any dependancies) automatically.
- Nick
01-19-2009, 07:39 PM
Peter Alfredsen
baselayout and openrc issues from inside a vserver
On Mon, 19 Jan 2009 10:28:05 -0800
kashani <kashani-list@badapple.net> wrote:
> I've been putting off the openrc upgrade on my vserver
> account for some time and think it's finally come around to bite me.
Our vserver team had this to say about it on -dev a few days ago.
> > - - baselayout-2/openrc isn't stable yet, in fact it's even masked
> > in profiles/targets/vserver/package.mask
>
> i don't care. baselayout-vserver is a hack, the vserver profiles are
> deprecated since ages (although i think the restructuring revived
> them), and the vserver team (that's only me currently) doesn't
> support anything else beside openrc.
>
> Greets,
> Bene
So, you should probably migrate to the normal profiles as recommended
by the vserver howto:
01-19-2009, 07:39 PM
Peter Alfredsen
baselayout and openrc issues from inside a vserver
Whoops, missed the link to the vserver howto:
http://www.gentoo.org/proj/en/vps/vserver-howto.xml
01-19-2009, 08:46 PM
kashani
baselayout and openrc issues from inside a vserver
Peter Alfredsen wrote:
On Mon, 19 Jan 2009 10:28:05 -0800
kashani <kashani-list@badapple.net> wrote:
I've been putting off the openrc upgrade on my vserver
account for some time and think it's finally come around to bite me.
Our vserver team had this to say about it on -dev a few days ago.
- - baselayout-2/openrc isn't stable yet, in fact it's even masked
in profiles/targets/vserver/package.mask
i don't care. baselayout-vserver is a hack, the vserver profiles are
deprecated since ages (although i think the restructuring revived
them), and the vserver team (that's only me currently) doesn't
support anything else beside openrc.
Greets,
Bene
So, you should probably migrate to the normal profiles as recommended
by the vserver howto:
Whoops, missed the link to the vserver howto:
http://www.gentoo.org/proj/en/vps/vserver-howto.xml
Unfortunately that doc isn't very up to date or very well written. Hell
the mentioned baselayout 1.13 doesn't even exist in portage.
It appears that I should.
1. Change profile from vserver to server so I don't have to go mucking
about in package.mask
2. emerge -C baselayout-vserver && emerge baselayout-2 openrc
3. clean up openrc baselayout issues.
4. Make backups, restart, and hope it doesn't explode.
That sound about right?
The other side is that I have no control over the host OS, I just pay
for a hosted vserver. Is any of this goes to have issues if I update the
quest and the host is not aware?
kashani
01-19-2009, 08:52 PM
Nick Cunningham
baselayout and openrc issues from inside a vserver
2009/1/19 kashani <kashani-list@badapple.net>
Peter Alfredsen wrote:
On Mon, 19 Jan 2009 10:28:05 -0800
kashani <kashani-list@badapple.net> wrote:
* * * *I've been putting off the openrc upgrade on my vserver
account for some time and think it's finally come around to bite me.
Our vserver team had this to say about it on -dev a few days ago.
- - baselayout-2/openrc isn't stable yet, in fact it's even masked
in profiles/targets/vserver/package.mask *
i don't care. baselayout-vserver is a hack, the vserver profiles are
deprecated since ages (although i think the restructuring revived
them), and the vserver team (that's only me currently) doesn't
support anything else beside openrc.
Greets,
Bene
So, you should probably migrate to the normal profiles as recommended
4. Make backups, restart, and hope it doesn't explode.
That sound about right?
The other side is that I have no control over the host OS, I just pay for a hosted vserver. Is any of this goes to have issues if I update the *quest and the host is not aware?
kashani
Dont edit anything inside of /usr/portage as it will get wiped out the next time you sync.
If you want to unmask openrc and baselayout then use /etc/portage/package.unmask and /etc/portage/package.keywords.
Make sure you read the OpenRC migration guide or you risk severely hosing your system!
http://www.gentoo.org/doc/en/openrc-migration.xml