Bug#907914: RFS: elpy/1.24.0-1
Package: sponsorship-requests
Severity: normal
Hi Chris, and dear mentors,
I am looking for a sponsor for my package "elpy".
Package name: elpy
Version : 1.24.0-1
URL : https://github.com/jorgenschaefer/elpy
License : GPL-3+
Section : devel
To address the last TODO list submitted for this package: I have not
yet pursued changes to lintian about the Informational message on
"wrong section". I will ask an Emacsen and Policy team member about
where the appropriate place to pursue this issue would be, because I
believe lintian is currently doing the right thing in providing
Informational-level nagging, as if to say "Are you really sure the
declared section is more appropriate?" Yes, I am certain that section
"devel" is most appropriate for an IDE addon ;-)
It builds this binary package:
elpa-elpy - Emacs Python Development Environment
To access further information about this package, please visit the following
URL:
https://mentors.debian.net/package/elpy
Alternatively, one can download the package with dget using this command:
dget -x https://mentors.debian.net/debian/pool/main/e/elpy/elpy_1.24.0-1.dsc
Changes since the last upload:
elpy (1.24.0-1) unstable; urgency=medium
* New upstream version.
* Revert "Compress README.rst with gzip before installing" because
README.rst is only 2.8k and dh_compress already does the right thing
automatically; that is to say, README.rst is not "larger than 4k in
size" (dh_compress(1)) and should not be compressed.
* Exclusively use Python 3 dependencies and configure the use of
/usr/bin/python3 by default. (Closes: #899212)
* debian/README.Debian: Document how Python 2 support is not enabled
in this Debian package.
* debian/debian-autoloads.el:
- Add Debian-specific configuration to default to using Python 3.
- Document this customisation in README.Debian along with instructions
on how to revert this when moving between Python 2 and Python 3
virtualenvs.
- Additionally unset Elpy's custom PYTHONPATH, which is not needed in
packages that use dh-python. Previously Elpy unnecessarily searched
site-lisp/elpa/elpy-1.23.0 for its associated Python modules.
* debian/control:
- Drop python2 dependencies which are no longer needed
for self-tests to pass.
- Put ELPA build-dep section before Python one (more alphabetical).
- Move python3-sphinx build dependency to the section for documentation.
- Add python3-jupyter-console to Suggests. The upstream Elpy project
recommends using Jupyter console for interactive Python.
- Rely on ${elpa:Depends} and drop explicitly declared ones in bin:pkg.
- Rely on ${python3:Depends} to generate dependency on python3-flake8.
- Add build and runtime dependency on flake8, which provides
/usr/bin/flake8. This wrapper script is still used in various places,
and it is part of the flake8 package provided by PyPI/pip.
* Declare Standards-Version: 4.2.1. (No additional changes required)
-- Nicholas D Steeves Mon, 03 Sep 2018 20:08:24 -0400
elpy (1.23.0-1) unstable; urgency=medium
Regards,
Nicholas D Steeves
Bug#907838: RFS: 2 pkgs once part of emacs-goodies-el: bm-el/201808-1, mutt-alias-el/1.5-1
Hi Chris, Thank you for sponsoring this upload! Also, thank you for these comments and critique. By the way, replies to these RFSs are automatically CCed to debian-mentors@d.o https://lists.debian.org/debian-mentors/2018/09/msg00033.html If you would still prefer that I not reply post-RFS, please let me know and I'll stop :-) All but two points have been addressed in my local copies. Response to these follows: On Mon, Sep 03, 2018 at 09:05:54AM +0100, Chris Lamb wrote: > Nicholas, > > Please separate upload requests for different packages regardless of > their origin. > ACK, will do. I estimate a max of a half dozen emacs-goodies-el related RFSs in the next week. > > https://mentors.debian.net/debian/pool/main/b/bm-el/bm-el_201808-1.dsc > > Uploaded. For your next upload please address: > > * Isn't: > > Files: bm-sync.el > Copyright: 2016 Jo Odland > License: GPL-2+ > > .. superfluous, given: > > Files: * > Copyright: 2000-2016 Jo Odland > License: GPL-2+ Personally, I agree. The specifics are: bm.el: 2000-2015 bm-sync.el: 2016 bm-tests.el: no header, could be potentially 2000-2018. * git blame shows a 2013-2015 range. Sean (from the Policy and Emacsen Team) prefers more strict, discrete Copyright dates rather than globby ranges. To be maximally strict requires a Files section for bm.el as well, but other Emacsen Team members ACKed merging it into "Files: *". What approach would you prefer for future RFSs? Cheers, Nicholas signature.asc Description: PGP signature
RFS: python-scp/0.11.0-1 [ITA]
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "python-scp". For some reason the uploaders field on mentors.d.o is Fabian Wolff, so I CC. * Package name: python-scp Version : 0.11.0-1 Upstream Author : James Bardin * URL : https://github.com/jbardin/scp.py * License : LGPL-2.1+ Section : python It builds those binary packages: python-scp - scp module for (Python 2) python3-scp - scp module for paramiko (Python 3) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/python-scp Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/python-scp/python-scp_0.11.0-1.dsc Changes since the last upload: [Ondřej Nový] * d/changelog: Remove trailing whitespaces * Fixed VCS URL (https) * d/control: Set Vcs-* to salsa.debian.org * d/copyright: Use https protocol in Format field * d/watch: Use https protocol * Convert git repository from git-dpm to gbp layout [Emmanuel Arias] * Add me to Uploaders field on d/control * Add to DPTM to Maintainer field on d/control * Adopt the package (Closes: #888215) * Update d/watch file * Update d/compat from 9 to 11 * Update debhelper to >= 11 from d/control * Update Standards-Version from 3.9.6 to 4.1.4 on d/control * Add Testsuite autopkgtest-pkg-python on d/control * Add me to d/copyright Regards, Emmanuel Arias
Re: Bug#907803: closed by Adam Borowski (Re: Bug#907803: RFS: udfclient/0.8.9-1)
Pali Rohár writes: > Ok. So which short names should I use? Because you are describing license texts that are not standard, you get to choose the short name for each one. I would advise choosing names that uniquely characterise each of the different texts you are naming. -- \ “I've always wanted to be somebody, but I see now that I should | `\ have been more specific.” —Jane Wagner, via Lily Tomlin | _o__) | Ben Finney
Re: [Debian-med-packaging] C++ help needed for yellyfish: "error: catching polymorphic type"
Am Montag, den 03.09.2018, 09:18 +0200 schrieb Andreas Tille: > Hi, > > I'm trying to build the latest version of jellyfish which I pushed to > Salsa[1]. Unfortunately I'm running into You can just catch by reference catch(MergeError& e) This is the better approach anyway: https://blog.knatten.org/2010/04/02/always-catch-exceptions-by-referenc e/ best, Gert
Bug#907838: RFS: 2 pkgs once part of emacs-goodies-el: bm-el/201808-1, mutt-alias-el/1.5-1
Nicholas, Please separate upload requests for different packages regardless of their origin. > https://mentors.debian.net/debian/pool/main/b/bm-el/bm-el_201808-1.dsc Uploaded. For your next upload please address: * Isn't: Files: bm-sync.el Copyright: 2016 Jo Odland License: GPL-2+ .. superfluous, given: Files: * Copyright: 2000-2016 Jo Odland License: GPL-2+ * Standards-Version: 4.2.0 → Standards-Version: 4.2.1 > https://mentors.debian.net/debian/pool/main/m/mutt-alias-el/mutt-alias-el_1.5-1.dsc Uploaded. For your next upload please address: * s/mutt/Mutt/ in description(s). * Standards-Version: 4.2.0 → Standards-Version: 4.2.1 * Drop DH_VERBOSE=1 * Tidy the long description; there is a de facto standard of sorts for such lists here or at least prettier ones. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#907803: closed by Adam Borowski (Re: Bug#907803: RFS: udfclient/0.8.9-1)
On Monday 03 September 2018 01:15:28 Adam Borowski wrote: > On Sun, Sep 02, 2018 at 11:37:43PM +0200, Pali Rohár wrote: > > On Sunday 02 September 2018 21:33:03 Debian Bug Tracking System wrote: > > > Nitpick: these warnings are trivial to fix: > > > W: udfclient source: dep5-copyright-license-name-not-unique bsd-2-clause > > > (paragraph at line 37) > > > W: udfclient source: dep5-copyright-license-name-not-unique bsd-2-clause > > > (paragraph at line 62) > > > W: udfclient source: dep5-copyright-license-name-not-unique bsd-4-clause > > > (paragraph at line 149) > > > so it'd be nice if you could get rid of them in the future. Not an > > > important thing, but less noise is good. > > > > How to fix this problem? There are basically 3 different texts of BSD > > licenses in source files. > > You need to give them unique names. If the body of a license is different, > so must be its short name. > > Yeah, that's somewhat unpleasant, but the reason is obvious. Ok. So which short names should I use? I used "bsd-*-clause" name as described in table at: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/#license-short-name -- Pali Rohár pali.ro...@gmail.com
C++ help needed for yellyfish: "error: catching polymorphic type"
Hi,
I'm trying to build the latest version of jellyfish which I pushed to
Salsa[1]. Unfortunately I'm running into
g++ -DHAVE_CONFIG_H -I. -Wall -Wnon-virtual-dtor -I. -I./include -Wdate-time
-D_FORTIFY_SOURCE=2 -Werror -std=c++11 -g -O2
-fdebug-prefix-map=/build/jellyfish-2.2.10=. -fstack-protector-strong -Wformat
-Werror=format-security -c -o sub_commands/count_main.o
sub_commands/count_main.cc
sub_commands/count_main.cc: In function 'int count_main(int, char**)':
sub_commands/count_main.cc:363:28: error: catching polymorphic type 'class
MergeError' by value [-Werror=catch-value=]
} catch(MergeError e) {
^
In file included from sub_commands/count_main.cc:38:
./include/jellyfish/hash_counter.hpp: In instantiation of 'bool
jellyfish::cooperative::hash_counter::double_size(bool) [with Key =
jellyfish::mer_dna_ns::mer_base_static; word = long
unsigned int; atomic_t = atomic::gcc; mem_block_t = allocators::mmap]':
./include/jellyfish/hash_counter.hpp:189:28: required from 'bool
jellyfish::cooperative::hash_counter::handle_full_ary() [with Key =
jellyfish::mer_dna_ns::mer_base_static; word = long
unsigned int; atomic_t = atomic::gcc; mem_block_t = allocators::mmap]'
./include/jellyfish/hash_counter.hpp:167:7: required from 'bool
jellyfish::cooperative::hash_counter::update_add(const Key&, uint64_t, Key&) [with Key =
jellyfish::mer_dna_ns::mer_base_static; word = long
unsigned int; atomic_t = atomic::gcc; mem_block_t = allocators::mmap; uint64_t
= long unsigned int]'
sub_commands/count_main.cc:176:11: required from 'void
mer_counter_base::start(int) [with MerIteratorType
= mer_qual_iterator; ParserType = sequence_qual_parser]'
sub_commands/count_main.cc:151:16: required from here
./include/jellyfish/hash_counter.hpp:216:9: error: catching polymorphic type
'class
jellyfish::large_hash::array_base, long unsigned int, atomic::gcc,
jellyfish::large_hash::unbounded_array, long unsigned int, atomic::gcc, allocators::mmap>
>::ErrorAllocation' by value [-Werror=catch-value=]
} catch(typename array::ErrorAllocation e) {
^
cc1plus: all warnings being treated as errors
My weak attempt to ignore this for the moment via
export DEB_CFLAGS_MAINT_APPEND = -Wno-error=catch-value
in d/rules failed. Any better hint, how to deal with this?
Kind regards
Andreas.
[1] https://salsa.debian.org/med-team/jellyfish
--
http://fam-tille.de
