Bug#766441: RFA: scala-mode-el -- Emacs major mode for editing scala source code

[Nicholas D Steeves]

Hi Sławomir,

Sławomir Wójcik  writes:

> On 22.05.2020 05:14, Nicholas D Steeves wrote:
>
> I've merged my changes into new repo initialized by gbp import-dsc from 
> the old package, it's here: 
> https://salsa.debian.org/Valdaer/scala-mode-el. Documented all of it in 
> the new changelog entry.
>
> The newly built package is here: 
> https://mentors.debian.net/package/scala-mode-el

Thank you for your work on this package; this one needs a fair bit of
work before it will meet current standards.  Sorry, it's not ready to
sponsor yet.

I'm short on time for the next week, and am exhausted right now, but
here's a very quick review.  Please read it as if I had written "please"
before every point, and sorry it seems terse or vague.  I just wanted to
send you the list of things to work on before I'll have time to review
again--probably in about a week:

Hint to save time: checkout the commit where you merged the upstream
tag, then 'git checkout -b merged-new-upstream-source'.  If ever you
need to rebase you can then rebase against that branch; if you need to
rebase, this will help avoid the sticky mess of non-fastforwarding master
branch that might not be a child of upstream.

Leave the changelog in UNRELEASED state for now.
Push upstream version tags.
Copyright file issues:
  * 2 files stanzas are missing
  * 2 people are missing
  * at least 1 license is missing
  * always dedicate one line to each year[s] copyright_holder_name 
  * "updated license and author" is too vague, and isn't entirely
  accurate (see above).  Also, why did the licenses and authors change?
  Documenting these facts is part of writing a good changelog entry ;-)
  * date ranges can be tricky.  I believe you see the value in combining
  them, but it's also important to guard against false matches.  For a
  small package like this comprehensive detail is expected.
  Silversearcher-ag (or similar) may make it faster to check for (C), ©,
  and Copyright.
Control file issues:
  * revert that section change; editors is correct, lintian's claim
  notwithstanding.  Thank you for reading lintian output, btw.
  * use debhelper-compat 13 (p.s. apt install -t buster-backports
  lintian.  Lintian should have caught this)
  * Standards-Version needs to be updated.  See Debian Policy and its
  upgrading checklist.  Start at the version from the last upload and
  work your way through from there. <- Please defer this until the
  beginning of our next review cycle unless you run out of things to
  do.
  * drop emacs25
  * expand the long description by a line or two (did this version lose
  the ability to send sexps to a scala process?  If so, document it in
  NEWS)  Is it just a boring mode that does very little or does it have
  any outstanding and/or cool features?
- NOTE: if this this new upstream source has less functionality than
the previous one it might be worth documenting the changes.  If it
has a significantly different keymap or workflow, or breaks existing
users' configs then do you think users would appreciate
notification?  If so, read up on the NEWS file (found in
debian/NEWS) and how to use it.
  * missing dummy transitional package, Breaks, and Provides; at present
  an upgrade path has not been provided.
  
elpa-test:
  * nice catch on the ert_eval! :-)

I'll review the changelog in more depth in the next cycle.  eg:

changelog:
  * "Removed old and no longer necessary files" <- removed what, and
  what was it that made it no longer necessary?  Was it part of a larger
  objective?  Was it an upstream change, a change in Debian tooling, a
  change you made, etc.

If you're in a time zone where no one seems to every be active in
#debian-emacs, try #debian-mentors, otherwise someone else on this list
may have the time to point you in the right direction--assuming I'm too
busy.  'hope this list is just the right length, without being too long
or two hard, and that you find the learning process rewarding.  The good
news is that there's a reason for most everything and there should be
high-quality documentation somewhere, the bad news (for people who don't
like to read) is that it's a lot to read and some things can be tricky
to find until one figures out the key words.  Feel free to take as many
breaks and as much time as you need; that said, before 2021 would be
nice--to unblock my ITP for smartparens ;-)


Have fun!
Nicholas


signature.asc
Description: PGP signature

Bug#961314: RFP: python3-s2sphere -- Python implementation of a part of the C++ S2 geometry library

[Emmanuel Arias]

Hi!

I would like to ITP under DPMT umbrella


Cheers,
Arias Emmanuel
@eamanu
yaerobi.com

Processed: owner 961314

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> owner 961314 eam...@yaerobi.com
Bug #961314 [wnpp] ITP: python3-s2sphere -- Python implementation of a part of 
the C++ S2 geometry library
Owner recorded as eam...@yaerobi.com.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
961314: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961314
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: retitle 961314 to ITP: python3-s2sphere -- Python implementation of a part of the C++ S2 geometry library

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 961314 ITP: python3-s2sphere -- Python implementation of a part of 
> the C++ S2 geometry library
Bug #961314 [wnpp] RFP: python3-s2sphere -- Python implementation of a part of 
the C++ S2 geometry library
Changed Bug title to 'ITP: python3-s2sphere -- Python implementation of a part 
of the C++ S2 geometry library' from 'RFP: python3-s2sphere -- Python 
implementation of a part of the C++ S2 geometry library'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
961314: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961314
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#766441: RFA: scala-mode-el -- Emacs major mode for editing scala source code

[Sławomir Wójcik]

On 22.05.2020 05:14, Nicholas D Steeves wrote:

Hi,

Sławomir Wójcik  writes:


Thanks for the quick reply,



You're welcome :-)  I'm happy I was able to--sometimes it may take a
while to reply.


On 21.05.2020 01:30, Nicholas D Steeves wrote:

Sławomir Wójcik  writes:

[snip]

The issue isn't the "repo" so much as continuity with the existing
source package.  Two people's occasional contributions over three years
are valuable, and erasing them from Debian history would be unjust.

I have imported from dsc by gbp-import-dsc in a new fresh repo, so I
should be able to merge my changes(basically replacing all debian/* files)


More or less, but it's a bit more involved than this, because a large
part of the work of maintaining a package is documenting that work.  At
a minimum, this means one must document changes from the previous
version in debian/changelog.  If you're maintaining the package in git
(highly recommended, and also generally expected for team packages),
then "good git hygiene" means each step is contained within a single
commit.

For example, updating a new upstream version should be one commit.
Adopting the package, or adopting it into the team, should be another.
Adding yourself to Uploaders should be another, etc.  As an example of
when it's ok to combine micro operations, I think it's ok to
combine changing debhelper to debhelper-compat and deleting
debian/compat in a "Switch to debhelper-compat $version" step.

Each of these actions must be documented in debian/changelog.

Your changelog entry (everything from the "package-name
(version-debian_revision)…" line at the top, to the " -- Your Name
 `date -R`" line should be appended to the top of the existing
changelog.  Generally I will use 'dch -v$upstream_version-1' for this.

" * Adopt package. (Closes: #ITA-bug-number)" should be the first line
of the entry.  Then "New upstream version." or "New upstream release.",
as you prefer, and additionally closing a bug if there's a bug
requesting a new version.  Then other items.

Finally, you're welcome to update the changelog all at once at the end,
as a separate commit.  Some people prefer to stage individual changelog
lines with the commit associated with the work.  You don't have to
follow that practise if you don't want to, but if you do then "magit"
can be used to do all your work at once, then stage and commit changes
into discrete commits.

All of this information should already be documented at:

   https://www.debian.org/doc/manuals/maint-guide
   https://www.debian.org/doc/manuals/debmake-doc

Please study those guides.  It's also recommended to look at other
packages from our team for hints, and to get a sense of what the
existing conventions are.  Fair warning: I was taught that " * Bump foo"
was an unacceptable practise.

If someone has a link in-hand to one of the conversations about
" * Bump foo" please share it!


-if we want to adhere to EmacsenTeam Addons packaging policy
(https://wiki.debian.org/EmacsenTeam) and I think we should for better
collaboration and consistency then the package name should be changed to
elpa-scala-mode and existing https://packages.debian.org/sid/scala-mode-el
should be marked as transitional dummy package installing new one, right?


The binary package name should be elpa-scala-mode, but the source
package should remain scala-mode-el.

Actually upstream project name is
emacs-scala-mode(https://github.com/hvesalai/emacs-scala-mode
) rather than
scala-mode-el, but I guess binary package name is more important for
debian users and if source package name will stay the same it won't be
such a big deal, right?


Exactly :-)  When I was a new member I also felt a strong inclination to
rename source packages to sate my desire for correctness, but after a
while I came to agree with more experienced developers; they expressed
to me the perspective that it was a waste of time, and after seeing my
packages wait for months in the "Debian NEW queue", waiting for an
ftpmaster to review the package, I came to understand that source
package renames burden the overworked/understaffed ftpmaster team with
extra work, for little gain.

For more info about why the binary package name is important, read the
dh-elpa and dh-make-elpa documentation, and feel free to ask for
clarification if anything there seems unclear.


-upstream version in existing package and most of debian files are very old
or outdated


Yup, that's part of the work of adopting a package that needs work ;-)


Please, let me know what should be done. As I pointed out here:
https://lists.debian.org/debian-emacsen/2020/05/msg00039.html
it would be the best if someone from Debian Emacsen Packaging Team will work
with me on this and other packages but maybe someone else will be
interested to
give his/her opinion.


If you proceed with this ITP I'd like to work with you and/or comaintain
it, because it's a blocker for my smartparens ITP.

That would be great.

Bug#961753: ITP: suru-icon-theme -- Suru icon theme for Lomiri Operating Environment

[Mike Gabriel]

Package: wnpp
Severity: wishlist
Owner: Mike Gabriel 

* Package name: suru-icon-theme
  Version : 20.05
  Upstream Author : Marius Gripsgard 
* URL : https://gitlab.com/ubports/core/suru-icon-theme/
* License : CC-BY-SA-3.0
  Programming Lang: 
  Description : Suru icon theme for Lomiri Operating Environment

 Lomiri Operating Environment is a convergent work shell designed
 for use cases on phone, tablet or desktop devices.
 .
 The Suru Icon Theme is the default icon theme in Lomiri (former Unity8).
 In Ubuntu, the suru-icon-theme bin:pkg is shipped as part of the ubuntu-theme
 src:pkg. The proposal is to share one suru-icon-theme between Debian
 Ubuntu (Desktop) and UBports' Ubuntu Touch.
 .
 See https://bugs.launchpad.net/ubuntu-themes/+bug/1881180 for details.
 .
 The package will be maintained by the Debian UBports team under the
 umbrella of the Debian Desktop Theme Team.
.

Bug#914312: marked as done (ITP: node-istanbuljs -- monorepo containing the various nuts and bolts that facilitate istanbul.js test instrumentation)

[Debian Bug Tracking System]

Your message dated Thu, 28 May 2020 18:38:36 +
with message-id <5b776b81ec8c242361d392333744a...@babelouest.org>
and subject line Re: ITP: node-istanbuljs -- monorepo containing the various 
nuts and
has caused the Debian Bug report #914312,
regarding ITP: node-istanbuljs -- monorepo containing the various nuts and 
bolts that facilitate istanbul.js test instrumentation
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.)


-- 
914312: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914312
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Nicolas Mora 
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name: node-istanbuljs
  Version : 1.x
  Upstream Author : Ben Coe 
* URL : https://github.com/istanbuljs/istanbuljs
* License : ISC
  Programming Lang: JavaScript
  Description : monorepo containing the various nuts and bolts that
facilitate istanbul.js test instrumentation

 This monorepo contains the nuts and bolts utility libraries that
facilitate IstanbulJS test coverage; Why a monorepo?
 + it allows us to more easily test API changes across coupled modules,
e.g., changes to istanbul-lib-coverage potentially have an effect on
istanbul-lib-instrument.
 + it gives us a centralized repo for discussions about bugs and
upcoming features.

This package is required for the package node-jest
--- End Message ---
--- Begin Message ---
Package no longer required--- End Message ---

Bug#914293: marked as done (ITP: node-append-transform -- Install a transform to require.extensions that always runs last)

[Debian Bug Tracking System]

Your message dated Thu, 28 May 2020 18:41:09 +
with message-id <8bcc67f9d2c18277223e842a7ea57...@babelouest.org>
and subject line Re: Subject: ITP: node-append-transform -- Install a transform 
to
has caused the Debian Bug report #914293,
regarding ITP: node-append-transform -- Install a transform to 
require.extensions that always runs last
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.)


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

Package: wnpp
Severity: wishlist
Owner: Nicolas Mora 
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name: node-append-transform
  Version : 1.0.0
  Upstream Author : James Talmage  
(github.com/jamestalmage)

* URL : https://github.com/istanbuljs/append-transform
* License : Expat
  Programming Lang: JavaScript
  Description : Install a transform to require.extensions that 
always runs last


 Install a transform to require.extensions that always runs last, even 
if

 additional extensions are added later
 .
 Node.js is an event-based server-side JavaScript engine.

This package is a dependency for the package node-istanbuljs
--- End Message ---
--- Begin Message ---
Package no longer required for my needs--- End Message ---

Bug#914294: marked as done (ITP: node-default-require-extensions -- Node's default require extensions as a separate module)

[Debian Bug Tracking System]

Your message dated Thu, 28 May 2020 18:39:31 +
with message-id 
and subject line Re: ITP: node-default-require-extensions -- Node's default 
require
has caused the Debian Bug report #914294,
regarding ITP: node-default-require-extensions -- Node's default require 
extensions as a separate module
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.)


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

Package: wnpp
Severity: wishlist
Owner: Nicolas Mora 
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name: node-default-require-extensions
  Version : 2.0.0
  Upstream Author : James Talmage  
(github.com/jamestalmage)

* URL : https://github.com/avajs/default-require-extensions
* License : Expat
  Programming Lang: JavaScript
  Description : Node's default require extensions as a separate 
module


 Handy for require extension authors that want reliable access to the 
default

 extension implementations.
 .
 By the time your extension is loaded, the default extension may have 
already
 been replaced. This provides extensions functionally identical to the 
default
 ones, which you know you can access reliably, no matter what extensions 
have

 been installed previously.
 .
 Node.js is an event-based server-side JavaScript engine.

This package is a dependency for the package node-append-transform
--- End Message ---
--- Begin Message ---
Package no longer reqiured--- End Message ---

Bug#915071: marked as done (ITP: node-memory-streams -- light-weight implementation of the Stream.Readable and Stream.Writable)

[Debian Bug Tracking System]

Your message dated Thu, 28 May 2020 18:37:33 +
with message-id <5cf40726833971ed2d5154393318e...@babelouest.org>
and subject line RE: ITP: node-memory-streams -- light-weight implementation of 
the Stream.Readable and Stream.Writable
has caused the Debian Bug report #915071,
regarding ITP: node-memory-streams -- light-weight implementation of the 
Stream.Readable and Stream.Writable
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.)


-- 
915071: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915071
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Nicolas Mora 
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name: node-memory-streams
  Version : 0.1.3
  Upstream Author : Paul Jackson (http://jaaco.uk/)
* URL : https://github.com/paulja/memory-streams-js
* License : Expat
  Programming Lang: JavaScript
  Description : light-weight implementation of the Stream.Readable
and Stream.Writable

 Memory Streams JS is a light-weight implementation of the
Stream.Readable and
 Stream.Writable abstract classes from node.js. You can use the classes
 provided to store the result of reading and writing streams in memory. This
 can be useful when you need pipe your test output for later inspection
or to
 stream files from the web into memory without have to use temporary
files on
 disk.
 .
 Forked from https://github.com/paulja/memory-streams-js to be modified
so that
  .end() calls emit a finish event.
 .
 Node.js is an event-based server-side JavaScript engine.

This package is required for node-istanbuljs
--- End Message ---
--- Begin Message ---
Package no longer required for my needs--- End Message ---

Processed: Re: ITP: python3-aiohue -- Python3 asyncio package to talk to Philips Hue

[Debian Bug Tracking System]

Processing control commands:

> forcemerge 898408 917079
Bug #898408 [wnpp] ITP: python3-aiohue -- Python3 asyncio package to talk to 
Philips Hue
Bug #917079 [wnpp] ITP: python-aiohue -- Async Python library to control 
Philips Hue
Bug #917079 [wnpp] ITP: python-aiohue -- Async Python library to control 
Philips Hue
Merged 898408 917079

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

Bug#898408: ITP: python3-aiohue -- Python3 asyncio package to talk to Philips Hue

[Jonas Smedegaard]

Control: forcemerge 898408 917079

It seems you are doing duplicate work here.  You probably want to 
coordinate your efforts.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Processed: Re: ITP: python3-aiohue -- Python3 asyncio package to talk to Philips Hue

[Debian Bug Tracking System]

Processing control commands:

> forcemerge 898408 917079
Bug #898408 [wnpp] ITP: python3-aiohue -- Python3 asyncio package to talk to 
Philips Hue
Bug #917079 [wnpp] ITP: python-aiohue -- Async Python library to control 
Philips Hue
Owner changed from Ruben Undheim  to Srujan Kumar 
Bojjam .
Merged 898408 917079

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

Bug#922961: ITP: vorta -- Desktop Backup Client for Borg

[Nicholas D Steeves]

On Tue, May 26, 2020 at 03:59:56PM -0400, Nicholas D Steeves wrote:
> 
> P.S. I suspect this ITP will take a while to resolve, because the
> upstream is very much in the "release a standalone bundle with
> everything vendored" camp..

This was perhaps an unfair assessment.  Things are moving smoothly
upstream now, and I am more optimistic.


signature.asc
Description: PGP signature

Bug#961742: ITP: nsntrace -- perform network trace of a single process by using network namespaces

[Sudip Mukherjee]

Package: wnpp
Severity: wishlist
Owner: Sudip Mukherjee 
X-Debbugs-CC: p...@debian.org

* Package name: nsntrace
  Version : v3 or v4
  Upstream Author : Jonas Danielsson 
* URL : https://github.com/nsntrace/nsntrace
* License : GPL-2+
  Programming Lang: C
  Description : perform network trace of a single process by using network 
namespaces

 Uses Linux network namespaces to perform network traces of a single
 application. The traces are saved as pcap files. And can later be analyzed
 by for instance Wireshark.

Note: This is a reintroduction of the package.

Processed: RFS: dragengine/1.1 -- Drag[en]gine Game Engine

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> block 961635 by 961738
Bug #961635 [wnpp] ITP: dragengine -- Drag[en]gine Game Engine
961635 was not blocked by any bugs.
961635 was not blocking any bugs.
Added blocking bug(s) of 961635: 961738
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
961635: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961635
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#961730: marked as done (ITP: presto -- REpertoire Sequencing TOolkit)

[Debian Bug Tracking System]

Your message dated Thu, 28 May 2020 15:43:22 +0200
with message-id <20200528134322.gp14...@an3as.eu>
and subject line Please do not hide clearly bioinformatics related stuff in 
language teams (Was: Bug#961730: ITP: presto -- REpertoire Sequencing TOolkit)
has caused the Debian Bug report #961730,
regarding ITP: presto -- REpertoire Sequencing TOolkit
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.)


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

Subject: ITP: presto -- REpertoire Sequencing TOolkit
Package: wnpp
Owner: Andreas Tille 
Severity: wishlist

* Package name: presto
  Version : 0.6.0
  Upstream Author : Kleinstein Lab, Yale University
* URL : https://presto.readthedocs.io/
* License : AGPL-3
  Programming Lang: Python
  Description : REpertoire Sequencing TOolkit
 pRESTO is a toolkit for processing raw reads from high-throughput
 sequencing of B cell and T cell repertoires.
 .
 Dramatic improvements in high-throughput sequencing technologies now
 enable large-scale characterization of lymphocyte repertoires, defined
 as the collection of trans-membrane antigen-receptor proteins located on
 the surface of B cells and T cells. The REpertoire Sequencing TOolkit
 (pRESTO) is composed of a suite of utilities to handle all stages of
 sequence processing prior to germline segment assignment. pRESTO is
 designed to handle either single reads or paired-end reads. It includes
 features for quality control, primer masking, annotation of reads with
 sequence embedded barcodes, generation of unique molecular identifier
 (UMI) consensus sequences, assembly of paired-end reads and
 identification of duplicate sequences. Numerous options for sequence
 sorting, sampling and conversion operations are also included.

Remark: This package is maintained by Debian Med Packaging Team at
   https://salsa.debian.org/med-team/presto
--- End Message ---
--- Begin Message ---
Hi Steffen,

well, its probably my fault to not have checked tasks for the string
presto but this name was pretty new to me and I admit I would not have
assumed that something which I consider rather a user application
toolset is prefixed by python3 in the package name.  I'd love that we in
the Debian Med team would agree that it makes no sense to move the
software we are packaging into "random" language teams without really
good reasons.

Currently we have bio-ruby inside the Ruby team since they have asked
for maintaining it (which makes sense since we have no Ruby competence
here).  We have golang-github-biogo-hts-dev in pkg-go team for similar
reasons.  There are also quite some Perl modules maintained by pkg-perl
team and I admit I'm not really happy about having some Perl modules
here and some there.  However, the Uploaders of these packages have at
least discussed this here.

For presto I definitely see no reason and I'd love to move the package
to Debian Med (surely after I have removed my duplicated work - but
I realised that I have at least not written the manpages vainly. ;-) )

I noticed that python3-presto is actually used in changeo as a module
while I was foxussing on the user application.  Once we are touching
the package do we want to split the binary into

   presto   and
   python3-presto

?

I'd volunteer to move the package (which we should do IMHO in any
case) and if you agree also doing the split of the binary package.

Kind regards

   Andreas.

On Thu, May 28, 2020 at 03:22:36PM +0200, Andreas Tille wrote:
> Package: wnpp
> Severity: wishlist
> 
> Subject: ITP: presto -- REpertoire Sequencing TOolkit
> Package: wnpp
> Owner: Andreas Tille 
> Severity: wishlist
> 
> * Package name: presto
>   Version : 0.6.0
>   Upstream Author : Kleinstein Lab, Yale University
> * URL : https://presto.readthedocs.io/
> * License : AGPL-3
>   Programming Lang: Python
>   Description : REpertoire Sequencing TOolkit
>  pRESTO is a toolkit for processing raw reads from high-throughput
>  sequencing of B cell and T cell repertoires.
>  .
>  Dramatic improvements in high-throughput sequencing technologies now
>  enable large-scale characterization of lymphocyte repertoires, defined
>  as the collection of trans-membrane antigen-receptor proteins located on
>  the surface of B cells and T cells. The REpertoire Sequencing TOolkit
>  (pRESTO) is composed of a suite of utilities to handle all stages of
>  sequence processing prior to germline segment assignment.

Bug#961726: OK ! here are the tarballs

[Enrico Zini]

On Thu, May 28, 2020 at 02:49:38PM +0200, Paolo Greppi wrote:

> This certainly makes sense and will be easier to digest by ftp-master 
> (although you'll have two packages in NEW).
> 
> For the tarballs, they are here:
> https://gitlab.eumetsat.int/open-source/PublicDecompWT/-/tags
> (click on the Download icon at the right).

Thanks! I don't see the sense of autogenerating a tarball from git in
order to build a non-native package, though.

Given that I'm also adding a CMakeLists.txt and a pkg-config template on
top of it, I find that using a native package regularly rebase on
upstream's git simplifies my work significantly.

> gitlab works well with uscan, see for example:
> https://codesearch.debian.net/search?q=gitlab+path%3Adebian%2Fwatch&literal=0

Thanks, good tip! I've added a watchfile looking for new tags.


Enrico

-- 
GPG key: 4096R/634F4BD1E7AD5568 2009-05-08 Enrico Zini 

Bug#961730: ITP: presto -- REpertoire Sequencing TOolkit

[Andreas Tille]

Package: wnpp
Severity: wishlist

Subject: ITP: presto -- REpertoire Sequencing TOolkit
Package: wnpp
Owner: Andreas Tille 
Severity: wishlist

* Package name: presto
  Version : 0.6.0
  Upstream Author : Kleinstein Lab, Yale University
* URL : https://presto.readthedocs.io/
* License : AGPL-3
  Programming Lang: Python
  Description : REpertoire Sequencing TOolkit
 pRESTO is a toolkit for processing raw reads from high-throughput
 sequencing of B cell and T cell repertoires.
 .
 Dramatic improvements in high-throughput sequencing technologies now
 enable large-scale characterization of lymphocyte repertoires, defined
 as the collection of trans-membrane antigen-receptor proteins located on
 the surface of B cells and T cells. The REpertoire Sequencing TOolkit
 (pRESTO) is composed of a suite of utilities to handle all stages of
 sequence processing prior to germline segment assignment. pRESTO is
 designed to handle either single reads or paired-end reads. It includes
 features for quality control, primer masking, annotation of reads with
 sequence embedded barcodes, generation of unique molecular identifier
 (UMI) consensus sequences, assembly of paired-end reads and
 identification of duplicate sequences. Numerous options for sequence
 sorting, sampling and conversion operations are also included.

Remark: This package is maintained by Debian Med Packaging Team at
   https://salsa.debian.org/med-team/presto

Re: Processed: ITP: python3-webdavclient – WebDAV client library for Python 3

[jojo]

On 28.05.20 11:57, Debian Bug Tracking System wrote:


Processing commands for cont...@bugs.debian.org:


owner 961715 J0J0 T 

Bug #961715 [wnpp] ITP: python3-webdavclient – WebDAV client library for Python 
3
Owner recorded as J0J0 T .
End of message, stopping processing here.

Please contact me if you need assistance.


Hi Bart,

sorry for sending this ITP twice, there was an email issue on my side. 
You fixed it already by marking the  other one (#961718) as "done" - 
thanks for that, perfect!


One thing: I can't find this (correct version) of the ITP-bug via this 
search engine yet: 
https://wnpp.debian.net/?type%5B%5D=ITA&type%5B%5D=ITP&type%5B%5D=O&type%5B%5D=RFA&type%5B%5D=RFH&type%5B%5D=RFP&project=&description=webdav&owner%5B%5D=yes&owner%5B%5D=no&col%5B%5D=dust&col%5B%5D=age&col%5B%5D=type&col%5B%5D=description&col%5B%5D=users&col%5B%5D=installs&col%5B%5D=owner&col%5B%5D=reporter&sort=project


Will probably be there in a bit, right?

Thanks a lot! Sorry again!

Jojo

Bug#961726: OK ! here are the tarballs

[Paolo Greppi]

This certainly makes sense and will be easier to digest by ftp-master (although 
you'll have two packages in NEW).

For the tarballs, they are here:
https://gitlab.eumetsat.int/open-source/PublicDecompWT/-/tags
(click on the Download icon at the right).

gitlab works well with uscan, see for example:
https://codesearch.debian.net/search?q=gitlab+path%3Adebian%2Fwatch&literal=0

Paolo

Bug#961726: ITP: publicdecompwt -- Wavelet decompression tool for xRIT files from MeteoSat Second Generation

[Enrico Zini]

Package: wnpp
Severity: wishlist
Owner: Enrico Zini 

* Package name: publicdecompwt
  Version : 2.7.2
  Upstream Author : EUMETSAT http://www.eumetsat.int/
* URL : 
https://gitlab.eumetsat.int/open-source/PublicDecompWT
* License : Apache
  Programming Lang: C++
  Description : Wavelet decompression tool for xRIT files from MeteoSat 
Second Generation

 This is a development-only library with the decompression code for
 MeteoSat Second Generation (MSG) images, provided by EUMETSAT.
 .
 It can be used to build software that can read MSG images.


EUMETSAT has finally freed the source code of this library, and I need to
package it as a build-dependency for meteosatlib:
https://github.com/ARPA-SIMC/meteosatlib/

To the best of my understanding, upstream does not distribute tarballs, does
not support shlibs, and provides only a rudimentary Makefile, so I've added a
simple CMakeLists.txt to make it build as Debian tools expect it, and packaged
it as a `-dev`-only native package.


Enrico

Processed: ITP: python3-webdavclient -- WebDAV client library for Python 3

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close 961718
Bug #961718 [wnpp] ITP: python3-webdavclient -- WebDAV client library for 
Python 3
Marked Bug as done
> stop
Stopping processing here.

Please contact me if you need assistance.
-- 
961718: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961718
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#961720: ITP: rhonabwy -- JWK, JWKS, JWS, JWE and JWT library

[Nicolas Mora]

Package: wnpp
Severity: wishlist
Owner: Nicolas Mora 
X-Debbugs-CC: Debian IoT Maintainers


* Package name: rhonabwy
  Version : 0.9.9
  Upstream Author : Nicolas Mora 
* URL : https://github.com/babelouest/rhonabwy
* License : LGPL-2.1
  Programming Lang: C
  Description :  JWK, JWKS, JWS, JWE and JWT library

 Rhonabwy - JWK, JWKS, JWS, JWE and JWT library
 .
  - Create, modify, parse, import or export JSON Web Keys (JWK) and JSON Web
Keys Set (JWKS)
  - Create, modify, parse, validate or serialize JSON Web Signatures (JWS)
  - Create, modify, parse, validate or serialize JSON Web Encryption (JWE)
limited and experimental!
  - Create, modify, parse, validate or serialize JSON Web Token (JWT)
 .
 JWT Relies on JWS and JWE functions, so it supports the same
functionnalities
 as the other 2. JWT functionnalities also support nesting serilization
 (JWE nested in a JWS or the opposite).



signature.asc
Description: OpenPGP digital signature

Bug#961718: ITP: python3-webdavclient -- WebDAV client library for Python 3

[J0J0 T]

Package: wnpp
Severity: wishlist
Owner: J0J0 

* Package name: python3-webdavclient
  Version : 3.14.3
  Upstream Author : Evgeny Ezhov 
* URL : https://github.com/ezhov-evgeny/webdav-client-python-3
* License : MIT
  Programming Lang: Python
  Description : WebDAV client library for Python 3

WebDAV client, based on original package
https://github.com/designerror/webdav-client-python but uses requests
instead of PyCURL

Further information on this packaging:
 - This library is a dependency for discodos, a package I already filed an
   ITP bug for (960698).
 - Thomas Goirand (zigo) from PAPT is already mentoring discodos packaging,
   and agreed to mentoring for this package as well.

Bug#961698: ITP: lomiri-url-dispatcher -- Lomiri Operating Environment service for requesting URLs to be opened

[Mike Gabriel]

Package: wnpp
Severity: wishlist
Owner: Mike Gabriel 

* Package name: lomiri-url-dispatcher
  Version : 0.1.0
  Upstream Author : Marius Gripsgard 
* URL : https://gitlab.com/ubports/core/lomiri-url-dispatcher
* License : LGPL-3
  Programming Lang: C / C++
  Description : Lomiri Operating Environment service for requesting URLs to 
be opened

 Lomiri's URL dispatcher allows applications to request a URL to be
 opened and handled by another process without seeing the list of other
 applications on the system, or starting them inside its own Application
 Confinement.
 .
 Lomiri URL dispatcher is a fork / continuation of Ubuntu's URL dispatcher and
 can be installed alongside of url-dispatcher.
 .
 This packaged is part of the effort of getting the Lomiri Operating Environment
 into Debian.
 

Bug#961716: ITP: orthanc-gdcm -- Transcoder/decoder of DICOM images for Orthanc using GDCM

[Sebastien Jodogne]

Package: wnpp
Severity: wishlist
Owner: Sebastien Jodogne 

* Package name: orthanc-gdcm
  Version : 1.0
  Upstream Author : Sebastien Jodogne 
* URL : https://www.orthanc-server.com/
* License : GPL
  Programming Lang: C++
  Description : Transcoder/decoder of DICOM images for Orthanc using GDCM

This package installs a plugin for Orthanc (lightweight, RESTful Vendor Neutral
Archive for medical imaging). The plugin extends Orthanc with a
transcoder/decoder of DICOM images that is built on the GDCM library, whereas
the built-in transcoder/decoder of Orthanc uses DCMTK.

Processed: ITP: python3-discogs-client -- Python Client for the Discogs API

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> owner 961714 J0J0 T 
Bug #961714 [wnpp] ITP: python3-discogs-client -- Python Client for the Discogs 
API
Owner recorded as J0J0 T .
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
961714: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961714
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: ITP: python3-webdavclient – WebDAV client library for Python 3

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> owner 961715 J0J0 T 
Bug #961715 [wnpp] ITP: python3-webdavclient – WebDAV client library for Python 
3
Owner recorded as J0J0 T .
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
961715: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961715
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#961715: ITP: python3-webdavclient – WebDAV client library for Python 3

[J0J0 T]

Package: wnpp
Severity: wishlist

X-Debbugs-CC: debian-de...@lists.debian.org

* Package name: python3-webdavclient
  Version : 3.14.3
  Upstream Author : Evgeny Ezhov 
* URL : https://github.com/ezhov-evgeny/webdav-client-python-3
* License : MIT
  Programming Lang: Python
  Description : WebDAV client library for Python 3

WebDAV client, based on original package
https://github.com/designerror/webdav-client-python but uses requests
instead of PyCURL

Further information on this packaging:
 - This library is a dependency for discodos, a package I already filed an
   ITP bug for (960698).
 - Thomas Goirand (zigo) from PAPT is already mentoring discodos packaging,
   and agreed to mentoring for this package as well.

Bug#961714: ITP: python3-discogs-client -- Python Client for the Discogs API

[J0J0 T]

Package: wnpp
Severity: wishlist

Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: J0J0 T 
To: Debian Bug Tracking System 
Subject: ITP: python3-discogs-client -- Python Client for the Discogs API
Message-ID: <159065804023.7538.4384819346194240242.reportbug@bird>
X-Mailer: reportbug 7.1.8ubuntu1
Date: Thu, 28 May 2020 11:27:20 +0200
X-Debbugs-Cc: debian-de...@lists.debian.org

Package: wnpp
Severity: wishlist

* Package name: python3-discogs-client
  Version : 2.2.2+jt0.1-1
  Upstream Author : J0J0 T 
* URL : https://github.com/joj0/discogs_client
* License : BSD-2-clause
  Programming Lang: Python
  Description : Python Client for the Discogs API

This fork of the Official Python Client for the Discogs API incorporates two
essential fixes/features:
* Fixes discogs#82 - Exposes X-Discogs-Ratelimit-Remaining header
  (https://github.com/discogs/discogs_client/pull/89)
* add a release to a CollectionFolder
  (https://github.com/discogs/discogs_client/pull/106)

Further information on this packaging:
 - This library is a dependency for discodos, a package I already filed an
   ITP bug for (960698).
 - Thomas Goirand (zigo) from PAPT is already mentoring discodos packaging,
   and agreed to mentoring this package as well.

Bug#959298: marked as done (ITP: php-horde-imap-client -- IMAP client library)

[Debian Bug Tracking System]

Your message dated Thu, 28 May 2020 09:00:10 +
with message-id 
and subject line Bug#959298: fixed in php-horde-imap-client 2.30.1-1
has caused the Debian Bug report #959298,
regarding ITP: php-horde-imap-client -- IMAP client library
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.)


-- 
959298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959298
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Mike Gabriel 

 Package name: Horde_Imap_Client
 Version : 2.29.17
 Upstream Author : Michael Slusarz 
 URL : http://horde.org/
 License : LGPL-2.1
 Programming Lang: PHP
 Description : IMAP client library

 Interface to access IMAP4rev1 (RFC 3501) mail servers. Also supports 
connections to POP3 (STD 53/RFC 1939).
 .
 Unfortunately, this package has recently been removed from Debian
 unstable.
 .
 I am planning to re-upload this package and pick up maintenance of Horde
 in Debian..
--- End Message ---
--- Begin Message ---
Source: php-horde-imap-client
Source-Version: 2.30.1-1
Done: Mike Gabriel 

We believe that the bug you reported is fixed in the latest version of
php-horde-imap-client, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 959...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated php-horde-imap-client 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 27 May 2020 14:30:11 +0200
Source: php-horde-imap-client
Binary: php-horde-imap-client
Architecture: source all
Version: 2.30.1-1
Distribution: unstable
Urgency: medium
Maintainer: Horde Maintainers 
Changed-By: Mike Gabriel 
Description:
 php-horde-imap-client -
Closes: 959298
Changes:
 php-horde-imap-client (2.30.1-1) unstable; urgency=medium
 .
   * Re-upload to Debian. (Closes: #959298).
 .
   * New upstream version 2.30.1
   * debian/copyright:
 + Fix license of Horde_Imap_Client-*/lib/Horde/Imap/Client/Utf7imap.php;
   drop comment.
 + Explain for Horde_Imap_Client-*/lib/Horde/Imap/Client/Socket.php about
   GPL-2+ portions in the code.
   * debian/patches:
 + Rebase 0001-s-PHPUnit_Framework_TestCase-Horde_Test_Case-g.patch.
Checksums-Sha1:
 d1c2b0882ea59c6ce44550d45990c0ceb3b1 2186 
php-horde-imap-client_2.30.1-1.dsc
 c976e951b1acea1e84721824b9c27489ecc14699 263228 
php-horde-imap-client_2.30.1.orig.tar.gz
 558b45e32347e7e42846bde284394adbf9629757 7436 
php-horde-imap-client_2.30.1-1.debian.tar.xz
 fcf42be0581f5727c76e7ed01d2ae274774e761b 223828 
php-horde-imap-client_2.30.1-1_all.deb
 3d3bf0b643bc836233e48209783456d52005b294 6111 
php-horde-imap-client_2.30.1-1_amd64.buildinfo
Checksums-Sha256:
 722f9b20c9b2fa082a38b21479783eb8a23408a67751aa8b03e76ad51104ebc6 2186 
php-horde-imap-client_2.30.1-1.dsc
 61e9af88ebf102693979685477c292a13b46d3a8c6102b725323abc460ceb450 263228 
php-horde-imap-client_2.30.1.orig.tar.gz
 8134bd74e23d67dc5a4e394bffcc2ff04f7c42a06dda181ee5af67f69ee34a69 7436 
php-horde-imap-client_2.30.1-1.debian.tar.xz
 8de9d980d3f918aaa3e0da62e0da1f4a7b0120c8e858bd4d114b9c525df2f99f 223828 
php-horde-imap-client_2.30.1-1_all.deb
 ecebda70618664c371f47e951d5fec61ed2891a9d3b5fa1013ff1f9ab011288c 6111 
php-horde-imap-client_2.30.1-1_amd64.buildinfo
Files:
 8d77a513847803358268684d6daa858b 2186 php optional 
php-horde-imap-client_2.30.1-1.dsc
 030b25f92f70a08c89477d0356ae0732 263228 php optional 
php-horde-imap-client_2.30.1.orig.tar.gz
 1bbc2cb06afdef4fefb96a964a168e87 7436 php optional 
php-horde-imap-client_2.30.1-1.debian.tar.xz
 2ad86f991e62252319bc6f43a84ce8fc 223828 php optional 
php-horde-imap-client_2.30.1-1_all.deb
 ee88c8d457af4f7eb48f5272b2167635 6111 php optional 
php-horde-imap-client_2.30.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAl7OXt8VHHN1bndlYXZl
ckBkZWJpYW4ub3JnAAoJEJr0azAldxsxIS4P/Ah15L/rWbIqJwxiLsFpBFRDxjw/
kJZTYiB5Jx/30FME3cRgX5PqF2Qr0YAN1kflGbnXuvZ8p0ztdDFwDi+Xr9TX/s0b
A+YluXR077ADijo5IaOz/9gwcGi5zhHmAQfpsyuVZzimcQipfSRdIfg6eDIyDZUj
C5n6sbkpb8OfIv/Sv6xFQdxwZYh+HU9lNZpMBjpKqwd5czQBsYZc1l7ErvvDY3et
AZDvMDHsydhLTXxve+7K

Bug#961706: ITP: protonvpn-cli -- command-line client for ProtonVPN

[Francisco Vilmar Cardoso Ruviaro]

Package: wnpp
Severity: wishlist
Owner: Francisco Vilmar Cardoso Ruviaro 

* Package name: protonvpn-cli
  Version : 2.2.2
  Upstream Author : Proton Technologies AG 
* URL : https://github.com/ProtonVPN/linux-cli
* License : GPL-3+
  Programming Lang: Python
  Description : command-line client for ProtonVPN

 ProtonVPN-CLI is a user-friendly command-line tool for accessing
 the Swiss based privacy-focused ProtonVPN VPN service.
 .
 Need a ProtonVPN account to use it: can create one at
 https://protonvpn.com. Free accounts are available, although with
 limited features: only 3 countries (Japan, Netherlands, USA) are
 available with the free plan.
 It can also easily add an extra layer of privacy by activating Tor
 (needs paid plan).