Bug#1057977: RM: python-pcl -- ROM; no longer maintained upstream

[Jochen Sprickerhof]

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

..also now rdeps, low popcon and FTBFS.

Bug#1057959: dhcpcd gets stopped during upgrade but never started again

[Martin-Éric Racine]

On Mon, 11 Dec 2023 08:29:35 +0200
=?UTF-8?Q?Martin=2D=C3=89ric_Racine?= 
wrote:
> On Mon, 11 Dec 2023 07:52:53 +0200
> =?UTF-8?Q?Martin=2D=C3=89ric_Racine?= 
> wrote:
> > On Mon, 11 Dec 2023 00:25:45 +0100 Maximilian Engelhardt
> >  wrote:
> > > Package: dhcpcd
> > > Version: 1:9.4.1-24~deb12u3
> > > Severity: normal
> > > X-Debbugs-Cc: m...@daemonizer.de
> > >
> > > Examining dhcpcd.preinst and dhcpcd.postinst scripts indeed shows that 
> > > dhcpcd
> > > gets stopped in the preinst script, but never started again anywhere.
> >
> > These are added by dh_installinit and dh_installsystemd. Reassigning.
>
> Looking at debian/rules, I currently install the package with the
> following overrides:
>
> # Avoid starting the unconfigured service as it may break connectivity.
> override_dh_installinit:
> dh_installinit --name=dhcpcd --no-start
>
> override_dh_installsystemd:
> dh_installsystemd --name=dhcpcd --no-start
> dh_installsystemd --name=dhcpcd@ --no-start
>
> The manual for both dh_scripts says that --no-start will update the
> files but neither stop or start the services (which is expected for a
> DHCP client: the connection must remain during the upgrade). This is
> apparently not the case. The additions made by the helpers stop the
> service (oops!) and never restart it (oops again!).

Unless I misunderstood, this is due to a change of debhelper behavior
since compatibility level 10. This leaves me with two possible
solutions:

1) No dh_install option. This will restart after upgrade (default since dh 10).

2) Add --no-stop-on-upgrade --no-restart-after-upgrade options. This
will explicitely disable stop and restart actions.

Maximilian, which one of these two would make the most sense to you?

Here, I only use the binaries via ifupdown (i.e. only dhcpcd-base), so
I have no preference.

Martin-Éric

Bug#1057899: libc++abi-18-dev has an undeclared file conflict on /usr/lib/x86_64-linux-gnu/libc++experimental.a

[Sylvestre Ledru]

Hello

Yes, I have an upload pending to fix that :)

thanks

S


Le 10/12/2023 à 15:40, Helmut Grohne a écrit :

Package: libc++abi-18-dev
Version: 1:18~++20231203063627+9f78edbd20ed-1~exp1
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + libc++-17-dev

libc++abi-18-dev has an undeclared file conflict. This may result in an
unpack error from dpkg.

The file /usr/lib/x86_64-linux-gnu/libc++experimental.a is contained in
the packages
  * libc++-17-dev/1:17.0.6-2 as present in unstable
  * libc++abi-18-dev/1:18~++20231203063627+9f78edbd20ed-1~exp1 as present in 
experimental

These packages can be unpacked concurrently, because there is no
relevant Replaces or Conflicts relation. Attempting to unpack these
packages concurrently results in an unpack error from dpkg, because none
of the packages installs a diversion for the affected file.

Kind regards

The Debian Usr Merge Analysis Tool

This bug report has been automatically filed with no human intervention.
The source code is available at https://salsa.debian.org/helmutg/dumat.
If the filing is unclear or in error, don't hesitate to contact
hel...@subdivi.de for assistance.

___
Pkg-llvm-team mailing list
pkg-llvm-t...@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-llvm-team

Bug#1057975: support for libhiredis version 1.1.0 (1.2.0-4) in bullseye and bookworm

[David Pilnik]

Package: libhiredis1.1.0
Version: 1.2.0-4 1


I require to use libhiredis in Debian bullseye and bookworm that support TLS 
which is supported only in version (libhiredis1.1.0) 1.2.0-4 1.
Today Debian bullseye and bookworm support this libhiredis version only from 
experimental sources, and we required it in the regular sources.


admin@setup:~$ sudo apt-cache  policy libhiredis*

libhiredis0.14:

  Installed: 0.14.1-1

  Candidate: 0.14.1-1

  Version table:

*** 0.14.1-1 500

500 http://debian-archive.trafficmanager.net/debian 
bullseye/main 
amd64 Packages

100 /var/lib/dpkg/status

libhiredis1.1.0:

  Installed: (none)

  Candidate: 1.2.0-4

  Version table:

 1.2.0-4 1

  1 https://deb.debian.org/debian 
experimental/main amd64 
Packages

libhiredis-dev:

  Installed: (none)

  Candidate: 0.14.1-1

  Version table:

 1.2.0-4 1

  1 https://deb.debian.org/debian 
experimental/main amd64 
Packages

 0.14.1-1 500

500 http://debian-archive.trafficmanager.net/debian 
bullseye/main 
amd64 Packages

My setup details:
admin@setup:~$ uname -a:
Linux setup 5.10.0-23-2-amd64 #1 SMP Debian 5.10.179-3 (2023-07-27) x86_64 
GNU/Linux

admin@setup:~$ sudo cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=debian
HOME_URL=https://www.debian.org/
SUPPORT_URL=https://www.debian.org/support
BUG_REPORT_URL=https://bugs.debian.org/

Can be seen this info also in Debian page:

[cid:image001.png@01DA2C15.0BD0CE60]



I appreciate if you can help and add support of this libhiredis1.1.0 version in 
regular Debian sources and not only experimental.

Thanks,
David Pilnik

Bug#1052444: ITA: w-scan-cpp -- DVB channel scanner (successor of w_scan)

[Phil Wyett]

retitle 1052444 ITA: w-scan-cpp -- DVB channel scanner (successor of w_scan)
owner 1052444 !
thanks

Hi,

I am interested in 'w-scan-cpp' and would like to adopt it.

I am the Debian Maintainer (DM) of rednotebook, filezilla and libfilezilla, so 
maintaining similar
package types is familiar to me. I am also currently in progress of adopting 
'bglibs' and 'nanomsg'.

Plans:

Initially I will bring the package up to date and inline with Debians current 
practices and
standards. After, I will offer the package long term maintenance as I do with 
all other packages
under my wing.

Regards

Phil

-- 
Playing the game for the games sake.

Web:

* Debian Wiki: https://wiki.debian.org/PhilWyett
* Website: https://kathenas.org
* Social Debian: https://pleroma.debian.social/kathenas/
* Social Instagram: https://www.instagram.com/kathenasorg/




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

Bug#1021349: RFA: wput -- tiny wget-like ftp-client for uploading files

[Phil Wyett]

Hi,

The lack of upstream activity and the fact this has been over a year wanting an 
adopter. This
package really should now go the the removal RM[1] path. What do you think?

[1] https://wiki.debian.org/ftpmaster_Removals

Regards

Phil

-- 
Playing the game for the games sake.

Web:

* Debian Wiki: https://wiki.debian.org/PhilWyett
* Website: https://kathenas.org
* Social Debian: https://pleroma.debian.social/kathenas/
* Social Instagram: https://www.instagram.com/kathenasorg/




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

Bug#1056866: python-pcl: ftbfs with cython 3.0.x

[Sebastiaan Couwenberg]

On 12/11/23 08:23, Jochen Sprickerhof wrote:

* Sebastiaan Couwenberg  [2023-12-10 12:22]:

On Sun, 26 Nov 2023 10:06:32 + Matthias Klose wrote:

If the package cannot be built with cython 3.0.5, please change the
build dependency from cython3 to cython3-legacy (available now in
unstable).  There is no replacement for cython3-dbg.


The attached patch switches to cython3-legacy as the short term 
workaround.


Feel free to NMU (or team upload) python-pcl.
Honestly I'm thinking of removing it form the archive as upstream is no 
longer maintained and I don't have a use anymore either (it also has a 
low popcon and no rdeps). Do you want to maintain it?


No, I don't want to maintain it as I don't use the package either. I 
just provided patches to hopefully speedup the process to get cython 3.0 
into unstable.


Removing the package is the right thing to do for projects that are dead 
upstream in my opinion.


Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#910664: Acknowledgement (ghc: ghc package can no longer be cross-compiled)

[Ilias Tsitsimpis]

Hi Helmut,

Thanks for offering to help with cross building. Let me first comment on
the following.

On Sun, Dec 10, 2023 at 09:01PM, Helmut Grohne wrote:
> While
> that you don't want to support cross building of ghc, would you mind
> others (like me) supporting it?

and

> Given that you (ghc
> maintainers) are evidently not interested in doing the work here, I also
> suggest that you close this bug when applying the patch and letting
> cross users file new bugs with new patches.

The above statements are not true. While rewriting d/rules to build GHC
using Hadrian, I tried very hard to implement cross-building for GHC. I
backported upstream fixes [1], engaged in upstream discussion about this
[2] and we concluded that the new Hadrian build system is not capable of
cross-building GHC [3]. Upstream is working on fixing this, but it's a
slow process [4].

This is why we have the error message there, and if you look at the
d/rules file, you will see it has comments that link to these upstream
issues.

With that said, I am happy to share everything I have seen while trying
to make cross-builds work, and we can work together to support this.

[1] 
https://salsa.debian.org/haskell-team/DHG_packages/-/blob/5e08edfeba1729c62d7292cdf47408de95a5b37c/p/ghc/debian/patches/fix-cross-compilation
[2] https://gitlab.haskell.org/ghc/ghc/-/issues/23975
[3] https://gitlab.haskell.org/ghc/ghc/-/issues/23975#note_526546
[4] https://gitlab.haskell.org/ghc/ghc/-/issues/23975#note_530201

Best,

-- 
Ilias

Bug#1022779: dosbox: could dosbox-x be a future to dosbox?

[Alexandre Detiste]

Please Recommends: dosbox-x in the metadata
& the free-text Description:

Greetings

Bug#1056866: python-pcl: ftbfs with cython 3.0.x

[Jochen Sprickerhof]

Hi Bas,

* Sebastiaan Couwenberg  [2023-12-10 12:22]:

Control: tags -1 patch

On Sun, 26 Nov 2023 10:06:32 + Matthias Klose wrote:

If the package cannot be built with cython 3.0.5, please change the
build dependency from cython3 to cython3-legacy (available now in
unstable).  There is no replacement for cython3-dbg.


The attached patch switches to cython3-legacy as the short term workaround.


Feel free to NMU (or team upload) python-pcl.
Honestly I'm thinking of removing it form the archive as upstream is no 
longer maintained and I don't have a use anymore either (it also has a 
low popcon and no rdeps). Do you want to maintain it?


Cheers Jochen


signature.asc
Description: PGP signature

Bug#1043240: transition: pandas 1.5 -> 2.1

[Matthias Klose]

On 10.12.23 14:06, Rebecca N. Palmer wrote:
I'd like to move forward with the pandas 1.5 -> 2.1 transition 
reasonably soon.


Given that pandas 2.x is *not* required for Python 3.12 (but is required 
for Cython 3.0), should we wait for the Python 3.12 transition to be 
done first?


These are broken by pandas 2.x and have a possible (but untested) fix in 
their bug - please test and apply it:
dask(?) dials influxdb-python* python-altair python-feather-format 
python-upsetplot seaborn tqdm*
(* = this package is currently also broken for a non-pandas reason, 
probably Python 3.12, that I don't have a fix for)


These are broken by pandas 2.x and have no known-to-me fix:
augur cnvkit dyda emperor esda mirtop pymatgen pyranges python-anndata 
python-biom-format python-cooler python-nanoget python-skbio python-ulmo 
q2-quality-control q2-demux q2-taxa q2-types q2templates sklearn-pandas
Some generic things to try are pandas.util.testing -> pandas.testing, 
.iteritems() -> .items(), and if one exists, a more recent upstream 
version.


Is this an acceptable amount of breakage or should we continue to wait? 
Bear in mind that if we wait too long, we may be forced into it by some 
transition further up the stack (e.g. a future Python or numpy) that 
breaks pandas 1.x.


up to the maintainers. But please wait at least until the current pandas 
and numpy migrated to testing, e.g. that the autopkg tests of pandas and 
numpy triggered by python3-defaults pass.


Is there a way to see the binNMUs which are still stuck in unstable, and 
don't migrate?


Matthias

Bug#1057962:

[Konstantin Isakov]

Hi,

The proposed patch has been accepted upstream.

Bug#1055316: heimdal: fails to build against glibc 2.38

[Brian May]

Samuel Thibault  writes:

>> Whaat is the process for a breaks transition?
>
> Some details examples are discussed in Bug#1043184 in the case of krb5.

Thinking if I just drop the symbols, this is going to break
libafsauthent2 while we still have glibc 2.37 in unstable. Does this
sound correct?

Although maybe this does not matter, I see that there is already a
serious bug against openafs anyway since
August... https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043131
-- 
Brian May @ Debian

Bug#1057959: dhcpcd gets stopped during upgrade but never started again

[Martin-Éric Racine]

On Mon, 11 Dec 2023 07:52:53 +0200
=?UTF-8?Q?Martin=2D=C3=89ric_Racine?= 
wrote:
> On Mon, 11 Dec 2023 00:25:45 +0100 Maximilian Engelhardt
>  wrote:
> > Package: dhcpcd
> > Version: 1:9.4.1-24~deb12u3
> > Severity: normal
> > X-Debbugs-Cc: m...@daemonizer.de
> >
> > Examining dhcpcd.preinst and dhcpcd.postinst scripts indeed shows that 
> > dhcpcd
> > gets stopped in the preinst script, but never started again anywhere.
>
> These are added by dh_installinit and dh_installsystemd. Reassigning.

Looking at debian/rules, I currently install the package with the
following overrides:

# Avoid starting the unconfigured service as it may break connectivity.
override_dh_installinit:
dh_installinit --name=dhcpcd --no-start

override_dh_installsystemd:
dh_installsystemd --name=dhcpcd --no-start
dh_installsystemd --name=dhcpcd@ --no-start

The manual for both dh_scripts says that --no-start will update the
files but neither stop or start the services (which is expected for a
DHCP client: the connection must remain during the upgrade). This is
apparently not the case. The additions made by the helpers stop the
service (oops!) and never restart it (oops again!).

Martin-Éric

Bug#1057974: RFS: tuiwidgets/0.2.1-1 -- high-level widget based toolkit for terminal applications - documentation

[Christoph Hueffelmann]

Package: sponsorship-requests
Severity: normal
X-Debbugs-CC: textsh...@uchuujin.de

Dear mentors,

I am looking for a sponsor for my package "tuiwidgets"

It is important for me, because another package will follow:

 * Package name : tuiwidgets
   Version  : 0.2.1-1
   Upstream contact : Martin Hostettler 
 * URL  : https://tuiwidgets.namepad.de/
 * License  : 0BSD or BSL-1.0 or MIT-0, BSL-1.0
 * Vcs  : https://salsa.debian.org/chr/tuiwidgets
   Section  : libs

The source builds the following binary packages:

  libtuiwidgets0a - high-level widget based toolkit for terminal 
applications - shared library
  libtuiwidgets-dev - high-level widget based toolkit for terminal 
applications - headers
  libtuiwidgets-doc - high-level widget based toolkit for terminal 
applications - documentation


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


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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/t/tuiwidgets/tuiwidgets_0.2.1-1.dsc


Changes since the last upload:

 tuiwidgets (0.2.1-1) unstable; urgency=medium
 .
   * New upstream version

Regards,
--
  Christoph Hueffelmann

Bug#1057959: dhcpcd gets stopped during upgrade but never started again

[Martin-Éric Racine]

reassign 1057959 debhelper
done

On Mon, 11 Dec 2023 00:25:45 +0100 Maximilian Engelhardt
 wrote:
> Package: dhcpcd
> Version: 1:9.4.1-24~deb12u3
> Severity: normal
> X-Debbugs-Cc: m...@daemonizer.de
>
> Hi,
> during the recent point release I noticed that during the unattended-upgrades
> run dhcpcd was stopped but never started again. This is undesired as it breaks
> internet connection for me and I need to manually start it again.
>
> Examining dhcpcd.preinst and dhcpcd.postinst scripts indeed shows that dhcpcd
> gets stopped in the preinst script, but never started again anywhere.

These are added by dh_installinit and dh_installsystemd. Reassigning.

Martin-Éric

Bug#1057940: swirc: FTBFS: invalid use of incomplete typedef ‘WINDOW’ {aka ‘struct _win_st’}

[Markus Uhlin]

Alright, I will do so when I have time, but as soon as possible.

Den 2023-12-10 kl. 23:17, skrev Santiago Vila:

El 10/12/23 a las 22:09, Markus Uhlin escribió:
My guess is that Ncurses is built with '--enable-opaque-curses' and 
defines NCURSES_OPAQUE=1.
I'm currently running stable so I'm not able to reproduce the problem 
but if you can give me access to a computer where the problem occurs 
I can investigate it.


Hmm, please note that when I say "if you can't reproduce it" it should
be understood as "if you can't reproduce it using an unstable chroot".

So, you should really use an unstable chroot in your own computer
first (you can create it with debootstrap and then use it with schroot).

Regarding the bug itself: Here is a very similar one which maybe gives
you an idea about how to fix it, as it contains a fix at the end:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057553

Thanks.

Bug#1057171: libitext5-java: FTBFS with bouncycastle 1.77

[tony mancill]

On Sat, Dec 09, 2023 at 12:50:33PM +0100, Andreas Tille wrote:
> I tried the latest upstream version of libitext5-java and commited the
> change to Git.  Unfortunately the problem persists.  Some Debian Med
> packages are depending from this package so I'd be happy if someone
> could have a look.  You can find the latest log in Salsa CI[1].

Hi Andreas,

Thank you for your efforts here.  I just pushed a patch that resolves
the FTBFS, and the tests are passing.  I plan to do a bit more poking
at the upstream tests to make sure that the patched classes are
exercised by the test cases, but will either update this bug or upload
in the 2-3 days.

Regards,
tony

Bug#1057973: gettext: new version available upstream

[Jeffrey Cliff]

Package: gettext
Version: 0.21-14
Severity: wishlist

Dear Maintainer,

a new version of gettext (0.22.4) is available upstream at the GNU
project repositories
https://www.gnu.org/software/gettext/



-- System Information:
Distributor ID: Devuan
Description: Devuan GNU/Linux 6 (excalibur/ceres)
Release: 6
Codename: excalibur ceres
Architecture: x86_64

Kernel: Linux 6.6.0-gnulibre (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8),
LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages gettext depends on:
ii  gettext-base   0.21-14
ii  libc6  2.37-13
ii  libgomp1   13.2.0-8
ii  libunistring5  1.1-2
ii  libxml22.9.14+dfsg-1.3+b1

Versions of packages gettext recommends:
ii  curl  8.5.0-1
ii  lynx  2.9.0dev.12-1
ii  wget  1.21.4-1+b1

Versions of packages gettext suggests:
ii  autopoint 0.21-14
pn  gettext-doc   
pn  libasprintf-dev   
pn  libgettextpo-dev  

-- no debconf information

Bug#1057972: libxt-dev: new version available upstream

[Jeffrey Cliff]

Package: libxt-dev
Version: 1:1.2.1-1.1
Severity: wishlist

Dear Maintainer,

a new verion of libxt (1.3.0) is available upstream
at https://www.x.org/releases/individual/lib/



-- System Information:
Distributor ID: Devuan
Description: Devuan GNU/Linux 6 (excalibur/ceres)
Release: 6
Codename: excalibur ceres
Architecture: x86_64

Kernel: Linux 6.6.0-gnulibre (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8),
LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages libxt-dev depends on:
ii  libsm-dev 2:1.2.3-1
ii  libx11-dev2:1.8.7-1
ii  libxt61:1.2.1-1.1
ii  x11proto-dev  2023.2-1

libxt-dev recommends no packages.

Versions of packages libxt-dev suggests:
pn  libxt-doc  

-- no debconf information
themusicgod1@wicksell:~$

Bug#1054523: RFS: persp-projectile/1:1.0.0+git20210618.4e374d7-1 [RC] [Team] -- integrate perspective.el with projectile

[Xiyue Deng]

Sean Whitton  writes:

> Hello,
>
> On Fri 03 Nov 2023 at 05:01pm -07, Xiyue Deng wrote:
>
>> I thought mentioning dropping Built-Using from arch:all package could be
>> an acceptable reason, which in turn also follows Lintian's suggestion :)
>> But do let me know if I should further clarify.
>
> But why couldn't an arch:all package have Built-Using?  Built-Using, per
> Policy, is for license issues.  arch:any vs. arch:all isn't
> determinative.

So a little further reading from the policy[1] and the lintian bug[2]
helped me understand the usage of "Built-Using" a bit better: it's used
to include other source package required for building without having to
depend on them.  So technically it's not mutually exclusive with
arch:all as stated in the bug.  However, in the case of
persp-perspective, I tried with or without it and it doesn't make any
difference.  What's important is that ${elpa:Depends} correctly added
elpa-perspective and elpa-projectile to the dependency list of the
binary package.  So I think in the end dropping it should be OK.

Still, it makes sense to clarify the actual reason to drop it, so I've
updated the changelog entry to reflect this fact[3].  PTAL, TIA!

[1] 
https://www.debian.org/doc/debian-policy/ch-relationships.html#additional-source-packages-used-to-build-the-binary-built-using
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999785
[3] 
https://salsa.debian.org/emacsen-team/persp-projectile/-/commit/a0c39b5d53d96f7e85b163f9cb530efbf34b6166

-- 
Xiyue Deng


signature.asc
Description: PGP signature

Bug#1035061: gnome-keyring: prevents chrome/chromium from running on a new account's first run

[Arnaud Rebillout]

I reported the issue upstream: 
https://gitlab.gnome.org/GNOME/gnome-keyring/-/issues/137

Bug#1057966: ntpsec-ntpdate not fully compatible with ntpdate, causes adjtimex --host breakage

[Richard Laager]

From ntpdate (the wrapper):
# Known bugs:
# * The -e and -p options of ntpdate are not yet implemented.
# * ntpdate took 4 samples and chose the best (shortest trip time).
#   This takes the first.

I suppose there are maybe 4 options here:

A) Do nothing.
B) Change adjtimex to not pass -p.
C) Change ntpdate to accept -p but ignore it. Currently, it gives an
   error message of "-p is no longer supported." as you saw.
D) Have the wrapper repeatedly calling ntpdig and... then what?
E) Actually implement support for this in ntpdig and pass the flag
   through.

Obviously A is the null option, and we are looking for something better.

I don't love C, as that silently eats an option rather than being 
explicit that it doesn't do anything.


D is terrible, so I'm going to veto that one.

I'm not personally interested in implementing E, but I don't see why I'd 
reject a patch if someone else was interested.



Regarding B, it turns out that -p4 is being _added_ in adjtimex as a 
Debian patch: debian/patches/11-Fix-ntpdate-command.patch


That references this bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987625

That is for the ntp ntpdate, not ntpsec-ntpdate.

@rosh, what do you think? Could you just remove 
11-Fix-ntpdate-command.patch? That would fix adjtimex.


--
Richard

Bug#947015: ITA: python-kaptan -- Python configuration manager in various formats

[javier . ruanno]

Dear Bo Yu,
Sure, I can try it. 
Tomorrow , I review the package, and I give you an answer, because i am using 
Mac now. I think using multi pass I can do it
Regards and thanks
Javier Ruano
Sent from my iPhone

> On 11 Dec 2023, at 04:15, Bo YU  wrote:
> Hi Javier!
> On Sat, Apr 04, 2020 at 11:06:32PM +, Javier Ruano wrote:
>> Package: wnpp
>> Severity: normal
> 
> Could me ask here, would you like to adopt the package again? Because I
> saw there is no active since your ITA.
> 
> If you do not have time or other searons to maintian the package in
> time, I would like to suggest you to maintain the package under the
> Debian Python Team.
> 
> So I think once I fix #1057614 and I will move it under DPT.
> 
> --
> Regards,
> --
>  Bo YU

Bug#1035044: autorandr: libinput-tools still missing in autorandr dependencies list?

[Don Armstrong]

On Sat, 09 Dec 2023, Allan Olsen wrote:
> Dec 08 22:44:15 Innerpeace systemd[1]: Started autorandr-lid-listener.service 
> - Runs autorandr whenever the lid state changes.
> Dec 08 22:44:15 Innerpeace autorandr[61889]: stdbuf: failed to run command 
> ‘libinput’: No such file or directory
> Dec 08 22:44:15 Innerpeace systemd[1]: autorandr-lid-listener.service: 
> Deactivated successfully.
> Dec 08 22:44:45 Innerpeace systemd[1]: autorandr-lid-listener.service: 
> Scheduled restart job, restart counter is at 1832.
> 
> seems like for now autorandr only have two dependencies 
> Depends: x11-xserver-utils, python3
> 
> After I installed libinput-tools Messages are gone. 

Heh; thanks for the report. I added the lid-listener.service in 1.14-1,
and didn't check for new dependencies.

I'll have this fixed up in 1.14-2 once I upload it.

-- 
Don Armstrong  https://www.donarmstrong.com

I'm wrong to criticize the valor of your brave men. It's important to
die for one's country when it means being the subject of a king who
wears a ruffled collar or a pleated one.
 -- Cyrano de Bergerac

Bug#1054152: rasdaemon: frequent crashes of rasdaemon

[Russell Coker]

If you stop rasdaemon, move aside /var/lib/rasdaemon/ras-mc_event.db, and then 
start it again does it still crash?

-- 
My Main Blog http://etbe.coker.com.au/
My Documents Bloghttp://doc.coker.com.au/

Bug#1057970: ITP: golang-github-envoyproxy-protoc-gen-validate -- protocol buffer validation

[Maytham Alsudany]

Control: retitle -1 ITP: protoc-gen-validate -- protocol buffer validation

Retitling this ITP as it's a program+library.

Kind regards,
Maytham


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

Bug#1057971: ITP: golang-github-lyft-protoc-gen-star -- protoc plugin library for efficient proto-based code generation

[Maytham Alsudany]

Package: wnpp
Severity: wishlist
Owner: Maytham Alsudany 
X-Debbugs-CC: debian-de...@lists.debian.org, debian...@lists.debian.org
Control: block 1057970 by -1

* Package name: golang-github-lyft-protoc-gen-star
  Version : 2.0.3-1
  Upstream Author : Lyft
* URL : https://github.com/lyft/protoc-gen-star
* License : Apache-2.0
  Programming Lang: Go
  Description : protoc plugin library for efficient proto-based code   
generation

 PG* is a protoc plugin library for efficient proto-based code generation.
 .
 Documentation can be found at https://godoc.org/github.com/lyft/protoc-gen-star

This package is a dependency of golang-github-envoyproxy-protoc-gen-validate[1].

Will be maintained within Debian Go Packaging Team, and I'll need a sponsor.

[1]: https://bugs.debian.org/1057970

Kind regards,
Maytham



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

Bug#947015: ITA: python-kaptan -- Python configuration manager in various formats

[Bo YU]

Hi Javier!
On Sat, Apr 04, 2020 at 11:06:32PM +, Javier Ruano wrote:

Package: wnpp
Severity: normal


Could me ask here, would you like to adopt the package again? Because I
saw there is no active since your ITA.

If you do not have time or other searons to maintian the package in
time, I would like to suggest you to maintain the package under the
Debian Python Team.

So I think once I fix #1057614 and I will move it under DPT.

--
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1057970: ITP: golang-github-envoyproxy-protoc-gen-validate -- protocol buffer validation

[Maytham Alsudany]

Package: wnpp
Severity: wishlist
Owner: Maytham Alsudany 
X-Debbugs-CC: debian-de...@lists.debian.org, debian...@lists.debian.org
Control: block 1057894 by -1

* Package name: protoc-gen-validate
  Version : 1.0.2
  Upstream Author : Buf
* URL : https://github.com/bufbuild/protoc-gen-validate
* License : Apache-2.0
  Programming Lang: Go
  Description : protocol buffer validation

 PGV is a protoc plugin to generate polyglot message validators. While protocol
 buffers effectively guarantee the types of structured data, they cannot
 enforce semantic rules for values. This plugin adds support to
 protoc-generated code to validate such constraints.

This package is a dependency of golang-github-cncf-xds[1].

[1]: https://bugs.debian.org/1057894

Kind regards,
Maytham



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

Bug#1057968: python3-flake8: cannot import name 'missing_whitespace_around_operator' from 'pycodestyle'

[Tomas Janousek]

Package: python3-flake8
Version: 5.0.4-4
Severity: normal

flake8 is today broken ($subj) in Debian testing because pycodestyle 
2.11 isn't API-compatible with 2.10 and python3-pycodestyle 2.11.1-1 
migrated to testing before python3-flake8 6.1.0-1 did. The relevant 
upstream change is this one:

  
https://github.com/PyCQA/flake8/commit/9786562feb573d30c73f18e1a0a6685c8584e9b5

Note that upstream does specify an upper bound on pycodestyle, but the 
Debian python3-flake8 package does not. If it had, it would probably 
prevent this scenario where one package migrated to testing and the 
other didn't. (Well, I hope it would, but I don't know enough about 
Debian to be sure.)

(Feel free to close this but please do consider whether that upper bound 
would be appropriate. Presumably a similar problem might affect 
python3-pyflakes but that didn't migrate yet.)

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

Kernel: Linux 6.5.0-3-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_CPU_OUT_OF_SPEC, TAINT_USER, TAINT_WARN
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python3-flake8 depends on:
ii  python3 3.11.4-5+b1
ii  python3-importlib-metadata  4.12.0-1
ii  python3-mccabe  0.7.0-1
ii  python3-pycodestyle 2.11.1-1
ii  python3-pyflakes2.5.0-1
ii  python3-setuptools  68.1.2-2

python3-flake8 recommends no packages.

python3-flake8 suggests no packages.

-- no debconf information

-- 
Tomáš "liskin" ("Pivník") Janoušek, https://lisk.in/

Bug#1057887: bind9 named logging for category rpz misses some rpz log messages

[Evan Harris]

https://gitlab.isc.org/isc-projects/bind9/-/issues/4483

Bug#1051044: ITA: opentk -- Open Toolkit wrapper for OpenGL, OpenAL and OpenCL

[Ying-Chun Liu (PaulLiu)]

owner 1051044 !
retitle 1051044 ITA: opentk -- Open Toolkit wrapper for OpenGL, OpenAL and 
OpenCL
thanks

Hi all,

I'll take care of this package as I'm the user of this library.

Yours,
Paul


OpenPGP_0x44173FA13D05.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1057967: linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely unusable

[Kevin Price]

Package: linux-image-6.1.0-15-amd64
Version: 6.1.66-1
Severity: critical
Control: -1 notfound 6.1.64-1

When booting 6.1.0-15, my physical amd64/bookworm/gnome computer
misbehaves in many ways, rendering it largely unusable. With kernels up
to 6.1.0-13, and even briefly with the otherwise broken 6.1.0-14, all of
this seemed fine.

Misbehavior includes, not limited to:

1. Most actions take considerably longer than usual.

2. The GDM greeter has an English keyboard layout, which otherwise is
German. (Login works.)

3. There seems to be no network connectivity. No WiFi icon. "ping
8.8.8.8" returns IIRC network unreachable.

4. Launching Firefox does apparently nothing.

5. Launching gnome-terminal does work, but some basic commands just
freeze, such as "ip a" or "sudo dmesg". sudo hangs before prompting for
the passphrase. At that stage, even "sudo -i", I cannot interrupt with "^C".

6. Shutting down takes ages, with systemd waiting for a bunch of
processes (sudo) and services to terminate, most of the latter seem to
be somehow network-related, but you tell me which aren't.

After more that 10 min I used hard power-off, leaving my ext4 dirty, but
being perfectly able to boot any of 6.1.0-12 through -15, with -12 and
-13 working properly, and -15 showing the exact same misbehavior
reproducibly.

I'll attach all I could get out of reportbug running under 6.1.0-15, and
please let me know what further testing I may perform IOT help you.
Please also specify whether you'd like me to do that testing under
6.1.0-15, in which I cannot even invoke sudo, or under 6.1.0-13, which
will do anything fine.

Thanks a lot in advance, and HTH!
-- 
Kevin PriceContent-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Kevin Price 
To: Debian Bug Tracking System 
Subject: linux-image-6.1.0-15-amd64 makes my physical bookworm/gnome system 
vastly unusable
Bcc: Kevin Price 

Package: src:linux
Version: 6.1.66-1
Severity: critical



-- Package-specific info:
** Version:
Linux version 6.1.0-15-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian 
12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP 
PREEMPT_DYNAMIC Debian 6.1.66-1 (2023-12-09)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-6.1.0-15-amd64 
root=UUID=b1e4af52-2d43-40ab-a468-ca11bf2a3122 ro quiet

** Tainted: POE (12289)
 * proprietary module was loaded
 * externally-built ("out-of-tree") module was loaded
 * unsigned module was loaded

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Model information
sys_vendor: LENOVO
product_name: 1068FQG
product_version: Lenovo B570
chassis_vendor: LENOVO
chassis_version: 0.1
bios_vendor: LENOVO
bios_version: 44CN41WW
board_vendor: LENOVO
board_name: Emerald Lake
board_version: FAB1

** Loaded modules:
cts
uinput
rfcomm
snd_seq_dummy
snd_hrtimer
snd_seq
snd_seq_device
xt_CHECKSUM
xt_MASQUERADE
bridge
stp
llc
cmac
algif_hash
algif_skcipher
af_alg
bnep
ip6t_rt
ip6t_REJECT
nf_reject_ipv6
nft_chain_nat
nf_nat
xt_set
ipt_REJECT
nf_reject_ipv4
xt_tcpudp
xt_conntrack
nf_conntrack
nf_defrag_ipv6
nf_defrag_ipv4
nft_compat
nf_tables
binfmt_misc
ip_set_hash_ipport
pktcdvd
ip_set
nfnetlink
intel_rapl_msr
intel_rapl_common
x86_pkg_temp_thermal
intel_powerclamp
nls_ascii
nls_cp437
btusb
kvm_intel
btrtl
btbcm
vfat
btintel
btmtk
fat
kvm
bluetooth
irqbypass
crc32_pclmul
crypto_simd
xts
ecb
jitterentropy_rng
dm_crypt
ghash_clmulni_intel
cryptd
snd_hda_codec_hdmi
sha512_ssse3
sha512_generic
isofs
sha256_ssse3
rtsx_usb_sdmmc
sha1_ssse3
snd_hda_codec_realtek
wl(POE)
snd_hda_codec_generic
mmc_core
ledtrig_audio
ctr
rtsx_usb_ms
memstick
snd_hda_intel
snd_intel_dspcfg
snd_intel_sdw_acpi
drbg
snd_hda_codec
iTCO_wdt
intel_pmc_bxt
uvcvideo
iTCO_vendor_support
mei_hdcp
at24
watchdog
videobuf2_vmalloc
snd_hda_core
videobuf2_memops
rtsx_usb
rapl
videobuf2_v4l2
ansi_cprng
videobuf2_common
snd_hwdep
intel_cstate
ecdh_generic
intel_uncore
wmi_bmof
ecc
snd_pcm
videodev
sr_mod
cdrom
r8169
cfg80211
realtek
i2c_i801
snd_timer
mc
pcspkr
i2c_smbus
mei_me
ideapad_laptop
mdio_devres
platform_profile
snd
libphy
mei
lpc_ich
soundcore
sparse_keymap
rfkill
ac
battery
button
joydev
sg
coretemp
parport_pc
ppdev
lp
parport
loop
fuse
efi_pstore
dm_mod
configfs
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
efivarfs
raid10
raid456
libcrc32c
crc32c_generic
async_raid6_recov
async_memcpy
async_pq
async_xor
xor
async_tx
raid6_pq
raid1
raid0
multipath
linear
md_mod
sd_mod
t10_pi
crc64_rocksoft
crc64
crc_t10dif
crct10dif_generic
hid_generic
usbhid
hid
i915
i2c_algo_bit
drm_buddy
drm_display_helper
ahci
libahci
drm_kms_helper
libata
cec
rc_core
ehci_pci
ehci_hcd
ttm
scsi_mod
usbcore
crct10dif_pclmul
crct10dif_common
drm
psmouse
evdev
crc32c_intel
scsi_common
serio_raw
usb_common
video
wmi

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core Processor 
Family DRAM Controller [8086:0104] (rev 09)
Subsystem: Lenovo 2nd Generation Core Processor Family DRAM 

Bug#1057966: ntpsec-ntpdate not fully compatible with ntpdate, causes adjtimex --host breakage

[E Harris]

Package: ntpsec-ntpdate
Version: 1.2.2+dfsg1-1+deb12u1
Severity: normal

When attempting to use adjtimex --host command, it fails due to current
ntpdate not being fully compatible with previous ntpdate package.

# adjtimex --host 66.118.228.14
ntpdate: -p is no longer supported.
ntpdig: querying 66.118.228.14 (66.118.228.14)
cannot understand ntpdate output


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

Kernel: Linux 5.10.0-26-amd64 (SMP w/4 CPU threads)
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

Versions of packages ntpsec-ntpdate depends on:
ii  netbase6.4
ii  ntpsec-ntpdig  1.2.2+dfsg1-1+deb12u1

ntpsec-ntpdate recommends no packages.

ntpsec-ntpdate suggests no packages.

-- debconf-show failed

Bug#1057965: adjtimex --host not working with change to ntpsec-ntpdate

[E Harris]

Package: adjtimex
Version: 1.29-11+b1
Severity: normal

When trying to use the adjtimex --host option, it fails with:

# adjtimex --host 66.118.228.14
ntpdate: -p is no longer supported.
ntpdig: querying 66.118.228.14 (66.118.228.14)
cannot understand ntpdate output

This seems to be caused by the change to replace the ntpdate package with
ntpsec-ntpdate, which is not fully compatible.


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

Kernel: Linux 5.10.0-26-amd64 (SMP w/4 CPU threads)
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

Versions of packages adjtimex depends on:
ii  debconf [debconf-2.0]  1.5.82
ii  libc6  2.36-9+deb12u3
ii  lsb-base   11.6
ii  sysvinit-utils [lsb-base]  3.06-4

adjtimex recommends no packages.

Versions of packages adjtimex suggests:
pn  ntpdate  

-- debconf-show failed

Bug#1024311: Bug#1024276: #1024276: ITP: golang-github-googleapis-enterprise-certificate-proxy -- Google Proxies for

[Maytham Alsudany]

Hi Drew,

> > I've got access to the Salsa repo, so are you ok with me pushing these 
> > changes
> > to the repo?
> 
> We've got a mechanism using debian/watch and debian/copyright to 
> automate removing third_party/pkcs11/* and creating the 0.*.0+dfsg 
> tarball.  I suggest making a Merge Request with your fix so we can 
> review that, and then merge it all together.

I've done precisely that, you can see the commit at [1].

You can find my work at [2].

I'd prefer to commit directly to the team repo rather than opening a merge
request, as the commits include the new (repacked) upstream version. A MR will
require the upstream branch and tag to be updated/added manually after merging,
or another separate MR.

Please have a look at my work and let me know if I can go ahead with pushing
these changes to the team repo.

[1]: https://salsa.debian.org/Maytha8/go-pkcs11/-/commit/3035f43e
[2]: https://salsa.debian.org/Maytha8/go-pkcs11

Kind regards,
Maytham


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

Bug#1057964: harfbuzz: Please update to 8.3.0

[Jeremy Bícha]

Source: harfbuzz
Version: 8.0.1-1
Severity: wishlist

harfbuzz 8.3.0 is available. Please package this new release.

https://github.com/harfbuzz/harfbuzz/releases

Thank you,
Jeremy Bícha

Bug#1047967: splash: Fails to build source after successful build - Bug: 1047967

[Phil Wyett]

Hi,

Saw the RFA you have filed, but also saw the reproducible builds failure.

Attached is a new 'd/clean' file that fixes the fail to build after successful 
build.

Regards

Phil

-- 
Playing the game for the games sake.

Web:

* Debian Wiki: https://wiki.debian.org/PhilWyett
* Website: https://kathenas.org
* Social Debian: https://pleroma.debian.social/kathenas/
* Social Instagram: https://www.instagram.com/kathenasorg/


src/read_data_sphNG_otherendian.f90
docs/splash.pdf
docs/splash.aux
docs/splash.log
docs/splash.out
docs/splash.toc
man/splash.1
docs/_build/doctrees/*.*
docs/_build/html/_images/*
docs/_build/html/_static/*.png
docs/_build/html/_static/fonts/*.ttf
docs/_build/html/_static/fonts/*.eot
docs/_build/html/_static/fonts/*.woff2
docs/_build/html/_static/fonts/*.woff
docs/_build/latex/*.pdf
docs/_build/html/*.inv
docs/_build/latex/*.png
docs/_build/latex/*.jpg
docs/_build/html/_static/*.css
docs/_build/html/_static/*.js
docs/_build/html/*.html
docs/_build/latex/*.bat
docs/_build/latex/*.idx
docs/_build/latex/*.ind
docs/_build/html/*.js
docs/_build/latex/latexmkjarc
docs/_build/latex/Makefile
docs/_build/latex/latexmkrc
docs/_build/latex/*.sty
docs/_build/latex/*.tex
docs/_build/html/.buildinfo
docs/_build/html/_sources/*.rst.txt
docs/_build/html/_static/css/*.css
docs/_build/html/_static/fonts/*.svg
docs/_build/html/_static/js/*.js
docs/_build/latex/*.xdy
docs/_build/latex/_static/*.js
docs/_build/latex/python.ist
docs/_build/latex/sphinx.xdy
docs/_build/latex/s*.cls
docs/_build/latex/splash.aux
docs/_build/latex/splash.fdb_latexmk
docs/_build/latex/splash.fls
docs/_build/latex/splash.ilg
docs/_build/latex/splash.log
docs/_build/latex/splash.out
docs/_build/latex/splash.toc

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

Bug#1057963: annotate-output: big overhaul

[Christoph Anton Mitterer]

Package: devscripts
Version: 2.23.6
Severity: wishlist
Tags: patch


Hey.

Shamlessly copy my text from:
https://salsa.debian.org/debian/devscripts/-/merge_requests/377

This is some major overhaul of annotate-output.

The core parts are IMO:
- getting rid of any shell variables set by the script itself, which
  may override variables that the caller wants to export to the
  invoked program (a355a37f1e285673d0fcb54fdff87893646848b9,
  383a82917fe180cc3a45dec520afa139b552e093 and
  ecea512825e964d073c74f6c9961ced44d5d3809)
- greatly improving performance when no date conversion specifiers are
  used (c236a7ecb4c178d72a4f477be451948831684063)

Per default the behaviour (in terms of output format) should not be
changed, at least the stuff that might get parsed by someone.

Please notice that I did some ugly reference of another commit ID (that
of a355a37f1e285673d0fcb54fdff87893646848b9) in some commits. So if you
don’t apply that on top of the current master or change commits, please
adapt the commit messages, or let me do it.

Other than that, please review and merge[0] :-)

Thanks, Chris.


[0] Or even better, let someone skilled in C and especially IO streams
(the latter being a weakness of mine), re-implemented it properly.

PS: I'm attaching the patch series here, too, though I guess I'd prefer
to discuss things on salsa/Gitlab.
>From 4091b4a3c12d8ef98fd949d09ab53d9dfaaf6efa Mon Sep 17 00:00:00 2001
From: Christoph Anton Mitterer 
Date: Sun, 10 Dec 2023 05:23:36 +0100
Subject: [PATCH 01/23] annotate-output: fixed typo

Signed-off-by: Christoph Anton Mitterer 
---
 scripts/annotate-output.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/scripts/annotate-output.sh b/scripts/annotate-output.sh
index 84025f58..da308252 100755
--- a/scripts/annotate-output.sh
+++ b/scripts/annotate-output.sh
@@ -70,7 +70,7 @@ echo Started "$@" | handler $formatter I
 
 # The following block redirects FD 2 (stderr) to FD 1 (stdout) which is then
 # processed by the stderr handler. It redirects FD 1 (stdout) to FD 4 such
-# that it can later be move to FD 1 (stdout) and handled by the stdout handler.
+# that it can later be moved to FD 1 (stdout) and handled by the stdout 
handler.
 # The exit status of the program gets written to FD 2 (stderr) which is then
 # captured to produce the correct exit status as the last step of the pipe.
 # Both the stdout and stderr handler output to FD 3 such that after exiting
-- 
2.43.0

From a355a37f1e285673d0fcb54fdff87893646848b9 Mon Sep 17 00:00:00 2001
From: Christoph Anton Mitterer 
Date: Sun, 10 Dec 2023 05:42:22 +0100
Subject: [PATCH 02/23] annotate-output: prevent `PROGNAME`-variable from
 leaking to command
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

annotate-output is a wrapper program that runs other programs. Such programs may
in turn make use of arbitrary environment variables.

Every variable that is set within the script, may have been already in the
environment of the shell (because it was already exported when `annotate-output`
itself was called).
The script would then overwrite the variable and export it further to the actual
program, which would not get the value as expected by the user.

A simple example (before this commit) would have been:
```
$ export PROGNAME=foo; annotate-output env | grep -E ^.{12}PROGNAME=
15:50:19 O: PROGNAME=annotate-output
```

Unfortunately, the problem cannot be fully solved in the Shell Command Language,
amongst others because:
- Shell always unconditionally set some own variables - which again my have
  already been marked as exported.
- Environment variables need to to be valid shell variables (e.g. `*=value`) is
  in principle a valid environment variable, but not a shell variable) and it’s
  unspecified whether such are still passed on to commands (called from the
  shell) or not.

A re-implementation in e.g. C would be needed to overcome this limitation (side
note: even Python cannot be made 100% transparent of the environment, see
https://github.com/python/cpython/issues/93446).

Signed-off-by: Christoph Anton Mitterer 
---
 scripts/annotate-output.sh | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/scripts/annotate-output.sh b/scripts/annotate-output.sh
index da308252..25307a17 100755
--- a/scripts/annotate-output.sh
+++ b/scripts/annotate-output.sh
@@ -14,8 +14,6 @@
 
 set -eu
 
-PROGNAME=${0##*/}
-
 handler() {
while IFS= read -r line; do
printf "%s %s: %s\n" "$($1)" "$2" "$line"
@@ -27,7 +25,7 @@ handler() {
 
 usage() {
echo \
-"Usage: $PROGNAME [options] program [args ...]
+"Usage: ${0##*/} [options] program [args ...]
   Run program and annotate STDOUT/STDERR with a timestamp.
 
   Options:
-- 
2.43.0

>From 554612e126d5fa6bafb3af2fad50d8e442dde777 Mon Sep 17 00:00:00 2001
From: Christoph Anton Mitterer 
Date: Sun, 10 Dec 2023 06:26:48 +0100
Subject: [PATCH 03/23] annotate-output: define 

Bug#1057962: bfd_find_nearest_line() leaks memory due to dwarf_rnglists_buffer never being freed

[Konstantin Isakov]

Package: libbinutils
Version: 2.41.50.20231206-1

Valgrind reports a leak when using bfd_find_nearest_line():

==2681185== 145,802 bytes in 1 blocks are definitely lost in loss record 39
of 39
==2681185==at 0x4840808: malloc (in
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==2681185==by 0x4FCA936: bfd_malloc (libbfd.c:290)
==2681185==by 0x5023665: read_section (dwarf2.c:737)
==2681185==by 0x5024E54: read_debug_rnglists (dwarf2.c:3181)
==2681185==by 0x5024E54: read_rnglists (dwarf2.c:3716)
==2681185==by 0x5026D42: read_rangelist (dwarf2.c:3791)
==2681185==by 0x5026D42: parse_comp_unit (dwarf2.c:4570)
==2681185==by 0x5026D42: stash_comp_unit (dwarf2.c:5589)
==2681185==by 0x502AB2A: _bfd_dwarf2_find_nearest_line_with_alt
(dwarf2.c:5969)
==2681185==by 0x4FFDC56: _bfd_elf_find_nearest_line_with_alt
(elf.c:10013)
==2681185==by 0x4FFDDC0: _bfd_elf_find_nearest_line (elf.c:9990)

The program does call bfd_close(), but that single allocation is still
leaked afterwards.

I've traced this to dwarf_rnglists_buffer in dwarf2_debug_file never being
freed. The following patch fixes it:

--- a/bfd/dwarf2.c 2023-11-25 04:59:00.0 -0300
+++ b/bfd/dwarf2.c 2023-12-10 21:05:02.084673848 -0300
@@ -6123,6 +6123,7 @@
   free (file->dwarf_line_str_buffer);
   free (file->dwarf_str_buffer);
   free (file->dwarf_ranges_buffer);
+  free (file->dwarf_rnglists_buffer);
   free (file->dwarf_line_buffer);
   free (file->dwarf_abbrev_buffer);
   free (file->dwarf_info_buffer);

I don't provide a test case, but it's very easy to see that the pointer
does get allocated but never gets freed anywhere, unlike its neighbours
(e.g. dwarf_ranges_buffer is allocated and freed in exactly the same way).
I've also tested the patch and the error goes away with it.

Bug#1057961: RFS: mplayer/2:1.5+svn38446-1 [RC] -- movie player for Unix-like systems

[lorenzo]

Package: sponsorship-requests
Severity: important

Dear mentors,

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

 * Package name : mplayer
   Version  : 2:1.5+svn38446-1
   Upstream contact : [fill in name and email of upstream]
 * URL  : https://mplayerhq.hu
 * License  : LGPL-2.1+, Expat, ISC, public-domain-tom, GPL-2+,
   BSD-2-Clause, other-2, other-1
 * Vcs  : https://salsa.debian.org/multimedia-team/mplayer
   Section  : video

The source builds the following binary packages:

  mplayer-gui - movie player for Unix-like systems (GUI variant)
  mencoder - MPlayer's Movie Encoder
  mplayer - movie player for Unix-like systems
  mplayer-doc - documentation for MPlayer

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

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

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

  dget -x
  
https://mentors.debian.net/debian/pool/main/m/mplayer/mplayer_1.5+svn38446-1.dsc

git repo:
  https://salsa.debian.org/multimedia-team/mplayer/-/tree/next?ref_type=heads

Changes since the last upload:

 mplayer (2:1.5+svn38446-1) unstable; urgency=medium
 .
   [ Lorenzo Puliti ]
   * New upstream version 1.5+svn38446
  - fix FTBFS (Closes: #1057579)
  - d/control: B-D: switch to nasm
  - avoid crahes when -wid specifies an
invalid Window ID, see #1034867
  - fix ID_VID_0_ROTATE, relevant for #1040168
 .
   [ Vagrant Cascadian ]
   * debian/rules: Use printf instead of echo.
  (Closes: #1039457)
   [ Paul Wise ]
   * improve printf line in d/rules.

Regards,
Lorenzo

Bug#1057960: Font for commands that disambiguates similar looking characters.

[Jeandré]

Package: installation-guide
Version: 20230508+deb12u1

Commands that users can type into a terminal are marked up as "span
class="command"", but I don't think the CSS defines how to format it
.
Commands are therefore formatted using the same font as the normal
text: "liberation sans" which is the 1st font option for the body in
the CSS. If the user has that font, commands show lowercase "L"s and
uppercase "i"s looking almost exactly the same, e.g. at
.
I'd suggest formatting Commands in the CSS with a font that makes it
easier to spot the difference, since a person may be looking a the
guide on a different computer than the one they're typing the Commands
on and not copying and pasting them. The font for Code is "liberation
mono", which like "DejaVu Sans Mono Book" is sans serif except for l,
I, 1, 0, i, j, and J.

Bug#1057953: nss-myhostname: different IP address between man page and package description

[Michael Biebl]

Daniele Forsi schrieb am 10.12.2023 22:32 (GMT +01:00):

> Package: libnss-myhostname
> Version: 254.5-1
> Severity: minor
> X-Debbugs-Cc: dfo...@gmail.com
> 
> Dear maintainer,
> 
> the package description says:
>> It returns all locally configured public IP addresses or -- if
>> none are configured, the IPv4 address 127.0.1.1
> 
> the man page says:
>> The local, configured hostname is resolved to [...] the IPv4 address 
>> 127.0.0.2
> and the example shows 127.0.0.2 
> 
> Do they refer to different things?

Most likely the package description is simply out-of-date.

Bug#1043240: pandas 1.5 -> 2.1?

[Drew Parsons]

On 2023-12-10 21:55, Kingsley G. Morse Jr. wrote:

Hi Rebecca, Julian and all science minded pythonistas of debian, great
and small!


3.) The following one-liner suggests 44 debian
packages might be affected by the breaks
Rebecca said would be caused by pandas 2.x:

$ for s in augur cnvkit dyda emperor esda mirtop pymatgen pyranges
python-anndata python-biom-format python-cooler python-nanoget
python-skbio python-ulmo q2-quality-control q2-demux q2-taxa q2-types
q2templates sklearn-pandas ; do apt-cache search "$s" ; done | less



I'd say don't worry about pymatgen in any case.  It's got a new version 
to upgrade to, and they make regular releases.


Drew

Bug#1057959: dhcpcd gets stopped during upgrade but never started again

[Maximilian Engelhardt]

Package: dhcpcd
Version: 1:9.4.1-24~deb12u3
Severity: normal
X-Debbugs-Cc: m...@daemonizer.de

Hi,
during the recent point release I noticed that during the unattended-upgrades 
run dhcpcd was stopped but never started again. This is undesired as it breaks 
internet connection for me and I need to manually start it again.

The behaviour can be easily reproduces by these commands:

$ systemctl status dhcpcd.service | grep Active
 Active: active (running) since Mon 2023-12-11 00:13:36 CET; 1min 52s ago
$ apt reinstall dhcpcd
$ systemctl status dhcpcd.service | grep Active
 Active: inactive (dead) since Mon 2023-12-11 00:16:02 CET; 4s ago

Examining dhcpcd.preinst and dhcpcd.postinst scripts indeed shows that dhcpcd 
gets stopped in the preinst script, but never started again anywhere.

Thanks,
Maxi

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

Bug#1057697: nodejs:please enable loong64

[Jérémy Lal]

Le sam. 9 déc. 2023 à 16:27, Bo YU  a écrit :

> Source: nodejs
> Followup-For: Bug #1057697
> Version: 18.19.0+dfsg-6
> Tags: patch
>
> >>It seems we need to merge the patch[0] from #1054259 to finish the first
> >>stage for bootstraping nodejs on any arches if based on 18.19.0.
>
> >>From my side it's like this.
>
> >Right, I overlooked those patches - because I only read the first one,
> which was very wrong.
> >The actual fixes those patches were proposing are now applied.
>
> >However now I'm a bit worried that this is all in vain, because nodejs
> unconditionally requires cjs-module-lexer,
> >so one cannot execute anything without it (that wasn't the case when only
> acorn was an external builtin).
> ^
> (Copied txt from #1054259)
>
> To be honest, I do not understand the first patch from #1054259.
> Based on past bootstrap riscv64 experiences, I easily bootstrap nodejs
> for loong64 following the debian/README.source.
>
> Just for your convenience, I attach the debdiff for bootstrap nodejs for
> loong64 after finishing the first stage bootstrap.


Good news, the first stage build now works pretty well,
meaning it produces a nodejs binary that can be useful.
It even pass most of its testsuite, except of course everything that needs
- the command line repl (acorn)
- fetch (undici)
- commonjs modules (cjs-module-lexer)

It is on current master-18.x branch, and i double-checked it builds fine.

Jérémy

Bug#1057958: RFP: vim-vimwiki -- a personal wiki for vim

[Matthias Geiger]

Package: wnpp
Severity: wishlist
X-Debbugs-Cc: team+...@tracker.debian.org, werdah...@riseup.net

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: vim-vimwiki
  Version : 2023.04.04
  Upstream Contact: vimwiki team
* URL : https://github.com/vimwiki/vimwiki 
* License : MIT
  Programming Lang: Vimscript
  Description : a personal wiki for vim

vimwiki is a personalized wiki within vim supporting links, export to
html, and much more. I would like to see this in debian; as my time is
pretty limited I can't maintain this in good faith.

best,

werdahias

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEEwuGmy/3s5RGopBdtGL0QaztsVHUFAmV2ROYVHHdlcmRhaGlh
c0ByaXNldXAubmV0AAoJEBi9EGs7bFR1qQcP/icNsd5N1xMms6KExMy8YdWZ0tYN
E9dIONC7JWbxWHM5/f8O9YT+UrQZrcf1z3bo7vOqMd+8ND7FH+o8gUHiAGbn17br
OurrS2wJhEZoHIzWOqDIHAX0aznjOb0IhSMc11GHhqSqEUaShSqyzXD4nz48217I
7VaLU3d1K9a1HAMAvNxg8nhWAcZFtjD32IGoR59oaLvPSS/rkfyWUI0MuGz16Uqc
u4y3I9OnT8xE4ytVTrIS23KeQgx2O+eXaRFp6MYkBS7uvI06jLh7QMtcxusavKMv
OXbr28VPTtEQoGHhUiYT5AnyFxiMC4nR67yKFXZb6NA2HfwmNqxIjwkKbQyBOTdx
FTiJT794nydw8gzAID00qU91CCS1cpT0PObQNBrwPjmGbmT54DSPl7GKmIMz7LaI
g++1Ocp6wKSlRFGOuGC3BPMFQ5AAhgUfB8uKqkH3sEctn/HSzJiHz8l6pgafIwWN
p9X4gpO/5Mq7su12K1HYuMMOyuXoPmHNk8CTfZ6SCYTtd0sxcT6wzbyRUGqPhhbb
PfynTgum52XpKbe6EVMEq1osQnQBcy+jO1LQnfiK1jobkVpsV5P0ZqYckUwxpY//
i6oHvQgtaowS8jfEIbu26/25HiWMXxKZrrSKRcFtQYxcWrgJB90B+tpNcFyeUhbC
QneLcY+59Hi5MX1E
=alaC
-END PGP SIGNATURE-

Bug#1057957: RFP: rust-numbat -- staticially typed programmin language for scientific computations

[Matthias Geiger]

Package: wnpp
Severity: wishlist
X-Debbugs-Cc: debian-r...@lists.debian.org, werdah...@riseup.net

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: rust-numbat
  Version : 1.8.0
  Upstream Contact: David Peter
* URL : https://github.com/sharkdp/numbat
* License : MIT/Apache 2.0
  Programming Lang: Rust
  Description : staticially typed programming language for scientific 
computations

numbat is a powerful CLI calculator. It supports mathematical
statements, unit and currency conversion, and much more. 

It consists of three libraries/crates where oen contains the CLI
application, another the underlying library and the last one contains
the currency conversion mechanics.

I do not have time to package this atm, thus filing as RFP.

best, 

werdahias

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEEwuGmy/3s5RGopBdtGL0QaztsVHUFAmV2QvMVHHdlcmRhaGlh
c0ByaXNldXAubmV0AAoJEBi9EGs7bFR1izwP/Ajr1Dpd7IEo/A4SZSJfBoR1FeMI
m2TBgtx7g1I/3RIs8pq5oXyjZxCiCBkmMzelyWlHeVIxLUDatVBGLJek9R5ibAWQ
1rZNzF3j7JESBvEZlwKzKg/N+fLCpmHWRl81HBijrNYLkXmWO9e8Ac/lZgzcVuEK
YbqPCTCRCuRwNRL5VxHM4B6nqPp9zSnR9Dtjl1uNH0/P5aRZcAeH/g07XpGjx4q3
rRXA+CIRkrEJG7K3EmpHAKp18S7W50zasNgHPvY8XbF2xUli93NRKB3nONGLkZUJ
NkZX8WNmeWzhUt+OqDjlsV6akSBQ0NzaVgNK2XHSkC6VrsAfKCqVcAmaudRegsjX
F9TRl+BaOgeG0SCuww9Vim0Pygen/MFmhKXX+84J/gSRAH0HVmyR60TYFYSRoKF/
nYrgUXiHWtx+8Ra3KS/u9k2ccTJJ3l6NXexdXTIKE+jhbjIE9YSq+PErhafLodsz
10FqQe0OD2tpDScP3qpb1RACY5O/sdJ9s0TCBTkTZzfxmKbggPahJkYLjgo0DwZc
hkl/U2WYrQ8sYNlpN939NYg5yF9cru9HTTi1Njc0My69H4AMHASx9Dg8i7biS43n
Q8Xx+fNbUp2nLLoMmsiH7f/ELnm3jyMWJ/Vzb5g9iqoOJtNZMUXYq4i94Q5jyHlj
iBSbNcbZlB2oV28f
=oDx0
-END PGP SIGNATURE-

Bug#1057933: libjose4j-java: FTBFS: IOException: Only named ECParameters supported

[tony mancill]

On Sun, Dec 10, 2023 at 08:18:03PM +0100, Santiago Vila wrote:
> Package: src:libjose4j-java
> Version: 0.7.12-2
> Severity: serious
> Tags: ftbfs
> 
> [ERROR] Tests run: 6, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 0.063 
> s <<< FAILURE! - in org.jose4j.jwk.EllipticCurveJsonWebKeyTest
> [ERROR] 
> testParseExampleWithPrivate256(org.jose4j.jwk.EllipticCurveJsonWebKeyTest)  
> Time elapsed: 0.031 s  <<< FAILURE!
> java.lang.AssertionError:
> expected: [8b:e2:14:0f:3a:17:e9:25:d1:ae:df:18:a3:b2:9a:fd:63:04:41:11]
> X: 
> 7fcdce2770f6c45d4183cbee6fdb4b7b580733357be9ef13bacf6e3c7bd15445
> Y: 
> c7f144cd1bbd9b7e872cdfedb9eeb9f4b3695d6ea90b24ad8a4623288588e5ad
> > but was:
>   at 
> org.jose4j.jwk.EllipticCurveJsonWebKeyTest.testParseExampleWithPrivate256(EllipticCurveJsonWebKeyTest.java:53)
> ...
>
> If required, the full build log is available here:
> 
> https://people.debian.org/~sanvila/build-logs/202312/

Thank you for making this available.

> About the archive rebuild: The build was made using virtual machines
> from AWS, with enough memory, enough disk, and either one or two
> CPUs, using a reduced chroot with only build-essential packages.

I'm not able to reproduce this locally, and the only potentially
relevant difference I see between the AWS testbed and my local
environment is that I am running Intel and the AWS system is AMD.

> If you could not reproduce the bug please contact me privately, as I
> am willing to provide ssh access to a virtual machine where the bug is
> fully reproducible.

Will do, as time permits.

This package has a low popcon, and is a build-dependency of
libcallstats-java, which also has a low popcon, and has no reverse
dependencies.  I believe both are part of an effort to get Jitsi back
into Debian.  If that's not likely to happen, an alternative is to file
RM bugs for both of them.  (I am adding the Uploaders to the cc:)

Thanks,
tony


signature.asc
Description: PGP signature

Bug#1057940: swirc: FTBFS: invalid use of incomplete typedef ‘WINDOW’ {aka ‘struct _win_st’}

[Santiago Vila]

El 10/12/23 a las 22:09, Markus Uhlin escribió:

My guess is that Ncurses is built with '--enable-opaque-curses' and defines 
NCURSES_OPAQUE=1.
I'm currently running stable so I'm not able to reproduce the problem but if 
you can give me access to a computer where the problem occurs I can investigate 
it.


Hmm, please note that when I say "if you can't reproduce it" it should
be understood as "if you can't reproduce it using an unstable chroot".

So, you should really use an unstable chroot in your own computer
first (you can create it with debootstrap and then use it with schroot).

Regarding the bug itself: Here is a very similar one which maybe gives
you an idea about how to fix it, as it contains a fix at the end:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057553

Thanks.

Bug#1055049: libtakari-polyglot-groovy-java: missing Breaks+Replaces: libtakari-polyglot-maven-java (<< 0.4.11-2)

[Andreas Beckmann]

Ok what I think I'll do is to add: "Breaks: 
libtakari-polyglot-maven-java (<< 0.4.11-2)" to 
libtakari-polyglot-groovy-java. I think that's more explicit than a 
versioned depends, and should prevent any instances of users 
accidentally having wrong versions of the two packages.


You'll need both
  Breaks:   libtakari-polyglot-maven-java (<< 0.4.11-2)
  Replaces: libtakari-polyglot-maven-java (<< 0.4.11-2)
s.t. dkms handles the takeover of the files correctly in all poassible 
unpacking orderings.




Andreas

Bug#1057955: pkgconf: issues wrong pc_path for non-default personality

[Helmut Grohne]

Package: pkgconf
Version: 1.8.1-1
User: debian-cr...@lists.debian.org
Usertags: ftcbfs
Control: affects -1 + src:ruby-cairo
X-Debbugs-Cc: debian-cr...@lists.debian.org

Hi Andrej,

ruby-cairo fails to cross build from source. In essence, it fails to
find cairo.pc. Now ruby-cairo uses ruby-pkg-config to locate cairo.pc,
which does the lookup itself, but before it does it consults pkg-config
for the relevant paths using `$PKG_CONFIG --variable=pc_path
pkg-config`. While it doesn't pass a cross pkg-config by default, this
part is easily fixed. Unfortunately, the cross pkg-config still gives
the native search path. This is due to pkgconf containing builtin
packages for pkgconf and pkg-config see
https://sources.debian.org/src/pkgconf/1.8.1-1/libpkgconf/pkg.c/?hl=946#L990.
While the values of these builtins are personality-dependent in theory,
their implementation is not. Thus they give the wrong answer, which
explains the rest of the build failure.

Example:
$ aarch64-linux-gnu-pkg-config --variable=pc_path pkg-config
/usr/local/lib/x86_64-linux-gnu/pkgconfig:/usr/local/lib/pkgconfig:/usr/local/share/pkgconfig:/usr/lib/x86_64-linux-gnu/pkgconfig:/usr/lib/pkgconfig:/usr/share/pkgconfig
$

Fixing these is a non-trivial affair. I recommend simply deleting the
builtin mechanism and placing a pkgconf.pc and symlink pkg-config.pc
file (which is architecture-dependent) in the pkgconf package (which is
m-a:same). We can easily generate these at package build time.

Do you agree with the analysis? Do you agree with the proposed solution?
Do you see a better approach to solving this? I suspect solving this in
C would amount to rewriting the builtin mechanism in a dynamic way that
can introspect personality properties. I'd like to avoid that.

Helmut

Bug#1057954: RFS: nanomsg/1.2+dfsg-1 [ITA] -- nanomsg utilities

[Phil Wyett]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name : nanomsg
   Version  : 1.2+dfsg-1
   Upstream contact : Martin Sústrik 
 * URL  : https://nanomsg.org/
 * License  : Expat
 * Vcs  : https://salsa.debian.org/debian/nanomsg
   Section  : libs

The source builds the following binary packages:

  libnanomsg6 - high-performance implementation of scalability libraries
  libnanomsg-dev - nanomsg development files
  nanomsg-utils - nanomsg utilities

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/n/nanomsg/nanomsg_1.2+dfsg-1.dsc

Changes since the last upload:

 nanomsg (1.2+dfsg-1) unstable; urgency=medium
 .
   * New upstream version 1.2.
   * Soname bump rename package to libnanomsg6.
   * New maintainer (Closes: #871443).
   * d/control: Use debhelper-compat 13.
 - Update paths for missing files.
   * d/control: Use HTTPS homepage URL.
   * d/control: Remove unneeded '${shlibs:Depends}'.
   * d/control: Update 'Standards-Version' to 4.6.2.0 - No Changes required.
   * d/control: Add 'Rules-Requires-Root: no'.
   * d/copyright: Remove 'License: Expat' from header section.
   * Add 'd/patches/lintian-overrides'.
 - Add 'nanomsg source: debian-watch-does-not-check-openpgp-signature'.
 - Add 'nanomsg source: very-long-line-length-in-source-file'
   * Add 'd/upstream/metadata'.
   * d/watch: Use latest GitHub API format.
   * d/README.source: Remove old data about archive naming.

Regards

Phil

-- 
Playing the game for the games sake.

Web:

* Debian Wiki: https://wiki.debian.org/PhilWyett
* Website: https://kathenas.org
* Social Debian: https://pleroma.debian.social/kathenas/
* Social Instagram: https://www.instagram.com/kathenasorg/




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

Bug#1057946: pypandoc: autopkgtest needs update for new version of pandoc

[Jonas Smedegaard]

Quoting Paul Gevers (2023-12-10 21:40:34)
> Source: pypandoc
> Version: 1.7.4+ds0-2
> Severity: serious
> X-Debbugs-CC: pan...@packages.debian.org
> Tags: sid trixie
> User: debian...@lists.debian.org
> Usertags: needs-update
> Control: affects -1 src:pandoc
> 
> Dear maintainer(s),
> 
> With a recent upload of pandoc the autopkgtest of pypandoc fails in 
> testing when that autopkgtest is run with the binary packages of pandoc 
> from unstable. It passes when run with only packages from testing. In 
> tabular form:
> 
> passfail
> pandoc from testing2.17.1.1+~git20230125+ds-1
> pypandoc   from testing1.7.4+ds0-2
> all others from testingfrom testing
> 
> I copied some of the output at the bottom of this report. The failing 
> tests checks that the version of pandoc is lower than the current version.
> 
> Currently this regression is blocking the migration of pandoc to testing 
> [1]. Of course, pandoc shouldn't just break your autopkgtest (or even 
> worse, your package), but it seems to me that the change in pandoc was 
> intended and your package needs to update to the new situation.
> 
> If this is a real problem in your package (and not only in your 
> autopkgtest), the right binary package(s) from pandoc should really add 
> a versioned Breaks on the unfixed version of (one of your) package(s). 
> Note: the Breaks is nice even if the issue is only in the autopkgtest as 
> it helps the migration software to figure out the right versions to 
> combine in the tests.
> 
> More information about this bug and the reason for filing it can be found on
> https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
> 
> Paul
> 
> [1] https://qa.debian.org/excuses.php?package=pandoc
> 
> https://ci.debian.net/packages/p/pypandoc/testing/amd64/40824353/
> 
> 
>   69s ==
>   69s FAIL: test_get_pandoc_version 
> (tests.TestPypandoc.test_get_pandoc_version)
>   69s --
>   69s Traceback (most recent call last):
>   69s   File 
> "/tmp/autopkgtest-lxc._ozpb6jh/downtmp/build.wmM/src/tests.py", line 
> 159, in test_get_pandoc_version
>   69s self.assertTrue(major in [0, 1, 2])
>   69s AssertionError: False is not true

Pandoc is a library and an executable binary.  The package pandoc
version 2.17.1.1+~git20230125+ds-1 links against ghc-pandoc-dev version
3.0.1-3.

Yesterday, upstream agreed to change the versioning of the executable
binary to be in sync with the library - as was the case with 1.x and 2.x
releases.  I have just now released pandoc version 3.0.1-1.

Hope that helps.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#1057949: nbconvert: needs update for new version of pandoc: PDF creating failed

[Jonas Smedegaard]

Quoting Paul Gevers (2023-12-10 21:45:50)
> With a recent upload of pandoc the autopkgtest of nbconvert fails in 
> testing when that autopkgtest is run with the binary packages of pandoc 
> from unstable. It passes when run with only packages from testing. In 
> tabular form:
> 
> passfail
> pandoc from testing2.17.1.1+~git20230125+ds-1
> nbconvert  from testing6.5.3-4
> all others from testingfrom testing
> 
> I copied some of the output at the bottom of this report.
[...]
> 378s E 
> /usr/lib/python3/dist-packages/nbconvert/utils/pandoc.py:51: 
> RuntimeWarning: You are using an unsupported version of pandoc (3.0.1).

Pandoc is a library and an executable binary.  The package pandoc
version 2.17.1.1+~git20230125+ds-1 links against ghc-pandoc-dev version
3.0.1-3.

Yesterday, upstream agreed to change the versioning of the executable
binary to be in sync with the library - as was the case with 1.x and 2.x
releases.  I have just now released pandoc version 3.0.1-1.

Hope that helps.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#1057940: swirc: FTBFS: invalid use of incomplete typedef ‘WINDOW’ {aka ‘struct _win_st’}

[Markus Uhlin]

My guess is that Ncurses is built with '--enable-opaque-curses' and 
defines NCURSES_OPAQUE=1.
I'm currently running stable so I'm not able to reproduce the problem 
but if you can give me access to a computer where the problem occurs I 
can investigate it.


Den 2023-12-10 kl. 20:18, skrev Santiago Vila:
invalid use of incomplete typedef ‘WINDOW’ {aka ‘struct _win_st’} 

Bug#1057953: nss-myhostname: different IP address between man page and package description

[Daniele Forsi]

Package: libnss-myhostname
Version: 254.5-1
Severity: minor
X-Debbugs-Cc: dfo...@gmail.com

Dear maintainer,

the package description says:
> It returns all locally configured public IP addresses or -- if
> none are configured, the IPv4 address 127.0.1.1

the man page says:
> The local, configured hostname is resolved to [...] the IPv4 address 127.0.0.2
and the example shows 127.0.0.2 

Do they refer to different things?

greetings,
Daniele

Bug#1057952: pandoc: FTBFS on ppc64el: This version of pandoc has been compiled without Lua support.

[Sebastian Ramacher]

Source: pandoc
Version: 2.17.1.1+~git20230125+ds-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

Thanks for working on the pandoc update. Unfortunately, it fails to
build on ppc64el due to the missing lua support:

https://buildd.debian.org/status/fetch.php?pkg=pandoc=ppc64el=2.17.1.1%2B%7Egit20230125%2Bds-1=1702140012=0

dist-ghc/build/pandoc/pandoc MANUAL.txt -f markdown -t man -s \
--lua-filter man/manfilter.lua \
--include-before-body man/pandoc.1.before \
--include-after-body man/pandoc.1.after \
--metadata author="" \
--variable footer="pandoc 3.0.1+2.17.1.1+~git20230125+ds-1" \
-o man/pandoc.1
This version of pandoc has been compiled without Lua support.
make: *** [debian/rules:95: man/pandoc.1] Error 89

Cheers
-- 
Sebastian Ramacher

Bug#1056485: python-mpd's autopkg tests fail with Python 3.12

[Simon McVittie]

Control: forwarded -1 https://github.com/Mic92/python-mpd2/issues/214
Control: tags -1 + upstream help

On Wed, 22 Nov 2023 at 15:18:06 +0100, Matthias Klose wrote:
> python-mpd's autopkg tests fail with Python 3.12:
> [...]
> 248s mpd.base.ConnectionError: Can not send command to disconnected client

Fedora opened an equivalent bug upstream. No fix is currently known -
patches would be very much appreciated.

Thanks,
smcv

Bug#1043240: pandas 1.5 -> 2.1?

[Kingsley G. Morse Jr.]

Hi Rebecca, Julian and all science minded pythonistas of debian, great and 
small!

I like your correspondence about upgrading from
version 1.5 of pandas to 2.1.

It's open, scientific and explores the ideal of
proceeding wisely in a matter of public interest.

My humble thoughts are:

1.) Rebecca: *Why* did you write that you'd like
to move forward with the pandas 1.5 -> 2.1
transition? What's your reason?

2.) What may be the advantage of migrating to
version 3.0 of Cython?

3.) The following one-liner suggests 44 debian
packages might be affected by the breaks
Rebecca said would be caused by pandas 2.x:

$ for s in augur cnvkit dyda emperor esda mirtop pymatgen pyranges 
python-anndata python-biom-format python-cooler python-nanoget python-skbio 
python-ulmo q2-quality-control q2-demux q2-taxa q2-types q2templates 
sklearn-pandas ; do apt-cache search "$s" ; done | less

4.) The break that worries me the most is
sklearn-pandas, because it seems to me that
sklearn is 

popular and 

fundamental.

Comment welcome,
Kingsley

On 12/10/2023 20:16, Julian Gilbey wrote:
> On Sun, Dec 10, 2023 at 01:06:01PM +, Rebecca N. Palmer wrote:
> > I'd like to move forward with the pandas 1.5 -> 2.1 transition reasonably
> > soon.
> > 
> > Given that pandas 2.x is *not* required for Python 3.12 (but is required for
> > Cython 3.0), should we wait for the Python 3.12 transition to be done first?
> 
> Well, I have seen at least one package that has an RC bug for the
> Python 3.12 transition that might be because it's still using an old
> version of cython3 :(  So it's a bit of chicken-and-egg - having Cython
> 3.0 might be very helpful.  But then there is this list of 28 packages
> broken by pandas 2.x.  On the other hand, these will need fixing at
> some point soon anyway, so I'd be in favour of doing the pandas
> transition now, which will allow Cython 3.0 to move into unstable.
> 
> Just my 2 cents' worth...
> 
> Best wishes,
> 
>Julian
> 

-- 
Time is the fire in which we all burn.

Bug#1057951: promod3: FTBFS: No such file or directory: 'model.pdb'

[Santiago Vila]

Package: src:promod3
Version: 3.3.1+ds-1
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules binary
dh binary --with python3
   dh_update_autotools_config
   dh_autoreconf
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- \
-DOPTIMIZE=ON -DDISABLE_DOCUMENTATION=ON -DOST_ROOT=/usr 
-DCOMPOUND_LIB=/var/cache/openstructure/compounds.chemlib
cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb cmake 
-DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON 
-DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
-DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DOPTIMIZE=ON -DDISABLE_DOCUMENTATION=ON 
-DOST_ROOT=/usr -DCOMPOUND_LIB=/var/cache/openstructure/compounds.chemlib ..
-- The CXX compiler identification is GNU 13.2.0
-- The C compiler identification is GNU 13.2.0
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped

[... snipped ...]

make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make  -f loop/pymod/CMakeFiles/loop_pymod.dir/build.make 
loop/pymod/CMakeFiles/loop_pymod.dir/build
make[4]: Entering directory '/<>/obj-x86_64-linux-gnu'
cd /<>/obj-x86_64-linux-gnu/loop/pymod && /usr/bin/cmake -E copy_if_different 
/<>/loop/pymod/__init__.py 
/<>/obj-x86_64-linux-gnu/stage/lib64/python3.11/site-packages//promod3/loop/__init__.py
cd /<>/obj-x86_64-linux-gnu/loop/src && /usr/bin/cmake -E copy_if_different 
/<>/loop/src/./backbone.hh 
/<>/obj-x86_64-linux-gnu/stage/include/promod3/loop/./backbone.hh
make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
[  0%] Built target loop_pymod
make  -f scoring/src/CMakeFiles/promod3_scoring_headers.dir/build.make 
scoring/src/CMakeFiles/promod3_scoring_headers.dir/depend
make[4]: Entering directory '/<>/obj-x86_64-linux-gnu'
cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<> 
/<>/scoring/src /<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu/scoring/src 
/<>/obj-x86_64-linux-gnu/scoring/src/CMakeFiles/promod3_scoring_headers.dir/DependInfo.cmake "--color="
cd /<>/obj-x86_64-linux-gnu/loop/src && /usr/bin/cmake -E copy_if_different 
/<>/loop/src/./bb_trace_param.hh 
/<>/obj-x86_64-linux-gnu/stage/include/promod3/loop/./bb_trace_param.hh
make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make  -f scoring/src/CMakeFiles/promod3_scoring_headers.dir/build.make 
scoring/src/CMakeFiles/promod3_scoring_headers.dir/build
cd /<>/obj-x86_64-linux-gnu/loop/src && /usr/bin/cmake -E copy_if_different 
/<>/loop/src/./data_bag.hh 
/<>/obj-x86_64-linux-gnu/stage/include/promod3/loop/./data_bag.hh
make[4]: Entering directory '/<>/obj-x86_64-linux-gnu'
cd /<>/obj-x86_64-linux-gnu/scoring/src && /usr/bin/cmake -E copy_if_different 
/<>/scoring/src/./backbone_score_base.hh 
/<>/obj-x86_64-linux-gnu/stage/include/promod3/scoring/./backbone_score_base.hh
cd /<>/obj-x86_64-linux-gnu/scoring/src && /usr/bin/cmake -E copy_if_different 
/<>/scoring/src/./backbone_overall_scorer.hh 
/<>/obj-x86_64-linux-gnu/stage/include/promod3/scoring/./backbone_overall_scorer.hh
cd /<>/obj-x86_64-linux-gnu/loop/src && /usr/bin/cmake -E copy_if_different 
/<>/loop/src/./dense_hash_table.hh 
/<>/obj-x86_64-linux-gnu/stage/include/promod3/loop/./dense_hash_table.hh
cd /<>/obj-x86_64-linux-gnu/scoring/src && /usr/bin/cmake -E copy_if_different 
/<>/scoring/src/./scoring_object_loader.hh 
/<>/obj-x86_64-linux-gnu/stage/include/promod3/scoring/./scoring_object_loader.hh
cd /<>/obj-x86_64-linux-gnu/loop/src && /usr/bin/cmake -E copy_if_different 
/<>/loop/src/./dense_map.hh 
/<>/obj-x86_64-linux-gnu/stage/include/promod3/loop/./dense_map.hh
cd /<>/obj-x86_64-linux-gnu/loop/src && /usr/bin/cmake -E copy_if_different 
/<>/loop/src/./dense_map.hh 
/<>/obj-x86_64-linux-gnu/stage/include/promod3/loop/./dense_map.hh
cd /<>/obj-x86_64-linux-gnu/loop/src && /usr/bin/cmake -E copy_if_different 
/<>/loop/src/./density_creator.hh 
/<>/obj-x86_64-linux-gnu/stage/include/promod3/loop/./density_creator.hh
cd /<>/obj-x86_64-linux-gnu/loop/src && /usr/bin/cmake -E copy_if_different 
/<>/loop/src/./forcefield_lookup.hh 
/<>/obj-x86_64-linux-gnu/stage/include/promod3/loop/./forcefield_lookup.hh
cd /<>/obj-x86_64-linux-gnu/loop/src && /usr/bin/cmake -E copy_if_different 
/<>/loop/src/./frag_db.hh 
/<>/obj-x86_64-linux-gnu/stage/include/promod3/loop/./frag_db.hh
cd /<>/obj-x86_64-linux-gnu/scoring/src && /usr/bin/cmake -E copy_if_different 
/<>/scoring/src/./cbeta_env_listener.hh 

Bug#1057950: dask.distributed: FTBFS: TypeError: not all arguments converted during string formatting

[Santiago Vila]

Package: src:dask.distributed
Version: 2023.8.0+ds.1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules binary
dh binary --with python3,sphinxdoc --buildsystem=pybuild
   dh_update_autotools_config -O--buildsystem=pybuild
   dh_autoreconf -O--buildsystem=pybuild
   dh_auto_configure -O--buildsystem=pybuild
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
rm -f distributed/comm/tests/__init__.py
set -e; \
for p in distributed/http/static/js/anime.js 
distributed/http/static/js/reconnecting-websocket.js; do \
uglifyjs -o $p debian/missing-sources/$p ; \
done
chmod a-x distributed/tests/test_utils_test.py
dh_auto_build

[... snipped ...]

copying build/lib/distributed/cli/tests/__init__.py -> 
build/bdist.linux-x86_64/wheel/distributed/cli/tests
copying build/lib/distributed/cli/tests/test_dask_spec.py -> 
build/bdist.linux-x86_64/wheel/distributed/cli/tests
copying build/lib/distributed/cli/tests/test_dask_worker.py -> 
build/bdist.linux-x86_64/wheel/distributed/cli/tests
copying build/lib/distributed/cli/tests/test_dask_scheduler.py -> 
build/bdist.linux-x86_64/wheel/distributed/cli/tests
copying build/lib/distributed/cli/tests/test_dask_ssh.py -> 
build/bdist.linux-x86_64/wheel/distributed/cli/tests
copying build/lib/distributed/cli/tests/test_tls_cli.py -> 
build/bdist.linux-x86_64/wheel/distributed/cli/tests
copying build/lib/distributed/cli/dask_worker.py -> 
build/bdist.linux-x86_64/wheel/distributed/cli
copying build/lib/distributed/cli/dask_scheduler.py -> 
build/bdist.linux-x86_64/wheel/distributed/cli
copying build/lib/distributed/cli/dask_spec.py -> 
build/bdist.linux-x86_64/wheel/distributed/cli
copying build/lib/distributed/cli/dask_ssh.py -> 
build/bdist.linux-x86_64/wheel/distributed/cli
copying build/lib/distributed/active_memory_manager.py -> 
build/bdist.linux-x86_64/wheel/distributed
copying build/lib/distributed/versions.py -> 
build/bdist.linux-x86_64/wheel/distributed
copying build/lib/distributed/lock.py -> 
build/bdist.linux-x86_64/wheel/distributed
creating build/bdist.linux-x86_64/wheel/distributed/deploy
copying build/lib/distributed/deploy/local.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy
copying build/lib/distributed/deploy/utils.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy
copying build/lib/distributed/deploy/__init__.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy
creating build/bdist.linux-x86_64/wheel/distributed/deploy/tests
copying build/lib/distributed/deploy/tests/test_cluster.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy/tests
copying build/lib/distributed/deploy/tests/test_adaptive_core.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy/tests
copying build/lib/distributed/deploy/tests/test_ssh.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy/tests
copying build/lib/distributed/deploy/tests/test_spec_cluster.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy/tests
copying build/lib/distributed/deploy/tests/test_local.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy/tests
copying build/lib/distributed/deploy/tests/test_slow_adaptive.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy/tests
copying build/lib/distributed/deploy/tests/test_deploy_utils.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy/tests
copying build/lib/distributed/deploy/tests/test_subprocess.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy/tests
copying build/lib/distributed/deploy/tests/test_old_ssh.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy/tests
copying build/lib/distributed/deploy/tests/test_adaptive.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy/tests
copying build/lib/distributed/deploy/adaptive.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy
copying build/lib/distributed/deploy/cluster.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy
copying build/lib/distributed/deploy/adaptive_core.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy
copying build/lib/distributed/deploy/spec.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy
copying build/lib/distributed/deploy/old_ssh.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy
copying build/lib/distributed/deploy/ssh.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy
copying build/lib/distributed/deploy/subprocess.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy
creating build/bdist.linux-x86_64/wheel/distributed/shuffle
copying build/lib/distributed/shuffle/_merge.py -> 
build/bdist.linux-x86_64/wheel/distributed/shuffle
copying build/lib/distributed/shuffle/__init__.py -> 
build/bdist.linux-x86_64/wheel/distributed/shuffle
copying build/lib/distributed/shuffle/_disk.py -> 
build/bdist.linux-x86_64/wheel/distributed/shuffle
copying build/lib/distributed/shuffle/_worker_plugin.py -> 

Bug#1057949: nbconvert: needs update for new version of pandoc: PDF creating failed

[Paul Gevers]

Source: nbconvert
Version: 6.5.3-4
Severity: serious
X-Debbugs-CC: pan...@packages.debian.org
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:pandoc

Dear maintainer(s),

With a recent upload of pandoc the autopkgtest of nbconvert fails in 
testing when that autopkgtest is run with the binary packages of pandoc 
from unstable. It passes when run with only packages from testing. In 
tabular form:


   passfail
pandoc from testing2.17.1.1+~git20230125+ds-1
nbconvert  from testing6.5.3-4
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of pandoc to testing 
[1]. Of course, pandoc shouldn't just break your autopkgtest (or even 
worse, your package), but it seems to me that the change in pandoc was 
intended and your package needs to update to the new situation.


If this is a real problem in your package (and not only in your 
autopkgtest), the right binary package(s) from pandoc should really add 
a versioned Breaks on the unfixed version of (one of your) package(s). 
Note: the Breaks is nice even if the issue is only in the autopkgtest as 
it helps the migration software to figure out the right versions to 
combine in the tests.


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

Paul

[1] https://qa.debian.org/excuses.php?package=pandoc

https://ci.debian.net/data/autopkgtest/testing/amd64/n/nbconvert/40824350/log.gz

378s E 
/usr/lib/python3/dist-packages/nbconvert/utils/pandoc.py:51: 
RuntimeWarning: You are using an unsupported version of pandoc (3.0.1).
378s E   Your version must be at least (1.12.1) but 
less than (3.0.0).

378s E   Refer to https://pandoc.org/installing.html.
378s E   Continuing with doubts...
378s E check_pandoc_version()
378s E   [NbConvertApp] Support files will be in 
notebook2_files/
378s E   [NbConvertApp] Making directory 
./notebook2_files
378s E   [NbConvertApp] Writing 2889 bytes to support 
file ./notebook2_files/notebook2_13_1.png
378s E   [NbConvertApp] Making directory 
./notebook2_files
378s E   [NbConvertApp] Writing 74369 bytes to support 
file ./notebook2_files/notebook2_13_1.pdf
378s E   [NbConvertApp] Writing 25528 bytes to 
notebook.tex

378s E   [NbConvertApp] Building PDF
378s E   [NbConvertApp] Running xelatex 1 time: 
['xelatex', 'notebook.tex', '-quiet']
378s E   [NbConvertApp] CRITICAL | xelatex failed: 
['xelatex', 'notebook.tex', '-quiet']

378s E   
378s E   Traceback (most recent call last):
378s E File "", line 198, in 
_run_module_as_main

378s E File "", line 88, in _run_code
378s E File 
"/usr/lib/python3/dist-packages/nbconvert/__main__.py", line 3, in 


378s E   main()
378s E File 
"/usr/lib/python3/dist-packages/jupyter_core/application.py", line 282, 
in launch_instance
378s E   super().launch_instance(argv=argv, 
**kwargs)
378s E File 
"/usr/lib/python3/dist-packages/traitlets/config/application.py", line 
982, in launch_instance

378s E   app.start()
378s E File 
"/usr/lib/python3/dist-packages/nbconvert/nbconvertapp.py", line 423, in 
start

378s E   self.convert_notebooks()
378s E File 
"/usr/lib/python3/dist-packages/nbconvert/nbconvertapp.py", line 597, in 
convert_notebooks
378s E 
self.convert_single_notebook(notebook_filename)
378s E File 
"/usr/lib/python3/dist-packages/nbconvert/nbconvertapp.py", line 560, in 
convert_single_notebook
378s E   output, resources = 
self.export_single_notebook(
378s E 

378s E File 
"/usr/lib/python3/dist-packages/nbconvert/nbconvertapp.py", line 488, in 
export_single_notebook
378s E   output, resources = 
self.exporter.from_filename(
378s E 

378s E File 
"/usr/lib/python3/dist-packages/nbconvert/exporters/exporter.py", line 
189, in from_filename
378s E   return self.from_file(f, 
resources=resources, **kw)
378s E 

378s E File 

Bug#1057932: kgb-bot: FTBFS: Failed test 'Changes contains all valid release dates'

[gregor herrmann]

COntrol: tag -1 + confirmed

On Sun, 10 Dec 2023 20:17:56 +0100, Santiago Vila wrote:

> During a rebuild of all packages in unstable, your package failed to build:

> #   Failed test 'Changes contains all valid release dates'
> #   at t/changes.t line 6.
> #   ERR: No date for version 1.59 (line 1)
> # Looks like you failed 1 test of 6.
> t/changes.t ...
> ok 1 - Changes is loadable
> ok 2 - Changes contains at least one release
> not ok 3 - Changes contains all valid release dates
> ok 4 - Changes contains all valid release versions
> ok 5 - Changes has an entry for version 1.59
> ok 6 - Changes version 1.59 has content
> 1..6
> Dubious, test returned 1 (wstat 256, 0x100)
> Failed 1/6 subtests

t/changes.t uses Test::CPAN::Changes in libcpan-changes-perl, which
was recently updated.

I guess, writing the "headers" in ./Changes as "1.59 2023-10-30" or
"1.59 - 2023-10-30" instead of "1.59 (2023-10-30)" could work.

(Maybe also guarding a few tests in t/ with RELEASE_TESTING …)

Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature

Bug#1057842: mini-httpd: Update of mini-httpd breaks default web page if it is not index.html

[Alexandru Mihail]

Hi,
Thanks for reporting this bug !
I retested your actions and successfully reproduced the problem.
This is an older patch before my role here, why index.mini-httpd.html
is in the second slot in that array eludes me totally. (probably
historic reasons ?)
> https://sources.debian.org/patches/mini-httpd/1.30-3/0003-fix-change-index-document-root/
> 
> The real problem is that
> https://salsa.debian.org/debian/mini-httpd/-/blob/master/debian/mini-httpd.postinst
> creates the file /var/www/html/index.mini-httpd.html at all, and that
> https://sources.debian.org/patches/mini-httpd/1.30-3/0003-fix-change-index-document-root/
> modifies the binary to deliver this file.
> 
Agreed, thanks for your detective work !
> A more sane way would be to follow the example of Apache, delivering
> a 
> default
> /var/www/html/index.html when the package is installed, update it
> only 
> if it is
> unmodified, and do not recreate it when the package is updated. That 
> way, the entire patch
> https://sources.debian.org/patches/mini-httpd/1.30-3/0003-fix-change-index-document-root/
> can be omitted and mini-httpd works as intended.

This is the solution I was considering as well; We're already shipping
the frugal default index.html which postinst is manually copying into /
var/www/html. Copying files like that in postinst is frowned upon,
anyway; package files, if possible, should be handled properly from the
beginning. I was thinking of removing 0003-fix-change-index-document-
root.patch all together; move the default index.html in the package
filesystem into /var/www/html/index.html and not recreating it if it's
dirty.

I find that an elegant solution to this problem. The only think we'd
break is any external scripts which would depend on index.mini-
httpd.html existing. I know of no such scripts, but other people's
packages might/might not complain. Maybe worth investigating.
This is a pretty important bug as it affects the version in stable,
too, not only sid/testing (1.30-3), so thanks for reporting, again !

If everything works as expected, I plan on releasing another update
1.30-6 the next week; I want to lump this bugfix together with some
general cleanup of the existing patches.

If you have any other questions/suggestions please reply to the bug.

Thanks !

Alexandru Mihail
mini-httpd maintainer




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

Bug#1057948: catch2: wrongly marked Multi-Arch: foreign

[Helmut Grohne]

Package: catch2
Version: 2.11.3-2
Severity: important
User: debian-cr...@lists.debian.org
Usertags: ftcbfs
Control: affects -1 + src:libodsstream

libodsstream fails to cross build from source, because linking catch2
fails. This is due to catch2 having been wrongly marked Multi-Arch:
foreign. That marking asserts that interfacing with catch2 is
architecture-independent. A static library does not comply with this
property. You must either remove Multi-Arch: foreign or remove all
static libraries from the catch2 package (e.g. moving them to a
different package that is not marked Multi-arch: foreign).

Please remove Multi-Arch: foreign asap. At least temporarily.

Helmut

Bug#1057947: hp48cc: missing error trapping in Makefile

[Helmut Grohne]

Source: hp48cc
Version: 1.0-3
Severity: serious
Justification: policy section 4.6

Debian policy section 4.6 requires that failures from a build step are
propagated rather than continuing and possibly misbuilding. hp48cc
violates this in the upstream build system. The toplevel Makefile.in
says:

| all install clean realclean mostyclean:
|   @for f in $(subdirs); do \
|   (cd $$f && $(MAKE) $@) \
|   done

If any of these fails, no failure is raised and the build continues. I
suggest adding "set -e" before the loop to fix this.

Helmut

Bug#1057946: pypandoc: autopkgtest needs update for new version of pandoc

[Paul Gevers]

Source: pypandoc
Version: 1.7.4+ds0-2
Severity: serious
X-Debbugs-CC: pan...@packages.debian.org
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:pandoc

Dear maintainer(s),

With a recent upload of pandoc the autopkgtest of pypandoc fails in 
testing when that autopkgtest is run with the binary packages of pandoc 
from unstable. It passes when run with only packages from testing. In 
tabular form:


   passfail
pandoc from testing2.17.1.1+~git20230125+ds-1
pypandoc   from testing1.7.4+ds0-2
all others from testingfrom testing

I copied some of the output at the bottom of this report. The failing 
tests checks that the version of pandoc is lower than the current version.


Currently this regression is blocking the migration of pandoc to testing 
[1]. Of course, pandoc shouldn't just break your autopkgtest (or even 
worse, your package), but it seems to me that the change in pandoc was 
intended and your package needs to update to the new situation.


If this is a real problem in your package (and not only in your 
autopkgtest), the right binary package(s) from pandoc should really add 
a versioned Breaks on the unfixed version of (one of your) package(s). 
Note: the Breaks is nice even if the issue is only in the autopkgtest as 
it helps the migration software to figure out the right versions to 
combine in the tests.


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

Paul

[1] https://qa.debian.org/excuses.php?package=pandoc

https://ci.debian.net/packages/p/pypandoc/testing/amd64/40824353/


 69s ==
 69s FAIL: test_get_pandoc_version 
(tests.TestPypandoc.test_get_pandoc_version)

 69s --
 69s Traceback (most recent call last):
 69s   File 
"/tmp/autopkgtest-lxc._ozpb6jh/downtmp/build.wmM/src/tests.py", line 
159, in test_get_pandoc_version

 69s self.assertTrue(major in [0, 1, 2])
 69s AssertionError: False is not true


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1055316: heimdal: fails to build against glibc 2.38

[Samuel Thibault]

Hello,

Brian May, le dim. 10 déc. 2023 09:18:47 +1100, a ecrit:
> Samuel Thibault  writes:
> > I checked all *_amd64.so packages, apparently libafsauthent2 is using
> > rk_strlcpy and rk_strlcat from libroken, so a Breaks transition is
> > needed for that.
> 
> Whaat is the process for a breaks transition?

Some details examples are discussed in Bug#1043184 in the case of krb5.

Samuel

Bug#910664: Acknowledgement (ghc: ghc package can no longer be cross-compiled)

[Helmut Grohne]

user debian-cr...@lists.debian.org
usertags 910664 + ftcbfs
tags 910664 + patch
thanks

Hi,

Given that the earlier bug about haskell-devscripts-minimal has been
fixed, I happen to have looked into this.

First and foremost, ghc now actively refuses being cross build with an
$(error ...). Would you mind weakening this to a $(warning ...)? While
that you don't want to support cross building of ghc, would you mind
others (like me) supporting it? Yes, it would still fail, but then
https://crossqa.debian.net/src/ghc could show a more useful reason for
that failure. (patch attached)

Then when you get past the $(error ...), stage1 tools are not found. In
a cross build, ghc prefixes these with the host gnu triplet. A bit of
renaming is required to make this work. (patch attached)

And then we run into:

On Tue, Oct 09, 2018 at 03:24:41PM +0200, John Paul Adrian Glaubitz wrote:
> This change to the debian/rules file helps to get a bit further:
> 
> --- debian/rules.orig   2018-09-26 11:08:46.0 +0200
> +++ debian/rules2018-10-09 15:22:43.080942145 +0200
> @@ -126,6 +126,7 @@
> echo 'V=1' >> mk/build.mk
> dh_auto_configure -- \
> $(EXTRA_CONFIGURE_FLAGS) \
> +   --host=$(DEB_BUILD_GNU_TYPE) \
> --with-system-libffi --libdir=/usr/lib
>  
>  override_dh_auto_build:
> 
> But it will still fail with:

I think this is wrong. The current ghc packaging includes this flag, but
ghc uses the same terminology as Debian, so when we say
--host=$(DEB_BUILD_GNU_TYPE) we ask it to produce a cross compiler, but
we really wanted a cross built ghc. One of the issues referenced from
the earlier $(error ...) also hints that this value is wrong for --host:
https://gitlab.haskell.org/ghc/ghc/-/issues/22006 Unless you have strong
reasons for why that should be correct, I suggest that we change it to
--host=$(DEB_HOST_GNU_TYPE). (not included in patch)

So this is where we are. I think we can make progress here if you want
to support this work. I'm also a big fan of actionable bug reports and
in having a patch, this bug becomes actionable. Given that you (ghc
maintainers) are evidently not interested in doing the work here, I also
suggest that you close this bug when applying the patch and letting
cross users file new bugs with new patches. Let me know what you think
about this.

Helmut
diff --minimal -Nru ghc-9.4.7/debian/changelog ghc-9.4.7/debian/changelog
--- ghc-9.4.7/debian/changelog  2023-10-18 21:50:19.0 +0200
+++ ghc-9.4.7/debian/changelog  2023-12-10 20:03:52.0 +0100
@@ -1,3 +1,10 @@
+ghc (9.4.7-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Improve cross building. (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 10 Dec 2023 20:03:52 +0100
+
 ghc (9.4.7-1) unstable; urgency=medium
 
   * Upload to unstable
diff --minimal -Nru ghc-9.4.7/debian/rules ghc-9.4.7/debian/rules
--- ghc-9.4.7/debian/rules  2023-10-18 21:49:38.0 +0200
+++ ghc-9.4.7/debian/rules  2023-12-10 20:03:52.0 +0100
@@ -47,8 +47,10 @@
   EXTRA_HADRIAN_FLAGS += --flavour=quickest
   # Do not build docs *at all* (avoid dependency on Sphinx)
   EXTRA_HADRIAN_FLAGS += --docs=none
+  STAGE1_TOOL = _build/stage1/bin/$(DEB_HOST_GNU_TYPE)-
   BUILD_CROSS = YES
 else
+  STAGE1_TOOL = _build/stage1/bin/
   BUILD_CROSS = NO
 endif
 
@@ -149,7 +151,7 @@
 ifeq (YES,$(BUILD_CROSS))
# See https://gitlab.haskell.org/ghc/ghc/-/issues/23975
# and https://gitlab.haskell.org/ghc/ghc/-/issues/22006
-   $(error cross-compilation is not supported)
+   $(warning cross-compilation is not supported)
 endif
hadrian/hadrian \
-V -j \
@@ -162,7 +164,7 @@
# correct), but we use ghc-pkg from stage2 when we generate our control 
file.
# Maybe we should consider using ghc-pkg from binary-dist-dir instead.
# As a work-around for now, regenerate the stage2 package cache.
-   _build/stage1/bin/ghc-pkg recache
+   $(STAGE1_TOOL)ghc-pkg recache
 
 # This rule is a superset of 'override_dh_auto_build-arch'. It builds 
everything
 # that the '-arch' rule builds, and then docs on top.
@@ -185,7 +187,7 @@
# correct), but we use ghc-pkg from stage2 when we generate our control 
file.
# Maybe we should consider using ghc-pkg from binary-dist-dir instead.
# As a work-around for now, regenerate the stage2 package cache.
-   _build/stage1/bin/ghc-pkg recache
+   $(STAGE1_TOOL)ghc-pkg recache
 
 
 # 
@@ -335,23 +337,23 @@
rm -rf debian/testghc
mkdir debian/testghc
echo 'main = putStrLn "Foo"' > debian/testghc/foo.hs
-   _build/stage1/bin/ghc debian/testghc/foo.hs -o debian/testghc/foo
+   $(STAGE1_TOOL)ghc debian/testghc/foo.hs -o debian/testghc/foo
[ "$$(debian/testghc/foo)" = "Foo" ]
rm debian/testghc/*
echo 'main = 

Bug#578953: No clamd causes clamassassin to crash fetchmail - Patches

[Shubhra Prakash Nandi]

You can apply either of the below patches and test. I had a different
version of clamassassin and patch 1 worked for me. Idea is to
fix/remove the multiline header which clamassassin is trying to add
when it gets an error code other than 0 or 1. The source below is the
debian package source and not what finally gets deployed on the system.


** Patch 1 **

--- clamassassin.in 2007-03-05 09:49:48.0 +0530
+++ clamassassin_fixed1.in  2023-12-11 01:16:47.649663604 +0530
@@ -147,9 +147,9 @@
   MINOR=`${SIGTOOL} --stdout -i ${SIGLOC}/daily.cvd \
 | ${SED} -e "/^Version: /!d" -e "s/.* //"`
   SIGVERS="${MAJOR}.${MINOR}"
-  VERSION="@PACKAGE_STRING@ with ${CLAMVERS} signatures ${SIGVERS}"
+  VERSION=`echo @PACKAGE_STRING@ with ${CLAMVERS} signatures
${SIGVERS}`
 else
-  VERSION="@PACKAGE_STRING@ with ${CLAMVERS}"
+  VERSION=`echo @PACKAGE_STRING@ with ${CLAMVERS}`
 fi
 
 # Have ClamAV check the message and save the simple results in the log






** Patch 2 **

--- clamassassin.in 2007-03-05 09:49:48.0 +0530
+++ clamassassin_fixed2.in  2023-12-11 01:17:40.621836298 +0530
@@ -187,8 +187,7 @@
   else
 # If the result was not 0 or 1 then some sort of error occured
 ${FORMAIL} -f -I "X-Virus-Status: Failed" -I \
-  "X-Virus-Report: ${CLAMSCAN} error ${RESULT}" \
-  -I "X-Virus-Checker-Version: ${VERSION}" < ${MSGTMP}
+  "X-Virus-Report: ${CLAMSCAN} error ${RESULT}" < ${MSGTMP}
 bailiferr $?
   fi
 fi






Regards,

Shubhra Prakash Nandi

Founder and CEO,
ISUB SOFTWARES (OPC) PRIVATE LIMITED

Phone: +91-9871482815

Bug#1040933: Packages from buster cannot be build on bookworm and bullseye.

[Christian T. Steigies]

On 12/8/23 18:55, Martin wrote:

On 2023-12-06 18:14, Christian Schulte wrote:

The trac package of bookworm-backports is
broken.


At least not entirely: I'm using it every day at my workplace.
Maybe it is broken when used with Apache?
In my job, we use Trac with nginx and gunicorn.
Maybe that is a possible workaround for you, too?


Still works for me when libapache2-mod-python has a "correct" version:

trac:
  Installed: 1.6-2~bpo12+1
libapache2-mod-python:
  Installed: 3.5.0.1-1

Christian

Bug#1043240: transition: pandas 1.5 -> 2.1

[Julian Gilbey]

On Sun, Dec 10, 2023 at 01:06:01PM +, Rebecca N. Palmer wrote:
> I'd like to move forward with the pandas 1.5 -> 2.1 transition reasonably
> soon.
> 
> Given that pandas 2.x is *not* required for Python 3.12 (but is required for
> Cython 3.0), should we wait for the Python 3.12 transition to be done first?

Well, I have seen at least one package that has an RC bug for the
Python 3.12 transition that might be because it's still using an old
version of cython3 :(  So it's a bit of chicken-and-egg - having Cython
3.0 might be very helpful.  But then there is this list of 28 packages
broken by pandas 2.x.  On the other hand, these will need fixing at
some point soon anyway, so I'd be in favour of doing the pandas
transition now, which will allow Cython 3.0 to move into unstable.

Just my 2 cents' worth...

Best wishes,

   Julian

Bug#1057945: xorg-server: use udev.pc to place udev rules

[Chris Hofstaedtler]

Source: xorg-server
Version: 21.1.9-1
Severity: normal
Tags: patch
User: helm...@debian.org
Usertags: dep17m2

Dear Maintainer,

your package installs files related to udev, into /lib. These
files need to be moved to /usr/lib as part of Debian's usr-merge
effort [1].

Attached you will find a patch to delegate the exact placement of
the udev files to udev.pc (using pkg-config). This works today
in unstable and also for bookworm.
Once udev.pc in unstable points to /usr/lib your package will
benefit automatically after a binNMU or any other upload.

If during the trixie cycle your package will undergo structural
changes or any other file moves, please see the wiki and upload
to experimental first when these changes are done.

Later during the trixie cycle I expect this bug class to raise in
priority.

Thank you for considering,
Chris

[1] https://wiki.debian.org/UsrMerge
diff -u xorg-server-21.1.9/debian/changelog xorg-server-21.1.9/debian/changelog
--- xorg-server-21.1.9/debian/changelog
+++ xorg-server-21.1.9/debian/changelog
@@ -1,3 +1,10 @@
+xorg-server (2:21.1.9-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Use udev.pc to place udev files. (Closes: #-1)
+
+ -- Chris Hofstaedtler   Sun, 10 Dec 2023 20:49:20 +0100
+
 xorg-server (2:21.1.9-1) unstable; urgency=medium
 
   * New upstream release.
diff -u xorg-server-21.1.9/debian/control xorg-server-21.1.9/debian/control
--- xorg-server-21.1.9/debian/control
+++ xorg-server-21.1.9/debian/control
@@ -73,6 +73,7 @@
   libdbus-1-dev (>= 1.0) [linux-any],
 # systemd-daemon
   libsystemd-dev [linux-any],
+  systemd-dev [linux-any],
 Build-Depends-Indep: xz-utils
 Standards-Version: 3.9.8
 Rules-Requires-Root: binary-targets
diff -u xorg-server-21.1.9/debian/rules xorg-server-21.1.9/debian/rules
--- xorg-server-21.1.9/debian/rules
+++ xorg-server-21.1.9/debian/rules
@@ -4,6 +4,10 @@
 
 include /usr/share/dpkg/architecture.mk
 
+ifeq ($(DEB_HOST_ARCH_OS), linux)
+deb_udevdir = $(shell pkg-config --variable=udevdir udev)
+endif
+
 %:
 	dh $@ --with quilt
 
@@ -129,10 +133,10 @@
 	install -m 755 -d debian/xserver-xorg-core/usr/share/bug/xserver-xorg-core
 	install -m 755 debian/xserver-xorg-core.bug.script debian/xserver-xorg-core/usr/share/bug/xserver-xorg-core/script
 ifeq ($(DEB_HOST_ARCH_OS), linux)
-	install -d debian/xserver-xorg-core/lib/udev/rules.d
-	install -m 644 debian/local/64-xorg-xkb.rules debian/xserver-xorg-core/lib/udev/rules.d
-	install -d debian/xserver-xorg-core-udeb/lib/udev/rules.d
-	install -m 644 debian/local/64-xorg-xkb.rules debian/xserver-xorg-core-udeb/lib/udev/rules.d
+	install -d debian/xserver-xorg-core$(deb_udevdir)/rules.d
+	install -m 644 debian/local/64-xorg-xkb.rules debian/xserver-xorg-core$(deb_udevdir)/rules.d
+	install -d debian/xserver-xorg-core-udeb$(deb_udevdir)/rules.d
+	install -m 644 debian/local/64-xorg-xkb.rules debian/xserver-xorg-core-udeb$(deb_udevdir)/rules.d
 endif
 
 override_dh_missing-indep:

Bug#1057926: 403 Access Denied on some packages on official Debian repo

[Salvatore Bonaccorso]

Hi,

On Sun, Dec 10, 2023 at 07:03:43PM +, Juan J. Fernandez wrote:
> Package: linux-image-6.1.0-14-rt-amd64
> Version: 6.1.64-1
> 
> When I run apt upgrade command it shows Error 403 Access Denied
> Here is a transcript:
> 
> E: Failed to fetch 
> http://ftp.debian.org/debian/pool/main/l/linux-signed-amd64/linux-image-6.1.0-14-rt-amd64_6.1.64-1_amd64.deb
>   403  Access denied - broken package [IP: 151.101.126.132 80]
> 
> I suggest that the file permissions be corrected
> 
> I am using Debian GNU/Linux 12 Bookworm, kernel 6.5.11-7-pve

Please see: https://www.debian.org/News/2023/2023120902

Regards,
Salvatore

Bug#960382: pushover: Renamed to Domino-Chain

[Alexandre Detiste]

Hi,

> What is the fastest way to fetch that upcoming version of
> game-data-packager?

The fastest way is to use Debian testing or stable and build from source:
   https://salsa.debian.org/games-team/game-data-packager
   The learning curve might be steep depending your experience with Debian,

Alternatively I publish a Ubuntu PPA here:
  https://launchpad.net/~alexandre-detiste/+archive/ubuntu/ppa/+packages

The _releases_ also trickle also in RPMFusion add-on for Fedora.
(RPMFusion is even in worse shape than EPEL ...)

> (Alternatively, feel free to provide a patch resp. merge request
> via GitLab.)

I will likely provide a patch next week.

Greetings,

Le jeu. 7 déc. 2023 à 08:18, Volker Diels-Grabsch  a écrit :
>
> Hi Alexandre,
>
> (Cc to Andreas, who is the main author of Domino-Chain)
>
> This sounds great!

Thanks :-)

Bug#1057943: haproxy: use systemd.pc to place systemd system units

[Chris Hofstaedtler]

Source: haproxy
Version: 2.8.5-1
Severity: normal
Tags: patch
User: helm...@debian.org
Usertags: dep17m2

Dear Maintainer,

your package installs systemd system units, currently into /lib.
These files need to be moved to /usr/lib as part of Debian's usr-merge
effort [1].

Attached you will find a patch to delegate the exact placement of
these files to systemd.pc (using pkg-config). This immediately works
in unstable, placing the files into /usr/lib.
It also works for backports to older releases, where it will continue
install into /lib.
Note that the patch is based upon haproxy from experimental.

The patch inside the debdiff is probably suitable for upstream, if
you want to forward it.

If during the trixie cycle your package will undergo structural
changes or any other file moves, please see the wiki and upload
to experimental first when these changes are done.

Later during the trixie cycle I expect this bug class to raise in
priority.

Thank you for considering,
Chris

[1] https://wiki.debian.org/UsrMerge

diff -Nru haproxy-2.9.0/debian/changelog haproxy-2.9.0/debian/changelog
--- haproxy-2.9.0/debian/changelog	2023-12-09 15:33:05.0 +0100
+++ haproxy-2.9.0/debian/changelog	2023-12-10 20:15:00.0 +0100
@@ -1,3 +1,10 @@
+haproxy (2.9.0-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Use dh_installsystemd to install .service files
+
+ -- Chris Hofstaedtler   Sun, 10 Dec 2023 20:15:00 +0100
+
 haproxy (2.9.0-1) experimental; urgency=medium
 
   * New upstream release.
diff -Nru haproxy-2.9.0/debian/control haproxy-2.9.0/debian/control
--- haproxy-2.9.0/debian/control	2023-12-09 15:33:05.0 +0100
+++ haproxy-2.9.0/debian/control	2023-12-10 20:15:00.0 +0100
@@ -14,7 +14,8 @@
libjemalloc-dev,
python3-sphinx,
libopentracing-c-wrapper-dev,
-   pkg-config
+   pkg-config,
+   systemd-dev [linux-any]
 Build-Depends-Indep: python3, python3-mako
 Homepage: http://www.haproxy.org/
 Vcs-Git: https://salsa.debian.org/haproxy-team/haproxy.git
diff -Nru haproxy-2.9.0/debian/haproxy.install haproxy-2.9.0/debian/haproxy.install
--- haproxy-2.9.0/debian/haproxy.install	2023-12-09 15:33:05.0 +0100
+++ haproxy-2.9.0/debian/haproxy.install	2023-12-10 20:14:28.0 +0100
@@ -1,4 +1,3 @@
 debian/haproxy.cfg etc/haproxy
 examples/errorfiles/*.http etc/haproxy/errors
-admin/systemd/haproxy.service lib/systemd/system
 admin/halog/halog usr/bin
diff -Nru haproxy-2.9.0/debian/rules haproxy-2.9.0/debian/rules
--- haproxy-2.9.0/debian/rules	2023-12-09 15:33:05.0 +0100
+++ haproxy-2.9.0/debian/rules	2023-12-10 20:15:00.0 +0100
@@ -27,6 +27,7 @@
 
 ifeq ($(DEB_HOST_ARCH_OS),linux)
 MAKEARGS+= TARGET=linux-glibc USE_SYSTEMD=1
+deb_systemdsystemunitdir=$(shell pkg-config --variable=systemdsystemunitdir systemd)
 else ifeq ($(DEB_HOST_ARCH_OS),kfreebsd)
 MAKEARGS+= TARGET=freebsd
 else
@@ -75,6 +76,9 @@
 	make $(MAKEARGS) install
 	install -m 0644 -D debian/rsyslog.conf debian/haproxy/etc/rsyslog.d/49-haproxy.conf
 	install -m 0644 -D debian/logrotate.conf debian/haproxy/etc/logrotate.d/haproxy
+ifneq ($(deb_systemdsystemunitdir),)
+	install -m 0644 -D admin/systemd/haproxy.service debian/haproxy$(deb_systemdsystemunitdir)/haproxy.service
+endif
 
 override_dh_auto_install-indep:
 

Bug#1057941: ycm-cmake-modules: FTBFS: TypeError: not all arguments converted during string formatting

[Santiago Vila]

Package: src:ycm-cmake-modules
Version: 0.13.0-3
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules binary
dh binary --without build-stamp --with linktree
   dh_update_autotools_config
   dh_autoreconf
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- \
 -DSPHINX_HTML=ON \
 -DSPHINX_MAN=ON \
 -DCMAKE_INSTALL_DOCDIR=share/doc/ycm-cmake-modules \
 -DCMAKE_INSTALL_LIBDIR=share \
 -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=OFF
cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb cmake 
-DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON 
-DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
-DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DSPHINX_HTML=ON -DSPHINX_MAN=ON 
-DCMAKE_INSTALL_DOCDIR=share/doc/ycm-cmake-modules -DCMAKE_INSTALL_LIBDIR=share 
-DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=OFF ..
-- YCM Version: 0.13.0 (0.13.0)
CMake Warning (dev) at find-modules/CMakeLists.txt:51 (message):
  A "FindGSL.cmake" module already exists in CMAKE_ROOT.  Please remove it,
  or move it to proposed.
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at find-modules/CMakeLists.txt:51 (message):
  A "FindOpenGL.cmake" module already exists in CMAKE_ROOT.  Please remove
  it, or move it to proposed.
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at deprecated/CMakeLists.txt:19 (message):
  A "FindGLUT.cmake" module already exists in CMAKE_ROOT.  Please remove it,
  or move it to proposed.
This warning is for project developers.  Use -Wno-dev to suppress it.

-- Configuring done (0.5s)
-- Generating done (0.0s)
CMake Warning:
  Manually-specified variables were not used by the project:

CMAKE_EXPORT_NO_PACKAGE_REGISTRY
CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY
CMAKE_FIND_USE_PACKAGE_REGISTRY
FETCHCONTENT_FULLY_DISCONNECTED


-- Build files have been written to: /<>/obj-x86_64-linux-gnu
make[1]: Leaving directory '/<>'
   dh_prep
   debian/rules override_dh_auto_install
make[1]: Entering directory '/<>'
dh_auto_install
cd obj-x86_64-linux-gnu && make -j2 install 
DESTDIR=/<>/debian/ycm-cmake-modules AM_UPDATE_INFO_DIR=no "INSTALL=install 
--strip-program=true"
make[2]: Entering directory '/<>/obj-x86_64-linux-gnu'
/usr/bin/cmake -S/<> -B/<>/obj-x86_64-linux-gnu 
--check-build-system CMakeFiles/Makefile.cmake 0
/usr/bin/cmake -E cmake_progress_start /<>/obj-x86_64-linux-gnu/CMakeFiles 
/<>/obj-x86_64-linux-gnu//CMakeFiles/progress.marks
make  -f CMakeFiles/Makefile2 all
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
make  -f modules/CMakeFiles/modules.dir/build.make 
modules/CMakeFiles/modules.dir/depend
make  -f find-modules/CMakeFiles/find-modules.dir/build.make 
find-modules/CMakeFiles/find-modules.dir/depend
make[4]: Entering directory '/<>/obj-x86_64-linux-gnu'
cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<> 
/<>/modules /<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu/modules 
/<>/obj-x86_64-linux-gnu/modules/CMakeFiles/modules.dir/DependInfo.cmake "--color="
make[4]: Entering directory '/<>/obj-x86_64-linux-gnu'
cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<> 
/<>/find-modules /<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu/find-modules 
/<>/obj-x86_64-linux-gnu/find-modules/CMakeFiles/find-modules.dir/DependInfo.cmake "--color="
make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make  -f find-modules/CMakeFiles/find-modules.dir/build.make 
find-modules/CMakeFiles/find-modules.dir/build
make  -f modules/CMakeFiles/modules.dir/build.make 
modules/CMakeFiles/modules.dir/build
make[4]: Entering directory '/<>/obj-x86_64-linux-gnu'
cd /<>/obj-x86_64-linux-gnu/modules && /usr/bin/cmake -E 
echo_append
make[4]: Entering directory '/<>/obj-x86_64-linux-gnu'
cd /<>/obj-x86_64-linux-gnu/find-modules && /usr/bin/cmake -E 
echo_append
cd /<>/obj-x86_64-linux-gnu/modules && /usr/bin/cmake -E touch 
/<>/obj-x86_64-linux-gnu/modules/CMakeFiles/modules.dir/ycm_download-complete
cd /<>/obj-x86_64-linux-gnu/find-modules && /usr/bin/cmake -E touch 
/<>/obj-x86_64-linux-gnu/find-modules/CMakeFiles/find-modules.dir/ycm_download-complete
cd /<>/obj-x86_64-linux-gnu/find-modules && /usr/bin/cmake -E 
echo_append
cd /<>/obj-x86_64-linux-gnu/modules && /usr/bin/cmake -E 
echo_append
cd 

Bug#1057942: ydpdict: FTBFS: invalid use of incomplete typedef ‘WINDOW’ {aka ‘struct _win_st’}

[Santiago Vila]

Package: src:ydpdict
Version: 1.0.4-1
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules build
dh build
   dh_update_autotools_config
   dh_autoreconf
find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path '*/.hg/*' -o 
-path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a  -type f -exec md5sum {} + -o 
-type l -printf "symlink  %p
" > debian/autoreconf.before
grep -q ^XDT_ configure.ac
autoreconf -f -i
Copying file ABOUT-NLS
Copying file config.rpath
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:9: installing './compile'
configure.ac:12: installing './config.guess'
configure.ac:12: installing './config.sub'
configure.ac:5: installing './install-sh'
configure.ac:5: installing './missing'
src/Makefile.am: installing './depcomp'
find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path '*/.hg/*' -o 
-path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a  -type f -exec md5sum {} + -o 
-type l -printf "symlink  %p
" > debian/autoreconf.after
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- --with-dictdir=/usr/local/share/ydpdict
./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-option-checking --disable-silent-rules 
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run 
--disable-maintainer-mode --disable-dependency-tracking 
--with-dictdir=/usr/local/share/ydpdict
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a race-free mkdir -p... /usr/bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C... yes
checking whether gcc accepts -g... yes
checking for gcc option to enable C11 features... none needed
checking whether gcc understands -c and -o together... yes
checking whether make supports the include directive... yes (GNU style)
checking dependency style of gcc... none
checking whether make sets $(MAKE)... (cached) yes
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking how to print strings... printf
checking for a sed that does not truncate output... /usr/bin/sed
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for fgrep... /usr/bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking how to convert x86_64-pc-linux-gnu file names to x86_64-pc-linux-gnu 
format... func_convert_file_noop
checking how to convert x86_64-pc-linux-gnu file names to toolchain format... 
func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for file... file
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for a working dd... /usr/bin/dd
checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1
checking for mt... no
checking if : is a manifest tool... no
checking for stdio.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for strings.h... yes
checking for sys/stat.h... yes
checking for sys/types.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC 

Bug#1057939: recommonmark: FTBFS: FAIL: test_headings (tests.test_sphinx.GenericTests.test_headings)

[Santiago Vila]

Package: src:recommonmark
Version: 0.7.1+ds-5
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules binary
dh binary --with python3 --buildsystem=pybuild
   dh_update_autotools_config -O--buildsystem=pybuild
   dh_autoreconf -O--buildsystem=pybuild
   dh_auto_configure -O--buildsystem=pybuild
I: pybuild base:310: python3.12 setup.py config
running config
I: pybuild base:310: python3.11 setup.py config
running config
   dh_auto_build -O--buildsystem=pybuild
I: pybuild base:310: /usr/bin/python3.12 setup.py build
running build
running build_py
creating /<>/.pybuild/cpython3_3.12/build/recommonmark

[... snipped ...]

/<>/.pybuild/cpython3_3.11/build/recommonmark/parser.py:75: 
UserWarning: Container node skipped: type=document
  warn("Container node skipped: type={0}".format(mdnode.t))

/<>/.pybuild/cpython3_3.11/build/tests/sphinx_generic/index.md::
 WARNING: image file not readable: image.png
looking for now-outdated files... none found
pickling environment... done
checking consistency... done
preparing documents... done
copying assets... copying static files... done
copying extra files... done
done
writing output... [100%] index

/<>/.pybuild/cpython3_3.11/build/tests/sphinx_generic/index.md:13:
 WARNING: None:any reference target not found: /example
generating indices... genindex done
writing additional pages... search done
dumping search index in English (code: en)... done
dumping object inventory... done
build succeeded, 56 warnings.

The HTML pages are in tests/sphinx_generic/_build/text.
ok
test_lists (tests.test_sphinx.GenericTests.test_lists) ... Running Sphinx 
v7.2.6
WARNING: Invalid configuration value found: 'language = None'. Update your 
configuration to a valid language code. Falling back to 'en' 
(English).
WARNING: while setting up extension sphinx.addnodes: node class 'toctree' 
is already registered, its visitors will be overridden
WARNING: while setting up extension sphinx.addnodes: node class 'desc' is 
already registered, its visitors will be overridden
WARNING: while setting up extension sphinx.addnodes: node class 
'desc_signature' is already registered, its visitors will be 
overridden
WARNING: while setting up extension sphinx.addnodes: node class 
'desc_signature_line' is already registered, its visitors will be 
overridden
WARNING: while setting up extension sphinx.addnodes: node class 
'desc_content' is already registered, its visitors will be overridden
WARNING: while setting up extension sphinx.addnodes: node class 
'desc_inline' is already registered, its visitors will be overridden
WARNING: while setting up extension sphinx.addnodes: node class 
'desc_name' is already registered, its visitors will be overridden
WARNING: while setting up extension sphinx.addnodes: node class 
'desc_addname' is already registered, its visitors will be overridden
WARNING: while setting up extension sphinx.addnodes: node class 
'desc_type' is already registered, its visitors will be overridden
WARNING: while setting up extension sphinx.addnodes: node class 
'desc_returns' is already registered, its visitors will be overridden
WARNING: while setting up extension sphinx.addnodes: node class 
'desc_parameterlist' is already registered, its visitors will be 
overridden
WARNING: while setting up extension sphinx.addnodes: node class 
'desc_type_parameter_list' is already registered, its visitors will be 
overridden
WARNING: while setting up extension sphinx.addnodes: node class 
'desc_parameter' is already registered, its visitors will be 
overridden
WARNING: while setting up extension sphinx.addnodes: node class 
'desc_type_parameter' is already registered, its visitors will be 
overridden
WARNING: while setting up extension sphinx.addnodes: node class 
'desc_optional' is already registered, its visitors will be 
overridden
WARNING: while setting up extension sphinx.addnodes: node class 
'desc_annotation' is already registered, its visitors will be 
overridden
WARNING: while setting up extension sphinx.addnodes: node class 
'desc_sig_keyword_type' is already registered, its visitors will be 
overridden
WARNING: while setting up extension sphinx.addnodes: node class 
'desc_sig_punctuation' is already registered, its visitors will be 
overridden
WARNING: 

Bug#1057940: swirc: FTBFS: invalid use of incomplete typedef ‘WINDOW’ {aka ‘struct _win_st’}

[Santiago Vila]

Package: src:swirc
Version: 3.4.6-1
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules binary
dh binary --without autoreconf
   dh_update_autotools_config
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
./configure --with-libnotify
creating temp file...ok
checking whether the etext segment is usable...yes
cleaning...
creating temp file...ok
checking for strcasestr()...yes
cleaning...
creating temp file...ok
checking whether to define 'USE_LIBNOTIFY=1'...yes
cleaning...
creating temp file...ok
checking for gnu libiconv...yes
cleaning...
creating temp file...ok
checking for gnu libidn...yes
cleaning...
creating temp file...ok
checking for 'libintl.h'...yes
cleaning...
creating temp file...ok
checking for libintl_setlocale()...no
cleaning...
make[2]: Entering directory '/<>/po'
msgfmt --output-file=de/swirc.mo de/swirc.po
msgfmt --output-file=fi/swirc.mo fi/swirc.po
msgfmt --output-file=fr/swirc.mo fr/swirc.po
msgfmt --output-file=sv/swirc.mo sv/swirc.po
make[2]: Leaving directory '/<>/po'
creating temp file...ok
checking for hunspell...yes
cleaning...
configure: options.mk successfully created!
make[1]: Leaving directory '/<>'
   dh_auto_build
make -j2
make[1]: Entering directory '/<>'
  CXX  src/commands/admin.o
  CC   src/commands/ban.o
  CXX  src/commands/cap.o
  CXX  src/commands/cleartoasts.o
  CXX  src/commands/colormap.o
  CC   src/commands/connect.o
In file included from src/commands/../terminal.h:5,
 from src/commands/connect.c:49:
src/commands/../term-unix.h: In function ‘term_set_attr’:
src/commands/../term-unix.h:38:20: error: invalid use of incomplete typedef 
‘WINDOW’ {aka ‘struct _win_st’}
   38 | win->_attrs = at;
  |^~
make[1]: *** [Makefile:17: src/commands/connect.o] Error 1
make[1]: *** Waiting for unfinished jobs
make[1]: Leaving directory '/<>'
dh_auto_build: error: make -j2 returned exit code 2
make: *** [debian/rules:18: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2


The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here:

https://people.debian.org/~sanvila/build-logs/202312/

About the archive rebuild: The build was made using virtual machines
from AWS, with enough memory, enough disk, and either one or two
CPUs, using a reduced chroot with only build-essential packages.

If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.

Thanks.

Bug#1057937: pkcs11-provider: FTBFS: failing tests

[Santiago Vila]

Package: src:pkcs11-provider
Version: 0.2+g20231107-1
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules binary
dh binary
   dh_update_autotools_config
   dh_autoreconf
aclocal: warning: couldn't open directory 'm4': No such file or directory
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:13: installing './ar-lib'
configure.ac:12: installing './compile'
configure.ac:14: installing './config.guess'
configure.ac:14: installing './config.sub'
configure.ac:8: installing './install-sh'
configure.ac:8: installing './missing'
src/Makefile.am: installing './depcomp'
parallel-tests: installing './test-driver'
   dh_auto_configure
./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-option-checking --disable-silent-rules 
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run 
--disable-maintainer-mode --disable-dependency-tracking
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a race-free mkdir -p... /usr/bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C... yes
checking whether gcc accepts -g... yes
checking for gcc option to enable C11 features... none needed
checking whether gcc understands -c and -o together... yes
checking whether make supports the include directive... yes (GNU style)
checking dependency style of gcc... none
checking for ar... ar
checking the archiver (ar) interface... ar
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking how to print strings... printf
checking for a sed that does not truncate output... /usr/bin/sed
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for fgrep... /usr/bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking how to convert x86_64-pc-linux-gnu file names to x86_64-pc-linux-gnu 
format... func_convert_file_noop
checking how to convert x86_64-pc-linux-gnu file names to toolchain format... 
func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for file... file
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for a working dd... /usr/bin/dd
checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1
checking for mt... no
checking if : is a manifest tool... no
checking for stdio.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for strings.h... yes
checking for sys/stat.h... yes
checking for sys/types.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared 
libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes

Bug#1057938: python-duniterpy: FTBFS: RuntimeError: The Poetry configuration is invalid

[Santiago Vila]

Package: src:python-duniterpy
Version: 1.1.1-2
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules build
dh build --buildsystem=pybuild --with=sphinxdoc
   dh_update_autotools_config -O--buildsystem=pybuild
   dh_autoreconf -O--buildsystem=pybuild
   dh_auto_configure -O--buildsystem=pybuild
   dh_auto_build -O--buildsystem=pybuild
I: pybuild plugin_pyproject:110: Building wheel for python3.11 with "build" 
module
I: pybuild base:310: python3.11 -m build --skip-dependency-check --no-isolation --wheel 
--outdir /<>/.pybuild/cpython3_3.11
* Building wheel...
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/pyproject_hooks/_in_process/_in_process.py", 
line 353, in 
main()
  File 
"/usr/lib/python3/dist-packages/pyproject_hooks/_in_process/_in_process.py", 
line 335, in main
json_out['return_val'] = hook(**hook_input['kwargs'])
 
  File 
"/usr/lib/python3/dist-packages/pyproject_hooks/_in_process/_in_process.py", 
line 251, in build_wheel
return _build_backend().build_wheel(wheel_directory, config_settings,
   ^^
  File "/usr/lib/python3/dist-packages/poetry/core/masonry/api.py", line 55, in 
build_wheel
poetry = Factory().create_poetry(Path(".").resolve(), with_groups=False)
 ^^^
  File "/usr/lib/python3/dist-packages/poetry/core/factory.py", line 58, in 
create_poetry
raise RuntimeError("The Poetry configuration is invalid:\n" + message)
RuntimeError: The Poetry configuration is invalid:
  - data.homepage must be uri


ERROR Backend subprocess exited when trying to invoke build_wheel
E: pybuild pybuild:395: build: plugin pyproject failed with: exit code=1: python3.11 -m 
build --skip-dependency-check --no-isolation --wheel --outdir 
/<>/.pybuild/cpython3_3.11
dh_auto_build: error: pybuild --build -i python{version} -p 3.11 returned exit 
code 13
make: *** [debian/rules:13: build] Error 25
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2


The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here:

https://people.debian.org/~sanvila/build-logs/202312/

About the archive rebuild: The build was made using virtual machines
from AWS, with enough memory, enough disk, and either one or two
CPUs, using a reduced chroot with only build-essential packages.

If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.

Thanks.

Bug#1057936: odpic: FTBFS: UndefinedError("'style' is undefined")

[Santiago Vila]

Package: src:odpic
Version: 4.6.0-1
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules binary
dh binary
   dh_update_autotools_config
   dh_autoreconf
   dh_auto_configure
   dh_auto_build
make -j2 "INSTALL=install --strip-program=true"
make[1]: Entering directory '/<>'
mkdir -p build
mkdir -p lib
cc -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Iinclude -O2 -g 
-Wall -Wextra -fPIC src/dpiConn.c -o build/dpiConn.o
cc -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Iinclude -O2 -g 
-Wall -Wextra -fPIC src/dpiContext.c -o build/dpiContext.o
cc -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Iinclude -O2 -g 
-Wall -Wextra -fPIC src/dpiData.c -o build/dpiData.o
cc -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Iinclude -O2 -g 
-Wall -Wextra -fPIC src/dpiEnv.c -o build/dpiEnv.o
cc -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Iinclude -O2 -g 
-Wall -Wextra -fPIC src/dpiError.c -o build/dpiError.o
cc -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Iinclude -O2 -g 
-Wall -Wextra -fPIC src/dpiGen.c -o build/dpiGen.o
cc -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Iinclude -O2 -g 
-Wall -Wextra -fPIC src/dpiGlobal.c -o build/dpiGlobal.o
cc -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Iinclude -O2 -g 
-Wall -Wextra -fPIC src/dpiLob.c -o build/dpiLob.o
cc -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Iinclude -O2 -g 
-Wall -Wextra -fPIC src/dpiObject.c -o build/dpiObject.o
cc -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Iinclude -O2 -g 
-Wall -Wextra -fPIC src/dpiObjectAttr.c -o build/dpiObjectAttr.o
cc -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Iinclude -O2 -g 
-Wall -Wextra -fPIC src/dpiObjectType.c -o build/dpiObjectType.o
cc -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Iinclude -O2 -g 
-Wall -Wextra -fPIC src/dpiPool.c -o build/dpiPool.o
cc -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Iinclude -O2 -g 
-Wall -Wextra -fPIC src/dpiStmt.c -o build/dpiStmt.o
cc -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Iinclude -O2 -g 
-Wall -Wextra -fPIC src/dpiUtils.c -o build/dpiUtils.o
cc -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Iinclude -O2 -g 
-Wall -Wextra -fPIC src/dpiVar.c -o build/dpiVar.o
cc -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Iinclude -O2 -g 
-Wall -Wextra -fPIC src/dpiOracleType.c -o build/dpiOracleType.o
cc -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Iinclude -O2 -g 
-Wall -Wextra -fPIC src/dpiSubscr.c -o build/dpiSubscr.o
cc -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Iinclude -O2 -g 
-Wall -Wextra -fPIC src/dpiDeqOptions.c -o build/dpiDeqOptions.o
cc -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 

Bug#1057933: libjose4j-java: FTBFS: IOException: Only named ECParameters supported

[Santiago Vila]

Package: src:libjose4j-java
Version: 0.7.12-2
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules binary
dh binary
   dh_update_autotools_config
   dh_autoreconf
   dh_auto_configure
mh_patchpoms -plibjose4j-java --debian-build --keep-pom-version 
--maven-repo=/<>/debian/maven-repo
   dh_auto_build
/usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar 
-Dmaven.home=/usr/share/maven -Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf -Dproperties.file.manual=/<>/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher -s/etc/maven/settings-debian.xml 
-Ddebian.dir=/<>/debian -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode 
package -DskipTests -Dnotimestamp=true -Dlocale=en_US
OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were 
deprecated in JDK 13 and will likely be removed in a future release.
[INFO] Scanning for projects...
[INFO]
[INFO] --< org.bitbucket.b_c:jose4j >--
[INFO] Building jose4j 0.7.12
[INFO] [ jar ]-

[... snipped ...]

at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:568)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:61)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
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.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)
at 
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384)
at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345)
at 
org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126)
at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418)
14:19:37.806 DEBUG org.jose4j.jwk.JsonWebKeySet - Ignoring an individual JWK in a JWKS due to a problem processing it. JWK params: {kty=null, x=riwTtQeRjmlDsR4PUQELhejpPkZkQstb0_Lf08qeBzM, y=izN8y6z-8j8bB_Lj10gX9mnaE_E0ZK5fl0hJVyLWMKA, crv=P-256} and the full JWKS content: 

Bug#1057935: ncurses-hexedit: FTBFS: invalid use of incomplete typedef ‘WINDOW’ {aka ‘struct _win_st’}

[Santiago Vila]

Package: src:ncurses-hexedit
Version: 0.9.7+orig-7.2
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules binary
dh binary
   debian/rules override_dh_update_autotools_config
make[1]: Entering directory '/<>'
dh_update_autotools_config
test -f debian/backup.tar || \
tar cpf debian/backup.tar -T debian/mutable
make[1]: Leaving directory '/<>'
   dh_autoreconf
find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path '*/.hg/*' -o 
-path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a  -type f -exec md5sum {} + -o 
-type l -printf "symlink  %p
" > debian/autoreconf.before
grep -q ^XDT_ configure.ac
autoreconf -f -i
configure.ac:11: warning: 'AM_CONFIG_HEADER': this macro is obsolete.
configure.ac:11: You should use the 'AC_CONFIG_HEADERS' macro instead.
./lib/autoconf/general.m4:2434: AC_DIAGNOSE is expanded from...
aclocal.m4:745: AM_CONFIG_HEADER is expanded from...
configure.ac:11: the top level
configure.ac:22: warning: The macro `AC_HEADER_STDC' is obsolete.
configure.ac:22: You should run autoupdate.
./lib/autoconf/headers.m4:704: AC_HEADER_STDC is expanded from...
configure.ac:22: the top level
configure.ac:109: warning: AC_OUTPUT should be used without arguments.
configure.ac:109: You should run autoupdate.
configure.ac:13: installing './compile'
src/Makefile.am: installing './depcomp'
find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path '*/.hg/*' -o 
-path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a  -type f -exec md5sum {} + -o 
-type l -printf "symlink  %p
" > debian/autoreconf.after
   dh_auto_configure
./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-option-checking --disable-silent-rules 
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run 
--disable-maintainer-mode --disable-dependency-tracking
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a race-free mkdir -p... /usr/bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C... yes
checking whether gcc accepts -g... yes
checking for gcc option to enable C11 features... none needed
checking whether gcc understands -c and -o together... yes
checking whether make supports the include directive... yes (GNU style)
checking dependency style of gcc... none
checking for stdio.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for strings.h... yes
checking for sys/stat.h... yes
checking for sys/types.h... yes
checking for unistd.h... yes
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking how to run the C preprocessor... gcc -E
checking whether gcc needs -traditional... no
checking for ncurses.h... yes
checking for fcntl.h... yes
checking for getopt.h... yes
checking for limits.h... yes
checking for sys/ioctl.h... yes
checking for unistd.h... (cached) yes
checking for dirent.h that defines DIR... yes
checking for library containing opendir... none required
checking for an ANSI C-conforming const... yes
checking whether struct tm is in sys/time.h or time.h... time.h
checking for snprintf... yes
checking for isprint... yes
checking for getopt_long... yes
checking for TIOCGWINSZ... yes, found in termio.h
checking for newwin in -lncurses... yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating docs/Makefile
config.status: creating gnu/Makefile
config.status: creating src/Makefile
config.status: creating config.h
config.status: executing depfiles commands
rm -f debian/ncurses-hexedit.debhelper.log
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build -- \

make -j2
make[2]: Entering directory '/<>'
make  all-recursive
make[3]: Entering directory '/<>'
Making all in docs
make[4]: Entering directory '/<>/docs'
restore=: && backupdir=".am$$" && \
am__cwd=`pwd` && CDPATH="${ZSH_VERSION+.}:" && cd . && \
rm -rf $backupdir && mkdir $backupdir && \
if (/bin/bash '/<>/missing' makeinfo --version) >/dev/null 2>&1; 
then \
  for f in hexeditor.info hexeditor.info-[0-9] 

Bug#1057932: kgb-bot: FTBFS: Failed test 'Changes contains all valid release dates'

[Santiago Vila]

Package: src:kgb-bot
Version: 1.59-1
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules binary
dh binary
   dh_update_autotools_config
   dh_autoreconf
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
[ "1.59" = "1.59" ] \
|| ( echo "Package version (1.59) doesn't match module version (1.59)"; 
exit 1 )
dh_auto_configure
/usr/bin/perl Build.PL --installdirs vendor --config "optimize=-g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2" --config "ld=x86_64-linux-gnu-gcc -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -Wl,-z,relro"
Checking prerequisites...
  test_requires:
!  Test::Perl::Critic is not installed

ERRORS/WARNINGS FOUND IN PREREQUISITES.  You may wish to install the versions
of the modules indicated above before proceeding with this installation

Run 'Build installdeps' to install missing prerequisites.

Created MYMETA.yml and MYMETA.json
Creating new 'Build' script for 'App-KGB' version '1.59'
make[1]: Leaving directory '/<>'
   dh_auto_build
/usr/bin/perl Build
Building App-KGB
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
LANG=bg_BG.utf8 LC_ALL=bg_BG.utf8 dh_auto_test
/usr/bin/perl Build test --verbose 1
t/00-compile.t 
ok 1 - blib/lib/App/KGB.pm compiles
ok 2 - blib/lib/App/KGB/API.pm compiles
ok 3 - blib/lib/App/KGB/Change.pm compiles
ok 4 - blib/lib/App/KGB/Client.pm compiles
ok 5 - blib/lib/App/KGB/Client/Fake.pm compiles
ok 6 - blib/lib/App/KGB/Client/Git.pm compiles
ok 7 - blib/lib/App/KGB/Client/RelayMsg.pm compiles
ok 8 - blib/lib/App/KGB/Client/ServerRef.pm compiles
ok 9 - blib/lib/App/KGB/Client/Subversion.pm compiles
ok 10 - blib/lib/App/KGB/Commit.pm compiles
ok 11 - blib/lib/App/KGB/Commit/Tag.pm compiles
ok 12 - blib/lib/App/KGB/Painter.pm compiles
ok 13 - blib/lib/JSON/RPC/Client/Any.pm compiles
ok 14 - blib/lib/WWW/Shorten/Debli.pm compiles
1..14
ok
t/00-compile_scripts.t 
1..2
ok 1 - blib/script/kgb-ci-report compiles
ok 2 - blib/script/kgb-client compiles
ok
t/00-compile_shell_scripts.t ..
ok 1
1..1
ok
t/30-bot-changes.t 
ok 1
ok 2
ok 3
1..3
ok
# trying port 5392
# port 5392 is available
# test bot listening on 127.0.0.1:5392, pid: 629908  at t/TestBot.pm line 133.
# Test bot started on 127.0.0.1:5392
# $>=924 $<=924 $ENV{USER}=buildd getpwuid($>)=buildd
# stopping test bot, pid 629908
# Removing directory /<>/t/bot
t/50-client.t .
Checked out revision 0.
A file
Adding file
Transmitting file data .done
Committing transaction...
Committed revision 1.
Sendingfile
Transmitting file data .done
Committing transaction...
Committed revision 2.
D file
A file
Replacing  file
Transmitting file data .done
Committing transaction...
Committed revision 3.
ok 1 - Test repository prepared
ok 2 - An object of class 'App::KGB::Client::Subversion' isa 
'App::KGB::Client::Subversion'
ok 3
ok 4
ok 5
ok 6
ok 7
ok 8
ok 9
ok 10
ok 11
ok 12
ok 13
ok 14
ok 15
ok 16
ok 17
ok 18
ok 19
ok 20
ok 21
ok 22
ok 23
ok 24 # skip UTF-8 locale needed for the test with UTF-8 commit message
ok 25 # skip UTF-8 locale needed for the test with UTF-8 commit message
ok 26 # skip UTF-8 locale needed for the test with UTF-8 commit message
ok 27 # skip UTF-8 locale needed for the test with UTF-8 commit message
ok 28 # skip UTF-8 locale needed for the test with UTF-8 commit message
ok 29 # skip UTF-8 locale needed for the test with UTF-8 commit message
ok 30 # skip UTF-8 locale needed for the test with UTF-8 commit message
ok 31
1..31
ok
t/51-client_branch_module.t ...
ok 1 - An object of class 'App::KGB::Client::Subversion' isa 
'App::KGB::Client::Subversion'
ok 2 - branch detection in [module and branch] (/kgb/trunk/some/file) =~ 
(^/([^/]+)/([^/]+)/)
ok 3 - module detection in [module and branch] (/kgb/trunk/some/file) =~ 
(^/([^/]+)/([^/]+)/)
ok 4 - file list for [module and branch]
ok 5 - branch detection in [branch and module] (/trunk/kgb/some/file) =~ 
(^/([^/]+)/([^/]+)/)
ok 6 - module detection in [branch and module] (/trunk/kgb/some/file) =~ 
(^/([^/]+)/([^/]+)/)
ok 7 - file list for [branch and module]
ok 8 - branch detection in [branch only] (/trunk/some/file) =~ (^/([^/]+)/())
ok 9 - module detection in [branch only] (/trunk/some/file) =~ (^/([^/]+)/())
ok 10 - file list for [branch only]
ok 11 - branch detection in [module only] (/website/some/file) =~ 
(^/(website)/())
ok 12 - module detection in [module only] (/website/some/file) =~ 
(^/(website)/())
ok 13 - file list for [module only]
ok 14 - branch detection in [real example] 

Bug#1057934: libjs-jquery-jstree: FTBFS: dh_debputy: error: debputy internal-command dh-integration-generate-debs -p libjs-jquery-jstree .. returned exit code 1

[Santiago Vila]

Package: src:libjs-jquery-jstree
Version: 3.3.16+dfsg1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules binary
dh binary
   dh_update_autotools_config
   dh_autoreconf
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
cp debian/build.js build.js
nodejs /usr/share/nodejs/requirejs/r.js -o build.js

Tracing dependencies for: jstree

/<>/dist/jstree.js

/<>/src/jstree.js
/<>/src/jstree.changed.js
/<>/src/jstree.checkbox.js
/<>/src/jstree.conditionalselect.js
/<>/src/jstree.contextmenu.js
/<>/src/jstree.dnd.js
/<>/src/jstree.massload.js
/<>/src/jstree.search.js
/<>/src/jstree.sort.js
/<>/src/jstree.state.js
/<>/src/jstree.types.js
/<>/src/jstree.unique.js
/<>/src/jstree.wholerow.js
/<>/src/vakata-jstree.js

sed -i -e 's/{{VERSION}}/3.3.16+dfsg1/' dist/jstree.js
Checking syntax of dist/jstree.js ...
uglifyjs dist/jstree.js --output dist/jstree.min.js --compress
dh_auto_build
make[1]: Leaving directory '/<>'
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
nodejs --check dist/jstree.js
nodejs --check dist/jstree.min.js
make[1]: Leaving directory '/<>'
   create-stamp debian/debhelper-build-stamp
   dh_prep
   dh_auto_install --destdir=debian/libjs-jquery-jstree/
   dh_debputy
Internal error in debputy
  - 8<  BEGIN STACK TRACE  8< -
Traceback (most recent call last):
  File "/usr/share/dh-debputy/debputy/commands/debputy_cmd.py", line 2082, in 
main
command.handler(cmd_context)
  File "/usr/share/dh-debputy/debputy/commands/debputy_cmd.py", line 1133, in 
_dh_integration_generate_debs
intermediate_manifest = manifest.finalize_data_tar_contents(

  File "/usr/share/dh-debputy/debputy/highlevel_manifest.py", line 1177, in 
finalize_data_tar_contents
intermediate_manifest = list(
^
  File "/usr/share/dh-debputy/debputy/highlevel_manifest.py", line 180, in 
_generate_intermediate_manifest
tar_member = _path_to_tar_member(path, clamp_mtime_to)
 ^
  File "/usr/share/dh-debputy/debputy/highlevel_manifest.py", line 159, in 
_path_to_tar_member
return TarMember.from_file(
   
  File "/usr/share/dh-debputy/debputy/intermediate_manifest.py", line 147, in 
from_file
"debputy/scratch_dir/" in fs_path
AssertionError: README.md should not have been stealable
  - 8<  END STACK TRACE  8< -
Please file a bug against debputy with the full output.
README.md should not have been stealable
dh_debputy: error: debputy internal-command dh-integration-generate-debs -p 
libjs-jquery-jstree .. returned exit code 1
make: *** [debian/rules:34: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2


The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here:

https://people.debian.org/~sanvila/build-logs/202312/

About the archive rebuild: The build was made using virtual machines
from AWS, with enough memory, enough disk, and either one or two
CPUs, using a reduced chroot with only build-essential packages.

If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.

Thanks.

Bug#1057931: greetd: FTBFS: failed to select a version for the requirement `rpassword = "^6.0"`

[Santiago Vila]

Package: src:greetd
Version: 0.9.0-5
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules binary
dh binary --buildsystem=cargo
   dh_update_autotools_config -O--buildsystem=cargo
   dh_autoreconf -O--buildsystem=cargo
   debian/rules execute_before_dh_auto_configure
make[1]: Entering directory '/<>'
printf '{"package":"%s","files":{}}\n' $(sha256sum Cargo.toml | grep -Po '^\S+') 
> debian/cargo-checksum.json;
make[1]: Leaving directory '/<>'
   dh_auto_configure -O--buildsystem=cargo
debian cargo wrapper: options, profiles, parallel, lto: ['parallel=2'] [] 
['-j2'] 0
debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu, 
x86_64-linux-gnu
debian cargo wrapper: linking /usr/share/cargo/registry/* into 
/<>/debian/cargo_registry/
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
# actually does the build
DEB_BUILD_OPTIONS= dh_auto_test -- --release
debian cargo wrapper: options, profiles, parallel, lto: [] [] [] 0
debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu, 
x86_64-linux-gnu
debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1', 
'/usr/bin/cargo', '-Zavoid-dev-deps', 'build', '--verbose', '--verbose', 
'--target', 'x86_64-unknown-linux-gnu', '--release'],) {}
error: failed to select a version for the requirement `rpassword = "^6.0"`
candidate versions found which didn't match: 7.2.0
location searched: directory source `/<>/debian/cargo_registry` 
(which is replacing registry `crates-io`)
required by package `agreety v0.9.0 (/<>/agreety)`
perhaps a crate was updated and forgotten to be re-vendored?
dh_auto_test: error: /usr/share/cargo/bin/cargo build --release returned exit 
code 101
make[1]: *** [debian/rules:19: override_dh_auto_build] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:8: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2


The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here:

https://people.debian.org/~sanvila/build-logs/202312/

About the archive rebuild: The build was made using virtual machines
from AWS, with enough memory, enough disk, and either one or two
CPUs, using a reduced chroot with only build-essential packages.

If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.

Thanks.

Bug#1057929: buildbot: FTBFS: locale.Error: unsupported locale setting

[Santiago Vila]

Package: src:buildbot
Version: 3.9.2-2
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules binary
dh binary --with python3,bash-completion,sphinxdoc
   dh_update_autotools_config
   dh_autoreconf
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure --buildsystem=pybuild --sourcedirectory=master \
--package=buildbot
pybuild --configure -i python{version} -p 3.11 --dir master
I: pybuild base:310: python3.11 setup.py config
/<>/master/setup.py:27: DeprecationWarning: pkg_resources is 
deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html
  import pkg_resources
/usr/lib/python3/dist-packages/setuptools/dist.py:508: InformationOnly: 
Normalizing '3.9.2-2' to '3.9.2.post2'
  self.metadata.version = self._normalize_version(
running config
dh_auto_configure --buildsystem=pybuild --sourcedirectory=worker \
--package=buildbot-worker
pybuild --configure -i python{version} -p 3.11 --dir worker
I: pybuild base:310: python3.11 setup.py config
/usr/lib/python3/dist-packages/setuptools/dist.py:508: InformationOnly: 
Normalizing '3.9.2-2' to '3.9.2.post2'
  self.metadata.version = self._normalize_version(
running config
make[1]: Leaving directory '/<>'
rm -f debian/buildbot-worker.debhelper.log debian/buildbot.debhelper.log
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build --buildsystem=pybuild --sourcedirectory=master \
--package=buildbot
pybuild --build -i python{version} -p 3.11 --dir master
I: pybuild base:310: /usr/bin/python3 setup.py build
/<>/master/setup.py:27: DeprecationWarning: pkg_resources is 
deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html
  import pkg_resources
/usr/lib/python3/dist-packages/setuptools/dist.py:508: InformationOnly: 
Normalizing '3.9.2-2' to '3.9.2.post2'
  self.metadata.version = self._normalize_version(
running build
running build_py
creating /<>/.pybuild/cpython3_3.11/build/buildbot
copying buildbot/__init__.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot
copying buildbot/pbutil.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot
copying buildbot/asyncio.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot
copying buildbot/scheduler.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot
copying buildbot/warnings.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot
copying buildbot/errors.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot
copying buildbot/buildbot_net_usage_data.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot
copying buildbot/locks.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot
copying buildbot/revlinks.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot
copying buildbot/buildrequest.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot
copying buildbot/manhole.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot
copying buildbot/interfaces.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot
copying buildbot/master.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot
creating /<>/.pybuild/cpython3_3.11/build/buildbot/configurators
copying buildbot/configurators/__init__.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot/configurators
copying buildbot/configurators/janitor.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot/configurators
creating /<>/.pybuild/cpython3_3.11/build/buildbot/worker
copying buildbot/worker/local.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot/worker
copying buildbot/worker/__init__.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot/worker
copying buildbot/worker/docker.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot/worker
copying buildbot/worker/latent.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot/worker
copying buildbot/worker/marathon.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot/worker
copying buildbot/worker/kubernetes.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot/worker
copying buildbot/worker/base.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot/worker
copying buildbot/worker/openstack.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot/worker
copying buildbot/worker/libvirt.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot/worker
copying buildbot/worker/ec2.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot/worker
copying buildbot/worker/manager.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot/worker
copying buildbot/worker/upcloud.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot/worker
creating /<>/.pybuild/cpython3_3.11/build/buildbot/worker/protocols
copying buildbot/worker/protocols/__init__.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot/worker/protocols
copying buildbot/worker/protocols/msgpack.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot/worker/protocols
copying buildbot/worker/protocols/null.py -> 
/<>/.pybuild/cpython3_3.11/build/buildbot/worker/protocols
copying 

Bug#1057930: cunit: FTBFS: invalid use of incomplete typedef ‘WINDOW’ {aka ‘struct _win_st’}

[Santiago Vila]

Package: src:cunit
Version: 2.1-3-dfsg-2.6
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules binary
dh binary --with autoreconf
dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
   dh_update_autotools_config
cp -an --reflink=auto config.guess 
debian/.debhelper/bucket/files/1d9048b0ac9d4d1dfce7aa4e3a0b59ccfd32db2f7693814aa6f4c778560f5669.tmp
mv 
debian/.debhelper/bucket/files/1d9048b0ac9d4d1dfce7aa4e3a0b59ccfd32db2f7693814aa6f4c778560f5669.tmp
 
debian/.debhelper/bucket/files/1d9048b0ac9d4d1dfce7aa4e3a0b59ccfd32db2f7693814aa6f4c778560f5669
cp -f /usr/share/misc/config.guess ./config.guess
cp -an --reflink=auto config.sub 
debian/.debhelper/bucket/files/4add30a10b137a5a4667e12868fb4783e385dbf865cfb7017b205321bd1a2f39.tmp
mv 
debian/.debhelper/bucket/files/4add30a10b137a5a4667e12868fb4783e385dbf865cfb7017b205321bd1a2f39.tmp
 
debian/.debhelper/bucket/files/4add30a10b137a5a4667e12868fb4783e385dbf865cfb7017b205321bd1a2f39
cp -f /usr/share/misc/config.sub ./config.sub
   dh_autoreconf
find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path '*/.hg/*' -o 
-path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a  -type f -exec md5sum {} + -o 
-type l -printf "symlink  %p
" > debian/autoreconf.before
grep -q ^XDT_ configure.in

[... snipped ...]

  |   
  ||
  |size_t {aka long unsigned int}
Console.c:504:29: warning: field width specifier ‘*’ expects argument of type 
‘int’, but argument 5 has type ‘size_t’ {aka ‘long unsigned int’} [-Wformat=]
  504 |   fprintf(stdout, "\n%*s  %-*s%*s%*s%*s%*s\n",
  |   ~~^~
  | |
  | int
  505 |   width[0], _("#"),
  506 |   width[1], _("Suite Name"),
  |   
  ||
  |size_t {aka long unsigned int}
Console.c:504:32: warning: field width specifier ‘*’ expects argument of type 
‘int’, but argument 7 has type ‘size_t’ {aka ‘long unsigned int’} [-Wformat=]
  504 |   fprintf(stdout, "\n%*s  %-*s%*s%*s%*s%*s\n",
  |   ~^~
  ||
  |int
..
  507 |   width[2], _("Init?"),
  |   
  ||
  |size_t {aka long unsigned int}
Console.c:504:35: warning: field width specifier ‘*’ expects argument of type 
‘int’, but argument 9 has type ‘size_t’ {aka ‘long unsigned int’} [-Wformat=]
  504 |   fprintf(stdout, "\n%*s  %-*s%*s%*s%*s%*s\n",
  |  ~^~
  |   |
  |   int
..
  508 |   width[3], _("Cleanup?"),
  |   
  ||
  |size_t {aka long unsigned int}
Console.c:504:38: warning: field width specifier ‘*’ expects argument of type 
‘int’, but argument 11 has type ‘size_t’ {aka ‘long unsigned int’} [-Wformat=]
  504 |   fprintf(stdout, "\n%*s  %-*s%*s%*s%*s%*s\n",
  | ~^~
  |  |
  |  int
..
  509 |   width[4], _("#Tests"),
  |   
  ||
  |size_t {aka long unsigned int}
Console.c:504:41: warning: field width specifier ‘*’ expects argument of type 
‘int’, but argument 13 has type ‘size_t’ {aka ‘long unsigned int’} [-Wformat=]
  504 |   fprintf(stdout, "\n%*s  %-*s%*s%*s%*s%*s\n",
  |~^~
  | |
  | int
..
  510 |   width[5], _("Active?"));
  |   
  ||
  |size_t {aka long unsigned int}
Console.c:514:25: warning: field width specifier ‘*’ expects argument of type 
‘int’, but argument 3 has type ‘size_t’ {aka ‘long unsigned int’} [-Wformat=]
  514 | fprintf(stdout, "\n%*d. %-*.*s%*s%*s%*u%*s",
  |~^~
  | |
  | int
  515 | width[0], i,
  | 
  |  |
  |  size_t {aka long unsigned int}
Console.c:514:31: warning: field width specifier ‘*’ expects argument of type 
‘int’, but argument 5 has type ‘size_t’ {aka ‘long unsigned int’} [-Wformat=]
 

Bug#1057928: boinctui: FTBFS: invalid use of incomplete type ‘ITEM’ {aka ‘struct tagITEM’}

[Santiago Vila]

Package: src:boinctui
Version: 2.7.0-1
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules binary
dh binary
   dh_update_autotools_config
   dh_autoreconf
find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path '*/.hg/*' -o 
-path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a  -type f -exec md5sum {} + -o 
-type l -printf "symlink  %p
" > debian/autoreconf.before
grep -q ^XDT_ configure.in
autoreconf -f -i
autoreconf: warning: autoconf input should be named 'configure.ac', not 
'configure.in'
aclocal: warning: autoconf input should be named 'configure.ac', not 
'configure.in'
find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path '*/.hg/*' -o 
-path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a  -type f -exec md5sum {} + -o 
-type l -printf "symlink  %p
" > debian/autoreconf.after
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
autoconf
dh_auto_configure
./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-option-checking --disable-silent-rules 
--libdir=\${prefix}/lib/x86_64-linux-gnu 
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run 
--disable-maintainer-mode --disable-dependency-tracking
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C... yes
checking whether gcc accepts -g... yes
checking for gcc option to enable C11 features... none needed
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... no
checking for g++... g++
checking whether the compiler supports GNU C++... yes
checking whether g++ accepts -g... yes
checking for g++ option to enable C++11 features... none needed
checking for main in -lncursesw... yes
checking for main in -lformw... yes
checking for main in -lpanelw... yes
checking for main in -lmenuw... yes
checking for main in -lexpat... yes
checking for main in -lpthread... yes
checking for MD5_Init in -lgnutls-openssl ... yes
checking for stdio.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for strings.h... yes
checking for sys/stat.h... yes
checking for sys/types.h... yes
checking for unistd.h... yes
checking for pthread.h... yes
checking for string.h... (cached) yes
checking for stdlib.h... (cached) yes
checking for stdio.h... (cached) yes
checking for sys/stat.h... (cached) yes
checking for unistd.h... (cached) yes
checking for stdarg.h... yes
checking for sys/ioctl.h... yes
checking for arpa/inet.h... yes
checking for locale.h... yes
checking for malloc.h... yes
checking for sys/socket.h... yes
checking for netdb.h... yes
checking for signal.h... yes
checking for ctype.h... yes
checking for algorithm... yes
checking for string... yes
checking for list... yes
checking for vector... yes
checking for queue... yes
checking for stack... yes
checking for sstream... yes
checking for expat.h... yes
checking for gnutls/openssl.h... yes
checking for ncursesw/curses.h... yes
checking for ncursesw/form.h... yes
checking for ncursesw/panel.h... yes
checking for ncursesw/menu.h... yes
checking for _Bool... yes
checking for stdbool.h that conforms to C99... yes
checking for size_t... yes
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking whether lstat correctly handles trailing slash... yes
checking for GNU libc compatible malloc... yes
checking for GNU libc compatible realloc... yes
checking for mblen... yes
checking for memset... yes
checking for setlocale... yes
checking for socket... yes
checking for strdup... yes
checking for strstr... yes
configure: creating ./config.status
config.status: creating Makefile
make[1]: Leaving directory '/<>'
   dh_auto_build
make -j2
make[1]: Entering directory '/<>'
create .obj
 
g++ -c -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -DENABLEMOUSE -DVERSION=2.7.0 -DPACKAGE_NAME=\"boinctui\" -DPACKAGE_TARNAME=\"boinctui\" -DPACKAGE_VERSION=\"VERSION\" -DPACKAGE_STRING=\"boinctui\ VERSION\" -DPACKAGE_BUGREPORT=\"BUG-REPORT-ADDRESS\" -DPACKAGE_URL=\"\" -DHAVE_LIBNCURSESW=1 -DHAVE_LIBFORMW=1 -DHAVE_LIBPANELW=1 -DHAVE_LIBMENUW=1 -DHAVE_LIBEXPAT=1 -DHAVE_LIBPTHREAD=1 -DHAVE_LIBGNUTLS_OPENSSL_=1 -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 

Bug#1057927: dracut: use systemd.pc to place systemd system units

[Chris Hofstaedtler]

Source: dracut
Version: 1.4.3-2
Severity: normal
Tags: patch
User: helm...@debian.org
Usertags: dep17m2

Dear Maintainer,

your package installs systemd system units, currently into /lib.
These files need to be moved to /usr/lib as part of Debian's usr-merge
effort [1].

Attached you will find a patch to delegate the exact placement of
these files to systemd.pc (using pkg-config). This immediately works
in unstable, placing the files into /usr/lib.
It also works for backports to older releases, where it will continue
install into /lib.
Salsa merge request: https://salsa.debian.org/debian/dracut/-/merge_requests/32

The patch inside the debdiff is probably suitable for upstream, if
you want to forward it.

If during the trixie cycle your package will undergo structural
changes or any other file moves, please see the wiki and upload
to experimental first when these changes are done.

Later during the trixie cycle I expect this bug class to raise in
priority.

Thank you for considering,
Chris

[1] https://wiki.debian.org/UsrMerge


PS: it appears the git repository on salsa.d.o is missing a push
to the upstream branch and a few upstream/... tags.

>From 736b5c3cf3b768bb0f4b6cfbec2a9cd3b7e2a044 Mon Sep 17 00:00:00 2001
From: Chris Hofstaedtler 
Date: Sun, 10 Dec 2023 20:08:09 +0100
Subject: [PATCH] Set --systemdsystemunitdir from pkg-config

---
 debian/control | 2 +-
 debian/dracut-core.install | 1 -
 debian/rules   | 8 +++-
 3 files changed, 8 insertions(+), 3 deletions(-)

diff --git a/debian/control b/debian/control
index 5d34b9f4..53e270e3 100644
--- a/debian/control
+++ b/debian/control
@@ -2,7 +2,7 @@ Source: dracut
 Section: utils
 Priority: optional
 Maintainer: Thomas Lange 
-Build-Depends: debhelper-compat (= 12), debhelper, asciidoc-base, xsltproc, docbook-xsl, docbook-xml, quilt, libkmod-dev, pkg-config
+Build-Depends: debhelper-compat (= 12), debhelper, asciidoc-base, xsltproc, docbook-xsl, docbook-xml, quilt, libkmod-dev, pkg-config, systemd-dev
 Standards-Version: 4.6.2
 Vcs-Browser: https://salsa.debian.org/debian/dracut
 Vcs-Git: https://salsa.debian.org/debian/dracut.git
diff --git a/debian/dracut-core.install b/debian/dracut-core.install
index aa675bf3..cbb526a5 100644
--- a/debian/dracut-core.install
+++ b/debian/dracut-core.install
@@ -9,7 +9,6 @@ usr/lib/dracut/dracut-install
 usr/lib/dracut/dracut-util
 usr/lib/dracut/skipcpio
 usr/lib/dracut/dracut-logger.sh
-lib/systemd/system
 usr/share/bash-completion/completions
 usr/share/pkgconfig/dracut.pc
 usr/lib/dracut/dracut-version.sh
diff --git a/debian/rules b/debian/rules
index bce1c66c..b6f1f770 100755
--- a/debian/rules
+++ b/debian/rules
@@ -9,11 +9,13 @@ DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH)
 export DRACUT_MAIN_VERSION=$(DEB_VERSION_UPSTREAM_REVISION)
 export DRACUT_FULL_VERSION=$(DEB_VERSION)
 
+deb_systemdsystemunitdir = $(shell pkg-config --variable=systemdsystemunitdir systemd | sed s,^/,,)
+
 %:
 	dh $@
 
 override_dh_auto_configure:
-	dh_auto_configure -- --systemdsystemunitdir=/lib/systemd/system --libdir=/usr/lib
+	dh_auto_configure -- --systemdsystemunitdir=/$(deb_systemdsystemunitdir) --libdir=/usr/lib
 	$(SHELL) debian/fix-revdate
 	mv dracut-version.sh dracut-version.sh.orig
 	echo '#!/bin/sh' > dracut-version.sh
@@ -40,6 +42,10 @@ endif
 
 override_dh_auto_test:
 
+override_dh_install:
+	dh_install
+	dh_install -pdracut-core $(deb_systemdsystemunitdir)
+
 override_dh_clean:
 	if test -e dracut-version.sh.orig ; then \
 	   mv -f dracut-version.sh.orig dracut-version.sh ;\
-- 
2.39.2

Bug#1057926: 403 Access Denied on some packages on official Debian repo

[Juan J. Fernandez]

Package: linux-image-6.1.0-14-rt-amd64
Version: 6.1.64-1

When I run apt upgrade command it shows Error 403 Access Denied
Here is a transcript:

E: Failed to fetch 
http://ftp.debian.org/debian/pool/main/l/linux-signed-amd64/linux-image-6.1.0-14-rt-amd64_6.1.64-1_amd64.deb
  403  Access denied - broken package [IP: 151.101.126.132 80]

I suggest that the file permissions be corrected

I am using Debian GNU/Linux 12 Bookworm, kernel 6.5.11-7-pve


Thanks for fix it,
Cheers
JJ

E: Failed to fetch 
https://deb.debian.org/debian/pool/main/l/linux-signed-amd64/linux-image-6.1.0-14-cloud-amd64_6.1.64-1_amd64.deb
  403  Access denied - broken package [IP: 151.101.54.132 443]

E: Failed to fetch 
https://deb.debian.org/debian/pool/main/l/linux-signed-amd64/linux-image-cloud-amd64_6.1.64-1_amd64.deb
  403  Access denied - broken package [IP: 151.101.54.132 443]

E: Failed to fetch 
http://ftp.debian.org/debian/pool/main/l/linux-signed-amd64/linux-image-6.1.0-14-rt-amd64_6.1.64-1_amd64.deb
  403  Access denied - broken package [IP: 151.101.126.132 80]

E: Failed to fetch 
http://ftp.debian.org/debian/pool/main/l/linux-signed-amd64/linux-image-rt-amd64_6.1.64-1_amd64.deb
  403  Access denied - broken package [IP: 151.101.126.132 80]

Sent from Mail for Windows

Bug#1057849: [Pkg-roundcube-maintainers] Bug#1057849: roundcube-core: Can't open file /etc/roundcube/plugins/jqueryui/config.inc.php.dpkg-new

[Guilhem Moulin]

On Sun, 10 Dec 2023 at 19:05:05 +0100, Daniel Huhardeaux via 
Pkg-roundcube-maintainers wrote:
> root@wwwmail11:/etc/roundcube# ls -l /etc/roundcube/plugins/jqueryui/
> total 20
> -rw-r--r-- 1 root root 1030 14 oct.  18:34 composer.json
> -rw-r--r-- 1 root root  307 14 oct.  18:34 config.inc.php.dist
> -rw-r--r-- 1 root root 5256 18 oct.  23:40 jqueryui.php
> drwxr-xr-x 2 root root 4096 10 déc.  18:46 js
> drwxr-xr-x 5 root root   46  6 nov.   2021 themes

It looks like you tried to manually install the plugin from composer.
1.4.15+dfsg.1-1~deb11u2, and AFAIK all versions since at least 1.1, ship
only

/etc/roundcube/plugins/jqueryui/config.inc.php

Please try to move the content of /etc/roundcube/plugins/jqueryui/ to a
seperate location and try again.  You might also want to recreate
/etc/roundcube/plugins/jqueryui/config.inc.php:



signature.asc
Description: PGP signature

Bug#1057925: cubemap: use systemd.pc to place systemd system units

[Chris Hofstaedtler]

Source: cubemap
Version: 1.4.3-2
Severity: normal
Tags: patch
User: helm...@debian.org
Usertags: dep17m2

Dear Maintainer,

your package installs systemd system units, currently into /lib.
These files need to be moved to /usr/lib as part of Debian's usr-merge
effort [1].

Attached you will find a patch to delegate the exact placement of
these files to systemd.pc (using pkg-config). This immediately works
in unstable, placing the files into /usr/lib.
It also works for backports to older releases, where it will continue
install into /lib.

The patch inside the debdiff is probably suitable for upstream, if
you want to forward it.

If during the trixie cycle your package will undergo structural
changes or any other file moves, please see the wiki and upload
to experimental first when these changes are done.

Later during the trixie cycle I expect this bug class to raise in
priority.

Thank you for considering,
Chris

[1] https://wiki.debian.org/UsrMerge

diff -Nru cubemap-1.4.3/debian/changelog cubemap-1.4.3/debian/changelog
--- cubemap-1.4.3/debian/changelog	2020-11-01 18:55:26.0 +0100
+++ cubemap-1.4.3/debian/changelog	2023-12-10 19:39:51.0 +0100
@@ -1,3 +1,11 @@
+cubemap (1.4.3-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Use systemd.pc to determine install location for systemd system unit files.
+(Closes: #-1)
+
+ -- Chris Hofstaedtler   Sun, 10 Dec 2023 19:39:51 +0100
+
 cubemap (1.4.3-2) unstable; urgency=medium
 
   * Remove myself from uploaders.
diff -Nru cubemap-1.4.3/debian/control cubemap-1.4.3/debian/control
--- cubemap-1.4.3/debian/control	2020-11-01 18:55:26.0 +0100
+++ cubemap-1.4.3/debian/control	2023-12-10 19:39:51.0 +0100
@@ -2,7 +2,7 @@
 Section: net
 Priority: optional
 Maintainer: Steinar H. Gunderson 
-Build-Depends: debhelper (>= 9.20160709), libprotobuf-dev, protobuf-compiler, dh-autoreconf, pkg-config, libsystemd-dev, libtomcrypt-dev
+Build-Depends: debhelper (>= 9.20160709), libprotobuf-dev, protobuf-compiler, dh-autoreconf, pkg-config, libsystemd-dev, libtomcrypt-dev, systemd-dev
 Standards-Version: 4.5.0
 Homepage: http://git.sesse.net/?p=cubemap
 
diff -Nru cubemap-1.4.3/debian/patches/1000-systemdsystemunitdir.patch cubemap-1.4.3/debian/patches/1000-systemdsystemunitdir.patch
--- cubemap-1.4.3/debian/patches/1000-systemdsystemunitdir.patch	1970-01-01 01:00:00.0 +0100
+++ cubemap-1.4.3/debian/patches/1000-systemdsystemunitdir.patch	2023-12-10 19:39:51.0 +0100
@@ -0,0 +1,43 @@
+Use systemd.pc to determine install location of systemd system unit files.
+
+Index: cubemap-1.4.3/Makefile.in
+===
+--- cubemap-1.4.3.orig/Makefile.in
 cubemap-1.4.3/Makefile.in
+@@ -7,6 +7,7 @@ CPPFLAGS += -Itlse -DWITH_KTLS -DNO_TLS_
+ CXXFLAGS=-Wall @CXXFLAGS@ @protobuf_CFLAGS@ @libsystemd_CFLAGS@ @libtomcrypt_CFLAGS@ -pthread
+ LDFLAGS=@LDFLAGS@ -pthread
+ LIBS=@LIBS@ @protobuf_LIBS@ @libsystemd_LIBS@ @libtomcrypt_LIBS@
++SYSTEMDSYSTEMUNITDIR=@SYSTEMDSYSTEMUNITDIR@
+ 
+ OBJS=main.o client.o server.o stream.o udpstream.o serverpool.o input.o input_stats.o httpinput.o udpinput.o parse.o config.o acceptor.o stats.o accesslog.o thread.o util.o log.o metacube2.o sa_compare.o timespec.o state.pb.o tlse/tlse.o
+ 
+@@ -41,14 +42,14 @@ install:
+ 		$(DESTDIR)$(LOCALSTATEDIR)/lib/cubemap \
+ 		$(DESTDIR)$(LOCALSTATEDIR)/log/cubemap \
+ 		$(DESTDIR)$(PREFIX)/share/munin/plugins \
+-		$(DESTDIR)/lib/systemd/system
++		$(DESTDIR)$(SYSTEMDSYSTEMUNITDIR)
+ 	$(INSTALL) -m 755 -o root -g root cubemap $(DESTDIR)$(PREFIX)/bin/cubemap
+ 	$(INSTALL) -m 755 -o root -g root munin/cubemap munin/cubemap_input $(DESTDIR)$(PREFIX)/share/munin/plugins/
+ 	gzip -c cubemap.1 > $(DESTDIR)$(PREFIX)/share/man/man1/cubemap.1.gz
+ 	sed \
+ 		-e "s,@prefix[@],$(PREFIX),g" \
+ 		-e "s,@sysconfdir[@],$(SYSCONFDIR),g" \
+-		cubemap.service.in > $(DESTDIR)/lib/systemd/system/cubemap.service
++		cubemap.service.in > $(DESTDIR)$(SYSTEMDSYSTEMUNITDIR)/cubemap.service
+ 	# Make sure we don't overwrite an existing configuration.
+ 	test ! -f $(DESTDIR)$(SYSCONFDIR)/cubemap.config
+ 	sed \
+Index: cubemap-1.4.3/configure.ac
+===
+--- cubemap-1.4.3.orig/configure.ac
 cubemap-1.4.3/configure.ac
+@@ -9,6 +9,7 @@ PKG_PROG_PKG_CONFIG
+ PKG_CHECK_MODULES([libsystemd], [libsystemd])
+ PKG_CHECK_MODULES([protobuf], [protobuf])
+ PKG_CHECK_MODULES([libtomcrypt], [libtomcrypt])
++PKG_CHECK_VAR(SYSTEMDSYSTEMUNITDIR, systemd, systemdsystemunitdir)
+ 
+ CXXFLAGS="$CXXFLAGS -std=gnu++11"
+ 
diff -Nru cubemap-1.4.3/debian/patches/series cubemap-1.4.3/debian/patches/series
--- cubemap-1.4.3/debian/patches/series	1970-01-01 01:00:00.0 +0100
+++ cubemap-1.4.3/debian/patches/series	2023-12-10 19:35:42.0 +0100
@@ -0,0 +1 @@
+1000-systemdsystemunitdir.patch

Bug#1055848: cfgrib failing to find eccodes

[Rebecca N. Palmer]

Control: retitle -1 cfgrib: test failure - can't find eccodes

Because we now enforce that build-depends of testing must be in testing, 
this bug is blocking python-xarray and hence pandas from testing, so is 
more important than this package's popcon would suggest.


I consider it likely that the real bug is in ecmwflibs, specifically 
this function, but haven't actually tested that:

https://sources.debian.org/src/ecmwflibs/2%3A0.5.7-1/ecmwflibs/__init__.py/#L118

Bug#871443: ITA: nanomsg -- nanomsg socket library that provides several common communication patterns

[Phil Wyett]

retitle 871443 ITA: nanomsg -- nanomsg socket library that provides several 
common communication
patterns
owner 871443 !
thanks

Hi,

I am interested in 'nanomsg' and would like to adopt it and remove a small part 
of the QA Teams
workload from them.

I am the Debian Maintainer (DM) of rednotebook, filezilla and libfilezilla, so 
maintaining similar
package types is familiar to me. I am also currently in progress of adopting 
'bglibs'.

Plans:

Initially I will bring the package up to date and inline with Debians current 
practices and
standards. After, I will offer the package long term maintenance as I do with 
all other packages
under my wing.

Regards

Phil

-- 
Playing the game for the games sake.

Web:

* Debian Wiki: https://wiki.debian.org/PhilWyett
* Website: https://kathenas.org
* Social Debian: https://pleroma.debian.social/kathenas/
* Social Instagram: https://www.instagram.com/kathenasorg/




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

Bug#1056780: openmsx: Source-less Windows binary in source package (and other packaging issues)

[Aaron Rainbolt]

On 12/10/23 12:08, Bas Wijnen wrote:

On Sun, Dec 03, 2023 at 02:18:38AM -0600, Aaron Rainbolt wrote:

[Catch 2]

While it is definitely possible to port the
openMSX tests to use catch2 v3, we will be departing from what
upstream supports, and that seems like it could lead to way more work
than necessary (for instance, what if the next major release of
openMSX still uses catch2 v2 and uses it in a way that's incompatible
with catch2 v3? Then we have to maintain that delta from upstream
ourselves, possibly for an extended period of time).

You are misunderstanding me. First of all, I was expecting the changes to be
minor. So I was thinking we can write a patch and let upstream use it. They are
very responsive, so I would expect them to include our patch immediately.

However, if it is a lot of work, it might be better to just file a bug report
upstream. I would expect them to respond to that as well, by doing it
themselves. Although it might take some time.

So because we are in a bit of a hurry with openMSX dropping from testing, I
think the approach for now is to use the bundled catch2-v2, and either port it
for them, or let them know it needs to be ported.


One possible solution might be for Debian to ship multiple major
versions of catch2.

I don't know enough about catch2 to know if that is a good idea. It might be,
but it's certainly out of the scope of this problem.


Maybe this is something we can bring up to whoever maintains catch2 in
Debian.

Yes, that sounds like a good idea. They will probably have an intelligent
opinion about it.


I'm not so sure it's a Lintian bug since HTML files oftentimes *are*
compiled from other source code.

They are, but Lintian is now very forceful in saying that files like these are
definitely compiled, which is just false. So if there is no better way to
detect this, at the very least the certainty of the problem should be decreased
(from error to warning, for example). It is quite common for hand-written text
files (including html files) to contain long lines and it is not reasonable for
all those files to either be required to be line-wrapped, nor for all those
packages to contain overrides.

I think that due to the urgency, I'll make a new package based on your work and
upload it. We can figure out how to handle the remaining issues after that.


Sounds good, and I'll see about a catch2 v3 port. (Part of the reason I 
was against that idea was because I actually tried to do it and it 
failed miserably. I didn't understand enough about how exactly the 
openMSX build system worked to do it "right" and the quick-and-dirty way 
of doing it was discouraged in the catch2 documentation.) I'll probably 
have to learn Perl before I can look into Lintian, but I've wanted to 
learn it before anyway, so may as well do so now.


Thanks you for all your help with this!


Thanks again,
Bas


--
Aaron Rainbolt
Lubuntu Developer
Matrix: @arraybolt3:matrix.org
IRC: arraybolt3 on irc.libera.chat
GitHub: https://github.com/ArrayBolt3