Bug#921408: RFS: python-bacpypes/0.17.5-1 [ITP]

2019-02-04 Thread Rob Wiesler
Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "python-bacpypes"

 * Package name: python-bacpypes
   Version : 0.17.5-1
   Upstream Author : Joel Bender
 * URL : https://github.com/JoelBender/bacpypes
 * License : Expat
   Section : python

It builds those binary packages:

python-bacpypes - BACnet application and network layer in Python
python3-bacpypes - BACnet application and network layer in Python

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

https://mentors.debian.net/package/python-bacpypes

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

dget -x 
https://mentors.debian.net/debian/pool/main/p/python-bacpypes/python-bacpypes_0.17.5-1.dsc

Changes since the last upload:

* Initial release (Closes: #921395)

Regards,
Rob Wiesler



Bug#921403: RFS: pyfltk/1.3.4.1-1 [ITP]

2019-02-04 Thread Paul Wise
On Tue, Feb 5, 2019 at 10:27 AM Robert Arkiletian wrote:

>   Alternatively, one can download the package with dget using this command:
>
> dget -x 
> https://mentors.debian.net/debian/pool/main/p/pyfltk/pyfltk_1.3.4.1-1.dsc

Here is a review:

>   More information about pyfltk can be obtained from https://www.example.com.

This appears to be incorrect :)

I'm not sure but I don't think Python documentation packages are meant
to be renamed when moving to Python 3. If you prefer to do so then
you'll need to rename the debian/python-fltk-doc.* files.

You have dropped debian/install, does the package still build
correctly without this?

You have changed the author in debian/patches/no_docs, which is meant
to indicate the author of the patch, not the current maintainer of the
package.

You have dropped debian/patches/platform_startswith, but I think that
should have been updated to apply to the new version instead.

The debian/changelog file has UNRELEASED at the top but it should have unstable.

debian/changelog is missing other changes that have been made to the package.

I suggest using the debhelper-compat mechanism instead of
debian/compat, and using debhelper compat level 12 instead of 10. I
chose 12 because that is the latest version of debhelper in Debian
backports. You also have a different version in debian/compat and the
debian/control Build-Depends, they should be the same (or just switch
to using debhelper-compat to avoid the version duplication).

https://manpages.debian.org/unstable/debhelper/debhelper.7.en.html#COMPATIBILITY_LEVELS

You have opted to bump the Python dependency versions to 3.7, does
pyfltk really need such a high version of Python? Using inflated
dependency versions limits backportability of the package.

You will need to unarchive and re-open the bugs closed in a +rm
version here, and then close them in debian/changelog if the version
you are uploading fixes those bugs. Seems like #866915 has been fixed
and #849973 would be easy to fix.

https://bugs.debian.org/cgi-bin/pkgreport.cgi?archive=both;src=pyfltk

I'm guessing python3-fltk-dbg can be dropped in favour of the
automatic debug symbols packages.

https://wiki.debian.org/AutomaticDebugPackages

You have removed the Standards-Version from debian/control, please
restore it, read the upgrading checklist, make any changes needed and
then update Standards-Version to the version of Debian Policy that the
package complies with.

https://www.debian.org/doc/debian-policy/upgrading-checklist

I think override_dh_strip can be removed from debian/control if it
isn't going to be used.

I suggest running this command to make diffs of the Debian packaging
easier to read:

wrap-and-sort --short-indent --wrap-always --sort-binary-packages
--trailing-comma --dry-run

The debian/watch file doesn't work:

https://qa.debian.org/watch/sf.php/pyfltk/

$ uscan --verbose

scan info: Newest version of pyfltk on remote site is 1.3.0, local
version is 1.3.4.1
uscan info:=> Only older package available from
  https://qa.debian.org/watch/sf.php/pyfltk/pyFltk-1.3.0.tar.gz

Automated checks:

lintian: lots of warnings/errors

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



Bug#921405: RFS: pyfltk/1.3.4.1-1 [ITA]

2019-02-04 Thread Robert Arkiletian
Package: sponsorship-requests
  Severity: normal [important for RC bugs, wishlist for new packages]

  Dear mentors,

  I am looking for a sponsor for my package "pyfltk". Sorry this is my
second post. I failed to set it as ITA. This package use to be in
Debian but was orphaned. I am looking to pick it up as the new
maintainer but need a sponsor. I am a high school CS teacher who needs
the package for my students.

 * Package name: pyfltk
   Version : 1.3.4.1-1
   Upstream Author : Andreas Held
 * URL : http://pyfltk.sourceforge.net/
 * License : LGPL
   Section : python

  It builds those binary packages:

python3-fltk - Python wrapper for the Fast Light Toolkit
python3-fltk-doc - Documentation for pyFltk
python3-fltk-dbg - Python wrapper for the Fast Light Toolkit - Debugging symbols

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

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


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

dget -x 
https://mentors.debian.net/debian/pool/main/p/pyfltk/pyfltk_1.3.4.1-1.dsc

  More information about pyfltk can be obtained from
http://pyfltk.sourceforge.net/


  Regards,
   Robert Arkiletian



Re: my first debian package

2019-02-04 Thread Robert Arkiletian
Looking for a sponsor.

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



Re: my first debian package

2019-02-04 Thread Robert Arkiletian
On Mon, Feb 4, 2019 at 6:13 PM Paul Wise  wrote:
>
> On Tue, Feb 5, 2019 at 7:58 AM Robert Arkiletian wrote:
>
> > Hurray! I built it.
>
> Congrats! Please also check the package with lintian.
>

Will do.



Bug#921403: RFS: pyfltk/1.3.4.1-1 [ITP]

2019-02-04 Thread Robert Arkiletian
Package: sponsorship-requests
  Severity: wishlist

  Dear mentors,

  I am looking for a sponsor for my package "pyfltk". I am a high
school Computer Science teacher. I teach gui programming with pyfltk
so I want to get the package back into Debian.

 * Package name: pyfltk
   Version : 1.3.4.1-1
   Upstream Author : Andreas Held
 * URL : http://pyfltk.sourceforge.net/
 * License : GNU Library General Public License
   Section : python

  It builds those binary packages:

python3-fltk - Python wrapper for the Fast Light Toolkit
python3-fltk-doc - Documentation for pyFltk
python3-fltk-dbg - Python wrapper for the Fast Light Toolkit - Debugging symbols

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

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


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

dget -x 
https://mentors.debian.net/debian/pool/main/p/pyfltk/pyfltk_1.3.4.1-1.dsc

  More information about pyfltk can be obtained from https://www.example.com.


  Regards,
   Robert Arkiletian



Re: my first debian package

2019-02-04 Thread Paul Wise
On Tue, Feb 5, 2019 at 7:58 AM Robert Arkiletian wrote:

> Hurray! I built it.

Congrats! Please also check the package with lintian.

> How do I sign the dsc and changes files with gpg before uploading to
> mentors site with dput.

The intro guide should document that, but it should be enough to run
debsign and debrelease (both from devscripts) .

https://mentors.debian.net/intro-maintainers

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



Bug#910004: RFS: apache-opennlp/1.9.0-1 [ITP] -- machine learning based toolkit for the processing of natural language text

2019-02-04 Thread Mo Zhou
On Mon, Feb 04, 2019 at 03:33:56PM +0200, Andrius Merkys wrote:
> Updated. Could you please try building the package once more?

It compiles now:

http://debomatic-amd64.debian.net/distribution#unstable/apache-opennlp/1.9.1-1/buildlog

However I guess you didn't install all the opennlp components:

http://debomatic-amd64.debian.net/distribution#unstable/apache-opennlp/1.9.1-1/contents
-rw-r--r-- root/root   1236603 2019-02-04 14:04 
./usr/share/java/opennlp-tools.jar
-rw-r--r-- root/root 66535 2019-02-04 14:04 
./usr/share/java/opennlp-uima.jar

I think the expected package content list should contain .jar files for
all these modules:

opennlp-brat-annotator
opennlp-distr
opennlp-docs
opennlp-morfologik-addon
opennlp-tools
opennlp-uima

Besides, there are also some wrapper scripts under several directories.
Are they omitted intentionally?

❯❯❯ find . -type d -name bin
./opennlp-tools/bin
./opennlp-brat-annotator/src/main/bin
./opennlp-morfologik-addon/bin
./opennlp-morfologik-addon/src/main/bin
./opennlp-distr/src/main/bin



Re: my first debian package

2019-02-04 Thread Robert Arkiletian
On Sun, Feb 3, 2019 at 7:15 PM Paul Wise  wrote:
...
> Once the package is ready, you can upload it to the mentors site and
> ask for a sponsor. If you have any questions while creating the
> package, you can ask them on this list or on the #debian-mentors IRC
> channel.
>
> https://mentors.debian.net/intro-maintainers
> https://mentors.debian.net/sponsors/rfs-howto
>
Hurray! I built it.

Everything is now updated in the git repo here
https://bitbucket.org/robark/python3-fltk/src/master

How do I sign the dsc and changes files with gpg before uploading to
mentors site with dput.



Bug#921373: RFS: codelite [QA] -- Powerful and lightweight IDE

2019-02-04 Thread Adam Borowski
On Mon, Feb 04, 2019 at 05:11:40PM +, David Hart wrote:
>   * Package name: codelite
> Version : 12.0+dfsg-1

> Changes since the last upload:
> 
> codelite (12.0+dfsg-1) unstable; urgency=medium
> 
>   * QA upload.
> 
>   * New upstream release.
> 
>   * debian/codelite-plugins.install:
> - Install new plugins.
>   * debian/copyright:
> - Add copyright for new plugin.
> - Update copyright dates.
>   * debian/patches:
> - Refresh patches.
> - Backport a fix for LLDB terminal crashes.
> - Fix 3 more spelling mistakes.
>   * debian/control:
> - Bump standards to 4.3.0.
>   * debian/compat:
> - Use debhelper 11.
>   * debian/watch:
> - Add oversionmangle for +dfsg

Your upload would remove the last changelog entry, could you please fix
that?  Otherwise, I see no problems so far.

The issue with VCS would be nice to solve but is not a showstopper.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Remember, the S in "IoT" stands for Security, while P stands
⢿⡄⠘⠷⠚⠋⠀ for Privacy.
⠈⠳⣄



Bug#921226: RFS: austin/0.6.1~beta-1 [ITP]

2019-02-04 Thread Gabriele
Hi

Sorry for not including the bug address in the CC. I have simplified
the debian/rules file
(https://github.com/P403n1x87/austin/commit/655c3beb09199bb9dbe6c9dbdb8395c25e9213c9)
and verified with gbp buildpackage. I have excluded the custom
Makefile from the sources and seems fine to me now.

Please let me know if you want me to re-upload the package with the
latest changes.

Regarding python2, the package doesn't include any python2 code. Even
the python project inside austin/ is compatible with python3. However,
the main C application shipped with the package (which is just the
single binary src/austin) supports both python2 (2.3 - 2.7) and
python3 (3.3 - 3.7).

Thanks,
Gabriele

On Sun, 3 Feb 2019 at 23:31, Adam Borowski  wrote:
>
> On Sun, Feb 03, 2019 at 10:39:09PM +, Gabriele wrote:
> > Hey
> >
> > Many thanks for getting back to me!
>
> Could you please re-add 921...@bugs.debian.org to CC?  (I'm 99.9% sure
> you'll be ok with that but the rule is to never make anything public without
> an explicit permission).  Any such package reviews are supposed to be done
> in public, for a number of reasons:
>  * there's a record of the review
>  * anyone else can chime in
>  * anyone else can continue the review -- I might need to pass if there'll
>be any complex python-specific questions
>  * others can learn
>
> > I have sent the public key to the keyserver as you have suggested.
>
> Great, thanks!  It'll probably take a bit of time for it to propagate.
>
> > Regarding the dependencies you have mentioned, they shouldn't really
> > be such. The tarball includes snapcraft sources for creating artifacts
> > for the snap store (think of this as the analogue of the debian/
> > folder but for another type of repository, https://snapcraft.io/).
> > This tool is then not required for the application to run and to even
> > build.
>
> Yeah, but the build system still calls it.  After your changes at least
> repacking the sources succeeds, but the actual build still fails:
>
>
> Command: dpkg-buildpackage -us -uc -b -rfakeroot
> dpkg-buildpackage: info: source package austin
> dpkg-buildpackage: info: source version 0.6.1~beta-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Gabriele N. Tornetta 
> 
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
>  fakeroot debian/rules clean
> dh clean
>dh_auto_clean
> make -j6 clean
> make[1]: Entering directory '/<>'
> snapcraft clean
> make[1]: snapcraft: Command not found
> make[1]: *** [Makefile:23: clean] Error 127
> make[1]: Leaving directory '/<>'
> dh_auto_clean: make -j6 clean returned exit code 2
>
> > In fact, all that austin requires is a C compiler. Python is
> > only a test dependency as it is invoked during tests. The Makefile
> > included in the tarball is not intended for autogeneration, but just
> > to simplify the testing during development. The package should be
> > built with the standard autoreconf process instead, as I think is
> > currently happening.
>
> Seems like this is the problem:
>
> dpkg-buildpackage: info: source package austin
> dpkg-buildpackage: info: source version 0.6.1~beta-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Gabriele N. Tornetta 
> 
>  dpkg-source --before-build .
>  fakeroot debian/rules clean
> dh clean
>dh_clean
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building austin using existing 
> ./austin_0.6.1~beta.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: warning: ignoring deletion of file Makefile, use 
> --include-removal to override
> dpkg-source: warning: ignoring deletion of file src/Makefile.in, use 
> --include-removal to override
> dpkg-source: warning: ignoring deletion of file src/austin, use 
> --include-removal to override
> dpkg-source: warning: ignoring deletion of file test/test_process_iter.py, 
> use --include-removal to override
> dpkg-source: info: building austin in austin_0.6.1~beta-1.debian.tar.xz
> dpkg-source: info: building austin in austin_0.6.1~beta-1.dsc
>  dpkg-genbuildinfo --build=source
>  dpkg-genchanges --build=source >../austin_0.6.1~beta-1_source.changes
> dpkg-genchanges: info: including full source code in upload
>  dpkg-source --after-build .
> dpkg-buildpackage: info: full upload (original source is included)
>
> The patch system ignores deletions unless specifically told so (there are
> usually nicer ways to get this effect), which apparently results in some old
> version of the Makefile being used.  Normally, dh_autoreconf would generate
> a proper version, but you specifically disable it in debian/rules.  That's
> bad for other reasons as well -- the package won't see improvements from new
> versions of autotools (bug fixes, support for new architectures, etc).
>
> > Please note that I have some local changes that fix some 

Bug#921373: RFS: codelite [QA] -- Powerful and lightweight IDE

2019-02-04 Thread David Hart
Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for an update of the orphaned package "codelite"

  * Package name: codelite
Version : 12.0+dfsg-1
Upstream Author : eranif 
  * URL : https://codelite.org
  * License : GPL2+
Section : devel

It builds these binary packages:

  codelite -- Powerful and lightweight IDE
  codelite-plugins -- Powerful and lightweight IDE - plugins


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

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


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

dget -x 
https://mentors.debian.net/debian/pool/main/c/codelite/codelite_12.0+dfsg-1.dsc

There is also a git repo:
 https://github.com/dghart/debian-salsa-codelite-clone 
which is a clone of
 https://salsa.debian.org/debian/codelite
to which afaict I can't upload.

After being RFA for some time, codelite is now orphaned: see #852312.
It still provides version 10.0, while the upstream version is 12.0. I've
updated the package to 12.0 and made other minor fixes.

This is a request for a review and upload of the update. The amended package
builds and works, and is lintian-clean apart from the warning:
 orphaned-package-not-maintained-in-debian-infrastructure.

Changes since the last upload:

codelite (12.0+dfsg-1) unstable; urgency=medium

  * QA upload.

  * New upstream release.

  * debian/codelite-plugins.install:
- Install new plugins.
  * debian/copyright:
- Add copyright for new plugin.
- Update copyright dates.
  * debian/patches:
- Refresh patches.
- Backport a fix for LLDB terminal crashes.
- Fix 3 more spelling mistakes.
  * debian/control:
- Bump standards to 4.3.0.
  * debian/compat:
- Use debhelper 11.
  * debian/watch:
- Add oversionmangle for +dfsg


Regards,

David Hart



Bug#919614: RFS: note/1.3.26-2 [ITA]

2019-02-04 Thread eamanu15
Hi,

There is proposal (DEP-14) to create tags, like debian/2.1.2-5
> in git repository, that mark state of source package, uploaded in
> archives.
>

I pretend use gbp, I That create the tags and branch
that you mention.

I have a new version 1.3.26-3 applied the fix. I need to create start an
mentors.d.n process
or just I let it know when I ready?

Thanks!
Regards


-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest


Bug#910004: RFS: apache-opennlp/1.9.0-1 [ITP] -- machine learning based toolkit for the processing of natural language text

2019-02-04 Thread Andrius Merkys
Hi Mo Zhou,

On 2019-02-02 10:26, Mo Zhou wrote:
> Thank you for the effort on apache-opennlp packaging. However it failed
> to build (I cannot help you diagnose the failure because I know nothing
> about Java):

I have just fixed the issue.

> BTW, 1.9.1 release is available.

Updated. Could you please try building the package once more?

Best wishes,
Andrius

-- 
Andrius Merkys
Vilnius University Institute of Biotechnology, Saulėtekio al. 7, room V325
LT-10257 Vilnius, Lithuania



Bug#919413: RFS: doxygen/1.8.15-1 [ITA]

2019-02-04 Thread Ole Streicher
Control: severity 921295 important
Control: severity -1 normal

(setting severity of RFS back to normal)

https://release.debian.org/buster/freeze_policy.html

> Transition Freeze
> Starting 2019-01-12, new transitions and large/disruptive changes are no 
> longer acceptable for buster.

I am wondering whether this applies here, given the large number of
packages which don't compile.

Best

Ole