Bug#1033170: libitext-rups-java: Does not work at all

2023-03-27 Thread tony mancill 
On Mon, Mar 20, 2023 at 07:37:48AM -0700, tony mancill wrote:
> However, given the low popcon count and the brokenness of the package,
> that may be the best path.  If there are users of libitext-rups-java who
> think otherwise, now would be the time to speak up.
> 
> ...
> 
> Returning to the focus of this bug, let's wait to see if there are
> other opinions regarding rups.  If not, I will prepare an upload of the
> libitext-java source package that removes the libitext-rups-java and
> file the bugs needed to remove the binary.

The upload is ready.  Any concerns?

$ reverse-depends libitext-rups-java   
No reverse dependencies found

$ reverse-depends -b libitext-rups-java
No reverse dependencies found

Thanks,
tony


signature.asc
Description: PGP signature

Processed: owner 1033170

2023-03-27 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> owner 1033170 !
Bug #1033170 [libitext-rups-java] libitext-rups-java: Does not work at all
Owner recorded as tony mancill .
> thanks
Stopping processing here.

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

Bug#1033517: yt-dlp: mpv fails to work with yt-dlp, after yt-dlp upgrade (uncoordinated API change?)

2023-03-27 Thread Francesco Poli 
On Mon, 27 Mar 2023 00:03:20 -0400 (EDT) Unit 193 wrote:

[...]
> On Sun, 26 Mar 2023, Francesco Poli (wintermute) wrote:
[...]
> This actually "only" happens when you use bestvideo, other formats such as 
> '22' still work.
> 
> Eg, `mpv --ytdl-format=22 https://www.youtube.com/watch?v=RZAq-_gz_W8`

Does this require to examine which formats are available, by issuing
the command

  yt-dlp --list-formats https://www.youtube.com/watch?v=

for each video you want to play?

[...]
> > Please fix this issue as soon as possible, or revert to the previous
> > version (yt-dlp/2023.02.17-1), until this behavior has been properly
> > investigated and solved.
> 
> And here lies the problem.  Seemingly one of the big fixes in 2023.03.03 
> is a workaround for the aforementioned throttling, to revert would mean to 
> make yt-dlp unusably slow.  But to leave it as is, mpv can't directly 
> utilize yt-dlp with the default quality option.
> 
> If we weren't so close to the freeze I'd say the right option would be to 
> simply patch the yt-dlp hook in mpv and move on, but that's not precisely 
> an option anymore either.

Why not?

The [freeze policy] states that, even in full freeze, fixes for
important bugs are appropriate, as long as they can be done via unstable
(as it is currently the case for mpv).

[freeze policy]: 

I have just filed bug [#1033595], in order to request that the patches
you cited are applied to mpv.

[#1033595]: 

I hope this can be the way to go.


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgptfbFv66H3Y.pgp
Description: PGP signature

Bug#1033589: python3-theano: module 'numpy' has no attribute 'bool'.

2023-03-27 Thread Rebecca N. Palmer 
While that particular problem is easy to fix, there are other 
incompatibilities that aren't (see #1026539, #1027215) and I intend to 
let autoremoval happen.

Bug#1033155: [pkg-gnupg-maint] Bug#1033155: migration test fails when EC key present in test keyrings

2023-03-27 Thread Daniel Kahn Gillmor 
Hi Andreas--

Thank you for addressing this problem, it is much appreciated!

  --dkg

On Sun 2023-03-26 14:00:17 +0200, Andreas Metzler wrote:
> On 2023-03-18 Jonathan Wiltshire  wrote:
>> Source: gnupg2
>> Version: 2.2.40-1
>> Severity: important
>> Tags: patch
>> X-Debbugs-Cc: j...@debian.org
>
>> Hi,
>
>> The stable release key for bookworm is EC, and this causes gpg1 to bail
>> out when it is imported as part of the migration test. Attached patch
>> limits the keyrings used to the archive's automatic keys, which are
>> still RSA.
> [...]
>
> Hello Jonathan,
>
> afaict currently all keys are RSA except for
> debian-archive-bookworm-stable.gpg. Wouldn't it be better to just skip
> this single key?
>
> cu Andreas
>
> ___
> pkg-gnupg-maint mailing list
> pkg-gnupg-ma...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-gnupg-maint


signature.asc
Description: PGP signature

Bug#1033590: ruby-mongo: autopkgtest failure since removal of mongodb-server in 2020

2023-03-27 Thread Paul Gevers 

Source: ruby-mongo
Version: 2.5.1-1.1
Severity: serious
Tags: bookworm-ignore
User: debian...@lists.debian.org
Usertags: regression
Control: found -1 2.4.1-1

Dear maintainer(s),

Your package has an autopkgtest, great. However, the test depends on 
mongodb-server which was removed from testing in 2019 and from unstable 
in 2020. Hence your test fails.


[Release Team hat on] Because of the timing of this bug (during the hard 
freeze) and because it doesn't indicate functionality failure of this 
package, I have marked it as bookworm-ignore.


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Processed: ruby-mongo: autopkgtest failure since removal of mongodb-server in 2020

2023-03-27 Thread Debian Bug Tracking System 
Processing control commands:

> found -1 2.4.1-1
Bug #1033590 [src:ruby-mongo] ruby-mongo: autopkgtest failure since removal of 
mongodb-server in 2020
Marked as found in versions ruby-mongo/2.4.1-1.

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

Bug#1033589: python3-theano: module 'numpy' has no attribute 'bool'.

2023-03-27 Thread Paul Gevers 

Package: python3-theano
Version: 1.0.5+dfsg-8
Severity: serious
Control: affects -1 deepnano
Control: found -1 1.1.2+dfsg-3

Dear maintainer(s),

I think the autopkgtest of deepnano points out that theano is using what 
I believe are removed attibutes from numpy.


Paul

https://ci.debian.net/data/autopkgtest/unstable/amd64/d/deepnano/32446139/log.gz

autopkgtest [19:57:01]: test run-test.sh: [---

#1 - deepnano_basecall
/usr/lib/python3/dist-packages/theano/scalar/basic.py:2412: 
FutureWarning: In the future `np.bool` will be defined as the 
corresponding NumPy scalar.

  self.ctor = getattr(np, o_type.dtype)
Traceback (most recent call last):
  File "/usr/share/deepnano/basecall.py", line 4, in 
from rnn_fin import RnnPredictor
  File "/usr/share/deepnano/rnn_fin.py", line 1, in 
import theano as th
  File "/usr/lib/python3/dist-packages/theano/__init__.py", line 83, in 


from theano import scalar, tensor
  File "/usr/lib/python3/dist-packages/theano/scalar/__init__.py", line 
1, in 

from .basic import *
  File "/usr/lib/python3/dist-packages/theano/scalar/basic.py", line 
2460, in 

convert_to_bool = Cast(bool, name="convert_to_bool")
  ^^
  File "/usr/lib/python3/dist-packages/theano/scalar/basic.py", line 
2412, in __init__

self.ctor = getattr(np, o_type.dtype)
^
  File "/usr/lib/python3/dist-packages/numpy/__init__.py", line 305, in 
__getattr__

raise AttributeError(__former_attrs__[attr])
AttributeError: module 'numpy' has no attribute 'bool'.
`np.bool` was a deprecated alias for the builtin `bool`. To avoid this 
error in existing code, use `bool` by itself. Doing this will not modify 
any behavior and is safe. If you specifically wanted the numpy scalar 
type, use `np.bool_` here.
The aliases was originally deprecated in NumPy 1.20; for more details 
and guidance see the original release note at:
https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations. 
Did you mean: 'bool_'?

autopkgtest [19:57:01]: test run-test.sh: ---]


OpenPGP_signature
Description: OpenPGP digital signature

Processed: python3-theano: module 'numpy' has no attribute 'bool'.

2023-03-27 Thread Debian Bug Tracking System 
Processing control commands:

> affects -1 deepnano
Bug #1033589 [python3-theano] python3-theano: module 'numpy' has no attribute 
'bool'.
Added indication that 1033589 affects deepnano
> found -1 1.1.2+dfsg-3
Bug #1033589 [python3-theano] python3-theano: module 'numpy' has no attribute 
'bool'.
Marked as found in versions theano/1.1.2+dfsg-3.

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

Processed: debtree: autopkgtest fails: output on stderr

2023-03-27 Thread Debian Bug Tracking System 
Processing control commands:

> found -1 1.0.11
Bug #1033587 [src:debtree] debtree: autopkgtest fails: output on stderr
Marked as found in versions debtree/1.0.11.

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

Bug#1033587: debtree: autopkgtest fails: output on stderr

2023-03-27 Thread Paul Gevers 

Source: debtree
Version: 1.1.1
Severity: serious
Tags: bookworm-ignore
User: debian...@lists.debian.org
Usertags: fails-always
Control: found -1 1.0.11

Dear maintainer(s),

Your package has an autopkgtest, great. However, it fails. Can you 
please investigate the situation and fix it? I copied some of the output 
at the bottom of this report. The test itself succeeds, but the 
autopkgtest fails because there is output to stderr and without the 
allow-stderr restriction that is considered a failure.


The release team has announced [1] that failing autopkgtest on amd64 and 
arm64 are considered RC in testing. Because of the timing in the hard 
freeze, I have marked this bug as bookworm-ignore.


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


Paul

[1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html

https://ci.debian.net/data/autopkgtest/testing/amd64/d/debtree/32153485/log.gz

autopkgtest [17:19:33]: test command1: [---

Reading package lists... 0%

Reading package lists... 0%

Reading package lists... 52%

Reading package lists... Done

Building dependency tree... 0%

Building dependency tree... 0%

Building dependency tree... 50%

Building dependency tree... 50%

Building dependency tree... Done

Reading state information... 0%

Reading state information... 4%

Reading state information... Done
I: The following dependencies have been excluded from the graph (skipped):
I: libc6 libstdc++6 zlib1g
digraph "debtree" {
rankdir=LR;
node [shape=box];
"debtree" -> "perl:any" [color=blue];
"perl:any" -> "perl" [dir=back,arrowtail=inv,color=green];
"perl:any" [shape=octagon];
"debtree" -> "libapt-pkg-perl" [color=blue];
"libapt-pkg-perl" -> "perl" [color=blue,label="(>= 5.36.0-4)"];
"libapt-pkg-perl" -> "perlapi-5.36.0" [color=blue];
"perlapi-5.36.0" -> "perl-base" [dir=back,arrowtail=inv,color=green];
"perl-base" -> "libcrypt1" [color=purple,style=bold,label="(>= 
1:4.1.0)"];
"perl-base" -> "dpkg" [color=purple,style=bold,label="(>= 1.17.17)"];
"perlapi-5.36.0" [shape=octagon];
"libapt-pkg-perl" -> "libapt-pkg6.0" [color=blue,label="(>= 2.1.20)"];
"libapt-pkg6.0" -> "libbz2-1.0" [color=blue];
"libapt-pkg6.0" -> "libgcc-s1" [color=blue,label="(>= 3.0)"];
"libgcc-s1" -> "gcc-12-base" [color=blue,label="(= 12.2.0-14)"];
"libapt-pkg6.0" -> "libgcrypt20" [color=blue,label="(>= 1.10.0)"];
"libgcrypt20" -> "libgpg-error0" [color=blue,label="(>= 1.27)"];
"libgpg-error0" -> "libgpg-error-l10n";
"libapt-pkg6.0" -> "liblz4-1" [color=blue,label="(>= 0.0~r127)"];
	"libapt-pkg6.0" -> "liblzma5" [color=blue,label="(>= 
5.1.1alpha+20120614)"];

"libapt-pkg6.0" -> "libsystemd0" [color=blue,label="(>= 221)"];
"libsystemd0" -> "libcap2" [color=blue,label="(>= 1:2.10)"];
"libsystemd0" -> "libgcrypt20" [color=blue,label="(>= 1.10.0)"];
"libsystemd0" -> "liblz4-1" [color=blue,label="(>= 0.0~r122)"];
"libsystemd0" -> "liblzma5" [color=blue,label="(>= 
5.1.1alpha+20120614)"];
"libsystemd0" -> "libzstd1" [color=blue,label="(>= 1.5.2)"];
"libapt-pkg6.0" -> "libudev1" [color=blue,label="(>= 183)"];
"libapt-pkg6.0" -> "libxxhash0" [color=blue,label="(>= 0.7.1)"];
"libapt-pkg6.0" -> "libzstd1" [color=blue,label="(>= 1.5.2)"];
"libapt-pkg6.0" -> "apt" [label="(>= 2.5.6)"];
"libapt-pkg-perl" -> "libgcc-s1" [color=blue,label="(>= 3.0)"];
"debtree" -> "ucf" [color=blue];
"debtree" -> "dctrl-tools" [color=blue];
"dctrl-tools" -> "grep-dctrl" [color=red];
"debtree" -> "graphviz";
"debtree" [style="setlinewidth(2)"]
"grep-dctrl" -> "dctrl-tools" [dir=back,arrowtail=inv,color=green];
"grep-dctrl" [shape=octagon];
"apt" [shape=diamond];
"dpkg" [shape=diamond];
"graphviz" [shape=diamond];
"perl" [shape=diamond];
"ucf" [shape=diamond];
}
// Excluded dependencies:
// libc6 libstdc++6 zlib1g
// total size of all shown packages: 17665024
// download size of all shown packages: 4859744
autopkgtest [17:19:34]: test command1: ---]
autopkgtest [17:19:34]: test command1:  - - - - - - - - - - results - - 
- - - - - - - -

command1 FAIL stderr:
autopkgtest [17:19:34]: test command1:  - - - - - - - - - - stderr - - - 
- - - - - - -


Reading package lists... 0%

Reading package lists... 0%

Reading package lists... 52%

Reading package lists... Done

Building dependency tree... 0%

Building dependency tree... 0%

Building dependency tree... 50%

Building dependency tree... 50%

Building dependency tree... Done

Reading state information... 0%

Reading state information... 4%

Reading state information... Done
I: The following dependencies have

Bug#1033586: cunit: autopkgtest regression: libncurses.so.6 [...] not found

2023-03-27 Thread Paul Gevers 

Source: cunit
Version: 2.1-3-dfsg-2.4
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

Your package has an autopkgtest, great. However, it recently (December 
2022) started to fail in testing.


Paul

https://ci.debian.net/data/autopkgtest/testing/amd64/c/cunit/32147692/log.gz

autopkgtest [12:20:37]: test test.sh: [---


 CUnit - A unit testing framework for C - Version 2.1-3
 http://cunit.sourceforge.net/

Suite initialized!

Suite: cunit_test
  Test: Verify 1 == 1... ...passed

Suite cleaned!


Run Summary:Type  TotalRan Passed Failed Inactive
  suites  1  1n/a  00
   tests  1  1  1  00
 asserts  1  1  1  0  n/a

Elapsed time =0.000 seconds

Done!
/usr/bin/ld: warning: libncurses.so.6, needed by 
/tmp/autopkgtest-lxc.6_783s7i/downtmp/build.8Z5/src/debian/tmp-ncurses/usr/lib/x86_64-linux-gnu/libcunit.so, 
not found (try using -rpath or -rpath-link)
/usr/bin/ld: 
/tmp/autopkgtest-lxc.6_783s7i/downtmp/build.8Z5/src/debian/tmp-ncurses/usr/lib/x86_64-linux-gnu/libcunit.so: 
undefined reference to `wattr_on@NCURSES6_5.0.19991023'
/usr/bin/ld: 
/tmp/autopkgtest-lxc.6_783s7i/downtmp/build.8Z5/src/debian/tmp-ncurses/usr/lib/x86_64-linux-gnu/libcunit.so: 
undefined reference to `endwin@NCURSES6_5.0.19991023'
/usr/bin/ld: 
/tmp/autopkgtest-lxc.6_783s7i/downtmp/build.8Z5/src/debian/tmp-ncurses/usr/lib/x86_64-linux-gnu/libcunit.so: 
undefined reference to `scrollok@NCURSES6_5.0.19991023'
/usr/bin/ld: 
/tmp/autopkgtest-lxc.6_783s7i/downtmp/build.8Z5/src/debian/tmp-ncurses/usr/lib/x86_64-linux-gnu/libcunit.so: 
undefined reference to `newpad@NCURSES6_5.0.19991023'
/usr/bin/ld: 
/tmp/autopkgtest-lxc.6_783s7i/downtmp/build.8Z5/src/debian/tmp-ncurses/usr/lib/x86_64-linux-gnu/libcunit.so: 
undefined reference to `mvwprintw@NCURSES6_5.0.19991023'
/usr/bin/ld: 
/tmp/autopkgtest-lxc.6_783s7i/downtmp/build.8Z5/src/debian/tmp-ncurses/usr/lib/x86_64-linux-gnu/libcunit.so: 
undefined reference to `wborder@NCURSES6_5.0.19991023'
/usr/bin/ld: 
/tmp/autopkgtest-lxc.6_783s7i/downtmp/build.8Z5/src/debian/tmp-ncurses/usr/lib/x86_64-linux-gnu/libcunit.so: 
undefined reference to `init_pair@NCURSES6_5.0.19991023'
/usr/bin/ld: 
/tmp/autopkgtest-lxc.6_783s7i/downtmp/build.8Z5/src/debian/tmp-ncurses/usr/lib/x86_64-linux-gnu/libcunit.so: 
undefined reference to `echo@NCURSES6_5.0.19991023'
/usr/bin/ld: 
/tmp/autopkgtest-lxc.6_783s7i/downtmp/build.8Z5/src/debian/tmp-ncurses/usr/lib/x86_64-linux-gnu/libcunit.so: 
undefined reference to `wmove@NCURSES6_5.0.19991023'
/usr/bin/ld: 
/tmp/autopkgtest-lxc.6_783s7i/downtmp/build.8Z5/src/debian/tmp-ncurses/usr/lib/x86_64-linux-gnu/libcunit.so: 
undefined reference to `start_color@NCURSES6_5.0.19991023'
/usr/bin/ld: 
/tmp/autopkgtest-lxc.6_783s7i/downtmp/build.8Z5/src/debian/tmp-ncurses/usr/lib/x86_64-linux-gnu/libcunit.so: 
undefined reference to `newwin@NCURSES6_5.0.19991023'
/usr/bin/ld: 
/tmp/autopkgtest-lxc.6_783s7i/downtmp/build.8Z5/src/debian/tmp-ncurses/usr/lib/x86_64-linux-gnu/libcunit.so: 
undefined reference to `waddnstr@NCURSES6_5.0.19991023'
/usr/bin/ld: 
/tmp/autopkgtest-lxc.6_783s7i/downtmp/build.8Z5/src/debian/tmp-ncurses/usr/lib/x86_64-linux-gnu/libcunit.so: 
undefined reference to `wgetch@NCURSES6_5.0.19991023'
/usr/bin/ld: 
/tmp/autopkgtest-lxc.6_783s7i/downtmp/build.8Z5/src/debian/tmp-ncurses/usr/lib/x86_64-linux-gnu/libcunit.so: 
undefined reference to `wgetnstr@NCURSES6_5.0.19991023'
/usr/bin/ld: 
/tmp/autopkgtest-lxc.6_783s7i/downtmp/build.8Z5/src/debian/tmp-ncurses/usr/lib/x86_64-linux-gnu/libcunit.so: 
undefined reference to `werase@NCURSES6_5.0.19991023'
/usr/bin/ld: 
/tmp/autopkgtest-lxc.6_783s7i/downtmp/build.8Z5/src/debian/tmp-ncurses/usr/lib/x86_64-linux-gnu/libcunit.so: 
undefined reference to `wrefresh@NCURSES6_5.0.19991023'
/usr/bin/ld: 
/tmp/autopkgtest-lxc.6_783s7i/downtmp/build.8Z5/src/debian/tmp-ncurses/usr/lib/x86_64-linux-gnu/libcunit.so: 
undefined reference to `initscr@NCURSES6_5.0.19991023'
/usr/bin/ld: 
/tmp/autopkgtest-lxc.6_783s7i/downtmp/build.8Z5/src/debian/tmp-ncurses/usr/lib/x86_64-linux-gnu/libcunit.so: 
undefined reference to `noecho@NCURSES6_5.0.19991023'
/usr/bin/ld: 
/tmp/autopkgtest-lxc.6_783s7i/downtmp/build.8Z5/src/debian/tmp-ncurses/usr/lib/x86_64-linux-gnu/libcunit.so: 
undefined reference to `delwin@NCURSES6_5.0.19991023'
/usr/bin/ld: 
/tmp/autopkgtest-lxc.6_783s7i/downtmp/build.8Z5/src/debian/tmp-ncurses/usr/lib/x86_64-linux-gnu/libcunit.so: 
undefined reference to `wattr_off@NCURSES6_5.0.19991023'
/usr/bin/ld: 
/tmp/autopkgtest-lxc.6_783s7i/downtmp/build.8Z5/src/debian/tmp-ncurses/usr/lib/x86_64-linux-gnu/libcunit.so: 
undefined reference to `wattrset@NCURSES6_5.0.19991023'
/usr/bin/ld: 
/tmp/autopkgtest-lxc.6_783s7i/downtmp/build.8Z5/src/debian/tmp-ncurses/usr/lib/x86_64-linux-gnu/libcunit.so: 
undefined reference to `wclear@NCURSES6_5.0.19991023'

Bug#1033584: brial: autopkgtest fails: cannot import name 'getargspec' from 'inspect'

2023-03-27 Thread Paul Gevers 

Source: brial
Version: 1.2.11-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

Your package has an autopkgtest, great. However, it fails. Can you 
please investigate the situation and fix it? I copied some of the output 
at the bottom of this report.


The release team has announced [1] that failing autopkgtest on amd64 and 
arm64 are considered RC in testing. In this case it seems to point out 
that the python package is close to useless. (If I am reading the signs 
wrong, feel free to mark this bug as bookworm-ignore (Release Team 
member hat on).)


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


Paul

[1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html

https://ci.debian.net/data/autopkgtest/testing/amd64/b/brial/32215813/log.gz

autopkgtest [18:27:16]: test autodep8-python3: [---
Testing with python3.11:
/usr/lib/python3/dist-packages/brial/PyPolyBoRi.py:72: DeprecationWarning:
Importing order_dict from here is deprecated. If you need to use it, 
please import it directly from sage.rings.polynomial.pbori.pbori

See https://trac.sagemath.org/30332 for details.
  OrderCode = type('OrderCode', (object,), dict(order_dict))
/usr/lib/python3/dist-packages/brial/PyPolyBoRi.py:91: DeprecationWarning:
Importing MonomialFactory from here is deprecated. If you need to use 
it, please import it directly from sage.rings.polynomial.pbori.pbori

See https://trac.sagemath.org/30332 for details.
  Monomial = MonomialFactory()
/usr/lib/python3/dist-packages/brial/PyPolyBoRi.py:92: DeprecationWarning:
Importing PolynomialFactory from here is deprecated. If you need to use 
it, please import it directly from sage.rings.polynomial.pbori.pbori

See https://trac.sagemath.org/30332 for details.
  Polynomial = PolynomialFactory()
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/brial/__init__.py", line 34, in 


from .gbcore import groebner_basis
  File "/usr/lib/python3/dist-packages/brial/gbcore.py", line 10, in 


from inspect import getargspec
ImportError: cannot import name 'getargspec' from 'inspect' 
(/usr/lib/python3.11/inspect.py)

autopkgtest [18:27:17]: test autodep8-python3: ---]


OpenPGP_signature
Description: OpenPGP digital signature

Processed: bonnie++: autopkgtest fails: Syntax error: "then" unexpected

2023-03-27 Thread Debian Bug Tracking System 
Processing control commands:

> found -1 1.98
Bug #1033582 [src:bonnie++] bonnie++: autopkgtest fails: Syntax error: "then" 
unexpected
Marked as found in versions bonnie++/1.98.

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

Bug#1033582: bonnie++: autopkgtest fails: Syntax error: "then" unexpected

2023-03-27 Thread Paul Gevers 

Source: bonnie++
Version: 2.00a+nmu1
Severity: serious
Tags: bookworm-ignore
User: debian...@lists.debian.org
Usertags: fails-always
Control: found -1 1.98

Dear maintainer(s),

Your package has an autopkgtest, great. However, it fails. Can you 
please investigate the situation and fix it? I copied some of the output 
at the bottom of this report.


The release team has announced [1] that failing autopkgtest on amd64 and 
arm64 are considered RC in testing. However, (Release Team member hat 
on) due to the current hard freeze I have marked this bug as 
bookworm-ignore. Please, if you fix this bug, also mark the test as 
superficial (the name "smoke" suggests it's not more than superficial).


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


Paul

[1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html

https://ci.debian.net/data/autopkgtest/testing/amd64/b/bonnie++/32118781/log.gz

autopkgtest [11:21:53]: test smoke: [---
/tmp/autopkgtest-lxc.6wrumbe1/downtmp/build.HhF/src/debian/tests/smoke: 
9: Syntax error: "then" unexpected

autopkgtest [11:21:53]: test smoke: ---]


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1027439: elementpath breaks python-xmlschema autopkgtest: 'XMLSchemaContext' object has no attribute 'iter'

2023-03-27 Thread Emmanuel Arias 
Hi Jochen,

On Mon, Mar 27, 2023 at 06:59:50PM +0200, Jochen Sprickerhof wrote:
> Hi Emmanuel,
> 
> note that the new upstream version of python-xmlschema fixes this and other
> errors but Debian unstable is frozen and the change would be too big. On the
> other hand this currently keeps the new upstream version of elementpath from
> transition to testing which is a viable outcome at the current release state
> as well. So there is not really something to do for this bug till the
> release of bookworm and afterwards an upload of the new upstream version
> should fix it.

Thanks for reply me. Ah ok, I downloaded the patch and iirc only change the
tests. But if this bug doesn't affect to elementpath, I will wait after
freeze end

Cheers,
Emmanuel

> 
> Cheers Jochen
> 
> * Emmanuel Arias  [2023-03-27 07:35]:
> > Hello,
> > 
> > Applying the patch all the tests are fixed except one:
> > 
> > ==
> > FAIL: test_xml_document_validation 
> > (xmlschema.testing._builders.TestValidator004.test_xml_document_validation)
> > --
> > Traceback (most recent call last):
> >  File 
> > "/<>/.pybuild/cpython3_3.11_xmlschema/build/xmlschema/testing/_builders.py",
> >  line 623, in test_xml_document_validation
> >self.check_data_conversion_with_lxml()
> >  File 
> > "/<>/.pybuild/cpython3_3.11_xmlschema/build/xmlschema/testing/_builders.py",
> >  line 507, in check_data_conversion_with_lxml
> >self.assertEqual(len(lxml_errors), len(self.errors), msg=xml_file)
> > AssertionError: 2 != 1 : 
> > tests/test_cases/examples/collection/collection3bis.xml
> > 
> > -
> > 
> > I will investigate a little bit today.
> > 
> > Cheers,
> > eamanu
> 
> 




signature.asc
Description: PGP signature

Bug#1027439: elementpath breaks python-xmlschema autopkgtest: 'XMLSchemaContext' object has no attribute 'iter'

2023-03-27 Thread Jochen Sprickerhof 

Hi Emmanuel,

note that the new upstream version of python-xmlschema fixes this and 
other errors but Debian unstable is frozen and the change would be too 
big. On the other hand this currently keeps the new upstream version of 
elementpath from transition to testing which is a viable outcome at the 
current release state as well. So there is not really something to do 
for this bug till the release of bookworm and afterwards an upload of 
the new upstream version should fix it.


Cheers Jochen

* Emmanuel Arias  [2023-03-27 07:35]:

Hello,

Applying the patch all the tests are fixed except one:

==
FAIL: test_xml_document_validation 
(xmlschema.testing._builders.TestValidator004.test_xml_document_validation)
--
Traceback (most recent call last):
 File 
"/<>/.pybuild/cpython3_3.11_xmlschema/build/xmlschema/testing/_builders.py",
 line 623, in test_xml_document_validation
   self.check_data_conversion_with_lxml()
 File 
"/<>/.pybuild/cpython3_3.11_xmlschema/build/xmlschema/testing/_builders.py",
 line 507, in check_data_conversion_with_lxml
   self.assertEqual(len(lxml_errors), len(self.errors), msg=xml_file)
AssertionError: 2 != 1 : tests/test_cases/examples/collection/collection3bis.xml

-

I will investigate a little bit today.

Cheers,
eamanu





signature.asc
Description: PGP signature

Bug#1029821: marked as done (change gnome-desktop's default choice of Japanese input methods for Debian)

2023-03-27 Thread Debian Bug Tracking System 
Your message dated Mon, 27 Mar 2023 13:05:26 +
with message-id 
and subject line Bug#1029821: fixed in gnome-desktop 44.0-1
has caused the Debian Bug report #1029821,
regarding change gnome-desktop's default choice of Japanese input methods for 
Debian
to be marked as done.

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

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


-- 
1029821: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029821
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-initial-setup
Followup-For: Bug #984875
X-Debbugs-Cc: yy.y.ja...@gmail.com
Control: clone -1 -2
Control: reassign -2 libgnome-desktop-4-2
Control: retitle -2 change gnome-desktop's default choice of Japanese input 
methods for Debian
Control: affects -2 gnome-initial-setup

Now in bookworm gnome metapackage Recommends: gnome-initial-setup.
This means all task-gnome-desktop users in all languages including
Japanese now have to use the gnome-initial-setup window after the first
login.

Cloning this bug because the choices of input methods and their ordering
are handled by gnome-initial-setup itself, and the default choice is
handled by the dependent libgnome-desktop-4-2 package, and both are
still not good at least for Japanese.

Regards,

-- 
YOSHINO Yoshihito 
--- End Message ---
--- Begin Message ---
Source: gnome-desktop
Source-Version: 44.0-1
Done: Jeremy Bicha 

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

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

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

Debian distribution maintenance software
pp.
Jeremy Bicha  (supplier of updated gnome-desktop package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 27 Mar 2023 08:35:20 -0400
Source: gnome-desktop
Built-For-Profiles: noudeb
Architecture: source
Version: 44.0-1
Distribution: experimental
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bicha 
Closes: 1029821
Changes:
 gnome-desktop (44.0-1) experimental; urgency=medium
 .
   [ Jeremy Bicha ]
   * New upstream release
 .
   [ Simon McVittie ]
   * Merge packaging changes from unstable
 - Default to mozc-jp where possible (Closes: #1029821)
Checksums-Sha1:
 810132b8ce2002eb1bcd20245a0cedd903166e68 3935 gnome-desktop_44.0-1.dsc
 2b845227730824c503251c418f2b275283721211 765764 gnome-desktop_44.0.orig.tar.xz
 2e0a870d75a63e8e7fc8fcfee84f7197063650fc 34696 
gnome-desktop_44.0-1.debian.tar.xz
 5f42d41458082984b528a7ae151acc50d65b8f42 19004 
gnome-desktop_44.0-1_source.buildinfo
Checksums-Sha256:
 a9782b2dab0001e09947f5a18d9f14d81056e569a6e88ed39fe1c08a2a25f927 3935 
gnome-desktop_44.0-1.dsc
 42c773745d84ba14bc1cf1c4c6f4606148803a5cd337941c63964795f3c59d42 765764 
gnome-desktop_44.0.orig.tar.xz
 0342c03a1ebfc1d9b75e219816152513ac3974b59efbdfecccfc45b516f920d6 34696 
gnome-desktop_44.0-1.debian.tar.xz
 c0b964a3f42c3d9df522543637fd0b858fe68e6f340ba9bde381b95b8206549e 19004 
gnome-desktop_44.0-1_source.buildinfo
Files:
 76b36add0357663a2727bb5aa638c55f 3935 gnome optional gnome-desktop_44.0-1.dsc
 1f0b7281e462d6dfc8d3888fdaafd2ba 765764 gnome optional 
gnome-desktop_44.0.orig.tar.xz
 ca6fa5fcb8cc98fb55b89e7459fcdfcb 34696 gnome optional 
gnome-desktop_44.0-1.debian.tar.xz
 f4bf8813a9a87bb133c33ea1652270a8 19004 gnome optional 
gnome-desktop_44.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmQhjaIACgkQ5mx3Wuv+
bH0R9BAA0LP9XjuqMYRllsCM6kTJ6MYMAj5hiHRAOsYLyK63aARLlGjVRnvURkTB
Gcql1WphRsrnMWlsndmOIG4Uwxty2h9yBmYmYB+PDuMmOcSUCoIx91dZgSqhoGZK
8Msv5utBfbRaVwm9lgYJXxETbzswVAw4PLHOqWwPxs7dCJsMzVpxcJE2wBdEaeFP
/la7xPV5UygF5cotUXkw1UrfIyhd40h972RbI8Sl3ed6AhI+13ylTDTOY6F4S1dz
grubgXPQiKycbHssZaK4r4sJZhxCi4JMcZyOBgjymzyFuHt6XE/+toKDqFVg+6je
nwXWztpbiRwDT2orgBNUxvVRckhm6rctM3YpJzzi85g20Te09ExzLcaxLaHuz5D3
noc/b1pmxplXt/o1j3nGxb5mi5gq8YKhVYSCqkV6vvraryS6YRMwN9nOOwp8nb3y
V2o3aUdk9JSlxLwpCewei/iTPsez6rl9QNb4sgfPmfptfVI1RbtVG0/E9JnBmpFI
2Qez5mFcYrW3FvvdJFyWP2WwVINJlfvF4E9aaPVzURc1ipULG6BvTHUuax+X9ZlQ
yW/YC/SQDJISpWMUmWCWYvC6ZoDogaYBQH5tHHsprTHTWGtht4j0OSyQFWC5D2uR
dgWThGJeDNcP3lWlQz1uR2hv7Q26MbYawvhhZecROC5iyf5p/AI=
=Q3tp
-END PGP SIGNATURE End

Bug#1027439: elementpath breaks python-xmlschema autopkgtest: 'XMLSchemaContext' object has no attribute 'iter'

2023-03-27 Thread Emmanuel Arias 
Hello, 

Applying the patch all the tests are fixed except one:

==
FAIL: test_xml_document_validation 
(xmlschema.testing._builders.TestValidator004.test_xml_document_validation)
--
Traceback (most recent call last):
  File 
"/<>/.pybuild/cpython3_3.11_xmlschema/build/xmlschema/testing/_builders.py",
 line 623, in test_xml_document_validation
self.check_data_conversion_with_lxml()
  File 
"/<>/.pybuild/cpython3_3.11_xmlschema/build/xmlschema/testing/_builders.py",
 line 507, in check_data_conversion_with_lxml
self.assertEqual(len(lxml_errors), len(self.errors), msg=xml_file)
AssertionError: 2 != 1 : tests/test_cases/examples/collection/collection3bis.xml

-

I will investigate a little bit today.

Cheers,
eamanu


signature.asc
Description: PGP signature

Bug#1031716: Generating stricter dependencies on python3-protobuf rdeps

2023-03-27 Thread Pirate Praveen 

On Tue, 7 Mar 2023 12:09:35 +0200 Adrian Bunk  wrote:
> 2. packages using python3-protobuf (e.g. python3-bernhard) ship files
>that were generated with protobuf-compiler during their build
>(e.g. /usr/lib/python3/dist-packages/bernhard/pb.py )

Can this generation be moved to postinst and use a dpkg trigger to 
regenerate it when protobuf is updated?


An example is 
https://sources.debian.org/src/node-constants-browserify/1.0.0%2Bdfsg-8/debian/postinst/


Though it would mean runtime dependency on protobuf-compiler.

Processed: bug 1033426 is forwarded to https://github.com/ultrabug/uhashring/pull/17, tagging 1033426

2023-03-27 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> forwarded 1033426 https://github.com/ultrabug/uhashring/pull/17
Bug #1033426 [src:python-uhashring] python-uhashring: FTBFS in testing: tests 
fail
Set Bug forwarded-to-address to 'https://github.com/ultrabug/uhashring/pull/17'.
> tags 1033426 + upstream fixed-upstream
Bug #1033426 [src:python-uhashring] python-uhashring: FTBFS in testing: tests 
fail
Added tag(s) fixed-upstream and upstream.
> thanks
Stopping processing here.

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

Processed: bug 1033431 is forwarded to https://github.com/cookiecutter/cookiecutter/commit/980ff089efaef27b99b97525f6a206bd7c3f2282 ...

2023-03-27 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> forwarded 1033431 
> https://github.com/cookiecutter/cookiecutter/commit/980ff089efaef27b99b97525f6a206bd7c3f2282
Bug #1033431 [src:cookiecutter] cookiecutter: FTBFS in testing: dh_auto_test: 
error: pybuild --test -i python{version} -p 3.11 returned exit code 13
Set Bug forwarded-to-address to 
'https://github.com/cookiecutter/cookiecutter/commit/980ff089efaef27b99b97525f6a206bd7c3f2282'.
> tags 1033431 + upstream fixed-upstream
Bug #1033431 [src:cookiecutter] cookiecutter: FTBFS in testing: dh_auto_test: 
error: pybuild --test -i python{version} -p 3.11 returned exit code 13
Added tag(s) upstream and fixed-upstream.
> thanks
Stopping processing here.

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

Processed: bug 1033432 is forwarded to https://github.com/Pylons/pyramid_jinja2/pull/159, tagging 1033432

2023-03-27 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> forwarded 1033432 https://github.com/Pylons/pyramid_jinja2/pull/159
Bug #1033432 [src:pyramid-jinja2] pyramid-jinja2: FTBFS in testing: 
ImportError: cannot import name 'contextfilter' from 'jinja2' 
(/usr/lib/python3/dist-packages/jinja2/__init__.py)
Set Bug forwarded-to-address to 
'https://github.com/Pylons/pyramid_jinja2/pull/159'.
> tags 1033432 + upstream fixed-upstream
Bug #1033432 [src:pyramid-jinja2] pyramid-jinja2: FTBFS in testing: 
ImportError: cannot import name 'contextfilter' from 'jinja2' 
(/usr/lib/python3/dist-packages/jinja2/__init__.py)
Added tag(s) fixed-upstream and upstream.
> thanks
Stopping processing here.

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

Bug#977027: [Pkg-javascript-devel] Bug#977027: rhino breaks dojo autopkgtest: Cannot set property "dojo" of null to "[object Object]"

2023-03-27 Thread Bastien ROUCARIES 
Le dim. 26 mars 2023 à 21:39, Markus Koschany  a écrit :

> Hi Graham,
>
> Am Sonntag, dem 26.03.2023 um 19:28 +0200 schrieb Graham Inggs:
> > Hi Markus
> >
> > On Sun, 26 Mar 2023 at 16:34, Markus Koschany  wrote:
> > > 1. There is no transition needed because only shrinksafe is affected
> by the
> > > new
> > > rhino version.
>
>
> > How did you determine this?
>
> Rhino 1.7.14 was mostly API compatible meaning I only had to fix an issue
> in
> closure-compiler. All other packages can be built from source without
> modifications. I didn't find any other runtime / ABI issues so far.
>
> >
> > > 2. shrinksafe has no reverse-dependencies
> >
> > That is true, but src:dojo has ledgersmb and tt-rss as
> reverse-dependencies.
>
> I used codesearch.debian.net and found only documentation or other minor
> references of shrinksafe in affected packages.
>
> https://codesearch.debian.net/search?q=shrinksafe=1
>
> Since all Java tests in dojo pass after the rebuild and almost all of the
> code
> in dojo is Javascript anyway, I don't see how ledgersmb and tt-rss can be
> affected by the new rhino version. Wouldn't those packages depend on rhino
> in
> some way? To me it seems rhino is only required to build shrinksafe which
> can
> be used for compressing Javascript files. But maybe the dojo maintainers
> can
> chime in here.
>

Yes shrinksafe is only used for compression.

Bastien

>
>
> Regards,
>
> Markus
> --
> Pkg-javascript-devel mailing list
> pkg-javascript-de...@alioth-lists.debian.net
>
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
>