Bug 2153570 - package google-noto-sans-display-fonts broken due to dependency bug on google-noto-fonts-common
Summary: package google-noto-sans-display-fonts broken due to dependency bug on google...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: google-noto-fonts
Version: 37
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Akira TAGOH
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-12-14 19:17 UTC by craigcabrey
Modified: 2023-06-12 11:29 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-06-12 11:29:38 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description craigcabrey 2022-12-14 19:17:16 UTC
Description of problem:

Package was not upgraded with core noto font package. Upgrading results in conflicts:

```
error: Could not depsolve transaction; 1 problem detected:
 Problem: cannot install both google-noto-fonts-common-20201206^1.git0c78c8329-5.fc37.noarch and google-noto-fonts-common-20201206^1.git0c78c8329-7.fc37.noarch
  - package google-noto-sans-display-fonts-20201206^1.git0c78c8329-5.fc37.noarch requires google-noto-fonts-common = 20201206^1.git0c78c8329-5.fc37, but none of the providers can be installed
  - conflicting requests
```

current status:

```
[craigcabrey@zephyrus ~]$ rpm-ostree status
State: idle
Deployments:
● fedora:fedora/37/x86_64/silverblue
                  Version: 37.20221201.0 (2022-12-01T00:47:04Z)
               BaseCommit: fa293b93fa6a5bc7601fff34b6dd0de591bbc05d242af0521e5f097d080ecd89
             GPGSignature: Valid signature by ACB5EE4E831C74BB7C168D27F55AD3FB5323552A
      RemovedBasePackages: firefox firefox-langpacks 107.0-4.fc37
           LocalOverrides: kernel-core kernel-modules-extra kernel-modules kernel 6.0.10-300.fc37 -> 6.0.9-302.rog.fc37
          LayeredPackages: asusctl gnome-tweak-tool google-noto-sans-display-fonts google-noto-sans-mono-fonts
                           langpacks-en NetworkManager-l2tp-gnome openssl pass
```

Version-Release number of selected component (if applicable):


How reproducible: reliably reproducible


Steps to Reproduce:
1. layer package google-noto-sans-display-fonts
2. upgrade to latest base image
3.

Actual results: upgrade fails (or if already on a problematic base image, package fails to layer)


Expected results: package layers without error


Additional info:

Comment 1 Jens Petersen 2022-12-20 04:15:41 UTC
Correct me if I am wrong, but I don't think rpm-ostree handles obsoletes of an overlay in this case.

Basically if you overlay a package which gets obsoleted it is your responsibility to remove it from your deployment first, as far as I know.
So I don't think there is anything that can be done in the google-noto-fonts to ameliorate this.

google-noto-sans-fonts already obsoletes google-noto-sans-display-fonts:

$ sudo dnf -q list google-noto-sans-fonts
Available Packages
google-noto-sans-fonts.noarch                                 20201206^1.git0c78c8329-7.fc37                                 updates
$ sudo dnf -q repoquery --obsoletes google-noto-sans-fonts
google-noto-sans-display-fonts < 20201206^1.git0c78c8329-7.fc37
google-noto-sans-ui-fonts < 20201206^1.git0c78c8329-7.fc37

Also we install google-noto-sans-vf-fonts by default in Silverblue,
so you may not need any overlay at all.

Comment 2 Akira TAGOH 2022-12-20 04:57:23 UTC
maybe this: https://github.com/coreos/rpm-ostree/issues/1978

Comment 3 Akira TAGOH 2023-06-12 11:29:38 UTC
I think there are nothing else we can do in packaging side. So closing.


Note You need to log in before you can comment on or make changes to this bug.