On Thu, 2004-03-11 at 03:59, Björn Stenberg wrote:
> Grzegorz B. Prokopski wrote:
> > I used to think that I would never ask such questions, but I am looking
> > for 10th time in last 3 days at:
> > http://bjorn.haxx.se/debian/testing.pl?package=sablevm
> >
> > And I still cannot understand why packages built from sablevm source
> > (sablevm, libsablevm1, libsablevm-dev, jikes-sablevm) cannot migrate to
> > testing along with packages built from sablevm-classlib
>
> It looks to me like they simply need to be hinted together.
> Since you cc:d debian-release, I'm sure someone will look into it.
Apparenty it's been done. Thanks Steve!
> I have been thinking about trying to make my script detect when hinting
> is needed, but it's a tricky problem and not at the top of my todo list.
I can only guess that if it was possible to detect when hinting is
needed, then hinting wouldn't be needed at all, as it could simply
become part of testing scripts mechanism :-)
> I have changed one of the explanation texts slightly, from "As soon as
> all other dependencies are solved, the two packages can go in together"
> to "As soon as all other dependencies are solved, the two packages can
> be hinted to go in together". I'm unsure if I should tell people to mail
> debian-release about it, as it could produce unwanted noise on the list.
> (Opinions from the list?)
I don't know how many packages are in similar situation to sablevm set.
Note that there _is_ a version of sablevm in testing, so you cannot
estimate this number by simply looking at what packages are not in
testing even though there's no RC bugs against them. I think that at
least an information like that would be in order:
"If you think your package might be held in unstable even though it
should have migrated to testing, as the above output doesn't show
valid obstackles, then you might want to contact debian-release to
explain the situation and possibly add "hints" to the testing scripts
which would allow this and next versions of your package to migrate
as they should."
Uh... break this in a couple sentences. I think I read too much /. ;-)
Thanks for the help,
Grzegorz B. Prokopski
