Hi László,
On Mon, May 21, 2018 at 11:15:13AM +0200, László Böszörményi (GCS) wrote:
> > > Laszlo, before I'll dive deeper into it I'd like to know what you think
> > > about maintaining this package in Debian Python Modules Team. I'd
> > > volunteer to create a Git repository on Salsa and try to
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
6 matches
Mail list logo
