Bug#996009: RFS: iotop-c/1.20-1~bpo11+1 -- simple top-like I/O monitor (implemented in C)

2021-10-09 Thread Boian Bonev
Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "iotop-c":

 * Package name: iotop-c
   Version : 1.20-1~bpo11+1
   Upstream Author : Boian Bonev 
 * URL : https://github.com/Tomas-M/iotop
 * License : GPL-2.0+
 * Vcs : https://github.com/Tomas-M/iotop
   Section : admin

It builds those binary packages:

  iotop-c - simple top-like I/O monitor (implemented in C)

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

  https://mentors.debian.net/package/iotop-c/

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

  dget -x 
https://mentors.debian.net/debian/pool/main/i/iotop-c/iotop-c_1.20-1~bpo11+1.dsc

Changes since the last upload:

 iotop-c (1.20-1~bpo11+1) bullseye-backports; urgency=medium
 .
   * Rebuild for bullseye-backports.

Regards,
-- 
  Boian Bonev



Re: Handling files with no copyright notices, many contributors

2021-10-09 Thread gregor herrmann
On Sat, 09 Oct 2021 18:51:37 +, John Scott wrote:

> It includes a statement that the license is GPL 2 only with system
> calls note (basically a GPL exception), and it's already distributed as
> part of the kernel, so surely it's free. However, I'm having trouble
> figuring out what to put in my DEP-5 copyright file.
> 
> Linux Git shows that this file has had too many contributors to
> enumerate, and in fact it's been in Linux since before 2.6.12-rc2,
> which is the oldest version in the main repo's history.
> 
> Documenting everyone that has ever contributed to this file would take
> an immense amount of time and is beyond practical.

The relevant question in my understanding is (in general) not "Who
are the contributors?" but "Who are the copyright holders?" [0]

If the file is taken from the kernel source I'd take a look at the
copyright file of source:linux-signed-amd64.

Taking /usr/share/doc/linux-image-5.10.0-8-amd64/copyright on my
disk, ch9.h doesn't seem to be mentioned, so it would seem to fall
under the general clause:

| Files: *
| Copyright: 1991-2012 Linus Torvalds and many others
| License: GPL-2


Cheers,
gregor


[0] Unless there are no copyright holder, then authors can be assumed
to be copyright holders, following the Geneva Convention. - But
that's not the case for the kernel.

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Pat Metheny, B.B. King, Dave Brubeck: Pat Metheny & Heath Brothers /


signature.asc
Description: Digital Signature


Bug#996004: RFS: connman/1.36-2.2 [NMU] [RC] -- Intel Connection Manager daemon

2021-10-09 Thread Ross Vandegrift
Package: sponsorship-requests
Severity: important
X-Debbugs-Cc: rvandegr...@debian.org

Dear mentors,

I am looking for a sponsor for the package "connman":

 * Package name: connman
   Version : 1.36-2.2
   Upstream Author : Marcel Holtmann
 * URL : 
 * License : GPL-2.0, GPL-2.0+
 * Vcs : https://git.kernel.org/pub/scm/network/connman/connman.git/
   Section : net

The release is waiting in this MR:

  https://salsa.debian.org/debian/connman/-/merge_requests/6

I cannot upload since I am DN, and this package isn't in my dak ACL.  The
uploader and maintainer seem inactive for some years, and #979100 has been open
without reply since January.

I don't know if I'm willing to salvage - enlightenment has a B-D on connman,
but I don't actually use it.

Changes since the last upload:

  connman (1.36-2.2) unstable; urgency=medium
  .
* Non-maintainer upload.
* d/copyright: license on client/* is GPL-2+
  Upstream commit 27e37a50 relicensed this to GPL-2+ to fix the license
  incompatibility with GPL-3+ releases of libreadline. (Closes: #979100)

Thanks,
Ross



Bug#994724: RFS: lebiniou-data/3.62.1-1 -- datafiles for Le Biniou

2021-10-09 Thread Olivier Girondel
Thanks, I think it needs the main lebiniou package for the test to succeed, 
since the printing to stderr is fixed there
Regards,

On October 9, 2021 10:39:32 PM GMT+02:00, Adam Borowski  
wrote:
>On Sat, Oct 09, 2021 at 04:31:48PM +0200, Olivier Girondel wrote:
>> Hi Adam,
>> 
>> Any news on this ?
>
>The autopkgtest for lebiniou-data still fails the same way.
>
>I've uploaded as-is, though, as it's possible the official machines are
>configured in a different way.  A bug that affects the schroot backend is
>still a bug, but I don't know if it will cause a failure here.
>
>
>Meow!
>-- 
>⢀⣴⠾⠻⢶⣦⠀
>⣾⠁⢠⠒⠀⣿⡁
>⢿⡄⠘⠷⠚⠋⠀ ᛊᚨᚾᛁᛏᚣ᛫ᛁᛊ᛫ᚠᛟᚱ᛫ᚦᛖ᛫ᚹᛖᚨᚲ
>⠈⠳⣄
>

-- 
Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma 
brièveté.

Bug#995993: RFS: zydis/3.1.0-1 [ITP] -- fast and lightweight x86/x86-64 disassembler library

2021-10-09 Thread Andrea Pappacoda
Package: sponsorship-requests
Severity: wishlist

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear mentors,

I am looking for a sponsor for my package "zydis":

 * Package name: zydis
   Version : 3.1.0-1
   Upstream Author : zyantific 
 * URL : https://zydis.re
 * License : Expat
   Section : libs

It builds those binary packages:

  libzydis-dev - fast and lightweight x86/x86-64 disassembler library -
development
  libzydis3.1 - fast and lightweight x86/x86-64 disassembler library

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

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

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

  dget -x https://mentors.debian.net/debian/pool/main/z/zydis/zydis_3.1.0-1.dsc

Changes for the initial release:

 zydis (3.1.0-1) unstable; urgency=low
 .
   * Initial release. Closes: #995921

Regards,
- --
  Andrea Pappacoda


-BEGIN PGP SIGNATURE-

iIoEARYIADIWIQRm3vFSgpkMIZnvqAGooSioqxzuSQUCYWHGABQcYW5kcmVhQHBh
cHBhY29kYS5pdAAKCRCooSioqxzuSWmMAQCPNODE2jzrDOrHuJengmbyDEVYgjGm
o2a0Mnej8iPqFwEAiXiqePle70zr/zCiObIH+uV1jlrgjuPhOYRW4CmoJAo=
=fMxW
-END PGP SIGNATURE-



Bug#994724: RFS: lebiniou-data/3.62.1-1 -- datafiles for Le Biniou

2021-10-09 Thread Adam Borowski
On Sat, Oct 09, 2021 at 04:31:48PM +0200, Olivier Girondel wrote:
> Hi Adam,
> 
> Any news on this ?

The autopkgtest for lebiniou-data still fails the same way.

I've uploaded as-is, though, as it's possible the official machines are
configured in a different way.  A bug that affects the schroot backend is
still a bug, but I don't know if it will cause a failure here.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁
⢿⡄⠘⠷⠚⠋⠀ ᛊᚨᚾᛁᛏᚣ᛫ᛁᛊ᛫ᚠᛟᚱ᛫ᚦᛖ᛫ᚹᛖᚨᚲ
⠈⠳⣄



Re: URL is OK in browser but returns 404 with uscan

2021-10-09 Thread Dominik George
> > Any idea how to help uscan reading that web page?
> 
> https://storage.googleapis.com/broad-alkesgroup-public?delimiter=/=BOLT-LMM/downloads/
> gets you a step further.

Digging a bit, there is actually an example for this in the uscan man
page (grep for AWS).

Find attached a patch for your package ☺.

*snip*
uscan info:  => Package is up to date from:
 => 
https://storage.googleapis.com/BOLT-LMM/downloads/BOLT-LMM_v2.3.5.tar.gz
uscan info:  => Forcing download as requested
uscan info: Downloading upstream package: BOLT-LMM_v2.3.5.tar.gz
*snip*

HTH,
Nik
From 8179eb9c8fc787d8d32d5fb5cf9ac9d604af3658 Mon Sep 17 00:00:00 2001
From: Dominik George 
Date: Sat, 9 Oct 2021 22:07:39 +0200
Subject: [PATCH] Correctly scan S3 bucket in d/watch

---
 debian/changelog | 4 +++-
 debian/watch | 4 ++--
 2 files changed, 5 insertions(+), 3 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index 879f2a0..d2abc9c 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,7 +1,9 @@
 bolt-lmm (2.3.5+dfsg-2) UNRELEASED; urgency=medium
 
   * Team upload.
-  TODO: Try to fix watch file ... but failed
+
+  [ Dominik George ]
+  * Scan and mangle S3 bucket list in d/watch.
 
  -- Andreas Tille   Sat, 09 Oct 2021 08:29:36 +0200
 
diff --git a/debian/watch b/debian/watch
index e1e1447..761a3a6 100644
--- a/debian/watch
+++ b/debian/watch
@@ -1,3 +1,3 @@
 version=4
-opts="repacksuffix=+dfsg,dversionmangle=s/\+dfsg//g,repack,compression=xz" \
-  https://alkesgroup.broadinstitute.org/BOLT-LMM/downloads/ .*/BOLT-LMM_v@ANY_VERSION@@ARCHIVE_EXT@
+opts="repacksuffix=+dfsg,dversionmangle=s/\+dfsg//g,pagemangle=s%([^<]*)%$1%g,repack,compression=xz" \
+  https://storage.googleapis.com/broad-alkesgroup-public?prefix=BOLT-LMM/downloads/ (?:.*)BOLT-LMM_v@ANY_VERSION@@ARCHIVE_EXT@
-- 
2.33.0



signature.asc
Description: PGP signature


Re: URL is OK in browser but returns 404 with uscan

2021-10-09 Thread Dominik George
Hi,

On Sat, Oct 09, 2021 at 09:46:51PM +0200, Andreas Tille wrote:
> Hi,
> 
> when I try to visit
> 
> https://alkesgroup.broadinstitute.org/BOLT-LMM/downloads/
> 
> with any browser I get a list of files.  However, the watch file
> of bolt-lmm[1] pointing to that web page returns:

You don't get a list of files. You get the same 404. Only there is
JavaScript on the page that in turn loads and renders the list of
files…

> Any idea how to help uscan reading that web page?

https://storage.googleapis.com/broad-alkesgroup-public?delimiter=/=BOLT-LMM/downloads/
gets you a step further.


It's a brave new world!

-nik


signature.asc
Description: PGP signature


URL is OK in browser but returns 404 with uscan

2021-10-09 Thread Andreas Tille
Hi,

when I try to visit

https://alkesgroup.broadinstitute.org/BOLT-LMM/downloads/

with any browser I get a list of files.  However, the watch file
of bolt-lmm[1] pointing to that web page returns:

$ uscan --verbose --report
uscan info: uscan (version 2.21.3) See uscan(1) for help
uscan info: Scan watch files in .
uscan info: Check debian/watch and debian/changelog in .
uscan info: package="bolt-lmm" version="2.3.5+dfsg-2" (as seen in 
debian/changelog)
uscan info: package="bolt-lmm" version="2.3.5+dfsg" (no epoch/revision)
uscan info: ./debian/changelog sets package="bolt-lmm" version="2.3.5+dfsg"
uscan info: Process watch file at: debian/watch
package = bolt-lmm
version = 2.3.5+dfsg
pkg_dir = .
uscan info: opts: 
repacksuffix=+dfsg,dversionmangle=s/\+dfsg//g,repack,compression=xz
uscan info: line: https://alkesgroup.broadinstitute.org/BOLT-LMM/downloads/ 
.*/BOLT-LMM_v(?:[-_]?(\d[\-+\.:\~\da-zA-Z]*))(?i)(?:\.(?:tar\.xz|tar\.bz2|tar\.gz|zip|tgz|tbz|txz))
uscan info: Parsing repacksuffix=+dfsg
uscan info: Parsing dversionmangle=s/\+dfsg//g
uscan info: Parsing repack
uscan info: Parsing compression=xz
uscan info: line: https://alkesgroup.broadinstitute.org/BOLT-LMM/downloads/ 
.*/BOLT-LMM_v(?:[-_]?(\d[\-+\.:\~\da-zA-Z]*))(?i)(?:\.(?:tar\.xz|tar\.bz2|tar\.gz|zip|tgz|tbz|txz))
uscan info: Last orig.tar.* tarball version (from debian/changelog): 2.3.5+dfsg
uscan info: Last orig.tar.* tarball version (dversionmangled): 2.3.5
uscan info: Requesting URL:
   https://alkesgroup.broadinstitute.org/BOLT-LMM/downloads/
uscan warn: In watchfile debian/watch, reading webpage
  https://alkesgroup.broadinstitute.org/BOLT-LMM/downloads/ failed: 404 Not 
Found
uscan info: Scan finished

Any idea how to help uscan reading that web page?

Kind regards

 Andreas.


[1] https://salsa.debian.org/med-team/bolt-lmm/-/blob/master/debian/watch

-- 
http://fam-tille.de



Handling files with no copyright notices, many contributors

2021-10-09 Thread John Scott
Hi,

My question is more to do with the practical ramifications of an upload
than the legal ones, so I'm directing my query here rather than debian-
legal.

I'm packaging carl9170fw (which is already present in Debian main, but
not built from source yet), and this includes a header file called
ch9.h that's taken almost verbatim from the Linux kernel source.

It includes a statement that the license is GPL 2 only with system
calls note (basically a GPL exception), and it's already distributed as
part of the kernel, so surely it's free. However, I'm having trouble
figuring out what to put in my DEP-5 copyright file.

Linux Git shows that this file has had too many contributors to
enumerate, and in fact it's been in Linux since before 2.6.12-rc2,
which is the oldest version in the main repo's history.

Documenting everyone that has ever contributed to this file would take
an immense amount of time and is beyond practical. What's the best
remedy that would satisfy the FTP masters as well as satisfy
prospective sponsors? In this statement from the FTP team [1], they
said that further exceptions for cases like this would not be allowed.

[1] https://lists.debian.org/debian-devel-announce/2018/10/msg4.html


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


Bug#995995: RFS: nemo-compare/5.0.1-1 [ITP] -- Context menu comparison extension for Nemo file manager

2021-10-09 Thread Joshua Peisach
Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "nemo-compare":

 * Package name: nemo-compare
   Version : 5.0.1-1
   Upstream Author : Clement Lefebvre 
 * URL : https://community.linuxmint.com/software/view/nemo-compare
 * License : GPL-3+
 * Vcs : https://salsa.debian.org/cinnamon-team/nemo-compare
   Section : utils

It builds those binary packages:

  nemo-compare - Context menu comparison extension for Nemo file manager

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

  https://mentors.debian.net/package/nemo-compare/

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

  dget -x 
https://mentors.debian.net/debian/pool/main/n/nemo-compare/nemo-compare_5.0.1-1.dsc

Changes for the initial release:

 nemo-compare (5.0.1-1) unstable; urgency=medium
 .
   * Initial release. (Closes: #972359)

Regards,
--
  Joshua Peisach



Bug#994724: RFS: lebiniou-data/3.62.1-1 -- datafiles for Le Biniou

2021-10-09 Thread Olivier Girondel

Hi Adam,

Any news on this ?

Best regards,

--
Olivier Girondel