Processing control commands:
> tags -1 + wontfix
Bug #859960 [gcj-jdk] gcj-jdk: dh_javadoc: please add -notimestamp to invocation
Added tag(s) wontfix.
--
859960: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859960
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 + wontfix
no, gcj is dead upstream, and will be removed for buster.
On 09.04.2017 19:54, Chris West wrote:
> Package: gcj-jdk
> Version: 4:6.3.0-4
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: timestamps toolchain
> Priority: wishlist
>
> By default, the javado
The bug is not really in gcj, it's in a script in gcc-defaults, which
ends up in the binary named gcj-jdk for some bizarre reason.
However, I've just been looking further, and it looks like the script is
literally only used by jaminid, and that jaminid looks pretty abandoned
upstream, and has no d
Dear debian-gcc,
When building current stable's gcc-4.9 I encountered bug 769218 and I
was also able to get a successful build on the same machine.
System:
Dual Xeon L5640 (24 threads) with 32 GB RAM, and all disk-based
filesystems residing on a magnetic hdd. The host system contains debian
Dear debian-gcc,
When building current stable's gcc-4.9 I encountered bug 769218 and I
was also able to get a successful build on the same machine.
System:
Dual Xeon L5640 (24 threads) with 32 GB RAM, and all disk-based
filesystems residing on a magnetic hdd. The host system contains debian
Package: gcj-jdk
Version: 4:6.3.0-4
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps toolchain
Priority: wishlist
By default, the javadoc(1) command adds timestamps to the generated
HTML. This prevents any build package from being reproducible. This
isn't useful in a Debian p
LAST_UPDATED: Thu Apr 6 20:18:06 UTC 2017 (revision 246741)
Target: x86_64-kfreebsd-gnu
gcc version 6.3.0 20170406 (Debian 6.3.0-12)
=== acats tests ===
FAIL: c52103x
FAIL: c52104x
FAIL: c52104y
FAIL: cb1010a
FAIL: cb1010c
FAIL: cb1010d
=== acats Sum
LAST_UPDATED: Tue Mar 21 11:43:07 UTC 2017 (revision 246313)
Target: x86_64-kfreebsd-gnu
gcc version 6.3.0 20170321 (Debian 6.3.0-11)
=== acats tests ===
FAIL: c52103x
FAIL: c52104x
FAIL: c52104y
FAIL: cb1010a
FAIL: cb1010c
FAIL: cb1010d
=== acats Sum
LAST_UPDATED: Thu Apr 6 20:18:06 UTC 2017 (revision 246741)
Target: i686-kfreebsd-gnu
gcc version 6.3.0 20170406 (Debian 6.3.0-12)
=== acats tests ===
FAIL: c52103x
FAIL: c52104x
FAIL: c52104y
FAIL: cb1010a
FAIL: cb1010c
FAIL: cb1010d
=== acats Summa
Processing commands for cont...@bugs.debian.org:
> unarchive 769218
Bug #769218 {Done: Matthias Klose } [src:gcc-4.9] gcc-4.9:
FTBFS in jessie: Error! CRCs do not match! Got 264aca47, expected 95962ba4
Unarchived Bug 769218
> found 769218 gcc-4.9/4.9.2-10
Bug #769218 {Done: Matthias Klose } [src:
Source: gcc-7
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap
Building gcc libraries with DEB_STAGE=rtlibs is now successful. Yet the
resulting packages are not currently installable. See e.g.:
> Setting up gcc-7-base:tilegx (7-20170316-1) ...
> dpkg: dependency problems prevent config
Processing control commands:
> affects -1 + libsikuli-script-jni
Bug #859914 [libstdc++6] libstdc++6: please add Breaks: libopencv-core2.4
Added indication that 859914 affects libsikuli-script-jni
--
859914: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859914
Debian Bug Tracking System
Conta
Package: libstdc++6
Version: 6.3.0-11
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + libsikuli-script-jni
Hi doko,
please add another Breaks to libstdc++: against libopencv-core2.4
In piuparts I found that the jessie->stretch upgrade of
libsikuli-sc
13 matches
Mail list logo
