Bug#1024578: mandos: diff for NMU version 1.8.15-1.2

[Adrian Bunk]

Control: tags 1024578 + pending

Dear maintainer,

I've prepared an NMU for mandos (versioned as 1.8.15-1.2) and uploaded 
it to DELAYED/14. Please feel free to tell me if I should cancel it.

cu
Adrian
diff -Nru mandos-1.8.15/debian/changelog mandos-1.8.15/debian/changelog
--- mandos-1.8.15/debian/changelog	2022-10-15 13:19:48.0 +0300
+++ mandos-1.8.15/debian/changelog	2022-12-20 08:17:19.0 +0200
@@ -1,3 +1,11 @@
+mandos (1.8.15-1.2) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Add patch from Andreas Metzler to fix building without gpgme-config.
+(Closes: #1024578)
+
+ -- Adrian Bunk   Tue, 20 Dec 2022 08:17:19 +0200
+
 mandos (1.8.15-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru mandos-1.8.15/debian/patches/gpgme-pkgconf.diff mandos-1.8.15/debian/patches/gpgme-pkgconf.diff
--- mandos-1.8.15/debian/patches/gpgme-pkgconf.diff	1970-01-01 02:00:00.0 +0200
+++ mandos-1.8.15/debian/patches/gpgme-pkgconf.diff	2022-12-20 08:14:19.0 +0200
@@ -0,0 +1,13 @@
+--- mandos-1.8.15.orig/Makefile
 mandos-1.8.15/Makefile
+@@ -96,8 +96,8 @@ GNUTLS_CFLAGS:=$(shell $(PKG_CONFIG) --c
+ GNUTLS_LIBS:=$(shell $(PKG_CONFIG) --libs gnutls)
+ AVAHI_CFLAGS:=$(shell $(PKG_CONFIG) --cflags-only-I avahi-core)
+ AVAHI_LIBS:=$(shell $(PKG_CONFIG) --libs avahi-core)
+-GPGME_CFLAGS:=$(shell gpgme-config --cflags; getconf LFS_CFLAGS)
+-GPGME_LIBS:=$(shell gpgme-config --libs; getconf LFS_LIBS; \
++GPGME_CFLAGS:=$(shell $(PKG_CONFIG) --cflags-only-I gpgme; getconf LFS_CFLAGS)
++GPGME_LIBS:=$(shell $(PKG_CONFIG) --libs gpgme; getconf LFS_LIBS; \
+ 	getconf LFS_LDFLAGS)
+ LIBNL3_CFLAGS:=$(shell $(PKG_CONFIG) --cflags-only-I libnl-route-3.0)
+ LIBNL3_LIBS:=$(shell $(PKG_CONFIG) --libs libnl-route-3.0)
diff -Nru mandos-1.8.15/debian/patches/series mandos-1.8.15/debian/patches/series
--- mandos-1.8.15/debian/patches/series	1970-01-01 02:00:00.0 +0200
+++ mandos-1.8.15/debian/patches/series	2022-12-20 08:17:18.0 +0200
@@ -0,0 +1 @@
+gpgme-pkgconf.diff

Processed: mandos: diff for NMU version 1.8.15-1.2

[Debian Bug Tracking System]

Processing control commands:

> tags 1024578 + pending
Bug #1024578 [src:mandos] mandos: FTBFS against libgpgme-dev >= 1.18.0-2
Added tag(s) pending.

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

Bug#1024561: Unmaintained, keep out of stable

[Adrian Bunk]

On Sat, Nov 26, 2022 at 10:34:28AM -0800, Sam Trenholme wrote:
>...
> If someone can not step up to plate to maintain MaraDNS for Debian, we
> should deprecate and eventually remove the package.
> 
> I may end up making my own .deb files for MaraDNS.

It would also be an option for you to become the maintainer of the 
package in Debian.

> -- Sam
>...

cu
Adrian

Bug#1015123: latex-cjk-chinese-arphic: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity

[韓達耐]

Ho Hilmar

Sorry, I forgot all about this!
I figured out it was a regression so in Unstable you need to go two
versions back for Fontforge, which will ignore the warnings instead of
halting the process.

I'll be back home on 30 December.
Meanwhile I'll send a message upstream.

Thanks for reminding me.

-- 
Danai

On Tue, 20 Dec 2022, 07:21 Hilmar Preuße,  wrote:

> Am 27.07.2022 um 12:10 teilte Danai SAE-HAN (韓達耐) mit:
>
> Hi Danai,
>
> is there progress? Did you get response from upstream?
>
> Hilmar
>
> > Some observations:
> >
> > Going back to fontforge version 20201107~dfsg-4 and its dependencies, I
> > notice the following warning message:
> >
> > 21900/1114292:
> >Add extrema...
> >Simplifying outlines...
> > NaN value in spline creationNaN value in spline creationNaN value in
> spline
> > creationNaN value in spline creationNaN value in spline creationNaN value
> > in spline creationNaN value in spline creationNaN value in spline
> > creationNaN value in spline creationNaN value in spline creationNaN value
> > in spline creationNaN value in spline creationNaN value in spline
> > creationNaN value in spline creationNaN value in spline creationNaN value
> > in spline creationNaN value in spline creationNaN value in spline
> > creationNaN value in spline creationNaN value in spline creationNaN value
> > in spline creationNaN value in spline creationNaN value in spline
> > creationNaN value in spline creationNaN value in spline creationNaN value
> > in spline creationNaN value in spline creationNaN value in spline
> > creationNaN value in spline creationNaN value in spline creationNaN value
> > in spline creationNaN value in spline creationNaN value in spline
> > creationNaN value in spline creationNaN value in spline creationNaN value
> > in spline creationNaN value in spline creationNaN value in spline
> > creationNaN value in spline creationNaN value in spline creationNaN value
> > in spline creation22000/1114292:
> >
> >Add extrema...
> >Simplifying outlines...
> >
> > A more recent version of Fontforge will just let the application hang.
> >
> > I will have to contact upstream to figure out what is causing this.
> >
>
>
> --
> sigfault
>
>

Bug#1026432: libbase58: Leaf library: keep out of bookworm?

[Chris Hofstaedtler]

Source: libbase58
Version: 0.1.4-5
Severity: serious

libbase58 appears to be a leaf library package - nothing else in Debian
debends on it. Apparently it was introduced for some other
bitcoin-related libraries, which are gone again.

I would suggest we waste no resources on this for bookworm. Interested
parties can still pick it up and maintain it properly, if they desire.

Chris

Bug#1026227: marked as done (vagrant: Uninstallable in sid with VirtualBox 7.0.x)

[Debian Bug Tracking System]

Your message dated Tue, 20 Dec 2022 01:27:50 +
with message-id 
and subject line Bug#1026227: fixed in vagrant 2.2.19+dfsg-3
has caused the Debian Bug report #1026227,
regarding vagrant: Uninstallable in sid with VirtualBox 7.0.x
to be marked as done.

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

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


-- 
1026227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026227
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: vagrant
Version: 2.2.19+dfsg-2
Severity: serious

Hi!

Since virtualbox 7.0.4 got uploaded, vagrant is no longer installable
in Debian sid. I assume this will require packaging a new upstream
release to support the new virtualbox version 7.0.x series.

Thanks,
Guillem
--- End Message ---
--- Begin Message ---
Source: vagrant
Source-Version: 2.2.19+dfsg-3
Done: Antonio Terceiro 

We believe that the bug you reported is fixed in the latest version of
vagrant, which is due to be installed in the Debian FTP archive.

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

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

Debian distribution maintenance software
pp.
Antonio Terceiro  (supplier of updated vagrant package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 19 Dec 2022 21:53:30 -0300
Source: vagrant
Architecture: source
Version: 2.2.19+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Antonio Terceiro 
Closes: 1026227
Changes:
 vagrant (2.2.19+dfsg-3) unstable; urgency=medium
 .
   * Add upstream patch with VirtualBox 7.0 support (Closes: #1026227)
Checksums-Sha1:
 b76f743948f5dd6bf9b28d1a15e28081dd85d813 2615 vagrant_2.2.19+dfsg-3.dsc
 ea672eee40fdab2ac5f71ea4ac20e94631e06b14 18128 
vagrant_2.2.19+dfsg-3.debian.tar.xz
 8cd4e3da0e0e2cd8037a21afd86e59abb986f11f 15085 
vagrant_2.2.19+dfsg-3_source.buildinfo
Checksums-Sha256:
 fd60397fc62e9eae88f91e26aa25b010bf4efc38e71d07898791119970abac91 2615 
vagrant_2.2.19+dfsg-3.dsc
 f2acc6f8e4f38488085f124f9f745b2ca94286b7dfd7f1b9b525388654a5e22f 18128 
vagrant_2.2.19+dfsg-3.debian.tar.xz
 be902f200b4edb19cd1e6015f3d8abc9cd4623dc9c1d526367e5b447680cbb78 15085 
vagrant_2.2.19+dfsg-3_source.buildinfo
Files:
 f31b808a79116008309abfd10dc5b978 2615 admin optional vagrant_2.2.19+dfsg-3.dsc
 96a3fd9c82ff6cb2b939c49be4f0e1dc 18128 admin optional 
vagrant_2.2.19+dfsg-3.debian.tar.xz
 5468adaf35ab1a9f2adb03a17296caaa 15085 admin optional 
vagrant_2.2.19+dfsg-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAmOhB5wACgkQ/A2xu81G
C95OVhAA43U+UMk8R/+bySZzjyvRkryGHVs6rG9AoyTveBhDPdQ/5Cs8Y9HzWnWT
5YxUEJjuU8A8p8tddRCjYcr3CWaOcJBP1P1fm5CWEv4q01k+YaLBw7IkE2Jem9UR
UiQP3d3Df40w3csB6zIBtvq/h+KVAvMSd6JLyflcSMzVUHKAZYyQiLJh3tQxEw5F
tFBtpc3jV7SxQlp/uJYQGk+ZunHR2Y0Ms62m42SbP880J87zt4Oz4hUpGkqexs1g
TskkKEU9j9Q98y9Rb7xhKQDLmhVGkoS6ZfJ0dVTKg6yZy1weJqIxXSX57kd8kLWm
JLV+rKP4EJQRmG4CL61hk31nld/mhDDDkefaH1xx/OHJjjeIpJ2iKstZ4aZUvPmX
GD69gr7IxryKB8pz6z65LR1yDM+eSTGO1yIxB415fIJCtXSp2tPH1UzXQskC6Zwk
V4sZRugq9jITZ2fOcDOt3nypYGvCWIcPTHYZYjhBV/SUPhN+YTPMBihOo0tw+Ad8
u+ysBNwacAg0xrKIxDyxGHpL5k5fHtsyg1YXZ/TsDzl/LZrsIbL+Kk0dmW/qb42E
3XOaFEuz0dQ49vOobtYDPstc1FopmWEpNskSntvi9zBEZB6d/cKw8m6KeckF3XNr
BRtrcGCmqqWGn5nU6jvPo4Y4mWjmQ3fvEMHLLo6EA/9yhukskTY=
=OXDB
-END PGP SIGNATURE End Message ---

Bug#1026431: Remove scalc for bookworm?

[Chris Hofstaedtler]

Source: scalc
Version: 0.2.4-6
Severity: serious

It appears src:scalc only builds a library package, and nothing in
Debian uses it. If people see value in keeping it in bookworm,
please speak up.

I'll note that there is a new, completely unrelated project using
the "scalc" name, so it might be a good idea to solve this sooner
than later :-)

Chris

Bug#998889: libcommoncpp2: Remove in bookworm?

[Chris Hofstaedtler]

* Adrian Bunk :
> Source: libcommoncpp2
[..]
> src:ucommon is the successor of libcommoncpp2, and the only
> remaining build dependency on libcommoncpp2-dev in
> vdr-plugin-fritzbox is stale.

It appears all r-(build-)deps are gone. Should src:libcommoncpp2
also go away from unstable?

Chris

Bug#1026427: jekyll: depends on deprecated and broken ruby-safe-yaml

[Antonio Terceiro]

Package: jekyll
Version: 3.9.0+dfsg-5
Severity: serious
Tags: upstream

Dear Maintainer,

Working to get ruby3.1 as the default Ruby version it was noticed that
ruby-safe-yaml is incompatible with ruby3.1 and thus deprecated. Most
upstreams have dropped their dependencies on it; I checked and jekyll is
not there yet. There is this pull request upstream, but that didn't get
into a release yet:

https://github.com/jekyll/jekyll/pull/8772

ruby-safe-yaml will soon be removed from testing due to this (maybe even
before the autoremoval), jekyll needs to drop its dependency on it.

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

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


signature.asc
Description: PGP signature

Bug#1022866: marked as done (libghc-product-isomorphic-doc: depends on non-existing haddock-interface-35)

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 23:36:29 +
with message-id 
and subject line Bug#1026380: Removed package(s) from unstable
has caused the Debian Bug report #1022866,
regarding libghc-product-isomorphic-doc: depends on non-existing 
haddock-interface-35
to be marked as done.

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

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


-- 
1022866: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022866
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libghc-product-isomorphic-doc
Version: 0.0.3.3-2
Severity: serious

Hi, libghc-dice-doc depends on haddock-interface-35 but that package
does not exist in the archive.

-Ralf.
--- End Message ---
--- Begin Message ---
Version: 0.0.3.3-2+rm

Dear submitter,

as the package haskell-product-isomorphic has just been removed from the Debian 
archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1026380

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1022189: marked as done (Removal notice: obsolete)

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 23:36:29 +
with message-id 
and subject line Bug#1026380: Removed package(s) from unstable
has caused the Debian Bug report #1022189,
regarding Removal notice: obsolete
to be marked as done.

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

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


-- 
1022189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022189
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-product-isomorphic
Version: 0.0.3.3-2
Severity: serious

I intend to remove this package:

  * The current version is incompatible with GHC 9.0 and FTBFS
  * Seems unmaintained; Last upload more than 3 years ago
  * It's not part of the latest Stackage LTS

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias
--- End Message ---
--- Begin Message ---
Version: 0.0.3.3-2+rm

Dear submitter,

as the package haskell-product-isomorphic has just been removed from the Debian 
archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1026380

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1015150: marked as done (haskell-product-isomorphic FTBFS: The constructor ‘PlainTV’ should have 2 arguments, but has been given 1)

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 23:36:29 +
with message-id 
and subject line Bug#1026380: Removed package(s) from unstable
has caused the Debian Bug report #1015150,
regarding haskell-product-isomorphic FTBFS: The constructor ‘PlainTV’ should 
have 2 arguments, but has been given 1
to be marked as done.

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

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


-- 
1015150: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015150
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-product-isomorphic
Version: 0.0.3.3-2
Severity: serious
Tags: ftbfs bookworm sid

https://buildd.debian.org/status/package.php?p=haskell-product-isomorphic=sid

...
src/Data/Functor/ProductIsomorphic/TH/Internal.hs:47:10: error:
• The constructor ‘PlainTV’ should have 2 arguments, but has been given 1
• In the pattern: PlainTV n
  In an equation for ‘getTV’: getTV (PlainTV n) = n
  In an equation for ‘recordInfo'’:
  recordInfo'
= d
where
d (TyConI tcon)
  = do (tcn, bs, r) <- ... <|> ...
   
d _ = Nothing
getTV (PlainTV n) = n
getTV (KindedTV n _) = n
buildT tcn vns = foldl' appT (conT tcn) [varT vn | vn <- vns]
   |
47 |   getTV (PlainTV n)=  n
   |  ^
 at /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 107.

Debian::Debhelper::Buildsystem::Haskell::Recipes::run_quiet("debian/hlibrary.setup",
 "haddock", "--builddir=dist-ghc", "--with-haddock=/usr/bin/haddock", 
"--with-ghc=ghc", "--verbose=2", "--html", "--hoogle", ...) called at 
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 131

Debian::Debhelper::Buildsystem::Haskell::Recipes::run("debian/hlibrary.setup", 
"haddock", "--builddir=dist-ghc", "--with-haddock=/usr/bin/haddock", 
"--with-ghc=ghc", "--verbose=2", "--html", "--hoogle", ...) called at 
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 709
Debian::Debhelper::Buildsystem::Haskell::Recipes::haddock_recipe() 
called at -e line 1
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: build-ghc-stamp] Error 25
--- End Message ---
--- Begin Message ---
Version: 0.0.3.3-2+rm

Dear submitter,

as the package haskell-product-isomorphic has just been removed from the Debian 
archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1026380

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1022867: marked as done (libghc-persistable-record-doc: depends on non-existing haddock-interface-35)

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 23:35:59 +
with message-id 
and subject line Bug#1026377: Removed package(s) from unstable
has caused the Debian Bug report #1022867,
regarding libghc-persistable-record-doc: depends on non-existing 
haddock-interface-35
to be marked as done.

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

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


-- 
1022867: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022867
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libghc-persistable-record-doc
Version: 0.6.0.5-1
Severity: serious

Hi, libghc-persistable-record-doc depends on haddock-interface-35 but
that package does not exist in the archive.

-Ralf.
--- End Message ---
--- Begin Message ---
Version: 0.6.0.5-1+rm

Dear submitter,

as the package haskell-persistable-record has just been removed from the Debian 
archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1026377

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1022190: marked as done (Removal notice: obsolete)

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 23:35:59 +
with message-id 
and subject line Bug#1026377: Removed package(s) from unstable
has caused the Debian Bug report #1022190,
regarding Removal notice: obsolete
to be marked as done.

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

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


-- 
1022190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022190
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-persistable-record
Version: 0.6.0.5-1
Severity: serious

I intend to remove this package, since it depends on the broken
haskell-product-isomorphic package (see https://bugs.debian.org/1022189).

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias
--- End Message ---
--- Begin Message ---
Version: 0.6.0.5-1+rm

Dear submitter,

as the package haskell-persistable-record has just been removed from the Debian 
archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1026377

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#982830: marked as done (golang-code.gitea-git: unmaintained go library - keep out of testing)

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 23:34:12 +
with message-id 
and subject line Bug#1026367: Removed package(s) from unstable
has caused the Debian Bug report #982830,
regarding golang-code.gitea-git: unmaintained go library - keep out of testing
to be marked as done.

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

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


-- 
982830: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982830
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-code.gitea-git
Version: 0.0~git20190411.63b74d4+ds-1
Severity: serious

Upstream (Gitea) appears to have moved on to another solution, so
this is dead code (upstream repo is marked as archived).

Lets not have it in bullseye, especially as nothing else depends on
it, and its orphaned in Debian.

Chris
--- End Message ---
--- Begin Message ---
Version: 0.0~git20190411.63b74d4+ds-1+rm

Dear submitter,

as the package golang-code.gitea-git has just been removed from the Debian 
archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1026367

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1022192: marked as done (Removal notice: obsolete)

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 23:35:33 +
with message-id 
and subject line Bug#1026378: Removed package(s) from unstable
has caused the Debian Bug report #1022192,
regarding Removal notice: obsolete
to be marked as done.

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

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


-- 
1022192: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022192
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-relational-query
Version: 0.12.3.0-1
Severity: serious

I intend to remove this package, since it depends on the broken
haskell-product-isomorphic package (see https://bugs.debian.org/1022189).

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias
--- End Message ---
--- Begin Message ---
Version: 0.12.3.0-1+rm

Dear submitter,

as the package haskell-relational-query has just been removed from the Debian 
archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1026378

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#970915: marked as done (isakmpd: outdated upstream source unacceptable for distribution)

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 23:34:39 +
with message-id 
and subject line Bug#1026370: Removed package(s) from unstable
has caused the Debian Bug report #970915,
regarding isakmpd: outdated upstream source unacceptable for distribution
to be marked as done.

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

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


-- 
970915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970915
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: isakmpd
Version: 20041012-10
Severity: grave

Our isakmpd sources are by now 16 years old. The sources in OpenBSD
have in the meantime seen a number of improvements and security
fixes, plus protocol fixes.

Shipping such an old version with known security problems is a
disgrace to our users.
If we do not want to properly maintain this, lets stop shipping it
at all - we have better IPsec VPN options to choose from.

Chris
--- End Message ---
--- Begin Message ---
Version: 20041012-10+rm

Dear submitter,

as the package isakmpd has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1026370

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1026365: marked as done (golang-code.gitea-git: unmaintained go library - keep out of testing)

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 23:33:47 +
with message-id 
and subject line Bug#1026366: Removed package(s) from unstable
has caused the Debian Bug report #1026365,
regarding golang-code.gitea-git: unmaintained go library - keep out of testing
to be marked as done.

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

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


-- 
1026365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026365
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-code.gitea-git
Version: 0.0~git20190411.63b74d4+ds-1
Severity: serious

Upstream (Gitea) appears to have moved on to another solution, so
this is dead code (upstream repo is marked as archived).

Lets not have it in bullseye, especially as nothing else depends on
it, and its orphaned in Debian.

Chris
--- End Message ---
--- Begin Message ---
Version: 0.0~git20171220.79eee8f-3+rm

Dear submitter,

as the package golang-code.gitea-sdk has just been removed from the Debian 
archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1026366

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#942281: marked as done (libapache2-mod-ruid2 package missing)

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 23:33:20 +
with message-id 
and subject line Bug#1026363: Removed package(s) from unstable
has caused the Debian Bug report #942281,
regarding libapache2-mod-ruid2 package missing
to be marked as done.

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

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


-- 
942281: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942281
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libapache2-mod-ruid2
Version: 0.9.8-3
Severity: grave

The package libapache2-mod-ruid2 is completely missing from Debian 10

(Buster) repositories, what's the problem why is it missing ?

It's available in previous releases and the the unstable release (SID)

but not Buster

jessie (httpd): 0.9.8-3
Binary packages: libapache2-mod-ruid2
stretch (httpd): 0.9.8-3
Binary packages: libapache2-mod-ruid2
sid (httpd): 0.9.8-3
Binary packages: libapache2-mod-ruid2
--- End Message ---
--- Begin Message ---
Version: 0.9.8-4+rm

Dear submitter,

as the package libapache2-mod-ruid2 has just been removed from the Debian 
archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1026363

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#866395: marked as done (libapache2-mod-ruid2: Server crashes (Signal 6 aborted) with mod_ruid2 after jessie->stretch update)

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 23:33:20 +
with message-id 
and subject line Bug#1026363: Removed package(s) from unstable
has caused the Debian Bug report #866395,
regarding libapache2-mod-ruid2: Server crashes (Signal 6 aborted) with 
mod_ruid2 after jessie->stretch update
to be marked as done.

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

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


-- 
866395: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866395
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libapache2-mod-ruid2
Version: 0.9.8-3
Severity: grave

Dear Maintainer,

I'm trying to use the ruid2 module to switch the context of some CGI
applications. This set-up has worked fine on Debian oldstable but
after the upgrade the Apache does not work anymore.

In order to track down this issue, I disabled all the
modules and now only the following ones are loaded:

Loaded Modules:
 core_module (static)
 so_module (static)
 watchdog_module (static)
 http_module (static)
 log_config_module (static)
 logio_module (static)
 version_module (static)
 unixd_module (static)
 authz_core_module (shared)
 mpm_worker_module (shared)
 ruid2_module (shared)


The error log looks like this:

[Thu Jun 29 14:34:21.382053 2017] [:notice] [pid 23114:tid 139997118780608] 
mod_ruid2/0.9.8 enabled
[Thu Jun 29 14:34:21.383740 2017] [mpm_worker:notice] [pid 23114:tid 
139997118780608] AH00292: Apache/2.4.25 (Debian) configured -- resuming normal 
operations
[Thu Jun 29 14:34:21.383804 2017] [core:notice] [pid 23114:tid 139997118780608] 
AH00094: Command line: '/usr/sbin/apache2'
[Thu Jun 29 14:34:22.385189 2017] [core:notice] [pid 23114:tid 139997118780608] 
AH00052: child pid 23115 exit signal Aborted (6)
[Thu Jun 29 14:34:22.385364 2017] [core:notice] [pid 23114:tid 139997118780608] 
AH00052: child pid 23116 exit signal Aborted (6)
[Thu Jun 29 14:34:24.388619 2017] [core:notice] [pid 23114:tid 139997118780608] 
AH00052: child pid 23171 exit signal Aborted (6)


I tried to generate a backtrace from GDB but I was unable to locate
any debug symbols package of mod_ruid2:

Thread 3 "apache2" received signal SIGABRT, Aborted.
[Switching to Thread 0x756bb700 (LWP 24165)]
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
51  ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt full
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
set = {__val = {18446744066193088519, 140737354102536, 140737310861680, 
8412440912, 140737354101680, 140737310861664, 140737342537836, 252833149, 
4294967295, 140737354102936, 140737338756568, 140737354102936, 3, 0, 5, 0}}
pid = 
tid = 
#1  0x771823fa in __GI_abort () at abort.c:89
save_stage = 2
act = {__sigaction_handler = {sa_handler = 0x2020202020202020, 
sa_sigaction = 0x2020202020202020}, sa_mask = {__val = {2314885530818453536, 5, 
0, 140737310862376, 140737351921873, 2, 0, 64, 140737342551037, 1, 
140737342553876, 
  140737353596552, 0, 140737310862272, 140737310862304, 33}}, 
sa_flags = -134253648, sa_restorer = 0x756babc0}
sigs = {__val = {32, 0 }}
#2  0x774f3cee in __nptl_setxid_error (cmdp=cmdp@entry=0x756babc0, 
error=) at allocatestack.c:1074
olderror = 
#3  0x774f3f27 in __nptl_setxid (cmdp=0x756babc0) at 
allocatestack.c:1181
signalled = 
result = 0
self = 0x756bb700
runp = 
error = 
#4  0x77202c26 in __GI_setgroups (n=, groups=) at ../sysdeps/unix/sysv/linux/setgroups.c:33
__p = 
__cmd = {syscall_no = 116, id = {1, 140737310862432, 140737353596552}, 
cntr = 0, error = 1}
__result = 
groups = 
n = 
#5  0x760c46e8 in ?? () from /usr/lib/apache2/modules/mod_ruid2.so
No symbol table info available.
#6  0x760c4e06 in ?? () from /usr/lib/apache2/modules/mod_ruid2.so
No symbol table info available.
#7  0x55595140 in ap_run_post_read_request ()
No symbol table info available.
#8  0x55596548 in ap_read_request ()
No symbol table info available.
#9  0x555bfb98 in ?? ()
No symbol table info available.
#10 0x555b56f0 in ap_run_process_connection ()
No symbol table info available.
#11 0x762cce4a in ?? () from /usr/lib/apache2/modules/mod_mpm_worker.so
No symbol table info available.
#12 0x774f4494 in start_thread (arg=0x756bb700) at 
pthread_create.c:333
__res = 
pd = 0x756bb700
now = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140737310865152, 
-508518614849429, 0, 

Bug#906032: marked as done (FTBFS: LaTeX first run problem.)

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 23:32:53 +
with message-id 
and subject line Bug#1026361: Removed package(s) from unstable
has caused the Debian Bug report #906032,
regarding FTBFS: LaTeX first run problem.
to be marked as done.

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

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


-- 
906032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906032
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnuift
Version: 0.1.14+ds-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi!
After applying the patch for gcc-8 FTBFS (#897761), the build fails later on
due to SGML issues:

Processing file configuring-and-hacking-the-gift.sgml
Use of uninitialized value in hash element at 
/usr/share/texinfo/Texinfo/Structuring.pm line 687.
/tmp/linuxdoc-tools.en1tzfmSG7/sgmltmp.configuring-and-hacking-the-gift.2.texi:1297:
 warning: @appendix missing argument
/tmp/linuxdoc-tools.en1tzfmSG7/sgmltmp.configuring-and-hacking-the-gift.2.texi:919:
 @node `plug_in_fo-cc' previously defined
/tmp/linuxdoc-tools.en1tzfmSG7/sgmltmp.configuring-and-hacking-the-gift.2.texi:636:
 here is the previous definition as @node
/tmp/linuxdoc-tools.en1tzfmSG7/sgmltmp.configuring-and-hacking-the-gift.2.texi:1023:
 @node `Some summarizing remarks' previously defined
/tmp/linuxdoc-tools.en1tzfmSG7/sgmltmp.configuring-and-hacking-the-gift.2.texi:747:
 here is the previous definition as @node
/tmp/linuxdoc-tools.en1tzfmSG7/sgmltmp.configuring-and-hacking-the-gift.2.texi:1041:
 @node `Typing' previously defined
/tmp/linuxdoc-tools.en1tzfmSG7/sgmltmp.configuring-and-hacking-the-gift.2.texi:765:
 here is the previous definition as @node
/tmp/linuxdoc-tools.en1tzfmSG7/sgmltmp.configuring-and-hacking-the-gift.2.texi:1049:
 @node `How to obtain parameters' previously defined
/tmp/linuxdoc-tools.en1tzfmSG7/sgmltmp.configuring-and-hacking-the-gift.2.texi:773:
 here is the previous definition as @node
/tmp/linuxdoc-tools.en1tzfmSG7/sgmltmp.configuring-and-hacking-the-gift.2.texi:1062:
 @node `Administrative code' previously defined
/tmp/linuxdoc-tools.en1tzfmSG7/sgmltmp.configuring-and-hacking-the-gift.2.texi:787:
 here is the previous definition as @node
/tmp/linuxdoc-tools.en1tzfmSG7/sgmltmp.configuring-and-hacking-the-gift.2.texi:1076:
 @node `Interfacing with query engines' previously defined
/tmp/linuxdoc-tools.en1tzfmSG7/sgmltmp.configuring-and-hacking-the-gift.2.texi:800:
 here is the previous definition as @node
/tmp/linuxdoc-tools.en1tzfmSG7/sgmltmp.configuring-and-hacking-the-gift.2.texi:1098:
 @node `Makefiles' previously defined
/tmp/linuxdoc-tools.en1tzfmSG7/sgmltmp.configuring-and-hacking-the-gift.2.texi:822:
 here is the previous definition as @node
/tmp/linuxdoc-tools.en1tzfmSG7/sgmltmp.configuring-and-hacking-the-gift.2.texi:636:
 warning: node next `plug_in_fo-cc' in menu `Static linking' and in sectioning 
`CAFHierarchy' differ
/tmp/linuxdoc-tools.en1tzfmSG7/sgmltmp.configuring-and-hacking-the-gift.2.texi:636:
 warning: node up `plug_in_fo-cc' in menu `libGIFTQuHierarchy browsing fixed 
hierarchies' and in sectioning `libGIFTAcHierarchy a simple hierarchy accessor' 
differ
/tmp/linuxdoc-tools.en1tzfmSG7/sgmltmp.configuring-and-hacking-the-gift.2.texi:747:
 warning: node prev `Some summarizing remarks' in menu `libGIFTQuHierarchy 
browsing fixed hierarchies' and in sectioning `libGIFTAcHierarchy a simple 
hierarchy accessor' differ
/tmp/linuxdoc-tools.en1tzfmSG7/sgmltmp.configuring-and-hacking-the-gift.2.texi:747:
 warning: node up `Some summarizing remarks' in menu `How to write an Query 
Proccessor plugin' and in sectioning `How to write an Accessor plugin' differ
/tmp/linuxdoc-tools.en1tzfmSG7/sgmltmp.configuring-and-hacking-the-gift.2.texi:765:
 warning: node `Accessor lifecycle' is prev for `Typing' in menu but not in 
sectioning
/tmp/linuxdoc-tools.en1tzfmSG7/sgmltmp.configuring-and-hacking-the-gift.2.texi:800:
 warning: node next `Interfacing with query engines' in menu `CQuery lifecycle' 
and in sectioning `Accessor lifecycle' differ
/tmp/linuxdoc-tools.en1tzfmSG7/sgmltmp.configuring-and-hacking-the-gift.2.texi:810:
 warning: node `Typing' is next for `Accessor lifecycle' in menu but not in 
sectioning
/tmp/linuxdoc-tools.en1tzfmSG7/sgmltmp.configuring-and-hacking-the-gift.2.texi:822:
 warning: node up `Makefiles' in menu `How to write an Query Proccessor plugin' 
and in sectioning `How to write an Accessor plugin' differ
/tmp/linuxdoc-tools.en1tzfmSG7/sgmltmp.configuring-and-hacking-the-gift.2.texi:873:
 warning: node next `libGIFTQuHierarchy browsing fixed 

Bug#897761: marked as done (gnuift: ftbfs with GCC-8)

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 23:32:53 +
with message-id 
and subject line Bug#1026361: Removed package(s) from unstable
has caused the Debian Bug report #897761,
regarding gnuift: ftbfs with GCC-8
to be marked as done.

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

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


-- 
897761: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897761
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gnuift
Version: 0.1.14+ds-1
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-8

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-8/g++-8, but succeeds to build with gcc-7/g++-7. The
severity of this report will be raised before the buster release.

The full build log can be found at:
http://aws-logs.debian.net/2018/05/01/gcc8/gnuift_0.1.14+ds-1_unstable_gcc8.log.gz
The last lines of the build log are at the end of this report.

To build with GCC 8, either set CC=gcc-8 CXX=g++-8 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-8/porting_to.html

[...]
   return (*mContent);
^
make[4]: *** [Makefile:511: CAcDistanceMatrix.lo] Error 1
make[4]: Leaving directory 
'/<>/gnuift-0.1.14+ds/libGIFTAcDistanceMatrix/cc'
make[4]: Entering directory 
'/<>/gnuift-0.1.14+ds/libGIFTAcDistanceMatrix/cc'
/bin/bash ../../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. 
-I../.. -DHAS_BOOL -I../../libMRML/include 
-I../../libGIFTAcInvertedFile/include -I../../libGIFTAcDistanceMatrix/include 
-I../../libGIFTAcURL2FTS/include -I../../libGIFTQuBayesian/include 
-I/sbuild-nonexistent/browsing/libGIFTQuBayesian/include  -Wdate-time 
-D_FORTIFY_SOURCE=2  -g -O2 -fdebug-prefix-map=/<>/gnuift-0.1.14+ds=. 
-fstack-protector-strong -Wformat -Werror=format-security -DEF_PROTECT_BELOW=1 
-DEF_PROTECT_FREE -DEF_PROTECT_ALIGNMENT=8 -DEF_FILL=42  -I /usr/include/mysql 
-DHAVE_LIBPTHREAD -D__GIFT_NEW_IS_MALLOC   -D__GIFT_USES_THREADS__ -pthread -c 
-o CDrawer.lo CDrawer.cc
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../.. -DHAS_BOOL 
-I../../libMRML/include -I../../libGIFTAcInvertedFile/include 
-I../../libGIFTAcDistanceMatrix/include -I../../libGIFTAcURL2FTS/include 
-I../../libGIFTQuBayesian/include 
-I/sbuild-nonexistent/browsing/libGIFTQuBayesian/include -Wdate-time 
-D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>/gnuift-0.1.14+ds=. 
-fstack-protector-strong -Wformat -Werror=format-security -DEF_PROTECT_BELOW=1 
-DEF_PROTECT_FREE -DEF_PROTECT_ALIGNMENT=8 -DEF_FILL=42 -I /usr/include/mysql 
-DHAVE_LIBPTHREAD -D__GIFT_NEW_IS_MALLOC -D__GIFT_USES_THREADS__ -pthread -c 
CDrawer.cc  -fPIC -DPIC -o .libs/CDrawer.o
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../.. -DHAS_BOOL 
-I../../libMRML/include -I../../libGIFTAcInvertedFile/include 
-I../../libGIFTAcDistanceMatrix/include -I../../libGIFTAcURL2FTS/include 
-I../../libGIFTQuBayesian/include 
-I/sbuild-nonexistent/browsing/libGIFTQuBayesian/include -Wdate-time 
-D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>/gnuift-0.1.14+ds=. 
-fstack-protector-strong -Wformat -Werror=format-security -DEF_PROTECT_BELOW=1 
-DEF_PROTECT_FREE -DEF_PROTECT_ALIGNMENT=8 -DEF_FILL=42 -I /usr/include/mysql 
-DHAVE_LIBPTHREAD -D__GIFT_NEW_IS_MALLOC -D__GIFT_USES_THREADS__ -pthread -c 
CDrawer.cc -o CDrawer.o >/dev/null 2>&1
make[4]: Leaving directory 
'/<>/gnuift-0.1.14+ds/libGIFTAcDistanceMatrix/cc'
make[4]: Entering directory 
'/<>/gnuift-0.1.14+ds/libGIFTAcDistanceMatrix/cc'
/bin/bash ../../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. 
-I../.. -DHAS_BOOL -I../../libMRML/include 
-I../../libGIFTAcInvertedFile/include -I../../libGIFTAcDistanceMatrix/include 
-I../../libGIFTAcURL2FTS/include -I../../libGIFTQuBayesian/include 
-I/sbuild-nonexistent/browsing/libGIFTQuBayesian/include  -Wdate-time 
-D_FORTIFY_SOURCE=2  -g -O2 -fdebug-prefix-map=/<>/gnuift-0.1.14+ds=. 
-fstack-protector-strong -Wformat -Werror=format-security -DEF_PROTECT_BELOW=1 
-DEF_PROTECT_FREE -DEF_PROTECT_ALIGNMENT=8 -DEF_FILL=42  -I /usr/include/mysql 

Bug#999724: marked as done (ruby-omniauth-salesforce: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in acti

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 23:29:26 +
with message-id 
and subject line Bug#1026266: Removed package(s) from unstable
has caused the Debian Bug report #999724,
regarding ruby-omniauth-salesforce: FTBFS with ruby-omniauth 2.0.x: ERROR: Test 
"ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in 
`rescue in block in activate_dependencies': Could not find 'omniauth' (~> 1.0) 
among 85 total gem(s) (Gem::MissingSpecError)
to be marked as done.

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

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


-- 
999724: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999724
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-omniauth-salesforce
Version: 1.0.5-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby-omniauth-2.0

Hi,

I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test
rebuild, ruby-omniauth-salesforce was found to fail to build in that situation.

To reproduce this locally, you need to install ruby-omniauth from experimental
on an unstable system or build chroot. I would expect a new upstream version to
work against the latest ruby-omniauth just fine.

Relevant part (hopefully):
> /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block 
> in activate_dependencies': Could not find 'omniauth' (~> 1.0) among 85 total 
> gem(s) (Gem::MissingSpecError)
> Checked in 
> 'GEM_PATH=/<>/debian/ruby-omniauth-salesforce/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0'
>  at: 
> /<>/debian/ruby-omniauth-salesforce/usr/share/rubygems-integration/all/specifications/omniauth-salesforce-1.0.5.gemspec,
>  execute `gem env` for more information
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1401:in `block 
> in activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in 
> `activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in 
> `activate'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `block in gem'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `synchronize'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `gem'
>   from -e:1:in `'
> /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not 
> find 'omniauth' (~> 1.0) - did find: [omniauth-2.0.4] 
> (Gem::MissingSpecVersionError)
> Checked in 
> 'GEM_PATH=/<>/debian/ruby-omniauth-salesforce/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0'
>  , execute `gem env` for more information
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1402:in `block 
> in activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in 
> `activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in 
> `activate'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `block in gem'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `synchronize'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `gem'
>   from -e:1:in `'
> addressable (2.8.0)
> benchmark (default: 0.1.0)
> bigdecimal (default: 2.0.0)
> bundler (default: 2.1.4)
> cgi (default: 0.1.0)
> crack (0.4.4)
> csv (default: 3.1.2)
> date (default: 3.0.0)
> dbm (default: 1.1.0)
> delegate (default: 0.1.0)
> did_you_mean (default: 1.4.0)
> diff-lcs (1.4.4)
> docile (1.1.5)
> etc (default: 1.1.0)
> faraday (1.1.0)
> fcntl (default: 1.0.0)
> fiddle (default: 1.0.0)
> fileutils (default: 1.4.1)
> forwardable (default: 1.3.1)
> gdbm (default: 2.1.0)
> getoptlong (default: 0.1.0)
> hashdiff (1.0.1)
> hashie (3.5.5)
> io-console (default: 0.5.6)
> ipaddr (default: 1.2.2)
> irb (default: 1.2.6)
> json (default: 2.3.0)
> jwt (2.2.2)
> logger (default: 1.4.2)
> matrix (default: 0.2.0)
> minitest (5.13.0)
> multi_json 

Bug#999714: marked as done (ruby-omniauth-crowd: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in activate_

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 23:29:52 +
with message-id 
and subject line Bug#1026267: Removed package(s) from unstable
has caused the Debian Bug report #999714,
regarding ruby-omniauth-crowd: FTBFS with ruby-omniauth 2.0.x: ERROR: Test 
"ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in 
`rescue in block in activate_dependencies': Could not find 'omniauth' (~> 1.0) 
among 84 total gem(s) (Gem::MissingSpecError)
to be marked as done.

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

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


-- 
999714: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999714
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-omniauth-crowd
Version: 2.4.0-1.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby-omniauth-2.0

Hi,

I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test
rebuild, ruby-omniauth-crowd was found to fail to build in that situation.

To reproduce this locally, you need to install ruby-omniauth from experimental
on an unstable system or build chroot.

Relevant part (hopefully):
> /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block 
> in activate_dependencies': Could not find 'omniauth' (~> 1.0) among 84 total 
> gem(s) (Gem::MissingSpecError)
> Checked in 
> 'GEM_PATH=/<>/debian/ruby-omniauth-crowd/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0'
>  at: 
> /<>/debian/ruby-omniauth-crowd/usr/share/rubygems-integration/all/specifications/omniauth_crowd-2.4.0.gemspec,
>  execute `gem env` for more information
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1401:in `block 
> in activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in 
> `activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in 
> `activate'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `block in gem'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `synchronize'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `gem'
>   from -e:1:in `'
> /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not 
> find 'omniauth' (~> 1.0) - did find: [omniauth-2.0.4] 
> (Gem::MissingSpecVersionError)
> Checked in 
> 'GEM_PATH=/<>/debian/ruby-omniauth-crowd/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0'
>  , execute `gem env` for more information
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1402:in `block 
> in activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in 
> `activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in 
> `activate'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `block in gem'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `synchronize'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `gem'
>   from -e:1:in `'
> activesupport (6.0.3.7)
> addressable (2.8.0)
> atomic (1.1.16)
> benchmark (default: 0.1.0)
> bigdecimal (default: 2.0.0)
> bundler (default: 2.1.4)
> cgi (default: 0.1.0)
> concurrent-ruby (1.1.6)
> concurrent-ruby-edge (0.6.0)
> crack (0.4.4)
> csv (default: 3.1.2)
> date (default: 3.0.0)
> dbm (default: 1.1.0)
> delegate (default: 0.1.0)
> did_you_mean (default: 1.4.0)
> diff-lcs (1.4.4)
> etc (default: 1.1.0)
> fcntl (default: 1.0.0)
> fiddle (default: 1.0.0)
> fileutils (default: 1.4.1)
> forwardable (default: 1.3.1)
> gdbm (default: 2.1.0)
> getoptlong (default: 0.1.0)
> hashdiff (1.0.1)
> hashie (3.5.5)
> i18n (1.8.11)
> io-console (default: 0.5.6)
> ipaddr (default: 1.2.2)
> irb (default: 1.2.6)
> json (default: 2.3.0)
> logger (default: 1.4.2)
> matrix (default: 0.2.0)
> minitest (5.13.0)
> mutex_m (default: 0.1.0)
> net-pop (default: 0.1.0)
> net-smtp 

Bug#931756: marked as done (bindgraph stop action fails)

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 23:32:09 +
with message-id 
and subject line Bug#1026360: Removed package(s) from unstable
has caused the Debian Bug report #931756,
regarding bindgraph stop action fails
to be marked as done.

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

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


-- 
931756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931756
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bindgraph
Version: 0.2a-6
Severity: serious
Tags: patch

Hello,

the sysv init script for bindgraph fails on the stop action with the message 
start-stop-daemon: matching only on non-root pidfile 
/var/run/servergraph/bindgraph.pid is insecure

Relevant other bugs are 923421, 921016, and 921557.

What works for me is adding -u daemon to the start-stop-daemon call on line 63.

Bye,

Joerg



signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 0.2a-6+rm

Dear submitter,

as the package bindgraph has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1026360

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#806946: marked as done (bindgraph doesn't show any graphic)

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 23:32:09 +
with message-id 
and subject line Bug#1026360: Removed package(s) from unstable
has caused the Debian Bug report #806946,
regarding bindgraph doesn't show any graphic
to be marked as done.

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

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


-- 
806946: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806946
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bindgraph
Version: 0.2a-5.1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I have installed bindgraph and modified /etc/bind/named.conf.options but when 
consulting http://myserver/cgi-bin/bindgraph.cgi there isn't any graphic.
the source of the webpage contains pictures which doesn't exist :


Day Graph

Week Graph

Month Graph

Year Graph



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

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

Versions of packages bindgraph depends on:
ii  debconf [debconf-2.0]  1.5.56
ii  libfile-tail-perl  0.99.3-5
ii  librrds-perl   1.4.8-1.2

Versions of packages bindgraph recommends:
ii  apache2 [httpd]  2.4.10-10+deb8u3
ii  bind91:9.9.5.dfsg-9+deb8u3

bindgraph suggests no packages.

-- Configuration Files:
/etc/init.d/bindgraph changed:
CONFIG=/etc/default/bindgraph
DNS_LOG=/var/log/bind9-query.log
NAME=bindgraph
DESC="DNS Statistics"
DAEMON=/usr/sbin/bindgraph.pl
PIDFILE=/var/run/servergraph/bindgraph.pid
CACHEDIR=/var/cache/bindgraph
RRD_DIR=/var/lib/bindgraph
RRD_NAME=bindgraph
test -x $DAEMON || exit 0
if [ -f $CONFIG ]; then
. $CONFIG
fi
pid_dir=`dirname $PIDFILE`
test -d $pid_dir || mkdir -p $pid_dir
chown daemon:root $pid_dir
. /lib/lsb/init-functions
if [ -n "$LOG_FORMAT" ]; then
FORMAT="--format=${LOG_FORMAT}"
fi
case "$1" in
  start)
log_daemon_msg "Starting $DESC" "$DAEMON"
if start-stop-daemon --start --quiet --exec $DAEMON -N 15 -c daemon:adm 
-- \
-l $DNS_LOG $FORMAT -d --daemon_rrd=$RRD_DIR 
--rrd_name=$RRD_NAME $ARGS ;
then
log_end_msg 0
else
log_end_msg $?
fi
  ;;
  stop)
log_daemon_msg "Stopping $DESC: " "$DAEMON"
start-stop-daemon --stop --oknodo --pidfile $PIDFILE -c daemon:adm ;
st=$?
rm -f $PIDFILE
log_end_msg $st
  ;;
  restart|force-reload)
$0 stop
sleep 1
$0 start
  ;;
  status)
if pidofproc -p $PIDFILE $DAEMON ; then
log_success_msg "$DAEMON is running"
exit 0
else
log_success_msg "$DAEMON is not running"
exit 3
fi  
  ;;
  *)
log_success_msg "Usage: $0 start|stop|restart|force-reload|status"
exit 0
;;
esac
exit 0


-- debconf information:
* bindgraph/start_on_boot: true
* bindgraph/stay_on_purge: true
* bindgraph/logfile: /var/log/bind9-query.log
--- End Message ---
--- Begin Message ---
Version: 0.2a-6+rm

Dear submitter,

as the package bindgraph has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1026360

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1013021: marked as done (qscintilla2: ftbfs with GCC-12)

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 23:09:54 +
with message-id 
and subject line Bug#1013021: fixed in qscintilla2 2.13.3+dfsg-1
has caused the Debian Bug report #1013021,
regarding qscintilla2: ftbfs with GCC-12
to be marked as done.

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

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


-- 
1013021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013021
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:qscintilla2
Version: 2.11.6+dfsg-4
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-12

[This bug is targeted to the upcoming bookworm release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-12/g++-12, but succeeds to build with gcc-11/g++-11. The
severity of this report will be raised before the bookworm release.

The full build log can be found at:
http://qa-logs.debian.net/2022/06/09/gcc12/qscintilla2_2.11.6+dfsg-4_unstable_gcc12.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
  
(optional=templinst)_ZSt13binary_searchIN9__gnu_cxx17__normal_iteratorIPKcSt6vectorIcSaIccEbT_S8_RKT0_@Base
 2.11.2
  
(optional=templinst)_ZSt13binary_searchIN9__gnu_cxx17__normal_iteratorIPKwSt6vectorIwSaIwwEbT_S8_RKT0_@Base
 2.11.2
- 
(optional=templinst)_ZSt14__partial_sortIN9__gnu_cxx17__normal_iteratorIPiSt6vectorIiSaIiNS0_5__ops15_Iter_comp_iterI6SorterEEEvT_SB_SB_T0_@Base
 2.11.5
+#MISSING: 2.11.6+dfsg-4# 
(optional=templinst)_ZSt14__partial_sortIN9__gnu_cxx17__normal_iteratorIPiSt6vectorIiSaIiNS0_5__ops15_Iter_comp_iterI6SorterEEEvT_SB_SB_T0_@Base
 2.11.5
+ 
_ZSt16__do_uninit_copyIN9__gnu_cxx17__normal_iteratorIPKN9Scintilla11SparseStateINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIc5StateESt6vectorISB_SaISB_PSB_ET0_T_SK_SJ_@Base
 2.11.6+dfsg-4
  
(optional=templinst)_ZSt16__insertion_sortIN9__gnu_cxx17__normal_iteratorIPiSt6vectorIiSaIiNS0_5__ops15_Iter_comp_iterI6SorterEEEvT_SB_T0_@Base
 2.11.2
  
(optional=templinst|subst)_ZSt16__introsort_loopIN9__gnu_cxx17__normal_iteratorIPiSt6vectorIiSaIi{ssize_t}NS0_5__ops15_Iter_comp_iterI6SorterEEEvT_SB_T0_T1_@Base
 2.11.2
  _ZSt19__throw_regex_errorNSt15regex_constants10error_typeEPKc@Base 2.11.2
  
(optional=templinst)_ZSt22__final_insertion_sortIN9__gnu_cxx17__normal_iteratorIPiSt6vectorIiSaIiNS0_5__ops15_Iter_comp_iterI6SorterEEEvT_SB_T0_@Base
 2.11.2
- 
(optional=templinst)_ZSt22__move_median_to_firstIN9__gnu_cxx17__normal_iteratorIPiSt6vectorIiSaIiNS0_5__ops15_Iter_comp_iterI6SorterEEEvT_SB_SB_SB_T0_@Base
 2.11.5
+#MISSING: 2.11.6+dfsg-4# 
(optional=templinst)_ZSt22__move_median_to_firstIN9__gnu_cxx17__normal_iteratorIPiSt6vectorIiSaIiNS0_5__ops15_Iter_comp_iterI6SorterEEEvT_SB_SB_SB_T0_@Base
 2.11.5
+ 
_ZSt27__unguarded_partition_pivotIN9__gnu_cxx17__normal_iteratorIPiSt6vectorIiSaIiNS0_5__ops15_Iter_comp_iterI6SorterEEET_SB_SB_T0_@Base
 2.11.6+dfsg-4
+ 
_ZSt4findIN9__gnu_cxx17__normal_iteratorIPKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt6vectorIS7_SaIS7_S7_ET_SE_SE_RKT0_@Base
 2.11.6+dfsg-4
+ 
_ZSt4findIN9__gnu_cxx17__normal_iteratorIPKNSt7__cxx1112basic_stringIwSt11char_traitsIwESaIwEEESt6vectorIS7_SaIS7_S7_ET_SE_SE_RKT0_@Base
 2.11.6+dfsg-4
  
(optional=templinst)_ZSt4sortIN9__gnu_cxx17__normal_iteratorIPiSt6vectorIiSaIi6SorterEvT_S8_T0_@Base
 2.11.5
  _ZTI10LexerBasic@Base 2.11.2
  _ZTI10LexerLaTeX@Base 2.11.2
@@ -4399,9 +4432,11 @@
  (arch=!armel 
!riscv64)_ZTISt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE2EE@Base 2.11.2
  (arch=armel armhf)_ZTISt19_Sp_make_shared_tag@Base 2.11.5
  (arch=armel 

Bug#1026297: marked as done (unifrac-tools: Frequent parallel FTBFS)

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 22:22:01 +
with message-id 
and subject line Bug#1026297: fixed in unifrac-tools 1.1.3-2
has caused the Debian Bug report #1026297,
regarding unifrac-tools: Frequent parallel FTBFS
to be marked as done.

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

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


-- 
1026297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026297
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: unifrac-tools
Version: 1.1.3-1
Severity: serious
Tags: ftbfs patch
Control: block 1021542 by -1

https://tests.reproducible-builds.org/debian/history/unifrac-tools.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/armhf/unifrac-tools.html
https://buildd.debian.org/status/logs.php?pkg=unifrac-tools=arm64

...
make[3]: Entering directory '/<>/src'
make[3]: warning: jobserver unavailable: using -j1.  Add '+' to parent make 
rule.
make[3]: Entering directory '/<>/src'
make[3]: warning: jobserver unavailable: using -j1.  Add '+' to parent make 
rule.
make[3]: Entering directory '/<>/src'
make[3]: warning: jobserver unavailable: using -j1.  Add '+' to parent make 
rule.
...
h5c++ -Wdate-time -D_FORTIFY_SOURCE=2 -fopenmp -Wextra -Wno-unused-parameter 
-Wall  -std=c++14 -pedantic -I. -O4 -fPIC -L/<>/debian/tmp/usr/lib 
 faithpd.cpp -o faithpd tree.o biom.o unifrac_internal.o unifrac_cmp_cpu.o 
unifrac.o cmd.o skbio_alt.o api.o -lhdf5_cpp -llz4 -llapacke -lblas -lpthread
h5c++ -Wdate-time -D_FORTIFY_SOURCE=2 -fopenmp -Wextra -Wno-unused-parameter 
-Wall  -std=c++14 -pedantic -I. -O4 -fPIC -L/<>/debian/tmp/usr/lib 
 faithpd.cpp -o faithpd tree.o biom.o unifrac_internal.o unifrac_cmp_cpu.o 
unifrac.o cmd.o skbio_alt.o api.o -lhdf5_cpp -llz4 -llapacke -lblas -lpthread
/usr/bin/ld: 
/usr/lib/gcc/aarch64-linux-gnu/12/../../../aarch64-linux-gnu/Scrt1.o: in 
function `_start':
(.text+0x1c): undefined reference to `main'
/usr/bin/ld: (.text+0x20): undefined reference to `main'
collect2: error: ld returned 1 exit status
make[3]: *** [Makefile:108: faithpd] Error 1


The problem is the toplevel Makefile calling make in src/ up to three
times in parallel during the build.

The easiest workaround is:

--- debian/rules.old2022-12-17 22:53:06.643268060 +
+++ debian/rules2022-12-17 22:53:11.403264194 +
@@ -7,7 +7,7 @@
 export DEB_BUILD_MAINT_OPTIONS=hardening=+all
 
 %:
-   dh $@
+   dh $@ --no-parallel
 
 override_dh_auto_build:
mkdir -p $(CURDIR)/debian/tmp/usr/bin
--- End Message ---
--- Begin Message ---
Source: unifrac-tools
Source-Version: 1.1.3-2
Done: Nilesh Patra 

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

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

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

Debian distribution maintenance software
pp.
Nilesh Patra  (supplier of updated unifrac-tools package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 18 Dec 2022 20:48:16 +0530
Source: unifrac-tools
Architecture: source
Version: 1.1.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Nilesh Patra 
Closes: 1026297
Changes:
 unifrac-tools (1.1.3-2) unstable; urgency=medium
 .
   * Team Upload.
   * Do not build unifrac-tools in parallel (Closes: #1026297)
Checksums-Sha1:
 4cda4c6c415bd6ce0abb5b83a0c278c988d0707d 1650 unifrac-tools_1.1.3-2.dsc
 b7fff5cf2e3abf1496eb658ce60ce129b0958f6c 7332 
unifrac-tools_1.1.3-2.debian.tar.xz
 666c5616f8645f21ee24f6fcda57a0949d885494 8043 
unifrac-tools_1.1.3-2_amd64.buildinfo
Checksums-Sha256:
 a6a6eae982d20cedb7170b880a818c3814f85f4f3821639c5e3fa53d71eae541 1650 
unifrac-tools_1.1.3-2.dsc
 91555c43d7bfd15997fd28ecb6c498b71db572c5cf2dae4b8d24c6267c3e98cf 7332 
unifrac-tools_1.1.3-2.debian.tar.xz
 a8087fd12d90e945f762de96645af9312a5784b3cf978d15d233cb88dcdc9605 8043 
unifrac-tools_1.1.3-2_amd64.buildinfo
Files:
 c3598201d988a4b19952ed3a0e484022 1650 science optional 
unifrac-tools_1.1.3-2.dsc
 26fdc3fd6fa52d43ce617281ea391e9f 7332 science optional 
unifrac-tools_1.1.3-2.debian.tar.xz
 deaa7681ca7e832257ccfeba4f963f9b 8043 science optional 
unifrac-tools_1.1.3-2_amd64.buildinfo

-BEGIN PGP 

Bug#1015123: latex-cjk-chinese-arphic: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity

[Hilmar Preuße]

Am 27.07.2022 um 12:10 teilte Danai SAE-HAN (韓達耐) mit:

Hi Danai,

is there progress? Did you get response from upstream?

Hilmar


Some observations:

Going back to fontforge version 20201107~dfsg-4 and its dependencies, I
notice the following warning message:

21900/1114292:
   Add extrema...
   Simplifying outlines...
NaN value in spline creationNaN value in spline creationNaN value in spline
creationNaN value in spline creationNaN value in spline creationNaN value
in spline creationNaN value in spline creationNaN value in spline
creationNaN value in spline creationNaN value in spline creationNaN value
in spline creationNaN value in spline creationNaN value in spline
creationNaN value in spline creationNaN value in spline creationNaN value
in spline creationNaN value in spline creationNaN value in spline
creationNaN value in spline creationNaN value in spline creationNaN value
in spline creationNaN value in spline creationNaN value in spline
creationNaN value in spline creationNaN value in spline creationNaN value
in spline creationNaN value in spline creationNaN value in spline
creationNaN value in spline creationNaN value in spline creationNaN value
in spline creationNaN value in spline creationNaN value in spline
creationNaN value in spline creationNaN value in spline creationNaN value
in spline creationNaN value in spline creationNaN value in spline
creationNaN value in spline creationNaN value in spline creationNaN value
in spline creation22000/1114292:

   Add extrema...
   Simplifying outlines...

A more recent version of Fontforge will just let the application hang.

I will have to contact upstream to figure out what is causing this.




--
sigfault

Bug#1026057: marked as done (swi-prolog: autopkgtest regression on armel armhf and i386: Segmentation fault)

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 22:20:24 +
with message-id 
and subject line Bug#1026057: fixed in swi-prolog 9.0.3+dfsg-1
has caused the Debian Bug report #1026057,
regarding swi-prolog: autopkgtest regression on armel armhf and i386: 
Segmentation fault
to be marked as done.

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

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


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

Source: swi-prolog
Version: 9.0.2+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent upload of swi-prolog the autopkgtest of swi-prolog fails 
in testing when that autopkgtest is run with the binary packages of 
swi-prolog from unstable on armel, armhf and i386. It passes when run 
with only packages from testing. In tabular form:


   passfail
swi-prolog from testing9.0.2+dfsg-1
all others from testingfrom testing

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

Currently this regression is blocking the migration to testing [1]. Can 
you please investigate the situation and fix it?


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=swi-prolog

https://ci.debian.net/data/autopkgtest/testing/armel/s/swi-prolog/29272723/log.gz

% Checking your SWI-Prolog kit for common issues ...
% % Version: . 9.0.2
% Address bits:  32
% Architecture:  armv7l-linux
% Installed at:  /usr/lib/swi-prolog
% Cores: ... 16
% % Checking tcmalloc  ok
% Checking gmp . ok
% Loading library(archive) . ok
%   Supported filters: bzip2, compress, gzip, grzip, lrzip, lzip, lzma, 
lzop, none, rpm, uu, xz
%   Supported formats: 7zip, ar, cab, cpio, empty, gnutar, iso9660, lha, 
mtree, rar, raw, tar, xar, zip

% Loading library(cgi) . ok
% Loading library(crypt) ... ok
% Loading library(bdb) . ok
% Loading library(double_metaphone)  ok
% Loading library(filesex) . ok
% Loading library(http/http_stream)  ok
% Loading library(http/json) ... ok
% Loading library(http/jquery) . ok
Warning:   Cannot find jQuery (jquery.min.js)
% Loading library(isub)  ok
% Loading library(jpl) . ok
% Loading library(memfile) . ok
% Loading library(odbc)  ok
% Loading library(pce) . ok
% Loading library(pcre)  ok
% Loading library(pdt_console) . ok
% Loading library(porter_stem) . ok
% Loading library(process) . ok
% Loading library(protobufs) ... ok
% Loading library(editline)  ok
% Loading library(readline)  ok
% Loading library(readutil)  ok
% Loading library(rlimit) .. ok
% Loading library(semweb/rdf_db) ... ok
% Loading library(semweb/rdf_ntriples) . ok
% Loading library(semweb/turtle) ... ok
% Loading library(sgml)  ok
% Loading library(sha) . ok
% Loading library(snowball)  ok
% Loading library(socket) .. ok
% Loading library(ssl) . ok
Warning: library(sweep_link) ... NOT FOUND
Warning: See http://www.swi-prolog.org/build/issues/sweep_link.html
% Loading library(crypto) .. ok
% Loading library(syslog) .. ok
% Loading library(table) ... ok
% Loading library(time)  ok
% Loading library(tipc/tipc) ... ok
% Loading library(unicode) . ok
% Loading library(uri) . ok
% Loading library(uuid)  ok
% Loading library(zlib)  ok
% Loading library(yaml)  ok
Warning: Found 1 issues.
% SWI-Prolog test suite.
% To run all tests run ?- test.
% Running test set "syntax" ... done.
Running test set "write_test" .. done.
Running test set "format_test" . done.
Running test set "unify" .. 

Bug#1026387: marked as done (samba-ad-provision: missing Breaks+Replaces: samba (<< 2:4.17.3+dfsg-4))

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 22:15:30 +
with message-id 
and subject line Bug#1026387: fixed in samba 2:4.17.4+dfsg-2
has caused the Debian Bug report #1026387,
regarding samba-ad-provision: missing Breaks+Replaces: samba (<< 
2:4.17.3+dfsg-4)
to be marked as done.

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

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


-- 
1026387: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026387
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: samba-ad-provision
Version: 2:4.17.3+dfsg-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

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

  Preparing to unpack .../samba-ad-provision_2%3a4.17.4+dfsg-1_all.deb ...
  Unpacking samba-ad-provision (2:4.17.4+dfsg-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/samba-ad-provision_2%3a4.17.4+dfsg-1_all.deb (--unpack):
   trying to overwrite 
'/usr/share/samba/setup/ad-schema/AD_DS_Attributes__Windows_Server_2012_R2.ldf',
 which is also in package samba 2:4.17.3+dfsg-3
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/samba-ad-provision_2%3a4.17.4+dfsg-1_all.deb


cheers,

Andreas


samba=2:4.17.3+dfsg-3_samba-ad-provision=2:4.17.4+dfsg-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: samba
Source-Version: 2:4.17.4+dfsg-2
Done: Michael Tokarev 

We believe that the bug you reported is fixed in the latest version of
samba, which is due to be installed in the Debian FTP archive.

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

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

Debian distribution maintenance software
pp.
Michael Tokarev  (supplier of updated samba package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 19 Dec 2022 16:36:00 +0300
Source: samba
Architecture: source
Version: 2:4.17.4+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Samba Maintainers 
Changed-By: Michael Tokarev 
Closes: 1026387
Changes:
 samba (2:4.17.4+dfsg-2) unstable; urgency=medium
 .
   * d/control: samba-dc-provision Replaces+Breaks samba (< 4.17.4+dfsg-2).
 Closes: #1026387
Checksums-Sha1:
 4c64e5aeb35ec086f71b41049a2152ec3aaa2dad 4386 samba_4.17.4+dfsg-2.dsc
 6ca7e5843e4568a51d5ad649787f5e8020dbb43e 267200 
samba_4.17.4+dfsg-2.debian.tar.xz
 e059f73416c4094e9211e788608b18127e47ffea 5983 
samba_4.17.4+dfsg-2_source.buildinfo
Checksums-Sha256:
 3f02b78c248855ecd1153bf4536ae352dca3a2ea2ec9f5e138b88f6868ed6ec4 4386 
samba_4.17.4+dfsg-2.dsc
 9b7c7a74b131c63a3e0e58661adf0e940f0051ea59f5e0556341d10080f29199 267200 
samba_4.17.4+dfsg-2.debian.tar.xz
 dff2e49a6002bf4aa5f123d691d9335994a0e17d6aca5a63271b605b824f26d0 5983 
samba_4.17.4+dfsg-2_source.buildinfo
Files:
 03fcb069b2081a4e37d8c48ec410 4386 net optional samba_4.17.4+dfsg-2.dsc
 d2693f60a28c8b7b1a9b52010591954e 267200 net optional 
samba_4.17.4+dfsg-2.debian.tar.xz
 ffbfd2e97c1e90ec6a182f073862e192 5983 net optional 
samba_4.17.4+dfsg-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFDBAEBCAAtFiEEe3O61ovnosKJMUsicBtPaxppPlkFAmOgaWAPHG1qdEB0bHMu
bXNrLnJ1AAoJEHAbT2saaT5ZgEkH/0paiJB+f8T/FZ69UWmFUXw2ajHzqxxiHfIy
2iAM4x+guKHwbdDpeMlxwlgmf3AEgiMDoVhtkJ0hyDf2CYqEFIVqqFKlOEA+jE93
nlmy6FeoW0vQE37CMXN/1mv9+r8TtfjoTAPjxZqv3VmLR2Y6hodKXBcTRXllbDuT
oMmWtTnqwbu20iyUPxPoyA37/gJMiLZygqHffZrg7mNqiECy9JfufTfB5RujEH8Y
1grtMpgQKt1lcPnE7pylKadXv00GRcESJrkpqiEkspNKkOst+TvTNgAhpTSTy02G
snK+Ntp18B6LFE1q6UIJERLFN1Rh7FPqRELdXOP5qY5fd0tYssY=
=WUbB
-END PGP SIGNATURE End Message ---

Bug#1026349: marked as done (sasview: autopkgtest needs update for new version of numpy: module 'numpy' has no attribute 'asscalar')

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 22:15:47 +
with message-id 
and subject line Bug#1026349: fixed in sasview 5.0.5-4
has caused the Debian Bug report #1026349,
regarding sasview: autopkgtest needs update for new version of numpy: module 
'numpy' has no attribute 'asscalar'
to be marked as done.

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

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


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

Source: sasview
Version: 5.0.5-3
Severity: serious
X-Debbugs-CC: nu...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:numpy

Dear maintainer(s),

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


   passfail
numpy  from testing1:1.23.5-2
sasviewfrom testing5.0.5-3
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 numpy to testing 
[1]. Of course, numpy shouldn't just break your autopkgtest (or even 
worse, your package), but it seems to me that the change in numpy 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 numpy 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=numpy

https://ci.debian.net/data/autopkgtest/testing/amd64/s/sasview/29465796/log.gz

=== FAILURES 
===
__ TestBasicComponent.test_iq 
__


self = testMethod=test_iq>


def test_iq(self):
"""
Test iq calculation
"""
q = 0.11
v1 = 8.0*math.pi**2/q * self.invertor.d_max 
*math.sin(q*self.invertor.d_max)

v1 /= ( math.pi**2 - (q*self.invertor.d_max)**2.0 )
pars = numpy.ones(1)

  self.assertAlmostEqual(self.invertor.iq(pars, q), v1, 2)


test/pr_inversion/utest_invertor.py:171: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/lib/python3/dist-packages/sas/sascalc/pr/invertor.py:315: in iq

return Pinvertor.iq(self, out, q) + self.background
/usr/lib/python3/dist-packages/sas/sascalc/pr/p_invertor.py:339: in iq
return np.asscalar(iq_val)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _

attr = 'asscalar'

def __getattr__(attr):
# Warn for expired attributes, and return a dummy function
# that always raises an exception.
try:
msg = __expired_functions__[attr]
except KeyError:
pass
else:
warnings.warn(msg, DeprecationWarning, stacklevel=2)
def _expired(*args, **kwds):
raise RuntimeError(msg)
return _expired
# Emit warnings for deprecated attributes
try:
val, msg = __deprecated_attrs__[attr]
except KeyError:
pass
else:
warnings.warn(msg, DeprecationWarning, stacklevel=2)
return val
# Importing Tester requires importing all of UnitTest which 
is not a
# cheap import Since it is mainly used in test suits, we lazy 
import it

# here to save on the order of 10 ms of import time for most users
#
# The previous way Tester was imported also had a side effect 
of adding

# the full `numpy.testing` namespace
if attr == 'testing':
import numpy.testing as testing
return testing
elif attr == 'Tester':
from .testing import Tester
return Tester
>   raise AttributeError("module {!r} has no attribute "
 "{!r}".format(__name__, attr))
E   AttributeError: module 'numpy' has no attribute 'asscalar'

Bug#1024882: marked as done (scm: FTBFS on armel, armhf and mipsel)

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 22:15:57 +
with message-id 
and subject line Bug#1024882: fixed in scm 5f3-2
has caused the Debian Bug report #1024882,
regarding scm: FTBFS on armel, armhf and mipsel
to be marked as done.

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

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


-- 
1024882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024882
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: scm
Version: 5f3-1+b1
Severity: serious
Tags: ftbfs, patch
Justification: fails to build from source (but built successfully in the past)

There is a build failure affecting scm on armel, armhf and mipsel:

| ;ERROR: "r4rstest.scm": integer-length: Wrong type in arg1 (0 . 0)
| ; in expression: (#@string->number (#@number->string #@number))
| ; in scope:
| ;   (number)  procedure testit
| ;   (testit . #@define)
| ;   (x)  procedure float-print-test
| ;   (log2 slow-frexp float-precision float-print-test mult-float-print-test 
float-rw-range-test float-powers-of-2-test . #@define)
| ;   (f0.0 f0.5 f1.0 f2.0 . #@let)
| ;   ()  procedure test-inexact-printing
| ; defined by load: "r4rstest.scm"
| 
| ;STACK TRACE
| 1; ((#@eqv? #@number (#@string->number (#@number->string #@number ...
| 2; (#@let* ((xx (#@+ #@x (#@* #@j #@eps))) (ok? (#@testit #@xx))) ...
| 3; (#@do ((j -100 (#@+ #@j 1))) ((#@or (#@not #@all-ok?) (#@> #@j ...
| 4; (#@define ((log2 (#@let ((l2 (#@log 2)))  (#@lambda (x) (/ (lo ...
| 5; (#@let ((have-inexacts? (#@and (#@string->number "0.0") (#@ine ...
| ...
| 
| ; program args: ("./scm" "-fr4rstest.scm" 
"-e(test-sc4)(test-cont)(test-delay)(gc)" "-e" "(or (null? errs) (quit 1))")
| make[1]: *** [Makefile:559: check] Error 1



I've tried to debug it and it's some sort of Heisenbug. The bug is
triggered by the buildds because they run with stdout redirected to a
file and stdin redirected from /dev/null. I think that this changes
the allocation patterns of the program slightly and exposes the bug.

There is a recent change in scm that adds the bigrec() function for
recycling bignums, i.e. freeing them without waiting for the gc to do
it. I believe that some use of this function is the source of the bug.
Note that the assertion error says "Wrong type in arg1 (0 . 0)", which
is the object after bigrecy() has modified it. I tried changing
"CAR(bgnm) = INUM0;" to "CAR(bgnm) = MAKINUM(42);" and the error then
changed to "Wrong type in arg1 (42 . 0)", which suggests that
bigrecy() was run on a reachable bignum.

I haven't managed to figure out exactly which call to bigrecy() is
causing the problem, so here's a patch to just disable it altogether.
The bigrecy() function is a performance hack, so disabling it
shouldn't cause any problems.


diff --git a/scl.c b/scl.c
index a572557..8d8026c 100644
--- a/scl.c
+++ b/scl.c
@@ -133,12 +133,14 @@ void strrecy(str)
 void bigrecy(bgnm)
  SCM bgnm;
 {
+#if 0
   if (IMP(bgnm) || !BIGP(bgnm)) return;
   DEFER_INTS;
   must_free(CHARS(bgnm), (sizet)NUMDIGS(bgnm)*sizeof(BIGDIG));
   CAR(bgnm) = INUM0;
   CDR(bgnm) = INUM0;
   ALLOW_INTS;
+#endif
 }
 
 /* can convert to string accurately with bignums */
--- End Message ---
--- Begin Message ---
Source: scm
Source-Version: 5f3-2
Done: Göran Weinholt 

We believe that the bug you reported is fixed in the latest version of
scm, which is due to be installed in the Debian FTP archive.

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

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

Debian distribution maintenance software
pp.
Göran Weinholt  (supplier of updated scm package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 18 Dec 2022 14:15:57 +0100
Source: scm
Architecture: source
Version: 5f3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Scheme Dream Team 
Changed-By: Göran Weinholt 
Closes: 1024882
Changes:
 scm (5f3-2) unstable; urgency=medium
 .
   Team upload.
 .
   [ Göran Weinholt ]
   * use-compiler-flags.patch: Pass through compilation flags to gcc
   * debian/patches/disable-bigrecy.patch: Disable bigrecy() again
 (Closes: #1024882)
   * debian/rules: Disable C optimizations to work around a test failure
   * debian/control: 

Bug#1026107: marked as done (ruby-asciidoctor-pdf: depends on deprecated ruby-safe-yaml)

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 22:12:55 +
with message-id 
and subject line Bug#1026107: fixed in ruby-asciidoctor-pdf 2.3.4-2
has caused the Debian Bug report #1026107,
regarding ruby-asciidoctor-pdf: depends on deprecated ruby-safe-yaml
to be marked as done.

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

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


-- 
1026107: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026107
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-asciidoctor-pdf
Version: 1.6.2-1
Severity: serious
Tags: upstream
User: debian-r...@lists.debian.org
Usertags: ruby3.1

Dear Maintainer,

Working to get ruby3.1 as the default Ruby version it was noticed that
ruby-safe-yaml is incompatible with ruby3.1 and thus deprecated. Most
upstreams have dropped their dependencies on it; I checked and that is
also the case for asciidoctor-pdf: v2.3.4 no longer depends on
safe_yaml.

ruby-safe-yaml will soon be removed from testing due to this,
ruby-asciidoctor-pdf needs to drop its dependency on it.

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

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

Versions of packages ruby-asciidoctor-pdf depends on:
ii  ruby  1:3.1~1
ii  ruby-asciidoctor  2.0.17-1
ii  ruby-concurrent   1.1.6+dfsg-5
pn  ruby-prawn
pn  ruby-prawn-icon   
pn  ruby-prawn-svg
pn  ruby-prawn-table  
ii  ruby-safe-yaml1.0.5-2
pn  ruby-treetop  

ruby-asciidoctor-pdf recommends no packages.

Versions of packages ruby-asciidoctor-pdf suggests:
ii  ruby-rouge  3.30.0-2


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby-asciidoctor-pdf
Source-Version: 2.3.4-2
Done: Lucas Kanashiro 

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

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

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

Debian distribution maintenance software
pp.
Lucas Kanashiro  (supplier of updated 
ruby-asciidoctor-pdf package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 19 Dec 2022 16:47:34 -0300
Source: ruby-asciidoctor-pdf
Architecture: source
Version: 2.3.4-2
Distribution: unstable
Urgency: medium
Maintainer: Keith Packard 
Changed-By: Lucas Kanashiro 
Closes: 1026107
Changes:
 ruby-asciidoctor-pdf (2.3.4-2) unstable; urgency=medium
 .
   * d/control: do not depend on ruby-safe-yaml (Closes: #1026107).
Checksums-Sha1:
 811baa869b96e75fda3d0922cd604040dfed5cb4 2305 ruby-asciidoctor-pdf_2.3.4-2.dsc
 76f0746b7a3053e9039ad3c44d77e9d26e960441 8000 
ruby-asciidoctor-pdf_2.3.4-2.debian.tar.xz
Checksums-Sha256:
 a443a86ed84ecf76fd74cb2202271199d2661afe88133d69c37c4174322f6561 2305 
ruby-asciidoctor-pdf_2.3.4-2.dsc
 23067c380c56b7d02890a261cde57389280fa14f04ea911f21c8926272ea8664 8000 
ruby-asciidoctor-pdf_2.3.4-2.debian.tar.xz
Files:
 44feb75d8f082bd2634fb93bf45bc0e1 2305 ruby optional 
ruby-asciidoctor-pdf_2.3.4-2.dsc
 1f644f353d0ae6d7c2672f2b21354891 8000 ruby optional 
ruby-asciidoctor-pdf_2.3.4-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEjtbD+LrJ23/BMKhw+COicpiDyXwFAmOgwIMVHGthbmFzaGly
b0BkZWJpYW4ub3JnAAoJEPgjonKYg8l8JDcP/A/E8Ssirk9LCkdT7w+zaVFBsfBq
zwH8ijQj/SEY6E9OpPhRMp9LZf/vLzW9yd5KfsClMM0zR++n3cnRhk76BwvsoH9K
wFdfJCRdKe5i1ENiBOKnwGvAFCJizflEOtQ70KxSn/kjJYSC9qHxFzcG7mpKQoLR
0CNPFQF7TyagMhVYSmHmPx7uXNPLMzQQIfsR9JIW9kDbytEGIx1gKq+ojLnwmgwN
tXQ/xZkmPgVevMt6ZmMmJysjODHyjERJAAfcgd84ZcZpjwMtbCV6cxqsihxLXGcX
4JIQhINOT7Z+NM2p/kezQAqR6awq42sFgIjzV0auFWXK/Am1eYDaT1ZarsTqFcjS
PSc/NPGiXF1rw+BGCcsjgmC2eD3OdqAkkSn4CGye63IJzqvc0tDeArhywfaNAaMe
lPiJriWSkCWyOr94JeN+vWkp9Nr8/iK82T5LnpopazH/DrnBpgkal5conpoJEb7U
2d+ty0VxJ/bVsBWCIpi90/CV5Q+dvt+8dqKlhf/Q4/fx+J4Hp4e0iJRdJCAPWHpK

Bug#1026326: marked as done (procps breaks pslist autopkgtest)

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 21:29:38 +
with message-id 
and subject line Bug#1026326: fixed in procps 2:4.0.2-3
has caused the Debian Bug report #1026326,
regarding procps breaks pslist autopkgtest
to be marked as done.

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

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


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

Source: procps, pslist
Control: found -1 procps/2:4.0.2-2
Control: found -1 pslist/1.4.0-4
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

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


   passfail
procps from testing2:4.0.2-2
pslist from testing1.4.0-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 procps to testing 
[1]. Due to the nature of this issue, I filed this bug report against 
both packages. Can you please investigate the situation and reassign the 
bug to the right package?


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=procps

https://ci.debian.net/data/autopkgtest/testing/amd64/p/pslist/29462267/log.gz


#   Failed test 'run the test tool succeeded'
#   at t/lib/Test/PSList.pm line 64.
#  got: 255
# expected: 0

#   Failed test 'run the test tool did not output any errors'
#   at t/lib/Test/PSList.pm line 65.
#  got: 'Parent: pslist did not return information about some 
children: 793 794 795 796 797 798

# '
# expected: ''
# Looks like you failed 2 tests of 2.
t/01-test-tool.t .. 1..2
not ok 1 - run the test tool succeeded
not ok 2 - run the test tool did not output any errors
Dubious, test returned 2 (wstat 512, 0x200)
Failed 2/2 subtests t/02-feature-check.t .. 1..3
# Subtest: Check for the pslist feature
1..2
ok 1 - check for the "pslist" feature succeeded
ok 2 - check for the "pslist" feature did not output any errors
ok 1 - Check for the pslist feature
# Subtest: pslist feature version >= 1
1..2
ok 1 - the "pslist" feature >= 1 succeeded
ok 2 - the "pslist" feature >= 1 did not output any errors
ok 2 - pslist feature version >= 1
# Subtest: pslist feature version < 1000
1..2
ok 1 - the "pslist" feature < 1000 succeeded
ok 2 - the "pslist" feature < 1000 did not output any errors
ok 3 - pslist feature version < 1000
ok

Test Summary Report
---
t/01-test-tool.t(Wstat: 512 (exited 2) Tests: 2 Failed: 2)
  Failed tests:  1-2
  Non-zero exit status: 2
Files=2, Tests=5,  0 wallclock secs ( 0.01 usr  0.01 sys +  0.24 cusr 
0.02 csys =  0.28 CPU)

Result: FAIL
autopkgtest [05:15:26]: test upstream



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: procps
Source-Version: 2:4.0.2-3
Done: Craig Small 

We believe that the bug you reported is fixed in the latest version of
procps, which is due to be installed in the Debian FTP archive.

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

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

Debian distribution maintenance software
pp.
Craig Small  (supplier of updated procps package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 19 Dec 2022 17:06:38 +1100
Source: procps
Architecture: source
Version: 2:4.0.2-3
Distribution: unstable
Urgency: medium
Maintainer: Craig Small 
Changed-By: Craig Small 
Closes: 192635 1025915 1026326
Changes:
 procps (2:4.0.2-3) unstable; urgency=medium
 .
   [ Pino Toscano ]
   * Drop the Debian menu file: (Closes: #192635)
 - the Debian menu is deprecated for some years already
 - the menu item does not have an icon
 - the menu item is for a terminal, and generally GUI environments have 
their
 

Bug#1024835: marked as done (python-pauvre: ftbfs with biopython 1.80)

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 21:31:47 +
with message-id 
and subject line Bug#1024835: fixed in python-pauvre 0.2.3-2
has caused the Debian Bug report #1024835,
regarding python-pauvre: ftbfs with biopython 1.80
to be marked as done.

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

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


-- 
1024835: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024835
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pauvre
Version: 0.2.3-1
Severity: important
Tags: ftbfs

Dear Maintainer,

python-pauvre fails its build time test suite when built against
biopython 1.80 in experimental but builds successfully against
biopython 1.79.  The relevant part of the log in case of failure
shows:

I: pybuild base:240: cd 
/<>/.pybuild/cpython3_3.10_pauvre/build; python3.10 -m unittest 
discover -v 
test_normal_plotting_scenario 
(pauvre.tests.test_synplot.libSeq_test_case)
This verifies that the LibSeq class is constructed with all of the ... 
+ export PYTHONPATH=/<>/.pybuild/cpython3_3.10_pauvre/build
+ PYTHONPATH=/<>/.pybuild/cpython3_3.10_pauvre/build
+ exec python3 
/<>/.pybuild/cpython3_3.10_pauvre/build/pauvre/pauvre_main.py 
synplot --aln_dir 
/<>/.pybuild/cpython3_3.10_pauvre/build/pauvre/tests/testdata/alignments/
 --fileform pdf --gff_paths 
/<>/.pybuild/cpython3_3.10_pauvre/build/pauvre/tests/testdata/gff_files/Bf201706.gff
 
/<>/.pybuild/cpython3_3.10_pauvre/build/pauvre/tests/testdata/gff_files/JN392469.gff
 
/<>/.pybuild/cpython3_3.10_pauvre/build/pauvre/tests/testdata/gff_files/NC016117.gff
 --center_on COX1 --gff_labels 'B. forskalii' 'P. bachei' 'M. leidyi'
Traceback (most recent call last):
  File 
"/<>/.pybuild/cpython3_3.10_pauvre/build/pauvre/pauvre_main.py", 
line 636, in 
main()
  File 
"/<>/.pybuild/cpython3_3.10_pauvre/build/pauvre/pauvre_main.py", 
line 630, in main
args.func(parser, args)
  File 
"/<>/.pybuild/cpython3_3.10_pauvre/build/pauvre/pauvre_main.py", 
line 62, in run_subtool
import pauvre.synplot as submodule
  File 
"/<>/.pybuild/cpython3_3.10_pauvre/build/pauvre/synplot.py", line 
46, in 
import Bio.SubsMat.MatrixInfo as MI
ModuleNotFoundError: No module named 'Bio.SubsMat'

Have a nice day,  :)
Étienne.

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

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


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: python-pauvre
Source-Version: 0.2.3-2
Done: Étienne Mollier 

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

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

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

Debian distribution maintenance software
pp.
Étienne Mollier  (supplier of updated python-pauvre 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 18 Dec 2022 15:56:49 +0100
Source: python-pauvre
Architecture: source
Version: 0.2.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Étienne Mollier 
Closes: 1024835
Changes:
 python-pauvre (0.2.3-2) unstable; urgency=medium
 .
   * biopython-1.80.patch: add; migrate away from Bio.SubsMat.
 This patch fixes build time test failures with Biopython 1.80 caused
 by removal of Bio.SubsMat in favor of Bio.Align.substitution_matrices.
 (Closes: 1024835)
   * d/control: declare compliance to standards version 4.6.2.
   * d/copyright: update debian/ authors and year.
Checksums-Sha1:
 2f7d193aab3d05f26e6b08dd727a48c30f8d2e64 2485 python-pauvre_0.2.3-2.dsc
 dbc83f44f932058a24c25c65cd8fe7689d57d159 7652 
python-pauvre_0.2.3-2.debian.tar.xz
Checksums-Sha256:
 ab8041c4bc5d9f6b99f746332bd2d6eaa1a0e89f5b5b3c91a32c3862a91c32e1 2485 
python-pauvre_0.2.3-2.dsc
 

Bug#1010973: marked as done (python-tesserocr: flaky autopkgtest)

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 21:31:54 +
with message-id 
and subject line Bug#1010973: fixed in python-tesserocr 2.5.2-2
has caused the Debian Bug report #1010973,
regarding python-tesserocr: flaky autopkgtest
to be marked as done.

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

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


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

Source: python-tesserocr
Version: 2.5.2-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of you package on ppc64el 
because it was showing up as a regression for the upload of gcc-12. I 
noticed that the test regularly fails and I saw failures on other 
architectures too (but not on amd64).


Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

Don't hesitate to reach out if you need help and some more information
from our infrastructure.

Paul

https://ci.debian.net/packages/p/python-tesserocr/

https://ci.debian.net/data/autopkgtest/testing/ppc64el/p/python-tesserocr/21168683/log.gz

autopkgtest [00:42:09]: test upstream: [---
...F..
==
FAIL: test_recognize (tests.test_api.TestTessBaseApi)
Test Recognize with and without timeout.
--
Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.zbt5r5ou/downtmp/autopkgtest_tmp/tests/test_api.py", 
line 336, in test_recognize

self.assertTrue(res)
AssertionError: False is not true

--
Ran 22 tests in 83.470s

FAILED (failures=1)
autopkgtest [00:43:33]: test upstream: ---]


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: python-tesserocr
Source-Version: 2.5.2-2
Done: Malik Mlitat 

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

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

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

Debian distribution maintenance software
pp.
Malik Mlitat  (supplier of updated python-tesserocr package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 18 Dec 2022 12:46:18 +0100
Source: python-tesserocr
Architecture: source
Version: 2.5.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Malik Mlitat 
Closes: 1010973
Changes:
 python-tesserocr (2.5.2-2) unstable; urgency=medium
 .
   [ Malik Mlitat ]
   * Add new patch to disable flaky test; Closes: #1010973
Checksums-Sha1:
 813d30c0ddc24971010055e32726fc21b1fd0c16 2279 python-tesserocr_2.5.2-2.dsc
 03b13b9abbc338547f2609e39a8fa70e7bdd7b1c 4680 
python-tesserocr_2.5.2-2.debian.tar.xz
 f4fd4dce28d841401fd8ccd7ad4d4e58288ed747 9968 
python-tesserocr_2.5.2-2_amd64.buildinfo
Checksums-Sha256:
 d7550568abf1ab710cc10faa261e9488652303fdf2dab430f98ba06984a78408 2279 
python-tesserocr_2.5.2-2.dsc
 1e0fb5a6721b629c62b3e4fb24a4eb7a2cb09d4e32952c98a0e86215591653c1 4680 
python-tesserocr_2.5.2-2.debian.tar.xz
 a72fcbede2777d35c52d353c98e51aac99e5205ff5352bf92bcfc1b5f2059acd 9968 
python-tesserocr_2.5.2-2_amd64.buildinfo
Files:
 425f8b4c17377928136af84c7d79b756 2279 python optional 
python-tesserocr_2.5.2-2.dsc
 ef5f3520b6a7c9b03fe49b0217472abd 4680 python optional 
python-tesserocr_2.5.2-2.debian.tar.xz
 2c93586835d8affe8c3033bbafe8785d 9968 python optional 
python-tesserocr_2.5.2-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCgAtFiEEbnQ09Yl9Q7F/zVe3U9W8ZLUjeKIFAmOfQ3EPHHN3dEB0ZWNo
aWUubmV0AAoJEFPVvGS1I3iiqn0P/AyhYxxuHxrzG1ae7mXSy88hMhyjNRYL1rc7
RCSmWYR5vZt6PkzP6vpTzu2NJULAyb87/3XfUgA3nUVJqXy6xtgD30z/R5V/BCE9
USSs5QZ7vn60DqQiAS3z9QUt/9y3OLJfmGYL0kiz0v+DXCJhsG7Gl1Ewtc+BngVF

Bug#1026304: marked as done (obantoo build-depends on dropped package.)

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 21:22:15 +
with message-id 
and subject line Bug#1026304: fixed in obantoo 2.1.12+ds1-4
has caused the Debian Bug report #1026304,
regarding obantoo build-depends on dropped package.
to be marked as done.

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

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


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

Package: obantoo
Version: 2.1.12+ds1-3
Severity: serious
Justification: rc policy - "packages must be buildable within the same 
release"

User: debian...@lists.debian.org
Usertags: edos-uninstallable

obantoo build-depends on libitext5-java-doc which is no longer built
by the libitext5-java source package. It is still present in unstable as
a cruft package, but is completely gone from testing.
--- End Message ---
--- Begin Message ---
Source: obantoo
Source-Version: 2.1.12+ds1-4
Done: Jochen Sprickerhof 

We believe that the bug you reported is fixed in the latest version of
obantoo, which is due to be installed in the Debian FTP archive.

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

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

Debian distribution maintenance software
pp.
Jochen Sprickerhof  (supplier of updated obantoo package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 18 Dec 2022 13:43:52 +0100
Source: obantoo
Architecture: source
Version: 2.1.12+ds1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Jochen Sprickerhof 
Closes: 1026304
Changes:
 obantoo (2.1.12+ds1-4) unstable; urgency=medium
 .
   * Drop unused build dependencies (Closes: #1026304)
   * Bump policy version (no changes)
Checksums-Sha1:
 e6f020635505c1c0130d24982430a1f4241c7b05 2057 obantoo_2.1.12+ds1-4.dsc
 e54c8944669a17dbf3f58a5885255c59b9b89189 2936 
obantoo_2.1.12+ds1-4.debian.tar.xz
 fb3106f24feed383a7a83ce3d9cac2af64987628 10864 
obantoo_2.1.12+ds1-4_source.buildinfo
Checksums-Sha256:
 f6f8d44bc7fce0054a3cfd4bd2258ffa4619a0b1ae46f610bb2283089cfbe79a 2057 
obantoo_2.1.12+ds1-4.dsc
 cc690995119ed007ab1aba1482178ee6e752bb7d5d908a58448eb1e5288e7535 2936 
obantoo_2.1.12+ds1-4.debian.tar.xz
 3869d1418a1bc8f1001131437f3184e2ee2398b698b41a070df5942d640d72c5 10864 
obantoo_2.1.12+ds1-4_source.buildinfo
Files:
 ce0b1e50b671aa8c3f695567095a493a 2057 java optional obantoo_2.1.12+ds1-4.dsc
 e8d87152fe8f585616c6f6bcf971548f 2936 java optional 
obantoo_2.1.12+ds1-4.debian.tar.xz
 90d76db694fbae9561658fa4aabd76ed 10864 java optional 
obantoo_2.1.12+ds1-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAmOfCyQACgkQW//cwljm
lDP4Bw//ZGk7ZdJTSt9Btf7JMSVcRVwpsk8Ifz5pBFiSqMe67e+fSOznqWprMfJr
k8p85sU7lJ6pzI2x5V9zgfy3tJ9nQYEFmwxu7v1xkgLSUDpDYDwVyLdZNQC+vtOK
N4NCf1C8essGaobwReC5UB7WrV3YJxEbQpsJTaXOS49gDwiZpPKAls4909T/2l4V
pXyRmUzyo+krouG4zJ5m53bJeftWDj8AZdMcrYkUnp64qe8i5TXgUmkGRlGxO09x
hV1+MI76U9quA9L2G1XO9snGAeGOh33SOYpQ6n3lVKVNdUBTkMi1jC9S5EyO6vp2
psB5g4O7n+pT6KsTFkgP3oICDFFJgJU0IaMKj23d1dgBTAS0SlOgvA3trzzO+rbF
ScVU1GqVb4FvlbpE40cZKUHAITNw314/Pe2PYZY92QB+Ydf1Edo7vlpVnsqCYSWP
R3P3I6nIvnswtlegTmMtQh2EPLDaMqNtVfn0dneziR5yPRjl6w6SjCq+dxZODWF+
GvxTlQFGY1Q/E1YYIBKh7AovPhXHhMUBIVUsre9wepCcwOBsK1GZscNAZbjklUdY
8vHCMfKPgfZGFplH3p4/wC8zq+M8dW/x8oWAPBxId8pCT6vBXavB3v7fqD7EhhuL
CH7BItGiO3MIsEh9Yo8fPsVX8Ysd5lfe4iMwrpPb8UI2VmH/SEs=
=kZxz
-END PGP SIGNATURE End Message ---

Bug#937049: marked as done (mini-buildd: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 21:19:10 +
with message-id 
and subject line Bug#937049: fixed in mini-buildd 1.9.112
has caused the Debian Bug report #937049,
regarding mini-buildd: Python2 removal in sid/bullseye
to be marked as done.

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

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


-- 
937049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937049
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mini-buildd
Version: 1.0.41
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:mini-buildd

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: mini-buildd
Source-Version: 1.9.112
Done: Stephan Sürken 

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

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

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

Debian distribution maintenance software
pp.
Stephan Sürken  (supplier of updated mini-buildd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 19 Dec 2022 17:58:52 +0100
Source: mini-buildd
Architecture: source
Version: 1.9.112
Distribution: unstable
Urgency: medium
Maintainer: Stephan Sürken 
Changed-By: Stephan Sürken 
Closes: 933751 937049
Changes:
 mini-buildd (1.9.112) unstable; urgency=medium
 .
   Upload to unstable:
 .
   * Bug fix: "mini-buildd (build-)depends on cruft package.", thanks to
  Peter Michael Green (Closes: #933751).
   * Bug fix: "Python2 removal in sid/bullseye", thanks to Matthias Klose
  (Closes: #937049).
 .
   Please wait for a '2.0.x release' for any production purposes. While no
   serious problem is known, some mandatory testing (&& documentation)
   is still outstanding, especially on
 - upgrades from 1.0.x
 - the new 'setup' system
 .
   Details:
 .
   * [cf90668] dist.py(setup): 'wheezy' needs 'apt-key-add' workaround
   * [bf3d0e1] dist.py(setup): 'wheezy' needs 'apt-urold' workaround
   * 

Bug#933751: marked as done (mini-buildd (build-)depends on cruft package.)

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 21:19:10 +
with message-id 
and subject line Bug#933751: fixed in mini-buildd 1.9.112
has caused the Debian Bug report #933751,
regarding mini-buildd (build-)depends on cruft package.
to be marked as done.

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

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


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

Package: mini-buildd
Version: 1.0.41
Severity: serious

python-mini-buildd depends on and the mini-buildd source package 
build-depends on the python-django-registration binary package which is 
no longer built by the python-django-registration source package.


I notice this already seems to be fixed in experimental, are there any 
blockers for uploading the experimental version to unstable?
--- End Message ---
--- Begin Message ---
Source: mini-buildd
Source-Version: 1.9.112
Done: Stephan Sürken 

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

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

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

Debian distribution maintenance software
pp.
Stephan Sürken  (supplier of updated mini-buildd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 19 Dec 2022 17:58:52 +0100
Source: mini-buildd
Architecture: source
Version: 1.9.112
Distribution: unstable
Urgency: medium
Maintainer: Stephan Sürken 
Changed-By: Stephan Sürken 
Closes: 933751 937049
Changes:
 mini-buildd (1.9.112) unstable; urgency=medium
 .
   Upload to unstable:
 .
   * Bug fix: "mini-buildd (build-)depends on cruft package.", thanks to
  Peter Michael Green (Closes: #933751).
   * Bug fix: "Python2 removal in sid/bullseye", thanks to Matthias Klose
  (Closes: #937049).
 .
   Please wait for a '2.0.x release' for any production purposes. While no
   serious problem is known, some mandatory testing (&& documentation)
   is still outstanding, especially on
 - upgrades from 1.0.x
 - the new 'setup' system
 .
   Details:
 .
   * [cf90668] dist.py(setup): 'wheezy' needs 'apt-key-add' workaround
   * [bf3d0e1] dist.py(setup): 'wheezy' needs 'apt-urold' workaround
   * [8a646b2] builder.py,ftpd.py: Cosmetic: Update two now misleading code
 comments
   * [5f4bc16] builtins.py (Css): Add "failed" as possible sbuild status
 (color)
   * [3d837a9] builder.py: Add "Canceled-By" tag for explicit build
 cancellation (by shutdown or user)
   * [353cddb] manual/administrator.rst: Improve 'vsyscall hint'
   * [d7743d6] repository.py (Repository._mbd_package_migrate): Fix
 'migrate' when 'version' not given
   * [b4734f5] events.html: Add 'rebuild' button on 'INSTALLED'
   * [e4b9c0e] dist.py: Add Ubuntu 22.10 (kinetic)
   * [a21af05] api/source_header.html: Use same header for ls && show
   * [a96f655] api.py (Output): Add meta argument class for 'output'
   * [ce187e4] builtins.py, api.html (mbd_api): 'output': Rather use
 'Output' meta option instance than explicit HTML
   * [ff6c6ea] api.py, tags/api_arg.html: Revive HTML 'select' for Choice*
 arguments
   * [fe3b5df] tags/api_arg.html: Fix includes of "checked" and "required"
 for correct spacing
   * [918f2b4] mini_buildd.js(mbd_api_call): Code (mostly style)
 improvements
   * [c8d37ee] api.html/js(API calls): Switch "confirm" to HTML only
   * [fea4f2c] api.html/mini_buildd.js: Switch to "onsubmit/action" (drop
 extra 

Bug#1024183: marked as done (llvm-toolchain-13: autopkgtest regression: /usr/lib/llvm-13/bin/mlir-tblgen doesn't exist)

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 21:16:54 +
with message-id 
and subject line Bug#1024183: fixed in llvm-toolchain-13 1:13.0.1-10
has caused the Debian Bug report #1024183,
regarding llvm-toolchain-13: autopkgtest regression: 
/usr/lib/llvm-13/bin/mlir-tblgen doesn't exist
to be marked as done.

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

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


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

Source: llvm-toolchain-13
Version: 1:13.0.1-9
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
llvm-toolchain-13  from testing1:13.0.1-9
all others from testingfrom testing

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

Currently this regression is blocking the migration to testing [1]. Can 
you please investigate the situation and fix it?


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=llvm-toolchain-13

https://ci.debian.net/data/autopkgtest/testing/amd64/l/llvm-toolchain-13/28320845/log.gz

-- The C compiler identification is GNU 12.2.0
-- The CXX compiler identification is GNU 12.2.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Could NOT find ZLIB (missing: ZLIB_LIBRARY ZLIB_INCLUDE_DIR) -- Found 
LibXml2: /usr/lib/x86_64-linux-gnu/libxml2.so (found version "2.9.14") 
CMake Error at /usr/lib/llvm-13/lib/cmake/llvm/LLVMExports.cmake:1535 
(message):

  The imported target "mlir-tblgen" references the file

 "/usr/lib/llvm-13/bin/mlir-tblgen"

  but this file does not exist.  Possible reasons include:

  * The file was deleted, renamed, or moved to another location.

  * An install or uninstall procedure did not complete successfully.

  * The installation package was faulty and contained

 "/usr/lib/llvm-13/lib/cmake/llvm/LLVMExports.cmake"

  but not all the files it references.

Call Stack (most recent call first):
  /usr/lib/llvm-13/cmake/LLVMConfig.cmake:300 (include)
  CMakeLists.txt:3 (find_package)


-- Configuring incomplete, errors occurred!
See also 
"/tmp/autopkgtest-lxc.pmp7rkht/downtmp/autopkgtest_tmp/build/CMakeFiles/CMakeOutput.log".

autopkgtest [09:20:41]: test cmake-test



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: llvm-toolchain-13
Source-Version: 1:13.0.1-10
Done: Sylvestre Ledru 

We believe that the bug you reported is fixed in the latest version of
llvm-toolchain-13, which is due to be installed in the Debian FTP archive.

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

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

Debian distribution maintenance software
pp.
Sylvestre Ledru  (supplier of updated llvm-toolchain-13 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 18 Nov 2022 09:47:27 +0100
Source: llvm-toolchain-13
Architecture: source
Version: 1:13.0.1-10
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team 
Changed-By: Sylvestre Ledru 
Closes: 1023532 1024183
Changes:
 llvm-toolchain-13 (1:13.0.1-10) unstable; urgency=medium
 .
   * cherry-pick the cmake workaround from 14 (Closes: #1024183)
   * Unbreak the build with a new version protobuf
 Thanks to gcs for the patch (Closes: #1023532)
Checksums-Sha1:
 69af6095e2d177f7f734bf9a6a8ac404347040ce 7277 llvm-toolchain-13_13.0.1-10.dsc
 62717696c6ef6f4c11cb3ed50ce28921bf5fef34 

Bug#1023532: marked as done (llvm-toolchain-13: FTBFS with protobuf 3.21)

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 21:16:54 +
with message-id 
and subject line Bug#1023532: fixed in llvm-toolchain-13 1:13.0.1-10
has caused the Debian Bug report #1023532,
regarding llvm-toolchain-13: FTBFS with protobuf 3.21
to be marked as done.

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

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


-- 
1023532: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023532
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: llvm-toolchain-13
Version: 1:13.0.1-7
Severity: important
Usertags: protobuf3_21
Tags: ftbfs bookworm sid

Hi,

Currently your package FTBFS for other reasons already, but the
upcoming Protobuf transition will also break it. I attach the fixing
patch to make it easier for you.

Regards,
Laszlo/GCS
diff -Nur a/clang-tools-extra/clangd/index/remote/monitor/Monitor.cpp b/clang-tools-extra/clangd/index/remote/monitor/Monitor.cpp
--- a/clang-tools-extra/clangd/index/remote/monitor/Monitor.cpp	2022-01-23 01:26:53.0 +0100
+++ b/clang-tools-extra/clangd/index/remote/monitor/Monitor.cpp	2022-09-08 19:17:39.103577486 +0200
@@ -66,9 +66,8 @@
   const auto JsonStatus =
   google::protobuf::util::MessageToJsonString(Response, , Options);
   if (!JsonStatus.ok()) {
-clang::clangd::elog("Can not convert response ({0}) to JSON ({1}): {2}\n",
-Response.DebugString(), JsonStatus.error_code(),
-JsonStatus.error_message().as_string());
+clang::clangd::elog("Can not convert response ({0}) to JSON: {1}\n",
+Response.DebugString(), JsonStatus.ToString());
 return -1;
   }
   llvm::outs() << Output;
--- End Message ---
--- Begin Message ---
Source: llvm-toolchain-13
Source-Version: 1:13.0.1-10
Done: Sylvestre Ledru 

We believe that the bug you reported is fixed in the latest version of
llvm-toolchain-13, which is due to be installed in the Debian FTP archive.

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

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

Debian distribution maintenance software
pp.
Sylvestre Ledru  (supplier of updated llvm-toolchain-13 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 18 Nov 2022 09:47:27 +0100
Source: llvm-toolchain-13
Architecture: source
Version: 1:13.0.1-10
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team 
Changed-By: Sylvestre Ledru 
Closes: 1023532 1024183
Changes:
 llvm-toolchain-13 (1:13.0.1-10) unstable; urgency=medium
 .
   * cherry-pick the cmake workaround from 14 (Closes: #1024183)
   * Unbreak the build with a new version protobuf
 Thanks to gcs for the patch (Closes: #1023532)
Checksums-Sha1:
 69af6095e2d177f7f734bf9a6a8ac404347040ce 7277 llvm-toolchain-13_13.0.1-10.dsc
 62717696c6ef6f4c11cb3ed50ce28921bf5fef34 158844 
llvm-toolchain-13_13.0.1-10.debian.tar.xz
 21cb648ea7c851bb66099b9d71bd8a4a1c4a88d5 31045 
llvm-toolchain-13_13.0.1-10_amd64.buildinfo
Checksums-Sha256:
 580a92fccc179edf10b855562ab98b449c70805d95520854a50da1946eaea7c4 7277 
llvm-toolchain-13_13.0.1-10.dsc
 29fa228b28b261cf4d29e02ad699d0da5c95093247ea3cfd248152cef5f99a26 158844 
llvm-toolchain-13_13.0.1-10.debian.tar.xz
 8490a8aae94bf64c6cc6eba4de544480abcd548c25f78a599da88be880ca84d2 31045 
llvm-toolchain-13_13.0.1-10_amd64.buildinfo
Files:
 8c0ddd5ad33eb78045190d7325c2a396 7277 devel optional 
llvm-toolchain-13_13.0.1-10.dsc
 3c98ef49dbad4ff4b1e88d96ee1e382a 158844 devel optional 
llvm-toolchain-13_13.0.1-10.debian.tar.xz
 d46d34d843eebb355813fae73b410cc1 31045 devel optional 
llvm-toolchain-13_13.0.1-10_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAmOgeCcACgkQfmUo2nUv
G+Fqyw/9FlSB0k8SSvPIlJvcz0eNWbaWA7H30b9FHS8HoopHXpFCy4ENiaIKeEDN
TIi23TAmxHk8WApo4C4ydvjg/AaB2tcPwk6TwoSyepnD+X054UDu6p/uI48IfCS9
z/fTiAPO8V069S2V99DQe0eZhAipBqUp2dJjsQSHqtmzi8ieuLK2Tl62O17+Ef2+
dVu0k6+077w1oXQYL7JxGLjo//Zumjvq+g2DJuy+uCTrrytwiupT5fxbsQ+LJx9t
GNrD0CtcLP5XgQjyRDEtbUT6ENRw4yIdySrzJCxy3ZWS2O8YNUA+k+V0Hg0/gPqO
gpAXo7z0aVT/ag3RvasaELGZRiPtkNITkzXzuh0Cwy2BAwh9H4Tf4fNYZPfpsUz2
+A4zcWBuJinQSyZwYUI7gt/BIPFhplearaZ2jRnZh74vHZsBzV3sB3iZHcIHjJ0Y
QdwIo/UmNga0ydz2wsGxh/N8P3Bwxd1DP6L010ARoXiqsCyLQ/zCbjRy6Y1rCdvo

Bug#1021705: marked as done (metakernel: build dependency missing in testing: python3-pypandoc)

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 16:02:56 -0500
with message-id 
and subject line Re: Bug#1021705: metakernel: build dependency missing in 
testing: python3-pypandoc
has caused the Debian Bug report #1021705,
regarding metakernel: build dependency missing in testing: python3-pypandoc
to be marked as done.

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

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


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

Source: metakernel
Version: 0.27.5-4
Severity: serious
User: debian...@lists.debian.org
Usertag: edos-uninstallable

Dear maintainer(s),

Dose [1] is reporting issues with your packages. Normally your build 
dependencies shouldn't be removed from testing without removal all 
reverse build dependencies too, nor should a package be allowed to 
migrate unless all build dependencies are candidate for migration too. 
However, somehow we ended up in the current state and your source 
package is missing some Build-Depends for some while now. Not being able 
to build from source in a suite is an RC bug in that suite.


Can you please solve the situation by either helping the maintainer of 
your Build-Depends to enable migration to testing, or by working around 
the lack of this build dependency?


Paul

[1] https://qa.debian.org/dose/debcheck/src_testing_main/index.html


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Hello Paul,

On Thu, Oct 13, 2022 at 12:23:40PM +0200, Paul Gevers wrote:
[snip]
> Can you please solve the situation by either helping the maintainer of your
> Build-Depends to enable migration to testing, or by working around the lack
> of this build dependency?

Sorry for the late reply. I see that python3-pypandoc is currently in bookworm:

$ date -u; rmadison -s bookworm python3-pypandoc
Mon 19 Dec 2022 08:59:55 PM UTC
python3-pypandoc | 1.7.4+ds0-2   | testing| all

Thus, I am closing this bug.

> Paul
--Joe--- End Message ---

Bug#1022340: marked as done (redmine: FTBFS: Could not find gem 'csv (~> 3.2.0)' in cached gems or installed locally. The source contains the following gems matching 'csv': csv-3.1.9)

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 23:07:57 +0200
with message-id 
and subject line Re: Bug#1022340: redmine: FTBFS: Could not find gem 'csv (~> 
3.2.0)' in cached gems or installed locally. The source contains the following 
gems matching 'csv': csv-3.1.9
has caused the Debian Bug report #1022340,
regarding redmine: FTBFS: Could not find gem 'csv (~> 3.2.0)' in cached gems or 
installed locally.  The source contains the following gems matching 'csv': 
csv-3.1.9
to be marked as done.

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

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


-- 
1022340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022340
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: redmine
Version: 5.0.2-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with ruby
>dh_update_autotools_config
>dh_autoreconf
>debian/rules override_dh_auto_configure
> make[1]: Entering directory '/<>'
> ./debian/check-locales
> bundle install --local --quiet
> `/sbuild-nonexistent` is not a directory.
> Bundler will use `/tmp/bundler20221023-854280-m4b28v854280' as your home 
> directory temporarily.
> Could not find gem 'csv (~> 3.2.0)' in cached gems or installed locally.
> 
> The source contains the following gems matching 'csv':
>   * csv-3.1.9
> make[1]: *** [debian/rules:14: override_dh_auto_configure] Error 7


The full build log is available from:
http://qa-logs.debian.net/2022/10/23/redmine_5.0.2-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221023=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
On Sun, Nov 20, 2022 at 11:35:49AM +0200, Adrian Bunk wrote:
> Control: block -1 by 1023495
> 
> On Thu, Oct 27, 2022 at 12:18:13AM +0900, Marc Dequènes wrote:
> > Quack,
> > 
> > Thanks for the report.
> > 
> > When I first read the logs I could not fathom what was going on: we B-D on
> > ruby-csv (>= 3.2.0) and it's not even installed!
> > So it happens that libruby3.0 provides ruby-csv but it explicitly specify
> > ruby-csv (= 3.1.9).
> > I seems the resolver is confused by the fact libruby3.0 also has to be
> > present to satisfy another dep.
> >...
> 
> The resolver is working as it should:
> One package that fulfills the dependency is installed (libruby3.1).
> 
> The easiest way to resolve this would be to wait until 3.1 becomes the 
> default soon (#1023495), which should fix this FTBFS.
>...

This has now happened:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/redmine.html
https://tests.reproducible-builds.org/debian/history/redmine.html

cu
Adrian--- End Message ---

Bug#1026338: marked as done (libnet-duo-perl: autopkgtest regression: use strict)

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 21:03:01 +
with message-id 
and subject line Bug#1026338: fixed in libnet-duo-perl 1.02-3
has caused the Debian Bug report #1026338,
regarding libnet-duo-perl: autopkgtest regression: use strict
to be marked as done.

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

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


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

Source: libnet-duo-perl
Version: 1.02-2
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
libnet-duo-perlfrom testing1.02-2
all others from testingfrom testing

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

Currently this regression is blocking the migration to testing [1]. Can 
you please investigate the situation and fix it?


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=libnet-duo-perl

https://ci.debian.net/data/autopkgtest/testing/amd64/libn/libnet-duo-perl/29144812/log.gz

ok 76 - Syntax check lib/Debian/pkgperl/Foobar.pm
not ok 77 - use strict   lib/Debian/pkgperl/Foobar.pm

#   Failed test 'use strict   lib/Debian/pkgperl/Foobar.pm'
#   at /usr/share/perl5/Test/Strict.pm line 436.
not ok 78 - use warnings lib/Debian/pkgperl/Foobar.pm

#   Failed test 'use warnings lib/Debian/pkgperl/Foobar.pm'
#   at /usr/share/perl5/Test/Strict.pm line 437.
1..78
# Looks like you failed 2 tests of 78.
Dubious, test returned 2 (wstat 512, 0x200)
Failed 2/78 subtests
Test Summary Report
---
t/style/module-version.t  (Wstat: 512 (exited 2) Tests: 0 Failed: 0)
  Non-zero exit status: 2
  Parse errors: No plan found in TAP output
t/style/strict.t  (Wstat: 512 (exited 2) Tests: 78 Failed: 2)
  Failed tests:  77-78
  Non-zero exit status: 2
Files=21, Tests=881,  7 wallclock secs ( 0.09 usr  0.02 sys +  5.95 cusr 
 0.68 csys =  6.74 CPU)

Result: FAIL
autopkgtest [03:27:10]: test autodep8-perl-build-deps



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: libnet-duo-perl
Source-Version: 1.02-3
Done: gregor herrmann 

We believe that the bug you reported is fixed in the latest version of
libnet-duo-perl, which is due to be installed in the Debian FTP archive.

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

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated libnet-duo-perl 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 18 Dec 2022 20:59:06 +0100
Source: libnet-duo-perl
Architecture: source
Version: 1.02-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 1026338
Changes:
 libnet-duo-perl (1.02-3) unstable; urgency=medium
 .
   * Team upload.
   * Add debian/tests/pkg-perl/smoke-env.
 Don't run automated/release tests during autopkgtests.
 (Closes: #1026338)
   * debian/watch: use uscan macros.
   * Declare compliance with Debian Policy 4.6.2.
   * Annotate test-only build dependencies with .
Checksums-Sha1:
 90992a76523eb66a0f4709201ae9b7bbf607f0e8 2626 libnet-duo-perl_1.02-3.dsc
 c296fbd167b30e0acf7b3d9f3e38bcff1266dfb1 8972 
libnet-duo-perl_1.02-3.debian.tar.xz
Checksums-Sha256:
 291b7407cb762b3c802b1095b7d6623f4c8d781faa121945b3d8622886efd2f6 2626 
libnet-duo-perl_1.02-3.dsc
 d2b0a91da33239ff1ca612b94ed35a85637a3f94dd8a7d4255805e9995c3f32a 8972 
libnet-duo-perl_1.02-3.debian.tar.xz
Files:
 96a2c1075334946197e3f38f4791d8d5 2626 perl optional libnet-duo-perl_1.02-3.dsc
 85dbdad46ba3abab1249866adfba03da 8972 perl optional 
libnet-duo-perl_1.02-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

Bug#1025980: marked as done (texlive-extra breaks latexml autopkgtest: Couldn't convert t/structure/glossary.tex)

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 21:00:34 +
with message-id 
and subject line Bug#1025980: fixed in latexml 0.8.7-1
has caused the Debian Bug report #1025980,
regarding texlive-extra breaks latexml autopkgtest: Couldn't convert 
t/structure/glossary.tex
to be marked as done.

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

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


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

Source: texlive-extra, latexml
Control: found -1 texlive-extra/2022.20221123-1
Control: found -1 latexml/0.8.6-5
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

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


   passfail
texlive-extra  from testing2022.20221123-1
latexmlfrom testing0.8.6-5
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 texlive-extra to 
testing [1]. Due to the nature of this issue, I filed this bug report 
against both packages. Can you please investigate the situation and 
reassign the bug to the right package?


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=texlive-extra

https://ci.debian.net/data/autopkgtest/testing/amd64/l/latexml/29254215/log.gz

PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" 
"-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(1, 
'blib/lib', 'blib/arch')" t/*.t

# #   LaTeXML version 0.8.6
#   XML::LibXML 2.0134; libxml2 20914
#   XML::LibXSLT 2.002000; libxslt 10135
#   TeX 3.141592653 (TeX Live 2022/Debian)
t/000_test_context.t .. 1..1
ok 1 - Test Context
ok
t/002_unit_findfile.t . ok 1 - use LaTeXML;
ok 2 - use LaTeXML::Core::State;
ok 3 - use LaTeXML::Core::Stomach;
ok 4 - use LaTeXML::Common::Model;
ok 5 - use LaTeXML::Global;
ok 6 - use LaTeXML::Package;
ok 7 - use LaTeXML::Common::Error;
ok 8 - amsmath.sty did not resolve as amsmath.sty.ltxml
ok 9 - amsmath2.sty did not resolve as amsmath.sty.ltxml
ok 10 - amsmath3-1.sty did not resolve as amsmath.sty.ltxml
ok 11 - amsmathv2.sty did not resolve as amsmath.sty.ltxml
ok 12 - amsmath_v2.sty did not resolve as amsmath.sty.ltxml
ok 13 - amsmath2019.sty did not resolve as amsmath.sty.ltxml
ok 14 - amsmath_v2019.sty did not resolve as amsmath.sty.ltxml
ok 15 - amsmath_2019.sty did not resolve as amsmath.sty.ltxml
ok 16 - amsmath_05_2019.sty did not resolve as amsmath.sty.ltxml
ok 17 - amsmath052019.sty did not resolve as amsmath.sty.ltxml
ok 18 - amsmath_052019.sty did not resolve as amsmath.sty.ltxml
ok 19 - amsmath05_2019.sty did not resolve as amsmath.sty.ltxml
ok 20 - amsmath05-2019.sty did not resolve as amsmath.sty.ltxml
ok 21 - amsmath_arxiv.sty did not resolve as amsmath.sty.ltxml
ok 22 - amsmath2_arxiv.sty did not resolve as amsmath.sty.ltxml
ok 23 - amsmath2019_arxiv.sty did not resolve as amsmath.sty.ltxml
ok 24 - amsmath_05-2019_arxiv.sty did not resolve as amsmath.sty.ltxml
ok 25 - amsmath_05-2019_arxiv.sty did not resolve as amsmath.sty.ltxml
ok 26 - amsmath95.sty did not resolve as amsmath.sty.ltxml
ok 27 - amsmath_conference.sty did not resolve as amsmath.sty.ltxml
ok 28 - amsmath2019_conference.sty did not resolve as amsmath.sty.ltxml
ok 29 - amsmath_v2-workshop.sty did not resolve as amsmath.sty.ltxml
1..29
ok
t/00_unittest.t ... ok 1 - use LaTeXML;
ok 2 - use LaTeXML::Package;
ok 3 - Make Token (x)
ok 4 - Got correct token (x)
ok 5 - Make Token (x)
ok 6 - Got correct deref (x)
ok 7 - Make Token (z)
ok 8 - Got correct token (z)
ok 9 - Make Tokens (x)
ok 10 - Got correct token (x)
ok 11 - Make Tokens from Token's (x,x,x)
ok 12 - Got correct tokens
ok 13 - Make Tokens from Tokens (x,x,x)
ok 14 - Make Token (z)
ok 15 - Got correct deref (x,x,x)
ok 16 - Make Tokens from Token's (z,z,z)
ok 17 - Got correct tokens (z,z,z)
ok 18 - Make Tokens from Tokens (x,x,x)
ok 19 - Got correct tokens (x,x,x)
ok 20 - Make balanced tokens
ok 21 - Check is balanced
ok 22 - Make unbalanced tokens
ok 23 - Check is not balancde
ok 24 - substitute tokens w/o params
ok 25 - Got correct (non)substitution
ok 26 - make tokens w/ params
ok 27 - 

Processed: Re: Bug#1026326: procps breaks pslist autopkgtest

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:procps 2:4.0.2-2
Bug #1026326 [src:procps, src:pslist] procps breaks pslist autopkgtest
Bug reassigned from package 'src:procps, src:pslist' to 'src:procps'.
No longer marked as found in versions pslist/1.4.0-4 and procps/2:4.0.2-2.
Ignoring request to alter fixed versions of bug #1026326 to the same values 
previously set
Bug #1026326 [src:procps] procps breaks pslist autopkgtest
Marked as found in versions procps/2:4.0.2-2.
> affects -1 src:pslist
Bug #1026326 [src:procps] procps breaks pslist autopkgtest
Added indication that 1026326 affects src:pslist

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

Bug#1026326: procps breaks pslist autopkgtest

[Paul Gevers]

Control: reassign -1 src:procps 2:4.0.2-2
Control: affects -1 src:pslist

Hi Craig,

On 19-12-2022 06:54, Craig Small wrote:
On Mon, 19 Dec 2022 at 03:54, Paul Gevers > wrote:


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

The good news is the testing caught this, yay for autopkgtest!


:)


The fix, with a test case, is already in upstream.[2]


So let's reassign to procps exclusively. Doing so with this message.

Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#997327: marked as done (jamin: FTBFS: configure: error: cannot find required auxiliary files: compile missing)

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 20:58:15 +
with message-id 
and subject line Bug#997327: fixed in jamin 0.98.9~git20170111~199091~repack1-2
has caused the Debian Bug report #997327,
regarding jamin: FTBFS: configure: error: cannot find required auxiliary files: 
compile missing
to be marked as done.

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

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


-- 
997327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997327
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jamin
Version: 0.98.9~git20170111~199091~repack1-1.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
> autoheader: WARNING: documentation.
> touch debian/stamp-autotools-files
> chmod a+x /<>/./configure
> mkdir -p .
> cd . && CFLAGS="-g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security" CXXFLAGS="-g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security" CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" 
> LDFLAGS="-Wl,-z,relro" /<>/./configure --build=x86_64-linux-gnu 
> --prefix=/usr --includedir="\${prefix}/include" 
> --mandir="\${prefix}/share/man" --infodir="\${prefix}/share/info" 
> --sysconfdir=/etc --localstatedir=/var --libexecdir="\${prefix}/lib/jamin" 
> --srcdir=. --disable-maintainer-mode --disable-dependency-tracking 
> --disable-silent-rules
> configure: error: cannot find required auxiliary files: compile missing


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/jamin_0.98.9~git20170111~199091~repack1-1.1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: jamin
Source-Version: 0.98.9~git20170111~199091~repack1-2
Done: Nilesh Patra 

We believe that the bug you reported is fixed in the latest version of
jamin, which is due to be installed in the Debian FTP archive.

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

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

Debian distribution maintenance software
pp.
Nilesh Patra  (supplier of updated jamin package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 19 Dec 2022 00:29:43 +0530
Source: jamin
Architecture: source
Version: 0.98.9~git20170111~199091~repack1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Nilesh Patra 
Closes: 997327 1025309
Changes:
 jamin (0.98.9~git20170111~199091~repack1-2) unstable; urgency=medium
 .
   * Team Upload.
   [ Ondřej Nový ]
   * d/copyright: Use https protocol in Format field
   * d/control: Set Vcs-* to salsa.debian.org
   * d/changelog: Remove trailing whitespaces
 .
   [ Felipe Sateler ]
   * Change maintainer address to debian-multime...@lists.debian.org
 .
   [ Ondřej Nový ]
   * d/watch: Use https protocol
 .
   [ Jonas Smedegaard ]
   * Remove myself from Uploaders
 .
   [ Bas Couwenberg ]
   * Build depend on libfftw3-dev, fftw3-dev no longer provided.
(closes: #1025309)
 .
   [ Nilesh Patra ]
   * d/compat: Bump compat to 10
   * Add d/clean
   * Remove useless files in debian/ dir
   * Add patch to Skip a couple of potiles
   * Un-mess d/copyright
   * d/control:
 + Prune B-D on cdbs
 + Remove useless B-D on dh_autoreconf
   * d/rules:
 + Propagate debug flag into CFLAGS
 + Switch from cdbs to debhelper (Closes: #997327)
Checksums-Sha1:
 cb58b1ccbaabcd62ceea61d96edd04775201e13a 1611 
jamin_0.98.9~git20170111~199091~repack1-2.dsc
 e21cd362b3fa6d97b4a773d48a8036e59488363e 8288 
jamin_0.98.9~git20170111~199091~repack1-2.debian.tar.xz
 b4cc190faea1238998f0746101cffc6af24cc073 16167 
jamin_0.98.9~git20170111~199091~repack1-2_amd64.buildinfo
Checksums-Sha256:
 

Bug#1026344: marked as done (insilicoseq: autopkgtest needs update for new version of numpy: EOFError)

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 20:57:50 +
with message-id 
and subject line Bug#1026344: fixed in insilicoseq 1.5.4-4
has caused the Debian Bug report #1026344,
regarding insilicoseq: autopkgtest needs update for new version of numpy: 
EOFError
to be marked as done.

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

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


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

Source: insilicoseq
Version: 1.5.4-3
Severity: serious
X-Debbugs-CC: nu...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:numpy

Dear maintainer(s),

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


   passfail
numpy  from testing1:1.23.5-2
insilicoseqfrom testing1.5.4-3
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 numpy to testing 
[1]. Of course, numpy shouldn't just break your autopkgtest (or even 
worse, your package), but it seems to me that the change in numpy 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 numpy 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=numpy

https://ci.debian.net/data/autopkgtest/testing/amd64/i/insilicoseq/29465792/log.gz

=== FAILURES 
===
___ test_bad_err_mod 
___


file = 'data/empty_file', mmap_mode = None, allow_pickle = True
fix_imports = True, encoding = 'ASCII'

@set_module('numpy')
def load(file, mmap_mode=None, allow_pickle=False, fix_imports=True,
 encoding='ASCII', *, max_header_size=format._MAX_HEADER_SIZE):
"""
Load arrays or pickled objects from ``.npy``, ``.npz`` or 
pickled files.
.. warning:: Loading files that contain object arrays uses 
the ``pickle``
 module, which is not secure against erroneous or 
maliciously
 constructed data. Consider passing 
``allow_pickle=False`` to
 load data that is known not to contain object 
arrays for the

 safer handling of untrusted sources.
Parameters
--
file : file-like object, string, or pathlib.Path
The file to read. File-like objects must support the
``seek()`` and ``read()`` methods and must always
be opened in binary mode.  Pickled files require that the
file-like object support the ``readline()`` method as well.
mmap_mode : {None, 'r+', 'r', 'w+', 'c'}, optional
If not None, then memory-map the file, using the given mode 
(see

`numpy.memmap` for a detailed description of the modes).  A
memory-mapped array is kept on disk. However, it can be 
accessed
and sliced like any ndarray.  Memory mapping is especially 
useful
for accessing small fragments of large files without 
reading the

entire file into memory.
allow_pickle : bool, optional
Allow loading pickled object arrays stored in npy files. 
Reasons for
disallowing pickles include security, as loading pickled 
data can
execute arbitrary code. If pickles are disallowed, loading 
object

arrays will fail. Default: False
.. versionchanged:: 1.16.3
Made default False in response to CVE-2019-6446.
fix_imports : bool, optional
Only useful when loading Python 2 generated pickled files 
on Python 3,
which includes npy/npz files containing object arrays. If 
`fix_imports`
is True, pickle will try to map the old Python 2 names to 

Bug#1026255: marked as done (FTBFS: error: invalid flag: -html4)

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 20:58:51 +
with message-id 
and subject line Bug#1026255: fixed in junit5-system-exit 1.1.2-4
has caused the Debian Bug report #1026255,
regarding FTBFS: error: invalid flag: -html4
to be marked as done.

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

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


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

Source: junit5-system-exit
Version: 1.1.2-3
Severity: serious
Tags: ftbfs patch

Dear Maintainer,

junit5-system-exit currently fails to build from source with the 
following error message:
Starting process 'command 
'/usr/lib/jvm/java-17-openjdk-amd64/bin/javadoc''. Working directory: 
/build/1st/junit5-system-exit-1.1.2 Command: 
/usr/lib/jvm/java-17-openjdk-amd64/bin/javadoc 
@/build/1st/junit5-system-exit-1.1.2/build/tmp/javadoc/javadoc.options
Successfully started process 'command 
'/usr/lib/jvm/java-17-openjdk-amd64/bin/javadoc''

error: invalid flag: -html4
1 error

(for details see 
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/junit5-system-exit.html)


I was able to reproduce this on my Sid system, and the package built 
successfully when replacing the flag, see the attached patch.


Based on the output from javadoc, this option now seems to be the 
default
-html5Generate HTML 5 output. This option is no longer 
required.
so alternatively the javadoc section can be trimmed down. Another thing 
is that I haven't checked when the html5 option was introduced or when 
it replaced html4. It builds successfully with the current JDK, but it 
might introduced problems when backporting the package in the future. I 
don't know if this is a concern.


Regardless, the attached patch should fix the build issue or serve as 
the base for a better fix :)


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

Kernel: Linux 6.0.0-5-amd64 (SMP w/3 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en

Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled


--
mvh / best regards
Hans Joachim Desserud
http://desserud.orgDescription: Replace html4 option with html5

The html4 option has been removed/replaced in newer JDKs, causing a build 
failure.

---
Forwarded: no

--- junit5-system-exit-1.1.2.orig/build.gradle
+++ junit5-system-exit-1.1.2/build.gradle
@@ -74,6 +74,6 @@ publishing {
 
 javadoc {
 if(JavaVersion.current().isJava9Compatible()) {
-options.addBooleanOption('html4', true)
+options.addBooleanOption('html5', true)
 }
 }
--- End Message ---
--- Begin Message ---
Source: junit5-system-exit
Source-Version: 1.1.2-4
Done: Emmanuel Bourg 

We believe that the bug you reported is fixed in the latest version of
junit5-system-exit, which is due to be installed in the Debian FTP archive.

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

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated junit5-system-exit 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 17 Dec 2022 18:58:59 +0100
Source: junit5-system-exit
Architecture: source
Version: 1.1.2-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Closes: 1026255
Changes:
 junit5-system-exit (1.1.2-4) unstable; urgency=medium
 .
   * Team upload.
   * Removed the -java-doc package (Closes: #1026255)
   * Standards-Version updated to 4.6.2
Checksums-Sha1:
 2b9fb5c1e8bc8bac9152ced16f7c6f422bbe0367 2150 junit5-system-exit_1.1.2-4.dsc
 9b2e10a7ae4afe8c7ca5b68d0a57201b8e949fe6 4588 
junit5-system-exit_1.1.2-4.debian.tar.xz
 098092f2262cba0293fd3c2739afbd51253bdab1 17728 
junit5-system-exit_1.1.2-4_source.buildinfo
Checksums-Sha256:
 ae993daf73c6072812c6f94ff1be910dc12b41177735dcc6f58058c9de5c5ca7 2150 
junit5-system-exit_1.1.2-4.dsc
 e407fb47c0b10addf37502bdc493bb2d35def98b43a7b561f5a25354947d289e 4588 
junit5-system-exit_1.1.2-4.debian.tar.xz
 

Bug#1025309: marked as done (jamin: FTBFS with fftw3 (3.3.10-1))

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 20:58:15 +
with message-id 
and subject line Bug#1025309: fixed in jamin 0.98.9~git20170111~199091~repack1-2
has caused the Debian Bug report #1025309,
regarding jamin: FTBFS with fftw3 (3.3.10-1)
to be marked as done.

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

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


-- 
1025309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025309
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jamin
Version: 0.98.9~git20170111~199091~repack1-1.1
Severity: serious
Tags: ftbfs patch

Dear Maintainer,

Your package FTBFS with fftw3 (3.3.10-1) because it not longer provides 
fftw3-dev.

The attached patch resolves the issue by changing the dependency to 
libfftw3-dev.

Kind Regards,

Bas
diff -Nru jamin-0.98.9~git20170111~199091~repack1/debian/changelog 
jamin-0.98.9~git20170111~199091~repack1/debian/changelog
--- jamin-0.98.9~git20170111~199091~repack1/debian/changelog2021-02-07 
10:12:13.0 +0100
+++ jamin-0.98.9~git20170111~199091~repack1/debian/changelog2022-12-02 
12:55:09.0 +0100
@@ -1,3 +1,10 @@
+jamin (0.98.9~git20170111~199091~repack1-1.2) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Build depend on libfftw3-dev, fftw3-dev no longer provided.
+
+ -- Bas Couwenberg   Fri, 02 Dec 2022 12:55:09 +0100
+
 jamin (0.98.9~git20170111~199091~repack1-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru jamin-0.98.9~git20170111~199091~repack1/debian/control 
jamin-0.98.9~git20170111~199091~repack1/debian/control
--- jamin-0.98.9~git20170111~199091~repack1/debian/control  2017-01-11 
21:31:55.0 +0100
+++ jamin-0.98.9~git20170111~199091~repack1/debian/control  2022-12-02 
12:55:09.0 +0100
@@ -9,7 +9,7 @@
  debhelper,
  dh-buildinfo,
  docbook-to-man,
- fftw3-dev,
+ libfftw3-dev,
  indent,
  intltool,
  libclutter-gtk-1.0-dev,
diff -Nru jamin-0.98.9~git20170111~199091~repack1/debian/control.in 
jamin-0.98.9~git20170111~199091~repack1/debian/control.in
--- jamin-0.98.9~git20170111~199091~repack1/debian/control.in   2017-01-11 
21:31:55.0 +0100
+++ jamin-0.98.9~git20170111~199091~repack1/debian/control.in   2022-12-02 
12:54:52.0 +0100
@@ -6,7 +6,7 @@
  Jonas Smedegaard ,
 Build-Depends: @cdbs@,
  docbook-to-man,
- fftw3-dev,
+ libfftw3-dev,
  indent,
  intltool,
  libclutter-gtk-1.0-dev,
--- End Message ---
--- Begin Message ---
Source: jamin
Source-Version: 0.98.9~git20170111~199091~repack1-2
Done: Nilesh Patra 

We believe that the bug you reported is fixed in the latest version of
jamin, which is due to be installed in the Debian FTP archive.

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

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

Debian distribution maintenance software
pp.
Nilesh Patra  (supplier of updated jamin package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 19 Dec 2022 00:29:43 +0530
Source: jamin
Architecture: source
Version: 0.98.9~git20170111~199091~repack1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Nilesh Patra 
Closes: 997327 1025309
Changes:
 jamin (0.98.9~git20170111~199091~repack1-2) unstable; urgency=medium
 .
   * Team Upload.
   [ Ondřej Nový ]
   * d/copyright: Use https protocol in Format field
   * d/control: Set Vcs-* to salsa.debian.org
   * d/changelog: Remove trailing whitespaces
 .
   [ Felipe Sateler ]
   * Change maintainer address to debian-multime...@lists.debian.org
 .
   [ Ondřej Nový ]
   * d/watch: Use https protocol
 .
   [ Jonas Smedegaard ]
   * Remove myself from Uploaders
 .
   [ Bas Couwenberg ]
   * Build depend on libfftw3-dev, fftw3-dev no longer provided.
(closes: #1025309)
 .
   [ Nilesh Patra ]
   * d/compat: Bump compat to 10
   * Add d/clean
   * Remove useless files in debian/ dir
   * Add patch to Skip a couple of potiles
   * Un-mess d/copyright
   * d/control:
 + Prune B-D on cdbs
 + Remove useless B-D on dh_autoreconf
   * d/rules:
 + Propagate debug flag into CFLAGS
 + Switch from cdbs to debhelper (Closes: #997327)
Checksums-Sha1:
 cb58b1ccbaabcd62ceea61d96edd04775201e13a 1611 
jamin_0.98.9~git20170111~199091~repack1-2.dsc
 

Bug#1025686: marked as done (Plugin cannot be loaded, not linked against hdf5)

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 20:56:09 +
with message-id 
and subject line Bug#1025686: fixed in hdf5-filter-plugin 
0.0~git2022.49e3b65-3
has caused the Debian Bug report #1025686,
regarding Plugin cannot be loaded, not linked against hdf5
to be marked as done.

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

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


-- 
1025686: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025686
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: hdf5-filter-plugin
Version: 0.0~git2022.49e3b65-2
Severity: serious
Tags: patch

Hello,

hdf5 cannot load the plugin dynamically:

   >>> import h5py
   >>> h5py.h5z.filter_avail(32004)
   False

This is because the library cannot be loaded due to missing HDF5 symbols:

   $ python3
   Python 3.10.8 (main, Nov  4 2022, 09:21:25) [GCC 12.2.0] on linux
   Type "help", "copyright", "credits" or "license" for more information.
   >>> import ctypes
   >>> lib = 
ctypes.CDLL("/usr/lib/x86_64-linux-gnu/hdf5/serial/plugins/libh5lz4.so")
   Traceback (most recent call last):
 File "", line 1, in 
 File "/usr/lib/python3.10/ctypes/__init__.py", line 374, in __init__
   self._handle = _dlopen(self._name, mode)
   OSError: /usr/lib/x86_64-linux-gnu/hdf5/serial/plugins/libh5lz4.so: 
undefined symbol: H5E_PLINE_g

I filed a PR upstream that fixes the problem:
https://github.com/nexusformat/HDF5-External-Filter-Plugins/pull/27

I'm attaching the corresponding patch.


Thanks,

Enrico


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

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

Versions of packages hdf5-filter-plugin depends on:
ii  libbz2-1.0 1.0.8-5+b1
ii  libc6  2.36-6
ii  libhdf5-103-1  1.10.8+repack-4
ii  liblz4-1   1.9.4-1

hdf5-filter-plugin recommends no packages.

hdf5-filter-plugin suggests no packages.
commit 3d93e1821dd10962f4477d8b3615024cf10f4cc6
Author: Enrico Zini 
Date:   Wed Dec 7 12:19:17 2022 +0100

Added missing libraries

diff --git a/LZ4/src/CMakeLists.txt b/LZ4/src/CMakeLists.txt
index b5bf34b..1823eff 100644
--- a/LZ4/src/CMakeLists.txt
+++ b/LZ4/src/CMakeLists.txt
@@ -1,7 +1,7 @@
 set(SOURCES H5Zlz4.c lz4_h5plugin.c)
 
 set(INCLUDE_DIRS ${HDF5_INCLUDE_DIRS} ${LZ4_INCLUDE_DIRS})
-set(LINK_LIBS ${LZ4_LIBRARIES})
+set(LINK_LIBS ${LZ4_LIBRARIES} ${HDF5_LIBRARIES})
 
 if(CMAKE_SYSTEM_NAME MATCHES Windows)
 #
--- End Message ---
--- Begin Message ---
Source: hdf5-filter-plugin
Source-Version: 0.0~git2022.49e3b65-3
Done: Thorsten Alteholz 

We believe that the bug you reported is fixed in the latest version of
hdf5-filter-plugin, which is due to be installed in the Debian FTP archive.

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

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

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated hdf5-filter-plugin 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 17 Dec 2022 17:07:18 +0100
Source: hdf5-filter-plugin
Architecture: source
Version: 0.0~git2022.49e3b65-3
Distribution: unstable
Urgency: medium
Maintainer: Freexian Packaging Team 
Changed-By: Thorsten Alteholz 
Closes: 1025391 1025686
Changes:
 hdf5-filter-plugin (0.0~git2022.49e3b65-3) unstable; urgency=medium
 .
   [ Enrico Zini ]
   * Disable building the bitshuffle plugin (Closes: #1025391)
   * Added patch to link against hdf5 (Closes: #1025686)
 .
   [ Thorsten Alteholz ]
   * debian/control: Maintainer: set to Freexian, moved myself to Uploaders:
Checksums-Sha1:
 32ba66585ee15372fea933dcadc3a2a396db6e3c 2375 
hdf5-filter-plugin_0.0~git2022.49e3b65-3.dsc
 5256ced7accd5b227c209f69234799ff87e1e75b 614592 
hdf5-filter-plugin_0.0~git2022.49e3b65.orig.tar.xz
 f8dd49cf6d5155f39a159457335a5712a7853f24 5052 
hdf5-filter-plugin_0.0~git2022.49e3b65-3.debian.tar.xz
 f43c97c181b05a8c416a07f7969f3305a87455bb 8447 
hdf5-filter-plugin_0.0~git2022.49e3b65-3_amd64.buildinfo
Checksums-Sha256:
 

Bug#1025391: marked as done (hdf5-filter-plugin: missing Breaks+Replaces: bitshuffle)

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 20:56:09 +
with message-id 
and subject line Bug#1025391: fixed in hdf5-filter-plugin 
0.0~git2022.49e3b65-3
has caused the Debian Bug report #1025391,
regarding hdf5-filter-plugin: missing Breaks+Replaces: bitshuffle
to be marked as done.

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

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


-- 
1025391: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025391
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: hdf5-filter-plugin
Version: 0.0~git2022.49e3b65-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

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

  Preparing to unpack 
.../hdf5-filter-plugin_0.0~git2022.49e3b65-2_amd64.deb ...
  Unpacking hdf5-filter-plugin (0.0~git2022.49e3b65-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/hdf5-filter-plugin_0.0~git2022.49e3b65-2_amd64.deb 
(--unpack):
   trying to overwrite 
'/usr/lib/x86_64-linux-gnu/hdf5/serial/plugins/libh5bshuf.so', which is also in 
package bitshuffle 0.3.5-4+b1
  Errors were encountered while processing:
   
/var/cache/apt/archives/hdf5-filter-plugin_0.0~git2022.49e3b65-2_amd64.deb


Is my understanding right that src:hdf5-filter-plugin supersedes src:bitshuffle?
Then please RM the obsolete bitshuffle package.

If bitshuffle is to be removed, the B+R against it can be unversioned (unless
you have a virtual bitshuffle package provided somewhere).


cheers,

Andreas


bitshuffle=0.3.5-4+b1_hdf5-filter-plugin=0.0~git2022.49e3b65-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: hdf5-filter-plugin
Source-Version: 0.0~git2022.49e3b65-3
Done: Thorsten Alteholz 

We believe that the bug you reported is fixed in the latest version of
hdf5-filter-plugin, which is due to be installed in the Debian FTP archive.

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

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

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated hdf5-filter-plugin 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 17 Dec 2022 17:07:18 +0100
Source: hdf5-filter-plugin
Architecture: source
Version: 0.0~git2022.49e3b65-3
Distribution: unstable
Urgency: medium
Maintainer: Freexian Packaging Team 
Changed-By: Thorsten Alteholz 
Closes: 1025391 1025686
Changes:
 hdf5-filter-plugin (0.0~git2022.49e3b65-3) unstable; urgency=medium
 .
   [ Enrico Zini ]
   * Disable building the bitshuffle plugin (Closes: #1025391)
   * Added patch to link against hdf5 (Closes: #1025686)
 .
   [ Thorsten Alteholz ]
   * debian/control: Maintainer: set to Freexian, moved myself to Uploaders:
Checksums-Sha1:
 32ba66585ee15372fea933dcadc3a2a396db6e3c 2375 
hdf5-filter-plugin_0.0~git2022.49e3b65-3.dsc
 5256ced7accd5b227c209f69234799ff87e1e75b 614592 
hdf5-filter-plugin_0.0~git2022.49e3b65.orig.tar.xz
 f8dd49cf6d5155f39a159457335a5712a7853f24 5052 
hdf5-filter-plugin_0.0~git2022.49e3b65-3.debian.tar.xz
 f43c97c181b05a8c416a07f7969f3305a87455bb 8447 
hdf5-filter-plugin_0.0~git2022.49e3b65-3_amd64.buildinfo
Checksums-Sha256:
 f084e507379232ff427c7d561ff6184dc1d77013366f5cfac76d84062a29fdb5 2375 
hdf5-filter-plugin_0.0~git2022.49e3b65-3.dsc
 583704a7410c1a021ce88c7165e5d3cc41e40024f8d9cd28de00ad009abaee34 614592 
hdf5-filter-plugin_0.0~git2022.49e3b65.orig.tar.xz
 7a0848b4592446e0f5a2ed81a3daa0de4fa44cc0d4d3c3784148098dce47c91c 5052 
hdf5-filter-plugin_0.0~git2022.49e3b65-3.debian.tar.xz
 c7be1b24414b288611ac392f8059f29008fda7e6bc01d53bc9bbbfde05455895 8447 
hdf5-filter-plugin_0.0~git2022.49e3b65-3_amd64.buildinfo
Files:
 a71c28e09dde6307ac531876cdd40238 2375 science optional 
hdf5-filter-plugin_0.0~git2022.49e3b65-3.dsc
 f859150e510294ace21fed7deae0b8a7 614592 science 

Bug#1025232: marked as done (hdf5: Build dependencies on openjdk-11 that will not be in bookworm)

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 20:56:00 +
with message-id 
and subject line Bug#1025232: fixed in hdf5 1.10.8+repack1-1
has caused the Debian Bug report #1025232,
regarding hdf5: Build dependencies on openjdk-11 that will not be in bookworm
to be marked as done.

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

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


-- 
1025232: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025232
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hdf5
Version: 1.10.8+repack-4
Severity: serious
Tags: sid bookworm
X-Debbugs-Cc: sramac...@debian.org

openjdk-11 will not be be part of bookworm (see #1023237). Please adapt
the package to use the default JDK version (openjdk-17) in its build
dependencies.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: hdf5
Source-Version: 1.10.8+repack1-1
Done: Gilles Filippini 

We believe that the bug you reported is fixed in the latest version of
hdf5, which is due to be installed in the Debian FTP archive.

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

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

Debian distribution maintenance software
pp.
Gilles Filippini  (supplier of updated hdf5 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 18 Dec 2022 18:20:33 +0100
Source: hdf5
Architecture: source
Version: 1.10.8+repack1-1
Distribution: unstable
Urgency: medium
Maintainer: Gilles Filippini 
Changed-By: Gilles Filippini 
Closes: 1025232
Changes:
 hdf5 (1.10.8+repack1-1) unstable; urgency=medium
 .
   * Build against default JDK for all arches (closes: #1025232)
   * java-test-TestH5Arw_array-overflow.patch: fix an array overflow
 in java test TestH5Arw
   * Repack upstream source to drop embedded jar files
   * java_use-system-jars.patch: use system provided jar files
 instead of the embedded ones
   * Build-Depends: junit4, libslf4j-java
   * debian/watch: use the Github upstream repo
Checksums-Sha1:
 aa890a6929bfa31af6bc9ef75bcfb4d919dfc7f8 3921 hdf5_1.10.8+repack1-1.dsc
 481711d480a847632c2071f8893dafea6d73550b 13422843 
hdf5_1.10.8+repack1.orig.tar.gz
 0dd52d2f34583325fe45e93006910efc4c6a40c6 150904 
hdf5_1.10.8+repack1-1.debian.tar.xz
 1b5270a31b489747e24eee06566297b6bcd45090 11849 
hdf5_1.10.8+repack1-1_source.buildinfo
Checksums-Sha256:
 3c9b7c438f174506fd2764b77437466fd528374aeab9db9c73c59ceee6ac990d 3921 
hdf5_1.10.8+repack1-1.dsc
 7b38e58ff83b13fd8959a90b13bf896bc318ba096c940ab0847abf3ad41a0b31 13422843 
hdf5_1.10.8+repack1.orig.tar.gz
 d11ad311c20f84199a04f44be87e03f91560c8f020576624edd07dd58eacbacb 150904 
hdf5_1.10.8+repack1-1.debian.tar.xz
 10415ef41a3ace6823a8eb3a7b97e66d1f18f45385a67f828a730d4069c443ce 11849 
hdf5_1.10.8+repack1-1_source.buildinfo
Files:
 3480b00a2af45b5e29c19a952783689d 3921 science optional 
hdf5_1.10.8+repack1-1.dsc
 3abe82551bb9d04ab6057043d21ff308 13422843 science optional 
hdf5_1.10.8+repack1.orig.tar.gz
 242471eefb632f365fb7c39bf928b4cd 150904 science optional 
hdf5_1.10.8+repack1-1.debian.tar.xz
 85e7a7315511f4d0fde0165f4560e12b 11849 science optional 
hdf5_1.10.8+repack1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFEBAEBCgAuFiEEoJObzArDE05WtIyR7+hsbH/+z4MFAmOfhxYQHHBpbmlAZGVi
aWFuLm9yZwAKCRDv6Gxsf/7Pg6HyB/wIkfDVILrKlCUI9LcL8Oyu3PKSm0jy4PpW
j/ruVCPgOUP4ipoRgmjeCadMiFzZXYOM+X7hiRYSuiczTerBCe40erLoiK9eYvak
cKQZbe3O31WfvOE/nzjpoRFaeBHO2+CfWMYcIA/7LLdN0Bn0zzZCWg2RTuUXrM52
Lm6u7FEbCx3ixEqsL5ht07iNhIlnJL6tZ4y9AV6n7mZG00Hb7TlbVA0uYKQgQOQs
JCHuw82O+3JXO5wGisOxlx8DUBvJDVebY1Vjc2DE2a/5HD9YBfkJX4ITNRjJF3p1
uQKH0bM0p00XhWjj0W3dlhZLjYFZB1mRliYudqs7VxIxiPMkKM4D
=0KCZ
-END PGP SIGNATURE End Message ---

Bug#1022796: marked as done (haskell-heist unsatisfiable build-dependency libghc-aeson-dev < 1.5)

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 20:55:29 +
with message-id 
and subject line Bug#1022796: fixed in haskell-heist 1.1.1.0-1
has caused the Debian Bug report #1022796,
regarding haskell-heist unsatisfiable build-dependency libghc-aeson-dev < 1.5
to be marked as done.

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

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


-- 
1022796: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022796
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-heist
Version: 1.1.0.1-3
Severity: serious

Hi,

haskell-heist build-depends on libghc-aeson-dev (<< 1.5) but the version
of that package in sid is 2.0.3.0-1.

-Ralf.
--- End Message ---
--- Begin Message ---
Source: haskell-heist
Source-Version: 1.1.1.0-1
Done: Ilias Tsitsimpis 

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

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

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

Debian distribution maintenance software
pp.
Ilias Tsitsimpis  (supplier of updated haskell-heist 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 19 Dec 2022 11:05:55 +0200
Source: haskell-heist
Architecture: source
Version: 1.1.1.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group 

Changed-By: Ilias Tsitsimpis 
Closes: 1022796
Changes:
 haskell-heist (1.1.1.0-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #1022796)
   * Declare compliance with Debian policy 4.6.1
Checksums-Sha1:
 ff9f96f2eccc2b5a9950b604ba83be2dedaf2178 4122 haskell-heist_1.1.1.0-1.dsc
 d61566117878f707fcefe4ad6c49286cb9cda552 72146 
haskell-heist_1.1.1.0.orig.tar.gz
 f41c87d0f852e9e4fefe4bf2532308e5bf655f54 4108 
haskell-heist_1.1.1.0-1.debian.tar.xz
 073d0f9132bb4c812c46175861fd6d2ec1725cbf 12995 
haskell-heist_1.1.1.0-1_amd64.buildinfo
Checksums-Sha256:
 a35d80ea0abc4bb89de4594c23497005fe7991993b4581d3a5b8b1d969dca188 4122 
haskell-heist_1.1.1.0-1.dsc
 d487bac70fe603f2157d14e61a8276924d31c50d99353fc0209313fdab046a9d 72146 
haskell-heist_1.1.1.0.orig.tar.gz
 22fcd4b8e0f1b62cf4c9a05d6c57f1a8da5124102b099286b8472b13ecb34aca 4108 
haskell-heist_1.1.1.0-1.debian.tar.xz
 e770c4224048da11269fdc563e07d097a555ce7b01505828926f26710a9958ef 12995 
haskell-heist_1.1.1.0-1_amd64.buildinfo
Files:
 3643982296a95e21672c1938d5de8a9f 4122 haskell optional 
haskell-heist_1.1.1.0-1.dsc
 82d31d9aa252a9f889e670d37539d1e5 72146 haskell optional 
haskell-heist_1.1.1.0.orig.tar.gz
 4cafee46774f0c96a48126dc7846e52e 4108 haskell optional 
haskell-heist_1.1.1.0-1.debian.tar.xz
 a94b1662c342e816e6cebecc4cbce4dc 12995 haskell optional 
haskell-heist_1.1.1.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEJ9c8pfW11+AaUTb116hngMxkQDwFAmOgK1sUHGlsaWFzdHNp
QGRlYmlhbi5vcmcACgkQ16hngMxkQDyLMRAAvWsXi/YylLsxL0ciwIo3XPvoodqc
MATZvs69qPE7BVflXXefSx7DR+Jhe71FHD9IewNstneHHtmzOvGwdfzS/GkSMAqa
Oaw9byN2LPPmgcBi65dhmC/H09ac5wGu/hRuf+2ESeZY+Y9Jjpi54Np80qxVKvDw
eWPw1hAzGB9bl7t4EvM5Z58EUrf3LR25gnTgiCAMxIlBsbtVgqu/qYe3K04FZoD+
Dk7/h2NAm3oQXpfB2DfraEGhx0+kAXF4kvDXSlkqIKwlb7Q4I8LuqsQc15qWUO66
jurulStoyNv62VpZ++dpQiWy4XYcQmi4482uMJLijJ3tB0I/iYovD80oaNtrKxai
S4WzFN6mmtVK2R86DmvvBGrIzMW0ETgJe3v0q37pAdinidX7v4sQE5G7bQraa3Yo
gyuzCtijYYzJr0S33r0rFZ2RM9/PMAlef7r/7KW15F866R20CK6jePgGs4h4FNPy
IT/s56FL2SIJ4eM1sUH5lBzGaR7y5DpmTOze3pMyJzEIo89aD6hj/MaGgC+azvEh
ofvy4IOOP2IpruEnv3EOnZS57CQFGmiX/KV9dWT45Y7taYN9bJuafqg8kBzqJ+Hj
g2sQpE69G+pjpQjMVDWWpHkPMSGzVte4crd2nX9/lfxEnAtiU3AVFgIEZCdSAO7V
+Bz9EiQ6y52+H2E=
=pt7r
-END PGP SIGNATURE End Message ---

Bug#998945: marked as done (gnuit: missing required debian/rules targets build-arch and/or build-indep)

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 20:52:27 +
with message-id 
and subject line Bug#998945: fixed in gnuit 4.9.5-4
has caused the Debian Bug report #998945,
regarding gnuit: missing required debian/rules targets build-arch and/or 
build-indep
to be marked as done.

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

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


-- 
998945: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998945
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnuit
Version: 4.9.5-3
Severity: important
Justification: Debian Policy section 4.9
Tags: bookworm sid
User: debian...@lists.debian.org
Usertags: missing-build-arch-indep

Dear maintainer,

Your package does not include build-arch and/or build-indep targets in
debian/rules. This is required by Debian Policy section 4.9, since 2012.
https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules

Please note that this is also a sign that the packaging of this software
could benefit from a refresh. For example, packages using 'dh' cannot be
affected by this issue.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00052.html .
The severity of this bug will be changed to 'serious' after a month.

Best,

Lucas
--- End Message ---
--- Begin Message ---
Source: gnuit
Source-Version: 4.9.5-4
Done: Josef Schneider 

We believe that the bug you reported is fixed in the latest version of
gnuit, which is due to be installed in the Debian FTP archive.

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

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

Debian distribution maintenance software
pp.
Josef Schneider  (supplier of updated gnuit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 12 Dec 2022 16:11:11 +0200
Source: gnuit
Architecture: source
Version: 4.9.5-4
Distribution: unstable
Urgency: medium
Maintainer: Josef Schneider 
Changed-By: Josef Schneider 
Closes: 869489 965566 998945 1014171
Changes:
 gnuit (4.9.5-4) unstable; urgency=medium
 .
   * New maintainer (Closes: #1014171).
   * debian/control:
 + Update to debhelper-compat version 13 (Closes: #965566).
 + Standards-Version 4.6.1.
 + Add Rules-Requires-Root: no.
 + Add Depends on sensible-utils.
 + Remove Build-Depends on autotools-dev.
 + Change http to https.
   * debian/compat: Deleted.
   * debian/copyright:
 + Update to dep5 format.
 + Update licensing.
   * debian/rules:
 + Update for debhelper-compat version 13 (Closes: #998945).
 + Add configure command to correctly pass --host flag (Closes: #869489).
   * debian/patches:
 + Add fix-printf-string.patch to fix FTBFS.
 + Remove .gitaction from install.
   * debian/watch: Update to version 4.
   * debian/source:
 + Add format file.
 + Add lintian-overrides to remove false positive warning.
Checksums-Sha1:
 42954cc3cd94ff613df029375464b115de72aff4 1843 gnuit_4.9.5-4.dsc
 deca319fd86b632378a75185e4ae993290b299fc 8220 gnuit_4.9.5-4.debian.tar.xz
 cf02c5e45aec3672e85d7c902b1b5fb93e9227da 6090 gnuit_4.9.5-4_source.buildinfo
Checksums-Sha256:
 532d9b110e9f6852846ec02397fba8b169443b64032720310b34dfb9eb9e9f01 1843 
gnuit_4.9.5-4.dsc
 f8767db8fec9649b13ff222a8c29b7b1830e78011e2610d2b8c6037011b5afaa 8220 
gnuit_4.9.5-4.debian.tar.xz
 ffe090e4fa8ad06a53b443a445858e7d1c6057a4dd5b6130a89b338d14405255 6090 
gnuit_4.9.5-4_source.buildinfo
Files:
 d17ee94a8ae533ddf9fa178198fcfcec 1843 utils optional gnuit_4.9.5-4.dsc
 74694becccde5a5b694eaf127b0c9a5f 8220 utils optional 
gnuit_4.9.5-4.debian.tar.xz
 694d47977c2fd50772aa426c0781885f 6090 utils optional 
gnuit_4.9.5-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAmOgussACgkQweDZLphv
fH5QeA//QUBLpo62WDhhMi/lfaFScEoT7gFqdOxzZTKlr6jfIBJzVZUQfdvii0i4
fdAKGH2UfnsksM842l9OfMTtCnnzSvKBDkHyCOOLLaYDYCr2vbNADHKuCeEpjIpH
r36czNg9OwkKf8KzKaw6DNk5DcA8cFXyOkGsXjN33bU7Qj/Jz62vIWgw1z8RJ+yS
lyRbMQFMpoG2MP3Ddq/af5+lu3NUeHiqjvVU77AUlI2/ygScSW04HqbQhxbvqnq9
9p2hOd9/gVZgalgFLyOwRagZtm4zprqHHpmmlmTP4ZFu+uLXOuBLPuCOHMm/69HJ
5x+hGdQbsSCDG/oIPDZwLEY+NUgaTN7vhgPSCrO0+EfzpY/Lg3Jw9TSlehYZomUN
Ia+4/aldtvYjDkDbKyUF6xYj9utLVUnQ1Y9FvPnNkseIZLFhrZuqjjhzIxylPs9j

Bug#965566: marked as done (gnuit: Removal of obsolete debhelper compat 5 and 6 in bookworm)

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 20:52:26 +
with message-id 
and subject line Bug#965566: fixed in gnuit 4.9.5-4
has caused the Debian Bug report #965566,
regarding gnuit: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.

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

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


-- 
965566: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965566
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnuit
Version: 4.9.5-3
Severity: normal
Usertags: compat-5-6-removal

Hi,

The package gnuit uses debhelper with a compat level of 5 or 6,
which is deprecated and scheduled for removal[1].

Please bump the debhelper compat at your earliest convenience
/outside the freeze/!

  * Compat 13 is recommended (supported in stable-backports)

  * Compat 7 is the bare minimum


PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads
with compat bumps during the freeze.

If there is any risk that the fix for this bug might not migrate to
testing before 2021-01-01[3] then please postpone the fix until after
the freeze.


At the time of filing this bug, compat 5 and 6 are expected to be
removed "some time during the development cycle of bookworm".


Thanks,
~Niels


[1] https://lists.debian.org/debian-devel/2020/07/msg00065.html

[2] https://release.debian.org/bullseye/FAQ.html

[3] The choice of 2021-01-01 as a "deadline" is set before the actual
freeze deadline to provide a safe cut off point for most people.

Mind you, it is still your responsibility to ensure that the upload
makes it into testing even if you upload before that date.
--- End Message ---
--- Begin Message ---
Source: gnuit
Source-Version: 4.9.5-4
Done: Josef Schneider 

We believe that the bug you reported is fixed in the latest version of
gnuit, which is due to be installed in the Debian FTP archive.

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

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

Debian distribution maintenance software
pp.
Josef Schneider  (supplier of updated gnuit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 12 Dec 2022 16:11:11 +0200
Source: gnuit
Architecture: source
Version: 4.9.5-4
Distribution: unstable
Urgency: medium
Maintainer: Josef Schneider 
Changed-By: Josef Schneider 
Closes: 869489 965566 998945 1014171
Changes:
 gnuit (4.9.5-4) unstable; urgency=medium
 .
   * New maintainer (Closes: #1014171).
   * debian/control:
 + Update to debhelper-compat version 13 (Closes: #965566).
 + Standards-Version 4.6.1.
 + Add Rules-Requires-Root: no.
 + Add Depends on sensible-utils.
 + Remove Build-Depends on autotools-dev.
 + Change http to https.
   * debian/compat: Deleted.
   * debian/copyright:
 + Update to dep5 format.
 + Update licensing.
   * debian/rules:
 + Update for debhelper-compat version 13 (Closes: #998945).
 + Add configure command to correctly pass --host flag (Closes: #869489).
   * debian/patches:
 + Add fix-printf-string.patch to fix FTBFS.
 + Remove .gitaction from install.
   * debian/watch: Update to version 4.
   * debian/source:
 + Add format file.
 + Add lintian-overrides to remove false positive warning.
Checksums-Sha1:
 42954cc3cd94ff613df029375464b115de72aff4 1843 gnuit_4.9.5-4.dsc
 deca319fd86b632378a75185e4ae993290b299fc 8220 gnuit_4.9.5-4.debian.tar.xz
 cf02c5e45aec3672e85d7c902b1b5fb93e9227da 6090 gnuit_4.9.5-4_source.buildinfo
Checksums-Sha256:
 532d9b110e9f6852846ec02397fba8b169443b64032720310b34dfb9eb9e9f01 1843 
gnuit_4.9.5-4.dsc
 f8767db8fec9649b13ff222a8c29b7b1830e78011e2610d2b8c6037011b5afaa 8220 
gnuit_4.9.5-4.debian.tar.xz
 ffe090e4fa8ad06a53b443a445858e7d1c6057a4dd5b6130a89b338d14405255 6090 
gnuit_4.9.5-4_source.buildinfo
Files:
 d17ee94a8ae533ddf9fa178198fcfcec 1843 utils optional gnuit_4.9.5-4.dsc
 74694becccde5a5b694eaf127b0c9a5f 8220 utils optional 
gnuit_4.9.5-4.debian.tar.xz
 694d47977c2fd50772aa426c0781885f 6090 utils optional 
gnuit_4.9.5-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAmOgussACgkQweDZLphv
fH5QeA//QUBLpo62WDhhMi/lfaFScEoT7gFqdOxzZTKlr6jfIBJzVZUQfdvii0i4
fdAKGH2UfnsksM842l9OfMTtCnnzSvKBDkHyCOOLLaYDYCr2vbNADHKuCeEpjIpH

Bug#1026229: marked as done (efibootguard: missing Breaks+Replaces: libebgenv-dev (<< 0.12-2))

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 20:48:30 +
with message-id 
and subject line Bug#1026229: fixed in efibootguard 0.13-1
has caused the Debian Bug report #1026229,
regarding efibootguard: missing Breaks+Replaces: libebgenv-dev (<< 0.12-2)
to be marked as done.

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

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


-- 
1026229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026229
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: efibootguard
Version: 0.12-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

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

  Preparing to unpack .../efibootguard_0.12-2_amd64.deb ...
  Unpacking efibootguard (0.12-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/efibootguard_0.12-2_amd64.deb (--unpack):
   trying to overwrite 
'/usr/lib/x86_64-linux-gnu/efibootguard/efibootguardx64.efi', which is also in 
package libebgenv-dev 0.12-1+b1
  Errors were encountered while processing:
   /var/cache/apt/archives/efibootguard_0.12-2_amd64.deb


cheers,

Andreas


libebgenv-dev=0.12-1+b1_efibootguard=0.12-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: efibootguard
Source-Version: 0.13-1
Done: Gylstorff Quirin 

We believe that the bug you reported is fixed in the latest version of
efibootguard, which is due to be installed in the Debian FTP archive.

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

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

Debian distribution maintenance software
pp.
Gylstorff Quirin  (supplier of updated 
efibootguard package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 19 Dec 2022 09:13:14 +0100
Source: efibootguard
Architecture: source
Version: 0.13-1
Distribution: unstable
Urgency: medium
Maintainer: Quirin Gylstorff 
Changed-By: Gylstorff Quirin 
Closes: 1026229
Changes:
 efibootguard (0.13-1) unstable; urgency=medium
 .
 * Update to efibootguard 0.13
 * Add breaks/replaces for 0.12-1 (Closes: #1026229)
Checksums-Sha1:
 77a84a29c59b3fed02b5069876d32252cc13fd31 1939 efibootguard_0.13-1.dsc
 1816d626dd5ff4289936a553c261106d8036f1f1 67504 efibootguard_0.13.orig.tar.xz
 6deaa3037504e5c0004c893033b643d009cbbc47 4576 efibootguard_0.13-1.debian.tar.xz
 30753b86239506928f8b79987d79c3c76f1de7c7 5846 
efibootguard_0.13-1_source.buildinfo
Checksums-Sha256:
 54d9f9c9de7bfbbb74e16e9636f2254b87f20826c43a5f3d9bc70153cd5db7e9 1939 
efibootguard_0.13-1.dsc
 65ccb0ba43506480d0621e2d90c4b8d9c1b059a9afb179be1bb68f0cd1be7d85 67504 
efibootguard_0.13.orig.tar.xz
 045636412e8fdbd2d2d2468c696bf7b3a9ac18a0d46023c9927077a48ede2ce6 4576 
efibootguard_0.13-1.debian.tar.xz
 96fcfc6808f4e9bdf460f8c6b9f3fcf89e1e880c53a640613dcdbc125d34cab4 5846 
efibootguard_0.13-1_source.buildinfo
Files:
 c192df00a497113ef7e9fb561b975b34 1939 admin optional efibootguard_0.13-1.dsc
 594ca02286c9171d4d0b3714f626d879 67504 admin optional 
efibootguard_0.13.orig.tar.xz
 10b6bb33730366c0c5e7ea6ae7c18fb4 4576 admin optional 
efibootguard_0.13-1.debian.tar.xz
 9e46d0527f3d8d0e96bba7e5a66ada25 5846 admin optional 
efibootguard_0.13-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmOgNxkQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFKKGDADsgYqCux2N0E5vNu64s3eSulqlvBDC6S21
NZ4TbW8QLmhUKwDPvyYnBM/c7Up98nOLT4HkVpl58RpsLunspLVZNEkjg0qDarmd
Jnjw2TnSUKpB8rxyXK1VlSFeBSKrKj1KQK12KFiy+qV0vJpz4eg/XW/r6IoOZXcV
JYwUb0VPT9m1TzjVNvnWoBlXCDfQSPwuo/iHVMZmh717+U7nZkJhuXbT7UHBphxF
mn9H1Apka2zaJ8SLX+zuzyWRE7yuJfjmJVQVnoWoKZuL3BgvHQJF2/f5Mh9F4t/T
on+me4JRpu+bu9N4fFi2o84XD/OGkortuVmKyYGbIzsrk94GKIhTBL5UtMUYLmSB
rc9kzCjQ/qm1zx6bjEUUwl9z+ljoS5CsI1HCoZNXBAk1ySNW4klPjT0UoVC8gDw0
nSTyJhuuD6s9OIoQ6wDFpCD0jH+wWDYDVdiIUQlrMk9nvUOi1p9kHXHSXa+OVRhu
bE5EUj9cL4MiGOCX+Zohc+Bn/X0DESc=
=XOM3
-END PGP SIGNATURE End Message ---

Bug#1024478: marked as done (ecryptfs-utils: FTBFS against libgpgme-dev >= 1.18.0-2 [Cannot locate gpgme])

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 20:48:21 +
with message-id 
and subject line Bug#1024478: fixed in ecryptfs-utils 111-6
has caused the Debian Bug report #1024478,
regarding ecryptfs-utils: FTBFS against libgpgme-dev >= 1.18.0-2 [Cannot locate 
gpgme]
to be marked as done.

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

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


-- 
1024478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024478
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ecryptfs-utils
Version: 111-5
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
User: pkg-gnupg-ma...@lists.alioth.debian.org
Usertags: gpgme-config-transition

ecryptfs-utils relies on gpgme-config to detect gpgme. gpgme-config has
been dropped and replaced by pkg-config pc files.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
--- ecryptfs-utils-111.orig/configure.ac
+++ ecryptfs-utils-111/configure.ac
@@ -135,13 +135,6 @@ AC_ARG_ENABLE(
 )
 
 AC_ARG_WITH(
-	[gpgme-prefix],
-	[AS_HELP_STRING([--with-gpgme-prefix=PATH],[Specify the directory where gpgme install, default /usr])],
-	,
-	[with_gpgme_prefix="/usr"]
-)
-
-AC_ARG_WITH(
 	[pamdir],
 	[AS_HELP_STRING([--with-pamdir=PATH],[Specify the directory where PAM modules are stored])],
 	[pamdir="${withval}"],
@@ -315,14 +308,7 @@ if test "${enable_tspi}" = "yes" ; then
 fi
 
 if test "${enable_gpg}" = "yes" ; then
-	AC_MSG_CHECKING([for gpgme])
-	if ! test -x "${with_gpgme_prefix}/bin/gpgme-config"; then
-		AC_MSG_ERROR([Cannot locate gpgme])
-	else
-		AC_MSG_RESULT([found])
-		GPGME_CFLAGS="`\"${with_gpgme_prefix}/bin/gpgme-config\" --cflags`"
-		GPGME_LIBS="`\"${with_gpgme_prefix}/bin/gpgme-config\" --libs`"
-	fi
+	PKG_CHECK_MODULES([GPGME], [gpgme >= 1.0.0])
 fi
 
 if test "${enable_pam}" = "yes" ; then
@@ -385,8 +371,6 @@ AC_SUBST([pamlibdir])
 AC_SUBST([pkgconfigdir])
 AC_SUBST([rootsbindir])
 AC_SUBST([ecryptfskeymoddir])
-AC_SUBST([GPGME_CFLAGS])
-AC_SUBST([GPGME_LIBS])
 AC_SUBST([CRYPTO_CFLAGS])
 AC_SUBST([CRYPTO_LIBS])
 AM_CONDITIONAL([BUILD_OPENSSL], [test "${enable_openssl}" = "yes"])
--- End Message ---
--- Begin Message ---
Source: ecryptfs-utils
Source-Version: 111-6
Done: Laszlo Boszormenyi (GCS) 

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

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

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated ecryptfs-utils 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 19 Dec 2022 19:46:40 +0100
Source: ecryptfs-utils
Architecture: source
Version: 111-6
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Closes: 1024478
Changes:
 ecryptfs-utils (111-6) unstable; urgency=medium
 .
   [ Andreas Metzler  ]
   * Use pkg-config to detect gpgme (closes: #1024478).
Checksums-Sha1:
 298b2e20539c69205a812ce7e61f0552ea71c9d4 2120 ecryptfs-utils_111-6.dsc
 415ae5d9c98d4ead3d01fcbe9a9f5b42b499e822 11836 
ecryptfs-utils_111-6.debian.tar.xz
Checksums-Sha256:
 c10d3ce58386154c41ec5e8900e9965bcd80bdef3a9c98b89d5197f3a9ffc1bc 2120 
ecryptfs-utils_111-6.dsc
 a06177f26ba568e4e679906e28a50191f127f5cb506558d1cb3bd347f736f024 11836 
ecryptfs-utils_111-6.debian.tar.xz
Files:
 acd9dc467ad5c41e4dd115814ded9a55 2120 misc optional ecryptfs-utils_111-6.dsc
 f07f0bd16948a1f5df74ae448f7d2eeb 11836 misc optional 
ecryptfs-utils_111-6.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAmOgtO4ACgkQ3OMQ54ZM
yL+fLw/+MfQWRfgCrT1tzlWS0HbiaazDfigaY4RGVnjnGcYMmbi9tPLDfLXuYuAh
RUvqIlZvHqwMUiJUo9BnN2bCFeV5s9k38pmMP2pw/zrizsXau5ygqUd9vGjtWR2C
Y7v4QZMkJIXK9VqDzASFl0TOeOmN9lz48/18pSQgTn9TMc4DyUCPE22DqLqiU5WE
Rj8JsAE5DbmOY31aUQ6fJJV51m5ZhUIDzQ0imce2mjybXOFkacsKUqGiYwMyvJN0
G3ks8x/z3epZTeFrbL9bomvCT6saKYI64cmJ01RT5LVxyA24ydQIPIVCV3CqG/KI
1tMU0ekd0H52I+pvkfQ/g+gKx16ufYsXdjVnvl3IhaMusFAFaHgWz12Mic9hxW9q

Bug#1023688: marked as done (improper permissions on fcgiwrap systemd socket lead to privilege escalation to www-data under default config)

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 20:49:54 +
with message-id 
and subject line Bug#1023688: fixed in fcgiwrap 1.1.0-14
has caused the Debian Bug report #1023688,
regarding improper permissions on fcgiwrap systemd socket lead to privilege 
escalation to www-data under default config
to be marked as done.

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

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


-- 
1023688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023688
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fcgiwrap
Version: 1.1.0-12
Severity: critical
Tags: patch, security

On a default installation of Debian 11 (bullseye) with other releases probably 
also affected, systemd socket file /lib/systemd/system/fcgiwrap.socket from 
package fcgiwrap contains no Mode= configuration parameter, making systemd pick 
the default 0666. The socket is therefore world accessible and any user on the 
system may, when package fcgiwrap is installed, elevate privileges and execute 
code as www-data user by communicating with the socket via fastcgi protocol. 
www-data is specified as User= and Group= in 
/lib/systemd/system/fcgiwrap.service, also supplied by package fcgiwrap.

Proof of concept terminal recording: http://upload.sijanec.eu/f.mp4

Solution: add SocketMode=0660, SocketUser=www-data, Group=www-data to 
/lib/systemd/system/fcgiwrap.socket --- this would, however, break existing 
configurations that rely on /run/fcgiwrap.socket being world connectable.

Is this intended behaviour? Doesn't it break user's expectations, as suddenly 
everyone can influence httpd (nginx slaves also run under www-data, for 
example)?

- BEGIN PATCH -
Author: Anton Luka Šijanec 
Description: Modify default user/group and listening mode of socket
Forwarded: no

--- a/systemd/fcgiwrap.socket
+++ b/systemd/fcgiwrap.socketfixed
@@ -3,6 +3,9 @@ Description=fcgiwrap Socket

 [Socket]
 ListenStream=/run/fcgiwrap.sock
+Mode=0660
+SocketUser=www-data
+SockerGroup=www-data

 [Install]
 WantedBy=sockets.target
- END PATCH -

Attachments:
root@host:~# ls -lah /run/fcgiwrap.socket
srw-rw-rw- 1 root root 0 Nov  8 19:42 /run/fcgiwrap.socket

=> /lib/systemd/system/fcgiwrap.socket
[Unit]
Description=fcgiwrap Socket

[Socket]
ListenStream=/run/fcgiwrap.socket

[Install]
WantedBy=sockets.target



=> /lib/systemd/system/fcgiwrap.service
[Unit]
Description=Simple CGI Server
After=nss-user-lookup.target
Requires=fcgiwrap.socket

[Service]
Environment=DAEMON_OPTS=-f
EnvironmentFile=-/etc/default/fcgiwrap
ExecStart=/usr/sbin/fcgiwrap ${DAEMON_OPTS}
User=www-data
Group=www-data

[Install]
Also=fcgiwrap.socket

-- 
Anton Luka Šijanec 
F4C3E3A4DFB7254397A9F993E76135F49802CD14
http://splet.sijanec.eu/pgp-key.txt
--- End Message ---
--- Begin Message ---
Source: fcgiwrap
Source-Version: 1.1.0-14
Done: Jordi Mallach 

We believe that the bug you reported is fixed in the latest version of
fcgiwrap, which is due to be installed in the Debian FTP archive.

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

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

Debian distribution maintenance software
pp.
Jordi Mallach  (supplier of updated fcgiwrap package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 17 Dec 2022 18:23:54 +0100
Source: fcgiwrap
Architecture: source
Version: 1.1.0-14
Distribution: unstable
Urgency: medium
Maintainer: Debian fcgiwrap Maintainers 
Changed-By: Jordi Mallach 
Closes: 1023688 1026251
Changes:
 fcgiwrap (1.1.0-14) unstable; urgency=medium
 .
   * Brown paper bag release.
   * Fix typo in systemd socket definition which actually made the
 security fixes in -13 not effective (closes: #1023688, #1026251).
Checksums-Sha1:
 a0d295b6eb4eeae6938ef7e78cde5179b53556e6 2062 fcgiwrap_1.1.0-14.dsc
 2e22a5dbc9128ae0fb943b0f869b1939b4c3281e 12036 fcgiwrap_1.1.0-14.debian.tar.xz
 5fcbd79df419e80d178e8c8923279789b034ef80 6764 fcgiwrap_1.1.0-14_amd64.buildinfo
Checksums-Sha256:
 62e1e2d44605b09142dcfad074d67a1f9dcbc6085cb92cab432037aed98225eb 2062 
fcgiwrap_1.1.0-14.dsc
 0553d9b7d4382d2ce0e61b0c50df1453be0da60dded23ad8e418a320a839ae63 12036 
fcgiwrap_1.1.0-14.debian.tar.xz
 18e77df86de8cd94d3fef0c32cbe9919db7dbb4053a2156ab82da5a402726c1c 6764 
fcgiwrap_1.1.0-14_amd64.buildinfo

Bug#1023569: marked as done (librte-net-af-xdp22 is empty after rebuild with libbpf 1.0.1)

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 20:46:13 +
with message-id 
and subject line Bug#1023569: fixed in dpdk 22.11.1-2
has caused the Debian Bug report #1023569,
regarding librte-net-af-xdp22 is empty after rebuild with libbpf 1.0.1
to be marked as done.

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

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


-- 
1023569: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023569
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: librte-net-af-xdp22
Version: 21.11-5
Severity: serious

$ dpkg -L librte-net-af-xdp22
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/librte-net-af-xdp22
/usr/share/doc/librte-net-af-xdp22/changelog.Debian.amd64.gz
/usr/share/doc/librte-net-af-xdp22/changelog.Debian.gz
/usr/share/doc/librte-net-af-xdp22/copyright
$
--- End Message ---
--- Begin Message ---
Source: dpdk
Source-Version: 22.11.1-2
Done: Luca Boccassi 

We believe that the bug you reported is fixed in the latest version of
dpdk, which is due to be installed in the Debian FTP archive.

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

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

Debian distribution maintenance software
pp.
Luca Boccassi  (supplier of updated dpdk package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 17 Dec 2022 13:59:11 +
Source: dpdk
Architecture: source
Version: 22.11.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian DPDK Maintainers 
Changed-By: Luca Boccassi 
Closes: 1021231 1023000 1023569
Changes:
 dpdk (22.11.1-2) unstable; urgency=medium
 .
   * d/watch: restrict to 22.11 LTS
   * Upload to unstable
 .
 dpdk (22.11.1-1) experimental; urgency=medium
 .
   * Update upstream source from tag 'upstream/22.11.1'
   * Drop Revert-drivers-omit-symbol-map-when-unneeded.patch, fixed
 upstream
   * Adjust symbols versions for PMDs for 22.11.1
 .
 dpdk (22.11-1) experimental; urgency=medium
 .
   * Update upstream source from tag 'upstream/22.11'
   * Drop docs-sort-files-lists-in-generator-scripts.patch, merged upstream
   * Install new dpdk-test-security-perf in dpdk-dev
   * Remove ~rc2-1 from d/*.symbols
   * Revert change to make all PMD functions public APIs
   * Drop obsolete NEWS file
 .
 dpdk (22.11~rc2-1) experimental; urgency=medium
 .
   [ Christian Ehrhardt ]
   * Update upstream source from tag 'upstream/22.11_rc2'
 this includes various fixes like (closes: #1023000):
 - vhost: fix header spanned across more than two descriptors
   (CVE-2022-2132)
 - vhost: discard too small descriptor chains
   (CVE-2022-2132)
 - net/mlx5: fix Rx queue recovery mechanism
   (CVE-2022-28199)
   * d/control: Bump to 22.11 ABI 23
   * d/p/disable_*_autopkgtest_fails.patch: update to match dpdk 22.11
   * d/control: new libs in 22.11-rc2
 - libs renamed baseband-acc100 -> baseband-acc
 - new libs: common-idpf, dma-dpaa2, net-gve, net-idpf, net-octeon-ep,
   raw-cnxk-gpio, regex-cn9k
 - removed libs: octeontx2-*, flow-classify, kni, librte-net-octeontx-ep23,
   raw-dpaa2-qdma23
   * d/*.symbols: update for 22.11
 - bump for ABI 23
 - register DPDK_23 in libs that were already stable before
 - rename to match the ABI change
 - add new libs in 22.11-rc2
 - remove older non symbol specific Missing statements
 - drop/update old ABI 22 references
 - d/*.symbols: drop removed libs
 - d/*.symbols: update changing symbols
   * avoid flaky test fails (closes: #1021231)
 - d/t/test-fastsuite: bump timeout 3->12
 - d/rules: bump timeout 3->6 (build had less issues and
   does more other things that consume time)
   * d/t/control: add jq to enable further tests
   * d/control: add libxdp-dev to libdpdk-dev as well to avoid pkconfig errors
 .
   [ Luca Boccassi ]
   * Add build-dep on libxdp-dev (closes: #1023569)
   * Backport patch to fix documentation reproducibility
   * Bump debhelper-compat to 13
Checksums-Sha1:
 157b60672721156a6d032a7edf35a270aacfa874 21251 dpdk_22.11.1-2.dsc
 b4796702f3ea6e4a6f689bf6729deeb4720b7370 69780 dpdk_22.11.1-2.debian.tar.xz
 451052b2cee415d53a14ed31649c5ab88f4476ea 9024 dpdk_22.11.1-2_source.buildinfo
Checksums-Sha256:
 

Bug#1023000: marked as done (dpdk: flaky autopkgtest on amd64 and ppc64el: pdump_autotest time out)

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 20:46:13 +
with message-id 
and subject line Bug#1023000: fixed in dpdk 22.11.1-2
has caused the Debian Bug report #1023000,
regarding dpdk: flaky autopkgtest on amd64 and ppc64el: pdump_autotest time out
to be marked as done.

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

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


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

Source: dpdk
Version: 20.11.5-1
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of your package. I noticed 
that it regularly fails on amd64 and ppc64el. From a cursory look it 
seems to have started around August 2022. The error seems to be 
different between different failures.


Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

Don't hesitate to reach out if you need help and some more information
from our infrastructure.

Paul

https://ci.debian.net/data/autopkgtest/testing/ppc64el/d/dpdk/27590240/log.gz

54/57 DPDK:fast-tests / pdump_autotest   RUNNING
>>> DPDK_TEST=pdump_autotest MALLOC_PERTURB_=178 
/tmp/autopkgtest-lxc.wxrxh9zu/downtmp/build.zmC/src/build/app/test/dpdk-test 
--no-huge -m 2048 --file-prefix=pdump_autotest
― ✀ 
―

EAL: Detected CPU lcores: 4
EAL: Detected NUMA nodes: 1
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /tmp/tmp.k8x9WW5het/dpdk/pdump_autotest/mp_socket
EAL: Physical addresses are unavailable, selecting IOVA as VA mode.
EAL: Selected IOVA mode 'VA'
EAL: WARNING! Base virtual address hint (0x101865000 != 0x7fff1f58) 
not respected!

EAL:This may cause issues with mapping memory into secondary processes
EAL: Probe PCI driver: net_virtio (1af4:1000) device: :00:01.0 
(socket 0)

eth_virtio_pci_init(): Failed to init PCI device
EAL: Requested device :00:01.0 cannot be used
APP: HPET is not enabled, using TSC as default timer
RTE>>pdump_autotest
IN PRIMARY PROCESS
pdump_init success
Running binary with 
argv[]:'/tmp/autopkgtest-lxc.wxrxh9zu/downtmp/build.zmC/src/build/app/test/dpdk-test' 
'-c' '1' '--proc-type=secondary' '--file-prefix=pdump_autotest'

EAL: Detected CPU lcores: 4
EAL: Detected NUMA nodes: 1
EAL: Detected static linkage of DPDK
EAL: Multi-process socket 
/tmp/tmp.k8x9WW5het/dpdk/pdump_autotest/mp_socket_16805_20758caec7b059

EAL: Physical addresses are unavailable, selecting IOVA as VA mode.
EAL: Selected IOVA mode 'VA'
EAL: Failed to open shared memory!
EAL: FATAL: Cannot get hugepage information.
EAL: Cannot get hugepage information.
EAL: Cannot destroy local memory map
EAL: Could not release memory subsystem data
IN PRIMARY PROCESS
pdump_init success
pdump_uninit success
Test OK
RTE>>DPDK:fast-tests / pdump_autotest time out (After 30.0 seconds)
――
54/57 DPDK:fast-tests / pdump_autotest   TIMEOUT30.06s 
killed by signal 15 SIGTERM


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: dpdk
Source-Version: 22.11.1-2
Done: Luca Boccassi 

We believe that the bug you reported is fixed in the latest version of
dpdk, which is due to be installed in the Debian FTP archive.

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

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

Debian distribution maintenance software
pp.
Luca Boccassi  (supplier of updated dpdk package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 17 Dec 2022 13:59:11 +
Source: dpdk
Architecture: source
Version: 22.11.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian DPDK Maintainers 
Changed-By: Luca Boccassi 
Closes: 1021231 1023000 1023569
Changes:
 dpdk (22.11.1-2) unstable; urgency=medium
 .
   * d/watch: restrict to 22.11 LTS
   * Upload to unstable
 .
 dpdk (22.11.1-1) experimental; urgency=medium
 .
   

Bug#1025658: marked as done (libboost-python1.74-dev: Python 3.11 changes break loading of boost-python using extensions)

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 20:41:15 +
with message-id 
and subject line Bug#1025658: fixed in boost1.74 1.74.0-18
has caused the Debian Bug report #1025658,
regarding libboost-python1.74-dev: Python 3.11 changes break loading of 
boost-python using extensions
to be marked as done.

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

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


-- 
1025658: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025658
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libboost-python1.74-dev
Version: 1.74.0-17+b2
Severity: serious
Tags: patch
Justification: Breaks reverse dependencies with Python 3.11
X-Debbugs-Cc: stu...@debian.org, debian-pyt...@lists.debian.org


Dear Maintainer,

Python 3.11 has changed some details around types and GC; boost's enum.cpp
needs modifying to cope. The result of this change is that trying to
load an extension compiled with Debian's boost 1.74 results in a C++
exception being thrown and, since not properly handled, the following
rather obscure error:

SystemError: initialization of $module raised unreported exception

Further details courtesy of Alastair McKinstry's debugging work are to
be found at

https://bugs.debian.org/1024911#14

So far, we've spotted this problem in:

cctbx: https://bugs.debian.org/1024859
ecflow: https://bugs.debian.org/1024911
python-pgmagick: https://bugs.debian.org/1023909

The attached patch is a (trivial) backport of the upstream change for
this:

https://github.com/boostorg/python/commit/a218babc8daee904a83f550fb66e5cb3f1cb3013

I've verified that the attached patch solves the Python 3.11 incompatibility
of python-pgmagick, allowing it to successfully build, meaning that it is
now able to load its boost-python extensions for the test suite.

regards
Stuart
Description: Tweak enum for python 3.11 compatibility
 Backport upstream patch for compatibility with python 3.11
Origin: 
https://github.com/boostorg/python/commit/a218babc8daee904a83f550fb66e5cb3f1cb3013
--- a/libs/python/src/object/enum.cpp
+++ b/libs/python/src/object/enum.cpp
@@ -119,7 +119,6 @@
 #if PY_VERSION_HEX < 0x0300
 | Py_TPFLAGS_CHECKTYPES
 #endif
-| Py_TPFLAGS_HAVE_GC
 | Py_TPFLAGS_BASETYPE,  /* tp_flags */
 0,  /* tp_doc */
 0,  /* tp_traverse */
--- End Message ---
--- Begin Message ---
Source: boost1.74
Source-Version: 1.74.0-18
Done: Anton Gladky 

We believe that the bug you reported is fixed in the latest version of
boost1.74, which is due to be installed in the Debian FTP archive.

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

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

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated boost1.74 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 17 Dec 2022 21:19:02 +0100
Source: boost1.74
Architecture: source
Version: 1.74.0-18
Distribution: unstable
Urgency: medium
Maintainer: Debian Boost Team 
Changed-By: Anton Gladky 
Closes: 1025658
Changes:
 boost1.74 (1.74.0-18) unstable; urgency=medium
 .
   * [754888a] Disable blhc-check in gitlab-ci.
   * [9e420e3] Fix loading of bosst-python 3.11 extensions. (Closes: #1025658)
   * [7aab252] Trim trailing whitespace.
Checksums-Sha1:
 352e6f279565ec7a5d869280a29079724ab4db88 9110 boost1.74_1.74.0-18.dsc
 01d10450d7f3342c8065d6ada9325c8ea2eddf8f 373372 
boost1.74_1.74.0-18.debian.tar.xz
 037c5cc13830e6131ffd42c34173a2e58ca21359 12534 
boost1.74_1.74.0-18_source.buildinfo
Checksums-Sha256:
 474e1c05c6f168adf89c483f678861c0d3559fa597679d4933c39937cce79cff 9110 
boost1.74_1.74.0-18.dsc
 7f95481afbdfeeac96087a0647930edbd332f4858bcd5afba2dd60998cdc9dd9 373372 
boost1.74_1.74.0-18.debian.tar.xz
 a12309c97769e21a6433faf07be532c2a8d7bd99886da3f0b3256796c03477ff 12534 
boost1.74_1.74.0-18_source.buildinfo
Files:
 58f4e02f98e5e96a115eb2b003467d43 9110 libs optional boost1.74_1.74.0-18.dsc
 eb5ec10e06150aba8877a4f5f9c50cd8 373372 libs optional 
boost1.74_1.74.0-18.debian.tar.xz
 6a6e77bf4efb55f7579a2b9566f4ffea 12534 libs optional 
boost1.74_1.74.0-18_source.buildinfo

-BEGIN PGP SIGNATURE-

Bug#1026337: marked as done (chake: autopkgtest regression: cannot load such file -- chake)

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 20:43:15 +
with message-id 
and subject line Bug#1026337: fixed in chake 0.90.1-1
has caused the Debian Bug report #1026337,
regarding chake: autopkgtest regression: cannot load such file -- chake
to be marked as done.

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

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


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

Source: chake
Version: 0.90-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
chake  from testing0.90-1
all others from testingfrom testing

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

Currently this regression is blocking the migration to testing [1]. Can 
you please investigate the situation and fix it?


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=chake

https://ci.debian.net/data/autopkgtest/testing/amd64/c/chake/29467384/log.gz

+ tmpdir=/tmp/autopkgtest-lxc.9hncv6o3/downtmp/autopkgtest_tmp
+ [ -z /tmp/autopkgtest-lxc.9hncv6o3/downtmp/autopkgtest_tmp ]
+ cd /tmp/autopkgtest-lxc.9hncv6o3/downtmp/autopkgtest_tmp
+ mkdir config
+ cd config
+ chake init[chef]
W: please install the \`wipe\` program for secure deletion, falling back 
to unlink(2)

create: Rakefile
create: cookbooks
create: cookbooks/basics
create: cookbooks/basics/default.rb
create: nodes.yaml
create: roles
create: roles/basic.rb
+ set +x
rake aborted!
ArgumentError: unknown keyword: :aliases
/usr/share/rubygems-integration/all/gems/chake-0.90/lib/chake/config.rb:16:in 
`block in '
/usr/share/rubygems-integration/all/gems/chake-0.90/lib/chake/config.rb:15:in 
`each'
/usr/share/rubygems-integration/all/gems/chake-0.90/lib/chake/config.rb:15:in 
`'
:85:in 
`require'
:85:in 
`require'
/usr/share/rubygems-integration/all/gems/chake-0.90/lib/chake.rb:5:in 
`'
:160:in 
`require'
:160:in 
`rescue in require'
:149:in 
`require'
/tmp/autopkgtest-lxc.9hncv6o3/downtmp/autopkgtest_tmp/config/Rakefile:1:in 
`'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/exe/rake:27:in 
`'


Caused by:
LoadError: cannot load such file -- chake
:85:in 
`require'
:85:in 
`require'
/tmp/autopkgtest-lxc.9hncv6o3/downtmp/autopkgtest_tmp/config/Rakefile:1:in 
`'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/exe/rake:27:in 
`'

(See full trace by running task with --trace)
autopkgtest [11:14:54]: test smoke-test



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: chake
Source-Version: 0.90.1-1
Done: Antonio Terceiro 

We believe that the bug you reported is fixed in the latest version of
chake, which is due to be installed in the Debian FTP archive.

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

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

Debian distribution maintenance software
pp.
Antonio Terceiro  (supplier of updated chake package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 18 Dec 2022 17:59:52 -0300
Source: chake
Architecture: source
Version: 0.90.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Antonio Terceiro 
Closes: 1026337
Changes:
 chake (0.90.1-1) unstable; urgency=medium
 .
   * New upstream version 0.90.1 (Closes: #1026337)
Checksums-Sha1:
 a7effa9b9cfbf482a3772339af4c1f032323f6a2 2046 chake_0.90.1-1.dsc
 76a4128d8c696f410cb3a47f969a3f2a1da5f8fc 29011 chake_0.90.1.orig.tar.gz
 5a86e58981ae28287069fcaf055dd427e1ea8208 4052 chake_0.90.1-1.debian.tar.xz
 0d334c700a7e0860aaea0c8d9ed161f139b971a6 10605 chake_0.90.1-1_amd64.buildinfo
Checksums-Sha256:
 98008b27d05b899ff24c56e310a166565e22f556f84025347d39606ddcf6ab0b 2046 
chake_0.90.1-1.dsc
 a9a4295a9cfc70eb4eccab4fd6d15c916076dd64d5c52f6a1f2baadaae0312b4 29011 

Bug#1021587: marked as done (caddy: FTBFS)

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 20:42:10 +
with message-id 
and subject line Bug#1021587: fixed in caddy 2.5.2-1
has caused the Debian Bug report #1021587,
regarding caddy: FTBFS
to be marked as done.

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

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


-- 
1021587: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021587
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: caddy
Version: 2.4.6-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi,

caddy recently started to FTBFS.

 debian/rules binary
dh binary --builddirectory=_build --buildsystem=golang --with=golang
   dh_update_autotools_config -O--builddirectory=_build -O--buildsystem=golang
   dh_autoreconf -O--builddirectory=_build -O--buildsystem=golang
   dh_auto_configure -O--builddirectory=_build -O--buildsystem=golang
   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/caddy-2.4.6'
dh_auto_build -- -ldflags '-X 
github.com/caddyserver/caddy/v2/cmd.version=2.4.6-2'
cd _build && go install -trimpath -v -p 3 -ldflags "-X 
github.com/caddyserver/caddy/v2/cmd.version=2.4.6-2" 
github.com/caddyserver/caddy/v2 github.com/caddyserver/caddy/v2/caddyconfig 
github.com/caddyserver/caddy/v2/caddyconfig/caddyfile github.com/caddyserver/ca
ddy/v2/caddyconfig/httpcaddyfile github.com/caddyserver/caddy/v2/caddytest 
github.com/caddyserver/caddy/v2/cmd github.com/caddyserver/caddy/v2/cmd/caddy 
github.com/caddyserver/caddy/v2/modules/caddyhttp 
github.com/caddyserver/caddy/v2/modules/caddyhttp/caddyauth github.c
om/caddyserver/caddy/v2/modules/caddyhttp/encode 
github.com/caddyserver/caddy/v2/modules/caddyhttp/encode/brotli 
github.com/caddyserver/caddy/v2/modules/caddyhttp/encode/gzip 
github.com/caddyserver/caddy/v2/modules/caddyhttp/encode/zstd 
github.com/caddyserver/caddy/v2/mo
dules/caddyhttp/fileserver 
github.com/caddyserver/caddy/v2/modules/caddyhttp/headers 
github.com/caddyserver/caddy/v2/modules/caddyhttp/map 
github.com/caddyserver/caddy/v2/modules/caddyhttp/push 
github.com/caddyserver/caddy/v2/modules/caddyhttp/requestbody github.com/cadd
yserver/caddy/v2/modules/caddyhttp/reverseproxy 
github.com/caddyserver/caddy/v2/modules/caddyhttp/reverseproxy/fastcgi 
github.com/caddyserver/caddy/v2/modules/caddyhttp/rewrite 
github.com/caddyserver/caddy/v2/modules/caddyhttp/standard 
github.com/caddyserver/caddy/v2/mod
ules/caddyhttp/templates github.com/caddyserver/caddy/v2/modules/caddypki 
github.com/caddyserver/caddy/v2/modules/caddypki/acmeserver 
github.com/caddyserver/caddy/v2/modules/caddytls 
github.com/caddyserver/caddy/v2/modules/caddytls/distributedstek 
github.com/caddyserver/
caddy/v2/modules/caddytls/standardstek 
github.com/caddyserver/caddy/v2/modules/filestorage 
github.com/caddyserver/caddy/v2/modules/logging 
github.com/caddyserver/caddy/v2/modules/manpages 
github.com/caddyserver/caddy/v2/modules/metrics 
github.com/caddyserver/caddy/v2/mod
ules/standard github.com/caddyserver/caddy/v2/notify
internal/unsafeheader
internal/cpu
internal/goarch
internal/abi
internal/goexperiment
internal/goos
runtime/internal/atomic
runtime/internal/math
internal/bytealg
runtime/internal/sys
runtime/internal/syscall
internal/race
sync/atomic
unicode
runtime
unicode/utf8
internal/itoa
math/bits
container/list
crypto/internal/subtle
math
crypto/subtle
crypto/internal/boring/sig
unicode/utf16
vendor/golang.org/x/crypto/cryptobyte/asn1
internal/nettrace
vendor/golang.org/x/crypto/internal/subtle
encoding
golang.org/x/net/internal/iana
golang.org/x/sys/internal/unsafeheader
google.golang.org/protobuf/internal/flags
google.golang.org/protobuf/internal/set
github.com/dgraph-io/badger/options
github.com/dgryski/go-farm
github.com/dgraph-io/badger/trie
golang.org/x/crypto/internal/alias
golang.org/x/net/html/atom
github.com/google/cel-go/common/operators
github.com/google/cel-go/common/overloads
golang.org/x/exp/constraints
golang.org/x/crypto/cryptobyte/asn1
github.com/lucas-clemente/quic-go/internal/utils/linkedlist
github.com/klauspost/compress
github.com/klauspost/compress/internal/cpuinfo
internal/reflectlite
sync
runtime/metrics
internal/testlog
math/rand
internal/singleflight
google.golang.org/protobuf/internal/pragma
internal/sysinfo
errors
sort
internal/oserror
io
syscall
strconv
bytes
hash
reflect
crypto
crypto/internal/nistec/fiat
time
path
context
io/fs
internal/syscall/unix
embed
internal/poll
internal/syscall/execenv
strings
encoding/binary
internal/fmtsort
os
crypto/cipher
crypto/internal/nistec
crypto/internal/boring
crypto/aes
crypto/des
fmt

Bug#1014694: marked as done (caddy.service: Failed to determine user credentials: No such process)

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 20:42:10 +
with message-id 
and subject line Bug#1014694: fixed in caddy 2.5.2-1
has caused the Debian Bug report #1014694,
regarding caddy.service: Failed to determine user credentials: No such process
to be marked as done.

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

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


-- 
1014694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014694
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: caddy
Version: 2.4.6-2
Severity: serious
Justification: package usable



Hello,


For me, on Debian Testing, doesn't Caddy start.

How I installed:

|stappers@hop:~
|$ wget 
http://ftp.nl.debian.org/debian/pool/main/c/caddy/caddy_2.4.6-2_amd64.deb
|--2022-07-10 11:15:44--  
http://ftp.nl.debian.org/debian/pool/main/c/caddy/caddy_2.4.6-2_amd64.deb
|Resolving ftp.nl.debian.org (ftp.nl.debian.org)... 2001:67c:2564:a120::21, 
130.89.149.21
|Connecting to ftp.nl.debian.org 
(ftp.nl.debian.org)|2001:67c:2564:a120::21|:80... connected.
|HTTP request sent, awaiting response... 200 OK
|Length: 8073508 (7.7M) [application/x-debian-package]
|Saving to: ‘caddy_2.4.6-2_amd64.deb’
|
|caddy_2.4.6-2_amd64.deb 100%[==>]  
 7.70M  --.-KB/sin 0.05s   
|
|2022-07-10 11:15:44 (141 MB/s) - ‘caddy_2.4.6-2_amd64.deb’ saved 
[8073508/8073508]
|
|stappers@hop:~
|$ sudo dpkg -i caddy_2.4.6-2_amd64.deb 
|Selecting previously unselected package caddy.
|(Reading database ... 26988 files and directories currently installed.)
|Preparing to unpack caddy_2.4.6-2_amd64.deb ...
|Unpacking caddy (2.4.6-2) ...
|Setting up caddy (2.4.6-2) ...
|Processing triggers for man-db (2.10.2-1) ...
|stappers@hop:~
|$ systemctl status caddy
|○ caddy.service - Caddy
| Loaded: loaded (/lib/systemd/system/caddy.service; disabled; vendor 
preset: enabled)
| Active: inactive (dead)
|   Docs: https://caddyserver.com/docs/
|stappers@hop:~
|$ 


What I have, including error message "Failed to determine user credentials":

|stappers@hop:~
|$ dpkg -l caddy
|Desired=Unknown/Install/Remove/Purge/Hold
|| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
||/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
|||/ Name   Version  Architecture Description
|+++-==---=
|ii  caddy  2.4.6-2  amd64Fast, lightweight web server with 
automatic HTTPS
|stappers@hop:~
|$ systemctl --failed
|  UNIT  LOAD   ACTIVE SUBDESCRIPTION
|● caddy.service loaded failed failed Caddy
|
|LOAD   = Reflects whether the unit definition was properly loaded.
|ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
|SUB= The low-level unit activation state, values depend on unit type.
|1 loaded units listed.
|stappers@hop:~
|$ systemctl status caddy
|× caddy.service - Caddy
| Loaded: loaded (/lib/systemd/system/caddy.service; disabled; vendor 
preset: enabled)
| Active: failed (Result: exit-code) since Sun 2022-07-10 11:16:23 UTC; 
42min ago
|   Docs: https://caddyserver.com/docs/
|Process: 189961 ExecStart=/usr/bin/caddy run --environ --config 
/etc/caddy/Caddyfile (code=exited, status=217/USER)
|   Main PID: 189961 (code=exited, status=217/USER)
|CPU: 2ms
|
|Jul 10 11:16:23 hop systemd[1]: Starting Caddy...
|Jul 10 11:16:23 hop systemd[189961]: caddy.service: Failed to determine user 
credentials: No such process
|Jul 10 11:16:23 hop systemd[189961]: caddy.service: Failed at step USER 
spawning /usr/bin/caddy: No such process
|Jul 10 11:16:23 hop systemd[1]: caddy.service: Main process exited, 
code=exited, status=217/USER
|Jul 10 11:16:23 hop systemd[1]: caddy.service: Failed with result 'exit-code'.
|Jul 10 11:16:23 hop systemd[1]: Failed to start Caddy.
|stappers@hop:~
|$ 


The unit file, without comment line, note the 'User=caddy' being present

|stappers@hop:~
|$ systemctl cat caddy | grep -v ^\#
|
|[Unit]
|Description=Caddy
|Documentation=https://caddyserver.com/docs/
|After=network.target network-online.target
|Requires=network-online.target
|
|[Service]
|Type=notify
|User=caddy
|Group=caddy
|ExecStart=/usr/bin/caddy run --environ --config /etc/caddy/Caddyfile
|ExecReload=/usr/bin/caddy reload --config /etc/caddy/Caddyfile
|TimeoutStopSec=5s
|LimitNOFILE=1048576
|LimitNPROC=512
|PrivateTmp=true
|ProtectSystem=full
|AmbientCapabilities=CAP_NET_BIND_SERVICE
|
|[Install]
|WantedBy=multi-user.target
|stappers@hop:~
|$ 

But user 'caddy' is not present.


|stappers@hop:~
|$ id caddy
|id: ‘caddy’: no such 

Bug#1013381: marked as done (buildbot: FTBFS with Sphinx 5.0, docutils 0.18: make[2]: *** [Makefile:67: singlehtml] Error 2)

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 20:41:46 +
with message-id 
and subject line Bug#1013381: fixed in buildbot 3.7.0-1
has caused the Debian Bug report #1013381,
regarding buildbot: FTBFS with Sphinx 5.0, docutils 0.18: make[2]: *** 
[Makefile:67: singlehtml] Error 2
to be marked as done.

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

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


-- 
1013381: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013381
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: buildbot
Version: 3.5.0-1
Severity: important
Tags: ftbfs
User: mity...@debian.org
Usertags: sphinx5.0

Hi,

buildbot fails to build with Sphinx 5.0 and docutils 0.18, both of which
are currently available in experimental.

Relevant part (hopefully):
> make[2]: Entering directory '/<>/master/docs'
> rm -rf _build/*
> sphinx-build -b html -d _build/doctrees  -q -W -j 8 . _build/html
> sphinx-build -b singlehtml -d _build/doctrees  -q -W -j 8 . _build/singlehtml
> enchant module import failed:
> No module named 'enchant'
> Spell checking disabled.
> enchant module import failed:
> No module named 'enchant'
> Spell checking disabled.
> 
> Warning, treated as error:
> extlinks: Sphinx-6.0 will require a caption string to contain exactly one 
> '%s' and all other '%' need to be escaped as '%%'.
> 
> Warning, treated as error:
> extlinks: Sphinx-6.0 will require a caption string to contain exactly one 
> '%s' and all other '%' need to be escaped as '%%'.
> make[2]: *** [Makefile:67: singlehtml] Error 2


The full build log is available from:
http://qa-logs.debian.net/2022/06/23/buildbot_3.5.0-1_unstable_sphinx-exp.log

Please see [1] for Sphinx changelog and [2] for Docutils changelog.

Also see [3] for the list of deprecated/removed APIs in Sphinx and possible
alternatives to them.

In case you have questions, please Cc sph...@packages.debian.org on reply.

[1]: https://www.sphinx-doc.org/en/master/changes.html
[2]: 
https://repo.or.cz/docutils.git/blob/refs/tags/docutils-0.18.1:/RELEASE-NOTES.txt
[3]: 
https://www.sphinx-doc.org/en/master/extdev/deprecated.html#dev-deprecated-apis

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=sphinx5.0;users=mity...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=sphinx5.0=mity...@debian.org=1=1=1=1#results

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
--- End Message ---
--- Begin Message ---
Source: buildbot
Source-Version: 3.7.0-1
Done: Robin Jarry 

We believe that the bug you reported is fixed in the latest version of
buildbot, which is due to be installed in the Debian FTP archive.

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

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

Debian distribution maintenance software
pp.
Robin Jarry  (supplier of updated buildbot package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 19 Dec 2022 17:31:02 +0100
Source: buildbot
Architecture: source
Version: 3.7.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Robin Jarry 
Closes: 1013381
Changes:
 buildbot (3.7.0-1) unstable; urgency=medium
 .
   * New upstream version 3.7.0 (Closes: #1013381)
Checksums-Sha1:
 c5cd85b6c0c2db48ed0ffa780b5bcd9520aea9d0 2693 buildbot_3.7.0-1.dsc
 210bf4be00941f27c24d5df5fd543211e1d75ed6 5158713 buildbot_3.7.0.orig.tar.gz
 8f2da419a7d9fc5c2021c65ec5e90a8caf098648 488 buildbot_3.7.0.orig.tar.gz.asc
 51fa6ce351410a6a2039a352587149c765ab0666 32120 buildbot_3.7.0-1.debian.tar.xz
 5c6dc1e7e774a6e19772742f7f2e7ea7597fadaa 9452 buildbot_3.7.0-1_source.buildinfo
Checksums-Sha256:
 7b049d261857306b0b6c3957199e38ddfd3c7c1129d8cb7b24b4a71afbf59aa8 2693 
buildbot_3.7.0-1.dsc
 8d8b519dd60374bc327f2f829cdffdaaca415d65c7a89abd9a89435e7b7f81b9 5158713 
buildbot_3.7.0.orig.tar.gz
 e15fa7d7623b48db8bc5ffc4b900c59ef7e24071fb7c20a41b7a33048da5c331 488 
buildbot_3.7.0.orig.tar.gz.asc
 5969850cf948a8f6193e8d13986ee79e8f5cc8a7867e7b1ee4ad779d15ff157e 32120 
buildbot_3.7.0-1.debian.tar.xz
 2bf61fd37da2c4bd2a4ca7a3048ce5d95220cce40aadac01cabe625b3662e5c7 9452 
buildbot_3.7.0-1_source.buildinfo
Files:
 

Bug#1026324: marked as done (asdf-astropy: autopkgtest regression: no tests ran)

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 20:37:17 +
with message-id 
and subject line Bug#1026324: fixed in asdf-astropy 0.3.0+github-1
has caused the Debian Bug report #1026324,
regarding asdf-astropy: autopkgtest regression: no tests ran
to be marked as done.

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

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


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

Source: asdf-astropy
Version: 0.3.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
asdf-astropy   from testing0.3.0-1
all others from testingfrom testing

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

Currently this regression is blocking the migration to testing [1]. Can 
you please investigate the situation and fix it?


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=asdf-astropy

https://ci.debian.net/data/autopkgtest/testing/amd64/a/asdf-astropy/29451632/log.gz

= test session starts 
==

platform linux -- Python 3.10.9, pytest-7.1.2, pluggy-1.0.0+repack
rootdir: /tmp/autopkgtest-lxc.y_r9z0vo/downtmp/autopkgtest_tmp
plugins: astropy-0.10.0, astropy-header-0.2.2, filter-subpackage-0.1.1, 
openfiles-0.5.0, cov-4.0.0, asdf-2.13.0, remotedata-0.3.3, mock-3.8.2, 
hypothesis-6.36.0, doctestplus-0.12.1, arraydiff-0.5.0

collected 0 items

 no tests ran in 0.17s 
=

autopkgtest [19:16:11]: test command1



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: asdf-astropy
Source-Version: 0.3.0+github-1
Done: Ole Streicher 

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

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

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

Debian distribution maintenance software
pp.
Ole Streicher  (supplier of updated asdf-astropy package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 19 Dec 2022 18:13:43 +0100
Source: asdf-astropy
Architecture: source
Version: 0.3.0+github-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Astronomy Team 

Changed-By: Ole Streicher 
Closes: 1026024 1026324
Changes:
 asdf-astropy (0.3.0+github-1) unstable; urgency=medium
 .
   * Switch uscan to github
   * Temporarily explicitly specify files to install (Closes: #1026024, 
#1026324)
Checksums-Sha1:
 2d32ed8e7496b69f6f23ee0462fffc2a72f089a8 2273 asdf-astropy_0.3.0+github-1.dsc
 3dc246e4012a7f001195d0c0a6b0900696b97521 62839 
asdf-astropy_0.3.0+github.orig.tar.gz
 e7b5c7fa7fefe9479fb3ec8982b657697160348d 2800 
asdf-astropy_0.3.0+github-1.debian.tar.xz
Checksums-Sha256:
 82b198eeb0222088171c263e3af255f3baf237a5f9df2ea0199154c1805c8416 2273 
asdf-astropy_0.3.0+github-1.dsc
 3a04fdbe81dcf01b661350b5fa3b58331ae574fcf56cfcd5db27d73384e345de 62839 
asdf-astropy_0.3.0+github.orig.tar.gz
 bf159e9b291e80ba55b2051cba1d2e582097bd61af83adf3cb1643fd80622f1d 2800 
asdf-astropy_0.3.0+github-1.debian.tar.xz
Files:
 66e31d1c82942d504d4bb6febb9f24b5 2273 python optional 
asdf-astropy_0.3.0+github-1.dsc
 87745c61872ea7098b7ea76e77b52d10 62839 python optional 
asdf-astropy_0.3.0+github.orig.tar.gz
 ff3fb5a6390a613d2368c3e1cb4477c7 2800 python optional 
asdf-astropy_0.3.0+github-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAmOgoCgACgkQcRWv0HcQ
3Pc6AA/+PaVeTfEdvyk8NGF6PIeU/YSlI7VXeZagUKZiRbZOqvmkdzuHCILXkwzW
3I6expSp9ConJI3SUW4dl5iG/FOdhCZT5xupy7g9IBzF59IekSJYViPufbNXEiLd
ktMRAtC4O8R/ylEmF3H5L2I76iDX6a/kHK+4cpWos7b8TsD1Oyi76ihjrESntn8H

Bug#1026256: marked as done (backuppc: BackupPC destroys its configuration when you "Save" in the admin web console)

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 20:37:44 +
with message-id 
and subject line Bug#1026256: fixed in backuppc 4.4.0-7
has caused the Debian Bug report #1026256,
regarding backuppc: BackupPC destroys its configuration when you "Save" in the 
admin web console
to be marked as done.

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

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


-- 
1026256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026256
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: backuppc
Version: 4.4.0-6+b1
Severity: important

Dear Maintainer,

after a recent update (probably to a Perl library), a bug in BackupPC leads to 
it destroying
its configuration files when saved from the BackupPC admin console.

On a system updated to the current versions of Debian Testing, I made minor 
modifications to
the configuration setup in the web admin console and pressed the "Save" button.

After that, any access to the admin console led to an internal error message. 
Restarting the
backuppc service fails from that point on as well.

Reason is that any configuration file saved this way is destroyed, as the 
brackets, [] and {},
required to store arrays or maps respectively, are replaced by ordinary 
brackets ().

CAUTION: For certain configuration files, this problem will *not* lead to 
backups reporting failure, but generating
faulty or incomplete backups due to misinterpretation of the config files, 
along with lack
of proper validation of the config files.

This bug is reported upstream: https://github.com/backuppc/backuppc/issues/466
A fix seems to be available and extremely easy to apply (not verified myself), 
but is  not
yet part of an upstream release.


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

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

Versions of packages backuppc depends on:
ii  adduser3.129
ii  apache2 [httpd]2.4.54-5
ii  apache2-utils  2.4.54-5
ii  backuppc-rsync 3.1.3.0-3
ii  bzip2  1.0.8-5+b1
ii  debconf [debconf-2.0]  1.5.80
ii  exim4  4.96-9
ii  exim4-daemon-light [mail-transport-agent]  4.96-9
ii  init-system-helpers1.65.2
ii  iputils-ping   3:20221126-1
ii  libarchive-zip-perl1.68-1
ii  libbackuppc-xs-perl0.62-2+b2
ii  libc6  2.36-6
ii  libcgi-pm-perl 4.54-1
ii  libfile-listing-perl   6.15-1
ii  libtime-parsedate-perl 2015.103-4
ii  lsb-base   11.5
ii  perl   5.36.0-4
ii  sysvinit-utils [lsb-base]  3.05-7
ii  ucf3.0043

Versions of packages backuppc recommends:
ii  libio-dirent-perl0.05-1.1+b2
ii  openssh-client [ssh-client]  1:9.1p1-1
ii  rrdtool  1.7.2-4+b6
ii  samba-common-bin 2:4.17.3+dfsg-3
ii  smbclient2:4.17.3+dfsg-3

Versions of packages backuppc suggests:
pn  certbot | acme-tiny | acmetool | dehydrated | lacme  
 | lecm | lego
pn  libscgi-perl 
ii  lynx [www-browser]   2.9.0dev.10-1+b1
ii  par2 0.8.1-3
ii  rsync3.2.6-4+b1
ii  w3m [www-browser]0.5.3+git20220429-1+b1

-- Configuration Files:
/etc/backuppc/apache.conf changed [not included]
/etc/backuppc/config.pl [Errno 13] Keine Berechtigung: '/etc/backuppc/config.pl'
/etc/backuppc/hosts [Errno 13] Keine Berechtigung: '/etc/backuppc/hosts'
/etc/backuppc/localhost.pl [Errno 13] Keine Berechtigung: 
'/etc/backuppc/localhost.pl'
/etc/default/backuppc changed [not included]

-- debconf information excluded
--- End Message ---
--- Begin Message ---
Source: backuppc
Source-Version: 4.4.0-7
Done: Axel Beckert 

We believe that the bug you reported is fixed in the latest 

Bug#1026024: marked as done (specutils: FTBFS, ModuleNotFoundError: No module named 'asdf_astropy.io')

[Debian Bug Tracking System]

Your message dated Mon, 19 Dec 2022 20:37:17 +
with message-id 
and subject line Bug#1026024: fixed in asdf-astropy 0.3.0+github-1
has caused the Debian Bug report #1026024,
regarding specutils: FTBFS, ModuleNotFoundError: No module named 
'asdf_astropy.io'
to be marked as done.

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

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


-- 
1026024: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026024
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: specutils
Version: 1.9.0-2
Severity: serious
Tags: ftbfs

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear maintainer,

your package has a FTBFS regression, presumably because of a missing
dependency. Relevant build log excerpt:


   dh_auto_test -O--buildsystem=pybuild
I: pybuild base:240: cd /<>/.pybuild/cpython3_3.11/build; 
python3.11 -m pytest --remote-data=none --doctest-rst
ERROR: while parsing the following warning configuration:

  ignore::astropy.wcs.wcs.FITSFixedWarning

This error occurred:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 1638, 
in parse_warning_filter
category: Type[Warning] = _resolve_warning_category(category_)
  
  File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 1676, 
in _resolve_warning_category
m = __import__(module, None, None, [klass])
^^^
  File "/usr/lib/python3/dist-packages/astropy/wcs/__init__.py", line 26, in 

from .wcs import *
  File "/usr/lib/python3/dist-packages/astropy/wcs/wcs.py", line 57, in 
from .wcsapi.fitswcs import FITSWCSAPIMixin, SlicedFITSWCS
  File "/usr/lib/python3/dist-packages/astropy/wcs/wcsapi/fitswcs.py", line 11, 
in 
from astropy.coordinates import SpectralCoord, Galactic, ICRS
  File "/usr/lib/python3/dist-packages/astropy/coordinates/__init__.py", line 
16, in 
from .builtin_frames import *
  File 
"/usr/lib/python3/dist-packages/astropy/coordinates/builtin_frames/__init__.py",
 line 29, in 
from .fk5 import FK5
  File 
"/usr/lib/python3/dist-packages/astropy/coordinates/builtin_frames/fk5.py", 
line 11, in 
from .utils import EQUINOX_J2000
  File 
"/usr/lib/python3/dist-packages/astropy/coordinates/builtin_frames/utils.py", 
line 16, in 
from astropy.utils import iers
  File "/usr/lib/python3/dist-packages/astropy/utils/iers/__init__.py", line 2, 
in 
from .iers import *
  File "/usr/lib/python3/dist-packages/astropy/utils/iers/iers.py", line 23, in 

from astropy.table import QTable, MaskedColumn
  File "/usr/lib/python3/dist-packages/astropy/table/__init__.py", line 75, in 

import asdf_astropy.io.connect
ModuleNotFoundError: No module named 'asdf_astropy.io'


E: pybuild pybuild:386: test: plugin distutils failed with: exit code=4: cd 
/<>/.pybuild/cpython3_3.11/build; python3.11 -m pytest 
--remote-data=none --doctest-rst
I: pybuild base:240: cd /<>/.pybuild/cpython3_3.10/build; 
python3.10 -m pytest --remote-data=none --doctest-rst
ERROR: while parsing the following warning configuration:

  ignore::astropy.wcs.wcs.FITSFixedWarning

This error occurred:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 1638, 
in parse_warning_filter
category: Type[Warning] = _resolve_warning_category(category_)
  File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 1676, 
in _resolve_warning_category
m = __import__(module, None, None, [klass])
  File "/usr/lib/python3/dist-packages/astropy/wcs/__init__.py", line 26, in 

from .wcs import *
  File "/usr/lib/python3/dist-packages/astropy/wcs/wcs.py", line 57, in 
from .wcsapi.fitswcs import FITSWCSAPIMixin, SlicedFITSWCS
  File "/usr/lib/python3/dist-packages/astropy/wcs/wcsapi/fitswcs.py", line 11, 
in 
from astropy.coordinates import SpectralCoord, Galactic, ICRS
  File "/usr/lib/python3/dist-packages/astropy/coordinates/__init__.py", line 
16, in 
from .builtin_frames import *
  File 
"/usr/lib/python3/dist-packages/astropy/coordinates/builtin_frames/__init__.py",
 line 29, in 
from .fk5 import FK5
  File 
"/usr/lib/python3/dist-packages/astropy/coordinates/builtin_frames/fk5.py", 
line 11, in 
from .utils import EQUINOX_J2000
  File 
"/usr/lib/python3/dist-packages/astropy/coordinates/builtin_frames/utils.py", 
line 16, in 
from astropy.utils import iers
  File "/usr/lib/python3/dist-packages/astropy/utils/iers/__init__.py", line 2, 
in 
from .iers import *
  File 

Bug#1026421: rclone should have a build dependency on golang >= 1.17

[Adam Buchbinder]

Package: rclone
Version: 1.60.1+dfsg-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: adam.buchbinder+deb...@gmail.com

Dear Maintainer,

I attempted to set up rclone 1.60 from Debian Testing on a Debian Stable
system. Apart from some versioned build dependencies, some of the packages
required Go features like unsafe.Slice (https://pkg.go.dev/unsafe#Slice),
added in go 1.17, or io.Discard (https://pkg.go.dev/io/ioutil#pkg-variables),
moved in go 1.16. Stable uses go 1.15, so this fails to build, and the
"golang-any" build dep doesn't allow the package to be built.

(I wound up moving 'testing' above 'stable' and upgrading the whole system,
but when I tried this I had 'stable' at priority 900 and 'testing' at 400.)

Adam Buchbinder

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (950, 'testing'), (900, 'stable'), (500, 'stable-updates'), (500, 
'stable-security'), (50, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-19-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
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 rclone depends on:
ii  libc6  2.36-6

rclone recommends no packages.

Versions of packages rclone suggests:
ii  fuse3 [fuse]  3.12.0-1

-- no debconf information

Processed: notfixed 1024180 in 3.0.2-2, fixed 997664 in 6.4.1+dfsg1-1, fixed 1023457 in 6.4.1+dfsg1-1 ...

[Debian Bug Tracking System]

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

> notfixed 1024180 3.0.2-2
Bug #1024180 {Done: David da Silva Polverari } 
[src:pngcheck] pngcheck: autopkgtest needs update for new version of zlib: 
warning on stderr
No longer marked as fixed in versions pngcheck/3.0.2-2.
> fixed 997664 6.4.1+dfsg1-1
Bug #997664 {Done: Drew Parsons } [src:sundials] sundials: 
apparent ABI bumps in sundials5 library packages
Marked as fixed in versions sundials/6.4.1+dfsg1-1.
> fixed 1023457 6.4.1+dfsg1-1
Bug #1023457 {Done: Drew Parsons } [src:sundials] 
sundials: FTBFS against hypre 2.26 and petsc 3.18
Marked as fixed in versions sundials/6.4.1+dfsg1-1.
> tags 1026382 + sid bookworm
Bug #1026382 [src:haskell-simple] Removal notice: obsolete
Added tag(s) sid and bookworm.
> found 1026369 0.0~git20170218.0.8372b90-9
Bug #1026369 [src:golang-github-unknwon-i18n] golang-github-unknwon-i18n: keep 
gitea deps out of testing
Marked as found in versions 
golang-github-unknwon-i18n/0.0~git20170218.0.8372b90-9.
> notfound 1026369 0.0~git20170218.0.8372b90-1
Bug #1026369 [src:golang-github-unknwon-i18n] golang-github-unknwon-i18n: keep 
gitea deps out of testing
No longer marked as found in versions 
golang-github-unknwon-i18n/0.0~git20170218.0.8372b90-1.
> tags 1026365 + sid bookworm
Bug #1026365 [src:golang-code.gitea-sdk] golang-code.gitea-git: unmaintained go 
library - keep out of testing
Added tag(s) sid and bookworm.
> tags 1026351 - bookworm sid
Bug #1026351 [src:pandas] pandas: autopkgtest on i386 needs update for new 
version of numpy: AssertionError
Removed tag(s) bookworm and sid.
> tags 1026349 - bookworm sid
Bug #1026349 [src:sasview] sasview: autopkgtest needs update for new version of 
numpy: module 'numpy' has no attribute 'asscalar'
Removed tag(s) bookworm and sid.
> notfound 1023972 3.22.1
Bug #1023972 [src:python-ase] python-ase: FTBFS with Python 3.11 due to 
pathlib.Path.__enter__() deprecation
The source 'python-ase' and version '3.22.1' do not appear to match any binary 
packages
No longer marked as found in versions python-ase/3.22.1.
> found 1023972 3.22.1-1
Bug #1023972 [src:python-ase] python-ase: FTBFS with Python 3.11 due to 
pathlib.Path.__enter__() deprecation
Marked as found in versions python-ase/3.22.1-1.
> tags 1026158 + sid bookworm
Bug #1026158 [src:haskell-ekg] Removal notice: obsolete
Added tag(s) bookworm and sid.
> tags 1026110 + sid bookworm
Bug #1026110 [xournal] xournal: FTBFS: Makefile:263: *** missing separator.  
Stop.
Added tag(s) sid and bookworm.
> tags 1026161 + sid bookworm
Bug #1026161 [src:haskell-ekg-json] Removal notice: obsolete
Added tag(s) sid and bookworm.
> found 1026094 1.6.1-1
Bug #1026094 {Done: Daniel Swarbrick } 
[prometheus-ipmi-exporter] prometheus-ipmi-exporter: autopkgtest/build fails 
due to API change in prometheus exporter-toolkit
Marked as found in versions prometheus-ipmi-exporter/1.6.1-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1023457: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023457
1023972: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023972
1024180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024180
1026094: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026094
1026110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026110
1026158: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026158
1026161: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026161
1026349: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026349
1026351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026351
1026365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026365
1026369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026369
1026382: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026382
997664: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997664
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Fixing metadata

[Debian Bug Tracking System]

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

> retitle 1010120 thrift: FTBFS in bullseye (expired certificates in test suite)
Bug #1010120 {Done: Laszlo Boszormenyi (GCS) } [src:thrift] 
thrift: FTBFS: dh_auto_test: error: make -j1 check "TESTSUITEFLAGS=-j1 
--verbose" VERBOSE=1 returned exit code 2
Changed Bug title to 'thrift: FTBFS in bullseye (expired certificates in test 
suite)' from 'thrift: FTBFS: dh_auto_test: error: make -j1 check 
"TESTSUITEFLAGS=-j1 --verbose" VERBOSE=1 returned exit code 2'.
> tags 1010120 + ftbfs patch
Bug #1010120 {Done: Laszlo Boszormenyi (GCS) } [src:thrift] 
thrift: FTBFS in bullseye (expired certificates in test suite)
Added tag(s) patch and ftbfs.
> severity 1010120 serious
Bug #1010120 {Done: Laszlo Boszormenyi (GCS) } [src:thrift] 
thrift: FTBFS in bullseye (expired certificates in test suite)
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: bug 1025825 is forwarded to https://github.com/joeyespo/grip/pull/360

[Debian Bug Tracking System]

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

> forwarded 1025825 https://github.com/joeyespo/grip/pull/360
Bug #1025825 [grip] ImportError: cannot import name 'safe_join' from 'flask'
Set Bug forwarded-to-address to 'https://github.com/joeyespo/grip/pull/360'.
> thanks
Stopping processing here.

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

Processed: severity of 1025825 is grave

[Debian Bug Tracking System]

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

> severity 1025825 grave
Bug #1025825 [grip] ImportError: cannot import name 'safe_join' from 'flask'
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Bug#1026387: samba-ad-provision: missing Breaks+Replaces: samba (<< 2:4.17.3+dfsg-4)

[Michael Tokarev]

19.12.2022 16:32, Michael Tokarev wrote:
..

Aargh.  This is due to my attempts to upload security update without waiting
for the NEW processing. It *had* proper Breaks+Replaces, but I removed it all
in an attempt to clean up new package introduction.


Actually it's a lie, it has nothing to do with that, it's plain stupid bug on 
my side.
Fixed now.

/mjt

Bug#1024438: mutter: autopkgtest regression: segfault in workspace-basic.metatest

[Bernhard Übelacker]

Am 18.12.22 um 16:58 schrieb Simon McVittie:


I was unable to reproduce this in a test VM, ...
..., but it is reproducible
on my laptop. Perhaps it's only reproducible if mutter has access to
some resource that my ssh login session to my test VM lacks, or perhaps
there's a race condition that makes this timing-dependent?



Hello Simon,
I forgot to mention that I had to add to
my qemu test VM this graphics configuration:

   -device virtio-vga-gl -display gtk,gl=on

Kind regards,
Bernhard

Bug#1026387: [Pkg-samba-maint] Bug#1026387: samba-ad-provision: missing Breaks+Replaces: samba (<< 2:4.17.3+dfsg-4)

[Michael Tokarev]

19.12.2022 14:29, Andreas Beckmann wrote:

Package: samba-ad-provision
Version: 2:4.17.3+dfsg-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.


Aargh.  This is due to my attempts to upload security update without waiting
for the NEW processing. It *had* proper Breaks+Replaces, but I removed it all
in an attempt to clean up new package introduction.  Meanwhile, it has been
accepted, and I re-did it again. And apparently missed this part.

Sigh.

Thank you!

/mjt

Processed: tagging 1024438

[Debian Bug Tracking System]

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

> tags 1024438 + pending
Bug #1024438 [src:mutter] mutter: autopkgtest regression: segfault in 
workspace-basic.metatest
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1026227: vagrant: Uninstallable in sid with VirtualBox 7.0.x

[Guillem Jover]

Hi!

On Sun, 2022-12-18 at 18:10:16 -0300, Antonio Terceiro wrote:
> On Fri, Dec 16, 2022 at 06:31:41PM +0100, Guillem Jover wrote:
> > Package: vagrant
> > Version: 2.2.19+dfsg-2
> > Severity: serious

> > Since virtualbox 7.0.4 got uploaded, vagrant is no longer installable
> > in Debian sid. I assume this will require packaging a new upstream
> > release to support the new virtualbox version 7.0.x series.
> 
> I cherry picked a patch from upstream that should solve the issue. The
> Breaks: restriction will now make the package installable with
> virtualbox 7.0, but I don't use virtualbox so I can't really test that
> it actually works.
> 
> Can you please try the package from git master?

I built it from git HEAD, installed and it seems to work fine now with
virtualbox 7.0.4, thanks! Even though I saw the following from the test
suite output:

  ,---
  # 
terminated with exception (report_on_exception is true):
  /tmp/vagrant/lib/vagrant/machine.rb:208:in `block in action': Vagrant 
attempted to call the action 'destroy' on the provider 
(Vagrant::Errors::UnimplementedProviderAction)
  '#', but this provider 
doesn't support this action. This
  is probably a bug in either the provider or the plugin calling this
  action, and should be reported.
  from /tmp/vagrant/lib/vagrant/environment.rb:614:in `lock'
  from /tmp/vagrant/lib/vagrant/machine.rb:201:in `call'
  from /tmp/vagrant/lib/vagrant/machine.rb:201:in `action'
  from /tmp/vagrant/lib/vagrant/batch_action.rb:86:in `block (2 levels) 
in run'
  `---

it didn't affect the test suite results nor the apparent operation with
the virtualbox plugin, so I guess this is completely unrelated.

Thanks,
Guillem

Processed: found 1012103 in 9.0.0+r42-1

[Debian Bug Tracking System]

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

> found 1012103 9.0.0+r42-1
Bug #1012103 [src:android-platform-external-doclava] 
android-platform-external-doclava: FTBFS with OpenJDK 17 due to com.sun.javadoc 
removal
Marked as found in versions android-platform-external-doclava/9.0.0+r42-1.
> thanks
Stopping processing here.

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

Processed: tagging 1024478

[Debian Bug Tracking System]

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

> tags 1024478 + pending
Bug #1024478 [ecryptfs-utils] ecryptfs-utils: FTBFS against libgpgme-dev >= 
1.18.0-2 [Cannot locate gpgme]
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1026387: samba-ad-provision: missing Breaks+Replaces: samba (<< 2:4.17.3+dfsg-4)

[Andreas Beckmann]

Package: samba-ad-provision
Version: 2:4.17.3+dfsg-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

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

  Preparing to unpack .../samba-ad-provision_2%3a4.17.4+dfsg-1_all.deb ...
  Unpacking samba-ad-provision (2:4.17.4+dfsg-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/samba-ad-provision_2%3a4.17.4+dfsg-1_all.deb (--unpack):
   trying to overwrite 
'/usr/share/samba/setup/ad-schema/AD_DS_Attributes__Windows_Server_2012_R2.ldf',
 which is also in package samba 2:4.17.3+dfsg-3
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/samba-ad-provision_2%3a4.17.4+dfsg-1_all.deb


cheers,

Andreas


samba=2:4.17.3+dfsg-3_samba-ad-provision=2:4.17.4+dfsg-1.log.gz
Description: application/gzip

Bug#1026386: orangeassassin: FTBFS with Python 3.11

[Andreas Beckmann]

Source: orangeassassin
Version: 1.0b-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Hi,

orangeassassin/experimental FTBFS with Python 3.11:

 fakeroot debian/rules clean
dh clean --with python3 --buildsystem=pybuild
   dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:240: python3.11 setup.py clean
error in OrangeAssassin setup command: 'tests_require' must be a string or list 
of strings containing valid project/version requirement specifiers; Parse error 
at "'+https:/'": Expected string_end
E: pybuild pybuild:386: clean: plugin distutils failed with: exit code=1: 
python3.11 setup.py clean
dh_auto_clean: error: pybuild --clean -i python{version} -p "3.11 3.10" 
returned exit code 13
make: *** [debian/rules:11: clean] Error 25


Andreas

Bug#1026383: Removal notice: obsolete

[Ilias Tsitsimpis]

Source: haskell-simple-templates
Version: 1.0.0-1
Severity: serious

I intend to remove the haskell-simple suite from Debian:

  * It FTBFS with latest aeson, no fix for more than 1 year (see
https://github.com/alevy/simple/issues/26)
  * Seems unmaintained: Home page doesn't work; Last upload more than 2
years ago
  * It's not part of the latest Stackage LTS

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias

Bug#1026382: Removal notice: obsolete

[Ilias Tsitsimpis]

Source: haskell-simple
Version: 1.0.0-1
Severity: serious

I intend to remove the haskell-simple-* suite from Debian:

  * It FTBFS with latest aeson, no fix for more than 1 year (see
https://github.com/alevy/simple/issues/26)
  * Seems unmaintained: Home page doesn't work; Last upload more than 2
years ago
  * It's not part of the latest Stackage LTS

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias

Processed: Re: Bug#1022189: Removal notice: obsolete

[Debian Bug Tracking System]

Processing control commands:

> clone -1 -2
Bug #1022189 [src:haskell-product-isomorphic] Removal notice: obsolete
Bug 1022189 cloned as bug 1026380
> reassign -2 ftp.debian.org
Bug #1026380 [src:haskell-product-isomorphic] Removal notice: obsolete
Bug reassigned from package 'src:haskell-product-isomorphic' to 
'ftp.debian.org'.
No longer marked as found in versions haskell-product-isomorphic/0.0.3.3-2.
Ignoring request to alter fixed versions of bug #1026380 to the same values 
previously set
> retitle -2 RM: haskell-product-isomorphic -- ROM; obsolete
Bug #1026380 [ftp.debian.org] Removal notice: obsolete
Changed Bug title to 'RM: haskell-product-isomorphic -- ROM; obsolete' from 
'Removal notice: obsolete'.
> severity -2 normal
Bug #1026380 [ftp.debian.org] RM: haskell-product-isomorphic -- ROM; obsolete
Severity set to 'normal' from 'serious'

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

Bug#1022189: Removal notice: obsolete

[Ilias Tsitsimpis]

Control: clone -1 -2
Control: reassign -2 ftp.debian.org
Control: retitle -2 RM: haskell-product-isomorphic -- ROM; obsolete
Control: severity -2 normal

Dear FTP masters, please remove haskell-product-isomorphic from unstable.

-- 
Ilias

Processed: Re: Bug#1022192: Removal notice: obsolete

[Debian Bug Tracking System]

Processing control commands:

> clone -1 -2
Bug #1022192 [src:haskell-relational-query] Removal notice: obsolete
Bug 1022192 cloned as bug 1026378
> reassign -2 ftp.debian.org
Bug #1026378 [src:haskell-relational-query] Removal notice: obsolete
Bug reassigned from package 'src:haskell-relational-query' to 'ftp.debian.org'.
No longer marked as found in versions haskell-relational-query/0.12.3.0-1.
Ignoring request to alter fixed versions of bug #1026378 to the same values 
previously set
> retitle -2 RM: haskell-relational-query -- ROM; obsolete
Bug #1026378 [ftp.debian.org] Removal notice: obsolete
Changed Bug title to 'RM: haskell-relational-query -- ROM; obsolete' from 
'Removal notice: obsolete'.
> severity -2 normal
Bug #1026378 [ftp.debian.org] RM: haskell-relational-query -- ROM; obsolete
Severity set to 'normal' from 'serious'

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

Processed: Re: Bug#1022190: Removal notice: obsolete

[Debian Bug Tracking System]

Processing control commands:

> clone -1 -2
Bug #1022190 [src:haskell-persistable-record] Removal notice: obsolete
Bug 1022190 cloned as bug 1026377
> reassign -2 ftp.debian.org
Bug #1026377 [src:haskell-persistable-record] Removal notice: obsolete
Bug reassigned from package 'src:haskell-persistable-record' to 
'ftp.debian.org'.
No longer marked as found in versions haskell-persistable-record/0.6.0.5-1.
Ignoring request to alter fixed versions of bug #1026377 to the same values 
previously set
> retitle -2 RM: haskell-persistable-record -- ROM; obsolete
Bug #1026377 [ftp.debian.org] Removal notice: obsolete
Changed Bug title to 'RM: haskell-persistable-record -- ROM; obsolete' from 
'Removal notice: obsolete'.
> severity -2 normal
Bug #1026377 [ftp.debian.org] RM: haskell-persistable-record -- ROM; obsolete
Severity set to 'normal' from 'serious'

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

Bug#1022192: Removal notice: obsolete

[Ilias Tsitsimpis]

Control: clone -1 -2
Control: reassign -2 ftp.debian.org
Control: retitle -2 RM: haskell-relational-query -- ROM; obsolete
Control: severity -2 normal

Dear FTP masters, please remove haskell-relational-query from unstable.

-- 
Ilias

Bug#1022190: Removal notice: obsolete

[Ilias Tsitsimpis]

Control: clone -1 -2
Control: reassign -2 ftp.debian.org
Control: retitle -2 RM: haskell-persistable-record -- ROM; obsolete
Control: severity -2 normal

Dear FTP masters, please remove haskell-persistable-record from unstable.

-- 
Ilias

Bug#1025370: ntcard: ftbfs with nthash 2.3.0

[Nilesh Patra]

Control: severity -1 important

For the time being, I have vendored the relevant header files
from nthash in ntcard itseld and patched the buildsystem a bit to
pick those up.

Ans so, for now, ntcard would "build" (with a compromise) and so
I am downgrading the severity.

-- 
Best,
Nilesh


signature.asc
Description: PGP signature

Processed: Re: ntcard: ftbfs with nthash 2.3.0

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #1025370 [src:ntcard] ntcard: ftbfs with nthash 2.3.0
Severity set to 'important' from 'serious'

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