Re: [HEADS-UP] systemd is now the default init system in rawhide

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Jul 23, 2010 at 08:04:48PM -0700, darrell pfeifer wrote:
> On Fri, Jul 23, 2010 at 18:26, Lennart Poettering <mzerqung@xxxxxxxxxxx>wrote:
> 
> > Heya,
> >
> > I have just uploaded a new systemd and a new upstart package which make
> > systemd the default init system for Rawhide. The scheme I followed makes
> > sure that in case systemd actually breaks systems there is an easy path
> > back to upstart. And here's how it works:
> >
> > - "upstart" and "systemd" are now parallel installable. When you upgrade
> >  rawhide you will get both installed. (we'll drop upstart eventually,
> >  but during the testing phase i made sure to explicitly install both,
> >  so that there is a safe backup init system)
> >
> >
> >
> Just gave it a try with the koji of moments ago.
> 
> ---> Package systemd-sysvinit.x86_64 0:4-3.fc14 set to be installed
> --> Processing Dependency: systemd = 4-3.fc14 for package:
> systemd-sysvinit-4-3.fc14.x86_64
> --> Processing Dependency: upstart >= 0.6.5-6.fc14 for package:
> systemd-sysvinit-4-3.fc14.x86_64

What?!

> ---> Package systemd-units.x86_64 0:4-3.fc14 set to be updated
> --> Running transaction check
> ---> Package systemd.x86_64 0:4-3.fc14 set to be installed
> ---> Package upstart.x86_64 0:0.6.5-7.fc14 set to be updated
> --> Processing Dependency: sysvinit-userspace for package:

Aand this is the other half of the problem. Change I made before Lennart was
around to make a complementary change in the systemd package unfortunately. It
shouldn't have caused a big issue except for the really bizzare dependency
mentioned above.

> upstart-0.6.5-7.fc14.x86_64
> --> Running transaction check
> ---> Package upstart-sysvinit.x86_64 0:0.6.5-7.fc14 set to be installed
> --> Processing Conflict: systemd-sysvinit-4-3.fc14.x86_64 conflicts
> upstart-sysvinit
> --> Processing Conflict: upstart-sysvinit-0.6.5-7.fc14.x86_64 conflicts
> systemd-sysvinit
> --> Finished Dependency Resolution
> Error: systemd-sysvinit conflicts with upstart-sysvinit
> Error: upstart-sysvinit conflicts with systemd-sysvinit
>  You could try using --skip-broken to work around the problem
>  You could try running: rpm -Va --nofiles --nodigest
> 
> 
> darrell

> -- 
> devel mailing list
> devel@xxxxxxxxxxxxxxxxxxxxxxx
> https://admin.fedoraproject.org/mailman/listinfo/devel

-- 
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux