| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/637022
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
|
|
| |
Submitted-by: pa.lacaze@gmail.com
Closes: https://bugs.gentoo.org/607062
Package-Manager: Portage-2.3.13, Repoman-2.3.3
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/643996
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/643996
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/645640
Closes: https://github.com/gentoo/gentoo/pull/6977
|
|
|
|
| |
Closes: https://bugs.gentoo.org/638024
|
|
|
|
|
|
|
|
| |
As there is no recent version available upstream, I've created
a patch to build with qt5.
Reported-In: https://bugs.gentoo.org/645434
Package-Manager: Portage-2.3.20, Repoman-2.3.6
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/644514
Package-Manager: Portage-2.3.20, Repoman-2.3.6
|
|
|
|
|
|
|
|
|
| |
Version 5.12.0-r1 is probably not going to be stabilised soon.
Considering 5.11.1-r1 is having issues as well, follow Soap_'s
advice and simply de-stabilise this package.
Bug: https://bugs.gentoo.org/644414
Package-Manager: Portage-2.3.20, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/641866
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/641938
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/640206
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
|
|
|
| |
First step to keep this package in tree is making any Qt4 ties optional
completely. Ultimately the Qt4 dependency has to go.
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.13, Repoman-2.3.3
|
|
|
|
| |
Package-Manager: Portage-2.3.14, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.14, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.13, Repoman-2.3.3
|
|
|
|
| |
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/642910
Signed-off-by: Justin Lecher <jlec@gentoo.org>
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/642910
Signed-off-by: Justin Lecher <jlec@gentoo.org>
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
|
| |
Signed-off-by: Justin Lecher <jlec@gentoo.org>
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
|
| |
Signed-off-by: Justin Lecher <jlec@gentoo.org>
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
|
|
|
|
| |
Add latest hashes
Closes: https://bugs.gentoo.org/642910
Signed-off-by: Justin Lecher <jlec@gentoo.org>
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
|
| |
Signed-off-by: Justin Lecher <jlec@gentoo.org>
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
|
|
|
|
| |
Add latest hashes
Closes: https://bugs.gentoo.org/642910
Signed-off-by: Justin Lecher <jlec@gentoo.org>
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/641534
Closes: https://bugs.gentoo.org/642944
Signed-off-by: Justin Lecher <jlec@gentoo.org>
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/634548
Signed-off-by: Justin Lecher <jlec@gentoo.org>
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
|
|
|
|
| |
* Specifying WANT_AUTOCONF=2.5 is unnecessary as this will
choose the most recent version of Autoconf anyways. It
only impedes future bumps of Autoconf.
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.13, Repoman-2.3.3
|
|
|
|
| |
Package-Manager: Portage-2.3.13, Repoman-2.3.3
|
|
|
|
| |
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
|
| |
Package-Manager: Portage-2.3.13, Repoman-2.3.3
RepoMan-Options: --include-arches="arm64"
|
|
|
|
| |
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/610362
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/641008
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
|
|
| |
Thanks-to: Attila Tóth <atoth@atoth.sote.hu>
Closes: https://bugs.gentoo.org/641658
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/615986
Package-Manager: Portage-2.3.13, Repoman-2.3.3
|