Your message dated Sun, 6 Mar 2016 20:48:10 -0500
with message-id <20160307014810.gx7...@onerussian.com>
and subject line Re: Bug#817000: pymvpa2: FTBFS in stretch, build dependencies
not in stretch
has caused the Debian Bug report #817000,
regarding pymvpa2: FTBFS in stretch, build dependencies not in stretch
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
817000: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817000
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pymvpa2
Version: 2.4.1-1
Severity: serious
Dear maintainer:
I tried to build this package with "dpkg-buildpackage -A"
(i.e. only architecture-independent packages), and it failed.
But the failure is build-depends related, so it has nothing to do
with the fact that I was doing "dpkg-buildpackage -A", hence
the serious severity.
--------------------------------------------------------------------------------
[...]
Installing build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
sbuild-build-depends-core-dummy
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/770 B of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 file:/<<BUILDDIR>>/resolver-ge9Qdo/apt_archive ./
sbuild-build-depends-core-dummy 0.invalid.0 [770 B]
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package sbuild-build-depends-core-dummy.
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 14543 files and directories currently installed.)
Preparing to unpack .../sbuild-build-depends-core-dummy.deb ...
Unpacking sbuild-build-depends-core-dummy (0.invalid.0) ...
Setting up sbuild-build-depends-core-dummy (0.invalid.0) ...
W: No sandbox user '_apt' on the system, can not drop privileges
Merged Build-Depends: debhelper (>= 7.0.50~), python-all-dev (>= 2.6.6-3~),
swig2.0 | swig (<= 3.0.5), python-numpy, python-scipy, python-nibabel,
python-nose, python-h5py, python-lxml, libsvm-dev (>= 2.84.0), help2man,
man2html, python-sphinx, python-numpydoc, graphviz, inkscape, imagemagick, bc,
python-matplotlib, python-statsmodels
Merged Build-Conflicts: swig3.0 (>= 3.0.5)
Filtered Build-Depends: debhelper (>= 7.0.50~), python-all-dev (>= 2.6.6-3~),
swig2.0 | swig (<= 3.0.5), python-numpy, python-scipy, python-nibabel,
python-nose, python-h5py, python-lxml, libsvm-dev (>= 2.84.0), help2man,
man2html, python-sphinx, python-numpydoc, graphviz, inkscape, imagemagick, bc,
python-matplotlib, python-statsmodels
Filtered Build-Conflicts: swig3.0 (>= 3.0.5)
dpkg-deb: building package 'sbuild-build-depends-pymvpa2-dummy' in
'/<<BUILDDIR>>/resolver-foUw1E/apt_archive/sbuild-build-depends-pymvpa2-dummy.deb'.
OK
Get:1 file:/<<BUILDDIR>>/resolver-foUw1E/apt_archive ./ InRelease
Ign:1 file:/<<BUILDDIR>>/resolver-foUw1E/apt_archive ./ InRelease
Get:2 file:/<<BUILDDIR>>/resolver-foUw1E/apt_archive ./ Release [2119 B]
Get:2 file:/<<BUILDDIR>>/resolver-foUw1E/apt_archive ./ Release [2119 B]
Get:3 file:/<<BUILDDIR>>/resolver-foUw1E/apt_archive ./ Release.gpg [299 B]
Get:3 file:/<<BUILDDIR>>/resolver-foUw1E/apt_archive ./ Release.gpg [299 B]
Get:4 file:/<<BUILDDIR>>/resolver-foUw1E/apt_archive ./ Sources [373 B]
Get:5 file:/<<BUILDDIR>>/resolver-foUw1E/apt_archive ./ Packages [693 B]
Reading package lists...
W: No sandbox user '_apt' on the system, can not drop privileges
Reading package lists...
+------------------------------------------------------------------------------+
| Install pymvpa2 build dependencies (apt-based resolver) |
+------------------------------------------------------------------------------+
Installing build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
sbuild-build-depends-pymvpa2-dummy : Depends: swig2.0 but it is not
installable or
swig (<= 3.0.5) but it is not
going to be installed
E: Unable to correct problems, you have held broken packages.
apt-get failed.
Package installation failed
Reading package lists...
Building dependency tree...
Reading state information...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists...
Building dependency tree...
Reading state information...
The following packages will be REMOVED:
sbuild-build-depends-core-dummy*
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 0 B of additional disk space will be used.
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 14543 files and directories currently installed.)
Removing sbuild-build-depends-core-dummy (0.invalid.0) ...
W: No sandbox user '_apt' on the system, can not drop privileges
+------------------------------------------------------------------------------+
| Cleanup |
+------------------------------------------------------------------------------+
Purging /<<BUILDDIR>>
Reading package lists...
Building dependency tree...
Reading state information...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists...
Building dependency tree...
Reading state information...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
E: Package build dependencies not satisfied; skipping
+------------------------------------------------------------------------------+
| Summary |
+------------------------------------------------------------------------------+
Build Architecture: amd64
Build-Space: 0
Build-Time: 0
Distribution: stretch
Fail-Stage: install-deps
Host Architecture: amd64
Install-Time: 0
Job: pymvpa2_2.4.1-1
Machine Architecture: amd64
Package: pymvpa2
Package-Time: 0
Source-Version: 2.4.1-1
Space: 0
Status: failed
Version: 2.4.1-1
--------------------------------------------------------------------------------
Finished at 20160306-2256
Build needed 00:00:00, 0k disc space
--------------------------------------------------------------------------------
Thanks.
--- End Message ---
--- Begin Message ---
On Mon, 07 Mar 2016, Santiago Vila wrote:
> The following packages have unmet dependencies:
> sbuild-build-depends-pymvpa2-dummy : Depends: swig2.0 but it is not
> installable or
> swig (<= 3.0.5) but it is not
> going to be installed
well -- swig2.0 was removed from testing but present in sid
my guess is that pymvpa2 pkg would eventually be autoremoved from
testing, and there is nothing for me to do about it neither now nor
later to "close" this issue.
FWIW -- can't use swig 3.x due to
https://github.com/swig/swig/issues/563 which could have been a
proper 'fix'. But as long as swig2.0 is part of the archive, issue is
not really an issue for me to tackle. So I will close it for now, feel
free to reopen if you feel it would be of some value (please describe of
which)
--
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
--- End Message ---
