date:20160325

Your message dated Sat, 26 Mar 2016 16:16:09 +1100
with message-id <4764623.j45CToVYrF@deblab>
and subject line Re: [pkg-go] Bug#817224: RFS: 
golang-github-square-go-jose/0.0~git20160304.0.7465d2b -- Javascript Object 
Signing and Encryption (JOSE) for Go
has caused the Debian Bug report #817224,
regarding RFS: golang-github-square-go-jose/0.0~git20160304.0.7465d2b [ITP] -- 
Javascript Object Signing and Encryption (JOSE) for Go
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.)


-- 
817224: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817224
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 the package "golang-github-square-go-jose":

  git clone 
https://anonscm.debian.org/git/pkg-go/packages/golang-github-square-go-jose.git

  cd golang-github-square-go-jose && pristine-tar checkout 
../golang-github-square-go-jose_0.0~git20160304.0.7465d2b.orig.tar.gz

For verification, these are the current branch heads:

  git show-ref --heads
  a10aeacc0ae2079a5377301367ca0b1a343bf62d refs/heads/master
  ec040e4084e7cef4905b1e5f34236afc5e3eceb4 refs/heads/pristine-tar
  d2c75c29e10dca028f1193d1c6a94679e23cfb5d refs/heads/upstream

It builds these binary packages:

  golang-github-square-go-jose-dev -- Javascript Object Signing and Encryption 
(JOSE) for Go

This package is a prerequisite for building acmetool [1], an automatic
certificate acquisition tool for Let's Encrypt [2].

[1] https://bugs.debian.org/817091
[2] https://letsencrypt.org/about/

More information about golang-github-square-go-jose can be obtained from

https://github.com/square/go-jose

If you decide to sponsor this package, please change the distribution
from UNRELEASED to unstable before upload. I will import the uploaded
source package into the git repository and push a tag afterwards.

Regards,
Peter
--- End Message ---
--- Begin Message ---
On Wednesday, 9 March 2016 1:02:42 AM AEDT Peter Colberg wrote:
> I am looking for a sponsor for the package "golang-github-square-go-jose":

Uploaded, thank you. :)

-- 
All the best,
 Dmitry Smirnov.

---

The great enemy of the truth is very often not the lie -- deliberate,
contrived and dishonest, but the myth, persistent, persuasive, and
unrealistic. Belief in myths allows the comfort of opinion without the
discomfort of thought.
-- John F Kennedy


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

Bug#817223: marked as done (RFS: golang-github-satori-go.uuid/0.0~git20160218.0.e673fdd [ITP] -- Go package for creating and parsing UUID)

Your message dated Sat, 26 Mar 2016 16:05:33 +1100
with message-id <2268829.edUhMiPij4@deblab>
and subject line Re: [pkg-go] Bug#817223: RFS: 
golang-github-satori-go.uuid/0.0~git20160218.0.e673fdd -- Go package for 
creating and parsing UUID
has caused the Debian Bug report #817223,
regarding RFS: golang-github-satori-go.uuid/0.0~git20160218.0.e673fdd [ITP] -- 
Go package for creating and parsing UUID
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.)


-- 
817223: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817223
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 the package "golang-github-satori-go.uuid":

  git clone 
https://anonscm.debian.org/git/pkg-go/packages/golang-github-satori-go.uuid.git

  cd golang-github-satori-go.uuid && pristine-tar checkout 
../golang-github-satori-go.uuid_0.0~git20160218.0.e673fdd.orig.tar.gz

For verification, these are the current branch heads:

  git show-ref --heads
  8e47fcd79e7d5da8f8f881ef032c2c374b761aa4 refs/heads/master
  ae97aad9ba1e129f8c1e32b4465d7870f333d197 refs/heads/pristine-tar
  0363f19ea24b1699b4470caa10c0a39b02f139d7 refs/heads/upstream

It builds these binary packages:

  golang-github-satori-go.uuid-dev -- Go package for creating and parsing UUID

This package is a prerequisite for building acmetool [1], an automatic
certificate acquisition tool for Let's Encrypt [2].

[1] https://bugs.debian.org/817091
[2] https://letsencrypt.org/about/

More information about golang-github-satori-go.uuid can be obtained from

https://github.com/satori/go.uuid

If you decide to sponsor this package, please change the distribution
from UNRELEASED to unstable before upload. I will import the uploaded
source package into the git repository and push a tag afterwards.

Regards,
Peter
--- End Message ---
--- Begin Message ---
On Wednesday, 9 March 2016 12:58:46 AM AEDT Peter Colberg wrote:
> I am looking for a sponsor for the package "golang-github-satori-go.uuid":

Uploaded, thank you. :)

-- 
All the best,
 Dmitry Smirnov.

---

We occasionally stumble over the truth but most of us pick ourselves up
and hurry off as if nothing had happened.
-- Winston Churchill


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

Bug#819289: RFS: pythonpy/0.4.10-1 [ITP]

Hi,

I've forgot to mention in the bug report that there's a Git
repository[1] for the package (as stated in debian/control). It would
be awesome if my sponsor is also able to help me to move it to
"collab-maint", which I already have write permissions.

Regards,
Tiago.

[1]: https://github.com/myhro/deb-pythonpy

-- 
Tiago "Myhro" Ilieve
Blog: https://blog.myhro.info/
GitHub: https://github.com/myhro
LinkedIn: https://br.linkedin.com/in/myhro
Montes Claros - MG, Brasil

Bug#817226: [pkg-go] Bug#817226: RFS: golang-gopkg-hlandau-svcutils.v1/1.0.7 -- utilities for writing services in Go

2016-03-25 Thread Dmitry Smirnov

On Wednesday, 9 March 2016 1:10:27 AM AEDT Peter Colberg wrote:
> I am looking for a sponsor for the package
> "golang-gopkg-hlandau-svcutils.v1":

Very good work, Peter. :)

I'd like upstream to clarify licensing before we upload:

https://github.com/hlandau/svcutils/issues/1

-- 
All the best,
 Dmitry Smirnov.

---

It is time that we admitted that faith is nothing more than the license
religious people give one another to keep believing when reasons fail.
-- Sam Harris


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

Bug#819289: RFS: pythonpy/0.4.10-1 [ITP]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

* Package name: pythonpy
  Version : 0.4.10-1
  Upstream Author : Russell Stewart 
* URL : https://github.com/Russell91/pythonpy
* License : MIT
  Section : utils

It builds those binary packages:

  pythonpy   - 'python -c', with tab completion and shorthand

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

http://mentors.debian.net/package/pythonpy

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

  dget -x 
http://mentors.debian.net/debian/pool/main/p/pythonpy/pythonpy_0.4.10-1.dsc

I would like to thank Ben Finney and Gianfranco Costamagna who helped
me with the initial packaging work. :-)

Regards,
Tiago.

-- 
Tiago "Myhro" Ilieve
Blog: https://blog.myhro.info/
GitHub: https://github.com/myhro
LinkedIn: https://br.linkedin.com/in/myhro
Montes Claros - MG, Brasil

Bug#817865: [Letsencrypt-devel] Bug#817865: RFS: acmetool/0.0.49 [ITP] -- automatic certificate acquisition tool for Let's Encrypt

2016-03-25 Thread Harlan Lieberman-Berg

Peter Colberg  writes:
> Did you find the time to take a brief look at the acmetool package to
> decide whether the Debian Let’s Encrypt team will provide sponsorship?

Hi Peter!

This definitely seems like something that could fit very well under the
Let's Encrypt team's umbrella.  I'd be happy to review it for
sponsorship.

At the moment, though, it seems there are several pending dependencies
that are required first, and I'm less certain that those would be a good
fit for the team -- I think pkg-go is probably a way better home for
them.  (I only know a little bit of go myself!)

When the blocks are resolved, ping me and I'll definitely take a look.

Thanks for your contributions!  Looking forward to working together.

-- 
Harlan Lieberman-Berg
~hlieberman

Bug#817827: marked as done (RFS: golang-gopkg-tylerb-graceful.v1/1.2.4 [ITP] -- Go package for gracefully shutting down HTTP server)

Your message dated Sat, 26 Mar 2016 14:34:20 +1100
with message-id <7913997.iCpsFNn5R2@deblab>
and subject line Re: [pkg-go] Bug#817827: RFS: 
golang-gopkg-tylerb-graceful.v1/1.2.4 [ITP] -- Go package for gracefully 
shutting down HTTP server
has caused the Debian Bug report #817827,
regarding RFS: golang-gopkg-tylerb-graceful.v1/1.2.4 [ITP] -- Go package for 
gracefully shutting down HTTP server
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.)

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

Dear mentors,

I am looking for a sponsor for the package "golang-gopkg-tylerb-graceful.v1":

  git clone 
https://anonscm.debian.org/git/pkg-go/packages/golang-gopkg-tylerb-graceful.v1.git

  cd golang-gopkg-tylerb-graceful.v1 && pristine-tar checkout 
../golang-gopkg-tylerb-graceful.v1_1.2.4.orig.tar.gz

For verification, these are the current branch heads:

  git show-ref --heads
  d703c4fbdfb3b882a36a857df5876aacf67b7669 refs/heads/master
  ef9d98ea7c26c08e9c4a089dc63b777b14c4cd61 refs/heads/pristine-tar
  11415e544504d350056e2e67955dcf1bd2bb5e18 refs/heads/upstream

It builds these binary packages:

  golang-gopkg-tylerb-graceful.v1-dev -- Go package for gracefully shutting 
down HTTP server

This package is a prerequisite for building acmetool [1], an
automatic certificate acquisition tool for Let's Encrypt [2].

[1] https://bugs.debian.org/817091
[2] https://letsencrypt.org/about/

More information about golang-gopkg-tylerb-graceful.v1 can be obtained from

https://github.com/tylerb/graceful

If you decide to sponsor this package, please change the distribution
from UNRELEASED to unstable before upload. I will import the uploaded
source package into the git repository and push a tag afterwards.

Regards,
Peter
--- End Message ---
--- Begin Message ---
On Thursday, 10 March 2016 12:46:14 PM AEDT Peter Colberg wrote:
> I am looking for a sponsor for the package
> "golang-gopkg-tylerb-graceful.v1":

Uploaded, thank you.

-- 
Regards,
 Dmitry Smirnov.

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

Bug#818839: marked as done (RFS: mathic/1.0~git20160320-1)

Your message dated Fri, 25 Mar 2016 22:19:26 -0400
with message-id <56f5f1ae.5040...@piedmont.edu>
and subject line Fwd: mathic_1.0~git20160320-1_amd64.changes ACCEPTED into 
unstable
has caused the Debian Bug report #818839,
regarding RFS: mathic/1.0~git20160320-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.)


-- 
818839: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818839
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 "mathic"

 * Package name: mathic
   Version : 1.0~git20160320-1
   Upstream Author : Bjarke Hammersholt Roune and Michael Stillman
 * URL : https://github.com/Macaulay2/mathic
 * License : LGPL-2+
   Section : libs

  It builds those binary packages:

libmathic-dev - C++ library for Groebner basis computation (developer tools)
 libmathic0v5 - C++ library for Groebner basis computation (runtime library)

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

  http://mentors.debian.net/package/mathic

  or

  https://anonscm.debian.org/git/debian-science/packages/mathic.git

  Changes since the last upload:

mathic (1.0~git20160320-1) unstable; urgency=medium

  * New upstream release.
- Now maintained by Macaulay2 developers.
  * debian/control
- Bump versioned dependency on debhelper to >= 9.20160114.  Needed for
  --dbgsym-migration option to dh_strip.
- Bump Standards-Version to 3.9.7.
- Update Homepage.
- Use https protocol for Vcs-Browser.
- Drop libmathic-dgb in favor of automatically generated
  libmathic0v5-dbgsym package.
  * debian/copyright
- Update Source.
- Change license to LGPL-2+. (This has actually always been the license;
  I must have misread it when initially preparing the package.)
  * debian/libmathic0v5.symbols
- Restore symbols file.
  * debian/patches
- Remove previous patches; patches applied upstream.
  * debian/patches/fix_typo.patch
- New patch. Fixes spelling-error-in-binary Lintian warning.
  * debian/rules
- Enable all hardening flags.
- Update definition of GTEST_PATH for dh_auto_configure.
- Add --enable-shared to dh_auto_configure.
- Modify override_dh_strip target. Instead of building the libmathic-dbg
  package, we use the --dbgsym-migration option to ensure proper migration
  to the new automatically generated package.
- Update get-orig-source target with new location.
  * debian/watch
- Update with new upstream webpage. Note that this is merely a comment;
  upstream does not tag their releases and uscan is currently not
  functional.

 -- Doug Torrance   Sun, 20 Mar 2016 16:54:38 -0400
--- End Message ---
--- Begin Message ---




 Forwarded Message 
Subject:mathic_1.0~git20160320-1_amd64.changes ACCEPTED into unstable
Resent-From:dtorra...@piedmont.edu
Date:   Fri, 25 Mar 2016 11:23:25 +
From:   Debian FTP Masters 
To: 	Debian Science Maintainers 
, Doug Torrance 
, ti...@debian.org




Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 20 Mar 2016 16:54:38 -0400
Source: mathic
Binary: libmathic-dev libmathic0v5
Architecture: source amd64
Version: 1.0~git20160320-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Doug Torrance 
Description:
 libmathic-dev - C++ library for Groebner basis computation (developer tools)
 libmathic0v5 - C++ library for Groebner basis computation (runtime library)
Changes:
 mathic (1.0~git20160320-1) unstable; urgency=medium
 .
   * New upstream release.
 - Now maintained by Macaulay2 developers.
   * debian/control
 - Bump versioned dependency on debhelper to >= 9.20160114.  Needed for
   --dbgsym-migration option to dh_strip.
 - Bump Standards-Version to 3.9.7.
 - Update Homepage.
 - Use https protocol for Vcs-Browser.
 - Drop libmathic-dgb in favor of automatically generated
   libmathic0v5-dbgsym package.
   * debian/copyright
 - Update Source.
 - Change license to LGPL-2+. (This has actually always been the license;
   I must have misread it when initially preparing the package.)
   * debian/libmathic0v5.symbols
 - Restore symbols file.
   * debian/patches

Bug#819285: RFS: mathic/1.0~git20160320-2

2016-03-25 Thread Doug Torrance

Package: sponsorship-requests
Severity: normal

 Dear mentors,

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

 * Package name: mathic
   Version : 1.0~git20160320-1
   Upstream Author : Bjarke Hammersholt Roune and Michael Stillman
 * URL : https://github.com/Macaulay2/mathic
 * License : LGPL-2+
   Section : libs

  It builds those binary packages:

libmathic-dev - C++ library for Groebner basis computation (developer tools)
libmathic0v5 - C++ library for Groebner basis computation (runtime library)

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

  http://mentors.debian.net/package/mathic

  or

  https://anonscm.debian.org/git/debian-science/packages/mathic.git

  Changes since the last upload:

mathic (1.0~git20160320-2) unstable; urgency=medium

  * debian/libmathic0v5.symbols
- Add some arch-specific tags to fix FTBFS.
  * debian/patches/fix_typo.patch
- Switch Forwarded to Applied-Upstream.

 -- Doug Torrance   Fri, 25 Mar 2016 20:49:52 -0400

  Regards,
   Doug Torrance

Re: Packaging pythonpy

Gianfranco,

On 25 March 2016 at 19:07, Gianfranco Costamagna
 wrote:
> up to your sponsor :)

Tried one or two new approaches and it didn't worked. In the I've
created a patch[1] changing "#!/usr/bin/env python2" to
"#!/usr/bin/env python". This should work as long as Python 2 is the
default interpreter, something which may change in the next years, but
isn't a problem at least for Stretch.

I'm all in for another options if someone doesn't like this patch.

> swap Files: debian/*
> and Files: *
>
> first the more comprehensive and later the less.
> (lintian might be more specific)

This is awesome. I would never figure out by myself that it was so
simple to fix. :-)

> I did fix the python apps in blah section with section "utils", and uploaded 
> on debomatic again.
> Now that lintian warning is not there anymore.

Yup. I've did that as well[2].

> (I won't download the package, I think I already answered the points)

No problem. You answers were very helpful, as always.

I've uploaded a new version of the package to mentors.d.n[3]. There
are the following lintian messages now:

* "newer-standards-version": which can be ignored, as mentors.d.n
doesn't consider 3.9.7 as the current standard.
* "debian-watch-file-is-missing" and "no-upstream-changelog": which
will be fixed in the near future with upstream help regarding tagged
releases.
* "binary-without-manpage": which I'll be fixing, adding a manpage
before submitting an RFS.

Thank you very much, Gianfranco!

Regards,
Tiago.

[1]: https://github.com/myhro/deb-pythonpy/commit/5450656
[2]: https://github.com/myhro/deb-pythonpy/commit/0e2d987
[3]: http://mentors.debian.net/package/pythonpy

-- 
Tiago "Myhro" Ilieve
Blog: https://blog.myhro.info/
GitHub: https://github.com/myhro
LinkedIn: https://br.linkedin.com/in/myhro
Montes Claros - MG, Brasil

Re: gbp import-orig maybe ignores .gitattributes?

Hi,

I have *never* been able to fix such issues, sometimes a git reset --hard 
commitid and git pull worked, sometimes else
a .gitattributes file helped

or removing the files and manually untarring the new release.
Git for some reasons doesn't take changing newlines as differences (not sure)
(look for boinc.git on alioth and the .gitattributes file)
https://help.github.com/articles/dealing-with-line-endings/
http://stackoverflow.com/questions/2825428/why-should-i-use-core-autocrlf-true-in-git
http://stackoverflow.com/questions/170961/whats-the-best-crlf-carriage-return-line-feed-handling-strategy-with-git
http://stackoverflow.com/questions/3206843/how-line-ending-conversions-work-with-git-core-autocrlf-between-different-operat
http://stackoverflow.com/questions/9976986/force-lf-eol-in-git-repo-and-working-copy


hope this helps!

have a nice hacking,

G.




Il Venerdì 25 Marzo 2016 21:02, Peter Spiess-Knafl  ha 
scritto:
Hi!

I am currently having troubles packaging the new upstream version of
libjsoncpp.

https://github.com/open-source-parsers/jsoncpp

I downloaded the newest upstream version using uscan and used gbp
import-orig to import the downloaded tarball.

Now I recognize that there are some Visual Studio files in it which have
CRLF lineendings in the tarball but LF line endings in the checkout
working directory.

dpkg-source complains during package built that the working directory
does not comply with the downloaded tarball.

Upstream does provide a .gitattributes file which takes care of this
problem. However gbp import-orig somehow seems to ignore this.

Can someone give me a hint what I am doing wrong?


Thank you and greetings
Peter

Re: Packaging pythonpy

Hi,
>I really appreciate your effort in trying to package it yourself, but

>you didn't solved the main problem, which is the
>"python-script-but-no-python-dep".


indeed, control file line two.

it is an application, so choose some Section from there
https://qa.debian.org/developer.php?login=python-apps-team%40lists.alioth.debian.org

Section: python is for libraries (e.g. called python-foo or python3-foo)


>The "dh_auto_install" override is used to place it in>"/usr/share/pythonpy" 
>which is the proper place for Python
>*applications*[1]. Without it, it goes to the place where *libraries*
>should be located.


ok
>The "remove_entry_points_scripts.patch" avoids the creation of
>py{2,2.7} binaries that aren't needed. Without it and removing the
>override for "dh_fixperms", the package becomes useless. There's no
>way to call the "py" command, as its main script doesn't have
>execution permissions.


ok, but why some of them have the +x set?
http://debomatic-amd64.debian.net/distribution#unstable/pythonpy/0.4.4-1/contents

I wouls suggest patching the setup file to perform correctly instead of 
overriding stuff.

>Looks like it would be way easier to fix the entry point scripts to
>created a binary named "py", avoiding just the other ones. We can also
>ignore the override that changes the target folder, but doing this
>feels wrong, is like we are ignoring the best practices for packaging
>Python applications. That's why I'm wrecking my head with this issue,
>removing every file that would be useless, instead of following the
>easiest path.


up to your sponsor :)

>About the lintian output:



>* "unused-file-paragraph-in-dep5-copyright": this info doesn't appear
>even when I run lintian with the same arguments on my machine. This is
>strange, as I'm running "v2.5.42.1" from sid and debomatic-amd64.d.n
>is using "v2.5.42.1~bpo8+1", which should be the same version. Do you
>know how can I do this?


swap Files: debian/*
and Files: *

first the more comprehensive and later the less.
(lintian might be more specific)


>* "debian-watch-file-is-missing": this is right. I've asked[2]>upstream to tag 
>every release on GitHub, so we can fetch information
>about new versions from there.
>* "application-in-library-section": fixed[3].
>* "no-upstream-changelog": the upstream added a changelog file in the
>last version (0.4.9, which I have packaged this afternoon), but it
>doesn't comes with the tarball available in PyPI. This will be solved
>when the releases are tagged and we grab them from GitHub.
>* "package-installs-into-obsolete-dir": fixed using dh_bash-completion[4].
>
>I've uploaded the last (0.4.9-1) package version to mentors.d.n[5].


I did fix the python apps in blah section with section "utils", and uploaded on 
debomatic again.

Now that lintian warning is not there anymore.


(I won't download the package, I think I already answered the points)

cheers,

G.

Re: Packaging pythonpy

Hi Gianfranco,

On 25 March 2016 at 16:21, Gianfranco Costamagna
 wrote:
> http://debomatic-amd64.debian.net/distribution#unstable/pythonpy/0.4.4-1/lintian
> please dget it from there and start again :)
>
> I fixed a lot of issues, and many more are there now!

I really appreciate your effort in trying to package it yourself, but
you didn't solved the main problem, which is the
"python-script-but-no-python-dep".

The "dh_auto_install" override is used to place it in
"/usr/share/pythonpy" which is the proper place for Python
*applications*[1]. Without it, it goes to the place where *libraries*
should be located.

The "remove_entry_points_scripts.patch" avoids the creation of
py{2,2.7} binaries that aren't needed. Without it and removing the
override for "dh_fixperms", the package becomes useless. There's no
way to call the "py" command, as its main script doesn't have
execution permissions.

Looks like it would be way easier to fix the entry point scripts to
created a binary named "py", avoiding just the other ones. We can also
ignore the override that changes the target folder, but doing this
feels wrong, is like we are ignoring the best practices for packaging
Python applications. That's why I'm wrecking my head with this issue,
removing every file that would be useless, instead of following the
easiest path.

About the lintian output:

* "unused-file-paragraph-in-dep5-copyright": this info doesn't appear
even when I run lintian with the same arguments on my machine. This is
strange, as I'm running "v2.5.42.1" from sid and debomatic-amd64.d.n
is using "v2.5.42.1~bpo8+1", which should be the same version. Do you
know how can I do this?
* "debian-watch-file-is-missing": this is right. I've asked[2]
upstream to tag every release on GitHub, so we can fetch information
about new versions from there.
* "application-in-library-section": fixed[3].
* "no-upstream-changelog": the upstream added a changelog file in the
last version (0.4.9, which I have packaged this afternoon), but it
doesn't comes with the tarball available in PyPI. This will be solved
when the releases are tagged and we grab them from GitHub.
* "package-installs-into-obsolete-dir": fixed using dh_bash-completion[4].

I've uploaded the last (0.4.9-1) package version to mentors.d.n[5].

Thanks,
Tiago.

[1]: https://wiki.debian.org/Python/Packaging#Example_2:_Python_application
[2]: https://github.com/Russell91/pythonpy/issues/76
[3]: https://github.com/myhro/deb-pythonpy/commit/0e2d987
[4]: https://github.com/myhro/deb-pythonpy/commit/954e424
[5]: http://mentors.debian.net/package/pythonpy

-- 
Tiago "Myhro" Ilieve
Blog: https://blog.myhro.info/
GitHub: https://github.com/myhro
LinkedIn: https://br.linkedin.com/in/myhro
Montes Claros - MG, Brasil

gbp import-orig maybe ignores .gitattributes?

2016-03-25 Thread Peter Spiess-Knafl

Hi!

I am currently having troubles packaging the new upstream version of
libjsoncpp.

https://github.com/open-source-parsers/jsoncpp

I downloaded the newest upstream version using uscan and used gbp
import-orig to import the downloaded tarball.

Now I recognize that there are some Visual Studio files in it which have
CRLF lineendings in the tarball but LF line endings in the checkout
working directory.

dpkg-source complains during package built that the working directory
does not comply with the downloaded tarball.

Upstream does provide a .gitattributes file which takes care of this
problem. However gbp import-orig somehow seems to ignore this.

Can someone give me a hint what I am doing wrong?


Thank you and greetings
Peter

Bug#818982: marked as done (RFS: nvme-cli/0.4-1 -- userspace tooling to control NVMe drives)

Your message dated Fri, 25 Mar 2016 19:53:23 + (UTC)
with message-id <110154726.587745.1458935603439.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#818982: RFS: nvme-cli/0.4-1 -- userspace tooling to 
control NVMe drives
has caused the Debian Bug report #818982,
regarding RFS: nvme-cli/0.4-1 -- userspace tooling to control NVMe drives
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.)


-- 
818982: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818982
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 a new nvme package release (0.5.1):

  dget -x 
http://mentors.debian.net/debian/pool/main/n/nvme-cli/nvme-cli_0.5-1.dsc

It builds these binary packages:

  nvme-cli - userspace tooling to control NVMe drives

More information about nvme can be obtained from
https://github.com/linux-nvme/nvme-cli

Changes since the last upload:

nvme-cli (0.5-1) unstable; urgency=medium

  * New upstream release
  * Fix version number (Closes: #816438)

 -- Breno Leitao   Wed, 02 Mar 2016 15:30:12 -0500
--- End Message ---
--- Begin Message ---
Hi Bruno.



I sponsored and took the liberty to tweak the changelog.
You should be more verbose next time.

* New upstream release
  - Fix version number (Closes: #816438)
* Bump Standard-Version to 3.9.7, no changes required.
* drop 0004-Fix-English-typos-only.patch: upstream.

the fix for 816438 is part of the new upstream release, so
it has to be a subsection of it.

cheers,
and thanks for your contribution to Debian!

Gianfranco--- End Message ---

Bug#817865: [Letsencrypt-devel] Bug#817865: RFS: acmetool/0.0.49 [ITP] -- automatic certificate acquisition tool for Let's Encrypt

2016-03-25 Thread Peter Colberg

Hi Harlan,

Did you find the time to take a brief look at the acmetool package to
decide whether the Debian Let’s Encrypt team will provide sponsorship?

Regards,
Peter

Bug#819166: marked as done (RFS: libsass-python/0.11.0-1 (new upstream release ; urgent : fix for FTBFS))

Your message dated Fri, 25 Mar 2016 20:37:23 +0100
with message-id <56f59373.8080...@debian.org>
and subject line sponsored.
has caused the Debian Bug report #819166,
regarding RFS: libsass-python/0.11.0-1 (new upstream release ; *urgent* : fix
for FTBFS)
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.)

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

Dear mentors, Gianfranco,

I am looking for a sponsor for an upgrade of the package "libsass-python".
This an upgrade of the previous version 0.9.3-1 which is marked for autoremoval
on 29 March because of FTBFS on some platforms. I worked with upstream to
provide a patch to libsass (which libsass-python depends on) and it has been
propagated in the lastest libsass 3.3.4-1 that got released in sid 2days ago.
Here is libsass-python/0.11.0-1 changelog :

libsass-python (0.11.0-1) unstable; urgency=medium

* debian/rules : taking default python version into account in shebang and
adapting upstream check of libsass version.
* debian/control : updated python3-libsass dependency. Closes: #811406
* Renaming sassc to pysassc while waiting for upstream. Closes: #817139
* Updating to new release. Closes: #814428

-- Frederic Bonnard Thu, 24 Mar 2016 10:26:12
+0100

Package infos :

Package name: libsass-python
Version : 0.11.0-1
Upstream Author : Hong Minhee
URL : http://hongminhee.org/libsass-python
License : MIT
Section : python

It builds those binary packages:

pysassc- SASS for Python: command line utility for libsass
python-libsass - SASS for Python: a straightforward binding of libsass for
Python
python3-libsass - SASS for Python 3: a straightforward binding of libsass for
Python3

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

http://mentors.debian.net/package/libsass-python

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

dget -x
http://mentors.debian.net/debian/pool/main/libs/libsass-python/libsass-python_0.11.0-1.dsc

More information about libsass-python can be obtained from
http://hongminhee.org/libsass-python.

Regards,
Frederic Bonnard
--- End Message ---
--- Begin Message ---
sponsored, even if it didn't fail locally and on DebOMatic, but everywhere else
on buildds.

cheers,

signature.asc
Description: OpenPGP digital signature
--- End Message ---

Re: Packaging pythonpy

http://debomatic-amd64.debian.net/distribution#unstable/pythonpy/0.4.4-1/lintian
please dget it from there and start again :)

I fixed a lot of issues, and many more are there now!

cheers,

G.

Il Venerdì 25 Marzo 2016 18:48, Tiago Ilieve  ha scritto:
Hi Gianfranco,

On 25 March 2016 at 06:25, Gianfranco Costamagna
 wrote:
>
> adding python to the dependencies?
> do you have python to build dependencies, dh-python and python:Depends on the
> binary package?

This is what is strange. I've made the following changes:

-
diff --git a/debian/control b/debian/control
index f0c1b3f..5205298 100644
--- a/debian/control
+++ b/debian/control
@@ -3,6 +3,7 @@ Section: python
Priority: optional
Maintainer: Tiago Ilieve 
Build-Depends: debhelper (>= 9),
+   dh-python,
python (>= 2.7.3),
python-setuptools (>= 0.6.24)
Standards-Version: 3.9.7
@@ -13,7 +14,9 @@ Vcs-Browser: https://github.com/myhro/deb-pythonpy

Package: pythonpy
Architecture: all
-Depends: ${misc:Depends}, ${python:Depends}
+Depends: python (>= 2.7.3),
+ ${misc:Depends},
+ ${python:Depends}
Description: 'python -c', with tab completion and shorthand
  pythonpy is an utility that facilitates the usage of Python one-liners. The
  command 'py' evaluates a string consisting of any Python expression. It can do
-

But this didn't helped at all. The lintian.d.o page for
"python-script-but-no-python-dep"[1] says:

"Packages with Python scripts should depend on the package python.
Those with scripts that specify a specific version of Python must
depend on that version of Python (exactly).

For example, if a script in the package uses #!/usr/bin/python, the
package needs a dependency on python. If a script uses
#!/usr/bin/python2.6, the package needs a dependency on python2.6. A
dependency on python (>= 2.6) is not correct, since later versions of
Python may not provide the /usr/bin/python2.6 binary."

What is the "exactly" version of Python for a script which has
"#!/usr/bin/env python2" as its shebang?

> it is generated *during/after* the build, so the clean target won't work.
>
> a "package.pyremove" file might help, not sure
>
> codesearch.debian.net might help
> egg path:pyremove$
>
> https://codesearch.debian.net/results/egg%20path%3Apyremove%24/page_0

"pyremove" didn't worked, but in the same page that I found references
to it[2], there's a suggestion to override "dh_python", which is what
I did[3]. Thanks for the suggestion. :-)

Regards,
Tiago.

[1]: https://lintian.debian.org/tags/python-script-but-no-python-dep.html
[2]: 
https://wiki.debian.org/Python/LibraryStyleGuide#Python_3.3.2F3.4_unittest_fixers_for_2to3
[3]: https://github.com/myhro/deb-pythonpy/commit/68db18e

-- 
Tiago "Myhro" Ilieve
Blog: https://blog.myhro.info/
GitHub: https://github.com/myhro
LinkedIn: https://br.linkedin.com/in/myhro
Montes Claros - MG, Brasil

Bug#816093: marked as done (RFS: osmose-emulator/0.9.96-1 [ITP] -- Sega Master System and Game Gear console emulator)

Your message dated Fri, 25 Mar 2016 19:29:51 + (UTC)
with message-id <1906104506.610713.1458934191141.javamail.ya...@mail.yahoo.com>
and subject line sponsored.
has caused the Debian Bug report #816093,
regarding RFS: osmose-emulator/0.9.96-1 [ITP] -- Sega Master System and Game 
Gear console emulator
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.)


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

Dear mentors,

  I am looking for a sponsor for my package "osmose-emulator"

 * Package name: osmose-emulator
   Version : 0.9.96-1
   Upstream Author : Bruno Vedder 
 * URL : http://bcz.asterope.fr/osmose.htm
 * License : GPL-3
   Section : games

  It builds those binary packages:

osmose-emulator - Sega Master System and Game Gear console emulator

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

  http://mentors.debian.net/package/osmose-emulator


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

dget -x http://mentors.debian.net/debian/pool/contrib/o/osmose-emulator
/osmose-emulator_0.9.96-1.dsc


  Regards,
   Carlos Donizete Froes



-- System Information:
Debian Release: 8.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=pt_BR.utf8, LC_CTYPE=pt_BR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Nothing left to do.
the package is in unstable now.


cheers,
G.--- End Message ---

Bug#818048: marked as done (RFS: osmose-emulator/0.9.96-1 [ITP] -- Sega Master System and Game Gear console emulator)

Your message dated Fri, 25 Mar 2016 19:29:51 + (UTC)
with message-id <1906104506.610713.1458934191141.javamail.ya...@mail.yahoo.com>
and subject line sponsored.
has caused the Debian Bug report #814610,
regarding RFS: osmose-emulator/0.9.96-1 [ITP] -- Sega Master System and Game 
Gear console emulator
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.)


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

  Dear mentors,

  I am looking for a sponsor for my package "osmose-emulator"

 * Package name: osmose-emulator
   Version : 0.9.96-1
   Upstream Author : Bruno Vedder 
 * URL : http://bcz.asterope.fr/osmose.htm
 * License : GPL-3
   Section : games

  It builds those binary packages:

osmose-emulator - Sega Master System and Game Gear console emulator

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

  http://mentors.debian.net/package/osmose-emulator


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

dget -x http://mentors.debian.net/debian/pool/contrib/o/osmose-emulator
/osmose-emulator_0.9.96-1.dsc


  Regards,
   Carlos Donizete Froes



-- System Information:
Debian Release: 8.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=pt_BR.utf8, LC_CTYPE=pt_BR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Nothing left to do.
the package is in unstable now.


cheers,
G.--- End Message ---

Bug#814610: marked as done (RFS: osmose-emulator/0.9.96-1 [ITP] -- Sega Master System and Game Gear console emulator)

Your message dated Fri, 25 Mar 2016 19:29:51 + (UTC)
with message-id <1906104506.610713.1458934191141.javamail.ya...@mail.yahoo.com>
and subject line sponsored.
has caused the Debian Bug report #814610,
regarding RFS: osmose-emulator/0.9.96-1 [ITP] -- Sega Master System and Game 
Gear console emulator
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.)


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

Dear mentors,

  I am looking for a sponsor for my package "osmose-emulator"

 * Package name: osmose-emulator
   Version : 0.9.96-1
   Upstream Author : Bruno Vedder 
 * URL : http://bcz.asterope.fr/osmose.htm
 * License : GPL-3+
   Section : games

  It builds those binary packages:

osmose-emulator - Sega Master System and Game Gear console emulator

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

  http://mentors.debian.net/package/osmose-emulator


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

dget -x http://mentors.debian.net/debian/pool/main/o/osmose-emulator
/osmose-emulator_0.9.96-1.dsc


  Regards,
   Carlos Donizete Froes



-- System Information:
Debian Release: 8.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=pt_BR.utf8, LC_CTYPE=pt_BR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Nothing left to do.
the package is in unstable now.


cheers,
G.--- End Message ---

Bug#814456: marked as done (RFS: libpam-ufpidentity/1.0-1 [ITP] -- UFP Identity PAM Module)

Your message dated Fri, 25 Mar 2016 19:23:25 + (UTC)
with message-id <1350406008.579488.1458933805465.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#814456: RFS: libpam-ufpidentity/1.0-1 [ITP] -- UFP 
Identity PAM Module
has caused the Debian Bug report #814456,
regarding RFS: libpam-ufpidentity/1.0-1 [ITP] -- UFP Identity PAM Module
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)

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

  Dear mentors,

  I am looking for a sponsor for my package "pam-ufpidentity"

 * Package name: pam-ufpidentity
   Version : 1.0-debian2~unstable
   Upstream Author : Richard Levenberg 
 * URL : https://github.com/ufpidentity/pam_ufpidentity
 * License : GPL-2+
   Section : libs

  It builds those binary packages:

pam-ufpidentity - Package UFP Identity PAM module
 pam-ufpidentity1 - PAM library for UFP identity

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

  http://mentors.debian.net/package/pam-ufpidentity

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

dget -x
http://mentors.debian.net/debian/pool/main/p/pam-ufpidentity/pam-ufpidentity_1.0-debian2~unstable.dsc

  More information about pam-ufpidentity can be obtained from
https://github.com/ufpidentity/pam_ufpidentity.

  Changes since the last upload:

  pam-ufpidentity (1.0-debian2~unstable) unstable; urgency=low

  * adding named package

 -- richardl   Tue, 09 Feb 2016 11:28:41 -0800

n.b. This package has a dependency on

  http://mentors.debian.net/package/identity4c

  One can also download this package with dget using this command:

dget -x
http://mentors.debian.net/debian/pool/main/i/identity4c/identity4c_1.0-debian1~unstable.dsc

  More information about hello can be obtained from
https://github.com/ufpidentity/identity4c

  Changes since the last upload:

  identity4c (1.0-debian1~unstable) unstable; urgency=low

  * building with sbuild

 -- richardl   Thu, 04 Feb 2016 00:36:51 -0800

  Regards,
   Richard Levenberg
-- 
Richard Levenberg

UFP Identity, Inc.
https://www.ufp.com/
--- End Message ---
--- Begin Message ---
Uploaded :)

cheers and happy Easter,

Gianfranco

Il Lunedì 21 Marzo 2016 19:27, Richard Levenberg  ha scritto:
The test credentials (example.com) are provided to allow for testing
with the services without having to register. The test credentials only
allow a username 'guest.' The test credentials are only used in the main
method which is only enabled in the static compilation when PIC is NOT
enabled. The main method is not compiled into the library.

The remote service requires registration of a client key/CSR which is
described here:

https://www.ufp.com/identity/integration.html#getting_started

Then send the CSR to i...@ufp.com.

Did you do that?

On 3/21/16 10:45 AM, Gianfranco Costamagna wrote:
> Hi, some questions about the identity4c package:
> why there is an example.com hardcoded in the sources?
> I see also some pem certificates provided here.
> 
> 
> how does it interface with the libpam-ufpidentity?
> I guess in no ways, because it is in the main, right?
> 
> second question: is the remote pam service something under a fee?
> I tried to register on ufp.com or whatever was written on readme, but I got 
> no confirmation email.
>--- End Message ---

Bug#811393: RFS: flint -- C library for arbitrary-precision ball arithmetic

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

Hi,

something needs changes:

- std-version is now 3.9.7
- unsecure VCS fields
- call ldconfig in rules? what?
- changing names usually is just bad, people won't find the package, and you 
will
diverge from upstream.

do you have any good rationale?

- do you pass --parallel twice? (I mean in build)
- what about dh_auto_configure -- (FLAGS) instead of ./configure?
(I think the build fails for "unknown parameters, right?"
- they have a Makefile.in, but no configure.ac.
please ask them to include it, and do autoreconf before building
(Probably they are not using autotools but they just like similar and confusing 
names)

- copyrights missing, e.g. Tommy Hofmann, Arb, FSFa
licenses looks good to me

check-all-the-things:
codespell --quiet-level=3
flawfinder -Q -c .
cppcheck -j1 --quiet -f . | grep -vF 'cppcheck: error: could not find or open 
any of the paths given.'
[lots]

# You should almost never use -m64 and -m32 when compiling.
$ grep -rE -- '-m64|-m32' .
./configure:   ABI_FLAG="-m32"
./configure:   ABI_FLAG="-m64"

$ pep8 --ignore W191 .

pyflakes{,3}

./doc/source/_static/arbtext.pdf
./doc/source/_static/arbtext.eps

maybe recreate during build?
Please add some upstream metadata: https://wiki.debian.org/UpstreamMetadata


and the other stuf LGTM
(you shouldn't address all the above, something is just nice to have)

cheers,

G.




Il Lunedì 18 Gennaio 2016 16:12, Julien Puydt  ha 
scritto:
Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I'm looking for a sponsor for a new package:

* Package name: arb
   Version : 2.8.1
   Upstream Author : Fredrik Johansson
* URL : https://github.com/fredrik-johansson/arb
* License : GPL-2+
   Programming Lang: C
   Description : C library for arbitrary-precision floating-point 
ball arithmetic

Arb is a C library for high-performance arbitrary-precision 
floating-point ball (mid-rad interval) arithmetic. It supports complex 
numbers, polynomials, matrices, and evaluation of special functions, all 
with rigorous error bounding.

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

  http://mentors.debian.net/package/flint-arb


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

 dget -x 
http://mentors.debian.net/debian/pool/main/f/flint-arb/flint-arb_2.8.1-1.dsc

I plan to maintain this package as part of the debian-science team:
Vcs-Browser: 
http://anonscm.debian.org/gitweb/?p=debian-science/packages/arb.git
Vcs-Git: git://anonscm.debian.org/debian-science/packages/arb

Thanks,

Snark on #debian-science

Bug#811073: RFS: lbfgsb/3.0-1 [ITP]

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

Hi,

something needs changes:
- std-version= 3.9.7
- no watch file?
- no sane build system, why are you building the library such way?
you seem to use just two files in your library, why everything is dropped?
I don't think flags in rules are actually evaluated, because you don't set them
- dbg package is useless now that we have ddbg automatic generation.

Please address/comment/fix the above, and I'll do another spin

cheers,

G.




Il Venerdì 15 Gennaio 2016 13:45, Gard Spreemann  ha 
scritto:
Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

* Package name: lbfgsb
   Version : 3.0-1
   Upstream Author : Ciyou Zhu, Richard Byrd, Jorge Nocedal and Jose Luis 
Morales
* URL : http://users.iems.northwestern.edu/~nocedal/lbfgsb.html
* License : BSD-3-clause
   Section : math

It builds these binary packages:

liblbfgsb-dev - Limited-memory quasi-Newton bound-constrained
optimization (static library)

liblbfgsb0 - Limited-memory quasi-Newton bound-constrained
optimization

liblbfgsb0-dbg - Limited-memory quasi-Newton bound-constrained
optimization (debug symbols)


Note that upstream's tarball [1] contains precompiled binaries, and is
also a minor tarbomb. I have therefore repackaged it. You will find
that my orig tarball is a strict subset of upstream's.

My package includes two patches:

- replace-linpack-with-lapack.patch: The library code originally uses
   LINPACK (from an embedded copy). Since LINPACK has largely been
   superseded by LAPACK, this patch replaces calls to the former with
   equivalent calls to the latter. Specifically, dpofa is replaced by
   dpotrf, and dtrsl is replaced by dtrtrs.

- silence.patch: The library's documentation indicates that it will
   only write out messages when the iprint flag is greater than
   zero. There are two places where writing still happens
   unconditionally, which this patch fixes. A similar patch was also
   applied by the SciPy project (see their issue 3238).

I've used the patched package on and off for the past few years and
have not encountered problems.


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

http://mentors.debian.net/package/lbfgsb

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

dget -x http://mentors.debian.net/debian/pool/main/l/lbfgsb/lbfgsb_3.0-1.dsc


More information about lbfgsb can be obtained from [2].

[1] http://users.iems.northwestern.edu/~nocedal/Software/Lbfgsb.3.0.tar.gz
[2] http://users.iems.northwestern.edu/~nocedal/lbfgsb.html

Regards,
Gard Spreemann

Re: Packaging pythonpy

Hi Gianfranco,

On 25 March 2016 at 06:25, Gianfranco Costamagna
 wrote:
>
> adding python to the dependencies?
> do you have python to build dependencies, dh-python and python:Depends on the
> binary package?

This is what is strange. I've made the following changes:

-
diff --git a/debian/control b/debian/control
index f0c1b3f..5205298 100644
--- a/debian/control
+++ b/debian/control
@@ -3,6 +3,7 @@ Section: python
 Priority: optional
 Maintainer: Tiago Ilieve 
 Build-Depends: debhelper (>= 9),
+   dh-python,
python (>= 2.7.3),
python-setuptools (>= 0.6.24)
 Standards-Version: 3.9.7
@@ -13,7 +14,9 @@ Vcs-Browser: https://github.com/myhro/deb-pythonpy

 Package: pythonpy
 Architecture: all
-Depends: ${misc:Depends}, ${python:Depends}
+Depends: python (>= 2.7.3),
+ ${misc:Depends},
+ ${python:Depends}
 Description: 'python -c', with tab completion and shorthand
  pythonpy is an utility that facilitates the usage of Python one-liners. The
  command 'py' evaluates a string consisting of any Python expression. It can do
-

But this didn't helped at all. The lintian.d.o page for
"python-script-but-no-python-dep"[1] says:

"Packages with Python scripts should depend on the package python.
Those with scripts that specify a specific version of Python must
depend on that version of Python (exactly).

For example, if a script in the package uses #!/usr/bin/python, the
package needs a dependency on python. If a script uses
#!/usr/bin/python2.6, the package needs a dependency on python2.6. A
dependency on python (>= 2.6) is not correct, since later versions of
Python may not provide the /usr/bin/python2.6 binary."

What is the "exactly" version of Python for a script which has
"#!/usr/bin/env python2" as its shebang?

> it is generated *during/after* the build, so the clean target won't work.
>
> a "package.pyremove" file might help, not sure
>
> codesearch.debian.net might help
> egg path:pyremove$
>
> https://codesearch.debian.net/results/egg%20path%3Apyremove%24/page_0

"pyremove" didn't worked, but in the same page that I found references
to it[2], there's a suggestion to override "dh_python", which is what
I did[3]. Thanks for the suggestion. :-)

Regards,
Tiago.

[1]: https://lintian.debian.org/tags/python-script-but-no-python-dep.html
[2]: 
https://wiki.debian.org/Python/LibraryStyleGuide#Python_3.3.2F3.4_unittest_fixers_for_2to3
[3]: https://github.com/myhro/deb-pythonpy/commit/68db18e

-- 
Tiago "Myhro" Ilieve
Blog: https://blog.myhro.info/
GitHub: https://github.com/myhro
LinkedIn: https://br.linkedin.com/in/myhro
Montes Claros - MG, Brasil

Re: Package openBVE requires a new maintainer

2016-03-25 Thread James Cowgill

Hi,

On Fri, 2016-03-25 at 14:44 +, Christopher Lees wrote:
> I hope this is the correct place to try and get into touch with someone.
> 
> I appear to have become the current upstream coder for the package openBVE:
> https://packages.debian.org/search?keywords=openbve
> My Github repository is here:
> http://github.com/leezer3/OpenBVE/
> 
> This was abandoned by the original developer in ~2007 or so, and
> unfortunately the version in the Debian repositories is broken on anything
> above Wheezy.

I had a go with the version in unstable using some routes I found and
things seem to work ok. What exactly is broken?

> Whilst I'm not sure I'd currently consider my much updated version ready
> for Debian itself, I would like to get into touch with someone who could
> potentially adopt the maintainership of the current package, and fix the
> current breaking issues with it.
> 
> When that's done, discussion could be had about what is required, and guide
> me through the process of getting a version of my builds into the
> repositories.
> 
> I have tried mailing the current maintainer- Paul Sladen, but whilst I've
> had two replies promising he'll get back to me, I've had nothing more.
> Whilst I have no experience in Debian packaging, I'm happy to work with
> someone to get this situation sorted out.

Did you contact the Debian CLI Applications Team, the team listed in
the maintainer field of the package as well?
pkg-cli-apps-t...@lists.alioth.debian.org

How long ago were those replies? The package was last updated in
January this year so it doesn't seem unmaintained.

James

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

Bug#818948: marked as done (RFS: gap-grape/4r7+ds-1 [ITP] -- GRaph Algorithms using PErmutation groups for GAP)

Your message dated Fri, 25 Mar 2016 15:55:23 +0100
with message-id <56f5515b.20...@rezozer.net>
and subject line RFS: gap-grape/4r7+ds-1 [ITP] -- GRaph Algorithms using 
PErmutation groups for GAP
has caused the Debian Bug report #818948,
regarding RFS: gap-grape/4r7+ds-1 [ITP] -- GRaph Algorithms using PErmutation 
groups for GAP
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.)


-- 
818948: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818948
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 the new Debian package gap-grape, a 
package
for the Computer Algebra System (CAS) GAP. This package brings nauty to 
GAP.

Thanks in advance,
Jerome

[1] https://anonscm.debian.org/git/debian-science/packages/gap-grape.git

-- 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)
--- End Message ---
--- Begin Message ---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Thanks to Andreas Tille,
Jerome
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJW9VFbAAoJEIC/w4IMSybj2VcH+wYl2xzLMmJI3L4lHJcQgEVH
SfIwwwKgN+lo1W/+Yv+V9TmCyVWvCCOSxfB9mn/wZSg5UUECbpjMmVdEFqP1bFSg
EZJ4fOvS7jlQFxrzZ4srrBfQit/diEJlqZT9SdYd0rzaSwPa4aBs2mgVmwa6wt6F
zt21jCpdpgMX/ejs0QFoV3Gq7ZE13mEmzQ0jmSPE5xugDfcGxFqsR9AHeuctZDc8
kOSFIR1djCz92GPfUgIUfWX88DNJ4qT8O+aEzLUmBcdWa6kXVs7O1K/X1Zko0Xuj
ONYZgE2/9yU3XY8jOTNa3Zj5YToDmQYFqsXz3ByySd3pcik/jAP91JEB1ATEQus=
=ol5J
-END PGP SIGNATURE End Message ---

Bug#818788: marked as done (RFS: gmp-ecm/7.0+ds-1 [NEW MAJOR VERSION] -- Factor integers using the Elliptic Curve Method)

Your message dated Fri, 25 Mar 2016 15:56:10 +0100
with message-id <56f5518a.8060...@rezozer.net>
and subject line RFS: gmp-ecm/7.0+ds-1 [NEW MAJOR VERSION] -- Factor integers 
using the Elliptic Curve Method
has caused the Debian Bug report #818788,
regarding RFS: gmp-ecm/7.0+ds-1 [NEW MAJOR VERSION] -- Factor integers using 
the Elliptic Curve Method
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.)


-- 
818788: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818788
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 gmp-ecm pacakge. This package brings
to Debian the latest major release of gmp-ecm, a mathematical
software suite to `Factor integers using the Elliptic Curve Method'.
This software is part of Sage.

Thanks in advance,
Jerome

[1] https://anonscm.debian.org/cgit/debian-science/packages/gmp-ecm.git

-- 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)
--- End Message ---
--- Begin Message ---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Thanks to Andreas Tille,
Jerome
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJW9VGKAAoJEIC/w4IMSybj1SAIAId/aWBQTLGYCNMlN4Gw7v+y
03m6U5OlL0B1Gk80QsDmHQ/aMg+/Zz+ZUsbdV80erm6/GX33vmbgNRimNlYsHRzB
mWei9Slsf5q1LsOZU/JbDT9n3Q99DTgwxyDV+cwh/QCCEHhVThq4Xst2zlDWZZ+g
BWPoXBeaw69T6mcqePG0yWCtLHmbbzPSaIqOlsZcysZmW7y4hBu2pXdLHE5DekzX
0T7mBARH3XEoq1X4dcNbMg6wWegXN4obxzctX2yoE1blhENp9ZK6T/J3aeCREbrF
OOI40p0lzJutE4tFkmBdsYB2tgHuHcJp69pKQvcghmdOWzwgbguOTb7YKB2j3h8=
=Ak0e
-END PGP SIGNATURE End Message ---

Bug#818974: RFS: gpvdm/4.40-1 – solar cell simulation tool

2016-03-25 Thread Paul Wise

On Tue, 22 Mar 2016 12:29:58 + Roderick MacKenzie wrote:

> I am looking for a sponsor for my package gpvdm.  To download the
> package please visit:  http://gpvdm.com/debian.php
> 
> Gpvdm is a tool to design and optimize solar cells.

I don't intend to sponsor this, but here are some thoughts:

The package fails to build under pbuilder due to the Build-Depends
issue I mentioned below, see below for the logs.

I would suggest joining the Debian Science team, they might sponsor it:

https://wiki.debian.org/Teams/DebianScience

Since you are upstream I would suggest reading Debian's upstream guide:

https://wiki.debian.org/UpstreamGuide

I would suggest publishing the upstream source code in a distributed
version control system like git.

https://git-scm.com/

Please add some upstream metadata: https://wiki.debian.org/UpstreamMetadata

Please add a debian/watch file: https://wiki.debian.org/debian/watch

You might want to publish tarballs upstream and publish OpenPGP
signatures for them and look at the OpenPGP best practices.

https://help.riseup.net/en/security/message-security/openpgp/best-practices

*.mo are generated files and should not be present in the source.

You may want to fuzz test C based programs using zzuf and afl.

You may want to fuzz test Python based programs using python-afl.

Unless your build system doesn't work with `make -j4`, I would suggest
using --parallel in the arguments to dh in debian/rules.

The manual pages should not be compressed in the source tree since they
can't easily be modified/patched. Also one has a typo: "Releced"

The manual pages should be installed by the upstream build system
rather than having dh_install install them.

You have overridden possible-gpl-code-linked-with-openssl (which
usually indicates a serious issue) without any explanation.

I would suggest Section: science instead of Section: misc.

-dev packages usually go in Build-Depends instead of Depends, since
they are needed at build time instead of runtime. You are also missing
a Build-Depends on pkg-config, see the build errors below.

The debian/changelog should have unstable as the suite instead
of UNRELEASED, which implies it isn't ready for upload.

Some parts of the code are GPLv2-only and some are GPLv2+, is that
intentional or should all the code be under the same terms?

Please publish the SVG/XCF files for your PNG images if they still
exist and render the PNG files at build time with rsvg/inkscape.

Personally I would put all the .c/.h files into a src subdir.

Personally I would wrap the README files at 80 columns.

The README references opvdm, is that the old name for gpvdm?

I would suggest running this command to make diffs of the Debian
packaging more readable.

wrap-and-sort --short-indent --wrap-always --sort-binary-packages 
--trailing-comma --verbose

Please read the upgrading checklist and update Standards-Version when
you have made the requisite changes.

https://www.debian.org/doc/debian-policy/upgrading-checklist

Automatic checks:

build

...
make[1]: Entering directory '/build/gpvdm-4.40'
gcc -c -D full_time_domain -D enable_fx -D LONGDOUBLE -D dos_bin -D linux
`pkg-config --cflags dbus-1` -I/usr/include/suitesparse/ -Werror -Wall -O2 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro -D dbus  
solver_interface.c -o solver_interface.o
/bin/sh: 1: pkg-config: not found
gcc -c -D full_time_domain -D enable_fx -D LONGDOUBLE -D dos_bin -D linux
`pkg-config --cflags dbus-1` -I/usr/include/suitesparse/ -Werror -Wall -O2 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro -D dbus  
light_utils.c -o light_utils.o
/bin/sh: 1: pkg-config: not found
gcc -c -D full_time_domain -D enable_fx -D LONGDOUBLE -D dos_bin -D linux
`pkg-config --cflags dbus-1` -I/usr/include/suitesparse/ -Werror -Wall -O2 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro -D dbus  
gui_hooks.c -o gui_hooks.o
/bin/sh: 1: pkg-config: not found
gui_hooks.c:31:23: fatal error: dbus/dbus.h: No such file or directory
compilation terminated.
makefile:67: recipe for target 'gui_hooks.o' failed
make[1]: *** [gui_hooks.o] Error 1
make[1]: Leaving directory '/build/gpvdm-4.40'
dh_auto_build: make -j1 returned exit code 2

lintian

I: gpvdm source: missing-debian-source-format
P: gpvdm source: no-homepage-field
P: gpvdm source: no-dep5-copyright
W: gpvdm source: out-of-date-standards-version 3.9.6 (current is 3.9.7)
I: gpvdm source: debian-watch-file-is-missing

check-all-the-things:

$ find -type f \( -iname '*.sh' -o -iname '*.bash' \) -exec bashate --ignore 
E002,E003 {} +
E010: Do not on same line as for: 'for i in `find -type f` ; do md5sum $i; done 
>list.dat'
 - ./update.sh : L23
E001: Trailing Whitespace: 'mkdir ${rpmdir} '
 - ./make_rpm.sh : L33
E001: Trailing Whitespace: 'cd ${rpmdir} '
 - ./make_rpm.sh : L34
E010: Do not on same line as for: 'for i in `find|grep -v .git|grep -v .o$|grep 
-v ~$|grep -v materials|grep -v dll$|grep -v

Package openBVE requires a new maintainer

2016-03-25 Thread Christopher Lees

Hi,

I hope this is the correct place to try and get into touch with someone.

I appear to have become the current upstream coder for the package openBVE:
https://packages.debian.org/search?keywords=openbve
My Github repository is here:
http://github.com/leezer3/OpenBVE/

This was abandoned by the original developer in ~2007 or so, and
unfortunately the version in the Debian repositories is broken on anything
above Wheezy.

Whilst I'm not sure I'd currently consider my much updated version ready
for Debian itself, I would like to get into touch with someone who could
potentially adopt the maintainership of the current package, and fix the
current breaking issues with it.

When that's done, discussion could be had about what is required, and guide
me through the process of getting a version of my builds into the
repositories.

I have tried mailing the current maintainer- Paul Sladen, but whilst I've
had two replies promising he'll get back to me, I've had nothing more.
Whilst I have no experience in Debian packaging, I'm happy to work with
someone to get this situation sorted out.


Many thanks.

Christopher Lees

Bug#819188: RFS: icu4j/57.1-1

grep google . -Ri |grep -i copyright


cheers,

G.





Il Venerdì 25 Marzo 2016 13:47, 殷啟聰  ha scritto:
There are Google stuff? Could you point me to the files? Thanks!

Bug#819188: RFS: icu4j/57.1-1

2016-03-25 Thread 殷啟聰

There are Google stuff? Could you point me to the files? Thanks!

Bug#819066: marked as done (RFS: python-bitstring/3.1.4-1)

Your message dated Fri, 25 Mar 2016 12:46:47 + (UTC)
with message-id <953721948.307239.1458910007661.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#819066: RFS: python-bitstring/3.1.4-1
has caused the Debian Bug report #819066,
regarding RFS: python-bitstring/3.1.4-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.)


-- 
819066: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819066
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 "python-bitstring"

* Package name: python-bitstring
  Version : 3.1.4-1
  Upstream Author : Scott Griffiths 
* URL : http://scott-griffiths.github.io/bitstring/
* License : MIT
  Section : python

It builds those binary packages:

  python-bitstring - Python module for manipulation of binary data 
(Python 2)
  python-bitstring-doc - Python module for manipulation of binary data 
(documentation)
  python3-bitstring - Python module for manipulation of binary data 
(Python 3)


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


  http://mentors.debian.net/package/python-bitstring

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

  dget -x 
http://mentors.debian.net/debian/pool/main/p/python-bitstring/python-bitstring_3.1.4-1.dsc


Or checkout the packaging repository at:


https://anonscm.debian.org/git/debian-science/packages/python-bitstring.git

Successful build log on debomatic:


http://debomatic-amd64.debian.net/distribution#unstable/python-bitstring/3.1.4-1/buildlog

Changes since the last upload:

  * Update patch queue:
- Drop 0001-fix-sphinxdoc-build.patch, fixed upstream.
- Refresh fix-testsuite-discovery.patch.
  * Add gbp configuration file.
  * d/rules: add DH_VERBOSE option.
  * d/copyright: update dates
  * d/control: cme fixed:
- Drop versioned depends on python-sphinx.
- Bump standards version to 3.9.7, no changes required.
- Wrap and sort.

Regards,
Ghislain Vaillant
--- End Message ---
--- Begin Message ---
Hi,  I sponsored it but please note:


you dropped this part of the patch:
--html_theme = 'bizstyle'
-+html_theme = 'default'



but this wasn't upstreamed.

so please send me a new request if you want me to do a new upload.

cheers,

G.


Il Mercoledì 23 Marzo 2016 13:18, Ghislain Vaillant  ha 
scritto:
Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "python-bitstring"

* Package name: python-bitstring
   Version : 3.1.4-1
   Upstream Author : Scott Griffiths 
* URL : http://scott-griffiths.github.io/bitstring/
* License : MIT
   Section : python

It builds those binary packages:

   python-bitstring - Python module for manipulation of binary data 
(Python 2)
   python-bitstring-doc - Python module for manipulation of binary data 
(documentation)
   python3-bitstring - Python module for manipulation of binary data 
(Python 3)

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

  http://mentors.debian.net/package/python-bitstring

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

   dget -x 
http://mentors.debian.net/debian/pool/main/p/python-bitstring/python-bitstring_3.1.4-1.dsc

Or checkout the packaging repository at:


https://anonscm.debian.org/git/debian-science/packages/python-bitstring.git

Successful build log on debomatic:


http://debomatic-amd64.debian.net/distribution#unstable/python-bitstring/3.1.4-1/buildlog

Changes since the last upload:

   * Update patch queue:
 - Drop 0001-fix-sphinxdoc-build.patch, fixed upstream.
 - Refresh fix-testsuite-discovery.patch.
   * Add gbp configuration file.
   * d/rules: add DH_VERBOSE option.
   * d/copyright: update dates
   * d/control: cme fixed:
 - Drop versioned depends on python-sphinx.
 - Bump standards version to 3.9.7, no changes required.
 - Wrap and sort.

Regards,
Ghislain Vaillant--- End Message ---

Bug#819181: RFS: cl-asdf/3.1.7 - Another System Definition Facility

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

hi,

+override_dh_clean:
+   dh_quilt_patch
+   dh_clean


why?
also adding quilt to b-d-i seems useless to me.

cheers,

G.

Bug#819188: RFS: icu4j/57.1-1

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

1)

some copyright seems missing:
google, unicode, IBM Corporation(?) and probably others



2) copyright-old.txt? why you have it?

the other stuff LGTM, I'm not a java man, but the package cleanup looks nice!

I dind't try to build and run, but if you fix the above I'll give it a shot.

cheers,

G.

Bug#818184: RFS: hal-flash/0.3.3-1 [ITP]

Hi,


>Personally, I would remove Flash from my system entirely and use HTML5>video 
>or when that isn't available, run youtube-dl, get-flash-videos,
>cclive or similar on the command-line. Some desktop video players can
>also use these to play video from the web.


I also hate flash, for many many and many reasons (including making my browser 
crash back some years
ago).

*but* the fact that Debian stops shipping flash, won't help much the world in 
faster deprecating
it, will just annoy some end users more and more.

I personally believe in free software, but the real world isn't so ideal, and 
while I don't
use flash anymore since some years (android helped here, sometimes I use an 
agent overrider on my firefox,
and the website shows me the android flash-free version), I can argue that 
somebody could use it.

So, my opinion is that it has some reasons to exist on Debian, even if probably 
I won't ever use it.

cheers,

G.

Re: Packaging pythonpy