On Sun, 2020-09-13 at 14:21 +0300, Andrew Savchenko wrote:
> On Sat, 29 Aug 2020 21:53:45 +0200 Michał Górny wrote:
> > Thanks to David Michael for the initial patch and upstream fixes.
> >
> > Signed-off-by: Michał Górny
> > ---
> > eclass/acct-group.eclass | 16 +++-
> > eclass/acc
* 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 executable), and only one of them was marked stable.
>
> Since we normally do not split up
Dnia September 13, 2020 11:21:28 AM UTC, Andrew Savchenko
napisał(a):
>On Sat, 29 Aug 2020 21:53:45 +0200 Michał Górny wrote:
>> Thanks to David Michael for the initial patch and upstream fixes.
>>
>> Signed-off-by: Michał Górny
>> ---
>> eclass/acct-group.eclass | 16 +++-
>> ecla
On Sun, Sep 13, 2020 at 11:52 PM Kent Fredric wrote:
>
> But when you file a bug, you rely on bugzilla being maintained by
> Gentoo Infra, not some 3rd party.
>
I think the Council will need to consider where it wants to draw the
lines on something like this. Here is my sense of how these sorts
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 remai
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 co
