Bug#1010636: [Pkg-freeipa-devel] Bug#1010636: dogtag-pki: please reduce unused Build-Depends

2023-01-14 Thread Helmut Grohne
Hi Timo,

On Fri, Jan 13, 2023 at 09:39:32AM +0200, Timo Aaltonen wrote:
> Hi, the others have been dropped from the version being prepared, but
> python3-dev is needed for dh_auto_test:
> 
> dh_auto_test: warning: warning: pybuild does not support building out of
> source tree. In source building enforced.
> E: Please add appropriate interpreter package to Build-Depends, see
> pybuild(1) for details.this: $VAR1 = bless( {
>  'py3def' => '3.11',
>  'pyvers' => '',
>  'pydef' => '',
>  'builddir' => undef,
>  'py3vers' => '3.10 3.11',
>  'sourcedir' => '.',
>  'cwd' => '/<>',
>  'parallel' => '32'
>}, 'Debian::Debhelper::Buildsystem::pybuild' );
> deps: $VAR1 = [
>   'python3-cryptography',
>   'python3-distutils',
>   'python3-ldap',
>   'python3-requests',
>   'python3-setuptools',
>   'python3-sphinx',
>   'python3-urllib3'
> ];
> make: *** [debian/rules:47: build] Error 25

Thank you for reviewing my list of suggested dependencies. Would you
mind using Build-Depends: python3-dev ? Thus the dependency
would be available for tests while not encumbering cross builds.

If that still fails, consider replacing python3-dev with
"libpython3-dev, python3-dev:native" to improve cross build support.

Helmut



Bug#1028523: dpkg-dev: No obvious way to include upstream signature in dpkg-genchanges

2023-01-14 Thread Helge Kreutzmann
Hello Sven,
sorry for my slow answer.

On Fri, Jan 13, 2023 at 10:14:24PM +0100, Sven Joachim wrote:
> Am 13.01.2023 um 21:50 schrieb Helge Kreutzmann:
> > As you can see, "linuxinfo_4.1.2.orig.tar.xz.asc" is contained in the
> > .dsc file, but not in the .changes file.
> 
> This is the opposite of what you wrote in the original report (where the
> .asc file was in the changes file and not in the .dsc), and is in fact
> normal as you did not include the upstream sources (the default if
> debian/changelog indicates that this is not the first debian revision).

This was a mistake of mine, I probably failed to write it correctly. I
apologize.

> > When I uploaded this (with -2) the archive rejected this.
> 
> Yes, because your .dsc file referenced the .asc file, but the changes
> file did not include it, nor was the file already in the archive.
> 
> > I manually edited the .changes to add
> > "linuxinfo_4.1.2.orig.tar.xz.asc", and this worked.
> 
> I guess could also have passed "-sa" to dpkg-buildpackage to include the
> full sources again, but whatever worked for you.

So I understand, if I had included the full sources, then the .asc file
would have been included as well? And does this work? - I remember that
in the past I was told that the sources are already in the archive,
and hence cannot be uploaded again (but I might be wrong on this).

Then this two things should be documented:

1. .asc files are always (automatically) included if the upstream
   sources are included (either by default or by -sa)

2. .asc files cannot be included on their own, but rather require the
   corresponding upstream sources (which would make sense, indeed).
   [1]

Greetings

 Helge

  [1] If I'm right that the upstream source can only be uploaded once,
  then possibly a sentence that .asc files should only be included at
  Debian revision 1.
-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/


signature.asc
Description: PGP signature


Bug#1028027: vice: contains non-free font file

2023-01-14 Thread GCS
Hi Bastian,

On Fri, Jan 6, 2023 at 3:00 AM Bastian Germann  wrote:
> The package includes C64_Pro_Mono-STYLE.ttf which has a non-free license.
> So please repack to get rid of it. As your package is in contrib, you can
> easily extract it to a new non-free package and depend on it.
 I have to check if a contrib package can or should depend on a
non-free one. At the moment I don't like the idea and switch back to
the previous free one instead.

Thanks for the note anyway,
Laszlo/GCS



Bug#1028955: Our Drawing version is severely outdated

2023-01-14 Thread Frank Mascal
Package: drawing
Version: 0.8.5-2

Hi,

The version of Drawing Debian ships is severely outdated, it is version 1.0.1 
nowadays.

It looks like upstream made a decent job already in their debian/ directory so 
it may be quite easy.

Can you please update the version provided in Debian?

Thanks in advance.
 
 
 



Bug#1028954: php-horde-rdo: (autopkgtest) needs update for php8.2: deprecation warnings on stderr

2023-01-14 Thread Paul Gevers

Source: php-horde-rdo
Version: 2.1.0-9
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults

Dear maintainer(s),

We are in the transition of replacing php8.1 with php8.2 [0]. With a 
recent upload of php-defaults the autopkgtest of php-horde-rdo fails in 
testing when that autopkgtest is run with the binary packages of 
php-defaults from unstable. It passes when run with only packages from 
testing. In tabular form:


   passfail
php-defaults   from testing93
php-horde-rdo  from testing2.1.0-9
all others from testingfrom testing

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

Currently this regression is blocking the migration of php-defaults to 
testing [1]. https://www.php.net/ChangeLog-8.php lists the changes since 
7.4 and may help to identify what needs to be updated.


The test itself passes, but the autopkgtest fails because of deprecation 
warnings on stderr. Output on stderr makes autopkgtest fail by default, 
unless `allow-stderr` is added to the set of restrictions. As a flood of 
deprecation warnings in server logs may be very unwanted, I'm not saying 
that adding the restriction to autopkgtest is the right answer to this 
issue, but because of the php transition, it needs to be resolved one 
way or the other.


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

Paul

[0] https://bugs.debian.org/1014460
[1] https://qa.debian.org/excuses.php?package=php-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-horde-rdo/30340553/log.gz

PHP Deprecated:  Creation of dynamic property 
Horde_Rdo_Test_Objects_SomeLazyBaseObjectMapper::$tableDefinition is 
deprecated in 
/tmp/autopkgtest-lxc.fj53cage/downtmp/build.udq/src/Horde_Rdo-2.1.0/lib/Horde/Rdo/Mapper.php 
on line 160
PHP Deprecated:  Creation of dynamic property 
Horde_Rdo_Test_Objects_SomeLazyBaseObjectMapper::$primaryKey is 
deprecated in 
/tmp/autopkgtest-lxc.fj53cage/downtmp/build.udq/src/Horde_Rdo-2.1.0/lib/Horde/Rdo/Mapper.php 
on line 152
PHP Deprecated:  Creation of dynamic property 
Horde_Rdo_Test_Objects_SomeLazyBaseObjectMapper::$fields is deprecated 
in 
/tmp/autopkgtest-lxc.fj53cage/downtmp/build.udq/src/Horde_Rdo-2.1.0/lib/Horde/Rdo/Mapper.php 
on line 164
PHP Deprecated:  Callables of the form ["Horde_Db_Adapter_Pdo_Sqlite", 
"parent::execute"] are deprecated in 
/usr/share/php/Horde/Db/Adapter/Pdo/Sqlite.php on line 187
PHP Deprecated:  Creation of dynamic property 
Horde_Rdo_Test_Objects_RelatedThingMapper::$adapter is deprecated in 
/tmp/autopkgtest-lxc.fj53cage/downtmp/build.udq/src/Horde_Rdo-2.1.0/lib/Horde/Rdo/Mapper.php 
on line 93
PHP Deprecated:  Creation of dynamic property 
Horde_Rdo_Test_Objects_RelatedThingMapper::$table is deprecated in 
/tmp/autopkgtest-lxc.fj53cage/downtmp/build.udq/src/Horde_Rdo-2.1.0/lib/Horde/Rdo/Mapper.php 
on line 156
PHP Deprecated:  Callables of the form ["Horde_Db_Adapter_Pdo_Sqlite", 
"parent::execute"] are deprecated in 
/usr/share/php/Horde/Db/Adapter/Pdo/Sqlite.php on line 187
PHP Deprecated:  Callables of the form ["Horde_Db_Adapter_Pdo_Sqlite", 
"parent::execute"] are deprecated in 
/usr/share/php/Horde/Db/Adapter/Pdo/Sqlite.php on line 187
PHP Deprecated:  Callables of the form ["Horde_Db_Adapter_Pdo_Sqlite", 
"parent::execute"] are deprecated in 
/usr/share/php/Horde/Db/Adapter/Pdo/Sqlite.php on line 187
PHP Deprecated:  Creation of dynamic property 
Horde_Rdo_Test_Objects_RelatedThingMapper::$tableDefinition is 
deprecated in 
/tmp/autopkgtest-lxc.fj53cage/downtmp/build.udq/src/Horde_Rdo-2.1.0/lib/Horde/Rdo/Mapper.php 
on line 160
PHP Deprecated:  Creation of dynamic property 
Horde_Rdo_Test_Objects_RelatedThingMapper::$primaryKey is deprecated in 
/tmp/autopkgtest-lxc.fj53cage/downtmp/build.udq/src/Horde_Rdo-2.1.0/lib/Horde/Rdo/Mapper.php 
on line 152
PHP Deprecated:  Creation of dynamic property 
Horde_Rdo_Test_Objects_RelatedThingMapper::$fields is deprecated in 
/tmp/autopkgtest-lxc.fj53cage/downtmp/build.udq/src/Horde_Rdo-2.1.0/lib/Horde/Rdo/Mapper.php 
on line 164
PHP Deprecated:  Callables of the form ["Horde_Db_Adapter_Pdo_Sqlite", 
"parent::execute"] are deprecated in 
/usr/share/php/Horde/Db/Adapter/Pdo/Sqlite.php on line 187
.PHP Deprecated:  Creation of dynamic property 
Horde_Rdo_Test_Objects_SomeLazyBaseObjectMapper::$adapter is deprecated 
in 
/tmp/autopkgtest-lxc.fj53cage/downtmp/build.udq/src/Horde_Rdo-2.1.0/lib/Horde/Rdo/Mapper.php 
on line 93
PHP Deprecated:  Creation of dynamic property 
Horde_Rdo_Test_Objects_SomeEagerBaseObjectMapper::$adapter is deprecated 
in 
/tmp/autopkgtest-lxc.fj53cage/downtmp/build.udq/src/Horde_Rdo-2.1.0/lib/Horde/Rdo/Mapper.php 
on line 93
PHP Deprecated:  Creation of dynamic property 
Horde_Rdo_Test_Objects_ManyToManyAMapper::$adapter is deprecated in 

Bug#1028953: mirror submission for deb.holownych.com

2023-01-14 Thread Mike Holownych
Package: mirrors
Severity: wishlist
User: mirr...@packages.debian.org
Usertags: mirror-submission

Submission-Type: new
Site: deb.holownych.com
Type: leaf
Archive-architecture: amd64 arm64 armhf i386
Archive-http: /debian/
Maintainer: Mike Holownych 
Country: CA Canada
Location: Toronto
Sponsor: Holownych https://holownych.com




Trace Url: http://deb.holownych.com/debian/project/trace/
Trace Url: http://deb.holownych.com/debian/project/trace/ftp-master.debian.org
Trace Url: http://deb.holownych.com/debian/project/trace/deb.holownych.com



Bug#1028774: macsyfinder: FTBFS: RuntimeError: cannot join current thread

2023-01-14 Thread Nilesh Patra

Hi Lucas,

On Sat, 14 Jan 2023 13:41:14 +0100 Lucas Nussbaum  wrote:

Source: macsyfinder
Version: 2.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230113 ftbfs-bookworm
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:240: python3.11 setup.py test 
> running test

> WARNING: Testing via this command is deprecated and will be removed in a 
future version. Users looking for a generic test entry point independent of test 
runner are encouraged to use tox.
> running egg_info
> creating MacSyFinder.egg-info


It passes for me in a clean unstable chroot. Could you please check if 
this is still persistent or was just a on-off thing?


Thanks
Nilesh



Bug#1028952: php-horde-util: autopkgtest needs update for new version of php-defaults

2023-01-14 Thread Paul Gevers

Source: php-horde-util
Version: 2.5.12-1
Severity: serious
X-Debbugs-CC: php-defau...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults

[Warning in the flood my other bugs: failure in test]

Dear maintainer(s),

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


   passfail
php-defaults   from testing93
php-horde-util from testing2.5.12-1
all others from testingfrom testing

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

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


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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-horde-util/30356872/log.gz

There were 3 failures:

1) Horde_Util_StringTest::testUpperTurkish
Failed asserting that two strings are equal.
--- Expected
+++ Actual
@@ @@
-'ABCDEFGHİI'
+'ABCDEFGHII'

/tmp/autopkgtest-lxc.gj_ux5tg/downtmp/build.g2n/src/Horde_Util-2.5.12/test/Horde/Util/StringTest.php:43
/usr/bin/phpunit:73

2) Horde_Util_StringTest::testLowerTurkish
Failed asserting that two strings are equal.
--- Expected
+++ Actual
@@ @@
-'abcdefghiı'
+'abcdefghii'

/tmp/autopkgtest-lxc.gj_ux5tg/downtmp/build.g2n/src/Horde_Util-2.5.12/test/Horde/Util/StringTest.php:74
/usr/bin/phpunit:73

3) Horde_Util_StringTest::testUcfirstTurkish
Failed asserting that two strings are equal.
--- Expected
+++ Actual
@@ @@
-'İnteger'
+'Integer'

/tmp/autopkgtest-lxc.gj_ux5tg/downtmp/build.g2n/src/Horde_Util-2.5.12/test/Horde/Util/StringTest.php:123
/usr/bin/phpunit:73

FAILURES!
Tests: 87, Assertions: 207, Failures: 3.
autopkgtest [06:17:53]: test phpunit



OpenPGP_signature
Description: OpenPGP digital signature


Bug#1028951: php-horde-imap-client: autopkgtest needs update for new version of php-defaults

2023-01-14 Thread Paul Gevers

Source: php-horde-imap-client
Version: 2.30.6-1
Severity: serious
X-Debbugs-CC: php-defau...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults

Dear maintainer(s),

[Warning in the flood my other bugs: failure in test]

With a recent upload of php-defaults the autopkgtest of 
php-horde-imap-client fails in testing when that autopkgtest is run with 
the binary packages of php-defaults from unstable. It passes when run 
with only packages from testing. In tabular form:


   passfail
php-defaults   from testing93
php-horde-imap-client  from testing2.30.6-1
all others from testingfrom testing

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

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


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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-horde-imap-client/30356856/log.gz


There was 1 failure:

1) Horde_Imap_Client_Data_Format_Mailbox_MailboxTest::testBadInput
Failed asserting that two strings are equal.
--- Expected
+++ Actual
@@ @@
-''
+Binary String: 0x666f6f00

/tmp/autopkgtest-lxc.u6c46v49/downtmp/build.WlH/src/Horde_Imap_Client-2.30.6/test/Horde/Imap/Client/Data/Format/Mailbox/MailboxTest.php:117


OpenPGP_signature
Description: OpenPGP digital signature


Bug#1028950: php-horde-view: (autopkgtest) needs update for php8.2: deprecation warnings on stderr

2023-01-14 Thread Paul Gevers

Source: php-horde-view
Version: 2.0.6-9
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults

Dear maintainer(s),

We are in the transition of replacing php8.1 with php8.2 [0]. With a 
recent upload of php-defaults the autopkgtest of php-horde-view fails in 
testing when that autopkgtest is run with the binary packages of 
php-defaults from unstable. It passes when run with only packages from 
testing. In tabular form:


   passfail
php-defaults   from testing93
php-horde-view from testing2.0.6-9
all others from testingfrom testing

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

Currently this regression is blocking the migration of php-defaults to 
testing [1]. https://www.php.net/ChangeLog-8.php lists the changes since 
7.4 and may help to identify what needs to be updated.


The test itself passes, but the autopkgtest fails because of deprecation 
warnings on stderr. Output on stderr makes autopkgtest fail by default, 
unless `allow-stderr` is added to the set of restrictions. As a flood of 
deprecation warnings in server logs may be very unwanted, I'm not saying 
that adding the restriction to autopkgtest is the right answer to this 
issue, but because of the php transition, it needs to be resolved one 
way or the other.


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

Paul

[0] https://bugs.debian.org/1014460
[1] https://qa.debian.org/excuses.php?package=php-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-horde-view/30356873/log.gz


.PHP Deprecated:  Creation of dynamic property 
Horde_View_Helper_NumberTest::$helper is deprecated in 
/tmp/autopkgtest-lxc.dl0apazk/downtmp/build.W6J/src/Horde_View-2.0.6/test/Horde/View/Helper/NumberTest.php 
on line 29
..W.PHP Deprecated:  Creation of dynamic property 
Horde_View_Helper_TagTest::$view is deprecated in 
/tmp/autopkgtest-lxc.dl0apazk/downtmp/build.W6J/src/Horde_View-2.0.6/test/Horde/View/Helper/TagTest.php 
on line 29
PHP Deprecated:  Creation of dynamic property 
Horde_View_Helper_TagTest::$view is deprecated in 
/tmp/autopkgtest-lxc.dl0apazk/downtmp/build.W6J/src/Horde_View-2.0.6/test/Horde/View/Helper/TagTest.php 
on line 29
PHP Deprecated:  Creation of dynamic property 
Horde_View_Helper_TagTest::$view is deprecated in 
/tmp/autopkgtest-lxc.dl0apazk/downtmp/build.W6J/src/Horde_View-2.0.6/test/Horde/View/Helper/TagTest.php 
on line 29
PHP Deprecated:  Creation of dynamic property 
Horde_View_Helper_TagTest::$view is deprecated in 
/tmp/autopkgtest-lxc.dl0apazk/downtmp/build.W6J/src/Horde_View-2.0.6/test/Horde/View/Helper/TagTest.php 
on line 29
PHP Deprecated:  Creation of dynamic property 
Horde_View_Helper_TagTest::$view is deprecated in 
/tmp/autopkgtest-lxc.dl0apazk/downtmp/build.W6J/src/Horde_View-2.0.6/test/Horde/View/Helper/TagTest.php 
on line 29
PHP Deprecated:  Creation of dynamic property 
Horde_View_Helper_TagTest::$view is deprecated in 
/tmp/autopkgtest-lxc.dl0apazk/downtmp/build.W6J/src/Horde_View-2.0.6/test/Horde/View/Helper/TagTest.php 
on line 29
PHP Deprecated:  Creation of dynamic property 
Horde_View_Helper_TagTest::$view is deprecated in 
/tmp/autopkgtest-lxc.dl0apazk/downtmp/build.W6J/src/Horde_View-2.0.6/test/Horde/View/Helper/TagTest.php 
on line 29
PHP Deprecated:  Creation of dynamic property 
Horde_View_Helper_TagTest::$view is deprecated in 
/tmp/autopkgtest-lxc.dl0apazk/downtmp/build.W6J/src/Horde_View-2.0.6/test/Horde/View/Helper/TagTest.php 
on line 29
PHP Deprecated:  Creation of dynamic property 
Horde_View_Helper_TagTest::$view is deprecated in 
/tmp/autopkgtest-lxc.dl0apazk/downtmp/build.W6J/src/Horde_View-2.0.6/test/Horde/View/Helper/TagTest.php 
on line 29
PHP Deprecated:  Creation of dynamic property 
Horde_View_Helper_TagTest::$view is deprecated in 
/tmp/autopkgtest-lxc.dl0apazk/downtmp/build.W6J/src/Horde_View-2.0.6/test/Horde/View/Helper/TagTest.php 
on line 29
PHP Deprecated:  Creation of dynamic property 
Horde_View_Helper_TextTest::$view is deprecated in 
/tmp/autopkgtest-lxc.dl0apazk/downtmp/build.W6J/src/Horde_View-2.0.6/test/Horde/View/Helper/TextTest.php 
on line 29
PHP Deprecated:  Creation of dynamic property 
Horde_View_Helper_TextTest::$view is deprecated in 
/tmp/autopkgtest-lxc.dl0apazk/downtmp/build.W6J/src/Horde_View-2.0.6/test/Horde/View/Helper/TextTest.php 
on line 29
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Creation of dynamic property 
Horde_View_Helper_TextTest::$view is deprecated in 
/tmp/autopkgtest-lxc.dl0apazk/downtmp/build.W6J/src/Horde_View-2.0.6/test/Horde/View/Helper/TextTest.php 
on line 29
PHP Deprecated:  

Bug#1028949: php-horde-token: (autopkgtest) needs update for php8.2: deprecation warnings on stderr

2023-01-14 Thread Paul Gevers

Source: php-horde-token
Version: 2.0.9-8
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults

Dear maintainer(s),

We are in the transition of replacing php8.1 with php8.2 [0]. With a 
recent upload of php-defaults the autopkgtest of php-horde-token fails 
in testing when that autopkgtest is run with the binary packages of 
php-defaults from unstable. It passes when run with only packages from 
testing. In tabular form:


   passfail
php-defaults   from testing93
php-horde-tokenfrom testing2.0.9-8
all others from testingfrom testing

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

Currently this regression is blocking the migration of php-defaults to 
testing [1]. https://www.php.net/ChangeLog-8.php lists the changes since 
7.4 and may help to identify what needs to be updated.


The test itself passes, but the autopkgtest fails because of deprecation 
warnings on stderr. Output on stderr makes autopkgtest fail by default, 
unless `allow-stderr` is added to the set of restrictions. As a flood of 
deprecation warnings in server logs may be very unwanted, I'm not saying 
that adding the restriction to autopkgtest is the right answer to this 
issue, but because of the php transition, it needs to be resolved one 
way or the other.


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

Paul

[0] https://bugs.debian.org/1014460
[1] https://qa.debian.org/excuses.php?package=php-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-horde-token/30356871/log.gz

PHPUnit 9.5.27 by Sebastian Bergmann and contributors.

Runtime:   PHP 8.2.1
Configuration: 
/tmp/autopkgtest-lxc.dt2hw5bk/downtmp/build.r5l/src/Horde_Token-2.0.9/test/Horde/Token/phpunit.xml

Warning:   Your XML configuration validates against a deprecated schema.
Suggestion:Migrate your XML configuration using 
"--migrate-configuration"!


PHP Deprecated:  Creation of dynamic property 
Horde_Token_Unit_FileTest::$_temp_dir is deprecated in 
/tmp/autopkgtest-lxc.dt2hw5bk/downtmp/build.r5l/src/Horde_Token-2.0.9/test/Horde/Token/Unit/FileTest.php 
on line 51
.PHP Deprecated:  Creation of dynamic property 
Horde_Token_Unit_FileTest::$_temp_dir is deprecated in 
/tmp/autopkgtest-lxc.dt2hw5bk/downtmp/build.r5l/src/Horde_Token-2.0.9/test/Horde/Token/Unit/FileTest.php 
on line 51
.PHP Deprecated:  Creation of dynamic property 
Horde_Token_Unit_FileTest::$_temp_dir is deprecated in 
/tmp/autopkgtest-lxc.dt2hw5bk/downtmp/build.r5l/src/Horde_Token-2.0.9/test/Horde/Token/Unit/FileTest.php 
on line 51
.PHP Deprecated:  Creation of dynamic property 
Horde_Token_Unit_FileTest::$_temp_dir is deprecated in 
/tmp/autopkgtest-lxc.dt2hw5bk/downtmp/build.r5l/src/Horde_Token-2.0.9/test/Horde/Token/Unit/FileTest.php 
on line 51
.PHP Deprecated:  Creation of dynamic property 
Horde_Token_Unit_FileTest::$_temp_dir is deprecated in 
/tmp/autopkgtest-lxc.dt2hw5bk/downtmp/build.r5l/src/Horde_Token-2.0.9/test/Horde/Token/Unit/FileTest.php 
on line 51
.PHP Deprecated:  Creation of dynamic property 
Horde_Token_Unit_FileTest::$_temp_dir is deprecated in 
/tmp/autopkgtest-lxc.dt2hw5bk/downtmp/build.r5l/src/Horde_Token-2.0.9/test/Horde/Token/Unit/FileTest.php 
on line 51
.PHP Deprecated:  Creation of dynamic property 
Horde_Token_Unit_FileTest::$_temp_dir is deprecated in 
/tmp/autopkgtest-lxc.dt2hw5bk/downtmp/build.r5l/src/Horde_Token-2.0.9/test/Horde/Token/Unit/FileTest.php 
on line 51
.PHP Deprecated:  Creation of dynamic property 
Horde_Token_Unit_FileTest::$_temp_dir is deprecated in 
/tmp/autopkgtest-lxc.dt2hw5bk/downtmp/build.r5l/src/Horde_Token-2.0.9/test/Horde/Token/Unit/FileTest.php 
on line 51
.PHP Deprecated:  Creation of dynamic property 
Horde_Token_Unit_FileTest::$_temp_dir is deprecated in 
/tmp/autopkgtest-lxc.dt2hw5bk/downtmp/build.r5l/src/Horde_Token-2.0.9/test/Horde/Token/Unit/FileTest.php 
on line 51
..PHP Deprecated:  Creation of dynamic property 
Horde_Token_Unit_FileTest::$_temp_dir is deprecated in 
/tmp/autopkgtest-lxc.dt2hw5bk/downtmp/build.r5l/src/Horde_Token-2.0.9/test/Horde/Token/Unit/FileTest.php 
on line 51
PHP Deprecated:  Creation of dynamic property 
Horde_Token_Unit_FileTest::$_temp_dir is deprecated in 
/tmp/autopkgtest-lxc.dt2hw5bk/downtmp/build.r5l/src/Horde_Token-2.0.9/test/Horde/Token/Unit/FileTest.php 
on line 51
PHP Deprecated:  Creation of dynamic property 
Horde_Token_Unit_FileTest::$_temp_dir is deprecated in 
/tmp/autopkgtest-lxc.dt2hw5bk/downtmp/build.r5l/src/Horde_Token-2.0.9/test/Horde/Token/Unit/FileTest.php 
on line 51
PHP Deprecated:  Creation of dynamic property 
Horde_Token_Unit_FileTest::$_temp_dir is deprecated in 
/tmp/autopkgtest-lxc.dt2hw5bk/downtmp/build.r5l/src/Horde_Token-2.0.9/test/Horde/Token/Unit/FileTest.php 
on line 51
PHP Deprecated:  

Bug#1028947: php-horde-text-diff: (autopkgtest) needs update for php8.2: deprecation warnings on stderr

2023-01-14 Thread Paul Gevers

Source: php-horde-text-diff
Version: 2.2.1-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults

Dear maintainer(s),

We are in the transition of replacing php8.1 with php8.2 [0]. With a 
recent upload of php-defaults the autopkgtest of php-horde-text-diff 
fails in testing when that autopkgtest is run with the binary packages 
of php-defaults from unstable. It passes when run with only packages 
from testing. In tabular form:


   passfail
php-defaults   from testing93
php-horde-text-difffrom testing2.2.1-2
all others from testingfrom testing

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

Currently this regression is blocking the migration of php-defaults to 
testing [1]. https://www.php.net/ChangeLog-8.php lists the changes since 
7.4 and may help to identify what needs to be updated.


The test itself passes, but the autopkgtest fails because of deprecation 
warnings on stderr. Output on stderr makes autopkgtest fail by default, 
unless `allow-stderr` is added to the set of restrictions. As a flood of 
deprecation warnings in server logs may be very unwanted, I'm not saying 
that adding the restriction to autopkgtest is the right answer to this 
issue, but because of the php transition, it needs to be resolved one 
way or the other.


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

Paul

[0] https://bugs.debian.org/1014460
[1] https://qa.debian.org/excuses.php?package=php-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-horde-text-diff/30356869/log.gz


PHP Deprecated:  Creation of dynamic property 
Horde_Text_Diff_Engine_Native::$xv is deprecated in 
/tmp/autopkgtest-lxc.rhry6cbi/downtmp/build.i3Q/src/Horde_Text_Diff-2.2.1/lib/Horde/Text/Diff/Engine/Native.php 
on line 40
PHP Deprecated:  Creation of dynamic property 
Horde_Text_Diff_Engine_Native::$yind is deprecated in 
/tmp/autopkgtest-lxc.rhry6cbi/downtmp/build.i3Q/src/Horde_Text_Diff-2.2.1/lib/Horde/Text/Diff/Engine/Native.php 
on line 41
PHP Deprecated:  Creation of dynamic property 
Horde_Text_Diff_Engine_Native::$xind is deprecated in 
/tmp/autopkgtest-lxc.rhry6cbi/downtmp/build.i3Q/src/Horde_Text_Diff-2.2.1/lib/Horde/Text/Diff/Engine/Native.php 
on line 41
PHP Deprecated:  Creation of dynamic property 
Horde_Text_Diff_Engine_Native::$ychanged is deprecated in 
/tmp/autopkgtest-lxc.rhry6cbi/downtmp/build.i3Q/src/Horde_Text_Diff-2.2.1/lib/Horde/Text/Diff/Engine/Native.php 
on line 39
PHP Deprecated:  Creation of dynamic property 
Horde_Text_Diff_Engine_Native::$xchanged is deprecated in 
/tmp/autopkgtest-lxc.rhry6cbi/downtmp/build.i3Q/src/Horde_Text_Diff-2.2.1/lib/Horde/Text/Diff/Engine/Native.php 
on line 39
PHP Deprecated:  Creation of dynamic property 
Horde_Text_Diff_Engine_Native::$yv is deprecated in 
/tmp/autopkgtest-lxc.rhry6cbi/downtmp/build.i3Q/src/Horde_Text_Diff-2.2.1/lib/Horde/Text/Diff/Engine/Native.php 
on line 40
PHP Deprecated:  Creation of dynamic property 
Horde_Text_Diff_Engine_Native::$xv is deprecated in 
/tmp/autopkgtest-lxc.rhry6cbi/downtmp/build.i3Q/src/Horde_Text_Diff-2.2.1/lib/Horde/Text/Diff/Engine/Native.php 
on line 40
PHP Deprecated:  Creation of dynamic property 
Horde_Text_Diff_Engine_Native::$yind is deprecated in 
/tmp/autopkgtest-lxc.rhry6cbi/downtmp/build.i3Q/src/Horde_Text_Diff-2.2.1/lib/Horde/Text/Diff/Engine/Native.php 
on line 41
PHP Deprecated:  Creation of dynamic property 
Horde_Text_Diff_Engine_Native::$xind is deprecated in 
/tmp/autopkgtest-lxc.rhry6cbi/downtmp/build.i3Q/src/Horde_Text_Diff-2.2.1/lib/Horde/Text/Diff/Engine/Native.php 
on line 41
PHP Deprecated:  Creation of dynamic property 
Horde_Text_Diff_Engine_Native::$ychanged is deprecated in 
/tmp/autopkgtest-lxc.rhry6cbi/downtmp/build.i3Q/src/Horde_Text_Diff-2.2.1/lib/Horde/Text/Diff/Engine/Native.php 
on line 39
PHP Deprecated:  Creation of dynamic property 
Horde_Text_Diff_Engine_Native::$xchanged is deprecated in 
/tmp/autopkgtest-lxc.rhry6cbi/downtmp/build.i3Q/src/Horde_Text_Diff-2.2.1/lib/Horde/Text/Diff/Engine/Native.php 
on line 39
PHP Deprecated:  Creation of dynamic property 
Horde_Text_Diff_Engine_Native::$yv is deprecated in 
/tmp/autopkgtest-lxc.rhry6cbi/downtmp/build.i3Q/src/Horde_Text_Diff-2.2.1/lib/Horde/Text/Diff/Engine/Native.php 
on line 40
PHP Deprecated:  Creation of dynamic property 
Horde_Text_Diff_Engine_Native::$xv is deprecated in 
/tmp/autopkgtest-lxc.rhry6cbi/downtmp/build.i3Q/src/Horde_Text_Diff-2.2.1/lib/Horde/Text/Diff/Engine/Native.php 
on line 40
PHP Deprecated:  Creation of dynamic property 
Horde_Text_Diff_Engine_Native::$yind is deprecated in 
/tmp/autopkgtest-lxc.rhry6cbi/downtmp/build.i3Q/src/Horde_Text_Diff-2.2.1/lib/Horde/Text/Diff/Engine/Native.php 
on line 41
PHP Deprecated:  Creation of dynamic property 

Bug#1028948: php-horde-text-flowed: (autopkgtest) needs update for php8.2: deprecation warnings on stderr

2023-01-14 Thread Paul Gevers

Source: php-horde-text-flowed
Version: 2.0.4-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults

Dear maintainer(s),

We are in the transition of replacing php8.1 with php8.2 [0]. With a 
recent upload of php-defaults the autopkgtest of php-horde-text-flowed 
fails in testing when that autopkgtest is run with the binary packages 
of php-defaults from unstable. It passes when run with only packages 
from testing. In tabular form:


   passfail
php-defaults   from testing93
php-horde-text-flowed  from testing2.0.4-2
all others from testingfrom testing

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

Currently this regression is blocking the migration of php-defaults to 
testing [1]. https://www.php.net/ChangeLog-8.php lists the changes since 
7.4 and may help to identify what needs to be updated.


The test itself passes, but the autopkgtest fails because of deprecation 
warnings on stderr. Output on stderr makes autopkgtest fail by default, 
unless `allow-stderr` is added to the set of restrictions. As a flood of 
deprecation warnings in server logs may be very unwanted, I'm not saying 
that adding the restriction to autopkgtest is the right answer to this 
issue, but because of the php transition, it needs to be resolved one 
way or the other.


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

Paul

[0] https://bugs.debian.org/1014460
[1] https://qa.debian.org/excuses.php?package=php-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-horde-text-flowed/30356870/log.gz

PHPUnit 9.5.27 by Sebastian Bergmann and contributors.

Runtime:   PHP 8.2.1
Configuration: 
/tmp/autopkgtest-lxc.hfseeczg/downtmp/build.wgj/src/Horde_Text_Flowed-2.0.4/test/Horde/Text/Flowed/phpunit.xml


PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
.PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
.PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
. 3 / 3 
(100%)


Time: 00:00.003, Memory: 6.00 MB

OK (3 tests, 9 assertions)
autopkgtest [06:17:32]: test phpunit



OpenPGP_signature
Description: OpenPGP digital signature


Bug#1028946: php-horde-support: (autopkgtest) needs update for php8.2: deprecation warnings on stderr

2023-01-14 Thread Paul Gevers

Source: php-horde-support
Version: 2.2.2-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults

Dear maintainer(s),

We are in the transition of replacing php8.1 with php8.2 [0]. With a 
recent upload of php-defaults the autopkgtest of php-horde-support fails 
in testing when that autopkgtest is run with the binary packages of 
php-defaults from unstable. It passes when run with only packages from 
testing. In tabular form:


   passfail
php-defaults   from testing93
php-horde-support  from testing2.2.2-1
all others from testingfrom testing

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

Currently this regression is blocking the migration of php-defaults to 
testing [1]. https://www.php.net/ChangeLog-8.php lists the changes since 
7.4 and may help to identify what needs to be updated.


The test itself passes, but the autopkgtest fails because of deprecation 
warnings on stderr. Output on stderr makes autopkgtest fail by default, 
unless `allow-stderr` is added to the set of restrictions. As a flood of 
deprecation warnings in server logs may be very unwanted, I'm not saying 
that adding the restriction to autopkgtest is the right answer to this 
issue, but because of the php transition, it needs to be resolved one 
way or the other.


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

Paul

[0] https://bugs.debian.org/1014460
[1] https://qa.debian.org/excuses.php?package=php-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-horde-support/30356868/log.gz

PHPUnit 9.5.27 by Sebastian Bergmann and contributors.

Runtime:   PHP 8.2.1
Configuration: 
/tmp/autopkgtest-lxc.1cpa922w/downtmp/build.5c4/src/Horde_Support-2.2.2/test/Horde/Support/phpunit.xml


PHP Deprecated: 
Creation of dynamic property 
Horde_Support_Inflector::$_uncountables_keys is deprecated in 
/tmp/autopkgtest-lxc.1cpa922w/downtmp/build.5c4/src/Horde_Support-2.2.2/lib/Horde/Support/Inflector.php 
on line 128
PHP Deprecated:  Creation of dynamic property 
Horde_Support_InflectorTest::$inflector is deprecated in 
/tmp/autopkgtest-lxc.1cpa922w/downtmp/build.5c4/src/Horde_Support-2.2.2/test/Horde/Support/InflectorTest.php 
on line 42
.PHP Deprecated:  Creation of dynamic property 
Horde_Support_Inflector::$_uncountables_keys is deprecated in 
/tmp/autopkgtest-lxc.1cpa922w/downtmp/build.5c4/src/Horde_Support-2.2.2/lib/Horde/Support/Inflector.php 
on line 128
PHP Deprecated:  Creation of dynamic property 
Horde_Support_InflectorTest::$inflector is deprecated in 
/tmp/autopkgtest-lxc.1cpa922w/downtmp/build.5c4/src/Horde_Support-2.2.2/test/Horde/Support/InflectorTest.php 
on line 42
.PHP Deprecated:  Creation of dynamic property 
Horde_Support_Inflector::$_uncountables_keys is deprecated in 
/tmp/autopkgtest-lxc.1cpa922w/downtmp/build.5c4/src/Horde_Support-2.2.2/lib/Horde/Support/Inflector.php 
on line 128
PHP Deprecated:  Creation of dynamic property 
Horde_Support_InflectorTest::$inflector is deprecated in 
/tmp/autopkgtest-lxc.1cpa922w/downtmp/build.5c4/src/Horde_Support-2.2.2/test/Horde/Support/InflectorTest.php 
on line 42
.PHP Deprecated:  Creation of dynamic property 
Horde_Support_Inflector::$_uncountables_keys is deprecated in 
/tmp/autopkgtest-lxc.1cpa922w/downtmp/build.5c4/src/Horde_Support-2.2.2/lib/Horde/Support/Inflector.php 
on line 128
PHP Deprecated:  Creation of dynamic property 
Horde_Support_InflectorTest::$inflector is deprecated in 
/tmp/autopkgtest-lxc.1cpa922w/downtmp/build.5c4/src/Horde_Support-2.2.2/test/Horde/Support/InflectorTest.php 
on line 42
IPHP Deprecated:  Creation of dynamic property 
Horde_Support_Inflector::$_uncountables_keys is deprecated in 
/tmp/autopkgtest-lxc.1cpa922w/downtmp/build.5c4/src/Horde_Support-2.2.2/lib/Horde/Support/Inflector.php 
on line 128
PHP Deprecated:  Creation of dynamic property 
Horde_Support_InflectorTest::$inflector is deprecated in 
/tmp/autopkgtest-lxc.1cpa922w/downtmp/build.5c4/src/Horde_Support-2.2.2/test/Horde/Support/InflectorTest.php 
on line 42
.PHP Deprecated:  Creation of dynamic property 
Horde_Support_Inflector::$_uncountables_keys is deprecated in 
/tmp/autopkgtest-lxc.1cpa922w/downtmp/build.5c4/src/Horde_Support-2.2.2/lib/Horde/Support/Inflector.php 
on line 128
PHP Deprecated:  Creation of dynamic property 
Horde_Support_InflectorTest::$inflector is deprecated in 
/tmp/autopkgtest-lxc.1cpa922w/downtmp/build.5c4/src/Horde_Support-2.2.2/test/Horde/Support/InflectorTest.php 
on line 42
PHP Deprecated:  Creation of dynamic property 
Horde_Support_Inflector::$_uncountables_keys is deprecated in 
/tmp/autopkgtest-lxc.1cpa922w/downtmp/build.5c4/src/Horde_Support-2.2.2/lib/Horde/Support/Inflector.php 
on line 128
PHP Deprecated:  Creation of 

Bug#1028945: php-horde-service-gravatar: (autopkgtest) needs update for php8.2: deprecation warnings on stderr

2023-01-14 Thread Paul Gevers

Source: php-horde-service-gravatar
Version: 1.0.1-9
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults

Dear maintainer(s),

We are in the transition of replacing php8.1 with php8.2 [0]. With a 
recent upload of php-defaults the autopkgtest of 
php-horde-service-gravatar fails in testing when that autopkgtest is run 
with the binary packages of php-defaults from unstable. It passes when 
run with only packages from testing. In tabular form:


   passfail
php-defaults   from testing93
php-horde-service-gravatar from testing1.0.1-9
all others from testingfrom testing

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

Currently this regression is blocking the migration of php-defaults to 
testing [1]. https://www.php.net/ChangeLog-8.php lists the changes since 
7.4 and may help to identify what needs to be updated.


The test itself passes, but the autopkgtest fails because of deprecation 
warnings on stderr. Output on stderr makes autopkgtest fail by default, 
unless `allow-stderr` is added to the set of restrictions. As a flood of 
deprecation warnings in server logs may be very unwanted, I'm not saying 
that adding the restriction to autopkgtest is the right answer to this 
issue, but because of the php transition, it needs to be resolved one 
way or the other.


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

Paul

[0] https://bugs.debian.org/1014460
[1] https://qa.debian.org/excuses.php?package=php-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-horde-service-gravatar/30356867/log.gz

PHPUnit 9.5.27 by Sebastian Bergmann and contributors.

Runtime:   PHP 8.2.1
Configuration: 
/tmp/autopkgtest-lxc.ykdwxav8/downtmp/build.nkx/src/Horde_Service_Gravatar-1.0.1/test/Horde/Service/Gravatar/phpunit.xml


..PHP Deprecated:  Creation of dynamic property 
Horde_Http_Response_Mock::$_stream is deprecated in 
/usr/share/php/Horde/Http/Response/Mock.php on line 25

..  16 / 16 (100%)

Time: 00:00.427, Memory: 6.00 MB

OK (16 tests, 20 assertions)
autopkgtest [06:17:13]: test phpunit



OpenPGP_signature
Description: OpenPGP digital signature


Bug#1028944: php-horde-serialize: (autopkgtest) needs update for php8.2: deprecation warnings on stderr

2023-01-14 Thread Paul Gevers

Source: php-horde-serialize
Version: 2.0.5-9
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults

Dear maintainer(s),

We are in the transition of replacing php8.1 with php8.2 [0]. With a 
recent upload of php-defaults the autopkgtest of php-horde-serialize 
fails in testing when that autopkgtest is run with the binary packages 
of php-defaults from unstable. It passes when run with only packages 
from testing. In tabular form:


   passfail
php-defaults   from testing93
php-horde-serializefrom testing2.0.5-9
all others from testingfrom testing

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

Currently this regression is blocking the migration of php-defaults to 
testing [1]. https://www.php.net/ChangeLog-8.php lists the changes since 
7.4 and may help to identify what needs to be updated.


The test itself passes, but the autopkgtest fails because of deprecation 
warnings on stderr. Output on stderr makes autopkgtest fail by default, 
unless `allow-stderr` is added to the set of restrictions. As a flood of 
deprecation warnings in server logs may be very unwanted, I'm not saying 
that adding the restriction to autopkgtest is the right answer to this 
issue, but because of the php transition, it needs to be resolved one 
way or the other.


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

Paul

[0] https://bugs.debian.org/1014460
[1] https://qa.debian.org/excuses.php?package=php-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-horde-serialize/30356866/log.gz

PHPUnit 9.5.27 by Sebastian Bergmann and contributors.

Runtime:   PHP 8.2.1
Configuration: 
/tmp/autopkgtest-lxc.wmpitqx9/downtmp/build.mjM/src/Horde_Serialize-2.0.5/test/Horde/Serialize/phpunit.xml


..PHP Deprecated:  Function utf8_encode() is deprecated in 
/usr/share/php/Horde/String.php on line 119
..8 / 8 
(100%)


Time: 00:00.009, Memory: 6.00 MB

OK (8 tests, 77 assertions)
autopkgtest [06:17:13]: test phpunit



OpenPGP_signature
Description: OpenPGP digital signature


Bug#1028943: php-horde-secret: (autopkgtest) needs update for php8.2: deprecation warnings on stderr

2023-01-14 Thread Paul Gevers

Source: php-horde-secret
Version: 2.0.6-9
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults

Dear maintainer(s),

We are in the transition of replacing php8.1 with php8.2 [0]. With a 
recent upload of php-defaults the autopkgtest of php-horde-secret fails 
in testing when that autopkgtest is run with the binary packages of 
php-defaults from unstable. It passes when run with only packages from 
testing. In tabular form:


   passfail
php-defaults   from testing93
php-horde-secret   from testing2.0.6-9
all others from testingfrom testing

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

Currently this regression is blocking the migration of php-defaults to 
testing [1]. https://www.php.net/ChangeLog-8.php lists the changes since 
7.4 and may help to identify what needs to be updated.


The test itself passes, but the autopkgtest fails because of deprecation 
warnings on stderr. Output on stderr makes autopkgtest fail by default, 
unless `allow-stderr` is added to the set of restrictions. As a flood of 
deprecation warnings in server logs may be very unwanted, I'm not saying 
that adding the restriction to autopkgtest is the right answer to this 
issue, but because of the php transition, it needs to be resolved one 
way or the other.


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

Paul

[0] https://bugs.debian.org/1014460
[1] https://qa.debian.org/excuses.php?package=php-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-horde-secret/30356865/log.gz

PHPUnit 9.5.27 by Sebastian Bergmann and contributors.

Runtime:   PHP 8.2.1
Configuration: 
/tmp/autopkgtest-lxc.ucs68m9x/downtmp/build.55S/src/Horde_Secret-2.0.6/test/Horde/Secret/phpunit.xml

Warning:   Your XML configuration validates against a deprecated schema.
Suggestion:Migrate your XML configuration using 
"--migrate-configuration"!


PHP Deprecated:  Creation of dynamic property Horde_Crypt_Blowfish::$iv 
is deprecated in /usr/share/php/Horde/Crypt/Blowfish.php on line 173
.PHP Deprecated:  Creation of dynamic property Horde_Crypt_Blowfish::$iv 
is deprecated in /usr/share/php/Horde/Crypt/Blowfish.php on line 173
.PHP Deprecated:  Creation of dynamic property Horde_Crypt_Blowfish::$iv 
is deprecated in /usr/share/php/Horde/Crypt/Blowfish.php on line 173
.PHP Deprecated:  Creation of dynamic property Horde_Crypt_Blowfish::$iv 
is deprecated in /usr/share/php/Horde/Crypt/Blowfish.php on line 173
..PHP Deprecated:  Creation of dynamic property 
Horde_Crypt_Blowfish::$iv is deprecated in 
/usr/share/php/Horde/Crypt/Blowfish.php on line 173

...8 / 8 (100%)

Time: 00:00.020, Memory: 6.00 MB

OK (8 tests, 8 assertions)
autopkgtest [06:17:10]: test phpunit



OpenPGP_signature
Description: OpenPGP digital signature


Bug#1028942: php-horde-passwd: (autopkgtest) needs update for php8.2: deprecation warnings on stderr

2023-01-14 Thread Paul Gevers

Source: php-horde-passwd
Version: 5.0.7-8
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults

Dear maintainer(s),

We are in the transition of replacing php8.1 with php8.2 [0]. With a 
recent upload of php-defaults the autopkgtest of php-horde-passwd fails 
in testing when that autopkgtest is run with the binary packages of 
php-defaults from unstable. It passes when run with only packages from 
testing. In tabular form:


   passfail
php-defaults   from testing93
php-horde-passwd   from testing5.0.7-8
all others from testingfrom testing

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

Currently this regression is blocking the migration of php-defaults to 
testing [1]. https://www.php.net/ChangeLog-8.php lists the changes since 
7.4 and may help to identify what needs to be updated.


The test itself passes, but the autopkgtest fails because of deprecation 
warnings on stderr. Output on stderr makes autopkgtest fail by default, 
unless `allow-stderr` is added to the set of restrictions. As a flood of 
deprecation warnings in server logs may be very unwanted, I'm not saying 
that adding the restriction to autopkgtest is the right answer to this 
issue, but because of the php transition, it needs to be resolved one 
way or the other.


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

Paul

[0] https://bugs.debian.org/1014460
[1] https://qa.debian.org/excuses.php?package=php-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-horde-passwd/30356864/log.gz

PHPUnit 9.5.27 by Sebastian Bergmann and contributors.

Runtime:   PHP 8.2.1
Configuration: 
/tmp/autopkgtest-lxc.lp2dbuv_/downtmp/build.93U/src/passwd-5.0.7/test/Passwd/phpunit.xml


PHP Deprecated:  Creation of dynamic property 
Passwd_Factory_Driver::$backends is deprecated in 
/tmp/autopkgtest-lxc.lp2dbuv_/downtmp/build.93U/src/passwd-5.0.7/test/Passwd/Unit/Driver/SqlTest.php 
on line 26
PHP Deprecated:  Callables of the form ["Horde_Db_Adapter_Pdo_Sqlite", 
"parent::execute"] are deprecated in 
/usr/share/php/Horde/Db/Adapter/Pdo/Sqlite.php on line 187
PHP Deprecated:  Callables of the form ["Horde_Db_Adapter_Pdo_Sqlite", 
"parent::execute"] are deprecated in 
/usr/share/php/Horde/Db/Adapter/Pdo/Sqlite.php on line 187
.PHP Deprecated:  Creation of dynamic property 
Passwd_Factory_Driver::$backends is deprecated in 
/tmp/autopkgtest-lxc.lp2dbuv_/downtmp/build.93U/src/passwd-5.0.7/test/Passwd/Unit/Driver/SqlTest.php 
on line 26
PHP Deprecated:  Callables of the form ["Horde_Db_Adapter_Pdo_Sqlite", 
"parent::execute"] are deprecated in 
/usr/share/php/Horde/Db/Adapter/Pdo/Sqlite.php on line 187
PHP Deprecated:  Callables of the form ["Horde_Db_Adapter_Pdo_Sqlite", 
"parent::execute"] are deprecated in 
/usr/share/php/Horde/Db/Adapter/Pdo/Sqlite.php on line 187
PHP Deprecated:  Callables of the form ["Horde_Db_Adapter_Pdo_Sqlite", 
"parent::execute"] are deprecated in 
/usr/share/php/Horde/Db/Adapter/Pdo/Sqlite.php on line 187
.III   5 / 5 
(100%)


Time: 00:00.013, Memory: 6.00 MB

There were 3 incomplete tests:

1) Passwd_Unit_Factory_DriverTest::testGettingSubdriversWorks
Factories with configuration files don't work out of the box.

/tmp/autopkgtest-lxc.lp2dbuv_/downtmp/build.93U/src/passwd-5.0.7/test/Passwd/Unit/Factory/DriverTest.php:19

2) Passwd_Unit_Factory_DriverTest::testGetBackendsReturnsResultOfSetBackends
Factories with configuration files don't work out of the box.

/tmp/autopkgtest-lxc.lp2dbuv_/downtmp/build.93U/src/passwd-5.0.7/test/Passwd/Unit/Factory/DriverTest.php:19

3) Passwd_Unit_Factory_DriverTest::testGettingTheSameDriverTwiceWorks
Factories with configuration files don't work out of the box.

/tmp/autopkgtest-lxc.lp2dbuv_/downtmp/build.93U/src/passwd-5.0.7/test/Passwd/Unit/Factory/DriverTest.php:19

OK, but incomplete, skipped, or risky tests!
Tests: 5, Assertions: 2, Incomplete: 3.
autopkgtest [06:17:12]: test phpunit



OpenPGP_signature
Description: OpenPGP digital signature


Bug#1028941: php-horde-notification: (autopkgtest) needs update for php8.2: deprecation warnings on stderr

2023-01-14 Thread Paul Gevers

Source: php-horde-notification
Version: 2.0.4-9
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults

Dear maintainer(s),

We are in the transition of replacing php8.1 with php8.2 [0]. With a 
recent upload of php-defaults the autopkgtest of php-horde-notification 
fails in testing when that autopkgtest is run with the binary packages 
of php-defaults from unstable. It passes when run with only packages 
from testing. In tabular form:


   passfail
php-defaults   from testing93
php-horde-notification from testing2.0.4-9
all others from testingfrom testing

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

Currently this regression is blocking the migration of php-defaults to 
testing [1]. https://www.php.net/ChangeLog-8.php lists the changes since 
7.4 and may help to identify what needs to be updated.


The test itself passes, but the autopkgtest fails because of deprecation 
warnings on stderr. Output on stderr makes autopkgtest fail by default, 
unless `allow-stderr` is added to the set of restrictions. As a flood of 
deprecation warnings in server logs may be very unwanted, I'm not saying 
that adding the restriction to autopkgtest is the right answer to this 
issue, but because of the php transition, it needs to be resolved one 
way or the other.


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

Paul

[0] https://bugs.debian.org/1014460
[1] https://qa.debian.org/excuses.php?package=php-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-horde-notification/30356863/log.gz

PHPUnit 9.5.27 by Sebastian Bergmann and contributors.

Runtime:   PHP 8.2.1
Configuration: 
/tmp/autopkgtest-lxc.avv7f_5c/downtmp/build.Fyn/src/Horde_Notification-2.0.4/test/Horde/Notification/phpunit.xml

Warning:   Your XML configuration validates against a deprecated schema.
Suggestion:Migrate your XML configuration using 
"--migrate-configuration"!


.IIPHP Deprecated:  Creation of dynamic property 
Horde_Notification_Class_Notification_Handler_Decorator_LogTest::$logger 
is deprecated in 
/tmp/autopkgtest-lxc.avv7f_5c/downtmp/build.Fyn/src/Horde_Notification-2.0.4/test/Horde/Notification/Class/Notification/Handler/Decorator/LogTest.php 
on line 36
PHP Deprecated:  Creation of dynamic property 
Horde_Notification_Class_Notification_Handler_Decorator_LogTest::$log is 
deprecated in 
/tmp/autopkgtest-lxc.avv7f_5c/downtmp/build.Fyn/src/Horde_Notification-2.0.4/test/Horde/Notification/Class/Notification/Handler/Decorator/LogTest.php 
on line 37
.PHP Deprecated:  Creation of dynamic property 
Horde_Notification_Class_Notification_HandlerTest::$storage is 
deprecated in 
/tmp/autopkgtest-lxc.avv7f_5c/downtmp/build.Fyn/src/Horde_Notification-2.0.4/test/Horde/Notification/Class/Notification/HandlerTest.php 
on line 31
PHP Deprecated:  Creation of dynamic property 
Horde_Notification_Class_Notification_HandlerTest::$handler is 
deprecated in 
/tmp/autopkgtest-lxc.avv7f_5c/downtmp/build.Fyn/src/Horde_Notification-2.0.4/test/Horde/Notification/Class/Notification/HandlerTest.php 
on line 32
.PHP Deprecated:  Creation of dynamic property 
Horde_Notification_Class_Notification_HandlerTest::$storage is 
deprecated in 
/tmp/autopkgtest-lxc.avv7f_5c/downtmp/build.Fyn/src/Horde_Notification-2.0.4/test/Horde/Notification/Class/Notification/HandlerTest.php 
on line 31
PHP Deprecated:  Creation of dynamic property 
Horde_Notification_Class_Notification_HandlerTest::$handler is 
deprecated in 
/tmp/autopkgtest-lxc.avv7f_5c/downtmp/build.Fyn/src/Horde_Notification-2.0.4/test/Horde/Notification/Class/Notification/HandlerTest.php 
on line 32
.PHP Deprecated:  Creation of dynamic property 
Horde_Notification_Class_Notification_HandlerTest::$storage is 
deprecated in 
/tmp/autopkgtest-lxc.avv7f_5c/downtmp/build.Fyn/src/Horde_Notification-2.0.4/test/Horde/Notification/Class/Notification/HandlerTest.php 
on line 31
PHP Deprecated:  Creation of dynamic property 
Horde_Notification_Class_Notification_HandlerTest::$handler is 
deprecated in 
/tmp/autopkgtest-lxc.avv7f_5c/downtmp/build.Fyn/src/Horde_Notification-2.0.4/test/Horde/Notification/Class/Notification/HandlerTest.php 
on line 32
.PHP Deprecated:  Creation of dynamic property 
Horde_Notification_Class_Notification_HandlerTest::$storage is 
deprecated in 
/tmp/autopkgtest-lxc.avv7f_5c/downtmp/build.Fyn/src/Horde_Notification-2.0.4/test/Horde/Notification/Class/Notification/HandlerTest.php 
on line 31
PHP Deprecated:  Creation of dynamic property 
Horde_Notification_Class_Notification_HandlerTest::$handler is 
deprecated in 
/tmp/autopkgtest-lxc.avv7f_5c/downtmp/build.Fyn/src/Horde_Notification-2.0.4/test/Horde/Notification/Class/Notification/HandlerTest.php 
on line 32
.PHP Deprecated:  Creation of dynamic property 

Bug#1028940: php-horde-mime: (autopkgtest) needs update for php8.2: deprecation warnings on stderr

2023-01-14 Thread Paul Gevers

Source: php-horde-mime
Version: 2.11.2-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults

Dear maintainer(s),

We are in the transition of replacing php8.1 with php8.2 [0]. With a 
recent upload of php-defaults the autopkgtest of php-horde-mime fails in 
testing when that autopkgtest is run with the binary packages of 
php-defaults from unstable. It passes when run with only packages from 
testing. In tabular form:


   passfail
php-defaults   from testing93
php-horde-mime from testing2.11.2-1
all others from testingfrom testing

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

Currently this regression is blocking the migration of php-defaults to 
testing [1]. https://www.php.net/ChangeLog-8.php lists the changes since 
7.4 and may help to identify what needs to be updated.


The test itself passes, but the autopkgtest fails because of deprecation 
warnings on stderr. Output on stderr makes autopkgtest fail by default, 
unless `allow-stderr` is added to the set of restrictions. As a flood of 
deprecation warnings in server logs may be very unwanted, I'm not saying 
that adding the restriction to autopkgtest is the right answer to this 
issue, but because of the php transition, it needs to be resolved one 
way or the other.


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

Paul

[0] https://bugs.debian.org/1014460
[1] https://qa.debian.org/excuses.php?package=php-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-horde-mime/30356862/log.gz

.PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
.PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
.PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 

Bug#1028939: php-horde-mapi: (autopkgtest) needs update for php8.2: deprecation warnings on stderr

2023-01-14 Thread Paul Gevers

Source: php-horde-mapi
Version: 1.0.10-4
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults

Dear maintainer(s),

We are in the transition of replacing php8.1 with php8.2 [0]. With a 
recent upload of php-defaults the autopkgtest of php-horde-mapi fails in 
testing when that autopkgtest is run with the binary packages of 
php-defaults from unstable. It passes when run with only packages from 
testing. In tabular form:


   passfail
php-defaults   from testing93
php-horde-mapi from testing1.0.10-4
all others from testingfrom testing

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

Currently this regression is blocking the migration of php-defaults to 
testing [1]. https://www.php.net/ChangeLog-8.php lists the changes since 
7.4 and may help to identify what needs to be updated.


The test itself passes, but the autopkgtest fails because of deprecation 
warnings on stderr. Output on stderr makes autopkgtest fail by default, 
unless `allow-stderr` is added to the set of restrictions. As a flood of 
deprecation warnings in server logs may be very unwanted, I'm not saying 
that adding the restriction to autopkgtest is the right answer to this 
issue, but because of the php transition, it needs to be resolved one 
way or the other.


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

Paul

[0] https://bugs.debian.org/1014460
[1] https://qa.debian.org/excuses.php?package=php-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-horde-mapi/30356861/log.gz

PHPUnit 9.5.27 by Sebastian Bergmann and contributors.

Runtime:   PHP 8.2.1
Configuration: 
/tmp/autopkgtest-lxc.92kcj24m/downtmp/build.BRM/src/Horde_Mapi-1.0.10/test/Horde/Mapi/phpunit.xml


..PHP Deprecated:  Creation of dynamic property 
Horde_Mapi_TimezoneTest::$_oldTimezone is deprecated in 
/tmp/autopkgtest-lxc.92kcj24m/downtmp/build.BRM/src/Horde_Mapi-1.0.10/test/Horde/Mapi/TimezoneTest.php 
on line 111
.PHP Deprecated:  Creation of dynamic property 
Horde_Mapi_TimezoneTest::$_oldTimezone is deprecated in 
/tmp/autopkgtest-lxc.92kcj24m/downtmp/build.BRM/src/Horde_Mapi-1.0.10/test/Horde/Mapi/TimezoneTest.php 
on line 111
.PHP Deprecated:  Creation of dynamic property 
Horde_Mapi_TimezoneTest::$_oldTimezone is deprecated in 
/tmp/autopkgtest-lxc.92kcj24m/downtmp/build.BRM/src/Horde_Mapi-1.0.10/test/Horde/Mapi/TimezoneTest.php 
on line 111
.PHP Deprecated:  Creation of dynamic property 
Horde_Mapi_TimezoneTest::$_oldTimezone is deprecated in 
/tmp/autopkgtest-lxc.92kcj24m/downtmp/build.BRM/src/Horde_Mapi-1.0.10/test/Horde/Mapi/TimezoneTest.php 
on line 111

.  6 / 6 (100%)

Time: 00:00.041, Memory: 6.00 MB

OK (6 tests, 183 assertions)
autopkgtest [06:17:10]: test phpunit



OpenPGP_signature
Description: OpenPGP digital signature


Bug#1027467: dyssol: FTBFS without network access

2023-01-14 Thread Graham Inggs
Control: reopen -1

Hi Anton

It seems dyssol 1.1.0+ds1-2 still fails in the same way.

Regards
Graham



Bug#1028938: php-horde-mail: (autopkgtest) needs update for php8.2: deprecation warnings on stderr

2023-01-14 Thread Paul Gevers

Source: php-horde-mail
Version: 2.6.6-4
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults

Dear maintainer(s),

We are in the transition of replacing php8.1 with php8.2 [0]. With a 
recent upload of php-defaults the autopkgtest of php-horde-mail fails in 
testing when that autopkgtest is run with the binary packages of 
php-defaults from unstable. It passes when run with only packages from 
testing. In tabular form:


   passfail
php-defaults   from testing93
php-horde-mail from testing2.6.6-4
all others from testingfrom testing

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

Currently this regression is blocking the migration of php-defaults to 
testing [1]. https://www.php.net/ChangeLog-8.php lists the changes since 
7.4 and may help to identify what needs to be updated.


The test itself passes, but the autopkgtest fails because of deprecation 
warnings on stderr. Output on stderr makes autopkgtest fail by default, 
unless `allow-stderr` is added to the set of restrictions. As a flood of 
deprecation warnings in server logs may be very unwanted, I'm not saying 
that adding the restriction to autopkgtest is the right answer to this 
issue, but because of the php transition, it needs to be resolved one 
way or the other.


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

Paul

[0] https://bugs.debian.org/1014460
[1] https://qa.debian.org/excuses.php?package=php-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-horde-mail/30356860/log.gz

PHPUnit 9.5.27 by Sebastian Bergmann and contributors.

Runtime:   PHP 8.2.1
Configuration: 
/tmp/autopkgtest-lxc._yv33utl/downtmp/build.7dZ/src/Horde_Mail-2.6.6/test/Horde/Mail/phpunit.xml


...  63 / 
118 ( 53%)
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 124
..PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
..PHP Deprecated:  Function 
utf8_decode() is deprecated in /usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
.PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
...PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
.PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384

.. 118 / 118 (100%)

Time: 00:00.121, Memory: 12.00 MB

OK (118 tests, 244 assertions)
autopkgtest [06:17:10]: test phpunit



OpenPGP_signature
Description: OpenPGP digital signature


Bug#1028936: php-horde-itip: (autopkgtest) needs update for php8.2: deprecation warnings on stderr

2023-01-14 Thread Paul Gevers

Source: php-horde-itip
Version: 2.1.2-8
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults

Dear maintainer(s),

We are in the transition of replacing php8.1 with php8.2 [0]. With a 
recent upload of php-defaults the autopkgtest of php-horde-itip fails in 
testing when that autopkgtest is run with the binary packages of 
php-defaults from unstable. It passes when run with only packages from 
testing. In tabular form:


   passfail
php-defaults   from testing93
php-horde-itip from testing2.1.2-8
all others from testingfrom testing

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

Currently this regression is blocking the migration of php-defaults to 
testing [1]. https://www.php.net/ChangeLog-8.php lists the changes since 
7.4 and may help to identify what needs to be updated.


The test itself passes, but the autopkgtest fails because of deprecation 
warnings on stderr. Output on stderr makes autopkgtest fail by default, 
unless `allow-stderr` is added to the set of restrictions. As a flood of 
deprecation warnings in server logs may be very unwanted, I'm not saying 
that adding the restriction to autopkgtest is the right answer to this 
issue, but because of the php transition, it needs to be resolved one 
way or the other.


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

Paul

[0] https://bugs.debian.org/1014460
[1] https://qa.debian.org/excuses.php?package=php-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-horde-itip/30356858/log.gz

PHPUnit 9.5.27 by Sebastian Bergmann and contributors.

Runtime:   PHP 8.2.1
Configuration: 
/tmp/autopkgtest-lxc.2jy_k83_/downtmp/build.fqf/src/Horde_Itip-2.1.2/test/Horde/Itip/phpunit.xml

Warning:   Your XML configuration validates against a deprecated schema.
Suggestion:Migrate your XML configuration using 
"--migrate-configuration"!


PHP Deprecated:  Creation of dynamic property 
Horde_Itip_Integration_ItipTest::$_transport is deprecated in 
/tmp/autopkgtest-lxc.2jy_k83_/downtmp/build.fqf/src/Horde_Itip-2.1.2/test/Horde/Itip/Integration/ItipTest.php 
on line 46
.PHP Deprecated:  Creation of dynamic property 
Horde_Itip_Integration_ItipTest::$_transport is deprecated in 
/tmp/autopkgtest-lxc.2jy_k83_/downtmp/build.fqf/src/Horde_Itip-2.1.2/test/Horde/Itip/Integration/ItipTest.php 
on line 46
.PHP Deprecated:  Creation of dynamic property 
Horde_Itip_Integration_ItipTest::$_transport is deprecated in 
/tmp/autopkgtest-lxc.2jy_k83_/downtmp/build.fqf/src/Horde_Itip-2.1.2/test/Horde/Itip/Integration/ItipTest.php 
on line 46
.PHP Deprecated:  Creation of dynamic property 
Horde_Itip_Integration_ItipTest::$_transport is deprecated in 
/tmp/autopkgtest-lxc.2jy_k83_/downtmp/build.fqf/src/Horde_Itip-2.1.2/test/Horde/Itip/Integration/ItipTest.php 
on line 46
.PHP Deprecated:  Creation of dynamic property 
Horde_Itip_Integration_ItipTest::$_transport is deprecated in 
/tmp/autopkgtest-lxc.2jy_k83_/downtmp/build.fqf/src/Horde_Itip-2.1.2/test/Horde/Itip/Integration/ItipTest.php 
on line 46
.PHP Deprecated:  Creation of dynamic property 
Horde_Itip_Integration_ItipTest::$_transport is deprecated in 
/tmp/autopkgtest-lxc.2jy_k83_/downtmp/build.fqf/src/Horde_Itip-2.1.2/test/Horde/Itip/Integration/ItipTest.php 
on line 46
.PHP Deprecated:  Creation of dynamic property 
Horde_Itip_Integration_ItipTest::$_transport is deprecated in 
/tmp/autopkgtest-lxc.2jy_k83_/downtmp/build.fqf/src/Horde_Itip-2.1.2/test/Horde/Itip/Integration/ItipTest.php 
on line 46
.PHP Deprecated:  Creation of dynamic property 
Horde_Itip_Integration_ItipTest::$_transport is deprecated in 
/tmp/autopkgtest-lxc.2jy_k83_/downtmp/build.fqf/src/Horde_Itip-2.1.2/test/Horde/Itip/Integration/ItipTest.php 
on line 46
.PHP Deprecated:  Creation of dynamic property 
Horde_Itip_Integration_ItipTest::$_transport is deprecated in 
/tmp/autopkgtest-lxc.2jy_k83_/downtmp/build.fqf/src/Horde_Itip-2.1.2/test/Horde/Itip/Integration/ItipTest.php 
on line 46
.PHP Deprecated:  Creation of dynamic property 
Horde_Itip_Integration_ItipTest::$_transport is deprecated in 
/tmp/autopkgtest-lxc.2jy_k83_/downtmp/build.fqf/src/Horde_Itip-2.1.2/test/Horde/Itip/Integration/ItipTest.php 
on line 46
.PHP Deprecated:  Creation of dynamic property 
Horde_Itip_Integration_ItipTest::$_transport is deprecated in 
/tmp/autopkgtest-lxc.2jy_k83_/downtmp/build.fqf/src/Horde_Itip-2.1.2/test/Horde/Itip/Integration/ItipTest.php 
on line 46
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function 

Bug#1028937: php-horde-log: (autopkgtest) needs update for php8.2: deprecation warnings on stderr

2023-01-14 Thread Paul Gevers

Source: php-horde-log
Version: 2.3.0-8
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults

Dear maintainer(s),

We are in the transition of replacing php8.1 with php8.2 [0]. With a 
recent upload of php-defaults the autopkgtest of php-horde-log fails in 
testing when that autopkgtest is run with the binary packages of 
php-defaults from unstable. It passes when run with only packages from 
testing. In tabular form:


   passfail
php-defaults   from testing93
php-horde-log  from testing2.3.0-8
all others from testingfrom testing

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

Currently this regression is blocking the migration of php-defaults to 
testing [1]. https://www.php.net/ChangeLog-8.php lists the changes since 
7.4 and may help to identify what needs to be updated.


The test itself passes, but the autopkgtest fails because of deprecation 
warnings on stderr. Output on stderr makes autopkgtest fail by default, 
unless `allow-stderr` is added to the set of restrictions. As a flood of 
deprecation warnings in server logs may be very unwanted, I'm not saying 
that adding the restriction to autopkgtest is the right answer to this 
issue, but because of the php transition, it needs to be resolved one 
way or the other.


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

Paul

[0] https://bugs.debian.org/1014460
[1] https://qa.debian.org/excuses.php?package=php-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-horde-log/30356859/log.gz

PHPUnit 9.5.27 by Sebastian Bergmann and contributors.

Runtime:   PHP 8.2.1
Configuration: 
/tmp/autopkgtest-lxc.y0abtly7/downtmp/build.IaO/src/Horde_Log-2.3.0/test/Horde/Log/phpunit.xml


PHP Deprecated:  Creation of dynamic property 
Horde_Log_Filter_ChainingTest::$log is deprecated in 
/tmp/autopkgtest-lxc.y0abtly7/downtmp/build.IaO/src/Horde_Log-2.3.0/test/Horde/Log/Filter/ChainingTest.php 
on line 31
PHP Deprecated:  Creation of dynamic property 
Horde_Log_Filter_ChainingTest::$logger is deprecated in 
/tmp/autopkgtest-lxc.y0abtly7/downtmp/build.IaO/src/Horde_Log-2.3.0/test/Horde/Log/Filter/ChainingTest.php 
on line 32
.PHP Deprecated:  Creation of dynamic property 
Horde_Log_Filter_ChainingTest::$log is deprecated in 
/tmp/autopkgtest-lxc.y0abtly7/downtmp/build.IaO/src/Horde_Log-2.3.0/test/Horde/Log/Filter/ChainingTest.php 
on line 31
PHP Deprecated:  Creation of dynamic property 
Horde_Log_Filter_ChainingTest::$logger is deprecated in 
/tmp/autopkgtest-lxc.y0abtly7/downtmp/build.IaO/src/Horde_Log-2.3.0/test/Horde/Log/Filter/ChainingTest.php 
on line 32
PHP Deprecated:  Creation of dynamic property 
Horde_Log_Filter_ExactLevelTest::$filter is deprecated in 
/tmp/autopkgtest-lxc.y0abtly7/downtmp/build.IaO/src/Horde_Log-2.3.0/test/Horde/Log/Filter/ExactLevelTest.php 
on line 30
.PHP Deprecated:  Creation of dynamic property 
Horde_Log_Filter_ExactLevelTest::$filter is deprecated in 
/tmp/autopkgtest-lxc.y0abtly7/downtmp/build.IaO/src/Horde_Log-2.3.0/test/Horde/Log/Filter/ExactLevelTest.php 
on line 30
.PHP Deprecated:  Creation of dynamic property 
Horde_Log_Filter_ExactLevelTest::$filter is deprecated in 
/tmp/autopkgtest-lxc.y0abtly7/downtmp/build.IaO/src/Horde_Log-2.3.0/test/Horde/Log/Filter/ExactLevelTest.php 
on line 30
.PHP Deprecated:  Creation of dynamic property 
Horde_Log_Filter_LevelTest::$filter is deprecated in 
/tmp/autopkgtest-lxc.y0abtly7/downtmp/build.IaO/src/Horde_Log-2.3.0/test/Horde/Log/Filter/LevelTest.php 
on line 30
.PHP Deprecated:  Creation of dynamic property 
Horde_Log_Filter_LevelTest::$filter is deprecated in 
/tmp/autopkgtest-lxc.y0abtly7/downtmp/build.IaO/src/Horde_Log-2.3.0/test/Horde/Log/Filter/LevelTest.php 
on line 30
.PHP Deprecated:  Creation of dynamic property 
Horde_Log_Filter_LevelTest::$filter is deprecated in 
/tmp/autopkgtest-lxc.y0abtly7/downtmp/build.IaO/src/Horde_Log-2.3.0/test/Horde/Log/Filter/LevelTest.php 
on line 30
...PHP Deprecated:  Creation of dynamic property 
Horde_Log_Filter_SuppressTest::$filter is deprecated in 
/tmp/autopkgtest-lxc.y0abtly7/downtmp/build.IaO/src/Horde_Log-2.3.0/test/Horde/Log/Filter/SuppressTest.php 
on line 29
.PHP Deprecated:  Creation of dynamic property 
Horde_Log_Filter_SuppressTest::$filter is deprecated in 
/tmp/autopkgtest-lxc.y0abtly7/downtmp/build.IaO/src/Horde_Log-2.3.0/test/Horde/Log/Filter/SuppressTest.php 
on line 29
.PHP Deprecated:  Creation of dynamic property 
Horde_Log_Filter_SuppressTest::$filter is deprecated in 
/tmp/autopkgtest-lxc.y0abtly7/downtmp/build.IaO/src/Horde_Log-2.3.0/test/Horde/Log/Filter/SuppressTest.php 
on line 29
.PHP Deprecated:  Creation of dynamic property 
Horde_Log_Filter_SuppressTest::$filter is deprecated in 

Bug#1028935: php-horde-injector: (autopkgtest) needs update for php8.2: deprecation warnings on stderr

2023-01-14 Thread Paul Gevers

Source: php-horde-injector
Version: 2.0.5-11
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults

Dear maintainer(s),

We are in the transition of replacing php8.1 with php8.2 [0]. With a 
recent upload of php-defaults the autopkgtest of php-horde-injector 
fails in testing when that autopkgtest is run with the binary packages 
of php-defaults from unstable. It passes when run with only packages 
from testing. In tabular form:


   passfail
php-defaults   from testing93
php-horde-injector from testing2.0.5-11
all others from testingfrom testing

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

Currently this regression is blocking the migration of php-defaults to 
testing [1]. https://www.php.net/ChangeLog-8.php lists the changes since 
7.4 and may help to identify what needs to be updated.


The test itself passes, but the autopkgtest fails because of deprecation 
warnings on stderr. Output on stderr makes autopkgtest fail by default, 
unless `allow-stderr` is added to the set of restrictions. As a flood of 
deprecation warnings in server logs may be very unwanted, I'm not saying 
that adding the restriction to autopkgtest is the right answer to this 
issue, but because of the php transition, it needs to be resolved one 
way or the other.


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

Paul

[0] https://bugs.debian.org/1014460
[1] https://qa.debian.org/excuses.php?package=php-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-horde-injector/30356857/log.gz

PHPUnit 9.5.27 by Sebastian Bergmann and contributors.

Runtime:   PHP 8.2.1
Configuration: 
/tmp/autopkgtest-lxc.cmq4l_eg/downtmp/build.0gS/src/Horde_Injector-2.0.5/test/Horde/Injector/phpunit.xml

Warning:   Your XML configuration validates against a deprecated schema.
Suggestion:Migrate your XML configuration using 
"--migrate-configuration"!


..PHP Deprecated:  Creation of dynamic property 
ClosureInjectorMockTestAccess::$TEST_ID is deprecated in 
/tmp/autopkgtest-lxc.cmq4l_eg/downtmp/build.0gS/src/Horde_Injector-2.0.5/test/Horde/Injector/Binder/ClosureTest.php 
on line 31
PHP Deprecated:  Creation of dynamic property 
ClosureInjectorMockTestAccess::$TEST_ID is deprecated in 
/tmp/autopkgtest-lxc.cmq4l_eg/downtmp/build.0gS/src/Horde_Injector-2.0.5/test/Horde/Injector/Binder/ClosureTest.php 
on line 56
...PHP Deprecated:  Creation of dynamic property 
InjectorMockTestAccess::$TEST_ID is deprecated in 
/tmp/autopkgtest-lxc.cmq4l_eg/downtmp/build.0gS/src/Horde_Injector-2.0.5/test/Horde/Injector/Binder/FactoryTest.php 
on line 44
PHP Deprecated:  Creation of dynamic property 
InjectorMockTestAccess::$TEST_ID is deprecated in 
/tmp/autopkgtest-lxc.cmq4l_eg/downtmp/build.0gS/src/Horde_Injector-2.0.5/test/Horde/Injector/Binder/FactoryTest.php 
on line 98
PHP Deprecated:  Creation of dynamic property 
InjectorFactoryTestMockFactory::$_injector is deprecated in 
/tmp/autopkgtest-lxc.cmq4l_eg/downtmp/build.0gS/src/Horde_Injector-2.0.5/test/Horde/Injector/Binder/FactoryTest.php 
on line 90
.PHP Deprecated:  Creation of dynamic property 
InjectorMockTestAccess::$TEST_ID is deprecated in 
/tmp/autopkgtest-lxc.cmq4l_eg/downtmp/build.0gS/src/Horde_Injector-2.0.5/test/Horde/Injector/Binder/FactoryTest.php 
on line 64
PHP Deprecated:  Creation of dynamic property 
InjectorFactoryTestMockFactory::$_injector is deprecated in 
/tmp/autopkgtest-lxc.cmq4l_eg/downtmp/build.0gS/src/Horde_Injector-2.0.5/test/Horde/Injector/Binder/FactoryTest.php 
on line 90
..PHP Deprecated:  Creation of dynamic property 
Horde_Injector_Binder_ImplementationTest::$df is deprecated in 
/tmp/autopkgtest-lxc.cmq4l_eg/downtmp/build.0gS/src/Horde_Injector-2.0.5/test/Horde/Injector/Binder/ImplementationTest.php 
on line 6
.PHP Deprecated:  Creation of dynamic property 
Horde_Injector_Binder_ImplementationTest::$df is deprecated in 
/tmp/autopkgtest-lxc.cmq4l_eg/downtmp/build.0gS/src/Horde_Injector-2.0.5/test/Horde/Injector/Binder/ImplementationTest.php 
on line 6
.PHP Deprecated:  Creation of dynamic property 
Horde_Injector_Binder_ImplementationTest::$df is deprecated in 
/tmp/autopkgtest-lxc.cmq4l_eg/downtmp/build.0gS/src/Horde_Injector-2.0.5/test/Horde/Injector/Binder/ImplementationTest.php 
on line 6
.PHP Deprecated:  Creation of dynamic property 
Horde_Injector_Binder_ImplementationTest::$df is deprecated in 
/tmp/autopkgtest-lxc.cmq4l_eg/downtmp/build.0gS/src/Horde_Injector-2.0.5/test/Horde/Injector/Binder/ImplementationTest.php 
on line 6
.PHP Deprecated:  Creation of dynamic property 
Horde_Injector_Binder_ImplementationTest::$df is deprecated in 
/tmp/autopkgtest-lxc.cmq4l_eg/downtmp/build.0gS/src/Horde_Injector-2.0.5/test/Horde/Injector/Binder/ImplementationTest.php 
on line 6
.PHP Deprecated:  

Bug#1028934: php-horde-idna: (autopkgtest) needs update for php8.2: deprecation warnings on stderr

2023-01-14 Thread Paul Gevers

Source: php-horde-idna
Version: 1.1.2-5
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults

Dear maintainer(s),

We are in the transition of replacing php8.1 with php8.2 [0]. With a 
recent upload of php-defaults the autopkgtest of php-horde-idna fails in 
testing when that autopkgtest is run with the binary packages of 
php-defaults from unstable. It passes when run with only packages from 
testing. In tabular form:


   passfail
php-defaults   from testing93
php-horde-idna from testing1.1.2-5
all others from testingfrom testing

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

Currently this regression is blocking the migration of php-defaults to 
testing [1]. https://www.php.net/ChangeLog-8.php lists the changes since 
7.4 and may help to identify what needs to be updated.


The test itself passes, but the autopkgtest fails because of deprecation 
warnings on stderr. Output on stderr makes autopkgtest fail by default, 
unless `allow-stderr` is added to the set of restrictions. As a flood of 
deprecation warnings in server logs may be very unwanted, I'm not saying 
that adding the restriction to autopkgtest is the right answer to this 
issue, but because of the php transition, it needs to be resolved one 
way or the other.


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

Paul

[0] https://bugs.debian.org/1014460
[1] https://qa.debian.org/excuses.php?package=php-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-horde-idna/30356855/log.gz

PHPUnit 9.5.27 by Sebastian Bergmann and contributors.

Runtime:   PHP 8.2.1
Configuration: 
/tmp/autopkgtest-lxc.fz5q8md6/downtmp/build.4Jz/src/Horde_Idna-1.1.2/test/Horde/Idna/phpunit.xml


PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
.PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
.PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
.PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
.PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
.PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
.PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
.PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 

Bug#1028933: php-horde-http: (autopkgtest) needs update for php8.2: deprecation warnings on stderr

2023-01-14 Thread Paul Gevers

Source: php-horde-http
Version: 2.1.7-10
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults

Dear maintainer(s),

We are in the transition of replacing php8.1 with php8.2 [0]. With a 
recent upload of php-defaults the autopkgtest of php-horde-http fails in 
testing when that autopkgtest is run with the binary packages of 
php-defaults from unstable. It passes when run with only packages from 
testing. In tabular form:


   passfail
php-defaults   from testing93
php-horde-http from testing2.1.7-10
all others from testingfrom testing

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

Currently this regression is blocking the migration of php-defaults to 
testing [1]. https://www.php.net/ChangeLog-8.php lists the changes since 
7.4 and may help to identify what needs to be updated.


The test itself passes, but the autopkgtest fails because of deprecation 
warnings on stderr. Output on stderr makes autopkgtest fail by default, 
unless `allow-stderr` is added to the set of restrictions. As a flood of 
deprecation warnings in server logs may be very unwanted, I'm not saying 
that adding the restriction to autopkgtest is the right answer to this 
issue, but because of the php transition, it needs to be resolved one 
way or the other.


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

Paul

[0] https://bugs.debian.org/1014460
[1] https://qa.debian.org/excuses.php?package=php-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-horde-http/30356854/log.gz

PHPUnit 9.5.27 by Sebastian Bergmann and contributors.

Runtime:   PHP 8.2.1
Configuration: 
/tmp/autopkgtest-lxc.njn0xa_3/downtmp/build.PCe/src/Horde_Http-2.1.7/test/Horde/Http/phpunit.xml

Warning:   Your XML configuration validates against a deprecated schema.
Suggestion:Migrate your XML configuration using 
"--migrate-configuration"!


...PHP Deprecated:  Creation of dynamic property 
Horde_Http_Response_Mock::$_stream is deprecated in 
/tmp/autopkgtest-lxc.njn0xa_3/downtmp/build.PCe/src/Horde_Http-2.1.7/lib/Horde/Http/Response/Mock.php 
on line 25
.PHP Deprecated:  Creation of dynamic property 
Horde_Http_Response_Mock::$_stream is deprecated in 
/tmp/autopkgtest-lxc.njn0xa_3/downtmp/build.PCe/src/Horde_Http-2.1.7/lib/Horde/Http/Response/Mock.php 
on line 25
.PHP Deprecated:  Creation of dynamic property 
Horde_Http_Response_Mock::$_stream is deprecated in 
/tmp/autopkgtest-lxc.njn0xa_3/downtmp/build.PCe/src/Horde_Http-2.1.7/lib/Horde/Http/Response/Mock.php 
on line 25
.PHP Deprecated:  Creation of dynamic property 
Horde_Http_Response_Mock::$_stream is deprecated in 
/tmp/autopkgtest-lxc.njn0xa_3/downtmp/build.PCe/src/Horde_Http-2.1.7/lib/Horde/Http/Response/Mock.php 
on line 25
.PHP Deprecated:  Creation of dynamic property 
Horde_Http_Response_Mock::$_stream is deprecated in 
/tmp/autopkgtest-lxc.njn0xa_3/downtmp/build.PCe/src/Horde_Http-2.1.7/lib/Horde/Http/Response/Mock.php 
on line 25
.PHP Deprecated:  Creation of dynamic property 
Horde_Http_Response_Mock::$_stream is deprecated in 
/tmp/autopkgtest-lxc.njn0xa_3/downtmp/build.PCe/src/Horde_Http-2.1.7/lib/Horde/Http/Response/Mock.php 
on line 25
PHP Deprecated:  Creation of dynamic property 
Horde_Http_Response_Mock::$_stream is deprecated in 
/tmp/autopkgtest-lxc.njn0xa_3/downtmp/build.PCe/src/Horde_Http-2.1.7/lib/Horde/Http/Response/Mock.php 
on line 25
.PHP Deprecated:  Creation of dynamic property 
Horde_Http_Response_Mock::$_stream is deprecated in 
/tmp/autopkgtest-lxc.njn0xa_3/downtmp/build.PCe/src/Horde_Http-2.1.7/lib/Horde/Http/Response/Mock.php 
on line 25
PHP Deprecated:  Creation of dynamic property 
Horde_Http_Response_Mock::$_stream is deprecated in 
/tmp/autopkgtest-lxc.njn0xa_3/downtmp/build.PCe/src/Horde_Http-2.1.7/lib/Horde/Http/Response/Mock.php 
on line 25
PHP Deprecated:  Creation of dynamic property 
Horde_Http_Response_Mock::$_stream is deprecated in 
/tmp/autopkgtest-lxc.njn0xa_3/downtmp/build.PCe/src/Horde_Http-2.1.7/lib/Horde/Http/Response/Mock.php 
on line 25
PHP Deprecated:  Creation of dynamic property 
Horde_Http_Response_Mock::$_stream is deprecated in 
/tmp/autopkgtest-lxc.njn0xa_3/downtmp/build.PCe/src/Horde_Http-2.1.7/lib/Horde/Http/Response/Mock.php 
on line 25

..S  32 / 32 (100%)

Time: 00:08.026, Memory: 6.00 MB

There were 5 skipped tests:

1) Horde_Http_PeclhttpTest::testRequest
Missing PHP extension "http" or wrong version!

/tmp/autopkgtest-lxc.njn0xa_3/downtmp/build.PCe/src/Horde_Http-2.1.7/test/Horde/Http/PeclhttpTest.php:24

2) Horde_Http_PeclhttpTest::testThrowsOnBadUri
Missing PHP extension "http" or wrong version!

/tmp/autopkgtest-lxc.njn0xa_3/downtmp/build.PCe/src/Horde_Http-2.1.7/test/Horde/Http/PeclhttpTest.php:24

Bug#1028932: php-horde-hashtable: (autopkgtest) needs update for php8.2: deprecation warnings on stderr

2023-01-14 Thread Paul Gevers

Source: php-horde-hashtable
Version: 1.2.6-11
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults

Dear maintainer(s),

We are in the transition of replacing php8.1 with php8.2 [0]. With a 
recent upload of php-defaults the autopkgtest of php-horde-hashtable 
fails in testing when that autopkgtest is run with the binary packages 
of php-defaults from unstable. It passes when run with only packages 
from testing. In tabular form:


   passfail
php-defaults   from testing93
php-horde-hashtablefrom testing1.2.6-11
all others from testingfrom testing

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

Currently this regression is blocking the migration of php-defaults to 
testing [1]. https://www.php.net/ChangeLog-8.php lists the changes since 
7.4 and may help to identify what needs to be updated.


The test itself passes, but the autopkgtest fails because of deprecation 
warnings on stderr. Output on stderr makes autopkgtest fail by default, 
unless `allow-stderr` is added to the set of restrictions. As a flood of 
deprecation warnings in server logs may be very unwanted, I'm not saying 
that adding the restriction to autopkgtest is the right answer to this 
issue, but because of the php transition, it needs to be resolved one 
way or the other.


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

Paul

[0] https://bugs.debian.org/1014460
[1] https://qa.debian.org/excuses.php?package=php-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-horde-hashtable/30356853/log.gz

PHPUnit 9.5.27 by Sebastian Bergmann and contributors.

Runtime:   PHP 8.2.1
Configuration: 
/tmp/autopkgtest-lxc.qvzzas_l/downtmp/build.eJV/src/Horde_HashTable-1.2.6/test/Horde/HashTable/phpunit.xml


PHP Deprecated:  Creation of dynamic property Memcache::$connection is 
deprecated in /usr/share/php/Horde/Memcache.php on line 176
PHP Deprecated:  Creation of dynamic property 
Memcache::$_failureCallback is deprecated in 
/usr/share/php/Horde/Memcache.php on line 176
  12 / 
12 (100%)


Time: 00:06.017, Memory: 6.00 MB

OK (12 tests, 54 assertions)
autopkgtest [06:16:25]: test phpunit



OpenPGP_signature
Description: OpenPGP digital signature


Bug#1028930: php-horde-crypt: (autopkgtest) needs update for php8.2: deprecation warnings on stderr

2023-01-14 Thread Paul Gevers

Source: php-horde-crypt
Version: 2.7.12-7
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults

Dear maintainer(s),

We are in the transition of replacing php8.1 with php8.2 [0]. With a 
recent upload of php-defaults the autopkgtest of php-horde-crypt fails 
in testing when that autopkgtest is run with the binary packages of 
php-defaults from unstable. It passes when run with only packages from 
testing. In tabular form:


   passfail
php-defaults   from testing93
php-horde-cryptfrom testing2.7.12-7
all others from testingfrom testing

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

Currently this regression is blocking the migration of php-defaults to 
testing [1]. https://www.php.net/ChangeLog-8.php lists the changes since 
7.4 and may help to identify what needs to be updated.


The test itself passes, but the autopkgtest fails because of deprecation 
warnings on stderr. Output on stderr makes autopkgtest fail by default, 
unless `allow-stderr` is added to the set of restrictions. As a flood of 
deprecation warnings in server logs may be very unwanted, I'm not saying 
that adding the restriction to autopkgtest is the right answer to this 
issue, but because of the php transition, it needs to be resolved one 
way or the other.


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

Paul

[0] https://bugs.debian.org/1014460
[1] https://qa.debian.org/excuses.php?package=php-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-horde-crypt/30356851/log.gz

PHPUnit 9.5.27 by Sebastian Bergmann and contributors.

Runtime:   PHP 8.2.1
Configuration: 
/tmp/autopkgtest-lxc.waqynnpp/downtmp/build.Xxl/src/Horde_Crypt-2.7.12/test/Horde/Crypt/phpunit.xml


PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
.PHP Deprecated:  Function utf8_encode() is deprecated in 
/usr/share/php/Horde/String.php on line 119
.PHP Deprecated:  Function utf8_encode() is deprecated in 
/usr/share/php/Horde/String.php on line 119
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 

Bug#1028929: php-horde-core: (autopkgtest) needs update for php8.2: deprecation warnings on stderr

2023-01-14 Thread Paul Gevers

Source: php-horde-core
Version: 2.31.16+debian0-4
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults

Dear maintainer(s),

We are in the transition of replacing php8.1 with php8.2 [0]. With a 
recent upload of php-defaults the autopkgtest of php-horde-core fails in 
testing when that autopkgtest is run with the binary packages of 
php-defaults from unstable. It passes when run with only packages from 
testing. In tabular form:


   passfail
php-defaults   from testing93
php-horde-core from testing2.31.16+debian0-4
all others from testingfrom testing

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

Currently this regression is blocking the migration of php-defaults to 
testing [1]. https://www.php.net/ChangeLog-8.php lists the changes since 
7.4 and may help to identify what needs to be updated.


The test itself passes, but the autopkgtest fails because of deprecation 
warnings on stderr. Output on stderr makes autopkgtest fail by default, 
unless `allow-stderr` is added to the set of restrictions. As a flood of 
deprecation warnings in server logs may be very unwanted, I'm not saying 
that adding the restriction to autopkgtest is the right answer to this 
issue, but because of the php transition, it needs to be resolved one 
way or the other.


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

Paul

[0] https://bugs.debian.org/1014460
[1] https://qa.debian.org/excuses.php?package=php-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-horde-core/30356850/log.gz


.PHP Deprecated:  Creation of 
dynamic property Horde_Test_Stub_Registry_Loadconfig::$config is 
deprecated in 
/tmp/autopkgtest-lxc.jxxr98u7/downtmp/build.APg/src/Horde_Core-2.31.16/test/Horde/Core/NlsconfigTest.php 
on line 32
PHP Deprecated:  Creation of dynamic property 
Horde_Test_Stub_Registry::$configObjects is deprecated in 
/usr/share/php/Horde/Test/Stub/Registry.php on line 160
.PHP Deprecated:  Creation of dynamic property 
Horde_Test_Stub_Registry_Loadconfig::$config is deprecated in 
/tmp/autopkgtest-lxc.jxxr98u7/downtmp/build.APg/src/Horde_Core-2.31.16/test/Horde/Core/NlsconfigTest.php 
on line 32
PHP Deprecated:  Creation of dynamic property 
Horde_Test_Stub_Registry::$configObjects is deprecated in 
/usr/share/php/Horde/Test/Stub/Registry.php on line 160
.PHP Deprecated:  Creation of dynamic property 
Horde_Test_Stub_Registry_Loadconfig::$config is deprecated in 
/tmp/autopkgtest-lxc.jxxr98u7/downtmp/build.APg/src/Horde_Core-2.31.16/test/Horde/Core/NlsconfigTest.php 
on line 32
PHP Deprecated:  Creation of dynamic property 
Horde_Test_Stub_Registry::$configObjects is deprecated in 
/usr/share/php/Horde/Test/Stub/Registry.php on line 160
.PHP Deprecated:  Creation of dynamic property 
Horde_Test_Stub_Registry_Loadconfig::$config is deprecated in 
/tmp/autopkgtest-lxc.jxxr98u7/downtmp/build.APg/src/Horde_Core-2.31.16/test/Horde/Core/NlsconfigTest.php 
on line 32
PHP Deprecated:  Creation of dynamic property 
Horde_Test_Stub_Registry::$configObjects is deprecated in 
/usr/share/php/Horde/Test/Stub/Registry.php on line 160

. 53 / 53 (100%)

Time: 00:00.012, Memory: 6.00 MB

There were 36 incomplete tests:

1) Horde_Core_Factory_KolabServerTest::testMethodGetserverReturnsServer
Needs some love

/tmp/autopkgtest-lxc.jxxr98u7/downtmp/build.APg/src/Horde_Core-2.31.16/test/Horde/Core/Factory/KolabServerTest.php:30
/usr/bin/phpunit:73

2) 
Horde_Core_Factory_KolabServerTest::testMethodGetconfigurationReturnsArrayConfiguration

Needs some love

/tmp/autopkgtest-lxc.jxxr98u7/downtmp/build.APg/src/Horde_Core-2.31.16/test/Horde/Core/Factory/KolabServerTest.php:30
/usr/bin/phpunit:73

3) 
Horde_Core_Factory_KolabServerTest::testMethodGetconnectionHasResultConnection

Needs some love

/tmp/autopkgtest-lxc.jxxr98u7/downtmp/build.APg/src/Horde_Core-2.31.16/test/Horde/Core/Factory/KolabServerTest.php:30
/usr/bin/phpunit:73

4) 
Horde_Core_Factory_KolabServerTest::testMethodConstructHasResultMockConnectionIfConfiguredThatWay

Needs some love

/tmp/autopkgtest-lxc.jxxr98u7/downtmp/build.APg/src/Horde_Core-2.31.16/test/Horde/Core/Factory/KolabServerTest.php:30
/usr/bin/phpunit:73

5) 
Horde_Core_Factory_KolabServerTest::testMethodGetconnectionHasResultMockConnectionWithDataIfConfiguredThatWay

Needs some love

/tmp/autopkgtest-lxc.jxxr98u7/downtmp/build.APg/src/Horde_Core-2.31.16/test/Horde/Core/Factory/KolabServerTest.php:30
/usr/bin/phpunit:73

6) 
Horde_Core_Factory_KolabServerTest::testMethodConstructHasResultSimpleConnectionByDefault

Needs some love

/tmp/autopkgtest-lxc.jxxr98u7/downtmp/build.APg/src/Horde_Core-2.31.16/test/Horde/Core/Factory/KolabServerTest.php:30
/usr/bin/phpunit:73

7) 

Bug#1028928: php-horde-compress: (autopkgtest) needs update for php8.2: deprecation warnings on stderr

2023-01-14 Thread Paul Gevers

Source: php-horde-compress
Version: 2.2.4-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults

Dear maintainer(s),

We are in the transition of replacing php8.1 with php8.2 [0]. With a 
recent upload of php-defaults the autopkgtest of php-horde-compress 
fails in testing when that autopkgtest is run with the binary packages 
of php-defaults from unstable. It passes when run with only packages 
from testing. In tabular form:


   passfail
php-defaults   from testing93
php-horde-compress from testing2.2.4-2
all others from testingfrom testing

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

Currently this regression is blocking the migration of php-defaults to 
testing [1]. https://www.php.net/ChangeLog-8.php lists the changes since 
7.4 and may help to identify what needs to be updated.


The test itself passes, but the autopkgtest fails because of deprecation 
warnings on stderr. Output on stderr makes autopkgtest fail by default, 
unless `allow-stderr` is added to the set of restrictions. As a flood of 
deprecation warnings in server logs may be very unwanted, I'm not saying 
that adding the restriction to autopkgtest is the right answer to this 
issue, but because of the php transition, it needs to be resolved one 
way or the other.


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

Paul

[0] https://bugs.debian.org/1014460
[1] https://qa.debian.org/excuses.php?package=php-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-horde-compress/30356849/log.gz

PHPUnit 9.5.27 by Sebastian Bergmann and contributors.

Runtime:   PHP 8.2.1
Configuration: 
/tmp/autopkgtest-lxc.4k_rbkus/downtmp/build.qPh/src/Horde_Compress-2.2.4/test/Horde/Compress/phpunit.xml


...PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
PHP Deprecated:  Function utf8_decode() is deprecated in 
/usr/share/php/Horde/String.php on line 384
.PHP Deprecated:  Creation of dynamic property 
Horde_Compress_Tnef_VTodo::$_organizer is deprecated in 
/tmp/autopkgtest-lxc.4k_rbkus/downtmp/build.qPh/src/Horde_Compress-2.2.4/lib/Horde/Compress/Tnef/VTodo.php 
on line 370
PHP Deprecated:  Function utf8_decode() is 

Bug#1028927: php-horde-autoloader: (autopkgtest) needs update for php8.2: deprecation warnings on stderr

2023-01-14 Thread Paul Gevers

Source: php-horde-autoloader
Version: 2.1.2-10
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults

Dear maintainer(s),

We are in the transition of replacing php8.1 with php8.2 [0]. With a 
recent upload of php-defaults the autopkgtest of php-horde-autoloader 
fails in testing when that autopkgtest is run with the binary packages 
of php-defaults from unstable. It passes when run with only packages 
from testing. In tabular form:


   passfail
php-defaults   from testing93
php-horde-autoloader   from testing2.1.2-10
all others from testingfrom testing

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

Currently this regression is blocking the migration of php-defaults to 
testing [1]. https://www.php.net/ChangeLog-8.php lists the changes since 
7.4 and may help to identify what needs to be updated.


The test itself passes, but the autopkgtest fails because of deprecation 
warnings on stderr. Output on stderr makes autopkgtest fail by default, 
unless `allow-stderr` is added to the set of restrictions. As a flood of 
deprecation warnings in server logs may be very unwanted, I'm not saying 
that adding the restriction to autopkgtest is the right answer to this 
issue, but because of the php transition, it needs to be resolved one 
way or the other.


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

Paul

[0] https://bugs.debian.org/1014460
[1] https://qa.debian.org/excuses.php?package=php-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-horde-autoloader/30356848/log.gz

PHPUnit 9.5.27 by Sebastian Bergmann and contributors.

Runtime:   PHP 8.2.1
Configuration: 
/tmp/autopkgtest-lxc.nm1ct_ru/downtmp/build.N26/src/Horde_Autoloader-2.1.2/test/Horde/Autoloader/phpunit.xml


PHP Deprecated:  Creation of dynamic property 
Horde_Autoloader_ClassPathMapper_Application::$_classMatchRegex is 
deprecated in 
/tmp/autopkgtest-lxc.nm1ct_ru/downtmp/build.N26/src/Horde_Autoloader-2.1.2/lib/Horde/Autoloader/ClassPathMapper/Application.php 
on line 65
.PHP Deprecated:  Creation of dynamic property 
Horde_Autoloader_ClassPathMapper_Application::$_classMatchRegex is 
deprecated in 
/tmp/autopkgtest-lxc.nm1ct_ru/downtmp/build.N26/src/Horde_Autoloader-2.1.2/lib/Horde/Autoloader/ClassPathMapper/Application.php 
on line 65
.PHP Deprecated:  Creation of dynamic property 
Horde_Autoloader_ClassPathMapper_Application::$_classMatchRegex is 
deprecated in 
/tmp/autopkgtest-lxc.nm1ct_ru/downtmp/build.N26/src/Horde_Autoloader-2.1.2/lib/Horde/Autoloader/ClassPathMapper/Application.php 
on line 65
.PHP Deprecated:  Creation of dynamic property 
Horde_Autoloader_ClassPathMapper_Application::$_classMatchRegex is 
deprecated in 
/tmp/autopkgtest-lxc.nm1ct_ru/downtmp/build.N26/src/Horde_Autoloader-2.1.2/lib/Horde/Autoloader/ClassPathMapper/Application.php 
on line 65
.PHP Deprecated:  Creation of dynamic property 
Horde_Autoloader_ClassPathMapper_Application::$_classMatchRegex is 
deprecated in 
/tmp/autopkgtest-lxc.nm1ct_ru/downtmp/build.N26/src/Horde_Autoloader-2.1.2/lib/Horde/Autoloader/ClassPathMapper/Application.php 
on line 65
.PHP Deprecated:  Creation of dynamic property 
Horde_Autoloader_ClassPathMapper_Application::$_classMatchRegex is 
deprecated in 
/tmp/autopkgtest-lxc.nm1ct_ru/downtmp/build.N26/src/Horde_Autoloader-2.1.2/lib/Horde/Autoloader/ClassPathMapper/Application.php 
on line 65
.PHP Deprecated:  Creation of dynamic property 
Horde_Autoloader_ClassPathMapper_Application::$_classMatchRegex is 
deprecated in 
/tmp/autopkgtest-lxc.nm1ct_ru/downtmp/build.N26/src/Horde_Autoloader-2.1.2/lib/Horde/Autoloader/ClassPathMapper/Application.php 
on line 65
.PHP Deprecated:  Creation of dynamic property 
Horde_Autoloader_ClassPathMapper_Application::$_classMatchRegex is 
deprecated in 
/tmp/autopkgtest-lxc.nm1ct_ru/downtmp/build.N26/src/Horde_Autoloader-2.1.2/lib/Horde/Autoloader/ClassPathMapper/Application.php 
on line 65
.PHP Deprecated:  Creation of dynamic property 
Horde_Autoloader_ClassPathMapper_Application::$_classMatchRegex is 
deprecated in 
/tmp/autopkgtest-lxc.nm1ct_ru/downtmp/build.N26/src/Horde_Autoloader-2.1.2/lib/Horde/Autoloader/ClassPathMapper/Application.php 
on line 65

. 33 / 33 (100%)

Time: 00:00.008, Memory: 6.00 MB

OK (33 tests, 39 assertions)
autopkgtest [06:16:04]: test phpunit



OpenPGP_signature
Description: OpenPGP digital signature


Bug#1028926: php-horde-auth: (autopkgtest) needs update for php8.2: deprecation warnings on stderr

2023-01-14 Thread Paul Gevers

Source: php-horde-auth
Version: 2.2.2-9
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults

Dear maintainer(s),

We are in the transition of replacing php8.1 with php8.2 [0]. With a 
recent upload of php-defaults the autopkgtest of php-horde-auth fails in 
testing when that autopkgtest is run with the binary packages of 
php-defaults from unstable. It passes when run with only packages from 
testing. In tabular form:


   passfail
php-defaults   from testing93
php-horde-auth from testing2.2.2-9
all others from testingfrom testing

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

Currently this regression is blocking the migration of php-defaults to 
testing [1]. https://www.php.net/ChangeLog-8.php lists the changes since 
7.4 and may help to identify what needs to be updated.


The test itself passes, but the autopkgtest fails because of deprecation 
warnings on stderr. Output on stderr makes autopkgtest fail by default, 
unless `allow-stderr` is added to the set of restrictions. As a flood of 
deprecation warnings in server logs may be very unwanted, I'm not saying 
that adding the restriction to autopkgtest is the right answer to this 
issue, but because of the php transition, it needs to be resolved one 
way or the other.


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

Paul

[0] https://bugs.debian.org/1014460
[1] https://qa.debian.org/excuses.php?package=php-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-horde-auth/30356847/log.gz

PHP Deprecated:  Creation of dynamic property 
Horde_Db_Migration_Migrator::$_inflector is deprecated in 
/usr/share/php/Horde/Db/Migration/Migrator.php on line 76
PHP Deprecated:  Callables of the form ["Horde_Db_Adapter_Pdo_Sqlite", 
"parent::execute"] are deprecated in 
/usr/share/php/Horde/Db/Adapter/Pdo/Sqlite.php on line 187
PHP Deprecated:  Callables of the form ["Horde_Db_Adapter_Pdo_Sqlite", 
"parent::execute"] are deprecated in 
/usr/share/php/Horde/Db/Adapter/Pdo/Sqlite.php on line 187
PHP Deprecated:  Callables of the form ["Horde_Db_Adapter_Pdo_Sqlite", 
"parent::execute"] are deprecated in 
/usr/share/php/Horde/Db/Adapter/Pdo/Sqlite.php on line 187
PHP Deprecated:  Callables of the form ["Horde_Db_Adapter_Pdo_Sqlite", 
"parent::execute"] are deprecated in 
/usr/share/php/Horde/Db/Adapter/Pdo/Sqlite.php on line 187
PHP Deprecated:  Callables of the form ["Horde_Db_Adapter_Pdo_Sqlite", 
"parent::execute"] are deprecated in 
/usr/share/php/Horde/Db/Adapter/Pdo/Sqlite.php on line 187
PHP Deprecated:  Callables of the form ["Horde_Db_Adapter_Pdo_Sqlite", 
"parent::execute"] are deprecated in 
/usr/share/php/Horde/Db/Adapter/Pdo/Sqlite.php on line 187
PHP Deprecated:  Callables of the form ["Horde_Db_Adapter_Pdo_Sqlite", 
"parent::execute"] are deprecated in 
/usr/share/php/Horde/Db/Adapter/Pdo/Sqlite.php on line 187
PHP Deprecated:  Callables of the form ["Horde_Db_Adapter_Pdo_Sqlite", 
"parent::execute"] are deprecated in 
/usr/share/php/Horde/Db/Adapter/Pdo/Sqlite.php on line 187
PHP Deprecated:  Callables of the form ["Horde_Db_Adapter_Pdo_Sqlite", 
"parent::execute"] are deprecated in 
/usr/share/php/Horde/Db/Adapter/Pdo/Sqlite.php on line 187
PHP Deprecated:  Callables of the form ["Horde_Db_Adapter_Pdo_Sqlite", 
"parent::execute"] are deprecated in 
/usr/share/php/Horde/Db/Adapter/Pdo/Sqlite.php on line 187
PHP Deprecated:  Callables of the form ["Horde_Db_Adapter_Pdo_Sqlite", 
"parent::execute"] are deprecated in 
/usr/share/php/Horde/Db/Adapter/Pdo/Sqlite.php on line 187
PHP Deprecated:  Callables of the form ["Horde_Db_Adapter_Pdo_Sqlite", 
"parent::execute"] are deprecated in 
/usr/share/php/Horde/Db/Adapter/Pdo/Sqlite.php on line 187
.PHP Deprecated:  Callables of the form ["Horde_Db_Adapter_Pdo_Sqlite", 
"parent::execute"] are deprecated in 
/usr/share/php/Horde/Db/Adapter/Pdo/Sqlite.php on line 187

. 65 / 69 ( 94%)
PHP Deprecated:  Callables of the form ["Horde_Db_Adapter_Pdo_Sqlite", 
"parent::execute"] are deprecated in 
/usr/share/php/Horde/Db/Adapter/Pdo/Sqlite.php on line 187
..PHP Deprecated:  Callables of the form ["Horde_Db_Adapter_Pdo_Sqlite", 
"parent::execute"] are deprecated in 
/usr/share/php/Horde/Db/Adapter/Pdo/Sqlite.php on line 187
.PHP Deprecated:  Callables of the form ["Horde_Db_Adapter_Pdo_Sqlite", 
"parent::execute"] are deprecated in 
/usr/share/php/Horde/Db/Adapter/Pdo/Sqlite.php on line 187
.  69 / 69 
(100%)PHP Deprecated:  Callables of the form 
["Horde_Db_Adapter_Pdo_Sqlite", "parent::execute"] are deprecated in 
/usr/share/php/Horde/Db/Adapter/Pdo/Sqlite.php on line 187
PHP Deprecated:  Callables of the form ["Horde_Db_Adapter_Pdo_Sqlite", 
"parent::execute"] are deprecated in 

Bug#1028925: php-horde-argv: (autopkgtest) needs update for php8.2: deprecation warnings on stderr

2023-01-14 Thread Paul Gevers

Source: php-horde-argv
Version: 2.1.0-8
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults

Dear maintainer(s),

We are in the transition of replacing php8.1 with php8.2 [0]. With a 
recent upload of php-defaults the autopkgtest of php-horde-argv fails in 
testing when that autopkgtest is run with the binary packages of 
php-defaults from unstable. It passes when run with only packages from 
testing. In tabular form:


   passfail
php-defaults   from testing93
php-horde-argv from testing2.1.0-8
all others from testingfrom testing

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

Currently this regression is blocking the migration of php-defaults to 
testing [1]. https://www.php.net/ChangeLog-8.php lists the changes since 
7.4 and may help to identify what needs to be updated.


The test itself passes, but the autopkgtest fails because of deprecation 
warnings on stderr. Output on stderr makes autopkgtest fail by default, 
unless `allow-stderr` is added to the set of restrictions. As a flood of 
deprecation warnings in server logs may be very unwanted, I'm not saying 
that adding the restriction to autopkgtest is the right answer to this 
issue, but because of the php8.2 transition, it needs to be resolved one 
way or the other.


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

Paul

[0] https://bugs.debian.org/1014460
[1] https://qa.debian.org/excuses.php?package=php-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-horde-argv/30356846/log.gz

Horde_Argv_InterceptingParser::$largs is deprecated in 
/tmp/autopkgtest-lxc.edkewlmf/downtmp/build.aqv/src/Horde_Argv-2.1.0/lib/Horde/Argv/Parser.php 
on line 169
PHP Deprecated:  Creation of dynamic property 
Horde_Argv_InterceptingParser::$values is deprecated in 
/tmp/autopkgtest-lxc.edkewlmf/downtmp/build.aqv/src/Horde_Argv-2.1.0/lib/Horde/Argv/Parser.php 
on line 170
PHP Deprecated:  Creation of dynamic property 
Horde_Argv_VersionTest::$parser is deprecated in 
/tmp/autopkgtest-lxc.edkewlmf/downtmp/build.aqv/src/Horde_Argv-2.1.0/test/Horde/Argv/VersionTest.php 
on line 47
PHP Deprecated:  Creation of dynamic property 
Horde_Argv_BadOptionException::$optionId is deprecated in 
/tmp/autopkgtest-lxc.edkewlmf/downtmp/build.aqv/src/Horde_Argv-2.1.0/lib/Horde/Argv/OptionException.php 
on line 32
PHP Deprecated:  Creation of dynamic property 
Horde_Argv_InterceptedException::$error_message is deprecated in 
/tmp/autopkgtest-lxc.edkewlmf/downtmp/build.aqv/src/Horde_Argv-2.1.0/test/Horde/Argv/InterceptedException.php 
on line 15
PHP Deprecated:  Creation of dynamic property 
Horde_Argv_InterceptedException::$exit_status is deprecated in 
/tmp/autopkgtest-lxc.edkewlmf/downtmp/build.aqv/src/Horde_Argv-2.1.0/test/Horde/Argv/InterceptedException.php 
on line 16
PHP Deprecated:  Creation of dynamic property 
Horde_Argv_InterceptedException::$exit_message is deprecated in 
/tmp/autopkgtest-lxc.edkewlmf/downtmp/build.aqv/src/Horde_Argv-2.1.0/test/Horde/Argv/InterceptedException.php 
on line 17

.   143 / 143 (100%)

Time: 00:00.140, Memory: 10.00 MB

OK (143 tests, 310 assertions)
autopkgtest [06:16:04]: test phpunit



OpenPGP_signature
Description: OpenPGP digital signature


Bug#1028275: perl: Return value of system()

2023-01-14 Thread David Christensen

Debian bug 1028275:

Below please find a more sophisticated test script for Perl system() 
using one argument and sample runs on Debian and FreeBSD.



HTH,

David



2023-01-14 20:55:10 dpchrist@laalaa /samba/dpchrist/sandbox/perl
$ cat system-one-argument.t
#!/usr/bin/env perl
# $Id: system-one-argument.t,v 1.1 2023/01/15 04:48:26 dpchrist Exp $
# by David Paul Christensen dpchr...@holgerdanske.com
# Public Domain
#
# Test Perl's system() built-in function w.r.t.:
# - Failure to execute
# - Child dying due to signal
# - Child exit value

use strict;
use warnings;
use Capture::Tiny   qw( capture );
use POSIX   qw( SIGHUP SIGUSR2 );
use Test::More;
use Test::Warn;

isnt $$, 0, join $", __FILE__, __LINE__,
sprintf 'Parent PID == %i is non-zero', $$;

isnt SIGHUP, 0, join $", __FILE__, __LINE__,
sprintf 'Signal SIGHUP == %i is non-zero', SIGHUP;

sub _debian_dash
{
my $sub = shift;
if (-e '/etc/debian_version') {
TODO: {
	local $TODO = 
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028275;;

$sub->();
}
}
else { $sub->() }
}

note "Child failed to execute";
{
my ($stdout, $stderr, $system) = capture {
system(q( nosuchprogram ));
};

is $stdout, '', join $", __FILE__, __LINE__,
sprintf q(STDOUT '%s' is empty string), $stdout;

my $qr = qr/^Can't exec "nosuchprogram": No such file or directory/;

like $stderr,
$qr,
join $", __FILE__, __LINE__,
sprintf q(STDERR '%s' is like %s), $stderr, $qr;

is $system, $?, join $", __FILE__, __LINE__,
sprintf 'System return value (0x%X) is $CHILD_ERROR (0x%X)',
$system,
$?;

is $?, -1, join $", __FILE__, __LINE__,
sprintf '$CHILD_ERROR (0x%X) is -1',
$?;

   is $? & 127, 0x7F, join $", __FILE__, __LINE__,
sprintf 'Lower 7 bits of $CHILD_ERROR (0x%X) are ones',
$? & 127;

is $? >> 8, (~0) >> 8, join $", __FILE__, __LINE__,
sprintf 'Upper bytes of $CHILD_ERROR (0x%X) are ones',
$? >> 8;
}

note "Child kills itself with signal HUP";
{
my $system = system(q( perl -e 'kill "HUP", $$' ));

is $system, $?, join $", __FILE__, __LINE__,
sprintf 'System return value (0x%X) is $CHILD_ERROR (0x%X)',
$system,
$?;

isnt $?, -1, join $", __FILE__, __LINE__,
sprintf '$CHILD_ERROR (0x%X) isnt -1',
$?;

_debian_dash sub {
is $? & 127, SIGHUP, join $", __FILE__, __LINE__,
sprintf 'Lower 7 bits of $CHILD_ERROR (0x%X) is SIGHUP (0x%X)',
$? & 127,
SIGHUP;
};

_debian_dash sub {
is $? >> 8, 0, join $", __FILE__, __LINE__,
sprintf 'Upper bytes of $CHILD_ERROR (0x%X) are zeroes',
$? >> 8;
};
}

note "Child kills itself with signal USR2";
{
my $system = system(q( perl -e 'kill "USR2", $$' ));

is $system, $?, join $", __FILE__, __LINE__,
sprintf 'System return value (0x%X) is $CHILD_ERROR (0x%X)',
$system,
$?;

isnt $?, -1, join $", __FILE__, __LINE__,
sprintf '$CHILD_ERROR (0x%X) isnt -1',
$?;

_debian_dash sub {
is $? & 127, SIGUSR2, join $", __FILE__, __LINE__,
sprintf 'Lower 7 bits of $CHILD_ERROR (0x%X) is SIGUSR2 (0x%X)',
$? & 127,
SIGUSR2;
};

_debian_dash sub {
is $? >> 8, 0, join $", __FILE__, __LINE__,
sprintf 'Upper bytes of $CHILD_ERROR (0x%X) are zeroes',
$? >> 8;
};
}

note "Child exits with value 0";
{
my $system = system(q( perl -e 'exit 0' ));

is $system, $?, join $", __FILE__, __LINE__,
sprintf 'System return value (0x%X) is $CHILD_ERROR (0x%X)',
$system,
$?;

isnt $?, -1, join $", __FILE__, __LINE__,
sprintf '$CHILD_ERROR (0x%X) isnt -1',
$?;

is $? & 127, 0, join $", __FILE__, __LINE__,
sprintf 'Lower 7 bits of $CHILD_ERROR (0x%X) are zeroes',
$? & 127;

is $? >> 8, 0, join $", __FILE__, __LINE__,
sprintf 'Upper bytes of $CHILD_ERROR (0x%X) are zeroes',
$? >> 8;
}

note "Child exits with value 0xA5";
{
my $system = system(qq( perl -e 'exit 0xA5' ));

is $system, $?, join $", __FILE__, __LINE__,
sprintf 'System return value (0x%X) is $CHILD_ERROR (0x%X)',
$system,
$?;

isnt $?, -1, join $", __FILE__, __LINE__,
sprintf '$CHILD_ERROR (0x%X) isnt -1',
$?;

is $? & 127, 0, join $", __FILE__, __LINE__,
sprintf 'Lower 7 bits of $CHILD_ERROR (0x%X) are zeroes',
$? & 127;

is $? >> 8, 0xA5, join $", __FILE__, __LINE__,
sprintf 'Upper bytes of $CHILD_ERROR (0x%X) are 0xA5',
$? >> 8;
}

done_testing;



2023-01-14 21:01:23 dpchrist@laalaa /samba/dpchrist/sandbox/perl
$ cat 

Bug#1028924: ledgersmb: Init script calls start-stop-daemon incorrectly, fails to start

2023-01-14 Thread JB

Package: ledgersmb
Version: 1.6.9+ds-2+deb11u3
Severity: important
X-Debbugs-Cc: j-dbug.666.114.1...@x.firehead.org

Dear Maintainer,

I installed LedgerSMB with defaults on Debian-11 with sysvinit (instead of
systemd).  When I try to start the daemon, it produces the following output:

# /etc/init.d/ledgersmb start
$Starting ledgersmb:
start-stop-daemon: unrecognized option '--interval=5'
Try 'start-stop-daemon --help' for more information.
#

I am not an expert on start-stop-daemon, but looking at the init script, it
seems start-stop-daemon is invoked with /usr/bin/start_server as the 
intended

program to run, which then has further arguments for that to start
/usr/bin/starman.  However the start-stop-daemon invocation lacks a 
"--start"
argument prior to the /usr/bin/start_server, and the "--start" seems to 
be the
norm among other uses of start-stop-daemon in the system's /etc/init.d/* 
files.

So maybe the init script is for some completely different version of
start-stop-daemon, or the arguments are really for a different program, or
something.  I'm not quite sure.


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

Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-20-amd64 (SMP w/2 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE 
not set

Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages ledgersmb depends on:
ii  adduser   3.118
ii  debconf [debconf-2.0] 1.5.77
ii  dpkg  1.20.12
ii  libcarp-always-perl   0.16-1
ii  libcgi-emulate-psgi-perl  0.23-1
ii  libcgi-simple-perl    1.115-2
ii  libclass-c3-xs-perl   0.15-1+b1
ii  libconfig-inifiles-perl   3.03-1
ii  libdata-uuid-perl 1.226-1+b1
ii  libdatetime-format-strptime-perl  1.7800-1
ii  libdatetime-perl  2:1.54-1
ii  libdbd-pg-perl    3.14.2-1+b1
ii  libdbi-perl   1.643-3+b1
ii  libhtml-escape-perl   1.10-1+b3
ii  libhttp-exception-perl    0.04007-1
ii  libio-stringy-perl    2.111-3
ii  libjs-dojo-dijit  1.15.4+dfsg1-1+deb11u1
ii  libjson-perl  4.03000-1
ii  liblocale-codes-perl  3.66-1
ii  liblocale-maketext-lexicon-perl   1.00-1.1
ii  liblog-log4perl-perl  1.54-1
ii  libmime-lite-perl 3.031-1
ii  libmime-types-perl    2.18-1
ii  libmoose-perl 2.2014-2
ii  libmoosex-nonmoose-perl   0.26-1.1
ii  libnamespace-autoclean-perl   0.29-1
ii  libnumber-format-perl 1.75-1.1
ii  libpgobject-perl  2.2.0-1
ii  libpgobject-simple-perl   3.02-1.1
ii  libpgobject-simple-role-perl  2.02-1.1
ii  libpgobject-type-bigfloat-perl    2.001-1
ii  libpgobject-type-bytestring-perl  1.2.3-1
ii  libpgobject-type-datetime-perl    2.02-1
ii  libpgobject-util-dbadmin-perl 1.4.0-1
ii  libpgobject-util-dbmethod-perl    1.00.003-1
ii  libplack-builder-conditionals-perl    0.05-1.1
ii  libplack-middleware-reverseproxy-perl 0.16-1
ii  libplack-perl 1.0048-1
ii  libplack-request-withencoding-perl    0.14-1
ii  libtemplate-perl  2.27-1+b3
ii  libtext-markdown-perl 1.31-3
ii  libtry-tiny-perl  0.30-1
ii  libversion-compare-perl   0.14-1.1
ii  libxml-simple-perl    2.25-1
ii  perl  5.32.1-4+deb11u2
ii  postgresql-client-13 [postgresql-client]  13.9-0+deb11u1
ii  postgresql-contrib    13+225
ii  starman   0.4015-1
ii  ucf   3.0043

Versions of packages ledgersmb recommends:
ii  apache2    2.4.54-1~deb11u1
pn  libjson-xs-perl    
pn  liblatex-driver-perl   
pn  libmath-bigint-gmp-perl    
pn  libtemplate-plugin-latex-perl  
pn  libtex-encode-perl 
pn  texlive-latex-recommended  

Versions of packages ledgersmb suggests:
ii  exim4-daemon-light [mail-transport-agent]  4.94.2-7
pn  latex-cjk-all  
pn  libimage-size-perl 
pn  libopenoffice-oodoc-perl   
pn  libx12-parser-perl 
pn  lpr    
ii  postgresql  

Bug#1028923: RFP: duelyst -- digital collectible card and turn-based strategy hybrid game

2023-01-14 Thread Joseph Nahmias
Package: wnpp
Severity: wishlist
X-Debbugs-Cc: j...@nahmias.net, debian-ga...@lists.debian.org, 
pkg-javascript-de...@lists.alioth.debian.org

* Package name: duelyst
  Version : 1.97.11
  Upstream Author : Counterplay Games
* URL : https://github.com/open-duelyst/duelyst
* License : CC0
  Programming Lang: JavaScript
  Description : digital collectible card and turn-based strategy hybrid game

In Duelyst, two players battle across a tactical battlefield, taking turns in
which they play and position minions and spells, represented by cards drawn
from a custom built deck, until one of the players eliminates the enemy
general. There are six factions in Duelyst, each with its own unique
characteristics that affect strategy and gameplay of the decks the player
builds.

The game offers a practice mode, puzzle-like challenges, a ranked season ladder
and a draft-style tournament mode.

Game client, server, and assets have all open-sourced.



Bug#1023160: ITP: libghc-filesystem -- Implementation of C++17 std::filesystem for C++11-20

2023-01-14 Thread Ben Westover
Hello,

On 1/8/23 10:59 AM, Bastian Germann wrote:
> Looking at Prism Launcher's source, this library is really unnecessary.
> Compiling with g++ -std set to c++17 or c++20 should do the trick.
> Maybe you have to patch the build system not to look for the library.

What in the source makes you think the library is unnecessary? I'm not
experienced with C++, but it seems that launcher/FileSystem.cpp makes
use of ghc::filesystem and some of its specific quirks.

Thanks,
--
Ben Westover


OpenPGP_signature
Description: PGP signature


Bug#1010445: Mono package in Debian is still very outdated (6.8 but should be 6.12)

2023-01-14 Thread Aaron Franke
Nearly a year ago I opened a bug report that Mono is outdated. It's still 
outdated. When will Debian update its package?
https://packages.debian.org/sid/mono-complete
When the package is updated, this website should say 6.12.0 instead of 6.8.0.


Bug#868871: Build diff-highlight

2023-01-14 Thread Franklin Yu
On Tue, 17 Nov 2020 15:17:44 -0800 Jonathan Nieder  wrote:
>
> Antoine Beaupré wrote:
>
> > On 2017-09-28 12:37:38, Jack Bates wrote:
> >
> > Any reason why this hasn't been applied to the package just yet?
> >
> > I'd be happy to do that in a NMU if there are no objections...
> 
> Please don't.  Adding additional contrib/ code to the supported
> surface without coordination is not an NMU I'd welcome at all
> (instead, it would be a bit of a rude shock).
> 
> Would it make sense to install this to /usr/share/git-core/contrib/?
> 
> If not, could it go in a separate package (within the same source
> package)?

Both choises sound good to me.

> I'm also curious about how this compares to
> https://pypi.org/project/diff-highlight/

Lack of diff-highlight currently blocks https://bugs.debian.org/931427. I don’t
think the Python version can work as a replacement in this case, so please
package the Git version regardless.

Bug#925288: please package diff-highlight executable

2023-01-14 Thread Franklin Yu
Thanks, Richard. I checked all the other three bugs merged with this bug, and I 
noticed that the bug 868871 has the latest status (from the package maintainer 
in 2020). I’ll post there.

Richard Lewis 
mailto:richard.lewis.deb...@googlemail.com>>
 於 2023年1月8日 上午8:08 寫道:

On Sat, 7 Jan 2023, 06:00 Franklin Yu, 
mailto:frankli...@hotmail.com>> wrote:
Hi maintainers, any update? Is there any plan to include the diff-highlight 
executable in the “git” package?

im not a maintainer, but it is in in /usr/share/doc/git/contrib/diff-highlight/

just needs to be made executable and put in /usr/bin (i would also like 
this "feature")

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




Bug#1028922: solaar doesn't enable plugdev when plugdev requested

2023-01-14 Thread Mason Loring Bliss
Package: solaar
Version: 1.0.4+dfsg-1

Solaar notes this on configuration:

> Please specify how non-root users should be given access to the Logitech
> receiver devices.
> 
> If systemd or consolekit are in use, they can apply ACLs to make them
> accessible via Solaar for the user logged in on the current seat. Right
> now, NEITHER daemon is running.
> 
> If neither of these daemons is in use, or if the receiver should also be
> accessible for remotely logged in users, it is possible to grant access
> for members of the "plugdev" system group.
> 
> If you do use the "plugdev" group, don't forget to make sure all the
> appropriate users are members of that group. You can add new members to
> the group by running, as root:
>adduser  plugdev
> For the group membership to take effect, the affected users need to log
> out and back in again.
> 
> Use plugdev group?
> 
>   

However, even if "yes" is selected, the line that includes plugdev is
commented out in the udev rules file shipped with the package,
/lib/udev/rules.d/60-solaar.rules:

# Grant members of the "plugdev" group access to receiver (useful for SSH users)
#MODE="0660", GROUP="plugdev"

...which results in plugdev not being set as the group for matching
devices, instead leaving them with the default 0600 root:root, which
plugdev users cannot access. If this line is manually uncommented Solaar
works as intended with plugdev users.

The easiest fix might be to simply be to note this in the configuration
dialog, as it'd be reasonable for users wanting this to work with plugdev
to understand that an additional manual step is required.

Observed on Debian Bullseye.

-- 
Mason Loring Bliss  ((   If I have not seen as far as others, it is because
 ma...@blisses.org   ))   giants were standing on my shoulders. - Hal Abelson


signature.asc
Description: PGP signature


Bug#1027844: btrfsmaintenance: noted BTRFS_BALANCE_PERIOD default in /etc/default/btrfsmaintenance is inconsistent w/systemd timer

2023-01-14 Thread Nicholas D Steeves
Control: tag -1 upstream

Hi Andrew,

andrew bezella  writes:

> ## Path:   System/File systems/btrfs
> ## Type:   string(none,daily,weekly,monthly)
> ## Default:"weekly"
> ## ServiceRestart: btrfsmaintenance-refresh
> #
> # Frequency of periodic balance.
> #
> # The frequency may be specified using one of the listed values or
> # in the format documented in the "Calendar Events" section of 
> systemd.time(7),
> # if available.
> BTRFS_BALANCE_PERIOD="weekly"
>
> however /lib/systemd/system/btrfs-balance.timer has:
> [Timer]
> OnCalendar=monthly
>
> it would seem that either the value/note in /etc/default/btrfsmaintenance
> or the OnCalendar value in btrfs-balance.timer should be updated to match
> the other.
>

Oh yeah!  I had forgotten about this minor issue.  The reason I hadn't
harmonised the files, doing this implicitly says that I (and Debian)
might recommend weekly balanced, or recommend monthly balances.

From what I've been able to gather, metadata balances have been
considered to be actively harmful for some time; This is mostly at the
level of tribal knowledge on the linux-btrfs mailing list.  It's also
the case that empty block groups are now automatically reclaimed by the
kernel, so a periodic balance only seems to be useful in
space-constrained situations where a lot of [meta]data churn occurs.

Thus, if I do anything, I'm inclined to set the period for balance to
"none" everywhere.

Also, what do you think about enabling the systemd patch watcher, so
that the timers are updated automatically when
/etc/default/btrfsmaintenance is modified?

Best,
Nicholas


signature.asc
Description: PGP signature


Bug#1027846: btrfsmaintenance: changing BTRFS_BALANCE_PERIOD, BTRFS_SCRUB_PERIOD etc. via systemd timer doesn't work

2023-01-14 Thread Nicholas D Steeves
Control: tag -1 + upstream pending

Hi Andrew,

Thank your reporting this, for writing a really nice bug report, and for
testing the fix.  Feel free to comment on the existing issue upstream
(if on exists), or to open a new one, because it is an upstream issue.
I agree with your analysis, and upstream's fix also uses the same method
as yours.

I've imported upstream's copy of the fix but will fully credit you in
the changelog :)

Regards,
Nicholas


signature.asc
Description: PGP signature


Bug#1028535: certbot: Please include the certbot(7) man page in the certbot package

2023-01-14 Thread Harlan Lieberman-Berg
tag 1028535 +pending
thanks

On Fri, Jan 13, 2023 at 12:28 PM Karl O. Pinc  wrote:
> What motivated me was interest in documenting this:
>
> ${webroot-path}/.well-known/acme-challenge
>
> I did just pester the certbot people into including that
> in certbot(1).  But it has been helpful in the past
> to know more about the protocol and details about choices,
> whether for validation or whatever.
> [snip]
> It can be helpful to have prose to look at and disk is
> cheap.

Fair point!  I committed the patch to my repo; it'll go out in the next upload.

Cheers!



Bug#1028921: RFS: pvm/3.4.6-5 [QA] -- Parallel Virtual Machine - binaries

2023-01-14 Thread Bo YU
Package: sponsorship-requests
Severity: important

Dear mentors,

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

 * Package name : pvm
   Version  : 3.4.6-5
   Upstream contact : [fill in name and email of upstream]
 * URL  : https://www.csm.ornl.gov/pvm/
 * License  : [fill in]
 * Vcs  : https://salsa.debian.org/debian/pvm
   Section  : devel

The source builds the following binary packages:

  pvm - Parallel Virtual Machine - binaries
  pvm-dev - Parallel Virtual Machine - development files
  libpvm3 - Parallel Virtual Machine - shared libraries
  pvm-examples - Parallel Virtual Machine - examples

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

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

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

  dget -x https://mentors.debian.net/debian/pool/main/p/pvm/pvm_3.4.6-5.dsc

Changes since the last upload:

 pvm (3.4.6-5) unstable; urgency=medium
 .
   * QA upload.
 .
   * Fix ftbfs on riscv64. (Closes: #1015924)
   * Set std ver to 4.6.2

--

The packages or its binary package is B-D for netpipe-pvm and tablix2,
so I think it make sense here, thanks.

-- 
Regards,
--
  Bo YU



signature.asc
Description: PGP signature


Bug#1021079: NMU w/o ppc64el?

2023-01-14 Thread Adam Borowski
Hi!
As you're apparently too busy to either fix ppc or suggest a different plan,
I'd make a NMU dropping ppc64el for now so the package can be released with
Bookworm.

Please say if I shouldn't.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Let's make a Debian conference in Yalta, Ukraine.
⢿⡄⠘⠷⠚⠋⠀
⠈⠳⣄



Bug#1028920: libpysal: FTBFS with new numpy

2023-01-14 Thread Bastian Germann

Source: libpysal
Version: 4.6.2-2
Severity: serious

libpysal FTBFS currently:

== short test summary info 
==
FAILED libpysal/weights/tests/test_gabriel.py::test_delaunay - numba.core.errors.TypingError: Failed in nopython mode 
pipeline (step: nopython frontend)
FAILED libpysal/weights/tests/test_gabriel.py::test_gabriel - numba.core.errors.TypingError: Failed in nopython mode 
pipeline (step: nopython frontend)
FAILED libpysal/weights/tests/test_gabriel.py::test_rng - numba.core.errors.TypingError: Failed in nopython mode 
pipeline (step: nopython frontend)
FAILED libpysal/weights/tests/test_raster.py::Testraster::test_da2W - numba.core.errors.LoweringError: Failed in 
nopython mode pipeline (step: native lowering)
FAILED libpysal/weights/tests/test_raster.py::Testraster::test_da2WSP - numba.core.errors.LoweringError: Failed in 
nopython mode pipeline (step: native lowering)
FAILED libpysal/weights/tests/test_raster.py::Testraster::test_wsp2da - numba.core.errors.LoweringError: Failed in 
nopython mode pipeline (step: native lowering)
FAILED libpysal/weights/tests/test_spatial_lag.py::Test_spatial_lag::test_lag_categorical - AttributeError: module 
'numpy' has no attribute 'int'

 7 failed, 416 passed, 41 skipped, 66 warnings in 
18.00s =



Bug#1028919: mupdf: Fails to build on GNU Hurd

2023-01-14 Thread Victor Westerhuis
Source: mupdf
Severity: normal
Tags: patch ftbfs

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear maintainer,

2 days ago sioyek was accepted into the Debian archive, but it fails to
build on GNU Hurd because of an old version of mupdf.

While GNU Hurd is not a release architecture, I managed to find out why
mupdf fails to build.

I have attached a patch that fixes the build issue on GNU Hurd without
breaking any other architectures.

Kind regards,


Victor Westerhuis


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

Kernel: Linux 6.0.0-6-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_NL.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en_US:en:nl_NL:nl
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEE6OxII3T+o0Ujs6ECQz2Rq5dHQPsFAmPDRksTHHZpY3RvckB3
ZXN0ZXJodS5pcwAKCRBDPZGrl0dA+9bMEACc75Oe2An9GtjTKPk8m1V1zGxff98x
v8F37eksHw2Ym6tcGZvj7ScDpzJ6eOnR4T/1HJHDrGYUwwkoCyDHAVu0sV+PH1Wz
NKAz0ozGm7rJglcoVFkvebinsCbqTOdcXIN8N9R2SnyrNW9LakgODKDlWzdexmgK
YYRueG9V4konee8xv4Sh4IuR5wqnEt1GYRfyDnBzZom01SwEB9puDWAUizmNm3vV
PXcniwbq3SdjUMguHiqf/DTC2o/4r2OP3npphuz/m4ASp8LXm9hQX7J3JTeiBlJF
xbHb75r3GlbDTUq03TeDkmQRKk2dUjzbMulsGGAbgMshbYDf+9jTXSOwRgDIkjxT
B5sq/i2ZLeYIvyyB6WS2wMiHgG5pwcHovBl474FcCI/4Hk/A4042AAWkTFtRIk2L
x9kbDDnSKx/OZZXBO6XP6RXTDuUqpeVEweg6rJv+JYzDhcOplwNrkj7uVT4bjkq8
tR6p+ynBtLIh9LRH5+uD2win/+pjionAWXmzjy95hDwEkDOhaG1gwOLFvGqxF+oC
sZtM53dXqQrgfz87VEHRnjy3eCakmnjmIokQ35h5mpBVp88FLl/l/h+dBszHvAv0
FTariZHkwCOzJQOdIOEjO8vDlohsCPFYt+FXtt0edGI3k69kixf1zmSQ49gsrETw
hjb8LD5g4BonOg==
=PFi4
-END PGP SIGNATURE-
From: Victor Westerhuis 
Date: Sun, 15 Jan 2023 00:21:34 +0100
Subject: Add fallback for missing SA_NOCLDWAIT

GNU Hurd does not implement SA_NOCLDWAIT. It also does not
automatically reap zombies if SIGCHLD is ignored.

This fallback does not check for failures from waitpid(2), because
there is not much the program can do about them.
---
 platform/gl/gl-main.c | 12 
 1 file changed, 12 insertions(+)

diff --git a/platform/gl/gl-main.c b/platform/gl/gl-main.c
index d5ae69c..3060020 100644
--- a/platform/gl/gl-main.c
+++ b/platform/gl/gl-main.c
@@ -2957,6 +2957,11 @@ static void signal_handler(int signal)
 {
if (signal == SIGHUP)
reloadrequested = 1;
+#ifndef SA_NOCLDWAIT
+   else if (signal == SIGCHLD)
+   while (waitpid(-1, NULL, WNOHANG) > 0)
+   ;
+#endif
 }
 #endif
 
@@ -2973,11 +2978,18 @@ int main(int argc, char **argv)
 #ifndef _WIN32
 
/* Never wait for termination of child processes. */
+#ifdef SA_NOCLDWAIT
struct sigaction arg = {
.sa_handler=SIG_IGN,
.sa_flags=SA_NOCLDWAIT
};
sigaction(SIGCHLD, , NULL);
+#else
+   struct sigaction arg = {
+   .sa_handler=signal_handler
+   };
+   sigaction(SIGCHLD, , NULL);
+#endif
 
signal(SIGHUP, signal_handler);
 #endif


Bug#1028917: passwd package missing dependency

2023-01-14 Thread Vincent Lefevre
On 2023-01-14 16:55:08 -0500, Jeffrey Walton wrote:
> As reported at https://lists.debian.org/debian-user/2023/01/msg00319.html :
> 
> Package: passwd (1:4.8.1-1) does not work without libpam-ldap , being
> a library which is not listed on the dependency section of the page
> dedicated to the package passwd

This message doesn't mention any issue.

On my bullseye machine, libpam-ldap is not installed, and everything
works fine.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#1026734: mricron: FTBFS: /usr/bin/ld.bfd: cannot find -lX11: No such file or directory

2023-01-14 Thread Lucas Nussbaum
Hi,

On 12/01/23 at 18:42 +0100, Andreas Tille wrote:
> Hi Santiago,
> 
> thanks again for watching me. ;-)
> 
> Am Thu, Jan 12, 2023 at 05:10:50PM +0100 schrieb Santiago Vila:
> > This is really weird.
> 
> +1
>  
> > This package also failed for me on bookworm, with the same error
> > which happened to Lucas (the one in the Subject).
> > 
> > But today I tried again (in bookworm) and it worked, without any source 
> > change at all.
> > (mricron version 1.2.20211006+dfsg-1).
> > 
> > I see that this change was made to try to fix the bug:
> > 
> > * Build-Depends: libx11-dev. Closes: #1026734
> > 
> > but libx11-dev was already being installed when the package was built:
> > 
> > https://buildd.debian.org/status/fetch.php?pkg=mricron=amd64=1.2.20211006%2Bdfsg-1=1637004231=0
> > 
> > (probably because of a build-dependency which in turn had a dependency on 
> > libx11-dev).
> 
> Yes, this is what I assumed ... but I wanted to be super sure.
>  
> > So, even if adding libx11-dev was probably correct and formally necessary,
> > as -lX11 was being used, I think it was not the real reason for the failure.
> > 
> > (Cc to Lucas, just in case he reported similar bugs in other packages).
> 
> I'd be also curious what might have caused that problem.

I don't think that there was a large number of similar failures when I
reported that bug. But yes it was probably a bug in another package.

You could try to 'bisect' using snapshot.debian.org to find the package
that introduced the problem, but it's fairly time consuming.

Lucas



Bug#1028857: libpsl: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2

2023-01-14 Thread Lucas Nussbaum
Hi Tim,

I can't find that new version (0.21.2) in Debian?

Lucas

On 14/01/23 at 20:19 +0100, Tim Rühsen wrote:
> Hey Lucas,
> 
> could you try with the latest release v0.21.2 ?
> 
> I am working on Debian sid, and can't reproduce the issue.
> 
> But I will examine the logs and/or try to build from the debian sources (in
> the next days).
> 
> Regards, Tim
> 
> On 14.01.23 13:59, Lucas Nussbaum wrote:
> > Source: libpsl
> > Version: 0.21.0-1.2
> > Severity: serious
> > Justification: FTBFS
> > Tags: bookworm sid ftbfs
> > User: lu...@debian.org
> > Usertags: ftbfs-20230113 ftbfs-bookworm
> > 
> > Hi,
> > 
> > During a rebuild of all packages in sid, your package failed to build
> > on amd64.
> > 
> > 
> > Relevant part (hopefully):
> > > make[5]: Entering directory '/<>/tests'
> > > PASS: test-is-public-builtin
> > > PASS: test-registrable-domain
> > > PASS: test-is-public
> > > PASS: test-is-cookie-domain-acceptable
> > > FAIL: test-is-public-all
> > > =
> > > libpsl 0.21.0: tests/test-suite.log
> > > =
> > > 
> > > # TOTAL: 5
> > > # PASS:  4
> > > # SKIP:  0
> > > # XFAIL: 0
> > > # FAIL:  1
> > > # XPASS: 0
> > > # ERROR: 0
> > > 
> > > .. contents:: :depth: 2
> > > 
> > > FAIL: test-is-public-all
> > > 
> > > 
> > > loaded 9458 suffixes and 8 exceptions
> > > builtin PSL has 9458 suffixes and 8 exceptions
> > > psl_is_public_suffix2(webview-assets.cloud9.ap-northeast-1.amazonaws.com, 
> > > PSL_TYPE_PRIVATE)=0 (expected 1)
> > > psl_is_public_suffix2(webview-assets.cloud9.ap-northeast-1.amazonaws.com, 
> > > PSL_TYPE_PRIVATE|PSL_TYPE_NO_STAR_RULE)=0 (expected 1)
> > > psl_is_public_suffix2(webview-assets.cloud9.ap-northeast-1.amazonaws.com, 
> > > PSL_TYPE_ANY)=0 (expected 1)
> > > psl_is_public_suffix2(webview-assets.cloud9.ap-northeast-1.amazonaws.com, 
> > > PSL_TYPE_ANY|PSL_TYPE_NO_STAR_RULE)=0 (expected 1)
> > > psl_is_public_suffix2(webview-assets.cloud9.ap-northeast-2.amazonaws.com, 
> > > PSL_TYPE_PRIVATE)=0 (expected 1)
> > > psl_is_public_suffix2(webview-assets.cloud9.ap-northeast-2.amazonaws.com, 
> > > PSL_TYPE_PRIVATE|PSL_TYPE_NO_STAR_RULE)=0 (expected 1)
> > > psl_is_public_suffix2(webview-assets.cloud9.ap-northeast-2.amazonaws.com, 
> > > PSL_TYPE_ANY)=0 (expected 1)
> > > psl_is_public_suffix2(webview-assets.cloud9.ap-northeast-2.amazonaws.com, 
> > > PSL_TYPE_ANY|PSL_TYPE_NO_STAR_RULE)=0 (expected 1)
> > > psl_is_public_suffix2(webview-assets.cloud9.ap-northeast-3.amazonaws.com, 
> > > PSL_TYPE_PRIVATE)=0 (expected 1)
> > > psl_is_public_suffix2(webview-assets.cloud9.ap-northeast-3.amazonaws.com, 
> > > PSL_TYPE_PRIVATE|PSL_TYPE_NO_STAR_RULE)=0 (expected 1)
> > > psl_is_public_suffix2(webview-assets.cloud9.ap-northeast-3.amazonaws.com, 
> > > PSL_TYPE_ANY)=0 (expected 1)
> > > psl_is_public_suffix2(webview-assets.cloud9.ap-northeast-3.amazonaws.com, 
> > > PSL_TYPE_ANY|PSL_TYPE_NO_STAR_RULE)=0 (expected 1)
> > > psl_is_public_suffix2(webview-assets.cloud9.ap-southeast-1.amazonaws.com, 
> > > PSL_TYPE_PRIVATE)=0 (expected 1)
> > > psl_is_public_suffix2(webview-assets.cloud9.ap-southeast-1.amazonaws.com, 
> > > PSL_TYPE_PRIVATE|PSL_TYPE_NO_STAR_RULE)=0 (expected 1)
> > > psl_is_public_suffix2(webview-assets.cloud9.ap-southeast-1.amazonaws.com, 
> > > PSL_TYPE_ANY)=0 (expected 1)
> > > psl_is_public_suffix2(webview-assets.cloud9.ap-southeast-1.amazonaws.com, 
> > > PSL_TYPE_ANY|PSL_TYPE_NO_STAR_RULE)=0 (expected 1)
> > > psl_is_public_suffix2(webview-assets.cloud9.ap-southeast-2.amazonaws.com, 
> > > PSL_TYPE_PRIVATE)=0 (expected 1)
> > > psl_is_public_suffix2(webview-assets.cloud9.ap-southeast-2.amazonaws.com, 
> > > PSL_TYPE_PRIVATE|PSL_TYPE_NO_STAR_RULE)=0 (expected 1)
> > > psl_is_public_suffix2(webview-assets.cloud9.ap-southeast-2.amazonaws.com, 
> > > PSL_TYPE_ANY)=0 (expected 1)
> > > psl_is_public_suffix2(webview-assets.cloud9.ap-southeast-2.amazonaws.com, 
> > > PSL_TYPE_ANY|PSL_TYPE_NO_STAR_RULE)=0 (expected 1)
> > > psl_is_public_suffix2(webview-assets.cloud9.ca-central-1.amazonaws.com, 
> > > PSL_TYPE_PRIVATE)=0 (expected 1)
> > > psl_is_public_suffix2(webview-assets.cloud9.ca-central-1.amazonaws.com, 
> > > PSL_TYPE_PRIVATE|PSL_TYPE_NO_STAR_RULE)=0 (expected 1)
> > > psl_is_public_suffix2(webview-assets.cloud9.ca-central-1.amazonaws.com, 
> > > PSL_TYPE_ANY)=0 (expected 1)
> > > psl_is_public_suffix2(webview-assets.cloud9.ca-central-1.amazonaws.com, 
> > > PSL_TYPE_ANY|PSL_TYPE_NO_STAR_RULE)=0 (expected 1)
> > > psl_is_public_suffix2(webview-assets.cloud9.eu-central-1.amazonaws.com, 
> > > PSL_TYPE_PRIVATE)=0 (expected 1)
> > > psl_is_public_suffix2(webview-assets.cloud9.eu-central-1.amazonaws.com, 
> > > PSL_TYPE_PRIVATE|PSL_TYPE_NO_STAR_RULE)=0 (expected 1)
> > > psl_is_public_suffix2(webview-assets.cloud9.eu-central-1.amazonaws.com, 
> > > PSL_TYPE_ANY)=0 (expected 1)
> > > psl_is_public_suffix2(webview-assets.cloud9.eu-central-1.amazonaws.com, 
> > > 

Bug#521169: apt-listbugs: aptcleanup gives spurious error message

2023-01-14 Thread Vincent Lefevre
Control: fixed -1 2.1.2-1.1

On 2023-01-14 23:18:27 +0100, Lucas Nussbaum wrote:
> This looks fixed in version 2.1.3-1 of ruby-locale (or fixed in another
> package in the meantime), but feel free to reopen if it is not the case.

This actually no longer works:

joooj% ruby -e "require 'locale'; print Locale.codeset"
Traceback (most recent call last):
-e:1:in `': undefined method `codeset' for Locale:Module (NoMethodError)

But according to /usr/lib/ruby/vendor_ruby/aptlistbugs/logic.rb,
this has been replaced by "Locale.charset", which gives:

joooj% ruby -e "require 'locale'; print Locale.charset"
ISO8859-1%

using the same locales as in my test in 2010:

joooj% locale   
LANG=POSIX
LANGUAGE=
LC_CTYPE=en_US.ISO8859-1
LC_NUMERIC="POSIX"
LC_TIME=en_DK
LC_COLLATE=POSIX
LC_MONETARY="POSIX"
LC_MESSAGES="POSIX"
LC_PAPER="POSIX"
LC_NAME="POSIX"
LC_ADDRESS="POSIX"
LC_TELEPHONE="POSIX"
LC_MEASUREMENT="POSIX"
LC_IDENTIFICATION="POSIX"
LC_ALL=

So this was fixed even in 2.1.2-1.1 (Debian 11.6 machine).

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#1028630: RFP: proftpd-mod-sftp-ldap -- module for ProFTPD supports retrieving/using user SSH public keys from LDAP

2023-01-14 Thread Hilmar Preuße

Am 13.01.2023 um 22:54 teilte Paweł Tomulik mit:

Hi Paweł,


ProFTPD mod_sftp_ldap may be very useful for ProFTPD installations with
virtual users stored in LDAP database together with SSH keys. It enables
the authentication based on these keys stored in LDAP.

The upstream project is here:
https://github.com/Castaglia/proftpd-mod_sftp_ldap

I've initially packaged it for Debian, and put here:
https://gitlab.com/ptomulik/proftpd-mod_sftp_ldap


Many thanks for your package so far, I can use the code nearly as it is!
For now I requested TJ to create a (pre-)release to make sure we don't
get in conflict when a potential 0.1 is released later on.

Yes, I could release version "0.0~git20220320.450f9b4-1"... let's see
how fast TJ answers.

Hilmar

[1] https://github.com/Castaglia/proftpd-mod_sftp_ldap/issues/9
--
sigfault



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

2023-01-14 Thread Thiago Franco Moraes
Hi Rebecca,

InVesalius can work without Theano (and Keras). It will use Pytorch.

Best regards.

Em sáb., 14 de jan. de 2023 às 08:12, Rebecca N. Palmer <
rebecca_pal...@zoho.com> escreveu:

> theano has been mostly abandoned upstream since 2018.  (The Aesara fork
> is not abandoned, but includes interface changes including the import
> name, so would break reverse dependencies not specifically altered for it.)
>
> Its reverse dependencies are keras, deepnano and invesalius.
>
> It is currently broken, probably by numpy 1.24 (#1027215), and the
> immediately obvious fixes weren't enough
> (https://salsa.debian.org/science-team/theano/-/pipelines).
>
> Is this worth spending more effort on fixing, or should we just remove it?
>
>
>


Bug#1028918: gtk3 flatpaks use subpixel highlighting

2023-01-14 Thread two
Package: flatpak, fontconfig-config

i am using Debian GNU/Linux testing, GNOME.

every package from flathub that uses GTK 3 displays text with subpixel 
antialiasing, while the system antialiasing is set to grayscale in dconf (the 
default).

users of other distros don't report this error.



Bug#962003: Linux kernel 5.6: [drm:i915_gem_gtt_finish_pages [i915]] *ERROR* Failed to wait for idle; VT'd may hang

2023-01-14 Thread Stefan Pietsch

On 30.12.22 11:42, Diederik de Haas wrote:

On Friday, 30 December 2022 01:48:53 CET Stefan Pietsch wrote:

Affected is at least linux-image-5.6.0-1-amd64 (5.6.7-1) and
linux-image-5.6.0-2-amd64 (5.6.14-1).>

This also affects 5.5.0-rc5-amd64.

(https://snapshot.debian.org/archive/debian/20200106T211159Z/pool/main/l/l
inux/)

The kernel boot option "intel_iommu=igfx_off" prevents the error message.


This seems to be resolved in newer kernel versions.
I'm not able to reproduce this with kernel version 5.14.0-4-amd64
(5.14.16-1).


Great that it is resolved :-)

As many people are affected and the Stable kernel version still seems to
exhibit the problem, I want to ask a question:
Are you willing to help out to narrow down as much as possible which version
introduced the error and in which is was fixed? Wrt the latter, does 5.14.12-1
still show the issue?


[...]

Just a small update: kernel version 5.13.9-1~exp2 is also not affected by the 
problem.



Bug#1028638: libproxy1v5: Gajim 1.6.0-1 crashes in libproxy call

2023-01-14 Thread Martin
Control: severity -1 normal

The problem disappeared magically for all users who reported it before.
I assume, that there is a hidden bug in libproxy, that only appears in
certain circumstances. Downgrading for now.



Bug#1028917: passwd package missing dependency

2023-01-14 Thread Jeffrey Walton
Package: passwd
Version:  1:4.8.1-1
Tags: bullseye

As reported at https://lists.debian.org/debian-user/2023/01/msg00319.html :

Package: passwd (1:4.8.1-1) does not work without libpam-ldap , being
a library which is not listed on the dependency section of the page
dedicated to the package passwd



Bug#1028916: RFP: watchfiles -- Simple, modern and fast file watching and code reload in python.

2023-01-14 Thread Sandro Tosi
Package: wnpp
Severity: wishlist
X-Debbugs-Cc: mo...@debian.org
Control: block -1 by #999850

* Package name: watchfiles
  Version : 0.18.1
  Upstream Contact: Samuel Colvin
* URL : https://github.com/samuelcolvin/watchfiles
* License : MIT
  Programming Lang: Python
  Description : Simple, modern and fast file watching and code reload in 
python.

This is the re-incarnation of https://tracker.debian.org/pkg/python-watchgod ,
and it's needed by the new upstream release of uvicorn:
https://github.com/encode/uvicorn/blob/master/pyproject.toml#L44 .

watchfiles build system needs maturin, which is currently not in debian but
being worked on in #999850



Bug#1002053: Also causes problems for MIT and Expat licenses

2023-01-14 Thread Soren Stoutner
The same basic problem also occurs with MIT and Expat licenses.  The 
specification for the 
AppStream metadata file only has a few options, one of them being MIT and none 
of them 
being Expat.

https://freedesktop.org/software/appstream/docs/chap-Quickstart.html#qsr-app-contents[1]

Debian, of course, prefers the Expat name as it is more precise.

Which leads to this Lintian warning:

inconsistent-appstream-metadata-license debian/metainfo.xml (mit != expat) 
[debian/
copyright]

-- 
Soren Stoutner
so...@stoutner.com


[1] 
https://freedesktop.org/software/appstream/docs/chap-Quickstart.html#qsr-app-contents


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


Bug#1028915: [pre-approve] unblock: rustc/1.63.0+dfsg1-2

2023-01-14 Thread Fabian Grünbichler
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: ru...@packages.debian.org, 
pkg-rust-maintain...@alioth-lists.debian.net
Control: affects -1 + src:rustc

Hello release team!

This request is for pre-approval of a not-yet-uploaded fixed version of
rustc. You can find the git tree for the proposed changes on salsa[0], a
debdiff (without changelog finalization) is attached. The current
version in experimental contains the same verified fix + an upgrade to
1.64.0 - I'd happy to upload that one to unstable as well, but you
probably prefer the more targeted approach of just cherry-picking the
armel fixes on top of 1.63.0, as described below.

[ Reason ]
The current rustc version in bookworm (1.63.0+dfsg1-1) is affected by
#1028629 (a broken hacky workaround for intrinsics breaking parts of the
atomic module of Rust's std library[1]).

[ Impact ]
Rust code using the broken parts of the atomic module will fail to link
(on armel).

[ Tests ]
The reproducer in the linked bug report and the rust-portable-atomic 
autopkgtests
reproduce the issue (the latter has other issues with autopkgtests on
armel, but the linking issue is separate from those), both are fixed
with the patches contained in the -2 release.

[ Risks ]
The original (broken) patch was just a workaround until the final fix
was developed upstream (in the compiler_builtins crate used by rustc).
The proposed fix is only cherry-picking upstream improvements in the
area of arm(el) intrinsics and reverting the workaround.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

[ Other info ]

0: https://salsa.debian.org/fg/rust/-/tree/bookworm-armel-fix
1: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028629

unblock rustc/1.63.0+dfsg1-2
diff -Nru rustc-1.63.0+dfsg1/debian/changelog 
rustc-1.63.0+dfsg1/debian/changelog
--- rustc-1.63.0+dfsg1/debian/changelog 2022-12-07 17:29:00.0 +0100
+++ rustc-1.63.0+dfsg1/debian/changelog 2023-01-14 09:38:46.0 +0100
@@ -1,3 +1,11 @@
+rustc (1.63.0+dfsg1-2) UNRELEASED; urgency=medium
+
+  [ Fabian Grünbichler ]
+  * fix compiler_builtins linkage on arm(el)
+  * add compiler_builtins sync fallbacks for arm(el)
+
+ -- Fabian Gruenbichler   Sat, 14 Jan 2023 
09:38:46 +0100
+
 rustc (1.63.0+dfsg1-1) unstable; urgency=medium
 
   * Upload to unstable (Closes: #1018859)
diff -Nru rustc-1.63.0+dfsg1/debian/patches/series 
rustc-1.63.0+dfsg1/debian/patches/series
--- rustc-1.63.0+dfsg1/debian/patches/series2022-12-07 17:29:00.0 
+0100
+++ rustc-1.63.0+dfsg1/debian/patches/series2023-01-14 09:38:29.0 
+0100
@@ -5,8 +5,9 @@
 u-reproducible-build.patch
 u-ignore-endian-big-diff.patch
 
-# should be replaced with a proper fix once fixed upstream
-u-hack-armel-no-kernel-user-helpers.patch
+# can be dropped once upstream updates compiler_builtins
+u-arm-compiler-builtins-weak-linkage-arm.patch
+u-arm-compiler-builtins-add-sync-builtin-fallbacks.patch
 
 # not forwarded, or forwarded but unlikely to be merged
 u-ignore-ppc-hangs.patch
diff -Nru 
rustc-1.63.0+dfsg1/debian/patches/u-arm-compiler-builtins-add-sync-builtin-fallbacks.patch
 
rustc-1.63.0+dfsg1/debian/patches/u-arm-compiler-builtins-add-sync-builtin-fallbacks.patch
--- 
rustc-1.63.0+dfsg1/debian/patches/u-arm-compiler-builtins-add-sync-builtin-fallbacks.patch
  1970-01-01 01:00:00.0 +0100
+++ 
rustc-1.63.0+dfsg1/debian/patches/u-arm-compiler-builtins-add-sync-builtin-fallbacks.patch
  2023-01-14 09:38:29.0 +0100
@@ -0,0 +1,223 @@
+From 56172fcd8bd045e38bbdf76697d1fcca1e965d6d Mon Sep 17 00:00:00 2001
+From: Alex Huszagh 
+Date: Fri, 29 Jul 2022 16:58:05 -0500
+Subject: [PATCH] Add compiler-rt fallbacks for sync builtins on armv5te-musl.
+
+---
+https://github.com/rust-lang/compiler-builtins/pull/484
+
+ src/arm_linux.rs | 110 +++
+ 1 file changed, 73 insertions(+), 37 deletions(-)
+
+diff --git a/vendor/compiler_builtins/src/arm_linux.rs 
b/vendor/compiler_builtins/src/arm_linux.rs
+index 8fe0948..8f22eb6 100644
+--- a/vendor/compiler_builtins/src/arm_linux.rs
 b/vendor/compiler_builtins/src/arm_linux.rs
+@@ -55,7 +55,7 @@ fn insert_aligned(aligned: u32, val: u32, shift: u32, mask: 
u32) -> u32 {
+ }
+ 
+ // Generic atomic read-modify-write operation
+-unsafe fn atomic_rmw u32>(ptr: *mut T, f: F) -> u32 {
++unsafe fn atomic_rmw u32, G: Fn(u32, u32) -> u32>(ptr: *mut 
T, f: F, g: G) -> u32 {
+ let aligned_ptr = align_ptr(ptr);
+ let (shift, mask) = get_shift_mask(ptr);
+ 
+@@ -65,7 +65,7 @@ unsafe fn atomic_rmw u32>(ptr: *mut T, f: 
F) -> u32 {
+ let newval = f(curval);
+ let newval_aligned = insert_aligned(curval_aligned, newval, shift, 
mask);
+ if __kuser_cmpxchg(curval_aligned, newval_aligned, aligned_ptr) {
+-return curval;
++

Bug#1028914: librust-dns-lookup+clippy-dev uninstallable

2023-01-14 Thread Steve Langasek
Package: librust-dns-lookup+clippy-dev
Version: 1.0.8-2
Severity: grave
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu lunar

rust-dns-lookup builds a binary package which is uninstallable, because
librust-clippy-0+default-dev is not available in Debian:

$ sudo apt install librust-dns-lookup+clippy-dev
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 librust-dns-lookup+clippy-dev : Depends: librust-clippy-0+default-dev but it 
is not installable
E: Unable to correct problems, you have held broken packages.
$

Please drop this uninstallable binary package so that rust-dns-lookup is
releasable.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature


Bug#1027467: dyssol: FTBFS without network access

2023-01-14 Thread Steve Langasek
Control: reopen -1

Output from build of 1.1.0+ds1-2:

[...]
(models_development: line 1596) broken
http://de.mathworks.com/help/matlab/cc-mx-matrix-library.html - 
HTTPConnectionPool(host='de.mathworks.com', port=80): Max retries exceeded with 
url: /help/matlab/cc-mx-matrix-library.html (Caused by 
NewConnectionError(': Failed to establish a new connection: [Errno -2] Name or 
service not known'))
(  simulation: line   93) broken
https://computing.llnl.gov/projects/sundials - 
HTTPSConnectionPool(host='computing.llnl.gov', port=443): Max retries exceeded 
with url: /projects/sundials (Caused by 
NewConnectionError(': Failed to establish a new connection: [Errno -2] Name or 
service not known'))
(   index: line   89) broken
https://doi.org/10.1007/978-3-030-45168-4_17 - 
HTTPSConnectionPool(host='doi.org', port=443): Max retries exceeded with url: 
/10.1007/978-3-030-45168-4_17 (Caused by 
NewConnectionError(': Failed to establish a new connection: [Errno -2] Name or 
service not known'))
(  simulation: line  100) broken
https://computing.llnl.gov/projects/sundials/ida - 
HTTPSConnectionPool(host='computing.llnl.gov', port=443): Max retries exceeded 
with url: /projects/sundials/ida (Caused by 
NewConnectionError(': Failed to establish a new connection: [Errno -2] Name or 
service not known'))
(  simulation: line  102) broken
https://computing.llnl.gov/projects/sundials/kinsol - 
HTTPSConnectionPool(host='computing.llnl.gov', port=443): Max retries exceeded 
with url: /projects/sundials/kinsol (Caused by 
NewConnectionError(': Failed to establish a new connection: [Errno -2] Name or 
service not known'))
(   units: line 1578) broken
https://doi.org/10.1007/978-3-662-52989-8_91 - 
HTTPSConnectionPool(host='doi.org', port=443): Max retries exceeded with url: 
/10.1007/978-3-662-52989-8_91 (Caused by 
NewConnectionError(': Failed to establish a new connection: [Errno -2] Name or 
service not known'))
(   index: line   85) broken
https://doi.org/10.1016/j.powtec.2017.01.061 - 
HTTPSConnectionPool(host='doi.org', port=443): Max retries exceeded with url: 
/10.1016/j.powtec.2017.01.061 (Caused by 
NewConnectionError(': Failed to establish a new connection: [Errno -2] Name or 
service not known'))
(   index: line   87) brokenhttps://doi.org/10.3390/pr7080535 - 
HTTPSConnectionPool(host='doi.org', port=443): Max retries exceeded with url: 
/10.3390/pr7080535 (Caused by 
NewConnectionError(': Failed to establish a new connection: [Errno -2] Name or 
service not known'))
(   index: line   88) broken
https://doi.org/10.1016/j.softx.2020.100572 - 
HTTPSConnectionPool(host='doi.org', port=443): Max retries exceeded with url: 
/10.1016/j.softx.2020.100572 (Caused by 
NewConnectionError(': Failed to establish a new connection: [Errno -2] Name or 
service not known'))
(   index: line   86) broken
https://doi.org/10.1016/j.apt.2018.12.007 - HTTPSConnectionPool(host='doi.org', 
port=443): Max retries exceeded with url: /10.1016/j.apt.2018.12.007 (Caused by 
NewConnectionError(': Failed to establish a new connection: [Errno -2] Name or 
service not known'))
(000_get_started/get_started: line   20) broken
https://github.com/FlowsheetSimulation/Dyssol-open/releases - 
HTTPSConnectionPool(host='github.com', port=443): Max retries exceeded with 
url: /FlowsheetSimulation/Dyssol-open/releases (Caused by 
NewConnectionError(': Failed to establish a new connection: [Errno -2] Name or 
service not known'))
(data: line   26) broken
https://www.hdfgroup.org/solutions/hdf5/ - 
HTTPSConnectionPool(host='www.hdfgroup.org', port=443): Max retries exceeded 
with url: /solutions/hdf5/ (Caused by 
NewConnectionError(': Failed to establish a new connection: [Errno -2] Name or 
service not known'))
(models_development: line9) broken
https://go.microsoft.com/fwlink/?LinkId=615448=0x409 - 
HTTPSConnectionPool(host='go.microsoft.com', port=443): Max retries exceeded 
with url: /fwlink/?LinkId=615448=0x409 (Caused by 
NewConnectionError(': Failed to establish a new connection: [Errno -2] Name or 
service not known'))

== slowest reading durations ===
0.726 class
0.351 units
0.302 models_development
0.100 001_ui/gui
0.074 001_ui/cli
build finished with problems, 1 warning.
make[5]: *** [CMakeFiles/doc.dir/build.make:74: doc] Error 1
[...]

  (https://launchpad.net/ubuntu/+source/dyssol/1.1.0+ds1-2/+build/25483317)

So no, doesn't appear to be fixed.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org



Bug#1026200: Please package LilyPond 2.24.0 if possible

2023-01-14 Thread Jonas Hahnfeld
On Wed, 2022-12-28 at 22:16 +0100, Jonas Hahnfeld wrote:
> On Fri, 16 Dec 2022 15:27:32 +1100 John Zaitseff
>  wrote:
> > Package: lilypond
> > Severity: wishlist
> > 
> > I know it's a lot to ask for :-), but now that LilyPond 2.24.0 has
> > been released, it would be good to have it in Debian.  Let me know
> > if I can help bring this about!
> 
> Yes, please  actually, aligning our release of LilyPond 2.24.0 with
> Debian's freeze plans was very intentional:
> https://lists.gnu.org/archive/html/lilypond-devel/2022-05/msg00099.html
> 
> That said, I just realized that guile-2.2-libs has been *removed* as
> part of #1023560 while it is the preferred version of Guile for this
> release of LilyPond. What are the chances of getting this back into the
> repos?

Ping, also CC'ing Rob Browning for Guile.


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


Bug#1028913: python3-poetry: poetry commands depends on pylev (python3-pylev)

2023-01-14 Thread Vincent-Xavier JUMEL
Package: python3-poetry
Version: 1.3.2+dfsg-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

   I've observed on Debian Sid that python3-pylev has to be removed when
   upgrading to python3.11. Alas, when trying to work with poetry, i got the
   following traceback :

❯ poetry new
Traceback (most recent call last):
  File "/usr/bin/poetry", line 5, in 
from poetry.console.application import main
  File "/usr/lib/python3/dist-packages/poetry/console/application.py", line 11, 
in 
from cleo.application import Application as BaseApplication
  File "/usr/lib/python3/dist-packages/cleo/application.py", line 12, in 

from cleo.commands.completions_command import CompletionsCommand
  File "/usr/lib/python3/dist-packages/cleo/commands/completions_command.py", 
line 10, in 
from cleo import helpers
  File "/usr/lib/python3/dist-packages/cleo/helpers.py", line 5, in 
from cleo.io.inputs.argument import Argument
  File "/usr/lib/python3/dist-packages/cleo/io/inputs/argument.py", line 5, in 

from cleo.exceptions import CleoLogicError
  File "/usr/lib/python3/dist-packages/cleo/exceptions/__init__.py", line 3, in 

from cleo._utils import find_similar_names
  File "/usr/lib/python3/dist-packages/cleo/_utils.py", line 8, in 
from pylev import levenshtein
ModuleNotFoundError: No module named 'pylev'

Poetry should depends on python3-pylev : if I install poetry in a Python
virtualenv, every thing works as excpeted and it pulls pylev from pip ; if I
install python3-pylev direct, poetry works fine.

I've even tested on a fresh new debian:sid docker image.

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

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

Versions of packages python3-poetry depends on:
ii  python3 3.11.1-1
ii  python3-cachecontrol0.12.12-2
ii  python3-cleo2.0.1-3
ii  python3-crashtest   0.4.1-1
ii  python3-dulwich 0.20.50-1+b1
ii  python3-filelock3.9.0-1
ii  python3-html5lib1.1-3
ii  python3-importlib-metadata  4.12.0-1
ii  python3-jsonschema  4.9.1-3
ii  python3-keyring 23.9.3-2
ii  python3-lockfile1:0.12.2-2.2
ii  python3-packaging   23.0-1
ii  python3-pexpect 4.8.0-4
ii  python3-pkginfo 1.8.2-2
ii  python3-platformdirs2.6.0-1
ii  python3-poetry-core 1.4.0-3
ii  python3-requests2.28.1+dfsg-1
ii  python3-requests-toolbelt   0.10.1-1
ii  python3-shellingham 1.5.0-1
ii  python3-tomli   2.0.1-2
ii  python3-tomlkit 0.11.6-1
ii  python3-urllib3 1.26.12-1
ii  python3-virtualenv  20.17.1+ds-1

python3-poetry recommends no packages.

python3-poetry suggests no packages.

-- no debconf information

-- 
Vincent-Xavier JUMEL Id: 0xBC8C2BAB14ABB3F2 https://blog.thetys-retz.net

Société Libre, Logiciel Libre http://www.april.org/adherer
Parinux, logiciel libre à Paris : http://www.parinux.org



Bug#1028810: aspectc++: FTBFS: ld: cannot find -lPolly: No such file or directory

2023-01-14 Thread Reinhard Tartler

Control: reassign -1 llvm-14
Control: affects -1 aspectc++

Hi Lucas,

thanks for filing this report.

My understanding of this issue is that a recent change in llvm 14 leads to the 
list of libraries listed by `llvm-config-14 --libs` to be incomplete. I think 
that this build would succeed if it included -lPolly.

You can see how aspectc++ invokes llvm-config here: 
https://salsa.debian.org/debian/aspectc/-/blob/791f390f845b2fafd19ff0c648618e8e14cee726/AspectC++/Makefile#L79

Dear LLVM maintainers, does this make sense to you?

-rt

On 1/14/23 7:30 AM, Lucas Nussbaum wrote:

Source: aspectc++
Version: 1:2.3+git20221129-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230113 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 '/<>/AspectC++/ACModel'
---
Making ACModel library for TARGET=linux-release
Compiler = g++ -DNDEBUG  -std=gnu++11 -I../../Puma/extern `xml2-config 
--cflags`  -O2 -g -Wall -pipe -Wno-deprecated-declarations -Wall -pipe 
-Wno-deprecated-declarations
---
Making dependency file ObjFiles/linux-release/Elements.o.
---
Making dependency file ObjFiles/linux-release/MatchExpr.o.
Making dependency file DepFiles/linux-release/ACConfig.d.
Making dependency file ObjFiles/linux-release/MatchName.o.
Making dependency file DepFiles/linux-release/ACProject.d.
Making AspectC++ for TARGET=linux-release
Making dependency file DepFiles/linux-release/AdviceInfo.d.
Making dependency file ObjFiles/linux-release/MatchTemplateArg.o.
   Compiler = g++ -DNDEBUG  -std=gnu++11 -I../Puma/extern -I../Puma/include 
-I/usr/include/libxml2  -I/usr/lib/llvm-14/include -D_GNU_SOURCE 
-D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS 
-DFRONTEND_CLANG -O2 -g -Wall -pipe -Wno-deprecated-declarations  -fno-rtti 
-Wno-strict-aliasing  -std=gnu++14
   Linker   = g++ -O2 -g -Wall -pipe -Wno-deprecated-declarations  -fno-rtti 
-Wno-strict-aliasing  -std=gnu++14   -L../Puma/lib/linux-release 
-lMiniPuma  -lxml2  -lclangRewriteFrontend -lclangRewrite -lclangFrontend 
-lclangSerialization -lclangDriver -lclangParse -lclangSema -lclangAnalysis 
-lclangEdit -lclangAST -lclangLex -lclangBasic -lLLVMAsmParser -lLLVMMCParser 
-lLLVMBitReader -lLLVMTransformUtils -lLLVMCore -lLLVMMC -lLLVMOption -lLLVMSupport 
-Wl,--as-needed -latomic -Wl,--no-as-needed -Xlinker 
--wrap=_ZN5clang4Sema19canSkipFunctionBodyEPNS_4DeclE -Xlinker 
--wrap=_ZN5clang4Sema21ProcessStmtAttributesEPNS_4StmtERKNS_25ParsedAttributesWithRangeERN4llvm15SmallVectorImplIPKNS_4AttrEEE
 -L/usr/lib/llvm-14/lib  -lLLVMWindowsManifest -lLLVMXRay -lLLVMLibDriver 
-lLLVMDlltoolDriver -lLLVMCoverage -lLLVMLineEditor -lLLVMM68kDisassembler 
-lLLVMM68kAsmParser -lLLVMM68kCodeGen -lLLVMM68kDesc -lLLVMM68kInfo 
-lLLVMXCoreDisassembler -lLLVMXCoreCodeGen -lLLVMXCoreDesc -lLLVMXCoreInfo 
-lLLVMX86TargetMCA -lLLVMX86Disassembler -lLLVMX86AsmParser -lLLVMX86CodeGen 
-lLLVMX86Desc -lLLVMX86Info -lLLVMWebAssemblyDisassembler -lLLVMWebAssemblyAsmParser 
-lLLVMWebAssemblyCodeGen -lLLVMWebAssemblyDesc -lLLVMWebAssemblyUtils 
-lLLVMWebAssemblyInfo -lLLVMVEDisassembler -lLLVMVEAsmParser -lLLVMVECodeGen 
-lLLVMVEDesc -lLLVMVEInfo -lLLVMSystemZDisassembler -lLLVMSystemZAsmParser 
-lLLVMSystemZCodeGen -lLLVMSystemZDesc -lLLVMSystemZInfo -lLLVMSparcDisassembler 
-lLLVMSparcAsmParser -lLLVMSparcCodeGen -lLLVMSparcDesc -lLLVMSparcInfo 
-lLLVMRISCVDisassembler -lLLVMRISCVAsmParser -lLLVMRISCVCodeGen -lLLVMRISCVDesc 
-lLLVMRISCVInfo -lLLVMPowerPCDisassembler -lLLVMPowerPCAsmParser -lLLVMPowerPCCodeGen 
-lLLVMPowerPCDesc -lLLVMPowerPCInfo -lLLVMNVPTXCodeGen -lLLVMNVPTXDesc 
-lLLVMNVPTXInfo -lLLVMMSP430Disassembler -lLLVMMSP430AsmParser -lLLVMMSP430CodeGen 
-lLLVMMSP430Desc -lLLVMMSP430Info -lLLVMMipsDisassembler -lLLVMMipsAsmParser 
-lLLVMMipsCodeGen -lLLVMMipsDesc -lLLVMMipsInfo -lLLVMLanaiDisassembler 
-lLLVMLanaiCodeGen -lLLVMLanaiAsmParser -lLLVMLanaiDesc -lLLVMLanaiInfo 
-lLLVMHexagonDisassembler -lLLVMHexagonCodeGen -lLLVMHexagonAsmParser 
-lLLVMHexagonDesc -lLLVMHexagonInfo -lLLVMBPFDisassembler -lLLVMBPFAsmParser 
-lLLVMBPFCodeGen -lLLVMBPFDesc -lLLVMBPFInfo -lLLVMAVRDisassembler -lLLVMAVRAsmParser 
-lLLVMAVRCodeGen -lLLVMAVRDesc -lLLVMAVRInfo -lLLVMARMDisassembler -lLLVMARMAsmParser 
-lLLVMARMCodeGen -lLLVMARMDesc -lLLVMARMUtils -lLLVMARMInfo -lLLVMAMDGPUTargetMCA 
-lLLVMAMDGPUDisassembler -lLLVMAMDGPUAsmParser -lLLVMAMDGPUCodeGen -lLLVMAMDGPUDesc 
-lLLVMAMDGPUUtils -lLLVMAMDGPUInfo -lLLVMAArch64Disassembler -lLLVMAArch64AsmParser 
-lLLVMAArch64CodeGen -lLLVMAArch64Desc -lLLVMAArch64Utils -lLLVMAArch64Info 
-lLLVMPerfJITEvents -lLLVMOrcJIT -lLLVMMCJIT -lLLVMJITLink -lLLVMInterpreter 
-lLLVMExecutionEngine -lLLVMRuntimeDyld -lLLVMOrcTargetProcess -lLLVMOrcShared 
-lLLVMDWP -lLLVMSymbolize -lLLVMDebugInfoPDB -lLLVMDebugInfoGSYM -lLLVMOption 
-lLLVMObjectYAML -lLLVMMCA -lLLVMMCDisassembler -lLLVMLTO 

Bug#1028897: fontconfig-config: default latin fonts changed from DejaVu to Noto

2023-01-14 Thread Raphaël Halimi

reassign 1028897 fontconfig
retitle 1028897 fontconfig: wrong name for the Noto monospace font
merge 1028897 1028643
tags 1028897 patch
thanks

--
Raphaël Halimi
Description: Fix default monospace font
 With Fontconfig 2.14, upstream made the Noto fonts default, but used "Noto
 Sans Mono" as the default font for the monospace family, which exists, but is
 actually not a monospace font. The right name is "Noto Mono".
Author: Raphaël Halimi 
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028897
Forwarded: no
Last-Update: 2023-01-14
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
--- a/conf.d/60-latin.conf
+++ b/conf.d/60-latin.conf
@@ -35,7 +35,7 @@
 	
 		monospace
 		
-			Noto Sans Mono
+			Noto Mono
 			DejaVu Sans Mono
 			Inconsolata
 			Andale Mono


Bug#1028897: fontconfig-config: default latin fonts changed from DejaVu to Noto

2023-01-14 Thread Raphaël Halimi

reassign -1 fontconfig
retitle -1 fontconfig: wrong name for the Noto monospace font
merge -1 1028643
tags -1 patch
thanks

Le 14/01/2023 à 19:45, Raphaël Halimi a écrit :

If you wish to keep DejaVu as default, here is a simple patch to do that.


Ok, scratch this patch. I know that Debian don't like to diverge from 
upstream (and I'm a maintainer myself), so this was not a good idea. 
Moreover, the change from DejaVu to Noto was not the root cause of the 
problem.


The problem is that the monospace Noto font is actually "Noto Mono" and 
not "Noto Sans Mono" (probably a typo on upstream's part).


If you use a font manager you'll see that there is indeed a font called 
"Noto Sans Mono", but if you filter them out to list only the monospace 
fonts, you can see that there's no font called "Noto Sans Mono" among 
them, but there is one called "Noto Mono".


Using this one (which I now believe is the "real" monospace font from 
Noto) as default for the monospace family does fix both Xterm and 
gnome-terminal (and probably other terminals too).


This new patch fixes what I think is actually a bug (and which probably 
needs to be forwarded to upstream).


Regards,

--
Raphaël Halimi
Description: Fix default monospace font
 With Fontconfig 2.14, upstream made the Noto fonts default, but used "Noto
 Sans Mono" as the default font for the monospace family, which exists, but is
 actually not a monospace font. The right name is "Noto Mono".
Author: Raphaël Halimi 
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028897
Forwarded: no
Last-Update: 2023-01-14
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
--- a/conf.d/60-latin.conf
+++ b/conf.d/60-latin.conf
@@ -35,7 +35,7 @@
 	
 		monospace
 		
-			Noto Sans Mono
+			Noto Mono
 			DejaVu Sans Mono
 			Inconsolata
 			Andale Mono


Bug#1028667: dask BD-Uninstallable

2023-01-14 Thread Andreas Tille
Hi Rebecca,

Am Sat, Jan 14, 2023 at 08:18:37PM + schrieb Rebecca N. Palmer:
> Control: retitle -1 dask: B-D on python-numpy-doc which no longer exists
> Control: tags -1 pending
> 
> The python-numpy-doc error is because that package no longer exists. This
> build-dependency has already been removed in Salsa.
> 
> However, that version doesn't build the dask documentation due to other
> issues.  There's a version in my test PPA that I think does build the
> documentation, but I have *not* checked whether that documentation works
> (that PPA existed for checking whether the new dask + dask.distributed broke
> any of their reverse dependencies):
> https://launchpad.net/~rebecca-palmer/+archive/ubuntu/dask2022p12v2/+packages

I'm positively convinced that we should for the moment live with an
empty doc package for dask - may be just containing a hint to the online
documentation.  There is no time to fine-tune the docs and leave lots
of other packages behind just for a piece of documentation.
 
> The python3-pandas error is because pandas now declares a Breaks: on dask
> (<= current) because of #1025393, and dask build-depends on
> python3-distributed and hence indirectly on itself.  (dask 2022.12 fixed
> #1025393, but there's a bootstrapping problem there...)
> 
> Does temporarily removing the build-dependency on python3-distributed work,
> or do we need a (temporary?) pandas without that Breaks?

This seems to be a sensible solution.  Feel free to go for it.

Kind regards

   Andreas.
 

-- 
http://fam-tille.de



Bug#1028912: Please build with C++20 to enable multi-symbol detection support for DataMatrix

2023-01-14 Thread Jakob Haufe
Source: zxing-cpp
Version: 1.4.0-3
Severity: wishlist
Tags: patch

In d6dc409ef15ff7171c7f9130dff7266a7c65f053[1], upstream implemented
detection for multiple DataMatrix symbols in a single input. As
mentioned in the commit message, this needs C++20.

Patch attached.

[1] 
https://github.com/zxing-cpp/zxing-cpp/commit/d6dc409ef15ff7171c7f9130dff7266a7c65f053

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

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



-- 
ceterum censeo microsoftem esse delendam.
From 3af7efcab6eef37182f8544a1c4618b1da242fa3 Mon Sep 17 00:00:00 2001
From: Jakob Haufe 
Date: Sat, 14 Jan 2023 21:02:49 +0100
Subject: [PATCH] Build with C++20

---
 debian/patches/0007-enable-c++20.patch | 15 +++
 debian/patches/series  |  1 +
 2 files changed, 16 insertions(+)
 create mode 100644 debian/patches/0007-enable-c++20.patch

diff --git a/debian/patches/0007-enable-c++20.patch b/debian/patches/0007-enable-c++20.patch
new file mode 100644
index 000..efd457f
--- /dev/null
+++ b/debian/patches/0007-enable-c++20.patch
@@ -0,0 +1,15 @@
+Description: Build with C++20
+Author: Jakob Haufe 
+Last-Update: 2023-01-14
+
+--- zxing-cpp-1.4.0.orig/CMakeLists.txt
 zxing-cpp-1.4.0/CMakeLists.txt
+@@ -43,7 +43,7 @@ if (BUILD_SHARED_LIBS)
+ set (CMAKE_WINDOWS_EXPORT_ALL_SYMBOLS ON)
+ endif()
+
+-set (CMAKE_CXX_STANDARD 17)
++set (CMAKE_CXX_STANDARD 20)
+ set (CMAKE_CXX_EXTENSIONS OFF)
+
+ if (NOT (BUILD_READERS OR BUILD_WRITERS))
diff --git a/debian/patches/series b/debian/patches/series
index 01506a0..c2859a6 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -3,3 +3,4 @@
 0004-Bump-SONAME-to-2.patch
 0005-test-update-to-libfmt-v9.0.0.patch
 0006-install-examples.patch
+0007-enable-c++20.patch
-- 
2.39.0



pgppA04EERVzy.pgp
Description: OpenPGP digital signature


Bug#1028911: gegl: FTBFS on mipsel: FAILED: docs/website/operations/images/gegl-oilify.png

2023-01-14 Thread Sebastian Ramacher
Source: gegl
Version: 1:0.4.40-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

https://buildd.debian.org/status/fetch.php?pkg=gegl=mipsel=1%3A0.4.40-1%2Bb1=1673697286=0

ok 175 - svg:src
ok 176 - gegl:subtract
ok 177 - svg:xor
not ok 178 - gegl:lens-blur 0dbbb05aa6bb17923afca177d7b35813 != 
c5dc4c97b0dacbe3fee41cefca1e6f42
not ok 179 - gegl:map-absolute (no ref) # TODO hash = 
f1b3ab0f1e84ec5882f23aee0a0c68f6
not ok 180 - gegl:map-relative 17cab1e3aa06a6d7a597c0ab98dfd820 != 
c662bb6323771333ee49f7a30638eb22
not ok 181 - gegl:matting-global (no ref) # TODO hash = 
72e111a28f07e2236d6378c3f64eaec3
not ok 182 - gegl:cast-space (noop) # TODO hash is noop
not ok 183 - gegl:convert-space (noop) # TODO hash is noop
ok 184 - gegl:crop
not ok 185 - gegl:matting-levin (no ref) # TODO hash = 
ad8719c0c19781a709110dbfe5209b3e
not ok 186 - gegl:seamless-clone (no ref) # TODO hash = 
0b5b377c61a19216c5d83d72d440bef6
ok 187 - gegl:oilify (ref b)
not ok 188 - gegl:remap (no ref) # TODO hash = 5c23950ebdae20c205a4f62685332915
not ok 189 - gegl:shadows-highlights (noop) # TODO hash is noop
ok 190 - gegl:focus-blur
ok 191 - gegl:variable-blur
ok 192 - gegl:bloom
ok 193 - gegl:color-assimilation-grid
ok 194 - gegl:difference-of-gaussians
ok 195 - gegl:dropshadow
ok 196 - gegl:gaussian-blur (ref b)
Segmentation fault
[848/850] /usr/bin/asciidoc --unsafe -o docs/website/index.html -a 
stylesheet=/<>/docs/gegl.css -a 'quirks!' ../docs/index.adoc
FAILED: docs/website/operations/images/gegl-oilify.png 
/usr/bin/env GEGL_SWAP=/<>/obj-mipsel-linux-gnu/RAM 
GEGL_PATH=/<>/obj-mipsel-linux-gnu/operations BABL_TOLERANCE=0.0 
/<>/obj-mipsel-linux-gnu/tools/gegl-tester --data-directory 
/<>/docs/images --output-directory docs/website/operations/images 
--all --exclusion-pattern 
'gegl:buffer-source|gegl:exr-load|gegl:ff-load|gegl:gegl-buffer-load|gegl:gif-load|gegl:icc-load|gegl:jp2-load|gegl:jpg-load|gegl:load|gegl:magick-load|gegl:open-buffer|gegl:pdf-load|gegl:pixbuf|gegl:png-load|gegl:ppm-load|gegl:rawbayer-load|gegl:raw-load|gegl:rgbe-load|gegl:svg-load|gegl:tiff-load|gegl:v4l|gegl:v4l2|gegl:webp-load|gegl:buffer-sink|gegl:display|gegl:exr-save|gegl:ff-save|gegl:gegl-buffer-save|gegl:icc-save|gegl:jpg-save|gegl:npy-save|gegl:png-save|gegl:ppm-save|gegl:rgbe-save|gegl:save|gegl:save-pixbuf|gegl:sdl2-display|gegl:tiff-save|gegl:webp-save|gegl:write-buffer|gegl:cache|gegl:cast-format|gegl:clone|gegl:convert-format|gegl:copy-buffer|gegl:image-compare|gegl:line-profile|gegl:nop|gegl:exp-combine|gegl:gegl|gegl:introspect|gegl:lcms-from-profile|gegl:mblur|gegl:alpha-inpaint|gegl:integral-image|gegl:aces-rrt'
ninja: build stopped: subcommand failed.


Cheers
-- 
Sebastian Ramacher



Bug#1028667: dask BD-Uninstallable

2023-01-14 Thread Rebecca N. Palmer

Control: retitle -1 dask: B-D on python-numpy-doc which no longer exists
Control: tags -1 pending

The python-numpy-doc error is because that package no longer exists. 
This build-dependency has already been removed in Salsa.


However, that version doesn't build the dask documentation due to other 
issues.  There's a version in my test PPA that I think does build the 
documentation, but I have *not* checked whether that documentation works 
(that PPA existed for checking whether the new dask + dask.distributed 
broke any of their reverse dependencies):

https://launchpad.net/~rebecca-palmer/+archive/ubuntu/dask2022p12v2/+packages



The python3-pandas error is because pandas now declares a Breaks: on 
dask (<= current) because of #1025393, and dask build-depends on 
python3-distributed and hence indirectly on itself.  (dask 2022.12 fixed 
#1025393, but there's a bootstrapping problem there...)


Does temporarily removing the build-dependency on python3-distributed 
work, or do we need a (temporary?) pandas without that Breaks?




Bug#1028748: bottleneck: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.11" returned exit code 13

2023-01-14 Thread Nilesh Patra
There is one hacky way to get this moving, and the package build with 
the patch. But not sure if it should be applied or not (as this is ugly)


I am not adding a patch tag for the same reason. Have also mentioned 
this as a comment in upstream issue.


--- a/bottleneck/slow/move.py
+++ b/bottleneck/slow/move.py
@@ -232,8 +232,9 @@
 # At least one dimension has length 0
 shape = list(a.shape)
 shape.pop(axis)
-r = np.empty(shape, dtype=a.dtype)
+r = np.empty(shape, dtype=float)
 r.fill(np.nan)
+r = r.astype(a.dtype)
 if (r.ndim == 0) and (r.size == 1):
 r = np.nan
 return r



Bug#1028475: Backport recent GVariant security fixes to Stable

2023-01-14 Thread Salvatore Bonaccorso
Hi Simon,

Thank you for adding looping in.

On Thu, Jan 12, 2023 at 10:10:35AM +, Simon McVittie wrote:
> Control: tags -1 + security
> 
> On Wed, 11 Jan 2023 at 16:37:01 +, Philip Withnall wrote:
> > Are there plans to backport the recent GVariant security fixes to
> > Debian Stable?
> > 
> > These are:
> >  - https://gitlab.gnome.org/GNOME/glib/-/issues/2782
> >  - https://gitlab.gnome.org/GNOME/glib/-/issues/2121
> >  - https://gitlab.gnome.org/GNOME/glib/-/issues/2540
> >  - https://gitlab.gnome.org/GNOME/glib/-/issues/2794
> >  - https://gitlab.gnome.org/GNOME/glib/-/issues/2797
> >  - https://gitlab.gnome.org/GNOME/glib/-/issues/2840
> >  - https://gitlab.gnome.org/GNOME/glib/-/issues/2841
> > 
> > In addition, these two issues have highly related fixes (which it’s
> > probably easiest to backport in the same tranche), but they are not
> > security issues:
> >  - https://gitlab.gnome.org/GNOME/glib/-/issues/2612
> >  - https://gitlab.gnome.org/GNOME/glib/-/issues/2839
> > 
> > Apologies if a decision has been deliberately taken to not backport
> > them, I don’t fully understand the criteria for what gets backported.
> 
> There are actually two sets of criteria for what gets backported to
> stable. If the Debian security team (Cc'd) thinks an issue is sufficiently
> serious to need a security advisory and an immediate release, then they
> prepare a security update, either doing the work themselves or coordinating
> with the package's maintainer for the actual code changes.
> 
> If the security team are not interested in an issue, but the package's
> maintainer thinks the issue needs a stable update, then the package's
> maintainer coordinates with the release team to get the change into the
> next stable point release, which happens once per 1-2 months.
> 
> I think these issues are all denial-of-service, which the security team
> usually treats as not sufficiently important for an advisory and an
> off-schedule fix. Security team: do you agree, based on the information
> quoted below? If yes, we can treat this as a low-priority security fix
> (I would personally rate its severity at somewhere between important
> and minor) and fix it in a point release later.

I do agree, a point release update seems enough (if feasible, in
backport size and confidence).

Regards,
Salvatore



Bug#1028910: libwlroots10: Invalid WLR_RENDERER value: "vulkan"

2023-01-14 Thread Jinesh Choksi
Package: libwlroots10
Version: 0.15.1-4
Severity: normal
X-Debbugs-Cc: jin...@onelittlehope.com

Dear Maintainer,

When setting an environment variable called WLR_RENDERER to the value "vulkan" 
and launching the sway window manager, I see the following error reported in 
sway's log file.

  [ERROR] [wlr] [render/wlr_renderer.c:293] Invalid WLR_RENDERER value: 'vulkan'

and sway then fails to start.

I believe this is happening since the wlroots library in Debian has not been
compiled with the vulkan renderer.

Would it be possible to have this renderer compiled in?

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

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

Versions of packages libwlroots10 depends on:
ii  libc62.36-7
ii  libdrm2  2.4.114-1
ii  libegl1  1.5.0-1
ii  libgbm1  22.3.2-1
ii  libgles2 1.5.0-1
ii  libinput10   1.22.0-1
ii  libpixman-1-00.42.2-1
ii  libseat1 0.7.0-6
ii  libudev1 252.4-1
ii  libwayland-client0   1.21.0-1
ii  libwayland-server0   1.21.0-1
ii  libxcb-composite01.15-1
ii  libxcb-dri3-01.15-1
ii  libxcb-icccm40.4.1-1.1
ii  libxcb-present0  1.15-1
ii  libxcb-render-util0  0.3.9-1+b1
ii  libxcb-render0   1.15-1
ii  libxcb-res0  1.15-1
ii  libxcb-shm0  1.15-1
ii  libxcb-xfixes0   1.15-1
ii  libxcb-xinput0   1.15-1
ii  libxcb1  1.15-1
ii  libxkbcommon01.4.1-1

libwlroots10 recommends no packages.

libwlroots10 suggests no packages.

-- no debconf information



Bug#1027143: openimageio: CVE-2022-43592 CVE-2022-43593 CVE-2022-43594 CVE-2022-43595 CVE-2022-43596 CVE-2022-43597 CVE-2022-43598 CVE-2022-43599 CVE-2022-43600 CVE-2022-43601 CVE-2022-43602 CVE-2022-

2023-01-14 Thread Bastian Germann

X-Debbugs-Cc: m...@debian.org

What is stopping this from being addresed? Importing the latest 2.3.x version
would fix at least some of the issues if 2.4 cannot be imported.



Bug#1028463: linux: enable MEI options for Intel ARC

2023-01-14 Thread Miguel Bernal Marin
Control: tags -1 + patch 

Dear Maintainer,

> In order to fully use Intel ARC GPUs, the following options need to get
> enabled:
> 
> CONFIG_INTEL_MEI_GSC
> CONFIG_INTEL_MEI_PXP
> CONFIG_DRM_I915_PXP
> 

Below is the description of the features requested:

# Intel MEI GSC embedded device

  CONFIG_INTEL_MEI_GSC=m

  The Intel Management Engine Interface (Intel MEI) auxiliary
  driver for Graphics System Controller (GSC) devices embedded
  in Intel graphics devices.

  An MEI device here called GSC can be embedded in an
  Intel graphics devices, to support a range of chassis
  tasks such as graphics card firmware update and security
  tasks.

# Intel PXP services of ME Interface

  CONFIG_INTEL_MEI_PXP=m

  MEI Support for Protected Xe Path (PXP) Services on Intel platforms.

  Enables the ME FW services required for PXP support through
  I915 display driver of Intel.

# Enable Intel PXP support

  CONFIG_DRM_I915_PXP=y

  PXP (Protected Xe Path) is an i915 component, available on graphics
  version 12 and newer GPUs, that helps to establish the hardware
  protected session and manage the status of the alive software session,
  as well as its life cycle.

And a MR was created at:

MR: https://salsa.debian.org/kernel-team/linux/-/merge_requests/633

Regards,
Miguel



Bug#1026204: tar FTBFS on armel, armhf, i386, hppa, powerpc and sparc64

2023-01-14 Thread Andreas Henriksson
Hello,

On Fri, Dec 16, 2022 at 09:13:44AM +0100, Helge Deller wrote:
> Package: tar
> Version: 1.34+dfsg-1.1
> Tags: hppa, patch, ftbfs, lfs
[...]
> I've found, that changing the line 12 in debian/rules from
> CPPFLAGS = `dpkg-buildflags --get CPPFLAGS`
> to:
> CPPFLAGS = `dpkg-buildflags --get CPPFLAGS` -D_LARGEFILE_SOURCE 
> -D_FILE_OFFSET_BITS=64 -D__USE_TIME_BITS64
> does solve the issue.
[...]

Thanks for identifying the solution already.
Here's a slightly different patch to implement basically the same thing
(and I can confirm it builds in an i386 chroot which previously failed).

(Note: The initial two lines in debian/rules could also be replaced by
`include /usr/share/dpkg/architecture.mk` for further slight modernization.)

Regards,
Andreas Henriksson

--- a/debian/rules  2023-01-14 19:20:32.572449385 +
+++ b/debian/rules  2023-01-14 19:19:02.745766528 +
@@ -6,10 +6,12 @@
 CONFARGS = --host=$(DEB_HOST_GNU_TYPE)
 endif
 
-CFLAGS = `dpkg-buildflags --get CFLAGS`
-CFLAGS += -Wall -Wno-analyzer-null-argument
-LDFLAGS += `dpkg-buildflags --get LDFLAGS`
-CPPFLAGS = `dpkg-buildflags --get CPPFLAGS`
+export DEB_BUILD_MAINT_OPTIONS = future=+lfs
+export DEB_CFLAGS_MAINT_APPEND = -Wall -Wno-analyzer-null-argument
+export DEB_CPPFLAGS_MAINT_APPEND = -D_TIME_BITS=64
+
+DPKG_EXPORT_BUILDFLAGS = 1
+include /usr/share/dpkg/buildflags.mk
 
 export BUILD_DATE = $(shell dpkg-parsechangelog | sed -n -e 's/^Date: //p')
 



Bug#1028517: tasksel: [INTL:tr] turkish translation update

2023-01-14 Thread Holger Wansing
Control: tags -1 + pending


Atila KOÇ  wrote (Thu, 12 Jan 2023 11:54:38 +0300):
> Package: tasksel
> Severity: wishlist
> Tags: l10n patch
> 
> Hello,
> 
> Attached is the updated Turkish translation of the tasksel debconf template.
> It has been submitted for review to the debian-l10n-turkish mailing list.
> Please include it in your next upload.

Committed into git.
Thanks


Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076



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

2023-01-14 Thread M. Zhou
Currently, I'd say PyTorch and TensorFlow are the two most
popular libraries. And I even worry google is trying to
write something new like Jax to replace TensorFlow in some aspects.

On Sat, 2023-01-14 at 11:12 +, Rebecca N. Palmer wrote:
> theano has been mostly abandoned upstream since 2018.  (The Aesara fork 
> is not abandoned, but includes interface changes including the import 
> name, so would break reverse dependencies not specifically altered for it.)
> 
> Its reverse dependencies are keras, deepnano and invesalius.
> 
> It is currently broken, probably by numpy 1.24 (#1027215), and the 
> immediately obvious fixes weren't enough 
> (https://salsa.debian.org/science-team/theano/-/pipelines).
> 
> Is this worth spending more effort on fixing, or should we just remove it?
> 



Bug#1028857: libpsl: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2

2023-01-14 Thread Tim Rühsen

Hey Lucas,

could you try with the latest release v0.21.2 ?

I am working on Debian sid, and can't reproduce the issue.

But I will examine the logs and/or try to build from the debian sources 
(in the next days).


Regards, Tim

On 14.01.23 13:59, Lucas Nussbaum wrote:

Source: libpsl
Version: 0.21.0-1.2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230113 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):

make[5]: Entering directory '/<>/tests'
PASS: test-is-public-builtin
PASS: test-registrable-domain
PASS: test-is-public
PASS: test-is-cookie-domain-acceptable
FAIL: test-is-public-all
=
libpsl 0.21.0: tests/test-suite.log
=

# TOTAL: 5
# PASS:  4
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: test-is-public-all


loaded 9458 suffixes and 8 exceptions
builtin PSL has 9458 suffixes and 8 exceptions
psl_is_public_suffix2(webview-assets.cloud9.ap-northeast-1.amazonaws.com, 
PSL_TYPE_PRIVATE)=0 (expected 1)
psl_is_public_suffix2(webview-assets.cloud9.ap-northeast-1.amazonaws.com, 
PSL_TYPE_PRIVATE|PSL_TYPE_NO_STAR_RULE)=0 (expected 1)
psl_is_public_suffix2(webview-assets.cloud9.ap-northeast-1.amazonaws.com, 
PSL_TYPE_ANY)=0 (expected 1)
psl_is_public_suffix2(webview-assets.cloud9.ap-northeast-1.amazonaws.com, 
PSL_TYPE_ANY|PSL_TYPE_NO_STAR_RULE)=0 (expected 1)
psl_is_public_suffix2(webview-assets.cloud9.ap-northeast-2.amazonaws.com, 
PSL_TYPE_PRIVATE)=0 (expected 1)
psl_is_public_suffix2(webview-assets.cloud9.ap-northeast-2.amazonaws.com, 
PSL_TYPE_PRIVATE|PSL_TYPE_NO_STAR_RULE)=0 (expected 1)
psl_is_public_suffix2(webview-assets.cloud9.ap-northeast-2.amazonaws.com, 
PSL_TYPE_ANY)=0 (expected 1)
psl_is_public_suffix2(webview-assets.cloud9.ap-northeast-2.amazonaws.com, 
PSL_TYPE_ANY|PSL_TYPE_NO_STAR_RULE)=0 (expected 1)
psl_is_public_suffix2(webview-assets.cloud9.ap-northeast-3.amazonaws.com, 
PSL_TYPE_PRIVATE)=0 (expected 1)
psl_is_public_suffix2(webview-assets.cloud9.ap-northeast-3.amazonaws.com, 
PSL_TYPE_PRIVATE|PSL_TYPE_NO_STAR_RULE)=0 (expected 1)
psl_is_public_suffix2(webview-assets.cloud9.ap-northeast-3.amazonaws.com, 
PSL_TYPE_ANY)=0 (expected 1)
psl_is_public_suffix2(webview-assets.cloud9.ap-northeast-3.amazonaws.com, 
PSL_TYPE_ANY|PSL_TYPE_NO_STAR_RULE)=0 (expected 1)
psl_is_public_suffix2(webview-assets.cloud9.ap-southeast-1.amazonaws.com, 
PSL_TYPE_PRIVATE)=0 (expected 1)
psl_is_public_suffix2(webview-assets.cloud9.ap-southeast-1.amazonaws.com, 
PSL_TYPE_PRIVATE|PSL_TYPE_NO_STAR_RULE)=0 (expected 1)
psl_is_public_suffix2(webview-assets.cloud9.ap-southeast-1.amazonaws.com, 
PSL_TYPE_ANY)=0 (expected 1)
psl_is_public_suffix2(webview-assets.cloud9.ap-southeast-1.amazonaws.com, 
PSL_TYPE_ANY|PSL_TYPE_NO_STAR_RULE)=0 (expected 1)
psl_is_public_suffix2(webview-assets.cloud9.ap-southeast-2.amazonaws.com, 
PSL_TYPE_PRIVATE)=0 (expected 1)
psl_is_public_suffix2(webview-assets.cloud9.ap-southeast-2.amazonaws.com, 
PSL_TYPE_PRIVATE|PSL_TYPE_NO_STAR_RULE)=0 (expected 1)
psl_is_public_suffix2(webview-assets.cloud9.ap-southeast-2.amazonaws.com, 
PSL_TYPE_ANY)=0 (expected 1)
psl_is_public_suffix2(webview-assets.cloud9.ap-southeast-2.amazonaws.com, 
PSL_TYPE_ANY|PSL_TYPE_NO_STAR_RULE)=0 (expected 1)
psl_is_public_suffix2(webview-assets.cloud9.ca-central-1.amazonaws.com, 
PSL_TYPE_PRIVATE)=0 (expected 1)
psl_is_public_suffix2(webview-assets.cloud9.ca-central-1.amazonaws.com, 
PSL_TYPE_PRIVATE|PSL_TYPE_NO_STAR_RULE)=0 (expected 1)
psl_is_public_suffix2(webview-assets.cloud9.ca-central-1.amazonaws.com, 
PSL_TYPE_ANY)=0 (expected 1)
psl_is_public_suffix2(webview-assets.cloud9.ca-central-1.amazonaws.com, 
PSL_TYPE_ANY|PSL_TYPE_NO_STAR_RULE)=0 (expected 1)
psl_is_public_suffix2(webview-assets.cloud9.eu-central-1.amazonaws.com, 
PSL_TYPE_PRIVATE)=0 (expected 1)
psl_is_public_suffix2(webview-assets.cloud9.eu-central-1.amazonaws.com, 
PSL_TYPE_PRIVATE|PSL_TYPE_NO_STAR_RULE)=0 (expected 1)
psl_is_public_suffix2(webview-assets.cloud9.eu-central-1.amazonaws.com, 
PSL_TYPE_ANY)=0 (expected 1)
psl_is_public_suffix2(webview-assets.cloud9.eu-central-1.amazonaws.com, 
PSL_TYPE_ANY|PSL_TYPE_NO_STAR_RULE)=0 (expected 1)
Summary: 28 out of 290640 tests failed
FAIL test-is-public-all (exit status: 1)


Testsuite summary for libpsl 0.21.0

# TOTAL: 5
# PASS:  4
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See tests/test-suite.log
Please report to tim.rueh...@gmx.de

make[5]: *** [Makefile:802: test-suite.log] Error 1
make[5]: Leaving 

Bug#1028909: /usr/bin/ozwcp: localhost:8090 returns 200, File not found: cp.html

2023-01-14 Thread Witold Baryluk
Package: openzwave-controlpanel
Version: 1.6~git20200306.4b8a39d-1
Severity: important
File: /usr/bin/ozwcp
X-Debbugs-Cc: witold.bary...@gmail.com

Probably some system paths not set up correctly

user@debian:~$ ozwcp
2023-01-14 18:57:38.439 Error, Cannot find a path to the configuration files at 
./config/, Using /etc/openzwave/ instead...
2023-01-14 18:57:38.439 Info, Reading /etc/openzwave/options.xml for Options
2023-01-14 18:57:38.439 Warning, Failed to Parse options.xml: Failed to open 
file
2023-01-14 18:57:38.439 Info, Options:
2023-01-14 18:57:38.439 Info,   appendlogfile: false
2023-01-14 18:57:38.439 Info,   associate: true
2023-01-14 18:57:38.439 Info,   assumeawake: true
2023-01-14 18:57:38.439 Info,   autoupdateconfigfile: true
2023-01-14 18:57:38.440 Info,   configpath: /etc/openzwave/
2023-01-14 18:57:38.440 Info,   consoleoutput: true
2023-01-14 18:57:38.440 Info,   customsecuredcc: 0x62,0x4c,0x63
2023-01-14 18:57:38.440 Info,   drivermaxattempts: 5
2023-01-14 18:57:38.440 Info,   dumptriggerlevel: 1
2023-01-14 18:57:38.440 Info,   enablesis: true
2023-01-14 18:57:38.440 Info,   enforcesecurereception: true
2023-01-14 18:57:38.440 Info,   exclude: 
2023-01-14 18:57:38.440 Info,   include: 
2023-01-14 18:57:38.440 Info,   includeinstancelabel: true
2023-01-14 18:57:38.440 Info,   interface: 
2023-01-14 18:57:38.440 Info,   intervalbetweenpolls: false
2023-01-14 18:57:38.440 Info,   language: 
2023-01-14 18:57:38.440 Info,   logfilename: OZW_Log.txt
2023-01-14 18:57:38.440 Info,   logging: true
2023-01-14 18:57:38.440 Info,   networkkey: 
2023-01-14 18:57:38.440 Info,   notifyondriverunload: false
2023-01-14 18:57:38.440 Info,   notifytransactions: false
2023-01-14 18:57:38.440 Info,   performreturnroutes: false
2023-01-14 18:57:38.440 Info,   pollinterval: 3
2023-01-14 18:57:38.440 Info,   queueloglevel: 9
2023-01-14 18:57:38.440 Info,   refreshallusercodes: false
2023-01-14 18:57:38.440 Info,   reloadafterupdate: AWAKE
2023-01-14 18:57:38.440 Info,   retrytimeout: 1
2023-01-14 18:57:38.440 Info,   saveconfiguration: true
2023-01-14 18:57:38.440 Info,   saveloglevel: 8
2023-01-14 18:57:38.440 Info,   securitystrategy: SUPPORTED
2023-01-14 18:57:38.440 Info,   suppressvaluerefresh: false
2023-01-14 18:57:38.440 Info,   userpath: 
2023-01-14 18:57:38.440 Always, OpenZwave Version  Starting Up
2023-01-14 18:57:38.445 Info, Loading Localization File 
/etc/openzwave/Localization.xml
2023-01-14 18:57:38.446 Info, Loaded /etc/openzwave/Localization.xml With 
Revision 12
2023-01-14 18:57:38.446 Always, Using Language Localization 
2023-01-14 18:57:38.447 Info, Loading NotificationCCTypes File 
/etc/openzwave/NotificationCCTypes.xml
2023-01-14 18:57:38.447 Info, Loaded /etc/openzwave/NotificationCCTypes.xml 
With Revision 11
2023-01-14 18:57:38.448 Info, Loading SensorMultiLevelCCTypes File 
/etc/openzwave/SensorMultiLevelCCTypes.xml
2023-01-14 18:57:38.448 Info, Loaded /etc/openzwave/SensorMultiLevelCCTypes.xml 
With Revision 4
webserver starting port 8090
Warning: MHD_USE_THREAD_PER_CONNECTION must be used only with 
MHD_USE_INTERNAL_POLLING_THREAD. Flag MHD_USE_INTERNAL_POLLING_THREAD was 
added. Consider setting MHD_USE_INTERNAL_POLLING_THREAD explicitly.
^C




$ curl --output - -v http://localhost:8090/
*   Trying 127.0.0.1:8090...
* Connected to localhost (127.0.0.1) port 8090 (#0)
> GET / HTTP/1.1
> Host: localhost:8090
> User-Agent: curl/7.87.0
> Accept: */*
> 
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Date: Sat, 14 Jan 2023 18:58:54 GMT
< Content-Length: 92
< 
* Connection #0 to host localhost left intact
File not foundFile not found: 
cp.html


Additionally wrong HTTP status code is retured (should be 404), and wrong
Content-Type (missing, which makes it look like binary, but should be
text/html).


If I strace the ozwcp and do a HTTP request I got this:

[pid 3353605] pselect6(7, [6], [], [], NULL, NULL) = 1 (in [6])
[pid 3353605] recvfrom(6, "GET / HTTP/1.1\r\nHost: localhost:"..., 16384, 0, 
NULL, NULL) = 442
[pid 3353605] newfstatat(AT_FDCWD, "cp.html", 0x7fec321ab730, 0) = -1 ENOENT 
(No such file or directory)
[pid 3353605] sendmsg(6, {msg_name=NULL, msg_namelen=0, 
msg_iov=[{iov_base="HTTP/1.1 200 OK\r\nDate: Sat, 14 J"..., iov_len=76}, 
{iov_base="File not foun"..., iov_len=92}], msg_iovlen=2, 
msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 168


Indicating to me it is looking at cp.html in the current working directory, 
which is wrong.



If I cd into /usr/share/openzwave-controlpanel, and then start ozwcp, it
does load the main page, but Firefox console shows that there is number
of missing components (404 errors):


GET http://localhost:8090/cp.js  404 Not Found
GET http://localhost:8090/javascript/bootstrap/css/bootstrap.min.css  404 Not 
Found
GET http://localhost:8090/javascript/jquery/jquery.min.js  404 Not Found
GET http://localhost:8090/javascript/bootstrap/js/bootstrap.min.js  404 Not 
Found
GET 

Bug#1027283: transition: tiff

2023-01-14 Thread Sebastian Ramacher
On 2023-01-13 21:39:10 +0100, Sebastiaan Couwenberg wrote:
> Please also binNMU grass in experimental.

Done

Cheers
-- 
Sebastian Ramacher



Bug#1028908: python3-pynndescent: "import pynndescent.sparse as sparse" results in error

2023-01-14 Thread Jörg-Volker Peetz

Package: python3-pynndescent
Version: 0.5.7-1
Severity: serious

Dear Debian Python Team,

in the python3 or ipython3 interpreter, the Python statement

   import pynndescent.sparse as sparse

fails and the output in ipython3 is
```
---
TypingError   Traceback (most recent call last)
Cell In [1], line 1
> 1 import pynndescent.sparse as sparse

File /usr/lib/python3/dist-packages/pynndescent/__init__.py:3
  1 import pkg_resources
  2 import numba
> 3 from .pynndescent_ import NNDescent, PyNNDescentTransformer
  5 # Workaround: https://github.com/numba/numba/issues/3341
  6 if numba.config.THREADING_LAYER == "omp":

File /usr/lib/python3/dist-packages/pynndescent/pynndescent_.py:16
 12 from scipy.sparse import csr_matrix, coo_matrix, isspmatrix_csr, vstack
as sparse_vstack, issparse
 14 import heapq
---> 16 import pynndescent.sparse as sparse
 17 import pynndescent.sparse_nndescent as sparse_nnd
 18 import pynndescent.distances as pynnd_dist

File /usr/lib/python3/dist-packages/pynndescent/sparse.py:381
377 result += aux_data[i] ** 2
378 return np.sqrt(result)
--> 381 @numba.njit(
382 [
383 "f4(i4[::1],f4[::1],i4[::1],f4[::1])",
384 numba.types.float32(
385 numba.types.Array(numba.types.int32, 1, "C", readonly=True),
386 numba.types.Array(numba.types.float32, 1, "C", 
readonly=True),
387 numba.types.Array(numba.types.int32, 1, "C", readonly=True),
388 numba.types.Array(numba.types.float32, 1, "C", 
readonly=True),
389 ),
390 ],
391 fastmath=True,
392 locals={
393 "aux_data": numba.types.float32[::1],
394 "result": numba.types.float32,
395 "diff": numba.types.float32,
396 "dim": numba.types.intp,
397 "i": numba.types.uint16,
398 },
399 )
400 def sparse_squared_euclidean(ind1, data1, ind2, data2):
401 _, aux_data = sparse_diff(ind1, data1, ind2, data2)
402 result = 0.0

File /usr/lib/python3/dist-packages/numba/core/decorators.py:219, in
_jit..wrapper(func)
217 with typeinfer.register_dispatcher(disp):
218 for sig in sigs:
--> 219 disp.compile(sig)
220 disp.disable_compile()
221 return disp

File /usr/lib/python3/dist-packages/numba/core/dispatcher.py:965, in
Dispatcher.compile(self, sig)
963 with ev.trigger_event("numba:compile", data=ev_details):
964 try:
--> 965 cres = self._compiler.compile(args, return_type)
966 except errors.ForceLiteralArg as e:
967 def folded(args, kws):

File /usr/lib/python3/dist-packages/numba/core/dispatcher.py:129, in
_FunctionCompiler.compile(self, args, return_type)
127 return retval
128 else:
--> 129 raise retval

File /usr/lib/python3/dist-packages/numba/core/dispatcher.py:139, in
_FunctionCompiler._compile_cached(self, args, return_type)
136 pass
138 try:
--> 139 retval = self._compile_core(args, return_type)
140 except errors.TypingError as e:
141 self._failed_cache[key] = e

File /usr/lib/python3/dist-packages/numba/core/dispatcher.py:152, in
_FunctionCompiler._compile_core(self, args, return_type)
149 flags = self._customize_flags(flags)
151 impl = self._get_implementation(args, {})
--> 152 cres = compiler.compile_extra(self.targetdescr.typing_context,
153   self.targetdescr.target_context,
154   impl,
155   args=args, return_type=return_type,
156   flags=flags, locals=self.locals,
157   pipeline_class=self.pipeline_class)
158 # Check typing error if object mode is used
159 if cres.typing_error is not None and not flags.enable_pyobject:

File /usr/lib/python3/dist-packages/numba/core/compiler.py:716, in
compile_extra(typingctx, targetctx, func, args, return_type, flags, locals,
library, pipeline_class)
692 """Compiler entry point
693
694 Parameter
   (...)
712 compiler pipeline
713 """
714 pipeline = pipeline_class(typingctx, targetctx, library,
715   args, return_type, flags, locals)
--> 716 return pipeline.compile_extra(func)

File /usr/lib/python3/dist-packages/numba/core/compiler.py:452, in
CompilerBase.compile_extra(self, func)
450 self.state.lifted = ()
451 self.state.lifted_from = None
--> 452 return self._compile_bytecode()

File /usr/lib/python3/dist-packages/numba/core/compiler.py:520, in
CompilerBase._compile_bytecode(self)
516 """
517 Populate and run pipeline for bytecode input
518 """
519 assert self.state.func_ir is None
--> 520 return self._compile_core()

File 

Bug#1010608: openldap: Flaky test test063-delta-multiprovider

2023-01-14 Thread Ryan Tandy

Control: severity -1 important

On Wed, Dec 28, 2022 at 10:32:30PM +0100, Paul Gevers wrote:
Then not running the script at all is an improvement over the current 
situation. Flaky tests are bad. Until a better solution is found, how 
about skipping the test?


I have uploaded -3 with the flaky test disabled. I'm downgrading the 
bug, but not closing it right now - I'm still optimistic about finding a 
proper solution (likely not for bookworm, though).




Bug#1028251: New Patch (Was: Re: Bug#1028251: xen: FTBFS when building xen binary packages for sid on x86_64)

2023-01-14 Thread Chuck Zmudzinski
On 1/13/2023 9:08 PM, Chuck Zmudzinski wrote:
> On 1/13/23 6:59 PM, Hans van Kranenburg wrote:
> > Hi,
> > 
> > On 1/13/23 22:45, Chuck Zmudzinski wrote:
> >> On 1/13/23 7:39 AM, Marek Marczykowski-Górecki wrote:
> >>> On Fri, Jan 13, 2023 at 12:58:29AM -0500, Chuck Zmudzinski wrote:
>  On 1/11/2023 10:58 PM, Chuck Zmudzinski wrote:
> > On 1/9/23 12:55 PM, Hans van Kranenburg wrote:
> >> Hi!
> > [...]
> > Yolo style cutting out lines here...
> > [...]
> 
>
> >> 
> >> Perhaps this is an opportunity for you to try to fix 922033 again.
> >> I see it has been sitting there for a few years now. Let's see
> >> what Hans thinks.
> > 
> > Yeah, well, so, the thing here is...
> > 
> > When Debian started to package Xen (thanks! Bastian, in 200X), the
> > upstream init scripts were copy pasted, and adjusted to have the ability
> > to have different Hypervisor-ABI-incompatible versions installed at the
> > same time. Also, this is related to the collection of Makefile patches
> > we carry around to have ABI-incompatible stuff end up in a directory
> > like /usr/lib/xen-4.14/ and /usr/lib/xen-4.17/ !
>
> That is a nice feature of the Xen Debian packages, to have the ability
> to manage guests on different versions of the hypervisor.
>
> > 
> > What does this mean? Well, in the most basic sense it means that you
> > could apt-get (dist-)upgrade and then still be able to xl shutdown a
> > domU afterwards before doing reboot, because it will choose the right
> > tools which match with the ABI of the *now* running hypervisor instead
> > of being left with a dumpster fire, which in the end causes you to shout
> > curse words and cause you to have to go to the machine and hold the
> > power button for 5 seconds to force power it off.
> > 
> > This is the thing about where you upgrade from Xen 4.14 to Xen 4.17
> > during the upgrade from Debian 11/Bullseye to Debian 12/Bookworm, it
> > will allow you, if booting the whole new thing is a huge failure, to
> > reset the computer, and in grub, choose to use the previous Xen (and
> > possibly do that in combination with previous Debian linux kernel) and
> > then have a system where you again at least can start your domUs again
> > *) and first have a good rest, night of sleep before starting to dig
> > into what's going wrong.
> > 
> > So, this is exactly the same way of doing stuff like how you can also
> > reboot back into the previous Linux kernel (ABI-compatible) one during a
> > system upgrade, even if you're not using Xen at all!
> > 
> > I like this very much. This is the kind of thing that helps admins of
> > systems that have just local disks and a few domUs. Like, the case where
> > you support some non-profit organization with their server stuff running
> > on donated hardware. (Yes, I also do some of those, I do!) And, in case
> > something does fail (there could always be something like a misbehaving
> > mpt3sas card in the hardware or anything that no one else spotted yet),
> > the admin does not have to end up in total panic mode after doing the
> > upgrade on a Friday afternoon lying upside down inside a broom closet,
> > but they can just at least recover from the situation and have something
> > that's running again, and then a day later, or 2 or 3 days or a week
> > later return on another planned moment to fix it, after asking around.
> > 
> > Upstream Xen stuff doesn't have anything like that.
> > 
> > But, they actually look at us, and they think, ooh, this is actually
> > nice, we should have that also by default.
> > 
> > The fact that we have this changed/altered/divergent init scripts in
> > Debian is the main reason that we cannot just enable systemd things
> > which will put upstream whatever on the system.
>
> I understand the problem here.
>
> > 
> > So, what could we do about this?
> > 
> > The project plan (that could be drafted on an A4 paper) could look like,
> > gather around all distro maintainers of Linux distro's that are shipping
> > Xen, and then search for a 'Project owner', which we totally need to be
> > someone that is actually employed at a company that actually cares about
> > getting the results of this.

"Totally need to be someone that is actually employed at a company." I am 
curious
about that statement. Has Debian given up on the idea that members of the FLOSS
community can band together and solve a problem like this without corporate
backing? I don't think other distros have given up on that idea: For example, 
Fedora has
its community spins, a KDE spin, for example. Perhaps a Xen spin at Fedora 
could lead
this project. But why not Debian, with all it's derivative distros pitching in 
to help? I think
maybe the conclusion to draw from the statement that it has to be someone 
actually
employed at a company really means there is not enough community for support for
Xen to do this, Xen just is not a very big priority for the larger FLOSS 
community any
more. AFAIK, Qubes is the only project downstream of Xen that 

Bug#1028897: fontconfig-config: default latin fonts changed from DejaVu to Noto

2023-01-14 Thread Raphaël Halimi

reassign -1 fontconfig
merge -1 1028643
tags -1 patch
thanks

Sorry, I checked the bugs reported against fontconfig-config before 
filing this one, I didn't think to check fontconfig also.


If you wish to keep DejaVu as default, here is a simple patch to do that.

Regards,

--
Raphaël HalimiDescription: Keep DejaVu fonts as default for latin languages
 With Fontconfig 2.14, upstream made the Noto fonts the default for serif,
 sans-serif and monospace families for latin languages. This patch simply
 undoes this change.
Author: Raphaël Halimi 
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028897
Forwarded: not-needed
Last-Update: 2023-01-14
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
--- a/conf.d/60-latin.conf
+++ b/conf.d/60-latin.conf
@@ -5,8 +5,8 @@
 	
 		serif
 		
-			Noto Serif
 			DejaVu Serif
+			Noto Serif
 			Times New Roman
 			Thorndale AMT
 			Luxi Serif
@@ -18,8 +18,8 @@
 	
 		sans-serif
 		
-			Noto Sans
 			DejaVu Sans
+			Noto Sans
 			Verdana
 			Arial
 			Albany AMT
@@ -35,8 +35,8 @@
 	
 		monospace
 		
-			Noto Sans Mono
 			DejaVu Sans Mono
+			Noto Sans Mono
 			Inconsolata
 			Andale Mono
 			Courier New


Bug#1028907: cryptsetup: initramfs hook can't handle xchacha20,aes-adantium-plain64

2023-01-14 Thread Łukasz Stelmach
Package: cryptsetup
Version: 2:2.3.7-1+deb11u1
Severity: normal
X-Debbugs-Cc: Łukasz Stelmach 

Dear Maintainer,

The populate_CRYPTO_MODULES() function in
/usr/share/initramfs-tools/hooks/cryptroot can't properly derive
required module names (MODULES=dep in initramfs.conf) from dmsetup
ouptput when using adantium[1] encryption. In such cases the cipher string
is:

xchacha20,aes-adantium-plain64

(or xchacha12 on even less performant platforms). 

Workaround: manually add the following modules to
/etc/initramfs-tools/modules:

aes_generic
chacha_generic
nhpoly1350
xts

[1] https://lwn.net/Articles/776721/

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

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

Versions of packages cryptsetup depends on:
ii  cryptsetup-bin 2:2.3.7-1+deb11u1
ii  debconf [debconf-2.0]  1.5.77
ii  dmsetup2:1.02.175-2.1
ii  libc6  2.31-13+deb11u5

Versions of packages cryptsetup recommends:
ii  cryptsetup-initramfs  2:2.3.7-1+deb11u1
ii  cryptsetup-run2:2.3.7-1+deb11u1

Versions of packages cryptsetup suggests:
ii  dosfstools  4.2-1
ii  keyutils1.6.1-2
ii  liblocale-gettext-perl  1.07-4+b1

-- debconf information:
  cryptsetup/prerm_active_mappings: true

-- 
Miłego dnia,
Łukasz Stelmach


signature.asc
Description: PGP signature


Bug#1020576: This implies uninstallable

2023-01-14 Thread Joachim Zobel
Hi.

Not sure if I am saying something new here, you are aware that the
dependendcy on libgap7 implies that sagemath is no longer installable
now. gap-core now provides libgap8.

Sincerely,
Joachim

-- 
   Papier ist gebundenes CO2. Bitte drucken Sie diese EMail aus und
archivieren Sie sie.



Bug#1026927: More analysis and improved patch

2023-01-14 Thread George Robbert
Hey,

I think I found why you still get the error after applying the patch.
The same thing happened to me on another of my systems.  The
difference was whether the package amd64-microcode was installed or
not.  I think I have a patch (attached) for both.  Here's what I found.



It looks like there are actually 2 related bugs here.  The first one
(which my original patch for line 182 addresses) applies when there is
microcode available.  The second, when there is not.  Here's what I've
found:

Both of these are exposed on line 904 of /usr/sbin/needrestart

print "NEEDRESTART-UCEXP: $ucode_vars{AVAIL}\n";

when $ucode_vars{AVAIL} never gets set.  There are 2 ways this can
happen.  The second (which I just found), comes when AMD.pm finds an
AMD cpu, but does not find microcode for it (namely _scan_ucodes does
not find a matching file in /lib/firmware/amd-ucode/microcode_*.bin).
This will, under -v, print

"$LOGPREF #$info->{processor} no ucode updates available\n"

and return NRM_CURRENT (indicating no reboot for microcode needed),
but still leave $ucode_vars{AVAIL} unset.  The fix is to make sure
that it is set even when there are no microcode updates available (on
line 176).


The first (original patch) bug comes when needrestart finds a matching
microcode.  There, on line 182 of /usr/share/perl5/NeedRestart/uCode/AMD.pm
the line ends with a comma (,) instead of a semicolon (;), which means
that the assignment to $ucode_vars{AVAIL} is subsumed under the if ($debug)
condoling the printing of microcode version under.  Thus,
$ucode_vars{AVAIL} is only set under needrestart -v.


The attached patch fixes both of these cases.

Thanks,
George

--- /tmp/AMD.pm 2023-01-14 09:09:28.324414456 -0700
+++ /usr/share/perl5/NeedRestart/uCode/AMD.pm   2023-01-14 09:11:39.210705528 
-0700
@@ -173,13 +173,13 @@
 _scan_ucodes();
 }
 
-my %vars = ( CURRENT => sprintf( "0x%08x", $ucode ), );
+my %vars = ( CURRENT => sprintf( "0x%08x", $ucode ), AVAIL => 
"unavailable");
 
 # check for microcode updates
 if ( exists( $_ucodes->{cpuid}->{$cpuid} ) ) {
 my $prid = $_ucodes->{cpuid}->{$cpuid};
 if ( exists( $_ucodes->{prid}->{$prid} ) ) {
-$vars{AVAIL} = sprintf( "0x%08x", $_ucodes->{prid}->{$prid} ),
+$vars{AVAIL} = sprintf( "0x%08x", $_ucodes->{prid}->{$prid} );
 
   print STDERR "$LOGPREF #$info->{processor} found ucode 
$vars{AVAIL}\n" if ($debug);
 if ( $_ucodes->{prid}->{$prid} > $ucode ) {


Bug#1028904: pillow: Lost tiff support after binNMU with tiff 4.5.0

2023-01-14 Thread Sebastiaan Couwenberg

On 1/14/23 18:57, Sebastiaan Couwenberg wrote:

On 1/14/23 18:27, Bas Couwenberg wrote:
python3-pil lost the libtiff dependency after the recent rebuild 
during the transition to tiff 4.5.0:


The attached patch resolves the issue by adding support for the tiff.h 
multiarch path.


The initial patch uses the DEB_HOST_MULTIARCH environment variable.

The attached patch uses sysconfig.get_config_var('MULTIARCH') which 
seems more appropriate for upstreaming:


 https://github.com/python-pillow/Pillow/pull/6896

Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1
Description: Add support for tiff.h in multiarch path.
Author: Bas Couwenberg 
Bug-Debian: https://bugs.debian.org/1028904

--- a/setup.py
+++ b/setup.py
@@ -16,6 +16,7 @@ import re
 import struct
 import subprocess
 import sys
+import sysconfig
 import warnings
 
 from setuptools import Extension, setup
@@ -733,6 +734,14 @@ class pil_build_ext(build_ext):
 
 if feature.want("tiff"):
 _dbg("Looking for tiff")
+
+multiarch = sysconfig.get_config_var('MULTIARCH')
+if multiarch is not None:
+_add_directory(
+self.compiler.include_dirs,
+'/usr/include/%s' % multiarch,
+)
+
 if _find_include_file(self, "tiff.h"):
 if _find_library_file(self, "tiff"):
 feature.tiff = "tiff"


Bug#1020248: marked as done (debian-policy: Clarifying nomenclature for control file names)

2023-01-14 Thread Guillem Jover
Hi!

On Sat, 2022-12-17 at 17:24:57 -0700, Sean Whitton wrote:
> On Sat 17 Dec 2022 at 04:43PM +01, Guillem Jover wrote:
> > Sorry, probably my fault! As I tend to use «Fixes:» git pseudo-fields
> > for things that fix part of a bug, but are not intended yet to close it,
> > for which I use «Closes:».
> >
> > And for some reason I think I also got the impression, even though
> > the stanza changes had been committed, they could still be backed out.
> > (BTW I've now gone over the wiki and updated all paragraph references
> > that applied to stanza.)
> >
> > In any case, I've sat down and gone over the meat of the original
> > report. See below.
>·
> We're sticking with 'stanza', and in light of that, could you confirm
> that the bug is reopened in order to make additional fixes, rather than
> back anything else out?

In case my other replies to Russ didn't make this clear. This comment
was in reference to the various replies in the sub-thread started by
Charles, where it looked to me like whether to back that out was still
an open question for the editors.

In any case, as I mentioned, given the changes being included in the
release, I took that as indeed, sticking with the term, and that's why
I reopened and submitted the actual changes this original report was
intending on requesting. :)

As an aside I've since updated the dpkg code and docs to refer to
these as stanzas everywhere applicable.

Thanks,
Guillem



Bug#1028906: RM: olla -- ROM; not updated in a while, no longer a good idea

2023-01-14 Thread Paul R. Tagliamonte
Package: ftp.debian.org
Severity: normal

I wrote olla to allow short names when addressing hosts by overloading
getaddrinfo. Lately, this seems like a bad idea, since anything that
lets you get away with this is something that isn't checking the
peer's identity (ok; not true for SSH but for the general case)

I don't think many people used this, it's only in experimental, so I
say we trim it.

paultag

-- 
:wq



Bug#967941: Bug appeared again

2023-01-14 Thread Stephan Verbücheln
This bug appears back some time ago. For some months, video thumbnails
failed to generate on multiple of my machines. Since then, I was trying
to figure out the cause.

It only seemed to affect h264, but not all videos were affected. I even
had multiple videos saved from Youtube, some were generating
thumbnails, others were not. I could not find any difference in the
codec parameters.

Adding the -l option in /usr/share/thumbnailers/totem.thumbnailer
worked to prevent this bug. Does this option have any downsides?

Regards


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


Bug#1028904: pillow: Lost tiff support after binNMU with tiff 4.5.0

2023-01-14 Thread Sebastiaan Couwenberg

Control: tags -1 patch

On 1/14/23 18:27, Bas Couwenberg wrote:

python3-pil lost the libtiff dependency after the recent rebuild during the 
transition to tiff 4.5.0:


The attached patch resolves the issue by adding support for the tiff.h 
multiarch path.


Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1
diff -Nru pillow-9.4.0/debian/changelog pillow-9.4.0/debian/changelog
--- pillow-9.4.0/debian/changelog   2023-01-03 09:06:46.0 +
+++ pillow-9.4.0/debian/changelog   2023-01-14 17:52:49.0 +
@@ -1,3 +1,11 @@
+pillow (9.4.0-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Add patch to support tiff.h multiarch path.
+(closes: #1028904)
+
+ -- Bas Couwenberg   Sat, 14 Jan 2023 17:52:49 +
+
 pillow (9.4.0-1) unstable; urgency=medium
 
   * New upstream version.
diff -Nru pillow-9.4.0/debian/patches/series pillow-9.4.0/debian/patches/series
--- pillow-9.4.0/debian/patches/series  2022-10-21 15:53:14.0 +
+++ pillow-9.4.0/debian/patches/series  2023-01-14 17:50:49.0 +
@@ -4,3 +4,4 @@
 no-sphinx-removed-in.diff
 no-sphinx-opengraph.diff
 no-sphinx-furo.diff
+tiff-4.5.0.patch
diff -Nru pillow-9.4.0/debian/patches/tiff-4.5.0.patch 
pillow-9.4.0/debian/patches/tiff-4.5.0.patch
--- pillow-9.4.0/debian/patches/tiff-4.5.0.patch1970-01-01 
00:00:00.0 +
+++ pillow-9.4.0/debian/patches/tiff-4.5.0.patch2023-01-14 
17:52:48.0 +
@@ -0,0 +1,20 @@
+Description: Add support for tiff.h in multiarch path.
+Author: Bas Couwenberg 
+Bug-Debian: https://bugs.debian.org/1028904
+
+--- a/setup.py
 b/setup.py
+@@ -733,6 +733,13 @@ class pil_build_ext(build_ext):
+ 
+ if feature.want("tiff"):
+ _dbg("Looking for tiff")
++
++if 'DEB_HOST_MULTIARCH' in os.environ:
++_add_directory(
++self.compiler.include_dirs,
++'/usr/include/%s' % os.environ['DEB_HOST_MULTIARCH'],
++)
++
+ if _find_include_file(self, "tiff.h"):
+ if _find_library_file(self, "tiff"):
+ feature.tiff = "tiff"


Bug#1028325: (no subject)

2023-01-14 Thread William Desportes

I also found this package on my QA dashboard: 
https://debian.dashboard.air-balloon.cloud/en/dashboard-ftp-rm-candidates


Last upload: 2013-05-29

List of checks (source code: 
https://github.com/air-balloon/debian-dashboard#qa-report ):

- [ ] Debian copyright file uses DEP-5 format
- [x] Has FTBFS bugs
- [ ] No d/watch file
- [ ] No d/copyright file
- [ ] No reverse dependencies
- [x] Missing autopkgtests
- [x] Standards are outdated
- [!] Outdated version in Debian
- [x] Debian watch file has an error (!)
- [ ] Missing build tests
- [ ] Missing Debian Vcs-* fields
- [x] Broken Vcs target
- [x] Not maintained
- [x] Upstream provides tests
- [ ] Found on GitLab salsa
- [x] Not in testing
- [x] Not in stable
- [x] Not in experimental

Informations reported:

- Dependent: libreoffice-canzeley-client on jessie from debian
- Vcs error: brz: ERROR: Not a branch: 
"nosmart+http://anonscm.debian.org/bzr/users/vorlon/myodbc/trunk/;.

Package bugs:

- #[250850][1] (libautomatic adding as odbc driver should default to yes)
- #[409447][2] (libInitial connection parameters)
- #[415401][3] (Handling of ints on 64bit systems differ from other ODBC 
drivers in Debian)
- #[598781][4] (libfailure in SQLDriverConnect)
- #[598787][5] (libFailure in SQLDriverConnect)
- #[647932][6] (Support dpkg-preconfigure(8), like other ODBC driver packages)
- #[658377][7] (libSQLPrimaryKeys broken, fixed in upstream)
- #[680412][8] (Error in my_thread_global_end: x threads didn't exit (MySQL bug 
#57727))
- #[712427][9] (libOut-of-bounds read in sqlchar_as_sqlwchar) [status-Closed]
- #[714236][10] (libsimple test crashes)
- #[721120][11] (libcolumn names don't follow charset setting)
- #[737221][12] ([INTL:it] Italian translation of debconf messages)
- #[770952][13] (libWrong error SQLSTATE on MySQL Server GONE)
- #[835166][14] (libSIGFPE, Arithmetic exception in sqlchar_as_sqlwchar)
- #[841561][15] (FTBFS: stringutil.c:71:29: error: too few arguments to 
function 'my_malloc') [ftbfs,qa-ftbfs,qa-ftbfs-20161021]
- #[846641][16] (need out-of-date due missing unicode? upgrade to 5.2 brand or 
5.3)
- #[849630][17] (libPrograms using it fails with floating point exeption, then 
connects to mariadb)
- #[852457][18] (switch to build depend on the metapackage 
default-libmysqlclient-dev) [default-mysql,edos-uninstallable,piuparts]
- #[868882][19] (libThe package is not installable in Sid due to missing 
libmysqlclient18 dependency)
- #[945992][20] (libmissing "libmyodbc" package, which is suggested by 
"unixodbc")
- #[1028325][21] (RM: myodbc -- RoQA, unmaintained, FTBFS since years) 
[rm-proposal]

[1]: https://bugs.debian.org/250850
[2]: https://bugs.debian.org/409447
[3]: https://bugs.debian.org/415401
[4]: https://bugs.debian.org/598781
[5]: https://bugs.debian.org/598787
[6]: https://bugs.debian.org/647932
[7]: https://bugs.debian.org/658377
[8]: https://bugs.debian.org/680412
[9]: https://bugs.debian.org/712427
[10]: https://bugs.debian.org/714236
[11]: https://bugs.debian.org/721120
[12]: https://bugs.debian.org/737221
[13]: https://bugs.debian.org/770952
[14]: https://bugs.debian.org/835166
[15]: https://bugs.debian.org/841561
[16]: https://bugs.debian.org/846641
[17]: https://bugs.debian.org/849630
[18]: https://bugs.debian.org/852457
[19]: https://bugs.debian.org/868882
[20]: https://bugs.debian.org/945992
[21]: https://bugs.debian.org/1028325



Bug#1028503: UDD: Unknown "yes" value for Forwarded field in patch metadata

2023-01-14 Thread Mattia Rizzolo
On Thu, Jan 12, 2023 at 12:05:51PM +0100, Lucas Nussbaum wrote:
> The problem I have is that the 'Bug' header is often misused, and used
> for the Debian bug instead of the upstream bug. But I could special-case
> that.

I wonder if we should have lintian flag this.
Something like warn if Bug points to bugs.debian.org, unless… mh, can't
think of when it should be really. Do we have "native" packages that use
quit?

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature


Bug#1028675: defcon: FTBFS: distutils.errors.DistutilsError: Command '['/usr/bin/python3.10', '-m', 'pip', '--disable-pip-version-check', 'wheel', '--no-deps', '-w', '/tmp/tmpyii6c34w', '--quiet', 'to

2023-01-14 Thread Nilesh Patra

Control: tags -1 unreproducible
Control: tags -1 moreinfo
Control: severity -1 important

Hi Lucas,

On Sat, 14 Jan 2023 13:39:00 +0100 Lucas Nussbaum  wrote:

Source: defcon
Version: 0.10.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230113 ftbfs-bookworm

Relevant part (hopefully):
>  debian/rules binary
> dh binary --with python3,sphinxdoc --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:240: python3.10 setup.py config 
> /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:508: SetuptoolsDeprecationWarning: The license_file parameter is deprecated, use license_files instead.

>   warnings.warn(msg, warning_class)
> /usr/lib/python3/dist-packages/setuptools/installer.py:27: 
SetuptoolsDeprecationWarning: setuptools.installer is deprecated. Requirements 
should be satisfied by a PEP 517 installer.
>   warnings.warn(
> WARNING: The wheel package is not available.
> /usr/bin/python3.10: No module named pip
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/setuptools/installer.py", line 82, in 
fetch_build_egg
> subprocess.check_call(cmd)
>   File "/usr/lib/python3.10/subprocess.py", line 369, in check_call
> raise CalledProcessError(retcode, cmd)
> subprocess.CalledProcessError: Command '['/usr/bin/python3.10', '-m', 'pip', 
'--disable-pip-version-check', 'wheel', '--no-deps', '-w', '/tmp/tmpyii6c34w', 
'--quiet', 'tomli>=1.0.0']' returned non-zero exit status 1.


I can't reproduce this in a clean unstable chroot. Nor do I see any 
dependency on tomli anywhere in the code, and setuptools seems to be 
doing fine.


Could you please consider to do a re-build and see if it works for you 
and this wasn't a one-off?


Thanks
Nilesh



  1   2   3   4   >