| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/664394
Closes: https://bugs.gentoo.org/664990
Package-Manager: Portage-2.3.46, Repoman-2.3.10
|
|
|
|
|
| |
Closes: https://github.com/gentoo/gentoo/pull/9730
Package-Manager: Portage-2.3.48, Repoman-2.3.10
|
|
|
|
| |
Package-Manager: Portage-2.3.48, Repoman-2.3.10
|
|
|
|
| |
Package-Manager: Portage-2.3.49, Repoman-2.3.10
|
|
|
|
|
|
| |
new lvm2
Package-Manager: Portage-2.3.49, Repoman-2.3.10
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/show_bug.cgi?id=665418
Package-Manager: Portage-2.3.49, Repoman-2.3.10
|
|
|
|
| |
Package-Manager: Portage-2.3.49, Repoman-2.3.10
|
|
|
|
| |
Package-Manager: Portage-2.3.49, Repoman-2.3.10
|
|
|
|
| |
Package-Manager: Portage-2.3.49, Repoman-2.3.10
|
|
|
|
|
|
|
|
|
|
|
| |
This also includes a fix for the install process breaking when a recent
version of konqueror is installed. Crossover relies on it for KDE
version detection while Konqueror in its infinite wisdom decided to open
things with write permissions, which are sandbox violations. Right now,
the fix is only in 17.5.1. I need to talk to upstream and think about
this some more before I decide the proper course of action.
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.48, Repoman-2.3.10
|
|
|
|
|
|
| |
Bump to 3.15
Package-Manager: Portage-2.3.48, Repoman-2.3.10
|
|
|
|
| |
Package-Manager: Portage-2.3.48, Repoman-2.3.10
|
|
|
|
|
|
| |
Bump to 3.15
Package-Manager: Portage-2.3.48, Repoman-2.3.10
|
|
|
|
| |
Package-Manager: Portage-2.3.48, Repoman-2.3.10
|
|
|
|
|
|
| |
Bump to 3.15
Package-Manager: Portage-2.3.48, Repoman-2.3.10
|
|
|
|
| |
Package-Manager: Portage-2.3.48, Repoman-2.3.10
|
|
|
|
|
|
| |
Bump to 3.15
Package-Manager: Portage-2.3.48, Repoman-2.3.10
|
|
|
|
| |
Package-Manager: Portage-2.3.48, Repoman-2.3.10
|
|
|
|
| |
Package-Manager: Portage-2.3.48, Repoman-2.3.10
|
|
|
|
| |
Package-Manager: Portage-2.3.48, Repoman-2.3.10
|
|
|
|
|
|
| |
Thanks [Arfrever] for the report
Package-Manager: Portage-2.3.48, Repoman-2.3.10
|
|
|
|
|
|
|
| |
Require vulkan for vkd3d
Bump to 3.14
Package-Manager: Portage-2.3.48, Repoman-2.3.10
|
|
|
|
|
|
|
| |
Require vulkan for vkd3d
Bump to 3.14
Package-Manager: Portage-2.3.48, Repoman-2.3.10
|
|
|
|
|
|
|
| |
Require vulkan for vkd3d
Bump to 3.14
Package-Manager: Portage-2.3.48, Repoman-2.3.10
|
|
|
|
|
|
|
| |
Require vulkan for vkd3d
Bump to 3.14
Package-Manager: Portage-2.3.48, Repoman-2.3.10
|
|
|
|
|
|
|
| |
This part was from before I was a developer
Fixes: https://bugs.gentoo.org/664906
Package-Manager: Portage-2.3.48, Repoman-2.3.10
|
|
|
|
| |
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
|
|
|
| |
Add patch for "layer not known" corruption issue 966.
See: https://github.com/projectatomic/buildah/issues/966
Package-Manager: Portage-2.3.48, Repoman-2.3.10
|
|
|
|
|
|
|
|
|
|
| |
Add btrfs USE flag, and also a device-mapper USE flag.
Use GOCACHE=off to hopefully avoid the reported /root/cache
sandbox violation.
Reported-by: Toralf Förster <toralf@gentoo.org>
Closes: https://bugs.gentoo.org/664574
Package-Manager: Portage-2.3.48, Repoman-2.3.10
|
|
|
|
|
|
|
| |
virt-viewer-7.0 needs spice-gtk-0.35 to build
Closes: https://bugs.gentoo.org/663902
Package-Manager: Portage-2.3.47, Repoman-2.3.10
|
| |
|
|
|
|
| |
Package-Manager: Portage-2.3.48, Repoman-2.3.10
|
|
|
|
| |
Package-Manager: Portage-2.3.48, Repoman-2.3.10
|
|
|
|
| |
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/663488
Package-Manager: Portage-2.3.48, Repoman-2.3.10
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/664260
Package-Manager: Portage-2.3.47, Repoman-2.3.10
|
|
|
|
| |
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.48, Repoman-2.3.10
|
|
|
|
| |
Package-Manager: Portage-2.3.48, Repoman-2.3.10
|
|
|
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/583886
Closes: https://bugs.gentoo.org/657816
Closes: https://bugs.gentoo.org/663780
Package-Manager: Portage-2.3.48, Repoman-2.3.10
Closes: https://github.com/gentoo/gentoo/pull/9651
|
|
|
|
|
|
|
| |
Thanks-to: Fabio Cavallo <fhorse@libero.it>
Closes: https://bugs.gentoo.org/661524
Package-Manager: Portage-2.3.40, Repoman-2.3.9
Closes: https://github.com/gentoo/gentoo/pull/9656
|
|
|
|
| |
Package-Manager: Portage-2.3.47, Repoman-2.3.10
|
|
|
|
| |
Package-Manager: Portage-2.3.47, Repoman-2.3.10
|
|
|
|
|
|
|
| |
Closing again.
Closes: Bug: https://bugs.gentoo.org/663330
Package-Manager: Portage-2.3.47, Repoman-2.3.10
|
|
|
|
| |
Package-Manager: Portage-2.3.46, Repoman-2.3.10
|
|
|
|
| |
Package-Manager: Portage-2.3.46, Repoman-2.3.10
|
|
|
|
|
|
|
|
| |
Add some dependencies used by upstream, fully build custom sqlite,
move tools to IUSE.
Closes: https://bugs.gentoo.org/show_bug.cgi?id=628346
Package-Manager: Portage-2.3.46, Repoman-2.3.10
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
From the bug report:
"""
When libvirt-guests tries to shutdown or suspend xen guests, it is
unable to tell when all of the guests have terminated and ends up
waiting the entire timeout before going on. This is because in xen,
dom0 is always running. Simply grepping out the dom0 uuid (all 0s)
should take care of this issue.
"""
Thanks to Karl Hakimian for bug report and patch.
This is fixed in versions 4.6.0-r1 and 9999.
Closes: https://bugs.gentoo.org/651598
Package-Manager: Portage-2.3.47, Repoman-2.3.10
|