Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 907423 - sci-geosciences/josm-bin-18700: stabelreq
Summary: sci-geosciences/josm-bin-18700: stabelreq
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Stabilization (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Henning Schild
URL:
Whiteboard:
Keywords: CC-ARCHES, STABLEREQ
Depends on:
Blocks:
 
Reported: 2023-05-30 16:42 UTC by Henning Schild
Modified: 2023-06-26 17:47 UTC (History)
3 users (show)

See Also:
Package list:
sci-geosciences/josm-bin-18700
Runtime testing required: ---
nattka: sanity-check+


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Henning Schild 2023-05-30 16:42:39 UTC
please stabilize

Reproducible: Always
Comment 2 Henning Schild 2023-05-31 17:53:05 UTC
(In reply to Mike Gilbert from comment #1)
> https://devmanual.gentoo.org/keywording/index.html#moving-from-arch-to-arch

not sure i understand what you want to point me to
Comment 3 Joonas Niilola gentoo-dev 2023-06-01 16:29:03 UTC
I _guess_ you could've pre-populate the package list, and add CC-ARCHES Keyword? 
pkgcheck looks fine:
  StableRequest: version 18700: slot(0) no change in 34 days for unstable keywords: [ ~amd64, ~x86 ]
Comment 4 Arthur Zamarin archtester Gentoo Infrastructure gentoo-dev Security 2023-06-01 17:08:12 UTC
x86 done
Comment 5 Arthur Zamarin archtester Gentoo Infrastructure gentoo-dev Security 2023-06-01 17:09:43 UTC
amd64 done

all arches done
Comment 6 Matt Turner gentoo-dev 2023-06-01 17:57:50 UTC
(In reply to Henning Schild from comment #2)
> (In reply to Mike Gilbert from comment #1)
> > https://devmanual.gentoo.org/keywording/index.html#moving-from-arch-to-arch
> 
> not sure i understand what you want to point me to

He's telling you that you're doing it wrong and to read the instructions that explain how to do it right :)
Comment 7 Henning Schild 2023-06-26 14:59:16 UTC
for some reason we lost x86 with https://github.com/gentoo/gentoo/commit/4db38aeac6bc3d2c3ce389c5e69c73d3303ae1cb on the way, looking at the latest stable bug only amd64 was done

I wonder why and can not find an answer.

Arthur maybe you can point me to the reasoning and maybe we can align that again. It is java so "there is no arch" really.
Comment 8 Arthur Zamarin archtester Gentoo Infrastructure gentoo-dev Security 2023-06-26 16:56:30 UTC
(In reply to Henning Schild from comment #7)
> for some reason we lost x86 with
> https://github.com/gentoo/gentoo/commit/
> 4db38aeac6bc3d2c3ce389c5e69c73d3303ae1cb on the way, looking at the latest
> stable bug only amd64 was done
> 
> I wonder why and can not find an answer.
>
> Arthur maybe you can point me to the reasoning and maybe we can align that
> again. It is java so "there is no arch" really.


We are working on easing the stable work size for 32 bit arches (x86, arm, ppc). As part of that patchset, we have destabilized most of sci-*/* for x86 and ppc.

*My main question* - is there a need for this package to be stable on x86? If you use it and you say "yes", good enough reason for me (no need to explain, just say).

This package is simple to stabilize on x86 (just java as dep tree), so I don't really care. It can be done as straight revert to my commit (no need to go through the full cycle).
Comment 9 Henning Schild 2023-06-26 17:47:26 UTC
I am the maintainer and was curious why i suddenly had a diversion between the two arches. On amd64 i am also a user.

Now i know it is about phasing out 32bit and that is fine with me, no need to revert.