[Debian-med-packaging] Bug#909708: Working tests seem to exist for epcr
Pranav Ballaney
ballaneypranav at gmail.com
Thu Feb 20 17:00:58 GMT 2020
Hi Andreas,
Thanks for looking into this and sending the guide about packages.
I saw the CI page for epcr, and I have a follow-up query about the same - I
had added autopkgtests to altree <https://salsa.debian.org/med-team/altree> the
other day, and I've now added to loki
<https://salsa.debian.org/med-team/loki> as well. So, can CI pages be built
for these packages now? If yes, how?
Also, is it that only after the CI pages are built, should the respective
bugs (#909708 <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909708>
and #909710 <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909710>) be
marked closed? Or is it enough if the tests are working on my local
machine, and can I close them right away?
Thanks a lot for your help.
Pranav
On Tue, Feb 18, 2020 at 8:35 PM Andreas Tille <andreas at fam-tille.de> wrote:
> Hi Pranav,
>
> On Tue, Feb 18, 2020 at 05:07:44PM +0530, Pranav Ballaney wrote:
> > I am Pranav Ballaney, a Biology and Computer Science student from India,
> > and I have recently joined the Debian Med team, primarily writing
> > autopkgtests for various packages.
>
> Thanks for the short introduction here and the interest into the Debian
> Med GSoC / Outreachy project.
> I tried running the tests present in this package, and they seem to
> > work well on my local machine. Can this bug be marked closed now?
>
> Ahhh, perfectly correct. We simply forgot to close this bug in Debian
> changelog the string "Closes: #909706" (see here[1]).
> Since I'm new to Debian's development process, I'm not aware of the
> > procedure to mark a bug resolved. Does it just involve sending a mail to
> > 909706-close at bugs.debian.org?
>
> Exactly. I'm doing this hereby (in CC).
>
> > I would really appreciate if someone could look into this for me. If any
> > more work is needed, I would be happy to work on it.
>
> No, you have properly analysed the situation - which despite beeing
> simple is very helpful anyway.
>
> BTW, to check whether the existing tests are running nicely you could
> have checked here the CI page of the package[2]. I'm just mentioning
> this since it might be helpful for other tests you might develop in
> future.
>
> > Thanks and regards,
>
> Thanks to you for spotting this issue
>
> Andreas.
>
>
> [1] https://www.debian.org/doc/manuals/developers-reference/pkgs.html
> [2] https://ci.debian.net/packages/e/epcr/
>
> --
> http://fam-tille.de
>
ᐧ
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/debian-med-packaging/attachments/20200220/99c69c05/attachment.html>
More information about the Debian-med-packaging
mailing list