Bug#1039617: liblopsub: reproducible-builds: timestamps in gzip headers for changelog and manpage

[Andre Noll]

On Thu, Jun 29, 19:45, Andre Noll wrote

> > It also needs someone to upload to Debian. Looks like Adam Borowski
> >  has sponsored in the past, but if you need someone
> > else to sponsor the upload, I could too.
> 
> Yes, Adam uploaded all previous versions so far. But of course it's
> also fine if you sponsor the upload this time.

Could either of you please upload v1.0.4 (released on Jun 28th)?

Thanks
Andre
-- 
Max Planck Institute for Biology
Tel: (+49) 7071 601 829
Max-Planck-Ring 5, 72076 Tübingen, Germany
http://people.tuebingen.mpg.de/maan/


signature.asc
Description: PGP signature

Bug#1040700: kleopatra: Depends upon pinentry-qt instead of pinentry

[Lisandro Damián Nicanor Pérez Meyer]

Package: kleopatra
Version: 4:22.12.3-1
Severity: normal
X-Debbugs-Cc: lisan...@debian.org

Hi! kleopatra has a direct dependency on pinentry-qt instead of
pinentry. The problem with this is that people wanting to use any other
pinentry fronted are forced to install the Qt version.

The correct solution for this would be to replace the dependency with
pinentry and move pinentry-qt as Recommends, thus giving the Qt version
a chance but allowing users to use any other variant, like the curses or
gtk one.


-- System Information:
Debian Release: 12.0
  APT prefers buildd-unstable
  APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (500, 'testing'), 
(1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64

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

Versions of packages kleopatra depends on:
ii  dirmngr  2.2.40-1.1
ii  gnupg2.2.40-1.1
ii  gpgsm2.2.40-1.1
ii  libassuan0   2.5.5-5
ii  libc62.36-9
ii  libgcc-s112.2.0-14
ii  libgpg-error01.46-1
ii  libgpgme11   1.18.0-3+b1
ii  libgpgmepp6  1.18.0-3+b1
ii  libkf5akonadimime5 [libkf5akonadimime5-22.12]4:22.12.3-1
ii  libkf5codecs55.103.0-1
ii  libkf5configcore55.103.0-2
ii  libkf5configgui5 5.103.0-2
ii  libkf5configwidgets5 5.103.0-1
ii  libkf5coreaddons55.103.0-1
ii  libkf5crash5 5.103.0-1
ii  libkf5dbusaddons55.103.0-1
ii  libkf5i18n5  5.103.0-1
ii  libkf5iconthemes55.103.0-1
ii  libkf5identitymanagement5 [libkf5identitymanagement5-22.12]  22.12.3-1
ii  libkf5itemmodels55.103.0-1
ii  libkf5libkleo5 [libkf5libkleo5-22.12]4:22.12.3-1
ii  libkf5mailtransport5 [libkf5mailtransport5-22.12]22.12.3-1
ii  libkf5mailtransportakonadi5 [libkf5mailtransportakonadi5-22  22.12.3-1
.12]
ii  libkf5mime5abi1 [libkf5mime5-22.12]  22.12.3-1
ii  libkf5notifications5 5.103.0-1
ii  libkf5textwidgets5   5.103.0-1
ii  libkf5widgetsaddons5 5.103.0-1
ii  libkf5windowsystem5  5.103.0-1
ii  libkf5xmlgui55.103.0-1
ii  libqgpgme15  1.18.0-3+b1
ii  libqt5core5a 5.15.8+dfsg-12
ii  libqt5dbus5  5.15.8+dfsg-12
ii  libqt5gui5   5.15.8+dfsg-12
ii  libqt5network5   5.15.8+dfsg-12
ii  libqt5printsupport5  5.15.8+dfsg-12
ii  libqt5widgets5   5.15.8+dfsg-12
ii  libstdc++6   12.2.0-14
ii  paperkey 1.6-1
ii  pinentry-qt  1.2.1-1

Versions of packages kleopatra recommends:
ii  breeze-icon-theme  4:5.103.0-1

kleopatra suggests no packages.

-- no debconf information

Bug#1038988: qt6-multimedia: Patch to build with system egein3

[Lisandro Damian Nicanor Perez Meyer]

Hi!

On sábado, 24 de junio de 2023 03:42:33 -03 Christian Marillat wrote:
> Source: qt6-multimedia
> Version: 6.4.2-5
> Severity: normal
> 
> Dear Maintainer,
> 
> Please find bellow a debdiff to build qt6-multimedia with system
> eigen3
> 
> Changes are:
>   Add libeigen3-dev to Build-Depends
>   Add a pacth to changes the cinclude path ../3rdparty/eigen to
> /usr/include/eigen3 in src/spatialaudio/CMakeLists.txt and
> src/resonance-audio/CMakeLists.txt

Thanks for your patch! to be totally honest I missed it yesterday while doing 
a Multimedia upload, my bad.

The patch looks really good, but I also just noticed that eigen3 provides both 
cmake and pkg-config files, so ideally we should try to use that. No, I'm not 
asking you to do it, I'll tyr to give it a go.

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

Bug#1040698: debian-reference: bad sentence

[so6rqs+sgc6clzjb7y4]

Package: debian-reference
Severity: normal

Dear Maintainer,

The english version of debian reference contains this sentence at the end of 
section 8.1.2:

`The locales-all package comes with all locale data pre-compiled but doesn't 
creating "/etc/default/locale".`

The meaning of the sentence is not clear because of the wording, please reword.

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

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

Versions of packages debian-reference depends on:
pn  debian-reference-en  

Versions of packages debian-reference recommends:
pn  debian-reference-de 
pn  debian-reference-es 
pn  debian-reference-fr 
pn  debian-reference-id 
pn  debian-reference-it 
pn  debian-reference-ja 
pn  debian-reference-pt 
pn  debian-reference-zh-cn  
pn  debian-reference-zh-tw  

debian-reference suggests no packages.

Bug#1040001: Role of tibble? (Was: Bug#1040001: Seeking advise how to proceed with the transition / move R stack to testing)

[Andreas Tille]

Am Sat, Jul 08, 2023 at 10:35:17PM +0200 schrieb Paul Gevers:
> Indeed, I think the pattern is that if we test in testing, with r-cran from
> unstable and r-cran-tibble from testing it fails, but with r-cran from
> unstable and r-cran-tibble from unstable, it works.
> 
> I'm working my through the list and the ppc64el ci workers have a bit of
> backlog; we're getting somewhere, but I'm think I'm still also seeing
> different failure modes than the graphics engine, tibble and dplyr.

I admit the only chance I personally see to clarify this question is to
open an issue at the tibble git repository[1].  May be we also need
something like an r-cran-tibble-api?

Kind regards
Andreas.

[1] https://github.com/tidyverse/tibble

-- 
http://fam-tille.de

Bug#1040689: List of emacs related packages installed

[Balbir Thomas]

As requested I am listing below all Emacs related
packages installed. These list was generated using
"dpkg --get-selections" and grepping for "emacs" and
"elpa".


emacs
emacs-bin-common
emacs-common
emacs-common-non-dfsg
emacs-el
emacs-goodies-el
emacs-gtk
emacsen-common
maxima-emacs
dh-elpa-helper
elpa-apache-mode
elpa-async
elpa-bar-cursor
elpa-bm
elpa-boxquote
elpa-browse-kill-ring
elpa-color-theme-modern
elpa-company
elpa-csv-mode
elpa-dash
elpa-deferred
elpa-diminish
elpa-eproject
elpa-ess
elpa-esxml
elpa-folding
elpa-graphviz-dot-mode
elpa-helm
elpa-helm-core
elpa-htmlize
elpa-initsplit
elpa-js2-mode
elpa-markdown-mode
elpa-mutt-alias
elpa-muttrc-mode
elpa-org
elpa-org-contrib
elpa-pod-mode
elpa-popup
elpa-s
elpa-session
elpa-simple-httpd
elpa-tabbar
elpa-xcscope

Bug#1040697: RM: abyss [s390x] -- ROM; unsatisfiable Build-Depends on s390x: libbtllib-dev

[Étienne Mollier]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: ab...@packages.debian.org
Control: affects -1 + src:abyss

Hi ftpmaster,

The package abyss has unsatisfiable Build-Depends on s390x, due
to missing libbtllib-dev.  Please kindly remove abyss from that
architecture.

I leave the d/control information unchanged, so that abyss has a
chance to go back to s390x in case btllib were to support s390x
in the future once again.

Have a nice day,  :)
-- 
  .''`.  Étienne Mollier 
 : :' :  gpg: 8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
 `. `'   sent from /dev/pts/6, please excuse my verbosity
   `-on air: Focus - Eruption


signature.asc
Description: PGP signature

Bug#1040472: p11-kit FTCBFS: AC_RUN_IFELSE

[Andreas Metzler]

On 2023-07-06 Helmut Grohne  wrote:
> Source: p11-kit
[...]
> - [AC_RUN_IFELSE(
> + [AC_CACHE_CHECK([strerror_r return 
> value],[ac_cv_strerror_r_ret],[
> +  AC_RUN_IFELSE(
>   [AC_LANG_SOURCE([[
>   #include 
>   #include 
> @@ -178,10 +179,13 @@
>   return strerror_r (EINVAL, buf, 32);
>   }
>   ]])],
> + [ac_cv_strerror_r_ret=xsi],
> + [ac_cv_strerror_r_ret=gnu],
> + [ac_cv_strerror_r_ret=cross])])
> +  dnl Guess that we cross build on glibc
> +  AS_IF([test "$ac_cv_strerror_r_ret" = xsi],
>  [AC_DEFINE([HAVE_XSI_STRERROR_R], 1, [Whether 
> XSI-compliant strerror_r() is available])],
> - [AC_DEFINE([HAVE_GNU_STRERROR_R], 1, [Whether 
> GNU-specific strerror_r() is available])],
> - [])],
> - [])
> + [AC_DEFINE([HAVE_GNU_STRERROR_R], 1, [Whether 
> GNU-specific strerror_r() is available])])])

>   AC_CACHE_CHECK([for thread-local storage class],
>   [ac_cv_tls_keyword],

Hello Helmut,

thanks.

I guess this should read 
AS_IF([test "$ac_cv_strerror_r_ret" = cross],

instead of

AS_IF([test "$ac_cv_strerror_r_ret" = xsi],

?

Also wouldn't using AC_FUNC_STRERROR_R be a better fix? (I do not expect
you to provide this, I asking for your opinion)

TIA, cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1040696: kbd: setfont doesn't set a default font

[Sven Grewe]

Package: kbd
Version: 2.5.1-1+b1
Severity: important
X-Debbugs-Cc: svengr...@posteo.de

Dear Maintainer,

If I type setfont into the console, I expect it to use the default font as
the manual says. It gives an error instead:

$ LANG=CC setfont
Couldn't get a file descriptor referring to the console.



-- System Information:
Debian Release: 12.0
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-9-amd64 (SMP w/2 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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 kbd depends on:
ii  libc6  2.36-9

Versions of packages kbd recommends:
ii  console-setup  1.221

kbd suggests no packages.

-- no debconf information

Bug#1040695: libvidstab: New upstream release (v1.1.1, 2022 May 30)

[Florian Ernst]

Source: libvidstab
Version: 1.1.0-2
Severity: wishlist

Dear maintainer,

there is a new upstream release available, cf.

(as referenced from
).

Please update the packaging when you think it is due time.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#1040689: Workaround without init and site file

[Balbir Thomas]

Thanks to bremner on IRC it was found that
launching emacs disabling the init and site lisp file
("emacs -Q") seems to fix the issue i.e. org-export-dispatch
does work and and exported file is generated.

regards

Bug#1040694: Segfault in CbcModel::initialSolve

[Pierre Gruet]

Source: coinor-cbc
Version: 2.10.10+ds1-1
Severity: important
X-Debbugs-Cc: schuel...@phimeca.com

Dear Maintainer,

Starting from version 2.10.10+ds1-1 (2.10.8+ds1-1 was OK), one of the
build-time tests of openturns started to fail: t_Bonmin_std. Running it with
gdb I get:

--->8

(gdb) run
Starting program: 
/build/openturns-eQ5lBV/openturns-1.20/builddir/lib/test/t_Bonmin_std
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
class=Bonmin
algorithm=B-BB
options=
mu_oracle=loqo


Program received signal SIGSEGV, Segmentation fault.
0x71ce1347 in CbcModel::initialSolve() () from 
/usr/lib/x86_64-linux-gnu/libCbc.so.3
(gdb) bt
#0  0x71ce1347 in CbcModel::initialSolve() () from 
/usr/lib/x86_64-linux-gnu/libCbc.so.3
#1  0x748a2705 in Bonmin::Bab::branchAndBound(Bonmin::BabSetupBase&) () 
from /usr/lib/x86_64-linux-gnu/libbonmin.so.4
#2  0x7755b48e in OT::Bonmin::run (this=this@entry=0x7fffe440) at 
./lib/src/Base/Optim/Bonmin.cxx:174
#3  0xf285 in main () at ./lib/test/t_Bonmin_std.cxx:131

--->8 

which indicates a problem in coinor-cbc.
The above backtrace is somewhat reminiscent of the one of the issue
https://github.com/coin-or/Cbc/issues/591
which has been fixed in upstream version 2.10.10. I suspect a close issue is
showing up here.

Thanks a lot for your help,

-- 
Pierre

Bug#1037190: closed by Debian FTP Masters (reply to Martin-Éric Racine ) (Bug#1037190: fixed in dhcpcd 10.0.1-1)

[Martin-Éric Racine]

On Sat, Jul 8, 2023 at 12:57 PM Martin-Éric Racine
 wrote:
>
> On Sat, Jul 8, 2023 at 12:42 PM Andreas Beckmann  wrote:
> > Thanks for fixng it in sid. Please backport the epoch related changes to
> > src:dhcpcd5 and get this fix into bookworm-pu over the next week s.t. it
> > can be included in the first point release.
>
> Welcome.
>
> I'm still missing the dhcpcd.preinst patch you submitted. I was
> waiting for 10.0.1-1, which was already sitting in NEW, to get
> accepted into the archive to merge it. I can do this now.

The preinst in included in 10.0.1-2 and waiting on Mentors.

> For bookworm-pu, I welcome feedback on any other cherry-pick since
> 9.4.1-22 that would be worth including. I'll also need a sponsor to
> ensure timely upload for Bookworm's point release.

If you have a debdiff for Bookworm, please attach it to this bug.

Martin-Éric

Bug#1040639: transition: rocksdb

[Sebastian Ramacher]

Control: tags -1 confirmed

On 2023-07-08 11:30:45 +0200, László Böszörményi wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> Control: affects -1 + src:rocksdb
> Control: forwarded -1
> https://release.debian.org/transitions/html/auto-rocksdb.html
> 
> Hi RMs,
> 
> Small transition for RocksDB as only two reverse dependencies are in
> the archives: balboa and sortmerna.

Please go ahead

Cheers.
-- 
Sebastian Ramacher

Bug#1039934: gcc-12: __builtin_cpu_supports does not detect SSE2 on VIA CPU, patch available

[Matthias Klose]

Version: 12.3.0-5

at least fixed in 12.3.0-5

Bug#1040693: less: sleeps with 100% CPU on specific search, all signals blocked

[наб]

Package: less
Version: 590-2
Severity: normal

Dear Maintainer,

I'm attaching p23.zst; doing less p23, /\b675\b, then enter,
sleeps less forever while using 100% CPU and with all signals blocked
(incl. SIGINT, SIGKILL, SIGWINCH, SIGHUP, ).
It only responds to SIGKILL.

It appears to be reading for a while, but then strace starts being
empty (to the continued tune of 100% CPU).

Best,
наб

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

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

Versions of packages less depends on:
ii  libc6  2.36-9
ii  libtinfo6  6.4-4

less recommends no packages.

less suggests no packages.

-- no debconf information


p23.zst
Description: application/zstd


signature.asc
Description: PGP signature

Bug#1040692: RFS: ipmiutil/3.1.9-2 -- IPMI management utilities

[Jörg Frings-Fürst]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "ipmiutil":

   Package name : ipmiutil
   Version  : 3.1.9-2
   URL  : https://sourceforge.net/projects/ipmiutil/
   License  : Zlib, GPL-2+, BSD-2-clause, Artistic-2.0, BSD-3-clause, 
  GPL-2+ with OpenSSL exception
   Vcs  : https://git.jff.email/cgit/ipmiutil.git
   Section  : utils

The source builds the following binary packages:

  ipmiutil - IPMI management utilities

To access further information about this package, please visit the following
URL:

  https://mentors.debian.net/package/ipmiutil/

Alternatively, you can download the package with 'dget' using this command:

 dget -x 
https://mentors.debian.net/debian/pool/main/i/ipmiutil/ipmiutil_3.1.9-2.dsc

or from 

 git https://git.jff.email/cgit/ipmiutil.git?h=release%2Fdebian%2F3.1.9-2

 git https://jff.email/cgit/ipmiutil.git?h=release%2Fdebian%2F3.1.9-2



Changes since the last upload:

 ipmiutil (3.1.9-2) unstable; urgency=medium
 .
   * New debian/patches/0110-fix_malformed_messages.patch (Closes: #1040349).
   * debian/control:
 - Change Vcs-* to new URL.

CU
Jörg


-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56


Jörg Frings-Fürst
D-54470 Lieser


git:  https://git.jff.email/cgit/

Skype:jff-skype@jff.email
Jami: joergfringsfuerst
Telegram: @joergfringsfuerst
Matrix:   @joergff:matrix.snct-gmbh.de

My wish list: 
 - Please send me a picture from the nature at your home.






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

Bug#1040682: FTBFS in colord with meson 1.2.0 rc2

[Eli Schwartz]

Control: severity -1 important


Helmut Grohne clarified that the "serious" severity should not be set
for packages that only fail with the new meson, since "the autoremover
will act on serious bugs and we don't want that to happen just yet".

The meson release candidates are only ever uploaded to experimental, and
are a preview for the future. Temporarily downgrading the severity. This
should be reset to "serious" once the final release is out, as which
will go directly to unstable.

-- 
Eli Schwartz

Bug#1021894: openjfx: FTBFS on arm64 and armhf

[Pierre Gruet]

Control: affects -1 src:libjogl2-java src:beast2-mcmc
Control: severity -1 serious

Hi,

I am restoring the severity of this FTBFS bug, which has concrete 
consequences on several packages.


Cheers,

--
Pierre


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1014193: This hit me on upgrade to bookworm

[Richard Lewis]

After upgrading to bookworm, encfs segfaults for me when trying to
open encrypted directories created a long time ago.

The solution in
https://askubuntu.com/questions/1405656/encfs-segfault-in-version-22-04
worked, which is to edit /etc/ssl/opensslf.conf and add

[openssl_init]
providers = provider_sect

# List of providers to load
[provider_sect]
default = default_sect
legacy = legacy_sect

[default_sect]
activate = 1

[legacy_sect]
activate = 1

It would be great to document this in NEWS.Debian as this worked fine
in bullseye

enfsctl info says:
 Version 5 configuration; created by EncFS 1.2.5 (revision 20040813)
 Filesystem cipher: "ssl/blowfish", version 2:1:1 (using 3:0:2)

Bug#1040690: emacs-el: Warnings resulting from org-mode source files not found

[Balbir Thomas]

Package: emacs-el
Version: 1:28.2+1-15
Severity: normal

Dear Maintainer,

On starting emacs 28 in bookworm various warnings are displayed because
elisp source files (mostly for) org-mode are not found. 

There are broken symlinks to source files in the directory 
/usr/share/emacs/site-lisp/elpa/org-9.4/
The symlinks point to files in the directory 
/usr/share/emacs/site-lisp/elpa-src/org-9.4/ which
does not exist.

Listed below are the warning messages
-

Warning (comp): Cannot look-up eln file as no source file was found for 
/usr/share/emacs/site-lisp/elpa/dash-2.17.0/dash.elc Disable showing Disable 
logging
Warning (comp): Cannot look-up eln file as no source file was found for 
/usr/share/emacs/site-lisp/elpa/esxml-0.3.5/esxml-query.elc Disable showing 
Disable logging
Warning (comp): Cannot look-up eln file as no source file was found for 
/usr/share/emacs/site-lisp/elpa/org-9.4/org.elc Disable showing Disable logging
Warning (comp): Cannot look-up eln file as no source file was found for 
/usr/share/emacs/site-lisp/elpa/org-9.4/org-macs.elc Disable showing Disable 
logging
Warning (comp): Cannot look-up eln file as no source file was found for 
/usr/share/emacs/site-lisp/elpa/org-9.4/org-compat.elc Disable showing Disable 
logging
Warning (comp): Cannot look-up eln file as no source file was found for 
/usr/share/emacs/site-lisp/elpa/org-9.4/org-keys.elc Disable showing Disable 
logging
Warning (comp): Cannot look-up eln file as no source file was found for 
/usr/share/emacs/site-lisp/elpa/org-9.4/ol.elc Disable showing Disable logging
Warning (comp): Cannot look-up eln file as no source file was found for 
/usr/share/emacs/site-lisp/elpa/org-9.4/org-table.elc Disable showing Disable 
logging
Warning (comp): Cannot look-up eln file as no source file was found for 
/usr/share/emacs/site-lisp/elpa/org-9.4/ob-emacs-lisp.elc Disable showing 
Disable logging
Warning (comp): Cannot look-up eln file as no source file was found for 
/usr/share/emacs/site-lisp/elpa/org-9.4/ob-core.elc Disable showing Disable 
logging
Warning (comp): Cannot look-up eln file as no source file was found for 
/usr/share/emacs/site-lisp/elpa/org-9.4/ob-eval.elc Disable showing Disable 
logging
Warning (comp): Cannot look-up eln file as no source file was found for 
/usr/share/emacs/site-lisp/elpa/org-9.4/org.elc Disable showing Disable logging
Warning (comp): Cannot look-up eln file as no source file was found for 
/usr/share/emacs/site-lisp/elpa/org-9.4/org-entities.elc Disable showing 
Disable logging
Warning (comp): Cannot look-up eln file as no source file was found for 
/usr/share/emacs/site-lisp/elpa/org-9.4/org-faces.elc Disable showing Disable 
logging
Warning (comp): Cannot look-up eln file as no source file was found for 
/usr/share/emacs/site-lisp/elpa/org-9.4/org-list.elc Disable showing Disable 
logging
Warning (comp): Cannot look-up eln file as no source file was found for 
/usr/share/emacs/site-lisp/elpa/org-9.4/org-pcomplete.elc Disable showing 
Disable logging
Warning (comp): Cannot look-up eln file as no source file was found for 
/usr/share/emacs/site-lisp/elpa/org-9.4/org-src.elc Disable showing Disable 
logging
Warning (comp): Cannot look-up eln file as no source file was found for 
/usr/share/emacs/site-lisp/elpa/org-9.4/ob-comint.elc Disable showing Disable 
logging
Warning (comp): Cannot look-up eln file as no source file was found for 
/usr/share/emacs/site-lisp/elpa/org-9.4/org-footnote.elc Disable showing 
Disable logging
Warning (comp): Cannot look-up eln file as no source file was found for 
/usr/share/emacs/site-lisp/elpa/org-9.4/org-macro.elc Disable showing Disable 
logging
Warning (comp): Cannot look-up eln file as no source file was found for 
/usr/share/emacs/site-lisp/elpa/org-9.4/ob.elc Disable showing Disable logging
Warning (comp): Cannot look-up eln file as no source file was found for 
/usr/share/emacs/site-lisp/elpa/org-9.4/ob-exp.elc Disable showing Disable 
logging
Warning (comp): Cannot look-up eln file as no source file was found for 
/usr/share/emacs/site-lisp/elpa/org-9.4/ob-table.elc Disable showing Disable 
logging
Warning (comp): Cannot look-up eln file as no source file was found for 
/usr/share/emacs/site-lisp/elpa/org-9.4/ob-lob.elc Disable showing Disable 
logging
Warning (comp): Cannot look-up eln file as no source file was found for 
/usr/share/emacs/site-lisp/elpa/org-9.4/ob-ref.elc Disable showing Disable 
logging
Warning (comp): Cannot look-up eln file as no source file was found for 
/usr/share/emacs/site-lisp/elpa/org-9.4/ob-tangle.elc Disable showing Disable 
logging
Warning (comp): Cannot look-up eln file as no source file was found for 
/usr/share/emacs/site-lisp/elpa/org-9.4/ob-R.elc Disable showing Disable logging
Warning (comp): Cannot look-up eln file as no source file was found for 
/usr/share/emacs/site-lisp/elpa/org-9.4/ob-shell.elc Disable showing Disable 
logging
Warning (comp): Cannot look-up eln file as no source file was found 

Bug#1040689: elpa-org: Org export fails

[Balbir Thomas]

Package: elpa-org
Version: 9.5.2+dfsh-5
Severity: normal

Dear Maintainer,

Trying export any org-mode file leads to the error :

"wrong type argument: commandp, org-export-dispatch"

This happens with or without any local emacs configuration (.emacs
file).


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

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

Versions of packages elpa-org depends on:
ii  elpa-htmlize   1.56-1
ii  emacs  1:28.2+1-15
ii  emacs-gtk [emacs]  1:28.2+1-15

elpa-org recommends no packages.

Versions of packages elpa-org suggests:
pn  ditaa  
ii  org-mode-doc   9.5.2-1
ii  texinfo6.8-6+b1
ii  texlive-fonts-recommended  2022.20230122-3
ii  texlive-latex-extra2022.20230122-4

-- no debconf information

Bug#1040519: bookworm-pu: package samba/2:4.17.9+dfsg-0+deb12u1

[Michael Tokarev]

09.07.2023 10:05, Michael Tokarev wrote:
...

Now after thought about all this in the morning, I think the following should
do it:

diff --git a/debian/changelog b/debian/changelog
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+samba (2:4.17.9+dfsg-0+deb12u2) bookworm; urgency=medium
+
+  * link with -latomic explicitly on a few architectures where gcc misses it
+    (notable armel & mipsel), to fix FTBFS there, - the same as on sid.
+    https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81358
+
+ -- Michael Tokarev   Sun, 09 Jul 2023 09:44:29 +0300
+
  samba (2:4.17.9+dfsg-0+deb12u1) bookworm-proposed-updates; urgency=medium

    * d/copyright: filter out autogenerated manpages from the upstream source
diff --git a/debian/rules b/debian/rules
--- a/debian/rules
+++ b/debian/rules
@@ -103,6 +103,20 @@ with-ceph =
  with-glusterfs =
  endif

+ifneq (,$(filter armel mipsel m68k powerpc sh4,${DEB_HOST_ARCH}))
+# https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81358
+# on these platforms gcc does not link with -latomic, resulting in
+#   third_party/heimdal/lib/krb5/krcache.c.55.o: in function 
`krcc_get_principal':
+#   third_party/heimdal/lib/krb5/krcache.c:1395: undefined reference to 
`__atomic_load_8'
+# ids.krcu_cache_and_princ_id = 
heim_base_atomic_load(>krc_cache_and_principal_id);
+#   third_party/heimdal/lib/base/heimbase-atomics.h:
+# #include 
+# #define heim_base_atomic_load(x)    atomic_load((x))
+# include a workaround for now
+# (-latomic and  comes from gcc, --as-needed is already in use)
+LDFLAGS := ${LDFLAGS} -latomic
+endif
+
  config-args += $(if ${with-ceph},\
   --enable-cephfs --enable-ceph-reclock,\
   --disable-cephfs)

(this is the same changes as on sid, *plus* a bit more, which updates the 
comment
with the gcc bug reference and drops -Wl,--no-as-needed, - since this one is 
already
enabled).


So I built this on armel and mipsel (and on amd64 too) and verified it works 
fine.
Uploading the fixed package (with the above diff from -0+deb12u1) now, feel 
free to
accept it as the fix for the previous broken upload.

Thank you for your time!

/mjt

Bug#1032289: libdiplay-info: Keep out of the Bookworm release

[duck]

Quack,

On 2023-07-08 01:30, Jeremy Bícha wrote:


Could you upload the version from Experimental to Unstable?


I just got back Pond and checked if there was a new version first; no 
luck with that but I uploaded the version in experimental in unstable 
and it just got ACCEPTED, enjoy.


\_o<

--
Marc Dequènes

Bug#1040688: wx3.2-examples: Some examples do not compile

[joel]

Package: wx3.2-examples
Version: 3.2.2+dfsg-2
Severity: normal
X-Debbugs-Cc: j.o.elpub...@gmail.com

Dear Maintainer,

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

   * What led up to the situation?
Tried to compile examples to understand wx-config flags.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Installed a clean debian VM.
Installed wx3.2-examples and the suggested libwxgtk3.2-dev + g++ and make
Copied /usr/share/doc/wx3.2-examples/examples/samples to a writable dir.
make
# failed
Iterate over each directory and make in each. 
Some are windows only and generate compile errors, but I have omitted
those.

   * What was the outcome of this action?
The following did not compile due to link errors:
archive
console
ipc
sockets

--
eg:
/usr/bin/ld: console_console.o: warning: relocation against 
`_ZTV17wxMDIClientWindow' in read-only section 
`.text._ZN17wxMDIClientWindowC2Ev[_ZN17wxMDIClientWindowC5Ev]'
/usr/bin/ld: console_console.o: in function `wxWindowBase::GetBestVirtualSize() 
const':
console.cpp:(.text._ZNK12wxWindowBase18GetBestVirtualSizeEv[_ZNK12wxWindowBase18GetBestVirtualSizeEv]+0x25):
 undefined reference to `wxWindowBase::GetBestSize() const'
/usr/bin/ld: console_console.o: in function `wxWindowBase::CanBeFocused() 
const':
...

   * What outcome did you expect instead?
I expected it to compile.

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

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

wx3.2-examples depends on no packages.

wx3.2-examples recommends no packages.

Versions of packages wx3.2-examples suggests:
ii  libwxgtk3.2-dev  3.2.2+dfsg-2
pn  wx3.2-doc

-- no debconf information

Bug#1040687: imagemagick-6.q16: HEIC/HEIF files cannot be opened by convert-img6.q16 and display-im6.q16

[Dai Maru]

Package: imagemagick-6.q16
Version: 8:6.9.11.60+dfsg-1.6
Severity: normal

Dear Maintainer,

After updateing imagemagic-6.q16 6.9.11.60-dfsg-1.6 (sorry I forget the verson 
which correctly worked),
convert-im6.q16 and dispaly-im6.q16 cannot read HEIC/HEIF files generated by 
iPhone.

displaye-im6.q16 cannot open HEIC/HEIF files.
When I tried following command,

  $ display-im6.q16 2023-07-02_09-49-17_IMG_2168.HEIC

As a result, the LOG image are shown.

In addtion convert-im6.q16 cannat read convert from HEIC/HECI files.
When I tried following command,

  $ convert-im6.q16 2023-07-02_09-49-17_IMG_2168.HEIC 
2023-07-02_09-49-17_IMG_2168.HEIC.JPG.

following message is shown.

  convert-im6.q16: no images defined `2023-07-02_09-49-17_IMG_2168.HEIC.JPG' @ 
error/convert.c/ConvertImageCommand/3229.

On the other hand, identify-im6.q16 command seems to be worked correctly.
Whe I tried following command,

  $ identify-im6.q16 2023-07-02_09-49-17_IMG_2168.HEIC

follwoing message is shown.

  2023-07-02_09-49-17_IMG_2168.HEIC HEIC 3024x4032 3024x4032+0+0 8-bit YCbCr 
0.010u 0:00.010

In addition, I tried the experimental package (6.9.12.20+dfsg1-1.2) and it was 
not work correctly, too.

I attached the sample HEIC file, please confirm.


Regards,

-- Package-specific info:
ImageMagick program version
---
animate:  ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 https://imagemagick.org
compare:  ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 https://imagemagick.org
convert:  ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 https://imagemagick.org
composite:  ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 https://imagemagick.org
conjure:  ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 https://imagemagick.org
display:  ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 https://imagemagick.org
identify:  ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 https://imagemagick.org
import:  ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 https://imagemagick.org
mogrify:  ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 https://imagemagick.org
montage:  ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 https://imagemagick.org
stream:  ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 https://imagemagick.org

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

Kernel: Linux 6.3.0-2-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.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 imagemagick-6.q16 depends on:
ii  hicolor-icon-theme 0.17-2
ii  libc6  2.37-5
ii  libmagickcore-6.q16-6  8:6.9.11.60+dfsg-1.6
ii  libmagickwand-6.q16-6  8:6.9.11.60+dfsg-1.6

Versions of packages imagemagick-6.q16 recommends:
ii  ghostscript  10.01.2~dfsg-1
ii  libmagickcore-6.q16-6-extra  8:6.9.11.60+dfsg-1.6
ii  netpbm   2:11.01.00-2

Versions of packages imagemagick-6.q16 suggests:
pn  autotrace   
pn  cups-bsd | lpr | lprng  
ii  curl7.88.1-10
pn  enscript
ii  ffmpeg  7:5.1.3-1
ii  gimp2.10.34-1
ii  gnuplot 5.4.4+dfsg1-2
ii  gnuplot-qt [gnuplot]5.4.4+dfsg1-2+b2
pn  grads   
ii  graphviz2.42.2-7+b3
ii  groff-base  1.22.4-10
pn  hp2xx   
pn  html2ps 
pn  imagemagick-doc 
pn  libwmf-bin  
pn  mplayer 
pn  povray  
pn  radiance
ii  sane-utils  1.2.1-3
pn  texlive-base-bin
pn  transfig
pn  ufraw-batch 
ii  xdg-utils   1.1.3-4.1

-- no debconf information

Bug#770171: sshd jail fails when system solely relies on systemd journal for logging

[Nathaniel Mitchell]

Hi all,

Still an issue for the backend option being left on 'auto', could the
default for Debian be changed to use systemd as the backend?

(Fresh install on Bookworm).

Regards,

Nephi.Aust

Bug#1040349: ipmiutil: postinst script fails when "ipmiutil sel" works but "ipmiutil sensor" fails

[Jörg Frings-Fürst]

forwarded 1040349 https://github.com/arcress0/ipmiutil/issues/17
thanks

Hello Louis,

thank you for spending your time helping to make Debian better with this bug
report. 

I have the bug forwarded to upstream. A patch is currently in the works.

Am Dienstag, dem 04.07.2023 um 20:19 +0200 schrieb Louis Sautier:
> Package: ipmiutil
> Version: 3.1.8-4
> 
> Hi,
> 
> In some cases (Intel S2600STB boards), ipmiutil fails to install the 
> first time:
> Setting up ipmiutil (3.1.8-4) ...
> SDR record 61 is malformed, length 12 is less than minimum 12
> 0061 GetSDR error -25, rlen = 10
> dpkg: error processing package ipmiutil (--configure):
>   installed ipmiutil package post-installation script subprocess 
> returned error exit status 231
> Processing triggers for man-db (2.11.2-2) ...
> Errors were encountered while processing:
>   ipmiutil
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> 
> The second time around, it works because 
> /var/lib/ipmiutil/sensor_out.txt now exists.
> 
> The issue can be reproduced by removing /var/lib/ipmiutil/sensor_out.txt 
> and running the postinst script again (with -x added here to highlight 
> the problem):
> # dpkg-reconfigure ipmiutil
> + sbindir=/usr/bin
> + vardir=/var/lib/ipmiutil
> + sensorout=/var/lib/ipmiutil/sensor_out.txt
> + mkdir -p /var/lib/ipmiutil
> + IPMIcmd=true
> + /usr/bin/ipmiutil sel -v
> + true
> + [ ! -f /var/lib/ipmiutil/sensor_out.txt ]
> + /usr/bin/ipmiutil sensor -q
> SDR record 61 is malformed, length 12 is less than minimum 12
> 0061 GetSDR error -25, rlen = 10
> 
> The issue here is that "ipmiutil sel" works but "ipmi sensor" does not.
> https://jff.email/cgit/ipmiutil.git/tree/debian/postinst?h=debian/3.1.9-1#n16
> https://jff.email/cgit/ipmiutil.git/tree/debian/postinst?h=debian/3.1.9-1#n22
> 
> The fact that a failing "ipmiutil sensor" command prevents the 
> installation is problematic. Would it please be possible to make this 
> failure non-fatal?
> 
> https://bugs.launchpad.net/ubuntu/+source/ipmiutil/+bug/1786562 seems to 
> be the same issue, it concerns the same error message with an Intel 
> S2600STB.
> 
> 
> PS: maybe there is also an upstream ipmiutil bug to report here? "length 
> 12 is less than minimum 12" sounds like an off-by-one error.
> 
> Kind regards,
> 
> Louis


CU
Jörg

-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56


Jörg Frings-Fürst
D-54470 Lieser


git:  https://git.jff.email/cgit/

Skype:jff-skype@jff.email
Jami: joergfringsfuerst
Telegram: @joergfringsfuerst
Matrix:   @joergff:matrix.snct-gmbh.de

My wish list: 
 - Please send me a picture from the nature at your home.






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

Bug#1031828: debootstrap: Please document --usr-merge option in --help output

[Simon McVittie]

Control: tags -1 + patch
Control: forwarded -1 
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/94

On Fri, 24 Feb 2023 at 01:19:46 +0100, Santiago Vila wrote:
> So, if the buildds are still running non-usr-merged chroot, can you at least
> document the --usr-merge option which already exists?

The option is named --[no-]merged-usr, not --usr-merge, as documented in
debootstrap(8). I've sent a merge request to add it to --help as well.

> It will certainly be
> needed when creating chroots for trixie from bookworm

See also
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/93
which changes the default if neither --merged-usr nor --no-merged-user is
specified, and could be backported to bookworm when ready.

smcv

Bug#1031052: puma: flaky autopkgtest: It fails randomly.

[Aurelien Jarno]

Dear maintainers,

On 2023-02-11 00:00, Sebastian Andrzej Siewior wrote:
> Source: puma
> Version: 5.6.5-2
> Severity: important
> X-Debbugs-CC: debian...@lists.debian.org
> User: debian...@lists.debian.org
> Usertags: flaky
> 
> Dear maintainer(s),
> 
> Your package has an autopkgtest, great. However, it fails from time to
> time.
> From
>   https://ci.debian.net/packages/p/puma/testing/amd64/
> 
> openssl/3.0.8-1 failed
>   
> https://ci.debian.net/data/autopkgtest/testing/amd64/p/puma/31159611/log.gz
> openssl/3.0.8-1 passed
>   
> https://ci.debian.net/data/autopkgtest/testing/amd64/p/puma/31166222/log.gz
> 
> s390x, failed:
>   
> https://ci.debian.net/data/autopkgtest/testing/s390x/p/puma/31163926/log.gz
>   
> https://ci.debian.net/data/autopkgtest/testing/s390x/p/puma/31207049/log.gz
>   
> https://ci.debian.net/data/autopkgtest/testing/s390x/p/puma/31207176/log.gz
> 
> then passed
>   
> https://ci.debian.net/data/autopkgtest/testing/s390x/p/puma/31207506/log.gz
> 
> My understanding is that the error is a different in the three failures
> on s390x.
> 
> Could you please have a look?

As additional data points, it fails evens for the migration reference
run very close in time, so with the exact same set of packages:

success:
https://ci.debian.net/data/autopkgtest/testing/amd64/p/puma/35598630/log.gz

failure:
https://ci.debian.net/data/autopkgtest/testing/amd64/p/puma/35598629/log.gz

Could you please have a look? It's annoying for other maintainers to get
their package blocked by this one.

Regards
Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://aurel32.net

Bug#1040686: libpdfbox-java: Missing build dependency on lcdf-typetool OR extraneous other relation in debian/

[Theodoric Stier]

Source: libpdfbox-java
Version: 1:1.8.16-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source
X-Debbugs-Cc: kerd...@gmail.com

Dear Maintainer,

This package fails to build when lcdf-typetool is not installed, but
only during packaging. It appears not to be used during the build.
Maybe it's supposed to be a build dependency. If it isn't supposed to
be a build dependency, then the build should succeed without its presence.

Salutations,
Ted

-- System Information:
Debian Release: 12.0
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-9-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=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

Bug#1040685: systemd-cron: the MAILTO variable in /etc/crontab is not applied to generated cron units environments

[info]

Package: systemd-cron
Version: 1.15.21-1
Severity: normal

Dear Maintainer,

The /etc/crontab files allow to define enviroment variables (MAILTO among 
others) as per the man page.
This definition should be applied to all the cron defintions as a fallback.

The generator form this package parses /etc/crontab to identify jobs for 
generating the associated sytemd units.
When parsing files in cron.d, the MAILTO is inserted as Environment if 
explicitly defined.
But if it not defined, the generator does not include the fallback value from 
the /etc/crontab file.

The generator should parse /etc/crontab, retrieve MAILTO and maybe PATH or 
other env variables, and pass this fallback to the parsing of each file in 
cron.d or user crontabs.


Regards,


-- Package-specific info:
-- output of systemd-delta

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (600, 'stable'), (500, 'stable-security'), 
(500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 'unstable'), 
(200, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages systemd-cron depends on:
ii  cron-daemon-common  3.0pl1-162
ii  libc6   2.37-3
ii  python3 3.11.2-1+b1
ii  systemd [systemd-sysusers]  252.11-1
ii  systemd-sysv252.11-1

systemd-cron recommends no packages.

Versions of packages systemd-cron suggests:
ii  exim4  4.96-16
ii  exim4-daemon-heavy [mail-transport-agent]  4.96-16

-- debconf-show failed

Bug#1036978: node-undici 5.15.0+dfsg1+~cs20.10.9.3-1+deb12u1 flagged for acceptance

[Jonathan Wiltshire]

package release.debian.org
tags 1036978 = bookworm pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bookworm.

Thanks for your contribution!

Upload details
==

Package: node-undici
Version: 5.15.0+dfsg1+~cs20.10.9.3-1+deb12u1

Explanation: security fixes

Bug#1040623: bup 0.33.2-1~deb12u1 flagged for acceptance

[Jonathan Wiltshire]

package release.debian.org
tags 1040623 = bookworm pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bookworm.

Thanks for your contribution!

Upload details
==

Package: bup
Version: 0.33.2-1~deb12u1

Explanation: correctly restore POSIX ACLs

Bug#1040684: RFS: opendmarc/1.4.2-3 -- Domain-based Message Authentication, Reporting and Conformance (DMARC) milter

[David Bürgin]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "opendmarc":

 * Package name : opendmarc
   Version  : 1.4.2-3
   Upstream contact : The Trusted Domain Project
 * URL  : http://www.trusteddomain.org/opendmarc
 * License  : BSD-2-clause, BSD-3-clause and SOSL, GPL-3+ with AutoConf 
exception
 * Vcs  : https://salsa.debian.org/kitterman/opendmarc
   Section  : mail

The source builds the following binary packages:

  opendmarc - Domain-based Message Authentication, Reporting and Conformance 
(DMARC) milter
  libopendmarc2 - DMARC policy library
  libopendmarc-dev - DMARC policy library (development files)

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/opendmarc/

Alternatively, you can download the package with 'dget' using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/o/opendmarc/opendmarc_1.4.2-3.dsc

Changes since the last upload:

 opendmarc (1.4.2-3) unstable; urgency=medium
 .
   [ David Bürgin ]
   * debian/patches: Add missing upstream bug metadata, add new patches:
 - arcares-segfaults.patch: Fix segfaults in ARC-A-Res headers
 - parse-arc-leaks.patch: Fix memory leaks when parsing ARC headers
   * Update debian/watch to monitor GitHub tags instead of releases page
   * Remove obsolete debian/opendmarc.NEWS
   * Remove obsolete lsb-base dependency in opendmarc package
   * systemd: Enable some basic sandboxing features in opendmarc service
   * Bump Standards-Version to 4.6.2 without further change
 .
   [ Remus-Gabriel Chelu ]
   * [INTL:ro] Romanian debconf templates translation (Closes: #1033171)

Cheers,
David

Bug#1040563: bookworm-pu: package node-tough-cookie/4.0.0-2+deb12u1

[Yadd]

On 7/7/23 21:43, Jonathan Wiltshire wrote:

Control: tag -1 moreinfo

On Fri, Jul 07, 2023 at 09:01:40PM +0400, Yadd wrote:

[ Reason ]
node-tough-cookie is vulnerable to prototype pollution


How has this been fixed in unstable? You'll need an upload there anyway for
version ordering.

Thanks,


Hi,

upload already done in unstable

Cheers,

Bug#1036978: Upload window for 12.1 closing soon

[Jonathan Wiltshire]

Hi,

This request for bookworm has been approved but as yet no upload has been
observed. Please note that the approval window for 12.1 closes by 15th July
and your package should be uploaded and built by that date for inclusion.

Thanks,

-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51
ed25519/0x196418AAEB74C8A1: CA619D65A72A7BADFC96D280196418AAEB74C8A1

Bug#1039965: linux-image-6.1.0-9-amd64: crash on boot

[Salvatore Bonaccorso]

Control: tags -1 - moreinfo
Control: tags -1 + upstream

Hi Richard,

On Sat, Jul 08, 2023 at 09:16:35AM +, Richard Rahl wrote:
> After some further testing, I verified that it's an upstream bug, so
> will report something upstream, after I figured out which commit is
> to blame.

Ok that is good news at least, because it can help us move forward.

Let us know as well if you can isolate the breaking commit!

Regards,
Salvatore

Bug#1040683: bookworm-pu: package node-webpack/5.75.0+dfsg+~cs17.16.14-1+deb12u1

[Yadd]

Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: node-webp...@packages.debian.org
Control: affects -1 + src:node-webpack

[ Reason ]
node-webpack is vulnerable to cross-realm object access
(#1032904, CVE-2023-28154).

[ Impact ]
Medium security issue

[ Tests ]
Test updated, passed

[ Risks ]
Low risk, patch is trivial

[ Checklist ]
  [X] all changes are documented in the d/changelog
  [X] I reviewed all changes and I approve them
  [X] attach debdiff against the package in (old)stable
  [X] the issue is verified as fixed in unstable

Regards,
Yadd
diff --git a/debian/changelog b/debian/changelog
index 0053d7ee..a07dd9d4 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+node-webpack (5.75.0+dfsg+~cs17.16.14-1+deb12u1) bookworm; urgency=medium
+
+  * Team upload
+  * Avoid cross-realm objects (Closes: #1032904, CVE-2023-28154)
+
+ -- Yadd   Mon, 29 May 2023 07:53:16 +0400
+
 node-webpack (5.75.0+dfsg+~cs17.16.14-1) unstable; urgency=medium
 
   * Team upload
diff --git a/debian/patches/CVE-2023-28154.patch 
b/debian/patches/CVE-2023-28154.patch
new file mode 100644
index ..2f651167
--- /dev/null
+++ b/debian/patches/CVE-2023-28154.patch
@@ -0,0 +1,80 @@
+Description: avoid cross-realm objects
+Author: Jack Works 
+Origin: upstream, https://github.com/webpack/webpack/commit/4b4ca3bb
+Bug: https://www.cve.org/CVERecord?id=CVE-2023-28154
+Bug-Debian: https://bugs.debian.org/1032904
+Forwarded: not-needed
+Applied-Upstream: 5.76.1, commit:4b4ca3bb
+Reviewed-By: Yadd 
+Last-Update: 2023-05-29
+
+--- a/lib/dependencies/ImportParserPlugin.js
 b/lib/dependencies/ImportParserPlugin.js
+@@ -137,7 +137,7 @@
+   if (importOptions.webpackInclude !== undefined) 
{
+   if (
+   !importOptions.webpackInclude ||
+-  
importOptions.webpackInclude.constructor.name !== "RegExp"
++  !(importOptions.webpackInclude 
instanceof RegExp)
+   ) {
+   parser.state.module.addWarning(
+   new 
UnsupportedFeatureWarning(
+@@ -146,13 +146,13 @@
+   )
+   );
+   } else {
+-  include = new 
RegExp(importOptions.webpackInclude);
++  include = 
importOptions.webpackInclude;
+   }
+   }
+   if (importOptions.webpackExclude !== undefined) 
{
+   if (
+   !importOptions.webpackExclude ||
+-  
importOptions.webpackExclude.constructor.name !== "RegExp"
++  !(importOptions.webpackExclude 
instanceof RegExp)
+   ) {
+   parser.state.module.addWarning(
+   new 
UnsupportedFeatureWarning(
+@@ -161,7 +161,7 @@
+   )
+   );
+   } else {
+-  exclude = new 
RegExp(importOptions.webpackExclude);
++  exclude = 
importOptions.webpackExclude;
+   }
+   }
+   if (importOptions.webpackExports !== undefined) 
{
+--- a/lib/javascript/JavascriptParser.js
 b/lib/javascript/JavascriptParser.js
+@@ -3635,17 +3635,27 @@
+   return EMPTY_COMMENT_OPTIONS;
+   }
+   let options = {};
++  /** @type {unknown[]} */
+   let errors = [];
+   for (const comment of comments) {
+   const { value } = comment;
+   if (value && webpackCommentRegExp.test(value)) {
+   // try compile only if webpack options comment 
is present
+   try {
+-  const val = 
vm.runInNewContext(`(function(){return {${value}};})()`);
+-  Object.assign(options, val);
++  for (let [key, val] of Object.entries(
++  
vm.runInNewContext(`(function(){return {${value}};})()`)
++  )) {
++

Bug#1040519: bookworm-pu: package samba/2:4.17.9+dfsg-0+deb12u1

[Michael Tokarev]

09.07.2023 01:45, Adrian Bunk wrote:

On Sun, Jul 09, 2023 at 01:13:55AM +0300, Michael Tokarev wrote:

09.07.2023 01:01, Adrian Bunk wrote:

This does apparently need the -latomic workaround from 2:4.18.3+dfsg-3:
https://buildd.debian.org/status/package.php?p=samba=bookworm


Sigh!
This is the kerberos in-kernel tickets.. :(

I haven't realized until now that atomic8 thing come into the game after
I enabled the in-kernel kerberos tickets.  I was sure it was due to some
toolchain changes.


FTR, the underlying toolchain bug is not new:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81358


Now I know why we weren't able to reproduce this issue
with upstream, - because it happens in the code which is enabled by this
change.
...


The error message is a bit cryptic, but it basically says in which lines
in krcache.c the 64bit loads/stores are for which the CPU has no
instructions and needs libatomic.

Not linking with libatomic automatically for C11 atomics is the gcc bug.


Yeah, I know this is a gcc issue (though I haven't found the gcc bugreport
about this, - thank you for the link! - updated comments now).  I just didn't
connect the dots when it happened, - I didn't think my kerberos changes in
samba were the trigger for this issue to pop up, I thought it was somehting
else outside of samba (as you can see, the comments in d/rules in sid samba
package refers to this same place in source), - instead of realizing it is
due to me enabling new code which weren't used in samba before.

Now after thought about all this in the morning, I think the following should
do it:

diff --git a/debian/changelog b/debian/changelog
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+samba (2:4.17.9+dfsg-0+deb12u2) bookworm; urgency=medium
+
+  * link with -latomic explicitly on a few architectures where gcc misses it
+(notable armel & mipsel), to fix FTBFS there, - the same as on sid.
+https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81358
+
+ -- Michael Tokarev   Sun, 09 Jul 2023 09:44:29 +0300
+
 samba (2:4.17.9+dfsg-0+deb12u1) bookworm-proposed-updates; urgency=medium

   * d/copyright: filter out autogenerated manpages from the upstream source
diff --git a/debian/rules b/debian/rules
--- a/debian/rules
+++ b/debian/rules
@@ -103,6 +103,20 @@ with-ceph =
 with-glusterfs =
 endif

+ifneq (,$(filter armel mipsel m68k powerpc sh4,${DEB_HOST_ARCH}))
+# https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81358
+# on these platforms gcc does not link with -latomic, resulting in
+#   third_party/heimdal/lib/krb5/krcache.c.55.o: in function 
`krcc_get_principal':
+#   third_party/heimdal/lib/krb5/krcache.c:1395: undefined reference to 
`__atomic_load_8'
+# ids.krcu_cache_and_princ_id = 
heim_base_atomic_load(>krc_cache_and_principal_id);
+#   third_party/heimdal/lib/base/heimbase-atomics.h:
+# #include 
+# #define heim_base_atomic_load(x)atomic_load((x))
+# include a workaround for now
+# (-latomic and  comes from gcc, --as-needed is already in use)
+LDFLAGS := ${LDFLAGS} -latomic
+endif
+
 config-args += $(if ${with-ceph},\
  --enable-cephfs --enable-ceph-reclock,\
  --disable-cephfs)

(this is the same changes as on sid, *plus* a bit more, which updates the 
comment
with the gcc bug reference and drops -Wl,--no-as-needed, - since this one is 
already
enabled).

I'm building it on a mipsel qemu chroot right now to verify, and think it's a
better fix than to revert  kerberos keyring changes for deb12u2.

BTW, I'm not sure why dch used "bookworm" in the Distribution field in 
d/changelog
when I run `dch -r' - the previous distribution was bookworm-p-u.  Now I'm a bit
confused which value should be used there.

Thank you Adrian for all the help!

/mjt