Your message dated Sun, 05 Jun 2022 05:18:58 +
with message-id
and subject line Bug#997466: fixed in texext 0.6.7-1
has caused the Debian Bug report #997466,
regarding texext: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i
python{version} -p 3.9 returned exit code 13
to be
Control: tag -1 pending
Hello,
Bug #997466 in texext reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Processing control commands:
> tag -1 pending
Bug #997466 [src:texext] texext: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.9 returned exit code 13
Added tag(s) pending.
--
997466: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997466
Debian Bug Tracking
Processing commands for cont...@bugs.debian.org:
> severity 1012083 important
Bug #1012083 [src:quickfix] quickfix FTBFS on riscv64
Severity set to 'important' from 'serious'
> user debian-ri...@lists.debian.org
Setting user to debian-ri...@lists.debian.org (was ab.bea...@gmail.com).
> usertags
Processing commands for cont...@bugs.debian.org:
> severity 1012181 important
Bug #1012181 [src:ldc] ldc ftbfs on riscv64
Severity set to 'important' from 'serious'
> user debian-ri...@lists.debian.org
Setting user to debian-ri...@lists.debian.org (was ab.bea...@gmail.com).
> usertags 1012181 +
Processing control commands:
> severity -1 important
Bug #1012077 [linuxinfo] linuxinfo FTBFS on riscv64
Severity set to 'important' from 'serious'
--
1012077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012077
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: severity -1 important
On Sun, 29 May 2022 14:45:29 -0400 Alan Beadle wrote:
> Package: linuxinfo
> Severity: serious
> Tags: ftbfs patch upstream
> Justification: fails to build from source
...
> linuxinfo currently fails to build on riscv64
Please note that FTBFS bugs on unofficial
Control: tags -1 = moreinfo unreproducible
Hi Lucas,
Thank you for reaching out. I've been looking into this report and am a
bit confused. I'm trying to reproduce it on my laptop, but it builds just
fine for me. Can you please help me understand why it would fail on your
end?
--
regards,
Processing control commands:
> tags -1 = moreinfo unreproducible
Bug #1011875 [src:golang-github-opencontainers-runtime-tools]
golang-github-opencontainers-runtime-tools: FTBFS: dh_auto_test: error: cd
obj-x86_64-linux-gnu && go test -vet=off -v -p 8
Processing commands for cont...@bugs.debian.org:
> tags 1006505 + fixed-upstream
Bug #1006505 [src:libsecp256k1] libsecp256k1: FTBFS with OpenSSL 3.0
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1006505:
Your message dated Sat, 04 Jun 2022 23:20:06 +
with message-id
and subject line Bug#1006127: fixed in wireless-regdb 2022.04.08-1
has caused the Debian Bug report #1006127,
regarding wireless-regdb stable policy
to be marked as done.
This means that you claim that the problem has been dealt
On Sat, 04 Jun 2022 14:54:12 +0200, Axel Beckert wrote:
> I also checked what close() returns. It is actually "undef". Also
> IO::Socket::SSL does not document any return value for close(). So the
> return code is actually not meant to mean anything.
Thanks for investigating this further!
>
Package: librust-rusty-fork-dev
Version: 0.2.1-1+b1
Severity: grave
Justification: renders package unusable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
- Jonas
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmKbwB4ACgkQLHwxRsGg
Your message dated Sat, 04 Jun 2022 19:34:16 +
with message-id
and subject line Bug#1012169: fixed in cataclysm-dda 0.F-3-4
has caused the Debian Bug report #1012169,
regarding cataclysm-dda: test-game intermittently fails with various different
messages
to be marked as done.
This means
Thanks for the report. I can't reproduce this, though.
The code in question is this:
/*
* Get the host name and its IP address. Convert the IP address to
dotted
* ASCII form.
*/
if (gethostname(hnm, sizeof(hnm) - 1)) {
cem = "ERROR!!! can't get this host's name";
goto
Source: dcm2niix
Version: 1.0.20211006-4
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always
Dear maintainer(s),
You recently added an autopkgtest to your package dcm2niix, great.
However, it fails on s390x. Currently this failure is blocking the
migration to testing
tisdag 31 maj 2022 kl. 16:11:03 CEST skrev Trent W. Buck:
> https://sources.debian.org/src/prayer/1.3.5-dfsg1-8/session/html_secure_tid
> y.c/#L274-L334
> https://api.html-tidy.org/tidy/tidylib_api_5.8.0/group__parser__h.html#ga46
> 769d54f0a1bcfd801d60c34eb563e7
>
> Is it sufficient to simply
Processing commands for cont...@bugs.debian.org:
> notfound 1012125 astroquery/0.4.1+dfsg-7
Bug #1012125 {Done: Vincent Prat } [src:astroquery]
astroquery: Autopkgtests failure due to trying to write to /usr/lib
No longer marked as found in versions astroquery/0.4.1+dfsg-7.
>
End of message,
Your message dated Sat, 04 Jun 2022 14:50:23 +
with message-id
and subject line Bug#1012120: fixed in libwww-dict-leo-org-perl 2.02-3
has caused the Debian Bug report #1012120,
regarding libwww-dict-leo-org-perl: does not connect anymore
to be marked as done.
This means that you claim that
Processing control commands:
> tag -1 pending
Bug #1012120 [libwww-dict-leo-org-perl] libwww-dict-leo-org-perl: does not
connect anymore
Ignoring request to alter tags of bug #1012120 to the same tags previously set
--
1012120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012120
Debian
Control: tag -1 pending
Hello,
Bug #1012120 in libwww-dict-leo-org-perl reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Hello Alan,
On Sat, Jun 04, 2022 at 08:52:40AM -0400, Alan Beadle wrote:
> It looks like this will always be a complex issue on RISC-V since
> there is such a variety of manufacturers. However I think the
> following would be the best approach.
>
> First, if there is a uarch field, use that since
Control: tag -1 + pending
Hi,
just run into this, too.
gregor herrmann wrote:
> Control: tag + confirmed bookworm sid
Indeed, it still works on Debian 11 Bullseye, so it is clearly no
change on the server side. (Which is reverse-proxied at Cloudflare
and Cloudflare known to be quite easy on
Processing control commands:
> tag -1 + pending
Bug #1012120 [libwww-dict-leo-org-perl] libwww-dict-leo-org-perl: does not
connect anymore
Added tag(s) pending.
--
1012120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012120
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Hi Helge,
It looks like this will always be a complex issue on RISC-V since
there is such a variety of manufacturers. However I think the
following would be the best approach.
First, if there is a uarch field, use that since it will describe the
design of the cores present, such as Sifive's
❦ 3 June 2022 20:48 +02, Salvatore Bonaccorso:
> close 1012275 101.0-1
Unfortunately, Firefox is not buildable due to depending on a version of
Cargo not available in unstable.
--
Don't diddle code to make it faster - find a better algorithm.
- The Elements of Programming Style
On Mon, 23 May 2022 01:00:26 +0300 Adrian Bunk wrote:
The segmentation fault looks fixed with the dependencies rebuilt with
OpenSSL 3.0, but the test still fails:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/xmltooling.html
You can find the explanation for the tests
Hello Alan,
hello Bo,
hello Xiao,
hello Tienhock,
I have preliminary support for riscv now locally. However, there is a
design question:
How would you put riscv processors into families? On x86, thats done
be vendor and some marketing label ("AMD" and "Ryzen"). On Alpha,
that's the model (i.e.
Thanks Bastian!
On Sat, Jun 04, 2022 at 01:46:49PM +0200, Bastian Germann wrote:
>Ubuntu has the patches to fix this and another OpenSSL 3.0 error.
>I have attached the debdiff that I have just uploaded to DELAYED/10.
>diff -Nru sbsigntool-0.9.4/debian/changelog sbsigntool-0.9.4/debian/changelog
Ubuntu has the patches to fix this and another OpenSSL 3.0 error.
I have attached the debdiff that I have just uploaded to DELAYED/10.diff -Nru sbsigntool-0.9.4/debian/changelog sbsigntool-0.9.4/debian/changelog
--- sbsigntool-0.9.4/debian/changelog 2021-09-14 06:39:01.0 +
+++
Your message dated Sat, 04 Jun 2022 11:04:55 +
with message-id
and subject line Bug#1008776: fixed in intel-media-driver 22.4.2+dfsg1-2
has caused the Debian Bug report #1008776,
regarding intel-media-va-driver: Segmentation fault with gstreamer based
applications
to be marked as done.
This
Processing commands for cont...@bugs.debian.org:
> retitle 1000932 Please upgrade to llvm-toolchain-13 or 14
Bug #1000932 [src:doxygen] doxygen: Please upgrade to llvm-toolchain-12 or 13
Changed Bug title to 'Please upgrade to llvm-toolchain-13 or 14' from 'doxygen:
Please upgrade to
Processing commands for cont...@bugs.debian.org:
> found 1006511 5.9.1+dfsg-2
Bug #1006511 [src:net-snmp] net-snmp: FTBFS with OpenSSL 3.0
The source 'net-snmp' and version '5.9.1+dfsg-2' do not appear to match any
binary packages
Marked as found in versions net-snmp/5.9.1+dfsg-2.
>
End of
Processing control commands:
> forwarded -1 https://github.com/bitcoin-core/secp256k1/pull/983
Bug #1006505 [src:libsecp256k1] libsecp256k1: FTBFS with OpenSSL 3.0
Set Bug forwarded-to-address to
'https://github.com/bitcoin-core/secp256k1/pull/983'.
--
1006505:
Control: forwarded -1 https://github.com/bitcoin-core/secp256k1/pull/983
The failing tests are now dropped. Please just import a newer version.
Processing commands for cont...@bugs.debian.org:
> fixed 1006022 5.6.4-1
Bug #1006022 [src:puma] puma: flaky tests
Marked as fixed in versions puma/5.6.4-1.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
1006022:
Your message dated Sat, 04 Jun 2022 10:03:54 +
with message-id
and subject line Bug#1012022: fixed in fenics-basix 0.4.2-1exp2
has caused the Debian Bug report #1012022,
regarding fenics-basix: FTBFS during separate binary-indep build
to be marked as done.
This means that you claim that the
The last release which contained petri-foo was stretch and upstream is going
nowhere.
I suggest to file a RM bug and if nobody reacts on this I am going to file one
in a month.
Your message dated Sat, 04 Jun 2022 09:34:44 +
with message-id
and subject line Bug#1011807: fixed in twitter-bootstrap4 4.6.1+dfsg1-2
has caused the Debian Bug report #1011807,
regarding twitter-bootstrap4: FTBFS: make[1]: *** [debian/rules:13:
override_dh_auto_build] Error 1
to be marked
Your message dated Sat, 4 Jun 2022 11:32:44 +0200
with message-id
and subject line Re: petri-foo: License incompatibility: links with OpenSSL
has caused the Debian Bug report #907691,
regarding petri-foo: License incompatibility: links with OpenSSL
to be marked as done.
This means that you claim
Control: tag -1 pending
Hello,
Bug #1011807 in twitter-bootstrap4 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Processing control commands:
> tag -1 pending
Bug #1011807 [src:twitter-bootstrap4] twitter-bootstrap4: FTBFS: make[1]: ***
[debian/rules:13: override_dh_auto_build] Error 1
Added tag(s) pending.
--
1011807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011807
Debian Bug Tracking System
Your message dated Sat, 04 Jun 2022 11:10:04 +0200
with message-id <0fbe05e56c699b78bd9fb9b2098d4...@debian.org>
and subject line Re: Bug#1012252: debhelper: execute_after not executed for
binary-indep build
has caused the Debian Bug report #1012252,
regarding debhelper: execute_after not
Source: python-jenkinsapi
Version: 0.3.11-5
Severity: serious
Usertags: edos-uninstallable
Hi, python-jenkinsapi build-depends on pylint3 but that package only
exists in stable and older stable releases.
-Ralf.
Processing control commands:
> tags -1 moreinfo
Bug #1012252 [debhelper] debhelper: execute_after not executed for binary-indep
build
Added tag(s) moreinfo.
--
1012252: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012252
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Control: tags -1 moreinfo
Drew Parsons:
> Package: debhelper
> Version: 13.7.1
> Severity: Serious
> Justification: FTBFS
> Control: block 1012022 by -1
>
> fenics-basix 0.4.2-1exp1 is currently failing to build in a
> binary-indep build, see
>
Processing control commands:
> tags -1 moreinfo
Bug #1012252 [debhelper] debhelper: execute_after not executed for binary-indep
build
Ignoring request to alter tags of bug #1012252 to the same tags previously set
--
1012252: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012252
Debian Bug
Processing control commands:
> block 1011807 by -1
Bug #1011807 [src:twitter-bootstrap4] twitter-bootstrap4: FTBFS: make[1]: ***
[debian/rules:13: override_dh_auto_build] Error 1
1011807 was not blocked by any bugs.
1011807 was not blocking any bugs.
Added blocking bug(s) of 1011807: 1012324
--
Your message dated Sat, 04 Jun 2022 09:09:11 +0200
with message-id <363ebdfb34e00c9effad54c8c364a...@debian.org>
and subject line (pas d'objet)
has caused the Debian Bug report #1009391,
regarding pytango: FTBFS: TypeError: entry_points() got an unexpected keyword
argument 'group'
to be marked as
Your message dated Sat, 04 Jun 2022 07:03:51 +
with message-id
and subject line Bug#1010408: fixed in golang-github-evanw-esbuild 0.14.36-1
has caused the Debian Bug report #1010408,
regarding ftbfs: Error: Failed to find "global.fs = fs;" in Go JS shim code
to be marked as done.
This means
Your message dated Sat, 04 Jun 2022 07:03:56 +
with message-id
and subject line Bug#1011795: fixed in node-fastcgi 1.3.3-7
has caused the Debian Bug report #1011795,
regarding node-fastcgi: FTBFS: dh_auto_test: error: /bin/sh -ex
debian/tests/pkg-js/test returned exit code 2
to be marked as
Hi Jérémy,
Thank you for your report!
On Sat, Apr 30, 2022 at 2:39 PM Jérémy Lal wrote:
> Source: golang-github-evanw-esbuild
> Version: 0.14.25-1
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the
past)
>
> your package FTBFS, however a
52 matches
Mail list logo