Opened 7 years ago
Closed 6 years ago
#56158 closed defect (fixed)
virt-manager @1.5.1: destroot fails
Reported by: | ryandesign (Ryan Carsten Schmidt) | Owned by: | danchr (Dan Villiom Podlaski Christiansen) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | ||
Port: | virt-manager |
Description
unable to execute 'gtk-update-icon-cache': No such file or directory error: command 'gtk-update-icon-cache' failed with exit status 1
Change History (4)
comment:1 Changed 7 years ago by raimue (Rainer Müller)
comment:2 Changed 7 years ago by danchr (Dan Villiom Podlaski Christiansen)
That's odd — I only ever build with trace mode active, and wasn't affected by this. Perhaps it only matters for X11 builds of GTK? If so, we should probably reinstate the quartz
variant.
comment:3 Changed 6 years ago by sbutler (Stephen J. Butler)
With gtk3 on my system the command is called "gtk-update-icon-cache-3.0". When I installed the gtk2 port installing this port succeeded.
comment:4 Changed 6 years ago by abusse (Anselm Busse)
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
I guess that was my fault with https://github.com/macports/macports-ports/pull/1463 as I moved gtk from depends_lib to depends_run, so it is no longer available at build time. Note that gtk-update-icon-cache is provided by gtk2, though, but this port was already using gtk3 before.
The icons and
.application
files end up in a strange place somewhere in the python framework path. Although icons in virt-manager are visible for me, I am not sure whether this is correct.Usually, gtk-update-icon-cache is run after activating the port, as it adds the new files to the cache that is used for all ports.