| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Package-Manager: Portage-2.3.5, Repoman-2.3.2
RepoMan-Options: --include-arches="amd64 arm arm64 ppc ppc64"
|
|
|
|
|
| |
Package-Manager: Portage-2.3.5, Repoman-2.3.2
RepoMan-Options: --include-arches="amd64 arm arm64 ppc ppc64"
|
|
|
|
|
| |
Package-Manager: Portage-2.3.5, Repoman-2.3.2
RepoMan-Options: --include-arches="amd64 arm arm64 ppc ppc64"
|
|
|
|
|
| |
Package-Manager: Portage-2.3.5, Repoman-2.3.2
RepoMan-Options: --include-arches="amd64 arm arm64 ppc ppc64"
|
|
|
|
|
| |
Package-Manager: Portage-2.3.5, Repoman-2.3.2
RepoMan-Options: --include-arches="amd64 arm arm64 ppc ppc64"
|
|
|
|
|
| |
Package-Manager: Portage-2.3.5, Repoman-2.3.2
RepoMan-Options: --include-arches="amd64 arm arm64 ppc ppc64"
|
|
|
|
|
| |
Package-Manager: Portage-2.3.5, Repoman-2.3.2
RepoMan-Options: --include-arches="amd64 arm arm64 ppc ppc64"
|
|
|
|
|
| |
Package-Manager: Portage-2.3.5, Repoman-2.3.2
RepoMan-Options: --include-arches="amd64 arm arm64 ppc ppc64"
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug 518422 tried to fix module cache file ownership to glib, but the ebuild
changes missed /modules path and used $libdir/gio/ instead of $libdir/gio/modules
While cross-compiling, we can't generate the cache file, so we shouldn't
die out either. Instead of removing the die, rework it all to not do any
of it while cross-compiling, because we'd end up with an empty glib owned
cache file, which could result in no modules working at all as a cache
file is present from the preinst touch.
Gentoo-bug: 518422
Gentoo-bug: 613306
Thanks-to: Alexis Ballier <aballier@gentoo.org>
|
|
|
|
| |
Package-Manager: Portage-2.3.3, Repoman-2.3.1
|
|
|
|
|
| |
Package-Manager: Portage-2.3.5, Repoman-2.3.2
RepoMan-Options: --include-arches="arm arm64 ppc ppc64"
|
|
|
|
| |
Package-Manager: Portage-2.3.5, Repoman-2.3.2
|
|
|
|
|
|
| |
Package-Manager: Portage-2.3.3, Repoman-2.3.1
RepoMan-Options: --include-arches="amd64"
Signed-off-by: Agostino Sarubbo <ago@gentoo.org>
|
|
|
|
|
| |
Package-Manager: Portage-2.3.5, Repoman-2.3.2
RepoMan-Options: --include-arches="arm arm64 ppc ppc64"
|
| |
|
|
|
|
|
|
| |
Bug: 613924
Package-Manager: Portage-2.3.3, Repoman-2.3.1
|
|
|
|
|
| |
Package-Manager: Portage-2.3.5, Repoman-2.3.2
RepoMan-Options: --ignore-arches
|
|
|
|
| |
Package-Manager: Portage-2.3.5, Repoman-2.3.2
|
|
|
|
| |
Package-Manager: Portage-2.3.5, Repoman-2.3.2
|
|
|
|
| |
Bug: https://bugs.gentoo.org/613924
|
|
|
|
|
| |
Package-Manager: Portage-2.3.3, Repoman-2.3.1
RepoMan-Options: --force
|
|
|
|
| |
Package-Manager: Portage-2.3.3, Repoman-2.3.1
|
|
|
|
| |
Package-Manager: Portage-2.3.3, Repoman-2.3.1
|
|
|
|
| |
Package-Manager: Portage-2.3.3, Repoman-2.3.1
|
|
|
|
| |
Package-Manager: Portage-2.3.3, Repoman-2.3.1
|
|
|
|
|
|
| |
Package-Manager: Portage-2.3.3, Repoman-2.3.1
RepoMan-Options: --include-arches="ppc64"
Signed-off-by: Agostino Sarubbo <ago@gentoo.org>
|
|
|
|
|
|
| |
Package-Manager: Portage-2.3.3, Repoman-2.3.1
RepoMan-Options: --include-arches="ppc"
Signed-off-by: Agostino Sarubbo <ago@gentoo.org>
|
|
|
|
| |
Gentoo-bug: 613822
|
|
|
|
| |
Package-Manager: Portage-2.3.3, Repoman-2.3.1
|
|
|
|
| |
Package-Manager: Portage-2.3.3, Repoman-2.3.1
|
|
|
|
| |
Package-Manager: Portage-2.3.3, Repoman-2.3.1
|
|
|
|
| |
Package-Manager: Portage-2.3.3, Repoman-2.3.1
|
|
|
|
| |
Package-Manager: Portage-2.3.3, Repoman-2.3.1
|
|
|
|
| |
Package-Manager: Portage-2.3.3, Repoman-2.3.1
|
|
|
|
| |
Package-Manager: Portage-2.3.3, Repoman-2.3.1
|
|
|
|
| |
Package-Manager: Portage-2.3.3, Repoman-2.3.1
|
|
|
|
| |
Package-Manager: Portage-2.3.3, Repoman-2.3.1
|
|
|
|
| |
Package-Manager: Portage-2.3.3, Repoman-2.3.1
|
|
|
|
| |
Package-Manager: Portage-2.3.5, Repoman-2.3.2
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I don't believe 3.0.4 is affected:
- it's a vulnerability in windows kernel driver. Not something you can easily build in gentoo today as it requires MSVS to build a driver
- the windows code was added in capstone-3.0.5-rc1. It's not present in 3.0.4 in gentoo at all
But not to forget about the vulnerability on next bump
I'm bumping up to vilnerable release candidate and applying
the upstream patch to fix CVE-2017-6952.
Reported-by: Agostino Sarubbo
Bug: https://bugs.gentoo.org/612912
Package-Manager: Portage-2.3.5, Repoman-2.3.2
|
|
|
|
|
|
| |
Package-Manager: Portage-2.3.3, Repoman-2.3.1
RepoMan-Options: --include-arches="amd64"
Signed-off-by: Agostino Sarubbo <ago@gentoo.org>
|
| |
|
|
|
|
| |
Package-Manager: Portage-2.3.3, Repoman-2.3.1
|
| |
|
|
|
|
| |
Package-Manager: Portage-2.3.5, Repoman-2.3.2
|
|
|
|
| |
Package-Manager: Portage-2.3.4, Repoman-2.3.1
|
| |
|
|
|
|
| |
Package-Manager: Portage-2.3.3, Repoman-2.3.2
|
|
|
|
| |
Package-Manager: Portage-2.3.3, Repoman-2.3.2
|
|
|
|
|
|
| |
Package-Manager: Portage-2.3.3, Repoman-2.3.1
RepoMan-Options: --include-arches="amd64"
Signed-off-by: Agostino Sarubbo <ago@gentoo.org>
|