Bug#1004037: Segmentation fault in plink2 (Was: src:plink2: fails to migrate to testing for too long: autopkgtest regression)

[Andreas Tille]

Hi Chris,

Am Sat, Feb 19, 2022 at 11:37:34PM -0800 schrieb Chris Chang:
> To elaborate: when I look at
> https://salsa.debian.org/med-team/plink2/-/tree/master , I can see that
> plink2.cc, include/plink2_base.h, and include/plink2_base.cc don't have the
> same contents as the v2.00a3-20220218 GitHub tag/release.  So I don't know
> where you grabbed the code from this time, but it does not appear to be
> from GitHub.

That's true since on Github the source code of plink1.9 and plink2 is not
separated.  Thus I download the tarball from

   https://www.cog-genomics.org/plink/2.0/

which points to

   https://www.cog-genomics.org/static/bin/plink2_src_220217.zip

I confirm that the tag on Github says v2.00a3-20220218 which seems to be
later than 220217.  In principle I could point the packaging metadata to
Github and exclude everything that I do not need for plink2 packaging (so
remove 1.9 directory and code copies of libdeflate, simde and zstd in 2.0)

In case you consider this the safer way to download plink2 code I'll do so.

Kind regards and thanks a lot for comparing the code base

 Andreas.

> On Sat, Feb 19, 2022 at 7:54 AM Chris Chang  wrote:
> 
> > If you build off the current head, the version string should say "18 Feb
> > 2022", not "17 Feb 2022".
> >
> > On Sat, Feb 19, 2022 at 7:02 AM Andreas Tille  wrote:
> >
> >> Hi again,
> >>
> >> Am Sat, Feb 19, 2022 at 12:28:21AM -0800 schrieb Chris Chang:
> >> > Ok, new release/tag created.
> >>
> >> I've built the new version now.  The bad news is that it keeps on
> >> SEGFAULTing for me:
> >>
> >> ...
> >> (gdb) run
> >> Starting program: /usr/lib/plink2/plink2-sse3 --debug --pfile tmp_data
> >> --export vcf vcf-dosage=DS --out tmp_data2
> >> [Thread debugging using libthread_db enabled]
> >> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> >> [New Thread 0x74cc7640 (LWP 985019)]
> >> [New Thread 0x744c6640 (LWP 985020)]
> >> [New Thread 0x7fffebcc5640 (LWP 985021)]
> >> PLINK v2.00a3 64-bit (17 Feb 2022)
> >> www.cog-genomics.org/plink/2.0/
> >> (C) 2005-2022 Shaun Purcell, Christopher Chang   GNU General Public
> >> License v3
> >> Logging to tmp_data2.log.
> >> Options in effect:
> >>   --debug
> >>   --export vcf vcf-dosage=DS
> >>   --out tmp_data2
> >>   --pfile tmp_data
> >>
> >> Start time: Sat Feb 19 16:00:00 2022
> >> 31998 MiB RAM detected; reserving 15999 MiB for main workspace.
> >> Using up to 4 compute threads.
> >> [New Thread 0x77fc5640 (LWP 985022)]
> >>
> >> Thread 1 "plink2-sse3" received signal SIGSEGV, Segmentation fault.
> >> plink2::LoadPsam (psamname=psamname@entry=0x7fffbe60
> >> "tmp_data.psam", pheno_range_list_ptr=, fam_cols=...,
> >> pheno_ct_max=,
> >> missing_pheno=, affection_01=0, max_thread_ct=4,
> >> piip=0x7fff8870, sample_include_ptr=0x7fff8790,
> >> founder_info_ptr=0x7fff87a8, sex_nm_ptr=0x7fff8798,
> >> sex_male_ptr=0x7fff87a0, pheno_cols_ptr=0x7fff8770,
> >> pheno_names_ptr=0x7fff8780, raw_sample_ct_ptr=0x7fff8728,
> >> pheno_ct_ptr=0x7fff8720,
> >> max_pheno_name_blen_ptr=0x7fff87b0) at ../plink2_psam.cc:611
> >> 611 pheno_cols[pheno_idx].nonmiss = nullptr;
> >>
> >>
> >> Please let me know if I can do further checks.
> >>
> >> Kind regards
> >>
> >>   Andreas.
> >>
> >> --
> >> http://fam-tille.de
> >>
> >

-- 
http://fam-tille.de

Bug#1004037: Segmentation fault in plink2 (Was: src:plink2: fails to migrate to testing for too long: autopkgtest regression)

[Chris Chang]

To elaborate: when I look at
https://salsa.debian.org/med-team/plink2/-/tree/master , I can see that
plink2.cc, include/plink2_base.h, and include/plink2_base.cc don't have the
same contents as the v2.00a3-20220218 GitHub tag/release.  So I don't know
where you grabbed the code from this time, but it does not appear to be
from GitHub.

On Sat, Feb 19, 2022 at 7:54 AM Chris Chang  wrote:

> If you build off the current head, the version string should say "18 Feb
> 2022", not "17 Feb 2022".
>
> On Sat, Feb 19, 2022 at 7:02 AM Andreas Tille  wrote:
>
>> Hi again,
>>
>> Am Sat, Feb 19, 2022 at 12:28:21AM -0800 schrieb Chris Chang:
>> > Ok, new release/tag created.
>>
>> I've built the new version now.  The bad news is that it keeps on
>> SEGFAULTing for me:
>>
>> ...
>> (gdb) run
>> Starting program: /usr/lib/plink2/plink2-sse3 --debug --pfile tmp_data
>> --export vcf vcf-dosage=DS --out tmp_data2
>> [Thread debugging using libthread_db enabled]
>> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
>> [New Thread 0x74cc7640 (LWP 985019)]
>> [New Thread 0x744c6640 (LWP 985020)]
>> [New Thread 0x7fffebcc5640 (LWP 985021)]
>> PLINK v2.00a3 64-bit (17 Feb 2022)
>> www.cog-genomics.org/plink/2.0/
>> (C) 2005-2022 Shaun Purcell, Christopher Chang   GNU General Public
>> License v3
>> Logging to tmp_data2.log.
>> Options in effect:
>>   --debug
>>   --export vcf vcf-dosage=DS
>>   --out tmp_data2
>>   --pfile tmp_data
>>
>> Start time: Sat Feb 19 16:00:00 2022
>> 31998 MiB RAM detected; reserving 15999 MiB for main workspace.
>> Using up to 4 compute threads.
>> [New Thread 0x77fc5640 (LWP 985022)]
>>
>> Thread 1 "plink2-sse3" received signal SIGSEGV, Segmentation fault.
>> plink2::LoadPsam (psamname=psamname@entry=0x7fffbe60
>> "tmp_data.psam", pheno_range_list_ptr=, fam_cols=...,
>> pheno_ct_max=,
>> missing_pheno=, affection_01=0, max_thread_ct=4,
>> piip=0x7fff8870, sample_include_ptr=0x7fff8790,
>> founder_info_ptr=0x7fff87a8, sex_nm_ptr=0x7fff8798,
>> sex_male_ptr=0x7fff87a0, pheno_cols_ptr=0x7fff8770,
>> pheno_names_ptr=0x7fff8780, raw_sample_ct_ptr=0x7fff8728,
>> pheno_ct_ptr=0x7fff8720,
>> max_pheno_name_blen_ptr=0x7fff87b0) at ../plink2_psam.cc:611
>> 611 pheno_cols[pheno_idx].nonmiss = nullptr;
>>
>>
>> Please let me know if I can do further checks.
>>
>> Kind regards
>>
>>   Andreas.
>>
>> --
>> http://fam-tille.de
>>
>

Bug#1006038: git-remote-hg: FTBFS: dh_auto_test: error: make -j8 test returned exit code 2

[Paul Wise]

Control: forwarded -1 https://github.com/mnauw/git-remote-hg/issues/48

On Sat, 2022-02-19 at 07:31 +0100, Lucas Nussbaum wrote:

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

This appears to be caused by git 1:2.35.1-1 in unstable,
the autopkgtests regressed too with the new git version.

https://tracker.debian.org/pkg/git

I've forwarded this issue upstream for debugging/fixing.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Processed: Re: Bug#1006038: git-remote-hg: FTBFS: dh_auto_test: error: make -j8 test returned exit code 2

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/mnauw/git-remote-hg/issues/48
Bug #1006038 [src:git-remote-hg] git-remote-hg: FTBFS: dh_auto_test: error: 
make -j8 test returned exit code 2
Set Bug forwarded-to-address to 
'https://github.com/mnauw/git-remote-hg/issues/48'.

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

Processed: Re: Bug#1006162: expat: autopkgtest regressions (from CVE-2022-25313 fix)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +confirmed
Bug #1006162 [src:expat] expat: autopkgtest regressions (from CVE-2022-25313 
fix)
Added tag(s) confirmed.

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

Bug#1006162: expat: autopkgtest regressions (from CVE-2022-25313 fix)

[GCS]

Control: tags -1 +confirmed

Hi Salvatore,

On Sun, Feb 20, 2022 at 8:15 AM Salvatore Bonaccorso  wrote:
> There appears to be regressions from the CVE-2022-25313 fix in 2.4.5.
> They are known already upstream, cf.
> https://github.com/NixOS/nixpkgs/pull/160826#issuecomment-1046074523
>
> I will hold of the planned expat security release until this is
> addressed.
 ACK, watching this GitHub issue and will update the package accordingly.

Thanks,
Laszlo/GCS

Processed: affects 1006162, affects 1006162

[Debian Bug Tracking System]

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

> # fix typo
> affects 1006162 - src;python3.9
Bug #1006162 [src:expat] expat: autopkgtest regressions (from CVE-2022-25313 
fix)
Removed indication that 1006162 affects src;python3.9
> affects 1006162 + src:python3.9
Bug #1006162 [src:expat] expat: autopkgtest regressions (from CVE-2022-25313 
fix)
Added indication that 1006162 affects src:python3.9
> thanks
Stopping processing here.

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

Bug#1006162: expat: autopkgtest regressions (from CVE-2022-25313 fix)

[Salvatore Bonaccorso]

Source: expat
Version: 2.4.5-1
Severity: serious
Justification: autopkgtest regression
X-Debbugs-Cc: car...@debian.org
Control: affects -1 
src:libxml-parser-perl,src:python2.7,src:python3.10,src;python3.9

Hi Laszlo,

There appears to be regressions from the CVE-2022-25313 fix in 2.4.5.
They are known already upstream, cf.
https://github.com/NixOS/nixpkgs/pull/160826#issuecomment-1046074523

I will hold of the planned expat security release until this is
addressed.

Regards,
Salvatore

Processed: expat: autopkgtest regressions (from CVE-2022-25313 fix)

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:libxml-parser-perl,src:python2.7,src:python3.10,src;python3.9
Bug #1006162 [src:expat] expat: autopkgtest regressions (from CVE-2022-25313 
fix)
Added indication that 1006162 affects src:libxml-parser-perl, src:python2.7, 
src:python3.10, and src;python3.9

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

Bug#993350: xsane: Scanimage detects scanner but Xsane won't start it

[Hans Georg Colle]

Hi,
after updating libsane1 yesterday xsane works as expected.
Georg

Processed: your mail

[Debian Bug Tracking System]

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

> # https://salsa.debian.org/dpward/sane-backends.git develop
> tags 1005737 + patch
Bug #1005737 [sane-utils] Purging sane-utils deletes the scanner group, created 
by libsane1
Added tag(s) patch.
> tags 1005736 + patch
Bug #1005736 [sane-utils] sane-umax_pp(5) does not describe umax_pp 
command-line utility
Added tag(s) patch.
> tags 1005817 + patch
Bug #1005817 [libsane1] Please recommend sane-airscan
Added tag(s) patch.
> tags 1005091 + patch
Bug #1005091 [sane-utils] Split saned out of sane-utils into a separate package
Added tag(s) patch.
>
End of message, stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> retitle 1005737 Purging sane-utils deletes the scanner group, created by 
> libsane1
Bug #1005737 [sane-utils] Purging package deletes the scanner group, which 
belongs to system
Changed Bug title to 'Purging sane-utils deletes the scanner group, created by 
libsane1' from 'Purging package deletes the scanner group, which belongs to 
system'.
> summary 1005737 15
Summary recorded from message bug 1005737 message 15
> severity 1005737 serious
Bug #1005737 [sane-utils] Purging sane-utils deletes the scanner group, created 
by libsane1
Severity set to 'serious' from 'normal'
> found 1005737 1.0.32-1
Bug #1005737 [sane-utils] Purging sane-utils deletes the scanner group, created 
by libsane1
Marked as found in versions sane-backends/1.0.32-1.
> #
> # Report against current version
> notfound 1005091 1.1.1-1
Bug #1005091 [sane-utils] Split saned out of sane-utils into a separate package
No longer marked as found in versions sane-backends/1.1.1-1.
> found 1005091 1.1.1-2
Bug #1005091 [sane-utils] Split saned out of sane-utils into a separate package
Marked as found in versions sane-backends/1.1.1-2.
>
End of message, stopping processing here.

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

Bug#1005961: marked as done (nq,fq: trying to overwrite '/usr/bin/fq', which is also in package nq 0.3.1-4)

[Debian Bug Tracking System]

Your message dated Sat, 19 Feb 2022 22:48:52 +
with message-id 
and subject line Bug#1005961: fixed in fq 0.0.5-1
has caused the Debian Bug report #1005961,
regarding nq,fq: trying to overwrite '/usr/bin/fq', which is also in package nq 
0.3.1-4
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.)


-- 
1005961: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005961
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nq,fq
Severity: serious
Control: found -1 fq/0.0.4-2
Control: found -1 nq/0.3.1-4

Trying to install fq fails for me as follows:

Preparing to unpack .../archives/fq_0.0.4-2_amd64.deb ...
Unpacking fq (0.0.4-2) ...
dpkg: error processing archive /var/cache/apt/archives/fq_0.0.4-2_amd64.deb 
(--unpack):
 trying to overwrite '/usr/bin/fq', which is also in package nq 0.3.1-4
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/fq_0.0.4-2_amd64.deb

As these two "fq" seem to have completely different purposes, please
either rename one of the commands (or both) or add a Conflicts header to
conflict with the other package.

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

Kernel: Linux 5.16.0-1-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_CPU_OUT_OF_SPEC, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: fq
Source-Version: 0.0.5-1
Done: Daniel Milde 

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

Debian distribution maintenance software
pp.
Daniel Milde  (supplier of updated fq package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 19 Feb 2022 23:12:58 +0100
Source: fq
Architecture: source
Version: 0.0.5-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
Changed-By: Daniel Milde 
Closes: 1005961
Changes:
 fq (0.0.5-1) unstable; urgency=medium
 .
   [ Xentripetal ]
   * initial work for avro OCF files
   * Hook into registry, add codecs
   * Cleanup
   * Change avro codec to funcs
   * Regenerate docs
   * Cleanup for linting
   * Use existing scalar description helper
   * Initial pass on logical types
   * Undo change to doc/file.mp4. I have no idea how
 this got changed in the first place? Maybe some macos shenanigans.
   * cleanup some docs, change enum to mapper, error zigzag on more than 8 bytes
   * Update linting
   * Parse header using avro decoders. Still not certain
 this is the best idea. Will get opinions before finalizing.
   * Add test case with all data types
 .
   [ Mattias Wadman ]
   * goreleaser: Use zip for macos
   * doc: Add macOS security notes and move supported format up a bit
   * id3v2: Should assert not validate magic
   * zip: Assert signature not validate
   * interp: Fix handling of group decode error from stdin
   * pcapng,fuzz: Fix infinite loop by fatal error on block length <= 0
   * mp4,fuzz: Fatal error on infinite sgpd box entries
   * mpeg_spu: Fatal error on infinite loop
   * fuzz: Fuzz all formats
   * interp: Use correct sym color
   * interp: Add grep_by/1 to recursively match using a filter
   * mp3: Decrease max sync seek length between frames to 4k
 .
   [ bump ]
   * Update make-golangci-lint from 1.43.0 to 1.44.0
   * Update github-golangci-lint from 1.43.0 to 1.44.0
 .
   [ Mattias Wadman ]
   * lint: Fix typeassert and case exhaustive warnings
   * github: Add basic issue template
 .
   [ Joel Rangsmo ]
   * Polish of problem template and clarifying questions
   * Remove redudant question and fix typo
 .
   [ Mattias Wadman ]
   * fq: Add arch and os to 

Bug#1006152: mozjs91: FTBFS on i386: test262/built-ins/Date/UTC/fp-evaluation-order.js

[Simon McVittie]

Source: mozjs91
Version: 91.6.0-1
Severity: serious
Tags: ftbfs

After applying patches to fix compilation on i386 and mipsel (see commits
3f0f229d, 585dadd4) there is a test failure unresolved on i386:

## test262/built-ins/Date/UTC/fp-evaluation-order.js: rc = 3, run time = 
0.022397
/home/smcv/mozjs/js/src/tests/test262/shell.js:415:9 uncaught exception: 
Test262Error: order of operations / precision in MakeTime Expected 
SameValue(«29256», «29312») to be true
Stack:
  Test262Error.thrower@/home/smcv/mozjs/js/src/tests/test262/shell.js:415:9
  assert.sameValue@/home/smcv/mozjs/js/src/tests/test262/shell.js:51:9
  
@/home/smcv/mozjs/js/src/tests/test262/built-ins/Date/UTC/fp-evaluation-order.js:19:8
TEST-UNEXPECTED-FAIL | test262/built-ins/Date/UTC/fp-evaluation-order.js | 
(args: "") [0.0 s]

mipsel is still running tests on eller, I'll open a separate bug if
there are unexpected failures.

smcv

Processed: reassign 1006128 to src:meta-kde, tagging 1002658, tagging 1006132

[Debian Bug Tracking System]

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

> reassign 1006128 src:meta-kde 5:111
Bug #1006128 [kde] kde: Keyboard Control key does not work in KDE on Debian 11
Warning: Unknown package 'kde'
Bug reassigned from package 'kde' to 'src:meta-kde'.
Ignoring request to alter found versions of bug #1006128 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1006128 to the same values 
previously set
Bug #1006128 [src:meta-kde] kde: Keyboard Control key does not work in KDE on 
Debian 11
Marked as found in versions meta-kde/5:111.
> tags 1002658 + experimental
Bug #1002658 {Done: Hans van Kranenburg } [src:xen] FTBFS 
with OCaml 4.13.1
Added tag(s) experimental.
> tags 1006132 + sid bookworm
Bug #1006132 [src:ifrench-gut] ifrench-gut: please stop build-depending on 
myspell-tools
Added tag(s) sid and bookworm.
> thanks
Stopping processing here.

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

Processed: Re: playitslowly doesn't start (hasn't for awhile)

[Debian Bug Tracking System]

Processing control commands:

> found -1 1.5.0-1
Bug #1006017 [playitslowly] playitslowly doesn't start (hasn't for awhile)
Marked as found in versions playitslowly/1.5.0-1.

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

Bug#1006017: playitslowly doesn't start (hasn't for awhile)

[Andreas Beckmann]

Followup-For: Bug #1006017
Control: found -1 1.5.0-1

This seems to go back to stretch:

# xvfb-run playitslowly
Traceback (most recent call last):
  File "", line 890, in _find_spec
AttributeError: 'DynamicImporter' object has no attribute 'find_spec'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3.5/runpy.py", line 193, in _run_module_as_main
"__main__", mod_spec)
  File "/usr/lib/python3.5/runpy.py", line 85, in _run_code
exec(code, run_globals)
  File "/usr/lib/python3/dist-packages/playitslowly/app.py", line 36, in 

from gi.repository import Gtk, GObject, Gst, Gio, Gdk
  File "/usr/lib/python3/dist-packages/gi/importer.py", line 127, in find_module
'introspection typelib not found' % namespace)
ImportError: cannot import name Gtk, introspection typelib not found


Andreas

Bug#1006149: linux-image-5.16.0-1-686: Fails to boot on T41 Thinkpads

[Diederik de Haas]

On Saturday, 19 February 2022 22:04:14 CET Petra R.-P. wrote:
> Package: src:linux
> Version: 5.16.7-2
> 
> This new kernel version does not boot on two fairly similar
> old IBM T41 Thinkpads.
> ...
> linux-image-5.15.0-3-686, which I am using to write this
> message, runs fine.
> 
> pn  firmware-iwlwifi  

I see you don't have firmware-iwlwifi installed, but there have been other bug 
reports which could be similar, so with the 5.15 kernel, do you have the 
'iwlwifi' kernel module loaded? If so, could you blacklist that and try to 
reboot into the 5.16 kernel and see whether it then works?

See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005884#17

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

Bug#1002658: marked as done (FTBFS with OCaml 4.13.1)

[Debian Bug Tracking System]

Your message dated Sat, 19 Feb 2022 21:20:52 +
with message-id 
and subject line Bug#1002658: fixed in xen 4.16.0+51-g0941d6cb-1
has caused the Debian Bug report #1002658,
regarding FTBFS with OCaml 4.13.1
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.)


-- 
1002658: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002658
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xen
Version: 4.14.3+32-g9de3671772-1
Severity: important
Tags: ftbfs

Dear Maintainer,

Your package FTBFS with OCaml 4.13.1 with the following error:
> x86_64-linux-gnu-gcc -m64 -DBUILD_ID -fno-strict-aliasing -std=gnu99 -Wall 
> -Wstrict-prototypes -Wdeclaration-after-statement 
> -Wno-unused-but-set-variable -Wno-unused-local-typedefs   -O2 
> -fomit-frame-pointer 
> -D__XEN_INTERFACE_VERSION__=__XEN_LATEST_INTERFACE_VERSION__ -MMD -MP -MF 
> .xentoollog_stubs.o.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE  -g -O2 
> -ffile-prefix-map=/tmp/build/xen-4.14.3+32-g9de3671772=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -fPIC -Werror -I/usr/lib/ocaml 
> -Wno-declaration-after-statement 
> -I/tmp/build/xen-4.14.3+32-g9de3671772/tools/ocaml/libs/xentoollog/../../../../tools/libs/toollog/include
>  
> -I/tmp/build/xen-4.14.3+32-g9de3671772/tools/ocaml/libs/xentoollog/../../../../tools/include
>   -c -o xentoollog_stubs.o xentoollog_stubs.c
> xentoollog_stubs.c:57: error: "Some_val" redefined [-Werror]
>57 | #define Some_val(v) Field(v,0)
>   | 
> In file included from /usr/lib/ocaml/caml/alloc.h:24,
>  from xentoollog_stubs.c:23:
> /usr/lib/ocaml/caml/mlvalues.h:404: note: this is the location of the 
> previous definition
>   404 | #define Some_val(v) Field(v, 0)
>   | 
> cc1: all warnings being treated as errors

Packages rebuilt with OCaml 4.13.1 are available at:

  https://ocaml.debian.net/transitions/ocaml-4.13.1/


Cheers,

-- 
Stéphane

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

Kernel: Linux 5.15.0-2-amd64 (SMP w/4 CPU threads)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: xen
Source-Version: 4.16.0+51-g0941d6cb-1
Done: Hans van Kranenburg 

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

Debian distribution maintenance software
pp.
Hans van Kranenburg  (supplier of updated xen package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 19 Feb 2022 20:29:32 +0100
Source: xen
Architecture: source
Version: 4.16.0+51-g0941d6cb-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Xen Team 
Changed-By: Hans van Kranenburg 
Closes: 976597 988901 992909 1002658
Changes:
 xen (4.16.0+51-g0941d6cb-1) unstable; urgency=medium
 .
   * Update to new upstream version 4.16.0+51-g0941d6cb, which also contains
 security fixes for the following issues:
 - arm: guest_physmap_remove_page not removing the p2m mappings
   XSA-393 CVE-2022-23033
 - A PV guest could DoS Xen while unmapping a grant
   XSA-394 CVE-2022-23034
 - Insufficient cleanup of passed-through device IRQs
   XSA-395 CVE-2022-23035
   * Note that the following XSA are not listed, because...
 - XSA-391 and XSA-392 have patches for the Linux kernel.
   * Upload to unstable now, which obsoletes the Xen 4.14 FTBFS issue.
 (Closes: #1002658)
 .
 xen (4.16.0-1~exp1) experimental; urgency=medium
 .
   Significant changes:
   * Update to new upstream version 4.16.0. This also includes a security fix
 for the following issue, which was not applicable to Xen 4.14 yet:
 - certain VT-d IOMMUs may not work in shared page table mode
   XSA-390 CVE-2021-28710
   * No longer build any package for the i386 architecture. It was 

Bug#995224: [Debian-med-packaging] Bug#995224: relion-cuda: FTBFS with cub 1.14

[Andreas Beckmann]

On 19/02/2022 20.13, Sascha Steinbiss wrote:

79 | #error The version of CUB in your include path is not compatible
with this release of Thrust. CUB is now included in the CUDA Toolkit, so
you no longer need to use your own checkout of CUB. Define
THRUST_IGNORE_CUB_VERSION_CHECK to ignore this.
   |  ^


Currently thrust and cub are out of sync. I got somewhat distracted ... 
trying to add some autopkg tests.
But this bug points out that thrust should have a tighter dependency on 
cub (not only >= upstreamversion , but also << upstreamversion+1).


If you want to blame anything, it's thrust.

Andreas, trying to fix this soon

Bug#1006149: linux-image-5.16.0-1-686: Fails to boot on T41 Thinkpads

[Petra R.-P.]

Package: src:linux
Version: 5.16.7-2
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

This new kernel version does not boot on two fairly similar
old IBM T41 Thinkpads.

What reproducibly happens is as follows:

After the lines

   Loading Linux 5.16.0-1-686 ...
   Loading initial ramdisk ...

the screen gets flushed, and I see:
   
   [  4.xx] ata1.00: Read log 0x00 page 0x00 failed  Emask 0x1
   

The "xx" vary for every try.

Then nothing else happens.
Ctrl-Alt-Del has no effect.
I have to reset the computer by pressing the button.

On an old PC running the same kernel the same message "ata1.00: Read log ..."
appears, but then the boot process continues normally.

linux-image-5.15.0-3-686, which I am using to write this
message, runs fine.


  Thanks for maintaining this package
 and best regards,
   Petra R.-P.


-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation 82855PM Processor to I/O 
Controller [8086:3340] (rev 03)
Subsystem: IBM Thinkpad T40 series [1014:0529]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: agpgart-intel

00:01.0 PCI bridge [0604]: Intel Corporation 82855PM Processor to AGP 
Controller [8086:3341] (rev 03) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- 
Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-

00:1d.0 USB controller [0c03]: Intel Corporation 82801DB/DBL/DBM 
(ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 [8086:24c2] (rev 01) (prog-if 00 
[UHCI])
Subsystem: IBM ThinkPad [1014:052d]
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- 
Kernel driver in use: ehci-pci
Kernel modules: ehci_pci

00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge 
[8086:2448] (rev 81) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- 
Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-

00:1f.0 ISA bridge [0601]: Intel Corporation 82801DBM (ICH4-M) LPC Interface 
Bridge [8086:24cc] (rev 01)
Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- 
Kernel driver in use: snd_intel8x0
Kernel modules: snd_intel8x0

00:1f.6 Modem [0703]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) 
AC'97 Modem Controller [8086:24c6] (rev 01) (prog-if 00 [Generic])
Subsystem: IBM ThinkPad T4x Series [1014:0524]
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: snd_intel8x0m
Kernel modules: snd_intel8x0m

01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] RV200/M7 [Mobility Radeon 7500] [1002:4c57] (prog-if 00 [VGA 
controller])
Subsystem: IBM ThinkPad T4x Series [1014:0530]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping+ SERR+ FastB2B+ DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: radeon
Kernel modules: radeonfb, radeon

02:00.0 CardBus bridge [0607]: Texas Instruments PCI4520 PC card Cardbus 
Controller [104c:ac46] (rev 01)
Subsystem: IBM ThinkPad [1014:0552]
Physical Slot: 1
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- 
SERR- Reset+ 16bInt+ PostWrite+
16-bit legacy interface ports at 0001
Capabilities: 
Kernel driver in use: yenta_cardbus
Kernel modules: yenta_socket

02:00.1 CardBus bridge [0607]: Texas Instruments PCI4520 PC card Cardbus 
Controller [104c:ac46] (rev 01)
Subsystem: IBM ThinkPad [1014:0552]
Physical Slot: 1
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- 
SERR- Reset+ 

Bug#1005419: marked as done (Fails to build with xtables-addons 3.19)

[Debian Bug Tracking System]

Your message dated Sat, 19 Feb 2022 20:51:55 +
with message-id 
and subject line Bug#1005419: fixed in west-chamber 20100405+svn2007.r124-14
has caused the Debian Bug report #1005419,
regarding Fails to build with xtables-addons 3.19
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.)


-- 
1005419: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005419
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: west-chamber-source
Version: 20100405+svn2007.r124-13
Severity: grave
Tags: bookworm sid

west-chamber-source extracts and uses the compat_xtnu.h header from
/usr/src/xtables-addons.tar.bz2.

xtables-addons 3.19 removed this header, so builds now fail.

Ben.

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

Kernel: Linux 5.15.0-3-amd64 (SMP w/2 CPU threads)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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 west-chamber-source depends on:
ii  bzip2  1.0.8-5
ii  debhelper  13.6
pn  libxtables-dev 
ii  make   4.3-4.1
ii  pkg-config 0.29.2-1
pn  xtables-addons-source  

Versions of packages west-chamber-source recommends:
ii  module-assistant  0.11.10

west-chamber-source suggests no packages.
--- End Message ---
--- Begin Message ---
Source: west-chamber
Source-Version: 20100405+svn2007.r124-14
Done: Ying-Chun Liu (PaulLiu) 

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

Debian distribution maintenance software
pp.
Ying-Chun Liu (PaulLiu)  (supplier of updated west-chamber 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 20 Feb 2022 03:12:52 +0800
Source: west-chamber
Architecture: source
Version: 20100405+svn2007.r124-14
Distribution: unstable
Urgency: low
Maintainer: Ying-Chun Liu (PaulLiu) 
Changed-By: Ying-Chun Liu (PaulLiu) 
Closes: 1005419
Changes:
 west-chamber (20100405+svn2007.r124-14) unstable; urgency=low
 .
   * Don't extract obsolete compat_xtnu.h (Closes: #1005419)
 - Thanks to Ben Hutchings 
Checksums-Sha1:
 b48eb9d5e4d4125e7ff53d42407c64569f574cf3 2185 
west-chamber_20100405+svn2007.r124-14.dsc
 5f3a73f4f2ae70951184674b939ac7dd3d2176ad 8504 
west-chamber_20100405+svn2007.r124-14.debian.tar.xz
 369e6e5304773e72ca3f95fc690cab2f99bf5148 6852 
west-chamber_20100405+svn2007.r124-14_source.buildinfo
Checksums-Sha256:
 3a24b1825565c2b98e1631520101540c9e19f39a4f88b407b0249d93904abb2f 2185 
west-chamber_20100405+svn2007.r124-14.dsc
 c8489cea97b9c7c84bce371c5e88b52fa58d0b7b7ff6fdb40bed92a98281ddb6 8504 
west-chamber_20100405+svn2007.r124-14.debian.tar.xz
 58448e82c529d89e1368729d7646fd5dcaf7664ef7737839e1e2f733882a0606 6852 
west-chamber_20100405+svn2007.r124-14_source.buildinfo
Files:
 bd0b52ddde8cdefd7bb1804f89a90531 2185 admin optional 
west-chamber_20100405+svn2007.r124-14.dsc
 c013db49158cac87cfd6e279e83e7fcb 8504 admin optional 
west-chamber_20100405+svn2007.r124-14.debian.tar.xz
 77ca0553cf3b8fa032aaff61ecc7a239 6852 admin optional 
west-chamber_20100405+svn2007.r124-14_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEEo2h49GQQhoFgDLZIRBc/oT0FiIgFAmIRTOUTHHBhdWxsaXVA
ZGViaWFuLm9yZwAKCRBEFz+hPQWIiHHKD/wOGzx45jAbHUIDaC/J2W76K65LkdCU
cewhpS1ELlKiJ3AK7qn9bdnQ4s2r6eeYIo+OKPDqWhTh6eWIPV2pmLbRixEXzbke
IWgYZBWmsIosJWZGk8jtwD71tdeDzg/2tLmzOhovspwuPGOASmrrg//a6qStKDNV
ki9QAg/jH+/oDBApHJ63hW5MmJg/pGKugWUerE1+LgYCyRSlbxulh9tqBd+XyZcR
/TOg5E/BtDFZn2Q3qPCwoWpC6grRYP1PZ2Y2E4mkuhaYQM7CIwPKvw/3e4r+Br2p
7zZrCYcCrCJHkYPTziFn9Dh7XAcABTSDcJrkqX9AOIFC41M7rtScfgoehtczH63y
9r5qTh3AuJ7ze0VMv1n3Efe5MNXTGKVUSni4SZ+5hQw03Cm/nLxUt4F+LBHJOLSd
h5SifWpfxJj5cBZ6LF1lFF6pF40YgeD1Zok75LwsuiXgByTCahYkULTONT6zh7I4

Processed: Re: Bug#1003894: fixed in h2database 2.1.210-1

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 1.4.197-4+deb10u1
Bug #1003894 {Done: Markus Koschany } [src:h2database] 
h2database: CVE-2021-42392
Marked as fixed in versions h2database/1.4.197-4+deb10u1.
> fixed -1 1.4.197-4+deb11u1
Bug #1003894 {Done: Markus Koschany } [src:h2database] 
h2database: CVE-2021-42392
Marked as fixed in versions h2database/1.4.197-4+deb11u1.

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

Bug#1003894: fixed in h2database 2.1.210-1

[Markus Koschany]

Control: fixed -1 1.4.197-4+deb10u1
Control: fixed -1 1.4.197-4+deb11u1


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

Bug#1006144: pychromecast: autopkgtest regression: ModuleNotFoundError: No module named 'requests'

[Paul Gevers]

Source: pychromecast
Version: 9.4.0-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
pychromecast   from testing9.4.0-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. Looks like a 
missing (test) dependency to me.


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

https://ci.debian.net/data/autopkgtest/testing/amd64/p/pychromecast/19345096/log.gz

Testing with python3.10:
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/pychromecast/__init__.py", line 
12, in 

from .config import *  # noqa: F403
  File "/usr/lib/python3/dist-packages/pychromecast/config.py", line 6, 
in 

import requests
ModuleNotFoundError: No module named 'requests'
autopkgtest [19:10:51]: test autodep8-python3



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1006143: kas: autopkgtest regression: ModuleNotFoundError: No module named 'snack'

[Paul Gevers]

Source: kas
Version: 2.6.3-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
kasfrom testing2.6.3-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. Looks like a 
missing (test) dependency to me.


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

https://ci.debian.net/data/autopkgtest/testing/amd64/k/kas/19345088/log.gz

= test session starts 
==

platform linux -- Python 3.9.10, pytest-6.2.5, py-1.10.0, pluggy-0.13.0
rootdir: /tmp/autopkgtest-lxc.q1wq9y5j/downtmp/build.jcd/src
collected 26 items

tests/test_build_system.py . 
 [  3%]
tests/test_commands.py .. 
 [ 11%]
tests/test_environment_variables.py .. 
 [ 19%]
tests/test_includehandler.py  
 [ 65%]
tests/test_layers.py  
 [ 80%]
tests/test_menu.py F 
 [ 84%]
tests/test_patch.py F. 
 [ 92%]
tests/test_refspec.py .. 
 [100%]


=== FAILURES 
===
__ test_menu 
___


monkeypatch = <_pytest.monkeypatch.MonkeyPatch object at 0x7f62f84bd100>
tmpdir = local('/tmp/pytest-of-debci/pytest-0/test_menu0')

def test_menu(monkeypatch, tmpdir):
tdir = str(tmpdir.mkdir('test_menu'))
shutil.rmtree(tdir, ignore_errors=True)
shutil.copytree('tests/test_menu', tdir)
cwd = os.getcwd()
os.chdir(tdir)
>   monkeypatch.setattr('snack.GridFormHelp.runOnce', mock_runOnce)

/tmp/autopkgtest-lxc.q1wq9y5j/downtmp/build.jcd/src/tests/test_menu.py:64: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _ /usr/lib/python3/dist-packages/_pytest/monkeypatch.py:98: in 
derive_importpath

target = resolve(module)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _

name = 'snack.GridFormHelp'

def resolve(name: str) -> object:
# Simplified from zope.dottedname.
parts = name.split(".")
used = parts.pop(0)

  found = __import__(used)

E   ModuleNotFoundError: No module named 'snack'

/usr/lib/python3/dist-packages/_pytest/monkeypatch.py:59: 
ModuleNotFoundError
__ test_patch 
__


changedir = None, tmpdir = 
local('/tmp/pytest-of-debci/pytest-0/test_patch0')


def test_patch(changedir, tmpdir):
tdir = str(tmpdir.mkdir('test_patch'))
shutil.rmtree(tdir, ignore_errors=True)

  shutil.copytree('tests/test_patch', tdir)


/tmp/autopkgtest-lxc.q1wq9y5j/downtmp/build.jcd/src/tests/test_patch.py:32: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _

src = 'tests/test_patch'
dst = '/tmp/pytest-of-debci/pytest-0/test_patch0/test_patch', symlinks = 
False

ignore = None, copy_function = 
ignore_dangling_symlinks = False, dirs_exist_ok = False

def copytree(src, dst, symlinks=False, ignore=None, 
copy_function=copy2,

 ignore_dangling_symlinks=False, dirs_exist_ok=False):
"""Recursively copy a directory tree and return the destination 
directory.
dirs_exist_ok dictates whether to raise an exception in 
case dst or any

missing parent directory already exists.
If exception(s) occur, an Error is raised with a list of 
reasons.

If the optional symlinks flag is true, symbolic links in the
source tree result in symbolic links in the destination tree; if
it is false, the contents of the files pointed to by symbolic
links are copied. If the file pointed by the symlink doesn't
exist, an exception will be added in the list of errors raised in
an Error exception at the end of the copy process.
You can set the optional ignore_dangling_symlinks flag to 
true if you

want to silence this exception. Notice that this has no effect on
platforms that don't support os.symlink.
The optional ignore argument is a callable. If given, it
is called with the `src` parameter, which is the directory
being visited by copytree(), and `names` which is the list of
`src` contents, as returned by os.listdir():
callable(src, names) -> ignored_names
Since copytree() 

Bug#995224: [Debian-med-packaging] Bug#995224: relion-cuda: FTBFS with cub 1.14

[Sascha Steinbiss]

Hi all,

greetings from the Debian Med Sprint 2021!

[...]
> /usr/bin/nvcc -M -D__CUDACC__ 
> /build/relion-cuda-3.1.0/src/acc/cuda/cuda_projector_plan.cu -o 
> /build/relion-cuda-3.1.0/build/src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/relion_gpu_util_generated_cuda_projector_plan.cu.o.NVCC-depend
>  -ccbin /usr/bin/cc -m64 -DINSTALL_LIBRARY_DIR=/usr/lib/ 
> -DSOURCE_DIR=/build/relion-cuda-3.1.0/src/ -DACC_CUDA=2 -DACC_CPU=1 -DCUDA 
> -DALLOW_CTF_IN_SGD -DHAVE_SINCOS -DHAVE_TIFF -Xcompiler 
> ,\"-g\",\"-O2\",\"-ffile-prefix-map=/build/relion-cuda-3.1.0=.\",\"-fstack-protector-strong\",\"-Wformat\",\"-Werror=format-security\",\"-O3\",\"-DNDEBUG\"
>  -arch=sm_35 -D__INTEL_COMPILER --default-stream per-thread 
> --disable-warnings -DNVCC -I/usr/include 
> -I/usr/lib/x86_64-linux-gnu/openmpi/include 
> -I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi 
> -I/build/relion-cuda-3.1.0 -I/usr/lib/fltk -I/usr/include/x86_64-linux-gnu
> nvcc warning : The 'compute_35', 'compute_37', 'compute_50', 'sm_35', 'sm_37' 
> and 'sm_50' architectures are deprecated, and may be removed in a future 
> release (Use -Wno-deprecated-gpu-targets to suppress warning).
> In file included from /usr/include/thrust/system/cuda/config.h:33,
>  from 
> /usr/include/thrust/system/cuda/detail/execution_policy.h:35,
>  from 
> /usr/include/thrust/iterator/detail/device_system_tag.h:23,
>  from 
> /usr/include/thrust/iterator/detail/iterator_facade_category.h:22,
>  from /usr/include/thrust/iterator/iterator_facade.h:37,
>  from 
> /build/relion-cuda-3.1.0/src/acc/cuda/cub/device/../iterator/arg_index_input_iterator.cuh:48,
>  from 
> /build/relion-cuda-3.1.0/src/acc/cuda/cub/device/device_reduce.cuh:41,
>  from 
> /build/relion-cuda-3.1.0/src/acc/cuda/cuda_utils_cub.cuh:16,
>  from 
> /build/relion-cuda-3.1.0/src/acc/cuda/cuda_projector_plan.cu:10:
> /usr/include/cub/util_namespace.cuh:46:2: error: #error CUB requires a 
> definition of CUB_NS_QUALIFIER when CUB_NS_PREFIX/POSTFIX are defined.
>46 | #error CUB requires a definition of CUB_NS_QUALIFIER when 
> CUB_NS_PREFIX/POSTFIX are defined.
>   |  ^
> CMake Error at 
> relion_gpu_util_generated_cuda_projector_plan.cu.o.Release.cmake:220 
> (message):
>   Error generating
>   
> /build/relion-cuda-3.1.0/build/src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/./relion_gpu_util_generated_cuda_projector_plan.cu.o
> 
> 
> make[4]: *** [src/apps/CMakeFiles/relion_gpu_util.dir/build.make:1439: 
> src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/relion_gpu_util_generated_cuda_projector_plan.cu.o]
>  Error 1
> make[4]: Leaving directory '/build/relion-cuda-3.1.0/build'
> 
> 
> This seems to be the Breaking Change described in
> https://github.com/NVIDIA/cub/releases/tag/1.14.0:
> 
> #350: When the CUB_NS_[PRE|POST]FIX macros are set, CUB_NS_QUALIFIER
> must also be defined to the fully qualified CUB namespace (e.g.
> #define CUB_NS_QUALIFIER ::foo::cub). Note that this is handled
> automatically when using the new [THRUST_]CUB_WRAPPED_NAMESPACE mechanism.

I updated the relion code to the latest upstream version (3.1.3) and
tried to rebuild in the hope that it changed something: it did, now I get:

[...]
/usr/bin/nvcc -M -D__CUDACC__
/build/relion-cuda-3.1.3/src/acc/cuda/cuda_projector_plan.cu -o
/build/relion-cuda-3.1.3/build/src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/relion_gpu_util_generated_cuda_projector_plan.cu.o.NVCC-depend
-ccbin /usr/bin/cc -m64 -DINSTALL_LIBRARY_DIR=/usr/lib/
-DSOURCE_DIR=/build/relion-cuda-3.1.3/src/ -DACC_CUDA=2 -DACC_CPU=1
-DCUDA -DALLOW_CTF_IN_SGD -DHAVE_SINCOS -DHAVE_TIFF -Xcompiler
,\"-g\",\"-O2\",\"-ffile-prefix-map=/build/relion-cuda-3.1.3=.\",\"-fstack-protector-strong\",\"-Wformat\",\"-Werror=format-security\",\"-O3\",\"-DNDEBUG\"
-arch=sm_35 -D__INTEL_COMPILER --default-stream per-thread
--disable-warnings -DNVCC -I/usr/include
-I/usr/lib/x86_64-linux-gnu/openmpi/include
-I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi
-I/build/relion-cuda-3.1.3 -I/usr/lib/fltk -I/usr/include/x86_64-linux-gnu
nvcc warning : The 'compute_35', 'compute_37', 'compute_50', 'sm_35',
'sm_37' and 'sm_50' architectures are deprecated, and may be removed in
a future release (Use -Wno-deprecated-gpu-targets to suppress warning).
In file included from
/usr/include/thrust/system/cuda/detail/execution_policy.h:35,
 from
/usr/include/thrust/iterator/detail/device_system_tag.h:23,
 from
/usr/include/thrust/iterator/detail/iterator_facade_category.h:22,
 from /usr/include/thrust/iterator/iterator_facade.h:37,
 from
/build/relion-cuda-3.1.3/src/acc/cuda/cub/device/../iterator/arg_index_input_iterator.cuh:48,
 from
/build/relion-cuda-3.1.3/src/acc/cuda/cub/device/device_reduce.cuh:41,
 from

Processed: Add additional command line options

[Debian Bug Tracking System]

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

> retitle 1005993 Add additional command line options
Bug #1005993 [diodon] diodon: The man page is entirely useless, violating 
section 12.1 of policy
Changed Bug title to 'Add additional command line options' from 'diodon: The 
man page is entirely useless, violating section 12.1 of policy'.
> severity 1005993 wishlist
Bug #1005993 [diodon] Add additional command line options
Severity set to 'wishlist' from 'serious'
>
End of message, stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> severity 1005479 normal
Bug #1005479 [src:toil] toil: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p "3.10 3.9" returned exit code 13
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Processed: ruby3.0

[Debian Bug Tracking System]

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

> block 1004915 by 1005947
Bug #1004915 [release.debian.org] transition: ruby2.7-rm
1004915 was blocked by: 1001217
1004915 was blocking: 1006119
Added blocking bug(s) of 1004915: 1005947
> thanks
Stopping processing here.

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

Processed: ruby3.0

[Debian Bug Tracking System]

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

> block 1004915 by 1001217
Bug #1004915 [release.debian.org] transition: ruby2.7-rm
1004915 was not blocked by any bugs.
1004915 was blocking: 1006119
Added blocking bug(s) of 1004915: 1001217
> thanks
Stopping processing here.

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

Bug#1006141: supertuxkart: FTBFS on armhf: Error: selected FPU does not support instruction -- `vldmia.64 r10,{d0-d7}'

[Sebastian Ramacher]

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

supertuxkart FTBFS on armhf:

[ 26%] Building ASM object 
lib/angelscript/projects/cmake/CMakeFiles/angelscript.dir/__/__/source/as_callfunc_arm_gcc.S.o
cd /<>/obj-arm-linux-gnueabihf/lib/angelscript/projects/cmake && 
/usr/bin/cc -DANGELSCRIPT_EXPORT -DENABLE_IPV6 -DNO_IRR_COMPILE_WITH_OPENGL_ 
-DSUPERTUXKART_VERSION=\"1.3\" -DUSE_GLES2 -D_IRR_COMPILE_WITH_OGLES2_ -D_LIB 
-I/<>/lib/wiiuse/src -I/<>/lib/irrlicht/include 
-I/<>/lib/tinygettext/include 
-I/<>/lib/graphics_utils 
-I/<>/lib/graphics_engine/include 
-I/<>/lib/enet/include -I/<>/lib/bullet/src 
-I/usr/include -I/usr/include/SDL2 -I/<>/src 
-I/<>/lib/angelscript/projects/cmake/../../include   
-Wa,-mimplicit-it=always -o 
CMakeFiles/angelscript.dir/__/__/source/as_callfunc_arm_gcc.S.o -c 
/<>/lib/angelscript/source/as_callfunc_arm_gcc.S
/<>/lib/angelscript/source/as_callfunc_arm_gcc.S: Assembler 
messages:
/<>/lib/angelscript/source/as_callfunc_arm_gcc.S:328: Error: 
selected FPU does not support instruction -- `vldmia.64 r10,{d0-d7}'
/<>/lib/angelscript/source/as_callfunc_arm_gcc.S:377: Error: 
selected FPU does not support instruction -- `vstmia.64 r10,{d0-d7}'
/<>/lib/angelscript/source/as_callfunc_arm_gcc.S:403: Error: 
selected FPU does not support instruction -- `vldmia.64 r10,{d0-d7}'
/<>/lib/angelscript/source/as_callfunc_arm_gcc.S:464: Error: 
selected FPU does not support instruction -- `vstmia.64 r10,{d0-d7}'
/<>/lib/angelscript/source/as_callfunc_arm_gcc.S:493: Error: 
selected FPU does not support instruction -- `vldmia.64 r10,{d0-d7}'
/<>/lib/angelscript/source/as_callfunc_arm_gcc.S:558: Error: 
selected FPU does not support instruction -- `vstmia.64 r10,{d0-d7}'
/<>/lib/angelscript/source/as_callfunc_arm_gcc.S:583: Error: 
selected FPU does not support instruction -- `vldmia.64 r10,{d0-d7}'
/<>/lib/angelscript/source/as_callfunc_arm_gcc.S:634: Error: 
selected FPU does not support instruction -- `vstmia.64 r10,{d0-d7}'
/<>/lib/angelscript/source/as_callfunc_arm_gcc.S:661: Error: 
selected FPU does not support instruction -- `vldmia.64 r10,{d0-d7}'
/<>/lib/angelscript/source/as_callfunc_arm_gcc.S:714: Error: 
selected FPU does not support instruction -- `vstmia.64 r10,{d0-d7}'
make[3]: *** 
[lib/angelscript/projects/cmake/CMakeFiles/angelscript.dir/build.make:554: 
lib/angelscript/projects/cmake/CMakeFiles/angelscript.dir/__/__/source/as_callfunc_arm_gcc.S.o]
 Error 1
make[3]: *** Waiting for unfinished jobs

See
https://buildd.debian.org/status/fetch.php?pkg=supertuxkart=armhf=1.3%2Bdfsg1-2%2Bb1=1645095866=0

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#1005890: marked as done (gsocket: flaky autopkgtest)

[Debian Bug Tracking System]

Your message dated Sat, 19 Feb 2022 17:33:46 +
with message-id 
and subject line Bug#1005890: fixed in gsocket 1.4.33-2
has caused the Debian Bug report #1005890,
regarding gsocket: flaky autopkgtest
to be marked as done.

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

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


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

Source: gsocket
Version: 1.4.33-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of you package on armhf 
because it was showing up as a regression for the upload of glibc. I 
noticed that the test regularly fails on all architectures.


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.

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

Paul

https://ci.debian.net/data/autopkgtest/testing/armhf/g/gsocket/19250005/log.gz

autopkgtest [07:10:23]: test upstream-tests: [---
Running: netcat #6.1 (stdin, 
1MB).[FAILED]-1

autopkgtest [07:10:25]: test upstream-tests: ---]


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: gsocket
Source-Version: 1.4.33-2
Done: Daniel Echeverri 

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

Debian distribution maintenance software
pp.
Daniel Echeverri  (supplier of updated gsocket package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 19 Feb 2022 11:18:52 -0500
Source: gsocket
Architecture: source
Version: 1.4.33-2
Distribution: unstable
Urgency: medium
Maintainer: Daniel Echeverri 
Changed-By: Daniel Echeverri 
Closes: 1005890
Changes:
 gsocket (1.4.33-2) unstable; urgency=medium
 .
   * Mark test 6.1 as flaky test. (Closes: #1005890)
   * Fix typo in d/upstream/metadata file.
Checksums-Sha1:
 9d3900ea224c6d82a3914710c73205eb80aff8f4 1989 gsocket_1.4.33-2.dsc
 cd1b5fe9255dbc3b9e27a6a455d5cfd6a35569d9 4004 gsocket_1.4.33-2.debian.tar.xz
 f29ff877b07fc31b250c02d63af3b1e6972fe332 6153 gsocket_1.4.33-2_amd64.buildinfo
Checksums-Sha256:
 cf3d01a04e03833cd6949975b5eaa41afb0aa1a7e9a19c2690f66ac7065c87cc 1989 
gsocket_1.4.33-2.dsc
 681d85e008f319ed755aa77d9f786f7e08182f5cdbabda4e202ff1d5e11d15f3 4004 
gsocket_1.4.33-2.debian.tar.xz
 4a7a1b4fdc9739b6eec8d854a515536dc97d7fa028e8a00753207528784cef5d 6153 
gsocket_1.4.33-2_amd64.buildinfo
Files:
 d971a0b41e5f7ec0c0bd6044203e267f 1989 net optional gsocket_1.4.33-2.dsc
 5d934db4a6314405313ddb7bd2db235a 4004 net optional 
gsocket_1.4.33-2.debian.tar.xz
 7c5f8cd41cadcaba2ddcd2f54a2cdf52 6153 net optional 
gsocket_1.4.33-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEE0NCFsWnDv9lASFj6IfwpUEtSMNsFAmIRJ4UTHGVwc2lsb25A
ZGViaWFuLm9yZwAKCRAh/ClQS1Iw2zifEACKl0n5ogrc6KkIkz5ZQGnbwOobcOu/
LOD5nCmB2rKnjfK+CmUVqnIpu7DtuFEc7utcBdEg0zm64lQ629f5CVx6UFMxYC4p
40DxEa6xWoTgEwWNZ4KLXp4xzLDIdDk/s///qPVx6Hp8a0KRQUZAVcx3tYqRw+Fk
cSTNxWLcfDjs6nmfSriaJhBjVLfjB/SueRTqLlZfMehYaF18jTNJy5Hi2nzcEA9+
nwlyRcYo64nCK0KdQaog3mG+LCRH1/5EP/nic+2W13qEWvWEM8H71X0SLIrFYKyi
BEqEENCv5UJ3vlDhI8ikZMoP+aLhYrXBOx+moCVRKhZ+/n+r79tA7pBeEBYtM34U
QCHIR6yZ1X2pVOQ/3Ax7iycizIeuYLdNQKv2g52Fd9TCcFM9MXqrpeGJFTulm52o
LCFtqoRFrFYLDi0AcGpFVIjpuL9iRattTRy3rOm3Tzh77ocfks7qlEY+EfPj+VRy
yJf+PMtENmNaGN1kpyUUIhQZDbAUdh+sokx1Q9N4d0vEi0huGn9yF18gvn87J1uR
zGn+ScApuEmGMBkp54R6iCh7BgcrVTQKA+5oSAXygfIa0LBz10HGIyvHAVfhUqQE
o7P2f6eIeL28YNbtgCtofskdoygSt/WbuU1xfrKoB9EdFlaDcJw0yS8Avi2ILBNx
B1r3WBfWJVa5qw==
=b9HI
-END PGP SIGNATURE End Message ---

Bug#287371: [xml/sgml-pkgs] Bug#287371: xsltproc: Probable memory leak (when using document()?)

[Vincent Lefevre]

On 2022-02-19 18:01:52 +0100, Mattia Rizzolo wrote:
> On Thu, Feb 10, 2022 at 01:08:33PM +0100, Vincent Lefevre wrote:
> > This is no different than CVE-2013-0338 and CVE-2013-0339[*]. The
> > point is that from a small document, one can exhaust the memory
> > of the machine. CVE-2013-0338 and CVE-2013-0339 are about entity
> > expansion, but there are the same consequences with just loading
> > data in memory.
> > 
> > [*] https://www.openwall.com/lists/oss-security/2013/02/22/3
> 
> If you believe so, and you confirmed that it hasn't been fixed in the
> past 15 years, could you please either (or both):
>  * report it to mitre's CVE form
>  * report it in https://gitlab.gnome.org/GNOME/libxml2/-/issues
> ?

I'll test again (I've been using a fake DTD for the past 15 years).

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

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

[Debian Bug Tracking System]

Your message dated Sat, 19 Feb 2022 17:05:05 +
with message-id 
and subject line Bug#1006041: fixed in pymarkups 3.1.3-2
has caused the Debian Bug report #1006041,
regarding pymarkups: FTBFS: dh_auto_test: error: pybuild --test -i 
python{version} -p "3.10 3.9" 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.)


-- 
1006041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006041
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pymarkups
Version: 3.1.3-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

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:237: python3.10 setup.py config 
> running config
> I: pybuild base:237: python3.9 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:237: /usr/bin/python3.10 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.10_markups/build/markups
> copying markups/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_markups/build/markups
> copying markups/markdown.py -> 
> /<>/.pybuild/cpython3_3.10_markups/build/markups
> copying markups/textile.py -> 
> /<>/.pybuild/cpython3_3.10_markups/build/markups
> copying markups/restructuredtext.py -> 
> /<>/.pybuild/cpython3_3.10_markups/build/markups
> copying markups/abstract.py -> 
> /<>/.pybuild/cpython3_3.10_markups/build/markups
> copying markups/common.py -> 
> /<>/.pybuild/cpython3_3.10_markups/build/markups
> I: pybuild base:237: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9_markups/build/markups
> copying markups/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_markups/build/markups
> copying markups/markdown.py -> 
> /<>/.pybuild/cpython3_3.9_markups/build/markups
> copying markups/textile.py -> 
> /<>/.pybuild/cpython3_3.9_markups/build/markups
> copying markups/restructuredtext.py -> 
> /<>/.pybuild/cpython3_3.9_markups/build/markups
> copying markups/abstract.py -> 
> /<>/.pybuild/cpython3_3.9_markups/build/markups
> copying markups/common.py -> 
> /<>/.pybuild/cpython3_3.9_markups/build/markups
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:237: cd 
> /<>/.pybuild/cpython3_3.10_markups/build; python3.10 -m unittest 
> discover -v 
> test_codehilite (tests.test_markdown.MarkdownTest) ... ok
> test_codehilite_custom_class (tests.test_markdown.MarkdownTest) ... ok
> test_default_math (tests.test_markdown.MarkdownTest) ... ok
> test_document_extensions_change (tests.test_markdown.MarkdownTest)
> Extensions from document should be replaced on each run, not added. ... ok
> test_document_extensions_parameters (tests.test_markdown.MarkdownTest) ... ok
> test_empty_file (tests.test_markdown.MarkdownTest) ... ok
> test_extensions_loading (tests.test_markdown.MarkdownTest) ... ok
> test_extensions_parameters (tests.test_markdown.MarkdownTest) ... ok
> test_extensions_txt_file (tests.test_markdown.MarkdownTest) ... ok
> test_extensions_yaml_file (tests.test_markdown.MarkdownTest) ... ok
> test_extensions_yaml_file_invalid (tests.test_markdown.MarkdownTest) ... ok
> test_extra (tests.test_markdown.MarkdownTest) ... ok
> test_loading_extensions_by_module_name (tests.test_markdown.MarkdownTest) ... 
> ok
> test_mathjax (tests.test_markdown.MarkdownTest) ... ok
> test_mathjax_asciimath (tests.test_markdown.MarkdownTest) ... ok
> test_mathjax_document_extension (tests.test_markdown.MarkdownTest) ... ok
> test_mathjax_multilevel (tests.test_markdown.MarkdownTest) ... ok
> test_mathjax_multiline (tests.test_markdown.MarkdownTest) ... ok
> test_meta (tests.test_markdown.MarkdownTest) ... ok
> test_not_loading_sys (tests.test_markdown.MarkdownTest) ... ok
> test_pymdownx_highlight (tests.test_markdown.MarkdownTest) ... skipped 
> 'pymdownx module is not available'
> test_pymdownx_highlight_custom_class (tests.test_markdown.MarkdownTest) ... 
> skipped 'pymdownx module is not available'
> test_remove_extra (tests.test_markdown.MarkdownTest) ... ok
> test_remove_extra_document_extension (tests.test_markdown.MarkdownTest) ... ok
> test_remove_extra_double (tests.test_markdown.MarkdownTest)
> Removing extra twice should not cause a crash. ... ok
> test_remove_extra_removes_mathjax (tests.test_markdown.MarkdownTest) ... ok
> 

Bug#1005787: marked as done (redis: CVE-2022-0543)

[Debian Bug Tracking System]

Your message dated Sat, 19 Feb 2022 17:02:39 +
with message-id 
and subject line Bug#1005787: fixed in redis 5:5.0.14-1+deb10u2
has caused the Debian Bug report #1005787,
regarding redis: CVE-2022-0543
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.)


-- 
1005787: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005787
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: redis
Version: 5:5.0.14-1+deb10u1
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

A vulnerability was published for redis as CVE-2022-0543[0]. This is
the placeholder Debian bug which will be renamed and fleshed out later
with more details once it has become unembargoed.

[0] https://security-tracker.debian.org/tracker/CVE-2022-0543
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0543


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: redis
Source-Version: 5:5.0.14-1+deb10u2
Done: Chris Lamb 

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

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated redis 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, 14 Feb 2022 14:40:49 -0800
Source: redis
Binary: redis redis-sentinel redis-server redis-tools redis-tools-dbgsym
Built-For-Profiles: nocheck
Architecture: source amd64 all
Version: 5:5.0.14-1+deb10u2
Distribution: buster-security
Urgency: high
Maintainer: Chris Lamb 
Changed-By: Chris Lamb 
Description:
 redis  - Persistent key-value database with network interface (metapackage
 redis-sentinel - Persistent key-value database with network interface 
(monitoring)
 redis-server - Persistent key-value database with network interface
 redis-tools - Persistent key-value database with network interface (client)
Closes: 1005787
Changes:
 redis (5:5.0.14-1+deb10u2) buster-security; urgency=high
 .
   * CVE-2022-0543: Prevent a Debian-specific Lua sandbox escape vulnerability.
 .
 This vulnerability existed because the Lua library in Debian is provided as
 a dynamic library. A "package" variable was automatically populated that
 in turn permitted access to arbitrary Lua functionality. As this extended
 to, for example, the "execute" function from the "os" module, an attacker
 with the ability to execute arbitrary Lua code could potentially execute
 arbitrary shell commands.
 .
 Thanks to Reginaldo Silva  for discovering and
 reporting this issue. (Closes: #1005787)
Checksums-Sha1:
 c7323594890807164422503c38c4d687e9e8e14f 2190 redis_5.0.14-1+deb10u2.dsc
 d383cc7958c7ea89006509e4793c76eaa591cd20 2017965 redis_5.0.14.orig.tar.gz
 f0606f84773a5dd31b43348a4ccc5b3cebd3e1c8 27040 
redis_5.0.14-1+deb10u2.debian.tar.xz
 95bc17791025dba181ad800d6c60823fb4f8f94f 63564 
redis-sentinel_5.0.14-1+deb10u2_amd64.deb
 fdce48049810468f5b0ab7db3c59097f5381b12a 90812 
redis-server_5.0.14-1+deb10u2_amd64.deb
 d3b4e1d5e72406ef7cfb2b9f9f505ba552882cc3 1254712 
redis-tools-dbgsym_5.0.14-1+deb10u2_amd64.deb
 272d111201ab937b40db64a5c8970390370a3f2b 540648 
redis-tools_5.0.14-1+deb10u2_amd64.deb
 9800667dd5f599f3f6ceac4edac179d1dcde7283 56136 redis_5.0.14-1+deb10u2_all.deb
 ba87f9c796cd875424b3417f534a0532f1242636 7061 
redis_5.0.14-1+deb10u2_amd64.buildinfo
Checksums-Sha256:
 b4f65b96b89f980077d7e042477c97421133bf19b77ebbfb0560db83ac13d70c 2190 
redis_5.0.14-1+deb10u2.dsc
 6d8e87baeaae521a4ad2d9b5e2af78f582a4212a370c4a8e7e1c58dbbd9a0f19 2017965 
redis_5.0.14.orig.tar.gz
 cae16a8e87c1f45eaa14b62cd5a46cf753e4ac688322cf300e49e350aebf5994 27040 
redis_5.0.14-1+deb10u2.debian.tar.xz
 86946a3aa9cc0efc1400e2f767d13bb527b4991d9ad67d4ea46e2d2ed1f56412 63564 
redis-sentinel_5.0.14-1+deb10u2_amd64.deb
 f3ca8e21d179771309e04ba74bd4d7fe10006d48f0a381d41d0e961b7f7e5afc 90812 
redis-server_5.0.14-1+deb10u2_amd64.deb
 5d7214ccb0be09a5bf7204a1ef56fe1c84ed07b004ebf3649934f35e828e2767 1254712 

Bug#1005787: marked as done (redis: CVE-2022-0543)

[Debian Bug Tracking System]

Your message dated Sat, 19 Feb 2022 17:02:12 +
with message-id 
and subject line Bug#1005787: fixed in redis 5:6.0.16-1+deb11u2
has caused the Debian Bug report #1005787,
regarding redis: CVE-2022-0543
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.)


-- 
1005787: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005787
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: redis
Version: 5:5.0.14-1+deb10u1
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

A vulnerability was published for redis as CVE-2022-0543[0]. This is
the placeholder Debian bug which will be renamed and fleshed out later
with more details once it has become unembargoed.

[0] https://security-tracker.debian.org/tracker/CVE-2022-0543
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0543


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: redis
Source-Version: 5:6.0.16-1+deb11u2
Done: Chris Lamb 

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

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated redis 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, 14 Feb 2022 14:45:00 -0800
Source: redis
Binary: redis redis-sentinel redis-server redis-tools redis-tools-dbgsym
Built-For-Profiles: nocheck
Architecture: source amd64 all
Version: 5:6.0.16-1+deb11u2
Distribution: bullseye-security
Urgency: high
Maintainer: Chris Lamb 
Changed-By: Chris Lamb 
Description:
 redis  - Persistent key-value database with network interface (metapackage
 redis-sentinel - Persistent key-value database with network interface 
(monitoring)
 redis-server - Persistent key-value database with network interface
 redis-tools - Persistent key-value database with network interface (client)
Closes: 1005787
Changes:
 redis (5:6.0.16-1+deb11u2) bullseye-security; urgency=high
 .
   * CVE-2022-0543: Prevent a Debian-specific Lua sandbox escape vulnerability.
 .
 This vulnerability existed because the Lua library in Debian is provided as
 a dynamic library. A "package" variable was automatically populated that
 in turn permitted access to arbitrary Lua functionality. As this extended
 to, for example, the "execute" function from the "os" module, an attacker
 with the ability to execute arbitrary Lua code could potentially execute
 arbitrary shell commands.
 .
 Thanks to Reginaldo Silva  for discovering and
 reporting this issue. (Closes: #1005787)
Checksums-Sha1:
 73a12dedee6e1510def455590526af17ccf56a24 2296 redis_6.0.16-1+deb11u2.dsc
 cd9e181eef1125b7c7eb9cd1198791ac0a9f24ae 29764 
redis_6.0.16-1+deb11u2.debian.tar.xz
 b750091b586a44eb6a208b5b0fd772943c0e323b 64540 
redis-sentinel_6.0.16-1+deb11u2_amd64.deb
 8e424ccd6768ead6b953c3b0438dc75fbf5ac1e4 98212 
redis-server_6.0.16-1+deb11u2_amd64.deb
 752ff3b7355ae569dd88e990c6ef5fb67abd7bf0 1760540 
redis-tools-dbgsym_6.0.16-1+deb11u2_amd64.deb
 52750a0022140b2d0f051cce4df742727411f759 741308 
redis-tools_6.0.16-1+deb11u2_amd64.deb
 d9921bfcfa27a7825ffed9b112b10b8e49063180 56796 redis_6.0.16-1+deb11u2_all.deb
 c271c00ede79a4f5a45983efe0350d1efe7ccd1f 7482 
redis_6.0.16-1+deb11u2_amd64.buildinfo
Checksums-Sha256:
 fbce4f2cb4b5c7d1e4371b74dfd54066de592080f398be148c274c7b116060fc 2296 
redis_6.0.16-1+deb11u2.dsc
 11dd7e429818fa7a4595849bc3223f4a23055d4e83b474e54102e5eeb922ad0d 29764 
redis_6.0.16-1+deb11u2.debian.tar.xz
 cec84029bd00b54bb7ee425c1561336141bfcdc626e87a32001e84e93510a923 64540 
redis-sentinel_6.0.16-1+deb11u2_amd64.deb
 d7d3d93e00d414982eef09b57de3ad39db5ab61c16aef58241dedb75db0105fc 98212 
redis-server_6.0.16-1+deb11u2_amd64.deb
 e3198c1a058b1dc0f795ff81f1b6346d39edbafa736e0ed36653c4f2546e1d38 1760540 
redis-tools-dbgsym_6.0.16-1+deb11u2_amd64.deb
 0329056b6cf1cc65ec1069a66bb0825ddb8307d1c6c5c93ab022fb19187138fd 741308 
redis-tools_6.0.16-1+deb11u2_amd64.deb
 

Bug#1005230: marked as done (chromium: essential dependencies (libgtk-3-0) no longer depended on)

[Debian Bug Tracking System]

Your message dated Sat, 19 Feb 2022 17:02:07 +
with message-id 
and subject line Bug#1005230: fixed in chromium 98.0.4758.102-1~deb11u1
has caused the Debian Bug report #1005230,
regarding chromium: essential dependencies (libgtk-3-0) no longer depended on
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.)


-- 
1005230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005230
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chromium
Version: 98.0.4758.80-1~deb11u1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: t...@security.debian.org

Hi,
  Jumping from chromium 90 to 98 causes many dependencies to be
uninstalled.  After this chromium fails to start with
"trace/breakpoint trap".
  stracing shows chromium looking for - but not finding -
 gtk related packages.
  Manually reinstalling those dependencies declared by chromium 90
allows 98 to start again.
  I think libgtk-3-0 is one of those essential missing dependencies.
There may be others.
  I'm running sway, which might explain why those dependencies are
not pulled in by other packages.

Thanks for your work!
C.

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

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

Versions of packages chromium depends on:
ii  chromium-common 98.0.4758.80-1~deb11u1
ii  libasound2  1.2.4-1.1
ii  libatk-bridge2.0-0  2.38.0-1
ii  libatk1.0-0 2.36.0-2
ii  libatomic1  10.2.1-6
ii  libatspi2.0-0   2.38.0-4
ii  libc6   2.31-13+deb11u2
ii  libcairo2   1.16.0-5
ii  libcups22.3.3op2-3+deb11u1
ii  libdbus-1-3 1.12.20-2
ii  libdrm2 2.4.104-1
ii  libevent-2.1-7  2.1.12-stable-1
ii  libexpat1   2.2.10-2
ii  libflac81.3.3-2
ii  libfontconfig1  2.13.1-4.2
ii  libfreetype62.10.4+dfsg-1
ii  libgbm1 20.3.5-1
ii  libgcc-s1   10.2.1-6
ii  libglib2.0-02.66.8-1
ii  libharfbuzz0b   2.7.4-1
ii  libicu6767.1-7
ii  libjpeg62-turbo 1:2.0.6-4
ii  libjsoncpp241.9.4-4
ii  liblcms2-2  2.12~rc1-2
ii  libminizip1 1.1-8+b1
ii  libnspr42:4.29-1
ii  libnss3 2:3.61-1+deb11u2
ii  libopenjp2-72.4.0-3
ii  libopus01.3.1-0.1
ii  libpango-1.0-0  1.46.2-3
ii  libpng16-16 1.6.37-3
ii  libpulse0   14.2-2
ii  libre2-920210201+dfsg-1
ii  libsnappy1v51.1.8-1
ii  libstdc++6  10.2.1-6
ii  libwebp60.6.1-2.1
ii  libwebpdemux2   0.6.1-2.1
ii  libwebpmux3 0.6.1-2.1
ii  libx11-62:1.7.2-1
ii  libxcb1 1.14-3
ii  libxcomposite1  1:0.4.5-1
ii  libxdamage1 1:1.1.5-2
ii  libxext62:1.3.3-1.1
ii  libxfixes3  1:5.0.3-2
ii  libxkbcommon0   1.0.3-2
ii  libxml2 2.9.10+dfsg-6.7
ii  libxrandr2  2:1.5.1-1
ii  libxslt1.1  1.1.34-4
ii  zlib1g  1:1.2.11.dfsg-2

Versions of packages chromium recommends:
ii  chromium-sandbox  98.0.4758.80-1~deb11u1

Versions of packages chromium suggests:
pn  chromium-driver  
pn  chromium-l10n
pn  chromium-shell   

Versions of packages chromium-common depends on:
ii  libc6   2.31-13+deb11u2
ii  libstdc++6  10.2.1-6
ii  libx11-62:1.7.2-1
ii  libxext62:1.3.3-1.1
ii  x11-utils   7.7+5
ii  xdg-utils   1.1.3-4.1
ii  zlib1g  1:1.2.11.dfsg-2

Versions of packages chromium-common recommends:
ii  chromium-sandbox   98.0.4758.80-1~deb11u1
pn  fonts-liberation   
ii  libgl1-mesa-dri20.3.5-1
pn  libu2f-udev
pn  notification-daemon
pn  system-config-printer  
ii  upower 0.99.11-2

Versions of packages chromium-sandbox depends on:
ii  libc6  2.31-13+deb11u2

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: chromium
Source-Version: 98.0.4758.102-1~deb11u1
Done: Andres Salomon 

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

Bug#287371: [xml/sgml-pkgs] Bug#287371: xsltproc: Probable memory leak (when using document()?)

[Mattia Rizzolo]

On Thu, Feb 10, 2022 at 01:08:33PM +0100, Vincent Lefevre wrote:
> This is no different than CVE-2013-0338 and CVE-2013-0339[*]. The
> point is that from a small document, one can exhaust the memory
> of the machine. CVE-2013-0338 and CVE-2013-0339 are about entity
> expansion, but there are the same consequences with just loading
> data in memory.
> 
> [*] https://www.openwall.com/lists/oss-security/2013/02/22/3

If you believe so, and you confirmed that it hasn't been fixed in the
past 15 years, could you please either (or both):
 * report it to mitre's CVE form
 * report it in https://gitlab.gnome.org/GNOME/libxml2/-/issues
?

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#1006127: wireless-regdb stable policy

[Salvatore Bonaccorso]

Hi,

On Sat, Feb 19, 2022 at 04:30:35PM +, Jiaxun Yang wrote:
> 
> 
> 在 2022/2/19 16:27, Salvatore Bonaccorso 写道:
> > Hi,
> > 
> > On Sat, Feb 19, 2022 at 02:49:32PM +, Jiaxun Yang wrote:
> > > Package: wireless-regdb
> > > Version: 2021.08.28-1
> > > Severity: grave
> > > 
> > > Dear Maintainer
> > > 
> > > wireless-regdb stores regulation information for various regions. It's
> > > importatnt to keep
> > > it updated on every system to ensure legal compliance on user's system.
> > > 
> > > For example, China resctrcted transmission power for 5150 - 5350 MHz to 20
> > > dBm, while
> > > the version in stable is still using the old 23 dBm limitation. System
> > > running stable can
> > > be accused violation of laws.
> > > 
> > > Thus this package needs to be a part of security update to all stable
> > > release to prevent
> > > legal issues for users.
> > In avoidance of doubts, no this is not material to be shipped via a
> > security update, but it can in fact be updated in stable through the
> > stable point releases (and when needed updated earlier through the
> > updates suites).
> Hi,
> 
> I see tzdata updates is shipping through security in strectch, I think
> wireless-regdb is in similiar situation.

You are mentioning stretch, which is supported by the LTS project. In
fact this is true there, because for the LTS suite there is no point
release approach. You will notice that tzdata for stable is released
at point releases times, and when needed earlier through the updates
suite, see for example
https://lists.debian.org/debian-stable-announce/2021/10/msg2.html
.

Anyway, the point is it can be updated for stable, but the channel
would be another one. It first should be updated in unstable and
testing, and then the other suites can follow via the mentioned
approach.

HTH,

Regards,
Salvatore

Processed: Bug#1006041 marked as pending in pymarkups

[Debian Bug Tracking System]

Processing control commands:

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

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

Bug#1006041: marked as pending in pymarkups

[Dmitry Shachnev]

Control: tag -1 pending

Hello,

Bug #1006041 in pymarkups 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/pymarkups/-/commit/2d7dcce330930a129fd70b0254e1f0f853715188


Add a patch to fix build with Pygments 2.11.

Closes: #1006041.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1006041

Processed: myspell: do not ship with bookworm

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 1006131 1006132
Bug #1006134 [src:myspell] myspell: do not ship with bookworm
1006134 was not blocked by any bugs.
1006134 was not blocking any bugs.
Added blocking bug(s) of 1006134: 1006131 and 1006132

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

Bug#1006134: myspell: do not ship with bookworm

[Mattia Rizzolo]

Source: myspell
Version: 1:3.0+pre3.1-24.2
Severity: serious
Tags: bookworm sid
Control: block -1 by 1006131 1006132

We don't want to release myspell with bookworm.

The only 2 packages that Build-Depends on myspell-tools are marked as
blockers.  Anything else that I found only uses myspell-tools as an
alternative where hunspell-tools is preferred first.


Since there are only 2 rev deps, we'd rather not introduce transitional
packages or such (as suggested in #898746).


This bug will become an RM bug soon, possibly after the above blockers
are fixed.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#1006132: ifrench-gut: please stop build-depending on myspell-tools

[Mattia Rizzolo]

Source: ifrench-gut
Version: 1:1.0-32.1
Severity: serious

Dear maintainer,

we plan to remove src:myspell really soon, and together with it also
the package "myspell-tools".
Your package still depends on it.

Please see whether you can move whatever the package is doing to
hunspell-tools, or otherwise please tell us src:hunspell maintainers how
that is not possible for you.

Thank you for maintaining ifrench-gut.


-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#1006131: rus-ispell: please stop build-depending on myspell-tools

[Mattia Rizzolo]

Source: rus-ispell
Version: 0.99g5-27
Severity: serious

Dear maintainer,

we plan to remove src:myspell really soon, and together with it also
the package "myspell-tools".
Your package still depends on it.

Please see whether you can move whatever the package is doing to
hunspell-tools, or otherwise please tell us src:hunspell maintainers how
that is not possible for you.

Thank you for maintaining rus-ispell.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#1006127: wireless-regdb stable policy

[Jiaxun Yang]

在 2022/2/19 16:27, Salvatore Bonaccorso 写道:

Hi,

On Sat, Feb 19, 2022 at 02:49:32PM +, Jiaxun Yang wrote:

Package: wireless-regdb
Version: 2021.08.28-1
Severity: grave

Dear Maintainer

wireless-regdb stores regulation information for various regions. It's
importatnt to keep
it updated on every system to ensure legal compliance on user's system.

For example, China resctrcted transmission power for 5150 - 5350 MHz to 20
dBm, while
the version in stable is still using the old 23 dBm limitation. System
running stable can
be accused violation of laws.

Thus this package needs to be a part of security update to all stable
release to prevent
legal issues for users.

In avoidance of doubts, no this is not material to be shipped via a
security update, but it can in fact be updated in stable through the
stable point releases (and when needed updated earlier through the
updates suites).

Hi,

I see tzdata updates is shipping through security in strectch, I think
wireless-regdb is in similiar situation.

Thanks.
- Jiaxun



Regards,
Salvatore

Bug#1006127: wireless-regdb stable policy

[Salvatore Bonaccorso]

Hi,

On Sat, Feb 19, 2022 at 02:49:32PM +, Jiaxun Yang wrote:
> Package: wireless-regdb
> Version: 2021.08.28-1
> Severity: grave
> 
> Dear Maintainer
> 
> wireless-regdb stores regulation information for various regions. It's
> importatnt to keep
> it updated on every system to ensure legal compliance on user's system.
> 
> For example, China resctrcted transmission power for 5150 - 5350 MHz to 20
> dBm, while
> the version in stable is still using the old 23 dBm limitation. System
> running stable can
> be accused violation of laws.
> 
> Thus this package needs to be a part of security update to all stable
> release to prevent
> legal issues for users.

In avoidance of doubts, no this is not material to be shipped via a
security update, but it can in fact be updated in stable through the
stable point releases (and when needed updated earlier through the
updates suites).

Regards,
Salvatore

Bug#1006037: marked as done (gnome-initial-setup: FTBFS: build-dependency not installable: libgnome-desktop-4-dev)

[Debian Bug Tracking System]

Your message dated Sat, 19 Feb 2022 16:03:58 +
with message-id 
and subject line Bug#1006037: fixed in gnome-desktop 42~beta-1
has caused the Debian Bug report #1006037,
regarding gnome-initial-setup: FTBFS: build-dependency not installable: 
libgnome-desktop-4-dev
to be marked as done.

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

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


-- 
1006037: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006037
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-initial-setup
Version: 42~beta-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 13), dh-sequence-gnome, 
> gsettings-desktop-schemas-dev (>= 3.37.1), itstool, libaccountsservice-dev, 
> libcheese-gtk-dev (>= 3.28), libfontconfig1-dev, libgdm-dev (>= 3.8.3), 
> libgeoclue-2-dev (>= 2.3.1), libgeocode-glib-dev, libglib2.0-dev (>= 2.63.1), 
> libgnome-desktop-4-dev, libgoa-1.0-dev, libgoa-backend-1.0-dev, libgtk-3-dev 
> (>= 3.19.12), libgweather-3-dev (>= 3.13.91), libhandy-1-dev (>= 1.5.90), 
> libibus-1.0-dev (>= 1.5.2), libjson-glib-dev, libkrb5-dev, 
> libmalcontent-0-dev, libmalcontent-ui-0-dev, libnm-dev (>= 1.2), libnma-dev 
> (>= 1.0), libpango1.0-dev (>= 1.32.5), libpolkit-gobject-1-dev (>= 0.103), 
> libpwquality-dev, librest-dev, libsecret-1-dev (>= 0.18.8), libsystemd-dev, 
> libwebkit2gtk-4.0-dev (>= 2.26), meson (>= 0.50.0), systemd (>= 242), 
> build-essential, fakeroot
> Filtered Build-Depends: debhelper-compat (= 13), dh-sequence-gnome, 
> gsettings-desktop-schemas-dev (>= 3.37.1), itstool, libaccountsservice-dev, 
> libcheese-gtk-dev (>= 3.28), libfontconfig1-dev, libgdm-dev (>= 3.8.3), 
> libgeoclue-2-dev (>= 2.3.1), libgeocode-glib-dev, libglib2.0-dev (>= 2.63.1), 
> libgnome-desktop-4-dev, libgoa-1.0-dev, libgoa-backend-1.0-dev, libgtk-3-dev 
> (>= 3.19.12), libgweather-3-dev (>= 3.13.91), libhandy-1-dev (>= 1.5.90), 
> libibus-1.0-dev (>= 1.5.2), libjson-glib-dev, libkrb5-dev, 
> libmalcontent-0-dev, libmalcontent-ui-0-dev, libnm-dev (>= 1.2), libnma-dev 
> (>= 1.0), libpango1.0-dev (>= 1.32.5), libpolkit-gobject-1-dev (>= 0.103), 
> libpwquality-dev, librest-dev, libsecret-1-dev (>= 0.18.8), libsystemd-dev, 
> libwebkit2gtk-4.0-dev (>= 2.26), meson (>= 0.50.0), systemd (>= 242), 
> build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [741 B]
> Get:5 copy:/<>/apt_archive ./ Packages [760 B]
> Fetched 2464 B in 0s (174 kB/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: libgnome-desktop-4-dev but it is 
> not installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2022/02/18/gnome-initial-setup_42~beta-1_unstable.log

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: gnome-desktop
Source-Version: 42~beta-1
Done: Jeremy Bicha 

We believe that the 

Bug#1004037: Segmentation fault in plink2 (Was: src:plink2: fails to migrate to testing for too long: autopkgtest regression)

[Chris Chang]

If you build off the current head, the version string should say "18 Feb
2022", not "17 Feb 2022".

On Sat, Feb 19, 2022 at 7:02 AM Andreas Tille  wrote:

> Hi again,
>
> Am Sat, Feb 19, 2022 at 12:28:21AM -0800 schrieb Chris Chang:
> > Ok, new release/tag created.
>
> I've built the new version now.  The bad news is that it keeps on
> SEGFAULTing for me:
>
> ...
> (gdb) run
> Starting program: /usr/lib/plink2/plink2-sse3 --debug --pfile tmp_data
> --export vcf vcf-dosage=DS --out tmp_data2
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> [New Thread 0x74cc7640 (LWP 985019)]
> [New Thread 0x744c6640 (LWP 985020)]
> [New Thread 0x7fffebcc5640 (LWP 985021)]
> PLINK v2.00a3 64-bit (17 Feb 2022)
> www.cog-genomics.org/plink/2.0/
> (C) 2005-2022 Shaun Purcell, Christopher Chang   GNU General Public
> License v3
> Logging to tmp_data2.log.
> Options in effect:
>   --debug
>   --export vcf vcf-dosage=DS
>   --out tmp_data2
>   --pfile tmp_data
>
> Start time: Sat Feb 19 16:00:00 2022
> 31998 MiB RAM detected; reserving 15999 MiB for main workspace.
> Using up to 4 compute threads.
> [New Thread 0x77fc5640 (LWP 985022)]
>
> Thread 1 "plink2-sse3" received signal SIGSEGV, Segmentation fault.
> plink2::LoadPsam (psamname=psamname@entry=0x7fffbe60 "tmp_data.psam",
> pheno_range_list_ptr=, fam_cols=..., pheno_ct_max= out>,
> missing_pheno=, affection_01=0, max_thread_ct=4,
> piip=0x7fff8870, sample_include_ptr=0x7fff8790,
> founder_info_ptr=0x7fff87a8, sex_nm_ptr=0x7fff8798,
> sex_male_ptr=0x7fff87a0, pheno_cols_ptr=0x7fff8770,
> pheno_names_ptr=0x7fff8780, raw_sample_ct_ptr=0x7fff8728,
> pheno_ct_ptr=0x7fff8720,
> max_pheno_name_blen_ptr=0x7fff87b0) at ../plink2_psam.cc:611
> 611 pheno_cols[pheno_idx].nonmiss = nullptr;
>
>
> Please let me know if I can do further checks.
>
> Kind regards
>
>   Andreas.
>
> --
> http://fam-tille.de
>

Processed (with 1 error): Re: Bug#1006037: gnome-initial-setup: FTBFS: build-dependency not installable: libgnome-desktop-4-dev

[Debian Bug Tracking System]

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

> reassign 1006037 src:gnome-desktop
Bug #1006037 [gnome-desktop] gnome-initial-setup: FTBFS: build-dependency not 
installable: libgnome-desktop-4-dev
Bug reassigned from package 'gnome-desktop' to 'src:gnome-desktop'.
Ignoring request to alter found versions of bug #1006037 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1006037 to the same values 
previously set
> assigns 1006037 src:gnome-initial-setup
Unknown command or malformed arguments to command.
>
End of message, stopping processing here.

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

Processed: Re: Bug#1006037: gnome-initial-setup: FTBFS: build-dependency not installable: libgnome-desktop-4-dev

[Debian Bug Tracking System]

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

> reassign 1006037 gnome-desktop
Bug #1006037 [src:gnome-initial-setup] gnome-initial-setup: FTBFS: 
build-dependency not installable: libgnome-desktop-4-dev
Bug reassigned from package 'src:gnome-initial-setup' to 'gnome-desktop'.
No longer marked as found in versions gnome-initial-setup/42~beta-1.
Ignoring request to alter fixed versions of bug #1006037 to the same values 
previously set
>
End of message, stopping processing here.

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

Bug#1006127: wireless-regdb stable policy

[Jiaxun Yang]

Package: wireless-regdb
Version: 2021.08.28-1
Severity: grave

Dear Maintainer

wireless-regdb stores regulation information for various regions. It's 
importatnt to keep

it updated on every system to ensure legal compliance on user's system.

For example, China resctrcted transmission power for 5150 - 5350 MHz to 
20 dBm, while
the version in stable is still using the old 23 dBm limitation. System 
running stable can

be accused violation of laws.

Thus this package needs to be a part of security update to all stable 
release to prevent

legal issues for users.

Thanks.
- Jiaxun

Bug#1005311:

[KeyofBlueS]

Hi, I tested the nvidia legacy 340.108-12+b1 driver with
xserver-xorg-core 2:21.1.3-2+b1 (xorg-video-abi-25) and it seems it's
working fine by just adding:

Section "ServerFlags"
  Option "IgnoreABI" "1"
EndSection

in /etc/X11/xorg.conf.d/20-nvidia.conf


Is there hope that the legacy 340.108 driver will still be supported
by debian sid? Andreas Beckmann? please?

Thanks and best regards.

Processed: bug 1006056 is forwarded to https://github.com/newren/git-filter-repo/issues/344

[Debian Bug Tracking System]

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

> forwarded 1006056 https://github.com/newren/git-filter-repo/issues/344
Bug #1006056 [src:git-filter-repo] git-filter-repo: FTBFS: t9390-filter-repo.sh 
failed
Set Bug forwarded-to-address to 
'https://github.com/newren/git-filter-repo/issues/344'.
> thanks
Stopping processing here.

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

Bug#1004037: Segmentation fault in plink2 (Was: src:plink2: fails to migrate to testing for too long: autopkgtest regression)

[Andreas Tille]

Hi again,

Am Sat, Feb 19, 2022 at 12:28:21AM -0800 schrieb Chris Chang:
> Ok, new release/tag created.

I've built the new version now.  The bad news is that it keeps on
SEGFAULTing for me:

...
(gdb) run
Starting program: /usr/lib/plink2/plink2-sse3 --debug --pfile tmp_data --export 
vcf vcf-dosage=DS --out tmp_data2
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x74cc7640 (LWP 985019)]
[New Thread 0x744c6640 (LWP 985020)]
[New Thread 0x7fffebcc5640 (LWP 985021)]
PLINK v2.00a3 64-bit (17 Feb 2022) www.cog-genomics.org/plink/2.0/
(C) 2005-2022 Shaun Purcell, Christopher Chang   GNU General Public License v3
Logging to tmp_data2.log.
Options in effect:
  --debug
  --export vcf vcf-dosage=DS
  --out tmp_data2
  --pfile tmp_data

Start time: Sat Feb 19 16:00:00 2022
31998 MiB RAM detected; reserving 15999 MiB for main workspace.
Using up to 4 compute threads.
[New Thread 0x77fc5640 (LWP 985022)]

Thread 1 "plink2-sse3" received signal SIGSEGV, Segmentation fault.
plink2::LoadPsam (psamname=psamname@entry=0x7fffbe60 "tmp_data.psam", 
pheno_range_list_ptr=, fam_cols=..., pheno_ct_max=, 
missing_pheno=, affection_01=0, max_thread_ct=4, 
piip=0x7fff8870, sample_include_ptr=0x7fff8790, 
founder_info_ptr=0x7fff87a8, sex_nm_ptr=0x7fff8798, 
sex_male_ptr=0x7fff87a0, pheno_cols_ptr=0x7fff8770, 
pheno_names_ptr=0x7fff8780, raw_sample_ct_ptr=0x7fff8728, 
pheno_ct_ptr=0x7fff8720, 
max_pheno_name_blen_ptr=0x7fff87b0) at ../plink2_psam.cc:611
611 pheno_cols[pheno_idx].nonmiss = nullptr;


Please let me know if I can do further checks.

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#997359: marked as done (Inkscape crashes when running as batch without X11)

[Debian Bug Tracking System]

Your message dated Sat, 19 Feb 2022 14:42:07 +
with message-id 
and subject line Bug#997359: fixed in inkscape 1.1.2-1
has caused the Debian Bug report #997359,
regarding Inkscape crashes when running as batch without X11
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.)


-- 
997359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997359
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: debian-astro
Version: 3.0
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> inkscape --batch-process Debian-Astro-logo.svg --export-width=25 
> --export-filename=Debian-Astro-logo-25x39.png
> Unable to init server: Could not connect: Connection refused
> 
> (inkscape:15837): Gtk-CRITICAL **: 07:38:18.224: 
> gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
> 
> Emergency save activated!
> Emergency save completed. Inkscape will close now.
> If you can reproduce this crash, please file a bug at 
> https://inkscape.org/report
> with a detailed description of the steps leading to the crash, so we can fix 
> it.
> 
> (inkscape:15837): Gtk-CRITICAL **: 07:38:18.225: 
> _gtk_style_provider_private_get_settings: assertion 
> 'GTK_IS_STYLE_PROVIDER_PRIVATE (provider)' failed
> 
> (inkscape:15837): Gtk-CRITICAL **: 07:38:18.225: 
> _gtk_style_provider_private_get_settings: assertion 
> 'GTK_IS_STYLE_PROVIDER_PRIVATE (provider)' failed
> 
> (inkscape:15837): Gtk-CRITICAL **: 07:38:18.225: 
> _gtk_style_provider_private_get_settings: assertion 
> 'GTK_IS_STYLE_PROVIDER_PRIVATE (provider)' failed
> make[1]: *** [debian/rules:9: build_logos] Segmentation fault
> make[1]: Leaving directory '/<>'
> make: *** [/usr/share/blends-dev/rules:33: build] Error 2


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/debian-astro_3.0_unstable.log

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: inkscape
Source-Version: 1.1.2-1
Done: Mattia Rizzolo 

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

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

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

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated inkscape package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 19 Feb 2022 13:40:23 +0100
Source: inkscape
Architecture: source
Version: 1.1.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Mattia Rizzolo 
Closes: 997359
Changes:
 inkscape (1.1.2-1) unstable; urgency=medium
 .
   * New upstream version 1.1.2.
 https://wiki.inkscape.org/wiki/index.php/Release_notes/1.1.2
   * Drop patch applied upstream.
   * Add patch from upstream to fix a crash when inkscape is run with --batch
 and a gui is not available.  Closes: #997359
   * Add patch to call `python3` instead of `python` when running tests.
   * Add new build-dep on python3-lxml .
Checksums-Sha1:
 0fc5ac6bee885f1f5c42c6f8317d65df7d5d8d3a 3043 inkscape_1.1.2-1.dsc
 a42b17d0ec6bcdd93528e0e5416b32ff3f5975da 34222832 inkscape_1.1.2.orig.tar.xz
 729c1c986ed52444ec18153ee2cf67ffc486ad2d 195 inkscape_1.1.2.orig.tar.xz.asc
 d2d1fca2205882a1fb83ec9c0ebed9ba9756ba62 32820 inkscape_1.1.2-1.debian.tar.xz
 fc60e2767234656e76d16832e686ee2fda923f05 19967 inkscape_1.1.2-1_amd64.buildinfo
Checksums-Sha256:
 f3a638930a98f5d4b3e4a4fd1babf5e2e504d26577b5272d2f64b728da11a67c 3043 
inkscape_1.1.2-1.dsc
 3ffe54a06d0b25a4cd8b6eb424536ef1ed205be13443a39cd437c8c7b89b96d1 34222832 
inkscape_1.1.2.orig.tar.xz
 

Processed: Re: Bug#1006115: linux-image-amd64: System does not boot with 5.16

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #1006115 [src:linux] linux-image-amd64: System does not boot with 5.16
Severity set to 'important' from 'critical'
> tags -1 + moreinfo
Bug #1006115 [src:linux] linux-image-amd64: System does not boot with 5.16
Added tag(s) moreinfo.

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

Bug#1006115: linux-image-amd64: System does not boot with 5.16

[Salvatore Bonaccorso]

Control: severity -1 important
Control: tags -1 + moreinfo

On Sat, Feb 19, 2022 at 12:27:11PM +, Julien-Benjamin wrote:
> Package: linux-image-amd64
> Version: 5.16.7-2
> Severity: critical
> Justification: breaks the whole system
> 
> After upgrading from 5.15 to 5.16 (testing branch), the system does
> not boot anymore.
> 
> I could not see any obvious reason as to why ; a quick and dirty
> workaround is to boot with the 5.15 version via GRUB.

>From the boot log you attached, it looks it goes far enough. Can you
elaborate on the does not boot anymore? Where does it get stuck for
you? Is it reacting on the console, and can you login? Can you login
remotely? It might be similar to #1005884.

What happens if you do not load the nvidia module tainting the kernel?

Would it be possible that you test the kernel in unstable, as uploaded
5.16.10-1? (Note the signed packages are not yet available though).

Regards,
Salvatore

Processed: reassign 1006115 to src:linux

[Debian Bug Tracking System]

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

> reassign 1006115 src:linux 5.16.7-2
Bug #1006115 [linux-image-amd64] linux-image-amd64: System does not boot with 
5.16
Bug reassigned from package 'linux-image-amd64' to 'src:linux'.
No longer marked as found in versions linux-signed-amd64/5.16.7+2.
Ignoring request to alter fixed versions of bug #1006115 to the same values 
previously set
Bug #1006115 [src:linux] linux-image-amd64: System does not boot with 5.16
Marked as found in versions linux/5.16.7-2.
> thanks
Stopping processing here.

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

Processed: tagging 1001217

[Debian Bug Tracking System]

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

> tags 1001217 + ftbfs
Bug #1001217 [dislocker] FTBFS against Ruby 3.0
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: severity of 1001217 is serious

[Debian Bug Tracking System]

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

> severity 1001217 serious
Bug #1001217 [dislocker] FTBFS against Ruby 3.0
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: Bug#997359 marked as pending in inkscape

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #997359 [inkscape] Inkscape crashes when running as batch without X11
Added tag(s) pending.

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

Bug#997359: marked as pending in inkscape

[Mattia Rizzolo]

Control: tag -1 pending

Hello,

Bug #997359 in inkscape 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/multimedia-team/inkscape/-/commit/22960b0b09d0f476a93f98e1ff90f5114ace8dec


Add patch from upstream to fix a crash when inkscape is run with --batch and a 
gui is not available

Closes: #997359
Signed-off-by: Mattia Rizzolo 


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/997359

Bug#990201: Update golang-github-appc-cni to 1.0 (was Re: singularity-container: CVE-2021-33622)

[Andreas Tille]

Hi,

Am Fri, Feb 18, 2022 at 10:19:01PM +0100 schrieb Andreas Tille:
> > So I do not know where this error comes from; or if you have something else 
> > locally.
> 
> I'll simply revert the version bump ...

I did so and uploaded to experimental[1].  I think once all
preconditions are in unstable we can upload to unstable as well.

I will keep on checking whether more vendored code copies can be
removed meanwhile.

Kind regards

  Andreas.
  
[1] 
https://buildd.debian.org/status/package.php?p=singularity-container=experimental
 

-- 
http://fam-tille.de

Processed: uwsgi: FTBFS with ruby3.0 as default

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 1004915
Bug #1006119 [src:uwsgi] uwsgi: FTBFS with ruby3.0 as default
1006119 was not blocked by any bugs.
1006119 was not blocking any bugs.
Added blocking bug(s) of 1006119: 1004915

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

Bug#1006119: uwsgi: FTBFS with ruby3.0 as default

[Paul Gevers]

Source: uwsgi
Version: 2.0.20-2
Severity: serious
Tags: ftbfs
Justification: FTBFS
Control: block -1 by 1004915

Dear maintainer,

I tried to binNMU your package for the ongoing ruby3.0 as default ruby
transition. It failed:
https://buildd.debian.org/status/package.php?p=uwsgi

Paul

*** uWSGI building and linking plugin plugins/python ***
x86_64-linux-gnu-gcc -pthread -fPIC -shared -o ./python39_plugin.so -I. -O2 -I. 
-Wall -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wextra -Wno-unused-parameter 
-Wno-missing-field-initializers -DUWSGI_HAS_IFADDRS -DUWSGI_ZLIB 
-DUWSGI_LOCK_USE_MUTEX -DUWSGI_EVENT_USE_EPOLL -DUWSGI_EVENT_TIMER_USE_TIMERFD 
-DUWSGI_EVENT_FILEMONITOR_USE_INOTIFY  -DUWSGI_PCRE -DUWSGI_ROUTING -DUWSGI_CAP 
-DUWSGI_UUID -DUWSGI_VERSION="\"2.0.20-debian\"" -DUWSGI_VERSION_BASE="2" 
-DUWSGI_VERSION_MAJOR="0" -DUWSGI_VERSION_MINOR="20" 
-DUWSGI_VERSION_REVISION="0" -DUWSGI_VERSION_CUSTOM="\"debian\"" -DUWSGI_YAML 
-DUWSGI_LIBYAML -I/usr/include/yajl -DUWSGI_JSON -DUWSGI_JSON_YAJL -DUWSGI_SSL 
-I/usr/include/libxml2 -DUWSGI_XML -DUWSGI_XML_LIBXML2 
-DUWSGI_PLUGIN_DIR="\".\"" -I/usr/include/python3.9 -I/usr/include/python3.9 
-Dpython_plugin=python39_plugin plugins/python/python_plugin.c 
plugins/python/pyutils.c plugins/python/pyloader.c 
plugins/python/wsgi_handlers.c plugins/python/wsgi_headers.c 
plugins/python/wsgi_subhandler.c plugins/python/web3_subhandler.c 
plugins/python/pump_subhandler.c plugins/python/gil.c 
plugins/python/uwsgi_pymodule.c plugins/python/profiler.c 
plugins/python/symimporter.c plugins/python/tracebacker.c plugins/python/raw.c 
-Wl,-z,relro -L/usr/lib/x86_64-linux-gnu -lcrypt -lpthread -ldl -lutil -lm -lm 
-lpython3.9
build time: 7 seconds
*** python39 plugin built and available in ./python39_plugin.so ***
touch debian/stamp-uwsgi-plugin-python3
\
 \
 \
 \
 CFLAGS="-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security" CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" 
LDFLAGS="-Wl,-z,relro" python3 uwsgiconfig.py -v --plugin plugins/rack_ruby27 
debian/buildconf/uwsgi-plugin.ini rack_ruby27
using profile: debian/buildconf/uwsgi-plugin.ini
detected include path: ['/usr/lib/gcc/x86_64-linux-gnu/11/include', 
'/usr/local/include', '/usr/include/x86_64-linux-gnu', '/usr/include']
*** uWSGI building and linking plugin plugins/rack_ruby27 ***
Error: unable to find directory 'plugins/rack_ruby27'
make: *** [debian/rules:425: debian/stamp-uwsgi-plugin-rack-ruby2.7] Error 1

Processed (with 1 error): src:dmrgpp: fails to migrate to testing for too long: autopkgtest regression

[Debian Bug Tracking System]

Processing control commands:

> close -1 6.02-2
Bug #1006118 [src:dmrgpp] src:dmrgpp: fails to migrate to testing for too long: 
autopkgtest regression
Marked as fixed in versions dmrgpp/6.02-2.
Bug #1006118 [src:dmrgpp] src:dmrgpp: fails to migrate to testing for too long: 
autopkgtest regression
Marked Bug as done
> block -1 1003061
Unknown command or malformed arguments to command.


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

Bug#1006118: src:dmrgpp: fails to migrate to testing for too long: autopkgtest regression

[Paul Gevers]

Source: dmrgpp
Version: 6.00-2
Severity: serious
Control: close -1 6.02-2
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 1003061

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:dmrgpp has been trying to migrate for 61 
days [2]. Hence, I am filing this bug.


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



OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:lomiri-app-launch: fails to migrate to testing for too long: depends on new non-migrating package

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.1.1-1
Bug #1006117 [src:lomiri-app-launch] src:lomiri-app-launch: fails to migrate to 
testing for too long: depends on new non-migrating package
Marked as fixed in versions lomiri-app-launch/0.1.1-1.
Bug #1006117 [src:lomiri-app-launch] src:lomiri-app-launch: fails to migrate to 
testing for too long: depends on new non-migrating package
Marked Bug as done

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

Bug#1006117: src:lomiri-app-launch: fails to migrate to testing for too long: depends on new non-migrating package

[Paul Gevers]

Source: lomiri-app-launch
Version: 0.0.90-10
Severity: serious
Control: close -1 0.1.1-1
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:lomiri-app-launch has been trying to 
migrate for 61 days [2]. Hence, I am filing this bug.


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=lomiri-app-launch



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1003020: marked as done (openblas breaks hypre autopkgtest on armhf: test times out after 2:47h)

[Debian Bug Tracking System]

Your message dated Sat, 19 Feb 2022 12:33:55 +
with message-id 
and subject line Bug#1003020: fixed in hypre 2.22.1-7
has caused the Debian Bug report #1003020,
regarding openblas breaks hypre autopkgtest on armhf: test times out after 2:47h
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.)


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

Source: openblas, hypre
Control: found -1 openblas/0.3.19+ds-1
Control: found -1 hypre/2.22.1-3
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of openblas the autopkgtest of hypre fails in 
testing when that autopkgtest is run with the binary packages of 
openblas from unstable on armhf due to a timeout after 2:47 h. It passes 
when run with only packages from testing in about 9-12 minutes. In 
tabular form:


   passfail
openblas   from testing0.3.19+ds-1
hypre  from testing2.22.1-3
all others from testingfrom testing

I copied some of the output at the bottom of this report, but as the 
test times out, I suspect it just hangs and there's not much useful to see.


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

https://ci.debian.net/data/autopkgtest/testing/armhf/h/hypre/17988587/log.gz

Building tests for HYPRE
rm -f *.o *.obj
rm -rf pchdir tca.map *inslog*
mpicc -I/usr/include/hypre -I/usr/include/superlu 
-I/usr/include/superlu-dist -pthread 
-I/usr/lib/arm-linux-gnueabihf/openmpi/include 
-I/usr/lib/arm-linux-gnueabihf/openmpi/include/openmpi-c -o ij.o ij.c
Building ij ... mpicc -o ij ij.o -L/lib -lHYPRE -Wl,-rpath,/lib 
 -L/usr/lib/arm-linux-gnueabihf/openmpi/lib -lmpi -lm mpicc 
-I/usr/include/hypre -I/usr/include/superlu -I/usr/include/superlu-dist 
-pthread -I/usr/lib/arm-linux-gnueabihf/openmpi/include 
-I/usr/lib/arm-linux-gnueabihf/openmpi/include/openmpi-c -o 
ij_assembly.o ij_assembly.c
Building ij_assembly ... mpicc -o ij_assembly ij_assembly.o -L/lib 
-lHYPRE -Wl,-rpath,/lib 
-L/usr/lib/arm-linux-gnueabihf/openmpi/lib -lmpi -lm mpicc 
-I/usr/include/hypre -I/usr/include/superlu -I/usr/include/superlu-dist 
-pthread -I/usr/lib/arm-linux-gnueabihf/openmpi/include 
-I/usr/lib/arm-linux-gnueabihf/openmpi/include/openmpi-c -o 
sstruct.o sstruct.c
Building sstruct ... mpicc -o sstruct sstruct.o -L/lib -lHYPRE 
-Wl,-rpath,/lib  -L/usr/lib/arm-linux-gnueabihf/openmpi/lib 
-lmpi -lm mpicc -I/usr/include/hypre -I/usr/include/superlu 
-I/usr/include/superlu-dist -pthread 
-I/usr/lib/arm-linux-gnueabihf/openmpi/include 
-I/usr/lib/arm-linux-gnueabihf/openmpi/include/openmpi-c -o struct.o 
struct.c
Building struct ... mpicc -o struct struct.o -L/lib -lHYPRE 
-Wl,-rpath,/lib  -L/usr/lib/arm-linux-gnueabihf/openmpi/lib 
-lmpi -lm mpicc -I/usr/include/hypre -I/usr/include/superlu 
-I/usr/include/superlu-dist -pthread 
-I/usr/lib/arm-linux-gnueabihf/openmpi/include 
-I/usr/lib/arm-linux-gnueabihf/openmpi/include/openmpi-c -o 
ams_driver.o ams_driver.c
Building ams_driver ... mpicc -o ams_driver ams_driver.o -L/lib -lHYPRE 
-Wl,-rpath,/lib  -L/usr/lib/arm-linux-gnueabihf/openmpi/lib 
-lmpi -lm mpicc -I/usr/include/hypre -I/usr/include/superlu 
-I/usr/include/superlu-dist -pthread 
-I/usr/lib/arm-linux-gnueabihf/openmpi/include 
-I/usr/lib/arm-linux-gnueabihf/openmpi/include/openmpi-c -o 
maxwell_unscaled.o maxwell_unscaled.c
Building maxwell_unscaled ... mpicc -o maxwell_unscaled 
maxwell_unscaled.o -L/lib -lHYPRE -Wl,-rpath,/lib 
-L/usr/lib/arm-linux-gnueabihf/openmpi/lib -lmpi -lm mpicc 
-I/usr/include/hypre -I/usr/include/superlu -I/usr/include/superlu-dist 
-pthread -I/usr/lib/arm-linux-gnueabihf/openmpi/include 
-I/usr/lib/arm-linux-gnueabihf/openmpi/include/openmpi-c -o 
struct_migrate.o struct_migrate.c
Building struct_migrate ... mpicc -o struct_migrate struct_migrate.o 
-L/lib -lHYPRE -Wl,-rpath,/lib 
-L/usr/lib/arm-linux-gnueabihf/openmpi/lib -lmpi -lm mpicc 
-I/usr/include/hypre 

Bug#1006029: gtk+3.0: FTBFS: various icons no longer present in adwaita-icon-theme

[Jeremy Bicha]

On Sat, Feb 19, 2022 at 6:05 AM Simon McVittie  wrote:
> I think this means adwaita-icon-theme has dropped some icons that GTK 3
> assumes will be present.
>
> (See also, all the bugs complaining that icons disappeared, most recently
> #1005997 - but my understanding is that there is no real specification for
> what an icon theme must contain, and consumers of icon themes frequently
> assume that every icon theme will have lots of random icons beyond the
> baseline set from hicolor-icon-theme.)

I did try running a debdiff on adwaita-icon-theme before uploading
because I was concerned that icons might have been dropped. My debdiff
came up clean but maybe I did it wrong.

When I asked in #gnome-design before uploading, I was told
emphatically that no icons were dropped in the 42 series but that
these symbolic app icons would be dropped early in the 43 release:
https://gitlab.gnome.org/GNOME/adwaita-icon-theme/-/issues/163

Jeremy

Bug#986487: marked as done (caftools: FTBFS with glibc >= 2.32)

[Debian Bug Tracking System]

Your message dated Sat, 19 Feb 2022 11:19:13 +
with message-id 
and subject line Bug#986487: fixed in caftools 2.0.3-2
has caused the Debian Bug report #986487,
regarding caftools: FTBFS with glibc >= 2.32
to be marked as done.

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

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


-- 
986487: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986487
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: caftools
Version: 2.0.3-1
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu hirsute ubuntu-patch

Hi,

caftools currently FTBFS against glibc 2.32, which is used in the
development release of Ubuntu (and should be in Debian soon).

This is because it uses sys_errlist instead of strerror(), which is also
supported in earlier versions of glibc.

In Ubuntu, the attached patch was applied to achieve the following:

  * d/p/glibc_2.32.patch: Use strerror() instead of sys_errlist/sys_nerr to
fix FTBFS with glibc >= 2.32.

Thanks for considering the patch.

Logan
diff -Nru caftools-2.0.3/debian/patches/glibc_2.32.patch 
caftools-2.0.3/debian/patches/glibc_2.32.patch
--- caftools-2.0.3/debian/patches/glibc_2.32.patch  1969-12-31 
19:00:00.0 -0500
+++ caftools-2.0.3/debian/patches/glibc_2.32.patch  2021-04-06 
15:56:49.0 -0400
@@ -0,0 +1,59 @@
+--- a/src/acedb/messubs.c
 b/src/acedb/messubs.c
+@@ -268,10 +268,6 @@
+   char *messbuf2 = [BUFSIZE/2];
+   static int total = 50 ;
+   /* extern int errno ; */
+-#if !defined(MACINTOSH) && !defined(__linux__)
+-  extern char *sys_errlist[] ;
+-  extern int sys_nerr ;
+-#endif
+ 
+   messFlag = TRUE ;
+ 
+@@ -284,15 +280,16 @@
+   messdump ("internal system error : %s", messbuf2) ;
+ }
+ #if !defined(MACINTOSH)
+-  else if (errno < sys_nerr)
+-{ messout ("%s : %s", messbuf2, sys_errlist[errno]) ;
+-  messdump ("%s : %s", messbuf2, sys_errlist[errno]) ;
++  else
++{ messout ("%s : %s", messbuf2, strerror(errno)) ;
++  messdump ("%s : %s", messbuf2, strerror(errno)) ;
+ }
+-#endif
++#else
+   else
+ { messout ("%s : system error %d", messbuf2, errno) ;
+   messdump ("%s : system error %d", messbuf2, errno) ;
+ }
++#endif
+ 
+   invokeDebugger () ;
+   errno = 0 ;
+@@ -312,10 +309,6 @@
+   extern void crashOut (char* text) ;
+ #else
+   /* extern int errno ; */
+-#if !defined(__linux__)
+-  extern char *sys_errlist[] ;
+-  extern int sys_nerr ;
+-#endif
+ #endif
+ 
+   if (messcrashbuf)
+@@ -330,11 +323,8 @@
+   crashOut (crashText) ;
+ #else
+   messbeep();
+-  if (errno <= 0 || errno >= sys_nerr)
+-fprintf (stderr,"!! FATAL ERROR %d: ", errno) ;
+-  else
+-fprintf (stderr,"!! FATAL ERROR: system error %d %s \n",
+-   errno, sys_errlist[errno]) ;
++  fprintf (stderr,"!! FATAL ERROR: system error %d %s \n",
++ errno, strerror(errno)) ;
+   fprintf (stderr, "!! %s\n", crashText) ;
+ #if !defined(MESSCLEAN)
+   graphOut (messbuf) ;/* to display on screen */
diff -Nru caftools-2.0.3/debian/patches/series 
caftools-2.0.3/debian/patches/series
--- caftools-2.0.3/debian/patches/series2020-05-19 10:14:05.0 
-0400
+++ caftools-2.0.3/debian/patches/series2021-04-06 15:53:55.0 
-0400
@@ -1,3 +1,4 @@
 messubs.patch
 autoconf.patch
 do_not_fail_building_man_pages.patch
+glibc_2.32.patch
--- End Message ---
--- Begin Message ---
Source: caftools
Source-Version: 2.0.3-2
Done: Sascha Steinbiss 

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

Debian distribution maintenance software
pp.
Sascha Steinbiss  (supplier of updated caftools 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: Sat, 19 Feb 2022 12:03:28 +0100
Source: caftools
Architecture: source
Version: 2.0.3-2
Distribution: unstable
Urgency: medium
Maintainer: Steffen Moeller 
Changed-By: Sascha Steinbiss 
Closes: 986487
Changes:
 caftools (2.0.3-2) unstable; urgency=medium
 .
   * Team upload.
   * Add patch to fix build on glibc >= 2.32. Thanks to Logan Rosen for the
 

Processed: Re: Bug#1006029: gtk+3.0: FTBFS: various icons no longer present in adwaita-icon-theme

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 adwaita-icon-theme 42~beta-1
Bug #1006029 [src:gtk+3.0] gtk+3.0: FTBFS: dh_auto_test: error: cd 
debian/build/deb && make -j8 check VERBOSE=1 -k check -j1 returned exit code 2
Bug reassigned from package 'src:gtk+3.0' to 'adwaita-icon-theme'.
No longer marked as found in versions gtk+3.0/3.24.31-1.
Ignoring request to alter fixed versions of bug #1006029 to the same values 
previously set
Bug #1006029 [adwaita-icon-theme] gtk+3.0: FTBFS: dh_auto_test: error: cd 
debian/build/deb && make -j8 check VERBOSE=1 -k check -j1 returned exit code 2
Marked as found in versions adwaita-icon-theme/42~beta-1.
> affects -1 + gtk+3.0
Bug #1006029 [adwaita-icon-theme] gtk+3.0: FTBFS: dh_auto_test: error: cd 
debian/build/deb && make -j8 check VERBOSE=1 -k check -j1 returned exit code 2
Added indication that 1006029 affects gtk+3.0

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

Bug#1006029: gtk+3.0: FTBFS: various icons no longer present in adwaita-icon-theme

[Simon McVittie]

Control: reassign -1 adwaita-icon-theme 42~beta-1
Control: affects -1 + gtk+3.0

On Sat, 19 Feb 2022 at 07:31:29 +0100, Lucas Nussbaum wrote:
> The full build log is available from:
> http://qa-logs.debian.net/2022/02/18/gtk+3.0_3.24.31-1_unstable.log

This also seems to be an autopkgtest regression triggered by an
adwaita-icon-theme update. From Lucas' build log:

TEST: check-icon-names... (pid=360930)
  /check-icon-names/dialog-password:   FAIL
GTester: last random seed: R02Sa4f8646711988095b3d1763d231f0c61
  /check-icon-names/dialog-error:  FAIL
GTester: last random seed: R02Sa4f8646711988095b3d1763d231f0c61
  /check-icon-names/dialog-information:FAIL
GTester: last random seed: R02Sa4f8646711988095b3d1763d231f0c61
  /check-icon-names/dialog-question:   FAIL
GTester: last random seed: R02Sa4f8646711988095b3d1763d231f0c61
  /check-icon-names/dialog-warning:FAIL
GTester: last random seed: R02Sa4f8646711988095b3d1763d231f0c61
  /check-icon-names/gtk-dnd:   OK
  /check-icon-names/gtk-dnd-multiple:  OK
  /check-icon-names/gtk-apply: OK
  /check-icon-names/gtk-cancel:OK
  /check-icon-names/gtk-no:OK
  /check-icon-names/gtk-ok:OK
  /check-icon-names/gtk-yes:   OK
  /check-icon-names/window-close:  FAIL
GTester: last random seed: R02Sa4f8646711988095b3d1763d231f0c61
  /check-icon-names/list-add:  FAIL

and so on.

I think this means adwaita-icon-theme has dropped some icons that GTK 3
assumes will be present.

(See also, all the bugs complaining that icons disappeared, most recently
#1005997 - but my understanding is that there is no real specification for
what an icon theme must contain, and consumers of icon themes frequently
assume that every icon theme will have lots of random icons beyond the
baseline set from hicolor-icon-theme.)

smcv

Bug#972212: marked as done (singularity-container: CVE-2020-15229)

[Debian Bug Tracking System]

Your message dated Sat, 19 Feb 2022 10:53:19 +
with message-id 
and subject line Bug#972212: fixed in singularity-container 3.9.4+ds2-1
has caused the Debian Bug report #972212,
regarding singularity-container: CVE-2020-15229
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.)


-- 
972212: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972212
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: singularity-container
Version: 3.5.2+ds1-1
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for singularity-container.

CVE-2020-15229[0]:
| Path traversal and files overwrite with unsquashfs

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2020-15229
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-15229
[1] https://github.com/hpcng/singularity/security/advisories/GHSA-7gcp-w6ww-2xv9

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: singularity-container
Source-Version: 3.9.4+ds2-1
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated singularity-container 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 18 Feb 2022 17:49:26 +0100
Source: singularity-container
Architecture: source
Version: 3.9.4+ds2-1
Distribution: experimental
Urgency: medium
Maintainer: Debian HPC Team 
Changed-By: Andreas Tille 
Closes: 965040 970465 972212 995171
Changes:
 singularity-container (3.9.4+ds2-1) experimental; urgency=medium
 .
   * Team upload
 .
   [ Yaroslav Halchenko ]
   * Fresh upstream release
 Closes: #995171
   * debian/watch - updated to point to -ce flavor of release on github.
 Thanks to Andreas Tille for the patch!
   * debian/patches
 - cni_plugin_path.patch - updated for moved files and more files with
   similar references of cni
 .
   [ Andreas Tille ]
   * New upstream release
  - Version 3.6.0 addresses CVE-2020-13845 CVE-2020-13846 CVE-2020-13847
Closes: #965040
  - Version 3.6.3 addresses CVE-2020-25039 CVE-2020-25040
Closes: #970465
  - Version 3.6.4 addresses CVE-2020-15229
Closes: #972212
   * Versioned (Build-)Depends: golang-github-blang-semver-dev (>= 4)
   * Versioned Build-Depends: golang-github-vbauerster-mpb-dev (>= 7.3.2)
   * Standards-Version: 4.6.0 (routine-update)
   * debhelper-compat 13 (routine-update)
   * Rules-Requires-Root: no (routine-update)
   * Use secure URI in Homepage field.
   * Update renamed lintian tag names in lintian overrides.
   * Use default salsa-ci pipeline
   * Bump github.com/vbauerster/mpb to v7
   * Drop Dave Love from Uploaders (Thanks a lot for your initial work Dave)
   * Versioned Build-Depends: golang-github-appc-cni-dev (>= 1.0.1~)
   * Do not try to `chown -c root.root` which is not permitted and granted
 in the final package anyway
   * Fix and simplify watch file
   * Replace vendored copies of
  github.com/Azure/go-ansiterm (golang-github-azure-go-ansiterm-dev)
  github.com/Netflix/go-expect (golang-github-netflix-go-expect-dev)
  github.com/ProtonMail/go-crypto (golang-github-protonmail-go-crypto-dev)
   * Distribute Apache-2.0 copyright NOTICE
 .
   [ Nilesh Patra ]
   * Follow pattern of d052a709acbe1fc2eae989842e4248a5ff90a591.patch to remove
 refervences to v4
Checksums-Sha1:
 b1f0cbfcd3765d48176e4839d67b49b225fca195 3761 
singularity-container_3.9.4+ds2-1.dsc
 6cb7531956db57dcc9b61ef28c15cb203be82c52 6244320 
singularity-container_3.9.4+ds2.orig.tar.xz
 79b9161d09288bfda76750a347b6c36a907c770e 19824 
singularity-container_3.9.4+ds2-1.debian.tar.xz
 657462f745988a2c5c27903684ca64d841cf7aef 24515 

Bug#970465: marked as done (singularity-container: CVE-2020-25039 CVE-2020-25040)

[Debian Bug Tracking System]

Your message dated Sat, 19 Feb 2022 10:53:19 +
with message-id 
and subject line Bug#970465: fixed in singularity-container 3.9.4+ds2-1
has caused the Debian Bug report #970465,
regarding singularity-container: CVE-2020-25039 CVE-2020-25040
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.)


-- 
970465: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970465
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: singularity-container
Version: 3.5.2+ds1-1
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerabilities were published for singularity-container.

CVE-2020-25039[0]:
| Sylabs Singularity 3.2.0 through 3.6.2 has Insecure Permissions on
| temporary directories used in fakeroot or user namespace container
| execution.


CVE-2020-25040[1]:
| Sylabs Singularity through 3.6.2 has Insecure Permissions on temporary
| directories used in explicit and implicit container build operations,
| a different vulnerability than CVE-2020-25039.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2020-25039
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-25039
[1] https://security-tracker.debian.org/tracker/CVE-2020-25040
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-25040

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: singularity-container
Source-Version: 3.9.4+ds2-1
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated singularity-container 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 18 Feb 2022 17:49:26 +0100
Source: singularity-container
Architecture: source
Version: 3.9.4+ds2-1
Distribution: experimental
Urgency: medium
Maintainer: Debian HPC Team 
Changed-By: Andreas Tille 
Closes: 965040 970465 972212 995171
Changes:
 singularity-container (3.9.4+ds2-1) experimental; urgency=medium
 .
   * Team upload
 .
   [ Yaroslav Halchenko ]
   * Fresh upstream release
 Closes: #995171
   * debian/watch - updated to point to -ce flavor of release on github.
 Thanks to Andreas Tille for the patch!
   * debian/patches
 - cni_plugin_path.patch - updated for moved files and more files with
   similar references of cni
 .
   [ Andreas Tille ]
   * New upstream release
  - Version 3.6.0 addresses CVE-2020-13845 CVE-2020-13846 CVE-2020-13847
Closes: #965040
  - Version 3.6.3 addresses CVE-2020-25039 CVE-2020-25040
Closes: #970465
  - Version 3.6.4 addresses CVE-2020-15229
Closes: #972212
   * Versioned (Build-)Depends: golang-github-blang-semver-dev (>= 4)
   * Versioned Build-Depends: golang-github-vbauerster-mpb-dev (>= 7.3.2)
   * Standards-Version: 4.6.0 (routine-update)
   * debhelper-compat 13 (routine-update)
   * Rules-Requires-Root: no (routine-update)
   * Use secure URI in Homepage field.
   * Update renamed lintian tag names in lintian overrides.
   * Use default salsa-ci pipeline
   * Bump github.com/vbauerster/mpb to v7
   * Drop Dave Love from Uploaders (Thanks a lot for your initial work Dave)
   * Versioned Build-Depends: golang-github-appc-cni-dev (>= 1.0.1~)
   * Do not try to `chown -c root.root` which is not permitted and granted
 in the final package anyway
   * Fix and simplify watch file
   * Replace vendored copies of
  github.com/Azure/go-ansiterm (golang-github-azure-go-ansiterm-dev)
  github.com/Netflix/go-expect (golang-github-netflix-go-expect-dev)
  github.com/ProtonMail/go-crypto (golang-github-protonmail-go-crypto-dev)
   * Distribute Apache-2.0 copyright NOTICE
 .
   [ Nilesh Patra ]
   * Follow pattern of d052a709acbe1fc2eae989842e4248a5ff90a591.patch to remove
 refervences to v4

Bug#965040: marked as done (singularity-container: CVE-2020-13845 CVE-2020-13846 CVE-2020-13847)

[Debian Bug Tracking System]

Your message dated Sat, 19 Feb 2022 10:53:19 +
with message-id 
and subject line Bug#965040: fixed in singularity-container 3.9.4+ds2-1
has caused the Debian Bug report #965040,
regarding singularity-container: CVE-2020-13845 CVE-2020-13846 CVE-2020-13847
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.)


-- 
965040: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965040
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: singularity-container
Version: 3.5.2+ds1-1
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: Debian Security Team 

Hi,

The following vulnerabilities were published for singularity-container.

CVE-2020-13845[0]:
| Sylabs Singularity 3.0 through 3.5 has Improper Validation of an
| Integrity Check Value. Image integrity is not validated when an ECL
| policy is enforced. The fingerprint required by the ECL is compared
| against the signature object descriptor(s) in the SIF file, rather
| than to a cryptographically validated signature.


CVE-2020-13846[1]:
| Sylabs Singularity 3.5.0 through 3.5.3 fails to report an error in a
| Status Code.


CVE-2020-13847[2]:
| Sylabs Singularity 3.0 through 3.5 lacks support for an Integrity
| Check. Singularity's sign and verify commands do not sign metadata
| found in the global header or data object descriptors of a SIF file.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2020-13845
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-13845
[1] https://security-tracker.debian.org/tracker/CVE-2020-13846
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-13846
[2] https://security-tracker.debian.org/tracker/CVE-2020-13847
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-13847

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: singularity-container
Source-Version: 3.9.4+ds2-1
Done: Andreas Tille 

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

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

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated singularity-container 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 18 Feb 2022 17:49:26 +0100
Source: singularity-container
Architecture: source
Version: 3.9.4+ds2-1
Distribution: experimental
Urgency: medium
Maintainer: Debian HPC Team 
Changed-By: Andreas Tille 
Closes: 965040 970465 972212 995171
Changes:
 singularity-container (3.9.4+ds2-1) experimental; urgency=medium
 .
   * Team upload
 .
   [ Yaroslav Halchenko ]
   * Fresh upstream release
 Closes: #995171
   * debian/watch - updated to point to -ce flavor of release on github.
 Thanks to Andreas Tille for the patch!
   * debian/patches
 - cni_plugin_path.patch - updated for moved files and more files with
   similar references of cni
 .
   [ Andreas Tille ]
   * New upstream release
  - Version 3.6.0 addresses CVE-2020-13845 CVE-2020-13846 CVE-2020-13847
Closes: #965040
  - Version 3.6.3 addresses CVE-2020-25039 CVE-2020-25040
Closes: #970465
  - Version 3.6.4 addresses CVE-2020-15229
Closes: #972212
   * Versioned (Build-)Depends: golang-github-blang-semver-dev (>= 4)
   * Versioned Build-Depends: golang-github-vbauerster-mpb-dev (>= 7.3.2)
   * Standards-Version: 4.6.0 (routine-update)
   * debhelper-compat 13 (routine-update)
   * Rules-Requires-Root: no (routine-update)
   * Use secure URI in Homepage field.
   * Update renamed lintian tag names in lintian overrides.
   * Use default salsa-ci pipeline
   * Bump github.com/vbauerster/mpb to v7
   * Drop Dave Love from Uploaders (Thanks a lot for your initial work Dave)
   * Versioned Build-Depends: golang-github-appc-cni-dev (>= 1.0.1~)
   * Do not try to `chown -c root.root` which is not permitted and granted
 in the final package anyway
   * Fix and simplify watch file
   * Replace 

Bug#970453: coq-float looks dead upstream: RM?

[Julien Puydt]

Hi,

I was looking around at all coq-related packages and found this poor
thing, which seems pretty dead.

I propose to ask for its removal ; I'll proceed in a few weeks if
nobody objects.

Cheers,

J.Puydt

Bug#1000336: numba: FTBFS with Python 3.10

[Drew Parsons]

Source: numba
Followup-For: Bug #1000336

onetbb is now building (in experimental) for all arches except
armel and armhf.

Is it worth at this point to make an upload of numba 0.55 to
experimental to check that it's building and passing tests for the
other arches?

Drew

Processed: severity of 1006017 is serious

[Debian Bug Tracking System]

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

> severity 1006017 serious
Bug #1006017 [playitslowly] playitslowly doesn't start (hasn't for awhile)
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#1006028: php-crypt-gpg: FTBFS: PHPUnit\Framework\Exception: PHP Fatal error: Uncaught Crypt_GPG_BadPassphraseException: Cannot export private key. Incorrect passphrase provided for keys: "First Ke

[Guilhem Moulin]

Control: tag -1 moreinfo

On Sat, 19 Feb 2022 at 07:38:04 +0100, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.

Seems like a false-positive to me.  It does build here, and also did
build on the buildds [0] (and Salsa CI too).  Perhaps that test is
unreliable though, in which case we should mark it as such or skip it.

> 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.

Attached diff for a local build (in minimal up to date sid chroot).

cheers
-- 
Guilhem.

[0] 
https://buildd.debian.org/status/fetch.php?pkg=php-crypt-gpg=all=1.6.7-1=1645097644=0
--- a/php-crypt-gpg_1.6.7-1_unstable.log
+++ b/php-crypt-gpg_1.6.7-1_amd64.build
@@ -1,10 +1,7 @@
-DC-Build-Header: php-crypt-gpg 1.6.7-1 / 2022-02-18 20:43:39 +
-DC-Task: type:rebuild-full source:php-crypt-gpg version:1.6.7-1 chroot:unstable esttime:127 logfile:/tmp/php-crypt-gpg_1.6.7-1_unstable.log modes:
-DC-Sbuild-call: su user42 -c 'sbuild -n -A -s --force-orig-source --apt-update -d unstable -v --no-run-lintian php-crypt-gpg_1.6.7-1'
-sbuild (Debian sbuild) 0.81.2 (31 January 2021) on ip-10-84-234-189.eu-central-1.compute.internal
+sbuild (Debian sbuild) 0.83.0 (05 February 2022) on odin.guilhem.org
 
 +==+
-| php-crypt-gpg 1.6.7-1 (amd64)Fri, 18 Feb 2022 20:43:39 + |
+| php-crypt-gpg 1.6.7-1 (amd64)Sat, 19 Feb 2022 09:58:33 + |
 +==+
 
 Package: php-crypt-gpg
@@ -16,17 +13,17 @@
 Build Architecture: amd64
 Build Type: full
 
-I: NOTICE: Log filtering will replace 'var/run/schroot/mount/sid-amd64-sbuild-95c36d99-de34-45d8-b2a5-0d1225712452' with '<>'
-I: NOTICE: Log filtering will replace 'build/php-crypt-gpg-pcurml/resolver-oJHJ6s' with '<>'
+I: 06ccache-tmpfs: Set cache size limit to 4.0 GB
+I: NOTICE: Log filtering will replace 'var/run/schroot/mount/sid-amd64-sbuild-c5e0e4c5-4fd3-4b24-b403-023f18c87b99' with '<>'
+I: NOTICE: Log filtering will replace 'build/php-crypt-gpg-ToTA24/resolver-tqhfbu' with '<>'
 
 +--+
 | Update chroot|
 +--+
 
-Hit:1 http://127.0.0.1:12990/debian sid InRelease
-Reading package lists...
 Reading package lists...
 Building dependency tree...
+Reading state information...
 Calculating upgrade...
 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
 
@@ -35,28 +32,12 @@
 +--+
 
 
-Check APT
--
-
-Checking available source versions...
-
-Download source files with APT
---
+Local sources
+-
 
-Reading package lists...
-NOTICE: 'php-crypt-gpg' packaging is maintained in the 'Git' version control system at:
-https://salsa.debian.org/php-team/pear/php-crypt-gpg.git -b debian/latest
-Please use:
-git clone https://salsa.debian.org/php-team/pear/php-crypt-gpg.git -b debian/latest
-to retrieve the latest (possibly unreleased) updates to the package.
-Need to get 353 kB of source archives.
-Get:1 http://127.0.0.1:12990/debian sid/main php-crypt-gpg 1.6.7-1 (dsc) [2244 B]
-Get:2 http://127.0.0.1:12990/debian sid/main php-crypt-gpg 1.6.7-1 (tar) [344 kB]
-Get:3 http://127.0.0.1:12990/debian sid/main php-crypt-gpg 1.6.7-1 (diff) [6580 B]
-Fetched 353 kB in 0s (6614 kB/s)
-Download complete and in download only mode
-I: NOTICE: Log filtering will replace 'build/php-crypt-gpg-pcurml/php-crypt-gpg-1.6.7' with '<>'
-I: NOTICE: Log filtering will replace 'build/php-crypt-gpg-pcurml' with '<>'
+/tmp/php-crypt-gpg_1.6.7-1.dsc exists in /tmp; copying to chroot
+I: NOTICE: Log filtering will replace 'build/php-crypt-gpg-ToTA24/php-crypt-gpg-1.6.7' with '<>'
+I: NOTICE: Log filtering will replace 'build/php-crypt-gpg-ToTA24' with '<>'
 
 +--+
 | Install package build dependencies   |
@@ -74,7 +55,7 @@
 Ign:3 copy:/<>/apt_archive ./ Release.gpg
 Get:4 copy:/<>/apt_archive ./ Sources [441 B]
 Get:5 copy:/<>/apt_archive ./ Packages [510 B]
-Fetched 1908 B in 0s (141 kB/s)
+Fetched 1908 B in 0s (0 B/s)
 Reading package lists...
 Reading package lists...
 
@@ -84,494 +65,481 @@
 Installing build dependencies
 Reading package lists...
 Building dependency tree...
+Reading state information...
 The following additional packages will be installed:
   autoconf automake autopoint autotools-dev bsdextrautils debhelper
   dh-autoreconf dh-strip-nondeterminism dwz file gettext gettext-base gpg
   gpg-agent gpgconf groff-base intltool-debian 

Processed: Re: Bug#1006028: php-crypt-gpg: FTBFS: PHPUnit\Framework\Exception: PHP Fatal error: Uncaught Crypt_GPG_BadPassphraseException: Cannot export private key. Incorrect passphrase provided for

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #1006028 [src:php-crypt-gpg] php-crypt-gpg: FTBFS: 
PHPUnit\Framework\Exception: PHP Fatal error: Uncaught 
Crypt_GPG_BadPassphraseException: Cannot export private key. Incorrect 
passphrase provided for keys: "First Keypair Test Key (do not encrypt important 
data with this key) ", 
"F27FB97E211A40BDD61FAD75E7493277280054C4", "First Keypair Test Key (do not 
encrypt important data with this key) ". in 
/<>/Crypt_GPG-1.6.7/Crypt/GPG/ProcessHandler.php on line 634
Added tag(s) moreinfo.

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

Bug#1006110: graphicsmagick: FTBFS on mipsel: test failure

[Sebastian Ramacher]

Source: graphicsmagick
Version: 1.4+really1.3.37+hg16662-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

graphicsmagick FTBFS on mipsel:

PASS: tests/rwfile.tap 629 - WEBP bilevel (lossless)
PASS: tests/rwfile.tap 630 - WEBP gray (lossless)
PASS: tests/rwfile.tap 631 - WEBP pallette (lossless)
FAIL: tests/rwfile.tap 632 - WEBP truecolor (lossless)
PASS: tests/rwfile.tap 633 - XBM bilevel
PASS: tests/rwfile.tap 634 - XBM bilevel (stdio)
PASS: tests/rwfile.tap 635 - XBM gray
PASS: tests/rwfile.tap 636 - XBM gray (stdio)

...


Testsuite summary for GraphicsMagick 1.4

# TOTAL: 1477
# PASS:  1427
# SKIP:  49
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0



See
https://buildd.debian.org/status/fetch.php?pkg=graphicsmagick=mipsel=1.4%2Breally1.3.37%2Bhg16662-1%2Bb1=1645260186=0

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#1006061: marked as done (node-deep-for-each: FTBFS: Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './lib/module-transformations' is not defined by "exports" in /usr/share/nodejs/@babel/pr

[Debian Bug Tracking System]

Your message dated Sat, 19 Feb 2022 09:04:21 +
with message-id 
and subject line Bug#1006061: fixed in node-babel7 7.17.4+~cs214.260.190-2
has caused the Debian Bug report #1006061,
regarding node-deep-for-each: FTBFS: Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: 
Package subpath './lib/module-transformations' is not defined by "exports" in 
/usr/share/nodejs/@babel/preset-env/package.json
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.)


-- 
1006061: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006061
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-deep-for-each
Version: 3.0.0-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> BABEL_ENV=commonjs babeljs-7 --presets '@babel/preset-env' --plugins 
> 'babel-plugin-add-module-exports' src -d lib
> Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath 
> './lib/module-transformations' is not defined by "exports" in 
> /usr/share/nodejs/@babel/preset-env/package.json
> at throwExportsNotFound (internal/modules/esm/resolve.js:299:9)
> at packageExportsResolve (internal/modules/esm/resolve.js:522:3)
> at resolveExports (internal/modules/cjs/loader.js:424:36)
> at Function.Module._findPath (internal/modules/cjs/loader.js:464:31)
> at Function.Module._resolveFilename 
> (internal/modules/cjs/loader.js:802:27)
> at Function.Module._load (internal/modules/cjs/loader.js:667:27)
> at Module.require (internal/modules/cjs/loader.js:887:19)
> at require (internal/modules/cjs/helpers.js:74:18)
> at Object. (/usr/share/nodejs/babel-preset-moxy/lib.js:3:31)
> at Module._compile (internal/modules/cjs/loader.js:999:30) {
>   code: 'ERR_PACKAGE_PATH_NOT_EXPORTED'
> }
> make[1]: *** [debian/rules:10: override_dh_auto_build] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/02/18/node-deep-for-each_3.0.0-3_unstable.log

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-babel7
Source-Version: 7.17.4+~cs214.260.190-2
Done: Yadd 

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-babel7 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 19 Feb 2022 09:24:48 +0100
Source: node-babel7
Architecture: source
Version: 7.17.4+~cs214.260.190-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 1006061
Changes:
 node-babel7 (7.17.4+~cs214.260.190-2) unstable; urgency=medium
 .
   * Team upload
   * Fix CRLF/LF by removing .gitattributes, thanks to Jochen Spricherhof
   * Allow babel-preset-moxy to require 
@babel/preset-env/lib/module-transformations
 (Closes: #1006061)
Checksums-Sha1: 
 5b2fc36cf4bee8ef08e049eab956afe9d1a1a865 20202 
node-babel7_7.17.4+~cs214.260.190-2.dsc
 7ceab635e4716879df7892c8506ad933d8ffa291 234192 
node-babel7_7.17.4+~cs214.260.190-2.debian.tar.xz
Checksums-Sha256: 
 a4221c302830a1a67b29790469268c071d2ff3f9d804e7e39cf712288f06f982 20202 
node-babel7_7.17.4+~cs214.260.190-2.dsc
 c35d2f75e39651fc57aee7c2077e6d818671f4f7d224f9835b532b85fd214e1c 234192 
node-babel7_7.17.4+~cs214.260.190-2.debian.tar.xz
Files: 
 b68e4b295f971bd44efb809e3c6d1445 20202 javascript optional 
node-babel7_7.17.4+~cs214.260.190-2.dsc
 6849c27bcc47ecad7db56438ab0ec07c 234192 javascript optional 
node-babel7_7.17.4+~cs214.260.190-2.debian.tar.xz

-BEGIN PGP 

Bug#1005981: Please migrate away from dpatch

[Moritz Muehlenhoff]

On Fri, Feb 18, 2022 at 02:41:57PM -0800, Bill Poser wrote:
> I am the developer of redet. I don't understand this bug report. redet does
> not use anything called dpatch so far as I know. Is this something added in
> the Debianization of redet downstream from me?

Yes, exactly. It's a legacy mechanism in Debian to apply patches to an
upstream codebase.

Cheers,
Moritz

Bug#1006061: marked as pending in node-babel

[Yadd]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/js-team/node-babel/-/commit/f9ca78cbfa8e386776fcf0fe6d6dffe59fcdc4a0


Allow babel-preset-moxy to require @babel/preset-env/lib/module-transformations

Closes: #1006061


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1006061

Processed: Bug#1006061 marked as pending in node-babel

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1006061 [node-jest-debbundle] node-deep-for-each: FTBFS: Error 
[ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './lib/module-transformations' 
is not defined by "exports" in /usr/share/nodejs/@babel/preset-env/package.json
Added tag(s) pending.

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

Bug#1006014: [Pkg-freeipa-devel] Bug#1006014: FTBFS: void value not ignored as it ought to be

[Timo Aaltonen]

Ryan Tandy kirjoitti 19.2.2022 klo 0.46:

Source: bind-dyndb-ldap
Version: 11.9-4
Severity: serious
Tags: ftbfs

Dear Maintainer,

bind-dyndb-ldap fails to build from source on amd64:

/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I../../src -I..   
-Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra -Werror -std=gnu99 -O2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wno-uninitialized -fvisibility=hidden 
-fno-delete-null-pointer-checks -c -o ldap_la-acl.lo `test -f 'acl.c' || echo 
'../../src/'`acl.c
In file included from ../../src/fwd_register.h:11,
  from ../../src/ldap_entry.h:11,
  from ../../src/acl.h:10,
  from ../../src/acl.c:32:
../../src/acl.c: In function ‘acl_configure_zone_ssutable’:
../../src/util.h:29:24: error: void value not ignored as it ought to be
29 | result = (op);  \
   |^
../../src/acl.c:286:9: note: in expansion of macro ‘CHECK’
   286 | CHECK(dns_ssutable_create(mctx, ));
   | ^
../../src/acl.c:328:24: error: void value not ignored as it ought to be
   328 | result = dns_ssutable_addrule(table, grant,
   |^
make[3]: *** [Makefile:542: ldap_la-acl.lo] Error 1

This looks like it could be caused by a recent change in bind9:

https://gitlab.isc.org/isc-projects/bind9/-/commit/8fb4c5bb7a703e7c174ccd13b2ede618696af69c

The complete build log is attached.

Thank you,
Ryan


Yes, known upstream and not fixed yet:

https://pagure.io/bind-dyndb-ldap/pull-request/212



--
t

Bug#1006079: marked as done (node-ipaddr.js: FTBFS: Unable to parse '' at /usr/share/perl5/Debian/Dependency.pm line 356.)

[Debian Bug Tracking System]

Your message dated Sat, 19 Feb 2022 08:37:54 +
with message-id 
and subject line Bug#1006079: fixed in node-ipaddr.js 2.0.1~dfsg-3
has caused the Debian Bug report #1006079,
regarding node-ipaddr.js: FTBFS: Unable to parse '' at 
/usr/share/perl5/Debian/Dependency.pm line 356.
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.)


-- 
1006079: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006079
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-ipaddr.js
Version: 2.0.1~dfsg-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> cd lib && terser -o ../debian/ipaddr.min.js ipaddr.js
> make[1]: Leaving directory '/<>'
>dh_auto_test --buildsystem=nodejs
>   mkdir -p node_modules
>   ln -s ../. node_modules/ipaddr.js
>   /bin/sh -ex debian/tests/pkg-js/test
> + mocha
> 
> 
>   ipaddr
> undefined should define main classes
> undefined can construct IPv4 from octets
> undefined refuses to construct invalid IPv4
> undefined converts IPv4 to string correctly
> undefined returns correct kind for IPv4
> undefined allows to access IPv4 octets
> undefined checks IPv4 address format
> undefined validates IPv4 addresses
> undefined parses IPv4 in several weird formats
> undefined barfs at invalid IPv4
> undefined matches IPv4 CIDR correctly
> undefined parses CIDR reversible
> undefined parses IPv4 CIDR correctly
> undefined detects reserved IPv4 networks
> undefined checks the conventional IPv4 address format
> undefined refuses to construct IPv4 address with trailing and leading 
> zeros
> undefined can construct IPv6 from 16bit parts
> undefined can construct IPv6 from 8bit parts
> undefined refuses to construct invalid IPv6
> undefined converts IPv6 to string correctly
> undefined converts IPv6 to RFC 5952 string correctly
> undefined returns IPv6 zoneIndex
> undefined returns IPv6 zoneIndex for IPv4-mapped IPv6 addresses
> undefined returns correct kind for IPv6
> undefined allows to access IPv6 address parts
> undefined checks IPv6 address format
> undefined validates IPv6 addresses
> undefined parses IPv6 in different formats
> undefined barfs at invalid IPv6
> undefined matches IPv6 CIDR correctly
> undefined parses IPv6 CIDR correctly
> undefined converts between IPv4-mapped IPv6 addresses and IPv4 addresses
> undefined refuses to convert non-IPv4-mapped IPv6 address to IPv4 address
> undefined detects reserved IPv6 networks
> undefined is able to determine IP address type
> undefined throws an error if tried to parse an invalid address
> undefined correctly processes IPv4-mapped addresses
> undefined correctly converts IPv6 and IPv4 addresses to byte arrays
> undefined correctly parses 1 as an IPv4 address
> undefined correctly detects IPv4 and IPv6 CIDR addresses
> undefined does not consider a very large or very small number a valid IP 
> address
> undefined does not hang on ::8:8:8:8:8:8:8:8:8
> undefined subnetMatch does not fail on empty range
> undefined subnetMatch returns default subnet on empty range
> undefined subnetMatch does not fail on IPv4 when looking for IPv6
> undefined subnetMatch does not fail on IPv6 when looking for IPv4
> undefined subnetMatch can use a hybrid IPv4/IPv6 range list
> undefined is able to determine IP address type from byte array input
> undefined prefixLengthFromSubnetMask returns proper CIDR notation for 
> standard IPv4 masks
> undefined prefixLengthFromSubnetMask returns proper CIDR notation for 
> standard IPv6 masks
> undefined subnetMaskFromPrefixLength returns correct IPv4 subnet mask 
> given prefix length
> undefined subnetMaskFromPrefixLength returns correct IPv6 subnet mask 
> given prefix length
> undefined broadcastAddressFromCIDR returns correct IPv4 broadcast address
> undefined networkAddressFromCIDR returns correct IPv4 network address
> undefined networkAddressFromCIDR returns correct IPv6 network address
> undefined broadcastAddressFromCIDR returns correct IPv6 broadcast address
> 
> 
>   56 passing (31ms)
> 
> Removing node_modules/ipaddr.js
>create-stamp debian/debhelper-build-stamp
>dh_prep
>dh_auto_install --buildsystem=nodejs
> dh_auto_install: warning: ./package.json#files: ipaddr.min.js does not exists
> 
> 

Bug#1006077: marked as done (node-dabh-diagnostics: FTBFS: Unable to parse '' at /usr/share/perl5/Debian/Dependency.pm line 356.)

[Debian Bug Tracking System]

Your message dated Sat, 19 Feb 2022 08:37:25 +
with message-id 
and subject line Bug#1006077: fixed in node-dabh-diagnostics 2.0.2-5
has caused the Debian Bug report #1006077,
regarding node-dabh-diagnostics: FTBFS: Unable to parse '' at 
/usr/share/perl5/Debian/Dependency.pm line 356.
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.)


-- 
1006077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006077
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-dabh-diagnostics
Version: 2.0.2-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
>  fakeroot debian/rules binary
> dh binary --with nodejs
>dh_testroot
>dh_prep
>dh_auto_install --buildsystem=nodejs 
> --destdir=debian/node-dabh-diagnostics/
> dh_auto_install: warning: ### Missing ./logs, skipping
> 
> dh_auto_install: warning: ### Missing ./pids, skipping
> 
> dh_auto_install: warning: ### Missing ./lib-cov, skipping
> 
> dh_auto_install: warning: ### Missing ./coverage, skipping
> 
> dh_auto_install: warning: ### Missing ./.nyc_output, skipping
> 
> dh_auto_install: warning: ### Missing ./.grunt, skipping
> 
> dh_auto_install: warning: ### Missing ./bower_components, skipping
> 
> dh_auto_install: warning: ### Missing ./.lock-wscript, skipping
> 
> dh_auto_install: warning: ### Missing ./build/Release, skipping
> 
> dh_auto_install: warning: ### Missing ./node_modules/, skipping
> 
> dh_auto_install: warning: ### Missing ./jspm_packages/, skipping
> 
> dh_auto_install: warning: ### Missing ./typings/, skipping
> 
> dh_auto_install: warning: ### Missing ./.npm, skipping
> 
> dh_auto_install: warning: ### Missing ./.eslintcache, skipping
> 
> dh_auto_install: warning: ### Missing ./.node_repl_history, skipping
> 
> dh_auto_install: warning: ### Missing ./.yarn-integrity, skipping
> 
> dh_auto_install: warning: ### Missing ./.env, skipping
> 
> dh_auto_install: warning: ### Missing ./.env.test, skipping
> 
> dh_auto_install: warning: ### Missing ./.cache, skipping
> 
> dh_auto_install: warning: ### Missing ./.next, skipping
> 
> dh_auto_install: warning: ### Missing ./.nuxt, skipping
> 
> dh_auto_install: warning: ### Missing ./.vuepress/dist, skipping
> 
> dh_auto_install: warning: ### Missing ./.serverless/, skipping
> 
> dh_auto_install: warning: ### Missing ./.fusebox/, skipping
> 
> dh_auto_install: warning: ### Missing ./.dynamodb/, skipping
> 
> dh_auto_install: warning: ### Missing ./dist, skipping
> 
> No "files" field in ./package.json, install all files
> Files to install: ., !./logs, !./*.log, !./npm-debug.log*, 
> !./yarn-debug.log*, !./yarn-error.log*, !./pids, !./*.pid, !./*.seed, 
> !./*.pid.lock, !./lib-cov, !./coverage, !./.nyc_output, !./.grunt, 
> !./bower_components, !./.lock-wscript, !./build/Release, !./node_modules/, 
> !./jspm_packages/, !./typings/, !./.npm, !./.eslintcache, 
> !./.node_repl_history, !./*.tgz, !./.yarn-integrity, !./.env, !./.env.test, 
> !./.cache, !./.next, !./.nuxt, !./.vuepress/dist, !./.serverless/, 
> !./.fusebox/, !./.dynamodb/, !./test, !./dist, !./.travis.yml, !./example.js
> Parsing expression ./*.log
> Line ./*.log becomes: ^./[^/]*\.log$
> Parsing expression ./npm-debug.log*
> Line ./npm-debug.log* becomes: ^./npm\-debug\.log[^/]*$
> Parsing expression ./yarn-debug.log*
> Line ./yarn-debug.log* becomes: ^./yarn\-debug\.log[^/]*$
> Parsing expression ./yarn-error.log*
> Line ./yarn-error.log* becomes: ^./yarn\-error\.log[^/]*$
> Parsing expression ./*.pid
> Line ./*.pid becomes: ^./[^/]*\.pid$
> Parsing expression ./*.seed
> Line ./*.seed becomes: ^./[^/]*\.seed$
> Parsing expression ./*.pid.lock
> Line ./*.pid.lock becomes: ^./[^/]*\.pid\.lock$
> Parsing expression ./*.tgz
> Line ./*.tgz becomes: ^./[^/]*\.tgz$
>   mkdir -p 
> /<>/debian/node-dabh-diagnostics//usr/share/nodejs/diagnostics/
>   install -m 644 ./diagnostics.js 
> /<>/debian/node-dabh-diagnostics//usr/share/nodejs/diagnostics//
>   install -m 644 ./package.json 
> /<>/debian/node-dabh-diagnostics//usr/share/nodejs/diagnostics//
>   install -m 644 ./example.png 
> /<>/debian/node-dabh-diagnostics//usr/share/nodejs/diagnostics//
>   mkdir -p 
> /<>/debian/node-dabh-diagnostics//usr/share/nodejs/diagnostics/adapters
>   install -m 644 ./adapters/asyncstorage.js 
> /<>/debian/node-dabh-diagnostics//usr/share/nodejs/diagnostics/adapters/
>   install -m 644 ./adapters/index.js 
> 

Bug#1006076: marked as done (node-kuler: FTBFS: Unable to parse '' at /usr/share/perl5/Debian/Dependency.pm line 356.)

[Debian Bug Tracking System]

Your message dated Sat, 19 Feb 2022 08:37:59 +
with message-id 
and subject line Bug#1006076: fixed in node-kuler 2.0.0-3
has caused the Debian Bug report #1006076,
regarding node-kuler: FTBFS: Unable to parse '' at 
/usr/share/perl5/Debian/Dependency.pm line 356.
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.)


-- 
1006076: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006076
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-kuler
Version: 2.0.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
>  fakeroot debian/rules binary
> dh binary --with nodejs
>dh_testroot
>dh_prep
>dh_auto_install --buildsystem=nodejs --destdir=debian/node-kuler/
> dh_auto_install: warning: ### Missing ./build/config.gypi, skipping
> 
> No "files" field in ./package.json, install all files
> Files to install: ., !./build/config.gypi
>   mkdir -p /<>/debian/node-kuler//usr/share/nodejs/kuler/
>   install -m 644 ./package.json 
> /<>/debian/node-kuler//usr/share/nodejs/kuler//
>   install -m 644 ./index.js 
> /<>/debian/node-kuler//usr/share/nodejs/kuler//
>   install -m 644 ./package.json 
> /<>/debian/node-kuler//usr/share/nodejs/kuler//
> Unable to parse '' at /usr/share/perl5/Debian/Dependency.pm line 356.
> make: *** [debian/rules:8: binary] Error 255


The full build log is available from:
http://qa-logs.debian.net/2022/02/18/node-kuler_2.0.0-2_unstable.log

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-kuler
Source-Version: 2.0.0-3
Done: Yadd 

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-kuler package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 19 Feb 2022 09:02:33 +0100
Source: node-kuler
Architecture: source
Version: 2.0.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 1006076
Changes:
 node-kuler (2.0.0-3) unstable; urgency=medium
 .
   * Team upload
 .
   [ lintian-brush ]
   * Trim trailing whitespace.
   * Bump debhelper from old 11 to 13.
   * Set upstream metadata fields: Bug-Submit.
   * Remove obsolete fields Contact, Name from debian/upstream/metadata
 (already present in machine-readable debian/copyright)
 .
   [ Yadd ]
   * Update standards version to 4.6.0, no changes needed.
   * Add "Rules-Requires-Root: no"
   * Use dh-sequence-nodejs instead of pkg-js-tools
   * Fix debian/control for Debian::Control (Closes: #1006076)
Checksums-Sha1: 
 e74741e66a375ff02cf99dcb065ae11dd97605fe 2004 node-kuler_2.0.0-3.dsc
 0351ea41db7b86213c9a907b044fa7107279640b 2628 node-kuler_2.0.0-3.debian.tar.xz
Checksums-Sha256: 
 44ff76b31261fc96922b185c2fde58a8527e3bd1bee4bf335692e0ff780cb029 2004 
node-kuler_2.0.0-3.dsc
 6c90ded242b7c8c5ae9d8d0bc5c3a07c65d5e9ee47743cc81420a3d1bed233c9 2628 
node-kuler_2.0.0-3.debian.tar.xz
Files: 
 92fdf770e9fe9a5d1753c580266c662c 2004 javascript optional 
node-kuler_2.0.0-3.dsc
 c5433941ad2c96783ab956cf71c329b2 2628 javascript optional 
node-kuler_2.0.0-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmIQpIsACgkQ9tdMp8mZ
7ummexAAiZFhSgX+2cKkwDF768PN9fM+T/CwuRHvg0wLqSGvH8cwgy0Wx9WN6KwR
h7Gke7B5lZWwm0BcGh/4Wz3vLgf5LzF2XdJnSirfT3EXLkGVt9AihbAieEbrIVoo
UmZ/nwjlwhfmQTvpjl7gu5VFN6KjycCVIchxjHwDk9HInTflTMDX1UHoMX6n/+AK
bTzvfXKtcfJ7VqgzsEhUO943L7ckhCyZ/qPmaml9LFiwvfIYFSwOWVIf0m8xjWSR

Bug#1006075: marked as done (node-err-code: FTBFS: Unable to parse '' at /usr/share/perl5/Debian/Dependency.pm line 356.)

[Debian Bug Tracking System]

Your message dated Sat, 19 Feb 2022 08:37:31 +
with message-id 
and subject line Bug#1006075: fixed in node-err-code 2.0.3+dfsg-3
has caused the Debian Bug report #1006075,
regarding node-err-code: FTBFS: Unable to parse '' at 
/usr/share/perl5/Debian/Dependency.pm line 356.
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.)


-- 
1006075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006075
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-err-code
Version: 2.0.3+dfsg-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

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
> browserify-lite --standalone err-code ./index.js --outfile index.umd.js
> make[1]: Leaving directory '/<>'
>dh_auto_test --buildsystem=nodejs
>   mkdir -p node_modules
>   ln -s ../. node_modules/err-code
>   /bin/sh -ex debian/tests/pkg-js/test
> + mocha -R spec --bail
> 
> 
>   errcode
> string as first argument
>   undefined should throw an error
> error as first argument
>   undefined should accept an error and do nothing
>   undefined should accept an error and add a code
>   undefined should accept an error object and add code & properties
>   undefined should create an error object without code but with properties
>   undefined should set a non-writable field
>   undefined should add a code to frozen object
>   undefined should to set a field that throws at assignment time
>   undefined should retain error type
>   undefined should add a code to a class that extends Error
>   undefined should support errors that are not Errors
> falsy first arguments
>   undefined should not allow passing null as the first argument
>   undefined should not allow passing undefined as the first argument
> 
> 
>   13 passing (45ms)
> 
> Removing node_modules/err-code
>create-stamp debian/debhelper-build-stamp
>dh_prep
>dh_auto_install --buildsystem=nodejs --destdir=debian/node-err-code/
> dh_auto_install: warning: ### Missing ./build/config.gypi, skipping
> 
> No "files" field in ./package.json, install all files
> Files to install: ., !./build/config.gypi
>   mkdir -p 
> /<>/node-err-code-2.0.3\+dfsg/debian/node-err-code//usr/share/nodejs/err-code/
>   install -m 644 ./package.json 
> /<>/node-err-code-2.0.3\+dfsg/debian/node-err-code//usr/share/nodejs/err-code//
>   install -m 644 ./index.js 
> /<>/node-err-code-2.0.3\+dfsg/debian/node-err-code//usr/share/nodejs/err-code//
>   install -m 644 ./index.umd.js 
> /<>/node-err-code-2.0.3\+dfsg/debian/node-err-code//usr/share/nodejs/err-code//
>   install -m 644 ./package.json 
> /<>/node-err-code-2.0.3\+dfsg/debian/node-err-code//usr/share/nodejs/err-code//
> Unable to parse '' at /usr/share/perl5/Debian/Dependency.pm line 356.
> make: *** [debian/rules:8: binary] Error 255


The full build log is available from:
http://qa-logs.debian.net/2022/02/18/node-err-code_2.0.3+dfsg-2_unstable.log

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-err-code
Source-Version: 2.0.3+dfsg-3
Done: Yadd 

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-err-code package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 19 Feb 2022 08:45:08 +0100
Source: node-err-code
Architecture: source
Version: 2.0.3+dfsg-3
Distribution: unstable
Urgency: medium

Bug#1006071: marked as done (node-autoprefixer: FTBFS: Unable to parse '' at /usr/share/perl5/Debian/Dependency.pm line 356.)

[Debian Bug Tracking System]

Your message dated Sat, 19 Feb 2022 08:37:00 +
with message-id 
and subject line Bug#1006071: fixed in node-autoprefixer 
10.4.2.0+dfsg1+~cs24.7.3-2
has caused the Debian Bug report #1006071,
regarding node-autoprefixer: FTBFS: Unable to parse '' at 
/usr/share/perl5/Debian/Dependency.pm line 356.
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.)


-- 
1006071: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006071
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-autoprefixer
Version: 10.4.2.0+dfsg1+~cs24.7.3-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

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_install --buildsystem=nodejs
> dh_auto_install: warning: ### Missing autoprefixer/coverage/, skipping
> 
> Found debian/nodejs/additional_components
> Adding component(s): build
> No "files" field in autoprefixer/package.json, install all files
> Files to install: autoprefixer, !autoprefixer/test/, !autoprefixer/coverage/, 
> !autoprefixer/logo.svg, !autoprefixer/AUTHORS
>   mkdir -p 
> /<>/node-autoprefixer-10.4.2.0\+dfsg1\+\~cs24.7.3/debian/tmp//usr/share/nodejs/autoprefixer/
>   install -m 644 autoprefixer/package.json 
> /<>/node-autoprefixer-10.4.2.0\+dfsg1\+\~cs24.7.3/debian/tmp//usr/share/nodejs/autoprefixer//
>   install -m 644 autoprefixer/pnpm-lock.yaml 
> /<>/node-autoprefixer-10.4.2.0\+dfsg1\+\~cs24.7.3/debian/tmp//usr/share/nodejs/autoprefixer//
>   mkdir -p 
> /<>/node-autoprefixer-10.4.2.0\+dfsg1\+\~cs24.7.3/debian/tmp//usr/share/nodejs/autoprefixer/lib
>   install -m 644 autoprefixer/lib/utils.js 
> /<>/node-autoprefixer-10.4.2.0\+dfsg1\+\~cs24.7.3/debian/tmp//usr/share/nodejs/autoprefixer/lib/
>   install -m 644 autoprefixer/lib/at-rule.js 
> /<>/node-autoprefixer-10.4.2.0\+dfsg1\+\~cs24.7.3/debian/tmp//usr/share/nodejs/autoprefixer/lib/
>   install -m 644 autoprefixer/lib/processor.js 
> /<>/node-autoprefixer-10.4.2.0\+dfsg1\+\~cs24.7.3/debian/tmp//usr/share/nodejs/autoprefixer/lib/
>   install -m 644 autoprefixer/lib/supports.js 
> /<>/node-autoprefixer-10.4.2.0\+dfsg1\+\~cs24.7.3/debian/tmp//usr/share/nodejs/autoprefixer/lib/
>   install -m 644 autoprefixer/lib/autoprefixer.js 
> /<>/node-autoprefixer-10.4.2.0\+dfsg1\+\~cs24.7.3/debian/tmp//usr/share/nodejs/autoprefixer/lib/
>   install -m 644 autoprefixer/lib/declaration.js 
> /<>/node-autoprefixer-10.4.2.0\+dfsg1\+\~cs24.7.3/debian/tmp//usr/share/nodejs/autoprefixer/lib/
>   install -m 644 autoprefixer/lib/vendor.js 
> /<>/node-autoprefixer-10.4.2.0\+dfsg1\+\~cs24.7.3/debian/tmp//usr/share/nodejs/autoprefixer/lib/
>   install -m 644 autoprefixer/lib/old-selector.js 
> /<>/node-autoprefixer-10.4.2.0\+dfsg1\+\~cs24.7.3/debian/tmp//usr/share/nodejs/autoprefixer/lib/
>   install -m 644 autoprefixer/lib/prefixes.js 
> /<>/node-autoprefixer-10.4.2.0\+dfsg1\+\~cs24.7.3/debian/tmp//usr/share/nodejs/autoprefixer/lib/
>   install -m 644 autoprefixer/lib/autoprefixer.d.ts 
> /<>/node-autoprefixer-10.4.2.0\+dfsg1\+\~cs24.7.3/debian/tmp//usr/share/nodejs/autoprefixer/lib/
>   install -m 644 autoprefixer/lib/brackets.js 
> /<>/node-autoprefixer-10.4.2.0\+dfsg1\+\~cs24.7.3/debian/tmp//usr/share/nodejs/autoprefixer/lib/
>   install -m 644 autoprefixer/lib/transition.js 
> /<>/node-autoprefixer-10.4.2.0\+dfsg1\+\~cs24.7.3/debian/tmp//usr/share/nodejs/autoprefixer/lib/
>   install -m 644 autoprefixer/lib/browsers.js 
> /<>/node-autoprefixer-10.4.2.0\+dfsg1\+\~cs24.7.3/debian/tmp//usr/share/nodejs/autoprefixer/lib/
>   install -m 644 autoprefixer/lib/prefixer.js 
> /<>/node-autoprefixer-10.4.2.0\+dfsg1\+\~cs24.7.3/debian/tmp//usr/share/nodejs/autoprefixer/lib/
>   install -m 644 autoprefixer/lib/resolution.js 
> /<>/node-autoprefixer-10.4.2.0\+dfsg1\+\~cs24.7.3/debian/tmp//usr/share/nodejs/autoprefixer/lib/
>   install -m 644 autoprefixer/lib/selector.js 
> /<>/node-autoprefixer-10.4.2.0\+dfsg1\+\~cs24.7.3/debian/tmp//usr/share/nodejs/autoprefixer/lib/
>   install -m 644 autoprefixer/lib/value.js 
> /<>/node-autoprefixer-10.4.2.0\+dfsg1\+\~cs24.7.3/debian/tmp//usr/share/nodejs/autoprefixer/lib/
>   install -m 644 autoprefixer/lib/old-value.js 
> /<>/node-autoprefixer-10.4.2.0\+dfsg1\+\~cs24.7.3/debian/tmp//usr/share/nodejs/autoprefixer/lib/
>   install -m 644 autoprefixer/lib/info.js 
> /<>/node-autoprefixer-10.4.2.0\+dfsg1\+\~cs24.7.3/debian/tmp//usr/share/nodejs/autoprefixer/lib/
>   mkdir -p 
> 

Bug#1006074: marked as done (node-grunt-legacy-util: FTBFS: Unable to parse '' at /usr/share/perl5/Debian/Dependency.pm line 356.)

[Debian Bug Tracking System]

Your message dated Sat, 19 Feb 2022 08:37:48 +
with message-id 
and subject line Bug#1006074: fixed in node-grunt-legacy-util 2.0.1-2
has caused the Debian Bug report #1006074,
regarding node-grunt-legacy-util: FTBFS: Unable to parse '' at 
/usr/share/perl5/Debian/Dependency.pm line 356.
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.)


-- 
1006074: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006074
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-grunt-legacy-util
Version: 2.0.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
>   cd ./. && grunt
> Running "nodeunit:util" (nodeunit) task
> Testing index.jsOK
> >> 92 assertions passed (1788ms)
> 
> Done.
> Command "grunt" succeeded in .
>dh_auto_test --buildsystem=nodejs
>   mkdir -p node_modules
>   ln -s ../. node_modules/grunt-legacy-util
>   /bin/sh -ex debian/tests/pkg-js/test
> + grunt test
> Running "nodeunit:util" (nodeunit) task
> Testing index.jsOK
> >> 92 assertions passed (1877ms)
> 
> Done.
> Removing node_modules/grunt-legacy-util
>create-stamp debian/debhelper-build-stamp
>dh_prep
>dh_auto_install --buildsystem=nodejs 
> --destdir=debian/node-grunt-legacy-util/
> dh_auto_install: warning: ### Missing ./build/config.gypi, skipping
> 
> No "files" field in ./package.json, install all files
> Files to install: ., !./build/config.gypi
>   mkdir -p 
> /<>/debian/node-grunt-legacy-util//usr/share/nodejs/grunt-legacy-util/
>   install -m 644 ./package.json 
> /<>/debian/node-grunt-legacy-util//usr/share/nodejs/grunt-legacy-util//
>   install -m 644 ./index.js 
> /<>/debian/node-grunt-legacy-util//usr/share/nodejs/grunt-legacy-util//
>   install -m 644 ./package.json 
> /<>/debian/node-grunt-legacy-util//usr/share/nodejs/grunt-legacy-util//
> Unable to parse '' at /usr/share/perl5/Debian/Dependency.pm line 356.
> make: *** [debian/rules:8: binary] Error 255


The full build log is available from:
http://qa-logs.debian.net/2022/02/18/node-grunt-legacy-util_2.0.1-1_unstable.log

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-grunt-legacy-util
Source-Version: 2.0.1-2
Done: Yadd 

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-grunt-legacy-util package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 19 Feb 2022 08:57:27 +0100
Source: node-grunt-legacy-util
Architecture: source
Version: 2.0.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 1006074
Changes:
 node-grunt-legacy-util (2.0.1-2) unstable; urgency=medium
 .
   * Team upload
   * Fix debian/control for Debian::Control (Closes: #1006074)
Checksums-Sha1: 
 de0fa5914b092b9937cd848b81ec6942e2cb518e 2366 
node-grunt-legacy-util_2.0.1-2.dsc
 e680abc19e79c7477f3374a39cfc5510b128cafa 3476 
node-grunt-legacy-util_2.0.1-2.debian.tar.xz
Checksums-Sha256: 
 ceb7c3c946453a0ef72f1dbb0a50e0059f0f99247432da6c981de05cac67b2b0 2366 
node-grunt-legacy-util_2.0.1-2.dsc
 d37ee1353cc382194222d5d33df8b172054537b18403b3c86ccf7ac9782c5184 3476 

Bug#1006069: marked as done (node-browser-stdout: FTBFS: Unable to parse '' at /usr/share/perl5/Debian/Dependency.pm line 356.)

[Debian Bug Tracking System]

Your message dated Sat, 19 Feb 2022 08:37:05 +
with message-id 
and subject line Bug#1006069: fixed in node-browser-stdout 1.3.1-6
has caused the Debian Bug report #1006069,
regarding node-browser-stdout: FTBFS: Unable to parse '' at 
/usr/share/perl5/Debian/Dependency.pm line 356.
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.)


-- 
1006069: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006069
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-browser-stdout
Version: 1.3.1-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
>   mkdir -p node_modules
>   ln -s ../. node_modules/browser-stdout
>   /usr/bin/node -e require\(\"./.\"\)
> Removing node_modules/browser-stdout
>create-stamp debian/debhelper-build-stamp
>dh_prep
>dh_auto_install --buildsystem=nodejs --destdir=debian/node-browser-stdout/
> dh_auto_install: warning: ### Missing ./build/config.gypi, skipping
> 
> No "files" field in ./package.json, install all files
> Files to install: ., !./build/config.gypi
>   mkdir -p 
> /<>/debian/node-browser-stdout//usr/share/nodejs/browser-stdout/
>   install -m 644 ./package.json 
> /<>/debian/node-browser-stdout//usr/share/nodejs/browser-stdout//
>   install -m 644 ./index.js 
> /<>/debian/node-browser-stdout//usr/share/nodejs/browser-stdout//
>   install -m 644 ./package.json 
> /<>/debian/node-browser-stdout//usr/share/nodejs/browser-stdout//
> Unable to parse '' at /usr/share/perl5/Debian/Dependency.pm line 356.
> make: *** [debian/rules:8: binary] Error 255


The full build log is available from:
http://qa-logs.debian.net/2022/02/18/node-browser-stdout_1.3.1-5_unstable.log

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-browser-stdout
Source-Version: 1.3.1-6
Done: Yadd 

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-browser-stdout package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 19 Feb 2022 08:30:05 +0100
Source: node-browser-stdout
Architecture: source
Version: 1.3.1-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 1006069
Changes:
 node-browser-stdout (1.3.1-6) unstable; urgency=medium
 .
   * Team upload
   * Fix debian/control for Debian::Control (Closes: #1006069)
Checksums-Sha1: 
 20a7f3e7bbf065dc6b555c00c2a9421654a39076 2102 node-browser-stdout_1.3.1-6.dsc
 379794f1766cd15dde5cba70d561f5e738b16b6d 2544 
node-browser-stdout_1.3.1-6.debian.tar.xz
Checksums-Sha256: 
 de03e9a2ed41fa561971cee576865ea41339f6710080908c0328273203dc7715 2102 
node-browser-stdout_1.3.1-6.dsc
 43118ec5d2742a183d744d67000e1c872b05e63ff15e155c4bc35d43c6630efc 2544 
node-browser-stdout_1.3.1-6.debian.tar.xz
Files: 
 27def53d489fc3f86c2d04e8a72d80b0 2102 javascript optional 
node-browser-stdout_1.3.1-6.dsc
 2bf979687a8a8c18303a71d8c4cd70f6 2544 javascript optional 
node-browser-stdout_1.3.1-6.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmIQn0wACgkQ9tdMp8mZ
7uktWQ//UUeARVAMnWXEqhdTr8ZjLCsZ4c3L2NPutHz+Aq20BTH3CjoXW3HyHspc

Bug#1006067: marked as done (node-rai: FTBFS: Unable to parse '' at /usr/share/perl5/Debian/Dependency.pm line 356.)

[Debian Bug Tracking System]

Your message dated Sat, 19 Feb 2022 08:38:04 +
with message-id 
and subject line Bug#1006067: fixed in node-rai 0.1.12-7
has caused the Debian Bug report #1006067,
regarding node-rai: FTBFS: Unable to parse '' at 
/usr/share/perl5/Debian/Dependency.pm line 356.
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.)


-- 
1006067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006067
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-rai
Version: 0.1.12-6
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
>   mkdir -p node_modules
>   ln -s ../. node_modules/rai
>   /bin/sh -ex debian/tests/pkg-js/test
> + nodeunit test
> 
> rai
> ✔ General tests - Create and close a server
> ✔ General tests - Create a secure server
> ✔ General tests - Duplicate server fails
> ✔ General tests - Connection event
> ✔ General tests - Close client socket
> (node:207704) [DEP0005] DeprecationWarning: Buffer() is deprecated due to 
> security and usability issues. Please use the Buffer.alloc(), 
> Buffer.allocUnsafe(), or Buffer.from() methods instead.
> ✔ General tests - Send data to client
> ✔ Client commands - Receive Simple Command
> ✔ Client commands - Receive Command with payload
> ✔ Data mode - DATA mode
> ✔ Data mode - Small chunks DATA mode
> ✔ Pipelining support - Pipelining
> ✔ Client Mockup - All command
> ✔ Client Mockup - Last commands
> 
> OK: 32 assertions (56ms)
> Removing node_modules/rai
>create-stamp debian/debhelper-build-stamp
>dh_prep
>dh_auto_install --buildsystem=nodejs --destdir=debian/node-rai/
> No "files" field in ./package.json, install all files
> Files to install: ., !./test, !./examples
>   mkdir -p /<>/debian/node-rai//usr/share/nodejs/rai/
>   install -m 644 ./package.json 
> /<>/debian/node-rai//usr/share/nodejs/rai//
>   mkdir -p /<>/debian/node-rai//usr/share/nodejs/rai/lib
>   install -m 644 ./lib/rai.js 
> /<>/debian/node-rai//usr/share/nodejs/rai/lib/
>   install -m 644 ./lib/mockup.js 
> /<>/debian/node-rai//usr/share/nodejs/rai/lib/
>   install -m 644 ./lib/starttls.js 
> /<>/debian/node-rai//usr/share/nodejs/rai/lib/
>   mkdir -p /<>/debian/node-rai//usr/share/nodejs/rai/cert
>   install -m 644 ./cert/server.crt 
> /<>/debian/node-rai//usr/share/nodejs/rai/cert/
>   install -m 644 ./cert/server.key 
> /<>/debian/node-rai//usr/share/nodejs/rai/cert/
>   install -m 644 ./package.json 
> /<>/debian/node-rai//usr/share/nodejs/rai//
> Unable to parse '' at /usr/share/perl5/Debian/Dependency.pm line 356.
> make: *** [debian/rules:8: binary] Error 255


The full build log is available from:
http://qa-logs.debian.net/2022/02/18/node-rai_0.1.12-6_unstable.log

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-rai
Source-Version: 0.1.12-7
Done: Yadd 

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-rai package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 19 Feb 2022 09:01:46 +0100
Source: node-rai
Architecture: source
Version: 0.1.12-7
Distribution: unstable
Urgency: medium
Maintainer: Debian 

Bug#1006062: marked as done (node-grunt-contrib-nodeunit: FTBFS: Unable to parse '' at /usr/share/perl5/Debian/Dependency.pm line 356.)

[Debian Bug Tracking System]

Your message dated Sat, 19 Feb 2022 08:37:42 +
with message-id 
and subject line Bug#1006062: fixed in node-grunt-contrib-nodeunit 2.0.0-6
has caused the Debian Bug report #1006062,
regarding node-grunt-contrib-nodeunit: FTBFS: Unable to parse '' at 
/usr/share/perl5/Debian/Dependency.pm line 356.
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.)


-- 
1006062: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006062
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-grunt-contrib-nodeunit
Version: 2.0.0-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> # No test during build to avoid circular dependencies
> make[1]: Leaving directory '/<>'
>create-stamp debian/debhelper-build-stamp
>dh_prep
>dh_auto_install --buildsystem=nodejs 
> --destdir=debian/node-grunt-contrib-nodeunit/
> dh_auto_install: warning: ### Missing ./build/config.gypi, skipping
> 
> Found "files" field in ./package.json, using it
>   mkdir -p 
> /<>/debian/node-grunt-contrib-nodeunit//usr/share/nodejs/grunt-contrib-nodeunit/tasks
>   install -m 644 ./tasks/nodeunit.js 
> /<>/debian/node-grunt-contrib-nodeunit//usr/share/nodejs/grunt-contrib-nodeunit/tasks/
>   install -m 644 ./package.json 
> /<>/debian/node-grunt-contrib-nodeunit//usr/share/nodejs/grunt-contrib-nodeunit//
>   install -m 644 ./package.json 
> /<>/debian/node-grunt-contrib-nodeunit//usr/share/nodejs/grunt-contrib-nodeunit//
> Unable to parse '' at /usr/share/perl5/Debian/Dependency.pm line 356.
> make: *** [debian/rules:8: binary] Error 255


The full build log is available from:
http://qa-logs.debian.net/2022/02/18/node-grunt-contrib-nodeunit_2.0.0-5_unstable.log

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-grunt-contrib-nodeunit
Source-Version: 2.0.0-6
Done: Yadd 

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-grunt-contrib-nodeunit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 19 Feb 2022 08:56:30 +0100
Source: node-grunt-contrib-nodeunit
Architecture: source
Version: 2.0.0-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 1006062
Changes:
 node-grunt-contrib-nodeunit (2.0.0-6) unstable; urgency=medium
 .
   * Team upload
   * Fix d/control for Debian::Control (Closes: #1006062)
Checksums-Sha1: 
 9fbebe622a7c4618baa249caebde6a45f8790146 2329 
node-grunt-contrib-nodeunit_2.0.0-6.dsc
 72738db95b87d179fbfa386a8faecf6a7397abfb 4916 
node-grunt-contrib-nodeunit_2.0.0-6.debian.tar.xz
Checksums-Sha256: 
 88e99a59eeafed7f6c28e7dc2f7e248c5203354e8f4b7d47edde1aeccd07d973 2329 
node-grunt-contrib-nodeunit_2.0.0-6.dsc
 256b5f8d4a02d66bd6a9a010e72b83160ac98f2d0daf5b301912efbc2226a4b6 4916 
node-grunt-contrib-nodeunit_2.0.0-6.debian.tar.xz
Files: 
 b6c2d26a0c294f4edbb3102ec430f9aa 2329 javascript optional 
node-grunt-contrib-nodeunit_2.0.0-6.dsc
 01ce722e4c71c00180e1073b1895b81e 4916 javascript optional 
node-grunt-contrib-nodeunit_2.0.0-6.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmIQovwACgkQ9tdMp8mZ
7umoxBAAnlUH+5kb7u2yGSDkGU3j0yMZg8hLABMcERBxgV/YIblmRbxT0XoIQ67f
oyT/qII4/eK1ygoNFg/yGBJoJ/5iYb3A3ZRyrM55PeIkjplwNYF/AaHQAo/fTuYO
17TKRhLQepYdIU8xWTJ/rxSKhnrriZHdlcunXuJyV6g35mZNz6BxiOOGYR2p+qd5

Bug#1006057: marked as done (node-tildify: FTBFS: Unable to parse '' at /usr/share/perl5/Debian/Dependency.pm line 356.)

[Debian Bug Tracking System]

Your message dated Sat, 19 Feb 2022 08:38:10 +
with message-id 
and subject line Bug#1006057: fixed in node-tildify 2.0.0-4
has caused the Debian Bug report #1006057,
regarding node-tildify: FTBFS: Unable to parse '' at 
/usr/share/perl5/Debian/Dependency.pm line 356.
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.)


-- 
1006057: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006057
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-tildify
Version: 2.0.0-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
>   mkdir -p node_modules
>   ln -s ../. node_modules/tildify
>   /bin/sh -ex debian/tests/pkg-js/test
> + tape test.js
> TAP version 13
> # tildify home
> ok 1 should be strictly equal
> # tildify path
> ok 2 should be strictly equal
> ok 3 should be truthy
> ok 4 should not be strictly equal
> # ensure only a fully matching path is replaced
> ok 5 should be strictly equal
> # ignore relative paths
> ok 6 should be strictly equal
> # only tildify when home is at the start of a path
> ok 7 should be strictly equal
> 
> 1..7
> # tests 7
> # pass  7
> 
> # ok
> 
> Removing node_modules/tildify
>create-stamp debian/debhelper-build-stamp
>dh_prep
>dh_auto_install --buildsystem=nodejs --destdir=debian/node-tildify/
> dh_auto_install: warning: ### Missing ./build/config.gypi, skipping
> 
> Found "files" field in ./package.json, using it
>   mkdir -p /<>/debian/node-tildify//usr/share/nodejs/tildify/
>   install -m 644 ./index.js 
> /<>/debian/node-tildify//usr/share/nodejs/tildify//
>   install -m 644 ./index.d.ts 
> /<>/debian/node-tildify//usr/share/nodejs/tildify//
>   install -m 644 ./package.json 
> /<>/debian/node-tildify//usr/share/nodejs/tildify//
>   install -m 644 ./package.json 
> /<>/debian/node-tildify//usr/share/nodejs/tildify//
> Unable to parse '' at /usr/share/perl5/Debian/Dependency.pm line 356.
> make: *** [debian/rules:8: binary] Error 255


The full build log is available from:
http://qa-logs.debian.net/2022/02/18/node-tildify_2.0.0-3_unstable.log

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-tildify
Source-Version: 2.0.0-4
Done: Yadd 

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-tildify package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 19 Feb 2022 09:05:53 +0100
Source: node-tildify
Architecture: source
Version: 2.0.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 1006057
Changes:
 node-tildify (2.0.0-4) unstable; urgency=medium
 .
   * Team upload
   * Fix d/control for Debian::Control (Closes: #1006057)
Checksums-Sha1: 
 8af57accf01c8972cd295fe7c0540d5f44d064c8 2045 node-tildify_2.0.0-4.dsc
 fcc6ff91e531b5c0ddf803c2768278bd708db7ad 3152 
node-tildify_2.0.0-4.debian.tar.xz
Checksums-Sha256: 
 1949494e7191fb5d30fcb7fd7db04142248056d0a46935a3a1c4376ac9669fb9 2045 
node-tildify_2.0.0-4.dsc
 b9029a51d4c5b3ba52cc92da0d3d51fe7e30fffe348c58cc4d91c4bf704fc294 3152 
node-tildify_2.0.0-4.debian.tar.xz
Files: 
 3f97dd417806b78688c82ed0b076a6a8 2045 javascript