I was trying to upgrade to FAW-28 Pre-release. I ran the following command:
[root@koenigii ~]# ostree remote add --set gpgkeypath=/etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-28-primary fedora-28-ah https://kojipkgs.fedoraproject.org/atomic/repo/
Then I tried to rebase, which failed:
[root@koenigii ~]# rpm-ostree rebase fedora-28-ah:fedora/28/x86_64/atomic-host 1 metadata, 0 content objects fetched; 569 B transferred in 0 seconds Checking out tree a435b1c... done Enabled rpm-md repositories: fedora updates rpm-md repo 'fedora' (cached); generated: 2018-04-11 11:06:33 rpm-md repo 'updates' (cached); generated: 2018-02-20 19:18:14 Importing metadata [=============] 100% Resolving dependencies... done Applying 851 overlays Building filesystem (851/851) [=============] 100% Running pre scripts... 15 done Running post scripts... error: Running %post for urw-base35-bookman-fonts: Executing bwrap(/bin/sh): Child process killed by signal 1; run `journalctl -t 'rpm-ostree(urw-base35-bookman-fonts.post)'` for more information [root@koenigii ~]# journalctl -t 'rpm-ostree(urw-base35-bookman-fonts.post)' -- Logs begin at Fri 2018-03-30 19:01:46 CDT, end at Thu 2018-04-12 16:19:07 CDT. -- Apr 12 16:10:35 koenigii.mklvr.io rpm-ostree(urw-base35-bookman-fonts.post)[3720]: mkdir: cannot create directory ‘/var/lib/rpm-state’: Read-only file system Apr 12 16:10:35 koenigii.mklvr.io rpm-ostree(urw-base35-bookman-fonts.post)[3720]: touch: cannot touch '/var/lib/rpm-state/urw-base35-fonts/cache-update-needed': No such file or directory Apr 12 16:10:35 koenigii.mklvr.io rpm-ostree(urw-base35-bookman-fonts.post)[3720]: chmod: cannot access '/var/lib/rpm-state/urw-base35-fonts/cache-update-needed': No such file or directory [root@koenigii ~]#
Here's my current rpm-ostree status:
[root@koenigii ~]# sudo rpm-ostree status State: idle; auto updates disabled Deployments: ● ostree://fedora-workstation:fedora/27/x86_64/workstation Version: 27.112 (2018-04-10 18:51:35) BaseCommit: bd025e11ffad9b42cf0c1fed10244ecf130d1b2f8b31d2831f9c6cfeaba4e13f GPGSignature: Valid signature by 860E19B0AFA800A1751881A6F55E7430F5282EE4 LayeredPackages: ImageMagick ansible autoconf buildah calibre emacs evolution evolution-ews flatpak-builder git gnome-tweak-tool htop hugo icedtea-web java-1.8.0-openjdk levien-inconsolata-fonts.noarch libvirt-daemon-qemu mariadb neovim nmap pandoc pass pcsc-lite perltidy rakudo remmina sbcl screen snapd stow terminator texinfo the_silver_searcher thunderbird tmux vim virt-manager zsh ostree://fedora-workstation:fedora/27/x86_64/workstation Version: 27.112 (2018-04-10 18:51:35) BaseCommit: bd025e11ffad9b42cf0c1fed10244ecf130d1b2f8b31d2831f9c6cfeaba4e13f GPGSignature: Valid signature by 860E19B0AFA800A1751881A6F55E7430F5282EE4 LayeredPackages: ImageMagick ansible autoconf buildah calibre emacs evolution evolution-ews flatpak-builder git gnome-tweak-tool htop hugo icedtea-web java-1.8.0-openjdk levien-inconsolata-fonts.noarch libvirt-daemon-qemu mariadb neovim nmap pandoc pass pcsc-lite perltidy rakudo remmina sbcl screen snapd stow terminator texinfo the_silver_searcher thunderbird tmux vim virt-manager zsh LocalPackages: rpmfusion-free-release-27-1.noarch rpmfusion-nonfree-release-27-1.noarch
This looks like a %post compatibility bug. @walters, can you confirm?
Should be fixed by https://github.com/projectatomic/rpm-ostree/pull/1319
(Also that font package should stop using that feature)
That said it's one of your layered packages pulling in that font; you can temporarily drop the layered packages and do the rebase (or find which package is pulilng in that font).
Metadata Update from @dustymabe: - Issue tagged with: F28, bug, workstation
@mklvr please take a look at https://github.com/projectatomic/rpm-ostree/pull/1319 to understand the problem. It will be fixed in the next release of rpm-ostree (so soon in Fedora, but it will be at least a few weeks). For now you can try to unlayer the package that is requiring urw-base35-bookman-fonts and you should then be able to rebase.
urw-base35-bookman-fonts
Thanks for the help! I'll figure out which package is requesting that and unlayer it. Keep up to good work.
will go ahead and close out this ticket since it will be fixed soon.
Metadata Update from @dustymabe: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.