date:20180925

Your message dated Wed, 26 Sep 2018 04:20:12 +
with message-id 
and subject line closing RFP: ssh-installkeys -- Install your ssh keys on 
remote sites
has caused the Debian Bug report #712431,
regarding RFP: ssh-installkeys -- Install your ssh keys on remote sites
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.)


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

* Package name : ssh-installkeys
 Version : 1.8
 Upstream Author: Eric S. Raymond
* URL : http://www.catb.org/~esr/ssh-installkeys/
* License : BSD
Description : Install your ssh keys on remote sites

This script tries to export ssh public keys to a specified site. It
will walk you through generating key pairs if it doesn't find any to
export. It handles all the fiddly details like making sure local and
remote permissions are correct, and tells you what it's doing if it
has to change anything. Unlike some competing tools, you only have to
enter your password once.
--- End Message ---
--- Begin Message ---
RFP 712431 has no visible progress for a long time, so closing.--- End Message ---

Bug#909562: ITP: black -- uncompromising Python code formatter

2018-09-25 Thread Nicholas D Steeves

Hi Neil,

On Tue, Sep 25, 2018 at 09:17:44AM +0100, Neil Williams wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Neil Williams 
> 
> * Package name: black
>   Version : 18.6b4
>   Upstream Author : Łukasz Langa 
> * URL : https://github.com/ambv/black
> * License : BSD-3-Clause
>   Programming Lang: Python
>   Description : uncompromising Python code formatter
[...]
> We'd like to use black as part of code review for LAVA and
> associated python packages. I'm currently investigating if this
> should be maintained by the LAVA team or the Python Modules team.
> 
> The package needs a small patch to remove privacy-breaching tracking URLs
> from the docs.

Thank you for packaging black!  I have subscribed to this bug because
I plan to enable support for it in Elpy (Emacs Python IDE) once black
is in the archive.  Given that its code review functionality is used
outside of LAVA I suspect the Python Modules team would be more
appropriate, but I don't have a strong opinion either way.

Kind regards,
Nicholas

signature.asc
Description: PGP signature

Bug#909610: ITP: eclipse-platform-debug -- Language independent facilities and mechanisms for debugging with the Eclipse platform

2018-09-25 Thread Emmanuel Bourg

Package: wnpp
Severity: wishlist
Owner: Emmanuel Bourg 

* Package name: eclipse-platform-debug
  Version : 4.7.3
  Upstream Author : Eclipse Foundation, Inc.
* URL : https://www.eclipse.org/eclipse/debug/
* License : EPL-1.0
  Programming Lang: Java
  Description : Language independent facilities and mechanisms for 
debugging with the Eclipse platform

The Debug component of the Eclipse platform defines language independent
facilities and mechanisms for:

 * Launching programs
 * Source lookup
 * Defining and registering breakpoints
 * Event notification from programs being debugged
 * A language independent debug model
 * A language independent debug UI

The Debug component does not provide an implementation of a debugger, it
is the duty of other plug-ins to provide language specific implementations
of debuggers.

This package will be maintained by the Java Team. It's required
to transition away from the old src:eclipse package.

Bug#908723: marked as done (ITP: django-auto-one-to-one -- Django module to automatically connect child model instances to parent class)

Your message dated Tue, 25 Sep 2018 19:00:10 +
with message-id 
and subject line Bug#908723: fixed in django-auto-one-to-one 3.0.0-1
has caused the Debian Bug report #908723,
regarding ITP: django-auto-one-to-one -- Django module to automatically connect 
child model instances to parent class
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.)


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

Package: wnpp
Severity: wishlist
X-Debbugs-cc: Chris Lamb 

Cc to the upstream developer.

* Package name: django-auto-one-to-one
  Version : 3.0.0
  Upstream Author : Chris Lamb 
* URL : https://chris-lamb.co.uk/projects/django-auto-one-to-one
* License : BSD-3-clause
  Description : Django module to automatically connect child model 
instances to parent class

This is very useful when associating more information with one of the
Django internal models like User.

I've created draft packaging in the debian branch on
https://github.com/petterreinholdtsen/django-auto-one-to-one > for
my own use.  It still need more work, and someone with the spare time
required to maintain the package in Debian.

-- 
Happy hacking
Petter Reinholdtsen
--- End Message ---
--- Begin Message ---
Source: django-auto-one-to-one
Source-Version: 3.0.0-1

We believe that the bug you reported is fixed in the latest version of
django-auto-one-to-one, 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 908...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated django-auto-one-to-one 
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: Mon, 24 Sep 2018 19:37:55 +0100
Source: django-auto-one-to-one
Binary: python3-django-auto-one-to-one
Architecture: source all
Version: 3.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Chris Lamb 
Description:
 python3-django-auto-one-to-one - Django module to connect child model 
instances to parent class
Closes: 908723
Changes:
 django-auto-one-to-one (3.0.0-1) unstable; urgency=medium
 .
   [ Petter Reinholdtsen ]
   * Initial release. (Closes: #908723)
   * Add Chris as uploader.
 .
   [ Chris Lamb ]
   * debian/control:
 - Set Maintainer to DPMT and move Petter to Uploaders.
 - Set Standards-Version to 4.2.1 and debhelper compat level to 11.
 - Update Vcs-{Git,Browser}
 - Improve long description.
 - Use my Debian email address.
 - wrap-and-sort -sa.
 - Drop Python 2.x build-dependencies.
 - Use autopkgtest-pkg-python as a Testsuite header.
   * Add/update myself in debian/copyright.
   * Drop boilerplate from debian/rules.
   * Drop dh_make boilerplate from debian/watch.
   * Update debian/gbp.conf to reflect DPMT repository layout/policy.
   * Don't complain about debian-watch-does-not-check-gpg-signature.
Checksums-Sha1:
 020c00c3eb39aaedd6196c5ee624a62773e2681d 2242 
django-auto-one-to-one_3.0.0-1.dsc
 ac87276faca9516aea7f18a259ab4cb81e8e 3073 
django-auto-one-to-one_3.0.0.orig.tar.gz
 ef4c8d2ea88d169bbd7e770180cf537f906c3a60 2712 
django-auto-one-to-one_3.0.0-1.debian.tar.xz
 dbfed36d7db023108011b2b417423e1374d35113 6174 
django-auto-one-to-one_3.0.0-1_amd64.buildinfo
 3b22f6e4aa3ee22ccfafb5c4c7d1bd2d6c7d7476 5336 
python3-django-auto-one-to-one_3.0.0-1_all.deb
Checksums-Sha256:
 829e8b638f36f43f6f47419b4e78ec74219e3cfb12402444f322d9a1899f1f52 2242 
django-auto-one-to-one_3.0.0-1.dsc
 b4e1a63883480a11b0714a27681b2d36517ed61b22fa2de0fac342f697b1d654 3073 
django-auto-one-to-one_3.0.0.orig.tar.gz
 0765707d6dea31f4b3e0997196891cb410ef255da19614c811fb29450da6ef0b 2712 
django-auto-one-to-one_3.0.0-1.debian.tar.xz
 a75492d46b20e5b4587e35c0145cc25954e2bb8b6606a3b05222cee3b23b47d4 6174 
django-auto-one-to-one_3.0.0-1_amd64.buildinfo
 cc3238636786da9d367bf29b55f3565b10188e2d3a885da02d13c55105bee574 5336 
python3-django-auto-one-to-one_3.0.0-1_all.deb
Files:
 4890759bf3e6456ff9878bc5d28a0518 2242 python optional 
django-auto-one-to-one_3.0.0-1.dsc
 3c25d4fe5f336d670b902218c27542b2 3073 python

Bug#908511: marked as done (ITP: immutables -- immutable objects and builders generator for Java)

Your message dated Tue, 25 Sep 2018 18:41:49 +0200
with message-id

and subject line Lost interest, closing,...
has caused the Debian Bug report #908511,
regarding ITP: immutables -- immutable objects and builders generator for Java
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.)

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

* Package name: immutables
Version : 2.7.1
Upstream Author : Immutables Authors and Contributors
Ievgen Lukash (e.luc...@gmail.com)
Ilya Vysharev (ivysha...@gmail.com)
Augusto Travillio (augusto.travil...@gmail.com)
* URL : http://immutables.github.io/
https://github.com/immutables/immutables
* License : Apache-2.0
Programming Lang: Java
Description : immutable objects and builders generator for Java

Annotation processor to create immutable objects and builders. Feels
like Guava's immutable collections but for regular value objects.
JSON, Jackson, Gson, JAX-RS integrations included.

Java annotation processors to generate simple, safe and consistent
value objects. Do not repeat yourself, try Immutables, the most
comprehensive tool in this field!
--- End Message ---
--- Begin Message ---
Lost interest into immutables, mainly because it depends on custom
fork of maven shade plugin. The fork should be be incorporated into
maven upstream instead of standalone fork. Sole reason for not doing
so it:

> ... I just couldn't afford time to dive into processes or infrastructure
> there.

Quoted from:
https://github.com/immutables/maven-shade-plugin/blob/4f21777ca83be75e795b7ef87d3ab2772b04c2be/README.md--- End Message ---

Processed: your mail

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

> tags 908602 wontfix
Bug #908602 {Done: Miroslav Kravec } [wnpp] ITP: 
immutables-maven-shade-plugin -- maven-shade-plugin with everything "fixed"
Added tag(s) wontfix.
> tags 908511 wontfix
Bug #908511 [wnpp] ITP: immutables -- immutable objects and builders generator 
for Java
Added tag(s) wontfix.
>
End of message, stopping processing here.

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

Bug#908602: marked as done (ITP: immutables-maven-shade-plugin -- maven-shade-plugin with everything "fixed")

Your message dated Tue, 25 Sep 2018 18:32:06 +0200
with message-id

and subject line Lost interest, closing
has caused the Debian Bug report #908602,
regarding ITP: immutables-maven-shade-plugin -- maven-shade-plugin with
everything "fixed"
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.

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

* Package name: immutables-maven-shade-plugin
Version : 4
Upstream Author : Immutables Authors and Contributors
Ievgen Lukash (e.luc...@gmail.com)
Ilya Vysharev (ivysha...@gmail.com)
Augusto Travillio (augusto.travil...@gmail.com)
* URL : https://github.com/immutables/maven-shade-plugin
* License : Apache-2.0
Programming Lang: Java
Description : maven-shade-plugin with everything "fixed"

Customized version of maven-shade-plugin:

1. Relocation with $ uglyfication,
2. ServiceResourceTransformer that actually works properly,
3. Minimize Jar that works properly

Needed to package #908511.
--- End Message ---
--- Begin Message ---
Control: tags -1 wontfix

Lost interest into immutables, and also lost interest packaging this
fork of maven plugin. Also, this should be incorporated into maven
upstream instead of standalone fork. Sole reason for not doing so it:

> ... I just couldn't afford time to dive into processes or infrastructure
> there.

Quoted from:
https://github.com/immutables/maven-shade-plugin/blob/4f21777ca83be75e795b7ef87d3ab2772b04c2be/README.md--- End Message ---

Bug#909585: RFP: rapidcheck -- RapidCheck is a C++ framework for property based testing inspired by QuickCheck and other similar frameworks.

2018-09-25 Thread Diederik de Haas

Package: wnpp
Severity: wishlist

* Package name: rapidcheck
* URL : https://github.com/emil-e/rapidcheck
* License : BSD 2-clause
  Programming Lang: C++
  Description : RapidCheck is a C++ framework for property based testing 
inspired by QuickCheck and other similar frameworks.

RapidCheck is a C++ framework for property based testing inspired by QuickCheck 
and other similar frameworks. In property based testing, you state facts about 
your code that given certain precondition should always be true. RapidCheck 
then generates random test data to try and find a case for which the property 
doesn't hold. If such a case is found, RapidCheck tries to find the smallest 
case (for some definition of smallest) for which the property is still false 
and then displays this as a counterexample. For example, if the input is an 
integer, RapidCheck tries to find the smallest integer for which the property 
is false.

It helps in software testing and thereby has the potential to make (C++)
programs more robust.
It has recently been integrated into bitcoin [1] but one of the
maintainers noticed it hasn't been packaged for Debian [2].
This bug hopes to fix that.


[1] https://github.com/bitcoin/bitcoin/pull/12775
[2] https://github.com/bitcoin/bitcoin/pull/12775#issuecomment-417618765

Bug#909584: O: rapid-photo-downloader -- Photo downloader (importer) from cameras, memory cards, other devices

2018-09-25 Thread Jörg Frings-Fürst

Package: wnpp
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

I intend to orphan the rapid-photo-downloader package.

The package description is:
 Rapid Photo Downloader can be used by both professional and amateur
 photographers to download photos and videos from multiple cameras,
 memory cards and Portable Storage Devices simultaneously. It provides




-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAluqYpEACgkQCfifPIyh
0l0Zbg/8C3arCdAGVvY8/1epiVUtYawUujSKuG56yaXWFaXb8L904vRpwfyqu5kp
tsyxX+4Zh2EG5QTaDPDpXfQpw2G99ZkfG0ASZIAlCc3FDujAg8Spmwapo+PdbYYz
E8ZV9NcHvRzWXtC39qvx8dxwN22gls3sCx3iClptMic9LyuuYhvsP6zcmud7GtC2
eC7o9mpNaP/ItgWLQ/l+EE3lUM7ZCQJObdinxkRQuJnznjHSdl7+WC28i1w83VQ1
pS5LHcfVQPnDTawJp3osAFbaZN15MbD+wWLv5K+09cSitSrYe+N1QcgazGS48AM9
yZ5qh7q+OgJ/CA85eiD8uwKPBZfZtCtPX6bGpL8JKCOdmE5aha30yhuATFmQDb8e
OKAS/qNs0FhfMM40WpkSFqKy4SmOmDpTEBWyz88Vis+JrK02+0FxhM58Y4poycfZ
Zc+OFmDh1d3OSeS9TpuK4B5pmsGbISoI97pP51xcK055Yn9rD3F1iI8X54NZtLRi
US5CmUMUPXXDIHzt4i3Y+BKvgOVAxAFdwqM43BSP2nAVc+3wjQWM5+lLGrrDjjO1
JmROAEcILthlp9kcvqtf5qu384xVl4gVeOHkf1JRrWBkts2E1sI752NOD0VphPDb
hK9tdMfHBuEeu8dxh6pXV3D2QOUnxZbFharNtuwHSo0NCAUIOKQ=
=yWSP
-END PGP SIGNATURE-

Bug#909264: marked as done (ITP: mmdebstrap -- creates a Debian chroot directory or tarball)

Your message dated Tue, 25 Sep 2018 15:03:08 +
with message-id 
and subject line Bug#909264: fixed in mmdebstrap 0.1.0-1
has caused the Debian Bug report #909264,
regarding ITP: mmdebstrap -- creates a Debian chroot directory or tarball
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.)


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

* Package name: mmdebstrap
  Version : 0.1.0
  Upstream Author : Johannes 'josch' Schauer 
* URL : https://gitlab.mister-muffin.de/josch/mmdebstrap
* License : Expat
  Programming Lang: Perl
  Description : creates a Debian chroot directory or tarball

An alternative to debootstrap which uses apt internally and is thus able to use
more than one mirror and resolve more complex dependencies.

A list of advantages in contrast to debootstrap:

 - more than one mirror possible (or really anything that is a legal apt
   sources.list entry)
 - security and updates mirror included for Debian stable chroots (a
   wontfix for debootstrap)
 - 2-3 times faster (for debootstrap variants)
 - chroot with apt in 11 seconds (if only installing `Essential: yes`
   and apt)
 - gzipped tarball with apt is 27M small
 - bit-by-bit reproducible output (if `$SOURCE_DATE_EPOCH` is set)
 - unprivileged operation using Linux user namespaces, fakechroot or
   proot (mode is chosen automatically)
 - can operate on filesystems mounted with nodev
 - foreign architecture chroots with qemu-user (without manually
   invoking `--second-stage`)
--- End Message ---
--- Begin Message ---
Source: mmdebstrap
Source-Version: 0.1.0-1

We believe that the bug you reported is fixed in the latest version of
mmdebstrap, 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 909...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Johannes 'josch' Schauer  (supplier of updated mmdebstrap 
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: Mon, 24 Sep 2018 08:38:53 +0200
Source: mmdebstrap
Binary: mmdebstrap
Architecture: all source
Version: 0.1.0-1
Distribution: unstable
Urgency: medium
Maintainer: Johannes 'josch' Schauer 
Changed-By: Johannes 'josch' Schauer 
Closes: 909264
Description: 
 mmdebstrap - create a Debian chroot
Changes:
 mmdebstrap (0.1.0-1) unstable; urgency=medium
 .
   * Initial release. (Closes: #909264)
Checksums-Sha1: 
 0348e01b0cbcc17e7fb352bc5f1d7e3eea0c2360 24212 mmdebstrap_0.1.0-1_all.deb
 14aab43167e16b3b099d14ce448bc778cc188fc8 5158 
mmdebstrap_0.1.0-1_amd64.buildinfo
 7ffa8f1d0c433f15706dedfe37a80ad88005a8df 1850 mmdebstrap_0.1.0-1.dsc
 8152180c775e10aab6682b67036ebcffbb11811f 23198 mmdebstrap_0.1.0.orig.tar.gz
 c1438477b68e4e653ee96b05f30ee21e50839f01 2056 mmdebstrap_0.1.0-1.debian.tar.xz
Checksums-Sha256: 
 5ed1048540cdb5b315ba3806841ff334c684954d790af87792f9e52206b848dc 24212 
mmdebstrap_0.1.0-1_all.deb
 be59600a90a28a6a95037272e301b3fe3f6cd458d17734573c42159d4dc73cdc 5158 
mmdebstrap_0.1.0-1_amd64.buildinfo
 695995b31dfa15d15d26563147011fddc931766b2637f36e6907d4ca9eb9c0a6 1850 
mmdebstrap_0.1.0-1.dsc
 8b72662e9dd93ae72d0695d0d42f90404d718640ef692650951e04a7ff1c8b48 23198 
mmdebstrap_0.1.0.orig.tar.gz
 e97d2cdfa51565c1909442f02a9f1c17a74c97a23b561ff3a6532aedf97e668d 2056 
mmdebstrap_0.1.0-1.debian.tar.xz
Files: 
 34a438040420a73827ea7d50f13a40ce 24212 admin optional 
mmdebstrap_0.1.0-1_all.deb
 99c6afc55c6d7f7a27a4a9dd1a99a771 5158 admin - 
mmdebstrap_0.1.0-1_amd64.buildinfo
 c2bdef468f916f5d2afc6d679d34d5dd 1850 admin - mmdebstrap_0.1.0-1.dsc
 f50a18f0030351c82e0a6659af33f0fb 23198 admin - mmdebstrap_0.1.0.orig.tar.gz
 96abd08aac0bfc51c9ae42a8653fbea4 2056 admin - mmdebstrap_0.1.0-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEElFhU6KL81LF4wVq58sulx4+9g+EFAlupQZ4ACgkQ8sulx4+9
g+HUtg/+JM2iN8hU2h3DvvCTJY3h01xjbwHaQbWVxFsut7g3iRv1J3jQNPSc3Vmw
aut2joZ9Bda5jm5X5vb+GiSo4pCk57G2JcxBINmrfqMFs1FyTc0p3gTfWP0deCNU
UD3Az0xipbh6eDPjGmSK9+x0If3cOAR87zHrbWq1TtNWmFQzaRhe0C9PprQeMJuU

Bug#908659: marked as done (ITP: poliastro -- Astrodynamics and Orbital Mechanics computations)

Your message dated Tue, 25 Sep 2018 15:03:09 +
with message-id 
and subject line Bug#908659: fixed in poliastro 0.11.0-1
has caused the Debian Bug report #908659,
regarding ITP: poliastro -- Astrodynamics and Orbital Mechanics computations
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.)


-- 
908659: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908659
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Ole Streicher 
X-Debbugs-Cc: debian-as...@lists.debian.org, debian-de...@lists.debian.org

* Package name : poliastro
  Version  : 0.10.0
  Upstream Author  : Juan Luis Cano Rodríguez
* URL  : http://docs.poliastro.space
* License  : MIT
  Programming lang : Python
  Upstream git : https://github.com/poliastro/poliastro
  Pypi URL : https://pypi.python.org/pypi/poliastro
  Description  : Astrodynamics and Orbital Mechanics computations

poliastro is an open source pure Python package dedicated to problems
arising in Astrodynamics and Orbital Mechanics, such as orbit
propagation, solution of the Lambert's problem, conversion between
position and velocity vectors and classical orbital elements and orbit
plotting, focusing on interplanetary applications

This is an Astropy affiliated package.

The Debian package will be maintained by the Debian Astro team. A git
repository will be created at

https://salsa.debian.org/debian-astro-team/poliastro

Best regards

Ole
--- End Message ---
--- Begin Message ---
Source: poliastro
Source-Version: 0.11.0-1

We believe that the bug you reported is fixed in the latest version of
poliastro, 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 908...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ole Streicher  (supplier of updated poliastro 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: SHA512

Format: 1.8
Date: Tue, 25 Sep 2018 11:56:50 +0200
Source: poliastro
Binary: python3-poliastro
Architecture: source all
Version: 0.11.0-1
Distribution: unstable
Urgency: low
Maintainer: Debian Astro Team 
Changed-By: Ole Streicher 
Description:
 python3-poliastro - Astrodynamics and Orbital Mechanics computations
Closes: 908659
Changes:
 poliastro (0.11.0-1) unstable; urgency=low
 .
   * Initial release. (Closes: #908659)
Checksums-Sha1:
 2c53c7b5ee6388452f61204dcec3388e855b1029 2223 poliastro_0.11.0-1.dsc
 a6216c7e2bb1ce9a3f51777bbb488b14f808543c 3357199 poliastro_0.11.0.orig.tar.gz
 b2126581fed06d82c1796d153e26b3ed0563eaad 2400 poliastro_0.11.0-1.debian.tar.xz
 02a2fbb266ca44620114b7a8841bf3c10d0f429f 9748 
poliastro_0.11.0-1_amd64.buildinfo
 bacfcb7764bb0864eb4547dc5de210fac45d5387 66956 
python3-poliastro_0.11.0-1_all.deb
Checksums-Sha256:
 79da81bd4dfa2c61800abd2f629131d82f19dfdfb55ac83f9b56380d9828aef4 2223 
poliastro_0.11.0-1.dsc
 bfeeca07ea900300deb7efb67b101c9b5971836bea6487e0b95288b22e38449f 3357199 
poliastro_0.11.0.orig.tar.gz
 fd7410081a8968a76f8c4b7f9cd75fd4c67e3e5b86637aa4f59379dffc03be5f 2400 
poliastro_0.11.0-1.debian.tar.xz
 183faf291a8c7b5f2db4adc8c2cc590ae54879532ac64cd58834a0c9f1532e2a 9748 
poliastro_0.11.0-1_amd64.buildinfo
 7e5ba34d846da44a4581c1c396beeca267a5b4f28e07d23f31c71c176b351f5e 66956 
python3-poliastro_0.11.0-1_all.deb
Files:
 4b707e652237e8059feba9fe71f1d521 2223 python optional poliastro_0.11.0-1.dsc
 5166f563d4c4c55c9edefc1bc6c70648 3357199 python optional 
poliastro_0.11.0.orig.tar.gz
 2ccfc3687206f410b0def08d2aa3fdb2 2400 python optional 
poliastro_0.11.0-1.debian.tar.xz
 a302ec1001886f03a6a86de87f56a36a 9748 python optional 
poliastro_0.11.0-1_amd64.buildinfo
 180bb43f138b47dbada4cd519732efca 66956 python optional 
python3-poliastro_0.11.0-1_all.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAluqNqEACgkQcRWv0HcQ
3PeyJxAAofHAub9iGCPD9ikU+T5+P8omwpKY3K9DrNmmmjzCqwXcKXVyw33sluaK
+L9cJz6EKHiJJYmwMEXRBIoRh4qFn/I+ZP0/HsPWWAhvLqPMq89goYPuMc3DANUU
xUSewQVoKdF3y3DQXsodQUeEtw9F+Kwz0bBJbfWi4wAUpQi9GrAfQX7yiMfPmqyy
GxUSrW6GPIJvtDXKmJ0f1NykPWzczlc1MjpestwFsaFMM2wPMI8NxpbhUt94E9rb
spUT544R+1xeZIDPSLyjOtq8hQ8CGkF7ZZblxhKAvwnua8i2MHuuU88WyHLdW3S6

Bug#907070: marked as done (ITP: unarr -- Decompression library for RAR, TAR, ZIP and 7z archives)

Your message dated Tue, 25 Sep 2018 15:03:10 +
with message-id 
and subject line Bug#907070: fixed in unarr 0~20150801.d1be8c4-1
has caused the Debian Bug report #907070,
regarding ITP: unarr -- Decompression library for RAR, TAR, ZIP and 7z archives
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.)


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

* Package name: unarr
  Version : 20150801.d1be8c43
  Upstream Author : Simon Bünzli 
* URL : https://github.com/zeniko/unarr
* License : LGPL-3
  Programming Lang: C++
  Description : Decompression library for RAR, TAR, ZIP and 7z

This is a dependency for opencpn, #907065
--- End Message ---
--- Begin Message ---
Source: unarr
Source-Version: 0~20150801.d1be8c4-1

We believe that the bug you reported is fixed in the latest version of
unarr, 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 907...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alec Leamas  (supplier of updated unarr 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: SHA512

Format: 1.8
Date: Sun, 02 Sep 2018 00:44:03 -0400
Source: unarr
Binary: libunarr-dev libunarr1
Architecture: source amd64
Version: 0~20150801.d1be8c4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project 
Changed-By: Alec Leamas 
Description:
 libunarr-dev - Decompression library for RAR, TAR, ZIP and 7z archives (devel)
 libunarr1  - Decompression library for RAR, TAR, ZIP and 7z archives (runtime)
Closes: 907070
Changes:
 unarr (0~20150801.d1be8c4-1) unstable; urgency=medium
 .
   * Initial release (Closes: #907070)
Checksums-Sha1:
 70219dc51e7dbae1c802a8d9d6f3e23f2cfe5571 2056 unarr_0~20150801.d1be8c4-1.dsc
 af994564b3b14891da0c5b18d54eff4ec15ed255 59152 
unarr_0~20150801.d1be8c4.orig.tar.xz
 45fd846c3617c6dc7898baa5d6eaa861d4395a3b 6572 
unarr_0~20150801.d1be8c4-1.debian.tar.xz
 59a92c7df4c50b94941255bfe9b7dd90c0704453 4024 
libunarr-dev_0~20150801.d1be8c4-1_amd64.deb
 034b03eef7724269ca401d30e42ca5972e8b8abf 168616 
libunarr1-dbgsym_0~20150801.d1be8c4-1_amd64.deb
 aba0963b39043dd520b945590a9e553ccb63995b 49484 
libunarr1_0~20150801.d1be8c4-1_amd64.deb
 8033270b2649c3769e99f1500c989e7e60a3276b 7918 
unarr_0~20150801.d1be8c4-1_amd64.buildinfo
Checksums-Sha256:
 2a43d4b6c25ff0af80611fcdd39e264a8a55576de540995204a596e1428ecb33 2056 
unarr_0~20150801.d1be8c4-1.dsc
 97fd5714893a734b57055f884fc9562b4c012b37a2ee98eccdcd766ead48361b 59152 
unarr_0~20150801.d1be8c4.orig.tar.xz
 5664f9c25de91206a9d3d5d18ca9f9a4c7aefda389350d75ad08b23f9c816812 6572 
unarr_0~20150801.d1be8c4-1.debian.tar.xz
 af2e51936b6bf1b713696b521ba6a1b6276af7bba959a819d563e610b2a9043c 4024 
libunarr-dev_0~20150801.d1be8c4-1_amd64.deb
 546f5fbee34c4196af46dd449ad9c8e218557daa368411d9f9475bf713c1a36b 168616 
libunarr1-dbgsym_0~20150801.d1be8c4-1_amd64.deb
 815909509d4fdd0c9b45b406c07b1db569825b5f4946949eff6128574d18a648 49484 
libunarr1_0~20150801.d1be8c4-1_amd64.deb
 63cf373f9589c8c1d7173d783821cb88aa0cc07a7581907a807f2573f974d6b3 7918 
unarr_0~20150801.d1be8c4-1_amd64.buildinfo
Files:
 0e80faf62f73d733b634baa64df412a0 2056 libs optional 
unarr_0~20150801.d1be8c4-1.dsc
 2941bbcf1e1659e189a7805ca179b88e 59152 libs optional 
unarr_0~20150801.d1be8c4.orig.tar.xz
 0ee2a5b2bcf349cbacbbdb51564630cd 6572 libs optional 
unarr_0~20150801.d1be8c4-1.debian.tar.xz
 fa7356585d72ce881e17e296d8564d4a 4024 libdevel optional 
libunarr-dev_0~20150801.d1be8c4-1_amd64.deb
 c25c7b4f48789a2bf9bdf47f7d5b327f 168616 debug optional 
libunarr1-dbgsym_0~20150801.d1be8c4-1_amd64.deb
 c23f9256b9af35cbb96337451e6ba6a3 49484 libs optional 
libunarr1_0~20150801.d1be8c4-1_amd64.deb
 d6e79ac034d502a75d91fa9c4d129927 7918 libs optional 
unarr_0~20150801.d1be8c4-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEgYLeQXBWQI1hRlDRZ1DxCuiNSvEFAlupEz4ACgkQZ1DxCuiN
SvFcehAAmimEdXsNA6cHiurcyhe65O0RdBnUHOgzJ9+h8wf5Ne09etKNXBZJAfcm
5w+xoHPg6q6aifd0D26u+OCIaJ0i2ZVFA/RFM2lU+6Fj4IrHixlJtEsfthn4n437

Bug#779893: ITP

2018-09-25 Thread Niv Sardi-Altivanik

Packaging work is being made on salsa under the pkg-golang group.
HELP WELCOMED =)
https://salsa.debian.org/go-team/packages/

Processed (with 5 errors): IPFS ITP

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

> retitle 779893  ITP: ipfs -- content-addressed global distributed file system
Bug #779893 [wnpp] RFP: ipfs -- content-addressed global distributed file system
Changed Bug title to 'ITP: ipfs -- content-addressed global distributed file 
system' from 'RFP: ipfs -- content-addressed global distributed file system'.
> thanks,
Unknown command or malformed arguments to command.
> Package: wnpp
Limiting to bugs with field 'package' containing at least one of 'wnpp'
Limit currently set to 'package':'wnpp'

> Severity: wishlist
Unknown command or malformed arguments to command.
> Owner: Niv Sardi 
Unknown command or malformed arguments to command.
> * Package name: go-ipfs
Unknown command or malformed arguments to command.
>   Version : 0.4.17+git20180914.996281702-1
Unknown command or malformed arguments to command.
Too many unknown commands, stopping here.

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

Bug#909550: possible conflict over the /usr/bin/ia namespace

On 2018-09-25 14:33:44, Ian Jackson wrote:
> Antoine Beaupré writes ("Re: possible conflict over the /usr/bin/ia 
> namespace"):
>> On 2018-09-25 14:22:44, Ian Jackson wrote:
>> > If you can't get a better idea I would suggest
>> >   << 0.242+git20151019-1.1~
>> > which is all versions until the next draft(~)-of-an-nmu (.1).
>> 
>> But wouldn't <= 0.242+git20151019-1~ be as effective? Why does it need
>> to be <
> 0.242+git20151019-1 is not <= 0.242+git20151019-1~ so that is
> definitely wrong.  Maybe you meant <= 0.242+git20151019-1.1~ ?
> But if I were preparing an NMU I would be intending to use
> 0.242+git20151019-1.1 as the nmu version; and my draft packages would
> be called precisely 0.242+git20151019-1.1~ and don't want to be
> conflicted against.  Hence  0.242+git20151019-1.1~
>
> This seems like arcane lore really.  Surely this stuff ought to be
> documented somewhere ?

It's super weird corner cases - those are hard to document... I looked
into those places in the policy, for example, and couldn't quite figure
it out:

https://www.debian.org/doc/debian-policy/ch-relationships.html#conflicting-binary-packages-conflicts
https://www.debian.org/doc/debian-policy/ch-relationships.html#syntax-of-relationship-fields

The former does not mention any way to specify the actual version; it
probably should. The latter mentions the comparison operators but it
doesn't go into details into how to use them.

The developer's reference also does not seem to have anything about this
that I could find quickly.

So anyways - irl will upload a new package now, presumably -2 or more,
so i think << 0.242+git20151019-2~ is fine.

A.

-- 
One of the things the Web teaches us is that everything is connected
(hyperlinks) and we all should work together (standards). Too often
school teaches us that everything is separate (many different
'subjects') and that we should all work alone.  - Aaron Swartz

Bug#909550: possible conflict over the /usr/bin/ia namespace

On 2018-09-25 14:25:25, Ian Jackson wrote:
> Iain Learmonth writes ("Re: possible conflict over the /usr/bin/ia 
> namespace"):
>> On 25/09/18 14:16, Antoine Beaupré wrote:
>> > ... but it hasn't been migrated to Salsa. Would you be okay to move this
>> > in the Python module's team umbrella (as opposed to simply collab-maint)?
>> 
>> The whole salsa thing is not something that I've been able to keep up
>> with. I have git repos locally and I've been moving things to salsa as
>> and when I do updates. You probably shouldn't trust what is on salsa
>> anyway unless we all start using signed commits and tags. The archive is
>> the only true record of packages.

I agree with that, for the record. Like any upload I sponsor or work on,
I review the diff before signing anyways, regardless of the source.

> For packages maintained by very small (or unitary) teams with limited
> collaboration, ad-hoc sharing via personal git repos works OK.  And of
> course you can share your git branch more formally with everyone,
> in step with the archive, and with reasonable security, by using `dgit
> push'.

I really should give dgit a try again, but I guess it's a great use case
for people allergic to salsa (pun intended) and that just need a git
repo, right? :)

>> I once looked at doing team maintenance on these packages but there was
>> enough extra policy regarding that team management that I did not have
>> the time to look at it. If you would like to adopt the package and move
>> it into the team then that's fine with me. I am also on the list of "low
>> nmu" maintainers. I am not interested in maintaining the package within
>> the team myself though.

>From what I understand, the Python folks are easy: it's just a way to
get the package some visibility and help, and the overhead is
minimal. You don't have to join the team to upload.

But "collab-maint" (also known as "debian" now on Salsa) also works
fine. I don't need a new package to maintain so I'd be happy to let you
proceed with the future of this one. :)

>> Ok, I will close that in approx 15 minutes. (:

Awesome! I'll proceed with the upload of "internetarchive" (binary and
source, after consulting with #debian-python people) shortly as well.

A.

-- 
Toute mère doit être mère par choix.
Tout enfant doit être un enfant désiré.
 - Henry Morgentaler

Bug#909550: possible conflict over the /usr/bin/ia namespace

Ian Jackson writes ("Re: possible conflict over the /usr/bin/ia namespace"):
> Antoine Beaupré writes ("Re: possible conflict over the /usr/bin/ia 
> namespace"):
> > On 2018-09-25 14:22:44, Ian Jackson wrote:
> > > If you can't get a better idea I would suggest
> > >   << 0.242+git20151019-1.1~
> > > which is all versions until the next draft(~)-of-an-nmu (.1).
> > 
> > But wouldn't <= 0.242+git20151019-1~ be as effective? Why does it need
> > to be < 
> 0.242+git20151019-1 is not <= 0.242+git20151019-1~ so that is
> definitely wrong.  Maybe you meant <= 0.242+git20151019-1.1~ ?
> But if I were preparing an NMU I would be intending to use
> 0.242+git20151019-1.1 as the nmu version; and my draft packages would
> be called precisely 0.242+git20151019-1.1~ and don't want to be
> conflicted against.  Hence  0.242+git20151019-1.1~

I mean, hence   << 0.242+git20151019-1.1~

Ian.

Bug#909550: possible conflict over the /usr/bin/ia namespace

Antoine Beaupré writes ("Re: possible conflict over the /usr/bin/ia namespace"):
> On 2018-09-25 14:22:44, Ian Jackson wrote:
> > If you can't get a better idea I would suggest
> >   << 0.242+git20151019-1.1~
> > which is all versions until the next draft(~)-of-an-nmu (.1).
> 
> But wouldn't <= 0.242+git20151019-1~ be as effective? Why does it need
> to be <   These opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.

Bug#909550: possible conflict over the /usr/bin/ia namespace

On 2018-09-25 14:22:44, Ian Jackson wrote:
> Antoine Beaupré writes ("Re: possible conflict over the /usr/bin/ia 
> namespace"):
>> Makes sense. How about:
>> 
>> Conflicts: python-duckduckgo2 (<= 0.242+git20151019-1)
>> 
>> This way we assume any newer upload of the package will remove ia?
>
> That's not a good choice because it excludes (local) backports,
> security updates, etc., which tend to add +something to versions.
> If you can't get a better idea I would suggest
>   << 0.242+git20151019-1.1~
> which is all versions until the next draft(~)-of-an-nmu (.1).

But wouldn't <= 0.242+git20151019-1~ be as effective? Why does it need
to be <

Bug#909550: possible conflict over the /usr/bin/ia namespace

Iain Learmonth writes ("Re: possible conflict over the /usr/bin/ia namespace"):
> On 25/09/18 14:16, Antoine Beaupré wrote:
> > ... but it hasn't been migrated to Salsa. Would you be okay to move this
> > in the Python module's team umbrella (as opposed to simply collab-maint)?
> 
> The whole salsa thing is not something that I've been able to keep up
> with. I have git repos locally and I've been moving things to salsa as
> and when I do updates. You probably shouldn't trust what is on salsa
> anyway unless we all start using signed commits and tags. The archive is
> the only true record of packages.

For packages maintained by very small (or unitary) teams with limited
collaboration, ad-hoc sharing via personal git repos works OK.  And of
course you can share your git branch more formally with everyone,
in step with the archive, and with reasonable security, by using `dgit
push'.

> Ok, I will close that in approx 15 minutes. (:

Yay :-).  Please use dgit push, so that you share your
actually-uploaded git branch as well as just the package.

Thanks,
Ian.
(back onto the dgit plug hobby-horse)

Bug#909550: possible conflict over the /usr/bin/ia namespace

2018-09-25 Thread Adam Borowski

On Tue, Sep 25, 2018 at 09:16:44AM -0400, Antoine Beaupré wrote:
> On 2018-09-25 13:43:42, Ian Jackson wrote:
> > You need to coordinate the transition for the /usr/bin/ia filename.  I
> > think that means your new internet-archive package should probably
> >   Conflict: python-duckduckgo2 (<< version-without-ia~)
> >
> > That can probably be uploaded before the new python-duckduckgo2 but
> > the relevant version number should be agreed.
> 
> Makes sense. How about:
> 
> Conflicts: python-duckduckgo2 (<= 0.242+git20151019-1)
> 
> This way we assume any newer upload of the package will remove ia?

That'd put a requirement on security updates -- and a program that talks to
untrusted remote servers is at risk of requiring such an update.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ 10 people enter a bar:
⣾⠁⢰⠒⠀⣿⡁ • 1 who understands binary,
⢿⡄⠘⠷⠚⠋⠀ • 1 who doesn't,
⠈⠳⣄ • and E who prefer to write it as hex.

Bug#909550: possible conflict over the /usr/bin/ia namespace

2018-09-25 Thread Iain Learmonth

Hi,

On 25/09/18 14:16, Antoine Beaupré wrote:
> Conflicts: python-duckduckgo2 (<= 0.242+git20151019-1)

The upload I am currently preparing is 0.242+git20151019-2

> I'd be happy to do that upload, actually. I see the git repo used to be
> on Alioth:
> 
> https://alioth-archive.debian.org/git/collab-maint/python-duckduckgo2.git.tar.xz
> 
> ... but it hasn't been migrated to Salsa. Would you be okay to move this
> in the Python module's team umbrella (as opposed to simply collab-maint)?

The whole salsa thing is not something that I've been able to keep up
with. I have git repos locally and I've been moving things to salsa as
and when I do updates. You probably shouldn't trust what is on salsa
anyway unless we all start using signed commits and tags. The archive is
the only true record of packages.

I once looked at doing team maintenance on these packages but there was
enough extra policy regarding that team management that I did not have
the time to look at it. If you would like to adopt the package and move
it into the team then that's fine with me. I am also on the list of "low
nmu" maintainers. I am not interested in maintaining the package within
the team myself though.

>> And if you do upload internet-archive before python-duckduckgo2 is
>> changed there there should probably be a bug against
>> python-duckduckgo2.
> 
> Sure, I'll file that anyways now.

Ok, I will close that in approx 15 minutes. (:

Thanks,
Iain.

signature.asc
Description: OpenPGP digital signature

Bug#909550: possible conflict over the /usr/bin/ia namespace

Antoine Beaupré writes ("Re: possible conflict over the /usr/bin/ia namespace"):
> Makes sense. How about:
> 
> Conflicts: python-duckduckgo2 (<= 0.242+git20151019-1)
> 
> This way we assume any newer upload of the package will remove ia?

That's not a good choice because it excludes (local) backports,
security updates, etc., which tend to add +something to versions.
If you can't get a better idea I would suggest
  << 0.242+git20151019-1.1~
which is all versions until the next draft(~)-of-an-nmu (.1).

Ian.

Bug#909550: possible conflict over the /usr/bin/ia namespace

On 2018-09-25 13:43:42, Ian Jackson wrote:
> Antoine Beaupré writes ("Re: possible conflict over the /usr/bin/ia 
> namespace"):
>> Great! I would be happy to help with that if you need any assistance.
>> In the meantime, should I just upload IA to NEW? :)
>
> You need to coordinate the transition for the /usr/bin/ia filename.  I
> think that means your new internet-archive package should probably
>   Conflict: python-duckduckgo2 (<< version-without-ia~)
>
> That can probably be uploaded before the new python-duckduckgo2 but
> the relevant version number should be agreed.

Makes sense. How about:

Conflicts: python-duckduckgo2 (<= 0.242+git20151019-1)

This way we assume any newer upload of the package will remove ia?

I'd be happy to do that upload, actually. I see the git repo used to be
on Alioth:

https://alioth-archive.debian.org/git/collab-maint/python-duckduckgo2.git.tar.xz

... but it hasn't been migrated to Salsa. Would you be okay to move this
in the Python module's team umbrella (as opposed to simply collab-maint)?

> And if you do upload internet-archive before python-duckduckgo2 is
> changed there there should probably be a bug against
> python-duckduckgo2.

Sure, I'll file that anyways now.

> I guess that bug doesn't need to be rc ?

Yeah, that's not RC material, as long as the bug is not forgotten in the
next upload of course. :)

A.

-- 
Instead of worrying about what somebody else is going to do, which is
not under your control, the important thing is, what are you going to
decide about what is under your control?
 - Richard Stallman

Bug#909550: possible conflict over the /usr/bin/ia namespace

Antoine Beaupré writes ("Re: possible conflict over the /usr/bin/ia namespace"):
> Great! I would be happy to help with that if you need any assistance.
> In the meantime, should I just upload IA to NEW? :)

You need to coordinate the transition for the /usr/bin/ia filename.  I
think that means your new internet-archive package should probably
  Conflict: python-duckduckgo2 (<< version-without-ia~)

That can probably be uploaded before the new python-duckduckgo2 but
the relevant version number should be agreed.  And if you do upload
internet-archive before python-duckduckgo2 is changed there there
should probably be a bug against python-duckduckgo2.  I guess that bug
doesn't need to be rc ?

Ian.

-- 
Ian JacksonThese opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.

Bug#909550: possible conflict over the /usr/bin/ia namespace

On 2018-09-25 10:45:07, Iain Learmonth wrote:
> Hi,
>
> On 25/09/18 05:35, Antoine Beaupré wrote:
>> I tried to figure out what the other package does:
>
> It uses the DuckDuckGo instant answers API to give an instant answer on
> the command line as a more human friendly version of the ddg command
> which is machine-readable but contains more information.
>
> popcon reports 7 old and 0 recent.
>
> The ia script was added in a patch and never actually present upstream:
>
> https://sources.debian.org/src/python-duckduckgo2/0.242+git20151019-1/debian/patches/0001-add-ia-script.patch/
>
> I was using this as part of an IRC bot but I now just call Python directly.
>
> The easiest solution here is probably that I drop that script. It was
> never accepted upstream anyway, nor have there been any updates upstream
> since 2015.

Great! I would be happy to help with that if you need any assistance.

In the meantime, should I just upload IA to NEW? :)

A.

-- 
To punish me for my contempt for authority, fate made me an authority myself.
   - Albert Einstein

Bug#909567: ITP: opensnitch -- Port of the Little Snitch application firewall

2018-09-25 Thread Chris Lamb

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

* Package name: opensnitch
  Version : 0~git20180913+e9c10b9-1
  Upstream Author : Simone "evilsocket" Margaritelli 
* URL : https://opensnitch.io/
* License : GPL-3
  Programming Lang: Go / Python (Qt)
  Description : Port of the Little Snitch application firewall

OpenSnitch works on the same principles of the macOS version, being a
host-based firewall that notifies users when local apps are attempting to
initiate new outgoing network connections.

When this happens, OpenSnitch will display a popup, asking the user for
instructions on how to deal with this new process.

All user decisions are saved as rules in local JSON files. Users can edit
these rules later to fine-tune the firewall or import/export rules from/to
other systems.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#909550: possible conflict over the /usr/bin/ia namespace

2018-09-25 Thread Iain Learmonth

Hi,

On 25/09/18 05:35, Antoine Beaupré wrote:
> I tried to figure out what the other package does:

It uses the DuckDuckGo instant answers API to give an instant answer on
the command line as a more human friendly version of the ddg command
which is machine-readable but contains more information.

popcon reports 7 old and 0 recent.

The ia script was added in a patch and never actually present upstream:

https://sources.debian.org/src/python-duckduckgo2/0.242+git20151019-1/debian/patches/0001-add-ia-script.patch/

I was using this as part of an IRC bot but I now just call Python directly.

The easiest solution here is probably that I drop that script. It was
never accepted upstream anyway, nor have there been any updates upstream
since 2015.

Thanks,
Iain.



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#894753: ITP: node-asmcrypto -- JavaScript Cryptographic Library

Processing control commands:

> retitle -1 node-asmcrypto.js -- JavaScript Cryptographic Library
Bug #894753 [wnpp] RFP: node-asmcrypto -- JavaScript Cryptographic Library
Changed Bug title to 'node-asmcrypto.js -- JavaScript Cryptographic Library' 
from 'RFP: node-asmcrypto -- JavaScript Cryptographic Library'.

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

Bug#894753: ITP: node-asmcrypto -- JavaScript Cryptographic Library

2018-09-25 Thread Jonas Smedegaard

Control: retitle -1 node-asmcrypto.js -- JavaScript Cryptographic Library

Hi Daniel,

Quoting Daniel Kahn Gillmor (2018-04-03 23:09:58)
> * Package name: node-asmcrypto

Upstream name (as declared in its package.json file) is "asmcrypto.js" - 
i.e. with a ".js" suffix.

Please therefore use package name "node-asmcrypto.js".


 - 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

Bug#909562: ITP: black -- uncompromising Python code formatter

2018-09-25 Thread Neil Williams

Package: wnpp
Severity: wishlist
Owner: Neil Williams 

* Package name: black
  Version : 18.6b4
  Upstream Author : Łukasz Langa 
* URL : https://github.com/ambv/black
* License : BSD-3-Clause
  Programming Lang: Python
  Description : uncompromising Python code formatter

 Black is the uncompromising Python code formatter. By using it, you 
 agree to cede control over minutiae of hand-formatting. In return, 
 Black gives you speed, determinism, and freedom from pycodestyle 
 nagging about formatting. You will save time and mental energy for 
 more important matters.
 .
 Blackened code looks the same regardless of the project you're reading. 
 Formatting becomes transparent after a while and you can focus on the 
 content instead.
 .
 Black makes code review faster by producing the smallest diffs 
 possible.

We'd like to use black as part of code review for LAVA and
associated python packages. I'm currently investigating if this
should be maintained by the LAVA team or the Python Modules team.

The package needs a small patch to remove privacy-breaching tracking URLs
from the docs.

Bug#717786: Ownership

2018-09-25 Thread Kyle Robbertze

Control: owner -1 !
Control: retitle -1 ITA: camomile -- Unicode library for OCaml

Hi,

I will take over maintainership of this package under the ocaml team, as
it is a dependency of Liquidsoap

Cheers



signature.asc
Description: OpenPGP digital signature

Processed: Ownership

Processing control commands:

> owner -1 !
Bug #717786 [wnpp] RFA: camomile -- Unicode library for OCaml
Owner recorded as Kyle Robbertze .
> retitle -1 ITA: camomile -- Unicode library for OCaml
Bug #717786 [wnpp] RFA: camomile -- Unicode library for OCaml
Changed Bug title to 'ITA: camomile -- Unicode library for OCaml' from 'RFA: 
camomile -- Unicode library for OCaml'.

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

Bug#532097: marked as done (RFH: cups -- Common UNIX Printing System)