Re: Salsa repository request

[Fabian Wolff]

On Sat, Jun 16, 2018 at 02:53:54PM -0400, Sergio Durigan Junior wrote:
> On Saturday, June 16 2018, Fabian Wolff wrote:
> > Could someone please create a 'libantlr3c' repository in the Debian
> > group on Salsa and give me (wolff-guest) write access to it? An empty
> > repository will suffice, I will populate the repository with the
> > history from snapshot.debian.org as well as my own changes.
> 
> Done:
> 
>   https://salsa.debian.org/debian/libantlr3c

Great, thank you.

You see, I am the maintainer of a reverse dependency of libantlr3c
(cvc4). libantlr3c is scheduled for autoremoval on 15 July due to
#900601, and since libantlr3c is currently orphaned, I took it upon
myself to investigate the issue.

I have attempted to fix the issue by removing the non-DFSG-compliant
files. One of the functions that was defined there is needed by other
parts of the code, however, which is why I have provided an
alternative implementation. I know rather little about proper Unicode
string handling, and I have never worked with libicu, which is why
I've attempted a solution in C++. Better solutions are welcome, of
course.

Removing the non-DFSG files changes the public API, so a transition is
necessary. There has also been a new upstream release that changes the
SONAME, so I figured it would be best to combine both of those into a
single transition, which is why I've included the new upstream release
into this QA upload.

I have uploaded the package to Mentors:

  https://mentors.debian.net/package/libantlr3c

I have set the distribution to "experimental", as described in [0].

Sergio, would you be willing to sponsor this upload? I would also be
glad if you could assist me with the rest of the transition process.

Thank you very much!

Best regards,
Fabian

[0] https://wiki.debian.org/Teams/ReleaseTeam/Transitions

Re: RFS: pcapy/0.11.3-1 [ITA]

[Sergio Durigan Junior]

Control: owner -1 !
Control: tags -1 + moreinfo

On Thursday, June 07 2018, eamanu wrote:

> Dear mentors,
>
> I am looking for a sponsor for my package "pcapy"
>
> * Package name: pcapy
> Version : 0.11.3-1
> Upstream Author : Core Security 
> * URL : https://github.com/CoreSecurity/pcapy
> * License : Apache Software License
> Section : python
>
> It builds those binary packages:
>
> python-pcapy - Python interface to the libpcap packet capture library
>
> To access further information about this package, please visit the
> following URL:
>
> https://mentors.debian.net/package/pcapy
>
>
> Alternatively, one can download the package with dget using this command:
>
> dget -x
> https://mentors.debian.net/debian/pool/main/p/pcapy/pcapy_0.11.3-1.dsc
>
> More information about hello can be obtained from https://www.example.com.
>
> Changes since the last upload:
>
> [ Jakub Wilk ]
> * Use canonical URIs for Vcs-* fields.
>
> [ Ondřej Nový ]
> * Fixed VCS URL (https)
> * d/control: Set Vcs-* to salsa.debian.org
> * d/changelog: Remove trailing whitespaces
> * Remove debian/pycompat, it's not used by any modern Python helper
>
> [ Emmanuel Arias ]
> * new upstream version
> * update d/watch to download correctly the last upstream version
> * update d/control to add Maintainer the DPMT
> * update d/control to add me to Uploaders field (Closes: #895787)
> * update debhelper on d/contorl from 5.0.37.2 to 11
> * update Standards-Version from 3.9.2 to 4.1.4 on d/control
> * add Testsuite: autopkgtest-pkg-python on d/control
> * update d/compat from 5 to 11
> * add to copyright file the debian files copyright

Hi Emmanuel,

Thanks for the package, and for your interest in adopting it!  The first
question I have is about the VCS.  I tried finding your commits on the
official Salsa repo, but wasn't able to.  Are you using any other
repository for that?  It's much easier to review the changes when
there's a repository, and I strongly suggest you use the official one
for the packaging.

As for the review, here's what I'd like you to address:

1) d/copyright should follow DEP-5.  Take a look at:

  https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/

and you'll be able to find instructions on the format of the file.  It
shouldn't be too hard for you to convert the existing file.

2) The package doesn't need CDBS anymore, so you can safely remove it
from the Build-Depends line.

3) The "Homepage" field can have a better URL:

  https://www.coresecurity.com/corelabs-research/open-source-tools/pcapy

4) You should consider packaging a Python 3 package, as well as the
Python 2 you're already packaging (in which case you could probably
split the documentation part into its own package).  If Python 3 is not
supported, you should contact upstream and probably file a bug against
it.

5) Any reason why the package has "Suggests: doc-base"?

6) It's a good habit to export the PYBUILD_NAME variable (on d/rules):

  export PYBUILD_NAME=pcapy

This variable tells pybuild what's the name of your project.

7) It's a good idea to use (on d/rules):

  export DEB_BUILD_MAINT_OPTIONS = hardening=+all

since your package is building a shlib.

8) The package is installing the LICENSE file by default, but this is
not needed since we have the d/copyright file.  Therefore, it'd be good
if you could remove this file from the package.  You can do that by
e.g. overriding dh_auto_install and rm'ing the file there.


I think that's basically everything I've spotted.  Please let me know if
you need any help.

Cheers,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/


signature.asc
Description: PGP signature

Re: Salsa repository request

[Sergio Durigan Junior]

On Saturday, June 16 2018, Fabian Wolff wrote:

> Dear mentors,

Hi Fabian,

> I am currently preparing a QA upload for the libantlr3c package.
>
> This package is currently orphaned and not maintained in any packaging
> VCS repository. For this reason, I think it would be a good idea to
> create a repository for this package on Salsa in the Debian group.
> However, since I am not a Debian Developer, I cannot create the
> repository myself.

Good idea.

> Could someone please create a 'libantlr3c' repository in the Debian
> group on Salsa and give me (wolff-guest) write access to it? An empty
> repository will suffice, I will populate the repository with the
> history from snapshot.debian.org as well as my own changes.

Done:

  https://salsa.debian.org/debian/libantlr3c

Cheers,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/


signature.asc
Description: PGP signature

Salsa repository request

[Fabian Wolff]

Dear mentors,

I am currently preparing a QA upload for the libantlr3c package.

This package is currently orphaned and not maintained in any packaging
VCS repository. For this reason, I think it would be a good idea to
create a repository for this package on Salsa in the Debian group.
However, since I am not a Debian Developer, I cannot create the
repository myself.

Could someone please create a 'libantlr3c' repository in the Debian
group on Salsa and give me (wolff-guest) write access to it? An empty
repository will suffice, I will populate the repository with the
history from snapshot.debian.org as well as my own changes.

Thank you!

Best regards,
Fabian

Yuhiu

[Okwui Egbue]

Thanks 

Sent from the my iPhone

Bug#901649: marked as done (RFS: gnucobol/2.2-2)

[Debian Bug Tracking System]

Your message dated Sat, 16 Jun 2018 14:51:02 +0200
with message-id <20180616125102.vipukptapqvd7...@angband.pl>
and subject line Re: Bug#901649: RFS: gnucobol/2.2-2
has caused the Debian Bug report #901649,
regarding RFS: gnucobol/2.2-2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
901649: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901649
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: sponsorship-requests
Severity: normal

Dear mentors,

  I am looking for a sponsor for my package "gnucobol"

 * Package name: gnucobol
   Version : 2.2-2
   Upstream Author : Simon Sobisch, Ron Norman, Edward Hart, Sergey Kashyrin, 
Dave Pitts and Brian Tiffin
 * URL :https://www.gnu.org/software/gnucobol/ 


 * License : mostly GPL3 and LGPL2
   Section : devel

It builds those binary packages:

 gnucobol   - COBOL compiler
 libcob4- COBOL compiler - runtime library
 libcob4-dev - COBOL compiler - development files
 open-cobol - transitional dummy package for gnucobol

  To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/gnucobol 




  Alternatively, one can download the package with dget using this command:

dget -xhttps://mentors.debian.net/debian/pool/main/g/gnucobol/gnucobol_2.2-2.dsc 




  Changes since the last upload:

  * Closes: #901190 (libcob4-dev: removal of libcob4-dev makes files disappear 
from libcob1-dev)

  Regards,
   Ludwin Janvier


--- End Message ---
--- Begin Message ---
On Sat, Jun 16, 2018 at 08:52:36AM +0200, Ludwin Janvier wrote:
>  * Package name: gnucobol
>Version : 2.2-2

>   Changes since the last upload:
> 
>   * Closes: #901190 (libcob4-dev: removal of libcob4-dev makes files 
> disappear from libcob1-dev)

Actual changelog entry is:

+gnucobol (2.2-2) unstable; urgency=medium
+
+  * Add breaks: libcob1-dev (Closes: #901190) 
+  * Add build-deps to rebuild pdf and info 

Thanks for making the docs actually build!

Instead of writing:
[ -f doc/gnucobol.pdf ] && rm doc/gnucobol.pdf || :
you can have:
rm -f doc/gnucobol.pdf


Meow.
-- 
⢀⣴⠾⠻⢶⣦⠀ There's an easy way to tell toy operating systems from real ones.
⣾⠁⢰⠒⠀⣿⡁ Just look at how their shipped fonts display U+1F52B, this makes
⢿⡄⠘⠷⠚⠋⠀ the intended audience obvious.  It's also interesting to see OSes
⠈⠳⣄ go back and forth wrt their intended target.--- End Message ---

Bug#901649: RFS: gnucobol/2.2-2

[Ludwin Janvier]

Package: sponsorship-requests
Severity: normal

Dear mentors,

  I am looking for a sponsor for my package "gnucobol"

 * Package name: gnucobol
   Version : 2.2-2
   Upstream Author : Simon Sobisch, Ron Norman, Edward Hart, Sergey Kashyrin, 
Dave Pitts and Brian Tiffin
 * URL :https://www.gnu.org/software/gnucobol/ 


 * License : mostly GPL3 and LGPL2
   Section : devel

It builds those binary packages:

 gnucobol   - COBOL compiler
 libcob4- COBOL compiler - runtime library
 libcob4-dev - COBOL compiler - development files
 open-cobol - transitional dummy package for gnucobol

  To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/gnucobol 




  Alternatively, one can download the package with dget using this command:

dget -xhttps://mentors.debian.net/debian/pool/main/g/gnucobol/gnucobol_2.2-2.dsc 




  Changes since the last upload:

  * Closes: #901190 (libcob4-dev: removal of libcob4-dev makes files disappear 
from libcob1-dev)

  Regards,
   Ludwin Janvier