Re: Naming convention for -doc package

[Christopher Hoskin]

Currently lintian is applying the
new-package-should-not-package-python2-module tag to documentation packages
as well.

I've filed a bug report with a patch:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855243

Christopher Hoskin

On 11 February 2017 at 01:51, Ben Finney  wrote:

> Ghislain Vaillant  writes:
>
> > So given your criteria above, you would choose:
> >
> > - python3-pytestqt
> > - python-pytestqt-doc
> >
> > Am I correct?
>
> That allows a future ‘python4-pytestqt’ to use the same documentation.
>
> So far, the overwhelming pattern is that upstream's documentation does
> not come in separate versions for different Python platforms. It's the
> same Py.test QT documentation, regardless of Python version.
>
> The corresponding Debian packages of documentation should not be named
> by any Python version, either.
>
> > Is everyone happy with that?
>
> I am.
>
> --
>  \ “Smoking cures weight problems. Eventually.” —Steven Wright |
>   `\   |
> _o__)  |
> Ben Finney 
>
>

Re: Moving off of git-dpm (Re: git-dpm breakage src:faker)

[Nikolaus Rath]

On Feb 14 2017, Scott Kitterman  wrote:
> How does dgit avoid maintainer forgot to push problems without being
> limited to the granularity of one commit per upload?

It does not. Until 'dgit push' is called the next time, it will revert
to one commit per upload for the "dark" period.

I am not sure if the next dgit push will retroactively fix history, or
only affect changes that have not yet been uploaded.

Best,
-Nikolaus

-- 
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

 »Time flies like an arrow, fruit flies like a Banana.«