Bug#1033490: unblock: py7zr/0.11.3+dfsg-5

2023-03-25 Thread Sandro Tosi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: py...@packages.debian.org, mo...@debian.org
Control: affects -1 + src:py7zr

Please unblock package py7zr

This package fixes CVE-2022-44900 aka #1032091

[ Reason ]
fixes a security issue and makes the package RC-free, allowing calibre to stay
in bookwork

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

The package diff is visible 
https://salsa.debian.org/python-team/packages/py7zr/-/compare/debian%2F0.11.3+dfsg-4...debian%2F0.11.3+dfsg-5?from_project_id=56010=false
 (if you prefer an actual debdiff file attached, let me know)

unblock py7zr/0.11.3+dfsg-5



Bug#1033375: unblock: amule/1:2.3.3-3

2023-03-23 Thread Sandro Tosi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: am...@packages.debian.org, mo...@debian.org
Control: affects -1 + src:amule

Please unblock package amule

amule was removed from testing during the Wx transition, but now support for wx
3.2 has been added and it builds and works properly in unstable

[ Reason ]
shipping amule

[ Impact ]
none, it's not in testing as of now

[ Tests ]
builds fine (as from the buildd network) and works fine too

[ Risks ]
none

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [ ] attach debdiff against the package in testing

[ Other info ]
(Anything else the release team should know.)

unblock amule/1:2.3.3-3



Bug#1027044: transition: numpy 1.24.x

2023-01-08 Thread Sandro Tosi
> The last packages involved in the Python 3.11 rebuilds build-depending
> on numpy have now built on all architectures.
>
> Please go ahead.

thanks! numpy/1.24.1-2 has been accepted in unstable and the pending
bugs severity has been bumped to serious.

Regards,
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi



Bug#1027044: transition: numpy 1.24.x

2023-01-07 Thread Sandro Tosi
> bugs have been filed:
> https://udd.debian.org/cgi-bin/bts-usertags.cgi?user=debian-python%40lists.debian.org=numpy1.24

the pending bugs number is dropping rapidly, so i'd like to ask for
this transition consideration. having numpy 1.24 in unstable, and
raising severity to RC, will likely speed up bugs fixing too.

Regards,
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi



Bug#1027044: transition: numpy 1.24.x

2022-12-28 Thread Sandro Tosi
> > There are handful more errors in the form of:
> >
> >   * ValueError: setting an array element with a sequence. The
> > requested array has an inhomogeneous shape after 1 dimensions. The
> > detected shape was (2,) + inhomogeneous part.
> >   * Too many indices for array: array is 0-dimensional, but 1 were indexed
> >
> > which will need to be looked at in more details, likely by individual
> > projects upstream.
>
> The sooner these bugs are filed, the better.

bugs have been filed:
https://udd.debian.org/cgi-bin/bts-usertags.cgi?user=debian-python%40lists.debian.org=numpy1.24


-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi



Bug#1026119: transition: matplotlib

2022-12-28 Thread Sandro Tosi
> thanks! matplotlib/3.6.2-3 has been accepted in unstable

bugs have been filed:
https://udd.debian.org/cgi-bin/bts-usertags.cgi?user=debian-python%40lists.debian.org=matplotlib3.6

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi



Bug#1027044: transition: numpy 1.24.x

2022-12-26 Thread Sandro Tosi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
X-Debbugs-Cc: nu...@packages.debian.org, mo...@debian.org
Control: affects -1 + src:numpy

Resuming from https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025788#43

In the meantime, since upstream released it, i've uploaded
numpy/1.24.0 to experimental and the autopkgtest results are
https://qa.debian.org/excuses.php?experimental=1=numpy

now, there's a lot of red in there but almost all of the errors come
in the format of

AttributeError: module 'numpy' has no attribute 'X'

with X being [float, int, bool, object, ...].

This is because, numpy upstream in 1.24.0, finally decided to expire
https://numpy.org/doc/stable/release/1.24.0-notes.html#:~:text=The%20deprecation%20for%20the%20aliases
some deprecations introduced in 1.20.0
https://numpy.org/doc/stable/release/1.20.0-notes.html#using-the-aliases-of-builtin-types-like-np-int-is-deprecated
(released almost 2 years ago).

All of those are quite straightforward to fix, since often it's just
necessary to stop importing them from numpy and use the python native
types.

There are handful more errors in the form of:

  * ValueError: setting an array element with a sequence. The
requested array has an inhomogeneous shape after 1 dimensions. The
detected shape was (2,) + inhomogeneous part.
  * Too many indices for array: array is 0-dimensional, but 1 were indexed

which will need to be looked at in more details, likely by individual
projects upstream.

This additional transition seems to be comfortably in the reach for
Bullseye and will place us in a better position to get support from
upstream. I also anticipate that a few more patch releases (fixing
bugs etc) for the 1.24.x series will be published before Bullseye is
released and we would like to update numpy to them in Debian if
reasonable.

Please let me know if i can proceed with a numpy upload to unstable.


With ginggs' reply https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025788#48

Hi Sandro

I should have closed this bug once numpy 1:1.23.5-2 migrated.  Doing
so now.  Please file a new bug for discussing 1.24.0.

On Mon, 26 Dec 2022 at 00:12, Sandro Tosi  wrote:
> In the meantime, since upstream released it, i've uploaded
> numpy/1.24.0 to experimental and the autopkgtest results are
> https://qa.debian.org/excuses.php?experimental=1=numpy
>
> now, there's a lot of red in there but almost all of the errors come
> in the format of
>
> AttributeError: module 'numpy' has no attribute 'X'
>
> with X being [float, int, bool, object, ...].
>
> This is because, numpy upstream in 1.24.0, finally decided to expire
> https://numpy.org/doc/stable/release/1.24.0-notes.html#:~:text=The%20deprecation%20for%20the%20aliases
> some deprecations introduced in 1.20.0
> https://numpy.org/doc/stable/release/1.20.0-notes.html#using-the-aliases-of-builtin-types-like-np-int-is-deprecated
> (released almost 2 years ago).
>
> All of those are quite straightforward to fix, since often it's just
> necessary to stop importing them from numpy and use the python native
> types.

That's a lot of breakage, but good that the fix is straightforward.

> There are handful more errors in the form of:
>
>   * ValueError: setting an array element with a sequence. The
> requested array has an inhomogeneous shape after 1 dimensions. The
> detected shape was (2,) + inhomogeneous part.
>   * Too many indices for array: array is 0-dimensional, but 1 were indexed
>
> which will need to be looked at in more details, likely by individual
> projects upstream.

The sooner these bugs are filed, the better.

> This additional transition seems to be comfortably in the reach for
> Bullseye and will place us in a better position to get support from
> upstream. I also anticipate that a few more patch releases (fixing
> bugs etc) for the 1.24.x series will be published before Bullseye is
> released and we would like to update numpy to them in Debian if
> reasonable.

s/Bullseye/bookworm but agreed.

> Please let me know if i can proceed with a numpy upload to unstable.

Please let's wait for a bit on this one.  There's still a matplotlib
transition in flight (#1026119) that needs bugs filed and autopkgtests
fixed before it can migrate.  Let's aim to do this once the initial
rebuilds for Python 3.11 as default (#1026825) have been done.  In the
meantime, it would help if bugs were filed against the packages that
need updating for numpy 1.24.x.



Bug#1025788: transition: numpy

2022-12-25 Thread Sandro Tosi
> On Mon, 12 Dec 2022 at 23:27, Sandro Tosi  wrote:
> > thanks, numpy/1.23.5-2 has just been uploaded to unstable.
>
> \o/

In the meantime, since upstream released it, i've uploaded
numpy/1.24.0 to experimental and the autopkgtest results are
https://qa.debian.org/excuses.php?experimental=1=numpy

now, there's a lot of red in there but almost all of the errors come
in the format of

AttributeError: module 'numpy' has no attribute 'X'

with X being [float, int, bool, object, ...].

This is because, numpy upstream in 1.24.0, finally decided to expire
https://numpy.org/doc/stable/release/1.24.0-notes.html#:~:text=The%20deprecation%20for%20the%20aliases
some deprecations introduced in 1.20.0
https://numpy.org/doc/stable/release/1.20.0-notes.html#using-the-aliases-of-builtin-types-like-np-int-is-deprecated
(released almost 2 years ago).

All of those are quite straightforward to fix, since often it's just
necessary to stop importing them from numpy and use the python native
types.

There are handful more errors in the form of:

  * ValueError: setting an array element with a sequence. The
requested array has an inhomogeneous shape after 1 dimensions. The
detected shape was (2,) + inhomogeneous part.
  * Too many indices for array: array is 0-dimensional, but 1 were indexed

which will need to be looked at in more details, likely by individual
projects upstream.

This additional transition seems to be comfortably in the reach for
Bullseye and will place us in a better position to get support from
upstream. I also anticipate that a few more patch releases (fixing
bugs etc) for the 1.24.x series will be published before Bullseye is
released and we would like to update numpy to them in Debian if
reasonable.

Please let me know if i can proceed with a numpy upload to unstable.

Regards,
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi



Bug#1026119: transition: matplotlib

2022-12-25 Thread Sandro Tosi
> > All in all, i think this transition is rather manageable and i'd like
> > to upload to unstable, if you're ok with it.
>
> Please go ahead.

thanks! matplotlib/3.6.2-3 has been accepted in unstable

Regards,
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi



Bug#1026119: transition: matplotlib

2022-12-24 Thread Sandro Tosi
> I'll update this report when i've uploaded a new release in experimental and
> with the results of some autopkgtests.

matplotlib/3.6.2-2 is in experimental and the results from autopkgtest
at https://qa.debian.org/excuses.php?experimental=1=matplotlib
are quite promising.

Looking at the errors:

* dolfin is a real bug, that needs to be correct:
https://bitbucket.org/fenics-project/dolfin/src/588d3acdb58727b6331588f9278d611534f4c93e/python/dolfin/common/plotting.py#lines-279
uses a now removed argument to `gca()`,
https://matplotlib.org/3.6.2/api/prev_api_changes/api_changes_3.6.0.html#:~:text=Keyword%20arguments%20to%20gca()

* lmfit-py, all failures seem unrelated to the new mpl, mostly missing modules

* mplcursors, seems like a valid bug, but it's unclear to me what the
failing test is trying to accomplish (catching warnings?) and so it
looks like an upstream fix (currently not available AFAICT) is neede

* poretools, not sure if this is a bug in this package or matplotlib

All in all, i think this transition is rather manageable and i'd like
to upload to unstable, if you're ok with it.

Regards,
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi



Re: Python 3.11 for bookworm?

2022-12-21 Thread Sandro Tosi
thoughts from a concerned maintainer

On Wed, Dec 21, 2022 at 1:24 PM Matthias Klose  wrote:
>
> while we have not an 100% agreement to go ahead, I think we should aim for 
> 3.11.
>
> The following steps would be:
>
>   - accept the current python3-defaults into
> testing (adding 3.11 as supported)
>   - ask for a transition slot to upload (see #1026825)
> python3-defaults with 3.11 as the default
>   - start the no-change NMUs
>   - file bug reports.
>   - fix issues
>   - let 3.11 as default migrate to testing.
>
> If things don't go as planned, we could default back to 3.10.  Mostly that 
> would
> be no-change uploads, however in the case of a 3.11 specific fix that doesn't
> work for 3.10, these fixes would need reverting.  I have no idea who many of
> these we will introduce with this transition.
>
> Also we might want to ask for some freeze exceptions for third party 
> libraries,
> that we can't fix before the feature freeze, unfortunately at this point we
> cannot say which and how many packages would be affected.

from expressions like

* "If things don't go as planned"
* "no idea who many of these we will introduce with this transition."
* "cannot say which and how many packages would be affected"

it seems this email advocates for a "let's wing it"[1] type of transition.

[1] https://en.wiktionary.org/wiki/wing_it

It appears there has been little work in preparing the work to
introduce python3.11 from its maintainer, instead that works has been
pushed downstream to maintainers.

if we continue with the plan as described above, several python
libraries/applications maintainers will be left with the short end of
the stick and deal with an unknown amount of issues (upstream fixes
not available, not ready and or/ not released, rushed, etc) with less
than a month from the beginning of the transition freeze[2]

[2] https://release.debian.org/bullseye/freeze_policy.html

[2] also highlights at the very beginning "Plan your changes for
bullseye", this change appears as if it was not planned and we should
be skeptical to proceed without further (and in advance) understanding
of the impact it may have on Bullseye.

Regards,
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi



Bug#1026119: transition: matplotlib

2022-12-14 Thread Sandro Tosi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
X-Debbugs-Cc: matplot...@packages.debian.org, mo...@debian.org
Control: affects -1 + src:matplotlib

Hello,
as suggested in #1025788, i'm filing this report to mark my intention to update
matplotlib from 3.5.2 (currently in unstable) to 3.6.2 (latest upstream
release).

I havent done any of the work needed for this task, so i'm not even sure if it's
feasable to achieve before the freeze (biggest unknown are possible NEW packages
either in mpl directly or in its b-d), but i'll give it a try.

I'll update this report when i've uploaded a new release in experimental and
with the results of some autopkgtests.

Regards,
Sandro



Bug#1025788: transition: numpy

2022-12-12 Thread Sandro Tosi
> Since the ABI package python3-numpy-abi9 was not bumped, I don't
> believe any rebuilds are needed.  Please go ahead and upload to
> unstable.

thanks, numpy/1.23.5-2 has just been uploaded to unstable.

> > Was i just too conservative in asking for a transition slow while i
> > should have uploaded to unstable (as done several other times) and
> > handle the autopkgtests one by one?
>
> Although this is not a transition in the way a C library transition
> requires rebuilding all reverse-dependencies, a transition to a new
> Python module often requires updating reverse-dependencies, of which
> numpy has many, so it's good to bring these to the attention of the
> release team.  Thanks for the headsup!

thanks! on the same line, i'm planning on upgrading matplotlib
(another foundation package) from 3.5.x in unstable to 3.6.x (latest
upstream release). Do you want me to submit a transition bug report
when ready?

Cheers,
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi



Bug#1025788: transition: numpy

2022-12-11 Thread Sandro Tosi
On Sun, Dec 11, 2022 at 1:26 PM Sebastian Ramacher  wrote:
> Which packages would be needed to be rebuilt for this transition?

I'm not sure how to answer this question.

numpy provides 2 virtual packages, to track the ABI/API version as
advertised by the upstream project. Between unstable and experimental,
we did not bump the ABI package (which stays at `python3-numpy-abi9`)
while we bumped the API package (from `python3-numpy-api14` to
`python3-numpy-api16`).

In the past times we asked for a transition (f.e. #658289 or #616364),
we referred to the -abiXX package, but in this case we cannot rely on
it since it was not bumped.

Was i just too conservative in asking for a transition slow while i
should have uploaded to unstable (as done several other times) and
handle the autopkgtests one by one?

Thanks,
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi



Bug#1025788: transition: numpy

2022-12-08 Thread Sandro Tosi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
X-Debbugs-Cc: nu...@packages.debian.org, mo...@debian.org
Control: affects -1 + src:numpy

Hello,
i would like to request a transition slot for numpy.

numpy/1.23.5 is in experimental, the autopkgtest for it are:

  https://qa.debian.org/excuses.php?experimental=1=numpy

I gave a look at the failures and several of them are due to other reasons
(uninstallable packages and the like), others may be attributed to python3.11
being added to unstable; issues related to the newer numpy are of the type

  AttributeError: module 'numpy' has no attribute 'asscalar'

which has been removed after being deprecated for 7 releases:

  https://numpy.org/doc/1.22/reference/generated/numpy.asscalar.html


Please let me know when i can upload numpy/1.23.5 to unstable.

Thanks,
Sandro



Re: Porter roll call for Debian Bookworm

2022-01-13 Thread Sandro Tosi
YunQiang,

On Tue, Jan 4, 2022 at 9:48 AM PICCA Frederic-emmanuel
 wrote:
>
>
> > > In case #1000435 (matplotlib crashes on mips64el) is not already on
> > > your radar, would you please take a look?
> > >
> >
> > Thank you. I will work on it right now.
>
> Hello, I just added some information about this problem on this bug
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001168#72
>
> it seems to me that this is something related to gcc-11.  If I build 
> matplotlib with gcc-10 there is no more crash.

did you have a chance to look at it yet? there's quite a substantial
number of packages depending on matplotlib that cant migrate to
testing until this issue is fixed, so we'd greatly appreciate it if
you can investigate it soon.

Thanks,
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi



Bug#989969: unblock: pylint/2.7.2-3

2021-06-16 Thread Sandro Tosi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package pylint

This fixes the RC bug 968897, by introducing a transitional package

[ Reason ]
fixig an RC bug

[ Impact ]
minimal/none, it's a new package

[ Tests ]
none

[ Risks ]
minimal/none

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

unblock pylint/2.7.2-3
diff --git a/debian/changelog b/debian/changelog
index bae2d32..9a67377 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,17 @@
+pylint (2.7.2-3) unstable; urgency=medium
+
+  * source only upload
+
+ -- Sandro Tosi   Wed, 16 Jun 2021 21:12:44 -0400
+
+pylint (2.7.2-2) unstable; urgency=medium
+
+  * Team upload
+  * debian/control
+- Introduce pylint3 trantional package for smooth upgrade (Closes: #968897)
+
+ -- Hideki Yamane   Mon, 14 Jun 2021 23:03:38 +0900
+
 pylint (2.7.2-1) unstable; urgency=medium
 
   * New upstream release
diff --git a/debian/control b/debian/control
index a60b507..cca8351 100644
--- a/debian/control
+++ b/debian/control
@@ -58,7 +58,7 @@ Depends: python3-astroid (>= 2.4.0),
 Recommends: python3-tk,
 Suggests: pylint-doc,
   python3-mccabe,
-Breaks: pylint3,
+Breaks: pylint3 (<< 2.7.2-2),
 python3-pylint-django (<< 2.0),
 python3-pylint-plugin-utils (<< 0.4),
 python3-pytest-pylint (<< 0.10),
@@ -83,3 +83,9 @@ Description: Python 3 code static checker and UML diagram 
generator
* pyreverse3: an UML diagram generator
* symilar3: an independent similarities checker
* epylint3: Emacs and Flymake compatible Pylint
+
+Package: pylint3
+Architecture: all
+Depends: pylint
+Description: Transitional dummy package
+ This is transitional dummy package for pylint, you can safely remove it.


Bug#984635: unblock: tqdm/4.57.0-2

2021-03-06 Thread Sandro Tosi
> > i'm open to suggestions on how to address it, but i would prefer to
> > avoid frankenstein monsters of x.y.zreallym.n.o or giant patches
> > against an old version of tqdm that could be addressed by a new
> > upstream release.
>
> Me too, but tqdm is a key package

apologies, i did not realized tqdm reached the "key package" status,
otherwise it'd have been more careful with the recent uploads :(

> and we really want to avoid
> unnecessary changes at much as possible at this stage. How much smaller
> is the diff between 4.51.0-1 and 4.56.2-1 compared to the current diff?

i let salsa do the diff, as i believe it's a bit easier to navigate
than pure debdiff (at least for upstream changes):

https://salsa.debian.org/python-team/packages/tqdm/-/compare/upstream%2F4.55.1...upstream%2F4.56.2

and this is the upstream diff between 4.56.2 and the latest upstream
release in unstable, 4.57.0:

https://salsa.debian.org/python-team/packages/tqdm/-/compare/upstream%2F4.56.2...upstream%2F4.57.0

which i believe is relatively tiny and mostly contains minor changes

> And what's in the additional delta?

sorry, delta between what specifically? 4.56.2-1 and 4.57.0-2?
https://salsa.debian.org/python-team/packages/tqdm/-/compare/debian%2F4.56.2-1...debian%2F4.57.0-2
the changes in the packaging files are just what's required by the
upstream code changes.

Let me know if some of these answer are not clear or satisfactory

Regards,
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi



Bug#984635: unblock: tqdm/4.57.0-2

2021-03-06 Thread Sandro Tosi
> What matters here is the delta between testing and unstable:
>  88 files changed, 2803 insertions(+), 1897 deletions(-)

that's right: the 4.56.2-1 upload fixed 980680 while this unblock
request is for 4.57.0-2 which fixes #983007, but you're right i didnt
diff testing..unstable

> Please review your own request taking into account all uploads since the
> package currently in testing. I would prefer a revert of the upstream
> version and just a fix for the FTBFS (#980680) in bullseye, is fixing
> that an option without the new upstream release?

to properly fix 980680 tqdm/4.56.2-1 is required, which is a newer
upstream release than bullseye anyway (since it has 4.51.0-1).

i'm open to suggestions on how to address it, but i would prefer to
avoid frankenstein monsters of x.y.zreallym.n.o or giant patches
against an old version of tqdm that could be addressed by a new
upstream release.

Regards,
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi



Bug#984635: unblock: tqdm/4.57.0-2

2021-03-05 Thread Sandro Tosi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package tqdm

[ Reason ]
the last upload of tqdm fixes a RC bug

the effects of that bug are only visible in reverse dependencies, and they were
caused by disabling setuptools_scm during build (as that interferes with our
build process).  That result in a package that would ship a egginfo with version
equals to 0.0.0.

Packages requiring a specific version would fail because that versoin would be
higher that 0.0.0.

the fix was using one of the common practices (documented via a link) of
retrieving the module version from a source file in setup.py, and update the
existing patch for disabling setuptools_scm to include this change.

[ Impact ]
(What is the impact for the user if the unblock isn't granted?)

[ Tests ]
i waited to open this request until all rdeps autopkgtests have completed

[ Risks ]
trivial fix

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing


unblock tqdm/4.57.0-2

-- System Information:
Debian Release: 10.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.6.0-1-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff --git a/debian/changelog b/debian/changelog
index ea9325b..0904f85 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+tqdm (4.57.0-2) unstable; urgency=medium
+
+  * debian/patches/dont-use-setuptools-scm.patch
+- since we disabled setuptools_scm, we need to explicly retrieve and set
+  tqdm version, so that egginfo has the right version too; Closes: #983007
+
+ -- Sandro Tosi   Fri, 05 Mar 2021 03:57:27 -0500
+
 tqdm (4.57.0-1) unstable; urgency=medium
 
   * New upstream release
diff --git a/debian/patches/dont-use-setuptools-scm.patch 
b/debian/patches/dont-use-setuptools-scm.patch
index 88aad5f..d34c346 100644
--- a/debian/patches/dont-use-setuptools-scm.patch
+++ b/debian/patches/dont-use-setuptools-scm.patch
@@ -1,11 +1,24 @@
 --- a/setup.py
 +++ b/setup.py
-@@ -13,4 +13,4 @@ if sys.argv[1].lower().strip() == 'make'
+@@ -5,6 +5,12 @@ from os import path
+ 
+ from setuptools import setup
+ 
++
++# https://packaging.python.org/guides/single-sourcing-package-version/
++version = {}
++with open('tqdm/_dist_ver.py') as fp:
++exec(fp.read(), version)
++
+ src_dir = path.abspath(path.dirname(__file__))
+ if sys.argv[1].lower().strip() == 'make':  # exec Makefile commands
+ import pymake
+@@ -13,4 +19,4 @@ if sys.argv[1].lower().strip() == 'make'
  # Stop to avoid setup.py raising non-standard command error
  sys.exit(0)
  
 -setup(use_scm_version=True)
-+setup()
++setup(version=version['__version__'])
 --- a/setup.cfg
 +++ b/setup.cfg
 @@ -74,7 +74,7 @@ classifiers =


Bug#950342: RM: volatility/2.6.1-1

2020-02-06 Thread Sandro Tosi
Control: tags -1 -moreinfo

> But it still has a reverse dependency. I think that package should get
> time drop the dependency first, don't you think (it seems to me that
> it's a meta-package that could easily do that)?

`forensics-all` is a metapackage from `src:forensics-all`, and i
thought we could ignore those?

anyhow, with this upload
https://packages.qa.debian.org/f/forensics-all/news/20200205T132048Z.html
volatility was dropped from forensics-all and now dak is clean:

```
$ ssh coccia.debian.org "dak rm -Rn -b volatility"
Will remove the following packages from unstable:

volatility |2.6.1-1 | all

Maintainer: Debian Security Tools 

--- Reason ---

--

Checking reverse dependencies...
No dependency problem found.
```

can we proceed?

Cheers,
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi



Bug#950342: RM: volatility/2.6.1-1

2020-01-31 Thread Sandro Tosi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm

Please remove volatility from testing;  volatility is the last reverse
dependency of python-openpyxl, which can then be dropped.

I've already filed an RC bug against src:volatility to keep it out of testing.

Thanks,
Sandro

-- System Information:
Debian Release: 10.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled



Bug#948474: RM: cain/1.10+dfsg-3

2020-01-08 Thread Sandro Tosi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm

cain is one of the only 2 remaining reverse dependencies of python-scipy in
testing (python-networkx is schedule for RM by ftp.d.o, and i'm working on
scikit-learn right now); while we figure out if it's worth keeping src:cain in
Debian (see #948473), can you please remove it from testing? this will simplify
the work on scipy.

Thanks,
Sandro

-- System Information:
Debian Release: 10.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled



Re: Proposal on how to proceed with Python 2 removal from bullseye

2020-01-06 Thread Sandro Tosi
On Sun, Dec 22, 2019 at 5:58 AM Simon McVittie  wrote:
>
> On Wed, 18 Dec 2019 at 01:08:11 -0500, Sandro Tosi wrote:
> > let me know if this makes sense or additional changes are required.
>
> #942941 in src:dbus-python was bumped to serious because:
> > python-dbus-tests is a module and has 0 external rdeps or not in testing
>
> Please could you give python-dbus-tests or *-tests an exception to the
> RC severity bumps, or only bump the severity if *every* Python 2 binary
> package in a source package is eligible for removal, or something?
> python-dbus still has a significant number of rdeps, and I don't want to
> support python-dbus without keeping its automated tests available.

i just implement what asked here, with also a "rollback" functionality
that will downgrade any RC bug for a source with not-leaf packages.
there's a chance some bugs which severity was raised by hand (f.e.
because a dependency package was removed) will get reverted to normal,
we'll see how it goes. the change will go live in a few minutes.

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi



Re: Proposal on how to proceed with Python 2 removal from bullseye

2019-12-17 Thread Sandro Tosi
> 1) all Python 2 removal bugs *can* be raised to RC level by the
> maintainers of the packages they belong to, but:
>
> 2) maintainers of non-key packages should carefully consider the
> backslash for their transitive reverse (normal, build and test)
> dependencies before raising the bug severity level and in my opinion
> should hold off doing that if there are many that need adaption for the
> Python 2 support removal. To be absolutely clear of my intent, if there
> is only a *very* limited set that needs adaption but they have a large
> set of reverse dependencies that is not what I mean here. The
> maintainers of the large set of reverse dependencies have a joint
> incentive to fix the issue if the maintainer of the to-be-adapted
> package(s) doesn't step up to fix the situation.
>
> 3) packages with unfixed reverse (normal, build or test) dependencies,
> that want to drop Python 2 support should first make sure their unfixed
> reverse dependencies have RC bugs themselves (but please take the
> consideration of 2 into account), stating at least something like
> "source package $foo is soon going to remove the binary $bar package on
> which the $baz package (build) depends, please fix that".
>
> To avoid problems with bug fixes that need to migrate to testing soon,
> please don't upload the Python 2 support drop immediately, but wait
> until either the reverse dependencies are fixed or the date for the
> autoremoval is near.
>
> 4) leaf packages (i.e. without normal, build or test reverse
> dependencies) that need to be adapted themselves for the Python 2
> removal can be marked as RC.
>
> 5) Please continue to use the approach used so far as well, but please
> also add checks on build dependencies.

i've modified the py2removal script as follow:

- extended the "real rdeps" concept as follow: while processing pkgA,
pkgB is a "real" reverse dependency of pkgA iff
-- pkgB is from another source package than pkgA (so python-foo-dbg
will not longer be marked as a rdep of python-foo, as ideally they
will get removed at the same time, as part of the same src:foo pkg)
-- if the pkgB is in testing (there are several packages in unstable
broken beyond repair, so even if we remove pkgA, it will still remain
broken but we can make progress on the py2removal front)
- added the check "real rdeps" == 0 both for modules and applications
(previously it was only for modules).

a test run shows only 3 additional severity bumps will happen when
re-enable, which i plan on doing with the next run (in 8~10 hours).

let me know if this makes sense or additional changes are required.

Regards,
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi



Re: Severity bump script

2019-12-08 Thread Sandro Tosi
there seems to be disagreement on how to proceed, so for the time
being i suspended the severity bump part of the py2removal tracking
script. let me know when everybody agrees on a solution, and what that
solution is, and i'll code it and re-enable.

regards,
Sandro

On Thu, Dec 5, 2019 at 6:07 AM Paul Gevers  wrote:
>
> Hi,
>
> On 03-12-2019 13:19, Matthias Klose wrote:
> > It's unfortunate that issues for some packages only get attention when the
> > severity of an issue is raised.  Following your proposal means that the 
> > issue is
> > probably ignored forever, and you don't propose a better way going forward, 
> > just
> > saying we should stop earlier.  I don't think that's the correct choice.  
> > For
> > now these seem to be single packages, so please could you name those, and 
> > we can
> > look at those with a priority?  That's at least a path that is forward 
> > looking,
> > or feel free to propose another approach better than your current proposal 
> > for
> > not getting the attention of maintainers.
>
> I guess what I'm asking for could be fulfilled by an announcement to
> d-d-a with a package list (including via which package(s) they are
> affected) attached including the standard grouping by DD. And then some
> time to react.
>
> Paul
>
> PS, my original typed reply below. After having writing it, the idea
> above emerged.
>
> My problem with the current approach is that the way that developers
> learn that they (potentially transitively) (build) depend on a Python 2
> package is by the autoremoval message. I don't think that is acceptable
> socially in the project. My proposal is to give the maintainers about
> those packages a heads up. Via a bug report may be a bit weird in cases,
> but in some cases may be the appropriate thing as the package could work
> around the (build) dependency. At least adding "affects" helps a tiny
> bit and direct e-mails to the maintainers (e.g. via the
> @packages.debian.org address will at least give them a heads
> up. Even if the RM bug is coming eventually.
>
> Again, I don't have a problem with Python 2 removal, even at the price
> of packages that don't care that their dependency is written in Python.
> I do care about proper communication. Using RC severity to trigger
> autoremoval for non-leaf packages just yet is not appropriate in the
> opinion of the release team. Even though I am well aware of the Python 2
> removal effort I can tell from personal experience (cacti) that
> receiving an autoremoval e-mail as the first sign of such a dependency
> isn't nice, that's the problem I'm having and that needs solving in my
> opinion.
>


-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi



Re: Severity bump script

2019-12-02 Thread Sandro Tosi
> You'll fix that, right? Because why would the tree stop at Python? A
> leaf package is a package without Depends/Build-Depends in Debian. (I
> appreciate it very much that you consider Recommends and
> autopkgtest-triggers as well).

so the revised logic should be:

* it's an app (package name doesnt start with 'python-' or end with -'doc')
* it has low popcorn (< 300)
* (NEW) it has "real" rdep = 0 (so the number of dependencies from
packages not from the same source pkg are 0)

is that correct or should it be something else?


-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi



Re: Severity bump script

2019-12-02 Thread Sandro Tosi
> > huh? We are not bumping any "blocked" bugs.
> > Depends/Build-Depends/Recommends/autopkgtests usage marks bug as
> > blocked. Any example of "wrong definition" please?
>
> #942999 and #936537

the blocks are only between py2removal packages, so if a package
un-related to the py2removal effort
depend/recomments/b-deps/autotest-triggers a py2removal *application*, that
is still considered a leaf package and will get its severity
raised (cfr 
https://github.com/sandrotosi/debian-tools/blob/master/py2rm_progress.py#L544-L546
); it doesnt happen with modules are we check the "real" rdeps for
those


--
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi



Bug#939989: transition: gdal

2019-10-02 Thread Sandro Tosi
Hello Emilio,

On Wed, Oct 2, 2019 at 4:57 AM Emilio Pozuelo Monfort  wrote:
> As it's been said, we need to disentangle the gdal library transition from the
> python2 removal. So either python2 support gets added back to 3.0.1 so that we
> can transition to that without the new lib getting stuck in sid, or the 
> removal
> happens before the library transition and we wait for the py2-free gdal to
> transition to testing before going ahead with gdal 3.0.1. Which given the 
> amount
> of rdeps, it seems like that could take a while and block other transitions 
> that
> will need gdal to get rebuilt and migrated to testing, so please don't do that
> until the rdeps are ready.

in case you are not aware, it was announced that even the package
currently in unstable (so unrelated to the GDAL transition) will get
its python2 package dropped:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932679#44

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi



Re: Bug#939989: transition: gdal

2019-10-01 Thread Sandro Tosi
> On Tue, Oct 01, 2019 at 05:42:56PM +0200, Sebastiaan Couwenberg wrote:
> > We shouldn't block removal of Python 2 support on badly and unmaintained
> > packages.

you can make your case to debian-python@ , but calling networkx or any
of its rdeps "badly and unmaintained packages" it's borderline
insulting. if you want to know the impact of breaking python-networkx
have a look at http://sandrotosi.me/debian/py2removal/python-networkx_2.svg
(and that's just 2 levels of dependencies, the tree is much deeper
than that)

> we should. as some people didnt respect this, piuparts is now broken in
> testing.

you're right Holger, this has happened and when i noticed, i asked the
uploader to revert and that usually happened pretty quickly (it is
easy to get over-excited and not noticing the real impact). i think
you can ask to revert the removal of whatever package broke piuparts

> i do however agree, that it doesnt make much sense to have rules if
> people can just break them.

I'm afraid that's always the case: we can upload RC buggy packages to
unstable, we can introduce regressions, and violate the Debian Policy
anytime (willingly or no) so the rule is there to say "people with
some experience on the topic thought about it and come up with this
rule you should probably follow", at least that's my take.

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi



Re: Bug#939989: transition: gdal

2019-09-17 Thread Sandro Tosi
Hello Release Team,

On Tue, Sep 10, 2019 at 3:54 PM Bas Couwenberg  wrote:
> For the Debian GIS team I'd like to transition to GDAL 3.x. This is the
> next step in the major update of the GIS stack after PROJ 6.
>
> All reverse dependencies rebuilt successfully with GDAL 3.0.1 from
> experimental as summarized below, except fiona, mysql-workbench & vtk7.
>
> The fiona issue is actually related to GDAL 3, mysql-workbench FTBFS due
> to gcc-9 & -Werror, and vtk7 hasn't been updated for PROJ 6 yet.
>
> libgdal-grass doesn't need a binNMU as the 3.0.1 version will be
> uploaded to unstable instead.

please be aware this transition also includes dropping python-gdal
from the gdal source package.  In unstable, that would currently
break:

```
Checking reverse dependencies...
# Broken Depends:
qgis: python3-qgis-common

# Broken Build-Depends:
python-networkx: python-gdal

Dependency problem found.
```

While it's true we are trying to remove python 2 from Debian
(https://wiki.debian.org/Python/2Removal), this shouldnt be done while
reverse dependencies are still present in the archive (quoting from
the previous link "NOTE: If there are reverse dependencies, you cannot
remove it yet!").

Bas was made aware of the impossible situation of removing
python-networkx (exactly due to its rdeps) in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932679#32 but that
didnt change his mind.  Dropping python-networkx would mean breaking

```
Checking reverse dependencies...
# Broken Depends:
cfflib: python-cfflib
falcon: falcon [amd64 arm64 mips64el ppc64el s390x]
hinge: hinge [amd64 arm64 mips64el ppc64el]
nipype: python-nipype
pbsuite: pbhoney
pbjelly
python-pbbanana
pdb2pqr: pdb2pqr
python-prov: python-prov
ragout: ragout
sagemath: sagemath [arm64 armhf i386 ppc64el]

# Broken Build-Depends:
cfflib: python-networkx
falcon: python-networkx (>= 1.7)
hinge: python-networkx
nipype: python-networkx (>= 1.3)
nitime: python-networkx
ragout: python-networkx (>= 2.2)
rdflib: python-networkx

Dependency problem found.
```

(and all their transitive rdeps). That seems quite a lot, and I'm not
ready to drop a package knowing others are still depending on it.

Please consider this when scheduling the gdal transition

Regards,
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi



Bug#925513: unblock: python-numpy/1:1.16.2-1

2019-03-25 Thread Sandro Tosi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package python-numpy

it looks like i missed the deadline for an automatic transition to testing by a
few hours with the latest upload of numpy, hence opening this ticket (with
attached debdiff). it's a patch release, with only bugfixes (which you can find
documented in the debdiff as part of the upstream changes).

unblock python-numpy/1:1.16.2-1

-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.14.0-3-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru python-numpy-1.16.1/debian/changelog 
python-numpy-1.16.2/debian/changelog
--- python-numpy-1.16.1/debian/changelog2019-01-31 22:21:17.0 
-0500
+++ python-numpy-1.16.2/debian/changelog2019-03-02 11:30:12.0 
-0500
@@ -1,3 +1,9 @@
+python-numpy (1:1.16.2-1) unstable; urgency=medium
+
+  * New upstream release
+
+ -- Sandro Tosi   Sat, 02 Mar 2019 11:30:12 -0500
+
 python-numpy (1:1.16.1-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru python-numpy-1.16.1/doc/changelog/1.16.2-changelog.rst 
python-numpy-1.16.2/doc/changelog/1.16.2-changelog.rst
--- python-numpy-1.16.1/doc/changelog/1.16.2-changelog.rst  1969-12-31 
19:00:00.0 -0500
+++ python-numpy-1.16.2/doc/changelog/1.16.2-changelog.rst  2019-02-26 
09:33:38.0 -0500
@@ -0,0 +1,25 @@
+
+Contributors
+
+
+A total of 5 people contributed to this release.  People with a "+" by their
+names contributed a patch for the first time.
+
+* Charles Harris
+* Eric Wieser
+* Matti Picus
+* Tyler Reddy
+* Tony LaTorre +
+
+Pull requests merged
+
+
+A total of 7 pull requests were merged for this release.
+
+* `#12909 <https://github.com/numpy/numpy/pull/12909>`__: TST: fix vmImage 
dispatch in Azure
+* `#12923 <https://github.com/numpy/numpy/pull/12923>`__: MAINT: remove 
complicated test of multiarray import failure mode
+* `#13020 <https://github.com/numpy/numpy/pull/13020>`__: BUG: fix signed zero 
behavior in npy_divmod
+* `#13026 <https://github.com/numpy/numpy/pull/13026>`__: MAINT: Add functions 
to parse shell-strings in the platform-native...
+* `#13028 <https://github.com/numpy/numpy/pull/13028>`__: BUG: Fix regression 
in parsing of F90 and F77 environment variables
+* `#13038 <https://github.com/numpy/numpy/pull/13038>`__: BUG: parse shell 
escaping in extra_compile_args and extra_link_args
+* `#13041 <https://github.com/numpy/numpy/pull/13041>`__: BLD: Windows 
absolute path DLL loading
diff -Nru python-numpy-1.16.1/doc/release/1.16.2-notes.rst 
python-numpy-1.16.2/doc/release/1.16.2-notes.rst
--- python-numpy-1.16.1/doc/release/1.16.2-notes.rst1969-12-31 
19:00:00.0 -0500
+++ python-numpy-1.16.2/doc/release/1.16.2-notes.rst2019-02-26 
09:33:38.0 -0500
@@ -0,0 +1,70 @@
+==
+NumPy 1.16.2 Release Notes
+==
+
+NumPy 1.16.2 is a quick release fixing several problems encountered on Windows.
+The Python versions supported are 2.7 and 3.5-3.7. The Windows problems
+addressed are:
+
+- DLL load problems for NumPy wheels on Windows,
+- distutils command line parsing on Windows.
+
+There is also a regression fix correcting signed zeros produced by divmod, see
+below for details.
+
+Downstream developers building this release should use Cython >= 0.29.2 and, if
+using OpenBLAS, OpenBLAS > v0.3.4.
+
+If you are installing using pip, you may encounter a problem with older
+installed versions of NumPy that pip did not delete becoming mixed with the
+current version, resulting in an ``ImportError``. That problem is particularly
+common on Debian derived distributions due to a modified pip.  The fix is to
+make sure all previous NumPy versions installed by pip have been removed. See
+`#12736 <https://github.com/numpy/numpy/issues/12736>`__ for discussion of the
+issue.
+
+
+Compatibility notes
+===
+
+Signed zero when using divmod
+-
+Starting in version 1.12.0, numpy incorrectly returned a negatively signed zero
+when using the ``divmod`` and ``floor_divide`` functions when the result was
+zero. For example::
+
+   >>> np.zeros(10)//1
+   array([-0., -0., -0., -0., -0., -0., -0., -0., -0., -0.])
+
+With this release, the result is correctly returned as a positively signed
+zero::
+
+   >>> np.zeros(10)//1
+   array([0., 0., 0., 0., 0., 0., 0

Bug#924148: unblock: python-dmidecode/3.12.2-9

2019-03-09 Thread Sandro Tosi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package python-dmidecode

this reverts completely the attempt to migrate to use symlinks for the doc
directory of the -dbg packages; i've wasted enough time on something that would
only save a handful of KBs. in doing so it fixes a FTBFS bug

Attached the debdiff

unblock python-dmidecode/3.12.2-9

-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.14.0-3-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru python-dmidecode-3.12.2/debian/changelog 
python-dmidecode-3.12.2/debian/changelog
--- python-dmidecode-3.12.2/debian/changelog2019-03-07 17:51:40.0 
-0500
+++ python-dmidecode-3.12.2/debian/changelog2019-03-09 14:49:11.0 
-0500
@@ -1,3 +1,9 @@
+python-dmidecode (3.12.2-9) unstable; urgency=medium
+
+  * revert symlink_to_dir for -dbg packages; Closes: #924007
+
+ -- Sandro Tosi   Sat, 09 Mar 2019 14:49:11 -0500
+
 python-dmidecode (3.12.2-8) unstable; urgency=medium
 
   * debian/rules
diff -Nru python-dmidecode-3.12.2/debian/python3-dmidecode-dbg.maintscript 
python-dmidecode-3.12.2/debian/python3-dmidecode-dbg.maintscript
--- python-dmidecode-3.12.2/debian/python3-dmidecode-dbg.maintscript
2019-03-07 17:51:40.0 -0500
+++ python-dmidecode-3.12.2/debian/python3-dmidecode-dbg.maintscript
2019-03-09 14:49:11.0 -0500
@@ -1 +1 @@
-dir_to_symlink /usr/share/doc/python3-dmidecode-dbg python3-dmidecode 3.12.2-8~
+symlink_to_dir /usr/share/doc/python3-dmidecode-dbg python3-dmidecode 3.12.2-9~
diff -Nru python-dmidecode-3.12.2/debian/python-dmidecode-dbg.maintscript 
python-dmidecode-3.12.2/debian/python-dmidecode-dbg.maintscript
--- python-dmidecode-3.12.2/debian/python-dmidecode-dbg.maintscript 
2019-03-07 17:51:40.0 -0500
+++ python-dmidecode-3.12.2/debian/python-dmidecode-dbg.maintscript 
2019-03-09 14:49:11.0 -0500
@@ -1 +1 @@
-dir_to_symlink /usr/share/doc/python-dmidecode-dbg python-dmidecode 3.12.2-8~
+symlink_to_dir /usr/share/doc/python-dmidecode-dbg python-dmidecode 3.12.2-9~
diff -Nru python-dmidecode-3.12.2/debian/rules 
python-dmidecode-3.12.2/debian/rules
--- python-dmidecode-3.12.2/debian/rules2019-03-07 17:51:40.0 
-0500
+++ python-dmidecode-3.12.2/debian/rules2019-03-09 14:49:11.0 
-0500
@@ -38,12 +38,7 @@
 endif
 
 override_dh_installdocs:
-   dh_installdocs -p$(P2)-dbg --link-doc=$(P2)
-   dh_installdocs -p$(P3)-dbg --link-doc=$(P3)
-   dh_installdocs -p$(P2) README doc/AUTHORS doc/changelog 
doc/README.types doc/AUTHORS.upstream doc/README.upstream
-   dh_installdocs -p$(P3) README doc/AUTHORS doc/changelog 
doc/README.types doc/AUTHORS.upstream doc/README.upstream
-   mkdir -p $(CURDIR)/debian/$(P2)-data/usr/share/doc/
-   cp -r $(CURDIR)/debian/$(P2)/usr/share/doc/$(P2) 
$(CURDIR)/debian/$(P2)-data/usr/share/doc/$(P2)-data
+   dh_installdocs -A README doc/AUTHORS doc/changelog doc/README.types 
doc/AUTHORS.upstream doc/README.upstream
 
 override_dh_strip:
 ifeq (,$(filter nostrip,$(DEB_BUILD_OPTIONS)))


Bug#923989: unblock: python-dmidecode/3.12.2-8

2019-03-07 Thread Sandro Tosi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package python-dmidecode

This upload fix the poor handling of the dir-to-symlink transition for the doc
directories

unblock python-dmidecode/3.12.2-8

-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.14.0-3-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru python-dmidecode-3.12.2/debian/changelog 
python-dmidecode-3.12.2/debian/changelog
--- python-dmidecode-3.12.2/debian/changelog2019-01-28 23:09:03.0 
-0500
+++ python-dmidecode-3.12.2/debian/changelog2019-03-07 17:51:40.0 
-0500
@@ -1,3 +1,12 @@
+python-dmidecode (3.12.2-8) unstable; urgency=medium
+
+  * debian/rules
+- remove doc/ directories, to actually use dir_to_symlink; Closes: #919442
+  * debian/*.maintscript
+- use prior-of tag at the end of the command-line
+
+ -- Sandro Tosi   Thu, 07 Mar 2019 17:51:40 -0500
+
 python-dmidecode (3.12.2-7) unstable; urgency=medium
 
   * debian/*.maintscript
diff -Nru python-dmidecode-3.12.2/debian/python3-dmidecode-dbg.maintscript 
python-dmidecode-3.12.2/debian/python3-dmidecode-dbg.maintscript
--- python-dmidecode-3.12.2/debian/python3-dmidecode-dbg.maintscript
2019-01-28 23:09:03.0 -0500
+++ python-dmidecode-3.12.2/debian/python3-dmidecode-dbg.maintscript
2019-03-07 17:51:40.0 -0500
@@ -1 +1 @@
-dir_to_symlink /usr/share/doc/python3-dmidecode-dbg python3-dmidecode
+dir_to_symlink /usr/share/doc/python3-dmidecode-dbg python3-dmidecode 3.12.2-8~
diff -Nru python-dmidecode-3.12.2/debian/python-dmidecode-dbg.maintscript 
python-dmidecode-3.12.2/debian/python-dmidecode-dbg.maintscript
--- python-dmidecode-3.12.2/debian/python-dmidecode-dbg.maintscript 
2019-01-28 23:09:03.0 -0500
+++ python-dmidecode-3.12.2/debian/python-dmidecode-dbg.maintscript 
2019-03-07 17:51:40.0 -0500
@@ -1 +1 @@
-dir_to_symlink /usr/share/doc/python-dmidecode-dbg python-dmidecode
+dir_to_symlink /usr/share/doc/python-dmidecode-dbg python-dmidecode 3.12.2-8~
diff -Nru python-dmidecode-3.12.2/debian/rules 
python-dmidecode-3.12.2/debian/rules
--- python-dmidecode-3.12.2/debian/rules2019-01-28 23:09:03.0 
-0500
+++ python-dmidecode-3.12.2/debian/rules2019-03-07 17:51:40.0 
-0500
@@ -38,9 +38,12 @@
 endif
 
 override_dh_installdocs:
-   dh_installdocs -A README doc/AUTHORS doc/changelog doc/README.types 
doc/AUTHORS.upstream doc/README.upstream
dh_installdocs -p$(P2)-dbg --link-doc=$(P2)
dh_installdocs -p$(P3)-dbg --link-doc=$(P3)
+   dh_installdocs -p$(P2) README doc/AUTHORS doc/changelog 
doc/README.types doc/AUTHORS.upstream doc/README.upstream
+   dh_installdocs -p$(P3) README doc/AUTHORS doc/changelog 
doc/README.types doc/AUTHORS.upstream doc/README.upstream
+   mkdir -p $(CURDIR)/debian/$(P2)-data/usr/share/doc/
+   cp -r $(CURDIR)/debian/$(P2)/usr/share/doc/$(P2) 
$(CURDIR)/debian/$(P2)-data/usr/share/doc/$(P2)-data
 
 override_dh_strip:
 ifeq (,$(filter nostrip,$(DEB_BUILD_OPTIONS)))


Bug#922194: unblock: matplotlib2/2.2.3-6

2019-02-12 Thread Sandro Tosi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package matplotlib2

the fix in unstable addresses a DeprecationWarning (due to numpy 1.16) that
caused FTBFS on other packages + it allows matplotlib2 to build with sphinx/1.8

attached is the debdiff, the package -although just uploaded- is already built
successfully on all release archs (except for mips, for now).

unblock matplotlib2/2.2.3-6

-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.14.0-3-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru matplotlib2-2.2.3/debian/changelog matplotlib2-2.2.3/debian/changelog
--- matplotlib2-2.2.3/debian/changelog  2018-12-28 11:46:51.0 -0500
+++ matplotlib2-2.2.3/debian/changelog  2019-02-12 17:51:04.0 -0500
@@ -1,3 +1,18 @@
+matplotlib2 (2.2.3-6) unstable; urgency=medium
+
+  * debian/control
+- update Vcs-* fields
+  * debian/patches/bts918819-numpy-deprecates-asscalar-gh12508.patch
+- fix DeprecationWarnings with Numpy 1.16; Closes: #918819
+  * debian/patches/bts918896-doc-backports-for-2.2.x-gh13258.patch
+- import upstream doc backports patches for 2.2.x branch; Closes: #918896
+  * debian/control
+- bump Standards-Version to 4.3.0 (no changes needed)
+  * debian/copyright
+- extend packaging copyright years
+
+ -- Sandro Tosi   Tue, 12 Feb 2019 17:51:04 -0500
+
 matplotlib2 (2.2.3-5) unstable; urgency=medium
 
   * install the default matplotlib config file at /etc/matplotlibrc2;
diff -Nru matplotlib2-2.2.3/debian/control matplotlib2-2.2.3/debian/control
--- matplotlib2-2.2.3/debian/control2018-12-28 11:46:51.0 -0500
+++ matplotlib2-2.2.3/debian/control2019-02-12 17:51:04.0 -0500
@@ -60,10 +60,10 @@
xvfb,
zlib1g-dev
 XS-Python-Version: all
-Standards-Version: 4.2.1
+Standards-Version: 4.3.0
 Homepage: http://matplotlib.org/
-Vcs-Git: https://salsa.debian.org/python-team/modules/matplotlib.git
-Vcs-Browser: https://salsa.debian.org/python-team/modules/matplotlib
+Vcs-Git: https://salsa.debian.org/python-team/modules/matplotlib2.git
+Vcs-Browser: https://salsa.debian.org/python-team/modules/matplotlib2
 
 Package: python-matplotlib
 Architecture: any
diff -Nru matplotlib2-2.2.3/debian/copyright matplotlib2-2.2.3/debian/copyright
--- matplotlib2-2.2.3/debian/copyright  2018-12-28 11:46:51.0 -0500
+++ matplotlib2-2.2.3/debian/copyright  2019-02-12 17:51:04.0 -0500
@@ -62,7 +62,7 @@
  Agreement.
 
 Files: debian/*
-Copyright: Copyright (C) 2008-2018 Sandro Tosi 
+Copyright: Copyright (C) 2008-2019 Sandro Tosi 
 License: same as upstream
 
 Files: lib/matplotlib/backends/backend_wxagg.py
diff -Nru 
matplotlib2-2.2.3/debian/patches/bts918819-numpy-deprecates-asscalar-gh12508.patch
 
matplotlib2-2.2.3/debian/patches/bts918819-numpy-deprecates-asscalar-gh12508.patch
--- 
matplotlib2-2.2.3/debian/patches/bts918819-numpy-deprecates-asscalar-gh12508.patch
  1969-12-31 19:00:00.0 -0500
+++ 
matplotlib2-2.2.3/debian/patches/bts918819-numpy-deprecates-asscalar-gh12508.patch
  2019-02-12 17:51:04.0 -0500
@@ -0,0 +1,26 @@
+--- a/lib/matplotlib/colors.py
 b/lib/matplotlib/colors.py
+@@ -98,7 +98,7 @@ def _sanitize_extrema(ex):
+ if ex is None:
+ return ex
+ try:
+-ret = np.asscalar(ex)
++ret = ex.item()
+ except AttributeError:
+ ret = float(ex)
+ return ret
+--- a/lib/matplotlib/image.py
 b/lib/matplotlib/image.py
+@@ -421,9 +421,9 @@ class _ImageBase(martist.Artist, cm.Scal
+ 
+ A_scaled -= a_min
+ # a_min and a_max might be ndarray subclasses so use
+-# asscalar to avoid errors
+-a_min = np.asscalar(a_min.astype(scaled_dtype))
+-a_max = np.asscalar(a_max.astype(scaled_dtype))
++# item to avoid errors
++a_min = a_min.astype(scaled_dtype).item()
++a_max = a_max.astype(scaled_dtype).item()
+ 
+ if a_min != a_max:
+ A_scaled /= ((a_max - a_min) / 0.8)
diff -Nru 
matplotlib2-2.2.3/debian/patches/bts918896-doc-backports-for-2.2.x-gh13258.patch
 
matplotlib2-2.2.3/debian/patches/bts918896-doc-backports-for-2.2.x-gh13258.patch
--- 
matplotlib2-2.2.3/debian/patches/bts918896-doc-backports-for-2.2.x-gh13258.patch
1969-12-31 19:00:00.0 -0500
+++ 
matplotlib2-2.2.3/debian/patches/bts918896-doc-backports-for-2.2.x-gh13258.patch
2019-02-12 17:51

Re: Bug#887150: reportbug: stable-pu request: don't ask whether the current version in stable is the correct one

2019-01-01 Thread Sandro Tosi
Hey Release Team, are you ok with the change described below? thanks!

On Tue, Jan 1, 2019 at 7:49 PM Andreas Beckmann  wrote:
>
> On 2019-01-02 01:29, Sandro Tosi wrote:
> >> when filing an (old)stable-pu request, reportbug asks whether the
> >
> > this is for `release.debian.org` correct?
>
> Yes.
>
> >> current version in (old)stable is the proper version. Obviously it never
> >> is, so this question is useless and should be omitted - or the most
> >> likely (old)stable increment version could be guessed and presented
> >> instead.
> >>
> >> If the version lookup is retained, it should also consider
> >> (old)stable-proposed-updates, which might already have an update queued.
> >
> > just to make it sure, do you want to remove `Latest version seems to
> > be XXX, is this the proper one ? [Y|n|?]?` question and make `Please
> > enter the version of the package: ` mandatory, correct?
>
> Exactly.
>
>
> Andreas



-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi



Re: Bug#862801: reportbug should stop offering wheezy-pu

2017-07-14 Thread Sandro Tosi
On Fri, Jul 14, 2017 at 1:27 PM, Adam D. Barratt
<a...@adam-barratt.org.uk> wrote:
> On Sat, 2017-05-27 at 09:13 +0200, Julien Cristau wrote:
>> On Wed, May 17, 2017 at 09:50:17 -0400, Sandro Tosi wrote:
>>
>> > > $ reportbug release.debian.org
>> > > ...
>> > > What sort of request is this? (If none of these things mean anything to 
>> > > you, or you are trying to report a bug in an existing package, please
>> > > press Enter to exit reportbug.)
> [...]
>> > > wheezy is now maintained by the LTS team, and there are no longer
>> > > any wheezy-pu updates throught the release team.
>> >
>> > In principle it makes sense to me, but given this is RT-land, i'd
>> > rather them ack it explicitly (added in CC)
>> >
>> > Release team: do you want to add a `stretch-pu` at the same time, so
>> > that we'll have a reportbug in stretch with that option too? (or is it
>> > too early?)
>> >
>> Yes, might as well.
>
> It looks like that never happened? #862801 is closed, but the only
> relevant-looking commit I can find in reportbug's git repository updates
> the codename to suite mapping list, but not the release.d.o bug handling
> code.

i tested it and it seemed to work, and now when i install reportbug
7.1.7 and try `reportbug r.d.o` i got this menu

```
1 binnmu  binNMU requests
2 britney testing migration script bugs
3 jessie-pu   jessie proposed updates requests
4 other   None of the other options
5 rm  Stable/Testing removal requests
6 stretch-pu  stretch proposed updates requests
7 transition  transition tracking
8 unblock unblock requests
```

which generates this templated report:

```
Subject: stretch-pu: package reportbug/7.1.7
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: pu
Tags: stretch
Severity: normal

(please explain the reason for this update here)
```

is this not correct?

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi



Bug#863523: unblock: (preapproval) matplotlib/2.0.2-1

2017-06-02 Thread Sandro Tosi
> Upstream has recently released matplotlib 2.0.2 which fixes only
> critical/important bugs in the 2.0.x branch.
>
> the high-level description of the changes is at [0] and also here below:
>
> [0] https://github.com/matplotlib/matplotlib/releases
>
> 2.0.0 -> 2.0.1
> ```
> API
>
>  - Do not clip the linewidth used for dash pattern scaling.  This is
>an API change, but is a major improvement.
>  - Deprecate 'vega' color names in favor of 'tab'.
>
> Bug Fixes
>
>  - Hatching color follows edge color again.
>  - Fixes a critical bug with masked images.
>  - Improved high-dpi support for Qt5.
>  - Log ticking no never skip minor ticks
>  - Do not skip points surrounded by nan/inf in vector outputs.
> ```
>
> 2.0.1 -> 2.0.2
>
> ```
> Critical bug fixes for 2.0.1
>
>  - fixed Qt4 support
>  - fixed LogFormatter
>  - fixed hatched artists in legends
>  - fixed segfault with large images
>
> ```
>
> I know it's late in the release, but 2.0.0 was a big milestone for upstream, 
> so
> some adjustments/bug fixes were expected. matplotlib is continuosly tested via
> travis[1] and you can see there how the 2.0.x branch is passing the upstream
> very extensive test suite.
>
> [1] https://travis-ci.org/matplotlib/matplotlib/branches
>
> An upsteam source diff is attached, filtering out doc/tests/examples; a full
> diff is available at [2] or via git.
>
> [2] 
> https://anonscm.debian.org/cgit/python-modules/packages/matplotlib.git/commit/?h=upstream=4816639bd3468d3e9f9cc9fed76324fdc8e0c9b6
>
> let me know if it's possible for me to proceed with an upload.

Any word on this?

Thanks,
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi



Bug#863923: unblock: phatch/0.2.7.1-5

2017-06-01 Thread Sandro Tosi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package phatch

This upload fixes the pending RC bug; the package is currently marked
will-remove but it's a really nice utility (and the fix is a one-liner) that'd
be a shame if it wont be part of stretch.

a source debdiff is attached

unblock phatch/0.2.7.1-5

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru phatch-0.2.7.1/debian/changelog phatch-0.2.7.1/debian/changelog
--- phatch-0.2.7.1/debian/changelog 2016-08-17 14:44:12.0 -0400
+++ phatch-0.2.7.1/debian/changelog 2017-06-01 20:01:28.0 -0400
@@ -1,3 +1,11 @@
+phatch (0.2.7.1-5) unstable; urgency=medium
+
+  * Team upload.
+  * debian/patches/bts823796.patch
+- fix compatibility with Pillow 4.x; patch by Steve Cotton; Closes: #823796
+
+ -- Sandro Tosi <mo...@debian.org>  Thu, 01 Jun 2017 20:01:28 -0400
+
 phatch (0.2.7.1-4) unstable; urgency=medium
 
   [ Mateusz Łukasik ]
diff -Nru phatch-0.2.7.1/debian/patches/bts823796.patch 
phatch-0.2.7.1/debian/patches/bts823796.patch
--- phatch-0.2.7.1/debian/patches/bts823796.patch   1969-12-31 
19:00:00.0 -0500
+++ phatch-0.2.7.1/debian/patches/bts823796.patch   2017-06-01 
20:00:07.0 -0400
@@ -0,0 +1,33 @@
+From: Steve Cotton <st...@octalot.co.uk>
+Date: Sat, 27 May 2017 01:32:21 +0200
+Subject: [PATCH] Convert images' wx.Size object to a tuple for the PIL library
+
+The wxPython library wraps image sizes in a wx.Size object, a class
+which provides the __len__ and accessor methods expected for a tuple.
+There's been a breaking change to the PIL library, which now
+explicitly checks the type of the size passed to it, and rejects
+anything which is not a tuple or a list.
+
+This patch adds a call to wx.Size.Get(), which returns the size as a
+tuple.
+
+Bug-Debian: https://bugs.debian.org/823796
+
+PIL library change: 
https://github.com/python-pillow/Pillow/commit/445451c0b9347b50e0f603db33f196e207de470d
+---
+ phatch/lib/pyWx/wxPil.py | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/phatch/lib/pyWx/wxPil.py b/phatch/lib/pyWx/wxPil.py
+index cf8c940..be73074 100644
+--- a/phatch/lib/pyWx/wxPil.py
 b/phatch/lib/pyWx/wxPil.py
+@@ -41,7 +41,7 @@ def pil_wxBitmap(image):
+ 
+ 
+ def wxImage_pil(wx_image):
+-size = wx_image.GetSize()
++size = wx_image.GetSize().Get()
+ image = Image.new('RGB', size)
+ image.frombytes(wx_image.GetData())
+ if wx_image.HasAlpha():
diff -Nru phatch-0.2.7.1/debian/patches/series 
phatch-0.2.7.1/debian/patches/series
--- phatch-0.2.7.1/debian/patches/series2016-08-10 02:36:33.0 
-0400
+++ phatch-0.2.7.1/debian/patches/series2017-06-01 20:00:07.0 
-0400
@@ -2,3 +2,4 @@
 pyexiv2.patch
 wxpy3.0-compat.patch
 fix-loading.patch
+bts823796.patch


Bug#863660: unblock: reportbug/7.1.7

2017-05-29 Thread Sandro Tosi
  fix for #859274
+  * bin/reportbug
+- fix error formatting when printing the error for draft directory
+  non-existing; patch by Gaetano Guerriero; Closes: #816375
+  * doc/README.source
+- update README.source to the current source layout; Closes: #827002
+  * debian/copyright
+- switch the Format field to the URL in the packaging-manuals
+
+ -- Sandro Tosi <mo...@debian.org>  Mon, 29 May 2017 16:00:17 -0400
+
 reportbug (7.1.6) unstable; urgency=medium
 
   * reportbug/utils.py
diff -Nru reportbug-7.1.6/debian/control reportbug-7.1.7/debian/control
--- reportbug-7.1.6/debian/control  2017-04-18 21:12:02.0 -0400
+++ reportbug-7.1.7/debian/control  2017-05-29 16:00:17.0 -0400
@@ -2,18 +2,18 @@
 Section: utils
 Priority: standard
 Maintainer: Reportbug Maintainers <reportbug-ma...@lists.alioth.debian.org>
-Uploaders: Sandro Tosi <mo...@debian.org>, Chris Lawrence <lawre...@debian.org>
+Uploaders: Sandro Tosi <mo...@debian.org>
 Standards-Version: 3.9.8
 Build-Depends: debhelper (>= 9), python3, dh-python
 Build-Depends-Indep: python3-nose, python3-setuptools, python3-mock
-Vcs-Git: git://anonscm.debian.org/reportbug/reportbug.git
-Vcs-Browser: http://anonscm.debian.org/gitweb/?p=reportbug/reportbug.git
+Vcs-Git: https://anonscm.debian.org/git/reportbug/reportbug.git
+Vcs-Browser: https://anonscm.debian.org/cgit/reportbug/reportbug.git
 Homepage: http://alioth.debian.org/projects/reportbug/
 
 Package: reportbug
 Architecture: all
 Depends: ${misc:Depends}, ${python3:Depends}, apt, python3-reportbug (= 
${source:Version})
-Suggests: postfix | exim4 | mail-transport-agent, gnupg | pgp, debconf-utils 
(>> 1.1.0), debsums (>= 2.0.47), file (>> 1.30), dlocate, python3-urwid, 
python3-gi, python3-gi-cairo, gir1.2-gtk-3.0, gir1.2-vte-2.91, 
python3-gtkspellcheck, xdg-utils, emacs23-bin-common | emacs24-bin-common, 
claws-mail (>= 3.8.0)
+Suggests: postfix | exim4 | mail-transport-agent, gnupg | pgp, debconf-utils 
(>> 1.1.0), debsums (>= 2.0.47), file (>> 1.30), dlocate, python3-urwid, 
python3-gi, python3-gi-cairo, gir1.2-gtk-3.0, gir1.2-vte-2.91, 
python3-gtkspellcheck, xdg-utils, emacs24-bin-common | emacs25-bin-common, 
claws-mail (>= 3.8.0)
 Description: reports bugs in the Debian distribution
  reportbug is a tool designed to make the reporting of bugs in Debian
  and derived distributions relatively painless.  Its features include:
diff -Nru reportbug-7.1.6/debian/copyright reportbug-7.1.7/debian/copyright
--- reportbug-7.1.6/debian/copyright2017-04-18 21:12:02.0 -0400
+++ reportbug-7.1.7/debian/copyright2017-05-29 16:00:17.0 -0400
@@ -1,4 +1,4 @@
-Format-Specification: http://wiki.debian.org/Proposals/CopyrightFormat
+Format-Specification: 
https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
 Upstream-Author: Chris Lawrence <lawre...@debian.org>
 Upstream-Author: Sandro Tosi <mo...@debian.org>
 Packaged-By: Chris Lawrence <lawre...@debian.org>
diff -Nru reportbug-7.1.6/debian/desktop reportbug-7.1.7/debian/desktop
--- reportbug-7.1.6/debian/desktop  2017-04-18 21:12:02.0 -0400
+++ reportbug-7.1.7/debian/desktop  2017-05-29 16:00:17.0 -0400
@@ -1,14 +1,18 @@
 [Desktop Entry]
 Type=Application
 Name=Reportbug
+Name[da]=Reportbug
 Name[ru]=Reportbug
 Name[zh_CN]=报告漏洞
 Comment=Report bugs to the Debian BTS
+Comment[da]=Rapportér fejl til Debian fejlrapporteringssystem
 Comment[ru]=Создание и отправка отчёта об ошибке в Debian BTS
 Comment[zh_CN]=向 Debian 缺陷跟踪系统报告漏洞
 GenericName=Debian bug reporting tool
+GenericName[da]=Debian fejlrapporteringsværktøj
 GenericName[ru]=Отчёт об ошибке Reportbug
 GenericName[zh_CN]=Debian 缺陷报告工具
+X-GNOME-FullName[da]=Debian fejlrapporteringsværktøj
 X-GNOME-FullName[ru]=Отчёт об ошибке Reportbug
 X-GNOME-FullName[zh_CN]=Debian 缺陷报告工具
 Icon=debian-swirl
@@ -16,4 +20,5 @@
 Exec=reportbug --exit-prompt --ui gtk2
 Categories=System;
 Keywords=Debian;Bug;Bugs;BTS;
+Keywords[da]=Debian;Bug;Bugs;BTS;Fejlrapporteringssystem;Fejl;
 Keywords[zh_CN]=漏洞;报告;缺陷;
diff -Nru reportbug-7.1.6/doc/README.source reportbug-7.1.7/doc/README.source
--- reportbug-7.1.6/doc/README.source   2017-04-18 21:12:02.0 -0400
+++ reportbug-7.1.7/doc/README.source   2017-05-29 16:00:17.0 -0400
@@ -5,7 +5,7 @@
 
 * Top level
 
-  * Manual pages.
+  * Installation tools
 
 * Debian packaging
 
@@ -25,18 +25,16 @@
 * `Unit testing framework`_
 
   * ``test/`` contains the unit test suite. Unit test modules are
-discovered and run using the ``nosetests`` program, and are named
+discovered and run using the ``nosetests3`` program, and are named
 as ``test_*.py``.
 
-* Internal checking framework
+* Documentation
 
-  * ``checks/`` contains various scripts that ensure reportbug's
-internals are up-to-date with the Debian BTS.
+  * ``doc/`` contains documentation for both users and developer

Bug#863573: unblock: diamond/4.0.515-4

2017-05-29 Thread Sandro Tosi
On Mon, May 29, 2017 at 8:20 AM, Jonathan Wiltshire <j...@debian.org> wrote:
> Control: tag -1 moreinfo
>
> On Sun, May 28, 2017 at 03:58:13PM -0400, Sandro Tosi wrote:
>> This upload improves (even if only slightly, as a proper solution is still 
>> being
>> worked on by upstream) the stop/restart time of diamond, by setting the 
>> systemd
>> killmode to mixed.
>
> I'm not sure how comfortable I am about this. Is the change to KillMode
> upstream advice?

sorry for not reporting it first, there is a long discussion with
upstream at https://github.com/python-diamond/Diamond/issues/595 -
their initial solution was to change the internal process management
logic and then use KillMode=process but paravoid had better result
with `mixed` without changing any code (since that procs mgmt change
still isnt 100% completed)

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi



Bug#863573: unblock: diamond/4.0.515-4

2017-05-28 Thread Sandro Tosi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package diamond

This upload improves (even if only slightly, as a proper solution is still being
worked on by upstream) the stop/restart time of diamond, by setting the systemd
killmode to mixed.

A source debdiff is attached

unblock diamond/4.0.515-4

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64
 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru diamond-4.0.515/debian/changelog diamond-4.0.515/debian/changelog
--- diamond-4.0.515/debian/changelog2017-01-22 17:28:37.0 -0500
+++ diamond-4.0.515/debian/changelog2017-05-28 15:48:29.0 -0400
@@ -1,3 +1,10 @@
+diamond (4.0.515-4) unstable; urgency=medium
+
+  * debian/diamond.service
+- set KillMode to `mixed`; Closes: #854842
+
+ -- Sandro Tosi <mo...@debian.org>  Sun, 28 May 2017 15:48:29 -0400
+
 diamond (4.0.515-3) unstable; urgency=medium
 
   * debian/control
diff -Nru diamond-4.0.515/debian/diamond.service 
diamond-4.0.515/debian/diamond.service
--- diamond-4.0.515/debian/diamond.service  2016-02-16 09:29:38.0 
-0500
+++ diamond-4.0.515/debian/diamond.service  2017-05-28 15:48:15.0 
-0400
@@ -4,6 +4,7 @@
 [Service]
 ExecStart=/usr/bin/python /usr/bin/diamond --log-stdout --foreground
 Restart=on-abort
+KillMode=mixed
 
 [Install]
 WantedBy=multi-user.target


Bug#863522: unblock: python-numpy/1:1.12.1-3

2017-05-27 Thread Sandro Tosi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package python-numpy

This upload fixes a bug when using numpy.abs() on numpy.nan on some
architectures; the bug is minor, but a user noticed nonetheless, the patch comes
directly from upstream and it's just a one-liner with extensive tests.

Source debdiff is attached

unblock python-numpy/1:1.12.1-3

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64
 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru python-numpy-1.12.1/debian/changelog 
python-numpy-1.12.1/debian/changelog
--- python-numpy-1.12.1/debian/changelog2017-04-05 06:26:43.0 
-0400
+++ python-numpy-1.12.1/debian/changelog2017-05-27 19:44:59.0 
-0400
@@ -1,3 +1,10 @@
+python-numpy (1:1.12.1-3) unstable; urgency=medium
+
+  * debian/patches/0007-BUG-Don-t-signal-FP-exceptions-in-np.absolute.patch
+- fix RuntimeWarning on numpy.abs(numpy.nan) on some archs; Closes: #863192
+
+ -- Sandro Tosi <mo...@debian.org>  Sat, 27 May 2017 19:44:59 -0400
+
 python-numpy (1:1.12.1-2) unstable; urgency=medium
 
   * Team upload
diff -Nru python-numpy-1.12.1/debian/.git-dpm 
python-numpy-1.12.1/debian/.git-dpm
--- python-numpy-1.12.1/debian/.git-dpm 2017-04-04 12:49:56.0 -0400
+++ python-numpy-1.12.1/debian/.git-dpm 2017-05-27 19:44:59.0 -0400
@@ -1,6 +1,6 @@
 # see git-dpm(1) from git-dpm package
-4b26915f32eec3afa476d678bc7831ab7b1899c1
-4b26915f32eec3afa476d678bc7831ab7b1899c1
+285b463e037cd9aeaf37ccc90ccf3349cc84b88a
+285b463e037cd9aeaf37ccc90ccf3349cc84b88a
 db9ad0d21c51a5a4983387c232c00bd6f844e406
 db9ad0d21c51a5a4983387c232c00bd6f844e406
 python-numpy_1.12.1.orig.tar.gz
diff -Nru 
python-numpy-1.12.1/debian/patches/0007-BUG-Don-t-signal-FP-exceptions-in-np.absolute.patch
 
python-numpy-1.12.1/debian/patches/0007-BUG-Don-t-signal-FP-exceptions-in-np.absolute.patch
--- 
python-numpy-1.12.1/debian/patches/0007-BUG-Don-t-signal-FP-exceptions-in-np.absolute.patch
 1969-12-31 19:00:00.0 -0500
+++ 
python-numpy-1.12.1/debian/patches/0007-BUG-Don-t-signal-FP-exceptions-in-np.absolute.patch
 2017-05-27 19:44:59.0 -0400
@@ -0,0 +1,89 @@
+From 285b463e037cd9aeaf37ccc90ccf3349cc84b88a Mon Sep 17 00:00:00 2001
+From: James Cowgill <james...@cowgill.org.uk>
+Date: Tue, 7 Mar 2017 11:39:01 +
+Subject: BUG: Don't signal FP exceptions in np.absolute
+
+Fixes #8686
+
+This PR centers around this piece of code in 
`numpy/core/src/umath/loops.c.src`:
+```c
+UNARY_LOOP {
+const @type@ in1 = *(@type@ *)ip1;
+const @type@ tmp = in1 > 0 ? in1 : -in1;
+/* add 0 to clear -0.0 */
+*((@type@ *)op1) = tmp + 0;
+}
+```
+
+If in1 is `NaN`, the C99 standard requires that the comparison `in1 > 0`
+signals `FE_INVALID`, but the usual semantics for the absolute function are
+that no FP exceptions should be generated (eg compare to C `fabs` and Python
+`abs`). This was probably never noticed due to a bug in GCC x86 where all
+floating point comparisons do not signal exceptions, however Clang on x86 and
+GCC on other architectures (including ARM and MIPS) do signal an FP exception
+here.
+
+Fix by clearing the floating point exceptions after the loop has
+finished. The alternative of rewriting the loop to use `npy_fabs`
+instead would also work but has performance issues because that function
+is not inlined. The `test_abs_neg_blocked` is adjusted not to ignore
+`FE_INVALID` errors because now both absolute and negate should never
+produce an FP exceptions.
+---
+ numpy/core/src/umath/loops.c.src |  1 +
+ numpy/core/tests/test_umath.py   | 30 ++
+ 2 files changed, 15 insertions(+), 16 deletions(-)
+
+diff --git a/numpy/core/src/umath/loops.c.src 
b/numpy/core/src/umath/loops.c.src
+index 3c11908..7e683ab 100644
+--- a/numpy/core/src/umath/loops.c.src
 b/numpy/core/src/umath/loops.c.src
+@@ -1840,6 +1840,7 @@ NPY_NO_EXPORT void
+ *((@type@ *)op1) = tmp + 0;
+ }
+ }
++npy_clear_floatstatus();
+ }
+ 
+ NPY_NO_EXPORT void
+diff --git a/numpy/core/tests/test_umath.py b/numpy/core/tests/test_umath.py
+index 6fea832..fad75cd 100644
+--- a/numpy/core/tests/test_umath.py
 b/numpy/core/tests/test_umath.py
+@@ -1226,22 +1226,20 @@ class TestAbsoluteNegative(TestCase):
+ np.negative(inp, out=out)
+ assert_equal(out, tgt, err_msg=msg)
+ 
+-# will throw invalid flag depending on compiler optimizations
+-with np.errstate(invalid='ignore'):
+-for v in [np.nan, -np.inf, np.inf]:
+-for i in range(inp.size):
+-d = 

Bug#861580: (pre-approval) unblock: mysql-connector-python/2.1.6

2017-05-27 Thread Sandro Tosi
Control: tags -1 -moreinfo

On Sat, May 27, 2017 at 4:55 PM, Ivo De Decker  wrote:
> Any news on the upload?

2.1.6 has just been uploaded, apologies for the delay

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi



Re: Bug#862801: reportbug should stop offering wheezy-pu

2017-05-17 Thread Sandro Tosi
> $ reportbug release.debian.org
> ...
> What sort of request is this? (If none of these things mean anything to you, 
> or you are trying to report a bug in an existing package, please
> press Enter to exit reportbug.)
>
> 1 binnmu  binNMU requests
> 2 britney testing migration script bugs
> 3 jessie-pu   jessie proposed updates requests
> 4 other   None of the other options
> 5 rm  Stable/Testing removal requests
> 6 transition  transition tracking
> 7 unblock unblock requests
> 8 wheezy-pu   wheezy proposed updates requests
>
> Choose the request type:
>
>
> wheezy is now maintained by the LTS team, and there are no longer
> any wheezy-pu updates throught the release team.

In principle it makes sense to me, but given this is RT-land, i'd
rather them ack it explicitly (added in CC)

Release team: do you want to add a `stretch-pu` at the same time, so
that we'll have a reportbug in stretch with that option too? (or is it
too early?)

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi



Bug#861580: (pre-approval) unblock: mysql-connector-python/2.1.6

2017-05-14 Thread Sandro Tosi
> NOTE: the test suite contains certificates that expire in 2018.  If that
> causes test failures, then that is an RC bug (as it would mean we would
> be unable to compile mysql-connector-python in stretch before its EOL).
> AFAICT, said problem would also exists in the current version (except
> the expiry reads 2017 instead).
>   Please consider replacing the certificates with once that can survive
> stretch + stretch-lts's life-time.

that's kinda tricky: what is the lifetime for stretch + stretch-lts?
:) should i guess (inferring from previous releases), do you want to
give me a date until making those certs valid, something else?

As of now tests failure wont make the build fail, so --if that's ok
with the RT-- i may continue with keeping those certs as upstream
released them.

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi



Bug#861580: (pre-approval) unblock: mysql-connector-python/2.1.6

2017-04-30 Thread Sandro Tosi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Hello,
BTS 861511 was reported yesterday against mysql-connector-python stating the new
upstream version (2.1.6) fixes CVE-2017-3590.

The upstream versions diff (attached) is quite important, so i would understand
if you decide not to accept a potential upload of this new version aiming for an
unblock to strech, but i would still like you to have a look and decide on it.

Thanks,
Sandro

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64
 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff --git a/CHANGES.txt b/CHANGES.txt
index 18112d1..6e2c797 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -3,11 +3,23 @@ MySQL Connector/Python 2.1 - Release Notes & Changes
 
 
 MySQL Connector/Python
-Copyright (c) 2009, 2016, Oracle and/or its affiliates. All rights reserved.
+Copyright (c) 2009, 2017, Oracle and/or its affiliates. All rights reserved.
 
 Full release notes:
  http://dev.mysql.com/doc/relnotes/connector-python/en/
 
+v2.1.6
+==
+
+- BUG#25726671: Fix compatibility issues with the latest Django versions
+- BUG#25558885: Set default connection timeout to pure connector/python
+- BUG#25397650: Verify server certificate only if ssl_verify_cert is True
+- BUG#25589496: Don't convert to unicode if non-ascii data is present
+- BUG#25383644: Add connection back to pool on exception
+- BUG#22476689: Importing world.sql fails with cext enabled
+- BUG#20736339: Expect multiple include directories from mysql_config
+- BUG#19685386: C extension tests are failing using MySQL 5.7.4
+
 v2.1.5
 ==
 
diff --git a/PKG-INFO b/PKG-INFO
index 4af4d6f..9ab448d 100644
--- a/PKG-INFO
+++ b/PKG-INFO
@@ -1,6 +1,6 @@
 Metadata-Version: 1.0
 Name: mysql-connector-python
-Version: 2.1.5
+Version: 2.1.6
 Summary: MySQL driver written in Python
 Home-page: http://dev.mysql.com/doc/connector-python/en/index.html
 Author: Oracle and/or its affiliates
@@ -27,6 +27,8 @@ Classifier: Programming Language :: Python :: 3
 Classifier: Programming Language :: Python :: 3.1
 Classifier: Programming Language :: Python :: 3.2
 Classifier: Programming Language :: Python :: 3.3
+Classifier: Programming Language :: Python :: 3.4
+Classifier: Programming Language :: Python :: 3.5
 Classifier: Topic :: Database
 Classifier: Topic :: Software Development
 Classifier: Topic :: Software Development :: Libraries :: Application 
Frameworks
diff --git a/README.txt b/README.txt
index 773af0b..46cce18 100644
--- a/README.txt
+++ b/README.txt
@@ -3,7 +3,7 @@ MySQL Connector/Python 2.1
 ==
 
 MySQL Connector/Python
-Copyright (c) 2009, 2016, Oracle and/or its affiliates. All rights reserved.
+Copyright (c) 2009, 2017, Oracle and/or its affiliates. All rights reserved.
 
 License information can be found in the LICENSE.txt file.
 
@@ -28,7 +28,7 @@ doubt, this particular copy of the software is released
 under the version 2 of the GNU General Public License.
 MySQL Connector/Python is brought to you by Oracle.
 
-Copyright (c) 2011, 2016, Oracle and/or its affiliates. All rights reserved.
+Copyright (c) 2011, 2017, Oracle and/or its affiliates. All rights reserved.
 
 License information can be found in the LICENSE.txt file.
 
diff --git a/lib/cpy_distutils.py b/lib/cpy_distutils.py
index e944ce6..04741ea 100644
--- a/lib/cpy_distutils.py
+++ b/lib/cpy_distutils.py
@@ -1,5 +1,5 @@
 # MySQL Connector/Python - MySQL driver written in Python.
-# Copyright (c) 2014, 2015, Oracle and/or its affiliates. All rights reserved.
+# Copyright (c) 2014, 2017, Oracle and/or its affiliates. All rights reserved.
 
 # MySQL Connector/Python is licensed under the terms of the GPLv2
 # , like most
@@ -136,21 +136,7 @@ def unix_lib_is64bit(lib_file):
 return False
 
 
-def get_mysql_config_info(mysql_config):
-"""Get MySQL information using mysql_config tool
-
-Returns a dict.
-"""
-options = ['cflags', 'include', 'libs', 'libs_r', 'plugindir', 'version']
-
-cmd = [mysql_config] + [ "--{0}".format(opt) for opt in options ]
-
-try:
-proc = Popen(cmd, stdout=PIPE, universal_newlines=True)
-stdout, _ = proc.communicate()
-except OSError as exc:
-raise DistutilsExecError("Failed executing mysql_config: {0}".format(
-str(exc)))
+def parse_mysql_config_info(options, stdout):
 log.debug("# stdout: {0}".format(stdout))
 info = {}
 for option, line in zip(options, stdout.split('\n')):
@@ -173,7 +159,28 @@ def get_mysql_config_info(mysql_config):
 info['lib_r_dir'] = libs[0].replace('-L', '')
 

Bug#861578: unblock: cairocffi/0.7.2-2

2017-04-30 Thread Sandro Tosi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package cairocffi

* it drops all the depencencies on xcffib as that pkg FTBFS
* it updates the VCS url, pointing to the HTTPS version (I consider this
  information begin updated and a valuable fix for stretch lifetime)
* if fixes a random FTBFS in the test_xcb.py tests. Now, test_xcb.py is disabled
  because we removed xcffib from b-d (so for this upload is a no-op) but once
  we'll be able to add it back, it's a valuable contribution (and also it was
  already in git so i was somewhat lazy and left it in the upload)

Source debdiff is attached

unblock cairocffi/0.7.2-2

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64
 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru cairocffi-0.7.2/debian/changelog cairocffi-0.7.2/debian/changelog
--- cairocffi-0.7.2/debian/changelog2015-12-10 13:02:02.0 -0500
+++ cairocffi-0.7.2/debian/changelog2017-04-30 20:32:16.0 -0400
@@ -1,3 +1,20 @@
+cairocffi (0.7.2-2) unstable; urgency=medium
+
+  [ Ondřej Nový ]
+  * Fixed VCS URL (https)
+
+  [ Stefano Rivera ]
+  * Fix XCB tests (Closes: #828929)
+
+  [ Christoph Reiter ]
+  * Drop Build-Depends and Recommends on xcffib and skip xcb tests
+(Closes: #861175)
+
+  [ Sandro Tosi ]
+  * Team upload.
+
+ -- Sandro Tosi <mo...@debian.org>  Sun, 30 Apr 2017 20:32:16 -0400
+
 cairocffi (0.7.2-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru cairocffi-0.7.2/debian/control cairocffi-0.7.2/debian/control
--- cairocffi-0.7.2/debian/control  2015-12-10 13:02:02.0 -0500
+++ cairocffi-0.7.2/debian/control  2017-04-30 20:32:16.0 -0400
@@ -10,7 +10,6 @@
python3-all,  
python3-setuptools,
python-cffi (>= 1.1.0), python3-cffi (>= 1.1.0),
-   python-xcffib (>= 0.3.2), python3-xcffib (>= 0.3.2),
python-sphinx | python3-sphinx, 
python-pytest, python3-pytest,
xvfb, xauth,
@@ -22,13 +21,12 @@
 X-Python3-Version: >= 3.2
 Standards-Version: 3.9.6
 Homepage: https://pythonhosted.org/cairocffi/
-Vcs-Git: git://anonscm.debian.org/python-modules/packages/cairocffi.git
+Vcs-Git: https://anonscm.debian.org/git/python-modules/packages/cairocffi.git
 Vcs-Browser: 
https://anonscm.debian.org/cgit/python-modules/packages/cairocffi.git
 
 Package: python-cairocffi
 Architecture: all
 Depends: ${misc:Depends}, ${python:Depends}, python-cffi, libcairo2, 
libgdk-pixbuf2.0-0
-Recommends: python-xcffib (>= 0.3.2)
 Suggests: python-cairocffi-doc
 Description: cffi-based cairo bindings for Python 
  cairocffi is a CFFI-based drop-in replacement for Pycairo,
@@ -39,7 +37,6 @@
 Package: python3-cairocffi
 Architecture: all
 Depends: ${misc:Depends}, ${python3:Depends}, python3-cffi, libcairo2, 
libgdk-pixbuf2.0-0
-Recommends: python3-xcffib (>= 0.3.2)
 Suggests: python-cairocffi-doc
 Description: cffi-based cairo bindings for Python (Python3)
  cairocffi is a CFFI-based drop-in replacement for Pycairo,
diff -Nru cairocffi-0.7.2/debian/.git-dpm cairocffi-0.7.2/debian/.git-dpm
--- cairocffi-0.7.2/debian/.git-dpm 2015-12-10 13:02:02.0 -0500
+++ cairocffi-0.7.2/debian/.git-dpm 2017-04-30 20:32:16.0 -0400
@@ -1,6 +1,6 @@
 # see git-dpm(1) from git-dpm package
-c60e548d413fe20495a53d6e5059d3805cb8f00b
-c60e548d413fe20495a53d6e5059d3805cb8f00b
+72067bb5a6d92564284f5a6a94369f24cd4405bb
+72067bb5a6d92564284f5a6a94369f24cd4405bb
 442c25e12a2070d915ac16d4daba19575babe9fa
 442c25e12a2070d915ac16d4daba19575babe9fa
 cairocffi_0.7.2.orig.tar.gz
diff -Nru cairocffi-0.7.2/debian/patches/fix-xcb-tests.patch 
cairocffi-0.7.2/debian/patches/fix-xcb-tests.patch
--- cairocffi-0.7.2/debian/patches/fix-xcb-tests.patch  1969-12-31 
19:00:00.0 -0500
+++ cairocffi-0.7.2/debian/patches/fix-xcb-tests.patch  2017-04-30 
20:32:16.0 -0400
@@ -0,0 +1,66 @@
+From 72067bb5a6d92564284f5a6a94369f24cd4405bb Mon Sep 17 00:00:00 2001
+From: Sean Vig <sean.v@gmail.com>
+Date: Tue, 6 Sep 2016 22:38:14 -0700
+Subject: Fix XCB tests
+
+Make sure XCB objects are free'd, and cffi objects set to None so they
+are gc'd and destroyed before the connection is disconnected.
+
+Origin: https://github.com/Kozea/cairocffi/pull/68
+Bug-Debian: https://bugs.debian.org/828929
+
+Patch-Name: fix-xcb-tests.patch
+---
+ cairocffi/test_xcb.py | 18 --
+ 1 file changed, 16 insertions(+), 2 deletions(-)
+
+diff --git a/cairocffi/test_xcb.py b/cairocffi/test_xcb.py
+index c8a6e70..1aa5123 100644
+--- a/cairocffi/test_xcb.py
 b/cairocffi/test_xcb.py
+@@ -87,6 +87,

Bug#860593: unblock: reportbug/7.1.6

2017-04-18 Thread Sandro Tosi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package reportbug

This upload fixes 2 crashes (one of which pinged by a RT member)

unblock reportbug/7.1.6

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64
 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru reportbug-7.1.5/debian/changelog reportbug-7.1.6/debian/changelog
--- reportbug-7.1.5/debian/changelog2017-02-12 12:07:18.0 -0500
+++ reportbug-7.1.6/debian/changelog2017-04-18 21:12:02.0 -0400
@@ -1,3 +1,15 @@
+reportbug (7.1.6) unstable; urgency=medium
+
+  * reportbug/utils.py
+- wrap every command execution in a helper function to (eventually) decode
+  the command output, this will prevent non-UTF-8 output to crash 
reportbug;
+  patch by Nis Martensen; Closes: #857794
+  * reportbug/submit.py
+- handle text attachments in different encodings, currently making 
reportbug
+  crash; patch by Nis Martensen; Follow up for #848729
+
+ -- Sandro Tosi <mo...@debian.org>  Tue, 18 Apr 2017 21:12:02 -0400
+
 reportbug (7.1.5) unstable; urgency=medium
 
   * reportbug/utils.py
diff -Nru reportbug-7.1.5/reportbug/__init__.py 
reportbug-7.1.6/reportbug/__init__.py
--- reportbug-7.1.5/reportbug/__init__.py   2017-02-12 12:07:18.0 
-0500
+++ reportbug-7.1.6/reportbug/__init__.py   2017-04-18 21:12:02.0 
-0400
@@ -25,7 +25,7 @@
 __all__ = ['bugreport', 'utils', 'urlutils', 'checkbuildd', 'checkversions',
'debbugs', 'exceptions', 'submit', 'tempfile']
 
-VERSION_NUMBER = "7.1.5"
+VERSION_NUMBER = "7.1.6"
 
 VERSION = "reportbug " + VERSION_NUMBER
 COPYRIGHT = VERSION + '\nCopyright (C) 1999-2008 Chris Lawrence 
<lawre...@debian.org>' + \
Binary files 
/tmp/1bRAXcxzCa/reportbug-7.1.5/reportbug/__pycache__/__init__.cpython-35.pyc 
and 
/tmp/snN27qW4Zs/reportbug-7.1.6/reportbug/__pycache__/__init__.cpython-35.pyc 
differ
Binary files 
/tmp/1bRAXcxzCa/reportbug-7.1.5/reportbug/__pycache__/utils.cpython-35.pyc and 
/tmp/snN27qW4Zs/reportbug-7.1.6/reportbug/__pycache__/utils.cpython-35.pyc 
differ
diff -Nru reportbug-7.1.5/reportbug/submit.py 
reportbug-7.1.6/reportbug/submit.py
--- reportbug-7.1.5/reportbug/submit.py 2017-02-12 12:07:18.0 -0500
+++ reportbug-7.1.6/reportbug/submit.py 2017-04-18 21:12:02.0 -0400
@@ -153,9 +153,15 @@
 
 maintype, subtype = ctype.split('/', 1)
 if maintype == 'text':
-fp = open(attachment, 'rU')
-part = MIMEText(fp.read())
-fp.close()
+try:
+with open(attachment, 'rU') as fp:
+part = MIMEText(fp.read())
+except UnicodeDecodeError:
+fp = open(attachment, 'rb')
+part = MIMEBase(maintype, subtype)
+part.set_payload(fp.read())
+fp.close()
+email.encoders.encode_base64(part)
 elif maintype == 'message':
 fp = open(attachment, 'rb')
 part = MIMEMessage(email.message_from_file(fp),
diff -Nru reportbug-7.1.5/reportbug/utils.py reportbug-7.1.6/reportbug/utils.py
--- reportbug-7.1.5/reportbug/utils.py  2017-02-12 12:07:18.0 -0500
+++ reportbug-7.1.6/reportbug/utils.py  2017-04-18 21:12:02.0 -0400
@@ -180,6 +180,13 @@
 return (pipe, use_dlocate)
 
 
+def get_command_output(cmd):
+use_shell = False
+if isinstance(cmd, str) and ' ' in cmd:
+use_shell = True
+return subprocess.run(cmd, shell=use_shell, 
stdout=subprocess.PIPE).stdout.decode(errors='backslashreplace')
+
+
 def query_dpkg_for(filename, use_dlocate=True):
 try:
 x = os.getcwd()
@@ -353,10 +360,10 @@
 
 packarg = pipes.quote(package)
 if avail:
-output = subprocess.getoutput(
+output = get_command_output(
 "COLUMNS=79 dpkg --print-avail %s 2>/dev/null" % packarg)
 else:
-output = subprocess.getoutput(
+output = get_command_output(
 "COLUMNS=79 dpkg --status %s 2>/dev/null" % packarg)
 
 for line in output.split(os.linesep):
@@ -511,7 +518,7 @@
 
 
 def available_package_description(package):
-data = subprocess.getoutput('apt-cache show ' + pipes.quote(package))
+data = get_command_output('apt-cache show ' + pipes.quote(package))
 descre = re.compile('^Description(?:-.*)?: (.*)$')
 for line in data.split('\n'):
 m = descre.match(line)
@@ -523,7 +530,7 @@
 def get_source_name(package):
 packages = []
 
-data = subprocess.getoutput('apt-cache showsrc ' + pipes.quote(package))
+data = get_command_output('ap

Bug#860589: unblock: pyvirtualdisplay/0.2.1-2

2017-04-18 Thread Sandro Tosi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package pyvirtualdisplay

The last upload add 2 dependencies, needed to be able to use pyvirtualdisplay
(without any of them, arguably xvfb the most important, so in depends, you cant
instantiate the main class Display())

source debdiff attached

unblock pyvirtualdisplay/0.2.1-2

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru pyvirtualdisplay-0.2.1/debian/changelog 
pyvirtualdisplay-0.2.1/debian/changelog
--- pyvirtualdisplay-0.2.1/debian/changelog 2016-12-13 19:16:11.0 
-0500
+++ pyvirtualdisplay-0.2.1/debian/changelog 2017-04-18 20:13:15.0 
-0400
@@ -1,3 +1,11 @@
+pyvirtualdisplay (0.2.1-2) unstable; urgency=medium
+
+  * debian/control
+- add xvfb to depends and xserver-xephyr to suggests: one of them has to be
+  available to instantiate the Display() class; Closes: #860501
+
+ -- Sandro Tosi <mo...@debian.org>  Tue, 18 Apr 2017 20:13:15 -0400
+
 pyvirtualdisplay (0.2.1-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru pyvirtualdisplay-0.2.1/debian/control 
pyvirtualdisplay-0.2.1/debian/control
--- pyvirtualdisplay-0.2.1/debian/control   2016-12-13 19:16:11.0 
-0500
+++ pyvirtualdisplay-0.2.1/debian/control   2017-04-18 20:13:15.0 
-0400
@@ -17,9 +17,9 @@
 
 Package: python-pyvirtualdisplay
 Architecture: all
-Depends: ${misc:Depends}, ${python:Depends},
+Depends: ${misc:Depends}, ${python:Depends}, xvfb
 Recommends: ${python:Recommends}
-Suggests: ${python:Suggests}
+Suggests: ${python:Suggests}, xserver-xephyr
 Description: python wrapper for Xvfb, Xephyr and Xvnc - Python 2.X
  pyvirtualdisplay is a python wrapper for Xvfb, Xephyr and Xvnc
  .
@@ -27,9 +27,9 @@
 
 Package: python3-pyvirtualdisplay
 Architecture: all
-Depends: ${misc:Depends}, ${python3:Depends},
+Depends: ${misc:Depends}, ${python3:Depends}, xvfb
 Recommends: ${python3:Recommends}
-Suggests: ${python3:Suggests}
+Suggests: ${python3:Suggests}, xserver-xephyr
 Description: python wrapper for Xvfb, Xephyr and Xvnc
  pyvirtualdisplay is a python wrapper for Xvfb, Xephyr and Xvnc
  .


Bug#855650: is it worth truing to unblock slimit/0.8.1-2 ?

2017-02-20 Thread Sandro Tosi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Hello Release Team,
reading the RC bugs against DPMT, i noticed the one[1] against slimit: i think
there was a "naive" upload[2] already in the deep freeze, which started to
provide a py3k package (something i think is really interesting to have for
stretch).

That upload sadly introduced [1], so what i would like to know from you is: is
it worth spending time to fix [1]? will you accept an unblock with the
(hypotetic) -3 release when -2 contains some major changes you might not want to
see in stretch?

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855510
[2] https://packages.qa.debian.org/s/slimit/news/20170208T070018Z.html

thanks for considering,
Sandro

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)



Bug#855556: unblock: python-ws4py/0.3.4-4

2017-02-19 Thread Sandro Tosi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package python-ws4py

I've just uploaded this package with a fix for a FTBFS on a 1 CPU machine.

The source debdiff between -3 and -4 is attached (some of the diffs are due to
git-dpm patch generation logic).

unblock python-ws4py/0.3.4-4

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru python-ws4py-0.3.4/debian/changelog 
python-ws4py-0.3.4/debian/changelog
--- python-ws4py-0.3.4/debian/changelog 2016-08-07 17:02:52.0 -0400
+++ python-ws4py-0.3.4/debian/changelog 2017-02-19 20:57:41.0 -0500
@@ -1,3 +1,14 @@
+python-ws4py (0.3.4-4) unstable; urgency=medium
+
+  [ Sandro Tosi ]
+  * Team upload.
+
+  [ Norimitsu Sugimoto ]
+  * fix to fail unittest test_manager.py on 1 core CPU machine.
+(Closes: #834921)
+
+ -- Sandro Tosi <mo...@debian.org>  Sun, 19 Feb 2017 20:57:41 -0500
+
 python-ws4py (0.3.4-3) unstable; urgency=medium
 
   [ Ondřej Nový ]
diff -Nru python-ws4py-0.3.4/debian/.git-dpm python-ws4py-0.3.4/debian/.git-dpm
--- python-ws4py-0.3.4/debian/.git-dpm  2016-08-07 16:56:14.0 -0400
+++ python-ws4py-0.3.4/debian/.git-dpm  2017-02-19 20:57:41.0 -0500
@@ -1,6 +1,6 @@
 # see git-dpm(1) from git-dpm package
-750981d4c6165b945def438b4dd790c3326d03de
-750981d4c6165b945def438b4dd790c3326d03de
+13ac903999b5f3472de0794d710e88d31793c436
+13ac903999b5f3472de0794d710e88d31793c436
 7f43f2a6bff1aabafad023652042439d7b9b8d84
 7f43f2a6bff1aabafad023652042439d7b9b8d84
 python-ws4py_0.3.4.orig.tar.gz
diff -Nru python-ws4py-0.3.4/debian/patches/0001-Fix-tests.patch 
python-ws4py-0.3.4/debian/patches/0001-Fix-tests.patch
--- python-ws4py-0.3.4/debian/patches/0001-Fix-tests.patch  2016-08-07 
16:56:14.0 -0400
+++ python-ws4py-0.3.4/debian/patches/0001-Fix-tests.patch  2017-02-19 
20:57:41.0 -0500
@@ -1,4 +1,4 @@
-From a7d5ce7c1e8d39c2e68eeb6ef5bab72b3981dc37 Mon Sep 17 00:00:00 2001
+From 3722f5ece7e22ed67a84bfaae464853a146d2eb4 Mon Sep 17 00:00:00 2001
 From: Stein Magnus Jodal <jo...@debian.org>
 Date: Thu, 5 Nov 2015 15:46:08 +0100
 Subject: Fix tests
@@ -6,12 +6,14 @@
 Based on upstream commits:
 - b5d47f7b3497f1b713a20fe6306b7d9afdd8c408
 - b2a76a33960040d7d3d27c68bf17c12f169f81c7
+
+fix unittest failing on 1 CPU machines
 ---
- test/test_manager.py | 13 +++--
- 1 file changed, 7 insertions(+), 6 deletions(-)
+ test/test_manager.py | 14 --
+ 1 file changed, 8 insertions(+), 6 deletions(-)
 
 diff --git a/test/test_manager.py b/test/test_manager.py
-index 8c229b0..da57d44 100644
+index 8c229b0..fceb77d 100644
 --- a/test/test_manager.py
 +++ b/test/test_manager.py
 @@ -16,10 +16,10 @@ class WSManagerTest(unittest.TestCase):
@@ -36,7 +38,15 @@
  m.poller.reset_mock()
  
  m.remove(ws)
-@@ -97,8 +97,9 @@ class WSManagerTest(unittest.TestCase):
+@@ -62,6 +62,7 @@ class WSManagerTest(unittest.TestCase):
+ self.assertFalse(m.running)
+ 
+ m.start()
++time.sleep(0.2)
+ self.assertTrue(m.running)
+ 
+ m.stop()
+@@ -97,8 +98,9 @@ class WSManagerTest(unittest.TestCase):
  
  m.add(ws)
  m.start()
@@ -47,7 +57,7 @@
  
  m.stop()
  
-@@ -109,7 +110,7 @@ class WSManagerTest(unittest.TestCase):
+@@ -109,7 +111,7 @@ class WSManagerTest(unittest.TestCase):
  ws = MagicMock()
  m.add(ws)
  m.close_all()
@@ -56,7 +66,7 @@
  
  @patch('ws4py.manager.SelectPoller')
  def test_broadcast(self, MockSelectPoller):
-@@ -120,7 +121,7 @@ class WSManagerTest(unittest.TestCase):
+@@ -120,7 +122,7 @@ class WSManagerTest(unittest.TestCase):
  m.add(ws)
  
  m.broadcast(b'hello there')
diff -Nru 
python-ws4py-0.3.4/debian/patches/0002-Make-intersphinx-use-object.inv-from-python-doc.patch
 
python-ws4py-0.3.4/debian/patches/0002-Make-intersphinx-use-object.inv-from-python-doc.patch
--- 
python-ws4py-0.3.4/debian/patches/0002-Make-intersphinx-use-object.inv-from-python-doc.patch
2016-08-07 16:56:14.0 -0400
+++ 
python-ws4py-0.3.4/debian/patches/0002-Make-intersphinx-use-object.inv-from-python-doc.patch
2017-02-19 20:57:41.0 -0500
@@ -1,4 +1,4 @@
-From 750981d4c6165b945def438b4dd790c3326d03de Mon Sep 17 00:00:00 2001
+From 13ac903999b5f3472de0794d710e88d31793c436 Mon Sep 17 00:00:00 2001
 From: Stein Magnus Jodal <jo...@debian.org>
 Date: Sun, 7 Aug 2016 22:56:09 +0200
 Subject: Make intersphinx use object.inv from python-doc


Bug#855481: RM: granule-manual/1.1.0+dfsg-2

2017-02-18 Thread Sandro Tosi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm

please remove granule-manual from testing as it provides documentation for
granule, which is not in stretch (cfr 854196 for granule-manual and 805203 for
granule)

thanks

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)



Bug#855177: unblock: matplotlib/2.0.0+dfsg1-2

2017-02-14 Thread Sandro Tosi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package matplotlib

During the last upload there was a mistake: after removing the non-free image,
an example was left behind; examples in mpl are used to generate the
documentation, and during the doc build this example failed, causing the failure
to generate all the HTML documentation for mpl. In this upload we remove that
example file, as suggested by upstream

I didnt notice this as erroneusly we were ignoring if the doc build process was
generating any errors; this upload also fixes this

debdiff between 2.0.0+dfsg1-1 and 2.0.0+dfsg1-2 is attached

unblock matplotlib/2.0.0+dfsg1-2

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru matplotlib-2.0.0+dfsg1/debian/changelog 
matplotlib-2.0.0+dfsg1/debian/changelog
--- matplotlib-2.0.0+dfsg1/debian/changelog 2017-02-12 16:13:26.0 
-0500
+++ matplotlib-2.0.0+dfsg1/debian/changelog 2017-02-14 19:48:20.0 
-0500
@@ -1,3 +1,13 @@
+matplotlib (2.0.0+dfsg1-2) unstable; urgency=medium
+
+  * debian/rules
+- make a failure in the doc build process also fail the package build
+  * debian/patches/0010-remove-interpolation_none_vs_nearest.py.patch
+- remove an example (which uses the removed necked_tensile_specimen.png
+  image) that made the HTML doc build to fail; Closes: #855029
+
+ -- Sandro Tosi <mo...@debian.org>  Tue, 14 Feb 2017 19:48:20 -0500
+
 matplotlib (2.0.0+dfsg1-1) unstable; urgency=medium
 
   * Import upstream tarball with necked_tensile_specimen.png removed
diff -Nru matplotlib-2.0.0+dfsg1/debian/.git-dpm 
matplotlib-2.0.0+dfsg1/debian/.git-dpm
--- matplotlib-2.0.0+dfsg1/debian/.git-dpm  2017-02-12 16:13:26.0 
-0500
+++ matplotlib-2.0.0+dfsg1/debian/.git-dpm  2017-02-14 19:48:20.0 
-0500
@@ -1,6 +1,6 @@
 # see git-dpm(1) from git-dpm package
-cb2f046ef7cc2dc44026a658e5a590685e122b5b
-cb2f046ef7cc2dc44026a658e5a590685e122b5b
+87576dc0ee642fc0c5a298807705eb13492d6d4f
+87576dc0ee642fc0c5a298807705eb13492d6d4f
 b358b1f4101ba66b027228d545973408d1b9
 b358b1f4101ba66b027228d545973408d1b9
 matplotlib_2.0.0+dfsg1.orig.tar.gz
diff -Nru 
matplotlib-2.0.0+dfsg1/debian/patches/0010-remove-interpolation_none_vs_nearest.py.patch
 
matplotlib-2.0.0+dfsg1/debian/patches/0010-remove-interpolation_none_vs_nearest.py.patch
--- 
matplotlib-2.0.0+dfsg1/debian/patches/0010-remove-interpolation_none_vs_nearest.py.patch
1969-12-31 19:00:00.0 -0500
+++ 
matplotlib-2.0.0+dfsg1/debian/patches/0010-remove-interpolation_none_vs_nearest.py.patch
2017-02-14 19:48:20.0 -0500
@@ -0,0 +1,81 @@
+From 87576dc0ee642fc0c5a298807705eb13492d6d4f Mon Sep 17 00:00:00 2001
+From: Sandro Tosi <mo...@debian.org>
+Date: Tue, 14 Feb 2017 19:43:40 -0500
+Subject: remove interpolation_none_vs_nearest.py
+
+this example uses necked_tensile_specimen.png, which has been removed due to a
+non distributable color calibration code, and so when it is executed during the
+build process makes it fail to generate the HTML doc.
+---
+ .../interpolation_none_vs_nearest.py   | 62 --
+ 1 file changed, 62 deletions(-)
+ delete mode 100644 
examples/images_contours_and_fields/interpolation_none_vs_nearest.py
+
+diff --git 
a/examples/images_contours_and_fields/interpolation_none_vs_nearest.py 
b/examples/images_contours_and_fields/interpolation_none_vs_nearest.py
+deleted file mode 100644
+index 487b401..000
+--- a/examples/images_contours_and_fields/interpolation_none_vs_nearest.py
 /dev/null
+@@ -1,62 +0,0 @@
+-"""
+-Displays the difference between interpolation = 'none' and
+-interpolation = 'nearest'.
+-
+-Interpolation = 'none' and interpolation = 'nearest' are equivalent when
+-converting a figure to an image file, such as a PNG.
+-Interpolation = 'none' and interpolation = 'nearest' behave quite
+-differently, however, when converting a figure to a vector graphics file,
+-such as a PDF.  As shown, Interpolation = 'none' works well when a big
+-image is scaled down, while interpolation = 'nearest' works well when a
+-small image is blown up.
+-"""
+-
+-import numpy as np
+-import matplotlib.pyplot as plt
+-import matplotlib.cbook as cbook
+-
+-# Load big image
+-big_im_path = cbook.get_sample_data('necked_tensile_specimen.png')
+-big_im = plt.imread(big_im_path)
+-# Define small image
+-small_im = np.array([[0.25, 0.75, 1.0, 0.75], [0.1, 0.65, 0.5, 0.4],
+- [0.6, 0.3, 0.0, 0.2], [0.7, 0.9, 0.4, 0.6]])
+-
+-# Create a 2x2 table of plots
+-fig, axes = plt.subplots(figsize=[8

Bug#854993: unblock: python-uniconvertor/1.1.5-4

2017-02-12 Thread Sandro Tosi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package python-uniconvertor

I just uploaded this package fixing the RC bug about the -dbg doc symlink that
got lost between jessie and now, by using the --link-doc option of
dh_installdocs and the maint script to handle the dir -> symlin migration.

I also took the liberty to update the Homepage, as it makes sense to have that
information as updated as possible for stretch lifetime

source debdiff between 1.1.5-3 and 1.1.5-4 is attached

unblock python-uniconvertor/1.1.5-4

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru python-uniconvertor-1.1.5/debian/changelog 
python-uniconvertor-1.1.5/debian/changelog
--- python-uniconvertor-1.1.5/debian/changelog  2016-10-01 11:14:52.0 
-0400
+++ python-uniconvertor-1.1.5/debian/changelog  2017-02-12 19:36:23.0 
-0500
@@ -1,3 +1,11 @@
+python-uniconvertor (1.1.5-4) unstable; urgency=medium
+
+  * QA upload.
+  * restore the doc symlink between -dbg and main pkg; Closes: #852144
+  * Update homepage URL; Closes: #845230
+
+ -- Sandro Tosi <mo...@debian.org>  Sun, 12 Feb 2017 19:36:15 -0500
+
 python-uniconvertor (1.1.5-3) unstable; urgency=medium
 
   * QA upload.
diff -Nru python-uniconvertor-1.1.5/debian/control 
python-uniconvertor-1.1.5/debian/control
--- python-uniconvertor-1.1.5/debian/control2016-10-01 10:51:52.0 
-0400
+++ python-uniconvertor-1.1.5/debian/control2017-02-12 19:32:27.0 
-0500
@@ -2,7 +2,7 @@
 Section: python
 Priority: optional
 Maintainer: Debian QA Group <packa...@qa.debian.org>
-Homepage: http://sk1project.org/modules.php?name=Products=uniconvertor
+Homepage: https://sk1project.net/modules.php?name=Products=uniconvertor
 Build-Depends:
  debhelper (>= 9),
  dh-python,
diff -Nru python-uniconvertor-1.1.5/debian/copyright 
python-uniconvertor-1.1.5/debian/copyright
--- python-uniconvertor-1.1.5/debian/copyright  2016-10-01 10:51:52.0 
-0400
+++ python-uniconvertor-1.1.5/debian/copyright  2017-02-12 19:32:41.0 
-0500
@@ -2,7 +2,7 @@
 Mon, 10 Mar 2008 22:42:50 +0100
 
 It was downloaded from:
-http://sk1project.org/modules.php?name=Products=uniconvertor
+https://sk1project.net/modules.php?name=Products=uniconvertor
 
 Copyright (C) 2007-2008 by Igor E. Novikov, Valek Fillipov
 
diff -Nru python-uniconvertor-1.1.5/debian/python-uniconvertor-dbg.maintscript 
python-uniconvertor-1.1.5/debian/python-uniconvertor-dbg.maintscript
--- python-uniconvertor-1.1.5/debian/python-uniconvertor-dbg.maintscript
1969-12-31 19:00:00.0 -0500
+++ python-uniconvertor-1.1.5/debian/python-uniconvertor-dbg.maintscript
2017-02-12 19:45:15.0 -0500
@@ -0,0 +1 @@
+dir_to_symlink /usr/share/doc/python-uniconvertor-dbg 
/usr/share/doc/python-uniconvertor 1.1.5-3
diff -Nru python-uniconvertor-1.1.5/debian/rules 
python-uniconvertor-1.1.5/debian/rules
--- python-uniconvertor-1.1.5/debian/rules  2016-10-01 11:14:52.0 
-0400
+++ python-uniconvertor-1.1.5/debian/rules  2017-02-12 19:28:54.0 
-0500
@@ -24,3 +24,5 @@
 override_dh_strip:
dh_strip -ppython-uniconvertor --dbg-package=python-uniconvertor-dbg
 
+override_dh_installdocs:
+   dh_installdocs --link-doc=python-uniconvertor


Bug#854990: unblock: matplotlib/2.0.0+dfsg1-1

2017-02-12 Thread Sandro Tosi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package matplotlib

I just uploaded matplotlib removing a non-free file (hence the "apparent" new
release, which is just the previous tarball without that file and the dfsg tag
appended to the version) and adding copyright/license notices for several font
files; those 2 changes closes 2 RC bugs against mpl 

Source debdiff between 2.0.0-3 and 2.0.0+dfsg1-1 is attached

unblock matplotlib/2.0.0+dfsg1-1

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru matplotlib-2.0.0/debian/changelog 
matplotlib-2.0.0+dfsg1/debian/changelog
--- matplotlib-2.0.0/debian/changelog   2017-01-21 21:35:45.0 -0500
+++ matplotlib-2.0.0+dfsg1/debian/changelog 2017-02-12 16:13:26.0 
-0500
@@ -1,3 +1,16 @@
+matplotlib (2.0.0+dfsg1-1) unstable; urgency=medium
+
+  * Import upstream tarball with necked_tensile_specimen.png removed
+  * exclude necked_tensile_specimen.png from upstream tarball, as that file
+contains a non-free color calibration profile; Closes: #854280
+  * debian/copyright
+- add pdfcorefiles license grant
+- add copyright notices for all AFM fonts
+- add license and copyright notice to TTG BaKoMa fonts files;
+  Closes: #854279
+
+ -- Sandro Tosi <mo...@debian.org>  Sun, 12 Feb 2017 16:13:26 -0500
+
 matplotlib (2.0.0-3) unstable; urgency=medium
 
   * debian/patches/0009-Add-a-newline-separator-in-fc-list-call.patch
diff -Nru matplotlib-2.0.0/debian/copyright 
matplotlib-2.0.0+dfsg1/debian/copyright
--- matplotlib-2.0.0/debian/copyright   2017-01-21 21:35:45.0 -0500
+++ matplotlib-2.0.0+dfsg1/debian/copyright 2017-02-12 16:13:26.0 
-0500
@@ -2,6 +2,7 @@
 Upstream-Name: matplotlib
 Upstream-Contact: John D. Hunter, Michael Droettboom <md...@stsci.edu>
 Source: http://matplotlib.org
+Files-Excluded: lib/matplotlib/mpl-data/sample_data/necked_tensile_specimen.png
 
 Files: *
 Copyright: Copyright (c) 2002 - 2012 John Hunter, Darren Dale, Eric Firing, 
Michael Droettboom and the matplotlib development team; 2012 - 2016 The 
matplotlib development team
@@ -259,11 +260,300 @@
  mathematical fonts, please contact MicroPress, Inc., 68-30 Harrow
  Street, Forest Hills, NY 11375, USA - Phone: (718) 575-1816.
 
+Files: lib/matplotlib/mpl-data/fonts/ttf/cmb10.ttf 
lib/matplotlib/mpl-data/fonts/ttf/cmex10.ttf 
lib/matplotlib/mpl-data/fonts/ttf/cmmi10.ttf 
lib/matplotlib/mpl-data/fonts/ttf/cmr10.ttf 
lib/matplotlib/mpl-data/fonts/ttf/cmss10.ttf 
lib/matplotlib/mpl-data/fonts/ttf/cmsy10.ttf 
lib/matplotlib/mpl-data/fonts/ttf/cmtt10.ttf
+Copyright: Copyright (C) 1994, Basil K. Malyshev. All Rights Reserved.
+License: from LICENSE/LICENSE_BAKOMA
+BaKoMa Fonts Licence
+
+ .
+  This licence covers two font packs (known as BaKoMa Fonts Colelction,
+  which is available at `CTAN:fonts/cm/ps-type1/bakoma/'):
+ .
+1) BaKoMa-CM (1.1/12-Nov-94)
+   Computer Modern Fonts in PostScript Type 1 and TrueType font formats.
+ .
+2) BaKoMa-AMS (1.2/19-Jan-95)
+   AMS TeX fonts in PostScript Type 1 and TrueType font formats.
+ .
+  Copyright (C) 1994, 1995, Basil K. Malyshev. All Rights Reserved.
+ .
+  Permission to copy and distribute these fonts for any purpose is
+  hereby granted without fee, provided that the above copyright notice,
+  author statement and this permission notice appear in all copies of
+  these fonts and related documentation.
+ .
+  Permission to modify and distribute modified fonts for any purpose is
+  hereby granted without fee, provided that the copyright notice,
+  author statement, this permission notice and location of original
+  fonts (http://www.ctan.org/tex-archive/fonts/cm/ps-type1/bakoma)
+  appear in all copies of modified fonts and related documentation.
+ .
+  Permission to use these fonts (embedding into PostScript, PDF, SVG
+  and printing by using any software) is hereby granted without fee.
+  It is not required to provide any notices about using these fonts.
+ .
+ Basil K. Malyshev
+ INSTITUTE FOR HIGH ENERGY PHYSICS
+ IHEP, OMVT
+ Moscow Region
+ 142281 PROTVINO
+ RUSSIA
+ .
+ E-Mail:bak...@mail.ru
+  ormalys...@mail.ihep.ru
+
 Files: lib/matplotlib/mpl-data/fonts/pdfcorefonts/*
 Copyright: Copyright (c) 1985, 1987, 1989, 1990, 1991, 1992, 1993, 1997 Adobe 
Systems Incorporated.  All Rights Reserved.
+License:
+ This directory contains font metrics for the 14 PDF Core Fonts,
+ downloaded from Adobe. The title and this paragraph were added by
+ Matplotlib developers. The do

Bug#854971: unblock: reportbug/7.1.5

2017-02-12 Thread Sandro Tosi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package reportbug

I just uploaded a new release of reportbug fixing bugs in GTK+ interface and in
charset/locale handling which are affecting many users

Source debdiff between 7.1.4 and 7.1.5 is attached

unblock reportbug/7.1.5

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru reportbug-7.1.4/debian/changelog reportbug-7.1.5/debian/changelog
--- reportbug-7.1.4/debian/changelog2017-01-22 18:16:04.0 -0500
+++ reportbug-7.1.5/debian/changelog2017-02-12 12:07:18.0 -0500
@@ -1,3 +1,20 @@
+reportbug (7.1.5) unstable; urgency=medium
+
+  * reportbug/utils.py
+- handle correcly the situation where reportbug config file and dpkg status
+  database have a different charset than current locale; patch by Nis
+  Martensen; Closes: #848729
+  * reportbug/ui/gtk2_ui.py
+- fallback gracefully to text UI if running GTK+ interface on a text
+  console; patch by Nis Martensen; Closes: #853269
+- fallback gracefully to text UI in case some of the GTK+ deps are not
+  available, by catching all the relevant exceptions; patch by Jakob Haufe;
+  Closes: #854405
+- require also Cairo, required to render the GTK+ interface; patch by Nis
+  Martensen; Closes: #852652
+
+ -- Sandro Tosi <mo...@debian.org>  Sun, 12 Feb 2017 12:07:18 -0500
+
 reportbug (7.1.4) unstable; urgency=medium
 
   * reportbug/submit.py
diff -Nru reportbug-7.1.4/reportbug/__init__.py 
reportbug-7.1.5/reportbug/__init__.py
--- reportbug-7.1.4/reportbug/__init__.py   2017-01-22 18:16:04.0 
-0500
+++ reportbug-7.1.5/reportbug/__init__.py   2017-02-12 12:07:18.0 
-0500
@@ -25,7 +25,7 @@
 __all__ = ['bugreport', 'utils', 'urlutils', 'checkbuildd', 'checkversions',
'debbugs', 'exceptions', 'submit', 'tempfile']
 
-VERSION_NUMBER = "7.1.4"
+VERSION_NUMBER = "7.1.5"
 
 VERSION = "reportbug " + VERSION_NUMBER
 COPYRIGHT = VERSION + '\nCopyright (C) 1999-2008 Chris Lawrence 
<lawre...@debian.org>' + \
Binary files 
/tmp/cOjLl1qlsz/reportbug-7.1.4/reportbug/__pycache__/__init__.cpython-35.pyc 
and 
/tmp/vTwa7oxWbv/reportbug-7.1.5/reportbug/__pycache__/__init__.cpython-35.pyc 
differ
Binary files 
/tmp/cOjLl1qlsz/reportbug-7.1.4/reportbug/__pycache__/submit.cpython-35.pyc and 
/tmp/vTwa7oxWbv/reportbug-7.1.5/reportbug/__pycache__/submit.cpython-35.pyc 
differ
Binary files 
/tmp/cOjLl1qlsz/reportbug-7.1.4/reportbug/__pycache__/utils.cpython-35.pyc and 
/tmp/vTwa7oxWbv/reportbug-7.1.5/reportbug/__pycache__/utils.cpython-35.pyc 
differ
diff -Nru reportbug-7.1.4/reportbug/ui/gtk2_ui.py 
reportbug-7.1.5/reportbug/ui/gtk2_ui.py
--- reportbug-7.1.4/reportbug/ui/gtk2_ui.py 2017-01-22 18:16:04.0 
-0500
+++ reportbug-7.1.5/reportbug/ui/gtk2_ui.py 2017-02-12 12:07:18.0 
-0500
@@ -22,6 +22,10 @@
 
 from reportbug.exceptions import UINotImportable
 
+import os
+if not ('DISPLAY' in os.environ or 'WAYLAND_DISPLAY' in os.environ):
+raise UINotImportable('No graphical display detected, falling back to text 
UI.')
+
 try:
 import gi
 
@@ -42,6 +46,8 @@
 
 gi.require_version('Gtk', '3.0')
 from gi.repository import Gtk
+
+gi.require_foreign('cairo')
 except ImportError:
 raise UINotImportable('Please install the python3-gi and gir1.2-gtk-3.0 
packages to use this interface.')
 
@@ -1777,7 +1783,7 @@
 try:
 gi.require_version('Vte', '2.91')
 from gi.repository import Vte
-except ImportError:
+except (ImportError,ValueError):
 message = """Please install the %s package to use the GTK+(known as 
'gtk2' in reportbug) interface.
 Falling back to 'text' interface."""
 dialog = Gtk.MessageDialog(None, Gtk.DialogFlags.MODAL | 
Gtk.DialogFlags.DESTROY_WITH_PARENT,
Binary files 
/tmp/cOjLl1qlsz/reportbug-7.1.4/reportbug/ui/__pycache__/gtk2_ui.cpython-35.pyc 
and 
/tmp/vTwa7oxWbv/reportbug-7.1.5/reportbug/ui/__pycache__/gtk2_ui.cpython-35.pyc 
differ
diff -Nru reportbug-7.1.4/reportbug/utils.py reportbug-7.1.5/reportbug/utils.py
--- reportbug-7.1.4/reportbug/utils.py  2017-01-22 18:16:04.0 -0500
+++ reportbug-7.1.5/reportbug/utils.py  2017-02-12 12:07:18.0 -0500
@@ -496,7 +496,7 @@
 
 def get_dpkg_database():
 try:
-fp = open(STATUSDB)
+fp = open(STATUSDB, errors="backslashreplace")
 if fp:
 return AvailDB(fp=fp)
 except IOError:
@@ -976,7 +976,7 @@
 for filename in FILES:
 if os.path.exists(file

Bug#854908: unblock: plainbox-provider-resource-generic/0.23-1.1

2017-02-11 Thread Sandro Tosi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package plainbox-provider-resource-generic

The recent NMU to unstable fixes a RC bug by setting an explicitly list of
architectures where we can install dmidecode

source package ebdiff is attached

unblock plainbox-provider-resource-generic/0.23-1.1

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru plainbox-provider-resource-generic-0.23/debian/changelog 
plainbox-provider-resource-generic-0.23/debian/changelog
--- plainbox-provider-resource-generic-0.23/debian/changelog2016-01-18 
16:23:53.0 -0500
+++ plainbox-provider-resource-generic-0.23/debian/changelog2017-02-07 
22:40:56.0 -0500
@@ -1,3 +1,12 @@
+plainbox-provider-resource-generic (0.23-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/patches/dmidecode_depends.patch
+- positively declare the list of architectures where to depends on
+  dmidecode; patch by Emilio Pozuelo Monfort; Closes: #814373
+
+ -- Sandro Tosi <mo...@debian.org>  Tue, 07 Feb 2017 22:39:19 -0500
+
 plainbox-provider-resource-generic (0.23-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru 
plainbox-provider-resource-generic-0.23/debian/patches/dmidecode_depends.patch 
plainbox-provider-resource-generic-0.23/debian/patches/dmidecode_depends.patch
--- 
plainbox-provider-resource-generic-0.23/debian/patches/dmidecode_depends.patch  
1969-12-31 19:00:00.0 -0500
+++ 
plainbox-provider-resource-generic-0.23/debian/patches/dmidecode_depends.patch  
2017-02-07 22:38:57.0 -0500
@@ -0,0 +1,11 @@
+--- a/jobs/resource.pxu
 b/jobs/resource.pxu
+@@ -20,7 +20,7 @@ Suggests: x11-server-utils
+ # This is for bin/dmi_resource
+ unit: packaging meta-data
+ os-id: debian
+-Depends: dmidecode [!armel !mips !mipsel !powerpc !ppc64el !s390x]
++Depends: dmidecode [any-amd64 any-i386 arm64 armhf x32]
+ 
+ # This is for bin/dpkg_resource
+ unit: packaging meta-data
diff -Nru plainbox-provider-resource-generic-0.23/debian/patches/series 
plainbox-provider-resource-generic-0.23/debian/patches/series
--- plainbox-provider-resource-generic-0.23/debian/patches/series   
1969-12-31 19:00:00.0 -0500
+++ plainbox-provider-resource-generic-0.23/debian/patches/series   
2017-02-07 22:37:57.0 -0500
@@ -0,0 +1 @@
+dmidecode_depends.patch


Bug#854531: RM: openteacher/3.2-2

2017-02-07 Thread Sandro Tosi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm

Hello,
openteacher has an RC bug, 851420, and while investigating it, it turned out
that its own upstream developer declared "This project is pretty much dead"[1]

please remove it from testing (and we can think about removing entirely from
debian once stretch has been released).

Thanks,
Sandro

[1] https://bugs.launchpad.net/openteacher/+bug/1547432

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)



Re: Bug#769355: reportbug: extend binNMU support to cover more distros besides unstable

2015-04-15 Thread Sandro Tosi
On Tue, Apr 14, 2015 at 5:12 PM, Niels Thykier ni...@thykier.net wrote:
 On 2015-04-13 13:22, Sandro Tosi wrote:
 Hello,

 On Wed, Nov 12, 2014 at 11:28 PM, Andreas Beckmann a...@debian.org wrote:
 Please enhance the release.debian.org binNMU reporting functionality to ask
 for the release where the binNMU should be performed. The question
 should default to sid similarily to the ftp.debian.org RM template 
 questions.

 This seems like a valid request for me, but I'm adding release.d.o
 team in the loop to seek for their input too.

 Regards,


 Hi Sandro,

 Sounds like a fine idea for me.

That's great! now, last doubt: what type of suites are allowed in the
nmu command? Andreas mentioned some (other than the default
'unstable'):

* experimental
* $STABLE-backports
* $STABLE-proposed-updates
* $STABLE

are there any other acceptable? is $STABLE 'stable' or 'wheezy' (the
former is preferred - from my POV - to avoid to update the suites list
at each release)? No binnmu in testing? so, really, what should I put
in this suites menu?! :)

Thanks  Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/cab4xwxyjk+fmzktfoddb03jwjua918ak__qspcrhwweypwd...@mail.gmail.com



Re: Bug#769355: reportbug: extend binNMU support to cover more distros besides unstable

2015-04-13 Thread Sandro Tosi
Hello,

On Wed, Nov 12, 2014 at 11:28 PM, Andreas Beckmann a...@debian.org wrote:
 Please enhance the release.debian.org binNMU reporting functionality to ask
 for the release where the binNMU should be performed. The question
 should default to sid similarily to the ftp.debian.org RM template questions.

This seems like a valid request for me, but I'm adding release.d.o
team in the loop to seek for their input too.

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/CAB4XWXwV30DsfDkQV5vuxW=pgbuer4cfztspctpwahldv10...@mail.gmail.com



Bug#779456: unblock: pylint/1.3.1-3

2015-02-28 Thread Sandro Tosi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package pylint

This upload fixed the pylint integration with emacs, which is currently broken
on testing.

unblock pylint/1.3.1-3

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 
'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -u pylint-1.3.1/debian/changelog pylint-1.3.1/debian/changelog
--- pylint-1.3.1/debian/changelog
+++ pylint-1.3.1/debian/changelog
@@ -1,3 +1,11 @@
+pylint (1.3.1-3) unstable; urgency=medium
+
+  * debian/patches/f4dcd0bd455451e3f358f7171990317b10436055.patch
+- fix pylint integration with emacs; thanks to Guido Günther for the report;
+  Closes: #778890
+
+ -- Sandro Tosi mo...@debian.org  Sat, 28 Feb 2015 20:44:14 +
+
 pylint (1.3.1-2) unstable; urgency=medium
 
   * debian/patches/5733254372edb1df9f72f72c6733608405a99a40.patch
diff -u pylint-1.3.1/debian/patches/series pylint-1.3.1/debian/patches/series
--- pylint-1.3.1/debian/patches/series
+++ pylint-1.3.1/debian/patches/series
@@ -1,0 +2 @@
+f4dcd0bd455451e3f358f7171990317b10436055.patch
only in patch2:
unchanged:
--- pylint-1.3.1.orig/debian/patches/f4dcd0bd455451e3f358f7171990317b10436055.patch
+++ pylint-1.3.1/debian/patches/f4dcd0bd455451e3f358f7171990317b10436055.patch
@@ -0,0 +1,19 @@
+# HG changeset patch
+# User Edgemaster grand.edgemas...@gmail.com
+# Date 1406657851 0
+# Branch Edgemaster/pylintel-missing-dependency-on-tramp-1406657844364
+# Node ID f4dcd0bd455451e3f358f7171990317b10436055
+# Parent  6c0c7d49cd37f6710d5c01273da45b1626f5beee
+pylint.el: Missing dependency on tramp
+
+diff --git a/elisp/pylint.el b/elisp/pylint.el
+--- a/elisp/pylint.el
 b/elisp/pylint.el
+@@ -34,6 +34,7 @@
+ ;;; Code:
+ 
+ (require 'compile)
++(require 'tramp)
+ 
+ (defgroup pylint nil
+   Minor mode for running the Pylint Python checker


Bug#774443: [reportbug/master] when checking the version for a PU upload, pass a list of distributions; thanks to Ivo De Decker for spotting; Addresses: #774443

2015-01-04 Thread Sandro Tosi
tag 774443 pending
thanks

Date:   Sun Jan 4 10:37:47 2015 +
Author: Sandro Tosi mo...@debian.org
Commit ID: 92a62f070c0e5429bacab7d02d35ed87ee5f1831
Commit URL: 
http://anonscm.debian.org/gitweb/?p=reportbug/reportbug.git;a=commitdiff;h=92a62f070c0e5429bacab7d02d35ed87ee5f1831
Patch URL: 
http://anonscm.debian.org/gitweb/?p=reportbug/reportbug.git;a=commitdiff_plain;h=92a62f070c0e5429bacab7d02d35ed87ee5f1831

when checking the version for a PU upload, pass a list of distributions; 
thanks to Ivo De Decker for spotting; Addresses: #774443

  


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/e1y7ihk-0004jp...@moszumanska.debian.org



Bug#774443: unblock: reportbug/6.6.2

2015-01-04 Thread Sandro Tosi
Hi,

On Sat, Jan 3, 2015 at 11:12 AM, Ivo De Decker iv...@debian.org wrote:
 Control: tags -1 moreinfo

 Hi,

 On Fri, Jan 02, 2015 at 08:59:16PM +, Sandro Tosi wrote:
 Please unblock package reportbug

 -if online:
 -if tag == 'wheezy-pu':
 -version = checkversions.get_versions_available(package, 
 timeout, 'wheezy').values()[0]
 -elif tag == 'squeeze-pu':
 -version = checkversions.get_versions_available(package, 
 timeout, 'squeeze').values()[0]
 +if online and tag.endswith('-pu'):
 +version = checkversions.get_versions_available(package, 
 timeout, tag[:-3]).values()[0]

 This doesn't actually seem to be correct. The url that gets checked is this
 one:

you're right! I just uploaded 6.6.3 to fix it.

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/cab4xwxxhr_k5tjasrqqocbemlqvvve8dzmeowm1w7w3xtkj...@mail.gmail.com



Bug#774443: unblock: reportbug/6.6.2

2015-01-02 Thread Sandro Tosi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package reportbug

This upload introduces the jessie-pu tag for release.d.o

unblock reportbug/6.6.2

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 
'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru reportbug-6.6.1/debian/changelog reportbug-6.6.2/debian/changelog
--- reportbug-6.6.1/debian/changelog	2014-12-02 21:53:13.0 +
+++ reportbug-6.6.2/debian/changelog	2015-01-02 20:52:25.0 +
@@ -1,3 +1,11 @@
+reportbug (6.6.2) unstable; urgency=medium
+
+  * reportbug/debbugs.py
+- introduce jessie-pu (removing now EOL squeeze-pu) tag for release.d.o;
+  thanks to Matt Kraai for the report and patch; Closes: #773142
+
+ -- Sandro Tosi mo...@debian.org  Fri, 02 Jan 2015 20:48:12 +
+
 reportbug (6.6.1) unstable; urgency=medium
 
   * reportbug/utils.py
diff -Nru reportbug-6.6.1/reportbug/debbugs.py reportbug-6.6.2/reportbug/debbugs.py
--- reportbug-6.6.1/reportbug/debbugs.py	2014-12-02 21:53:13.0 +
+++ reportbug-6.6.2/reportbug/debbugs.py	2015-01-02 20:52:25.0 +
@@ -399,8 +399,8 @@
 'britney':  testing migration script bugs,
 'transition':   transition tracking,
 'unblock':  unblock requests,
-'squeeze-pu':   squeeze proposed updates requests,
 'wheezy-pu':wheezy proposed updates requests,
+'jessie-pu':jessie proposed updates requests,
 'rm':   Stable/Testing removal requests,
 'other' :   None of the other options,
 }, 'Choose the request type: ', empty_ok=True)
@@ -445,14 +445,11 @@
 else:
 package = info[12] or package
 
-if tag in ('binnmu', 'unblock', 'wheezy-pu', 'squeeze-pu', 'rm'):
+if tag in ('binnmu', 'unblock', 'jessie-pu', 'wheezy-pu', 'rm'):
 # FIXME: pu/rm should lookup the version elsewhere
 version = info and info[0]
-if online:
-if tag == 'wheezy-pu':
-version = checkversions.get_versions_available(package, timeout, 'wheezy').values()[0]
-elif tag == 'squeeze-pu':
-version = checkversions.get_versions_available(package, timeout, 'squeeze').values()[0]
+if online and tag.endswith('-pu'):
+version = checkversions.get_versions_available(package, timeout, tag[:-3]).values()[0]
 if version:
 cont = ui.select_options(
 Latest version seems to be %s, is this the proper one ? % (version),
diff -Nru reportbug-6.6.1/reportbug/__init__.py reportbug-6.6.2/reportbug/__init__.py
--- reportbug-6.6.1/reportbug/__init__.py	2014-12-02 21:53:13.0 +
+++ reportbug-6.6.2/reportbug/__init__.py	2015-01-02 20:52:25.0 +
@@ -25,7 +25,7 @@
 __all__ = ['bugreport', 'utils', 'urlutils', 'checkbuildd', 'checkversions',
'debbugs', 'exceptions', 'submit', 'tempfile']
 
-VERSION_NUMBER = 6.6.1
+VERSION_NUMBER = 6.6.2
 
 VERSION = reportbug +VERSION_NUMBER
 COPYRIGHT = VERSION + '\nCopyright (C) 1999-2008 Chris Lawrence lawre...@debian.org' + \
Binary files /tmp/M2Ea93id_g/reportbug-6.6.1/reportbug/__init__.pyc and /tmp/SozF3ygwqT/reportbug-6.6.2/reportbug/__init__.pyc differ


Bug#774432: unblock: pyogg/1.3+repack-7

2015-01-02 Thread Sandro Tosi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package pyogg

this upload fixes an RC bug in how the transition from directory to symlink was
performed for python-ogg-dbg doc dir

unblock pyogg/1.3+repack-7

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 
'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru pyogg-1.3+repack/debian/changelog pyogg-1.3+repack/debian/changelog
--- pyogg-1.3+repack/debian/changelog	2014-02-22 11:10:10.0 +
+++ pyogg-1.3+repack/debian/changelog	2015-01-02 17:21:02.0 +
@@ -1,3 +1,13 @@
+pyogg (1.3+repack-7) unstable; urgency=medium
+
+  * debian/copyright
+- fix upstream source name
+  * debian/{control, *.maintscript, rules}
+- properly handle the transition from dir to symlink for python-ogg-dbg doc
+  directory; thanks to Andreas Beckmann for the report; Closes: #773191
+
+ -- Sandro Tosi mo...@debian.org  Fri, 02 Jan 2015 17:20:58 +
+
 pyogg (1.3+repack-6) unstable; urgency=low
 
   [ Sandro Tosi ]
diff -Nru pyogg-1.3+repack/debian/control pyogg-1.3+repack/debian/control
--- pyogg-1.3+repack/debian/control	2014-02-22 10:47:36.0 +
+++ pyogg-1.3+repack/debian/control	2015-01-02 17:20:27.0 +
@@ -22,6 +22,7 @@
 Architecture: any
 Section: debug
 Priority: extra
+Pre-Depends: ${misc:Pre-Depends}
 Depends: ${misc:Depends}, python-ogg (= ${binary:Version}), python-dbg, ${shlibs:Depends}
 Description: Python interface to the Ogg library (debug extension)
  This module makes the libogg (Ogg) functions available
diff -Nru pyogg-1.3+repack/debian/copyright pyogg-1.3+repack/debian/copyright
--- pyogg-1.3+repack/debian/copyright	2014-02-22 10:57:27.0 +
+++ pyogg-1.3+repack/debian/copyright	2014-02-22 17:51:21.0 +
@@ -1,5 +1,5 @@
 Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
-Upstream-Name: astroid
+Upstream-Name: pyogg
 Source: http://ekyo.nerim.net/software/pyogg/
 
 Files: *
diff -Nru pyogg-1.3+repack/debian/python-ogg-dbg.maintscript pyogg-1.3+repack/debian/python-ogg-dbg.maintscript
--- pyogg-1.3+repack/debian/python-ogg-dbg.maintscript	1970-01-01 01:00:00.0 +0100
+++ pyogg-1.3+repack/debian/python-ogg-dbg.maintscript	2015-01-02 17:20:27.0 +
@@ -0,0 +1 @@
+dir_to_symlink /usr/share/doc/python-ogg-dbg python-ogg
diff -Nru pyogg-1.3+repack/debian/rules pyogg-1.3+repack/debian/rules
--- pyogg-1.3+repack/debian/rules	2014-02-22 10:47:36.0 +
+++ pyogg-1.3+repack/debian/rules	2015-01-02 17:20:27.0 +
@@ -44,5 +44,4 @@
 endif
 
 override_dh_installdocs:
-	dh_installdocs
-	dh_installdocs -A --link-doc=python-ogg
+	dh_installdocs --link-doc=python-ogg


Bug#767781: unblock: matplotlib/1.4.2-3

2014-12-17 Thread Sandro Tosi
 Looks like this got lost among the floorboards, sorry about that. No, the
 unblock is not realistic right now; could you pick targetted fixes please?

I will (but sadly not before next week), but I hope you do realize no
one has ever run or tested mpl 1.3.1 with WX3.0.

Thanks  Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/cab4xwxy9cu-e3jfvdx05rnuk0zsyph8oskunbhwrbeuj33z...@mail.gmail.com



Re: Bug#773142: reportbug: add support for jessie-pu

2014-12-17 Thread Sandro Tosi
Hello,
thanks for the report.

On Sun, Dec 14, 2014 at 11:27 PM, Matt Kraai kr...@ftbfs.org wrote:
 jcristau:  hmm should probably update reportbug to handle jessie-pu at some
 point
 adsb:  ack

 I've attached a patch that adds support for jessie-pu.

RT: can 'squeeze-pu' be removed at the same time jessie-pu is added?
do you want this fix into Jessie?

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/CAB4XWXyWZw4igm5Ny=eyfrdqyacdvmfdsdfvcig-aqsrbnu...@mail.gmail.com



Bug#772756: unblock: pylint/1.3.1-2

2014-12-10 Thread Sandro Tosi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package pylint

As pre-approved in #772038 I just uploaded pylint with the backport of an
upstream patch to allow users to inspect third-party extensions too, in addition
to standard library ones.

The diff contains also:

- a tightened dep on astroid, needed to select the proper patch (they are twin
  packages)
- an explict depends on quilt (+ rules) as I thought it would be better than
  switching the source format at this stage.

unblock pylint/1.3.1-2

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 
'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -u pylint-1.3.1/debian/changelog pylint-1.3.1/debian/changelog
--- pylint-1.3.1/debian/changelog
+++ pylint-1.3.1/debian/changelog
@@ -1,3 +1,17 @@
+pylint (1.3.1-2) unstable; urgency=medium
+
+  * debian/patches/5733254372edb1df9f72f72c6733608405a99a40.patch
+- backport of --unsafe-load-any-extension and --extension-pkg-whitelist to
+  be able to run pylint even on third-party extensions (and not only on
+  Standard Library ones); Closes: #772018
+  * debian/{control,rules}
+- add quilt to apply the patch
+  * debian/control
+- tighten dep on python-astroid to select the version with the changes
+  needed to fix #772018
+
+ -- Sandro Tosi mo...@debian.org  Wed, 10 Dec 2014 19:42:55 +
+
 pylint (1.3.1-1) unstable; urgency=medium
 
   * New upstream release
diff -u pylint-1.3.1/debian/control pylint-1.3.1/debian/control
--- pylint-1.3.1/debian/control
+++ pylint-1.3.1/debian/control
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Sandro Tosi mo...@debian.org
 Uploaders: Python Applications Packaging Team python-apps-t...@lists.alioth.debian.org
-Build-Depends: debhelper (= 9), python (= 2.6.6-3~), dh-python
+Build-Depends: debhelper (= 9), python (= 2.6.6-3~), dh-python, quilt
 Build-Depends-Indep: python-logilab-common (= 0.53.0), python-astroid (= 1.2.1), python-unittest2
 Standards-Version: 3.9.6
 XS-Python-Version: = 2.6
@@ -13,7 +13,7 @@
 
 Package: pylint
 Architecture: all
-Depends: ${python:Depends}, ${misc:Depends}, python-logilab-common (= 0.53.0), python-astroid (= 1.2.1)
+Depends: ${python:Depends}, ${misc:Depends}, python-logilab-common (= 0.53.0), python-astroid (= 1.2.1-3~)
 Recommends: python-tk
 Description: Python code static checker and UML diagram generator
  Pylint is a Python source code analyzer which looks for programming
diff -u pylint-1.3.1/debian/rules pylint-1.3.1/debian/rules
--- pylint-1.3.1/debian/rules
+++ pylint-1.3.1/debian/rules
@@ -6,7 +6,7 @@
 PYVERS := $(shell pyversions -s -v)
 
 %:
-	dh $@ --with python2
+	dh $@ --with python2,quilt
 
 override_dh_auto_build:
 	dh_auto_build
only in patch2:
unchanged:
--- pylint-1.3.1.orig/debian/patches/5733254372edb1df9f72f72c6733608405a99a40.patch
+++ pylint-1.3.1/debian/patches/5733254372edb1df9f72f72c6733608405a99a40.patch
@@ -0,0 +1,55 @@
+# HG changeset patch
+# User Torsten Marek shlo...@gmail.com
+# Date 1416661887 -3600
+# Node ID 5733254372edb1df9f72f72c6733608405a99a40
+# Parent  f8fa8f2bd2bbe88a2c4f6d87d3cab200ca0160c6
+Add options to control extension loading in astroid.
+
+--- a/ChangeLog
 b/ChangeLog
+@@ -1,6 +1,13 @@
+ ChangeLog for Pylint
+ 
+ 
++* Added new options for controlling the loading of C extensions.
++  By default, only C extensions from the stdlib will be loaded
++  into the active Python interpreter for inspection, because they
++  can run arbitrary code on import. The option 
++  `--extension-pkg-whitelist` can be used to specify modules
++  or packages that are safe to load.
++
+ 2014-08-24 -- 1.3.1
+ 
+ * Fix a false positive with string formatting checker, when
+--- a/lint.py
 b/lint.py
+@@ -275,6 +275,20 @@ class PyLinter(OptionsManagerMixIn, Mess
+ 
+ ('include-ids', _deprecated_option('i', 'yn')),
+ ('symbols', _deprecated_option('s', 'yn')),
++
++('unsafe-load-any-extension',
++ {'type': 'yn', 'metavar': 'yn', 'default': False, 'hide': True,
++  'help': ('Allow loading of arbitrary C extensions. Extensions'
++   ' are imported into the active Python interpreter and'
++   ' may run arbitrary code.')}),
++
++('extension-pkg-whitelist',
++  {'type': 'csv', 'metavar': 'pkg[,pkg]', 'default': [],
++   'help': ('A comma-separated list of package or module names'
++' from where C extensions may be loaded. Extensions

Bug#772594: unblock: astroid/1.2.1-3

2014-12-08 Thread Sandro Tosi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package astroid

As previously pre-approved in #772038, please unblock astroid, this fix is
needed to improve the fix at #591676 in order to allow users to load extensions
if the want to (hence bringing back an-par at functionaly level what pylint was
before, and as upstream have decided to evolve it).

unblock astroid/1.2.1-3

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 
'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru astroid-1.2.1/debian/changelog astroid-1.2.1/debian/changelog
--- astroid-1.2.1/debian/changelog	2014-11-23 13:36:47.0 +
+++ astroid-1.2.1/debian/changelog	2014-12-08 21:43:06.0 +
@@ -1,3 +1,11 @@
+astroid (1.2.1-3) unstable; urgency=medium
+
+  * debian/patches/afea46c0380956213976db2ce0f1e8f3cf6a0abc.patch
+- enable fine-grained control over extensions loading; this fix is needed
+  after #591676 fix; Addresses: #772018
+
+ -- Sandro Tosi mo...@debian.org  Mon, 08 Dec 2014 21:43:04 +
+
 astroid (1.2.1-2) unstable; urgency=medium
 
   * debian/patches/e24cacb15e2e152db155fdca9197a8d1bf9ce235.patch
diff -Nru astroid-1.2.1/debian/patches/afea46c0380956213976db2ce0f1e8f3cf6a0abc.patch astroid-1.2.1/debian/patches/afea46c0380956213976db2ce0f1e8f3cf6a0abc.patch
--- astroid-1.2.1/debian/patches/afea46c0380956213976db2ce0f1e8f3cf6a0abc.patch	1970-01-01 01:00:00.0 +0100
+++ astroid-1.2.1/debian/patches/afea46c0380956213976db2ce0f1e8f3cf6a0abc.patch	2014-12-08 21:34:50.0 +
@@ -0,0 +1,44 @@
+# HG changeset patch
+# User Torsten Marek shlo...@gmail.com
+# Date 1416661998 -3600
+# Node ID afea46c0380956213976db2ce0f1e8f3cf6a0abc
+# Parent  c9c283ee85618a5e3a0701dac0925804a73ec4b6
+Add support for more fine-grained control over extension loading.
+
+--- a/manager.py
 b/manager.py
+@@ -86,6 +86,8 @@ class AstroidManager(OptionsProviderMixI
+ self.astroid_cache = {}
+ self._mod_file_cache = {}
+ self.transforms = {}
++self.always_load_extensions = False
++self.extension_package_whitelist = set()
+ 
+ def ast_from_file(self, filepath, modname=None, fallback=True, source=False):
+ given a module name, return the astroid object
+@@ -113,6 +115,16 @@ class AstroidManager(OptionsProviderMixI
+ from astroid.builder import AstroidBuilder
+ return AstroidBuilder(self).string_build('', modname)
+ 
++def _can_load_extension(self, modname):
++if self.always_load_extensions:
++return True
++if modutils.is_standard_module(modname):
++return True
++parts = modname.split('.')
++return any(
++'.'.join(parts[:x]) in self.extension_package_whitelist
++for x in range(1, len(parts) + 1))
++
+ def ast_from_module_name(self, modname, context_file=None):
+ given a module name, return the astroid object
+ if modname in self.astroid_cache:
+@@ -129,7 +141,7 @@ class AstroidManager(OptionsProviderMixI
+ if module is not None:
+ return module
+ elif mp_type in (imp.C_BUILTIN, imp.C_EXTENSION):
+-if mp_type == imp.C_EXTENSION and not modutils.is_standard_module(modname):
++if mp_type == imp.C_EXTENSION and not self._can_load_extension(modname): 
+ return self._build_stub_module(modname)
+ try:
+ module = modutils.load_module_from_name(modname)
diff -Nru astroid-1.2.1/debian/patches/series astroid-1.2.1/debian/patches/series
--- astroid-1.2.1/debian/patches/series	2014-11-23 13:36:27.0 +
+++ astroid-1.2.1/debian/patches/series	2014-12-08 21:34:50.0 +
@@ -1 +1,2 @@
 e24cacb15e2e152db155fdca9197a8d1bf9ce235.patch
+afea46c0380956213976db2ce0f1e8f3cf6a0abc.patch


Bug#772038: pre-approval for astroid + pylint

2014-12-04 Thread Sandro Tosi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Hello,
the latest update to astroid 1.2.1-2 (to remove the ability of pylint
(thru astroid) to import and execute python extensions) has a drawback
in BTS#772018

```
Since the upload of python-astroid 1.2.1-2, pylint is unusable on
projects using C extensions. Since this affects a number of commonly
used 3rd party modules (numpy, PyQT, python-gtk, etc.) this will
severely restricts the usablity of pylint in jessie.

This is fixed in pylint 1.4 and astroid 1.3.2 with the following
patches:

https://bitbucket.org/logilab/astroid/commits/afea46c03809
https://bitbucket.org/logilab/pylint/commits/5733254372ed
```

So I'm asking if you would accept the uploads for pylint and astroid
with the 2 patches mentioned above.

Regards,
Sandro


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/cab4xwxzdhwqvculwgmhw6orswtfco_3qt453yzv2dsj9m_e...@mail.gmail.com



Bug#771856: unblock: reportbug/6.6.1

2014-12-02 Thread Sandro Tosi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package reportbug

This update fixes these bugs:

- a small issue when displaying the foreing archs when more than 1 is available
- add the init system information to bug template
- add the 'newcomer' tag (tests for this are a bit of a mess, sorry about it)

unblock reportbug/6.6.1

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 
'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru reportbug-6.6.0/debian/changelog reportbug-6.6.1/debian/changelog
--- reportbug-6.6.0/debian/changelog	2014-10-29 00:36:13.0 +
+++ reportbug-6.6.1/debian/changelog	2014-12-02 21:53:13.0 +
@@ -1,3 +1,17 @@
+reportbug (6.6.1) unstable; urgency=medium
+
+  * reportbug/utils.py
+- don't split multiarch information on multiple lines; thanks to James
+  Cowgill for the report; Closes: #759690
+  * reportbug/{bugreport.py, utils.py}
+- include init system information in bug reports; thanks to Yves-Alexis
+  Perez for the report and debian-devel ml for suggestions and inputs;
+  Closes #741930
+  * reportbug/debbugs.py
+- add 'newcomer' tag
+
+ -- Sandro Tosi mo...@debian.org  Tue, 02 Dec 2014 21:52:57 +
+
 reportbug (6.6.0) unstable; urgency=medium
 
   * bin/reportbug, man/reportbug.1 share/reportbug.el
diff -Nru reportbug-6.6.0/reportbug/bugreport.py reportbug-6.6.1/reportbug/bugreport.py
--- reportbug-6.6.0/reportbug/bugreport.py	2014-10-29 00:36:13.0 +
+++ reportbug-6.6.1/reportbug/bugreport.py	2014-12-02 21:53:13.0 +
@@ -80,6 +80,7 @@
 un = os.uname()
 debinfo = u''
 shellpath = utils.realpath('/bin/sh')
+init = utils.get_init_system()
 
 locinfo = []
 langsetting = os.environ.get('LANG', 'C')
@@ -174,6 +175,8 @@
 debinfo += u'Locale: %s\n' % locinfo
 if shellpath != '/bin/sh':
 debinfo += u'Shell: /bin/sh linked to %s\n' % shellpath
+if init:
+debinfo += u'Init: %s\n' % init
 
 # Don't include system info for certain packages
 if self.sysinfo:
Binary files /tmp/K97uUNl2T2/reportbug-6.6.0/reportbug/bugreport.pyc and /tmp/DGMmGZ0yUt/reportbug-6.6.1/reportbug/bugreport.pyc differ
diff -Nru reportbug-6.6.0/reportbug/debbugs.py reportbug-6.6.1/reportbug/debbugs.py
--- reportbug-6.6.0/reportbug/debbugs.py	2014-10-29 00:36:13.0 +
+++ reportbug-6.6.1/reportbug/debbugs.py	2014-12-02 21:53:13.0 +
@@ -793,7 +793,8 @@
 'd-i' : 'This bug is relevant to the development of debian-installer.',
 'ipv6' : 'This bug affects support for Internet Protocol version 6.',
 'lfs' : 'This bug affects support for large files (over 2 gigabytes).',
-'l10n' : 'This bug reports a localization/internationalization issue.'
+'l10n' : 'This bug reports a localization/internationalization issue.',
+'newcomer' : 'This bug has a known solution but the maintainer requests someone else implement it.',
 }
 
 def get_tags(severity='', mode=utils.MODE_NOVICE):
Binary files /tmp/K97uUNl2T2/reportbug-6.6.0/reportbug/debbugs.pyc and /tmp/DGMmGZ0yUt/reportbug-6.6.1/reportbug/debbugs.pyc differ
diff -Nru reportbug-6.6.0/reportbug/__init__.py reportbug-6.6.1/reportbug/__init__.py
--- reportbug-6.6.0/reportbug/__init__.py	2014-10-29 00:36:13.0 +
+++ reportbug-6.6.1/reportbug/__init__.py	2014-12-02 21:53:13.0 +
@@ -25,7 +25,7 @@
 __all__ = ['bugreport', 'utils', 'urlutils', 'checkbuildd', 'checkversions',
'debbugs', 'exceptions', 'submit', 'tempfile']
 
-VERSION_NUMBER = 6.6.0
+VERSION_NUMBER = 6.6.1
 
 VERSION = reportbug +VERSION_NUMBER
 COPYRIGHT = VERSION + '\nCopyright (C) 1999-2008 Chris Lawrence lawre...@debian.org' + \
Binary files /tmp/K97uUNl2T2/reportbug-6.6.0/reportbug/__init__.pyc and /tmp/DGMmGZ0yUt/reportbug-6.6.1/reportbug/__init__.pyc differ
diff -Nru reportbug-6.6.0/reportbug/utils.py reportbug-6.6.1/reportbug/utils.py
--- reportbug-6.6.0/reportbug/utils.py	2014-10-29 00:36:13.0 +
+++ reportbug-6.6.1/reportbug/utils.py	2014-12-02 21:53:13.0 +
@@ -765,7 +765,8 @@
 return arch
 
 def get_multiarch():
-return commands.getoutput('COLUMNS=79 dpkg --print-foreign-architectures 2/dev/null')
+out = commands.getoutput('COLUMNS=79 dpkg --print-foreign-architectures 2/dev/null')
+return ', '.join(out.splitlines())
 
 def generate_blank_report(package, pkgversion, severity, justification,
   depinfo, confinfo, foundfile='', incfiles='',
@@ -1225,3 +1226,17 @@
 pkg_re = re.compile

Bug#770708: unblock: astroid/1.2.1-2

2014-11-23 Thread Sandro Tosi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package astroid

This upload fixes a bug which affects pylint, which would let it import (and
this possibly execute code) when checking python extensions (which is agains the
contract with pylint users to be a static checker).

unblock astroid/1.2.1-2

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 
'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru astroid-1.2.1/debian/changelog astroid-1.2.1/debian/changelog
--- astroid-1.2.1/debian/changelog	2014-11-02 14:47:31.0 +
+++ astroid-1.2.1/debian/changelog	2014-11-23 13:36:47.0 +
@@ -1,3 +1,12 @@
+astroid (1.2.1-2) unstable; urgency=medium
+
+  * debian/patches/e24cacb15e2e152db155fdca9197a8d1bf9ce235.patch
+- Never load C extensions that are not from the standard library and also
+  never load any compiled Python files; thanks to Jakub Wilk for the report;
+  Closes: #591676
+
+ -- Sandro Tosi mo...@debian.org  Sun, 23 Nov 2014 13:36:44 +
+
 astroid (1.2.1-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru astroid-1.2.1/debian/patches/e24cacb15e2e152db155fdca9197a8d1bf9ce235.patch astroid-1.2.1/debian/patches/e24cacb15e2e152db155fdca9197a8d1bf9ce235.patch
--- astroid-1.2.1/debian/patches/e24cacb15e2e152db155fdca9197a8d1bf9ce235.patch	1970-01-01 01:00:00.0 +0100
+++ astroid-1.2.1/debian/patches/e24cacb15e2e152db155fdca9197a8d1bf9ce235.patch	2014-11-23 13:36:27.0 +
@@ -0,0 +1,383 @@
+# HG changeset patch
+# User Torsten Marek shlo...@gmail.com
+# Date 1415534030 -3600
+# Node ID e24cacb15e2e152db155fdca9197a8d1bf9ce235
+# Parent  8b1f838e213786440a65bbfcb2ba4f743caa19ca
+Never load C extensions that are not from the standard library and also never load any compiled Python files.
+
+Fixes pylint issue #347.
+
+--- a/manager.py
 b/manager.py
+@@ -22,16 +22,16 @@ from various source and using a cache of
+ 
+ __docformat__ = restructuredtext en
+ 
++import imp
+ import os
+ from os.path import dirname, join, isdir, exists
+ from warnings import warn
++import zipimport
+ 
+ from logilab.common.configuration import OptionsProviderMixIn
+ 
+ from astroid.exceptions import AstroidBuildingException
+-from astroid.modutils import NoSourceFile, is_python_source, \
+- file_from_modpath, load_module_from_name, modpath_from_file, \
+- get_module_files, get_source_file, zipimport
++from astroid import modutils
+ 
+ 
+ def astroid_wrapper(func, modname):
+@@ -90,13 +90,13 @@ class AstroidManager(OptionsProviderMixI
+ def ast_from_file(self, filepath, modname=None, fallback=True, source=False):
+ given a module name, return the astroid object
+ try:
+-filepath = get_source_file(filepath, include_no_ext=True)
++filepath = modutils.get_source_file(filepath, include_no_ext=True)
+ source = True
+-except NoSourceFile:
++except modutils.NoSourceFile:
+ pass
+ if modname is None:
+ try:
+-modname = '.'.join(modpath_from_file(filepath))
++modname = '.'.join(modutils.modpath_from_file(filepath))
+ except ImportError:
+ modname = filepath
+ if modname in self.astroid_cache and self.astroid_cache[modname].file == filepath:
+@@ -109,29 +109,36 @@ class AstroidManager(OptionsProviderMixI
+ raise AstroidBuildingException('unable to get astroid for file %s' %
+filepath)
+ 
++def _build_stub_module(self, modname):
++from astroid.builder import AstroidBuilder
++return AstroidBuilder(self).string_build('', modname)
++
+ def ast_from_module_name(self, modname, context_file=None):
+ given a module name, return the astroid object
+ if modname in self.astroid_cache:
+ return self.astroid_cache[modname]
+ if modname == '__main__':
+-from astroid.builder import AstroidBuilder
+-return AstroidBuilder(self).string_build('', modname)
++return self._build_stub_module(modname)
+ old_cwd = os.getcwd()
+ if context_file:
+ os.chdir(dirname(context_file))
+ try:
+-filepath = self.file_from_module_name(modname, context_file)
+-if filepath is not None and not is_python_source(filepath):
++filepath, mp_type = self.file_from_module_name(modname, context_file)
++if mp_type == modutils.PY_ZIPMODULE:
+ module = self.zip_import_data(filepath)
+ if module is not None

Bug#770708: unblock: astroid/1.2.1-2

2014-11-23 Thread Sandro Tosi
Hello Julien,

On Sun, Nov 23, 2014 at 3:45 PM, Julien Cristau jcris...@debian.org wrote:
 On Sun, Nov 23, 2014 at 13:43:15 +, Sandro Tosi wrote:

 Please unblock package astroid

 This upload fixes a bug which affects pylint, which would let it import (and
 this possibly execute code) when checking python extensions (which is agains 
 the
 contract with pylint users to be a static checker).

 FWIW I disagree that that was a bug, and it's behaved that way forever,

I see your point, I can only reply with what upstream (and I know the
subtle line in that) thinks[1] of it:

This is important. In some cases, Pylint will import a module if and

only if it cannot find its source, which could lead to failures like
crashes from user code or segfault. We should probably give up on this
behavior, even if we lose support for inferring certain types of
objects, in order to be truly a static checker.

[1] https://lists.logilab.org/pipermail/pylint-dev/2014-November/15.html

 so I don't think it needs to get a freeze exception.

I'm ok with whatever RT decides.

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/CAB4XWXxTUGS14iCiVzOuM=kkoqv+typ1wm6t6yhtg+so6lp...@mail.gmail.com



Bug#770523: unblock: python-regex/0.1.20141024-2

2014-11-22 Thread Sandro Tosi
 Looks good, but I believe you need a Pre-Depends on dpkg for that (or a
 ${misc:Pre-Depends})

I didnt consider that you require a newer version of dpkg than stable;
just uploaded -3 with the P-D (debdiff attached against testing),
sorry about that.

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi


python-regex_0.1.20141024-1_0.1.20141024-3.debdiff
Description: Binary data


Bug#767781: unblock: matplotlib/1.4.2-3

2014-11-21 Thread Sandro Tosi
Hi,

 Would it be possible for you to provide us with a targeted RC bug fix?

Is there really no chance to accept the new release? It is really a
superior release than what we have in Jessie right now, it has proven
its stability, and it missed the cut just due to a race condition in
the build process (which upstream fixed in less than 1 day) and not a
grave bug in its code.

Of course, if the answer is still no, I will upload to tpu a targeted
fix, but please consider what written above.

Thanks for considering,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/CAB4XWXyrW2wrpk2Y4kRVFM=_7n8_3psm7ee_2pumgprg9dk...@mail.gmail.com



Bug#770523: unblock: python-regex/0.1.20141024-2

2014-11-21 Thread Sandro Tosi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package python-regex

This upload fixes and RC bug, due to the switch from dir to symlink for doc

unblock python-regex/0.1.20141024-2

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 
'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru python-regex-0.1.20141024/debian/changelog python-regex-0.1.20141024/debian/changelog
--- python-regex-0.1.20141024/debian/changelog	2014-10-26 10:01:03.0 +
+++ python-regex-0.1.20141024/debian/changelog	2014-11-21 23:54:06.0 +
@@ -1,3 +1,11 @@
+python-regex (0.1.20141024-2) unstable; urgency=medium
+
+  * debian/*.maintscript
+- properly handle the doc directories switch to symlinks; thanks to Andreas
+  Beckmann for the report; Closes: #768238
+
+ -- Sandro Tosi mo...@debian.org  Fri, 21 Nov 2014 23:53:10 +
+
 python-regex (0.1.20141024-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru python-regex-0.1.20141024/debian/python3-regex-dbg.maintscript python-regex-0.1.20141024/debian/python3-regex-dbg.maintscript
--- python-regex-0.1.20141024/debian/python3-regex-dbg.maintscript	1970-01-01 01:00:00.0 +0100
+++ python-regex-0.1.20141024/debian/python3-regex-dbg.maintscript	2014-11-21 23:53:00.0 +
@@ -0,0 +1 @@
+dir_to_symlink /usr/share/doc/python3-regex-dbg python-regex
diff -Nru python-regex-0.1.20141024/debian/python3-regex.maintscript python-regex-0.1.20141024/debian/python3-regex.maintscript
--- python-regex-0.1.20141024/debian/python3-regex.maintscript	1970-01-01 01:00:00.0 +0100
+++ python-regex-0.1.20141024/debian/python3-regex.maintscript	2014-11-21 23:53:00.0 +
@@ -0,0 +1 @@
+dir_to_symlink /usr/share/doc/python3-regex python-regex
diff -Nru python-regex-0.1.20141024/debian/python-regex-dbg.maintscript python-regex-0.1.20141024/debian/python-regex-dbg.maintscript
--- python-regex-0.1.20141024/debian/python-regex-dbg.maintscript	1970-01-01 01:00:00.0 +0100
+++ python-regex-0.1.20141024/debian/python-regex-dbg.maintscript	2014-11-21 23:53:00.0 +
@@ -0,0 +1 @@
+dir_to_symlink /usr/share/doc/python-regex-dbg python-regex


Bug#769964: unblock: pyvorbis/1.5-4

2014-11-17 Thread Sandro Tosi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package pyvorbis

The upload fixes a regression introduced during Jessie development period
regarding -dbg doc directory, which now has been set back to a symlink, as in
Wheezy

unblock pyvorbis/1.5-4

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 
'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru pyvorbis-1.5/debian/changelog pyvorbis-1.5/debian/changelog
--- pyvorbis-1.5/debian/changelog	2014-02-22 17:57:23.0 +
+++ pyvorbis-1.5/debian/changelog	2014-11-17 22:36:55.0 +
@@ -1,3 +1,12 @@
+pyvorbis (1.5-4) unstable; urgency=medium
+
+  * debian/rules
+- correctly link -dbg doc directory to the main package one; thanks to
+  Andreas Beckmann for the report and to Jean-Michel Nirgal Vourgère for the
+  first patch; Closes: #768285
+
+ -- Sandro Tosi mo...@debian.org  Mon, 17 Nov 2014 22:36:50 +
+
 pyvorbis (1.5-3) unstable; urgency=low
 
   [ Jakub Wilk ]
diff -Nru pyvorbis-1.5/debian/rules pyvorbis-1.5/debian/rules
--- pyvorbis-1.5/debian/rules	2014-02-22 17:46:42.0 +
+++ pyvorbis-1.5/debian/rules	2014-11-17 22:35:49.0 +
@@ -47,8 +47,7 @@
 endif
 
 override_dh_installdocs:
-	dh_installdocs
-	dh_installdocs -A --link-doc=python-pyvorbis
+	dh_installdocs --link-doc=python-pyvorbis
 
 override_dh_compress:
 	dh_compress -X.py


Bug#767781: unblock: matplotlib/1.4.2-3

2014-11-12 Thread Sandro Tosi
Hello,

On Sun, Nov 2, 2014 at 6:09 PM, Sandro Tosi mo...@debian.org wrote:
 1.4 series is the latest release of mpl, and it will be the one upstream will
 support during Jessie lifecycle. It has been in Debian since Sept (in
 experimental) and it would have made the cut for the freeze if not for some
 uploads for upstream bugfixes and build system deadlock fixes.

 This version is built on all the buildd except mips, but that arch has a long
 queue, with big packages still to build before mpl.

 Please consider unblocking it.

 unblock matplotlib/1.4.2-3

Just a gentle ping, to make sure this request was not lost in the huge
unblocks stream. Another thing to point out about this upload is the
migration from wx 2.8 to 3.0

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/cab4xwxwqdwu4jhoqixxuogvfetrsuqtmqz8dnbnydfcrxag...@mail.gmail.com



Bug#768387: unblock: pylint/1.3.1-1

2014-11-06 Thread Sandro Tosi
:08.0 +
@@ -1,3 +1,15 @@
+pylint (1.3.1-1) unstable; urgency=medium
+
+  * New upstream release
+  * debian/rules
+- force execution of test suite
+  * debian/control
+- bump version of astroid to minimum 1.2.1
+- bump Standards-Version to 3.9.6 (no changes needed)
+- add dh-python to b-d
+
+ -- Sandro Tosi mo...@debian.org  Thu, 06 Nov 2014 23:53:16 +
+
 pylint (1.3.0-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru pylint-1.3.0/debian/control pylint-1.3.1/debian/control
--- pylint-1.3.0/debian/control	2014-11-07 00:02:08.0 +
+++ pylint-1.3.1/debian/control	2014-11-07 00:02:08.0 +
@@ -3,9 +3,9 @@
 Priority: optional
 Maintainer: Sandro Tosi mo...@debian.org
 Uploaders: Python Applications Packaging Team python-apps-t...@lists.alioth.debian.org
-Build-Depends: debhelper (= 9), python (= 2.6.6-3~)
-Build-Depends-Indep: python-logilab-common (= 0.53.0), python-astroid (= 1.2.0), python-unittest2
-Standards-Version: 3.9.5
+Build-Depends: debhelper (= 9), python (= 2.6.6-3~), dh-python
+Build-Depends-Indep: python-logilab-common (= 0.53.0), python-astroid (= 1.2.1), python-unittest2
+Standards-Version: 3.9.6
 XS-Python-Version: = 2.6
 Homepage: http://www.pylint.org/
 Vcs-Svn: svn://anonscm.debian.org/python-apps/packages/pylint/trunk/
@@ -13,7 +13,7 @@
 
 Package: pylint
 Architecture: all
-Depends: ${python:Depends}, ${misc:Depends}, python-logilab-common (= 0.53.0), python-astroid (= 1.2.0)
+Depends: ${python:Depends}, ${misc:Depends}, python-logilab-common (= 0.53.0), python-astroid (= 1.2.1)
 Recommends: python-tk
 Description: Python code static checker and UML diagram generator
  Pylint is a Python source code analyzer which looks for programming
diff -Nru pylint-1.3.0/debian/rules pylint-1.3.1/debian/rules
--- pylint-1.3.0/debian/rules	2014-11-07 00:02:08.0 +
+++ pylint-1.3.1/debian/rules	2014-11-07 00:02:08.0 +
@@ -15,7 +15,7 @@
 override_dh_auto_test:
 ifeq (,$(findstring nocheck,$(DEB_BUILD_OPTIONS)))
 	# use the default python version to select the script dir to run the tests
-	-./test/fulltest.sh $(PYVERS)
+	-/bin/sh ./test/fulltest.sh $(PYVERS)
 endif
 
 
diff -Nru pylint-1.3.0/DEPENDS pylint-1.3.1/DEPENDS
--- pylint-1.3.0/DEPENDS	2014-07-26 07:45:30.0 +0100
+++ pylint-1.3.1/DEPENDS	2014-08-24 22:07:48.0 +0100
@@ -1,3 +1,3 @@
 python-logilab-common (= 0.19.0)
-python-astroid (= 1.2.0)
+python-astroid (= 1.2.1)
 python-tk
diff -Nru pylint-1.3.0/MANIFEST.in pylint-1.3.1/MANIFEST.in
--- pylint-1.3.0/MANIFEST.in	2014-07-26 07:44:30.0 +0100
+++ pylint-1.3.1/MANIFEST.in	2014-08-24 21:58:08.0 +0100
@@ -7,7 +7,7 @@
 include elisp/startup elisp/*.el
 include man/*.1
 recursive-include doc *.rst *.jpeg Makefile *.html *.py
-recursive-include test *.py *.txt *.dot *.sh *.args
+recursive-include test *.py *.txt *.dot *.sh *.rc
 include test/input/similar* 
 include test/input/noext
 include test/data/ascript
diff -Nru pylint-1.3.0/PKG-INFO pylint-1.3.1/PKG-INFO
--- pylint-1.3.0/PKG-INFO	2014-07-26 08:29:40.0 +0100
+++ pylint-1.3.1/PKG-INFO	2014-08-24 22:20:42.0 +0100
@@ -1,6 +1,6 @@
 Metadata-Version: 1.1
 Name: pylint
-Version: 1.3.0
+Version: 1.3.1
 Summary: python code static checker
 Home-page: http://www.pylint.org
 Author: Logilab
diff -Nru pylint-1.3.0/__pkginfo__.py pylint-1.3.1/__pkginfo__.py
--- pylint-1.3.0/__pkginfo__.py	2014-07-26 07:46:10.0 +0100
+++ pylint-1.3.1/__pkginfo__.py	2014-08-24 22:06:36.0 +0100
@@ -19,14 +19,14 @@
 
 modname = distname = 'pylint'
 
-numversion = (1, 3, 0)
+numversion = (1, 3, 1)
 version = '.'.join([str(num) for num in numversion])
 
 if sys.version_info  (2, 6):
-install_requires = ['logilab-common = 0.53.0', 'astroid = 1.1',
+install_requires = ['logilab-common = 0.53.0', 'astroid = 1.2.1',
 'StringFormat']
 else:
-install_requires = ['logilab-common = 0.53.0', 'astroid = 1.1']
+install_requires = ['logilab-common = 0.53.0', 'astroid = 1.2.1']
 
 license = 'GPL'
 description = python code static checker
diff -Nru pylint-1.3.0/pylint.egg-info/entry_points.txt pylint-1.3.1/pylint.egg-info/entry_points.txt
--- pylint-1.3.0/pylint.egg-info/entry_points.txt	2014-07-26 08:29:30.0 +0100
+++ pylint-1.3.1/pylint.egg-info/entry_points.txt	2014-08-24 22:20:24.0 +0100
@@ -1,7 +1,7 @@
 [console_scripts]
-pylint = pylint:run_pylint
+pylint-gui = pylint:run_pylint_gui
 pyreverse = pylint:run_pyreverse
 epylint = pylint:run_epylint
 symilar = pylint:run_symilar
-pylint-gui = pylint:run_pylint_gui
+pylint = pylint:run_pylint
 
diff -Nru pylint-1.3.0/pylint.egg-info/PKG-INFO pylint-1.3.1/pylint.egg-info/PKG-INFO
--- pylint-1.3.0/pylint.egg-info/PKG-INFO	2014-07-26 08:29:30.0 +0100
+++ pylint-1.3.1/pylint.egg-info/PKG-INFO	2014-08-24 22:20:24.0 +0100
@@ -1,6 +1,6 @@
 Metadata-Version: 1.1
 Name: pylint
-Version: 1.3.0
+Version: 1.3.1
 Summary: python code

Bug#767984: unblock: python-levenshtein/0.11.2-2

2014-11-03 Thread Sandro Tosi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package python-levenshtein

This new package includes a patch from upstream closing a long-standing bug in
the code, and thus preventing from crashing when using seq*() functions.

unblock python-levenshtein/0.11.2-2

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 
'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20141103214355.20401.21165.report...@oracle.matrix.int



Bug#767778: unblock: astroid/1.2.1-1

2014-11-02 Thread Sandro Tosi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package astroid

This is a bugfix release and it is required by pylint 1.3.1 (still to be
uploaded, and another bugfix release, for which I will open another bug when
landed in sid).

unblock astroid/1.2.1-1

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 
'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20141102174417.28904.85836.report...@oracle.matrix.int



Bug#767781: unblock: matplotlib/1.4.2-3

2014-11-02 Thread Sandro Tosi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package matplotlib

1.4 series is the latest release of mpl, and it will be the one upstream will
support during Jessie lifecycle. It has been in Debian since Sept (in
experimental) and it would have made the cut for the freeze if not for some
uploads for upstream bugfixes and build system deadlock fixes.

This version is built on all the buildd except mips, but that arch has a long
queue, with big packages still to build before mpl.

Please consider unblocking it.

unblock matplotlib/1.4.2-3

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 
'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20141102180943.31733.63810.report...@oracle.matrix.int



Bug#767799: unblock: python-graph/1.8.2-6

2014-11-02 Thread Sandro Tosi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package python-graph

The package fixes a FTBFS if build twice in a row, switch to dh_python2 (the
preferred helper for python) and removes a spurious dependencies on an
not-existing package.

unblock python-graph/1.8.2-6

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 
'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20141102183754.1007.49842.report...@oracle.matrix.int



Bug#767841: unblock: python-pygraphviz/1.3~rc2-1

2014-11-02 Thread Sandro Tosi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package python-pygraphviz

This new RC release contains fixes to enable unittests execution at build time
and small other bug fixes.

unblock python-pygraphviz/1.3~rc2-1

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 
'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20141102215058.13314.44180.report...@oracle.matrix.int



Re: reportbug 6.6.0 MIGRATED to testing

2014-10-31 Thread Sandro Tosi
On Fri, Oct 31, 2014 at 4:39 PM, Debian testing watch
nore...@release.debian.org wrote:
 FYI: The status of the reportbug source package
 in Debian's testing distribution has changed.

   Previous version: 6.5.1
   Current version:  6.6.0

Thanks RT! I was about to file an unblock bug you came at it first :)

-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/cab4xwxx4i6ldua3zue0wo7bndcjcpe5brgkcqvf_souwmc5...@mail.gmail.com



Re: [Reportbug-maint] Bug#736179: opu: package spip/2.1.1-3squeeze8

2014-01-21 Thread Sandro Tosi
 #707631.  Seems reportbug is unmaintained at the moment though :(

I'm working on reducing the reportbug bugs backlog ATM - #707631 will
be fixed soon.

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/cab4xwxwhp+cgrbfv6b5igfsk0qfom3y288qhw81dv5wntn-...@mail.gmail.com



Bug#703860: unblock: reportbug/6.4.4

2013-03-25 Thread Sandro Tosi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package reportbug

This package fixes the crashes seen with GTK+ UI, which impacted several users.

unblock reportbug/6.4.4

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
diff -Nru reportbug-6.4.3/debian/changelog reportbug-6.4.4/debian/changelog
--- reportbug-6.4.3/debian/changelog	2012-08-18 22:50:08.0 +0200
+++ reportbug-6.4.4/debian/changelog	2013-03-12 23:45:53.0 +0100
@@ -1,3 +1,13 @@
+reportbug (6.4.4) unstable; urgency=low
+
+  * reportbug/ui/gtk2_ui.py
+- proper update GTK+ UI from threads, using gobject.idle_add(), possibily
+  fixing the crashes seen with GTK+ reportbug UI; thanks to all the
+  reporters and to Bruno Filipe Oliveira Ramos for the patch;
+  Closes: #620225
+
+ -- Sandro Tosi mo...@debian.org  Tue, 12 Mar 2013 23:45:13 +0100
+
 reportbug (6.4.3) unstable; urgency=low
 
   * reportbug/debbugs.py
diff -Nru reportbug-6.4.3/reportbug/__init__.py reportbug-6.4.4/reportbug/__init__.py
--- reportbug-6.4.3/reportbug/__init__.py	2012-08-18 22:50:08.0 +0200
+++ reportbug-6.4.4/reportbug/__init__.py	2013-03-12 23:45:53.0 +0100
@@ -25,7 +25,7 @@
 __all__ = ['bugreport', 'utils', 'urlutils', 'checkbuildd', 'checkversions',
'debbugs', 'exceptions', 'submit', 'tempfile']
 
-VERSION_NUMBER = 6.4.3
+VERSION_NUMBER = 6.4.4
 
 VERSION = reportbug +VERSION_NUMBER
 COPYRIGHT = VERSION + '\nCopyright (C) 1999-2008 Chris Lawrence lawre...@debian.org' + \
diff -Nru reportbug-6.4.3/reportbug/ui/gtk2_ui.py reportbug-6.4.4/reportbug/ui/gtk2_ui.py
--- reportbug-6.4.3/reportbug/ui/gtk2_ui.py	2012-08-18 22:50:08.0 +0200
+++ reportbug-6.4.4/reportbug/ui/gtk2_ui.py	2013-03-12 23:45:53.0 +0100
@@ -616,7 +616,7 @@
 
 def execute (self, prompt, options=None, force_prompt=False, default=''):
 # Hackish: remove the text needed for textual UIs...
-self.label.set_text (prompt.replace(' (enter Ctrl+c to exit reportbug without reporting a bug)', ''))
+gobject.idle_add (self.label.set_text, prompt.replace(' (enter Ctrl+c to exit reportbug without reporting a bug)', ''))
 self.entry.set_text (default)
 
 if options:
@@ -673,7 +673,7 @@
 def execute (self, prompt):
 self.empty_ok = True
 # The result must be iterable for reportbug even if it's empty and not modified
-self.label.set_text (prompt)
+gobject.idle_add (self.label.set_text, prompt)
 self.buffer.set_text ()
 self.buffer.emit ('changed')
 
@@ -762,7 +762,7 @@
 def execute (self, prompt):
 self.empty_ok = True
 
-self.label.set_text (prompt)
+gobject.idle_add (self.label.set_text, prompt)
 
 self.model = gtk.ListStore (str)
 self.model.connect ('row-changed', self.validate)
@@ -803,7 +803,7 @@
 
 def execute (self, par, options, prompt, default=None, any_ok=False,
  order=None, extras=None, multiple=False):
-self.label.set_text (par)
+gobject.idle_add (self.label.set_text, par)
 
 self.model = gtk.ListStore (str, str)
 self.view.set_model (self.model)
@@ -1011,7 +1011,7 @@
 return matches
 
 def execute (self, buglist, sectitle):
-self.label.set_text (%s. Double-click a bug to retrieve and submit more information. % sectitle)
+gobject.idle_add (self.label.set_text, %s. Double-click a bug to retrieve and submit more information. % sectitle)
 
 self.model = gtk.TreeStore (*([str] * len (self.columns)))
 for category in buglist:
@@ -1089,7 +1089,7 @@
 message = message % args
 # make it all on one line, it will be wrapped at display-time
 message = ' '.join(message.split())
-self.label.set_text (message)
+gobject.idle_add (self.label.set_text, message)
 # Reportbug should use final_message, so emulate it
 if ('99' in message):
 self.set_page_type (gtk.ASSISTANT_PAGE_CONFIRM)
@@ -1215,7 +1215,7 @@
 self.default.grab_focus ()
 
 def execute (self, prompt, menuopts, options):
-self.label.set_text (prompt)
+gobject.idle_add (self.label.set_text, prompt)
 
 buttons = []
 for menuopt in menuopts:
@@ -1294,7 +1294,7 @@
 return vbox
 
 def set_label (self, text):
-self.label.set_text (text)
+gobject.idle_add (self.label.set_text, text)
 
 def reset_label (self):
 self.set_label (This operation may take a while)


Bug#698798: unblock: parallelpython/1.6.2-2

2013-01-23 Thread Sandro Tosi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package parallelpython

i've just uploaded parallelpython as preapproved at: 
http://lists.debian.org/debian-release/2013/01/msg00893.html

unblock parallelpython/1.6.2-2

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.7-trunk-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru parallelpython-1.6.2/debian/changelog parallelpython-1.6.2/debian/changelog
--- parallelpython-1.6.2/debian/changelog	2012-06-07 22:49:53.0 +0200
+++ parallelpython-1.6.2/debian/changelog	2013-01-23 20:10:02.0 +0100
@@ -1,3 +1,11 @@
+parallelpython (1.6.2-2) unstable; urgency=low
+
+  * Invoke ppworker via python -m avoiding addition of /usr/share/pyshared
+to sys.path; thanks to Zbigniew Jędrzejewski-Szmek for the report and to
+Yaroslav Halchenko, Jakub Wilk for the fix; Closes: #620551
+
+ -- Sandro Tosi mo...@debian.org  Wed, 23 Jan 2013 20:09:51 +0100
+
 parallelpython (1.6.2-1) unstable; urgency=low
 
   * New upstream release
diff -Nru parallelpython-1.6.2/debian/patches/30_ppworker_invoke_via-m.patch parallelpython-1.6.2/debian/patches/30_ppworker_invoke_via-m.patch
--- parallelpython-1.6.2/debian/patches/30_ppworker_invoke_via-m.patch	1970-01-01 01:00:00.0 +0100
+++ parallelpython-1.6.2/debian/patches/30_ppworker_invoke_via-m.patch	2013-01-23 20:09:17.0 +0100
@@ -0,0 +1,26 @@
+From: Yaroslav Halchenko deb...@onerussian.com
+Author: Jakub Wilk jw...@debian.org
+Subject: Do not invoke ppworker script directory -- run it via -m option of python
+
+ Invocation of script directly results in Python adding a directory containing
+ the symlink-dereferenced path to the script into the path.  On Debian systems
+ it would result in adding /usr/share/pyshared path to the sys.path breaking
+ import of many modules.
+
+Origin: Debian
+Bug-Debian: http://bugs.debian.org/620551
+Last-Update: 2013-01-22
+
+--- a/pp.py
 b/pp.py
+@@ -127,9 +127,7 @@ class _Task(object):
+ class _Worker(object):
+ Local worker class
+ 
+-command = [sys.executable, -u,
+-os.path.dirname(os.path.abspath(__file__))
+-+ os.sep + ppworker.py]
++command = [sys.executable, -u, -m , ppworker]
+ 
+ command.append(2/dev/null)
+ 
diff -Nru parallelpython-1.6.2/debian/patches/series parallelpython-1.6.2/debian/patches/series
--- parallelpython-1.6.2/debian/patches/series	2011-09-15 23:35:22.0 +0200
+++ parallelpython-1.6.2/debian/patches/series	2013-01-23 20:09:17.0 +0100
@@ -1,2 +1,3 @@
 10_remove_default_password.patch
 20_hyphen-used-as-minus-sign.patch
+30_ppworker_invoke_via-m.patch


Bug#696716: unblock: pyvorbis/1.5-2

2012-12-26 Thread Sandro Tosi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package pyvorbis

It fixes a crash when calling read() method.

unblock pyvorbis/1.5-2

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.6-trunk-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru pyvorbis-1.5/debian/changelog pyvorbis-1.5/debian/changelog
--- pyvorbis-1.5/debian/changelog	2011-08-17 17:47:52.0 +0200
+++ pyvorbis-1.5/debian/changelog	2012-12-26 12:38:03.0 +0100
@@ -1,3 +1,12 @@
+pyvorbis (1.5-2) unstable; urgency=low
+
+  * debian/patches/03_fix_call_to_ov_read.patch
+- fix a crash (Floating point exception) when calling read(); thanks to
+  Alessio Gaeta for the report and to Emmanuel Anne for the patch;
+  Closes: #696640
+
+ -- Sandro Tosi mo...@debian.org  Wed, 26 Dec 2012 12:37:57 +0100
+
 pyvorbis (1.5-1) unstable; urgency=low
 
   * New upstream release
diff -Nru pyvorbis-1.5/debian/patches/03_fix_call_to_ov_read.patch pyvorbis-1.5/debian/patches/03_fix_call_to_ov_read.patch
--- pyvorbis-1.5/debian/patches/03_fix_call_to_ov_read.patch	1970-01-01 01:00:00.0 +0100
+++ pyvorbis-1.5/debian/patches/03_fix_call_to_ov_read.patch	2012-12-26 12:37:28.0 +0100
@@ -0,0 +1,90 @@
+Description: Fix the crash/no sound while trying to play fofix/guitar hero
+ This mod was trying to force a prototype on an array of callbacks, it's a
+ miracle that it ever worked, maybe older versions of python were more
+ forgiving, or recent versions of libc don't let this kind of thing to
+ pass...
+ .
+ Also changed the memory allocation of py_ov_read to something simpler
+Origin: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670062#10
+Bug-Debian: http://bugs.debian.org/696640
+Forwarded: https://groups.google.com/d/topic/pyogg/IuvxXV5UgP4/discussion
+
+--- pyvorbis-1.5.orig/src/pyvorbisfile.c
 pyvorbis-1.5/src/pyvorbisfile.c
+@@ -35,7 +35,7 @@ length is the number of bytes to read\n\
+ \tbigendian is the endianness you want (defaults to host endianness)\n\
+ \tword is the word size\n\tnot sure what signed does\n;
+ 
+-static PyObject *py_ov_read(PyObject *, PyObject *, PyObject *);
++static PyObject *py_ov_read(PyObject *, PyObject *); // , PyObject *);
+ 
+ FDEF(ov_streams) Returns the number of logical streams in this VorbisFile;
+ FDEF(ov_seekable) Returns whether this VorbisFile is seekable.;
+@@ -119,7 +119,7 @@ PyTypeObject py_vorbisfile_type = {
+ 
+ 
+ static PyMethodDef OggVorbis_File_methods[] = {
+-  {read, (PyCFunction) py_ov_read, 
++  {read, py_ov_read, 
+METH_VARARGS | METH_KEYWORDS, py_ov_read_doc},
+   {info, py_ov_info, 
+METH_VARARGS, py_ov_info_doc},
+@@ -288,7 +288,7 @@ static int is_big_endian() {
+ }
+ 
+ static PyObject *
+-py_ov_read(PyObject *self, PyObject *args, PyObject *kwdict)
++py_ov_read(PyObject *self, PyObject *args) // , PyObject *kwdict)
+ {
+   py_vorbisfile * ov_self = (py_vorbisfile *) self;
+   PyObject *retobj;
+@@ -298,7 +298,7 @@ py_ov_read(PyObject *self, PyObject *arg
+   PyObject *tuple;
+   char *buff;
+   
+-  int length, word, sgned, bitstream;
++  int length, word, sgned, bitstream = 0;
+   int bigendianp;
+ 
+   // Default to host order
+@@ -307,33 +307,23 @@ py_ov_read(PyObject *self, PyObject *arg
+   word = 2;
+   sgned = 1;
+ 
+-  if (!PyArg_ParseTupleAndKeywords(args, kwdict, |, read_kwlist,
++/*  if (!PyArg_ParseTupleAndKeywords(args, kwdict, |, read_kwlist,
+length, bigendianp, word, sgned))
+-return NULL;
+-
+-  buffobj = PyBuffer_New(length);
+-
+-  tuple = PyTuple_New(1);
+-  Py_INCREF(buffobj);
+-  PyTuple_SET_ITEM(tuple, 0, buffobj);
++return NULL; */
+ 
+-  if (!(PyArg_ParseTuple(tuple, t#, buff, length))) {
+-return NULL;
+-  }
+-  Py_DECREF(tuple);
++buff = malloc(length);
++if (!buff) return NULL;
+ 
+-  Py_BEGIN_ALLOW_THREADS
+ retval = ov_read(ov_self-ovf, buff, length, 
+  bigendianp, word, sgned, bitstream);
+-  Py_END_ALLOW_THREADS
+ 
+ if (retval  0) {
+-  Py_DECREF(buffobj);
++	free(buff);
+   return v_error_from_code(retval, Error reading file: );
+ }
+ 
+-  retobj = Py_BuildValue(Oii, buffobj, retval, bitstream);
+-  Py_DECREF(buffobj);
++  retobj = Py_BuildValue(s#ii, buff, retval, retval, bitstream);
++  free(buff);
+   return retobj;
+ }
+ 
diff -Nru pyvorbis-1.5/debian/patches/series pyvorbis-1.5/debian/patches/series
--- pyvorbis-1.5/debian/patches/series	2011-08-17 17:15:18.0 +0200
+++ pyvorbis-1.5/debian/patches/series	2012-12-26 12:37:28.0 +0100
@@ -1,2 +1,3 @@
 01_previous_changes.patch
 02_whrandom_gone.patch
+03_fix_call_to_ov_read.patch


Bug#684884: unblock: mrtg/2.17.4-2

2012-08-14 Thread Sandro Tosi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package mrtg

It fixes a typo in a debconf translation

unblock mrtg/2.17.4-2

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 
'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.4-trunk-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff --git a/debian/changelog b/debian/changelog
index 795c444..df203c2 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+mrtg (2.17.4-2) unstable; urgency=low
+
+  * debian/po/sv.po
+- updated debconf PO Swedish translation; thanks to Martin Bagge for the
+  report and patch; Closes: #681497
+
+ -- Sandro Tosi mo...@debian.org  Tue, 14 Aug 2012 13:57:30 +0200
+
 mrtg (2.17.4-1) unstable; urgency=low
 
   * New upstream release
diff --git a/debian/po/sv.po b/debian/po/sv.po
index 7395010..5fd090c 100644
--- a/debian/po/sv.po
+++ b/debian/po/sv.po
@@ -1,15 +1,15 @@
 # Translation of mrtg debconf template to Swedish
-# Copyright (C) 2009 Martin Bagge brot...@bsnet.se
+# Copyright (C) 2012 Martin Bagge brot...@bsnet.se
 # This file is distributed under the same license as the mrtg package.
 #
-# Martin Bagge brot...@bsnet.se, 2009
+# Martin Bagge brot...@bsnet.se, 2009, 2012
 # Daniel Nylander p...@danielnylander.se, 2005
 msgid 
 msgstr 
 Project-Id-Version: mrtg 2.12.1-1\n
 Report-Msgid-Bugs-To: m...@packages.debian.org\n
 POT-Creation-Date: 2009-11-01 14:34+0100\n
-PO-Revision-Date: 2009-12-29 11:34+0100\n
+PO-Revision-Date: 2012-07-13 10:33-0700\n
 Last-Translator: Martin Bagge brot...@bsnet.se\n
 Language-Team: Swedish debian-l10n-swed...@lists.debian.org\n
 MIME-Version: 1.0\n
@@ -23,7 +23,7 @@ msgstr 
 #: ../mrtg.templates:1001
 #| msgid Make /etc/mrtg.cfg owned by and readable only by the MRTG user?
 msgid Make /etc/mrtg.cfg owned by and readable only by root?
-msgstr Ska /etc/mrtg.cfg ägas av och lendast vara äsbar av root?
+msgstr Ska /etc/mrtg.cfg ägas av och endast vara läsbar av root?
 
 #. Type: boolean
 #. Description


Bug#684212: unblock: python-networkx/1.7~rc1-3

2012-08-07 Thread Sandro Tosi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package python-networkx

It includes an upstream patch to fix a FTBFS bug in nypype .

unblock python-networkx/1.7~rc1-3

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 
'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.4-trunk-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Index: debian/patches/changeset_9ebe087b8bbcdeee3051e07cacd05fa07436c16e.diff
===
--- debian/patches/changeset_9ebe087b8bbcdeee3051e07cacd05fa07436c16e.diff	(revision 0)
+++ debian/patches/changeset_9ebe087b8bbcdeee3051e07cacd05fa07436c16e.diff	(revision 0)
@@ -0,0 +1,59 @@
+From 9ebe087b8bbcdeee3051e07cacd05fa07436c16e Mon Sep 17 00:00:00 2001
+From: Aric Hagberg aric.hagb...@gmail.com
+Date: Fri, 29 Jun 2012 21:30:38 -0600
+Subject: [PATCH] Preserver order in G.nodes() or given in nodelist when
+ converting to scipy sparse matrix.  Update docs to reflect
+ use of COO matrix. Addresses #737
+
+---
+ networkx/convert.py  |8 +---
+ networkx/tests/test_convert_scipy.py |8 
+ 2 files changed, 13 insertions(+), 3 deletions(-)
+
+diff --git a/networkx/convert.py b/networkx/convert.py
+index 833c754..6333b9f 100644
+--- a/networkx/convert.py
 b/networkx/convert.py
+@@ -745,7 +745,7 @@ def to_scipy_sparse_matrix(G, nodelist=None, dtype=None,
+ When `nodelist` does not contain every node in `G`, the matrix is built
+ from the subgraph of `G` that is induced by the nodes in `nodelist`.
+ 
+-Uses lil_matrix format. To convert to other formats specify the
++Uses coo_matrix format. To convert to other formats specify the
+ format= keyword.
+ 
+ Examples
+@@ -777,10 +777,12 @@ def to_scipy_sparse_matrix(G, nodelist=None, dtype=None,
+ nlen = len(nodelist)
+ if nlen == 0:
+ raise nx.NetworkXError(Graph has no nodes or edges)
+-index = dict(zip(set(nodelist),range(nlen)))
+-if len(nodelist) != len(index):
++
++if len(nodelist) != len(set(nodelist)):
+ msg = Ambiguous ordering: `nodelist` contained duplicates.
+ raise nx.NetworkXError(msg)
++
++index = dict(zip(nodelist,range(nlen)))
+ if G.number_of_edges() == 0:
+ row,col,data=[],[],[]
+ else:
+diff --git a/networkx/tests/test_convert_scipy.py b/networkx/tests/test_convert_scipy.py
+index 27ab786..f90dee7 100644
+--- a/networkx/tests/test_convert_scipy.py
 b/networkx/tests/test_convert_scipy.py
+@@ -169,3 +169,11 @@ class TestConvertNumpy(object):
+ G.add_node(1)
+ M = nx.to_scipy_sparse_matrix(G)
+ np_assert_equal(M.todense(), np.matrix([[0]]))
++
++def test_ordering(self):
++G = nx.DiGraph()
++G.add_edge(1,2)
++G.add_edge(2,3)
++G.add_edge(3,1)
++M = nx.to_scipy_sparse_matrix(G,nodelist=[3,2,1])
++np_assert_equal(M.todense(), np.matrix([[0,0,1],[1,0,0],[0,1,0]]))
+-- 
+1.7.10.4
+
Index: debian/patches/series
===
--- debian/patches/series	(revision 22488)
+++ debian/patches/series	(working copy)
@@ -4,3 +4,4 @@
 40_no_setuptools_in_requires.txt
 changeset_fed4cb6e78dc7047c06522b0418ef5b0d8197290.diff
 changeset_8960521b5ae4897bdbac4ff49525d8b37bff88d2.diff
+changeset_9ebe087b8bbcdeee3051e07cacd05fa07436c16e.diff
Index: debian/changelog
===
--- debian/changelog	(revision 22488)
+++ debian/changelog	(working copy)
@@ -1,3 +1,11 @@
+python-networkx (1.7~rc1-3) UNRELEASED; urgency=low
+
+  * debian/patches/changeset_9ebe087b8bbcdeee3051e07cacd05fa07436c16e.diff
+- Preserver order in G.nodes(), fixing a FTBFS in nipype; thanks to Yaroslav
+  Halchenko for the report and analysis; Closes: #684107
+
+ -- Sandro Tosi mo...@debian.org  Tue, 07 Aug 2012 22:07:59 +0200
+
 python-networkx (1.7~rc1-2) unstable; urgency=low
 
   * debian/patches/changeset_8960521b5ae4897bdbac4ff49525d8b37bff88d2.diff


Bug#683822: unblock: amule/2.3.1-9

2012-08-04 Thread Sandro Tosi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package amule

It fixes a crash when statistics.dat file is empty; #683680

unblock amule/2.3.1-9

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 
'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.5-trunk-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff --git a/debian/changelog b/debian/changelog
index e7bbc9a..434084a 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+amule (2.3.1-9) unstable; urgency=low
+
+  * [bd952ab] handle gracefully (ie not crashing) an empty statistics.dat file;
+thanks to florian for the report and to Michael Stapelberg for preparing
+the patch; Closes: #683680
+
+ -- Sandro Tosi mo...@debian.org  Sat, 04 Aug 2012 12:24:53 +0200
+
 amule (2.3.1-8) unstable; urgency=low
 
   * [27f7932] mark libupnp patch as not-needed for forward (it's a Debian
diff --git a/debian/patches/handle_empty_statistics_file.patch b/debian/patches/handle_empty_statistics_file.patch
new file mode 100644
index 000..f215b09
--- /dev/null
+++ b/debian/patches/handle_empty_statistics_file.patch
@@ -0,0 +1,44 @@
+Description: Cope with empty statistics.dat file
+ If, for some reason (corruption), the ~/.aMule/statistics.dat is empty, aMule
+ will refuse to start until the file is deleted. This patch catches the
+ occuring exception, logs the problem, and then continues as if the file did
+ not exist in the first place.
+Bug-Debian: http://bugs.debian.org/683680
+Last-Update: 2012-02-11
+Origin: upstream, http://www.amule.org/abugs/view.php?id=1704
+Forwarded: not-needed
+
+Index: amule/src/Statistics.cpp
+===
+--- amule.orig/src/Statistics.cpp	2012-08-04 10:44:30.564102710 +0200
 amule/src/Statistics.cpp	2012-08-04 10:44:39.708219780 +0200
+@@ -50,6 +50,7 @@
+ #endif
+ 
+ #include amule.h		// Needed for theApp
++#include Logger.h
+ #include wx/intl.h
+ 
+ #ifdef __BSD__
+@@ -311,12 +312,16 @@
+ 
+ 	s_totalSent = 0;
+ 	s_totalReceived = 0;
+-	if (f.Open(JoinPaths(theApp-ConfigDir, wxT(statistics.dat {
+-		uint8_t version = f.ReadUInt8();
+-		if (version == 0) {
+-			s_totalSent = f.ReadUInt64();
+-			s_totalReceived = f.ReadUInt64();
++	try {
++		if (f.Open(JoinPaths(theApp-ConfigDir, wxT(statistics.dat {
++			uint8_t version = f.ReadUInt8();
++			if (version == 0) {
++s_totalSent = f.ReadUInt64();
++s_totalReceived = f.ReadUInt64();
++			}
+ 		}
++	} catch (CSafeIOException e) {
++		AddLogLineN(e.what());
+ 	}
+ 
+ 	// Load old values from config
diff --git a/debian/patches/series b/debian/patches/series
index f473898..ad39f0c 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -5,3 +5,4 @@ fallocate.diff
 version_check.diff
 libupnp-fix-publisherurl.patch
 gcc_4.7.diff
+handle_empty_statistics_file.patch


Bug#683152: unblock: reportbug/6.4.1

2012-07-29 Thread Sandro Tosi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package reportbug

It fixes a bug that made reporting bugs to src:p be actually reported to 
'src'.

unblock reportbug/6.4.1

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 
'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.4-trunk-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20120729091729.20775.42615.report...@oracle.matrix.int



Bug#658289: transition: python-numpy

2012-04-04 Thread Sandro Tosi
On Mon, Feb 27, 2012 at 19:22, Julien Cristau jcris...@debian.org wrote:
 On Sun, Feb 26, 2012 at 00:04:39 +0100, Cyril Brulebois wrote:

  All the remaining packages are either RC-buggy (cmor #661283,
  pytables #661285 #661286 #661287) or not in testing (shogun,
  plplot).

 So time to look at removal hints and preparing an easy hint if needed? Great.

 Well.  Or nmu.

those packages seem to have gone, and the transition on the tracker is
at 100%: what is the release team opinion on it, is it completed? is
there something else missing?

I've see just 2 blocking bugs on this bug on the BTS , but they are
related to numpy 1.6, which is still in experimental and not intended
for this particular transition.

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi



--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAB4XWXxpW+4aYoifuUMagKz4DBBP=l4iceo3wp6+jqb1mmq...@mail.gmail.com



Bug#663632: transition: geos

2012-03-24 Thread Sandro Tosi
On Mon, Mar 12, 2012 at 21:19, Julien Cristau jcris...@debian.org wrote:
 - basemap FTBFS (#663403)

Fixed and built everywhere.

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi



-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAB4XWXzf3UHjHsSJrzhFkiXkaE7RaVnvWKD=szbijkvnxz2...@mail.gmail.com



Re: Bug#636929: release.debian.org: add a template for urgency bumps?

2011-12-04 Thread Sandro Tosi
On Mon, Nov 21, 2011 at 23:49, Julien Cristau jcris...@debian.org wrote:
 On Thu, Nov  3, 2011 at 22:31:38 +0100, Sandro Tosi wrote:

 Could release team comment on this bug: do you think it's something
 you might be interested in? If so, how would you like to receive a
 urgency bump bug report?

 Not sure if it's worth it, these don't happen very often...

Thanks Julien for the reply. Given the main user of this feature (RT)
don't seem to need it that much, I'm just going to close this bug. If
things will change, we can always reopen it.

Cheers,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi


--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAPdtAj0frcdz=-zfitpgm-m_4awxcsfpfmyzg7zeh6blrkd...@mail.gmail.com



Re: Bug#636929: release.debian.org: add a template for urgency bumps?

2011-11-03 Thread Sandro Tosi
On Sun, Aug 7, 2011 at 10:53, Sandro Tosi mo...@debian.org wrote:
 Hello Christian,

 On Sun, Aug 7, 2011 at 08:58, Christian Perrier bubu...@debian.org wrote:
 This suggestion comes after sending a BR against release.d.o to
 request for an urgency bump for a package of mine.

 I like the use of the BTS for release-related things, with various
 templates for common actions requested to the release team.It could be
 good to have a template for urgency bump requests, when one wants to
 request raising (or lowering) the urgency of a given package in
 unstable.

 The template could ask for the source package name, current urgency
 and target urgency, as well as, of course, a rationale.

 At least d-release should be added in the loop, in order to allow them
 to ack/nack the request (ie if they want such requests as bug report
 of a specific category). Added d-r@ let's see what they say.

Could release team comment on this bug: do you think it's something
you might be interested in? If so, how would you like to receive a
urgency bump bug report?

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/capdtaj2gtyknfzgvrtk+o1cps0pjxgtdlaurfbtuuvwy4t1...@mail.gmail.com



Re: Bug#639897: Please don't check /proc/mounts

2011-09-08 Thread Sandro Tosi
Dear SRM,
would you consider the attached patches for a squeeze point release for eglibc?

The reason behind this request is: on systems with a lot of mounts,
statvfs64() libc function takes a huge amount of times since it needs
to parse /proc/mounts. With the proposed patches, and with a kernel
from bpo (it's needed = 2.6.36 where there's a syscall to get what
libc needs) we can fix this behavior.

Thanks for considering,
Sandro  Aurelien

On Thu, Sep 8, 2011 at 15:50, Aurelien Jarno aure...@debian.org wrote:
 Hi,

 On Wed, Sep 07, 2011 at 11:30:17AM +0200, Sandro Tosi wrote:
 Hi Aurelien,
 thanks for your reply and sorry for mine being so late

 On Fri, Sep 2, 2011 at 21:56, Aurelien Jarno aure...@debian.org wrote:
  As always, when the libc doesn't have the information from a kernel
  syscall, it needs to get it another way, and it often ends up using
  /proc or /sys as the source of information. In some cases it can't take
  huge amount of time, but the problem is not that the libc doesn't parse
  the pseudo file inefficiently, just that the kernel has to generate
  insane amount of useless data.

 Thanks for the explanation!

  In your case of statvfs(), the problem has been solved a bit more than
  one year ago, by exporting the missing data directly through the
  syscall. For that you need a libc = 2.13 and a kernel = 2.6.36. I
  guess in your case you are using Squeeze, which doesn't meet these
  requirements.

 Yep, I'm on squeeze.

  The libc patch is trivial to backport, having it in squeeze is mostly
  about convincing the release managers that it's useful and safe. On the

 Can you point me to that relevant patch? I can try to talk to RM but I
 guess we won't get that far: given it won't solve the problem at hand
 just by itself, because it requires an updated kernel, it would
 probably get rejected - but worth a try.

 Please find attached the two patches, one for the libc and one for the
 architectures in ports. Even if they might look big at the first place,
 they are actually quite trivail.

  kernel side, it seems a bit more complicated, as the change has been
  followed by a lot of small bug fixes.

 I see. What would you suggest as a better approach to solve our
 problem? is backporting libc a feasable solution? bpo already have
 2.6.38 (or now even later) kernel version, so we can probably use
 that.


 I don't think having a libc in backports.org is really a good idea,
 especially with all the current multiarch changes, it would also mean
 that plenty of other packages would have to be backported (most of the
 toolchain for example). Given that backports is now an official Debian
 service, it looks like the best is to get the needed changes in
 eglibc/stable and use a kernel from backports.org.

 Cheers,
 Aurelien

 --
 Aurelien Jarno                          GPG: 1024D/F1BCDB73
 aurel...@aurel32.net                 http://www.aurel32.net




-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
commit 3cdaa6adb113a088fdfb87aa6d7747557eccc58d
Author: Ulrich Drepper drep...@redhat.com
Date:   Wed Aug 11 14:07:28 2010 -0700

f_flags in Linux statfs implementation.

The 2.6.36 kernel provides an additional field in the statfs results.
Use this value in the statvfs emulation to avoid filling in f_flag
the hard way.

diff --git a/ChangeLog b/ChangeLog
index 1d12009..250eaf9 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,18 @@
 2010-08-11  Ulrich Drepper  drep...@redhat.com
 
+	* sysdeps/unix/sysv/linux/bits/statfs.h (struct statfs): Add f_flags
+	field.
+	(struct statfs64): Likewise.
+	(_STATFS_F_FLAGS): Define.
+	* sysdeps/unix/sysv/linux/s390/bits/statfs.h: Likewise.
+	* sysdeps/unix/sysv/linux/internal_statvfs.c (__statvfs_getflags):
+	Don't define if __ASSUME_STATFS_F_FLAGS is defined.
+	(ST_VALID): Define locally.
+	(INTERNAL_STATVFS): If f_flags has ST_VALID set don't call
+	__statvfs_getflags, use the provided value.
+	* sysdeps/unix/sysv/linux/kernel-features.h: Define
+	__ASSUME_STATFS_F_FLAGS.
+
 	* sysdeps/unix/sysv/linux/sys/inotify.h (IN_EXCL_UNLINK): Define.
 
 	* sysdeps/unix/sysv/linux/Makefile [subdir=misc] (sysdep_headers):
diff --git a/sysdeps/unix/sysv/linux/bits/statfs.h b/sysdeps/unix/sysv/linux/bits/statfs.h
index 0e27865..7bd90d0 100644
--- a/sysdeps/unix/sysv/linux/bits/statfs.h
+++ b/sysdeps/unix/sysv/linux/bits/statfs.h
@@ -1,4 +1,4 @@
-/* Copyright (C) 1997, 1998, 2000, 2002, 2003 Free Software Foundation, Inc.
+/* Copyright (C) 1997,1998,2000,2002,2003,2010 Free Software Foundation, Inc.
This file is part of the GNU C Library.
 
The GNU C Library is free software; you can redistribute it and/or
@@ -42,7 +42,8 @@ struct statfs
 __fsid_t f_fsid;
 __SWORD_TYPE f_namelen;
 __SWORD_TYPE f_frsize;
-__SWORD_TYPE f_spare[5];
+__SWORD_TYPE f_flags;
+__SWORD_TYPE f_spare[4];
   };
 
 #ifdef __USE_LARGEFILE64
@@ -58,10 +59,12

Bug#640922: pu: package eglibc/2.11.2-10 (Was: Bug#639897: Please don't check /proc/mounts)

2011-09-08 Thread Sandro Tosi
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: pu
Severity: normal

Dear SRM,
would you consider the attached patches for a squeeze point release for eglibc?

The reason behind this request is: on systems with a lot of mounts,
statvfs64() libc function takes a huge amount of times since it needs
to parse /proc/mounts. With the proposed patches, and with a kernel
from bpo (it's needed = 2.6.36 where there's a syscall to get what
libc needs) we can fix this behavior.

Thanks for considering,
Sandro  Aurelien

PS: resent as a bug.

On Thu, Sep 8, 2011 at 15:50, Aurelien Jarno aure...@debian.org wrote:
 Hi,

 On Wed, Sep 07, 2011 at 11:30:17AM +0200, Sandro Tosi wrote:
 Hi Aurelien,
 thanks for your reply and sorry for mine being so late

 On Fri, Sep 2, 2011 at 21:56, Aurelien Jarno aure...@debian.org wrote:
  As always, when the libc doesn't have the information from a kernel
  syscall, it needs to get it another way, and it often ends up using
  /proc or /sys as the source of information. In some cases it can't take
  huge amount of time, but the problem is not that the libc doesn't parse
  the pseudo file inefficiently, just that the kernel has to generate
  insane amount of useless data.

 Thanks for the explanation!

  In your case of statvfs(), the problem has been solved a bit more than
  one year ago, by exporting the missing data directly through the
  syscall. For that you need a libc = 2.13 and a kernel = 2.6.36. I
  guess in your case you are using Squeeze, which doesn't meet these
  requirements.

 Yep, I'm on squeeze.

  The libc patch is trivial to backport, having it in squeeze is mostly
  about convincing the release managers that it's useful and safe. On the

 Can you point me to that relevant patch? I can try to talk to RM but I
 guess we won't get that far: given it won't solve the problem at hand
 just by itself, because it requires an updated kernel, it would
 probably get rejected - but worth a try.

 Please find attached the two patches, one for the libc and one for the
 architectures in ports. Even if they might look big at the first place,
 they are actually quite trivail.

  kernel side, it seems a bit more complicated, as the change has been
  followed by a lot of small bug fixes.

 I see. What would you suggest as a better approach to solve our
 problem? is backporting libc a feasable solution? bpo already have
 2.6.38 (or now even later) kernel version, so we can probably use
 that.


 I don't think having a libc in backports.org is really a good idea,
 especially with all the current multiarch changes, it would also mean
 that plenty of other packages would have to be backported (most of the
 toolchain for example). Given that backports is now an official Debian
 service, it looks like the best is to get the needed changes in
 eglibc/stable and use a kernel from backports.org.

 Cheers,
 Aurelien

 --
 Aurelien Jarno                          GPG: 1024D/F1BCDB73
 aurel...@aurel32.net                 http://www.aurel32.net




-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
commit 3cdaa6adb113a088fdfb87aa6d7747557eccc58d
Author: Ulrich Drepper drep...@redhat.com
Date:   Wed Aug 11 14:07:28 2010 -0700

f_flags in Linux statfs implementation.

The 2.6.36 kernel provides an additional field in the statfs results.
Use this value in the statvfs emulation to avoid filling in f_flag
the hard way.

diff --git a/ChangeLog b/ChangeLog
index 1d12009..250eaf9 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,18 @@
 2010-08-11  Ulrich Drepper  drep...@redhat.com
 
+	* sysdeps/unix/sysv/linux/bits/statfs.h (struct statfs): Add f_flags
+	field.
+	(struct statfs64): Likewise.
+	(_STATFS_F_FLAGS): Define.
+	* sysdeps/unix/sysv/linux/s390/bits/statfs.h: Likewise.
+	* sysdeps/unix/sysv/linux/internal_statvfs.c (__statvfs_getflags):
+	Don't define if __ASSUME_STATFS_F_FLAGS is defined.
+	(ST_VALID): Define locally.
+	(INTERNAL_STATVFS): If f_flags has ST_VALID set don't call
+	__statvfs_getflags, use the provided value.
+	* sysdeps/unix/sysv/linux/kernel-features.h: Define
+	__ASSUME_STATFS_F_FLAGS.
+
 	* sysdeps/unix/sysv/linux/sys/inotify.h (IN_EXCL_UNLINK): Define.
 
 	* sysdeps/unix/sysv/linux/Makefile [subdir=misc] (sysdep_headers):
diff --git a/sysdeps/unix/sysv/linux/bits/statfs.h b/sysdeps/unix/sysv/linux/bits/statfs.h
index 0e27865..7bd90d0 100644
--- a/sysdeps/unix/sysv/linux/bits/statfs.h
+++ b/sysdeps/unix/sysv/linux/bits/statfs.h
@@ -1,4 +1,4 @@
-/* Copyright (C) 1997, 1998, 2000, 2002, 2003 Free Software Foundation, Inc.
+/* Copyright (C) 1997,1998,2000,2002,2003,2010 Free Software Foundation, Inc.
This file is part of the GNU C Library.
 
The GNU C Library is free software; you can redistribute it and/or
@@ -42,7 +42,8 @@ struct statfs
 __fsid_t f_fsid;
 __SWORD_TYPE f_namelen;
 __SWORD_TYPE f_frsize

  1   2   >