Fedora 29 compose report: 20181014.n.0 changes
by Fedora Branched Report
OLD: Fedora-29-20181013.n.0
NEW: Fedora-29-20181014.n.0
===== SUMMARY =====
Added images: 0
Dropped images: 0
Added packages: 0
Dropped packages: 0
Upgraded packages: 0
Downgraded packages: 0
Size of added packages: 0 B
Size of dropped packages: 0 B
Size of upgraded packages: 0 B
Size of downgraded packages: 0 B
Size change of upgraded packages: 0 B
Size change of downgraded packages: 0 B
===== ADDED IMAGES =====
===== DROPPED IMAGES =====
===== ADDED PACKAGES =====
===== DROPPED PACKAGES =====
===== UPGRADED PACKAGES =====
===== DOWNGRADED PACKAGES =====
5 years, 7 months
Re: Cannot Boot After Doing system-upgrade
by Garry T. Williams
By the way, from the journal during the dnf system-upgrade reboot:
Sep 30 10:02:27 vfr dnf[831]: grub2-common.noarch 1:2.02-58.fc29
Sep 30 10:02:27 vfr dnf[831]: grub2-efi-x64.x86_64 1:2.02-58.fc29
Sep 30 10:02:27 vfr dnf[831]: grub2-pc.x86_64 1:2.02-58.fc29
Sep 30 10:02:27 vfr dnf[831]: grub2-pc-modules.noarch 1:2.02-58.fc29
Sep 30 10:02:27 vfr dnf[831]: grub2-tools.x86_64 1:2.02-58.fc29
Sep 30 10:02:27 vfr dnf[831]: grub2-tools-efi.x86_64 1:2.02-58.fc29
Sep 30 10:02:27 vfr dnf[831]: grub2-tools-extra.x86_64
1:2.02-58.fc29
Sep 30 10:02:27 vfr dnf[831]: grub2-tools-minimal.x86_64
1:2.02-58.fc29
Sep 30 10:02:28 vfr dnf[831]: shim-x64.x86_64 15-5
And now:
garry@vfr$ rpm -q grub2-common grub2-efi-x64 grub2-pc grub2-pc-modules
grub2-tools grub2-tools-efi grub2-tools-extra grub2-tools-minimal
shim-x64
grub2-common-2.02-62.fc29.noarch
grub2-efi-x64-2.02-62.fc29.x86_64
grub2-pc-2.02-62.fc29.x86_64
grub2-pc-modules-2.02-62.fc29.noarch
grub2-tools-2.02-62.fc29.x86_64
grub2-tools-efi-2.02-62.fc29.x86_64
grub2-tools-extra-2.02-62.fc29.x86_64
grub2-tools-minimal-2.02-62.fc29.x86_64
shim-x64-15-7.x86_64
garry@vfr$
--
Garry T. Williams
5 years, 7 months
Re: Cannot Boot After Doing system-upgrade
by Garry T. Williams
On Saturday, October 13, 2018 5:42:15 PM EDT Chris Murphy wrote:
> On Sat, Oct 13, 2018 at 1:30 PM, Garry T. Williams
> <gtwilliams(a)gmail.com> wrote:
> > On Saturday, October 13, 2018 3:12:44 PM EDT Samuel Sieb wrote:
> >> On 10/13/18 10:39 AM, Garry T. Williams wrote:
> >>
> >> > What am I doing wrong here that I cannot boot after a
> >> > system-upgrade?
> >>
> >> "Doesn't boot" is no information. What exactly is happening?
> >
> > Sorry, the boot record is gone.
>
> You determined this how?
The machine did not boot the Fedora OS. Instead, it booted the OS on
/dev/sda.
Of course, I attempted to boot from the Fedora disk by using the boot
device configuration screen by hitting F12 during reboot. This
failed. (A photograph of the error would have been a good idea.)
I assumed that the reason was the boot record was missing.
> >I happen to have another system on
> >
> > the same machine and that system boots instead of the Fedora
> > system before my recovery actions. When I forced a boot from
> > the fedora system using the machine's boot selection screen, it
> > fails. (No diagnostic information in the BIOS setup screen --
> > just won't boot. I was forced to specify the USB Live system to
> > start a recovery.)
>
> Screen shots or cell photo of the failure might be useful because
> failure/won't boot doesn't tell us what is happening. And what is
> happening is a hint as to what the source of the problem is, how to
> prevent it, and how to fix it. But "won't boot" is not much to go
> on.
Understood.
> Is this BIOS or UEFI? From any other Linux, what do you get for
> 'parted -l u s p' or "fdisk -l" ? And what do you get for
> 'efibootmgr -v' ?
This is useful. I will try to document these results when I upgrade
to F30, if the same happens again.
The fdisk -l did show what I expected it to show:
Disk /dev/sda: 477 GiB, 512110190592 bytes, 1000215216 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 4B21E327-DFE8-4105-AA9B-FEFF8AE8439F
Device Start End Sectors Size Type
/dev/sda1 2048 1026047 1024000 500M EFI System
/dev/sda2 1026048 7317503 6291456 3G Microsoft basic data
/dev/sda3 7317504 933572607 926255104 441.7G Linux filesystem
/dev/sda4 933572608 1000214527 66641920 31.8G Linux swap
Disk /dev/sdb: 477 GiB, 512110190592 bytes, 1000215216 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 9114D615-2FD0-4CF1-A601-DAD4507F6254
Device Start End Sectors Size Type
/dev/sdb1 2048 411647 409600 200M EFI System
/dev/sdb2 411648 2508799 2097152 1G Linux filesystem
/dev/sdb3 2508800 1000214527 997705728 475.8G Linux LVM
Admittedly, this is output from the now-recovered system, but I can
attest that the same was displayed when the command was done using the
Ubuntu system that loaded from /dev/sda.
> > The system-upgrade somehow wiped out my boot record on /dev/sdb.
>
> "boot record" is a BIOS term, so this could mean the code on LBA 0
> or in the MBR gap or BIOS Boot partition has been stepped on; but
> dnf system upgrade doesn't have such an ability. In fact it's a bit
> of a security and bug endurance problem that 'grub2-install' isn't
> run on BIOS upgrades. Whereas on UEFI the bootloader binaries on
> the EFI System partition are replaced during updates, so what
> you're describing might be a GRUB bug.
OK, the system was able to boot from /dev/sdb only after I reinstalled
grub2-efi and shim.
I assumed that was what restored the boot record (or whatever it's
called).
(I was able to boot normally from Fedora immediately before doing the
dnf system-upgrade. A reinstall was not accepted by dnf, so I used
update instead.)
> But the details you're giving only lead to speculation so you need
> to provide specifics, just won't boot is identical to what happens
> to a computer without a drive at all.
Well, I will not be so fast to restore, if it occurs again (f30).
Thank you for your suggestions. I am sorry for the assumptions I
made.
For what it's worth now:
garry@vfr$ efibootmgr -v
BootCurrent: 0002
Timeout: 1 seconds
BootOrder: 0002,0000,0003,0004,0005,0006,0007,0008,0009
Boot0000 ubuntu HD(1,GPT,3252a9ab-23eb-4fd4-9d11-6dc13c6f50ec,
0x800,0xfa000)/File(\EFI\ubuntu\shimx64.efi)
Boot0002* Fedora HD(1,GPT,0534ef43-afb9-409c-8dc8-a1eff1e396ef,
0x800,0x64000)/File(\EFI\fedora\shim.efi)
Boot0003* UEFI: SanDisk Extreme 0001 PciRoot(0x0)/Pci(0x14,0x0)/
USB(17,0)/HD(1,MBR,0x3cb5dbe1,0x16960,0x2990)..BO
Boot0004* Diskette Drive BBS(Floppy,Diskette Drive,0x0)..BO
Boot0005* P0: SK hynix SC300 SATA 512GB BBS(HD,P0: SK hynix SC300 SATA
512GB ,0x0)..BO
Boot0006* P2: INTEL SSDSC2KF512H6 SATA 5 BBS(HD,P2: INTEL
SSDSC2KF512H6 SATA 5,0x0)..BO
Boot0007* USB Storage Device BBS(USB,SanDisk Extreme 0001,0x0)..BO
Boot0008* CD/DVD/CD-RW Drive BBS(CDROM,P1: PLDS DVD+/-RW DU-8A5LH
,0x0)..BO
Boot0009 Onboard NIC BBS(Network,IBA CL Slot 00FE v0106,0x0)..BO
Boot000B* P2: INTEL SSDSC2KF512H6 SATA 5 BBS(HD,P2: INTEL
SSDSC2KF512H6 SATA 5,0x0)..BO
garry@vfr$ sudo parted -l u s p
[sudo] password for garry:
Model: ATA SK hynix SC300 S (scsi)
Disk /dev/sda: 512GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name
Flags
1 1049kB 525MB 524MB fat32 EFI system partition
boot, esp
2 525MB 3747MB 3221MB fat32 Basic data partition
msftdata
3 3747MB 478GB 474GB ext4
4 478GB 512GB 34.1GB linux-swap(v1)
swap
Model: ATA INTEL SSDSC2KF51 (scsi)
Disk /dev/sdb: 512GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name
Flags
1 1049kB 211MB 210MB fat16 EFI System Partition
boot, esp
2 211MB 1285MB 1074MB ext4
3 1285MB 512GB 511GB lvm
Warning: The driver descriptor says the physical block size is 2048
bytes, but
Linux says it is 512 bytes.
Ignore/Cancel? i
Model: SanDisk Extreme (scsi)
Disk /dev/sdc: 251GB
Sector size (logical/physical): 2048B/512B
Partition Table: mac
Disk Flags:
Number Start End Size File system Name Flags
1 2048B 10.2kB 8192B Apple
2 47.4MB 52.8MB 5448kB EFI
3 52.8MB 64.8MB 12.0MB EFI
garry@vfr$
--
Garry T. Williams
5 years, 7 months
Yet another gargantuan mathematical software update
by Jerry James
Hi folks,
It's about time for another "update the world" moment for some of the
mathematical software we have in Fedora. I'm going to try to clear
away a big chunk of my backlogged package work with this update, so it
will be even bigger than usual. Primary goals are to switch from
atlas or the reference blas to openblas, and to drop python 2
packages.
I plan to do all of the necessary rebuilds myself. Package
maintainers, if you would rather that I did not rebuild your package
for you, please let me know. Otherwise, I will do all of these builds
in approximately 1 week from today. I plan to build for Rawhide only.
As usual with this package set, the rebuilds will take a few days, so
expect broken dependencies in the middle.
4ti2: revive this package now that latte-integrale upstream has split
it back out
arb: update to 2.15.0
cddlib: update to 0.94j; epoch bump needed to deal with the new dot in
the version number
ceres-solver: rebuild for tbb
cocoalib: switch to openblas
cryptominisat: update to 5.6.5
cxsc: switch to openblas
DSDP: switch to openblas
eclib: update to 20180815
embree: rebuild for tbb
fawkes: rebuild for tbb
fflas-ffpack: switch to openblas
flint: switch to openblas (needs rebuild anyway due to ntl update)
gazebo: rebuild for tbb
gfan: rebuild for cddlib
giac: rebuild for ntl
iml: switch to openblas
latte-integrale: update to 1.7.5. Not really integrale anymore since
4ti2 was unbundled...
linbox: switch to openblas, enable OpenCL interface
Macaulay2: switch to openblas (needs rebuild anyway due to ntl update)
mathicgb: rebuild for tbb, fix incompatibility with recent gtest versions
ntl: update to 11.3.0. This involves an soname bump.
OCE: rebuild for tbb
opencv: rebuild for tbb
openvdb: rebuild for tbb
polymake: rebuild for cddlib
pynac: switch to openblas, switch from python 2 to python 3
python-cvxopt: update to 1.2.1, switch to openblas, drop the python 2 subpackage
python-fastcache: update to 1.1.0, drop the python 2 subpackage
python-networkx: update to 2.1, drop the python 2 subpackages,
consolidate back to a single package again since this cannot appear in
EPEL < 8 anyway
python-theano: switch to openblas, build with libgpuarray for OpenCL
support, drop the python 2 subpackage
root: rebuild for tbb
sagemath: switch to openblas, switch (with great fear and trepidation)
to the experimental python 3 build
Singular: rebuild for cddlib
suitesparse: rebuild for tbb
sympol: rebuild for cddlib
sympy: update to 1.3, drop the python 2 subpackage
tbb: update to 2019_U1. This has the same soname, but has a
backwards-incompatible ABI change on 32-bit platforms. Therefore, all
consumers must be rebuilt.
TOPCOM: rebuild for cddlib
Regards,
--
Jerry James
http://www.jamezone.org/
5 years, 7 months
Fedora 29 compose report: 20181013.n.0 changes
by Fedora Branched Report
OLD: Fedora-29-20181012.n.0
NEW: Fedora-29-20181013.n.0
===== SUMMARY =====
Added images: 0
Dropped images: 0
Added packages: 0
Dropped packages: 0
Upgraded packages: 3
Downgraded packages: 0
Size of added packages: 0 B
Size of dropped packages: 0 B
Size of upgraded packages: 40.39 MiB
Size of downgraded packages: 0 B
Size change of upgraded packages: 51.95 KiB
Size change of downgraded packages: 0 B
===== ADDED IMAGES =====
===== DROPPED IMAGES =====
===== ADDED PACKAGES =====
===== DROPPED PACKAGES =====
===== UPGRADED PACKAGES =====
Package: krb5-1.16.1-21.fc29
Old package: krb5-1.16.1-20.fc29
Summary: The Kerberos network authentication system
RPMs: krb5-devel krb5-libs krb5-pkinit krb5-server krb5-server-ldap krb5-workstation libkadm5
Size: 18.42 MiB
Size change: 4.84 KiB
Changelog:
* Tue Oct 09 2018 Adam Williamson <awilliam(a)redhat.com> - 1.16.1-21
- Revert the patch from -20 for now as it seems to make FreeIPA worse
Package: nautilus-3.30.2-1.fc29
Old package: nautilus-3.30.1-1.fc29
Summary: File manager for GNOME
RPMs: nautilus nautilus-devel nautilus-extensions
Size: 16.16 MiB
Size change: 24.49 KiB
Changelog:
* Fri Oct 12 2018 Kalev Lember <klember(a)redhat.com> - 3.30.2-1
- Update to 3.30.2
Package: plymouth-0.9.3-14.fc29
Old package: plymouth-0.9.3-13.fc29
Summary: Graphical Boot Animation and Logger
RPMs: plymouth plymouth-core-libs plymouth-devel plymouth-graphics-libs plymouth-plugin-fade-throbber plymouth-plugin-label plymouth-plugin-script plymouth-plugin-space-flares plymouth-plugin-throbgress plymouth-plugin-two-step plymouth-scripts plymouth-system-theme plymouth-theme-charge plymouth-theme-fade-in plymouth-theme-script plymouth-theme-solar plymouth-theme-spinfinity plymouth-theme-spinner
Size: 5.81 MiB
Size change: 22.62 KiB
Changelog:
* Thu Oct 04 2018 Hans de Goede <jwrdegoede(a)fedoraproject.org> - 0.9.3-14
- Add patches from upstream to fix the disk unlock screen sometimes having
a very low resolution on UEFI machines:
https://gitlab.freedesktop.org/plymouth/plymouth/issues/68
===== DOWNGRADED PACKAGES =====
5 years, 7 months
package downgrades from f28 to f29
by Fabio Valentini
Hi all,
I tried upgrading my system to f29, and I noticed some packages that
would have been downgraded. Upon further investigation, their
maintainers seem to have forgotten (or missed) to build and/or submit
updates for these packages to fedora 29 - so, for example, the newer
version is only available on f28 and rawhide, but f29 is stuck on an
older version.
- gd (missing f29 update in bodhi, but koji build is present)
- pipewire (missing f29 update in bodhi, but koji build is present)
- rng-tools (missing both a koji build and bodhi update for f29)
Those three are just the ones that happen to be installed on my
system, probably there are more of these "older on the newer fedora
release" packages.
I haven't been able to find the documentation for this, but I seem to
remember that package versions should always be higher in newer fedora
releases (so there are no downgrades when upgrading from N to N+1). Is
this what is referred to as a "broken upgrade path"?
Fabio
5 years, 7 months