control: tag -1 - moreinfo On Mon, Mar 30, 2015 at 12:58 AM, Cyril Brulebois wrote: > Thanks for trying, but no, that's not sufficient. I really would > like having a real use case where the bug gets reproduced without > “cheating” (for the lack of a better wording), so that we can actually > check that the change isn't worse than the bug it's supposed to fix.
It turns out the difficulty getting rdnssd automatically installed is a bug: http://bugs.debian.org/782299 Steve will be uploading a debian-cd fix soon, but in the meantime I tested a mini.iso (since it configures networking sufficiently early to be able to fetch the package) for a sid gnome install. Here is the installer syslog relevant to rdnssd; netcfg[1369]: rdnssd started; PID: 1384 [...] apt-install: Queueing package rdnssd for later installation netcfg[1369]: DEBUG: Stopping rdnssd, PID 1384 [...] in-target: The following NEW packages will be installed: in-target: rdnssd [...] in-target: Unpacking rdnssd (1.0.1-2) [...] in-target: Setting up rdnssd (1.0.1-2) [...] in-target: pkgsel: starting tasksel [selected gnome as the desktop environment] [...] in-target: The following packages will be REMOVED: in-target: rdnssd [...] in-target: Removing rdnssd (1.0.1-2) [...] in-target: Setting up network-manager-gnome (0.9.10.0-2) In conclusion again everything works entirely as expected. Is this now sufficient? Best wishes, Mike -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CANTw=MOT3OVGaZcDJVejLwu10G466tsMMir=1vvlt63n-th...@mail.gmail.com
