Summary: | [blocks B ] <sys-apps/systemd-217 ("<sys-apps/systemd-217" is blocking sys-apps/kmod-18-r2) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | tman <cornicx> |
Component: | [OLD] Core system | Assignee: | Gentoo systemd Team <systemd> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | fabio.coatti, gmurray, qa, rose, tsg |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
tman
2014-10-30 07:41:24 UTC
Yes, we know. There are Gentoo developers who just love adding blockers on systemd, and leaving us notices on IRC in middle of the night. Like it was *that hard* to wait a few hours to give us time to bump it. But well, this is Gentoo. You can't expect grown-up behavior here. CC-ing comrel@ in case they considered this kind of repetitive behavior bad for Gentoo's image. *** Bug 527466 has been marked as a duplicate of this bug. *** Same issue here. Wath will be the solution? (In reply to Michał Górny from comment #1) > Yes, we know. There are Gentoo developers who just love adding blockers on > systemd, and leaving us notices on IRC in middle of the night. Like it was > *that hard* to wait a few hours to give us time to bump it. But well, this > is Gentoo. You can't expect grown-up behavior here. So far this is a technical issue, and I don't really see anything for comrel here yet. If other methods of resolution fail, please cc us back. Handing over to QA. (In reply to Juergen Rose from comment #4) > Same issue here. Wath will be the solution? The reference solution is 'emerge --sync'. We can discuss other solutions if you like :). |