Signed-off-by: Michał Górny
---
glep-0068.rst | 62 ---
1 file changed, 59 insertions(+), 3 deletions(-)
diff --git a/glep-0068.rst b/glep-0068.rst
index d8fc379..5b7e2b9 100644
--- a/glep-0068.rst
+++ b/glep-0068.rst
@@ -4,10 +4,10 @@ Title:
On Mon, Sep 14, 2020 at 12:30:48PM +0200, Marc Schiffbauer wrote:
> * William Hubbs schrieb am 14.09.20 um 00:39 Uhr:
> > All,
> >
> > I would like to get some thoughts on kubernetes packaging.
> >
> > When I started maintaining it in Gentoo, it was packaged as 7 ebuilds
> > (one per
All revdeps are already masked for removal, so let's add it to their
pmask:
# Michał Górny (2020-07-13)
# Python 2 dev-python/pillow revdeps with extended removal time.
# Also the only revdeps of dev-python/matplotlib-python2.
# Removal in 90 days. Bug #729672.
dev-python/matplotlib-python2
--
# Sam James (2020-09-15)
# No longer exists upstream, stuck on long-obsolete EAPI 4,
# and fails to build with glibc-2.32.
# Vestige of Gentoo/FreeBSD.
# bug #715506, #737892, #740916, #547244.
sys-fs/ufsutils
signature.asc
Description: Message signed with OpenPGP
# Stephan Hartmann (2020-09-15)
# Stuck on EAPI 4, does not build, homepage gone, no maintainer.
# Removal in 30 days. See bugs #717188, #725212, #736607,
# #742158.
net-nntp/sn
signature.asc
Description: OpenPGP digital signature
Hi,
The current state is that the Ansible in tree is not working due to fact
that it misses core modules.
I'd say 2.10.0 should be masked, as ~arch or stable arch, it does not
work, then revbump to use bundle package, not ansible-base. If
maintainer want to split it into ansible-base + separated
On 15/09/2020 12:03, Marek Szuba wrote:
> Dear Matthew,
>
> I notice that you have recently stabilised app-admin/ansible-2.10.0 in
> Gentoo. Ansible upstream has introduced in that version major changes to
> their project structure [1] which given the current state of Ansible
> packaging in
Dear Matthew,
I notice that you have recently stabilised app-admin/ansible-2.10.0 in
Gentoo. Ansible upstream has introduced in that version major changes to
their project structure [1] which given the current state of Ansible
packaging in Gentoo can be considered severely breaking for our users.
On Tue, 15 Sep 2020 09:12:58 +0200
Toralf Förster wrote:
> However this doesn't cover bugs filed a while ago and are not be fixed in
> current stable.
A mitigation would be it wouldn't file a stabilization req if there was
already one open.
Basically means as soon as there's one stable req,
On 9/15/20 8:42 AM, Michał Górny wrote:
> Do you have any suggestions how we could improve this?
A (naive) approach would be to have something like auto_stable_after_x_days=n
somewhere and a bot which checks whether a bug was opened related to the last
version.
However this doesn't cover bugs
On 9/15/20 9:42 AM, Michał Górny wrote:
> Hi,
>
> The regular stabilization workflow works for the majority of packages.
> However, it makes little sense for packages with frequent release
> cycles. Examples of these are boto3/botocore (daily release cycle) or
> hypothesis (upstream conflates
Hi,
The regular stabilization workflow works for the majority of packages.
However, it makes little sense for packages with frequent release
cycles. Examples of these are boto3/botocore (daily release cycle) or
hypothesis (upstream conflates commits with releases).
When the latest release
12 matches
Mail list logo
