Bug#1016598: marked as done (binoculars: vtk[6,7] removal)
Your message dated Fri, 24 Feb 2023 07:34:02 + with message-id and subject line Bug#1016598: fixed in binoculars 0.0.12-1.2 has caused the Debian Bug report #1016598, regarding binoculars: vtk[6,7] removal 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.) -- 1016598: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016598 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: binoculars Version: 0.0.11-1 Severity: serious X-Debbugs-Cc: sramac...@debian.org Tags: sid bookworm Control: block 1016597 by -1 User: gl...@debian.org Usertags: vtk6_vtk7_removal Based on #1013156 and similar bugs: Dear maintainer, Debian archive has now three major versions of the VTK (The Visualization Toolkit) package: vtk6, vtk7 and vtk9. Old vesions (vtk6 and vtk7) are not supported by upstream and the package itself is not easy for the mainance. We aim to drop old and deprecated version vtk6 and vtk7 packages before the freeze of the Debian 12 Bookworm. Your package depends on vtk6 or vtk7. Thus we ask you to migrate it to the latest vtk9 package. Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: binoculars Source-Version: 0.0.12-1.2 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of binoculars, 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 1016...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated binoculars 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: Tue, 21 Feb 2023 15:13:26 +0200 Source: binoculars Architecture: source Version: 0.0.12-1.2 Distribution: unstable Urgency: medium Maintainer: Debian PaN Maintainers Changed-By: Adrian Bunk Closes: 1016598 Changes: binoculars (0.0.12-1.2) unstable; urgency=medium . * Non-maintainer upload. * Also switch the binary dependency from python3-vtk7 to python3-vtk9. (Closes: #1016598) Checksums-Sha1: 99025284fd921e4ce62d8d0ef18513a196e6ad05 2409 binoculars_0.0.12-1.2.dsc 0a2d07aa3595a011f07c40dc6b80f9f328c25710 5040 binoculars_0.0.12-1.2.debian.tar.xz Checksums-Sha256: 879388b883b8d8467febc2f434fe3d050d0a54452087afc46d3984aaf0e62096 2409 binoculars_0.0.12-1.2.dsc 78e91356fa1dced86e38f9470d8cdf540204efb84d4342d654c9f1b1555a 5040 binoculars_0.0.12-1.2.debian.tar.xz Files: 4c6afe4d97c03798ecd219feb4a07c5a 2409 science optional binoculars_0.0.12-1.2.dsc 5e254f903e4849c677ee0887d128e991 5040 science optional binoculars_0.0.12-1.2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmP0xaYACgkQiNJCh6LY mLGrQQ//d8sSBC65LSg9Ux7NH96QJO7DRJdZLjnXJqjHdKnbd97ykbSf7H/kEaYs hlZOJvDtLek8rf9QPuq91JHN7mpltf8xOLnGA4xy/I+HqdkYTLrepc1tAoicTsWk GosVzOkmmI3XI2B21qZ2jJSqVY/DdC0klEa8qIBOe2Lbb1lYSpFkMyUQwEJBxqYq 5+h5SzOvf9OhTcV1oL2Cflc37UbunzoNQtBhTIoS95OE7AaAPZMq+O5kxvJzDA98 jOLXSwCZBTNaGNgvETDZTu1FXOilPEXlh99LYHPp66gwBjhb+YsB9JOJ2kl2TqVq AZXiwqQV0slXdTWuhQQdDpKG8nguGSf+vtrqDvBMjAl3y2runn7pBi1WMhgdSxp4 SCnqhejGxb5Jk7g4iZvXUxRwNrK9wafb3gE+4zeTnqSa6jZq3DZOIph9fqfD8oaC zw4OcrkP6dLFVxom+FO6ufHTVL3tJ3DOwYjU7h+9eOZjW2NaAxUxqY2FiwCknD9f peYbPTUTQdBOyF68tsUeJHisHX9P56pZjGIyFPvKc2WitYC/x/rAbi9ZTVfIf93f sY/Xqw0wjEthjJ8yDP9MLsF8b/EuSppj79Tb0jQ+TAo3UrimSoI4UB768nvzbhzr S9Ato5NCcH98y94tkK70jLiTStHQ2TSgGZGMUH1hOZUjialujyw= =y575 -END PGP SIGNATURE End Message ---
Bug#1028185: marked as done (NSSound.h unusable as single #import)
Your message dated Fri, 24 Feb 2023 06:19:41 + with message-id and subject line Bug#1028185: fixed in gnustep-gui 0.30.0-2 has caused the Debian Bug report #1028185, regarding NSSound.h unusable as single #import 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.) -- 1028185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028185 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: agenda.app Version: 0.46-2 Severity: important Tags: sid bookworm ftbfs User: pkg-gnustep-maintain...@lists.alioth.debian.org Usertags: gnustep-gui0.30-transition gnustep-transition This package fails to build with gnustep-gui/0.30.0-1 from experimental: gcc SoundBackend.m -c \ -MMD -MP -Wdate-time -D_FORTIFY_SOURCE=2 -DGNUSTEP -DGNUSTEP_BASE_LIBRARY=1 -DGNU_GUI_LIBRARY=1 -DGNU_RUNTIME=1 -DGNUSTEP_BASE_LIBRARY=1 -fno-strict-aliasing -fexceptions -fobjc-exceptions -D_NATIVE_OBJC_EXCEPTIONS -pthread -fPIC -Wall -DGSWARN -DGSDIAGNOSE -Wno-import -g -O2 -g -O2 -ffile-prefix-map=/build/agenda.app-0.46=. -fstack-protector-strong -Wformat -Werror=format-security -fconstant-string-class=NSConstantString -I. -I/usr/local/include/GNUstep -I/usr/include/GNUstep \ -o obj/SimpleAgenda.obj/SoundBackend.m.o In file included from SoundBackend.m:1: /usr/include/GNUstep/AppKit/NSSound.h:58:1: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'interface' 58 | @interface NSSound : NSObject | ^~ make[5]: *** [/usr/share/GNUstep/Makefiles/rules.make:521: obj/SimpleAgenda.obj/SoundBackend.m.o] Error 1 That's certainly a gnustep-gui bug, trivial to fix. I'll reassign and fix accordingly. --- End Message --- --- Begin Message --- Source: gnustep-gui Source-Version: 0.30.0-2 Done: Yavor Doganov We believe that the bug you reported is fixed in the latest version of gnustep-gui, 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 1028...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yavor Doganov (supplier of updated gnustep-gui 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, 23 Feb 2023 19:50:33 +0200 Source: gnustep-gui Architecture: source Version: 0.30.0-2 Distribution: experimental Urgency: medium Maintainer: Debian GNUstep maintainers Changed-By: Yavor Doganov Closes: 1028185 Changes: gnustep-gui (0.30.0-2) experimental; urgency=medium . * debian/rules (v_base): Bump to 1.29. (override_dh_auto_configure): Delete manpages from -common's .install file if "nodoc" is set. Conditionally create -doc's .install/.links. (override_dh_auto_build-indep): Enclose documentation-related commands within an appropriate nodoc conditional to support "nodoc". (override_dh_auto_install-indep): Likewise. * debian/templates/control.m4 (Build-Depends-Indep): Annotate all with ; they are only needed for building documentation. (gnustep-gui-doc) : Set to . * debian/control: Regenerate. * debian/gnustep-gui-doc.links: Rename as... * debian/templates/gnustep-gui.doc.links.in: ...to support "nodoc". * debian/clean: Add gnustep-gui-doc.links. * debian/patches/NSSound-header.patch: New; fix compiler error when #import'ing NSSound.h (Closes: #1028185). * debian/changelog: Fix typo in previous entry. Checksums-Sha1: d08bd6e8e9240c4571a98f6cdbecc6ee2883796c 3070 gnustep-gui_0.30.0-2.dsc acb47861f8c1484e10bf34028d201c3ab826cf1d 20144 gnustep-gui_0.30.0-2.debian.tar.xz a3e3f1e42fb64f431fde1b14145a560210b40153 13944 gnustep-gui_0.30.0-2_source.buildinfo Checksums-Sha256: 964e072e129c371fffa1afa7093dc40f4c6a422358af18cee0e89862e354116d 3070 gnustep-gui_0.30.0-2.dsc c52777a95d82791ec7c4212e3e5ec93fba32d1e1e02f8ded6832b8eb8a0fdd8b 20144 gnustep-gui_0.30.0-2.debian.tar.xz 0145b22b475fa7c5c821ff0e205a22f8bb0a43fd11fc77c7e5e388b0a4af9526 13944 gnustep-gui_0.30.0-2_source.buildinfo Files: 2fde3b8b935da82c49da87d935304e45 3070 gnustep optional gnustep-gui_0.30.0-2.dsc 1d4c355543770da2a9b2e4d938b18973 20144 gnustep optional gnustep-gui_0.30.0-2.debian.tar.xz 347d47a21f8acda8ba956dd4370cc8e6 13944 gnustep optional
Bug#1004869: marked as done (python-xarray: autopkgtest regression on i386)
Your message dated Fri, 24 Feb 2023 04:36:24 +
with message-id
and subject line Bug#1004869: fixed in python-xarray 2023.01.0-1.1
has caused the Debian Bug report #1004869,
regarding python-xarray: autopkgtest regression on i386
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.)
--
1004869: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004869
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-xarray
Version: 0.21.0-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
python-xarray's autopkgtests are failing on the i386 architecture [1].
I've copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.debian.net/packages/p/python-xarray/unstable/i386/
=== FAILURES ===
___ test_interpolate_chunk_advanced[linear]
method = 'linear'
@requires_scipy
@requires_dask
@pytest.mark.parametrize("method", ["linear", "nearest"])
@pytest.mark.filterwarnings("ignore:Increasing number of chunks")
def test_interpolate_chunk_advanced(method):
"""Interpolate nd array with an nd indexer sharing coordinates."""
# Create original array
x = np.linspace(-1, 1, 5)
y = np.linspace(-1, 1, 7)
z = np.linspace(-1, 1, 11)
t = np.linspace(0, 1, 13)
q = np.linspace(0, 1, 17)
da = xr.DataArray(
data=np.sin(x[:, np.newaxis, np.newaxis, np.newaxis, np.newaxis])
* np.cos(y[:, np.newaxis, np.newaxis, np.newaxis])
* np.exp(z[:, np.newaxis, np.newaxis])
* t[:, np.newaxis]
+ q,
dims=("x", "y", "z", "t", "q"),
coords={"x": x, "y": y, "z": z, "t": t, "q": q, "label":
"dummy_attr"},
)
# Create indexer into `da` with shared coordinate
("full-twist" Möbius strip)
theta = np.linspace(0, 2 * np.pi, 5)
w = np.linspace(-0.25, 0.25, 7)
r = xr.DataArray(
data=1 + w[:, np.newaxis] * np.cos(theta),
coords=[("w", w), ("theta", theta)],
)
x = r * np.cos(theta)
y = r * np.sin(theta)
z = xr.DataArray(
data=w[:, np.newaxis] * np.sin(theta),
coords=[("w", w), ("theta", theta)],
)
kwargs = {"fill_value": None}
expected = da.interp(t=0.5, x=x, y=y, z=z, kwargs=kwargs, method=method)
da = da.chunk(2)
x = x.chunk(1)
z = z.chunk(3)
actual = da.interp(t=0.5, x=x, y=y, z=z, kwargs=kwargs, method=method)
> assert_identical(actual, expected)
E AssertionError: Left and right DataArray objects are not identical
E
E Differing values:
E L
E array([[[ 3.302241e-01, 3.927241e-01, ..., 1.267724e+00,
1.330224e+00],
E [ 1.239764e-17, 6.25e-02, ..., 9.375000e-01,
1.00e+00],
E ...,
E [-5.560517e-17, 6.25e-02, ..., 9.375000e-01,
1.00e+00],
E [ 3.302241e-01, 3.927241e-01, ..., 1.267724e+00,
1.330224e+00]],
E
E [[ 3.603946e-01, 4.228946e-01, ..., 1.297895e+00,
1.360395e+00],
E [ 1.346533e-17, 6.25e-02, ..., 9.375000e-01,
1.00e+00],
E ...,
E [-5.109700e-17, 6.25e-02, ..., 9.375000e-01,
1.00e+00],
E [ 3.603946e-01, 4.228946e-01, ..., 1.297895e+00,
1.360395e+00]],
E
E ...,
E
E [[ 4.810764e-01, 5.435764e-01, ..., 1.418576e+00,
1.481076e+00],
E [ 1.878775e-17, 6.25e-02, ..., 9.375000e-01,
1.00e+00],
E ...,
E [-3.662163e-17, 6.25e-02, ..., 9.375000e-01,
1.00e+00],
E [ 4.810764e-01, 5.435764e-01, ..., 1.418576e+00,
1.481076e+00]],
E
E [[ 5.112469e-01, 5.737469e-01, ..., 1.448747e+00,
1.511247e+00],
E [ 2.044535e-17, 6.25e-02, ..., 9.375000e-01,
1.00e+00],
E ...,
E [-3.371783e-17, 6.25e-02, ..., 9.375000e-01,
1.00e+00],
E [ 5.112469e-01, 5.737469e-01, ..., 1.448747e+00,
1.511247e+00]]])
E R
E array([[[ 3.302241e-01, 3.927241e-01, ..., 1.267724e+00,
1.330224e+00],
E [ 1.239764e-17, 6.25e-02, ..., 9.375000e-01,
1.00e+00],
E ...,
E
Bug#1020192: Remove cycle-quotes from Debian? (was: Re: Bug#1020192: cycle-quotes: FTBFS: make: *** [debian/rules:4: build] Error 25)
On Sunday, October 02 2022, David Bremner wrote: > Lucas Nussbaum writes: > >> Source: cycle-quotes >> Version: 0.1-4 >> Severity: serious >> Justification: FTBFS >> Tags: bookworm sid ftbfs >> User: lu...@debian.org >> Usertags: ftbfs-20220917 ftbfs-bookworm >> >> Hi, >> >> During a rebuild of all packages in sid, your package failed to build >> on amd64. >> > > this seems unrelated to native compilation. It probably needs an > upstream fix for emacs 28. Unfortunately upstream seems dead / static. Agreed. I'm thinking about filing an RM bug against cycle-quotes; its last release happened 4 years ago (although there are some non-useful new commits on https://github.com/emacsmirror/cycle-quotes), it fails to build with Emacs 28, has been blocked for 790 days, and doesn't have any reverse-dependencies. Thoughts? -- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible https://sergiodj.net/ signature.asc Description: PGP signature
Bug#961147: libcolor-calc-perl: broken by new libgraphics-colornames-perl
On 24/02/23 1:53 pm, gregor herrmann wrote: On Wed, 25 May 2022 11:34:20 +0200, gregor herrmann wrote: On Mon, 21 Feb 2022 21:18:10 +, Damyan Ivanov wrote: -=| intrigeri, 22.05.2020 08:47:25 +0200 |=- Niko Tyni (2020-05-21): libcolor-calc-perl has just one reverse dependency AFAICS: libcgi-application-plugin-authentication-perl. I took a quick look. Me too, a longer one :) … Then I read your comments about removal :) The last rdep is gone, so I guess we can just RM libcolor-calc-perl? Or we can salvage it, as mtj has added another patch, which makes the tests pass. Not sure if it's woth it; if yes we probably should 1) merge the two patches and 2) upload quickly. i'm happy to merge the patches today
Bug#1031842: xdg-desktop-portal-gnome: 44 appears incompatible with GNOME Shell 43
Source: xdg-desktop-portal-gnome Version: 44~beta-1 Severity: serious Tags: trixie It appears that xdg-desktop-portal-gnome 44 is incompatible with mutter/gnome-shell 43. https://launchpad.net/ubuntu/+source/xdg-desktop-portal-gnome/44~beta-1ubuntu1 GNOME Shell 43 uses libmutter-11-0 ; GNOME Shell 44 uses libmutter-12-0 Therefore, would it be correct to set an unversioned Breaks: libmutter-11-0 Thank you, Jeremy Bícha
Bug#961147: libcolor-calc-perl: broken by new libgraphics-colornames-perl
On Wed, 25 May 2022 11:34:20 +0200, gregor herrmann wrote: > On Mon, 21 Feb 2022 21:18:10 +, Damyan Ivanov wrote: > > -=| intrigeri, 22.05.2020 08:47:25 +0200 |=- > > > Niko Tyni (2020-05-21): > > > > libcolor-calc-perl has just one reverse dependency AFAICS: > > > > libcgi-application-plugin-authentication-perl. > > > I took a quick look. > > Me too, a longer one :) > … > > Then I read your comments about removal :) > The last rdep is gone, so I guess we can just RM libcolor-calc-perl? Or we can salvage it, as mtj has added another patch, which makes the tests pass. Not sure if it's woth it; if yes we probably should 1) merge the two patches and 2) upload quickly. Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#962065: rdist: Non-free license
The 7.0 alpha version has been relicensed but this license still occurs in at least one file (missing/strcasecmp.c).
Processed: reassign 1031773 to mariadb-10.3
Processing commands for cont...@bugs.debian.org: > reassign 1031773 mariadb-10.3 1:10.3.38.0+deb10u1 Bug #1031773 [mariadb-10.3.38.0+deb10u1] mariadb-10.3.38.0+deb10u1: kmail fails after upgrading mariadb to 10.3.38.0+deb10u1 Warning: Unknown package 'mariadb-10.3.38.0+deb10u1' Bug reassigned from package 'mariadb-10.3.38.0+deb10u1' to 'mariadb-10.3'. No longer marked as found in versions 10.3.38.0+deb10u1. Ignoring request to alter fixed versions of bug #1031773 to the same values previously set Bug #1031773 [mariadb-10.3] mariadb-10.3.38.0+deb10u1: kmail fails after upgrading mariadb to 10.3.38.0+deb10u1 There is no source info for the package 'mariadb-10.3' at version '1:10.3.38.0+deb10u1' with architecture '' Unable to make a source version for version '1:10.3.38.0+deb10u1' Marked as found in versions 1:10.3.38.0+deb10u1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1031773: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031773 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998889: libcommoncpp2: Remove in bookworm?
Control: severity -1 normal Control: retitle -1 RM: libcommoncpp2 -- RoQA; orphaned; RC-buggy; better alternative available Control: reassign -1 ftp.debian.org Yes, the package should be gone from unstable as well.
Processed: Re: Bug#998889: libcommoncpp2: Remove in bookworm?
Processing control commands: > severity -1 normal Bug #998889 [src:libcommoncpp2] libcommoncpp2: Remove in bookworm? Severity set to 'normal' from 'serious' > retitle -1 RM: libcommoncpp2 -- RoQA; orphaned; RC-buggy; better alternative > available Bug #998889 [src:libcommoncpp2] libcommoncpp2: Remove in bookworm? Changed Bug title to 'RM: libcommoncpp2 -- RoQA; orphaned; RC-buggy; better alternative available' from 'libcommoncpp2: Remove in bookworm?'. > reassign -1 ftp.debian.org Bug #998889 [src:libcommoncpp2] RM: libcommoncpp2 -- RoQA; orphaned; RC-buggy; better alternative available Bug reassigned from package 'src:libcommoncpp2' to 'ftp.debian.org'. No longer marked as found in versions libcommoncpp2/1.8.1-10. Ignoring request to alter fixed versions of bug #998889 to the same values previously set -- 998889: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998889 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1029250: marked as done (meson: FTBFS: test_verbose: '1/1 subtest 1' not found in test output)
Your message dated Thu, 23 Feb 2023 23:41:20 + with message-id and subject line Bug#1029250: fixed in meson 1.0.1-1 has caused the Debian Bug report #1029250, regarding meson: FTBFS: test_verbose: '1/1 subtest 1' not found in test output 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.) -- 1029250: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029250 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: meson Version: 1.0.0-1.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230120 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ld: bobuser.p/bobuser.c.o: in function `main': > ./b 52a78b9866/../test cases/failing build/2 hidden symbol/bobuser.c:4: > undefined reference to `hidden_function' > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2023/01/20/meson_1.0.0-1.1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230120;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230120=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: meson Source-Version: 1.0.1-1 Done: Jussi Pakkanen We believe that the bug you reported is fixed in the latest version of meson, 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 1029...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jussi Pakkanen (supplier of updated meson 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, 24 Feb 2023 00:09:22 +0200 Source: meson Architecture: source Version: 1.0.1-1 Distribution: unstable Urgency: medium Maintainer: Jussi Pakkanen Changed-By: Jussi Pakkanen Closes: 1029250 Changes: meson (1.0.1-1) unstable; urgency=medium . * New upstream release. Closes: #1029250. Checksums-Sha1: 00f57880beb073812ebac39c6110427911a8d13e 3471 meson_1.0.1-1.dsc a2d102eb6a37307c9b67283e9764ed57cf286223 2104183 meson_1.0.1.orig.tar.gz ed32b389498c790c619d60caf502cf33ddc22525 16268 meson_1.0.1-1.debian.tar.xz 1da61bb5b43bfc063d47eda047ef0212ea99b9b0 35245 meson_1.0.1-1_source.buildinfo Checksums-Sha256: 0d15018b0e7a067109e8eeddf9f7e1fa363302655212a646db402cfcbd8bffdc 3471 meson_1.0.1-1.dsc d926b730de6f518728cc7c57bc5e701667bae0c3522f9e369427b2cc7839d3c1 2104183 meson_1.0.1.orig.tar.gz 7950e52a69d174014c8e2606933ee919d3ccd408f5f7269cbf4c838af23319e5 16268 meson_1.0.1-1.debian.tar.xz 14e6725a6faf01f3cb265016d0bc42578d8ff98282a97299684a2b63c2256fd6 35245 meson_1.0.1-1_source.buildinfo Files: b2bf53f452e7f355e46753ba96fe8930 3471 devel optional meson_1.0.1-1.dsc 843ba549bb2a199d9e04092116a7e749 2104183 devel optional meson_1.0.1.orig.tar.gz 9a2b3fb85fe77421ab1990dc4f8e514b 16268 devel optional meson_1.0.1-1.debian.tar.xz 5c357a76c50d0668958b28af0246679f 35245 devel optional meson_1.0.1-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEGeLW2bRtjapiiPh3wk5jG6ux/nAFAmP35HwTHGpwYWtrYW5l QGdtYWlsLmNvbQAKCRDCTmMbq7H+cBRBD/9jHlpLyV/lYut41msQV/lUeQSIi7Wy +O1cNmcINR8bWXUxpq5rZrqzsMQaPcpKfCPusdMEMvyt9Ag0eBfBibYg7rfpR9l8 70QvHKquLCTNDKz6FcP+CYy0LiiI2qnkbAR/+b4zvgOHCABToZn6+tObCSaPHGeI fgYxRojdh6ioiPGP8PazLgiR08y55b2U+wDQ3GTOgrDODeD7HPJPFXgznJCcFYLq kpRyB6SkDWt6/zE7rpAzIrcFovr0oJNtO5B3I2ZMB5MYXpdx1RopJxRnm/KH3gpu Rg5CbCl3B82xlrwOgwocbTbq6OhRq4amftlzsFIaAWLO5u/szpP4vGCoHL2yab9s PqPoDBrqhmlHt0ckCqndQsRCtr7ecXfVormcu56kl8pdwibsk0H/0h82So85iQ3g HB/TPrBHNIetENOCyYT7cKXnnGZL0f15/QSjLRFVwEB5rOGuaqUaiqMHpDLxBLDc
Processed: Re: Remove scalc for bookworm?
Processing control commands: > retitle -1 RM: scalc -- RoQA; orphaned; no reverse deps Bug #1026431 [src:scalc] Remove scalc for bookworm? Changed Bug title to 'RM: scalc -- RoQA; orphaned; no reverse deps' from 'Remove scalc for bookworm?'. > severity -1 normal Bug #1026431 [src:scalc] RM: scalc -- RoQA; orphaned; no reverse deps Severity set to 'normal' from 'serious' > reassign -1 ftp.debian.org Bug #1026431 [src:scalc] RM: scalc -- RoQA; orphaned; no reverse deps Bug reassigned from package 'src:scalc' to 'ftp.debian.org'. No longer marked as found in versions scalc/0.2.4-6. Ignoring request to alter fixed versions of bug #1026431 to the same values previously set -- 1026431: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026431 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026431: Remove scalc for bookworm?
Control: retitle -1 RM: scalc -- RoQA; orphaned; no reverse deps Control: severity -1 normal Control: reassign -1 ftp.debian.org Please remove scalc from the archive. There is no real use of it and popcon is very low.
Bug#1029439: feynmf: FTBFS in bookworm (I can't open file `fmfsamp4')
On 2/23/23 14:28, James Addison wrote: On Thu, 23 Feb 2023 at 12:53, James Addison wrote: Hi, pass: texlive-base (2022.20220605-1) unstable; urgency=low fail: texlive-base (2022.20220923-2) unstable; urgency=medium It should be possible to look at the differences between those (and maybe the related packages such as texlive-latex-base) to find further clues. I'm going to start on that fairly soon. Ok, it turns out that the problem was a compatibility-break between v2 and v3 of the base doc.sty file. Fortunately the texlive-latex-base package ships the previous (v2, feynmf-compatible) version of that file along with v3. This seems to be just a temporary solution, as the TL upstream people, will stop providing the old doc.sty at any time in the future. You may lower the severity, but not close the issue. Hilmar -- Testmail
Bug#1031744: httpdirfs: usage of ubsan might introduce vulnerabilities
On Thu, Feb 23, 2023 at 01:49:49AM +, Fufu Fang wrote: > Hi Adrian, > I have pushed a commit to Github which removes the usage of UBSAN. I am > happy to go with this method. > > Do let me know if you prefer ASAN to be added alongside UBSAN, rather > than simply removing UBSAN. Enabling ASAN makes it even worse, so this was correct. > Best wishes, > Fufu Thanks Adrian
Bug#1026739: marked as done (pytest-bdd: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.11 3.10" --system=custom "--test-args={interpreter} -m pytest -k 'not test_ge
Your message dated Thu, 23 Feb 2023 23:23:39 +0100
with message-id
and subject line python-glob2_0.5-6_source.changes ACCEPTED into unstable
has caused the Debian Bug report #1026739,
regarding pytest-bdd: FTBFS: dh_auto_test: error: pybuild --test --test-pytest
-i python{version} -p "3.11 3.10" --system=custom "--test-args={interpreter} -m
pytest -k 'not test_generate_with_quotes and not test_unicode_characters'"
returned exit code 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.)
--
1026739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026739
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pytest-bdd
Version: 5.0.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm
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_install
> I: pybuild base:240: /usr/bin/python3.11 setup.py install --root
> /<>/debian/python3-pytest-bdd
> running install
> /usr/lib/python3/dist-packages/setuptools/command/install.py:34:
> SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and
> pip and other standards-based tools.
> warnings.warn(
> running build
> running build_py
> running egg_info
> writing pytest_bdd.egg-info/PKG-INFO
> writing dependency_links to pytest_bdd.egg-info/dependency_links.txt
> writing entry points to pytest_bdd.egg-info/entry_points.txt
> writing requirements to pytest_bdd.egg-info/requires.txt
> writing top-level names to pytest_bdd.egg-info/top_level.txt
> reading manifest file 'pytest_bdd.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> adding license file 'LICENSE.txt'
> adding license file 'AUTHORS.rst'
> writing manifest file 'pytest_bdd.egg-info/SOURCES.txt'
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:202:
> SetuptoolsDeprecationWarning: Installing 'pytest_bdd.templates' as data
> is deprecated, please list it in `packages`.
> !!
>
>
>
> # Package would be ignored #
>
> Python recognizes 'pytest_bdd.templates' as an importable package,
> but it is not listed in the `packages` configuration of setuptools.
>
> 'pytest_bdd.templates' has been automatically added to the distribution
> only
> because it may contain data files, but this behavior is likely to change
> in future versions of setuptools (and therefore is considered deprecated).
>
> Please make sure that 'pytest_bdd.templates' is included as a package by
> using
> the `packages` configuration field or the proper discovery methods
> (for example by using `find_namespace_packages(...)`/`find_namespace:`
> instead of `find_packages(...)`/`find:`).
>
> You can read more about "package discovery" and "data files" on setuptools
> documentation page.
>
>
> !!
>
> check.warn(importable)
> running install_lib
> creating /<>/debian/python3-pytest-bdd/usr
> creating /<>/debian/python3-pytest-bdd/usr/lib
> creating /<>/debian/python3-pytest-bdd/usr/lib/python3.11
> creating
> /<>/debian/python3-pytest-bdd/usr/lib/python3.11/dist-packages
> creating
> /<>/debian/python3-pytest-bdd/usr/lib/python3.11/dist-packages/pytest_bdd
> copying
> /<>/.pybuild/cpython3_3.11_pytest-bdd/build/pytest_bdd/__init__.py
> ->
> /<>/debian/python3-pytest-bdd/usr/lib/python3.11/dist-packages/pytest_bdd
> copying
> /<>/.pybuild/cpython3_3.11_pytest-bdd/build/pytest_bdd/parser.py
> ->
> /<>/debian/python3-pytest-bdd/usr/lib/python3.11/dist-packages/pytest_bdd
> copying
> /<>/.pybuild/cpython3_3.11_pytest-bdd/build/pytest_bdd/cucumber_json.py
> ->
> /<>/debian/python3-pytest-bdd/usr/lib/python3.11/dist-packages/pytest_bdd
> copying
> /<>/.pybuild/cpython3_3.11_pytest-bdd/build/pytest_bdd/hooks.py
> ->
> /<>/debian/python3-pytest-bdd/usr/lib/python3.11/dist-packages/pytest_bdd
> copying
> /<>/.pybuild/cpython3_3.11_pytest-bdd/build/pytest_bdd/exceptions.py
> ->
> /<>/debian/python3-pytest-bdd/usr/lib/python3.11/dist-packages/pytest_bdd
> copying
> /<>/.pybuild/cpython3_3.11_pytest-bdd/build/pytest_bdd/gherkin_terminal_reporter.py
> ->
> /<>/debian/python3-pytest-bdd/usr/lib/python3.11/dist-packages/pytest_bdd
> copying
> /<>/.pybuild/cpython3_3.11_pytest-bdd/build/pytest_bdd/feature.py
> ->
> /<>/debian/python3-pytest-bdd/usr/lib/python3.11/dist-packages/pytest_bdd
> copying
>
Bug#1029829: Server connections refused after applying update?
I applied this update to my one remaining buster machine and now it is refusing to connect to my bullseye-based amanda backup server. amcheck and the amanda server are both reporting "Connection refused" when accessing the updated buster machine. -- Barry A. Trent 952-829-5864, x109 barry.tr...@atcorp.com smime.p7s Description: S/MIME Cryptographic Signature
Bug#1022969: marked as done (isc-dhcp-client: dhcp6 client failing to renew the IPv6 address upon T1 expiry.)
Your message dated Thu, 23 Feb 2023 21:47:08 + with message-id and subject line Bug#1022969: fixed in isc-dhcp 4.4.1-2.3+deb11u2 has caused the Debian Bug report #1022969, regarding isc-dhcp-client: dhcp6 client failing to renew the IPv6 address upon T1 expiry. 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.) -- 1022969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022969 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: isc-dhcp-client Version: 4.4.1-2+deb10u1 Severity: normal Dear Maintainer, * What led up to the situation? Change the date to more than that of T1 and then systemctl restart networking.service. * What exactly did you do (or not do) that was effective (or ineffective)? 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 promiscuity 0 minmtu 0 maxmtu 0 numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 00:0d:3a:7a:1e:a5 brd ff:ff:ff:ff:ff:ff promiscuity 0 minmtu 68 maxmtu 65521 numtxqueues 64 numrxqueues 64 gso_max_size 62780 gso_max_segs 65535 inet 10.0.0.5/24 brd 10.0.0.255 scope global eth0 valid_lft forever preferred_lft forever inet6 2404:f800:8000:122::4/128 scope global deprecated valid_lft forever preferred_lft 0sec inet6 fe80::20d:3aff:fe7a:1ea5/64 scope link valid_lft forever preferred_lft forever * What was the outcome of this action? As a result, the IPv6 network communication of these VMs is problematic, causing business problems * What outcome did you expect instead? Renewal of the IPv6 address. -- System Information: Debian Release: 10.13 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-21-cloud-amd64 (SMP w/2 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages isc-dhcp-client depends on: ii debianutils4.8.6.1 ii iproute2 4.20.0-2+deb10u1 ii libc6 2.28-10+deb10u1 ii libdns-export1104 1:9.11.5.P4+dfsg-5.1+deb10u7 ii libisc-export1100 1:9.11.5.P4+dfsg-5.1+deb10u7 Versions of packages isc-dhcp-client recommends: pn isc-dhcp-common Versions of packages isc-dhcp-client suggests: pn avahi-autoipd pn isc-dhcp-client-ddns pn resolvconf -- Configuration Files: /etc/dhcp/dhclient.conf changed: option rfc3442-classless-static-routes code 121 = array of unsigned integer 8; send host-name = gethostname(); request subnet-mask, broadcast-address, time-offset, routers, domain-name, domain-name-servers, domain-search, host-name, dhcp6.name-servers, dhcp6.domain-search, dhcp6.fqdn, dhcp6.sntp-servers, netbios-name-servers, netbios-scope, interface-mtu, rfc3442-classless-static-routes, ntp-servers; timeout 300; -- no debconf information --- End Message --- --- Begin Message --- Source: isc-dhcp Source-Version: 4.4.1-2.3+deb11u2 Done: Bastian Blank We believe that the bug you reported is fixed in the latest version of isc-dhcp, 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 1022...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Blank (supplier of updated isc-dhcp 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: Mon, 20 Feb 2023 09:19:43 +0100 Source: isc-dhcp Architecture: source Version: 4.4.1-2.3+deb11u2 Distribution: bullseye Urgency: medium Maintainer: Debian ISC DHCP Maintainers Changed-By: Bastian Blank Closes: 1022969 Changes: isc-dhcp (4.4.1-2.3+deb11u2) bullseye; urgency=medium . * Non-maintainer upload. * Backport missing IPv6 address
Bug#1029803: marked as done (command-not-found breaks dist-upgrade bullseye → bookworm)
Your message dated Thu, 23 Feb 2023 21:17:08 + with message-id and subject line Bug#1029803: fixed in command-not-found 20.10.1-1+deb11u1 has caused the Debian Bug report #1029803, regarding command-not-found breaks dist-upgrade bullseye → 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.) -- 1029803: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029803 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: command-not-found Version: 20.10.1-1 Severity: grave Tags: patch X-Debbugs-Cc: deb...@rocketjump.eu, k...@debian.org Hi Julian, (this is somewhat related to #968757 and #954249) (kibi CCed) Steps to reproduce (on an bullseye installation) 1) Install command-not-found 2) Edit /etc/apt/sources.list to deb http://deb.debian.org/debian/ bookworm main contrib non-free non-free-firmware (note the new component non-free-firmware) 3) run `apt update` # apt update Hit:1 http://deb.debian.org/debian bullseye InRelease Hit:2 http://deb.debian.org/debian-security bullseye-security InRelease Hit:3 http://deb.debian.org/debian bullseye-updates InRelease Hit:4 http://deb.debian.org/debian bullseye-backports InRelease Hit:5 https://packages.chef.io/repos/apt/stable bullseye InRelease Hit:6 http://deb.debian.org/debian bookworm InRelease Hit:7 http://deb.debian.org/debian sid InRelease Hit:8 http://deb.debian.org/debian experimental InRelease Traceback (most recent call last): File "/usr/lib/cnf-update-db", line 26, in col.create(db) File "/usr/share/command-not-found/CommandNotFound/db/creator.py", line 95, in create self._fill_commands(con) File "/usr/share/command-not-found/CommandNotFound/db/creator.py", line 143, in _fill_commands self._parse_single_contents_file(con, f, fp.stdout) File "/usr/share/command-not-found/CommandNotFound/db/creator.py", line 282, in _parse_single_contents_file priority = component_priorities[component] KeyError: 'non-free-firmware' Reading package lists... Done E: Problem executing scripts APT::Update::Post-Invoke-Success 'if /usr/bin/test -w /var/lib/command-not-found/ -a -e /usr/lib/cnf-update-db; then /usr/lib/cnf-update-db > /dev/null; fi' E: Sub-process returned an error code This is already fixed in unstable, but in it's current form this will break the upgrade path from bullseye to bookworm. The fix is trivial, adding `'non-free-firmware': 60,` to CommandNotFound/db/creator.py is enough. I propose doing a p-u to fix it. Greets, Lee -- System Information: Debian Release: 11.6 APT prefers stable-updates APT policy: (990, 'stable-updates'), (990, 'stable-security'), (990, 'stable'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-0.deb11.6-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages command-not-found depends on: ii apt-file 3.2.2 ii lsb-release 11.1.0 ii python3 3.9.2-3 ii python3-apt 2.2.1 command-not-found recommends no packages. Versions of packages command-not-found suggests: pn snapd -- no debconf information -- debsums errors found: debsums: changed file /usr/share/command-not-found/CommandNotFound/db/creator.py (from command-not-found package) --- End Message --- --- Begin Message --- Source: command-not-found Source-Version: 20.10.1-1+deb11u1 Done: Paul Gevers We believe that the bug you reported is fixed in the latest version of command-not-found, 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 1029...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paul Gevers (supplier of updated command-not-found 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: Wed, 22 Feb 2023 16:09:19 +0100 Source: command-not-found Architecture: source Version: 20.10.1-1+deb11u1 Distribution: bullseye Urgency: medium Maintainer: Julian Andres Klode Changed-By: Paul Gevers Closes:
Bug#1026227: marked as done (vagrant: Uninstallable in sid with VirtualBox 7.0.x)
Your message dated Thu, 23 Feb 2023 21:17:11 + with message-id and subject line Bug#1026227: fixed in vagrant 2.2.14+dfsg-2 has caused the Debian Bug report #1026227, regarding vagrant: Uninstallable in sid with VirtualBox 7.0.x 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.) -- 1026227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026227 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: vagrant Version: 2.2.19+dfsg-2 Severity: serious Hi! Since virtualbox 7.0.4 got uploaded, vagrant is no longer installable in Debian sid. I assume this will require packaging a new upstream release to support the new virtualbox version 7.0.x series. Thanks, Guillem --- End Message --- --- Begin Message --- Source: vagrant Source-Version: 2.2.14+dfsg-2 Done: Antonio Terceiro We believe that the bug you reported is fixed in the latest version of vagrant, 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 1026...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Antonio Terceiro (supplier of updated vagrant 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: Tue, 07 Feb 2023 10:33:52 +0100 Source: vagrant Architecture: source Version: 2.2.14+dfsg-2 Distribution: bullseye Urgency: medium Maintainer: Debian Ruby Team Changed-By: Antonio Terceiro Closes: 1026227 Changes: vagrant (2.2.14+dfsg-2) bullseye; urgency=medium . * Add support for VirtualBox 7.0 (Closes: #1026227) Checksums-Sha1: ac347a7be1c7d44cbea048a7851abf7a3d0128ff 2569 vagrant_2.2.14+dfsg-2.dsc 1ac49363b4567573ec62c4c1cf1e182da0389651 17292 vagrant_2.2.14+dfsg-2.debian.tar.xz 2cb4135a82efe75b4756598f34fd428a741dbb4e 10770 vagrant_2.2.14+dfsg-2_amd64.buildinfo Checksums-Sha256: 0f5ed43ae4ecd4e14d69cdfbb76485d9770722a154260ce76498fbe83f0c7248 2569 vagrant_2.2.14+dfsg-2.dsc 8e6ef64a42d2de04db086e0970c609e6045b8ad527ba4284ceeca05acf8d2fe8 17292 vagrant_2.2.14+dfsg-2.debian.tar.xz 47fe167f08f67288dfc331a51dce5078bbc344c3250253a42fe8aea1df18fb19 10770 vagrant_2.2.14+dfsg-2_amd64.buildinfo Files: 69e5ad25a994c45933796c90aa3f030f 2569 admin optional vagrant_2.2.14+dfsg-2.dsc 1ce07b146650e476c46d3aaa60e994e2 17292 admin optional vagrant_2.2.14+dfsg-2.debian.tar.xz 727042b7cd4ca0e9e7dd10b69eba5762 10770 admin optional vagrant_2.2.14+dfsg-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAmP0LAIACgkQ/A2xu81G C94/gQ/+JoSs4HovfgaPIGyzcR48ayJrq/3xK8Kqiqxi9ZwAsGz6Tu02z6jcvb+E qKrBKzTVtSFzkfteMmAr2MWuFMSQ83LC1FMl2LmYMf9gZXXb2s9h72g11Fu0M5DC 9OpdQeZN5M58xqucJEGlAVk8q8wn+BI1h0uhKsgSH707foVPdxccreVR7yjuOFuG xwQYqAD0B8c7t8XoGaLG0WHmVdhk5em8NCQQwmRVIAECnhM7B7Oj0H0ffVELQnjp cvSJwbDJCGI+cVM3CKp3zfiZ4RfIB1L5e2I+E8Sw3adEr/bgk8OlYg8ysNWbfVSx Llu/b8UWn5A3GmJOx/dWaPCgcocssC0zeHzxK5aMdjTsvO6v2+H/NnQiRxlKwuzd kqXiXqOKGi/bYwPKXzCM5wxsISp/Ux+8ZH/sVeIMvXqvLedZijnAf0aMSi6g4tyz uHNMHj8zU983Gtv91SVsfaGSXqIguhcdycuMLwe3pgOJb/oTwFozj5ebdbjbPZhs jhnw8CdhkawyIXu2OOXL8KWyhjMNMsM1YxnQGT++bSumAR+0goRrYw4SzpV1c6r8 BzQ/vnYJKe3EGrYBydb6xB2OLX20MMCuoti310BTlpXtELL+kZlX4Y63arAiWRTH Vg5m4fce/vbCPPRykpZLdLOMLxk8Vc4YokgVXZstLpWgzWsi4dk= =RaJM -END PGP SIGNATURE End Message ---
Bug#1031834: nodejs: CVE-2023-23918 CVE-2023-23919 CVE-2023-23920
Source: nodejs Version: 18.13.0+dfsg1-1 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerabilities were published for nodejs. CVE-2023-23918[0]: | A privilege escalation vulnerability exists in Node.js 19.6.1, | 18.14.1, 16.19.1 and 14.21.3 that made it possible to | bypass the experimental Permissions | (https://nodejs.org/api/permissions.html) feature in Node.js and | access non authorized modules by using process.mainModule.require(). | This only affects users who had enabled the experimental permissions | option with --experimental-policy. CVE-2023-23919[1]: | A cryptographic vulnerability exists in Node.js 19.2.0, | 18.14.1, 16.19.1, 14.21.3 that in some cases did does not | clear the OpenSSL error stack after operations that may set it. This | may lead to false positive errors during subsequent cryptographic | operations that happen to be on the same thread. This in turn could be | used to cause a denial of service. CVE-2023-23920[2]: | An untrusted search path vulnerability exists in Node.js. 19.6.1, | 18.14.1, 16.19.1, and 14.21.3 that could allow an attacker | to search and potentially load ICU data when running with elevated | privileges. If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-23918 https://www.cve.org/CVERecord?id=CVE-2023-23918 [1] https://security-tracker.debian.org/tracker/CVE-2023-23919 https://www.cve.org/CVERecord?id=CVE-2023-23919 [2] https://security-tracker.debian.org/tracker/CVE-2023-23920 https://www.cve.org/CVERecord?id=CVE-2023-23920 Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Bug#1031278: marked as done (buddy: Contains non-source file)
Your message dated Thu, 23 Feb 2023 21:03:56 + with message-id and subject line Bug#1031278: fixed in buddy 2.4+dfsg-1 has caused the Debian Bug report #1031278, regarding buddy: Contains non-source file 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.) -- 1031278: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031278 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: buddy Version: 2.4-11 Severity: serious The doc/buddy.ps file contained in the package is not a source file. Please repack to get rid of it or build it from source if it is available. --- End Message --- --- Begin Message --- Source: buddy Source-Version: 2.4+dfsg-1 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of buddy, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1031...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated buddy 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: Thu, 23 Feb 2023 21:35:42 +0100 Source: buddy Architecture: source Version: 2.4+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Andreas Tille Closes: 1031278 Changes: buddy (2.4+dfsg-1) unstable; urgency=medium . * Take over package into Debian Science team maintenance * Fix homepage * Exclude non-source file doc/buddy.ps Closes: #1031278 * Remove outdated autotools helper files * d/rules: Short dh * Hardening * Standards-Version: 4.6.2 (routine-update) * debhelper-compat 13 (routine-update) * Remove trailing whitespace in debian/changelog (routine-update) * Remove trailing whitespace in debian/control (routine-update) * Add salsa-ci file (routine-update) * Rules-Requires-Root: no (routine-update) * Trim trailing whitespace. * Set upstream metadata fields: Archive, Bug-Database, Name, Repository. * Drop unneeded Build-Depends * Simplify examples usage * Add autopkgtest Checksums-Sha1: 9e3af46379a931f22ccabdfa9ca8ca4b366e1b90 2076 buddy_2.4+dfsg-1.dsc 67f37f588331bed01ac87d35a27d1c6db7392df4 356640 buddy_2.4+dfsg.orig.tar.xz d29b055f841130c307b128d3d23da8bd7c570402 5104 buddy_2.4+dfsg-1.debian.tar.xz 4d5e8a458d80369da68a847d5bd6bff86843c92e 6579 buddy_2.4+dfsg-1_amd64.buildinfo Checksums-Sha256: 11804f7e43cbd1eff41d76a3daec42ee0210ff77f7725915cf9a3dad4b3806aa 2076 buddy_2.4+dfsg-1.dsc 6ccfd46769bf32ebf3561c6e0364330bf0cf63ee5d632afd5cbc98b216bd2a85 356640 buddy_2.4+dfsg.orig.tar.xz 95f98fe2177b7964fabc549a2be96754307f4e4d427398227d72a06edafff15c 5104 buddy_2.4+dfsg-1.debian.tar.xz 18a294bcfebb9df71292b1a32ad9e693b6b0336c113624012058efe5914c3e89 6579 buddy_2.4+dfsg-1_amd64.buildinfo Files: 04f098475190302fed3ef0631c58259c 2076 devel optional buddy_2.4+dfsg-1.dsc 4c502d28ec1283abda3d56f47a8074a6 356640 devel optional buddy_2.4+dfsg.orig.tar.xz 95adaafa749da80b68d978e15857f63f 5104 devel optional buddy_2.4+dfsg-1.debian.tar.xz 4568094a21ffb8663112a6122509358c 6579 devel optional buddy_2.4+dfsg-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmP3zxERHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtEYpA//Qn7xsWl3sNmsP/otDNSMYUIfRIBD0DTm clwn0Kig8es+kt5JOjty7uOYYlp+/9oRrNE48/fMJ9yggr2ZueyZemj6DGKt20zc avlHiXSmQCriMiT6nsV8beMqX5R7lblc3NuvplQLvfiTZGn32wBE/BYVFotqcysY J0DEEvcnN344Tks1LeICcMcs23LjyF5iis149uL2lYDDZQWI2oqf5x9Z3/XifxyI nwhCCJk6IKgiv5cNkH2UE7GjNhRYsK9GQXhwXE0RbD4j+5mWVfzlBIA/X0l0wgyY UHx9nNfnc2r2WB5Uf1DVN9hSdeBrgFMNwTosP9oUtqQ2YXeOPcEhMDAiPg92Vhi7 HZUAXzMqp0zh34akVrRtRxxY56I3ZkAESgDVQxoaC1LcN5LbOd/41F3WD5SEDMTL JRcw4elsDe0PQLPA24nMHCU7bqJYvsa4+M+SOWHWnuGove5cxFiILpdxNNwuQiTK LNSTvYCQQIcHzgzqZbukPMTQA3hRk0wHqW+GAz8YZcB0J7/S3ZFfoDThorIhl4rc R4dlGndzzoUdvSEdVqzDYZ3085MeIRP3YXzzG88ZL0J2ch268B/9XnjyWSuQsaHD HuohqcsWy1rhjtLTMN66pBAvmtiPfrfLF7e+AVg61F7c3WpVUytEJAsPPKn5yhO5 imcCVtTYIPU= =IUn6 -END PGP SIGNATURE End Message ---
Bug#1029523: ruby-net-http-persistent want Ruby (~> 2.1)
Hi, On Tue, 24 Jan 2023 00:21:06 +0530 Pirate Praveen wrote: net-http-persistent (~> 3.0, >= 3.0.0) was resolved to 3.1.0, which depends on Ruby (~> 2.1) This doesn't seem to be an issue on reproducible builds [1] when building ruby-faraday. Does that make sense? Paul [1] https://tests.reproducible-builds.org/debian/history/ruby-faraday.html OpenPGP_signature Description: OpenPGP digital signature
Processed: bookworm-ignore
Processing commands for cont...@bugs.debian.org: > # too late now > tag 994758 bookworm-ignore Bug #994758 [libsgutils2-2] Soname change without package name change Added tag(s) bookworm-ignore. > tag 1000955 moreinfo Bug #1000955 [libkf5globalaccel-bin] libkf5globalaccel-bin: /usr/bin/kglobalaccel5 eats up huge amount of CPU after suspend Added tag(s) moreinfo. > tag 1014503 bookworm-ignore Bug #1014503 [bind9-libs] bind9-libs: please provide libraries that enable reverse dependencies to use them Added tag(s) bookworm-ignore. > tag 1030129 bookworm-ignore Bug #1030129 [ca-certificates-java] ca-certificates-java - Fails to install with OpenJDK 21: Error loading java.security file Added tag(s) bookworm-ignore. > tag 1031364 bookworm-ignore Bug #1031364 [vmdb2] e2fsprogs: generates filesystems that grub-install doesn't recognize Added tag(s) bookworm-ignore. > thanks Stopping processing here. Please contact me if you need assistance. -- 1000955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000955 1014503: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014503 1030129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030129 1031364: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031364 994758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994758 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: runit fails to install: useradd: not found
Processing control commands: > affects -1 + runit Bug #1031833 [sysuser-helper] runit fails to install: useradd: not found Added indication that 1031833 affects runit -- 1031833: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031833 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1031833: runit fails to install: useradd: not found
Package: sysuser-helper Version: 2.1.2-54 Severity: serious Justification: makes runit fail to install Control: affects -1 + runit runit fails to install in unstable. An easy reproducer is this: $ mmdebstrap --variant=essential --include runit sid /dev/null ... Setting up runit (2.1.2-54) ... /lib/sysuser-helper/sysuser-helper: 19: useradd: not found dpkg: error processing package runit (--configure): installed runit package post-installation script subprocess returned error exit status 127 Errors were encountered while processing: runit E: Sub-process env returned an error code (1) E: setup failed: E: apt-get -o Dir::Bin::dpkg=env -o DPkg::Options::=--unset=TMPDIR -o DPkg::Options::=dpkg -o DPkg::Chroot-Directory=/tmp/mmdebstrap.ZhieYGlyAI -d I: main() received signal PIPE: waiting for setup... I: removing tempdir /tmp/mmdebstrap.ZhieYGlyAI... E: mmdebstrap failed to run $ I think the failure actually is with sysuser-helper, which misses a dependency on passwd. passwd used to be pseudo-essential but no longer is. As such sysuser-helper must depend on it explicitly. Helmut
Processed: Re: Bug#1030297: pytango: FTBFS: = 364 failed, 689 passed, 26 xfailed, 2 warnings, 40 errors in 176.40s (0:02:56) =
Processing control commands: > forwarded -1 https://gitlab.com/tango-controls/pytango/-/issues/450 Bug #1030297 [src:pytango] pytango FTBFS on IPV6-only buildds Set Bug forwarded-to-address to 'https://gitlab.com/tango-controls/pytango/-/issues/450'. -- 1030297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030297 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1030297: pytango: FTBFS: = 364 failed, 689 passed, 26 xfailed, 2 warnings, 40 errors in 176.40s (0:02:56) =
Control: forwarded -1 https://gitlab.com/tango-controls/pytango/-/issues/450 Hi, On Fri, Feb 03, 2023 at 08:40:38PM +0200, Adrian Bunk wrote: > Control: retitle -1 pytango FTBFS on IPV6-only buildds > > This is FTBFS on IPV6-only buildds: > https://buildd.debian.org/status/logs.php?pkg=pytango=all > https://buildd.debian.org/status/logs.php?pkg=pytango=9.3.6-2%2B > > Several error messages in lines like > > self.host, self.port = args > E ValueError: too many values to unpack (expected 2) > confirm that it is related to that. Thank you for the pre-diagnosis. This is fully accurate, but the issue is deeper. It also isn't the first IPv6-only FTBFS for pytango. The earlier one was #1014179 and pytango actually carries a patch for it. Unfortunately, the patch does not work at all. The patch also isn't upstream, but upstream has an issue for it and seems responsive. Let's keep the technical discussion at the upstream tracker. In essence though, it seems that cpptango does not work with IPv6 at all. This isn't super convenient, but unworkable either. However, it seems that it requires a non-loopback IP address and that's something we don't have on all buildds. It also seems to work when the hostname resolves to the loopback address, but that's also not the case on buildds. Helmut
Bug#1031832: python3-vispy: import fails: AttributeError: module 'numpy' has no attribute 'bool'
Package: python3-vispy Severity: serious Dear Maintainer, This import fails in a Sid chroot: >>> from vispy.plot import Fig /usr/lib/python3/dist-packages/vispy/gloo/program.py:113: FutureWarning: In the future `np.bool` will be defined as the corresponding NumPy scalar. 'bvec2': (np.bool, 2), Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/vispy/plot/__init__.py", line 34, in from .fig import Fig # noqa File "/usr/lib/python3/dist-packages/vispy/plot/fig.py", line 5, in from ..scene import SceneCanvas File "/usr/lib/python3/dist-packages/vispy/scene/__init__.py", line 33, in from .visuals import * # noqa ^^ File "/usr/lib/python3/dist-packages/vispy/scene/visuals.py", line 18, in from .. import visuals File "/usr/lib/python3/dist-packages/vispy/visuals/__init__.py", line 14, in from .axis import AxisVisual # noqa File "/usr/lib/python3/dist-packages/vispy/visuals/axis.py", line 11, in from .visual import CompoundVisual File "/usr/lib/python3/dist-packages/vispy/visuals/visual.py", line 90, in from .. import gloo File "/usr/lib/python3/dist-packages/vispy/gloo/__init__.py", line 54, in from .program import Program # noqa File "/usr/lib/python3/dist-packages/vispy/gloo/program.py", line 74, in class Program(GLObject): File "/usr/lib/python3/dist-packages/vispy/gloo/program.py", line 113, in Program 'bvec2': (np.bool, 2), ^^^ File "/usr/lib/python3/dist-packages/numpy/__init__.py", line 305, in __getattr__ raise AttributeError(__former_attrs__[attr]) AttributeError: module 'numpy' has no attribute 'bool'. `np.bool` was a deprecated alias for the builtin `bool`. To avoid this error in existing code, use `bool` by itself. Doing this will not modify any behavior and is safe. If you specifically wanted the numpy scalar type, use `np.bool_` here. The aliases was originally deprecated in NumPy 1.20; for more details and guidance see the original release note at: https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations. Did you mean: 'bool_'? Kind Regards
Processed: found 1031730 in 1:27.1+1-3.1
Processing commands for cont...@bugs.debian.org:
> found 1031730 1:27.1+1-3.1
Bug #1031730 {Done: Sean Whitton } [src:emacs] emacs:
CVE-2022-48339 CVE-2022-48338 CVE-2022-48337
Marked as found in versions emacs/1:27.1+1-3.1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1031730: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031730
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1016732: marked as done (node-sockjs throws: TypeError: Cannot read properties of undefined (reading 'addEventListener') at WebSocketReceiver.setUp)
Your message dated Thu, 23 Feb 2023 19:35:12 + with message-id and subject line Bug#1016732: fixed in node-sockjs 0.3.24+~0.3.33-6 has caused the Debian Bug report #1016732, regarding node-sockjs throws: TypeError: Cannot read properties of undefined (reading 'addEventListener') at WebSocketReceiver.setUp 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.) -- 1016732: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016732 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-sockjs Version: 0.3.24+~0.3.33-1 Severity: serious X-Debbugs-Cc: e...@ericebrown.com Hi, On running shiny-server with 0.3.24+~0.3.33-1 it chokes with: | [2022-08-06T04:59:03.613] [ERROR] shiny-server - Uncaught exception: TypeError: Cannot read properties of undefined (reading 'addEventListener') | [2022-08-06T04:59:03.614] [ERROR] shiny-server - TypeError: Cannot read properties of undefined (reading 'addEventListener') |at WebSocketReceiver.setUp (/usr/share/nodejs/sockjs/lib/trans-websocket.js:76:24) |at new GenericReceiver (/usr/share/nodejs/sockjs/lib/transport.js:313:12) |at new WebSocketReceiver (/usr/share/nodejs/sockjs/lib/trans-websocket.js:63:9) |at ws.onopen (/usr/share/nodejs/sockjs/lib/trans-websocket.js:31:55) |at WebSocket.dispatchEvent (/usr/share/nodejs/faye-websocket/lib/faye/websocket/api/event_target.js:24:30) |at WebSocket._open (/usr/share/nodejs/faye-websocket/lib/faye/websocket/api.js:144:10) |at Hybi. (/usr/share/nodejs/faye-websocket/lib/faye/websocket/api.js:35:49) |at Hybi.emit (node:events:513:28) |at Hybi._open (/usr/share/nodejs/websocket-driver/lib/websocket/driver/base.js:148:10) |at Hybi.start (/usr/share/nodejs/websocket-driver/lib/websocket/driver/base.js:105:34) | [2022-08-06T04:59:03.615] [INFO] shiny-server - Stopping listener on http://[::]:3838 | [2022-08-06T04:59:03.615] [INFO] shiny-server - Shutting down worker processes (with notification) | /usr/lib/shiny-server/lib/main.js:391 | throw err; | ^ | | TypeError: Cannot read properties of undefined (reading 'addEventListener') |at WebSocketReceiver.setUp (/usr/share/nodejs/sockjs/lib/trans-websocket.js:76:24) |at new GenericReceiver (/usr/share/nodejs/sockjs/lib/transport.js:313:12) |at new WebSocketReceiver (/usr/share/nodejs/sockjs/lib/trans-websocket.js:63:9) |at ws.onopen (/usr/share/nodejs/sockjs/lib/trans-websocket.js:31:55) |at WebSocket.dispatchEvent (/usr/share/nodejs/faye-websocket/lib/faye/websocket/api/event_target.js:24:30) |at WebSocket._open (/usr/share/nodejs/faye-websocket/lib/faye/websocket/api.js:144:10) |at Hybi. (/usr/share/nodejs/faye-websocket/lib/faye/websocket/api.js:35:49) |at Hybi.emit (node:events:513:28) |at Hybi._open (/usr/share/nodejs/websocket-driver/lib/websocket/driver/base.js:148:10) |at Hybi.start (/usr/share/nodejs/websocket-driver/lib/websocket/driver/base.js:105:34) | | Node.js v18.6.0 While it is running perfectly ok _with 0.3.24-2_. Since this is not a new release, there is a regression with the new changelog revision. In particular, it seems that something is off with the coffeescript generated files. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.14.0-2-amd64 (SMP w/8 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages node-sockjs depends on: pn node-faye-websocket ii node-uuid 8.3.2+~8.3.3-2 pn node-websocket-driver node-sockjs recommends no packages. node-sockjs suggests no packages. --- End Message --- --- Begin Message --- Source: node-sockjs Source-Version: 0.3.24+~0.3.33-6 Done: Nilesh Patra We believe that the bug you reported is fixed in the latest version of node-sockjs, 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 1016...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nilesh Patra (supplier of updated node-sockjs package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive
Bug#1012138: marked as done (CVE-2021-40426)
Your message dated Thu, 23 Feb 2023 19:32:31 + with message-id and subject line Bug#1012138: fixed in sox 14.4.2+git20190427-2+deb11u1 has caused the Debian Bug report #1012138, regarding CVE-2021-40426 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.) -- 1012138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012138 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sox Version: 14.4.2+git20190427-3 Severity: grave Tags: security X-Debbugs-Cc: Debian Security Team https://talosintelligence.com/vulnerability_reports/TALOS-2021-1434 The report states that upstream was notified, but we need to figure out whether this was addressed by upstream already or not (and if so, in which commit) Cheers, Moritz --- End Message --- --- Begin Message --- Source: sox Source-Version: 14.4.2+git20190427-2+deb11u1 Done: Moritz Mühlenhoff We believe that the bug you reported is fixed in the latest version of sox, 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 1012...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Moritz Mühlenhoff (supplier of updated sox 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, 17 Feb 2023 17:13:54 +0100 Source: sox Architecture: source Version: 14.4.2+git20190427-2+deb11u1 Distribution: bullseye-security Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Moritz Mühlenhoff Closes: 1010374 1012138 1012516 1021133 1021134 1021135 Changes: sox (14.4.2+git20190427-2+deb11u1) bullseye-security; urgency=medium . * CVE-2021-23159 CVE-2021-23172 (Closes: #1021133, #1021134) * CVE-2021-3643 CVE-2021-23210 (Closes: #1010374) * CVE-2021-33844 (Closes: #1021135) * CVE-2021-40426 (Closes: #1012138) * CVE-2022-31650 (Closes: #1012516) * CVE-2022-31651 (Closes: #1012516) * All patches taken from Helmut Grohne's uploads to unstable, thanks! Checksums-Sha1: b517566e2935d6632abdf865e3335edf1cc87fdf 2858 sox_14.4.2+git20190427-2+deb11u1.dsc dc9668256b9d81ef25d672f14f12ec026b0b4087 935449 sox_14.4.2+git20190427.orig.tar.bz2 b8421c9c64d63e1f25c4678fdd38d6bfd70e5faa 27088 sox_14.4.2+git20190427-2+deb11u1.debian.tar.xz Checksums-Sha256: 015a6e0bb053a2cd3231be0ad4821b5c51cea8c1f90d9db7001f5cde066953ec 2858 sox_14.4.2+git20190427-2+deb11u1.dsc 81a6956d4330e75b5827316e44ae381e6f1e8928003c6aa45896da9041ea149c 935449 sox_14.4.2+git20190427.orig.tar.bz2 9a695b613dedf66aa5112b3bfe4bab966656880efbad911d16f09ea0fc8f40ad 27088 sox_14.4.2+git20190427-2+deb11u1.debian.tar.xz Files: 8f475269158258bc09eedd34a397390d 2858 sound optional sox_14.4.2+git20190427-2+deb11u1.dsc ba804bb1ce5c71dd484a102a5b27d0dd 935449 sound optional sox_14.4.2+git20190427.orig.tar.bz2 e68b99879c9d6d41116402f361139a88 27088 sound optional sox_14.4.2+git20190427-2+deb11u1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEtuYvPRKsOElcDakFEMKTtsN8TjYFAmPvzKYACgkQEMKTtsN8 TjbnYBAAsEIB6Cqm95H3YT7T2cE7inynwFladhbIT81jATWKR5Ffa+FXMfuQ5k2n MCK/R2iWAvxOBFrugEl6RC0xDxTQ1EQVXG0f82ewJglUFh/Yp1Z+vBgEUC+AFkYn E85x07Y7cBzqXWWZxhPRX0imgxW67b6bZkKdsM7C4vv+LThM9bCeCjBh3qqcqQd3 d4x6lBFjeYs5yYZd1GZ5tZkFVL8vXPD6NrFIsojkdLURMji+JKFNtJE1vJEHEUyv kuUmaqykONxhtIpUKfinVvsUdXygZtY+HvbhEc5aERlZ/QhBCLYfs+oNmjva26Ju SxPLoiI6U9G2qH7P8iX5sURhNTdvjW9ypsKZF2Fcfonx2gitP1uRCblFtzPrP3k0 lO2S2LbAWRsiMnn9RMWDfIL9zgFkkFrVtJDI6qSahJae5t3GFioxUqLsucemn4bH AvONgB1r2PM9acM2iQcxCGZxM7wCRAmrF1lDU3hNXq6IWvQ7LENqEskuKEniLvlc NNQLEOZ8MEDiXrnttMBW7KHbHcis7AHhykKDYjMkzbvrod0FQxjwQE6pU4t2EF0Y PBt4ZD5BvOR+AvWlhi6LJ8SVVn8p9YCMZZ1gulo9YsgxMC7SsISJ72yNSuALfgGF jqx94ohXuCjx3PfLXxhfVkyzl/YqUJLlKshUkY61Plw76d1MdQM= =SaAi -END PGP SIGNATURE End Message ---
Processed: Re: Bug#1031626: marked as done (gdb-doc: Keep new version out of testing until gdb migrates)
Processing control commands:
> reopen -1
Bug #1031626 {Done: Héctor Orón Martínez } [gdb-doc] gdb-doc:
Keep new version out of testing until gdb migrates
'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 gdb-doc/13.1-1.
--
1031626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031626
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1031626: marked as done (gdb-doc: Keep new version out of testing until gdb migrates)
Control: reopen -1 On 2023-02-23 19:09 +, Debian Bug Tracking System wrote: > From: Adrian Bunk > Subject: gdb-doc: Keep new version out of testing until gdb migrates > To: Debian Bug Tracking System > Date: Sun, 19 Feb 2023 15:46:01 +0200 (4 days, 5 hours, 33 minutes ago) > Message-ID: <167681436181.973107.11105752777461364991.reportbug@localhost> > X-Mailer: reportbug 7.10.3+deb11u1 > > Package: gdb-doc > Version: 13.0.91.20230210-0.2 > Severity: serious > Control: block -1 by 1031625 > > This bug exists to keep the new version of gdb-doc out of testing > until gdb migrates, it can be closed at the same time as #1031625. > -- > Source: gdb-doc > Binary: gdb-doc > Architecture: source all > Version: 13.1-1 > Distribution: unstable > Urgency: high > Maintainer: Héctor Orón Martínez > Changed-By: Héctor Orón Martínez > Description: > gdb-doc- The GNU Debugger Documentation > Closes: 1031626 > Changes: > gdb-doc (13.1-1) unstable; urgency=high > . >* New upstream version 13.1 > (Closes: #1031626) Thanks for the update of gdb-doc, but it still should not migrate to testing while gdb is kept out there by both #1031745 and a manual block request by the release team. Please keep this bug open until gdb 13.1 migrates. Cheers, Sven
Processed: your mail
Processing commands for cont...@bugs.debian.org: > severity 1031639 normal Bug #1031639 [freedom-maker] e2fsprogs: generates filesystems that grub-install doesn't recognize Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1031639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031639 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1031626: marked as done (gdb-doc: Keep new version out of testing until gdb migrates)
Your message dated Thu, 23 Feb 2023 19:05:52 + with message-id and subject line Bug#1031626: fixed in gdb-doc 13.1-1 has caused the Debian Bug report #1031626, regarding gdb-doc: Keep new version out of testing until gdb migrates 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.) -- 1031626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031626 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gdb-doc Version: 13.0.91.20230210-0.2 Severity: serious Control: block -1 by 1031625 This bug exists to keep the new version of gdb-doc out of testing until gdb migrates, it can be closed at the same time as #1031625. --- End Message --- --- Begin Message --- Source: gdb-doc Source-Version: 13.1-1 Done: Héctor Orón Martínez We believe that the bug you reported is fixed in the latest version of gdb-doc, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1031...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Héctor Orón Martínez (supplier of updated gdb-doc 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: Thu, 23 Feb 2023 19:38:27 +0100 Source: gdb-doc Binary: gdb-doc Architecture: source all Version: 13.1-1 Distribution: unstable Urgency: high Maintainer: Héctor Orón Martínez Changed-By: Héctor Orón Martínez Description: gdb-doc- The GNU Debugger Documentation Closes: 1031626 Changes: gdb-doc (13.1-1) unstable; urgency=high . * New upstream version 13.1 (Closes: #1031626) * debian/compat: bump to 10, no changes * drop lintian overrides, no longer needed * debian/rules: install changelogs * debian/control: - drop dependency, no longer needed - bump debhelper to v10 - bump standards version, no changes - adjust build dependencies Checksums-Sha1: be2a043ee021441ba0edb9e7c944167e63032672 1915 gdb-doc_13.1-1.dsc a09d5a7875f67d37506da17e5332017be1aabf64 25435268 gdb-doc_13.1.orig.tar.xz 93bc2c13c314467a7f7a174e97caba7648e81ec9 13320 gdb-doc_13.1-1.debian.tar.xz 8bd9ce7f4cd8faf3cba6559f6c9e841d4af074a2 5229312 gdb-doc_13.1-1_all.deb 1192d2a15307b02076ecb6a1c0a55f30bb877a46 7402 gdb-doc_13.1-1_amd64.buildinfo Checksums-Sha256: 8fcf5e4c7274fcea59eb462c980beb965b1ea452f998d925c46814df51c83076 1915 gdb-doc_13.1-1.dsc 0204f47a01b803143baa3be40aedc0b95b5c4c040c189a20cc76b37960ffa96f 25435268 gdb-doc_13.1.orig.tar.xz aa987f546c2b0f71370409d39862a91921262458475b270d14fa5ff866a588f6 13320 gdb-doc_13.1-1.debian.tar.xz f04bb1f2b05ca553826fada6f3cc8600759761350502ea7a861f5ed8218d6480 5229312 gdb-doc_13.1-1_all.deb 464866d495b161e28bc3a43beb332d9d4a205988bd93832eb0efa200c41655ca 7402 gdb-doc_13.1-1_amd64.buildinfo Files: a2086a95d945bdfe49b8741d7121db5f 1915 non-free/devel optional gdb-doc_13.1-1.dsc 89d578d0a561693054eaf1a738d782e3 25435268 non-free/devel optional gdb-doc_13.1.orig.tar.xz d373b53ef5b495a4346829f9b0e41c99 13320 non-free/devel optional gdb-doc_13.1-1.debian.tar.xz 3e5215e41b2df92fbf4b0f5889ade068 5229312 non-free/doc optional gdb-doc_13.1-1_all.deb 4e43f678e642be76ef41b6586dc8fbbe 7402 non-free/devel optional gdb-doc_13.1-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE6Q8IiVReeMgqnedOryKDqnbirHsFAmP3tOEACgkQryKDqnbi rHtsoQ//TI3cCmFzdGg88Ar26qfsNCjOWwi5RKGfiR6RGfAvIU47HkFpVVGk3noA 3Ud9u4Fs5MQi5D7r1cawunD9Lh7I4NI4jlEeXhX/rxOUI9U4f3d07qapdg8jB3Dz gSzEhl/cl85SFHtEfmfY7MZdwa6WSAM/F90CukTRyVjyT5tcBKyQk2YLtKzy2vB0 +zNXb2tCNP4M+LyhSh+ySQGL4Lidah+PuFelvsFY/btq97wUbP0F3Upi4WCb5dBY Qsx1wz5vYTBt8kUv4Aj1ZAMKg9PXVEjlCftcdSlxpTJY7tmIn6ULUY27exnpOdS3 qz7CJu8VVC+RqwgcuJX2F7KIf30d+4BrfEZmCzHGlH1HMHlC0fwoa5tGAJNCJPOo kQ2qrFPK7F5e3emDB9IMpsoaqtecuJrSypFEbWcbTVeU3vSH7gTpajkbcaXP2Jt/ 2MGHfBoHadLbcicnfycgZ1NocdK2h2hdLCob4rPBykzAfFtN8+vwQ19R438ceazp 1It51NLAlC+nWLJqQeb2mQ8SbyVGEmDz4zE4k1WzbrpHojjb1YVaBnS6nvqMk89Y tOOlZzUVQ/1B4rgHFtx9uytxDwy3azdL5/RIzt8rx6KdAZlCg+xoKu03esC/aC1Q qZnjm+aKjrXuUPwMW06wFBTWLDZShJZH5pmBAmKrPRhAXo4hFzI= =NgEO -END PGP SIGNATURE End Message ---
Bug#1031639: Bug#1030939: e2fsprogs: generates filesystems that grub-install doesn't recognize
On Sun, 19 Feb 2023 19:01:22 +0100 Paul Gevers wrote: > On 2023-02-15 21:04:36 +0100, Sebastian Ramacher wrote: > > > > On 2023-02-14 01:01:38 +0100, Daniel Leidert wrote: > > > > > > This problem breaks e.g. vmdb2. I can no longer create a Bullseye > > > system image with vmdb2 on Sid, because the grub-install step in the > > > Bullseye chroot now fails, because the created filesystem (created with > > > e2fsprogs on Sid) cannot be recognized by grub. I have to downgrade > > > e2fsprogs to the version in Testing to get the build going again. It > > > also means that a Bookworm system can never be used to format and > > > debootstrap a Bullseye or Buster system that requires a grub > > > installation. > > > > > > I guess that the fix applied to grub2 in Sid would have to be applied > > > to grub2 in Bullseye as well (and basically to any grub2 package in any > > > Debian or Ubuntu or Raspbian release supported by debootstrap). > > > > > > This situation is really messy. It breaks basically all my image builds > > > with vmdb2. > > > > Regardless of the outcome of #1031325, this issue will need to be fixed > > in vmdb2 eventually. vmdb2, similar to other bootstraping tools, has to > > account for the feature and disable it if necessary for older > > distributions. > > > > Cloning and reassign to vmdb2. > > Based on more feedback from #10313225, I am also cloning and reassigning > this issue to fai and grml-debootstrap. Dear maintainers, please check > whether this issue is relevant for your packages. The same appears to apply for debos and freedom-maker. Dear maintainers, please check whether this issue is relevant for your packages. Control: severity -1 normal The images built by freedom-maker have btrfs root partition by default, which are not affected by e2fsprogs. Although freedom-maker includes code to support ext4 root partition, to actually build an image using ext4 requires patching the source code of freedom-maker. If one modifies freedom-maker in this way, then there will be an error if building a bullseye image on a bookworm host: 2023-02-23 13:08:25,297 - ERROR - Target failed - virtualbox-amd64-ext4 Traceback (most recent call last): File "", line 198, in _run_module_as_main File "", line 88, in _run_code File "/home/james/salsa/freedombox-team/freedom-maker/freedommaker/__main__.py", line 13, in Application().run() File "/home/james/salsa/freedombox-team/freedom-maker/freedommaker/application.py", line 57, in run builder.build() File "/home/james/salsa/freedombox-team/freedom-maker/freedommaker/builders/vm.py", line 21, in build self.make_image() File "/home/james/salsa/freedombox-team/freedom-maker/freedommaker/builder.py", line 106, in make_image self._get_builder_backend().make_image() File "/home/james/salsa/freedombox-team/freedom-maker/freedommaker/internal.py", line 43, in make_image self._install_boot_loader() File "/home/james/salsa/freedombox-team/freedom-maker/freedommaker/internal.py", line 352, in _install_boot_loader library.install_grub(self.state) File "/home/james/salsa/freedombox-team/freedom-maker/freedommaker/library.py", line 476, in install_grub run_in_chroot(state, ['grub-install', device] + args) File "/home/james/salsa/freedombox-team/freedom-maker/freedommaker/library.py", line 49, in run_in_chroot return run(*args, **kwargs) File "/home/james/salsa/freedombox-team/freedom-maker/freedommaker/library.py", line 43, in run return cliapp.runcmd(*args, **kwargs) ^^ File "/usr/lib/python3/dist-packages/cliapp/runcmd.py", line 64, in runcmd raise cliapp.AppException(msg) cliapp.app.AppException: Command failed: chroot /tmp/tmpxa690dib grub-install /dev/loop0 b'' b'Installing for i386-pc platform.\ngrub-install: error: unknown filesystem.\n' Building a bookworm image that uses ext4 does not have this error. In addition, it's not clear to me that there is a requirement for freedom-maker in bookworm to build bullseye images. OpenPGP_signature Description: OpenPGP digital signature
Processed: severity of 1031809 is important
Processing commands for cont...@bugs.debian.org: > severity 1031809 important Bug #1031809 [webp-pixbuf-loader] Bump webp-pixbuf-loader version to 0.1.2 as it contains important bugfixes Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1031809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031809 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1031379: Works on my machine
Hello, I'm also using it on amd64 and it works without any noticable problems. I would first check if the TV card works at all. I initially had some problems, but these are not related to kaffeine. So I suggest to downgrade this bug and tag it +moreinfo. Greetings Helge -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software "libre": http://www.ffii.de/ signature.asc Description: PGP signature
Processed: Re: python-bottle: FTBFS: AssertionError: b'OK' != "URLError(ConnectionRefusedError(111, 'Connection refused'))"
Processing control commands: > tags -1 patch Bug #1028743 [src:python-bottle] python-bottle: FTBFS: AssertionError: b'OK' != "URLError(ConnectionRefusedError(111, 'Connection refused'))" Added tag(s) patch. -- 1028743: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028743 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1030434: marked as done (rauc: FTBFS: tests failed writing: Error opening file ?/tmp/tmp.I4dlWcaK4g/notexisting/out.raucb?: No such file or directory)
Your message dated Thu, 23 Feb 2023 16:49:02 + with message-id and subject line Bug#1030434: fixed in opensc 0.23.0-0.2 has caused the Debian Bug report #1030434, regarding rauc: FTBFS: tests failed writing: Error opening file ?/tmp/tmp.I4dlWcaK4g/notexisting/out.raucb?: No such file or directory 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.) -- 1030434: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030434 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rauc Version: 1.8-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230203 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. The full build log is available from: http://qa-logs.debian.net/2023/02/03/rauc_1.8-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230203;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230203=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: opensc Source-Version: 0.23.0-0.2 Done: Bastian Germann We believe that the bug you reported is fixed in the latest version of opensc, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1030...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Germann (supplier of updated opensc 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, 13 Feb 2023 17:13:20 +0100 Source: opensc Architecture: source Version: 0.23.0-0.2 Distribution: unstable Urgency: medium Maintainer: Debian OpenSC Maintainers Changed-By: Bastian Germann Closes: 1030434 Changes: opensc (0.23.0-0.2) unstable; urgency=medium . * Non-maintainer upload * Fix rauc build (Closes: #1030434) Checksums-Sha1: 903ae6f2dd4d5f482ff426c013490230e00f9ac3 2008 opensc_0.23.0-0.2.dsc 76c59162de318e6369f71d321f4ad10a98e75a84 15040 opensc_0.23.0-0.2.debian.tar.xz 047b72dd4f7cdcae44932255cb6a09fa552462a6 6093 opensc_0.23.0-0.2_source.buildinfo Checksums-Sha256: 5946e460fa7fe9499945c435b50089d2bae17b0a5413854a42a90aafd9a22735 2008 opensc_0.23.0-0.2.dsc 4c33b8e9e1ebaee0acc595e4e862cf83253c3fcd9f9b40684f139e9691ea 15040 opensc_0.23.0-0.2.debian.tar.xz b3bf7bfeb18bba44f45333a9a698863c11d3f2f1a7c02df9e5366f00d252a357 6093 opensc_0.23.0-0.2_source.buildinfo Files: 2711a742d61a14f8e1950a1db89e0dc5 2008 utils optional opensc_0.23.0-0.2.dsc 21ab2f77f6bb18326a6f0ab664560c88 15040 utils optional opensc_0.23.0-0.2.debian.tar.xz 27667f2498dfa13c41bb7a85dc2642cf 6093 utils optional opensc_0.23.0-0.2_source.buildinfo -BEGIN PGP SIGNATURE- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmPqYgkQHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFCoLC/92qn1h/JZ61Eg3JxE1rHRrAL638tFdXVUT GXzN8LrpU0APdmY1017t6DbWhpzD/XjlxoH8jREuOvpVuyO+W8kiPELx8VgZVR1l 65kH1OC/D36efx71wMxGWkw0lQjzlbtK4W9/TxYq5vTKiEVDpdyKGGfF9LbzPhwv kdegF3cvpnC+9N/dMdg2QqeRkHHXXPL1U/flfnFEVtGIR/f0SXjR9/bkdoqfhW/n Ww/dlwFKvfdJ8CuiN1+Q3q84T0b8IyjhibGBiKhN0d2bsKcbEbbPS734xS8lm8wy 9DGnuVGkFvQLYs29BylrjgOH/+aWvQj6RrSLBL2Qc5U3XMlN96sulSuCmixCZhf4 CrYbPWC7i3PkPURWhKX9DYfECwP8rGpSmvWFdenixotUOdtuFTzh5ojUpFfentm9 FYi7u6P0iQ8h02DsCJBAcInb4mEMxXPL22FMzALDGbkRiLmIBBxBbZfdCPb/qH3B ywwJ0sscnDHC1igOFSe0TdhsO6tSGCU= =qWHE -END PGP SIGNATURE End Message ---
Bug#1029092: Don't update mysql-defaults in Debian testing/Bookworm too early
> On Tue, 17 Jan 2023 08:00:00 -0800 =?UTF-8?B?T3R0byBLZWvDpGzDpGluZW4=?= > wrote: > > This severity 'serious' bug should prevent the migration > > automatically. Close this bug when migration is free to proceed. > > I believe this has happened now. Do you think it should solve that issue > I was seeing? Potentially, but I need more info. This mysql-defaults definitely needs to migrate for the full repository view to be correct/complete. I was planning to do it 1-2 days after mariadb has migrated.
Bug#1029092: Don't update mysql-defaults in Debian testing/Bookworm too early
Hi Otto, On Tue, 17 Jan 2023 08:00:00 -0800 =?UTF-8?B?T3R0byBLZWvDpGzDpGluZW4=?= wrote: This severity 'serious' bug should prevent the migration automatically. Close this bug when migration is free to proceed. I believe this has happened now. Do you think it should solve that issue I was seeing? Paul OpenPGP_signature Description: OpenPGP digital signature
Processed: Re: feynmf: FTBFS in bookworm (I can't open file `fmfsamp4')
Processing control commands: > tags -1 - help Bug #1029439 [src:feynmf] feynmf: FTBFS in bookworm (I can't open file `fmfsamp4') Removed tag(s) help. -- 1029439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029439 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1029439: feynmf: FTBFS in bookworm (I can't open file `fmfsamp4')
Source: feynmf Followup-For: Bug #1029439 Control: tags -1 - help
Processed: Re: feynmf: FTBFS in bookworm (I can't open file `fmfsamp4')
Processing control commands: > tags -1 patch Bug #1029439 [src:feynmf] feynmf: FTBFS in bookworm (I can't open file `fmfsamp4') Added tag(s) patch. -- 1029439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029439 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1029439: feynmf: FTBFS in bookworm (I can't open file `fmfsamp4')
Source: feynmf Followup-For: Bug #1029439 Control: tags -1 patch
Bug#1028416: shutdown system properly
Probably #778849
Processed: forwarded gdb issue
Processing commands for cont...@bugs.debian.org: > forwarded 1031745 https://sourceware.org/bugzilla/show_bug.cgi?id=30158 Bug #1031745 [gdb] gdb: breaks rustc gdb debuginfo tests Set Bug forwarded-to-address to 'https://sourceware.org/bugzilla/show_bug.cgi?id=30158'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1031745: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031745 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1029439: feynmf: FTBFS in bookworm (I can't open file `fmfsamp4')
On Thu, 23 Feb 2023 at 12:53, James Addison wrote: > > pass: texlive-base (2022.20220605-1) unstable; urgency=low > fail: texlive-base (2022.20220923-2) unstable; urgency=medium > > It should be possible to look at the differences between those (and > maybe the related packages such as texlive-latex-base) to find further > clues. I'm going to start on that fairly soon. Ok, it turns out that the problem was a compatibility-break between v2 and v3 of the base doc.sty file. Fortunately the texlive-latex-base package ships the previous (v2, feynmf-compatible) version of that file along with v3. Thanks, Jochen for providing a patch to resolve the bug. I'm able to successfully build manual.pdf using texlive-latex-base 2022.20230122-1 with that patch applied.
Bug#1029439: feynmf: FTBFS in bookworm (I can't open file `fmfsamp4')
Source: feynmf Followup-For: Bug #1029439 My current best guess is that this commit line in latex3 that added a dependency on 'hypdoc' to the 'latex/base/doc.sty' file could be the cause - note that GitHub may not expand the 'doc.sty' file by default in some web browsers due to their filtering of large diffs from the user in some cases: https://github.com/latex3/latex3/commit/015a0593721446d2f5ddfa8d2f5d7c44e9d00fe5#diff-7c335dcde21c7d07e25db3dd241750d7907f90e7ca9b59d4a97309b028e30275R982 I'm not sure why that would be backwards-incompatible with 'feynmf.dtx' though.
Bug#1029439: help fixing this bug
Hi Thorsten,
/usr/share/texlive/texmf-dist/tex/latex/base/doc.sty changed in
texlive-latex-base_2022.20220722-1. But it also ships doc-2021-06-01.sty
so the attached patch fixes the FTBFS.
Cheers Jochen
* Thorsten Alteholz [2023-02-14 09:28]:
In case somebody has any idea how to fix this bug, I would be happy to
apply a patch.
Thorsten
From d99bbd41e95a27849e611b11dee7688568dfc70c Mon Sep 17 00:00:00 2001
From: Jochen Sprickerhof
Date: Thu, 23 Feb 2023 13:53:42 +0100
Subject: [PATCH] Add patch for build failure
Closes: #1029439
---
debian/patches/0003-Use-old-doc-package.patch | 22 +++
debian/patches/series | 1 +
2 files changed, 23 insertions(+)
create mode 100644 debian/patches/0003-Use-old-doc-package.patch
diff --git a/debian/patches/0003-Use-old-doc-package.patch b/debian/patches/0003-Use-old-doc-package.patch
new file mode 100644
index 000..87b12c4
--- /dev/null
+++ b/debian/patches/0003-Use-old-doc-package.patch
@@ -0,0 +1,22 @@
+From: Jochen Sprickerhof
+Date: Thu, 23 Feb 2023 13:53:01 +0100
+Subject: Use old doc package
+
+Closes: #1029439
+---
+ feynmf.dtx | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/feynmf.dtx b/feynmf.dtx
+index 4ed5c70..890579f 100644
+--- a/feynmf.dtx
b/feynmf.dtx
+@@ -7695,7 +7695,7 @@ endinput;
+ %<*driver>
+ %<*!209>
+ \documentclass[a4paper]{article}
+-\usepackage{doc}
++\usepackage{doc-2021-06-01}
+ \usepackage[T1]{fontenc}
+ %\end{macrocode}
+ % The \MF{} and \MP{} logos come out much nicer if you have |mflogo|
diff --git a/debian/patches/series b/debian/patches/series
index c6bf829..e3220cd 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,2 +1,3 @@
reproducible-build.patch
docu.patch
+0003-Use-old-doc-package.patch
--
2.39.2
signature.asc
Description: PGP signature
Bug#1029439: feynmf: FTBFS in bookworm (I can't open file `fmfsamp4')
On Wed, 22 Feb 2023 at 22:51, Hilmar Preuße wrote: > > On 2/21/23 22:00, James Addison wrote: > Sorry, I'm not of any help here. At the first glance we look at a syntax > error in the feynmf.dtx file however I'm wondering why this did not pop > within the last > 25 years. That's OK - taking a look is already a help. With some assistance from the snapshot.debian.org archives, it seems that these errors began appearing fairly recently: pass: texlive-base (2022.20220605-1) unstable; urgency=low fail: texlive-base (2022.20220923-2) unstable; urgency=medium It should be possible to look at the differences between those (and maybe the related packages such as texlive-latex-base) to find further clues. I'm going to start on that fairly soon.
Processed: Re: xmms2: do not release with bookworm
Processing control commands: > severity -1 normal Bug #1005902 [src:xmms2] xmms2: do not release with bookworm Severity set to 'normal' from 'serious' > retitle -1 xmms2: Update to latest xmms2-devel version Bug #1005902 [src:xmms2] xmms2: do not release with bookworm Changed Bug title to 'xmms2: Update to latest xmms2-devel version' from 'xmms2: do not release with bookworm'. -- 1005902: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005902 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1005902: xmms2: do not release with bookworm
Control: severity -1 normal Control: retitle -1 xmms2: Update to latest xmms2-devel version The pkg will not be part of bookworm because it failed to migrate before the freeze.
Bug#1031231: marked as done (tries to overwrite /etc/cron.yearly/.placeholder from systemd-cron)
Your message dated Thu, 23 Feb 2023 11:34:04 + with message-id and subject line Bug#1031231: fixed in cron 3.0pl1-161 has caused the Debian Bug report #1031231, regarding tries to overwrite /etc/cron.yearly/.placeholder from systemd-cron 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.) -- 1031231: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031231 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cron-daemon-common Version: 3.0pl1-159 Severity: serious Hi, cron-daemon-common can't be upgraded if systemd-cron is also installed: Preparing to unpack .../cron-daemon-common_3.0pl1-159_all.deb ... Unpacking cron-daemon-common (3.0pl1-159) over (3.0pl1-156) ... dpkg: error processing archive /var/cache/apt/archives/cron-daemon-common_3.0pl1-159_all.deb (--unpack): trying to overwrite '/etc/cron.yearly/.placeholder', which is also in package systemd-cron 1.15.19-4 Errors were encountered while processing: /var/cache/apt/archives/cron-daemon-common_3.0pl1-159_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) AFAICS this hasn't been fixed in the already uploaded but not yet avaible 3.0pl1-160 --- End Message --- --- Begin Message --- Source: cron Source-Version: 3.0pl1-161 Done: Georges Khaznadar We believe that the bug you reported is fixed in the latest version of cron, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1031...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Georges Khaznadar (supplier of updated cron 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, 23 Feb 2023 12:10:17 +0100 Source: cron Architecture: source Version: 3.0pl1-161 Distribution: unstable Urgency: medium Maintainer: Javier Fernández-Sanguino Peña Changed-By: Georges Khaznadar Closes: 1031231 Changes: cron (3.0pl1-161) unstable; urgency=medium . * added "Breaks: systemd-cron(<<1.15.19-5~)"; Closes: #1031231 Checksums-Sha1: 5202be41a6e7b1c9bd8d72b6468fb722534b504c 2129 cron_3.0pl1-161.dsc d123008480e124295114d77fd385cc93f567e126 115020 cron_3.0pl1-161.debian.tar.xz 6f184aa306ac3917a5aa44cad5b86bf173cef1d1 6224 cron_3.0pl1-161_source.buildinfo Checksums-Sha256: 840314a191153625801823f24604d47a7202c5cb83f62d4b8ba7007e0a700664 2129 cron_3.0pl1-161.dsc 481300db1336506e4d08820279b01779a34833f588a7879a0e06b63eadd1b6cd 115020 cron_3.0pl1-161.debian.tar.xz 1ce8f6453d6e2d81d350d27d3809c5096e51d00d41f27e423f2efaf464da3e4d 6224 cron_3.0pl1-161_source.buildinfo Files: a1ad6bb3327bc8665909d98ac3f848f2 2129 admin important cron_3.0pl1-161.dsc 509be450a49c4bb3e9440a6972c3f7e8 115020 admin important cron_3.0pl1-161.debian.tar.xz bb817e9440e05f6eef14b0d29d3ffe9e 6224 admin important cron_3.0pl1-161_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCAAyFiEEM0CzZP9nFT+3zK6FHCgWkHE2rjkFAmP3SgYUHGdlb3JnZXNr QGRlYmlhbi5vcmcACgkQHCgWkHE2rjmWvA/9H0fWXSf4AupDu+wAuVMMueddiL7o aqXJL1SXDrw/pFmRhDmrm2tgMTNxrhSTSxXwuv2ZfmO4GLCCMNM+8Q8Vmh8sPkd2 sSA8Tms7pNSkmAgnDggSRiahr4XvJTWfmkJmEntX4uQe+aUbtzwRqvXQ9oZ9gRJo WZBkiqKX+/M43oRX3ZmuL18ZvmBMnPi9RfcTFXYT5jEqHAoSf3MKFdvN7xU+F5RU 3mAn9E6qNakV0lQ4+CEXLvaIkAXnXZcWix+8evwcJB8xyYlGwIdlshgFrJRmmMHe wsZ/Nf4D4ZXbHA8g0eo7JtsiPmZtlDg9BQvMqmoFM8VNZlyjb3CBHf7Ul5Rtlq9w JBD81DCwBp8Q0weYN7HZS0QPfYRWp+LYb+Li0sI7eBhKJ1aHj0WH/Hj2X4L2O/sZ Ok3Jksgm8NeUNEJ/sOKoSsfajtx33ISZ1E0D0uV1Id9UFLqWtXcotm2IIAXvU7BY tM+LU+ISCIQBm55Ja59ejwiK5Mkt/1p/5oVhfdlRb3MPok9C3rDLhkZDh9DlC8Wl 7m7YNn0ekGo9zLIICkumLlptNGfg3PVsvyKCn589o5TVlw1UHpj5KCbdSKUW6Fvr VCPhd74ZzqHBg9ylloa3C4FEZINS4pYbJgRLOzf5IZohbmNsvlihTr/fWUzlJ5HD 7PFxqP/Wuyhy5WI= =3m9O -END PGP SIGNATURE End Message ---
Processed: Bug#1026728 marked as pending in cssutils
Processing control commands:
> tag -1 pending
Bug #1026728 [src:cssutils] cssutils: FTBFS: dh_auto_test: error: pybuild
--test --test-pytest -i python{version} -p "3.11 3.10" returned exit code 13
Added tag(s) pending.
--
1026728: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026728
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1026728: marked as pending in cssutils
Control: tag -1 pending Hello, Bug #1026728 in cssutils reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/cssutils/-/commit/8b4f540c323c26eabd57e8fbb003a68936159155 Apply upstream patch for 2to3 conversion Closes: #1026728 Signed-off-by: Benjamin Drung (this message was generated automatically) -- Greetings https://bugs.debian.org/1026728
Bug#1031812: crystal missing several dependencies
Package: crystal
Version: 1.6.0+dfsg-2
Severity: serious
Hi!
On a fresh unstable install, installing crystal and trying to compile a
program with it fails due to dependency issues:
$ crystal hello.cr --: 1: cc: not found
Error: execution of command failed with code: 127: `cc "${@}" -o
/root/.cache/crystal/crystal-run-hello.tmp -rdynamic
-L/usr/bin/../lib/crystal -lm -lgc -lpthread -levent -lrt -lpthread -ldl`
After installing the 'gcc' package, the error turns to
$ crystal hello.cr
/usr/bin/ld: cannot find -levent (this usually means you need to install
the development package for libevent): No such file or directory
collect2: error: ld returned 1 exit status
Error: execution of command failed with code: 1: `cc "${@}" -o
/root/.cache/crystal/crystal-run-hello.tmp -rdynamic
-L/usr/bin/../lib/crystal -lm -lgc -lpthread -levent -lrt -lpthread -ldl`
Only after also installing the 'libevent-dev' package it starts to work:
$ crystal hello.cr Hello World!
I am setting this as 'serious' as a violation of policy §3.5.
thanks,
Taavi
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-3-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages crystal depends on:
ii libc6 2.36-8
ii libevent-2.1-72.1.12-stable-5+b1
ii libgc-dev 1:8.2.2-3
ii libgc11:8.2.2-3
ii libgcc-s1 12.2.0-14
ii libllvm14 1:14.0.6-10+b1
ii libpcre3 2:8.39-15
ii libstdc++612.2.0-14
ii pkg-config1.8.1-1
ii pkgconf [pkg-config] 1.8.1-1
crystal recommends no packages.
Versions of packages crystal suggests:
pn crystal-doc
pn crystal-samples
-- no debconf information
OpenPGP_0xEF242F709F912FBE.asc
Description: OpenPGP public key
OpenPGP_signature
Description: OpenPGP digital signature
Bug#983719: esptool: Version 3.0 fixes critical bugs
On Tue, Feb 21, 2023 at 02:16:40PM +0200, Faidon Liambotis wrote: > I should note that while the package seems to meet the criteria for > Salvaging (DevRef 5.12) I don't currently have the bandwidth to maintain > it properly in the long run either. I'm happy to do a one-off NMU to > bring it to a more decent shape, however. Update: I pushed a branch into the main repo, feature/2.8-update, that just brings up the packaging to modern standards and switches to using pybuild -- a step necessary given new upstream releases are now using Python modules etc. This is still tagged as a 2.8+dfsg-1.1 release that builds the package as-is with enhancements and no regressions. I also have changes underway for 4.5, but currently looking into what it would take dependency-wise to accomplish this, as there are 1-2 new Python module dependencies that are not present in Debian yet. I'll follow up once I have something; I expect this to be in the next week or so. Regards, Faidon
Bug#1031716: python3-protobuf: Do reverse dependencies need stricter version constraints?
Hello,
On Tue, 21 Feb 2023 20:15:12 +0100
=?UTF-8?B?TMOhc3psw7MgQsO2c3rDtnJtw6lueWkgKEdDUyk=?= wrote:
On Tue, Feb 21, 2023 at 1:27 PM Adrian Bunk wrote:
> Looking at #1028371, should generated dependencies on python3-protobuf be
> python3-protobuf (>= 3.21), python3-protobuf (<< 3.22)
You mean on python3-bernhard, right?
yes
> to ensure that the binary package is used with the same version
> as the protobuf-compiler used during the build?
Then what? It would become uninstallable when a new protobuf version
(3.22 next time) is uploaded and built.
this is the idea, since right now even a basic import of bernhard is just not
working
> If yes, are other language bindings also affected by this problem?
I still don't get your point. How does a language binding package
version relate to the protobuf-compiler version? I don't follow the
internals of Protobuf, but I would say it's more related to the
library soname and its provided API version.
Bernhard uses protobuf to generate a python binding code, and this code is not
working anymore when a new protobuf
version is uploaded.
The idea is to restrict the protobuf version it was built with, to make sure
the import works.
E.g. this is the current pb.py autogenerated code
# -*- coding: utf-8 -*-
# Generated by the protocol buffer compiler. DO NOT EDIT!
# source: riemann.proto
from google.protobuf import descriptor as _descriptor
from google.protobuf import message as _message
from google.protobuf import reflection as _reflection
from google.protobuf import symbol_database as _symbol_database
# @@protoc_insertion_point(imports)
_sym_db = _symbol_database.Default()
DESCRIPTOR = _descriptor.FileDescriptor(
name='riemann.proto',
package='',
syntax='proto2',
serialized_options=b'\n\021com.aphyr.riemannB\005Proto',
create_key=_descriptor._internal_create_key,
serialized_pb=b'\n\rriemann.proto\"\x81\x01\n\x05State\x12\x0c\n\x04time\x18\x01
\x01(\x03\x12\r\n\x05state\x18\x02 \x01(\t\x12\x0f\n\x07service\x18\x03
\x01(\t\x12\x0c\n\x04host\x18\x04 \x01(\t\x12\x13\n\x0b\x64\x65scription\x18\x05
\x01(\t\x12\x0c\n\x04once\x18\x06 \x01(\x08\x12\x0c\n\x04tags\x18\x07 \x03(\t\x12\x0b\n\x03ttl\x18\x08
\x01(\x02\"\xce\x01\n\x05\x45vent\x12\x0c\n\x04time\x18\x01 \x01(\x03\x12\r\n\x05state\x18\x02
\x01(\t\x12\x0f\n\x07service\x18\x03 \x01(\t\x12\x0c\n\x04host\x18\x04
\x01(\t\x12\x13\n\x0b\x64\x65scription\x18\x05 \x01(\t\x12\x0c\n\x04tags\x18\x07
\x03(\t\x12\x0b\n\x03ttl\x18\x08 \x01(\x02\x12\x1e\n\nattributes\x18\t
\x03(\x0b\x32\n.Attribute\x12\x15\n\rmetric_sint64\x18\r \x01(\x12\x12\x10\n\x08metric_d\x18\x0e
\x01(\x01\x12\x10\n\x08metric_f\x18\x0f \x01(\x02\"\x17\n\x05Query\x12\x0e\n\x06string\x18\x01
\x01(\t\"g\n\x03Msg\x12\n\n\x02ok\x18\x02 \x01(\x08\x12\r\n\x05\x65rror\x18\x03
\x01(\t\x12\x16\n\x06states\x18\x04 \x03(\x0b\x32\x06.State\x12\x15\n\x05query\x18\x05
\x01(\x0b\x32\x06.Query\x12\x16\n\x06\x65vents\x18\x06
\x03(\x0b\x32\x06.Event\"\'\n\tAttribute\x12\x0b\n\x03key\x18\x01 \x02(\t\x12\r\n\x05value\x18\x02
\x01(\tB\x1a\n\x11\x63om.aphyr.riemannB\x05Proto'
)
_STATE = _descriptor.Descriptor(
name='State',
full_name='State',
filename=None,
file=DESCRIPTOR,
containing_type=None,
create_key=_descriptor._internal_create_key,
fields=[
_descriptor.FieldDescriptor(
name='time', full_name='State.time', index=0,
number=1, type=3, cpp_type=2, label=1,
has_default_value=False, default_value=0,
message_type=None, enum_type=None, containing_type=None,
is_extension=False, extension_scope=None,
serialized_options=None, file=DESCRIPTOR,
create_key=_descriptor._internal_create_key),
_descriptor.FieldDescriptor(
name='state', full_name='State.state', index=1,
number=2, type=9, cpp_type=9, label=1,
has_default_value=False, default_value=b"".decode('utf-8'),
message_type=None, enum_type=None, containing_type=None,
is_extension=False, extension_scope=None,
serialized_options=None, file=DESCRIPTOR,
create_key=_descriptor._internal_create_key),
_descriptor.FieldDescriptor(
name='service', full_name='State.service', index=2,
number=3, type=9, cpp_type=9, label=1,
has_default_value=False, default_value=b"".decode('utf-8'),
message_type=None, enum_type=None, containing_type=None,
is_extension=False, extension_scope=None,
serialized_options=None, file=DESCRIPTOR,
create_key=_descriptor._internal_create_key),
_descriptor.FieldDescriptor(
name='host', full_name='State.host', index=3,
number=4, type=9, cpp_type=9, label=1,
has_default_value=False, default_value=b"".decode('utf-8'),
message_type=None, enum_type=None, containing_type=None,
is_extension=False, extension_scope=None,
serialized_options=None, file=DESCRIPTOR,
create_key=_descriptor._internal_create_key),
_descriptor.FieldDescriptor(
name='description', full_name='State.description', index=4,
Bug#1031758: marked as done (autopkg tests broken with python3.11 (timeout))
Your message dated Thu, 23 Feb 2023 09:20:40 +0100 with message-id <49da64fa-f5be-3b05-3f05-ae29e2475...@debian.org> and subject line Duplicate bug filled against the wrong version of the package has caused the Debian Bug report #1031758, regarding autopkg tests broken with python3.11 (timeout) 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.) -- 1031758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031758 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-oslo.db Version: 12.1.0-3 Severity: serious Tags: sid bullseye the autopkg tests fail with a timeout, please see https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-oslo.db/31558294/log.gz --- End Message --- --- Begin Message --- Hi, The log shows this: PYTHON=python3.11 stestr run --parallel --subunit oslo_db\.tests.* when version 12.1.0-3 has: pkgos-dh_auto_test --no-py2 'oslo_db\.tests\.(?!.*test_enginefacade.*)' This means the bug was filled against 12.1.0-3 when it should have been against 12.1.0-2, and really, it's a duplicate of #1031481 that was fixed a few hours before this bug was filled. I'm therefore closing this bug without any further action. Cheers, Thomas Goirand (zigo)--- End Message ---
Bug#1030658: marked as done (fail to retrieve docset info: TLS initialization failed (caused by unresolved OpenSSL symbols))
Your message dated Thu, 23 Feb 2023 09:10:20 +0100 with message-id and subject line Re: More info needed on the RC bug you opened has caused the Debian Bug report #1030658, regarding fail to retrieve docset info: TLS initialization failed (caused by unresolved OpenSSL symbols) 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.) -- 1030658: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030658 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: zeal Version: 1:0.6.1+git20220714+6fee23-2 Severity: grave This problem makes it impossible to download docsets and start using Zeal, thus the severity. I observe this error since months, so it is not related to a recent change in some other package. Sorry for not reporting it earlier. Trying to retrieve docsets fails with: Download failed! Error: TLS initialization failed URL: https://api.zealdocs.org/v1/docsets [Cancel][Retry] The console contains the following: qt.network.ssl: QSslSocket: cannot resolve OPENSSL_init_ssl qt.network.ssl: QSslSocket: cannot resolve OPENSSL_init_crypto qt.network.ssl: QSslSocket: cannot resolve ASN1_STRING_get0_data qt.network.ssl: QSslSocket: cannot resolve EVP_CIPHER_CTX_reset qt.network.ssl: QSslSocket: cannot resolve EVP_PKEY_up_ref qt.network.ssl: QSslSocket: cannot resolve EVP_PKEY_CTX_new qt.network.ssl: QSslSocket: cannot resolve EVP_PKEY_param_check qt.network.ssl: QSslSocket: cannot resolve EVP_PKEY_CTX_free qt.network.ssl: QSslSocket: cannot resolve RSA_bits qt.network.ssl: QSslSocket: cannot resolve OPENSSL_sk_new_null qt.network.ssl: QSslSocket: cannot resolve OPENSSL_sk_push qt.network.ssl: QSslSocket: cannot resolve OPENSSL_sk_free qt.network.ssl: QSslSocket: cannot resolve OPENSSL_sk_num qt.network.ssl: QSslSocket: cannot resolve OPENSSL_sk_pop_free qt.network.ssl: QSslSocket: cannot resolve OPENSSL_sk_value qt.network.ssl: QSslSocket: cannot resolve DH_get0_pqg qt.network.ssl: QSslSocket: cannot resolve SSL_CTX_set_options qt.network.ssl: QSslSocket: cannot resolve SSL_CTX_get_security_level qt.network.ssl: QSslSocket: cannot resolve SSL_CTX_set_security_level qt.network.ssl: QSslSocket: cannot resolve SSL_CTX_set_ciphersuites qt.network.ssl: QSslSocket: cannot resolve SSL_set_psk_use_session_callback qt.network.ssl: QSslSocket: cannot resolve SSL_SESSION_is_resumable qt.network.ssl: QSslSocket: cannot resolve SSL_get_client_random qt.network.ssl: QSslSocket: cannot resolve SSL_SESSION_get_master_key qt.network.ssl: QSslSocket: cannot resolve SSL_session_reused qt.network.ssl: QSslSocket: cannot resolve SSL_set_options qt.network.ssl: QSslSocket: cannot resolve TLS_method qt.network.ssl: QSslSocket: cannot resolve TLS_client_method qt.network.ssl: QSslSocket: cannot resolve TLS_server_method qt.network.ssl: QSslSocket: cannot resolve X509_up_ref qt.network.ssl: QSslSocket: cannot resolve X509_STORE_CTX_get0_chain qt.network.ssl: QSslSocket: cannot resolve X509_getm_notBefore qt.network.ssl: QSslSocket: cannot resolve X509_getm_notAfter qt.network.ssl: QSslSocket: cannot resolve X509_get_version qt.network.ssl: QSslSocket: cannot resolve X509_STORE_set_verify_cb qt.network.ssl: QSslSocket: cannot resolve X509_STORE_set_ex_data qt.network.ssl: QSslSocket: cannot resolve X509_STORE_get_ex_data qt.network.ssl: QSslSocket: cannot resolve OpenSSL_version_num qt.network.ssl: QSslSocket: cannot resolve OpenSSL_version qt.network.ssl: Incompatible version of OpenSSL qt.network.ssl: QSslSocket: cannot call unresolved function d2i_X509 (repeats numerous times) qt.network.ssl: QSslSocket::connectToHostEncrypted: TLS initialization failed Rebuilding the package using current unstable didn't help. -- Damyan -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=bg_BG.UTF-8, LC_CTYPE=bg_BG.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages zeal depends on: ii libarchive13 3.6.2-1 ii libc62.36-8 ii libgcc-s112.2.0-14 ii libqt5concurrent55.15.8+dfsg-2 ii libqt5core5a 5.15.8+dfsg-2 ii libqt5gui5 5.15.8+dfsg-2 ii libqt5network5 5.15.8+dfsg-2 ii libqt5sql5-sqlite5.15.8+dfsg-2 ii libqt5webchannel5
Bug#1029731: libglapi-mesa: Apps fail with 'DRM_IOCTL_MODE_CREATE_DUMB failed: Cannot allocate memory' after upgrade from 22.3.2-1 to 22.3.3-1
On Thursday, 23 February 2023 04:44:16 CET Stuart Young wrote: > Just a note that it looks like this patch got picked up in the 22.3.6 > release that just went out. That's good to know, thanks. But I don't know if at this stage in the Freeze new upstream releases are still allowed. I'm pretty confident that targeted fixes are and therefor I attached the patch. If 22.3.6 is allowed, that would be better I presume. signature.asc Description: This is a digitally signed message part.
