Hi, Cyril Brulebois <k...@debian.org> wrote (Sun, 25 Apr 2021 11:53:22 +0200): > Given the question below, I suppose you could revert this change > manually and restart the installer (after all, it's about a symlink and > a line in a config file).
Sure. I did that already. But this does not gain any value, because building an image myself now without doing any changings leads to a working d-i (on i386, if arch matters) !!! I don't need to do anything to get a working d-i, just build myself. But why does the RC1 fail then? Holger > > However, I don't get it, why recent dailies are not affected, while > > RC1 (and alpha3) is ??? > > > > (That might be the reason, why this issue slipped through our > > attention until now...) > > > > Are there differences during build for the "release builds" (alpha, > > rc) compared to the dailies? > > You can check debian/rules for USE_UDEBS_FROM: > - releases fetch their udebs from testing; > - dailies fetch their udebs from unstable (to shorten the feedback > loop, and to inform our decision to let some packages migrate or not > when a freeze — udebs or otherwise — is in effect) > > You can switch to/from UNRELEASED in the first line of the changelog to > get the desired results. Or you can set the variable yourself if you run > something like this: > > make -C build/ rebuild_netboot-gtk USE_UDEBS_FROM=unstable > > > Cheers, > -- > Cyril Brulebois (k...@debian.org) <https://debamax.com/> > D-I release manager -- Release team member -- Freelance Consultant -- Holger Wansing <hwans...@mailbox.org> PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
