Followup-For: Bug #1091161
A few rounds of cvise produced this minimized reproducer:
extern "C" double copysign(double, double);
double ccosh_x;
struct type {
double x;
double y;
};
template struct complex {
complex(T, T);
complex() = default;
T real() { return data.x; }
T imag() { r
Control: reopen -1
On Tue, 12 Nov 2024 18:05:31 +0100 Matthias Klose wrote:
Version: 2.43.50.20241004-1
That version looks like it belongs to src:binutils, not src:cvise.
Andreas
Source: gcc-doc-defaults
Version: 5:27
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
gcc-doc-defaults started to FTBFS when the default compiler has been
switched to GCC 14. Please update the doc package to GCC 14, too.
Andreas
Source: gcc-13-cross
Version: 14
Severity: serious
Hi,
there are undeclared file conflicts between gnat-13- and
gnat-{9,10}- in sid. (but not between -9- and -10-).
Maybe it would be sufficient to rebuild the package against gcc-13
13.2.0-13 which had some gnat conflict fixes.
The conflicting fi
Package: gnat-13-x86-64-linux-gnu
Version: 13.2.0-12
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.
>From the attached log (scroll to the bottom...)
Package: libgccjit-14-doc
Version: 14-20240127-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwr
Please try to get this fixed in bookworm, too.
Thanks
Andreas
Followup-For: Bug #999414
Control: found -1 0.189-2
Control: found -1 0.189-3
Control: severity -1 serious
Control: tag -1 sid trixie
the postrm script contains a bashism in purge_debuginfod_ubuntu:
local -r
and another bug: calling purge_debuginfod_ubuntu even for Debian
resulting in this purge
Followup-For: Bug #1036641
Control: tag -1 patch
I've been running bullseye->bookworm upgrade tests with the following
change applied to src:gcc-12, this had the best results w.r.t. upgrading
gnat related packages:
--- gcc-12-12.2.0/debian/rules.conf 2023-01-02 14:06:37.0 +0100
+++ gc
Package: gcc-12-base
Version: 12.2.0-14
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
As usual, it is helpful to bump the Breaks against gnat (which is not
co-installable) for smoother upgrades from bullseye to ensure the
obsolete gnat-10 stack gets removed.
Andreas
Package: gm2-12-doc,gm2-13-doc
Severity: serious
Control: found -1 12.2.0-10
Control: found -1 13-20221214-1
Hi,
there is a file conflict between gm2-12-doc and gm2-13-doc:
Preparing to unpack .../gm2-13-doc_13-20221214-1_all.deb ...
Unpacking gm2-13-doc (13-20221214-1) ...
dpkg: error pro
Package: gm2-12-doc
Version: 12.2.0-8
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries t
Package: dwz
Version: 0.14-1
Severity: serious
Control: block 1016935 with -1
Hi,
assaultcube recently started to FTBFS with a dwz error. Since both
src:assaultcube and src:dwz haven't been changed for a long time and
successfully built previously, I suspect this is related to GCC 12
becoming the
Control: found -1 12-2027-1
All fixed but gcc-11-locales=11.2.0-10 vs. gcc-12-locales=12-2027-1:
usr/share/locale/be/LC_MESSAGES/cpplib-11.mo
usr/share/locale/ca/LC_MESSAGES/cpplib-11.mo
usr/share/locale/da/LC_MESSAGES/cpplib-11.mo
usr/share/locale/de/LC_MESSAGES/cpplib-11.mo
usr/share/l
Source: gcc-12
Version: 12-2023-1
Severity: serious
To avoid repeating this bug on every new major upstrema release,
I'd suggest to add
Conflicts+Replaces+Provides: some-new-virtual-package
to all intentionally not co-installable packages in addition to the
Breaks+Replaces that is needed now
Source: gcc-doc-defaults
Version: 5:22
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
debian/rules override_dh_gencontrol-arch
make[1]: Entering directory '/build/gcc-doc-defaults-22'
# call dh_gencontrol one at a time for *-doc pack
Package: libdebuginfod-common
Version: 0.183-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package modifies conffiles.
This is forbidden by the policy, see
https://www.debian.org/doc/debian-policy/ch-files.html#configuration
On 15/02/2021 10.07, Matthias Klose wrote:
On 2/14/21 5:58 PM, Simon McVittie wrote:
On Sat, 13 Feb 2021 at 19:52:10 +0100, Paul Gevers wrote:
[The release team are] pretty concerned about a couple of known RC bugs
which need the proper attention of people familiar with upgrade paths
as there's
Package: gcc-10-base
Version: 10.2.1-6
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
while investigating some buster->bullseye upgrade failures in piuparts I
came across a case where apt tries to keep libstdc++-8-dev installed to
satisfy the libstdc++-dev dependency of
Package: g++-10
Version: 10.2.1-6
Severity: serious
Hi,
while rebuilding src:nheko I noticed an ICE with SEGFAULT.
I've somewhat minimized the testcase with delta (from 3.3 MB to 15 KB).
Build the attached code with
x86_64-linux-gnu-g++-10 -std=c++17 -Wno-return-type -c gcc-10-segfault.
Package:
gcc-10-offload-amdgcn,gcc-11-offload-amdgcn,gcc-10-hppa64-linux-gnu,gcc-11-hppa64-linux-gnu
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: found -1 10.2.1-1
Control: found -1 11-20201208-1
Hi,
during a test with piuparts I noticed your package fails to up
Followup-For: Bug #977408
Add libgccjit-11-doc which misses a Conflicts: libgccjit-10-doc to the list.
There are file conflicts on .png files with very generic names:
usr/share/info/factorial.png
usr/share/info/factorial1.png
usr/share/info/libgccjit.info.gz
usr/share/info/sum-of-squares.png
usr
Package: libgm2-17
Version: 11-20201208-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships
-rw-r--r-- root/root 31064 2020-12-08 14:08
./usr/lib/x86_64-linux-gnu/libm2cor.so.15.0.0
-rw-r--r-- root/root189
Package: libstdc++-11-doc
Version: 11-20201208-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because
I have a similar usecase like Bill: I have lots of gcc-*-multilib
packages installed (from ancient to to experimental) for doing
compilation tests for $software with many different compiler versions.
nearly all lib(x)32XYZ packages built by gcc-N (N < 9? 8?) depend on
lib(x)32gcc1
In the end I wo
Package: gcc-doc-defaults
Version: 5:20
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi,
gcc-doc-defaults needs to be updated after GCC 10 was made the default
compiler. It does currently FTBFS.
Andreas
On 21/05/2020 14.05, Matthias Klose wrote:
> On 5/20/20 10:32 PM, Andreas Beckmann wrote:
>> With the transitional packages gone in 10.1.0-2, please add versioned
>> (epoched!) provides on the old names (as already done in libgcc-s1)
>> in order to keep old packages install
Package: lib32gcc-s1,libx32gcc-s1
Version: 10.1.0-2
Severity: important
With the transitional packages gone in 10.1.0-2, please add versioned
(epoched!) provides on the old names (as already done in libgcc-s1)
in order to keep old packages installable along the latest gcc.
Thanks
Andreas
On 02/04/2020 11.13, Matthias Klose wrote:
> On 4/2/20 1:30 AM, Andreas Beckmann wrote:
>> On Thu, 26 Mar 2020 21:02:59 +0100 Matthias Klose wrote:
>>> yes, but we cannot rebuild the package, because it build-depends on gnat-8.
>>> Filed a removal bug for gcc-8 inste
On Thu, 26 Mar 2020 21:02:59 +0100 Matthias Klose wrote:
> yes, but we cannot rebuild the package, because it build-depends on gnat-8.
> Filed a removal bug for gcc-8 instead.
An easy fix would probably be to temporarily add a versioned
Provides: libgcc-s1 (= 1:${binary:Version})
to libgcc-s1 i
Package: libgomp-plugin-nvptx1
Version: 9.2.1-21
Severity: normal
Hi,
libgomp-plugin-nvptx1 currently comes with
Suggests: libcuda1
Please update that to
Suggests: libcuda1 | libcuda1-any
to include the virtual package provided by all libcuda1 variants in
non-free.
Or if you prefer to have a
Package: g++-x86-64-linux-gnu
Version: 4:8.3.0-1
Severity: normal
User: debian...@lists.debian.org
Usertags: piuparts
Control: found -1 g++-x86-64-linux-gnu/4:8.3.0-1
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the
On 2019-03-26 13:21, Debian Bug Tracking System wrote:
> #924911: gcc-8-base: please add Breaks: gnat-6 (<< 6.4)
That worked as expected :-)
Thanks!
Andreas
Package: gcc-8-base
Version: 8.3.0-3
Severity: important
Hi,
this should fix some upgrade paths from stretch to buster as encountered
by piuparts. In some cases apt tries to keep gnat-6 installed instead of
installing gnat-8. The existing Breaks: gnat (<< 7) is not sufficient to
"solve" this prop
Followup-For: Bug #915678
Control: found -1 4:8.3.0-1
Control: found -1 g++-x86-64-linux-gnux32/4:8.3.0-1
Control: affects -1 + g++-x86-64-linux-gnux32
Hi,
this invalid symlink is still present in some packages:
0m28.0s ERROR: FAIL: Broken symlinks:
/usr/share/doc/g++-x86_64-linux-gnux32 -> cp
Package: dwz
Version: 0.12-3
Severity: important
Hi,
I tried updating pocl to debhelper-compat (= 12), but it failed on i386
(while amd64 built fine):
[...]
dh_install -O--buildsystem=cmake
dh_installdocs -O--buildsystem=cmake
dh_installdocs: Cannot auto-detect main package for pocl-doc.
Package: libgccjit-9-doc
Version: 9-20190103-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
libgccjit-9-doc needs to conflict with libgccjit-8-doc like it does with
the older ones.
Andreas
libgccjit-8-doc=8.2.0-13_libgccjit-9-doc=9-20190103-1.log.gz
Description: applic
Package: gccgo-doc
Version: 5:7.2.0-2
Severity: normal
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
0m46.5s ERROR: FAIL: Broken symlinks:
/usr/s
Package: gcc-x86-64-linux-gnux32
Version: 4:8.2.0-2
Severity: normal
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
0m26.3s ERROR: FAIL: Broken syml
Package: cpp-6-x86-64-linux-gnu
Version: 6.5.0-2cross1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.
>From the attached log (scroll to the bottom..
Package: gcc-8-base
Version: 8.2.0-8
Severity: important
Hi doko,
the
Breaks: gnat (<< 7)
is present in gcc-7-base, but missing in gcc-8-base. Adding this should
fix some upgrade issues from stretch to buster where old gnat-6 built
packages are kept installed instead of being removed. gcc-7-bas
On 2018-10-22 15:13, Matthias Klose wrote:
> The compat symbol was in GCC 7, and then removed in GCC 8. Sure, that doesn't
> help with the distro upgrade. There is nothing in GCC to change, so if you
> want
> to fix that, you need a rename of the affected library packages.
That sounds like someo
Control: clone -1 -2
Control: reassign -2 g++-8
Control: retitle -2 g++-8: removal of old abi mangling breaks compatibility
with stretch
On 2018-10-15 18:18, Julian Andres Klode wrote:
> So, I think this affects more than just apt. gcc 7 broke the ABI
> by adding a new mangling
>
> URI::operat
Package: cpp-x86-64-linux-gnu
Version: 4:8.2.0-1
Severity: normal
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + gcc-x86-64-linux-gnu
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the botto
Source: gcc-doc-defaults
Version: 5:17.1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Hi,
gcc-doc-defaults FTBFS in sid. It probably needs some updates now that
gcc-8 has become the default gcc.
[...]
debian/rules override_dh_gencontrol-arc
Package: gcc-x86-64-linux-gnux32
Version: 4:8.1.0-1
Severity: normal
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
0m33.0s ERROR: FAIL: Broken syml
On 2018-06-08 17:51, Matthias Klose wrote:
> you should not run piuparts against outdated binaries.
These tests take everything available in the Packages files ...
> I filed #899045
> to remove these packages, but that didn't get yet processed. Closing
> this issue now.
Interestingly these pac
Package: gnat-7-x86-64-linux-gnu,gnat-8-x86-64-linux-gnu
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'stretch'.
It installed fine in 'stretch', then the upgrade to 'buster' fails
because it trie
Source: gcc-8-cross
Version: 12
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.
>From the attached log (scroll to the bottom...):
Selecting previo
Package: gcc-7-base
Version: 7.2.0-14
Severity: normal
Hi,
please add a
Breaks: gnat (<< 7)
to gcc-7-base (and merge this to gcc-8-base ...) to fix some stretch ->
buster upgrade paths involving old ada libraries where apt may prefer to
keep gnat-6 installed instead of switching to gnat-7 ...
On 11/09/2017 04:43 PM, Matthias Klose wrote:
> is this with the gcc-5-cross* packages which are currently built but not
> uploaded?
I waited a bit, but no new binaries appeared. The tested packages are
versioned 5.5.0-3cross1.
There is another broken link in some gcj-5- packages, that does
remi
Source: gcc-5
Version: 5.5.0-3
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
0m25.1s ERROR: FAIL: Broken symlinks:
/usr/lib/g
Package: libx32stdc++6-8-dbg
Version: 8-20171023-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi doko,
the last round of adding Conflicts seems to have missed this one:
Selecting previously unselected package libx32stdc++6-8-dbg.
Preparing to unpack .../15-libx32st
Followup-For: Bug #872233
Control: affects -1 + lib64objc-5-dev
There is also a similar broken symlink in lib64objc-5-dev
0m40.2s ERROR: FAIL: Broken symlinks:
/usr/lib/gcc/i686-linux-gnu/5/64/libobjc_gc.so ->
../../../../../lib64/libobjc_gc.so.4
Andreas
Source: gcc-8
Version: 8-20170923-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + lib32stdc++6-8-dbg libgccjit-8-doc libstdc++-8-doc
libstdc++6-8-dbg libx32stdc++6-8-dbg
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'si
Followup-For: Bug #872233
Control: found -1 5.4.1-12
Hi,
the broken symlinks are still here:
0m46.5s ERROR: FAIL: Broken symlinks:
/usr/lib/gcc/x86_64-linux-gnu/5/32/libobjc_gc.so ->
../../../../../lib32/libobjc_gc.so.4
0m57.3s ERROR: FAIL: Broken symlinks:
/usr/lib/gcc/x86_64-linux-gnu/5/
Source: gcc-6
Version: 6.4.0-3
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
0m42.6s ERROR: FAIL: Broken symlinks:
/usr/lib/g
Package: lib32objc-5-dev,libx32objc-5-dev
Version: 5.4.1-11
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
0m26.7s ERROR: FAIL: Br
Package: gcc-doc-defaults
Version: 5:16
Severity: serious
Tags: sid buster
User: debian-gcc@lists.debian.org
Usertags: ftbfs-gcc-7
gcc-doc-defaults FTBFS since GCC-7 was made the default compiler:
[...]
debian/rules override_dh_gencontrol-arch
make[1]: Entering directory '/build/gcc-doc-defaul
Source: gcc-7
Version: 7.1.0-11
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
new version, new broken symlinks ;-)
During a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
0m22.6s ERROR
Followup-For: Bug #866150
Control: affects -1 + libx32objc-6-dev lib64objc-7-dev libx32objc-7-dev
Similar problems in libx32objc-6-dev, lib64objc-7-dev, libx32objc-7-dev:
0m26.6s ERROR: FAIL: Broken symlinks:
/usr/lib/gcc/i686-linux-gnu/6/x32/libobjc_gc.so ->
../../../../../libx32/libobjc_gc.s
Package: lib64objc-6-dev
Version: 6.3.0-19
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
0m27.1s ERROR: FAIL: Broken symlinks:
On 2017-05-31 22:55, Andreas Beckmann wrote:
> libktoblzcheck1c2a (replaced by libktoblzcheck1v5)
> libterralib (replaced by libterralib3)
> libmagickcore-6.q16-2 (replaced by
> libmagick
Package: libstdc++6
Version: 6.3.0-18
Severity: important
Hi,
during my piuparts upgrade tests I identified a few upgrade paths that
could likely be smoothened by adding a few Breaks to libstdc++6:
libktoblzcheck1c2a(replaced by libktoblzcheck1v5)
libterralib
On 2017-05-31 16:01, Andreas Beckmann wrote:
> I'll now build a gcc-6 with that Breaks added ...
... and can confirm that it fixes the upgrade path of
libreoffice-subsequentcheckbase (where I previously observed a kept back
tzdata (and openjdk-7) from jessie).
Andreas
Package: gcc-6-base
Version: 6.3.0-18
Severity: important
Hi Doko,
would it be possible to use gcc-6-base as the bigger hammer to smoothen
the openjdk 7 -> 8 upgrade from jessie to stretch?
The Breaks: tzdata-java added in openjdk-8-jre-headless (#857992)
improved the situation a lot, but I still
Package: libstdc++6
Version: 6.3.0-14
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + gir1.2-ganv-1.0
Hi,
I just found an upgrade path on i386 that doesn't work as expected:
Starting 2 pkgProblemResolver with broken count: 2
Investigating (0) lib
Control: severity -1 important
On Wed, 5 Apr 2017 21:21:06 +0200 Andreas Beckmann wrote:
> Control: severity -1 serious
> and resulting in packages without copyright file after upgrade
> e.g. gdc-mips64-linux-gnuabi64 4:6.3.0-1 -> 4:6.3.0-2
This is tracked separately as #860117
Andreas
Followup-For: Bug #858112
Control: reopen -1
Control: found -1 1.168
Hi,
the broken README.Bugs symlink is still there ...
/usr/share/doc/cpp-mips-linux-gnu/README.Bugs -> ../gcc-6-base/README.Bugs
/usr/share/doc/cpp-s390x-linux-gnu/README.Bugs -> ../gcc-6-base/README.Bugs
/usr/share/doc/c
Package: gcc-hppa-linux-gnu,gcc-sh4-linux-gnu
Version: 4:6.3.0-4
Severity: normal
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
0m39.9s ERROR: FAIL
Source: gcc-defaults
Version: 1.168
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
a test with piuparts revealed that your package misses the copyright
file after an upgrade, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#s-co
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
Control: severity -1 serious
On Sat, 18 Mar 2017 15:07:06 +0100 Andreas Beckmann wrote:
> and another one in gdc-
>
> /usr/share/doc/gdc-/cpp- ->
> cpp-
and resulting in packages without copyright file after upgrade
e.g. gdc-mips64-linux-gnuabi64 4:6.3.0-1 -> 4:6.3.0-2
Followup-For: Bug #858112
and another one in gdc-
/usr/share/doc/gdc-/cpp- -> cpp-
Andreas
Source: gcc-defaults
Version: 1.165
Severity: normal
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
0m35.0s ERROR: FAIL: Broken symlinks:
/usr/sha
Followup-For: Bug #857384
Hi,
there is a similar problem in the -cross packages:
0m28.6s ERROR: FAIL: Broken symlinks:
/usr/share/man/man1/alpha-linux-gnu-gnatgcc.1.gz -> alpha-linux-gnu-gcc-6.1.gz
as well as in gnat-5:
0m52.1s ERROR: FAIL: Broken symlinks:
/usr/share/man/man1/gnatgcc.1.gz
same problem in gcc-5-hppa64-linux-gnu:
0m30.3s ERROR: FAIL: Broken symlinks:
/usr/share/man/man1/hppa64-linux-gnu-gcc-ranlib-5.1.gz -> gcc-ranlib-5.1.gz
/usr/share/man/man1/hppa64-linux-gnu-gcc-nm-5.1.gz -> gcc-nm-5.1.gz
/usr/share/man/man1/hppa64-linux-gnu-gcc-ar-5.1.gz -> gcc-ar-5.1.gz
Followup-For: Bug #855640
Hi,
this problem also exists in the gcc-5-cross packages, should I clone
this bug?
Andreas
Package: gcc-6-hppa64-linux-gnu
Version: 6.3.0-8
Severity: normal
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
0m39.4s ERROR: FAIL: Broken symlink
Package: gnat-6
Version: 6.3.0-8
Severity: normal
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
0m40.5s ERROR: FAIL: Broken symlinks:
/usr/share/
Source: gcc-6-cross
Version: 18
Severity: normal
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed the gcc-6- cross compilers
ship a broken symlink.
>From the attached log (scroll to the bottom...):
0m32.5s ERROR: FAIL: Broken symlinks:
/usr/lib/gcc
Source: gcc-6-cross
Version: 16
Severity: normal
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed that the gcj-6- packages
built from src:gcc-6-cross ship a broken symlink:
/usr/lib/gcc-cross//6/ecj1 -> ../../ecj1
I couldn't find the target /usr/li
Package: libstdc++6
Version: 6.3.0-6
Severity: important
Hi,
while analyzing piuparts upgrade logs for jessie->stretch, I came across
several cases where the openmpi stack was kept at the jessie version
(libopenmpi1.6 and friends) instead of being upgraded to libopenmpi2
etc. (See also #851681: a
Control: reassign -1 gcc-6 6.3.0-3
On 2017-01-19 17:14, Matthias Klose wrote:
> That was fixed in today's gcc-6 6.3.0-3 upload. The man pages should be there.
looks better, but not perfect, since there is now a new issue:
0m28.5s ERROR: FAIL: Broken symlinks:
/usr/share/man/man1/gcov-6.1 -> x8
Package: gcc
Version: 4:6.3.0-1
Severity: normal
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
the gcc metapackage installs a few broken manpage symlinks:
/usr/share/man/man1/x86_64-linux-gnu-gcc-ranlib.1.gz -> gcc-ranlib-6.1.gz
/usr/share/man/man1/x86_64-linux-gnu-gcc-nm.1.gz -> g
Control: retitle -1 libgcc-6-dev: Missing crtfastmath.o on kfreebsd-*
Control: affects -1 + src:vlc
On Tue, 9 Aug 2016 11:39:54 +0200 Matthias Klose wrote:
> > I'm unable to build a package because crtfastmath.o is missing from this
> > package. Architecture is kfreebsd-i386. I don't see this bug
Package: gdc-5
Version: 5.4.0-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other package
Package: libgcj-bc
Version: 5.3.1-2
Severity: serious
Hi,
the libgcj-bc.shlibs file contains
libgcj_bc 1 libgcj-bc (>= 5.3.1-17~)
which is unsatisfiable and causes e.g. uninstallable ant packages:
https://packages.qa.debian.org/a/ant.html
Should this have been
libgcj_bc 1 libgcj16 (>=
Source: gcc-doc-defaults
Version: 5:14
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Hi,
gcc-doc-defaults FTBFS in curent sid:
dh_builddeb
dpkg-deb: building package 'gcc-doc' in '../gcc-doc_5.1.0-1_amd64.deb'.
dpkg-deb: building package 'gcc
Control: tag -1 - help + pending
On 2016-05-09 11:54, Matthias Klose wrote:
> On 09.05.2016 10:17, Andreas Beckmann wrote:
>> Followup-For: Bug #818873
>
> that's already fixed in the VCS.
Good, so let's fix the tags :-)
Andreas
Followup-For: Bug #818873
Hi,
in
https://buildd.debian.org/status/fetch.php?pkg=gcc-5-cross&arch=all&ver=21&stamp=1462410260
the failing command is
DEB_HOST_ARCH=s390x ARCH=s390x MAKEFLAGS="CC=something" dh_shlibdeps
-plibgnat-5-s390x-cross \
-l/lib/s390x-linux-gnu:/usr/lib/s390x-li
Followup-For: Bug #810809
Control: reassign -1 src:gcc-6 6-20160205-1
Control: reopen -1
Control: affects -1 + src:gcc-6-cross src:gcc-6-cross-ports
Hi,
the *gnat*-cross package relationships seem not to work correctly, yet:
Selecting previously unselected package gnat-6-aarch64-linux-gnu.
P
Package: libgccjit-6-doc
Version: 6-20160205-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because i
Package: libx32stdc++6-6-dbg,lib32stdc++6-6-dbg,libgccjit-6-doc
Version: 6-20160122-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the up
Source: gcc-6-cross
Version: 6-20160109-1cross1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
During a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because
Control: found -1 6-20160109-1
On 2016-01-09 20:51, Debian Bug Tracking System wrote:
> Version: 6-20160109-1
I can still reproduce these overwrite conflicts with the 20160109 snapshot.
Andreas
Package: libstdc++-6-doc
Version: 6-20160109-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.
Severity: serious
Followup-For: Bug #810514
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite
Package: libgcj17,libgcj17-awt
Version: 6-20160103-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.
See
Package: libstdc++6-6-dbg
Version: 6-20151211-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because
1 - 100 of 137 matches
Mail list logo
