Bug#1037547: More info

[Bill Hay,,,]

pilgrim:/etc/fapolicyd/rules.d# ls
90-deny-execute.rules
pilgrim:/etc/fapolicyd/rules.d# cat 90-deny-execute.rules 
# Deny execution for anything untrusted

deny_audit perm=execute all : all

pilgrim:/etc/fapolicyd# cat fapolicyd.conf
#
# This file controls the configuration of the file access policy daemon.
# See the fapolicyd.conf man page for explanation.
#

permissive = 0
nice_val = 14
q_size = 640
uid = fapolicyd
gid = fapolicyd
do_stat_report = 1
detailed_report = 1
db_max_size = 50
subj_cache_size = 1549
obj_cache_size = 8191
watch_fs = ext2,ext3,ext4,tmpfs,xfs,vfat,iso9660,btrfs
trust = rpmdb,file
integrity = none
syslog_format = rule,dec,perm,auid,pid,exe,:,path,ftype,trust
rpm_sha256_only = 0
allow_filesystem_mark = 0

  
Looks like the shipped policy is to deny all execute and with permissive=0 this 
is enforced.  

Processed: severity of 1037548 is normal

[Debian Bug Tracking System]

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

> severity 1037548 normal
Bug #1037548 [qbittorrent-nox] qbittorrent-nox: web interface doesn't display 
content, browsers download html instead
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.

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

Processed: For some reason reportbug only let me set this as high as important.

[Debian Bug Tracking System]

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

> severity 1037547 critical
Bug #1037547 [fapolicyd] fapolicyd: Installation of fapolicyd via apt caused 
everything to immediately become non-executable.
Severity set to 'critical' from 'important'
>
End of message, stopping processing here.

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

Bug#1037548: qbittorrent-nox: web interface doesn't display content, browsers download html instead

[Christian Marillat]

1037548 severity normal
1037548 tags unreproducible
thanks

On 13 juin 2023 19:26, allan grossman  wrote:

> Package: qbittorrent-nox
> Version: 4.5.3-2
> Severity: grave
> Justification: renders package unusable
> X-Debbugs-Cc: wizard10...@gmail.com

[...]

> * What was the outcome of this action?
>
> No change.  Browsers still download html code instead of displaying html
> content.
>
> * What outcome did you expect instead?
>
> I expected the web interface to display in a browser window.

Work fine for me with firefox.

Maybe the problem come from your browser ?

Christian

Processed: fixed 1034752 in 2.4.0+dfsg-1~exp1

[Debian Bug Tracking System]

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

> fixed 1034752 2.4.0+dfsg-1~exp1
Bug #1034752 [src:gluegen2] embeds non-free headers
Marked as fixed in versions gluegen2/2.4.0+dfsg-1~exp1.
> thanks
Stopping processing here.

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

Bug#1037548: qbittorrent-nox: web interface doesn't display content, browsers download html instead

[allan grossman]

Package: qbittorrent-nox
Version: 4.5.3-2
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: wizard10...@gmail.com

Dear Maintainer,

* What led up to the situation?

Running Debian Unstable, upgraded qbittorrent-nox to version 4.5.3-2 and
restarted its systemd service.

* What exactly did you do (or not do) that was effective (or ineffective)?

Reinstalled qbittorent-nox and libtorrent-rasterbar2.0 - ineffective
Renamed ~/.config/qBittorrent so get a clean config - ineffective

* What was the outcome of this action?

No change.  Browsers still download html code instead of displaying html
content.

* What outcome did you expect instead?

I expected the web interface to display in a browser window.


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (900, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: ia64

Kernel: Linux 6.1.0-9-amd64 (SMP w/8 CPU threads; PREEMPT)
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 qbittorrent-nox depends on:
ii  libc62.36-9
ii  libgcc-s113.1.0-5
ii  libqt5sql5-sqlite5.15.8+dfsg-12
ii  libqt6core6  6.4.2+dfsg-11
ii  libqt6network6   6.4.2+dfsg-11
ii  libqt6sql6   6.4.2+dfsg-11
ii  libqt6xml6   6.4.2+dfsg-11
ii  libssl3  3.0.9-1
ii  libstdc++6   13.1.0-5
ii  libtorrent-rasterbar2.0  2.0.9-1
ii  zlib1g   1:1.2.13.dfsg-1

qbittorrent-nox recommends no packages.

qbittorrent-nox suggests no packages.

-- no debconf information
[Unit]
Description=qBittorrent Daemon Service
After=network-online.target

[Service]
User=wizard
Group=wizard
ExecStart=/usr/bin/ionice -c2 -n7 /usr/bin/qbittorrent-nox --webui-port=8090
ExecStop=/usr/bin/killall -w qbittorrent-nox

[Install]
WantedBy=multi-user.target
[AddNewTorrentDialog]
DialogSize=@Size(900 665)
Enabled=false
RememberLastSavePath=false
SplitterState=@ByteArray(\0\0\0\xff\0\0\0\x1\0\0\0\x2\0\0\x1\x93\0\0\x1\0\0\xff\xff\xff\xff\x1\0\0\0\x1\0)
TopLevel=true
TreeHeaderState="@ByteArray(\0\0\0\xff\0\0\0\0\0\0\0\x1\0\0\0\0\0\0\0\0\x1\0\0\0\0\0\0\0\0\0\0\0\x6\x34\0\0\0\x3\0\0\0\x2\0\0\0\x64\0\0\0\x4\0\0\0\x64\0\0\0\x5\0\0\0\x64\0\0\x1,\0\0\0\x6\x1\x1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\x64\xff\xff\xff\xff\0\0\0\x81\0\0\0\0\0\0\0\x6\0\0\0\x64\0\0\0\x1\0\0\0\0\0\0\0\x64\0\0\0\x1\0\0\0\0\0\0\0\0\0\0\0\x1\0\0\0\0\0\0\0\x64\0\0\0\x1\0\0\0\0\0\0\0\0\0\0\0\x1\0\0\0\0\0\0\0\0\0\0\0\x1\0\0\0\0\0\0\x3\xe8\0\xff\xff\xff\xff)"

[Application]
FileLogger\Age=1
FileLogger\AgeType=1
FileLogger\Backup=true
FileLogger\DeleteOld=true
FileLogger\Enabled=false
FileLogger\MaxSizeBytes=66560
FileLogger\Path=/home/wizard/.local/share/qBittorrent/logs

[AutoRun]
OnTorrentAdded\Enabled=false
OnTorrentAdded\Program=
enabled=false
program=

[BitTorrent]
Session\AddExtensionToIncompleteFiles=true
Session\AlternativeGlobalDLSpeedLimit=0
Session\AlternativeGlobalUPSpeedLimit=0
Session\AnnounceToAllTrackers=true
Session\AsyncIOThreadsCount=32
Session\BTProtocol=TCP
Session\CheckingMemUsageSize=320
Session\DefaultSavePath=/media/internal/temp
Session\DisableAutoTMMByDefault=false
Session\DisableAutoTMMTriggers\CategorySavePathChanged=false
Session\DisableAutoTMMTriggers\DefaultSavePathChanged=false
Session\ExcludedFileNames=
Session\FilePoolSize=1000
Session\GlobalMaxRatio=-1
Session\GlobalMaxSeedingMinutes=1
Session\IgnoreLimitsOnLAN=true
Session\Interface=wg-mullvad
Session\InterfaceAddress=0.0.0.0
Session\InterfaceName=wg-mullvad
Session\LSDEnabled=false
Session\MaxActiveDownloads=20
Session\MaxActiveTorrents=20
Session\MaxActiveUploads=20
Session\MaxConnections=1
Session\MaxConnectionsPerTorrent=1000
Session\MaxRatioAction=0
Session\MaxUploads=1000
Session\MaxUploadsPerTorrent=1000
Session\Port=54881
Session\Preallocation=true
Session\QueueingSystemEnabled=true
Session\SaveResumeDataInterval=10
Session\uTPRateLimited=false

[Core]
AutoDeleteAddedTorrentFile=Never

[DownloadFromURLDialog]
Size=@Size(501 220)

[GUI]
DownloadTrackerFavicon=false
Log\Enabled=false
Notifications\Enabled=true
Notifications\Timeout=-1
Notifications\TorrentAdded=false

[IPSubnetWhitelistOptionsDialog]
Size=@Size(360 450)

[LegalNotice]
Accepted=true

[MainWindow]
geometry="@ByteArray(\x1\xd9\xd0\xcb\0\x3\0\0\0\0\0$\0\0\0\x17\0\0\x6\x85\0\0\x3\xe1\0\0\0%\0\0\0;\0\0\x6\x84\0\0\x3\xde\0\0\0\0\0\0\0\0\a\x80\0\0\0%\0\0\0;\0\0\x6\x84\0\0\x3\xde)"
qt5\vsplitterState=@ByteArray(\0\0\0\xff\0\0\0\x1\0\0\0\x2\0\0\0\0\0\0\x6L\x1\xff\xff\xff\xff\x1\0\0\0\x1\0)

[Meta]
MigrationVersion=4

[Network]
Cookies=@Invalid()
PortForwardingEnabled=true
Proxy\OnlyForTorrents=false

[OptionsDialog]
HorizontalSplitterSizes=119, 634
LastViewedPage=2
Size=@Size(779 591)

[Preferences]
Advanced\DisableRecursiveDownload=false
Advanced\EnableIconsInMenus=true
Advanced\Recheck

Bug#1037435: marked as done (ojalgo tests using the network at build time (again))

[Debian Bug Tracking System]

Your message dated Tue, 13 Jun 2023 22:51:08 +
with message-id 
and subject line Bug#1037435: fixed in ojalgo 52.0.1+ds-2
has caused the Debian Bug report #1037435,
regarding ojalgo tests using the network at build time (again)
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.)


-- 
1037435: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037435
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ojalgo
Version: 52.0.1+ds-1
Severity: serious
Tags: patch
Justification: Policy 4.9
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu mantic ubuntu-patch

Hi Pierre,

The ojalgo package has been failing to build from source in Ubuntu, because
its tests are trying to access the network:

[...]
[ERROR] Failures: 
[ERROR]   YahooDataSourceTest.testFetchDaily:54 No data!
[ERROR]   YahooDataSourceTest.testFetchMonthly:62 No data!
[ERROR]   YahooDataSourceTest.testFetchWeekly:70 No data!
[ERROR]   
YahooDataSourceTest.testYahooDailyAAPL:79->FinanceSeriesTests.assertAtLeastExpectedItems:64
 No data!
[ERROR]   
YahooDataSourceTest.testYahooMonthlyAAPL:87->FinanceSeriesTests.assertAtLeastExpectedItems:64
 No data!
[ERROR]   
YahooDataSourceTest.testYahooWeeklyAAPL:95->FinanceSeriesTests.assertAtLeastExpectedItems:64
 No data!
[ERROR] Errors: 
[ERROR]   
YahooDataSourceTest.testDeriveDistributions:47->FinanceSeriesTests.doTestDeriveDistribution:84
 » NegativeArraySize
[ERROR]   OptimisationServiceTest.testEnvironment:67 » Runtime 
java.util.concurrent.Exec...
[ERROR]   OptimisationServiceTest.testTest:55 » Runtime 
java.util.concurrent.ExecutionEx...
[ERROR]   OptimisationServiceTest.testVeryBasicModel:41 » Runtime 
java.util.concurrent.E...
[...]

  (https://launchpad.net/ubuntu/+source/ojalgo/52.0.1+ds-1/+build/26010077)

There was already a patch in the source to disable network tests, but it
appears that some new network tests have now been added.  I've extended the
patch to disable these tests as well; please see the attached diff.

Thanks for considering,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru ojalgo-52.0.1+ds/debian/patches/no_network_tests.patch 
ojalgo-52.0.1+ds/debian/patches/no_network_tests.patch
--- ojalgo-52.0.1+ds/debian/patches/no_network_tests.patch  2023-01-18 
13:33:30.0 -0800
+++ ojalgo-52.0.1+ds/debian/patches/no_network_tests.patch  2023-06-12 
12:54:52.0 -0700
@@ -4,8 +4,10 @@
 Reviewed-by: Pierre Gruet 
 Last-Update: 2022-12-17
 
 
a/src/test/java/org/ojalgo/data/domain/finance/series/AlphaVantageDataSourceTest.java
-+++ 
b/src/test/java/org/ojalgo/data/domain/finance/series/AlphaVantageDataSourceTest.java
+Index: 
ojalgo-52.0.1+ds/src/test/java/org/ojalgo/data/domain/finance/series/AlphaVantageDataSourceTest.java
+===
+--- 
ojalgo-52.0.1+ds.orig/src/test/java/org/ojalgo/data/domain/finance/series/AlphaVantageDataSourceTest.java
 
ojalgo-52.0.1+ds/src/test/java/org/ojalgo/data/domain/finance/series/AlphaVantageDataSourceTest.java
 @@ -22,6 +22,7 @@
   */
  package org.ojalgo.data.domain.finance.series;
@@ -22,3 +24,43 @@
  public class AlphaVantageDataSourceTest extends FinanceSeriesTests {
  
  public AlphaVantageDataSourceTest() {
+Index: 
ojalgo-52.0.1+ds/src/test/java/org/ojalgo/data/domain/finance/series/YahooDataSourceTest.java
+===
+--- 
ojalgo-52.0.1+ds.orig/src/test/java/org/ojalgo/data/domain/finance/series/YahooDataSourceTest.java
 
ojalgo-52.0.1+ds/src/test/java/org/ojalgo/data/domain/finance/series/YahooDataSourceTest.java
+@@ -22,6 +22,7 @@
+  */
+ package org.ojalgo.data.domain.finance.series;
+ 
++import org.junit.jupiter.api.Disabled;
+ import org.junit.jupiter.api.Test;
+ import org.ojalgo.TestUtils;
+ import org.ojalgo.type.CalendarDateUnit;
+@@ -31,6 +32,7 @@
+  *
+  * @author apete
+  */
++@Disabled("Requires network access")
+ public class YahooDataSourceTest extends FinanceSeriesTests {
+ 
+ private static YahooSession SESSION = new YahooSession();
+Index: 
ojalgo-52.0.1+ds/src/test/java/org/ojalgo/optimisation/service/OptimisationServiceTest.java
+===
+--- 
ojalgo-52.0.1+ds.orig/src/test/java/org/ojalgo/optimisation/service/OptimisationServi

Bug#1037535: libnet-twitter-perl: "Could not authenticate you." errors since 2023-06-13

[Vincent Lefevre]

On 2023-06-13 23:18:47 +0200, Vincent Lefevre wrote:
> It seems that something changed on Twitter, which yields the
> "Could not authenticate you." error with Net::Twitter. This
> started to happen a few hours ago.

I think that's it:

https://twitter.com/TwitterDev/status/1621026986784337922

"Starting February 9, we will no longer support free access to the
Twitter API, both v2 and v1.1. A paid basic tier will be available
instead"

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1037541: libguestfs: FTBFS: supermin: error: lstat: Value too large for defined data type: /var/tmp/supermin2b73c8.tmpdir/base.d/init

[Sebastian Ramacher]

Source: libguestfs
Version: 1:1.50.1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=libguestfs&arch=i386&ver=1%3A1.50.1-1&stamp=1686678530&raw=0

tar: etc: implausibly old time stamp -9223372036854775808
tar: usr/sbin/guestfsd: implausibly old time stamp -9223372036854775808
tar: usr/sbin: implausibly old time stamp -9223372036854775808
tar: usr: implausibly old time stamp -9223372036854775808
supermin: build: visiting 
/<>/debian/build-4/appliance/supermin.d/excludefiles type 
uncompressed excludefiles
supermin: build: visiting 
/<>/debian/build-4/appliance/supermin.d/hostfiles type 
uncompressed hostfiles
supermin: build: visiting 
/<>/debian/build-4/appliance/supermin.d/init.tar.gz type gzip base 
image (tar)
tar: init: implausibly old time stamp -9223372036854775808
supermin: build: visiting 
/<>/debian/build-4/appliance/supermin.d/packages type uncompressed 
packages
supermin: build: visiting 
/<>/debian/build-4/appliance/supermin.d/udev-rules.tar.gz type 
gzip base image (tar)
tar: etc/udev/rules.d/99-guestfs-serial.rules: implausibly old time stamp 
-9223372036854775808
tar: etc/udev/rules.d: implausibly old time stamp -9223372036854775808
tar: etc/udev: implausibly old time stamp -9223372036854775808
tar: etc: implausibly old time stamp -9223372036854775808
supermin: mapping package names to installed packages
supermin: resolving full list of package dependencies
supermin: build: 247 packages, including dependencies
supermin: build: 10324 files
supermin: build: 5081 files, after matching excludefiles
supermin: build: 5084 files, after adding hostfiles
supermin: build: 5084 files, after removing unreadable files
supermin: build: 5085 files, after munging
supermin: kernel: looking for kernel using environment variables ...
supermin: kernel: looking for kernels in /lib/modules/*/vmlinuz ...
supermin: kernel: looking for kernels in /boot ...
supermin: kernel: kernel version of /boot/vmlinuz-6.1.0-9-686-pae = 
6.1.0-9-686-pae (from content)
supermin: kernel: picked modules path /lib/modules/6.1.0-9-686-pae
supermin: kernel: picked vmlinuz /boot/vmlinuz-6.1.0-9-686-pae
supermin: kernel: kernel_version 6.1.0-9-686-pae
supermin: kernel: modpath /lib/modules/6.1.0-9-686-pae
supermin: ext2: creating empty ext2 filesystem 
'/<>/debian/build-4/tmp/.guestfs-2952/appliance.d.cs96n5v2/root'
supermin: ext2: populating from base image
supermin: error: lstat: Value too large for defined data type: 
/var/tmp/supermin2b73c8.tmpdir/base.d/init
libguestfs: error: /usr/bin/supermin exited with error status 1, see debug 
messages above
libguestfs: closing guestfs handle 0x57dcea80 (state 0)
libguestfs: command: run: rm
libguestfs: command: run: \ -rf 
/<>/debian/build-4/tmp/libguestfsLo9Elv
make[2]: *** [Makefile:1763: quickcheck] Error 1
make[2]: Leaving directory '/<>/debian/build-4'
make[1]: *** [debian/rules:133: override_dh_auto_test] Error 2
make[1]: Leaving directory '/<>'

Cheers
-- 
Sebastian Ramacher

Bug#1037540: Thunar (4.18.4-1) Segfaults If Using Tab Key While Using Split View

[Fjords]

Package: thunar
Version: 4.18.4-1
Severity: grave

Hello, Thunar has been regularly crashing if using the current stable 
build with split view enabled.


To reproduce this issue, open a new Thunar instance, enable split view, 
and have one of the directories contain images, focus on the 
image-containing directory, and then press the Tab key multiple times 
until it crashes. Terminal output: https://pastebin.com/2mpdYyUb


This has been apparently fixed upstream with 4.18.5, but linking it here 
anyway for your information: 
https://gitlab.xfce.org/xfce/thunar/-/issues/1067


Thank you.

Bug#1037538: gerbera: FTBFS with libupnp17

[Sebastian Ramacher]

Source: gerbera
Version: 1.1.0+dfsg-3.1
Severity: serious
Tags: ftbfs sid trixie
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=gerbera&arch=amd64&ver=1.1.0%2Bdfsg-3.1%2Bb2&stamp=1686649192&raw=0

-- Found LFS: TRUE  
CMake Warning (dev) at 
/usr/share/cmake-3.25/Modules/FindPackageHandleStandardArgs.cmake:438 (message):
  The package name passed to `find_package_handle_standard_args` (UPnP) does
  not match the name of the calling package (LibUpnp).  This can lead to
  problems in calling code that expects `find_package` result variables
  (e.g., `_FOUND`) to follow a certain pattern.
Call Stack (most recent call first):
  cmake/FindLibUpnp.cmake:39 (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
  CMakeLists.txt:372 (find_package)
This warning is for project developers.  Use -Wno-dev to suppress it.

-- Found UPnP: /usr/lib/x86_64-linux-gnu/libupnp.so (found version "17.1.8") 
CMake Error at CMakeLists.txt:389 (message):
  

  !! You are using a very old 1.8 snapshot.  Please upgrade to a 1.8.x
  release from upstream (https://github.com/mrjimenez/pupnp) !!



-- Configuring incomplete, errors occurred!

Cheers
-- 
Sebastian Ramacher

Bug#1037535: libnet-twitter-perl: "Could not authenticate you." errors since 2023-06-13

[Vincent Lefevre]

Package: libnet-twitter-perl
Version: 4.01043-2
Severity: grave
Justification: renders package unusable

It seems that something changed on Twitter, which yields the
"Could not authenticate you." error with Net::Twitter. This
started to happen a few hours ago.

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-security'), (500, 
'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
merged-usr: no
Architecture: amd64 (x86_64)

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

Versions of packages libnet-twitter-perl depends on:
ii  libcarp-clan-perl  6.08-2
ii  libclass-load-perl 0.25-2
ii  libcrypt-ssleay-perl   0.73.06-2+b1
ii  libdata-visitor-perl   0.31-1
ii  libdatetime-format-strptime-perl   1.7900-1
ii  libdatetime-perl   2:1.59-1
ii  libdevel-stacktrace-perl   2.0400-2
ii  libdigest-hmac-perl1.04+dfsg-2
ii  libhtml-parser-perl3.81-1
ii  libio-socket-ssl-perl  2.083-1
ii  libjson-maybexs-perl   1.004004-1
ii  liblwp-protocol-https-perl 6.10-1
ii  libmoose-perl  2.2203-1
ii  libmoosex-role-parameterized-perl  1.11-2
ii  libnamespace-autoclean-perl0.29-2
ii  libnet-http-perl   6.22-1
ii  libnet-oauth-perl  0.28-4
ii  libtry-tiny-perl   0.31-2
ii  liburi-perl5.19-1
ii  libwww-perl6.70-1
ii  perl   5.36.0-7

libnet-twitter-perl recommends no packages.

libnet-twitter-perl suggests no packages.

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1030966: marked as done (ruby-jekyll-remote-theme accesses the internet during the build)

[Debian Bug Tracking System]

Your message dated Tue, 13 Jun 2023 21:13:23 +
with message-id 
and subject line Bug#1030966: fixed in ruby-jekyll-remote-theme 0.4.3-4
has caused the Debian Bug report #1030966,
regarding ruby-jekyll-remote-theme accesses the internet during the build
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.)


-- 
1030966: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030966
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-jekyll-remote-theme
Version: 0.4.3-3
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-jekyll-remote-theme.html

...
2) Jekyll::RemoteTheme::Munger with a malicious theme requires whitelisted 
plugins
 Failure/Error:
   http.request(request) do |response|
 raise_unless_sucess(response)
 enforce_max_file_size(response.content_length)
 response.read_body do |chunk|
   zip_file.write chunk
 end
   end

 SocketError:
   Failed to open TCP connection to codeload.github.com:443 (getaddrinfo: 
Temporary failure in name resolution)
...
Failed examples:

rspec ./spec/jekyll-remote-theme/munger_spec.rb:127 # 
Jekyll::RemoteTheme::Munger with a malicious theme doesn't require malicious 
plugins
rspec ./spec/jekyll-remote-theme/munger_spec.rb:122 # 
Jekyll::RemoteTheme::Munger with a malicious theme requires whitelisted plugins
rspec ./spec/jekyll-remote-theme/munger_spec.rb:116 # 
Jekyll::RemoteTheme::Munger with a malicious theme sets the theme
rspec ./spec/jekyll-remote-theme/munger_spec.rb:99 # 
Jekyll::RemoteTheme::Munger with a remote theme requires plugins
rspec ./spec/jekyll-remote-theme/munger_spec.rb:93 # 
Jekyll::RemoteTheme::Munger with a remote theme sets layouts
rspec ./spec/jekyll-remote-theme/munger_spec.rb:73 # 
Jekyll::RemoteTheme::Munger with a remote theme downloads
rspec ./spec/jekyll-remote-theme/munger_spec.rb:89 # 
Jekyll::RemoteTheme::Munger with a remote theme sets include paths
rspec ./spec/jekyll-remote-theme/munger_spec.rb:67 # 
Jekyll::RemoteTheme::Munger with a remote theme sets the theme
rspec ./spec/jekyll-remote-theme/munger_spec.rb:77 # 
Jekyll::RemoteTheme::Munger with a remote theme sets sass paths
rspec ./spec/jekyll_remote_theme_spec.rb:13 # Jekyll::RemoteTheme inits
...
--- End Message ---
--- Begin Message ---
Source: ruby-jekyll-remote-theme
Source-Version: 0.4.3-4
Done: Lucas Kanashiro 

We believe that the bug you reported is fixed in the latest version of
ruby-jekyll-remote-theme, which is due to be installed in the Debian FTP 
archive.

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

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

Debian distribution maintenance software
pp.
Lucas Kanashiro  (supplier of updated 
ruby-jekyll-remote-theme 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, 13 Jun 2023 16:40:33 -0300
Source: ruby-jekyll-remote-theme
Architecture: source
Version: 0.4.3-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Lucas Kanashiro 
Closes: 1030966
Changes:
 ruby-jekyll-remote-theme (0.4.3-4) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Daniel Leidert ]
   * d/ruby-tests.rake: Revert a debugging commit that enabled tests by default
 that access the internet (closes: #1030966) (LP: #2023682).
 .
   [ Lucas Kanashiro ]
   * d/p/0005-Skip-integration-tests-relying-on-jekyll-theme-prime.patch: skip
 failing integration tests
Checksums-Sha1:
 69628f9291327a889d15ed73fb69c3506f302064 2575 
ruby-jekyll-remote-theme_0.4.3-4.dsc
 f7da23b7bee73c46e01a58a77e97b55e5a06603b 5176 
ruby-jekyll-remote-theme_0.4.3-4.debian.tar.xz
Checksums-Sha256:
 be02f1335f8b0571423acdc01aaa9f3eac2c14bb3072dd0136599adb30c324e9 2575 
ruby-jekyll-remote-theme_0.4.3-4.dsc
 93f13111e02fad2f2f7ca0aa9be50d76c4362b7b16159a6a9c432b32520f8636 5176 
ruby-jekyll-remote-theme_0.4.3-4.debian.tar.xz
Files:
 97f375bbcbcf4c4cc3db2eb85c95869d 2575 ruby optional 
ruby-jekyll-remote-theme_0.4.3-4.dsc
 11e2dff8cd1946ab370e686abcb020e8 5176 ruby optional 
ruby-jekyll-remote-theme_0.4.3-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEjtbD+LrJ23/BMKhw+COicpiDyXwFAmSIyOEVHGt

Processed: Re: ojalgo tests using the network at build time (again)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #1037435 [ojalgo] ojalgo tests using the network at build time (again)
Added tag(s) pending.

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

Bug#1037435: ojalgo tests using the network at build time (again)

[Pierre Gruet]

Control: tags -1 pending

Hello Steve,

Thanks a lot for the submission and the patch -- as usual! I am sorry 
there were still tests using the network.


Upload pending.

Best,

--
Pierre


OpenPGP_signature
Description: OpenPGP digital signature

Processed: affects 1030129

[Debian Bug Tracking System]

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

> affects 1030129 src:mysql-workbench
Bug #1030129 [ca-certificates-java] ca-certificates-java - Fails to install: 
Error loading java.security file
Added indication that 1030129 affects src:mysql-workbench
> thanks
Stopping processing here.

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

Processed: severity of 1037485 is normal

[Debian Bug Tracking System]

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

> severity 1037485 normal
Bug #1037485 [open-vm-tools] Adsense of ovt in Debian 12 iso image
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Processed: tagging 1037494

[Debian Bug Tracking System]

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

> tags 1037494 + sid trixie
Bug #1037494 [src:redmine] FTBFS, fails to install on sid due to updated 
nokogiri
Added tag(s) trixie and sid.
> thanks
Stopping processing here.

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

Processed: tagging 1036869

[Debian Bug Tracking System]

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

> tags 1036869 + sid trixie
Bug #1036869 [src:ghostscript] ghostscript: Needs commitment for Debian 
downstream maintenance
Added tag(s) trixie and sid.
> thanks
Stopping processing here.

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

Processed: tagging 1037472

[Debian Bug Tracking System]

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

> tags 1037472 + sid trixie
Bug #1037472 [src:molmodel] molmodel: FTBFS with gemmi 0.6.2+ds-1
Added tag(s) trixie and sid.
> thanks
Stopping processing here.

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

Processed: tagging 1037480

[Debian Bug Tracking System]

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

> tags 1037480 + sid trixie
Bug #1037480 [src:ycmd] autopkgtest fails with golang-1.20
Added tag(s) sid and trixie.
> thanks
Stopping processing here.

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

Processed: tagging 1037415

[Debian Bug Tracking System]

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

> tags 1037415 + sid trixie
Bug #1037415 {Done: Peter Michael Green } 
[librust-grep-printer-dev] librust-grep-printer-dev: impossible to install: 
depends on gone package librust-base64-0.13+default-dev
Added tag(s) sid and trixie.
> thanks
Stopping processing here.

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

Processed: tagging 1037463

[Debian Bug Tracking System]

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

> tags 1037463 + sid trixie
Bug #1037463 [src:macromoleculebuilder] macromoleculebuilder: FTBFS with gemmi 
0.6.2+ds-1
Added tag(s) trixie and sid.
> thanks
Stopping processing here.

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

Bug#1037529: ruby-jekyll-github-metadata: FTBFS with test failures when there's no network

[Steve Langasek]

Package: ruby-jekyll-github-metadata
Version: 2.15.0-1
Severity: serious
Tags: patch
Justification: Policy 4.9
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu mantic ubuntu-patch

Hi Daniel,

ruby-jekyll-github-metadata has a test suite that relies on accessing the
github.com website at build time, so the package fails to build in an
offline environment.

[...]
Failures:

  1) Jekyll::GitHubMetadata::SiteGitHubMunger generating repo for org with 
displayname sets title to org's displayname
 Failure/Error: expect(site.config["title"]).to eql("Jekyll")

   expected: "Jekyll"
got: #

   (compared using eql?)

   Diff:
   @@ -1,4 +1,7 @@
   -"Jekyll"
   +#
 # ./spec/site_github_munger_spec.rb:177:in `block (3 levels) in '
 # 
/usr/share/rubygems-integration/all/gems/webmock-3.18.1/lib/webmock/rspec.rb:37:in
 `block (2 levels) in '
[...]

  
(https://launchpad.net/ubuntu/+source/ruby-jekyll-github-metadata/2.15.0-1/+build/26010086)

The attached patch filters out those source files whose tests fail when
offline.  I've uploaded it to Ubuntu to fix a build failure there.

Thanks for considering,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru ruby-jekyll-github-metadata-2.15.0/debian/ruby-tests.rake 
ruby-jekyll-github-metadata-2.15.0/debian/ruby-tests.rake
--- ruby-jekyll-github-metadata-2.15.0/debian/ruby-tests.rake   2023-02-09 
02:27:58.0 -0800
+++ ruby-jekyll-github-metadata-2.15.0/debian/ruby-tests.rake   2023-06-13 
13:27:27.0 -0700
@@ -2,7 +2,11 @@
 
 skip = [
   './spec/integration_spec.rb',
-  './spec/metadata_drop_spec.rb'
+  './spec/metadata_drop_spec.rb',
+  './spec/site_github_munger_spec.rb',
+  './spec/owner_spec.rb',
+  './spec/client_spec.rb',
+  './spec/repository_spec.rb'
 ]
 
 Gem2Deb::Rake::RSpecTask.new do |spec|

Bug#1036359: elpa-markdown-toc -- crashes with (wrong-type-argument consp nil)

[Antoine Beaupré]

I can confirm that trashing the eln-cache and restarting emacs with
`markdown` in the block list works.

-- 
Le monochrome, c'est pour ceux qui s'intéressent (encore) au contenu.
Usenet dans ces conditions, c'est comme le web avec lynx, on prend
trop conscience du vide, c'est déprimant.
- JLC dans le Guide du linuxien pervers:
  "Coup de cafard..."

Bug#923824: marked as done (libdancer2-plugin-database-perl: FTBFS randomly (failing tests))

[Debian Bug Tracking System]

Your message dated Tue, 13 Jun 2023 19:06:09 +
with message-id 
and subject line Bug#923824: fixed in libdancer2-plugin-database-perl 2.17-3
has caused the Debian Bug report #923824,
regarding libdancer2-plugin-database-perl: FTBFS randomly (failing tests)
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.)


-- 
923824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923824
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libdancer2-plugin-database-perl
Version: 2.17-1
Severity: important
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_auto_configure -i
perl -I. Makefile.PL INSTALLDIRS=vendor "OPTIMIZE=-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" 
"LD=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro"
Checking if your kit is complete...
Looks good
Generating a Unix-style Makefile
Writing Makefile for Dancer2::Plugin::Database
Writing MYMETA.yml and MYMETA.json
   dh_auto_build -i
make -j1
make[1]: Entering directory '/<>'
cp lib/Dancer2/Plugin/Database.pm blib/lib/Dancer2/Plugin/Database.pm
Manifying 1 pod document
make[1]: Leaving directory '/<>'
   dh_auto_test -i
make -j1 test TEST_VERBOSE=1
make[1]: Entering directory '/<>'
PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" 
"-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib', 'blib/arch')" 
t/*.t
# Testing Dancer2::Plugin::Database 2.17, with Dancer2 0.207000 in Perl 
5.028001, /usr/bin/perl
t/00-load.t ... 
1..1
ok 1 - use Dancer2::Plugin::Database;
ok
#   Failed test 'database_connection_failed hook fires'
#   at t/01-basic.t line 247.
#  got: ''
# expected: '1'
# Looks like you failed 1 test of 43.
t/01-basic.t .. 
ok 1 - Got a code ref
ok 2 - database_connected hook fires
ok 3 - database_error hook fires
ok 4 - handle isa('DBI::db')
ok 5 - handle isa('Dancer::Plugin::Database::Core::Handle')
ok 6 - handle isa('t::lib::TestHandleClass')
ok 7 - handle is not a duck
ok 8 - db is created
ok 9 - GET / is found
ok 10 - content looks good for / (7 users afiter DB initialisation)
ok 11 - GET /user/1 is found
ok 12 - content looks good for /user/1
ok 13 - content looks good for /user/2
ok 14 - DELETE /user/3 is ok
ok 15 - content looks good for / (6 users after deleting one)
ok 16 - quick_insert returned OK status
ok 17 - quick_insert created a record successfully
ok 18 - quick_select returned the record created by quick_insert
ok 19 - quick_select doesn't return non-matching record
ok 20 - content looks good for /quick_select/1/category
ok 21 - content looks good for /quick_select/2/name
ok 22 - content looks good for /quick_lookup/bigpresh
ok 23 - quick_count shows 2 admins
ok 24 - Complex where clause succeeded
ok 25 - Complex not where clause succeeded
ok 26 - set operation where clause succeeded
ok 27 - quick_select returns multiple records in list context
ok 28 - quick_update returned OK status
ok 29 - quick_update updated a record successfully
ok 30 - quick_delete returned OK status
ok 31 - quick_delete deleted a record successfully
ok 32 - Fetched a single specified column OK
ok 33 - Fetched multiple specified columns OK
ok 34 - User-specified LIMIT works (1 row)
ok 35 - User-specified LIMIT works (2 row)
ok 36 - Records sorted properly
ok 37 - Records sorted properly in descending order
ok 38
ok 39 - runtime_config returned OK status
ok 40 - runtime_config got a usable database handle
ok 41
ok 42 - database_connection_lost hook fires
not ok 43 - database_connection_failed hook fires
1..43
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/43 subtests 
t/manifest.t .. skipped: Author tests not required for installation
t/pod-coverage.t .. skipped: Author tests not required for installation
t/pod.t ... 
1..1
ok 1 - POD test for blib/lib/Dancer2/Plugin/Database.pm
ok

Test Summary Report
---
t/01-basic.t(Wstat: 256 Tests: 43 Failed: 1)
  Failed test:  43
  Non-zero exit status: 1
Files=5, Tests=45,  4 wallclock secs ( 0.07 usr  0.03 sys +  2.54 cusr  0.27 
csys =  2.91 CPU)
Result: FAIL
Failed 1/5 test programs. 1/45 subtests failed.
make[1]: *** [Makefile:851: test_dynamic] Error 255
make[1]: Leaving directory '/<>'
dh_auto_test: make -j1 test TEST_V

Bug#923824: marked as pending in libdancer2-plugin-database-perl

[Étienne Mollier]

Control: tag -1 pending

Hello,

Bug #923824 in libdancer2-plugin-database-perl 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/perl-team/modules/packages/libdancer2-plugin-database-perl/-/commit/c40e2150ac2129d84869c6ae4b34fa3e0fdf9907


stabilize-test-database-connection.patch: new patch.

Closes: #923824


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/923824

Processed: Bug#923824 marked as pending in libdancer2-plugin-database-perl

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #923824 [src:libdancer2-plugin-database-perl] 
libdancer2-plugin-database-perl: FTBFS randomly (failing tests)
Added tag(s) pending.

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

Bug#1037523: gnome-shell-extension-pixelsaver doesn't work at all

[Al Ma]

Package: gnome-shell-extension-pixelsaver
Version: 1.30-1
Severity: grave
Installing and then activating gnome-shell-extension-pixelsaver has no effect. 
When the lowest buttom in the attached screenshot is clicked, no visible effect 
is observed. In the journallog I see this (up to the anonymized user name and 
machine name):
Jun 13 20:08:56 AnonymizedMachineName gnome-shell[2573]: [pixel-saver]: 
'appmenu' is not a valid button. Jun 13 20:08:56 AnonymizedMachineName 
gnome-shell[2573]: Usage of object.actor is deprecated for AppMenuButton 
get@resource:///org/gnome/shell/ui/environment.js:387:29 
enable@/usr/share/gnome-shell/extensions/pixel-sa...@deadalnix.me/app_menu.js:212:2
 
enable@/usr/share/gnome-shell/extensions/pixel-sa...@deadalnix.me/extension.js:62:10
 _callExtensionEnable@resource:///org/gnome/shell/ui/extensionSystem.js:184:32 
_onEnabledExtensionsChanged/<@resource:///org/gnome/shell/ui/extensionSystem.js:529:35
 
_onEnabledExtensionsChanged@resource:///org/gnome/shell/ui/extensionSystem.js:529:14
 
createCheckedMethod/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:686:46
 enableExtension@resource:///org/gnome/shell/ui/extensionSystem.js:211:29 
EnableExtension@resource:///org/gnome/shell/ui/shellDBus.js:447:38 
_handleMethodCall@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:324:38
 _wrapJSObject/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:401:34 
Jun 13 20:08:56 AnonymizedMachineName gnome-shell[2573]: Jun 13 20:08:56 
AnonymizedMachineName gnome-shell[2573]: Jun 13 20:08:56 AnonymizedMachineName 
gnome-shell[2573]: [pixel-saver]: Can't find original state for 
AnonymizedUserName@AnonymizedMachineName: ~ with id 0x2800020
The package is useless (on my machine, it fails to work in a visible way), 
hence the raised severity. I use  Debian stable 12 “bookworm”, gnome 1:42+1 
with X11.  The package should be repaired or removed from Debian altogether.
Gratefully,
AlMa

Bug#1036986: marked as done (libboost-json1.81-dev: missing Depends: libboost-json1.81.0 (= ${binary:Version}))

[Debian Bug Tracking System]

Your message dated Tue, 13 Jun 2023 18:07:14 +
with message-id 
and subject line Bug#1036986: fixed in boost1.81 1.81.0-5.1
has caused the Debian Bug report #1036986,
regarding libboost-json1.81-dev: missing Depends: libboost-json1.81.0 (= 
${binary:Version})
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.)


-- 
1036986: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036986
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libboost-json1.81-dev
Version: 1.81.0-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink:

0m41.1s ERROR: FAIL: Broken symlinks:
  /usr/lib/x86_64-linux-gnu/libboost_json.so -> libboost_json.so.1.81.0 
(libboost-json1.81-dev:amd64)

Please also check the other -dev packages from src:boost1.81, even if I
don't see more failures in piuparts.


cheers,

Andreas
--- End Message ---
--- Begin Message ---
Source: boost1.81
Source-Version: 1.81.0-5.1
Done: Sebastian Ramacher 

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated boost1.81 
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, 11 Jun 2023 19:35:53 +0200
Source: boost1.81
Architecture: source
Version: 1.81.0-5.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Boost Team 
Changed-By: Sebastian Ramacher 
Closes: 1036986
Changes:
 boost1.81 (1.81.0-5.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/control: Add dependency on libboost-json1.81.0 for
 libboost-json1.81-dev (Closes: #1036986)
Checksums-Sha1:
 04fee7c70cfe37fcec615abfc1667192497968f6 8146 boost1.81_1.81.0-5.1.dsc
 f32affb6eeefa542409b5b02131ca5a588aeff3b 375956 
boost1.81_1.81.0-5.1.debian.tar.xz
Checksums-Sha256:
 9305801c953c15c49d53daca675aae326764a894e8ceadb4839e40e34a434a33 8146 
boost1.81_1.81.0-5.1.dsc
 42cba5e325c8880f1015f099ac00a7d3622534f35ab740dc130550a16b4c850a 375956 
boost1.81_1.81.0-5.1.debian.tar.xz
Files:
 fd1d33daf345a150b5a4b0418c8abb65 8146 libs optional boost1.81_1.81.0-5.1.dsc
 28df7b06dcfd213e7d4f37e3baa8f7d8 375956 libs optional 
boost1.81_1.81.0-5.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQRCYn6EHZln2oPh+pAhk2s2YA/NiQUCZIYGggAKCRAhk2s2YA/N
iW4tAP4hv8P/qx03AN4+bAUw5a5s8VY36Q58iQ/7IpvWtihexAD/XY+eR1ybCxYL
MCRSN75HO1kLgIydQzqkCr/QMDGfgQA=
=vHXm
-END PGP SIGNATURE End Message ---

Bug#1016903: Does this bug affect Bookworm on AMD64?

[Alex Lieflander]

I’m sorry if this is the wrong place to post this, but I’m still trying to 
figure everything out.

Am I correct in concluding that this bug doesn’t affect packages compiled for 
Bookworm on AMD64? What about packages on AMD64 (like libpcre2-32-0) with 
32-bit runtimes/versions/ABIs or packages (like fdupes) that depend on them?

Bug#1037511: silverjuke: FTBFS with libupnp17

[Sebastian Ramacher]

Source: silverjuke
Version: 18.2.1-4
Severity: serious
Tags: ftbfs sid trixie
Justification: fails to build from source (but built successfully in the past)

https://buildd.debian.org/status/fetch.php?pkg=silverjuke&arch=amd64&ver=18.2.1-4%2Bb3&stamp=1686650401&raw=0

g++ -DPACKAGE_NAME=\"silverjuke\" -DPACKAGE_TARNAME=\"silverjuke\" 
-DPACKAGE_VERSION=\"18.2.1\" -DPACKAGE_STRING=\"silverjuke\ 18.2.1\" 
-DPACKAGE_BUGREPORT=\"r...@b44t.com\" -DPACKAGE_URL=\"\" 
-DPACKAGE=\"silverjuke\" -DVERSION=\"18.2.1\" -DENABLE_NLS=1 -DHAVE_GETTEXT=1 
-DHAVE_DCGETTEXT=1 -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 
-DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1 -DHAVE_SYS_STAT_H=1 
-DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 -DSTDC_HEADERS=1 -DHAVE_ENDIAN_H=1 -I.  
-Isrc -I/usr/lib/x86_64-linux-gnu/wx/include/gtk3-unicode-3.2 
-I/usr/include/wx-3.2 -D_FILE_OFFSET_BITS=64 -DWXUSINGDLL -D__WXGTK__ 
-I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/x86_64-linux-gnu 
-pthread-DPKGDATADIR=\"/usr/share/silverjuke\" 
-DPKGDOCDIR=\"/usr/share/doc/silverjuke\" -Wdate-time -D_FORTIFY_SOURCE=2 -Isrc 
-Wall -Wno-unused-but-set-variable -g
-I/usr/lib/x86_64-linux-gnu/wx/include/gtk3-unicode-3.2 -I/usr/include/wx-3.2 
-D_FILE_OFFSET_BITS=64 -DWXUSINGDLL -D__WXGTK__ -pthread -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o src/sjmodules/silverjuke-viewsettings.o `test -f 
'src/sjmodules/viewsettings.cpp' || echo './'`src/sjmodules/viewsettings.cpp
src/sjmodules/upnp.cpp: In member function ‘bool SjUpnpModule::InitLibupnp()’:
src/sjmodules/upnp.cpp:181:20: error: ‘UpnpInit’ was not declared in this 
scope; did you mean ‘UpnpInit2’?
  181 | if( (error=UpnpInit(NULL, 0)) != UPNP_E_SUCCESS ) {
  |^~~~
  |UpnpInit2
make[2]: *** [Makefile:3616: src/sjmodules/silverjuke-upnp.o] Error 1

Cheers
-- 
Sebastian Ramacher

Bug#1037510: texlive-lang-japanese: dangling symlinks due to missing dependencies

[Vincent Lefevre]

Package: texlive-lang-japanese
Version: 2022.20230122-1
Severity: serious

There is a dangling symlink on my machine:
/usr/share/texlive/texmf-dist/fonts/truetype/public/ipaex/ipaexm.ttf -> 
../../../../../../fonts/opentype/ipaexfont-mincho/ipaexm.ttf

This seems to be due to a missing dependency on fonts-ipaexfont-mincho.

Since texlive-lang-japanese provides the following symlinks:

lrwxrwxrwx 1 root root 60 2023-01-24 23:31:57 ipaexg.ttf -> 
../../../../../../fonts/opentype/ipaexfont-gothic/ipaexg.ttf
lrwxrwxrwx 1 root root 60 2023-01-24 23:31:57 ipaexm.ttf -> 
../../../../../../fonts/opentype/ipaexfont-mincho/ipaexm.ttf
lrwxrwxrwx 1 root root 56 2023-01-24 23:31:57 ipag.ttf -> 
../../../../../../fonts/opentype/ipafont-gothic/ipag.ttf
lrwxrwxrwx 1 root root 57 2023-01-24 23:31:57 ipagp.ttf -> 
../../../../../../fonts/opentype/ipafont-gothic/ipagp.ttf
lrwxrwxrwx 1 root root 56 2023-01-24 23:31:57 ipam.ttf -> 
../../../../../../fonts/opentype/ipafont-mincho/ipam.ttf
lrwxrwxrwx 1 root root 57 2023-01-24 23:31:57 ipamp.ttf -> 
../../../../../../fonts/opentype/ipafont-mincho/ipamp.ttf

it should also depend on fonts-ipaexfont-gothic, fonts-ipafont-gothic
and fonts-ipafont-mincho.

-- Package-specific info:
IMPORTANT INFORMATION: We will only consider bug reports concerning
the packaging of TeX Live as relevant. If you have problems with
combination of packages in a LaTeX document, please consult your
local TeX User Group, the comp.text.tex user group, the author of
the original .sty file, or any other help resource. 

In particular, bugs that are related to up-upstream, i.e., neither
Debian nor TeX Live (upstream), but the original package authors,
will be closed immediately.

   *** The Debian TeX Team is *not* a LaTeX Help Desk ***

If you report an error when running one of the TeX-related binaries 
(latex, pdftex, metafont,...), or if the bug is related to bad or wrong
output, please include a MINIMAL example input file that produces the
error in your report.

Please run your example with
(pdf)latex -recorder ...
(or any other program that supports -recorder) and send us the generated
file with the extension .fls, it lists all the files loaded during
the run and can easily explain problems induced by outdated files in
your home directory.

Don't forget to also include minimal examples of other files that are 
needed, e.g. bibtex databases. Often it also helps
to include the logfile. Please, never send included pictures!

If your example file isn't short or produces more than one page of
output (except when multiple pages are needed to show the problem),
you can probably minimize it further. Instructions on how to do that
can be found at

http://www.minimalbeispiel.de/mini-en.html (english)

or 

http://www.minimalbeispiel.de/mini.html (german)

##
minimal input file


##
other files

##
 List of ls-R files

-rw-r--r-- 1 root root 3539 2023-06-13 11:22:32 /var/lib/texmf/ls-R
lrwxrwxrwx 1 root root 29 2022-10-12 23:25:33 /usr/share/texmf/ls-R -> 
/var/lib/texmf/ls-R-TEXMFMAIN
lrwxrwxrwx 1 root root 31 2023-04-09 11:54:45 
/usr/share/texlive/texmf-dist/ls-R -> /var/lib/texmf/ls-R-TEXLIVEDIST
lrwxrwxrwx 1 root root 31 2023-04-09 11:54:45 
/usr/share/texlive/texmf-dist/ls-R -> /var/lib/texmf/ls-R-TEXLIVEDIST
##
 Config files
-rw-r--r-- 1 root root 475 2022-10-13 13:39:43 /etc/texmf/web2c/texmf.cnf
lrwxrwxrwx 1 root root 33 2023-04-09 11:54:45 
/usr/share/texmf/web2c/fmtutil.cnf -> /var/lib/texmf/fmtutil.cnf-DEBIAN
lrwxrwxrwx 1 root root 32 2023-04-09 11:54:45 /usr/share/texmf/web2c/updmap.cfg 
-> /var/lib/texmf/updmap.cfg-DEBIAN
-rw-r--r-- 1 root root 5130 2023-05-22 11:27:35 
/var/lib/texmf/tex/generic/config/language.dat
##
 Files in /etc/texmf/web2c/
total 8
-rw-r--r-- 1 root root 283 2015-09-03 02:24:29 mktex.cnf
-rw-r--r-- 1 root root 475 2022-10-13 13:39:43 texmf.cnf
##
 md5sums of texmf.d
ca40c66f144b4bafc3e59a2dd32ecb9c  /etc/texmf/texmf.d/00debian.cnf

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-security'), (500, 
'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages texlive-lang-japanese depends on:
ii  ruby  1:3.1
ii  tex-common6.18
ii  texlive-base  2022.20230122-3
ii  texlive-binaries  2022.20220321.62855-5.1
ii  texlive-lang-cjk  2022.20230122-1

Versions o

Bug#1036987: marked as done (libeccodes-data: fails to upgrade from sid: unable to install new version of '/usr/share/eccodes/definitions/bufr/tables/0/local/8/78/1/codetables/11199.table': No such fi

[Debian Bug Tracking System]

Your message dated Tue, 13 Jun 2023 15:24:05 +
with message-id 
and subject line Bug#1036987: fixed in eccodes 2.30.2-1
has caused the Debian Bug report #1036987,
regarding libeccodes-data: fails to upgrade from sid: unable to install new 
version of 
'/usr/share/eccodes/definitions/bufr/tables/0/local/8/78/1/codetables/11199.table':
 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.)


-- 
1036987: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036987
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libeccodes-data
Version: 2.30.0-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.

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

  Preparing to unpack .../libeccodes-data_2.30.0-1_all.deb ...
  Unpacking libeccodes-data (2.30.0-1) over (2.28.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libeccodes-data_2.30.0-1_all.deb (--unpack):
   unable to install new version of 
'/usr/share/eccodes/definitions/bufr/tables/0/local/8/78/1/codetables/11199.table':
 No such file or directory
  Errors were encountered while processing:
   /var/cache/apt/archives/libeccodes-data_2.30.0-1_all.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

This looks like there are some missing dpkg-maintscript-helper
symlink_to_dir calls, since e.g. in sid there is
/usr/share/eccodes/definitions/bufr/tables/0/local/8/78/1 -> 0 a symlink
while in experimental it is directory containing files.
While unpacking, dpkg seems to write a file over a dangling directory
symlink, causing the above error.

Quoting from the unhandled_symlink_to_directory_conversion template:
"""
an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:


For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.
"""

You seem to fall into the "anything interesting may happen" category,
it's the first time that I've seen such an error while caring for
piuparts.


cheers,

Andreas


libeccodes-data_2.30.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: eccodes
Source-Version: 2.30.2-1
Done: Alastair McKinstry 

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated eccodes 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, 13 Jun 2023 15:40:00 +0100
Source: eccodes
Architecture: source
Version: 2.30.2-1
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair

Bug#1036061: frr: CVE-2023-31489

[David Lamparter]

Fixed upstream in 9f1ba873637fd6ce4a2d366eafcf41402775852b for 8.4,
pending pick-up together with fix for #1036062 / CVE-2023-31490.

(Would bump to upstream 8.4.4 if that's acceptable?)


-equi

Processed: 1035829

[Debian Bug Tracking System]

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

> notfound 1035829 frr/8.4.2-1
Bug #1035829 [src:frr] frr: CVE-2022-43681 CVE-2022-40318 CVE-2022-40302
No longer marked as found in versions frr/8.4.2-1.
>
End of message, stopping processing here.

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

Bug#1036062: frr: CVE-2023-31490

[David Lamparter]

Fixed upstream in 9f1ba873637fd6ce4a2d366eafcf41402775852b on stable/8.4
branch.

Debian fix incoming with bump to 8.4.4 if that's OK?  That wouldn't be a
targeted security fix, but FRR minor versions are bugfix-only.


-equi

Bug#1036062: frr: CVE-2023-31490

[David Lamparter]

Argh, wrong bug, previous mail was for 1036061.

On Tue, Jun 13, 2023 at 03:17:52PM +0200, David Lamparter wrote:
> Fixed upstream in 9f1ba873637fd6ce4a2d366eafcf41402775852b on stable/8.4
> branch.

CVE-2023-31489 / 1036062 was fixed upstream on master but not backported
to 8.4 yet; now pending upstream CI & review in
https://github.com/FRRouting/frr/pull/13782

8.4.4 release is expected upstream shortly, including fixes for both
this and CVE-2023-31490.

-equi

Bug#1035829: frr: CVE-2022-43681 CVE-2022-40318 CVE-2022-40302

[David Lamparter]

notfound 1035829 frr/8.4.2-1
stop

On Tue, May 09, 2023 at 09:19:30PM +0200, Moritz Mühlenhoff wrote:
> CVE-2022-43681[0]:
> CVE-2022-40318[1]:
> CVE-2022-40302[2]:

All 3 issues are fixed/not present in 8.4 and thus also 8.4.2-1:

- CVE-2022-43681 - 6c4ca9812976596bf8b5226600269fc4031f1422
- CVE-2022-40318 - 1117baca3c592877a4d8a13ed6a1d9bd83977487
- CVE-2022-40302 - 3e46b43e3788f0f87bae56a86b54d412b4710286

Communication on this was indeed rather poor :( ... working with FRR
community to improve this.


-equi

Bug#1032652: marked as done (monero FTBFS with nocheck profile: python3 not found)

[Debian Bug Tracking System]

Your message dated Tue, 13 Jun 2023 13:07:38 +
with message-id 
and subject line Bug#1032652: fixed in monero 0.18.2.2+~0+20200826-1
has caused the Debian Bug report #1032652,
regarding monero FTBFS with nocheck profile: python3 not found
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.)


-- 
1032652: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032652
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: monero
Version: 0.18.0.0+~0+20200826-1
Severity: serious
Tags: ftbfs trixie sid
Justification: nocheck ftfbs is serious since trixie

monero fails to build from source when enabling the nocheck build
profile. Evidently, cmake expects python3, which is tagged  in
debian/control. Please either drop the  annotations or ensure
that the build passes.

Note that this is not an RC bug for bookworm and earlier. There is no
expectation to fix this before the bookworm release though it may still
be included there if the fix is not invasive (e.g. dropping
annotations).  It only becomes RC after bookworm as been released due to
a change in release policy.

Helmut
--- End Message ---
--- Begin Message ---
Source: monero
Source-Version: 0.18.2.2+~0+20200826-1
Done: Bastian Germann 

We believe that the bug you reported is fixed in the latest version of
monero, 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.
Bastian Germann  (supplier of updated monero 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 Jun 2023 12:21:18 +0200
Source: monero
Architecture: source
Version: 0.18.2.2+~0+20200826-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Cryptocoin Team 
Changed-By: Bastian Germann 
Closes: 1032652
Changes:
 monero (0.18.2.2+~0+20200826-1) unstable; urgency=medium
 .
   * New upstream version 0.18.2.2+~0+20200826
   * Install python also for nocheck (Closes: #1032652)
 .
   [ Graham Inggs ]
   * Build with -O1 on riscv64 to avoid link error (LP: #1940505)
Checksums-Sha1:
 3e05aa5fd57ea9f20bf4e98a7d95e434c1eee50b 2803 monero_0.18.2.2+~0+20200826-1.dsc
 597195e37fa2f76f5a30623f8a9d7849b9bf003a 337678 
monero_0.18.2.2+~0+20200826.orig-Xsupercop.tar.gz
 77e9c5813d0af23841e746320c2546b757aab4e9 11640001 
monero_0.18.2.2+~0+20200826.orig.tar.gz
 d8a23a7abf75bde7dc34cb7c874cfeff3a9144c7 22604 
monero_0.18.2.2+~0+20200826-1.debian.tar.xz
 83423d5cc490a5b211763309738f25aac86023b0 14606 
monero_0.18.2.2+~0+20200826-1_source.buildinfo
Checksums-Sha256:
 86bddb207f6406d0d523a498aac1cf07284ac9252aa31f231320d9f6cd7cd909 2803 
monero_0.18.2.2+~0+20200826-1.dsc
 3916443dbcb26e58c5ff975b174b4d17044bd52555663707db9fcc3da41bb837 337678 
monero_0.18.2.2+~0+20200826.orig-Xsupercop.tar.gz
 3877c664d43046811407b92208a9f5c90f62f4b8077014854ebff56909a48b5e 11640001 
monero_0.18.2.2+~0+20200826.orig.tar.gz
 db50cb62044bd709963e62dbbe0e3b247cfc750531e23ee8f22b1945a38a7434 22604 
monero_0.18.2.2+~0+20200826-1.debian.tar.xz
 2932a0548fd99135da98cb8bf4d83c48b25d6bce11227dd11f72cfafb78e2223 14606 
monero_0.18.2.2+~0+20200826-1_source.buildinfo
Files:
 0d28934e74678b8cda5c29c2aa4f27da 2803 utils optional 
monero_0.18.2.2+~0+20200826-1.dsc
 a3d8f46d5638ff39f3fe1068ea9d537a 337678 utils optional 
monero_0.18.2.2+~0+20200826.orig-Xsupercop.tar.gz
 9f4e5afe1f52b2a4b6b3a036e2d3e695 11640001 utils optional 
monero_0.18.2.2+~0+20200826.orig.tar.gz
 e32d7b64604dab6c77930d79dc0b4cfb 22604 utils optional 
monero_0.18.2.2+~0+20200826-1.debian.tar.xz
 e79fbe1c25d4fa2b9a69e97b25bf97d9 14606 utils optional 
monero_0.18.2.2+~0+20200826-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmSIQ7oQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFAUFC/9O5mxwSSvjuNNb6E7x8pnzN3hRvdYE/PZK
GIFEPQyEIBfF+NouaEB4G/kJRW6fR9qU3Ks+28abnx6lc93548h6wxllGvGSCt48
cwoDhiu7SWXR9E9zY1UgItLcw6q6JBkVQTr3hiX///wKQwKoGuLi/bRy2mAdSrik
0JQFZu8lMdXUAv8njr883TOjmzfxyhtepXnB5u4RV3UvfpLeV7BsKl6/fsPx6fTh
FmjNe10cWnQ4EJC8WCCA21/N/mC5baHimes1X8uOcYms/iQE9sooi5wZ3C9ZMg2H
hgXJTzB8GeDeF91R0WmyOrB0UKqo6wkXxUyXd5jS7aST+SpZEB22mBo6ZvMpG8+K
czk/MaujAyAD5/iT5527zHGW5TrsjPVVU3vS85RzNISP

Processed: your mail

[Debian Bug Tracking System]

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

> affects 1031765 obs-advanced-scene-switcher
Bug #1031765 [procps] pgrep: signal handler matching breaks argument parsing
Added indication that 1031765 affects obs-advanced-scene-switcher
>
End of message, stopping processing here.

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

Processed: Bug#1037494 marked as pending in redmine

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1037494 [src:redmine] FTBFS, fails to install on sid due to updated 
nokogiri
Added tag(s) pending.

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

Bug#1037494: marked as pending in redmine

[Jakob Haufe]

Control: tag -1 pending

Hello,

Bug #1037494 in redmine 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/ruby-team/redmine/-/commit/6dad08aa478f4f521b0b18ccb0887c99ad72abd5


Bump nokogiri (Closes: #1037494)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1037494

Processed: add notfound info - this was fixed in node-autoprefixer-rails

[Debian Bug Tracking System]

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

> notfound 998253 14.2.6+ds1-1
Bug #998253 {Done: Pirate Praveen } [gitlab] 
ExecJS::ProgramError: TypeError: Cannot read property 'env' of undefined
There is no source info for the package 'gitlab' at version '14.2.6+ds1-1' with 
architecture ''
Unable to make a source version for version '14.2.6+ds1-1'
No longer marked as found in versions 14.2.6+ds1-1.
> notfound 993964 14.0.10+dfsg-1
Bug #993964 {Done: Pirate Praveen } [gitaly] gitaly 14.0 
fails to start with error panic: failed to open gzip reader: EOF
Ignoring request to alter found versions of bug #993964 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#1037485: Adsense of ovt in Debian 12 iso image

[Winnie Yue]

Package: open-vm-tools
Version: 11.2.5 or higher versions
Severity: Serious

We noticed that there is no open-vm-tools in Debian 12.0 iso image. We’d like 
to learn more about this change, is that by designed? If so, could you please 
tell us more about the reason? Thanks a lot.


Best regards
Winnie Yue

Bug#1036641: marked as done (gcc-12-base: please bump the Breaks: gnat (<< 12) for smoother upgrades from bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 13 Jun 2023 11:19:38 +
with message-id 
and subject line Bug#1036641: fixed in gcc-12 12.3.0-3
has caused the Debian Bug report #1036641,
regarding gcc-12-base: please bump the Breaks: gnat (<< 12) for smoother 
upgrades from 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.)


-- 
1036641: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036641
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gcc-12-base
Version: 12.2.0-14
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

As usual, it is helpful to bump the Breaks against gnat (which is not
co-installable) for smoother upgrades from bullseye to ensure the
obsolete gnat-10 stack gets removed.

Andreas
--- End Message ---
--- Begin Message ---
Source: gcc-12
Source-Version: 12.3.0-3
Done: Matthias Klose 

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated gcc-12 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 Jun 2023 12:57:17 +0200
Source: gcc-12
Architecture: source
Version: 12.3.0-3
Distribution: unstable
Urgency: high
Maintainer: Debian GCC Maintainers 
Changed-By: Matthias Klose 
Closes: 1036641
Changes:
 gcc-12 (12.3.0-3) unstable; urgency=high
 .
   * Update to git 20230613 from the gcc-12 branch.
 - Fix PR middle-end/110200.
   * gcc-12-base: Bump the Breaks: gnat (<< 12) for smoother upgrades from
 bullseye (Andreas Beckmann). Closes: #1036641.
   * Remove obsolete gcn assembler patch.
Checksums-Sha1:
 7e83f42590f0cf29838c7d7c9988b334de1139f5 21854 gcc-12_12.3.0-3.dsc
 77e4135bdb08cf8c865ad2bf3c2e79c1bce3730d 752276 gcc-12_12.3.0-3.debian.tar.xz
 14398f50156a30fe8ecd78f38dde6cc51b260266 8999 gcc-12_12.3.0-3_source.buildinfo
Checksums-Sha256:
 07a3a6d4061c3797712f30676ef1ca732c9c36a9c356a32970f4eafe1467ccbc 21854 
gcc-12_12.3.0-3.dsc
 308a3a827b5686f7819bc116228d52e2a2f37ad1021cde31ba7ea027e20cde12 752276 
gcc-12_12.3.0-3.debian.tar.xz
 68ab817a40d2611425856d6c7cdf0945d670c3924acd680784caa65108802864 8999 
gcc-12_12.3.0-3_source.buildinfo
Files:
 2e9983620d3b770c20b008bed1c83818 21854 devel optional gcc-12_12.3.0-3.dsc
 8a8ba0baf833735bd2d9d4c94ebee9dc 752276 devel optional 
gcc-12_12.3.0-3.debian.tar.xz
 2f1eee2c70462b7d5aa6ed8dc958866f 8999 devel optional 
gcc-12_12.3.0-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAmSIS7sQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9d/mEACltCahTnRy5GVR5XOA7AfSoL/QH8qvBOsb
o94jAI4miHxGXIZcUfETF+bwIsGYZ7CpoLi/nXGuTxt+ULQ9lDrolPq3Bcg/HvFW
E5OjpSOlK97VTHDWTf+BBhoIYrZLTGsWv3uN3toAt1sfTVMXHnM5u9WE8ZMMkHpp
eK0438+ClGkahMdJsVxoGQ+AApBZDdB0SDK+MyNTY12HE5U4rsmaSLyLv9hwmZxR
cj84LxLDUanZ1EJwLuICWphk6E415V/2c9ydQsk5pCFJMlkdhjj67OcP/XLXINPY
1K7c/bB36LtjqtG9aLaiBjdzOWzJx5WHgfI523D4P9lrobPIDV7C0F5a/7BHRmD0
/T/6EtUt9dJzwCSULYALcqX9I1cS2Mwcmo10PejfyaxT6zfYOc+mhgR0BlvhloAv
XCRmSXQ18GCVnpmuKrI65vK7pVbavGvHfL+MUtnXbiiILta5zGH+zhU3Iiog5iBS
+H3UrDV6nK+zZzP20NlO4qyY8Q8Rl2uKeamo/dsUcrVJH3fA5ywmDAlFacC271+A
anHQpK0SFNBFKxJopjow/VjeLGatBu+f9zRE3R6yW/LrndDl2w2ZV3LjVhKsK1D1
3NHghq0mRMlPWKXtGJTIhtRRBtqF+OeAMsOTAv4ii2W9z6UAZ8Z7yfc1rQDPFBy1
4eQ5vNiKyg==
=kM7g
-END PGP SIGNATURE End Message ---

Bug#1037364: nextcloud-desktop: TLS initilization failed

[Hefee]

Control: tags -1 moreinfo
Control: serverity -1 important

Hey,

I never had issues with using Nextcloud desktop to connect to my server, 
that's why I downgrade the serverity, as it has something to do with your 
specific setup.
I expect that the issue is that your server only accepts TLS < 1.3. The last 
years a lot of ciphers are not trusted anymore by default. You can check your 
servers certificate with online tools e.g. https://www.ssllabs.com/ssltest/.

regards,

hefee

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

Processed (with 1 error): Re: Bug#1037364: nextcloud-desktop: TLS initilization failed

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo
Bug #1037364 [nextcloud-desktop] nextcloud-desktop: TLS initilization failed
Added tag(s) moreinfo.
> serverity -1 important
Unknown command or malformed arguments to command.


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

Processed: closing 1033699

[Debian Bug Tracking System]

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

> close 1033699 0~20220915gita545498-4
Bug #1033699 [src:fpga-icestorm] fpga-icestorm: autopkgtest regression: 
icetime: No such file or directory
The source 'fpga-icestorm' and version '0~20220915gita545498-4' do not appear 
to match any binary packages
Marked as fixed in versions fpga-icestorm/0~20220915gita545498-4.
Bug #1033699 [src:fpga-icestorm] fpga-icestorm: autopkgtest regression: 
icetime: No such file or directory
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1034995: marked as done (python-is-python3: missing Breaks+Replaces for python-dev-is-python2 when upgrading from bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 13 Jun 2023 10:37:29 +
with message-id 
and subject line Bug#1034995: fixed in what-is-python 14
has caused the Debian Bug report #1034995,
regarding python-is-python3: missing Breaks+Replaces for python-dev-is-python2 
when upgrading from 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.)


-- 
1034995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034995
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-is-python3
Version: 3.11.1-3
Severity: serious
Justification: dpkg unpack error

Attempting to unpack python-is-python3/3.11.1-3 from Debian bookworm
on a minimal Debian bullseye with python-dev-is-python2/2.7.18-9
installed, causes an unpack error from dpkg due to
/usr/bin/pydoc being contained in both packages.

| Selecting previously unselected package python-is-python3.
| dpkg: considering deconfiguration of python-is-python2, which would be broken 
by installation of python-is-python3 ...
| dpkg: yes, will deconfigure python-is-python2 (broken by python-is-python3)
| (Reading database ... 9300 files and directories currently installed.)
| Preparing to unpack .../python-is-python3_3.11.1-3_all.deb ...
| De-configuring python-is-python2 (2.7.18-9) ...
| Unpacking python-is-python3 (3.11.1-3) ...
| dpkg: error processing archive ./python-is-python3_3.11.1-3_all.deb 
(--unpack):
|  trying to overwrite '/usr/bin/pydoc', which is also in package 
python-dev-is-python2 2.7.18-9
| Errors were encountered while processing:
|  ./python-is-python3_3.11.1-3_all.deb


Please ensure that python-is-python3 has sufficient Breaks and Replaces 
declarations.

Helmut
--- End Message ---
--- Begin Message ---
Source: what-is-python
Source-Version: 14
Done: Matthias Klose 

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated what-is-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: Tue, 13 Jun 2023 12:17:23 +0200
Source: what-is-python
Architecture: source
Version: 14
Distribution: unstable
Urgency: medium
Maintainer: Matthias Klose  
Changed-By: Matthias Klose 
Closes: 1034995
Changes:
 what-is-python (14) unstable; urgency=medium
 .
   * python-is-python3: Add breaks/replaces to python-dev-is-python2.
 Closes: #1034995.
   * Bump standards version.
   * Bump version to 11.4.
Checksums-Sha1:
 7033c1d79e4592888164b554ac08b06115764ee5 1577 what-is-python_14.dsc
 a786724031285a7cde170d90aaff79a170b69859 2560 what-is-python_14.tar.xz
 43d7b261b2f89b61416761cd1bb54bb719db8bd5 6263 
what-is-python_14_source.buildinfo
Checksums-Sha256:
 ab5cc77097ed4e6f47cd94ac17c1611ad7ab03455698a5a4a93393788b0505b3 1577 
what-is-python_14.dsc
 3a8ec3210f726d938a79c52d8c9754a4c5b4e0b315f71fb42f272f845fd33852 2560 
what-is-python_14.tar.xz
 b7f3f50a5c3f9b9e986925f2c62f54661dd50a9428a197311ec335f79190fb09 6263 
what-is-python_14_source.buildinfo
Files:
 d40a2d0afdbb07a8066b1d99895dcf78 1577 python optional what-is-python_14.dsc
 60216e5c4faa214f316f22dbef37c4f9 2560 python optional what-is-python_14.tar.xz
 85ffdf2006fc00d4fe25ef6027f7e4af 6263 python optional 
what-is-python_14_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAmSIQ9oQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9W17D/0Q3bj0a7+0geKWy6Ko3k6Nb7R29MXEucj1
8wob/Gh1stoOiDoF+JuX9CpLBmWpOl36IG7QDGXXLRn/3iyHb7USfsa8zQ9JICpc
3gAh7M8LNjVzOJjmeNbBfL++SiDGHJaE0ENFqhH0FMpwTNBa8WfxHBLsJshWp2Bt
cYVAU0FhJT5pWLFpkcI7scDjeN81cy/Y4cuhqYYeomVWfe10imWsWePJrydeskA/
oJ0d2xZT6D9Kj0Ue4w9kD2+P09hROfrEkFE01Xcv/hOZfu2HBMTlhcXN83QI9GZh
tIl9jpZGXeUdmYZ7kJZ9H2pHgzjypnCesvkJX37hEH2cs/50mfnKr/grFSsZM78y
Q7CRlTk3ndOgixPkHmbqn05RZXJr6gkQ+IyfO0G0u6H0R5fn5rMUBHcIz/LiCghR
a6ik8FMmzyo1lY9vxEBfvDZJwA+XjmzadxwSH3wR7muforLL5rUGRoyBcYhMx2sX
yjf/1DX+0EriLGPYumvEaLwJStad0in7eAAQ72yI9ZJKxIjBREbmXRyEAT6BrG2z
eieb+cljdioPrWx0e3nLR6F8fjzDuFoQWKZIBKJOy1o5lcsMLPTKQw7kHwpRbr7U
h6BU8YHaaNS8qznmCX9lfJcXiLwDJnSq4utO2K7QWJIR+pzpX7MAoBBiLNu4Wn4U
Z+tg9xlnvg=

Bug#1037480: autopkgtest fails with golang-1.20

[Shengjing Zhu]

Source: ycmd
Version: 0+20230103+gitf53e7ac+ds-1
Severity: serious
X-Debbugs-Cc: z...@debian.org

Control: forworded -1 https://github.com/ycm-core/ycmd/commit/01a1f543

I've updated golang-defaults to 1.20 in unstable, your package's autopkgtest
fails with that.

I've sent the fix to upstream, could you backport the commit or package a new
snapshot.

https://github.com/ycm-core/ycmd/commit/01a1f543

-- System Information:
Debian Release: 12.0
  APT prefers testing
  APT policy: (500, 'testing'), (100, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-9-amd64 (SMP w/16 CPU threads; PREEMPT)
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

Processed: fixed 1029731 in 23.1.0~rc2-1

[Debian Bug Tracking System]

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

> # Upstream fix was backported to the 22.3 series and merged into 23.1 -- 
> https://gitlab.freedesktop.org/mesa/mesa/-/commit/c426e5677f36c3b0b8e8ea199ed4f2c7fad06d47
> fixed 1029731 23.1.0~rc2-1
Bug #1029731 {Done: Timo Aaltonen } [libglapi-mesa] 
libglapi-mesa: Apps fail with 'DRM_IOCTL_MODE_CREATE_DUMB failed: Cannot 
allocate memory' after upgrade from 22.3.2-1 to 22.3.3-1
Marked as fixed in versions mesa/23.1.0~rc2-1.
> thanks
Stopping processing here.

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

Bug#1037478: ca-certificates-java: Loop in the execution of the trigger

[Laurent Bigonville]

Package: ca-certificates-java
Version: 20230103
Severity: serious

Hello,

While updating today, I got the following error:

dpkg: boucle détectée durant le traitement des actions différées :
 listes des paquets qui en sont responsables (normalement) :
  ca-certificates-java -> ca-certificates-java
 paquets bloqués par le traitement impossible d'actions différées requises :
  ca-certificates-java: update-ca-certificates-java: /usr/lib/jvm
  libc-bin: ldconfig
  dictionaries-common: aspell-autobuildhash

There seems to be a loop in the trigger execution

Kind regards
Laurent Bigonville


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

Kernel: Linux 6.1.0-9-amd64 (SMP w/8 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: SELinux: enabled - Mode: Permissive - Policy name: refpolicy

Versions of packages ca-certificates-java depends on:
ii  ca-certificates   20230311
ii  openjdk-11-jre-headless [java8-runtime-headless]  11.0.19+7-1

ca-certificates-java recommends no packages.

ca-certificates-java suggests no packages.

-- Configuration Files:
/etc/default/cacerts [Errno 13] Permission non accordée: '/etc/default/cacerts'

-- no debconf information

Bug#1036789: marked as done (libpython3.12-testsuite: fails to install: SyntaxError: Missing parentheses in call to 'print'. Did you mean print(...)?)

[Debian Bug Tracking System]

Your message dated Tue, 13 Jun 2023 09:12:12 +
with message-id 
and subject line Bug#1036789: fixed in python3.12 3.12.0~b2-2
has caused the Debian Bug report #1036789,
regarding libpython3.12-testsuite: fails to install: SyntaxError: Missing 
parentheses in call to 'print'. Did you mean print(...)?
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.)


-- 
1036789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036789
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libpython3.12-testsuite
Version: 3.12.0~b1-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.

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

  Setting up libpython3.12-testsuite (3.12.0~b1-1) ...
File "/usr/lib/python3.12/test/test_lib2to3/data/bom.py", line 2
  print "BOM BOOM!"
  ^
  SyntaxError: Missing parentheses in call to 'print'. Did you mean print(...)?
  dpkg: error processing package libpython3.12-testsuite (--configure):
   installed libpython3.12-testsuite package post-installation script 
subprocess returned error exit status 1
  Processing triggers for libc-bin (2.36-9) ...
  Errors were encountered while processing:
   libpython3.12-testsuite


cheers,

Andreas


libpython3.12-testsuite_3.12.0~b1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: python3.12
Source-Version: 3.12.0~b2-2
Done: Matthias Klose 

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated python3.12 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 Jun 2023 06:48:48 +0200
Source: python3.12
Architecture: source
Version: 3.12.0~b2-2
Distribution: unstable
Urgency: medium
Maintainer: Matthias Klose 
Changed-By: Matthias Klose 
Closes: 1036789
Changes:
 python3.12 (3.12.0~b2-2) unstable; urgency=medium
 .
   * Fix bytecode compilation for python3.12-testsuite. Closes: #1036789.
   * Tighten autopkg test dependencies on python3-tk and python3-gdbm.
Checksums-Sha1:
 5fe882bd9ae3675eadcc07674c1d040a54dbd795 3627 python3.12_3.12.0~b2-2.dsc
 d1e9916fd6110898bb4cbfe4d51cbcb37baccc89 211428 
python3.12_3.12.0~b2-2.debian.tar.xz
 db1b574a4de474cedfd9d5b0ba96ee00eb4f1ef4 8577 
python3.12_3.12.0~b2-2_source.buildinfo
Checksums-Sha256:
 77d7d4465668b58e81c1d9e46f3ab28fdaff9e2cfafc2e0ff1b2c7095a5aefe8 3627 
python3.12_3.12.0~b2-2.dsc
 c40b899f6dcc6da72a77bb74a76b2e40468d96c2adfe2d22f7c8b851f01dfeb7 211428 
python3.12_3.12.0~b2-2.debian.tar.xz
 338f3100e81d8ef1fd422c5d7dbf3cd38096ea46dd7b9223e836df412e7bb546 8577 
python3.12_3.12.0~b2-2_source.buildinfo
Files:
 37413e53a478e6041137d2b20e0c3be8 3627 python optional 
python3.12_3.12.0~b2-2.dsc
 2e8c6ea7799e9df382b36a268ae5ef1d 211428 python optional 
python3.12_3.12.0~b2-2.debian.tar.xz
 b4f587ab02fa571f3f16a09498da63d6 8577 python optional 
python3.12_3.12.0~b2-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAmSIHawQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9U4PD/4rlm5KBsDyd6GGWT0khsCtfblrQUdtu1VL
VdnhjzaSz7wuxEfQMUS0FJQRyQcpfbgGNkgZfMYTK+vM/n+UlLAi8iRKdnEWyHxH
u8Yks0cYMlgnANAnYxK1bt3hcihowz+S9qCh9Blk07Wf9xrAi7TdsumARacjSMPr
7Ik8L5VoJKDdBGw5yzdTDc0P86UJ/CsPrf2YRo0zUc+wEHPTbB665J3RJQA72iEI
jnvZunfKudORpHs4H+jL6bUqCijv+vqK9vna6tB4BbtQkF1HuIBhu530M6pbBkpA
oaqja5nGkmQFxSZ43FlKdg/yZ98kg3tcqI1XQzSCK71DXUtEsj1E3w57rYOQHL/t
EQp/8ZP39UAGg5lOcRUG6msFUtEFU5j39HRj7tvoxKFwqazAUHegx9oecxqAhcKM
C8BRIx4aIkwoNrqlc5T8f3dGDG6mYMP9WT5BkO2tAT+SkgY0QwGGd+LxUzK5uvAp
FsQusjzQHkWy8Tl07LRJLPinqSzq3WCx63H6AC+xeP4rFVCF5+l2oJiCffWnPAnt
cRFZS7q013SNrWNf8GFVPbfvi4MOy24PgnNqt8QZC92s1dSqwimmccRznWMdJ1yC
EGPJgEZIcOWxnkBaAaO3XGlCB29Im0dEynHX4d33DhzYa9E3jAUgPMW5dKlr8CVP
rjHojWKRkg==
=AfBG
-END PGP SIGNATURE End Message ---

Bug#1037472: molmodel: FTBFS with gemmi 0.6.2+ds-1

[Andrius Merkys]

Source: molmodel
Severity: serious
Version: 3.1.0-2

Hello,

molmodel FTBFS after recent update of gemmi to 0.6.2+ds-1:

/home/merkys/molmodel-3.1.0/src/PDBReader.cpp: In function 
'gemmi::Structure getStructureFromFile(const std::string&)':
/home/merkys/molmodel-3.1.0/src/PDBReader.cpp:98:29: error: 
'make_structure_from_block' is not a member of 'gemmi::impl'; did you 
mean 'gemmi::make_structure_from_block'?
   98 | return gemmi::impl::make_structure_from_block ( 
gemmiDoc.blocks.at(0) );

  | ^
In file included from /usr/include/gemmi/mmread.hpp:13,
 from 
/home/merkys/molmodel-3.1.0/./include/molmodel/internal/Compound.h:48,
 from 
/home/merkys/molmodel-3.1.0/./include/molmodel/internal/CompoundSystem.h:6,
 from 
/home/merkys/molmodel-3.1.0/./include/molmodel/internal/PDBReader.h:36,

 from /home/merkys/molmodel-3.1.0/src/PDBReader.cpp:33:
/usr/include/gemmi/mmcif.hpp:15:21: note: 
'gemmi::make_structure_from_block' declared here
   15 | GEMMI_DLL Structure make_structure_from_block(const cif::Block& 
block);

  | ^
make[3]: *** [CMakeFiles/SimTKmolmodel.dir/build.make:219: 
CMakeFiles/SimTKmolmodel.dir/src/PDBReader.cpp.o] Error 1

make[3]: *** Waiting for unfinished jobs
/home/merkys/molmodel-3.1.0/src/Pdb.cpp: In function 'gemmi::Structure 
gemmiStructFromDoc(const gemmi::cif::Document&)':
/home/merkys/molmodel-3.1.0/src/Pdb.cpp:39:25: error: 
'make_structure_from_block' is not a member of 'gemmi::impl'; did you 
mean 'gemmi::make_structure_from_block'?
   39 | return 
gemmi::impl::make_structure_from_block(doc.blocks.front());

  | ^
In file included from /usr/include/gemmi/mmread.hpp:13,
 from 
/home/merkys/molmodel-3.1.0/./include/molmodel/internal/Compound.h:48,
 from 
/home/merkys/molmodel-3.1.0/./include/molmodel/internal/Pdb.h:6,

 from /home/merkys/molmodel-3.1.0/src/Pdb.cpp:4:
/usr/include/gemmi/mmcif.hpp:15:21: note: 
'gemmi::make_structure_from_block' declared here
   15 | GEMMI_DLL Structure make_structure_from_block(const cif::Block& 
block);

  | ^

The issue is better fixed upstream, I will forward the report. In the 
meantime it is OK to remove molmodel from testing to not obstruct the 
upcoming openmm transition.


Andrius

Bug#1036641: marked as done (gcc-12-base: please bump the Breaks: gnat (<< 12) for smoother upgrades from bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 13 Jun 2023 07:37:38 +
with message-id 
and subject line Bug#1036641: fixed in gcc-12 12.3.0-3~exp1
has caused the Debian Bug report #1036641,
regarding gcc-12-base: please bump the Breaks: gnat (<< 12) for smoother 
upgrades from 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.)


-- 
1036641: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036641
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gcc-12-base
Version: 12.2.0-14
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

As usual, it is helpful to bump the Breaks against gnat (which is not
co-installable) for smoother upgrades from bullseye to ensure the
obsolete gnat-10 stack gets removed.

Andreas
--- End Message ---
--- Begin Message ---
Source: gcc-12
Source-Version: 12.3.0-3~exp1
Done: Matthias Klose 

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated gcc-12 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 Jun 2023 09:08:08 +0200
Source: gcc-12
Architecture: source
Version: 12.3.0-3~exp1
Distribution: experimental
Urgency: high
Maintainer: Debian GCC Maintainers 
Changed-By: Matthias Klose 
Closes: 1036641
Changes:
 gcc-12 (12.3.0-3~exp1) experimental; urgency=high
 .
   * Update to git 20230613 from the gcc-12 branch.
 - Fix PR middle-end/110200.
   * gcc-12-base: Bump the Breaks: gnat (<< 12) for smoother upgrades from
 bullseye (Andreas Beckmann). Closes: #1036641.
   * Remove obsolete gcn assembler patch.
Checksums-Sha1:
 e83536622ff5093dda32a614d240f3492d095352 21874 gcc-12_12.3.0-3~exp1.dsc
 e0daa03b91762a300ebc913fdcf56f4655e751d4 752212 
gcc-12_12.3.0-3~exp1.debian.tar.xz
 d6b63e4f82bbee5cafe3736039dcb4aa28de9297 8983 
gcc-12_12.3.0-3~exp1_source.buildinfo
Checksums-Sha256:
 cafcc8736e9bb5713d99e82f9d760ad689d391a622bf02b2c9d1ce396f3bb483 21874 
gcc-12_12.3.0-3~exp1.dsc
 2feca9bdfa3f9c4fad65751ebdadd9634c534071750c41a73877e29127a6e13d 752212 
gcc-12_12.3.0-3~exp1.debian.tar.xz
 27d4bdcfc8fcb08f443a30b214796225ee95c5313e2f2b440ebe066f4986d4a1 8983 
gcc-12_12.3.0-3~exp1_source.buildinfo
Files:
 e7120b88e6d5eec89ced40f5e1a90f4c 21874 devel optional gcc-12_12.3.0-3~exp1.dsc
 6d7bc8725315f1064700d2eb2bfa6a7a 752212 devel optional 
gcc-12_12.3.0-3~exp1.debian.tar.xz
 ef0e6000a0e77a0e4cb20100bb678b01 8983 devel optional 
gcc-12_12.3.0-3~exp1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAmSIF0wQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9aCaEAC/wXOzSdAxzR5Ci+5nlYBbsaOIKCuWCX/k
NZsltCt9N+RIVQun1a5ZyAULKLYrHA97iCAI6IxGhV3aDGNpBggPN8m9cN+iumQz
ILbuPaiiEUc4LZUmh1+9OafVdZ29MDWYPppv8QqICieMsR67if0PCu5ln8zdIRVn
RdMPg4P9wFJyrhBwh/rB4b7baM9FMNJlJa38Fi+tCrhLyyC8bXgJwzQVQpmJVO8X
POSGoLgsyb3xt9j/C2qX2CulSAJWH9PMgS1z42DfZzn2TsAiGhNdpZBGukWk1FmB
/gJB10UOuqlFyAOXsEyixrCIWCzPHjFToBDRHCGlYHBbDv3Vgo+q4/L79SZIsCGz
JiX3+PBtGokvpOcEHMBUk2Oxld8tJvinximeuRLSxJb3/+lS4E+YT8yuDjNei420
hafa2UvE6j9fQ2yXJa07cSyy3Fz8HqPM4jjaQHiy4RBha1CmIGjWZxQ5LZqDUDg4
fqducJqsYxNDLjpcpz+Jus2Q7FVU4QUDOVHkNVKgBCwv22LmriL/y+cEmahSN9QQ
vwcj2FBrfEiLAxH44lQAg/cKejHrd8WbdE2nLqlRe02lquc58A8xQIenj55vZudQ
3Ec0rJ6vPdQW0+MNaABy4J9yfItmAmewEOq7UdXCj8mZGc3cLhA6wn94fn4QrFdq
NXfFGrD2gw==
=1img
-END PGP SIGNATURE End Message ---

Processed: found 1034433 in 3~git20230601+dfsg-1

[Debian Bug Tracking System]

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

> found 1034433 3~git20230601+dfsg-1
Bug #1034433 [libsdl3-doc] libsdl3-doc: missing Breaks+Replaces: libsdl1.2-dev 
(<< 3)
Ignoring request to alter found versions of bug #1034433 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#1037463: macromoleculebuilder: FTBFS with gemmi 0.6.2+ds-1

[Andrius Merkys]

Source: macromoleculebuilder
Severity: serious
Version: 4.0.0+dfsg-2

Hello,

macromoleculebuilder FTBFS after recent update of gemmi to 0.6.2+ds-1:

/home/merkys/macromoleculebuilder-4.0.0+dfsg/src/CifOutput.cpp: In 
function 'void SimTK::CIFOut::reWriteOutCif(const gemmi::Model&, const 
std::string&, const std::string&, ParameterReader&, const 
SimTK::CompoundSystem&, bool)':
/home/merkys/macromoleculebuilder-4.0.0+dfsg/src/CifOutput.cpp:113:81: 
error: cannot bind rvalue reference of type 'gemmi::cif::Document&&' to 
lvalue of type 'gemmi::cif::Document'
  113 | gemmi::Structure myTrajectoryOutputFile   = 
gemmi::make_structure ( doc );
  | 
^~~


The issue is better fixed upstream, I will forward the report. In the 
meantime it is OK to remove macromoleculebuilder from testing to not 
obstruct the upcoming openmm transition.


Andrius