Re: [gentoo-dev] ALLARCHES and the maintainer action(s)
Hi! On Sat, 19 Sep 2015, Agostino Sarubbo wrote: > The ALLARCHES keyword is out since some time. For who does not > remeber, the announcement is here [1] > > So, if an arch developer tests the package(s) on one > architecture, he is allowed to stabilize/keyword for all. This can lead to an interesting effect: arch_A maintainer sees ALLARCHES keyworded bug, and tests everything on A. Upon keywording and running repoman, she finds that two other arches need additional deps. What to do? The only feasible thing is to keyword for A and remove the ALLARCHES keyword from the bug (and add a comment to that effect). Anything that involves more work than that will result in maintainer mikado: whoever first touches the bug is stuck with it. As a result, these bugs will rot much longer than is useful. If anything, I'd say that the _maintainer_ can go ahead and stabilize on all[0] arches after the first arch-specific stabilization. Thus owning the decision and possible fallout. Regards, Tobias [0] I am pretty sure some arches will want to opt out of this scheme, at least for some more critical packages. -- Sent from aboard the Culture ship OU I Said, I've Got A Big Stick
Re: [gentoo-dev] ALLARCHES and the maintainer action(s)
On Sat, 19 Sep 2015 14:24:25 +0200 Agostino Sarubbo wrote: > Unfortunately some people forget to look at the KEYWORDS field and > stabilize the package only for one architecture. Funny to see how you use "forget" here. How about, laugh at and ignore? > At this point I'm asking maintainer(s) to stabilize/keyword their > packages when an arch developer made a stabilization and forget to do > the task for all arches. > > In this way you give an hand to the arch teams. No, you don't. I'll just call that "stabilisation theatre" (harking back to "security theatre") and leave it at that. jer
Re: [gentoo-dev] ALLARCHES and the maintainer action(s)
Saturday 19 Sep 2015 09:55:14, Anthony G. Basile wrote : > On 9/19/15 8:56 AM, Ian Stakenvicius wrote: > > Sent from an iPhone, sorry for the HTML... > > > > On Sep 19, 2015, at 8:31 AM, Vadim A. Misbakh-Soloviov > > wrote: > > > >>> So, if an arch developer tests the package(s) on one architecture, he is > >>> allowed to stabilize/keyword for all. > >> And how about the > >>> some arches rquires additional tests during stabilization, like so: mips*, > >> arm*, and some more exotic ones > >> definition in developer manuals? :) > >> > >> -- > >> Best regards, > >> mva > > The ALLARCHES keyword is meant for stuff that is essentially > > platform-agnostic. Python code shouldn't act any different on arm than > > arm64 than amd64. Using that keyword on something like ffmpeg would be a > > bad use of the keyword. > > Even with python where, for example, `import ctypes' might trigger > something on one arch and not another. Anyhow, thanks for the reminder > ago. I see that keyword as "risky" but an unfortunate risk we have to > take because we are short of manpower and don't have automated arch > testing. I say use it where it appears reasonable (eg interpreted > script and not compiled code) but be ready that every once in a while > we'll get bitten. > > -- > Anthony G. Basile, Ph.D. > Gentoo Linux Developer [Hardened] > E-Mail: bluen...@gentoo.org > GnuPG FP : 1FED FAD9 D82C 52A5 3BAB DC79 9384 FA6E F52D 4BBA > GnuPG ID : F52D4BBA > > We've been using this keyword fairly often (we = Gentoo Java team) whenever possible since the announcement and it worked out pretty well so far. -- Patrice Clement Gentoo Linux developer http://www.gentoo.org
Re: [gentoo-dev] ALLARCHES and the maintainer action(s)
On 9/19/15 8:56 AM, Ian Stakenvicius wrote: Sent from an iPhone, sorry for the HTML... On Sep 19, 2015, at 8:31 AM, Vadim A. Misbakh-Soloviov wrote: So, if an arch developer tests the package(s) on one architecture, he is allowed to stabilize/keyword for all. And how about the some arches rquires additional tests during stabilization, like so: mips*, arm*, and some more exotic ones definition in developer manuals? :) -- Best regards, mva The ALLARCHES keyword is meant for stuff that is essentially platform-agnostic. Python code shouldn't act any different on arm than arm64 than amd64. Using that keyword on something like ffmpeg would be a bad use of the keyword. Even with python where, for example, `import ctypes' might trigger something on one arch and not another. Anyhow, thanks for the reminder ago. I see that keyword as "risky" but an unfortunate risk we have to take because we are short of manpower and don't have automated arch testing. I say use it where it appears reasonable (eg interpreted script and not compiled code) but be ready that every once in a while we'll get bitten. -- Anthony G. Basile, Ph.D. Gentoo Linux Developer [Hardened] E-Mail: bluen...@gentoo.org GnuPG FP : 1FED FAD9 D82C 52A5 3BAB DC79 9384 FA6E F52D 4BBA GnuPG ID : F52D4BBA
Re: [gentoo-dev] ALLARCHES and the maintainer action(s)
Sent from an iPhone, sorry for the HTML... On Sep 19, 2015, at 8:31 AM, Vadim A. Misbakh-Soloviov wrote: >> So, if an arch developer tests the package(s) on one architecture, he is >> allowed to stabilize/keyword for all. > > And how about the >> some arches rquires additional tests during stabilization, like so: mips*, > arm*, and some more exotic ones > definition in developer manuals? :) > > -- > Best regards, > mva The ALLARCHES keyword is meant for stuff that is essentially platform-agnostic. Python code shouldn't act any different on arm than arm64 than amd64. Using that keyword on something like ffmpeg would be a bad use of the keyword.
Re: [gentoo-dev] ALLARCHES and the maintainer action(s)
> So, if an arch developer tests the package(s) on one architecture, he is > allowed to stabilize/keyword for all. And how about the > some arches rquires additional tests during stabilization, like so: mips*, arm*, and some more exotic ones definition in developer manuals? :) -- Best regards, mva signature.asc Description: This is a digitally signed message part.
[gentoo-dev] ALLARCHES and the maintainer action(s)
Hello, The ALLARCHES keyword is out since some time. For who does not remeber, the announcement is here [1] So, if an arch developer tests the package(s) on one architecture, he is allowed to stabilize/keyword for all. Unfortunately some people forget to look at the KEYWORDS field and stabilize the package only for one architecture. At this point I'm asking maintainer(s) to stabilize/keyword their packages when an arch developer made a stabilization and forget to do the task for all arches. In this way you give an hand to the arch teams. Thanks in advance. [1]: https://archives.gentoo.org/gentoo-dev/message/5d96b51ced1d1ed126951f117c828482 -- Agostino Sarubbo Gentoo Linux Developer
