I'm using zabbix, but I can't sign up as the single active maintainer,
although, I'd be happy to co-maintain it with somebody else.
BTW, @mgorny, as I see, Patrick already fixed the issue, so can we talk about
unmasking and un-lastriting zabbix now?
--
Best regards,
mva
signature.asc
Descri
On Thu, Nov 7, 2019 at 11:13 AM Vadim A. Misbakh-Soloviov
wrote:
> I'm using zabbix, but I can't sign up as the single active maintainer,
> although, I'd be happy to co-maintain it with somebody else.
>
> BTW, @mgorny, as I see, Patrick already fixed the issue, so can we talk
> about
> unmasking
# Thomas Deutschmann (2019-11-07)
# EAPI 0. It's been almost a decade since that openssl bug.
# Removal in 30 days. Bug #697218.
net-misc/openssh-blacklist
--
Regards,
Thomas Deutschmann / Gentoo Linux Developer
C4DD 695F A713 8F24 2AA1 5638 5849 7EE5 1D5D 74A5
signature.asc
Description: Op
sys-apps/lsb-release - Linux Standard Base version query program
Low maintenance, but with six open bug reports.
Regards,
jer
On 2019-11-07 18:57, Jeroen Roovers wrote:
> sys-apps/lsb-release - Linux Standard Base version query program
>
> Low maintenance, but with six open bug reports.
base-system will take that package.
--
Regards,
Thomas Deutschmann / Gentoo Linux Developer
C4DD 695F A713 8F24 2AA1 5638 5849 7EE5
Given glibc upstream's tentative plans to remove libcrypt [1], I think
we should start working out the kinks well in advance. Toolchain has
already added a package.use.force-ed "crypt" USE flag to
sys-libs/glibc-2.30-r2 [2]. The main alternative out there is libxcrypt,
which I have recently bumped
On Thu, 2019-11-07 at 11:52 -0800, Patrick McLean wrote:
> Given glibc upstream's tentative plans to remove libcrypt [1], I think
> we should start working out the kinks well in advance. Toolchain has
> already added a package.use.force-ed "crypt" USE flag to
> sys-libs/glibc-2.30-r2 [2]. The main
On Thu, 7 Nov 2019 11:52:19 -0800
Patrick McLean wrote:
> Given glibc upstream's tentative plans to remove libcrypt [1], I think
> we should start working out the kinks well in advance. Toolchain has
> already added a package.use.force-ed "crypt" USE flag to
> sys-libs/glibc-2.30-r2 [2]. The main
On Thu, 07 Nov 2019 21:28:34 +0100
Michał Górny wrote:
> On Thu, 2019-11-07 at 11:52 -0800, Patrick McLean wrote:
> > Given glibc upstream's tentative plans to remove libcrypt [1], I
> > think we should start working out the kinks well in advance.
> > Toolchain has already added a package.use.for
On Thu, 7 Nov 2019 20:40:40 +
Sergei Trofimovich wrote:
> On Thu, 7 Nov 2019 11:52:19 -0800
> Patrick McLean wrote:
>
> > Given glibc upstream's tentative plans to remove libcrypt [1], I
> > think we should start working out the kinks well in advance.
> > Toolchain has already added a packa
* Tomas Mozes:
> I'll take it: https://github.com/gentoo/gentoo/pull/13567
Thank you for stepping up for this oldie but goodie, Tomas.
-Ralph
On 11/7/19 11:52 AM, Patrick McLean wrote:
> DEPEND="
> elibc_glibc? ( || (
> sys-libs/glibc[crypt(+)]
If a new version of glibc will remove crypt then it needs to be
something like:
|| ( >=sys-libs/glibc-2.30-r2[crypt(-)]
signature.asc
Description: OpenPGP digital s
man2html cannot cope with multi-character number-register names and
also doesn't recognize the square brackets in the '\n' escape
sequence. This breaks the autogenerated HTML output. Rename the
number-register from "step" to "R" and get rid of the square brackets.
Closes: https://bugs.gentoo.org/6
On Thu, 2019-11-07 at 18:56 -0500, Göktürk Yüksek wrote:
> man2html cannot cope with multi-character number-register names and
> also doesn't recognize the square brackets in the '\n' escape
> sequence. This breaks the autogenerated HTML output. Rename the
> number-register from "step" to "R" and g
14 matches
Mail list logo
