[request-tracker-maintainers] Re: Bug#400655: request-tracker3.6:
search by requestor broken
Niko Tyni
ntyni at iki.fi
Tue Dec 12 21:11:49 CET 2006
On Tue, Dec 12, 2006 at 04:53:32PM +0100, Toni Mueller wrote:
> > this is probably because of the Alioth upgrade in October, where
> > the old svn.debian.org (costa) was merged with alioth.debian.org
> > (haydn).
>
> I made enough progress to upload an updated 3.6 package, but would like
> your ideas first before going to the Alioth maintainers:
>
> I had the right password, but it usually takes 3-5 attempts to get it
> accepted (cut&paste, no chance for typos). Any idea what that could
> be?
I assume that's with svn-buildpackage, which is actually a script
that makes several svn+ssh connections while doing it's work.
You get prompted for a password every time, since there's no caching.
The only way around that is to use RSA keys and ssh-agent, and the
authorized_keys file is managed with the web interface nowadays.
(I think you can edit it, but the changes will get overwritten from cron.)
> Also, if you have some experience dealing with the release managers,
> I'd like your advice about how to convince them to take a look. :-|
Well, the only question is whether #400655 can be classified as
severity:important. The other change is a documentation update, and
that's explicitly OK.
Important is defined [1] as
a bug which has a major effect on the usability of a package, without
rendering it completely unusable to everyone.
which I do think can be justified in this case. If you agree, I suppose
we just upgrade the bug with an explanation and contact debian-release.
I'm not sure if the 10-day rule for urgency=low uploads applies, but I
guess it's better to contact the release team sooner than later.
[1] http://www.debian.org/Bugs/Developer#severities
Cheers,
--
Niko
More information about the pkg-request-tracker-maintainers
mailing list