Showing responsible packages at errors caused by dependencies

[fbruetting]

Host system details

State: idle
AutomaticUpdates: disabled
Deployments:
● ostree://fedora-workstation:fedora/28/x86_64/workstation
                   Version: 28.20180907.0 (2018-09-07 15:00:58)
                BaseCommit: 15c1d3ca7f58f6874e982d6f254fd3abb1204b7976477101695ad8787007debd
              GPGSignature: Valid signature by 128CF232A9371991C8A65695E08E7E629DB62FB1
           LayeredPackages: adapta-gtk-theme adobe-source-code-pro-fonts adobe-source-sans-pro-fonts adobe-source-serif-pro-fonts android-tools chrome-gnome-shell chromium cockpit
                            dconf-editor dnf easytag exa exfat-utils fd-find fedora-repos-modular ffmpeg ffmpeg-libs gdb git glances gnome-encfs-manager gnome-tweaks gnome-usage gpick
                            hack-fonts htop iftop julia linux-libertine-biolinum-fonts linux-libertine-fonts mosh mozilla-fira-mono-fonts mozilla-fira-sans-fonts neovim powerline-go pv
                            pygobject3 python3-matplotlib ripgrep setroubleshoot task tilix tilix-nautilus tmux tokei xenlism-wildfire xenlism-wildfire-midnight youtube-dl zsh

Expected vs actual behavior

I wanted to rebase to F29SB, but received this error with my layered packages:

error: Importing libpeas-gtk: Unsupported path: /app/lib64/girepository-1.0/PeasGtk-1.0.typelib; See https://github.com/projectatomic/rpm-ostree/issues/233

Expected:
Would be cool if all packages pulling in this dependency could be listed (as in this case, the removal of chromium didn’t solve that issue).

[jlebon]

Yeah, AFAIK this requires a richer libsolv API to tease out. See #1113 and #731. Closing as dupe of the latter (though that one is about treecompose, it's the same underlying functionality required).

[cgwalters]

error: Importing libpeas-gtk: Unsupported path: /app/lib64/girepository-1.0/PeasGtk-1.0.typelib

That looks like an RPM rebuilt for flatpak. The main libpeas-gtk looks OK to me. Do you have some custom repos?

[fbruetting]

No, I didn’t have to modify any Flatpak, one of my layered RPMs caused this (I at some point uninstalled all of them for making rebase work). I can find out which one exactly caused this, if this is of interest to you?

[dustymabe]

I think this is also related to another issue report. colin found the problem related to the modularity repos being enabled and is trying to fix it with: https://pagure.io/workstation-ostree-config/pull-request/105