Bug#1034450: marked as done (jekyll: autopkgtest fails on arm64 (in UTC+8 timezone): a document with a date with timezone should have the expected date)

2023-04-16 Thread Debian Bug Tracking System
Your message dated Mon, 17 Apr 2023 02:34:01 +
with message-id 
and subject line Bug#1034450: fixed in jekyll 4.3.1+dfsg-2
has caused the Debian Bug report #1034450,
regarding jekyll: autopkgtest fails on arm64 (in UTC+8 timezone): a document 
with a date with timezone should have the expected date
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.)


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

Source: jekyll
Version: 4.3.1+dfsg-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 on arm64 since 
mid 2022. I noticed that the two tests that failed are about timezones 
and our arm64 hosts are located in a UTC+8 timezone. Until 2023-04-13 
the hosts were also configured in their local timezone, but changing 
that to UTC didn't solve the problem. 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/j/jekyll/32926900/log.gz


Failure:
Minitest::Result#test_: a document with a date with timezone should have 
the expected date. 
[/tmp/autopkgtest-lxc.a_d0zzn9/downtmp/build.XLd/src/test/test_document.rb:627]

Minitest::Assertion: Expected: "2015/09/30"
  Actual: "2015/10/01"

Failure:
Minitest::Result#test_: a document with a date with timezone should 
return the expected date via Liquid. 
[/tmp/autopkgtest-lxc.a_d0zzn9/downtmp/build.XLd/src/test/test_document.rb:631]

Minitest::Assertion: Expected: "2015/09/30"
  Actual: "2015/10/01"


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: jekyll
Source-Version: 4.3.1+dfsg-2
Done: Antonio Terceiro 

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

Debian distribution maintenance software
pp.
Antonio Terceiro  (supplier of updated jekyll 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: Sun, 16 Apr 2023 18:35:56 -0300
Source: jekyll
Architecture: source
Version: 4.3.1+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Antonio Terceiro 
Closes: 1034450
Changes:
 jekyll (4.3.1+dfsg-2) unstable; urgency=medium
 .
   * Team upload
   * debian/ruby-tests.rake: always run tests under TZ=UTC (Closes: #1034450)
Checksums-Sha1:
 ea1a2b67207952383b33616928a6840543214127 2711 jekyll_4.3.1+dfsg-2.dsc
 aa281e27c7aa3db54928cfa9161029489d02d7d6 39704 
jekyll_4.3.1+dfsg-2.debian.tar.xz
 279bdf16e4a48632f0873e6ec95150603ce5c574 26464 
jekyll_4.3.1+dfsg-2_source.buildinfo
Checksums-Sha256:
 efdd0b1308063a6f5cec739b52c0cd5ceeac1d4712fff90565f7f87c14c9f0e0 2711 
jekyll_4.3.1+dfsg-2.dsc
 596ac5d246386d8460e2a5e053ea6cacff3171f897fa8311a0536e8809810aac 39704 
jekyll_4.3.1+dfsg-2.debian.tar.xz
 cee421427b3c9d8e244f0af6d8e1d303b1449c4367002b9a59b14b4aebf07607 26464 
jekyll_4.3.1+dfsg-2_source.buildinfo
Files:
 8d7536a88d8af5b773a392e74a3937e9 2711 web optional jekyll_4.3.1+dfsg-2.dsc
 965977dd47c0bb9959f9ec4068e75c59 39704 web optional 
jekyll_4.3.1+dfsg-2.debian.tar.xz
 06f759456de39fbf844d8fedaa2b3ebd 26464 web optional 
jekyll_4.3.1+dfsg-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAmQ8rTcACgkQ/A2xu81G
C97JsBAAipfxoGUb1kVNcEOgHobSXsTOrf8B3VZs6GZgNLp0xPEaHM/zuBWQGSV5
BLyJijq26+7OhjO+sR+AKOy8+rl3BxslHCr24d0YxtFsply6yNxmsd/Ht2FJzlmJ

Bug#1034190: marked as done (More security bugs in game loading)

2023-04-16 Thread Debian Bug Tracking System
Your message dated Mon, 17 Apr 2023 00:03:58 +
with message-id 
and subject line Bug#1034190: fixed in sgt-puzzles 20230122.806ae71-2
has caused the Debian Bug report #1034190,
regarding More security bugs in game loading
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.)


-- 
1034190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034190
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sgt-puzzles
Version: 20230122.806ae71-1
Severity: serious
Tags: security upstream fixed-upstream
X-Debbugs-Cc: Debian Security Team 

Ben Harris found multiple issues in sgt-puzzles where a malformed game
description or save file can lead to a buffer overflow, buffer
overread, use of an uniniitialised pointer, integer overflow, null
pointer dereference, division by zero, assertion failure, or memory
leak.  These were fixed upstream over the past few months.

The Debian package doesn't register any media type handler for save
files, so I think this can only be exploited by social-engineering a
user into loading such a file or description.

For most of these bugs, the impact is limited to a crash of the
application.  However, the various memory safety errors may be more
serious.  On some architectures, division by zero does not cause an
exception and this might also be exploitable.

Ben.

-- System Information:
Debian Release: 12.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'stable-security'), (500, 'oldstable-updates'), (500, 'unstable'), (500, 
'stable'), (500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-7-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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 sgt-puzzles depends on:
ii  libc62.36-8
ii  libcairo21.16.0-7
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1+b1
ii  libglib2.0-0 2.74.6-1
ii  libgtk-3-0   3.24.37-2
ii  libpango-1.0-0   1.50.12+ds-1
ii  libpangocairo-1.0-0  1.50.12+ds-1

Versions of packages sgt-puzzles recommends:
ii  chromium [www-browser]  111.0.5563.64-1
ii  firefox [www-browser]   111.0-3
ii  lynx [www-browser]  2.9.0dev.12-1
ii  xdg-utils   1.1.3-4.1

sgt-puzzles suggests no packages.

-- debconf-show failed
--- End Message ---
--- Begin Message ---
Source: sgt-puzzles
Source-Version: 20230122.806ae71-2
Done: Ben Hutchings 

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

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated sgt-puzzles package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 16 Apr 2023 21:19:11 +0200
Source: sgt-puzzles
Architecture: source
Version: 20230122.806ae71-2
Distribution: unstable
Urgency: medium
Maintainer: Ben Hutchings 
Changed-By: Ben Hutchings 
Closes: 905852 1034190
Changes:
 sgt-puzzles (20230122.806ae71-2) unstable; urgency=medium
 .
   * Fix various security issues in game loading (Closes: #1034190):
 - Black Box: reject negative ball counts in game_params.
 - Add validate_params bounds checks in a few more games.
 - Don't allow Bridges games with < 2 islands
 - Forbid moves that fill with the current colour in Flood
 - Cleanly reject ill-formed solve moves in Flood
 - Don't segfault on premature solve moves in Mines
 - Limit number of mines in Mines game description
 - Validate the number of pegs and holes in a Pegs game ID
 - Mines: forbid moves that flag or unflag an exposed square
 - Mines: Don't check if the player has won if they've already lost
 - Avoid invalid moves when solving Tracks
 - Fix move validation in Netslide
 - Tighten validation of Tents game descriptions
 - Dominosa: require the two halves of a domino to be adjacent
 - Forbid lines off the grid in Pearl
 - Tolerate 

Processed: Re: Bug#1002642: missing dependency on python3-requests

2023-04-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 1002642 important
Bug #1002642 [cups-tea4cups] missing dependency on python3-requests
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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



Bug#813492: marked as done (kde-workspace-bin: kdeinit4 increase memory-consumption by every extern ssh-login and never release it)

2023-04-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Apr 2023 23:19:11 +0200
with message-id 
and subject line kde-workspace has been superseded by Plasma 5
has caused the Debian Bug report #813492,
regarding kde-workspace-bin: kdeinit4 increase memory-consumption by every 
extern ssh-login and never release it
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.)


-- 
813492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813492
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kde-workspace-bin
Version: 4:4.11.13-2
Severity: critical
Justification: causes serious data loss



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

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages kde-workspace-bin depends on:
ii  iso-codes 3.57-1
ii  kde-runtime   4:4.14.2-2
ii  kde-style-oxygen  4:4.11.13-2
ii  kde-workspace-data4:4.11.13-2
ii  kde-workspace-kgreet-plugins  4:4.11.13-2
ii  kscreen   1.0.2.1-1
ii  libc6 2.19-18+deb8u2
ii  libcln6   1.3.4-1
ii  libdbusmenu-qt2   0.9.2-1
ii  libfontconfig12.11.0-6.3
ii  libfreetype6  2.5.2-3+deb8u1
ii  libgcc1   1:4.9.2-10
ii  libgl1-mesa-glx [libgl1]  10.3.2-1+deb8u1
ii  libice6   2:1.0.9-1+b1
ii  libjpeg62-turbo   1:1.3.1-12
ii  libkactivities6   4:4.13.3-1
ii  libkcmutils4  4:4.14.2-5
ii  libkdeclarative5  4:4.14.2-5
ii  libkdecore5   4:4.14.2-5
ii  libkdesu5 4:4.14.2-5
ii  libkdeui5 4:4.14.2-5
ii  libkfile4 4:4.14.2-5
ii  libkidletime4 4:4.14.2-5
ii  libkio5   4:4.14.2-5
ii  libknewstuff3-4   4:4.14.2-5
ii  libknotifyconfig4 4:4.14.2-5
ii  libkparts44:4.14.2-5
ii  libkpty4  4:4.14.2-5
ii  libkscreensaver5  4:4.11.13-2
ii  libkworkspace4abi24:4.11.13-2
ii  libnepomukcore4   4:4.14.0-1+b2
ii  libpam0g  1.1.8-3.1+deb8u1
ii  libphonon44:4.8.0-4
ii  libplasma34:4.14.2-5
ii  libplasmagenericshell44:4.11.13-2
ii  libpng12-01.2.50-2+deb8u2
ii  libprocesscore4abi1   4:4.11.13-2
ii  libprocessui4a4:4.11.13-2
ii  libqalculate5 0.9.7-9
ii  libqimageblitz4   1:0.0.6-4
ii  libqjson0 0.8.1-3
ii  libqt4-dbus   4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqt4-declarative4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqt4-sql4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqt4-xml4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqtcore44:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libsm62:1.2.2-1+b1
ii  libsolid4 4:4.14.2-5
ii  libsoprano4   2.9.4+dfsg-1.1
ii  libstdc++64.9.2-10
ii  libstreamanalyzer00.7.8-1.2+b2
ii  libudev1  215-17+deb8u3
ii  libusb-0.1-4  2:0.1.12-25
ii  libx11-6  2:1.6.2-3
ii  libxcursor1   1:1.1.14-1+b1
ii  libxext6  2:1.3.3-1
ii  libxfixes31:5.0.1-2+b2
ii  libxft2   2.3.2-1
ii  libxi62:1.7.4-1+b2
ii  libxinerama1  2:1.1.3-1+b1
ii  libxkbfile1   1:1.0.8-1
ii  libxrandr22:1.4.2-1+b1
ii  libxrender1   1:0.9.8-1+b1
ii  libxtst6  2:1.2.2-1+b1
ii  phonon4:4.8.0-4
ii  plasma-desktop4:4.11.13-2
ii  qdbus 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  x11-utils 7.7+2
ii  x11-xserver-utils 7.7+3+b1

Versions of packages kde-workspace-bin recommends:
ii  plasma-scriptengines  4:4.11.13-2
ii  policykit-1-gnome 0.105-2
ii  polkit-kde-1  0.99.1-1
ii  upower0.99.1-3.2

Versions of packages kde-workspace-bin suggests:
ii  

Bug#769155: marked as done (kde-workspace-bin: laptop does not go to sleep when critical battery level is reached)

2023-04-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Apr 2023 23:19:11 +0200
with message-id 
and subject line kde-workspace has been superseded by Plasma 5
has caused the Debian Bug report #769155,
regarding kde-workspace-bin: laptop does not go to sleep when critical battery 
level is reached
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.)


-- 
769155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769155
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kde-workspace-bin
Version: 4:4.11.13-1
Severity: normal

Dear Maintainer,

I'm following jessie and this is a feature which was working.
System settings -> Power Management -> Advanced Settings -> Battery levels
-> Battery is at low level at 30% , Battery is at critical level at 17%,
-> When battery is at critical level: Sleep

Up until (not quite sure) one/two months the laptop would fall asleep when
passing the critical level, but now it does absolutely nothing when passing
the critical level.

I attach the output of 
upower --monitor-detail
beginning with battery level 19%, up to 9%. The laptop did not fall asleep.

Thanks, 
Giorgos

-- System Information:
Debian Release: jessie/sid
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages kde-workspace-bin depends on:
ii  iso-codes 3.57-1
ii  kde-runtime   4:4.14.2-1
ii  kde-style-oxygen  4:4.11.13-1
ii  kde-workspace-data4:4.11.13-1
ii  kde-workspace-kgreet-plugins  4:4.11.13-1
ii  kscreen   1.0.2.1-1
ii  libc6 2.19-12
ii  libcln6   1.3.4-1
ii  libdbusmenu-qt2   0.9.2-1
ii  libfontconfig12.11.0-6.1
ii  libfreetype6  2.5.2-2
ii  libgcc1   1:4.9.1-19
ii  libgl1-mesa-glx [libgl1]  10.3.2-1
ii  libice6   2:1.0.9-1
ii  libjpeg62-turbo   1:1.3.1-10
ii  libkactivities6   4:4.13.3-1
ii  libkcmutils4  4:4.14.2-3
ii  libkdeclarative5  4:4.14.2-3
ii  libkdecore5   4:4.14.2-3
ii  libkdesu5 4:4.14.2-3
ii  libkdeui5 4:4.14.2-3
ii  libkfile4 4:4.14.2-3
ii  libkidletime4 4:4.14.2-3
ii  libkio5   4:4.14.2-3
ii  libknewstuff3-4   4:4.14.2-3
ii  libknotifyconfig4 4:4.14.2-3
ii  libkparts44:4.14.2-3
ii  libkpty4  4:4.14.2-3
ii  libkscreensaver5  4:4.11.13-1
ii  libkworkspace4abi24:4.11.13-1
ii  libnepomukcore4   4:4.14.0-1+b2
ii  libpam0g  1.1.8-3.1
ii  libphonon44:4.8.0-3
ii  libplasma34:4.14.2-3
ii  libplasmagenericshell44:4.11.13-1
ii  libpng12-01.2.50-2+b1
ii  libprocesscore4abi1   4:4.11.13-1
ii  libprocessui4a4:4.11.13-1
ii  libqalculate5 0.9.7-9
ii  libqimageblitz4   1:0.0.6-4
ii  libqjson0 0.8.1-3
ii  libqt4-dbus   4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqt4-declarative4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqt4-sql4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqt4-xml4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqtcore44:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libsm62:1.2.2-1
ii  libsolid4 4:4.14.2-3
ii  libsoprano4   2.9.4+dfsg-1.1
ii  libstdc++64.9.1-19
ii  libstreamanalyzer00.7.8-1.2+b2
ii  libudev1  215-5+b1
ii  libusb-0.1-4  2:0.1.12-25
ii  libx11-6  2:1.6.2-3
ii  libxcursor1   1:1.1.14-1+b1
ii  libxext6  2:1.3.3-1
ii  libxfixes31:5.0.1-2+b1
ii  libxft2   2.3.2-1
ii  libxi62:1.7.4-1+b1
ii  libxinerama1  2:1.1.3-1+b1
ii  libxkbfile1   1:1.0.8-1
ii  libxrandr22:1.4.2-1+b1
ii  libxrender1   1:0.9.8-1+b1
ii  libxtst6  2:1.2.2-1+b1
ii  phonon   

Bug#1034190: marked as done (More security bugs in game loading)

2023-04-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Apr 2023 18:11:36 +
with message-id 
and subject line Bug#1034190: fixed in sgt-puzzles 20230410.71cf891-1
has caused the Debian Bug report #1034190,
regarding More security bugs in game loading
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.)


-- 
1034190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034190
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sgt-puzzles
Version: 20230122.806ae71-1
Severity: serious
Tags: security upstream fixed-upstream
X-Debbugs-Cc: Debian Security Team 

Ben Harris found multiple issues in sgt-puzzles where a malformed game
description or save file can lead to a buffer overflow, buffer
overread, use of an uniniitialised pointer, integer overflow, null
pointer dereference, division by zero, assertion failure, or memory
leak.  These were fixed upstream over the past few months.

The Debian package doesn't register any media type handler for save
files, so I think this can only be exploited by social-engineering a
user into loading such a file or description.

For most of these bugs, the impact is limited to a crash of the
application.  However, the various memory safety errors may be more
serious.  On some architectures, division by zero does not cause an
exception and this might also be exploitable.

Ben.

-- System Information:
Debian Release: 12.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'stable-security'), (500, 'oldstable-updates'), (500, 'unstable'), (500, 
'stable'), (500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-7-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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 sgt-puzzles depends on:
ii  libc62.36-8
ii  libcairo21.16.0-7
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1+b1
ii  libglib2.0-0 2.74.6-1
ii  libgtk-3-0   3.24.37-2
ii  libpango-1.0-0   1.50.12+ds-1
ii  libpangocairo-1.0-0  1.50.12+ds-1

Versions of packages sgt-puzzles recommends:
ii  chromium [www-browser]  111.0.5563.64-1
ii  firefox [www-browser]   111.0-3
ii  lynx [www-browser]  2.9.0dev.12-1
ii  xdg-utils   1.1.3-4.1

sgt-puzzles suggests no packages.

-- debconf-show failed
--- End Message ---
--- Begin Message ---
Source: sgt-puzzles
Source-Version: 20230410.71cf891-1
Done: Ben Hutchings 

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

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated sgt-puzzles 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, 11 Apr 2023 01:30:57 +0200
Source: sgt-puzzles
Architecture: source
Version: 20230410.71cf891-1
Distribution: experimental
Urgency: medium
Maintainer: Ben Hutchings 
Changed-By: Ben Hutchings 
Closes: 642207 905852 1034190
Changes:
 sgt-puzzles (20230410.71cf891-1) experimental; urgency=medium
 .
   * New upstream version:
 - Note in the documentation that Pattern clues are in order
   (Closes: #642207)
 - Solo: cope with pencil marks when tilesize == 1 (Closes: #905852)
 - Multiple fixes for security issues in game loading (Closes: #1034190)
   * d/rules: Fix various bugs in update-upstream rule
Checksums-Sha1:
 c42f466b48efaf293b444dd92e61b738b40b4b6a 2044 
sgt-puzzles_20230410.71cf891-1.dsc
 7f76b870013065afcc2ed8de7ea08a29d8c46f9b 922180 
sgt-puzzles_20230410.71cf891.orig.tar.xz
 2c0f96062deb99f8c47696a12404045e41cf51c9 99860 
sgt-puzzles_20230410.71cf891-1.debian.tar.xz
 bb50ce8544f4cfc5cbb89610ee185e0f6ff7ec11 15341 
sgt-puzzles_20230410.71cf891-1_amd64.buildinfo
Checksums-Sha256:
 0723aa3fcd750fdf5c2717c04b4bce4daa3f458e5e18e47effb16a1527453e1a 2044 
sgt-puzzles_20230410.71cf891-1.dsc
 09c8aa5af21a79e57feb4070501384f8e1195bb3675f69c1906565738dc5cd14 922180 

Bug#982794: marked as done (firefox-esr/armhf: fails on non-NEON systems)

2023-04-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Apr 2023 17:17:11 +
with message-id 
and subject line Bug#982794: fixed in firefox-esr 102.10.0esr-1~deb11u1
has caused the Debian Bug report #982794,
regarding firefox-esr/armhf: fails on non-NEON systems
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.)


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

Dear Maintainer,

Firefox is killed with SIGILL shortly after startup:
$ firefox-esr -safe-mode
Illegal instruction
$ 

A gdb session on a dumped core to investigate:
[...]
Core was generated by `firefox-esr'.
Program terminated with signal SIGILL, Illegal instruction.
#0  0xaf6f0ab0 in ?? () from /usr/lib/firefox-esr/libxul.so
(gdb) backtrace
#0  0xaf6f0ab0 in ?? () from /usr/lib/firefox-esr/libxul.so
#1  0xb6f32f40 in call_init (l=, argc=argc@entry=1, 
argv=argv@entry=0xbeb44584, env=env@entry=0xb6a0a240) at dl-init.c:72
#2  0xb6f32fe2 in call_init (env=, argv=, 
argc=, l=) at dl-init.c:30
#3  _dl_init (main_map=0xb6a30c00, argc=1, argv=0xbeb44584, env=0xb6a0a240) at 
dl-init.c:119
#4  0xb6cec52e in __GI__dl_catch_exception (exception=exception@entry=0x0, 
operate=0xb6f352c1 , args=0xbeb41ed8, args@entry=0xbeb41f10)
at dl-error-skeleton.c:182
#5  0xb6f35d04 in dl_open_worker (a=) at dl-open.c:758
#6  0xb6cec4f4 in __GI__dl_catch_exception 
(exception=exception@entry=0xbeb420d8, operate=0xb6f35869 , 
args=args@entry=0xbeb420e4)
at dl-error-skeleton.c:208
#7  0xb6f355cc in _dl_open (file=0xbeb4237c "/usr/lib/firefox-esr/libxul.so", 
mode=-2147483391, caller_dlopen=0xb6f5df85 <_start+2424>, nsid=-2, argc=1, 
argv=0xbeb44584, env=0xb6a0a240) at dl-open.c:837
#8  0xb6eeed18 in dlopen_doit (a=0xbeb42344) at dlopen.c:66
#9  0xb6cec4f4 in __GI__dl_catch_exception 
(exception=exception@entry=0xbeb42300, operate=0xb6eeecc1 , 
args=args@entry=0xbeb42344)
at dl-error-skeleton.c:208
#10 0xb6cec588 in __GI__dl_catch_error (objname=objname@entry=0xb6a0d2ec, 
errstring=errstring@entry=0xb6a0d2f0, mallocedp=mallocedp@entry=0xb6a0d2e8, 
operate=, args=args@entry=0xbeb42344) at 
dl-error-skeleton.c:227
#11 0xb6eef3de in _dlerror_run (operate=, 
args=args@entry=0xbeb42344) at dlerror.c:170
#12 0xb6eeed9e in __dlopen (file=0xbeb4237c "/usr/lib/firefox-esr/libxul.so", 
mode=) at dlopen.c:87
#13 0xb6f5df84 in _start ()
(gdb) layout asm
0xaf6f0ab0  vmov.i32q8, #0  ; 0x

This is on a Marvell Dove system, with VFPv3-D16. From /proc/cpuinfo:
Features: swp half thumb fastmult vfp edsp iwmmxt thumbee vfpv3 
vfpv3d16 tls 

The referenced (NEON?) register Q8 is not available here, nor even the 
VFPv3-D32 registers D16-D17 that it maps to.

-- Package-specific info:


-- Addons package information

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: armhf (armv7l)

Kernel: Linux 3.5.7-14-ARCH (PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages firefox-esr depends on:
ii  debianutils  4.11.2
ii  fontconfig   2.13.1-4.2
ii  libatk1.0-0  2.36.0-2
ii  libc62.31-9
ii  libcairo-gobject21.16.0-5
ii  libcairo21.16.0-5
ii  libdbus-1-3  1.12.20-1
ii  libdbus-glib-1-2 0.110-6
ii  libevent-2.1-7   2.1.12-stable-1
ii  libffi7  3.3-5
ii  libfontconfig1   2.13.1-4.2
ii  libfreetype6 2.10.4+dfsg-1
ii  libgcc-s110.2.1-6
ii  libgdk-pixbuf-2.0-0  2.42.2+dfsg-1
ii  libglib2.0-0 2.66.6-2
ii  libgtk-3-0   3.24.24-1
ii  libnspr4 2:4.29-1
ii  libnss3  2:3.60-1
ii  libpango-1.0-0   1.46.2-3
ii  libstdc++6   10.2.1-6
ii  libvpx6  1.9.0-1
ii  libx11-6 2:1.7.0-2
ii  libx11-xcb1  2:1.7.0-2
ii  libxcb-shm0  1.14-3
ii  libxcb1  1.14-3
ii  libxcomposite1   1:0.4.5-1
ii  libxdamage1  1:1.1.5-2
ii  libxext6 2:1.3.3-1.1
ii  libxfixes3   1:5.0.3-2
ii  libxrender1  1:0.9.10-1
ii  procps   2:3.3.16-5
ii  zlib1g   1:1.2.11.dfsg-2

Versions of packages firefox-esr recommends:
ii  libavcodec58  7:4.3.1-8

Versions of packages firefox-esr suggests:
pn  fonts-lmodern  
pn  fonts-stix | otf-stix  
pn  libcanberra0   
ii  libgssapi-krb5-2   1.18.3-4
pn  libgtk2.0-0

Bug#1032510: marked as done (packagekit: pkcon what-provides application/x-keepass2 makes PK crash)

2023-04-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Apr 2023 17:19:45 +
with message-id 
and subject line Bug#1032510: fixed in packagekit 1.2.6-4
has caused the Debian Bug report #1032510,
regarding packagekit: pkcon what-provides application/x-keepass2 makes PK crash
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.)


-- 
1032510: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032510
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: packagekit
Version: 1.2.6-3
Severity: serious

Hello,

pkcon what-provides application/x-keepass2 makes PK crash:

$ pkcon what-provides application/x-keepass2
Getting provides[=]
Loading cache   [=]
Querying[=] e 
daemon crashed mid-transaction!
Finished[ ] (0%)

   Stack trace of thread 10447:
#0  0x7faf3ef75ccc __pthread_kill_implementation (libc.so.6 
+ 0x8accc)
#1  0x7faf3ef26ef2 __GI_raise (libc.so.6 + 0x3bef2)
#2  0x7faf3ef11472 __GI_abort (libc.so.6 + 0x26472)
#3  0x7faf3c89d919 
_ZN9__gnu_cxx27__verbose_terminate_handlerEv (libstdc++.so.6 + 0x9d919)
#4  0x7faf3c8a8e1a _ZN10__cxxabiv111__terminateEPFvvE 
(libstdc++.so.6 + 0xa8e1a)
#5  0x7faf3c8a8e85 _ZSt9terminatev (libstdc++.so.6 + 
0xa8e85)
#6  0x7faf3c8a90d8 __cxa_throw (libstdc++.so.6 + 0xa90d8)
#7  0x7faf3c8a00e4 _ZSt19__throw_logic_errorPKc 
(libstdc++.so.6 + 0xa00e4)
#8  0x7faf3e96cb3a 
_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEC4IS3_EEPKcRKS3_ 
(libpk_backend_apt.so + 0x2cb3a)
#9  0x7faf3e95d122 backend_what_provides_thread 
(libpk_backend_apt.so + 0x1d122)
#10 0x5644cb0c7aca pk_backend_job_thread_setup (packagekitd 
+ 0x23aca)
#11 0x7faf3f5dbcfd g_thread_proxy (libglib-2.0.so.0 + 
0x7ecfd)
#12 0x7faf3ef73fd4 start_thread (libc.so.6 + 0x88fd4)
#13 0x7faf3eff466c __clone3 (libc.so.6 + 0x10966c)


This breaks GNOME ability to suggest which application to install when
opening files.

Feel free to downgrade the severity if you want.

Kind regards,
Laurent Bigonville


-- System Information:
Debian Release: 12.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 
'experimental-debug')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-6-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE:fr
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages packagekit depends on:
ii  init-system-helpers 1.65.2
ii  libappstream4   0.16.1-1
ii  libapt-pkg6.0   2.6.0
ii  libc6   2.36-8
ii  libgcc-s1   12.2.0-14
ii  libglib2.0-02.74.6-1
ii  libglib2.0-bin  2.74.6-1
ii  libgstreamer1.0-0   1.22.0-2
ii  libpackagekit-glib2-18  1.2.6-3
ii  libpolkit-gobject-1-0   122-3
ii  libsqlite3-03.40.1-1
ii  libstdc++6  12.2.0-14
ii  libsystemd0 252.6-1
ii  polkitd 122-3

Versions of packages packagekit recommends:
ii  packagekit-tools  1.2.6-3
ii  systemd   252.6-1

Versions of packages packagekit suggests:
ii  appstream  0.16.1-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: packagekit
Source-Version: 1.2.6-4
Done: Matthias Klumpp 

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

Debian distribution maintenance software
pp.
Matthias Klumpp  (supplier of updated packagekit 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: Sun, 16 Apr 2023 18:58:34 +0200
Source: packagekit
Architecture: source
Version: 1.2.6-4

Bug#1034212: marked as done (amazon-ec2-net-utils: dh_installsystemd doesn't handle files in /usr/lib/systemd/system)

2023-04-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Apr 2023 16:33:55 +
with message-id 
and subject line Bug#1034212: fixed in amazon-ec2-net-utils 2.3.0-3
has caused the Debian Bug report #1034212,
regarding amazon-ec2-net-utils: dh_installsystemd doesn't handle files in 
/usr/lib/systemd/system
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.)


-- 
1034212: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034212
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: amazon-ec2-net-utils
Version: 2.3.0-2   
Severity: serious
Tags: sid bookworm
User: debhel...@packages.debian.org
Usertags: systemd-files-in-usr-bookworm

Dear Maintainer,

It seems that your package amazon-ec2-net-utils is shipping files (.service, 
.socket or
.timer) in /usr/lib/systemd/system.

This is not supported by the version of dh_installsystemd/debhelper currently
in unstable and bookworm (See: #1031695). That means that currently your
service might not be enabled at boot and/or started as expected.

With the freeze currently in effect, debhelper will not be fixed for bookworm.

As a result, could you please move these files to /lib/systemd/system instead
so they are properly detected by debhelper?
As soon as debhelper is supporting (not until bookworm+1 aka Trixie) you will
be able to move them back to the newer location.

Note that bookworm is currently in hard freeze, please limit the changes you
are uploading to the ones fixing RC bugs.  Also note that you might have to
request a freeze exception to the release team.
See: https://release.debian.org/testing/freeze_policy.html

Feel free to contact me if you have any questions.

Kind regards,
Laurent Bigonville

The list of packages has been generated with the following command:
apt-file search -x '^/usr/lib/systemd/system/.*\.(service|timer|socket)$'|cut 
-d: -f1|sort -u
--- End Message ---
--- Begin Message ---
Source: amazon-ec2-net-utils
Source-Version: 2.3.0-3
Done: Noah Meyerhans 

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

Debian distribution maintenance software
pp.
Noah Meyerhans  (supplier of updated amazon-ec2-net-utils 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 13 Apr 2023 10:22:32 -0700
Source: amazon-ec2-net-utils
Architecture: source
Version: 2.3.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Cloud Team 
Changed-By: Noah Meyerhans 
Closes: 1034212
Changes:
 amazon-ec2-net-utils (2.3.0-3) unstable; urgency=medium
 .
   * Install systemd services to /lib/systemd/system. (Closes: 1034212)
Checksums-Sha1:
 0926c14a35e34fb66d3a6fa3041eb14a28c8b972 2096 amazon-ec2-net-utils_2.3.0-3.dsc
 7498232e5419e549b3ebc2daee3b39836a04c5a6 3568 
amazon-ec2-net-utils_2.3.0-3.debian.tar.xz
 4fb0d5a1d67f2d5d06a12dfabaffd54d22313753 6669 
amazon-ec2-net-utils_2.3.0-3_source.buildinfo
Checksums-Sha256:
 48efd5a2d1d272e47bd146ca9bf4ac65647e242ca5963f0a546c427a46bf9690 2096 
amazon-ec2-net-utils_2.3.0-3.dsc
 999a82466a8cc36bf2b5a12b9001a92e4bd715400607f7d40e8ce75cceae2353 3568 
amazon-ec2-net-utils_2.3.0-3.debian.tar.xz
 167fd59d696487f7ef551c064fae5c4c872c881d0ce159909cd69c8596ceb4b3 6669 
amazon-ec2-net-utils_2.3.0-3_source.buildinfo
Files:
 dd92266044d53da0b7634f863c048f7a 2096 net optional 
amazon-ec2-net-utils_2.3.0-3.dsc
 cd34e6608569e9a333692be214f37b19 3568 net optional 
amazon-ec2-net-utils_2.3.0-3.debian.tar.xz
 fcac63a9d21df5c5e5a9aca95fcc4c31 6669 net optional 
amazon-ec2-net-utils_2.3.0-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE5G+E0xEKhJuZ7RJ34+c1IpshdTUFAmQ8Hm4RHG5vYWhtQGRl
Ymlhbi5vcmcACgkQ4+c1IpshdTXXlA/+KWLWYUxMMjcKlzCFcshBPKNJVH0NekQ2
i6I95LF3P7Y7Av8OsL/FrqeL0YZxhz3EdnNY64su9hqexQAd5yiljMoGDLPQxbmG
On9wiw7cTTQg4ZYDkqiQRT08AbyGCXNcXxp76uyCyx74Bjgpcj8VadysHoBb4eem
GnawL0s8rchynhrWtHbIKKP/MjBovgs8e/vyEhuJLkUK4vGaQfDZH1fUCIJB+pfx
Iycmt2jv5TNdq0+5mSYF9w6E55obNg4/IZtHm9iwO2gH06iRvtN6SzLpgYbT4p3+
hnPKbIzex5Ck7iUhzXJd6S9Vt3hkQla8B9/dZzK8BhiCUnuPf9DpJTQB/t/UEOw/
4hZG58FP5iBtbGY6iC7GKjIEjLCXrKmF7frWq+gnRaH2ijow92uCIX1f2//qvKdp

Bug#1034221: caddy: dh_installsystemd doesn't handle files in /usr/lib/systemd/system

2023-04-16 Thread Nilesh Patra
Hi Peymaneh,

On Tue, 11 Apr 2023 15:54:02 +0200 Andreas Henriksson  wrote:
> On Tue, Apr 11, 2023 at 09:37:27AM +0200, bi...@debian.org wrote:
> > Package: caddy
> > Version: 2.6.2-4
> > Severity: serious
> > Tags: sid bookworm
> > It seems that your package caddy is shipping files (.service, .socket or
> > .timer) in /usr/lib/systemd/system.
> [...]
> 
> The culprit seems to be wrong path at:
> https://sources.debian.org/src/caddy/2.6.2-4/debian/caddy.install/#L2-L3
> 
> Please note that if you change it to /lib/systemd/system now, you'll
> likely need to reverse that change again in the future.
> 
> Preferably the correct path is derived from the value given by
> pkg-config --variable=systemdsystemunitdir systemd

Can you take care of this?

-- 
Best,
Nilesh


signature.asc
Description: PGP signature


Bug#1034219: marked as done (debomatic: dh_installsystemd doesn't handle files in /usr/lib/systemd/system)

2023-04-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Apr 2023 14:34:01 +
with message-id 
and subject line Bug#1034219: fixed in debomatic 0.26-2
has caused the Debian Bug report #1034219,
regarding debomatic: dh_installsystemd doesn't handle files in 
/usr/lib/systemd/system
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.)


-- 
1034219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034219
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debomatic
Version: 0.26-1
Severity: serious
Tags: sid bookworm
User: debhel...@packages.debian.org
Usertags: systemd-files-in-usr-bookworm

Dear Maintainer,

It seems that your package debomatic is shipping files (.service, .socket or
.timer) in /usr/lib/systemd/system.

This is not supported by the version of dh_installsystemd/debhelper currently
in unstable and bookworm (See: #1031695). That means that currently your
service might not be enabled at boot and/or started as expected.

With the freeze currently in effect, debhelper will not be fixed for bookworm.

As a result, could you please move these files to /lib/systemd/system instead
so they are properly detected by debhelper?
As soon as debhelper is supporting (not until bookworm+1 aka Trixie) you will
be able to move them back to the newer location.

Note that bookworm is currently in hard freeze, please limit the changes you
are uploading to the ones fixing RC bugs.  Also note that you might have to
request a freeze exception to the release team.
See: https://release.debian.org/testing/freeze_policy.html

Feel free to contact me if you have any questions.

Kind regards,
Laurent Bigonville

The list of packages has been generated with the following command:
apt-file search -x '^/usr/lib/systemd/system/.*\.(service|timer|socket)$'|cut 
-d: -f1|sort -u
--- End Message ---
--- Begin Message ---
Source: debomatic
Source-Version: 0.26-2
Done: Luca Falavigna 

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

Debian distribution maintenance software
pp.
Luca Falavigna  (supplier of updated debomatic package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 13 Apr 2023 09:09:31 +
Source: debomatic
Binary: debomatic
Architecture: source
Version: 0.26-2
Distribution: unstable
Urgency: medium
Maintainer: Luca Falavigna 
Changed-By: Luca Falavigna 
Description:
 debomatic  - automatic build machine for Debian source packages
Closes: 1034219
Changes:
 debomatic (0.26-2) unstable; urgency=medium
 .
   * debian/patches/bug1034219.patch:
 - Install systemd unit file under /lib/systemd/system (Closes: #1034219).
Checksums-Sha1:
 e5bf146c0199b1d36a9ea7435a5be2a8ea03b60c 2282 debomatic_0.26-2.dsc
 cf934e6a8cd77386db3477fe13d872442028852b 8348 debomatic_0.26-2.debian.tar.xz
 c47fa9030f5bdb7b7d801c5c1ddde59da2c7d86f 9252 debomatic_0.26-2_amd64.buildinfo
Checksums-Sha256:
 fced9e07d580b460f723f7b4490e900cc82b279a13dba56072dd07d9056af9f3 2282 
debomatic_0.26-2.dsc
 41138c1cf65b3a76a75dd7d35d2a7c11e3c9fde529bc66b756bfb0b6825cca6a 8348 
debomatic_0.26-2.debian.tar.xz
 5e99777c6654a69f7fcf41ec9cf3269ad980fff6e4d1498aa13ff3b42b2dced7 9252 
debomatic_0.26-2_amd64.buildinfo
Files:
 a2fcb2d70598b3b3e2d3ec82727f8049 2282 devel optional debomatic_0.26-2.dsc
 c589ee095670188386595853fb50b35d 8348 devel optional 
debomatic_0.26-2.debian.tar.xz
 517ee302fd99b2f87e9e03c4dbaa4721 9252 devel optional 
debomatic_0.26-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE3cU+UTD9CCI/mJRWSQhq0+vi8x8FAmQ7/rcACgkQSQhq0+vi
8x+KRw//TBRKgu667NQw3kKZlI3UD5KwzUuSNKNPG6NoAk5Jn/hgai0NYRhXdeGx
MA7/kJL8UluFzWe6slo7dx34Wy5VkLD7XWd2Bsu8NKyRW7FLp9lRkF6NC5AbhFAF
Q/HfmpXjXWB1Az/YaIBXsc0pWrSKvUqYNTyQZRH18t4nIP2Fich5AECvNhQIKQ6E
BxD3G3QB20lWd/keDfywMDyDE3QaI7lZdi1AN1Pvt38i55WHkQ3Ak2C4Yh3QlRW5
3GNKTCXJegeEKgRxAp/SVzs/mP3yVQhNwWhmlmNLTTyxtme5OgYf0Iu3DWlgOHeM
iimY1I+2sADv3xpUGrdN6OQNRz37miZqK8RDM/2kkb9RXWXYgMhqToE2PAC/L/Dd
FZek8j4Weer2F6+NHCNoCBFSrqkA2jy0/GJvBonvzUPB+Jjmr6mFCAvOnhPVIEg2
5TRNoJWTdV8oFpGuQqmo8ynUUi3TER+L2xng+FG0NYidMpwKRZhTXTN3uGs/hZiR

Bug#1033407: duplicate bugs

2023-04-16 Thread Kentaro Hayashi
FYI:

It seems this bug was fixed in #1032989, so this bug also have to be closed.


NOTE: this fix is not landed to bookworm yet.


On Sat, 25 Mar 2023 13:20:27 +0100 Dominik Stadler  
wrote:
> merge 1033407 1032989
> 
> --
> These two bug-reports sound very similar, #1032989 has a lot of
> investigation already.



Bug#1034476: librocprim-dev: Missing Depends on libamdhip64-dev

2023-04-16 Thread Christian Kastner
Package: librocprim-dev
Version: 5.3.3-3
Severity: serious

librocprim-dev needs libamdhip64-dev, but this dependency is missing
from the package.



Bug#1034238: marked as done (fapolicyd: dh_installsystemd doesn't handle files in /usr/lib/systemd/system)

2023-04-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Apr 2023 11:03:53 +
with message-id 
and subject line Bug#1034238: fixed in fapolicyd 1.1.7-4
has caused the Debian Bug report #1034238,
regarding fapolicyd: dh_installsystemd doesn't handle files in 
/usr/lib/systemd/system
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.)


-- 
1034238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034238
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fapolicyd
Version: 1.1.7-3   
Severity: serious
Tags: sid bookworm
User: debhel...@packages.debian.org
Usertags: systemd-files-in-usr-bookworm

Dear Maintainer,

It seems that your package fapolicyd is shipping files (.service, .socket or
.timer) in /usr/lib/systemd/system.

This is not supported by the version of dh_installsystemd/debhelper currently
in unstable and bookworm (See: #1031695). That means that currently your
service might not be enabled at boot and/or started as expected.

With the freeze currently in effect, debhelper will not be fixed for bookworm.

As a result, could you please move these files to /lib/systemd/system instead
so they are properly detected by debhelper?
As soon as debhelper is supporting (not until bookworm+1 aka Trixie) you will
be able to move them back to the newer location.

Note that bookworm is currently in hard freeze, please limit the changes you
are uploading to the ones fixing RC bugs.  Also note that you might have to
request a freeze exception to the release team.
See: https://release.debian.org/testing/freeze_policy.html

Feel free to contact me if you have any questions.

Kind regards,
Laurent Bigonville

The list of packages has been generated with the following command:
apt-file search -x '^/usr/lib/systemd/system/.*\.(service|timer|socket)$'|cut 
-d: -f1|sort -u
--- End Message ---
--- Begin Message ---
Source: fapolicyd
Source-Version: 1.1.7-4
Done: Nobuhiro Iwamatsu 

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

Debian distribution maintenance software
pp.
Nobuhiro Iwamatsu  (supplier of updated fapolicyd 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: Sun, 16 Apr 2023 19:34:20 +0900
Source: fapolicyd
Architecture: source
Version: 1.1.7-4
Distribution: unstable
Urgency: medium
Maintainer: Nobuhiro Iwamatsu 
Changed-By: Nobuhiro Iwamatsu 
Closes: 1034238
Changes:
 fapolicyd (1.1.7-4) unstable; urgency=medium
 .
   * Fix install path of systemd service file from /usr/lib/systemd/system
 to /usr/lib/systemd . (Closes: #1034238)
 Add d/patches/0007-Install-service-file-to-usr-lib-systemd.patch
Checksums-Sha1:
 91387ecf03dcb50b30e13a62fa986cc121dd3825 2038 fapolicyd_1.1.7-4.dsc
 7d48ab325b8e130142a2a4bf3ceb1944f47cec69 9216 fapolicyd_1.1.7-4.debian.tar.xz
 b8ebdec7828b6ef2713237dc78e53a3db6448fa6 6310 fapolicyd_1.1.7-4_amd64.buildinfo
Checksums-Sha256:
 db3b7935de777992e165cf939815b1748e9ab46187f62e62d03adb60831d8150 2038 
fapolicyd_1.1.7-4.dsc
 c55e4772b843d94895c96fd16fdd8f2315a3a4f27e217f33421ac0ce0082f29b 9216 
fapolicyd_1.1.7-4.debian.tar.xz
 1c7e91adbba52822524d9df79651519b361932e7b81ceda92466ea95b8a3eb02 6310 
fapolicyd_1.1.7-4_amd64.buildinfo
Files:
 34885a39bb9504947fd30514fc0c9030 2038 utils optional fapolicyd_1.1.7-4.dsc
 06bba6745c490716d5e44e92b94d2482 9216 utils optional 
fapolicyd_1.1.7-4.debian.tar.xz
 1a0bc484c23c3850fe73cbeac1723cf5 6310 utils optional 
fapolicyd_1.1.7-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEXmKe5SMhlzV7hM9DMiR/u0CtH6YFAmQ70kwACgkQMiR/u0Ct
H6ZGXQ//W8dCm61AqwNAxFtSP7vKesiyEUv/8apJPDVnNkuwlrwuazWw4MgbXDPn
QhtwjhSNe28ajS3c6n/0gPD0qix4smxr6yqIjbrWrFbm5XDWTA1YJ0/WEXT25d1H
AfodNqTS4Q1tzhT5wI97KeRizY6gqo+iK6+s2UOEHy98cnGm/6XKi5qDKjJ9yBRm
9bYeMiRUjNWjJzNXDZChRXcrdbKrHdLiE+eN8GkWyQ6ynSGCj05VVmOB9avvZsfk
X6OSq3pBbmn793HRXbqOb03Y+8hYlaNXctHto3lWmXg/inZn4yvQ1dp6yile5RQj
26eWIi1bPO7yfzDHLte7GsWBU8x6ZhNBmnPukzcMTzTxpkMeDSNivJakwz8o+ppz
/VoTl7GSFWpeWNFPOMA3fDnKS/LWXg25Aejt61NnbC2PsuNOsnuABUoLe3wboXrH
7ExVN7qheBUt+DXeXtdDvdasNTQ61ZJdJhJNkv7nSHor7l1WSz2eKgMpBRF8SPOD

Bug#1034081: openbgpd: FTBFS twice in a row: src/bgpd/parse.c cannot be regenerated

2023-04-16 Thread Marco d'Itri
On Apr 08, Andreas Beckmann  wrote:

> Justification: fails to build from source twice in a row
This can be fixed by adding a build-dependency on yacc.

> openbgpd/experimental fails to build twice in a row. (I haven't checked
> whether the version in sid has the same problem.)
It does: should I bother requesting a freeze exception for this?

> The first build succeeds, a subsequent make distclean deletes
> src/bgpd/parse.c:
Indeed. The openbgpd upstream source packages are inconvenient because 
they contain generated files, but then distclean deletes them.
I would like to delete the generated files at build time to make sure 
that I do not make this mistake again, but it is not trivial since the 
Makefile does not exist until configure is run.
Is there an established design pattern for this situation?

-- 
ciao,
Marco


signature.asc
Description: PGP signature


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

2023-04-16 Thread Rainer Dorsch
Hi Steve,

Am Sonntag, 16. April 2023, 00:27:46 CEST schrieben Sie:
> 
> Hello Rainer,
> 
> I've looked at the upstream bug, and all the information you provided. 
> That's awesome -- I wish that every bug submitter would be as thorough as
> you!

It was not difficult and did not take a lot of time. But I can imagine that 
with 
such a popular package as digikam, there are many uses w/o any packaging or 
development experience.

> It seems that, even with disabling the splash screen, you still experience
> the bug -- is that correct?

With splash screen disabled, I don't see it anymore ;-).

> I can say that I'm not experiencing any such crash.  I created a new user to
> test from scratch.  I see the splash screen come and go, then the pop-up
> that offers to download the faces data files.  I can download them or not
> and it all works fine either way.
> 
> So it's puzzling.  I'm also using an x64 system, but I run on the "sid/
> unstable" distribution so I have slightly different versions of the
> dependency packages.   Maybe it's worth attempting an upgrade of some or
> all of these to see if the problem goes away?

Let me elaborate a somewhat:

The spash screen bug I found is visible in the backtrace in comment 5:

https://bugs.kde.org/show_bug.cgi?id=466170#c5

According to Maik, the bug is triggered by a race condition (comment 6). I.e. 
even with exact the same software configuration, there is a good chance that 
you don't see it, because the timing on your hardware might be different 
(different CPU, memory latencies, cache configurations,). In particular if 
it is hard to hit the race condition, as it seems to be the case.

In comment 9

https://bugs.kde.org/show_bug.cgi?id=466170#c9

Maik provided a fix for the splash screen issue.

I see to good options to handle this:

Either check if the commit also applies to 7.9, I would think there is a good 
chance for this.  I can help and build 7.9 on my system with the commit. Do 
you know a good way to generate a patch for debian/patches out of the commit 
above? And if yes, would it be sufficient to add it to debian/patches/series 
before building?

Or since splash screen is not a key feature, disable splash screen in the 
default config and tell the users who upgrade that disabling splash screen 
would be a workaround for this issue. At least some packages notify users on 
important changes before the upgrade.


But the more important issue is the crash which I see after disabling splash 
screen. The backtrace is provided in comment 7

https://bugs.kde.org/show_bug.cgi?id=466170#c7

Here Maik thinks it is a Debian problem, related to QtWebEngine.


> Perhaps start with libkf5configcore5, since the failing assert seems to be
> in that library:
> 
>   qt_assert_x(char const*, char const*, char const*, int) () at /lib/
> x86_64-linux-gnu/libQt5Core.so.5

Looking at the changes that is likely a red herring:

https://tracker.debian.org/news/1427674/accepted-kconfig-51030-2-source-into-unstable/

I am on Xorg, are you using Wayland?

> Here is the list from my system today.
> 
> Versions of packages digikam depends on:
> ii  digikam-data  4:7.9.0-1
> ii  digikam-private-libs  4:7.9.0-1+b2
> ii  libc6 2.36-9
> ii  libgcc-s1 12.2.0-14
> ii  libkf5configcore5 5.103.0-2
> ii  libkf5coreaddons5 5.103.0-1
> ii  libkf5i18n5   5.103.0-1
> ii  libmagick++-6.q16-8   8:6.9.11.60+dfsg-1.6
> ii  libqt5core5a  5.15.8+dfsg-7
> ii  libqt5gui55.15.8+dfsg-7
> ii  libqt5sql55.15.8+dfsg-7
> ii  libqt5sql5-mysql  5.15.8+dfsg-7
> ii  libqt5sql5-sqlite 5.15.8+dfsg-7
> ii  libqt5widgets55.15.8+dfsg-7
> ii  libstdc++612.2.0-14
> ii  perl  5.36.0-7
> 
> Versions of packages digikam recommends:
> ii  brave-browser [www-browser] 1.50.119
> ii  ffmpegthumbs4:22.12.3-1
> ii  firefox-esr [www-browser]   102.10.0esr-1
> ii  google-chrome-stable [www-browser]  112.0.5615.121-1
> ii  konqueror [www-browser] 4:22.12.3-1
> ii  lynx [www-browser]  2.9.0dev.12-1
> ii  w3m [www-browser]   0.5.3+git20230121-2
> 
> Versions of packages digikam suggests:
> ii  breeze-icon-theme  4:5.103.0-1
> pn  digikam-doc
> ii  systemsettings 4:5.27.2-1

How do you generate this list?

Do you know if I can disable the faces download? I am not using faces 
(assuming it is related to the the face recognition feature) and I am afraid 
that I hit more bugs afterwards, at least I have seen in previous upgrades 
that issues may also pop up in the digikam database and I am not not yet there 
:-).

Thanks
Rainer

-- 
Rainer Dorsch
http://bokomoko.de/