Hello Helmut,
On 20.04.2018 20:06, Helmut Grohne wrote:
> I just looked into the package and only then noticed Christoph's upload.
> Let me share a few remarks though:
>
> * The new upstream release is a bit "strange". Even github uses the
>same commit id for both 6.1.5 and 6.1.7. That looks
On Tue, Apr 17, 2018 at 12:04:07PM +0200, Moritz Schlarb wrote:
> I addressed this issue in 6.1.5-2, but since this leads to a new binary
> upload, I can't upload it myself since I'm just a DM.
> My mentor/sponsor Christoph is currently out of the office, so he can't
> do it either.
> So I've uploa
I uploaded Version 6.1.7-1 yesterday. It is currently in the NEW queue.
Christoph
Am 17.04.2018 um 12:04 schrieb Moritz Schlarb:
> Hi Helmut,
>
> I addressed this issue in 6.1.5-2, but since this leads to a new binary
> upload, I can't upload it myself since I'm just a DM.
> My mentor/sponsor Ch
Hi Helmut,
I addressed this issue in 6.1.5-2, but since this leads to a new binary
upload, I can't upload it myself since I'm just a DM.
My mentor/sponsor Christoph is currently out of the office, so he can't
do it either.
So I've uploaded it to https://mentors.debian.net/package/ccnet - maybe
you
Package: libccnet0
Version: 6.1.5-1
Severity: serious
Justification: policy 8.2
libccnet0 contains a python module "ccnet". The Debian policy section
8.2 prohibits shipping soname-independent files with the shared library
package:
| If your package contains files whose names do not change with ea
5 matches
Mail list logo
