Bug#1050549: src:r-cran-remotes: fails to migrate to testing for too long: autopkgtest regression
Source: r-cran-remotes Version: 2.4.2-1 Severity: serious Control: close -1 2.4.2.1+dfsg-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:r-cran-remotes has been trying to migrate for 35 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=r-cran-remotes OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: src:r-cran-remotes: fails to migrate to testing for too long: autopkgtest regression
Processing control commands: > close -1 2.4.2.1+dfsg-1 Bug #1050549 [src:r-cran-remotes] src:r-cran-remotes: fails to migrate to testing for too long: autopkgtest regression Marked as fixed in versions r-cran-remotes/2.4.2.1+dfsg-1. Bug #1050549 [src:r-cran-remotes] src:r-cran-remotes: fails to migrate to testing for too long: autopkgtest regression Marked Bug as done -- 1050549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050549 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1050526: dask: autopkgtest regression on s390x
Hi,
I'm kind of shocked I think I found a fix.
I looked a little bit, and it seems like the random number generator
behaves differently between s390x and x86
Eventually the test calls dask.util.random_state_data(1, 42)
on x86 it starts with this on two different machines:
In [9]: random_state_data(1, 0)
Out[9]:
[array([2357136044, 2546248239, 3071714933, 3626093760, 2588848963,
3684848379, 2340255427, 3638918503, 1819583497, 2678185683,
2774094101, 1650906866, 1879422756, 1277901399, 3830135878,
243580376, 4138900056, 1171049868, 1646868794, 2051556033,
3400433126, 3488238119, 2271586391, 2061486254, 2439732824,
1686997841, 3975407269, 3590930969, 305097549, 1449105480,
374217481, 2783877012, 86837363, 1581585360, 3576074995,
and on s390x it starts with
In [16]: random_state_data(1, 42)
Out[16]:
[array([1725751647, 3007179467, 1543725811, 244708654, 1794401211,
1205115335, 3165536665, 338480024, 1725362215, 2031624818,
3527536423, 3606353689, 1251073550, 3394605429, 1471725021,
1961717077, 1672274585, 1743491620, 2537440437, 2191564966,
2500216069, 889024526, 16993528, 1474942136, 3958708949,
2650621168, 635132726, 2164863744, 3205794862, 3146973694,
345633582, 2688816030, 3419529805, 961385884, 359683718,
Digging further there's a place where they convert some random bytes
into unsigned int 32s using numpy.frombuffer.
I added some code to force little endian byte order on the buffer, and
after that random_state_data returns the same list of values on s390x.
So hopefully will then generate the same random values as x86_64.
Roughly the likely change.
===
--- dask-2023.8.0+dfsg.orig/dask/utils.py
+++ dask-2023.8.0+dfsg/dask/utils.py
@@ -426,7 +426,9 @@ def random_state_data(n: int, random_sta
random_state = np.random.RandomState(random_state)
random_data = random_state.bytes(624 * n * 4) # `n * 624` 32-bit
integers
-l = list(np.frombuffer(random_data, dtype=np.uint32).reshape((n, -
1)))
+dt = np.dtype(np.uint32)
+dt = dt.newbyteorder("<")
+l = list(np.frombuffer(random_data, dtype=dt).reshape((n, -1)))
assert len(l) == n
return l
signature.asc
Description: This is a digitally signed message part
Processed: limit source to gnustep-base, tagging 1050528
Processing commands for cont...@bugs.debian.org: > limit source gnustep-base Limiting to bugs with field 'source' containing at least one of 'gnustep-base' Limit currently set to 'source':'gnustep-base' > tags 1050528 + pending Bug #1050528 [src:gnustep-base] gnustep-base: autopkgtest needs update for new version of tzdata Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1050528: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050528 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1041687: marked as done (src:accountsservice: fails to migrate to testing for too long: FTBFS)
Your message dated Sat, 26 Aug 2023 02:33:59 + with message-id and subject line Bug#1041687: fixed in accountsservice 23.13.9-3 has caused the Debian Bug report #1041687, regarding src:accountsservice: fails to migrate to testing for too long: FTBFS 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.) -- 1041687: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041687 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: accountsservice Version: 22.08.8-6 Severity: serious Control: close -1 23.13.9-2 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1038865 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:accountsservice has been trying to migrate for 31 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=accountsservice OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: accountsservice Source-Version: 23.13.9-3 Done: Gunnar Hjalmarsson We believe that the bug you reported is fixed in the latest version of accountsservice, 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 1041...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gunnar Hjalmarsson (supplier of updated accountsservice 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: SHA256 Format: 1.8 Date: Sat, 26 Aug 2023 03:37:58 +0200 Source: accountsservice Built-For-Profiles: noudeb Architecture: source Version: 23.13.9-3 Distribution: unstable Urgency: medium Maintainer: Debian freedesktop.org maintainers Changed-By: Gunnar Hjalmarsson Closes: 1038865 1041687 Changes: accountsservice (23.13.9-3) unstable; urgency=medium . * Team upload * debian/patches/Disable-test_languages.patch - Temporary measure to work around failed test when building (closes: #1038865, #1041687). Checksums-Sha1: 77ae3584b0b5e47b67c93309d4dfc88fa96f10bf 2589 accountsservice_23.13.9-3.dsc 0b004f7214f8a6f2511ac67f2a240c94473f5b5d 22088 accountsservice_23.13.9-3.debian.tar.xz 9440c73ae21fdd0b5fc5ed92979834bdb71cabd8 11618 accountsservice_23.13.9-3_source.buildinfo Checksums-Sha256: 92908a6e27860f63b35b4be33b78b1c1408969e9d2491a98c6dfb134a16ecc41 2589 accountsservice_23.13.9-3.dsc 8e204fb3bd2ef1592d239753328de8ef5caf257f680894250331984790c25e55 22088 accountsservice_23.13.9-3.debian.tar.xz 3095713c612f2b482241981db88292fc9332ba9959b82bb99befe0d82f76 11618 accountsservice_23.13.9-3_source.buildinfo Files: 0743fee52af28c8c97904da379930a1b 2589 admin optional accountsservice_23.13.9-3.dsc 85b969923a0e48b6b78527d0aba92e67 22088 admin optional accountsservice_23.13.9-3.debian.tar.xz f62546094aa9ab2b887bcd686f331d61 11618 admin optional accountsservice_23.13.9-3_source.buildinfo -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEDP6Ze3JFgKf6cvjP8LEQ51ppLzIFAmTpWOgACgkQ8LEQ51pp LzKjHAgApQyLxrwG
Bug#1038865: marked as done (accountsservice FTBFS: FAIL: test_languages (__main__.Tests.test_languages))
Your message dated Sat, 26 Aug 2023 02:33:59 +
with message-id
and subject line Bug#1038865: fixed in accountsservice 23.13.9-3
has caused the Debian Bug report #1038865,
regarding accountsservice FTBFS: FAIL: test_languages
(__main__.Tests.test_languages)
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.)
--
1038865: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038865
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: accountsservice
Version: 23.13.9-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=accountsservice&ver=23.13.9-1
(m68k and sh4 are building with nocheck)
...
=== 16/18
test: accountsservice:accounts-service+daemon+Tests /
Tests.test_languages
start time: 15:06:49
duration: 0.57s
result: exit status 1
command: top_srcdir=/<> G_MESSAGES_DEBUG=all
GI_TYPELIB_PATH=/<>/obj-x86_64-linux-gnu/src/libaccountsservice
top_builddir=/<>/obj-x86_64-linux-gnu
LD_LIBRARY_PATH=/<>/obj-x86_64-linux-gnu/src/libaccountsservice
MALLOC_PERTURB_=218 G_DEBUG=fatal-criticals
MOCKLIBC_LD_PRELOAD=/<>/obj-x86_64-linux-gnu/subprojects/mocklibc-1.0/src/libmocklibc.so.0.0.0
/usr/bin/python3 /<>/obj-x86_64-linux-gnu/../tests/test-daemon.py
Tests.test_languages
--- stdout ---
(process:2978577): GLib-GIO-DEBUG: 15:06:49.432: Using cross-namespace EXTERNAL
authentication (this will deadlock if server is GDBus < 2.73.3)
1687360009.656 SetAllowed ["org.freedesktop.accounts.change-own-user-data",
"org.freedesktop.accounts.user-administration"]
1687360009.675 GetAll /org/freedesktop/PolicyKit1/Authority
org.freedesktop.PolicyKit1.Authority
1687360009.775 CheckAuthorization dbus.Struct((dbus.String('system-bus-name'),
dbus.Dictionary({dbus.String('name'): dbus.String(':1.0', variant_level=1)},
signature=dbus.Signature('sv'))), signature=None)
"org.freedesktop.accounts.user-administration" {} 0 ""
(process:2978577): GLib-DEBUG: 15:06:49.818: unsetenv() is not thread-safe and
should not be used after threads are created
(process:2978577): GLib-DEBUG: 15:06:49.818: unsetenv() is not thread-safe and
should not be used after threads are created
(process:2978577): GLib-DEBUG: 15:06:49.818: unsetenv() is not thread-safe and
should not be used after threads are created
(process:2978577): GLib-DEBUG: 15:06:49.818: unsetenv() is not thread-safe and
should not be used after threads are created
(process:2978577): GLib-DEBUG: 15:06:49.818: unsetenv() is not thread-safe and
should not be used after threads are created
Testing binaries from local build tree
(/<>/obj-x86_64-linux-gnu/src/accounts-daemon)
--- stderr ---
F
-- daemon log:
** (accounts-daemon:2978611): DEBUG: 15:06:49.667: entering main loop
(accounts-daemon:2978611): GLib-GIO-DEBUG: 15:06:49.669: Using cross-namespace
EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)
** (accounts-daemon:2978611): DEBUG: 15:06:49.670: Changing permission of
/tmp/tmpnnupatsq/var/lib/AccountsService/users/benedict to 0600
** (accounts-daemon:2978611): DEBUG: 15:06:49.670: Changing permission of
/tmp/tmpnnupatsq/var/lib/AccountsService/users/rupert to 0600
** (accounts-daemon:2978611): DEBUG: 15:06:49.670: Changing permission of
/tmp/tmpnnupatsq/var/lib/AccountsService/users/gdm to 0600
(accounts-daemon:2978611): GLib-GIO-DEBUG: 15:06:49.671:
_g_io_module_get_default: Found default implementation local (GLocalVfs) for
?gio-vfs?
** (accounts-daemon:2978611): DEBUG: 15:06:49.671: skipping user: benedict
** (accounts-daemon:2978611): DEBUG: 15:06:49.672: sudo group not found
** (accounts-daemon:2978611): DEBUG: 15:06:49.672: loaded user: rupert
** (accounts-daemon:2978611): DEBUG: 15:06:49.672: skipping user: gdm
** (accounts-daemon:2978611): DEBUG: 15:06:49.672: sudo group not found
** (accounts-daemon:2978611): DEBUG: 15:06:49.672: loaded user: benedict
** (accounts-daemon:2978611): DEBUG: 15:06:49.672: sudo group not found
** (accounts-daemon:2978611): DEBUG: 15:06:49.672: loaded user: gdm
** (accounts-daemon:2978611): DEBUG: 15:06:49.675: failed to load autologin
conf file: Unsupported Display Manager
** (accounts-daemon:2978611): DEBUG: 15:06:49.768: user benedict 1000 not
excluded
** (accounts-daemon:2978611): DEBUG: 15:06:49.768: user gdm 42 excluded
** (accounts-daemon:2978611): DEBUG: 15:06:49.768: user rupert 1001 not excluded
** (accounts
Bug#952583: marked as done (mps-youtube: Mps-youtube failes to find anything because google disabled its api key... and a 2 more minor issues)
Your message dated Fri, 25 Aug 2023 23:21:54 + with message-id and subject line Bug#1050146: Removed package(s) from unstable has caused the Debian Bug report #952583, regarding mps-youtube: Mps-youtube failes to find anything because google disabled its api key... and a 2 more minor issues 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.) -- 952583: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952583 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mps-youtube Version: 0.2.7.1-2 Severity: grave Tags: upstream Justification: renders package unusable Dear Maintainer, It seems that google has disabled mps-youtube's api key, so it can no longer search for videos. Here is the full discussion on the project's github page https://github.com/mps-youtube/mps-youtube/issues/1063 On top of that, please update the info of the package so as to reflect its correct github page (https://github.com/mps-youtube/mps-youtube/), because the one that apt mentions now leads to a 404. And last but not least, please update to v2.8.0. It has been relased ~2 years ago and it will probably have solved the other grave bug report. Thank you. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-4-amd64 (SMP w/2 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages mps-youtube depends on: ii ffmpeg 10:4.2.2-dmo3 ii mpv1:0.32.0-dmo1 ii python33.7.5-3 ii python3-pafy 0.5.2-2 ii python3-pkg-resources 44.0.0-1 Versions of packages mps-youtube recommends: ii libnotify40.7.8-1 ii python3-dbus 1.2.16-1 ii python3-gi3.34.0-6 pn xclip mps-youtube suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 2.9.4-1+rm Dear submitter, as the package mps-youtube 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/1050146 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#877035: marked as done (mps-youtube: crashes with TypeError after search)
Your message dated Fri, 25 Aug 2023 23:21:54 +
with message-id
and subject line Bug#1050146: Removed package(s) from unstable
has caused the Debian Bug report #877035,
regarding mps-youtube: crashes with TypeError after search
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.)
--
877035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877035
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mps-youtube
Version: 0.2.7.1-2
Severity: grave
Justification: renders package unusable
mpsyt crashes whenever I try to do a search:
Searching for 'radiohead'
Traceback (most recent call last):
File "/usr/bin/mpsyt", line 11, in
load_entry_point('mps-youtube==0.2.7.1', 'console_scripts', 'mpsyt')()
File "/usr/lib/python3/dist-packages/mps_youtube/main.py", line 141, in main
if matchfunction(i.function, i.regex, userinput):
File "/usr/lib/python3/dist-packages/mps_youtube/main.py", line 64, in
matchfunction
func(*matches)
File "/usr/lib/python3/dist-packages/mps_youtube/commands/search.py", line
212, in search
_search(term, query, msg, failmsg)
File "/usr/lib/python3/dist-packages/mps_youtube/commands/search.py", line
41, in _search
loadmsg=loadmsg)
File "/usr/lib/python3/dist-packages/mps_youtube/commands/songlist.py", line
56, in paginatesongs
songs = func[s:e]
File "/usr/lib/python3/dist-packages/mps_youtube/util.py", line 47, in
__getitem__
self.ilist.append(next(self.iterable))
File "/usr/lib/python3/dist-packages/mps_youtube/commands/search.py", line
28, in iter_songs
for song in get_tracks_from_json(wdata2):
File "/usr/lib/python3/dist-packages/mps_youtube/commands/search.py", line
342, in get_tracks_from_json
'id': ','.join([get_track_id_from_json(i) for i in items])}
TypeError: sequence item 9: expected str instance, dict found
Other searches produce slightly different tracebacks, this time after
the search seemingly has returned:
Traceback (most recent call last):
File "/usr/lib/python3.5/threading.py", line 914, in _bootstrap_inner
self.run()
File "/usr/lib/python3.5/threading.py", line 862, in run
self._target(*self._args, **self._kwargs)
File "/usr/lib/python3/dist-packages/mps_youtube/streams.py", line 171, in
_preload
streamlist = get(song)
File "/usr/lib/python3/dist-packages/mps_youtube/streams.py", line 51, in get
p = util.get_pafy(vid, force=force, callback=callback)
File "/usr/lib/python3/dist-packages/mps_youtube/util.py", line 201, in
get_pafy
p = pafy.new(ytid, callback=callback_fn)
File "/usr/lib/python3/dist-packages/pafy/pafy.py", line 122, in new
return Pafy(url, basic, gdata, size, callback, ydl_opts)
File "/usr/lib/python3/dist-packages/pafy/backend_youtube_dl.py", line 29, in
__init__
super(YtdlPafy, self).__init__(*args, **kwargs)
File "/usr/lib/python3/dist-packages/pafy/backend_shared.py", line 95, in
__init__
self._fetch_basic()
File "/usr/lib/python3/dist-packages/pafy/backend_youtube_dl.py", line 53, in
_fetch_basic
self._category = self._ydl_info['categories'][0]
TypeError: 'NoneType' object is not subscriptable
In any event, the package is unusable as is.
Thanks.
jamie.
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (600, 'testing'), (500, 'stable'), (200, 'unstable'), (101,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.12.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages mps-youtube depends on:
ii ffmpeg 7:3.3.4-1
ii mpv0.26.0-3
ii python33.5.3-3
ii python3-pafy 0.5.2-2
ii python3-pkg-resources 36.2.7-2
Versions of packages mps-youtube recommends:
ii libnotify40.7.7-2
ii python3-dbus 1.2.4-1+b2
ii python3-gi3.24.1-3
ii xclip 0.12+svn84-4+b1
mps-youtube suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 2.9.4-1+rm
Dear submitter,
as the package mps-youtube 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/1050146
The version of this package that was in Debian prior to this removal
can still be found using
Bug#855453: marked as done (mps-youtube can't search anything)
Your message dated Fri, 25 Aug 2023 23:21:54 + with message-id and subject line Bug#1050146: Removed package(s) from unstable has caused the Debian Bug report #855453, regarding mps-youtube can't search anything 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.) -- 855453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855453 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mps-youtube Version: 0.01.46-3 Severity: important All searches yield just Found nothing for ... According to https://github.com/mps-youtube/mps-youtube/issues/401 the 0.01.46 version is broken with current youtube, so probably the jessie version should be increased. -- System Information: Debian Release: 8.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages mps-youtube depends on: ii mplayer2 2.0-728-g2c378c7-4+b1 ii python 2.7.9-1 ii python-pafy 0.3.62-1 mps-youtube recommends no packages. mps-youtube suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 2.9.4-1+rm Dear submitter, as the package mps-youtube 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/1050146 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#832087: marked as done (mps-youtube: Missing dependency python-pkg-resources)
Your message dated Fri, 25 Aug 2023 23:21:54 + with message-id and subject line Bug#1050146: Removed package(s) from unstable has caused the Debian Bug report #832087, regarding mps-youtube: Missing dependency python-pkg-resources 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.) -- 832087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832087 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mps-youtube Version: 0.01.46-3 Severity: serious Justification: 3 Dear Maintainer, I installed mps-youtube and tried to run it: $ mpsyt Traceback (most recent call last): File "/usr/bin/mpsyt", line 5, in from pkg_resources import load_entry_point ImportError: No module named pkg_resources After debug it find out, that package python-pkg-resources is required to use mpsyt, and it is not listed as dependency in mps-youtube package. -- System Information: Debian Release: 8.5 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.6.0-0.bpo.1-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages mps-youtube depends on: ii mplayer2 2.0-728-g2c378c7-4+b1 ii python 2.7.9-1 ii python-pafy 0.3.62-1 mps-youtube recommends no packages. mps-youtube suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 2.9.4-1+rm Dear submitter, as the package mps-youtube 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/1050146 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#1050138: marked as done (rust-wasmer-enumset-derive should not be in trixie)
Your message dated Fri, 25 Aug 2023 23:22:57 + with message-id and subject line Bug#1050158: Removed package(s) from unstable has caused the Debian Bug report #1050138, regarding rust-wasmer-enumset-derive should not be in trixie 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.) -- 1050138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050138 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: rust-wasmer-enumset-derive Version: 0.5.0-2 Severity: serious Tags: trixie, sid rust-wasmer-enumset-derive and it's reverse dependency rust-wasmer-enumset are an abandoned fork of rust-enumset-dervive and rust-enumset, no applications use them anymore so there is no reason to keep them around creating more busywork for the rust team to prevent them blocking semver transitions. --- End Message --- --- Begin Message --- Version: 0.5.0-3+rm Dear submitter, as the package rust-wasmer-enumset-derive 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/1050158 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#1018277: marked as done (gnome-shell-extension-sound-device-chooser: needs update for GNOME Shell 43)
Your message dated Fri, 25 Aug 2023 23:22:24 + with message-id and subject line Bug#1050151: Removed package(s) from unstable has caused the Debian Bug report #1018277, regarding gnome-shell-extension-sound-device-chooser: needs update for GNOME Shell 43 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.) -- 1018277: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018277 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gnome-shell-extension-sound-device-chooser Version: 43-1 Severity: important Tags: bookworm sid User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: gnome-shell-43 This extension has not been checked for compatibility with GNOME Shell 43. Depending how compatible it is, it will either need an update to its metadata.json and debian/control to declare compatibility with the new version, or code changes to adapt it to the new Shell version. If not updated, it will have to be removed from testing for the GNOME Shell 43 transition (see https://bugs.debian.org/1018118 for details). This bug will be raised to serious severity when the transition is ready to go ahead. smcv --- End Message --- --- Begin Message --- Version: 43-1+rm Dear submitter, as the package gnome-shell-extension-sound-device-chooser 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/1050151 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#1042179: marked as done (r-cran-lasso2: FTBFS: lasso.h:46:23: error: unknown type name ‘Sint’; did you mean ‘uint’?)
Your message dated Fri, 25 Aug 2023 23:20:02 + with message-id and subject line Bug#1049998: Removed package(s) from unstable has caused the Debian Bug report #1042179, regarding r-cran-lasso2: FTBFS: lasso.h:46:23: error: unknown type name ‘Sint’; did you mean ‘uint’? 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.) -- 1042179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042179 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: r-cran-lasso2 Version: 1.2-22-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > gcc -I"/usr/share/R/include" -DNDEBUG -fpic -g -O2 > -ffile-prefix-map=/build/r-base-hJdbdy/r-base-4.3.1=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -c lasso.c -o lasso.o > In file included from lasso.c:19: > lasso.h:46:23: error: unknown type name ‘Sint’; did you mean ‘uint’? >46 | void lasso(double *x, Sint *pn, Sint *pm, double *pt, > | ^~~~ > | uint > lasso.h:46:33: error: unknown type name ‘Sint’; did you mean ‘uint’? >46 | void lasso(double *x, Sint *pn, Sint *pm, double *pt, > | ^~~~ > | uint > lasso.h:48:32: error: unknown type name ‘Sint’; did you mean ‘uint’? >48 |double *lagrangian, Sint *psuc, Sint *pverb, Sint > *pas_sub); > |^~~~ > |uint > lasso.h:48:45: error: unknown type name ‘Sint’; did you mean ‘uint’? >48 |double *lagrangian, Sint *psuc, Sint *pverb, Sint > *pas_sub); > | ^~~~ > | uint > lasso.h:48:58: error: unknown type name ‘Sint’; did you mean ‘uint’? >48 |double *lagrangian, Sint *psuc, Sint *pverb, Sint > *pas_sub); > | ^~~~ > | uint > lasso.h:49:28: error: unknown type name ‘Sint’; did you mean ‘uint’? >49 | void mult_lasso(double *x, Sint *pn, Sint *pm, double *pt, Sint *pl, > |^~~~ > |uint > lasso.h:49:38: error: unknown type name ‘Sint’; did you mean ‘uint’? >49 | void mult_lasso(double *x, Sint *pn, Sint *pm, double *pt, Sint *pl, > | ^~~~ > | uint > lasso.h:49:60: error: unknown type name ‘Sint’; did you mean ‘uint’? >49 | void mult_lasso(double *x, Sint *pn, Sint *pm, double *pt, Sint *pl, > |^~~~ > |uint > lasso.h:51:37: error: unknown type name ‘Sint’; did you mean ‘uint’? >51 | double *lagrangian, Sint *psuc, Sint *pverb); > | ^~~~ > | uint > lasso.h:51:49: error: unknown type name ‘Sint’; did you mean ‘uint’? >51 | double *lagrangian, Sint *psuc, Sint *pverb); > | ^~~~ > | uint > lasso.h:52:37: error: unknown type name ‘Sint’; did you mean ‘uint’? >52 | void rs_lasso(double *x, double *y, Sint *pn, Sint *porder, > | ^~~~ > | uint > lasso.h:52:47: error: unknown type name ‘Sint’; did you mean ‘uint’? >52 | void rs_lasso(double *x, double *y, Sint *pn, Sint *porder, > | ^~~~ > | uint > lasso.h:54:23: error: unknown type name ‘Sint’; did you mean ‘uint’? >54 |double *r, Sint *psuc, Sint *pverb, Sint *pas_sub); > | ^~~~ > | uint > lasso.h:54:35: error: unknown type name ‘Sint’; did you mean ‘uint’? >54 |double *r, Sint *psuc, Sint *pverb, Sint *pas_sub); > | ^~~~ > | uint > lasso.h:54:48: error: unknown type name ‘Sint’; di
Bug#1032086: marked as done (Don't include in Bookworm)
Your message dated Fri, 25 Aug 2023 23:19:32 + with message-id and subject line Bug#1049946: Removed package(s) from unstable has caused the Debian Bug report #1032086, regarding Don't include 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.) -- 1032086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032086 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-labstack-echo.v3 Version: 3.3.10-2 Severity: serious This is an older version of src:golang-github-labstack-echo. None of the reverse deps are currently in bookworm, so golang-github-labstack-echo.v3 should be dropped as well (and post freeze the reverse deps fixed and the package removed) --- End Message --- --- Begin Message --- Version: 3.3.10-2+rm Dear submitter, as the package golang-github-labstack-echo.v3 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/1049946 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#1032085: marked as done (Don't include in Bookworm)
Your message dated Fri, 25 Aug 2023 23:18:55 + with message-id and subject line Bug#1049945: Removed package(s) from unstable has caused the Debian Bug report #1032085, regarding Don't include 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.) -- 1032085: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032085 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-labstack-echo.v2 Version: 2.2.0-3 Severity: serious This is an older version of src:golang-github-labstack-echo. None of the reverse deps are currently in bookworm, so golang-github-labstack-echo.v2 should be dropped as well (and post freeze the reverse deps fixed and the package removed) --- End Message --- --- Begin Message --- Version: 2.2.0-3+rm Dear submitter, as the package golang-github-labstack-echo.v2 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/1049945 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#1050535: marked as done (rust-rustls-webpki FTBFS, tests require rcgen.)
Your message dated Fri, 25 Aug 2023 20:51:29 +
with message-id
and subject line Bug#1050535: fixed in rust-rustls-webpki 0.101.4-2
has caused the Debian Bug report #1050535,
regarding rust-rustls-webpki FTBFS, tests require rcgen.
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.)
--
1050535: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050535
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rust-rustls-webpki
Version: 0.101.4-1
Severity: serious
Tags: patch
It seems that in addition to the security fix, the new version of
rustls-webpki added some new tests, these depend on "rcgen" which is
currently patched away by 2001_bencher.patch.
After reinstating the dependency (but NOT the "patch.crates-io" section)
and adding corresponding build and test dependencies I was able to
successfully build the package and run it's autopkgtests.
Debdiff attatched, I may NMU this later (but I'd appreciate a prompt
maintainer upload).
diff -Nru rust-rustls-webpki-0.101.4/debian/changelog
rust-rustls-webpki-0.101.4/debian/changelog
--- rust-rustls-webpki-0.101.4/debian/changelog 2023-08-24 08:06:53.0
+
+++ rust-rustls-webpki-0.101.4/debian/changelog 2023-08-25 18:57:05.0
+
@@ -1,3 +1,13 @@
+rust-rustls-webpki (0.101.4-1.1) UNRELEASED; urgency=high
+
+ * Non-maintainer upload.
+ * Adjust patch 2001, reinstate rcgen dependency, some newly added tests need
+it. Do not reinstate the "patch.crates-io" section since we want to build
+against debian packaged crates, not stuff from github.
+ * Add build and test dependencies on librust-rcgen-0.11+default-dev (>=
0.11.1-2)
+
+ -- Peter Michael Green Fri, 25 Aug 2023 18:57:05 +
+
rust-rustls-webpki (0.101.4-1) unstable; urgency=high
* bump project version in virtual packages and autopkgtests;
diff -Nru rust-rustls-webpki-0.101.4/debian/control
rust-rustls-webpki-0.101.4/debian/control
--- rust-rustls-webpki-0.101.4/debian/control 2023-08-24 08:05:29.0
+
+++ rust-rustls-webpki-0.101.4/debian/control 2023-08-25 18:57:05.0
+
@@ -6,6 +6,7 @@
dh-cargo,
librust-base64-0.21+default-dev ,
librust-ring-0.16+default-dev ,
+ librust-rcgen-0.11+default-dev (>= 0.11.1-2) ,
librust-serde-1+default-dev ,
librust-serde-1+derive-dev ,
librust-serde-json-1+default-dev ,
diff -Nru rust-rustls-webpki-0.101.4/debian/patches/2001_bencher.patch
rust-rustls-webpki-0.101.4/debian/patches/2001_bencher.patch
--- rust-rustls-webpki-0.101.4/debian/patches/2001_bencher.patch
2023-08-24 08:06:28.0 +
+++ rust-rustls-webpki-0.101.4/debian/patches/2001_bencher.patch
2023-08-25 18:56:43.0 +
@@ -15,16 +15,15 @@
include = [
"Cargo.toml",
-@@ -72,9 +73,6 @@
+@@ -72,8 +73,6 @@
[dev-dependencies]
base64 = "0.21"
-bencher = "0.1.5"
-once_cell = "1.17.2"
--rcgen = { version = "0.11.1", default-features = false }
+ rcgen = { version = "0.11.1", default-features = false }
serde = { version = "1.0", features = ["derive"] }
serde_json = "1.0"
-
@@ -93,12 +91,3 @@
lto = true
debug-assertions = false
diff -Nru rust-rustls-webpki-0.101.4/debian/tests/control
rust-rustls-webpki-0.101.4/debian/tests/control
--- rust-rustls-webpki-0.101.4/debian/tests/control 2023-08-24
08:05:35.0 +
+++ rust-rustls-webpki-0.101.4/debian/tests/control 2023-08-25
18:57:05.0 +
@@ -8,6 +8,7 @@
librust-serde-1+default-dev,
librust-serde-1+derive-dev,
librust-serde-json-1+default-dev,
+ librust-rcgen-0.11+default-dev (>= 0.11.1-2),
Restrictions: allow-stderr
Test-Command: SOURCEPACKAGEDIR=$PWD /usr/share/cargo/bin/cargo-auto-test
rustls-webpki 0.101.4
@@ -20,6 +21,7 @@
librust-serde-1+default-dev,
librust-serde-1+derive-dev,
librust-serde-json-1+default-dev,
+ librust-rcgen-0.11+default-dev (>= 0.11.1-2),
Restrictions: allow-stderr
Test-Command: SOURCEPACKAGEDIR=$PWD /usr/share/cargo/bin/cargo-auto-test
rustls-webpki 0.101.4
@@ -32,6 +34,7 @@
librust-serde-1+default-dev,
librust-serde-1+derive-dev,
librust-serde-json-1+default-dev,
+ librust-rcgen-0.11+default-dev (>= 0.11.1-2),
Restrictions: allow-stderr
Test-Command: SOURCEPACKAGEDIR=$PWD /usr/share/cargo/bin/cargo-auto-test
rustls-webpki 0.101.4
@@ -44,6 +47,7 @@
librust-serde-1+default-dev,
librust-serde-1+derive-dev,
librust-serde-json-1+default-dev,
+ librust-rcgen-0.11+default-dev (>= 0.11.1-2),
Restrictions: allow-stderr
Test-Command: SOURCEPACKAGEDIR=$PWD /usr/share/cargo/bin/cargo-auto-test
rustls-webpki 0.101.4
@@
Bug#968312: marked as done (eztrace-contrib: FTBFS with CUDA 11: cuda_runtime.cu(92): error: function "cudaMalloc(void **, size_t)" has already been defined)
Your message dated Fri, 25 Aug 2023 20:41:50 + with message-id and subject line Bug#968312: fixed in eztrace-contrib 2.1-1 has caused the Debian Bug report #968312, regarding eztrace-contrib: FTBFS with CUDA 11: cuda_runtime.cu(92): error: function "cudaMalloc(void **, size_t)" has already been defined 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.) -- 968312: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968312 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: eztrace-contrib Version: 1.1-8-6+contrib Severity: important Tags: ftbfs Justification: fails to build from source Hi, eztrace-contrib FTBFS with CUDA 11 in experimental: ../../../../src/modules/cuda/cuda_runtime.cu(92): error: function "cudaMalloc(void **, size_t)" has already been defined Andreas --- End Message --- --- Begin Message --- Source: eztrace-contrib Source-Version: 2.1-1 Done: Samuel Thibault We believe that the bug you reported is fixed in the latest version of eztrace-contrib, 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 968...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Samuel Thibault (supplier of updated eztrace-contrib 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: Fri, 25 Aug 2023 15:03:30 +0200 Source: eztrace-contrib Binary: libeztrace0-contrib libeztrace0-contrib-dbgsym Architecture: source amd64 Version: 2.1-1 Distribution: unstable Urgency: medium Maintainer: Samuel Thibault Changed-By: Samuel Thibault Description: libeztrace0-contrib - Automatic execution trace generation for HPC - runtime libraries Closes: 968312 Changes: eztrace-contrib (2.1-1) unstable; urgency=medium . * New upstream release (Closes: #968312) - control: Add libnetcdf-dev and libpnetcdf-dev dependencies. - patches/git-arm: Upstreamed. - patches/git-atomic: Upstreamed. - patches/git-eztpomp: Upstreamed. - patches/git-eztrace_cc_path: Upstreamed. - patches/git-eztrace_cc_x: Upstreamed. - patches/git-functions: Upstreamed. - patches/git-input: Upstreamed. - patches/git-libatomic: Upstreamed. - patches/git-manpage: Upstreamed. - patches/git-memory-noopt: Upstreamed. - patches/git-missing-tests: Upstreamed. - patches/git-mpi-init: Upstreamed. - patches/git-mpi-init-called: Upstreamed. - patches/git-mpi-types: Upstreamed. - patches/git-mpi_module_name: Upstreamed. - patches/git-no-install-cmake: Upstreamed. - patches/git-opari2: Upstreamed. - patches/git-openmp-nested-lock: Upstreamed. - patches/git-otf2: Upstreamed. - patches/git-otf2-3: Upstreamed. - patches/git-path_space: Upstreamed. - patches/git-pkg-config: Upstreamed. - patches/git-pkgconfig: Upstreamed. - patches/git-rename: Upstreamed. - patches/git-test-conditioned: Upstreamed. - patches/git-test-mpi-path: Upstreamed. - patches/git-test-openmp: Upstreamed. - patches/git-test-openmp2: Upstreamed. - patches/git-test-path: Upstreamed. - patches/git-test-paths: Upstreamed. - patches/git-test-preload-libs: Upstreamed. - patches/git-test-programs-path: Upstreamed. - patches/git-test-source: Upstreamed. - patches/git-test-verbose: Upstreamed. - patches/otf2-2.0.3: Upstreamed. - patches/starpu-1.3: Upstreamed. - patches/norpath: Refreshed. - patches/werror: Refreshed. - patches/git-starpu-1.4: Fix finding starpu-1.4. - patches/git-starpu-1.4-task_submit: Fix building against starpu 1.4. - patches/starpu-job: Drop some test for now. - patches/git-eztrace_avail: Fix finding eztrace_avail. - patches/git-self-link: Fix linking against libeztpomp. - patches/git-starpu-install: Actually install StarPU module. - libeztrace0.lintian-overrides: Update. - rules: Enable STARPU, NETCDF and PNETCDF (where applicable). - rules: Set STARPU_HOME to CURDIR. - rules: Update blhc ignore patterns. - tests/control: Enable compiler_instrumentation and starpu tests. - libeztrace0-contrib.install: Install only cuda plugin. Chec
Processed: Re: Processed (with 2 errors): test depends on r-cran-rgdal
Processing commands for cont...@bugs.debian.org: > reassign 1050533 src:r-cran-rgeos Bug #1050533 [src:r-cran-exactextractr] test depends on r-cran-rgdal Bug reassigned from package 'src:r-cran-exactextractr' to 'src:r-cran-rgeos'. No longer marked as found in versions r-cran-exactextractr/0.9.1-1. Ignoring request to alter fixed versions of bug #1050533 to the same values previously set > reassign 1050534 src:r-cran-spacetime Bug #1050534 [src:r-cran-exactextractr] test depends on r-cran-rgdal Bug reassigned from package 'src:r-cran-exactextractr' to 'src:r-cran-spacetime'. No longer marked as found in versions r-cran-exactextractr/0.9.1-1. Ignoring request to alter fixed versions of bug #1050534 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1050533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050533 1050534: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050534 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1050535: rust-rustls-webpki FTBFS, tests require rcgen.
Package: rust-rustls-webpki
Version: 0.101.4-1
Severity: serious
Tags: patch
It seems that in addition to the security fix, the new version of
rustls-webpki added some new tests, these depend on "rcgen" which is
currently patched away by 2001_bencher.patch.
After reinstating the dependency (but NOT the "patch.crates-io" section)
and adding corresponding build and test dependencies I was able to
successfully build the package and run it's autopkgtests.
Debdiff attatched, I may NMU this later (but I'd appreciate a prompt
maintainer upload).
diff -Nru rust-rustls-webpki-0.101.4/debian/changelog
rust-rustls-webpki-0.101.4/debian/changelog
--- rust-rustls-webpki-0.101.4/debian/changelog 2023-08-24 08:06:53.0
+
+++ rust-rustls-webpki-0.101.4/debian/changelog 2023-08-25 18:57:05.0
+
@@ -1,3 +1,13 @@
+rust-rustls-webpki (0.101.4-1.1) UNRELEASED; urgency=high
+
+ * Non-maintainer upload.
+ * Adjust patch 2001, reinstate rcgen dependency, some newly added tests need
+it. Do not reinstate the "patch.crates-io" section since we want to build
+against debian packaged crates, not stuff from github.
+ * Add build and test dependencies on librust-rcgen-0.11+default-dev (>=
0.11.1-2)
+
+ -- Peter Michael Green Fri, 25 Aug 2023 18:57:05 +
+
rust-rustls-webpki (0.101.4-1) unstable; urgency=high
* bump project version in virtual packages and autopkgtests;
diff -Nru rust-rustls-webpki-0.101.4/debian/control
rust-rustls-webpki-0.101.4/debian/control
--- rust-rustls-webpki-0.101.4/debian/control 2023-08-24 08:05:29.0
+
+++ rust-rustls-webpki-0.101.4/debian/control 2023-08-25 18:57:05.0
+
@@ -6,6 +6,7 @@
dh-cargo,
librust-base64-0.21+default-dev ,
librust-ring-0.16+default-dev ,
+ librust-rcgen-0.11+default-dev (>= 0.11.1-2) ,
librust-serde-1+default-dev ,
librust-serde-1+derive-dev ,
librust-serde-json-1+default-dev ,
diff -Nru rust-rustls-webpki-0.101.4/debian/patches/2001_bencher.patch
rust-rustls-webpki-0.101.4/debian/patches/2001_bencher.patch
--- rust-rustls-webpki-0.101.4/debian/patches/2001_bencher.patch
2023-08-24 08:06:28.0 +
+++ rust-rustls-webpki-0.101.4/debian/patches/2001_bencher.patch
2023-08-25 18:56:43.0 +
@@ -15,16 +15,15 @@
include = [
"Cargo.toml",
-@@ -72,9 +73,6 @@
+@@ -72,8 +73,6 @@
[dev-dependencies]
base64 = "0.21"
-bencher = "0.1.5"
-once_cell = "1.17.2"
--rcgen = { version = "0.11.1", default-features = false }
+ rcgen = { version = "0.11.1", default-features = false }
serde = { version = "1.0", features = ["derive"] }
serde_json = "1.0"
-
@@ -93,12 +91,3 @@
lto = true
debug-assertions = false
diff -Nru rust-rustls-webpki-0.101.4/debian/tests/control
rust-rustls-webpki-0.101.4/debian/tests/control
--- rust-rustls-webpki-0.101.4/debian/tests/control 2023-08-24
08:05:35.0 +
+++ rust-rustls-webpki-0.101.4/debian/tests/control 2023-08-25
18:57:05.0 +
@@ -8,6 +8,7 @@
librust-serde-1+default-dev,
librust-serde-1+derive-dev,
librust-serde-json-1+default-dev,
+ librust-rcgen-0.11+default-dev (>= 0.11.1-2),
Restrictions: allow-stderr
Test-Command: SOURCEPACKAGEDIR=$PWD /usr/share/cargo/bin/cargo-auto-test
rustls-webpki 0.101.4
@@ -20,6 +21,7 @@
librust-serde-1+default-dev,
librust-serde-1+derive-dev,
librust-serde-json-1+default-dev,
+ librust-rcgen-0.11+default-dev (>= 0.11.1-2),
Restrictions: allow-stderr
Test-Command: SOURCEPACKAGEDIR=$PWD /usr/share/cargo/bin/cargo-auto-test
rustls-webpki 0.101.4
@@ -32,6 +34,7 @@
librust-serde-1+default-dev,
librust-serde-1+derive-dev,
librust-serde-json-1+default-dev,
+ librust-rcgen-0.11+default-dev (>= 0.11.1-2),
Restrictions: allow-stderr
Test-Command: SOURCEPACKAGEDIR=$PWD /usr/share/cargo/bin/cargo-auto-test
rustls-webpki 0.101.4
@@ -44,6 +47,7 @@
librust-serde-1+default-dev,
librust-serde-1+derive-dev,
librust-serde-json-1+default-dev,
+ librust-rcgen-0.11+default-dev (>= 0.11.1-2),
Restrictions: allow-stderr
Test-Command: SOURCEPACKAGEDIR=$PWD /usr/share/cargo/bin/cargo-auto-test
rustls-webpki 0.101.4
@@ -56,4 +60,5 @@
librust-serde-1+default-dev,
librust-serde-1+derive-dev,
librust-serde-json-1+default-dev,
+ librust-rcgen-0.11+default-dev (>= 0.11.1-2),
Restrictions: allow-stderr
Bug#965847: marked as done (tralics: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Fri, 25 Aug 2023 19:33:24 + with message-id and subject line Bug#965847: fixed in tralics 2.14.4-2.1 has caused the Debian Bug report #965847, regarding tralics: 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.) -- 965847: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965847 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tralics Version: 2.14.4-2 Severity: normal Usertags: compat-5-6-removal Hi, The package tralics 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 --- Source: tralics Source-Version: 2.14.4-2.1 Done: Thiago Marques Siqueira We believe that the bug you reported is fixed in the latest version of tralics, 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 965...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thiago Marques Siqueira (supplier of updated tralics 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: Mon, 14 Aug 2023 22:32:29 +0100 Source: tralics Architecture: source Version: 2.14.4-2.1 Distribution: unstable Urgency: medium Maintainer: Zbigniew Jędrzejewski-Szmek Changed-By: Thiago Marques Siqueira Closes: 965847 Changes: tralics (2.14.4-2.1) unstable; urgency=medium . * Non-maintainer upload. * Using new DH level format. Consequently: - debian/compat: removed. - debian/control: changed from 'debhelper' to 'debhelper-compat' in Build-Depends field and bumped level to 13. - Closes: #965847 Checksums-Sha1: 00c128ddbec8fff7cc8d36640a4e401743797fcd 1740 tralics_2.14.4-2.1.dsc 66f6318485471f335c3f9ae8934a7c783e05fd72 4616 tralics_2.14.4-2.1.debian.tar.xz 2caf18710d600c9da762dd2fb73b9b06900fc13e 6008 tralics_2.14.4-2.1_source.buildinfo Checksums-Sha256: 52641e77ae580b466ba2af63efbdeb28e025c0e5acb9ffc5c13f5e9d4b5ac12f 1740 tralics_2.14.4-2.1.dsc cf2b111e97180d33ffdbb355f0cfa1ed0d25a318daf3ef640ed6f64ff19fa3ba 4616 tralics_2.14.4-2.1.debian.tar.xz 04e9a831d015ee91f9a719e3d810c1497a3d2964164e2126a2e2d7b6da46f0d4 6008 tralics_2.14.4-2.1_source.buildinfo Files: c4145bbfd259dc09ebbd0ef464ad14ce 1740 tex optional tralics_2.14.4-2.1.dsc 9d230227a66c0282f52c7027e5a2e46d 4616 tex optional tralics_2.14.4-2.1.debian.tar.xz 237e43c45483d703b25b35a465b0d40b 6008 tex optional tralics_2.14.4-2.1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAmTbv2MACgkQ3mO5xwTr 6e9Dpw//RDmyXhjn9hRNFRNdeBSjNPx0qdq7VEvAmSp154ns6RfYPweIXV30AuMS tBvXNnUbSJ/1Imlx11rDyKmAulIS4xaUfTdIHGwYa0AiTpM6tDhVMdmcW9uBSxE5 F9+M1Z38l4IVSCgRaBQzF1wEVA0BiRRhqGARcre8LLaUEr8ExmTQjtfHz/af/bNI VdabpP3pqHYD8crHafWc07lemCDA3zkMeI4SvShp8j3S4L0YeaLra2n/9B60pDim 3x6pzXQWrAN72OcfvtrmzoUwUGH4FB2yingW2A6mn+tTFsqQzspyQyQv0i8ZflpJ Sl4Pzw3T3DaOzbq1gCYqIt8U6KXt68p3a1xI+AKwEs3IXpsO0aOY7gCbwlt1qn/2 vPCNqkSMaY8Lsx1ytQC8CmlEEtDbmlX4+eWTPKw92WffTa5/DPq9bzdD8UwuIx2k BHFLOu05iqbyH586cTWP0EgYfo9rYL9I0NiJr1AjDbVIXAZliN/rHr4J+O9ADrhE Av7IT7z15g6Ja+3wjjoVXlAVkNhStOCHgTvJxktPhZQN5T63ZDeu4Ci8k44FEymF Dq+O9EkL22zgep69+VTVIyl2sSSMP9IWZ+Q2J
Bug#1050532: test depends on r-cran-rgdal
Source: r-cran-exactextractr Version: 0.9.1-1 Severity: serious Tags: sid trixie Control: clone -1 -2 -3 Control: reassign -2 r-cran-rgeos/0.6-4-1 Control: reassign -3 r-cran-spacetime/1.3-0+dfsg-1 Dear maintainer(s), Your package has an autopkgtest, great. However it test depends on r-cran-rgdal which is going to be removed from testing (see bug 1049438). Can you please change your tests such that they don't need r-cran-rgdal? Paul OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1050462: gtg: crashes on startup often
Dear Antonio, thanks for the crash report! I can reproduce it easily with unstable distribution and the call stack points to pango_font_description_to_string method. The issues seems to have been already reported upstream [1] and the suggested worj around is to add "font_name = Sans 11" in the [browser] section of the ~/.config/gtg/gtg.conf config file. I've checked the fix and no more crash occurs, so it could be integrated as a quilt patch for the Debian package. Best Regards, François [1] https://github.com/getting-things-gnome/gtg/issues/961#issuecomment-1475321154 signature.asc Description: This is a digitally signed message part
Processed (with 2 errors): test depends on r-cran-rgdal
Processing control commands: > clone -1 -2 -3 Bug #1050532 [src:r-cran-exactextractr] test depends on r-cran-rgdal Bug 1050532 cloned as bugs 1050533-1050534 > reassign -2 r-cran-rgeos/0.6-4-1 Unknown command or malformed arguments to command. > reassign -3 r-cran-spacetime/1.3-0+dfsg-1 Unknown command or malformed arguments to command. -- 1050532: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050532 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: python3.11: autopkgtest needs update for new version of tzdata
Processing control commands: > affects -1 src:tzdata Bug #1050530 [src:python3.11] python3.11: autopkgtest needs update for new version of tzdata Added indication that 1050530 affects src:tzdata -- 1050530: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050530 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1050530: python3.11: autopkgtest needs update for new version of tzdata
Source: python3.11 Version: 3.11.4-1 Severity: serious X-Debbugs-CC: tzd...@packages.debian.org Tags: sid trixie User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:tzdata Dear maintainer(s), With a recent upload of tzdata the autopkgtest of python3.11 fails in testing when that autopkgtest is run with the binary packages of tzdata from unstable. It passes when run with only packages from testing. In tabular form: passfail tzdata from testing2023c-10 python3.11 from testing3.11.4-1 all others from testingfrom testing I copied some of the output at the bottom of this report. I note that src:tzdata recently introduced a tzdata-legacy package although I don't know if that has to do with the failure. Currently this regression is blocking the migration of tzdata to testing [1]. Of course, tzdata shouldn't just break your autopkgtest (or even worse, your package), but it seems to me that the change in tzdata was intended and your package needs to update to the new situation. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=tzdata https://ci.debian.net/data/autopkgtest/testing/amd64/p/python3.11/37127326/log.gz 1107s == 1107s FAIL: test_variable_tzname (test.test_email.test_utils.LocaltimeTests.test_variable_tzname) 1107s -- 1107s Traceback (most recent call last): 1107s File "/usr/lib/python3.11/test/support/__init__.py", line 847, in inner 1107s return func(*args, **kwds) 1107s^^^ 1107s File "/usr/lib/python3.11/test/test_email/test_utils.py", line 155, in test_variable_tzname 1107s self.assertEqual(t1.tzname(), 'MSK') 1107s AssertionError: 'Europe' != 'MSK' 1107s - Europe 1107s + MSK OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1050529: python3.12: autopkgtest needs update for new version of tzdata
Source: python3.12 Version: 3.12.0~rc1-1 Severity: serious X-Debbugs-CC: tzd...@packages.debian.org Tags: sid trixie User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:tzdata Dear maintainer(s), With a recent upload of tzdata the autopkgtest of python3.12 fails in testing when that autopkgtest is run with the binary packages of tzdata from unstable. It passes when run with only packages from testing. In tabular form: passfail tzdata from testing2023c-10 python3.12 from testing3.12.0~rc1-1 all others from testingfrom testing I copied some of the output at the bottom of this report. I note that src:tzdata recently introduced a tzdata-legacy package although I don't know if that has to do with the failure. Currently this regression is blocking the migration of tzdata to testing [1]. Of course, tzdata shouldn't just break your autopkgtest (or even worse, your package), but it seems to me that the change in tzdata was intended and your package needs to update to the new situation. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=tzdata https://ci.debian.net/data/autopkgtest/testing/amd64/p/python3.12/37119077/log.gz 947s == 947s FAIL: test_variable_tzname (test.test_email.test_utils.LocaltimeTests.test_variable_tzname) 947s -- 947s Traceback (most recent call last): 947s File "/usr/lib/python3.12/test/support/__init__.py", line 862, in inner 947s return func(*args, **kwds) 947s^^^ 947s File "/usr/lib/python3.12/test/test_email/test_utils.py", line 155, in test_variable_tzname 947s self.assertEqual(t1.tzname(), 'MSK') 947s AssertionError: 'Europe' != 'MSK' 947s - Europe 947s + MSK OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: python3.12: autopkgtest needs update for new version of tzdata
Processing control commands: > affects -1 src:tzdata Bug #1050529 [src:python3.12] python3.12: autopkgtest needs update for new version of tzdata Added indication that 1050529 affects src:tzdata -- 1050529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050529 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: upower: autopkgtest regression on i386: excessive precision?
Processing commands for cont...@bugs.debian.org: > # used wrong syntax during submission > reassign 1050436 src:upower Bug #1050436 [src:upower 1.90.2-4] upower: autopkgtest regression on i386: excessive precision? Warning: Unknown package '1.90.2-4' Bug reassigned from package 'src:upower 1.90.2-4' to 'src:upower'. Ignoring request to alter found versions of bug #1050436 to the same values previously set Ignoring request to alter fixed versions of bug #1050436 to the same values previously set > found 1050436 1.90.2-4 Bug #1050436 [src:upower] upower: autopkgtest regression on i386: excessive precision? Marked as found in versions upower/1.90.2-4. > thanks Stopping processing here. Please contact me if you need assistance. -- 1050436: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050436 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1050523: dh-make-golang: fails to determine dependencies
On 25.08.23 19:40, Mathias Gibbens wrote: Something has changed in sid's golang environment since August 4 which is causing dh-make-golang to fail to determine a package's dependencies and generate a correct d/control. For example, this worked fine on August 4 but now fails: It's probably also worth noting that dh-make-golang is now FTBFS (#1043070) due to golang.org/x/tools/go/vcs having been deprecated and removed from golang-golang-x-tools-dev as of version 0.11.0. OpenPGP_signature Description: OpenPGP digital signature
Bug#1050528: gnustep-base: autopkgtest needs update for new version of tzdata
Source: gnustep-base Version: 1.29.0-6 Severity: serious X-Debbugs-CC: tzd...@packages.debian.org Tags: sid trixie User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:tzdata Dear maintainer(s), With a recent upload of tzdata the autopkgtest of gnustep-base fails in testing when that autopkgtest is run with the binary packages of tzdata from unstable. It passes when run with only packages from testing. In tabular form: passfail tzdata from testing2023c-10 gnustep-base from testing1.29.0-6 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of tzdata to testing [1]. Of course, tzdata shouldn't just break your autopkgtest (or even worse, your package), but it seems to me that the change in tzdata was intended and your package needs to update to the new situation. If this is a real problem in your package (and not only in your autopkgtest), the right binary package(s) from tzdata should really add a versioned Breaks on the unfixed version of (one of your) package(s). Note: the Breaks is nice even if the issue is only in the autopkgtest as it helps the migration software to figure out the right versions to combine in the tests. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=tzdata https://ci.debian.net/data/autopkgtest/testing/amd64/g/gnustep-base/37117679/log.gz 106s Tests/base/NSCalendarDate/test00.m: 106s Failed test: (2023-08-25 06:10:33.417 +) test00.m:253 ... date check with 2002-03-31 01:30:00 106s Failed test: (2023-08-25 06:10:33.417 +) test00.m:268 ... date check with 2002-03-31 01:30:00 106s Failed test: (2023-08-25 06:10:33.417 +) test00.m:272 ... date check with 2002-03-31 00:30:00 106s Failed test: (2023-08-25 06:10:33.417 +) test00.m:430 ... date year calculation preserves timezone OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: gnustep-base: autopkgtest needs update for new version of tzdata
Processing control commands: > affects -1 src:tzdata Bug #1050528 [src:gnustep-base] gnustep-base: autopkgtest needs update for new version of tzdata Added indication that 1050528 affects src:tzdata -- 1050528: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050528 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1042124: marked as done (eegdev: FTBFS: ../../lib/stdio.h:64:3: error: #error "Please include config.h first.")
Your message dated Fri, 25 Aug 2023 18:50:11 + with message-id and subject line Bug#1042124: fixed in eegdev 0.2-7 has caused the Debian Bug report #1042124, regarding eegdev: FTBFS: ../../lib/stdio.h:64:3: error: #error "Please include config.h first." 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.) -- 1042124: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042124 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: eegdev Version: 0.2-6 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. > -I../../config -I/usr/include/libusb-1.0 -Wdate-time -I../../lib > -I/usr/include/libusb-1.0 -Wdate-time -fvisibility=hidden -g -O2 > -ffile-prefix-map=/<>=. > -specs=/usr/share/dpkg/no-pie-compile.specs -Wformat -Werror=format-security > -O3 -Wall -Wextra -c -o confline.lex.lo confline.lex.c > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../config > -I/usr/include/libusb-1.0 -Wdate-time -I../../lib -I/usr/include/libusb-1.0 > -Wdate-time -fvisibility=hidden -g -O2 -ffile-prefix-map=/<>=. > -specs=/usr/share/dpkg/no-pie-compile.specs -Wformat -Werror=format-security > -O3 -Wall -Wextra -c sensortypes.c -fPIC -DPIC -o .libs/sensortypes.o > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../config > -I/usr/include/libusb-1.0 -Wdate-time -I../../lib -I/usr/include/libusb-1.0 > -Wdate-time -fvisibility=hidden -g -O2 -ffile-prefix-map=/<>=. > -specs=/usr/share/dpkg/no-pie-compile.specs -Wformat -Werror=format-security > -O3 -Wall -Wextra -c typecast.c -fPIC -DPIC -o .libs/typecast.o > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../config > -I/usr/include/libusb-1.0 -Wdate-time -I../../lib -I/usr/include/libusb-1.0 > -Wdate-time -fvisibility=hidden -g -O2 -ffile-prefix-map=/<>=. > -specs=/usr/share/dpkg/no-pie-compile.specs -Wformat -Werror=format-security > -O3 -Wall -Wextra -c conffile.lex.c -fPIC -DPIC -o .libs/conffile.lex.o > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../config > -I/usr/include/libusb-1.0 -Wdate-time -I../../lib -I/usr/include/libusb-1.0 > -Wdate-time -fvisibility=hidden -g -O2 -ffile-prefix-map=/<>=. > -specs=/usr/share/dpkg/no-pie-compile.specs -Wformat -Werror=format-security > -O3 -Wall -Wextra -c core.c -fPIC -DPIC -o .libs/core.o > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../config > -I/usr/include/libusb-1.0 -Wdate-time -I../../lib -I/usr/include/libusb-1.0 > -Wdate-time -fvisibility=hidden -g -O2 -ffile-prefix-map=/<>=. > -specs=/usr/share/dpkg/no-pie-compile.specs -Wformat -Werror=format-security > -O3 -Wall -Wextra -c confline.lex.c -fPIC -DPIC -o .libs/confline.lex.o > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../config > -I/usr/include/libusb-1.0 -Wdate-time -I../../lib -I/usr/include/libusb-1.0 > -Wdate-time -fvisibility=hidden -g -O2 -ffile-prefix-map=/<>=. > -specs=/usr/share/dpkg/no-pie-compile.specs -Wformat -Werror=format-security > -O3 -Wall -Wextra -c configuration.c -fPIC -DPIC -o .libs/configuration.o > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../config > -I/usr/include/libusb-1.0 -Wdate-time -I../../lib -I/usr/include/libusb-1.0 > -Wdate-time -fvisibility=hidden -g -O2 -ffile-prefix-map=/<>=. > -specs=/usr/share/dpkg/no-pie-compile.specs -Wformat -Werror=format-security > -O3 -Wall -Wextra -c opendev.c -fPIC -DPIC -o .libs/opendev.o > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../config > -I/usr/include/libusb-1.0 -Wdate-time -I../../lib -I/usr/include/libusb-1.0 > -Wdate-time -fvisibility=hidden -g -O2 -ffile-prefix-map=/<>=. > -specs=/usr/share/dpkg/no-pie-compile.specs -Wformat -Werror=format-security > -O3 -Wall -Wextra -c conffile.tab.c -fPIC -DPIC -o .libs/conffile.tab.o > In file included from conffile.lex.c:242: > ../../lib/stdio.h:64:3: error: #error "Please include config.h first." >64 | #error "Please include config.h first." > | ^ > In file included from ../../lib/stdio.h:70: > ../../lib/stddef.h:107:3: error: #error "Please include config.h first." > 107 | #error "Please include config.h first." > | ^ > In file included from ../../lib/stdio.h:75: > ../../lib/sys/types.h:28:3: error: #error "Please include config.h first." >28 | #error "Please include config.h first." > | ^ > In file included from confline.lex.c:242: > ../../lib/stdio.h:64:3: error:
Bug#1050526: dask: autopkgtest regression on s390x
Source: dask Version: 2023.8.0+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of dask the autopkgtest of dask fails in testing on s390x when that autopkgtest is run with the binary packages of dask from unstable. It passes when run with only packages from testing. In tabular form: passfail dask from testing2023.8.0+dfsg-1 all others from testingfrom testing I copied some of the output at the bottom of this report. I note that s390x is our only big endian release architecture. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul PS: the tests on armhf and i386 architectures regressed too about 8 months ago on what seems to be an 32 bit arch test problem [1] https://qa.debian.org/excuses.php?package=dask https://ci.debian.net/data/autopkgtest/testing/s390x/d/dask/37104621/log.gz 700s === FAILURES === 700s test_with_spec_integer_method _ 700s 700s def test_with_spec_integer_method(): 700s from dask.dataframe.io.demo import ColumnSpec, DatasetSpec, with_spec 700s 700s spec = DatasetSpec( 700s npartitions=1, 700s nrecords=5, 700s column_specs=[ 700s ColumnSpec(prefix="pois", dtype=int, method="poisson"), 700s ColumnSpec(prefix="norm", dtype=int, method="normal"), 700s ColumnSpec(prefix="unif", dtype=int, method="uniform"), 700s ColumnSpec(prefix="binom", dtype=int, method="binomial", args=(100, 0.4)), 700s ColumnSpec(prefix="choice", dtype=int, method="choice", args=(10,)), 700s ColumnSpec(prefix="rand", dtype=int, random=True, low=0, high=10), 700s ColumnSpec(prefix="rand", dtype=int, random=True), 700s ], 700s ) 700s ddf = with_spec(spec, seed=42) 700s res = ddf.compute() 700s > assert res["pois1"].tolist() == [1002, 985, 947, 1003, 1017] 700s E assert [1021, 1006, 1024, 1030, 930] == [1002, 985, 947, 1003, 1017] 700s E At index 0 diff: 1021 != 1002 700s E Full diff: 700s E - [1002, 985, 947, 1003, 1017] 700s E + [1021, 1006, 1024, 1030, 930] 700s 700s /usr/lib/python3/dist-packages/dask/dataframe/io/tests/test_demo.py:338: AssertionError OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: Re: Bug#1050522: wdm: FTBFS: fatal error: pango/pango.h: No such file or directory
Processing control commands: > tag -1 + confirmed pending Bug #1050522 [src:wdm] wdm: FTBFS: fatal error: pango/pango.h: No such file or directory Added tag(s) pending and confirmed. -- 1050522: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050522 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1050522: wdm: FTBFS: fatal error: pango/pango.h: No such file or directory
Control: tag -1 + confirmed pending Hi Aurelien, Aurelien Jarno wrote: > wdm fails to build from source. From my build log on amd64: Thanks for the bug report! > | /usr/include/WINGs/WINGsP.h:8:10: fatal error: pango/pango.h: No such file > or directory > | 8 | #include I can reproduce in a clean chroot. But it does not happen when building in my Sid workstation. So it looks like a missing respectively now separate build dependency. Just tested: Adding a build-dependency on libpango1.0-dev suffices to get it building in a clean chroot again. Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Bug#1042124: Flex help needed for eegdev (Was: Re: eegdev: FTBFS: ../../lib/stdio.h:64:3: error: #error "Please include config.h first.")
On Fri, Aug 25, 2023 at 06:29:34PM +0200, Niels Thykier wrote: > Nilesh Patra: > > On Fri, Aug 25, 2023 at 05:17:47PM +0200, Niels Thykier wrote: > > > [...] > > > > I had figured out this already, but conffile.lex.c does not exist in the > > project, it is generated as a part of the lexer output. In particular: > > > > Ok, apologies it was not clear to me from your opening email, where you were > stuck. I incorrectly assumed it was an an earlier stage than you are, so my > input was not useful to you. > > I checked the source of `conffile.l` and it need already has to runes to > include config.h where I would have assumed you needed to > (https://salsa.debian.org/med-team/eegdev/-/blob/master/src/core/conffile.l#L24). > > A bit of searching found the following flex upstream bug: > > * https://github.com/westes/flex/issues/564 > > Which seems related. Hopefully, it can help you. So, it was a lexer issue after all :) That did help, and I could fix the package. Thanks a lot! Best, Nilesh signature.asc Description: PGP signature
Bug#1050525: elan: FTBFS: error: failed to select a version for the requirement `dirs = "^4.0.0"`
Source: elan
Version: 2.0.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Dear maintainer,
elan fails to build from source. From my build log on amd64:
|dh_auto_test -a -O--buildsystem=cargo
| debian cargo wrapper: options, profiles, parallel: ['parallel=12'] [] ['-j12']
| debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu,
x86_64-linux-gnu
| debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1',
'/usr/bin/cargo', '-Zavoid-dev-deps', 'build', '--verbose', '--verbose',
'-j12', '--target', 'x86_64-unknown-linux-gnu'],) {}
| error: failed to select a version for the requirement `dirs = "^4.0.0"`
| candidate versions found which didn't match: 5.0.1
| location searched: directory source `/<>/debian/cargo_registry`
(which is replacing registry `crates-io`)
| required by package `elan-utils v1.11.0 (/<>/src/elan-utils)`
| ... which satisfies path dependency `elan-utils` of package `elan v2.0.0
(/<>)`
| perhaps a crate was updated and forgotten to be re-vendored?
| dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101
| make: *** [debian/rules:19: binary-arch] Error 25
| dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit
status 2
A full build log on riscv64 is also available:
https://buildd.debian.org/status/fetch.php?pkg=elan&arch=riscv64&ver=2.0.0-1&stamp=1692960457&raw=0
Regards
Aurelien
Bug#1050524: solfege: binary-any FTBFS with recent jdupes
Source: solfege
Version: 3.23.4-11
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Dear maintainer,
solfege fails to build from source when building only binary-any and
not binary-all. From my build log on amd64:
| make[1]: Leaving directory '/<>'
|dh_install -a
|dh_installdocs -a
|dh_installchangelogs -a
|dh_python3 -a
| E: dh_python3 dh_python3:197: no package to act on (python3-foo or one with
${python3:Depends} in Depends)
|dh_perl -a
|debian/rules override_dh_link
| make[1]: Entering directory '/<>'
| dh_link
| jdupes -rl debian/solfege-doc/usr/share/doc
|
| could not stat dir debian/solfege-doc/usr/share/doc
| No duplicates found.
| make[1]: *** [debian/rules:30: override_dh_link] Error 1
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:10: binary-arch] Error 2
| dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit
status 2
A full build log on riscv64 is also available:
https://buildd.debian.org/status/fetch.php?pkg=solfege&arch=riscv64&ver=3.23.4-11&stamp=1692931581&raw=0
The return value of jdupes changed after bookworm to no longer return
success when the given paths do not exist, which causes this failure in
binary-any builds.
A possible untested patch is:
--- a/debian/rules
+++ b/debian/rules
@@ -25,6 +25,5 @@
iconv --from-code=iso-8859-1 --to-code=utf-8 --output=$$ifile
$$ifile; \
done
-override_dh_link:
- dh_link
+execute_after_dh_link-indep:
jdupes -rl debian/solfege-doc/usr/share/doc
Regards
Aurelien
Bug#1042124: Flex help needed for eegdev (Was: Re: eegdev: FTBFS: ../../lib/stdio.h:64:3: error: #error "Please include config.h first.")
On 2023-08-25, at 18:29:34 +0200, Niels Thykier wrote: > Nilesh Patra: > > On Fri, Aug 25, 2023 at 05:17:47PM +0200, Niels Thykier wrote: > > > [...] > > > > I had figured out this already, but conffile.lex.c does not exist in the > > project, it is generated as a part of the lexer output. In particular: > > > > Ok, apologies it was not clear to me from your opening email, where you were > stuck. I incorrectly assumed it was an an earlier stage than you are, so my > input was not useful to you. > > I checked the source of `conffile.l` and it need already has to runes to > include config.h where I would have assumed you needed to > (https://salsa.debian.org/med-team/eegdev/-/blob/master/src/core/conffile.l#L24). > > A bit of searching found the following flex upstream bug: > > * https://github.com/westes/flex/issues/564 > > Which seems related. Hopefully, it can help you. Another possibility would be just not to use gnulib. Debian is a GNU system, so it shouldn't be needed. If one removes the dh_autoreconf override and just lets dh_autoreconf do its thing, the package builds successfully. J. signature.asc Description: PGP signature
Bug#1050521: mdevctl: FTBFS: error: failed to select a version for the requirement `env_logger = "^0.9.0"`
Package: mdevctl
Version: 1.2.0-3+b1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Dear maintainer,
mdevctl fails to build from source. From my build log on amd64:
| make[1]: Entering directory '/<>'
| dh_auto_test override_dh_auto_test
| find . ! -newermt 'jan 01, 2000' -exec touch -d@1674131836 {} +
| /usr/share/cargo/bin/cargo build
| debian cargo wrapper: options, profiles, parallel: ['parallel=12'] [] ['-j12']
| debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu,
x86_64-linux-gnu
| debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1',
'/usr/bin/cargo', '-Zavoid-dev-deps', 'build', '--verbose', '--verbose',
'-j12', '--target', 'x86_64-unknown-linux-gnu'],) {}
| error: failed to select a version for the requirement `env_logger = "^0.9.0"`
| candidate versions found which didn't match: 0.10.0
| location searched: directory source `/<>/debian/cargo_registry`
(which is replacing registry `crates-io`)
| required by package `mdevctl v1.2.0 (/<>)`
| perhaps a crate was updated and forgotten to be re-vendored?
| rm -fr -- /tmp/dh-xdg-rundir-mtiZmKlf
| dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101
| make[1]: *** [debian/rules:33: override_dh_auto_test] Error 25
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:9: binary] Error 2
| dpkg-buildpackage: error: debian/rules binary subprocess returned exit status
2
A full build log on riscv64 is also available:
https://buildd.debian.org/status/fetch.php?pkg=mdevctl&arch=riscv64&ver=1.2.0-3&stamp=1692924764&raw=0
Regards
Aurelien
Bug#1050522: wdm: FTBFS: fatal error: pango/pango.h: No such file or directory
Source: wdm Version: 1.28-26 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Dear maintainer, wdm fails to build from source. From my build log on amd64: | gcc -Wl,-z,relro -Wl,-z,now -L./bin src/wdm/Greet.o src/wdm/access.o src/wdm/auth.o src/wdm/choose.o src/wdm/daemon.o src/wdm/dm.o src/wdm/dpylist.o src/wdm/file.o src/wdm/genauth.o src/wdm/loghelpers.o src/wdm/mitauth.o src/wdm/netaddr.o src/wdm/policy.o src/wdm/protodpy.o src/wdm/reset.o src/wdm/resource.o src/wdm/server.o src/wdm/session.o src/wdm/socket.o src/wdm/util.o src/wdm/verify.o src/wdm/xdmcp.o -lWINGs -lwraster -lWUtil -lWUtil -lfontconfig -lcrypt -lutil -lwdm -lSM -lICE -lXext -lX11 -lm -lXinerama -lpam -ldl -lselinux -lXmu -lXau -lXdmcp -o bin/wdm | gcc -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -DHAVE_CONFIG_H -I./include -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo -I/usr/include/pixman-1 -pthread src/wdmChooser/chooser.c -o src/wdmChooser/chooser.o | mkdir -p bin | gcc -Wl,-z,relro -Wl,-z,now -L./bin src/wdmChooser/chooser.o -lWINGs -lwraster -lWUtil -lWUtil -lfontconfig -lcrypt -lutil -lwdm -lSM -lICE -lXext -lX11 -lm -lXinerama -o bin/wdmChooser | gcc -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -DHAVE_CONFIG_H -I./include -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo -I/usr/include/pixman-1 -pthread src/wdmLogin/Login.c -o src/wdmLogin/Login.o | In file included from src/wdmLogin/Login.c:46: | /usr/include/WINGs/WINGsP.h:8:10: fatal error: pango/pango.h: No such file or directory | 8 | #include | | ^~~ | compilation terminated. | make[1]: *** [Makefile:197: src/wdmLogin/Login.o] Error 1 | make[1]: Leaving directory '/<>' | dh_auto_build: error: make -j1 returned exit code 2 | make: *** [debian/rules:33: binary-arch] Error 25 | dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2 A full build log on riscv64 is also available: https://buildd.debian.org/status/fetch.php?pkg=wdm&arch=riscv64&ver=1.28-26&stamp=1692927817&raw=0 Regards Aurelien
Bug#1050523: dh-make-golang: fails to determine dependencies
Source: dh-make-golang Version: 0.6.0-2 Severity: serious X-Debbugs-CC: debian...@lists.debian.org Something has changed in sid's golang environment since August 4 which is causing dh-make-golang to fail to determine a package's dependencies and generate a correct d/control. For example, this worked fine on August 4 but now fails: > $ dh-make-golang -type library github.com/uber/jaeger-client-go > 2023/08/25 17:06:47 Starting "dh-make-golang v0.6.0 linux/amd64" > 2023/08/25 17:06:47 Downloading "github.com/uber/jaeger-client-go/..." > 2023/08/25 17:06:48 Determining upstream version number > 2023/08/25 17:06:48 Found latest tag "v2.30.0" > 2023/08/25 17:06:48 INFO: master is ahead of "v2.30.0" by 3 commits > 2023/08/25 17:06:48 Package version is "2.30.0" > /tmp/dh-make-golang4249120626/src/github.com/uber/jaeger-client-go/constants.go:20:2: > cannot find package "github.com/opentracing/opentracing-go" in any of: > /usr/lib/go-1.21/src/github.com/opentracing/opentracing-go (from > $GOROOT) > /tmp/dh-make-golang4249120626/src/github.com/opentracing/opentracing-go > (from $GOPATH) > /tmp/dh-make-golang4249120626/src/github.com/uber/jaeger-client-go/span.go:23:2: > cannot find package "github.com/opentracing/opentracing-go/ext" in any of: > /usr/lib/go-1.21/src/github.com/opentracing/opentracing-go/ext (from > $GOROOT) > > /tmp/dh-make-golang4249120626/src/github.com/opentracing/opentracing-go/ext > (from $GOPATH) > /tmp/dh-make-golang4249120626/src/github.com/uber/jaeger-client-go/baggage_setter.go:18:2: > cannot find package "github.com/opentracing/opentracing-go/log" in any of: > /usr/lib/go-1.21/src/github.com/opentracing/opentracing-go/log (from > $GOROOT) > > /tmp/dh-make-golang4249120626/src/github.com/opentracing/opentracing-go/log > (from $GOPATH) > [snip] signature.asc Description: This is a digitally signed message part
Bug#1042124: Flex help needed for eegdev (Was: Re: eegdev: FTBFS: ../../lib/stdio.h:64:3: error: #error "Please include config.h first.")
On Fri, Aug 25, 2023 at 05:17:47PM +0200, Niels Thykier wrote: > Nilesh Patra: > > > > > > On 25 August 2023 1:47:26 pm IST, Nilesh Patra wrote: > > > On Wed, 26 Jul 2023 21:52:17 +0200 Lucas Nussbaum > > > wrote: > > > > Source: eegdev > > > > Version: 0.2-6 > > > > Severity: serious > > > > > In file included from conffile.lex.c:242: > > > > > ../../lib/stdio.h:64:3: error: #error "Please include config.h first." > > > > > 64 | #error "Please include config.h first." > > > > >| ^ > > > > > > The lexed file conffile.lex.c seems to include some stuff before > > > config.h is included which is causing it to choke. > > > > > > I'm not acquainted with lexers and not sure what causes this. I'd > > > appreciate any help. > > > > Adding mentors list as well. If someone can help with this, that'd be great. > I do not think the lexer has anything to do with this. > > A quick look at the log suggests that the package is "rolling" its own > "stdio.h" (note the "../../lib/stdio.h" in the error message). Indeed, the > full log has "mv stdio.h-t3 stdio.h" as well. > > I believe that this is stdio.h is generated by the embedded gnulib copy and > that is as far as I am willing to debug that rabbit hole. Based on the > error, I assume gnulib's generated stdio.h requires the project specific > "config.h" to be loaded first. > > As for solving it, I would have a look at the "conffile.lex.c" file, see > where it has its "#include" for stdio.h and then add an `include "config.h"` > before that to see if it works (via a patch). I had figured out this already, but conffile.lex.c does not exist in the project, it is generated as a part of the lexer output. In particular: $ ls conffile.lex.c ls: cannot access 'conffile.lex.c': No such file or directory $ flex conffile.l $ ls conffile.lex.c conffile.lex.c And this indeed has config.h include after a few C-specific includes. Since this is not a part of the source, there's nothing I can patch in this file. conffile.l has the config.h include present before everything else, and hence I'm not sure where this should be fixed. Did I misunderstand your solution somehow? If not, can you recommend something else? Best, Nilesh signature.asc Description: PGP signature
Bug#1050516: checkit-tiff: FTBFS on big-endian platforms
Source: checkit-tiff Severity: serious X-Debbugs-Cc: a...@andreas-romeyke.de, oltma...@zib.de The new checkit-tiff upstream version 1.4.3 does not build on big-endian platforms. Note: it was updated from 0.4.2, so the issue is not necessarily only in 1.4.3. You can get logs at https://buildd.debian.org/status/package.php?p=checkit-tiff The issue triggers multiple times on running the test suite and ends up: "(HE)TIFF Header error, not a MAGIC BYTE for TIFF: 0x2a00"
Bug#1042124: Flex help needed for eegdev (Was: Re: eegdev: FTBFS: ../../lib/stdio.h:64:3: error: #error "Please include config.h first.")
Nilesh Patra: On 25 August 2023 1:47:26 pm IST, Nilesh Patra wrote: On Wed, 26 Jul 2023 21:52:17 +0200 Lucas Nussbaum wrote: Source: eegdev Version: 0.2-6 Severity: serious In file included from conffile.lex.c:242: ../../lib/stdio.h:64:3: error: #error "Please include config.h first." 64 | #error "Please include config.h first." | ^ The lexed file conffile.lex.c seems to include some stuff before config.h is included which is causing it to choke. I'm not acquainted with lexers and not sure what causes this. I'd appreciate any help. Adding mentors list as well. If someone can help with this, that'd be great. Best, Nilesh Hi, I do not think the lexer has anything to do with this. A quick look at the log suggests that the package is "rolling" its own "stdio.h" (note the "../../lib/stdio.h" in the error message). Indeed, the full log has "mv stdio.h-t3 stdio.h" as well. I believe that this is stdio.h is generated by the embedded gnulib copy and that is as far as I am willing to debug that rabbit hole. Based on the error, I assume gnulib's generated stdio.h requires the project specific "config.h" to be loaded first. As for solving it, I would have a look at the "conffile.lex.c" file, see where it has its "#include" for stdio.h and then add an `include "config.h"` before that to see if it works (via a patch). Hope that helps. Best regards, Niels
Bug#1042124: Flex help needed for eegdev (Was: Re: eegdev: FTBFS: ../../lib/stdio.h:64:3: error: #error "Please include config.h first.")
Niels Thykier: [...] Hi, [...] I believe that this is stdio.h is generated by the embedded gnulib copy and that is as far as I am willing to debug that rabbit hole. Based on the error, I assume gnulib's generated stdio.h requires the project specific "config.h" to be loaded first. [...] Best regards, Niels Correction; the gnulib was probably not an "embedded copy". The file still seems to be generated via gnulib, so the rest of my argument would remain the same.
Bug#1049369: RM: notify-sharp-3.0 -- RoQA; leaf library package
Control: severity -1 normal Control: reassign -1 ftp.debian.org Please remove notify-sharp-3.0. It is not used by any other package. Also, it is a reverse dependency of gtk-sharp3, which should be moved to another upstream: #1050515. Dropping this will ease that transition.
Processed: Re: RM: notify-sharp-3.0 -- RoQA; leaf library package
Processing control commands: > severity -1 normal Bug #1049369 [src:notify-sharp-3.0] RM: notify-sharp-3.0 -- RoQA; leaf package Severity set to 'normal' from 'serious' > reassign -1 ftp.debian.org Bug #1049369 [src:notify-sharp-3.0] RM: notify-sharp-3.0 -- RoQA; leaf package Bug reassigned from package 'src:notify-sharp-3.0' to 'ftp.debian.org'. No longer marked as found in versions notify-sharp-3.0/3.0.3-3.1. Ignoring request to alter fixed versions of bug #1049369 to the same values previously set -- 1049369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049369 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1049952: csh: maintained by ubuntu-devel-disc...@lists.ubuntu.com
On Thu, 17 Aug 2023 11:34:56 +0200 Lucas Nussbaum wrote: > Source: csh > Version: 20110502-7 > Severity: serious Is this really a serious enough issue to warrant removal from Debian? > > Hi, > > this package is maintained by ubuntu-devel-disc...@lists.ubuntu.com, > which is not a suitable contact point for Debian packages maintenance > according to https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss > > This is most likely due to generating the source package on an Ubuntu > machine. I think there's some magic that replaces the Maintainer field > in the Ubuntu tooling. > > signature.asc Description: This is a digitally signed message part.
Processed: Re: [Pkg-cmake-team] Bug#1050506: Could NOT find EXPAT (missing: EXPAT_LIBRARY) (found version "2.5.0")
Processing control commands: > severity -1 normal Bug #1050506 [src:cmake] Could NOT find EXPAT (missing: EXPAT_LIBRARY) (found version "2.5.0") Severity set to 'normal' from 'serious' > tags -1 +moreinfo Bug #1050506 [src:cmake] Could NOT find EXPAT (missing: EXPAT_LIBRARY) (found version "2.5.0") Added tag(s) moreinfo. -- 1050506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050506 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1050506: [Pkg-cmake-team] Bug#1050506: Could NOT find EXPAT (missing: EXPAT_LIBRARY) (found version "2.5.0")
Control: severity -1 normal Control: tags -1 +moreinfo * Mathieu Malaterre [2023-08-25 15:33]: It is unclear why changing: cmake_minimum_required(VERSION 3.9.2) into cmake_minimum_required(VERSION 3.27) make the symptoms go away. Did you investigate this further? What is the smallest VERSION that fixes your problem? Also, why do you think this is a CMake issue and not a VTK issue? I see the error originating in VTK's FindEXPAT.cmake in VTK, not the one shipped in CMake. Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │ ⠈⠳⣄ ╰╯ signature.asc Description: PGP signature
Bug#905449: marked as done (libfsharp-core4.3-cil: It is impossible to configure libfsharp-core4.3-cil package)
Your message dated Fri, 25 Aug 2023 15:40:54 +0200 with message-id <922f5e65-8941-450b-b31d-52ebb9a5c...@debian.org> and subject line Re: libfsharp-core4.3-cil: It is impossible to configure libfsharp-core4.3-cil package has caused the Debian Bug report #905449, regarding libfsharp-core4.3-cil: It is impossible to configure libfsharp-core4.3-cil package 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.) -- 905449: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905449 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libfsharp-core4.3-cil Version: 4.0.0.4+dfsg2-2 Severity: important Dear Maintainer, When I try to install libfsharp-core4.3-cil package, I get the following error: Setting up libfsharp-core4.3-cil (4.0.0.4+dfsg2-2) ... * Installing 13 assemblies from libfsharp-core4.3-cil into Mono E: installing Assembly /usr/lib/cli/FSharp.Core-4.3/FSharp.Core.dll failed E: Installation of libfsharp-core4.3-cil with /usr/share/cli-common/runtimes.d/mono failed dpkg: error processing package libfsharp-core4.3-cil (--configure): subprocess installed post-installation script returned error exit status 29 If I then try to gac FSharp.Core.dll manually: # gacutil -i /usr/lib/cli/FSharp.Core-4.3/FSharp.Core.dll I get the folloing error: Couldn't find machine.config Failure adding assembly /usr/lib/cli/FSharp.Core-4.3/FSharp.Core.dll to the cache: Strong name cannot be verified for delay-signed assembly -- System Information: Debian Release: 9.5 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-6-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libfsharp-core4.3-cil depends on: ii cli-common 0.9+nmu1 ii libmono-corlib4.5-cil 4.6.2.7+dfsg-1 ii libmono-system-core4.0-cil 4.6.2.7+dfsg-1 ii libmono-system-numerics4.0-cil 4.6.2.7+dfsg-1 ii libmono-system4.0-cil 4.6.2.7+dfsg-1 ii mono-runtime4.6.2.7+dfsg-1 ii mono-runtime-common 4.6.2.7+dfsg-1 libfsharp-core4.3-cil recommends no packages. libfsharp-core4.3-cil suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- This was resolved. Most probably via a change in some other package.--- End Message ---
Processed: tagging 968312
Processing commands for cont...@bugs.debian.org: > tags 968312 + pending Bug #968312 [src:eztrace-contrib] eztrace-contrib: FTBFS with CUDA 11: cuda_runtime.cu(92): error: function "cudaMalloc(void **, size_t)" has already been defined Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 968312: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968312 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1042246: gdcm: FTBFS: make[1]: *** [debian/rules:107: override_dh_auto_configure] Error 2
Forwarded as #1050506
Bug#1042246: marked as done (gdcm: FTBFS: make[1]: *** [debian/rules:107: override_dh_auto_configure] Error 2)
Your message dated Fri, 25 Aug 2023 13:34:04 + with message-id and subject line Bug#1042246: fixed in gdcm 3.0.21-2 has caused the Debian Bug report #1042246, regarding gdcm: FTBFS: make[1]: *** [debian/rules:107: override_dh_auto_configure] Error 2 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.) -- 1042246: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042246 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gdcm Version: 3.0.21-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_configure -- -DGDCM_WRAP_JAVA:BOOL=ON -DVTKGDCM_WRAP_JAVA:BOOL=ON > -DGDCM_DEFAULT_JAVA_VERSION:STRING=1.8 -DCMAKE_SKIP_RPATH=ON > -DCMAKE_BUILD_TYPE:STRING=None -DGDCM_DOXYGEN_NO_FOOTER:BOOL=ON > -DGDCM_BUILD_APPLICATIONS:BOOL=ON -DGDCM_DOCUMENTATION:BOOL=ON > -DGDCM_VTK_DOCUMENTATION:BOOL=OFF > -DDOCUMENTATION_DOWNLOAD_VTK_TAGFILE:BOOL=OFF > -DGDCM_PDF_DOCUMENTATION:BOOL=ON -DGDCM_BUILD_SHARED_LIBS:BOOL=ON > -DGDCM_WRAP_PYTHON:BOOL=ON -DVTKGDCM_WRAP_PYTHON:BOOL=ON > -DVTKGDCM_WRAP_JAVA:BOOL=OFF -DGDCM_WRAP_CSHARP:BOOL=1 > -DGDCM_WRAP_PHP:BOOL=OFF -DGDCM_USE_PVRG:BOOL=ON > -DGDCM_USE_SYSTEM_PVRG:BOOL=ON -DGMCS_EXECUTABLE:FILEPATH=/usr/bin/mono-csc > -DGDCM_BUILD_TESTING:BOOL=OFF -DGDCM_USE_SYSTEM_EXPAT:BOOL=ON > -DGDCM_USE_SYSTEM_UUID:BOOL=ON -DGDCM_USE_SYSTEM_ZLIB:BOOL=ON > -DGDCM_USE_SYSTEM_OPENJPEG:BOOL=ON -DGDCM_USE_SYSTEM_OPENSSL:BOOL=ON > -DGDCM_USE_SYSTEM_CHARLS:BOOL=ON -DGDCM_USE_SYSTEM_POPPLER:BOOL=ON > -DGDCM_USE_SYSTEM_LIBXML2:BOOL=ON -DGDCM_USE_SYSTEM_JSON:BOOL=ON > -DGDCM_USE_PARAVIEW:BOOL=OFF -DGDCM_USE_ACTIVIZ:BOOL=OFF > -DGDCM_USE_SYSTEM_PAPYRUS3:BOOL=ON -DGDCM_USE_SYSTEM_SOCKETXX:BOOL=ON > -DPython_ADDITIONAL_VERSIONS:STRING=3.11 > -DGDCM_INSTALL_DOC_DIR:STRING=share/doc/gdcm-doc > -DTAGFILES:STRING="/usr/share/doc/vtk-doc/html/vtk9.1.tag=/usr/share/doc/vtk-doc/html/" > -DGDCM_INSTALL_PYTHONMODULE_DIR:STRING=lib/python/dist-packages > -DGDCM_INSTALL_JAVAMODULE_DIR:STRING=lib/x86_64-linux-gnu/jni > -DGDCM_NO_PYTHON_LIBS_LINKING:BOOL=ON -DGDCM_NO_VTKJAVA_LIBS_LINKING:BOOL=ON > -DGDCM_INSTALL_LIB_DIR:STRING=lib/x86_64-linux-gnu -DGDCM_USE_VTK:BOOL=ON > -DVTK_JAVA_JAR=/usr/share/java/vtk9.jar > cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr > -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc > -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON > -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF > -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON > -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run > -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON -GNinja -DCMAKE_VERBOSE_MAKEFILE=ON > -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DGDCM_WRAP_JAVA:BOOL=ON > -DVTKGDCM_WRAP_JAVA:BOOL=ON -DGDCM_DEFAULT_JAVA_VERSION:STRING=1.8 > -DCMAKE_SKIP_RPATH=ON -DCMAKE_BUILD_TYPE:STRING=None > -DGDCM_DOXYGEN_NO_FOOTER:BOOL=ON -DGDCM_BUILD_APPLICATIONS:BOOL=ON > -DGDCM_DOCUMENTATION:BOOL=ON -DGDCM_VTK_DOCUMENTATION:BOOL=OFF > -DDOCUMENTATION_DOWNLOAD_VTK_TAGFILE:BOOL=OFF > -DGDCM_PDF_DOCUMENTATION:BOOL=ON -DGDCM_BUILD_SHARED_LIBS:BOOL=ON > -DGDCM_WRAP_PYTHON:BOOL=ON -DVTKGDCM_WRAP_PYTHON:BOOL=ON > -DVTKGDCM_WRAP_JAVA:BOOL=OFF -DGDCM_WRAP_CSHARP:BOOL=1 > -DGDCM_WRAP_PHP:BOOL=OFF -DGDCM_USE_PVRG:BOOL=ON > -DGDCM_USE_SYSTEM_PVRG:BOOL=ON -DGMCS_EXECUTABLE:FILEPATH=/usr/bin/mono-csc > -DGDCM_BUILD_TESTING:BOOL=OFF -DGDCM_USE_SYSTEM_EXPAT:BOOL=ON > -DGDCM_USE_SYSTEM_UUID:BOOL=ON -DGDCM_USE_SYSTEM_ZLIB:BOOL=ON > -DGDCM_USE_SYSTEM_OPENJPEG:BOOL=ON -DGDCM_USE_SYSTEM_OPENSSL:BOOL=ON > -DGDCM_USE_SYSTEM_CHARLS:BOOL=ON -DGDCM_USE_SYSTEM_POPPLER:BOOL=ON > -DGDCM_USE_SYSTEM_LIBXML2:BOOL=ON -DGDCM_USE_SYSTEM_JSON:BOOL=ON > -DGDCM_USE_PARAVIEW:BOOL=OFF -DGDCM_USE_ACTIVIZ:BOOL=OFF > -DGDCM_USE_SYSTEM_PAPYRUS3:BOOL=ON -DGDCM_USE_SYSTEM_SOCKETXX:BOOL=ON > -DPython_ADDITIONAL_VERSIONS:STRING=3.11 > -DGDCM_INSTALL_DOC_DIR:STRING=share/doc/gdcm-doc > -DTAGFILES:STRING=/usr/share/doc/vtk-doc/html/vtk9.1.tag=/usr/share/doc/vtk-doc/html/ > -DGDCM_INSTALL_PYTHONMODULE_DIR:STRING=lib/python/dist-packages > -DGDCM_INSTALL_JAVAMODULE_DIR:STRING=lib/x86_64-linux-gnu/jni > -DGDCM_NO_PYTHON_LIBS_LINKING:BOOL=ON -DGDCM_NO_VTKJAVA_LIBS_LINKING:BOOL=ON > -DGDCM_INSTALL_LIB_DIR:STRING=lib/x86_64-linux-gnu -DGDCM_USE_VTK:BOOL=ON > -DVTK_JAVA_JAR=/usr/share/java/vtk9.jar .. > -- The CXX compiler identification is
Bug#1050506: Could NOT find EXPAT (missing: EXPAT_LIBRARY) (found version "2.5.0")
Source: cmake Version: 3.27.3-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Affects: src:gdcm Original bug report is #1042246 Here is a minimal reproduce: % cat ../CMakeLists.txt cmake_minimum_required(VERSION 3.9.2) #cmake_minimum_required(VERSION 3.27) project(p) find_package(EXPAT REQUIRED) find_package(VTK REQUIRED) The above gives: % rm CMakeCache.txt && cmake .. [...] CMake Error at /usr/share/cmake-3.27/Modules/FindPackageHandleStandardArgs.cmake:230 (message): Could NOT find EXPAT (missing: EXPAT_LIBRARY) (found version "2.5.0") Call Stack (most recent call first): /usr/share/cmake-3.27/Modules/FindPackageHandleStandardArgs.cmake:600 (_FPHSA_FAILURE_MESSAGE) /usr/lib/x86_64-linux-gnu/cmake/vtk-9.1/FindEXPAT.cmake:65 (FIND_PACKAGE_HANDLE_STANDARD_ARGS) /usr/lib/x86_64-linux-gnu/cmake/vtk-9.1/VTK-vtk-module-find-packages.cmake:1243 (find_package) /usr/lib/x86_64-linux-gnu/cmake/vtk-9.1/vtk-config.cmake:150 (include) CMakeLists.txt:6 (find_package) It is unclear why changing: cmake_minimum_required(VERSION 3.9.2) into cmake_minimum_required(VERSION 3.27) make the symptoms go away. Thanks for comments,
Bug#1042124: Flex help needed for eegdev (Was: Re: eegdev: FTBFS: ../../lib/stdio.h:64:3: error: #error "Please include config.h first.")
On 25 August 2023 1:47:26 pm IST, Nilesh Patra wrote: >On Wed, 26 Jul 2023 21:52:17 +0200 Lucas Nussbaum wrote: >> Source: eegdev >> Version: 0.2-6 >> Severity: serious >> > In file included from conffile.lex.c:242: >> > ../../lib/stdio.h:64:3: error: #error "Please include config.h first." >> >64 | #error "Please include config.h first." >> > | ^ > >The lexed file conffile.lex.c seems to include some stuff before >config.h is included which is causing it to choke. > >I'm not acquainted with lexers and not sure what causes this. I'd >appreciate any help. Adding mentors list as well. If someone can help with this, that'd be great. Best, Nilesh
Bug#1042246: marked as pending in gdcm
Control: tag -1 pending Hello, Bug #1042246 in gdcm 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/med-team/gdcm/-/commit/aa371fe473c4c892343eaafb3ce29f96006ad59e d/rules: Hack to work around FTBFS. Closes: #1042246 (this message was generated automatically) -- Greetings https://bugs.debian.org/1042246
Processed: Bug#1042246 marked as pending in gdcm
Processing control commands: > tag -1 pending Bug #1042246 [src:gdcm] gdcm: FTBFS: make[1]: *** [debian/rules:107: override_dh_auto_configure] Error 2 Added tag(s) pending. -- 1042246: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042246 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1039650: marked as done (r-cran-glmmtmb: autopkgtest failure with r-base (4.3.1-1))
Your message dated Fri, 25 Aug 2023 13:04:41 +
with message-id
and subject line Bug#1039650: fixed in r-cran-glmmtmb 1.1.7+dfsg-2
has caused the Debian Bug report #1039650,
regarding r-cran-glmmtmb: autopkgtest failure with r-base (4.3.1-1)
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.)
--
1039650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039650
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-glmmtmb
Version: 1.1.5+dfsg-4
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
50s autopkgtest [01:19:09]: test run-unit-test: [---
50s dpkg-architecture: warning: cannot determine CC system type, falling back
to default (native compilation)
50s BEGIN TEST AAAtest-all.R
50s
50s R version 4.3.1 (2023-06-16) -- "Beagle Scouts"
50s Copyright (C) 2023 The R Foundation for Statistical Computing
50s Platform: x86_64-pc-linux-gnu (64-bit)
50s
50s R is free software and comes with ABSOLUTELY NO WARRANTY.
50s You are welcome to redistribute it under certain conditions.
50s Type 'license()' or 'licence()' for distribution details.
50s
50s R is a collaborative project with many contributors.
50s Type 'contributors()' for more information and
50s 'citation()' on how to cite R or R packages in publications.
50s
50s Type 'demo()' for some demos, 'help()' for on-line help, or
50s 'help.start()' for an HTML browser interface to help.
50s Type 'q()' to quit R.
50s
50s > if (require("testthat")) {
50s + pkg <- "glmmTMB"
50s + require(pkg, character.only=TRUE)
50s + print(sessionInfo())
50s + test_check(pkg, reporter="summary")
50s + print(warnings()) # TODO? catch most of these by expect_warning(..)
50s + } else {
50s + warnings("Package 'testthat' not available, cannot run unit tests
for package",
50s + sQuote(pkg))
50s + }
50s Loading required package: testthat
51s Loading required package: glmmTMB
52s R version 4.3.1 (2023-06-16)
52s Platform: x86_64-pc-linux-gnu (64-bit)
52s Running under: Debian GNU/Linux trixie/sid
52s
52s Matrix products: default
52s BLAS: /usr/lib/x86_64-linux-gnu/blas/libblas.so.3.11.0
52s LAPACK: /usr/lib/x86_64-linux-gnu/lapack/liblapack.so.3.11.0
52s
52s locale:
52s [1] C
52s
52s time zone: Etc/UTC
52s tzcode source: system (glibc)
52s
52s attached base packages:
52s [1] stats graphics grDevices utils datasets methods base
52s
52s other attached packages:
52s [1] glmmTMB_1.1.5 testthat_3.1.6
52s
52s loaded via a namespace (and not attached):
52s [1] nlme_3.1-162cli_3.6.0 rlang_1.0.6
52s [4] TH.data_1.1-1 estimability_1.4.1 xtable_1.8-4
52s [7] minqa_1.2.5 zoo_1.8-11 TMB_1.9.2
52s [10] lme4_1.1-31 brio_1.1.3 grid_4.3.1
52s [13] MASS_7.3-60 mvtnorm_1.1-3 numDeriv_2016.8-1.1
52s [16] compiler_4.3.1 multcomp_1.4-22 codetools_0.2-19
52s [19] sandwich_3.0-2 emmeans_1.8.4-1 coda_0.19-4
52s [22] Rcpp_1.0.10 lattice_0.20-45 nloptr_2.0.3
52s [25] R6_2.5.1splines_4.3.1 magrittr_2.0.3
52s [28] Matrix_1.5-3boot_1.3-28.1 survival_3.5-3
53s Anova: ..
56s VarCorr: .
56s altopt:
56s alternative optimizers: S
58s basics: .SS.S12..3.S
59s trickier examples: SS...
59s bootMer:
59s bootMer: SS
65s checkRank: ..W..W..
65s control: SS
65s diagnose: .
67s disp: ...
68s downstream: S..
68s edgecases:
68s test edge cases: .
68s env:
70s basic examples: ...
70s families:
71s alternative binomial specifications: ..
73s non-integer count warnings: ...
73s fitting exotic families: S
73s trunc compois: S
73s compois: S
73s genpois: S
73s tweedie: S.
73s link function info available:
74s link info added to family: ..
74s formulas:
74s formula parsing:
74s mapopt:
79s methods:
S
79s simulate consistency with glm/lm: ...
82s Ranef etc.: ...S...
83s misc: .
83s offset: S
83s predict: .SSS
88s Predict two-column response case:
SS.S..SSS...S..S...S.S.W.W..
88s reml:
89s REML: ...
89s rr: W
89s saveload:
90s Saving and loading glmmTMB objects: .
90s spars
Bug#1050497: marked as done (incompatible with the current gnome-shell version)
Your message dated Fri, 25 Aug 2023 13:04:09 + with message-id and subject line Bug#1050497: fixed in gnome-shell-extension-dashtodock 87+really84-1 has caused the Debian Bug report #1050497, regarding incompatible with the current gnome-shell version 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.) -- 1050497: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050497 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gnome-shell-extension-dashtodock Version: 87-1 Severity: serious Dear maintainer, The last version you uploaded to sid (87) is incompatible with the gnome-shell version available in unstable (44) This render your package completely unusable. The last dashtodock version compatible with g-s 44 is v84 Regards, Sébastien --- End Message --- --- Begin Message --- Source: gnome-shell-extension-dashtodock Source-Version: 87+really84-1 Done: Jeremy Bícha We believe that the bug you reported is fixed in the latest version of gnome-shell-extension-dashtodock, 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 1050...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jeremy Bícha (supplier of updated gnome-shell-extension-dashtodock 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: Fri, 25 Aug 2023 08:37:59 -0400 Source: gnome-shell-extension-dashtodock Built-For-Profiles: noudeb Architecture: source Version: 87+really84-1 Distribution: unstable Urgency: high Maintainer: Debian GNOME Maintainers Changed-By: Jeremy Bícha Closes: 1050497 Changes: gnome-shell-extension-dashtodock (87+really84-1) unstable; urgency=high . * Revert to version 84, last version compatible with GNOME Shell 44 (Closes: #1050497) * debian/control: Update allowed gnome-shell versions per metadata.json Checksums-Sha1: 2e724b3422b4b2cc72b92122d09752a2819dffe0 2350 gnome-shell-extension-dashtodock_87+really84-1.dsc e7473c9b9c94296b376d8fa563d4ef3a192d116c 329337 gnome-shell-extension-dashtodock_87+really84.orig.tar.gz ac3e421814e47de46ac0ee3e0cc35d4f2db29070 4872 gnome-shell-extension-dashtodock_87+really84-1.debian.tar.xz f9f2bb904a3836556b6d3e9ddca7efb0ad6dbf1b 7393 gnome-shell-extension-dashtodock_87+really84-1_source.buildinfo Checksums-Sha256: e1cf7a957abda90f74ae91a382848a25c95d1eb6e04d97d1ecc1d4231381e04c 2350 gnome-shell-extension-dashtodock_87+really84-1.dsc 13a1550693e99871c1dd493561a8ef44be6456185b19d28b6df1b025ff5b4af7 329337 gnome-shell-extension-dashtodock_87+really84.orig.tar.gz aa9d59ebdcdeb74147bcfbbf66e049c5f743ae67e73e4c557626a5ce17b0f78a 4872 gnome-shell-extension-dashtodock_87+really84-1.debian.tar.xz 9ef1b8b483ede0061e4c68d25efb634dd92d8aaad9c0dd8c72e83acd0a938fba 7393 gnome-shell-extension-dashtodock_87+really84-1_source.buildinfo Files: 73b86fc9361e31e3387be76215215fbc 2350 gnome optional gnome-shell-extension-dashtodock_87+really84-1.dsc 372776b45ea2c6352be61fd0cca63779 329337 gnome optional gnome-shell-extension-dashtodock_87+really84.orig.tar.gz 7ca73f5ecb1b92afd897e839c9fdeed9 4872 gnome optional gnome-shell-extension-dashtodock_87+really84-1.debian.tar.xz 09f684de10e8f56db76eed7a3f261de6 7393 gnome optional gnome-shell-extension-dashtodock_87+really84-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmTooi4ACgkQ5mx3Wuv+ bH1xpBAAycG9QJqgGNHMoDxGmOpYHQUR9EsWW49U2LUfOK6DLPZpa7WsSAdoHC6/ Bf1f+sTVmSO3LLIMVcyESxTKS2LfxgtD+IQb+o45pdFzf3R66b2GXkSK0/djiejh vNq/cQU6D3xPHbaEusB1ShPSe/pA9SIUnwMNLVwpvZLrNebEaj+u47GucGRCFBO4 IOKfHSntCQl645wVaAhaFH3z0F9IrviGQ+m/ZxddonaqIPKG/VtRptGM9yZHYfY9 J334YuMxIICZCWHO4KfhrLf9JkfVRxA+XbLSG8XcH3dKCFOVOL34y6Q1sPwwyWc2 8Ab/lRzMSZbmxze4X+GBxIqzEhQ2lMA++E2T+9ew/oI8H0EW6FkPYfDwYgMxm9+i 0BTG6YUOZq2lEVV2bwZ9djKG3Tw3oQ4htm9HhSsNKA/yEc0BjbIKgy9xz+LesJAn aH8uiHfVSkZ2bPQPCYTdXn2o4bWBM97T0OXeNwKUEQIwxQ4n6GTVATV+jcgamaaT O1C99FBdoM+Qv3mf92GctxBE9kKn3VunvwYj3sDzIvUCVqzvsL8y1ZJ/y049OAA1 fALfqAQ96gUCyhipUgey78mLoTPE8cPE1K5Ue0rDOQQkp3+wenXzP432LA6yrveg 67EsWSg9W3i7FjgxsqgQkIM1N4Ehy3QTQMD/2wVWp1y7+YpN0Ko= =i+9P -END PGP SIGNATURE End Message ---
Bug#1049886: btllib: FTBFS on armhf due to tests timing out
Hallo Andreas, On Fri, Aug 25, 2023 at 11:28:16AM +0200, Andreas Tille wrote: > Am Wed, Aug 16, 2023 at 03:43:24PM +0200 schrieb Emanuele Rocca: > > btllib currently fails to build from source on armhf with the following > > tests-related error: > > Armhf (as well as all other 32bit archs) are not part of the supportet > architectures. since the latest upload > > btllib (1.4.10+dfsg-1) unstable; urgency=medium [...] > So I'm wondering why this bug came up at all and closing it hereby. Ah yes, the reason why it came up is that btllib-tools is still Architecture: any. The buildds are attempting to build the package, and it fails. See for example 1.4.10+dfsg-1 on i386: https://buildd.debian.org/status/fetch.php?pkg=btllib&arch=i386&ver=1.4.10%2Bdfsg-1&stamp=1685883214&raw=0 Emanuele
Bug#1049876: [Debian-med-packaging] Bug#1050491: RM: bbhash [armel armhf i386 mipsel powerpc Buildd exposure stats hurd-i386 hppa sh4] -- ROM; Does not build on 32bit architectures
Hi, On 2023-08-25 09:46, Graham Inggs wrote: > On Fri, 25 Aug 2023 at 09:03, Andreas Tille wrote: > > upstream does not support 32bit and the usage of this package on 32bit is > > questionable anyway so please remove all 32bit builds of this package. > > Andreas, what 32-bit builds? bbhash has never built on 32-bit architectures. > > Emanuele, since when is this RC? My apologies! For some reason I was convinced bbhash and btllib did build in the past. In both cases it seems to make sense to limit the Architecture field to the supported ones, given that as far as I understand both packages and are not portable? See: https://www.debian.org/doc/debian-policy/ch-controlfields.html#architecture
Bug#1049869: marked as done (FTBFS with GCC-13 on arm64 and armhf)
Your message dated Fri, 25 Aug 2023 12:00:11 + with message-id and subject line Bug#1049869: fixed in arm-compute-library 23.08+dfsg-1 has caused the Debian Bug report #1049869, regarding FTBFS with GCC-13 on arm64 and armhf 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.) -- 1049869: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049869 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:arm-compute-library Version: 20.08+dfsg-7 Severity: serious Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-13 With GCC-13, arm-compute-library fails to build from source on both arm64 and armhf with the following errors: ./arm_compute/core/utils/misc/Utility.h: In function ‘bool arm_compute::utility::check_aligned(void*, size_t)’: ./arm_compute/core/utils/misc/Utility.h:194:35: error: ‘uintptr_t’ in namespace ‘std’ does not name a type 194 | return (reinterpret_cast(ptr) % alignment) == 0; | ^ ./arm_compute/core/utils/misc/Utility.h:32:1: note: ‘std::uintptr_t’ is defined in header ‘’; did you forget to ‘#include ’? 31 | #include +++ |+#include 32 | In file included from ./arm_compute/core/TensorShape.h:29, from ./arm_compute/core/IAccessWindow.h:28, from ./arm_compute/core/AccessWindowTranspose.h:28, from src/core/AccessWindowTranspose.cpp:24: ./arm_compute/core/utils/misc/Utility.h: In function ‘bool arm_compute::utility::check_aligned(void*, size_t)’: ./arm_compute/core/utils/misc/Utility.h:194:35: error: ‘uintptr_t’ in namespace ‘std’ does not name a type 194 | return (reinterpret_cast(ptr) % alignment) == 0; | ^ ./arm_compute/core/utils/misc/Utility.h:32:1: note: ‘std::uintptr_t’ is defined in header ‘’; did you forget to ‘#include ’? 31 | #include +++ |+#include 32 | ./arm_compute/core/TensorShape.h: At global scope: ./arm_compute/core/TensorShape.h:39:39: error: ‘uint32_t’ was not declared in this scope 39 | class TensorShape : public Dimensions | ^~~~ ./arm_compute/core/TensorShape.h:30:1: note: ‘uint32_t’ is defined in header ‘’; did you forget to ‘#include ’? 29 | #include "arm_compute/core/utils/misc/Utility.h" +++ |+#include 30 | ./arm_compute/core/TensorShape.h:39:47: error: template argument 1 is invalid 39 | class TensorShape : public Dimensions | ^ [...] --- End Message --- --- Begin Message --- Source: arm-compute-library Source-Version: 23.08+dfsg-1 Done: Emanuele Rocca We believe that the bug you reported is fixed in the latest version of arm-compute-library, 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 1049...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emanuele Rocca (supplier of updated arm-compute-library 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: SHA256 Format: 1.8 Date: Thu, 24 Aug 2023 20:15:14 +0200 Binary: libarm-compute32 libarm-compute32-dbgsym libarm-compute-dev libarm-compute-doc Source: arm-compute-library Architecture: all amd64 source Version: 23.08+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Compute Library Team Changed-By: Emanuele Rocca Closes: 1049869 Description: libarm-compute32 - Arm Compute Library libarm-compute-dev - Arm Compute Library - development files libarm-compute-doc - Arm Compute Library - documentation Changes: arm-compute-library (23.08+dfsg-1) unstable; urgency=medium . * New upstream release (Closes: #1049869) * Rename binary package to libarm-compute32 for soname bump. * Build on amd64 as well. * Split assembler block in a32_merge_float_8x6.hpp to fix FTBFS on armhf. * Build with buildsystem=none. * Drop gles_compute from scons arguments. * Build with debug=1 to include debug symbols. * Drop libarm_compute_core, now an empty dummy library. * Set debhelper compatibility level to 13 to get dh_install variable expansion without dh-exec. Drop build-dependency on dh-exec
Bug#1039638: marked as done (r-bioc-mutationalpatterns: autopkgtest failure with r-base (4.3.1-1))
Your message dated Fri, 25 Aug 2023 13:17:17 +0200
with message-id
and subject line Closing
has caused the Debian Bug report #1039638,
regarding r-bioc-mutationalpatterns: autopkgtest failure with r-base (4.3.1-1)
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.)
--
1039638: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039638
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-bioc-mutationalpatterns
Version: 3.8.1+dfsg-1
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
147s [ FAIL 4 | WARN 4 | SKIP 0 | PASS 271 ]
147s
147s ══ Failed tests
147s ── Error ('test-fit_to_signatures_bootstrapped.R:12'): Output has correct
class ──
147s Error in `vectbl_assign(x[[j]], i, recycled_value[[j]])`: DLL requires
the use of native symbols
147s Backtrace:
147s ▆
147s 1. ├─MutationalPatterns::fit_to_signatures_bootstrapped(...) at
test-fit_to_signatures_bootstrapped.R:12:2
147s 2. │ └─MutationalPatterns::fit_to_signatures_strict(...)
147s 3. │ └─... %>% purrr::reduce(dplyr::full_join, by = "rowname")
147s 4. └─purrr::reduce(., dplyr::full_join, by = "rowname")
147s 5. └─purrr:::reduce_impl(.x, .f, ..., .init = .init, .dir = .dir)
147s 6. ├─dplyr (local) fn(out, elt, ...)
147s 7. └─dplyr:::full_join.data.frame(out, elt, ...)
147s 8. └─dplyr:::join_mutate(...)
147s 9. ├─base::`[<-`(`*tmp*`, new_rows, names(y_key), value =
``)
147s 10. └─tibble:::`[<-.tbl_df`(`*tmp*`, new_rows, names(y_key),
value = ``)
147s 11. └─tibble:::tbl_subassign(x, i, j, value, i_arg, j_arg,
substitute(value))
147s 12. └─tibble:::tbl_subassign_row(xj, i, value, i_arg,
value_arg)
147s 13. ├─base::withCallingHandlers(...)
147s 14. └─tibble:::vectbl_assign(x[[j]], i,
recycled_value[[j]])
147s ── Error ('test-fit_to_signatures_bootstrapped.R:31'): Output is equal to
expected ──
147s Error in `vectbl_assign(x[[j]], i, recycled_value[[j]])`: DLL requires
the use of native symbols
147s Backtrace:
147s ▆
147s 1. ├─MutationalPatterns::fit_to_signatures_bootstrapped(...) at
test-fit_to_signatures_bootstrapped.R:31:2
147s 2. │ └─MutationalPatterns::fit_to_signatures_strict(...)
147s 3. │ └─... %>% purrr::reduce(dplyr::full_join, by = "rowname")
147s 4. └─purrr::reduce(., dplyr::full_join, by = "rowname")
147s 5. └─purrr:::reduce_impl(.x, .f, ..., .init = .init, .dir = .dir)
147s 6. ├─dplyr (local) fn(out, elt, ...)
147s 7. └─dplyr:::full_join.data.frame(out, elt, ...)
147s 8. └─dplyr:::join_mutate(...)
147s 9. ├─base::`[<-`(`*tmp*`, new_rows, names(y_key), value =
``)
147s 10. └─tibble:::`[<-.tbl_df`(`*tmp*`, new_rows, names(y_key),
value = ``)
147s 11. └─tibble:::tbl_subassign(x, i, j, value, i_arg, j_arg,
substitute(value))
147s 12. └─tibble:::tbl_subassign_row(xj, i, value, i_arg,
value_arg)
147s 13. ├─base::withCallingHandlers(...)
147s 14. └─tibble:::vectbl_assign(x[[j]], i,
recycled_value[[j]])
147s ── Error ('test-fit_to_signatures_strict.R:11'): (code run outside of
`test_that()`) ──
147s Error in `vectbl_assign(x[[j]], i, recycled_value[[j]])`: DLL requires
the use of native symbols
147s Backtrace:
147s ▆
147s 1. ├─MutationalPatterns::fit_to_signatures_strict(...) at
test-fit_to_signatures_strict.R:11:0
147s 2. │ └─... %>% purrr::reduce(dplyr::full_join, by = "rowname")
147s 3. └─purrr::reduce(., dplyr::full_join, by = "rowname")
147s 4. └─purrr:::reduce_impl(.x, .f, ..., .init = .init, .dir = .dir)
147s 5. ├─dplyr (local) fn(out, elt, ...)
147s 6. └─dplyr:::full_join.data.frame(out, elt, ...)
147s 7. └─dplyr:::join_mutate(...)
147s 8. ├─base::`[<-`(`*tmp*`, new_rows, names(y_key), value =
``)
147s 9. └─tibble:::`[<-.tbl_df`(`*tmp*`, new_rows, names(y_key),
value = ``)
147s 10. └─tibble:::tbl_subassign(x, i, j, value, i_arg, j_arg,
substitute(value))
147s 11. └─tibble:::tbl_subassign_row(xj, i, value, i_arg,
value_arg)
147s 12. ├─base::withCallingHandlers(...)
147s 13. └─tibble:::vectbl_assign(x[[j]], i,
recycled_value[[j]])
147s ── Error ('test-plot_lesion_segregation.R:22'): (code run outside of
`test_that()`) ──
147s Error in `vectbl_assign(x[[j]], i, recycled_va
Bug#1049876: Bug#1050491: RM: bbhash [armel armhf i386 mipsel powerpc Buildd exposure stats hurd-i386 hppa sh4] -- ROM; Does not build on 32bit architectures
Am Fri, Aug 25, 2023 at 09:46:43AM + schrieb Graham Inggs: > > Andreas, what 32-bit builds? bbhash has never built on 32-bit architectures. Good question - I was not properly looking at the build matrix. Sorry for the noise > Emanuele, since when is this RC? I'm tempted to close this bug since its at best wishlist but there is no point at all to provide this package for 32bit. Kind regards Andreas. -- http://fam-tille.de
Bug#1050497: incompatible with the current gnome-shell version
Package: gnome-shell-extension-dashtodock Version: 87-1 Severity: serious Dear maintainer, The last version you uploaded to sid (87) is incompatible with the gnome-shell version available in unstable (44) This render your package completely unusable. The last dashtodock version compatible with g-s 44 is v84 Regards, Sébastien
Processed: severity of 1042754 is normal
Processing commands for cont...@bugs.debian.org: > severity 1042754 normal Bug #1042754 [tor] tor: don't autostart the service on installation Severity set to 'normal' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 1042754: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042754 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1050096: marked as done (virtualbox-dkms: Does not build on 6.4.0-3-amd64)
Your message dated Fri, 25 Aug 2023 09:53:20 +
with message-id
and subject line Bug#1050096: fixed in virtualbox 7.0.10-dfsg-3
has caused the Debian Bug report #1050096,
regarding virtualbox-dkms: Does not build on 6.4.0-3-amd64
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.)
--
1050096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050096
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: virtualbox-dkms
Version: 7.0.10-dfsg-2
Severity: grave
Justification: renders package unusable
Dear Maintainer,
DKMS make.log for virtualbox-7.0.10 for kernel 6.4.0-3-amd64 (x86_64)
2023-08-19T19:17:04 CEST
make: Entering directory '/usr/src/linux-headers-6.4.0-3-amd64'
CC [M] /var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/linux/SUPDrv-linux.o
CC [M] /var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/SUPDrv.o
CC [M] /var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/SUPDrvGip.o
CC [M] /var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/SUPDrvSem.o
CC [M] /var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/SUPDrvTracer.o
CC [M] /var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/SUPLibAll.o
CC [M]
/var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/common/string/strformatrt.o
CC [M] /var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/combined-agnostic1.o
CC [M] /var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/combined-agnostic2.o
CC [M] /var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/combined-os-specific.o
LD [M] /var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/vboxdrv.o
/var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/vboxdrv.o: warning: objtool:
SUPR0TracerFireProbe+0x7: indirect jump found in RETPOLINE build
/var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/vboxdrv.o: warning: objtool:
supdrvTracerProbeFireStub+0x0: 'naked' return found in RETHUNK build
/var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/vboxdrv.o: warning: objtool:
rtThreadCtxHooksLnxSchedOut+0x23: call to {dynamic}() with UACCESS enabled
/var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/vboxdrv.o: warning: objtool:
rtThreadCtxHooksLnxSchedIn+0x2d: call to {dynamic}() with UACCESS enabled
/var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/vboxdrv.o: warning: objtool:
VBoxHost_RTR0MemKernelCopyFrom+0x17: redundant CLD
/var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/vboxdrv.o: warning: objtool:
VBoxHost_RTR0MemKernelCopyTo+0x17: redundant CLD
/var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/vboxdrv.o: warning: objtool:
supdrvTracerCommonDeregisterImpl+0x3c: relocation to !ENDBR:
supdrvTracerProbeFireStub+0x0
/var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/vboxdrv.o: warning: objtool:
___ksymtab+SUPR0TracerFireProbe+0x0: data relocation to !ENDBR:
SUPR0TracerFireProbe+0x0
/var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/vboxdrv.o: warning: objtool:
g_aFunctions+0xea0: data relocation to !ENDBR: SUPR0TracerFireProbe+0x0
/var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/vboxdrv.o: warning: objtool:
g_pfnSupdrvProbeFireKernel+0x0: data relocation to !ENDBR:
supdrvTracerProbeFireStub+0x0
/var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/vboxdrv.o: warning: objtool:
SUPR0TracerFireProbe+0x7: missing int3 after indirect jump
/var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/vboxdrv.o: warning: objtool:
supdrvTracerProbeFireStub+0x0: missing int3 after ret
CC [M]
/var/lib/dkms/virtualbox/7.0.10/build/vboxnetflt/linux/VBoxNetFlt-linux.o
CC [M] /var/lib/dkms/virtualbox/7.0.10/build/vboxnetflt/VBoxNetFlt.o
CC [M] /var/lib/dkms/virtualbox/7.0.10/build/vboxnetflt/SUPR0IdcClient.o
CC [M]
/var/lib/dkms/virtualbox/7.0.10/build/vboxnetflt/SUPR0IdcClientComponent.o
CC [M]
/var/lib/dkms/virtualbox/7.0.10/build/vboxnetflt/linux/SUPR0IdcClient-linux.o
/var/lib/dkms/virtualbox/7.0.10/build/vboxnetflt/linux/VBoxNetFlt-linux.c: In
function ‘vboxNetFltLinuxForwardToIntNetInner’:
/var/lib/dkms/virtualbox/7.0.10/build/vboxnetflt/linux/VBoxNetFlt-linux.c:1570:40:
error: implicit declaration of function ‘skb_gso_segment’; did you mean
‘skb_gso_reset’? [-Werror=implicit-function-declaration]
1570 | struct sk_buff *pSegment = skb_gso_segment(pBuf, 0
/*supported features*/);
|^~~
|skb_gso_reset
/var/lib/dkms/virtualbox/7.0.10/build/vboxnetflt/linux/VBoxNetFlt-linux.c:1570:40:
warning: initialization of ‘struct sk_buff *’ from ‘int’ makes pointer from
integer without a cast [-Wint-conversion]
cc1: some warnings being treated as errors
make[2]: *** [/usr/src/linux-headers-6.4.0-3-common/scripts/Makefile.build:257:
/var/lib/dkms/virtualbox/7.0.10/build/vbo
Bug#1049876: [Debian-med-packaging] Bug#1050491: RM: bbhash [armel armhf i386 mipsel powerpc Buildd exposure stats hurd-i386 hppa sh4] -- ROM; Does not build on 32bit architectures
On Fri, 25 Aug 2023 at 09:03, Andreas Tille wrote: > upstream does not support 32bit and the usage of this package on 32bit is > questionable anyway so please remove all 32bit builds of this package. Andreas, what 32-bit builds? bbhash has never built on 32-bit architectures. Emanuele, since when is this RC?
Processed: tagging 1050366
Processing commands for cont...@bugs.debian.org: > tags 1050366 + ftbfs Bug #1050366 [src:opencolorio] opencolorio: FTBFS with newer yaml-cpp [PATCH] Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1050366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050366 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: RM: viewnior -- RoQA; unmaintained; depends on gtk2
Processing control commands: > retitle -1 O: viewnior -- simple, fast and elegant image viewer Bug #1049351 [src:viewnior] RM: viewnior -- RoQA; unmaintained; depends on gtk2 Changed Bug title to 'O: viewnior -- simple, fast and elegant image viewer' from 'RM: viewnior -- RoQA; unmaintained; depends on gtk2'. > reassign -1 wnpp Bug #1049351 [src:viewnior] O: viewnior -- simple, fast and elegant image viewer Bug reassigned from package 'src:viewnior' to 'wnpp'. No longer marked as found in versions viewnior/1.6-1. Ignoring request to alter fixed versions of bug #1049351 to the same values previously set -- 1049351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049351 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity
Processing commands for cont...@bugs.debian.org: > severity 1049351 normal Bug #1049351 [wnpp] O: viewnior -- simple, fast and elegant image viewer Severity set to 'normal' from 'serious' > End of message, stopping processing here. Please contact me if you need assistance. -- 1049351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049351 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1049351: RM: viewnior -- RoQA; unmaintained; depends on gtk2
Control: retitle -1 O: viewnior -- simple, fast and elegant image viewer Control: reassign -1 wnpp It still has quite a high popcon, so I am orphaning viewnior instead.
Bug#1040521: tpm2-tss: FTBFS (test failures)
On Thu, 24 Aug 2023 16:54:36 +0200 Paul Gevers wrote: Hi Paul, On Sun, 6 Aug 2023 05:59:48 +0800 "Ying-Chun Liu (PaulLiu)" wrote: > But there are 3 more test that needed to be fixed. > 1. test/unit/fapi-eventlog > 2. test/unit/tcti-spi-helper > 3. test/unit/fapi-ima-eventlog > > I'll find some time to fix the rest of the failure and do a single upload that fixes every s390x > test failure. If you think (or have reason to hope) that the issue is *only* in the tests itself (and the built binaries might actually be OK), than it's also an option to *temporarily* disable these tests on big endian systems. Paul Hello, in the meanwhile Ubuntu folks did some deep analysis and crafted an additional patch (as well as disabling some other tests) http://launchpadlibrarian.net/683169589/tpm2-tss_4.0.1-2ubuntu1_4.0.1-2ubuntu2.diff.gz G. OpenPGP_signature Description: OpenPGP digital signature
Bug#1049886: marked as done (btllib: FTBFS on armhf due to tests timing out)
Your message dated Fri, 25 Aug 2023 11:28:16 +0200 with message-id and subject line Re: Bug#1049886: btllib: FTBFS on armhf due to tests timing out has caused the Debian Bug report #1049886, regarding btllib: FTBFS on armhf due to tests timing out 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.) -- 1049886: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049886 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: btllib Version: 1.4.10+dfsg-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs Hi, btllib currently fails to build from source on armhf with the following tests-related error: Iteration 1 Test FASTA == Summary of Failures: 9/15 indexlr TIMEOUT30.18s killed by signal 15 SIGTERM 10/15 seq_reader_fasta_module TIMEOUT30.08s killed by signal 15 SIGTERM 11/15 seq_reader_fastq_module TIMEOUT30.14s killed by signal 15 SIGTERM 12/15 seq_reader_multiline_fasta_module TIMEOUT30.07s killed by signal 15 SIGTERM 13/15 seq_reader_multiline_fastq_module TIMEOUT30.12s killed by signal 15 SIGTERM 14/15 seq_reader_sam_module TIMEOUT30.08s killed by signal 15 SIGTERM 15/15 seq_writerTIMEOUT30.05s killed by signal 15 SIGTERM Ok: 8 Expected Fail: 0 Fail: 0 Unexpected Pass:0 Skipped:0 Timeout:7 dh_auto_test: error: cd obj-arm-linux-gnueabihf && LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test returned exit code 7 make[1]: *** [debian/rules:12: override_dh_auto_test] Error 25 make[1]: Leaving directory '/<>' make: *** [debian/rules:8: binary] Error 2 --- End Message --- --- Begin Message --- Hi Emanuele, Am Wed, Aug 16, 2023 at 03:43:24PM +0200 schrieb Emanuele Rocca: > btllib currently fails to build from source on armhf with the following > tests-related error: Armhf (as well as all other 32bit archs) are not part of the supportet architectures. since the latest upload btllib (1.4.10+dfsg-1) unstable; urgency=medium * Exclude 32bit architectures since upstream confirmed these are not supported. Closes: #1022772 ... -- Andreas Tille Thu, 02 Feb 2023 08:10:47 +0100 So I'm wondering why this bug came up at all and closing it hereby. Thank you for all your QA work anyway Andreas. -- http://fam-tille.de--- End Message ---
Processed: Re: Bug#1049876: bbhash: FTBFS on 32 bit architectures
Processing control commands: > block -1 by 1050491 Bug #1049876 [src:bbhash] bbhash: FTBFS on 32 bit architectures 1049876 was not blocked by any bugs. 1049876 was not blocking any bugs. Added blocking bug(s) of 1049876: 1050491 -- 1049876: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049876 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1049876: bbhash: FTBFS on 32 bit architectures
Control: block -1 by 1050491 Am Wed, Aug 16, 2023 at 02:44:55PM +0200 schrieb Emanuele Rocca: > bbhash does not build correctly on the following 32 bit architectures: > armel, armhf, i386, mipsel. I've asked for removal of these architectures in bug #1050491. Kind regards Andreas. -- http://fam-tille.de
Bug#1042340: marked as done (xxsds-dynamic: FTBFS: make: *** [debian/rules:9: binary] Error 2)
Your message dated Fri, 25 Aug 2023 08:40:43 + with message-id and subject line Bug#1042340: fixed in xxsds-dynamic 1.0~alpha.1+git20210426.548c6f7-2 has caused the Debian Bug report #1042340, regarding xxsds-dynamic: FTBFS: make: *** [debian/rules:9: binary] Error 2 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.) -- 1042340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042340 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xxsds-dynamic Version: 1.0~alpha.1+git20210426.548c6f7-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary >dh_update_autotools_config >dh_autoreconf >dh_auto_configure > cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr > -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc > -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON > -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF > -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON > -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run > -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" > -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu .. > CMake Deprecation Warning at CMakeLists.txt:1 (cmake_minimum_required): > Compatibility with CMake < 3.5 will be removed from a future version of > CMake. > > Update the VERSION argument value or use a ... suffix to tell > CMake that the project does not need compatibility with older versions. > > > -- The C compiler identification is GNU 13.1.0 > -- The CXX compiler identification is GNU 13.1.0 > -- Detecting C compiler ABI info > -- Detecting C compiler ABI info - done > -- Check for working C compiler: /usr/bin/cc - skipped > -- Detecting C compile features > -- Detecting C compile features - done > -- Detecting CXX compiler ABI info > -- Detecting CXX compiler ABI info - done > -- Check for working CXX compiler: /usr/bin/c++ - skipped > -- Detecting CXX compile features > -- Detecting CXX compile features - done > Building in None mode > -- Configuring done (0.4s) > CMake Error at CMakeLists.txt:49 (add_dependencies): > The dependency target "hopscotch_map" of target "debug" does not exist. > > > CMake Error at CMakeLists.txt:50 (add_dependencies): > The dependency target "hopscotch_map" of target "rle_lz77_v1" does not > exist. > > > CMake Error at CMakeLists.txt:51 (add_dependencies): > The dependency target "hopscotch_map" of target "rle_lz77_v2" does not > exist. > > > CMake Error at CMakeLists.txt:52 (add_dependencies): > The dependency target "hopscotch_map" of target "h0_lz77" does not exist. > > > CMake Error at CMakeLists.txt:53 (add_dependencies): > The dependency target "hopscotch_map" of target "rle_bwt" does not exist. > > > CMake Error at CMakeLists.txt:54 (add_dependencies): > The dependency target "hopscotch_map" of target "cw-bwt" does not exist. > > > CMake Error at CMakeLists.txt:55 (add_dependencies): > The dependency target "hopscotch_map" of target "benchmark" does not exist. > > > CMake Error at CMakeLists.txt:56 (add_dependencies): > The dependency target "hopscotch_map" of target "wm_string" does not exist. > > > -- Generating done (0.0s) > CMake Warning: > Manually-specified variables were not used by the project: > > CMAKE_EXPORT_NO_PACKAGE_REGISTRY > CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY > CMAKE_FIND_USE_PACKAGE_REGISTRY > CMAKE_INSTALL_LIBDIR > CMAKE_INSTALL_LOCALSTATEDIR > CMAKE_INSTALL_RUNSTATEDIR > CMAKE_INSTALL_SYSCONFDIR > FETCHCONTENT_FULLY_DISCONNECTED > > > CMake Generate step failed. Build files cannot be regenerated correctly. > cd obj-x86_64-linux-gnu && tail -v -n \+0 CMakeCache.txt > ==> CMakeCache.txt <== > # This is the CMakeCache file. > # For build in directory: /<>/obj-x86_64-linux-gnu > # It was generated by CMake: /usr/bin/cmake > # You can edit this file to change values found and used by cmake. > # If you do not want to change any of the values, simply exit the editor. > # If you do want to change a value, simply edit, save, and exit the editor. > # The syntax for the file is as follows: > # KEY:TYPE=VALUE > # KEY is the name of a variable in the cache. > # TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!. > # VALUE is the current value for the KEY. > > > # EXTERNAL cache
Bug#1037715: marked as done (libatomic-queue: ftbfs with GCC-13)
Your message dated Fri, 25 Aug 2023 08:37:16 +
with message-id
and subject line Bug#1037715: fixed in libatomic-queue 1.4-1
has caused the Debian Bug report #1037715,
regarding libatomic-queue: ftbfs with GCC-13
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.)
--
1037715: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037715
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libatomic-queue
Version: 0.0+git20220518.83774a2-1
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13
[This bug is targeted to the upcoming trixie release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.
The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/libatomic-queue_0.0+git20220518.83774a2-1_unstable_gccexp.log
The last lines of the build log are at the end of this report.
To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-13/porting_to.html
[...]
inlined from ‘void {anonymous}::run_throughput_benchmark(const char*,
atomic_queue::HugePages&, const std::vector&, unsigned int,
unsigned int, unsigned int) [with Queue = atomic_queue::AtomicQueue2]’ at
/<>/src/benchmarks.cc:292:60:
/usr/include/c++/13/bits/new_allocator.h:147:55: note: at offset 16 into object
of size 8 allocated by ‘operator new’
147 | return static_cast<_Tp*>(_GLIBCXX_OPERATOR_NEW(__n *
sizeof(_Tp)));
| ^
In function ‘std::_Require >,
std::is_move_constructible<_Tp>, std::is_move_assignable<_Tp> > std::swap(_Tp&,
_Tp&) [with _Tp = thread::id]’,
inlined from ‘void std::thread::swap(std::thread&)’ at
/usr/include/c++/13/bits/std_thread.h:193:16,
inlined from ‘std::thread& std::thread::operator=(std::thread&&)’ at
/usr/include/c++/13/bits/std_thread.h:187:11,
inlined from ‘{anonymous}::cycles_t
{anonymous}::benchmark_throughput(atomic_queue::HugePages&, const
std::vector&, unsigned int, unsigned int, bool, sum_t*) [with
Queue = atomic_queue::AtomicQueue]’ at /<>/src/benchmarks.cc:252:43,
inlined from ‘void {anonymous}::run_throughput_benchmark(const char*,
atomic_queue::HugePages&, const std::vector&, unsigned int,
unsigned int, unsigned int) [with Queue = atomic_queue::AtomicQueue]’ at
/<>/src/benchmarks.cc:292:60:
/usr/include/c++/13/bits/move.h:198:7: error: array subscript 2 is outside
array bounds of ‘long long int [1]’ [-Werror=array-bounds=]
198 | __a = _GLIBCXX_MOVE(__b);
| ^~~
In member function ‘_Tp* std::__new_allocator<_Tp>::allocate(size_type, const
void*) [with _Tp = long long int]’,
inlined from ‘static _Tp* std::allocator_traits
>::allocate(allocator_type&, size_type) [with _Tp = long long int]’ at
/usr/include/c++/13/bits/alloc_traits.h:482:28,
inlined from ‘std::_Vector_base<_Tp, _Alloc>::pointer
std::_Vector_base<_Tp, _Alloc>::_M_allocate(std::size_t) [with _Tp = long long
int; _Alloc = std::allocator]’ at
/usr/include/c++/13/bits/stl_vector.h:378:33,
inlined from ‘std::_Vector_base<_Tp, _Alloc>::pointer
std::_Vector_base<_Tp, _Alloc>::_M_allocate(std::size_t) [with _Tp =
std::thread; _Alloc = std::allocator]’ at
/usr/include/c++/13/bits/stl_vector.h:375:7,
inlined from ‘void std::_Vector_base<_Tp,
_Alloc>::_M_create_storage(std::size_t) [with _Tp = std::thread; _Alloc =
std::allocator]’ at /usr/include/c++/13/bits/stl_vector.h:395:44,
inlined from ‘std::_Vector_base<_Tp, _Alloc>::_Vector_base(std::size_t,
const allocator_type&) [with _Tp = std::thread; _Alloc =
std::allocator]’ at /usr/include/c++/13/bits/stl_vector.h:332:26,
inlined from ‘std::vector<_Tp, _Alloc>::vector(size_type, const
allocator_type&) [with _Tp = std::thread; _Alloc =
std::allocator]’ at /usr/include/c++/13/bits/stl_vector.h:554:47,
Bug#1042124: Flex help needed for eegdev (Was: Re: eegdev: FTBFS: ../../lib/stdio.h:64:3: error: #error "Please include config.h first.")
On Wed, 26 Jul 2023 21:52:17 +0200 Lucas Nussbaum wrote: > Source: eegdev > Version: 0.2-6 > Severity: serious > > In file included from conffile.lex.c:242: > > ../../lib/stdio.h:64:3: error: #error "Please include config.h first." > >64 | #error "Please include config.h first." > > | ^ The lexed file conffile.lex.c seems to include some stuff before config.h is included which is causing it to choke. I'm not acquainted with lexers and not sure what causes this. I'd appreciate any help. Best, Nilesh signature.asc Description: PGP signature
Processed: RM: logol -- ROM; unmaintained package; low popcon
Processing control commands: > retitle -1 RM: logol -- ROM; unmaintained package; low popcon Bug #1040566 [logol] logol: broken symlink /usr/share/logol/lib/biojava.jar -> ../../java/biojava.jar Changed Bug title to 'RM: logol -- ROM; unmaintained package; low popcon' from 'logol: broken symlink /usr/share/logol/lib/biojava.jar -> ../../java/biojava.jar'. > reassign -1 ftp.debian.org Bug #1040566 [logol] RM: logol -- ROM; unmaintained package; low popcon Bug reassigned from package 'logol' to 'ftp.debian.org'. No longer marked as found in versions logol/1.7.9+dfsg-6. Ignoring request to alter fixed versions of bug #1040566 to the same values previously set > severity -1 normal Bug #1040566 [ftp.debian.org] RM: logol -- ROM; unmaintained package; low popcon Severity set to 'normal' from 'serious' -- 1040566: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040566 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1040566: RM: logol -- ROM; unmaintained package; low popcon
Control: retitle -1 RM: logol -- ROM; unmaintained package; low popcon Control: reassign -1 ftp.debian.org Control: severity -1 normal Hi FTP team, On Wed, 19 Jul 2023 08:13:37 +0200 olivier sallou wrote: > Le mer. 19 juil. 2023, 06:58, Andreas Tille a écrit : > > > Hi Olivier, > > > > Am Mon, Jul 17, 2023 at 12:13:30PM +0200 schrieb olivier sallou: > > > logol is not maintained anymore for quite some time now > > > > > > effort to keep in line with swi-prolog updates (need to recompile on each > > > ABI break of swi-prolog) AND biojava requires frequent work for an old > > > software with low usage. > > > > > > I would let it be removed > > > > You introduced the package so you know its usage best. I think any > > removal should be announced on debian-med@l.d.o which I'm doing hereby. > > > > IMHO if the fix would be "simple" (in terms of needs only less than > > 10min) keeping it might be worth it. Otherwise its a good time in the > > beginning of the release process to remove packages that just drain > > developer resources and do not serve a mentionable amount of users. > > > > It would require analysis and many updates, so quite some efforts for > unmaintained software and targetting low number of users (sure of that), so > i am for removal. > > > Olivier As discussed on this bug report, Olivier (the uploader) feels that this is not worth keeping, and nobody objected so far. Please remove this from the archive. Best, Nilesh signature.asc Description: PGP signature
Processed: bug 1050096 is forwarded to https://www.virtualbox.org/ticket/21796
Processing commands for cont...@bugs.debian.org: > forwarded 1050096 https://www.virtualbox.org/ticket/21796 Bug #1050096 [virtualbox-dkms] virtualbox-dkms: Does not build on 6.4.0-3-amd64 Set Bug forwarded-to-address to 'https://www.virtualbox.org/ticket/21796'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1050096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050096 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Reopen
Processing control commands:
> reopen -1
Bug #1049438 {Done: Andreas Tille } [src:r-cran-rgdal]
r-cran-rgdal: autopkgtest needs update for new version of r-cran-sp
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions r-cran-sp/1:2.0-0+dfsg-2.
--
1049438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049438
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1049438: Reopen
Control: reopen -1 Closing this bug was wrong since this issue is not solved. -- http://fam-tille.de
