Bug#1031114: jquery-timepicker: autopkgtest failures
On Sun, Feb 12 2023 at 02:42:12 AM +0100, William Desportes
wrote:
I think this has nothing to do with my package :)
selenium.common.exceptions.WebDriverException: Message: unknown
error: unable to discover open pages
And this should be enough to reproduce it (deps: python3-selenium,
chromium-driver):
from selenium import webdriver
from selenium.webdriver.support.wait import WebDriverWait
from selenium.webdriver.common.by import By
import os
data_dir = os.getenv('AUTOPKGTEST_TMP', default='/tmp') +
'/google-chrome'
options = webdriver.ChromeOptions()
options.add_argument('--headless')
options.add_argument('--no-sandbox')
options.add_argument('--headless')
options.add_argument('--disable-gpu')
options.add_argument('--disable-dev-shm-usage')
options.add_argument('--profile-directory=Default')
options.add_argument('--user-data-dir=' + data_dir)
driver = webdriver.Chrome(options=options)
print("Running tests")
driver.get("http://localhost:/SpecRunner.html?random=false;)
Let me know if you can reproduce this WebDriverException
I don't get a successful test with chromium 109 in a bookworm virtual
box. I haven't used selenium before and I'm not sure what this is
supposed to look like..
dilinger@debian:~$ python3 ./test.py
Running tests
Traceback (most recent call last):
File "/home/dilinger/./test.py", line 19, in
driver.get("http://localhost:/SpecRunner.html?random=false;)
File
"/usr/lib/python3/dist-packages/selenium/webdriver/remote/webdriver.py",
line 449, in get
self.execute(Command.GET, {"url": url})
File
"/usr/lib/python3/dist-packages/selenium/webdriver/remote/webdriver.py",
line 440, in execute
self.error_handler.check_response(response)
File
"/usr/lib/python3/dist-packages/selenium/webdriver/remote/errorhandler.py",
line 245, in check_response
raise exception_class(message, screen, stacktrace)
selenium.common.exceptions.WebDriverException: Message: unknown error:
net::ERR_CONNECTION_REFUSED
(Session info: headless chrome=109.0.5414.119)
Stacktrace:
#0 0x562fe7b45c53
#1 0x562fe78f902c
#2 0x562fe78f286c
#3 0x562fe78e6d77
#4 0x562fe78e8391
#5 0x562fe78e70fe
#6 0x562fe78e62a5
#7 0x562fe78e612f
#8 0x562fe78e5074
#9 0x562fe78e543b
#10 0x562fe78fb60b
#11 0x562fe796be08
#12 0x562fe79544c2
#13 0x562fe796ba13
#14 0x562fe7954283
#15 0x562fe792675b
#16 0x562fe7927bf2
#17 0x562fe7b8bd9d
#18 0x562fe7b8e151
#19 0x562fe7b8db00
#20 0x562fe7b8e8b5
#21 0x562fe7b795a6
#22 0x562fe7b8ec33
#23 0x562fe7b6b8e0
#24 0x562fe7ba8835
#25 0x562fe7ba89da
#26 0x562fe7bc288f
#27 0x7fed246a7fd4
Bug#1031114: jquery-timepicker: autopkgtest failures
I think this has nothing to do with my package :)
selenium.common.exceptions.WebDriverException: Message: unknown error:
unable to discover open pages
And this should be enough to reproduce it (deps: python3-selenium,
chromium-driver):
from selenium import webdriver
from selenium.webdriver.support.wait import WebDriverWait
from selenium.webdriver.common.by import By
import os
data_dir = os.getenv('AUTOPKGTEST_TMP', default='/tmp') +
'/google-chrome'
options = webdriver.ChromeOptions()
options.add_argument('--headless')
options.add_argument('--no-sandbox')
options.add_argument('--headless')
options.add_argument('--disable-gpu')
options.add_argument('--disable-dev-shm-usage')
options.add_argument('--profile-directory=Default')
options.add_argument('--user-data-dir=' + data_dir)
driver = webdriver.Chrome(options=options)
print("Running tests")
driver.get("http://localhost:/SpecRunner.html?random=false;)
Let me know if you can reproduce this WebDriverException
Processed: Re: tomcat10: Catalina won't deploy applications missing class jakarta.websocket.DeploymentException
Processing control commands: > tags -1 pending Bug #1030869 [tomcat10] tomcat10: Catalina won't deploy applications missing class jakarta.websocket.DeploymentException Added tag(s) pending. -- 1030869: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030869 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1030869: tomcat10: Catalina won't deploy applications missing class jakarta.websocket.DeploymentException
Control: tags -1 pending On Wed, 08 Feb 2023 11:38:25 -0500 Jorge Moraleda wrote: > Package: tomcat10 > Version: 10.1.5-1 > Severity: grave > Justification: renders package unusable > X-Debbugs-Cc: jorge.moral...@gmail.com > > Dear Maintainer, > > Catalina is unable to deploy any applications (including samplp ROOT) > complaining of java.lang.ClassNotFoundException: > jakarta.websocket.DeploymentException Thanks for the report! I believe I have found the root cause for this Exception. Apparently upstream split the websocket API into two jar files in version 10.1.x but only one was linked into the correct location. I will upload a new revision shortly. Regards, Markus signature.asc Description: This is a digitally signed message part
Bug#1031114: jquery-timepicker: autopkgtest failures
Source: jquery-timepicker Control: found -1 jquery-timepicker/1.6.3-3 Control: affects -1 chromium Severity: serious Tags: sid bookworm It would appear that jquery-timepicker's autopkgtests are failing with chromium. You can see some of the failures here: https://ci.debian.net/packages/j/jquery-timepicker/testing/amd64/ This is keeping chromium 110.0.5481.77-2 from migrating to testing. Please update your tests to use chromium v110. If it turns out that you're actually hitting a bug in chromium, please reassign this bug to chromium (ideally with a short snippet for reproducing it without having to run the entire test suite), and I'll investigate. A snippet from the test failure is below. Thanks, Andres autopkgtest [11:12:45]: test jasmine: [--- 2023-02-11 11:12:45: (server.c.1588) server started (lighttpd/1.4.67) Using chrome data dir: /tmp/autopkgtest-lxc.up3az_7k/downtmp/autopkgtest_tmp/google-chrome Traceback (most recent call last): File "/tmp/autopkgtest-lxc.up3az_7k/downtmp/build.zKa/src/./debian/tests/test-runner.py", line 18, in driver = webdriver.Chrome(options=options) ^ File "/usr/lib/python3/dist-packages/selenium/webdriver/chrome/webdriver.py", line 80, in __init__ super().__init__( File "/usr/lib/python3/dist-packages/selenium/webdriver/chromium/webdriver.py", line 104, in __init__ super().__init__( File "/usr/lib/python3/dist-packages/selenium/webdriver/remote/webdriver.py", line 286, in __init__ self.start_session(capabilities, browser_profile) File "/usr/lib/python3/dist-packages/selenium/webdriver/remote/webdriver.py", line 378, in start_session response = self.execute(Command.NEW_SESSION, parameters) ^ File "/usr/lib/python3/dist-packages/selenium/webdriver/remote/webdriver.py", line 440, in execute self.error_handler.check_response(response) File "/usr/lib/python3/dist-packages/selenium/webdriver/remote/errorhandler.py", line 245, in check_response raise exception_class(message, screen, stacktrace) selenium.common.exceptions.WebDriverException: Message: unknown error: unable to discover open pages Stacktrace: #0 0x562327ef29e3 #1 0x562327ca622c #2 0x562327cd044d #3 0x562327ccc597 #4 0x562327cc9218 #5 0x562327d0da10 #6 0x562327d047c3 #7 0x562327cd3593 #8 0x562327cd4b9b #9 0x562327f3c29d #10 0x562327f3ea34 #11 0x562327f3e30c #12 0x562327f3f285 #13 0x562327f28746 #14 0x562327f3f685 #15 0x562327f1a2d3 #16 0x562327f5b925 #17 0x562327f5baca #18 0x562327f75594 #19 0x7fe2f8f35fd4 Tests failed !
Processed: jquery-timepicker: autopkgtest failures
Processing control commands: > found -1 jquery-timepicker/1.6.3-3 Bug #1031114 [src:jquery-timepicker] jquery-timepicker: autopkgtest failures Marked as found in versions jquery-timepicker/1.6.3-3. > affects -1 chromium Bug #1031114 [src:jquery-timepicker] jquery-timepicker: autopkgtest failures Added indication that 1031114 affects chromium -- 1031114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031114 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1030941: librsb: build-depends unsatisfiable on armhf
On 09/02/2023 23:43, Michele Martone wrote: On 20230209@17:50, Peter Green wrote: Package: librsb Version: 1.3.0.2+dfsg-1 Tags: bookworm, sid Severity: serious Justification: rc policy - "packages must be buildable within the same release" User: debian...@lists.debian.org Usertags: edos-uninstallable librsb build-depends on coccinelle which appears to have been removed on armhf, presumablly because it fails to build with an out of memory error. This leaves your package in violation of the rc policy. In general in cases like this there are three possible ways forward, in roughly descending order of preference. 1. Fix the package you depend on so that it once again builds on all release architectures. 2. Modify your package to eliminate the build-dependency in question on architectures where it is not available. 3. Decide it is not reasonable to support your package on armhf and file a removal request with the ftp team. I do not know enough about your individual package to say which are feasible in your particular case. The coccinelle-based patch was there only for gcc-11, which had a bug in -O3 and generated buggy code. So if one is sure to build with a different compiler thant gcc-11, one can drop the coccinelle patch. Otherwise one can remedy by using '-O3 -fno-tree-loop-vectorize' instead of '-O3'. Is it safe to assume gcc-11 is *not* being used? It should be safe, but I would suggest adding a build-dependency on gcc (>= 12) to make sure the package is not inadvertently built in an out of date environment.
Processed: Debian bugs control
Processing commands for cont...@bugs.debian.org:
> retitle 1006529 mariadb: FTBFS on hppa: builds, but test suite crashes
> immediately, previously also main.func_json_notembedded crash and
> anon_inode:io_uring warning (regression from 10.11.1-3 with only 2/1021 tests
> failed and 10.5.12-1 all 792 tests passed)
Bug #1006529 [mariadb] mariadb: FTBFS on hppa: builds, but test suite crashes
immediately with "'aio write' returned OS error 0"), maybe io_uring related
Changed Bug title to 'mariadb: FTBFS on hppa: builds, but test suite crashes
immediately, previously also main.func_json_notembedded crash and
anon_inode:io_uring warning (regression from 10.11.1-3 with only 2/1021 tests
failed and 10.5.12-1 all 792 tests passed)' from 'mariadb: FTBFS on hppa:
builds, but test suite crashes immediately with "'aio write' returned OS error
0"), maybe io_uring related'.
> retitle 1029374 mariadb: FTBFS on ppc64: main.func_json_notembedded very long
> output and crash, also main.mysql_upgrade complains about mysql.proc column
> count (3/1031 tests failed, regression from 1:10.11.1-3 where all 1029 tests
> passed)
Bug #1029374 [src:mariadb] mariadb: FTBFS on ppc64: main.func_json_notembedded
very long output and crash
Changed Bug title to 'mariadb: FTBFS on ppc64: main.func_json_notembedded very
long output and crash, also main.mysql_upgrade complains about mysql.proc
column count (3/1031 tests failed, regression from 1:10.11.1-3 where all 1029
tests passed)' from 'mariadb: FTBFS on ppc64: main.func_json_notembedded very
long output and crash'.
> retitle 1030630 mariadb: FTBFS on sparc64: main.func_json_notembedded very
> long output and crash, anon_inode:io_uring warning (10/1026 tests failed, so
> far best result in all reviewed build logs for MariaDB 5.5-10.11)
Bug #1030630 [src:mariadb] mariadb: FTBFS on sparc64: /bin/sh: Bad address
Changed Bug title to 'mariadb: FTBFS on sparc64: main.func_json_notembedded
very long output and crash, anon_inode:io_uring warning (10/1026 tests failed,
so far best result in all reviewed build logs for MariaDB 5.5-10.11)' from
'mariadb: FTBFS on sparc64: /bin/sh: Bad address'.
> retitle 1030510 mariadb: FTBFS on s390x: builds, but test suite crashes
> randomly on different tests (regression from 10.11.1-1 with all 1028 passed)
Bug #1030510 [src:mariadb] mariadb: FTBFS on s390x: crash on munmap(),
Changed Bug title to 'mariadb: FTBFS on s390x: builds, but test suite crashes
randomly on different tests (regression from 10.11.1-1 with all 1028 passed)'
from 'mariadb: FTBFS on s390x: crash on munmap(),'.
> severity 1030510 important
Bug #1030510 [src:mariadb] mariadb: FTBFS on s390x: builds, but test suite
crashes randomly on different tests (regression from 10.11.1-1 with all 1028
passed)
Severity set to 'important' from 'serious'
> fixed 1030604 mariadb-10.6/1:10.6.11-2
Bug #1030604 {Done: Otto Kekäläinen } [src:mariadb,
src:mariadb-10.6] mariadb breaks mariadb-10.6 autopkgtest: Variable
'innodb_compression_algorithm' can't be set to the value of 'lz4'
Marked as fixed in versions mariadb-10.6/1:10.6.11-2.
> affects 1020831 mariadb/10.11.1-2
Bug #1020831 [src:linux] linux-signed-arm64: iouring tmpfs pwrite returns 125
error sporadically
Added indication that 1020831 affects mariadb/10.11.1-2
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1006529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006529
1020831: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020831
1029374: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029374
1030510: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030510
1030604: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030604
1030630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030630
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#965734: marked as done (mrtg-rrd: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Sat, 11 Feb 2023 22:39:39 + with message-id and subject line Bug#1031067: Removed package(s) from unstable has caused the Debian Bug report #965734, regarding mrtg-rrd: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 965734: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965734 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mrtg-rrd Version: 0.7-5.1 Severity: normal Usertags: compat-5-6-removal Hi, The package mrtg-rrd uses debhelper with a compat level of 5 or 6, which is deprecated and scheduled for removal[1]. Please bump the debhelper compat at your earliest convenience /outside the freeze/! * Compat 13 is recommended (supported in stable-backports) * Compat 7 is the bare minimum PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads with compat bumps during the freeze. If there is any risk that the fix for this bug might not migrate to testing before 2021-01-01[3] then please postpone the fix until after the freeze. At the time of filing this bug, compat 5 and 6 are expected to be removed "some time during the development cycle of bookworm". Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2020/07/msg00065.html [2] https://release.debian.org/bullseye/FAQ.html [3] The choice of 2021-01-01 as a "deadline" is set before the actual freeze deadline to provide a safe cut off point for most people. Mind you, it is still your responsibility to ensure that the upload makes it into testing even if you upload before that date. --- End Message --- --- Begin Message --- Version: 0.7-5.1+rm Dear submitter, as the package mrtg-rrd has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1031067 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#799097: marked as done (mrtg-rrd: Regression after the fix for bug #787608.)
Your message dated Sat, 11 Feb 2023 22:39:39 +
with message-id
and subject line Bug#1031067: Removed package(s) from unstable
has caused the Debian Bug report #799097,
regarding mrtg-rrd: Regression after the fix for bug #787608.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
799097: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799097
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mrtg-rrd
Version: 0.7-5.1
Severity: grave
Tags: patch
Justification: renders package unusable
Dear Maintainer,
The fix for bug #787608 has left the package in an unusable state (the result
of the execution of mrtg-rrd.cgi is a blank page).
The cause is the blind removal of the defined function. At least in 3 of the 4
instances it should be replaced with exists. I don't know about the fourth
instance since I am not a Perl expert.
Please, see the proposed patch below. It should be applied instead of
no-defined-hash-array.patch, i.e. against the original source.
--- a/mrtg-rrd.cgi
+++ b/mrtg-rrd.cgi
@@ -496,7 +496,7 @@ sub common_args($$$)
{
my ($name, $target, $q) = @_;
- return @{$target->{args}} if defined @{$target->{args}};
+ return @{$target->{args}} if exists $target->{args};
my $noi = 1 if $target->{options}{noi};
my $noo = 1 if $target->{options}{noo};
@@ -521,7 +521,7 @@ sub common_args($$$)
$target->{rrd} = $dir . '/' . $tdir . $name . '.rrd';
%{$target->{options}} = ()
- unless defined %{$target->{options}};
+ unless %{$target->{options}};
$dir = $cfg->{workdir};
$dir = $cfg->{imagedir}
@@ -908,7 +908,7 @@ EOF
print $directories{$dir}{bodytag};
my $subdirs_printed;
- if (defined @{$directories{$dir}{subdir}}) {
+ if (exists $directories{$dir}{subdir}) {
$subdirs_printed = 1;
print
Bug#965474: marked as done (crossfire-maps-small: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Sat, 11 Feb 2023 22:36:51 + with message-id and subject line Bug#1031035: Removed package(s) from unstable has caused the Debian Bug report #965474, regarding crossfire-maps-small: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 965474: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965474 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: crossfire-maps-small Version: 1.5.0-3 Severity: normal Usertags: compat-5-6-removal Hi, The package crossfire-maps-small uses debhelper with a compat level of 5 or 6, which is deprecated and scheduled for removal[1]. Please bump the debhelper compat at your earliest convenience /outside the freeze/! * Compat 13 is recommended (supported in stable-backports) * Compat 7 is the bare minimum PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads with compat bumps during the freeze. If there is any risk that the fix for this bug might not migrate to testing before 2021-01-01[3] then please postpone the fix until after the freeze. At the time of filing this bug, compat 5 and 6 are expected to be removed "some time during the development cycle of bookworm". Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2020/07/msg00065.html [2] https://release.debian.org/bullseye/FAQ.html [3] The choice of 2021-01-01 as a "deadline" is set before the actual freeze deadline to provide a safe cut off point for most people. Mind you, it is still your responsibility to ensure that the upload makes it into testing even if you upload before that date. --- End Message --- --- Begin Message --- Version: 1.5.0-3.1+rm Dear submitter, as the package crossfire-maps-small has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1031035 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1030268: marked as pending in fparser
Hi Alastair On 2023-02-06 12:24:16 +, Alastair McKinstry wrote: > Control: tag -1 pending > > Hello, > > Bug #1030268 in fparser 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: > > https://salsa.debian.org/python-team/packages/fparser/-/commit/ca1a17bacfaa03b2075c375f4a9675d6f89c10e3 > > > Changes to d/rules from Sebastian Ramacher to build on all pyvers Closes: > #1030268 > Thanks for applying the patch. As we are trying to finish the python3.11-only transition, could you please upload this change? Cheers -- Sebastian Ramacher
Processed: tagging 1028625
Processing commands for cont...@bugs.debian.org:
> tags 1028625 + pending
Bug #1028625 {Done: Paul Gevers } [src:x-loader]
src:x-loader: fails to migrate to testing for too long: FTBFS
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1028625: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028625
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1030510: Info received (Bug#1030510: Info received (Bug#1030510: Info received (mariadb: FTBFS on s390x: timeout)))
For the record, the failing Debian machines run: Linux ci-worker-s390x-01 5.10.0-21-s390x #1 SMP Debian 5.10.162-1 (2023-01-21) s390x GNU/Linux The passing Launchpad builders run: Linux bos02-s390x-013 5.4.0-137-generic #154-Ubuntu SMP Thu Jan 5 17:03:11 UTC 2023 s390x
Bug#1025125: closing 1025125
close 1025125 thanks
Processed: closing 1025125
Processing commands for cont...@bugs.debian.org: > close 1025125 Bug #1025125 [src:ruby-sinatra] ruby-sinatra: CVE-2022-45442: Reflected File Download attack Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1025125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025125 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1030510: Info received (Bug#1030510: Info received (Bug#1030510: Info received (mariadb: FTBFS on s390x: timeout)))
Hi, On 11-02-2023 22:41, Andrew Hutchings wrote: On 11/02/2023 20:17, Paul Gevers wrote: Well, the buildd's don't run bookworm, but they run stable (which currently is bullseye). Sorry, I was told this was Bookworm blocker when this was emailed to me, not a Bullseye one. That is true. But Debian build infrastructure runs stable and the build happens in a schroot (if I recall correctly). If the intention is to release 10.11 for Bookworm, surely that is what should be tested? Given that the entire underlying base kernal and OS will be different? I see your point, but the kernel is nearly always different anyways between the moment you use a build artifact and the moment it's build. That's how binary distributions work. Obviously ideally we should have the same kernel during testing, but at this moment the infrastructure uses lxc (giving you the same OS, but a different kernel) and the host runs stable. Or is the intention to release update Bullseye to have 10.11? No. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1030510: Info received (Bug#1030510: Info received (Bug#1030510: Info received (mariadb: FTBFS on s390x: timeout)))
Hi Paul, On 11/02/2023 20:17, Paul Gevers wrote: Well, the buildd's don't run bookworm, but they run stable (which currently is bullseye). Sorry, I was told this was Bookworm blocker when this was emailed to me, not a Bullseye one. If the intention is to release 10.11 for Bookworm, surely that is what should be tested? Given that the entire underlying base kernal and OS will be different? Or is the intention to release update Bullseye to have 10.11? Kind Regards -- Andrew (LinuxJedi) Hutchings Chief Contributions Officer MariaDB Foundation
Bug#1031108: kotlin: FTBFS (Build failed with an exception)
Package: src:kotlin Version: 1.3.31+~1.0.1+~0.11.12-5 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in bookworm, your package failed to build: [...] debian/rules binary-indep dh binary-indep --buildsystem=gradle --with-maven-repo-helper dh_update_autotools_config -i -O--buildsystem=gradle -O--with-maven-repo-helper dh_autoreconf -i -O--buildsystem=gradle -O--with-maven-repo-helper dh_auto_configure -i -O--buildsystem=gradle -O--with-maven-repo-helper debian/rules override_dh_auto_build make[1]: Entering directory '/<>' sed -e "s|__VERSION__|1.3.31|g" < debian/kotlin.poms.in > debian/kotlin.poms # Build atomicfu component dh_auto_build -- --project-dir=atomicfu -Dkotlin.compiler.execution.strategy=in-proces -Pkotlin_version=1.3.31 -Pversion=0.11.12 install mkdir -p .gradle/init.d cp /usr/share/gradle-debian-helper/init.gradle .gradle/init.d/ gradle --info --console plain --offline --stacktrace --no-daemon --refresh-dependencies --gradle-user-home .gradle -Duser.home=. -Duser.name=debian -Ddebian.package=kotlin -Dfile.encoding=UTF-8 --project-dir=atomicfu -Dkotlin.compiler.execution.strategy=in-proces -Pkotlin_version=1.3.31 -Pversion=0.11.12 install openjdk version "17.0.6" 2023-01-17 [... snipped ...] Skipping task ':compiler:backend.jvm:processResources' as it has no source files and no previous output files. :compiler:backend.jvm:processResources NO-SOURCE :compiler:backend.jvm:processResources (Thread[Daemon worker,5,main]) completed. Took 0.0 secs. :compiler:backend.jvm:classes (Thread[Daemon worker,5,main]) started. :compiler:backend.jvm:classes Skipping task ':compiler:backend.jvm:classes' as it has no actions. :compiler:backend.jvm:classes (Thread[Daemon worker,5,main]) completed. Took 0.0 secs. :compiler:backend.jvm:debianMavenPom (Thread[Daemon worker,5,main]) started. :compiler:backend.jvm:debianMavenPom Putting task artifact state for task ':compiler:backend.jvm:debianMavenPom' into context took 0.0 secs. Up-to-date check for task ':compiler:backend.jvm:debianMavenPom' took 0.0 secs. It is not up-to-date because: No history is available. Generating pom file /<>/compiler/ir/backend.jvm/build/debian/backend.jvm.pom :compiler:backend.jvm:debianMavenPom (Thread[Daemon worker,5,main]) completed. Took 0.021 secs. :compiler:backend.jvm:inspectClassesForKotlinIC (Thread[Daemon worker,5,main]) started. :compiler:backend.jvm:inspectClassesForKotlinIC Putting task artifact state for task ':compiler:backend.jvm:inspectClassesForKotlinIC' into context took 0.0 secs. Up-to-date check for task ':compiler:backend.jvm:inspectClassesForKotlinIC' took 0.004 secs. It is not up-to-date because: No history is available. :compiler:backend.jvm:inspectClassesForKotlinIC (Thread[Daemon worker,5,main]) completed. Took 0.009 secs. :compiler:backend.jvm:jar (Thread[Daemon worker,5,main]) started. :compiler:backend.jvm:jar Putting task artifact state for task ':compiler:backend.jvm:jar' into context took 0.0 secs. Up-to-date check for task ':compiler:backend.jvm:jar' took 0.004 secs. It is not up-to-date because: No history is available. :compiler:backend.jvm:jar (Thread[Daemon worker,5,main]) completed. Took 0.049 secs. :core:descriptors.runtime:compileKotlin (Thread[Daemon worker,5,main]) started. :core:descriptors.runtime:compileKotlin Putting task artifact state for task ':core:descriptors.runtime:compileKotlin' into context took 0.0 secs. file or directory '/<>/core/descriptors.runtime/src/main/kotlin', not found file or directory '/<>/core/descriptors.runtime/src/main/java', not found file or directory '/<>/core/descriptors.runtime/src/main/kotlin', not found file or directory '/<>/core/descriptors.runtime/src/main/java', not found Up-to-date check for task ':core:descriptors.runtime:compileKotlin' took 0.008 secs. It is not up-to-date because: No history is available. All input files are considered out-of-date for incremental task ':core:descriptors.runtime:compileKotlin'. file or directory '/<>/core/descriptors.runtime/src/main/kotlin', not found file or directory '/<>/core/descriptors.runtime/src/main/java', not found file or directory '/<>/core/descriptors.runtime/src/main/kotlin', not found file or directory '/<>/core/descriptors.runtime/src/main/java', not found Using Kotlin/JVM incremental compilation java.lang.UnsatisfiedLinkError: 'int org.jetbrains.kotlin.org.fusesource.jansi.internal.CLibrary.isatty(int)' at org.jetbrains.kotlin.org.fusesource.jansi.internal.CLibrary.isatty(Native Method) at org.jetbrains.kotlin.cli.common.messages.PlainTextMessageRenderer.(PlainTextMessageRenderer.java:42) at org.jetbrains.kotlin.cli.common.messages.MessageRenderer.(MessageRenderer.java:31) at org.jetbrains.kotlin.cli.common.CLITool.exec(CLITool.kt:42) at
Bug#1030545: qemu: qemu-img and qemu-system-s390x hang on s390x
Hi, On Sat, 11 Feb 2023 20:18:57 + James Addison wrote: Source: qemu Followup-For: Bug #1030545 For anyone else looking into this bug: it seemed to me that 'qcow2.c' is a likely candidate for this infinite looping[1] behaviour to originate from. The fact that metadata preallocation is enabled when it occurs could be relevant information too. (my guess is that it is _not_ a kernel-related regression, but I could be wrong about that) [1] - https://gitlab.com/qemu-project/qemu/-/blob/v7.2.0/block.c#L574-576 Cross posting what I just posted to bug #1030510 (FTBFS of mariadb on s390x). I'm absolutely not claiming anything, but two recent bugs where the kernel *might* be involved is too much coincidence in my book. I am seeing something weird on ci.debian.net too, which also runs stable. I upgraded the systems several days ago which pulled in a new security kernel. Since then I'm seeing that mariadb fails to install on s390x in tests because the install of mariadb-server-10.6 (1:10.6.11-2 testing) or mariadb-server (1:10.11.1-4 unstable) times out. root@ci-worker-s390x-01:~# uname -a Linux ci-worker-s390x-01 5.10.0-21-s390x #1 SMP Debian 5.10.162-1 (2023-01-21) s390x GNU/Linux See the recent tmpfails e.g. here: https://ci.debian.net/packages/d/dbconfig-common/testing/s390x/ https://ci.debian.net/packages/b/bacula/testing/s390x/ https://ci.debian.net/packages/d/django-reversion/testing/s390x/ Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1009261: bug 1009261 is forwarded to https://bugs.webkit.org/show_bug.cgi?id=202363
On Sat, 2023-02-11 at 22:03 +0200, Adrian Bunk wrote: > On Sat, Feb 11, 2023 at 11:46:56AM -0800, Diane Trout wrote: > > forwarded 1009261 https://bugs.webkit.org/show_bug.cgi?id=202363 > > thanks > > If this was the problem, then this bug is a duplicate of #986218 that > was fixed in oldstable/stable/unstable in September. The bug reports certainly look similar to me
Bug#1009261: closing 1009261
close 1009261 3.46.3-1 thanks I forgot to specify which evolution version I tested works. It may have been fixed a bit earlier than 3.46.3, but it looks like the full fix was somewhere around 3.4x. Diane
Processed: closing 1009261
Processing commands for cont...@bugs.debian.org:
> close 1009261 3.46.3-1
Bug #1009261 {Done: Diane Trout } [evolution] evolution:
Evolution bwrap problem - may fail to print or hang in startup
Marked as fixed in versions evolution/3.46.3-1.
Bug #1009261 {Done: Diane Trout } [evolution] evolution:
Evolution bwrap problem - may fail to print or hang in startup
Bug 1009261 is already marked as done; not doing anything.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1009261: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009261
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1031078: marked as done (qt6-speech-dev: library libqtexttospeech_mock.so referenced but not provided)
Your message dated Sat, 11 Feb 2023 20:36:58 + with message-id and subject line Bug#1031078: fixed in qt6-speech 6.4.2-3 has caused the Debian Bug report #1031078, regarding qt6-speech-dev: library libqtexttospeech_mock.so referenced but not provided to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1031078: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031078 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: qt6-speech-dev Version: 6.4.2-2 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 When I try to build a project containing this line: find_package(Qt6 COMPONENTS TextToSpeech REQUIRED) The configure fails like this: CMake Error at /usr/lib/x86_64-linux-gnu/cmake/Qt6TextToSpeech/Qt6QTextToSpeechMockPluginTargets.cmake:96 (message): The imported target "Qt6::QTextToSpeechMockPlugin" references the file "/usr/lib/x86_64-linux-gnu/qt6/plugins/texttospeech/libqtexttospeech_mock.so" but this file does not exist. Possible reasons include: * The file was deleted, renamed, or moved to another location. * An install or uninstall procedure did not complete successfully. * The installation package was faulty and contained "/usr/lib/x86_64-linux-gnu/cmake/Qt6TextToSpeech/Qt6QTextToSpeechMockPluginTargets.cmake" but not all the files it references. Call Stack (most recent call first): /usr/lib/x86_64-linux-gnu/cmake/Qt6TextToSpeech/Qt6QTextToSpeechMockPluginConfig.cmake:61 (include) /usr/lib/x86_64-linux-gnu/cmake/Qt6/QtPublicPluginHelpers.cmake:439 (include) /usr/lib/x86_64-linux-gnu/cmake/Qt6TextToSpeech/Qt6TextToSpeechPlugins.cmake:5 (__qt_internal_include_plugin_packages) /usr/lib/x86_64-linux-gnu/cmake/Qt6TextToSpeech/Qt6TextToSpeechConfig.cmake:133 (include) /usr/lib/x86_64-linux-gnu/cmake/Qt6/Qt6Config.cmake:167 (find_package) plugins/speech/CMakeLists.txt:22 (find_package) Concretely, the pacakge I try to build is hyperborg, available here: https://salsa.debian.org/tinker-team/hyperborg - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmPnXJUACgkQLHwxRsGg ASG3mQ//b0L2GLW6AxJRB9JBKDxulflFHv8BWDGVwS3Yn1FYH3kgLlRonhf6UHAY Hsi5dHTcHbOSL4sArtKslurfzPDOBMvtpHfuf5oGni1WVeQghFMd0kMp7ggGxTRj s5XtZAQSQ/AjroL9VFXZTam4tHsf1o1pW+8niBTN7NdMiE7IaKrU9zvg7fjdYMdv vKi7TQ1NZ/QOnVHT0bKwwHpXcNRKPFWy49NyHBOVzNHTI4wv0+CffX0Wf2t2WNE8 EmlKDPi+VO4nKffF+m4madlmfp7ERGVa1OSmEs8kgEszC+2DQgQsHK5aRA91dqPq SqJH8N9Hm9oNxuoW7G1GQpeqjD4RwvmdXa6htBMlfl29QuO6X11SRtkmxgp7ZrCq GElYE61Z97+OduOhjb5AEIym0At5q4BWnDVj341lQctIOAEBsImFuasDI1SCSH5/ Kvc1ac27whPt42pcqg0Xmo57f0m2i5LNO0RhHAALgw+e1ZUzUdmBffflFvVQKrM3 vEq6fLHicXP9MiKFLtEU1pCWp/iCWEWkoPqbcaMugAkDgqlp5hFbLsM/FppYFm1p IrsrhyYnTtrsZRJ0p23pxxGV1cRNDv6roq/Rev0pppuQnQVLOckZNca01otgfjaM MOuIV3YKJ8imBgeF1404z/wdhZrEJlPrSIdds6+lQJVtZ2tLqJg= =eV50 -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: qt6-speech Source-Version: 6.4.2-3 Done: Lisandro Damián Nicanor Pérez Meyer We believe that the bug you reported is fixed in the latest version of qt6-speech, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1031...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Lisandro Damián Nicanor Pérez Meyer (supplier of updated qt6-speech package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 11 Feb 2023 17:22:59 -0300 Source: qt6-speech Architecture: source Version: 6.4.2-3 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Lisandro Damián Nicanor Pérez Meyer Closes: 1031078 Changes: qt6-speech (6.4.2-3) unstable; urgency=medium . * Team upload. * Do not install plugins-related CMake files (Closes: #1031078). Thanks Jonas Smedegaard for the bug report. Checksums-Sha1: cc1fc2d4e3a6670900ed537a6cb119b2324c7a4d 2581 qt6-speech_6.4.2-3.dsc c3b67ff849301bf46241b459bc05de9e1139f390 5316 qt6-speech_6.4.2-3.debian.tar.xz b73ba851a2c07731fcd5e8f9ad0b3d181a696395 16794 qt6-speech_6.4.2-3_source.buildinfo Checksums-Sha256:
Bug#1009261: marked as done (evolution: Evolution bwrap problem - may fail to print or hang in startup)
Your message dated Sat, 11 Feb 2023 12:35:38 -0800
with message-id <29017c650c48cd05ebc52add9e6c104b973499e9.ca...@ghic.org>
and subject line Chain of bug reports in leading me to think this fixed.
has caused the Debian Bug report #1009261,
regarding evolution: Evolution bwrap problem - may fail to print or hang in
startup
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1009261: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009261
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: evolution
Version: 3.38.3-1
Severity: grave
X-Debbugs-Cc: none, H.-Dirk Schmitt
Evolution stopped printing on several installations.
Also currently evoltution is hanging on startup.
The analysis of the startup problem is triggered that here the socket
`/run/user/${UID}/at-spi/bus_1` is already
existing bevore evolution startup. Manual removal of the socket mitigates the
startup problem.
A better mitigation is avoiding the bubblewrap (bwarp) sandboxing at all. (Only
intendend for flatpack? Why it is used
for traditional debian packages?)
To avoid bubblewrap sandboxing start evolution with 'WEBKIT_FORCE_SANDBOX=0
/usr/bin/evolution`
Avoiding the bubblewarp sandbox also enable the printing again and would also
solve
bug #990325 – evolution: printer not recognised
[Backref c42 bug ids: #4809, #4844]
-- System Information:
Debian Release: 11.3
APT prefers stable-updates
APT policy: (600, 'stable-updates'), (600, 'stable-security'), (600,
'stable'), (500, 'oldstable-updates'), (490, 'focal-updates'), (490,
'focal-security'), (490, 'focal'), (200, 'testing'), (99, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.16.0-0.bpo.4-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to de_DE.UTF-8), LANGUAGE=de_DE:de:en_US:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages evolution depends on:
ii dbus 1.12.20-2
ii evolution-common 3.38.3-1
ii evolution-data-server 3.38.3-1
ii libc6 2.31-13+deb11u3
ii libcamel-1.2-623.38.3-1
pn libclutter-gtk-1.0-0
ii libecal-2.0-1 3.38.3-1
ii libedataserver-1.2-25 3.38.3-1
ii libevolution 3.38.3-1
ii libglib2.0-0 2.66.8-1
ii libgtk-3-0 3.24.24-4+deb11u2
ii libical3 3.0.9-2
ii libnotify4 0.7.9-3
ii libsoup2.4-1 2.72.0-2
ii libwebkit2gtk-4.0-37 2.36.0-3~deb11u1
ii libxml22.9.10+dfsg-6.7+deb11u1
ii psmisc 23.4-2
Versions of packages evolution recommends:
pn evolution-plugin-bogofilter | evolution-plugin-spamassassin
pn evolution-plugin-pstimport
ii evolution-plugins3.38.3-1
ii yelp 3.38.3-1
Versions of packages evolution suggests:
pn evolution-ews
ii evolution-plugins-experimental 3.38.3-1
ii gnupg 2.2.27-2+deb11u1
ii network-manager 1.30.0-2
-- no debconf information
--
---
H.-Dirk_Schmitt
Dipl.Math.
eMail:dirk.schm...@computer42.org
pgp: http://www.computer42.org/~dirk/OpenPGP-fingerprint.html
--- End Message ---
--- Begin Message ---
This redhat bug looks to match the Debian bug.
Can't print from evolution (Closed, Upstream)
https://bugzilla.redhat.com/show_bug.cgi?id=1896902
One comment offers the same workaround and links to the webkitgtk bug.
"Thanks for a bug report. This is a WebKitGTK bug:
https://bugs.webkit.org/show_bug.cgi?id=202363 (resolved fixed)
Run evolution from a terminal as:
$ WEBKIT_FORCE_SANDBOX=0 evolution"
https://bugzilla.redhat.com/show_bug.cgi?id=1896902#c1
The webkitgtk bug describes they needed different solutions for
printing with for flatpak and bubblewrap.
And this pull request fixes printing with bubblewrap
https://github.com/WebKit/WebKit/pull/3651
I can't find anything specific about the at-spi bus though.
In the evolution bug tracker it looks like around 3.40 they may be have
turned off bwrap, but by 3.46 it appears to be on.
https://gitlab.gnome.org/GNOME/evolution/-/issues/1577 closed--- End Message ---
Bug#1031078: qt6-speech-dev: library libqtexttospeech_mock.so referenced but not provided
For the sake of completeness, here is the patch that fixes the missing find_package() calls. Feel free to send it upstream, it's so simple it's not even copyrighteable.Description: Adds missing find_package() entries. The CMake builds links against Qt;;SerialPort and Qt::Sql on Linux, but never calls the relevant find_package() functions. . This patch simply adds them. Author: Lisandro Damián Nicanor Pérez Meyer Bug-Debian: https://bugs.debian.org/973795 Forwarded: no --- hyperborg-1.0.orig/node/CMakeLists.txt +++ hyperborg-1.0/node/CMakeLists.txt @@ -24,6 +24,8 @@ find_package(Qt6 COMPONENTS Widgets) find_package(Qt6 COMPONENTS Xml) find_package(Qt6 COMPONENTS Qml) find_package(Qt6 COMPONENTS Quick) +find_package(Qt6 COMPONENTS SerialPort) +find_package(Qt6 COMPONENTS Sql) qt_add_executable(hynode WIN32 MACOSX_BUNDLE ../common/buffer.cpp ../common/buffer.h signature.asc Description: This is a digitally signed message part.
Processed: Re: Processed: Re: Bug#1031078: marked as done (qt6-speech-dev: library libqtexttospeech_mock.so referenced but not provided)
Processing commands for cont...@bugs.debian.org: > tag 1031078 pending Bug #1031078 [qt6-speech-dev] qt6-speech-dev: library libqtexttospeech_mock.so referenced but not provided Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1031078: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031078 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1030545: qemu: qemu-img and qemu-system-s390x hang on s390x
Source: qemu Followup-For: Bug #1030545 For anyone else looking into this bug: it seemed to me that 'qcow2.c' is a likely candidate for this infinite looping[1] behaviour to originate from. The fact that metadata preallocation is enabled when it occurs could be relevant information too. (my guess is that it is _not_ a kernel-related regression, but I could be wrong about that) [1] - https://gitlab.com/qemu-project/qemu/-/blob/v7.2.0/block.c#L574-576
Bug#1030510: Info received (Bug#1030510: Info received (Bug#1030510: Info received (mariadb: FTBFS on s390x: timeout)))
Hi, On Wed, 8 Feb 2023 11:42:10 + Andrew Hutchings wrote: Are we 100% sure that Bookworm's kernel on S390x is good? Well, the buildd's don't run bookworm, but they run stable (which currently is bullseye). I am seeing something weird on ci.debian.net too, which also runs stable. I upgraded the systems several days ago which pulled in a new security kernel. Since then I'm seeing that mariadb fails to install on s390x in tests because the install of mariadb-server-10.6 (1:10.6.11-2 testing) or mariadb-server (1:10.11.1-4 unstable) times out. root@ci-worker-s390x-01:~# uname -a Linux ci-worker-s390x-01 5.10.0-21-s390x #1 SMP Debian 5.10.162-1 (2023-01-21) s390x GNU/Linux See the recent tmpfails e.g. here: https://ci.debian.net/packages/d/dbconfig-common/testing/s390x/ https://ci.debian.net/packages/b/bacula/testing/s390x/ https://ci.debian.net/packages/d/django-reversion/testing/s390x/ Paul OpenPGP_signature Description: OpenPGP digital signature
Processed: Re: Bug#1031078: marked as done (qt6-speech-dev: library libqtexttospeech_mock.so referenced but not provided)
Processing commands for cont...@bugs.debian.org:
> reopen 1031078
Bug #1031078 {Done: Jonas Smedegaard } [qt6-speech-dev]
qt6-speech-dev: library libqtexttospeech_mock.so referenced but not provided
Bug reopened
Ignoring request to alter fixed versions of bug #1031078 to the same values
previously set
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1031078: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031078
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1031078: marked as done (qt6-speech-dev: library libqtexttospeech_mock.so referenced but not provided)
reopen 1031078 thanks > Oh, please ignore: I realize now that debhelper does not yet cover Qt6 > and the failure relates to upstream-shipped pre-generated CMakefiles, > and I (until debhelper is improved) need to override dh_auto_configure > to call qmake6. > > Closing this as a non-bug. Actually this is a bug, a real bug, so re opening. Turns out that qmake does not has the ability to find plugins as CMake does. Debhelper does cover Qt 6 with CMake, and actually is preferring CMake over qmake, which is the right thing to do. debhelper might need to learn about qt6, though. signature.asc Description: This is a digitally signed message part.
Bug#1009261: bug 1009261 is forwarded to https://bugs.webkit.org/show_bug.cgi?id=202363
On Sat, Feb 11, 2023 at 11:46:56AM -0800, Diane Trout wrote: > forwarded 1009261 https://bugs.webkit.org/show_bug.cgi?id=202363 > thanks If this was the problem, then this bug is a duplicate of #986218 that was fixed in oldstable/stable/unstable in September. cu Adrian
Bug#1031078: qt6-speech-dev: library libqtexttospeech_mock.so referenced but not provided
Hi Jonas! El sábado, 11 de febrero de 2023 06:15:04 -03 Jonas Smedegaard escribió: > Package: qt6-speech-dev > Version: 6.4.2-2 > Severity: grave > Justification: renders package unusable > > When I try to build a project containing this line: > > find_package(Qt6 COMPONENTS TextToSpeech REQUIRED) > > The configure fails like this: > > CMake Error at > /usr/lib/x86_64-linux-gnu/cmake/Qt6TextToSpeech/Qt6QTextToSpeechMockPluginT > argets.cmake:96 (message): The imported target > "Qt6::QTextToSpeechMockPlugin" references the file > > > "/usr/lib/x86_64-linux-gnu/qt6/plugins/texttospeech/libqtexttospeech_mock.s > o" > > but this file does not exist. Possible reasons include: > > * The file was deleted, renamed, or moved to another location. > > * An install or uninstall procedure did not complete successfully. > > * The installation package was faulty and contained > > > "/usr/lib/x86_64-linux-gnu/cmake/Qt6TextToSpeech/Qt6QTextToSpeechMockPlugin > Targets.cmake" > > but not all the files it references. > > Call Stack (most recent call first): > > /usr/lib/x86_64-linux-gnu/cmake/Qt6TextToSpeech/Qt6QTextToSpeechMockPluginC > onfig.cmake:61 (include) > /usr/lib/x86_64-linux-gnu/cmake/Qt6/QtPublicPluginHelpers.cmake:439 > (include) > /usr/lib/x86_64-linux-gnu/cmake/Qt6TextToSpeech/Qt6TextToSpeechPlugins.cmak > e:5 (__qt_internal_include_plugin_packages) > /usr/lib/x86_64-linux-gnu/cmake/Qt6TextToSpeech/Qt6TextToSpeechConfig.cmake > :133 (include) /usr/lib/x86_64-linux-gnu/cmake/Qt6/Qt6Config.cmake:167 > (find_package) plugins/speech/CMakeLists.txt:22 (find_package) First of all, thanks for your bug report. Indeed some CMake files are being installed when they shouldn't be there. For the sake of completeness CMake files for plugins are used in order for the plugins to be found when packaging applications built with CMake, ie, in order to find where the plugin is and copy it somewhere else to ship it along the application. This is of course not a Debian use case so we remove those .cmake files. > Concretely, the pacakge I try to build is hyperborg, available here: > https://salsa.debian.org/tinker-team/hyperborg Also thanks for this. After modifying the packaging (well, creating a chroot and removing the relevant .cmake files) I've got to build the package... with some modifications. 1. In the file node/CMakelists.txt you will need to add: find_package(Qt6 COMPONENTS SerialPort) find_package(Qt6 COMPONENTS Sql) around line 27. This is because around line 98 the system wants to link against them. 2. This is not strictly necessary but heavily recommended: please add qt6- base-dev to your build dependencies. It is currently brought in by the other dependencies, and will always be there, but it's presence help us a lot to track symbols and packages using them. I'll see to fix qtspeech and upload it ASAP. Regards, Lisandro. signature.asc Description: This is a digitally signed message part.
Bug#1031104: minexpert2: FTBFS (error: ‘QMouseEvent::QMouseEvent(QEvent::Type, const QPointF&, Qt::MouseButton, Qt::MouseButtons, Qt::KeyboardModifiers, const QPointingDevice*)’ is deprecated)
Package: src:minexpert2 Version: 8.6.2-2 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in bookworm, your package failed to build: [...] debian/rules binary-indep PATH: /<>/doc/user-manual/scripts:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games dh binary-indep dh_update_autotools_config -i dh_autoreconf -i debian/rules override_dh_auto_configure make[1]: Entering directory '/<>' PATH: /<>/doc/user-manual/scripts:/<>/doc/user-manual/scripts:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games mkdir -p debian/build mkdir -p debian/tmp cd debian/build && cmake -DCMAKE_BUILD_TYPE=Release -DBUILD_USER_MANUAL=1 -DCMAKE_INSTALL_PREFIX=/usr ../.. -- The C compiler identification is GNU 12.2.0 -- The CXX compiler identification is GNU 12.2.0 -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done [...] [ 71%] Building CXX object src/CMakeFiles/minexpert2.dir/gui/BasePlotCompositeWidget.cpp.o cd /<>/debian/build/src && /usr/bin/c++ -DQT_CORE5COMPAT_LIB -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG -DQT_NO_DEBUG_OUTPUT -DQT_PRINTSUPPORT_LIB -DQT_SVG_LIB -DQT_WIDGETS_LIB -DQT_XML_LIB -I/<>/debian/build/src -I/<>/src -I/<>/debian/build/src/minexpert2_autogen/include -I/<>/debian/build -I/<> -isystem /usr/include/x86_64-linux-gnu/qt6/QtWidgets -isystem /usr/include/x86_64-linux-gnu/qt6 -isystem /usr/include/x86_64-linux-gnu/qt6/QtCore -isystem /usr/lib/x86_64-linux-gnu/qt6/mkspecs/linux-g++ -isystem /usr/include/x86_64-linux-gnu/qt6/QtGui -isystem /usr/include/x86_64-linux-gnu/qt6/QtXml -isystem /usr/include/x86_64-linux-gnu/qt6/QtSvg -isystem /usr/include/x86_64-linux-gnu/qt6/QtPrintSupport -isystem /usr/include/IsoSpec++ -isystem /usr/include/pappsomspp -isystem /usr/include/QuaZip-Qt6-1.4 -isystem /usr/include/QuaZip-Qt6-1.4/quazip -isystem /usr/include/x86_64-linux-gnu/qt6/QtCore5Compat -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fopenmp -O3 -DNDEBUG -Wno-unknown-pragmas -Wall -pedantic -Wextra -Werror -fPIC -std=gnu++17 -MD -MT src/CMakeFiles/minexpert2.dir/gui/BasePlotCompositeWidget.cpp.o -MF CMakeFiles/minexpert2.dir/gui/BasePlotCompositeWidget.cpp.o.d -o CMakeFiles/minexpert2.dir/gui/BasePlotCompositeWidget.cpp.o -c /<>/src/gui/BasePlotCompositeWidget.cpp [ 72%] Building CXX object src/CMakeFiles/minexpert2.dir/gui/BaseTracePlotCompositeWidget.cpp.o cd /<>/debian/build/src && /usr/bin/c++ -DQT_CORE5COMPAT_LIB -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG -DQT_NO_DEBUG_OUTPUT -DQT_PRINTSUPPORT_LIB -DQT_SVG_LIB -DQT_WIDGETS_LIB -DQT_XML_LIB -I/<>/debian/build/src -I/<>/src -I/<>/debian/build/src/minexpert2_autogen/include -I/<>/debian/build -I/<> -isystem /usr/include/x86_64-linux-gnu/qt6/QtWidgets -isystem /usr/include/x86_64-linux-gnu/qt6 -isystem /usr/include/x86_64-linux-gnu/qt6/QtCore -isystem /usr/lib/x86_64-linux-gnu/qt6/mkspecs/linux-g++ -isystem /usr/include/x86_64-linux-gnu/qt6/QtGui -isystem /usr/include/x86_64-linux-gnu/qt6/QtXml -isystem /usr/include/x86_64-linux-gnu/qt6/QtSvg -isystem /usr/include/x86_64-linux-gnu/qt6/QtPrintSupport -isystem /usr/include/IsoSpec++ -isystem /usr/include/pappsomspp -isystem /usr/include/QuaZip-Qt6-1.4 -isystem /usr/include/QuaZip-Qt6-1.4/quazip -isystem /usr/include/x86_64-linux-gnu/qt6/QtCore5Compat -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fopenmp -O3 -DNDEBUG -Wno-unknown-pragmas -Wall -pedantic -Wextra -Werror -fPIC -std=gnu++17 -MD -MT src/CMakeFiles/minexpert2.dir/gui/BaseTracePlotCompositeWidget.cpp.o -MF CMakeFiles/minexpert2.dir/gui/BaseTracePlotCompositeWidget.cpp.o.d -o CMakeFiles/minexpert2.dir/gui/BaseTracePlotCompositeWidget.cpp.o -c /<>/src/gui/BaseTracePlotCompositeWidget.cpp /<>/src/gui/BaseTracePlotCompositeWidget.cpp: In member function ‘virtual void msxps::minexpert::BaseTracePlotCompositeWidget::plotWidgetKeyReleaseEvent(const pappso::BasePlotContext&)’: /<>/src/gui/BaseTracePlotCompositeWidget.cpp:812:70: error: ‘QMouseEvent::QMouseEvent(QEvent::Type, const QPointF&, Qt::MouseButton, Qt::MouseButtons, Qt::KeyboardModifiers, const QPointingDevice*)’ is deprecated: Use another constructor [-Werror=deprecated-declarations] 812 |Qt::NoModifier); | ^ In file included from /usr/include/x86_64-linux-gnu/qt6/QtGui/QPaintEvent:1, from /usr/include/qcustomplot.h:56, from /usr/include/pappsomspp/widget/plotwidget/basetraceplotwidget.h:41, from /<>/src/gui/BaseTracePlotCompositeWidget.hpp:47, from /<>/src/gui/BaseTracePlotCompositeWidget.cpp:51: /usr/include/x86_64-linux-gnu/qt6/QtGui/qevent.h:193:5: note: declared here 193 | QMouseEvent(Type type,
Bug#985760: closing 985760
close 985760 thanks
Processed: closing 985760
Processing commands for cont...@bugs.debian.org: > close 985760 Bug #985760 [amd64-microcode] amd64-microcode: jessie-lts has newer version than stretch(-lts) Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 985760: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985760 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 1009261 is forwarded to https://bugs.webkit.org/show_bug.cgi?id=202363
Processing commands for cont...@bugs.debian.org: > forwarded 1009261 https://bugs.webkit.org/show_bug.cgi?id=202363 Bug #1009261 [evolution] evolution: Evolution bwrap problem - may fail to print or hang in startup Set Bug forwarded-to-address to 'https://bugs.webkit.org/show_bug.cgi?id=202363'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1009261: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009261 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1031102: wine: FTBFS (error: unknown type name ‘StdVideoH264LevelIdc’)
Package: src:wine
Version: 8.0~repack-2
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in bookworm, your package failed to build:
[...]
debian/rules binary-arch
dh binary-arch
dh_update_autotools_config -a
dh_autoreconf -a
find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path '*/.hg/*' -o
-path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a -type f -exec md5sum {} + -o
-type l -printf "symlink %p
" > debian/autoreconf.before
grep -q ^XDT_ configure.ac
autoreconf -f -i
find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path '*/.hg/*' -o
-path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a -type f -exec md5sum {} + -o
-type l -printf "symlink %p
" > debian/autoreconf.after
debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
[...]
x86_64-w64-mingw32-gcc -c -o dlls/d3d11/x86_64-windows/device.o dlls/d3d11/device.c
-Idlls/d3d11 -Iinclude -Iinclude/msvcrt -Ilibs/vkd3d/include -D_UCRT -D__WINESRC__
-D__WINE_PE_BUILD -Wall -fno-strict-aliasing -Wdeclaration-after-statement -Wempty-body
-Wignored-qualifiers -Winit-self -Wno-packed-not-aligned -Wshift-overflow=2
-Wstrict-prototypes -Wtype-limits -Wunused-but-set-parameter -Wvla -Wwrite-strings
-Wpointer-arith -Wlogical-op -Wabsolute-value -Wformat-overflow -Wnonnull -mcx16 -gdwarf-4
-Werror -Wdate-time -g -O2 -ffile-prefix-map=/<>=.
-Wno-array-bounds -Wno-unused-function -Wno-format
x86_64-w64-mingw32-gcc -c -o dlls/d3d11/x86_64-windows/inputlayout.o
dlls/d3d11/inputlayout.c -Idlls/d3d11 -Iinclude -Iinclude/msvcrt -Ilibs/vkd3d/include
-D_UCRT -D__WINESRC__ -D__WINE_PE_BUILD -Wall -fno-strict-aliasing
-Wdeclaration-after-statement -Wempty-body -Wignored-qualifiers -Winit-self
-Wno-packed-not-aligned -Wshift-overflow=2 -Wstrict-prototypes -Wtype-limits
-Wunused-but-set-parameter -Wvla -Wwrite-strings -Wpointer-arith -Wlogical-op
-Wabsolute-value -Wformat-overflow -Wnonnull -mcx16 -gdwarf-4 -Werror -Wdate-time -g -O2
-ffile-prefix-map=/<>=. -Wno-array-bounds -Wno-unused-function
-Wno-format
x86_64-w64-mingw32-gcc -c -o dlls/d3d11/x86_64-windows/shader.o dlls/d3d11/shader.c
-Idlls/d3d11 -Iinclude -Iinclude/msvcrt -Ilibs/vkd3d/include -D_UCRT -D__WINESRC__
-D__WINE_PE_BUILD -Wall -fno-strict-aliasing -Wdeclaration-after-statement -Wempty-body
-Wignored-qualifiers -Winit-self -Wno-packed-not-aligned -Wshift-overflow=2
-Wstrict-prototypes -Wtype-limits -Wunused-but-set-parameter -Wvla -Wwrite-strings
-Wpointer-arith -Wlogical-op -Wabsolute-value -Wformat-overflow -Wnonnull -mcx16 -gdwarf-4
-Werror -Wdate-time -g -O2 -ffile-prefix-map=/<>=.
-Wno-array-bounds -Wno-unused-function -Wno-format
x86_64-w64-mingw32-gcc -c -o dlls/d3d11/x86_64-windows/state.o dlls/d3d11/state.c
-Idlls/d3d11 -Iinclude -Iinclude/msvcrt -Ilibs/vkd3d/include -D_UCRT -D__WINESRC__
-D__WINE_PE_BUILD -Wall -fno-strict-aliasing -Wdeclaration-after-statement -Wempty-body
-Wignored-qualifiers -Winit-self -Wno-packed-not-aligned -Wshift-overflow=2
-Wstrict-prototypes -Wtype-limits -Wunused-but-set-parameter -Wvla -Wwrite-strings
-Wpointer-arith -Wlogical-op -Wabsolute-value -Wformat-overflow -Wnonnull -mcx16 -gdwarf-4
-Werror -Wdate-time -g -O2 -ffile-prefix-map=/<>=.
-Wno-array-bounds -Wno-unused-function -Wno-format
x86_64-w64-mingw32-gcc -c -o dlls/d3d11/x86_64-windows/texture.o dlls/d3d11/texture.c
-Idlls/d3d11 -Iinclude -Iinclude/msvcrt -Ilibs/vkd3d/include -D_UCRT -D__WINESRC__
-D__WINE_PE_BUILD -Wall -fno-strict-aliasing -Wdeclaration-after-statement -Wempty-body
-Wignored-qualifiers -Winit-self -Wno-packed-not-aligned -Wshift-overflow=2
-Wstrict-prototypes -Wtype-limits -Wunused-but-set-parameter -Wvla -Wwrite-strings
-Wpointer-arith -Wlogical-op -Wabsolute-value -Wformat-overflow -Wnonnull -mcx16 -gdwarf-4
-Werror -Wdate-time -g -O2 -ffile-prefix-map=/<>=.
-Wno-array-bounds -Wno-unused-function -Wno-format
x86_64-w64-mingw32-gcc -c -o dlls/d3d11/x86_64-windows/utils.o dlls/d3d11/utils.c
-Idlls/d3d11 -Iinclude -Iinclude/msvcrt -Ilibs/vkd3d/include -D_UCRT -D__WINESRC__
-D__WINE_PE_BUILD -Wall -fno-strict-aliasing -Wdeclaration-after-statement -Wempty-body
-Wignored-qualifiers -Winit-self -Wno-packed-not-aligned -Wshift-overflow=2
-Wstrict-prototypes -Wtype-limits -Wunused-but-set-parameter -Wvla -Wwrite-strings
-Wpointer-arith -Wlogical-op -Wabsolute-value -Wformat-overflow -Wnonnull -mcx16 -gdwarf-4
-Werror -Wdate-time -g -O2 -ffile-prefix-map=/<>=.
-Wno-array-bounds -Wno-unused-function -Wno-format
x86_64-w64-mingw32-gcc -c -o dlls/d3d11/x86_64-windows/view.o dlls/d3d11/view.c
-Idlls/d3d11 -Iinclude -Iinclude/msvcrt -Ilibs/vkd3d/include -D_UCRT -D__WINESRC__
-D__WINE_PE_BUILD -Wall -fno-strict-aliasing -Wdeclaration-after-statement -Wempty-body
-Wignored-qualifiers -Winit-self -Wno-packed-not-aligned -Wshift-overflow=2
Bug#1031101: gnome-bluetooth is not installable
Package: gnome-bluetooth Version: 3.34.5-9 Severity: serious The following packages have unmet dependencies: gnome-bluetooth-sendto : Breaks: gnome-bluetooth (< 42~)
Bug#1029944: neon27 FTBFS on IPV6-only buildds
Hi,
On Sat, Feb 11, 2023 at 7:48 PM Andreas Henriksson wrote:
> If replacing "127.0.0.1" with "localhost" does not work the attached
> (completely untested) patch might be an option instead (simply skip the
> test on EAFNOSUPPORT).
I don't have access to an IPv6 host to test on, so I just think it
would not work.
> (Sorry if the patch is completely broken, but I hope you get the
> idea...)
This is broken for sure as some tests create a server socket (get the
'Address family for hostname not supported' error) and then next tests
would like to connect to it ('request failed: Could not connect to
proxy server: Connection refused' error) or simply get an other error
('request failed with 5 not NE_ERROR' message). While your patch would
skip the former, the latter would still be a problem.
I can remove the IPv4 only tests that are detected on buildds, but
there's at least one which hangs ('Build killed with signal TERM after
150 minutes of inactivity').
Any IPv6 porterbox available?
Regards,
Laszlo/GCS
Bug#1028857: libpsl: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2
On Sat, 11 Feb 2023 18:47:04 +0100 Florian Ernst wrote: Of course, updating to 0.21.2 with its "273 changed files with 70,410 additions and 1,392 deletions"[0] feels rather invasive this late in the Debian release cycle, so maybe a more targeted fix could be extracted. These files are mostly test corpora from OSS-Fuzz. So I wouldn't be too bothered, as those are only used with `make check`. Some other changes are updates of the copyright year and meson and msvc build files, both have no influence on the Debian build (autotools/make). I leave it to you to decide about the few remaining changed files. Regards, Tim OpenPGP_signature Description: OpenPGP digital signature
Bug#1029944: neon27 FTBFS on IPV6-only buildds
Hello again,
On Sat, Feb 11, 2023 at 06:55:13PM +0100, Andreas Henriksson wrote:
> On Sun, Jan 29, 2023 at 02:29:23PM +0100, László Böszörményi (GCS) wrote:
> > Control: tags -1 +confirmed
> >
> > On Sun, Jan 29, 2023 at 12:33 PM Adrian Bunk wrote:
> > > https://buildd.debian.org/status/logs.php?pkg=neon27=amd64
> > >
> > > ...
> > > auth.. 3/20 FAIL - retries (line 311: HTTP error:
> > > Could not resolve hostname `127.0.0.1': Address family for hostname not
> > > supported)
> > Is there a way to detect such buildds as a maintainer? What can I do
> > except notifying upstream and / or disable such tests?
If replacing "127.0.0.1" with "localhost" does not work the attached
(completely untested) patch might be an option instead (simply skip the
test on EAFNOSUPPORT).
(Sorry if the patch is completely broken, but I hope you get the
idea...)
Regards,
Andreas Henriksson
--- test/utils.h.orig 2023-02-11 19:38:52.122713689 +0100
+++ test/utils.h 2023-02-11 19:40:25.601514834 +0100
@@ -25,7 +25,7 @@
#include "child.h"
-#define ONREQ(x) do { int _ret = (x); if (_ret) { t_context("line %d: HTTP error:\n%s", __LINE__, ne_get_error(sess)); return FAIL; } } while (0);
+#define ONREQ(x) do { int _ret = (x); if (_ret) { t_context("line %d: HTTP error:\n%s", __LINE__, ne_get_error(sess)); if (strcmp(ne_get_error(sess), "Could not resolve hostname `127.0.0.1': Address family for hostname not supported") == 0) { return SKIP; } else { return FAIL; } } } while (0);
int single_serve_string(ne_socket *s, void *userdata);
Bug#1030971: marked as done (rust-configparser: autopkgtest failure)
Your message dated Sat, 11 Feb 2023 18:32:40 +
with message-id
and subject line re: rust-configparser: autopkgtest failure
has caused the Debian Bug report #1030971,
regarding rust-configparser: autopkgtest failure
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1030971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030971
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-configparser
Version: 2.0.0-2
Severity: serious
https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-configparser/31203190/log.gz
...
running 2 tests
Error: Os { code: 13, kind: PermissionDenied, message: "Permission denied" }
Error: Os { code: 13, kind: PermissionDenied, message: "Permission denied" }
test non_cs ... FAILED
test cs ... FAILED
failures:
non_cs stdout
thread 'non_cs' panicked at 'assertion failed: `(left == right)`
left: `1`,
right: `0`: the test returned a termination value with a non-zero status code
(1) which indicates a failure',
/usr/src/rustc-1.63.0/library/test/src/lib.rs:184:5
stack backtrace:
0: rust_begin_unwind
at /usr/src/rustc-1.63.0/library/std/src/panicking.rs:584:5
1: core::panicking::panic_fmt
at /usr/src/rustc-1.63.0/library/core/src/panicking.rs:142:14
2: core::panicking::assert_failed_inner
3: core::panicking::assert_failed
at /usr/src/rustc-1.63.0/library/core/src/panicking.rs:181:5
4: test::assert_test_result
at /usr/src/rustc-1.63.0/library/test/src/lib.rs:184:5
5: test::non_cs::{{closure}}
at ./tests/test.rs:5:1
6: core::ops::function::FnOnce::call_once
at /usr/src/rustc-1.63.0/library/core/src/ops/function.rs:248:5
7: core::ops::function::FnOnce::call_once
at /usr/src/rustc-1.63.0/library/core/src/ops/function.rs:248:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose
backtrace.
cs stdout
thread 'cs' panicked at 'assertion failed: `(left == right)`
left: `1`,
right: `0`: the test returned a termination value with a non-zero status code
(1) which indicates a failure',
/usr/src/rustc-1.63.0/library/test/src/lib.rs:184:5
stack backtrace:
0: rust_begin_unwind
at /usr/src/rustc-1.63.0/library/std/src/panicking.rs:584:5
1: core::panicking::panic_fmt
at /usr/src/rustc-1.63.0/library/core/src/panicking.rs:142:14
2: core::panicking::assert_failed_inner
3: core::panicking::assert_failed
at /usr/src/rustc-1.63.0/library/core/src/panicking.rs:181:5
4: test::assert_test_result
at /usr/src/rustc-1.63.0/library/test/src/lib.rs:184:5
5: test::cs::{{closure}}
at ./tests/test.rs:108:1
6: core::ops::function::FnOnce::call_once
at /usr/src/rustc-1.63.0/library/core/src/ops/function.rs:248:5
7: core::ops::function::FnOnce::call_once
at /usr/src/rustc-1.63.0/library/core/src/ops/function.rs:248:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose
backtrace.
failures:
cs
non_cs
test result: FAILED. 0 passed; 2 failed; 0 ignored; 0 measured; 0 filtered out;
finished in 0.01s
error: test failed, to rerun pass `--test test`
autopkgtest [02:09:53]: test librust-configparser-dev:: ---]
autopkgtest [02:09:53]: test librust-configparser-dev:: - - - - - - - - - -
results - - - - - - - - - -
librust-configparser-dev: FAIL non-zero exit status 101
autopkgtest [02:09:53]: summary
rust-configparser:@ FAIL non-zero exit status 101
librust-configparser-dev:default FAIL non-zero exit status 101
librust-configparser-dev: FAIL non-zero exit status 101
--- End Message ---
--- Begin Message ---
Version: 3.0.2-2
This looks fixed now.--- End Message ---
Bug#1030175: libgetdata: FTBFS: dh_install: error: missing files, aborting
On Sun, Feb 05, 2023 at 02:52:49PM +0100, s3v wrote: > Dear Maintainer, > > > dh_install: warning: Cannot find (any matches for) > > "usr/local/lib/python3.10/dist-packages/*" (tried in ., debian/tmp) > > > > dh_install: warning: python3-pygetdata missing files: > > usr/local/lib/python3.10/dist-packages/* > > dh_install: error: missing files, aborting > > make: *** [debian/rules:28: binary-arch] Error 25 > > this is caused by a reference to python 3.10 in this file [1] > > Kind Regards > > [1] > https://sources.debian.org/src/libgetdata/0.11.0-5/debian/python3-pygetdata.install/ I think this is only half the truth. The file explicitly list both 3.10 and 3.11. The second half is that python3-all-dev no longer brings in both 3.10 and 3.11 since (see last bullet): python3-defaults (3.11.1-2) unstable; urgency=medium * Provide python3-supported-min and python3-supported-max versioned virtual packages, to allow modules to easily declare dependencies for all supported versions. * Bump Depends to 3.11.1-1. * Drop support for Python 3.10. -- Stefano Rivera Sat, 28 Jan 2023 09:46:57 -0400 It would however probably be a good idea if libgetdata / python3-pygetdata.install did not hardcode which python versions it expects python3-all-dev to bring in at all?! Is there any specific reason why it explicitly lists both the 3.10 and 3.11 paths rather than just use a wildcard in the path? If it's only to move files from /usr/local/lib to /usr/lib then maybe that would be better to do in debian/rules exectute_after_dh_auto_install target?! (Unless there's a better way to get the upstream install to use prefix /usr instead of /usr/local ofcourse) Oh well... now that I've written all this I see there's already: https://salsa.debian.org/science-team/libgetdata/-/commit/f698db0b309351d8dc66fad194f9462fb5c531ea Might still be worth considering not hardcoding any versions as discussed above though (to avoid repeating this problem once python 3.11 goes out of fashion)... Regards, Andreas Henriksson
Bug#1030186: enigmail: FTBFS (Error: Cannot find module 'chalk')
On Wed, Feb 01, 2023 at 12:32:44AM +0100, Santiago Vila wrote: > Package: src:enigmail > Version: 2:2.2.4-0.3 > Severity: serious > Tags: ftbfs > > Dear maintainer: > > I've just noticed that enigmail currently fails to build in bookworm: > > make[1]: Leaving directory '/<>' >dh_auto_test -i > make -j1 test "TESTSUITEFLAGS=-j1 --verbose" VERBOSE=1 > make[1]: Entering directory '/<>' > static_analysis/eslint package > There was a problem loading formatter: > /usr/share/nodejs/eslint/lib/cli-engine/formatters/stylish > Error: Cannot find module 'chalk' [...] /usr/share/nodejs/eslint/lib/cli-engine/formatters/stylish is part of eslint package. The eslint package (build-depends and) *recommends* node-chalk. This changelog entry seems relevant: eslint (1.3.1~dfsg-3) experimental; urgency=medium * Fix install executable. * Add patch cherry-picked upstream to lazy-load rules. Relax to recommend (not depend on) node-chalk node-inquirer node-strip-ansi node-text-table. Fix explicitly depend on node-escape-string-regexp (previously pulled in by node-chalk). -- Jonas Smedegaard Sat, 12 Oct 2019 15:19:55 +0200 I'm not able to determine if either enigmail should dep on node-chalk itself because it uses supposedly optional components of eslint or if there's a mistake in eslint which should have node-chalk as a depends rather than recommends Hope someone else can figure this out. Regards, Andreas Henriksson
Bug#997217: marked as done (libtag1-dev: Missing dependency on zlib1g-dev)
Your message dated Sat, 11 Feb 2023 18:05:36 + with message-id and subject line Bug#997217: fixed in taglib 1.13-2 has caused the Debian Bug report #997217, regarding libtag1-dev: Missing dependency on zlib1g-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 997217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997217 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: emms Version: 5.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > g++ -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o > src/emms-print-metadata src/emms-print-metadata.cpp `taglib-config --cflags > --libs` > /usr/bin/ld: cannot find -lz > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2021/10/23/emms_5.1-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: taglib Source-Version: 1.13-2 Done: Boyuan Yang We believe that the bug you reported is fixed in the latest version of taglib, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 997...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boyuan Yang (supplier of updated taglib package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 11 Feb 2023 12:25:27 -0500 Source: taglib Architecture: source Version: 1.13-2 Distribution: unstable Urgency: high Maintainer: Debian Multimedia Maintainers Changed-By: Boyuan Yang Closes: 997217 Changes: taglib (1.13-2) unstable; urgency=high . * Bump Standards-Version to 4.6.2. * debian/: Apply wrap-and-sort -abst. * debian/control: libtag1-dev: Add missing dep zlib1g-dev. (Closes: #997217) Checksums-Sha1: 71323092dec4ced69c540189a11ee8e5e60c38de 2336 taglib_1.13-2.dsc e68319d1ac8fcf7fd68697c6d08427d847b5ebb3 1371504 taglib_1.13.orig.tar.gz 3d36a51a965e02b16d850d71845aa732d3f1d49b 33860 taglib_1.13-2.debian.tar.xz d6dce88d13bec2cc251c089327ae767fd15d6f0f 11051 taglib_1.13-2_amd64.buildinfo Checksums-Sha256: d4032865e0a7e9ea07fa057d0c924f89ae57e44797d0462a1368438935371ebf 2336 taglib_1.13-2.dsc 58f08b4db3dc31ed152c04896ee9172d22052bc7ef12888028c01d8b1d60ade0 1371504 taglib_1.13.orig.tar.gz 5d8b0c9b0302313a780b445967b49c681edd6a1d006bd313fd78eae42c9d7675 33860 taglib_1.13-2.debian.tar.xz 5afdce43a738e716a026f69e4d2bfc2a27ef7ed5f1f8135fe95fe9f0949e0d16 11051 taglib_1.13-2_amd64.buildinfo Files: 4ce6f58cc32c2cea704f92778eba1127 2336 libs optional taglib_1.13-2.dsc 0b75619b67b9149cfcbbe5c127df6395 1371504 libs optional taglib_1.13.orig.tar.gz 3f3e2f84b2d11e1ce93490442e66212b 33860 libs optional taglib_1.13-2.debian.tar.xz 3f2660886ad832f9beeef703df8b9263 11051 libs optional taglib_1.13-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmPn0LEACgkQwpPntGGC Ws5h7w//XYxdq8QXU5DXH4/XAuIkg1oTyzO8LtsiR/nSP7HHu3TarPtQo9ZuxRtD pzAp4pLaxU4gxuf5AoNouyt6doMo3D5KVPYPJseJPIu14ryW8n6I8BKnkw8J2Yxk SfSFJe5nwkv9UMglpOT11W24BxxBBMOzVySY30rQ9NdH/w1sx/nDZYneJSnPZqwK hZl+yMcqNjn314pibyc/U03jRxMwK2480VYR2QhXSsXRzTJb0RHdYaHHZar8jJtc YRWfndK7SFXrVF3iY7uUS3uvweY7/yKX+aCapnL0kL0H2KM+yQFg8DJlk6Bdcjx7 +94p+j9ohXWZoQxb+JVucODWdxP6iUgYALuOYUbEmuI63Y5R4e+3/aRAIo6fFREj BrlXtM9U+ypxFFIEK4bGkxxQ8UHu63BEzepgKqXRq/UyY/O7uPxryQKjeWXDo/83 Ae5z9Cv7y4+9QPbVlsoqGHdYDN5/Yq76SxTHAKTIvXubK67x2Jpmv6yxumjqGhm0 r8rfcHlkXcz66YIhajD1LkCP0yCseshtOolBfahMRWJhaGrZySo5gkwZqKbcS8ed uV/eyPR1IIQBZYdve3CA8/9nbULRiHUgoH0+pCPIw0nFarBqDh1vj0/rJMx0iQ3H
Bug#1029944: neon27 FTBFS on IPV6-only buildds
On Sun, Jan 29, 2023 at 02:29:23PM +0100, László Böszörményi (GCS) wrote: > Control: tags -1 +confirmed > > On Sun, Jan 29, 2023 at 12:33 PM Adrian Bunk wrote: > > https://buildd.debian.org/status/logs.php?pkg=neon27=amd64 > > > > ... > > auth.. 3/20 FAIL - retries (line 311: HTTP error: > > Could not resolve hostname `127.0.0.1': Address family for hostname not > > supported) > Is there a way to detect such buildds as a maintainer? What can I do > except notifying upstream and / or disable such tests? FWIW "127.0.0.1" is hardcoded here: https://sources.debian.org/src/neon27/0.32.5-1/test/utils.c/#L207 Possibly that could be replaced with "localhost" instead, but I'm not sure if using 127.0.0.1 is an attempt at hiding that the code is ipv4-only rather than protocol independent (maybe)... I tried quickly looking at upstream git history if it could confirm my suspicion, but the closest I could find was: https://github.com/notroj/neon/commit/eff6521be537c74511593743bf8665d898e26567 Seems like localhost -> 127.0.0.1 switch was intentional (and done during SVN days?). Maybe someone digging deeper can find "r1910". Regards, Andreas Henriksson
Processed: Re: Bug#1028857: libpsl: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2
Processing control commands: > tags -1 upstream fixed-upstream Bug #1028857 [src:libpsl] libpsl: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2 Added tag(s) fixed-upstream and upstream. -- 1028857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028857 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1031014: marked as done (rust-r2d2: autopkgtest regression on ppc64el)
Your message dated Sat, 11 Feb 2023 18:25:54 +0100 (CET)
with message-id
and subject line
has caused the Debian Bug report #1031014,
regarding rust-r2d2: autopkgtest regression on ppc64el
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1031014: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031014
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-r2d2
Version: 0.8.10-3
Severity: serious
https://ci.debian.net/data/autopkgtest/testing/ppc64el/r/rust-r2d2/31176721/log.gz
...
test test::test_idle_timeout ... FAILED
test test::test_max_lifetime ... ok
failures:
test::test_idle_timeout stdout
thread 'test::test_idle_timeout' panicked at 'assertion failed: `(left ==
right)`
left: `4`,
right: `2`', src/test.rs:392:5
stack backtrace:
0: rust_begin_unwind
at /usr/src/rustc-1.63.0/library/std/src/panicking.rs:584:5
1: core::panicking::panic_fmt
at /usr/src/rustc-1.63.0/library/core/src/panicking.rs:142:14
2: core::panicking::assert_failed_inner
3: core::panicking::assert_failed
at /usr/src/rustc-1.63.0/library/core/src/panicking.rs:181:5
4: r2d2::test::test_idle_timeout
at ./src/test.rs:392:5
5: r2d2::test::test_idle_timeout::{{closure}}
at ./src/test.rs:350:1
6: core::ops::function::FnOnce::call_once
at /usr/src/rustc-1.63.0/library/core/src/ops/function.rs:248:5
7: core::ops::function::FnOnce::call_once
at /usr/src/rustc-1.63.0/library/core/src/ops/function.rs:248:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose
backtrace.
failures:
test::test_idle_timeout
test result: FAILED. 17 passed; 1 failed; 0 ignored; 0 measured; 0 filtered
out; finished in 9.13s
error: test failed, to rerun pass `--lib`
autopkgtest [00:20:10]: test librust-r2d2-dev:default: ---]
librust-r2d2-dev:default FAIL non-zero exit status 101
...
autopkgtest [00:20:43]: summary
rust-r2d2:@ PASS
librust-r2d2-dev:default FAIL non-zero exit status 101
librust-r2d2-dev:PASS
This might be related to
rust-r2d2 (0.8.10-3) unstable; urgency=medium
...
* Dropped fix-test.diff; skipped idle_timeout on arm(el,hf), i386 and
ppc64el
-- Matthias Geiger Fri, 10 Feb 2023
10:12:58 +0100
--- End Message ---
--- Begin Message ---
Version: 0.8.10-4
--- End Message ---
Bug#1030982: gscan2pdf: Not a JPEG file: starts with 0x00 0x00 (was: Segmentation fault)
On Sat, Feb 11 2023 at 14:03 GMT, Jeff wrote: > I still don't understand. The log you provided covered a successful > scan, with a couple of post-processing steps. > > Please provide a log where the scan job failed. As I said earlier, I provided it already. On Fri, Feb 10 2023 at 12:33 +01, Janusz S. Bień wrote: > On Fri, Feb 10 2023 at 10:55 GMT, Jeff wrote: >> There's no segfault there. > > It was at first trial, but I'm unable now to reproduce it. > >> >> Please start gscan2pdf from the command line with the --log=log >> option, if necessary, hit OK to select the crashed session, reproduce >> the problem (i.e. the segfaul), quit, and post the log file, which >> gscan2pdf may have compressed with xz. > > Now gscan2pdf offers the choice of two devices (physically it is the same > devices), one of them works. > > The failure log is missing the line which appeared on the terminal: > > Not a JPEG file: starts with 0x00 0x00 This mail had two attachments. The failure log was [log1 (application/octet-stream, attachment)] If you want something else, please specify it explicitely. Regards - Janusz -- , Janusz S. Bien emeryt (emeritus) https://sites.google.com/view/jsbien
Bug#1030982: gscan2pdf: Segmentation fault
I still don't understand. The log you provided covered a successful scan, with a couple of post-processing steps. Please provide a log where the scan job failed. OpenPGP_signature Description: OpenPGP digital signature
Bug#1031087: marked as done (aspic sources ship src/aspic binary and execute it during the build)
Your message dated Sat, 11 Feb 2023 14:55:55 +0100 with message-id and subject line Re: Bug#1031087: aspic sources ship src/aspic binary and execute it during the build has caused the Debian Bug report #1031087, regarding aspic sources ship src/aspic binary and execute it during the build to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1031087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031087 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: aspic Version: 2.00-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=aspic=2.00-1 ... cd doc && ./Build ./Build: 5: ../src/aspic: Exec format error ... dh_strip -a objcopy: Unable to recognise the format of the input file `debian/aspic/usr/bin/aspic' dh_strip: error: objcopy --only-keep-debug --compress-debug-sections debian/aspic/usr/bin/aspic debian/.debhelper/aspic/dbgsym-root/usr/lib/debug/.build-id/cc/91951bf43c2554a608eed2c5731ad48ce617dd.debug returned exit code 1 dh_strip: error: Aborting due to earlier error make: *** [debian/rules:3: binary-arch] Error 25 --- End Message --- --- Begin Message --- Version: 2.00+dfsg-1--- End Message ---
Bug#1031087: aspic sources ship src/aspic binary and execute it during the build
Source: aspic Version: 2.00-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=aspic=2.00-1 ... cd doc && ./Build ./Build: 5: ../src/aspic: Exec format error ... dh_strip -a objcopy: Unable to recognise the format of the input file `debian/aspic/usr/bin/aspic' dh_strip: error: objcopy --only-keep-debug --compress-debug-sections debian/aspic/usr/bin/aspic debian/.debhelper/aspic/dbgsym-root/usr/lib/debug/.build-id/cc/91951bf43c2554a608eed2c5731ad48ce617dd.debug returned exit code 1 dh_strip: error: Aborting due to earlier error make: *** [debian/rules:3: binary-arch] Error 25
Processed: forward
Processing commands for cont...@bugs.debian.org: > forwarded 1029466 https://github.com/pysal/esda/issues/240 Bug #1029466 [src:esda] esda: FTBFS with current numba version Set Bug forwarded-to-address to 'https://github.com/pysal/esda/issues/240'. > found 1029466 2.4.3-2 Bug #1029466 [src:esda] esda: FTBFS with current numba version Marked as found in versions esda/2.4.3-2. > notfound 1029466 esda/0.1.0-1 Bug #1029466 [src:esda] esda: FTBFS with current numba version The source esda and version 0.1.0-1 do not appear to match any binary packages No longer marked as found in versions esda/0.1.0-1. > End of message, stopping processing here. Please contact me if you need assistance. -- 1029466: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029466 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1031072: librust-rspotify-dev is not installable
On Sat, 11 Feb 2023 08:45:32 + Peter Green wrote: > > > > The following packages have unmet dependencies: > > librust-rspotify-dev : Depends: librust-base64-0.12+default-dev > > Depends: librust-itertools-0.9+default-dev > > Depends: librust-rand-0.7+default-dev > > Depends: librust-reqwest-0.9+default-dev but it is > > not installable > > > As far as I can tell, rspotify was packaged as a dependency of spotify-tui. > > The problem is that while there is a new version of rspotify that has > modernised dependencies, spotify-tui was never updated to modernise it's > dependencies and was eventually removed from Debian. > > https://github.com/Rigellute/spotify-tui/issues/915 > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018166 > > I don't think there is much value in fixing this package, until/unless > either spotify-tui is updated upstream and someone wants to get it > back into Debian or some other package comes up that needs rspotify > > I intend to package [ncspot], which depends on rspotify. I'll work on it after freeze, please don't RM it. [ncspot]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020522 -- Sdrager, Blair Noctis OpenPGP_signature Description: OpenPGP digital signature
Bug#1031073: marked as done (librust-lewton+async-ogg-dev is not installable)
Your message dated Sat, 11 Feb 2023 09:58:58 + with message-id <8f680d75-d1e3-f1f3-5c69-24cdeac93...@debian.org> and subject line re: librust-lewton+async-ogg-dev is not installable has caused the Debian Bug report #1031073, regarding librust-lewton+async-ogg-dev is not installable to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1031073: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031073 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: librust-lewton+async-ogg-dev Version: 0.9.4-3 Severity: serious The following packages have unmet dependencies: librust-lewton+async-ogg-dev : Depends: librust-futures-0.1+default-dev Depends: librust-ogg-0.7+async-dev Depends: librust-ogg-0.7+default-dev Depends: librust-tokio-io-0.1+default-dev --- End Message --- --- Begin Message --- Version: 0.10.2-1 The following packages have unmet dependencies: librust-lewton+async-ogg-dev : Depends: librust-futures-0.1+default-dev Depends: librust-ogg-0.7+async-dev Depends: librust-ogg-0.7+default-dev Depends: librust-tokio-io-0.1+default-dev The latest upload has dropped the "async-ogg" feature--- End Message ---
Bug#1031078: marked as done (qt6-speech-dev: library libqtexttospeech_mock.so referenced but not provided)
Your message dated Sat, 11 Feb 2023 10:40:11 +0100 with message-id <167610841148.3113738.3987509373673188...@auryn.jones.dk> and subject line Re: qt6-speech-dev: library libqtexttospeech_mock.so referenced but not provided has caused the Debian Bug report #1031078, regarding qt6-speech-dev: library libqtexttospeech_mock.so referenced but not provided to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1031078: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031078 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: qt6-speech-dev Version: 6.4.2-2 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 When I try to build a project containing this line: find_package(Qt6 COMPONENTS TextToSpeech REQUIRED) The configure fails like this: CMake Error at /usr/lib/x86_64-linux-gnu/cmake/Qt6TextToSpeech/Qt6QTextToSpeechMockPluginTargets.cmake:96 (message): The imported target "Qt6::QTextToSpeechMockPlugin" references the file "/usr/lib/x86_64-linux-gnu/qt6/plugins/texttospeech/libqtexttospeech_mock.so" but this file does not exist. Possible reasons include: * The file was deleted, renamed, or moved to another location. * An install or uninstall procedure did not complete successfully. * The installation package was faulty and contained "/usr/lib/x86_64-linux-gnu/cmake/Qt6TextToSpeech/Qt6QTextToSpeechMockPluginTargets.cmake" but not all the files it references. Call Stack (most recent call first): /usr/lib/x86_64-linux-gnu/cmake/Qt6TextToSpeech/Qt6QTextToSpeechMockPluginConfig.cmake:61 (include) /usr/lib/x86_64-linux-gnu/cmake/Qt6/QtPublicPluginHelpers.cmake:439 (include) /usr/lib/x86_64-linux-gnu/cmake/Qt6TextToSpeech/Qt6TextToSpeechPlugins.cmake:5 (__qt_internal_include_plugin_packages) /usr/lib/x86_64-linux-gnu/cmake/Qt6TextToSpeech/Qt6TextToSpeechConfig.cmake:133 (include) /usr/lib/x86_64-linux-gnu/cmake/Qt6/Qt6Config.cmake:167 (find_package) plugins/speech/CMakeLists.txt:22 (find_package) Concretely, the pacakge I try to build is hyperborg, available here: https://salsa.debian.org/tinker-team/hyperborg - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmPnXJUACgkQLHwxRsGg ASG3mQ//b0L2GLW6AxJRB9JBKDxulflFHv8BWDGVwS3Yn1FYH3kgLlRonhf6UHAY Hsi5dHTcHbOSL4sArtKslurfzPDOBMvtpHfuf5oGni1WVeQghFMd0kMp7ggGxTRj s5XtZAQSQ/AjroL9VFXZTam4tHsf1o1pW+8niBTN7NdMiE7IaKrU9zvg7fjdYMdv vKi7TQ1NZ/QOnVHT0bKwwHpXcNRKPFWy49NyHBOVzNHTI4wv0+CffX0Wf2t2WNE8 EmlKDPi+VO4nKffF+m4madlmfp7ERGVa1OSmEs8kgEszC+2DQgQsHK5aRA91dqPq SqJH8N9Hm9oNxuoW7G1GQpeqjD4RwvmdXa6htBMlfl29QuO6X11SRtkmxgp7ZrCq GElYE61Z97+OduOhjb5AEIym0At5q4BWnDVj341lQctIOAEBsImFuasDI1SCSH5/ Kvc1ac27whPt42pcqg0Xmo57f0m2i5LNO0RhHAALgw+e1ZUzUdmBffflFvVQKrM3 vEq6fLHicXP9MiKFLtEU1pCWp/iCWEWkoPqbcaMugAkDgqlp5hFbLsM/FppYFm1p IrsrhyYnTtrsZRJ0p23pxxGV1cRNDv6roq/Rev0pppuQnQVLOckZNca01otgfjaM MOuIV3YKJ8imBgeF1404z/wdhZrEJlPrSIdds6+lQJVtZ2tLqJg= =eV50 -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Quoting Jonas Smedegaard (2023-02-11 10:15:04) > When I try to build a project containing this line: > > find_package(Qt6 COMPONENTS TextToSpeech REQUIRED) > > The configure fails like this: Oh, please ignore: I realize now that debhelper does not yet cover Qt6 and the failure relates to upstream-shipped pre-generated CMakefiles, and I (until debhelper is improved) need to override dh_auto_configure to call qmake6. Closing this as a non-bug. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature --- End Message ---
Bug#1018023: Update on this bug?
Hi, Do you have plans to fix this before the bookworm freeze, please? I think netbsd at least have patched eterm to work with the newer imlib; at least per the comment here https://github.com/mej/Eterm/issues/4 That linked to http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/x11/eterm/patches/ Which has a couple of patches that seem like they'd do the trick... Thanks, Matthew
Bug#1031078: qt6-speech-dev: library libqtexttospeech_mock.so referenced but not provided
Package: qt6-speech-dev Version: 6.4.2-2 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 When I try to build a project containing this line: find_package(Qt6 COMPONENTS TextToSpeech REQUIRED) The configure fails like this: CMake Error at /usr/lib/x86_64-linux-gnu/cmake/Qt6TextToSpeech/Qt6QTextToSpeechMockPluginTargets.cmake:96 (message): The imported target "Qt6::QTextToSpeechMockPlugin" references the file "/usr/lib/x86_64-linux-gnu/qt6/plugins/texttospeech/libqtexttospeech_mock.so" but this file does not exist. Possible reasons include: * The file was deleted, renamed, or moved to another location. * An install or uninstall procedure did not complete successfully. * The installation package was faulty and contained "/usr/lib/x86_64-linux-gnu/cmake/Qt6TextToSpeech/Qt6QTextToSpeechMockPluginTargets.cmake" but not all the files it references. Call Stack (most recent call first): /usr/lib/x86_64-linux-gnu/cmake/Qt6TextToSpeech/Qt6QTextToSpeechMockPluginConfig.cmake:61 (include) /usr/lib/x86_64-linux-gnu/cmake/Qt6/QtPublicPluginHelpers.cmake:439 (include) /usr/lib/x86_64-linux-gnu/cmake/Qt6TextToSpeech/Qt6TextToSpeechPlugins.cmake:5 (__qt_internal_include_plugin_packages) /usr/lib/x86_64-linux-gnu/cmake/Qt6TextToSpeech/Qt6TextToSpeechConfig.cmake:133 (include) /usr/lib/x86_64-linux-gnu/cmake/Qt6/Qt6Config.cmake:167 (find_package) plugins/speech/CMakeLists.txt:22 (find_package) Concretely, the pacakge I try to build is hyperborg, available here: https://salsa.debian.org/tinker-team/hyperborg - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmPnXJUACgkQLHwxRsGg ASG3mQ//b0L2GLW6AxJRB9JBKDxulflFHv8BWDGVwS3Yn1FYH3kgLlRonhf6UHAY Hsi5dHTcHbOSL4sArtKslurfzPDOBMvtpHfuf5oGni1WVeQghFMd0kMp7ggGxTRj s5XtZAQSQ/AjroL9VFXZTam4tHsf1o1pW+8niBTN7NdMiE7IaKrU9zvg7fjdYMdv vKi7TQ1NZ/QOnVHT0bKwwHpXcNRKPFWy49NyHBOVzNHTI4wv0+CffX0Wf2t2WNE8 EmlKDPi+VO4nKffF+m4madlmfp7ERGVa1OSmEs8kgEszC+2DQgQsHK5aRA91dqPq SqJH8N9Hm9oNxuoW7G1GQpeqjD4RwvmdXa6htBMlfl29QuO6X11SRtkmxgp7ZrCq GElYE61Z97+OduOhjb5AEIym0At5q4BWnDVj341lQctIOAEBsImFuasDI1SCSH5/ Kvc1ac27whPt42pcqg0Xmo57f0m2i5LNO0RhHAALgw+e1ZUzUdmBffflFvVQKrM3 vEq6fLHicXP9MiKFLtEU1pCWp/iCWEWkoPqbcaMugAkDgqlp5hFbLsM/FppYFm1p IrsrhyYnTtrsZRJ0p23pxxGV1cRNDv6roq/Rev0pppuQnQVLOckZNca01otgfjaM MOuIV3YKJ8imBgeF1404z/wdhZrEJlPrSIdds6+lQJVtZ2tLqJg= =eV50 -END PGP SIGNATURE-
Bug#1031072: librust-rspotify-dev is not installable
The following packages have unmet dependencies: librust-rspotify-dev : Depends: librust-base64-0.12+default-dev Depends: librust-itertools-0.9+default-dev Depends: librust-rand-0.7+default-dev Depends: librust-reqwest-0.9+default-dev but it is not installable As far as I can tell, rspotify was packaged as a dependency of spotify-tui. The problem is that while there is a new version of rspotify that has modernised dependencies, spotify-tui was never updated to modernise it's dependencies and was eventually removed from Debian. https://github.com/Rigellute/spotify-tui/issues/915 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018166 I don't think there is much value in fixing this package, until/unless either spotify-tui is updated upstream and someone wants to get it back into Debian or some other package comes up that needs rspotify
Bug#1030971: marked as done (rust-configparser: autopkgtest failure)
Your message dated Sat, 11 Feb 2023 08:37:20 +
with message-id
and subject line Bug#1030971: fixed in rust-configparser 3.0.2-1
has caused the Debian Bug report #1030971,
regarding rust-configparser: autopkgtest failure
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1030971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030971
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-configparser
Version: 2.0.0-2
Severity: serious
https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-configparser/31203190/log.gz
...
running 2 tests
Error: Os { code: 13, kind: PermissionDenied, message: "Permission denied" }
Error: Os { code: 13, kind: PermissionDenied, message: "Permission denied" }
test non_cs ... FAILED
test cs ... FAILED
failures:
non_cs stdout
thread 'non_cs' panicked at 'assertion failed: `(left == right)`
left: `1`,
right: `0`: the test returned a termination value with a non-zero status code
(1) which indicates a failure',
/usr/src/rustc-1.63.0/library/test/src/lib.rs:184:5
stack backtrace:
0: rust_begin_unwind
at /usr/src/rustc-1.63.0/library/std/src/panicking.rs:584:5
1: core::panicking::panic_fmt
at /usr/src/rustc-1.63.0/library/core/src/panicking.rs:142:14
2: core::panicking::assert_failed_inner
3: core::panicking::assert_failed
at /usr/src/rustc-1.63.0/library/core/src/panicking.rs:181:5
4: test::assert_test_result
at /usr/src/rustc-1.63.0/library/test/src/lib.rs:184:5
5: test::non_cs::{{closure}}
at ./tests/test.rs:5:1
6: core::ops::function::FnOnce::call_once
at /usr/src/rustc-1.63.0/library/core/src/ops/function.rs:248:5
7: core::ops::function::FnOnce::call_once
at /usr/src/rustc-1.63.0/library/core/src/ops/function.rs:248:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose
backtrace.
cs stdout
thread 'cs' panicked at 'assertion failed: `(left == right)`
left: `1`,
right: `0`: the test returned a termination value with a non-zero status code
(1) which indicates a failure',
/usr/src/rustc-1.63.0/library/test/src/lib.rs:184:5
stack backtrace:
0: rust_begin_unwind
at /usr/src/rustc-1.63.0/library/std/src/panicking.rs:584:5
1: core::panicking::panic_fmt
at /usr/src/rustc-1.63.0/library/core/src/panicking.rs:142:14
2: core::panicking::assert_failed_inner
3: core::panicking::assert_failed
at /usr/src/rustc-1.63.0/library/core/src/panicking.rs:181:5
4: test::assert_test_result
at /usr/src/rustc-1.63.0/library/test/src/lib.rs:184:5
5: test::cs::{{closure}}
at ./tests/test.rs:108:1
6: core::ops::function::FnOnce::call_once
at /usr/src/rustc-1.63.0/library/core/src/ops/function.rs:248:5
7: core::ops::function::FnOnce::call_once
at /usr/src/rustc-1.63.0/library/core/src/ops/function.rs:248:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose
backtrace.
failures:
cs
non_cs
test result: FAILED. 0 passed; 2 failed; 0 ignored; 0 measured; 0 filtered out;
finished in 0.01s
error: test failed, to rerun pass `--test test`
autopkgtest [02:09:53]: test librust-configparser-dev:: ---]
autopkgtest [02:09:53]: test librust-configparser-dev:: - - - - - - - - - -
results - - - - - - - - - -
librust-configparser-dev: FAIL non-zero exit status 101
autopkgtest [02:09:53]: summary
rust-configparser:@ FAIL non-zero exit status 101
librust-configparser-dev:default FAIL non-zero exit status 101
librust-configparser-dev: FAIL non-zero exit status 101
--- End Message ---
--- Begin Message ---
Source: rust-configparser
Source-Version: 3.0.2-1
Done: Blair Noctis
We believe that the bug you reported is fixed in the latest version of
rust-configparser, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1030...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Blair Noctis (supplier of updated rust-configparser package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Bug#1030907: marked as done (umap-learn: FTBFS (failing tests))
Your message dated Sat, 11 Feb 2023 08:38:12 + with message-id and subject line Bug#1030907: fixed in umap-learn 0.5.3+dfsg-1 has caused the Debian Bug report #1030907, regarding umap-learn: FTBFS (failing tests) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1030907: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030907 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:umap-learn Version: 0.4.5+dfsg-3 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in bookworm, your package failed to build: [...] debian/rules binary-indep dh binary-indep --with python3 --buildsystem=pybuild dh_update_autotools_config -i -O--buildsystem=pybuild dh_autoreconf -i -O--buildsystem=pybuild dh_auto_configure -i -O--buildsystem=pybuild I: pybuild base:240: python3.11 setup.py config running config dh_auto_build -i -O--buildsystem=pybuild I: pybuild base:240: /usr/bin/python3 setup.py build running build running build_py creating /<>/.pybuild/cpython3_3.11/build/umap copying umap/spectral.py -> /<>/.pybuild/cpython3_3.11/build/umap copying umap/sparse_nndescent.py -> /<>/.pybuild/cpython3_3.11/build/umap [... snipped ...] FAILED umap/tests/test_umap_nn.py::test_sparse_nn_search - numba.core.errors FAILED umap/tests/test_umap_on_iris.py::test_initialized_umap_trustworthiness_on_iris FAILED umap/tests/test_umap_on_iris.py::test_umap_trustworthiness_on_sphere_iris FAILED umap/tests/test_umap_on_iris.py::test_umap_transform_on_iris - numba.c... FAILED umap/tests/test_umap_on_iris.py::test_umap_transform_on_iris_modified_dtype FAILED umap/tests/test_umap_on_iris.py::test_umap_sparse_transform_on_iris - ... FAILED umap/tests/test_umap_ops.py::test_blobs_cluster - numba.core.errors.Lo... FAILED umap/tests/test_umap_ops.py::test_multi_component_layout - numba.core FAILED umap/tests/test_umap_ops.py::test_umap_transform_embedding_stability FAILED umap/tests/test_umap_repeated_data.py::test_repeated_points_large_sparse_spatial FAILED umap/tests/test_umap_repeated_data.py::test_repeated_points_small_sparse_spatial FAILED umap/tests/test_umap_repeated_data.py::test_repeated_points_large_dense_spatial FAILED umap/tests/test_umap_repeated_data.py::test_repeated_points_small_dense_spatial FAILED umap/tests/test_umap_repeated_data.py::test_repeated_points_large_sparse_binary FAILED umap/tests/test_umap_repeated_data.py::test_repeated_points_small_sparse_binary FAILED umap/tests/test_umap_repeated_data.py::test_repeated_points_large_dense_binary FAILED umap/tests/test_umap_repeated_data.py::test_repeated_points_small_dense_binary FAILED umap/tests/test_umap_repeated_data.py::test_repeated_points_large_n - ... FAILED umap/tests/test_umap_trustworthiness.py::test_umap_sparse_trustworthiness FAILED umap/tests/test_umap_trustworthiness.py::test_umap_trustworthiness_fast_approx FAILED umap/tests/test_umap_trustworthiness.py::test_umap_trustworthiness_random_init FAILED umap/tests/test_umap_trustworthiness.py::test_supervised_umap_trustworthiness FAILED umap/tests/test_umap_trustworthiness.py::test_semisupervised_umap_trustworthiness FAILED umap/tests/test_umap_trustworthiness.py::test_metric_supervised_umap_trustworthiness FAILED umap/tests/test_umap_trustworthiness.py::test_string_metric_supervised_umap_trustworthiness FAILED umap/tests/test_umap_trustworthiness.py::test_discrete_metric_supervised_umap_trustworthiness FAILED umap/tests/test_umap_trustworthiness.py::test_count_metric_supervised_umap_trustworthiness FAILED umap/tests/test_umap_validation_params.py::test_haversine_on_highd - n... FAILED umap/tests/test_umap_validation_params.py::test_umap_haversine_embed_to_highd FAILED umap/tests/test_umap_validation_params.py::test_umap_too_many_neighbors_warns FAILED umap/tests/test_umap_validation_params.py::test_umap_fit_data_and_targets_compliant FAILED umap/tests/test_umap_validation_params.py::test_umap_fit_instance_returned ERROR umap/tests/test_umap_on_iris.py::test_umap_trustworthiness_on_iris - nu... ERROR umap/tests/test_umap_on_iris.py::test_umap_clusterability_on_supervised_iris ERROR umap/tests/test_umap_on_iris.py::test_umap_inverse_transform_on_iris - ... === 56 failed, 66 passed, 2 xfailed, 20 warnings, 3 errors in 48.47s === E: pybuild pybuild:388: test: plugin custom failed with: exit code=1: PYTHONPATH=/<>/.pybuild/cpython3_3.11/build python3.11 -m pytest dh_auto_test: error: pybuild --test --test-pytest -i
Bug#996042: Missing sources for the html part
retitle 996042 rebuild inline html from source thanks Current status: * the sources in html/* are complete (already since some ttyd releases ago) * not all required node-* packages are in debian to build html.h * some of the required node-* packages that are in debian are still in too old versions and need to be updated by their maintainers (see bugs that are blocking this one) Regards, Daniel
Processed: Re: Missing sources for the html part
Processing commands for cont...@bugs.debian.org: > retitle 996042 rebuild inline html from source Bug #996042 [ttyd] Missing sources for the html part Changed Bug title to 'rebuild inline html from source' from 'Missing sources for the html part'. > thanks Stopping processing here. Please contact me if you need assistance. -- 996042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996042 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
