Hi again,
I did not expected to do any more on this issue since the bug was fixed
quickly. Unfortunately the build failed on s390x (see my mail to
debian-devel) and we are now ending up with a package that is IMHO
affected by a "testing removal" warning for no good reason.
Was there any outcome on your discussion of the severity of those
bugs (and where did this discussion happened - I can not find anything
on debian-devel or debian-ci list)?
I'm tempted to set the bug severity to normal (or if you want important
whatever you decide) but I think removing bart from testing because the
autopkgtest is not marked superficial is not rectified (I'm fine to give
reasons for my opinion in an open discussion if needed - please CC me
if its on debian-ci list since I'm not subscribed).
Kind regards
Andreas.
On Thu, Sep 10, 2020 at 11:57:37AM +0200, Andreas Tille wrote:
> Hi Sudip,
>
> On Thu, Sep 10, 2020 at 10:45:07AM +0100, Sudip Mukherjee wrote:
> > Apologies for not mentioning it as 'serious' bug in my mass-bug mail
> > on debian-devel. That was my first mass-bug mail and I was wondering
> > what I have missed in it. :(
>
> No need to apologize. Its great that you care for the issue in
> principle. BTW, gnumed-client has a similarly primitive test. I fixed
> this in Git[1] and it will be fixed with next upstream version which
> will happen quite regularly. So if you stumble upon this one there is
> no need to spent time on drafting a bug report.
>
> > Thanks for pointing it out, I will let Paul and his team to decide if
> > it should be serious or important and will mention accordingly in my
> > next mass-bug mail.
>
> Thanks again
>
> Andreas.
>
>
> [1]
> https://salsa.debian.org/med-team/gnumed-client/-/commit/cb8677c80b6a0e8b4f92c434c1b95461199331d9
>
>
> --
> http://fam-tille.de
--
http://fam-tille.de
