Bug#1008508: borgbackup: Uninstallable in Debian Unstable due dependency on python 3 < 3.10
Hi, Axel Beckert wrote: > borgbackup became uninstallable in Debian Unstable due a dependency on > python3 < 3.10 while Python 3.10 has landed in Unstable yesterday. Ah, I just saw https://release.debian.org/transitions/html/python3.10-default.html so I assume this can be fixed with a BinNMU which probably will be done by the release team. Sorry for the noise. Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Bug#1008508: borgbackup: Uninstallable in Debian Unstable due dependency on python 3 < 3.10
Package: borgbackup Version: 1.2.0-1 Severity: serious Hi, borgbackup became uninstallable in Debian Unstable due a dependency on python3 < 3.10 while Python 3.10 has landed in Unstable yesterday. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (990, 'unstable'), (980, 'unstable-debug'), (600, 'testing'), (111, 'buildd-unstable'), (111, 'buildd-experimental'), (110, 'experimental'), (105, 'experimental-debug') Architecture: amd64 (x86_64) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages borgbackup depends on: ii libacl12.3.1-1 ii libc6 2.33-7 ii liblz4-1 1.9.3-2 ii libssl1.1 1.1.1n-1 ii libxxhash0 0.8.1-1 ii libzstd1 1.4.9+dfsg-1 ii python33.9.8-1 ii python3-msgpack1.0.3-1 ii python3-packaging 21.3-1 ii python3-pkg-resources 59.6.0-1.2 Versions of packages borgbackup recommends: ii fuse3 [fuse] 3.10.5-1 ii python3-llfuse 1.4.1+dfsg-2 pn python3-pyfuse3 Versions of packages borgbackup suggests: pn borgbackup-doc -- no debconf information
Processed: Bug#1005438 marked as pending in pygame
Processing control commands:
> tag -1 pending
Bug #1005438 {Done: Scott Talbert } [src:pygame] pygame:
FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9"
--system=custom --test-args "/usr/bin/xvfb-run {interpreter} -m
pygame.tests.__main__ --exclude opengl" returned exit code 13
Added tag(s) pending.
--
1005438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005438
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1005438: marked as pending in pygame
Control: tag -1 pending Hello, Bug #1005438 in pygame 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/pygame/-/commit/ee23ea00fa9caedf8f3916e146cc3869785afda8 Update to new upstream release 2.1.2 (Closes: #973352, #1005438) (this message was generated automatically) -- Greetings https://bugs.debian.org/1005438
Bug#1005438: marked as done (pygame: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" --system=custom --test-args "/usr/bin/xvfb-run {interpreter} -m pygame.tests.__main__ -
Your message dated Mon, 28 Mar 2022 03:18:45 +
with message-id
and subject line Bug#1005438: fixed in pygame 2.1.2+dfsg-1
has caused the Debian Bug report #1005438,
regarding pygame: FTBFS: dh_auto_test: error: pybuild --test -i python{version}
-p "3.10 3.9" --system=custom --test-args "/usr/bin/xvfb-run {interpreter} -m
pygame.tests.__main__ --exclude opengl" 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.)
--
1005438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005438
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pygame
Version: 1.9.6+dfsg-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220212 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 '/<>'
> # Removed from +dfsg, but tests need it:
> ln -fs /usr/share/fonts/truetype/dejavu/DejaVuSans.ttf
> test/fixtures/fonts/test_sans.ttf
> # buildds don't provide graphical interfaces or audio/video devices
> # to test with, hence some tests won't work properly without:
> SDL_VIDEODRIVER=dummy SDL_AUDIODRIVER=disk LC_ALL=C.UTF-8 \
> dh_auto_test -- --system=custom --test-args \
> '/usr/bin/xvfb-run {interpreter} -m pygame.tests.__main__ --exclude
> opengl'
> I: pybuild pybuild:298: cp /<>/src_py/pygame_icon.bmp
> /<>/.pybuild/cpython3_3.10_pygame/build/pygame; cp
> /usr/share/fonts/truetype/freefont/FreeSansBold.ttf
> /<>/.pybuild/cpython3_3.10_pygame/build/pygame/freesansbold.ttf;
> ln -sf /<>/examples/data
> /<>/.pybuild/cpython3_3.10_pygame/build/pygame/examples; ln -sf
> /<>/test/fixtures
> /<>/.pybuild/cpython3_3.10_pygame/build/pygame/tests/
> I: pybuild base:237: /usr/bin/xvfb-run python3.10 -m pygame.tests.__main__
> --exclude opengl
> /<>/.pybuild/cpython3_3.10_pygame/build/pygame/tests/test_utils/__init__.py:178:
> SyntaxWarning: "is not" with a literal. Did you mean "!="?
> (rect.left is not 0 and [(rect.left-1, rect.top)] or []) +
> WARNING: You are using the SDL disk writer audio driver!
> Writing to file [sdlaudio.raw].
> WARNING: You are using the SDL disk writer audio driver!
> Writing to file [sdlaudio.raw].
> WARNING: You are using the SDL disk writer audio driver!
> Writing to file [sdlaudio.raw].
> WARNING: You are using the SDL disk writer audio driver!
> Writing to file [sdlaudio.raw].
> WARNING: You are using the SDL disk writer audio driver!
> Writing to file [sdlaudio.raw].
> WARNING: You are using the SDL disk writer audio driver!
> Writing to file [sdlaudio.raw].
> Segmentation fault
> E: pybuild pybuild:367: test: plugin custom failed with: exit code=139:
> /usr/bin/xvfb-run python3.10 -m pygame.tests.__main__ --exclude opengl
> I: pybuild pybuild:298: cp /<>/src_py/pygame_icon.bmp
> /<>/.pybuild/cpython3_3.9_pygame/build/pygame; cp
> /usr/share/fonts/truetype/freefont/FreeSansBold.ttf
> /<>/.pybuild/cpython3_3.9_pygame/build/pygame/freesansbold.ttf;
> ln -sf /<>/examples/data
> /<>/.pybuild/cpython3_3.9_pygame/build/pygame/examples; ln -sf
> /<>/test/fixtures
> /<>/.pybuild/cpython3_3.9_pygame/build/pygame/tests/
> I: pybuild base:237: /usr/bin/xvfb-run python3.9 -m pygame.tests.__main__
> --exclude opengl
> /<>/.pybuild/cpython3_3.9_pygame/build/pygame/tests/test_utils/__init__.py:178:
> SyntaxWarning: "is not" with a literal. Did you mean "!="?
> (rect.left is not 0 and [(rect.left-1, rect.top)] or []) +
> WARNING: You are using the SDL disk writer audio driver!
> Writing to file [sdlaudio.raw].
> WARNING: You are using the SDL disk writer audio driver!
> Writing to file [sdlaudio.raw].
> WARNING: You are using the SDL disk writer audio driver!
> Writing to file [sdlaudio.raw].
> WARNING: You are using the SDL disk writer audio driver!
> Writing to file [sdlaudio.raw].
> WARNING: You are using the SDL disk writer audio driver!
> Writing to file [sdlaudio.raw].
> WARNING: You are using the SDL disk writer audio driver!
> Writing to file [sdlaudio.raw].
> Segmentation fault
> E: pybuild pybuild:367: test: plugin custom failed with: exit code=139:
> /usr/bin/xvfb-run python3.9 -m pygame.tests.__main__ --exclude opengl
> dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9"
> --system=custom --test-args "/usr/bin/xvfb-run {interpreter} -m
> pygame.tests.__main__ --exclude opengl" returned exit code 13
The full build log is available from:
http://qa-logs.debian.net/2022/02/12/pygame_1.9.6+dfsg-5_unstable.log
A list of current common
Bug#1008343: marked as done (snek: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity)
Your message dated Sun, 27 Mar 2022 18:03:01 -0700 with message-id <87r16mc2ii@keithp.com> and subject line Re: Bug#1008343: snek: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity has caused the Debian Bug report #1008343, regarding snek: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity 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.) -- 1008343: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008343 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: snek Version: 1.7-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220326 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<>/doc/lessons/lesson-5' > echo 'nothing in lesson 5 yet' > nothing in lesson 5 yet > make[3]: Leaving directory '/<>/doc/lessons/lesson-5' > make[2]: Leaving directory '/<>/doc' > make[2]: Entering directory '/<>/examples' > echo all done > all done > make[2]: Leaving directory '/<>/examples' > cd test && make check > make[2]: Entering directory '/<>/test' > Running test pass-andor.py. > pass python3 > pass snek > Welcome to snek 1.7 > E: Build killed with signal TERM after 150 minutes of inactivity The full build log is available from: http://qa-logs.debian.net/2022/03/26/snek_1.7-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Lucas Nussbaum writes: Version: 1.8-1 This was caused by an update to picolibc; snek has been updated to adapt to that change. Thanks for your report -- -keith signature.asc Description: PGP signature --- End Message ---
Processed: Bug#1008478 in package dpkg marked as pending
Processing control commands: > tag 1008478 pending Bug #1008478 [dpkg] dpkg-fsys-usrunmess depends on umask 022 Added tag(s) pending. -- 1008478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008478 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1008478: in package dpkg marked as pending
Control: tag 1008478 pending Hi! Bug #1008478 in package dpkg reported by you has been fixed in the dpkg/dpkg.git Git repository. You can see the changelog below, and you can check the diff of the fix at: https://git.dpkg.org/cgit/dpkg/dpkg.git/diff/?id=77756084e --- dpkg-fsys-usrunmess: Explicitly set user/group and mode for created dirs We should explicitly set the user/group and mode for the newly created directories, to make sure they end up with the expected values, instead of assuming a good environment (umask and user/group). We will still be setting a known umask in a subsequent commit as a defensive measure. Closes: #1008478
Processed: Re: Bug#1008382: meson 0.62 regression: gtk-doc targets in src:glib2.0 lose their dependencies
Processing control commands: > reassign -1 meson 0.62.0-1 Bug #1008382 [src:glib2.0] glib2.0: FTBFS: ld: cannot find -lgdbus-example-objectmanager: No such file or directory Bug reassigned from package 'src:glib2.0' to 'meson'. No longer marked as found in versions glib2.0/2.72.0-1. Ignoring request to alter fixed versions of bug #1008382 to the same values previously set Bug #1008382 [meson] glib2.0: FTBFS: ld: cannot find -lgdbus-example-objectmanager: No such file or directory Marked as found in versions meson/0.62.0-1. > retitle -1 meson 0.62 regression: gtk-doc targets in src:glib2.0 lose their > dependencies Bug #1008382 [meson] glib2.0: FTBFS: ld: cannot find -lgdbus-example-objectmanager: No such file or directory Changed Bug title to 'meson 0.62 regression: gtk-doc targets in src:glib2.0 lose their dependencies' from 'glib2.0: FTBFS: ld: cannot find -lgdbus-example-objectmanager: No such file or directory'. > affects -1 + src:glib2.0 Bug #1008382 [meson] meson 0.62 regression: gtk-doc targets in src:glib2.0 lose their dependencies Added indication that 1008382 affects src:glib2.0 -- 1008382: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008382 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1008382: meson 0.62 regression: gtk-doc targets in src:glib2.0 lose their dependencies
Control: reassign -1 meson 0.62.0-1 Control: retitle -1 meson 0.62 regression: gtk-doc targets in src:glib2.0 lose their dependencies Control: affects -1 + src:glib2.0 On Sat, 26 Mar 2022 at 21:44:54 +0100, Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build > on amd64. > > > [473/1344] /usr/bin/meson --internal gtkdoc --sourcedir=/<> > > --builddir=/<>/debian/build/deb > > --subdir=docs/reference/gio/gdbus-object-manager-example > > --headerdirs=gio/tests/gdbus-object-manager-example > > --mainfile=gdbus-object-manager-example-docs.xml > > --modulename=gdbus-object-manager-example --moduleversion= --mode=auto > > --gtkdoc-scan=/usr/bin/gtkdoc-scan > > --gtkdoc-scangobj=/usr/bin/gtkdoc-scangobj > > --gtkdoc-mkdb=/usr/bin/gtkdoc-mkdb --gtkdoc-mkhtml=/usr/bin/gtkdoc-mkhtml > > --gtkdoc-fixxref=/usr/bin/gtkdoc-fixxref --namespace=example --htmlargs= > >
Bug#1008502: vdirsyncer: Unknown error occured: unmatched ')'
Package: vdirsyncer Version: 0.16.8-2 Severity: grave Justification: renders package unusable Dear Maintainer, Running vdirsyncer sync causes the above error message about unmatched ')'. This renders 0.4.4 - the version in stable - unusable. The root cause is that python-click-threading 0.4.4, which vdirsyncer is depending on, introduced an incompatibility with python-click. More info on the problem can be found in [2] and [3]. The version in testing (0.18.0-6) is working fine as it depends on a python-click-version that does not have the problem. So installing the version from testing including its dependencies works. Would you please upgrade vdirsyncer in stable to the current version in testing to make the program work again for everyone on stable? Cheers, Christof [1] https://github.com/pimutils/vdirsyncer/pull/891 [2] https://github.com/click-contrib/click-threading/pull/5 [3] https://github.com/pimutils/vdirsyncer/issues/887 -- System Information: Debian Release: 11.3 APT prefers stable APT policy: (990, 'stable'), (400, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-10-amd64 (SMP w/4 CPU threads) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to de_DE.UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages vdirsyncer depends on: ii init-system-helpers1.60 ii python33.9.2-3 ii python3-atomicwrites 1.4.0-2 ii python3-click 7.1.2-1 ii python3-click-log 0.2.1-2 ii python3-click-threading0.4.4-2 ii python3-requests 2.25.1+dfsg-2 ii python3-requests-toolbelt 0.9.1-1 vdirsyncer recommends no packages. Versions of packages vdirsyncer suggests: pn python3-requests-oauthlib pn vdirsyncer-doc -- no debconf information
Processed: Re: Bug#1008316: dpkg-fsys-usrunmess breaks system boot
Processing control commands: > retitle -1 dpkg-fsys-usrunmess: Does not deal with untracked kernel modules Bug #1008316 [dpkg] dpkg-fsys-usrunmess breaks system boot Changed Bug title to 'dpkg-fsys-usrunmess: Does not deal with untracked kernel modules' from 'dpkg-fsys-usrunmess breaks system boot'. -- 1008316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008316 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1008316: dpkg-fsys-usrunmess breaks system boot
Control: retitle -1 dpkg-fsys-usrunmess: Does not deal with untracked kernel modules Hi! On Sat, 2022-03-26 at 19:21:44 +0100, Eric Valette wrote: > Package: dpkg > Version: 1.21.4 > Severity: critical > Justification: breaks the whole system > Gobally the scripts does a very good job but it missed to copy > /usr/lib/modules to > /lib/modules on a self generated kernel that has modules build via dkms and a > few native kernel modules. I assume the custom built kernel was installed w/o a .deb package? > Invoquing the dkms postinstall script fails because it does not find > /lib/modules/x.y.z > directories and rebooting without graphic drivers and other stff does not > work. Just to understand, did dpkg-fsys-usrunmess fail (exited non-zero) while configuring packages (with dkms)? And then you rebooted? If so, I guess the error message should be more clear that the system has many chances of not being in a bootable state. And perhaps add some instructions on how to proceed or similar. And it should ideally be restartable (as already requested in another report), which I guess I'll be working on next. > So you probably should copy /usr/lib/modules to /lib/modules before the > calling the > postinstall. Hmm, right, because these were not tracked, they got missed in the migration. I've checked the Debian archive and at least there, it does not look like anything else besides kernel modules are being current shipped in those directories (via apt-file), but the problem is that I've seen references in source code (via codesearch.d.o) to /usr/lib/modules, for at least apache and python modules, so I don't think an unconditional move for untracked files would be safe there. I'm thinking the following special-case options (in order of decreasing preference): * move only untracked «/usr/lib/modules/[0-9]*» expecting/assuming those to be kernel modules, * copy (not move) all untracked files from «/usr/lib/modules/*» to «/lib/modules», and print a message at the end, but that will leave cruft behind if not cleaned up, * record them, and print a list at the end of the execution for the user to deal with, but that can be rather unfriendly, and that can include usual dkms built modules too, > To fix i did: >1) boot in recovery mode, >2) copy /usr/lib/modules to /lib/modules >3) dkms autoinstall >4) update-grub > > and it wworked. I guess depending on whether the program failed or not that might change what the better approach might be. Thanks, Guillem
Processed: bugs metadata
Processing commands for cont...@bugs.debian.org: > found 1008316 1.20.6 Bug #1008316 [dpkg] dpkg-fsys-usrunmess breaks system boot Marked as found in versions dpkg/1.20.6. > found 1008478 1.20.6 Bug #1008478 [dpkg] dpkg-fsys-usrunmess depends on umask 022 Marked as found in versions dpkg/1.20.6. > severity 986644 wishlist Bug #986644 [dpkg] dpkg-divert: document how to use with --no-rename Severity set to 'wishlist' from 'important' > severity 983072 wishlist Bug #983072 [dpkg] dpkg: Vendor Hooks - add ability to update build profiles Severity set to 'wishlist' from 'normal' > severity 985553 wishlist Bug #985553 [dpkg] dpkg: RFC use gcc .spec files for fixfilepath/fixdebugpath Severity set to 'wishlist' from 'normal' > severity 999598 wishlist Bug #999598 [dpkg-dev] dpkg-dev: Can we have binary package descriptions back for source uploads? Severity set to 'wishlist' from 'normal' > severity 996587 wishlist Bug #996587 [dpkg] Support method of waiting for release of db lock Severity set to 'wishlist' from 'normal' > severity 1008486 wishlist Bug #1008486 [dpkg] dpkg-fsys-usrunmess: should include warning that systems will be unsupported Severity set to 'wishlist' from 'serious' > severity 1008489 wishlist Bug #1008489 [dpkg] dpkg: postinst should not warn about Debian's default filesystem layout Severity set to 'wishlist' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1008316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008316 1008478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008478 1008486: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008486 1008489: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008489 983072: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983072 985553: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985553 986644: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986644 996587: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996587 999598: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999598 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1005833: [DRE-maint] Bug#1005833: src:ruby-redis: fails to migrate to testing for too long: autopkgtest regression
Quoting Paul Gevers (2022-03-21 21:13:29) > Is there any progress on this issue? Is no progress is there another way > to move the problem forward? E.g. revert ruby-redis to the previous > version if redis and fakeredis can agree on the change in behavior? I am preparing an upload of ruby-fakeredis with an upstream PR accomodating the fact that 'exists' returns now an integer, plus some modifications of the test suite. This should fix the issue. Best wishes, Cédric
Processed: severity of 1008498 is normal, reassign 1008498 to ftp.debian.org ...
Processing commands for cont...@bugs.debian.org: > severity 1008498 normal Bug #1008498 [src:hgsubversion] Should hgsubversion be removed? Severity set to 'normal' from 'serious' > reassign 1008498 ftp.debian.org Bug #1008498 [src:hgsubversion] Should hgsubversion be removed? Bug reassigned from package 'src:hgsubversion' to 'ftp.debian.org'. No longer marked as found in versions hgsubversion/1.9.3+git20190419+6a6ce-5. Ignoring request to alter fixed versions of bug #1008498 to the same values previously set > retitle 1008498 RM: -- RoM; Python 2-only, dead upstream Bug #1008498 [ftp.debian.org] Should hgsubversion be removed? Changed Bug title to 'RM: -- RoM; Python 2-only, dead upstream' from 'Should hgsubversion be removed?'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1008498: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008498 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1008498: Should hgsubversion be removed?
Hi, On Sun, 27 Mar 2022, at 23:33, Moritz Muehlenhoff wrote: > Source: hgsubversion > Version: 1.9.3+git20190419+6a6ce-5 > Severity: serious > > Your package came up as a candidate for removal from Debian: > > - Still depends on Python 2 and removed from testing since 2020 > - Dead upstream (no commits after 2019) Thanks, I fully agree. > If you disagree and want to continue to maintain this package, > please just close this bug (and fix the open issues). > > If you agree with the removal, please reassign to ftp.debian.org > by sending the following commands to cont...@bugs.debian.org: Doing so. -- Cheers, Andrej
Bug#1008500: Should undertaker be removed?
Source: undertaker Version: 1.6.1-4.2 Severity: serious Your package came up as a candidate for removal from Debian: - Still depends on Python 2 and thus removed from testing since 2019 - Last maintainer upload in 2016 If you disagree and want to continue to maintain this package, please just close this bug (and fix the open issues). If you agree with the removal, please reassign to ftp.debian.org by sending the following commands to cont...@bugs.debian.org: -- severity $BUGNUM normal reassign $BUGNUM ftp.debian.org retitle $BUGNUM RM: -- RoM; thx -- Otherwise I'll move forward and request it's removal in a month. Cheers, Moritz
Bug#1008499: Should neard be removed?
Source: neard Version: 0.16-0.1 Severity: serious Your package came up as a candidate for removal from Debian: - Last maintainer upload in 2013 - Depends on Python 2 and thus removed from testing since 2019 If you disagree and want to continue to maintain this package, please just close this bug (and fix the open issues). If you agree with the removal, please reassign to ftp.debian.org by sending the following commands to cont...@bugs.debian.org: -- severity $BUGNUM normal reassign $BUGNUM ftp.debian.org retitle $BUGNUM RM: -- RoM; thx -- Otherwise I'll move forward and request it's removal in a month. Cheers, Moritz
Bug#1008498: Should hgsubversion be removed?
Source: hgsubversion Version: 1.9.3+git20190419+6a6ce-5 Severity: serious Your package came up as a candidate for removal from Debian: - Still depends on Python 2 and removed from testing since 2020 - Dead upstream (no commits after 2019) If you disagree and want to continue to maintain this package, please just close this bug (and fix the open issues). If you agree with the removal, please reassign to ftp.debian.org by sending the following commands to cont...@bugs.debian.org: -- severity $BUGNUM normal reassign $BUGNUM ftp.debian.org retitle $BUGNUM RM: -- RoM; thx -- Otherwise I'll move forward and request it's removal in a month. Cheers, Moritz
Bug#1008497: linux-image-5.10.0-13-arm64: 5.10.0-13-arm64 gets stuck after loading ramdisk on VMWareFusion under M1. 5.10.0-12-arm64 works.
Package: src:linux Version: 5.10.106-1 Severity: critical Tags: d-i Justification: breaks the whole system Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** Brand new Mac Studio M1 Ultra Install VMWare Fusion Pro Tech Preview for ARM/M1 Download 11.3 DVD iso Install ISO. Install process completes First reboot System hangs after loading ramdisk Same procedure under Parallels Desktop 17 however works As I had an older Debian 11 running on my Laptop, I copied it over and it worked. After I did apt-get update, all started to fail. I nailed it down to the kernel version Linux kernel 5.10.0-13-arm64 #1 SMP Debian 5.10.106-1 (2022-03-17) aarch64 GNU/Linux fails Linux kernel 5.10.0-12-arm64 #1 SMP Debian 5.10.70-1 (2021-09-30) aarch64 GNU/Linux works Linux kernel 5.10.0-9-arm64 #1 SMP Debian 5.10.70-1 (2021-09-30) aarch64 GNU/Linux works -- Package-specific info: ** Kernel log: boot messages should be attached Loading Linux 5.10.0-13-arm64 ... Loading initial ramdisk ... _ ** Model information Device Tree model: linux,dummy-virt ** Network interface configuration: *** /etc/network/interfaces: source /etc/network/interfaces.d/* auto lo iface lo inet loopback allow-hotplug ens160 iface ens160 inet static address 79.134.238.12 netmask 255.255.255.128 gateway 79.134.238.1 iface ens160 inet6 static address 2a01:528:1:2::c/64 ** PCI devices: 00:00.0 Host bridge [0600]: VMware Device [15ad:1976] (rev 01) Subsystem: VMware Device [15ad:1976] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [40] Subsystem: VMware PCI bridge [15ad:0790] 00:15.0 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [40] Subsystem: VMware PCI Express Root Port [15ad:07a0] Capabilities: [48] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [50] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE- DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend- LnkCap: Port #0, Speed 5GT/s, Width x32, ASPM L0s, Exit Latency L0s <64ns ClockPM- Surprise- LLActRep+ BwNot- ASPMOptComp- LnkCtl: ASPM Disabled; RCB 64 bytes, Disabled- CommClk- ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 5GT/s (ok), Width x32 (ok) TrErr- Train- SlotClk- DLActive+ BWMgmt- ABWMgmt- SltCap: AttnBtn+ PwrCtrl+ MRL- AttnInd- PwrInd- HotPlug+ Surprise- Slot #160, PowerLimit 240.000W; Interlock- NoCompl+ SltCtl: Enable: AttnBtn+ PwrFlt- MRL- PresDet- CmdCplt- HPIrq+ LinkChg+ Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock- SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock- Changed: MRL- PresDet- LinkState- RootCap: CRSVisible- RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ CRSVisible- RootSta: PME ReqID , PMEStatus- PMEPending- DevCap2: Completion Timeout: Not Supported, TimeoutDis- NROPrPrP- LTR- 10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt- EETLPPrefix- EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit- FRS- LN System CLS Not Supported, TPHComp- ExtTPHComp- ARIFwd- AtomicOpsCap: Routing- 32bit- 64bit- 128bitCAS- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR- OBFF Disabled, ARIFwd- AtomicOpsCtl: ReqEn- EgressBlck- LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance-
Processed: tagging 997213
Processing commands for cont...@bugs.debian.org: > tags 997213 + patch Bug #997213 [src:i2p] i2p: FTBFS: [javac] /<>/apps/jetty/java/src/net/i2p/jetty/I2PRequestLog.java:25: error: package javax.servlet.http does not exist Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 997213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997213 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997213: NMU to DELAYED/5
Dear Maintainer, I have prepared a NMU of i2p fixing bugs #997213 and #986474. Please find enclosed the corresponding source debdiff. I made the upload to DELAYED/5, please feel free to ask me to cancel it if you want. Best regards, -- Pierre diff -Nru i2p-0.9.48/debian/changelog i2p-0.9.48/debian/changelog --- i2p-0.9.48/debian/changelog 2020-12-03 06:51:17.0 +0100 +++ i2p-0.9.48/debian/changelog 2022-03-27 22:11:17.0 +0200 @@ -1,3 +1,13 @@ +i2p (0.9.48-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Adding an explicit (build-)dependency on libservlet3.1-java, which was +previously provided by libnetty9-java (Closes: #997213) + * Adding an explicit dependency of i2p-router on libecj-java +(Closes: #986474) + + -- Pierre Gruet Sun, 27 Mar 2022 22:11:17 +0200 + i2p (0.9.48-1) unstable; urgency=medium * New upstream release. diff -Nru i2p-0.9.48/debian/control i2p-0.9.48/debian/control --- i2p-0.9.48/debian/control 2020-12-03 06:51:17.0 +0100 +++ i2p-0.9.48/debian/control 2022-03-27 22:09:13.0 +0200 @@ -11,6 +11,7 @@ ,debconf ,default-jdk ,libjetty9-java (>= 9.4) + ,libservlet3.1-java ,libtaglibs-standard-jstlel-java ,libtomcat9-java ,dh-apparmor @@ -76,9 +77,11 @@ openjdk-14-jre-headless | openjdk-13-jre-headless | openjdk-12-jre-headless | openjdk-11-jre-headless | default-jre-headless | java14-runtime-headless | java13-runtime-headless | java12-runtime-headless | java11-runtime-headless, geoip-database, gettext-base, + libecj-java, libgetopt-java, libjson-simple-java (>= 2),libjson-simple-java (<< 3), libjetty9-java (>= 9.4), + libservlet3.1-java, libtaglibs-standard-jstlel-java, libtomcat9-java, famfamfam-flag-png, OpenPGP_signature Description: OpenPGP digital signature
Bug#1005596: marked as done (modem-manager-gui: FTBFS: ../appdata/meson.build:3:5: ERROR: Function does not take positional arguments.)
Your message dated Sun, 27 Mar 2022 20:35:59 + with message-id and subject line Bug#1005596: fixed in modem-manager-gui 0.0.20-3 has caused the Debian Bug report #1005596, regarding modem-manager-gui: FTBFS: ../appdata/meson.build:3:5: ERROR: Function does not take positional arguments. 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.) -- 1005596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005596 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: modem-manager-gui Version: 0.0.20-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220212 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary --buildsystem=meson+ninja >dh_update_autotools_config -O--buildsystem=meson\+ninja >dh_autoreconf -O--buildsystem=meson\+ninja >dh_auto_configure -O--buildsystem=meson\+ninja > cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu > The Meson build system > Version: 0.61.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > Project name: Modem Manager GUI > Project version: 0.0.19.1 > C compiler for the host machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-16) > 11.2.0") > C linker for the host machine: cc ld.bfd 2.38 > Host machine cpu family: x86_64 > Host machine cpu: x86_64 > Found pkg-config: /usr/bin/pkg-config (0.29.2) > Run-time dependency glib-2.0 found: YES 2.70.3 > Run-time dependency gobject-2.0 found: YES 2.70.3 > Run-time dependency gio-2.0 found: YES 2.70.3 > Run-time dependency gmodule-2.0 found: YES 2.70.3 > Run-time dependency gtk+-3.0 found: YES 3.24.31 > Run-time dependency ofono found: YES 1.31 > Run-time dependency gtkspell3-3.0 found: YES 3.0.10 > Run-time dependency ayatana-appindicator3-0.1 found: YES 0.5.90 > Library gdbm found: YES > Library rt found: YES > Library m found: YES > Program po4a found: YES (/usr/bin/po4a) > Configuring resources.h using configuration > > ../appdata/meson.build:3:5: ERROR: Function does not take positional > arguments. > > A full log can be found at > /<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt > cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt > ==> meson-logs/meson-log.txt <== > Build started at 2022-02-12T22:47:53.904356 > Main binary: /usr/bin/python3 > Build Options: -Dprefix=/usr -Dlibdir=lib/x86_64-linux-gnu > -Dlocalstatedir=/var -Dsysconfdir=/etc -Dbuildtype=plain > -Dwrap_mode=nodownload > Python system: Linux > The Meson build system > Version: 0.61.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > Project name: Modem Manager GUI > Project version: 0.0.19.1 > Sanity testing C compiler: cc > Is cross compiler: False. > Sanity check compiler command line: cc sanitycheckc.c -o sanitycheckc.exe -g > -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 > -D_FILE_OFFSET_BITS=64 -Wl,-z,relro -Wl,-z,now > Sanity check compile stdout: > > - > Sanity check compile stderr: > > - > Running test binary command: > /<>/obj-x86_64-linux-gnu/meson-private/sanitycheckc.exe > C compiler for the host machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-16) > 11.2.0") > C linker for the host machine: cc ld.bfd 2.38 > Sanity testing C compiler: cc > Is cross compiler: False. > Sanity check compiler command line: cc sanitycheckc.c -o sanitycheckc.exe -g > -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 > -D_FILE_OFFSET_BITS=64 -Wl,-z,relro -Wl,-z,now > Sanity check compile stdout: > > - > Sanity check compile stderr: > > - > Running test binary command: > /<>/obj-x86_64-linux-gnu/meson-private/sanitycheckc.exe > C compiler for the build machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-16) > 11.2.0") > C linker for the build machine: cc ld.bfd 2.38 > Build machine cpu family: x86_64 > Build machine cpu: x86_64 > Host machine cpu family: x86_64 > Host machine cpu: x86_64 > Target machine cpu family: x86_64 > Target machine cpu: x86_64 > Pkg-config binary for 1 is not cached. > Pkg-config binary missing from cross or native file, or env var undefined. > Trying a default Pkg-config fallback at pkg-config > Found pkg-config: /usr/bin/pkg-config (0.29.2) > Determining dependency 'glib-2.0'
Bug#1008415: libnih: FTBFS: dh_auto_test: error: make -j8 check VERBOSE=1 returned exit code 2
Hi Axel, On Sa 26 Mär 2022 23:57:57 CET, Axel Beckert wrote: But a short look through those binary packages most likely having reverse-dependencies (libnih-dbus1 and libnih1), I though found a single reverse dependency not coming from the libnih package: $ apt-cache rdepends libnih1 libnih1 Reverse Depends: libnih-dbus1 libnih1-dbgsym nih-dbus-tool libnih-dev $ apt-cache rdepends libnih-dbus1 libnih-dbus1 Reverse Depends: libnih-dbus-dev libnih-dbus1-dbgsym libldm-priv-common0 ^^^ So with just one reverse dependency left and being orphaned since 2016, it's probably time for removal. Cc'ing the package maintainers of the sole reverse dependency I've found, lomiri-download-manager (source package of libldm-priv-common0) for a comment how "needed" libnih is in their package. I will bring this up in our next upstream dev meeting and see what we can do about this. Personally, I think the dependency on libnih-dbus-dev looks so minimal in lomiri-download-manager, it should be replacable. Mike -- mike gabriel aka sunweaver (Debian Developer) mobile: +49 (1520) 1976 148 landline: +49 (4351) 486 14 27 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: sunwea...@debian.org, http://sunweavers.net pgpqagS4m9Gk5.pgp Description: Digitale PGP-Signatur
Processed: forcibly merging 1003012 1008235
Processing commands for cont...@bugs.debian.org:
> forcemerge 1003012 1008235
Bug #1003012 {Done: Salvatore Bonaccorso } [bash] bash:
Corrupted multibyte characters in command substitutions
Bug #1008235 [bash] bash: corrupting variables containing long unicode content
Set Bug forwarded-to-address to
'https://lists.gnu.org/archive/html/bug-bash/2022-01/msg0.html
https://savannah.gnu.org/patch/?10035'.
Severity set to 'critical' from 'important'
Marked Bug as done
Marked as fixed in versions bash/5.1-6.
Added tag(s) patch, upstream, and l10n.
Merged 1003012 1008235
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1003012: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003012
1008235: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008235
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tags 1001669 help Bug #1001669 [src:openvpn-auth-ldap] openvpn-auth-ldap: flaky autopkgtest on amd64 Added tag(s) help. > End of message, stopping processing here. Please contact me if you need assistance. -- 1001669: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001669 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1001669: closed by Debian FTP Masters
On Wed, 23 Mar 2022 09:09:00 +0100 Aniol Martí wrote:> I've tried several times and I can't reproduce the bug. I would need further details or assistance. Besides, I also noticed that the last test passed fine: https://ci.debian.net/data/autopkgtest/unstable/amd64/o/openvpn-auth-ldap/20263239/log.gz I've added some verbosity to the test and I've tried in with Salsa and the problem seems to be the following: ERROR: Cannot open TUN/TAP dev /dev/net/tun: Operation not permitted (errno=1) Although I've added "isolation-container" to the test restrictions it still fails. Maybe there have been some changes in the Docker configuration? Regards, Aniol
Bug#1008465: [Debian-pan-maintainers] Bug#1008465: python-fabio: FTBFS: Could not import extension nbsphinx (exception: No module named 'ipython_genutils')
Hi Lucas,
Thanks for the report. This looks like a bug I recently fixed in pyFAI ... I'll
have a look tomorrow. Probably just a missing dependency like in
https://github.com/silx-kit/pyFAI/commit/7bcb6dd7419b48580d97cd91a28d05f86b301f1c
Cheers,
Jerome
On Sat, 26 Mar 2022 22:57:37 +0100
Lucas Nussbaum wrote:
> Source: python-fabio
> Version: 0.13.0+dfsg-1
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20220326 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_build
> > I: pybuild base:237: /usr/bin/python3.10 setup.py build
> > /<>/setup.py:49: DeprecationWarning: The distutils package is
> > deprecated and slated for removal in Python 3.12. Use setuptools or check
> > PEP 632 for potential alternatives
> > from distutils.command.clean import clean as Clean
> > INFO:fabio.setup:Use setuptools with cython
> > INFO:fabio.setup:Install requires: numpy >=1.21.5
> > running build
> > running build_py
> > running build_ext
> > I: pybuild base:237: /usr/bin/python3 setup.py build
> > INFO:fabio.setup:Use setuptools with cython
> > INFO:fabio.setup:Install requires: numpy >=1.21.5
> > running build
> > running build_py
> > running build_ext
> > dh_auto_build -- -s custom --build-args="PYTHONPATH={build_dir} xvfb-run -a
> > --server-args=\"-screen 0 1024x768x24\" {interpreter} setup.py build_man"
> > I: pybuild base:237:
> > PYTHONPATH=/<>/.pybuild/cpython3_3.10_fabio/build xvfb-run -a
> > --server-args="-screen 0 1024x768x24" python3.10 setup.py build_man
> > /<>/setup.py:49: DeprecationWarning: The distutils package is
> > deprecated and slated for removal in Python 3.12. Use setuptools or check
> > PEP 632 for potential alternatives
> > from distutils.command.clean import clean as Clean
> > INFO:fabio.setup:Use setuptools with cython
> > INFO:fabio.setup:Install requires: numpy >=1.21.5
> > running build_man
> > INFO:fabio.setup:Build man for entry-point target 'fabio-convert'
> > INFO:fabio.setup:Build man for entry-point target 'eiger2cbf'
> > ERROR:eiger2cbf:Numexpr is needed to interpret formula ...
> > INFO:fabio.setup:Build man for entry-point target 'eiger2crysalis'
> > ERROR:eiger2crysalis:Numexpr is needed to interpret formula ...
> > INFO:fabio.setup:Build man for entry-point target 'densify-Bragg'
> > INFO:fabio.setup:Build man for entry-point target 'fabio_viewer'
> > I: pybuild base:237:
> > PYTHONPATH=/<>/.pybuild/cpython3_3.9_fabio/build xvfb-run -a
> > --server-args="-screen 0 1024x768x24" python3.9 setup.py build_man
> > INFO:fabio.setup:Use setuptools with cython
> > INFO:fabio.setup:Install requires: numpy >=1.21.5
> > running build_man
> > INFO:fabio.setup:Build man for entry-point target 'fabio-convert'
> > INFO:fabio.setup:Build man for entry-point target 'eiger2cbf'
> > ERROR:eiger2cbf:Numexpr is needed to interpret formula ...
> > INFO:fabio.setup:Build man for entry-point target 'eiger2crysalis'
> > ERROR:eiger2crysalis:Numexpr is needed to interpret formula ...
> > INFO:fabio.setup:Build man for entry-point target 'densify-Bragg'
> > INFO:fabio.setup:Build man for entry-point target 'fabio_viewer'
> > dh_auto_build -- -s custom --build-args="cd doc && PYTHONPATH={build_dir}
> > http_proxy='127.0.0.1:9' {interpreter} -m sphinx -N -bhtml source
> > build/html"
> > I: pybuild base:237: cd doc &&
> > PYTHONPATH=/<>/.pybuild/cpython3_3.10_fabio/build
> > http_proxy='127.0.0.1:9' python3.10 -m sphinx -N -bhtml source build/html
> > Running Sphinx v4.3.2
> >
> > Extension error:
> > Could not import extension nbsphinx (exception: No module named
> > 'ipython_genutils')
> > E: pybuild pybuild:367: build: plugin custom failed with: exit code=2: cd
> > doc && PYTHONPATH=/<>/.pybuild/cpython3_3.10_fabio/build
> > http_proxy='127.0.0.1:9' python3.10 -m sphinx -N -bhtml source build/html
> > I: pybuild base:237: cd doc &&
> > PYTHONPATH=/<>/.pybuild/cpython3_3.9_fabio/build
> > http_proxy='127.0.0.1:9' python3.9 -m sphinx -N -bhtml source build/html
> > Running Sphinx v4.3.2
> >
> > Extension error:
> > Could not import extension nbsphinx (exception: No module named
> > 'ipython_genutils')
> > E: pybuild pybuild:367: build: plugin custom failed with: exit code=2: cd
> > doc && PYTHONPATH=/<>/.pybuild/cpython3_3.9_fabio/build
> > http_proxy='127.0.0.1:9' python3.9 -m sphinx -N -bhtml source build/html
> > dh_auto_build: error: pybuild --build -i python{version} -p "3.10 3.9" -s
> > custom "--build-args=cd doc && PYTHONPATH={build_dir}
> > http_proxy='127.0.0.1:9' {interpreter} -m sphinx -N -bhtml source
> > build/html" returned exit code 13
> > make[1]: *** [debian/rules:21: override_dh_auto_build-indep] Error 25
>
>
> The full build log is available from:
> http://qa-logs.debian.net/2022/03/26/python-fabio_0.13.0+dfsg-1_unstable.log
>
> A list of
Processed: Re: Bug#1008337: shotwell: FTBFS: ../src/Resources.vala:38.34-38.40: error: value is less accessible than constant `Resources.PREFIX'
Processing commands for cont...@bugs.debian.org: > forwarded 1008337 https://gitlab.gnome.org/GNOME/shotwell/-/issues/4967 Bug #1008337 [src:shotwell] shotwell: FTBFS: ../src/Resources.vala:38.34-38.40: error: value is less accessible than constant `Resources.PREFIX' Set Bug forwarded-to-address to 'https://gitlab.gnome.org/GNOME/shotwell/-/issues/4967'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1008337: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008337 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1008337: shotwell: FTBFS: ../src/Resources.vala:38.34-38.40: error: value is less accessible than constant `Resources.PREFIX'
forwarded 1008337 https://gitlab.gnome.org/GNOME/shotwell/-/issues/4967 thanks Hello Lucas, thank you for spending your time helping to make Debian better with this bug report. Am Samstag, dem 26.03.2022 um 21:48 +0100 schrieb Lucas Nussbaum: > Source: shotwell > Version: 0.30.14-2 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20220326 ftbfs-bookworm > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > [...] I have forwarded this bug to upstream. CU Jörg -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key: 8CA1D25D Jörg Frings-Fürst D-54470 Lieser git: https://jff.email/cgit/ Threema: SYR8SJXB Skype: joergpenguin Telegram: @joergfringsfuerst My wish list: - Please send me a picture from the nature at your home. signature.asc Description: This is a digitally signed message part
Bug#1008456: marked as done (python-whitenoise: FTBFS: FAILED tests/test_django_whitenoise.py::test_get_gzip - AssertionError: asser...)
Your message dated Sun, 27 Mar 2022 14:35:21 +
with message-id
and subject line Bug#1008456: fixed in python-whitenoise 6.0.0-1
has caused the Debian Bug report #1008456,
regarding python-whitenoise: FTBFS: FAILED
tests/test_django_whitenoise.py::test_get_gzip - AssertionError: asser...
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.)
--
1008456: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008456
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-whitenoise
Version: 5.2.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220326 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 '/<>'
> set -e; for python in $(py3versions --requested 2>/dev/null); do \
> DJANGO_SETTINGS_MODULE=tests.django_settings $python -m pytest; \
> done
> = test session starts
> ==
> platform linux -- Python 3.10.4, pytest-6.2.5, py-1.10.0, pluggy-1.0.0
> rootdir: /<>, configfile: setup.cfg
> collected 108 items
>
> tests/test_compress.py . [
> 8%]
> tests/test_django_whitenoise.py ...F.. [
> 28%]
> tests/test_runserver_nostatic.py . [
> 29%]
> tests/test_storage.py . [
> 34%]
> tests/test_whitenoise.py ..s [
> 77%]
>
> [100%]
>
> === FAILURES
> ===
> test_get_gzip
> _
>
> server =
> static_files =
> _collect_static = None
>
> def test_get_gzip(server, static_files, _collect_static):
> url = storage.staticfiles_storage.url(static_files.js_path)
> response = server.get(url)
> assert response.content == static_files.js_content
> > assert response.headers["Content-Encoding"] == "gzip"
> E AssertionError: assert 'br' == 'gzip'
> E - gzip
> E + br
>
> tests/test_django_whitenoise.py:103: AssertionError
> === warnings summary
> ===
> ../../../usr/lib/python3/dist-packages/_pytest/config/__init__.py:1233
> /usr/lib/python3/dist-packages/_pytest/config/__init__.py:1233:
> PytestConfigWarning: Unknown config option: DJANGO_SETTINGS_MODULE
>
> self._warn_or_fail_if_strict(f"Unknown config option: {key}\n")
>
> tests/test_django_whitenoise.py::test_non_ascii_requests_safely_ignored[True]
> /<>/tests/django_urls.py:9: RemovedInDjango40Warning:
> django.conf.urls.url() is deprecated in favor of django.urls.re_path().
> urlpatterns = [url(r"^hello$", hello_world)]
>
> -- Docs: https://docs.pytest.org/en/stable/warnings.html
> === short test summary info
>
> FAILED tests/test_django_whitenoise.py::test_get_gzip - AssertionError:
> asser...
> = 1 failed, 106 passed, 1 skipped, 2 warnings in 0.66s
> =
> make[1]: *** [debian/rules:14: override_dh_auto_test] Error 1
The full build log is available from:
http://qa-logs.debian.net/2022/03/26/python-whitenoise_5.2.0-1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: python-whitenoise
Source-Version: 6.0.0-1
Done: Antonio Terceiro
We believe that the bug you reported is fixed in the latest version of
python-whitenoise, 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 1008...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Antonio Terceiro (supplier of updated python-whitenoise
Bug#1008436: marked as done (golang-github-ugorji-go-codec: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 github.com/ugorji/go/codec github.com/ugorji/go/codec/codecg
Your message dated Sun, 27 Mar 2022 12:19:09 + with message-id and subject line Bug#1008436: fixed in golang-github-ugorji-go-codec 1.2.7-1 has caused the Debian Bug report #1008436, regarding golang-github-ugorji-go-codec: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 github.com/ugorji/go/codec github.com/ugorji/go/codec/codecgen returned exit code 1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1008436: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008436 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-ugorji-go-codec Version: 1.1.7-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220326 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary --buildsystem=golang --with=golang >dh_update_autotools_config -O--buildsystem=golang >dh_autoreconf -O--buildsystem=golang >dh_auto_configure -O--buildsystem=golang >dh_auto_build -O--buildsystem=golang > cd obj-x86_64-linux-gnu && go generate -v github.com/ugorji/go/codec > github.com/ugorji/go/codec/codecgen > src/github.com/ugorji/go/codec/0_importpath.go > src/github.com/ugorji/go/codec/binc.go > src/github.com/ugorji/go/codec/cbor.go > src/github.com/ugorji/go/codec/cbor_test.go > src/github.com/ugorji/go/codec/codec_test.go > src/github.com/ugorji/go/codec/decode.go > src/github.com/ugorji/go/codec/doc.go > src/github.com/ugorji/go/codec/encode.go > src/github.com/ugorji/go/codec/fast-path.generated.go > src/github.com/ugorji/go/codec/float.go > src/github.com/ugorji/go/codec/gen-helper.generated.go > src/github.com/ugorji/go/codec/goversion_arrayof_gte_go15.go > src/github.com/ugorji/go/codec/goversion_fmt_time_gte_go15.go > src/github.com/ugorji/go/codec/goversion_makemap_gte_go19.go > src/github.com/ugorji/go/codec/goversion_unexportedembeddedptr_gte_go110.go > src/github.com/ugorji/go/codec/goversion_vendor_gte_go17.go > src/github.com/ugorji/go/codec/helper.go > src/github.com/ugorji/go/codec/helper_internal.go > src/github.com/ugorji/go/codec/helper_test.go > src/github.com/ugorji/go/codec/helper_unsafe.go > src/github.com/ugorji/go/codec/json.go > src/github.com/ugorji/go/codec/mammoth2_generated_test.go > src/github.com/ugorji/go/codec/mammoth_generated_test.go > src/github.com/ugorji/go/codec/msgpack.go > src/github.com/ugorji/go/codec/reader.go > src/github.com/ugorji/go/codec/register_ext.go > src/github.com/ugorji/go/codec/rpc.go > src/github.com/ugorji/go/codec/shared_test.go > src/github.com/ugorji/go/codec/simple.go > src/github.com/ugorji/go/codec/sort-slice.generated.go > src/github.com/ugorji/go/codec/values_flex_test.go > src/github.com/ugorji/go/codec/values_test.go > src/github.com/ugorji/go/codec/writer.go > src/github.com/ugorji/go/codec/codecgen/gen.go > src/github.com/ugorji/go/codec/codecgen/goversion_pkgpath_gte_go111.go > src/github.com/ugorji/go/codec/codecgen/z.go > cd obj-x86_64-linux-gnu && go install -trimpath -v -p 8 > github.com/ugorji/go/codec github.com/ugorji/go/codec/codecgen > internal/goarch > internal/goexperiment > internal/race > internal/unsafeheader > internal/cpu > internal/goos > runtime/internal/atomic > runtime/internal/syscall > internal/abi > sync/atomic > runtime/internal/math > unicode > runtime/internal/sys > unicode/utf8 > encoding > math/bits > internal/itoa > unicode/utf16 > internal/nettrace > container/list > crypto/internal/subtle > crypto/subtle > vendor/golang.org/x/crypto/cryptobyte/asn1 > vendor/golang.org/x/crypto/internal/subtle > internal/goversion > golang.org/x/xerrors/internal > internal/bytealg > math > runtime > internal/reflectlite > sync > internal/testlog > internal/singleflight > math/rand > runtime/cgo > errors > sort > io > internal/oserror > path > vendor/golang.org/x/net/dns/dnsmessage > strconv > crypto/elliptic/internal/fiat > syscall > container/heap > golang.org/x/mod/semver > bytes > strings > hash > hash/crc32 > crypto/internal/randutil > reflect > crypto > crypto/hmac > crypto/rc4 > vendor/golang.org/x/text/transform > vendor/golang.org/x/crypto/hkdf > html > bufio > net/http/internal/ascii > regexp/syntax > go/build/constraint > crypto/elliptic/internal/nistec > internal/syscall/execenv > time > internal/syscall/unix > regexp > encoding/binary > internal/fmtsort > io/fs > internal/poll > context > embed > crypto/cipher > crypto/sha512 > crypto/ed25519/internal/edwards25519/field >
Bug#1008441: marked as done (astropy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13)
Your message dated Sun, 27 Mar 2022 13:53:12 +0200
with message-id <5c4c8692-bb95-eb25-1782-937913b52...@debian.org>
and subject line Re: astropy: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.10 3.9" returned exit code 13
has caused the Debian Bug report #1008441,
regarding astropy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i
python{version} -p "3.10 3.9" 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.)
--
1008441: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008441
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: astropy
Version: 5.0.2-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220326 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_test
> I: pybuild base:237: cd /<>/.pybuild/cpython3_3.10/build;
> python3.10 -m pytest --astropy-header -m "not hypothesis"
> = test session starts
> ==
> platform linux -- Python 3.10.4, pytest-6.2.5, py-1.10.0, pluggy-1.0.0
>
> Running tests with Astropy version 5.0.2.
> Running tests in .pybuild/cpython3_3.10/build.
>
> Date: 2022-03-26T19:25:44
>
> Platform: Linux-5.10.0-9-cloud-amd64-x86_64-with-glibc2.33
>
> Executable: /usr/bin/python3.10
>
> Full Python Version:
> 3.10.4 (main, Mar 24 2022, 13:07:27) [GCC 11.2.0]
>
> encodings: sys: utf-8, locale: UTF-8, filesystem: utf-8
> byteorder: little
> float info: dig: 15, mant_dig: 15
>
> Package versions:
> Numpy: 1.21.5
> Scipy: 1.7.3
> Matplotlib: 3.5.1
> h5py: 3.6.0
> Pandas: not available
> PyERFA: 2.0.0.1
> Cython: 0.29.28
> Scikit-image: 0.18.3
> asdf: not available
> pyarrow: not available
>
> Using Astropy options: remote_data: none.
>
> Matplotlib: 3.5.1
> Freetype: 2.11.1
> ARCH_ON_CI: undefined
> IS_CRON: undefined
>
> rootdir: /<>, configfile: setup.cfg
> plugins: astropy-header-0.2.1, mock-3.6.1, hypothesis-6.36.0, mpl-0.11,
> filter-subpackage-0.1.1, arraydiff-0.5.0, doctestplus-0.12.0,
> openfiles-0.5.0, cov-3.0.0, remotedata-0.3.3
> collected 19928 items / 67 deselected / 10 skipped / 19851 selected
>
> astropy/config/configuration.py .[
> 0%]
> astropy/config/tests/test_configs.py .sss.. [
> 0%]
> astropy/constants/__init__.py . [
> 0%]
> astropy/constants/tests/test_constant.py [
> 0%]
> astropy/constants/tests/test_pickle.py . [
> 0%]
> astropy/constants/tests/test_prior_version.py .. [
> 0%]
> astropy/constants/tests/test_sciencestate.py .. [
> 0%]
> astropy/convolution/convolve.py .[
> 0%]
> astropy/convolution/kernels.py ... [
> 0%]
> astropy/convolution/tests/test_convolve.py . [
> 0%]
> [
> 0%]
> [
> 1%]
> [
> 1%]
> [
> 1%]
> [
> 2%]
> [
> 2%]
> ...x.x.x.x.x.x.x.x.. [
> 2%]
> s... [
> 3%]
> [
> 3%]
> astropy/convolution/tests/test_convolve_fft.py . [
> 3%]
> [
> 3%]
> [
> 4%]
> [
> 4%]
> [
> 4%]
> [
> 5%]
> [
> 5%]
> [
Bug#1008486: dpkg-fsys-usrunmess: should include warning that systems will be unsupported
Package: dpkg Version: 1.21.2 Severity: serious Hi, the `dpkg-fsys-usrunmess` program should include a warning that it will convert the system into a state that will no longer be supported in the future by Debian. Ansgar
Processed: Bug#1008429 marked as pending in golang-github-docker-distribution
Processing control commands: > tag -1 pending Bug #1008429 [src:docker-registry] docker-registry: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 -test.short -test.timeout=1h github.com/docker/distribution github.com/docker/distribution/cmd/registry [...] github.com/docker/distribution/testutil github.com/docker/distribution/uuid github.com/docker/distribution/version returned exit code 1 Added tag(s) pending. -- 1008429: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008429 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1008429: marked as pending in golang-github-docker-distribution
Control: tag -1 pending Hello, Bug #1008429 in golang-github-docker-distribution 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/go-team/packages/golang-github-docker-distribution/-/commit/b6e18f882ddda41809ea39a6922a5110767fd4a4 Fix panic in inmemory driver (Closes: #1008429) (this message was generated automatically) -- Greetings https://bugs.debian.org/1008429
Bug#1008329: apertium-spa-arg: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.7) were not met
On 26/03/22 at 23:36 +0100, Tino Didriksen wrote: > This was an expected failure due to new incompatible tool packages, and > same goes for all the other Apertium-related FTBFS. > > How can one prevent such a slew of superfluous automatic bugs from being > filed? Is there a way to mark packages as "will be updated, just waiting > for deps in NEW queue"? Hi Tino, First, I don't mind filing those bugs. I try to avoid filing useless bugs, but generally, when the number of affected packages is relatively low, investigating the root cause and determining if/where a bug should be filed is quite hard, and it's simpler to stick to the fact that a package fails to build, and file a bug for each package. Note that: - it's easy to identify all bugs there were filed using the BTS usertag - sometimes, the full set of failures is nontrivial to identify from the maintainer's POV, so filing all bugs also has some value to clearly identify the scope. However, if you know that a set of packages FTBFS due to a change in another package, you could document it using a single bug against the breaking package, marking all affected packages as "affects" in the BTS. Lucas
Bug#1008360: [Debian-on-mobile-maintainers] Bug#1008360: phoc: FTBFS: ../src/layer_shell.c:244:72: error: ‘struct wlr_layer_surface_v1’ has no member named ‘client_pending’
control: tags -1 +pending
Hi,
On Sat, Mar 26, 2022 at 09:47:37PM +0100, Lucas Nussbaum wrote:
> Source: phoc
> Version: 0.12.0-1
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20220326 ftbfs-bookworm
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
I'll upload a version that works with wlroots 0.15.1 over the next days.
Upstream MR is here:
https://gitlab.gnome.org/World/Phosh/phoc/-/merge_requests/329
Cheers,
-- Guido
>
>
> Relevant part (hopefully):
> > cc -Isrc/libphoc.a.p -Isrc -I../src -Iprotocols -I/usr/include/libdrm
> > -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0
> > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include
> > -I/usr/include/gnome-desktop-3.0 -I/usr/include/libxml2
> > -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0
> > -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0
> > -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gio-unix-2.0
> > -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/harfbuzz
> > -I/usr/include/fribidi -I/usr/include/atk-1.0 -I/usr/include/pixman-1
> > -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16
> > -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/x86_64-linux-gnu
> > -I/usr/include/gsettings-desktop-schemas
> > -I/<>/obj-x86_64-linux-gnu -fdiagnostics-color=always
> > -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu11 -O0
> > -DWLR_USE_UNSTABLE -Wcast-align -Wdate-time -Werror=format-security
> > -Werror=format=2 -Wendif-labels -Werror=incompatible-pointer-types
> > -Werror=missing-declarations -Werror=overflow -Werror=return-type
> > -Werror=shift-count-overflow -Werror=shift-overflow=2
> > -Werror=implicit-fallthrough=3 -Wformat-nonliteral -Wformat-security
> > -Winit-self -Wmaybe-uninitialized -Wmissing-field-initializers
> > -Wmissing-include-dirs -Wmissing-noreturn -Wnested-externs
> > -Wno-missing-field-initializers -Wno-sign-compare -Wno-strict-aliasing
> > -Wno-unused-parameter -Wold-style-definition -Wpointer-arith
> > -Wredundant-decls -Wshadow -Wstrict-prototypes -Wtype-limits -Wundef
> > -Wunused-function -Wswitch-default -g -O2
> > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD
> > -MQ src/libphoc.a.p/layer_shell.c.o -MF src/libphoc.a.p/layer_shell.c.o.d
> > -o src/libphoc.a.p/layer_shell.c.o -c ../src/layer_shell.c
> > In file included from ../src/layer_shell.c:15:
> > /usr/include/wlr/types/wlr_box.h:4:2: warning: #warning "wlr_box has been
> > moved to wlr/util/box.h" [-Wcpp]
> > 4 | #warning "wlr_box has been moved to wlr/util/box.h"
> > | ^~~
> > ../src/layer_shell.c: In function ‘arrange_layer’:
> > ../src/layer_shell.c:187:25: warning: implicit declaration of function
> > ‘wlr_layer_surface_v1_close’; did you mean ‘wlr_layer_surface_v1_destroy’?
> > [-Wimplicit-function-declaration]
> > 187 | wlr_layer_surface_v1_close(layer);
> > | ^~
> > | wlr_layer_surface_v1_destroy
> > ../src/layer_shell.c:187:25: warning: nested extern declaration of
> > ‘wlr_layer_surface_v1_close’ [-Wnested-externs]
> > ../src/layer_shell.c: In function ‘change_osk’:
> > ../src/layer_shell.c:244:72: error: ‘struct wlr_layer_surface_v1’ has no
> > member named ‘client_pending’
> > 244 | if (!force_overlay && osk->layer !=
> > osk->surface->layer_surface->client_pending.layer) {
> > |
> >^~
> > ../src/layer_shell.c:246:67: error: ‘struct wlr_layer_surface_v1’ has no
> > member named ‘client_pending’
> > 246 |
> > wl_list_insert([osk->surface->layer_surface->client_pending.layer],
> > >surface->link);
> > | ^~
> > ../src/layer_shell.c: In function ‘phoc_layer_shell_arrange’:
> > ../src/layer_shell.c:273:53: error: ‘struct wlr_layer_surface_v1’ has no
> > member named ‘client_pending’
> > 273 | if (seat->focused_layer &&
> > seat->focused_layer->client_pending.layer >=
> > osk_place.surface->layer_surface->client_pending.layer) {
> > | ^~
> > ../src/layer_shell.c:273:111: error: ‘struct wlr_layer_surface_v1’ has no
> > member named ‘client_pending’
> > 273 | if (seat->focused_layer &&
> > seat->focused_layer->client_pending.layer >=
> > osk_place.surface->layer_surface->client_pending.layer) {
> > |
> > ^~
> > ../src/layer_shell.c: In function ‘popup_damage’:
> > ../src/layer_shell.c:436:55: error: ‘struct wlr_xdg_surface’ has no member
> > named ‘geometry’
> > 436
Processed: Re: [Debian-on-mobile-maintainers] Bug#1008360: phoc: FTBFS: ../src/layer_shell.c:244:72: error: ‘struct wlr_layer_surface_v1’ has no member named ‘client_pending’
Processing control commands: > tags -1 +pending Bug #1008360 [src:phoc] phoc: FTBFS: ../src/layer_shell.c:244:72: error: ‘struct wlr_layer_surface_v1’ has no member named ‘client_pending’ Added tag(s) pending. -- 1008360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008360 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1008417: marked as done (golang-github-rican7-retry: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 8 github.com/Rican7/retry github.com/Rican7/retry/backoff github.com/Rican7/ret
Your message dated Sun, 27 Mar 2022 10:03:56 + with message-id and subject line Bug#1008417: fixed in golang-github-rican7-retry 0.3.1-1 has caused the Debian Bug report #1008417, regarding golang-github-rican7-retry: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 8 github.com/Rican7/retry github.com/Rican7/retry/backoff github.com/Rican7/retry/jitter github.com/Rican7/retry/strategy returned exit code 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1008417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008417 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-rican7-retry Version: 0.1.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220326 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary --builddirectory=_build --buildsystem=golang --with=golang >dh_update_autotools_config -O--builddirectory=_build -O--buildsystem=golang >dh_autoreconf -O--builddirectory=_build -O--buildsystem=golang >dh_auto_configure -O--builddirectory=_build -O--buildsystem=golang >dh_auto_build -O--builddirectory=_build -O--buildsystem=golang > cd _build && go install -trimpath -v -p 8 github.com/Rican7/retry > github.com/Rican7/retry/backoff github.com/Rican7/retry/jitter > github.com/Rican7/retry/strategy > math/bits > internal/unsafeheader > internal/goarch > internal/cpu > runtime/internal/syscall > runtime/internal/atomic > internal/goexperiment > internal/goos > internal/race > sync/atomic > internal/abi > runtime/internal/math > runtime/internal/sys > internal/itoa > internal/bytealg > math > runtime > internal/reflectlite > sync > math/rand > errors > internal/oserror > syscall > time > github.com/Rican7/retry/backoff > github.com/Rican7/retry/jitter > github.com/Rican7/retry/strategy > github.com/Rican7/retry >dh_auto_test -O--builddirectory=_build -O--buildsystem=golang > cd _build && go test -vet=off -v -p 8 github.com/Rican7/retry > github.com/Rican7/retry/backoff github.com/Rican7/retry/jitter > github.com/Rican7/retry/strategy > # github.com/Rican7/retry [github.com/Rican7/retry.test] > src/github.com/Rican7/retry/retry_test.go:143:6: logFile declared but not used > FAIL github.com/Rican7/retry [build failed] > === RUN TestIncremental > --- PASS: TestIncremental (0.00s) > === RUN TestLinear > --- PASS: TestLinear (0.00s) > === RUN TestExponential > --- PASS: TestExponential (0.00s) > === RUN TestBinaryExponential > --- PASS: TestBinaryExponential (0.00s) > === RUN TestFibonacci > --- PASS: TestFibonacci (0.00s) > === RUN TestFibonacciNumber > --- PASS: TestFibonacciNumber (0.00s) > === RUN ExampleIncremental > --- PASS: ExampleIncremental (0.00s) > === RUN ExampleLinear > --- PASS: ExampleLinear (0.00s) > === RUN ExampleExponential > --- PASS: ExampleExponential (0.00s) > === RUN ExampleBinaryExponential > --- PASS: ExampleBinaryExponential (0.00s) > === RUN ExampleFibonacci > --- PASS: ExampleFibonacci (0.00s) > PASS > okgithub.com/Rican7/retry/backoff 0.002s > === RUN TestFull > --- PASS: TestFull (0.00s) > === RUN TestEqual > --- PASS: TestEqual (0.00s) > === RUN TestDeviation > --- PASS: TestDeviation (0.00s) > === RUN TestNormalDistribution > --- PASS: TestNormalDistribution (0.00s) > === RUN TestFallbackNewRandom > --- PASS: TestFallbackNewRandom (0.00s) > PASS > okgithub.com/Rican7/retry/jitter 0.002s > === RUN TestLimit > --- PASS: TestLimit (0.00s) > === RUN TestDelay > --- PASS: TestDelay (0.01s) > === RUN TestWait > --- PASS: TestWait (0.00s) > === RUN TestWaitWithDuration > --- PASS: TestWaitWithDuration (0.01s) > === RUN TestWaitWithMultipleDurations > --- PASS: TestWaitWithMultipleDurations (0.08s) > === RUN TestBackoff > --- PASS: TestBackoff (0.05s) > === RUN TestBackoffWithJitter > --- PASS: TestBackoffWithJitter (0.00s) > === RUN TestNoJitter > --- PASS: TestNoJitter (0.00s) > PASS > okgithub.com/Rican7/retry/strategy0.149s > FAIL > dh_auto_test: error: cd _build && go test -vet=off -v -p 8 > github.com/Rican7/retry github.com/Rican7/retry/backoff > github.com/Rican7/retry/jitter github.com/Rican7/retry/strategy returned exit > code 2 The full build log is available from: http://qa-logs.debian.net/2022/03/26/golang-github-rican7-retry_0.1.0-2_unstable.log A list of current common problems and possible solutions is available at
Bug#1008446: marked as done (diffoscope: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13)
Your message dated Sun, 27 Mar 2022 08:33:46 +
with message-id
and subject line Bug#1008446: fixed in diffoscope 209
has caused the Debian Bug report #1008446,
regarding diffoscope: FTBFS: dh_auto_test: error: pybuild --test --test-pytest
-i python{version} -p "3.10 3.9" 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.)
--
1008446: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008446
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: diffoscope
Version: 208
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220326 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> === FAILURES
> ===
> test_item_rdb
> _
>
> differences_rdb = [ {} []>]
>
> @skip_unless_tools_exist("Rscript")
> def test_item_rdb(differences_rdb):
> assert differences_rdb[0].source1.startswith("Rscript")
> > assert_diff(differences_rdb[0], "rdb_expected_diff")
>
> differences_rdb = [ {} []>]
>
> tests/comparators/test_rdata.py:63:
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _
>
> difference =
> filename = 'rdb_expected_diff'
>
> def assert_diff(difference, filename):
> # Assign seen and expected values to local variables to improve
> contextual
> # information in failed tests.
> seen = difference.unified_diff
> expected = get_data(filename)
> > assert seen == expected
> E AssertionError
>
> difference =
> expected = ('@@ -1,10116 +1,4941 @@\n'
> '-%c%.matrix (closure) = function (e1, e2) \n'
> '-{\n'
> '-x <- as.sociomatrix.sna(e1)\n'
> '-y <- as.sociomatrix.sna(e2)\n'
> '-if (!(is.matrix(x) && is.matrix(y))) \n'
> '-stop("Single graphs required for composition.")\n'
> '-round((x %*% y) > 0)\n'
> '-}\n'
> '+.__C__Biodetection (S4) = new("classRepresentation", slots = list(dat = '
> 'structure("list", package = "methods")), \n'
> '+contains = list(), virtual = FALSE, prototype = 'NULL>, \n'
> '+validity = NULL, access = list(), className =
> structure("Biodetection", '
> 'package = "NOISeq"), \n'
> '+package = "NOISeq", subclasses = list(), versionKey = '(nil)>, \n'
> '+sealed = FALSE)\n'
> '+\n'
> '+.__C__CD (S4) = new("classRepresentation", slots = list(dat = '
> 'structure("list", package = "methods")), \n'
> '+contains = list(), virtual = FALSE, prototype = 'NULL>, \n'
> '+validity = NULL, access = list(), className = structure("CD", package
> = '
> '"NOISeq"), \n'
> '+package = "NOISeq", subclasses = list(), versionKey = '(nil)>, \n'
> '+sealed = FALSE)\n'
> '+\n'
> '+.__C__CountsBio (S4) = new("classRepresentation", slots = list(dat = '
> 'structure("list", package = "methods")), \n'
> '+contains = list(), virtual = FALSE, prototype = 'NULL>, \n'
> '+validity = NULL, access = list(), className = structure("CountsBio", '
> 'package = "NOISeq"), \n'
> '+package = "NOISeq", subclasses = list(), versionKey = '(nil)>, \n'
> '+sealed = FALSE)\n'
> '+\n'
> '+.__C__GCbias (S4) = new("classRepresentation", slots = list(dat = '
> 'structure("list", package = "methods")), \n'
> '+contains = list(), virtual = FALSE, prototype = 'NULL>, \n'
> '+validity = NULL, access = list(), className = structure("GCbias", '
> 'package = "NOISeq"), \n'
> '+package = "NOISeq", subclasses = list(), versionKey = '(nil)>, \n'
> '+sealed = FALSE)\n'
> '+\n'
> '+.__C__Output (S4) = new("classRepresentation", slots = list(results = '
> 'structure("list", package = "methods"), \n'
> '+method = structure("character", package = "methods"), k = '
> 'structure("numeric", package = "methods"), \n'
> '+lc = structure("numeric", package = "methods"), factor = '
> 'structure("vector", package = "methods"), \n'
> '+v = structure("numeric", package = "methods"), nss = '
> 'structure("numeric", package = "methods"), \n'
> '+pnr = structure("numeric", package = "methods"), comparison = '
> 'structure("vector", package = "methods"), \n'
> '+replicates = structure("character", package = "methods")), \n'
> '+contains = list(myInfo = new("SClassExtension", subClass = '
> 'structure("Output", package = "NOISeq"), \n'
> '+superClass = structure("myInfo", package =
Bug#1008377: zanshin: FTBFS: unsatisfiable build-dependencies: libkf5akonadi-dev (>= 4:21.08.40~), libkf5akonadicalendar-dev (>= 4:21.08.40~), libkf5kontactinterface-dev (>= 21.08.40~)
Le 26 mars 2022 21:52:54 GMT+01:00, Lucas Nussbaum a écrit : > >Hi, Dear Lucas, >During a rebuild of all packages in sid, your package failed to build >on amd64. Thanks for your bug report. I uploaded zanshin to unstable instead of experimental by mistake. This will be fixed once KDE PIM transitions to unstable and zanshin is rebuilt. Happy hacking ! -- Aurélien
Bug#1008318: marked as done (nanopb: missing dependency python3-protobuf)
Your message dated Sun, 27 Mar 2022 07:48:39 + with message-id and subject line Bug#1008318: fixed in nanopb 0.4.5-3 has caused the Debian Bug report #1008318, regarding nanopb: missing dependency python3-protobuf 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.) -- 1008318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008318 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nanopb Version: 0.4.5-2 Severity: serious Dear maintainer, nanopb is missing a dependency on python3-protobuf. Without it, the included tools are not running at all: > $ nanopb_generator.py > > * > *** Could not import the Google protobuf Python libraries *** > *** Try installing package 'python3-protobuf' or similar. *** > * > > Traceback (most recent call last): > File "/usr/bin/nanopb_generator.py", line 36, in > import google.protobuf.text_format as text_format > ModuleNotFoundError: No module named 'google' > > $ protoc-gen-nanopb > > * > *** Could not import the Google protobuf Python libraries *** > *** Try installing package 'python3-protobuf' or similar. *** > * > > Traceback (most recent call last): > File "/usr/bin/nanopb_generator.py", line 36, in > import google.protobuf.text_format as text_format > ModuleNotFoundError: No module named 'google' After installing python3-protobuf the tools are starting successfully. Kind regards, Reiner --- End Message --- --- Begin Message --- Source: nanopb Source-Version: 0.4.5-3 Done: Laszlo Boszormenyi (GCS) We believe that the bug you reported is fixed in the latest version of nanopb, 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 1008...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Laszlo Boszormenyi (GCS) (supplier of updated nanopb 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: Sun, 27 Mar 2022 09:03:25 +0200 Source: nanopb Architecture: source Version: 0.4.5-3 Distribution: unstable Urgency: medium Maintainer: Laszlo Boszormenyi (GCS) Changed-By: Laszlo Boszormenyi (GCS) Closes: 1008318 Changes: nanopb (0.4.5-3) unstable; urgency=medium . * Add python3-protobuf dependency (closes: #1008318). Checksums-Sha1: 7daaa5388e1d8a434bab5279b3ae22b4f8e109f5 1839 nanopb_0.4.5-3.dsc 6f37961bb61615c36fcdf44433f8ebb563ee2297 5440 nanopb_0.4.5-3.debian.tar.xz Checksums-Sha256: 9ccdb92b7bcef84448753352fc30b17c6401cd77b2a43cb72978b7daf0b6d382 1839 nanopb_0.4.5-3.dsc d3cec4ef9b11eeea397928d52e8572e8fe804f0c16225ede61750a8f23b029ef 5440 nanopb_0.4.5-3.debian.tar.xz Files: c4cebc12cc60306b03b19cd5f879839a 1839 devel optional nanopb_0.4.5-3.dsc 1ff709e585d1da018cf4e231bcb28f83 5440 devel optional nanopb_0.4.5-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAmJAE5QACgkQ3OMQ54ZM yL/64w/+NA/e7LPH90yee4XerXxmAOAwC84Tx564wWw1xjcZ3e2pzaGdFY5QdBxS wsBgI5zh5CfoPbC3Shv+pgmA3GMgTREo1MKdtaSISQiX9r2LBj6zb3a+47c5WFLy zSTgjIniuX29o4ji7zIzoKGXTG0ErbDNzQA7wjPchcmHg6l1ZpB/GB+o5odu+GkL FBbYHHf2/zkIbI+GrVWvmvLxqzaH5qShykOgm5wYdBY5bTWx7FKhVJbuOyIDAfrh vDsomA2IRl5tgYj8NJgZCq5YFYF2zKHPKMmHXBI1XINrspERdhD6aBktTqY/MeUI bI3KxxSWoMPvrC+Ch24v+8hJyGnWlMrm5Bm39AqfniIwWfslZOAmgyNN83bm69g5 BWEHO1uuMO8g+vua0Jx6lG4AksOifhhhA3B43JcEyN574MgKROeIQZU12rfzVIAJ qUF29ZQl7svKWJ2AFizH7pYmP7K55JRQlpu0+YlmuIFxoC+xkUtr3ogArQxcv/IM knX7LHJMlrxu1uHUUNcRH/JVSc8Uz7ggL6rrXFsZiOW1BPbUtvfjhgWhGBSFphQx 1m43yXTIySQgvUwJPWHV0s0dZS3mAO45XylT3KB2vbUEPc8O1bDDV3F/qO2DiMiV kxwvXMtqYQ30fE035jbuz09GDVhVETRpSUxkAerb/FPlDnUTnXQ= =HHNc -END PGP SIGNATURE End Message ---
Bug#1008156: telegram-desktop: Crash when switch account
Package: telegram-desktop
Version: 3.6.1+ds-2
Followup-For: Bug #1008156
X-Debbugs-Cc: mo...@debian.org
I can confirm the same problem. Moreover, my instance crashes also when I
choose the "Settings" ("Impostazioni" in Italian) menu.
-- Package-specific info:
-- System Information:
Debian Release: bookworm/sid
APT prefers stable-security
APT policy: (500, 'stable-security'), (500, 'unstable'), (500, 'testing'),
(500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.16.0-5-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages telegram-desktop depends on:
ii libabsl20210324 0~20210324.2-2
ii libavcodec587:4.4.1-3+b2
ii libavformat58 7:4.4.1-3+b2
ii libavutil56 7:4.4.1-3+b2
ii libc6 2.33-7
ii libgcc-s1 12-20220319-1
ii libglib2.0-02.72.0-1
ii libglibmm-2.4-1v5 2.66.2-2+b1
ii libhunspell-1.7-0 1.7.0-4
ii libjpeg62-turbo 1:2.1.2-1
ii libkf5waylandclient54:5.90.0-1
ii liblz4-11.9.3-2
ii libminizip1 1.1-8+b1
ii libopenal1 1:1.19.1-2
ii libopus01.3.1-0.1
ii libqrcodegencpp11.7.0-2+b1
ii libqt5core5a [qtbase-abi-5-15-2]5.15.2+dfsg-15
ii libqt5gui5 5.15.2+dfsg-15
ii libqt5network5 5.15.2+dfsg-15
ii libqt5svg5 5.15.2-4
ii libqt5waylandclient5 [qtwayland-client-abi-5-15-2] 5.15.2-4
ii libqt5widgets5 5.15.2+dfsg-15
ii librlottie0-1 0.1+dfsg-2
ii libsigc++-2.0-0v5 2.10.4-2
ii libssl1.1 1.1.1n-1
ii libstdc++6 12-20220319-1
ii libswresample3 7:4.4.1-3+b2
ii libswscale5 7:4.4.1-3+b2
ii libvpx7 1.11.0-2
ii libx11-62:1.7.2-2+b1
ii libxcb-keysyms1 0.4.0-1+b2
ii libxcb-record0 1.14-3
ii libxcb-screensaver0 1.14-3
ii libxcb1 1.14-3
ii libxcomposite1 1:0.4.5-1
ii libxdamage1 1:1.1.5-2
ii libxext62:1.3.4-1
ii libxfixes3 1:6.0.0-1
ii libxrandr2 2:1.5.2-1
ii libxtst62:1.2.3-1
ii libxxhash0 0.8.1-1
ii qt5-image-formats-plugins 5.15.2-2+b1
ii zlib1g 1:1.2.11.dfsg-4
Versions of packages telegram-desktop recommends:
ii fonts-open-sans 1.11-2
telegram-desktop suggests no packages.
Versions of packages telegram-desktop is related to:
ii xdg-desktop-portal 1.14.1-1
ii xdg-desktop-portal-gnome [xdg-desktop-portal-backend] 42.0.1-1
ii xdg-desktop-portal-gtk [xdg-desktop-portal-backend]1.14.0-1
-- no debconf information
[2022.03.27 09:17:34] Launched version: 3006001, install beta: [FALSE], alpha:
0, debug mode: [FALSE]
[2022.03.27 09:17:34] Executable dir: /usr/bin/, name: telegram-desktop
[2022.03.27 09:17:34] Initial working dir:
/opt/unburden/.unburden-monga/local/share/
[2022.03.27 09:17:34] Working dir: /home/monga/.local/share/TelegramDesktop/
[2022.03.27 09:17:34] Command line: telegram-desktop
[2022.03.27 09:17:34] Executable path before check: /usr/bin/telegram-desktop
[2022.03.27 09:17:34] Logs started
[2022.03.27 09:17:34] Launcher filename: telegramdesktop.desktop
[2022.03.27 09:17:34] We use allocator from /lib/x86_64-linux-gnu/libc.so.6
[2022.03.27 09:17:34] IBus portal is present! Using it.
[2022.03.27 09:17:34] Getting DE, XDG_CURRENT_DESKTOP: 'GNOME'
[2022.03.27 09:17:34] Getting DE, XDG_SESSION_DESKTOP: 'gnome-xorg'
[2022.03.27 09:17:34] Getting DE,
