date:20230425

Bug#1034310: [digikam] [Bug 466170] Digikam 7.9.0 (and 7.8.0) crashes on startup

2023-04-25 Thread Steven Robbins

On Tuesday, April 25, 2023 12:50:39 P.M. CDT Rainer Dorsch wrote:
> Am Dienstag, 25. April 2023, 03:51:44 CEST schrieben Sie:
> > I'd be interested to know if the issue persists on your system after
> > upgrading.
> 
> Yes, it repros always.

OK.

> -- System Information:
> Debian Release: 12.0
>   APT prefers testing-security
>   APT policy: (500, 'testing-security'), (500, 'testing-debug'), (105,
> 'testing')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 6.1.0-7-amd64 (SMP w/6 CPU threads; PREEMPT)
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
> LANGUAGE=de:en_US

I'm still not able to reproduce the issue.  Today I was trying with the same 
locale as you (de_DE.UTF-8).   I have seen issues in the past with certain 
locales -- typically in software that isn't careful enough and gets into 
trouble when a locale switches the period and comma in number formats.  

Even though I wasn't able to reproduce the problem here, it would be 
interesting if you can try with locale set to en_US for example:

I have no idea where else to look.  Given that no-one else has reported this, 
I'm leaning towards downgrading the severity to keep digikam in the upcoming 
release.

-Steve

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

Bug#1034854: [pkg-php-pear] Bug#1034854: symfony: autopkgtest regression: "error:10800075:PKCS7 routines::certificate verify error".

2023-04-25 Thread David Prévot



Hi Paul,

Thanks for the report.

Le 25/04/2023 à 21:43, Paul Gevers a écrit :

Source: symfony

[…]
Your package has an autopkgtest, great. However, it fails since April 
2023.


Meh, between 3 and 19 on Sid and between 11 and 21 on Bookworm.

[…]

Targeted fixes are still welcome.

[…]
7) 
Symfony\Component\Mime\Tests\Crypto\SMimeSignerTest::testSignedMessageExtraCerts
Verification of the message /tmp/phpe95PWJ failed. Internal error 
"error:10800075:PKCS7 routines::certificate verify error".

Failed asserting that false is true.

/tmp/autopkgtest-lxc.oubjjog1/downtmp/build.dE0/src/src/Symfony/Component/Mime/Tests/Crypto/SMimeSignerTest.php:160
/tmp/autopkgtest-lxc.oubjjog1/downtmp/build.dE0/src/src/Symfony/Component/Mime/Tests/Crypto/SMimeSignerTest.php:150


Thanks, hope to find time to look at it (this issue in the Symfony Mime 
Coponent testsuite) really soon.


Regards

taffit


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1034688: [Pkg-privacy-maintainers] Bug#1034688: onionshare: flaky autopkgtest

2023-04-25 Thread Hefee

Hey,

I have no real idea why we see only a problem in the chat_server test. It is a 
problem in the shutdown... I can mark it as superficial so the failing test 
does not block the CI. But is only a workaround. Can you enable the verbose 
flag by hand, so we can see what function triggers this segmentation fault? 

Test-Command: XDG_CONFIG_HOME="$AUTOPKGTEST_TMP" onionshare-cli -v --local-
only --chat --auto-stop-timer 2

Or can you give me the the back trace of the segmentation fault?
On my system, I don't see the segmentation fault, so hard to taggle down.

Properly it is
https://github.com/onionshare/onionshare/issues/1408#issuecomment-908150292
and it is harmless. But without verbose log I cannot be sure. 

> The autopkgtests from onionshare are flaky and have been failing roughly
> half the time over the last couple of weeks.

Does that mean, that it run successfully before?

Regards,

hefee

--

On Freitag, 21. April 2023 20:53:03 CEST Sebastian Ramacher wrote:
> Source: onionshare
> Version: 2.6-1
> Severity: serious
> 

> 
> https://ci.debian.net/data/autopkgtest/testing/amd64/o/onionshare/32901091/l
> og.gz
> 
> Give this address and private key to the recipient:
> http://127.0.0.1:17632
> Private key: E2GOT5LTUTP3OAMRCRXO4GSH6VKJEUOXZQUC336SRKAHTTT5OVSA
> 
> Press Ctrl+C to stop the server
> Stopped because auto-stop timer ran out
> Segmentation fault
> autopkgtest [22:20:10]: test chat_server: ---]
> autopkgtest [22:20:10]: test chat_server:  - - - - - - - - - - results - - -
> - - - - - - - chat_server  FAIL non-zero exit status 139

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

Bug#965565: marked as done (gplcver: Removal of obsolete debhelper compat 5 and 6 in bookworm)

2023-04-25 Thread Debian Bug Tracking System

Your message dated Tue, 25 Apr 2023 21:18:54 +
with message-id 
and subject line Bug#965565: fixed in gplcver 2.12a-2
has caused the Debian Bug report #965565,
regarding gplcver: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
965565: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965565
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gplcver
Version: 2.12a-1.1
Severity: normal
Usertags: compat-5-6-removal

Hi,

The package gplcver uses debhelper with a compat level of 5 or 6,
which is deprecated and scheduled for removal[1].

Please bump the debhelper compat at your earliest convenience
/outside the freeze/!

  * Compat 13 is recommended (supported in stable-backports)

  * Compat 7 is the bare minimum


PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads
with compat bumps during the freeze.

If there is any risk that the fix for this bug might not migrate to
testing before 2021-01-01[3] then please postpone the fix until after
the freeze.


At the time of filing this bug, compat 5 and 6 are expected to be
removed "some time during the development cycle of bookworm".


Thanks,
~Niels


[1] https://lists.debian.org/debian-devel/2020/07/msg00065.html

[2] https://release.debian.org/bullseye/FAQ.html

[3] The choice of 2021-01-01 as a "deadline" is set before the actual
freeze deadline to provide a safe cut off point for most people.

Mind you, it is still your responsibility to ensure that the upload
makes it into testing even if you upload before that date.
--- End Message ---
--- Begin Message ---
Source: gplcver
Source-Version: 2.12a-2
Done: أحمد المحمودي (Ahmed El-Mahmoudy) 

We believe that the bug you reported is fixed in the latest version of
gplcver, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 965...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
أحمد المحمودي (Ahmed El-Mahmoudy)  (supplier 
of updated gplcver 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, 25 Apr 2023 20:47:35 +0200
Source: gplcver
Architecture: source
Version: 2.12a-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Electronics Team 

Changed-By: أحمد المحمودي (Ahmed El-Mahmoudy) 

Closes: 694118 965565
Changes:
 gplcver (2.12a-2) unstable; urgency=medium
 .
   * Adopt gplcver (Closes: #694118)
   * d/control:
 + Add ${misc:Depends} to Depends field
 + Remove Homepage URL, no longer valid
 + Change priority to optional
 + Add Rules-Requires-Root: no
 + Add Vcs-* fields
 + Change section to electronics
   * d/copyright:
 + Update copyright format & years
 + Add myself to Debian packaging copyright holders
 + Added PD license paragraph
   * Simplify rules file.
   * Added debian/manpages & debian/install
   * Switch to debhelper-compat 13 (Closes: #965565)
 + Remove autoconf files added by previous maintainer, autoreconf will
 autogenerate them.
   * Switch to 3.0 (quilt) source format.
 Move changes to patches: autoconf.diff, fix_sparc_ftbfs.diff
   * Add string_format_security.diff to fix string format security
   * Added typos.diff patch to fix some typos
   * d/copyright: add myself to Debian packaging copyright holders
   * Update changelog for 2.12a-1.2~4.gbp39f71b release
Checksums-Sha1:
 090527f08dd439ce92c284e5cf9817e0a9e73575 1779 gplcver_2.12a-2.dsc
 b9522b537e9162117612e78fe1a43813b9064926 12140 gplcver_2.12a-2.debian.tar.xz
 561868d7ffafb0a7266d863a67296669b995e996 5436 gplcver_2.12a-2_source.buildinfo
Checksums-Sha256:
 fae54dd7d319738e55943affd3c6244e97c9cd9201f1c0adb7c54058c955013e 1779 
gplcver_2.12a-2.dsc
 711326edc782fb3a4727f8e02f31650428d1d4e46f4dcd4f96e71ce13de942f5 12140 
gplcver_2.12a-2.debian.tar.xz
 95ef672dc7bf1cb44a15d370cede90cdfd8b9c7245c1c77e26391213921709b4 5436 
gplcver_2.12a-2_source.buildinfo
Files:
 13cc2f04d447b50bf0922e2de5a33762 1779 electronics optional gplcver_2.12a-2.dsc
 f27e6cbba88af73b5ffe13c007a36f77 12140 electronics optional 
gplcver_2.12a-2.debian.tar.xz
 56365775c105ab20e7419785df9afbfd 5436 electronics optional

Bug#1004026: marked as done (covered: gplcver support should be dropped or gplcver adopted by the Electronics Team)

2023-04-25 Thread Debian Bug Tracking System

Your message dated Tue, 25 Apr 2023 22:57:54 +0200
with message-id <3c63b5f4-d9a4-8e25-c6f5-395e6d716...@debian.org>
and subject line Re: covered: gplcver support should be dropped or gplcver 
adopted by the Electronics Team
has caused the Debian Bug report #1004026,
regarding covered: gplcver support should be dropped or gplcver adopted by the 
Electronics Team
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.)


-- 
1004026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004026
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: covered
Version: 0.7.10-3.1
Severity: serious
Control: block 965565 by -1

If gplcver provides any functionality not available in iverilog,
it would be useful if this orphaned package could be adopted by
the Electronics Team.

Otherwise, please drop gplcver support from covered.
--- End Message ---
--- Begin Message ---

On Wed, 19 Jan 2022 16:49:01 +0200 Adrian Bunk  wrote:

If gplcver provides any functionality not available in iverilog,
it would be useful if this orphaned package could be adopted by
the Electronics Team.


Doing so.--- End Message ---

Bug#1034856: dstat: autopkgtest regression on multiple archs: TypeError: '<' not supported between instances of 'dict' and 'int'

2023-04-25 Thread Paul Gevers


Hi,

On Tue, 25 Apr 2023 22:03:43 +0200 Paul Gevers  wrote:
Your package has an autopkgtest, great. However, it fails since April 
2023 on arm64, i386, ppc64el and s390x.


Sorry, I forgot to spot what I should have spotted: those are the 
architectures that I upgraded on ci.debian.net to a bookworm kernel. 
Even the tests in stable started to fail. We run lxc, so the kernel is 
determined by the host.


Also, bug #1032615 has the same stack trace.

Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1034856: dstat: autopkgtest regression on multiple archs: TypeError: '<' not supported between instances of 'dict' and 'int'

2023-04-25 Thread Paul Gevers


Source: dstat
Version: 0.7.4-6.1
Severity: serious
Control: tags -1 bookworm-ignore
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

Your package has an autopkgtest, great. However, it fails since April 
2023 on arm64, i386, ppc64el and s390x. Can you please investigate the 
situation and fix it? I copied some of the output at the bottom of this 
report.


The release team has announced [1] that failing autopkgtest on amd64 and 
arm64 are considered RC in testing. [Release Team member hat on] Because 
we're currently in the hard freeze for bookworm, I have marked this bug 
as bookworm-ignore. Targeted fixes are still welcome.


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


Paul

[1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html

https://ci.debian.net/data/autopkgtest/testing/arm64/d/dstat/33156935/log.gz

* Exception in plugin ['loop0', 'loop1', 'loop2', 'loop3', 'loop4', 
'loop5', 'loop6', 'loop7', 'vda']

'rq_ticks'
main()
  File "/usr/bin/dstat", line 2687, in main
scheduler.run()
  File "/usr/lib/python3.11/sched.py", line 151, in run
action(*argument, **kwargs)
  File "/usr/bin/dstat", line 2804, in perform
line = line + o.show() + o.showend(totlist, vislist)
  
  File "/usr/bin/dstat", line 526, in show
line = line + cprint(self.val[name], ctype, self.width, scale)
  
  File "/usr/bin/dstat", line 2105, in cprint
if ctype != 's' and var < 0:
^^^
TypeError: '<' not supported between instances of 'dict' and 'int'


OpenPGP_signature
Description: OpenPGP digital signature

Processed: dstat: autopkgtest regression on multiple archs: TypeError: '<' not supported between instances of 'dict' and 'int'

2023-04-25 Thread Debian Bug Tracking System

Processing control commands:

> tags -1 bookworm-ignore
Bug #1034856 [src:dstat] dstat: autopkgtest regression on multiple archs: 
TypeError: '<' not supported between instances of 'dict' and 'int'
Added tag(s) bookworm-ignore.

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

Processed: trapperkeeper-webserver-jetty9-clojure: autopkgtest regression: Cannot invoke "Object.toString()" because "s" is null

2023-04-25 Thread Debian Bug Tracking System

Processing control commands:

> tags -1 bookworm-ignore
Bug #1034855 [src:trapperkeeper-webserver-jetty9-clojure] 
trapperkeeper-webserver-jetty9-clojure: autopkgtest regression: Cannot invoke 
"Object.toString()" because "s" is null
Added tag(s) bookworm-ignore.

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

Bug#1034855: trapperkeeper-webserver-jetty9-clojure: autopkgtest regression: Cannot invoke "Object.toString()" because "s" is null

2023-04-25 Thread Paul Gevers


Source: trapperkeeper-webserver-jetty9-clojure
Version: 4.4.1-5
Severity: serious
Control: tags -1 bookworm-ignore
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

Your package has an autopkgtest, great. However, it fails since April 
2023. Can you please investigate the situation and fix it? I copied some 
of the output at the bottom of this report.


The release team has announced [1] that failing autopkgtest on amd64 and 
arm64 are considered RC in testing. [Release Team member hat on] Because 
we're currently in the hard freeze for bookworm, I have marked this bug 
as bookworm-ignore. Targeted fixes are still welcome.


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


Paul

[1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html

https://ci.debian.net/data/autopkgtest/testing/amd64/t/trapperkeeper-webserver-jetty9-clojure/33156934/log.gz

ERROR in (request-logging-test) (Matcher.java:1769)
request logging occurs when :access-log-config is configured
expected: (re-find #"\"GET /hi_world/ HTTP/1.1\" 200 8" (first list))
  actual: java.lang.NullPointerException: Cannot invoke 
"java.lang.CharSequence.length()" because "this.text" is null

 at java.util.regex.Matcher.getTextLength (Matcher.java:1769)
java.util.regex.Matcher.reset (Matcher.java:415)
java.util.regex.Matcher. (Matcher.java:252)
java.util.regex.Pattern.matcher (Pattern.java:1134)
clojure.core$re_matcher.invokeStatic (core.clj:4881)
clojure.core$re_find.invokeStatic (core.clj:4923)
clojure.core$re_find.invoke (core.clj:4923)
clojure.lang.AFn.applyToHelper (AFn.java:156)
clojure.lang.AFn.applyTo (AFn.java:144)
clojure.core$apply.invokeStatic (core.clj:667)
clojure.core$apply.invoke (core.clj:662)

puppetlabs.trapperkeeper.services.webserver.jetty9_service_test$fn__29186$fn__29189$fn__29190.invoke 
(jetty9_service_test.clj:740)


puppetlabs.trapperkeeper.services.webserver.jetty9_service_test$fn__29186$fn__29189.invoke 
(jetty9_service_test.clj:733)

clojure.core$with_redefs_fn.invokeStatic (core.clj:7582)
clojure.core$with_redefs_fn.invoke (core.clj:7566)

puppetlabs.trapperkeeper.services.webserver.jetty9_service_test$fn__29186.invokeStatic 
(jetty9_service_test.clj:722)
puppetlabs.trapperkeeper.services.webserver.jetty9_service_test/fn 
(jetty9_service_test.clj:721)

clojure.test$test_var$fn__9856.invoke (test.clj:717)
clojure.test$test_var.invokeStatic (test.clj:717)
clojure.test$test_var.invoke (test.clj:708)
clojure.test$test_vars$fn__9882$fn__9887.invoke (test.clj:735)
clojure.test$default_fixture.invokeStatic (test.clj:687)
clojure.test$default_fixture.invoke (test.clj:683)
clojure.test$test_vars$fn__9882.invoke (test.clj:735)

puppetlabs.trapperkeeper.services.webserver.jetty9_service_test$eval28533$fn__28534.invoke 
(jetty9_service_test.clj:43)

clojure.test$compose_fixtures$fn__9850$fn__9851.invoke (test.clj:694)

puppetlabs.trapperkeeper.testutils.webserver$assert_clean_shutdown.invokeStatic 
(webserver.clj:75)


puppetlabs.trapperkeeper.testutils.webserver$assert_clean_shutdown.invoke 
(webserver.clj:71)

clojure.test$compose_fixtures$fn__9850$fn__9851.invoke (test.clj:694)
schema.test$validate_schemas$fn25482__25491$fn__25492.invoke 
(test.cljc:12)

schema.test$validate_schemas$fn25482__25491.invoke (test.cljc:12)
clojure.lang.AFn.applyToHelper (AFn.java:152)
clojure.lang.AFn.applyTo (AFn.java:144)
clojure.lang.AFunction$1.doInvoke (AFunction.java:31)
clojure.lang.RestFn.invoke (RestFn.java:397)
schema.test$validate_schemas.invokeStatic (test.cljc:12)
schema.test$validate_schemas.invoke (test.cljc:7)
clojure.test$compose_fixtures$fn__9850$fn__9851.invoke (test.clj:694)

puppetlabs.kitchensink.testutils.fixtures$with_no_jvm_shutdown_hooks$fn__28235.invoke 
(fixtures.clj:10)

clojure.core$with_redefs_fn.invokeStatic (core.clj:7582)
clojure.core$with_redefs_fn.invoke (core.clj:7566)

puppetlabs.kitchensink.testutils.fixtures$with_no_jvm_shutdown_hooks.invokeStatic 
(fixtures.clj:9)


puppetlabs.kitchensink.testutils.fixtures$with_no_jvm_shutdown_hooks.invoke 
(fixtures.clj:4)

clojure.test$compose_fixtures$fn__9850$fn__9851.invoke (test.clj:694)
clojure.test$default_fixture.invokeStatic (test.clj:687)
clojure.test$default_fixture.invoke (test.clj:683)
clojure.test$compose_fixtures$fn__9850.invoke (test.clj:694)
clojure.test$compose_fixtures$fn__9850.invoke (test.clj:694)
clojure.test$compose_fixtures$fn__9850.invoke (test.clj:694)
clojure.test$compose_fixtures$fn__9850.invoke (test.clj:694)
clojure.test$test_vars.invokeStatic (test.clj:731)
clojure.test$test_all_vars.invokeStatic (test.clj:737)
clojure.test$test_ns.invokeStatic (test.clj:758)
clojure.test$test_ns.invoke (test.clj:743)

Processed: symfony: autopkgtest regression: "error:10800075:PKCS7 routines::certificate verify error".

2023-04-25 Thread Debian Bug Tracking System

Processing control commands:

> tags -1 bookworm-ignore
Bug #1034854 [src:symfony] symfony: autopkgtest regression: 
"error:10800075:PKCS7 routines::certificate verify error".
Added tag(s) bookworm-ignore.

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

Bug#1034854: symfony: autopkgtest regression: "error:10800075:PKCS7 routines::certificate verify error".

2023-04-25 Thread Paul Gevers

Source: symfony
Version: 5.4.22+dfsg-2
Severity: serious
Control: tags -1 bookworm-ignore
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

Your package has an autopkgtest, great. However, it fails since April
2023. Can you please investigate the situation and fix it? I copied some
of the output at the bottom of this report.

The release team has announced [1] that failing autopkgtest on amd64 and
arm64 are considered RC in testing. [Release Team member hat on] Because
we're currently in the hard freeze for bookworm, I have marked this bug
as bookworm-ignore. Targeted fixes are still welcome.

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

Paul

[1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html

https://ci.debian.net/data/autopkgtest/testing/amd64/s/symfony/33122795/log.gz

There were 7 failures:

1) Symfony\Component\Mime\Tests\Crypto\SMimeSignerTest::testSignedMessage
Verification of the message /tmp/phpxnGzwx failed. Internal error
"error:10800075:PKCS7 routines::certificate verify error".