Bug#981930: libelf1: fails to install
Package: libelf1 Version: 0.182+20210203-1.1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: norb...@preining.info Updates are impossible since the update, the NMU which is supposed to fix the issue doesn't really fix it, I still get errors on installation: Unpacking libelf1:i386 (0.182+20210203-1.1) over (0.182-3) ... dpkg: error processing archive /var/cache/apt/archives/libelf1_0.182+20210203-1.1_i386.deb (--unpack): trying to overwrite shared '/usr/share/locale/en@boldquot/LC_MESSAGES/elfutils.mo', which is different from other instances of package libelf1:i386 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) This is preventing the whole system updates as apt immediately bails out. The NMU needs to be reverted or fixed ASAP. Thanks Norbert -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.12 (SMP w/8 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libelf1 depends on: ii libc6 2.31-9 ii zlib1g 1:1.2.11.dfsg-2 libelf1 recommends no packages. libelf1 suggests no packages. -- no debconf information
Bug#981930: libelf1: fails to install
Hi Helmut, > The bug you report is actually present in -1 already. Hmmm > The package is not unusable. It merely cannot be coinstalled. then why on earth did I have both arch (amd64, i386) installed on my computer before? And in addition, downgrading to the versions in testing did work without a hinch. So no, sorry to say, but you are wrong. The previous -1 packages **were** co-installable, and that bug did not occur. > It doesn't really fix it, because dh-strip-nondeterminism doesn't fix it > yet. That's a separate bug report. Might be a bug induced by the almighty nodeteriminsim/reproducible groups, but it does show up here. > Reverting the NMU doesn't help in any way. It's reproducibility issue. It **does**. I reverted to the version in testing without any problems. And whatever it is, if it is a reproducibility issue, I honestly don't give a #$#$Y(#'$ about it when it breaks the system. Reproducibility is not the highest aim we are targetting, it is just a tool. If it is broken, then dump it and ignore it, who cares (besides some former Debian Majesty). Best regards Norbert -- PREINING Norbert https://www.preining.info Fujitsu Research Labs + IFMGA Guide + TU Wien + TeX Live + Debian Dev GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
GCC 10 transition
Dear GCC Team, (please Cc) I would like to ask about how we should deal with gcc10 creating completely different symbols than what we currently have. Are we supposed to bump the ABI version for every library due to the symbols changes, or is there any other procedure to be expected. The announcement of Matthias: > I'm planning to make gcc-10 the default after gcc-10 (10.2.0) is available > (upstream targets mid July). binutils will be updated before making the GCC > switch. The GCC 10 switch involves some minor library transitions for D, > gccgo, > M2, which should be no-brainers. The gnat transition will be handled > separately > by the debian Ada maintainers. Doesn't really hint at problems to be expected, but we see considerable FTBFS due to symbols disappearing. Do you have any guideline on how to deal with these cases? Thanks Norbert -- PREINING Norbert https://www.preining.info Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Bug#889631: Bug#889647: mpfr 4.0 branch fails to build with texinfo.tex from automake
Hi everyone, > I see that the texinfo.tex version in automake is from 2013, and is definitely Automake is ^W (redacted). This is so much out of date that I not even consider it for bug reports. The version shipped by automake if from texinfo 4.13 which was released around 2008 (!) Since then there have been the releases of 5.0, 5.1, 5.2, 6.0, 6.1, 6.2, 6.3, 6.3, and 6.5, all of which (besides 6.2) have been in Debian. > assume texinfo's version of texinfo.tex is too old as well for the mpfr4 > build, That is a problem of mpfr4. If they require a texinfo.tex that is newer than what is in the latest released version, then this is a problem of mpfr4, and not texinfo. The latest release of texinfo is 6.5, and that is what is shipped in Debian and that is what texinfo.tex corresponds to. This bug shoud be (only) assigned to automake and mpfr4. All the best Norbert -- PREINING Norbert http://www.preining.info Accelia Inc. +JAIST +TeX Live +Debian Developer GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Bug#889631: Bug#889647: mpfr 4.0 branch fails to build with texinfo.tex from automake
Hi Vincent,
I cannot add much to your email, all correct.
> > I assume texinfo's version of texinfo.tex is too old as well for the
> > mpfr4 build,
>
> Probably, but maybe for a different reason. The current version
> from the texinfo package does not support @var in exponent or
> subscript as it yields a "\scriptfont 5 is undefined" error:
Indeed. That is fixed (partially) in the current SVN version, and an
updated texinfo files can be downloaded from the fnu server.
If you think it is worth it, I can patch the texinfo package to update
texinfo.tex
-\def\texinfoversion{2017-08-23.19}
+\def\texinfoversion{2018-01-09.11}
> (possibly patched, which would be the case now, but otherwise it seems
> that in general, this file is up-to-date as upstream texinfo has quite
See above, I can patch it.
> the symlink target, or it should be a separate package with the
> /usr/share/texmf/tex/texinfo files, similar to autotools-dev.
I don't see the need for a separate package, though.
Best
Norbert
--
PREINING Norbert http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian Developer
GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Bug#889631: Bug#889647: mpfr 4.0 branch fails to build with texinfo.tex from automake
> In case this was not clear, I meant that in addition to the texinfo > correction, something else needs to be done in another package, > either in automake or in mpfr4, to that the right texinfo.tex file automake is the culprit. Shipping and ancient, pre-historic texinfo.tex is simply wrong. Norbert -- PREINING Norbert http://www.preining.info Accelia Inc. +JAIST +TeX Live +Debian Developer GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Bug#889631: Bug#889647: mpfr 4.0 branch fails to build with texinfo.tex from automake
> Yes. To fix the automake issue, I would see 2 possibilities: Both are fine with me, I don't care which one is taken. I have uploaded a new texinfo package with patched texinfo.tex just now. Norbert -- PREINING Norbert http://www.preining.info Accelia Inc. +JAIST +TeX Live +Debian Developer GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Bug#892719: gcc-7: internal compiler error: unexpected expression ‘I’ of kind template_parm_index -- fixed upstream
Package: gcc-7 Version: 7.3.0-10 Severity: normal Tags: upstream Building TeX Live is hit by this bug: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84785 ../../../../../texk/dvisvgm/dvisvgm-src/src/utility.hpp:46:14: required from here ../../../../../texk/dvisvgm/dvisvgm-src/libs/variant/include/mpark/variant.hpp:1351:9: internal compiler error: unexpected expression ‘I’ of kind template_parm_index typename T = lib::type_pack_element_t, ^~~~ Please submit a full bug report, with preprocessed source if appropriate. See for instructions. which should be fixed for gcc7 in https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=258409 Thanks Norbert -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.15.8 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gcc-7 depends on: ii binutils 2.30-7 ii cpp-7 7.3.0-10 ii gcc-7-base7.3.0-10 ii libc6 2.27-2 ii libcc1-0 8-20180308-1 ii libgcc-7-dev 7.3.0-10 ii libgcc1 1:8-20180308-1 ii libgmp10 2:6.1.2+dfsg-3 ii libisl15 0.18-1 ii libmpc3 1.1.0-1 ii libmpfr6 4.0.1-1 ii libstdc++68-20180308-1 ii zlib1g1:1.2.8.dfsg-5 Versions of packages gcc-7 recommends: ii libc6-dev 2.27-2 Versions of packages gcc-7 suggests: pn gcc-7-doc pn gcc-7-locales pn gcc-7-multilib pn libasan4-dbg pn libatomic1-dbg pn libcilkrts5-dbg pn libgcc1-dbg pn libgomp1-dbg pn libitm1-dbg pn liblsan0-dbg pn libmpx2-dbg pn libquadmath0-dbg pn libtsan0-dbg pn libubsan0-dbg -- no debconf information
Bug#892719: gcc-7: internal compiler error: unexpected expression ‘I’ of kind template_parm_index -- fixed upstream
> Version: 7.3.0-11 Thanks Norbert -- PREINING Norbert http://www.preining.info Accelia Inc. +JAIST +TeX Live +Debian Developer GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Bug#528879: please add info-dir-section to your info files
Package: libcloog-ppl-dev Version: 0.15-1 Severity: normal Usertags: texinfo-transition Dear maintainer, we are currently replacing the dpkg install-info with GNU install-info and at the same time reworking the installation method for info files with triggers (see http://wiki.debian.org/Transitions/DpkgToGnuInstallInfo for details). As a package maintainer your only job is to drop info files below /usr/share/info and the package install-info will care for the rest by recreating the dir file from all installed info files. There is one problem in the info files of your packages libcloog-ppl-dev because the files: usr/share/info/cloog.info.gz do not ship info dir sections. Thus, calling install-info (the GNU version) on these files issue a warning: install-info: warning: no info dir entry in `/usr/share/info/...' and the file is not included in the dir file. The source of this problem is the following missing entry in the texinfo source: @dircategory Package short info @direntry * menu item 1: (infofile). Description. * menu item 2: (infofile2). Description. @end direntry In the experimental package we still let the above warnings go through, but with an upload to unstable they will be probably supressed. Can you please add an info dir entry to the texinfo files of your package to fix these warnings. If you have any questions please see the texinfo manual available in info format in texinfo-doc-nonfree, chapter 21 Creating and Installing Info Files, and do not hesitate to contact us at debian-tex-ma...@lists.debian.org Thanks a lot and all the best Norbert Preining texinfo maintainer -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
