| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Gentoo-Bug: http://bugs.gentoo.org/645356
|
|
|
|
|
|
| |
also drop absolute path for dosym
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
|
|
|
| |
drop all vulnerable versions
Gentoo-Bug: 634422
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
|
|
| |
Signed-off-by: Agostino Sarubbo <ago@gentoo.org>
Package-Manager: Portage-2.3.19, Repoman-2.3.6
RepoMan-Options: --include-arches="amd64"
|
|
|
|
|
|
|
|
| |
Update HOMEPAGE
Resolve ebuild.absdosym warnings
See: https://www.mail-archive.com/haproxy@formilux.org/msg28937.html
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
|
|
|
|
|
| |
branch 1.8 is not under heavy development anymore while 1.9 is
Update HOMEPAGE
Resolve ebuild.absdosym warnings
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
|
|
|
|
| |
haproxy 1.6 and 1.7 are no longer under heavy development, keeping live
ebuild for them seems unecessary anymore
Package-Manager: Portage-2.3.19, Repoman-2.3.6
Closes: https://github.com/gentoo/gentoo/pull/7153
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
| |
|
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
RepoMan-Options: --include-arches="hppa"
|
| |
|
| |
|
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
RepoMan-Options: --include-arches="ia64"
|
|
|
|
|
| |
Package-Manager: Portage-2.3.19, Repoman-2.3.6
RepoMan-Options: --include-arches="arm"
|
|
|
|
| |
Package-Manager: Portage-2.3.20, Repoman-2.3.6
|
|
|
|
|
|
| |
Package-Manager: Portage-2.3.13, Repoman-2.3.3
RepoMan-Options: --include-arches="amd64"
Signed-off-by: Agostino Sarubbo <ago@gentoo.org>
|
|
|
|
| |
Package-Manager: Portage-2.3.20, Repoman-2.3.6
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/645356
Package-Manager: Portage-2.3.20, Repoman-2.3.6
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Current versions of squid have a run test for gnu atomics w/no
cross-compile fallback causing builds to fail. Upstream has
rewritten this completely, so until we update to a newer version,
force the cache variable when cross-compiling. Forcing it to no
might not be optimal in all cases, but it's better than nothing.
We have been turning on large-file-system support for a while now,
but the configure test for that probes the build system for flags
to compile with (via `getconf ...`). These flags don't work for
the cross-compile target, and in reality are rarely necessary. By
selecting the default, we always go the standard POSIX route with
the -D_FILE_OFFSET_BITS=64 flag. If a target doesn't respect that
flag, then it might fail to build, but we can wait for anyone to
complain.
|
|
|
|
| |
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
|
| |
Package-Manager: Portage-2.3.13, Repoman-2.3.3
Closes: https://github.com/gentoo/gentoo/pull/6785
|
|
|
|
|
| |
Package-Manager: Portage-2.3.13, Repoman-2.3.3
RepoMan-Options: --include-arches="sparc"
|
| |
|
|
|
|
| |
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.13, Repoman-2.3.3
|
|
|
|
| |
Package-Manager: Portage-2.3.13, Repoman-2.3.3
|
| |
|
|
|
|
| |
Package-Manager: Portage-2.3.16, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.16, Repoman-2.3.6
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The change in https://bugs.gentoo.org/show_bug.cgi?id=584410 only worked because of
multiple bugs interacting.
Due to variable shadowing https://bugs.gentoo.org/show_bug.cgi?id=639164 the loop did not
actually work, and the /run/haproxy.pid was used in every loop iteration.
This only worked because of a bug in openrc: https://bugs.gentoo.org/show_bug.cgi?id=639218
which was fixed in 0.34.11
So before it killed all processes called haproxy if nbproc > 1 in the config
(which means multiple haproxy instances are all killed if one is stopped!)
After the bugfix it doesn't kill, so we're back to the original situation of leftover
processes. And we don't want to rely on the cgroup killer!
The fix is obviously to use start-stop-daemon directly instead of calling openrc
internals that don't do what you think they do.
Package-Manager: Portage-2.3.16, Repoman-2.3.6
RepoMan-Options: --force
|
| |
|
| |
|
| |
|
|
|
|
| |
Package-Manager: Portage-2.3.16, Repoman-2.3.6
|
|
|
|
| |
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.14, Repoman-2.3.6
RepoMan-Options: --include-arches="hppa"
|
|
|
|
|
| |
Package-Manager: Portage-2.3.13, Repoman-2.3.4
RepoMan-Options: --include-arches="sparc"
|
| |
|
|
|
|
|
|
|
| |
Requires building a docker container, which is probably more involved
than I am willing to support.
Closes: https://bugs.gentoo.org/623442
|
|
|
|
|
| |
Package-Manager: Portage-2.3.10, Repoman-2.3.3
RepoMan-Options: --include-arches="ppc"
|
|
|
|
|
| |
Package-Manager: Portage-2.3.10, Repoman-2.3.3
RepoMan-Options: --include-arches="ppc64"
|
| |
|
|
|
|
| |
Gentoo-Bug: 613302
|
| |
|
| |
|
| |
|
| |
|