Control: severity -1 important
On Thu, Jul 19, 2018 at 12:16:00PM +0200, JCF Ploemen wrote:
> The original bug reported here - partial failure of cram's test suite -
> seems to be triggered by python-coverage >= 4.5, first uploaded to
> Debian in Februari of 2018 (i.e. roughly 2 years after cram 0
The original bug reported here - partial failure of cram's test suite -
seems to be triggered by python-coverage >= 4.5, first uploaded to
Debian in Februari of 2018 (i.e. roughly 2 years after cram 0.7-1). With
earlier versions of coverage, cram 0.7-1 builds fine. I don't know
whether the bug is i
as not hijacking the package from you. If you do not
plan to care for the package please declare so publicly.
The reason why I was steping in to cram packaging was that due to bug
#897516 [1] with severity serious is affecting three packages of the
Debian Med team (Uploader Afif Elghraoui in CC)
toes. I simply experienced that
people did not responded for a long time and since bug #897516 is now
removing several packages in Debian Med maintenance out of testing,
I felt some action would be needed.
> Possibly due to that I was not online for some
> days. But no problem, I see you maint
On Sun, May 20, 2018 at 2:00 PM Andreas Tille wrote:
> On Thu, May 10, 2018 at 10:00:07AM +0200, Andreas Tille wrote:
> I've uploaded a package with decreased fail-limit and hereby I'm
> decreasing the severity of the bug. Further investigation about the
> failure should be done - possibly by inv
Control: tags -1 help,upstream
Control: forwarded -1 https://github.com/brodie/cram/issues/32
Control: severity -1 serious
On Sun, May 20, 2018 at 01:56:57PM +0200, Andreas Tille wrote:
> Control: severity -1 important
>...
0.7-2 did FTBFS on the buildd, raising severity again:
https://buildd.debian.org/status/package.php?p=cram
> Kind regards
>
>Andreas.
>...
cu
Adrian
--
Control: severity -1 important
On Thu, May 10, 2018 at 10:00:07AM +0200, Andreas Tille wrote:
> so it seems that fail-under is the percentage that is permitted
> to fail. I'm not sure why _encoding.py and __main__.py are
> contributing to the failure count (obviously since some point
> in time).
Hi,
I've checked this bug and found that
root@sputnik:/build/cram-0.7# python-coverage report --fail-under=95
NameStmts Miss Cover
---
cram/__init__.py3 0 100%
cram/__main__.py6 6 0%
cram/_cli.py 74
Source: cram
Version: 0.7-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20180502 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> make[2]: Entering di
10 matches
Mail list logo
