Re: Upgrading from F30 to F31 beta reboot issue

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Oct 2, 2019 at 6:14 PM Samuel Sieb <samuel@xxxxxxxx> wrote:
>
> On 10/2/19 5:03 PM, Chris Murphy wrote:
> > On Wed, Oct 2, 2019 at 3:32 PM Alan <alan@xxxxxxxxxxxxxx> wrote:
> >>
> >> This is interesting... I am going to do a heavy clean of the packages
> >> and try again.
> >>
> >> Oct 02 11:22:23 daimajin dnf[1390]: Transaction Summary
> >> Oct 02 11:22:23 daimajin dnf[1390]:
> >> =======================================================================
> >> =========
> >> Oct 02 11:22:23 daimajin dnf[1390]: Install     144 Packages
> >> Oct 02 11:22:23 daimajin dnf[1390]: Upgrade    4828 Packages
> >> Oct 02 11:22:23 daimajin dnf[1390]: Remove       12 Packages
> >> Oct 02 11:22:23 daimajin dnf[1390]: Downgrade     9 Packages
> >> Oct 02 11:22:23 daimajin dnf[1390]: Skip          3 Packages
> >> Oct 02 11:22:27 daimajin systemd[1]: systemd-hostnamed.service:
> >> Succeeded.
> >> Oct 02 11:22:27 daimajin kernel: audit: type=1131
> >> audit(1570040547.732:91): pid=1 uid=0 auid=4294967295 ses=4294967295
> >> subj=system_u:system_r:init_t:s0 msg='unit=systemd-hostnam>
> >> Oct 02 11:22:27 daimajin audit[1]: SERVICE_STOP pid=1 uid=0
> >> auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
> >> msg='unit=systemd-hostnamed comm="systemd" exe="/usr/>
> >> Oct 02 11:23:01 daimajin dnf[1390]: Total size: 9.4 G
> >> Oct 02 11:23:01 daimajin dnf[1390]: Total download size: 19 M
> >
> > I'm confused right off the bat, if this is the reboot that's supposed
> > to do the offline upgrade. There shouldn't be anything to download, it
> > should already have everything downloaded.
>
> dnf runs builds the whole transaction again using cached data.  There's
> a mention of that at the bottom.  It shouldn't have to download, but
> that's the problem here.  Somehow there are some missing packages (maybe
> damaged, but it looks more like missing) and it can't download them
> because it's in cache-only mode.

I'm thinking both missing and corrupt. The early message "download
size: 19 M" is consistent with missing, but then why are they missing
when the download process includes a transaction check? Ostensibly,
the transaction check is the same as what happens in the offline/cache
mode. I'm not sure how 'download --allow-erasing' gets passed onto the
reboot and subsequent upgrade. Does it need to be passed twice? And
then also I wonder if -v can be passed to 'dnf system-upgrade reboot'
to get verbose messages for the offline/upgrade boot dumped into the
journal.

"Error opening file for checksum" taken literally, to me, means the
file is there but fails RPM checksum. Similar to the above question I
wonder if '--rpmverbosity debug' can be passed to dnf for the reboot.
But if so, it should reveal if this really is an RPM checksum fail.



-- 
Chris Murphy
_______________________________________________
test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/test@xxxxxxxxxxxxxxxxxxxxxxx




[Index of Archives]     [Fedora Desktop]     [Fedora SELinux]     [Photo Sharing]     [Yosemite Forum]     [KDE Users]

  Powered by Linux