Richard Freeman <rich@...> posted
44FB0741.8050305@..., excerpted below, on Sun, 03 Sep 2006
> FYI - I had the bug with stable timidity - I'm still rebuilding and
> don't want to mess up my --resume list, so I'll post on how well ~amd64
> works for this package in a few days. I'm otherwise stable.
> Note I believe that typically it would be policy not to mark this
> package stable as it is brand new and not stable on any arch. On the
> other hand, the fact that the stable version of the package doesn't work
> might change things. I guess the other approach would be to
> de-stabilize the non-working ebuild.
The normal policy, for which there are exceptions and from which an
individual maintainer can diverge, is 30 days in ~arch without bugs
(enhancement level bugs and the like excluded, of course).
The current ~arch timidity++ has been in portage at least since January,
since as I noted, that's when I appear to have merged it. Thus, it's well
past the 30-day period. I haven't checked to see how many bugs may still
be open on it besides the stabilize request bug, but it's certainly not
brand new in terms of the 30-day policy.
As for keywording:
timidity++-2.13.2: amd64 arm hppa ppc sparc x86
timidity++-2.13.2-r2: ~amd64 ~arm ~ppc ppc64 ~sparc ~x86
So the -r2 that's ~amd64 is already stable on ppc64.
$herdstat -m timidity++
Description: A handy MIDI to WAV converter with OSS and ALSA output support
So there's no maintainer listed, sound herd. Checking the changelog,
corsair is the dev that did the ppc64 keywording.
$herdstat -d corsair
Herds(2): ppc ppc64
So he's a ppc/ppc64 arch-team member, not a sound herd member, and it's
safe to say that it was keyworded by the arch, not the sound herd so that
keywording doesn't necessarily mean anything for other archs, beyond the
obvious that one team considered it stable enough to keyword. However,
without a specified maintainer for the package, sound herd may be leaving
keywording up to the archs themselves.
Certainly, there's no indication on the stabilization bug that there are
remaining bugs preventing stabilization. However, all reports on it so
far are x86, so the amd64 team has little to go on until or unless the
arch testers get around to verifying it's stable. If someone running
stable amd64 reports it runs for them, it'll make it that much easier for
the amd64 team to keyword it as such.
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
email@example.com mailing list