gives result that cron cant start Reproducible: Always
I can't reproduce this. Please give more detailed information about what exactly fails, e.g. error messages etc. PS: Maybe you're running a pre-2.0 version of sys-apps/baselayout which is not supported any more, I think.
reopen with more information please.
yes i still on baselayout 1.x, there is no sign of need more then that in the ebuild so it should still work with 1.x ? will create another bug now that is why i keep baselayout 1.x, funtoo have same bug btw (baselayout have / root partion in double listing in mtab, and a belive its something that really needs fixin, it just not give errors, ubuntu does not have this error, only exists on gentoo/funtoo) cant reopen btw
possible to have 2 init scripts ?, one pr baselayout ?
It's time to upgrade to baselayout-2.
(In reply to comment #5) > It's time to upgrade to baselayout-2. why no depend then ?
(In reply to comment #6) > (In reply to comment #5) > > It's time to upgrade to baselayout-2. > > why no depend then ? I agree that there should be dependencies for such things. And this is not the only package affected. Overall, the time between baselayout-2 being stabilized and baselayout-1 being completely phased out has been too short for a lot of stable systems. There are still systems out there which run baselayout-1, which still need to keep staying online for some time, but at the same time kept up-to-date with the latest security patches. I don't want a philosophical discussion, but only state that the upgrade path has caused many similar problems for users. For example, people with machines running baselayout-1 who upgrade from important_service-2.0-r3 to 2.0-r4 and do a mere "/etc/init.d/important_service restart" might get serious service downtime. Proper dependencies might have prevented such downtime resulting from incompatible init-scripts.
this is not something to be done on a per-package basis. baselayout-1 isn't supported anywhere anymore. http://sources.gentoo.org/profiles/base/packages?r1=1.58&r2=1.59
https://bugs.gentoo.org/show_bug.cgi?id=398197 created this bug, is why i keep baselayout 1 a little more
(In reply to comment #7) > (In reply to comment #6) > > (In reply to comment #5) > > > It's time to upgrade to baselayout-2. > > > > why no depend then ? Because baselayout-1.x is no longer supported for running systems. we support migration from baselayout-1 to baselayout-2, but that is all. We are not interested in keeping two sets of init scripts around so that users can stay on baselayout-1. > I agree that there should be dependencies for such things. And this is not the > only package affected. > > Overall, the time between baselayout-2 being stabilized and baselayout-1 being > completely phased out has been too short for a lot of stable systems. There are > still systems out there which run baselayout-1, which still need to keep > staying online for some time, but at the same time kept up-to-date with the > latest security patches. I don't want a philosophical discussion, but only > state that the upgrade path has caused many similar problems for users. All we are supporting is _migration_ from baselayout-1 to baselayout-2, and that has been true since 28 Jun 2011, which was the first day baselayout-2 was stable for all architectures. We will stop supporting even that on 28 Jun 2012, as per gentoo policy. You really should upgrade. > For example, people with machines running baselayout-1 who upgrade from > important_service-2.0-r3 to 2.0-r4 and do a mere "/etc/init.d/important_service > restart" might get serious service downtime. Proper dependencies might have > prevented such downtime resulting from incompatible init-scripts. As I said above, when that happens, they need to upgrade to baselayout-2.
