Bug#911245: ITP: libvma -- libvma is a LD_PRELOAD-able library that boosts performance

2018-10-18 Thread Ben Hutchings
On Wed, 2018-10-17 at 18:22 +0300, Talat Batheesh wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Talat Batheesh 
> 
> * Package name: libvma
>   Version : 8.7.1
>   Upstream Author : Liran Oz 
> * URL : https://github.com/Mellanox/libvma
> * License : GPLv2 and BSD
>   Programming Lang: C, C++
>   Description : libvma is a LD_PRELOAD-able library that boosts 
> performance

For the actual binary packages, the short description should not
include "libvma is" but should make it clear what this depends on
ib_verbs.

Ben.

> libvma is a LD_PRELOAD-able library that boosts performance of TCP and UDP 
> traffic.
> It allows application written over standard socket API to handle fast path 
> data
> traffic from user space over Ethernet and/or Infiniband with full network 
> stack
> bypass and get better throughput, latency and packets/sec rate.
> 
> No application binary change is required for that.
> libvma is supported by RDMA capable devices that support "verbs" 
> IBV_QPT_RAW_PACKET QP for Ethernet and/or IBV_QPT_UD QP for IPoIB.
> 
-- 
Ben Hutchings
If at first you don't succeed, you're doing about average.




signature.asc
Description: This is a digitally signed message part


Bug#911335: ITP bug reports for the backend packages

2018-10-18 Thread Till Kamppeter

CUPS/IPP backend:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911340

Google Cloud Print backend:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911342

Print-to-File backend:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911345



Bug#911345: ITP: cpdb-backend-file -- Common Print Dialog Backends - Print-to-File Backend

2018-10-18 Thread Till Kamppeter
Package: wnpp
Severity: wishlist
Owner: Till Kamppeter 

* Package name: cpdb-backend-file
  Version : 1.0.1
  Upstream Author : Ayush Bansal 
* URL : https://github.com/OpenPrinting/cpdb-backend-file
* License : MIT
  Programming Lang: C
  Description : Common Print Dialog Backends - Print-to-File Backend

This package needs cpdb-libs, ITP here:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911335

This is already packaged for Ubuntu. This is the long description of
the Ubuntu package:

 This is the Print-to-File backend for print dialogs using the Common Print
 Dialog Backends concept of OpenPrinting. It makes the dialog list one
 single print queue and if you print to it, the data is put into a PDF file
 and not sent to a printer.

The idea is to decouple the print dialog's GUI code (GTK, Qt,
LibreOffice, ... The frontends) from the code which communicates with
actual print technologies (CUPS, IPP, Google Cloud Print, Save to
File, ... The backends) to make them independently
interchangable. This way one can do things like

- Add a new print technology and it is immediately available for all
  GUI apps. Especially an online print service provider could simply
  put its backend into the Snap Store and asks his Linux users to
  install it.

- A change in a print technology, for example new functionality in
  CUPS, can be covered by simply updating the CUPS backend. No need to
  change all GUI libraries.

- User logs in for Google Cloud Print once and not separately for each
  GUI platform to get his cloud printers into all the apps.

- In case of a security bug in the communication code with one print
  technology only the backend needs to get fixed, not several GUI
  libs.

This package contains a backend which creates a printer entry in all
print dialogs (using cpdb-libs) which drops jobs sent to it simply in
PDF files. The backend instructs the print dialogs to show a printer
entry and to pop-up a "Save as ..." dialog when hitting "Print"
(and/or selecting the "Destination File Name" option).

For this to work at least one application with a print dialog using
cpdb-libs must be installed.

Of the GUIs LibreOffice already supports this system and only needs to
get rebuilt with this library. Patches for GTK and a modified Qt print
dialog are in the works.

All packages are already available as Ubuntu packages in Ubuntu's
Universe part. The maintenance in Debian should be done in the Debian
Printing Team.

I am not a Debian Developer but OdyX (Didier Raboud, o...@debian.org)
is willing to upload these packages.



Bug#911342: ITP: cpdb-backend-gcp -- Common Print Dialog Backends - Google Cloud Print Backend

2018-10-18 Thread Till Kamppeter
Package: wnpp
Severity: wishlist
Owner: Till Kamppeter 

* Package name: cpdb-backend-gcp
  Version : 1.1.0
  Upstream Author : Abhijeet Dubey 
* URL : https://github.com/OpenPrinting/cpdb-backend-gcp
* License : MIT
  Programming Lang: C
  Description : Common Print Dialog Backends - Google Cloud Print Backend

This package needs cpdb-libs, ITP here:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911335

This is already packaged for Ubuntu. This is the long description of
the Ubuntu package:

 This is the Google Cloud Print backend for print dialogs using the
 Common Print Dialog Backends concept of OpenPrinting. It makes the
 dialog list the Google Cloud Print destinations set by the current
 user plus the option to drop the job as PDF on the Google Drive and
 allows printing on these using the dialog.
 .
 For a user to be able to use this facility he must set up his Google
 account in the "Online Accounts" section of GNOME Control Center.

The idea is to decouple the print dialog's GUI code (GTK, Qt,
LibreOffice, ... The frontends) from the code which communicates with
actual print technologies (CUPS, IPP, Google Cloud Print, Save to
File, ... The backends) to make them independently
interchangable. This way one can do things like

- Add a new print technology and it is immediately available for all
  GUI apps. Especially an online print service provider could simply
  put its backend into the Snap Store and asks his Linux users to
  install it.

- A change in a print technology, for example new functionality in
  CUPS, can be covered by simply updating the CUPS backend. No need to
  change all GUI libraries.

- User logs in for Google Cloud Print once and not separately for each
  GUI platform to get his cloud printers into all the apps.

- In case of a security bug in the communication code with one print
  technology only the backend needs to get fixed, not several GUI
  libs.

This package contains the backend for access the printers and the
Google Drive (to save as PDF) of the Google account of the current
user. It supplies information about the Google-registered printers,
their capabilities, and user-settable options and it passes print jobs
on to Google. The print dialogs (using cpdb-libs) connect to this
backend via D-Bus. To do so, it is enough to have this backend package
installed and each user who wants to use it, logged into his Google
account via Online Accounts.

For this to work at least one application with a print dialog using
cpdb-libs must be installed.

Of the GUIs LibreOffice already supports this system and only needs to
get rebuilt with this library. Patches for GTK and a modified Qt print
dialog are in the works.

All packages are already available as Ubuntu packages in Ubuntu's
Universe part. The maintenance in Debian should be done in the Debian
Printing Team.

I am not a Debian Developer but OdyX (Didier Raboud, o...@debian.org)
is willing to upload these packages.



Bug#904216: marked as done (ITP: fuse3 -- Filesystem in Userspace (3.x version))

2018-10-18 Thread Debian Bug Tracking System
Your message dated Thu, 18 Oct 2018 20:02:58 +
with message-id 
and subject line Bug#904216: fixed in fuse3 3.2.4-1
has caused the Debian Bug report #904216,
regarding ITP: fuse3 -- Filesystem in Userspace (3.x version)
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.)


-- 
904216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904216
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Laszlo Boszormenyi (GCS) 

* Package name: fuse3
  Version : 3.2.4
  Upstream Author : Nikolaus Rath 
* URL : https://github.com/libfuse/libfuse/wiki
* License : GPL-2, LGPL-2.1
  Programming Lang: C
  Description : Filesystem in Userspace (3.x version)

 Filesystem in Userspace (FUSE) is a simple interface for userspace
 programs to export a virtual filesystem to the Linux kernel. It also
 aims to provide a secure method for non privileged users to create
 and mount their own filesystem implementations.
--- End Message ---
--- Begin Message ---
Source: fuse3
Source-Version: 3.2.4-1

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated fuse3 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: Sat, 21 Jul 2018 14:11:44 +
Source: fuse3
Binary: fuse3 libfuse3-3 libfuse3-dev fuse3-udeb libfuse3-3-udeb
Architecture: source amd64
Version: 3.2.4-1
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Description:
 fuse3  - Filesystem in Userspace (3.x version)
 fuse3-udeb - Filesystem in Userspace (3.x version) (udeb)
 libfuse3-3 - Filesystem in Userspace (library) (3.x version)
 libfuse3-3-udeb - Filesystem in Userspace (library) (3.x version) (udeb)
 libfuse3-dev - Filesystem in Userspace (development) (3.x version)
Closes: 904216
Changes:
 fuse3 (3.2.4-1) unstable; urgency=medium
 .
   * New major upstream release (closes: #904216).
   * Drop own udev rules.
   * Update watch file.
   * Update copyright file.
   * Update debhelper level to 11:
 - remove dh-autoreconf build dependency,
 - don't specify parallel to debhelper.
   * Update Standards-Version to 4.1.5:
 - remove fuse-dbg package and use the auto-generated one.
Checksums-Sha1:
 e0dc2cdbeb8a147ef20cc5d906579c78ca63a232 2327 fuse3_3.2.4-1.dsc
 d3d6b7fa703c1be96f03322fdba3eca836e1f40c 1336412 fuse3_3.2.4.orig.tar.xz
 0d796db73254fa058900da4150990f86100b1908 1012 fuse3_3.2.4.orig.tar.xz.asc
 60a61eb72f4d2d4fefc37fa61cca5632c9ad2e90 16172 fuse3_3.2.4-1.debian.tar.xz
 03b7584351d2468de1f942749339e67bfc302c8e 43616 fuse3-dbgsym_3.2.4-1_amd64.deb
 7a3394ddf01c9e51e486ee8ce36e9264f24db1fe 14328 fuse3-udeb_3.2.4-1_amd64.udeb
 2d1de0198e741e455bdcf2a43d9efa0468c12092 9056 fuse3_3.2.4-1_amd64.buildinfo
 d265ea4a0f567303f2f8aabf9f03b0323b8092d5 29072 fuse3_3.2.4-1_amd64.deb
 53d8de76005993db2e314d3fade0e9868fb5a957 261544 
libfuse3-3-dbgsym_3.2.4-1_amd64.deb
 9eee0cf9214fca1fc89d0d5bd0a8396e8044278d 62052 
libfuse3-3-udeb_3.2.4-1_amd64.udeb
 6ae5be2f4055b8c4e7e35f361fbd0ea1c29d5ec4 78652 libfuse3-3_3.2.4-1_amd64.deb
 ce8d01acb0e5317e4c1e120ee68872f287fe75fa 122236 libfuse3-dev_3.2.4-1_amd64.deb
Checksums-Sha256:
 38b222a4e39d708e26ad837784f71739b0897998e422418502f2925a6d46b81e 2327 
fuse3_3.2.4-1.dsc
 61fcd35939b7ede710fca6fd3c3f1dd76f2d267bf62b05d4f140ddedd225490a 1336412 
fuse3_3.2.4.orig.tar.xz
 e31a255cb9748749c113302e04e8daf725755cd550f44e73aa0e3d2a793a8456 1012 
fuse3_3.2.4.orig.tar.xz.asc
 85f5325c9a9414dab665dd781708317ab2ab15a6ad3ff5c5602db9b38902ca18 16172 
fuse3_3.2.4-1.debian.tar.xz
 2a4fd0f7fc9f70ade88bb88c35457073db62fc661b00e2915eccb71bebc982e5 43616 
fuse3-dbgsym_3.2.4-1_amd64.deb
 c9607610d31cc1381b5df6b90943924ff7678f57fb6a2261b595eba8da38c768 14328 
fuse3-udeb_3.2.4-1_amd64.udeb
 26b0e2a985f157108c7209a72b0e4fcb09d5ca55050d0e8692625c142589f65c 9056 
fuse3_3.2.4-1_amd64.buildinfo
 bc53791efdec4a510cccf1be3d56130afe8a04b8b08a0d6f1dd9

Bug#911340: ITP: cpdb-backend-cups -- Common Print Dialog Backends - CUPS/IPP Backend

2018-10-18 Thread Till Kamppeter
Package: wnpp
Severity: wishlist
Owner: Till Kamppeter 

* Package name: cpdb-backend-cups
  Version : 1.1.0
  Upstream Author : Nilanjana Lodh 
* URL : https://github.com/OpenPrinting/cpdb-backend-cups
* License : MIT
  Programming Lang: C
  Description : Common Print Dialog Backends - CUPS/IPP Backend

This package needs cpdb-libs, ITP here:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911335

This is already packaged for Ubuntu. This is the long description of
the Ubuntu package:

 This is the CUPS/IPP backend for print dialogs using the Common Print
 Dialog Backends concept of OpenPrinting. It makes the dialog list CUPS
 print queues and driverless-capable IPP printers and allows printing
 on these using the dialog.

The idea is to decouple the print dialog's GUI code (GTK, Qt,
LibreOffice, ... The frontends) from the code which communicates with
actual print technologies (CUPS, IPP, Google Cloud Print, Save to
File, ... The backends) to make them independently
interchangable. This way one can do things like

- Add a new print technology and it is immediately available for all
  GUI apps. Especially an online print service provider could simply
  put its backend into the Snap Store and asks his Linux users to
  install it.

- A change in a print technology, for example new functionality in
  CUPS, can be covered by simply updating the CUPS backend. No need to
  change all GUI libraries.

- User logs in for Google Cloud Print once and not separately for each
  GUI platform to get his cloud printers into all the apps.

- In case of a security bug in the communication code with one print
  technology only the backend needs to get fixed, not several GUI
  libs.

This package contains the backend for access local and remote CUPS
print queues and IPP network printers. It supplies information about
the printers, their capabilities, and user-settable options and it
passes print jobs on to printers. The print dialogs (using cpdb-libs)
connect to this backend via D-Bus. To do so, it is enough to have this
backend package installed.

For this to work at least one application with a print dialog using
cpdb-libs must be installed.

Of the GUIs LibreOffice already supports this system and only needs to
get rebuilt with this library. Patches for GTK and a modified Qt print
dialog are in the works.

All packages are already available as Ubuntu packages in Ubuntu's
Universe part. The maintenance in Debian should be done in the Debian
Printing Team.

I am not a Debian Developer but OdyX (Didier Raboud, o...@debian.org)
is willing to upload these packages.



Bug#911339: RFP: node-chai -- assertion library for node and the browser

2018-10-18 Thread Daniel Kahn Gillmor
Package: wnpp
Severity: wishlist
Control: block 911189 by -1
Control: affects src:gpgme1.0

* Package name: node-chai
  Version : 4.1.2
  Upstream Author : Chai development team
* URL : https://www.chaijs.com/
* License : MIT
  Programming Lang: Javascript
  Description : assertion library for node and the browser

Chai is a Behavior-driven-development (BDD) / Test-driven-development
(TDD) assertion library for node and the browser that can be
delightfully paired with any javascript testing framework.


--

I want chai in debian because it appears to be necessary to be able to
run unit tests for gpgme's native messaging examples (see
https://bugs.debian.org/911189).

I am not prepared to maintain node packages these days (i've tried,
and failed), so i would appreciate it if someone with more node chops
than i've got could take this on.

Thanks!

--dkg



Processed (with 1 error): RFP: node-chai -- assertion library for node and the browser

2018-10-18 Thread Debian Bug Tracking System
Processing control commands:

> block 911189 by -1
Bug #911189 [src:gpgme1.0] src:gpgme1.0: please ship gpgme-json with native 
messaging hooks for chromium and firefox
911189 was blocked by: 911338
911189 was not blocking any bugs.
Added blocking bug(s) of 911189: 911339
> affects src:gpgme1.0
Unknown command or malformed arguments to command.


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



Bug#908787: packaging pgpio for Debian

2018-10-18 Thread peter green

Hi

I have been looking at getting pigpio into Debian. I will probablly start from 
the raspberry pi foundation's deb packaging and try to improve it to meet 
Debian standards.

Firstly there seem to be a number of components to pigpio, I understand they 
fit together as follows. Please tell me if my understanding is correct.

pigpio: library for accessing the gpio directly, used by pigpiod
pigpiod: daemon for accessing the GPIO
pigs: command line client for accessing the GPIO via the daemon
pigpiod_if: deprecated library for accessing the GPIO via the daemon
pigpiod_if2: library for talking for accessing the GPIO via the daemon
pig2vcd: tool for converting data for use with gtkwave, not clear to me exactly 
where the input data comes from.
pigpio.py: python module for accessing the GPIO via the daemon.

Is this understanding correct?

Secondly your libraries don't seem to have sonames, would you object to a patch 
adding them?

Finally I notice that your code doesn't seem to have any checks that it is 
actually running on a Pi, would you object to a patch adding such checks?



Bug#911335: ITP: cpdb-libs -- Common Print Dialog Backends - Interface Library for Backends

2018-10-18 Thread Till Kamppeter
Package: wnpp
Severity: wishlist
Owner: Till Kamppeter 

* Package name: cpdb-libs
  Version : 1.1.2
  Upstream Author : Nilanjana Lodh 
* URL : https://github.com/OpenPrinting/cpdb-libs
* License : MIT
  Programming Lang: C
  Description : Common Print Dialog Backends - Interface Library for 
Backends

This is already packaged for Ubuntu. This is the long description of
the Ubuntu package:

 The Common Print Dialog Backends project provides a D-Bus interface
 so that the print dialogs of GUI applications and the communication
 with the print technologies (CUPS/IPP, Google Cloud Print, Save to
 File, ...)  are put into separate executables to be separately
 exchangeable.
 .
 The print dialogs of the different GUI toolkits and applications
 (GTK, Qt, LibreOffice, ...) are the frontends and to communicate with
 the different print technologies they use common backends. This way
 one simply adds new backends for new print technologies and updates
 the backends for changes in the print technologies, and immediately
 all applications are up-to-date, without need of modifying the code
 of the GUI toolkits or applications.
 .
 This package contains the library which provides the functions needed
 by both the frontends and the backends.

The idea is to decouple the print dialog's GUI code (GTK, Qt,
LibreOffice, ... The frontends) from the code which communicates with
actual print technologies (CUPS, IPP, Google Cloud Print, Save to
File, ... The backends) to make them independently
interchangable. This way one can do things like

- Add a new print technology and it is immediately available for all
  GUI apps. Especially an online print service provider could simply
  put its backend into the Snap Store and asks his Linux users to
  install it.

- A change in a print technology, for example new functionality in
  CUPS, can be covered by simply updating the CUPS backend. No need to
  change all GUI libraries.

- User logs in for Google Cloud Print once and not separately for each
  GUI platform to get his cloud printers into all the apps.

- In case of a security bug in the communication code with one print
  technology only the backend needs to get fixed, not several GUI
  libs.

This package contains the general libraries which especially provide a
session D-Bus interface between the print dialogs (frontends) and the
print technology backends.

For this to work at least one print technology backend package is
needed. These packages are suggested in separate bug reports.

Of the GUIs LibreOffice already supports this system and only needs to
get rebuilt with this library. Patches for GTK and a modified Qt print
dialog are in the works.

All packages are already available as Ubuntu packages in Ubuntu's
Universe part. The maintenance in Debian should be done in the Debian
Printing Team.

I am not a Debian Developer but OdyX (Didier Raboud, o...@debian.org)
is willing to upload these packages.



Bug#908787: gpiozero: please provide python module on all architectures

2018-10-18 Thread peter green

I have chatted with Dave Jones (waveform80) about getting gpiozero support on 
more architectures. It seems sensible that as part of doing this we also 
package pigpio to support remote gpio operations.

Dominik do you mind if I add myself to the uploaders for this package and work 
on updating it to the lastest upstream version opening up the architecture list?

One thing we need to look at is making sure pi-specific code that hits hardware 
directly doesn't run on anything other than Pis. Both in gpiozero and in 
pigpio. Obviously this is a potential issue now but the risk rises as we 
package more stuff. I spoke to Dave about this at Manchester raspberry jam and 
he told me he had improved the detection in gpiozero recently, but the version 
at https://github.com/rpi-distro/python-gpiozero still seems to have the same 
code.

Dave is there an "experimental" gpiozero repository somewhere I have failed to 
find?


I don't believe any changes to the library would be required for this. The
control file
already states "Architecture: all" [1]. Is that correct, or is there
anything else required?

The gpiozero packaging in Debian and the gpiozero packaging in the raspberry pi 
foundation repo seem to be unrelated. This bug report is discussing the former.


pigpio is the C library which runs as a daemon on the Pi. It accepts remote
commands
and executes them on the Pi. The Python client (the package would be
python3-pigpio)
is pure Python and is what communicates with remote Pis.
However, both pigpio and python3-pigpio are contained within the same
source repo
on GitHub. In Raspbian we have both of these packaged.


No, you have them packaged in the rasperry pi foundation repo.

And looking at that packaging it's going to need some work before
it's something acceptable to upload to Debian.

Right now the python stuff is directed to it's own binary packages but
all the c stuff is stuffed into one binary package. I see several issues
with this package.

1. It contains not one but three shared libaries, none of which seem to have 
proper so-versioning
2. It seems to have a directory for some sort of scripts in /opt/pigpio/cgi, I 
don't think this compiles with the filesystem heirachy standard.

I will follow up these issues in more detail in another mail with a different 
recipient list (which will include https://bugs.debian.org/908787 but not 
https://bugs.debian.org/856413 )




Bug#768073: [pkg-lxc-devel] Bug#768073: LXD packaging (and lxc-go plus a little bit of salsa)

2018-10-18 Thread Jonathan Dowland

Clément Hermann wrote:

Actually, yes, it's a bit outdated. I'm currently working on the
dependancies needed for 3.0.1, see this edited output of dh-make-golang
estimate (some entries were false positive, due to different import path
that'll need to be patched, or an apparently useless for in the case of
go4):


I updated https://wiki.debian.org/LXD with the list from your email, and
then


People interested, please check the up-to-date list in the Gobby doc at
gobby.debian.org/Teams/Go/lxd-dep-packaging (or the export at
https://gobby.debian.org/export/Teams/Go/lxd-dep-packaging). It
contains comments, #ITPs, etc.


I'd never heard of Gobby before. I've linked to it from the wiki page,
but it doesn't seem to make sense to try and track this in two places.
It's kind-of unfortunate to have introduced yet-another-collaborative
editor. I'd delete the list from the wiki page and point at the Gobby
doc except I don't know how accessible that is yet, and I don't know
if the list there is current to now, either.

https://salsa.debian.org/lxc-team/lxd doesn't exist still but I guess
it wouldn't until the dependencies were done.


--

Jonathan Dowland



Bug#911302: ITP: string-template-maven-plugin -- execute other plugins within a Maven plugin

2018-10-18 Thread Andrius Merkys
Package: wnpp
Severity: wishlist
Owner: Andrius Merkys 
Control: block -1 by 911286

* Package name: string-template-maven-plugin
  Version : 1.1
  Upstream Author : Kevin Birch 
* URL : https://kevinbirch.github.io/string-template-maven-plugin
* License : MIT
  Programming Lang: Java
  Description : execute StringTemplate template files during Maven build

This plugin allows you to execute StringTemplate template files during your
build. The values for templates can come from static declarations or from a
Java class specified to be executed.

This package is a part of dependency tree to update antlr4 to v4.7.1.
The package is to be maintained inside Debian Java team.

Best,
Andrius

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



Processed: ITP: string-template-maven-plugin -- execute other plugins within a Maven plugin

2018-10-18 Thread Debian Bug Tracking System
Processing control commands:

> block -1 by 911286
Bug #911302 [wnpp] ITP: string-template-maven-plugin -- execute other plugins 
within a Maven plugin
911302 was not blocked by any bugs.
911302 was not blocking any bugs.
Added blocking bug(s) of 911302: 911286

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



Processed: retitle to RFP: python-ete3 -- Python toolkit for phylogenetic tree manipulation and visualisation.

2018-10-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> retitle 861182 RFP: python-ete3 -- Python toolkit for phylogenetic tree 
> manipulation and visualisation.
Bug #861182 [wnpp] ITP: python-ete3 -- Python toolkit for phylogenetic tree 
manipulation and visualisation.
Changed Bug title to 'RFP: python-ete3 -- Python toolkit for phylogenetic tree 
manipulation and visualisation.' from 'ITP: python-ete3 -- Python toolkit for 
phylogenetic tree manipulation and visualisation.'.
> noowner 861182
Bug #861182 [wnpp] RFP: python-ete3 -- Python toolkit for phylogenetic tree 
manipulation and visualisation.
Removed annotation that Bug was owned by Alba Crespi 
.
> stop
Stopping processing here.

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



Bug#911293: ITP: libre-engine-re2-perl -- RE2 regex engine

2018-10-18 Thread Jonas Smedegaard
Package: wnpp
Severity: wishlist
Owner: Jonas Smedegaard 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: libre-engine-re2-perl
  Version : 0.13
  Upstream Author : David Leadbeater 
* URL : https://metacpan.org/release/re-engine-RE2
* License : Artistic or GPL-1+
  Programming Lang: Perl, C
  Description : RE2 regex engine

 re::engine::RE2 replaces perl's regex engine
 in a given lexical scope with RE2.
 .
 RE2 is a primarily DFA based regexp engine from Google
 that is very fast at matching large amounts of text.
 However it does not support look behind
 and some other Perl regular expression features.
 See RE2's website at  for more information.
 .
 Fallback to normal Perl regexp is implemented by this module.
 If RE2 is unable to compile a regexp it will use Perl instead,
 therefore features not implemented by RE2 don't suddenly stop working,
 they will just use Perl's regexp implementation.

The package is an optional dependency of upcoming Licensecheck.

The package will be maintained in the Perl group.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlvIV1oACgkQLHwxRsGg
ASEaTQ/8CmNfeehPWatlPCfK5glpt5aeViUUVivKYwXpeUo01luSjDG88NkshkdG
YPBjpCCskMWKEV6YHXEn7iQVlarNo+1kX3DQjjY45+friDi8trFqimjSMt61SDs5
LTyWtAexABr2yVhaqaiDaXEOK7wkuqUjcrx66jhv11fQ4l4PDpQRz0lO8Wm+9V5M
tG7p6f1PsR9xH+H7ddc+9abzotl56FDStoY/HN8ffca13DLRiwqBK6k2rSjJWdZO
NvJpp203VF5KDdKGRF5Iji9mECvt570jfJSsrxb0TGvef7b1w25IO+GKDccyzFoT
h/HmziMPB98iO43U9SxY3eNuf8e+aeTHcn2Yr0ohI6PKvXz9y8gaUHNCb0xZIW1c
S+faVAVS4yuQNAFIOGAXy1Ez22MzaRBcYwQR3ohvEvY4RIkCV6jAcGjBkdIS33VB
QXYjQVW23qxANrjXd/qzm72M1PxbSgFUHIAWFHZz5SHv1N8f/qMDdiS4MdFE3Fku
PfcvVXBLtL5kH3rlqxrFA1qn6VNo4nyyBLnVnPIbC7MmANT+gTcFe68o1Bxlf4oc
dtKVFn7eBpMBd48wJYFMPfH938mHgCrUbcx+yoNrD5fJb3PpfPwOsm1yokbS6ou7
y8pTw/gUeU6eUAroegU21z5HwCh6CE/s3NHPWzrMouM6nGZD/hE=
=u5Zs
-END PGP SIGNATURE-



Bug#887490: Offering my help to be part of team

2018-10-18 Thread Axel Beckert
Hi Tobias,

Tobias Frost wrote:
> I've just did an QA upload of BackupPC and created a repository at
> salsa: https://salsa.debian.org/debian/backuppc

Thanks a lot, much appreciated.

> Could be a starting point for all the interested folks and non-
> developers can now also create merge-requests more easily ;-)

Will see if I can merge in the IPv6 support patches floating around.
That bothers me most.

> (I'm using BackupPPC myself, so I can volunteer helping in the
> packaging too,

Same here, but I still don't have a BackupPC running on testing, so
"testing" stuff is limited to stable.

Would you join a potential BackupPC team. I would, I just don't want
to take the lead as I have the feeling, I don't have enough time for
that.

> but with the limitation that I'm no perl guy…)

I can help there. :-)

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



Bug#893807: marked as done (ITP: libudis86 -- Disassembler Library for x86 and x86-64)

2018-10-18 Thread Debian Bug Tracking System
Your message dated Thu, 18 Oct 2018 10:30:40 +0200 (CEST)
with message-id <1817804170.133767.1539851440...@office.mailbox.org>
and subject line ITP: libudis86 -- Disassembler Library for x86 and x86-64
has caused the Debian Bug report #893807,
regarding ITP: libudis86 -- Disassembler Library for x86 and x86-64
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.)


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

* Package name: libudis86
  Version : 1.7.2
  Upstream Author : Vivek Thampi 
* URL : http://udis86.sourceforge.net
* License : BSD 2-Clause
  Programming Lang: C
  Description : Disassembler Library for x86 and x86-64

Udis86 is a disassembler for the x86 and x86-64 class of instruction set
architectures. It consists of a C library called libudis86 which
provides a clean and simple interface to decode a stream of raw binary
data, and to inspect the disassembled instructions in a structured
manner.

A lot of debian packages and even the linux kernel seem to reference this
library[1]. I need it as dependency for pev and libpe.

[1]https://codesearch.debian.net/search?q=udis86.h&page=1
--- End Message ---
--- Begin Message ---
Closing ITP because the initial reason for this ITP (libpe and pev) are not 
actively maintained upstream any more.

Regards,

Robert Haist

2BC8 3F55 A400 7468 864C 680E 1B7C C8D4 D4E9 14AA--- End Message ---


Bug#893056: marked as done (ITP: libpe1 -- The PE library used by pev)

2018-10-18 Thread Debian Bug Tracking System
Your message dated Thu, 18 Oct 2018 10:27:47 +0200 (CEST)
with message-id <678678129.133752.1539851267...@office.mailbox.org>
and subject line ITP: libpe1 -- The PE library used by pev
has caused the Debian Bug report #893056,
regarding ITP: libpe1 -- The PE library used by pev
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.)


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

* Package name: libpe1
  Version : 1.0.0
  Upstream Author : Fernando Mercês
* URL : https://github.com/merces/libpe
* License : LGPLv3
  Programming Lang: C
  Description : The PE library used by pev

Currently the pev package in debian contains the pev tools and the library,
because upstream had a single integrated repo in the past. Now upstream is
divided in two repos and we have to package the library as dependency too.
--- End Message ---
--- Begin Message ---
Close ITP because of wrong package naming.
Also the library seems to be unmaintained by upstream.

Regards,

Robert Haist

2BC8 3F55 A400 7468 864C 680E 1B7C C8D4 D4E9 14AA--- End Message ---


Bug#911286: ITP: mojo-executor -- execute other plugins within a Maven plugin

2018-10-18 Thread Andrius Merkys
Package: wnpp
Severity: wishlist
Owner: Andrius Merkys 

* Package name: mojo-executor
  Version : 2.3.0
  Upstream Author : Don Brown 
* URL : https://timmoore.github.com/mojo-executor/
* License : Apache-2.0 or GPL-2
  Programming Lang: Java
  Description : execute other plugins within a Maven plugin

The Mojo Executor provides a way to execute other Mojos (plugins) within a
Maven plugin, allowing you to easily create Maven plugins that are composed
of other plugins.

This package is a part of dependency tree to update antlr4 to v4.7.1.
The package is to be maintained inside Debian Java team.

Best,
Andrius

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