Bug#861414: unblock: pysurfer/0.7-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package pysurfer -2 fixes documentation issue (manpages being garbage), should be safe otherwise Full diff: diff -Nru pysurfer-0.7/debian/changelog pysurfer-0.7/debian/changelog --- pysurfer-0.7/debian/changelog 2016-11-12 13:43:21.0 -0500 +++ pysurfer-0.7/debian/changelog 2017-03-27 17:09:17.0 -0400 @@ -1,3 +1,10 @@ +pysurfer (0.7-2) unstable; urgency=medium + + * Run help2man under xvfb to avoid manpage containing just an error +message (Closes: #858848) + + -- Yaroslav Halchenko <deb...@onerussian.com> Mon, 27 Mar 2017 17:09:17 -0400 + pysurfer (0.7-1) unstable; urgency=medium * Fresh upstream release diff -Nru pysurfer-0.7/debian/control pysurfer-0.7/debian/control --- pysurfer-0.7/debian/control 2016-11-12 13:43:21.0 -0500 +++ pysurfer-0.7/debian/control 2017-03-27 17:09:17.0 -0400 @@ -13,6 +13,7 @@ mayavi2, python-matplotlib, ipython, + xvfb, xauth, Standards-Version: 3.9.6 XS-Python-Version: >= 2.6 Homepage: http://pysurfer.github.com diff -Nru pysurfer-0.7/debian/rules pysurfer-0.7/debian/rules --- pysurfer-0.7/debian/rules 2016-11-12 13:43:21.0 -0500 +++ pysurfer-0.7/debian/rules 2017-03-27 17:09:17.0 -0400 @@ -27,7 +27,7 @@ #endif override_dh_installman: - PYTHONPATH=. help2man --version-string="$(upstreamver)" -N \ + PYTHONPATH=. xvfb-run --auto-servernum help2man --version-string="$(upstreamver)" -N \ --no-discard-stderr \ -n 'visualize cortical surface reconstruction from Freesurfer' \ debian/python-surfer/usr/bin/pysurfer > build/pysurfer.1 unblock pysurfer/0.7-2 -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental'), (100, 'unstable-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.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/dash Init: systemd (via /run/systemd/system)
Bug#855216: unblock: singularity-container/2.2-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package singularity-container
2.2 release contained a vulnerability described in detail upstream
https://github.com/singularityware/singularity/releases/tag/2.2.1 :
In versions of Singularity previous to 2.2.1, it was possible for a malicious
user to create and manipulate specifically crafted raw devices within
containers they own. Utilizing MS_NODEV as a container image mount option
mitigates this potential vector of attack. As a result, this update should be
implemented with high urgency. A big thanks to Mattias Wadenstein (@UMU in
Sweden) for identifying and reporting this issue!
2.2-2 (debdiff attached) was prepared in collaboration with upstream to cover
that vulnerability and address few other possibly security related (snprintf)
and functionality related issues. security@d.o was provided with debdiff and
no negative opinions were expressed.
unblock singularity-container/2.2-2
-- System Information:
Debian Release: 9.0
APT prefers testing
APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental'), (100,
'unstable-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-1-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/dash
Init: systemd (via /run/systemd/system)
diff -Nru singularity-container-2.2/debian/changelog
singularity-container-2.2/debian/changelog
--- singularity-container-2.2/debian/changelog 2016-11-30 12:33:01.0
-0500
+++ singularity-container-2.2/debian/changelog 2017-02-09 16:27:55.0
-0500
@@ -1,3 +1,24 @@
+singularity-container (2.2-2) unstable; urgency=high
+
+ * debian/patches - picks up from upcoming 2.2.1 release
+critical functionality and possibly security-related fixes
+- changeset_b859cd8b4b9293f2a8a893ef41c5d93a5318dd6c.diff
+ to support mounting ext4 formatted images read-only
+- changeset_f79e853d9ee8a15b1d16cdc7dfbe85eca50efc6d.diff
+ to utilize mount option MS_NODEV for images
+ (fixes potential security implications)
+- changeset_d835fa1d20efc4aaacca4be68431d193d6625bd8.diff
+ to fix bootstrapping ran as root (thus no MS_NODEV restriction
+ from above patch should be applied)
+- changeset_3a2b6537f0b1386336e29d7f763ae62374a7cb77.diff
+ exit with error if snprintf would have went out of bounds
+- changeset_acc02b921192e7e16afe1513d5338904f8e6f907.diff
+ changeset_0935d68145ce575444b7ced43417cc6fccffd670.diff
+ changeset_0d04edaeb5cb3607ab25588f4db177c0878adcc0.diff
+ Various obvious fixes (updated URLs, apt --force-yes)
+
+ -- Yaroslav Halchenko <deb...@onerussian.com> Thu, 09 Feb 2017 16:27:55 -0500
+
singularity-container (2.2-1) unstable; urgency=medium
[ Mehdi Dogguy ]
diff -Nru
singularity-container-2.2/debian/patches/changeset_0935d68145ce575444b7ced43417cc6fccffd670.diff
singularity-container-2.2/debian/patches/changeset_0935d68145ce575444b7ced43417cc6fccffd670.diff
---
singularity-container-2.2/debian/patches/changeset_0935d68145ce575444b7ced43417cc6fccffd670.diff
1969-12-31 19:00:00.0 -0500
+++
singularity-container-2.2/debian/patches/changeset_0935d68145ce575444b7ced43417cc6fccffd670.diff
2017-02-09 16:27:55.0 -0500
@@ -0,0 +1,21 @@
+From: Gregory M. Kurtzer <gmkurt...@lbl.gov>
+Subject: Use --force-yes
+
+--- a/examples/debian.def
b/examples/debian.def
+@@ -16,5 +16,5 @@ MirrorURL: http://ftp.us.debian.org/debi
+ %post
+ echo "Hello from inside the container"
+ apt-get update
+-apt-get -y install vim
++apt-get -y --force-yes install vim
+
+--- a/examples/ubuntu.def
b/examples/ubuntu.def
+@@ -16,5 +16,5 @@ MirrorURL: http://us.archive.ubuntu.com/
+ %post
+ echo "Hello from inside the container"
+ sed -i 's/$/ universe/' /etc/apt/sources.list
+-apt-get -y install vim
++apt-get -y --force-yes install vim
+
diff -Nru
singularity-container-2.2/debian/patches/changeset_0d04edaeb5cb3607ab25588f4db177c0878adcc0.diff
singularity-container-2.2/debian/patches/changeset_0d04edaeb5cb3607ab25588f4db177c0878adcc0.diff
---
singularity-container-2.2/debian/patches/changeset_0d04edaeb5cb3607ab25588f4db177c0878adcc0.diff
1969-12-31 19:00:00.0 -0500
+++
singularity-container-2.2/debian/patches/changeset_0d04edaeb5cb3607ab25588f4db177c0878adcc0.diff
2017-02-09 16:27:55.0 -0500
@@ -0,0 +1,14 @@
+From: Nekel-Seyew <kylemdswee...@gmail.com>
+Subject: added an ERRNO==ENOENT clause
+
+--- a/src/lib/file/group/group.c
b/src/lib/file/group/group.c
+@@ -139,7 +139,7 @@ int singularity_file_group(void) {
+ singularity_message(VERBOSE3, "Found supplementary group
membership in: %d\n", gids[i]);
+ singularity_message(VERBOSE2, "Adding user's supplementar
Bug#851300: unblock: utopia-documents/3.0.0-1
On Fri, 13 Jan 2017, Mattia Rizzolo wrote: > > d'oh -- I should have noted that it wasn't in testing -- somehow > > I was under impression (saw "jessie" -- thought "stretch") that it was > > in testing at that point. > … > > Thanks Mattia for the patience with my silly questions ;) > Remember that I'm not from the Release Team; if they want to make an > exception it's entirely up to them, I was just replying to explain why > this didn't migrate when you expected it to do. double thanks then ;) I will leave it up to release team to decide if they are still reading this report. Cheers, -- Yaroslav O. Halchenko Center for Open Neuroscience http://centerforopenneuroscience.org Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik
Bug#851300: unblock: utopia-documents/3.0.0-1
On January 13, 2017 2:22:43 PM EST, Mattia Rizzolo <mat...@debian.org> wrote: >On Fri, Jan 13, 2017 at 02:11:03PM -0500, Yaroslav Halchenko wrote: >> Please unblock package utopia-documents >> >> It was uploaded in time to propagate to testing before the freeze >point > >It wasn't. >It was uploaded the 29th Dec, 3 days too late (last good day was the >26th, so 10 days later would have been the 5th of Jan, day of the >freeze). Could you please clarify, since this package was in testing already and wasn't kicked out, why it can't migrate now? Jan 5: soft freeze Deadline for: * New (source) packages in stretch * Letting packages re-enter stretch (if they have been removed) Updates to existing packages in stretch will continue as normal.
Bug#851300: unblock: utopia-documents/3.0.0-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package utopia-documents It was uploaded in time to propagate to testing before the freeze point but we haven't spotted that there was some custom Extra-Depends set for previous version binnmu (but buildd ppl, not us) which lead to "BD-Uninstallable (Extra-Depends: libglew1.13)"... yesterday that was fixed and all the relevant archs binaries were built just fine so it is ready for migration into testing RC (include/attach the debdiff against the package in testing) irrelevant unblock utopia-documents/3.0.0-1 -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental'), (100, 'unstable-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.8.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/dash Init: systemd (via /run/systemd/system)
Bug#837688: nmu: mpi4py_2.0.0-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu mpi4py_2.0.0-2 . ANY . unstable . -m "Rebuild against libopenmpi2" Should resolve #837633 -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental'), (100, 'unstable-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.6.0-1-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/dash Init: systemd (via /run/systemd/system)
Bug#798999: transition: python3.5 supported
On Sat, 26 Sep 2015, Scott Kitterman wrote: > > On Thu, Sep 24, 2015 at 22:19:20 -0400, Scott Kitterman wrote: > > > I have the python3-defaults upload to enable python3.5 as a supported > > > python3 version prepared and ready to upload when I get an ack from the > > > release team. > > ack. > > Cheers, > > Julien > Thanks. I've uploaded python3-defaults, so once it's built/installed > python3.5 is supported. is round of binNMUs scheduled already? since now nothing depending on python3-numpy at build time would build: # python3.5 -c 'import numpy' Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/numpy/__init__.py", line 170, in from . import add_newdocs File "/usr/lib/python3/dist-packages/numpy/add_newdocs.py", line 13, in from numpy.lib import add_newdoc File "/usr/lib/python3/dist-packages/numpy/lib/__init__.py", line 8, in from .type_check import * File "/usr/lib/python3/dist-packages/numpy/lib/type_check.py", line 11, in import numpy.core.numeric as _nx File "/usr/lib/python3/dist-packages/numpy/core/__init__.py", line 6, in from . import multiarray ImportError: cannot import name 'multiarray' -- Yaroslav O. Halchenko Center for Open Neuroscience http://centerforopenneuroscience.org Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik
Bug#772892: unblock: python-mne/0.8.6+dfsg-2
On Fri, 12 Dec 2014, Ivo De Decker wrote: Please unblock package python-mne Unblocked. Great -- thank you! P.S. For full clarity: while building this package in dirty environment today with pandas present, I found that build would fail with pandas version in sid (pandas failed to propagate to jessie before the freeze because of FTBFS on some archs due to some failing tests), and mne upstream has fix for that [1]. It is just a minor patch so if desired -- I could include it as well which should solidify this package across jessie/sid. But it is relevant only for sid, not for jessie, and even in sid shouldn't cause FTBFS in clean build environments. That change isn't appropriate for jessie. For stretch, it would be good to make sure that the build doesn't produce a different result in an unclean environment (though obviously, uploads to the archive should always be built in a clean environment). yeap -- gotcha. Have a good weekend -- Yaroslav O. Halchenko, Ph.D. http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org Research Scientist,Psychological and Brain Sciences Dept. Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- 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/20141212194157.gn7...@onerussian.com
Bug#772892: unblock: python-mne/0.8.6+dfsg-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package python-mne python-mne 0.8.4+dfsg-1 was recently (2014-12-08) removed from jessie because of FTBFS due to failing unittests excercised at build time (writing to $HOME). before that I had uploaded 0.8.6+dfsg-1 into sid since changes were abnisimal (docs + 1 small bug with obvious fix). Per our discussion on #IRC today's morning to mitigate the FTBFS in jessie I am uploading sid's version with the patch to properly address the failing unittests (using temp directory instead of HOME). I am attaching the full debdiff from the version previously in jessie. It also could be found at http://www.onerussian.com/tmp/python-mne_0.8.6+dfsg-2.debdiff P.S. For full clarity: while building this package in dirty environment today with pandas present, I found that build would fail with pandas version in sid (pandas failed to propagate to jessie before the freeze because of FTBFS on some archs due to some failing tests), and mne upstream has fix for that [1]. It is just a minor patch so if desired -- I could include it as well which should solidify this package across jessie/sid. But it is relevant only for sid, not for jessie, and even in sid shouldn't cause FTBFS in clean build environments. [1] https://github.com/mne-tools/mne-python/commit/80dbf150bf7fe0baa313a0caccc69ae6c85f9de0 unblock python-mne/0.8.6+dfsg-2 -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.17-1-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/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/20141212002422.14960.44472.report...@hopa.kiewit.dartmouth.edu
Bug#772892: forgotten to be attached patch
and please pardon in the best traditions forgotten to be attached patch.
Now it should be
--
Yaroslav O. Halchenko, Ph.D.
http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org
Research Scientist,Psychological and Brain Sciences Dept.
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419
WWW: http://www.linkedin.com/in/yarik
diff -Nru python-mne-0.8.4+dfsg/debian/changelog
python-mne-0.8.6+dfsg/debian/changelog
--- python-mne-0.8.4+dfsg/debian/changelog 2014-09-24 08:22:55.0
-0400
+++ python-mne-0.8.6+dfsg/debian/changelog 2014-12-11 17:02:51.0
-0500
@@ -1,3 +1,18 @@
+python-mne (0.8.6+dfsg-2) unstable; urgency=medium
+
+ * debian/{rules.patches/changeset_b9d4d*}
+Absorb upstream patch and specify not using HOME directory for generated
+pre-computed data, but instead use tempdir. (Closes: #768730)
+
+ -- Yaroslav Halchenko deb...@onerussian.com Thu, 11 Dec 2014 09:33:18 -0500
+
+python-mne (0.8.6+dfsg-1) unstable; urgency=low
+
+ * New upstream version
+ * remove dependency on d3
+
+ -- Alexandre Gramfort alexandre.gramf...@m4x.org Sat, 25 Oct 2014 16:09:07
-0400
+
python-mne (0.8.4+dfsg-1) unstable; urgency=low
[ Alexandre Gramfort ]
diff -Nru python-mne-0.8.4+dfsg/debian/control
python-mne-0.8.6+dfsg/debian/control
--- python-mne-0.8.4+dfsg/debian/control2014-09-24 08:22:55.0
-0400
+++ python-mne-0.8.6+dfsg/debian/control2014-12-11 17:02:51.0
-0500
@@ -43,7 +43,6 @@
xauth,
libgl1-mesa-dri,
help2man,
- libjs-d3,
libjs-jquery,
libjs-jquery-ui,
Recommends: python-nose,
diff -Nru
python-mne-0.8.4+dfsg/debian/patches/changeset_b9d4df78db7aaeda1feb58c18b0071934de2361e.diff
python-mne-0.8.6+dfsg/debian/patches/changeset_b9d4df78db7aaeda1feb58c18b0071934de2361e.diff
---
python-mne-0.8.4+dfsg/debian/patches/changeset_b9d4df78db7aaeda1feb58c18b0071934de2361e.diff
1969-12-31 19:00:00.0 -0500
+++
python-mne-0.8.6+dfsg/debian/patches/changeset_b9d4df78db7aaeda1feb58c18b0071934de2361e.diff
2014-12-11 17:02:51.0 -0500
@@ -0,0 +1,46 @@
+commit b9d4df78db7aaeda1feb58c18b0071934de2361e
+Author: Eric89GXL larson.eri...@gmail.com
+Date: Wed Nov 12 10:22:45 2014 -0800
+
+ENH: Allow not writing home
+
+--- a/mne/utils.py
b/mne/utils.py
+@@ -24,6 +24,8 @@ from math import log, ceil
+ import json
+ import ftplib
+ import hashlib
++from functools import partial
++import atexit
+
+ import numpy as np
+ import scipy
+@@ -983,8 +985,12 @@ def get_subjects_dir(subjects_dir=None,
+ return subjects_dir
+
+
++_temp_home_dir = None
++
++
+ def _get_extra_data_path(home_dir=None):
+ Get path to extra data (config, tables, etc.)
++global _temp_home_dir
+ if home_dir is None:
+ # this has been checked on OSX64, Linux64, and Win32
+ if 'nt' == os.name.lower():
+@@ -996,7 +1002,14 @@ def _get_extra_data_path(home_dir=None):
+ # of script that isn't launched via the command line (e.g. a
script
+ # launched via Upstart) then the HOME environment variable will
+ # not be set.
+-home_dir = os.path.expanduser('~')
++if os.getenv('MNE_DONTWRITE_HOME', '') == 'true':
++if _temp_home_dir is None:
++_temp_home_dir = tempfile.mkdtemp()
++atexit.register(partial(shutil.rmtree, _temp_home_dir,
++ignore_errors=True))
++home_dir = _temp_home_dir
++else:
++home_dir = os.path.expanduser('~')
+
+ if home_dir is None:
+ raise ValueError('mne-python config file path could '
diff -Nru python-mne-0.8.4+dfsg/debian/patches/series
python-mne-0.8.6+dfsg/debian/patches/series
--- python-mne-0.8.4+dfsg/debian/patches/series 2014-09-24 08:22:55.0
-0400
+++ python-mne-0.8.6+dfsg/debian/patches/series 2014-12-11 17:02:51.0
-0500
@@ -1,2 +1,3 @@
+changeset_b9d4df78db7aaeda1feb58c18b0071934de2361e.diff
changeset_9c7ef6d10f1f767b742525ea31e42a65a0469327.diff
debian_paths
diff -Nru python-mne-0.8.4+dfsg/debian/rules python-mne-0.8.6+dfsg/debian/rules
--- python-mne-0.8.4+dfsg/debian/rules 2014-09-24 08:22:55.0 -0400
+++ python-mne-0.8.6+dfsg/debian/rules 2014-12-11 17:02:51.0 -0500
@@ -15,7 +15,7 @@
yui-compressor debian/JS/bootstrap/bootstrap.js
$(CURDIR)/mne/html/bootstrap.min.js
override_dh_auto_test:
- MNE_SKIP_SAMPLE_DATASET_TESTS=true MNE_FORCE_SERIAL=true
MNE_SKIP_NETWORK_TESTS=1 \
+ MNE_DONTWRITE_HOME=true MNE_SKIP_SAMPLE_DATASET_TESTS=true
MNE_FORCE_SERIAL=true MNE_SKIP_NETWORK_TESTS=1 \
xvfb-run --auto-servernum --server-num=20 -s -screen 0 1024x768x24
-ac +extension GLX +render -noreset \
$(NOSETESTS) mne
Bug#770959: unblock: mpi4py/1.3.1+hg20131106-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package mpi4py
Skipped some tests to resolve some FTBFS due to exotic setup of some
build boxes.
diff -Nru mpi4py-1.3.1+hg20131106/debian/changelog
mpi4py-1.3.1+hg20131106/debian/changelog
--- mpi4py-1.3.1+hg20131106/debian/changelog2013-11-06 16:46:58.0
-0500
+++ mpi4py-1.3.1+hg20131106/debian/changelog2014-11-24 09:21:30.0
-0500
@@ -1,3 +1,13 @@
+mpi4py (1.3.1+hg20131106-2) unstable; urgency=medium
+
+ * debian/rules
+- assure absent reliance on network via http*_proxy env var
+ * debian/patches
+- up_tests_network_attr tag BaseTestSpawn tests as relying on network
+ access and exclude them from running at pkg build time (Closes: #769801)
+
+ -- Yaroslav Halchenko deb...@onerussian.com Sun, 16 Nov 2014 15:06:21 -0500
+
mpi4py (1.3.1+hg20131106-1) unstable; urgency=low
* Fresh upstream snapshot which includes 1.3.1 stable release
diff -Nru mpi4py-1.3.1+hg20131106/debian/patches/series
mpi4py-1.3.1+hg20131106/debian/patches/series
--- mpi4py-1.3.1+hg20131106/debian/patches/series 2013-11-06
16:46:58.0 -0500
+++ mpi4py-1.3.1+hg20131106/debian/patches/series 2014-11-24
09:21:30.0 -0500
@@ -1 +1,2 @@
up_no_modlibs
+up_tests_network_attr
diff -Nru mpi4py-1.3.1+hg20131106/debian/patches/up_tests_network_attr
mpi4py-1.3.1+hg20131106/debian/patches/up_tests_network_attr
--- mpi4py-1.3.1+hg20131106/debian/patches/up_tests_network_attr1969-12-31
19:00:00.0 -0500
+++ mpi4py-1.3.1+hg20131106/debian/patches/up_tests_network_attr2014-11-24
09:21:30.0 -0500
@@ -0,0 +1,25 @@
+--- a/test/test_spawn.py
b/test/test_spawn.py
+@@ -2,11 +2,14 @@ import sys, os, mpi4py
+ from mpi4py import MPI
+ import mpiunittest as unittest
+
++from nose.plugins.attrib import attr
++
+ MPI4PYPATH = os.path.abspath(os.path.dirname(mpi4py.__path__[0]))
+ CHILDSCRIPT = os.path.abspath(
+ os.path.join(os.path.dirname(__file__), 'spawn_child.py')
+ )
+
++@attr('network')
+ class BaseTestSpawn(object):
+
+ COMM = MPI.COMM_NULL
+@@ -104,6 +107,7 @@ class BaseTestSpawn(object):
+ child.Disconnect()
+ self.COMM.Barrier()
+
++
+ class TestSpawnSelf(BaseTestSpawn, unittest.TestCase):
+ COMM = MPI.COMM_SELF
+
diff -Nru mpi4py-1.3.1+hg20131106/debian/rules
mpi4py-1.3.1+hg20131106/debian/rules
--- mpi4py-1.3.1+hg20131106/debian/rules2013-11-06 16:46:58.0 -0500
+++ mpi4py-1.3.1+hg20131106/debian/rules2014-11-24 09:21:30.0 -0500
@@ -12,6 +12,9 @@
# just use the default.
# MPI=.openmpi
+export http_proxy=http://127.0.0.1:9/
+export https_proxy=http://127.0.0.1:9/
+
%:
dh $@ --with python2,python3$(RECONF),sphinxdoc --buildsystem
python_distutils
@@ -83,7 +86,7 @@
set -e; for v in $(PY2VERS) $(PY3VERS); do \
echo I: testing using python$$v; \
PYTHONPATH=`/bin/ls -d $(CURDIR)/build/lib.*-$$v` \
- /usr/bin/python$$v /usr/bin/nosetests -v
--exclude='testPackUnpackExternal'; \
+ /usr/bin/python$$v /usr/bin/nosetests -v
--exclude='testPackUnpackExternal' -A not network ; \
done
else
: # Skip unittests due to nocheck
unblock mpi4py/1.3.1+hg20131106-2
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.17-1-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/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/20141125142141.23148.19393.report...@hopa.kiewit.dartmouth.edu
Bug#770730: thanks for the NMU
Hi Guys, Thanks for the NMU. Note that that instead of a heavy patch you could have disabled the tests (if we decide to fix by burring bugs away) by extending --exclude=sandbox option in debian/rules without any patch to upstream. Feel welcome to reupload without delay though - a patch is better than no patch ;) -- Yaroslav O. Halchenko, Ph.D. http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org Research Scientist,Psychological and Brain Sciences Dept. Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- 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/20141124134034.ga21...@onerussian.com
Bug#770867: unblock: ants/2.1.0~rc2+git3-g9103999-4
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package ants
these two debian revisions (-3 and -4) fixed outstanding serious issues (see
changelog below) marking ants for the autoremoval
unblock ants/2.1.0~rc2+git3-g9103999-4
here is the debdiff:
diff -Nru ants-2.1.0~rc2+git3-g9103999/debian/changelog
ants-2.1.0~rc2+git3-g9103999/debian/changelog
--- ants-2.1.0~rc2+git3-g9103999/debian/changelog 2014-08-18
23:57:59.0 -0400
+++ ants-2.1.0~rc2+git3-g9103999/debian/changelog 2014-11-21
15:43:54.0 -0500
@@ -1,3 +1,21 @@
+ants (2.1.0~rc2+git3-g9103999-4) unstable; urgency=medium
+
+ * patches/up_lower_cc_3_test_i386_precision
+- lower precision for the ANTS_CC_3_WARP_METRIC_0 test to mitigate
+ FTBFS on i386 (Closes: #768645)
+
+ -- Yaroslav Halchenko deb...@onerussian.com Fri, 21 Nov 2014 15:35:44 -0500
+
+ants (2.1.0~rc2+git3-g9103999-3) unstable; urgency=medium
+
+ * Added Conflicts for gpe-conf also providing bl.1.gz manpage
+(gpe-conf is for embedded systems, so unlikely to be co-installed with
+ants in production) (Closes: #768222)
+ * patches/up_Rscript
+- prepend Rscript call with /usr/bin/env
+
+ -- Yaroslav Halchenko deb...@onerussian.com Wed, 05 Nov 2014 21:27:30 -0500
+
ants (2.1.0~rc2+git3-g9103999-2) unstable; urgency=medium
* Robustify bogomips comparison, fix tests execution
diff -Nru ants-2.1.0~rc2+git3-g9103999/debian/control
ants-2.1.0~rc2+git3-g9103999/debian/control
--- ants-2.1.0~rc2+git3-g9103999/debian/control 2014-08-18 23:57:59.0
-0400
+++ ants-2.1.0~rc2+git3-g9103999/debian/control 2014-11-21 15:43:54.0
-0500
@@ -24,6 +24,7 @@
Package: ants
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}
+Conflicts: gpe-conf
Recommends: environment-modules
Suggests: fsl, gridengine-client, r-base-core
Description: advanced normalization tools for brain and image analysis
diff -Nru ants-2.1.0~rc2+git3-g9103999/debian/patches/deb_local-data.patch
ants-2.1.0~rc2+git3-g9103999/debian/patches/deb_local-data.patch
--- ants-2.1.0~rc2+git3-g9103999/debian/patches/deb_local-data.patch
2014-08-18 23:57:59.0 -0400
+++ ants-2.1.0~rc2+git3-g9103999/debian/patches/deb_local-data.patch
2014-11-21 15:43:54.0 -0500
@@ -5,8 +5,8 @@
Forwarded: no
Last-Update: 2014-08-11
ants-2.0.0.orig/CMake/ANTSExternalData.cmake
-+++ ants-2.0.0/CMake/ANTSExternalData.cmake
+--- a/CMake/ANTSExternalData.cmake
b/CMake/ANTSExternalData.cmake
@@ -31,14 +31,7 @@ file:///var/bigharddrive/%(algo)/%(hash)
mark_as_advanced(ExternalData_URL_TEMPLATES)
list(APPEND ExternalData_URL_TEMPLATES
diff -Nru ants-2.1.0~rc2+git3-g9103999/debian/patches/series
ants-2.1.0~rc2+git3-g9103999/debian/patches/series
--- ants-2.1.0~rc2+git3-g9103999/debian/patches/series 2014-08-18
23:57:59.0 -0400
+++ ants-2.1.0~rc2+git3-g9103999/debian/patches/series 2014-11-21
15:43:54.0 -0500
@@ -1 +1,3 @@
+up_lower_cc_3_test_i386_precision
+up_Rscript
deb_local-data.patch
diff -Nru
ants-2.1.0~rc2+git3-g9103999/debian/patches/up_lower_cc_3_test_i386_precision
ants-2.1.0~rc2+git3-g9103999/debian/patches/up_lower_cc_3_test_i386_precision
---
ants-2.1.0~rc2+git3-g9103999/debian/patches/up_lower_cc_3_test_i386_precision
1969-12-31 19:00:00.0 -0500
+++
ants-2.1.0~rc2+git3-g9103999/debian/patches/up_lower_cc_3_test_i386_precision
2014-11-21 15:43:54.0 -0500
@@ -0,0 +1,11 @@
+--- a/Examples/TestSuite/ANTS_CC_3_test.cmake
b/Examples/TestSuite/ANTS_CC_3_test.cmake
+@@ -23,7 +23,7 @@ set_property(TEST ${THIS_TEST_NAME}_JPG
+ add_test(NAME ${THIS_TEST_NAME}_WARP_METRIC_0 COMMAND
$TARGET_FILE:MeasureImageSimilarity 2 0
+ ${R16_IMAGE} ${WARP_IMAGE}
+ ${OUTPUT_PREFIX}log.txt ${OUTPUT_PREFIX}metric.nii.gz
+- 14.3283 0.05)
++ 14.3283 0.1)
+ set_property(TEST ${THIS_TEST_NAME}_WARP_METRIC_0 APPEND PROPERTY DEPENDS
${THIS_TEST_NAME}_WARP)
+
+ add_test(NAME ${THIS_TEST_NAME}_WARP_METRIC_1 COMMAND
$TARGET_FILE:MeasureImageSimilarity 2 1
diff -Nru ants-2.1.0~rc2+git3-g9103999/debian/patches/up_Rscript
ants-2.1.0~rc2+git3-g9103999/debian/patches/up_Rscript
--- ants-2.1.0~rc2+git3-g9103999/debian/patches/up_Rscript 1969-12-31
19:00:00.0 -0500
+++ ants-2.1.0~rc2+git3-g9103999/debian/patches/up_Rscript 2014-11-21
15:43:54.0 -0500
@@ -0,0 +1,8 @@
+--- a/Scripts/cbf_pasl_robust_batch.R
b/Scripts/cbf_pasl_robust_batch.R
+@@ -1,4 +1,4 @@
+-#!Rscript --vanilla --slave
++#!/usr/bin/env Rscript
+
+ library( ANTsR )
+ library(extremevalues )
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.17-1-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/dash
--
To UNSUBSCRIBE
Bug#770730: thanks for the NMU
On Mon, 24 Nov 2014, Tomasz Buchert wrote: I still think that there are cases well the interface of scipy will bite you, but I did my best. and thanks for that! Cheers, -- Yaroslav O. Halchenko, Ph.D. http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org Research Scientist,Psychological and Brain Sciences Dept. Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- 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/20141124201734.gg32...@onerussian.com
Bug#768976: unblock: fail2ban/0.9.1-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package fail2ban We have 0.8.13 in jessie ATM and I have released 0.9.1 and uploaded 0.9.1-1 just few days too short of a freeze - 10days (why didn't I change urgency? ;)) [2014-10-28] Accepted fail2ban 0.9.1-1 (source all) into unstable (Yaroslav Halchenko) 0.9.1 is the 2nd release in the 0.9.0 line and I had 0.9.0 in experimental for a while. So far it shows great promise to be very stable and much more versatile than 0.8.x -- we introduced multiline matching, eliminated divergance between Debian's and upstream jail.conf definitions, extended testing a lot (92% code coverage). After the release I haven't seen major bug reports (there is one minor typo to be fixed) and I have high confidence that this release would be a much better fit to maintain in Debian jessie (instead of now very stable but aging fast 0.8.). debdiff would be infeasible (we also made it a proper fail2ban python module instead of a bunch of internal submodules), but let me know if I need to provide more lines of argumentation to feature unblock unblock fail2ban/0.9.1-1 -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.17-1-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 -- 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/20141110141221.21835.35354.report...@hopa.kiewit.dartmouth.edu
Bug#768981: unblock: nipy/0.3.0+git262-gbb838d7-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package nipy It was removed from jessie a year ago due to a test failing https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729594 which was resolved also long ago, but I forgot to close this bug report :-/ nipy built fine across all architectures https://buildd.debian.org/status/package.php?p=nipysuite=unstable almost a month ago and I have closed that bugreport now Sorry for forgetting about this one for a while unblock nipy/0.3.0+git262-gbb838d7-1 -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.17-1-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 -- 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/20141110144810.24379.89752.report...@hopa.kiewit.dartmouth.edu
Bug#768981: unblock: nipy/0.3.0+git262-gbb838d7-1
On Mon, 10 Nov 2014, Niels Thykier wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package nipy It was removed from jessie a year ago due to a test failing https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729594 which was resolved also long ago, but I forgot to close this bug report :-/ nipy built fine across all architectures https://buildd.debian.org/status/package.php?p=nipysuite=unstable almost a month ago and I have closed that bugreport now Sorry for forgetting about this one for a while unblock nipy/0.3.0+git262-gbb838d7-1 [...] Sorry, but I am afraid I will have to decline your as your package was not in testing at the time of the freeze. While it may seem harsh, we have already rejected similar cases - if I was to give you special treatment here, I would risk having to give that to all existing cases that we have rejected. oh well. I guess stock wheezy would be quite leaner and crippled enough for quite a few neuroscientists (this request was a pre-condition for the next one -- nipype)... good that at least we will have neuro.debian.net to cover up for insufficiencies of the stock Debian. But in case you guys decide to warrant such requests at some point -- keep me posted please ;-) Cheers, -- Yaroslav O. Halchenko, Ph.D. http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org Research Scientist,Psychological and Brain Sciences Dept. Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- 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/20141110162046.gz32...@onerussian.com
Bug#768976: unblock: fail2ban/0.9.1-1
On Mon, 10 Nov 2014, Niels Thykier wrote: We have 0.8.13 in jessie ATM and I have released 0.9.1 and uploaded 0.9.1-1 just few days too short of a freeze - 10days (why didn't I change urgency? ;)) FTR, that would not have helped. Prior to the freeze, there was a forced 10-day migration[1]. [2014-10-28] Accepted fail2ban 0.9.1-1 (source all) into unstable (Yaroslav Halchenko) 0.9.1 is the 2nd release in the 0.9.0 line and I had 0.9.0 in experimental for a while. So far it shows great promise to be very stable and much more versatile than 0.8.x -- we introduced multiline matching, eliminated divergance between Debian's and upstream jail.conf definitions, extended testing a lot (92% code coverage). After the release I haven't seen major bug reports (there is one minor typo to be fixed) and I have high confidence that this release would be a much better fit to maintain in Debian jessie (instead of now very stable but aging fast 0.8.). debdiff would be infeasible (we also made it a proper fail2ban python module instead of a bunch of internal submodules), but let me know if I need to provide more lines of argumentation to feature unblock unblock fail2ban/0.9.1-1 [...] While the changes do sound interesting and promising, a freeze is not the time to apply such a change. Sadly, I will be declining your request, sorry. that is a pity that few busy days delay is so critical that makes jessie worse. but oh well -- your call Thanks for your work and looking at this one -- Yaroslav O. Halchenko, Ph.D. http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org Research Scientist,Psychological and Brain Sciences Dept. Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- 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/20141110171659.ga32...@onerussian.com
Bug#730118: nmu: gpac_0.5.0+svn4288~dfsg1-4
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu gpac_0.5.0+svn4288~dfsg1-4 . amd64 armel armhf i386 ia64 kfreebsd-amd64 kfreebsd-i386 m68k mips mipsel powerpc powerpcspe s390x sparc sparc64 . -m rebuild against libfreenect 0.2 -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- 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/20131121161916.10977.24018.report...@novo.onerussian.com
Re: transition: libfreenect
I would really appreciate someone having a look at this banal transition so I could progress forward. On Mon, 23 Sep 2013, Yaroslav Halchenko wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition The reason: with 0.2.0 some functions were dropped from public API completely. See https://github.com/yarikoptic/libfreenect/commit/de7802a38cbbca9817ddbee0d06658a7a5f5e4ca for changes in .symbols file There are only 2 reverse dependencies: psychtoolbox-3 unstable: 3.0.9+svn2579.dfsg1 -- FTBFS due to gcc 4.8 incompatibilities experimental: 3.0.10.20130108.dfsg1-1 And I will upload shortly 3.0.11.20130711.dfsg1-1 to experimental which resolved 4.8 incompatibilities otherwise -- libfreenect should not impact building of this package (tested locally). But for transition to happen it seems to depend on both gcc 4.8 transition and glew... if 4.8 gcc gets into jessie before glew 1.9, ptb-3 would need to be removed from jessie anyways. visp binNMU should be sufficient Please let me know if you see any obstacle here and/or should I go ahead and upload 0.2.0 package to unstable. Ben file: title = libfreenect; is_affected = .depends ~ libfreenect0.1 | .depends ~ libfreenect0.2; is_good = .depends ~ libfreenect0.2; is_bad = .depends ~ libfreenect0.1; -- Yaroslav O. Halchenko, Ph.D. http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org Senior Research Associate, Psychological and Brain Sciences Dept. Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- 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/20131011194643.ga31...@onerussian.com
Bug#724329: transition: libfreenect
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition The reason: with 0.2.0 some functions were dropped from public API completely. See https://github.com/yarikoptic/libfreenect/commit/de7802a38cbbca9817ddbee0d06658a7a5f5e4ca for changes in .symbols file There are only 2 reverse dependencies: psychtoolbox-3 unstable: 3.0.9+svn2579.dfsg1 -- FTBFS due to gcc 4.8 incompatibilities experimental: 3.0.10.20130108.dfsg1-1 And I will upload shortly 3.0.11.20130711.dfsg1-1 to experimental which resolved 4.8 incompatibilities otherwise -- libfreenect should not impact building of this package (tested locally). But for transition to happen it seems to depend on both gcc 4.8 transition and glew... if 4.8 gcc gets into jessie before glew 1.9, ptb-3 would need to be removed from jessie anyways. visp binNMU should be sufficient Please let me know if you see any obstacle here and/or should I go ahead and upload 0.2.0 package to unstable. Ben file: title = libfreenect; is_affected = .depends ~ libfreenect0.1 | .depends ~ libfreenect0.2; is_good = .depends ~ libfreenect0.2; is_bad = .depends ~ libfreenect0.1; -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- 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/20130923192056.16918.78058.report...@novo.onerussian.com
fix to pp into wheezy?
Hi RT, We came up with a resolution for http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620551 the gist of the patch for which is replacing invocation of the shipped script to use python -m mechanism. That prevents Python inserting the original directory (after following symlinks) into sys.path causing pp to work if e.g. numpy is imported in the payload script. The patch is: @@ -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) I have tested the patch on my laptop (shipped pp examples), also with MDP which uses python-pp. AFAIK there should be no side-effects from this change, and it does address the problem. I am attaching a complete tentative debdiff for you consideration -- would such upload be allowed to get into wheezy from unstable? -- Yaroslav O. Halchenko Postdoctoral Fellow, Department of Psychological and Brain Sciences Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik diff -Nru parallelpython-1.6.2/debian/changelog parallelpython-1.6.2/debian/changelog --- parallelpython-1.6.2/debian/changelog 2012-06-07 16:49:53.0 -0400 +++ parallelpython-1.6.2/debian/changelog 2013-01-22 13:30:25.0 -0500 @@ -1,3 +1,11 @@ +parallelpython (1.6.2-2) unstable; urgency=low + + * Team upload + * Invoke ppworker via python -m avoiding addition of /usr/share/pyshared +to sys.path (Closes: #620551) + + -- Yaroslav Halchenko deb...@onerussian.com Tue, 22 Jan 2013 13:29:34 -0500 + 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 1969-12-31 19:00:00.0 -0500 +++ parallelpython-1.6.2/debian/patches/30_ppworker_invoke_via-m.patch 2013-01-22 13:29:31.0 -0500 @@ -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 17:35:22.0 -0400 +++ parallelpython-1.6.2/debian/patches/series 2013-01-22 13:25:41.0 -0500 @@ -1,2 +1,3 @@ 10_remove_default_password.patch 20_hyphen-used-as-minus-sign.patch +30_ppworker_invoke_via-m.patch signature.asc Description: Digital signature
Bug#697258: unblock: fail2ban/0.8.6-3wheezy1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
unblock fail2ban/0.8.6-3wheezy1
Please unblock package fail2ban -- addressed a CVE (through a cherry-pick from
upstream changes released in 0.8.8, in experimental). likelihood that anyone
running vulnerable version was affected is close to 0, since it requires a
custom configuration enabling use of matches. Here is a debdiff -- seems to
be working fine ;-)
~/deb/builds/fail2ban$ debdiff 0.8.6-3/fail2ban_0.8.6-3.dsc
0.8.6-3wheezy1/fail2ban_0.8.6-3wheezy1.dsc
diff -u fail2ban-0.8.6/debian/changelog fail2ban-0.8.6/debian/changelog
--- fail2ban-0.8.6/debian/changelog
+++ fail2ban-0.8.6/debian/changelog
@@ -1,3 +1,12 @@
+fail2ban (0.8.6-3wheezy1) unstable; urgency=high
+
+ * CVE-2012-5642: Escape the content of matches since its value could
+contain arbitrary symbols (Closes: #696184)
+ * Since package source format remained 1.0, manpages patch
+(deb_manpages_reportbug) was not applied -- fold it into .diff.gz
+
+ -- Yaroslav Halchenko deb...@onerussian.com Mon, 17 Dec 2012 13:19:32 -0500
+
fail2ban (0.8.6-3) unstable; urgency=low
* Added dovecot section to Debian's jail.conf. Thanks to Laurent
diff -u fail2ban-0.8.6/debian/gbp.conf fail2ban-0.8.6/debian/gbp.conf
--- fail2ban-0.8.6/debian/gbp.conf
+++ fail2ban-0.8.6/debian/gbp.conf
@@ -2,7 +2,7 @@
# the default branch for upstream sources:
upstream-branch = upstream
# the default branch for the debian patch:
-debian-branch = debian
+debian-branch = debian-releases/wheezy
# use pristine-tar
pristine-tar = True
# the default tag formats used:
reverted:
--- fail2ban-0.8.6/debian/patches/series
+++ fail2ban-0.8.6.orig/debian/patches/series
@@ -1 +0,0 @@
-deb_manpages_reportbug
reverted:
--- fail2ban-0.8.6/debian/patches/deb_manpages_reportbug
+++ fail2ban-0.8.6.orig/debian/patches/deb_manpages_reportbug
@@ -1,28 +0,0 @@
-From: Yaroslav Halchenko deb...@onerussian.com
-Date: Fri, 8 Feb 2008 00:40:57 -0500
-Subject: tune ups in upstream manpages to direct users to use reportbug
-
a/man/fail2ban-client.1
-+++ b/man/fail2ban-client.1
-@@ -251,7 +251,8 @@ action ACT for JAIL
- Written by Cyril Jaquier cyril.jaqu...@fail2ban.org.
- Many contributions by Yaroslav O. Halchenko deb...@onerussian.com.
- .SH REPORTING BUGS
--Report bugs to cyril.jaqu...@fail2ban.org
-+Please report bugs via Debian bug tracking system
-+http://www.debian.org/Bugs/.
- .SH COPYRIGHT
- Copyright \(co 2004-2008 Cyril Jaquier
- .br
a/man/fail2ban-server.1
-+++ b/man/fail2ban-server.1
-@@ -35,7 +35,8 @@ print the version
- Written by Cyril Jaquier cyril.jaqu...@fail2ban.org.
- Many contributions by Yaroslav O. Halchenko deb...@onerussian.com.
- .SH REPORTING BUGS
--Report bugs to cyril.jaqu...@fail2ban.org
-+Please report bugs via Debian bug tracking system
-+http://www.debian.org/Bugs/.
- .SH COPYRIGHT
- Copyright \(co 2004-2008 Cyril Jaquier
- .br
only in patch2:
unchanged:
--- fail2ban-0.8.6.orig/man/fail2ban-server.1
+++ fail2ban-0.8.6/man/fail2ban-server.1
@@ -35,7 +35,8 @@
Written by Cyril Jaquier cyril.jaqu...@fail2ban.org.
Many contributions by Yaroslav O. Halchenko deb...@onerussian.com.
.SH REPORTING BUGS
-Report bugs to cyril.jaqu...@fail2ban.org
+Please report bugs via Debian bug tracking system
+http://www.debian.org/Bugs/.
.SH COPYRIGHT
Copyright \(co 2004-2008 Cyril Jaquier
.br
only in patch2:
unchanged:
--- fail2ban-0.8.6.orig/man/fail2ban-client.1
+++ fail2ban-0.8.6/man/fail2ban-client.1
@@ -251,7 +251,8 @@
Written by Cyril Jaquier cyril.jaqu...@fail2ban.org.
Many contributions by Yaroslav O. Halchenko deb...@onerussian.com.
.SH REPORTING BUGS
-Report bugs to cyril.jaqu...@fail2ban.org
+Please report bugs via Debian bug tracking system
+http://www.debian.org/Bugs/.
.SH COPYRIGHT
Copyright \(co 2004-2008 Cyril Jaquier
.br
only in patch2:
unchanged:
--- fail2ban-0.8.6.orig/server/action.py
+++ fail2ban-0.8.6/server/action.py
@@ -230,7 +230,14 @@
def execActionStop(self):
stopCmd = Action.replaceTag(self.__actionStop, self.__cInfo)
return Action.executeCmd(stopCmd)
-
+
+ def escapeTag(tag):
+ for c in '\\#;`|*?~^()[]{}$\n':
+ if c in tag:
+ tag = tag.replace(c, '\\' + c)
+ return tag
+ escapeTag = staticmethod(escapeTag)
+
##
# Replaces tags in query with property values in aInfo.
#
@@ -243,8 +250,13 @@
Replace tags in query
string = query
- for tag in aInfo:
- string = string.replace('' + tag + '', str(aInfo[tag]))
+ for tag, value in aInfo.iteritems():
+ value = str(value)# assure string
+ if tag == 'matches':
+ # That one needs to be escaped since its content is
+ # out of our control
+ value = Action.escapeTag(value)
+ string = string.replace('' + tag + '', value)
# New line
string = string.replace(br
Bug#695935: RM: nipy/0.1.999-2
Thanks! On Tue, 01 Jan 2013, Julien Cristau wrote: On Fri, Dec 14, 2012 at 10:23:51 -0500, Yaroslav Halchenko wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm 0.1.999 was a pre-release uploaded before the freeze, while 0.2 was uploaded shortly after the release and besides fixing countless bugs it had quite a bit of restructuring/docs changes forbidding adequate review of the changes. remove hint added. -- Yaroslav O. Halchenko Postdoctoral Fellow, Department of Psychological and Brain Sciences Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- 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/20130102015428.gb26...@onerussian.com
Bug#692135: unblock: whohas/0.29-0.2
On Thu, 20 Dec 2012, Adam D. Barratt wrote: if above change is ok with you (if not -- feel free to elaborate or provide your wording) -- I could upload adjusted -0.3 to sid That looks fine; thanks. (Well, s/version/s/ to be picky.) -- I learned something new, thanks ;) I will upload shortly -- Yaroslav O. Halchenko Postdoctoral Fellow, Department of Psychological and Brain Sciences Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- 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/20121220134351.gb17...@onerussian.com
Bug#696405: unblock: whohas/0.29-0.3
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package whohas
Per Adam's suggestions (see #692135) wording in the patch description was
adjusted. See debdiff below
unblock whohas/0.29-0.3
Jonathan, I have pushed all my changes on top of your GIT to
http://git.onerussian.com/?p=deb/whohas.git
for you to update your official packaging repository
debdiffs:
$ debdiff ../0.29-0.2/whohas_0.29-0.2.dsc whohas_0.29-0.3.dsc
dpkg-source: warning: extracting unsigned source package
(/backup/neurodebian/deb/builds/whohas/0.29-0.3/whohas_0.29-0.3.dsc)
diff -Nru whohas-0.29/debian/changelog whohas-0.29/debian/changelog
--- whohas-0.29/debian/changelog2012-09-27 10:19:48.0 -0400
+++ whohas-0.29/debian/changelog2012-12-20 08:48:23.0 -0500
@@ -1,3 +1,11 @@
+whohas (0.29-0.3) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * debian/patches/10-debian-versions -- fixed up wording and removed
+obsolete meta-information (Thanks to Adam D. Barratt for the review)
+
+ -- Yaroslav Halchenko deb...@onerussian.com Thu, 20 Dec 2012 08:44:38 -0500
+
whohas (0.29-0.2) unstable; urgency=low
* Non-maintainer upload.
diff -Nru whohas-0.29/debian/patches/10-debian-versions
whohas-0.29/debian/patches/10-debian-versions
--- whohas-0.29/debian/patches/10-debian-versions 2012-09-27
10:12:02.0 -0400
+++ whohas-0.29/debian/patches/10-debian-versions 2012-12-20
08:48:23.0 -0500
@@ -1,7 +1,7 @@
From: Yaroslav Halchenko deb...@onerussian.com
Subject: Fetch all versions from the same page for Debian
-Similarly to Ubuntu's logic supplied in the previous patch -- fetch all version
+Similarly to Ubuntu's logic supplied in 06-ubuntu-versions patch -- fetch all
versions
available from the same page without querying each suite separately. This way
we also get possibly present urls to backports (#655497). Also altogether
should be more efficient avoiding multiple fetches/parsings.
@@ -9,10 +9,6 @@
Origin: Debian
Bug-Debian: http://bugs.debian.org/655497
Last-Update: 2012-09-27
-
-## Description: Add unstable and experimental Debian repositories.
-## Origin/Author: Jonathan Wiltshire deb...@jwiltshire.org.uk
-## Bug: https://bugs.debian.org/511364
--- a/program/whohas
+++ b/program/whohas
@@ -938,7 +938,7 @@ sub debian_size_convert {
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental'), (100,
'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--
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/20121220135807.13078.19688.report...@novo.onerussian.com
Bug#692135: unblock: whohas/0.29-0.2
Hi Adam, thanks for looking into it: On Wed, 19 Dec 2012, Adam D. Barratt wrote: --- whohas-0.29/debian/patches/10-debian-versions 2012-01-15 18:21:29.0 + +++ whohas-0.29/debian/patches/10-debian-versions 2012-09-27 14:12:02.0 + @@ -1,16 +1,26 @@ +From: Yaroslav Halchenko deb...@onerussian.com +Subject: Fetch all versions from the same page for Debian + +Similarly to Ubuntu's logic supplied in the previous patch -- fetch all version Referring simply to the previous patch seems somewhat odd here - would this change be sufficient? -Similarly to Ubuntu's logic supplied in the previous patch -- fetch all version +Similarly to Ubuntu's logic supplied in 06-ubuntu-versions patch -- fetch all version there's no guarantee the patch in question will even be in the package at any future point, yet alone be the previous patch. IIRC if 06-ubuntu-versions gets dropped, 'all' logic would not be implemented, thus 10-debian-versions would get broken. Therefore I am not expecting 10-debian-versions to exist without 06-ubuntu-versions (it is also unlikely for upstream to adopt one without another). The meta-data is also now wrong: ## Description: Add unstable and experimental Debian repositories. ## Origin/Author: Jonathan Wiltshire deb...@jwiltshire.org.uk ## Bug: https://bugs.debian.org/511364 indeed -- removed Unblocked, but I wouldn't be entirely averse to an update fixing the headers. if above change is ok with you (if not -- feel free to elaborate or provide your wording) -- I could upload adjusted -0.3 to sid -- Yaroslav O. Halchenko Postdoctoral Fellow, Department of Psychological and Brain Sciences Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- 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/20121219204329.gx17...@onerussian.com
Bug#695935: RM: nipy/0.1.999-2
On Sat, 15 Dec 2012, Julien Cristau wrote: Control: tag -1 moreinfo Block request for 0.2-1, filed in July, was finally rejected due to too late reason [0]. Upon discussion with upstream [1], we decided that it would be better for all not to ship 0.1.999 at all in Debian wheezy. 0.2 would be available from sid, backports for it would be available from NeuroDebian (or may be even from b.d.o whenever that would be possible). # Broken Build-Depends: nipype: python-nipy (= 0.1.2+20101206-1~) Do you want that removed as well? d'oh -- my bad, thanks -- forgotten that I have added it as an optional build-dependency for extended testing. Let me upload adjusted nipype without nipy build-dependency to sid to get into wheezy first, so we could proceed with the RM of nipy. -- Yaroslav O. Halchenko Postdoctoral Fellow, Department of Psychological and Brain Sciences Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- 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/20121215201429.gj17...@onerussian.com
Bug#695935: RM: nipy/0.1.999-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm 0.1.999 was a pre-release uploaded before the freeze, while 0.2 was uploaded shortly after the release and besides fixing countless bugs it had quite a bit of restructuring/docs changes forbidding adequate review of the changes. Block request for 0.2-1, filed in July, was finally rejected due to too late reason [0]. Upon discussion with upstream [1], we decided that it would be better for all not to ship 0.1.999 at all in Debian wheezy. 0.2 would be available from sid, backports for it would be available from NeuroDebian (or may be even from b.d.o whenever that would be possible). So please remove 0.1.999 from wheezy Cheers, [0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683292 [1] e.g. http://grokbase.com/p/neuroimaging.scipy.org/nipy-devel/12c3xa8yx4/debian-wheezy-keep-or-kick-0-1-999 -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental'), (100, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- 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/20121214152351.27272.49661.report...@novo.onerussian.com
Bug#683292: unblock: nipy/0.2.0-1
On Sat, 01 Dec 2012, Julien Cristau wrote: On Mon, Jul 30, 2012 at 11:22:04 -0400, Yaroslav Halchenko wrote: unblock nipy/0.2.0-1 Looks like this is too big and too late. Closing, sorry. taking into account that this report was opened in July, too late in particular sounds like a mockery to me making the whole freezing a farce especially given my original detailed reasoning for this freeze exception. Have a good weekend -- Yaroslav O. Halchenko Postdoctoral Fellow, Department of Psychological and Brain Sciences Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- 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/20121201145617.gv7...@onerussian.com
Bug#692135: unblock: whohas/0.29-0.2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package whohas
More than a month ago I have NMU-ed two fixes:
* Fixed and improved 06-ubuntu-versions to get information on all
reported releases for Ubuntu (Closes: #670675)
before it was reporting only 1 ubuntu release, making this tool useless for me
* Adjusted 10-debian-versions to rely on fixed in 06-ubuntu-versions
functionality to fetch information on all available releases at once,
instead of looping through predefined list of releases. This way
it should obtain information about oldstable and backports when
available (Closes: #616297,#655497)
which made it much faster and increased coverage
Those fixes rendered package usable again for people in the land of Debian and
its derivatives. I have been using it quite often since then and have not seen
any side-effects of my patches. I am also attaching a complete debdiff for the
-0.2 package from -0.1 in wheezy ATM -- my fix is pretty much just 1 chunk of
perl code, which I am not expert in, but which was based on the previously
shipped patch (removed by mistake in -0.1) and this code seems to function
properly atm.
Cheers,
unblock whohas/0.29-0.2
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental'), (100,
'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
diff -Nru whohas-0.29/debian/changelog whohas-0.29/debian/changelog
--- whohas-0.29/debian/changelog 2012-01-15 14:13:43.0 -0500
+++ whohas-0.29/debian/changelog 2012-09-27 10:19:48.0 -0400
@@ -1,3 +1,17 @@
+whohas (0.29-0.2) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Fixed and improved 06-ubuntu-versions to get information on all
+reported releases for Ubuntu (Closes: #670675)
+ * Adjusted 10-debian-versions to rely on fixed in 06-ubuntu-versions
+functionality to fetch information on all available releases at once,
+instead of looping through predefined list of releases. This way
+it should obtain information about oldstable and backports when
+available (Closes: #616297,#655497)
+ * The other patches in the series were updated
+
+ -- Yaroslav Halchenko deb...@onerussian.com Thu, 27 Sep 2012 10:14:28 -0400
+
whohas (0.29-0.1) unstable; urgency=low
* Non-maintainer upload.
diff -Nru whohas-0.29/debian/patches/06-ubuntu-versions whohas-0.29/debian/patches/06-ubuntu-versions
--- whohas-0.29/debian/patches/06-ubuntu-versions 2012-01-15 12:34:13.0 -0500
+++ whohas-0.29/debian/patches/06-ubuntu-versions 2012-09-27 10:09:51.0 -0400
@@ -1,8 +1,27 @@
-Index: whohas-0.29/program/whohas
-===
whohas-0.29.orig/program/whohas 2012-01-15 14:33:25.223864820 -0300
-+++ whohas-0.29/program/whohas 2012-01-15 14:34:10.853958060 -0300
-@@ -51,7 +51,7 @@
+From: Yaroslav Halchenko deb...@onerussian.com
+Subject: Reincarnated and refactored the patch to fetch multiple suites from listing page for ubuntu (and Debian)
+
+original patch had header:
+## 06-ubuntu-versions-510203.dpatch by Jonathan Wiltshire deb...@jwiltshire.org.uk
+##
+## All lines beginning with `## DP:' are a description of the patch.
+## DP: Patch to show all versions of a package from Ubuntu, not just
+## DP: the earliest, see bug 510203.
+## DP: Additionally, show the repo that the package is from (eg. universe)
+## DP: Original patch from Steve Cotton steve0...@s.cotton.clara.co.uk
+## DP: Status: forwarded upstream to Philipp Wesche phi1...@yahoo.com
+
+I have not relied on it actually but redone it, this time relying more on the
+markup instead of lines counts. Also fixed stripping of additional HREFs after
+the version (e.g. to backports repo)
+
+Origin: Debian
+Bug-Debian: http://bugs.debian.org/670675
+Last-Update: 2012-09-27
+
+--- a/program/whohas
b/program/whohas
+@@ -51,7 +51,7 @@ my @columns = (11,38,18,4,10,25);
my $cols = 6;
my $fedora_release = 16 ;
@@ -11,3 +30,46 @@
my $opensuse_major = 12 ;
my $opensuse_minor = 1 ;
my $mandrivaVersion = 2011.0 ;
+@@ -964,17 +964,31 @@ sub debuntu {
+ for (my $i = 50; $i @lines; $i++) {
+ if ($lines[$i] =~ /h3Package /) {
+ my $name = (split /h3Package |\/h3/, $lines[$i])[1];
+-push @names, $name;
+-my @parts = split /href\=\|\\|\/a\/, $lines[$i+3];
+-$parts[4] =~ s/ \(|\)://g;
+-push @groups, $parts[4];
+-push @repos, $dists[$x];
+-push @urls, $baseurl.$parts[2];
+-push @dates, ;
+-@parts = split /|: /, $lines[$i+6];
+-$parts[1] =~ s/ \[\strong.*//;
+-push @versions, $parts[1];
+-$i += 11;
++# There are now one or more 8-line blocks
fix to scipy into wheezy proposed-updates?
Dear Release team,
While building a squeeze backport of new release of python-brian package
I just found out that there is a g++ 4.4 compatibility issue with weave
of scipy shipped in squeeze. Fix is trivial -- I adopted it from a
package in Ubuntu (links are in the patch). I tested that it
resolves my brian build failures. See attached the debdiff for a
proposed upload. Would it be acceptable? Thank you in advance
--
Yaroslav O. Halchenko
Postdoctoral Fellow, Department of Psychological and Brain Sciences
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419
WWW: http://www.linkedin.com/in/yarik
diff -Nru python-scipy-0.7.2+dfsg1/debian/changelog
python-scipy-0.7.2+dfsg1/debian/changelog
--- python-scipy-0.7.2+dfsg1/debian/changelog 2010-07-30 18:35:56.0
-0400
+++ python-scipy-0.7.2+dfsg1/debian/changelog 2012-08-31 09:54:37.0
-0400
@@ -1,3 +1,11 @@
+python-scipy (0.7.2+dfsg1-1+squeeze1) stable; urgency=low
+
+ * Team upload.
+ * Patch weave-739.patch to include cstdlib in blitz/*.h for weave inline
+functionality (Closes: #686353)
+
+ -- Yaroslav Halchenko deb...@onerussian.com Fri, 31 Aug 2012 09:46:13 -0400
+
python-scipy (0.7.2+dfsg1-1) unstable; urgency=low
* Release with a new source tarball with missing cython source files
diff -Nru python-scipy-0.7.2+dfsg1/debian/patches/series
python-scipy-0.7.2+dfsg1/debian/patches/series
--- python-scipy-0.7.2+dfsg1/debian/patches/series 2010-06-07
08:51:28.0 -0400
+++ python-scipy-0.7.2+dfsg1/debian/patches/series 2012-08-31
09:44:24.0 -0400
@@ -1,2 +1,3 @@
restore_sys_argv.patch
string_exception.patch
+weave-739.patch
diff -Nru python-scipy-0.7.2+dfsg1/debian/patches/weave-739.patch
python-scipy-0.7.2+dfsg1/debian/patches/weave-739.patch
--- python-scipy-0.7.2+dfsg1/debian/patches/weave-739.patch 1969-12-31
19:00:00.0 -0500
+++ python-scipy-0.7.2+dfsg1/debian/patches/weave-739.patch 2012-08-31
09:46:05.0 -0400
@@ -0,0 +1,41 @@
+From: Yaroslav Halchenko deb...@onerussian.com
+Author: Sameer Morar smo...@gmail.com
+Description: compatibility with g++ 4.4
+
+Origin: http://projects.scipy.org/scipy/attachment/ticket/739/weave-739.patch
+Applied-Upstream: 6e1155ea14e85efdb6c3d944ded3583c12d01778
+Last-Update: 2012-08-31
+
+--- a/scipy/weave/blitz/blitz/mathfunc.h
b/scipy/weave/blitz/blitz/mathfunc.h
+@@ -12,6 +12,8 @@
+ #include blitz/prettyprint.h
+ #endif
+
++#include cstdlib
++
+ BZ_NAMESPACE(blitz)
+
+ // abs(P_numtype1)Absolute value
+--- a/scipy/weave/blitz/blitz/blitz.h
b/scipy/weave/blitz/blitz/blitz.h
+@@ -65,6 +65,8 @@
+
+ #define BZ_THROW // Needed in blitz/numinquire.h
+
++#include cstdlib
++
+ BZ_NAMESPACE(blitz)
+
+ #ifdef BZ_HAVE_STD
+--- a/scipy/weave/blitz/blitz/prettyprint.h
b/scipy/weave/blitz/blitz/prettyprint.h
+@@ -22,6 +22,8 @@
+ #ifndef BZ_PRETTYPRINT_H
+ #define BZ_PRETTYPRINT_H
+
++#include cstdlib
++
+ BZ_NAMESPACE(blitz)
+
+ class prettyPrintFormat {
signature.asc
Description: Digital signature
Re: fix to scipy into wheezy proposed-updates?
fixed python-scipy/0.8.0-1 thanks On Fri, 31 Aug 2012, Adam D. Barratt wrote: On Fri, 2012-08-31 at 11:53 -0400, Yaroslav Halchenko wrote: While building a squeeze backport of new release of python-brian package I just found out that there is a g++ 4.4 compatibility issue with weave of scipy shipped in squeeze. Fix is trivial -- I adopted it from a package in Ubuntu (links are in the patch). I tested that it resolves my brian build failures. See attached the debdiff for a proposed upload. Would it be acceptable? Thank you in advance Do you mean for wheezy, or for squeeze? The subject says wheezy, but: sorry -- I was dreaming I guess while composing the subject. It is intended for the current stable -- squeeze +python-scipy (0.7.2+dfsg1-1+squeeze1) stable; urgency=low In either case, the fix doesn't appear to be in unstable? it is fixed upstream in ... according to gitk: Author: Stefan van der Walt ste...@sun.ac.za 2009-01-08 10:01:34 Committer: Stefan van der Walt ste...@sun.ac.za 2009-01-08 10:01:34 Parent: a409f9f8886baac8057b0a9f256165c724eae9ff (Backport a couple of trivial fixes from 0.7.x (5397:5398).) Child: d8cb63968a8036e16190839b4948edc8a7a910a5 (Fix gcc 4.3 warnings in weave.) Follows: v0.4.3 Precedes: v0.10.0b1, v0.11.0b1, v0.8.0b1, v0.9.0b1 Include cstdio to provide `labs` to gcc 4.3. so I guess it was fixed in 0.8.0 ... marking as such with this email -- Yaroslav O. Halchenko Postdoctoral Fellow, Department of Psychological and Brain Sciences Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik signature.asc Description: Digital signature
Re: fix to scipy into wheezy proposed-updates?
On Fri, 31 Aug 2012, Julien Cristau wrote: While building a squeeze backport of new release of python-brian package I just found out that there is a g++ 4.4 compatibility issue with weave of scipy shipped in squeeze. Fix is trivial -- I adopted it from a package in Ubuntu (links are in the patch). I tested that it resolves my brian build failures. See attached the debdiff for a proposed upload. Would it be acceptable? Thank you in advance Does that affect any package in squeeze? not AFAIK (I cannot know for sure since many packages lack build-time unittesting so even if package uses affected inline weave'ing I would not know). otherwise we would have spotted it by now ;) If not then I don't think this is required, as it can easily enough be worked around in users? not sure if easily since the majority of magic is hidden away from users, e.g. actual code would look like: (Pdb) print code int numspikes=0; for(int i=0;iN;i++) if(V(i)Vt) spikes(numspikes++) = i; return_val = numspikes; and then bug shows itself up via using blitz typeconverter which shipped with scipy aren't g++ 4.4 compatible. may be there is a 'user-level' workaround but I am not aware of it... anyone? Altogether acceptance of the patch would not fix any FTBFS in the stable archive but should make few scipy users of 'stable' happier. Due to minimalistic patch, I do not think that it should have negative side-effects. -- Yaroslav O. Halchenko Postdoctoral Fellow, Department of Psychological and Brain Sciences Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- 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/20120831191911.gv2...@onerussian.com
Bug#681233: unblock: pynn/0.7.4-1
unblocked anyway...
thanks Julien! you made me blush that I have missed them in my
quick review of the changes.
NB I am CCing upstream who might like to straighten those up
On Wed, 22 Aug 2012, Julien Cristau wrote:
def setup(timestep=0.1, min_delay=0.1, max_delay=0.1,
debug=False,**extra_params):
+
+logger.debug(setup() called, extra_params = +str(extra_params))
this is broken, surely it should be below the docstring?
ideally -- yes -- but should be harmless
Should be called at the very beginning of a script.
extra_params contains any keyword arguments that are required by a
given
simulator but not by others.
also the sys.path.append('/usr/lib/python2.x/site-packages/oldxml')
seems like a horrible, horrible hack.
indeed... with not 100% clear motive (besides suggesting wanting
an older xml module, which was just bluntly manually copied on
that system).
Andrew -- could you clarify?:
src/neuroml.py:sys.path.append('/usr/lib/python%s/site-packages/oldxml' %
sys.version[:3]) # needed for Ubuntu
src/neuroml2.py:sys.path.append('/usr/lib/python%s/site-packages/oldxml' %
sys.version[:3]) # needed for Ubuntu
may be those are just left-overs which could be safely dropped?
--
Yaroslav O. Halchenko
Postdoctoral Fellow, Department of Psychological and Brain Sciences
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419
WWW: http://www.linkedin.com/in/yarik
--
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/20120822160843.gn2...@onerussian.com
Bug#683292: unblock: nipy/0.2.0-1
Hi Adam, Thanks you looking at the package. On Fri, 17 Aug 2012, Adam D. Barratt wrote: I am attaching a gzipped debdiff on .dsc from 0.2.0~rc2+git27-g7b9b5a5-1 -- there is a bulk of changes indeed BUT most of them are examples and documentation fixes; all functionality changes/fixes were accompanied with unittests and passed peer-review. Neither of those changes should effect python-nipy -- the only package (loosly) depending on nipy. Even after dropping doc/*, examples/*, tests/* and whitespace-only changes, the debdiff is still 137 files changed, 16586 insertions(+), 8818 deletions(-) I'm not sure how we're supposed to sanely review that. Sorry for dumping that big diff on you... even besides whitespace changes there was a bulk of docstrings changes which could not be filtered easily indeed. it might be worth looking at the upstream log of changes instead: $ git log --pretty=oneline debian/0.2.0_rc2+git27-g7b9b5a5-1...debian/0.2.0-1 -- nipy 1cbe46b0038255bd6fad9438236427f397133b8f REL: bump info to indicate 0.2.0 release bacaa6c98758211df69e6e5a6cf737ccc94399e9 MISC: make interfaces tests a package 83ff905c38cf40e7610a9ac693191307c36a7898 DOC: harmonize README and info.py c6b4dc1b1cf13be42ea2aa2a2ebe4eb46c7e1df0 DOC: point to collated data installation page f66cefa8daeea5e4b9a17fd729939aa27a84aafd DOC: fix section heading in fmri.utils 10cd8c168232dbd821cc96f6a0c0b5c8183cb75a Merge pull request #203 from matthew-brett/convolve-review 4e913137a2d822bd336e1119c4ad0d1991b854d6 HACK: add diag_indices helper for numpy 1.4.0 e14dbaa0a4158cd9e8434ffd72a51c20f9893422 Merge branch 'multichannel-segmentation' into main-master 192a085cd64526e98de7d8f9e947669676b3f72a MISC: update generated .c files from .pyx files a3ec7b96724944a4cf1736c7a9318c6f95c6f2a1 fixed type error related to numpy.exp 280746985c4d4c89c8c2385df7887340c6e899aa RF+TST: refactor convolve_functions interface 8a18eaed46eec59074121ff4b1756de6f1239b6f DOC: add note from Jonathan about bug in convolve 377d246f4d0b45bf6f3a7dbba3691d70e28329a8 RF+API: change interp behavior for fill arguments dc1fb39d9a0b3ba227cee77f9e358850066c2979 Merge pull request #200 from matthew-brett/fmri-utils-fixes 9dca074b8be768140f2d5412488d4d2915f84721 fixed 64-bit bug in histogram cython function d20376a81e281d4e4f1586ebc4ec7f8910f93727 add optional user-specified initialization for brain seg class ee1d022d99ed8394a9e6e7ca94081568fd8d4066 fixed 64-bit bug + add related tests b5b6dbae14c9eec357df1dc5ae22a375cba8b788 minor clean up 744f6e009bb951137055b8b9dccf03556b114fb1 update reference parameters for segmentation initialization d04598f62dbe16b7bece15430fe7e722be2f1d85 fix numerical issue 1381389181f029fb2803d86dce3da01cdd2db3fd slight refactoring of the brain segmentation class and further tests fdf8029db06217d69bc0a1acc7588f47269c633b add short comment 231ea9c71a1a959dbf30f09dd27a863ccd744337 enable ngb_size input argument in BrainSegmentation class 119b91da725d35d71d3f74c3d0850103554d4b8e adding a histogram test 4adf405b207d151fcfbee4711a7adfee174a0def add segmentation tests + some code cleaning 438b52a68399e08a636f6bba4a563558d998593b remove nibabel dependency in tissue classification example c8a3dd1103f1d80484ae607a1eb27eb3425a84f9 generalize brain segmentation model fa7aed950016eaa929ceabde94bcef3faf5464b7 fixed imports b564596fa7cf057203ea78e7f7a9446e584a130e fixed tests f53d8cf6a6c9c2449a7d377be3792704b0fe0ff1 adding a fast histogram routine in algorithms.statistics f5019dfa041e1c12b7bcdeaeef8121d5297b40c1 fix memory leak 7ee5a0f49eab5a1159b8462e734cf910582a72df redesign brain segmentation model 965cd4f3bef45f6d339818168cec43f88bdc6f91 copy input parameter arrays in segmentation db3a533db05a9c3a6ebbca1be24b2da1a0dfbc32 removed print statementsw e5398287b4172d220220d23dfba08dcc687caadd small API change in Segmentation class 147bec1ee46d206300eb7a269086320c92f364fd fixed free energy computation under no zero-beta 035989a5e37862af6a83e4bc7cc3821b11f293f8 initialize VEM using proper uniform distributions 60ed6b92727dfd400aea4c20978dfdd681cbb460 fix segfault 02db1b46b15bfafc95cf1aa35a52e854585a6550 implement free energy computation f0aed02cf7754a7577f0699fb6c1330ebd84b1f9 some cleaning cec78e65488ad95ab572d0cab7f788d316f3b12b improve behavior of edge making function 32b41ba05abb52ea81cd1fbe858b53df09cf97a8 Fixed error message, minor change 4c899421d8f0262d014418bae0cc39449dc9c3e8 implement edge computation method and rigorous boundary checks ac34942e1010e1d32ff8023ca52e8d6b2c9cc874 make customizable neighborhood system in segmentation b7f00ea81d16ec21be9b28039f1ffa3267e1d3fc generalizing segmentation code to multichannel problems 5b3511525f51d4b2d434696ae37f74d88ce0b2a0 more general MRF model 4aac1573b55c94b17cf81eef423947cc35f038a3 TST: add test for step_function and block names b1aeb67a5addfd9a018ccffcaf8b00567aa70eaf NF: adding a name to blocks cfdad830baaf77620b4ba7650131c99b4344333b
Bug#683738: unblock: joblib/0.6.4-3
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package joblib
Had to fix kfreebsd compatibility issue which was detected/triggered by
statsmodels unittests ran at build time
unblock joblib/0.6.4-3
neurodebian@head2:~/deb/builds/joblib$ debdiff 0.6.4-1/joblib_0.6.4-1.dsc
0.6.4-3/joblib_0.6.4-3.dsc
diff -Nru joblib-0.6.4/debian/changelog joblib-0.6.4/debian/changelog
--- joblib-0.6.4/debian/changelog 2012-05-07 22:35:53.0 -0400
+++ joblib-0.6.4/debian/changelog 2012-07-23 14:36:37.0 -0400
@@ -1,3 +1,18 @@
+joblib (0.6.4-3) unstable; urgency=low
+
+ * debian/patches/up_no_parallel_if_no_locking -- needed more work for
+python2.6 compatibility where the exception was not triggered.
+
+ -- Yaroslav Halchenko deb...@onerussian.com Mon, 23 Jul 2012 14:35:45 -0400
+
+joblib (0.6.4-2) unstable; urgency=low
+
+ * debian/patches/up_no_parallel_if_no_locking -- additional check for
+availability of locking mechanisms to decide upon using multiprocessing.
+Needed for robust functioning on kfrebsd systems.
+
+ -- Yaroslav Halchenko deb...@onerussian.com Mon, 16 Jul 2012 22:59:47 -0400
+
joblib (0.6.4-1) unstable; urgency=low
* New upstream release
diff -Nru joblib-0.6.4/debian/patches/series joblib-0.6.4/debian/patches/series
--- joblib-0.6.4/debian/patches/series 2012-05-07 22:35:53.0 -0400
+++ joblib-0.6.4/debian/patches/series 2012-07-23 14:36:37.0 -0400
@@ -0,0 +1 @@
+up_no_parallel_if_no_locking
diff -Nru joblib-0.6.4/debian/patches/up_no_parallel_if_no_locking
joblib-0.6.4/debian/patches/up_no_parallel_if_no_locking
--- joblib-0.6.4/debian/patches/up_no_parallel_if_no_locking1969-12-31
19:00:00.0 -0500
+++ joblib-0.6.4/debian/patches/up_no_parallel_if_no_locking2012-07-23
14:36:37.0 -0400
@@ -0,0 +1,30 @@
+From: Yaroslav Halchenko deb...@onerussian.com
+Subject: joblib uses .Pool which requres locking to be available on the
platform
+
+e.g. needed on kfreebsd systems -- otherwise would try to initiate the .Pool
+and would backtrace -- leads to FTBFS of any package which excercizes
+build-time tests using joblib, e.g. statsmodels
+
+Origin: Debian
+Forwarded: https://github.com/joblib/joblib/pull/39
+Last-Update: 2012-07-16
+
+--- a/joblib/parallel.py
b/joblib/parallel.py
+@@ -28,6 +28,16 @@ if multiprocessing:
+ except ImportError:
+ multiprocessing = None
+
++# 2nd stage: validate that locking is available on the system and
++#issue a warning if not
++if multiprocessing:
++try:
++_sem = multiprocessing.Semaphore()
++del _sem # cleanup
++except (ImportError, OSError), e:
++multiprocessing = None
++warnings.warn('%s. joblib will operate in serial mode' % (e,))
++
+ from .format_stack import format_exc, format_outer_frames
+ from .logger import Logger, short_format_time
+ from .my_exceptions import TransportableException, _mk_exception
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental'), (100,
'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--
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/20120803130952.23534.49639.report...@novo.onerussian.com
Bug#683740: unblock: statsmodels/0.4.2-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package statsmodels Sorry -- I have missed 30th of July deadline... 0.4.2-1 was uploaded on June 30th, but due to a FTBFS on kfreebsd's (only) it did not propagate (#678708). The issue was resolved by fixing joblib, statsmodels build-depends upon and I have just filed unblock request for it (#683738). Otherwise -- package is in a great shape, does unittesting at build time and they pass all around. unblock statsmodels/0.4.2-1 -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental'), (100, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- 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/20120803131952.24168.15066.report...@novo.onerussian.com
Bug#683741: unblock: gamin/0.1.10-4.1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package gamin
unblock gamin/0.1.10-4.1
This NMU fixed (according to my experience too) an old grave bug which
made gamin unusable before.
$ debdiff 0.1.10-4/gamin_0.1.10-4.dsc 0.1.10-4.1/gamin_0.1.10-4.1.dsc
dpkg-source: warning: extracting unsigned source package
(/backup/neurodebian/deb/builds/gamin/0.1.10-4.1/gamin_0.1.10-4.1.dsc)
diff -Nru gamin-0.1.10/debian/changelog gamin-0.1.10/debian/changelog
--- gamin-0.1.10/debian/changelog 2011-10-18 10:19:06.0 -0400
+++ gamin-0.1.10/debian/changelog 2012-07-19 22:08:26.0 -0400
@@ -1,3 +1,11 @@
+gamin (0.1.10-4.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Add 18_gam_server_deadlocks.patch: removes locking from ih_sub_cancel()
+to resolve intermittent deadlocks (Closes: #542361)
+
+ -- Yaroslav Halchenko deb...@onerussian.com Thu, 19 Jul 2012 22:03:23 -0400
+
gamin (0.1.10-4) unstable; urgency=low
* Add 17_deprecated_const_return.patch: Don't use deprecated G_CONST_RETURN.
diff -Nru gamin-0.1.10/debian/control gamin-0.1.10/debian/control
--- gamin-0.1.10/debian/control 2011-10-18 10:22:12.0 -0400
+++ gamin-0.1.10/debian/control 2012-07-19 22:34:18.0 -0400
@@ -7,7 +7,7 @@
Section: admin
Priority: optional
Maintainer: Michael Banck mba...@debian.org
-Uploaders: Debian GNOME Maintainers
pkg-gnome-maintain...@lists.alioth.debian.org, Emilio Pozuelo Monfort
po...@debian.org, Josselin Mouette j...@debian.org, Loic Minier
l...@dooz.org, Sebastian Dröge sl...@debian.org
+Uploaders: Debian GNOME Maintainers
pkg-gnome-maintain...@lists.alioth.debian.org, Emilio Pozuelo Monfort
po...@debian.org, Loic Minier l...@dooz.org, Martin Pitt
mp...@debian.org, Sebastian Dröge sl...@debian.org
Build-Depends: cdbs (= 0.4.73),
debhelper( = 5.0.37.2),
libglib2.0-dev,
diff -Nru gamin-0.1.10/debian/patches/18_gam_server_deadlocks.patch
gamin-0.1.10/debian/patches/18_gam_server_deadlocks.patch
--- gamin-0.1.10/debian/patches/18_gam_server_deadlocks.patch 1969-12-31
19:00:00.0 -0500
+++ gamin-0.1.10/debian/patches/18_gam_server_deadlocks.patch 2012-07-19
22:02:48.0 -0400
@@ -0,0 +1,70 @@
+From cc14440eface093548cb3bc7814da11d9a99d283 Mon Sep 17 00:00:00 2001
+From: Anssi Hannula an...@mageia.org
+Date: Wed, 4 Jan 2012 00:23:55 +0200
+Subject: [PATCH] fix possible server deadlock in ih_sub_cancel
+
+ih_sub_foreach() calls ih_sub_cancel() while inotify_lock is locked.
+However, ih_sub_cancel() locks it again, and locking GMutex recursively
+causes undefined behaviour.
+
+Fix that by removing locking from ih_sub_cancel() as ih_sub_foreach()
+is its only user. Also make the function static so that it won't
+accidentally get used by other files without locking (inotify-helper.h
+is an internal server header).
+
+This should fix the intermittent deadlocks I've been experiencing
+causing KDE applications to no longer start, and probably also
+http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=542361
+
+Origin: http://bugzilla-attachments.gnome.org/attachment.cgi?id=204537
+Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/gamin/+bug/926862
+Bug-Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=542361
+
+---
+ server/inotify-helper.c |7 ++-
+ server/inotify-helper.h |1 -
+ 2 files changed, 2 insertions(+), 6 deletions(-)
+
+diff --git a/server/inotify-helper.c b/server/inotify-helper.c
+index d77203e..0789fa4 100644
+--- a/server/inotify-helper.c
b/server/inotify-helper.c
+@@ -123,13 +123,11 @@ ih_sub_add (ih_sub_t * sub)
+
+ /**
+ * Cancels a subscription which was being monitored.
++ * inotify_lock must be held when calling.
+ */
+-gboolean
++static gboolean
+ ih_sub_cancel (ih_sub_t * sub)
+ {
+- G_LOCK(inotify_lock);
+-
+-
+ if (!sub-cancelled)
+ {
+ IH_W(cancelling %s\n, sub-pathname);
+@@ -140,7 +138,6 @@ ih_sub_cancel (ih_sub_t * sub)
+ sub_list = g_list_remove (sub_list, sub);
+ }
+
+- G_UNLOCK(inotify_lock);
+ return TRUE;
+ }
+
+diff --git a/server/inotify-helper.h b/server/inotify-helper.h
+index 5d3b6d0..d36b5fd 100644
+--- a/server/inotify-helper.h
b/server/inotify-helper.h
+@@ -34,7 +34,6 @@ gboolean ih_startup (event_callback_t ecb,
+found_callback_t fcb);
+ gboolean ih_running (void);
+ gboolean ih_sub_add (ih_sub_t *sub);
+-gboolean ih_sub_cancel (ih_sub_t *sub);
+
+ /* Return FALSE from 'f' if the subscription should be cancelled */
+ void ih_sub_foreach (void *callerdata, gboolean (*f)(ih_sub_t *sub,
void *callerdata));
+--
+1.7.7.2
+
diff -Nru gamin-0.1.10/debian/patches/series gamin-0.1.10/debian/patches/series
--- gamin-0.1.10/debian/patches/series 2011-10-18 10:12:20.0 -0400
+++ gamin-0.1.10/debian/patches/series 2012-07-19 21:59:58.0 -0400
@@ -2,4 +2,5 @@
15_kfreebsd.patch
16_armel
Re: would it be possible to reinstantiate openmeeg and ants in wheezy?
Thank you Niels -- I am reporting that I have filed those bug reports and closed #679315 (succeeded upon re-build) On Sat, 28 Jul 2012, Niels Thykier wrote: ants [...] FTBFS atm on mips, mipsel, s390 imho due to insufficient resources and might be tricky to make them build reliably What is keeping this package out is the fact there it FTBFS on mips, mipsel and s390. If your package is unsupported (or unsupportable) on these architectures, have the FTP masters remove the binaries on these architectures in unstable. #683086 Pretty much the same story as ants, though #679315 is still open despite looking fixed. Please close that bug as well. closed and opened #683085 for ftp.debian.org -- Yaroslav O. Halchenko Postdoctoral Fellow, Department of Psychological and Brain Sciences Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- 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/20120728145041.gg16...@onerussian.com
Re: would it be possible to reinstantiate openmeeg and ants in wheezy?
any feedback would be welcome Cheers, On Thu, 05 Jul 2012, Yaroslav Halchenko wrote: Hi Release Team, 2 packages of mine, primarily due to demanding resources for build (c++ with heavy use of templating) and testing (I do prefer to do build-time testing and they use realistic data) always were somewhat problematic to be built across architectures; thus they were removed from wheezy (while in testing) whenever new FTBFS were detected. Both are highly specialized to the field of neuroimaging. Both are old versions (see below) but relatively popular as for a specialized software. ants Slightly updated snapshot version than then one in squeeze Fresh upstream version requires fresh ITK (in experimental) popcon ~100 FTBFS atm on mips, mipsel, s390 imho due to insufficient resources and might be tricky to make them build reliably openmeeg The same upstream version as in squeeze -- minor additional patching (gcc 4.7) + enabled build time unittests Fresh upstream requires fresh libmat (in experimental) popcon ~200 FTBFS atm on mips only, and could be resolved simply through disabling build time unittesting I wondered, than even if I manage to overcome FTBFS on those -- would they be allowed to come back to wheezy? Thanks in advance -- Yaroslav O. Halchenko Postdoctoral Fellow, Department of Psychological and Brain Sciences Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- 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/20120714013839.gb5...@onerussian.com
Bug#681536: unblock: pandas/0.8.0-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Please unblock package pandas Very simple fix -- just tagged a test requiring network access (those are excluded from being run in debian/rules). This closes #681449 unblock pandas/0.8.0-2 Complete diff: diff -Nru pandas-0.8.0/debian/changelog pandas-0.8.0/debian/changelog --- pandas-0.8.0/debian/changelog 2012-06-29 13:37:46.0 -0400 +++ pandas-0.8.0/debian/changelog 2012-07-13 08:57:31.0 -0400 @@ -1,3 +1,11 @@ +pandas (0.8.0-2) unstable; urgency=medium + + * up_tag_yahoo_test_requiring_network patch cherry-picked from upstream +GIT so that tests would not be excercised at package build time +(Closes: #681449) + + -- Yaroslav Halchenko deb...@onerussian.com Fri, 13 Jul 2012 08:54:41 -0400 + pandas (0.8.0-1) unstable; urgency=low * Fresh upstream release diff -Nru pandas-0.8.0/debian/patches/series pandas-0.8.0/debian/patches/series --- pandas-0.8.0/debian/patches/series 1969-12-31 19:00:00.0 -0500 +++ pandas-0.8.0/debian/patches/series 2012-07-13 08:57:31.0 -0400 @@ -0,0 +1 @@ +up_tag_yahoo_test_requiring_network diff -Nru pandas-0.8.0/debian/patches/up_tag_yahoo_test_requiring_network pandas-0.8.0/debian/patches/up_tag_yahoo_test_requiring_network --- pandas-0.8.0/debian/patches/up_tag_yahoo_test_requiring_network 1969-12-31 19:00:00.0 -0500 +++ pandas-0.8.0/debian/patches/up_tag_yahoo_test_requiring_network 2012-07-13 08:57:31.0 -0400 @@ -0,0 +1,30 @@ +From: Wes McKinney wesmck...@gmail.com +Date: Thu, 12 Jul 2012 17:36:23 -0400 +Subject: [PATCH] BUG: fix duplicate index indexing problems close #1201 + +Partially taken from +4406d37b71cc3303b40847010299534c03723651 + +diff --git a/pandas/io/tests/test_yahoo.py b/pandas/io/tests/test_yahoo.py +index 9f123e0..1f10a86 100644 +--- a/pandas/io/tests/test_yahoo.py b/pandas/io/tests/test_yahoo.py +@@ -7,13 +7,15 @@ import re + import unittest + import pandas.io.data as pd + import nose ++from pandas.util.testing import network + + class TestYahoo(unittest.TestCase): + ++@network + def test_yahoo(self): +-asserts that yahoo is minimally working and that it throws +-an excecption when DataReader can't get a 200 response from +-yahoo ++# asserts that yahoo is minimally working and that it throws ++# an excecption when DataReader can't get a 200 response from ++# yahoo + start = datetime(2010,1,1) + end = datetime(2012,1,24) + self.assertEquals( -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental'), (100, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- 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/20120714013539.14909.50459.report...@novo.onerussian.com
would it be possible to reinstantiate openmeeg and ants in wheezy?
Hi Release Team, 2 packages of mine, primarily due to demanding resources for build (c++ with heavy use of templating) and testing (I do prefer to do build-time testing and they use realistic data) always were somewhat problematic to be built across architectures; thus they were removed from wheezy (while in testing) whenever new FTBFS were detected. Both are highly specialized to the field of neuroimaging. Both are old versions (see below) but relatively popular as for a specialized software. ants Slightly updated snapshot version than then one in squeeze Fresh upstream version requires fresh ITK (in experimental) popcon ~100 FTBFS atm on mips, mipsel, s390 imho due to insufficient resources and might be tricky to make them build reliably openmeeg The same upstream version as in squeeze -- minor additional patching (gcc 4.7) + enabled build time unittests Fresh upstream requires fresh libmat (in experimental) popcon ~200 FTBFS atm on mips only, and could be resolved simply through disabling build time unittesting I wondered, than even if I manage to overcome FTBFS on those -- would they be allowed to come back to wheezy? Thanks in advance -- Yaroslav O. Halchenko Postdoctoral Fellow, Department of Psychological and Brain Sciences Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- 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/20120705160939.gf5...@onerussian.com
Bug#680091: RM: nuitka/0.3.22.1+ds-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm Nuitka is a new and actively developed project. But it is not yet a good fit for a stable Debian release because of its yet experimental and evolving nature. So please remove it from wheezy. Thanks in advance -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental'), (100, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- 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/20120703135310.11759.73034.report...@novo.onerussian.com
Bug#680006: nmu: openmeeg_2.0.0.dfsg-5
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu gb openmeeg_2.0.0.dfsg-5 . mips there were also FTBFS on powerpc and kfreebsd-i386 with various obscure signs -- they all completed just fine now. So to not waste admin's time (and mine) in setting up the build env, it would be great if we could try another build run before getting hands dirty. it builds otherwise across all ports -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental'), (100, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- 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/20120702215259.18007.65427.report...@novo.onerussian.com
Bug#675976: transition: libguac
Adam D. Barratt a...@adam-barratt.org.uk wrote: On Mon, 2012-06-04 at 14:04 -0400, Yaroslav Halchenko wrote: On Mon, 04 Jun 2012, Niels Thykier wrote: package and thus in NEW queue atm. All dependees will be built/uploaded whenever libguac gets into sid and gets built across platforms: [...] Tracker is at [3]. Just to be on the same page, I read built/uploaded as you were going to upload a new version. This is perfectly fine if you do so, I just need to know what packages (if any) that needs binNMUs. Since they depend on current version of libguac (which is in NEW) -- imho there is no reason to upload new versions until libguac becomes part of sid. And then I guess there would be no need for binNMUs (i.e. less work for you ;-) ) libguac 0.6.0-1 has been in unstable since Monday evening. Will the r-deps be uploaded soon? Regards, Adam Yes They are built and are going through the review for sponsorship in spare time -- Sent from a phone which beats iPhone. -- 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/5d52b789-66ac-4da3-8432-57e457e73...@email.android.com
Bug#675968: transition: biosig4c++
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Please pardon me for apparently missing an important advisory for not using experimental first... Transition is tiny -- just 2 dependent packages on libbiosig-dev packages (below). Transition bug against biosig4c++ source is #675967. Outstanding FTBFS on ia64 was fixed (closed now) and I expect it to build fine on sparc (which would resolve #633346) The following source packages need to be rebuilt: sigviewer # this one might need a compatibility patch -- although seems to build nicely without openwalnut In terms of 'ben' lingo, my non-experienced guestimate that the transition should have the following parameters: Affected: .build-depends ~ /libbiosig-dev/ Good: .depends ~ /lbbiosig1/ Bad: .depends ~ /lbbiosig0/ What should be my course of action -- should I just close a transition bug (#675967) whenever transition slot is allocated? -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental'), (100, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- 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/20120604160306.12869.93434.report...@novo.onerussian.com
Bug#675968: transition: biosig4c++
Thank you Niels, On Mon, 04 Jun 2012, Niels Thykier wrote: I am not entirely sure if this was implied or not in your sentence, but we would prefer getting a transition bug before the package is uploaded to sid. yes -- that is what I meant (I have sinned twice btw -- just yesterday uploaded fresh libguac -- it is in NEW -- will report transition bug again). but for upcoming upload of libcomedi will report first (may be today) Transition is tiny -- just 2 dependent packages on libbiosig-dev packages (below). Transition bug against biosig4c++ source is #675967. The bts is acting up a bit, so I cannot actually read the contents of #675967 right now. Anyhow, it appears to be RC, which will stall the transition so please close it or downgrade it. For the purpose of tracking the transition, this bug is sufficient. that was a fresh bugreport which I filed to prevent biosig4c++ to migrate to wheezy before all depends are fine (i.e. trying to do transition manually). I guess I mixed up the meaning of 'transition bug' and #675967 wasn't really necessary -- closing with this email. Outstanding FTBFS on ia64 was fixed (closed now) and I expect it to build fine on sparc (which would resolve #633346). Thanks for solving the ia64 issue so quickly - I see biosig4c++ has already been rebuilt on all architectures (except sparc and armhf). I doubt armhf will cause any issues (given armel succeeded and that armhf succeesfully built 1.3.0-1). As biosig4c++ has not been built on sparc previously, it is less of a concern for the transition. But it is nice to see another bug fixed. :) ;-) thanks for thanks. I have built 1.3.0-1 on a local sparc box without problem -- that is why I am somewhat positive about positive outcome on buildd ;) We already scheduled the binNMUs for these earlier today and indeed sigviewer appears to be doing fine (still waiting for mipsel and armhf though). openwalut is still building, but I hope it will be as painless as you expect. actually openwalnut I haven't tested yet locally so there might be surprises. In terms of 'ben' lingo, my non-experienced guestimate that the transition should have the following parameters: Affected: .build-depends ~ /libbiosig-dev/ Good: .depends ~ /lbbiosig1/ Bad: .depends ~ /lbbiosig0/ There is a tracker at [1]. It uses a slightly different affected line as I wrote the ben file before you reported this bug, but yours would have been just as good (modulo the lbbiosig typo?). You can ignore d'oh -- I keep saying myself to cut/paste but keep typing ... sorry about that -- Yaroslav O. Halchenko Postdoctoral Fellow, Department of Psychological and Brain Sciences Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- 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/20120604171151.gp15...@onerussian.com
Bug#675976: transition: libguac
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Actually all dependent packages are part of the same 'guacamole' project and there is no 3rd party dependees (yet). libguac 0.6.0-1 provides libguac3 binary package and thus in NEW queue atm. All dependees will be built/uploaded whenever libguac gets into sid and gets built across platforms: libguac-client-vnc guacd Affected: .build-depends ~ /libguac-dev/ Good: .depends ~ /libguac3/ Bad: .depends ~ /libguac2/ -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental'), (100, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- 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/20120604171737.19505.20530.report...@novo.onerussian.com
Bug#675968: transition: biosig4c++
On Mon, 04 Jun 2012, Yaroslav Halchenko wrote: uploaded fresh libguac -- it is in NEW -- will report transition bug again). but for upcoming upload of libcomedi will report first (may be today) doh -- there is no need for transition with libcomedi seems to me -- just incremental change in API and soversion remains the same... in the worst may be a round of binNMUs would be needed for ABI compatibility but ignorant me can't tell if that would be needed for sure. -- Yaroslav O. Halchenko Postdoctoral Fellow, Department of Psychological and Brain Sciences Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- 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/20120604172357.gb8...@onerussian.com
Bug#675976: transition: libguac
On Mon, 04 Jun 2012, Niels Thykier wrote: I am CC'ing Michael Jumper (maintainer of libguac). I thought I have added him into CC while reporting the bug... or I thought I did ;) thanks for the CC In the given case, I see Michael is the maintainer of all involved packages, which is half the reason why I am okay with starting the transition[2]. yes -- I am just a mentor/sponsor package and thus in NEW queue atm. All dependees will be built/uploaded whenever libguac gets into sid and gets built across platforms: libguac-client-vnc guacd Tracker is at [3]. Just to be on the same page, I read built/uploaded as you were going to upload a new version. This is perfectly fine if you do so, I just need to know what packages (if any) that needs binNMUs. Since they depend on current version of libguac (which is in NEW) -- imho there is no reason to upload new versions until libguac becomes part of sid. And then I guess there would be no need for binNMUs (i.e. less work for you ;-) ) -- Yaroslav O. Halchenko Postdoctoral Fellow, Department of Psychological and Brain Sciences Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- 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/20120604180414.gq15...@onerussian.com
Bug#675968: transition: biosig4c++
On Mon, 04 Jun 2012, Julien Cristau wrote: again). but for upcoming upload of libcomedi will report first (may be today) doh -- there is no need for transition with libcomedi seems to me -- just incremental change in API and soversion remains the same... in the worst may be a round of binNMUs would be needed for ABI compatibility but ignorant me can't tell if that would be needed for sure. And yet you maintain shared libraries? Sigh. yes -- trying to... someone has to... package is on mentors [1] -- if you would like to give more experienced view and mentor/sponsor it instead of me -- you are more than welcome! [1] http://mentors.debian.net/package/comedilib -- Yaroslav O. Halchenko Postdoctoral Fellow, Department of Psychological and Brain Sciences Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- 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/20120604182712.gt15...@onerussian.com
Bug#670114: nmu: shogun_1.1.0-4
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu shogun_1.1.0-4 . ALL . -m Binary rebuild against numpy 1.6.1 in sid -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental'), (100, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- 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/20120423015634.19416.73192.report...@novo.onerussian.com
Re: please review/accept patch against fail2ban 0.8.4-3 in stable
ah -- sorry, went off my radar... IIRC there were no additional changes necessary, right? Meanwhile -- I will build the package on stable and upload it. On Fri, 06 Apr 2012, Adam D. Barratt wrote: On Sat, 2012-02-18 at 16:10 +, Adam D. Barratt wrote: On Thu, 2012-02-16 at 10:36 -0500, Yaroslav Halchenko wrote: full patch attached -- I just want to hear your feedback first and then will do additional testing to assure correct behavior on a stable system Well, even lenny has python as 2.5, so the double try shouldn't really be necessary. Other than that, please go ahead; thanks. Any news on that? Regards, Adam -- =--= Keep in touch www.onerussian.com Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic -- 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/20120406211332.go22...@onerussian.com
Bug#667579: nmu: numexpr_2.0.1-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu gb numexpr_2.0.1-2 . sparc . -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental'), (100, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- 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/20120405014752.21731.28489.report...@novo.onerussian.com
Re: Plans for ITK version 4
BTW -- just to keep itk4 packaging going forward: tried to build it on sid, seems to build (32bit tools on 64bit kernel) but some tests fail/segfault: The following tests FAILED: 589 - itkFFTWF_FFTTest (SEGFAULT) 590 - itkFFTWF_RealFFTTest (SEGFAULT) 591 - itkVnlFFTWF_FFTTest (SEGFAULT) 592 - itkVnlFFTWF_RealFFTTest (SEGFAULT) 595 - itkVnlFFTWD_FFTTest (SEGFAULT) 596 - itkVnlFFTWD_RealFFTTest (SEGFAULT) 1300 - itkVectorThresholdSegmentationLevelSetImageFilterTest (Failed) 1327 - itkLevelSetsv4DenseImageBaseTest (Failed) 1647 - itkSimpleImageRegistrationTest (Failed) 1972 - itkOtsuThresholdImageFilterTestShort (Failed) 2142 - DigitallyReconstructedRadiograph1Test (Failed) Errors while running CTest make[2]: *** [test] Error 8 make[2]: Leaving directory `/tmp/buildd/insighttoolkit4-4.0.0/BUILD' is that something known? NB that sid environment might be a bit outdated though... On Sat, 28 Jan 2012, Steve M. Robbins wrote: On Sat, Jan 28, 2012 at 01:25:46PM -0500, Dominique Belhachemi wrote: On Sat, Jan 28, 2012 at 4:43 AM, Steve M. Robbins st...@sumost.ca wrote: On Tue, Jan 24, 2012 at 08:38:44AM -0500, Dominique Belhachemi wrote: Steve, Thanks for all the work. It would be good to have ITK4 in 'experimental'. Having coexisting packages is nice to have but will cause probably too much trouble (especially if we build all the language wrappers again) Since it's released, I was planning to upload straight to 'unstable'. Do you think there's a need to stage in 'experimental' first? I think it is better to have ITK4 in experimental for one or two weeks. This is just to be on the safe side, there are sometimes unexpected problems with including cmake configuration files. I fully expect a number of problems with configuration. However, I see no problem with working this out in unstable rather than experimental. The new packages do not replace any existing ones and nothing will build-depend on the new packages at first. Can you explain what issue you see with working this out in unstable? Thanks, -Steve -- =--= Keep in touch www.onerussian.com Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic -- 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/20120302144750.ga14...@onerussian.com
Re: please review/accept patch against fail2ban 0.8.4-3 in stable
full patch attached -- I just want to hear your feedback first and then will do additional testing to assure correct behavior on a stable system Well, even lenny has python as 2.5, so the double try shouldn't really be necessary. Other than that, please go ahead; thanks. it just was taken from upstream commit and upstream is still 2.4 compatible -- I saw no reason to tune it up Major change is to deal with grave: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650678 which prevented use of fail2ban with multiple jails enabled. It has been in unstable and testing for a while and I have not heard about any negative feedback #554162 was a more useful reference there, imho. (quilt)) suggested NMU http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635746 Likewise #544232, as the newer bug is purely about the suggested NMU, not what the actual problem was. so -- in general -- should I list all of them as well (even those closed and archived in sid)? ignorantly I thought that it should be still open squeeze-tagged bug reports... -- =--= Keep in touch www.onerussian.com Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic -- 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/20120218184423.gs16...@onerussian.com
please review/accept patch against fail2ban 0.8.4-3 in stable
full patch attached -- I just want to hear your feedback first and then will do additional testing to assure correct behavior on a stable system Major change is to deal with grave: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650678 which prevented use of fail2ban with multiple jails enabled. It has been in unstable and testing for a while and I have not heard about any negative feedback Also it incorporates (sorry -- that version of f2b didn't use yet 3.0 (quilt)) suggested NMU http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635746 about insecure temporary files creation. -- =--= Keep in touch www.onerussian.com Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic diff --git a/config/action.d/dshield.conf b/config/action.d/dshield.conf index b80698b..8549a55 100644 --- a/config/action.d/dshield.conf +++ b/config/action.d/dshield.conf @@ -206,5 +206,5 @@ dest = repo...@dshield.org # Notes.: Base name of temporary files used for buffering # Values: [ STRING ] Default: /tmp/fail2ban-dshield # -tmpfile = /tmp/fail2ban-dshield +tmpfile = /var/run/fail2ban/tmp-dshield diff --git a/config/action.d/mail-buffered.conf b/config/action.d/mail-buffered.conf index 04788ab..b2255a1 100644 --- a/config/action.d/mail-buffered.conf +++ b/config/action.d/mail-buffered.conf @@ -81,7 +81,7 @@ lines = 5 # Default temporary file # -tmpfile = /tmp/fail2ban-mail.txt +tmpfile = /var/run/fail2ban/tmp-mail.txt # Destination/Addressee of the mail # diff --git a/config/action.d/mynetwatchman.conf b/config/action.d/mynetwatchman.conf index 15b91b1..f0e5515 100644 --- a/config/action.d/mynetwatchman.conf +++ b/config/action.d/mynetwatchman.conf @@ -141,4 +141,4 @@ mnwurl = http://mynetwatchman.com/insertwebreport.asp # Notes.: Base name of temporary files # Values: [ STRING ] Default: /tmp/fail2ban-mynetwatchman # -tmpfile = /tmp/fail2ban-mynetwatchman +tmpfile = /var/run/fail2ban/tmp-mynetwatchman diff --git a/config/action.d/sendmail-buffered.conf b/config/action.d/sendmail-buffered.conf index 90a482d..ad78b57 100644 --- a/config/action.d/sendmail-buffered.conf +++ b/config/action.d/sendmail-buffered.conf @@ -101,5 +101,5 @@ lines = 5 # Default temporary file # -tmpfile = /tmp/fail2ban-mail.txt +tmpfile = /var/run/fail2ban/tmp-mail.txt diff --git a/debian/changelog b/debian/changelog index 7ccb6e6..0e70377 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,15 @@ +fail2ban (0.8.4-3+squeeze1) stable; urgency=low + + [ Jonathan Wiltshire ] + * [e2232fc] Backport patch to fix CVE-2009-5023: Insecure creation of +tempfile (Closes: #544232, #635746) + + [ Yaroslav Halchenko ] + * [6fc6c7b] Backport patch: Lock server's executeCmd to prevent racing +among iptables calls (Closes: #650678) + + -- Yaroslav Halchenko deb...@onerussian.com Thu, 16 Feb 2012 10:29:08 -0500 + fail2ban (0.8.4-3) unstable; urgency=low * Commenting out named-refused-udp jail and providing even fatter diff --git a/server/action.py b/server/action.py index 70f4c37..ea79dd8 100644 --- a/server/action.py +++ b/server/action.py @@ -25,11 +25,15 @@ __copyright__ = Copyright (c) 2004 Cyril Jaquier __license__ = GPL import logging, os +import threading #from subprocess import call # Gets the instance of the logger. logSys = logging.getLogger(fail2ban.actions.action) +# Create a lock for running system commands +_cmd_lock = threading.Lock() + ## # Execute commands. # @@ -301,17 +305,21 @@ class Action: #@staticmethod def executeCmd(realCmd): logSys.debug(realCmd) - try: - # The following line gives deadlock with multiple jails - #retcode = call(realCmd, shell=True) - retcode = os.system(realCmd) - if retcode == 0: -logSys.debug(%s returned successfully % realCmd) -return True - else: -logSys.error(%s returned %x % (realCmd, retcode)) - except OSError, e: - logSys.error(%s failed with %s % (realCmd, e)) + _cmd_lock.acquire() + try: # Try wrapped within another try needed for python version 2.5 + try: +# The following line gives deadlock with multiple jails +#retcode = call(realCmd, shell=True) +retcode = os.system(realCmd) +if retcode == 0: + logSys.debug(%s returned successfully % realCmd) + return True +else: + logSys.error(%s returned %x % (realCmd, retcode)) + except OSError, e: +logSys.error(%s failed with %s % (realCmd, e)) + finally: + _cmd_lock.release() return False executeCmd = staticmethod(executeCmd) signature.asc Description: Digital signature
Re: please review/accept patch against fail2ban 0.8.4-3 in stable
Major change is to deal with grave: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650678 which prevented use of fail2ban with multiple jails enabled. It has been in unstable and testing for a while and I have not heard about any negative feedback Also it incorporates (sorry -- that version of f2b didn't use yet 3.0 (quilt)) suggested NMU http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635746 about insecure temporary files creation. from the BTS version graph: please fix it in unstable first. I have marked 635746 as fixed in 0.8.4+svn20110323-1 and tagged with squeeze I have marked 650678 as fixed in 0.8.5-2 is that what was necessary? -- =--= Keep in touch www.onerussian.com Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic -- 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/20120216184246.gg16...@onerussian.com
Re: please review/accept patch against fail2ban 0.8.4-3 in stable
Yaroslav Halchenko y...@debian.org (16/02/2012): I have marked 635746 as fixed in 0.8.4+svn20110323-1 and tagged with squeeze This is a bit confusing. From the version graph, squeeze is still unaffected? probably because original report was missing version, so did now bts found 635746 0.8.4-3 would it be of help? is that what was necessary? Clarifying that stable is affected and sid/testing has a (possibly harmless) fix is what we like. Helps us make sure the fix does not harm. thanks for the explanation -- I just wondered if the step I have done were the ones you were wanting me to do ;) -- =--= Keep in touch www.onerussian.com Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic -- 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/20120216232124.gr16...@onerussian.com
Re: tentative upload to stable-proposed-updates [cython]
Hi Team, I have got swamped a bit with RL and other duties... if anyone could take care about preparing this bugfix upload into squeeze -- would be awesome! (more communication is available on bugs.debian.org/641128) Cheers! Mon, 31 Oct 2011, Kirill Smelkov wrote: Hello up there, On Sun, Sep 18, 2011 at 04:55:36PM +0100, Adam D. Barratt wrote: On Sat, 2011-09-17 at 22:21 -0400, Yaroslav Halchenko wrote: I wonder would an upload to s-p-u be ok to fix a regression in cython package, which is apparently of importance for some users (who even triaged repository to the specific commit resolving the issue). Patch (see commit below) will be trivial. Thanks for working on this. As far as I can see from the log in #641128, this issue is not yet resolved in unstable? If that's correct, then while I'd be likely to accept a stable update fixing the issue, it should be handled in unstable first. Once that's happened and there's been no obvious regressions then we can look at updating stable. Regards, Adam I wonder, is there any chance to get this trivial fix for Squeeze regression into Squeeze actually? Thanks, Kirill -- =--= Keep in touch www.onerussian.com Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic -- 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/20111207234647.gd2...@onerussian.com
tentative upload to stable-proposed-updates [cython]
Dear Release team, I wonder would an upload to s-p-u be ok to fix a regression in cython package, which is apparently of importance for some users (who even triaged repository to the specific commit resolving the issue). Patch (see commit below) will be trivial. Please let us know so we could prepare the upload. Best, Yarik On Fri, 16 Sep 2011, Kirill Smelkov wrote: wow -- thanks Kirill for the details! I think within few days we will get 0.15 (or post 0.15 snapshot unless 0.15.1 gets released) into Debian which should close this issue Thanks. It's good that 0.15.* will hopefully make it into Sid soon, but I'd like to clarify that my point here is that we should apply the fix for the regression to Squeeze as well. Thanks again, Kirill On Tue, 13 Sep 2011, Kirill Smelkov wrote: and fixed in 0.14.1-111-g78e134e (unfortunately without tests): commit 78e134ede7646bacfaaafb71172fd4f86b890d0f Author: Robert Bradshaw rober...@math.washington.edu Date: Thu Mar 3 11:07:23 2011 -0800 Fix compile time division. diff --git a/Cython/Compiler/ExprNodes.py b/Cython/Compiler/ExprNodes.py index c965251..1fe8538 100755 --- a/Cython/Compiler/ExprNodes.py +++ b/Cython/Compiler/ExprNodes.py @@ -5992,7 +5992,7 @@ class DivNode(NumBinopNode): operand2 = self.operand2.compile_time_value(denv) try: func = self.find_compile_time_binary_operator( -self, operand1, operand2) +operand1, operand2) return func(operand1, operand2) except Exception, e: self.compile_time_value_error(e) which I think should be backported to Debian Cython packages. -- =--= Keep in touch www.onerussian.com Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic signature.asc Description: Digital signature
Bug#625644: transition: python-numpy
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Please hint python-numpy 1:1.5.1-2+b1 and python-pebl 1.0.2-2 to enter testing. http://release.debian.org/migration/testing.pl?package=python-pebl binary package python-pebl is part of source package pebl trying to update pebl from 1.0.2-1 to 1.0.2-2 (candidate is 5 days old) pebl is waiting for python-numpy Updating python-numpy makes 2 depending packages uninstallable on amd64: python-pebl, python-pebl-dbg Updating pebl makes 2 non-depending packages uninstallable on i386: python-pebl, python-pebl-dbg trying to update python-numpy from 1:1.5.1-2 to 1:1.5.1-2+b1 Updating python-numpy makes 2 depending packages uninstallable on amd64: python-pebl, python-pebl-dbg -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental'), (100, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- 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/20110504193157.6210.58268.report...@novo.onerussian.com
Bug#616364: Bug#611316: Bug#616364: transition: python-numpy
On Mon, 04 Apr 2011, Sandro Tosi wrote: 616702 was cleared last night. What's the status of the other two? 611316: if it holds the transition, we can remove it from testing until fixed (76 days RC bug, 58 popcon), but in any case: Yaroslav, any news on that? I believe that fresh upstream snapshot (which took nibabel out and we have nibabel in wheezy already) should resolve the issue -- I will check it out later on this week. Feel free to remove from testing if it starts to hold the transition -- =--= Keep in touch www.onerussian.com Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic -- 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/20110404133451.gz6...@onerussian.com
Bug#616364: transition: python-numpy
On Thu, 03 Mar 2011, Jakub Wilk wrote: Jakub kindly rebuilt these packages, successfully: brian h5py libvigraimpex magics++ mayavi2 nipy petsc4py plplot pygtk pytables python-scipy scikit-learn shogun . All of these (maybe except scikit-learn) will need binNMUs. I can schedule them myself if that's OK for you. it is ok with me for brian nipy scikit-learn currently FTBFS with python-sphinx = 1.0 (bug #588630, already fixed in experimental). I CCed this mail to scikit-learn maintainers. thanks -- very soon fresh upstream version of scikit-learn will come out which will go into unstable directly, so FTBFS of current sid version will not last too long ;) (or I could upload experimental version into sid if upstream release gets delayed) cheers -- =--= Keep in touch www.onerussian.com Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic -- 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/20110303205634.gs29...@onerussian.com
Bug#598651: unblock: ants/1.9+svn532-5
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Please unblock package ants 1.9+svn532-4 [ Tue, 06 Jul 2010 ] was meant for squeeze (fixed #588195), but did not propagate into squeeze since testing of the built version was timing out on some (e.g. mipsel) architectures. I have uploaded 1.9+svn532-5 which disabled some lengthy tests (and included BSD-3 license to be compliant with 3.9.1), but that was not yet sufficient, so few architectures got manually rebuilt on debian machines with disabled tests (got +b1 suffix for) for armel and mips. Now all architectures are covered and -5 ready for transition into squeeze. unblock ants/1.9+svn532-5 -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (901, 'unstable'), (900, 'testing'), (300, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- 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/20100930190225.25475.67656.report...@novo.onerussian.com
Bug#594151: unblock: nipype/0.3.2-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Please unblock package nipype 0.3 release (present in squeeze atm) was the first release in 0.3 series and upstream followed it up shortly with two bugfix releases: Release 0.3.1 (Jul 29, 2010) Release 0.3.2 (Aug 03, 2010) which fixed some bugs and introduced some additional documentation. Due to participation in debconf10 I had to postpone packaging those and only accomplished the mission with 0.3.2-1 package on 9th of August, and that package is now ready for transition from unstable into testing. I am sorry that I have not preliminary confirmed that the package would be granted freeze exception for sure -- I have just relied on a common sense of our common goal to get good stable versions into the squeeze, and bugfix version 0.3.2 imho is much better candidate, please let it transition. unblock nipype/0.3.2-1 -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (901, 'unstable'), (900, 'testing'), (300, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- 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/20100824033846.2129.91223.report...@novo.onerussian.com
Bug#594152: unblock: psychopy/1.61.03.dfsg-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Please unblock package psychopy 1.61.03 is a bugfix release on top of upstream 1.61.02. 1.61.02.dfsg-2 (present in squeeze atm) already contained major fixes from 1.61.03, and 1.61.03 upstrem release which officially includes them + finally removed upstream non-DFSG video with DFSG version of the video improved for better user experience + documentation improvements + 1 new minor feature in configuration UI This is the last version in 1.6x development cycle and 1.62.00.dfsg-1 is already in Experimental. unblock psychopy/1.61.03.dfsg-1 -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (901, 'unstable'), (900, 'testing'), (300, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- 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/20100824034551.3554.72552.report...@novo.onerussian.com
Re: Processed: severity of 581204 is serious, block 574770 with 581204
# as per squeeze RC policy, point 4: severity 581204 serious evil you! ;) Please contact me if you need assistance. doing so: This bug has NOTHING to do with the transition -- the bug would be as good or as bad with python-default being 2.6. May be even it would disappear if 2.6 is the default, we don't know! So why is it a blocker for the transition? NB I see it indeed as a blocker for a release, but for the transition blockers should be the ones which are ok with 2.5 but fail with 2.6, so please do not overdo, and remove it from the blockers for the transition. On Tue, 11 May 2010, Debian Bug Tracking System wrote: Processing commands for cont...@bugs.debian.org: # as per squeeze RC policy, point 4: severity 581204 serious Bug #581204 [python-nipy] python-nipy: FTBFS on hppa due to undefined symbol: __canonicalize_funcptr_for_compare while sphinxing Severity set to 'serious' from 'important' block 574770 with 581204 Bug #574770 [release.debian.org] transition: python-defaults (2.6) Was blocked by: 558996 573161 578785 576225 576210 574730 518049 558983 524746 574741 534848 577061 534068 565665 529478 570580 577388 580678 581008 577898 Added blocking bug(s) of 574770: 581204 thanks Stopping processing here. -- .-. =-- /v\ = Keep in touch// \\ (yoh@|www.)onerussian.com Yaroslav Halchenko /( )\ ICQ#: 60653192 Linux User^^-^^[17] signature.asc Description: Digital signature
Re: Processed: severity of 581204 is serious, block 574770 with 581204
On Tue, 11 May 2010, Jakub Wilk wrote: This bug has NOTHING to do with the transition -- the bug would be as good or as bad with python-default being 2.6. May be even it would disappear if 2.6 is the default, we don't know! Well, maybe. But I bet I will FTBFS with Python 2.6 as well. I would probably bet too that it would ;) but once again, we don't know, and have no easy way to check atm (I doubt that I could request a chroot on hppa with python 2.6 as default...) So why is it a blocker for the transition? Because it will need a binNMU after new python-defaults is uploaded. python-nipy-lib currently depends on python ( 2.6) so it couldn't live with new python in testing. ah, ok -- wonders of broken (apparently by design) cdbs [1] [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=577580 but I see it now, indeed... ok -- I guess I should finally migrate to dh, and set separate build-indep and build-arch targets, so there is no FTBFS from building a documentation... everyone needs to pay for his laziness ;) NB I see it indeed as a blocker for a release, but for the transition blockers should be the ones which are ok with 2.5 but fail with 2.6, Well, that's exactly the case. ok ok -- indeed version which already managed to get in, probably is ok... will check just for fun -- .-. =-- /v\ = Keep in touch// \\ (yoh@|www.)onerussian.com Yaroslav Halchenko /( )\ ICQ#: 60653192 Linux User^^-^^[17] -- 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/20100511181249.gc20...@onerussian.com
please binNMU nipy to build for 2.6 as well
Hello, binNMU of nipy is necessary so python-nipy-lib* build compiled modules for supported python2.6. nmu nipy_0.1.2+1741-2.2 . ALL . -m 'Build extensions for 2.6.' Thanks! -- .-. =-- /v\ = Keep in touch// \\ (yoh@|www.)onerussian.com Yaroslav Halchenko /( )\ ICQ#: 60653192 Linux User^^-^^[17] -- 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/20100327150627.gk1...@onerussian.com
please binNMU pynifti to build extensions for 2.6 and drop for 2.4
Hello, binNMU of pynifti is needed to address FTBFS #571499 of nipy (emulating situation whenever python2.6 is the default, which isn't yet the case, so it could be closed with a simple binNMU of pynifti) nmu pynifti_0.20090303.1-1 . ALL . -m 'Build extensions for 2.6 and drop for 2.4.' Thanks! -- .-. =-- /v\ = Keep in touch// \\ (yoh@|www.)onerussian.com Yaroslav Halchenko /( )\ ICQ#: 60653192 Linux User^^-^^[17] signature.asc Description: Digital signature
RM: mozilla-firefox-adblock/testing -- ROM; was already removed from sid - but still present in testing (squeeze)
subj -- .-. =-- /v\ = Keep in touch// \\ (yoh@|www.)onerussian.com Yaroslav Halchenko /( )\ ICQ#: 60653192 Linux User^^-^^[17] signature.asc Description: Digital signature
Re: fail2ban uploaded into sid fixing security issue
Quoting IRC for the benefit of other release people: 18:21 dato yoh: please prepare and update for lenny 18:21 yoh damn... I just sent out email to debian-release mailing list ;) 18:21 yoh right after I hit 'Send' I've heard 'beep' from IRC ;-) unblocked pardon my ignorance -- does it mean that I don't have to prepare separate package for lenny now and current version would propagate from sid? (Unfortunately there is no 10 days available to wait prior scheduled release, damn me I forgotten proper urgency in changelog for sid version, hence shouldn't it be pushed into lenny manually?) -- .-. =-- /v\ = Keep in touch// \\ (yoh@|www.)onerussian.com Yaroslav Halchenko /( )\ ICQ#: 60653192 Linux User^^-^^[17] -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
fail2ban uploaded into sid fixing security issue
Dear Release Team, Yesterday fresh bug report [1] spoiled my day. It concerns with ability to run DoS on a victim through injection of victim's IP into domain name... I've uploaded fixed versions both into sid and experimental with version in sid: fail2ban (0.8.3-2sid1) unstable; urgency=low * BF: anchoring regex for IP with *$ at the end + adjust regexp for HOST (closes: #514163) * NF: adding unittests for previous commit Unfortunately sid's version was already 1 debian revision ahead of lenny's, but that revision is also a bug fix although not-security related: fail2ban (0.8.3-2) unstable; urgency=low * BF in apache-noscript.conf - regexp matched in referer (Closes: #492319). Thanks Bernd Zeimetz. * BF: extended apache-noscript with additional regexp -- Yaroslav Halchenko deb...@onerussian.com Fri, 25 Jul 2008 13:33:56 -0400 As you can see change in -2 has been in sid for half-year without additional bug reports about introduced changes. I wonder if it would be possible to push (0.8.3-2sid1) version into lenny or should I prep yet another version ((0.8.3-1lenny1) with only security-related change in it? P.S. t...@security was already contacted with necessary diff against etch (stable-security). [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=514163 -- Yaroslav Halchenko Research Assistant, Psychology Department, Rutgers-Newark Student Ph.D. @ CS Dept. NJIT Office: (973) 353-1412 | FWD: 82823 | Fax: (973) 353-1171 101 Warren Str, Smith Hall, Rm 4-105, Newark NJ 07102 WWW: http://www.linkedin.com/in/yarik -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
unfreeze jsmath [i10n]
Please let 3.4f-2 enter lenny from sid. changes from -1 were: +jsmath (3.4f-2) unstable; urgency=low + + * [INTL:sv] Swedish strings for jsmath debconf (Closes: #504249) +(Thanks Martin Bagge) + * All .po files were updated by the recent debconf-updatepo (1.0.15) + + -- Yaroslav Halchenko deb...@onerussian.com Fri, 12 Dec 2008 23:21:29 -0500 -- Yaroslav Halchenko Research Assistant, Psychology Department, Rutgers-Newark Student Ph.D. @ CS Dept. NJIT Office: (973) 353-1412 | FWD: 82823 | Fax: (973) 353-1171 101 Warren Str, Smith Hall, Rm 4-105, Newark NJ 07102 WWW: http://www.linkedin.com/in/yarik -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
impressive (former keyjnote) is unblocking possible?
Hi Release Team, Due to trademark violation, keyjnote was removed from lenny a bit more than a week ago. Meanwhile I have uploaded the same version of a new brand of the project: impressive. It has been in unstable for 13 days, functionally it is 100% equivalent to the last release of keyjnote which was in lenny prior removal. I have done only minor changes to packaging (listed below) to make it even better ;-) (Thanks to Thomas Viehmann for helping to expedite impressive through NEW queue) I wonder if there is a way to get impressive into lenny or at least into lenny-proposed-updates? Since the main goal of Debian project is to ship as many useful and popular packages as possible, it would be great to see impressive there. According to popcon there are 150 installation of impressive, whenever total number of keyjnote installations was around 270. And there are no new bugreports -- imho it says that package is in a good shape ;) So, changes from the last release (same version) of keyjnote: impressive (0.10.2r-2) unstable; urgency=low * Resolving problems which forbid impressive to pass through NEW: - fixing debian/copyright to match upstream: GPLv2 firm - adding the source for the demo.pdf - added missing copyright holders into debian/copyright - building demo.pdf from the shipped with debian .tex source -- Yaroslav Halchenko deb...@onerussian.com Fri, 05 Dec 2008 12:57:16 -0500 impressive (0.10.2r-1) unstable; urgency=low * New Upstream Version (version suffix 'r' stands for 'r'enamed to provide proper Replaces): - Project was renamed to impressive - Manpage is shipped by the upstream (closes: #482581) * Migrated VCS for the packaging into git, added Vcs fields to debian/control. * Boosted policy to 3.8.0 (no changes needed) * Removed obsolete manpage since upstream ships manpage now * Changed gs - ghostscript-x in Recommends * Created transitional package keyjnote -- Yaroslav Halchenko deb...@onerussian.com Sun, 23 Nov 2008 19:50:31 -0500 -- Yaroslav Halchenko Research Assistant, Psychology Department, Rutgers-Newark Student Ph.D. @ CS Dept. NJIT Office: (973) 353-1412 | FWD: 82823 | Fax: (973) 353-1171 101 Warren Str, Smith Hall, Rm 4-105, Newark NJ 07102 WWW: http://www.linkedin.com/in/yarik -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Bug#492837: remove mozilla-bookmarksftp from lenny
Indeed it is useless in lenny, thus should be removed from release for the sake of clarity, but I would drag it within sid -- may be some effort would appear to fix it up to be compatible with firefox 3.0, so we could patch it within Debian. Cheers Yarik On Sat, 11 Oct 2008, Thomas Viehmann wrote: Hi, according to the discussion in #492837, mozilla-bookmarksftp is completely unusable with the lenny's version of iceweasel and fixing will be finding a new upstream (because it's dead) and uploading that. That's too invasive at this point of the release cycle, so mozilla-bookmarksftp should be removed from lenny if not lenny and unstable. Kind regards T. -- Yaroslav Halchenko Research Assistant, Psychology Department, Rutgers-Newark Student Ph.D. @ CS Dept. NJIT Office: (973) 353-5440x263 | FWD: 82823 | Fax: (973) 353-1171 101 Warren Str, Smith Hall, Rm 4-105, Newark NJ 07102 WWW: http://www.linkedin.com/in/yarik signature.asc Description: Digital signature
Re: [Pkg-exppsy-maintainers] libode ABI breackage
Sorry for the delay -- pyode will be uploaded shortly -- I thought actually that I did already -- package was ready and just needs minor testing (but requires major update of the test box ;-)). Yes a rebuild is needed to link the package against the new libode0debian1. Is there a minimum number of packages involved to ask the release team for an autobuild binNUM ? -- Yaroslav Halchenko Research Assistant, Psychology Department, Rutgers-Newark Student Ph.D. @ CS Dept. NJIT Office: (973) 353-5440x263 | FWD: 82823 | Fax: (973) 353-1171 101 Warren Str, Smith Hall, Rm 4-105, Newark NJ 07102 WWW: http://www.linkedin.com/in/yarik pgpkDgiB2R42O.pgp Description: PGP signature
please unblock lush
Dear Release Team,
I want to present to your attention lush package which was recently orphaned
and which I decided to take care about in the future, thus I adopted it.
Current sid version (1.2.1-4) has fixed/closed 3 bugs total and I
consider 1 bug nonexistent since it builds now for ia64, so it can be closed.
Current etch version of lush (1.1-5) is quite useless due to #336570 -- 99% of
the lush users will have to get backports from sid, or at least rebuild it on a
system with necessary libraries. Thus I consider it important to have
working version shipped with etch. And the working version is 1.2.1-4 which is
now in sid and which is now 8 days old.
Here is a full list of changes I've done:
lush (1.2.1-4) unstable; urgency=low
* New maintainer. (Closes: #402989: ITA: lush -- Lisp Universal Shell
Executable - Debian Bug report logs)
* Moved copying of config.{sub,guess} under rule autotools, which has to be
manually invoked to provide deterministic update of those files and to
don't freak out svn-buildpackage. TODO: Need to clarify since that
statement was added by dh_make
* Tiny adjustment of debian/copyright file
* Added homepage to the description in debian/control
* Multiple changes within debian/rules
* Added proper Build-Depends, which includes libxt-dev and others necessary
to build lush so it could run demos (Closes: #336570)
* Added development packages for on-fly-compilation done by lush into
Recommends and Suggests, depending on how common they are. libcv-dev was
added to Suggests (Closes: #312081)
* Ship and properly enable lush.el along with lush-library package to
enable lush command within emacs
* Mentioned demos in README.Debian
* Adjusted paths in the manpage patch
* More things to do in future. But enough for current upload I hope
--
.-.
=-- /v\ =
Keep in touch// \\ (yoh@|www.)onerussian.com
Yaroslav Halchenko /( )\ ICQ#: 60653192
Linux User^^-^^[17]
pgpSouVVxipDM.pgp
Description: PGP signature
Re: please unblock imagezoom 0.2.7-5
Fresh bugs were fixed and current version was in unstable for 4 days already - so there is a big chance that now it will migrate into testing finally ;-) Could you please update unblock hint to be for 0.2.7-7 Thank you in advance Changelog entries since latest unblock request: imagezoom (0.2.7-7) unstable; urgency=low * Removed per application links to preferences file for iceweasel/firefox and icedove/thunderbird (Closes: #404611) -- Yaroslav Halchenko [EMAIL PROTECTED] Wed, 27 Dec 2006 23:00:21 -0500 imagezoom (0.2.7-6) unstable; urgency=low * There must be no files in /usr/lib/iceape/chrome: now link is created under /usr/share/iceape/chrome (Closes: #404300) -- Yaroslav Halchenko [EMAIL PROTECTED] Sat, 23 Dec 2006 23:29:08 -0500 On Sat, 16 Dec 2006, Marc 'HE' Brockschmidt wrote: Yaroslav Halchenko [EMAIL PROTECTED] writes: Sorry for the noise but unblocked 0.2.7-3 was missing proper links for iceape/icedove and missing call to update-iceape-chrome now everything is fixed and it must be ready for etch OK, I've updated my unblock hint. Marc -- .-. =-- /v\ = Keep in touch// \\ (yoh@|www.)onerussian.com Yaroslav Halchenko /( )\ ICQ#: 60653192 Linux User^^-^^[17] pgp1Ia7qZ68K7.pgp Description: PGP signature
Re: this bug is not severe! I would love to see keyjnote in etch - please unblock
On Tue, 19 Dec 2006, Luk Claes wrote: ... I'm afraid I don't see why we should unblock a package were noone took care of the RC bug in a for release point of view new package... Valid reasoning - abandoned package is not a good one for a stable distribution! The reason is probably that Florian god overwhelmed with other 100 packages to maintain and keyjnote is new in Debian so it didn't get its daily audience yet ;-) But I think it is a very nice project and it has been actively developed upstream, and it is stable in my experience, so many etch users might enjoy it a lot. Florian, do you need any help with this package? I would love to co-maintain it or just pick it up from your at this point. Luk, would my promise to help to maintain it help on its way to etch? :-) -- .-. =-- /v\ = Keep in touch// \\ (yoh@|www.)onerussian.com Yaroslav Halchenko /( )\ ICQ#: 60653192 Linux User^^-^^[17] pgpGS0zNarpdS.pgp Description: PGP signature
Re: this bug is not severe! I would love to see keyjnote in etch - please unblock
On Tue, 19 Dec 2006, Florian Ragwitz wrote: ... If you're going to maintain or co-maintain this package I'll be glad to sponsor it for you, though. Great! No sponsoring would be necessary though -- I am a freshly cooked DD ;-) I didn't have much experience in co-maintaining packages (besides pkg-exppsy project) but if you consider that it is worth to co-maintain, then it is ok. Otherwise I would not mind to adopt it from you so its packaging would take a place in my SVN repository for debian packages. It is your call, Florian. But before anything, I would like to hear the last decision from Luk on etch destiny of keyjnote, ie if he would allow this new to etch package to get included. Thanks everyone in advance -Flo -- .-. =-- /v\ = Keep in touch// \\ (yoh@|www.)onerussian.com Yaroslav Halchenko /( )\ ICQ#: 60653192 Linux User^^-^^[17] pgpZnKy6c4JBA.pgp Description: PGP signature
would it be allowed to have keyjnote in etch?
Dear Release Team I've CCed a follow up on the bug to the list but it seems to never arrive the destination - there is not sign of it in the archive. keyjnote is a relatively young package within Debian (initial release of Debian package is 11 Sep 2006) and it got stuck in unstable without ever seeing etch due to #389691 which was filed with grave severity, whenever it is actually normal at worst (or most probably it is not even a bug of keyjnote per se). I've lowered severity to normal now. This package is quite nice and everybody, whom I made aware of it, loved it. It worked fine for everyone whom I've refered to it. Is there a chance to allow it to propagate into etch or since it is new to it - it can't happen? Thank you in advance - Forwarded message from Yaroslav Halchenko [EMAIL PROTECTED] - Date: Fri, 15 Dec 2006 11:07:05 -0500 From: Yaroslav Halchenko [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED], debian-release@lists.debian.org Subject: this bug is not severe! I would love to see keyjnote in etch - please unblock severity 389691 normal thanks I am not sure why the maintainer didn't lower the severity -- this issues seems to be not even a keyjnote fault but SDL/ALSA configuration issue on the box of the submitter. So MOST of the people do not experience this bug, thus at most it must be of normal severity. This package has no other serious bug filed for a while (besides wishlist for me for new upstream version), so I would ask to remove the hold from this package so it gets into etch, and dear maintainer please do not upload fresh release into unstable so current version (if approved) penetrate into etch. -- .-. =-- /v\ = Keep in touch// \\ (yoh@|www.)onerussian.com Yaroslav Halchenko /( )\ ICQ#: 60653192 Linux User^^-^^[17] - End forwarded message - -- .-. =-- /v\ = Keep in touch// \\ (yoh@|www.)onerussian.com Yaroslav Halchenko /( )\ ICQ#: 60653192 Linux User^^-^^[17]
this bug is not severe! I would love to see keyjnote in etch - please unblock
severity 389691 normal thanks I am not sure why the maintainer didn't lower the severity -- this issues seems to be not even a keyjnote fault but SDL/ALSA configuration issue on the box of the submitter. So MOST of the people do not experience this bug, thus at most it must be of normal severity. This package has no other serious bug filed for a while (besides wishlist for me for new upstream version), so I would ask to remove the hold from this package so it gets into etch, and dear maintainer please do not upload fresh release into unstable so current version (if approved) penetrate into etch. -- .-. =-- /v\ = Keep in touch// \\ (yoh@|www.)onerussian.com Yaroslav Halchenko /( )\ ICQ#: 60653192 Linux User^^-^^[17] pgpRC3wzHTcwk.pgp Description: PGP signature
Re: please unblock imagezoom 0.2.7-5
Sorry for the noise but unblocked 0.2.7-3 was missing proper links for iceape/icedove and missing call to update-iceape-chrome now everything is fixed and it must be ready for etch Thank you in advance On Tue, 12 Dec 2006, Marc 'HE' Brockschmidt wrote: Yaroslav Halchenko [EMAIL PROTECTED] writes: 0.2.7-3 closes release relevant bug (400168) of migrating over to iceweasel. Depends were corrected to include iceweasel. Done. Marc -- .-. =-- /v\ = Keep in touch// \\ (yoh@|www.)onerussian.com Yaroslav Halchenko /( )\ ICQ#: 60653192 Linux User^^-^^[17] pgpdlNJVVqJrw.pgp Description: PGP signature
please unblock bookmarksftp 1.0.2-6
1.0.2-4 was ublocked since it was fixing RC bug. But apparently it was just a partial fix, 1.0.2-6 should be the one we need in etch ;-) Thank you in advance! -- .-. =-- /v\ = Keep in touch// \\ (yoh@|www.)onerussian.com Yaroslav Halchenko /( )\ ICQ#: 60653192 Linux User^^-^^[17] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
please ublock fail2ban
Dear Release Team, I didn't make it quite in time: testing has 0.7.4-3 whenever unstable 0.7.5-2 - ie 1 upstream release away. 0.7.5 upstream release is ia bugfix release though * closes 2 debian bugs (Closes: 400162, 400278) which can be encountered by many users but none of which is higher than normal priority (unfortunately ;-)) * fixes few other bugs which never hit Debian user yet * extends documentation Besides that 0.7.4-5: which never made into testing due to upload of 0.7.5 was extending documentation (Closes: 398739) which might be very beneficial to have in the new release. 0.7.5-2: refines the warning and NEWS entry for users upgrading from 0.6 releases of fail2ban (present in backports of sarge). Proper announcement on that transition is quite important for anyone using fail2ban since configuration files scheme was changed drastically. Closes: 402350 If no fresh RC bugs get filed within 10 days I would consider this release of fail2ban very worth been included into the next stable release of Debian. Thank you in advance -- .-. =-- /v\ = Keep in touch// \\ (yoh@|www.)onerussian.com Yaroslav Halchenko /( )\ ICQ#: 60653192 Linux User^^-^^[17] pgpLtAnU8xqfO.pgp Description: PGP signature
please unblock imagezoom
Dear Release Team, 0.2.7-3 closes release relevant bug (400168) of migrating over to iceweasel. Depends were corrected to include iceweasel. -- .-. =-- /v\ = Keep in touch// \\ (yoh@|www.)onerussian.com Yaroslav Halchenko /( )\ ICQ#: 60653192 Linux User^^-^^[17] pgpWjkcQHc3df.pgp Description: PGP signature
please ublock jsmath (3.3g-3)
The only changes were added debconf i18n translations (ru,fr,de) closing bugs (#402269,#399436,#399434) -- .-. =-- /v\ = Keep in touch// \\ (yoh@|www.)onerussian.com Yaroslav Halchenko /( )\ ICQ#: 60653192 Linux User^^-^^[17] pgpmxrBangN6y.pgp Description: PGP signature
