Processed: Re: [Pkg-javascript-devel] Bug#1054167: ftbfs: AssertionError in tests

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #1054167 [src:node-grunt-legacy-log] ftbfs: AssertionError in tests
Severity set to 'important' from 'serious'

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

Bug#1054167: [Pkg-javascript-devel] Bug#1054167: ftbfs: AssertionError in tests

[Yadd]

Control: severity -1 important

Hi,

not really a serious-bug since it exists only when using a color term. 
Fixed anyway in version 2.0.0-4


Cheers,
Yadd

Bug#1054167: marked as pending in node-grunt-legacy-log

[Yadd]

Control: tag -1 pending

Hello,

Bug #1054167 in node-grunt-legacy-log 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/js-team/node-grunt-legacy-log/-/commit/a99a6dcef30cdff218135b42f672c34f3bd7c768


Disable colors during test

Closes: #1054167


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1054167

Processed: Bug#1054167 marked as pending in node-grunt-legacy-log

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1054167 [src:node-grunt-legacy-log] ftbfs: AssertionError in tests
Added tag(s) pending.

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

Bug#1054261: tint2 coredumps on startup

[Phil Dibowitz]

Package: tint2
Version: 17.0.1-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

tint2 crashes reliably on startup with this:

```
$ tint2
tint2: Using glib slice allocator (default). Run tint2 with environment 
variable G_SLICE=always-malloc in case of strange behavior or crashes
tint2: xRandr: Found crtc's: 6
tint2: xRandr: Linking output DisplayPort-1 with crtc 0, resolution 1920x1080, 
DPI 102
tint2: xRandr: Linking output HDMI-A-0 with crtc 1, resolution 1920x1080, DPI 
102
tint2: xRandr: crtc 2 seems disabled
tint2: xRandr: crtc 3 seems disabled
tint2: xRandr: crtc 4 seems disabled
tint2: xRandr: crtc 5 seems disabled
tint2: No XSETTINGS manager, tint2 uses config option 'launcher_icon_theme'.
tint2: Loading config file: /home/phil/.config/tint2/tint2rc
tint2: real transparency off depth: 24
tint2: panel items: TSC
tint2: Systray composited rendering off
tint2: systray_asb forced to 100 0 0
tint2: nb monitors 2, nb monitors used 2, nb desktops 4
tint2: panel 1 uses scale 1 
tint2: panel 2 uses scale 1 
tint2: Kernel uevent interface initialized...
tint2: systray window 27263052
tint2: systray started add_icon: 46137383 (), pid 24844, visual 0x55fcc6f9e1c0, 
colormap 46137384, depth 32, width 22, height 22
tint2: Couldn't get geometry of window! systray 823: cannot embed icon for 
window 46137383 () parent 27263080 pid 24844
tint2: remove_icon: 46137383 () Segmentation fault (core dumped) 
```

Despite what the message says, even if you define G_SLICE=always-malloc,
it still prints that message:

```
[phil@rider ~]$ export G_SLICE=always-malloc
[phil@rider ~]$ tint2
tint2: Using glib slice allocator (default). Run tint2 with environment 
variable G_SLICE=always-malloc in case of strange behavior or crashes
tint2: xRandr: Found crtc's: 6
```

The internet believes it's due to newer glibc2: 
https://bbs.archlinux.org/viewtopic.php?id=284293

I'm using openbox.



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

Kernel: Linux 6.5.0-1-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (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 tint2 depends on:
ii  libc6 2.37-12
ii  libcairo2 1.18.0-1
ii  libgdk-pixbuf-2.0-0   2.42.10+dfsg-1+b1
ii  libglib2.0-0  2.78.0-2
ii  libgtk-3-03.24.38-5
ii  libimlib2 1.12.1-1
ii  libpango-1.0-01.51.0+ds-2
ii  libpangocairo-1.0-0   1.51.0+ds-2
ii  librsvg2-22.54.7+dfsg-2
ii  libstartup-notification0  0.12-6+b1
ii  libx11-6  2:1.8.7-1
ii  libxcomposite11:0.4.5-1
ii  libxdamage1   1:1.1.6-1
ii  libxext6  2:1.3.4-1+b1
ii  libxinerama1  2:1.1.4-3
ii  libxrandr22:1.5.2-2+b1
ii  libxrender1   1:0.9.10-1.1

tint2 recommends no packages.

tint2 suggests no packages.

-- no debconf information

Processed: forcibly merging 1050431 1052751

[Debian Bug Tracking System]

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

> forcemerge 1050431 1052751
Bug #1050431 [src:binutils-mipsen] binutils-mipsen: FTBFS on all architectures
Bug #1052751 [src:binutils-mipsen] binutils-mipsen: FTBFS: ld: 
mips.o:(.data.rel.ro+0x740): undefined reference to 
`gold::Output_data_reloc_base<9, true, 32, 
true>::do_adjust_output_section(gold::Output_section*)'
1052345 was blocked by: 1050431
1052345 was not blocking any bugs.
Added blocking bug(s) of 1052345: 1052751
1040626 was blocked by: 1050431
1040626 was not blocking any bugs.
Added blocking bug(s) of 1040626: 1052751
1052751 was not blocked by any bugs.
1052751 was blocking: 1040626 1052345
Added blocking bug(s) of 1052751: 1049455
The source binutils-mipsen and version 10+c5 do not appear to match any binary 
packages
Marked as found in versions binutils-mipsen/10+c4.
Bug #1050431 [src:binutils-mipsen] binutils-mipsen: FTBFS on all architectures
The source binutils-mipsen and version 10+c5 do not appear to match any binary 
packages
Marked as found in versions binutils-mipsen/10+c5.
Added tag(s) trixie and sid.
Merged 1050431 1052751
> thanks
Stopping processing here.

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

Bug#1054256: ruby-blade: uninstallable in unstable (ruby-blade : Depends: ruby-thin (>= 1.6.0) but it is not installable)

[Antonio Terceiro]

Package: ruby-blade
Version: 0.7.1-4
Severity: serious
Justification: uninstallable

After the last upload, ruby-blade ended up with a dependency on
ruby-thin, which does not exist.

8<8<8<-
$ LANG=C sudo apt install ruby-blade/unstable
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Selected version '0.7.1-4' (Debian:unstable [all]) for 'ruby-blade'
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 ruby-blade : Depends: ruby-thin (>= 1.6.0) but it is not installable
E: Unable to correct problems, you have held broken packages.
8<8<8<-

The correct dependency would be on `thin`.

This is actually caused by a bug in gem2deb (unreported), which was not
finding the correct mapping between gem names and Debian package names
for architecture dependent packages. In any case, ruby-blade will need a
no changes upload to be rebuilt once gem2deb 2.2, just uploaded, is
available.

See 
https://salsa.debian.org/ruby-team/gem2deb/-/commit/827cb954c941872e24bb8f489d1a54cba416694b
for more details.

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (900, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: arm64 (aarch64)

Kernel: Linux 6.5.0-1-arm64 (SMP w/32 CPU threads)
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.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 ruby-blade depends on:
ii  ruby  1:3.1
ii  ruby-activesupport2:6.1.7.3+dfsg-2
ii  ruby-blade-qunit-adapter  2.0.1-2
ii  ruby-curses   1.4.4-1+b2
ii  ruby-eventmachine 1.3~pre20220315-df4ab006-3+b1
ii  ruby-faye 1.4.0-1
ii  ruby-sprockets3.7.2-4
pn  ruby-thin 
ii  ruby-thor 1.2.2-1
ii  ruby-useragent0.16.8-1.1
ii  thin  1.8.1-2

ruby-blade recommends no packages.

ruby-blade suggests no packages.


signature.asc
Description: PGP signature

Bug#1054237: marked as done (jdupes: data loss behaviour from fdupes)

[Debian Bug Tracking System]

Your message dated Thu, 19 Oct 2023 20:49:31 +
with message-id 
and subject line Bug#1054237: fixed in jdupes 1.27.3-4
has caused the Debian Bug report #1054237,
regarding jdupes: data loss behaviour from fdupes
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.)


-- 
1054237: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054237
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jdupes
Version: 1.12-1
Severity: grave
Tags: upstream patch
Justification: causes non-serious data loss

>From the upstream in a private message:

jdupes inherited interactive deletion from fdupes and there were zero
input safeguards. A user tried to use ranges "2-4" and files 3 and 4 were
deleted, not preserved. This is a major data loss concern because the
behavior is destructive and contrary to user expectations. In the latest
commit I've placed heavy safeguards in the interactive deletion code that
should prevent all of the invalid input scenarios I can conceive.

The commit 4888e85[1] can and should be immediately applied to ALL
versions of jdupes that are being distributed. It should cleanly apply
and work without modification to every remotely recent version spanning
several years back.

[1] https://codeberg.org/jbruchon/jdupes/commit/4888e85
--- End Message ---
--- Begin Message ---
Source: jdupes
Source-Version: 1.27.3-4
Done: Joao Eriberto Mota Filho 

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

Debian distribution maintenance software
pp.
Joao Eriberto Mota Filho  (supplier of updated jdupes 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 19 Oct 2023 13:40:10 -0300
Source: jdupes
Architecture: source
Version: 1.27.3-4
Distribution: unstable
Urgency: medium
Maintainer: Joao Eriberto Mota Filho 
Changed-By: Joao Eriberto Mota Filho 
Closes: 1054237
Changes:
 jdupes (1.27.3-4) unstable; urgency=medium
 .
   * debian/patches/020_fix-data-loss.patch: created to avoid a potential data
 loss caused by a wrong message that induces the users to use a range of
 values with -d option. Currently, the -d option doesn't understand ranges.
 (Closes: #1054237)
Checksums-Sha1:
 264740eaef8a988cb220f3ab26bb82f17bec0502 1907 jdupes_1.27.3-4.dsc
 071ff93f81e63bd6e64681eff1a3e328113e7083 15312 jdupes_1.27.3-4.debian.tar.xz
 dd8d4ce6b3ada2f889888c40d94291893b624b3c 6090 jdupes_1.27.3-4_source.buildinfo
Checksums-Sha256:
 a9baa90d82c10d37702bb2765c39f25c9283b5cc01c2152f811622ac71ce9cf2 1907 
jdupes_1.27.3-4.dsc
 97d1cdcde0c95d27a1bb9f121911e52c89ea6a9ac7743be2ef6fdc452fce1646 15312 
jdupes_1.27.3-4.debian.tar.xz
 60c71b2b3bf6d1d8036b759456f02204288c8caf4b61de5f28e27ae0c0a287e5 6090 
jdupes_1.27.3-4_source.buildinfo
Files:
 40c0e90834276069b947a11b3d73471a 1907 utils optional jdupes_1.27.3-4.dsc
 642c1273bdeed15c3eb33ec674ebd335 15312 utils optional 
jdupes_1.27.3-4.debian.tar.xz
 cd586755c3574a7c1ecc24887534785d 6090 utils optional 
jdupes_1.27.3-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAmUxj/MACgkQ3mO5xwTr
6e8t2w//XBTSrNLRwDcCZmeKj2Gjw5i10HqL/bzAkB9Nhw+HoazbTrvKCo+hL/Tv
vuhtbmpcnHnHEXbmMZRKi87GlPvdsddmreyVJbGRiZrUJIBtTShdbtGokuphqMSU
49KhNATj0FLaBMzhAaRDYzjzCVoZbNoJEQMDdB/pTb2oenQoSlqkmpLhePBvUlBT
RM+PAwjs1oyjj8Mjs5IKTtxLqid+bgL/eniFbZhSuVXCHWWT2p/mnh8ifA17gSwN
lJFzAyTLpjsA9I097Dg5MC62KGichXCYbzdr4X1W9FVR+WkcWm2M2/zQeIh6sK1/
SqQ+0jGvSnpfek7tSAjIWpE1APzetUy81NnxlquxhvZXqUOCS1Q1XTMxB1XNl3YW
p3Q4JYeW8iqKpuxb9n7AipSWE9VgyHuBRwKQKBlrwiuQCtNfvrSegtX4HY/cyqC5
yEHGcq6HnF/5liamMton/GtjBmzHqFa2Wy4JNgd8p4qadRZzrRoO2Byex/4BQx1+
LxB62eHCK7EwEKAOSYg28sowDEgo60Vo5N4u6ypYeDJnEnh6BH39UUxUDKqHoGdj
lE1lPlLV4GOTLDbPx9F5SszqDYnju0JyX1ayvy8PNkxSZ2GBP++TmOfty84KpeAU
qkWk+LSH5Zt8w3fZSn6JCPBldAmLhTvlP8GRg/1LkL0CeTkwdnE=
=361m
-END PGP SIGNATURE End Message ---

Processed: bug 1004706 is forwarded to https://github.com/pavlin-policar/openTSNE/issues/247

[Debian Bug Tracking System]

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

> forwarded 1004706 https://github.com/pavlin-policar/openTSNE/issues/247
Bug #1004706 [src:opentsne] opentsne: FTBFS on i386, test failure
Set Bug forwarded-to-address to 
'https://github.com/pavlin-policar/openTSNE/issues/247'.
> thanks
Stopping processing here.

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

Bug#1054253: icu FTBFS with gcc 13 on i386

[Adrian Bunk]

Source: icu
Version: 72.1-3
Severity: serious
Tags: ftbfs patch trixie sid experimental

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/icu.html

...
-
| *** FAILING TEST SUMMARY FOR:  intltest  
 TestFixedDecimal
  IntlTestDecimalFormatAPI
 TestCurrencyFormatForMixParsing
  NumberFormatTest
 Test4118594
  MessageFormatRegressionTest
 Test4243108
  NumberFormatRegressionTest
roundingIncrementRegressionTest
 NumberFormatterApiTest
  NumberTest
   format
| *** END FAILING TEST SUMMARY FOR:  intltest
---
ALL TESTS SUMMARY:
ok:  testdata iotest cintltst
= ERRS:  intltest
make[3]: *** [Makefile:91: check-recursive] Error 1
...


Fix:

--- debian/rules.old2023-10-19 19:46:14.664980859 +
+++ debian/rules2023-10-19 19:46:34.536970355 +
@@ -16,6 +16,8 @@
 export DEB_CPPFLAGS_MAINT_APPEND = 
-DU_TIMEZONE_FILES_DIR=/usr/share/zoneinfo-icu/44/be/
 endif
 
+export DEB_CXXFLAGS_MAINT_APPEND += -fexcess-precision=fast
+
 include /usr/share/dpkg/buildflags.mk
 
 l_SONAME=70

Bug#1054252: g2o: binary-all FTBFS

[Adrian Bunk]

Source: g2o
Version: 0~20230806-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=g2o=all=0~20230806-2=1696411342=0

...
The following tests FAILED:
  1 - unittest_general (Not Run)
  2 - unittest_data (Not Run)
  3 - unittest_stuff (Not Run)
  4 - unittest_sclam2d (Not Run)
  5 - unittest_slam2d (Not Run)
  6 - unittest_slam2d_addons (Not Run)
  7 - unittest_slam3d (Not Run)
  8 - unittest_slam3d_addons (Not Run)
  9 - unittest_sim3 (Not Run)
 10 - unittest_sba (Not Run)
 11 - unittest_solver (Not Run)
Errors while running CTest
make[1]: *** [Makefile:94: test] Error 8

Bug#1053825: Screensaver with only blank does not work after suspend

[Salvatore Bonaccorso]

Hi,

On Thu, Oct 12, 2023 at 06:57:20AM +0100, Klaus Ethgen wrote:
> Package: src:linux
> Version: 6.5.6-1
> Severity: critical
> Tags: security
> X-Debbugs-Cc: Debian Security Team 
> 
> It is not fully clear for me, where exactly this bug happens. First I
> was thinking about xscreensaver but that package got not updated for
> ages. The bug happens with updates from kernel 6.4.0 to 6.5.0.

So you are saying this happens solely after switching from 6.4.y
series to 6.5.y series. Thus I assume 6.5.3-1 in testing as well
exposes the issue.

> I use xscreensaver with fvwm3 on my amd laptop. xscreensaver is set up
> to only blank the screen.
> 
> When I lock the screen and press a key or moving the mouse, everything
> is fine. But when I go to suspend too ram after locking and waking up
> the laptop, the password dialog gets showed as usual but I can see the
> full desktop content with probably sensitive material on in. Although, I
> cannot interact with the desktop, it is a security break to reveal the
> content without authenticating.
> 
> It might be related, when I have a PSI chat window on the screen but on
> different desktop, it gets moved to the current one. That definitively
> also came with the new kernel.

Can you please attach as well the kernel log once you triggered the
behaviour? Anything suspicious logged? 

Next, can you bisect the kernel between a good known upstream version
and 6.5.6? Can you as well test 6.5.7 upstream to see if it fixes the
issue?

Currently there is nothing which sound similar in the kernel
regression tracking status, TTBOMK.

Regards,
Salvatore

Processed: found 1053825 in 6.5.3-1, tagging 1053825, severity of 1053825 is serious

[Debian Bug Tracking System]

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

> # according to reporter after switching from 6.4.y to 6.5.y
> found 1053825 6.5.3-1
Bug #1053825 [src:linux] Screensaver with only blank does not work after suspend
Marked as found in versions linux/6.5.3-1.
> tags 1053825 + moreinfo
Bug #1053825 [src:linux] Screensaver with only blank does not work after suspend
Added tag(s) moreinfo.
> # keep it RC for now
> severity 1053825 serious
Bug #1053825 [src:linux] Screensaver with only blank does not work after suspend
Severity set to 'serious' from 'critical'
> thanks
Stopping processing here.

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

Bug#1054249: python3-certbot-dns-gandi: Break with API key deprecation

[doriancoding]

Package: python3-certbot-dns-gandi
Version: 1.4.3-1
Severity: grave
Tags: newcomer
Justification: renders package unusable
X-Debbugs-Cc: dorian.le...@icloud.com

Dear Maintainer,

Due to recent changes in Gandi LiveDNS, api key are deprecated and the script 
cannot work anymore with new keys.

The solution is developed on the Github to solve this issue.

As of today, anyone using new keys cannot use the script.

Thank you.

-- System Information:
Distributor ID: Raspbian
Description:Raspbian GNU/Linux trixie/sid
Release:n/a
Codename:   trixie
Architecture: armv7l

Kernel: Linux 6.1.21-v7+ (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages python3-certbot-dns-gandi depends on:
ii  certbot  2.1.0-4
ii  python3  3.11.4-5
ii  python3-certbot [python3-certbot-abi-2]  2.1.0-4
ii  python3-requests 2.31.0+dfsg-1

python3-certbot-dns-gandi recommends no packages.

python3-certbot-dns-gandi suggests no packages.

-- no debconf information

Bug#1052889: closing 1052889

[Debian/GNU]

close 1052889 
thanks

this is fixed in faust_2.68.1+ds-2.

the fixed version was upload to unstable on the very day this bug (which is
really a duplicate of #1051880) was reported (that's why i missed this bug for a
while).

cheers

Bug#1054241: nastran: Demonstration problems fail.

[Chris Fisichella]

Package: nastran
Version: 0.1.95-2
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: ch...@communityrenewables.com

Dear Maintainer,

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

   * What led up to the situation?
   I installed nastran from the debian distribution. 
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 I read the man page. I made a copy of the examples that come with the 
distribution to my home directory. I downloaded the NASTRAN demonstration 
problem manual and read it over. I sucessively copied about ten demonstration 
problems to another directory in my home directory and on each .inp file, 
executed nastran .inp, where  is the example file name that came with 
the distribution.
   * What was the outcome of this action?
   Nastran ran successfully. Nastran found errors on its own and reported them. 
A popular error was
   0*** USER FATAL MESSAGE 8020, SYNTAX ERROR NEAR COLUMN  16 IN THE FOLLOWING 
CARD- 
SBST   1,  3

01 2 3 4 5 
6 7 8
10 0 0 0 0 
0 0 0
this error can be found in the .out file NASTRAN creates. 
   * What outcome did you expect instead?
   I expected the example problems to run successfully. The are used to test 
the system NASTRAN is running on against published known results. 

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


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

Kernel: Linux 5.10.0-18-amd64 (SMP w/2 CPU threads)
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 nastran depends on:
ii  libc6 2.31-13+deb11u4
ii  libgcc-s1 10.2.1-6
ii  libgfortran5  10.2.1-6

nastran recommends no packages.

nastran suggests no packages.

-- no debconf information

Processed: closing 1052889

[Debian Bug Tracking System]

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

> close 1052889
Bug #1052889 [src:faust] faust: FTBFS: make[7]: *** No rule to make target 
'__tmp_llvm_lib__/libPolly.dir', needed by 'lib/libfaustwithllvm.a'.  Stop.
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: Re: Bug#1051980: FTBFS on i386: angle-test/bezier-test fail

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://gitlab.com/inkscape/lib2geom/-/issues/67
Bug #1051980 [src:lib2geom] FTBFS on i386: angle-test/bezier-test fail
Set Bug forwarded-to-address to 
'https://gitlab.com/inkscape/lib2geom/-/issues/67'.

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

Bug#1051980: FTBFS on i386: angle-test/bezier-test fail

[Adrian Bunk]

Control: forwarded -1 https://gitlab.com/inkscape/lib2geom/-/issues/67

On Sat, Sep 16, 2023 at 03:21:21PM +0800, Shengjing Zhu wrote:
> Control: tag -1 + patch
> 
> Hi,
> 
> On Fri, Sep 15, 2023 at 4:27 PM Shengjing Zhu  wrote:
> > The following tests FAILED:
> >   2 - angle-test (Failed)
> >   3 - bezier-test (Failed)
> 
> They are caused by gcc-13 which defaults to -fexcess-precision=standard for 
> c++.
> 
> Please see the attached patch.

That solves only part of the problem for experimental, adding
  export DEB_CXXFLAGS_MAINT_APPEND += -ffloat-store -fexcess-precision=fast
to debian/rules is the easiest fix to get all tests passing in both 
unstable and experimental.

> Shengjing Zhu

cu
Adrian

Processed: [bts-link] source package src:ezquake

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:ezquake
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #135 (http://bugs.debian.org/135)
> # Bug title: ezquake: depends on obsolete pcre3 library
> #  * https://github.com/QW-Group/ezquake-source/issues/815
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 135 + fixed-upstream
Bug #135 [src:ezquake] ezquake: depends on obsolete pcre3 library
Added tag(s) fixed-upstream.
> usertags 135 - status-open
Usertags were: status-open.
There are now no usertags set.
> usertags 135 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#1054239: libixion FTBFS with gcc 13 on i386

[Adrian Bunk]

Source: libixion
Version: 0.17.0-3
Severity: serious
Tags: ftbfs trixie sid patch

https://buildd.debian.org/status/fetch.php?pkg=libixion=i386=0.19.0-1=1697292545=0

...
FAIL: document-test
===

test_basic_calc: --begin
document-test: document_test.cpp:50: void test_basic_calc(): Assertion 
`doc.get_numeric_value(A1) == 1.1' failed.
FAIL document-test (exit status: 134)

FAIL: general-test
==

test_size: --begin
test size
* int: 4
* long: 4
* double: 8
* size_t: 4
* string_id_t: 4 (min:0; max:4294967295)
* celltype_t: 1
* formula_cell: 4
* formula_tokens_t: 12
test_size: --end (duration: 0 sec)
test_string_to_double: --begin
test_string_to_double: --end (duration: 0 sec)
test_string_pool: --begin
string count: 4
* 0: 'Table1' (0x57251a98)
* 1: 'Table2' (0x57251ab0)
* 2: 'Category' (0x57251ac8)
* 3: 'Value' (0x57251ae0)
string map count: 4
* key: 'Value' (0x57251ae0; 5), value: 3
* key: 'Category' (0x57251ac8; 8), value: 2
* key: 'Table2' (0x57251ab0; 6), value: 1
* key: 'Table1' (0x57251a98; 6), value: 0
test_string_pool: --end (duration: 0 sec)
test_formula_tokens_store: --begin
test_formula_tokens_store: --end (duration: 0 sec)
test_matrix: --begin
test_matrix: --end (duration: 0 sec)
test_matrix_non_numeric_values: --begin
general-test: general_test.cpp:166: void 
{anonymous}::test_matrix_non_numeric_values(): Assertion `mtx.get_numeric(0, 0) 
== 1.1' failed.
FAIL general-test (exit status: 134)


Testsuite summary for libixion 0.19.0

# TOTAL: 6
# PASS:  4
# SKIP:  0
# XFAIL: 0
# FAIL:  2
# XPASS: 0
# ERROR: 0

See src/libixion/test-suite.log

make[6]: *** [Makefile:1101: test-suite.log] Error 1



There are two ways to fix this:


--- debian/rules.old2023-10-19 17:03:33.109096000 +
+++ debian/rules2023-10-19 17:03:52.569079353 +
@@ -5,6 +5,8 @@
 
 include /usr/share/dpkg/architecture.mk
 
+export DEB_CXXFLAGS_MAINT_APPEND += -fexcess-precision=fast
+
 %:
dh $@
 


OR


--- configure.ac.old2023-10-19 17:04:03.837069635 +
+++ configure.ac2023-10-19 17:04:13.189061522 +
@@ -19,7 +19,7 @@
 AC_CONFIG_HEADERS([config.h])
 AM_INIT_AUTOMAKE([1.11 foreign dist-bzip2 dist-xz])
 m4_ifdef([AM_SILENT_RULES], [AM_SILENT_RULES([yes])])
-AX_CXX_COMPILE_STDCXX_17([noext], [mandatory])
+AX_CXX_COMPILE_STDCXX_17([ext], [mandatory])
 CXXFLAGS="$CXXFLAGS -fvisibility=hidden -Wall -Wshadow -Wno-write-strings 
-pthread"
 
 AC_CANONICAL_HOST

Processed: Control tag

[Debian Bug Tracking System]

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

> tags 1054197 - bookworm
Bug #1054197 [src:hcloud-cli] hcloud-cli FTBFS: cannot use cert.ID (variable of 
type int64) as int value in argument to strconv.Itoa
Removed tag(s) bookworm.
> tags 1054197 trixie
Bug #1054197 [src:hcloud-cli] hcloud-cli FTBFS: cannot use cert.ID (variable of 
type int64) as int value in argument to strconv.Itoa
Added tag(s) trixie.
> thanks
Stopping processing here.

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

Bug#1054237: jdupes: data loss behaviour from fdupes

[Joao Eriberto Mota Filho]

Package: jdupes
Version: 1.12-1
Severity: grave
Tags: upstream patch
Justification: causes non-serious data loss

>From the upstream in a private message:

jdupes inherited interactive deletion from fdupes and there were zero
input safeguards. A user tried to use ranges "2-4" and files 3 and 4 were
deleted, not preserved. This is a major data loss concern because the
behavior is destructive and contrary to user expectations. In the latest
commit I've placed heavy safeguards in the interactive deletion code that
should prevent all of the invalid input scenarios I can conceive.

The commit 4888e85[1] can and should be immediately applied to ALL
versions of jdupes that are being distributed. It should cleanly apply
and work without modification to every remotely recent version spanning
several years back.

[1] https://codeberg.org/jbruchon/jdupes/commit/4888e85

Processed: ortp: FTBFS: b64.h:293: error: unable to resolve link to 'b64::b64_encode2' for \link command (warning treated as error, aborting now)

[Debian Bug Tracking System]

Processing control commands:

> close -1 1:5.2.98-1
Bug #1052747 [src:ortp] ortp: FTBFS: b64.h:293: error: unable to resolve link 
to 'b64::b64_encode2' for \link command (warning treated as error, aborting now)
Marked as fixed in versions ortp/1:5.2.98-1.
Bug #1052747 [src:ortp] ortp: FTBFS: b64.h:293: error: unable to resolve link 
to 'b64::b64_encode2' for \link command (warning treated as error, aborting now)
Marked Bug as done

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

Bug#1052747: ortp: FTBFS: b64.h:293: error: unable to resolve link to 'b64::b64_encode2' for \link command (warning treated as error, aborting now)

[Dennis Filder]

Control: close -1 1:5.2.98-1
X-Debbugs-Cc: lu...@debian.org

I'm closing this as this was fixed with 1:5.2.98-1 in experimental.

Reopen at will.

Regards.

Bug#1053310: closed by Debian FTP Masters (reply to Andreas Metzler ) (Bug#1053310: fixed in exim4 4.97~RC2-2)

[Salvatore Bonaccorso]

On Mon, Oct 16, 2023 at 04:51:03PM +, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the exim4-base package:
> 
> #1053310: exim4-base: Various severe CVE reports are outstanding
> 
> It has been closed by Debian FTP Masters  
> (reply to Andreas Metzler ).
> 
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Debian FTP Masters 
>  (reply to Andreas Metzler 
> ) by
> replying to this email.
> 
> 
> -- 
> 1053310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053310
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems

> From: Debian FTP Masters 
> Reply-To: Andreas Metzler 
> Date: Mon, 16 Oct 2023 16:49:09 +
> To: 1053310-cl...@bugs.debian.org
> Subject: Bug#1053310: fixed in exim4 4.97~RC2-2
> Message-Id: 
> 
> Source: exim4
> Source-Version: 4.97~RC2-2
> Done: Andreas Metzler 
> 
> We believe that the bug you reported is fixed in the latest version of
> exim4, 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 1053...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
> 
> Debian distribution maintenance software
> pp.
> Andreas Metzler  (supplier of updated exim4 package)
> 
> (This message was generated automatically at their request; if you
> believe that there is a problem with it please contact the archive
> administrators by mailing ftpmas...@ftp-master.debian.org)
> 
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> Format: 1.8
> Date: Mon, 16 Oct 2023 18:26:40 +0200
> Source: exim4
> Architecture: source
> Version: 4.97~RC2-2
> Distribution: unstable
> Urgency: high
> Maintainer: Exim4 Maintainers 
> Changed-By: Andreas Metzler 
> Closes: 1053310
> Changes:
>  exim4 (4.97~RC2-2) unstable; urgency=high
>  .
>* 76_changesfrom_4.96.2.diff: Pull fixes for CVE-2023-42117 and
>  CVE-2023-41227 from upstream GIT master. Closes: #1053310

This should have been CVE-2023-42117 and CVE-2023-42119 AFAICT.

Regards,
Salvatore

Bug#1025581: marked as done (lxsession: dependency on transitional policykit-1 package)

[Debian Bug Tracking System]

Your message dated Thu, 19 Oct 2023 15:50:31 +
with message-id 
and subject line Bug#1025581: fixed in lxsession 0.5.5-2.1
has caused the Debian Bug report #1025581,
regarding lxsession: dependency on transitional policykit-1 package
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.)


-- 
1025581: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025581
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lxsession
Version: 0.5.5-2
Severity: normal
User: pkg-utopia-maintain...@lists.alioth.debian.org
Usertags: policykit-1
Control: block 1025540 by -1

This package has a Depends and/or Build-Depends on the transitional
package policykit-1, which has been separated into polkitd, pkexec and
(deprecated) polkitd-pkla packages.

If this package communicates with polkitd via D-Bus, please represent that
as a Depends, Recommends or Suggests on polkitd, whichever is appropriate
for the strength of the requirement.

If this package runs /usr/bin/pkexec, please represent that as a Depends,
Recommends or Suggests on pkexec, whichever is appropriate for the strength
of the requirement.

If this package requires polkit at build-time (usually for the gettext
extensions polkit.its and polkit.loc), please build-depend on both
libpolkit-gobject-1-dev and polkitd, even if the package does not
actually depend on libpolkit-gobject-1 at runtime. This is because
the gettext extensions are currently in polkitd, but might be moved to
libpolkit-gobject-1-dev in future (see #955204). pkexec is usually not
required at build-time.

For packages that are expected to be backported to bullseye, it's OK to
use an alternative dependency: polkitd | policykit-1 and/or
pkexec | policykit-1.

This is part of a mass bug filing, see
.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: lxsession
Source-Version: 0.5.5-2.1
Done: Simon McVittie 

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated lxsession package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 19 Oct 2023 08:53:46 +0100
Source: lxsession
Architecture: source
Version: 0.5.5-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian LXDE Maintainers 

Changed-By: Simon McVittie 
Closes: 1025581
Changes:
 lxsession (0.5.5-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload
   * lxpolkit, lxsession-logout: Depend on polkitd, not policykit-1.
 The polkitd package replaces the transitional policykit-1, which
 should be removed before Debian 13 and also depends on pkexec. These
 components don't seem to use pkexec. (Closes: #1025581)
   * lxsession: Add Suggests on pkexec.
 This can be used for apport-gtk integration (but that feature is off
 by default) and for apt integration via synaptic-pkexec (but that
 feature has been patched out because it depends on direct access to
 internal dpkg files).
Checksums-Sha1:
 45d92ee4e63a992ac350b480679db8f2df6500f7 2569 lxsession_0.5.5-2.1.dsc
 eb02a0b2fd329bc40b73162512ff79b832e2abe4 12912 
lxsession_0.5.5-2.1.debian.tar.xz
 afd60824987760292c789e55845d12675d06cc24 12201 
lxsession_0.5.5-2.1_source.buildinfo
Checksums-Sha256:
 df43791f7eb902a6a9aad5cbb4beb10fe2b2ab69de156e175ef9887655a2cfb7 2569 
lxsession_0.5.5-2.1.dsc
 ba709041b52b63377974bd6b4de01c47a66841c760d7fa8b1446a375d8279433 12912 
lxsession_0.5.5-2.1.debian.tar.xz
 3974ba9e4075f6cb5324a7f785049ef5e023d6f2d6e4c33ae5f172b45bf42ead 12201 
lxsession_0.5.5-2.1_source.buildinfo
Files:
 4bf3da92b6594e23ce2e5860af037fbc 2569 x11 optional lxsession_0.5.5-2.1.dsc
 c80ab99473db629461ea57f8a4bddb7a 12912 x11 optional 
lxsession_0.5.5-2.1.debian.tar.xz
 9bd91f21f1ac52bdda2b4f1c7d0d2324 12201 x11 optional 
lxsession_0.5.5-2.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAmUxTj8ACgkQ4FrhR4+B
TE8isw/+I5iPJo1stuESmRgezEiNclIjlscozCiLwF+Yai5GeHX3+WGkWOqaWcQ2

Processed: lxsession: diff for NMU version 0.5.5-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1025581 + patch pending
Bug #1025581 [src:lxsession] lxsession: dependency on transitional policykit-1 
package
Added tag(s) patch and pending.

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

Bug#1025581: lxsession: diff for NMU version 0.5.5-2.1

[Simon McVittie]

Control: tags 1025581 + patch pending

Because this bug has been RC for a while with no maintainer response,
and lxsession is now one of only two packages in trixie with dependencies
on policykit-1 (the other is fwupd), I've prepared an NMU for lxsession
versioned as 0.5.5-2.1 and uploaded it. Please see attached debdiff,
or alternatively, the attached patches.

Thanks,
smcv
diffstat for lxsession-0.5.5 lxsession-0.5.5

 changelog |   15 +++
 control   |6 +++---
 2 files changed, 18 insertions(+), 3 deletions(-)

diff -Nru lxsession-0.5.5/debian/changelog lxsession-0.5.5/debian/changelog
--- lxsession-0.5.5/debian/changelog	2020-03-20 19:05:34.0 +
+++ lxsession-0.5.5/debian/changelog	2023-10-19 08:53:46.0 +0100
@@ -1,3 +1,18 @@
+lxsession (0.5.5-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * lxpolkit, lxsession-logout: Depend on polkitd, not policykit-1.
+The polkitd package replaces the transitional policykit-1, which
+should be removed before Debian 13 and also depends on pkexec. These
+components don't seem to use pkexec. (Closes: #1025581)
+  * lxsession: Add Suggests on pkexec.
+This can be used for apport-gtk integration (but that feature is off
+by default) and for apt integration via synaptic-pkexec (but that
+feature has been patched out because it depends on direct access to
+internal dpkg files).
+
+ -- Simon McVittie   Thu, 19 Oct 2023 08:53:46 +0100
+
 lxsession (0.5.5-2) unstable; urgency=medium
 
   * Rename debian/TODO.Debian to fix lintian warning.
diff -Nru lxsession-0.5.5/debian/control lxsession-0.5.5/debian/control
--- lxsession-0.5.5/debian/control	2020-03-20 18:05:10.0 +
+++ lxsession-0.5.5/debian/control	2023-10-19 08:53:46.0 +0100
@@ -25,7 +25,7 @@
  lxde-session, lxsession-default-apps | lxsession-edit,
  openssh-client | ssh-client
 Suggests:
- gpicview, lxpanel, pcmanfm,
+ gpicview, lxpanel, pcmanfm, pkexec,
  consolekit | libpam-systemd [linux-any]
 Provides: x-session-manager, lxde-settings-daemon
 Breaks: lxsession-data (<< 0.5.3-1)
@@ -64,7 +64,7 @@
 Package: lxpolkit
 Architecture: any
 Multi-Arch: allowed
-Depends: ${shlibs:Depends}, ${misc:Depends}, lxsession-data, policykit-1
+Depends: ${shlibs:Depends}, ${misc:Depends}, lxsession-data, polkitd
 Breaks: lxsession (<< 0.5.3-1)
 Replaces: lxsession (<< 0.5.3-1)
 Provides: polkit-1-auth-agent
@@ -92,7 +92,7 @@
 Multi-Arch: allowed
 Depends: ${shlibs:Depends}, ${misc:Depends},
  lxsession-data, lxlock | xdg-utils,
- policykit-1
+ polkitd
 Recommends:
  lsb-release, consolekit | logind [linux-any] | default-logind [linux-any]
 Breaks: lxsession (<< 0.5.3-1)
>From 7223999bb2fb761c51977d786233cbe41a3cb4bc Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Thu, 19 Oct 2023 08:47:09 +0100
Subject: [PATCH 1/3] lxpolkit, lxsession-logout: Depend on polkitd, not
 policykit-1

The polkitd package replaces the transitional policykit-1, which should
be removed before Debian 13 and also depends on pkexec. These components
don't seem to use pkexec.

Closes: #1025581
Signed-off-by: Simon McVittie 
---
 debian/control | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/debian/control b/debian/control
index 6b5f1c3..0312ea2 100644
--- a/debian/control
+++ b/debian/control
@@ -64,7 +64,7 @@ Description: configure what application start up automatically in LXDE
 Package: lxpolkit
 Architecture: any
 Multi-Arch: allowed
-Depends: ${shlibs:Depends}, ${misc:Depends}, lxsession-data, policykit-1
+Depends: ${shlibs:Depends}, ${misc:Depends}, lxsession-data, polkitd
 Breaks: lxsession (<< 0.5.3-1)
 Replaces: lxsession (<< 0.5.3-1)
 Provides: polkit-1-auth-agent
@@ -92,7 +92,7 @@ Architecture: any
 Multi-Arch: allowed
 Depends: ${shlibs:Depends}, ${misc:Depends},
  lxsession-data, lxlock | xdg-utils,
- policykit-1
+ polkitd
 Recommends:
  lsb-release, consolekit | logind [linux-any] | default-logind [linux-any]
 Breaks: lxsession (<< 0.5.3-1)
-- 
2.42.0

>From 7eedbe0823ae137a4d9086fb99903d070895866a Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Thu, 19 Oct 2023 08:50:10 +0100
Subject: [PATCH 2/3] lxsession: Add Suggests on pkexec

This can be used for apport-gtk integration (but that feature is off
by default) and for apt integration via synaptic-pkexec (but that
feature has been patched out because it depends on direct access to
internal dpkg files).

Signed-off-by: Simon McVittie 
---
 debian/control | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/control b/debian/control
index 0312ea2..b67eacc 100644
--- a/debian/control
+++ b/debian/control
@@ -25,7 +25,7 @@ Recommends:
  lxde-session, lxsession-default-apps | lxsession-edit,
  openssh-client | ssh-client
 Suggests:
- gpicview, lxpanel, pcmanfm,
+ gpicview, lxpanel, pcmanfm, pkexec,
  consolekit | libpam-systemd [linux-any]
 Provides: x-session-manager, lxde-settings-daemon
 Breaks: lxsession-data (<< 0.5.3-1)
-- 
2.42.0

>From 

Processed: forwarded 1053873 - cronie: Crond with high load after 19-01-2038

[Debian Bug Tracking System]

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

> forwarded 1053873 https://github.com/cronie-crond/cronie/issues/162
Bug #1053873 [cronie] cronie: Crond with high load after 19-01-2038
Set Bug forwarded-to-address to 
'https://github.com/cronie-crond/cronie/issues/162'.
>
End of message, stopping processing here.

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

Bug#1054174: marked as done (node-clean-css: failed dh_auto_test)

[Debian Bug Tracking System]

Your message dated Thu, 19 Oct 2023 15:05:57 +
with message-id 
and subject line Bug#1054174: fixed in node-clean-css 5.3.2+~5.6.2-1
has caused the Debian Bug report #1054174,
regarding node-clean-css: failed dh_auto_test
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.)


-- 
1054174: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054174
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-clean-css
Version: 5.3.1+~5.6.1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
X-Debbugs-Cc: sweetyf...@deepin.org

Hi,

During a rebuild of your package in unstable, your package fails to
build from source.

Full log can be accessed at:


https://build.opensuse.org/package/live_build_log/home:utsweetyfish:node-202309/node-clean-css/Debian_Unstable/x86_64

Tail of log for your package:

  ✗ Errored » Asynchronous Error
  in protocol imports
  in 
test/protocol-imports-test.js/usr/src/packages/BUILD/test/protocol-imports-test.js:706
  this.proxyServer.destroy();
   ^

TypeError: Cannot read properties of undefined (reading 'destroy')
at Object.teardown 
(/usr/src/packages/BUILD/test/protocol-imports-test.js:706:24)
at runTeardown (/usr/share/nodejs/vows/lib/vows/suite.js:382:37)
at Object.tryEnd (/usr/share/nodejs/vows/lib/vows/suite.js:362:17)
at EventEmitter. 
(/usr/share/nodejs/vows/lib/vows.js:94:18)
at EventEmitter.emit (node:events:525:35)
at options.Emitter.emit (/usr/share/nodejs/vows/lib/vows.js:241:24)
at /usr/share/nodejs/vows/lib/vows/context.js:31:52
at process.processTicksAndRejections 
(node:internal/process/task_queues:77:11)

Node.js v18.13.0
dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit 
code 1
make: *** [debian/rules:8: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit 
status 2

Thanks!
Tianyu Chen @ deepin
--- End Message ---
--- Begin Message ---
Source: node-clean-css
Source-Version: 5.3.2+~5.6.2-1
Done: Yadd 

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-clean-css package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 19 Oct 2023 18:44:11 +0400
Source: node-clean-css
Architecture: source
Version: 5.3.2+~5.6.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 1054174
Changes:
 node-clean-css (5.3.2+~5.6.2-1) unstable; urgency=medium
 .
   * Update lintian override info format in d/source/lintian-overrides
 on line 4-5.
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository-Browse
   * Update standards version to 4.6.2, no changes needed.
   * New upstream version 5.3.2+~5.6.2
   * Fix test using an older node-nock (Closes: #1054174)
Checksums-Sha1: 
 eebea1ed1a846adf2f6ff61cd137498359c35c38 2843 node-clean-css_5.3.2+~5.6.2-1.dsc
 1430c2032c0342ee96f530e1c25be593b95ec007 27581 
node-clean-css_5.3.2+~5.6.2.orig-cli.tar.gz
 fb684f4c0b1c743b98ecf8a1a5749d48a9d7b140 502372 
node-clean-css_5.3.2+~5.6.2.orig.tar.gz
 8a2ec0586317a8bac20d493fe8da129ae73c92da 36580 
node-clean-css_5.3.2+~5.6.2-1.debian.tar.xz
Checksums-Sha256: 
 41b019655792ddc2cf97c3fb6c14f4bb6f63db12ae2470365ba4e05fcd185e36 2843 
node-clean-css_5.3.2+~5.6.2-1.dsc
 06e8535f47a074cad194633d2b8a661c08de58907d983d939a85532851a6ce0a 27581 
node-clean-css_5.3.2+~5.6.2.orig-cli.tar.gz
 33723a9d45c69dc1bcce631caea2217645bbec39fcdb9860b2971fc115a8c572 502372 
node-clean-css_5.3.2+~5.6.2.orig.tar.gz
 ab29ecaec0be33c5f693e235d740fe4d1b89996f093b78a798d2ab3b2f66de63 36580 
node-clean-css_5.3.2+~5.6.2-1.debian.tar.xz
Files: 
 bfc7db64f7d572b5dd5e0b08662cc43b 2843 javascript optional 
node-clean-css_5.3.2+~5.6.2-1.dsc
 b40eb8792d5cbab6c1e721823fbf38ac 27581 

Bug#1054176: marked as done (node-rollup-plugin-typescript: failing dh_auto_test)

[Debian Bug Tracking System]

Your message dated Thu, 19 Oct 2023 14:56:21 +
with message-id 
and subject line Bug#1054176: fixed in node-rollup-plugin-typescript 
11.1.5~ds+~1.0.1-1
has caused the Debian Bug report #1054176,
regarding node-rollup-plugin-typescript: failing dh_auto_test
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.)


-- 
1054176: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054176
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-rollup-plugin-typescript
Version: 11.1.2~ds+~1.0.1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
X-Debbugs-Cc: sweetyf...@deepin.org

Hi,

During a rebuild of your package in unstable, your package fails to
build from source.

Full log can be accessed at:


https://build.opensuse.org/package/live_build_log/home:utsweetyfish:node-202309/node-rollup-plugin-typescript/Debian_Unstable/aarch64

Tail of log for your package:

not ok 81 one.js
  ---
operator: ok
expected: true
actual:   false
at: Test. 
(/usr/src/packages/BUILD/packages/typescript/test/test.js:927:9)
stack: |-
  Error: one.js
  at Test.assert [as _assert] 
(/usr/share/nodejs/tape/lib/test.js:312:48)
  at Test.bound [as _assert] 
(/usr/share/nodejs/tape/lib/test.js:95:17)
  at Test.assert (/usr/share/nodejs/tape/lib/test.js:431:7)
  at Test.bound [as true] 
(/usr/share/nodejs/tape/lib/test.js:95:17)
  at Test. 
(/usr/src/packages/BUILD/packages/typescript/test/test.js:927:9)
  ...
not ok 82 /* eslint-disable */ function one() { console.log('one'); } 
export { one }; 
  ---
operator: ok
expected: true
actual:   false
at: Test. 
(/usr/src/packages/BUILD/packages/typescript/test/test.js:928:9)
stack: |-
  Error: /* eslint-disable */
  function one() {
  console.log('one');
  }
  
  export { one };
  
  at Test.assert [as _assert] 
(/usr/share/nodejs/tape/lib/test.js:312:48)
  at Test.bound [as _assert] 
(/usr/share/nodejs/tape/lib/test.js:95:17)
  at Test.assert (/usr/share/nodejs/tape/lib/test.js:431:7)
  at Test.bound [as true] 
(/usr/share/nodejs/tape/lib/test.js:95:17)
  at Test. 
(/usr/src/packages/BUILD/packages/typescript/test/test.js:928:9)
  ...
...
1..105
# tests 105
# pass  103
# fail  2

dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit 
code 1
make: *** [debian/rules:5: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit 
status 2

Thanks!
Tianyu Chen @ deepin
--- End Message ---
--- Begin Message ---
Source: node-rollup-plugin-typescript
Source-Version: 11.1.5~ds+~1.0.1-1
Done: Yadd 

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-rollup-plugin-typescript 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 19 Oct 2023 18:30:39 +0400
Source: node-rollup-plugin-typescript
Architecture: source
Version: 11.1.5~ds+~1.0.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 1054176
Changes:
 node-rollup-plugin-typescript (11.1.5~ds+~1.0.1-1) unstable; urgency=medium
 .
   * Team upload
   * New upstream version 11.1.5~ds+~1.0.1
   * Refresh patches
   * Update build (Closes: #1054176)
Checksums-Sha1: 
 054e94dfa628ddaa642c9c051ec01bca828a2a7a 2942 
node-rollup-plugin-typescript_11.1.5~ds+~1.0.1-1.dsc
 304ba24e4796b452e61d01e8a66742a7701f8fab 33176 
node-rollup-plugin-typescript_11.1.5~ds+~1.0.1.orig-legacy.tar.xz
 a8bfc3f5e777d19a410b99eef3e892cce4803ea8 158108 

Bug#1054174: marked as pending in node-clean-css

[Yadd]

Control: tag -1 pending

Hello,

Bug #1054174 in node-clean-css 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/js-team/node-clean-css/-/commit/c8dc3ca049bd8edfc8560f37e03a2979b2aa92b0


Fix test using an older node-nock

Closes: #1054174


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1054174

Processed: Bug#1054174 marked as pending in node-clean-css

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1054174 [src:node-clean-css] node-clean-css: failed dh_auto_test
Added tag(s) pending.

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

Bug#1054176: marked as pending in node-rollup-plugin-typescript

[Yadd]

Control: tag -1 pending

Hello,

Bug #1054176 in node-rollup-plugin-typescript 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/js-team/node-rollup-plugin-typescript/-/commit/a075c1e7fae34b6c2583b0d0620548b53838d6c1


Update build

Closes: #1054176


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1054176

Processed: Bug#1054176 marked as pending in node-rollup-plugin-typescript

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1054176 [src:node-rollup-plugin-typescript] node-rollup-plugin-typescript: 
failing dh_auto_test
Added tag(s) pending.

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

Bug#1050828: marked as done (src:pd-xsample: fails to migrate to testing for too long: FTBFS on ppc64el)

[Debian Bug Tracking System]

Your message dated Thu, 19 Oct 2023 14:34:59 +
with message-id 
and subject line Bug#1050828: fixed in pd-xsample 0.3.2+git20170905.1.4441ae5-7
has caused the Debian Bug report #1050828,
regarding src:pd-xsample: fails to migrate to testing for too long: FTBFS on 
ppc64el
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.)


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

Source: pd-xsample
Version: 0.3.2+git20170905.1.4441ae5-5
Severity: serious
Control: close -1 0.3.2+git20170905.1.4441ae5-6
Tags: sid trixie ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:pd-xsample has been trying to migrate for 
32 days [2]. Hence, I am filing this bug. The version in unstable failed 
to build on ppc64el, while it built there successfully in the past.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=pd-xsample



OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: pd-xsample
Source-Version: 0.3.2+git20170905.1.4441ae5-7
Done: Benjamin Drung 

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

Debian distribution maintenance software
pp.
Benjamin Drung  (supplier of updated pd-xsample package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 19 Oct 2023 15:52:10 +0200
Source: pd-xsample
Built-For-Profiles: noudeb
Architecture: source
Version: 0.3.2+git20170905.1.4441ae5-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Benjamin Drung 
Closes: 1050828
Launchpad-Bugs-Fixed: 2039810
Changes:
 pd-xsample (0.3.2+git20170905.1.4441ae5-7) unstable; urgency=medium
 .
   * Team upload.
   * Skip Pd64 externals for ppc64el, because vec_dst does not support double
 (Closes: #1050828, LP: #2039810)
Checksums-Sha1:
 92e270de0a78c27870fd959ae74a13c02dd95317 2171 
pd-xsample_0.3.2+git20170905.1.4441ae5-7.dsc
 b8d8fd8460ec62a15ab83a5c1a0edc96d960ebad 4116 
pd-xsample_0.3.2+git20170905.1.4441ae5-7.debian.tar.xz
 fca485415633ff8efeecd9dda089629937377fa1 7216 
pd-xsample_0.3.2+git20170905.1.4441ae5-7_source.buildinfo
Checksums-Sha256:
 da08760d8abe0047884457619f46952a3d7906bdbf113c3ba3343a311ac0154f 2171 
pd-xsample_0.3.2+git20170905.1.4441ae5-7.dsc
 7ab01ccd8523c0ce0e61867138b8a55c7b8c5b03a1c84257f1bfb43e7006b8c3 4116 
pd-xsample_0.3.2+git20170905.1.4441ae5-7.debian.tar.xz
 906fd34a9e96f3dda78f0c8a91e9ccc276e34e4f1e20f9554c79585ecdd7d5aa 7216 
pd-xsample_0.3.2+git20170905.1.4441ae5-7_source.buildinfo
Files:
 bff62f75ebf15510a0c7cd4518179498 2171 sound optional 
pd-xsample_0.3.2+git20170905.1.4441ae5-7.dsc
 b676d39f5380123bed64854cf1de036a 4116 sound optional 

Bug#1054228: pam FTBFS: No series file found

[Helmut Grohne]

Source: pam
Version: 1.5.2-7
Tags: ftbfs patch
Severity: serious
User: helm...@debian.org
Usertags: rebootstrap

pam fails to build from source in unstable, because quilt no longer
recognizes the QUILT_PATCHES_DIR variable and therefore does not find a
series file. Renaming it to QUILT_PATCHES fixes the build. I'm attaching
a patch for your convenience. This bug happens to break architecture
bootstrap for all architectures.

Helmut
diff --minimal -Nru pam-1.5.2/debian/changelog pam-1.5.2/debian/changelog
--- pam-1.5.2/debian/changelog  2023-08-17 01:22:53.0 +0200
+++ pam-1.5.2/debian/changelog  2023-10-19 16:24:44.0 +0200
@@ -1,3 +1,10 @@
+pam (1.5.2-7.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS: s/QUILT_PATCHES_DIR/QUILT_PATCHES/. (Closes: #-1)
+
+ -- Helmut Grohne   Thu, 19 Oct 2023 16:24:44 +0200
+
 pam (1.5.2-7) unstable; urgency=medium
 
   [ Steve Langasek ]
diff --minimal -Nru pam-1.5.2/debian/rules pam-1.5.2/debian/rules
--- pam-1.5.2/debian/rules  2023-08-17 01:22:53.0 +0200
+++ pam-1.5.2/debian/rules  2023-10-19 16:24:44.0 +0200
@@ -13,7 +13,7 @@
 LC_COLLATE=C
 export LC_COLLATE
 
-export QUILT_PATCH_DIR = debian/patches-applied
+export QUILT_PATCHES = debian/patches-applied
 
 d = $(CURDIR)/debian
 dl = $(d)/local

Processed: Re: [Pkg-javascript-devel] Bug#1054175: node-require-main-filename: failing dh_auto_test

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #1054175 [src:node-require-main-filename] node-require-main-filename: 
failing dh_auto_test
Added tag(s) moreinfo.

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

Bug#1054175: [Pkg-javascript-devel] Bug#1054175: node-require-main-filename: failing dh_auto_test

[Yadd]

Control: tags -1 + moreinfo

On 10/18/23 20:27, Tianyu Chen wrote:

Source: node-require-main-filename
Version: 2.0.0-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source
X-Debbugs-Cc: sweetyf...@deepin.org

Hi,

During a rebuild of your package in unstable, your package fails to
build from source.

Full log can be accessed at:


https://build.opensuse.org/package/live_build_log/home:utsweetyfish:node-202309/node-require-main-filename/Debian_Unstable/aarch64

Tail of log for your package:

# Subtest: should default to process.cwd() if require.main is 
undefined
not ok 1 - expected '/usr/src/packages/BUILD' to match 
/(?:.*autopkgtest.*|require-main-filename)/
  ---
[...]

1..1
# failed 1 test
# time=95.325ms
not ok 1 - test.js # time=95.325ms
  ---
  env: {}
  file: test.js
  timeout: 3
  command: /usr/bin/node
  args:
- test.js
  stdio:
- 0
- pipe
- 2
  cwd: /usr/src/packages/BUILD
  exitCode: 1
  ...

1..1
# failed 1 test
# time=1113.041ms
--|-|--|-|-|---
File  | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
--|-|--|-|-|---
All files | 100 |  100 | 100 | 100 |
 index.js | 100 |  100 | 100 | 100 |
--|-|--|-|-|---
dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit 
code 1
make: *** [debian/rules:8: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit 
status 2

Thanks!
Tianyu Chen @ deepin


Hi,

I'm not able to reproduce this issue

Processed: bug 1053870 is forwarded to https://github.com/shevek/libspf2/issues/45

[Debian Bug Tracking System]

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

> forwarded 1053870 https://github.com/shevek/libspf2/issues/45
Bug #1053870 [libspf2-2] CVE-2023-42118: integer underflow in libspf2 resulting 
in RCE
Set Bug forwarded-to-address to 'https://github.com/shevek/libspf2/issues/45'.
> thanks
Stopping processing here.

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

Bug#1054224: zookeeper: CVE-2023-44981

[Salvatore Bonaccorso]

Source: zookeeper
Version: 3.8.0-11
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 3.4.13-6

Hi,

The following vulnerability was published for zookeeper.

CVE-2023-44981[0]:
| Authorization Bypass Through User-Controlled Key vulnerability in
| Apache ZooKeeper. If SASL Quorum Peer authentication is enabled in
| ZooKeeper (quorum.auth.enableSasl=true), the authorization is done
| by verifying that the instance part in SASL authentication ID is
| listed in zoo.cfg server list. The instance part in SASL auth ID is
| optional and if it's missing, like 'e...@example.com', the
| authorization check will be skipped. As a result an arbitrary
| endpoint could join the cluster and begin propagating counterfeit
| changes to the leader, essentially giving it complete read-write
| access to the data tree. Quorum Peer authentication is not enabled
| by default.  Users are recommended to upgrade to version 3.9.1,
| 3.8.3, 3.7.2, which fixes the issue.  Alternately ensure the
| ensemble election/quorum communication is protected by a firewall as
| this will mitigate the issue.  See the documentation for more
| details on correct cluster administration.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-44981
https://www.cve.org/CVERecord?id=CVE-2023-44981
[1] https://www.openwall.com/lists/oss-security/2023/10/11/4
[2] 
https://github.com/apache/zookeeper/commit/96b3172ca249a8580e9a315d589d319286cee4ee

Regards,
Salvatore

Processed: zookeeper: CVE-2023-44981

[Debian Bug Tracking System]

Processing control commands:

> found -1 3.4.13-6
Bug #1054224 [src:zookeeper] zookeeper: CVE-2023-44981
Marked as found in versions zookeeper/3.4.13-6.

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

Bug#1054223: golang-github-crewjam-saml: CVE-2023-45683

[Salvatore Bonaccorso]

Source: golang-github-crewjam-saml
Version: 0.4.12-2
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for golang-github-crewjam-saml.

CVE-2023-45683[0]:
| github.com/crewjam/saml is a saml library for the go language. In
| affected versions the package does not validate the ACS Location URI
| according to the SAML binding being parsed. If abused, this flaw
| allows attackers to register malicious Service Providers at the IdP
| and inject Javascript in the ACS endpoint definition, achieving
| Cross-Site-Scripting (XSS) in the IdP context during the redirection
| at the end of a SAML SSO Flow. Consequently, an attacker may perform
| any authenticated action as the victim once the victim’s browser
| loaded the SAML IdP initiated SSO link for the malicious service
| provider. Note: SP registration is commonly an unrestricted
| operation in IdPs, hence not requiring particular permissions or
| publicly accessible to ease the IdP interoperability. This issue is
| fixed in version 0.4.14. Users unable to upgrade may perform
| external validation of URLs provided in SAML metadata, or restrict
| the ability for end-users to upload arbitrary metadata.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-45683
https://www.cve.org/CVERecord?id=CVE-2023-45683
[1] https://github.com/crewjam/saml/security/advisories/GHSA-267v-3v32-g6q5

Regards,
Salvatore

Bug#1053265: dipy: test_icm_square test fails since exact equality used with floating point numbers

[Andreas Tille]

Hi,

I tried to reproduce this issue.  When running autopkgtst in my local
pbuilder chroot I get four failures - but different from the one said
below.  When checking Salsa CI[1] it has just one failure which is
pretty strange:

>   assert_equal(duration_2core < duration_1core, True)
E   AssertionError: 
E   Items are not equal:
EACTUAL: False
EDESIRED: True

I wonder whether it makes sense at all to compare the execution times
depending from the number of cores used when running in our CI.  Would
you agree that this test should be rather skipped?

Unfortunately I can't reproduce the h5py related issue.

Kind regards
   Andreas.

[1] https://salsa.debian.org/med-team/dipy/-/jobs/4827654#L790

Am Sat, Sep 30, 2023 at 11:30:59AM +0200 schrieb Drew Parsons:
> Source: dipy
> Version: 1.7.0-2
> Severity: serious
> Justification: debci
> 
> h5py 3.9.0 is triggering an error in dipy debci tests,
> https://ci.debian.net/data/autopkgtest/testing/amd64/d/dipy/38279462/log.gz
> 
> However from the error log, it's not clear that the problem is
> directly related to h5py.  An exact [in]equality test is failing
> between floating point numbers.
> 
> The error log is:
> 
> 1967s ___ test_icm_square 
> 
> 1967s 
> 1967s def test_icm_square():
> 1967s 
> 1967s com = ConstantObservationModel()
> 1967s icm = IteratedConditionalModes()
> 1967s 
> 1967s initial_segmentation = square
> 1967s 
> 1967s mu, sigma = com.seg_stats(square_1, initial_segmentation,
> 1967s   nclasses)
> 1967s sigmasq = sigma ** 2
> 1967s npt.assert_(mu[0] >= 0.0)
> 1967s npt.assert_(mu[1] >= 0.0)
> 1967s npt.assert_(mu[2] >= 0.0)
> 1967s npt.assert_(mu[3] >= 0.0)
> 1967s npt.assert_(sigmasq[0] >= 0.0)
> 1967s npt.assert_(sigmasq[1] >= 0.0)
> 1967s npt.assert_(sigmasq[2] >= 0.0)
> 1967s npt.assert_(sigmasq[3] >= 0.0)
> 1967s 
> 1967s negll = com.negloglikelihood(square_1, mu, sigmasq, nclasses)
> 1967s 
> 1967s final_segmentation_1 = np.empty_like(square_1)
> 1967s final_segmentation_2 = np.empty_like(square_1)
> 1967s 
> 1967s beta = 0.0
> 1967s 
> 1967s for i in range(max_iter):
> 1967s 
> 1967s print('\n')
> 1967s print('>> Iteration: ' + str(i))
> 1967s print('\n')
> 1967s 
> 1967s final_segmentation_1, energy_1 = icm.icm_ising(negll, beta,
> 1967s
> initial_segmentation)
> 1967s initial_segmentation = final_segmentation_1
> 1967s 
> 1967s beta = 2
> 1967s initial_segmentation = square
> 1967s 
> 1967s for j in range(max_iter):
> 1967s 
> 1967s print('\n')
> 1967s print('>> Iteration: ' + str(j))
> 1967s print('\n')
> 1967s 
> 1967s final_segmentation_2, energy_2 = icm.icm_ising(negll, beta,
> 1967s
> initial_segmentation)
> 1967s initial_segmentation = final_segmentation_2
> 1967s 
> 1967s difference_map = np.abs(final_segmentation_1 - 
> final_segmentation_2)
> 1967s >   npt.assert_(np.abs(np.sum(difference_map)) != 0)
> 1967s E   AssertionError
> 1967s 
> 1967s dipy/segment/tests/test_mrf.py:370: AssertionError
> 
> 
> I'm assumung final_segmentation is floating point, not integer.
> Correct me if that's wrong. In general exact equality of floating
> point numbers should always be expected to fail. The test should be
> something like
>npt.assert_( not np.isclose( np.abs(np.sum(difference_map)), 0 ) )
>
> 
> If final_segmentation is an integer then of course it's a different
> problem.
> 
> ___
> Debian-med-packaging mailing list
> debian-med-packag...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging
> 

-- 
http://fam-tille.de

Processed: Re: Bug#967799: RM: vte / depends on deprecated GTK 2

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 887649
Bug #967799 [src:vte] vte: depends on deprecated GTK 2
967799 was not blocked by any bugs.
967799 was blocking: 947713
Added blocking bug(s) of 967799: 887649

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

Bug#1040043: additional info

[Chris Vogel]

I saw in Boris logfile that the log is partly in german as well as my log on a 
Debian Bullseye using rspamd 3.2.1 on a RockPro64.

I opened an issue for yunhost which is the system integration I use on that 
system on the basis of Debian here: 
https://github.com/YunoHost/issues/issues/2269

"Switched the locale back to de_DE.UTF-8, restarted rspamd and reproduced the 
bahviour.

To get my ynh working with rspamd I switched back to C.UTF-8, restarted rspamd 
and got the same errors containing german again. WTF.

After I restarted the daemon a few times and tried after each time to learn 
more ham/spam from existing folders it suddenly started working without crashes 
again.

I guess someone needs to look at the problem on their host to compare results."

Processed: tagging 1053880

[Debian Bug Tracking System]

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

> tags 1053880 + upstream
Bug #1053880 {Done: Yadd } [src:node-babel7] node-babel7: 
CVE-2023-45133
Ignoring request to alter tags of bug #1053880 to the same tags previously set
> thanks
Stopping processing here.

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

Processed: tagging 1053877

[Debian Bug Tracking System]

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

> tags 1053877 + upstream
Bug #1053877 [src:zabbix] zabbix: CVE-2023-32721 CVE-2023-32722 CVE-2023-32723 
CVE-2023-32724
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Bug#1052847: python-marshmallow: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.11 returned exit code 13

[Benjamin Drung]

On Tue, 10 Oct 2023 13:21:26 +0800 Paul Wise  wrote:
> On Tue, 26 Sep 2023 15:23:12 +0200 Lucas Nussbaum wrote:
>  
> > During a rebuild of all packages in sid, your package failed to
build
> > on amd64.
> ...
> > > ImportError while loading conftest
'/<>/.pybuild/cpython3_3.11_marshmallow/build/tests/conftes
t.py'.
> > > tests/conftest.py:4: in 
> > > from tests.base import User, UserSchema, Blog
> > > tests/base.py:14: in 
> > > central = pytz.timezone("US/Central")
> > > /usr/lib/python3/dist-packages/pytz/__init__.py:202: in timezone
> > > raise UnknownTimeZoneError(zone)
> > > E   pytz.exceptions.UnknownTimeZoneError: 'US/Central'
> 
> This was caused by the split of tzdata-legacy from tzdata, the fix is
> to add tzdata-legacy to build-depends and I notice that you already
> fixed the issue in git and tagged an upload but haven't uploaded yet.

I submitted an upstream PR to change the timezone to a non-legacy one:
https://github.com/marshmallow-code/marshmallow/pull/2198

The change was merged. So the tzdata-legacy build dependency can be
dropped when packaging the next upstream release.

-- 
Benjamin Drung
Debian & Ubuntu Developer

Bug#1052778: marked as done (php-nesbot-carbon: FTBFS: make[1]: *** [debian/rules:22: override_dh_auto_test] Error 2)

[Debian Bug Tracking System]

Your message dated Thu, 19 Oct 2023 08:50:10 +
with message-id 
and subject line Bug#1052778: fixed in php-nesbot-carbon 2.69.0-2
has caused the Debian Bug report #1052778,
regarding php-nesbot-carbon: FTBFS: make[1]: *** [debian/rules:22: 
override_dh_auto_test] Error 2
to be marked as done.

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

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


-- 
1052778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052778
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php-nesbot-carbon
Version: 2.69.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> phpabtpl \
>   --require nesbot/carbon \
>   --require doctrine/dbal \
>   > debian/autoload.php.test.tpl
> Proceeding without a composer.json file.phpab \
>   -o tests/autoload.php \
>   -t debian/autoload.php.test.tpl \
>   --blacklist 'carbon\\cli' \
>   --blacklist 'symfony\\component\\translation\\translatorinterface' \
>   tests
> phpab %development% - Copyright (C) 2009 - 2023 by Arne Blankerts and 
> Contributors
> 
> Scanning directory tests
> 
> Autoload file tests/autoload.php generated.
> 
> phpunit --bootstrap tests/autoload.php --include-path src
> PHPUnit 9.6.13 by Sebastian Bergmann and contributors.
> 
> Warning:   Your XML configuration validates against a deprecated schema.
> Suggestion:Migrate your XML configuration using "--migrate-configuration"!
> 
> .   61 / 5634 (  
> 1%)
> .  122 / 5634 (  
> 2%)
> .  183 / 5634 (  
> 3%)
> .  244 / 5634 (  
> 4%)
> .  305 / 5634 (  
> 5%)
> .  366 / 5634 (  
> 6%)
> .  427 / 5634 (  
> 7%)
> .  488 / 5634 (  
> 8%)
> .  549 / 5634 (  
> 9%)
> .  610 / 5634 ( 
> 10%)
> .  671 / 5634 ( 
> 11%)
> .  732 / 5634 ( 
> 12%)
> .  793 / 5634 ( 
> 14%)
> .  854 / 5634 ( 
> 15%)
> .  915 / 5634 ( 
> 16%)
> .  976 / 5634 ( 
> 17%)
> . 1037 / 5634 ( 
> 18%)
> . 1098 / 5634 ( 
> 19%)
> . 1159 / 5634 ( 
> 20%)
> . 1220 / 5634 ( 
> 21%)
> . 1281 / 5634 ( 
> 22%)
> . 1342 / 5634 ( 
> 23%)
> .S... 1403 / 5634 ( 
> 24%)
> . 1464 / 5634 ( 
> 25%)
> . 1525 / 5634 ( 
> 27%)
> . 1586 / 5634 ( 
> 28%)
> . 1647 / 5634 ( 
> 29%)
> . 1708 / 5634 ( 
> 30%)
> . 1769 / 5634 ( 
> 31%)
> . 1830 / 5634 ( 
> 32%)
> . 1891 / 5634 ( 
> 33%)
> . 1952 / 5634 ( 
> 34%)
> . 2013 / 5634 ( 
> 35%)
> . 2074 / 5634 ( 
> 36%)
> SS... 

Bug#1052842: marked as pending in pydevd

[Julian Gilbey]

Control: tag -1 pending

Hello,

Bug #1052842 in pydevd reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/python-team/packages/pydevd/-/commit/33c36a4f4ed1cd041a3fcf68551f2ebc5268714e


Allow django 4.2 in tests (closes: #1052842)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1052842

Processed: Bug#1052842 marked as pending in pydevd

[Debian Bug Tracking System]

Processing control commands:

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

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

Processed: src:yavta: fails to migrate to testing for too long: FTBFS on mips64el and ppc64el

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.0+git20220328.c7b5b75-2
Bug #1054208 [src:yavta] src:yavta: fails to migrate to testing for too long: 
FTBFS on mips64el and ppc64el
Marked as fixed in versions yavta/0.0+git20220328.c7b5b75-2.
Bug #1054208 [src:yavta] src:yavta: fails to migrate to testing for too long: 
FTBFS on mips64el and ppc64el
Marked Bug as done

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

Bug#1054208: src:yavta: fails to migrate to testing for too long: FTBFS on mips64el and ppc64el

[Paul Gevers]

Source: yavta
Version: 0.0+git20220328.c7b5b75-1
Severity: serious
Control: close -1 0.0+git20220328.c7b5b75-2
Tags: sid trixie ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:yavta has been trying to migrate for 31 
days [2]. Hence, I am filing this bug. The version in unstable failed to 
build on mips64el and ppc64el.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=yavta



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1054024: marked as done (hdf5: FTBFS: Testing JUnit-TestH5Fbasic Failure)

[Debian Bug Tracking System]

Your message dated Thu, 19 Oct 2023 15:18:39 +0800
with message-id 

and subject line close the bug
has caused the Debian Bug report #1054024,
regarding hdf5: FTBFS: Testing JUnit-TestH5Fbasic Failure
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.)


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

Package: hdf5
Version: 1.10.10+repack-2
Severity: wishlist
Tags: ftbfs
User: debian-loonga...@lists.debian.org
Usertags: loong64

Dear maintainers,

I've encountered an issue I would like to give feedback on. The 
hdf5_1.10.10+repack-2 version has a problem with test case errors when 
compiling locally again, e.g. in amd64 rootfs environment.

The error message is as follows:
```
java  -Xmx1024M -Dorg.slf4j.simpleLogger.defaultLog=trace 
-Djava.library.path=./testlibs -cp 
.:./testlibs/jarhdf5-1.10.10.jar:./testlibs/junit4.jar:./testlibs/hamcrest.jar:./testlibs/slf4j-api.jar:./testlibs/slf4j-simple.jar:jarhdf5test.jar: 
-ea org.junit.runner.JUnitCore test.TestH5Fbasic
Testing JUnit-TestH5Fbasic [main] INFO hdf.hdf5lib.H5 - HDF5 library: 
hdf5_java

[main] INFO hdf.hdf5lib.H5 -  successfully loaded from java.library.path
**FAILED**    JUnit-TestH5Fbasic
    Expected result differs from actual result
    *** JUnit-TestH5Fbasic.txt    2023-10-15 22:17:39.14000 -0400
    --- JUnit-TestH5Fbasic.out    2023-10-15 22:17:41.32800 -0400
    ***
    *** 15,22 
  .testH5Fclose_twice
  .testH5Freopen
  .testH5Fopen_read_only
    !
  Time:  

    ! OK (16 tests)

    --- 15,55 
  .testH5Fclose_twice
  .testH5Freopen
  .testH5Fopen_read_only
    ! E
  Time:  
    + There was 1 failure:
    + 1) testH5Fopen_read_only(test.TestH5Fbasic)
    + java.lang.AssertionError: Expected exception: 
hdf.hdf5lib.exceptions.HDF5LibraryException
    +     at 
org.junit.internal.runners.statements.ExpectException.evaluate(ExpectException.java:35)
    +     at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
    +     at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)

    +     at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:61)
    +     at 
org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
    +     at 
org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)

    +     at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
    +     at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
    +     at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)

    +     at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
    +     at 
org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
    +     at 
org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
    +     at 
org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
    +     at 
org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
    +     at 
org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)

    +     at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
    +     at org.junit.runners.Suite.runChild(Suite.java:128)
    +     at org.junit.runners.Suite.runChild(Suite.java:27)
    +     at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
    +     at 
org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
    +     at 
org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
    +     at 
org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
    +     at 
org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
    +     at 
org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)

    +     at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
    +     at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
    +     at org.junit.runner.JUnitCore.run(JUnitCore.java:115)
    +     at org.junit.runner.JUnitCore.runMain(JUnitCore.java:77)
    +     at org.junit.runner.JUnitCore.main(JUnitCore.java:36)

    ! FAILURES!!!
    ! Tests run: 16,  Failures: 1
```

Please pay attention to the above phenomenon.
So far it seems that Debian Package Auto-Building environment [1] 
compiles hdf5 without the above test case failures.

If this is my problem, please correct me.

[1]:https://buildd.debian.org/status/package.php?p=hdf5=sid

thanks,
Dandan Zhang
--- End Message ---
--- Begin Message ---
Version: 1.10.10+repack-3
Tag: fixed

Bug#1052966: marked as done (rainbow-delimiters: FTBFS: make: *** [debian/rules:4: binary] Error 25)

[Debian Bug Tracking System]

Your message dated Thu, 19 Oct 2023 07:13:03 +
with message-id 
and subject line Bug#1052966: fixed in rainbow-delimiters 
2.1.5+git20230830.1.f40ece5-1
has caused the Debian Bug report #1052966,
regarding rainbow-delimiters: FTBFS: make: *** [debian/rules:4: binary] Error 25
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.)


-- 
1052966: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052966
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rainbow-delimiters
Version: 2.1.5-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with elpa
>dh_update_autotools_config
>dh_autoreconf
>dh_elpa_test
>   emacs -batch -Q -l package --eval "(add-to-list 'package-directory-list 
> \"/usr/share/emacs/site-lisp/elpa\")" --eval "(add-to-list 
> 'package-directory-list \"/usr/share/emacs/site-lisp/elpa-src\")" -f 
> package-initialize -L . -l rainbow-delimiters-test.el --eval 
> \(ert-run-tests-batch-and-exit\)
> Running 24 tests (2023-09-26 06:54:26+, selector ‘t’)
>passed   1/24  can-customize-face-picker (0.000448 sec)
>passed   2/24  can-disable-mode (0.60 sec)
>passed   3/24  can-enable-mode (0.42 sec)
>passed   4/24  cycles-faces (0.000152 sec)
>passed   5/24  delimiters-disabled-by-face-picker-contribute-to-depth 
> (0.98 sec)
>passed   6/24  doesnt-cycle-outermost-only-faces (0.000130 sec)
>passed   7/24  doesnt-highlight-escaped-delimiters (0.000213 sec)
>passed   8/24  doesnt-highlight-in-comments-1 (0.000250 sec)
>passed   9/24  doesnt-highlight-in-comments-2 (0.002313 sec)
>passed  10/24  doesnt-highlight-in-strings (0.000266 sec)
>passed  11/24  doesnt-higlight-nondelimiters-1 (0.91 sec)
>passed  12/24  doesnt-higlight-nondelimiters-2 (0.000202 sec)
>passed  13/24  face-picker-can-disable-highlighting (0.000127 sec)
> Test highlights-all-delimiters backtrace:
>   signal(ert-test-failed (((should (ert-equal-including-properties (pr
>   ert-fail(((should (ert-equal-including-properties (progn (remove-lis
>   (if (unwind-protect (setq value-46 (apply fn-44 args-45)) (setq form
>   (let (form-description-48) (if (unwind-protect (setq value-46 (apply
>   (let ((value-46 'ert-form-evaluation-aborted-47)) (let (form-descrip
>   (let* ((fn-44 #'ert-equal-including-properties) (args-45 (condition-
>   (let ((str "foo x;")) (insert str) (fontify-buffer) (let* ((fn-
>   (progn (funcall 'c++-mode) (font-lock-mode) (rainbow-delimiters-mode
>   (unwind-protect (progn (funcall 'c++-mode) (font-lock-mode) (rainbow
>   (save-current-buffer (set-buffer temp-buffer) (unwind-protect (progn
>   (let ((temp-buffer (generate-new-buffer " *temp*" t))) (save-current
>   (lambda nil (let ((temp-buffer (generate-new-buffer " *temp*" t))) (
>   ert--run-test-internal(#s(ert--test-execution-info :test #s(ert-test
>   ert-run-test(#s(ert-test :name highlights-all-delimiters :documentat
>   ert-run-or-rerun-test(#s(ert--stats :selector t :tests ... :test-map
>   ert-run-tests(t #f(compiled-function (event-type  event-args) #
>   ert-run-tests-batch(nil)
>   ert-run-tests-batch-and-exit()
>   command-line-1(("-l" "package" "--eval" "(add-to-list 'package-direc
>   command-line()
>   normal-top-level()
> Test highlights-all-delimiters condition:
> (ert-test-failed
>  ((should
>(ert-equal-including-properties
>   (progn ... ...)
>   #("foo x;" 0 3 ... 3 4 ... 4 7 ... 7 8 ... 9 10 ...)))
>   :form
>   (ert-equal-including-properties
>#("foo x;" 0 3
>(face font-lock-type-face)
>3 4
>(face ... c-<>-c-types-set t)
>4 7
>(face font-lock-type-face)
>7 8
>(face ...)
>9 10
>(face font-lock-variable-name-face))
>#("foo x;" 0 3
>(face font-lock-type-face)
>3 4
>(face ...)
>4 7
>(face font-lock-type-face)
>7 8
>(face ...)
>9 10
>(face font-lock-variable-name-face)))
>   :value nil :explanation
>   (char 3 "<"
>   (different-properties-for-key c-<>-c-types-set
> (different-atoms t nil))
>   context-before "foo" context-after "int> x;")))
>FAILED  14/24  highlights-all-delimiters (0.048558 sec) at 
> rainbow-delimiters-test.el:144
>passed  15/24  

Bug#1050388: marked as done (canu: autopkgtest generates unreasonably large artifacts)

[Debian Bug Tracking System]

Your message dated Thu, 19 Oct 2023 08:57:11 +0200
with message-id 
and subject line Close: canu: autopkgtest generates unreasonably large artifacts
has caused the Debian Bug report #1050388,
regarding canu: autopkgtest generates unreasonably large artifacts
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.)


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

Source: canu
Version: 2.2+dfsg-3
Severity: serious
User: debian...@lists.debian.org
Usertags: other

Dear maintainer(s),

Your package has an autopkgtest, great. However, it breaks the 
infrastructure. In the last version upload to unstable, the package 
started to save unreasonably large files as artifacts:


root@ci-worker13:/tmp/debci-worker-37061072-xELMvGodQM/autopkgtest-incoming/unstable/amd64/c# 
du -h --max-depth=0 canu/

256Mcanu/

which is more than our communication infrastructure can handle. Yes, 
we'll implement sane handling, but at the moment this test breaks the 
ci.d.n infrastructure. I have therefore put the package on our reject 
list, until either this bug is fixed, or our tooling handles this better.


Paul


OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Closing this bug since the issue seems to be solved.


-- 
http://fam-tille.de--- End Message ---

Processed: Re: src:canu: fails to migrate to testing for too long: unresolved RC issue

[Debian Bug Tracking System]

Processing control commands:

> tags -1 upstream
Bug #1052347 {Done: Paul Gevers } [src:canu] src:canu: fails 
to migrate to testing for too long: unresolved RC issue
Added tag(s) upstream.
> forwarded -1 https://github.com/marbl/canu/issues/2271
Bug #1052347 {Done: Paul Gevers } [src:canu] src:canu: fails 
to migrate to testing for too long: unresolved RC issue
Set Bug forwarded-to-address to 'https://github.com/marbl/canu/issues/2271'.

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

Bug#1052347: src:canu: fails to migrate to testing for too long: unresolved RC issue

[Andreas Tille]

Control: tags -1 upstream
Control: forwarded -1 https://github.com/marbl/canu/issues/2271