John Pilkington writes:
On 16/11/17 22:33, Dario Lesca wrote:
> Il giorno gio, 16/11/2017 alle 13.39 -0500, Sam Varshavchik ha scritto:
>> Looks like this is going to be a common, very, very popular bug.
>> Pretty sure
>> this is bug 1513111.
>> "system-upgrade reboot" apparently now requires a fully working
>> network stack, because it tries to resynchronize with all the repos,
>> despite that this is supposed to be done, and it was done, by
>> "system-upgrade download".
>> I think this is a bug, and it needs to be fixed.
> Thanks Sam, what Bug you talking about?, can you please post me the
The plot thickens. By pointing changing the URL to the server own's repo to
a file:/// URL its upgraded succeeding. Now, it's up on F27, and serving the
But now, an upgrade of another server failed because, once again, 'system-
upgrade reboot' decided to resync during its reboot, and it failed to reach
the local server. The local repo server itself is up, 'system-upgrade
download' doesn't squeak, but the server being upgraded apparently does not
have networking during 'system-upgrade reboot'.
This explains why someone else managed to upgrade a wireless laptop without
networking. Something is going horribly sideways here. 'system-upgrade
reboot' is whining only about my local repo:
Nov 16 18:20:29 monster.email-scan.com
dnf: Failed to synchronize
cache for repo 'my', disabling.
Which is immediately followed by about dozen packages from this repo that
it's "Unable to match":
Nov 16 18:20:36 monster.email-scan.com
dnf: Unable to match package:
And followed by a dozen more. But no mention is made of thousands of
packages from fedora, and fedora-updates! So why is this dumb thing refuses
to run only because it can't reach my repository, but it doesn't feel the
need to verify that the stock fedora repositories are reachable over the
Of course, I can always copy my local repo to the same server, and stick a
file:/// URL on it. But why do I need to do something so stupid? No reason
why this shouldn't work, as is.
The only thing I could possibly think of is that, for my local repository, I
do not use a signing PGP key. Is that the B.S.? I'll find out later tonight.