| 1 |
On Wed, 9 Sep 2020 09:48:04 -0400 |
| 2 |
David Michael <fedora.dm0@×××××.com> wrote: |
| 3 |
|
| 4 |
> On Wed, Sep 9, 2020 at 5:37 AM Alexis Ballier <aballier@g.o> |
| 5 |
> wrote: |
| 6 |
> > On Tue, 8 Sep 2020 15:54:14 -0400 |
| 7 |
> > David Michael <fedora.dm0@×××××.com> wrote: |
| 8 |
> > |
| 9 |
> > > Hi, |
| 10 |
> > > |
| 11 |
> > > This fix might not be so straightforward. A configuration I |
| 12 |
> > > tested hit a dependency loop with shadow -> pambase -> systemd -> |
| 13 |
> > > a bunch of groups -> shadow. It is possible to bootstrap around |
| 14 |
> > > by emerging shadow with no USE flags first, but I don't know how |
| 15 |
> > > acceptable it is to introduce new dep loops like this. |
| 16 |
> > |
| 17 |
> > what happens without your change ? |
| 18 |
> |
| 19 |
> Someone reported an issue in https://bugs.gentoo.org/720948 that |
| 20 |
> showed shadow and groups are not ordered during installation. I am |
| 21 |
> not sure what environment produced those symptoms since I never |
| 22 |
> encountered it, but you can rage-clean shadow and a group, delete the |
| 23 |
> group, then reinstall it to reproduce the problem. |
| 24 |
> |
| 25 |
|
| 26 |
Yep, that's exactly why one needs the change you are proposing. |
| 27 |
The dependency loop needs to be resolved, but introducing it like that |
| 28 |
is IMHO better than failing like in the above bug because it is not |
| 29 |
resolved properly. |
Archives