Bug#1013587: marked as done (slinkwatch: FTBFS: cannot find package "github.com/shirou/gopsutil/net")

2022-06-27 Thread Debian Bug Tracking System
Your message dated Tue, 28 Jun 2022 07:46:33 +0200
with message-id <7ae051bd-d2fa-5277-db65-f2ce522d2...@debian.org>
and subject line Re: Bug#1013587: slinkwatch: FTBFS: cannot find package 
"github.com/shirou/gopsutil/net"
has caused the Debian Bug report #1013587,
regarding slinkwatch: FTBFS: cannot find package 
"github.com/shirou/gopsutil/net"
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.)


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

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --buildsystem=golang --with=golang
>dh_update_autotools_config -O--buildsystem=golang
>dh_autoreconf -O--buildsystem=golang
>dh_auto_configure -O--buildsystem=golang
>debian/rules override_dh_auto_build
> make[1]: Entering directory '/<>'
> dh_auto_build
>   cd obj-x86_64-linux-gnu && go install -trimpath -v -p 8 
> github.com/DCSO/slinkwatch github.com/DCSO/slinkwatch/cmd/slinkwatch 
> github.com/DCSO/slinkwatch/cmd/slinkwatch/cmds
> src/github.com/satta/ifplugo/ifplugo.go:8:2: cannot find package 
> "github.com/shirou/gopsutil/net" in any of:
>   /usr/lib/go-1.18/src/github.com/shirou/gopsutil/net (from $GOROOT)
>   
> /<>/obj-x86_64-linux-gnu/src/github.com/shirou/gopsutil/net 
> (from $GOPATH)
> dh_auto_build: error: cd obj-x86_64-linux-gnu && go install -trimpath -v -p 8 
> github.com/DCSO/slinkwatch github.com/DCSO/slinkwatch/cmd/slinkwatch 
> github.com/DCSO/slinkwatch/cmd/slinkwatch/cmds returned exit code 1
> make[1]: *** [debian/rules:19: override_dh_auto_build] Error 25


The full build log is available from:
http://qa-logs.debian.net/2022/06/24/slinkwatch_1.1-3_unstable.log

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

reassign 1013587 golang-github-satta-ifplugo
affects 1013587 slinkwatch
fixed 1013587 0.0~git20200508.ca679be-5
thanks

Reassigning this to golang-github-satta-ifplugo. The maintainer of 
ifplugo's gopsutil dependency had changed the import path, breaking 
builds. This has now been resolved by reverting this change and its fallout.


Thanks
Sascha

On 24.06.22 13:20, Lucas Nussbaum wrote:

Source: slinkwatch
Version: 1.1-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220624 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):

  debian/rules binary
dh binary --buildsystem=golang --with=golang
dh_update_autotools_config -O--buildsystem=golang
dh_autoreconf -O--buildsystem=golang
dh_auto_configure -O--buildsystem=golang
debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build
cd obj-x86_64-linux-gnu && go install -trimpath -v -p 8 
github.com/DCSO/slinkwatch github.com/DCSO/slinkwatch/cmd/slinkwatch 
github.com/DCSO/slinkwatch/cmd/slinkwatch/cmds
src/github.com/satta/ifplugo/ifplugo.go:8:2: cannot find package 
"github.com/shirou/gopsutil/net" in any of:
/usr/lib/go-1.18/src/github.com/shirou/gopsutil/net (from $GOROOT)

/<>/obj-x86_64-linux-gnu/src/github.com/shirou/gopsutil/net (from 
$GOPATH)
dh_auto_build: error: cd obj-x86_64-linux-gnu && go install -trimpath -v -p 8 
github.com/DCSO/slinkwatch github.com/DCSO/slinkwatch/cmd/slinkwatch 
github.com/DCSO/slinkwatch/cmd/slinkwatch/cmds returned exit code 1
make[1]: *** [debian/rules:19: override_dh_auto_build] Error 25



The full build log is available from:
http://qa-logs.debian.net/2022/06

Processed: Re: Bug#1013587: slinkwatch: FTBFS: cannot find package "github.com/shirou/gopsutil/net"

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

> reassign 1013587 golang-github-satta-ifplugo
Bug #1013587 [src:slinkwatch] slinkwatch: FTBFS: cannot find package 
"github.com/shirou/gopsutil/net"
Bug reassigned from package 'src:slinkwatch' to 'golang-github-satta-ifplugo'.
No longer marked as found in versions slinkwatch/1.1-3.
Ignoring request to alter fixed versions of bug #1013587 to the same values 
previously set
> affects 1013587 slinkwatch
Bug #1013587 [golang-github-satta-ifplugo] slinkwatch: FTBFS: cannot find 
package "github.com/shirou/gopsutil/net"
Added indication that 1013587 affects slinkwatch
> fixed 1013587 0.0~git20200508.ca679be-5
Bug #1013587 [golang-github-satta-ifplugo] slinkwatch: FTBFS: cannot find 
package "github.com/shirou/gopsutil/net"
There is no source info for the package 'golang-github-satta-ifplugo' at 
version '0.0~git20200508.ca679be-5' with architecture ''
Unable to make a source version for version '0.0~git20200508.ca679be-5'
Marked as fixed in versions 0.0~git20200508.ca679be-5.
> thanks
Stopping processing here.

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



Bug#1012789: linucnc runtime prob with tiff is because of tiff

2022-06-27 Thread Petter Reinholdtsen
Upstream worked around this problem by dropping the use of libtk-img in
https://github.com/LinuxCNC/linuxcnc/commit/98a847899ee6bc59406bcee9fc79bac310e2bdd8
 >.
Thus this will be fixed in the next upload from upstream master, or
Debian can fetch the patch.

-- 
Happy hacking
Petter Reinholdtsen



Bug#1013920: Info received (Bug#1013920: rust-all: Debian violating Rust Trademark (as serious a situation as "iceweasel"))

2022-06-27 Thread lkcl
https://www.debian.org/doc/debian-policy/ch-archive.html#the-debian-free-software-guidelines

urrr 50% of the clauses of DFSG 2.1 are violated

section 2.1 3 is violated

3. Derived Works

The license must allow modifications and derived works, and must allow them
to be distributed under the same terms as the license of the
original software.

the additional conditions remove the redistribution rights normally associated
with Free Software Licenses, requiring explicit consent should "modifications
and derived works" be made.

section 2.1.5 is violated

5 No Discrimination Against Persons or Groups
The license must not discriminate against any person or group of persons.

distribibutors constitute a "group of persons" and consequently they are
discriminated against by the imposition of the restriction requiring explicit
permission to modify.

section 2.1 4 is also violated

4 Integrity of The Author’s Source Code

The license may restrict source-code from being distributed in
 modified form only if the license allows the distribution of “patch files”
 with the source code for the purpose of modifying the program at
build time.
The license must explicitly permit distribution of software built
from modified source code.

with the Trademark License creating an additional (Aggregate) License that
overrides and nullifies the "normal" expected Copyright Licenses, section 4
is violated.

section 2.1 7 is violated

7 Distribution of License

The rights attached to the program must apply to all to whom the
program is redistributed without the need for execution of an additional
license by those parties.

the imposition of the additional License Conditions from the Trademark
*are themselves* a violation of this condition

section 2.1 7 is violated as already discussed

section 2.1 9 is violated

9 License Must Not Contaminate Other Software

The license must not place restrictions on other software that is
distributed along with the licensed software.

given that the linux kernel will soon be critically dependent on having
a rust compiler...



Bug#1012246: nvidia-graphics-drivers-tesla-510: fails on ppc64el due to transitive GPL symbol usage

2022-06-27 Thread Andreas Beckmann
Control: severity -1 important
Control: tag -1 - sid bookworm

I've temporarily disabled the autopkgtest on ppc64el.


Andreas



Processed: Re: nvidia-graphics-drivers-tesla-510: fails on ppc64el due to transitive GPL symbol usage

2022-06-27 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 important
Bug #1012246 [src:nvidia-graphics-drivers-tesla-510] 
nvidia-graphics-drivers-tesla-510: fails on ppc64el due to transitive GPL 
symbol usage
Severity set to 'important' from 'serious'
> tag -1 - sid bookworm
Bug #1012246 [src:nvidia-graphics-drivers-tesla-510] 
nvidia-graphics-drivers-tesla-510: fails on ppc64el due to transitive GPL 
symbol usage
Removed tag(s) sid and bookworm.

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



Processed: closing 1013558

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

> close 1013558 4:22.04.2-2
Bug #1013558 [src:libkf5ksieve] libkf5ksieve: FTBFS: 
parsingresultdialog.h:8:10: fatal error: KSyntaxHighlighting/Repository: No 
such file or directory
Marked as fixed in versions libkf5ksieve/4:22.04.2-2.
Bug #1013558 [src:libkf5ksieve] libkf5ksieve: FTBFS: 
parsingresultdialog.h:8:10: fatal error: KSyntaxHighlighting/Repository: No 
such file or directory
Marked Bug as done
> thanks
Stopping processing here.

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



Bug#1004799: marked as done (ignition-common: FTBFS with ffmpeg 5.0)

2022-06-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Jun 2022 23:05:59 +
with message-id 
and subject line Bug#1004799: fixed in ignition-common 4.5.1+ds-1
has caused the Debian Bug report #1004799,
regarding ignition-common: FTBFS with ffmpeg 5.0
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.)


-- 
1004799: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004799
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ignition-common
Version: 4.4.0+ds-5
Severity: important
X-Debbugs-Cc: sramac...@debian.org
Tags: sid bookworm ftbfs
Usertags: ffmpeg5.0

ignition-common FTBFS with ffmpeg 5.0 in experimental:

cd /<>/obj-x86_64-linux-gnu/src && /usr/lib/ccache/c++  
-I/<>/include -I/<>/obj-x86_64-linux-gnu/include 
-I/<> -I/<>/obj-x86_64-linux-gnu 
-I/<>/test/gtest/include -I/<>/src 
-I/<>/obj-x86_64-linux-gnu/core/include -isystem /usr/include/uuid 
-isystem /usr/include/ignition/cmake2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/uuid 
-std=c++17 -MD -MT src/CMakeFiles/UNIT_Base64_TEST.dir/Base64_TEST.cc.o -MF 
CMakeFiles/UNIT_Base64_TEST.dir/Base64_TEST.cc.o.d -o 
CMakeFiles/UNIT_Base64_TEST.dir/Base64_TEST.cc.o -c 
/<>/src/Base64_TEST.cc
/<>/av/src/AudioDecoder.cc: In member function ‘bool 
ignition::common::AudioDecoder::Decode(uint8_t**, unsigned int*)’:
/<>/av/src/AudioDecoder.cc:135:24: error: ‘avcodec_decode_audio4’ 
was not declared in this scope; did you mean ‘avcodec_decode_subtitle2’?
  135 | bytesDecoded = avcodec_decode_audio4(this->data->codecCtx, 
decodedFrame,
  |^
  |avcodec_decode_subtitle2
/<>/av/src/AudioDecoder.cc: In member function ‘bool 
ignition::common::AudioDecoder::SetFile(const string&)’:
/<>/av/src/AudioDecoder.cc:227:44: error: ‘AVStream’ {aka ‘struct 
AVStream’} has no member named ‘codec’
  227 | if (this->data->formatCtx->streams[i]->codec->codec_type == // 
NOLINT(*)
  |^
/<>/av/src/AudioDecoder.cc:253:31: error: ‘AVStream’ {aka ‘struct 
AVStream’} has no member named ‘codec’
  253 | this->data->audioStream]->codec;
  |   ^
/<>/av/src/AudioDecoder.cc:259:43: error: invalid conversion from 
‘const AVCodec*’ to ‘AVCodec*’ [-fpermissive]
  259 |   this->data->codec = 
avcodec_find_decoder(this->data->codecCtx->codec_id);
  |   
^~~~
  |   |
  |   const AVCodec*
make[3]: *** [av/src/CMakeFiles/ignition-common4-av.dir/build.make:79: 
av/src/CMakeFiles/ignition-common4-av.dir/AudioDecoder.cc.o] Error 1


Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ignition-common
Source-Version: 4.5.1+ds-1
Done: Jochen Sprickerhof 

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

Debian distribution maintenance software
pp.
Jochen Sprickerhof  (supplier of updated ignition-common 
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, 28 Jun 2022 00:41:46 +0200
Source: ignition-common
Architecture: source
Version: 4.5.1+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jochen Sprickerhof 
Closes: 1004799
Changes:
 ignition-common (4.5.1+ds-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version 4.5.1+ds (Closes: #1004799)
   * Update d/copyright
   * Bump policy version (no changes)
   * Rebase patches
Checksums-Sha1:
 db74026f720612026d83ae06914aaf6ebc31ebd3 3160 ignition-common_4.5.1+ds-1.dsc
 e17ee3c3398fa7f590eafb5829268529d08f7a38 408024 
ignition-common_4.5.1+ds.orig.tar.xz
 b8b99f6bed9aa13814ca715b791e1a5c93d3fd26 14364 
ignition-common_4.5.1+ds-1.debian.tar.xz
 51fd5d267b3dec3a1c9cb529855cfbcb0560a802 10342 
ignition-common_4.5.1+ds-1_

Bug#1004800: marked as done (ignition-common3: FTBFS with ffmpeg 5.0)

2022-06-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Jun 2022 22:50:53 +
with message-id 
and subject line Bug#1004800: fixed in ignition-common3 3.14.1+dfsg-1
has caused the Debian Bug report #1004800,
regarding ignition-common3: FTBFS with ffmpeg 5.0
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.)


-- 
1004800: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004800
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ignition-common3
Version: 3.14.0+dfsg-5
Severity: important
X-Debbugs-Cc: sramac...@debian.org
Usertags: ffmpeg5.0
Tags: sid bookworm ftbfs

ignition-common3 FTBFS with ffmpeg 5.0 in experimental:

[ 27%] Building CXX object 
graphics/src/CMakeFiles/ignition-common3-graphics.dir/ColladaExporter.cc.o
cd /<>/obj-x86_64-linux-gnu/graphics/src && /usr/lib/ccache/c++ 
-DTINYXML2_MAJOR_VERSION_GE_6 -Dignition_common3_graphics_EXPORTS 
-I/<>/include -I/<>/obj-x86_64-linux-gnu/include 
-I/<>/graphics/include 
-I/<>/obj-x86_64-linux-gnu/graphics/include 
-I/<>/obj-x86_64-linux-gnu/core/include -isystem /usr/include/uuid 
-isystem /usr/include/ignition/math6 -isystem /usr/include/glib-2.0 -isystem 
/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fPIC 
-I/usr/include/uuid -pthread -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -std=c++17 -MD -MT 
graphics/src/CMakeFiles/ignition-common3-graphics.dir/ColladaExporter.cc.o -MF 
CMakeFiles/ignition-common3-graphics.dir/ColladaExporter.cc.o.d -o 
CMakeFiles/ignition-common3-graphics.dir/ColladaExporter.cc.o -c 
/<>/graphics/src/ColladaExporter.cc
/<>/av/src/AudioDecoder.cc: In member function ‘bool 
ignition::common::AudioDecoder::Decode(uint8_t**, unsigned int*)’:
/<>/av/src/AudioDecoder.cc:135:24: error: ‘avcodec_decode_audio4’ 
was not declared in this scope; did you mean ‘avcodec_decode_subtitle2’?
  135 | bytesDecoded = avcodec_decode_audio4(this->data->codecCtx, 
decodedFrame,
  |^
  |avcodec_decode_subtitle2
/<>/av/src/AudioDecoder.cc: In member function ‘bool 
ignition::common::AudioDecoder::SetFile(const string&)’:
/<>/av/src/AudioDecoder.cc:227:44: error: ‘AVStream’ {aka ‘struct 
AVStream’} has no member named ‘codec’
  227 | if (this->data->formatCtx->streams[i]->codec->codec_type == // 
NOLINT(*)
  |^
/<>/av/src/AudioDecoder.cc:253:31: error: ‘AVStream’ {aka ‘struct 
AVStream’} has no member named ‘codec’
  253 | this->data->audioStream]->codec;
  |   ^
/<>/av/src/AudioDecoder.cc:259:43: error: invalid conversion from 
‘const AVCodec*’ to ‘AVCodec*’ [-fpermissive]
  259 |   this->data->codec = 
avcodec_find_decoder(this->data->codecCtx->codec_id);
  |   
^~~~
  |   |
  |   const AVCodec*
make[3]: *** [av/src/CMakeFiles/ignition-common3-av.dir/build.make:79: 
av/src/CMakeFiles/ignition-common3-av.dir/AudioDecoder.cc.o] Error 1


Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ignition-common3
Source-Version: 3.14.1+dfsg-1
Done: Jochen Sprickerhof 

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

Debian distribution maintenance software
pp.
Jochen Sprickerhof  (supplier of updated ignition-common3 
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, 28 Jun 2022 00:24:42 +0200
Source: ignition-common3
Architecture: source
Version: 3.14.1+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jochen Sprickerhof 
Closes: 1004800
Changes:
 ignition-common3 (3.14.1+dfsg-1) unstable; urgency=medium
 .
   * Team upload.
   * Add branch to Vcs-Git:
   * New upstream 

Bug#1013162: marked as done (gifticlib: autopkgtest failure on s390x: computed checksum did NOT match)

2022-06-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Jun 2022 20:38:52 +
with message-id 
and subject line Bug#1013162: fixed in gifticlib 1.0.9-6
has caused the Debian Bug report #1013162,
regarding gifticlib: autopkgtest failure on s390x: computed checksum did NOT 
match
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.)


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

Source: gifticlib
Version: 1.0.9-5
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always

Dear maintainer(s),

You recently added an autopkgtest to your package gifticlib, great. 
However, it fails on s390x. Currently this failure is blocking the 
migration to testing [1] (but I'm going to disable s390x shortly for a 
day or so). Can you please investigate the situation and fix it? Please 
bear in mind that s390x is a big endian system so I would not be 
surprised if md5sums of files would be different there by design.


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

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

https://ci.debian.net/data/autopkgtest/testing/s390x/g/gifticlib/22340589/log.gz

Running Tests
==
FINAL IMAGE gifti_image struct
version= 1.0
numDA  = 3
gim->meta nvpairs struct, len = 3 :
nvpair: 'Caret-Version' = '5.511'
nvpair: 'date' = 'Wed Nov 21 14:53:44 2007'
nvpair: 'encoding' = 'XML'

gim->labeltable giiLabelTable struct, len = 3 :
key 17, rgba (0.620, 0.620, 0.620, 1.000), label 'PickleCenter'
key 23, rgba (0.500, 0.500, 0.500, 1.000), label 'DonutRegion'
key 29, rgba (1.000, 0.000, 0.000, 1.000), label 'MyCDATARegion'

--
gim->darray[0] giiDataArray struct
intent   1008 = NIFTI_INTENT_POINTSET
datatype   16 = NIFTI_TYPE_FLOAT32
ind_ord 1 = RowMajorOrder
num_dim   = 2
dims  = 10, 3, 0, 0, 0, 0
encoding1 = ASCII
endian  2 = LittleEndian
ext_fname = ext_offset= 0
darray->meta nvpairs struct, len = 4 :
nvpair: 'AnatomicalStructurePrimary' = 'CortexLeft'
nvpair: 'AnatomicalStructureSecondary' = 'Pial'
nvpair: 'GeometricType' = 'Anatomical'
nvpair: 'UniqueID' = '{e31cd8a6-bba6-4a1f-a26b-eb7337909a1c}'

darray->coordsys giiCoordSystem struct
dataspace  = NIFTI_XFORM_TALAIRACH
xformspace = NIFTI_XFORM_TALAIRACH
xform[0] :  1.00  0.00  0.00  0.00
xform[1] :  0.00  1.00  0.00  0.00
xform[2] :  0.00  0.00  1.00  0.00
xform[3] :  0.00  0.00  0.00  1.00
data   = 
nvals  = 30
nbyper = 4
numCS  = 1
darray->ex_atrs nvpairs struct, len = 0 :
--
--
gim->darray[1] giiDataArray struct
intent   1007 = NIFTI_INTENT_VECTOR
datatype   16 = NIFTI_TYPE_FLOAT32
ind_ord 1 = RowMajorOrder
num_dim   = 2
dims  = 10, 3, 0, 0, 0, 0
encoding1 = ASCII
endian  2 = LittleEndian
ext_fname = ext_offset= 0
darray->meta nvpairs struct, len = 1 :
nvpair: 'UniqueID' = '{ae03859c-3bd6-409e-9d95-b693380d0bdf}'

data   = 
nvals  = 30
nbyper = 4
numCS  = 0
darray->ex_atrs nvpairs struct, len = 0 :
--
--
gim->darray[2] giiDataArray struct
intent   1009 = NIFTI_INTENT_TRIANGLE
datatype8 = NIFTI_TYPE_INT32
ind_ord 1 = RowMajorOrder
num_dim   = 2
dims  = 10, 3, 0, 0, 0, 0
encoding1 = ASCII
endian  2 = LittleEndian
ext_fname = ext_offset= 0
darray->meta nvpairs struct, len = 2 :
nvpair: 'TopologicalType' = 'CLOSED'
nvpair: 'UniqueID' = '{52f9c071-75ea-4e42-bde9-3d9ba3930b94}'

data   = 
nvals  = 30
nbyper = 4
numCS  = 0
darray->ex_atrs nvpairs struct, len = 0 :
--
gifti_image struct
swapped= 0
compressed = 0
 -- darray totals: 0 MB
gim->ex_atrs nvpairs struct, len = 0 :
==
md5sum: WARNING: 1 computed checksum did NOT match
created.gii: FAILED
autopkgtest [1

Bug#1013938: balboa: regression + flaky autopkgtest: regularly times out on amd64, i386 and s390x

2022-06-27 Thread Sascha Steinbiss

Hi Paul,

thanks for letting me know!


I noticed that there were several runs that took 2:47 (our timeout
time), while successful runs more in the order of minutes. This
started to happen recently.
This is likely related to #1012629 [1] (also see #1012804 [2]), a hang 
issue that was in fact caused by rocksdb and was eventually fixed in 
rocksdb 7.2.2-5. Could the version that is tested in the autopkgtest and 
its dependencies be still affected by that?


[...]
On top of that, when a test just hangs that's not good for our 
infrastructure. I'll put balboa on our reject_list for amd64, i386, and 
s390x.


I see. I wonder what the procedure to get off that list is?
With an updated autopkgtest chroot, the latest librocksdb and a rebuilt 
version of balboa the autopkgtest consistently succeeds for me; see 
attached log.


Cheers
Sascha


[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012629
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012804Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
  apt-utils
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 446 kB of archives.
After this operation, 1,196 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian sid/main amd64 apt-utils amd64 2.5.0 [446 kB]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 446 kB in 0s (1,135 kB/s)
Selecting previously unselected package apt-utils.
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 12914 files and directories currently installed.)
Preparing to unpack .../apt-utils_2.5.0_amd64.deb ...
Unpacking apt-utils (2.5.0) ...
Setting up apt-utils (2.5.0) ...
Get:1 file:/tmp/autopkgtest-lxc.51ch70jm/downtmp/binaries  InRelease
Ign:1 file:/tmp/autopkgtest-lxc.51ch70jm/downtmp/binaries  InRelease
Get:2 file:/tmp/autopkgtest-lxc.51ch70jm/downtmp/binaries  Release [816 B]
Get:2 file:/tmp/autopkgtest-lxc.51ch70jm/downtmp/binaries  Release [816 B]
Get:3 file:/tmp/autopkgtest-lxc.51ch70jm/downtmp/binaries  Release.gpg
Ign:3 file:/tmp/autopkgtest-lxc.51ch70jm/downtmp/binaries  Release.gpg
Get:4 file:/tmp/autopkgtest-lxc.51ch70jm/downtmp/binaries  Packages [4,116 B]
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Correcting dependencies...Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
 Done
Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
The following additional packages will be installed:
  balboa balboa-backend-common balboa-backend-rocksdb curl libbrotli1 libcurl4
  libgflags2.2 libnghttp2-14 libpsl5 librocksdb7.2 librtmp1 libsnappy1v5
  libssh2-1
Recommended packages:
  ca-certificates publicsuffix
The following NEW packages will be installed:
  balboa balboa-backend-common balboa-backend-rocksdb curl libbrotli1 libcurl4
  libgflags2.2 libnghttp2-14 libpsl5 librocksdb7.2 librtmp1 libsnappy1v5
  libssh2-1
0 upgraded, 13 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 4,323 kB/7,945 kB of archives.
After this operation, 25.9 MB of additional disk space will be used.
Get:1 file:/tmp/autopkgtest-lxc.51ch70jm/downtmp/binaries  balboa 2.0.0+ds-4 [3,236 kB]
Get:2 file:/tmp/autopkgtest-lxc.51ch70jm/downtmp/binaries  balboa-backend-common 2.0.0+ds-4 [354 kB]
Get:3 file:/tmp/autopkgtest-lxc.51ch70jm/downtmp/binaries  balboa-backend-rocksdb 2.0.0+ds-4 [31.6 kB]
Get:4 http://deb.debian.org/debian sid/main amd64 libgflags2.2 amd64 2.2.2-2 [83.5 kB]
Get:5 http://deb.debian.org/debian sid/main amd64 libsnappy1v5 amd64 1.1.9-2 [27.4 kB]
Get:6 http://deb.debian.org/debian sid/main amd64 librocksdb7.2 amd64 7.2.2-5 [2,921 kB]
Get:7 http://deb.debian.org/debian sid/main amd64 libbrotli1 amd64 1.0.9-2+b3 [276 kB]
Get:8 http://deb.debian.org/debian sid/main amd64 libnghttp2-14 amd64 1.47.0-1+b1 [76.3 kB]
Get:9 http://deb.debian.org/debian sid/main amd64 libpsl5 amd64 0.21.0-1.2 [57.3 kB]
Get:10 http://deb.debian.org/debian sid/main amd64 librtmp1 amd64 2.4+20151223.gitfa8646d.1-2+b2 [60.8 kB]
Get:11 http://deb.debian.org/debian sid/main amd64 libssh2-1 amd64 1.10.0-3+b1 [179 kB]
Get:12 http://deb.debian.org/debian sid/main amd64 libcurl4 amd64 7.83.1-2 [358 kB]
Get:13 http://deb.debian.org/debian sid/main amd64 curl amd64 7.83.1-2 [285 kB]
Fetched 4,323 kB in 2s (

Processed: fails to install

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

> # package fails to install
> severity 1013295 serious
Bug #1013295 [python3-stsci.distutils] python3-stsci.distutils: 
post-installation script returned error when installing the package
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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



Bug#1013940: nfft breaks pynfft autopkgtest on i386: Segmentation fault

2022-06-27 Thread Paul Gevers

Source: nfft, pynfft
Control: found -1 nfft/3.3.2-2.1
Control: found -1 pynfft/1.3.2-5
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

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


   passfail
nfft   from testing3.3.2-2.1
pynfft from testing1.3.2-5
all others from testingfrom testing

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

Currently this regression is blocking the migration of nfft 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=nfft

https://ci.debian.net/data/autopkgtest/testing/i386/p/pynfft/23100486/log.gz

=== python3.9 ===
Segmentation fault
autopkgtest [15:22:19]: test python3



OpenPGP_signature
Description: OpenPGP digital signature


Processed: nfft breaks pynfft autopkgtest on i386: Segmentation fault

2022-06-27 Thread Debian Bug Tracking System
Processing control commands:

> found -1 nfft/3.3.2-2.1
Bug #1013940 [src:nfft, src:pynfft] nfft breaks pynfft autopkgtest on i386: 
Segmentation fault
Marked as found in versions nfft/3.3.2-2.1.
> found -1 pynfft/1.3.2-5
Bug #1013940 [src:nfft, src:pynfft] nfft breaks pynfft autopkgtest on i386: 
Segmentation fault
Marked as found in versions pynfft/1.3.2-5.

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



Bug#1013939: python-xarray: autopkgtest regression: Left and right DataArray objects are not close

2022-06-27 Thread Paul Gevers

Source: python-xarray
Version: 2022.06.0~rc1-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 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.06.0~rc1-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/amd64/p/python-xarray/23134419/log.gz

=== FAILURES 
===
___ test_weighted_operations_nonequal_coords 
___


def test_weighted_operations_nonequal_coords():
# There are no weights for a == 4, so that data point is ignored.
weights = DataArray(np.random.randn(4), dims=("a",), 
coords=dict(a=[0, 1, 2, 3]))
data = DataArray(np.random.randn(4), dims=("a",), 
coords=dict(a=[1, 2, 3, 4]))

check_weighted_operations(data, weights, dim="a", skipna=None)
q = 0.5
result = data.weighted(weights).quantile(q, dim="a")
# Expected value computed using code from 
https://aakinshin.net/posts/weighted-quantiles/ with values at a=1,2,3
expected = DataArray([0.9308707], coords={"quantile": 
[q]}).squeeze()

  assert_allclose(result, expected)

E   AssertionError: Left and right DataArray objects are not close
E   E   Differing values:
E   L
E   array(-0.289754)
E   R
E   array(0.930871)

/usr/lib/python3/dist-packages/xarray/tests/test_weighted.py:667: 
AssertionError


OpenPGP_signature
Description: OpenPGP digital signature


Bug#1013162: marked as pending in gifticlib

2022-06-27 Thread Étienne Mollier
Control: tag -1 pending

Hello,

Bug #1013162 in gifticlib 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/med-team/gifticlib/-/commit/86d250c72e83a1b96703bcaaf04022734af6e07b


d/t/run-unit-test: take endianness of the underlying system into account.

Closes: #1013162
Thanks: Paul Gevers


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1013162



Processed: Bug#1013162 marked as pending in gifticlib

2022-06-27 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #1013162 [src:gifticlib] gifticlib: autopkgtest failure on s390x: computed 
checksum did NOT match
Added tag(s) pending.

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



Bug#1013938: balboa: regression + flaky autopkgtest: regularly times out on amd64, i386 and s390x

2022-06-27 Thread Paul Gevers

Source: balboa
Version: 2.0.0+ds-4
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of you package because it was 
showing up on our "slow" page [1]. I noticed that there were several 
runs that took 2:47 (our timeout time), while successful runs more in 
the order of minutes. This started to happen recently.


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

On top of that, when a test just hangs that's not good for our 
infrastructure. I'll put balboa on our reject_list for amd64, i386, and 
s390x.


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

Paul

[1] https://ci.debian.net/status/slow/


OpenPGP_signature
Description: OpenPGP digital signature


Bug#1013889: rpmlint: autopkgtest regression: No module named 'zstandard'

2022-06-27 Thread Boyuan Yang
Hi,

在 2022-06-26星期日的 22:12 +0200,Paul Gevers写道:
> Source: rpmlint
> Version: 2.3.0+ds1-0.1
> Severity: serious
> X-Debbugs-CC: Boyuan Yang 
> User: debian...@lists.debian.org
> Usertags: regression
> 
> Dear maintainer(s), Boyuan,
> 
> With a recent upload of rpmlint the autopkgtest of rpmlint fails in 
> testing when that autopkgtest is run with the binary packages of rpmlint 
> from unstable. It passes when run with only packages from testing. In 
> tabular form:
> 
>     pass    fail
> rpmlint    from testing    2.3.0+ds1-0.1
> all others from testing    from 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=rpmlint
> 
> https://ci.debian.net/data/autopkgtest/testing/amd64/r/rpmlint/23083611/log.gz
> 
>  ERRORS 
> 
> __ ERROR collecting test/test_cli.py 
> ___
> ImportError while importing test module 
> '/tmp/autopkgtest-lxc.i2hlbh7a/downtmp/build.cyC/src/test/test_cli.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> /usr/lib/python3/dist-packages/_pytest/python.py:578: in _importtestmodule
>  mod = import_path(self.fspath, mode=importmode)
> /usr/lib/python3/dist-packages/_pytest/pathlib.py:524: in import_path
>  importlib.import_module(module_name)
> /usr/lib/python3.10/importlib/__init__.py:126: in import_module
>  return _bootstrap._gcd_import(name[level:], package, level)
> :1050: in _gcd_import
>  ???
> :1027: in _find_and_load
>  ???
> :1006: in _find_and_load_unlocked
>  ???
> :688: in _load_unlocked
>  ???
> /usr/lib/python3/dist-packages/_pytest/assertion/rewrite.py:170: in 
> exec_module
>  exec(co, module.__dict__)
> test/test_cli.py:4: in 
>  from rpmlint.cli import process_lint_args
> rpmlint/cli.py:6: in 
>  from rpmlint.lint import Lint
> rpmlint/lint.py:14: in 
>  from rpmlint.pkg import FakePkg, get_installed_pkgs, Pkg
> rpmlint/pkg.py:27: in 
>  import zstandard as zstd
> E   ModuleNotFoundError: No module named 'zstandard'

A new test dependency python-zstandard (
https://salsa.debian.org/python-team/packages/python-zstandard , not python-
zstd) is needed. This is now prepared and put into the NEW queue.

Thanks,
Boyuan Yang


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


Bug#1013935: dogtag-pki: flaky autopkgtest: regularly times out on amd64, armhf and s390x

2022-06-27 Thread Paul Gevers

Source: dogtag-pki
Version: 11.0.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of you package because it was 
showing up on our "slow" page [1]. I noticed that there were several 
runs that took 2:47 (our timeout time), while successful runs more in 
the order of minutes.


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

On top of that, when a test just hangs that's not good for our 
infrastructure. I'll put dogtag-pki on our reject_list for amd64, armhf, 
and s390x.


Don't hesitate to reach out if you need help and some more information
from our infrastructure. E.g. I note that the runs on amd64 that I 
happen to check are run on ci-worker13 that, together with our armhf 
worker is running on a host with lots of CPUs (64 and 160) and RAM 
(256GB and 511GB) and also our s390x has 10 CPUs and 32 GB.


Paul

[1] https://ci.debian.net/status/slow/


OpenPGP_signature
Description: OpenPGP digital signature


Bug#1011688: synaptic: diff for NMU version 0.90.2+nmu1

2022-06-27 Thread Boyuan Yang
Control: tags 1011688 + patch
Control: tags 1011688 + pending

Dear maintainer,

I've prepared an NMU for synaptic (versioned as 0.90.2+nmu1) and
uploaded it to DELAYED/14. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru synaptic-0.90.2/common/rconfiguration.cc synaptic-
0.90.2+nmu1/common/rconfiguration.cc
--- synaptic-0.90.2/common/rconfiguration.cc2020-11-16
03:56:34.0 -0500
+++ synaptic-0.90.2+nmu1/common/rconfiguration.cc   2022-06-27
14:01:08.0 -0400
@@ -30,6 +30,8 @@
 #include 
 #include 
 
+#include 
+
 #include 
 #include 
 #include 
diff -Nru synaptic-0.90.2/configure.ac synaptic-0.90.2+nmu1/configure.ac
--- synaptic-0.90.2/configure.ac2020-11-16 03:56:34.0 -0500
+++ synaptic-0.90.2+nmu1/configure.ac   2022-06-27 14:01:08.0 -0400
@@ -1,5 +1,5 @@
 dnl Process this file with autoconf to produce a configure script.
-AC_INIT(synaptic, 0.90.2)
+AC_INIT(synaptic, 0.90.2+nmu1)
 
 AM_INIT_AUTOMAKE([subdir-objects -Wno-portability])
 AM_CONFIG_HEADER(config.h)
diff -Nru synaptic-0.90.2/debian/changelog synaptic-
0.90.2+nmu1/debian/changelog
--- synaptic-0.90.2/debian/changelog2020-11-16 03:56:34.0 -0500
+++ synaptic-0.90.2+nmu1/debian/changelog   2022-06-27
14:01:08.0 -0400
@@ -1,3 +1,12 @@
+synaptic (0.90.2+nmu1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * common/rconfiguration.cc: Include unistd.h to prevent FTBFS
+due to undefined getuid(2). (Closes: #1011688)
+  * configure.ac: Bump version string.
+
+ -- Boyuan Yang   Mon, 27 Jun 2022 14:01:08 -0400
+
 synaptic (0.90.2) unstable; urgency=medium
 
   [ Heimen Stoffels ]


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


Processed: synaptic: diff for NMU version 0.90.2+nmu1

2022-06-27 Thread Debian Bug Tracking System
Processing control commands:

> tags 1011688 + patch
Bug #1011688 [src:synaptic] synaptic: FTBFS: rconfiguration.cc:89:8: error: 
‘getuid’ was not declared in this scope; did you mean ‘getpwuid’?
Added tag(s) patch.
> tags 1011688 + pending
Bug #1011688 [src:synaptic] synaptic: FTBFS: rconfiguration.cc:89:8: error: 
‘getuid’ was not declared in this scope; did you mean ‘getpwuid’?
Added tag(s) pending.

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



Bug#1013920: Info received (Bug#1013920: rust-all: Debian violating Rust Trademark (as serious a situation as "iceweasel"))

2022-06-27 Thread lkcl
jeremy i didn't see your reply until i checked online.  you spotted the second 
half:

We will usually allow these uses as long as the modifications
are (1) relatively small and (2) very clearly communicated to
end-users.

i did not include this because DFSG 8 is already violated by the first
half.  the *very fact* of needing to ask is an unreasonable burden
that is directly in conflict with the entire Libre/Open Concept.

imagine a Copyright License that said, "you MUST come to us to
ask permission to distribute modified versions oh but otherwise this License is 
a Free/Open One, No Really"

absolutely everyone would freak out and agree that is non-free, and the package 
either moved to nonfree or pulled entirely.

this unfortunately is exactly what the Rust Trademark has done:
added *additional* Lawfully-enforceable requirements that must
legally be complied with or suffer the consequences.

* It's Free because Copyright License BSD (whatever)
* Oh But under the Trademark We Don't Grant Distribution
   Rights for Derivative Works

and no, the existence of the Copyright License does *not* invalidate or 
override the Legal requirement to also comply with Trademark Law.  it is 
astonishing the number of FOSS developers who genuinely believe that they can 
blatantly disregard Trademark Law "Because Open Source"

> For instance, here is an excerpt without context from Debian's policy:
> "You cannot use Debian trademarks in a company or organization name or
> as the name of a product or service."

this is standard fare as part of Trademark Law.  it causes "confusion".

l.






Bug#1013933: Keep xsane out of Debian releases

2022-06-27 Thread Jörg Frings-Fürst
Package: xsane
Version: 0.999-12
Severity: serious


This is a placeholder RC bug to prevent xsane from entering testing
and making it to a Debian release. Xsane has not been maintained by
the Upstream author since 2014. Even the current fork does not show
much further development.

Because of the bugs in the GUI I don't think the current version
is suitable for a Debian release.

Should the fork develop positively, I will close this bug.


CU
Jörg


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

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

Versions of packages xsane depends on:
ii  libc62.33-7
ii  libgimp2.0   2.10.30-1+b1
ii  libglib2.0-0 2.72.2-2
ii  libgtk2.0-0  2.24.33-2
ii  libjpeg62-turbo  1:2.1.2-1
ii  liblcms2-2   2.12~rc1-2
ii  libpng16-16  1.6.37-5
ii  libsane1 1.1.1-5
ii  libtiff5 4.4.0-2
ii  sensible-utils   0.0.17
ii  xsane-common 0.999-12
ii  zlib1g   1:1.2.11.dfsg-4

Versions of packages xsane recommends:
ii  cups-client 2.4.2-1
ii  firefox [www-browser]   101.0.1-1
ii  firefox-esr [www-browser]   91.10.0esr-1
ii  google-chrome-stable [www-browser]  103.0.5060.53-1
ii  hv3 [www-browser]   3.0~fossil20110109-8
ii  lynx [www-browser]  2.9.0dev.10-1

Versions of packages xsane suggests:
ii  gimp  2.10.30-1+b1
pn  gocr | cuneiform | tesseract-ocr | ocrad  
pn  gv
pn  hylafax-client | mgetty-fax   

-- no debconf information


Bug#1013932: yade: FTBFS in unstable and testing

2022-06-27 Thread Graham Inggs
Source: yade
Version: 2022.01a-9
Severity: serious
Tags: ftbfs

Hi Maintainer

yade currently FTBFS in unstable and testing.  The  failure [1] was
picked up during the onetbb transition, but might not be related as
yade was test built before the transition was started.

I've copied what I hope is the relevant part of the log below.

Regards
Graham


[1] https://buildd.debian.org/status/package.php?p=yade


--
Ran 93 tests in 9.139s

OK
 [92m*** ALL TESTS PASSED *** [0m
[x86-csail-01:2352391] *** Process received signal ***
[x86-csail-01:2352391] Signal: Segmentation fault (11)
[x86-csail-01:2352391] Signal code: Address not mapped (1)
[x86-csail-01:2352391] Failing at address: 0x7fee112ef5e0
Segmentation fault



Bug#1013931: libtorrent-rasterbar2.0: Crash on exit

2022-06-27 Thread Hilko Bengen
Package: libtorrent-rasterbar2.0
Version: 2.0.6-3+b1
Severity: grave
X-Debbugs-Cc: none, Hilko Bengen 
Control: notfound -1 2.0.6-3

Dear Maintainer,

bug #1013470 about a nbdkit rebuild failure was reported and it turned
out that this happens because of a crash that happens even in trivial
cases:

,
| $ server/nbdkit plugins/torrent/.libs/nbdkit-torrent-plugin.so --help
| nbdkit [-4|--ipv4-only] [-6|--ipv6-only]
|[-D|--debug PLUGIN|FILTER|nbdkit.FLAG=N]
|[-e|--exportname EXPORTNAME] [--exit-with-parent]
|[--filter FILTER ...] [-f|--foreground]
|[-g|--group GROUP] [-i|--ipaddr IPADDR]
|[--log stderr|syslog|null]
|[-n|--newstyle] [--mask-handshake MASK] [--no-sr] [-o|--oldstyle]
|[-P|--pidfile PIDFILE]
|[-p|--port PORT] [-r|--readonly]
|[--run CMD] [-s|--single] [--selinux-label LABEL] [--swap]
|[-t|--threads THREADS]
|[--tls off|on|require]
|[--tls-certificates /path/to/certificates]
|[--tls-psk /path/to/pskfile] [--tls-verify-peer]
|[-U|--unix SOCKET] [-u|--user USER]
|[-v|--verbose] [-V|--version] [--vsock]
|PLUGIN [[KEY=]VALUE [KEY=VALUE [...]]]
| 
| nbdkit --dump-config
| 
| nbdkit PLUGIN --dump-plugin
| 
| nbdkit --help
| 
| Please read the nbdkit(1) manual page for full usage.
| 
| plugin: torrent (nbdkit bittorrent plugin)
| (plugins/torrent/.libs/nbdkit-torrent-plugin.so)
| torrent=   (required) Torrent or magnet link.
| file=DISK.iso  File to serve within torrent.
| cache=DIR  Set directory to store partial downloads.
| Segmentation fault
`

>From the output, it looks as if the crash occurred on a cleanup code
path.

Downgrading to 2.0.6-3 (before the OpenSSL 3 rebuild) makes the
segmentation fault go away.

The stacktrace below suggests that this is related to cleanup code
registered using atexit(3): pthread_rwlock_wrlock() is called with a
NULL pointer.

,
| $ gdb --args server/nbdkit plugins/torrent/.libs/nbdkit-torrent-plugin.so 
--help
| GNU gdb (Debian 12.1-2) 12.1
| Copyright (C) 2022 Free Software Foundation, Inc.
| [...]
| (gdb) run
| Starting program: /home/bengen/p/deb/nbdkit/server/nbdkit 
plugins/torrent/.libs/nbdkit-torrent-plugin.so --help
| [Thread debugging using libthread_db enabled]
| Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
| nbdkit [-4|--ipv4-only] [-6|--ipv6-only]
|[-D|--debug PLUGIN|FILTER|nbdkit.FLAG=N]
| [...]
| torrent=   (required) Torrent or magnet link.
| file=DISK.iso  File to serve within torrent.
| cache=DIR  Set directory to store partial downloads.
| 
| Program received signal SIGSEGV, Segmentation fault.
| __GI___pthread_rwlock_wrlock (rwlock=0x0) at pthread_rwlock_wrlock.c:27
| 27pthread_rwlock_wrlock.c: No such file or directory.
| (gdb) bt
| #0  __GI___pthread_rwlock_wrlock (rwlock=0x0) at pthread_rwlock_wrlock.c:27
| #1  0x76c8a8e9 in CRYPTO_THREAD_write_lock (lock=) at 
../crypto/threads_pthread.c:112
| #2  0x76ba7a03 in conf_modules_finish_int () at 
../crypto/conf/conf_mod.c:524
| #3  0x76ba8132 in CONF_modules_unload (all=1) at 
../crypto/conf/conf_mod.c:482
| #4  0x7726af24 in 
boost::asio::ssl::detail::openssl_init_base::do_init::~do_init 
(this=0x6157dc50, __in_chrg=)
| at /usr/include/boost/asio/ssl/detail/impl/openssl_init.ipp:90
| #5  
std::_Sp_counted_ptr::_M_dispose (
| this=) at /usr/include/c++/11/bits/shared_ptr_base.h:348
| #6  0x7726b09a in 
std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release 
(this=0x6157db90)
| at /usr/include/c++/11/bits/shared_ptr_base.h:168
| #7  std::__shared_count<(__gnu_cxx::_Lock_policy)2>::~__shared_count 
(this=, __in_chrg=)
| at /usr/include/c++/11/bits/shared_ptr_base.h:705
| #8  std::__shared_ptr::~__shared_ptr (
| this=, __in_chrg=) at 
/usr/include/c++/11/bits/shared_ptr_base.h:1154
| #9  
std::shared_ptr::~shared_ptr
 (this=, __in_chrg=)
| at /usr/include/c++/11/bits/shared_ptr.h:122
| #10 0x77bb9f77 in __run_exit_handlers (status=status@entry=0, 
listp=0x77d4d738 <__exit_funcs>, 
| run_list_atexit=run_list_atexit@entry=true, 
run_dtors=run_dtors@entry=true) at exit.c:108
| #11 0x77bba11a in __GI_exit (status=status@entry=0) at exit.c:139
| #12 0xa944 in main (argc=, argv=) 
at ./server/main.c:678
`

Cheers,
-Hilko



Processed: libtorrent-rasterbar2.0: Crash on exit

2022-06-27 Thread Debian Bug Tracking System
Processing control commands:

> notfound -1 2.0.6-3
Bug #1013931 [libtorrent-rasterbar2.0] libtorrent-rasterbar2.0: Crash on exit
No longer marked as found in versions libtorrent-rasterbar/2.0.6-3.

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



Bug#1013930: src:iperf3: fails to migrate to testing for too long: piuparts regression, changes conffile

2022-06-27 Thread Paul Gevers

Source: iperf3
Version: 3.9-1
Severity: serious
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 60 days as having a Release Critical bug in 
testing [1]. Your package src:iperf3 has been trying to migrate for 61 
days [2]. Hence, I am filing this bug. The migration is blocked because 
piuparts reports a regression. A quick glance (piuparts log and your 
changelog) suggests you are now changing a conffile (not to be confused 
with a normal configuration file), see [3].


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and bookworm, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=iperf3
[3] 
https://www.debian.org/doc/debian-policy/ch-files.html#configuration-files


OpenPGP_signature
Description: OpenPGP digital signature


Bug#1013929: src:goffice: fails to migrate to testing for too long: FTBFS on mips64el

2022-06-27 Thread Paul Gevers

Source: goffice
Version: 0.10.51-1
Severity: serious
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 60 days as having a Release Critical bug in 
testing [1]. Your package src:goffice has been trying to migrate for 61 
days [2]. Hence, I am filing this bug. Your package fails to build from 
source on mips64el where it successfully built in the past.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have tagged this bug to only affect sid and bookworm, so it doesn't 
affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=goffice



OpenPGP_signature
Description: OpenPGP digital signature


Bug#1013920: rust-all: Debian violating Rust Trademark (as serious a situation as "iceweasel")

2022-06-27 Thread lkcl
the alternative is to work with the Mozilla Foundation to rewrite their 
Trademark License.

the *intent* is clear, they do not trust Licensees (distributors) to "damage" 
the rust API, which is perfectly reasonable.

therefore, why don't they just say that?

"if a distributor performs source code modifications to a
 published revision that cause security holes, cause API or
 language incompatibilities or cause other end-user
 complaints, then this a Trademark Violation"

something along these lines is waaay more sensible than pissing about trying to 
completely unreasonably "lock down" the source code.

normally i would suggest that they convert the Trademark to a Certification 
Mark because the rust API is a Standard, and its unit tests the Compliance 
Suite, but the fact that they sell T-Shirts and merchandise prohibits that from 
being accepted (sale of products including merchandise is commercial 
competition with Licensees, and is prohibited under Certification Mark Law but 
*not* Trademark Law ).

l.




Bug#1013920: rust-all: Debian violating Rust Trademark (as serious a situation as "iceweasel")

2022-06-27 Thread Geert Stappers
On Mon, Jun 27, 2022 at 03:00:22PM +0100, lkcl wrote:
> hi Geert,

;-)


> sorry i have an odd mailer which can only toppost.

Acknowledge on "odd mailer"  and thanks for NOT
poluting the Bug Tracking System with topposts (thanks
for preventing needless scrolling)

> as in the initial post, i found a link that indicates that such explicit
> requests are in direct violation of DFSG Section 8, namely that others
> (including Derivatives) may take the source that goes through Debian
> and continue to use and distribute it without limit or restriction.

Ah, I missed that.


> the message to the Mozilla Foundation needs to be more along the lines,
> "please remove the restriction from the Trademark License so that we
> may comply with DFSG Section 8, otherwise we have to do an iceweasel".

Yeah, avoiding another iceweasel is a good thing.


Groeten
Geert Stappers
-- 
Silence is hard to parse



Bug#1009010: fix remaining bugs

2022-06-27 Thread Antoine Beaupré
On 2022-06-24 16:53:20, Georges Khaznadar wrote:
> Hello, please find as an attachment a patch to fix #1012190 and #981703
> and close them.

Hi,

thanks for the patches.

I am note sure they work though, see my comments below...

> -- 
> Georges KHAZNADAR et Jocelyne FOURNIER
> 22 rue des mouettes, 59240 Dunkerque France.
> Téléphone +33 (0)3 28 29 17 70
>
> diff --git a/debian/changelog b/debian/changelog
> index f5795bd..2c59b7e 100644
> --- a/debian/changelog
> +++ b/debian/changelog
> @@ -1,3 +1,18 @@
> +slop (7.6-2.1) unstable; urgency=medium
> +
> +  * Non-maintainer upload.
> +  * added a file d/libslop7.6.shlibs; #closes: #1012190

I don't understand why this is necessary. #1012190 should be closed
automatically when 7.6 migrates to testing, it's already marked as fixed
in unstable, deliberately.

> +  * modified d/control
> ++ now libslop7.6 conflicts with libslop7.5 and replaces it

libslop7.5 doesn't exist as far as I know, why is that necessary?

> ++ added a strict dependency libdevel =>
> +  libslopy7.6(>= ${source:Version}), libslopy7.6(<= ${source:Version}.1~)

shouldn't the shlibs:Depends do the right thing here?

i should also note that the bug to fix here is #1009010 and it's going
to be fixed once 7.6-2 passes NEW (which it entered yesterday).

> +  * applied GSR's patch; closes: #981703

i'd rather have that merged in when upstream does that release, instead
of carrying that local patch...

> +  * modified d/rules to clean out bin/slop

[...]

> diff --git a/debian/rules b/debian/rules
> index bb2a2a9..61fae45 100755
> --- a/debian/rules
> +++ b/debian/rules
> @@ -20,3 +20,8 @@ export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed
>  # main packaging script based on dh7 syntax
>  %:
>   dh $@
> +
> +override_dh_auto_clean:
> + dh_auto_clean
> + # remove a binary file not cleaned by the Makefile
> + rm -f bin/slop

could you submit this upstream?

thanks.

-- 
Nothing incites to money-crimes like great poverty or great wealth.
- Mark Twain



Bug#1013920: rust-all: Debian violating Rust Trademark (as serious a situation as "iceweasel")

2022-06-27 Thread lkcl
hi Geert,

sorry i have an odd mailer which can only toppost.

as in the initial post, i found a link that indicates that such explicit 
requests are in direct violation of DFSG Section 8, namely that others 
(including Derivatives) may take the source that goes through Debian and 
continue to use and distribute it without limit or restriction.

the message to the Mozilla Foundation needs to be more along the lines, "please 
remove the restriction from the Trademark License so that we may comply with 
DFSG Section 8, otherwise we have to do an iceweasel".

l.


Bug#1013920: rust-all: Debian violating Rust Trademark (as serious a situation as "iceweasel")

2022-06-27 Thread Geert Stappers
On Mon, Jun 27, 2022 at 01:58:41PM +0100, lkcl wrote:
> everything is "fine" as long as:
>
> 1) the Mozilla Foundation acts reasonably and non-discriminatorily
> (FRAND applies to Trademarks just as it applies to patent Licensing)
> 2) the Mozilla Foundation does not appreciate quite how much power it
> actually has under Trademark Law.
>
> given that this is between Free Software Groups i would expect the
> discussion to remain civil and reasonable, and for them to drop or
> modify the unachievable nonfree constraint, but please for goodness
> sake do not let the civility of the interaction lull you into a sense
> of false safety.
>
> under the Trademark as they have defined it, the Mozilla Foundation
> is perfectly permitted to issue Debian a Legal Notice to Cease and
> Desist distribution of the Unlawfully patched rustc binaries.
>
> l.


Hi Luke,
Hi all others,


Let's continue thinking several steps ahead.

* Allow all room to move forward
* Accept there is NO  "request pending" documentation,
  trust https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013920#10
  that it is "work in progress"
* Ask over six weeks how much you should worry about this
* Meanwhile team-up with other Linux distributions
* Meanwhile create a concept letter you want to have, like
We, Mozilla Foundation grant these Linux distributions
* foo
* bar
* debian
* baz
to distribute our Rust and our Cargo that we still
can recognice as our Rust and as our Cargo.
* Continue enjoying Rust and Cargo



Regards
Geert Stappers


P.S.

a Trade Mark is a request for respect, not a demand for respect.
And yes, respect is something like trust, it has to be earnt.
-- 
Silence is hard to parse



Bug#1013475: marked as done (python-django-pyscss: FTBFS: ImportError: cannot import name 'url' from 'django.conf.urls' (/usr/lib/python3/dist-packages/django/conf/urls/__init__.py))

2022-06-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Jun 2022 13:19:06 +
with message-id 
and subject line Bug#1013475: fixed in python-django-pyscss 2.0.2-11
has caused the Debian Bug report #1013475,
regarding python-django-pyscss: FTBFS: ImportError: cannot import name 'url' 
from 'django.conf.urls' 
(/usr/lib/python3/dist-packages/django/conf/urls/__init__.py)
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.)


-- 
1013475: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013475
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-django-pyscss
Version: 2.0.2-10
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220624 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> pkgos-dh_auto_install --no-py2
> + PKGOS_USE_PY2=yes
> + PKGOS_USE_PY3=yes
> + PKGOS_IN_TMP=no
> + PKGOS_USE_PY2=no
> + shift
> + dpkg-parsechangelog -SSource
> + SRC_PKG_NAME=python-django-pyscss
> + echo python-django-pyscss
> + sed s/python-//
> + PY_MODULE_NAME=django-pyscss
> + [ no = yes ]
> + [ yes = yes ]
> + py3versions -vr
> + PYTHON3S=3.9 3.10
> + [ no = yes ]
> + [ yes = yes ]
> + [ no = yes ]
> + TARGET_DIR=python3-django-pyscss
> + pwd
> + python3.9 setup.py install --install-layout=deb --root 
> /<>/debian/python3-django-pyscss
> running install
> /usr/lib/python3/dist-packages/setuptools/command/install.py:34: 
> SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and 
> pip and other standards-based tools.
>   warnings.warn(
> running build
> running build_py
> creating build
> creating build/lib
> creating build/lib/django_pyscss
> copying django_pyscss/__init__.py -> build/lib/django_pyscss
> copying django_pyscss/compressor.py -> build/lib/django_pyscss
> copying django_pyscss/compiler.py -> build/lib/django_pyscss
> copying django_pyscss/utils.py -> build/lib/django_pyscss
> creating build/lib/django_pyscss/extension
> copying django_pyscss/extension/__init__.py -> 
> build/lib/django_pyscss/extension
> copying django_pyscss/extension/django.py -> build/lib/django_pyscss/extension
> running egg_info
> creating django_pyscss.egg-info
> writing django_pyscss.egg-info/PKG-INFO
> writing dependency_links to django_pyscss.egg-info/dependency_links.txt
> writing requirements to django_pyscss.egg-info/requires.txt
> writing top-level names to django_pyscss.egg-info/top_level.txt
> /usr/lib/python3/dist-packages/calmjs/cli.py:234: RuntimeWarning: Unable to 
> locate the 'npm' binary or runtime; default module level functions will not 
> work. Please either provide PATH and/or update PATH environment variable with 
> one that provides 'npm'; or specify a working NODE_PATH environment variable 
> with npm installed; or have install 'npm' into the current working directory 
> (/<>) either through npm or calmjs framework for this package. 
> Restart or reload this module once that is done. Alternatively, create a 
> manual Driver instance for 'npm' with explicitly defined arguments.
>   warnings.warn(msg, RuntimeWarning)
> writing manifest file 'django_pyscss.egg-info/SOURCES.txt'
> reading manifest file 'django_pyscss.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no previously-included files matching '*.pyc' found under directory 
> 'tests'
> warning: no previously-included files matching '*.pyc' found under directory 
> 'testproject'
> adding license file 'LICENSE'
> writing manifest file 'django_pyscss.egg-info/SOURCES.txt'
> running install_lib
> creating /<>/debian/python3-django-pyscss
> creating /<>/debian/python3-django-pyscss/usr
> creating /<>/debian/python3-django-pyscss/usr/lib
> creating /<>/debian/python3-django-pyscss/usr/lib/python3
> creating 
> /<>/debian/python3-django-pyscss/usr/lib/python3/dist-packages
> creating 
> /<>/debian/python3-django-pyscss/usr/lib/python3/dist-packages/django_pyscss
> copying build/lib/django_pyscss/__init__.py -> 
> /<>/debian/python3-django-pyscss/usr/lib/python3/dist-packages/django_pyscss
> copying build/lib/django_pyscss/compressor.py -> 
> /<>/debian/python3-django-pyscss/usr/lib/python3/dist-packages/django_pyscss
> copying build/lib/django_pyscss/compiler.py -> 
> /<>/debian/python3-django-pyscss/usr/lib/python3/dist-packages/django_pyscss
> creating 
> /<>/debian/python3-django-pyscss/usr/lib/python3/dist-packages/django_pyscss/e

Bug#928224: Valgrind is broken on armhf

2022-06-27 Thread Mathieu Malaterre
% gdb "/usr/libexec/valgrind/memcheck-arm-linux"
GNU gdb (Debian 12.1-2) 12.1
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "arm-linux-gnueabihf".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/libexec/valgrind/memcheck-arm-linux...
Reading symbols from
/usr/lib/debug/.build-id/c8/4acaae37749c83c7183bc7a37bbde299e52e82.debug...
(gdb) r
Starting program: /usr/libexec/valgrind/memcheck-arm-linux

Program received signal SIGILL, Illegal instruction.
vgPlain_am_startup (sp_at_startup=3204445888) at
m_aspacemgr/aspacemgr-linux.c:1626
1626   init_nsegment(&seg);
(gdb) bt full
#0  vgPlain_am_startup (sp_at_startup=3204445888) at
m_aspacemgr/aspacemgr-linux.c:1626
seg = {kind = 0, start = 0, end = 0, smode = SmLower, dev = 0,
ino = 0, offset = 5376491600740352, mode = 3204445892, fnIdx =
-1090521408, hasR = 0 '\000', hasW = 160 '\240', hasX = 37 '%',
  hasT = 88 'X', isCH = 248 '\370'}
suggested_clstack_end = 
__PRETTY_FUNCTION__ = "vgPlain_am_startup"
#1  0x580cc5e4 in valgrind_main (envp=0xbefff6cc, argv=0xbefff6c4,
argc=1) at m_main.c:1387
loglevel = 
i = 
vex_archinfo = {hwcaps = 0, endness = 0, hwcache_info =
{num_levels = 0, num_caches = 0, caches = 0x0,
icaches_maintain_coherence = 0 '\000'}, ppc_icache_line_szB = 0,
ppc_dcbz_szB = 0,
  ppc_dcbzl_szB = 0, arm64_dMinLine_lg2_szB = 0,
arm64_iMinLine_lg2_szB = 0, arm64_requires_fallback_LLSC = 0 '\000'}
need_help = 
tid_main = 0
addr2dihandle = 0x0
wd = 
need_help = 
tid_main = 
loglevel = 
i = 
addr2dihandle = 
__PRETTY_FUNCTION__ = "valgrind_main"
vex_archinfo = 
wd = 
tmp_str = 
res = 
val = 
res = 
val = 
s = 
n = 
res = 
val = 
s = 
n = 
val = 
ok = 
errmsg = 
limLo = 
limHi = 
aLocal = 
p = 
cp = 
vex_arch = 
ok = 
buf = 
buf2 = 
fd = 
r = 
nul = 
exename = 
client_auxv = 
client_auxv_len = 
--Type  for more, q to quit, c to continue without paging--
arg = 
s = 
ok = 
seg_starts = 
n_seg_starts = 
anu = 
change_ownership_v_c_OK = 
co_start = 
co_endPlus = 
buf = 
seg_starts = 
n_seg_starts = 
j = 
n = 
seg = 
anl = 
inaccessible_len = 
seg = 
seg = 
#2  _start_in_C_linux (pArgc=0xbefff6c0) at m_main.c:3081
r = 
argc = 1
argv = 0xbefff6c4
envp = 0xbefff6cc
#3  0x in ?? ()
No symbol table info available.
Backtrace stopped: previous frame identical to this frame (corrupt stack?)



Processed: Bug#1013475 marked as pending in python-django-pyscss

2022-06-27 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #1013475 [src:python-django-pyscss] python-django-pyscss: FTBFS: 
ImportError: cannot import name 'url' from 'django.conf.urls' 
(/usr/lib/python3/dist-packages/django/conf/urls/__init__.py)
Added tag(s) pending.

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



Bug#1013475: marked as pending in python-django-pyscss

2022-06-27 Thread Thomas Goirand
Control: tag -1 pending

Hello,

Bug #1013475 in python-django-pyscss 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/openstack-team/python/python-django-pyscss/-/commit/a0e28f037c525c4d48eb13c67e9778b4c65d7fa7


Add django-4-compat.patch (Closes: #1013475).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1013475



Bug#1013920: [Pkg-rust-maintainers] Bug#1013920: rust-all: Debian violating Rust Trademark (as serious a situation as "iceweasel")

2022-06-27 Thread lkcl
everything is "fine" as long as:

1) the Mozilla Foundation acts reasonably and non-discriminatorily (FRAND 
applies to Trademarks just as it applies to patent Licensing)
2) the Mozilla Foundation does not appreciate quite how much power it actually 
has under Trademark Law.

given that this is between Free Software Groups i would expect the discussion 
to remain civil and reasonable, and for them to drop or modify the unachievable 
nonfree constraint, but please for goodness sake do not let the civility of the 
interaction lull you into a sense of false safety.

under the Trademark as they have defined it, the Mozilla Foundation is 
perfectly permitted to issue Debian a Legal Notice to Cease and Desist 
distribution of the Unlawfully patched rustc binaries.

l.




On June 27, 2022 1:07:14 PM GMT+01:00, Sylvestre Ledru  
wrote:
>Hello
>
>I don't think it is a big deal but I will chat with some people on the
>Rust side about this.
>
>Cheers,
>Sylvestre (who managed the iceweasel/firefox thing)
>
>
>Le 27/06/2022 à 13:52, lkcl a écrit :
>> Package: rust-all
>> Severity: serious
>> Tags: upstream
>> Justification: Policy 2.1
>> 
>> https://internals.rust-lang.org/t/rust-s-freedom-flaws/11533
>> https://lists.debian.org/debian-legal/2021/05/msg6.html
>>
>https://foundation.rust-lang.org/policies/logo-policy-and-media-guide/
>> 
>> this is an extremely serious situation that exposes debian to a
>greater
>> level of risk that was undergone for the last Mozilla-Foundation
>> Trademark fiasco, iceweasel
>> 
>> Rust's Trademark requirements are that "you must seek our explicit
>> permission before distributing patches".
>> 
>>  Uses that require explicit approval
>> 
>>  Distributing a **MODIFIED VERSION** of the Rust programming
>language
>>  or the Cargo package manager and calling it Rust or Cargo
>requires
>>  explicit, written permission from the Rust core team.
>> 
>> there are dozens of such patches and every single one of them, unless
>> explicit permission has been sought, is a DIRECT Trademark violation
>> 
>>  https://sources.debian.org/patches/rustc/1.36.0+dfsg1-2/
>> 
>> the over-ride of the Trademark on "Free" software is Lawful and
>> in this case makes rust (and cargo) non-free software.
>> 
>> unlike the Iceweasel debacle, the linux kernel is upstream merging
>> rust, potentially making the entire linux kernel critically dependent
>> on a non-free compiler.
>> 
>> there is the additional issue that although Debian might seek and
>> be granted explicit permission for a Trademark License Grant to
>> Distribute, that does not cover Derivatives, which would also
>> need to explicitly seek their own permission
>> 
>>  https://www.debian.org/derivatives/
>>  https://devuan.org
>> 
>> this has been discussed that DFSG Guideline 8 is violated by even
>> attempting to seek a License specific to Debian
>> 
>> 
>https://www.mail-archive.com/debian-legal@lists.debian.org/msg45464.html
>> 
>> this is an extremely serious situation that either requires pulling
>> rust and cargo from debian or a rename of both rust and cargo exactly
>> as was done with iceweasel.
>> 
>> failure to do so is also extremely serious because Unlawful
>Distribution
>> may still be considered grounds for financial compensation as well as
>> a Legal Notice to Cease and Desist, and also to remove all public and
>private
>> use of the Trademark from all Records.  mailing lists, bugtracker,
>> debian archives - everything.
>> 
>> this one cannot be ignored.
>> 
>> 
>> -- System Information:
>> 
>> ___
>> Pkg-rust-maintainers mailing list
>> pkg-rust-maintain...@alioth-lists.debian.net
>>
>https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-rust-maintainers


Processed: your mail

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

> severity 928224 grave
Bug #928224 [valgrind] Valgrind is broken on armhf
Severity set to 'grave' from 'important'
>
End of message, stopping processing here.

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



Bug#1013910: src:mlucas: invalid maintainer address

2022-06-27 Thread Adam Borowski
On Mon, Jun 27, 2022 at 10:41:58AM +0200, Ansgar wrote:
> Source: mlucas
> Version: 20.1.1-1
> Severity: serious

> The maintainer address for src:mlucas is obviously invalid:
> 
> Maintainer: Alex Vong 

Well, besides the doofus sponsor who *somehow* managed to not notice this
change, let's CC the _previous_ maintainer.

Alex: the new address' "alexvong1995-AT-protonmail-DOT-com" server can't be
contacted -- it fails with:

drill -t mx nospam.invalid
;; ->>HEADER<<- opcode: QUERY, rcode: NXDOMAIN
drill -t  nospam.invalid
;; ->>HEADER<<- opcode: QUERY, rcode: NXDOMAIN
drill -t a nospam.invalid
;; ->>HEADER<<- opcode: QUERY, rcode: NXDOMAIN

Could you perhaps take the package back, and fix build failures on most
archs?


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ What kind of a drug are "base" and "red pill"?  I think acid is
⢿⡄⠘⠷⠚⠋⠀ LSD, which would make base... ?  Judging from the behaviour of
⠈⠳⣄ those "based and redpilled", something nasty.



Bug#1013920: rust-all: Debian violating Rust Trademark (as serious a situation as "iceweasel")

2022-06-27 Thread Jeremy Bicha
The full paragraph [1] is
"Distributing a modified version of the Rust programming language or
the Cargo package manager and calling it Rust or Cargo requires
explicit, written permission from the Rust core team. We will usually
allow these uses as long as the modifications are (1) relatively small
and (2) very clearly communicated to end-users."

By only providing half of that quote in your bug report, I think
you're missing important context.

I think that would probably be easy enough to comply with. I also
think that is fairly in line with trademark policies in general. If
someone significantly modifies Debian, I believe the Debian Project
would insist that they use a different name for their product despite
the DFSG and despite that Debian is free and open source.

For instance, here is an excerpt without context from Debian's policy:
"You cannot use Debian trademarks in a company or organization name or
as the name of a product or service."

[1] https://foundation.rust-lang.org/policies/logo-policy-and-media-guide/
[2] https://www.debian.org/trademark

Thank you,
Jeremy Bicha



Processed: 1013714 is forwarded

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

> forwarded 1013714 https://gitlab.com/ase/ase/-/issues/1117
Bug #1013714 [src:python-ase] python-ase: FTBFS: pytest7 regression, deprecated 
pytest feature: pytest.warnsNone
Set Bug forwarded-to-address to 'https://gitlab.com/ase/ase/-/issues/1117'.
> thanks
Stopping processing here.

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



Bug#1013920: [Pkg-rust-maintainers] Bug#1013920: rust-all: Debian violating Rust Trademark (as serious a situation as "iceweasel")

2022-06-27 Thread Sylvestre Ledru

Hello

I don't think it is a big deal but I will chat with some people on the Rust 
side about this.

Cheers,
Sylvestre (who managed the iceweasel/firefox thing)


Le 27/06/2022 à 13:52, lkcl a écrit :

Package: rust-all
Severity: serious
Tags: upstream
Justification: Policy 2.1

https://internals.rust-lang.org/t/rust-s-freedom-flaws/11533
https://lists.debian.org/debian-legal/2021/05/msg6.html
https://foundation.rust-lang.org/policies/logo-policy-and-media-guide/

this is an extremely serious situation that exposes debian to a greater
level of risk that was undergone for the last Mozilla-Foundation
Trademark fiasco, iceweasel

Rust's Trademark requirements are that "you must seek our explicit
permission before distributing patches".

 Uses that require explicit approval

 Distributing a **MODIFIED VERSION** of the Rust programming language
 or the Cargo package manager and calling it Rust or Cargo requires
 explicit, written permission from the Rust core team.

there are dozens of such patches and every single one of them, unless
explicit permission has been sought, is a DIRECT Trademark violation

 https://sources.debian.org/patches/rustc/1.36.0+dfsg1-2/

the over-ride of the Trademark on "Free" software is Lawful and
in this case makes rust (and cargo) non-free software.

unlike the Iceweasel debacle, the linux kernel is upstream merging
rust, potentially making the entire linux kernel critically dependent
on a non-free compiler.

there is the additional issue that although Debian might seek and
be granted explicit permission for a Trademark License Grant to
Distribute, that does not cover Derivatives, which would also
need to explicitly seek their own permission

 https://www.debian.org/derivatives/
 https://devuan.org

this has been discussed that DFSG Guideline 8 is violated by even
attempting to seek a License specific to Debian

 https://www.mail-archive.com/debian-legal@lists.debian.org/msg45464.html

this is an extremely serious situation that either requires pulling
rust and cargo from debian or a rename of both rust and cargo exactly
as was done with iceweasel.

failure to do so is also extremely serious because Unlawful Distribution
may still be considered grounds for financial compensation as well as
a Legal Notice to Cease and Desist, and also to remove all public and private
use of the Trademark from all Records.  mailing lists, bugtracker,
debian archives - everything.

this one cannot be ignored.


-- System Information:

___
Pkg-rust-maintainers mailing list
pkg-rust-maintain...@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-rust-maintainers




Bug#1013618: marked as done (suitesparse: FTBFS: ! Undefined control sequence. l.96 \htmladdnormallink)

2022-06-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Jun 2022 12:03:54 +
with message-id 
and subject line Bug#1013618: fixed in suitesparse 1:5.12.0+dfsg-2
has caused the Debian Bug report #1013618,
regarding suitesparse: FTBFS: ! Undefined control sequence.  l.96 
\htmladdnormallink
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.)


-- 
1013618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013618
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: suitesparse
Version: 1:5.12.0+dfsg-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220624 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[4]: Entering directory '/<>/SPQR/Doc'
> pdflatex spqr_user_guide.tex
> This is pdfTeX, Version 3.141592653-2.6-1.40.24 (TeX Live 2022/Debian) 
> (preloaded format=pdflatex)
>  restricted \write18 enabled.
> entering extended mode
> (./spqr_user_guide.tex
> LaTeX2e <2021-11-15> patch level 1
> L3 programming layer <2022-02-24>
> (/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
> Document Class: article 2021/10/04 v1.4n Standard LaTeX document class
> (/usr/share/texlive/texmf-dist/tex/latex/base/size12.clo))
> (/usr/share/texlive/texmf-dist/tex/latex/hyperref/hyperref.sty
> (/usr/share/texlive/texmf-dist/tex/generic/ltxcmds/ltxcmds.sty)
> (/usr/share/texlive/texmf-dist/tex/generic/iftex/iftex.sty)
> (/usr/share/texlive/texmf-dist/tex/generic/pdftexcmds/pdftexcmds.sty
> (/usr/share/texlive/texmf-dist/tex/generic/infwarerr/infwarerr.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty)
> (/usr/share/texlive/texmf-dist/tex/generic/kvsetkeys/kvsetkeys.sty)
> (/usr/share/texlive/texmf-dist/tex/generic/kvdefinekeys/kvdefinekeys.sty)
> (/usr/share/texlive/texmf-dist/tex/generic/pdfescape/pdfescape.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/hycolor/hycolor.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/letltxmacro/letltxmacro.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/auxhook/auxhook.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/kvoptions/kvoptions.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/hyperref/pd1enc.def)
> (/usr/share/texlive/texmf-dist/tex/generic/intcalc/intcalc.sty)
> (/usr/share/texlive/texmf-dist/tex/generic/etexcmds/etexcmds.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/hyperref/puenc.def)
> (/usr/share/texlive/texmf-dist/tex/latex/url/url.sty)
> (/usr/share/texlive/texmf-dist/tex/generic/bitset/bitset.sty
> (/usr/share/texlive/texmf-dist/tex/generic/bigintcalc/bigintcalc.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/base/atbegshi-ltx.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/hyperref/hpdftex.def
> (/usr/share/texlive/texmf-dist/tex/latex/base/atveryend-ltx.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/rerunfilecheck/rerunfilecheck.sty
> (/usr/share/texlive/texmf-dist/tex/generic/uniquecounter/uniquecounter.sty)))
> (/usr/share/texlive/texmf-dist/tex/generic/epsf/epsf.tex
> This is `epsf.tex' v2.7.4 <14 February 2011>
> ) (/usr/share/texlive/texmf-dist/tex/latex/l3backend/l3backend-pdftex.def)
> No file spqr_user_guide.aux.
> (/usr/share/texlive/texmf-dist/tex/latex/hyperref/nameref.sty
> (/usr/share/texlive/texmf-dist/tex/latex/refcount/refcount.sty)
> (/usr/share/texlive/texmf-dist/tex/generic/gettitlestring/gettitlestring.sty))
> Overfull \hbox (17.34248pt too wide) in paragraph at lines 38--38
>  [][] 
> 
> LaTeX Warning: Citation `Davis08a' on page 1 undefined on input line 59.
> 
> 
> LaTeX Warning: Citation `Davis08b' on page 1 undefined on input line 60.
> 
> 
> LaTeX Warning: Citation `GilbertMolerSchreiber' on page 1 undefined on input 
> li
> ne 69.
> 
> [1{/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map}]
> ! Undefined control sequence.
> l.96 \htmladdnormallink
>
> {http://www.microsoft.com/express/vc/}{http://www.mic...
> 
> ? 
> ! Emergency stop.
> l.96 
>  
> !  ==> Fatal error occurred, no output PDF file produced!
> Transcript written on spqr_user_guide.log.
> make[4]: *** [Makefile:7: spqr_user_guide.pdf] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/06/24/suitesparse_5.12.0+dfsg-1_unstable.log

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


Bug#1013920: rust-all: Debian violating Rust Trademark (as serious a situation as "iceweasel")

2022-06-27 Thread lkcl
Package: rust-all
Severity: serious
Tags: upstream
Justification: Policy 2.1

https://internals.rust-lang.org/t/rust-s-freedom-flaws/11533
https://lists.debian.org/debian-legal/2021/05/msg6.html
https://foundation.rust-lang.org/policies/logo-policy-and-media-guide/

this is an extremely serious situation that exposes debian to a greater
level of risk that was undergone for the last Mozilla-Foundation
Trademark fiasco, iceweasel

Rust's Trademark requirements are that "you must seek our explicit
permission before distributing patches".

Uses that require explicit approval

Distributing a **MODIFIED VERSION** of the Rust programming language
or the Cargo package manager and calling it Rust or Cargo requires
explicit, written permission from the Rust core team. 

there are dozens of such patches and every single one of them, unless
explicit permission has been sought, is a DIRECT Trademark violation

https://sources.debian.org/patches/rustc/1.36.0+dfsg1-2/

the over-ride of the Trademark on "Free" software is Lawful and
in this case makes rust (and cargo) non-free software.

unlike the Iceweasel debacle, the linux kernel is upstream merging
rust, potentially making the entire linux kernel critically dependent
on a non-free compiler.

there is the additional issue that although Debian might seek and
be granted explicit permission for a Trademark License Grant to
Distribute, that does not cover Derivatives, which would also
need to explicitly seek their own permission

https://www.debian.org/derivatives/
https://devuan.org

this has been discussed that DFSG Guideline 8 is violated by even
attempting to seek a License specific to Debian

https://www.mail-archive.com/debian-legal@lists.debian.org/msg45464.html

this is an extremely serious situation that either requires pulling
rust and cargo from debian or a rename of both rust and cargo exactly
as was done with iceweasel.

failure to do so is also extremely serious because Unlawful Distribution
may still be considered grounds for financial compensation as well as
a Legal Notice to Cease and Desist, and also to remove all public and private
use of the Trademark from all Records.  mailing lists, bugtracker,
debian archives - everything.

this one cannot be ignored.


-- System Information:



Bug#1013615: marked as done (hiredis: FTBFS: 2 TESTS FAILED ***)

2022-06-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Jun 2022 11:04:37 +
with message-id 
and subject line Bug#1013615: fixed in hiredis 0.14.1-3
has caused the Debian Bug report #1013615,
regarding hiredis: FTBFS: 2 TESTS FAILED ***
to be marked as done.

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

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


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

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> 347517:C 24 Jun 2022 06:06:43.771 # Reading config from stdin
> for i in 1 2 3 4 5; do \
>   if [ -r /tmp/hiredis-test-redis.sock ]; then \
>   break; \
>   fi; \
>   sleep 1; \
> done
> ./hiredis-test -h 127.0.0.1 -p 56379 -s /tmp/hiredis-test-redis.sock || \
>   ( kill `cat /tmp/hiredis-test-redis.pid` && false )
> #01 Format command without interpolation: PASSED
> #02 Format command with %s string interpolation: PASSED
> #03 Format command with %s and an empty string: PASSED
> #04 Format command with an empty string in between proper interpolations: 
> PASSED
> #05 Format command with %b string interpolation: PASSED
> #06 Format command with %b and an empty string: PASSED
> #07 Format command with literal %: PASSED
> #08 Format command with printf-delegation (int): PASSED
> #09 Format command with printf-delegation (char): PASSED
> #10 Format command with printf-delegation (short): PASSED
> #11 Format command with printf-delegation (long): PASSED
> #12 Format command with printf-delegation (long long): PASSED
> #13 Format command with printf-delegation (unsigned int): PASSED
> #14 Format command with printf-delegation (unsigned char): PASSED
> #15 Format command with printf-delegation (unsigned short): 
> PASSED
> #16 Format command with printf-delegation (unsigned long): PASSED
> #17 Format command with printf-delegation (unsigned long long): 
> PASSED
> #18 Format command with printf-delegation (float): PASSED
> #19 Format command with printf-delegation (double): PASSED
> #20 Format command with invalid printf format: PASSED
> #21 Format command by passing argc/argv without lengths: PASSED
> #22 Format command by passing argc/argv with lengths: PASSED
> #23 Format command into sds by passing argc/argv without lengths: 
> PASSED
> #24 Format command into sds by passing argc/argv with lengths: 
> PASSED
> #25 Error handling in reply parser: PASSED
> #26 Memory cleanup in reply parser: PASSED
> #27 Set error on nested multi bulks with depth > 7: PASSED
> #28 Correctly parses LLONG_MAX: PASSED
> #29 Set error when > LLONG_MAX: PASSED
> #30 Correctly parses LLONG_MIN: PASSED
> #31 Set error when < LLONG_MIN: PASSED
> #32 Set error when array < -1: PASSED
> #33 Set error when bulk < -1: PASSED
> #34 Set error when array > INT_MAX: PASSED
> #35 Works with NULL functions for reply: PASSED
> #36 Works when a single newline (\r\n) covers two calls to feed: 
> PASSED
> #37 Don't reset state after protocol error: PASSED
> #38 Don't do empty allocation for empty multi bulk: PASSED
> #39 Returns error when host cannot be resolved: PASSED
> #40 Returns error when the port is not open: PASSED
> #41 Returns error when the unix_sock socket path doesn't accept connections: 
> PASSED
> #42 Don't fail when redisFree is passed a NULL value: PASSED
> #43 Don't fail when freeReplyObject is passed a NULL value: 
> PASSED
> 
> Testing against TCP connection (127.0.0.1:56379):
> #44 Is able to deliver commands: PASSED
> #45 Is a able to send commands verbatim: PASSED
> #46 %s String interpolation works: PASSED
> #47 %b String interpolation works: PASSED
> #48 Binary reply length is correct: PASSED
> #49 Can parse nil replies: PASSED
> #50 Can parse integer replies: [0;32

Bug#1013474: marked as done (libgnatcoll-bindings: FTBFS: ld: final link failed: bad value)

2022-06-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Jun 2022 10:19:51 +
with message-id 
and subject line Bug#1013474: fixed in libgnatcoll-bindings 22.0.0-3
has caused the Debian Bug report #1013474,
regarding libgnatcoll-bindings: FTBFS: ld: final link failed: bad value
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.)


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

Hi,

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


Relevant part (hopefully):
> /usr/bin/ld: /<>/python3/obj/relocatable/python_support.o: 
> relocation R_X86_64_PC32 against symbol `PyExc_TypeError' can not be used 
> when making a shared object; recompile with -fPIC
> /usr/bin/ld: final link failed: bad value
> collect2: error: ld returned 1 exit status


The full build log is available from:
http://qa-logs.debian.net/2022/06/24/libgnatcoll-bindings_22.0.0-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220624;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220624&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: libgnatcoll-bindings
Source-Version: 22.0.0-3
Done: Nicolas Boulenguez 

We believe that the bug you reported is fixed in the latest version of
libgnatcoll-bindings, 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.
Nicolas Boulenguez  (supplier of updated 
libgnatcoll-bindings 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, 27 Jun 2022 10:02:31 +
Source: libgnatcoll-bindings
Architecture: source
Version: 22.0.0-3
Distribution: unstable
Urgency: medium
Maintainer: Nicolas Boulenguez 
Changed-By: Nicolas Boulenguez 
Closes: 1013474
Changes:
 libgnatcoll-bindings (22.0.0-3) unstable; urgency=medium
 .
   * Closes: #1013474. Explicitly select the same compiler for Ada and C
   * Update Standards-Version
Checksums-Sha1:
 e2358715c8c8711d9c37742f2d2df59e348371ed 3387 libgnatcoll-bindings_22.0.0-3.dsc
 99baac9bb6eb517eb3a944f241ed18668c212806 10432 
libgnatcoll-bindings_22.0.0-3.debian.tar.xz
Checksums-Sha256:
 91bc438b046f27b825d802c203627f5f0dda7c919d7b02d8f0dc981672cd0622 3387 
libgnatcoll-bindings_22.0.0-3.dsc
 565151d161219e7b41b72cdc8d5cce6204c33c604a6e54ba1f85826bca8808dd 10432 
libgnatcoll-bindings_22.0.0-3.debian.tar.xz
Files:
 ebdbab750a40b18fb9eda0568fd1f465 3387 libdevel optional 
libgnatcoll-bindings_22.0.0-3.dsc
 883242c6cbc03967cdb8db14e6707df9 10432 libdevel optional 
libgnatcoll-bindings_22.0.0-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEEawm/6zYhqkfTAKHtFHKayZgPCdIFAmK5gWUTHG5pY29sYXNA
ZGViaWFuLm9yZwAKCRAUcprJmA8J0niFEACIz/pI5efDkLq1uGfcfXiJsh5esR35
6a1459wdY8R5DPzZYzupN892zZFIx97H/WW3WxcZvDMV91gYRO4CJ97f0bVBWY+W
BNH4sumJ6wVZLu3kPsiR9OiAZiK96zg+wpS3C9YEi/7J120HdGnJakyH0fHEWQLK
JSNWLVEnQjgn7WWbIHVBJmK7j50/fV+giusVdsUrZ4cnd2Ug8KKZqJxOwbi5FEid
lsKTgZX8HRJD59vLKy9ktTjkwe2ezEB/61uYDvGcJ4DPxUtvYI1+9e++wtU6qa2g
dCVt/jSiUl18SaUaZgk06oOHxf+URja0JqZs/Hz9+b7Nm+VXpt5a60nWbrN0ilCn
lQh/CuSz4D5V8R+vXRJDGLX9KFcws4rnZUdsSZjycsTq+6+nAUP9BAJ5oC80ae7K
jJKtF0pnCKzj9mFV/az7ge2TtCZY0bpOYZgtroGC5G04+rP2T93nKfgjbhHcAHDw
A4gsEle6DkmBZvNq3Inpip6acX/JxNUBUV6k0Mel6q+jxRbKlHlfke9NTkYek9Pd
oSUltle8ytSjeZpgwCNxrA6gc

Bug#1013469: marked as done (libtexttools: FTBFS: ld: final link failed: bad value)

2022-06-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Jun 2022 10:03:58 +
with message-id 
and subject line Bug#1013469: fixed in libtexttools 2.1.0-21
has caused the Debian Bug report #1013469,
regarding libtexttools: FTBFS: ld: final link failed: bad value
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.)


-- 
1013469: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013469
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libtexttools
Version: 2.1.0-20
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220624 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> /usr/bin/ld: /<>/build-obj-dynamic/curses.o: relocation 
> R_X86_64_PC32 against symbol `colour_flag' can not be used when making a 
> shared object; recompile with -fPIC
> /usr/bin/ld: final link failed: bad value
> collect2: error: ld returned 1 exit status


The full build log is available from:
http://qa-logs.debian.net/2022/06/24/libtexttools_2.1.0-20_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220624;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220624&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: libtexttools
Source-Version: 2.1.0-21
Done: Nicolas Boulenguez 

We believe that the bug you reported is fixed in the latest version of
libtexttools, 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.
Nicolas Boulenguez  (supplier of updated libtexttools 
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, 27 Jun 2022 08:43:56 +
Source: libtexttools
Architecture: source
Version: 2.1.0-21
Distribution: unstable
Urgency: medium
Maintainer: Nicolas Boulenguez 
Changed-By: Nicolas Boulenguez 
Closes: 1013469
Changes:
 libtexttools (2.1.0-21) unstable; urgency=medium
 .
   * Closes: #1013469. Explicitly select the same compiler version for Ada and C
   * Trivial simplifications in patches
   * Standards-Version: 4.6.1
   * uscan: use HTTPS download URL, instead of HTTP
Checksums-Sha1:
 180b83b0a7108813d0636546bd3164641358c862 2240 libtexttools_2.1.0-21.dsc
 bc20af57509509f7d0f217ee700b9c5ec48d87f3 9284 
libtexttools_2.1.0-21.debian.tar.xz
Checksums-Sha256:
 70b00d13c62f4e42ed2aeb168daf62ca76e106e1872e748c6aa8dd4ce091d7f7 2240 
libtexttools_2.1.0-21.dsc
 0d30008eae863cd13607ef96d3f164b7476faea7e25199bbc0194fd07a96 9284 
libtexttools_2.1.0-21.debian.tar.xz
Files:
 f13e03a59e9aaebb8add89b3f28f6851 2240 libdevel optional 
libtexttools_2.1.0-21.dsc
 33a7a433ddf697d7018c1c709960f389 9284 libdevel optional 
libtexttools_2.1.0-21.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEEawm/6zYhqkfTAKHtFHKayZgPCdIFAmK5fM8THG5pY29sYXNA
ZGViaWFuLm9yZwAKCRAUcprJmA8J0nTSD/9wa90kxDVJbRGZ1yC2+kJGhfU8+8wQ
xTTgbcqUqt+9IeEGjP2rhAXTJTmwVL1/GQqJ+fg9gq0IRi8dCC6wAeRG+nxewbF7
4ND4b8UuVzhgM83/hRLyQ+upag2JQ89fzu4/SulVZOkHRjMM5YUWXLJcBfygNHaF
Hdj5MpB6zt0Sh2TIpZXbA2pe/FaaeWlHv+4XUfGblUrJDdFrSfPN435hx2JRTc80
6a91/Q+AhCN0H3scD05+wFI54++qdRVLdCGv8hfsnozcocygTfmA95tIwMuOMg32
75oKKzFdejtEgha2PX8+8SXee92zCqHpjwlEiTX5zMI0AeyTX8iEaOroj5RpDgSB
mQAvzhE3oe0WXfVPX6Pl4MVPvfVercsg20jdOH/s0MYPiVfFURTylu0pxfWnQ9Vr
+W1Pi5bJD6ct+8lGeH1RLA0KBPzAzheFPuorVasgh9cDFLKRKIdNRzjvw7Vy/Fol
bqH+iZNXxZt2G1eqUIcr2PUSIG54bztmBRh0BdY1RGuIjCG9yFDnDCdd4xUGVUVW
JqPQOA2TUc9itwo7HWkwzPsgrsjEES7FU9dHSRZKK41FaldIsOVqn2Ajvl949tdd
I

Bug#1013869: rust-reqwest: feature rustls-tls has disappeared

2022-06-27 Thread Jonas Smedegaard
Quoting plugwash (2022-06-27 03:11:42)
> 
> On 27/06/2022 01:15, Jonas Smedegaard wrote:
> > Thanks for clarifying.
> >
> > I consider it a *horrific* bug that an interface is explicitly
> > advertised as available, linking against it succeeds, yet it is
> > non-functional.
> >
> > In my opinion this renders the whole package unsuitable for release, and
> > I hereby flag this bugreport as such.
> >
> > Please as a minimum ensure that broken or missing features are *not*
> > advertised by the package.
> 
> I'll remove the rustls support completely until/unless it can be 
> re-enabled in a sane form.

Please do.  Bogusly advertising a feature not actually provided is what
I find horrific here.  With this change alone I find it sensible to
lower severity of this bugreport back to "normal" (but that is just a
suggestion: you as package maintainer has final say in how you treat
bugreports for this package).


> but lets be clear not every "feature" that exists in a rust crate 
> actually provides useful functionality. The "feature" 
> "rustls-native-certs" was never advertised as providing any particular 
> functionality. At this point I have only removed features, I have not 
> changed the functionality of any existing features. Depending on the 
> "feature" "rustls-native-certs" would be just as useless with the 
> unmodified upstream source as it would be with my patched version.

Removing features but continue advertise them as offered (through
package names containing "+") is what I consider horrific here.

It is arguably correct that you didn't change any *code* but you patched
Cargo.toml file to remove upstream-declared dependencies, causing builds
to succeed that should have failed.


> Assuming tokio-rustls and hyper-rustls are packaged, I do intend to 
> switch the "rustls-tls" feature from being an alias for 
> "rustls-tls-webpki-roots" to being an alias for 
> "rustls-tls-native-roots" in line with what I believe is appropriate for 
> Debian. Indeed I already have a patch in the package doing that, but the 
> feature is currently removed completely by a patch later in the series.

I find it sensible that you choose to skip some features.

I am not sure I find it sensible to *redefine* some features to mean
something else that upstream, however.  If you choose to do that, please
consider making such strong deviation *very* clear - e.g. *both*
document it in README.Debian and *also* mention it in long description.

Let me try clarify my concerns here:

I find it problematic generally is that Debian package deviates notably
from upstream project without it being explicitly documented.  By
explicit documentation I don't mean changelog (and certainly not patch
files installed next to code) but a README.Debian file.

What I then find horrific here is that the vague deviation information
hinted in virtual package names is not reliable.

Please consider documenting deliberate deviation from upstream in
README.Debian, in addition to ensuring that provided package names
accurately reflects the features offered by the package.

And please reconsider your proposed plan to change features to mean
something different from what they are documented upstream to mean -
especially when no Debian-specific documentation is offered!


Thanks,

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature


Bug#1004622: marked as done (dvbcut: FTBFS with ffmpeg 5.0)

2022-06-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Jun 2022 09:48:52 +
with message-id 
and subject line Bug#1004622: fixed in dvbcut 0.7.4-1
has caused the Debian Bug report #1004622,
regarding dvbcut: FTBFS with ffmpeg 5.0
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.)


-- 
1004622: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004622
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dvbcut
Version: 0.7.3-1
Severity: important
X-Debbugs-Cc: sramac...@debian.org
Tags: sid bookworm ftbfs
Usertags: ffmpeg5.0

dvbcut FTBFS with ffmpeg 5.0 (in experimental):
| g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -Wcast-align -DPACKAGE_NAME=\"\" 
-DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" 
-DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DHAVE_LIB_SWSCALE=1 
-DHAVE_LIB_MAD=1 -DHAVE_LIB_A52=1 -DHAVE_LIB_AO=1 -DHAVE_STDIO_H=1 
-DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 
-DHAVE_STRINGS_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 
-DHAVE_SYS_PARAM_H=1 -DSTDC_HEADERS=1 -DHAVE_AO_AO_H=1 -DHAVE_MAD_H=1 
-DHAVE_STDINT_H=1 -DHAVE_A52DEC_A52_H=1 -DHAVE_GETPAGESIZE=1 -DHAVE_MMAP=1 
-D__STDC_LIMIT_MACROS=1 -D__STDC_CONSTANT_MACROS=1 -D_FILE_OFFSET_BITS=64 
-Wdate-time -D_FORTIFY_SOURCE=2 -DDVBCUT_VERSION=\"0.7.3-1\" -fPIC -DQT_XML_LIB 
-DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CORE_LIB 
-I/usr/include/x86_64-linux-gnu/qt5/QtXml -I/usr/include/x86_64-linux-gnu/qt5 
-I/usr/include/x86_64-linux-gnu/qt5/QtWidgets 
-I/usr/include/x86_64-linux-gnu/qt5 -I/usr/include/x86_64-linux-gnu/qt5/QtGui 
-I/usr/include/x86_64-linux-gnu/qt5 -I/usr/include/x86_64-linux-gnu/qt5/QtCore 
-I/usr/include/x86_64-linux-gnu/qt5 -I. -Wdate-time -D_FORTIFY_SOURCE=2 
-DDVBCUT_VERSION=\"0.7.3-1\" -fPIC -DQT_XML_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB 
-DQT_CORE_LIB -I/usr/include/x86_64-linux-gnu/qt5/QtXml 
-I/usr/include/x86_64-linux-gnu/qt5 
-I/usr/include/x86_64-linux-gnu/qt5/QtWidgets 
-I/usr/include/x86_64-linux-gnu/qt5 -I/usr/include/x86_64-linux-gnu/qt5/QtGui 
-I/usr/include/x86_64-linux-gnu/qt5 -I/usr/include/x86_64-linux-gnu/qt5/QtCore 
-I/usr/include/x86_64-linux-gnu/qt5 -I.  -c -o index.o index.cpp
| In file included from mpgfile.h:34,
|  from differenceimageprovider.cpp:25:
| stream.h: In member function ‘void stream::allocavcc()’:
| stream.h:58:5: error: ‘avcodec_get_context_defaults3’ was not declared in 
this scope
|58 | avcodec_get_context_defaults3(avcc, NULL);
|   | ^
| make[2]: *** [: differenceimageprovider.o] Error 1
| make[2]: *** Waiting for unfinished jobs
| eventlistitem.cpp: In member function ‘QString EventListItem::getstring() 
const’:
| eventlistitem.cpp:71:35: warning: ‘QString& QString::sprintf(const char*, 
...)’ is deprecated: Use asprintf(), arg() or QTextStream instead 
[-Wdeprecated-declarations]
|71 |   return label + QString().sprintf("%02d:%02d:%02d.%03d%d 
(%c)",
|   |  
~^~
|72 |int(pts/(3600*9)),
|   |~~
|73 |int(pts/(60*9))%60,
|   |~~~
|74 |int(pts/9)%60,
|   |~~
|75 |int(pts/90)%1000,
|   |~
|76 |pic,
|   |
|77 |((const char *)".IPB")[pictype&7]);
|   |~~
| In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:47,
|  from 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qwidget.h:45,
|  from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qframe.h:44,
|  from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qlabel.h:44,
|  from eventlistitem.cpp:21:
| /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:393:14: note: declared here
|   393 | QString &sprintf(const char *format, ...) 
Q_ATTRIBUTE_FORMAT_PRINTF(2, 3);
|   |  ^~~
| In file included from mpgfile.h:34,
|  from imageprovider.cpp:22:
| stream.h: In member function ‘void stream::allocavcc()’:
| stream.h:58:5: error: ‘avcodec_get_context_defaults3’ was not declared in 
this scope
|58 |  

Bug#1013754: marked as done (python-h5netcdf: FTBFS with NetCDF 4.9.0 (test failures))

2022-06-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Jun 2022 09:34:11 +
with message-id 
and subject line Bug#1013754: fixed in python-h5netcdf 1.0.1-1
has caused the Debian Bug report #1013754,
regarding python-h5netcdf: FTBFS with NetCDF 4.9.0 (test failures)
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.)


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

Dear Maintainer,

Your package FTBFS with NetCDF 4.9.0 which added more compression options, this 
also causes the autopkgtest to fail:

=== FAILURES ===
__ test_write_legacyapi_read_netCDF4 ___

tmp_local_netcdf = 
'/tmp/pytest-of-debci/pytest-0/test_write_legacyapi_read_netC0/testfile.nc'

def test_write_legacyapi_read_netCDF4(tmp_local_netcdf):
>   roundtrip_legacy_netcdf(tmp_local_netcdf, netCDF4, legacyapi)

tests/test_h5netcdf.py:450: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
tests/test_h5netcdf.py:446: in roundtrip_legacy_netcdf
read_legacy_netcdf(tmp_netcdf, read_module, write_module)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

tmp_netcdf = 
'/tmp/pytest-of-debci/pytest-0/test_write_legacyapi_read_netC0/testfile.nc'
read_module = 
write_module = 

def read_legacy_netcdf(tmp_netcdf, read_module, write_module):
ds = read_module.Dataset(tmp_netcdf, "r")
assert ds.ncattrs() == ["global", "other_attr"]
assert ds.getncattr("global") == 42
if write_module is not netCDF4:
# skip for now: https://github.com/Unidata/netcdf4-python/issues/388
assert ds.other_attr == "yes"
with pytest.raises(AttributeError):
ds.does_not_exist
assert set(ds.dimensions) == set(
["x", "y", "z", "empty", "string3", "mismatched_dim", "unlimited"]
)
assert set(ds.variables) == set(
[
"foo",
"y",
"z",
"intscalar",
"scalar",
"var_len_str",
"mismatched_dim",
"foo_unlimited",
]
)

assert set(ds.groups) == set(["subgroup"])
assert ds.parent is None
v = ds.variables["foo"]
assert array_equal(v, np.ones((4, 5)))
assert v.dtype == float
assert v.dimensions == ("x", "y")
assert v.ndim == 2
assert v.ncattrs() == ["units"]
if write_module is not netCDF4:
assert v.getncattr("units") == "meters"
assert tuple(v.chunking()) == (4, 5)
>   assert v.filters() == {
"complevel": 4,
"fletcher32": False,
"shuffle": True,
"zlib": True,
}
E   AssertionError: assert {'blosc': Fal...': False, ...} == 
{'complevel':... 'zlib': True}
E Omitting 4 identical items, use -vv to show
E Left contains 4 more items:
E {'blosc': False, 'bzip2': False, 'szip': False, 'zstd': False}
E Use -v to get the full diff

tests/test_h5netcdf.py:259: AssertionError
___ test_write_h5netcdf_read_netCDF4 ___

tmp_local_netcdf = 
'/tmp/pytest-of-debci/pytest-0/test_write_h5netcdf_read_netCD0/testfile.nc'

def test_write_h5netcdf_read_netCDF4(tmp_local_netcdf):
write_h5netcdf(tmp_local_netcdf)
>   read_legacy_netcdf(tmp_local_netcdf, netCDF4, h5netcdf)

tests/test_h5netcdf.py:468: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

tmp_netcdf = 
'/tmp/pytest-of-debci/pytest-0/test_write_h5netcdf_read_netCD0/testfile.nc'
read_module = 
write_module = 

def read_legacy_netcdf(tmp_netcdf, read_module, write_module):
ds = read_module.Dataset(tmp_netcdf, "r")
assert ds.ncattrs() == ["global", "other_attr"]
assert ds.getncattr("global") == 42
if write_module is not netCDF4:
# skip for now: https://github.com/Unidata/netcdf4-python/issues/388
assert ds.other_attr == "yes"
with pytest.raises(AttributeError):
ds.does_not_exist
assert set(ds.dimensions) == set(
["x", "y", "z", "empty", "string3", "mismatched_dim", "unlimited"]
)
assert set(ds.variables) == set(
[
"foo",
"y",
"z",
  

Processed: merge 1013537 1013085

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

> forwarded 1013537 https://gitlab.com/ase/ase/-/issues/1038
Bug #1013537 [src:python-ase] python-ase: FTBFS: dh_auto_test: error: pybuild 
--test --test-pytest -i python{version} -p "3.9 3.10" returned exit code 13
Set Bug forwarded-to-address to 'https://gitlab.com/ase/ase/-/issues/1038'.
> merge 1013537 1013085
Bug #1013537 [src:python-ase] python-ase: FTBFS: dh_auto_test: error: pybuild 
--test --test-pytest -i python{version} -p "3.9 3.10" returned exit code 13
Bug #1013537 [src:python-ase] python-ase: FTBFS: dh_auto_test: error: pybuild 
--test --test-pytest -i python{version} -p "3.9 3.10" returned exit code 13
Added tag(s) upstream, patch, and pending.
Bug #1013085 [src:python-ase] python-ase: 
scipy.constants.codata._physical_constants_ no longer in scipy-1.8.0
Added tag(s) bookworm, ftbfs, and sid.
Merged 1013085 1013537
> thanks
Stopping processing here.

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



Bug#1013910: src:mlucas: invalid maintainer address

2022-06-27 Thread Ansgar
Source: mlucas
Version: 20.1.1-1
Severity: serious
X-Debbugs-Cc: Adam Borowski 

The maintainer address for src:mlucas is obviously invalid:

Maintainer: Alex Vong 

Ansgar



Bug#1013085: marked as pending in python-ase

2022-06-27 Thread Andrius Merkys
Control: tag -1 pending

Hello,

Bug #1013085 in python-ase 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/debichem-team/python-ase/-/commit/c46ddfb3c73b679151f71a98920ce19933523ba4


Fix test failure due to the usage of deprecated scipy API (Closes: #1013085)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1013085



Bug#1013877: marked as done (libtk-img: add _TIFFsetString to its internal tiff library)

2022-06-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Jun 2022 08:36:36 +
with message-id 
and subject line Bug#1013877: fixed in libtk-img 1:1.4.13+dfsg-2
has caused the Debian Bug report #1013877,
regarding libtk-img: add _TIFFsetString to its internal tiff library
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.)


-- 
1013877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013877
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linuxcnc-uspace
Version: 2.9.0~pre0+git20220402.2500863908-4
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: vectorhast...@gmail.com

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation? I installed the package from respository 
with sudo apt-get install
   * What exactly did you do (or not do) that was effective (or
 ineffective)? Tried to understand from the error message if there was a 
missing package, but could not find one.
   * What was the outcome of this action? It did not help
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


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

Kernel: Linux 4.19.0-20-rt-arm64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linuxcnc-uspace depends on:
ii  blt2.5.3+dfsg-4.1
ii  bwidget1.9.15-1
ii  iptables   1.8.8-1
ii  libboost-python1.74.0  1.74.0-16
ii  libc6  2.33-7
ii  libcairo2  1.16.0-5
ii  libedit2   3.1-20210910-1
ii  libepoxy0  1.5.10-1
ii  libgcc-s1  12.1.0-2
ii  libglib2.0-0   2.72.2-2
ii  libgtk-3-0 3.24.34-1
ii  libgtk2.0-02.24.33-2
ii  libgtksourceview-3.0-dev   3.24.11-2+b1
ii  libmodbus5 3.1.6-2
ii  libpango-1.0-0 1.50.7+ds-1
ii  libpangocairo-1.0-01.50.7+ds-1
ii  libpython3.10  3.10.5-1
ii  libstdc++6 12.1.0-2
ii  libtirpc3  1.3.2-2
ii  libtk-img  1:1.4.13+dfsg-1
ii  libtk8.6   8.6.12-1
ii  libudev-dev251.2-5
ii  libudev1   251.2-5
ii  libusb-1.0-0   2:1.0.26-1
ii  libx11-6   2:1.7.5-1
ii  libxinerama1   2:1.1.4-3
ii  libxmu62:1.1.3-3
ii  mesa-utils 8.5.0-1
ii  procps 2:3.3.17-7+b1
ii  psmisc 23.5-1
ii  python33.10.4-1+b1
ii  python3-cairo  1.20.1-3
ii  python3-configobj  5.0.6-5
ii  python3-gi-cairo   3.42.1-1
ii  python3-numpy  1:1.21.5-1
ii  python3-opengl 3.1.5+dfsg-1
ii  python3-tk 3.10.5-1
ii  python3-xlib   0.29-1
ii  tcl-tclreadline [tclreadline]  2.3.8-1
ii  tcl8.6 8.6.12+dfsg-1
ii  tclx8.4 [tclx] 8.4.1-4
ii  tk8.6  8.6.12-1
ii  udev   251.2-5

Versions of packages linuxcnc-uspace recommends:
ii  espeak  1.48.15+dfsg-3
ii  espeak-ng   1.51+dfsg-7
ii  gstreamer1.0-tools  1.20.2-1
pn  hostmot2-firmware-all   
ii  librsvg2-dev2.54.3+dfsg-1
ii  linuxcnc-doc-en [linuxcnc-doc]  2.9.0~pre0+git20220402.2500863908-4
ii  pyqt5-dev-tools 5.15.6+dfsg-1+b2
ii  python3-dbus1.2.18-3+b1
ii  python3-dbus.mainloop.pyqt5 5.15.6+dfsg-1+b2
ii  python3-espeak  0.5-4+b1
ii  python3-opencv  4.5.4+dfsg-9+b7
ii  python3-pil 9.1.1-1
ii  python3-pil.imagetk 9.1.1-1
ii  python3-pyqt5   5.15.6+dfsg-1+b2
ii  python3-pyqt5.qsci  2.11.6+dfsg-4+b1
ii  python3-pyqt5.qtopengl  5.15.6+dfsg-1+b2
ii  python3-pyqt5.qtsvg 5.15.6+dfsg-1+b2
ii  python3-pyqt5.qtwebkit  5.15.6+dfsg-1+b2
ii  sound-theme-freedesktop 0.8-2

Versions of packages linuxcnc-uspace suggests:

Bug#1013877: marked as done (libtk-img: add _TIFFsetString to its internal tiff library)

2022-06-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Jun 2022 08:36:36 +
with message-id 
and subject line Bug#1013878: fixed in libtk-img 1:1.4.13+dfsg-2
has caused the Debian Bug report #1013878,
regarding libtk-img: add _TIFFsetString to its internal tiff library
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.)


-- 
1013878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013878
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linuxcnc-uspace
Version: 2.9.0~pre0+git20220402.2500863908-4
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: vectorhast...@gmail.com

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation? I installed the package from respository 
with sudo apt-get install
   * What exactly did you do (or not do) that was effective (or
 ineffective)? Tried to understand from the error message if there was a 
missing package, but could not find one.
   * What was the outcome of this action? It did not help
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


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

Kernel: Linux 4.19.0-20-rt-arm64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linuxcnc-uspace depends on:
ii  blt2.5.3+dfsg-4.1
ii  bwidget1.9.15-1
ii  iptables   1.8.8-1
ii  libboost-python1.74.0  1.74.0-16
ii  libc6  2.33-7
ii  libcairo2  1.16.0-5
ii  libedit2   3.1-20210910-1
ii  libepoxy0  1.5.10-1
ii  libgcc-s1  12.1.0-2
ii  libglib2.0-0   2.72.2-2
ii  libgtk-3-0 3.24.34-1
ii  libgtk2.0-02.24.33-2
ii  libgtksourceview-3.0-dev   3.24.11-2+b1
ii  libmodbus5 3.1.6-2
ii  libpango-1.0-0 1.50.7+ds-1
ii  libpangocairo-1.0-01.50.7+ds-1
ii  libpython3.10  3.10.5-1
ii  libstdc++6 12.1.0-2
ii  libtirpc3  1.3.2-2
ii  libtk-img  1:1.4.13+dfsg-1
ii  libtk8.6   8.6.12-1
ii  libudev-dev251.2-5
ii  libudev1   251.2-5
ii  libusb-1.0-0   2:1.0.26-1
ii  libx11-6   2:1.7.5-1
ii  libxinerama1   2:1.1.4-3
ii  libxmu62:1.1.3-3
ii  mesa-utils 8.5.0-1
ii  procps 2:3.3.17-7+b1
ii  psmisc 23.5-1
ii  python33.10.4-1+b1
ii  python3-cairo  1.20.1-3
ii  python3-configobj  5.0.6-5
ii  python3-gi-cairo   3.42.1-1
ii  python3-numpy  1:1.21.5-1
ii  python3-opengl 3.1.5+dfsg-1
ii  python3-tk 3.10.5-1
ii  python3-xlib   0.29-1
ii  tcl-tclreadline [tclreadline]  2.3.8-1
ii  tcl8.6 8.6.12+dfsg-1
ii  tclx8.4 [tclx] 8.4.1-4
ii  tk8.6  8.6.12-1
ii  udev   251.2-5

Versions of packages linuxcnc-uspace recommends:
ii  espeak  1.48.15+dfsg-3
ii  espeak-ng   1.51+dfsg-7
ii  gstreamer1.0-tools  1.20.2-1
pn  hostmot2-firmware-all   
ii  librsvg2-dev2.54.3+dfsg-1
ii  linuxcnc-doc-en [linuxcnc-doc]  2.9.0~pre0+git20220402.2500863908-4
ii  pyqt5-dev-tools 5.15.6+dfsg-1+b2
ii  python3-dbus1.2.18-3+b1
ii  python3-dbus.mainloop.pyqt5 5.15.6+dfsg-1+b2
ii  python3-espeak  0.5-4+b1
ii  python3-opencv  4.5.4+dfsg-9+b7
ii  python3-pil 9.1.1-1
ii  python3-pil.imagetk 9.1.1-1
ii  python3-pyqt5   5.15.6+dfsg-1+b2
ii  python3-pyqt5.qsci  2.11.6+dfsg-4+b1
ii  python3-pyqt5.qtopengl  5.15.6+dfsg-1+b2
ii  python3-pyqt5.qtsvg 5.15.6+dfsg-1+b2
ii  python3-pyqt5.qtwebkit  5.15.6+dfsg-1+b2
ii  sound-theme-freedesktop 0.8-2

Versions of packages linuxcnc-uspace suggests:

Processed: Bug#1013085 marked as pending in python-ase

2022-06-27 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #1013085 [src:python-ase] python-ase: 
scipy.constants.codata._physical_constants_ no longer in scipy-1.8.0
Added tag(s) pending.

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



Bug#1013878: marked as done (libtk-img: add _TIFFsetString to its internal tiff library)

2022-06-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Jun 2022 08:36:36 +
with message-id 
and subject line Bug#1013878: fixed in libtk-img 1:1.4.13+dfsg-2
has caused the Debian Bug report #1013878,
regarding libtk-img: add _TIFFsetString to its internal tiff library
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.)


-- 
1013878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013878
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linuxcnc-uspace
Version: 2.9.0~pre0+git20220402.2500863908-4
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: vectorhast...@gmail.com

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation? I installed the package from respository 
with sudo apt-get install
   * What exactly did you do (or not do) that was effective (or
 ineffective)? Tried to understand from the error message if there was a 
missing package, but could not find one.
   * What was the outcome of this action? It did not help
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


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

Kernel: Linux 4.19.0-20-rt-arm64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linuxcnc-uspace depends on:
ii  blt2.5.3+dfsg-4.1
ii  bwidget1.9.15-1
ii  iptables   1.8.8-1
ii  libboost-python1.74.0  1.74.0-16
ii  libc6  2.33-7
ii  libcairo2  1.16.0-5
ii  libedit2   3.1-20210910-1
ii  libepoxy0  1.5.10-1
ii  libgcc-s1  12.1.0-2
ii  libglib2.0-0   2.72.2-2
ii  libgtk-3-0 3.24.34-1
ii  libgtk2.0-02.24.33-2
ii  libgtksourceview-3.0-dev   3.24.11-2+b1
ii  libmodbus5 3.1.6-2
ii  libpango-1.0-0 1.50.7+ds-1
ii  libpangocairo-1.0-01.50.7+ds-1
ii  libpython3.10  3.10.5-1
ii  libstdc++6 12.1.0-2
ii  libtirpc3  1.3.2-2
ii  libtk-img  1:1.4.13+dfsg-1
ii  libtk8.6   8.6.12-1
ii  libudev-dev251.2-5
ii  libudev1   251.2-5
ii  libusb-1.0-0   2:1.0.26-1
ii  libx11-6   2:1.7.5-1
ii  libxinerama1   2:1.1.4-3
ii  libxmu62:1.1.3-3
ii  mesa-utils 8.5.0-1
ii  procps 2:3.3.17-7+b1
ii  psmisc 23.5-1
ii  python33.10.4-1+b1
ii  python3-cairo  1.20.1-3
ii  python3-configobj  5.0.6-5
ii  python3-gi-cairo   3.42.1-1
ii  python3-numpy  1:1.21.5-1
ii  python3-opengl 3.1.5+dfsg-1
ii  python3-tk 3.10.5-1
ii  python3-xlib   0.29-1
ii  tcl-tclreadline [tclreadline]  2.3.8-1
ii  tcl8.6 8.6.12+dfsg-1
ii  tclx8.4 [tclx] 8.4.1-4
ii  tk8.6  8.6.12-1
ii  udev   251.2-5

Versions of packages linuxcnc-uspace recommends:
ii  espeak  1.48.15+dfsg-3
ii  espeak-ng   1.51+dfsg-7
ii  gstreamer1.0-tools  1.20.2-1
pn  hostmot2-firmware-all   
ii  librsvg2-dev2.54.3+dfsg-1
ii  linuxcnc-doc-en [linuxcnc-doc]  2.9.0~pre0+git20220402.2500863908-4
ii  pyqt5-dev-tools 5.15.6+dfsg-1+b2
ii  python3-dbus1.2.18-3+b1
ii  python3-dbus.mainloop.pyqt5 5.15.6+dfsg-1+b2
ii  python3-espeak  0.5-4+b1
ii  python3-opencv  4.5.4+dfsg-9+b7
ii  python3-pil 9.1.1-1
ii  python3-pil.imagetk 9.1.1-1
ii  python3-pyqt5   5.15.6+dfsg-1+b2
ii  python3-pyqt5.qsci  2.11.6+dfsg-4+b1
ii  python3-pyqt5.qtopengl  5.15.6+dfsg-1+b2
ii  python3-pyqt5.qtsvg 5.15.6+dfsg-1+b2
ii  python3-pyqt5.qtwebkit  5.15.6+dfsg-1+b2
ii  sound-theme-freedesktop 0.8-2

Versions of packages linuxcnc-uspace suggests:

Bug#1013878: marked as done (libtk-img: add _TIFFsetString to its internal tiff library)

2022-06-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Jun 2022 08:36:36 +
with message-id 
and subject line Bug#1013877: fixed in libtk-img 1:1.4.13+dfsg-2
has caused the Debian Bug report #1013877,
regarding libtk-img: add _TIFFsetString to its internal tiff library
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.)


-- 
1013877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013877
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linuxcnc-uspace
Version: 2.9.0~pre0+git20220402.2500863908-4
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: vectorhast...@gmail.com

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation? I installed the package from respository 
with sudo apt-get install
   * What exactly did you do (or not do) that was effective (or
 ineffective)? Tried to understand from the error message if there was a 
missing package, but could not find one.
   * What was the outcome of this action? It did not help
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


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

Kernel: Linux 4.19.0-20-rt-arm64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linuxcnc-uspace depends on:
ii  blt2.5.3+dfsg-4.1
ii  bwidget1.9.15-1
ii  iptables   1.8.8-1
ii  libboost-python1.74.0  1.74.0-16
ii  libc6  2.33-7
ii  libcairo2  1.16.0-5
ii  libedit2   3.1-20210910-1
ii  libepoxy0  1.5.10-1
ii  libgcc-s1  12.1.0-2
ii  libglib2.0-0   2.72.2-2
ii  libgtk-3-0 3.24.34-1
ii  libgtk2.0-02.24.33-2
ii  libgtksourceview-3.0-dev   3.24.11-2+b1
ii  libmodbus5 3.1.6-2
ii  libpango-1.0-0 1.50.7+ds-1
ii  libpangocairo-1.0-01.50.7+ds-1
ii  libpython3.10  3.10.5-1
ii  libstdc++6 12.1.0-2
ii  libtirpc3  1.3.2-2
ii  libtk-img  1:1.4.13+dfsg-1
ii  libtk8.6   8.6.12-1
ii  libudev-dev251.2-5
ii  libudev1   251.2-5
ii  libusb-1.0-0   2:1.0.26-1
ii  libx11-6   2:1.7.5-1
ii  libxinerama1   2:1.1.4-3
ii  libxmu62:1.1.3-3
ii  mesa-utils 8.5.0-1
ii  procps 2:3.3.17-7+b1
ii  psmisc 23.5-1
ii  python33.10.4-1+b1
ii  python3-cairo  1.20.1-3
ii  python3-configobj  5.0.6-5
ii  python3-gi-cairo   3.42.1-1
ii  python3-numpy  1:1.21.5-1
ii  python3-opengl 3.1.5+dfsg-1
ii  python3-tk 3.10.5-1
ii  python3-xlib   0.29-1
ii  tcl-tclreadline [tclreadline]  2.3.8-1
ii  tcl8.6 8.6.12+dfsg-1
ii  tclx8.4 [tclx] 8.4.1-4
ii  tk8.6  8.6.12-1
ii  udev   251.2-5

Versions of packages linuxcnc-uspace recommends:
ii  espeak  1.48.15+dfsg-3
ii  espeak-ng   1.51+dfsg-7
ii  gstreamer1.0-tools  1.20.2-1
pn  hostmot2-firmware-all   
ii  librsvg2-dev2.54.3+dfsg-1
ii  linuxcnc-doc-en [linuxcnc-doc]  2.9.0~pre0+git20220402.2500863908-4
ii  pyqt5-dev-tools 5.15.6+dfsg-1+b2
ii  python3-dbus1.2.18-3+b1
ii  python3-dbus.mainloop.pyqt5 5.15.6+dfsg-1+b2
ii  python3-espeak  0.5-4+b1
ii  python3-opencv  4.5.4+dfsg-9+b7
ii  python3-pil 9.1.1-1
ii  python3-pil.imagetk 9.1.1-1
ii  python3-pyqt5   5.15.6+dfsg-1+b2
ii  python3-pyqt5.qsci  2.11.6+dfsg-4+b1
ii  python3-pyqt5.qtopengl  5.15.6+dfsg-1+b2
ii  python3-pyqt5.qtsvg 5.15.6+dfsg-1+b2
ii  python3-pyqt5.qtwebkit  5.15.6+dfsg-1+b2
ii  sound-theme-freedesktop 0.8-2

Versions of packages linuxcnc-uspace suggests:

Bug#1013479: marked as done (libncursesada: FTBFS: ld: final link failed: bad value)

2022-06-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Jun 2022 08:36:29 +
with message-id 
and subject line Bug#1013479: fixed in libncursesada 6.3.20211021-3
has caused the Debian Bug report #1013479,
regarding libncursesada: FTBFS: ld: final link failed: bad value
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.)


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

Hi,

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


Relevant part (hopefully):
> /usr/bin/ld: 
> /<>/debian/build/obj-dynamic/c_threaded_variables.o: relocation 
> R_X86_64_PC32 against symbol `stdscr@@NCURSES6_TINFO_5.0.19991023' can not be 
> used when making a shared object; recompile with -fPIC
> /usr/bin/ld: final link failed: bad value
> collect2: error: ld returned 1 exit status


The full build log is available from:
http://qa-logs.debian.net/2022/06/24/libncursesada_6.3.20211021-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220624;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220624&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: libncursesada
Source-Version: 6.3.20211021-3
Done: Nicolas Boulenguez 

We believe that the bug you reported is fixed in the latest version of
libncursesada, 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.
Nicolas Boulenguez  (supplier of updated libncursesada 
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, 26 Jun 2022 22:13:32 +
Source: libncursesada
Architecture: source
Version: 6.3.20211021-3
Distribution: unstable
Urgency: medium
Maintainer: Nicolas Boulenguez 
Changed-By: Nicolas Boulenguez 
Closes: 1013479
Changes:
 libncursesada (6.3.20211021-3) unstable; urgency=medium
 .
   * Closes: #1013479. Explicitly select the same compiler for Ada and C
 instead of relying on broken black magic in gprconfig-kb.
   * Bump Standards-Version.
Checksums-Sha1:
 7d9c777493012fb78d50d772585d5cd0b3962ea2 2308 libncursesada_6.3.20211021-3.dsc
 065be6ca5b3b614c91de5eda28e3666c631db6c8 11964 
libncursesada_6.3.20211021-3.debian.tar.xz
Checksums-Sha256:
 b8a38ca1d70a49c20075de023c1308dac6706fc85ed91ae380371e0d06700699 2308 
libncursesada_6.3.20211021-3.dsc
 9a9f5275cd53c19ceb3fb7ce8297f6b5d035cf5f386533cd26add892a3c17cd3 11964 
libncursesada_6.3.20211021-3.debian.tar.xz
Files:
 bd17a46bf4465a69d305a72cda3c56d0 2308 libdevel optional 
libncursesada_6.3.20211021-3.dsc
 4f2beaf00318e98c4686aad2bc2fd4a1 11964 libdevel optional 
libncursesada_6.3.20211021-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEEawm/6zYhqkfTAKHtFHKayZgPCdIFAmK5ZGYTHG5pY29sYXNA
ZGViaWFuLm9yZwAKCRAUcprJmA8J0spfD/0W5670ipj+fi9Ab/3YOBVXD2q/1Orx
09aV/LhGbS6Dg7IRkJ3WPOcflh+NLB9ur+claNv4iedqJaw2rtJjfnQOhQfdHf+r
/b4hlcWiF45EQ7T8w5CYPIQmnrBJjf0O4Jp1lLXQlFPjYEXUB8Fqc+9kqC2sB/ua
GhihB6M4B/V9oqAGjQFMJVgvsebThtV+OIQaln69VkfeHRAFGd+LOdIsiPt2/DJU
MfXfOyTkAUs2fjgJ3s3qxbyAPdg+R55EKEwEg5cePPNjrJd7si1BrvA5KWbA0KQh
IIv9IJlnb405Sqr8Eu3HwdRMD/9dLmzO4ZFXXDctm4ctco4plD3KVVixyeovjaPv
Vu4NIht0qC53anpzugM4h5Cyya7EUEExfrIjdeN0Fh7kNanL6V9mwe26MKfAyJip
nixjewX+agvcjg2lIaMzKn5kvi70gpXVY+PxRYQjcnNloFlv1ohZRJfGCKE+9jgY
oDM+B2tfwS3DS1nd3YQRjDoF4WnkRHh

Bug#1012795: marked as done (libengine-gost-openssl1.1: Shared library file in /)

2022-06-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Jun 2022 10:57:37 +0300
with message-id 

and subject line Re: Bug#1012795: libengine-gost-openssl1.1: Shared library 
file in /
has caused the Debian Bug report #1012795,
regarding libengine-gost-openssl1.1: Shared library file in /
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.)


-- 
1012795: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012795
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libengine-gost-openssl1.1
Version: 1.1.0.3-1.1
Severity: important

Dear Maintainer,

The package is ill-configured and end up
putting gost.so in the root of the filesystem (/gost.so),
as shown in [1].
The source of the issue is [2], which is empty...

[1] https://packages.debian.org/sid/amd64/libengine-gost-openssl1.1/filelist
[2] 
https://sources.debian.org/src/libengine-gost-openssl1.1/1.1.0.3-1.1/debian/rules/#L22

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

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

Versions of packages libengine-gost-openssl1.1 depends on:
ii  libc62.33-7
ii  libssl3  3.0.3-7

libengine-gost-openssl1.1 recommends no packages.

libengine-gost-openssl1.1 suggests no packages.

-- 

Cédric Hannotier
--- End Message ---
--- Begin Message ---
Fixed in 3.0.1-1.

On Tue, Jun 14, 2022 at 6:44 PM Wartan Hachaturow <
wartan.hachatu...@gmail.com> wrote:

> This seems to be caused by last NMU :(
> libengine-gost-openssl 3.0.1-1, which fixes that (and other) problem, and
> also deprecates libengine-gost-openssl1.1, is in the NEW queue.
> I will leave the bug open, though, until it installs in the archive, as a
> reminder.
>
> Thanks for the report!
>
> On Tue, Jun 14, 2022, 11:39 Cédric Hannotier 
> wrote:
>
>> Package: libengine-gost-openssl1.1
>> Version: 1.1.0.3-1.1
>> Severity: important
>>
>> Dear Maintainer,
>>
>> The package is ill-configured and end up
>> putting gost.so in the root of the filesystem (/gost.so),
>> as shown in [1].
>> The source of the issue is [2], which is empty...
>>
>> [1]
>> https://packages.debian.org/sid/amd64/libengine-gost-openssl1.1/filelist
>> [2]
>> https://sources.debian.org/src/libengine-gost-openssl1.1/1.1.0.3-1.1/debian/rules/#L22
>>
>> -- System Information:
>> Debian Release: bookworm/sid
>>   APT prefers testing
>>   APT policy: (990, 'testing'), (500, 'unstable-debug'), (500,
>> 'testing-debug'), (500, 'unstable'), (1, 'experimental')
>> Architecture: amd64 (x86_64)
>>
>> Kernel: Linux 5.17.0-1-amd64 (SMP w/12 CPU threads; PREEMPT)
>> Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8),
>> LANGUAGE=en_US:en
>> Shell: /bin/sh linked to /usr/bin/dash
>> Init: systemd (via /run/systemd/system)
>> LSM: AppArmor: enabled
>>
>> Versions of packages libengine-gost-openssl1.1 depends on:
>> ii  libc62.33-7
>> ii  libssl3  3.0.3-7
>>
>> libengine-gost-openssl1.1 recommends no packages.
>>
>> libengine-gost-openssl1.1 suggests no packages.
>>
>> --
>>
>> Cédric Hannotier
>>
>
--- End Message ---


Bug#1013534: marked as done (python-django-celery-beat: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.10" returned exit code 13)

2022-06-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Jun 2022 07:50:27 +
with message-id 
and subject line Bug#1013534: fixed in python-django-celery-beat 2.3.0-1
has caused the Debian Bug report #1013534,
regarding python-django-celery-beat: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p "3.9 3.10" returned exit code 13
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.)


-- 
1013534: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013534
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-django-celery-beat
Version: 2.2.1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220624 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build
> I: pybuild base:239: /usr/bin/python3.9 setup.py build 
> running build
> running build_py
> creating 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat
> copying django_celery_beat/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat
> copying django_celery_beat/models.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat
> copying django_celery_beat/tzcrontab.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat
> copying django_celery_beat/validators.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat
> copying django_celery_beat/schedulers.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat
> copying django_celery_beat/apps.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat
> copying django_celery_beat/clockedschedule.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat
> copying django_celery_beat/admin.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat
> copying django_celery_beat/managers.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat
> copying django_celery_beat/utils.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat
> creating 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat/migrations
> copying django_celery_beat/migrations/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat/migrations
> copying 
> django_celery_beat/migrations/0015_edit_solarschedule_events_choices.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat/migrations
> copying django_celery_beat/migrations/0004_auto_20170221_.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat/migrations
> copying django_celery_beat/migrations/0006_periodictask_priority.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat/migrations
> copying django_celery_beat/migrations/0006_auto_20180210_1226.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat/migrations
> copying django_celery_beat/migrations/0001_initial.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat/migrations
> copying django_celery_beat/migrations/0006_auto_20180322_0932.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat/migrations
> copying django_celery_beat/migrations/0013_auto_20200609_0727.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat/migrations
> copying django_celery_beat/migrations/0009_periodictask_headers.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat/migrations
> copying django_celery_beat/migrations/0014_remove_clockedschedule_enabled.py 
> -> 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat/migrations
> copying 
> django_celery_beat/migrations/0005_add_solarschedule_events_choices.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat/migrations
> copying django_celery_beat/migrations/0007_auto_20180521_0826.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat/migrations
> copying django_celery_beat/migrations/0011_auto_20190508_0153.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat/migrations
> copying django_celery_beat/migrations/0002_auto_20161118_0346.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-beat/build/django_celery_beat/migrations
> copying django_celery_beat/migrations/0008_auto_20180914_1922.py -> 
> /<>/.pybuild/cpython3_3.9_dj

Processed: Re: python-h5netcdf: FTBFS with NetCDF 4.9.0 (test failures)

2022-06-27 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 fixed-upstream
Bug #1013754 [src:python-h5netcdf] python-h5netcdf: FTBFS with NetCDF 4.9.0 
(test failures)
Added tag(s) fixed-upstream.

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



Bug#1013754: python-h5netcdf: FTBFS with NetCDF 4.9.0 (test failures)

2022-06-27 Thread Sebastiaan Couwenberg

Control: tags -1 fixed-upstream

On 6/25/22 14:30, Bas Couwenberg wrote:

The attached patch fixes the issue.


Upstream has published a new release with a fix for this issue:

"
 h5netcdf patch release 1.0.1 is available on PyPI now.
"

Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1



Bug#1013566: [Pkg-javascript-devel] Bug#1013566: node-sockjs: FTBFS: sockjs.coffee:137:9: error: Can't reference 'this' before calling super in derived class constructors

2022-06-27 Thread Andrius Merkys
Hi Yadd,

On 2022-06-24 17:10, Yadd wrote:
> I prepared a fix, pushed to salsa. Could you take a look ?

Thanks a lot, reviewed and uploaded.

Best wishes,
Andrius



Bug#1013534: marked as pending in python-django-celery-beat

2022-06-27 Thread Michael Fladischer
Control: tag -1 pending

Hello,

Bug #1013534 in python-django-celery-beat 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/python-team/packages/python-django-celery-beat/-/commit/4b6b369bd88a633081e9aa029862b2802378101f


New upstream release (Closes: #1013534).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1013534



Processed: Bug#1013534 marked as pending in python-django-celery-beat

2022-06-27 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #1013534 [src:python-django-celery-beat] python-django-celery-beat: FTBFS: 
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 
3.10" returned exit code 13
Added tag(s) pending.

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



Bug#1013567: marked as done (sunpy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.10" returned exit code 13)

2022-06-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Jun 2022 07:18:54 +
with message-id 
and subject line Bug#1013567: fixed in sunpy 4.0.2-1
has caused the Debian Bug report #1013567,
regarding sunpy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i 
python{version} -p "3.9 3.10" returned exit code 13
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.)


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

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:239: python3.9 setup.py config 
> running config
> I: pybuild base:239: python3.10 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:239: /usr/bin/python3.9 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9_sunpy/build/sunpy
> copying sunpy/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_sunpy/build/sunpy
> copying sunpy/conftest.py -> 
> /<>/.pybuild/cpython3_3.9_sunpy/build/sunpy
> copying sunpy/_version.py -> 
> /<>/.pybuild/cpython3_3.9_sunpy/build/sunpy
> copying sunpy/version.py -> 
> /<>/.pybuild/cpython3_3.9_sunpy/build/sunpy
> creating /<>/.pybuild/cpython3_3.9_sunpy/build/sunpy/sun
> copying sunpy/sun/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_sunpy/build/sunpy/sun
> copying sunpy/sun/_constants.py -> 
> /<>/.pybuild/cpython3_3.9_sunpy/build/sunpy/sun
> copying sunpy/sun/models.py -> 
> /<>/.pybuild/cpython3_3.9_sunpy/build/sunpy/sun
> copying sunpy/sun/constants.py -> 
> /<>/.pybuild/cpython3_3.9_sunpy/build/sunpy/sun
> creating /<>/.pybuild/cpython3_3.9_sunpy/build/sunpy/map
> copying sunpy/map/map_factory.py -> 
> /<>/.pybuild/cpython3_3.9_sunpy/build/sunpy/map
> copying sunpy/map/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_sunpy/build/sunpy/map
> copying sunpy/map/compositemap.py -> 
> /<>/.pybuild/cpython3_3.9_sunpy/build/sunpy/map
> copying sunpy/map/header_helper.py -> 
> /<>/.pybuild/cpython3_3.9_sunpy/build/sunpy/map
> copying sunpy/map/_units.py -> 
> /<>/.pybuild/cpython3_3.9_sunpy/build/sunpy/map
> copying sunpy/map/mapsequence.py -> 
> /<>/.pybuild/cpython3_3.9_sunpy/build/sunpy/map
> copying sunpy/map/mapbase.py -> 
> /<>/.pybuild/cpython3_3.9_sunpy/build/sunpy/map
> copying sunpy/map/maputils.py -> 
> /<>/.pybuild/cpython3_3.9_sunpy/build/sunpy/map
> creating 
> /<>/.pybuild/cpython3_3.9_sunpy/build/sunpy/visualization
> copying sunpy/visualization/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_sunpy/build/sunpy/visualization
> copying sunpy/visualization/limb.py -> 
> /<>/.pybuild/cpython3_3.9_sunpy/build/sunpy/visualization
> copying sunpy/visualization/wcsaxes_compat.py -> 
> /<>/.pybuild/cpython3_3.9_sunpy/build/sunpy/visualization
> copying sunpy/visualization/visualization.py -> 
> /<>/.pybuild/cpython3_3.9_sunpy/build/sunpy/visualization
> creating /<>/.pybuild/cpython3_3.9_sunpy/build/sunpy/physics
> copying sunpy/physics/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_sunpy/build/sunpy/physics
> copying sunpy/physics/differential_rotation.py -> 
> /<>/.pybuild/cpython3_3.9_sunpy/build/sunpy/physics
> copying sunpy/physics/solar_rotation.py -> 
> /<>/.pybuild/cpython3_3.9_sunpy/build/sunpy/physics
> creating /<>/.pybuild/cpython3_3.9_sunpy/build/sunpy/timeseries
> copying sunpy/timeseries/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_sunpy/build/sunpy/timeseries
> copying sunpy/timeseries/timeseries_factory.py -> 
> /<>/.pybuild/cpython3_3.9_sunpy/build/sunpy/timeseries
> copying sunpy/timeseries/metadata.py -> 
> /<>/.pybuild/cpython3_3.9_sunpy/build/sunpy/timeseries
> copying sunpy/timeseries/timeseriesbase.py -> 
> /<>/.pybuild/cpython3_3.9_sunpy/build/sunpy/timeseries
> creating /<>/.pybuild/cpython3_3.9_sunpy/build/sunpy/util
> copying sunpy/util/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_sunpy/build/sunpy/util
> copying sunpy/util/logger.py -> 
> /<>/.pybuild/cpython3_3.9_sunpy/build/sunpy/util
> copying sunpy/util/util.py -> 
> /<>/.pybuild/cpython3_3.9_sunpy/build/sunpy/util
> copying sunpy/util/parfive_helpers.py -> 
> /<>/.pybuild/cpython3_3.9_sunpy/build/sunpy/util
> copying sunpy/util/exceptions.py -> 
> /<>/.pybuild/cpytho

Bug#1013606: freeart end of life

2022-06-27 Thread Henri Payno



Dear all,

I would like to inform you that the freeart library 
(https://gitlab.esrf.fr/freeart/freeart) has reach end of life. It will 
not be maintained anymore. It should be removed from the debian 
packages.

Bug#1013566: marked as done (node-sockjs: FTBFS: sockjs.coffee:137:9: error: Can't reference 'this' before calling super in derived class constructors)

2022-06-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Jun 2022 07:04:14 +
with message-id 
and subject line Bug#1013566: fixed in node-sockjs 0.3.24+~0.3.33-1
has caused the Debian Bug report #1013566,
regarding node-sockjs: FTBFS: sockjs.coffee:137:9: error: Can't reference 
'this' before calling super in derived class constructors
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.)


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

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> coffee -o lib/ -c src/*.coffee
> /<>/src/sockjs.coffee:137:9: error: Can't reference 'this' 
> before calling super in derived class constructors
> @options =
> ^
> make[2]: *** [Makefile:11: build] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/06/24/node-sockjs_0.3.24-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220624;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220624&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: node-sockjs
Source-Version: 0.3.24+~0.3.33-1
Done: Andrius Merkys 

We believe that the bug you reported is fixed in the latest version of
node-sockjs, 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.
Andrius Merkys  (supplier of updated node-sockjs package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 27 Jun 2022 02:42:16 -0400
Source: node-sockjs
Architecture: source
Version: 0.3.24+~0.3.33-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Andrius Merkys 
Closes: 1013566
Changes:
 node-sockjs (0.3.24+~0.3.33-1) unstable; urgency=medium
 .
   [ Yadd ]
   * Declare compliance with policy 4.6.1
   * Embed typescript declarations and repack
   * Add fix for coffeescript 2 (Closes: #1013566)
Checksums-Sha1:
 d8ae89e8befa9807409bc8b010495012d9282ea9 2475 node-sockjs_0.3.24+~0.3.33-1.dsc
 570d3a0b99ac995360e3136fd6045113b1bd236f 2042 
node-sockjs_0.3.24+~0.3.33.orig-types-sockjs.tar.gz
 9c9752ab373befba84a6d7472b307a6e99a13073 28583 
node-sockjs_0.3.24+~0.3.33.orig.tar.gz
 90c0d5093576c65b28cd6e855ee16a05bde0e759 4116 
node-sockjs_0.3.24+~0.3.33-1.debian.tar.xz
 a6b6a6d56cacb2bb8c9956ae7d04eba9025c1f4c 8754 
node-sockjs_0.3.24+~0.3.33-1_source.buildinfo
Checksums-Sha256:
 bfa4383b5f94090681a87064cdbfc9a4940a7877bf9594bd585f02dc8c37ff4a 2475 
node-sockjs_0.3.24+~0.3.33-1.dsc
 6d04ef3932128dec02c82628164fe4405ceff815135fd118807aa2c5ac4c3448 2042 
node-sockjs_0.3.24+~0.3.33.orig-types-sockjs.tar.gz
 4682448f05f8a9847987b7de2253d08eb33b9986486982a534faeec91b935b9d 28583 
node-sockjs_0.3.24+~0.3.33.orig.tar.gz
 3e8cd4a0fc82702c6c06f92e45b370bc72b131f7169d0a6ba435050eb185171a 4116 
node-sockjs_0.3.24+~0.3.33-1.debian.tar.xz
 e5febe3deee921ac106a2ee1e07aea26ad957f16c4868484445d027bbae2e71a 8754 
node-sockjs_0.3.24+~0.3.33-1_source.buildinfo
Files:
 cbd22e89d5b8fedec2d6c79961776dbd 2475 javascript optional 
node-sockjs_0.3.24+~0.3.33-1.dsc
 d4ff6bee2fddec106cc3e0556af47d3d 2042 javascript optional 
node-sockjs_0.3.24+~0.3.33.orig-types-sockjs.tar.gz
 c1c6536d62aa72109