Bug#1069424: yosys: FTBFS on armhf: make[3]: *** [Makefile:32: 011/submod_dots.pdf] Error 1
Hi Tarkik, Hi Larry, I think I've finally found the issue and uploaded 0.33-6~exp3 to confirm. On Sun, Sep 22, 2024 at 12:11:21PM +0200, Tarik Graba wrote: > This bug seems to be related to an old version of the upstream source. > Is it still present on newer releases? The issue is still present upstream https://github.com/YosysHQ/yosys/issues/4631. > Also, shouldn't this package be in the Debian/Electronics category? I assume you're talking about the Maintainer field. Yosys is maintained under the Debian Science team for historical reasons I've considered moving it before but it didn't seem worth the hassle. It's part of the debian-electronics (electronics-digital) metapackage either way. > I am not very aware of the Debian packaging process, but I can help with > testing if needed. I'm still looking for suggestions for FPGA designs we can use to test the whole yosys+nextpnr flow in Debian. See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068174#30. --Daniel signature.asc Description: PGP signature
Bug#1067465: yosys-plugin-ghdl builds on x86 only, but built on other architectures before
Hi Matthias, On Thu, Mar 21, 2024 at 11:16:56PM +0100, Matthias Klose wrote: > Package: src:yosys-plugin-ghdl > * Use ghdl-mcode instead of ghdl-gcc as it's more portable > > but ghdl-mcode is only available on amd64 and i386. With this choice you're > making things worse. My bad, I was under the impression mcode was an interpreter backend. Will fix this with the next upload. --Daniel signature.asc Description: PGP signature
Bug#1066707: ifupdown-ng: FTBFS: libifupdown/interface.c:28:9: error: implicit declaration of function ‘strlcpy’; did you mean ‘strncpy’? [-Werror=implicit-function-declaration]
On Wed, Mar 13, 2024 at 12:51:44PM +0100, Lucas Nussbaum wrote: > Source: ifupdown-ng > > During a rebuild of all packages in sid, your package failed to build > on amd64. Thanks Lucas, I'm uploading a fix right now. > This is most likely caused by a change in dpkg 1.22.6, that enabled > -Werror=implicit-function-declaration. For more information, see > https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration It was due to a hardcoded path to libbsd's include directory which seems to have moved to to a multiarch location. Thanks, --Daniel signature.asc Description: PGP signature
Bug#1042276: closing 1042276
close 1042276 3.0.0+dfsg-1 thanks We're now depending on g++-12 explicitly.
Bug#1052902: yosys: FTBFS: make[2]: *** [Makefile:971: docs/gen_images] Error 2
Hi Lucas, On Tue, Sep 26, 2023 at 03:43:28PM +0200, Lucas Nussbaum wrote: > Source: yosys > Version: 0.33-5 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20230925 ftbfs-trixie > > The full build log is available from: > http://qa-logs.debian.net/2023/09/25/yosys_0.33-5_unstable.log Is the buildinfo file for the rebuild available somewhere too? I'd like to diff the build environment against what the buildds had. Thanks, --Daniel signature.asc Description: PGP signature
Bug#1051847: iproute2 ships configuration files in /usr/lib violating debian-policy
Package: iproute2 Version: 6.1.0-3 Severity: serious Justification: Policy 10.7.2 X-Debbugs-Cc: d...@darkboxed.org Dear Maintainer, your iproute2 6.5.0-3 package installs configuration files in /usr/lib/iproute2. This is a blatant violation of debian-policy section 10.7.2. "Configuration files / Location" which states as follows: > Any configuration files created or used by your package must reside > in /etc. If there are several, consider creating a subdirectory of > /etc named after your package. As I've mentioned in Bug#1051577 this is related to upstream commit commit 0a0a8f12fa1b03dd0ccbebf5f85209d1c8a0f580 Read configuration files from /etc and /usr Add support for the so called "stateless" configuration pattern (read from /etc, fall back to /usr), giving system administrators a way to define local configuration without changing any distro-provided files. In practice this means that each configuration file FOO is loaded from /usr/lib/iproute2/FOO unless /etc/iproute2/FOO exists. but moving the config files from /etc/iproute to /usr/lib is misguided and should be overriden in your Debian package. Thanks, --Daniel
Bug#1010964: yosys: autopkgtest regression
On Sun, Jul 03, 2022 at 08:49:38AM +0200, Petter Reinholdtsen wrote: > I notice the new upload of 0.18 already happened, which is very nice to > see. But this bug was not closed in debian/changelog. Does this mean > bug #1010964 is not solved? > > Also, remember to ask ftpmasters to remove any mips64el binaries from > unstable when excluding it for the package, if you have not done so > already. Thanks for the reminder. The mips64el RM request is Bug#1014274 and seeing that autopkgtest seems to succeed now I'm closing this bug. --Daniel
Bug#1008718: src:yosys: fails to migrate to testing for too long: FTBFS on mips64el and s390x & autopkgtest regression
Hi Paul, On Thu, Mar 31, 2022 at 10:06:24AM +0200, Paul Gevers wrote: > The Release Team considers packages that are out-of-sync between testing and > unstable for more than 60 days as having a Release Critical bug in testing > [1]. Your package src:yosys has been trying to migrate for 61 days [2]. > Hence, I am filing this bug. Your latest upload failed to build from source > on mips64el and s390x where it built successfully in the past. The latest > upload also caused autopgktest regression on all architectures. Getting myself a porterbox guest account just took ages, I'm on it now :) > If you believe your package is unable to migrate to testing due to issues > beyond your control, don't hesitate to contact the Release Team. It seems to me berkeley-abc is to blame for most yosys test suite failures and particularly the s390x one that's blocking migration. Apparently it has major problems on big-endian architectures that aren't easily fixed: https://github.com/YosysHQ/yosys/issues/2645 How would I go about documenting and excluding s390x from building yosys and is there anything I need to do about the non-offical Debian ports architectures or can I just let those builds fail without it affecting yosys' migration? Thanks, --Daniel signature.asc Description: PGP signature
Bug#1004212: closing 1004212
close 1004212 1.01+20211229git48498af+dfsg-2 thanks Fixe by https://salsa.debian.org/science-team/berkeley-abc/-/commit/cf6ed6eb2ce4b9ea0494d4d145f8bc1a6d47d2f5 Thanks, --Daniel
Bug#1003984: [Pkg-electronics-devel] Bug#1003984: fpga-icestorm: binary-all FTBFS
Hi Adrian,
Thanks for the report.
On Wed, Jan 19, 2022 at 01:04:27AM +0200, Adrian Bunk wrote:
> https://buildd.debian.org/status/logs.php?pkg=fpga-icestorm&arch=all
>
> ...
>debian/rules override_dh_install
> make[1]: Entering directory '/<>'
> dh_install
> cd debian/fpga-icestorm/usr/share/fpga-icestorm/python/ && \
> find . -type f -print0 | xargs -0 -n1 -I{} rm ../../../bin/{}
> /bin/sh: 1: cd: can't cd to
> debian/fpga-icestorm/usr/share/fpga-icestorm/python/
> make[1]: *** [debian/rules:25: override_dh_install] Error 2
Fixed on salsa in[1], I'm just waiting for a sponsored upload.
[1]:
https://salsa.debian.org/electronics-team/fpga-icestorm/-/commit/bd60e6882085d2713e46c0d822ad974852a64266
--Daniel
signature.asc
Description: PGP signature
Bug#815363: ola: build-depends on libslp-dev
Package: ola Version: 0.9.8-1 Followup-For: Bug #815363 According to OLA's NEWS file the dependency on SLP was removed in version 0.9.4: "Remove the SLP code since it's no longer required for E1.33.". I tried building the ola package after removing the depency on libslp-dev and it seems to build and work just fine. --Daniel -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.6.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages ola depends on: ii adduser 3.115 ii libc6 2.22-13 ii libftdi10.20-4 ii libgcc1 1:6.1.1-8 ii libncurses5 6.0+20160319-2+b1 ii libola1 0.9.8-1 ii libprotobuf9v5 2.6.1-2 ii libstdc++6 6.1.1-8 ii libtinfo5 6.0+20160319-2+b1 ii libusb-0.1-42:0.1.12-30 ola recommends no packages. Versions of packages ola suggests: ii bash-completion 1:2.1-4.3 -- no debconf information
