[gentoo-dev] De-stabilizing and re-stabilizing (on amd64 only)

[gentoo-dev] De-stabilizing and re-stabilizing (on amd64 only)

[Andreas K. Hüttel]

[-- Attachment #1: Type: text/plain, Size: 868 bytes --]

Hi all, 

quite some packages were un-stabilized across the tree recently. 

In general that is in my opinion a good thing if it helps us keep up, in 
particular where many arches are involved.

What's the general opinion on re-stabilizing things on *amd64* only?

I would say that maintaining a larger stable tree is comparatively easy there, 
since everyone of us devs is running (I guess) an amd64 machine and can 
stabilize own packages.

Background, I tried to locally emulate www.g.o using jekyll, and ran into 
troubles because lots of dev-ruby/* lost stable keywords. Newest ~arch didn't 
do the job, so I needed to figure out the config of www.g.o (corresponding to 
former stable) first... 

Cheers, 
Andreas

-- 
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer 
(council, qa, toolchain, base-system, perl, libreoffice)

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [gentoo-dev] De-stabilizing and re-stabilizing (on amd64 only)

[Hans de Graaff]

[-- Attachment #1: Type: text/plain, Size: 572 bytes --]

On Fri, 2020-05-08 at 13:33 +0300, Andreas K. Hüttel wrote:
> 
> Background, I tried to locally emulate www.g.o using jekyll, and ran
> into 
> troubles because lots of dev-ruby/* lost stable keywords. Newest
> ~arch didn't 
> do the job, so I needed to figure out the config of www.g.o
> (corresponding to 
> former stable) first... 

I'm not aware of amd64 stable keywords being lost in dev-ruby, other
than dev-ruby/rails a long time ago. Which packages did you get in
trouble with?

And you can always file a stable bug for the maintainers :-)

Hans

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]