acct-user/mighttpd2
A user for www-servers/mighttpd2
ChangeLog
commit a2f524e74d7e5e5000c1d057a74dcd7f4af7b43c
Author: hololeap <hololeap@users.noreply.github.com>
Date: Sat May 6 17:04:20 2023 -0600
*/*: Remove ~x86 (and related) from KEYWORDS
x86 is mostly untested, and even building a subset of ::haskell
revealed failing tests which pass on amd64.
With the new behavior of hackport to only add ARCH to KEYWORDS, there
will be CI failures if a package has ~x86 removed but not from its
revdep tree as well. The only sensible mitigation is to remove ~x86
tree-wide until we have a dedicated tester willing to fix current bugs.
See: https://github.com/snoyberg/mono-traversable/issues/210
Signed-off-by: hololeap <hololeap@users.noreply.github.com>
commit 26cb666073c2131cfd6e8b39362212e87006a29b
Author: hololeap <hololeap@users.noreply.github.com>
Date: Wed Dec 7 12:55:22 2022 -0700
acct-user/mighttpd2: new package, add 0
Signed-off-by: hololeap <hololeap@users.noreply.github.com>
Author: hololeap <hololeap@users.noreply.github.com>
Date: Sat May 6 17:04:20 2023 -0600
*/*: Remove ~x86 (and related) from KEYWORDS
x86 is mostly untested, and even building a subset of ::haskell
revealed failing tests which pass on amd64.
With the new behavior of hackport to only add ARCH to KEYWORDS, there
will be CI failures if a package has ~x86 removed but not from its
revdep tree as well. The only sensible mitigation is to remove ~x86
tree-wide until we have a dedicated tester willing to fix current bugs.
See: https://github.com/snoyberg/mono-traversable/issues/210
Signed-off-by: hololeap <hololeap@users.noreply.github.com>
commit 26cb666073c2131cfd6e8b39362212e87006a29b
Author: hololeap <hololeap@users.noreply.github.com>
Date: Wed Dec 7 12:55:22 2022 -0700
acct-user/mighttpd2: new package, add 0
Signed-off-by: hololeap <hololeap@users.noreply.github.com>