Your message dated Tue, 8 Mar 2016 20:50:44 +0100
with message-id <56df2d14.8050...@debian.org>
and subject line Re: jpathwatch: FTBFS in stretch, build dependencies not in
stretch
has caused the Debian Bug report #816998,
regarding jpathwatch: 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.)
--
816998: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816998
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:jpathwatch
Version: 0.95-4
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-ouaOcq/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 (>= 9), javahelper, default-jdk (>= 2:1.8), bnd
(>= 2.1.0), maven-repo-helper
Filtered Build-Depends: debhelper (>= 9), javahelper, default-jdk (>= 2:1.8),
bnd (>= 2.1.0), maven-repo-helper
dpkg-deb: building package 'sbuild-build-depends-jpathwatch-dummy' in
'/<<BUILDDIR>>/resolver-fye126/apt_archive/sbuild-build-depends-jpathwatch-dummy.deb'.
OK
Get:1 file:/<<BUILDDIR>>/resolver-fye126/apt_archive ./ InRelease
Ign:1 file:/<<BUILDDIR>>/resolver-fye126/apt_archive ./ InRelease
Get:2 file:/<<BUILDDIR>>/resolver-fye126/apt_archive ./ Release [2119 B]
Get:2 file:/<<BUILDDIR>>/resolver-fye126/apt_archive ./ Release [2119 B]
Get:3 file:/<<BUILDDIR>>/resolver-fye126/apt_archive ./ Release.gpg [299 B]
Get:3 file:/<<BUILDDIR>>/resolver-fye126/apt_archive ./ Release.gpg [299 B]
Get:4 file:/<<BUILDDIR>>/resolver-fye126/apt_archive ./ Sources [252 B]
Get:5 file:/<<BUILDDIR>>/resolver-fye126/apt_archive ./ Packages [571 B]
Reading package lists...
W: No sandbox user '_apt' on the system, can not drop privileges
Reading package lists...
+------------------------------------------------------------------------------+
| Install jpathwatch 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-jpathwatch-dummy : Depends: default-jdk (>= 2:1.8) 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: jpathwatch_0.95-4
Machine Architecture: amd64
Package: jpathwatch
Package-Time: 0
Source-Version: 0.95-4
Space: 0
Status: failed
Version: 0.95-4
--------------------------------------------------------------------------------
Finished at 20160306-2309
Build needed 00:00:00, 0k disc space
--------------------------------------------------------------------------------
Thanks.
--- End Message ---
--- Begin Message ---
On Mon, 07 Mar 2016 00:10:36 +0000 Santiago Vila <sanv...@debian.org> wrote:
> Package: src:jpathwatch
> Version: 0.95-4
> 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.
Hello,
jpathwatch build-depends on default-jdk (>= 2:1.8) which is not in
testing yet. It will definitely be part of Stretch in the near future.
https://packages.qa.debian.org/j/java-common.html
There is nothing wrong with the packaging of jpathwatch and the
versioned build-dependency is correct. Since jpathwatch builds fine in
Sid I am going to close this bug report now.
Regards,
Markus
signature.asc
Description: OpenPGP digital signature
--- End Message ---
