Bug#1032048: marked as pending in node-d3-dsv

[Yadd]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/js-team/node-d3-dsv/-/commit/4a74d6cf36bca129ab0186eccb4c0248870f61fe


Fix links

Closes: #1032048


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1032048

Processed: Bug#1032048 marked as pending in node-d3-dsv

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1032048 [d3-dsv-tools] d3-dsv-tools: Dangling symlinks in /usr/bin/
Ignoring request to alter tags of bug #1032048 to the same tags previously set

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

Processed: fixed 1032048 in 3.0.1+~3.0.0-1

[Debian Bug Tracking System]

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

> fixed 1032048 3.0.1+~3.0.0-1
Bug #1032048 [d3-dsv-tools] d3-dsv-tools: Dangling symlinks in /usr/bin/
There is no source info for the package 'd3-dsv-tools' at version 
'3.0.1+~3.0.0-1' with architecture ''
Unable to make a source version for version '3.0.1+~3.0.0-1'
Marked as fixed in versions 3.0.1+~3.0.0-1.
> thanks
Stopping processing here.

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

Bug#1032048: marked as pending in node-d3-dsv

[Yadd]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/js-team/node-d3-dsv/-/commit/4a74d6cf36bca129ab0186eccb4c0248870f61fe


Fix links

Closes: #1032048


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1032048

Processed: Bug#1032048 marked as pending in node-d3-dsv

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1032048 [d3-dsv-tools] d3-dsv-tools: Dangling symlinks in /usr/bin/
Added tag(s) pending.

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

Processed: tagging 1028454

[Debian Bug Tracking System]

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

> tags 1028454 - patch
Bug #1028454 [nsscache] nsscache: build-depends on python3-mox3, to be removed 
from Debian
Removed tag(s) patch.
> thanks
Stopping processing here.

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

Bug#1026539: Bug#1027215: Bug#1026539: How much do we lose if we remove theano (+keras, deepnano, invesalius)?

[Andreas Tille]

Hi Rebecca,

Am Thu, Mar 02, 2023 at 09:00:14PM + schrieb Rebecca N. Palmer:
> 
> 1.1.2 isn't the latest version, just the latest that calls the module theano
> rather than aesara.  (I chose it to package because I didn't want to fully
> break compatibility, then abandoned it because I didn't like how much it did
> break.)

Ahh, so aesara is not really a "fork" but a "rename"?
 
> > If it would have build smoothly on all architectures, yes.
> 
> If you wouldn't want to do this work if it can't get into bookworm (possibly
> because you'd prefer to package 2.0 as aesara if you have to wait until
> trixie anyway), you might want to ask them first.

I admit I do not want to take over theano / aesara.  I simply wanted to
see what I can do to lend a helping hand on packages that are not yet
removed from testing.  I naively assumed that just numpy issues should
be solvable.
 
> > But we have
> > the first trouble on arm64[1]
> Sorry - I forgot that theano skips most of its tests on Salsa-CI (because
> there's enough of them to take several hours), which is probably why it
> "passed" that but failed the full build.
> 
> Given how many failures there are (everywhere), I don't consider this worth
> fixing, but you are of course free to disagree.

Considering my practical experience now I agree.

> (If you're planning to xfail tests, note that I consider *wrong-answer* bugs
> (though not crash bugs) in this kind of package to be RC.  I haven't checked
> whether we currently have any.)

I admit I'll give up here on that package where we decided that the
loose we have is acceptable.

Kind regards and thanks a lot for your work on this package as well as
your hints in this mail

 Andreas.

-- 
http://fam-tille.de

Bug#1032289: Keep out of the Bookworm release

[duck]

Source: libdisplay-info
Severity: serious

The library is new and just starting to be stable, with no rdepends yet, 
so even if the binary is useful to get info I'm not sure it's worth 
maintaining a full release cycle.


\_o<

--
Marc Dequènes

Bug#1020164: marked as done (clojure-mode: FTBFS with emacs 28: 24 tests failed)

[Debian Bug Tracking System]

Your message dated Fri, 03 Mar 2023 05:03:57 +
with message-id 
and subject line Bug#1020164: fixed in clojure-mode 5.10.0-4
has caused the Debian Bug report #1020164,
regarding clojure-mode: FTBFS with emacs 28: 24 tests failed
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.)


-- 
1020164: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020164
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: clojure-mode
Version: 5.10.0-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220917 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules build
> dh build --with elpa
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
>dh_elpa_test
>   emacs -batch -Q -l package --eval "(add-to-list 'package-directory-list 
> \"/usr/share/emacs/site-lisp/elpa\")" --eval "(add-to-list 
> 'package-directory-list \"/usr/share/emacs/site-lisp/elpa-src\")" -f 
> package-initialize -L . -L test --eval "(load-file \"test/test-helper.el\")" 
> -l test/test-helper.el -l test/clojure-mode-indentation-test.el -l 
> test/clojure-mode-sexp-test.el -l test/clojure-mode-font-lock-test.el -l 
> test/clojure-mode-syntax-test.el -l test/clojure-mode-util-test.el --eval 
> \(ert-run-tests-batch-and-exit\)
> Loading /<>/test/test-helper.el (source)...
> Running tests on Emacs 28.1
> Running tests on Emacs 28.1
> clojure-mode.el: Warning: ‘project-roots’ is an obsolete generic function (as 
> of 0.3.0); use ‘project-root’ instead.
> Running 106 tests (2022-09-17 20:05:39+, selector ‘t’)
> Indenting region... 
> Indenting region...done
>passed1/106  clojure-align-remove-extra-commas (0.019116 sec)
>passed2/106  clojure-allowed-collection-tags (0.000432 sec)
>passed3/106  clojure-find-ns-test (0.000180 sec)
>passed4/106  clojure-mode-syntax-table/camelcase (0.004129 sec)
>passed5/106  clojure-mode-syntax-table/characters (0.001091 sec)
>passed6/106  clojure-mode-syntax-table/comment-macros (0.000540 sec)
>passed7/106  clojure-mode-syntax-table/custom-def-with-special-chars1 
> (0.000215 sec)
>passed8/106  clojure-mode-syntax-table/custom-def-with-special-chars2 
> (0.000273 sec)
>passed9/106  clojure-mode-syntax-table/custom-def-with-special-chars3 
> (0.000227 sec)
>passed   10/106  clojure-mode-syntax-table/dynamic-var (0.001293 sec)
>passed   11/106  clojure-mode-syntax-table/false (0.001223 sec)
>passed   12/106  clojure-mode-syntax-table/fn (0.000369 sec)
>passed   13/106  
> clojure-mode-syntax-table/fontify-let-when-while-type-forms (0.000565 sec)
>passed   14/106  clojure-mode-syntax-table/function-def (0.003711 sec)
>passed   15/106  clojure-mode-syntax-table/keyword-allowed-chars (0.000220 
> sec)
>passed   16/106  clojure-mode-syntax-table/keyword-disallowed-chars 
> (0.025015 sec)
>passed   17/106  clojure-mode-syntax-table/keyword-meta (0.000216 sec)
>passed   18/106  clojure-mode-syntax-table/kw-camelcase (0.003733 sec)
>passed   19/106  clojure-mode-syntax-table/kw-mixedcase (0.002758 sec)
>passed   20/106  clojure-mode-syntax-table/kw-namespaced (0.020145 sec)
>passed   21/106  clojure-mode-syntax-table/kw-oneword (0.002759 sec)
>passed   22/106  clojure-mode-syntax-table/kw-segment (0.002650 sec)
>passed   23/106  clojure-mode-syntax-table/kw-verycomplex (0.023073 sec)
>passed   24/106  clojure-mode-syntax-table/lambda-params (0.000244 sec)
>passed   25/106  clojure-mode-syntax-table/mixedcase (0.002946 sec)
>passed   26/106  clojure-mode-syntax-table/namespace (0.019926 sec)
>passed   27/106  clojure-mode-syntax-table/namespaced-def (0.000402 sec)
>passed   28/106  clojure-mode-syntax-table/nil (0.000319 sec)
>passed   29/106  clojure-mode-syntax-table/oneword (0.003017 sec)
>passed   30/106  clojure-mode-syntax-table/refer-ns (0.000332 sec)
>passed   31/106  clojure-mode-syntax-table/segment (0.002983 sec)
>passed   32/106  clojure-mode-syntax-table/stuff-in-backticks (0.020070 
> sec)
>passed   33/106  clojure-mode-syntax-table/true (0.000233 sec)
>passed   34/106  clojure-mode-syntax-table/type-def (0.000222 sec)
>passed   35/106  clojure-mode-syntax-table/variable-def (0.000356 sec)
>passed   36/106  clojure-mode-syntax-table/verycomplex (0.003746 sec)
>passed   37/106  clojure-namespace-name-regex-test (0.000155 sec)
>passed   38/106  cloj

Bug#1032048: d3-dsv-tools: Dangling symlinks in /usr/bin/

[Pirate Praveen]

On Mon, 27 Feb 2023 00:51:52 +0100 Axel Beckert  wrote:
> Package: d3-dsv-tools
> Version: 1.1.1-8
> Severity: grave
> Justification: renders package unusable
>
> $ symlinks -tv /usr/bin* | fgrep dangling
> dangling: /usr/bin/csv2json -> ../share/nodejs/d3-dsv/bin/dsv2json.js
> dangling: /usr/bin/csv2tsv -> ../share/nodejs/d3-dsv/bin/dsv2dsv.js
> dangling: /usr/bin/dsv2dsv -> ../share/nodejs/d3-dsv/bin/dsv2dsv.js
> dangling: /usr/bin/json2csv -> ../share/nodejs/d3-dsv/bin/json2dsv.js
> dangling: /usr/bin/json2dsv -> ../share/nodejs/d3-dsv/bin/json2dsv.js
> dangling: /usr/bin/tsv2csv -> ../share/nodejs/d3-dsv/bin/dsv2dsv.js
> dangling: /usr/bin/json2tsv -> ../share/nodejs/d3-dsv/bin/json2dsv.js
> dangling: /usr/bin/dsv2json -> ../share/nodejs/d3-dsv/bin/dsv2json.js
> dangling: /usr/bin/tsv2json -> ../share/nodejs/d3-dsv/bin/dsv2json.js
>
> Looking at where those files actually might be, I figured that the
> symlinks probably should point to the same target without the .js
> suffix — or that those files need to be renamed:
>
> /usr/share/nodejs/d3-dsv/bin/dsv2dsv
> /usr/share/nodejs/d3-dsv/bin/dsv2json
> /usr/share/nodejs/d3-dsv/bin/json2dsv

debian/nodejs/links should be modified to drop the .js suffix.



since master branch is used for experimental, a new branch for bookworm 
should be created from debian/1.1.1-8 tag


> -- System Information:
> Debian Release: bookworm/sid
>   APT prefers testing
>   APT policy: (600, 'testing')
> merged-usr: yes
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 6.1.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
> Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not 
set

> Shell: /bin/sh linked to /bin/dash
> Init: sysvinit (via /sbin/init)
> LSM: AppArmor: enabled
>
> Versions of packages d3-dsv-tools depends on:
> ii  node-d3-dsv  1.1.1-8
> ii  nodejs   18.13.0+dfsg1-1
>
> d3-dsv-tools recommends no packages.
>
> d3-dsv-tools suggests no packages.
>
> -- no debconf information
>
>

Bug#1004626: forked-daapd: FTBFS with ffmpeg 5.0

[Nicholas D Steeves]

Steve Langasek  writes:

> Package: forked-daapd
> Version: 26.4+dfsg1-2
> Followup-For: Bug #1004626
> User: ubuntu-de...@lists.ubuntu.com
> Usertags: origin-ubuntu kinetic ubuntu-patch
> Control: tags -1 patch
>
> Please find attached a debdiff that cherry-picks the two commits from
> upstream necessary for forked-daapd to build against ffmpeg 5.0.
>
> This change has been uploaded to Ubuntu for the ffmpeg 5.0 transition.
>

Hi Sébastien,

This RC (release critical) bug will is preventing forked-daapd from
being part of Debian 12 (bookworm).  If you'd like to join the
Multimedia Team or salvage the package, is this key bug.  Uploading this
package with a targeted fix also meets the criteria for the freeze;
however, forked-daapd isn't in testing, and there is "no re-entry to
testing" by the time an upload today would migrate to testing.  I'm not
sure if the release team would make an exception, but I'd hope that they
would if it means giving someone new a chance to fix software they care
about :)

Thank you for the patch Steve!

Regards,
Nicholas


signature.asc
Description: PGP signature

Bug#1032287: python-qrencode: diff for NMU version 1.2-5.1

[anarcat]

Control: tags 1032287 + pending

Dear maintainer,

I've prepared an NMU for python-qrencode (versioned as 1.2-5.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards.


-- 
diff -Nru python-qrencode-1.2/debian/changelog python-qrencode-1.2/debian/changelog
--- python-qrencode-1.2/debian/changelog	2019-08-30 08:31:57.0 -0400
+++ python-qrencode-1.2/debian/changelog	2023-03-02 22:19:32.0 -0500
@@ -1,3 +1,10 @@
+python-qrencode (1.2-5.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * fix crash in Python 3.10 (Closes: #1032287)
+
+ -- Antoine Beaupré   Thu, 02 Mar 2023 22:19:32 -0500
+
 python-qrencode (1.2-5) unstable; urgency=medium
 
   * Drop Python 2 support (Closes: #938112).
diff -Nru python-qrencode-1.2/debian/patches/python3-10-port.patch python-qrencode-1.2/debian/patches/python3-10-port.patch
--- python-qrencode-1.2/debian/patches/python3-10-port.patch	1969-12-31 19:00:00.0 -0500
+++ python-qrencode-1.2/debian/patches/python3-10-port.patch	2023-03-02 22:19:28.0 -0500
@@ -0,0 +1,13 @@
+Description: adapt to changes in Python 3.10
+Author: anar...@debian.org
+Origin: Debian
+Forwarded: no
+Last-Update: 2023-03-03
+
+--- python-qrencode-1.2.orig/qr_encode.c
 python-qrencode-1.2/qr_encode.c
+@@ -1,3 +1,4 @@
++#define PY_SSIZE_T_CLEAN
+ #include 
+ #include 
+ #include 
diff -Nru python-qrencode-1.2/debian/patches/series python-qrencode-1.2/debian/patches/series
--- python-qrencode-1.2/debian/patches/series	1969-12-31 19:00:00.0 -0500
+++ python-qrencode-1.2/debian/patches/series	2023-03-02 22:18:59.0 -0500
@@ -0,0 +1 @@
+python3-10-port.patch


signature.asc
Description: PGP signature

Processed: python-qrencode: diff for NMU version 1.2-5.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1032287 + pending
Bug #1032287 [python3-qrencode] SystemError: PY_SSIZE_T_CLEAN macro must be 
defined for '#' formats
Added tag(s) pending.

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

Processed: bug 1032287 is forwarded to https://github.com/Arachnid/pyqrencode/issues/13, tagging 1032287

[Debian Bug Tracking System]

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

> forwarded 1032287 https://github.com/Arachnid/pyqrencode/issues/13
Bug #1032287 [python3-qrencode] SystemError: PY_SSIZE_T_CLEAN macro must be 
defined for '#' formats
Set Bug forwarded-to-address to 
'https://github.com/Arachnid/pyqrencode/issues/13'.
> tags 1032287 + patch
Bug #1032287 [python3-qrencode] SystemError: PY_SSIZE_T_CLEAN macro must be 
defined for '#' formats
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#1032287: SystemError: PY_SSIZE_T_CLEAN macro must be defined for '#' formats

[Antoine Beaupre]

Package: python3-qrencode
Version: 1.2-5+b8
Severity: grave
X-Debbugs-Cc: debian-pyt...@lists.debian.org

It looks like the qrencode Python library is currently unusable in
Debian bookworm. Here's a simple example:

anarcat@angela:paperbackup$ python3 -c 'import qrencode ; version, size, data = 
qrencode.encode(b"test")'
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/qrencode/__init__.py", line 47, in encode
version, size, data = _encode(data, version, level, hint, True)
  ^
SystemError: PY_SSIZE_T_CLEAN macro must be defined for '#' formats
anarcat@angela:paperbackup[1]$

According to a casual search on the web, it looks like the extension
needs to be recompiled / patched for Python 3.10:

https://stackoverflow.com/a/71019907

Quote:

> On 3.10 any module(s) that use the # variant when parsing arguments
> need to have a #define PY_SSIZE_T_CLEAN before including Python.h.

So this could be as simple as:

--- python-qrencode-1.2.orig/qr_encode.c
+++ python-qrencode-1.2/qr_encode.c
@@ -1,3 +1,4 @@
+#define PY_SSIZE_T_CLEAN
 #include 
 #include 
 #include 

Will test this out soon.

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

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

Versions of packages python3-qrencode depends on:
ii  libc6 2.36-8
ii  libqrencode4  4.1.1-1
ii  python3   3.11.2-1

python3-qrencode recommends no packages.

python3-qrencode suggests no packages.

-- no debconf information

Bug#1001144: Info received (odbc-mdbtools: Missing dependency on odbcinst)

[Wookey]

The attached patch is confirmed as fixing the problem.

Wookey
-- 
Principal hats:  Debian, Wookware, ARM
http://wookware.org/
diff -Nru mdbtools-1.0.0+dfsg/debian/changelog mdbtools-1.0.0+dfsg/debian/changelog
--- mdbtools-1.0.0+dfsg/debian/changelog	2021-10-31 14:01:12.0 +
+++ mdbtools-1.0.0+dfsg/debian/changelog	2023-03-02 20:59:21.0 +
@@ -1,3 +1,10 @@
+mdbtools (1.0.0+dfsg-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add dependency on obdcinst for odbc-mdbtools (Closes:#1001144)
+
+ -- Wookey   Thu, 02 Mar 2023 20:59:21 +
+
 mdbtools (1.0.0+dfsg-1) unstable; urgency=medium
 
   * New upstream release:
diff -Nru mdbtools-1.0.0+dfsg/debian/control mdbtools-1.0.0+dfsg/debian/control
--- mdbtools-1.0.0+dfsg/debian/control	2021-10-31 13:56:49.0 +
+++ mdbtools-1.0.0+dfsg/debian/control	2023-03-02 20:59:17.0 +
@@ -76,7 +76,7 @@
 Multi-Arch: same
 Section: libs
 Pre-Depends: ${misc:Pre-Depends}
-Depends: ${misc:Depends}, ${shlibs:Depends}
+Depends: ${misc:Depends}, ${shlibs:Depends}, odbcinst
 Recommends: libodbc1
 Breaks: libiodbc2 (<< 3.52.7-2+deb7u1),
 libmdbodbc1 (<< 0.7.1-1~),


signature.asc
Description: PGP signature

Bug#1029821: change gnome-desktop's default choice of Japanese input methods for Debian

[James Addison]

Package: libgnome-desktop-4-2
Followup-For: Bug #1029821
X-Debbugs-Cc: s...@debian.org, z...@debian.org, ken...@xdump.org, 
yy.y.ja...@gmail.com, iwama...@debian.org, gunna...@debian.org, 
debian-i...@lists.debian.org, debian-japan...@lists.debian.org, 
m...@packages.debian.org, ibus-an...@packages.debian.org

After attempting a re-install with Japanese language defaults (to try to make
sure that I understand the problem), I'd like to check some more details.

If I'm on the wrong path, then I'll stop adding further comments for a while to
let you all and others find a better solution.

On Thu, 2 Mar 2023 15:50:22 +, Simon wrote:
> When there are patches available for whatever we decide is the right
> behaviour, you shouldn't need to walk through the whole install process.

This is true.  However, these comments seem particularly relevant:

On Thu, 2 Mar 2023 18:39:04 +0800, Shengjing wrote:
> I'm not a Japanese user. But I've been frustrated in the last few days
> of the Bullseye release, when Gnome's upstream choice conflicts with
> Debian's tasksel.

On Thu, 2 Mar 2023 22:07:16 +0900, Kentaro wrote:
> The problem is conflicting with task-japanese-gnome-desktop's recommends.


Based on those, it seems to me that part -- perhaps most -- of the problem is
the 'task-japanese-gnome-desktop' entry[1] for bookworm is currently:

  ibus-mozc | ibus-anthy


So I believe mozc is selected as the first dep-satisfying option during a fresh
Debian bookworm plus GNOME install.  Please correct me if I'm wrong about that.


That conflicts with the default that 'gnome-initial-setup' configures, namely
the 'anthy' input method -- explaining the patch that Yoshino-san provided.


So: regardless of whether we choose 'mozc' or 'anthy', we should try to match
the input method that we install by default with the input method that is
configured by 'gnome-initial-setup'.

(the idea to query the available input engines at selection-time is
theoretically a much more robust approach.. but it could take longer for that
to become available and be tested thoroughly, and as noted previously in the
thread, the default install of GNOME desktop for Japanese language input is
known broken today)


Note: if everyone else understood all that already, and I'm only finally
catching up with you all now, then my apologies for being slow.  It didn't seem
clear to me previously what the core of the problem here is.

[1] - https://sources.debian.org/src/tasksel/3.71/debian/control/#L1462

Bug#1032166: do not release in bookworm

[Petter Reinholdtsen]

[Ana Guerrero Lopez]
> Please, keep debian-timeline out of bookworm, the installed HTML doesn't
> show the timeline like it should so the package is useless.

Are you talking about the issue in #655664?
-- 
Happy hacking
Petter Reinholdtsen

Processed: tagging 1032032, tagging 1031963, tagging 1031832

[Debian Bug Tracking System]

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

> tags 1032032 + sid bookworm
Bug #1032032 [src:fenix-plugins] FTBFS: error: AM_INIT_AUTOMAKE expanded 
multiple times
Added tag(s) sid and bookworm.
> tags 1031963 + sid bookworm
Bug #1031963 [src:zsnes] FTBFS: error: ISO C++17 does not allow dynamic 
exception specifications
Added tag(s) bookworm and sid.
> tags 1031832 + sid bookworm
Bug #1031832 {Done: Étienne Mollier } [python3-vispy] 
python3-vispy: import fails: AttributeError: module 'numpy' has no attribute 
'bool'
Added tag(s) bookworm and sid.
> thanks
Stopping processing here.

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

Bug#1032124: marked as done (pd-ableton-link: FTBFS on armel: fatal error: gnu/stubs-hard.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Thu, 02 Mar 2023 22:37:18 +
with message-id 
and subject line Bug#1032124: fixed in pd-ableton-link 0.6~ds0-6
has caused the Debian Bug report #1032124,
regarding pd-ableton-link: FTBFS on armel: fatal error: gnu/stubs-hard.h: No 
such file or directory
to be marked as done.

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

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


-- 
1032124: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032124
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pd-ableton-link
Version: 0.6~ds0-5
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

https://buildd.debian.org/status/fetch.php?pkg=pd-ableton-link&arch=armel&ver=0.6%7Eds0-5%2Bb3&stamp=1677541943&raw=0

make[1]: Entering directory '/<>/external'
 info: using Makefile.pdlibbuilder version 0.6.0
 info: using Pd API /usr/include/pd/m_pd.h
 info: making target all in lib abl_link~
 info: making abl_link~.o in lib abl_link~
g++ -DPD -I "/usr/include/pd" -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-fcheck-new -std=c++11 -I./link/include 
-I./link/modules/asio-standalone/asio/include -Wno-multichar 
-DLINK_PLATFORM_LINUX=1 -Wall -Wextra -Wshadow -Winline -Wstrict-aliasing 
-Wno-unused-function -Wno-unused-parameter -Wno-unused-value 
-Wno-unused-variable -O3 -ffast-math -funroll-loops -fomit-frame-pointer 
-march=armv7-a -mfpu=vfpv3 -mfloat-abi=hard -o abl_link~.o -c abl_link~.cpp
 info: making abl_link_instance.o in lib abl_link~
g++ -DPD -I "/usr/include/pd" -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-fcheck-new -std=c++11 -I./link/include 
-I./link/modules/asio-standalone/asio/include -Wno-multichar 
-DLINK_PLATFORM_LINUX=1 -Wall -Wextra -Wshadow -Winline -Wstrict-aliasing 
-Wno-unused-function -Wno-unused-parameter -Wno-unused-value 
-Wno-unused-variable -O3 -ffast-math -funroll-loops -fomit-frame-pointer 
-march=armv7-a -mfpu=vfpv3 -mfloat-abi=hard -o abl_link_instance.o -c 
abl_link_instance.cpp
In file included from /usr/include/features.h:513,
 from 
/usr/include/arm-linux-gnueabi/c++/12/bits/os_defines.h:39,
 from 
/usr/include/arm-linux-gnueabi/c++/12/bits/c++config.h:655,
 from /usr/include/c++/12/cmath:41,
 from /usr/include/c++/12/math.h:36,
 from abl_link~.cpp:9:
/usr/include/arm-linux-gnueabi/gnu/stubs.h:10:11: fatal error: 
gnu/stubs-hard.h: No such file or directory
   10 | # include 
  |   ^~
compilation terminated.
In file included from /usr/include/features.h:513,
 from 
/usr/include/arm-linux-gnueabi/c++/12/bits/os_defines.h:39,
 from 
/usr/include/arm-linux-gnueabi/c++/12/bits/c++config.h:655,
 from /usr/include/c++/12/bits/stl_algobase.h:59,
 from /usr/include/c++/12/memory:63,
 from abl_link_instance.hpp:10,
 from abl_link_instance.cpp:7:
/usr/include/arm-linux-gnueabi/gnu/stubs.h:10:11: fatal error: 
gnu/stubs-hard.h: No such file or directory
   10 | # include 
  |   ^~
compilation terminated.
make[1]: *** [Makefile.pdlibbuilder:959: abl_link~.o] Error 1

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: pd-ableton-link
Source-Version: 0.6~ds0-6
Done: IOhannes m zmölnig (Debian/GNU) 

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

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

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

Debian distribution maintenance software
pp.
IOhannes m zmölnig (Debian/GNU)  (supplier of updated 
pd-ableton-link package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 02 Mar 2023 23:19:13 +0100
Source: pd-ableton-link
Architecture: source
Version: 0.6~ds0-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: IOhannes m zmölnig (Debian/GNU) 
Closes: 1032124
Changes:
 pd-ableton-link (0.6~ds0-6) unstable; urgency=medium
 .
   * Explicitly set buildsystem to 'pd_lib_builder' (Closes: #1032124)
   * Bump standards version to 4.6.

Bug#1031296: marked as done (sccache FTBFS (on non-i386 32bit?))

[Debian Bug Tracking System]

Your message dated Thu, 02 Mar 2023 22:37:41 +
with message-id 
and subject line Bug#1031296: fixed in sccache 0.4.0~~pre8-6
has caused the Debian Bug report #1031296,
regarding sccache FTBFS (on non-i386 32bit?)
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.)


-- 
1031296: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031296
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sccache
Version: 0.4.0~~pre7-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=sccache&ver=0.4.0%7E%7Epre7-1

...
[io-lifetimes 0.7.2] error[E0554]: `#![feature]` may not be used on the stable 
release channel
[io-lifetimes 0.7.2]  --> :1:1
[io-lifetimes 0.7.2]   |
[io-lifetimes 0.7.2] 1 | #![feature(rustc_attrs)]
[io-lifetimes 0.7.2]   | 
[io-lifetimes 0.7.2] 
[io-lifetimes 0.7.2] error: aborting due to previous error
[io-lifetimes 0.7.2] 
[io-lifetimes 0.7.2] For more information about this error, try `rustc 
--explain E0554`.
...
--- End Message ---
--- Begin Message ---
Source: sccache
Source-Version: 0.4.0~~pre8-6
Done: Jonas Smedegaard 

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated sccache package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 02 Mar 2023 23:01:04 +0100
Source: sccache
Architecture: source
Version: 0.4.0~~pre8-6
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard 
Changed-By: Jonas Smedegaard 
Closes: 1031296
Changes:
 sccache (0.4.0~~pre8-6) unstable; urgency=medium
 .
   * disable feature dist-client
 and tolerate failure compiling+checking tests
 for weak arches armel armhf mipsel;
 closes: bug#1031296, thanks to Adrian Bunk
Checksums-Sha1:
 19114a2021064ccdaf917d059a3753d8481b87af 4233 sccache_0.4.0~~pre8-6.dsc
 55a01935fa6249467cbc0097736cc03e849a03bf 21884 
sccache_0.4.0~~pre8-6.debian.tar.xz
 fc88a4d16526847ebb94e2c3feedfb3684e573a6 22748 
sccache_0.4.0~~pre8-6_amd64.buildinfo
Checksums-Sha256:
 ae4aaf3cd9506cf005e2a38c331dd4317f430bd00b7bf1cfdaad1628c20c6928 4233 
sccache_0.4.0~~pre8-6.dsc
 01b0d766a19870271b07de9fc73ea8d4e5b7276859d110d39410bedb42c7ddb6 21884 
sccache_0.4.0~~pre8-6.debian.tar.xz
 81e5e3615b07cf0972ba822da7e0a84ba5331c79a1444745b18865e677b441a2 22748 
sccache_0.4.0~~pre8-6_amd64.buildinfo
Files:
 15bb4a239557e276a4caf6f6d2156466 4233 devel optional sccache_0.4.0~~pre8-6.dsc
 4adaaadae162bd47ecd5b89ba15504d4 21884 devel optional 
sccache_0.4.0~~pre8-6.debian.tar.xz
 7a089599e8baebba33665db5fa1f1ed0 22748 devel optional 
sccache_0.4.0~~pre8-6_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIyBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmQBIgIACgkQLHwxRsGg
ASGosA/4yhXnuJqujGnsscoUmv0LQdlUYgFYkc5aT+bh+8ny8eSVs/yNLqGLozSt
FnDO/Ryo0M98ELvhaGZKRfMi+6D8tpV0J5l/xlic4Wrgr2bUXxrtZcDiLkJHc8lX
LvGqysEVsyTFpE4S5sn6GunVBixK5d4Zh3hdBVs3BmC4BKk98Z8bhOyUcGA9db19
C9BU+34Y/c6+CdOHOKl5Ln98DubS2Q3V1OvlVuiKPfDJCCnVNzHc5tMdkaIl+8UM
u1hXIpwpB6IAN5WNIpkMcDtfk5ZGRMTSl0ATXXthv1I3wTUC6h3maRrG1ly6pvkM
beBo6ncXTncrCjYK0vb2nCtakMgaEjM8NFuLDMctgDiu06XK5/5mkfjTzz2+VguO
orlsdsj/zIwndiqVin7LZZ9ehvPhB+0E3T7MSRu5zdWWsRk6xF0TyMVe46aq7u95
T3CyITRQgJsbVGYp36uQR8YuZc0DNKQpXU4qLqNd85x7UjJ3IPQiMXxFNynvCf2v
1ORz9xOfI6pQi4qdLXQdxQwa0yjD7olUM+Pl05m/Y3LbgkYhSd+49P0exPdlF6kf
DOUrUyubHV9bRcE41IeIzdYw5uT0I/Ymrm2eu2Ht4vNhC8SkNV4k2BhOMsBfDAMe
o1kF5RdkaJsRyWdYZSO/Qnw82Ew10jv37uMRIE8KY23HxQqgCw==
=OaCO
-END PGP SIGNATURE End Message ---

Processed: tagging 1032166, tagging 1032198, tagging 994758, tagging 1028727, tagging 1031481, tagging 1019641 ...

[Debian Bug Tracking System]

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

> tags 1032166 + sid bookworm
Bug #1032166 [src:debian-timeline] do not release in bookworm
Added tag(s) bookworm and sid.
> tags 1032198 + sid bookworm
Bug #1032198 [wapiti] wapiti fails to start with Python 3.11
Added tag(s) bookworm and sid.
> tags 994758 + experimental
Bug #994758 {Done: Jonathan McDowell } [libsgutils2-2] Soname 
change without package name change
Added tag(s) experimental.
> tags 1028727 + experimental
Bug #1028727 {Done: Jochen Sprickerhof } 
[src:maven-debian-helper] maven-debian-helper: FTBFS: No plugin found for 
prefix plugin in the current project
Added tag(s) experimental.
> tags 1031481 + experimental
Bug #1031481 {Done: Thomas Goirand } [src:python-oslo.db] 
python-oslo.db: FTBFS: E: Build killed with signal TERM after 150 minutes of 
inactivity
Added tag(s) experimental.
> tags 1019641 + experimental
Bug #1019641 {Done: Pirate Praveen } 
[src:ruby-omniauth-auth0] ruby-omniauth-auth0: FTBFS: ERROR: Test "ruby3.0" 
failed:  Failure/Error: expect(last_response.status).to eq(302)
Added tag(s) experimental.
> reassign 1032196 kinfocenter 4:5.27.2-1
Bug #1032196 [kinfoc] kinfoc: Plasma incorrectly displays 5.26.90 in info 
center when synaptic displays 5.27 as the installed version
Warning: Unknown package 'kinfoc'
Bug reassigned from package 'kinfoc' to 'kinfocenter'.
No longer marked as found in versions kinfocenter.
Ignoring request to alter fixed versions of bug #1032196 to the same values 
previously set
Bug #1032196 [kinfocenter] kinfoc: Plasma incorrectly displays 5.26.90 in info 
center when synaptic displays 5.27 as the installed version
Marked as found in versions kinfocenter/4:5.27.2-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1019641: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019641
1028727: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028727
1031481: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031481
1032166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032166
1032196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032196
1032198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032198
994758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994758
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1032174: xfishtank does nothing

[ziegler]

https://gitlab.com/wvermin/xfishtank works in xfce4

(Martin)

Processed: bug 1032124 is forwarded to https://salsa.debian.org/multimedia-team/pd/pd-ableton-link/-/merge_requests/4

[Debian Bug Tracking System]

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

> forwarded 1032124 
> https://salsa.debian.org/multimedia-team/pd/pd-ableton-link/-/merge_requests/4
Bug #1032124 [src:pd-ableton-link] pd-ableton-link: FTBFS on armel: fatal 
error: gnu/stubs-hard.h: No such file or directory
Set Bug forwarded-to-address to 
'https://salsa.debian.org/multimedia-team/pd/pd-ableton-link/-/merge_requests/4'.
> thanks
Stopping processing here.

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

Bug#1032174: xfishtank does nothing

[Andrey Rakhmatullin]

On Wed, Mar 01, 2023 at 03:25:42AM +0100, zieg...@uni-freiburg.de wrote:
> xfishtank does nothing, just
> waiting to be interrupted.
> 
> I started it from a terminal on an xfce4-desktop.
It doesn't work on KDE either, but TBH I would assume software that "turns
your X root into something" doesn't work on DEs.

Bug#1026539: Bug#1027215: Bug#1026539: How much do we lose if we remove theano (+keras, deepnano, invesalius)?

[Rebecca N. Palmer]

On 02/03/2023 10:38, Andreas Tille wrote:

I admit I do not see any good reason to stick to the old version if we
decided before that keras/deepnano are no real blockers to even drop
theano.  Thus I was considering it more promising to spent my time on
the latest version.


1.1.2 isn't the latest version, just the latest that calls the module 
theano rather than aesara.  (I chose it to package because I didn't want 
to fully break compatibility, then abandoned it because I didn't like 
how much it did break.)



Do you want to ask release team for permission to do this?


If it would have build smoothly on all architectures, yes.


If you wouldn't want to do this work if it can't get into bookworm 
(possibly because you'd prefer to package 2.0 as aesara if you have to 
wait until trixie anyway), you might want to ask them first.



But we have
the first trouble on arm64[1]
Sorry - I forgot that theano skips most of its tests on Salsa-CI 
(because there's enough of them to take several hours), which is 
probably why it "passed" that but failed the full build.


Given how many failures there are (everywhere), I don't consider this 
worth fixing, but you are of course free to disagree.


(If you're planning to xfail tests, note that I consider *wrong-answer* 
bugs (though not crash bugs) in this kind of package to be RC.  I 
haven't checked whether we currently have any.)

Processed: severity of 1001144 is serious

[Debian Bug Tracking System]

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

> severity 1001144 serious
Bug #1001144 [odbc-mdbtools] odbc-mdbtools: Missing dependency on odbcinst
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#1031489: Fedora 37 + 340.108 + Qt 5.15.8 = ALL QT WORKING GOOD

[Andreas Beckmann]

On 02/03/2023 20.23, Alexander Procenko wrote:

Fedora 37 + 340.108 + Qt 5.15.8 = ALL QT WORKING GOOD
https://i.imgur.com/8Sma9pM.png
So its Debian issue?


What would be interesting is the ldd output on a Qt binary that works on 
Fedora and fails on Debian (of course using the corresponding distro 
builds of the same application) ... since they are supposedly built 
differently, they will pull in the GL/GLX/... bits differently.



Andreas

Processed: Re: python3-django-hyperkitty: Javascript not loaded because of HTML error

[Debian Bug Tracking System]

Processing control commands:

> tags -1 - moreinfo
Bug #1031928 [python3-django-hyperkitty] python3-django-hyperkitty: Javascript 
not loaded because of HTML error
Removed tag(s) moreinfo.
> tags -1 + confirmed
Bug #1031928 [python3-django-hyperkitty] python3-django-hyperkitty: Javascript 
not loaded because of HTML error
Added tag(s) confirmed.
> severity -1 important
Bug #1031928 [python3-django-hyperkitty] python3-django-hyperkitty: Javascript 
not loaded because of HTML error
Severity set to 'important' from 'grave'

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

Bug#1031928: python3-django-hyperkitty: Javascript not loaded because of HTML error

[James Addison]

Package: python3-django-hyperkitty
Followup-For: Bug #1031928
Control: tags -1 - moreinfo
Control: tags -1 + confirmed
Control: severity -1 important

On Thu, 2 Mar 2023 20:30:04 +0100, Peter J. Holzer wrote:
> On 2023-03-02 19:53:12 +0100, Peter J. Holzer wrote:
> > So it seems that my suspicion that {% compress js %}...{% endcompress %}
> > wasn't working properly was correct. But of course that raises the
> > question why that would fail on one system and work on another. I'll
> > investigate that and then get back to you.

> Found it (RTFM helps). I had set DEBUG = True in
> /etc/mailman3/mailman-web.py. This implicitly sets COMPRESS_ENABLED =
> False, so it was just passing the wrong HTML from the template through
> to the browser.

Perfect, thank you - I can confirm that I see the same errant HTML after
turning off compression in mailman-web.py and restarting the service:

   
   
   ...

I'm lowering the severity by one level because I don't think that this is a
release critical bug for bookworm given that it is a non-default setting, but
please feel free to disagree with me on that.

The patch looks good to me -- and I expect that it should work -- but I haven't
tested it yet to verify that.

Processed: tagging 1032198

[Debian Bug Tracking System]

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

> tags 1032198 + upstream fixed-upstream
Bug #1032198 [wapiti] wapiti fails to start with Python 3.11
Added tag(s) fixed-upstream and upstream.
> thanks
Stopping processing here.

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

Bug#1028454: nsscache: diff for NMU version 0.42-2.1

[Adrian Bunk]

Control: tags 1028454 + patch
Control: tags 1028454 + pending

Dear maintainer,

I've prepared an NMU for nsscache (versioned as 0.42-2.1) and uploaded 
it to DELAYED/7. Please feel free to tell me if I should cancel it.

cu
Adrian
diff -Nru nsscache-0.42/debian/changelog nsscache-0.42/debian/changelog
--- nsscache-0.42/debian/changelog	2021-10-08 00:38:32.0 +0300
+++ nsscache-0.42/debian/changelog	2023-03-02 22:20:08.0 +0200
@@ -1,3 +1,11 @@
+nsscache (0.42-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Disable buildtime tests to get rid of the build dependency
+on python3-mox3. (Closes: #1028454)
+
+ -- Adrian Bunk   Thu, 02 Mar 2023 22:20:08 +0200
+
 nsscache (0.42-2) unstable; urgency=medium
 
   [ Sergio Durigan Junior ]
diff -Nru nsscache-0.42/debian/control nsscache-0.42/debian/control
--- nsscache-0.42/debian/control	2021-10-07 12:01:13.0 +0300
+++ nsscache-0.42/debian/control	2023-03-02 22:20:06.0 +0200
@@ -2,7 +2,7 @@
 Section: admin
 Priority: optional
 Maintainer: Jamie Wilkinson 
-Build-Depends: debhelper-compat (= 13), python3, dh-python, python3-pycurl, python3-ldap, python3-mox3, python3-bsddb3, libnss-db, tzdata, python3-pytest-runner, python3-pytest, python3-boto3
+Build-Depends: debhelper-compat (= 13), python3, dh-python, python3-pycurl, python3-ldap, python3-bsddb3, libnss-db, tzdata, python3-pytest-runner, python3-pytest, python3-boto3
 Standards-Version: 4.5.1
 Homepage: https://github.com/google/nsscache
 Vcs-Browser: https://salsa.debian.org/debian/nsscache
diff -Nru nsscache-0.42/debian/rules nsscache-0.42/debian/rules
--- nsscache-0.42/debian/rules	2021-10-01 07:23:19.0 +0300
+++ nsscache-0.42/debian/rules	2023-03-02 22:20:06.0 +0200
@@ -10,3 +10,5 @@
 
 %:
 	dh $@ --with=python3 --buildsystem=pybuild
+
+override_dh_auto_test:

Processed: nsscache: diff for NMU version 0.42-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1028454 + patch
Bug #1028454 [nsscache] nsscache: build-depends on python3-mox3, to be removed 
from Debian
Added tag(s) patch.
> tags 1028454 + pending
Bug #1028454 [nsscache] nsscache: build-depends on python3-mox3, to be removed 
from Debian
Added tag(s) pending.

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

Processed: severity of 1011616 is grave

[Debian Bug Tracking System]

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

> severity 1011616 grave
Bug #1011616 [src:golang-github-tidwall-gjson] golang-github-tidwall-gjson: 
CVE-2021-42248 allows attackers to cause a redos via crafted JSON input
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Processed: severity of 1000225 is grave

[Debian Bug Tracking System]

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

> severity 1000225 grave
Bug #1000225 [src:golang-github-tidwall-gjson] golang-github-tidwall-gjson: 
CVE-2021-42836
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Bug#1031928: python3-django-hyperkitty: Javascript not loaded because of HTML error

[Peter J. Holzer]

On 2023-03-02 19:53:12 +0100, Peter J. Holzer wrote:
> So it seems that my suspicion that {% compress js %}...{% endcompress %}
> wasn't working properly was correct. But of course that raises the
> question why that would fail on one system and work on another. I'll
> investigate that and then get back to you.

Found it (RTFM helps). I had set DEBUG = True in
/etc/mailman3/mailman-web.py. This implicitly sets COMPRESS_ENABLED =
False, so it was just passing the wrong HTML from the template through
to the browser.

hp


-- 
   _  | Peter J. Holzer| Story must make more sense than reality.
|_|_) ||
| |   | h...@hjp.at |-- Charles Stross, "Creative writing
__/   | http://www.hjp.at/ |   challenge!"


signature.asc
Description: PGP signature

Bug#1031489: Fedora 37 + 340.108 + Qt 5.15.8 = ALL QT WORKING GOOD

[Alexander Procenko]

Fedora 37 + 340.108 + Qt 5.15.8 = ALL QT WORKING GOOD
https://i.imgur.com/8Sma9pM.png
So its Debian issue?

Bug#1026571: marked as done (jnlp-servlet: FTBFS: src/classes/jnlp/sample/servlet/JnlpResource.java:47: error: cannot find symbol)

[Debian Bug Tracking System]

Your message dated Thu, 02 Mar 2023 19:20:01 +
with message-id 
and subject line Bug#1026571: fixed in jnlp-servlet 20120126-5
has caused the Debian Bug report #1026571,
regarding jnlp-servlet: FTBFS: 
src/classes/jnlp/sample/servlet/JnlpResource.java:47: error: cannot find symbol
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.)


-- 
1026571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026571
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jnlp-servlet
Version: 20120126-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> rm -rf classes
> rm -rf lib
> mkdir -p classes
> mkdir -p lib
> /usr/lib/jvm/default-java/bin/javac -source 1.8 -target 1.8 -classpath 
> "/usr/lib/jvm/default-java/lib/javaws.jar:/usr/share/java/servlet-api-3.1.jar:src/classes"
>  -d classes src/classes/jnlp/sample/jardiff/JarDiffConstants.java
> warning: [options] bootstrap class path not set in conjunction with -source 8
> 1 warning
> /usr/lib/jvm/default-java/bin/javac -source 1.8 -target 1.8 -classpath 
> "/usr/lib/jvm/default-java/lib/javaws.jar:/usr/share/java/servlet-api-3.1.jar:src/classes"
>  -d classes src/classes/jnlp/sample/jardiff/JarDiff.java
> warning: [options] bootstrap class path not set in conjunction with -source 8
> src/classes/jnlp/sample/jardiff/JarDiff.java:475: warning: [removal] 
> Long(long) in Long has been deprecated and marked for removal
>   Long crcL = new Long(entry.getCrc());
>   ^
> src/classes/jnlp/sample/jardiff/JarDiff.java:523: warning: [removal] 
> Long(long) in Long has been deprecated and marked for removal
>   Long crcL = new Long(crc);
>   ^
> Note: Some input files use unchecked or unsafe operations.
> Note: Recompile with -Xlint:unchecked for details.
> 3 warnings
> mkdir -p classes/jnlp/sample/jardiff/resources/
> cp -fr src/classes/jnlp/sample/jardiff/resources/strings.properties 
> classes/jnlp/sample/jardiff/resources/strings.properties
> echo 'Main-Class:' jnlp.sample.jardiff.JarDiff > ./jardiff.manifest
> /usr/lib/jvm/default-java/bin/jar cvfm lib/jnlp-jardiff.jar 
> ./jardiff.manifest -C classes .
> added manifest
> adding: jnlp/(in = 0) (out= 0)(stored 0%)
> adding: jnlp/sample/(in = 0) (out= 0)(stored 0%)
> adding: jnlp/sample/jardiff/(in = 0) (out= 0)(stored 0%)
> adding: jnlp/sample/jardiff/JarDiff$JarFile2.class(in = 4287) (out= 
> 2376)(deflated 44%)
> adding: jnlp/sample/jardiff/JarDiff.class(in = 8069) (out= 4257)(deflated 47%)
> adding: jnlp/sample/jardiff/JarDiffConstants.class(in = 358) (out= 
> 258)(deflated 27%)
> adding: jnlp/sample/jardiff/JarDiffPatcher.class(in = 6853) (out= 
> 3687)(deflated 46%)
> adding: jnlp/sample/jardiff/Patcher$PatchDelegate.class(in = 235) (out= 
> 171)(deflated 27%)
> adding: jnlp/sample/jardiff/Patcher.class(in = 385) (out= 230)(deflated 40%)
> adding: jnlp/sample/jardiff/resources/(in = 0) (out= 0)(stored 0%)
> adding: jnlp/sample/jardiff/resources/strings.properties(in = 2160) (out= 
> 1077)(deflated 50%)
> rm -f ./jardiff.manifest
> /usr/lib/jvm/default-java/bin/javac -source 1.8 -target 1.8 -classpath 
> "/usr/lib/jvm/default-java/lib/javaws.jar:/usr/share/java/servlet-api-3.1.jar:src/classes"
>  -d classes src/classes/jnlp/sample/servlet/JnlpDownloadServlet.java
> warning: [options] bootstrap class path not set in conjunction with -source 8
> src/classes/jnlp/sample/servlet/JnlpResource.java:47: error: cannot find 
> symbol
> import java.util.jar.Pack200;
> ^
>   symbol:   class Pack200
>   location: package java.util.jar
> src/classes/jnlp/sample/servlet/JnlpResource.java:48: error: package 
> java.util.jar.Pack200 does not exist
> import java.util.jar.Pack200.Packer;
> ^
> src/classes/jnlp/sample/servlet/JnlpResource.java:93: error: cannot find 
> symbol
>   private static Packer packer;
>  ^
>   symbol:   class Packer
>   location: class JnlpResource
> src/classes/jnlp/sample/servlet/JnlpResource.java:96: error: cannot find 
> symbol
>   packer = Pack200.newPacker();
>^
>   symbol:   variable Pack200
>   location: class JnlpResource
> src/classes/jnlp/sample/jardiff/JarDiff.java:475: warning: [removal] 
> Long(long) in Long has been deprecated and marked for removal
>   Long crcL = new Lo

Bug#1031928: python3-django-hyperkitty: Javascript not loaded because of HTML error

[Peter J. Holzer]

On 2023-03-02 01:32:55 +, James Addison wrote:
> Package: python3-django-hyperkitty
> Followup-For: Bug #1031928
> X-Debbugs-Cc: h...@hjp.at
> Control: tags -1 moreinfo
> 
> Hi Peter,
> 
> I'd like to gain some experience with configuring email infrastructure, and
> this bug seems like a good opportunity to learn.
> 
> I haven't yet been able to reproduce the self-closing HTML script tags; here's
> roughly the series of install steps I used (I may have omitted one or two
> details) to get the interface up-and-running:
> 
>   # apt install mailman3-full
>   # vim /etc/mailman3/mailman-web.py  # configure REST API creds
>   # ln -s /etc/mailman3/apache.conf /etc/apache2/conf-available/mailman3.conf
>   # a2enconf mailman3
>   # a2enmod proxy_uwsgi
>   # systemctl restart mailman3-web
>   # systemctl restart apache2

I just did that on a fresh VM to to have a pristine state again.


> (note that I also had postfix utilities installed on the system)
> 
> That seemed to work: I was able to browse the postorius web interface and see
> that I had no mailing lists configured.

The problem is only on the "Archives" page (/mailman3/hyperkitty), and
it's not immediately noticable without any archived mailinglists,
however ...


> Checking the HTML source of the page, I did see some  tags -- 
> including
> for 'popper.js' -- each of them had a closing  tag, as expected.

At the bottom of the hyperkitty page I see now:





This is ok, but it's not what I saw on the other system. Instead of the
last line with the cached compressed javascript I got the 12 individual
script entries from the template.

So it seems that my suspicion that {% compress js %}...{% endcompress %}
wasn't working properly was correct. But of course that raises the
question why that would fail on one system and work on another. I'll
investigate that and then get back to you.


> Could you provide any more information on configuration steps / settings that
> may be required to reproduce the problem?

My process wasn't as straightforward as yours, there was quite a bit of
trial and error involved (for example, I installed postgresql after
mailman3 and then did a dpkg-reconfigure to get mailman3 to use
posgresql instead of sqlite; and I also needed a few attempts to get the
apache config right), however, browsing through the shell history I see
no differences which look relevant.

hp

-- 
   _  | Peter J. Holzer| Story must make more sense than reality.
|_|_) ||
| |   | h...@hjp.at |-- Charles Stross, "Creative writing
__/   | http://www.hjp.at/ |   challenge!"


signature.asc
Description: PGP signature

Processed: Re: Bug#1030846: e2fsprogs: generates filesystems that grub-install doesn't recognize

[Debian Bug Tracking System]

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

> affects 1030939 installation-reports
Bug #1030939 [e2fsprogs] e2fsprogs: generates filesystems that grub-install 
doesn't recognize
Added indication that 1030939 affects installation-reports
>
End of message, stopping processing here.

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

Bug#1032235: Bug#1014110: libargon2 0~20190702-0.1 no longer links against libpthread which breaks cryptsetup-initramfs

[Bastian Germann]

On Thu, 2 Mar 2023 05:10:41 +0100 Guilhem Moulin  wrote:

Ah no my bad, the changelog entry is probably incorrect and the
cryptsetup-initramfs breakage is caused by the recent libargon2 upload
indeed, but AFAICT not by anything particular in the upload.


I am sorry for having caused that issue, Daniel. Thanks for investigating, 
Guilhem.

The changelog entry is correct because it fixes a formerly made change.
0~20171227-0.1 intended to compile only udeb without threads:
"Build udeb without a dependency on pthreads"
But it unintentionally compiled the .deb executable with the .a compiled 
without threads.
The additional "make clean" fixes accidentally picking up the wrong .a.

Bug#1032174: Update

[ziegler]

* Using Debian kernel linux-image-6.1.0-5-amd64
 changes nothing

* xfishtank works with the icewm Desktop.

(Martin)

Bug#1029821: change gnome-desktop's default choice of Japanese input methods for Debian

[James Addison]

Package: libgnome-desktop-4-2
Followup-For: Bug #1029821

On Thu, 2 Mar 2023 15:50:22 +, smcv wrote:
> When there are patches available for whatever we decide is the right
> behaviour, you shouldn't need to walk through the whole install process.

Thanks; yep, I think I took an unnecessarily long path through this.  I'd been
looking for a reason to try the latest Debian installer (and may have learned
one or two things about it along the way, but I'll save any of that for
separate threads).

On Wed, 01 Mar 2023 16:47:22 + James Addison  wrote:
>   2. select 'anthy' in 'gnome-initial-setup'
>   3. attempt Japanese keyboard input

Result: ペンギン

>   5. select 'mozc-jp' in 'gnome-initial-setup'
>   6. attempt Japanese keyboard input

Result: ペンギン

(in truth: those are not from the d-i alpha 2 sessions I was running; after
reading Simon's advice, I used a local user account instead)

In both the anthy and mozc cases, the keypresses (chords?) required were fairly
similar: 'pe', 'ng', 'gi', 'ng' - with some delete-key and enter-key usage to
complete each glyph and/or input entry.

Processed: Re: Bug #1000209

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1000209 [timidity-daemon] timidity-daemon: Fails to install due to no 
timidity.service
Added tag(s) patch.

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

Bug#1000209: Bug #1000209

[Paul Gevers]

Control: tags -1 patch

Hi,

On Sat, 25 Feb 2023 14:53:54 -0500 =?UTF-8?Q?Charles_Fl=C3=A8che?= 
 wrote:


> We've been able to install the package using the attached patch that
> doesn't hack around the migration to timidity-daemon. Does this
> approach looks OK ?

Although I'm not the maintainer, with a brief look I'd say it does. But, 
if I understand correctly, *only* because the migration between timidity 
and timidity-daemon happened in version 2.14.0-1 which was somewhere 
during the buster release cycle.



diff --git a/debian/timidity-daemon.postinst b/debian/timidity-daemon.postinst
index a3610f9..573bc09 100644
--- a/debian/timidity-daemon.postinst
+++ b/debian/timidity-daemon.postinst
@@ -53,14 +53,6 @@ esac
 
 rm -f /etc/timidity/timidity.daemon
 
-# make sure we really stop, because packaging system doesn't

-# understand what we're trying to do with migration to timidity-daemon
-[ -f "/etc/init.d/timidity" ] && if which invoke-rc.d >/dev/null 2>&1; then
-  invoke-rc.d timidity stop
-else
-  /etc/init.d/timidity stop
-fi
-
 #DEBHELPER#
 
 exit 0




Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1031622: d-i regression in weekly builds: FEATURE_C12 unsupported by the installed e2fsck

[Marc Leeman]

I fixed my builds with the bookworm weekly netinst by adding this in the
preseed:

d-i partman/early_command string \
sed -i -e "s/,metadata_csum_seed//g" -e "s/,orphan_file//g"
/etc/mke2fs.conf;\
   ...


On Wed, 1 Mar 2023 at 15:59, Marc Leeman  wrote:

>
> Note that updating ext2fs with these new features also breaks other
> software components like refind (volume detection) in bookworm (this is how
> I came to this bug).
>
>
>

-- 
g. Marc

Bug#1029821: change gnome-desktop's default choice of Japanese input methods for Debian

[Simon McVittie]

On Thu, 02 Mar 2023 at 14:58:36 +, James Addison wrote:
> Thank you; I currently have side-by-side graphical installations of d-i alpha 
> 2
> running in both English and Japanese, to help my menu navigation, and hope to
> confirm keyboard input results within the next day or so.

When there are patches available for whatever we decide is the right
behaviour, you shouldn't need to walk through the whole install process.
It should be enough to:

* install the proposed gnome-initial-setup and/or libgnome-desktop-4-2
* as a privileged (root-equivalent) user, use GNOME Settings or adduser
  to create a new user account
* Log Out or Switch User
* log in as the new user account

You should get the gnome-initial-setup dialog again for the new user,
the first time they log in.

Delete the new user and create another one to continue testing.

If you can't read Japanese, it would probably be helpful to set the
system language to Japanese but set your root-equivalent user's language
to English.

smcv

Bug#1032258: marked as done (plasma-welcome: contains unintended patches providing a nonsensical welcome screen)

[Debian Bug Tracking System]

Your message dated Thu, 2 Mar 2023 15:37:13 +
with message-id 
and subject line Re: Bug#1032258: plasma-welcome: contains unintended patches 
providing a nonsensical welcome screen
has caused the Debian Bug report #1032258,
regarding plasma-welcome: contains unintended patches providing a nonsensical 
welcome screen
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.)


-- 
1032258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032258
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: plasma-welcome
Version: 5.27.0-1
Severity: serious
Justification: not suitable for inclusion in a stable release in this form
Control: fixed -1 5.27.2-1

To reproduce:

* install Debian 12 with Plasma
* install plasma-welcome
* run plasma-welcome

Expected result: a welcome screen that makes sense

Actual result:

* a window titled "Welcome to KDE Plasmama"
* which claims that "Debian is a free and open-source desktop environment"
  (not true) "created by KDE" (also not true)

This is caused by
https://sources.debian.org/src/plasma-welcome/5.27.0-1/debian/patches/toto
and
https://sources.debian.org/src/plasma-welcome/5.27.0-1/debian/patches/toto2
which don't seem to have been intended to be included in the package, and
aren't in the git repository.

5.27.2-1 doesn't have those patches, but needs to migrate into bookworm
for this to be fixed.

smcv
--- End Message ---
--- Begin Message ---
Version: 5.27.2-1

On Thu, 02 Mar 2023 at 15:06:22 +0100, Aurélien COUDERC wrote:
> Le 2 mars 2023 14:09:46 GMT+01:00, Simon McVittie  a écrit :
> >Package: plasma-welcome
> >Justification: not suitable for inclusion in a stable release in this form
> >Control: fixed -1 5.27.2-1

Closing the bug "properly" now that I have a bug number for it.

On Thu, 02 Mar 2023 at 15:51:39 +0100, Aurélien COUDERC wrote:
> Now I just need to convince someone from the release team to let 5.27.2
> migrate urgently. :)

Well, I've done my bit by giving you a RC bug you can point to as
justification :-)

Thanks,
smcv--- End Message ---

Bug#1029821: change gnome-desktop's default choice of Japanese input methods for Debian

[James Addison]

Package: libgnome-desktop-4-2
Followup-For: Bug #1029821
X-Debbugs-Cc: ken...@xdump.org

On Thu, 02 Mar 2023 22:07:16 +0900 Kentaro Hayashi  wrote:
> On Wed, 01 Mar 2023 16:47:22 + James Addison  wrote:

> > My plan is to:
> > 
> >   1. run the graphical d-i install of a fresh GNOME 43 system
> >   2. select 'anthy' in 'gnome-initial-setup'
> >   3. attempt Japanese keyboard input

> Need to do extra setup.
>
> * sudo apt install -y ibus-anthy
> * ibus restart

Thank you; I currently have side-by-side graphical installations of d-i alpha 2
running in both English and Japanese, to help my menu navigation, and hope to
confirm keyboard input results within the next day or so.

The text that I'll attempt to enter is 'ペンギン', that I believe is a
translation of 'penguin' (according to libretranslate and Google Translate).

Bug#1032258: plasma-welcome: contains unintended patches providing a nonsensical welcome screen

[Aurélien COUDERC]

Oops.

Will fix that right away.


Le 2 mars 2023 14:09:46 GMT+01:00, Simon McVittie  a écrit :
>Package: plasma-welcome
>Version: 5.27.0-1
>Severity: serious
>Justification: not suitable for inclusion in a stable release in this form
>Control: fixed -1 5.27.2-1
>

Bug#1032242: marked as done (yadifa FTBFS on 32bit)

[Debian Bug Tracking System]

Your message dated Thu, 02 Mar 2023 13:57:15 +
with message-id 
and subject line Bug#1032242: fixed in yadifa 2.6.4-1
has caused the Debian Bug report #1032242,
regarding yadifa FTBFS on 32bit
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.)


-- 
1032242: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032242
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: yadifa
Version: 2.6.3-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=yadifa&ver=2.6.3-1

...
src/fdtools.c: In function ‘file_mtime_set_add_file’:
src/fdtools.c:1754:15: error: ‘ptr_node’ has no member named ‘value_s64’; did 
you mean ‘value_s32’?
 1754 | node->value_s64 = mtime;
  |   ^
  |   value_s32
src/fdtools.c: In function ‘file_mtime_set_modified’:
src/fdtools.c:1776:22: error: ‘ptr_node’ has no member named ‘value_s64’; did 
you mean ‘value_s32’?
 1776 | if(node->value_s64 < mtime)
  |  ^
  |  value_s32
make[4]: *** [Makefile:1544: src/fdtools.lo] Error 1
--- End Message ---
--- Begin Message ---
Source: yadifa
Source-Version: 2.6.4-1
Done: Markus Schade 

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

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

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

Debian distribution maintenance software
pp.
Markus Schade  (supplier of updated yadifa package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 02 Mar 2023 13:45:53 +0100
Source: yadifa
Architecture: source
Version: 2.6.4-1
Distribution: unstable
Urgency: medium
Maintainer: Markus Schade 
Changed-By: Markus Schade 
Closes: 1032242
Changes:
 yadifa (2.6.4-1) unstable; urgency=medium
 .
   * New upstream version 2.6.4 (Closes: #1032242)
   * Drop depends on lsb-base
Checksums-Sha1:
 77e7e1c823a32a5be7fa757926cbbb5a092a6fa1 2119 yadifa_2.6.4-1.dsc
 8326a96319578018f7d1d0b8c7f0d3191d4b408e 2696804 yadifa_2.6.4.orig.tar.gz
 1577181dd9d3adfff6f3323a95fc2fafde3c0042 836 yadifa_2.6.4.orig.tar.gz.asc
 f5868d91adb3191fb1c5e37f85505c2fada605c7 17872 yadifa_2.6.4-1.debian.tar.xz
 6f4a065b7af2f1399251a81e092b8e5e68f7c9fa 6535 yadifa_2.6.4-1_amd64.buildinfo
Checksums-Sha256:
 0c5f65f67cd47df50617ca3425875333f8a51c9baacfba20a84046b64876df76 2119 
yadifa_2.6.4-1.dsc
 d8bb73a2d645594acbf05169542947bbf447911fbe63392e010dae00d803b571 2696804 
yadifa_2.6.4.orig.tar.gz
 c29669f720a64f4fa724555bde74a49527d072d40efe90bc1de9bc241d7c4cd1 836 
yadifa_2.6.4.orig.tar.gz.asc
 ce1ddfa6acdbc19b306cefe9c241ffd08e2588c2852139a78b805740f8999436 17872 
yadifa_2.6.4-1.debian.tar.xz
 b7314ac6626f4ba15db653904f165cc4ba227099b67c54683253c1c29973afa9 6535 
yadifa_2.6.4-1_amd64.buildinfo
Files:
 653ccfd9ddba4d0155ce7f6f822c1278 2119 net optional yadifa_2.6.4-1.dsc
 4a421c192bbb1f45f23e57a0dff6e262 2696804 net optional yadifa_2.6.4.orig.tar.gz
 cb8efaf6db196c764180960b64d7f821 836 net optional yadifa_2.6.4.orig.tar.gz.asc
 fc1faf65b445f16d5b492c2a1deb9344 17872 net optional 
yadifa_2.6.4-1.debian.tar.xz
 caf3148d4ce83ce41f3f7edcdb3fb501 6535 net optional 
yadifa_2.6.4-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEZpRdLHRYqlRMf/GUn7tbAnlnRjYFAmQAor0ACgkQn7tbAnln
RjZfIQ/+OQNeitk0zM3Q/1Wg7gpGc5bGlHwR6mPJ/37gofASgcBXhovWoJGDx2Z6
D5+MXOBOisQQNI1E2e3N4qxKHnz0mWloQZvLBngwvIzzNKscmgmwGA4ELmFTKaTM
xv/xbWLiEYpMsRJqP3ETnv77BUHWC+Ngi97zYWLqQyKASUxIo6tj+bVtla2aQUtd
UwxUNk7htgh35mgaV/5W+CAw17GcTAyM6XlLImNsZwPDP39c56gzUtBJwpBl2r2W
brnhPZBAmefgNFNC/BaqXarFvh7q0XZtB8om2xG4Sp40oroYiha0KxGnhI1PXFqf
disMnH8Kv0PHx55q6R56x6dz8ituu0o60wKl8MCpq3gkH44s2Ww7wtNfCSbKVu8q
Sp/5jac27ZfHk3IFsSq3VgTfL5Jeo/y8uYd0clmvS41jvY7cW9oRFeJW9Kbmafq6
RqbY4Boo3CvLiC9b12HFNc5jBwcm/WDzG6I2Dnca7koJMcyIDA0bMWghi9doaD/0
dCQJE8MiLE3JxjDMj7bS7Gz0ESniP7memUZ1aK7/fJ2nURzl59fgUidsgG6aMsNb
nSlj4RY4hIPMjD/8iiiGrKTt5bf3a+2OrWbLs9ooaaz39wSYQnwpqEkKDszHKJKT
SHDPcHlPkdU/hhsFE8MqkwPlWyu1FSsMce3UULIT2XqMkJ1V2T4=
=YIoV
-END PGP SIGNATURE End Message ---

Bug#1029821: change gnome-desktop's default choice of Japanese input methods for Debian

[Osamu Aoki]

Hi,

This is very convoluted issue.

Disclaimer: I use (n)vim and anthy and voted for non-free-firmware=yes (i.e.,
prioritize user experience)

On Thu, 2023-03-02 at 09:42 +, Simon McVittie wrote:
> Control: tags -1 + moreinfo
> 
> On Sat, 28 Jan 2023 at 16:46:35 +0900, YOSHINO Yoshihito wrote:
> > As mentioned in Bug #984875, gnome-initial-setup's default choice of
> > input method is hardcoded in the dependent libgnome-desktop-4-2 package.
> > The Japanese one is anthy
> > https://sources.debian.org/src/gnome-desktop/43.1-1/libgnome-desktop/default-input-sources.h/#L39
> > preferred by upstream (Fedora/Red Hat) perhaps because its code base is
> > simple and easy to maintain, while this is not suitable for most Debian
> > Japanese users, who use mozc because of its better conversion quality,
> > thus task-japanese-gnome-desktop and task-japanese-desktop has preferred
> > mozc over anthy. So the hardcoded value should be adjusted for our
> > users.
> 
> Is there consensus among Japanese-speaking users of Debian that mozc is
> a better default for all Japanese speakers, including new users who are
> not familiar with GNOME or Debian?

Choice of input method engine and its framework are hot topics without easy
unanimous agreements. 

Before going into that kind of discussion, I would like to draw attention to
general performance perception and some technical points.

* Why mozc:
In general, mozc tends to provide better suggestions for the possible choice of
input conversion choices than ones provided by anthy.  This may be the reason
why people like mozc than anthy.

* Why anthy:
In debian/control, mozc source package comes as:
> Architecture: i386 amd64 armel armhf arm64 riscv64
while anthy doesn't have such limitation.  My vague memory tells me that the
code for mozc is written for the little endian system only.  (mozc's C++ header
file structure and shipped data requires specific endianness.)

Also data used for obtaining conversion proposals are more opaque for mozc. 
Data for anthy is more intuitive for modification than that of mozc.  Neither
are easy to do, though.

> I want to avoid changing this from anthy to mozc-jp, and then getting a
> second bug report from a different Japanese user saying that we need to
> change it back!
> 
> Looking at #984875 and #983653, I also see a mention of mozc only being
> available on certain architectures: it's available on x86, ARM and riscv64,
> but not on mips*el, ppc64el or s390x.

Correct.

> How does this interact with the default being mozc-jp? Do we need to use
> a #ifdef to make the default be mozc on architectures that have it, and
> anthy on architectures that don't?

If we decide to propose mozc as preferred choice, that should be a possible
choice.

> I'm also concerned that mozc still depends on GTK 2 (a switch to GTK
> 3 was tried and then reverted, see #967641). This is OK for bookworm,
> but will probably not be supportable in Debian 13.

> > Upstream prefers ibus-anthy for Japanese input
> 
> Please talk to upstream about this: if mozc is a better default for Debian,
> then it's probably also a better default for upstream.
>
> The only issue reports I could find upstream are
> https://gitlab.gnome.org/GNOME/gnome-desktop/-/issues/181 which is about
> switching the default from kkc to anthy, and
> https://gitlab.gnome.org/GNOME/gnome-initial-setup/-/issues/104 which is
> older and refers to kkc as being the default.

 * kkc and anthy are both in GPL: kkc was intended to be improved replacement of
anthy by RH developer.  Its resulting performance was not convincing to replace
anthy.  Anthy was by Japanese government sponsored and it's last updates was
gathered and organized by DD (muto-san).

 * mozc is mostly BSD-3-Clause with its opaque learned data being BSD-3-Clause-
with-ICOT-term.  It's by google employee, if I recall.  RH ppl may not like
opaqueness of learned data outside of their easy update.  Learned data is only
provided as a data dump.

> On Wed, 22 Feb 2023 at 15:09:15 +0900, ken...@xdump.org wrote:
> >   Thus with attached patch, gnome-initial-setup will not
> >   show label for mozc-jp as "日本語 (Mozc)" by default.
> 
> What would be the best label to be displayed there?
> 
> What is actually displayed instead?
> 
> >   To display label correctly, fetch_ibus_engines_result must be called 
> >   in advance.
> 
> That's probably not possible: fetch_ibus_engines_result is called
> asynchronously with the result of a D-Bus method call, so it's already
> called as early as possible, and before that point we don't have the
> necessary information.
> 
> Probably the best we can do there is to hard-code a special case for
> mozc-jp.
> 
>     smcv

In order to get mozc to be promoted to be more prominent position, we need to
make sure the maintainer of mozc feels comfortable.  He (Iwamatsu-san) seems to
be making curating many patches and making patch to keep up with gtk3
transition.  Gunnar also seems to be doing QA and regression checks. 

Bug#1029821: change gnome-desktop's default choice of Japanese input methods for Debian

[Kentaro Hayashi]

Hi,


On Thu, 2 Mar 2023 09:42:36 + Simon McVittie  wrote:
> Control: tags -1 + moreinfo
> 
snip
> 
> Is there consensus among Japanese-speaking users of Debian that mozc is
> a better default for all Japanese speakers, including new users who are
> not familiar with GNOME or Debian?

At least, there is the fact that bullseye's default choice is ibus-mozc 
for Japanese users.

> I want to avoid changing this from anthy to mozc-jp, and then getting a
> second bug report from a different Japanese user saying that we need to
> change it back!
> 
> Looking at #984875 and #983653, I also see a mention of mozc only being
> available on certain architectures: it's available on x86, ARM and riscv64,
> but not on mips*el, ppc64el or s390x.
> 
> How does this interact with the default being mozc-jp? Do we need to use
> a #ifdef to make the default be mozc on architectures that have it, and
> anthy on architectures that don't?

Surely, it may be better to modify the patch to consider non-available mozc
 on certain architectures. 

> I'm also concerned that mozc still depends on GTK 2 (a switch to GTK
> 3 was tried and then reverted, see #967641). This is OK for bookworm,
> but will probably not be supportable in Debian 13.

I didn't noticed that issue. Thank you.

> On Wed, 22 Feb 2023 at 15:09:15 +0900, ken...@xdump.org wrote:
> >   Thus with attached patch, gnome-initial-setup will not
> >   show label for mozc-jp as "日本語 (Mozc)" by default.
> 
> What would be the best label to be displayed there?
> 

IMHO, 日本語 (Mozc).

> What is actually displayed instead?
> 

As I mentioned already, "mozc-jp".

> >   To display label correctly, fetch_ibus_engines_result must be called 
> >   in advance.
> 
> That's probably not possible: fetch_ibus_engines_result is called
> asynchronously with the result of a D-Bus method call, so it's already
> called as early as possible, and before that point we don't have the
> necessary information.

Currently, I agree with you.

Regards,

Bug#1029821: change gnome-desktop's default choice of Japanese input methods for Debian

[Kentaro Hayashi]

Hi,

On Wed, 01 Mar 2023 16:47:22 + James Addison  wrote:
> Package: libgnome-desktop-4-2
> Followup-For: Bug #1029821
> X-Debbugs-Cc: yy.y.ja...@gmail.com
> 
> I'd like to contribute by testing d-i with Japanese input (I'm not a Japanese
> speaker, but can offer some time to help).
> 
> My plan is to:
> 
>   1. run the graphical d-i install of a fresh GNOME 43 system
>   2. select 'anthy' in 'gnome-initial-setup'
>   3. attempt Japanese keyboard input

Need to do extra setup.

* sudo apt install -y ibus-anthy
* ibus restart

After restarting ibus, you can switch input source to 「日本語(Anthy)」.
if you change 入力モード(_A), you can type Japanese.

> 
>   4. run the graphical d-i install of a fresh GNOME 43 system
>   5. select 'mozc-jp' in 'gnome-initial-setup'
>   6. attempt Japanese keyboard input

After that, if you change 入力モード(A), you can type Japanese.

> Also:
> 
> My understanding is that the _only_ difference that the patch will make is
> that it will change the default in 'gnome-initial-setup'.  Users could still
> choose 'anthy' -- or another input method -- if they want, for some reason.  
> Is
> that correct?

Yes. users can still choose their preferrable input method.
The problem is conflicting with task-japanese-gnome-desktop's recommends.

Regards,

Bug#1032258: plasma-welcome: contains unintended patches providing a nonsensical welcome screen

[Simon McVittie]

Package: plasma-welcome
Version: 5.27.0-1
Severity: serious
Justification: not suitable for inclusion in a stable release in this form
Control: fixed -1 5.27.2-1

To reproduce:

* install Debian 12 with Plasma
* install plasma-welcome
* run plasma-welcome

Expected result: a welcome screen that makes sense

Actual result:

* a window titled "Welcome to KDE Plasmama"
* which claims that "Debian is a free and open-source desktop environment"
  (not true) "created by KDE" (also not true)

This is caused by
https://sources.debian.org/src/plasma-welcome/5.27.0-1/debian/patches/toto
and
https://sources.debian.org/src/plasma-welcome/5.27.0-1/debian/patches/toto2
which don't seem to have been intended to be included in the package, and
aren't in the git repository.

5.27.2-1 doesn't have those patches, but needs to migrate into bookworm
for this to be fixed.

smcv

Processed: plasma-welcome: contains unintended patches providing a nonsensical welcome screen

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 5.27.2-1
Bug #1032258 [plasma-welcome] plasma-welcome: contains unintended patches 
providing a nonsensical welcome screen
Marked as fixed in versions plasma-welcome/5.27.2-1.

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

Bug#1032257: alt-ergo free and non-free

[Stéphane Glondu]

Dear Jean-Christophe,

Le 02/03/2023 à 13:08, Jean-Christophe Léchenet a écrit :
We were surprised to see that the last version 
of alt-ergo (2.4.2) is in Debian testing, while it is non-free. At the 
moment, the latest free version is 2.3.0. Is there some mechanism to 
extract the free subset of alt-ergo or something like that?


I was not aware of that. I've opened a bug report:

  https://bugs.debian.org/1032257

to track this issue.


Cheers,

--
Stéphane

Bug#1032257: Non-free (non-commercial) license

[Stéphane Glondu]

Source: alt-ergo
Version: 2.4.2-2
Severity: serious

Dear Maintainers,

It has been brought to my attention [1] that the version of alt-ergo
currently in testing has a non-free license [2]. According to [3], the
latest free version is Alt-Ergo-Free version 2.3.3, which is the
version which should be (IMHO) in Debian.

[1] https://lists.debian.org/debian-ocaml-maint/2023/03/msg2.html
[2] https://ocamlpro.github.io/alt-ergo/About/license.html
[3] https://alt-ergo.ocamlpro.com/



Cheers,

-- 
Stéphane

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

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

Bug#1029821: change gnome-desktop's default choice of Japanese input methods for Debian

[Gunnar Hjalmarsson]

Hi!

I'm commenting on this with my Ubuntu glasses on. :/

On 2023-03-02 10:42, Simon McVittie wrote:

Is there consensus among Japanese-speaking users of Debian that mozc
is a better default for all Japanese speakers, including new users
who are not familiar with GNOME or Debian?

I want to avoid changing this from anthy to mozc-jp, and then getting
a second bug report from a different Japanese user saying that we
need to change it back!


My impression from the Ubuntu side is that there is a consensus. 
ibus-mozc has been preferred over ibus-anthy since Ubuntu 16.04 at the 
request of Japanese Ubuntu users. I can't recall any user request since 
then to change the default Japanese IBus IM.


There is a point of concern, though: mozc upstream seems to be moving 
towards replacing gtk with qt. Since the main Ubuntu ISO does not 
include qt, that may result in an undesired change of Ubuntu's default 
in the end. Not sure if qt would be a problem for Debian.


But even if there is a risk that Debian would need to change again in a 
later release, the current situation is an inconsistency between the 
installer and gnome-initial-setup. So to me it sounds reasonable to make 
the suggested change to mozc-jp in Debian 12. Doing it the other way 
around wouldn't have much user support AFAICT.



Looking at #984875 and #983653, I also see a mention of mozc only
being available on certain architectures: it's available on x86, ARM
and riscv64, but not on mips*el, ppc64el or s390x.


I don't know the reasoning behind that. Not long ago riscv64 was added 
to the list due to , and it proved to 
build on that arch without issues. So possibly mozc can be built on more 
architectures without a hassle, if that is desired.



I'm also concerned that mozc still depends on GTK 2 (a switch to GTK
3 was tried and then reverted, see #967641).


I did that reversal, sorry. But it was for a good reason. The patch is 
still in the source (but disabled), and maybe just needs a bit more work.


--
Gunnar

Bug#1032255: pulseaudio: sound keeps dying (on Tiger Lake)

[Dave Love]

Severity: normal

Bug#1032255: pulseaudio: sound keeps dying (on Tiger Lake)

[Dave Love]

Package: pulseaudio
Severity: serious
X-Debbugs-Cc: none, Dave Love 

I kept losing sound and had to restart applications.  In contrast to
#1022143, removing pipewire packages didn't help, but after replacing
pulseaudio with pipewire, things are working fine.  (I'm using the
bullseye-backports version, but I don't know if that's necessary.)

This is probably hardware-related, since I found it after replacing a
Thinkpad with a "HP EliteBook 840 G8 Notebook PC (19X36AV)" which has a
"Tiger Lake-LP Smart Sound Technology Audio Controller".  I can't see
any similar reports in a web search, though.

Sorry I can't report the actual package versions now, but recent, and
pulseaudio doesn't seems to have changed recently, and perhaps the
solution helps others.

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

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

Processed: Re: Bug#1032244: tryton-server 6.0.28-1 causes autopkgtest regression in tryton-modules-stock-location-move

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://foss.heptapod.net/tryton/tryton/-/issues/12112
Bug #1032244 [src:tryton-server] tryton-server 6.0.28-1 causes autopkgtest 
regression in tryton-modules-stock-location-move
Set Bug forwarded-to-address to 
'https://foss.heptapod.net/tryton/tryton/-/issues/12112'.
> tags -1 + pending
Bug #1032244 [src:tryton-server] tryton-server 6.0.28-1 causes autopkgtest 
regression in tryton-modules-stock-location-move
Added tag(s) pending.

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

Bug#1032244: tryton-server 6.0.28-1 causes autopkgtest regression in tryton-modules-stock-location-move

[Mathias Behrle]

Source: tryton-server
Version: 6.0.28-1
Control: forwarded -1 https://foss.heptapod.net/tryton/tryton/-/issues/12112
Control: tags -1 + pending

Fix will be part of next Bugfix release.

Bug#1029821: change gnome-desktop's default choice of Japanese input methods for Debian

[Shengjing Zhu]

Hi

On Thu, Mar 2, 2023 at 5:43 PM Simon McVittie  wrote:
>
> Control: tags -1 + moreinfo
>
> On Sat, 28 Jan 2023 at 16:46:35 +0900, YOSHINO Yoshihito wrote:
> > As mentioned in Bug #984875, gnome-initial-setup's default choice of
> > input method is hardcoded in the dependent libgnome-desktop-4-2 package.
> > The Japanese one is anthy
> > https://sources.debian.org/src/gnome-desktop/43.1-1/libgnome-desktop/default-input-sources.h/#L39
> > preferred by upstream (Fedora/Red Hat) perhaps because its code base is
> > simple and easy to maintain, while this is not suitable for most Debian
> > Japanese users, who use mozc because of its better conversion quality,
> > thus task-japanese-gnome-desktop and task-japanese-desktop has preferred
> > mozc over anthy. So the hardcoded value should be adjusted for our
> > users.
>
> Is there consensus among Japanese-speaking users of Debian that mozc is
> a better default for all Japanese speakers, including new users who are
> not familiar with GNOME or Debian?
>
> I want to avoid changing this from anthy to mozc-jp, and then getting a
> second bug report from a different Japanese user saying that we need to
> change it back!
>

I'm not a Japanese user. But I've been frustrated in the last few days
of the Bullseye release, when Gnome's upstream choice conflicts with
Debian's tasksel.

The problem is that in Debian's tasksel, it has the prefered input
method. So if the Debian system is installed by our default installer,
the user can't have out of box input experience.

So if neither taksel or Gnome in Debian is going to change, it really
hurts our users.

-- 
Shengjing Zhu

Bug#1026539: How much do we lose if we remove theano (+keras, deepnano, invesalius)?

[Andreas Tille]

Hi Rebecca,

Am Wed, Mar 01, 2023 at 10:41:23PM + schrieb Rebecca N. Palmer:
> I agree that switching to Aesara is probably the only reasonable option
> other than removal.  (I'd given up on trying to fix 1.0, and was intending
> to let removal happen.)
> 
> However, it's a much bigger change than is normally allowed in bookworm at
> this point.  (1.1 includes multiple breaking changes, which is why it's in
> experimental, but a quick codesearch suggests these parts *may* not be used
> in keras/deepnano. https://github.com/aesara-devs/aesara/releases?page=8 )

I admit I do not see any good reason to stick to the old version if we
decided before that keras/deepnano are no real blockers to even drop
theano.  Thus I was considering it more promising to spent my time on
the latest version.
 
> Do you want to ask release team for permission to do this?

If it would have build smoothly on all architectures, yes.  But we have
the first trouble on arm64[1]

> Or do you want
> to try the same patches on 1.0?  (I suspect that that won't work, but I
> haven't actually tried it.)
> 
> (Also, you might not want numpy1p24_compat.patch - the v1p0 branch is
> currently in whatever state it was in when I gave up on it, and my vague
> memory is that this was a failed experiment, though I don't know if that
> meant "actively bad" or just "not a (full) solution".)

I've found some patches inside numpy1p24_compat.patch that were also
in Aesara.  Since the package did not fully build with this patch
alone I've added a separate patch with the only goal to build and pass
the test suite.

Kind regards
Andreas.

[1] 
https://buildd.debian.org/status/fetch.php?pkg=theano&arch=amd64&ver=1.1.2%2Bdfsg-4&stamp=1677751828&raw=0

-- 
http://fam-tille.de

Processed: Re: Bug#1008313: lxpolkit: no authentication dialog can't use it

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #1008313 [lxpolkit] lxpolkit: no authentication dialog can't use it
Severity set to 'normal' from 'grave'
> tags -1 + moreinfo unreproducible
Bug #1008313 [lxpolkit] lxpolkit: no authentication dialog can't use it
Added tag(s) unreproducible and moreinfo.

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

Bug#1008313: lxpolkit: no authentication dialog can't use it

[Simon McVittie]

Control: severity -1 normal
Control: tags -1 + moreinfo unreproducible

On Fri, 30 Dec 2022 at 21:33:06 +0200, Andriy Grytsenko wrote:
> I use LXDE myself each day, I cannot say it's *nearly useless*
> but many people use it and rarely have problems.

I happen to have installed a Debian 12 virtual machine with LXDE recently
while investigating a different bug, so I tried checking what happens in a
default installation.

By default, task-desktop-lxde installs both lxpolkit (lxsession dependency)
and policykit-1-gnome (gnome-system-tools dependency). With these installed,
when I am logged in to a LXDE session, pkexec works as expected. I didn't
test gparted.

I also tried removing policykit-1-gnome (which requires removing
gnome-system-tools) so that lxpolkit was the only polkit agent on the
system, and then rebooting. With only lxpolkit installed, when I am
logged in to a LXDE session, pkexec and gparted both work as expected.

LXDE is not my preferred desktop environment and has more dependencies on
unmaintained components than I'm really happy about, but I confirm that
it works, is not useless, and does not need to be removed from bookworm.

On Sat, 26 Mar 2022 at 17:59:53 +0100, realroot wrote:
> If I try to use pkexec:
>
>  AUTHENTICATING FOR org.freedesktop.policykit.exec ===
> Authentication is needed to run `/usr/bin/env' as the super user
> Authenticating as: root
> Password:
> polkit-agent-helper-1: error response to PolicyKit daemon:
> GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
>  AUTHENTICATION FAILED ===
> Error executing command as another user: Not authorized
...
> If I try to launch a program tha requires root like gparted:
> 
> /usr/sbin/gparted
> Error executing command as another user: No authentication agent found.

I suspect the situation here might be that the user reporting the bug is
not using a complete desktop environment, but has installed individual
packages to make their own desktop environment out of components.

This is something that can be made to work, but if you do this, it's up
to you to make sure you're running all the necessary pieces, and that
includes choosing and running a suitable polkit agent.

For example, if I log in to a plain Openbox session, that doesn't
include a polkit authentication agent, and running gparted will fail;
but if I run `lxpolkit &` and then run gparted again, this time I get
a lxpolkit prompt. A more realistic setup would be to run both openbox
and lxpolkit from ~/.xsession.

It is not possible to auto-start a polkit agent via D-Bus activation,
because the system does not know which of potentially several polkit
agents is the one you wanted to include in your desktop environment.

pkexec is meant to be able to operate without a polkit agent, but
something is wrong in its implementation, leading to the "No session for
cookie" error message (this is a known bug, #1031676). systemctl is an
example of a component that can do the equivalent thing correctly. If
someone works out what pkexec is doing wrong, patches would be welcome.

smcv

Bug#1030425: marked as done (vistrails: FTBFS: pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: '2.x')

[Debian Bug Tracking System]

Your message dated Thu, 02 Mar 2023 10:21:09 +
with message-id 
and subject line Bug#1030425: fixed in vistrails 3.0~git+9dc22bd.dfsg.1-1.1
has caused the Debian Bug report #1030425,
regarding vistrails: FTBFS: 
pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: '2.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.)


-- 
1030425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030425
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vistrails
Version: 3.0~git+9dc22bd.dfsg.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230203 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules build
> dh build --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:240: python3.11 setup.py config 
> /usr/lib/python3/dist-packages/setuptools/dist.py:548: UserWarning: The 
> version specified ('2.x') is an invalid version, this may not work as 
> expected with newer versions of setuptools, pip, and PyPI. Please see PEP 440 
> for more details.
>   warnings.warn(
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> /usr/lib/python3/dist-packages/setuptools/dist.py:548: UserWarning: The 
> version specified ('2.x') is an invalid version, this may not work as 
> expected with newer versions of setuptools, pip, and PyPI. Please see PEP 440 
> for more details.
>   warnings.warn(
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11/build/vistrails
> copying vistrails/__init__.py -> 
> /<>/.pybuild/cpython3_3.11/build/vistrails
> copying vistrails/stop_vistrails_server.py -> 
> /<>/.pybuild/cpython3_3.11/build/vistrails
> copying vistrails/vistrails_server.py -> 
> /<>/.pybuild/cpython3_3.11/build/vistrails
> copying vistrails/run.py -> 
> /<>/.pybuild/cpython3_3.11/build/vistrails
> creating /<>/.pybuild/cpython3_3.11/build/vistrails/gui
> copying vistrails/gui/version_view.py -> 
> /<>/.pybuild/cpython3_3.11/build/vistrails/gui
> copying vistrails/gui/__init__.py -> 
> /<>/.pybuild/cpython3_3.11/build/vistrails/gui
> copying vistrails/gui/vis_diff.py -> 
> /<>/.pybuild/cpython3_3.11/build/vistrails/gui
> copying vistrails/gui/graphics_view.py -> 
> /<>/.pybuild/cpython3_3.11/build/vistrails/gui
> copying vistrails/gui/shell.py -> 
> /<>/.pybuild/cpython3_3.11/build/vistrails/gui
> copying vistrails/gui/query_view.py -> 
> /<>/.pybuild/cpython3_3.11/build/vistrails/gui
> copying vistrails/gui/application_server.py -> 
> /<>/.pybuild/cpython3_3.11/build/vistrails/gui
> copying vistrails/gui/ports_pane.py -> 
> /<>/.pybuild/cpython3_3.11/build/vistrails/gui
> copying vistrails/gui/pipeline_view.py -> 
> /<>/.pybuild/cpython3_3.11/build/vistrails/gui
> copying vistrails/gui/debug.py -> 
> /<>/.pybuild/cpython3_3.11/build/vistrails/gui
> copying vistrails/gui/vistrail_controller.py -> 
> /<>/.pybuild/cpython3_3.11/build/vistrails/gui
> copying vistrails/gui/module_palette.py -> 
> /<>/.pybuild/cpython3_3.11/build/vistrails/gui
> copying vistrails/gui/repository.py -> 
> /<>/.pybuild/cpython3_3.11/build/vistrails/gui
> copying vistrails/gui/vistrail_view.py -> 
> /<>/.pybuild/cpython3_3.11/build/vistrails/gui
> copying vistrails/gui/vistrails_palette.py -> 
> /<>/.pybuild/cpython3_3.11/build/vistrails/gui
> copying vistrails/gui/version_prop.py -> 
> /<>/.pybuild/cpython3_3.11/build/vistrails/gui
> copying vistrails/gui/variable_dropbox.py -> 
> /<>/.pybuild/cpython3_3.11/build/vistrails/gui
> copying vistrails/gui/base_view.py -> 
> /<>/.pybuild/cpython3_3.11/build/vistrails/gui
> copying vistrails/gui/publishing.py -> 
> /<>/.pybuild/cpython3_3.11/build/vistrails/gui
> copying vistrails/gui/port_documentation.py -> 
> /<>/.pybuild/cpython3_3.11/build/vistrails/gui
> copying vistrails/gui/debugger.py -> 
> /<>/.pybuild/cpython3_3.11/build/vistrails/gui
> copying vistrails/gui/module_configuration.py -> 
> /<>/.pybuild/cpython3_3.11/build/vistrails/gui
> copying vistrails/gui/module_options.py -> 
> /<>/.pybuild/cpython3_3.11/build/vistrails/gui
> copying vistrails/gui/qt.py -> 
> /<>/.pybuild/cpython3_3.11/build/vistrails/gui
> copying vistrails/gui/requirements.py -> 
> /<>/.pybuild/cpython3_3.11/build/vistrails/gui
> copying vistrails/gui/vistrail_variables.py -> 
> /<>/.pybuild/cpython3_3.11/build/vistrai

Bug#1027663: marked as done (vdr-plugin-skinenigmang: FTBFS: make: *** [debian/rules:11: binary] Error 25)

[Debian Bug Tracking System]

Your message dated Thu, 02 Mar 2023 10:20:49 +
with message-id 
and subject line Bug#1026310: fixed in vdr 2.6.0-1.1
has caused the Debian Bug report #1026310,
regarding vdr-plugin-skinenigmang: FTBFS: make: *** [debian/rules:11: binary] 
Error 25
to be marked as done.

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

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


-- 
1026310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026310
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vdr-plugin-skinenigmang
Version: 0.1.2+git20190720-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230101 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  fakeroot debian/rules binary
> dh binary --with vdrplugin
>dh_testroot
>dh_prep
>dh_auto_install --destdir=debian/vdr-plugin-skinenigmang/
>dh_install
>dh_vdrplugin_enable
>dh_installdocs
>dh_installchangelogs
>dh_perl
>dh_link
>dh_strip_nondeterminism
>   Normalized 
> debian/vdr-plugin-skinenigmang/usr/share/locale/da_DK/LC_MESSAGES/vdr-skinenigmang.mo
>   Normalized 
> debian/vdr-plugin-skinenigmang/usr/share/locale/cs_CZ/LC_MESSAGES/vdr-skinenigmang.mo
>   Normalized 
> debian/vdr-plugin-skinenigmang/usr/share/locale/ro_RO/LC_MESSAGES/vdr-skinenigmang.mo
>   Normalized 
> debian/vdr-plugin-skinenigmang/usr/share/locale/nl_NL/LC_MESSAGES/vdr-skinenigmang.mo
>   Normalized 
> debian/vdr-plugin-skinenigmang/usr/share/locale/fr_FR/LC_MESSAGES/vdr-skinenigmang.mo
>   Normalized 
> debian/vdr-plugin-skinenigmang/usr/share/locale/sv_SE/LC_MESSAGES/vdr-skinenigmang.mo
>   Normalized 
> debian/vdr-plugin-skinenigmang/usr/share/locale/it_IT/LC_MESSAGES/vdr-skinenigmang.mo
>   Normalized 
> debian/vdr-plugin-skinenigmang/usr/share/locale/el_GR/LC_MESSAGES/vdr-skinenigmang.mo
>   Normalized 
> debian/vdr-plugin-skinenigmang/usr/share/locale/ca_ES/LC_MESSAGES/vdr-skinenigmang.mo
>   Normalized 
> debian/vdr-plugin-skinenigmang/usr/share/locale/ru_RU/LC_MESSAGES/vdr-skinenigmang.mo
>   Normalized 
> debian/vdr-plugin-skinenigmang/usr/share/locale/es_ES/LC_MESSAGES/vdr-skinenigmang.mo
>   Normalized 
> debian/vdr-plugin-skinenigmang/usr/share/locale/et_EE/LC_MESSAGES/vdr-skinenigmang.mo
>   Normalized 
> debian/vdr-plugin-skinenigmang/usr/share/locale/de_DE/LC_MESSAGES/vdr-skinenigmang.mo
>   Normalized 
> debian/vdr-plugin-skinenigmang/usr/share/locale/fi_FI/LC_MESSAGES/vdr-skinenigmang.mo
>   Normalized 
> debian/vdr-plugin-skinenigmang/usr/share/locale/pl_PL/LC_MESSAGES/vdr-skinenigmang.mo
>   Normalized 
> debian/vdr-plugin-skinenigmang/usr/share/locale/hu_HU/LC_MESSAGES/vdr-skinenigmang.mo
>   Normalized 
> debian/vdr-plugin-skinenigmang/usr/share/locale/sl_SI/LC_MESSAGES/vdr-skinenigmang.mo
>   Normalized 
> debian/vdr-plugin-skinenigmang/usr/share/locale/pt_PT/LC_MESSAGES/vdr-skinenigmang.mo
>   Normalized 
> debian/vdr-plugin-skinenigmang/usr/share/locale/hr_HR/LC_MESSAGES/vdr-skinenigmang.mo
>   Normalized 
> debian/vdr-plugin-skinenigmang/usr/share/locale/tr_TR/LC_MESSAGES/vdr-skinenigmang.mo
>   Normalized 
> debian/vdr-plugin-skinenigmang/usr/share/locale/nn_NO/LC_MESSAGES/vdr-skinenigmang.mo
>dh_compress
>dh_fixperms
>dh_missing
>dh_dwz -a
>dh_strip -a
>dh_makeshlibs -a
>dh_shlibdeps -a
>dh_vdrplugin_depends
> dh_vdrplugin_depends: warning: Unescaped newlines in the value of a substvars 
> can cause broken substvars files (see #1025714).
> dh_vdrplugin_depends: warning: Hint: If you really need a newline character, 
> provide it as "${Newline}".
> dh_vdrplugin_depends: error: Bug in helper: The substvar must not contain a 
> raw newline character (vdr:Depends=vdr-abi-2.6.0-debian\n)
> make: *** [debian/rules:11: binary] Error 25


The full build log is available from:
http://qa-logs.debian.net/2023/01/01/vdr-plugin-skinenigmang_0.1.2+git20190720-4_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230101;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230101&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=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 mark it as 'affects'-in

Bug#1027660: marked as done (vdr-plugin-svdrpservice: FTBFS: make: *** [debian/rules:9: binary] Error 25)

[Debian Bug Tracking System]

Your message dated Thu, 02 Mar 2023 10:20:49 +
with message-id 
and subject line Bug#1026310: fixed in vdr 2.6.0-1.1
has caused the Debian Bug report #1026310,
regarding vdr-plugin-svdrpservice: FTBFS: make: *** [debian/rules:9: binary] 
Error 25
to be marked as done.

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

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


-- 
1026310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026310
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vdr-plugin-svdrpservice
Version: 1.0.0-10
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230101 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> install -D libvdr-svdrpservice.so 
> /<>/debian/tmp/usr/lib/vdr/plugins/libvdr-svdrpservice.so.2.6.0
> install -D -m644 po/de_DE.mo 
> /<>/debian/tmp/usr/share/locale/de_DE/LC_MESSAGES/vdr-svdrpservice.mo
> install -D -m644 po/it_IT.mo 
> /<>/debian/tmp/usr/share/locale/it_IT/LC_MESSAGES/vdr-svdrpservice.mo
> install -D -m644 po/sk_SK.mo 
> /<>/debian/tmp/usr/share/locale/sk_SK/LC_MESSAGES/vdr-svdrpservice.mo
> make[1]: Leaving directory '/<>'
>dh_install
>dh_vdrplugin_enable
>dh_installdocs
>dh_installchangelogs
>dh_perl
>dh_link
>dh_strip_nondeterminism
>   Normalized 
> debian/vdr-plugin-svdrpservice/usr/share/locale/sk_SK/LC_MESSAGES/vdr-svdrpservice.mo
>   Normalized 
> debian/vdr-plugin-svdrpservice/usr/share/locale/de_DE/LC_MESSAGES/vdr-svdrpservice.mo
>   Normalized 
> debian/vdr-plugin-svdrpservice/usr/share/locale/it_IT/LC_MESSAGES/vdr-svdrpservice.mo
>dh_compress
>dh_fixperms
>dh_missing
>dh_dwz -a
>dh_strip -a
>dh_makeshlibs -a
>dh_shlibdeps -a
>dh_vdrplugin_depends
> dh_vdrplugin_depends: warning: Unescaped newlines in the value of a substvars 
> can cause broken substvars files (see #1025714).
> dh_vdrplugin_depends: warning: Hint: If you really need a newline character, 
> provide it as "${Newline}".
> dh_vdrplugin_depends: error: Bug in helper: The substvar must not contain a 
> raw newline character (vdr:Depends=vdr-abi-2.6.0-debian\n)
> make: *** [debian/rules:9: binary] Error 25


The full build log is available from:
http://qa-logs.debian.net/2023/01/01/vdr-plugin-svdrpservice_1.0.0-10_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230101;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230101&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=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 mark 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: vdr
Source-Version: 2.6.0-1.1
Done: Adrian Bunk 

We believe that the bug you reported is fixed in the latest version of
vdr, 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.
Adrian Bunk  (supplier of updated vdr 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, 26 Feb 2023 01:32:03 +0200
Source: vdr
Architecture: source
Version: 2.6.0-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian VDR Team 
Changed-By: Adrian Bunk 
Closes: 1026310
Changes:
 vdr (2.6.0-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Apply patch from Rogo to remove trailing newline from abiversion.
 (Closes: #1026310)
Checksums-Sha1:
 5c7d5017119d419137f07c0227a6ca77de2e1aa6 2136 vdr_2.6.0-1.1.dsc
 bf1c46543020a369895e67c72b02baef03504020 51300 vdr_2.6.0-1.1.debian.tar.xz
Checksums-Sha256:

Bug#1027659: marked as done (vdr-plugin-dvbhddevice: FTBFS: make: *** [debian/rules:7: binary] Error 25)

[Debian Bug Tracking System]

Your message dated Thu, 02 Mar 2023 10:20:49 +
with message-id 
and subject line Bug#1026310: fixed in vdr 2.6.0-1.1
has caused the Debian Bug report #1026310,
regarding vdr-plugin-dvbhddevice: FTBFS: make: *** [debian/rules:7: binary] 
Error 25
to be marked as done.

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

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


-- 
1026310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026310
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vdr-plugin-dvbhddevice
Version: 2.2.0-15
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230101 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_strip --dbgsym-migration='vdr-plugin-dvbhddevice-dbg (<< 2.2.0-6~)'
> make[1]: Leaving directory '/<>'
>dh_makeshlibs -a
>dh_shlibdeps -a
>dh_vdrplugin_depends
> dh_vdrplugin_depends: warning: Unescaped newlines in the value of a substvars 
> can cause broken substvars files (see #1025714).
> dh_vdrplugin_depends: warning: Hint: If you really need a newline character, 
> provide it as "${Newline}".
> dh_vdrplugin_depends: error: Bug in helper: The substvar must not contain a 
> raw newline character (vdr:Depends=vdr-abi-2.6.0-debian\n)
> make: *** [debian/rules:7: binary] Error 25


The full build log is available from:
http://qa-logs.debian.net/2023/01/01/vdr-plugin-dvbhddevice_2.2.0-15_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230101;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230101&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=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 mark 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: vdr
Source-Version: 2.6.0-1.1
Done: Adrian Bunk 

We believe that the bug you reported is fixed in the latest version of
vdr, 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.
Adrian Bunk  (supplier of updated vdr 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, 26 Feb 2023 01:32:03 +0200
Source: vdr
Architecture: source
Version: 2.6.0-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian VDR Team 
Changed-By: Adrian Bunk 
Closes: 1026310
Changes:
 vdr (2.6.0-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Apply patch from Rogo to remove trailing newline from abiversion.
 (Closes: #1026310)
Checksums-Sha1:
 5c7d5017119d419137f07c0227a6ca77de2e1aa6 2136 vdr_2.6.0-1.1.dsc
 bf1c46543020a369895e67c72b02baef03504020 51300 vdr_2.6.0-1.1.debian.tar.xz
Checksums-Sha256:
 226c0a072b73103f1965a1ba593fec81d90c80b6292a03a5a7e4cd4e7cc2e5b2 2136 
vdr_2.6.0-1.1.dsc
 7bfd7297298e9838b17329308a2b36a5c0c12d33474b53f227492ca7194124de 51300 
vdr_2.6.0-1.1.debian.tar.xz
Files:
 be7446e9890863a0918a3e162158afe4 2136 video optional vdr_2.6.0-1.1.dsc
 dc672debb9fb43744077ddf83b3479ef 51300 video optional 
vdr_2.6.0-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmP6nNAACgkQiNJCh6LY
mLFlsBAAtD8rsriIPUiEEvqDCaZU8pEjRpfSV9snWrxuhqS/eHmqkdgtJWrl77R+
SWJHgNc27X7bnNwyjjPR/JDGM+/iEzwgESz+v2+M12Qu07LSEuHrIV1t4O0puy80
iSbEGizBULeMv5DUAuaEHDgyWCAskNq6utaczD4uF1xPMu5eRlu3EbtMKONJpb96
PS8yK25fcFlrPOkSoiOg7An+pS64EjtbnwsXKousY0zj2NrXJhCgg2qN8U8YKr/l
AY18Q6y2z5FueBob84t548mGmpjR/QIkTEtFa9HIiBodYwFVL6WtL4BuHx4brTh9
UrpHwGdY1IjeIH5sKCKHu3vTRfe/DioBE0/gqLfkTwamAuyyzclttB5AFIGQaR2J
nzyn8VjAxvU1Caphipqm3ZJ59iEZjap/4nKtW5p9qdIyQ++/E49

Bug#1027627: marked as done (vdr-plugin-osdteletext: FTBFS: make: *** [debian/rules:7: binary] Error 25)

[Debian Bug Tracking System]

Your message dated Thu, 02 Mar 2023 10:20:49 +
with message-id 
and subject line Bug#1026310: fixed in vdr 2.6.0-1.1
has caused the Debian Bug report #1026310,
regarding vdr-plugin-osdteletext: FTBFS: make: *** [debian/rules:7: binary] 
Error 25
to be marked as done.

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

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


-- 
1026310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026310
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vdr-plugin-osdteletext
Version: 2.3.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230101 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> install -D libvdr-osdteletext.so 
> /<>/debian/vdr-plugin-osdteletext/usr/lib/vdr/plugins/libvdr-osdteletext.so.2.6.0
> install -D -m644 po/ca_ES.mo 
> /<>/debian/vdr-plugin-osdteletext/usr/share/locale/ca_ES/LC_MESSAGES/vdr-osdteletext.mo
> install -D -m644 po/de_DE.mo 
> /<>/debian/vdr-plugin-osdteletext/usr/share/locale/de_DE/LC_MESSAGES/vdr-osdteletext.mo
> install -D -m644 po/es_ES.mo 
> /<>/debian/vdr-plugin-osdteletext/usr/share/locale/es_ES/LC_MESSAGES/vdr-osdteletext.mo
> install -D -m644 po/fi_FI.mo 
> /<>/debian/vdr-plugin-osdteletext/usr/share/locale/fi_FI/LC_MESSAGES/vdr-osdteletext.mo
> install -D -m644 po/fr_FR.mo 
> /<>/debian/vdr-plugin-osdteletext/usr/share/locale/fr_FR/LC_MESSAGES/vdr-osdteletext.mo
> install -D -m644 po/it_IT.mo 
> /<>/debian/vdr-plugin-osdteletext/usr/share/locale/it_IT/LC_MESSAGES/vdr-osdteletext.mo
> install -D -m644 po/pt_PT.mo 
> /<>/debian/vdr-plugin-osdteletext/usr/share/locale/pt_PT/LC_MESSAGES/vdr-osdteletext.mo
> install -D -m644 po/ru_RU.mo 
> /<>/debian/vdr-plugin-osdteletext/usr/share/locale/ru_RU/LC_MESSAGES/vdr-osdteletext.mo
> install -D -m644 po/sk_SK.mo 
> /<>/debian/vdr-plugin-osdteletext/usr/share/locale/sk_SK/LC_MESSAGES/vdr-osdteletext.mo
> install -D -m644 po/uk_UA.mo 
> /<>/debian/vdr-plugin-osdteletext/usr/share/locale/uk_UA/LC_MESSAGES/vdr-osdteletext.mo
> make[1]: Leaving directory '/<>'
>dh_install
>dh_vdrplugin_enable
>dh_installdocs
>dh_installchangelogs
>dh_perl
>dh_link
>dh_strip_nondeterminism
>   Normalized 
> debian/vdr-plugin-osdteletext/usr/share/locale/fr_FR/LC_MESSAGES/vdr-osdteletext.mo
>   Normalized 
> debian/vdr-plugin-osdteletext/usr/share/locale/it_IT/LC_MESSAGES/vdr-osdteletext.mo
>   Normalized 
> debian/vdr-plugin-osdteletext/usr/share/locale/sk_SK/LC_MESSAGES/vdr-osdteletext.mo
>   Normalized 
> debian/vdr-plugin-osdteletext/usr/share/locale/uk_UA/LC_MESSAGES/vdr-osdteletext.mo
>   Normalized 
> debian/vdr-plugin-osdteletext/usr/share/locale/ca_ES/LC_MESSAGES/vdr-osdteletext.mo
>   Normalized 
> debian/vdr-plugin-osdteletext/usr/share/locale/ru_RU/LC_MESSAGES/vdr-osdteletext.mo
>   Normalized 
> debian/vdr-plugin-osdteletext/usr/share/locale/es_ES/LC_MESSAGES/vdr-osdteletext.mo
>   Normalized 
> debian/vdr-plugin-osdteletext/usr/share/locale/de_DE/LC_MESSAGES/vdr-osdteletext.mo
>   Normalized 
> debian/vdr-plugin-osdteletext/usr/share/locale/fi_FI/LC_MESSAGES/vdr-osdteletext.mo
>   Normalized 
> debian/vdr-plugin-osdteletext/usr/share/locale/pt_PT/LC_MESSAGES/vdr-osdteletext.mo
>dh_compress
>dh_fixperms
>dh_missing
>dh_dwz -a
>dh_strip -a
>dh_makeshlibs -a
>dh_shlibdeps -a
>dh_vdrplugin_depends
> dh_vdrplugin_depends: warning: Unescaped newlines in the value of a substvars 
> can cause broken substvars files (see #1025714).
> dh_vdrplugin_depends: warning: Hint: If you really need a newline character, 
> provide it as "${Newline}".
> dh_vdrplugin_depends: error: Bug in helper: The substvar must not contain a 
> raw newline character (vdr:Depends=vdr-abi-2.6.0-debian\n)
> make: *** [debian/rules:7: binary] Error 25


The full build log is available from:
http://qa-logs.debian.net/2023/01/01/vdr-plugin-osdteletext_2.3.1-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230101;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230101&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=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 mar

Bug#1027646: marked as done (vdr-plugin-vnsiserver: FTBFS: make: *** [debian/rules:16: binary] Error 25)

[Debian Bug Tracking System]

Your message dated Thu, 02 Mar 2023 10:20:49 +
with message-id 
and subject line Bug#1026310: fixed in vdr 2.6.0-1.1
has caused the Debian Bug report #1026310,
regarding vdr-plugin-vnsiserver: FTBFS: make: *** [debian/rules:16: binary] 
Error 25
to be marked as done.

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

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


-- 
1026310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026310
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vdr-plugin-vnsiserver
Version: 1:1.8.0+git20211205-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230101 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_strip --dbgsym-migration='vdr-plugin-live-dbg (<< 1:1.8.0-1~)'
> make[1]: Leaving directory '/<>'
>dh_makeshlibs -a
>dh_shlibdeps -a
>dh_vdrplugin_depends
> dh_vdrplugin_depends: warning: Unescaped newlines in the value of a substvars 
> can cause broken substvars files (see #1025714).
> dh_vdrplugin_depends: warning: Hint: If you really need a newline character, 
> provide it as "${Newline}".
> dh_vdrplugin_depends: error: Bug in helper: The substvar must not contain a 
> raw newline character (vdr:Depends=vdr-abi-2.6.0-debian\n)
> make: *** [debian/rules:16: binary] Error 25


The full build log is available from:
http://qa-logs.debian.net/2023/01/01/vdr-plugin-vnsiserver_1.8.0+git20211205-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230101;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230101&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=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 mark 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: vdr
Source-Version: 2.6.0-1.1
Done: Adrian Bunk 

We believe that the bug you reported is fixed in the latest version of
vdr, 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.
Adrian Bunk  (supplier of updated vdr 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, 26 Feb 2023 01:32:03 +0200
Source: vdr
Architecture: source
Version: 2.6.0-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian VDR Team 
Changed-By: Adrian Bunk 
Closes: 1026310
Changes:
 vdr (2.6.0-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Apply patch from Rogo to remove trailing newline from abiversion.
 (Closes: #1026310)
Checksums-Sha1:
 5c7d5017119d419137f07c0227a6ca77de2e1aa6 2136 vdr_2.6.0-1.1.dsc
 bf1c46543020a369895e67c72b02baef03504020 51300 vdr_2.6.0-1.1.debian.tar.xz
Checksums-Sha256:
 226c0a072b73103f1965a1ba593fec81d90c80b6292a03a5a7e4cd4e7cc2e5b2 2136 
vdr_2.6.0-1.1.dsc
 7bfd7297298e9838b17329308a2b36a5c0c12d33474b53f227492ca7194124de 51300 
vdr_2.6.0-1.1.debian.tar.xz
Files:
 be7446e9890863a0918a3e162158afe4 2136 video optional vdr_2.6.0-1.1.dsc
 dc672debb9fb43744077ddf83b3479ef 51300 video optional 
vdr_2.6.0-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmP6nNAACgkQiNJCh6LY
mLFlsBAAtD8rsriIPUiEEvqDCaZU8pEjRpfSV9snWrxuhqS/eHmqkdgtJWrl77R+
SWJHgNc27X7bnNwyjjPR/JDGM+/iEzwgESz+v2+M12Qu07LSEuHrIV1t4O0puy80
iSbEGizBULeMv5DUAuaEHDgyWCAskNq6utaczD4uF1xPMu5eRlu3EbtMKONJpb96
PS8yK25fcFlrPOkSoiOg7An+pS64EjtbnwsXKousY0zj2NrXJhCgg2qN8U8YKr/l
AY18Q6y2z5FueBob84t548mGmpjR/QIkTEtFa9HIiBodYwFVL6WtL4BuHx4brTh9
UrpHwGdY1IjeIH5sKCKHu3vTRfe/DioBE0/gqLfkTwamAuyyzclttB5AFIGQaR2J
nzyn8VjAxvU1Caphipqm3ZJ59iEZjap/4

Bug#1027645: marked as done (vdr-plugin-dvbsddevice: FTBFS: make: *** [debian/rules:7: binary] Error 25)

[Debian Bug Tracking System]

Your message dated Thu, 02 Mar 2023 10:20:49 +
with message-id 
and subject line Bug#1026310: fixed in vdr 2.6.0-1.1
has caused the Debian Bug report #1026310,
regarding vdr-plugin-dvbsddevice: FTBFS: make: *** [debian/rules:7: binary] 
Error 25
to be marked as done.

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

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


-- 
1026310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026310
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vdr-plugin-dvbsddevice
Version: 2.2.0-15
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230101 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_strip --dbgsym-migration='vdr-plugin-dvbsddevice-dbg (<< 2.2.0-6~)'
> make[1]: Leaving directory '/<>'
>dh_makeshlibs -a
>dh_shlibdeps -a
>dh_vdrplugin_depends
> dh_vdrplugin_depends: warning: Unescaped newlines in the value of a substvars 
> can cause broken substvars files (see #1025714).
> dh_vdrplugin_depends: warning: Hint: If you really need a newline character, 
> provide it as "${Newline}".
> dh_vdrplugin_depends: error: Bug in helper: The substvar must not contain a 
> raw newline character (vdr:Depends=vdr-abi-2.6.0-debian\n)
> make: *** [debian/rules:7: binary] Error 25


The full build log is available from:
http://qa-logs.debian.net/2023/01/01/vdr-plugin-dvbsddevice_2.2.0-15_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230101;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230101&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=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 mark 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: vdr
Source-Version: 2.6.0-1.1
Done: Adrian Bunk 

We believe that the bug you reported is fixed in the latest version of
vdr, 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.
Adrian Bunk  (supplier of updated vdr 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, 26 Feb 2023 01:32:03 +0200
Source: vdr
Architecture: source
Version: 2.6.0-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian VDR Team 
Changed-By: Adrian Bunk 
Closes: 1026310
Changes:
 vdr (2.6.0-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Apply patch from Rogo to remove trailing newline from abiversion.
 (Closes: #1026310)
Checksums-Sha1:
 5c7d5017119d419137f07c0227a6ca77de2e1aa6 2136 vdr_2.6.0-1.1.dsc
 bf1c46543020a369895e67c72b02baef03504020 51300 vdr_2.6.0-1.1.debian.tar.xz
Checksums-Sha256:
 226c0a072b73103f1965a1ba593fec81d90c80b6292a03a5a7e4cd4e7cc2e5b2 2136 
vdr_2.6.0-1.1.dsc
 7bfd7297298e9838b17329308a2b36a5c0c12d33474b53f227492ca7194124de 51300 
vdr_2.6.0-1.1.debian.tar.xz
Files:
 be7446e9890863a0918a3e162158afe4 2136 video optional vdr_2.6.0-1.1.dsc
 dc672debb9fb43744077ddf83b3479ef 51300 video optional 
vdr_2.6.0-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmP6nNAACgkQiNJCh6LY
mLFlsBAAtD8rsriIPUiEEvqDCaZU8pEjRpfSV9snWrxuhqS/eHmqkdgtJWrl77R+
SWJHgNc27X7bnNwyjjPR/JDGM+/iEzwgESz+v2+M12Qu07LSEuHrIV1t4O0puy80
iSbEGizBULeMv5DUAuaEHDgyWCAskNq6utaczD4uF1xPMu5eRlu3EbtMKONJpb96
PS8yK25fcFlrPOkSoiOg7An+pS64EjtbnwsXKousY0zj2NrXJhCgg2qN8U8YKr/l
AY18Q6y2z5FueBob84t548mGmpjR/QIkTEtFa9HIiBodYwFVL6WtL4BuHx4brTh9
UrpHwGdY1IjeIH5sKCKHu3vTRfe/DioBE0/gqLfkTwamAuyyzclttB5AFIGQaR2J
nzyn8VjAxvU1Caphipqm3ZJ59iEZjap/4nKtW5p9qdIyQ++/E49

Bug#1027631: marked as done (vdr-plugin-epgsync: FTBFS: make: *** [debian/rules:7: binary] Error 25)

[Debian Bug Tracking System]

Your message dated Thu, 02 Mar 2023 10:20:49 +
with message-id 
and subject line Bug#1026310: fixed in vdr 2.6.0-1.1
has caused the Debian Bug report #1026310,
regarding vdr-plugin-epgsync: FTBFS: make: *** [debian/rules:7: binary] Error 25
to be marked as done.

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

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


-- 
1026310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026310
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vdr-plugin-epgsync
Version: 1.0.1-8
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230101 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> install -D libvdr-epgsync.so 
> /<>/debian/vdr-plugin-epgsync/usr/lib/vdr/plugins/libvdr-epgsync.so.2.6.0
> install -D -m644 po/de_DE.mo 
> /<>/debian/vdr-plugin-epgsync/usr/share/locale/de_DE/LC_MESSAGES/vdr-epgsync.mo
> install -D -m644 po/it_IT.mo 
> /<>/debian/vdr-plugin-epgsync/usr/share/locale/it_IT/LC_MESSAGES/vdr-epgsync.mo
> install -D -m644 po/sk_SK.mo 
> /<>/debian/vdr-plugin-epgsync/usr/share/locale/sk_SK/LC_MESSAGES/vdr-epgsync.mo
> make[1]: Leaving directory '/<>'
>dh_vdrplugin_enable
>dh_installdocs
>dh_installchangelogs
>dh_perl
>dh_link
>dh_strip_nondeterminism
>   Normalized 
> debian/vdr-plugin-epgsync/usr/share/locale/it_IT/LC_MESSAGES/vdr-epgsync.mo
>   Normalized 
> debian/vdr-plugin-epgsync/usr/share/locale/sk_SK/LC_MESSAGES/vdr-epgsync.mo
>   Normalized 
> debian/vdr-plugin-epgsync/usr/share/locale/de_DE/LC_MESSAGES/vdr-epgsync.mo
>dh_compress
>dh_fixperms
>dh_missing
>dh_dwz -a
>dh_strip -a
>dh_makeshlibs -a
>dh_shlibdeps -a
>dh_vdrplugin_depends
> dh_vdrplugin_depends: warning: Unescaped newlines in the value of a substvars 
> can cause broken substvars files (see #1025714).
> dh_vdrplugin_depends: warning: Hint: If you really need a newline character, 
> provide it as "${Newline}".
> dh_vdrplugin_depends: error: Bug in helper: The substvar must not contain a 
> raw newline character (vdr:Depends=vdr-abi-2.6.0-debian\n)
> make: *** [debian/rules:7: binary] Error 25


The full build log is available from:
http://qa-logs.debian.net/2023/01/01/vdr-plugin-epgsync_1.0.1-8_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230101;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230101&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=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 mark 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: vdr
Source-Version: 2.6.0-1.1
Done: Adrian Bunk 

We believe that the bug you reported is fixed in the latest version of
vdr, 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.
Adrian Bunk  (supplier of updated vdr 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, 26 Feb 2023 01:32:03 +0200
Source: vdr
Architecture: source
Version: 2.6.0-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian VDR Team 
Changed-By: Adrian Bunk 
Closes: 1026310
Changes:
 vdr (2.6.0-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Apply patch from Rogo to remove trailing newline from abiversion.
 (Closes: #1026310)
Checksums-Sha1:
 5c7d5017119d419137f07c0227a6ca77de2e1aa6 2136 vdr_2.6.0-1.1.dsc
 bf1c46543020a369895e67c72b02baef03504020 51300 vdr_2.6.0-1.1.debian.tar.xz
Checksums-Sha256:
 226c0a072b73103f1965a1ba593

Bug#1027630: marked as done (vdr-plugin-satip: FTBFS: make: *** [debian/rules:11: binary] Error 25)

[Debian Bug Tracking System]

Your message dated Thu, 02 Mar 2023 10:20:49 +
with message-id 
and subject line Bug#1026310: fixed in vdr 2.6.0-1.1
has caused the Debian Bug report #1026310,
regarding vdr-plugin-satip: FTBFS: make: *** [debian/rules:11: binary] Error 25
to be marked as done.

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

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


-- 
1026310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026310
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vdr-plugin-satip
Version: 2.4.1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230101 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> IN 
> /<>/debian/vdr-plugin-satip/usr/lib/vdr/plugins/libvdr-satip.so.2.6.0
> install -D libvdr-satip.so 
> /<>/debian/vdr-plugin-satip/usr/lib/vdr/plugins/libvdr-satip.so.2.6.0
> IN 
> /<>/debian/vdr-plugin-satip/usr/share/locale/ca_ES/LC_MESSAGES/vdr-satip.mo
> install -D -m644 po/ca_ES.mo 
> /<>/debian/vdr-plugin-satip/usr/share/locale/ca_ES/LC_MESSAGES/vdr-satip.mo
> IN 
> /<>/debian/vdr-plugin-satip/usr/share/locale/de_DE/LC_MESSAGES/vdr-satip.mo
> install -D -m644 po/de_DE.mo 
> /<>/debian/vdr-plugin-satip/usr/share/locale/de_DE/LC_MESSAGES/vdr-satip.mo
> IN 
> /<>/debian/vdr-plugin-satip/usr/share/locale/es_ES/LC_MESSAGES/vdr-satip.mo
> install -D -m644 po/es_ES.mo 
> /<>/debian/vdr-plugin-satip/usr/share/locale/es_ES/LC_MESSAGES/vdr-satip.mo
> IN 
> /<>/debian/vdr-plugin-satip/usr/share/locale/fi_FI/LC_MESSAGES/vdr-satip.mo
> install -D -m644 po/fi_FI.mo 
> /<>/debian/vdr-plugin-satip/usr/share/locale/fi_FI/LC_MESSAGES/vdr-satip.mo
> IN 
> /<>/debian/vdr-plugin-satip/usr/share/locale/pl_PL/LC_MESSAGES/vdr-satip.mo
> install -D -m644 po/pl_PL.mo 
> /<>/debian/vdr-plugin-satip/usr/share/locale/pl_PL/LC_MESSAGES/vdr-satip.mo
> make[1]: Leaving directory '/<>'
>dh_install
>dh_vdrplugin_enable
>dh_installdocs
>dh_installchangelogs
>dh_perl
>dh_link
>dh_strip_nondeterminism
>   Normalized 
> debian/vdr-plugin-satip/usr/share/locale/ca_ES/LC_MESSAGES/vdr-satip.mo
>   Normalized 
> debian/vdr-plugin-satip/usr/share/locale/es_ES/LC_MESSAGES/vdr-satip.mo
>   Normalized 
> debian/vdr-plugin-satip/usr/share/locale/de_DE/LC_MESSAGES/vdr-satip.mo
>   Normalized 
> debian/vdr-plugin-satip/usr/share/locale/fi_FI/LC_MESSAGES/vdr-satip.mo
>   Normalized 
> debian/vdr-plugin-satip/usr/share/locale/pl_PL/LC_MESSAGES/vdr-satip.mo
>dh_compress
>dh_fixperms
>dh_missing
>dh_dwz -a
>dh_strip -a
>dh_makeshlibs -a
>dh_shlibdeps -a
>dh_vdrplugin_depends
> dh_vdrplugin_depends: warning: Unescaped newlines in the value of a substvars 
> can cause broken substvars files (see #1025714).
> dh_vdrplugin_depends: warning: Hint: If you really need a newline character, 
> provide it as "${Newline}".
> dh_vdrplugin_depends: error: Bug in helper: The substvar must not contain a 
> raw newline character (vdr:Depends=vdr-abi-2.6.0-debian\n)
> make: *** [debian/rules:11: binary] Error 25


The full build log is available from:
http://qa-logs.debian.net/2023/01/01/vdr-plugin-satip_2.4.1-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230101;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230101&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=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 mark 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: vdr
Source-Version: 2.6.0-1.1
Done: Adrian Bunk 

We believe that the bug you reported is fixed in the latest version of
vdr, 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

Bug#1027609: marked as done (vdr-plugin-xineliboutput: FTBFS: make: *** [debian/rules:13: binary] Error 25)

[Debian Bug Tracking System]

Your message dated Thu, 02 Mar 2023 10:20:49 +
with message-id 
and subject line Bug#1026310: fixed in vdr 2.6.0-1.1
has caused the Debian Bug report #1026310,
regarding vdr-plugin-xineliboutput: FTBFS: make: *** [debian/rules:13: binary] 
Error 25
to be marked as done.

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

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


-- 
1026310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026310
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vdr-plugin-xineliboutput
Version: 2.2.0+git20211212-2.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230101 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_strip --dbgsym-migration='vdr-plugin-xineliboutput-dbg (<< 
> 2.1.0+git20190511-1~)'
> dh_strip --dbgsym-migration='libxineliboutput-fbfe-dbg (<< 
> 2.1.0+git20190511-1~)'
> dh_strip --dbgsym-migration='libxineliboutput-sxfe-dbg (<< 
> 2.1.0+git20190511-1~)'
> dh_strip --dbgsym-migration='xineliboutput-fbfe-dbg (<< 2.1.0+git20190511-1~)'
> dh_strip --dbgsym-migration='xineliboutput-sxfe-dbg (<< 2.1.0+git20190511-1~)'
> dh_strip --dbgsym-migration='libxine2-xvdr-dbg (<< 2.1.0+git20190511-1~)'
> make[1]: Leaving directory '/<>'
>dh_makeshlibs -a
>dh_shlibdeps -a
>dh_vdrplugin_depends
> dh_vdrplugin_depends: warning: Unescaped newlines in the value of a substvars 
> can cause broken substvars files (see #1025714).
> dh_vdrplugin_depends: warning: Hint: If you really need a newline character, 
> provide it as "${Newline}".
> dh_vdrplugin_depends: error: Bug in helper: The substvar must not contain a 
> raw newline character (vdr:Depends=vdr-abi-2.6.0-debian\n)
> make: *** [debian/rules:13: binary] Error 25


The full build log is available from:
http://qa-logs.debian.net/2023/01/01/vdr-plugin-xineliboutput_2.2.0+git20211212-2.1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230101;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230101&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=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 mark 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: vdr
Source-Version: 2.6.0-1.1
Done: Adrian Bunk 

We believe that the bug you reported is fixed in the latest version of
vdr, 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.
Adrian Bunk  (supplier of updated vdr 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, 26 Feb 2023 01:32:03 +0200
Source: vdr
Architecture: source
Version: 2.6.0-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian VDR Team 
Changed-By: Adrian Bunk 
Closes: 1026310
Changes:
 vdr (2.6.0-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Apply patch from Rogo to remove trailing newline from abiversion.
 (Closes: #1026310)
Checksums-Sha1:
 5c7d5017119d419137f07c0227a6ca77de2e1aa6 2136 vdr_2.6.0-1.1.dsc
 bf1c46543020a369895e67c72b02baef03504020 51300 vdr_2.6.0-1.1.debian.tar.xz
Checksums-Sha256:
 226c0a072b73103f1965a1ba593fec81d90c80b6292a03a5a7e4cd4e7cc2e5b2 2136 
vdr_2.6.0-1.1.dsc
 7bfd7297298e9838b17329308a2b36a5c0c12d33474b53f227492ca7194124de 51300 
vdr_2.6.0-1.1.debian.tar.xz
Files:
 be7446e9890863a0918a3e162158afe4 2136 video optional vdr_2.6.0-1.1.dsc
 dc672debb9fb43744077ddf83b3479ef 51300 video optional 
vdr_2.6.0-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLE

Bug#1027575: marked as done (vdr-plugin-epgsearch: FTBFS: make: *** [debian/rules:7: binary] Error 25)

[Debian Bug Tracking System]

Your message dated Thu, 02 Mar 2023 10:20:49 +
with message-id 
and subject line Bug#1026310: fixed in vdr 2.6.0-1.1
has caused the Debian Bug report #1026310,
regarding vdr-plugin-epgsearch: FTBFS: make: *** [debian/rules:7: binary] Error 
25
to be marked as done.

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

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


-- 
1026310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026310
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vdr-plugin-epgsearch
Version: 2.4.1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230101 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> IN install-epgsearch
> install -D libvdr-epgsearch.so 
> /<>/debian/vdr-plugin-epgsearch/usr/lib/vdr/plugins/libvdr-epgsearch.so.2.6.0
> IN install-epgsearchonly
> install -D libvdr-epgsearchonly.so 
> /<>/debian/vdr-plugin-epgsearch/usr/lib/vdr/plugins/libvdr-epgsearchonly.so.2.6.0
> IN install-conflictcheckonly
> install -D libvdr-conflictcheckonly.so 
> /<>/debian/vdr-plugin-epgsearch/usr/lib/vdr/plugins/libvdr-conflictcheckonly.so.2.6.0
> IN install-quickepgsearch
> install -D libvdr-quickepgsearch.so 
> /<>/debian/vdr-plugin-epgsearch/usr/lib/vdr/plugins/libvdr-quickepgsearch.so.2.6.0
> IN 
> /<>/debian/vdr-plugin-epgsearch/usr/share/locale/ca_ES/LC_MESSAGES/vdr-epgsearch.mo
> install -D -m644 po/ca_ES.mo 
> /<>/debian/vdr-plugin-epgsearch/usr/share/locale/ca_ES/LC_MESSAGES/vdr-epgsearch.mo
> IN 
> /<>/debian/vdr-plugin-epgsearch/usr/share/locale/cs_CZ/LC_MESSAGES/vdr-epgsearch.mo
> install -D -m644 po/cs_CZ.mo 
> /<>/debian/vdr-plugin-epgsearch/usr/share/locale/cs_CZ/LC_MESSAGES/vdr-epgsearch.mo
> IN 
> /<>/debian/vdr-plugin-epgsearch/usr/share/locale/da_DK/LC_MESSAGES/vdr-epgsearch.mo
> install -D -m644 po/da_DK.mo 
> /<>/debian/vdr-plugin-epgsearch/usr/share/locale/da_DK/LC_MESSAGES/vdr-epgsearch.mo
> IN 
> /<>/debian/vdr-plugin-epgsearch/usr/share/locale/de_DE/LC_MESSAGES/vdr-epgsearch.mo
> install -D -m644 po/de_DE.mo 
> /<>/debian/vdr-plugin-epgsearch/usr/share/locale/de_DE/LC_MESSAGES/vdr-epgsearch.mo
> IN 
> /<>/debian/vdr-plugin-epgsearch/usr/share/locale/el_GR/LC_MESSAGES/vdr-epgsearch.mo
> install -D -m644 po/el_GR.mo 
> /<>/debian/vdr-plugin-epgsearch/usr/share/locale/el_GR/LC_MESSAGES/vdr-epgsearch.mo
> IN 
> /<>/debian/vdr-plugin-epgsearch/usr/share/locale/es_ES/LC_MESSAGES/vdr-epgsearch.mo
> install -D -m644 po/es_ES.mo 
> /<>/debian/vdr-plugin-epgsearch/usr/share/locale/es_ES/LC_MESSAGES/vdr-epgsearch.mo
> IN 
> /<>/debian/vdr-plugin-epgsearch/usr/share/locale/et_EE/LC_MESSAGES/vdr-epgsearch.mo
> install -D -m644 po/et_EE.mo 
> /<>/debian/vdr-plugin-epgsearch/usr/share/locale/et_EE/LC_MESSAGES/vdr-epgsearch.mo
> IN 
> /<>/debian/vdr-plugin-epgsearch/usr/share/locale/fi_FI/LC_MESSAGES/vdr-epgsearch.mo
> install -D -m644 po/fi_FI.mo 
> /<>/debian/vdr-plugin-epgsearch/usr/share/locale/fi_FI/LC_MESSAGES/vdr-epgsearch.mo
> IN 
> /<>/debian/vdr-plugin-epgsearch/usr/share/locale/fr_FR/LC_MESSAGES/vdr-epgsearch.mo
> install -D -m644 po/fr_FR.mo 
> /<>/debian/vdr-plugin-epgsearch/usr/share/locale/fr_FR/LC_MESSAGES/vdr-epgsearch.mo
> IN 
> /<>/debian/vdr-plugin-epgsearch/usr/share/locale/hr_HR/LC_MESSAGES/vdr-epgsearch.mo
> install -D -m644 po/hr_HR.mo 
> /<>/debian/vdr-plugin-epgsearch/usr/share/locale/hr_HR/LC_MESSAGES/vdr-epgsearch.mo
> IN 
> /<>/debian/vdr-plugin-epgsearch/usr/share/locale/hu_HU/LC_MESSAGES/vdr-epgsearch.mo
> install -D -m644 po/hu_HU.mo 
> /<>/debian/vdr-plugin-epgsearch/usr/share/locale/hu_HU/LC_MESSAGES/vdr-epgsearch.mo
> IN 
> /<>/debian/vdr-plugin-epgsearch/usr/share/locale/it_IT/LC_MESSAGES/vdr-epgsearch.mo
> install -D -m644 po/it_IT.mo 
> /<>/debian/vdr-plugin-epgsearch/usr/share/locale/it_IT/LC_MESSAGES/vdr-epgsearch.mo
> IN 
> /<>/debian/vdr-plugin-epgsearch/usr/share/locale/lt_LT/LC_MESSAGES/vdr-epgsearch.mo
> install -D -m644 po/lt_LT.mo 
> /<>/debian/vdr-plugin-epgsearch/usr/share/locale/lt_LT/LC_MESSAGES/vdr-epgsearch.mo
> IN 
> /<>/debian/vdr-plugin-epgsearch/usr/share/locale/nl_NL/LC_MESSAGES/vdr-epgsearch.mo
> install -D -m644 po/nl_NL.mo 
> /<>/debian/vdr-plugin-epgsearch/usr/share/locale/nl_NL/LC_MESSAGES/vdr-epgsearch.mo
> IN 
> /<>/debian/vdr-plugin-epgsearch/usr/share/locale/nn_NO/LC_MESSAGES/vdr-epgsearch.mo
> install -D -m644 po/nn_NO.mo 
> /<>/debian/vdr-plugin-epgsearch/usr/share/locale/nn_NO/LC_MESSAGES/vdr-epgsearch.mo
> IN 
> /<>/debian/vdr-plugin-epgsearch/usr/share/locale/pl_PL/LC_MESSAGES/vdr-epgsear

Bug#1027532: marked as done (vdr-plugin-dvd: FTBFS: make: *** [debian/rules:7: binary] Error 25)

[Debian Bug Tracking System]

Your message dated Thu, 02 Mar 2023 10:20:49 +
with message-id 
and subject line Bug#1026310: fixed in vdr 2.6.0-1.1
has caused the Debian Bug report #1026310,
regarding vdr-plugin-dvd: FTBFS: make: *** [debian/rules:7: binary] Error 25
to be marked as done.

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

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


-- 
1026310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026310
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vdr-plugin-dvd
Version: 0.3.6~b03+git20211216-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230101 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> install -D libvdr-dvd.so 
> /<>/debian/vdr-plugin-dvd/usr/lib/vdr/plugins/libvdr-dvd.so.2.6.0
> install -D -m644 po/de_DE.mo 
> /<>/debian/vdr-plugin-dvd/usr/share/locale/de_DE/LC_MESSAGES/vdr-dvd.mo
> install -D -m644 po/ru_RU.mo 
> /<>/debian/vdr-plugin-dvd/usr/share/locale/ru_RU/LC_MESSAGES/vdr-dvd.mo
> make[1]: Leaving directory '/<>'
>dh_install
>dh_vdrplugin_enable
>dh_installdocs
>dh_installchangelogs
>dh_perl
>dh_link
>dh_strip_nondeterminism
>   Normalized 
> debian/vdr-plugin-dvd/usr/share/locale/ru_RU/LC_MESSAGES/vdr-dvd.mo
>   Normalized 
> debian/vdr-plugin-dvd/usr/share/locale/de_DE/LC_MESSAGES/vdr-dvd.mo
>dh_compress
>dh_fixperms
>dh_missing
>dh_dwz -a
>dh_strip -a
>dh_makeshlibs -a
>dh_shlibdeps -a
>dh_vdrplugin_depends
> dh_vdrplugin_depends: warning: Unescaped newlines in the value of a substvars 
> can cause broken substvars files (see #1025714).
> dh_vdrplugin_depends: warning: Hint: If you really need a newline character, 
> provide it as "${Newline}".
> dh_vdrplugin_depends: error: Bug in helper: The substvar must not contain a 
> raw newline character (vdr:Depends=vdr-abi-2.6.0-debian\n)
> make: *** [debian/rules:7: binary] Error 25


The full build log is available from:
http://qa-logs.debian.net/2023/01/01/vdr-plugin-dvd_0.3.6~b03+git20211216-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230101;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230101&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=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 mark 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: vdr
Source-Version: 2.6.0-1.1
Done: Adrian Bunk 

We believe that the bug you reported is fixed in the latest version of
vdr, 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.
Adrian Bunk  (supplier of updated vdr 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, 26 Feb 2023 01:32:03 +0200
Source: vdr
Architecture: source
Version: 2.6.0-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian VDR Team 
Changed-By: Adrian Bunk 
Closes: 1026310
Changes:
 vdr (2.6.0-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Apply patch from Rogo to remove trailing newline from abiversion.
 (Closes: #1026310)
Checksums-Sha1:
 5c7d5017119d419137f07c0227a6ca77de2e1aa6 2136 vdr_2.6.0-1.1.dsc
 bf1c46543020a369895e67c72b02baef03504020 51300 vdr_2.6.0-1.1.debian.tar.xz
Checksums-Sha256:
 226c0a072b73103f1965a1ba593fec81d90c80b6292a03a5a7e4cd4e7cc2e5b2 2136 
vdr_2.6.0-1.1.dsc
 7bfd7297298e9838b17329308a2b36a5c0c12d33474b53f227492ca7194124de 51300 
vdr_2.6.0-1.1.debian.tar.xz
Files:
 be7446e9890863a0918a3e162158afe4 2136 video optio

Bug#1027568: marked as done (vdr-plugin-fritzbox: FTBFS: make: *** [debian/rules:9: binary] Error 25)

[Debian Bug Tracking System]

Your message dated Thu, 02 Mar 2023 10:20:49 +
with message-id 
and subject line Bug#1026310: fixed in vdr 2.6.0-1.1
has caused the Debian Bug report #1026310,
regarding vdr-plugin-fritzbox: FTBFS: make: *** [debian/rules:9: binary] Error 
25
to be marked as done.

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

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


-- 
1026310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026310
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vdr-plugin-fritzbox
Version: 1.5.4-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230101 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>/libconv++'
> make[2]: 'libconv++.a' is up to date.
> make[2]: Leaving directory '/<>/libconv++'
> install -D -m644 po/fr_FR.mo 
> /<>/debian/vdr-plugin-fritzbox/usr/share/locale/fr_FR/LC_MESSAGES/vdr-fritzbox.mo
> install -D -m644 po/it_IT.mo 
> /<>/debian/vdr-plugin-fritzbox/usr/share/locale/it_IT/LC_MESSAGES/vdr-fritzbox.mo
> install -D -m644 po/ru_RU.mo 
> /<>/debian/vdr-plugin-fritzbox/usr/share/locale/ru_RU/LC_MESSAGES/vdr-fritzbox.mo
> install -D -m644 po/tr_TR.mo 
> /<>/debian/vdr-plugin-fritzbox/usr/share/locale/tr_TR/LC_MESSAGES/vdr-fritzbox.mo
> install -D libvdr-fritzbox.so 
> /<>/debian/vdr-plugin-fritzbox/usr/lib/vdr/plugins/libvdr-fritzbox.so.2.6.0
> make[1]: Leaving directory '/<>'
>dh_install
>dh_vdrplugin_enable
>dh_installdocs
>dh_installchangelogs
>dh_perl
>dh_link
>dh_strip_nondeterminism
>   Normalized 
> debian/vdr-plugin-fritzbox/usr/share/locale/it_IT/LC_MESSAGES/vdr-fritzbox.mo
>   Normalized 
> debian/vdr-plugin-fritzbox/usr/share/locale/fr_FR/LC_MESSAGES/vdr-fritzbox.mo
>   Normalized 
> debian/vdr-plugin-fritzbox/usr/share/locale/ru_RU/LC_MESSAGES/vdr-fritzbox.mo
>   Normalized 
> debian/vdr-plugin-fritzbox/usr/share/locale/de_DE/LC_MESSAGES/vdr-fritzbox.mo
>   Normalized 
> debian/vdr-plugin-fritzbox/usr/share/locale/tr_TR/LC_MESSAGES/vdr-fritzbox.mo
>dh_compress
>dh_fixperms
>dh_missing
>dh_dwz -a
>dh_strip -a
>dh_makeshlibs -a
>dh_shlibdeps -a
>dh_vdrplugin_depends
> dh_vdrplugin_depends: warning: Unescaped newlines in the value of a substvars 
> can cause broken substvars files (see #1025714).
> dh_vdrplugin_depends: warning: Hint: If you really need a newline character, 
> provide it as "${Newline}".
> dh_vdrplugin_depends: error: Bug in helper: The substvar must not contain a 
> raw newline character (vdr:Depends=vdr-abi-2.6.0-debian\n)
> make: *** [debian/rules:9: binary] Error 25


The full build log is available from:
http://qa-logs.debian.net/2023/01/01/vdr-plugin-fritzbox_1.5.4-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230101;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230101&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=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 mark 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: vdr
Source-Version: 2.6.0-1.1
Done: Adrian Bunk 

We believe that the bug you reported is fixed in the latest version of
vdr, 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.
Adrian Bunk  (supplier of updated vdr 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, 26 Feb 2023 01:32:03 +0200
Source: vdr
Architecture: source
Version: 2.6.0-1.1
Distribution: unstable
Urgency: medium
Main

Bug#1027543: marked as done (vdr-plugin-osdserver: FTBFS: make: *** [debian/rules:10: binary] Error 25)

[Debian Bug Tracking System]

Your message dated Thu, 02 Mar 2023 10:20:49 +
with message-id 
and subject line Bug#1026310: fixed in vdr 2.6.0-1.1
has caused the Debian Bug report #1026310,
regarding vdr-plugin-osdserver: FTBFS: make: *** [debian/rules:10: binary] 
Error 25
to be marked as done.

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

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


-- 
1026310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026310
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vdr-plugin-osdserver
Version: 0.1.3-22
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230101 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  fakeroot debian/rules binary
> dh binary --with vdrplugin
>dh_testroot
>dh_prep
>dh_auto_install --destdir=debian/vdr-plugin-osdserver/
>dh_install
>dh_vdrplugin_enable
>dh_installdocs
>dh_installchangelogs
>dh_installexamples
>dh_perl
>dh_link
>dh_strip_nondeterminism
>dh_compress
>dh_fixperms
>dh_missing
>dh_dwz -a
>dh_strip -a
>dh_makeshlibs -a
>dh_shlibdeps -a
>dh_vdrplugin_depends
> dh_vdrplugin_depends: warning: Unescaped newlines in the value of a substvars 
> can cause broken substvars files (see #1025714).
> dh_vdrplugin_depends: warning: Hint: If you really need a newline character, 
> provide it as "${Newline}".
> dh_vdrplugin_depends: error: Bug in helper: The substvar must not contain a 
> raw newline character (vdr:Depends=vdr-abi-2.6.0-debian\n)
> make: *** [debian/rules:10: binary] Error 25


The full build log is available from:
http://qa-logs.debian.net/2023/01/01/vdr-plugin-osdserver_0.1.3-22_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230101;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230101&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=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 mark 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: vdr
Source-Version: 2.6.0-1.1
Done: Adrian Bunk 

We believe that the bug you reported is fixed in the latest version of
vdr, 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.
Adrian Bunk  (supplier of updated vdr 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, 26 Feb 2023 01:32:03 +0200
Source: vdr
Architecture: source
Version: 2.6.0-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian VDR Team 
Changed-By: Adrian Bunk 
Closes: 1026310
Changes:
 vdr (2.6.0-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Apply patch from Rogo to remove trailing newline from abiversion.
 (Closes: #1026310)
Checksums-Sha1:
 5c7d5017119d419137f07c0227a6ca77de2e1aa6 2136 vdr_2.6.0-1.1.dsc
 bf1c46543020a369895e67c72b02baef03504020 51300 vdr_2.6.0-1.1.debian.tar.xz
Checksums-Sha256:
 226c0a072b73103f1965a1ba593fec81d90c80b6292a03a5a7e4cd4e7cc2e5b2 2136 
vdr_2.6.0-1.1.dsc
 7bfd7297298e9838b17329308a2b36a5c0c12d33474b53f227492ca7194124de 51300 
vdr_2.6.0-1.1.debian.tar.xz
Files:
 be7446e9890863a0918a3e162158afe4 2136 video optional vdr_2.6.0-1.1.dsc
 dc672debb9fb43744077ddf83b3479ef 51300 video optional 
vdr_2.6.0-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmP6nNAACgkQiNJCh6LY
mLFlsBAAtD8rsriIPUiEEvqDCaZU8pEjRpfSV9snWrxuhqS/eHmqkdgtJWrl77R+
SWJHgNc27X7bnNwyjjPR/JDGM+/iEzwgESz+v2+M12Qu07LSEuHrIV1t4O0puy80
iSbEGizBULeMv5DUAuaEHDgyWCAskNq6utaczD4uF1xPMu5eRlu3EbtMKONJ

Bug#1027499: marked as done (vdr-plugin-svdrposd: FTBFS: make: *** [debian/rules:7: binary] Error 25)

[Debian Bug Tracking System]

Your message dated Thu, 02 Mar 2023 10:20:49 +
with message-id 
and subject line Bug#1026310: fixed in vdr 2.6.0-1.1
has caused the Debian Bug report #1026310,
regarding vdr-plugin-svdrposd: FTBFS: make: *** [debian/rules:7: binary] Error 
25
to be marked as done.

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

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


-- 
1026310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026310
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vdr-plugin-svdrposd
Version: 1.0.0-11
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230101 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> install -D libvdr-svdrposd.so 
> /<>/debian/vdr-plugin-svdrposd/usr/lib/vdr/plugins/libvdr-svdrposd.so.2.6.0
> make[1]: Leaving directory '/<>'
>dh_vdrplugin_enable
>dh_installdocs
>dh_installchangelogs
>dh_perl
>dh_link
>dh_strip_nondeterminism
>dh_compress
>dh_fixperms
>dh_missing
>dh_dwz -a
>dh_strip -a
>dh_makeshlibs -a
>dh_shlibdeps -a
>dh_vdrplugin_depends
> dh_vdrplugin_depends: warning: Unescaped newlines in the value of a substvars 
> can cause broken substvars files (see #1025714).
> dh_vdrplugin_depends: warning: Hint: If you really need a newline character, 
> provide it as "${Newline}".
> dh_vdrplugin_depends: error: Bug in helper: The substvar must not contain a 
> raw newline character (vdr:Depends=vdr-abi-2.6.0-debian\n)
> make: *** [debian/rules:7: binary] Error 25


The full build log is available from:
http://qa-logs.debian.net/2023/01/01/vdr-plugin-svdrposd_1.0.0-11_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230101;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230101&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=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 mark 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: vdr
Source-Version: 2.6.0-1.1
Done: Adrian Bunk 

We believe that the bug you reported is fixed in the latest version of
vdr, 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.
Adrian Bunk  (supplier of updated vdr 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, 26 Feb 2023 01:32:03 +0200
Source: vdr
Architecture: source
Version: 2.6.0-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian VDR Team 
Changed-By: Adrian Bunk 
Closes: 1026310
Changes:
 vdr (2.6.0-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Apply patch from Rogo to remove trailing newline from abiversion.
 (Closes: #1026310)
Checksums-Sha1:
 5c7d5017119d419137f07c0227a6ca77de2e1aa6 2136 vdr_2.6.0-1.1.dsc
 bf1c46543020a369895e67c72b02baef03504020 51300 vdr_2.6.0-1.1.debian.tar.xz
Checksums-Sha256:
 226c0a072b73103f1965a1ba593fec81d90c80b6292a03a5a7e4cd4e7cc2e5b2 2136 
vdr_2.6.0-1.1.dsc
 7bfd7297298e9838b17329308a2b36a5c0c12d33474b53f227492ca7194124de 51300 
vdr_2.6.0-1.1.debian.tar.xz
Files:
 be7446e9890863a0918a3e162158afe4 2136 video optional vdr_2.6.0-1.1.dsc
 dc672debb9fb43744077ddf83b3479ef 51300 video optional 
vdr_2.6.0-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmP6nNAACgkQiNJCh6LY
mLFlsBAAtD8rsriIPUiEEvqDCaZU8pEjRpfSV9snWrxuhqS/eHmqkdgtJWrl77R+
SWJHgNc27X7bnNwyjjPR/JDGM+/iEzwgESz+v2+M12Qu07LSEuHrIV1t4O0puy80
iSbEGizBULeMv5DUAuaEHDgyWCAskNq6utaczD4uF1xPMu5eRlu3EbtMKONJpb96
PS8yK25fc

Bug#1027498: marked as done (vdr-plugin-streamdev: FTBFS: make: *** [debian/rules:9: binary] Error 25)

[Debian Bug Tracking System]

Your message dated Thu, 02 Mar 2023 10:20:49 +
with message-id 
and subject line Bug#1026310: fixed in vdr 2.6.0-1.1
has caused the Debian Bug report #1026310,
regarding vdr-plugin-streamdev: FTBFS: make: *** [debian/rules:9: binary] Error 
25
to be marked as done.

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

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


-- 
1026310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026310
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vdr-plugin-streamdev
Version: 0.6.1+git20180514-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230101 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>/server'
> install -D libvdr-streamdev-server.so 
> /<>/debian/tmp/usr/lib/vdr/plugins/libvdr-streamdev-server.so.2.6.0
> install -D -m644 po/de_DE.mo 
> /<>/debian/tmp/usr/share/locale/de_DE/LC_MESSAGES/vdr-streamdev-server.mo
> install -D -m644 po/es_ES.mo 
> /<>/debian/tmp/usr/share/locale/es_ES/LC_MESSAGES/vdr-streamdev-server.mo
> install -D -m644 po/fi_FI.mo 
> /<>/debian/tmp/usr/share/locale/fi_FI/LC_MESSAGES/vdr-streamdev-server.mo
> install -D -m644 po/fr_FR.mo 
> /<>/debian/tmp/usr/share/locale/fr_FR/LC_MESSAGES/vdr-streamdev-server.mo
> install -D -m644 po/it_IT.mo 
> /<>/debian/tmp/usr/share/locale/it_IT/LC_MESSAGES/vdr-streamdev-server.mo
> install -D -m644 po/lt_LT.mo 
> /<>/debian/tmp/usr/share/locale/lt_LT/LC_MESSAGES/vdr-streamdev-server.mo
> install -D -m644 po/pl_PL.mo 
> /<>/debian/tmp/usr/share/locale/pl_PL/LC_MESSAGES/vdr-streamdev-server.mo
> install -D -m644 po/ru_RU.mo 
> /<>/debian/tmp/usr/share/locale/ru_RU/LC_MESSAGES/vdr-streamdev-server.mo
> install -D -m644 po/sk_SK.mo 
> /<>/debian/tmp/usr/share/locale/sk_SK/LC_MESSAGES/vdr-streamdev-server.mo
> make[2]: Leaving directory '/<>/server'
> # installs to /usr/lib/vdr/plugins/libvdr-streamdev-server.so.2.6.0
> make[1]: Leaving directory '/<>'
>dh_install
>dh_vdrplugin_enable
>dh_installdocs
>dh_installchangelogs
>dh_installexamples
>dh_perl
>dh_link
>dh_strip_nondeterminism
>   Normalized 
> debian/vdr-plugin-streamdev-client/usr/share/locale/sk_SK/LC_MESSAGES/vdr-streamdev-client.mo
>   Normalized 
> debian/vdr-plugin-streamdev-client/usr/share/locale/fr_FR/LC_MESSAGES/vdr-streamdev-client.mo
>   Normalized 
> debian/vdr-plugin-streamdev-client/usr/share/locale/it_IT/LC_MESSAGES/vdr-streamdev-client.mo
>   Normalized 
> debian/vdr-plugin-streamdev-client/usr/share/locale/ru_RU/LC_MESSAGES/vdr-streamdev-client.mo
>   Normalized 
> debian/vdr-plugin-streamdev-client/usr/share/locale/lt_LT/LC_MESSAGES/vdr-streamdev-client.mo
>   Normalized 
> debian/vdr-plugin-streamdev-client/usr/share/locale/es_ES/LC_MESSAGES/vdr-streamdev-client.mo
>   Normalized 
> debian/vdr-plugin-streamdev-client/usr/share/locale/pl_PL/LC_MESSAGES/vdr-streamdev-client.mo
>   Normalized 
> debian/vdr-plugin-streamdev-client/usr/share/locale/de_DE/LC_MESSAGES/vdr-streamdev-client.mo
>   Normalized 
> debian/vdr-plugin-streamdev-client/usr/share/locale/fi_FI/LC_MESSAGES/vdr-streamdev-client.mo
>   Normalized 
> debian/vdr-plugin-streamdev-server/usr/share/locale/sk_SK/LC_MESSAGES/vdr-streamdev-server.mo
>   Normalized 
> debian/vdr-plugin-streamdev-server/usr/share/locale/fr_FR/LC_MESSAGES/vdr-streamdev-server.mo
>   Normalized 
> debian/vdr-plugin-streamdev-server/usr/share/locale/it_IT/LC_MESSAGES/vdr-streamdev-server.mo
>   Normalized 
> debian/vdr-plugin-streamdev-server/usr/share/locale/ru_RU/LC_MESSAGES/vdr-streamdev-server.mo
>   Normalized 
> debian/vdr-plugin-streamdev-server/usr/share/locale/de_DE/LC_MESSAGES/vdr-streamdev-server.mo
>   Normalized 
> debian/vdr-plugin-streamdev-server/usr/share/locale/fi_FI/LC_MESSAGES/vdr-streamdev-server.mo
>   Normalized 
> debian/vdr-plugin-streamdev-server/usr/share/locale/pl_PL/LC_MESSAGES/vdr-streamdev-server.mo
>   Normalized 
> debian/vdr-plugin-streamdev-server/usr/share/locale/lt_LT/LC_MESSAGES/vdr-streamdev-server.mo
>   Normalized 
> debian/vdr-plugin-streamdev-server/usr/share/locale/es_ES/LC_MESSAGES/vdr-streamdev-server.mo
>dh_compress
>dh_fixperms
>dh_missing
>dh_dwz -a
>dh_strip -a
>dh_makeshlibs -a
>dh_shlibdeps -a
>dh_vdrplugin_depends
> dh_vdrplugin_depends: warning: Unescaped newlines in the value of a substvars 
> can cause broken substvars files (see #1025714).
> dh_vdrplugin_depends: warning: Hint: If you rea

Bug#1026533: marked as done (vdr-plugin-femon: FTBFS: make: *** [debian/rules:7: binary] Error 25)

[Debian Bug Tracking System]

Your message dated Thu, 02 Mar 2023 10:20:49 +
with message-id 
and subject line Bug#1026310: fixed in vdr 2.6.0-1.1
has caused the Debian Bug report #1026310,
regarding vdr-plugin-femon: FTBFS: make: *** [debian/rules:7: binary] Error 25
to be marked as done.

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

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


-- 
1026310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026310
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vdr-plugin-femon
Version: 2.4.0-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> IN 
> /<>/debian/vdr-plugin-femon/usr/lib/vdr/plugins/libvdr-femon.so.2.6.0
> install -D libvdr-femon.so 
> /<>/debian/vdr-plugin-femon/usr/lib/vdr/plugins/libvdr-femon.so.2.6.0
> IN 
> /<>/debian/vdr-plugin-femon/usr/share/locale/de_DE/LC_MESSAGES/vdr-femon.mo
> install -D -m644 po/de_DE.mo 
> /<>/debian/vdr-plugin-femon/usr/share/locale/de_DE/LC_MESSAGES/vdr-femon.mo
> IN 
> /<>/debian/vdr-plugin-femon/usr/share/locale/es_ES/LC_MESSAGES/vdr-femon.mo
> install -D -m644 po/es_ES.mo 
> /<>/debian/vdr-plugin-femon/usr/share/locale/es_ES/LC_MESSAGES/vdr-femon.mo
> IN 
> /<>/debian/vdr-plugin-femon/usr/share/locale/et_EE/LC_MESSAGES/vdr-femon.mo
> install -D -m644 po/et_EE.mo 
> /<>/debian/vdr-plugin-femon/usr/share/locale/et_EE/LC_MESSAGES/vdr-femon.mo
> IN 
> /<>/debian/vdr-plugin-femon/usr/share/locale/fi_FI/LC_MESSAGES/vdr-femon.mo
> install -D -m644 po/fi_FI.mo 
> /<>/debian/vdr-plugin-femon/usr/share/locale/fi_FI/LC_MESSAGES/vdr-femon.mo
> IN 
> /<>/debian/vdr-plugin-femon/usr/share/locale/fr_FR/LC_MESSAGES/vdr-femon.mo
> install -D -m644 po/fr_FR.mo 
> /<>/debian/vdr-plugin-femon/usr/share/locale/fr_FR/LC_MESSAGES/vdr-femon.mo
> IN 
> /<>/debian/vdr-plugin-femon/usr/share/locale/hu_HU/LC_MESSAGES/vdr-femon.mo
> install -D -m644 po/hu_HU.mo 
> /<>/debian/vdr-plugin-femon/usr/share/locale/hu_HU/LC_MESSAGES/vdr-femon.mo
> IN 
> /<>/debian/vdr-plugin-femon/usr/share/locale/it_IT/LC_MESSAGES/vdr-femon.mo
> install -D -m644 po/it_IT.mo 
> /<>/debian/vdr-plugin-femon/usr/share/locale/it_IT/LC_MESSAGES/vdr-femon.mo
> IN 
> /<>/debian/vdr-plugin-femon/usr/share/locale/lt_LT/LC_MESSAGES/vdr-femon.mo
> install -D -m644 po/lt_LT.mo 
> /<>/debian/vdr-plugin-femon/usr/share/locale/lt_LT/LC_MESSAGES/vdr-femon.mo
> IN 
> /<>/debian/vdr-plugin-femon/usr/share/locale/pl_PL/LC_MESSAGES/vdr-femon.mo
> install -D -m644 po/pl_PL.mo 
> /<>/debian/vdr-plugin-femon/usr/share/locale/pl_PL/LC_MESSAGES/vdr-femon.mo
> IN 
> /<>/debian/vdr-plugin-femon/usr/share/locale/ru_RU/LC_MESSAGES/vdr-femon.mo
> install -D -m644 po/ru_RU.mo 
> /<>/debian/vdr-plugin-femon/usr/share/locale/ru_RU/LC_MESSAGES/vdr-femon.mo
> IN 
> /<>/debian/vdr-plugin-femon/usr/share/locale/sk_SK/LC_MESSAGES/vdr-femon.mo
> install -D -m644 po/sk_SK.mo 
> /<>/debian/vdr-plugin-femon/usr/share/locale/sk_SK/LC_MESSAGES/vdr-femon.mo
> IN 
> /<>/debian/vdr-plugin-femon/usr/share/locale/uk_UA/LC_MESSAGES/vdr-femon.mo
> install -D -m644 po/uk_UA.mo 
> /<>/debian/vdr-plugin-femon/usr/share/locale/uk_UA/LC_MESSAGES/vdr-femon.mo
> IN 
> /<>/debian/vdr-plugin-femon/usr/share/locale/zh_CN/LC_MESSAGES/vdr-femon.mo
> install -D -m644 po/zh_CN.mo 
> /<>/debian/vdr-plugin-femon/usr/share/locale/zh_CN/LC_MESSAGES/vdr-femon.mo
> IN 
> /<>/debian/vdr-plugin-femon/usr/share/locale/zh_TW/LC_MESSAGES/vdr-femon.mo
> install -D -m644 po/zh_TW.mo 
> /<>/debian/vdr-plugin-femon/usr/share/locale/zh_TW/LC_MESSAGES/vdr-femon.mo
> make[1]: Leaving directory '/<>'
>dh_vdrplugin_enable
>dh_installdocs
>dh_installchangelogs
>dh_perl
>dh_link
>dh_strip_nondeterminism
>   Normalized 
> debian/vdr-plugin-femon/usr/share/locale/uk_UA/LC_MESSAGES/vdr-femon.mo
>   Normalized 
> debian/vdr-plugin-femon/usr/share/locale/fr_FR/LC_MESSAGES/vdr-femon.mo
>   Normalized 
> debian/vdr-plugin-femon/usr/share/locale/it_IT/LC_MESSAGES/vdr-femon.mo
>   Normalized 
> debian/vdr-plugin-femon/usr/share/locale/ru_RU/LC_MESSAGES/vdr-femon.mo
>   Normalized 
> debian/vdr-plugin-femon/usr/share/locale/zh_TW/LC_MESSAGES/vdr-femon.mo
>   Normalized 
> debian/vdr-plugin-femon/usr/share/locale/sk_SK/LC_MESSAGES/vdr-femon.mo
>   Normalized 
> debian/vdr-plugin-femon/usr/share/locale/lt_LT/LC_MESSAGES/vdr-femon.mo
>   Normalized 
> debian/vdr-plugin-femon/usr/share/locale/es_ES/LC_MESSAGES/vdr-femon.mo
>   Normalized 
> debian/vdr-pl

Bug#1026475: marked as done (vdr-plugin-remote: FTBFS: make: *** [debian/rules:7: binary] Error 25)

[Debian Bug Tracking System]

Your message dated Thu, 02 Mar 2023 10:20:49 +
with message-id 
and subject line Bug#1026310: fixed in vdr 2.6.0-1.1
has caused the Debian Bug report #1026310,
regarding vdr-plugin-remote: FTBFS: make: *** [debian/rules:7: binary] Error 25
to be marked as done.

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

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


-- 
1026310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026310
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vdr-plugin-remote
Version: 0.7.0-6
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> install -D libvdr-remote.so 
> /<>/debian/vdr-plugin-remote/usr/lib/vdr/plugins/libvdr-remote.so.2.6.0
> install -D -m644 po/de_DE.mo 
> /<>/debian/vdr-plugin-remote/usr/share/locale/de_DE/LC_MESSAGES/vdr-remote.mo
> install -D -m644 po/fi_FI.mo 
> /<>/debian/vdr-plugin-remote/usr/share/locale/fi_FI/LC_MESSAGES/vdr-remote.mo
> install -D -m644 po/fr_FR.mo 
> /<>/debian/vdr-plugin-remote/usr/share/locale/fr_FR/LC_MESSAGES/vdr-remote.mo
> install -D -m644 po/it_IT.mo 
> /<>/debian/vdr-plugin-remote/usr/share/locale/it_IT/LC_MESSAGES/vdr-remote.mo
> install -D -m644 po/pl_PL.mo 
> /<>/debian/vdr-plugin-remote/usr/share/locale/pl_PL/LC_MESSAGES/vdr-remote.mo
> install -D -m644 po/ru_RU.mo 
> /<>/debian/vdr-plugin-remote/usr/share/locale/ru_RU/LC_MESSAGES/vdr-remote.mo
> make[1]: Leaving directory '/<>'
>dh_install
>dh_vdrplugin_enable
>dh_installdocs
>dh_installchangelogs
>dh_perl
>dh_link
>dh_strip_nondeterminism
>   Normalized 
> debian/vdr-plugin-remote/usr/share/locale/it_IT/LC_MESSAGES/vdr-remote.mo
>   Normalized 
> debian/vdr-plugin-remote/usr/share/locale/fr_FR/LC_MESSAGES/vdr-remote.mo
>   Normalized 
> debian/vdr-plugin-remote/usr/share/locale/ru_RU/LC_MESSAGES/vdr-remote.mo
>   Normalized 
> debian/vdr-plugin-remote/usr/share/locale/de_DE/LC_MESSAGES/vdr-remote.mo
>   Normalized 
> debian/vdr-plugin-remote/usr/share/locale/fi_FI/LC_MESSAGES/vdr-remote.mo
>   Normalized 
> debian/vdr-plugin-remote/usr/share/locale/pl_PL/LC_MESSAGES/vdr-remote.mo
>dh_compress
>dh_fixperms
>dh_missing
>dh_dwz -a
>dh_strip -a
>dh_makeshlibs -a
>dh_shlibdeps -a
>dh_vdrplugin_depends
> dh_vdrplugin_depends: warning: Unescaped newlines in the value of a substvars 
> can cause broken substvars files (see #1025714).
> dh_vdrplugin_depends: warning: Hint: If you really need a newline character, 
> provide it as "${Newline}".
> dh_vdrplugin_depends: error: Bug in helper: The substvar must not contain a 
> raw newline character (vdr:Depends=vdr-abi-2.6.0-debian\n)
> make: *** [debian/rules:7: binary] Error 25


The full build log is available from:
http://qa-logs.debian.net/2022/12/20/vdr-plugin-remote_0.7.0-6_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221220;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20221220&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=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 mark 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: vdr
Source-Version: 2.6.0-1.1
Done: Adrian Bunk 

We believe that the bug you reported is fixed in the latest version of
vdr, 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.
Adrian Bunk  (supplier of updated vdr 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 SIG

Bug#1026310: marked as done (vdr-dev: dh_vdrplugin_depends fail with "error: Bug in helper:")

[Debian Bug Tracking System]

Your message dated Thu, 02 Mar 2023 10:20:49 +
with message-id 
and subject line Bug#1026310: fixed in vdr 2.6.0-1.1
has caused the Debian Bug report #1026310,
regarding vdr-dev: dh_vdrplugin_depends fail with "error: Bug in helper:"
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.)


-- 
1026310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026310
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: vdr-dev
Version: 2.6.0-1+b1
Severity: normal

Dear Maintainer,

I don't know if this is a bug in debhelepr or in  vdr-dev

Feel free to reassign if needed.

,
| dh_vdrplugin_depends: warning: Unescaped newlines in the value of a substvars 
can cause broken substvars files (see #1025714).
| dh_vdrplugin_depends: warning: Hint: If you really need a newline character, 
provide it as "${Newline}".
| dh_vdrplugin_depends: error: Bug in helper: The substvar must not contain a 
raw newline character (vdr:Depends=vdr-abi-2.6.0-debian\n)
`

Christian


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

Kernel: Linux 6.0.13 (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages vdr-dev depends on:
ii  debhelper   13.11.3
ii  linux-libc-dev  6.0.12-1

vdr-dev recommends no packages.

Versions of packages vdr-dev suggests:
ii  dh-make  2.202204
ii  make 4.3-4.1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: vdr
Source-Version: 2.6.0-1.1
Done: Adrian Bunk 

We believe that the bug you reported is fixed in the latest version of
vdr, 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.
Adrian Bunk  (supplier of updated vdr 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, 26 Feb 2023 01:32:03 +0200
Source: vdr
Architecture: source
Version: 2.6.0-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian VDR Team 
Changed-By: Adrian Bunk 
Closes: 1026310
Changes:
 vdr (2.6.0-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Apply patch from Rogo to remove trailing newline from abiversion.
 (Closes: #1026310)
Checksums-Sha1:
 5c7d5017119d419137f07c0227a6ca77de2e1aa6 2136 vdr_2.6.0-1.1.dsc
 bf1c46543020a369895e67c72b02baef03504020 51300 vdr_2.6.0-1.1.debian.tar.xz
Checksums-Sha256:
 226c0a072b73103f1965a1ba593fec81d90c80b6292a03a5a7e4cd4e7cc2e5b2 2136 
vdr_2.6.0-1.1.dsc
 7bfd7297298e9838b17329308a2b36a5c0c12d33474b53f227492ca7194124de 51300 
vdr_2.6.0-1.1.debian.tar.xz
Files:
 be7446e9890863a0918a3e162158afe4 2136 video optional vdr_2.6.0-1.1.dsc
 dc672debb9fb43744077ddf83b3479ef 51300 video optional 
vdr_2.6.0-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmP6nNAACgkQiNJCh6LY
mLFlsBAAtD8rsriIPUiEEvqDCaZU8pEjRpfSV9snWrxuhqS/eHmqkdgtJWrl77R+
SWJHgNc27X7bnNwyjjPR/JDGM+/iEzwgESz+v2+M12Qu07LSEuHrIV1t4O0puy80
iSbEGizBULeMv5DUAuaEHDgyWCAskNq6utaczD4uF1xPMu5eRlu3EbtMKONJpb96
PS8yK25fcFlrPOkSoiOg7An+pS64EjtbnwsXKousY0zj2NrXJhCgg2qN8U8YKr/l
AY18Q6y2z5FueBob84t548mGmpjR/QIkTEtFa9HIiBodYwFVL6WtL4BuHx4brTh9
UrpHwGdY1IjeIH5sKCKHu3vTRfe/DioBE0/gqLfkTwamAuyyzclttB5AFIGQaR2J
nzyn8VjAxvU1Caphipqm3ZJ59iEZjap/4nKtW5p9qdIyQ++/E4916wcnC9s5Vt1n
z0gZtsRtiqFJeBGE29NRzR6qJuPdYUN7pmdB+tqmUAtQDHgEnnpyaCaDiqRgTl+9
Pe3iBP6BsGAM8759uHxI5hxdFNrYZMHLQO6QRh7V+SUseaCCgKi2mvAEvy0gS7vp
pC9Mfup/D17k/KbYFvAWZk0AIW4oGK+pwVR20IX94wmfC+pOiJa82UUoXQauU5Ib
HTLErcSkhl28nr8wQhH0vJKuaXZICM/PGub4LKN7PwuIJxfbXLw=
=Ed3S
-END PGP SIGNATURE End Message ---

Bug#1026106: marked as done (pacparser: CVE-2019-25078: memory overwrite issue for pacparser_find_proxy function)

[Debian Bug Tracking System]

Your message dated Thu, 02 Mar 2023 10:20:38 +
with message-id 
and subject line Bug#1026106: fixed in pacparser 1.3.6-1.4
has caused the Debian Bug report #1026106,
regarding pacparser: CVE-2019-25078: memory overwrite issue for 
pacparser_find_proxy function
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.)


-- 
1026106: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026106
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pacparser
Version: 1.3.6-1.1
Severity: important
Tags: security upstream
Forwarded: https://github.com/manugarg/pacparser/issues/99
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for pacparser.

CVE-2019-25078[0]:
| A vulnerability classified as problematic was found in pacparser up to
| 1.3.x. Affected by this vulnerability is the function
| pacparser_find_proxy of the file src/pacparser.c. The manipulation of
| the argument url leads to buffer overflow. Attacking locally is a
| requirement. Upgrading to version 1.4.0 is able to address this issue.
| The name of the patch is 853e8f45607cb07b877ffd270c63dbcdd5201ad9. It
| is recommended to upgrade the affected component. The associated
| identifier of this vulnerability is VDB-215443.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-25078
https://www.cve.org/CVERecord?id=CVE-2019-25078
[1] https://github.com/manugarg/pacparser/issues/99
[2] 
https://github.com/manugarg/pacparser/commit/853e8f45607cb07b877ffd270c63dbcdd5201ad9

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: pacparser
Source-Version: 1.3.6-1.4
Done: Adrian Bunk 

We believe that the bug you reported is fixed in the latest version of
pacparser, 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.
Adrian Bunk  (supplier of updated pacparser 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, 25 Feb 2023 16:48:20 +0200
Source: pacparser
Architecture: source
Version: 1.3.6-1.4
Distribution: unstable
Urgency: medium
Maintainer: Manu Garg 
Changed-By: Adrian Bunk 
Closes: 1026106
Changes:
 pacparser (1.3.6-1.4) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * CVE-2019-25078: Possible memory overwrite in pacparser_find_proxy()
 (Closes: #1026106)
Checksums-Sha1:
 45a9260ffea5b020f0975684306d7eede88c7f36 1884 pacparser_1.3.6-1.4.dsc
 bad028a28cbbc21d4ff100cda4c2c34a5880d8a6 4972 pacparser_1.3.6-1.4.debian.tar.xz
Checksums-Sha256:
 d475ed3159fcd01f9c6e8328db885a8f8d5619df03625310f33f7744e9aca8cf 1884 
pacparser_1.3.6-1.4.dsc
 2840cc627eaf0518fd8a897188c71e83257789fef4f5e3078be2c03496329543 4972 
pacparser_1.3.6-1.4.debian.tar.xz
Files:
 d1aada5cb8c8f9ff25f588eb185a8833 1884 libs extra pacparser_1.3.6-1.4.dsc
 94aeedf00fe5382d04410a7f2206e518 4972 libs extra 
pacparser_1.3.6-1.4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmP6JUoACgkQiNJCh6LY
mLE/mhAAqTh7t9zIXAF7gBQKSbjt7wdTO/fmHJz3gMxuI+3E5gheFPMXl3KDYgKN
NN5wYJLeUan/de64yMEx3vSi1g6eZOZjja0CDouzewg14jTUnsiBRjkf66kRiytr
W8JlFUQLhT6KLev3HJJ6e5uzu6fOpWe1troVxC9ihmWn1j5v+Yb4XHKdIRq3MP4Z
iwERDrBsd3b481ES3j4LhyFwPBFTWLjHnvpLzA4f7ed4FY+ot1ljMiRQHN2O394b
yYQSaVSf7IjU1sYnttBoAJwASpgddJYa5NCXa53Y8rnfPgp5QDDm0dVXtAjLPadv
i9aMZYGBTuR6BigqHn6canpbiFDxzQ2DAYgxdz+2NK54BdheRMTL8wgTtEvMVtO/
mRKsTYu0tL3Ihl1C5kB/E9sY3KG0OgJWwitZ9kr02CUDadu0qT4v+9cCBY0LCo6h
OCjzodJY0gejW2FSDEqBGmOM39S/el3N8EJ4cHKDC1F5rhgsTBl/+QJRIUgcc8iC
TaAT+skp4TIVFauh2gEm1n96pYOxdC7JLlIh4bSS4t/oOvgOvtycbwZ+KfQ5UdOR
HidbSyEipHS63TOY1v1w/FAWKON7KnH6ZONuBQ3aV3HzZWnmH+8vV+3i67Si+5iw
zt41Xcsg67FOEDkozyEA/qDNoqSCttCJxwtw4jPkD1xxa2HTDb8=
=pPS3
-END PGP SIGNATURE End Message ---

Bug#1031448: marked as done (libfrashrom-dev missing dependency on pkg-config required libraries)

[Debian Bug Tracking System]

Your message dated Thu, 02 Mar 2023 10:19:52 +
with message-id 
and subject line Bug#1031448: fixed in flashrom 1.3.0-2.1
has caused the Debian Bug report #1031448,
regarding libfrashrom-dev missing dependency on pkg-config required libraries
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.)


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

Hi,

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


Relevant part (hopefully):
>  /usr/bin/ld: /tmp/ccLdacAo.o: in function `main':
> ./obj-x86_64-linux-gnu/meson-private/tmp7p7957mh/./obj-x86_64-linux-gnu/meson-private/tmp7p7957mh/testfile.c:17:
>  undefined reference to `gcab_cabinet_add_allowed_compression'
> collect2: error: ld returned 1 exit status


The full build log is available from:
http://qa-logs.debian.net/2023/02/16/fwupd_1.8.10-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230216;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230216&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=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 mark 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: flashrom
Source-Version: 1.3.0-2.1
Done: Adrian Bunk 

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated flashrom 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, 25 Feb 2023 17:13:29 +0200
Source: flashrom
Architecture: source
Version: 1.3.0-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian EFI 
Changed-By: Adrian Bunk 
Closes: 1031448
Changes:
 flashrom (1.3.0-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Remove no longer used debian/flashrom.pc
 (pkg-config file is now generated during the build).
   * libflashrom-dev: Remove the unnecessary Requires.private
 from flashrom.pc. (Closes: #1031448)
Checksums-Sha1:
 6b440ecfa231fe90db1c393f45502746d0c9ee00 2209 flashrom_1.3.0-2.1.dsc
 56184c72a696438b69d129876f7047c8e08d7eba 11124 flashrom_1.3.0-2.1.debian.tar.xz
Checksums-Sha256:
 e12b905ef7ea551e2c5d743aedd3435752d14dccd045f7474a60147682ba745b 2209 
flashrom_1.3.0-2.1.dsc
 7d1a10fe9b1f5e08a92b7de8a422f002bfb4681f3e7ec562f1a7f4a9c7c85adb 11124 
flashrom_1.3.0-2.1.debian.tar.xz
Files:
 5696ae0b67177ff39f79fa875c4022aa 2209 electronics optional 
flashrom_1.3.0-2.1.dsc
 ce9a93abed24ac84f4dcd5505565296d 11124 electronics optional 
flashrom_1.3.0-2.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmP6LnkACgkQiNJCh6LY
mLEkARAAwIwHkTuyJw4T3AJ+d3Cizla1hzmWf2b2rhS6g5dQXsD9a4lj6Z804PLw
nRbUxAzR5k8vzTmn4mRBHkU5Algv0yamzHhxsDYwMQReKN11QvAFgM+nUDXMK0lb
1gzkdTxYZWMKFoEGLx60TdHEinSCjYLylQGmJWmNgiRHF3wCrQ1pl9wg0NPIirRz
mbEJ7vm4mcQTo1pCDBHQAhAneIXqlFF88Yg2u4JSI/AqXADJcwNJwwCw/WkbDw3d
NoGIT+p1OnfhibJmKhlzs7Fi+hziVyxBq4xPtIhhCicMXv7xIkYHrtc7SJTyx24A
fwR1wgrcnIuyGuOLNiER7+BHpUqumMehHigPEGJhzGHPce3v5Geqdsz2e1TBZo6+
6xw4KCpAY1G9soujflqd+zyEL4vZzUj2NhgMQURPq6sy28lyTaR5dnZ8EvzOc6MR
+34eLKQnb81lcOhUID5ic9GsZEI1OJ10VLfjwcKew3yhiDTFMJdIb9uh1L+fijOl
p6ttx3X+NlbFR+osdiwr80+iPToMplFrkAig7D2MGouJL5D+rRf9UC4Sik5Cni++
XFaUgB9u0jRxm21aEUPERNc2XOd+Le2qZltK7mQO2enrGfWTmQQVBnv3Of13cYpH
t25b0fq7yhviDgx

Bug#1030456: marked as done (drslib: FTBFS: pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: '0.3.1p3')

[Debian Bug Tracking System]

Your message dated Thu, 02 Mar 2023 10:19:42 +
with message-id 
and subject line Bug#1030456: fixed in drslib 0.3.1.p3-2.1
has caused the Debian Bug report #1030456,
regarding drslib: FTBFS: pkg_resources.extern.packaging.version.InvalidVersion: 
Invalid version: '0.3.1p3'
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.)


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> py3versions: no X-Python3-Version in control file, using supported versions
> py3versions: no X-Python3-Version in control file, using supported versions
> python3.11 setup.py build
> /usr/lib/python3/dist-packages/setuptools/dist.py:548: UserWarning: The 
> version specified ('0.3.1p3') is an invalid version, this may not work as 
> expected with newer versions of setuptools, pip, and PyPI. Please see PEP 440 
> for more details.
>   warnings.warn(
> running build
> running build_py
> creating build
> creating build/lib
> creating build/lib/drslib
> copying drslib/__init__.py -> build/lib/drslib
> copying drslib/drs_tree_check.py -> build/lib/drslib
> copying drslib/cmip3.py -> build/lib/drslib
> copying drslib/cordex.py -> build/lib/drslib
> copying drslib/specs.py -> build/lib/drslib
> copying drslib/publisher_tree.py -> build/lib/drslib
> copying drslib/exceptions.py -> build/lib/drslib
> copying drslib/drs_command.py -> build/lib/drslib
> copying drslib/cmip5.py -> build/lib/drslib
> copying drslib/translate_iface.py -> build/lib/drslib
> copying drslib/thredds.py -> build/lib/drslib
> copying drslib/translate_cmip3.py -> build/lib/drslib
> copying drslib/drs_tree.py -> build/lib/drslib
> copying drslib/mapfile.py -> build/lib/drslib
> copying drslib/mip_table.py -> build/lib/drslib
> copying drslib/config.py -> build/lib/drslib
> copying drslib/translate.py -> build/lib/drslib
> copying drslib/drs.py -> build/lib/drslib
> creating build/lib/drslib/p_cmip5
> copying drslib/p_cmip5/__init__.py -> build/lib/drslib/p_cmip5
> copying drslib/p_cmip5/product.py -> build/lib/drslib/p_cmip5
> copying drslib/p_cmip5/init.py -> build/lib/drslib/p_cmip5
> copying drslib/p_cmip5/time_slices.py -> build/lib/drslib/p_cmip5
> running egg_info
> Traceback (most recent call last):
>   File "/<>/setup.py", line 14, in 
> setup(name='drslib',
>   File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 108, in 
> setup
> return distutils.core.setup(**attrs)
>^
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 
> 185, in setup
> return run_commands(dist)
>^^
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 
> 201, in run_commands
> dist.run_commands()
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
> 969, in run_commands
> self.run_command(cmd)
>   File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1213, in 
> run_command
> super().run_command(command)
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
> 988, in run_command
> cmd_obj.run()
>   File 
> "/usr/lib/python3/dist-packages/setuptools/_distutils/command/build.py", line 
> 132, in run
> self.run_command(cmd_name)
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line 
> 318, in run_command
> self.distribution.run_command(command)
>   File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1213, in 
> run_command
> super().run_command(command)
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
> 988, in run_command
> cmd_obj.run()
>   File "/usr/lib/python3/dist-packages/setuptools/command/build_py.py", line 
> 63, in run
> self.build_package_data()
>   File "/usr/lib/python3/dist-packages/setuptools/command/build_py.py", line 
> 159, in build_package_data
> for target, srcfile in self._get_package_data_output_mapping():
>   File "/usr/lib/python3/dist-packages/setuptools/command/build_py.py", line 
> 151, in _get_package_data_output_mapping
> for package, src_dir, build_dir, filenames in self.data_files:
>   ^^^
>   File "/usr/li

Bug#1023436: marked as done (unusable on mipsel: unexpected breakpoint at 0x...)

[Debian Bug Tracking System]

Your message dated Thu, 02 Mar 2023 10:20:12 +
with message-id 
and subject line Bug#1023436: fixed in ltrace 0.7.3-6.4
has caused the Debian Bug report #1023436,
regarding unusable on mipsel: unexpected breakpoint at 0x...
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.)


-- 
1023436: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023436
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ltrace
Version: 0.7.3-6.3
Severity: grave

Hi,

running ltrace on mipsel, I get:

$ ltrace echo
unexpected breakpoint at 0x77e74ef8
unexpected breakpoint at 0x77e74ef8
unexpected breakpoint at 0x77e74ee8
unexpected breakpoint at 0x77e74ee8
unexpected breakpoint at 0x77e74ef8
unexpected breakpoint at 0x77e74ef8
unexpected breakpoint at 0x77e74ee8
unexpected breakpoint at 0x77e74ee8
unexpected breakpoint at 0x77e74ee8
unexpected breakpoint at 0x77e74ee8
unexpected breakpoint at 0x77e74ef8
unexpected breakpoint at 0x77e74ef8
unexpected breakpoint at 0x77e74ef8
unexpected breakpoint at 0x77e74ef8
unexpected breakpoint at 0x77e74ef8
unexpected breakpoint at 0x77e74ef8
unexpected breakpoint at 0x77e74ef8
unexpected breakpoint at 0x77e74ef8
unexpected breakpoint at 0x77e74ef8
unexpected breakpoint at 0x77e74ef8
unexpected breakpoint at 0x77d926c8
unexpected breakpoint at 0x77d926c8
unexpected breakpoint at 0x77d926d8
unexpected breakpoint at 0x77d926d8
unexpected breakpoint at 0x77d926c8
unexpected breakpoint at 0x77d926c8
unexpected breakpoint at 0x77d926d8
unexpected breakpoint at 0x77d926d8
unexpected breakpoint at 0x77d926c8
unexpected breakpoint at 0x77d926c8
unexpected breakpoint at 0x77d926d8
unexpected breakpoint at 0x77d926d8
unexpected breakpoint at 0x77d926c8
unexpected breakpoint at 0x77d926c8
unexpected breakpoint at 0x77d926d8
unexpected breakpoint at 0x77d926d8
unexpected breakpoint at 0x77d926c8
unexpected breakpoint at 0x77d926c8
unexpected breakpoint at 0x77d926d8
unexpected breakpoint at 0x77d926d8
unexpected breakpoint at 0x77d926c8
unexpected breakpoint at 0x77d926c8
unexpected breakpoint at 0x77d926d8
unexpected breakpoint at 0x77d926d8
unexpected breakpoint at 0x77d926c8
unexpected breakpoint at 0x77d926c8
unexpected breakpoint at 0x77d926d8
unexpected breakpoint at 0x77d926d8
unexpected breakpoint at 0x77d926c8
unexpected breakpoint at 0x77d926c8
unexpected breakpoint at 0x77d926c8
unexpected breakpoint at 0x77d926c8
unexpected breakpoint at 0x77d926d8
unexpected breakpoint at 0x77d926d8
unexpected breakpoint at 0x77d926c8
unexpected breakpoint at 0x77d926c8
unexpected breakpoint at 0x77d926d8
unexpected breakpoint at 0x77d926d8
unexpected breakpoint at 0x77d926c8
unexpected breakpoint at 0x77d926c8
unexpected breakpoint at 0x77d926d8
unexpected breakpoint at 0x77d926d8
unexpected breakpoint at 0x77d926c8
unexpected breakpoint at 0x77d926c8
unexpected breakpoint at 0x77d926d8
unexpected breakpoint at 0x77d926d8
unexpected breakpoint at 0x77d926c8
unexpected breakpoint at 0x77d926c8
unexpected breakpoint at 0x77d926d8
unexpected breakpoint at 0x77d926d8
unexpected breakpoint at 0x77d926c8
unexpected breakpoint at 0x77d926c8
unexpected breakpoint at 0x77d926d8
unexpected breakpoint at 0x77d926d8
unexpected breakpoint at 0x77d926c8
unexpected breakpoint at 0x77d926c8

+++ exited (status 0) +++

This makes the package unusable.

Thanks!

cheers, josch
--- End Message ---
--- Begin Message ---
Source: ltrace
Source-Version: 0.7.3-6.4
Done: Adrian Bunk 

We believe that the bug you reported is fixed in the latest version of
ltrace, 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.
Adrian Bunk  (supplier of updated ltrace 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, 25 Feb 2023 20:40:34 +0200
Source: ltrace
Architecture: source
Version: 0.7.3-6.4
Distribution: unstable
Urgency: medium
Maintainer: Juan Cespedes 
Changed-By: Adrian Bunk 
Closes: 1023436
Changes:
 ltrace (0.7.3-6.4) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Stop building for MIPS, ltrace no longer works there.
 (Closes: #1023436)
Checksums-Sha

Bug#1032247: breezy-debian FTBFS: ERROR: breezy.plugins.debian.tests.test_upstream.LazyUpstreamBranchSourceTests.test_get_latest_version

[Adrian Bunk]

Source: breezy-debian
Version: 2.8.77
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=breezy-debian&arch=all&ver=2.8.77&stamp=1677498906&raw=0

...
==
ERROR: 
breezy.plugins.debian.tests.test_upstream.LazyUpstreamBranchSourceTests.test_get_latest_version
--
testtools.testresult.real._StringException: log: {{{
19.771  creating repository in 
file:///tmp/testbzr-7xxlu7i0.tmp/breezy.plugins.debian.tests.test_upstream.LazyUpstreamBranchSourceTests.test_get_latest_version/work/.bzr/.
19.773  creating branch  in 
file:///tmp/testbzr-7xxlu7i0.tmp/breezy.plugins.debian.tests.test_upstream.LazyUpstreamBranchSourceTests.test_get_latest_version/work/
19.778  trying to create missing lock 
'/tmp/testbzr-7xxlu7i0.tmp/breezy.plugins.debian.tests.test_upstream.LazyUpstreamBranchSourceTests.test_get_latest_version/work/.bzr/checkout/dirstate'
19.778  opening working tree 
'/tmp/testbzr-7xxlu7i0.tmp/breezy.plugins.debian.tests.test_upstream.LazyUpstreamBranchSourceTests.test_get_latest_version/work'
19.784  preparing to commit
INFO  Committing to: 
/tmp/testbzr-7xxlu7i0.tmp/breezy.plugins.debian.tests.test_upstream.LazyUpstreamBranchSourceTests.test_get_latest_version/work/
19.785  Selecting files for commit with filter None
INFO  Committed revision 1.
19.792  Committed revid b'jran...@example.com-20230227115456-yxlugfpwfxn7x7m6' 
as revno 1.
INFO  Current version is release, merging new release.
INFO  No upstream upstream-revision format specified, trying tag:1.0
19.797  Returning RevisionSpec RevisionSpec_tag for tag:1.0
INFO  No upstream upstream-revision format specified, trying tag:foo-1.0
19.797  Returning RevisionSpec RevisionSpec_tag for tag:foo-1.0
INFO  No upstream upstream-revision format specified, trying tag:v1.0
19.797  Returning RevisionSpec RevisionSpec_tag for tag:v1.0
INFO  No upstream upstream-revision format specified, trying tag:v.1.0
19.797  Returning RevisionSpec RevisionSpec_tag for tag:v.1.0
INFO  No upstream upstream-revision format specified, trying tag:release-1.0
19.798  Returning RevisionSpec RevisionSpec_tag for tag:release-1.0
INFO  No upstream upstream-revision format specified, trying tag:1_0_release
19.798  Returning RevisionSpec RevisionSpec_tag for tag:1_0_release
INFO  No upstream upstream-revision format specified, trying tag:1_0
19.798  Returning RevisionSpec RevisionSpec_tag for tag:1_0
INFO  No upstream upstream-revision format specified, trying tag:version-1.0
19.798  Returning RevisionSpec RevisionSpec_tag for tag:version-1.0
INFO  No upstream upstream-revision format specified, trying 
tag:foo-1_0-release
19.798  Returning RevisionSpec RevisionSpec_tag for tag:foo-1_0-release
INFO  No upstream upstream-revision format specified, trying tag:foo-v1.0
19.798  Returning RevisionSpec RevisionSpec_tag for tag:foo-v1.0
}}}

Traceback (most recent call last):
  File "/<>/upstream/branch.py", line 560, in get_recent_versions
since_revision, _subpath = self.version_as_revision(
   ^
  File "/<>/upstream/branch.py", line 477, in version_as_revision
raise PackageVersionNotPresent(package, version, self)
breezy.plugins.debian.upstream.PackageVersionNotPresent: foo 1.0 was not found 
in .

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/<>/tests/test_upstream.py", line 602, in 
test_get_latest_version
("2.1", "2.1"), source.get_latest_version("foo", "1.0"))
^^^
  File "/<>/upstream/branch.py", line 537, in get_latest_version
version = self.get_latest_release_version(
  
  File "/<>/upstream/branch.py", line 509, in 
get_latest_release_version
versions = list(self.get_recent_versions(package, current_version))
^^
  File "/<>/upstream/branch.py", line 563, in get_recent_versions
raise PreviousVersionTagMissing(
breezy.plugins.debian.upstream.branch.PreviousVersionTagMissing: Unable to find 
the tag for the previous upstream version (foo) in the upstream branch: 1.0

--
Ran 559 tests in 21.453s

FAILED (errors=1, known_failure_count=3)
4 tests skipped
make[1]: *** [debian/rules:24: override_dh_auto_test] Error 1

Bug#1029821: change gnome-desktop's default choice of Japanese input methods for Debian

[Simon McVittie]

Control: tags -1 + moreinfo

On Sat, 28 Jan 2023 at 16:46:35 +0900, YOSHINO Yoshihito wrote:
> As mentioned in Bug #984875, gnome-initial-setup's default choice of
> input method is hardcoded in the dependent libgnome-desktop-4-2 package.
> The Japanese one is anthy
> https://sources.debian.org/src/gnome-desktop/43.1-1/libgnome-desktop/default-input-sources.h/#L39
> preferred by upstream (Fedora/Red Hat) perhaps because its code base is
> simple and easy to maintain, while this is not suitable for most Debian
> Japanese users, who use mozc because of its better conversion quality,
> thus task-japanese-gnome-desktop and task-japanese-desktop has preferred
> mozc over anthy. So the hardcoded value should be adjusted for our
> users.

Is there consensus among Japanese-speaking users of Debian that mozc is
a better default for all Japanese speakers, including new users who are
not familiar with GNOME or Debian?

I want to avoid changing this from anthy to mozc-jp, and then getting a
second bug report from a different Japanese user saying that we need to
change it back!

Looking at #984875 and #983653, I also see a mention of mozc only being
available on certain architectures: it's available on x86, ARM and riscv64,
but not on mips*el, ppc64el or s390x.

How does this interact with the default being mozc-jp? Do we need to use
a #ifdef to make the default be mozc on architectures that have it, and
anthy on architectures that don't?

I'm also concerned that mozc still depends on GTK 2 (a switch to GTK
3 was tried and then reverted, see #967641). This is OK for bookworm,
but will probably not be supportable in Debian 13.

> Upstream prefers ibus-anthy for Japanese input

Please talk to upstream about this: if mozc is a better default for Debian,
then it's probably also a better default for upstream.

The only issue reports I could find upstream are
https://gitlab.gnome.org/GNOME/gnome-desktop/-/issues/181 which is about
switching the default from kkc to anthy, and
https://gitlab.gnome.org/GNOME/gnome-initial-setup/-/issues/104 which is
older and refers to kkc as being the default.

On Wed, 22 Feb 2023 at 15:09:15 +0900, ken...@xdump.org wrote:
>   Thus with attached patch, gnome-initial-setup will not
>   show label for mozc-jp as "日本語 (Mozc)" by default.

What would be the best label to be displayed there?

What is actually displayed instead?

>   To display label correctly, fetch_ibus_engines_result must be called 
>   in advance.

That's probably not possible: fetch_ibus_engines_result is called
asynchronously with the result of a D-Bus method call, so it's already
called as early as possible, and before that point we don't have the
necessary information.

Probably the best we can do there is to hard-code a special case for
mozc-jp.

smcv

Processed: Re: Bug#1029821: change gnome-desktop's default choice of Japanese input methods for Debian

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #1029821 [libgnome-desktop-4-2] change gnome-desktop's default choice of 
Japanese input methods for Debian
Added tag(s) moreinfo.

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

Processed: found 1031977 in 4

[Debian Bug Tracking System]

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

> found 1031977 4
Bug #1031977 [src:gdb-bpf] gdb-bpf: not binNMU safe
Marked as found in versions gdb-bpf/4.
> thanks
Stopping processing here.

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

Bug#1032244: tryton-server 6.0.28-1 causes autopkgtest regression in tryton-modules-stock-location-move

[Adrian Bunk]

Source: tryton-server
Version: 6.0.28-1
Severity: serious

https://tracker.debian.org/pkg/tryton-server

ssues preventing migration:
∙ ∙ autopkgtest for tryton-modules-stock-location-move/6.0.0-3: amd64: 
Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armel: 
Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression 
♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ 
(reference ♻)


https://ci.debian.net/data/autopkgtest/testing/amd64/t/tryton-modules-stock-location-move/31808215/log.gz

...
==
FAIL: 
/usr/lib/python3/dist-packages/trytond/modules/stock_location_move/tests/scenario_stock_location_move.rst
Doctest: scenario_stock_location_move.rst
--
Traceback (most recent call last):
  File "/usr/lib/python3.11/doctest.py", line , in runTest
raise self.failureException(self.format_failure(new.getvalue()))
AssertionError: Failed doctest test for scenario_stock_location_move.rst
  File 
"/usr/lib/python3/dist-packages/trytond/modules/stock_location_move/tests/scenario_stock_location_move.rst",
 line 0

--
File 
"/usr/lib/python3/dist-packages/trytond/modules/stock_location_move/tests/scenario_stock_location_move.rst",
 line 70, in scenario_stock_location_move.rst
Failed example:
shipment.click('assign_try')  # doctest: +IGNORE_EXCEPTION_DETAIL
Expected:
Traceback (most recent call last):
...
DomainValidationError: ...
Got:
True


--
Ran 23 tests in 60.652s

FAILED (failures=1)
autopkgtest [01:13:45]: test run-testsuite: ---]
autopkgtest [01:13:45]: test run-testsuite:  - - - - - - - - - - results - - - 
- - - - - - -
run-testsuiteFAIL non-zero exit status 1

Bug#1032242: yadifa FTBFS on 32bit

[Adrian Bunk]

Source: yadifa
Version: 2.6.3-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=yadifa&ver=2.6.3-1

...
src/fdtools.c: In function ‘file_mtime_set_add_file’:
src/fdtools.c:1754:15: error: ‘ptr_node’ has no member named ‘value_s64’; did 
you mean ‘value_s32’?
 1754 | node->value_s64 = mtime;
  |   ^
  |   value_s32
src/fdtools.c: In function ‘file_mtime_set_modified’:
src/fdtools.c:1776:22: error: ‘ptr_node’ has no member named ‘value_s64’; did 
you mean ‘value_s32’?
 1776 | if(node->value_s64 < mtime)
  |  ^
  |  value_s32
make[4]: *** [Makefile:1544: src/fdtools.lo] Error 1

Bug#1032240: akonadi server fails to start since it cannot connect to mysql database

[Enrique]

Package: akonadi-backend-mysql
Version: 4:22.12.2-1
Severity: grave
X-Debbugs-Cc: cqu...@arcor.de

I cannot use my kmail email client due to akonadi server not being started. To
debug it I have tried the following:
# akonadictl start
org.kde.pim.akonadictl: Starting Akonadi Server...
org.kde.pim.akonadictl:done.
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
org.kde.pim.akonadiserver: Starting up the Akonadi Server...
org.kde.pim.akonadiserver: database server stopped unexpectedly
org.kde.pim.akonadiserver: Database process exited unexpectedly during initial
connection!
org.kde.pim.akonadiserver: executable: "/usr/sbin/mysqld"
org.kde.pim.akonadiserver: arguments: ("--defaults-
file=/home/cgarcia/.local/share/akonadi/mysql.conf", "--
datadir=/home/cgarcia/.local/share/akonadi/db_data/", "--
socket=/run/user/4876/akonadi/mysql.socket", "--pid-
file=/run/user/4876/akonadi/mysql.pid")
org.kde.pim.akonadiserver: stdout: ""
org.kde.pim.akonadiserver: stderr: ""
org.kde.pim.akonadiserver: exit code: 1
org.kde.pim.akonadiserver: process error: "Unknown error"
org.kde.pim.akonadiserver: Shutting down AkonadiServer...
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadiserver' exited
normally...

So apparently mysql cannot be started. I have tried to manually start mysql but
I get the following message:
# /usr/sbin/mysqld --verbose --defaults-
file=/home/cgarcia/.local/share/akonadi/mysql.conf
--datadir=/home/cgarcia/.local/share/akonadi/db_data/
--socket=/run/user/4876/akonadi/mysql.socket --pid-
file=/run/user/4876/akonadi/mysql.pid
2023-03-02  9:21:47 0 [Note] Starting MariaDB 10.11.2-MariaDB-1 source revision
as process 13921
2023-03-02  9:21:48 0 [Note] InnoDB: Compressed tables use zlib 1.2.13
2023-03-02  9:21:48 0 [Note] InnoDB: Number of transaction pools: 1
2023-03-02  9:21:48 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2023-03-02  9:21:48 0 [Note] InnoDB: Using liburing
2023-03-02  9:21:48 0 [Note] InnoDB: Initializing buffer pool, total size =
128.000MiB, chunk size = 2.000MiB
2023-03-02  9:21:48 0 [Note] InnoDB: Completed initialization of buffer pool
2023-03-02  9:21:48 0 [Note] InnoDB: File system buffers for log disabled
(block size=512 bytes)
2023-03-02  9:21:48 0 [ERROR] InnoDB: Upgrade after a crash is not supported.
The redo log was created with MariaDB 10.6.11. You must start up and shut down
MariaDB 10.7 or earlier.
2023-03-02  9:21:48 0 [ERROR] InnoDB: Plugin initialization aborted with error
Generic error
2023-03-02  9:21:48 0 [Note] InnoDB: Starting shutdown...
2023-03-02  9:21:48 0 [ERROR] Plugin 'InnoDB' init function returned error.
2023-03-02  9:21:48 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE
failed.
2023-03-02  9:21:48 0 [Note] Plugin 'FEEDBACK' is disabled.
2023-03-02  9:21:48 0 [ERROR] Could not open mysql.plugin table: "Table
'mysql.plugin' doesn't exist". Some plugins may be not loaded
2023-03-02  9:21:48 0 [ERROR] /usr/sbin/mysqld: unknown variable 'defaults-
file=/home/cgarcia/.local/share/akonadi/mysql.conf'
2023-03-02  9:21:48 0 [ERROR] Aborting

That renders all KDE PIM applications unusable in Debian Bookworm.


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

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

Versions of packages akonadi-backend-mysql depends on:
ii  default-mysql-client-core1.1.0
ii  default-mysql-server-core1.1.0
ii  libqt5sql5-mysql 5.15.8+dfsg-2
ii  mariadb-client-core [virtual-mysql-client-core]  1:10.11.2-1
ii  mariadb-server-core [virtual-mysql-server-core]  1:10.11.2-1

Versions of packages akonadi-backend-mysql recommends:
ii  akonadi-server  4:22.12.2-1

akonadi-backend-mysql suggests no packages.

-- no debconf information