| Summary: | stabilize sys-apps/sysvinit-2.86-r10 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Doug Goldstein (RETIRED) <cardoe> |
| Component: | New packages | Assignee: | Gentoo's Team for Core System packages <base-system> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | Keywords: | STABLEREQ |
| Priority: | High | ||
| Version: | 2007.0 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Doug Goldstein (RETIRED)
2007-12-19 15:06:03 UTC
spoke with Uberlord about this pkg and we should be good to go. robbat2 and I would prefer that all arches are on the same baselayout-1 version before we unmask baselayout-2 so that there's only 1 migration path rather then 2. Stable for sparc. amd64 stable not stable with
sys-apps/baselayout-2.0.0_rc6 inside VServer
it overriedes reboot.sh and shutdown.sh files and broke guest OS in vserver
the files reboot.sh and shutdown.sh should have simple checks inside like:
# If we are in a VPS, we don't need anything below here, because
# 1) we don't need (and by default can't) umount anything (VServer) or
# 2) the host utils take care of all umounting stuff (OpenVZ)
if [ "${RC_SYS}" = "VPS" ] ; then
exit 0
fi
see halt.sh code from sys-apps/baselayout-2.0.0_rc6
currenty, latest sysvinit BROKE rebooting guest OS inside vservers
(In reply to comment #4) > not stable with > sys-apps/baselayout-2.0.0_rc6 inside VServer > This package is masked and mixing hardmasked ~arch packages with stable packages is broken and unsupported. > > currenty, latest sysvinit BROKE rebooting guest OS inside vservers > Are you saying that this is a regression from 2.86-r8 to 2.86-r10? If -r8 had the same behavior then this is not a regression but a request for a feature change and as such belongs in it's own bug. its NOT masked or hardmasked for vserver guests. its default for any gentoo os running inside vserver for VPS guests we havent any stable and supported baselayout, only latest is acceptible now. many my friends got a troubles after auto-updating init.d dir (files has been autorewritten) <Cardoe> !herd vserver <jeeves> Cardoe: (vserver) chtekk, hollow <Hollow> Cardoe: pong <Cardoe> Hollow: should vserver users be using baselayout-2.0.0_rc6? <Hollow> yes <Cardoe> is there a regression between sysvinit-2.86-r8 and sysvinit-2.86-r10? <Cardoe> bug #202790 <Hollow> *sigh* i told him, if he blindly overwrites config protected files he is on his own <Hollow> vservers have a custom shutdown.sh/reboot.sh <Hollow> and these custom files have a big warning in them, that you should never overwrite them This is not a regression but a new feature request. i admit it's not that fat: # gentoo init style needs this (and nothing else) exit 0 but you shouldn't overwrite it nevertheless... vservers sucking is not a reason to block stabilization open a new bug Stable for HPPA. alpha/ia64/x86 stable ppc stable ppc64 stable |