Bug#1020895: whatmaps: postinst fails in clean chroot/container

[Gioele Barabucci]

Package: whatmaps
Version: 0.0.12-3
Severity: serious

Dear whatmaps maintainer,

whatmaps' postinst maintscript fails when run in a newly created 
unstable system, as used by autopkgtest.


Setting up whatmaps (0.0.12-3) ...
sed: can't read /etc/apt/apt.conf.d/20services: No such file
or directory
dpkg: error processing package whatmaps (--configure):
 installed whatmaps package post-installation script
 subprocess returned error exit status 2

A full log can be found at .

As of 2022-09-28, this can be reproduced using autopkgtest and lxc:

$ sudo autopkgtest-build-lxc debian sid
$ autopkgtest . -- lxc --sudo autopkgtest-sid

Regards,

--
Gioele Barabucci

Processed: Bug#1020083 marked as pending in fastapi

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1020083 [src:fastapi] fastapi: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p 3.10 returned exit code 13
Added tag(s) pending.

-- 
1020083: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020083
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1020083: marked as pending in fastapi

[Sandro Tosi]

Control: tag -1 pending

Hello,

Bug #1020083 in fastapi 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/fastapi/-/commit/31c96d2db7808e32d13c1086226500e4ed5ca513


New upstream release; Closes: #1020083


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1020083

Bug#1020442: marked as done (heimdal breaks openldap autopkgtest: test smbk5pwd)

[Debian Bug Tracking System]

Your message dated Wed, 28 Sep 2022 02:37:48 +
with message-id 
and subject line Bug#1020442: fixed in openldap 2.5.13+dfsg-2
has caused the Debian Bug report #1020442,
regarding heimdal breaks openldap autopkgtest: test smbk5pwd
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.)


-- 
1020442: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020442
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Source: heimdal, openldap
Control: found -1 heimdal/7.7.0+dfsg-6
Control: found -1 openldap/2.5.12+dfsg-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of heimdal the autopkgtest of openldap fails in 
testing when that autopkgtest is run with the binary packages of heimdal 
from unstable. It passes when run with only packages from testing (I 
note that the test in  unstable with the new version of openldap is also 
broken with seemingly the same output). In tabular form:


   passfail
heimdalfrom testing7.7.0+dfsg-6
openldap   from testing2.5.12+dfsg-2
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of heimdal to 
testing [1]. Due to the nature of this issue, I filed this bug report 
against both packages. Can you please investigate the situation and 
reassign the bug to the right package?


More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=heimdal

https://ci.debian.net/data/autopkgtest/testing/amd64/o/openldap/26275057/log.gz

SASL/EXTERNAL authentication started
SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth
SASL SSF: 0
adding new entry "cn=samba,cn=schema,cn=config"

SASL/EXTERNAL authentication started
SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth
SASL SSF: 0
adding new entry "cn=hdb,cn=schema,cn=config"

SASL/EXTERNAL authentication started
SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth
SASL SSF: 0
ldap_add: Other (e.g., implementation specific) error (80)
additional info:  handler exited with 1
modifying entry "cn=module{0},cn=config"

adding new entry "olcOverlay=smbk5pwd,olcDatabase={1}mdb,cn=config"

autopkgtest [00:24:46]: test smbk5pwd



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: openldap
Source-Version: 2.5.13+dfsg-2
Done: Ryan Tandy 

We believe that the bug you reported is fixed in the latest version of
openldap, 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 1020...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ryan Tandy  (supplier of updated openldap package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 24 Sep 2022 12:40:21 -0700
Source: openldap
Architecture: source
Version: 2.5.13+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenLDAP Maintainers 

Changed-By: Ryan Tandy 
Closes: 1020442
Changes:
 openldap (2.5.13+dfsg-2) unstable; urgency=medium
 .
   * d/tests/smbk5pwd: Grant slapd access to /var/lib/heimdal-kdc. Fixes the
 autopkgtest failure due to heimdal setting mode 700 on this directory.
 (Closes: #1020442)
   * d/source/lintian-overrides: Add wildcards to make overrides compatible
 with both older and newer versions of lintian.
   * d/slapd-contrib.lintian-overrides: Remove unused
 custom-library-search-path override now that krb5-config no longer sets
 -rpath.
Checksums-Sha1:
 b876fb8fcc6cd592b030a27a68d82cf66f2daf48 3224 openldap_2.5.13+dfsg-2.dsc
 a00a8c2b1946f00d79d2bb7d95746b68fce34108 164476 
openldap_2.5.13+dfsg-2.debian.tar.xz
Checksums-Sha256:
 304eb2f104e2c1986f18c14c4f3d0ddba6049aa4440f8401c903303c6943ef24 3224 
openldap_2.5.13+dfsg-2.dsc
 ca255fdc5ef77c3c9660af701331f19a0fe7dffbd625c5302746d2ace75a9656 164476 
openldap_2.5.13+dfsg-2.debian.tar.xz

Processed: cleanup dh_elpa_test bugs 10/n

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign  1020078  src:emacs-buttercup
Bug #1020078 [src:beginend-el] beginend-el: FTBFS: make: *** [debian/rules:4: 
binary] Error 25
Bug reassigned from package 'src:beginend-el' to 'src:emacs-buttercup'.
No longer marked as found in versions beginend-el/2.3.0-1.
Ignoring request to alter fixed versions of bug #1020078 to the same values 
previously set
> forcemerge 1020095 1020078
Bug #1020095 {Done: David Bremner } [src:emacs-buttercup] 
emacs-buttercup: FTBFS: make[1]: *** [Makefile:16: test-docs] Error 255
Bug #1020187 {Done: David Bremner } [src:emacs-buttercup] 
ido-ubiquitous: FTBFS: make: *** [debian/rules:4: binary] Error 25
Bug #1020095 {Done: David Bremner } [src:emacs-buttercup] 
emacs-buttercup: FTBFS: make[1]: *** [Makefile:16: test-docs] Error 255
Added tag(s) bookworm.
Added tag(s) bookworm.
Bug #1020078 [src:emacs-buttercup] beginend-el: FTBFS: make: *** 
[debian/rules:4: binary] Error 25
Marked Bug as done
Added indication that 1020078 affects ido-ubiquitous
Marked as fixed in versions emacs-buttercup/1.26-1.
Marked as found in versions emacs-buttercup/1.24-1.
Bug #1020187 {Done: David Bremner } [src:emacs-buttercup] 
ido-ubiquitous: FTBFS: make: *** [debian/rules:4: binary] Error 25
Merged 1020078 1020095 1020187
> affects   1020095 +beginend-el
Bug #1020095 {Done: David Bremner } [src:emacs-buttercup] 
emacs-buttercup: FTBFS: make[1]: *** [Makefile:16: test-docs] Error 255
Bug #1020078 {Done: David Bremner } [src:emacs-buttercup] 
beginend-el: FTBFS: make: *** [debian/rules:4: binary] Error 25
Bug #1020187 {Done: David Bremner } [src:emacs-buttercup] 
ido-ubiquitous: FTBFS: make: *** [debian/rules:4: binary] Error 25
Added indication that 1020095 affects beginend-el
Added indication that 1020078 affects beginend-el
Added indication that 1020187 affects beginend-el
> tag 1020078 -bookworm
Bug #1020078 {Done: David Bremner } [src:emacs-buttercup] 
beginend-el: FTBFS: make: *** [debian/rules:4: binary] Error 25
Bug #1020095 {Done: David Bremner } [src:emacs-buttercup] 
emacs-buttercup: FTBFS: make[1]: *** [Makefile:16: test-docs] Error 255
Bug #1020187 {Done: David Bremner } [src:emacs-buttercup] 
ido-ubiquitous: FTBFS: make: *** [debian/rules:4: binary] Error 25
Removed tag(s) bookworm.
Removed tag(s) bookworm.
Removed tag(s) bookworm.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
1020078: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020078
1020095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020095
1020187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020187
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: cleanup dh_elpa_test bugs 11/n

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign   1020167 dh-elpa
Bug #1020167 [src:seq-el] seq-el: FTBFS: make: *** [debian/rules:4: build] 
Error 25
Bug reassigned from package 'src:seq-el' to 'dh-elpa'.
No longer marked as found in versions seq-el/2.23-1.
Ignoring request to alter fixed versions of bug #1020167 to the same values 
previously set
> forcemerge 1020179 1020167
Bug #1020179 [dh-elpa] "dh_elpa_test should not cache native code in 
non-writable $HOME"
Bug #1020186 [dh-elpa] markdown-toc-el: FTBFS: make: *** [debian/rules:4: 
binary] Error 25
Bug #1020191 [dh-elpa] ebib: FTBFS: make: *** [debian/rules:4: build] Error 25
Bug #1020196 [dh-elpa] use-package: FTBFS: make: *** [debian/rules:4: binary] 
Error 25
Bug #1020203 [dh-elpa] package-lint-el: FTBFS: make: *** [debian/rules:4: 
binary] Error 25
Bug #1020204 [dh-elpa] elisp-refs: FTBFS: make: *** [debian/rules:4: binary] 
Error 25
Bug #1020210 [dh-elpa] emacs-websocket: FTBFS: make: *** [debian/rules:4: 
binary] Error 25
Bug #1020167 [dh-elpa] seq-el: FTBFS: make: *** [debian/rules:4: build] Error 25
Added indication that 1020167 affects 
paredit-everywhere,elisp-refs,markdown-toc-el,use-package,package-lint-el,elfeed,ebib,emacs-websocket
Marked as fixed in versions dh-elpa/2.0.12.
Marked as found in versions dh-elpa/2.0.11.
Bug #1020196 [dh-elpa] use-package: FTBFS: make: *** [debian/rules:4: binary] 
Error 25
Removed indication that 1020196 affects package-lint-el, emacs-websocket, 
elisp-refs, markdown-toc-el, elfeed, paredit-everywhere, use-package, and ebib
Added indication that 1020196 affects 
paredit-everywhere,elisp-refs,markdown-toc-el,use-package,package-lint-el,elfeed,ebib,emacs-websocket
Removed indication that 1020179 affects emacs-websocket, elisp-refs, 
package-lint-el, paredit-everywhere, markdown-toc-el, elfeed, use-package, and 
ebib
Added indication that 1020179 affects 
paredit-everywhere,elisp-refs,markdown-toc-el,use-package,package-lint-el,elfeed,ebib,emacs-websocket
Removed indication that 1020186 affects use-package, ebib, elisp-refs, 
emacs-websocket, package-lint-el, paredit-everywhere, elfeed, and 
markdown-toc-el
Added indication that 1020186 affects 
paredit-everywhere,elisp-refs,markdown-toc-el,use-package,package-lint-el,elfeed,ebib,emacs-websocket
Removed indication that 1020191 affects ebib, use-package, markdown-toc-el, 
elfeed, paredit-everywhere, package-lint-el, emacs-websocket, and elisp-refs
Added indication that 1020191 affects 
paredit-everywhere,elisp-refs,markdown-toc-el,use-package,package-lint-el,elfeed,ebib,emacs-websocket
Removed indication that 1020203 affects emacs-websocket, elisp-refs, 
package-lint-el, paredit-everywhere, markdown-toc-el, elfeed, use-package, and 
ebib
Added indication that 1020203 affects 
paredit-everywhere,elisp-refs,markdown-toc-el,use-package,package-lint-el,elfeed,ebib,emacs-websocket
Removed indication that 1020204 affects package-lint-el, elisp-refs, 
emacs-websocket, elfeed, markdown-toc-el, paredit-everywhere, use-package, and 
ebib
Added indication that 1020204 affects 
paredit-everywhere,elisp-refs,markdown-toc-el,use-package,package-lint-el,elfeed,ebib,emacs-websocket
Removed indication that 1020210 affects ebib, use-package, markdown-toc-el, 
elfeed, paredit-everywhere, package-lint-el, emacs-websocket, and elisp-refs
Added indication that 1020210 affects 
paredit-everywhere,elisp-refs,markdown-toc-el,use-package,package-lint-el,elfeed,ebib,emacs-websocket
Added tag(s) bookworm.
Added tag(s) bookworm.
Added tag(s) bookworm.
Added tag(s) bookworm.
Added tag(s) bookworm.
Added tag(s) bookworm.
Added tag(s) bookworm.
Bug #1020186 [dh-elpa] markdown-toc-el: FTBFS: make: *** [debian/rules:4: 
binary] Error 25
Bug #1020191 [dh-elpa] ebib: FTBFS: make: *** [debian/rules:4: build] Error 25
Bug #1020203 [dh-elpa] package-lint-el: FTBFS: make: *** [debian/rules:4: 
binary] Error 25
Bug #1020204 [dh-elpa] elisp-refs: FTBFS: make: *** [debian/rules:4: binary] 
Error 25
Bug #1020210 [dh-elpa] emacs-websocket: FTBFS: make: *** [debian/rules:4: 
binary] Error 25
Merged 1020167 1020179 1020186 1020191 1020196 1020203 1020204 1020210
> affects1020179 +seq-el
Bug #1020179 [dh-elpa] "dh_elpa_test should not cache native code in 
non-writable $HOME"
Bug #1020167 [dh-elpa] seq-el: FTBFS: make: *** [debian/rules:4: build] Error 25
Bug #1020186 [dh-elpa] markdown-toc-el: FTBFS: make: *** [debian/rules:4: 
binary] Error 25
Bug #1020191 [dh-elpa] ebib: FTBFS: make: *** [debian/rules:4: build] Error 25
Bug #1020196 [dh-elpa] use-package: FTBFS: make: *** [debian/rules:4: binary] 
Error 25
Bug #1020203 [dh-elpa] package-lint-el: FTBFS: make: *** [debian/rules:4: 
binary] Error 25
Bug #1020204 [dh-elpa] elisp-refs: FTBFS: make: *** [debian/rules:4: binary] 
Error 25
Bug #1020210 [dh-elpa] emacs-websocket: FTBFS: make: *** [debian/rules:4: 
binary] Error 25
Added indication that 1020179 affects seq-el
Added indication that 1020167 affects seq-el
Added indication that 

Bug#1020189: still failing with dh-elpa 2.0.12

[David Bremner]

This looks like a real bug though, unrelated to native compilation

Searched 1/1 files
   passed  19/87  helpful--display-implementations (0.122235 sec)
   passed  20/87  helpful--docstring (0.44 sec)
Test helpful--docstring-advice backtrace:
  signal(ert-test-failed (((should (equal (helpful--docstring #'test-f
  ert-fail(((should (equal (helpful--docstring #'test-foo-advised t) "
  (if (unwind-protect (setq value-47 (apply fn-45 args-46)) (setq form
  (let (form-description-49) (if (unwind-protect (setq value-47 (apply
  (let ((value-47 'ert-form-evaluation-aborted-48)) (let (form-descrip
  (let* ((fn-45 #'equal) (args-46 (condition-case err (let ((signal-ho
  (let ((lexical-binding t)) (let* ((fn-45 #'equal) (args-46 (conditio
  (closure (t) nil (let ((lexical-binding t)) (let* ((fn-45 #'equal) (
  ert--run-test-internal(#s(ert--test-execution-info :test #s(ert-test
  ert-run-test(#s(ert-test :name helpful--docstring-advice :documentat
  ert-run-or-rerun-test(#s(ert--stats :selector t :tests ... :test-map
  ert-run-tests(t #f(compiled-function (event-type  event-args) #
  ert-run-tests-batch(nil)
  ert-run-tests-batch-and-exit()
  command-line-1(("-l" "package" "--eval" "(setq native-compile-target
  command-line()
  normal-top-level()
Test helpful--docstring-advice condition:
(ert-test-failed
 ((should
   (equal
(helpful--docstring ... t)
"Docstring here too."))
  :form
  (equal "Docstring here too.\n\nThis function has :around advice: 
`ad-Advice-test-foo-advised'." "Docstring here too.")
  :value nil :explanation
  (arrays-of-different-length 84 19 "Docstring here too.\n\nThis function 
has :around advice: `ad-Advice-test-foo-advised'." "Docstring here too." 
first-mismatch-at 19)))
   FAILED  21/87  helpful--docstring-advice (0.000165 sec)
   passed  22/87  helpful--docstring-keymap (0.000490 sec)

Bug#1020885: libshumate-1.0-1: move pkg-config file to the -dev package

[Paul Wise]

Package: libshumate-1.0-1
Version: 1.0.1-1
Control: found -1 1.0.0~alpha.1-1
Severity: serious
File: /usr/lib/x86_64-linux-gnu/pkgconfig/shumate-1.0.pc
User: debian...@lists.debian.org
Usertags: adequate missing-pkgconfig-dependency

The shumate-1.0.pc file should be moved from the libshumate-1.0-1 package to 
the 
libshumate-dev package, since the shumate-1.0.pc is only used at compile time.

This issue has been present since version 1.0.0~alpha.1-1 according to
the binary packages available on the snapshot.debian.org service.

 from the release team advised me on #debian-gnome that this
issue represents a serious issue, hence the severity above.

This issue was detected by adequate, hence the usertags above.

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
merged-usr: no
Architecture: amd64 (x86_64)

Kernel: Linux 5.19.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libshumate-1.0-1 depends on:
ii  libc62.34-8
ii  libcairo21.16.0-6
ii  libgdk-pixbuf-2.0-0  2.42.9+dfsg-1
ii  libglib2.0-0 2.74.0-1
ii  libgraphene-1.0-01.10.8-1
ii  libgtk-4-1   4.8.1+ds-1
ii  libshumate-common1.0.1-1
ii  libsoup-3.0-03.2.0-1
ii  libsqlite3-0 3.39.3-1

libshumate-1.0-1 recommends no packages.

libshumate-1.0-1 suggests no packages.

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part

Processed: libshumate-1.0-1: move pkg-config file to the -dev package

[Debian Bug Tracking System]

Processing control commands:

> found -1 1.0.0~alpha.1-1
Bug #1020885 [libshumate-1.0-1] libshumate-1.0-1: move pkg-config file to the 
-dev package
Marked as found in versions libshumate/1.0.0~alpha.1-1.

-- 
1020885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020885
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1017137: marked as done (newsboat: FTBFS: ./3rd-party/catch.hpp:10830:58: error: call to non-‘constexpr’ function ‘long int sysconf(int)’)

[Debian Bug Tracking System]

Your message dated Tue, 27 Sep 2022 21:24:15 +
with message-id 
and subject line Bug#1017137: fixed in newsboat 2.21-1.4
has caused the Debian Bug report #1017137,
regarding newsboat: FTBFS: ./3rd-party/catch.hpp:10830:58: error: call to 
non-‘constexpr’ function ‘long int sysconf(int)’
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.)


-- 
1017137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017137
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: newsboat
Version: 2.21-1.3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220813 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> g++ -std=c++11 -O2 -ggdb -Iinclude -Istfl -Ifilter -I. -Irss -Werror -Wall 
> -Wextra -Wunreachable-code -DLOCALEDIR=\"/usr/local/share/locale\" 
> -I/usr/include/x86_64-linux-gnu -I/usr/include/libxml2 -I/usr/include/json-c 
> -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -o test/utils.o -c 
> test/utils.cpp
> In file included from /usr/include/signal.h:328,
>  from ./3rd-party/catch.hpp:8042,
>  from test/test.cpp:2:
> ./3rd-party/catch.hpp:10830:58: error: call to non-‘constexpr’ function ‘long 
> int sysconf(int)’
> 10830 | static constexpr std::size_t sigStackSize = 32768 >= MINSIGSTKSZ 
> ? 32768 : MINSIGSTKSZ;
>   |  ^~~
> In file included from /usr/include/x86_64-linux-gnu/bits/sigstksz.h:24:
> /usr/include/unistd.h:640:17: note: ‘long int sysconf(int)’ declared here
>   640 | extern long int sysconf (int __name) __THROW;
>   | ^~~
> ./3rd-party/catch.hpp:10889:45: error: size of array ‘altStackMem’ is not an 
> integral constant-expression
> 10889 | char FatalConditionHandler::altStackMem[sigStackSize] = {};
>   | ^~~~
> g++ -std=c++11 -O2 -ggdb -Iinclude -Istfl -Ifilter -I. -Irss -Werror -Wall 
> -Wextra -Wunreachable-code -DLOCALEDIR=\"/usr/local/share/locale\" 
> -I/usr/include/x86_64-linux-gnu -I/usr/include/libxml2 -I/usr/include/json-c 
> -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -o 
> test/test-helpers/chdir.o -c test/test-helpers/chdir.cpp
> g++ -std=c++11 -O2 -ggdb -Iinclude -Istfl -Ifilter -I. -Irss -Werror -Wall 
> -Wextra -Wunreachable-code -DLOCALEDIR=\"/usr/local/share/locale\" 
> -I/usr/include/x86_64-linux-gnu -I/usr/include/libxml2 -I/usr/include/json-c 
> -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -o 
> test/test-helpers/chmod.o -c test/test-helpers/chmod.cpp
> g++ -std=c++11 -O2 -ggdb -Iinclude -Istfl -Ifilter -I. -Irss -Werror -Wall 
> -Wextra -Wunreachable-code -DLOCALEDIR=\"/usr/local/share/locale\" 
> -I/usr/include/x86_64-linux-gnu -I/usr/include/libxml2 -I/usr/include/json-c 
> -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -o 
> test/test-helpers/envvar.o -c test/test-helpers/envvar.cpp
> g++ -std=c++11 -O2 -ggdb -Iinclude -Istfl -Ifilter -I. -Irss -Werror -Wall 
> -Wextra -Wunreachable-code -DLOCALEDIR=\"/usr/local/share/locale\" 
> -I/usr/include/x86_64-linux-gnu -I/usr/include/libxml2 -I/usr/include/json-c 
> -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -o 
> test/test-helpers/loggerresetter.o -c test/test-helpers/loggerresetter.cpp
> g++ -std=c++11 -O2 -ggdb -Iinclude -Istfl -Ifilter -I. -Irss -Werror -Wall 
> -Wextra -Wunreachable-code -DLOCALEDIR=\"/usr/local/share/locale\" 
> -I/usr/include/x86_64-linux-gnu -I/usr/include/libxml2 -I/usr/include/json-c 
> -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -o 
> test/test-helpers/maintempdir.o -c test/test-helpers/maintempdir.cpp
> g++ -std=c++11 -O2 -ggdb -Iinclude -Istfl -Ifilter -I. -Irss -Werror -Wall 
> -Wextra -Wunreachable-code -DLOCALEDIR=\"/usr/local/share/locale\" 
> 

Bug#1020837: marked as done (gajim: Dependency to gtk 3.24.30 not available in backports)

[Debian Bug Tracking System]

Your message dated Tue, 27 Sep 2022 21:13:14 +
with message-id <87leq4v7oe@fama.lan>
and subject line Re: Bug#1020837: gajim: Dependency to gtk 3.24.30 not 
available in backports
has caused the Debian Bug report #1020837,
regarding gajim: Dependency to gtk 3.24.30 not available in backports
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.)


-- 
1020837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020837
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gajim
Version: 1.5.1-1~bpo11+1
Severity: grave
Tags: a11y
Justification: renders package unusable
X-Debbugs-Cc: cle...@zaclys.net

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
I installed gajim 1.5.1 from debian bullseye backports
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
After installing the package, it dit not launch from de desktop. When i tried 
from the console I got an error regarding the dependency to gkt3 3.24.30.
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: 11.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-18-amd64 (SMP w/4 CPU threads)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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 gajim depends on:
ii  desktop-file-utils   0.26-1
ii  gir1.2-gst-plugins-base-1.0  1.18.4-2
ii  gir1.2-gtk-3.0   3.24.24-4+deb11u2
ii  gir1.2-gtksource-4   4.8.0-1
ii  python3  3.9.2-3
ii  python3-cairo1.16.2-4+b2
ii  python3-css-parser   1.0.6-1
ii  python3-gi   3.42.2-2~bpo11+1
ii  python3-gi-cairo 3.42.2-2~bpo11+1
ii  python3-idna 2.10-1
ii  python3-keyring  22.0.1-1
ii  python3-nbxmpp   3.2.2-1~bpo11+1
ii  python3-openssl  20.0.1-1
ii  python3-packaging20.9-2
ii  python3-pil  8.1.2+dfsg-0.3+deb11u1
ii  python3-precis-i18n  1.0.2-3

Versions of packages gajim recommends:
ii  alsa-utils 1.2.4-1
ii  aspell-en [aspell-dictionary]  2018.04.16-0-1
ii  aspell-fr [aspell-dictionary]  0.50-3-8.1
ii  ca-certificates20210119
ii  dbus   1.12.20-2
ii  fonts-noto-color-emoji 0~20200916-1
ii  gajim-omemo2.8.15-1~bpo11+1
ii  gajim-openpgp  1.4.9-1~bpo11+1
ii  gir1.2-farstream-0.2   0.2.9-1
ii  gir1.2-geoclue-2.0 2.5.7-3
ii  gir1.2-gsound-1.0  1.0.2-5
ii  gir1.2-gspell-11.8.4-1
ii  gir1.2-gstreamer-1.0   1.18.4-2.1
ii  gir1.2-gupnpigd-1.01.2.0-1
ii  gir1.2-secret-10.20.4-2
ii  gnome-shell [notification-daemon]  3.38.6-1~deb11u1
ii  gstreamer1.0-plugins-ugly  1.18.4-2
ii  notification-daemon3.20.0-4
ii  pulseaudio-utils   14.2-2
ii  python3-dbus   1.2.16-5
ii  python3-sentry-sdk 0.13.2-1

Versions of packages gajim suggests:
ii  libxss1  1:1.2.3-1
pn  nautilus-sendto  

-- no debconf information
--- End Message ---
--- Begin Message ---
Unfortunately, I had to revert to 1.4.7.
The GTK+ dependency was not to workaround.
If there is ever a bullseye-backport of GTK+, I'll upgrade Gajim, too.
Sorry!--- End Message ---

Bug#1020837: gajim: Dependency to gtk 3.24.30 not available in backports

[Martin]

Unfortunately, I had to revert to 1.4.7.
The GTK+ dependency was not to workaround.
If there is ever a bullseye-backport of GTK+, I'll upgrade Gajim, too.
Sorry!

Bug#943237: marked as done (telepathy-rakia: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 27 Sep 2022 20:58:20 +
with message-id 
and subject line Bug#943237: fixed in telepathy-rakia 0.8.0-4.1
has caused the Debian Bug report #943237,
regarding telepathy-rakia: Python2 removal in sid/bullseye
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.)


-- 
943237: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943237
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: telepathy-rakia
Version: 0.8.0-3
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests (the specific reason can be found searching this
source package in
https://people.debian.org/~morph/mass-bug-py2removal_take2.txt ).
Please stop using Python2, and fix this issue by one of the following
actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: telepathy-rakia
Source-Version: 0.8.0-4.1
Done: Adrian Bunk 

We believe that the bug you reported is fixed in the latest version of
telepathy-rakia, 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 943...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated telepathy-rakia 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, 13 Sep 2022 22:16:31 +0300
Source: telepathy-rakia
Architecture: source
Version: 0.8.0-4.1
Distribution: unstable
Urgency: low
Maintainer: Debian Telepathy maintainers 

Changed-By: Adrian Bunk 
Closes: 943237
Changes:
 telepathy-rakia (0.8.0-4.1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Add proposed patch for building with Python 3. (Closes: #943237)
Checksums-Sha1:
 d74b626cbc6e58aa23b2f31dccb9e4dc70b3aeb8 2266 telepathy-rakia_0.8.0-4.1.dsc
 d41ad9c5c2a75d3192d020843c2f1cbf989cbf2d 6856 
telepathy-rakia_0.8.0-4.1.debian.tar.xz
Checksums-Sha256:
 20676774c89fc625b4bcac32fe3ef1118f3eb5d2dac81282f7868e92947d8963 2266 
telepathy-rakia_0.8.0-4.1.dsc
 3fd784b16a5dcaed8787478c0a9e2ab782dbbe49cc3346da3be84e8784679bd9 6856 
telepathy-rakia_0.8.0-4.1.debian.tar.xz
Files:
 b74c97ebbaae85ea9e4385f59f8edd1e 2266 net optional 
telepathy-rakia_0.8.0-4.1.dsc
 a2349bba1b8caa849d969238ed670b52 6856 net optional 
telepathy-rakia_0.8.0-4.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmMg19sACgkQiNJCh6LY

Processed: oh oh, try again setting the version…

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> notfound 1020592 odejs/18.7.0+dfsg-5
Bug #1020592 [nodejs] nodejs: Testsuite is using smoil keys
The source odejs and version 18.7.0+dfsg-5 do not appear to match any binary 
packages
No longer marked as found in versions odejs/18.7.0+dfsg-5.
> notfound 1020592 8.7.0+dfsg-5
Bug #1020592 [nodejs] nodejs: Testsuite is using smoil keys
There is no source info for the package 'nodejs' at version '8.7.0+dfsg-5' with 
architecture ''
Unable to make a source version for version '8.7.0+dfsg-5'
No longer marked as found in versions 8.7.0+dfsg-5.
> found 1020592 18.7.0+dfsg-5
Bug #1020592 [nodejs] nodejs: Testsuite is using smoil keys
Marked as found in versions nodejs/18.7.0+dfsg-5.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
1020592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020592
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: fixed 1020569 in 5.10.0-2

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> fixed 1020569 5.10.0-2
Bug #1020569 {Done: Thomas Goirand } [src:python-pbr] 
python-pbr's autopkg tests fail with setuptools 65
Marked as fixed in versions python-pbr/5.10.0-2.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1020569: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020569
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1020776: qemu-system-data in bullseye-backports is too old

[Michael Tokarev]

On 26.09.2022 17:39, Justin Ossevoort wrote:

Package: qemu-system-data
Version: 1:5.2+dfsg-11+deb11u2
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: deb...@internetionals.nl

Dear Maintainer,

The latest packages in Debian Bullseye Backports depend on

qemu-system-data (>> 1:7.1+dfsg~)

But the current version in the Debian APT archives (and according to
https://packages.debian.org/bullseye-backports/qemu-system-data) is:

qemu-system-data (1:7.0+dfsg-2~bpo11+2)


the current q-s-d hasn't been built - that's why it can't be installed.

As Diederik correctly noted, this is because of the wrong dependency on
gcc-alpha which does not exist on bullseye. Apparently I forgot to re-
generate d/control in +bpo11+2 upload so the change didn't propagate
to it, keeping q-s-d unbuildable.

I'll fix this (with a 3-char change in d/control) when I'll return,
hopefully next week.

/mjt

Processed: forcibly merging 1019579 1019687

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 1019579 1019687
Bug #1019579 {Done: Dominique Dumont } [dh-raku] Missing 
pre-compiled file in dependency packages lead to 'trying to overwrite file' 
errors
Bug #1019687 [dh-raku] raku-meta6: trying to overwrite 
'/usr/lib/perl6/vendor/precomp/A234FA60C249CF61DEFEC1FD7D434DF2D0D597D5/0F/0F5CCC81E3EDCF1EE7139F2E5E72A089F34C3091',
 which is also in package raku-license-spdx 3.17.0-1
Marked Bug as done
Removed indication that 1019687 affects raku-license-spdx and raku-meta6
Added indication that 1019687 affects 
raku-json-marshal,raku-json-unmarshal,src:raku-json-class
Marked as fixed in versions dh-raku/0.13.
Added tag(s) ftbfs.
Merged 1019579 1019687
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1019579: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019579
1019687: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019687
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1019388: Acknowledgement (apt-clone: Fails to run - no /usr/bin/dpkg-repack found)

[Boyuan Yang]

X-Debbugs-CC: baronr...@gmail.com
Control: severity -1 wishlist

On Thu, 8 Sep 2022 12:35:38 -0400 Rann Bar-On  wrote:
> Fixed by installing dpkg-repack. So maybe this is just a dependency issue?

Package apt-clone Recommends: dpkg-repack. Are you installing apt-clone with
--no-install-recommends? This is not the default behavior and highly
discouraged. You will need to find the solution by yourself like in this
case.

That being said, having a better elaboration that dpkg-repack need to be
installed could be better. Thus I am downgrading the severity to wishlist.

Thanks,
Boyuan Yang


signature.asc
Description: This is a digitally signed message part

Processed: Re: Bug#1019388: Acknowledgement (apt-clone: Fails to run - no /usr/bin/dpkg-repack found)

[Debian Bug Tracking System]

Processing control commands:

> severity -1 wishlist
Bug #1019388 [apt-clone] apt-clone: Fails to run - no /usr/bin/dpkg-repack found
Severity set to 'wishlist' from 'grave'

-- 
1019388: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019388
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1019993: marked as done (python-django-crispy-forms: FTBFS: ModuleNotFoundError: No module named 'setuptools')

[Debian Bug Tracking System]

Your message dated Tue, 27 Sep 2022 17:36:23 +
with message-id 
and subject line Bug#1019993: fixed in python-django-crispy-forms 1.14.0-2
has caused the Debian Bug report #1019993,
regarding python-django-crispy-forms: FTBFS: ModuleNotFoundError: No module 
named 'setuptools'
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.)


-- 
1019993: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019993
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-django-crispy-forms
Version: 1.14.0-1
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.


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with=python3,sphinxdoc --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild plugin_pyproject:107: Building wheel for python3.10 with "build" 
> module
> I: pybuild base:240: python3.10 -m build --skip-dependency-check 
> --no-isolation --wheel --outdir 
> /<>/.pybuild/cpython3_3.10_django-crispy-forms 
> * Building wheel...
> 
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/pep517/wrappers.py", line 332, in 
> _call_hook
> raise BackendUnavailable(data.get('traceback', ''))
> pep517.wrappers.BackendUnavailable: Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/pep517/in_process/_in_process.py", 
> line 89, in _build_backend
> obj = import_module(mod_path)
>   File "/usr/lib/python3.10/importlib/__init__.py", line 126, in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
>   File "", line 1050, in _gcd_import
>   File "", line 1027, in _find_and_load
>   File "", line 992, in _find_and_load_unlocked
>   File "", line 241, in _call_with_frames_removed
>   File "", line 1050, in _gcd_import
>   File "", line 1027, in _find_and_load
>   File "", line 1004, in _find_and_load_unlocked
> ModuleNotFoundError: No module named 'setuptools'
> 
> ERROR Backend 'setuptools.build_meta:__legacy__' is not available.
> E: pybuild pybuild:379: build: plugin pyproject failed with: exit code=1: 
> python3.10 -m build --skip-dependency-check --no-isolation --wheel --outdir 
> /<>/.pybuild/cpython3_3.10_django-crispy-forms 
> dh_auto_build: error: pybuild --build -i python{version} -p 3.10 returned 
> exit code 13
> make: *** [debian/rules:9: binary] Error 25


The full build log is available from:
http://qa-logs.debian.net/2022/09/17/python-django-crispy-forms_1.14.0-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220917;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220917=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 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-django-crispy-forms
Source-Version: 1.14.0-2
Done: Carsten Schoenert 

We believe that the bug you reported is fixed in the latest version of
python-django-crispy-forms, 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 1019...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Carsten Schoenert  (supplier of updated 
python-django-crispy-forms 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, 27 Sep 2022 19:06:36 +0200
Source: python-django-crispy-forms
Architecture: source
Version: 1.14.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 

Bug#1020047: marked as done (jzmq: FTBFS: Event.cpp:5:10: fatal error: zmq.hpp: No such file or directory)

[Debian Bug Tracking System]

Your message dated Tue, 27 Sep 2022 17:20:02 +
with message-id 
and subject line Bug#1020047: fixed in jzmq 3.1.0-16
has caused the Debian Bug report #1020047,
regarding jzmq: FTBFS: Event.cpp:5:10: fatal error: zmq.hpp: 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.)


-- 
1020047: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020047
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jzmq
Version: 3.1.0-15.1
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.


Relevant part (hopefully):
> /bin/bash ../../../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H 
> -I.   -D_REENTRANT -D_THREAD_SAFE -Wdate-time -D_FORTIFY_SOURCE=2 -isystem 
> /usr/include/mit-krb5 -I/usr/include/pgm-5.3 -I/usr/include/libxml2 
> -I/usr/lib/jvm/java-11-openjdk-amd64/include 
> -I/usr/lib/jvm/java-11-openjdk-amd64/include/linux -Wall -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -c -o libjzmq_la-Event.lo `test -f 'Event.cpp' || 
> echo './'`Event.cpp
> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -D_REENTRANT -D_THREAD_SAFE 
> -Wdate-time -D_FORTIFY_SOURCE=2 -isystem /usr/include/mit-krb5 
> -I/usr/include/pgm-5.3 -I/usr/include/libxml2 
> -I/usr/lib/jvm/java-11-openjdk-amd64/include 
> -I/usr/lib/jvm/java-11-openjdk-amd64/include/linux -Wall -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -c Event.cpp  -fPIC -DPIC -o .libs/libjzmq_la-Event.o
> Event.cpp:5:10: fatal error: zmq.hpp: No such file or directory
> 5 | #include 
>   |  ^
> compilation terminated.
> make[3]: *** [Makefile:595: libjzmq_la-Event.lo] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/09/17/jzmq_3.1.0-15.1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220917;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220917=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 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: jzmq
Source-Version: 3.1.0-16
Done: Jan Niehusmann 

We believe that the bug you reported is fixed in the latest version of
jzmq, 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 1020...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jan Niehusmann  (supplier of updated jzmq 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, 27 Sep 2022 18:59:17 +0200
Source: jzmq
Architecture: source
Version: 3.1.0-16
Distribution: unstable
Urgency: medium
Maintainer: Jan Niehusmann 
Changed-By: Jan Niehusmann 
Closes: 1020047
Changes:
 jzmq (3.1.0-16) unstable; urgency=medium
 .
   * Add dependency on cppzmq-dev to fix broken build caused by
 change in zeromq3 (in fix for #972785).
 (Closes: #1020047)
Checksums-Sha1:
 cf523f4c5324e9157d622153706990a05e7bcd5f 1998 jzmq_3.1.0-16.dsc
 697d4f42538089e4084799cb064afc4d6243a080 4716 jzmq_3.1.0-16.debian.tar.xz
 e2b8cb01c78e15d4b59c35c60624e91ee4889b9b 11436 jzmq_3.1.0-16_amd64.buildinfo
Checksums-Sha256:
 1d533da2ddd7e2edb0303149e82b31078fe21bfbdeb605834fc0d539b4c90ce1 1998 
jzmq_3.1.0-16.dsc
 01a388940d914ae2205feb8080868a2cfafc8b582c3037ba54c6438ea1524028 4716 
jzmq_3.1.0-16.debian.tar.xz
 1ccad4ab4709df644fa5fea18ff2637be1361d9b4c33ed523698f048902a4dde 11436 
jzmq_3.1.0-16_amd64.buildinfo
Files:
 aa70e2b81fb52ebfae8b9e8e29525e6f 1998 java optional jzmq_3.1.0-16.dsc
 99ccef03b0e3e8178c62b50b947793a2 4716 

Bug#1020207: marked as done (debian-reference: FTBFS: mv: cannot stat 'po/templates.pot.new': No such file or directory)

[Debian Bug Tracking System]

Your message dated Tue, 27 Sep 2022 16:04:14 +
with message-id 
and subject line Bug#1020207: fixed in debian-reference 2.94
has caused the Debian Bug report #1020207,
regarding debian-reference: FTBFS: mv: cannot stat 'po/templates.pot.new': 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.)


-- 
1020207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020207
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: debian-reference
Version: 2.93
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.


Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> rm -rf /<>/build/images
> mkdir -p /<>/build/images
> #echo rawxml/00_bookinfo.rawxml rawxml/00_preface.rawxml 
> rawxml/01_gnu_linux_tutorials.rawxml 
> rawxml/02_debian_package_management.rawxml 
> rawxml/03_the_system_initialization.rawxml rawxml/04_authentication.rawxml 
> rawxml/05_network_setup.rawxml rawxml/06_network_applications.rawxml 
> rawxml/07_gui_system.rawxml rawxml/08_i18n_and_l10n.rawxml 
> rawxml/09_system_tips.rawxml rawxml/10_data_management.rawxml 
> rawxml/11_data_conversion.rawxml rawxml/12_programming.rawxml 
> rawxml/90_appendix.rawxml
> cp -f xslt/debian-reference.css /<>/build/debian-reference.css
> cd rawxml ; ./merge.sh
> echo ""   
> >  common.ent
> + echo 
> + echo  "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd;>
> + echo 
> + cat 00_bookinfo.rawxml
> + cat 00_preface.rawxml
> echo "AddCharset UTF-8 .txt" > /<>/build/.htaccess
> + cat 01_gnu_linux_tutorials.rawxml
> echo ""  >> common.ent
> #cd /usr/share/xml/docbook/stylesheet/nwalsh/images ; cp caution.png home.png 
> important.png next.png note.png prev.png tip.png up.gif warning.png 
> /<>/build/images
> mkdir -p /<>/build
> + cat 02_debian_package_management.rawxml
> echo ""   >> common.ent
> cd /usr/share/xml/docbook/stylesheet/nwalsh/images ; cp caution.png 
> important.png note.png tip.png up.gif warning.png 
> /<>/build/images
> echo "">> common.ent
> cd /<>/build; \
> xelatex ../nopdf.tex
> echo "">> common.ent
> + cat 03_the_system_initialization.rawxml
> echo ""   >> common.ent
> cd png ; cp home.png next.png prev.png /<>/build/images
> echo ""   >> common.ent
> echo "" >> common.ent
> echo "" >> common.ent
> echo "">> common.ent
> echo ""  >> common.ent
> echo ""   >> common.ent
> echo "stable)\">"  
> >> common.ent
> echo "testing)\">" 
> >> common.ent
> + cat 04_authentication.rawxml
> + cat 05_network_setup.rawxml
> + cat 06_network_applications.rawxml
> + cat 07_gui_system.rawxml
> + cat 08_i18n_and_l10n.rawxml
> + cat 09_system_tips.rawxml
> + cat 10_data_management.rawxml
> + cat 11_data_conversion.rawxml
> + cat 12_programming.rawxml
> + cat 90_appendix.rawxml
> + echo 
> cat rawxml/header1.rawxml >  rawxml/header.rawxml
> xsltproc --novalid --nonet xslt/urls.xsl rawxml/debian-reference.rawxml | 
> sort | uniq |\
> sed -e "s/&/\/g"   |  fgrep -v -e '' >> rawxml/header.rawxml
> This is XeTeX, Version 3.141592653-2.6-0.94 (TeX Live 2022/Debian) 
> (preloaded format=xelatex)
>  restricted \write18 enabled.
> cat rawxml/header2.rawxml >> rawxml/header.rawxml
> # GENERATE debian-reference.en.xmlt (TEMPLATE to avoid bloated PO/POT files)
> # Note: tablet.xsl with tailing "t"
> xsltproc --novalid --nonet xslt/tablet.xsl rawxml/debian-reference.rawxml |\
> bin/colspec.py  |\
> sed -e '/ sed -e 's/@-@amp@-@/\&/g' -e 's/@-@\([^@]\+\)@-@/\&\1;/g' > 
> debian-reference.en.xmlt
> xsltproc --novalid --nonet xslt/table.xsl rawxml/debian-reference.rawxml |\
> bin/colspec.py  |\
> sed -e '/ sed -e 's/@-@amp@-@/\&/g' -e 's/@-@\([^@]\+\)@-@/\&\1;/g' > 
> debian-reference.en.xml
> entering extended mode
> (../nopdf.tex
> LaTeX2e <2022-06-01> patch level 5
> L3 programming layer <2022-07-15>
> (/usr/share/texlive/texmf-dist/tex/latex/base/report.cls
> Document Class: report 2021/10/04 v1.4n Standard LaTeX document class
> (/usr/share/texlive/texmf-dist/tex/latex/base/size10.clopo4a-gettextize -M 
> utf-8 -L utf-8 --format docbook -m debian-reference.en.xmlt | \
> sed -e 's,^"Content-Type: text/plain; charset=CHARSET\\n"$,"Content-Type: 
> text/plain; charset=UTF-8\\n",' |\
> msgcat --no-location -o po/templates.pot.new -
> mkdir -p /<>/build
> mkdir -p /<>/build
> /usr/bin/faketime 

Bug#1020851: elpa-ement: fails to install along emacs

[Andreas Beckmann]

Package: elpa-ement
Version: 0.1.4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

This is the failure when installing the package along emacs 27 in bookworm.
(In sid there is currently a different error that is likely caused by
emacs 28 and hides this problem.)

>From the attached log (scroll to the bottom...):

  Setting up elpa-ement (0.1.4-1) ...
  Install elpa-magit-section for emacs
  install/magit-section-3.3.0: Handling install of emacsen flavor emacs
  install/magit-section-3.3.0: byte-compiling for emacs
  Install emacsen-common for emacs
  emacsen-common: Handling install of emacsen flavor emacs
  Install elpa-svg-lib for emacs
  install/svg-lib-0.2.5: Handling install of emacsen flavor emacs
  install/svg-lib-0.2.5: byte-compiling for emacs
  Install elpa-taxy for emacs
  install/taxy-0.10: Handling install of emacsen flavor emacs
  install/taxy-0.10: byte-compiling for emacs
  Install elpa-plz for emacs
  install/plz-0.2: Handling install of emacsen flavor emacs
  install/plz-0.2: byte-compiling for emacs
  Install elpa-taxy-magit-section for emacs
  install/taxy-magit-section-0.9.1: Handling install of emacsen flavor emacs
  install/taxy-magit-section-0.9.1: byte-compiling for emacs
  Install elpa-ement for emacs
  install/ement-0.1.4: Handling install of emacsen flavor emacs
  install/ement-0.1.4: byte-compiling for emacs
  
  In ement--xml-escape-string:
  ement-lib.el:1113:8:Warning: xml-escape-string called with 2 arguments, but
  accepts only 1
  
  In end of data:
  ement-lib.el:1227:1:Warning: the following functions are not known to be
  defined: color-dark-p, button-buttonize
  
  In toplevel form:
  ement-notify.el:34:1:Error: Cannot open load file: No such file or directory, 
transient
  
  In toplevel form:
  ement-room-list.el:48:1:Error: Cannot open load file: No such file or 
directory, transient
  
  In toplevel form:
  ement-room.el:2443:1:Warning: Unused lexical variable `room-buffer'
  ement-room.el:4084:1:Error: Cannot open load file: No such file or directory, 
transient
  
  In toplevel form:
  ement-taxy.el:34:1:Error: Cannot open load file: No such file or directory, 
transient
  
  In toplevel form:
  ement.el:62:1:Error: Cannot open load file: No such file or directory, 
transient
  ERROR: install script from elpa-ement package failed
  dpkg: error processing package elpa-ement (--configure):
   installed elpa-ement package post-installation script subprocess returned 
error exit status 1
  Processing triggers for install-info (6.8-6) ...
  Errors were encountered while processing:
   elpa-ement


cheers,

Andreas


elpa-ement=0.1.4-1_emacs.log.gz
Description: application/gzip

Processed: Bug#1019995 marked as pending in supercollider

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1019995 [src:supercollider] supercollider: FTBFS: sndfile.h:356:33: error: 
conflicting declaration ‘typedef struct sf_private_tag SNDFILE’
Added tag(s) pending.

-- 
1019995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019995
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1019995: marked as pending in supercollider

[Dennis Braun]

Control: tag -1 pending

Hello,

Bug #1019995 in supercollider 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/multimedia-team/supercollider/-/commit/0338ed3f9d8cba2b17fc8e155b8e27b8916d2168


Use macro instead of redefining struct (Closes: #1019995)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1019995

Bug#1020568: marked as done (pocketsphinx-python's autopkg tests fail with setuptools 65)

[Debian Bug Tracking System]

Your message dated Tue, 27 Sep 2022 14:40:56 +
with message-id 
and subject line Bug#1020568: fixed in pocketsphinx-python 1:0.1.15-3
has caused the Debian Bug report #1020568,
regarding pocketsphinx-python's autopkg tests fail with setuptools 65
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.)


-- 
1020568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020568
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: src:pocketsphinx-python
Version: 1:0.1.15-2
Severity: serious
Tags: sid bookworm

https://ci.debian.net/data/autopkgtest/testing/amd64/p/pocketsphinx-python/26322074/log.gz

[...]
autopkgtest [07:48:02]: test tests: [---
patching file setup.py
  configure with PYTHON 3.10 ==
/tmp/autopkgtest-lxc.wiu8e7yd/downtmp/build.lPV/src/setup.py:7: 
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 import log
/usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning: 
Distutils was imported before Setuptools, but importing Setuptools also replaces 
the `distutils` module in `sys.modules`. This may lead to undesirable behaviors 
or errors. To avoid these issues, avoid using distutils directly, ensure that 
setuptools is installed in the traditional way (e.g. not an editable install), 
and/or make sure that setuptools is always imported before distutils.

  warnings.warn(
/usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning: 
Setuptools is replacing distutils.

  warnings.warn("Setuptools is replacing distutils.")
error: Multiple top-level packages discovered in a flat-layout: ['deps', 'swig', 
'debian', 'pocketsphinx_disabled'].


To avoid accidental inclusion of unwanted files or directories,
setuptools will not proceed with this build.

If you are trying to create a single distribution with multiple packages
on purpose, you should not rely on automatic discovery.
Instead, consider the following options:

1. set up custom discovery (`find` directive with `include` or `exclude`)
2. use a `src-layout`
3. explicitly set `py_modules` or `packages` with a list of names

To find more information, look for "package discovery" on setuptools docs.
--- End Message ---
--- Begin Message ---
Source: pocketsphinx-python
Source-Version: 1:0.1.15-3
Done: Samuel Thibault 

We believe that the bug you reported is fixed in the latest version of
pocketsphinx-python, 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 1020...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Samuel Thibault  (supplier of updated pocketsphinx-python 
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, 26 Sep 2022 01:14:20 +0200
Source: pocketsphinx-python
Architecture: source
Version: 1:0.1.15-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Accessibility Team 
Changed-By: Samuel Thibault 
Closes: 1020568
Changes:
 pocketsphinx-python (1:0.1.15-3) unstable; urgency=medium
 .
   [ Samuel Thibault ]
   * control: Update alioth list domain.
   * Move tests patches from patches to tests-patches.
   * control: Bump Standards-Version to 4.6.0 (no change)
   * control: Set Rules-Requires-Root to no.
   * control: Make Multi-Arch: same.
   * control: Replace python3-all-dev build-dep with python3-all-dev:any,
 libpython3-all-dev.
   * control, rules: Replace dh-python and --with python3 with
 dh-sequence-python3.
   * watch: Use tags instead of releases.
   * patches/setuptools: Fix build against setuptools 65 (Closes: #1020568)
 .
   [ Debian Janitor ]
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
 Repository-Browse.
   * Set branch from vcswatch in Vcs-Git URL.
   * Use canonical URL in Vcs-Git.
   * Remove constraints unnecessary since buster:
 + Build-Depends: Drop versioned constraint on libpocketsphinx-dev and
   libsphinxbase-dev.
   * Bump debhelper from old 12 to 13.
Checksums-Sha1:
 9dddb12a03356bddcc8ee3045f14e63102ee23c4 2442 

Processed: Re: Bug#1020568: pocketsphinx-python's autopkg tests fail with setuptools 65

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #1020568 [src:pocketsphinx-python] pocketsphinx-python's autopkg tests fail 
with setuptools 65
Added tag(s) pending.

-- 
1020568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020568
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1020568: pocketsphinx-python's autopkg tests fail with setuptools 65

[Samuel Thibault]

Control: tags -1 + pending

Samuel Thibault, le lun. 26 sept. 2022 01:47:58 +0200, a ecrit:
> Ok, I have fixed this in git, but now we are getting a different issue:
> 
> «
> error: Multiple top-level packages discovered in a flat-layout: ['swig', 
> 'deps', 'debian', 'pocketsphinx_disabled'].
> To avoid accidental inclusion of unwanted files or directories,
> setuptools will not proceed with this build.
> If you are trying to create a single distribution with multiple packages
> on purpose, you should not rely on automatic discovery.
> Instead, consider the following options:
> 1. set up custom discovery (`find` directive with `include` or `exclude`)
> 2. use a `src-layout`
> 3. explicitly set `py_modules` or `packages` with a list of names
> To find more information, look for "package discovery" on setuptools docs.
> »

Ok, I found the issue, I'll be able to fix it.

Samuel

Bug#1020846: libgs10-common: missing Breaks+Replaces: libgs9-common (<< 10)

[Andreas Beckmann]

Package: libgs10-common
Version: 10.0.0~dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.
This error may also be triggered by having a predecessor package from
'sid 'installed while installing the package from 'experimental'.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../libgs10-common_10.0.0~dfsg-1_all.deb ...
  Unpacking libgs10-common (10.0.0~dfsg-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libgs10-common_10.0.0~dfsg-1_all.deb (--unpack):
   trying to overwrite '/usr/share/color/icc/ghostscript/a98.icc', which is 
also in package libgs9-common 9.56.1~dfsg-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libgs10-common_10.0.0~dfsg-1_all.deb


cheers,

Andreas


libgs9-common=9.56.1~dfsg-1_libgs10-common=10.0.0~dfsg-1.log.gz
Description: application/gzip

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 1020776 1:7.1+dfsg-2~bpo11+2
Bug #1020776 [qemu-system-data] qemu-system-data in bullseye-backports is too 
old
There is no source info for the package 'qemu-system-data' at version 
'1:7.1+dfsg-2~bpo11+2' with architecture ''
Unable to make a source version for version '1:7.1+dfsg-2~bpo11+2'
Marked as found in versions 1:7.1+dfsg-2~bpo11+2.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
1020776: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020776
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1020845: golang-github-newrelic-go-agent-v3-dev: missing Breaks+Replaces: golang-github-newrelic-go-agent-dev (<< 3.15.2-4)

[Andreas Beckmann]

Package: golang-github-newrelic-go-agent-v3-dev
Version: 3.15.2-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Preparing to unpack 
.../golang-github-newrelic-go-agent-v3-dev_3.15.2-4_all.deb ...
  Unpacking golang-github-newrelic-go-agent-v3-dev (3.15.2-4) ...
  dpkg: error processing archive 
/var/cache/apt/archives/golang-github-newrelic-go-agent-v3-dev_3.15.2-4_all.deb 
(--unpack):
   trying to overwrite 
'/usr/share/gocode/src/github.com/newrelic/go-agent/v3/integrations/logcontext/logcontext.go',
 which is also in package golang-github-newrelic-go-agent-dev 3.15.2-3
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   
/var/cache/apt/archives/golang-github-newrelic-go-agent-v3-dev_3.15.2-4_all.deb


cheers,

Andreas


golang-github-newrelic-go-agent-dev=3.15.2-3_golang-github-newrelic-go-agent-v3-dev=3.15.2-4.log.gz
Description: application/gzip

Processed: severity of 1014628 is important

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 1014628 important
Bug #1014628 [src:git-annex] src:git-annex: fails to migrate to testing for too 
long: FTBFS on armel and armhf
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1014628: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014628
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1020098: marked as done (postgresfixture: FTBFS: TypeError: a bytes-like object is required, not 'str')

[Debian Bug Tracking System]

Your message dated Tue, 27 Sep 2022 13:05:04 +
with message-id 
and subject line Bug#1020098: fixed in postgresfixture 0.4.3-1
has caused the Debian Bug report #1020098,
regarding postgresfixture: FTBFS: TypeError: a bytes-like object is required, 
not 'str'
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.)


-- 
1020098: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020098
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: postgresfixture
Version: 0.4.2-2
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.


Relevant part (hopefully):
>  debian/rules build
> dh build --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:240: python3.10 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating 
> /<>/.pybuild/cpython3_3.10_postgresfixture/build/postgresfixture
> copying postgresfixture/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_postgresfixture/build/postgresfixture
> copying postgresfixture/__main__.py -> 
> /<>/.pybuild/cpython3_3.10_postgresfixture/build/postgresfixture
> copying postgresfixture/clusterfixture.py -> 
> /<>/.pybuild/cpython3_3.10_postgresfixture/build/postgresfixture
> copying postgresfixture/main.py -> 
> /<>/.pybuild/cpython3_3.10_postgresfixture/build/postgresfixture
> copying postgresfixture/cluster.py -> 
> /<>/.pybuild/cpython3_3.10_postgresfixture/build/postgresfixture
> copying postgresfixture/utils.py -> 
> /<>/.pybuild/cpython3_3.10_postgresfixture/build/postgresfixture
> creating 
> /<>/.pybuild/cpython3_3.10_postgresfixture/build/postgresfixture/testing
> copying postgresfixture/testing/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_postgresfixture/build/postgresfixture/testing
> creating 
> /<>/.pybuild/cpython3_3.10_postgresfixture/build/postgresfixture/tests
> copying postgresfixture/tests/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_postgresfixture/build/postgresfixture/tests
> copying postgresfixture/tests/test_cluster.py -> 
> /<>/.pybuild/cpython3_3.10_postgresfixture/build/postgresfixture/tests
> copying postgresfixture/tests/test_main.py -> 
> /<>/.pybuild/cpython3_3.10_postgresfixture/build/postgresfixture/tests
> copying postgresfixture/tests/test_clusterfixture.py -> 
> /<>/.pybuild/cpython3_3.10_postgresfixture/build/postgresfixture/tests
> running egg_info
> writing postgresfixture.egg-info/PKG-INFO
> writing dependency_links to postgresfixture.egg-info/dependency_links.txt
> writing entry points to postgresfixture.egg-info/entry_points.txt
> writing requirements to postgresfixture.egg-info/requires.txt
> writing top-level names to postgresfixture.egg-info/top_level.txt
> reading manifest file 'postgresfixture.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> writing manifest file 'postgresfixture.egg-info/SOURCES.txt'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:240: python3.10 setup.py test 
> running test
> WARNING: Testing via this command is deprecated and will be removed in a 
> future version. Users looking for a generic test entry point independent of 
> test runner are encouraged to use tox.
> running egg_info
> writing postgresfixture.egg-info/PKG-INFO
> writing dependency_links to postgresfixture.egg-info/dependency_links.txt
> writing entry points to postgresfixture.egg-info/entry_points.txt
> writing requirements to postgresfixture.egg-info/requires.txt
> writing top-level names to postgresfixture.egg-info/top_level.txt
> reading manifest file 'postgresfixture.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> writing manifest file 'postgresfixture.egg-info/SOURCES.txt'
> running build_ext
> test_connect (postgresfixture.tests.test_cluster.TestCluster)
> postgresfixture.tests.test_cluster.TestCluster.test_connect (14) ... 
> /<>/postgresfixture/cluster.py:120: DeprecationWarning: 
> distutils Version classes are deprecated. Use packaging.version instead.
>   version = LooseVersion(self.version)
> /<>/postgresfixture/cluster.py:121: DeprecationWarning: 
> distutils Version classes are deprecated. Use packaging.version instead.
>   if version >= LooseVersion("9.4"):
> ok
> test_create (postgresfixture.tests.test_cluster.TestCluster)
> 

Bug#1020025: marked as done (ocp: FTBFS: configure: error: /usr/share/fonts/truetype/unifont/unifont.ttf (unifont.ttf) not found - please use --with-unifontdir=/dir/ or --with-unifont-ttf=/dir/file (n

[Debian Bug Tracking System]

Your message dated Tue, 27 Sep 2022 13:04:50 +
with message-id 
and subject line Bug#1020025: fixed in ocp 1:0.2.100+ds-1
has caused the Debian Bug report #1020025,
regarding ocp: FTBFS: configure: error: 
/usr/share/fonts/truetype/unifont/unifont.ttf (unifont.ttf) not found - please 
use --with-unifontdir=/dir/ or --with-unifont-ttf=/dir/file (needed by X11, 
SDL1.x and SDL2)
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.)


-- 
1020025: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020025
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ocp
Version: 1:0.2.95-1
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.


Relevant part (hopefully):
> checking for vorbisfile... yes
> checking for flac... yes
> checking for sdl2 >= 2.0.0... yes
> checking for freetype2... yes
> checking for /usr/share/fonts/truetype/unifont/unifont.ttf... no
> configure: error: /usr/share/fonts/truetype/unifont/unifont.ttf (unifont.ttf) 
> not found - please use --with-unifontdir=/dir/ or 
> --with-unifont-ttf=/dir/file (needed by X11, SDL1.x and SDL2)
>   tail -v -n \+0 config.log


The full build log is available from:
http://qa-logs.debian.net/2022/09/17/ocp_0.2.95-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220917;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220917=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 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: ocp
Source-Version: 1:0.2.100+ds-1
Done: Gürkan Myczko 

We believe that the bug you reported is fixed in the latest version of
ocp, 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 1020...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Gürkan Myczko  (supplier of updated ocp 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, 27 Sep 2022 13:52:10 +0200
Source: ocp
Architecture: source
Version: 1:0.2.100+ds-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Multimedia Team 
Changed-By: Gürkan Myczko 
Closes: 1020025
Changes:
 ocp (1:0.2.100+ds-1) experimental; urgency=medium
 .
   * New upstream version. (Closes: #1020025)
   * Bump standards version to 4.6.1.
   * d/control: add sensible-utils to Depends.
   * d/clean: updated.
   * d/copyright: add Files-Excluded field.
Checksums-Sha1:
 c41d2ce13fb8c7790a046b9f9ac0d47cd2e26352 2361 ocp_0.2.100+ds-1.dsc
 25391fc2da1865577cb088db4ae4413e12dd9a2f 2750940 ocp_0.2.100+ds.orig.tar.xz
 81d1d23de7fba9eaffc267c9efd07462c3bde92a 10536 ocp_0.2.100+ds-1.debian.tar.xz
 cefe5eeb6f0c98b3b3f24bcb41d2072e799c6c81 13247 
ocp_0.2.100+ds-1_source.buildinfo
Checksums-Sha256:
 550c315b5394d2d156b1edfb3bdfd5fb9be6c128ba8ac47a3efa60e9ae6f0366 2361 
ocp_0.2.100+ds-1.dsc
 e0c0c8dd2a33d8509552f71660189876c03684e4c33df6492810e4e7b9fffc57 2750940 
ocp_0.2.100+ds.orig.tar.xz
 6c8cbc0f06c9bd4d437d1bccfb7d0a7d41b4d68ad6ac2db3792b1746bc3a91f6 10536 
ocp_0.2.100+ds-1.debian.tar.xz
 d0cca6872b008c7e36c9eaba22d99650b5515e27ddca7eadf08f8d9e66c643c7 13247 
ocp_0.2.100+ds-1_source.buildinfo
Files:
 26dd6bb7cf5b299d635467e93010ad15 2361 sound optional ocp_0.2.100+ds-1.dsc
 9f31e6a6887dabf0c68f2cb6596ac3e9 2750940 sound optional 
ocp_0.2.100+ds.orig.tar.xz
 48f3457746b8efdfe8637edeb2bc6a82 10536 sound optional 
ocp_0.2.100+ds-1.debian.tar.xz
 312f034c79d5b31fa04be5da405856d8 13247 sound optional 
ocp_0.2.100+ds-1_source.buildinfo

-BEGIN PGP SIGNATURE-

Bug#1020701: marked as done (gimp: Gimp crash when write on text box)

[Debian Bug Tracking System]

Your message dated Tue, 27 Sep 2022 13:04:05 +
with message-id 
and subject line Bug#1018105: fixed in glib2.0 2.74.0-2
has caused the Debian Bug report #1018105,
regarding gimp: Gimp crash when write on text box
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.)


-- 
1018105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018105
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: gimp
Version: 2.10.32-1+b1
Severity: normal

Dear Maintainer,

The program crash when add text to TextBox.
This is de debug info:




```
GNU Image Manipulation Program version 2.10.32
git-describe: GIMP_2_10_32
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/12/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian
12.1.0-8' --with-bugurl=file:///usr/share/doc/gcc-12/README.Bugs --enable-
languages=c,ada,c++,go,d,fortran,objc,obj-c++,m2 --prefix=/usr --with-gcc-
major-version-only --program-suffix=-12 --program-prefix=x86_64-linux-gnu-
--enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-
included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls
--enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object 
--disable-vtable-

verify --enable-plugin --enable-default-pie --with-system-zlib --enable-
libphobos-checking=release --with-target-system-zlib=auto 
--enable-objc-gc=auto

--enable-multiarch --disable-werror --enable-cet --with-arch-32=i686 --with-
abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib 
--with-tune=generic

--enable-offload-targets=nvptx-
none=/build/gcc-12-WXbu70/gcc-12-12.1.0/debian/tmp-nvptx/usr,amdgcn-
amdhsa=/build/gcc-12-WXbu70/gcc-12-12.1.0/debian/tmp-gcn/usr 
--enable-offload-
defaulted --without-cuda-driver --enable-checking=release 
--build=x86_64-linux-

gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 12.1.0 (Debian 12.1.0-8)

# Libraries #
using babl version 0.1.96 (compiled against version 0.1.92)
using GEGL version 0.4.38 (compiled against version 0.4.38)
using GLib version 2.74.0 (compiled against version 2.72.3)
using GdkPixbuf version 2.42.9 (compiled against version 2.42.9)
using GTK+ version 2.24.33 (compiled against version 2.24.33)
using Pango version 1.50.10 (compiled against version 1.50.9)
using Fontconfig version 2.13.1 (compiled against version 2.13.1)
using Cairo version 1.16.0 (compiled against version 1.16.0)

```
> fatal error: Violación de segmento

Stack trace:
```
/lib/x86_64-linux-
gnu/libgimpbase-2.0.so.0(gimp_stack_trace_print+0x3e8)[0x7ff011d00638]
gimp-2.10(+0xdcd1f)[0x5603b60b7d1f]
gimp-2.10(+0xdd0f8)[0x5603b60b80f8]
gimp-2.10(+0xdd749)[0x5603b60b8749]
/lib/x86_64-linux-gnu/libc.so.6(+0x3daf0)[0x7ff010e3daf0]
/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x25103)[0x7ff011396103]
/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x1b6d8)[0x7ff01138c6d8]
/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x1bf5a)[0x7ff01138cf5a]
/lib/x86_64-linux-
gnu/libgobject-2.0.so.0(g_object_new_with_properties+0x194)[0x7ff01138e3f4]
gimp-2.10(gimp_image_undo_push+0x1a7)[0x5603b6435787]
gimp-2.10(gimp_image_undo_push_text_layer+0x104)[0x5603b6438344]
gimp-2.10(gimp_text_tool_apply+0x103)[0x5603b6167e93]
gimp-2.10(+0x18ea27)[0x5603b6169a27]
gimp-2.10(+0x18ec62)[0x5603b6169c62]
/lib/x86_64-linux-
gnu/libgobject-2.0.so.0(g_closure_invoke+0x160)[0x7ff011387500]
/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x29b36)[0x7ff01139ab36]
/lib/x86_64-linux-
gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xf35)[0x7ff0113a16b5]
/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x8f)[0x7ff0113a187f]
gimp-2.10(+0x1913e5)[0x5603b616c3e5]
/lib/x86_64-linux-
gnu/libgobject-2.0.so.0(g_closure_invoke+0x160)[0x7ff011387500]
/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x29b36)[0x7ff01139ab36]
/lib/x86_64-linux-
gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xf35)[0x7ff0113a16b5]
/lib/x86_64-linux-
gnu/libgobject-2.0.so.0(g_signal_emit_by_name+0x1f8)[0x7ff0113a1a98]
/lib/x86_64-linux-
gnu/libgobject-2.0.so.0(g_closure_invoke+0x160)[0x7ff011387500]
/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x29b36)[0x7ff01139ab36]
/lib/x86_64-linux-
gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xf35)[0x7ff0113a16b5]
/lib/x86_64-linux-
gnu/libgobject-2.0.so.0(g_signal_emit_by_name+0x1f8)[0x7ff0113a1a98]

Bug#1020682: marked as done (GIMP - segfaults using Text tool on large XCF/JPG image; gimp unstable thereafter; corrupting the gimp config?)

[Debian Bug Tracking System]

Your message dated Tue, 27 Sep 2022 13:04:05 +
with message-id 
and subject line Bug#1018105: fixed in glib2.0 2.74.0-2
has caused the Debian Bug report #1018105,
regarding GIMP - segfaults using Text tool on large XCF/JPG image; gimp 
unstable thereafter; corrupting the gimp config?
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.)


-- 
1018105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018105
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: gimp

Version: 2.10.32-1+b1


GIMP segfaults using Text tool on a large image (5421px * 7016px). Image 
format seems to be irrelevant. Segfaults with both RGB 8-bit XCF and JPG.


Crash occurs when resizing the Text window, or just when typing text 
into the Text window.


Repeatable on two separate machines, one machine had a completely fresh 
Debian install including GIMP


After the segfault crash, GIMP is left unstable and now crashes when 
Text tool is used on any image, large or small.


At a guess, something in the GIMP configuration file(s) has been 
corrupted by the segfault.






```
GNU Image Manipulation Program version 2.10.32
git-describe: GIMP_2_10_32
Build: unknown rev 0 for linux
# C compiler #
    Using built-in specs.
    COLLECT_GCC=gcc
 COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/12/lto-wrapper
    OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa
    OFFLOAD_TARGET_DEFAULT=1
    Target: x86_64-linux-gnu
    Configured with: ../src/configure -v --with-pkgversion='Debian 
12.1.0-8' --with-bugurl=file:///usr/share/doc/gcc-12/README.Bugs 
--enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++,m2 --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-12 
--program-prefix=x86_64-linux-gnu- --enable-shared 
--enable-linker-build-id --libexecdir=/usr/lib 
--without-included-gettext --enable-threads=posix --libdir=/usr/lib 
--enable-nls --enable-clocale=gnu --enable-libstdcxx-debug 
--enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new 
--enable-gnu-unique-object --disable-vtable-verify --enable-plugin 
--enable-default-pie --with-system-zlib 
--enable-libphobos-checking=release --with-target-system-zlib=auto 
--enable-objc-gc=auto --enable-multiarch --disable-werror --enable-cet 
--with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 
--enable-multilib --with-tune=generic 
--enable-offload-targets=nvptx-none=/build/gcc-12-WXbu70/gcc-12-12.1.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-12-WXbu70/gcc-12-12.1.0/debian/tmp-gcn/usr 
--enable-offload-defaulted --without-cuda-driver 
--enable-checking=release --build=x86_64-linux-gnu 
--host=x86_64-linux-gnu --target=x86_64-linux-gnu

    Thread model: posix
    Supported LTO compression algorithms: zlib zstd
    gcc version 12.1.0 (Debian 12.1.0-8)

# Libraries #
using babl version 0.1.96 (compiled against version 0.1.92)
using GEGL version 0.4.38 (compiled against version 0.4.38)
using GLib version 2.73.3 (compiled against version 2.72.3)
using GdkPixbuf version 2.42.9 (compiled against version 2.42.9)
using GTK+ version 2.24.33 (compiled against version 2.24.33)
using Pango version 1.50.9 (compiled against version 1.50.9)
using Fontconfig version 2.13.1 (compiled against version 2.13.1)
using Cairo version 1.16.0 (compiled against version 1.16.0)

```
> fatal error: Segmentation fault

Stack trace:
```
/usr/lib/x86_64-linux-gnu/libgimpbase-2.0.so.0(gimp_stack_trace_print+0x3e8)[0x7ff464ad6638] 


gimp-2.10(+0xdcd1f)[0x56476f936d1f]
gimp-2.10(+0xdd0f8)[0x56476f9370f8]
gimp-2.10(+0xdd749)[0x56476f937749]
/lib/x86_64-linux-gnu/libc.so.6(+0x3daf0)[0x7ff46383daf0]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x25103)[0x7ff463d09103]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x1b6d8)[0x7ff463cff6d8]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x1bf5a)[0x7ff463cfff5a]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_object_new_with_properties+0x194)[0x7ff463d013f4] 


gimp-2.10(gimp_image_undo_push+0x1a7)[0x56476fcb4787]
gimp-2.10(gimp_image_undo_push_text_layer+0x104)[0x56476fcb7344]
gimp-2.10(gimp_text_tool_apply+0x103)[0x56476f9e6e93]
gimp-2.10(+0x18d3b6)[0x56476f9e73b6]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x160)[0x7ff463cfa500] 


/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x29b36)[0x7ff463d0db36]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xf35)[0x7ff463d146b5] 

/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x8f)[0x7ff463d1487f] 


gimp-2.10(+0x20d86a)[0x56476fa6786a]
gimp-2.10(+0x18c269)[0x56476f9e6269]
gimp-2.10(gimp_tool_button_release+0x191)[0x56476f9f07d1]

Bug#1020663: marked as done (GIMP crashes when trying to using test tool)

[Debian Bug Tracking System]

Your message dated Tue, 27 Sep 2022 13:04:05 +
with message-id 
and subject line Bug#1018105: fixed in glib2.0 2.74.0-2
has caused the Debian Bug report #1018105,
regarding GIMP crashes when trying to using test tool
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.)


-- 
1018105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018105
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gimp
Version: 2.10.32-1+b1
Severity: important

When using text tool to add text to an image GIMP crashes.

Information from the GIMP Crash Debug tool:

```
GNU Image Manipulation Program version 2.10.32
git-describe: GIMP_2_10_32
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/12/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 
12.1.0-8' --with-bugurl=file:///usr/share/doc/gcc-12/README.Bugs 
--enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++,m2 --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-12 
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug 
--enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new 
--enable-gnu-unique-object --disable-vtable-verify --enable-plugin 
--enable-default-pie --with-system-zlib --enable-libphobos-checking=release 
--with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch 
--disable-werror --enable-cet --with-arch-32=i686 --with-abi=m64 
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic 
--enable-offload-targets=nvptx-none=/build/gcc-12-WXbu70/gcc-12-12.1.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-12-WXbu70/gcc-12-12.1.0/debian/tmp-gcn/usr
 --enable-offload-defaulted --without-cuda-driver --enable-checking=release 
--build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 12.1.0 (Debian 12.1.0-8) 

# Libraries #
using babl version 0.1.96 (compiled against version 0.1.92)
using GEGL version 0.4.38 (compiled against version 0.4.38)
using GLib version 2.74.0 (compiled against version 2.72.3)
using GdkPixbuf version 2.42.9 (compiled against version 2.42.9)
using GTK+ version 2.24.33 (compiled against version 2.24.33)
using Pango version 1.50.10 (compiled against version 1.50.9)
using Fontconfig version 2.13.1 (compiled against version 2.13.1)
using Cairo version 1.16.0 (compiled against version 1.16.0)

```
> fatal error: Segmentation fault

Stack trace:
```

# Stack traces obtained from PID 649629 - Thread 649629 #

[New LWP 649632]
[New LWP 649633]
[New LWP 649634]
[New LWP 649635]
[New LWP 649636]
[New LWP 649637]
[New LWP 649639]
[New LWP 649677]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
__GI___libc_read (nbytes=256, buf=0x7ffc88a59b70, fd=19) at 
../sysdeps/unix/sysv/linux/read.c:26
  Id   Target Id Frame 
* 1Thread 0x7faef3c82e40 (LWP 649629) "gimp-2.10"__GI___libc_read 
(nbytes=256, buf=0x7ffc88a59b70, fd=19) at ../sysdeps/unix/sysv/linux/read.c:26
  2Thread 0x7faef3505640 (LWP 649632) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  3Thread 0x7faef2d04640 (LWP 649633) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  4Thread 0x7faef2503640 (LWP 649634) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  5Thread 0x7faef0ccd640 (LWP 649635) "gmain"0x7faef48dd1ef in 
__GI___poll (fds=0x55cae7c92bc0, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  6Thread 0x7faeebfff640 (LWP 649636) "dconf worker" 0x7faef48dd1ef in 
__GI___poll (fds=0x55cae7c965b0, nfds=1, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  7Thread 0x7faeeb7fe640 (LWP 649637) "gdbus"0x7faef48dd1ef in 
__GI___poll (fds=0x7faed0015a90, nfds=3, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  8Thread 0x7faec31fe640 (LWP 649639) "async"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  9Thread 0x7faeeaffd640 (LWP 649677) "swap writer"  syscall () at 

Bug#1020608: marked as done (GIMP crashed with a fatal error)

[Debian Bug Tracking System]

Your message dated Tue, 27 Sep 2022 13:04:05 +
with message-id 
and subject line Bug#1018105: fixed in glib2.0 2.74.0-2
has caused the Debian Bug report #1018105,
regarding GIMP crashed with a fatal error
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.)


-- 
1018105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018105
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package:gimp
Version:2.10.32-1+b1

GIMP crashed with a fatal error: fatal error: Erreur de segmentation

When (re)editing a text, GIMP crashed with a fatal error




```
GNU Image Manipulation Program version 2.10.32
git-describe: GIMP_2_10_32
Build: unknown rev 0 for linux
# C compiler #
    Using built-in specs.
    COLLECT_GCC=gcc
    COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/12/lto-wrapper
    OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa
    OFFLOAD_TARGET_DEFAULT=1
    Target: x86_64-linux-gnu
    Configured with: ../src/configure -v --with-pkgversion='Debian 
12.1.0-8' --with-bugurl=file:///usr/share/doc/gcc-12/README.Bugs 
--enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++,m2 --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-12 
--program-prefix=x86_64-linux-gnu- --enable-shared 
--enable-linker-build-id --libexecdir=/usr/lib 
--without-included-gettext --enable-threads=posix --libdir=/usr/lib 
--enable-nls --enable-clocale=gnu --enable-libstdcxx-debug 
--enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new 
--enable-gnu-unique-object --disable-vtable-verify --enable-plugin 
--enable-default-pie --with-system-zlib 
--enable-libphobos-checking=release --with-target-system-zlib=auto 
--enable-objc-gc=auto --enable-multiarch --disable-werror --enable-cet 
--with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 
--enable-multilib --with-tune=generic 
--enable-offload-targets=nvptx-none=/build/gcc-12-WXbu70/gcc-12-12.1.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-12-WXbu70/gcc-12-12.1.0/debian/tmp-gcn/usr 
--enable-offload-defaulted --without-cuda-driver 
--enable-checking=release --build=x86_64-linux-gnu 
--host=x86_64-linux-gnu --target=x86_64-linux-gnu

    Thread model: posix
    Supported LTO compression algorithms: zlib zstd
    gcc version 12.1.0 (Debian 12.1.0-8)

# Libraries #
using babl version 0.1.96 (compiled against version 0.1.92)
using GEGL version 0.4.38 (compiled against version 0.4.38)
using GLib version 2.74.0 (compiled against version 2.72.3)
using GdkPixbuf version 2.42.9 (compiled against version 2.42.9)
using GTK+ version 2.24.33 (compiled against version 2.24.33)
using Pango version 1.50.10 (compiled against version 1.50.9)
using Fontconfig version 2.13.1 (compiled against version 2.13.1)
using Cairo version 1.16.0 (compiled against version 1.16.0)

```
> fatal error: Erreur de segmentation

Stack trace:
```
/lib/x86_64-linux-gnu/libgimpbase-2.0.so.0(gimp_stack_trace_print+0x3e8)[0x7f99641a9638]
gimp-2.10(+0xdcd1f)[0x559fb7e0cd1f]
gimp-2.10(+0xdd0f8)[0x559fb7e0d0f8]
gimp-2.10(+0xdd749)[0x559fb7e0d749]
/lib/x86_64-linux-gnu/libc.so.6(+0x3daf0)[0x7f9963443af0]
/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x25103)[0x7f996383d103]
/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x1b6d8)[0x7f99638336d8]
/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x1bf5a)[0x7f9963833f5a]
/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_object_new_with_properties+0x194)[0x7f99638353f4]
gimp-2.10(gimp_image_undo_push+0x1a7)[0x559fb818a787]
gimp-2.10(gimp_image_undo_push_text_layer+0x104)[0x559fb818d344]
gimp-2.10(gimp_text_tool_apply+0x103)[0x559fb7ebce93]
gimp-2.10(+0x18d3b6)[0x559fb7ebd3b6]
/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x160)[0x7f996382e500]
/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x29b36)[0x7f9963841b36]
/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xf35)[0x7f99638486b5]
/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x8f)[0x7f996384887f]
gimp-2.10(+0x20d86a)[0x559fb7f3d86a]
gimp-2.10(+0x18c269)[0x559fb7ebc269]
gimp-2.10(gimp_tool_button_release+0x191)[0x559fb7ec67d1]
gimp-2.10(+0x1e8cc4)[0x559fb7f18cc4]
gimp-2.10(gimp_display_shell_canvas_tool_events+0x79)[0x559fb7f19139]
/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x1391ab)[0x7f99644041ab]
/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x160)[0x7f996382e500]
/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x29b36)[0x7f9963841b36]
/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0x76d)[0x7f9963847eed]
/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x8f)[0x7f996384887f]
/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x258fe4)[0x7f9964523fe4]

Bug#1020261: marked as done (gimp: GIMP crashes when interacting with text)

[Debian Bug Tracking System]

Your message dated Tue, 27 Sep 2022 13:04:05 +
with message-id 
and subject line Bug#1018105: fixed in glib2.0 2.74.0-2
has caused the Debian Bug report #1018105,
regarding gimp: GIMP crashes when interacting with text
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.)


-- 
1018105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018105
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gimp
Version: 2.10.32-1+b1
Severity: normal
X-Debbugs-Cc: lorenzorodrigues...@gmail.com

Dear Maintainer,

A crash occurs when I try to interact with text that I've inserted.

Steps to reproduce:
1. Open image;
2. Select the text tool and insert text;
3. Try to interact with it by: changing font size, changing color, resizing the 
text box.

Unlike bugs #376821 and #869514, I can insert the text just fine, but by doing 
one the actions that I've mentioned (there could be more that I simply didn't 
observe yet), the program crashes. Also, it happens with either antialiasing 
enabled or disabled.

Debug data given by GIMP (when trying to change font size):

```
GNU Image Manipulation Program version 2.10.32
git-describe: GIMP_2_10_32
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/12/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 
12.1.0-8' --with-bugurl=file:///usr/share/doc/gcc-12/README.Bugs 
--enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++,m2 --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-12 
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug 
--enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new 
--enable-gnu-unique-object --disable-vtable-verify --enable-plugin 
--enable-default-pie --with-system-zlib --enable-libphobos-checking=release 
--with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch 
--disable-werror --enable-cet --with-arch-32=i686 --with-abi=m64 
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic 
--enable-offload-targets=nvptx-none=/build/gcc-12-WXbu70/gcc-12-12.1.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-12-WXbu70/gcc-12-12.1.0/debian/tmp-gcn/usr
 --enable-offload-defaulted --without-cuda-driver --enable-checking=release 
--build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 12.1.0 (Debian 12.1.0-8) 

# Libraries #
using babl version 0.1.96 (compiled against version 0.1.92)
using GEGL version 0.4.38 (compiled against version 0.4.38)
using GLib version 2.73.3 (compiled against version 2.72.3)
using GdkPixbuf version 2.42.9 (compiled against version 2.42.9)
using GTK+ version 2.24.33 (compiled against version 2.24.33)
using Pango version 1.50.9 (compiled against version 1.50.9)
using Fontconfig version 2.13.1 (compiled against version 2.13.1)
using Cairo version 1.16.0 (compiled against version 1.16.0)

```
> fatal error: Falha de segmentação

Stack trace:
```

# Stack traces obtained from PID 48998 - Thread 48998 #

[New LWP 48999]
[New LWP 49000]
[New LWP 49001]
[New LWP 49002]
[New LWP 49003]
[New LWP 49004]
[New LWP 49005]
[New LWP 49009]
[New LWP 49043]
[New LWP 49093]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
__GI___libc_read (nbytes=256, buf=0x7ffcef9b30b0, fd=17) at 
../sysdeps/unix/sysv/linux/read.c:26
  Id   Target Id  Frame 
* 1Thread 0x7fc09fe72380 (LWP 48998) "gimp-2.10"  __GI___libc_read 
(nbytes=256, buf=0x7ffcef9b30b0, fd=17) at ../sysdeps/unix/sysv/linux/read.c:26
  2Thread 0x7fc09f10d640 (LWP 48999) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  3Thread 0x7fc09e90c640 (LWP 49000) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  4Thread 0x7fc09e10b640 (LWP 49001) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  5Thread 0x7fc09590a640 (LWP 49002) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  6Thread 0x7fc09d90a640 (LWP 49003) "worker" syscall () at 

Bug#1020532: marked as done (gimp: text element crashes gimp)

[Debian Bug Tracking System]

Your message dated Tue, 27 Sep 2022 13:04:05 +
with message-id 
and subject line Bug#1018105: fixed in glib2.0 2.74.0-2
has caused the Debian Bug report #1018105,
regarding gimp: text element crashes gimp
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.)


-- 
1018105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018105
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gimp
Version: 2.10.32-1+b1
Severity: important
X-Debbugs-Cc: off...@klepp.biz

Dear Maintainer,

Gimp crashes, when a text element is modified:

- open gimp, create new image
- create text element
- select some characters inside this text element 
- change the font size

--> gimp crashes


Console errors:

gimp: fatal error: Speicherzugriffsfehler
(script-fu:16693): LibGimpBase-WARNING **: 20:57:28.455: script-fu: 
gimp_wire_read(): error


-- System Information:
Debian Release: bookworm/sid
merged-usr: no
Architecture: amd64 (x86_64)

Kernel: Linux 5.19.0-1-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_AT:de
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages gimp depends on:
ii  gimp-data2.10.32-1
ii  graphviz 2.42.2-7
ii  libaa1   1.4p5-50
ii  libbabl-0.1-01:0.1.96-1
ii  libbz2-1.0   1.0.8-5+b1
ii  libc62.34-8
ii  libcairo21.16.0-6
ii  libfontconfig1   2.13.1-4.5
ii  libfreetype6 2.12.1+dfsg-3
ii  libgcc-s112.2.0-2
ii  libgdk-pixbuf-2.0-0  2.42.9+dfsg-1
ii  libgegl-0.4-01:0.4.38-1+b1
ii  libgexiv2-2  0.14.0-1+b1
ii  libgimp2.0   2.10.32-1+b1
ii  libglib2.0-0 2.74.0-1
ii  libgs9   9.56.1~dfsg-1
ii  libgtk2.0-0  2.24.33-2
ii  libgudev-1.0-0   237-2
ii  libharfbuzz0b2.7.4-1+b1
ii  libheif1 1.13.0-1
ii  libjpeg62-turbo  1:2.1.2-1+b1
ii  libjson-glib-1.0-0   1.6.6-1
ii  liblcms2-2   2.13.1-1+b1
ii  liblzma5 5.2.5-2.1
ii  libmng1  1.0.10+dfsg-3.1+b5
ii  libmypaint-1.5-1 1.6.0-2
ii  libopenexr-3-1-303.1.5-4
ii  libopenjp2-7 2.5.0-1
ii  libpango-1.0-0   1.50.10+ds-1
ii  libpangocairo-1.0-0  1.50.10+ds-1
ii  libpangoft2-1.0-01.50.10+ds-1
ii  libpng16-16  1.6.37-5
ii  libpoppler-glib8 22.08.0-2.1
ii  librsvg2-2   2.54.4+dfsg-1
ii  libstdc++6   12.2.0-2
ii  libtiff5 4.4.0-4
ii  libwebp7 1.2.2-2+b1
ii  libwebpdemux21.2.2-2+b1
ii  libwebpmux3  1.2.2-2+b1
ii  libwmf-0.2-7 0.2.12-5
ii  libwmflite-0.2-7 0.2.12-5
ii  libx11-6 2:1.8.1-2
ii  libxcursor1  1:1.2.1-1
ii  libxext6 2:1.3.4-1+b1
ii  libxfixes3   1:6.0.0-1
ii  libxmu6  2:1.1.3-3
ii  libxpm4  1:3.5.12-1
ii  xdg-utils1.1.3-4.1
ii  zlib1g   1:1.2.11.dfsg-4.1

Versions of packages gimp recommends:
ii  ghostscript  9.56.1~dfsg-1

Versions of packages gimp suggests:
pn  gimp-data-extras  
pn  gimp-help-en | gimp-help  
pn  gvfs-backends 
ii  libasound21.2.7.2-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: glib2.0
Source-Version: 2.74.0-2
Done: Simon McVittie 

We believe that the bug you reported is fixed in the latest version of
glib2.0, 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 1018...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated glib2.0 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, 27 Sep 2022 09:53:09 +0100
Source: glib2.0
Architecture: source
Version: 2.74.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Closes: 1018105
Changes:
 glib2.0 (2.74.0-2) unstable; urgency=medium
 .
   * d/p/Empty-values-are-not-valid-GParamSpec.patch:
 Add patch from upstream to fix GIMP crashes with GLib 2.74.0
 (Closes: 

Bug#1020339: marked as done (Gimp crash when use Text tool)

[Debian Bug Tracking System]

Your message dated Tue, 27 Sep 2022 13:04:05 +
with message-id 
and subject line Bug#1018105: fixed in glib2.0 2.74.0-2
has caused the Debian Bug report #1018105,
regarding Gimp crash when use Text tool
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.)


-- 
1018105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018105
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gimp
Version: 2.10.32-1+b1






```
GNU Image Manipulation Program version 2.10.32
git-describe: GIMP_2_10_32
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/12/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian
12.1.0-8' --with-bugurl=file:///usr/share/doc/gcc-12/README.Bugs
--enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++,m2 --prefix=/usr
--with-gcc-major-version-only --program-suffix=-12
--program-prefix=x86_64-linux-gnu- --enable-shared
--enable-linker-build-id --libexecdir=/usr/lib
--without-included-gettext --enable-threads=posix --libdir=/usr/lib
--enable-nls --enable-clocale=gnu --enable-libstdcxx-debug
--enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new
--enable-gnu-unique-object --disable-vtable-verify --enable-plugin
--enable-default-pie --with-system-zlib
--enable-libphobos-checking=release --with-target-system-zlib=auto
--enable-objc-gc=auto --enable-multiarch --disable-werror --enable-cet
--with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32
--enable-multilib --with-tune=generic
--enable-offload-targets=nvptx-none=/build/gcc-12-WXbu70/gcc-12-12.1.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-12-WXbu70/gcc-12-12.1.0/debian/tmp-gcn/usr
--enable-offload-defaulted --without-cuda-driver
--enable-checking=release --build=x86_64-linux-gnu
--host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix
Supported LTO compression algorithms: zlib zstd gcc version 12.1.0
(Debian 12.1.0-8) 

# Libraries #
using babl version 0.1.96 (compiled against version 0.1.92)
using GEGL version 0.4.38 (compiled against version 0.4.38)
using GLib version 2.74.0 (compiled against version 2.72.3)
using GdkPixbuf version 2.42.9 (compiled against version 2.42.9)
using GTK+ version 2.24.33 (compiled against version 2.24.33)
using Pango version 1.50.10 (compiled against version 1.50.9)
using Fontconfig version 2.13.1 (compiled against version 2.13.1)
using Cairo version 1.16.0 (compiled against version 1.16.0)

```
> fatal error: Segmentation fault

Stack trace:
```
/lib/x86_64-linux-gnu/libgimpbase-2.0.so.0(gimp_stack_trace_print+0x3e8)[0x7f65020f8638]
gimp(+0xdcd1f)[0x55fe296c0d1f]
gimp(+0xdd0f8)[0x55fe296c10f8]
gimp(+0xdd749)[0x55fe296c1749]
/lib/x86_64-linux-gnu/libc.so.6(+0x3daf0)[0x7f650123daf0]
/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x25103)[0x7f650178c103]
/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x1b6d8)[0x7f65017826d8]
/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x1bf5a)[0x7f6501782f5a]
/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_object_new_with_properties+0x194)[0x7f65017843f4]
gimp(gimp_image_undo_push+0x1a7)[0x55fe29a3e787]
gimp(gimp_image_undo_push_text_layer+0x104)[0x55fe29a41344]
gimp(gimp_text_tool_apply+0x103)[0x55fe29770e93]
gimp(+0x18ea27)[0x55fe29772a27]
gimp(+0x18ec62)[0x55fe29772c62]
/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x160)[0x7f650177d500]
/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x29b36)[0x7f6501790b36]
/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xf35)[0x7f65017976b5]
/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x8f)[0x7f650179787f]
gimp(+0x1913e5)[0x55fe297753e5]
/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x160)[0x7f650177d500]
/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x29b36)[0x7f6501790b36]
/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xf35)[0x7f65017976b5]
/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_by_name+0x1f8)[0x7f6501797a98]
/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x160)[0x7f650177d500]
/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x29b36)[0x7f6501790b36]
/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xf35)[0x7f65017976b5]
/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_by_name+0x1f8)[0x7f6501797a98]
/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x11f030)[0x7f650231f030]
/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x11f613)[0x7f650231f613]

Bug#1020266: marked as done (gimp: GIMP crash frequently)

[Debian Bug Tracking System]

Your message dated Tue, 27 Sep 2022 13:04:05 +
with message-id 
and subject line Bug#1018105: fixed in glib2.0 2.74.0-2
has caused the Debian Bug report #1018105,
regarding gimp: GIMP crash frequently
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.)


-- 
1018105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018105
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: gimp
Version: 2.10.32-1+b1
Severity: normal

Dear Maintainer,

GIMP crash randomly and frequently. I don't know what is that reason.

```
GNU Image Manipulation Program version 2.10.32
git-describe: GIMP_2_10_32
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/12/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian
12.1.0-8' --with-bugurl=file:///usr/share/doc/gcc-12/README.Bugs --enable-
languages=c,ada,c++,go,d,fortran,objc,obj-c++,m2 --prefix=/usr --with-gcc-
major-version-only --program-suffix=-12 --program-prefix=x86_64-linux-gnu-
--enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-
included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls
--enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-
verify --enable-plugin --enable-default-pie --with-system-zlib --enable-
libphobos-checking=release --with-target-system-zlib=auto --enable-objc-gc=auto
--enable-multiarch --disable-werror --enable-cet --with-arch-32=i686 --with-
abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic
--enable-offload-targets=nvptx-
none=/build/gcc-12-WXbu70/gcc-12-12.1.0/debian/tmp-nvptx/usr,amdgcn-
amdhsa=/build/gcc-12-WXbu70/gcc-12-12.1.0/debian/tmp-gcn/usr --enable-offload-
defaulted --without-cuda-driver --enable-checking=release --build=x86_64-linux-
gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 12.1.0 (Debian 12.1.0-8)

# Libraries #
using babl version 0.1.96 (compiled against version 0.1.92)
using GEGL version 0.4.38 (compiled against version 0.4.38)
using GLib version 2.73.3 (compiled against version 2.72.3)
using GdkPixbuf version 2.42.9 (compiled against version 2.42.9)
using GTK+ version 2.24.33 (compiled against version 2.24.33)
using Pango version 1.50.9 (compiled against version 1.50.9)
using Fontconfig version 2.13.1 (compiled against version 2.13.1)
using Cairo version 1.16.0 (compiled against version 1.16.0)

```
> fatal error: Falha de segmentação

Stack trace:
```

# Stack traces obtained from PID 265373 - Thread 265373 #

[New LWP 265377]
[New LWP 265378]
[New LWP 265379]
[New LWP 265380]
[New LWP 265381]
[New LWP 265383]
[New LWP 265422]
[New LWP 265437]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
__GI___libc_read (nbytes=256, buf=0x7ffd957e2af0, fd=20) at
../sysdeps/unix/sysv/linux/read.c:26
  Id   Target Id   Frame
* 1Thread 0x7fdea638b380 (LWP 265373) "gimp-2.10"  __GI___libc_read
(nbytes=256, buf=0x7ffd957e2af0, fd=20) at ../sysdeps/unix/sysv/linux/read.c:26
  2Thread 0x7fdea5a29640 (LWP 265377) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  3Thread 0x7fdea5228640 (LWP 265378) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  4Thread 0x7fde9640 (LWP 265379) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  5Thread 0x7fde9f1e7640 (LWP 265380) "gmain"  0x7fdea6efda3f
in __GI___poll (fds=0x55f3a7c0a070, nfds=2, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
  6Thread 0x7fde9e9e6640 (LWP 265381) "gdbus"  0x7fdea6efda3f
in __GI___poll (fds=0x55f3a7c1a880, nfds=3, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
  7Thread 0x7fde88bff640 (LWP 265383) "async"  syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  8Thread 0x7fde821ff640 (LWP 265422) "swap writer"syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  9Thread 0x7fde811fd640 (LWP 265437) "pool-gimp-2.10" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38

Thread 9 (Thread 0x7fde811fd640 (LWP 265437) "pool-gimp-2.10"):
#0  

Bug#1019970: marked as done (gimp: Typing on a text box layer, a segfault occurs)

[Debian Bug Tracking System]

Your message dated Tue, 27 Sep 2022 13:04:05 +
with message-id 
and subject line Bug#1018105: fixed in glib2.0 2.74.0-2
has caused the Debian Bug report #1018105,
regarding gimp: Typing on a text box layer, a segfault occurs
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.)


-- 
1018105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018105
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gimp
Version: 2.99.10-1
Severity: normal

Dear Maintainer,

Trying to create a text box will make GIMP segfault with the
following stacktrace:

# Stack traces obtained from PID 177415 - Thread 177415 #

[New LWP 177416]
[New LWP 177417]
[New LWP 177418]
[New LWP 177419]
[New LWP 177420]
[New LWP 177421]
[New LWP 177422]
[New LWP 177423]
[New LWP 177424]
[New LWP 177425]
[New LWP 177426]
[New LWP 177427]
[New LWP 177428]
[New LWP 177443]
[New LWP 177445]
[New LWP 177446]
[New LWP 177447]
[New LWP 177448]
[New LWP 177449]
[New LWP 177450]
[New LWP 177451]
[New LWP 177452]
[New LWP 177453]
[New LWP 177454]
[New LWP 177455]
[New LWP 177456]
[New LWP 177498]
[New LWP 177525]
[New LWP 177542]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
__GI___libc_read (nbytes=255, buf=0x7ffea7c13af0, fd=21) at 
../sysdeps/unix/sysv/linux/read.c:26
  Id   Target Id   Frame 
* 1Thread 0x7f289a4b8140 (LWP 177415) "gimp-2.99"  __GI___libc_read 
(nbytes=255, buf=0x7ffea7c13af0, fd=21) at ../sysdeps/unix/sysv/linux/read.c:26
  2Thread 0x7f289a154640 (LWP 177416) "gmain"  0x7f289e910a3f 
in __GI___poll (fds=0x5588ebd37bb0, nfds=2, timeout=7000) at 
../sysdeps/unix/sysv/linux/poll.c:29
  3Thread 0x7f2899953640 (LWP 177417) "gdbus"  0x7f289e910a3f 
in __GI___poll (fds=0x5588ee2ee440, nfds=6, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  4Thread 0x7f2898e2e640 (LWP 177418) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  5Thread 0x7f2893fff640 (LWP 177419) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  6Thread 0x7f28937fe640 (LWP 177420) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  7Thread 0x7f2892ffd640 (LWP 177421) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  8Thread 0x7f28927fc640 (LWP 177422) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  9Thread 0x7f2891ffb640 (LWP 177423) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  10   Thread 0x7f28917fa640 (LWP 177424) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  11   Thread 0x7f2890ff9640 (LWP 177425) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  12   Thread 0x7f286640 (LWP 177426) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  13   Thread 0x7f286f7fe640 (LWP 177427) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  14   Thread 0x7f286effd640 (LWP 177428) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  15   Thread 0x7f2856a18640 (LWP 177443) "async"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  16   Thread 0x7f2855841640 (LWP 177445) "gimp-2.99"  
__futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x0, op=393, 
expected=0, futex_word=0x5588ec2f9ae8) at ./nptl/futex-internal.c:57
  17   Thread 0x7f2855640640 (LWP 177446) "gimp-2.99"  
__futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x0, op=393, 
expected=0, futex_word=0x5588ec2fa208) at ./nptl/futex-internal.c:57
  18   Thread 0x7f285543f640 (LWP 177447) "gimp-2.99"  
__futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x0, op=393, 
expected=0, futex_word=0x5588ec2fa27c) at ./nptl/futex-internal.c:57
  19   Thread 0x7f285523e640 (LWP 177448) "gimp-2.99"  
__futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x0, op=393, 
expected=0, futex_word=0x5588ec2fa2e8) at ./nptl/futex-internal.c:57
  20   Thread 0x7f285503d640 (LWP 177449) "gimp-2.99"  
__futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x0, op=393, 
expected=0, futex_word=0x5588ec2fa35c) at ./nptl/futex-internal.c:57
  21   Thread 0x7f2854e3c640 (LWP 177450) "gimp-2.99"  
__futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x0, op=393, 
expected=0, futex_word=0x5588ec2fa3cc) at 

Bug#1018105: marked as done (gimp: crashes when adding text to image)

[Debian Bug Tracking System]

Your message dated Tue, 27 Sep 2022 13:04:05 +
with message-id 
and subject line Bug#1018105: fixed in glib2.0 2.74.0-2
has caused the Debian Bug report #1018105,
regarding gimp: crashes when adding text to image
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.)


-- 
1018105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018105
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gimp
Version: 2.10.32-1+b1
Severity: important
X-Debbugs-Cc: somethingsomethingg...@gmail.com

Dear Maintainer,


   * What led up to the situation? adding text to an image after deleting part
of the image
   * What was the outcome of this action? gimp crashed
   * What outcome did you expect instead? text to be added to image



-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.18.0-4-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gimp depends on:
ii  gimp-data2.10.32-1
ii  graphviz 2.42.2-7
ii  libaa1   1.4p5-50
ii  libbabl-0.1-01:0.1.92-1
ii  libbz2-1.0   1.0.8-5
ii  libc62.34-5
ii  libcairo21.16.0-6
ii  libfontconfig1   2.13.1-4.4
ii  libfreetype6 2.12.1+dfsg-3
ii  libgcc-s112.2.0-1
ii  libgdk-pixbuf-2.0-0  2.42.9+dfsg-1
ii  libgegl-0.4-01:0.4.38-1+b1
ii  libgexiv2-2  0.14.0-1
ii  libgimp2.0   2.10.32-1+b1
ii  libglib2.0-0 2.73.3-2
ii  libgs9   9.56.1~dfsg-1
ii  libgtk2.0-0  2.24.33-2
ii  libgudev-1.0-0   237-2
ii  libharfbuzz0b2.7.4-1+b1
ii  libheif1 1.12.0-2+b4
ii  libjpeg62-turbo  1:2.1.2-1
ii  libjson-glib-1.0-0   1.6.6-1
ii  liblcms2-2   2.13.1-1
ii  liblzma5 5.2.5-2.1
ii  libmng1  1.0.10+dfsg-3.1+b5
ii  libmypaint-1.5-1 1.6.0-2
ii  libopenexr-3-1-303.1.5-4
ii  libopenjp2-7 2.5.0-1
ii  libpango-1.0-0   1.50.9+ds-1
ii  libpangocairo-1.0-0  1.50.9+ds-1
ii  libpangoft2-1.0-01.50.9+ds-1
ii  libpng16-16  1.6.37-5
ii  libpoppler-glib8 22.08.0-2
ii  librsvg2-2   2.54.4+dfsg-1
ii  libstdc++6   12.2.0-1
ii  libtiff5 4.4.0-4
ii  libwebp7 1.2.2-2+b1
ii  libwebpdemux21.2.2-2+b1
ii  libwebpmux3  1.2.2-2+b1
ii  libwmf-0.2-7 0.2.12-5
ii  libwmflite-0.2-7 0.2.12-5
ii  libx11-6 2:1.8.1-2
ii  libxcursor1  1:1.2.1-1
ii  libxext6 2:1.3.4-1
ii  libxfixes3   1:6.0.0-1
ii  libxmu6  2:1.1.3-3
ii  libxpm4  1:3.5.12-1
ii  xdg-utils1.1.3-4.1
ii  zlib1g   1:1.2.11.dfsg-4.1

Versions of packages gimp recommends:
ii  ghostscript  9.56.1~dfsg-1

Versions of packages gimp suggests:
ii  gimp-data-extras  1:2.0.2-1.1
ii  gimp-help-en [gimp-help]  2.10.0-1
ii  gvfs-backends 1.50.2-1
ii  libasound21.2.7.2-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: glib2.0
Source-Version: 2.74.0-2
Done: Simon McVittie 

We believe that the bug you reported is fixed in the latest version of
glib2.0, 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 1018...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated glib2.0 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, 27 Sep 2022 09:53:09 +0100
Source: glib2.0
Architecture: source
Version: 2.74.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Closes: 1018105
Changes:
 glib2.0 (2.74.0-2) unstable; urgency=medium
 .
   * d/p/Empty-values-are-not-valid-GParamSpec.patch:
 Add patch from upstream to fix GIMP crashes with GLib 2.74.0
 (Closes: #1018105)
   * 

Bug#1020844: haskell-gi-harfbuzz FTBFS: error: Could not find module ‘GI.Freetype2.Structs.Face’

[Adrian Bunk]

Source: haskell-gi-harfbuzz
Version: 0.0.5-1
Severity: serious
Tags: ftbfs
Forwarded: 
https://github.com/haskell-gi/haskell-gi/commit/6c2440aa0cc340c87f8a03a765b9494d311b

https://buildd.debian.org/status/fetch.php?pkg=haskell-gi-harfbuzz=amd64=0.0.5-1%2Bb2=1664186335=0

...
GI/HarfBuzz/Functions.hs:1772:1: error:
Could not find module ‘GI.Freetype2.Structs.Face’
Use -v (or `:set -v` in ghci) to see a list of the files searched for.
 |
1772 | import qualified GI.Freetype2.Structs.Face as Freetype2.Face
 | 
...

Bug#1020840: arcanist fails with 'Toolset "arcanist" is unknown'

[Taavi Väänänen]

Package: arcanist
Version: 0~git20220903-1
Severity: grave

Hello. A recent update to the Arcanist packaging moved the binary from
/usr/bin/arc to /usr/bin/arcanist. The binary name change makes the CLI
fail to function properly:

taavi@runko:~ $ arcanist
USAGE EXCEPTION  Toolset "arcanist" is unknown. The binary should be
executed so that "argv[0]" identifies a supported toolset. Rename the
binary or install the library that provides the desired toolset.
Current available toolsets: arc, phage.

Thanks!

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.19.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
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 arcanist depends on:
ii  debconf [debconf-2.0]   1.5.79
ii  libphutil   0~git20220903-1
ii  php-cli 2:8.1+92
ii  php-curl2:8.1+92
ii  php-xml 2:8.1+92
ii  php8.1-cli [php-cli]8.1.5-1+b1
ii  php8.1-curl [php-curl]  8.1.5-1+b1
ii  php8.1-xml [php-xml]8.1.5-1+b1

arcanist recommends no packages.

Versions of packages arcanist suggests:
pn  python  

-- debconf information excluded

Bug#1020837: gajim: Dependency to gtk 3.24.30 not available in backports

[Martin]

Oh, damned. Will try a fix later this day.
Sorry for the inconvenience!

Processed: cleanup dh_elpa_test bugs 10/n

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign  1020187  src:emacs-buttercup
Bug #1020187 [elpa-buttercup] ido-ubiquitous: FTBFS: make: *** [debian/rules:4: 
binary] Error 25
Bug reassigned from package 'elpa-buttercup' to 'src:emacs-buttercup'.
Ignoring request to alter found versions of bug #1020187 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1020187 to the same values 
previously set
> forcemerge 1020095 1020187
Bug #1020095 {Done: David Bremner } [src:emacs-buttercup] 
emacs-buttercup: FTBFS: make[1]: *** [Makefile:16: test-docs] Error 255
Bug #1020187 [src:emacs-buttercup] ido-ubiquitous: FTBFS: make: *** 
[debian/rules:4: binary] Error 25
Marked Bug as done
Marked as fixed in versions emacs-buttercup/1.26-1.
Marked as found in versions emacs-buttercup/1.24-1.
Merged 1020095 1020187
> affects   1020095 +ido-ubiquitous
Bug #1020095 {Done: David Bremner } [src:emacs-buttercup] 
emacs-buttercup: FTBFS: make[1]: *** [Makefile:16: test-docs] Error 255
Bug #1020187 {Done: David Bremner } [src:emacs-buttercup] 
ido-ubiquitous: FTBFS: make: *** [debian/rules:4: binary] Error 25
Added indication that 1020095 affects ido-ubiquitous
Added indication that 1020187 affects ido-ubiquitous
> tag 1020187 -bookworm
Bug #1020187 {Done: David Bremner } [src:emacs-buttercup] 
ido-ubiquitous: FTBFS: make: *** [debian/rules:4: binary] Error 25
Bug #1020095 {Done: David Bremner } [src:emacs-buttercup] 
emacs-buttercup: FTBFS: make[1]: *** [Makefile:16: test-docs] Error 255
Ignoring request to alter tags of bug #1020187 to the same tags previously set
Ignoring request to alter tags of bug #1020095 to the same tags previously set
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
1020095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020095
1020187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020187
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 1020171

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1020171 + pending
Bug #1020171 [src:paredit-everywhere] paredit-everywhere: FTBFS: make: *** 
[debian/rules:7: binary] Error 25
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1020171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020171
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1020788: marked as done (dh-raku: Failed to create directory '/sbuild-nonexistent/.raku/short')

[Debian Bug Tracking System]

Your message dated Tue, 27 Sep 2022 10:34:28 +
with message-id 
and subject line Bug#1020788: fixed in dh-raku 0.14
has caused the Debian Bug report #1020788,
regarding dh-raku: Failed to create directory '/sbuild-nonexistent/.raku/short'
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.)


-- 
1020788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020788
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dh-raku
Version: 0.13
Severity: serious
Tags: ftbfs
Control: affects -1 src:raku-getopt-long src:raku-log src:raku-tap-harness 
src:raku-librarycheck src:raku-file-find

https://buildd.debian.org/status/logs.php?pkg=raku-getopt-long=0.3.3-2%2Bb3
https://buildd.debian.org/status/logs.php?pkg=raku-log=0.3.1-4%2Bb1
https://buildd.debian.org/status/logs.php?pkg=raku-tap-harness=0.3.8-2%2Bb1
https://buildd.debian.org/status/logs.php?pkg=raku-librarycheck=0.0.10-3
https://buildd.debian.org/status/logs.php?pkg=raku-file-find=0.1.1-4

...
   dh_raku_build -a
Pre-compiling raku-getopt-long
RAKUDO_LOG_PRECOMP=1 RAKUDO_MODULE_DEBUG=1 
RAKUDO_RERESOLVE_DEPENDENCIES=0 
RAKULIB=inst\#/<>/debian/tmp/pre-compiled/ raku 
/usr/share/perl6/tools/install-dist.raku --for=vendor --from=. 
--to=/<>/debian/tmp/pre-compiled/
 1 RMD: Requested for settings CORE.d
 1 RMD: Loading settings CORE.d
 1 RMD: Loading bytecode from CORE.d.setting.moarvm
 1 RMD: Loading bootstrap Perl6::BOOTSTRAP::v6d
 1 RMD: Requested for settings CORE.c
 1 RMD: Loading settings CORE.c
 1 RMD: Loading bytecode from CORE.c.setting.moarvm
 1 RMD: Loading bootstrap Perl6::BOOTSTRAP::v6c
 1 RMD: Settings CORE.c loaded
 1 RMD: Settings CORE.d loaded
 1 RMD: Attempting 'CompUnit::Repository::Staging' as a pragma
 1 RMD:   'CompUnit::Repository::Staging' is not a valid pragma
 1 RMD: Attempting to load 'CompUnit::Repository::Staging'
 1 RMD:   Late loading 'CompUnit::Repository::Staging'
 1 RMD: Parsing specs: inst#./debian/tmp/pre-compiled/
===SORRY!=== Error while compiling 
/usr/share/perl6/tools/install-dist.raku
Failed to create directory '/sbuild-nonexistent/.raku/short' with mode '0o777': 
Failed to mkdir: No such file or directory
at /usr/share/perl6/tools/install-dist.raku:3
Actually thrown at:
  in any statement_control at /usr/lib/perl6/lib/Perl6/Grammar.moarvm line 1

dh_raku_build: error: RAKUDO_LOG_PRECOMP=1 RAKUDO_MODULE_DEBUG=1 
RAKUDO_RERESOLVE_DEPENDENCIES=0 
RAKULIB=inst\#/<>/debian/tmp/pre-compiled/ raku 
/usr/share/perl6/tools/install-dist.raku --for=vendor --from=. 
--to=/<>/debian/tmp/pre-compiled/ returned exit code 1
make: *** [debian/rules:4: binary-arch] Error 25


This might be caused by

dh-raku (0.13) unstable; urgency=medium

  * dh_raku_build:
...
* remove $HOME setup
...
 -- Dominique Dumont   Sat, 24 Sep 2022 18:16:51 +0200
--- End Message ---
--- Begin Message ---
Source: dh-raku
Source-Version: 0.14
Done: Dominique Dumont 

We believe that the bug you reported is fixed in the latest version of
dh-raku, 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 1020...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dominique Dumont  (supplier of updated dh-raku 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, 27 Sep 2022 12:15:32 +0200
Source: dh-raku
Architecture: source
Version: 0.14
Distribution: unstable
Urgency: medium
Maintainer: Debian Rakudo Maintainers 
Changed-By: Dominique Dumont 
Closes: 1020788
Changes:
 dh-raku (0.14) unstable; urgency=medium
 .
   * Revert "dh_raku_build: remove $HOME setup" (Closes: 1020788)
Checksums-Sha1:
 694cd65d3e2cf87ea06a797a947b3033bcde4e5b 1588 dh-raku_0.14.dsc
 ecd664b196ed5bb24ecce540319645e6cc526663 7480 dh-raku_0.14.tar.xz
 d44e685cd4b8742237c93083ff2f66ae8dbcef0e 7305 dh-raku_0.14_source.buildinfo
Checksums-Sha256:
 ca358c6427fdfb7b2d9b9d6fd0aeaf5b774bf571d25405be1db76d11974c5178 1588 
dh-raku_0.14.dsc
 e4914992da9430197452f1fae72ab6b083ed5809fa0984e33bbd326321c1e683 7480 
dh-raku_0.14.tar.xz
 de38868a549df0b045daca4dfb943f3518cc19c1822bab1002703401270a1085 7305 
dh-raku_0.14_source.buildinfo
Files:
 

Bug#1020837: gajim: Dependency to gtk 3.24.30 not available in backports

[CleVer]

Package: gajim
Version: 1.5.1-1~bpo11+1
Severity: grave
Tags: a11y
Justification: renders package unusable
X-Debbugs-Cc: cle...@zaclys.net

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
I installed gajim 1.5.1 from debian bullseye backports
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
After installing the package, it dit not launch from de desktop. When i tried 
from the console I got an error regarding the dependency to gkt3 3.24.30.
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: 11.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-18-amd64 (SMP w/4 CPU threads)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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 gajim depends on:
ii  desktop-file-utils   0.26-1
ii  gir1.2-gst-plugins-base-1.0  1.18.4-2
ii  gir1.2-gtk-3.0   3.24.24-4+deb11u2
ii  gir1.2-gtksource-4   4.8.0-1
ii  python3  3.9.2-3
ii  python3-cairo1.16.2-4+b2
ii  python3-css-parser   1.0.6-1
ii  python3-gi   3.42.2-2~bpo11+1
ii  python3-gi-cairo 3.42.2-2~bpo11+1
ii  python3-idna 2.10-1
ii  python3-keyring  22.0.1-1
ii  python3-nbxmpp   3.2.2-1~bpo11+1
ii  python3-openssl  20.0.1-1
ii  python3-packaging20.9-2
ii  python3-pil  8.1.2+dfsg-0.3+deb11u1
ii  python3-precis-i18n  1.0.2-3

Versions of packages gajim recommends:
ii  alsa-utils 1.2.4-1
ii  aspell-en [aspell-dictionary]  2018.04.16-0-1
ii  aspell-fr [aspell-dictionary]  0.50-3-8.1
ii  ca-certificates20210119
ii  dbus   1.12.20-2
ii  fonts-noto-color-emoji 0~20200916-1
ii  gajim-omemo2.8.15-1~bpo11+1
ii  gajim-openpgp  1.4.9-1~bpo11+1
ii  gir1.2-farstream-0.2   0.2.9-1
ii  gir1.2-geoclue-2.0 2.5.7-3
ii  gir1.2-gsound-1.0  1.0.2-5
ii  gir1.2-gspell-11.8.4-1
ii  gir1.2-gstreamer-1.0   1.18.4-2.1
ii  gir1.2-gupnpigd-1.01.2.0-1
ii  gir1.2-secret-10.20.4-2
ii  gnome-shell [notification-daemon]  3.38.6-1~deb11u1
ii  gstreamer1.0-plugins-ugly  1.18.4-2
ii  notification-daemon3.20.0-4
ii  pulseaudio-utils   14.2-2
ii  python3-dbus   1.2.16-5
ii  python3-sentry-sdk 0.13.2-1

Versions of packages gajim suggests:
ii  libxss1  1:1.2.3-1
pn  nautilus-sendto  

-- no debconf information

Processed: tagging 1020095

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1020095 - bookworm
Bug #1020095 {Done: David Bremner } [src:emacs-buttercup] 
emacs-buttercup: FTBFS: make[1]: *** [Makefile:16: test-docs] Error 255
Removed tag(s) bookworm.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1020095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020095
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed (with 2 errors): cleanup dh_elpa_test bugs 9/n

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign  1020187  elpa-buttercup
Bug #1020187 [src:ido-ubiquitous] ido-ubiquitous: FTBFS: make: *** 
[debian/rules:4: binary] Error 25
Bug reassigned from package 'src:ido-ubiquitous' to 'elpa-buttercup'.
No longer marked as found in versions ido-ubiquitous/4.14-1.
Ignoring request to alter fixed versions of bug #1020187 to the same values 
previously set
> forcemerge 1020095 1020187
Bug #1020095 {Done: David Bremner } [src:emacs-buttercup] 
emacs-buttercup: FTBFS: make[1]: *** [Makefile:16: test-docs] Error 255
Unable to merge bugs because:
package of #1020187 is 'elpa-buttercup' not 'src:emacs-buttercup'
Failed to forcibly merge 1020095: Did not alter merged bugs.

> affects   1020095 +ido-ubiquitous
Failed to mark 1020095 as affecting package(s): failed to get lock on 
/srv/bugs.debian.org/spool/lock/1020095 -- Unable to lock 
/srv/bugs.debian.org/spool/lock/1020095 Resource temporarily unavailable.
Unable to lock /srv/bugs.debian.org/spool/lock/1020095 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1020095 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1020095 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1020095 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1020095 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1020095 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1020095 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1020095 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1020095 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
 at /usr/local/lib/site_perl/Debbugs/Common.pm line 650.

> tag 1020187 -bookworm
Bug #1020187 [elpa-buttercup] ido-ubiquitous: FTBFS: make: *** [debian/rules:4: 
binary] Error 25
Removed tag(s) bookworm.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
1020095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020095
1020187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020187
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1020788: dh-raku: Failed to create directory '/sbuild-nonexistent/.raku/short'

[Dominique Dumont]

On Mon, 26 Sep 2022 21:26:45 +0300 Adrian Bunk  wrote:
> Package: dh-raku
> Version: 0.13

I knew this was not a good version number ;-)

I'll fix this soon.

Thanks for the report.

All the best

Processed: gdb: FTBFS with readline 8.2 due to constness changes

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> merge 1018821 1020032
Bug #1018821 [src:gdb] gdb: FTBFS with readline 8.2 due to constness changes
Bug #1020032 [src:gdb] gdb: FTBFS: completer.c:2014:10: error: invalid 
conversion from ‘const char*’ to ‘char*’ [-fpermissive]
Added tag(s) patch and fixed-upstream.
Bug #1018821 [src:gdb] gdb: FTBFS with readline 8.2 due to constness changes
Added tag(s) bookworm and sid.
Merged 1018821 1020032
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1018821: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018821
1020032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020032
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 1020179

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1020179 - bookworm
Bug #1020179 [dh-elpa] "dh_elpa_test should not cache native code in 
non-writable $HOME"
Bug #1020186 [dh-elpa] markdown-toc-el: FTBFS: make: *** [debian/rules:4: 
binary] Error 25
Bug #1020191 [dh-elpa] ebib: FTBFS: make: *** [debian/rules:4: build] Error 25
Bug #1020196 [dh-elpa] use-package: FTBFS: make: *** [debian/rules:4: binary] 
Error 25
Bug #1020203 [dh-elpa] package-lint-el: FTBFS: make: *** [debian/rules:4: 
binary] Error 25
Bug #1020204 [dh-elpa] elisp-refs: FTBFS: make: *** [debian/rules:4: binary] 
Error 25
Bug #1020210 [dh-elpa] emacs-websocket: FTBFS: make: *** [debian/rules:4: 
binary] Error 25
Removed tag(s) bookworm.
Removed tag(s) bookworm.
Removed tag(s) bookworm.
Removed tag(s) bookworm.
Removed tag(s) bookworm.
Removed tag(s) bookworm.
Removed tag(s) bookworm.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1020179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020179
1020186: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020186
1020191: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020191
1020196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020196
1020203: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020203
1020204: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020204
1020210: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020210
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 1020177

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1020177 - bookworm
Bug #1020177 {Done: David Bremner } [src:gnuplot-mode] 
gnuplot-mode: FTBFS: mkdir: cannot create directory ‘././sbuild-nonexistent’: 
Permission denied
Removed tag(s) bookworm.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1020177: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020177
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1019695: r-cran-qpdf: FTBFS with qpdf 11.0.0

[Andreas Tille]

Control: tags -1 upstream
Control: forwarded -1 https://github.com/ropensci/qpdf/issues/20

Processed: Re: r-cran-qpdf: FTBFS with qpdf 11.0.0

[Debian Bug Tracking System]

Processing control commands:

> tags -1 upstream
Bug #1019695 [src:r-cran-qpdf] r-cran-qpdf: FTBFS with qpdf 11.0.0
Added tag(s) upstream.
> forwarded -1 https://github.com/ropensci/qpdf/issues/20
Bug #1019695 [src:r-cran-qpdf] r-cran-qpdf: FTBFS with qpdf 11.0.0
Set Bug forwarded-to-address to 'https://github.com/ropensci/qpdf/issues/20'.

-- 
1019695: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019695
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1016085: any progress?

[Johannes Sebastian Lade]

I just wanted to ask if there is any progress on this bug?

Bug#1020073: [Debian-pan-maintainers] Bug#1020073: pyfai: FTBFS: distutils.errors.DistutilsError: Command '['/usr/bin/python3.10', '-m', 'pip', '--disable-pip-version-check', 'wheel', '--no-deps', '-w

[Jerome Kieffer]

Hi Lucas,

All my packages (and probably many more) are marked for removal because of this 
bug.

I believe this bugs comes from a specificity of Debian which does not
install python3-pip together with python3. If python3-pip is now needed by
pybuild it should be a build dependency.

Cheers,

Jerome


On Sun, 18 Sep 2022 08:31:39 +0200
Lucas Nussbaum  wrote:

> Source: pyfai
> Version: 0.21.3+dfsg1-1
> 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.
> 
> 
> Relevant part (hopefully):
> >  fakeroot debian/rules clean
> > dh clean --buildsystem=pybuild
> >dh_auto_clean -O--buildsystem=pybuild
> > install -d 
> > /<>/pyfai-0.21.3\+dfsg1/debian/.debhelper/generated/_source/home
> > pybuild --clean -i python{version} -p 3.10
> > I: pybuild base:240: python3.10 setup.py clean 
> > /<>/setup.py:43: 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
> > /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning: 
> > Distutils was imported before Setuptools, but importing Setuptools also 
> > replaces the `distutils` module in `sys.modules`. This may lead to 
> > undesirable behaviors or errors. To avoid these issues, avoid using 
> > distutils directly, ensure that setuptools is installed in the traditional 
> > way (e.g. not an editable install), and/or make sure that setuptools is 
> > always imported before distutils.
> >   warnings.warn(
> > /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning: 
> > Setuptools is replacing distutils.
> >   warnings.warn("Setuptools is replacing distutils.")
> > INFO: Disabling color, you really want to install colorlog.
> > INFO:pythran:Disabling color, you really want to install colorlog.
> > INFO:pyFAI.setup:Use setuptools with cython
> > INFO:pyFAI.setup:Use setuptools.setup
> > /usr/lib/python3/dist-packages/setuptools/installer.py:27: 
> > SetuptoolsDeprecationWarning: setuptools.installer is deprecated. 
> > Requirements should be satisfied by a PEP 517 installer.
> >   warnings.warn(
> > /usr/lib/python3/dist-packages/setuptools/installer.py:34: UserWarning: 
> > Unbuilt egg for pyFAI [unknown version] (/<>)
> >   pkg_resources.get_distribution('wheel')
> > WARNING: The wheel package is not available.
> > /usr/lib/python3/dist-packages/setuptools/installer.py:60: UserWarning: 
> > Unbuilt egg for pyFAI [unknown version] (/<>)
> >   environment = pkg_resources.Environment()
> > /usr/bin/python3.10: No module named pip
> > Traceback (most recent call last):
> >   File "/usr/lib/python3/dist-packages/setuptools/installer.py", line 82, 
> > in fetch_build_egg
> > subprocess.check_call(cmd)
> >   File "/usr/lib/python3.10/subprocess.py", line 369, in check_call
> > raise CalledProcessError(retcode, cmd)
> > subprocess.CalledProcessError: Command '['/usr/bin/python3.10', '-m', 
> > 'pip', '--disable-pip-version-check', 'wheel', '--no-deps', '-w', 
> > '/tmp/tmpymrbi1ta', '--quiet', 'setuptools<60.0.0']' returned non-zero exit 
> > status 1.
> > 
> > The above exception was the direct cause of the following exception:
> > 
> > Traceback (most recent call last):
> >   File "/<>/setup.py", line 1137, in 
> > setup_package()
> >   File "/<>/setup.py", line 1133, in setup_package
> > setup(**setup_kwargs)
> >   File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 86, in 
> > setup
> > _install_setup_requires(attrs)
> >   File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 80, in 
> > _install_setup_requires
> > dist.fetch_build_eggs(dist.setup_requires)
> >   File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 875, in 
> > fetch_build_eggs
> > resolved_dists = pkg_resources.working_set.resolve(
> >   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 
> > 789, in resolve
> > dist = best[req.key] = env.best_match(
> >   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 
> > 1075, in best_match
> > return self.obtain(req, installer)
> >   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 
> > 1087, in obtain
> > return installer(requirement)
> >   File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 945, in 
> > fetch_build_egg
> > return fetch_build_egg(self, req)
> >   File "/usr/lib/python3/dist-packages/setuptools/installer.py", line 84, 
> > in fetch_build_egg
> > raise DistutilsError(str(e)) from e
> > distutils.errors.DistutilsError: Command '['/usr/bin/python3.10', '-m', 
> > 'pip', '--disable-pip-version-check', 'wheel', '--no-deps', '-w', 
> > '/tmp/tmpymrbi1ta', '--quiet', 'setuptools<60.0.0']' returned non-zero exit 
> 

Bug#1020129: marked as done (python-avro: FTBFS: AttributeError: module 'distutils' has no attribute 'log')

[Debian Bug Tracking System]

Your message dated Tue, 27 Sep 2022 09:34:44 +
with message-id 
and subject line Bug#1020129: fixed in python-avro 1.11.1+dfsg-1
has caused the Debian Bug report #1020129,
regarding python-avro: FTBFS: AttributeError: module 'distutils' has no 
attribute 'log'
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.)


-- 
1020129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020129
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-avro
Version: 1.11.0+dfsg-1
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.


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_clean
> I: pybuild base:240: python3.10 setup.py clean 
> /<>/lang/py/setup.py:21: DeprecationWarning: The distutils 
> package is deprecated and slated for removal in Python 3.12. Use setuptools 
> or check PEP 632 for potential alternatives
>   import distutils.errors
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning: 
> Distutils was imported before Setuptools, but importing Setuptools also 
> replaces the `distutils` module in `sys.modules`. This may lead to 
> undesirable behaviors or errors. To avoid these issues, avoid using distutils 
> directly, ensure that setuptools is installed in the traditional way (e.g. 
> not an editable install), and/or make sure that setuptools is always imported 
> before distutils.
>   warnings.warn(
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning: 
> Setuptools is replacing distutils.
>   warnings.warn("Setuptools is replacing distutils.")
> Traceback (most recent call last):
>   File "/<>/lang/py/setup.py", line 135, in 
> main()
>   File "/<>/lang/py/setup.py", line 125, in main
> _generate_package_data()
>   File "/<>/lang/py/setup.py", line 51, in _generate_package_data
> distutils.log.info("Generating package data")
> AttributeError: module 'distutils' has no attribute 'log'
> E: pybuild pybuild:379: clean: plugin distutils failed with: exit code=1: 
> python3.10 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.10 --dir 
> lang/py returned exit code 13
> make[1]: *** [debian/rules:28: override_dh_auto_clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2022/09/17/python-avro_1.11.0+dfsg-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220917;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220917=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 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-avro
Source-Version: 1.11.1+dfsg-1
Done: Andreas Tille 

We believe that the bug you reported is fixed in the latest version of
python-avro, 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 1020...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated python-avro 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, 27 Sep 2022 11:13:17 +0200
Source: python-avro
Architecture: source
Version: 1.11.1+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Andreas Tille 
Closes: 1020129
Changes:
 python-avro (1.11.1+dfsg-1) unstable; urgency=medium
 .
   * Team upload.
   * Fix watch file
   * Standards-Version: 4.6.1 (routine-update)
   * Build-Depends: pybuild-plugin-pyproject
 Closes: #1020129
   * Lintian-overrides for false positives
Checksums-Sha1:
 

Processed: Re: Bug#1020035: seqan3: FTBFS: char_traits.h:431:56: error: ‘void* __builtin_memcpy(void*, const void*, long unsigned int) ’ accessing 9223372036854775810 or more bytes at offsets 4 and 3

[Debian Bug Tracking System]

Processing control commands:

> tags -1 upstream, help
Bug #1020035 [src:seqan3] seqan3: FTBFS: char_traits.h:431:56: error: ‘void* 
__builtin_memcpy(void*, const void*, long unsigned int)’ accessing 
9223372036854775810 or more bytes at offsets 4 and 3 may overlap up to 
9223372036854775813 bytes at offset -3 [-Werror=restrict]
Added tag(s) help and upstream.
> forwarded -1 https://github.com/seqan/seqan3/issues/3054
Bug #1020035 [src:seqan3] seqan3: FTBFS: char_traits.h:431:56: error: ‘void* 
__builtin_memcpy(void*, const void*, long unsigned int)’ accessing 
9223372036854775810 or more bytes at offsets 4 and 3 may overlap up to 
9223372036854775813 bytes at offset -3 [-Werror=restrict]
Set Bug forwarded-to-address to 'https://github.com/seqan/seqan3/issues/3054'.

-- 
1020035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020035
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1020035: seqan3: FTBFS: char_traits.h:431:56: error: ‘void* __builtin_memcpy(void*, const void*, long unsigned int) ’ accessing 9223372036854775810 or more bytes at offsets 4 and 3 may overlap up

[Andreas Tille]

Control: tags -1 upstream, help
Control: forwarded -1 https://github.com/seqan/seqan3/issues/3054

Bug#1020833: openmsx-catapult: flaky autopkgtest: dogtail.tree.SearchError: child of [desktop frame | main]: "openmsx-catapult" application

[Simon McVittie]

Source: openmsx-catapult
Version: 18.0-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky

The autopkgtest for openmsx-catapult seems to be intermittently failing
like this:

> Warning: AT-SPI's desktop is visible but it has no children. Are you running 
> any AT-SPI-aware applications?
> Clicking on [check box | Check for working hardware configurations after 
> closing this dialog]
> Mouse button 1 click at (236.5,79.0)
> Clicking on [push button | OK]
> Mouse button 1 click at (330.5,129.0)
> Clicking on [menu | File]
> Mouse button 1 click at (19.5,12.5)
> Clicking on [menu item | Test MSX Hardware]
> Mouse button 1 click at (117.5,37.5)
> searching for child of [desktop frame | main]: "openmsx-catapult" application 
> (attempt 3)
> searching for child of [desktop frame | main]: "openmsx-catapult" application 
> (attempt 4)
> searching for child of [desktop frame | main]: "openmsx-catapult" application 
> (attempt 5)
> searching for child of [desktop frame | main]: "openmsx-catapult" application 
> (attempt 6)
> searching for child of [desktop frame | main]: "openmsx-catapult" application 
> (attempt 7)
> searching for child of [desktop frame | main]: "openmsx-catapult" application 
> (attempt 8)
> searching for child of [desktop frame | main]: "openmsx-catapult" application 
> (attempt 9)
> searching for child of [desktop frame | main]: "openmsx-catapult" application 
> (attempt 10)
> searching for child of [desktop frame | main]: "openmsx-catapult" application 
> (attempt 11)
> searching for child of [desktop frame | main]: "openmsx-catapult" application 
> (attempt 12)
> searching for child of [desktop frame | main]: "openmsx-catapult" application 
> (attempt 13)
> searching for child of [desktop frame | main]: "openmsx-catapult" application 
> (attempt 14)
> searching for child of [desktop frame | main]: "openmsx-catapult" application 
> (attempt 15)
> searching for child of [desktop frame | main]: "openmsx-catapult" application 
> (attempt 16)
> searching for child of [desktop frame | main]: "openmsx-catapult" application 
> (attempt 17)
> searching for child of [desktop frame | main]: "openmsx-catapult" application 
> (attempt 18)
> searching for child of [desktop frame | main]: "openmsx-catapult" application 
> (attempt 19)
> Traceback (most recent call last):
>   File 
> "/tmp/autopkgtest-lxc.nboffbe8/downtmp/build.7HA/src/debian/tests/run.py", 
> line 83, in 
> test_detect()
>   File 
> "/tmp/autopkgtest-lxc.nboffbe8/downtmp/build.7HA/src/debian/tests/run.py", 
> line 56, in test_detect
> done = find('Done', idx = 1)
>   File 
> "/tmp/autopkgtest-lxc.nboffbe8/downtmp/build.7HA/src/debian/tests/run.py", 
> line 21, in find
> window = tree.root.application('openmsx-catapult')
>   File "/usr/lib/python3/dist-packages/dogtail/tree.py", line 1173, in 
> application
> return root.findChild(predicate.IsAnApplicationNamed(appName), 
> recursive=False, retry=retry, showingOnly=False)
>   File "/usr/lib/python3/dist-packages/dogtail/tree.py", line 939, in 
> findChild
> raise SearchError(describeSearch(self, pred, recursive, debugName))
> dogtail.tree.SearchError: child of [desktop frame | main]: "openmsx-catapult" 
> application

for example in

and
.

When testing a proposed update to a package it depends on (such as
glib2.0 and xorg-server in those logs), a test failure like this is
assumed to be a regression in the updated package, which can delay or
prevent testing migration.

Please look into whether this test can be made reliable, or if it cannot,
mark the test with "Restrictions: flaky" so that it doesn't disrupt other
packages.

Thanks,
smcv

Bug#1020832: openmsx-catapult: flaky autopkgtest: "local variable 'done' referenced before assignment"

[Simon McVittie]

Source: openmsx-catapult
Version: 18.0-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky

The autopkgtest for openmsx-catapult seems to be intermittently failing
like this:

> Traceback (most recent call last):
>   File 
> "/tmp/autopkgtest-lxc.7f56s1c5/downtmp/build.0aM/src/debian/tests/run.py", 
> line 83, in 
> test_detect()
>   File 
> "/tmp/autopkgtest-lxc.7f56s1c5/downtmp/build.0aM/src/debian/tests/run.py", 
> line 60, in test_detect
> done.click()
> UnboundLocalError: local variable 'done' referenced before assignment

for example in

and
.

When testing a proposed update to a package it depends on (such as dbus
and gcc-12, in this case), a test failure like this is assumed to be a
regression in the updated package, which can delay or prevent testing
migration.

Please look into whether this test can be made reliable, or if it cannot,
mark the test with "Restrictions: flaky" so that it doesn't disrupt other
packages.

In this case I suspect this is a bug in the test script rather than the
upstream code.

Thanks,
smcv

Processed: Bug#1018105 marked as pending in glib2.0

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1018105 [glib2.0] gimp: crashes when adding text to image
Bug #1019970 [glib2.0] gimp: Typing on a text box layer, a segfault occurs
Bug #1020261 [glib2.0] gimp: GIMP crashes when interacting with text
Bug #1020266 [glib2.0] gimp: GIMP crash frequently
Bug #1020339 [glib2.0] Gimp crash when use Text tool
Bug #1020532 [glib2.0] gimp: text element crashes gimp
Bug #1020608 [glib2.0] GIMP crashed with a fatal error
Bug #1020663 [glib2.0] GIMP crashes when trying to using test tool
Bug #1020682 [glib2.0] GIMP - segfaults using Text tool on large XCF/JPG image; 
gimp unstable thereafter; corrupting the gimp config?
Bug #1020701 [glib2.0] gimp: Gimp crash when write on text box
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.

-- 
1018105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018105
1019970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019970
1020261: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020261
1020266: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020266
1020339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020339
1020532: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020532
1020608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020608
1020663: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020663
1020682: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020682
1020701: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020701
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1018105: marked as pending in glib2.0

[Simon McVittie]

Control: tag -1 pending

Hello,

Bug #1018105 in glib2.0 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/gnome-team/glib/-/commit/1790e2f6e66799096af5f8f6f8e6b7a31cc617ff


Add various post-release bug fixes from upstream

Closes: #1018105


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1018105

Processed: reassign 1020701 to glib2.0, forcibly merging 1018105 1020701

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 1020701 glib2.0 2.74.0-1
Bug #1020701 [gimp] gimp: Gimp crash when write on text box
Bug reassigned from package 'gimp' to 'glib2.0'.
No longer marked as found in versions gimp/2.10.32-1.
Ignoring request to alter fixed versions of bug #1020701 to the same values 
previously set
Bug #1020701 [glib2.0] gimp: Gimp crash when write on text box
There is no source info for the package 'glib2.0' at version '2.74.0-1' with 
architecture ''
Unable to make a source version for version '2.74.0-1'
Marked as found in versions 2.74.0-1.
> forcemerge 1018105 1020701
Bug #1018105 [glib2.0] gimp: crashes when adding text to image
Bug #1019970 [glib2.0] gimp: Typing on a text box layer, a segfault occurs
Bug #1020261 [glib2.0] gimp: GIMP crashes when interacting with text
Bug #1020266 [glib2.0] gimp: GIMP crash frequently
Bug #1020339 [glib2.0] Gimp crash when use Text tool
Bug #1020532 [glib2.0] gimp: text element crashes gimp
Bug #1020608 [glib2.0] GIMP crashed with a fatal error
Bug #1020663 [glib2.0] GIMP crashes when trying to using test tool
Bug #1020682 [glib2.0] GIMP - segfaults using Text tool on large XCF/JPG image; 
gimp unstable thereafter; corrupting the gimp config?
Bug #1020701 [glib2.0] gimp: Gimp crash when write on text box
Set Bug forwarded-to-address to 
'https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2921'.
Severity set to 'serious' from 'normal'
Added indication that 1020701 affects gimp
Added tag(s) patch.
Bug #1019970 [glib2.0] gimp: Typing on a text box layer, a segfault occurs
Bug #1020261 [glib2.0] gimp: GIMP crashes when interacting with text
Bug #1020266 [glib2.0] gimp: GIMP crash frequently
Bug #1020339 [glib2.0] Gimp crash when use Text tool
Bug #1020532 [glib2.0] gimp: text element crashes gimp
Bug #1020608 [glib2.0] GIMP crashed with a fatal error
Bug #1020663 [glib2.0] GIMP crashes when trying to using test tool
Bug #1020682 [glib2.0] GIMP - segfaults using Text tool on large XCF/JPG image; 
gimp unstable thereafter; corrupting the gimp config?
Merged 1018105 1019970 1020261 1020266 1020339 1020532 1020608 1020663 1020682 
1020701
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1018105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018105
1019970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019970
1020261: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020261
1020266: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020266
1020339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020339
1020532: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020532
1020608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020608
1020663: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020663
1020682: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020682
1020701: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020701
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: bug 1018105 is forwarded to https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2921 ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 1018105 https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2921
Bug #1018105 [glib2.0] gimp: crashes when adding text to image
Bug #1019970 [glib2.0] gimp: Typing on a text box layer, a segfault occurs
Bug #1020261 [glib2.0] gimp: GIMP crashes when interacting with text
Bug #1020266 [glib2.0] gimp: GIMP crash frequently
Bug #1020339 [glib2.0] Gimp crash when use Text tool
Bug #1020532 [glib2.0] gimp: text element crashes gimp
Bug #1020608 [glib2.0] GIMP crashed with a fatal error
Bug #1020663 [glib2.0] GIMP crashes when trying to using test tool
Bug #1020682 [glib2.0] GIMP - segfaults using Text tool on large XCF/JPG image; 
gimp unstable thereafter; corrupting the gimp config?
Set Bug forwarded-to-address to 
'https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2921'.
Set Bug forwarded-to-address to 
'https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2921'.
Set Bug forwarded-to-address to 
'https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2921'.
Set Bug forwarded-to-address to 
'https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2921'.
Set Bug forwarded-to-address to 
'https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2921'.
Set Bug forwarded-to-address to 
'https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2921'.
Set Bug forwarded-to-address to 
'https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2921'.
Set Bug forwarded-to-address to 
'https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2921'.
Set Bug forwarded-to-address to 
'https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2921'.
> tags 1018105 + patch
Bug #1018105 [glib2.0] gimp: crashes when adding text to image
Bug #1019970 [glib2.0] gimp: Typing on a text box layer, a segfault occurs
Bug #1020261 [glib2.0] gimp: GIMP crashes when interacting with text
Bug #1020266 [glib2.0] gimp: GIMP crash frequently
Bug #1020339 [glib2.0] Gimp crash when use Text tool
Bug #1020532 [glib2.0] gimp: text element crashes gimp
Bug #1020608 [glib2.0] GIMP crashed with a fatal error
Bug #1020663 [glib2.0] GIMP crashes when trying to using test tool
Bug #1020682 [glib2.0] GIMP - segfaults using Text tool on large XCF/JPG image; 
gimp unstable thereafter; corrupting the gimp config?
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1018105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018105
1019970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019970
1020261: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020261
1020266: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020266
1020339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020339
1020532: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020532
1020608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020608
1020663: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020663
1020682: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020682
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: reassign 1018105 to glib2.0, affects 1018105, severity of 1018105 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 1018105 glib2.0 2.74.0-1
Bug #1018105 [gimp] gimp: crashes when adding text to image
Bug #1019970 [gimp] gimp: Typing on a text box layer, a segfault occurs
Bug #1020261 [gimp] gimp: GIMP crashes when interacting with text
Bug #1020266 [gimp] gimp: GIMP crash frequently
Bug #1020339 [gimp] Gimp crash when use Text tool
Bug #1020532 [gimp] gimp: text element crashes gimp
Bug #1020608 [gimp] GIMP crashed with a fatal error
Bug #1020663 [gimp] GIMP crashes when trying to using test tool
Bug #1020682 [gimp] GIMP - segfaults using Text tool on large XCF/JPG image; 
gimp unstable thereafter; corrupting the gimp config?
Bug reassigned from package 'gimp' to 'glib2.0'.
Bug reassigned from package 'gimp' to 'glib2.0'.
Bug reassigned from package 'gimp' to 'glib2.0'.
Bug reassigned from package 'gimp' to 'glib2.0'.
Bug reassigned from package 'gimp' to 'glib2.0'.
Bug reassigned from package 'gimp' to 'glib2.0'.
Bug reassigned from package 'gimp' to 'glib2.0'.
Bug reassigned from package 'gimp' to 'glib2.0'.
Bug reassigned from package 'gimp' to 'glib2.0'.
No longer marked as found in versions gimp/2.99.10-1 and gimp/2.10.32-1.
No longer marked as found in versions gimp/2.99.10-1 and gimp/2.10.32-1.
No longer marked as found in versions gimp/2.10.32-1 and gimp/2.99.10-1.
No longer marked as found in versions gimp/2.10.32-1 and gimp/2.99.10-1.
No longer marked as found in versions gimp/2.10.32-1 and gimp/2.99.10-1.
No longer marked as found in versions gimp/2.99.10-1 and gimp/2.10.32-1.
No longer marked as found in versions gimp/2.99.10-1 and gimp/2.10.32-1.
No longer marked as found in versions gimp/2.99.10-1 and gimp/2.10.32-1.
No longer marked as found in versions gimp/2.99.10-1 and gimp/2.10.32-1.
Ignoring request to alter fixed versions of bug #1018105 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1019970 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1020261 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1020266 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1020339 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1020532 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1020608 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1020663 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1020682 to the same values 
previously set
Bug #1018105 [glib2.0] gimp: crashes when adding text to image
Bug #1019970 [glib2.0] gimp: Typing on a text box layer, a segfault occurs
Bug #1020261 [glib2.0] gimp: GIMP crashes when interacting with text
Bug #1020266 [glib2.0] gimp: GIMP crash frequently
Bug #1020339 [glib2.0] Gimp crash when use Text tool
Bug #1020532 [glib2.0] gimp: text element crashes gimp
Bug #1020608 [glib2.0] GIMP crashed with a fatal error
Bug #1020663 [glib2.0] GIMP crashes when trying to using test tool
Bug #1020682 [glib2.0] GIMP - segfaults using Text tool on large XCF/JPG image; 
gimp unstable thereafter; corrupting the gimp config?
There is no source info for the package 'glib2.0' at version '2.74.0-1' with 
architecture ''
Unable to make a source version for version '2.74.0-1'
Marked as found in versions 2.74.0-1.
Marked as found in versions 2.74.0-1.
Marked as found in versions 2.74.0-1.
Marked as found in versions 2.74.0-1.
Marked as found in versions 2.74.0-1.
Marked as found in versions 2.74.0-1.
Marked as found in versions 2.74.0-1.
Marked as found in versions 2.74.0-1.
Marked as found in versions 2.74.0-1.
> affects 1018105 + gimp
Bug #1018105 [glib2.0] gimp: crashes when adding text to image
Bug #1019970 [glib2.0] gimp: Typing on a text box layer, a segfault occurs
Bug #1020261 [glib2.0] gimp: GIMP crashes when interacting with text
Bug #1020266 [glib2.0] gimp: GIMP crash frequently
Bug #1020339 [glib2.0] Gimp crash when use Text tool
Bug #1020532 [glib2.0] gimp: text element crashes gimp
Bug #1020608 [glib2.0] GIMP crashed with a fatal error
Bug #1020663 [glib2.0] GIMP crashes when trying to using test tool
Bug #1020682 [glib2.0] GIMP - segfaults using Text tool on large XCF/JPG image; 
gimp unstable thereafter; corrupting the gimp config?
Added indication that 1018105 affects gimp
Added indication that 1019970 affects gimp
Added indication that 1020261 affects gimp
Added indication that 1020266 affects gimp
Added indication that 1020339 affects gimp
Added indication that 1020532 affects gimp
Added indication that 1020608 affects gimp
Added indication that 1020663 affects gimp
Added indication that 1020682 affects gimp
> severity 1018105 serious
Bug #1018105 [glib2.0] gimp: crashes when adding text to image
Bug #1019970 [glib2.0] gimp: Typing on a text box layer, a segfault occurs
Bug #1020261 [glib2.0] gimp: GIMP crashes when interacting with text
Bug 

Bug#963445: fixed 963445 in 22.03-1, closing 963445

[Chow Loong Jin]

fixed 963445 22.03-1
close 963445 22.03-1
thanks

Fixed in 22.03-1

-- 
Kind regards,
Loong Jin

Processed: fixed 963445 in 22.03-1, closing 963445

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> fixed 963445 22.03-1
Bug #963445 [src:mediaconch] mediaconch: FTBFS: dh: error: Unknown sequence 
configure-Project/GNU/CLI/ (choose from: binary binary-arch binary-indep build 
build-arch build-indep clean install install-arch install-indep)
Marked as fixed in versions mediaconch/22.03-1.
> close 963445 22.03-1
Bug #963445 [src:mediaconch] mediaconch: FTBFS: dh: error: Unknown sequence 
configure-Project/GNU/CLI/ (choose from: binary binary-arch binary-indep build 
build-arch build-indep clean install install-arch install-indep)
Ignoring request to alter fixed versions of bug #963445 to the same values 
previously set
Bug #963445 [src:mediaconch] mediaconch: FTBFS: dh: error: Unknown sequence 
configure-Project/GNU/CLI/ (choose from: binary binary-arch binary-indep build 
build-arch build-indep clean install install-arch install-indep)
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
963445: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963445
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#997514: fixed 997514 in 0.3.4+dfsg-2, closing 997514

[Chow Loong Jin]

fixed 997514 0.3.4+dfsg-2
close 997514 0.3.4+dfsg-2
thanks

Bug #997514 was fixed in 0.3.4+dfsg-2

-- 
Kind regards,
Loong Jin

Processed: fixed 997514 in 0.3.4+dfsg-2, closing 997514

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> fixed 997514 0.3.4+dfsg-2
Bug #997514 [src:ctpl] ctpl: FTBFS: dh_auto_test: error: make -j1 check 
VERBOSE=1 returned exit code 2
The source 'ctpl' and version '0.3.4+dfsg-2' do not appear to match any binary 
packages
Marked as fixed in versions ctpl/0.3.4+dfsg-2.
> close 997514 0.3.4+dfsg-2
Bug #997514 [src:ctpl] ctpl: FTBFS: dh_auto_test: error: make -j1 check 
VERBOSE=1 returned exit code 2
The source 'ctpl' and version '0.3.4+dfsg-2' do not appear to match any binary 
packages
Ignoring request to alter fixed versions of bug #997514 to the same values 
previously set
Bug #997514 [src:ctpl] ctpl: FTBFS: dh_auto_test: error: make -j1 check 
VERBOSE=1 returned exit code 2
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
997514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997514
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1020779: [3dprinter-general] Bug#1020779: slic3r-prusa: FTBFS on 32-bit arches

[Gregor Riepl]

Do you have a bit more context for this?

From the log, I can't see what the actual issue is.
Is it an autoconf check that fails or an actual compilation issue?

If it's a check, which one?

If it's actually in the source, the error doesn't make any sense. 
Compilation is done without -Werror, and the deprecation message is only 
a warning.

Bug#1020702: [3dprinter-general] Bug#1020702: prusa-slicer: SEGV on start

[Gregor Riepl]

That seems to be a dead giveaway:


#2  0x7696e0c6 in wxTranslations::SetLanguage (this=0x0, 
lang=lang@entry=wxLANGUAGE_DEFAULT) at ./src/common/translation.cpp:1384


I'd expect it to crash when *this* is a null pointer.

Have you reported the issue upstream?

Bug#1020820: joblib: CVE-2022-21797

[Salvatore Bonaccorso]

Source: joblib
Version: 1.1.0-2
Severity: grave
Tags: security
Justification: user security hole
Forwarded: https://github.com/joblib/joblib/issues/1128
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for joblib.

CVE-2022-21797[0]:
| The package joblib from 0 and before 1.2.0 are vulnerable to Arbitrary
| Code Execution via the pre_dispatch flag in Parallel() class due to
| the eval() statement.


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-21797
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21797
[1] https://github.com/joblib/joblib/issues/1128
[2] 
https://github.com/joblib/joblib/commit/b90f10efeb670a2cc877fb88ebb3f2019189e059

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#1012250: Fixing CI bugs for a package on the REJECT list

[Jeff]

Hi Paul,

On 26/09/2022 19:46, Paul Gevers wrote:

The bug has a user specified for the usertag and explicitly mentions:
"""
Don't hesitate to reach out if you need help [...]
"""

So, either using debian...@lists.debian.org or the submitter's address 
(mine) seems appropriate.


In which case, I evidently misunderstood. I had assumed that replying to 
the bug mail would do the same.



In this case:
we can trigger the test from the backside, such that you can get a fresh 
log, but I prefer to only do that coordinated and after you give it a 
try to enable more diagnostic logging, because apparently in the 
original logs there wasn't enough information for you.


I also offer to run the test (once or twice) manually and get 
information out of the testbed, if you tell me the exact commands you 
want me to run in the testbed.


Please trigger a new run. I can't add more diagnostics until I know where.

What bothers me about this is that these flaky tests do not occur with 
the buildd hosts:


https://buildd.debian.org/status/logs.php?pkg=gscan2pdf=all

The only failure took 7 minutes, not 27 hours.

So how do the CI hosts diff from the buildd ones?

Thanks for your help.

Regards

Jeff


OpenPGP_signature
Description: OpenPGP digital signature