Bug#839114: marked as done (RFS: [ITA] Hi, I'd like to adopt systemd-shim)

[Debian Bug Tracking System]

Your message dated Wed, 28 Sep 2016 21:05:23 -0700
with message-id <20160929040523.4k2x6radukoqi...@hephaestus.silentflame.com>
and subject line Re: Bug#839114: RFS: [ITA] Hi, I'd like to adopt systemd-shim
has caused the Debian Bug report #839114,
regarding RFS: [ITA] Hi, I'd like to adopt systemd-shim
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.)


-- 
839114: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839114
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: normal [important for RC bugs, wishlist for new packages]

  Dear mentors,

  Hello.  I'd like to adopt the systemd-shim package.  I suppose I
would need a sponsor/mentor to do that?

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

It looks like it's up for adoption.  To sell myself a little I have a
bachelors in compsci.

Hopefully this will be a fairly low-effort package requiring only
sporadic attention.

  Thanks, Alex
--- End Message ---
--- Begin Message ---
Dear Ab,

You need to prepare a proposed upload of the package, and upload it
somewhere (usually mentors.debian.net), before filing the RFS bug.

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

-- 
Sean Whitton


signature.asc
Description: PGP signature
--- End Message ---

Bug#839114: RFS: [ITA] Hi, I'd like to adopt systemd-shim

[Ab B]

Package: sponsorship-requests
Severity: normal [important for RC bugs, wishlist for new packages]

  Dear mentors,

  Hello.  I'd like to adopt the systemd-shim package.  I suppose I
would need a sponsor/mentor to do that?

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

It looks like it's up for adoption.  To sell myself a little I have a
bachelors in compsci.

Hopefully this will be a fairly low-effort package requiring only
sporadic attention.

  Thanks, Alex

Bug#837798: RFS: libcgicc/3.2.16-0.1 NMU -- C++ class library for writing CGI applications

[Gianfranco Costamagna]

Hi

> They are both used in the build. But if I understand you right, are you 
> suggesting to drop the explicit dependencies since dh-autoreconf already 
> depends on automake and libtool? If this is the customary way then I'll 
> drop the explicit dependencies on automake and libtool.

I think so. dh-autoreconf should be enough (with an added pkg-config if needed,
IIRC)

> This file is made obsolete by the pkg-config file, and it was creating a 
> problem for multiarch packages: it would install in 
> /usr/bin/cgicc-config, making it impossible to install two architectures 
> of this package.

this is a problem when the files are not bit-bit identical between 
architecture, and
this seems to be this case
## Host information
--host)echo "x86_64-pc-linux-gnu" && exit 0 ;;  

this changes.

You can patch that change out, as example you can grab what we did for 
libpng1.6[1]
or try to print the triplet at runtime, when the user asks for it

maybe dpkg-architecture has something interesting for you

[1] 
https://sources.debian.net/src/libpng1.6/1.6.25-1/debian/patches/libpng-config.patch/

> | Using this kind of system to pass compile file is obsolete and will 
> likely introduce bugs in a multi-arch system.
> | Particularly, this kind of script could only belong to a package that 
> is not Multi-Arch.
> 
> So I took this as excuse to remove the file from the package.
> 
> One possible solution (suggested by lintian) is to move the file out of 
> the way (to /usr/share/doc, I presume) so it is still shipped, but it 
>won't be found by build tools, which kind of defeats its purpose. I'm 
>doubtful there is any benefit in shipping this file.

I think patching it to be architecture independent might be the best solution

>As far as I can see from the CVS changes, the 'current' value in the 
>soname was increased in the early 2000's, presumably due to ABI changes. 
>Then in 2013 the soname was decreased from 5 to 3 in order to match the 
>library version. This was done as part of these bugs:
>
>I presume the package should follow the upstream soname. And this would 
>probably also justify the renamed package, as you were musing in your 
>mail. If there are no objections, I will rename the packages from 
>libcgicc5 to libcgicc.

libcgicc3 you mean :)

>This should be fixed by the renaming from libcgicc5* -> libcgicc*.

always a final 3

>Raised as https://savannah.gnu.org/bugs/index.php?49120

>Thinking again, I guess that's not correct. This would require the 
>packages to be renamed to libcgicc3.

oops you got it already

>I have uploaded a new build to debian mentors for further review.
I'll have a look if you can provide an answer to my above comments :)

thanks!

Gianfranco



signature.asc
Description: OpenPGP digital signature

Bug#838859: marked as done (RFS: clipf/0.4-2 [QA])

[Debian Bug Tracking System]

Your message dated Wed, 28 Sep 2016 20:36:57 + (UTC)
with message-id <1332832103.805778.1475095017...@mail.yahoo.com>
and subject line Re: Bug#838859: RFS: clipf/0.4-2 [QA]
has caused the Debian Bug report #838859,
regarding RFS: clipf/0.4-2 [QA]
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.)


-- 
838859: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838859
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
  Severity: normal

  Dear mentors,

  I am looking for a sponsor for my package "clipf"

 * Package name: clipf
   Version : 0.4-2
   Upstream Author : Galtsev Denis 
 * URL : http://code.google.com/p/clipf/
 * License : GPL-2+
   Section : misc

  It builds those binary packages:

clipf - command line minimalistic personal finance manager

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

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


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

dget -x https://mentors.debian.net/debian/pool/main/c/clipf/clipf_0.4-2.dsc


  Regards,
   Gustavo Soares de Lima
--- End Message ---
--- Begin Message ---
Hi,


>clipf

done :)

G.--- End Message ---

Bug#838575: marked as done (RFS: flask-compress/1.3.1-1 [ITP])

[Mattia Rizzolo]

> >It went to "found a sponsor, had to change something, did not reupload 
> >because sponsor does not use mentors" ;).
> 
> 
> well, so in this case it is good to have it close, avoiding double reviews 
> since
> you already have somebody who picked up the work!

well, or put an Owner on the bug, which would be me...

anyway, nevermind, I'll handle it as soon as you poke me on IRC.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#838575: marked as done (RFS: flask-compress/1.3.1-1 [ITP])

[Debian Bug Tracking System]

Your message dated Wed, 28 Sep 2016 18:42:00 + (UTC)
with message-id <1779962806.714628.1475088120...@mail.yahoo.com>
and subject line Re: Bug#838575: RFS: flask-compress/1.3.1-1 [ITP]
has caused the Debian Bug report #838575,
regarding RFS: flask-compress/1.3.1-1 [ITP]
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.)


-- 
838575: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838575
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: wishlist

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear mentors,

I am looking for a sponsor for my package "flask-compress"

 * Package name: flask-compress
   Version : 1.3.1-1
   Upstream Author : William Fagan
 * URL : https://github.com/libwilliam/flask-compress
 * License : MIT
   Section : python

It builds those binary packages:

  python-flask-compress - Compress responses in a Flask app with gzip (Python 2)
  python3-flask-compress - Compress responses in a Flask app with gzip (Python 
3)

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

  https://mentors.debian.net/package/flask-compress

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

  dget -x 
https://mentors.debian.net/debian/pool/main/f/flask-compress/flask-compress_1.3.1-1.dsc


Flask-Compress is an extension for the popular Flask micro-framework for web 
applications.

  Regards,
   Dominik George
-BEGIN PGP SIGNATURE-

iQJhBAEBCABLBQJX4/Q2MRpodHRwczovL3d3dy5kb21pbmlrLWdlb3JnZS5kZS9n
cGctcG9saWN5LnR4dC5hc2MSHG5pa0BuYXR1cmFsbmV0LmRlAAoJELeaPBagxPKW
EHQP/RlBk46ylNURHGc+Q9S1GznIsFC60YH+sEq1Kb0jZ+go2sDRCO6zoQBG06OH
19OQxa+u/KVdlw23J78sckeFC9Q/Z5vmGKG9f73SfEBSwkwJT1jJLJCr66OyXu1j
RYvD1yebcHMGDuvVkK8NOHN+Trd4TA9EA9OG3DGMLRlj5jbkmEoayH1VP4J/kSZd
3Cn3RqwKifACCTOzRuQzUik5rE5rQ+5pBHFdkZM8zRkjwHxWDOmKcGp6+2uYx2ep
Qu9GH2nZsuQF/+Quw9etiU1f9K3Dj872SpOU78zCHtjsxlYEmOlsmi1vCK89JDDp
kobKTwc9mXiG/aTevKhJBPmaT4JTmKSNXk1gJUxiTaHPnDK+W3J2MSUODJAf4Yzd
+kaz5lLAh3iLeiFloowVSZ78QhZAboaaRpoZrJ4DlDahMupkflHpj9q72f0RvFIq
NLR4sm44D2xegYLOjJdYVYMXxANoSQM9nYGU/vgNBUiihE+z7tR143zyJT2Lya9m
pJWlbaGLMyIVm0UmGJnNFom+vcuElrlEo6m9Gx5sJCi8bjbPfeL4OIhmQW1KNFd4
3duqOAYDQUzlvrdSOIzsuuWqAV8xvmgFIRJcLREE4QVj9TyDwayXDUdu+TGkI7Ib
yA0XIvXulNrs3VZ4pfhv2dzG/JuJI2CjrTni+7i+Zjf71LWH
=jWru
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Hi,


>It went to "found a sponsor, had to change something, did not reupload because 
>sponsor does not use mentors" ;).


well, so in this case it is good to have it close, avoiding double reviews since
you already have somebody who picked up the work!

G.--- End Message ---

Bug#838004: marked as done (RFS: rear/1.18-1 ITP: rear -- Bare metal disaster recovery and system migration framework)

[Debian Bug Tracking System]

Your message dated Wed, 28 Sep 2016 18:38:59 + (UTC)
with message-id <1232100538.715019.1475087939...@mail.yahoo.com>
and subject line Re: Bug#838004: RFS: rear/1.18-1 ITP: rear -- Bare metal 
disaster recovery and system migration framework
has caused the Debian Bug report #838004,
regarding RFS: rear/1.18-1 ITP: rear -- Bare metal disaster recovery and system 
migration framework
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.)


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


Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "rear"

 Package name: rear
 Version : 1.18-1
 Upstream Author : Schlomo Schapiro, Gratien D'haese, Stefan Semmelroggen, Peer 
Heinlein, Dag Wieers, Jeroen Hoekx
 URL : https://github.com/rear/rear/
 License : GPL-3+, LGPL-2.1+, GPL-2+, CC-BY-ND-3.0
 Section : admin

It builds those binary packages:

  rear  - Bare metal disaster recovery and system migration framework
  rear-doc   - Bare metal disaster recovery and system migration framework 
(documentation)

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

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


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

  dget -x https://mentors.debian.net/debian/pool/main/r/rear/rear_1.18-1.dsc

More information about rear can be obtained from http://relax-and-recover.org/

Note:
  There is a load of Info lintians but this is due to the fact that rear embeds
  skeleton files/dirs that won't be use by the system installing rear, but
  those files will be used by the rear OS created to be booted later.


Regards,
 Frederic Bonnard
--- End Message ---
--- Begin Message ---
Hi,

>I am looking for a sponsor for my package "rear"



I see many "copyright matches no file" lintian warnings, but files are there.
Not sure what is wrong, but I sponsored it anyway.

cheers,

G.--- End Message ---

Bug#838575: RFS: flask-compress/1.3.1-1 [ITP]

[Dominik George]

Control: reopen -1

Hi,

>>I am looking for a sponsor for my package "flask-compress"
>
>
>where did the package go?

It went to "found a sponsor, had to change something, did not reupload because 
sponsor does not use mentors" ;).

-nik

Bug#838679: [Debian-science-sagemath] Fwd: Bug#838679: RFS: cysignals/1.1.1+ds-1 [ITP] -- interrupt and signal handling for Cython

[Ximin Luo]

Ximin Luo:
> Hey, nice work. I'm taking a look now.
> 

Hey, it looks good! I couldn't spot any problems.

Just the following minor things:

(1) 

d/rules:
override_dh_install-arch:
true

Could you add a comment explaining this? I didn't look in too much detail but I 
couldn't figure out the reason for this. I did run dpkg-buildpackage -A and -B 
checked they still work, so that's good. It would be good to add a comment, so 
future readers don't get confused.

(2)

Instead of maintaining two separate git branches, I suggest using build 
profiles:

https://wiki.debian.org/BuildProfileSpec

I've pushed some commits to the git repo that makes this work already, see if 
you like them, or revert if you don't :p

The default build will leave out the -pari stuff. To enable the pari stuff, you 
can either :

a. use `(dpkg-buildpackage|gbp buildpackage) -Ppkg.cysignals.pari` or
b. set DEB_BUILD_PROFILES=pkg.cysignals.pari for lower-level tools like 
`debian/rules`

I had to use a slight hack in debian/tests/control but I thought it was still 
worth it, to avoid switching between branches all the time.

If you like this, please also edit debian/README.source to describe this new 
workflow.

(3)

You tagged debian/1.1.1+ds-1 already in the git repo. I suggest not doing this 
yet, and delete the current tag - we have some newer unreleased commits anyway.

My preferred workflow is to keep UNRELEASED in d/changelog, then when 
everything is ready I git push, then `dch -r`, commit, build, dput and wait for 
the ACCEPTED email from ftp-masters. Only after I get email, do I then run `gbp 
buildpackage --git-tag-only` and then push this last commit plus the tag that 
was just created.

Sometimes (like now) there's no point using UNRELEASED if d/changelog already 
says something else, but the rest of the above still works.

X

-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git

Bug#839065: RFS: pyzo/4.3-1

[Gianfranco Costamagna]

Hi,

>It is currently used and in a way that makes bypassing the vendoring
>not trivial. I filed a bug upstream [1] to ask for a better solution.



I'm sure you already know why this is bad, so I'll leave it in deferred/5, maybe
in the meanwhile upstream writes a patch :)

G.

Bug#839065: RFS: pyzo/4.3-1

[Ghislain Vaillant]

On 28/09/16 17:30, Gianfranco Costamagna wrote:

Hi Ghislain,


Argh, I though Almar did not embed QtPy in the codebase. My bad.







I pushed a new version on mentors with the updated d/copyright.

is that embedded copy used or not?

while waiting for the answer, I pushed it in deferred/5

G.


It is currently used and in a way that makes bypassing the vendoring
not trivial. I filed a bug upstream [1] to ask for a better solution.

[1] https://github.com/pyzo/pyzo/issues/440

Ghis

Bug#838801: marked as done (RFS: zxcvbn-c/0.20150103-1 [ITP])

[Debian Bug Tracking System]

Your message dated Wed, 28 Sep 2016 16:51:25 + (UTC)
with message-id <2060439112.627156.1475081485...@mail.yahoo.com>
and subject line Re: Bug#838801: RFS: zxcvbn-c/0.20150103-1 [ITP]
has caused the Debian Bug report #838801,
regarding RFS: zxcvbn-c/0.20150103-1 [ITP]
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.)


-- 
838801: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838801
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: wishlist
Control: block 838492 by -1

Dear mentors,

I am looking for a sponsor for my package "zxcvbn-c".

This is a shlib dependency of a Haskell library I want to package, on
the way to packaging keysafe, the latest cool project from Joey Hess:

https://joeyh.name/code/keysafe/

* Package name: zxcvbn-c
  Version : 0.20150103-1
  Upstream Author : Tony Evans
* URL : https://github.com/tsyrogit/zxcvbn-c
* License : BSD-3-clause
  Section : libs

It builds those binary packages:

libzxcvbn-dev - password strength estimation library - development files
libzxcvbn0 - password strength estimation library

Mentors information page:

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

Download with dget:

dget -x 
https://mentors.debian.net/debian/pool/main/z/zxcvbn-c/zxcvbn-c_0.20150103-1.dsc

Or build it with gbp:

gbp clone --pristine-tar https://git.spwhitton.name/zxcvbn-c
git checkout debian/0.20150103-1
git verify-tag debian/0.20150103-1 # my key is in DM keyring
gbp buildpackage

-- 
Sean Whitton


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Hi,

it is on its way for new queue

G.--- End Message ---

Bug#838801: RFS: zxcvbn-c/0.20150103-1 [ITP]

[Sean Whitton]

control: tags -1 -moreinfo

Hello Gianfranco,

On Wed, Sep 28, 2016 at 02:29:42PM +, Gianfranco Costamagna wrote:
> control: owner -1 !

Thank you for your interest!
>
> CFLAGS ?= -O2 -Wall -Wextra -Wdeclaration-after-statement
> CPPFLAGS ?= -O2 -Wall -Wextra
> 
> 
> this is a no-op I guess, maybe a "+=" might be better

As discussed on IRC, I'd prefer to keep it this way -- these are
upstream's choice of flags, and we have our own set which can be allowed
to override them.  They're there in case someone wants to build the
library outside of Debian.

>
> gcc $(CFLAGS) $(LDFLAGS) -fPIC -shared -Wl,-soname,$(SONAME) -o $@ $^
> -lm
> 
> this is wrong in many places, e.g.:
> 
> "gcc" might be a $(CC)
> with 
> 
> $(CC) ?= gcc
> as example (I don't see a good reason for forcing a gcc when people might want
> to try to build it with clang as example)
> 
> LDFLAGS should be at the bottom of the ine, just before -lm, to avoid 
> stripping
> with wl-asneeded flag (and build failures)
> 
> 
> blhc:
> 
> CXXFLAGS missing (-g -O2 -fPIE -fstack-protector-strong -Wformat 
> -Werror=format-security): g++ -std=c++11 -Wdate-time -D_FORTIFY_SOURCE=2 -I. 
> -o dictgen dict-generate.cpp
> LDFLAGS missing (-fPIE -pie -Wl,-z,relro -Wl,-z,now): g++ -std=c++11 
> -Wdate-time -D_FORTIFY_SOURCE=2 -I. -o dictgen dict-generate.cpp
> CPPFLAGS missing (-D_FORTIFY_SOURCE=2): gcc -g -O2 
> -fdebug-prefix-map=/<>=. -fPIE -fstack-protector-strong -Wformat 
> -Werror=format-security -I. -DUSE_DICT_FILE -c -o zxcvbn-file.o zxcvbn.c

All fixed, thanks.

> deb files: -rw-r--r-- root/root 568880 2016-09-25 01:14
> ./usr/lib/x86_64-linux-gnu/libzxcvbn.a
> 
> static library? ok if you think it is useful

I've pushed a new tag debian/0.20160925-1 to my git repository, and
updated mentors:

dget -x 
https://mentors.debian.net/debian/pool/main/z/zxcvbn-c/zxcvbn-c_0.20160925-1.dsc

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#838575: RFS: flask-compress/1.3.1-1 [ITP]

[Gianfranco Costamagna]

Hi Dominik


>I am looking for a sponsor for my package "flask-compress"


where did the package go?

G.

Bug#839065: marked as done (RFS: pyzo/4.3-1)

[Debian Bug Tracking System]

Your message dated Wed, 28 Sep 2016 16:30:03 + (UTC)
with message-id <1644257473.553742.1475080203...@mail.yahoo.com>
and subject line Re: Bug#839065: RFS: pyzo/4.3-1
has caused the Debian Bug report #839065,
regarding RFS: pyzo/4.3-1
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.)


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

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "pyzo"

* Package name: pyzo
  Version : 4.3-1
* License : BSD
  Section : science

It builds those binary packages:

   iep   - transitional dummy package for IEP
   pyzo  - interactive editor for scientific Python
   pyzo-doc   - documentation for Pyzo

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


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

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

   dget -x 
https://mentors.debian.net/debian/pool/main/p/pyzo/pyzo_4.3-1.dsc


Successful builds on debomatic:


http://debomatic-amd64.debian.net/distribution#unstable/pyzo/4.3-1/buildlog

Changes since the last upload:

   * New upstream release.
   * Change install dependencies for pyzo.
 - Remove dependency on pyzolib, now merged into pyzo.
 - Add transitive dependency on Qt via QtPy.
   * Sort install dependencies of iep.

Regards,
Ghislain Vaillant
--- End Message ---
--- Begin Message ---
Hi Ghislain,

>Argh, I though Almar did not embed QtPy in the codebase. My bad.

>

>I pushed a new version on mentors with the updated d/copyright.
is that embedded copy used or not?

while waiting for the answer, I pushed it in deferred/5

G.--- End Message ---

Bug#838575: marked as done (RFS: flask-compress/1.3.1-1 [ITP])

[Debian Bug Tracking System]

Your message dated Wed, 28 Sep 2016 16:26:46 +
with message-id 
and subject line closing RFS: flask-compress/1.3.1-1 [ITP]
has caused the Debian Bug report #838575,
regarding RFS: flask-compress/1.3.1-1 [ITP]
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.)


-- 
838575: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838575
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: wishlist

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear mentors,

I am looking for a sponsor for my package "flask-compress"

 * Package name: flask-compress
   Version : 1.3.1-1
   Upstream Author : William Fagan
 * URL : https://github.com/libwilliam/flask-compress
 * License : MIT
   Section : python

It builds those binary packages:

  python-flask-compress - Compress responses in a Flask app with gzip (Python 2)
  python3-flask-compress - Compress responses in a Flask app with gzip (Python 
3)

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

  https://mentors.debian.net/package/flask-compress

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

  dget -x 
https://mentors.debian.net/debian/pool/main/f/flask-compress/flask-compress_1.3.1-1.dsc


Flask-Compress is an extension for the popular Flask micro-framework for web 
applications.

  Regards,
   Dominik George
-BEGIN PGP SIGNATURE-

iQJhBAEBCABLBQJX4/Q2MRpodHRwczovL3d3dy5kb21pbmlrLWdlb3JnZS5kZS9n
cGctcG9saWN5LnR4dC5hc2MSHG5pa0BuYXR1cmFsbmV0LmRlAAoJELeaPBagxPKW
EHQP/RlBk46ylNURHGc+Q9S1GznIsFC60YH+sEq1Kb0jZ+go2sDRCO6zoQBG06OH
19OQxa+u/KVdlw23J78sckeFC9Q/Z5vmGKG9f73SfEBSwkwJT1jJLJCr66OyXu1j
RYvD1yebcHMGDuvVkK8NOHN+Trd4TA9EA9OG3DGMLRlj5jbkmEoayH1VP4J/kSZd
3Cn3RqwKifACCTOzRuQzUik5rE5rQ+5pBHFdkZM8zRkjwHxWDOmKcGp6+2uYx2ep
Qu9GH2nZsuQF/+Quw9etiU1f9K3Dj872SpOU78zCHtjsxlYEmOlsmi1vCK89JDDp
kobKTwc9mXiG/aTevKhJBPmaT4JTmKSNXk1gJUxiTaHPnDK+W3J2MSUODJAf4Yzd
+kaz5lLAh3iLeiFloowVSZ78QhZAboaaRpoZrJ4DlDahMupkflHpj9q72f0RvFIq
NLR4sm44D2xegYLOjJdYVYMXxANoSQM9nYGU/vgNBUiihE+z7tR143zyJT2Lya9m
pJWlbaGLMyIVm0UmGJnNFom+vcuElrlEo6m9Gx5sJCi8bjbPfeL4OIhmQW1KNFd4
3duqOAYDQUzlvrdSOIzsuuWqAV8xvmgFIRJcLREE4QVj9TyDwayXDUdu+TGkI7Ib
yA0XIvXulNrs3VZ4pfhv2dzG/JuJI2CjrTni+7i+Zjf71LWH
=jWru
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Package flask-compress has been removed from mentors.--- End Message ---

Bug#839065: RFS: pyzo/4.3-1

[Ghislain Vaillant]

On 28/09/16 14:58, Gianfranco Costamagna wrote:

control: owner -1 !
control: tags -1 moreinfo



I am looking for a sponsor for my package "pyzo"



ERR:

--- pyzo-4.2.1/pyzo/util/qt/__init__.py 1970-01-01 01:00:00.0 +0100
+++ pyzo-4.3/pyzo/util/qt/__init__.py   2016-09-28 10:21:34.0 +0200
@@ -0,0 +1,134 @@
+# -*- coding: utf-8 -*-
+#
+# Copyright © 2009- The Spyder Development Team
+# Copyright © 2014-2015 Colin Duquesnoy
+#
+# Licensed under the terms of the MIT License
+# (see LICENSE.txt for details)
+


--- pyzo-4.2.1/pyzo/util/qt/QtCore.py   1970-01-01 01:00:00.0 +0100
+++ pyzo-4.3/pyzo/util/qt/QtCore.py 2016-09-28 10:21:34.0 +0200
@@ -0,0 +1,49 @@
+# -*- coding: utf-8 -*-
+#
+# Copyright © 2014-2015 Colin Duquesnoy
+# Copyright © 2009- The Spyder Development Team
+#
+# Licensed under the terms of the MIT License
+# (see LICENSE.txt for details)


and so on

G.


Argh, I though Almar did not embed QtPy in the codebase. My bad.

I pushed a new version on mentors with the updated d/copyright.

Ghis

Bug#838679: [Debian-science-sagemath] Fwd: Bug#838679: RFS: cysignals/1.1.1+ds-1 [ITP] -- interrupt and signal handling for Cython

[Ximin Luo]

Hey, nice work. I'm taking a look now.

X

Jerome BENOIT:
> 
> 
> 
>  Forwarded Message 
> Subject: Bug#838679: RFS: cysignals/1.1.1+ds-1 [ITP] -- interrupt and signal 
> handling for Cython
> Resent-Date: Fri, 23 Sep 2016 14:54:01 +
> Resent-From: Jerome Benoit 
> Resent-To: debian-bugs-d...@lists.debian.org
> Resent-CC: debian-pyt...@lists.debian.org, Debian Mentors 
> 
> Date: Fri, 23 Sep 2016 15:50:13 +0100
> From: Jerome Benoit 
> Reply-To: Jerome Benoit , 838...@bugs.debian.org
> To: Debian Bug Tracking System 
> 
> Package: sponsorship-requests
> Severity: wishlist
> 
> Dear Sponsor,
> 
>   I am looking for sponsorship for the Debian package cysignals [0].
>   This package brings cysignals to Debian on behalf of the Debian
>   Python Modules Team. This is my very first Debian Python Module
>   package, so it might certainly be subject to some gross mistakes.
>   Its Alioth Git repository [1] has an experimental[-sage] branch
>   beside the master branch: the master branch is meant for the unstable
>   distribution, that is, to be exposed to a large audience; the
>   experimental[-sage] branch is meant to the Debian Sage[Math] Team [2].
>   More information can be found in d/README.source and d/README.Debian
>   as expected.
> 
> Thanks in advance,
> Jerome
> 
> [0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834232
> [1] https://anonscm.debian.org/git/python-modules/packages/cysignals.git
> [2] https://wiki.debian.org/DebianScience/Sage
> 
> -- System Information:
> Debian Release: Jessie*
>   APT prefers stable
>   APT policy: (990, 'stable'), (500, 'stable-updates')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 3.16.7-ckt20-0001-mbp62 (SMP w/4 CPU cores)
> Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: sysvinit (via /sbin/init)
> 
> 
> ___
> Debian-science-sagemath mailing list
> debian-science-sagem...@lists.alioth.debian.org
> https://lists.alioth.debian.org/mailman/listinfo/debian-science-sagemath
> 

-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git

-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git

Re: it would be a felony to miss it

[Sheila Varner]

On May 31, 2016 2:14 PM, "WalmartNotice" <
walpro...@mpls-executed.focusomes.com> wrote:
>>
>> Gratrs___sheliavarner47: Your__$ I000__Walmart GiftCard is Ready
>>>
>>> Get Your Card Here

Bug#838939: RFS: devtodo/0.1.20-6.1 [NMU]

[Gianfranco Costamagna]

control: owner -1 !
control: tags -1 moreinfo

Hi Fernando



>I am looking for a sponsor for my package "devtodo"


I would expect some changes more if you want


(note: they are usually out of an NMU scope, but with a maintainer mostly MIA, 
and a package
RC buggy since 3 years, I think some work might be nice).

e.g.

1) you bumped std-version, please mention in changelog.
2) you might want to convert VCS fields in https mode and push changes on 
collab-maint
Vcs-Git: https://git.debian.org/git/collab-maint/devtodo.git
Vcs-Browser: https://git.debian.org/cgit/collab-maint/devtodo.git

3) you might consider a Team upload (collab-maint).
It is not written in policy, but some people thinks collab-maint is a team, and 
then you can team
upload if you are part of it. (really border-line thinking)

4) debhelper >=9 or 10 and compat 9 or 10


5) modernize rules file (a.k.a. drop mostly everything):q

6) d/clean should be useless now

7) check if d/dirs and so on are still useful

other stuff is good
(I suggest you to run meld on build log files and debdiff on built deb files to 
see if changes are good or not
other than by testing the package :p )

Of course if you don't want, or you are out of time, I can sponsor it as-is, 
maybe with a revert of the
std-version bump (or a mention in changelog, even if policy forbids changes of 
it for NMUs)

G.

Re: Bug#838941: RFS: duperemove/0.11~beta3-3 ITP

[Peter Zahradnik]

On 2016-09-28 14:07, Adam Borowski wrote:

On Wed, Sep 28, 2016 at 11:24:20AM +0200, Dariusz Dwornikowski wrote:

On 26 September 2016 at 23:12,   wrote:
>  * Package name: duperemove
>Version : 0.11~beta3-3

"When given the -d option, duperemove will submit those extents for
deduplication using the btrfs-extent-same ioctl."


It's a vital piece of information, as without this option duperemove 
does
nothing but waste CPU and I/O.  An user would be able to use it 
intuitively

otherwise.

I have no idea why dry run is the default (probably from early debug
times?), but compared to most similar programs, the output is pretty
useless for purposes other than deduplicating, as duperemove does some
heurestics and thus its results are incomplete.

Thus, this option is needed to get started.  On the other hand, perhaps 
it
could be better to make a patch to switch the logic and have a 
--dry-run

option instead?


Thank you both for reviews, much appreciated.

@Adam
Make sense, I'll try to create patch for --dry-run and push it upstream

@Dariusz
I've removed -d from d/control for now and fixed d/changelog
Pristine-tar branch has been pushed to github
Upstream author released 0.11-beta4 so I could drop the patch with wrong 
utf8

coding altogether

new version has been uploaded to mentors
https://mentors.debian.net/debian/pool/main/d/duperemove/duperemove_0.11~beta4-1.dsc

thanks
Peter

Bug#838801: RFS: zxcvbn-c/0.20150103-1 [ITP]

[Gianfranco Costamagna]

control: owner -1 !
control: tags -1 moreinfo

Hi Sean,


>libzxcvbn-dev - password strength estimation library - development files

>libzxcvbn0 - password strength estimation library



I'm a little bit worried about the makefile :(

CFLAGS ?= -O2 -Wall -Wextra -Wdeclaration-after-statement
CPPFLAGS ?= -O2 -Wall -Wextra


this is a no-op I guess, maybe a "+=" might be better
gcc $(CFLAGS) $(LDFLAGS) -fPIC -shared -Wl,-soname,$(SONAME) -o $@ $^ -lm

this is wrong in many places, e.g.:

"gcc" might be a $(CC)
with 

$(CC) ?= gcc
as example (I don't see a good reason for forcing a gcc when people might want
to try to build it with clang as example)

LDFLAGS should be at the bottom of the ine, just before -lm, to avoid stripping
with wl-asneeded flag (and build failures)


blhc:

CXXFLAGS missing (-g -O2 -fPIE -fstack-protector-strong -Wformat 
-Werror=format-security): g++ -std=c++11 -Wdate-time -D_FORTIFY_SOURCE=2 -I. -o 
dictgen dict-generate.cpp
LDFLAGS missing (-fPIE -pie -Wl,-z,relro -Wl,-z,now): g++ -std=c++11 
-Wdate-time -D_FORTIFY_SOURCE=2 -I. -o dictgen dict-generate.cpp
CPPFLAGS missing (-D_FORTIFY_SOURCE=2): gcc -g -O2 
-fdebug-prefix-map=/<>=. -fPIE -fstack-protector-strong -Wformat 
-Werror=format-security -I. -DUSE_DICT_FILE -c -o zxcvbn-file.o zxcvbn.c

deb files:
-rw-r--r-- root/root568880 2016-09-25 01:14 
./usr/lib/x86_64-linux-gnu/libzxcvbn.a

static library? ok if you think it is useful


other stuff is good :)

thanks!

G.

Bug#839065: RFS: pyzo/4.3-1

[Gianfranco Costamagna]

control: owner -1 !
control: tags -1 moreinfo


>I am looking for a sponsor for my package "pyzo"


ERR:

--- pyzo-4.2.1/pyzo/util/qt/__init__.py 1970-01-01 01:00:00.0 +0100
+++ pyzo-4.3/pyzo/util/qt/__init__.py   2016-09-28 10:21:34.0 +0200
@@ -0,0 +1,134 @@
+# -*- coding: utf-8 -*-
+#
+# Copyright © 2009- The Spyder Development Team
+# Copyright © 2014-2015 Colin Duquesnoy
+#
+# Licensed under the terms of the MIT License
+# (see LICENSE.txt for details)
+


--- pyzo-4.2.1/pyzo/util/qt/QtCore.py   1970-01-01 01:00:00.0 +0100
+++ pyzo-4.3/pyzo/util/qt/QtCore.py 2016-09-28 10:21:34.0 +0200
@@ -0,0 +1,49 @@
+# -*- coding: utf-8 -*-
+#
+# Copyright © 2014-2015 Colin Duquesnoy
+# Copyright © 2009- The Spyder Development Team
+#
+# Licensed under the terms of the MIT License
+# (see LICENSE.txt for details)


and so on

G.

Re: Bug#838941: RFS: duperemove/0.11~beta3-3 ITP

[Adam Borowski]

On Wed, Sep 28, 2016 at 11:24:20AM +0200, Dariusz Dwornikowski wrote:
> On 26 September 2016 at 23:12,   wrote:
> >  * Package name: duperemove
> >Version : 0.11~beta3-3
> 
> "When given the -d option, duperemove will submit those extents for
> deduplication using the btrfs-extent-same ioctl."

It's a vital piece of information, as without this option duperemove does
nothing but waste CPU and I/O.  An user would be able to use it intuitively
otherwise.

I have no idea why dry run is the default (probably from early debug
times?), but compared to most similar programs, the output is pretty
useless for purposes other than deduplicating, as duperemove does some
heurestics and thus its results are incomplete.

Thus, this option is needed to get started.  On the other hand, perhaps it
could be better to make a patch to switch the logic and have a --dry-run
option instead?

-- 
A MAP07 (Dead Simple) raspberry tincture recipe: 0.5l 95% alcohol, 1kg
raspberries, 0.4kg sugar; put into a big jar for 1 month.  Filter out and
throw away the fruits (can dump them into a cake, etc), let the drink age
at least 3-6 months.

Bug#839065: RFS: pyzo/4.3-1

[Ghislain Vaillant]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "pyzo"

* Package name: pyzo
  Version : 4.3-1
* License : BSD
  Section : science

It builds those binary packages:

   iep   - transitional dummy package for IEP
   pyzo  - interactive editor for scientific Python
   pyzo-doc   - documentation for Pyzo

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


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

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

   dget -x 
https://mentors.debian.net/debian/pool/main/p/pyzo/pyzo_4.3-1.dsc


Successful builds on debomatic:


http://debomatic-amd64.debian.net/distribution#unstable/pyzo/4.3-1/buildlog

Changes since the last upload:

   * New upstream release.
   * Change install dependencies for pyzo.
 - Remove dependency on pyzolib, now merged into pyzo.
 - Add transitive dependency on Qt via QtPy.
   * Sort install dependencies of iep.

Regards,
Ghislain Vaillant

Bug#838566: marked as done (RFS: mimerender/0.6.0-1 [ITP])

[Debian Bug Tracking System]

Your message dated Wed, 28 Sep 2016 11:55:30 +
with message-id <20160928115528.zrpxynnqdx5w6...@chase.mapreri.org>
and subject line Re: Bug#838566: RFS: mimerender/0.6.0-1 [ITP]
has caused the Debian Bug report #838566,
regarding RFS: mimerender/0.6.0-1 [ITP]
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.)


-- 
838566: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838566
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: wishlist

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear mentors,

I am looking for a sponsor for my package "mimerender"

 * Package name: mimerender
   Version : 0.6.0-1
   Upstream Author : Martin Blech 
 * URL : https://github.com/martinblech/mimerender
 * License : MIT
   Section : python

It builds those binary packages:

  python-mimerender - RESTful HTTP Content Negotiation for web frameworks 
(Python 2)
  python3-mimerender - RESTful HTTP Content Negotiation for web frameworks 
(Python 3)

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/m/mimerender/mimerender_0.6.0-1.dsc

The package is a dependency of the soon to be added flask-restless package.

  Regards,
   Dominik George

-BEGIN PGP SIGNATURE-

iQJhBAEBCABLBQJX49MdMRpodHRwczovL3d3dy5kb21pbmlrLWdlb3JnZS5kZS9n
cGctcG9saWN5LnR4dC5hc2MSHG5pa0BuYXR1cmFsbmV0LmRlAAoJELeaPBagxPKW
5VcP/2d2QeKrmW4BjHgi/f47zf6sPuyaCI/J+K5LkIEo1giM09XGyXGj+qmJQgE1
o+PtW+Mgmzb2y+4SP8Oil39Rzs3w7DQd/2V8xV/MvrbWnnymQh2aqmv4r5aW4GKS
N4TLMfKm0yPkEljg6e6tByG7RtFaIwwYD26j3qq6E8yn5FYVbQJZLQee222AeLVA
U6L1JJvk+dwDW52HvS8yHjKexj5RxE34fRpJ3NFS82bHzUCRTY/mtB3SEqOHWBqf
X23+LIjx0YcSM4/6Phe5ZZ1YhSPby5wtdHAvPBVLKo/SAvbrSzX02zeAzcrwm/vO
AqNjAlReydi6p2WOrkWGj9yCQbTf/xMe/0RPY9HL+SuAOXjh5Fkwixj3WI/BXAUs
mbGBPOfI9Kn9g88sVreVtnyaJmIJBGt++VjRCHlp3AOjkR+0rUTJFjrjTyNJEtIM
CVrayIKxpOe8ozAWZRZPP7e/KoQDux3FPK643lQEf+f/n3tHTLmVoumTkspc5cWo
nTCSdpBhL+SiOvI7o7IwyKFcr9CZMwSVY81cVpbhOipcQLVLbYrIvyJsoXDJHMOd
Cu1Tj/PybMfcSeMxs+4cj3JWRmh1oDxpKjVSGZjumc0qlBr+sftGHfSQBSfJLJck
/zLyIJpmxCjdMiUtElQsROBRusKD5ypnpIbWH6vZ780/4hqx
=fkb9
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
On Wed, Sep 28, 2016 at 01:43:46PM +0200, Dominik George wrote:
> I verified the package still builds and is lintian clean.

Great, uploaded!


-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
--- End Message ---

Bug#838566: RFS: mimerender/0.6.0-1 [ITP]

[Dominik George]

Hi Mattia,

thanks for looking at the package!

> so, this package is in DPMT, hence I'm looking only at the git repo.

I removed it from mentors and, as you are not far from sponsoring it ;),
did not re-upload the fixed version.

In case the sponsorship will not work out, I will re-upload it to
mentors for others.

> 
> blocking things:
>  * this package doesn't seem to be using git-dpm, as mandate by DPMT.

Sorry, I mistook a thread on debian-python as discouraging git-dpm.

However, I fixed that now, and made the repo work with git-dpm.

> 
> nice to have:
>  * properly sorted build-depends.  `wrap-and-sort -ast` might help here
>  * the last debhelper compat level is 10
>  * in Debian the standard MIT license is called Expat, see DEP-5.

Done (all three).

I verified the package still builds and is lintian clean.

Cheers,
Nik


signature.asc
Description: PGP signature

Re: useless lintian error?

[Gianfranco Costamagna]

Hi,

>It doesn't look closed to me.


Indeed, the bug was pending and then excluded from the list in BTS
https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=doona=no=pending-fixed=fixed=done=critical=grave=serious=no

this is why I didn't see it.

thanks!

G.

Re: useless lintian error?

[James Cowgill]

On 28/09/16 10:55, Gianfranco Costamagna wrote:
> Hi mentors,
> I did a doona upload, with "closes #foo" in changelog, getting
> a lintian error:
> 
> E possible-missing-colon-in-closes
> closes #838630
> 
> since the bug is closed

It doesn't look closed to me.

> because the system closes bugs even without the colon, isn't this time to drop
> that error?

The uses 'Closes:' with a colon to close bugs is required by Policy
(section 4.4).

James



signature.asc
Description: OpenPGP digital signature

useless lintian error?

[Gianfranco Costamagna]

Hi mentors,
I did a doona upload, with "closes #foo" in changelog, getting
a lintian error:


E possible-missing-colon-in-closes
closes #838630


since the bug is closed, because the system closes bugs even without the colon,
isn't this time to drop that error?

I'm not sure why something that works might need fixing...
thanks,

G.

Bug#838941: RFS: duperemove/0.11~beta3-3 ITP

[Dariusz Dwornikowski]

On 26 September 2016 at 23:12,   wrote:
> Package: sponsorship-requests
> Severity: wishlist
>
>   Dear mentors,
>
>   I am looking for a sponsor for my package "duperemove"
>
>  * Package name: duperemove
>Version : 0.11~beta3-3

Hi,

First of all, thank you for your contribution. I am DD but can't
sponsor you because my key expired.

Some comments:
- this is ITP bug so in d/changelog you should have one entry. with
one version, with Initial release and (Closes: #).
- in your patch there seems to be some UTF problem in the From:
- can you push pristine tar branches to the git ? I can't build it.
In d/control, the passage is not needed, options, arguments have place
in a man page.
"When given the -d option, duperemove will submit those extents for
deduplication using the btrfs-extent-same ioctl."