date:20221121

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

> severity 1023371 normal
Bug #1023371 [plocate] plocate.postint requires a depedency on adduser
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#1024520: debhelper: Use of uninitialized value $dest in -l at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 662.

2022-11-21 Thread Axel Beckert

Hi Niels,

Niels Thykier wrote:
> > Will upload anyway as it clearly improves the situation and we need a
> > fix quickly.
> > 
> > Niels: Feel free to improve my fix in the next upload in case I
> > understood some of the new code wrongly.
> 
> Thanks for finding and working around the bug.

You're welcome.

> It was indeed an oversight.

Yep, looked like that: Was the only occurence far away from the
remaining calls.

Also wondered if that call better should have been a simple
install_file() instead.

> I will probably not change anything for now. Having slept on it and given
> additional evidence, I think the underlying issue was a bug in fakeroot
> (#1023286 is most my most likely candidate) and not a bug in debhelper

I see. Given that comment and the fact that #1023286 only affects 32
bit architectures, I think that #1024261 (in debhelper) is related and
might have the same cause as only 32-bit files seem to be affected.
(Or was #1024261 the whole trigger for that 4-argument conversion? Saw
no comment from you there so far.)

> (meaning the change to 4 parameters should probably be undone).

Ack, sounds as if this is probably the way to go once it's clear that
#1023286 was really the cause. I also wonder if some versioned Breaks
or Conflicts would be helpful, too.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Processed: fixed 1012067 in 5.2.0-1

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

> fixed 1012067 5.2.0-1
Bug #1012067 [src:jss] jss: FTBFS with OpenJDK 17: no such provider SunJSSE
Marked as fixed in versions jss/5.2.0-1.
> thanks
Stopping processing here.

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

Processed: closing 1012067

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

> close 1012067 5.2.0-1
Bug #1012067 [src:jss] jss: FTBFS with OpenJDK 17: no such provider SunJSSE
Ignoring request to alter fixed versions of bug #1012067 to the same values 
previously set
Bug #1012067 [src:jss] jss: FTBFS with OpenJDK 17: no such provider SunJSSE
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: closing 1023204

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

> close 1023204
Bug #1023204 [sssd-ipa] sssd-ipa: sssd fails to start due to broken dependency
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1012067: closing 1012067

2022-11-21 Thread Timo Aaltonen

close 1012067 5.2.0-1
thanks

forgot to close this via the changelog

Bug#1023204: closing 1023204

2022-11-21 Thread Timo Aaltonen

close 1023204 
thanks

alright, good to know

Bug#732570: Let's remove it

2022-11-21 Thread Jelmer Vernooĳ

reassign 732570 ftp.debian.org
title 732570 RM: libarch-perl -- RoM; few users, dead upstream
user debian-rele...@lists.debian.org
usertag 732570 + bsp-2022-11-nl-tilburg
thanks

Let's remove it - popcon has dropped below 20 at this point
(https://qa.debian.org/popcon.php?package=libarch-perl) and I
can no longer discern the line for it on the percent graph
(https://qa.debian.org/popcon-graph.php?packages=git-all%2Cgit-arch%2Ctla%2Clibarch-perl&show_installed=on&want_percent=on&want_legend=on&from_date=&to_date=&hlght_date=&date_fmt=%25Y-%25m&beenhere=1)

The last upstream release is more than 12 years old - 
https://metacpan.org/dist/Arch/changes

libarch-perl by itself is also not useful, it's a library meant to be
used by other software - and no reverse dependencies are packaged in
Debian.

I have some experience with arch, but all arch repositories I knew
about have also long since migrated to other VCSes. I think there's an
argument that tla itself should be kept around, to at least allow
people to be able to access old repositories and migrate away.

-- 
Jelmer Vernooĳ 
PGP Key: https://www.jelmer.uk/D729A457.asc

Processed (with 1 error): Let's remove it

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

> reassign 732570 ftp.debian.org
Bug #732570 [libarch-perl] libarch-perl should be removed
Bug reassigned from package 'libarch-perl' to 'ftp.debian.org'.
No longer marked as found in versions libarch-perl/0.5.2-1.
Ignoring request to alter fixed versions of bug #732570 to the same values 
previously set
> title 732570 RM: libarch-perl -- RoM; few users, dead upstream
Unknown command or malformed arguments to command.
> user debian-rele...@lists.debian.org
Setting user to debian-rele...@lists.debian.org (was jel...@jelmer.uk).
> usertag 732570 + bsp-2022-11-nl-tilburg
There were no usertags set.
Usertags are now: bsp-2022-11-nl-tilburg.
> thanks
Stopping processing here.

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

Bug#1024493: Proposed-RM: bs1770gain -- RoQA; inappropriate content

2022-11-21 Thread Petter Reinholdtsen



Personally I find the story of Daryl Davis inspiring, and believe such
approach have higher chances of success than one using contempt and
rejection.

https://en.wikipedia.org/wiki/Daryl_Davis >
https://www.npr.org/2017/08/20/544861933/how-one-man-convinced-200-ku-klux-klan-members-to-give-up-their-robes
 >

The Homepage URL is a statement of fact about a package, ie its origin
and where users can check out the upstream information.  It is also
useful to track down upstream if it move in the future.  It is not a
useful marketing channel, but can improve search engine ranking slightly
due to its use within Debian.  I believe the advantages of machine
readable links to the package origin outweigh any improved search
ranking, as I believe the latter is very minuscule.

If I understand the objections about the code, it is about the strings
'#WLM' and 'Nanos gigantum humeris insidentes.'.  The former seem to be
a reference to 'white lives matters', a sad reaction to the 'black lives
matter' movement that have gained traction the last few years[1], and
the latter is a reference to a cristian quote initially from Bernard of
Chartres, according to wikipedia[2], and later made more known by Isac
Newton.  As I see it these strings have no operational function for the
software and I have no attachment to them whatsoever.  I understand that
the objections is regarding believed intent behind the strings.  I do
not see any point in spending time discussing them, and thus removed
them from the binary.  In my opinion they have no marketing or
promotional value in the source, so I see very little gain from taking
the extra work to repack the tarball with these 9 lines from the source
code

 [1] https://en.wikipedia.org/wiki/White_Lives_Matter >
 [2] https://en.wikipedia.org/wiki/Standing_on_the_shoulders_of_giants >

-- 
Happy hacking
Petter Reinholdtsen

Bug#1024303: marked as pending in zookeeper

2022-11-21 Thread Thomas Goirand

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/java-team/zookeeper/-/commit/c27dcbbca4a2a463e04a1eb60958ce139fbf292c


* Team upload.
  * Rebuilt for all Python3 versions (Closes: #1024303).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1024303

Processed: Bug#1024303 marked as pending in zookeeper

Processing control commands:

> tag -1 pending
Bug #1024303 [src:zookeeper] zookeeper: b-d on python3-all-dev, but not built 
for all supported Python3 versions
Added tag(s) pending.

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

Bug#1022577: llvm-toolchain-15 fails with LLVM ERROR when using mesa

On Sun, Nov 13, 2022 at 12:04:07AM +0200, Adrian Bunk wrote:
> Control: close 1022576 22.2.3-1
> 
> On Sat, Nov 05, 2022 at 10:22:18AM +, Simon McVittie wrote:
> > Control: retitle -1 llvm-toolchain-15: Mesa on armel,armhf fails with LLVM 
> > ERROR: Cannot select
> > Control: tags -1 + patch fixed-upstream
> > 
> > On Mon, 24 Oct 2022 at 12:45:01 +0300, Adrian Bunk wrote:
> > > https://buildd.debian.org/status/fetch.php?pkg=mutter&arch=armhf&ver=43.0-3&stamp=1666029584&raw=0
> > > 
> > > ...
> > > # Start of pipeline tests
> > > LLVM ERROR: Cannot select: 0x1300f80: v4i32 = ARMISD::VCMPZ 0x1301c70, 
> > > Constant:i32<2>
> > >   0x1301c70: v4i32,ch = ARMISD::VLD1DUP<(load (s32) from %ir.212)> 
> > > 0xdf9afc, 0x131c538:1, Constant:i32<4>
> > > 0x131c538: i32,i32,ch = load<(load (s32) from %ir.209, align 8), 
> > > > 0xdf9afc, 0x12fb7e0, Constant:i32<64>
> > >   0x12fb7e0: i32,ch = CopyFromReg 0xdf9afc, Register:i32 %23
> > > 0x12e99c0: i32 = Register %23
> > >   0x131a9a8: i32 = Constant<64>
> > > 0x1319fd0: i32 = Constant<4>
> > >   0x131a2e8: i32 = Constant<2>
> > > In function: fs_variant_partial
> > > ...
> > > 
> > > 
> > > Some discussion is in
> > > https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-15/+bug/1993800
> > 
> > According to upstream bug 
> > 
> > this is fixed by commit
> > .
> 
> The reason why mesa hit this issue often has been fixed in mesa in [1],
> and I am closing the bug in mesa.
> 
> With current mesa all visible issues are gone,
> except perhaps mutter FTBFS.
> 
> mutter on armhf/armel went from 62 test failures to 1-2 test failures,
> I have not investigated whether they are due to this issue or unrelated.
>...

FYI:
mutter built on armhf/armel with the fixed LLVM.[1]

cu
Adrian

[1] I haven't double-checked that it was the LLVM patches and not 
something unrelated that fixed the build.

Bug#1024303: marked as done (zookeeper: b-d on python3-all-dev, but not built for all supported Python3 versions)

Your message dated Mon, 21 Nov 2022 11:36:59 +
with message-id 
and subject line Bug#1024303: fixed in zookeeper 3.8.0-10
has caused the Debian Bug report #1024303,
regarding zookeeper: b-d on python3-all-dev, but not built for all supported 
Python3 versions
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.)


-- 
1024303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024303
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zookeeper
Version: 3.8.0-9
Severity: serious
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.11 python3-all-dev

Hi Maintainer

This package build-depends on python3-all-dev, but does not build
extensions/libraries for all supported python3 versions.  This is seen
on the transition tracker for adding python3.11 support [1] and
creates false positives.

Please either replace the b-d python3-all-dev with python3-dev, or
build for all supported Python3 versions.  With the former solution
you get later exposure to a new python3 version, with the latter
solution you get early exposure.

Regards
Graham


[1] https://release.debian.org/transitions/html/python3.11-add.html
--- End Message ---
--- Begin Message ---
Source: zookeeper
Source-Version: 3.8.0-10
Done: Thomas Goirand 

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

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

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated zookeeper package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 21 Nov 2022 11:14:39 +0100
Source: zookeeper
Architecture: source
Version: 3.8.0-10
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Thomas Goirand 
Closes: 1024303
Changes:
 zookeeper (3.8.0-10) unstable; urgency=medium
 .
   * Team upload.
   * Rebuilt for all Python3 versions (Closes: #1024303).
Checksums-Sha1:
 6cbfac537811c4ae53d65778d5102a0a23ea99c7 3517 zookeeper_3.8.0-10.dsc
 1fa29a19084b89a5a3ded9e31ea07c17b136fe38 89136 zookeeper_3.8.0-10.debian.tar.xz
 d5dc0cf0cd0ce095e89e587709896f4134f5db45 24402 
zookeeper_3.8.0-10_amd64.buildinfo
Checksums-Sha256:
 9d476e68d29a7417bafc526fc41f4e957ba80fb1afb5c8bf38d579e72501b674 3517 
zookeeper_3.8.0-10.dsc
 be936f1dd4a5d4703a82c9b60fc73d567f72dae960360c445c41cde40b7fb3dc 89136 
zookeeper_3.8.0-10.debian.tar.xz
 81066172dd9f2d0fb93ac494141e4e4c62c9b281fdf15aafbc49e0d96895c883 24402 
zookeeper_3.8.0-10_amd64.buildinfo
Files:
 897d9c859141913096ca0a8a4a6ffb7d 3517 java optional zookeeper_3.8.0-10.dsc
 a1763548be179b32d4a8155713d99cfc 89136 java optional 
zookeeper_3.8.0-10.debian.tar.xz
 05af5d08fa6dae74c517352ae442ca4f 24402 java optional 
zookeeper_3.8.0-10_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmN7XoMACgkQ1BatFaxr
Q/5c0w/+NDsgYz2SnOlCMrS56Y4YCSnzKEg8AwwKb4X6Mif1pUIUCfKfz3I/DJVA
T4ae4ObUBMLQbAEVg179ppRumra4opJZIV/YKp3Gek4PUB09UxnElAsqZpx4lz11
QLTxh1SmnT1RraLoUm387lagYeaf0BdF6PPstJ1xLRIC3VurWjbamSc2LATgckW5
pQo5WEcRjhvkIO7pQ/Ma17j5Xx43hH9EipzIKFruI4qT5V3/mY6K33q7zxFIqEXE
Eg6yRazCg0tXnD1+quZVwKuPwN9ggqLQAsd89LllJW9CT9AgjKu42yYLFadKOvu2
/lJuo2doMdrYC2f8/Cs11NgoYwoJy15m3mj5K26rb829pjuuCLzNGbJRMIdXX993
B1hkTHJJ5vDt9rCbK2rdxJoTUQ0T+RvAfbWRmFvJeE8ZY8tgck1Srey4bWZhVGkE
L7+3VuJqioLA7tDCwMzNoOJl/j+FploINfSi2R8rl2wtcflJeub8+I5FF1+Wl25g
cDbADZi0BbCj07gvrv7aAIAZetxfyWUvcQhi1Untskpn4kYKyfa9PIar6bdDzbdv
x6zOgKIb7BKvu+C00NLZcoc0kj+ZXWFYNOagfJh+OdP7ecsZEmOuJmEIgOQfwT1s
hluonFUy7OODO5XGoU9vlJEBDfPlPpEc1BKCfgQG/ZNHtcubr0g=
=5YnI
-END PGP SIGNATURE End Message ---

Processed: swig4.0 bug causes FTBFS of XDMF

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

> clone 1023911 -1
Bug #1023911 [src:xdmf] xdmf FTBFS with SWIG 4.1.0
Bug 1023911 cloned as bug 1024555
> reassign -1 swig
Bug #1024555 [src:xdmf] xdmf FTBFS with SWIG 4.1.0
Bug reassigned from package 'src:xdmf' to 'swig'.
No longer marked as found in versions xdmf/3.0+git20190531-11.
Ignoring request to alter fixed versions of bug #1024555 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#1024557: python3-branca: version "unknown" breaks folium

Package: python3-branca
Version: 0.6.0-1
Severity: serious
Tags: ftbfs
Control: affects -1 python3-folium src:osmnx

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/osmnx.html

...
 ERRORS 
_ ERROR collecting debian/tests/test_osmnx_offline.py __
debian/tests/test_osmnx_offline.py:22: in 
import folium
/usr/lib/python3/dist-packages/folium/__init__.py:51: in 
if tuple(int(x) for x in branca.__version__.split('.')[:2]) < (0, 3):
/usr/lib/python3/dist-packages/folium/__init__.py:51: in 
if tuple(int(x) for x in branca.__version__.split('.')[:2]) < (0, 3):
E   ValueError: invalid literal for int() with base 10: 'unknown'
...


This regression is caused by:

$ python3
Python 3.10.8 (main, Nov  4 2022, 09:21:25) [GCC 12.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import branca
>>> print(branca.__version__)
unknown
>>>

Processed: python3-branca: version "unknown" breaks folium

Processing control commands:

> affects -1 python3-folium src:osmnx
Bug #1024557 [python3-branca] python3-branca: __version__ "unknown" breaks 
folium
Added indication that 1024557 affects python3-folium and src:osmnx

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

Bug#1024015: marked as done (python-gevent FTBFS with Python 3.11 as supported version)

Your message dated Mon, 21 Nov 2022 12:22:22 +
with message-id 
and subject line Bug#1024015: fixed in python-gevent 22.10.2-1
has caused the Debian Bug report #1024015,
regarding python-gevent FTBFS with Python 3.11 as supported version
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.)


-- 
1024015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024015
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-gevent
Version: 21.12.0-3
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=python-gevent&ver=21.12.0-3%2Bb1

...
In file included from src/gevent/_greenlet_primitives.c:764:
/<>/deps/greenlet/greenlet.h:42:5: error: unknown type name 
‘CFrame’
   42 | CFrame* cframe;
  | ^~
error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1
E: pybuild pybuild:379: build: plugin distutils failed with: exit code=1: 
/usr/bin/python3.11 setup.py build 
--- End Message ---
--- Begin Message ---
Source: python-gevent
Source-Version: 22.10.2-1
Done: Jelmer Vernooĳ 

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

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

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

Debian distribution maintenance software
pp.
Jelmer Vernooĳ  (supplier of updated python-gevent 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, 21 Nov 2022 11:52:25 +
Source: python-gevent
Architecture: source
Version: 22.10.2-1
Distribution: unstable
Urgency: low
Maintainer: Debian Python Team 
Changed-By: Jelmer Vernooĳ 
Closes: 1024015
Changes:
 python-gevent (22.10.2-1) unstable; urgency=low
 .
   * New upstream release.
 + Fixes compatibility with Python 3.11. Closes: #1024015
Checksums-Sha1:
 5f6f8647bc0e0f66999d5c96983176489ceb9b38 2453 python-gevent_22.10.2-1.dsc
 4c298150452e921d5621a54ea7b4b1b29f8b4051 4737568 
python-gevent_22.10.2.orig.tar.gz
 92eeda8644982048a2441d2d570679885f41ab3a 73020 
python-gevent_22.10.2-1.debian.tar.xz
 8ef77a11ff43b870d8dd3be201717842cd203dc3 9948 
python-gevent_22.10.2-1_amd64.buildinfo
Checksums-Sha256:
 abf477bde3101898feddaebc76583c5259a544d7ce3be98e79ee3c5bafa8285a 2453 
python-gevent_22.10.2-1.dsc
 59fef0c7802c77e7392a3f14e46d1288e1ec79484360f8d7f258b10fb3d4934e 4737568 
python-gevent_22.10.2.orig.tar.gz
 e58dc520505e0433118ce2509790654e66e9a96895d47b03a49c588638282eee 73020 
python-gevent_22.10.2-1.debian.tar.xz
 d89ffabbffe7beb0ea74186d68fdb2f18c0afa5aafa6f339831c89aba960cf54 9948 
python-gevent_22.10.2-1_amd64.buildinfo
Files:
 1c516f32431403723d5f434827cce364 2453 python optional 
python-gevent_22.10.2-1.dsc
 b17364c72f43ca9883551ace76a61016 4737568 python optional 
python-gevent_22.10.2.orig.tar.gz
 0f1263628a3f6f61236cbf5f7f48425f 73020 python optional 
python-gevent_22.10.2-1.debian.tar.xz
 65fe39a230e03fc16b1012471c9dc5b6 9948 python optional 
python-gevent_22.10.2-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEsjhixBXWVlpOhsvXV5wWDUyeI+gFAmN7aa0ACgkQV5wWDUye
I+h9VA//QfaRTiTp3qAw/+LxkXSUEXvU/FRjhXBX1KdnLuOyWZ0ZC1CllbgBdbVH
weBe0ekXuzqnoUcl8BovvKVRBa8s3VhEgfF3jujhxkIAL1BQmYmrQZTuznFv3VcA
hMWzgA7ihHgRZ65v0eT+1gWIXg0J+xBpbbpJcLILuDo0MlD2Gcg/zl6lwKXkTxVM
/iG7MSOn5Wopso6gUluZMuxzLO/eP0BV+rq10nC8awRYaZG2fwVg3eUcb1d5q5Ue
UYiD7qI4gHcoH66oJMtO6/sbrTGYhtQnZXBHEZ7HtseS6G3eZW/g2wKn4OH2dfx2
WkkoKYf80HziFO+Iqgodg8Ep4NQPuibUE9s4/M2VW+wVoyxEykE8OS3gX80miu1y
z+vT19xe+5ekvSf3ikP71ci5pYfstb1k1RPsNb8YVapR78KM5QgLqTAHykkji7Tb
P5+1BFmeBRv8hR14YQCelU2TGS/L+Dr0UwbHk5t6J2L1/sCDFuFMLnxqEs+OvqE9
HIYyyBRcjOXNI+MdfZ6xlfSNS9IClViONd84y/90CM6vJtRumI41ueD8B3iHFfSO
mynivXqF/xOklRgxXIanQvuBxhSZ/UAIWb2+mXge2+cIfo2xrvhlF8PFY0llefn+
Oo8Un/3vu3jvpLc1RyFADN//7hBFsESckE2WS3+9c+gpgtg99kY=
=m1aL
-END PGP SIGNATURE End Message ---

Processed: Re: Bug#1024546: python3-spyder: error when I try to install this package

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

> forcemerge 1024008 1024546
Bug #1024008 [python3-spyder] python3-spyder is not installable
Bug #1024546 [python3-spyder] python3-spyder: error when I try to install this 
package
Severity set to 'serious' from 'normal'
1024546 was not blocked by any bugs.
1024546 was not blocking any bugs.
Added blocking bug(s) of 1024546: 1023986
Added indication that 1024546 affects 
src:python-xrt,src:guiqwt,src:guidata,src:spyder-unittest
Added tag(s) ftbfs.
Merged 1024008 1024546
> thanks
Stopping processing here.

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

Bug#1022292: scute: diff for NMU version 1:1.5.0-1.1

Control: tags 1022292 + patch
Control: tags 1022292 + pending

Dear maintainer,

I've prepared an NMU for scute (versioned as 1:1.5.0-1.1) and uploaded 
it to DELAYED/14. Please feel free to tell me if I should cancel it.

cu
Adrian
diff -Nru scute-1.5.0/debian/changelog scute-1.5.0/debian/changelog
--- scute-1.5.0/debian/changelog	2019-01-16 06:34:52.0 +0200
+++ scute-1.5.0/debian/changelog	2022-11-20 00:06:15.0 +0200
@@ -1,3 +1,11 @@
+scute (1:1.5.0-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Delete m4/gpg-error.m4 to get the latest version from
+libgpg-error-dev instead. (Closes: #1022292)
+
+ -- Adrian Bunk   Sun, 20 Nov 2022 00:06:15 +0200
+
 scute (1:1.5.0-1) unstable; urgency=medium
 
   * New from upstram: Final released version of 1.5.0.
diff -Nru scute-1.5.0/debian/clean scute-1.5.0/debian/clean
--- scute-1.5.0/debian/clean	1970-01-01 02:00:00.0 +0200
+++ scute-1.5.0/debian/clean	2022-11-20 00:06:10.0 +0200
@@ -0,0 +1 @@
+m4/gpg-error.m4

Bug#1024559: camv-rnd-{core,-doc}: missing Breaks+Replaces: camv-rnd (<< 1.1.0-2)

2022-11-21 Thread Andreas Beckmann

Package: camv-rnd-core,camv-rnd-doc
Version: 1.1.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Preparing to unpack .../camv-rnd-core_1.1.0-2_amd64.deb ...
  Unpacking camv-rnd-core (1.1.0-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/camv-rnd-core_1.1.0-2_amd64.deb (--unpack):
   trying to overwrite '/etc/camv-rnd/conf_core.lht', which is also in package 
camv-rnd 1.0.2-1
  Errors were encountered while processing:
   /var/cache/apt/archives/camv-rnd-core_1.1.0-2_amd64.deb

  Preparing to unpack .../camv-rnd-doc_1.1.0-2_all.deb ...
  Unpacking camv-rnd-doc (1.1.0-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/camv-rnd-doc_1.1.0-2_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/camv-rnd/Autostyle.html', which is also 
in package camv-rnd 1.0.2-1
  Errors were encountered while processing:
   /var/cache/apt/archives/camv-rnd-doc_1.1.0-2_all.deb


cheers,

Andreas


camv-rnd=1.0.2-1_camv-rnd-core=1.1.0-2.log.gz
Description: application/gzip

Processed: scute: diff for NMU version 1:1.5.0-1.1

Processing control commands:

> tags 1022292 + patch
Bug #1022292 [src:scute] scute: FTBFS: configure: error:You need libgpg-error 
to build this program.
Added tag(s) patch.
> tags 1022292 + pending
Bug #1022292 [src:scute] scute: FTBFS: configure: error:You need libgpg-error 
to build this program.
Added tag(s) pending.

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

Processed: block 1022305 with 1023764

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

> block 1022305 with 1023764
Bug #1022305 {Done: Thomas Goirand } [src:networking-l2gw] 
networking-l2gw: FTBFS: oslo_config.cfg.NoSuchOptError: no such option 
api_extensions_path in group [DEFAULT]
1022305 was not blocked by any bugs.
1022305 was not blocking any bugs.
Added blocking bug(s) of 1022305: 1023764
> thanks
Stopping processing here.

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

Bug#934664: marked as done (shush: fails to send email)

Your message dated Mon, 21 Nov 2022 12:51:47 +
with message-id 
and subject line Bug#934664: fixed in shush 1.2.3-5.1
has caused the Debian Bug report #934664,
regarding shush: fails to send email
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.)


-- 
934664: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934664
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: shush
Version: 1.2.3-5+b2
Severity: important

Dear Maintainer,

I noticed that recent upgrade of shush (from 1.2.3-5 to 1.2.3-5+b2)
somehow prevents shush from sending mail. 

I have some shush configuration files (for backup jobs) that I regularly
run each night via cron. After I upgraded shush yesterday, the mail
reports didn't arrive any more, which was odd. So I manually ran shush
with the same configuration file, and this interesting bit of output
showed up:

> shush: execv(NOSENDMAIL): No such file or directory
> shush encountered the following error(s) while running
> "duply-rootfs.conf" on host fik:
> 
> The impossible just happened: line 51 in file exec.c was reached!
> shush encountered the following error(s) while running
> "duply-rootfs.conf" on host fik:
> 
> sendmail for report "success" died from Aborted

If I simply rebuild the shush package from its source (via apt-get source,
and dpkg-buildpackage), the issue goes away; shush sends the report via
email as it is supposed to do.

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

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

Versions of packages shush depends on:
ii  libc6 2.28-10
ii  libpcre3  2:8.39-12+b1

shush recommends no packages.

shush suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: shush
Source-Version: 1.2.3-5.1
Done: Adrian Bunk 

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated shush package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 12 Nov 2022 01:26:36 +0200
Source: shush
Architecture: source
Version: 1.2.3-5.1
Distribution: unstable
Urgency: medium
Maintainer: Dario Minnucci 
Changed-By: Adrian Bunk 
Closes: 934664 1003543
Changes:
 shush (1.2.3-5.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/rules: Export CRONTAB to fix crontab installation,
 thanks to Antoine Duranel. (Closes: #1003543)
   * debian/rules: Export SENDMAIL to fix email sending,
 thanks to Uroš Golja. (Closes: #934664)
Checksums-Sha1:
 76d56396496949fe32609150094915026430fe28 1840 shush_1.2.3-5.1.dsc
 f976ae5af7d5054d64fc3853e15df4f00c1d613c 5508 shush_1.2.3-5.1.debian.tar.xz
Checksums-Sha256:
 9010dbbedd252655c0ecff702644e0368abaaf61698ab465e367ef0105349c36 1840 
shush_1.2.3-5.1.dsc
 bca1edcad284ba05b829694840ea23524dd6aff2a317fe5a1092754c472624e3 5508 
shush_1.2.3-5.1.debian.tar.xz
Files:
 bdad6b27a7aecc142ea712757d701648 1840 admin extra shush_1.2.3-5.1.dsc
 a796f89ef32fe0514d55aaf2ca9eab8e 5508 admin extra shush_1.2.3-5.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmNu3oMACgkQiNJCh6LY
mLHFnRAAqn+KIlT1QYWHBwFqLRN3YrABURXO6kHH2ip8Uoptam3bu4rkdGgPmU9G
amStrFF/5gFXsgzgE5lRBPlxIVYynoM7/63ovgyGlmhZXzMl6pyAOpqLicp1bsyW
0Y/OenwvgUvv9yGCocRw6ZxAYB5bVtIRfzDlAfGiZq/ZzJV5O33h67mXJA/QmdxR
XJUL5y5fpTLZijXPBTB84hCi49U4Qs3j1gxIrvMqnh1/9QhZty+zaoRzALeKS21Q
AbJbyVwDOdQdLq0eARpwuNdfT9ho3P90zf6tuzXMUdrUfOGSjItrWCxnRfavNXpX
+B3g1275DEr8DnlZpul/v4T9nrRMuwFIq0JqwWB4bJv/ZWT7/BgabVzeqoGYjRqY
Whhx8ec6VK+8OztMr6f2p8pdtSHfh/+fuMa70N45JFvr0qssTXrHgcnNJbCdvCW2
qx+EfMa7QEQHC9Qpaqyvc4w0nuniPplEPGLbQp77b6bNhXT3jREHR0RZzOzUScAK
69PCQ1un4q5eWB2m/YscgQ4eAs

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

Your message dated Mon, 21 Nov 2022 12:50:24 +
with message-id 
and subject line Bug#965591: fixed in iitalian 1:2.3-3.1
has caused the Debian Bug report #965591,
regarding iitalian: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.

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

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


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

Hi,

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

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

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

  * Compat 7 is the bare minimum


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

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


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


Thanks,
~Niels


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

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

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

Mind you, it is still your responsibility to ensure that the upload
makes it into testing even if you upload before that date.
--- End Message ---
--- Begin Message ---
Source: iitalian
Source-Version: 1:2.3-3.1
Done: Adrian Bunk 

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

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

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated iitalian 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: Fri, 11 Nov 2022 23:53:01 +0200
Source: iitalian
Architecture: source
Version: 1:2.3-3.1
Distribution: unstable
Urgency: medium
Maintainer: Francesco Paolo Lovergine 
Changed-By: Adrian Bunk 
Closes: 965591 996361 999201
Changes:
 iitalian (1:2.3-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/compat: 5 -> 7. (Closes: #965591)
   * debian/rules: Add build-{arch,indep}. (Closes: #999201)
   * Rebuild with new ispell. (Closes: #996361)
Checksums-Sha1:
 ca54e2291e83e8feffa1b1eee56e6a8b2148d4a4 1703 iitalian_2.3-3.1.dsc
 8d33818e2117cfcc8a80d9fdd7a14042cf8c410d 3655 iitalian_2.3-3.1.diff.gz
Checksums-Sha256:
 a0582c7f020fcf761cc75a5fe3c14656f986e7f2f41d812ea0ea2395e079d9d9 1703 
iitalian_2.3-3.1.dsc
 ff4b6f8c0499ade0f75ee18e356ad344120a50055c5001fa4f1bc3824b3f44c5 3655 
iitalian_2.3-3.1.diff.gz
Files:
 34969f905dbb8f4fed5f694505b37ed6 1703 text optional iitalian_2.3-3.1.dsc
 64b95c99e02bbd5843d528b6396fa361 3655 text optional iitalian_2.3-3.1.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmNuxkAACgkQiNJCh6LY
mLF/oQ//QnAr5l9+FCLEx++VGX8XpBRKUBpRv8oEn8u+TELblIyQB0c+g1UFFWqY
lWlPmvGjJ2evY0ZF15bsYVWuhUU291MuFWR0CtmatfP5ybxz8ZdP0+v4WZwvAeD6
Az09I0Dlsu54sV3qI3g6gXsdRYHwXvFL9PmqL+72Za0aqPOH/tUZXuPJQi/al1+m
tZxdXrOwCM1Yv3g2Vp7tIN+bsYfQoTQXKIajTy0At+EZb2P4TEvKTkNCAmFLCxgD
YpSGAK/lXSIaxtrLsSy7Bb1UeS9L/Zow59LEggAVgbZzOdQVO6rAAOAEPe2Bkq7M
KS16SpktjwvuFxuVE4QoeRdr1D8fPh24Z552bXapzISpzFG/237I4wV2EzTETfoT
ZynRGoJA6pW7nFhhI+7NDhGfrUSLPqGg8XzvBaCI3NfoRk2hh7OgeyXnoNeu5TAm
+9+pG3vI7b0zIL5WI4IK83ozgO0lbymGeIb37yOC9ONrBHf3+Y/eV5zxBut54wQd
QzxR9rqCNzB2+MyTAkuQXkxdxfKnG1er4aIgNPKDm5LE7ht5JhYH/puE1b5vt16b
vpcFaT8yRB/7SxTiTMQwT6jxoW17iLpDR8uV2Y0FmNsfYtni30EfWL75Xzf0tCRh
q6X7K/ovsEYrdNO5sqlhDpBIhDqgLPSyUKMjl8fT9I5N8nTXRjk=
=IeL0
-END PGP SIGNATURE End Message ---

Bug#996361: marked as done (iitalian: Italian hash file not compatible with current version of ispell)

Your message dated Mon, 21 Nov 2022 12:50:24 +
with message-id 
and subject line Bug#996361: fixed in iitalian 1:2.3-3.1
has caused the Debian Bug report #996361,
regarding iitalian: Italian hash file not compatible with current version of 
ispell
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.)


-- 
996361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996361
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: iitalian
Version: 1:2.3-3+b1
Severity: grave
Justification: renders package unusable

$ echo albergo ciao | ispell -d american -l
albergo

$ echo albergo ciao | ispell -d italian -l
Illegal format hash table /usr/lib/ispell/italian.hash - expected magic2 
0x9602, got 0x5053

$ file -L /usr/lib/ispell/[ai]*.hash
/usr/lib/ispell/american.hash: little endian ispell 3.1 hash file, 7-bit, 
capitalization, 52 flags and 1024 string characters
/usr/lib/ispell/italian.hash:  little endian ispell 3.1 hash file, 7-bit, 
capitalization, 52 flags and 512 string characters

$ ls -lL /usr/lib/ispell/[ai]*.hash
-rw-r--r-- 1 root root 1693656 Oct 13 11:19 /usr/lib/ispell/american.hash
-rw-r--r-- 1 root root 1548432 Jul 29  2019 /usr/lib/ispell/italian.hash

Most likely this package was not rebuilt after the last backward-incompatible
change to on-disk format in ispell.  Perhaps a rebuild would solve the problem.

Best regards
g.

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

Kernel: Linux 5.10.0-9-amd64 (SMP w/2 CPU threads)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages iitalian depends on:
ii  debconf [debconf-2.0]  1.5.77
ii  dictionaries-common1.28.4
ii  ispell 3.4.02-2

iitalian recommends no packages.

Versions of packages iitalian suggests:
ii  witalian  1.10

-- debconf information:
  iitalian/languages: italiano (Italian)
  shared/packages-ispell:
--- End Message ---
--- Begin Message ---
Source: iitalian
Source-Version: 1:2.3-3.1
Done: Adrian Bunk 

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated iitalian 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: Fri, 11 Nov 2022 23:53:01 +0200
Source: iitalian
Architecture: source
Version: 1:2.3-3.1
Distribution: unstable
Urgency: medium
Maintainer: Francesco Paolo Lovergine 
Changed-By: Adrian Bunk 
Closes: 965591 996361 999201
Changes:
 iitalian (1:2.3-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/compat: 5 -> 7. (Closes: #965591)
   * debian/rules: Add build-{arch,indep}. (Closes: #999201)
   * Rebuild with new ispell. (Closes: #996361)
Checksums-Sha1:
 ca54e2291e83e8feffa1b1eee56e6a8b2148d4a4 1703 iitalian_2.3-3.1.dsc
 8d33818e2117cfcc8a80d9fdd7a14042cf8c410d 3655 iitalian_2.3-3.1.diff.gz
Checksums-Sha256:
 a0582c7f020fcf761cc75a5fe3c14656f986e7f2f41d812ea0ea2395e079d9d9 1703 
iitalian_2.3-3.1.dsc
 ff4b6f8c0499ade0f75ee18e356ad344120a50055c5001fa4f1bc3824b3f44c5 3655 
iitalian_2.3-3.1.diff.gz
Files:
 34969f905dbb8f4fed5f694505b37ed6 1703 text optional iitalian_2.3-3.1.dsc
 64b95c99e02bbd5843d528b6396fa361 3655 text optional iitalian_2.3-3.1.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmNuxkAACgkQiNJCh6LY
mLF/oQ//QnAr5l9+FCLEx++VGX8XpBRKUBpRv8oEn8u+TELblIyQB0c+g1UFFWqY
lWlPmvGjJ2evY0ZF15bsYVWuhUU291MuFWR0CtmatfP5ybxz8ZdP0+v4WZwvAeD6
Az09I0Dlsu54sV3qI3g6gXsdRYHwXvFL9PmqL+72Za0aqPOH/tUZXuPJQi/al1+m
tZxdXrOwCM1Yv3g2Vp7tIN+bsYfQoTQXKIajTy0At+EZb2P4TEvKTkNCAmFLCxgD
YpSGAK/lXSIaxtrLsSy7Bb1UeS9L/Zow59LEggAVgbZzOdQVO6rAAOAEPe2Bkq7M
KS16SpktjwvuFxuVE4QoeRdr1D8fPh24Z552bXapzISpzFG/237I4wV2EzTETfoT
ZynRGoJA6pW7nFhhI+7NDhGfrUSLPqGg8XzvBaCI3NfoRk2hh7OgeyXnoNeu5TAm
+9+pG3vI7b0zIL5WI4IK83ozgO0lbymGeIb37yOC9ONrBHf3+Y/eV5zxBut54wQd
Qz

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

Your message dated Mon, 21 Nov 2022 12:50:24 +
with message-id 
and subject line Bug#999201: fixed in iitalian 1:2.3-3.1
has caused the Debian Bug report #999201,
regarding iitalian: missing required debian/rules targets build-arch and/or 
build-indep
to be marked as done.

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

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


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

Dear maintainer,

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

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

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

Best,

Lucas
--- End Message ---
--- Begin Message ---
Source: iitalian
Source-Version: 1:2.3-3.1
Done: Adrian Bunk 

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated iitalian 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: Fri, 11 Nov 2022 23:53:01 +0200
Source: iitalian
Architecture: source
Version: 1:2.3-3.1
Distribution: unstable
Urgency: medium
Maintainer: Francesco Paolo Lovergine 
Changed-By: Adrian Bunk 
Closes: 965591 996361 999201
Changes:
 iitalian (1:2.3-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/compat: 5 -> 7. (Closes: #965591)
   * debian/rules: Add build-{arch,indep}. (Closes: #999201)
   * Rebuild with new ispell. (Closes: #996361)
Checksums-Sha1:
 ca54e2291e83e8feffa1b1eee56e6a8b2148d4a4 1703 iitalian_2.3-3.1.dsc
 8d33818e2117cfcc8a80d9fdd7a14042cf8c410d 3655 iitalian_2.3-3.1.diff.gz
Checksums-Sha256:
 a0582c7f020fcf761cc75a5fe3c14656f986e7f2f41d812ea0ea2395e079d9d9 1703 
iitalian_2.3-3.1.dsc
 ff4b6f8c0499ade0f75ee18e356ad344120a50055c5001fa4f1bc3824b3f44c5 3655 
iitalian_2.3-3.1.diff.gz
Files:
 34969f905dbb8f4fed5f694505b37ed6 1703 text optional iitalian_2.3-3.1.dsc
 64b95c99e02bbd5843d528b6396fa361 3655 text optional iitalian_2.3-3.1.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmNuxkAACgkQiNJCh6LY
mLF/oQ//QnAr5l9+FCLEx++VGX8XpBRKUBpRv8oEn8u+TELblIyQB0c+g1UFFWqY
lWlPmvGjJ2evY0ZF15bsYVWuhUU291MuFWR0CtmatfP5ybxz8ZdP0+v4WZwvAeD6
Az09I0Dlsu54sV3qI3g6gXsdRYHwXvFL9PmqL+72Za0aqPOH/tUZXuPJQi/al1+m
tZxdXrOwCM1Yv3g2Vp7tIN+bsYfQoTQXKIajTy0At+EZb2P4TEvKTkNCAmFLCxgD
YpSGAK/lXSIaxtrLsSy7Bb1UeS9L/Zow59LEggAVgbZzOdQVO6rAAOAEPe2Bkq7M
KS16SpktjwvuFxuVE4QoeRdr1D8fPh24Z552bXapzISpzFG/237I4wV2EzTETfoT
ZynRGoJA6pW7nFhhI+7NDhGfrUSLPqGg8XzvBaCI3NfoRk2hh7OgeyXnoNeu5TAm
+9+pG3vI7b0zIL5WI4IK83ozgO0lbymGeIb37yOC9ONrBHf3+Y/eV5zxBut54wQd
QzxR9rqCNzB2+MyTAkuQXkxdxfKnG1er4aIgNPKDm5LE7ht5JhYH/puE1b5vt16b
vpcFaT8yRB/7SxTiTMQwT6jxoW17iLpDR8uV2Y0FmNsfYtni30EfWL75Xzf0tCRh
q6X7K/ovsEYrdNO5sqlhDpBIhDqgLPSyUKMjl8fT9I5N8nTXRjk=
=IeL0
-END PGP SIGNATURE End Message ---

Bug#1003543: marked as done (shush: crontab path not defined)

Your message dated Mon, 21 Nov 2022 12:51:47 +
with message-id 
and subject line Bug#1003543: fixed in shush 1.2.3-5.1
has caused the Debian Bug report #1003543,
regarding shush: crontab path not defined
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.)


-- 
1003543: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003543
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: shush
Version: 1.2.3-5+b2
Severity: grave
Justification: renders package unusable


Dear Maintainer,

shush is unable to find crontab path on Debian bullseye (similar to
#758126):
$ shush -i
shush: execv(NOCRONTAB): No such file or directory
shush: The impossible just happened: line 51 in file exec.c was reached!
shush: Nothing to do.


Re-building the package from source after having installed the cron package
fix the issue.

Thank for your work,
Antoine

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

Kernel: Linux 5.14.17-201.fc34.x86_64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages shush depends on:
ii  libc6 2.31-13+deb11u2
ii  libpcre3  2:8.39-13

shush recommends no packages.

shush suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: shush
Source-Version: 1.2.3-5.1
Done: Adrian Bunk 

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated shush package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 12 Nov 2022 01:26:36 +0200
Source: shush
Architecture: source
Version: 1.2.3-5.1
Distribution: unstable
Urgency: medium
Maintainer: Dario Minnucci 
Changed-By: Adrian Bunk 
Closes: 934664 1003543
Changes:
 shush (1.2.3-5.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/rules: Export CRONTAB to fix crontab installation,
 thanks to Antoine Duranel. (Closes: #1003543)
   * debian/rules: Export SENDMAIL to fix email sending,
 thanks to Uroš Golja. (Closes: #934664)
Checksums-Sha1:
 76d56396496949fe32609150094915026430fe28 1840 shush_1.2.3-5.1.dsc
 f976ae5af7d5054d64fc3853e15df4f00c1d613c 5508 shush_1.2.3-5.1.debian.tar.xz
Checksums-Sha256:
 9010dbbedd252655c0ecff702644e0368abaaf61698ab465e367ef0105349c36 1840 
shush_1.2.3-5.1.dsc
 bca1edcad284ba05b829694840ea23524dd6aff2a317fe5a1092754c472624e3 5508 
shush_1.2.3-5.1.debian.tar.xz
Files:
 bdad6b27a7aecc142ea712757d701648 1840 admin extra shush_1.2.3-5.1.dsc
 a796f89ef32fe0514d55aaf2ca9eab8e 5508 admin extra shush_1.2.3-5.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmNu3oMACgkQiNJCh6LY
mLHFnRAAqn+KIlT1QYWHBwFqLRN3YrABURXO6kHH2ip8Uoptam3bu4rkdGgPmU9G
amStrFF/5gFXsgzgE5lRBPlxIVYynoM7/63ovgyGlmhZXzMl6pyAOpqLicp1bsyW
0Y/OenwvgUvv9yGCocRw6ZxAYB5bVtIRfzDlAfGiZq/ZzJV5O33h67mXJA/QmdxR
XJUL5y5fpTLZijXPBTB84hCi49U4Qs3j1gxIrvMqnh1/9QhZty+zaoRzALeKS21Q
AbJbyVwDOdQdLq0eARpwuNdfT9ho3P90zf6tuzXMUdrUfOGSjItrWCxnRfavNXpX
+B3g1275DEr8DnlZpul/v4T9nrRMuwFIq0JqwWB4bJv/ZWT7/BgabVzeqoGYjRqY
Whhx8ec6VK+8OztMr6f2p8pdtSHfh/+fuMa70N45JFvr0qssTXrHgcnNJbCdvCW2
qx+EfMa7QEQHC9Qpaqyvc4w0nuniPplEPGLbQp77b6bNhXT3jREHR0RZzOzUScAK
69PCQ1un4q5eWB2m/YscgQ4eAsPi/gmsiCf2BLHvo6eEgcdsjH4v4JFyrZFxHkdK
hFZrhp+FWmiMKiPpt0wEcX5nCQ9uG6wooWr8dzWFMEJh1CCeboPBnQ8K9GSjw+Sv
WuClIcrQuLBD1XA0vwVw0NYvmFpjLUtl5tBETbEPRpN5Kuc7NOI=
=4zCN
-END PGP SIGNATURE End Message ---

Bug#1024493: Proposed-RM: bs1770gain -- RoQA; inappropriate content

2022-11-21 Thread Leon van Kammen

my few cents: the problem with censorship is, once you start, the
rabbithole is infinite.
Whatever shitty homepage or comment it is, eventually it's just a homepage
or comment.
I think debian-devs should not be going down the rabbithole of scanning all
code for 'bad' words, bad images, suspicious logos etc, as the creativity
of humans in infinite too..
The reactive path also plays in the hands of those activists (expect
"debian turns out to be ran by X" youtube vids).

kind regards

Leon (and hi if we haven't met yet)

On Mon, Nov 21, 2022 at 12:12 PM Petter Reinholdtsen 
wrote:

>
> Personally I find the story of Daryl Davis inspiring, and believe such
> approach have higher chances of success than one using contempt and
> rejection.
>
> https://en.wikipedia.org/wiki/Daryl_Davis >
>  https://www.npr.org/2017/08/20/544861933/how-one-man-convinced-200-ku-klux-klan-members-to-give-up-their-robes
> >
>
> The Homepage URL is a statement of fact about a package, ie its origin
> and where users can check out the upstream information.  It is also
> useful to track down upstream if it move in the future.  It is not a
> useful marketing channel, but can improve search engine ranking slightly
> due to its use within Debian.  I believe the advantages of machine
> readable links to the package origin outweigh any improved search
> ranking, as I believe the latter is very minuscule.
>
> If I understand the objections about the code, it is about the strings
> '#WLM' and 'Nanos gigantum humeris insidentes.'.  The former seem to be
> a reference to 'white lives matters', a sad reaction to the 'black lives
> matter' movement that have gained traction the last few years[1], and
> the latter is a reference to a cristian quote initially from Bernard of
> Chartres, according to wikipedia[2], and later made more known by Isac
> Newton.  As I see it these strings have no operational function for the
> software and I have no attachment to them whatsoever.  I understand that
> the objections is regarding believed intent behind the strings.  I do
> not see any point in spending time discussing them, and thus removed
> them from the binary.  In my opinion they have no marketing or
> promotional value in the source, so I see very little gain from taking
> the extra work to repack the tarball with these 9 lines from the source
> code
>
>  [1] https://en.wikipedia.org/wiki/White_Lives_Matter >
>  [2]  https://en.wikipedia.org/wiki/Standing_on_the_shoulders_of_giants >
>
> --
> Happy hacking
> Petter Reinholdtsen
>
>

-- 
L Ξ Ο N   V Λ N   Κ Λ Μ Μ Ξ N

Senior creative technologist & researcher
https://2wa.isvery.ninja/hello
https://www.linkedin.com/in/leonvankammen

Bug#1024561: Unmaintained, keep out of stable

2022-11-21 Thread Moritz Muehlenhoff

Source: maradns
Version: 2.0.13-1.4
Severity: serious

The last maintainer upload was in 2015 and the version currently in the
archive is way behind current upstream releases (which is at 3.4.07),
we have plenty of maintained DNS servers, keep it out of testing (
and if noone picks it up, remove it from the archive).

Bug#1024562: form FTBFS on 32bit

Source: form
Version: 4.3.0-1
Severity: serious
Tags: ftbfs
Forwarded: https://github.com/vermaseren/form/issues/422

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

...
reken.c: In function ‘Moebius’:
reken.c:3752:28: error: ‘struct R_const’ has no member named ‘numinprimelist’
 3752 | for ( i = 0; i < AR.numinprimelist; i++ ) {
  |^
reken.c:3753:23: error: ‘struct R_const’ has no member named ‘PrimeList’
 3753 | x = AR.PrimeList[i];
  |   ^
make[4]: *** [Makefile:1710: form-reken.o] Error 1

Bug#1013158: facet-analyser: vtk[6,7] removal

2022-11-21 Thread PICCA Frederic-Emmanuel

Hello Anton, I have just pushed a few dependencies in the -dev package in the 
salsa repo

I did not updated the changelog.

Cheers

Fred

Bug#997874: marked as done (django-uwsgi: autopkgtest regression: No module named 'django_uwsgi_ng')

Your message dated Mon, 21 Nov 2022 13:49:47 +
with message-id 
and subject line Bug#997874: fixed in django-uwsgi 1.1.2-3
has caused the Debian Bug report #997874,
regarding django-uwsgi: autopkgtest regression: No module named 
'django_uwsgi_ng'
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.)


-- 
997874: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997874
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: django-uwsgi
Version: 1.1.2-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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

   passfail
django-uwsgi   from testing1.1.2-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. It seems to me
that because the old package is now a dummy package autodep8 doesn't
spot the right module to include. autodep8 has the ability to be taught
the right name of the module to include, see $(man autodep8) under
`PACKAGE-SPECIFIC CONFIGURATION`.

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

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/d/django-uwsgi/1617/log.gz

Testing with python3.9:
Traceback (most recent call last):
  File "", line 1, in 
ModuleNotFoundError: No module named 'django_uwsgi_ng'
autopkgtest [13:09:21]: test autodep8-python3




OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: django-uwsgi
Source-Version: 1.1.2-3
Done: Jelmer Vernooĳ 

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

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

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

Debian distribution maintenance software
pp.
Jelmer Vernooĳ  (supplier of updated django-uwsgi 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, 21 Nov 2022 13:35:39 +
Source: django-uwsgi
Architecture: source
Version: 1.1.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Jelmer Vernooĳ 
Closes: 997874
Changes:
 django-uwsgi (1.1.2-3) unstable; urgency=medium
 .
   [ Mohammed Bilal ]
   * d/t/autopkgtest-pkg-python.conf: set import_name for autodep.
 Closes: #997874
Checksums-Sha1:
 409c0ad3631edd450da13a747b8e9393f2715670 2357 django-uwsgi_1.1.2-3.dsc
 880b4160fae11e446a49666413c88b36ffb481b6 4692 
django-uwsgi_1.1.2-3.debian.tar.xz
 77f09711475cbeffb7da9043f0cc0f3a4348f68f 9089 
django-uwsgi_1.1.2-3_amd64.buildinfo
Checksums-Sha256:
 e84b57236b634dbe0f741ef19a8d2683ecf9657f4afea25068ee3a706732b106 2357 
django-uwsgi_1.1.2-3.dsc
 fef93b28042dfe3c6b47246b9c93d55a63d77fe406ab07444b12f2c49d31e3e3 4692 
django-uwsgi_1.1.2-3.debian.tar.xz
 1c67342b2c2e66e29ce96a0401d83cecae2a45c85d21c53d115b0c486332763a 9089 
django-uwsgi_1.1.2-3_amd64.buildinfo
Files:
 6bab9b527945bd1a2ab32603dc4c0823 2357 python optional django-uwsgi_1.1.2-3.dsc
 9fba2d32fcf89453259321b642b0faff 4692 python optional 
django-uwsgi_1.1.2-3.debian.tar.xz
 6a4dc2c8cf85a7a690feb72457a7f968 9089 python optional 
django-uwsgi_1.1.2-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEsjhixBXWVlpOhsvXV5wWDUyeI+gFAmN7fvYACgkQV5wWDUye
I+gx/hAAqBE1Xg6uYfMLjatm4gJ8K5geMxrMRT1yKKEq33vbqBHULPlH4jXxDsnk
YQMaeu8f49KuhMlIhGUquA7C4In7o5fiNZAPySJVnAyAst9GY0wv/l+9FJ+Znh3e
LenmjwkFJl6m/YlILOlX3vQFfDCi0xnTsOBw4aDQdfGo/J0Pcv7k2UIPLR67aZVY
Eh6z9fmeQze5t+9bPDeaM4V1icUOhGyQjV20jazrIrm1hub7IVUS7e8b7DriStL0
y321vya0p49lZiVpVMcjmKAN9H/U9tp5jULpQS9wyWq6d8gR6d0jHo3BbFpvk0is
FWhh9qzcYOkdMR4YHesYMvBHUtm9mb5Q9BBjr/Tqf2KE67nWgzkQnQUU2K9+

Processed: tagging 1024474

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

> tags 1024474 + ftbfs
Bug #1024474 [src:pacman-package-manager] 
pacman-package-manager_6.0.2-2_mips64el-buildd.changes REJECTED
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#979257: RabbitVCS status?

2022-11-21 Thread Jelmer Vernooĳ

tags 979257 +upstream
forwarded 979257 https://github.com/rabbitvcs/rabbitvcs/issues/34
thanks

There doesn't appear to be much movement on this at all in upstream,
the bug has been open since 2014. There is other upstream activity
though.

Perhaps the best approach would be to drop this specific binary
package for bookworm.

-- 
Jelmer Vernooĳ 
PGP Key: https://www.jelmer.uk/D729A457.asc

Processed: RabbitVCS status?

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

> tags 979257 +upstream
Bug #979257 [rabbitvcs-gedit] rabbitvcs-gedit plugin does not load on gedit 3.8+
Added tag(s) upstream.
> forwarded 979257 https://github.com/rabbitvcs/rabbitvcs/issues/34
Bug #979257 [rabbitvcs-gedit] rabbitvcs-gedit plugin does not load on gedit 3.8+
Set Bug forwarded-to-address to 
'https://github.com/rabbitvcs/rabbitvcs/issues/34'.
> thanks
Stopping processing here.

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

Bug#953630: [Debichem-devel] Bug#953630: openbabel autopkg tests fail on non-amd64 architectures

2022-11-21 Thread Andrius Merkys


Hi,

On 2022-11-20 18:18, Paul Gevers wrote:
 From the BSP in Tilburg, I uploaded the attached NMU to DELAYED/5. 
Please let me know if I should delay more or cancel.


Thanks, IMO this NMU is fine. Similar logic should be applied to the 
build time tests in future, since now their failures are plainly ignored.


Andrius

Bug#1013158: marked as done (facet-analyser: vtk[6,7] removal)

Your message dated Mon, 21 Nov 2022 15:06:08 +
with message-id 
and subject line Bug#1013158: fixed in facet-analyser 
0.0~git20221121142040.6be10b8+ds1-1
has caused the Debian Bug report #1013158,
regarding facet-analyser: vtk[6,7] removal
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.)


-- 
1013158: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013158
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: facet-analyser
Severity: important
User: gl...@debian.org
Usertags: vtk6_vtk7_removal

Dear maintainer,

Debian archive has now three major versions of the VTK (The
Visualization Toolkit) package: vtk6, vtk7 and vtk9. Old vesions
(vtk6 and vtk7) are not supported by upstream and the package itself
is not easy for the mainance.

We aim to drop old and deprecated version vtk6 and vtk7 packages
before the freeze of the Debian 12 Bookworm. The severity of this
ticket will be raised to serious some time for the freeze.

Your package depends on vtk6 or vtk7. Thus we ask you to migrate it
to the latest vtk9 package.

Thanks

Anton 
--- End Message ---
--- Begin Message ---
Source: facet-analyser
Source-Version: 0.0~git20221121142040.6be10b8+ds1-1
Done: Picca Frédéric-Emmanuel 

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

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

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

Debian distribution maintenance software
pp.
Picca Frédéric-Emmanuel  (supplier of updated facet-analyser 
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, 21 Nov 2022 15:40:30 +0100
Source: facet-analyser
Architecture: source
Version: 0.0~git20221121142040.6be10b8+ds1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Picca Frédéric-Emmanuel 
Closes: 1013158 1017211
Changes:
 facet-analyser (0.0~git20221121142040.6be10b8+ds1-1) unstable; urgency=medium
 .
   * New upstream version 0.0~git20221121142040.6be10b8+ds1
   * Bug fix: "FTBFS: build-dependency not installable:
 libinsighttoolkit4-dev", thanks to Lucas Nussbaum (Closes: #1017211).
   * d/control: B-D replace libinsighttoolkit4-dev with libinsighttoolkit5-dev
   * Bug fix: "vtk[6,7] removal", thanks to gl...@debian.org; (Closes:
 #1013158).
Checksums-Sha1:
 e7dff4ea1684dec0d3335f282fa2dc158736c549 2794 
facet-analyser_0.0~git20221121142040.6be10b8+ds1-1.dsc
 d6b440b0a9ff05a4f8fa3e55af0b503988fd0ae4 1188580 
facet-analyser_0.0~git20221121142040.6be10b8+ds1.orig.tar.xz
 c9e7a5cd13bb524fa24442ab365683be52500ab0 9820 
facet-analyser_0.0~git20221121142040.6be10b8+ds1-1.debian.tar.xz
Checksums-Sha256:
 db6f6b5233888b51289fe028b1f52f83580b3375c65cd5284e0ba57aa3fd94ee 2794 
facet-analyser_0.0~git20221121142040.6be10b8+ds1-1.dsc
 423d060c5fb8bf405419729f0262296b524f03ebc5adfdad82bd4d4177f0d7f1 1188580 
facet-analyser_0.0~git20221121142040.6be10b8+ds1.orig.tar.xz
 8998566cdb29a3f31f86e2f8c47ddd491f2e27166d10eb22f4de54a85d11882c 9820 
facet-analyser_0.0~git20221121142040.6be10b8+ds1-1.debian.tar.xz
Files:
 424eb64331d6fdaf8e013a8bf7bc6e52 2794 science optional 
facet-analyser_0.0~git20221121142040.6be10b8+ds1-1.dsc
 214ff98b16dcf73eb27665cb11e53bde 1188580 science optional 
facet-analyser_0.0~git20221121142040.6be10b8+ds1.orig.tar.xz
 80670dc9345f6466296b731a38d97340 9820 science optional 
facet-analyser_0.0~git20221121142040.6be10b8+ds1-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE2bRTt5m4gw2UXmoKW/VOXhK5ALsFAmN7jnIRHHBpY2NhQGRl
Ymlhbi5vcmcACgkQW/VOXhK5ALtMRxAAwNt8lS3+lLeyX4XEeR9aYioeiO4QTm48
y8OVDb7BEaFe8LXt8BScKQYU0Dkq3JVlRfs2I44V34f44Gr820AsLr53KYNftYJZ
9vX3i+Cps26LfrioNCZPArY1ZIHHzumiP45PgbrbNeYW4xLNR75QULK1ai7bq9bj
CwVjE6vb+LD605ruVzjsEFA1mO/VT24RQ882Ba1k1PLgjBw+A4qGx4SYGmmSNCQx
iHjtCLGIM8aulo+XLerFDMaVGl7NwLHLW+n+UGfnrPPGA/TPCH7ajxsp9SNmP0QK
tgy+IrrQsUhKa0RyiZqYbn0I5h5lCMXxSusZBLDMWPlwLEISej4SFKIaWWRwwY4K
3M4zxEG5WjWDUiNgpoCycsKt0g5KeQ7YB5tn1QAzMGHCJJtji/PwJAyqK0pl579z
92AelL3L+ayIaqWeRRnW0JJw1Uc1JpZ28Gmf+K1HtindTbf0CPoKnGbgyZEEE1sX
J4x3uNQ20Bqh+VaBdT9dvNGntkymhSK08NCtM3SklNWiX5DAPsk6YZc9PsFjqyHi
dBZHKHFKcQLwSDJTt9wIR5JYtCGHYqb26HK1RoVLlYFTIrp+WmQ

Bug#1017211: marked as done (facet-analyser: FTBFS: build-dependency not installable: libinsighttoolkit4-dev)

Your message dated Mon, 21 Nov 2022 15:06:08 +
with message-id 
and subject line Bug#1017211: fixed in facet-analyser 
0.0~git20221121142040.6be10b8+ds1-1
has caused the Debian Bug report #1017211,
regarding facet-analyser: FTBFS: build-dependency not installable: 
libinsighttoolkit4-dev
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.)


-- 
1017211: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017211
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: facet-analyser
Version: 0.0~git20210718121026.869873a+ds1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220813 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: cmake, debhelper-compat (= 13), 
> libdouble-conversion-dev, libfftw3-dev, libgdcm-tools, 
> libinsighttoolkit4-dev, liblz4-dev, libopengl-dev, libqt5opengl5-dev, 
> libqt5svg5-dev, libutfcpp-dev, libvtk7-dev, libvtkgdcm-cil, libvtkgdcm-dev, 
> libvtkgdcm-java, libx11-dev, paraview-dev, python3-paraview, python3-vtkgdcm, 
> qtbase5-dev, qttools5-dev, qtxmlpatterns5-dev-tools, vtk7, xalan, xvfb, 
> xauth, build-essential, fakeroot
> Filtered Build-Depends: cmake, debhelper-compat (= 13), 
> libdouble-conversion-dev, libfftw3-dev, libgdcm-tools, 
> libinsighttoolkit4-dev, liblz4-dev, libopengl-dev, libqt5opengl5-dev, 
> libqt5svg5-dev, libutfcpp-dev, libvtk7-dev, libvtkgdcm-cil, libvtkgdcm-dev, 
> libvtkgdcm-java, libx11-dev, paraview-dev, python3-paraview, python3-vtkgdcm, 
> qtbase5-dev, qttools5-dev, qtxmlpatterns5-dev-tools, vtk7, xalan, xvfb, 
> xauth, build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [529 B]
> Get:5 copy:/<>/apt_archive ./ Packages [604 B]
> Fetched 2096 B in 0s (92.0 kB/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> 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:
>  sbuild-build-depends-main-dummy : Depends: libinsighttoolkit4-dev but it is 
> not installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2022/08/13/facet-analyser_0.0~git20210718121026.869873a+ds1-2_unstable.log

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

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: facet-analyser
Source-Version: 0.0~git20221121142040.6be10b8+ds1-1
Done: Picca Frédéric-Emmanuel 

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

Bug#1019830: marked as done (codeblocks: Please transition to wxwidgets3.2)

Your message dated Mon, 21 Nov 2022 15:05:52 +
with message-id 
and subject line Bug#1019830: fixed in codeblocks 20.03+svn13046-0.1
has caused the Debian Bug report #1019830,
regarding codeblocks: Please transition to wxwidgets3.2
to be marked as done.

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

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


-- 
1019830: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019830
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: codeblocks
Severity: normal
Control: block 1019416 by -1

Hi,

Please transition codeblocks from wxwidgets3.0 to wxwidgets3.2.

wxWidgets 3.2 (a new API/ABI stable release) has been released a few
months ago and is now packaged in unstable as wxwidgets3.2. Upstream
has stopped supporting wxWidgets 3.0, so the Debian wx team would
like to migrate all wx package users to wxwidgets3.2 for bullseye,
with the plan to remove wxwidgets3.0 before release.

For most packages, the transition should be as simple as changing
Build-Depends from libwxgtk3.0-gtk3-dev to libwxgtk3.2-dev. Some
packages may require small patches; I'm happy to help with those (and
I have some already from working on this transition in Fedora
already).

Thanks, Scott 
--- End Message ---
--- Begin Message ---
Source: codeblocks
Source-Version: 20.03+svn13046-0.1
Done: Bo YU 

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

Debian distribution maintenance software
pp.
Bo YU  (supplier of updated codeblocks package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 20 Nov 2022 15:12:29 +0800
Source: codeblocks
Architecture: source
Version: 20.03+svn13046-0.1
Distribution: unstable
Urgency: medium
Maintainer: David Paleino 
Changed-By: Bo YU 
Closes: 1011502 1019830
Changes:
 codeblocks (20.03+svn13046-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream version 20.03+svn13046. (Closes: #1019830)
   * Upstream support riscv64. (Closes: #1011502)
   * d/patch: add revision.m4
   * adjust usr/share/appdata/codeblocks.appdata.xml
 to usr/share/metainfo/codeblocks.appdata.xml
   * add source/lintian-overrides
   * rebase d/patch
Checksums-Sha1:
 39403a36612d701aaaf7ad4129f4c37e5c1e632a 2381 codeblocks_20.03+svn13046-0.1.dsc
 dbb3183c52be4b0c3616fcf7ec101cf699d2b2c6 21611012 
codeblocks_20.03+svn13046.orig.tar.gz
 f34fd8441b4f9863680d1ef0973efcc921388d7b 26308 
codeblocks_20.03+svn13046-0.1.debian.tar.xz
 a820cac2c35c1c07a53d2d6ba5b0cdfb7edb723d 14355 
codeblocks_20.03+svn13046-0.1_source.buildinfo
Checksums-Sha256:
 decf7bc8b9fefa7dd150164f863af7cb7a409b9e8c96cd0857bb5a71065d513c 2381 
codeblocks_20.03+svn13046-0.1.dsc
 e513233a898cd233b6fb0bdba62a43bbdd156d642a815b34f8be7c0209b23f39 21611012 
codeblocks_20.03+svn13046.orig.tar.gz
 938fed13160d19862731acd46f706239ef065d8002eb86a1dffc183365342d75 26308 
codeblocks_20.03+svn13046-0.1.debian.tar.xz
 a21939cccbae43b6d38a3797c473a6353e89bc23ee73fd57504afd68837008a8 14355 
codeblocks_20.03+svn13046-0.1_source.buildinfo
Files:
 f9676e313335817077b074dbaf67cb55 2381 x11 optional 
codeblocks_20.03+svn13046-0.1.dsc
 2fbcedbf3190c6a21d132a9afd82f1fd 21611012 x11 optional 
codeblocks_20.03+svn13046.orig.tar.gz
 24cc038fa4c4f6a1e830ce84ec647a14 26308 x11 optional 
codeblocks_20.03+svn13046-0.1.debian.tar.xz
 505e9234d68fecea155403a22b3b608e 14355 x11 optional 
codeblocks_20.03+svn13046-0.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmN7kLEQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFPaDC/4wQ+g9hDQ9MtebHg/Ko3RGpkYlB53d2hFL
01+2cK4dDBU6KjTp9bY3owwin9RLYjcWyrZJzpB/3e9zRyARcs2xX6mRefsacsmu
e+bsou6DJSAUGCRJz2YfE5gKb7BaClQjDE7GKVn5yzdFnyB77u+h35MMkzMI+u19
3z3RFYLyua8Ywh2NkyWwmeZ1XlBIy9Je6SZvFxnUUOYg/q+pB89iUest11ipob7P
hBD8E+tNeRE3WRLcT1Iei2g3r/dLM5qCYibSo2GGAuWjiy5ZtHOOzpfhzaUOq9In
FS1Yc9DZ21nLrgrX+aCZck8agi/bLRWnw4whLXBfz1Xe3TI3Ib8366YJoDw2tI0S
+BNY3tODSoK1gI1AFH1oG42HAAlZpipFct9BY6ACAkThGXsa3fAZwMbaZ31s8vXp
v5Ttr410eNzoHmQ3xo8FwN97sYAAAysym0R8fTLBuPUfQ0RbOnk3Wc5VuLPGA7s5
aEh3bZmRSicAJirekqZZe3rl6/DmlHY=
=qyrX
-END PGP SIGNATURE End

Bug#1004869: marked as done (python-xarray: autopkgtest regression on i386)

Your message dated Mon, 21 Nov 2022 15:12:02 +
with message-id 
and subject line Bug#1004869: fixed in python-xarray 2022.11.0-2
has caused the Debian Bug report #1004869,
regarding python-xarray: autopkgtest regression on i386
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.)


-- 
1004869: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004869
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-xarray
Version: 0.21.0-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Hi Maintainer

python-xarray's autopkgtests are failing on the i386 architecture [1].
I've copied what I hope is the relevant part of the log below.

Regards
Graham


[1] https://ci.debian.net/packages/p/python-xarray/unstable/i386/


=== FAILURES ===
___ test_interpolate_chunk_advanced[linear] 

method = 'linear'

@requires_scipy
@requires_dask
@pytest.mark.parametrize("method", ["linear", "nearest"])
@pytest.mark.filterwarnings("ignore:Increasing number of chunks")
def test_interpolate_chunk_advanced(method):
"""Interpolate nd array with an nd indexer sharing coordinates."""
# Create original array
x = np.linspace(-1, 1, 5)
y = np.linspace(-1, 1, 7)
z = np.linspace(-1, 1, 11)
t = np.linspace(0, 1, 13)
q = np.linspace(0, 1, 17)
da = xr.DataArray(
data=np.sin(x[:, np.newaxis, np.newaxis, np.newaxis, np.newaxis])
* np.cos(y[:, np.newaxis, np.newaxis, np.newaxis])
* np.exp(z[:, np.newaxis, np.newaxis])
* t[:, np.newaxis]
+ q,
dims=("x", "y", "z", "t", "q"),
coords={"x": x, "y": y, "z": z, "t": t, "q": q, "label":
"dummy_attr"},
)

# Create indexer into `da` with shared coordinate
("full-twist" Möbius strip)
theta = np.linspace(0, 2 * np.pi, 5)
w = np.linspace(-0.25, 0.25, 7)
r = xr.DataArray(
data=1 + w[:, np.newaxis] * np.cos(theta),
coords=[("w", w), ("theta", theta)],
)

x = r * np.cos(theta)
y = r * np.sin(theta)
z = xr.DataArray(
data=w[:, np.newaxis] * np.sin(theta),
coords=[("w", w), ("theta", theta)],
)

kwargs = {"fill_value": None}
expected = da.interp(t=0.5, x=x, y=y, z=z, kwargs=kwargs, method=method)

da = da.chunk(2)
x = x.chunk(1)
z = z.chunk(3)
actual = da.interp(t=0.5, x=x, y=y, z=z, kwargs=kwargs, method=method)
>   assert_identical(actual, expected)
E   AssertionError: Left and right DataArray objects are not identical
E
E   Differing values:
E   L
E   array([[[ 3.302241e-01,  3.927241e-01, ...,  1.267724e+00,
 1.330224e+00],
E   [ 1.239764e-17,  6.25e-02, ...,  9.375000e-01,
 1.00e+00],
E   ...,
E   [-5.560517e-17,  6.25e-02, ...,  9.375000e-01,
 1.00e+00],
E   [ 3.302241e-01,  3.927241e-01, ...,  1.267724e+00,
 1.330224e+00]],
E
E  [[ 3.603946e-01,  4.228946e-01, ...,  1.297895e+00,
 1.360395e+00],
E   [ 1.346533e-17,  6.25e-02, ...,  9.375000e-01,
 1.00e+00],
E   ...,
E   [-5.109700e-17,  6.25e-02, ...,  9.375000e-01,
 1.00e+00],
E   [ 3.603946e-01,  4.228946e-01, ...,  1.297895e+00,
 1.360395e+00]],
E
E  ...,
E
E  [[ 4.810764e-01,  5.435764e-01, ...,  1.418576e+00,
 1.481076e+00],
E   [ 1.878775e-17,  6.25e-02, ...,  9.375000e-01,
 1.00e+00],
E   ...,
E   [-3.662163e-17,  6.25e-02, ...,  9.375000e-01,
 1.00e+00],
E   [ 4.810764e-01,  5.435764e-01, ...,  1.418576e+00,
 1.481076e+00]],
E
E  [[ 5.112469e-01,  5.737469e-01, ...,  1.448747e+00,
 1.511247e+00],
E   [ 2.044535e-17,  6.25e-02, ...,  9.375000e-01,
 1.00e+00],
E   ...,
E   [-3.371783e-17,  6.25e-02, ...,  9.375000e-01,
 1.00e+00],
E   [ 5.112469e-01,  5.737469e-01, ...,  1.448747e+00,
 1.511247e+00]]])
E   R
E   array([[[ 3.302241e-01,  3.927241e-01, ...,  1.267724e+00,
 1.330224e+00],
E   [ 1.239764e-17,  6.25e-02, ...,  9.375000e-01,
 1.00e+00],
E   ...,
E   [-5.560

Bug#1023222: marked as done (python-xarray: autopkgtest regression on s390x: segmentation fault)

Your message dated Mon, 21 Nov 2022 15:12:02 +
with message-id 
and subject line Bug#1023222: fixed in python-xarray 2022.11.0-2
has caused the Debian Bug report #1023222,
regarding python-xarray: autopkgtest regression on s390x: segmentation fault
to be marked as done.

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

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


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

Source: python-xarray
Version: 2022.10.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
python-xarray  from testing2022.10.0-1
all others from testingfrom testing

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

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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/s390x/p/python-xarray/27672266/log.gz

[ 90%]
tests/test_sparse.py::test_variable_property[nbytes] PASSED 
[ 90%]
tests/test_sparse.py::test_variable_property[ndim] PASSED 
[ 90%]
tests/test_sparse.py::test_variable_property[values] XFAIL (Coercion...) 
[ 90%]
tests/test_sparse.py::test_variable_method[obj.all(*(), **{})-False] 
Fatal Python error: Segmentation fault


Current thread 0x03ff91575040 (most recent call first):
  File "/usr/lib/python3/dist-packages/sparse/_coo/core.py", line 1562 
in _grouped_reduce
  File "/usr/lib/python3/dist-packages/sparse/_coo/core.py", line 687 
in _reduce_calc
  File "/usr/lib/python3/dist-packages/sparse/_sparse_array.py", line 
360 in reduce
  File "/usr/lib/python3/dist-packages/sparse/_sparse_array.py", line 
278 in _reduce
  File "/usr/lib/python3/dist-packages/sparse/_sparse_array.py", line 
307 in __array_ufunc__
  File "/usr/lib/python3/dist-packages/sparse/_sparse_array.py", line 
490 in all
  File "/usr/lib/python3/dist-packages/sparse/_sparse_array.py", line 
268 in __array_function__

  File "<__array_function__ internals>", line 5 in all
  File "/usr/lib/python3/dist-packages/xarray/core/variable.py", line 
1901 in reduce
  File "/usr/lib/python3/dist-packages/xarray/core/common.py", line 73 
in wrapped_func
  File "/usr/lib/python3/dist-packages/xarray/tests/test_sparse.py", 
line 69 in __call__
  File "/usr/lib/python3/dist-packages/xarray/tests/test_sparse.py", 
line 231 in test_variable_method
  File "/usr/lib/python3/dist-packages/_pytest/python.py", line 192 in 
pytest_pyfunc_call
  File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 39 in 
_multicall
  File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 80 in 
_hookexec
  File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 265 in 
__call__
  File "/usr/lib/python3/dist-packages/_pytest/python.py", line 1761 in 
runtest
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 166 in 
pytest_runtest_call
  File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 39 in 
_multicall
  File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 80 in 
_hookexec
  File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 265 in 
__call__
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 259 in 

  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 338 in 
from_call
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 258 in 
call_runtest_hook
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 219 in 
call_and_report
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 130 in 
runtestprotocol
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 111 in 
pytest_runtest_protocol
  File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 39 in 
_multicall
  File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 80 in 
_hookexec
  File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 265 in 
__call__
  File "/usr/lib/python3/dist-packages/_pytest/main.py", line 347 in 
pytest_runtestloop
  File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 39 in 
_multical

Bug#1022255: marked as done (python-xarray breaks satpy autopkgtest)

Your message dated Mon, 21 Nov 2022 15:12:02 +
with message-id 
and subject line Bug#1022255: fixed in python-xarray 2022.11.0-2
has caused the Debian Bug report #1022255,
regarding python-xarray breaks satpy autopkgtest
to be marked as done.

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

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


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

Source: python-xarray, satpy
Control: found -1 python-xarray/2022.10.0-1
Control: found -1 satpy/0.37.1-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

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


   passfail
python-xarray  from testing2022.10.0-1
satpy  from testing0.37.1-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 python-xarray to 
testing [1]. Due to the nature of this issue, I filed this bug report 
against both packages. Can you please investigate the situation and 
reassign the bug to the right package?


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/s/satpy/27389134/log.gz

 TestNIRReflectance.test_no_sunz_no_co2 



self = testMethod=test_no_sunz_no_co2>

calculator = 
apply_modifier_info = id='139765627664464'>

sza = 

@mock.patch('satpy.modifiers.spectral.sun_zenith_angle')
@mock.patch('satpy.modifiers.NIRReflectance.apply_modifier_info')
@mock.patch('satpy.modifiers.spectral.Calculator')
def test_no_sunz_no_co2(self, calculator, apply_modifier_info, sza):
"""Test NIR reflectance compositor with minimal parameters."""
calculator.return_value = mock.MagicMock(
reflectance_from_tbs=self.refl_from_tbs)
sza.return_value = self.da_sunz
from satpy.modifiers.spectral import NIRReflectance
comp = NIRReflectance(name='test')
info = {'modifiers': None}
res = comp([self.nir, self.ir_], optional_datasets=[], **info)
>   self.get_lonlats.assert_called()

/usr/lib/python3/dist-packages/satpy/tests/test_modifiers.py:244: _ _ _ 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

self = 

def assert_called(self):
"""assert that the mock was called at least once
"""
if self.call_count == 0:
msg = ("Expected '%s' to have been called." %
   (self._mock_name or 'mock'))

  raise AssertionError(msg)

E   AssertionError: Expected 'get_lonlats' to have been called.

/usr/lib/python3.10/unittest/mock.py:888: AssertionError
___ TestSceneLoading.test_load_comp4 
___


self = 

def test_load_comp4(self):
"""Test loading a composite that depends on a composite."""
scene = Scene(filenames=['fake1_1.txt'], reader='fake1')
scene.load(['comp4'])
loaded_ids = list(scene._datasets.keys())

  assert len(loaded_ids) == 1

E   AssertionError: assert 2 == 1
E+  where 2 = len([DataID(name='comp2'), DataID(name='ds3', 
modifiers=())])


/usr/lib/python3/dist-packages/satpy/tests/test_scene.py:1059: 
AssertionError
-- Captured log call 
---
WARNING  satpy.scene:scene.py:1275 The following datasets were not 
created and may require resampling to be generated: DataID(name='comp4')
___ TestSceneLoading.test_load_multiple_resolutions 



self = 

def test_load_multiple_resolutions(self):
"""Test loading a dataset has multiple resolutions available 
with different resolutions."""

scene = Scene(filenames=['fake1_1.txt'], reader='fake1')
comp25 = make_cid(name='comp25', resolution=1000)
scene[comp25] = xr.DataArray([], attrs={'name': 'comp25', 
'resolution': 1000})

scene.load(['comp25'], resolution=500)
loaded_ids = list(scene._datasets.keys())

  assert len(loaded_ids) == 2

E   AssertionError: assert 3

Bug#1013827: marked as done (FTBFS, post-build tests fail on architectures armel and armhf)

Your message dated Mon, 21 Nov 2022 15:08:21 +
with message-id 
and subject line Fixed in 0.20.0-2
has caused the Debian Bug report #1013827,
regarding FTBFS, post-build tests fail on architectures armel and armhf
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.)


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

Source: varnish-modules
Version: 0.20.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the 
past)


Dear Maintainer,

This version fails to build on Ubuntu Kinetic with varnish 7.1.0-6 only on
armhf. The builds for all other architectures succeed.

Build log: 
https://launchpadlibrarian.net/609387386/buildlog_ubuntu-kinetic-armhf.varnish-modules_0.20.0-1_BUILDING.txt.gz


Failing tests:
FAIL: tests/bodyaccess/test01.vtc
FAIL: tests/bodyaccess/test03.vtc
FAIL: tests/bodyaccess/test05.vtc
FAIL: tests/header/append.vtc
FAIL: tests/header/copy.vtc
FAIL: tests/header/get.vtc
FAIL: tests/header/import.vtc
FAIL: tests/header/keep-others.vtc
FAIL: tests/header/remove.vtc
FAIL: tests/header/some-data.vtc
FAIL: tests/header/regsub.vtc
FAIL: tests/saintmode/test04.vtc
FAIL: tests/saintmode/test05.vtc
FAIL: tests/str/test01.vtc
FAIL: tests/str/test02.vtc
FAIL: tests/str/test03.vtc
FAIL: tests/str/test04.vtc
FAIL: tests/str/test05.vtc
FAIL: tests/str/test06.vtc
FAIL: tests/str/test08.vtc
FAIL: tests/tcp/01-dumpinfo.vtc
FAIL: tests/tcp/02-congestion.vtc
FAIL: tests/tcp/03-read-tcpinfo.vtc
FAIL: tests/tcp/04-pacing.vtc
FAIL: tests/var/test01.vtc
FAIL: tests/var/test02.vtc
FAIL: tests/var/test03.vtc
FAIL: tests/var/test04.vtc
FAIL: tests/var/test05.vtc
FAIL: tests/var/test06.vtc
FAIL: tests/vsthrottle/test01.vtc
FAIL: tests/vsthrottle/test02.vtc
FAIL: tests/vsthrottle/test04.vtc
FAIL: tests/xkey/test01.vtc
FAIL: tests/xkey/test02.vtc
FAIL: tests/xkey/test03.vtc
FAIL: tests/xkey/test04.vtc
FAIL: tests/xkey/test05.vtc
FAIL: tests/xkey/test06.vtc
FAIL: tests/xkey/test07.vtc
FAIL: tests/xkey/test08.vtc
FAIL: tests/xkey/test09.vtc
FAIL: tests/xkey/test10.vtc
FAIL: tests/xkey/test11.vtc
FAIL: tests/xkey/test13.vtc
--- End Message ---
--- Begin Message ---

To whom it may concern,

The maintainer provided a workaround in version 0.20.0-2, that disables 
the build on architectures where

tests fail.

Kind regards,
Luís Infante da Câmara--- End Message ---

Processed: Re: python3-branca: version "unknown" breaks folium

Processing control commands:

> tags -1 patch
Bug #1024557 [python3-branca] python3-branca: __version__ "unknown" breaks 
folium
Added tag(s) patch.

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

Bug#1024557: python3-branca: version "unknown" breaks folium

2022-11-21 Thread Nilesh Patra

Control: tags -1 patch

Hi,

The fix is just a one-liner. If you do not fix it in next seven days,
I will NMU it.
(I prefer not going the delayed queue route)

diff --git a/debian/control b/debian/control
index 7eff938..fce9cfa 100644
--- a/debian/control
+++ b/debian/control
@@ -6,6 +6,7 @@ Build-Depends: debhelper-compat (= 13),
  dh-python,
  python3,
  python3-setuptools,
+ python3-setuptools-scm,
  python3-jinja2,
  python3-six
 X-Python3-Version: >= 3.7

-- 
Best,
Nilesh


signature.asc
Description: PGP signature

Bug#1024520: debhelper: Use of uninitialized value $dest in -l at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 662.

2022-11-21 Thread Niels Thykier


Axel Beckert:

Hi Niels,

Niels Thykier wrote:
[...]

It was indeed an oversight.


Yep, looked like that: Was the only occurence far away from the
remaining calls.

Also wondered if that call better should have been a simple
install_file() instead.



The $mode parameter gets in the way.  However, no one is using that 
function outside of debhelper, so I can just simplify it so we can use 
install_file instead - done!


Thanks for the suggestion.


I will probably not change anything for now. Having slept on it and given
additional evidence, I think the underlying issue was a bug in fakeroot
(#1023286 is most my most likely candidate) and not a bug in debhelper


I see. Given that comment and the fact that #1023286 only affects 32
bit architectures, I think that #1024261 (in debhelper) is related and
might have the same cause as only 32-bit files seem to be affected.
(Or was #1024261 the whole trigger for that 4-argument conversion? Saw
no comment from you there so far.)



I got #1024261 filed against debhelper, which made me assume this was a 
bug in debhelper.  While I had seen #1023286, I originally thought 
debhelper was not doing the job properly as well. This prompted me to do 
the 4-argument conversion to resolve it.  To be honest, it was a 
precursor for a change to `install_dir`, which I thought we would be the 
full fix - but `install_dir` had "complicated" usage outside debhelper, 
so I got rid of the easy parts first.



However, post upload, I finally understood that the real problem is not 
related to debhelper creating the directory with the wrong ownership (if 
it did, *all* directories in the dbgsym would be wrong).  Instead, it is 
most likely a "cp" or a "mv" call that copies a file into the directory 
that causes fakeroot to drop its ownership information.


I.e., the 4-argument conversion changes will not change anything as the 
bug is 100% fakeroot. At least hindsight is still 20/20.



(meaning the change to 4 parameters should probably be undone).


Ack, sounds as if this is probably the way to go once it's clear that
#1023286 was really the cause. I also wonder if some versioned Breaks
or Conflicts would be helpful, too.

Regards, Axel


I am not sure version Breaks/Conflicts is necessary to be honest.  My 
13.11 upload included a fail-safe that works around this particular bug 
in fakeroot in dbgsyms - one could argue that I "fixed" #1024261 with 
that. At the time, I felt it was a work around, so I kept it open. 
However, I think once the dusts settles, I will probably close #1024261 
as "not a bug in debhelper" and undo the 4-argument conversion.


But for now - I will just let the dust settle; after all the fakeroot 
bug is still present in mipsel due to a FTBFS (#1024544)...


Thanks,
~Niels

Bug#1022287: poldi: diff for NMU version 0.4.2+git20161115.553060d-1.1

On 2022-11-19 Adrian Bunk  wrote:
> Control: tags 1022287 + patch
> Control: tags 1022287 + pending

> Dear maintainer,

> I've prepared an NMU for poldi (versioned as 0.4.2+git20161115.553060d-1.1)
> and uploaded it to DELAYED/14. Please feel free to tell me if I should 
> cancel it.
[...]
> +poldi (0.4.2+git20161115.553060d-1.1) unstable; urgency=low
> +
> +  * Non-maintainer upload.
> +  * Delete m4/gpg-error.m4 to get the latest version from
> +libgpg-error-dev instead. (Closes: #1022287)
[...]

Please also remove the outdated ksba.m4 to prevent:

checking for ksba-config... no
checking for KSBA - version >= 1.0.2... no
[...]
configure:
***
*** libksba not found, building without X.509 authentication support.

TIA, cu Andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1024261: debhelper: dbgsym packages contain directoryr writable by build user

2022-11-21 Thread Niels Thykier


Axel Beckert:

Hi,

Helmut Grohne wrote:

 308 armel
 313 armhf
 316 i386
 613 mipsel

I think it is fairly safe to say that the problem affects 32bit
architectures.


Could this be https://bugs.debian.org/1023286 in fakeroot as well as
Niels pointed out in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024520#37 ?

Regards, Axel


It is.

Helmut and I discussed this on IRC and Helmut's findings is based on 
that IRC discussion between him and I in relation to #1023286.  (Which 
people not IRC had no chance of knowing, so putting the context here for 
good measure)


Thanks,
~Niels

Bug#1024575: node-har-validator: Unmaintained upstream and useless

2022-11-21 Thread Yadd

Package: node-har-validator
Version: 5.1.5-3
Severity: serious
Tags: security upstream
Justification: Security
X-Debbugs-Cc: Debian Security Team 

According to https://www.npmjs.com/package/har-validator this library is
no more maintained. It is used in Debian only for deprecated
node-request and was used for test in node-client-sessions,
node-configurable-http-proxy and node-fastcgi (I dropped those tests).

It is safe to remove it from Debian.

Bug#1024576: librepo: FTBFS against libgpgme-dev >= 1.18.0-2

Source: librepo
Version: 1.12.1-4
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
User: pkg-gnupg-ma...@lists.alioth.debian.org
Usertags: gpgme-config-transition^

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

Please also see #1024417 or #1024500 which also use FindGpgme.cmake.

cu Andreas

Processed: [bts-link] source package src:ogre-1.9

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

> #
> # bts-link upstream status pull for source package src:ogre-1.9
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #1024206 (http://bugs.debian.org/1024206)
> # Bug title: ogre-1.9 FTBFS on armel/armhf with glibc >= 2.32
> #  * https://github.com/OGRECave/ogre/pull/1592
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 1024206 + fixed-upstream
Bug #1024206 [src:ogre-1.9] ogre-1.9 FTBFS on armel/armhf with glibc >= 2.32
Added tag(s) fixed-upstream.
> usertags 1024206 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:bazel-bootstrap

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

> #
> # bts-link upstream status pull for source package src:bazel-bootstrap
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #1023833 (http://bugs.debian.org/1023833)
> # Bug title: FTBFS with OpenJDK 17
> #  * https://github.com/bazelbuild/bazel/issues/15831
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 1023833 + fixed-upstream
Bug #1023833 [src:bazel-bootstrap] FTBFS with OpenJDK 17
Added tag(s) fixed-upstream.
> usertags 1023833 - status-open
Usertags were: status-open.
There are now no usertags set.
> usertags 1023833 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package laminar

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

> #
> # bts-link upstream status pull for source package laminar
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #1019455 (http://bugs.debian.org/1019455)
> # Bug title: laminard: WebUI of laminar fails because newer incompatible 
> version of Chart.js is included
> #  * https://github.com/ohwgiles/laminar/issues/175
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 1019455 + fixed-upstream
Bug #1019455 [laminard] laminard: WebUI of laminar fails because newer 
incompatible version of Chart.js is included
Added tag(s) fixed-upstream.
> usertags 1019455 - status-open
Usertags were: status-open.
There are now no usertags set.
> usertags 1019455 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#1024577: libzypp: FTBFS against libgpgme-dev >= 1.18.0-2

Source: libzypp
Version: 17.25.7-2.2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
User: pkg-gnupg-ma...@lists.alioth.debian.org
Usertags: gpgme-config-transition

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

I would suggest following #1024417 where the same cmake module seems to
be used.

cu Andreas

Bug#1024578: mandos: FTBFS against libgpgme-dev >= 1.18.0-2

Source: mandos
Version: 1.8.15-1.1
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
User: pkg-gnupg-ma...@lists.alioth.debian.org
Usertags: gpgme-config-transition

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

cu Andreas
--- mandos-1.8.15.orig/Makefile
+++ mandos-1.8.15/Makefile
@@ -96,8 +96,8 @@ GNUTLS_CFLAGS:=$(shell $(PKG_CONFIG) --c
 GNUTLS_LIBS:=$(shell $(PKG_CONFIG) --libs gnutls)
 AVAHI_CFLAGS:=$(shell $(PKG_CONFIG) --cflags-only-I avahi-core)
 AVAHI_LIBS:=$(shell $(PKG_CONFIG) --libs avahi-core)
-GPGME_CFLAGS:=$(shell gpgme-config --cflags; getconf LFS_CFLAGS)
-GPGME_LIBS:=$(shell gpgme-config --libs; getconf LFS_LIBS; \
+GPGME_CFLAGS:=$(shell $(PKG_CONFIG) --cflags-only-I gpgme; getconf LFS_CFLAGS)
+GPGME_LIBS:=$(shell $(PKG_CONFIG) --libs gpgme; getconf LFS_LIBS; \
 	getconf LFS_LDFLAGS)
 LIBNL3_CFLAGS:=$(shell $(PKG_CONFIG) --cflags-only-I libnl-route-3.0)
 LIBNL3_LIBS:=$(shell $(PKG_CONFIG) --libs libnl-route-3.0)

Bug#1023678: clasp: diff for NMU version 3.3.5-4.2

2022-11-21 Thread Nilesh Patra

On Sat, 19 Nov 2022 12:14:16 +0200 Adrian Bunk  wrote:
> Control: tags 1023678 + patch
> Control: tags 1023678 + pending
> 
> Dear maintainer,
> 
> I've prepared an NMU for clasp (versioned as 3.3.5-4.2) and uploaded
> it to DELAYED/15. Please feel free to tell me if I should cancel it.

This is a science team package, and I am not quite sure if the uploader
is gonna respond. I have granted you push access to the corresponding repo
of this package.
Will you please commit your NMU (after it is accepted) to the salsa repo?

Thanks!

-- 
Best,
Nilesh

signature.asc
Description: PGP signature

Bug#1023907: marked as done (pybluez FTBFS with Python 3.11 as supported version)

Your message dated Mon, 21 Nov 2022 18:04:33 +
with message-id 
and subject line Bug#1023907: fixed in pybluez 0.23-5.1
has caused the Debian Bug report #1023907,
regarding pybluez FTBFS with Python 3.11 as supported version
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.)


-- 
1023907: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023907
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pybluez
Version: 0.23-5
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=pybluez&ver=0.23-5%2Bb2

...
bluez/btmodule.c: In function ‘PyInit__bluetooth’:
bluez/btmodule.c:2984:25: error: lvalue required as left operand of assignment
 2984 | Py_TYPE(&sock_type) = &PyType_Type;
  | ^
bluez/btmodule.c:2985:32: error: lvalue required as left operand of assignment
 2985 | Py_TYPE(&sdp_session_type) = &PyType_Type;
  |^
error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1
E: pybuild pybuild:379: build: plugin distutils failed with: exit code=1: 
/usr/bin/python3.11 setup.py build 
--- End Message ---
--- Begin Message ---
Source: pybluez
Source-Version: 0.23-5.1
Done: Stefano Rivera 

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

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

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

Debian distribution maintenance software
pp.
Stefano Rivera  (supplier of updated pybluez 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: Wed, 16 Nov 2022 19:19:13 +0200
Source: pybluez
Architecture: source
Version: 0.23-5.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Bluetooth Maintainers 
Changed-By: Stefano Rivera 
Closes: 1023907
Changes:
 pybluez (0.23-5.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Python 3.11 support. (Closes: #1023907)
Checksums-Sha1:
 1cba6023e1c467b16530359e856081198e9966cd 1492 pybluez_0.23-5.1.dsc
 6fc7b94a946e502f944358fce9275790a16f7f05 9212 pybluez_0.23-5.1.debian.tar.xz
 7c1cf2f0fde490ec267e0ae33ba50c3058fc072f 6401 pybluez_0.23-5.1_source.buildinfo
Checksums-Sha256:
 a12d68032a20ec943170f1b09ce0692695c6eb056a79e8d0d28d0878a0ac6a09 1492 
pybluez_0.23-5.1.dsc
 573a435468799e0c022e6c831fdcb74058fa42909ec7c7ce3580899e08554529 9212 
pybluez_0.23-5.1.debian.tar.xz
 0576b33549789a91a5e48796fcb71bfc61ecd9ddd7ee53849840a8dfb0e1a058 6401 
pybluez_0.23-5.1_source.buildinfo
Files:
 fa00137b8bbfa8683593d02f40a26909 1492 python optional pybluez_0.23-5.1.dsc
 06585ff57d0e11d45bff5f49cc2fa29e 9212 python optional 
pybluez_0.23-5.1.debian.tar.xz
 e7cb4096e66644015feea1b3a4f42b7b 6401 python optional 
pybluez_0.23-5.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iIoEARYKADIWIQTumtb5BSD6EfafSCRHew2wJjpU2AUCY3Ue2RQcc3RlZmFub3JA
ZGViaWFuLm9yZwAKCRBHew2wJjpU2J8UAP9nYRSwf+9sDRsTdhBUZ2ZQyaVxRKo1
EYXH+hDUOA2n/QD/ThrQIThTaxSptp812e/MoO1vEq1F9DNgJBgzUhD3KQo=
=iIx3
-END PGP SIGNATURE End Message ---

Bug#1010544: victoriametrics: FTBFS on armel

2022-11-21 Thread Antoine Beaupré

Seems to me we could just kick armel out of the supported architectures
for this package for now... I think we'd need to downgrade the severity
of this bug report, and remove the armel package from testing.

What do people think here?
-- 
Never believe that a few caring people can't change the world. For,
indeed, that's all who ever have.
- Margaret Mead

Bug#1024587: alkimia: BD-Uninstallable on s390x

2022-11-21 Thread Sebastian Ramacher

Source: alkimia
Version: 8.1.1-2
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/package.php?p=alkimia

Dependency installability problem for alkimia on s390x:

alkimia build-depends on:
- libkf5kio-dev:s390x
libkf5kio-dev depends on:
- libkf5xmlgui-dev:s390x (>= 5.98.0~)
libkf5xmlgui-dev depends on:
- libkf5xmlgui5:s390x (= 5.98.0-1+b1)
libkf5xmlgui5 depends on missing:
- libkf5xmlgui-data:s390x (= 5.98.0-1)

Cheers
-- 
Sebastian Ramacher

Bug#1024561: Unmaintained, keep out of stable

2022-11-21 Thread Sam Trenholme

Upstream here. I should probably summarize the security issues post
2.0.13; MaraDNS is the authoritative server and Deadwood is the
recursive server:

- A theoretical issue with the cryptographic code which doesn’t affect
gcc and clang compiles of Deadwood.
- An issue where a clever attacker could had kept a record in the
cache longer than desired in a fully recursive instance of Deadwood.
- An issue where a clever attack could make Deadwood perform around
500 queries to resolve a given name, if they can control the query and
responses Deadwood gets. In the fix, that number was reduced to 83.

None of these are serious security issues; I would be comfortable
using a non-Recursive instance of MaraDNS 2.0.13 on a public network,
but they are “it’s probably worth updating” security issues. I should
point out that MaraDNS 3 is fully compatible with MaraDNS 2
configuration files and the number jump was done to keep Deadwood’s
and MaraDNS’s version numbers in sync.

In terms of the upgrade, there are two branches to consider:

- The very stable 3.4 branch, where the fixes are by and large
security and other serious fixes. This branch, which was dormant for
about three years, recently had a flurry of updates for minor security
and Y2038 fixes. [1] The majority of the updates are made as patches
which can be applied to older versions, if Debian wants to take the
“patch older software” route. My plan is to keep this branch dormant
again unless another security issue comes up. In particular, this
branch is generally *not* updated to fix resolution issues with the
Deadwood recursive resolver, unless it’s something huge like
amazon.com not resolving.
- The less stable 3.5 branch. This is the continuous integration
version of MaraDNS; features are added and there’s no “frozen” branch.
Automated testing is done once a day whenever the Git tree changes and
I frequently make new releases when a given Git checkout passes
automated tests. Effort is made to keep older configuration files
compatible, so we don’t get the situation where configuration files
need to be revised to apply a security update.

[1] Other stuff was changed too. I changed a bunch Makefiles and
filenames in MaraDNS 3.4 so that it will compile with a mostly-POSIX
compliant implementation of `make`; POSIX actually didn’t mandate `-`
in make targets (it will in the next 202X POSIX release); I added
min_ttl to Deadwood so it remains semi usable as a fully recursive DNS
server on the modern Internet.

On Mon, Nov 21, 2022 at 5:03 AM Moritz Muehlenhoff  wrote:
>
> Source: maradns
> Version: 2.0.13-1.4
> Severity: serious
>
> The last maintainer upload was in 2015 and the version currently in the
> archive is way behind current upstream releases (which is at 3.4.07),
> we have plenty of maintained DNS servers, keep it out of testing (
> and if noone picks it up, remove it from the archive).
>

Bug#1024587: marked as done (alkimia: BD-Uninstallable on s390x)

Your message dated Mon, 21 Nov 2022 22:01:01 +0200
with message-id 
and subject line Re: Bug#1024587: alkimia: BD-Uninstallable on s390x
has caused the Debian Bug report #1024587,
regarding alkimia: BD-Uninstallable on s390x
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.)

-- 
1024587: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024587
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: alkimia
Version: 8.1.1-2
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/package.php?p=alkimia

Dependency installability problem for alkimia on s390x:

alkimia build-depends on:
- libkf5kio-dev:s390x
libkf5kio-dev depends on:
- libkf5xmlgui-dev:s390x (>= 5.98.0~)
libkf5xmlgui-dev depends on:
- libkf5xmlgui5:s390x (= 5.98.0-1+b1)
libkf5xmlgui5 depends on missing:
- libkf5xmlgui-data:s390x (= 5.98.0-1)

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
On Mon, Nov 21, 2022 at 08:26:10PM +0100, Sebastian Ramacher wrote:
> Source: alkimia
> Version: 8.1.1-2
> Severity: serious
> Tags: ftbfs sid bookworm
> Justification: fails to build from source (but built successfully in the past)
> X-Debbugs-Cc: sramac...@debian.org
> 
> https://buildd.debian.org/status/package.php?p=alkimia
> 
> Dependency installability problem for alkimia on s390x:
> 
> alkimia build-depends on:
> - libkf5kio-dev:s390x
> libkf5kio-dev depends on:
> - libkf5xmlgui-dev:s390x (>= 5.98.0~)
> libkf5xmlgui-dev depends on:
> - libkf5xmlgui5:s390x (= 5.98.0-1+b1)
> libkf5xmlgui5 depends on missing:
> - libkf5xmlgui-data:s390x (= 5.98.0-1)

That's just some KDE package not yet built:
https://buildd.debian.org/status/package.php?p=kxmlgui&suite=sid

> Cheers

cu
Adrian--- End Message ---

Bug#953630: [Debichem-devel] Bug#953630: openbabel autopkg tests fail on non-amd64 architectures

2022-11-21 Thread Paul Gevers


Hi,

On 21-11-2022 16:01, Andrius Merkys wrote:

On 2022-11-20 18:18, Paul Gevers wrote:
 From the BSP in Tilburg, I uploaded the attached NMU to DELAYED/5. 
Please let me know if I should delay more or cancel.


Thanks, IMO this NMU is fine. Similar logic should be applied to the 
build time tests in future, since now their failures are plainly ignored.


Rescheduled to DELAYED/0.

Thanks.

Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#953630: marked as done (openbabel autopkg tests fail on non-amd64 architectures)

Your message dated Mon, 21 Nov 2022 21:03:29 +
with message-id 
and subject line Bug#953630: fixed in openbabel 3.1.1+dfsg-7.1
has caused the Debian Bug report #953630,
regarding openbabel autopkg tests fail on non-amd64 architectures
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.)


-- 
953630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953630
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:openbabel
Version: 3.0.0+dfsg-3
Tags: patch

openbabel autopkg tests areq quiet interesting. Working around the timeout on
arm64 hides the fact that two other tests fail on every non-amd64 architecture.
Also looking at the test output, you see that one test succeeds despites the
python3 binary segfaulting.

Attached is a patch which runs all tests, skips some problematic tests, and runs
all tests before failing.

diff -Nru openbabel-3.0.0+dfsg/debian/changelog openbabel-3.0.0+dfsg/debian/changelog
--- openbabel-3.0.0+dfsg/debian/changelog	2020-01-28 13:35:16.0 +0100
+++ openbabel-3.0.0+dfsg/debian/changelog	2020-03-11 12:52:36.0 +0100
@@ -1,3 +1,13 @@
+openbabel (3.0.0+dfsg-3ubuntu3) focal; urgency=medium
+
+  * Make the autopkg tests more verbose, don't fail on the first failing test.
+  * Re-enable the tests on arm64.
+  * Skip the test/testroundtrip.py test on all architectures, times out on the
+buildds.
+  * Skip the testbindings.py and testsym.py tests on non amd64 architectures.
+
+ -- Matthias Klose   Wed, 11 Mar 2020 12:52:36 +0100
+
 openbabel (3.0.0+dfsg-3) unstable; urgency=medium
 
   [ Drew Parsons ]
diff -Nru openbabel-3.0.0+dfsg/debian/tests/python3 openbabel-3.0.0+dfsg/debian/tests/python3
--- openbabel-3.0.0+dfsg/debian/tests/python3	2020-01-28 13:35:16.0 +0100
+++ openbabel-3.0.0+dfsg/debian/tests/python3	2020-03-11 12:50:25.0 +0100
@@ -1,10 +1,33 @@
 #!/bin/bash
 
-test "$(dpkg --print-architecture)" = arm64 && exit 77
+#test "$(dpkg --print-architecture)" = arm64 && exit 77
 
 sed -i 's/"\.\."/"\/usr"/' test/testbabel.py
 
+arch=$(dpkg --print-architecture)
+fails=
 for TEST in test/test*.py
 do
-python3 ${TEST}
+case $TEST in
+  test/testroundtrip.py)
+	echo "Skipping ${TEST} ..."
+	continue;;
+  test/testbindings.py|test/testsym.py)
+	case "$arch" in arm64|armhf|ppc64el|s390x)
+	  echo "Skipping ${TEST} on $arch ..."
+	  continue;;
+	esac;;
+esac
+echo "Running ${TEST} ..."
+if python3 ${TEST}; then
+	:
+else
+	fails="$fails $TEST"
+fi
 done
+
+if [ -n "$fails" ]; then
+echo "Failing tests: $fails"
+exit 1
+fi
+exit 0
--- End Message ---
--- Begin Message ---
Source: openbabel
Source-Version: 3.1.1+dfsg-7.1
Done: Paul Gevers 

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

Debian distribution maintenance software
pp.
Paul Gevers  (supplier of updated openbabel package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 20 Nov 2022 10:24:49 +0100
Source: openbabel
Architecture: source
Version: 3.1.1+dfsg-7.1
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team 
Changed-By: Paul Gevers 
Closes: 953630
Changes:
 openbabel (3.1.1+dfsg-7.1) unstable; urgency=medium
 .
   * Non-maintainer upload
 .
   [ Matthias Klose ]
   * Make the autopkg tests more verbose, don't fail on the first failing test.
   * Re-enable the tests on arm64.
   * Skip the test/testroundtrip.py test on all architectures, times out
 (Closes: #953630)
   * Skip the testbindings.py and testsym.py tests on non amd64 architectures.
 .
   [ Paul Gevers ]
   * Run all tests that don't timeout, but ignore specific failures on
 specific architectures
Checksums-Sha1:
 5924a477f58a78d1b05a94c8ed80417d52135586 2464 openbabel_3.1.1+dfsg-7.1.dsc
 66100cc6bc6de80946913d8147853e24447e3cbc 20844 
openbabel_3.1.1+dfsg-7.1.debian.tar.xz
Checksums-Sha256:
 a797be7034fd94b95b52f771a6f554775a58bd97bcc2a9ff804bab7f760be4dc 2464 
openbabel_3.1.1+dfsg-7.1.dsc
 7648ed26a6547a32e41388f8320a5bf427cb9f632bef1f99a6ad74a878b48a9c 20844 
openbabe

Bug#1024474: marked as done (pacman-package-manager_6.0.2-2_mips64el-buildd.changes REJECTED)

Your message dated Mon, 21 Nov 2022 21:22:08 +
with message-id 
and subject line Bug#1024474: fixed in pacman-package-manager 6.0.2-3
has caused the Debian Bug report #1024474,
regarding pacman-package-manager_6.0.2-2_mips64el-buildd.changes REJECTED
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.)


-- 
1024474: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024474
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pacman-package-manager
Version: 6.0.2-2
Severity: serious

On 2022-11-20 00:06, Debian FTP Masters wrote:
> Version check failed:
> Your upload included the binary package libalpm-dev, version 13.0.2-1, for 
> mips64el,
> however testing already has version 13.0.2-1.
> Uploads to unstable must have a higher version than present in testing.
> 
> Mapping sid to unstable.
> 
> ===
> 
> Please feel free to respond to this email if you don't understand why
> your files were rejected, or if you upload new files which address our
> concerns.
> 
> 
> 
--- End Message ---
--- Begin Message ---
Source: pacman-package-manager
Source-Version: 6.0.2-3
Done: Ben Westover 

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

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

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

Debian distribution maintenance software
pp.
Ben Westover  (supplier of updated 
pacman-package-manager 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, 21 Nov 2022 15:48:16 -0400
Source: pacman-package-manager
Architecture: source
Version: 6.0.2-3
Distribution: unstable
Urgency: medium
Maintainer: Ben Westover 
Changed-By: Ben Westover 
Closes: 1024474
Changes:
 pacman-package-manager (6.0.2-3) unstable; urgency=medium
 .
   * Update Debian revision of libalpm (Closes: #1024474)
Checksums-Sha1:
 b2c8503392fbfaf85cac2b45477b8355dff35332 2681 
pacman-package-manager_6.0.2-3.dsc
 e65a2fb4b54c640d1d2dec528526a6a43f46cb65 11084 
pacman-package-manager_6.0.2-3.debian.tar.xz
 c4c8fd4bbcd985795c092337ed5d043ca150cd8d 11611 
pacman-package-manager_6.0.2-3_source.buildinfo
Checksums-Sha256:
 13d413cdcd8f4be834f9e254195dfd329a76367f369e31f298a5fd16b175c6e5 2681 
pacman-package-manager_6.0.2-3.dsc
 edf74bfe2a935eaa880032cd6e3625fa1969cde55b102421579031c05451fcb4 11084 
pacman-package-manager_6.0.2-3.debian.tar.xz
 15a2b49050520ad96a0f6296cd9b083e6b7932c727087b3aaa8273c1fbf3ea8f 11611 
pacman-package-manager_6.0.2-3_source.buildinfo
Files:
 793ac93ef37b6a7cadf831b7b99bfa64 2681 admin optional 
pacman-package-manager_6.0.2-3.dsc
 0f6521607f5aec9c10448e683bd9ee9e 11084 admin optional 
pacman-package-manager_6.0.2-3.debian.tar.xz
 3a6b540396a013004f160742ecfd6907 11611 admin optional 
pacman-package-manager_6.0.2-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEEOGnacqRhdU6eNmtFwxHF9U6JtpgFAmN75BcVHG1lQGJlbnRo
ZXRlY2hndXkubmV0AAoJEMMRxfVOibaYGygP/jEkG0Fcy5CGcF5sTQS5XAoLD2/9
oqkYrA5juzASASNz7Xf0PnMQwHvg71cpJKyKlK2GOWG2GoqYbfUMyfZBwSN9YfR5
qatE2IfaRa8wVXltCGQ6Lja1zvGAj8dmSEW/4MGGdbEzqGDsmUGwIumS9a91QuYU
9qPZOKJPcR+y0mnyNL49lRcCfZ/XqMDYIhoAws22lJYiCXEPxTxQyFWZEy7cOcSr
uD8jItp72EnVvQeUa3Wv/MAbKFmc0Bt14tkO5dYLXZ6SqgBNwphACCzYOyINpCvi
LSQpkji+LdNKD1mSulkB3pLyXLFFuNvuS8lgshTvHVsj738/PRBiYLdxuhFgTKYk
X3StCVTcGtS3Ss8d9jtHvZ0MNQKmYwRUU3Zyh5So5Ig0x0EcL2Fj/Wsn7Zg1BRGZ
SaEugyT7AxbY6Ycy9+47B5usThSuflJtnVOehFf7Kf/RG23BoGxD7IeUjCPNxgqb
TqQP0kJW0wVuYKvKpJQv9CE0aZ+GKZ79fv0FONOecgkWurrOSY8J2zrwSDn+/bvP
6iBDa6fhLhlnNK/rKDrTAyZCVAbvvMDShgfokdsWoI39WbRhaygrKQSA/cZrifte
y4h0HJr+UVQ+c76yqIr3r7uz43psF5f9cnIiqCJOZwj8WcZine3u9if0YNa0Mwl2
7ZHXEoy8a9UctuVF
=OTuW
-END PGP SIGNATURE End Message ---

Processed: block 1024575 with 956423

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

> block 1024575 with 956423
Bug #1024575 [node-har-validator] node-har-validator: Unmaintained upstream and 
useless
1024575 was not blocked by any bugs.
1024575 was not blocking any bugs.
Added blocking bug(s) of 1024575: 956423
> thanks
Stopping processing here.

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

Processed: Set pybdsf bug forwarded

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

> forwarded 1024499 https://github.com/lofar-astron/PyBDSF/issues/189
Bug #1024499 [src:pybdsf] pybdsf: FTBFS with Python 3.11 as a supported version
Set Bug forwarded-to-address to 
'https://github.com/lofar-astron/PyBDSF/issues/189'.
> thanks
Stopping processing here.

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

Bug#1024595: python3-gevent 22.10.2 must depend on python3-greenlet >= 2.0.1

Package: python3-gevent
Version: 22.10.2-1
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: Jelmer Vernooĳ 
Control: affects -1 src:derpconf
Control: block -1 by 1024433

https://buildd.debian.org/status/fetch.php?pkg=derpconf&arch=all&ver=0.8.3-3&stamp=1669044556&raw=0

...
/usr/bin/make test
make[2]: Entering directory '/<>'
:241: RuntimeWarning: greenlet.greenlet size 
changed, may indicate binary incompatibility. Expected 40 from C header, got 
160 from PyObject
:241: RuntimeWarning: greenlet.greenlet size 
changed, may indicate binary incompatibility. Expected 40 from C header, got 
160 from PyObject
:241: RuntimeWarning: greenlet.greenlet size 
changed, may indicate binary incompatibility. Expected 40 from C header, got 
160 from PyObject
:241: RuntimeWarning: greenlet.greenlet size 
changed, may indicate binary incompatibility. Expected 40 from C header, got 
160 from PyObject
:241: RuntimeWarning: greenlet.greenlet size 
changed, may indicate binary incompatibility. Expected 40 from C header, got 
160 from PyObject
:241: RuntimeWarning: greenlet.greenlet size 
changed, may indicate binary incompatibility. Expected 40 from C header, got 
160 from PyObject
:241: RuntimeWarning: greenlet.greenlet size 
changed, may indicate binary incompatibility. Expected 40 from C header, got 
160 from PyObject
:241: RuntimeWarning: greenlet.greenlet size 
changed, may indicate binary incompatibility. Expected 40 from C header, got 
160 from PyObject
Segmentation fault
make[2]: *** [Makefile:2: test] Error 139


This is due to:

https://sources.debian.org/src/python-gevent/22.10.2-1/CHANGES.rst/

...
22.10.2 (2022-10-31)



Bugfixes


- Update to greenlet 2.0. This fixes a deallocation issue that required
  a change in greenlet's ABI. The design of greenlet 2.0 is intended to
  prevent future fixes and enhancements from requiring an ABI change,
  making it easier to update gevent and greenlet independently.
...

Processed: python3-gevent 22.10.2 must depend on python3-greenlet >= 2.0.1

Processing control commands:

> affects -1 src:derpconf
Bug #1024595 [python3-gevent] python3-gevent 22.10.2 must depend on 
python3-greenlet >= 2.0.1
Added indication that 1024595 affects src:derpconf
> block -1 by 1024433
Bug #1024595 [python3-gevent] python3-gevent 22.10.2 must depend on 
python3-greenlet >= 2.0.1
1024595 was not blocked by any bugs.
1024595 was not blocking any bugs.
Added blocking bug(s) of 1024595: 1024433

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

Bug#1024206: marked as pending in ogre-1.9

2022-11-21 Thread Manuel A. Fernandez Montecelo

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/games-team/ogre-1.9/-/commit/b3a8a3297e783607ce824d2aedc23f1f8b110318


d/patches: add aa0219de16e95df61c0e81586f359d07aea35fe6.patch (Closes: #1024206)

Add aa0219de16e95df61c0e81586f359d07aea35fe6.patch to fix FTBFS on arm ports
(Closes: #1024206)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1024206

Processed: Bug#1024206 marked as pending in ogre-1.9

Processing control commands:

> tag -1 pending
Bug #1024206 [src:ogre-1.9] ogre-1.9 FTBFS on armel/armhf with glibc >= 2.32
Added tag(s) pending.

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

Bug#1024597: r-bioc-demixt FTBFS: dependency ‘DSS’ is not available for package ‘DeMixT’

Source: r-bioc-demixt
Version: 1.14.0-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=r-bioc-demixt&ver=1.14.0-1

...
I: Using built-time from d/changelog: Mon, 21 Nov 2022 13:38:58 +0100
mkdir -p /<>/debian/r-bioc-demixt/usr/lib/R/site-library
R CMD INSTALL -l 
/<>/debian/r-bioc-demixt/usr/lib/R/site-library --clean . 
"--built-timestamp='Mon, 21 Nov 2022 13:38:58 +0100'"
ERROR: dependency ‘DSS’ is not available for package ‘DeMixT’
* removing ‘/<>/debian/r-bioc-demixt/usr/lib/R/site-library/DeMixT’
dh_auto_install: error: R CMD INSTALL -l 
/<>/debian/r-bioc-demixt/usr/lib/R/site-library --clean . 
"--built-timestamp='Mon, 21 Nov 2022 13:38:58 +0100'" returned exit code 1
make: *** [debian/rules:4: binary-arch] Error 25

Bug#1024206: marked as done (ogre-1.9 FTBFS on armel/armhf with glibc >= 2.32)

Your message dated Mon, 21 Nov 2022 23:06:25 +
with message-id 
and subject line Bug#1024206: fixed in ogre-1.9 1.9.0+dfsg1-14
has caused the Debian Bug report #1024206,
regarding ogre-1.9 FTBFS on armel/armhf with glibc >= 2.32
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.)


-- 
1024206: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024206
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ogre-1.9
Version: 1.9.0+dfsg1-13
Severity: serious
Tags: ftbfs patch
Forwarded: https://github.com/OGRECave/ogre/pull/1592

https://buildd.debian.org/status/fetch.php?pkg=ogre-1.9&arch=armhf&ver=1.9.0%2Bdfsg1-13&stamp=1668553225&raw=0

...
/<>/OgreMain/src/OgrePlatformInformation.cpp:46:18: fatal error: 
sys/sysctl.h: No such file or directory
   46 | #include 
  |  ^~
compilation terminated.
make[3]: *** [OgreMain/CMakeFiles/OgreMain.dir/build.make:1563: 
OgreMain/CMakeFiles/OgreMain.dir/src/OgrePlatformInformation.cpp.o] Error 1
--- End Message ---
--- Begin Message ---
Source: ogre-1.9
Source-Version: 1.9.0+dfsg1-14
Done: Manuel A. Fernandez Montecelo 

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

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

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

Debian distribution maintenance software
pp.
Manuel A. Fernandez Montecelo  (supplier of updated ogre-1.9 
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: Tue, 15 Nov 2022 23:07:30 +0100
Source: ogre-1.9
Architecture: source
Version: 1.9.0+dfsg1-14
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Manuel A. Fernandez Montecelo 
Closes: 1024206
Changes:
 ogre-1.9 (1.9.0+dfsg1-14) unstable; urgency=medium
 .
   * Bump Standards-Version to 4.6.1 (no changes needed)
   * Set ogre-1.9-doc as "Multi-Arch: foreign"
   * d/patches:
 - add aa0219de16e95df61c0e81586f359d07aea35fe6.patch to fix FTBFS on
   arm ports (Closes: #1024206)
Checksums-Sha1:
 8e147dde0109ba4765fe73f524fb92d2172f4530 2696 ogre-1.9_1.9.0+dfsg1-14.dsc
 d95b7cdcfc4b69ac9f50eafe43f12739170a2398 25596 
ogre-1.9_1.9.0+dfsg1-14.debian.tar.xz
 b239fbab919301835baec845ae128afbcd352471 14147 
ogre-1.9_1.9.0+dfsg1-14_amd64.buildinfo
Checksums-Sha256:
 0ed373863058e7480ddcee9f3c1d653dddfb3efbf69ed06bbedc0ac95e6f6f6a 2696 
ogre-1.9_1.9.0+dfsg1-14.dsc
 931c5ca05d3e4ea3f0043e8725261745c5c09f4882151c62144bca26d3b25039 25596 
ogre-1.9_1.9.0+dfsg1-14.debian.tar.xz
 55779676805b8b4cacdd16cdc9a500b8585889c254ee042f20f4d98f8523a7fb 14147 
ogre-1.9_1.9.0+dfsg1-14_amd64.buildinfo
Files:
 0e4fcaa3cc234a251e8f36de55cae948 2696 libs optional ogre-1.9_1.9.0+dfsg1-14.dsc
 c2621718debaa92c45740b32fca4d1cf 25596 libs optional 
ogre-1.9_1.9.0+dfsg1-14.debian.tar.xz
 e7a35304b0c4ba6b23102e8f191e8e33 14147 libs optional 
ogre-1.9_1.9.0+dfsg1-14_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEEKo6AUFxIYphDDdCTf3YGpEXcqA4FAmN8AIUQHG1hZm1AZGVi
aWFuLm9yZwAKCRB/dgakRdyoDnDzD/9JtXvJotzrUSwEZPG8u299WRrHhVWUcs6N
Ebhgkuo4jH4er6JhQbR5d58wlwxkpr2vBx+a4eqWWVvHqIe1p8WXkBIFcHzkQg3m
Z2hVg/HQZXB8j99Ebf4SiupLwzsaLAQhNcoXpJFBWl7i4bDUm1NDWNCEoYrxhTNL
fBI+ZT6/KAit+Aq57UtrZOaWmlw7h/urN78YJohPYr6KWQG3NF1ztfcqztL+e0Rl
UKK/sW5MP94axGoXbXZSzn5I8AbzByKoIXWeRLBb+eOzFbYo6TLwDSQnQZtpd2mU
gC4CnvT2usfnu9LJ3L2sE/f3xHxVaFHCY1tlNqf+ThojLgRdqekokpX4S50RBftF
wuA5Pu/fiMCaiHZU7RdikoGDuTEpQuQIHwXbw0F0nnFaVQXPImHpv3hWLxG4eWnO
fMoJKngnCYVoPHEo/hcJTSME9QgOWK8znE+f/YrT+ZgLx5aSjxki5Xc+aozR3xii
tK5DUrsXMRJZ806goLVWb8oL/n2cyKf5rmTn06eoQQd5svLxfIae2GWT6zAw+iIp
wPnIWNOIA+0ikK8gzY2uZhGOHWt4er3VDSsnaRqEpH1xxLuMhHjMw5NdIiQ13p+G
Fw+6Ce+lrMlJ5ZTuLAUHfaJ9eeRKyudZIhSW+iKUhN8UxqAmSFow/z1xrjAGYhwM
B2fSKn4tyA==
=dDL0
-END PGP SIGNATURE End Message ---

Bug#1024598: bash: non-source file

2022-11-21 Thread Bastian Germann


Source: bash
Version: 5.2-2
Severity: serious

The bash source includes doc/aosa-bash-full.pdf which is a non-source file 
without corresponding source.
Please remove it additionally to doc/aosa-bash.pdf (already excluded).
You should also add a repack suffix to the upstream version.

Processed: Re: Bug#1023767: neomutt: unable to find gpgme-config

Processing control commands:

> tags 1023767 + patch
Bug #1023767 [src:neomutt] neomutt: unable to find gpgme-config
Added tag(s) patch.

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

Bug#1023767: neomutt: unable to find gpgme-config

2022-11-21 Thread Daniel Kahn Gillmor

Control: tags 1023767 + patch

On Wed 2022-11-09 22:04:00 +0100, Timo Röhling wrote:
> neomutt fails to build with the recent libgpgme-dev update that dropped
> the gpgme-config executable.
>
> https://github.com/neomutt/neomutt/pull/3555 fixes the problem, but does
> not apply cleanly to the neomutt release in Debian, unfortunately.

The attached patch appears to fix things for me so that neomutt builds
successfully against libgpgme-dev 1.18.0-3, though i don't know enough
about how to adequately test neomutt to be confident in the results (i
don't use neomutt myself).

It's also on salsa at
https://salsa.debian.org/mutt-team/neomutt/-/merge_requests/8 if that's
useful.

Please let me know if you'd like me to NMU it.

   --dkg

From a9d3c0fe8c8e678311ad7a4810df6db519abc798 Mon Sep 17 00:00:00 2001
From: Daniel Kahn Gillmor 
Date: Mon, 21 Nov 2022 19:10:20 -0500
Subject: [PATCH] find modern versions of gpgme (Closes: #1023767)

---
 debian/patches/series |   1 +
 .../upstream/Use-pkgconf-to-find-GPGMe.patch  | 121 ++
 2 files changed, 122 insertions(+)
 create mode 100644 debian/patches/upstream/Use-pkgconf-to-find-GPGMe.patch

diff --git a/debian/patches/series b/debian/patches/series
index 8c37cf1cc..b0cb4f4fc 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -6,3 +6,4 @@ upstream/964416-manpages-fixes.patch
 upstream/1020414-gsasl-support-prereq.patch
 upstream/1020414-gsasl-support.patch
 upstream/use-pkgconfig-for-libgpg-error.patch
+upstream/Use-pkgconf-to-find-GPGMe.patch
diff --git a/debian/patches/upstream/Use-pkgconf-to-find-GPGMe.patch b/debian/patches/upstream/Use-pkgconf-to-find-GPGMe.patch
new file mode 100644
index 0..f4c583cdb
--- /dev/null
+++ b/debian/patches/upstream/Use-pkgconf-to-find-GPGMe.patch
@@ -0,0 +1,121 @@
+From: Pietro Cerutti 
+Date: Mon, 7 Nov 2022 08:41:07 +
+Subject: Use pkgconf to find GPGMe
+
+(cherry-picked from upstream 516568f3f0769fad1c006a6b3a70884e97092a2a)
+---
+ Makefile.autosetup |  2 +-
+ auto.def   | 85 --
+ 2 files changed, 6 insertions(+), 81 deletions(-)
+
+diff --git a/Makefile.autosetup b/Makefile.autosetup
+index 3884704..24a2f17 100644
+--- a/Makefile.autosetup
 b/Makefile.autosetup
+@@ -572,7 +572,7 @@ $(PWD)/mutt:
+ LIBNCRYPT=	libncrypt.a
+ LIBNCRYPTOBJS=	ncrypt/config.o ncrypt/crypt.o ncrypt/cryptglue.o \
+ 		ncrypt/crypt_mod.o
+-@if HAVE_GPGME
++@if HAVE_PKG_GPGME
+ LIBNCRYPTOBJS+=	ncrypt/crypt_gpgme.o ncrypt/dlg_gpgme.o \
+ 		ncrypt/crypt_mod_pgp_gpgme.o ncrypt/crypt_mod_smime_gpgme.o
+ @endif
+diff --git a/auto.def b/auto.def
+index 12dc5d3..e0dcbb5 100644
+--- a/auto.def
 b/auto.def
+@@ -480,88 +480,13 @@ if {[get-define want-gpgme]} {
+ define-append CFLAGS -D_FILE_OFFSET_BITS=[get-define _FILE_OFFSET_BITS]
+   }
+ 
+-  msg-checking "Checking for GPGME..."
+-  if {1} {
+-# Locate gpgme-config
+-set gpgme_prefix [opt-val with-gpgme $prefix]
+-set gpgme_config_guess [file join $gpgme_prefix bin gpgme-config]
+-if {[file-isexec $gpgme_config_guess]} {
+-  define GPGME-CONFIG $gpgme_config_guess
+-} else {
+-  if {![cc-check-progs gpgme-config]} {
+-user-error "Unable to find gpgme-config"
+-  }
+-}
+-set gpgme_config [get-define GPGME-CONFIG]
+-
+-# Version
+-if {[catch {exec-with-stderr $gpgme_config --version} gpgme_version err]} {
+-  user-error "Could not derive --version from $gpgme_config"
+-}
+-if {[scan $gpgme_version "%d.%d.%d" gpgme_maj gpgme_min gpgme_patch] != 3} {
+-  user-error "Could not parse GPGME version $gpgme_version"
+-}
+-msg-result $gpgme_version
+-if {[get-define want-autocrypt]} {
+-  if {$gpgme_maj < 1 || $gpgme_min < 8} {
+-user-error "Found GPGME version $gpgme_version, need 1.8.0 for AutoCrypt"
+-  }
+-} else {
+-  if {$gpgme_maj < 1 || $gpgme_min < 4} {
+-user-error "Found GPGME version $gpgme_version, need 1.4.0"
+-  }
+-}
+-define GPGME_VERSION_NUMBER [format "0x%02x%02x%02x" $gpgme_maj $gpgme_min $gpgme_patch]
+-
+-# RHEL6 doesn't have this function yet
+-cc-check-function-in-lib gpgme_op_export_keys gpgme
+-
+-# CFLAGS
+-if {[catch {exec-with-stderr $gpgme_config --cflags} res err]} {
+-  user-error "Could not derive --cflags from $gpgme_config"
+-}
+-define-append CFLAGS $res
+-
+-# LIBS
+-if {[catch {exec-with-stderr $gpgme_config --libs} res err]} {
+-  user-error "Could not derive --libs from $gpgme_config"
+-}
+-define-append LIBS $res
+-  }
+-  define-feature gpgme
+-
+-  if {![get-define want-pkgconf] || ![pkgconf false gpg-error]} {
+-# Locate gpg-error-config
+-msg-checking "Checking for gpg-error..."
+-set gpg_error_config_guess [file join $gpgme_prefix bin gpg-error-config]
+-if {[file-isexec $gpg_error_config_guess]} {
+-  define GPG-ERROR-CONFIG $gpg_error_config_guess

Bug#1024602: bash: inaccurate copyright file

2022-11-21 Thread Bastian Germann

Source: bash
Version: 5.2-2
Severity: serious
Tags: patch

The bash package's copyright file is inaccurate.

It includes the Bash exemption that refers to GPL-2 while Bash was relicensed
to GPL-3 and lost that exemption.

bashref.texi does not have the following as part of its license (anymore?):
"Permission is granted to make and distribute verbatim copies of
this manual provided the copyright notice and this permission notice
are preserved on all copies."

The Bison exception is missing.

GPL-2+ is missing.

I have attached a machine-readable copyright file that solves these issues.

More features of the attached copyright file:
Files-Excluded for automatic repacking with #1024598 taken into account.
BSD-4-clause's advertisement clause is removed per allowance of the University
of Berkeley.
doc/FAQ's non-free license is removed.
You should also remove the file debian/FAQ because the FAQ is not maintained
anymore upstream.

The copyright and licenses of the embedded fonts of the non-source files in the
doc directory are not included.
You should instead get rid of them and build them from source if needed.Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Upstream-Contact: c...@po.cwru.edu
Comment:
This is Debian GNU/Linux's prepackaged version of the FSF's GNU Bash,
the Bourne Again SHell.
.
This package was put together by Matthias Klose .
Source:
ftp.gnu.org:/pub/gnu/bash
Files-Excluded:
doc/FAQ
doc/aosa-bash*.pdf
doc/article.*
doc/rose94.*

Files: support/checkbashisms
Copyright:
Copyright (C) 1998 Richard Braakman
Copyright (C) 2002 Josip Rodin
Copyright (C) 2003 Julian Gilbey
License: GPL-3+

Files:
tests/ifs-posix.tests
tests/posix2.tests
Copyright: (C) 2005 Glen Fowler
Copyright (c) 1995 Stephen Gildea
License: GPL-3+

License: GPL-3+
Bash is free software; you can redistribute it and/or modify it under
the terms of the GNU General Public License as published by the Free
Software Foundation; either version 3, or (at your option) any later
version.
.
Bash is distributed in the hope that it will be useful, but WITHOUT
ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License
for more details.
.
You should have received a copy of the GNU General Public License
along with Bash. If not, see .
Comment:
On Debian systems, the complete text of the GNU General Public License
version 3 can be found in `/usr/share/common-licenses/GPL-3'.

Files: y.tab.*
Copyright: (C) 1984, 1989-1990, 2000-2015, 2018-2021 Free Software Foundation,
Inc.
License: GPL-3+ with Bison exception
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
.
You should have received a copy of the GNU General Public License
along with this program. If not, see .
.
As a special exception, you may create a larger work that contains
part or all of the Bison parser skeleton and distribute that work
under terms of your choice, so long as that work isn't itself a
parser generator using the skeleton or a modified version thereof
as a parser skeleton. Alternatively, if you modify or redistribute
the parser skeleton itself, you may (at your option) remove this
special exception, which will cause the skeleton and the resulting
Bison output files to be licensed under the GNU General Public
License without this special exception.
.
This special exception was added by the Free Software Foundation in
version 2.2 of Bison.
Comment:
On Debian systems, the complete text of the GNU General Public License
version 3 can be found in `/usr/share/common-licenses/GPL-3'.

Files:
examples/functions/array-stuff
examples/functions/fstty
examples/functions/func
examples/functions/inetaddr
examples/functions/isnum2
examples/functions/ksh*
examples/functions/notify.bash
examples/functions/seq*
examples/functions/sort-pos-params
examples/functions/substr*
examples/functions/substr2
examples/functions/w*
tests/complete.tests
Copyright: 1992-2020 Chester Ramey
License: GPL-2+

Files:
debian/clear_console.c
examples/complete/bash_completion
Copyright:
Copyright (C) 2006-2019 Canonical Ltd.
Copyright (C) Ian Macdonald

Bug#1023046: zabbix: FTBFS: unsafe.Slice requires go1.17 or later (-lang was set to go1.16; check go.mod)

2022-11-21 Thread Dmitry Smirnov

On Sunday, 20 November 2022 6:22:10 PM AEDT Adrian Bunk wrote:
> > > golang.org/x/text/unicode/norm
> > > # golang.org/x/sys/unix
> > > vendor/golang.org/x/sys/unix/syscall.go:83:16: unsafe.Slice requires
> > > go1.17 or later (-lang was set to go1.16; check go.mod)
> > > vendor/golang.org/x/sys/unix/syscall_linux.go:2255:9: unsafe.Slice
> > > requires go1.17 or later (-lang was set to go1.16; check go.mod)
> > > vendor/golang.org/x/sys/unix/syscall_unix.go:118:7: unsafe.Slice
> > > requires go1.17 or later (-lang was set to go1.16; check go.mod)
> > > vendor/golang.org/x/sys/unix/sysvshm_unix.go:33:7: unsafe.Slice
> > > requires go1.17 or later (-lang was set to go1.16; check go.mod)
> > > zabbix.com/pkg/procfs
> > > # golang.org/x/sys/unix
> > > vendor/golang.org/x/sys/unix/syscall.go:83:16: unsafe.Slice requires
> > > go1.17 or later (-lang was set to go1.16; check go.mod)
> > > vendor/golang.org/x/sys/unix/syscall_linux.go:2255:9: unsafe.Slice
> > > requires go1.17 or later (-lang was set to go1.16; check go.mod)
> > > vendor/golang.org/x/sys/unix/syscall_unix.go:118:7: unsafe.Slice
> > > requires go1.17 or later (-lang was set to go1.16; check go.mod)
> > > vendor/golang.org/x/sys/unix/sysvshm_unix.go:33:7: unsafe.Slice
> > > requires go1.17 or later (-lang was set to go1.16; check go.mod)
> This comes from the new version of golang-golang-x-sys, see also [1].
> 
> [1]
> https://tracker.debian.org/news/1384566/accepted-golang-golang-x-sys-010-1
> bpo111-source-into-bullseye-backports/

Unfortunately "golang-golang-x-sys/0.1.0-1" did not fix this FTBFS.
Maybe it is because it ships "go.mod" ?

-- 
Best wishes,
 Dmitry Smirnov
 GPG key : 4096R/52B6BBD953968D1B

---

Without doubt you are not sane.
 -- Tage Danielsson

---

COVID-19: The Trouble With PCR Tests
https://swprs.org/the-trouble-with-pcr-tests/


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

Processed: Bug#1023046 marked as pending in zabbix

Processing control commands:

> tag -1 pending
Bug #1023046 [src:zabbix] zabbix: FTBFS: unsafe.Slice requires go1.17 or later 
(-lang was set to go1.16; check go.mod)
Added tag(s) pending.

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

Bug#1023046: marked as pending in zabbix

2022-11-21 Thread Dmitry Smirnov

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/debian/zabbix/-/commit/9b2165f1d76219892c6645e5d62ff3c265858374


Use bundled "golang.org/x/{sys|net}" to fix FTBFS (Closes: #1023046).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1023046

Processed: Re: Bug#1023046: zabbix: FTBFS: unsafe.Slice requires go1.17 or later (-lang was set to go1.16; check go.mod)