Bug#969938: debirf: bullseye: switch from /updates to -security

[Paul Wise]

Package: debirf
Severity: serious
File: /usr/share/debirf/modules/a0_add_security_repos
User: debian-de...@lists.debian.org
Usertags: bullseye-security

The above script references /updates instead of -security for the
bullseye release and later. This means that images generated for
bullseye will be missing fixes for security issues. Probably this issue
should also get fixed in Debian buster and stretch too.

   $ grep -A11 'debian)' src/modules/a0_add_security_repos 
   debian)
   case "$DEBIRF_SUITE" in
   sid|unstable)
   echo "not adding security repository for sid/unstable"
   ;;
   *)
   cat < 
"${DEBIRF_ROOT}/etc/apt/sources.list.d/security_repos.list"
   deb http://security.debian.org/ ${DEBIRF_SUITE}/updates main contrib non-free
   EOF
   ;;
   esac
   ;;


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.7.0-3-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages debirf depends on:
ii  apt2.1.10
ii  cpio   2.13+dfsg-2
ii  debootstrap1.0.123
ii  fakechroot 2.19-3.3
ii  fakeroot   1.24-1
ii  klibc-utils2.0.8-1
ii  pseudo [fakeroot]  1.9.0+git20200626+067950b-2
ii  xz-utils   5.2.4-1+b1

Versions of packages debirf recommends:
ii  grub-common  2.04-9
ii  lsb-release  11.1.0
pn  xorriso  

Versions of packages debirf suggests:
ii  syslinux-common  3:6.04~git20190206.bf6db5b4+dfsg1-3

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#969936: bullseye: add support, switch from /updates to -security

[Paul Wise]

Package: debian-lan-config
Version: 0.26
Severity: serious
File: /usr/share/debian-lan-config/fai/config/scripts/LAST/50-misc
User: debian-de...@lists.debian.org
Usertags: bullseye-security

The above script references $release/updates but when bullseye is
released that should be replaced by $release-security.

It looks like when a bullseye system is being installed, the setrel
function does not recognise the target release and so it won't setup
the apt sources.list at all.

Then even if the release were recognised properly, the script would
generate an incorrect sources.list using /updates instead of -security
which would cause the target system to not get security updates from
bullseye in a timely manner.

In addition, the SERVER_A sources.list references buster for the main
set of packages but uses stable/updates for security updates. This
means that after the bullseye release servers installed using the
debian-lan-config package will get packages from buster but their
security updates from bullseye, which seems incorrect.

   $  grep -A100 setrel 
./usr/share/debian-lan-config/fai/config/scripts/LAST/50-misc
   setrel() {

   # if release is not set, try to determine it

   if [ -n "$release" ]; then
return
   fi
   if [ ! -f $target/etc/os-release ]; then
return
   fi

   dists="jessie stretch buster bionic xenial trusty"
   for d in $dists; do
if grep -iq $d $target/etc/os-release; then
release=$d
break
fi
   done
   }

   # if installation was done from CD, replace useless sources.list
   setrel
   if [ -f $target/etc/apt/sources.list -a -n "$release" ]; then
   grep -q 'file generated by fai-cd' $target/etc/apt/sources.list && cat 
< $target/etc/apt/sources.list
   deb $apt_cdn/debian $release main contrib non-free
   deb $apt_cdn/debian-security $release/updates main contrib non-free
   #deb [trusted=yes] http://fai-project.org/download $release koeln
   EOF
   # if the package fai-server was installed, enable the project's 
repository
   if [ -f $target/var/lib/dpkg/info/fai-server.list ]; then
sed -i -e '/fai-project.org/s/^#//' $target/etc/apt/sources.list
   fi
   fi

   # for ARM architecture, we may need the kernel and initrd to boot or flash 
the device
   if ifclass ARM64; then
   cp -pv $target/boot/vmlinuz* $target/boot/initrd* $FAI_RUNDIR
   fi

   exit $error

   $ cat 
/usr/share/debian-lan-config/fai/config/files/etc/fai/apt/sources.list/SERVER_A
   deb http://deb.debian.org/debian/ buster main
   deb http://security.debian.org/ stable/updates main
   deb http://deb.debian.org/debian/ buster-updates main

   ## Backports repository:
   #deb http://deb.debian.org/debian/ buster-backports main

   -- System Information:
   Debian Release: bullseye/sid
 APT prefers testing-debug
 APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
   Architecture: amd64 (x86_64)

   Kernel: Linux 5.7.0-3-amd64 (SMP w/4 CPU threads)
   Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), 
LANGUAGE=en_AU:en
   Shell: /bin/sh linked to /bin/dash
   Init: systemd (via /run/systemd/system)
   LSM: AppArmor: enabled

   debian-lan-config depends on no packages.

   debian-lan-config recommends no packages.

   Versions of packages debian-lan-config suggests:
   pn  fai-server  

   -- 
   bye,
   pabs

   https://wiki.debian.org/PaulWise


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

Processed: bug 969926 is forwarded to https://sourceware.org/bugzilla/show_bug.cgi?id=20338

[Debian Bug Tracking System]

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

> forwarded 969926 https://sourceware.org/bugzilla/show_bug.cgi?id=20338
Bug #969926 [src:glibc] glibc: Parsing of /etc/gshadow can return bad pointers 
causing segfaults in applications
Set Bug forwarded-to-address to 
'https://sourceware.org/bugzilla/show_bug.cgi?id=20338'.
> thanks
Stopping processing here.

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

Bug#962651: marked as done (rst2pdf depends and build depends on python3-pdfrw that might not be in bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 09 Sep 2020 03:19:10 +
with message-id 
and subject line Bug#962651: fixed in rst2pdf 0.98-1
has caused the Debian Bug report #962651,
regarding rst2pdf depends and build depends on python3-pdfrw that might not be 
in bullseye
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.)


-- 
962651: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962651
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rst2pdf
Version: 0.97-2
Severity: serious
Control: block 958362 by -1

rst2pdf depends and build depends on python3-pdfrw
that might not be in bullseye due to #958362.
--- End Message ---
--- Begin Message ---
Source: rst2pdf
Source-Version: 0.98-1
Done: Sandro Tosi 

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated rst2pdf 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: Tue, 08 Sep 2020 22:59:47 -0400
Source: rst2pdf
Architecture: source
Version: 0.98-1
Distribution: unstable
Urgency: medium
Maintainer: Python Applications Packaging Team 

Changed-By: Sandro Tosi 
Closes: 962651
Changes:
 rst2pdf (0.98-1) unstable; urgency=medium
 .
   * New upstream release
   * debian/copyright
 - update upstream copyright notice
   * debian/control
 - remove pdfrw, upstream no longer uses it; Closes: #962651
 - remove six from b-d, no longer needed
 - add new b-d: importlib-metadata, packaging
   * debian/patches/disable_scm.patch
 - dont use setuptools_scm
Checksums-Sha1:
 3bd1eac49a4ee4c2df41b0ee58f3f3aecb0bbfef 2246 rst2pdf_0.98-1.dsc
 232ee10b3bc1a38b71c8e0f3b7dc4451c92907d6 8543480 rst2pdf_0.98.orig.tar.xz
 e846d3b3864ca18796dcb665581a8bc6ffac9a7c 5352 rst2pdf_0.98-1.debian.tar.xz
 93072c5a803beb6d117792ef0caf2863411e2001 5768 rst2pdf_0.98-1_source.buildinfo
Checksums-Sha256:
 5414bcdafdbc3411d2573d42312990dc72cfa7e1d1dcdcb4824285a4935a7194 2246 
rst2pdf_0.98-1.dsc
 a808a774f4f812ab30b41712af30f5d99a79d9b667da2fab05d5e56160601d2b 8543480 
rst2pdf_0.98.orig.tar.xz
 d9774431c067af9bc8f289d4dbe74838d79f66b8cf9a26af250bf48154369f12 5352 
rst2pdf_0.98-1.debian.tar.xz
 8f8b6fb89eca6c4eee85d3ee636e019cd98ddfa6829e714d85f7a2d33f254ce9 5768 
rst2pdf_0.98-1_source.buildinfo
Files:
 80a40326d057d51428743985672d1f37 2246 utils optional rst2pdf_0.98-1.dsc
 d5265fed6c60d296b617245f5c5d4ed7 8543480 utils optional 
rst2pdf_0.98.orig.tar.xz
 e78e3d4a4be56ecc84282ca8623a36c5 5352 utils optional 
rst2pdf_0.98-1.debian.tar.xz
 4ad980f4fb47ddf78e23df5520fef187 5768 utils optional 
rst2pdf_0.98-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAl9YRT4ACgkQh588mTgB
qU+BqQ//XVK4ez1NpRZE7k9Bwvf64CDeK8e1X6LP6FAqbf/8SXP/AdQ+be2Zj6Kp
tl94Z5X0bLgzjNrNWbADrTRmeSGg1YwbrQ215XXadbE45wyml0XXSz6SmydD6O/d
1oeVI8qHeeWxu/wqAsw+fIc1Xm8HWtr99OTCWoZIwzNXJHujsFZNEkR/0rVvZNxt
v7nV+wJlfIgLB9XYZftMgV+i0LkESqdUcosV0reQj5zL28uaeHPi3Ikx469J0WFE
0YKGX8dUoSIpK4rJg0SRZ6rEA6sVBG+ap6CBgfnMDnuJ9ji7QRWe9VWWEseEXTYA
u0h/x5otriy+aHLZJQVCOszFoOSETJxvpYdTjawShtHLyhzdCj2ABqzS82iJ97MD
bqR6KXcUDJYR8sOAVBvb/UQmIjB5/cpweegogfXJT7SKs94v67v4uh/lo/2EVqGG
JWvACftLPvWkB/lxUCieclDGPHuGbSdt7stgUHOluoHDJ0BJWb0ocvJcxr+bbbHb
vCyvl2SMsAYaIKmY1BhmdgDUhKb6VdfkkSuGR9OS/M+8qraM1HZVytlkPHD5f6zh
qOXTW+g/aa3hvP9K4MHUZa0kDFShShgaeTztGDn8NHoS8fH+iZXSgzS98tZA+gl+
c7JWTK6dxl+5Lp99hHB6W6jTl0QZvFmB8MYL0u+MgedOgxw4uMs=
=0rZI
-END PGP SIGNATURE End Message ---

Bug#969930: calamares-settings-debian: switch security.d.o apt sources entry from bullseye/updates to bullseye-security

[Paul Wise]

Package: calamares-settings-debian
Severity: serious

Please switch the security.d.o apt sources entry from bullseye/updates
to bullseye-security otherwise folks who install bullseye from the
bullseye live images using the Calamares installer will not get any
security updates after the bullseye release and they will continue to
get apt errors when they try to do updates.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#962651: marked as pending in pdfposter

[Sandro Tosi]

Control: tag -1 pending

Hello,

Bug #962651 in pdfposter 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/applications/rst2pdf/-/commit/2155cf3f77e28e6321cc64779b0123ad79c23426


remove pdfrw, upstream no longer uses it; Closes: #962651


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/962651

Processed: Bug#962651 marked as pending in pdfposter

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #962651 [rst2pdf] rst2pdf depends and build depends on python3-pdfrw that 
might not be in bullseye
Added tag(s) pending.

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

Bug#969815: marked as done (comprez: autopkgtest should be marked superficial)

[Debian Bug Tracking System]

Your message dated Wed, 09 Sep 2020 02:33:47 +
with message-id 
and subject line Bug#969815: fixed in comprez 2.7.3-2
has caused the Debian Bug report #969815,
regarding comprez: autopkgtest should be marked superficial
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.)


-- 
969815: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969815
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: comprez
Severity: serious
Usertags: superficialtest
X-Debbugs-CC: elb...@debian.org

Hi,

The test done in the autopkgtest of 'comprez' does not provide
significant test coverage and it should be marked with "Restrictions:
superficial".

Ref: https://people.debian.org/~eriberto/README.package-tests.html

Examples of tests which are not significant includes (its not a
complete list):

1) Executing the binary to check version

Test-Command: foo -v

Test-Command: foo -V

Test-Command: foo --version

2) Executing the binary to check help (foo -h)

Test-Command: foo -h

Test-Command: foo --help

3) checking for files installed with 'ls'.

Test-Command: ls -l /usr/lib/*/foo.so

4) A Python or Perl library runs import foo or require Foo; but does
not attempt to use the library beyond that.

Test-Command: python3 -c "import foo"

Please add "Restrictions: superficial" to 'debian/tests/control' of
'comprez'.

--

Sudip 
--- End Message ---
--- Begin Message ---
Source: comprez
Source-Version: 2.7.3-2
Done: Giovani Augusto Ferreira 

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

Debian distribution maintenance software
pp.
Giovani Augusto Ferreira  (supplier of updated comprez 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 08 Sep 2020 21:20:31 -0300
Source: comprez
Architecture: source
Version: 2.7.3-2
Distribution: unstable
Urgency: medium
Maintainer: Giovani Augusto Ferreira 
Changed-By: Giovani Augusto Ferreira 
Closes: 969815
Changes:
 comprez (2.7.3-2) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Use correct machine-readable copyright file URI.
 .
   [ Giovani Augusto Ferreira ]
   * Bumped DH level to 13.
   * Bumped Standards-Version to 4.5.0
   * debian/tests/control: Add superficial restriction (closes: #969815)
Checksums-Sha1:
 426a58bfea472341dafc43c2c05affcd8be13cc4 1846 comprez_2.7.3-2.dsc
 d03bf3c27496937f564ce32972a2a5815f77f571 6228 comprez_2.7.3-2.debian.tar.xz
 954f7e2365d97c8e499187adb624e01b55ee99b5 5394 comprez_2.7.3-2_source.buildinfo
Checksums-Sha256:
 bc65bb455e211bb182f01102c1749471b25f16379eeed6cd42f5080fd7de909e 1846 
comprez_2.7.3-2.dsc
 0945c0d5f6702a3ee5958259b74960f2acc53a59141eaf9af4d3fd0fb43de904 6228 
comprez_2.7.3-2.debian.tar.xz
 a6691dd1add946500470bbf04498204f295a300d532d8722261cc9070b371f27 5394 
comprez_2.7.3-2_source.buildinfo
Files:
 ae8f95cc6e1d817bd9dd6c6d536ba9e9 1846 utils optional comprez_2.7.3-2.dsc
 d9bd6b81e8ef172236e2814e850cd517 6228 utils optional 
comprez_2.7.3-2.debian.tar.xz
 d430232849e2135c251b91911220f91d 5394 utils optional 
comprez_2.7.3-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEs/UaJxJhnD7NdLjheElO9yN1pmwFAl9YN5MACgkQeElO9yN1
pmzdmBAAuo5Zsdilmb+oc0O6VrGcXxay2r42NO/WFzG+Rzd2AWa/jJWJvWWE2AzM
IWZE7rOQ5q8CpEqSagOYrnlzLwTdhRsQjSA1a5GnAWHcpHy8kjO6EMnITb5Eaq9J
2++Jg7hwfNgRYvxd/Ekc8gyBiFZZ+pSrX/LVIV8SWH1jsjkzO7NlVOKQMsKYHII0
Z8PKwZ8RB4AYIx4VXa+5PS/ZVjawM3lyAVCyhui2rsHfvTZyaMEi9RH+nHHaKP3o
Zw5dHxHTFV/DudonJjQQ/QYST2h9ePczYuiD2rddi178Dl0NoLwk1StkX+hJLBjX
LfJGvknMOFlFPXXIstMklvYWktX7RYVqp8wCOdyjggRYwj5rgHYajC7gu6E8HzNt
IovObjCKYqCtTsHZgTXIXywpFKZGkxMqBWH1RXxUJ5kaYexrW3UZOFlhgHg2zxou
6OOPAy6RAyrMzgB7IZXt2GNx72bcukusiETaLBsSUlsQsoCZknyUsFAd0YpHKvzy
n1gD/zVQBaevc1uRsx8vs6vx51v4IAzExEx1LldmIqhQSTAZ0a92XJH2gQoW8vrl
DGQPOfP5JajagcLs2OOLHh4dHOe/Usm2Eg7t1QRXENDDbvyEiiCe6ABuzXsx+3hY
yUddPxMt9sn7INr6WWqSLjAC/ObYnoRxObP+msr37Qi7cCc/Z6k=
=Phgs
-END PGP SIGNATURE End Message ---

Bug#968689: marked as done (python3-commonmark: file conflict with cmark, php-league-commonmark)

[Debian Bug Tracking System]

Your message dated Wed, 09 Sep 2020 02:33:34 +
with message-id 
and subject line Bug#968689: fixed in commonmark 0.9.1-3
has caused the Debian Bug report #968689,
regarding python3-commonmark: file conflict with cmark, php-league-commonmark
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.)


-- 
968689: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968689
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-commonmark
Version: 0.9.1-1
Severity: serious
Justification: file conflict

Unpacking python3-commonmark (0.9.1-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/python3-commonmark_0.9.1-1_all.deb (--unpack):
 trying to overwrite '/usr/bin/cmark', which is also in package cmark 0.29.0-4

Best

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

Kernel: Linux 5.8.1 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages python3-commonmark depends on:
ii  python3  3.8.2-3

python3-commonmark recommends no packages.

python3-commonmark suggests no packages.
--- End Message ---
--- Begin Message ---
Source: commonmark
Source-Version: 0.9.1-3
Done: Sandro Tosi 

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated commonmark 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: Tue, 08 Sep 2020 21:35:42 -0400
Source: commonmark
Architecture: source
Version: 0.9.1-3
Distribution: unstable
Urgency: medium
Maintainer: Sandro Tosi 
Changed-By: Sandro Tosi 
Closes: 968689
Changes:
 commonmark (0.9.1-3) unstable; urgency=medium
 .
   * debian/rules
 - move /usr/bin/cmark to /u/b/python3-commonark, to avoid a further 
conflict
   with src:php-league-commonmark; Closes: #968689
Checksums-Sha1:
 a2d2ec88dede6fde563150bf22a6fade3eabfa0e 2031 commonmark_0.9.1-3.dsc
 5799a21561f9620de7c322de24a0820769cb9201 2388 commonmark_0.9.1-3.debian.tar.xz
 e086691baab22912456f3f40a4750d38a23ab633 6369 
commonmark_0.9.1-3_source.buildinfo
Checksums-Sha256:
 579b065e3caf81b21c4a31d5fad70ec153cc56ccd645f14445d490219c420a15 2031 
commonmark_0.9.1-3.dsc
 fb7b649d9216168cfc6fa44228acefe8e64b055bb096f594f95415ad1086a14d 2388 
commonmark_0.9.1-3.debian.tar.xz
 eb0595b2cc8eb9dabdb97af78ee30924c5f1aaf80e85ddc52b0b508063f77952 6369 
commonmark_0.9.1-3_source.buildinfo
Files:
 e0c1dadc3c965c0259cf9028e136a3f4 2031 python optional commonmark_0.9.1-3.dsc
 62010f1b75ef38da3b7ea761236087a1 2388 python optional 
commonmark_0.9.1-3.debian.tar.xz
 2e12133852245cc003eede4ff0e80a44 6369 python optional 
commonmark_0.9.1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIyBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAl9YMYcACgkQh588mTgB
qU92ag/1FL+IMg96JBplom/ee3IO0teb1wNe0+td7JOItU5Pr3RgfhpUIRjqTEQN
PkODftcN2dAWevRiVO5j1azRAQzBYxrPPMJLyiPLagZAqTGffYl6MqdbDxoQbUUL
tNQ2yQfWGneFPxOXHAevwhEKSm2DEK0KUcUskIb3Wyt7mZ1Vnn/8WcqfslzRZLBC
mz9pygWL/L+CBfFxdx9cw3zATruzAseUIG2vxZy5h+CjJsZAFhGj4/LAy5yLVJBz
rs14OuFE38CwXByqtylBp2jR+pEbq9x9qS4LZlw4wWtD9r4Gb3axoIfWJGqJlSo9
M6gsBTKwyLJwO6jHQefyaB0O+UxsUe2JvG8gt/I+gUrXzaI7nCoF3lziQvFBCSs+
WKgP7d0zG8jg/V7872BD/wYCyvzhhHcKdOa8cHgiaV5eQ6f0uMc4X2Q01rqId7ca
4QhattWWfdIIV5Z17qWglQe2hBTmpr2Z1QyBxocgoTFTguZ+dHGnytqQHpJVJh9f
qaAdvk8B/RI627WWipdxj9JMaY3lzgZKb1uzJ63mDz0xXxbZPas76FX86S38xftB
4K5oweZdBNtjiYxvIQG3lc5+akjp7Eve59/Ts9dGDA68WGSL/lnmsCvB3pkyOaOU
/4afADBhoSu+5tvvbjTL6L1kZGvf/ORhHbqyFPjFGPTo4djKPA==
=DwY5
-END PGP SIGNATURE End Message ---

Bug#969894: nvidia-legacy-390xx-driver: X will not start with nvidia-legacy-390.xx driver and 5.8 kernel

[Jiri Kanicky]

$ dpkg-reconfigure nvidia-kernel-dkms

Does not seem to build the modules for 5.8.0-1.


Building initial module for 5.8.0-1-amd64
Error! Bad return status for module build on kernel: 5.8.0-1-amd64 (x86_64)
Consult /var/lib/dkms/nvidia-current/440.82/build/make.log for more 
information.


make.log attached.

--
Jiri

DKMS make.log for nvidia-current-440.82 for kernel 5.8.0-1-amd64 (x86_64)
Wed 09 Sep 2020 10:54:48 AEST
make KBUILD_OUTPUT=/lib/modules/5.8.0-1-amd64/build V=1 -C /lib/modules/5.8.0-1-amd64/source M=/var/lib/dkms/nvidia-current/440.82/build ARCH=x86_64 NV_KERNEL_SOURCES=/lib/modules/5.8.0-1-amd64/source NV_KERNEL_OUTPUT=/lib/modules/5.8.0-1-amd64/build NV_KERNEL_MODULES="nvidia nvidia-uvm nvidia-modeset nvidia-drm" INSTALL_MOD_DIR=kernel/drivers/video NV_SPECTRE_V2=0 modules
make[1]: Entering directory '/usr/src/linux-headers-5.8.0-1-common'
make -C /usr/src/linux-headers-5.8.0-1-amd64 -f /usr/src/linux-headers-5.8.0-1-common/Makefile modules
make[2]: Entering directory '/usr/src/linux-headers-5.8.0-1-amd64'
test -e include/generated/autoconf.h -a -e include/config/auto.conf || (		\
echo >&2;			\
echo >&2 "  ERROR: Kernel configuration is invalid.";		\
echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\
echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.";	\
echo >&2 ;			\
/bin/false)
make -f /usr/src/linux-headers-5.8.0-1-common/scripts/Makefile.build obj=/var/lib/dkms/nvidia-current/440.82/build \
single-build= \
need-builtin=1 need-modorder=1
scripts/Makefile.lib:8: 'always' is deprecated. Please use 'always-y' instead
NV_CONFTEST_CMD=/bin/sh /var/lib/dkms/nvidia-current/440.82/build/conftest.sh " gcc-10" x86_64 /lib/modules/5.8.0-1-amd64/source /lib/modules/5.8.0-1-amd64/build
NV_CONFTEST_CFLAGS=-O2 -D__KERNEL__ -DKBUILD_BASENAME="#conftest16218" -DKBUILD_MODNAME="#conftest16218" -nostdinc -isystem /usr/lib/gcc/x86_64-linux-gnu/10/include -I/lib/modules/5.8.0-1-amd64/source/arch/x86/include/asm/mach-default -I/lib/modules/5.8.0-1-amd64/source/include/asm-x86/mach-default -I/lib/modules/5.8.0-1-amd64/build/include2 -I/lib/modules/5.8.0-1-amd64/build/include -include /lib/modules/5.8.0-1-amd64/build/include/generated/autoconf.h -I/lib/modules/5.8.0-1-amd64/source/arch/x86/include -I/lib/modules/5.8.0-1-amd64/source/arch/x86/include/uapi -I/lib/modules/5.8.0-1-amd64/build/arch/x86/include/generated -I/lib/modules/5.8.0-1-amd64/build/arch/x86/include/generated/uapi -I/lib/modules/5.8.0-1-amd64/source/include -I/lib/modules/5.8.0-1-amd64/source/include/uapi -I/lib/modules/5.8.0-1-amd64/source/include/xen -I/lib/modules/5.8.0-1-amd64/build/include/generated/uapi -I/var/lib/dkms/nvidia-current/440.82/build/common/inc -I/var/lib/dkms/nvidia-current/440.82/build -Wall -MD   -Wno-cast-qual -Wno-error -Wno-format-extra-args -D__KERNEL__ -DMODULE -DNVRM -DNV_VERSION_STRING=\"440.82\" -Wno-unused-function -Wuninitialized -fno-strict-aliasing -mno-red-zone -mcmodel=kernel -DNV_UVM_ENABLE -Werror=undef -DNV_SPECTRE_V2=0 -fno-pie -Wall -Wundef -Wno-trigraphs -fno-strict-aliasing -fno-common -fshort-wchar -fno-PIE -Wno-format-security -std=gnu89 -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic -mno-red-zone -mcmodel=kernel -DCONFIG_X86_X32_ABI -Wno-sign-compare -fno-asynchronous-unwind-tables -mindirect-branch=thunk-extern -mindirect-branch-register -fno-jump-tables -fno-delete-null-pointer-checks -Wno-frame-address -Wno-format-truncation -Wno-format-overflow -Wno-address-of-packed-member -O2 -fno-allow-store-data-races -Wframe-larger-than=2048 -fstack-protector-strong -Wno-unused-but-set-variable -Wimplicit-fallthrough -Wno-unused-const-variable -fno-var-tracking-assignments -g -pg -mrecord-mcount -mfentry -DCC_USING_FENTRY -flive-patching=inline-clone -Wdeclaration-after-statement -Wvla -Wno-pointer-sign -Wno-stringop-truncation -Wno-zero-length-bounds -Wno-array-bounds -Wno-stringop-overflow -Wno-restrict -Wno-maybe-uninitialized -fno-strict-overflow -fno-merge-all-constants -fmerge-constants -fno-stack-check -fconserve-stack -fmacro-prefix-map=/usr/src/linux-headers-5.8.0-1-common/= -fcf-protection=none -Wno-packed-not-aligned
KBUILD_CFLAGS=-Wall -Wundef -Werror=strict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -fshort-wchar -fno-PIE -Werror=implicit-function-declaration -Werror=implicit-int -Wno-format-security -std=gnu89 -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic -mno-red-zone -mcmodel=kernel -DCONFIG_X86_X32_ABI -Wno-sign-compare -fno-asynchronous-unwind-tables -mindirect-branch=thunk-extern -mindirect-branch-register -fno-jump-tables -fno-delete-null-pointer-checks -Wno-frame-address -Wno-format-truncation -Wno-format-overflow 

Bug#969926: glibc: Parsing of /etc/gshadow can return bad pointers causing segfaults in applications

[Bernd Zeimetz]

Source: glibc
Version: 2.28-10
Severity: serious
Tags: security upstream patch
X-Debbugs-Cc: Debian Security Team 

Hi,

we are running into the bug
https://sourceware.org/bugzilla/show_bug.cgi?id=20338
causing systemd-sysusers to segfault.

Patch is available in the linked bug report.

As it was flagged security in the upstream bugtracker, I'm doing the
same here.

A fix in buster would be appreciated.

Thanks a lot,

Bernd


-- 
 Bernd ZeimetzDebian GNU/Linux Developer
 http://bzed.dehttp://www.debian.org
 GPG Fingerprint: ECA1 E3F2 8E11 2432 D485  DD95 EB36 171A 6FF9 435F

Bug#968913: marked as done (perl-base: IO::Socket::IP: AI_ADDRCONFIG breaks many test suites on IPv6-only hosts)

[Debian Bug Tracking System]

Your message dated Wed, 09 Sep 2020 00:04:20 +
with message-id 
and subject line Bug#968913: fixed in perl 5.32.0-3
has caused the Debian Bug report #968913,
regarding perl-base: IO::Socket::IP: AI_ADDRCONFIG breaks many test suites on 
IPv6-only hosts
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.)


-- 
968913: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968913
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libio-socket-ip-perl
Version: 0.39-2
Severity: serious
Tags: patch ipv6

This is a follow-up for #962047 "fails to build on IPv6-only buildds".

The background here is that a while ago new official build daemons were
added that only have IPv6 connectivity, and this exposed a new class
of build failures, mainly due to getaddrinfo(3) behaviour with the
AI_ADDRCONFIG flag.

Quoting Julien Cristau there:

> FWIW, it seems IO::Socket::IP passes AI_ADDRCONFIG to getaddrinfo, which
> then doesn't return ipv4 addresses because the host doesn't have
> non-local ones, even though the address we're trying to resolve is
> "127.0.0.1".
> 
> Passing either GetAddrInfoFlags => AI_NUMERICHOST or GetAddrInfoFlags =>
> 0 to both IO::Socket::IP->new calls in the test file lets it pass, by
> turning off the smarts in getaddrinfo.

We fixed the test suite of libio-socket-ip-perl itself in 0.39-2 by
making it pass AI_NUMERICHOST in all the tests. However, it turns out
that the problem is much more widespread than this.

I've been testing systematically for these issues by test rebuilding
the whole archive, and found

1) 138 packages that failed to build on a host with an IPv6 address
   on a "real" interface, and IPv4 + IPv6 on lo, but no internet
   connection

2) 8 of those 138 also failed to build on a host with both an IPv6 address
   and an IPv4 address on a "real interface", still without a real internet
   connection (these are regular "needs internet" bugs, not IPv6 specific)

3) only 42 of the remaining 130 packages fail to build with the same setup
   as 1), after applying the patch discussed below to IO::Socket::IP.

So it looks like the AI_ADDRCONFIG default of IO-Socket-IP is causing
88 potential build failures on the new IPv6-only buildds. Examples of
those can be seen on for instance

 https://buildd.debian.org/status/logs.php?pkg=libmojolicious-perl

 https://buildd.debian.org/status/logs.php?pkg=libtest-redisserver-perl

 https://buildd.debian.org/status/logs.php?pkg=libwww-mechanize-perl

The attached patch changes IO-Socket-IP to pass AI_NUMERICHOST to
getaddrinfo(3) when the address looks like an IPv4 numeric address (rather
than a hostname), and special cases a PeerHost value of "localhost"
not to use AI_ADDRCONFIG.

I have tried quite a few variants, and this was the best I could do
without removing AI_ADDRCONFIG (which is a documented feature) altogether.
(TODO: The patch does not currently update the documentation about the
new behaviour.)

It would be good to get something like this upstream of course, and it
will also need to go in src:perl which has a copy of IO::Socket::IP.

I've tested that this makes libio-socket-perl pass its own test suite
without the modifications in 0.39-2, so this supersedes the current test
suite patch.

Build logs can currently (but not guaranteed indefinitely) be found at

 http://perl.debian.net/rebuild-logs/sid-v6only/

 http://perl.debian.net/rebuild-logs/experimental-v6only/

where the latter had a patched libio-socket-ip-perl package pre-installed
in the chroot.

Below is the list of packages detected as fixed by this. I'll bring up the
other IPv6-related build failures on the debian-devel list soonish. Bugs
have already been filed for the handful of "needs internet" issues.

alice_0.19-2
boxbackup_0.13~~git20200326.g8e8b63c-1
gdnsd_2.4.2-1
kgb-bot_1.56-1
libanyevent-connection-perl_0.06-5
libanyevent-connector-perl_0.03-2
libanyevent-memcached-perl_0.08-1
libanyevent-redis-perl_0.24-2
libapache2-authcookie-perl_3.30-1
libapache2-reload-perl_0.13-3
libapache-authenhook-perl_2.00-04+pristine-7
libapache-singleton-perl_0.17-1
libapache-ssllookup-perl_2.00-04-3
libapp-termcast-perl_0.13-3
libaudio-mpd-perl_2.004-2
libcgi-application-plugin-captcha-perl_0.04-2
libcgi-application-server-perl_0.063-2
libcorona-perl_0.1004-4
libcpan-mini-inject-perl_0.35-1
libcrypt-ssleay-perl_0.73.06-1
libdancer-perl_1.3513+dfsg-1
libdanga-socket-perl_1.62-1
libfcgi-engine-perl_0.22-1
libfurl-perl_3.13-2
libgearman-client-perl_2.004.015-1
libhtml-html5-parser-perl_0.301-2
libhttp-async-perl_0.33-1
libhttp-daemon-ssl-perl_1.05-01-2

Bug#969552: [Help] Re: Bug#969552: phipack: arm64 autopkgtest failure: ERROR: Illegal state encountered: �

[Lennart Sorensen]

On Tue, Sep 08, 2020 at 05:35:45PM -0400, Lennart Sorensen wrote:
> On Tue, Sep 08, 2020 at 10:35:26PM +0200, Andreas Tille wrote:
> > Control: tags -1 help
> > 
> > Hi Debian Arm team,
> > 
> > I admit I have no idea how to deal with this except by excluding
> > arm64 from the list of supported architectures which is definitely
> > not my prefered way of action.
> > 
> > Any help would be really appreciated.
> 
> I don't have access to an arm64 system at the moment, but a good start
> might be to fix the compiler warnings, such as the array subscript out
> of bounds in global.c line 44.  The rest of the warnings appear harmless.
> 
> It would appear that GAP_SIZE = 2 is wrong given GAP[] only contains a
> single character.

I found the actual problem.  Someone didn't know that there are 3 types
of char in C.  char, signed char and unsigned char.  char is _only_ for
use in strings, and never to be used as a numerical value.  This is due
to the sign of char being implementation specific.  On x86 it is signed,
on arm it is unsigned.  So any time you want to work with numerical
values of a char, you must specify if you want signed or unsigned.
Changing char ch to unsigned char ch, made x86 fail the same way arm64
did, and making it signed char, makes both pass the test.

So here is a patch that appears to solve the problems in the code.

-- 
Len Sorensen
diff -ruN phipack-0.0.20160614/src/fasta.c phipack-0.0.20160614.arm64/src/fasta.c
--- phipack-0.0.20160614/src/fasta.c	2016-06-14 00:18:29.0 -0400
+++ phipack-0.0.20160614.arm64/src/fasta.c	2020-09-08 19:08:06.672390326 -0400
@@ -36,7 +36,7 @@
 void read_sequence_name(FILE *in_file,char *name, int capacity)
 {
   int i=0;
-  char ch='\0';
+  signed char ch='\0';
 
   ch=fgetc(in_file);
   if(ch != '>')
@@ -97,7 +97,7 @@
 {
   int bases_read=0;
   int new_limit;
-  char ch;
+  signed char ch;
   char s[250];
   
   ch=fgetc(in_file);
@@ -175,7 +175,7 @@
   int *seq_counter;
   int i;
  
-  char ch;
+  signed char ch;
 
   int cur_seqs;
   int num_seqs=1,new_num;
diff -ruN phipack-0.0.20160614/src/global.c phipack-0.0.20160614.arm64/src/global.c
--- phipack-0.0.20160614/src/global.c	2016-06-13 22:33:15.0 -0400
+++ phipack-0.0.20160614.arm64/src/global.c	2020-09-08 18:04:48.956444973 -0400
@@ -34,7 +34,7 @@
 const int AA_AMBIG_SIZE =2;
 
 const char GAP[] = {'-'};
-const int GAP_SIZE=2;
+const int GAP_SIZE=1;
 
 cbool memberOf(const char *set, const int num, char ch)
 {
@@ -79,10 +79,10 @@
   switch(alignKind)
 {
 case DNA:
-  return (memberOf(DNA_MISSING,DNA_MISSING_SIZE,ch) || memberOf(DNA_AMBIG,DNA_AMBIG_SIZE,ch));
+  return (memberOf(DNA_MISSING,DNA_MISSING_SIZE,ch) || memberOf(DNA_AMBIG,DNA_AMBIG_SIZE,ch)) ? TRUE : FALSE;
   break;
 case AA:
-  return (memberOf(AA_MISSING,AA_MISSING_SIZE,ch) || memberOf(AA_AMBIG,AA_AMBIG_SIZE,ch));
+  return (memberOf(AA_MISSING,AA_MISSING_SIZE,ch) || memberOf(AA_AMBIG,AA_AMBIG_SIZE,ch)) ? TRUE : FALSE;
   break;
 case OTHER:
   if(ch == GLOBAL_MISSING)
diff -ruN phipack-0.0.20160614/src/main.c phipack-0.0.20160614.arm64/src/main.c
--- phipack-0.0.20160614/src/main.c	2016-06-14 00:18:17.0 -0400
+++ phipack-0.0.20160614.arm64/src/main.c	2020-09-08 19:17:18.230153542 -0400
@@ -71,7 +71,8 @@
 
 void get_params(int argc, char**argv, options *opt) 
 { 
-  char *cur,ch,nextch;
+  char *cur;
+  signed char ch,nextch;
   char temp[MAX_SIZE+1];
   int i;
   cbool inFileFound=FALSE;
diff -ruN phipack-0.0.20160614/src/mem.c phipack-0.0.20160614.arm64/src/mem.c
--- phipack-0.0.20160614/src/mem.c	2016-06-13 22:33:15.0 -0400
+++ phipack-0.0.20160614.arm64/src/mem.c	2020-09-08 19:12:52.415278666 -0400
@@ -96,7 +96,7 @@
 
 char ffclose(FILE *handle)
 {
-  char f;
+  signed char f;
   char s[MAX_SIZE+1];
 
   f=fclose(handle);
diff -ruN phipack-0.0.20160614/src/misc.c phipack-0.0.20160614.arm64/src/misc.c
--- phipack-0.0.20160614/src/misc.c	2016-06-13 22:33:15.0 -0400
+++ phipack-0.0.20160614.arm64/src/misc.c	2020-09-08 19:08:28.352322441 -0400
@@ -46,7 +46,7 @@
 
 char skip_all_space(FILE *in_file)
 {
-  char ch;
+  signed char ch;
   
   ch=fgetc(in_file);
   while((ch != EOF) && isspace(ch))
@@ -61,7 +61,7 @@
 
 char skip_newlines(FILE *in_file)
 {
-  char ch;
+  signed char ch;
   
   ch=fgetc(in_file);
   while((ch != EOF) && (ch == '\n'))
@@ -76,7 +76,7 @@
 
 char skip_non_newline(FILE *in_file)
 {
-  char ch;
+  signed char ch;
   
   ch=fgetc(in_file);
   while((ch != EOF) && (ch != '\n'))
@@ -90,7 +90,7 @@
 
 char skip_non_newline_space(FILE *in_file)
 {
-  char ch;
+  signed char ch;
   
   ch=fgetc(in_file);
   while((ch != EOF) && (ch != '\n') && isspace(ch))
diff -ruN phipack-0.0.20160614/src/phylip.c phipack-0.0.20160614.arm64/src/phylip.c
--- phipack-0.0.20160614/src/phylip.c	2016-06-14 00:18:17.0 -0400
+++ phipack-0.0.20160614.arm64/src/phylip.c	2020-09-08 19:10:06.483985652 -0400
@@ -30,7 +30,7 @@
 void read_strict_name(FILE 

Bug#966433: marked as done (seqan autopkg test failures triggered by gcc-defaults)

[Debian Bug Tracking System]

Your message dated Tue, 08 Sep 2020 23:19:00 +
with message-id 
and subject line Bug#966433: fixed in seqan3 3.0.2~rc1+bf04354+ds-1
has caused the Debian Bug report #966433,
regarding seqan autopkg test failures triggered by gcc-defaults
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.)


-- 
966433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966433
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:seqan
Version: 3.0.1+ds-10
Severity: serious
Tags: sid bullseye

seqan autopkg test failures triggered by gcc-defaults, this doesn't seem to be
related to GCC 10.

https://ci.debian.net/data/autopkgtest/testing/amd64/s/seqan3/6396315/log.gz

/usr/include/seqan3/alphabet/concept.hpp:441:62: error: wrong number of template
arguments (2, should be 3)
  441 | remove_cvref_t,
  |  ^
--- End Message ---
--- Begin Message ---
Source: seqan3
Source-Version: 3.0.2~rc1+bf04354+ds-1
Done: Dimitri John Ledkov 

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

Debian distribution maintenance software
pp.
Dimitri John Ledkov  (supplier of updated seqan3 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 08 Sep 2020 14:59:35 +0100
Source: seqan3
Architecture: source
Version: 3.0.2~rc1+bf04354+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Dimitri John Ledkov 
Closes: 966270 966433
Changes:
 seqan3 (3.0.2~rc1+bf04354+ds-1) unstable; urgency=medium
 .
   [ Michael R. Crusoe ]
   * Update patch headers
   * Package pre-release from upstream to fix gcc 10.2 FTBFS.
 Closes: #966270, #966433
   * debhelper-compat 13 (routine-update)
   * Switch to upstream's fork of range-v3
Checksums-Sha1:
 e397704b0496c4895f8981d111dd9cc1fe6d5193 2566 seqan3_3.0.2~rc1+bf04354+ds-1.dsc
 3f5a99382c696109c124753f9a1cfea828b0fdeb 2240716 
seqan3_3.0.2~rc1+bf04354+ds.orig.tar.xz
 42ce8877d458060fe77cce1d36a52ee031fc7c12 10988 
seqan3_3.0.2~rc1+bf04354+ds-1.debian.tar.xz
 a4b4b737386ec6a355fd381b678fbfb37642f66a 12136 
seqan3_3.0.2~rc1+bf04354+ds-1_source.buildinfo
Checksums-Sha256:
 b4b64262e5799da56cf2ab3a4d2fd14077adae46d34a142482ee4ff094cd8063 2566 
seqan3_3.0.2~rc1+bf04354+ds-1.dsc
 c2f5153fb56ee886fe68f7f69d76325f4d5da4cbf69244c4ae9281b5493a410a 2240716 
seqan3_3.0.2~rc1+bf04354+ds.orig.tar.xz
 0aa51400b8b82dfe478592069b3e01a4d232d1ee06bac3321856614e1e329a88 10988 
seqan3_3.0.2~rc1+bf04354+ds-1.debian.tar.xz
 db0a8edbb828c787c97a99893eef42d46a9e4c651213c91db31819946d146760 12136 
seqan3_3.0.2~rc1+bf04354+ds-1_source.buildinfo
Files:
 616a214c0f0681ec203c1d3a7853f3d2 2566 science optional 
seqan3_3.0.2~rc1+bf04354+ds-1.dsc
 613199b1c628121ab7a1aa1b1d513a73 2240716 science optional 
seqan3_3.0.2~rc1+bf04354+ds.orig.tar.xz
 95af7a33d91b01e79c309c17e0373184 10988 science optional 
seqan3_3.0.2~rc1+bf04354+ds-1.debian.tar.xz
 4d841534ab48fa49046babb006f2f3cc 12136 science optional 
seqan3_3.0.2~rc1+bf04354+ds-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE7iQKBSojGtiSWEHXm47ISdXvcO0FAl9XjzsACgkQm47ISdXv
cO0mpBAAlAFMimrmh3QI7DpYmv5MPOwMAbckw020CmR4iYotwWcebkzTocLYa8/K
Pza9xlk97OFuOyuy4ej/omk44+MO+okv5QOvCh3TyT3iPD2lWAwD2IEjXuHzH7p5
XLGqnI78DuCLyLgD7mEOZ+fVCp2R1LEU20pNZoWEEeli9WShr0/cqA9NLROf/6YW
5VnywbQfph0pHNU0tqNSQHOTj2kumOe7rvthKiSM1oBGZ5wf3Zx8vxPzgC8hROlk
X58sKX6Grg+QklEMt6Cw59Rc/t718KKrxCb+Bccbp1h9SkD/pSt4844t7ZWgOciz
mFt/puap0x5MRCMBA7gcjDO+Su0BHJB2SjduKRagGl0DGUuQaWLqbUTgfz4aqOHE
mcqrJp/YCepfcLeeFsJTW2vXSXZcr5OvLc/Aj1Q6F+Diuieccqj2nYS9sF3QbCcu
sgsR7VNU8LnOG/dbuPvTsxeXmzxBKsILl+bYC9i858XySSwAtNPknXOmVkh24RsO
6aU8PBz8AzG0YYi0Np5bQ4hI0PaZSxhPkELRJJKs+CiDGDJMvvc2uXZsqC0BvCqQ
EQ+hV6NN3m4TMwjNMdczO7L8CBmVdHdtCWxtHrs8VPBCsWnM0vWkOKnWmDcqSgpb
Emj4p58FKGiyLRXVRLNzDjKA7BDtPrFw1lOPS+tNsMc0ZDFqncs=
=M3wp
-END PGP SIGNATURE End Message ---

Bug#966270: marked as done (seqan3 FTBFS with gcc 10)

[Debian Bug Tracking System]

Your message dated Tue, 08 Sep 2020 23:19:00 +
with message-id 
and subject line Bug#966270: fixed in seqan3 3.0.2~rc1+bf04354+ds-1
has caused the Debian Bug report #966270,
regarding seqan3 FTBFS with gcc 10
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.)


-- 
966270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966270
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: seqan3
Version: 3.0.1+ds-10
Severity: serious
Tags: ftbfs

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

...
In file included from 
/build/1st/seqan3-3.0.1+ds/include/seqan3/core/algorithm/concept.hpp:20,
 from 
/build/1st/seqan3-3.0.1+ds/include/seqan3/core/algorithm/configuration_utility.hpp:20,
 from 
/build/1st/seqan3-3.0.1+ds/include/seqan3/alignment/configuration/detail.hpp:15,
 from 
/build/1st/seqan3-3.0.1+ds/include/seqan3/alignment/configuration/align_config_max_error.hpp:15,
 from 
/build/1st/seqan3-3.0.1+ds/test/unit/alignment/configuration/align_config_max_error_test.cpp:13:
/build/1st/seqan3-3.0.1+ds/include/seqan3/core/type_traits/template_inspection.hpp:150:14:
 error: expression must be enclosed in parentheses
  150 | requires 
!std::same_as, void>,
  |  
^~
  |  (
  151 | void>
  | ~
  |  )
...
--- End Message ---
--- Begin Message ---
Source: seqan3
Source-Version: 3.0.2~rc1+bf04354+ds-1
Done: Dimitri John Ledkov 

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

Debian distribution maintenance software
pp.
Dimitri John Ledkov  (supplier of updated seqan3 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 08 Sep 2020 14:59:35 +0100
Source: seqan3
Architecture: source
Version: 3.0.2~rc1+bf04354+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Dimitri John Ledkov 
Closes: 966270 966433
Changes:
 seqan3 (3.0.2~rc1+bf04354+ds-1) unstable; urgency=medium
 .
   [ Michael R. Crusoe ]
   * Update patch headers
   * Package pre-release from upstream to fix gcc 10.2 FTBFS.
 Closes: #966270, #966433
   * debhelper-compat 13 (routine-update)
   * Switch to upstream's fork of range-v3
Checksums-Sha1:
 e397704b0496c4895f8981d111dd9cc1fe6d5193 2566 seqan3_3.0.2~rc1+bf04354+ds-1.dsc
 3f5a99382c696109c124753f9a1cfea828b0fdeb 2240716 
seqan3_3.0.2~rc1+bf04354+ds.orig.tar.xz
 42ce8877d458060fe77cce1d36a52ee031fc7c12 10988 
seqan3_3.0.2~rc1+bf04354+ds-1.debian.tar.xz
 a4b4b737386ec6a355fd381b678fbfb37642f66a 12136 
seqan3_3.0.2~rc1+bf04354+ds-1_source.buildinfo
Checksums-Sha256:
 b4b64262e5799da56cf2ab3a4d2fd14077adae46d34a142482ee4ff094cd8063 2566 
seqan3_3.0.2~rc1+bf04354+ds-1.dsc
 c2f5153fb56ee886fe68f7f69d76325f4d5da4cbf69244c4ae9281b5493a410a 2240716 
seqan3_3.0.2~rc1+bf04354+ds.orig.tar.xz
 0aa51400b8b82dfe478592069b3e01a4d232d1ee06bac3321856614e1e329a88 10988 
seqan3_3.0.2~rc1+bf04354+ds-1.debian.tar.xz
 db0a8edbb828c787c97a99893eef42d46a9e4c651213c91db31819946d146760 12136 
seqan3_3.0.2~rc1+bf04354+ds-1_source.buildinfo
Files:
 616a214c0f0681ec203c1d3a7853f3d2 2566 science optional 
seqan3_3.0.2~rc1+bf04354+ds-1.dsc
 613199b1c628121ab7a1aa1b1d513a73 2240716 science optional 
seqan3_3.0.2~rc1+bf04354+ds.orig.tar.xz
 95af7a33d91b01e79c309c17e0373184 10988 science optional 
seqan3_3.0.2~rc1+bf04354+ds-1.debian.tar.xz
 4d841534ab48fa49046babb006f2f3cc 12136 science optional 
seqan3_3.0.2~rc1+bf04354+ds-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE7iQKBSojGtiSWEHXm47ISdXvcO0FAl9XjzsACgkQm47ISdXv
cO0mpBAAlAFMimrmh3QI7DpYmv5MPOwMAbckw020CmR4iYotwWcebkzTocLYa8/K
Pza9xlk97OFuOyuy4ej/omk44+MO+okv5QOvCh3TyT3iPD2lWAwD2IEjXuHzH7p5
XLGqnI78DuCLyLgD7mEOZ+fVCp2R1LEU20pNZoWEEeli9WShr0/cqA9NLROf/6YW

Bug#969552: [Help] Re: Bug#969552: phipack: arm64 autopkgtest failure: ERROR: Illegal state encountered: �

[Lennart Sorensen]

On Tue, Sep 08, 2020 at 10:35:26PM +0200, Andreas Tille wrote:
> Control: tags -1 help
> 
> Hi Debian Arm team,
> 
> I admit I have no idea how to deal with this except by excluding
> arm64 from the list of supported architectures which is definitely
> not my prefered way of action.
> 
> Any help would be really appreciated.

I don't have access to an arm64 system at the moment, but a good start
might be to fix the compiler warnings, such as the array subscript out
of bounds in global.c line 44.  The rest of the warnings appear harmless.

It would appear that GAP_SIZE = 2 is wrong given GAP[] only contains a
single character.

-- 
Len Sorensen

Bug#967219: nextcloud-desktop: Upgrade removed part of configuration

[Marek Straka]

Does thunarx-python depends on Python2 ?

See dependencies on https://git.xfce.org/bindings/thunarx-python/about/
- Thunar (1.7.0 or later)
- pygobject (3.20.0 or later)
- gtk+3 (3.20.0 or later)

Bug#957468: libpsm2: ftbfs with GCC-10

[Brian Smith]

I have uploaded libpsm 11.2.185-1, which addresses this bug.

As requested, I'm leaving Bug #957468 open.

-- 
Brian T. Smith
System Fabric Works
Senior Principal Engineer
bsm...@systemfabricworks.com
GPG Key: 0xB3C2C7B73BA3CD7F

Bug#969797: marked as done (altermime: autopkgtest should be marked superficial)

[Debian Bug Tracking System]

Your message dated Tue, 08 Sep 2020 21:03:26 +
with message-id 
and subject line Bug#969797: fixed in altermime 0.3.10-12
has caused the Debian Bug report #969797,
regarding altermime: autopkgtest should be marked superficial
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.)


-- 
969797: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969797
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: altermime
Severity: serious
Usertags: superficialtest
X-Debbugs-CC: elb...@debian.org

Hi,

The test done in the autopkgtest of 'altermime' does not provide
significant test coverage and it should be marked with "Restrictions:
superficial".

Ref: https://people.debian.org/~eriberto/README.package-tests.html

Examples of tests which are not significant includes (its not a
complete list):

1) Executing the binary to check version

Test-Command: foo -v

Test-Command: foo -V

Test-Command: foo --version

2) Executing the binary to check help (foo -h)

Test-Command: foo -h

Test-Command: foo --help

3) checking for files installed with 'ls'.

Test-Command: ls -l /usr/lib/*/foo.so

4) A Python or Perl library runs import foo or require Foo; but does
not attempt to use the library beyond that.

Test-Command: python3 -c "import foo"

Please add "Restrictions: superficial" to 'debian/tests/control' of
'altermime'.

--

Sudip 
--- End Message ---
--- Begin Message ---
Source: altermime
Source-Version: 0.3.10-12
Done: Sudip Mukherjee 

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

Debian distribution maintenance software
pp.
Sudip Mukherjee  (supplier of updated altermime 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 08 Sep 2020 21:35:56 +0100
Source: altermime
Architecture: source
Version: 0.3.10-12
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Sudip Mukherjee 
Closes: 969797
Changes:
 altermime (0.3.10-12) unstable; urgency=medium
 .
   * QA upload.
   * Update compat level to 13.
   * Mark autopkgtest as superficial. (Closes: #969797)
Checksums-Sha1:
 118df44b532b011120c6e1a60d920a5f6c1cd84b 1887 altermime_0.3.10-12.dsc
 2c3a003dbbcec0c3fb63e78b672c6582109df635 13844 
altermime_0.3.10-12.debian.tar.xz
 dbca77622a3148e36703264782721c4cfd51b1ef 5875 
altermime_0.3.10-12_amd64.buildinfo
Checksums-Sha256:
 e399b1c0e8db546079d01560fe5acf58288c54a9ab1e5917b4e139c7f8c0f43d 1887 
altermime_0.3.10-12.dsc
 59dc11ca883537046301ece151148b88386a99a08fc952509b837376a58e04f7 13844 
altermime_0.3.10-12.debian.tar.xz
 0f379211efee2cb1e6f0c64dea6239fc36026f254cf5c34274d19ea8c500565a 5875 
altermime_0.3.10-12_amd64.buildinfo
Files:
 b896f92cae1b834a4060c96391edc478 1887 mail optional altermime_0.3.10-12.dsc
 42792678bfca845d222ea418acdb8f29 13844 mail optional 
altermime_0.3.10-12.debian.tar.xz
 77b76b516101fbec2c10a6821867d659 5875 mail optional 
altermime_0.3.10-12_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuDQJkCg9jZvBlJrHR5mjUUbRKzUFAl9X6+cACgkQR5mjUUbR
KzXE4A//QXi1plYOksNfTHM8iW7CEAqSOtyZhCY9IY3M0+07rOybUdKt0Lb5zjMU
5KCUf1vTzMReM3y/x3JG2+2VuAH3CvSVV8Pxo+ajYDwNHVqbSsrvLgn10I57NCIp
yHBmZ+c2YJym9lH+ogE+LHX30ao2EFeNraXQi9QnCeRJ6UCupgcFHkYMvMQyQrVZ
dzJUU3B5MxiEQWwv0mJcte0seG33ZrqzpwW36jzycbu0OpRo1+7ONip4LZNXFX1P
+fp3WoGKABu9pr5ESZN5BIKv4l66Sa6sY6XxkJEi8E6kM9i5YoadMufeznV08enq
c4Qstd1USu7boQtMAURl9g9YoPUgw9A+zQDuVbWM9797KAs3g9oAdj63MWNkuath
+T6G30hftsFOIfJqcoqgZKmAh6DuchjHg91xik+8zVxcv6JZtSFHDe2DsxNsa+Ga
6eG5BwzIQHW1dbp82+xn+YpK2rzvmMRL+Tc6TT/BUIVCHF9oOjnSPGSm8ItO1NhC
I4pBgcHKKknMhl3yFgzhw8nzcBFGXdASzmdZ+VJVGjNyCEVwWVpGvPAhudZen88b
VAQidS+L4tVM8TEff5sWKkVwrg4eIXRJJQPOHeAWdpg6FRBuKLAQWDmN4qUBRQnE
OavDY2Km7cH7Rd3jzuv4OIaNXeFXme3VcA+zWmclIz3hhwv8rM8=
=NlUY
-END PGP SIGNATURE End Message ---

Bug#969364: marked as done (ignition-math: FTBFS in sid)

[Debian Bug Tracking System]

Your message dated Tue, 08 Sep 2020 21:03:39 +
with message-id 
and subject line Bug#969364: fixed in ignition-math 6.4.0+ds-10
has caused the Debian Bug report #969364,
regarding ignition-math: FTBFS in sid
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.)


-- 
969364: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969364
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ignition-math
Version: 6.4.0+ds-9
Severity: serious

Hello, your package failed to build on arm64, ppc64el, s390x, ia64, powerpc, 
ppc64, riscv64
because of a testsuite error:

  Start 22: UNIT_Pose_TEST
22/46 Test #22: UNIT_Pose_TEST ...***Failed0.00 sec
Running main() from /usr/src/gtest/src/gtest_main.cc
[==] Running 3 tests from 1 test suite.
[--] Global test environment set-up.
[--] 3 tests from PoseTest
[ RUN  ] PoseTest.Pose
[   OK ] PoseTest.Pose (0 ms)
[ RUN  ] PoseTest.ConstPose
[   OK ] PoseTest.ConstPose (0 ms)
[ RUN  ] PoseTest.OperatorStreamOut
/<>/src/Pose_TEST.cc:155: Failure
Expected equality of these values:
  stream.str()
Which is: "0.1 1.2 2.3 -0 0.1 1"
  "0.1 1.2 2.3 0 0.1 1"
[  FAILED  ] PoseTest.OperatorStreamOut (0 ms)
[--] 3 tests from PoseTest (0 ms total)

[--] Global test environment tear-down
[==] 3 tests from 1 test suite ran. (0 ms total)
[  PASSED  ] 2 tests.
[  FAILED  ] 1 test, listed below:
[  FAILED  ] PoseTest.OperatorStreamOut

 1 FAILED TEST

  Start 23: UNIT_Quaternion_TEST
23/46 Test #23: UNIT_Quaternion_TEST .   Passed0.00 sec


cheers,

Gianfranco
--- End Message ---
--- Begin Message ---
Source: ignition-math
Source-Version: 6.4.0+ds-10
Done: Jose Luis Rivero 

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

Debian distribution maintenance software
pp.
Jose Luis Rivero  (supplier of updated ignition-math 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 08 Sep 2020 14:17:02 +
Source: ignition-math
Architecture: source
Version: 6.4.0+ds-10
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jose Luis Rivero 
Closes: 969364
Changes:
 ignition-math (6.4.0+ds-10) unstable; urgency=medium
 .
   * Add patch to fix problems in different arches realated to Pose test
 (Closes: #969364)
Checksums-Sha1:
 b05c0a93ae41afdc5986375d8030b2c636c591c0 2036 ignition-math_6.4.0+ds-10.dsc
 903704f935d59c928a888ed53a2cd2a5530e3786 5984 
ignition-math_6.4.0+ds-10.debian.tar.xz
 f756cf3e4f83ed4565939126c8d11842954e8bf5 7903 
ignition-math_6.4.0+ds-10_source.buildinfo
Checksums-Sha256:
 383ae4982c9f9f958e326d0e4794057c0e55c77a7e109ef09edc6cfb79464d36 2036 
ignition-math_6.4.0+ds-10.dsc
 2afd8be8006ae84175cf7a9d8b6371f10f0326ce1b14f0697e47f533ad38fcae 5984 
ignition-math_6.4.0+ds-10.debian.tar.xz
 2d38d00ae971382f7075deba02262307a2538dc0ae9fda0329a5253a2d27c44a 7903 
ignition-math_6.4.0+ds-10_source.buildinfo
Files:
 83b4f5b3556fe9a7591b6430dcd3d407 2036 science optional 
ignition-math_6.4.0+ds-10.dsc
 e2e476e99361ec4df0d506ecade9c81c 5984 science optional 
ignition-math_6.4.0+ds-10.debian.tar.xz
 bf54fc13d680c1a0dea9b7745c12a401 7903 science optional 
ignition-math_6.4.0+ds-10_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFOBAEBCgA4FiEEoIFhu+wcwGOWFFkDXpRsCQr/BCcFAl9X7jsaHGpyaXZlcm9A
b3NyZm91bmRhdGlvbi5vcmcACgkQXpRsCQr/BCdaHwf+N+gY3SIQ61bmHIowCbsm
kJOIdeIhk6z1C0y2TpZpcHbEC9ApzNBOBR3fks5ZUaIBP1cWhUb2BD7z0cjYFGuy
qQvYpdOXt3hyR4+jy/MLJeriq08YoVjRw3wVSMePEK8UInXMHyQ5dAOMWrcKjpg7
u6OIT09Idaumy3sXPL8itowMPYD9xzchZRngNq+YpVC0j4ecKr6OmJFeG1R2C1Dx
Dn0x0PbC0z/hOGekmNCCyQ0QMcgqX5xJFa1CVy8MjgL0rhSI2e396blR4Y/3rPa2
GrLD8yP+MqbLAWS0kmnjzN/j0IPw9fKksDPcw3kipXvE3xSkPpSXi0quGOq86V9E
1Q==
=wbdh
-END PGP SIGNATURE End Message ---

Bug#969552: [Help] Re: Bug#969552: phipack: arm64 autopkgtest failure: ERROR: Illegal state encountered: �

[Andreas Tille]

Control: tags -1 help

Hi Debian Arm team,

I admit I have no idea how to deal with this except by excluding
arm64 from the list of supported architectures which is definitely
not my prefered way of action.

Any help would be really appreciated.

Kind regards

Andreas.

On Fri, Sep 04, 2020 at 09:26:47PM +0200, Paul Gevers wrote:
> Source: phipack
> Version: 0.0.20160614-4
> X-Debbugs-CC: debian...@lists.debian.org
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: fails-always
> 
> Dear maintainer(s),
> 
> You recently added an autopkgtest to your package phipack, great.
> However, it fails on arm64. Currently this failure is blocking the
> migration to testing [1]. Can you please investigate the situation and
> fix it?
> 
> I copied some of the output at the bottom of this report.
> 
> More information about this bug and the reason for filing it can be found on
> https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
> 
> Paul
> 
> [1] https://qa.debian.org/excuses.php?package=phipack
> 
> https://ci.debian.net/data/autopkgtest/testing/arm64/p/phipack/6611212/log.gz
> 
> autopkgtest [07:17:38]: test run-unit-test: [---
> Run test for functionality ...
> 
> ERROR: Illegal state encountered: �
> 
> Exiting...
> Reading sequence file noro.fasta
> autopkgtest [07:17:38]: test run-unit-test: ---]
> 




> ___
> Debian-med-packaging mailing list
> debian-med-packag...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging


-- 
http://fam-tille.de

Processed: [Help] Re: Bug#969552: phipack: arm64 autopkgtest failure: ERROR: Illegal state encountered: �

[Debian Bug Tracking System]

Processing control commands:

> tags -1 help
Bug #969552 [src:phipack] phipack: arm64 autopkgtest failure: ERROR: Illegal 
state encountered: �
Added tag(s) help.

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

Bug#969609: [Pkg-rust-maintainers] Bug#969609: rust-zstd: unbuildable, uninstallable, depends on non-existent rust-zstd-safe

[Ximin Luo]

Steve,

You keep filing these same bugs. I have told you this many times before 
already: this is just how rust packaging works, Britney's migration policy 
already prevents these packages from reaching Debian Testing, so there is no 
problem, no users are affected.

You filing these bug reports accomplishes nothing, except delay & annoy other 
Rust packagers who forget to close these pointless bugs, thereby unnecessarily 
blocking any fixed packages from actually reaching Debian Testing. Oftentimes 
the fix is also not to update the package itself, but to upload another 
package. Due to the idiosyncracies of the BTS, not everyone knows how to close 
these bugs correctly (notfound -1 $version) and it will result in further 
delays.

Please stop filing these bug reports, they only create extra unnecessary work 
for other people, and make Debian worse for users, by slowing down the stream 
of fixes. Britney already prevents Testing migration.

Ximin

Steve Langasek:
> Source: rust-zstd
> Version: 0.5.1-1
> Severity: grave
> 
> The rust-zstd package has both a dependency and a build-dependency on
> librust-zstd-safe-2.0.3+experimental-dev, which does not exist anywhere in
> Debian.  Presumably it would be built by a rust-zstd-safe package, but no
> such package exists, including in the Debian NEW queue.
> 
> The binaries of rust-zstd that are in Debian were clearly not built on the
> autobuilders, and all other architectures besides amd64 are unable to build
> this package.
> 
> 
> ___
> Pkg-rust-maintainers mailing list
> pkg-rust-maintain...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-rust-maintainers
> 


-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git

Bug#969493: src:nanook: fails to migrate to testing for too long: maintainer built arch:all binaries

[Andreas Tille]

Hi Paul,

On Mon, Sep 07, 2020 at 08:13:54PM +0200, Paul Gevers wrote:
> Control: tags -1 pending
> 
> On 03-09-2020 20:46, Paul Gevers wrote:
> > Your package is only blocked because the arch:all binary package(s)
> > aren't built on a buildd. Unfortunately the Debian infrastructure
> > doesn't allow arch:all packages to be properly binNMU'ed. Normally I
> > would do a no-changes source-only upload to DELAYED/15, closing this
> > bug, but I'm very limited on Internet at the moment.
> 
> I'm back on internet. I have just uploaded to DELAYED/15. Please let me
> know if I should delay or cancel.

Thanks a lot.  There is no point in any delay for Debian Med packages.

Kind regards

 Andreas.

-- 
http://fam-tille.de

Bug#969917: trimage: Trimage crashes with 10 or more png images

[Daniel]

Package: trimage
Version: 1.0.6-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: antonucci.d...@gmail.com

Dear Maintainer,

if you try to compress 10 or more images Trimage crashes with this output:

 File "/usr/lib/python3/dist-packages/trimage/trimage.py", line 286, in data
data = self.imagelist[index.row()][index.column()]
  File "/usr/lib/python3/dist-packages/trimage/trimage.py", line 340, in 
__getitem__
return self.d[key](self.image)
  File "/usr/lib/python3/dist-packages/trimage/trimage.py", line 308, in 

'filename_w_ext': lambda i: self.statusStr() % i.filename_w_ext,
TypeError: not all arguments converted during string formatting


Thanks for you attention,

Daniel


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

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

Versions of packages trimage depends on:
ii  advancecomp2.1-2.1
ii  jpegoptim  1.4.6-1
ii  optipng0.7.7-1+b1
ii  pngcrush   1.8.13-0.1
ii  python33.8.2-3
ii  python3-pyqt5  5.15.0+dfsg-1+b1

trimage recommends no packages.

trimage suggests no packages.

-- no debconf information

Bug#957948: wmmatrix: diff for NMU version 0.2-12.1

[Sudip Mukherjee]

Control: tags 957948 + patch
Control: tags 957948 + pending
--

Dear maintainer,

I've prepared an NMU for wmmatrix (versioned as 0.2-12.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should cancel it.

--
Regards
Sudip

diff -u wmmatrix-0.2/debian/changelog wmmatrix-0.2/debian/changelog
--- wmmatrix-0.2/debian/changelog
+++ wmmatrix-0.2/debian/changelog
@@ -1,3 +1,10 @@
+wmmatrix (0.2-12.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix ftbfs with GCC-10. (Closes: #957948)
+
+ -- Sudip Mukherjee   Tue, 08 Sep 2020 20:51:45 
+0100
+
 wmmatrix (0.2-12) unstable; urgency=low
 
   * Change Build-Depends: x11proto-core-dev. (Closes: #515407)
only in patch2:
unchanged:
--- wmmatrix-0.2.orig/xutils.c
+++ wmmatrix-0.2/xutils.c
@@ -63,10 +63,14 @@
 extern charTimeColor[30];
 extern charBackgroundColor[30];
 
-
-
-
-
+/*
+ *   Global variable
+ */
+Display*display;
+Window Root;
+Window iconwin, win;
+intscreen;
+intDisplayDepth;
 
 /*
  *   flush_expose
only in patch2:
unchanged:
--- wmmatrix-0.2.orig/xutils.h
+++ wmmatrix-0.2/xutils.h
@@ -18,11 +18,11 @@
 /*
  *   Global variable
  */
-Display*display;
-Window  Root;
-Window  iconwin, win;
-int screen; 
-int DisplayDepth;
+extern Display *display;
+extern Window  Root;
+extern Window  iconwin, win;
+extern int screen;
+extern int DisplayDepth;
 
 
 

Processed: wmmatrix: diff for NMU version 0.2-12.1

[Debian Bug Tracking System]

Processing control commands:

> tags 957948 + patch
Bug #957948 [src:wmmatrix] wmmatrix: ftbfs with GCC-10
Added tag(s) patch.
> tags 957948 + pending
Bug #957948 [src:wmmatrix] wmmatrix: ftbfs with GCC-10
Added tag(s) pending.

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

Bug#957920: marked as done (vpcs: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Tue, 08 Sep 2020 19:50:09 +
with message-id 
and subject line Bug#957920: fixed in vpcs 0.5b2-2.2
has caused the Debian Bug report #957920,
regarding vpcs: ftbfs with GCC-10
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.)


-- 
957920: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957920
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:vpcs
Version: 0.5b2-2.1
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/vpcs_0.5b2-2.1_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html

[...]
command6.c: In function ‘ip6Info’:
command6.c:752:20: warning: ‘%s’ directive writing up to 46 bytes into a region 
of size 44 [-Wformat-overflow=]
  752 |   sprintf(buf, "ip %s/%d", tmp, vpc[id].ip6.cidr);
  |^~  ~~~
In file included from /usr/include/stdio.h:867,
 from command6.c:28:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:36:10: note: 
‘__builtin___sprintf_chk’ output between 6 and 62 bytes into a destination of 
size 47
   36 |   return __builtin___sprintf_chk (__s, __USE_FORTIFY_LEVEL - 1,
  |  ^~
   37 |   __bos (__s), __fmt, __va_arg_pack ());
  |   ~
gcc  -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -DLinux -Wall -DTAP -DHV -Wno-strict-aliasing -c 
packets6.c
gcc  -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -DLinux -Wall -DTAP -DHV -Wno-strict-aliasing -c ip.c
gcc  -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -DLinux -Wall -DTAP -DHV -Wno-strict-aliasing -c tcp.c
gcc  -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -DLinux -Wall -DTAP -DHV -Wno-strict-aliasing -c inet6.c
gcc  -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -DLinux -Wall -DTAP -DHV -Wno-strict-aliasing -c dns.c
dns.c: In function ‘hostresolv’:
dns.c:64:41: warning: ‘__builtin___snprintf_chk’ output may be truncated before 
the last format character [-Wformat-truncation=]
   64 |snprintf(dname, sizeof(dname), "%s.%s", name, pc->ip4.dhcp.domain);
  | ^
In file included from /usr/include/stdio.h:867,
 from dns.c:27:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:67:10: note: 
‘__builtin___snprintf_chk’ output 2 or more bytes (assuming 65) into a 
destination of size 64
   67 |   return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
  |  ^~~~
   68 |__bos (__s), __fmt, __va_arg_pack ());
  |~
dns.c:62:41: warning: ‘__builtin___snprintf_chk’ output may be truncated before 
the last format character [-Wformat-truncation=]
   62 |snprintf(dname, sizeof(dname), "%s.%s", name, pc->ip4.domain);
  | ^
In file included from /usr/include/stdio.h:867,
 from dns.c:27:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:67:10: note: 
‘__builtin___snprintf_chk’ output 2 or more bytes (assuming 65) into a 
destination of size 64
 

Bug#966982: Uploading disabling that test to DELAYED/2

[Håvard Flaget Aasen]

tir. 8. sep. 2020 kl. 14:29 skrev Thomas Goirand :
>
> On 9/8/20 2:01 PM, Håvard Flaget Aasen wrote:
> > On Tue, 8 Sep 2020 13:40:25 +0200 Thomas Goirand  wrote:
> >> Hi,
> >>
> >> Since nobody seem to care about this, I've uploaded disabling that
> >> failing test to DELAYED/2. Indeed, to me, it looked like a broken test,
> >> rather than a broken package. Otherwise, a long list of reverse
> >> dependency will be removed from testing in 8 days.
> >>
> >> Debdiff of the change attached. Let me know if you would like me to
> >> cancel the upload.
> >>
> >> Cheers,
> >>
> >> Thomas Goirand (zigo)
> >
> > Thanks for this Thomas but I actually have a package up for RFS to
> > address this issue.
> > I must admit I removed all tests during build. Because of the same
> > reason.  same testsuite is being run as an autopkgtest which succeeds.
> > Previous there has also been some issues with these tests bug: [761325]
> > I intend to reopen this bug.
> >
> > Can I persuade you to review and upload my own package instead of doing
> > an NMU? bug: [965370] package in mentors [3]
> >
> > Thanks,
> > H??vard
> >
> > [761325] https://bugs.debian.org/761325
> > [965370] https://bugs.debian.org/965370
> > [3] https://mentors.debian.net/package/wand/
> >
>
> Hi Håvard,
>

Hi Thomas,

> I'm very much surprised by this. Why didn't you write in the bug report
> then, saying you've addressed the issue and was searching for a sponsor?

I guess the reason for that is my workflow, I work from a forked repo
and don't push it to the official until it has been released into
Debian. I will change this from now on, so the BTS can track when I
close a bug in salsa, and make it easier to collaborate with others.

> I had the impression that nobody cared, you know... And you can't expect
> everyone to closely monitor mentors.

I don't expect it, but for me, and many others, it's the only way to
get a sponsor.
There is a pane in the package tracker page, that informs about the RFS.

>
> I do not agree that removing all tests is the solution, when only a
> single one fails. I would happily sponsor your upload, but *not* if it's
> removing all tests.

I do agree with you that disabling all the tests isn't the best
option, but keep in mind that I enabled the testsuite with the last
release, and it didn't last much more than two months before a test
failed, because of the test, not the package. The testsuite had been
disabled for four years before that.
The autopkgtest also uses the same testsuite, which strangely enough succeeds.

If my reasoning isn't enough, I will comply and change the package to
only disable that one test.

>
> Cheers,
>
> Thomas Goirand (zigo)


Regards,
Håvard

Bug#965026: [CONFIRM] grub-emu is unusable with orca nor BRLTTY

[Dennis Filder]

I can reproduce the problem only by running grub-emu as root.  It is
reproducible in both the 2.02+dfsg1-20+deb10u2 (Buster) and 2.04-8
(current Bullseye).

The severity is not an exaggeration IMO as afterwards your machine
will be headless.  Recovering with Alt+SysRq+k does not work; neither
does restarting the X server.  I had to restart the machine every time
I ran grub-emu as root.  If logging in remotely is not an option,
pressing "Alt+SysRq+r" and then "Ctrl+Alt+Del" at least 8 times in
quick succession should make systemd reboot the machine cleanly as
long as this feature was not disabled.

For debugging purposes I added this as the first entry in grub.cfg:

  menuentry 'halt' {
  set timeout=5
  halt
  }

In non-SDL-mode it makes "grub-emu" exit normally even without
pressing any keys.

I see at least two problems at play:

 * grub-emu in SDL mode does not react in any way to key presses
   after starting

 * grub-emu in SDL mode does not restore the previous video mode even
   after exiting normally using the above grub.cfg snippet.

I think only these options are realistic:

* have upstream fix the bug
* compile with --disable-grub-emu-sdl
* stop shipping grub-emu altogether

Unless someone stops me I'll file a bug in the upstream tracker for
this 14 days from now.

Regards,
Dennis.

Bug#969803: awscli: autopkgtest should be marked superficial

[Noah Meyerhans]

On Tue, Sep 08, 2020 at 07:33:13PM +0100, Sudip Mukherjee wrote:
> > Short of communicating with a remote service, I'm not sure how we can
> > get more meaningful functional test coverage in this package, but it
> > would be nice to do so.
> 
> There is also another "Restrictions: needs-internet" which might be
> useful for you.
> Please check 
> https://sources.debian.org/data/main/a/autopkgtest/5.14/doc/README.package-tests.rst
> which has a section for "Network access". That says:
> "But for many packages their main purpose is to interact with remote
> web services and thus their testing should actually cover those too,
> to ensure that the distribution package keeps working with their
> corresponding web service.".

Yeah, the bigger issue there is not network access but authentication
credentials.  If there's a mechanism to allow us to provide credentials
in the test environment with reasonable expectations of security, then
we'd be very much interested in using that.  I haven't found evidence of
such support in Debian's CI infrastructure, though.

noah

Bug#969880: marked as done (wig: autopkgtest should be marked superficial)

[Debian Bug Tracking System]

Your message dated Tue, 08 Sep 2020 18:48:40 +
with message-id 
and subject line Bug#969880: fixed in wig 0.6-2
has caused the Debian Bug report #969880,
regarding wig: autopkgtest should be marked superficial
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.)


-- 
969880: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969880
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wig
Severity: serious
Usertags: superficialtest
X-Debbugs-CC: elb...@debian.org

Hi,

The test done in the autopkgtest of 'wig' does not provide
significant test coverage and it should be marked with "Restrictions:
superficial".

Ref: https://people.debian.org/~eriberto/README.package-tests.html

Examples of tests which are not significant includes (its not a
complete list):

1) Executing the binary to check version

Test-Command: foo -v

Test-Command: foo -V

Test-Command: foo --version

2) Executing the binary to check help (foo -h)

Test-Command: foo -h

Test-Command: foo --help

3) checking for files installed with 'ls'.

Test-Command: ls -l /usr/lib/*/foo.so

4) A Python or Perl library runs import foo or require Foo; but does
not attempt to use the library beyond that.

Test-Command: python3 -c "import foo"

Please add "Restrictions: superficial" to 'debian/tests/control' of
'wig'.

--

Sudip 
--- End Message ---
--- Begin Message ---
Source: wig
Source-Version: 0.6-2
Done: Samuel Henrique 

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

Debian distribution maintenance software
pp.
Samuel Henrique  (supplier of updated wig package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 08 Sep 2020 19:21:25 +0100
Source: wig
Architecture: source
Version: 0.6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Samuel Henrique 
Closes: 969880
Changes:
 wig (0.6-2) unstable; urgency=medium
 .
   [ Samuel Henrique ]
   * Bump DH to 13
   * Bump Standards-Version to 4.5.0
   * Add salsa-ci.yml
   * Configure git-buildpackage for Debian
   * d/t/control: Add superficial restriction (closes: #969880)
   * d/control: Add Rules-Requires-Root: no
 .
   [ Debian Janitor ]
   * Trim trailing whitespace.
   * Bump debhelper from old 11 to 12.
   * Set debhelper-compat version in Build-Depends.
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
 Repository-Browse.
Checksums-Sha1:
 44c80b6ca1275463a28938056cb8258af8a9da1f 1892 wig_0.6-2.dsc
 08e7f86d60ec19e7d2217edf1c4353531dc8f1e7 3636 wig_0.6-2.debian.tar.xz
 a455984b7c221f07bd42a1031f015ead1c9a4c08 5994 wig_0.6-2_amd64.buildinfo
Checksums-Sha256:
 d8bee19967e580eaa878c2c72e95a51ac0b8d90572f1366eab6ec9e7b1ee964f 1892 
wig_0.6-2.dsc
 6019901bd87de5755830687c96149d3f1142fb513627bc6c24698e4edc41a462 3636 
wig_0.6-2.debian.tar.xz
 d227a262f40cf83785a54b867c137308644d8f6888ec917e6af355668b6a6dab 5994 
wig_0.6-2_amd64.buildinfo
Files:
 9ee7ae5a854f64ca1340c5aa97dbc93c 1892 misc optional wig_0.6-2.dsc
 24530c47fc9c0a9e2abc7f8321388228 3636 misc optional wig_0.6-2.debian.tar.xz
 e9fc702ca6912e7b4a916505bdad394a 5994 misc optional wig_0.6-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEBdtqg34QX0sdAsVfu6n6rcz7RwcFAl9XzIoACgkQu6n6rcz7
RwcZfBAA0T4f5w6rR/8KgxQin/CCkGmmVl4zkRVQsj5Psj22V/KwtAkBtptfIZ1X
kSoYc2xNVtX1U1nWxnOpQiyj0tEogXoz5ecRdHOq5qr/hco3/gYCALRmTB13ZRBp
Yh7afI9PXTOLR8fK8QHUCT8Pr8AiNCyI+P1pwSSUqrAQO+1cBv0UFSl3fyGrEkvk
S30rXwzfXt+qgAQwuhrF0vHqDEPBs9GNk9hJyTt4j148PlCorW2zaWk/cYyUAzs8
oIELWNRnvTlwoU/9I0wtSza++oHwcbQpWfdapi//LL3Tdc0PiRvXGLCjztqiL9G1
4cnpZDOT+vYNtbatpeiT3hEyZQzct/K2Faa7OvqmlCIZL+UlTx+BXKGXrsVYJr59
aNXfYhuazTbr2uQmBOLGutD7WIkxwETcOelrJ7cwzskajpoBbQF8eahx/n8zCiv5
DzMOcJHBFCdFVfj7ZKOuMGsqKBb4X4sVE4ChQJLCZxGxh60BVoHKHTn7W8eOLLMI
f1kDiYFkXQ/qErySqTN1LhEY2ew+7BLMqL2OzdBwQCuSed5u7LPEKLCPCQ+/trH8
aRumpyA8F0msO6zH/kdid0kOlYaeWiRWr13d5XmOFXrKBdNg5f4fyijpafkgdlc9
NDOSLfs4HKHxYdFR5R+JCO89K6eSVy91rK2KMF2Xq6yRn5h6osI=
=Q1E+
-END PGP SIGNATURE End Message ---

Bug#969803: awscli: autopkgtest should be marked superficial

[Paul Gevers]

Hi Noah, all,

On 08-09-2020 20:33, Sudip Mukherjee wrote:
> On Tue, Sep 8, 2020 at 5:48 PM Noah Meyerhans  wrote:
>>
>> On Tue, Sep 08, 2020 at 10:38:18AM +0100, Sudip Mukherjee wrote:
>>> The test done in the autopkgtest of 'awscli' does not provide
>>> significant test coverage and it should be marked with "Restrictions:
>>> superficial".
>>
>> The current test merely invokes "/usr/bin/aws help".  Is there any
>> actual value in this test at all?  Should we just remove it?
> 
> I think you can keep it and mark it superficial. This will atleast
> show you that it has built properly and is executing.

That. And that your dependencies don't suddenly break your binary
completely.

>> Short of communicating with a remote service, I'm not sure how we can
>> get more meaningful functional test coverage in this package, but it
>> would be nice to do so.
> 
> There is also another "Restrictions: needs-internet" which might be
> useful for you.
> Please check 
> https://sources.debian.org/data/main/a/autopkgtest/5.14/doc/README.package-tests.rst
> which has a section for "Network access". That says:
> "But for many packages their main purpose is to interact with remote
> web services and thus their testing should actually cover those too,
> to ensure that the distribution package keeps working with their
> corresponding web service.".

Please be aware that relying on remote service may make you test become
flaky, depending on the reliability of the service now and in the
future. Not saying those tests should be added, but just a thought about
them.
> Also, Paul might have some more suggestions.

Well, there is a bug open for advanced support in autopkgtest itself:
#908274 Please add the capability to run tests that require a server.
Not sure if that's feasible for awscli if autopkgtest would grow that
feature.

Paul




signature.asc
Description: OpenPGP digital signature

Bug#969872: marked as done (termineter: autopkgtest should be marked superficial)

[Debian Bug Tracking System]

Your message dated Tue, 08 Sep 2020 18:37:22 +
with message-id 
and subject line Bug#969872: fixed in termineter 1.0.4-2
has caused the Debian Bug report #969872,
regarding termineter: autopkgtest should be marked superficial
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.)


-- 
969872: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969872
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: termineter
Severity: serious
Usertags: superficialtest
X-Debbugs-CC: elb...@debian.org

Hi,

The test done in the autopkgtest of 'termineter' does not provide
significant test coverage and it should be marked with "Restrictions:
superficial".

Ref: https://people.debian.org/~eriberto/README.package-tests.html

Examples of tests which are not significant includes (its not a
complete list):

1) Executing the binary to check version

Test-Command: foo -v

Test-Command: foo -V

Test-Command: foo --version

2) Executing the binary to check help (foo -h)

Test-Command: foo -h

Test-Command: foo --help

3) checking for files installed with 'ls'.

Test-Command: ls -l /usr/lib/*/foo.so

4) A Python or Perl library runs import foo or require Foo; but does
not attempt to use the library beyond that.

Test-Command: python3 -c "import foo"

Please add "Restrictions: superficial" to 'debian/tests/control' of
'termineter'.

--

Sudip 
--- End Message ---
--- Begin Message ---
Source: termineter
Source-Version: 1.0.4-2
Done: Samuel Henrique 

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

Debian distribution maintenance software
pp.
Samuel Henrique  (supplier of updated termineter package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 08 Sep 2020 19:05:47 +0100
Source: termineter
Architecture: source
Version: 1.0.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Samuel Henrique 
Closes: 969872
Changes:
 termineter (1.0.4-2) unstable; urgency=medium
 .
   [ Samuel Henrique ]
   * Add salsa-ci.yml
   * Configure git-buildpackage for Debian
   * Bump DH to 13
   * d/control: Add Rules-Requires-Root: no
   * Bump Standards-Version to 4.5.0
   * d/t/control: Add superficial restriction (closes: #969872)
 .
   [ Debian Janitor ]
   * Trim trailing whitespace.
   * Use secure copyright file specification URI.
   * Bump debhelper from old 11 to 12.
   * Set debhelper-compat version in Build-Depends.
   * Set upstream metadata fields: Repository, Repository-Browse.
   * Update standards version to 4.2.1, no changes needed.
Checksums-Sha1:
 9ba1779aee3d694165636a75e7755d8b33e5f24e 2032 termineter_1.0.4-2.dsc
 402da0db5f0da3b211337e0e6b8ac806cc62237d 3444 termineter_1.0.4-2.debian.tar.xz
 8b157fec37006fe93510b06d20f86fb303fcfb66 6157 
termineter_1.0.4-2_amd64.buildinfo
Checksums-Sha256:
 ae1ebd0c655f50a96083009c90ee58f1e0afbd93a52392898922305992beb3bb 2032 
termineter_1.0.4-2.dsc
 acad196487db3780350ce62035d0ed43bcdb269bfa7081a7aa8816f69fc0c3c9 3444 
termineter_1.0.4-2.debian.tar.xz
 66197441e9db6a7afe5ca448af6583eeba5ced79b9dcd64eabbdbaff5e0b4165 6157 
termineter_1.0.4-2_amd64.buildinfo
Files:
 692bcc30e8841c534187d0a052910da8 2032 utils optional termineter_1.0.4-2.dsc
 2da86189e6a58498258503a19d03de11 3444 utils optional 
termineter_1.0.4-2.debian.tar.xz
 3c9bf62a1c4d3ab9861e841497ee6ea5 6157 utils optional 
termineter_1.0.4-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEBdtqg34QX0sdAsVfu6n6rcz7RwcFAl9XyMwACgkQu6n6rcz7
Rwc+TRAAhTDyk0hVUfoa9mR1L4j3vc7oUdZoxAO91cT2sx+gIVX5hg/vyfpi6lIz
iSqHmLlvgLo7W29ywkNhSudFVEm3yk0Vl+I5zkaWCu+EzNOQaUmlaDmfXcUh2raL
VTM2SgxQF+HCx9kLJH71kPzxUOl6wBnliiEk36uNqtvssnx0Mfbh4NxRsei2tvaq
oosDQM1tipmneYZrxOcu/MHP5Sp5aUMux8o+BRwDT7qSzZ33ZKQVNN8lIiXKFbCK
5zJn4GCT15eSpieFp9O55brq5XLDzybnXF/aAlFFtcf2skdTsr4aXN2cSXbXSeLH
RUiqkBhv5k3g80ijaM7mH661NHdzX9Hbh32hZWFbeXhdKPS0a1KmQA3sXL9axE4r
7VZPdzT9Fk0xidxdlS5958qmVPGXASPMqwMA2z+9wzuF8O1HSYog7EYNzstp3vpR
HznJCng7T3tWHN+my1as7j6iSjV1YoZShPTEk7TmLjSih4BrMRcqwFyGtHzLx1Yk

Bug#957133: marked as done (dia2code: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Tue, 08 Sep 2020 18:33:49 +
with message-id 
and subject line Bug#957133: fixed in dia2code 0.8.3-4.1
has caused the Debian Bug report #957133,
regarding dia2code: ftbfs with GCC-10
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.)


-- 
957133: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957133
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:dia2code
Version: 0.8.3-4
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/dia2code_0.8.3-4_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html

[...]
  177 | fprintf(outfile,"# 
XXX\n",tmplist->key->comment);
  | ^
gcc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/include/libxml2  -Wdate-time 
-D_FORTIFY_SOURCE=2 -DDSO  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c `test -f 'main.c' 
|| echo './'`main.c
rm -f libdia2code.a
ar cru libdia2code.a decls.o includes.o generate_code_idl.o generate_code_php.o 
generate_code_php_five.o generate_code_shp.o generate_code_python.o 
generate_code_ada.o generate_code_sql.o scan_tree.o generate_code_c.o 
parse_diagram.o dia2code.o generate_code_java.o generate_code_cpp.o 
generate_code_csharp.o generate_code_ruby.o main.o 
ar: `u' modifier ignored since `D' is the default (see `U')
ranlib libdia2code.a
gcc  -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security  -Wl,-z,relro -rdynamic -o dia2code  
dia2code.o main.o parse_diagram.o scan_tree.o generate_code_c.o 
generate_code_java.o generate_code_cpp.o generate_code_ada.o 
generate_code_sql.o generate_code_python.o generate_code_php.o 
generate_code_shp.o generate_code_idl.o generate_code_csharp.o 
generate_code_php_five.o generate_code_ruby.o decls.o includes.o  -lxml2 -ldl
/usr/bin/ld: main.o:./dia2code/dia2code.h:268: multiple definition of 
`indent_open_brace_on_newline'; dia2code.o:./dia2code/dia2code.h:268: first 
defined here
/usr/bin/ld: main.o:./dia2code/dia2code.h:267: multiple definition of 
`indent_count'; dia2code.o:./dia2code/dia2code.h:267: first defined here
/usr/bin/ld: main.o:./dia2code/dia2code.h:269: multiple definition of 
`generate_backup'; dia2code.o:./dia2code/dia2code.h:269: first defined here
/usr/bin/ld: parse_diagram.o:./dia2code/dia2code.h:269: multiple definition of 
`generate_backup'; dia2code.o:./dia2code/dia2code.h:269: first defined here
/usr/bin/ld: parse_diagram.o:./dia2code/dia2code.h:268: multiple definition of 
`indent_open_brace_on_newline'; dia2code.o:./dia2code/dia2code.h:268: first 
defined here
/usr/bin/ld: parse_diagram.o:./dia2code/dia2code.h:267: multiple definition of 
`indent_count'; dia2code.o:./dia2code/dia2code.h:267: first defined here
/usr/bin/ld: scan_tree.o:./dia2code/dia2code.h:269: multiple definition of 
`generate_backup'; dia2code.o:./dia2code/dia2code.h:269: first defined here
/usr/bin/ld: scan_tree.o:./dia2code/dia2code.h:268: multiple definition of 
`indent_open_brace_on_newline'; dia2code.o:./dia2code/dia2code.h:268: first 
defined here
/usr/bin/ld: scan_tree.o:./dia2code/dia2code.h:267: multiple definition of 
`indent_count'; dia2code.o:./dia2code/dia2code.h:267: first defined here
/usr/bin/ld: generate_code_c.o:./dia2code/dia2code.h:269: multiple definition 
of `generate_backup'; dia2code.o:./dia2code/dia2code.h:269: first defined here
/usr/bin/ld: generate_code_c.o:./dia2code/dia2code.h:268: multiple definition 

Bug#969803: awscli: autopkgtest should be marked superficial

[Sudip Mukherjee]

Hi Noah,

On Tue, Sep 8, 2020 at 5:48 PM Noah Meyerhans  wrote:
>
> On Tue, Sep 08, 2020 at 10:38:18AM +0100, Sudip Mukherjee wrote:
> > The test done in the autopkgtest of 'awscli' does not provide
> > significant test coverage and it should be marked with "Restrictions:
> > superficial".
>
> The current test merely invokes "/usr/bin/aws help".  Is there any
> actual value in this test at all?  Should we just remove it?

I think you can keep it and mark it superficial. This will atleast
show you that it has built properly and is executing.

>
> Short of communicating with a remote service, I'm not sure how we can
> get more meaningful functional test coverage in this package, but it
> would be nice to do so.

There is also another "Restrictions: needs-internet" which might be
useful for you.
Please check 
https://sources.debian.org/data/main/a/autopkgtest/5.14/doc/README.package-tests.rst
which has a section for "Network access". That says:
"But for many packages their main purpose is to interact with remote
web services and thus their testing should actually cover those too,
to ensure that the distribution package keeps working with their
corresponding web service.".

Also, Paul might have some more suggestions.


-- 
Regards
Sudip

Processed: [Help] Re: r-cran-rstanarm: FTBFS: error: (converted from warning) TBB library not found.

[Debian Bug Tracking System]

Processing control commands:

> tags -1 help
Bug #963392 [src:r-cran-rstanarm] r-cran-rstanarm: FTBFS: error: (converted 
from warning) TBB library  not found.
Added tag(s) help.

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

Bug#963392: [Help] Re: r-cran-rstanarm: FTBFS: error: (converted from warning) TBB library not found.

[Andreas Tille]

Control: tags -1 help

Hi,

any help why TBB is not found?  I think this issue is actually causes by
r-cran-rcppparallel since the code copy of libtbb was removed there -
but it seems to not provide the Debian packaged lib properly.

Kind regards

Andreas.

-- 
http://fam-tille.de

Bug#969880: marked as pending in wig

[Samuel Henrique]

Control: tag -1 pending

Hello,

Bug #969880 in wig 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/pkg-security-team/wig/-/commit/16c84ecf61e3d9d48e73a7913e761637bdb26981


d/t/control: Add superficial restriction (closes: #969880)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/969880

Processed: Bug#969880 marked as pending in wig

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #969880 [src:wig] wig: autopkgtest should be marked superficial
Added tag(s) pending.

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

Bug#969810: marked as done (changeme: autopkgtest should be marked superficial)

[Debian Bug Tracking System]

Your message dated Tue, 08 Sep 2020 18:18:39 +
with message-id 
and subject line Bug#969810: fixed in changeme 1.2.3-2
has caused the Debian Bug report #969810,
regarding changeme: autopkgtest should be marked superficial
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.)


-- 
969810: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969810
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: changeme
Severity: serious
Usertags: superficialtest
X-Debbugs-CC: elb...@debian.org

Hi,

The test done in the autopkgtest of 'changeme' does not provide
significant test coverage and it should be marked with "Restrictions:
superficial".

Ref: https://people.debian.org/~eriberto/README.package-tests.html

Examples of tests which are not significant includes (its not a
complete list):

1) Executing the binary to check version

Test-Command: foo -v

Test-Command: foo -V

Test-Command: foo --version

2) Executing the binary to check help (foo -h)

Test-Command: foo -h

Test-Command: foo --help

3) checking for files installed with 'ls'.

Test-Command: ls -l /usr/lib/*/foo.so

4) A Python or Perl library runs import foo or require Foo; but does
not attempt to use the library beyond that.

Test-Command: python3 -c "import foo"

Please add "Restrictions: superficial" to 'debian/tests/control' of
'changeme'.

--

Sudip 
--- End Message ---
--- Begin Message ---
Source: changeme
Source-Version: 1.2.3-2
Done: Samuel Henrique 

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

Debian distribution maintenance software
pp.
Samuel Henrique  (supplier of updated changeme package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 08 Sep 2020 18:56:37 +0100
Source: changeme
Architecture: source
Version: 1.2.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Samuel Henrique 
Closes: 969810
Changes:
 changeme (1.2.3-2) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
 Repository-Browse.
 .
   [ Samuel Henrique ]
   * d/t/control: Add superficial restriction (closes: #969810)
Checksums-Sha1:
 0e6ec626534e5ff2b1a515fd8ae1901efc56b4ff 1965 changeme_1.2.3-2.dsc
 73cfc7c4b7c4f2d1382e4d2599babd5bfbe0e949 3080 changeme_1.2.3-2.debian.tar.xz
 659e911bcd92bbcf78b1553055de6b3c363b9039 6057 changeme_1.2.3-2_amd64.buildinfo
Checksums-Sha256:
 0c61c56a1e423f5201683b29abc2cbd589a5d2f8baf4a82dd714efeb26b0e175 1965 
changeme_1.2.3-2.dsc
 24f7194ec807d66981d3976a03a281335cd250d109216867b783b5cf194bcb14 3080 
changeme_1.2.3-2.debian.tar.xz
 e314e4d1dca101bf3fb7913c04ce760502caa7f7febef15d590b279a11412fbb 6057 
changeme_1.2.3-2_amd64.buildinfo
Files:
 ed380bbb33b7a9e9fe5a431ee0cea03e 1965 misc optional changeme_1.2.3-2.dsc
 856fc3504c34e5fbce96e8669eafbbe3 3080 misc optional 
changeme_1.2.3-2.debian.tar.xz
 0911837a4abe83db7eb5d16101003e2b 6057 misc optional 
changeme_1.2.3-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEBdtqg34QX0sdAsVfu6n6rcz7RwcFAl9XxkYACgkQu6n6rcz7
Rwfgug//Zut4vTZgy3UR0e8lGzfBarPei+okhxOLeNztp8a7dNkyvtNr6CkaX03+
llZ6Y4MOBm+650WepfMJK6UUWHMqaeUrbWHr5URqq61RlycOtIb2RW0cGDy1sDdK
d/cAP1CARe1gp2KNkwmzD9uIPWg8Dq9ekhZ5lLuFfTCBsCL9rv1XyXyYgJxiIAGg
IIlbXwfeNeM3W1VhfuFH5AyNTjXg0eS+JYARv8gwCnbjF5MZQJN9LpJL8u8gcKy6
pWCL1pKe5+D3ulsNdGlHuKXMIymgQX9FZ8pQCzW4Sjq8YPvN2+S3+V/VCkNPzeDp
XrzXDAnF6PmnTwYcvvRvTSJShiOyuZ+dik6mybUVur1QAq6LvLU6lOf595cTyLnO
zgCdFBDSsjIIY15X/7jid4RFLpUd032jOpc1moGpHfa1NPWD0myS2hoh7ZN+99fw
1ueNvSyXer9HmhQnb6MrICjYySuAinmMjCRlkRPd02EGThy5JsvpIiLYyLL2BkFe
TgjnNRsM4liYuUlpwuDrCig7LFTfi+4W4LbHv9O3yuTmNV2aTffgW3Tdc/wNzqa3
MkTGjiKDW9s73yr2hAfXZMul7Hvq/bx45CUd4uaCfYc2yqohLlaHqrIACXYX9PpS
daupvDJMTx4zMaeAOk8J3vtnfkDf/m1v0mS+DO6P3avFMZur2Dg=
=30gL
-END PGP SIGNATURE End Message ---

Processed: Bug#969872 marked as pending in termineter

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #969872 [src:termineter] termineter: autopkgtest should be marked 
superficial
Added tag(s) pending.

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

Bug#969872: marked as pending in termineter

[Samuel Henrique]

Control: tag -1 pending

Hello,

Bug #969872 in termineter 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/pkg-security-team/termineter/-/commit/f1334dab0521dcb9bde0792fd6692931f8a838dd


d/t/control: Add superficial restriction (closes: #969872)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/969872

Bug#969868: marked as done (smbmap: autopkgtest should be marked superficial)

[Debian Bug Tracking System]

Your message dated Tue, 08 Sep 2020 18:06:22 +
with message-id 
and subject line Bug#969868: fixed in smbmap 1.8.2-2
has caused the Debian Bug report #969868,
regarding smbmap: autopkgtest should be marked superficial
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.)


-- 
969868: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969868
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: smbmap
Severity: serious
Usertags: superficialtest
X-Debbugs-CC: elb...@debian.org

Hi,

The test done in the autopkgtest of 'smbmap' does not provide
significant test coverage and it should be marked with "Restrictions:
superficial".

Ref: https://people.debian.org/~eriberto/README.package-tests.html

Examples of tests which are not significant includes (its not a
complete list):

1) Executing the binary to check version

Test-Command: foo -v

Test-Command: foo -V

Test-Command: foo --version

2) Executing the binary to check help (foo -h)

Test-Command: foo -h

Test-Command: foo --help

3) checking for files installed with 'ls'.

Test-Command: ls -l /usr/lib/*/foo.so

4) A Python or Perl library runs import foo or require Foo; but does
not attempt to use the library beyond that.

Test-Command: python3 -c "import foo"

Please add "Restrictions: superficial" to 'debian/tests/control' of
'smbmap'.

--

Sudip 
--- End Message ---
--- Begin Message ---
Source: smbmap
Source-Version: 1.8.2-2
Done: Samuel Henrique 

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

Debian distribution maintenance software
pp.
Samuel Henrique  (supplier of updated smbmap package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 08 Sep 2020 18:51:11 +0100
Source: smbmap
Architecture: source
Version: 1.8.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Samuel Henrique 
Closes: 969868
Changes:
 smbmap (1.8.2-2) unstable; urgency=medium
 .
   * Bump DH to 13
   * d/t/control: Add superficial restriction (closes: #969868)
Checksums-Sha1:
 eb819a9c1cc21e8ef111acb71370a9fc2197566a 1945 smbmap_1.8.2-2.dsc
 ff431d57639c2c1bbd485ee53fbe696c5d96610d 4528 smbmap_1.8.2-2.debian.tar.xz
 a473423dbb5cfbfe65574e4767df2354224fabd9 6037 smbmap_1.8.2-2_amd64.buildinfo
Checksums-Sha256:
 757e34b94fc7fcbc66c623b58b58cee053a12854bcbb5d561cfcfaf91b3c69cf 1945 
smbmap_1.8.2-2.dsc
 8dfccdf8d568d880ac467467d981fe96cf47e1c705860bc1e45048cd9975d1dc 4528 
smbmap_1.8.2-2.debian.tar.xz
 06cf47ea9f222fad13e5e3c81d740ac5b8dd20ec66197e96b81cafb7f5964633 6037 
smbmap_1.8.2-2_amd64.buildinfo
Files:
 4c2c107c964fa288589e4439e97363d8 1945 misc optional smbmap_1.8.2-2.dsc
 41283a180d199450768687c6bc0e40d6 4528 misc optional 
smbmap_1.8.2-2.debian.tar.xz
 a97e96bbbc88a0988756fb7d01acae37 6037 misc optional 
smbmap_1.8.2-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEBdtqg34QX0sdAsVfu6n6rcz7RwcFAl9XxPcACgkQu6n6rcz7
RwfrHg/7BDV+shX+LXgWID9nBEJ1obf0OcBp+vyu0a6R7zmcqn6iYQT+akL4LqnA
gr4cPZU2s11mAVP8LfjKJvlxhwjVjW6cx8Z+FUvUV5+qzMCq0e0LCGazj0KhPtnV
7eF02p8p9fnVLkC0JFb0/1+rphZ9drGk7frTILs/nYt3aZTsVA8cNowW6lPxmkzZ
m39hbSd0pI+NWchToW6jDgagya76KyyiwpGJbLr22RK3K9B3cIicTxEeVQrZJaHB
WkSxz/A6+5Wc0aLBtlNGT4nEor+rwCCbJE+U52mMZqf/9c+ZaWz274hrTViGsIHf
yd2jTK0cN0lXofIyzSBwqomqTE6+LT8GWR8aVXEVZH97C+Xps/QfYXb6fIUu+A9Z
Verhgc+NuU5XfP2GkT2ycjBjdtLnociNKzNZvsUjSmZHrt2vu8i4zSde8uXPu/yb
rW15B/494GFFTlkLTHP3TBTNzKMoFqQK4pQg7nI6goasvkII0Bvpq4tEsEtLFFM9
thfdQr5f7D62IJ/k68UGTpVG0NinMlG30bJMKXwibr6A6FTnLaZVPzJ/KQg9dzdw
Oi0EIJs7pTSURc3e1xVsgwrdfgby1u6BvFXEOeXgPDpzm628/BW2cva8HqWrzxqr
EwB0hG+7Y9bSqXJ6I9v34tOmJ9qEscLfIOX0TcJYiWBQyYh1J6Y=
=GL8P
-END PGP SIGNATURE End Message ---

Bug#969810: marked as pending in changeme

[Samuel Henrique]

Control: tag -1 pending

Hello,

Bug #969810 in changeme 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/pkg-security-team/changeme/-/commit/fb963c7447da14d6dd93a72b6c348be7caa307cd


d/t/control: Add superficial restriction (closes: #969810)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/969810

Processed: Bug#969810 marked as pending in changeme

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #969810 [src:changeme] changeme: autopkgtest should be marked superficial
Added tag(s) pending.

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

Processed: Bug#969868 marked as pending in smbmap

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #969868 [src:smbmap] smbmap: autopkgtest should be marked superficial
Added tag(s) pending.

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

Bug#969868: marked as pending in smbmap

[Samuel Henrique]

Control: tag -1 pending

Hello,

Bug #969868 in smbmap 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/pkg-security-team/smbmap/-/commit/6922fd85020fb525caa54e215c9ec1320f95e6dd


d/t/control: Add superficial restriction (closes: #969868)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/969868

Bug#969901: marked as done (torbrowser-launcher: depends on /usr/bin/gpg2 but dependency not expressed)

[Debian Bug Tracking System]

Your message dated Tue, 08 Sep 2020 17:34:10 +
with message-id 
and subject line Bug#969901: fixed in torbrowser-launcher 0.3.2-13
has caused the Debian Bug report #969901,
regarding torbrowser-launcher: depends on /usr/bin/gpg2 but dependency not 
expressed
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.)


-- 
969901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969901
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: torbrowser-launcher
Version: 0.3.2-11~bpo10+1
Severity: serious
Justification: Policy 3.5

There's a few things going on in this session, but this bug report is
about the last backtrace in particular:

$ torbrowser-launcher
Tor Browser Launcher
By Micah Lee, licensed under MIT
version 0.3.2
https://github.com/micahflee/torbrowser-launcher
Creating GnuPG homedir /home/jon/.local/share/torbrowser/gnupg_homedir
Downloading Tor Browser for the first time.
Downloading 
https://aus1.torproject.org/torbrowser/update_3/release/Linux_x86_64-gcc3/x/en-US
Latest version: 9.5.4
Downloading 
https://dist.torproject.org/torbrowser/9.5.4/tor-browser-linux64-9.5.4_en-US.tar.xz.asc
Downloading 
https://dist.torproject.org/torbrowser/9.5.4/tor-browser-linux64-9.5.4_en-US.tar.xz
Verifying Signature
Refreshing local keyring...
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/torbrowser_launcher/launcher.py", line 
589, in verify
c.verify(signature=sig, signed_data=signed)
  File "/usr/lib/python3/dist-packages/gpg/core.py", line 559, in verify
raise errors.BadSignatures(results[1], results=results)
gpg.errors.BadSignatures: 110775B5D101FB36BC6C911BEB774491D9FF06E2: Key expired

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/torbrowser_launcher/launcher.py", line 
600, in run
verify()
  File "/usr/lib/python3/dist-packages/torbrowser_launcher/launcher.py", line 
594, in verify
raise Exception
Exception

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/torbrowser_launcher/launcher.py", line 
603, in run
self.common.refresh_keyring()
  File "/usr/lib/python3/dist-packages/torbrowser_launcher/common.py", line 
209, in refresh_keyring
'--refresh-keys'], stderr=subprocess.PIPE)
  File "/usr/lib/python3.7/subprocess.py", line 775, in __init__
restore_signals, start_new_session)
  File "/usr/lib/python3.7/subprocess.py", line 1522, in _execute_child
raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: '/usr/bin/gpg2': 
'/usr/bin/gpg2'
Aborted




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

Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages torbrowser-launcher depends on:
ii  ca-certificates   20190110
ii  libdbus-glib-1-2  0.110-4
ii  python3   3.7.3-1
ii  python3-gpg   1.12.0-6
ii  python3-pyqt5 5.11.3+dfsg-1+b3
ii  python3-requests  2.21.0-1
ii  python3-socks 1.6.8+dfsg-1

Versions of packages torbrowser-launcher recommends:
ii  tor  0.3.5.10-1

Versions of packages torbrowser-launcher suggests:
ii  apparmor  2.13.2-10

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: torbrowser-launcher
Source-Version: 0.3.2-13
Done: Roger Shimizu 

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

Debian distribution maintenance software
pp.
Roger Shimizu  (supplier of updated torbrowser-launcher 
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

Bug#969803: awscli: autopkgtest should be marked superficial

[Noah Meyerhans]

On Tue, Sep 08, 2020 at 10:38:18AM +0100, Sudip Mukherjee wrote:
> The test done in the autopkgtest of 'awscli' does not provide
> significant test coverage and it should be marked with "Restrictions:
> superficial".

The current test merely invokes "/usr/bin/aws help".  Is there any
actual value in this test at all?  Should we just remove it?

Short of communicating with a remote service, I'm not sure how we can
get more meaningful functional test coverage in this package, but it
would be nice to do so.

noah

Bug#966982: Uploading disabling that test to DELAYED/2

[Håvard Flaget Aasen]

On Tue, 8 Sep 2020 13:40:25 +0200 Thomas Goirand  wrote:
> Hi,
> 
> Since nobody seem to care about this, I've uploaded disabling that
> failing test to DELAYED/2. Indeed, to me, it looked like a broken test,
> rather than a broken package. Otherwise, a long list of reverse
> dependency will be removed from testing in 8 days.
> 
> Debdiff of the change attached. Let me know if you would like me to
> cancel the upload.
> 
> Cheers,
> 
> Thomas Goirand (zigo)

Thanks for this Thomas but I actually have a package up for RFS to
address this issue.
I must admit I removed all tests during build. Because of the same
reason.  same testsuite is being run as an autopkgtest which succeeds.
Previous there has also been some issues with these tests bug: [761325]
I intend to reopen this bug.

Can I persuade you to review and upload my own package instead of doing
an NMU? bug: [965370] package in mentors [3]

Thanks,
H??vard

[761325] https://bugs.debian.org/761325
[965370] https://bugs.debian.org/965370
[3] https://mentors.debian.net/package/wand/

Processed: reopening 969907

[Debian Bug Tracking System]

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

> reopen 969907
Bug #969907 {Done: David Bremner } [libpoppler-glib8] 
libpoppler-glib8: introduces new ABI without bumping shlibs version
Bug reopened
Ignoring request to alter fixed versions of bug #969907 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: found 964902 in 0.39-1

[Debian Bug Tracking System]

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

> found 964902 0.39-1
Bug #964902 {Done: Dominic Hargreaves } [libio-socket-ip-perl] 
libio-socket-ip-perl: AI_ADDRCONFIG breaks many test suites on IPv6-only hosts
Marked as found in versions libio-socket-ip-perl/0.39-1.
> thanks
Stopping processing here.

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

Bug#957526: marked as done (medusa: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Tue, 08 Sep 2020 15:35:30 +
with message-id 
and subject line Bug#957526: fixed in medusa 2.2-7
has caused the Debian Bug report #957526,
regarding medusa: ftbfs with GCC-10
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.)


-- 
957526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957526
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:medusa
Version: 2.2-6
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/medusa_2.2-6_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html

[...]
  |  ^~
web-form.c: In function ‘go’:
web-form.c:190:11: note: length computed here
  190 |   strncpy(psSessionData->szFormData, pOpt, strlen(pOpt));
  |   ^~
In file included from /usr/include/string.h:495,
 from ../medusa-net.h:27,
 from module.h:35,
 from web-form.c:32:
In function ‘strncpy’,
inlined from ‘go’ at web-form.c:176:11:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:10: warning: 
‘__builtin_strncpy’ specified bound depends on the length of the source 
argument [-Wstringop-overflow=]
  106 |   return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest));
  |  ^~
web-form.c: In function ‘go’:
web-form.c:176:11: note: length computed here
  176 |   strncpy(psSessionData->szDenySignal, pOpt, strlen(pOpt));
  |   ^~~~
In file included from /usr/include/string.h:495,
 from ../medusa-net.h:27,
 from module.h:35,
 from web-form.c:32:
In function ‘strncpy’,
inlined from ‘go’ at web-form.c:162:11:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:10: warning: 
‘__builtin_strncpy’ specified bound depends on the length of the source 
argument [-Wstringop-overflow=]
  106 |   return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest));
  |  ^~
web-form.c: In function ‘go’:
web-form.c:162:11: note: length computed here
  162 |   strncpy(psSessionData->szDir, pOpt, strlen(pOpt));
  |   ^
gcc  -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -fPIC  -Wl,-z,relro -Wl,-z,now 
-L/usr/local/lib -L/usr//lib -rdynamic  -o cvs.mod cvs.o ../medusa-trace.o -lpq 
 -lssh2 -lsvn_client-1 -shared -ldl -lpthread  -lssl -lcrypto -lssl -lcrypto 
-lgcrypt -lgnutls -ldl -lrt -lm
gcc  -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -fPIC -Wl,-z,relro -Wl,-z,now -L/usr/local/lib 
-L/usr//lib -rdynamic  -o ftp.mod ftp.o ../medusa-trace.o -lpq  -lssh2 
-lsvn_client-1 -shared -ldl -lpthread  -lssl -lcrypto -lssl -lcrypto -lgcrypt 
-lgnutls -ldl -lrt -lm
/usr/bin/ld: /usr/bin/ld: ../medusa-trace.o:./src/modsrc/../medusa.h:68: 
multiple definition of `iVerboseLevel'; 
../medusa-trace.o:./src/modsrc/../medusa.h:68: multiple definition of 
`iVerboseLevel'; cvs.o:./src/modsrc/../medusa.h:68: first defined here
/usr/bin/ld: ../medusa-trace.o:./src/modsrc/../medusa.h:66: multiple definition 
of `pOutputFile'; cvs.o:./src/modsrc/../medusa.h:66: first defined here

Bug#961211: marked as done (r-cran-lwgeom: autopkgtest failures on s390x)

[Debian Bug Tracking System]

Your message dated Tue, 08 Sep 2020 15:26:04 +
with message-id 
and subject line Bug#961211: fixed in r-cran-lwgeom 0.2-5-2
has caused the Debian Bug report #961211,
regarding r-cran-lwgeom: autopkgtest failures on s390x
to be marked as done.

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

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


-- 
961211: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961211
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-lwgeom
Version: 0.2-3-1
Severity: serious

Hello, looks like some changes in r-cran-lwgeom/proj/geom made the testsuite 
fail with the latest versions
of the programs in sid.
Looks like an endianess regression introduced in the last version fo lwgeom, 
can you please have a look?

I'm attaching a log taken from a test on zelenka.debian.org

thanks

Gianfranco
BEGIN TEST azimuth.R

R version 4.0.0 (2020-04-24) -- "Arbor Day"
Copyright (C) 2020 The R Foundation for Statistical Computing
Platform: s390x-ibm-linux-gnu (64-bit)

R is free software and comes with ABSOLUTELY NO WARRANTY.
You are welcome to redistribute it under certain conditions.
Type 'license()' or 'licence()' for distribution details.

R is a collaborative project with many contributors.
Type 'contributors()' for more information and
'citation()' on how to cite R or R packages in publications.

Type 'demo()' for some demos, 'help()' for on-line help, or
'help.start()' for an HTML browser interface to help.
Type 'q()' to quit R.

> suppressPackageStartupMessages(library(sf))
> suppressPackageStartupMessages(library(lwgeom))
> p = st_sfc(st_point(c(7,52)), st_point(c(8,53)), crs = 4326)
> st_geod_azimuth(p)
Unknown WKB type (248)! Full WKB type number was (16777248).
Error in CPL_geodetic_azimuth(st_geometry(x), p$SemiMajor, p$InvFlattening) : 
  lwgeom error
Calls: st_geod_azimuth -> CPL_geodetic_azimuth
Execution halted
BEGIN TEST dist.R

R version 4.0.0 (2020-04-24) -- "Arbor Day"
Copyright (C) 2020 The R Foundation for Statistical Computing
Platform: s390x-ibm-linux-gnu (64-bit)

R is free software and comes with ABSOLUTELY NO WARRANTY.
You are welcome to redistribute it under certain conditions.
Type 'license()' or 'licence()' for distribution details.

R is a collaborative project with many contributors.
Type 'contributors()' for more information and
'citation()' on how to cite R or R packages in publications.

Type 'demo()' for some demos, 'help()' for on-line help, or
'help.start()' for an HTML browser interface to help.
Type 'q()' to quit R.

> suppressPackageStartupMessages(library(sf))
> library(sp)
> suppressPackageStartupMessages(library(units))
> library(geosphere)
> 
> x = st_sfc(
+ st_point(c(0,0)),
+ st_point(c(1,0)),
+ st_point(c(2,0)),
+ st_point(c(3,0)),
+ crs = 4326
+ )
> 
> y = st_sfc(
+ st_point(c(0,10)),
+ st_point(c(1,0)),
+ st_point(c(2,0)),
+ st_point(c(3,0)),
+ st_point(c(4,0)),
+ crs = 4326
+ )
> 
> st_crs(y) = 4326
> st_crs(x) = 4326
> (d.sf = st_distance(x, y))
Error in CPL_geodetic_distance(st_geometry(x), st_geometry(y), p$SemiMajor,  : 
  Unknown WKB type (248)! Full WKB type number was (16777248).
Calls: st_distance ->  -> CPL_geodetic_distance
Execution halted
BEGIN TEST geod.R

R version 4.0.0 (2020-04-24) -- "Arbor Day"
Copyright (C) 2020 The R Foundation for Statistical Computing
Platform: s390x-ibm-linux-gnu (64-bit)

R is free software and comes with ABSOLUTELY NO WARRANTY.
You are welcome to redistribute it under certain conditions.
Type 'license()' or 'licence()' for distribution details.

R is a collaborative project with many contributors.
Type 'contributors()' for more information and
'citation()' on how to cite R or R packages in publications.

Type 'demo()' for some demos, 'help()' for on-line help, or
'help.start()' for an HTML browser interface to help.
Type 'q()' to quit R.

> ### Name: lw_geodetic
> ### Title: geodetic length, area, and predicates
> ### Aliases: lw_geodetic st_geod_area lw_geodetic st_geod_length
> ###   lw_geodetic st_geod_segmentize lw_geodetic st_geod_covers
> 
> ### ** Examples
> 
> suppressPackageStartupMessages(library(sf))
> suppressPackageStartupMessages(library(lwgeom))
> suppressPackageStartupMessages(library(units))
> nc = st_read(system.file("gpkg/nc.gpkg", package="sf"), quiet = TRUE)
> st_geod_area(nc[1:3,])
Unknown WKB type (296)! Full WKB type number was (100663296).
Error in CPL_geodetic_area(st_geometry(x), p$SemiMajor, p$InvFlattening) : 
  lwgeom error
Calls: st_geod_area -> CPL_geodetic_area
Execution halted
BEGIN TEST perimeter.R

R version 4.0.0 (2020-04-24) -- "Arbor Day"
Copyright (C) 2020 The R Foundation for Statistical Computing

Bug#969909: xmoto-data: Broken links to DejaVu fonts

[Pavel Reznicek]

Package: xmoto-data
Version: 0.6.1+repack-2
Severity: serious
Justification: 4

Dear Maintainer,

  the links to DejaVu fonts are pointing to non-existent locations:

/usr/share/games/xmoto/Textures/Fonts/DejaVuSans.ttf -> 
../../../../fonts/truetype/ttf-dejavu/DejaVuSans.ttf
/usr/share/games/xmoto/Textures/Fonts/DejaVuSansMono.ttf -> 
../../../../fonts/truetype/ttf-dejavu/DejaVuSansMono.ttf

The correction locations are:

../../../../fonts/truetype/dejavu/DejaVuSans.ttf
../../../../fonts/truetype/dejavu/DejaVuSansMono.ttf

(most likely connected with transition from ttf-dejavu-core to 
fonts-dejavu-core).

Best reagards,
Pavel



-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (840, 'testing'), (740, 'unstable'), (738, 'experimental'), (540, 
'proposed-updates'), (540, 'stable'), (500, 'oldoldstable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.8.0-1-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages xmoto-data depends on:
ii  fonts-arphic-bkai00mp  2.10-21
ii  fonts-dejavu-core  2.37-2

xmoto-data recommends no packages.

Versions of packages xmoto-data suggests:
ii  xmoto  0.6.1+repack-2

-- no debconf information

Bug#962318: marked as done (libmojolicious-perl: build fails on IPv6-only buildds)

[Debian Bug Tracking System]

Your message dated Tue, 08 Sep 2020 15:21:56 +
with message-id 
and subject line Bug#962318: fixed in libmojolicious-perl 8.58+dfsg-2
has caused the Debian Bug report #962318,
regarding libmojolicious-perl: build fails on IPv6-only buildds
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.)


-- 
962318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962318
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libmojolicious-perl
Version: 8.52+dfsg-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=libmojolicious-perl=8.52%2Bdfsg-1

...
Can't create listen socket: Address family for hostname not supported at 
/<>/blib/lib/Mojo/IOLoop.pm line 123.
# Tests were run but no plan was declared and done_testing() was not seen.
...
Failed 39/103 test programs. 0/6415 subtests failed.
make[2]: *** [Makefile:1393: test_dynamic] Error 22


See #962019 as example of a similar problem in another package.
--- End Message ---
--- Begin Message ---
Source: libmojolicious-perl
Source-Version: 8.58+dfsg-2
Done: gregor herrmann 

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated libmojolicious-perl 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 08 Sep 2020 16:45:41 +0200
Source: libmojolicious-perl
Architecture: source
Version: 8.58+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 962318
Changes:
 libmojolicious-perl (8.58+dfsg-2) unstable; urgency=medium
 .
   * Build-depend on libio-socket-ip-perl 0.39-3 to fix test failures on
 IPv6-only hosts (cf. #964902).
 Closes: #962318
Checksums-Sha1:
 db1d83e4308f29a51f491294ebf6212ec808a13e 2792 
libmojolicious-perl_8.58+dfsg-2.dsc
 72dc9b1eb619917424ffd23c8cdb78a9a46fbaf3 16064 
libmojolicious-perl_8.58+dfsg-2.debian.tar.xz
Checksums-Sha256:
 80d815c77c6158c18d334364d9a87f95fecfb606325640af1bbb832f4c1697f7 2792 
libmojolicious-perl_8.58+dfsg-2.dsc
 e25d34ca23f4e66884554e528a5f00556c1949242e058005d2e6d225ea08a22f 16064 
libmojolicious-perl_8.58+dfsg-2.debian.tar.xz
Files:
 6e0d945a9c5852b82f4595a6662c87e1 2792 perl optional 
libmojolicious-perl_8.58+dfsg-2.dsc
 094a5512a074bcd18253a84ae2c8d3c3 16064 perl optional 
libmojolicious-perl_8.58+dfsg-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAl9XmkpfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgZSdw//ajMqCzz6c1waEFzfiTZZWFBcW+hSNrgunNq8jyv9sHMMnz2BoWWMBgyx
ejSWyeqxtzhy5DgMIj6kZceB+uRJO+E1PCps1xfNK2HH072kkw8vmgA/FnqzwAzP
fgmptap71p8aix2jnaQaXjpGd7EsQi4XAxa7FluY5gP+Agf+gSOgz70n6iIoSFlO
Bia5705M+YKASn27zZEHHJRYUvqVkj3BldXC8DLpeMP770FxbRu2EWybbKphyB1m
yoJu6m28tQGOj6t56UbVboa8Zwm0kTX0cDxstoMOdfp9nWQlxySARuov0mrkd8K0
tD6/ELFI4bDbBd2n7XDrdMAJ3aDWjtVlB+E5u9NRSZI4j4WL1uI9VkqmxzxnVrz8
fJZmKnoOlPc+SDcKOpF2mHA2ojvSFm+clp+OB6vFZRhW/wPvRvdMTXp0LHSy4g4S
v9q9oTpVwT+Va5djOyZ2SU7WE13ly1gi1LsXr14dPEtUzB1A8LTIkmWx6NWMFdsP
nrJDong6aEBGnZ8yjhqkHQdva25TNaQGW0CWRxdH9EoGBhFF7J9Q8BnQqIYeEsyU
OTRPZ55x3JPKw9aibBH2UCU3rmgkBhihc89NKFTHB1RHm1SDkqfNQIz3KJ5zVLK8
xxc2hcytq3DjawO4U6+LXD4/V602fQVX+ElhKF+kjlb5lStZ3so=
=G2hV
-END PGP SIGNATURE End Message ---

Bug#966653: Any progress?

[GCS]

Hi Thomas,

On Tue, Sep 8, 2020 at 1:27 PM Thomas Goirand  wrote:
> I'm not seeing any progress on this bug. Is anyone working on this?
 The bug report is too wide, "GitLab can't start" doesn't help to
narrow it down. I even suspect the real bug is in GitLab itself, it
may not (correctly) handle the new gRPC version.

> Without any action, this going to trigger the removal of most of
> OpenStack from testing... :/
 For some weeks I don't have time to learn GitLab and its internals to
find out where and why it fails with gRPC 1.30.2 version.
In the long run it might be the best to drop Ruby support from
src:grpc and let Pirate maintain that from a separate source tree.

Cheers,
Laszlo/GCS

Bug#969823: marked as done (etktab: autopkgtest should be marked superficial)

[Debian Bug Tracking System]

Your message dated Tue, 08 Sep 2020 15:03:28 +
with message-id 
and subject line Bug#969823: fixed in etktab 3.2-12
has caused the Debian Bug report #969823,
regarding etktab: autopkgtest should be marked superficial
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.)


-- 
969823: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969823
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: etktab
Severity: serious
Usertags: superficialtest
X-Debbugs-CC: elb...@debian.org

Hi,

The test done in the autopkgtest of 'etktab' does not provide
significant test coverage and it should be marked with "Restrictions:
superficial".

Ref: https://people.debian.org/~eriberto/README.package-tests.html

Examples of tests which are not significant includes (its not a
complete list):

1) Executing the binary to check version

Test-Command: foo -v

Test-Command: foo -V

Test-Command: foo --version

2) Executing the binary to check help (foo -h)

Test-Command: foo -h

Test-Command: foo --help

3) checking for files installed with 'ls'.

Test-Command: ls -l /usr/lib/*/foo.so

4) A Python or Perl library runs import foo or require Foo; but does
not attempt to use the library beyond that.

Test-Command: python3 -c "import foo"

Please add "Restrictions: superficial" to 'debian/tests/control' of
'etktab'.

--

Sudip 
--- End Message ---
--- Begin Message ---
Source: etktab
Source-Version: 3.2-12
Done: Fabio Augusto De Muzio Tobich 

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

Debian distribution maintenance software
pp.
Fabio Augusto De Muzio Tobich  (supplier of updated etktab 
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: Tue, 08 Sep 2020 10:59:21 -0300
Source: etktab
Architecture: source
Version: 3.2-12
Distribution: unstable
Urgency: medium
Maintainer: Fabio Augusto De Muzio Tobich 
Changed-By: Fabio Augusto De Muzio Tobich 
Closes: 969823
Changes:
 etktab (3.2-12) unstable; urgency=medium
 .
   * debian/copyright: added Upstream-Contact field.
   * debian/patches/:
   - 005_convert-files-to-utf8.patch: added to convert some files to UTF-8,
 rather than use national encoding.
   - Refreshed all patches.
   - Removed some trailing whitespace from patches 001 to 003.
   - Updated all patches headers to include Forwarded field.
   * debian/tests/control:
   - Added '-a' option to xvfb-run to get a free server number.
   - Test marked as superficial since does not provide significant test
 coverage. Thanks to Sudip Mukherjee. (Closes: #969823)
Checksums-Sha1:
 118b63cceef8b6b985dcd54959494685cf68f7ea 1867 etktab_3.2-12.dsc
 57845ad93af4a0162017e929b098637f7e7caf57 17368 etktab_3.2-12.debian.tar.xz
 6fce9851a633bc6b6065422735147ebda91c1cfd 5195 etktab_3.2-12_source.buildinfo
Checksums-Sha256:
 a61903119b966f6b1558c8b74b90dcd56a897e1fc0b1c36b97d33e98ed57c4f8 1867 
etktab_3.2-12.dsc
 cbe6925434a47b5d28a5dcd8d9793967efceb84ac3ede34c4783bbfb591d0021 17368 
etktab_3.2-12.debian.tar.xz
 a29bcfda29e1a6aa00a8a124b6a9f83961921abb3a04fb7269fbe512396d3430 5195 
etktab_3.2-12_source.buildinfo
Files:
 1b9e46c6dc1f2d588d7499b5cd2effb6 1867 sound optional etktab_3.2-12.dsc
 4baf3564242c8ebb0513c78b0e2caa3b 17368 sound optional 
etktab_3.2-12.debian.tar.xz
 99c88c41b68ef9909a0a05ab42c2bec0 5195 sound optional 
etktab_3.2-12_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAl9XmL4ACgkQkWT6HRe9
XTb8RA//dY3sOcZugfBq1Rj8L3xuMAJAgjLMxFnxJxr10XNwj0MWfIWHBAicTDFT
SSxi24NU4M9Y76V1qbBsNPcEDVtbN9vKMwf04WCponn7KGVcy/AZkvg/KKXELyk8
DrIga1eWOfYpkxhYoZh1Ox5b6YtzWzDZVG2qP3jyYO0I8N4VWtc5bBM++QjfHyQ9
51F/LUplQYTyvQ9QoJnrrNalfR2Hl9ge0cFa1N0rXdxaVM9DpP/DflI6Fbnqmmdo
srAkqtxlPIWTTBEhkAcJugfNpoOAAAkTTfg2awARARWvqOR2tak1oTXF4hglJsEx
ZYdJtDwXbgbFMaSd0j0Ryf8Zb0H13oL2+trKHkc6mbjkdspvXasJM0+kn67fBdhO
zaei1fgkT4uHDATzhxFQMajSvibLN4Nt59Pk+C8vntLxM3HNwXwjWOTf2w/YUz6C
SCQahVshcgQ0Rym1B3iWK6rNjGXK7x2du5o1em3aNJn5kpr9ihZQIW5AnLomJv+P

Bug#966523: r-bioc-rsubread FTBFS on 32bit: error: conflicting types for ‘uintptr_t’

[Andreas Tille]

Hi,

I'm hereby forwarding a problem that was detected on the Debian packaged
version of Rsubread.  Any idea how to fix this?

Kind regards

   Andreas.

On Thu, Jul 30, 2020 at 08:50:31AM +0300, Adrian Bunk wrote:
> Source: r-bioc-rsubread
> Version: 2.2.5-1
> Severity: serious
> Tags: ftbfs
> 
> https://buildd.debian.org/status/package.php?p=r-bioc-rsubread=sid
> 
> ...
> In file included from /usr/lib/gcc/i686-linux-gnu/10/include/stdint.h:9,
>  from HelperFunctions.h:139,
>  from R_wrapper.c:35:
> /usr/include/stdint.h:96:23: error: conflicting types for ‘uintptr_t’
>96 | typedef unsigned int  uintptr_t;
>   |   ^
> In file included from R_wrapper.c:30:
> /usr/share/R/include/Rinterface.h:110:24: note: previous declaration of 
> ‘uintptr_t’ was here
>   110 |  typedef unsigned long uintptr_t;
>   |^
> make[1]: *** [/usr/lib/R/etc/Makeconf:167: R_wrapper.o] Error 1

-- 
http://fam-tille.de

Processed: cloning 969537, reassign -1 to libpoppler-glib8 ...

[Debian Bug Tracking System]

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

> clone 969537 -1
Bug #969537 {Done: David Bremner } [elpa-pdf-tools-server] 
elpa-pdf-tools-server: broken when compiled against libpoppler102
Bug 969537 cloned as bug 969907
> reassign -1 libpoppler-glib8 20.09.0-2
Bug #969907 {Done: David Bremner } [elpa-pdf-tools-server] 
elpa-pdf-tools-server: broken when compiled against libpoppler102
Bug reassigned from package 'elpa-pdf-tools-server' to 'libpoppler-glib8'.
No longer marked as found in versions emacs-pdf-tools/0.90-3.
No longer marked as fixed in versions emacs-pdf-tools/1.0~20200512-1.
Bug #969907 {Done: David Bremner } [libpoppler-glib8] 
elpa-pdf-tools-server: broken when compiled against libpoppler102
Marked as found in versions poppler/20.09.0-2.
> retitle -1 libpoppler-glib8: introduces new ABI without bumping shlibs version
Bug #969907 {Done: David Bremner } [libpoppler-glib8] 
elpa-pdf-tools-server: broken when compiled against libpoppler102
Changed Bug title to 'libpoppler-glib8: introduces new ABI without bumping 
shlibs version' from 'elpa-pdf-tools-server: broken when compiled against 
libpoppler102'.
> thanks
Stopping processing here.

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

Processed: Bug#962318 marked as pending in libmojolicious-perl

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #962318 [src:libmojolicious-perl] libmojolicious-perl: build fails on 
IPv6-only buildds
Added tag(s) pending.

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

Bug#962318: marked as pending in libmojolicious-perl

[gregor herrmann]

Control: tag -1 pending

Hello,

Bug #962318 in libmojolicious-perl 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/perl-team/modules/packages/libmojolicious-perl/-/commit/b11871cc4f0ed7c694236d2c26a2b1caf245833c


Build-depend on libio-socket-ip-perl 0.39-3

to fix test failures on IPv6-only hosts (cf. #964902).

Closes: #962318


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/962318

Bug#966982: Uploading disabling that test to DELAYED/2

[Thomas Goirand]

On 9/8/20 2:01 PM, Håvard Flaget Aasen wrote:
> On Tue, 8 Sep 2020 13:40:25 +0200 Thomas Goirand  wrote:
>> Hi,
>>
>> Since nobody seem to care about this, I've uploaded disabling that
>> failing test to DELAYED/2. Indeed, to me, it looked like a broken test,
>> rather than a broken package. Otherwise, a long list of reverse
>> dependency will be removed from testing in 8 days.
>>
>> Debdiff of the change attached. Let me know if you would like me to
>> cancel the upload.
>>
>> Cheers,
>>
>> Thomas Goirand (zigo)
> 
> Thanks for this Thomas but I actually have a package up for RFS to
> address this issue.
> I must admit I removed all tests during build. Because of the same
> reason.  same testsuite is being run as an autopkgtest which succeeds.
> Previous there has also been some issues with these tests bug: [761325]
> I intend to reopen this bug.
> 
> Can I persuade you to review and upload my own package instead of doing
> an NMU? bug: [965370] package in mentors [3]
> 
> Thanks,
> H??vard
> 
> [761325] https://bugs.debian.org/761325
> [965370] https://bugs.debian.org/965370
> [3] https://mentors.debian.net/package/wand/
> 

Hi Håvard,

I'm very much surprised by this. Why didn't you write in the bug report
then, saying you've addressed the issue and was searching for a sponsor?
I had the impression that nobody cared, you know... And you can't expect
everyone to closely monitor mentors.

I do not agree that removing all tests is the solution, when only a
single one fails. I would happily sponsor your upload, but *not* if it's
removing all tests.

Cheers,

Thomas Goirand (zigo)

Bug#969788: nextcloud-desktop: Upgrade removed part of configuration

[Marek Straka]

It looks like after reboot old config is back.

Bug#954855: php7.4-enchant: API/ABI change for enchant-2

[Tommy Wu]

linux-vdso.so.1 (0x7fffe0938000)
libenchant-2.so.2 => /usr/lib/x86_64-linux-gnu/libenchant-2.so.2 
(0x7f1264539000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f1264374000)
libgmodule-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0 
(0x7f126436e000)
libglib-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 
(0x7f1264248000)
/lib64/ld-linux-x86-64.so.2 (0x7f1264567000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f1264242000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f126422)
libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x7f12641ab000)


Ondřej Surý  wrote:

> Hi,
> 
> could you do:
> 
> ldd /usr/lib/php/20190902/enchant.so
> 
> on the affected system?
> 
> Ondrej
> 
> > On 8 Sep 2020, at 10:09, Tommy Wu  wrote:
> > 
> > Package: php7.4-enchant
> > Version: 7.4.9-2
> > Followup-For: Bug #954855
> > 
> > Dear Maintainer,
> > 
> > Error message like this:
> > PHP Warning:  PHP Startup: Unable to load dynamic library 'enchant.so' 
> > (tried: /usr/lib/php/20190902/enchant.so (/usr/lib/php/20190902/enchant.so: 
> > undefined symbol: enchant_dict_is_in_session), 
> > /usr/lib/php/20190902/enchant.so.so (/usr/lib/php/20190902/enchant.so.so: 
> > cannot open shared object file: No such file or directory)) in Unknown on 
> > line 0
> > 
> > I found this bug in PHP's open bug:
> > https://bugs.php.net/bug.php?id=76962
> > 
> > -- Package-specific info:
> >  Additional PHP 7.4 information 
> > 
> >  PHP @PHP_VERSION SAPI (php7.4query -S): 
> > 
> >  PHP 7.4 Extensions (php7.4query -M -v): 
> > 
> >  Configuration files: 
> >  /etc/php/7.4/mods-available/enchant.ini 
> > extension=enchant.so
> > 
> > 
> > -- System Information:
> > Debian Release: bullseye/sid
> >  APT prefers testing
> >  APT policy: (500, 'testing')
> > Architecture: amd64 (x86_64)
> > Foreign Architectures: i386, armhf
> > 
> > Kernel: Linux 5.7.0-1-amd64 (SMP w/8 CPU threads)
> > Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
> > Locale: LANG=en_US.UTF-8, LC_CTYPE=zh_TW.UTF-8 (charmap=UTF-8), 
> > LANGUAGE=en_US:en
> > Shell: /bin/sh linked to /bin/bash
> > Init: systemd (via /run/systemd/system)
> > 
> > Versions of packages php7.4-enchant depends on:
> > ii  libc6   2.31-3
> > ii  libenchant-2-2  2.2.8-1
> > ii  php-common  2:76
> > ii  php7.4-common   7.4.9-2
> > ii  ucf 3.0043
> > 
> > php7.4-enchant recommends no packages.
> > 
> > php7.4-enchant suggests no packages.
> > 
> > Versions of packages php7.4-common depends on:
> > ii  libc6   2.31-3
> > ii  libffi7 3.3-4
> > ii  libssl1.1   1.1.1g-1
> > ii  php-common  2:76
> > ii  ucf 3.0043
> > 
> > Versions of packages php7.4-cli depends on:
> > ii  libargon2-1  0~20171227-0.2
> > ii  libc62.31-3
> > ii  libedit2 3.1-20191231-1
> > ii  libmagic11:5.38-5
> > ii  libpcre2-8-0 10.34-7
> > ii  libsodium23  1.0.18-1
> > ii  libssl1.11.1.1g-1
> > ii  libxml2  2.9.10+dfsg-6
> > ii  mime-support 3.64
> > ii  php7.4-common7.4.9-2
> > ii  php7.4-json  7.4.9-2
> > ii  php7.4-opcache   7.4.9-2
> > ii  php7.4-readline  7.4.9-2
> > ii  tzdata   2020a-1
> > ii  ucf  3.0043
> > ii  zlib1g   1:1.2.11.dfsg-2
> > 
> > Versions of packages php7.4-cli suggests:
> > ii  php-pear  1:1.10.9+submodules+notgz-1
> > 
> > Versions of packages php7.4-fpm depends on:
> > ii  libapparmor12.13.4-3
> > ii  libargon2-1 0~20171227-0.2
> > ii  libc6   2.31-3
> > ii  libmagic1   1:5.38-5
> > ii  libpcre2-8-010.34-7
> > ii  libsodium23 1.0.18-1
> > ii  libssl1.1   1.1.1g-1
> > ii  libsystemd0 246.4-1
> > ii  libxml2 2.9.10+dfsg-6
> > ii  mime-support3.64
> > ii  php7.4-cli  7.4.9-2
> > ii  php7.4-common   7.4.9-2
> > ii  php7.4-json 7.4.9-2
> > ii  php7.4-opcache  7.4.9-2
> > ii  procps  2:3.3.16-5
> > ii  systemd 246.4-1
> > ii  tzdata  2020a-1
> > ii  ucf 3.0043
> > ii  zlib1g  1:1.2.11.dfsg-2
> > 
> > Versions of packages php7.4-fpm suggests:
> > ii  php-pear  1:1.10.9+submodules+notgz-1
> > 
> > -- no debconf information
> > 

-- 

Bug#968661: marked as done (peony-extensions: hardcodes dependency on libpeony2)

[Debian Bug Tracking System]

Your message dated Tue, 08 Sep 2020 14:10:19 +
with message-id 
and subject line Bug#968661: fixed in peony-extensions 3.0.0-1
has caused the Debian Bug report #968661,
regarding peony-extensions: hardcodes dependency on libpeony2
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.)


-- 
968661: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968661
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: peony-extensions
Version: 2.0.2-1
Severity: serious

peony-share, parchives and peony-open-terminal currently hardcode
dependencies on libpeony2. These dependencies will be added as part of
${shlibs:Depends} anyway. Please drop them so that package can be
rebuilt to drop the libpeony2 dependencies in favor of libpeony2.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: peony-extensions
Source-Version: 3.0.0-1
Done: handsome_feng 

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

Debian distribution maintenance software
pp.
handsome_feng  (supplier of updated 
peony-extensions 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: Thu, 20 Aug 2020 10:06:58 +0800
Source: peony-extensions
Binary: parchives parchives-dbgsym peony-admin peony-admin-dbgsym 
peony-extension-computer-view peony-extension-computer-view-dbgsym 
peony-extensions peony-open-terminal peony-open-terminal-dbgsym 
peony-set-wallpaper peony-set-wallpaper-dbgsym peony-share peony-share-dbgsym
Architecture: source amd64
Version: 3.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Kylin Team 
Changed-By: handsome_feng 
Description:
 parchives  - Peony qt plugin for file compress and uncompress
 peony-admin - Peony plugin for open files or directories as admin
 peony-extension-computer-view - Peony plugin for displaying computer:/// with 
more information
 peony-extensions - Peony qt extensions
 peony-open-terminal - Peony plugin for opening terminals in arbitrary local 
paths
 peony-set-wallpaper - Peony plugin for right click a picture to set as 
wallpaper
 peony-share - Allows one to quickly share a folder from the Peony file manager
Closes: 968661
Changes:
 peony-extensions (3.0.0-1) unstable; urgency=medium
 .
   * New upstream release.
   * d/control:
 - Add peony-extension-computer-view, peony-set-wallpaper,
   peony-admin, peony-extensions.
 - Remove hardcodes dependency on libpeony. (Closes: #968661)
Checksums-Sha1:
 eac07901ff097c338fe869fc5354cd5b4d9e4067 2161 peony-extensions_3.0.0-1.dsc
 4db6823bf147acd3a4dc1e1cfb650fd731a377c2 44452 
peony-extensions_3.0.0.orig.tar.gz
 fa89f34f81fd4020d78cde263c80446484de263b 2992 
peony-extensions_3.0.0-1.debian.tar.xz
 ca05a4ef9fb1d76c969cdfe35146a4e1488c5ebf 300304 
parchives-dbgsym_3.0.0-1_amd64.deb
 0eaebe4595de680333cdf359e3e67e533235689b 15616 parchives_3.0.0-1_amd64.deb
 bfc1ff8bce9f7ad0d188781dee85d08a4dc0a529 375008 
peony-admin-dbgsym_3.0.0-1_amd64.deb
 96148e0efe0e6b5400ec6b6bc4a63cec1bf14660 18092 peony-admin_3.0.0-1_amd64.deb
 571f76b470ff261d4308f39d552a48e1487c3d12 1903676 
peony-extension-computer-view-dbgsym_3.0.0-1_amd64.deb
 3d3f6518c7ba055be72c08f661e35515322c8201 63744 
peony-extension-computer-view_3.0.0-1_amd64.deb
 b87887332ee67481ef583ae341d2c5df17e54e03 14433 
peony-extensions_3.0.0-1_amd64.buildinfo
 ed9ca999c9bae2f65d629a5f8f80d4ac29cad713 2528 
peony-extensions_3.0.0-1_amd64.deb
 1ca37223121bf75650f400534b18cd976fe5f655 363344 
peony-open-terminal-dbgsym_3.0.0-1_amd64.deb
 ed9e04e9310b012e5e964ddd460de0b04ae97e34 15296 
peony-open-terminal_3.0.0-1_amd64.deb
 6a4f9be64a8aa2c00ef6d1512ccdb5bdbbdd3ec6 285896 
peony-set-wallpaper-dbgsym_3.0.0-1_amd64.deb
 c12a8f7226e8d59a18d62a2f2bd9e264a7490bd6 13000 
peony-set-wallpaper_3.0.0-1_amd64.deb
 e41a07320e086313854faa51b440b15bb96f10ff 527880 
peony-share-dbgsym_3.0.0-1_amd64.deb
 77f218d298b36316f883c57df77ed319c5ccc194 25052 peony-share_3.0.0-1_amd64.deb
Checksums-Sha256:
 371d462876c68e5b8b537a8e9583537900f809d4abe1613b2cc068e433d91b5a 2161 
peony-extensions_3.0.0-1.dsc
 

Processed: Re: Bug#969894: nvidia-legacy-390xx-driver: X will not start with nvidia-legacy-390.xx driver and 5.8 kernel

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:nvidia-graphics-drivers-legacy-390xx
Bug #969894 [nvidia-legacy-390xx-driver] nvidia-legacy-390xx-driver: X will not 
start with nvidia-legacy-390.xx driver and 5.8 kernel
Bug reassigned from package 'nvidia-legacy-390xx-driver' to 
'src:nvidia-graphics-drivers-legacy-390xx'.
No longer marked as found in versions 
nvidia-graphics-drivers-legacy-390xx/390.138-2.
Ignoring request to alter fixed versions of bug #969894 to the same values 
previously set
> affects -1 linux-image-5.8.0-1-amd64
Bug #969894 [src:nvidia-graphics-drivers-legacy-390xx] 
nvidia-legacy-390xx-driver: X will not start with nvidia-legacy-390.xx driver 
and 5.8 kernel
Added indication that 969894 affects linux-image-5.8.0-1-amd64
> merge 969889 -1
Bug #969889 [src:nvidia-graphics-drivers-legacy-390xx] 
linux-image-5.8.0-1-amd64: fails to load kernel modules, X does not work
Bug #969894 [src:nvidia-graphics-drivers-legacy-390xx] 
nvidia-legacy-390xx-driver: X will not start with nvidia-legacy-390.xx driver 
and 5.8 kernel
Merged 969889 969894

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

Bug#969894: nvidia-legacy-390xx-driver: X will not start with nvidia-legacy-390.xx driver and 5.8 kernel

[Vincent Lefevre]

Control: reassign -1 src:nvidia-graphics-drivers-legacy-390xx
Control: affects -1 linux-image-5.8.0-1-amd64
Control: merge 969889 -1

On 2020-09-08 07:17:18 -0500, allan grossman wrote:
> Upgraded Sid this morning and X will not start with 5.8 kernel with nvidia-
> legacy-390xx-driver.  Works fine with 5.7.x kernel.

That's probably because the module cannot be built with the 5.8 kernel,
which is what I could notice (unfortunately, no error is reported to
apt/aptitude).

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

Bug#969901: torbrowser-launcher: depends on /usr/bin/gpg2 but dependency not expressed

[Jonathan Dowland]

Package: torbrowser-launcher
Version: 0.3.2-11~bpo10+1
Severity: serious
Justification: Policy 3.5

There's a few things going on in this session, but this bug report is
about the last backtrace in particular:

$ torbrowser-launcher
Tor Browser Launcher
By Micah Lee, licensed under MIT
version 0.3.2
https://github.com/micahflee/torbrowser-launcher
Creating GnuPG homedir /home/jon/.local/share/torbrowser/gnupg_homedir
Downloading Tor Browser for the first time.
Downloading 
https://aus1.torproject.org/torbrowser/update_3/release/Linux_x86_64-gcc3/x/en-US
Latest version: 9.5.4
Downloading 
https://dist.torproject.org/torbrowser/9.5.4/tor-browser-linux64-9.5.4_en-US.tar.xz.asc
Downloading 
https://dist.torproject.org/torbrowser/9.5.4/tor-browser-linux64-9.5.4_en-US.tar.xz
Verifying Signature
Refreshing local keyring...
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/torbrowser_launcher/launcher.py", line 
589, in verify
c.verify(signature=sig, signed_data=signed)
  File "/usr/lib/python3/dist-packages/gpg/core.py", line 559, in verify
raise errors.BadSignatures(results[1], results=results)
gpg.errors.BadSignatures: 110775B5D101FB36BC6C911BEB774491D9FF06E2: Key expired

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/torbrowser_launcher/launcher.py", line 
600, in run
verify()
  File "/usr/lib/python3/dist-packages/torbrowser_launcher/launcher.py", line 
594, in verify
raise Exception
Exception

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/torbrowser_launcher/launcher.py", line 
603, in run
self.common.refresh_keyring()
  File "/usr/lib/python3/dist-packages/torbrowser_launcher/common.py", line 
209, in refresh_keyring
'--refresh-keys'], stderr=subprocess.PIPE)
  File "/usr/lib/python3.7/subprocess.py", line 775, in __init__
restore_signals, start_new_session)
  File "/usr/lib/python3.7/subprocess.py", line 1522, in _execute_child
raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: '/usr/bin/gpg2': 
'/usr/bin/gpg2'
Aborted




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

Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages torbrowser-launcher depends on:
ii  ca-certificates   20190110
ii  libdbus-glib-1-2  0.110-4
ii  python3   3.7.3-1
ii  python3-gpg   1.12.0-6
ii  python3-pyqt5 5.11.3+dfsg-1+b3
ii  python3-requests  2.21.0-1
ii  python3-socks 1.6.8+dfsg-1

Versions of packages torbrowser-launcher recommends:
ii  tor  0.3.5.10-1

Versions of packages torbrowser-launcher suggests:
ii  apparmor  2.13.2-10

-- no debconf information

Bug#962213: package ftbfs on arm64 and armhf

[Alec Leamas]

On Mon, 20 Jul 2020 12:38:36 +0200 Alec Leamas 
wrote:

> I have not been able to test the arm builds, taking your word that
> lindrm-dev should fix it.

ubuntu test builds at
https://launchpad.net/~leamas-alec/+archive/ubuntu/opencpn/+sourcepub/11570928/+listing-archive-extra

The package builds ok on armhf and arm64. Now, the question is just
about a reviewer...

--alec

Processed: Re: Bug#969889: linux-image-5.8.0-1-amd64: fails to load kernel modules, X does not work

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #969889 [src:nvidia-graphics-drivers-legacy-390xx] 
linux-image-5.8.0-1-amd64: fails to load kernel modules, X does not work
Severity set to 'grave' from 'important'
> tags -1 - moreinfo
Bug #969889 [src:nvidia-graphics-drivers-legacy-390xx] 
linux-image-5.8.0-1-amd64: fails to load kernel modules, X does not work
Removed tag(s) moreinfo.
> affects -1 linux-image-5.8.0-1-amd64
Bug #969889 [src:nvidia-graphics-drivers-legacy-390xx] 
linux-image-5.8.0-1-amd64: fails to load kernel modules, X does not work
Added indication that 969889 affects linux-image-5.8.0-1-amd64

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

Bug#969074: [PATCH] d/p/lp-1894129-*: fix FTBFS (LP: #1894129 Closes: #969074)

[Christian Ehrhardt]

Signed-off-by: Christian Ehrhardt 
---
 ...raseReserved-override-driver-queue_p.patch |  74 
 ...BlockEraseReserved-skip-unless-iSCSI.patch |  39 
 ...e-Write-override-driver-queue_pdu-ca.patch |  71 
 ...e-Write-skip-InvalidDataOutSize-unle.patch |  39 
 ...EraseReserved-override-driver-queue_.patch |  74 
 ...ryptoEraseReserved-skip-unless-iSCSI.patch |  39 
 ...iteReserved-override-driver-queue_pd.patch |  68 +++
 ...-test-tool-Use-extern-int-in-headers.patch |  58 ++
 ...mdSnTooHigh-override-driver-queue_pd.patch |  68 +++
 ...mdSnTooLow-override-driver-queue_pdu.patch |  69 
 ...ataSnInvalid-override-driver-queue_p.patch | 166 ++
 ...-unused-iscsi_queue_pdu-symbol-overl.patch | 104 +++
 debian/patches/series |  12 ++
 13 files changed, 881 insertions(+)
 create mode 100644 
debian/patches/lp-1894129-test-tool-BlockEraseReserved-override-driver-queue_p.patch
 create mode 100644 
debian/patches/lp-1894129-test-tool-BlockEraseReserved-skip-unless-iSCSI.patch
 create mode 100644 
debian/patches/lp-1894129-test-tool-Compare-Write-override-driver-queue_pdu-ca.patch
 create mode 100644 
debian/patches/lp-1894129-test-tool-Compare-Write-skip-InvalidDataOutSize-unle.patch
 create mode 100644 
debian/patches/lp-1894129-test-tool-CryptoEraseReserved-override-driver-queue_.patch
 create mode 100644 
debian/patches/lp-1894129-test-tool-CryptoEraseReserved-skip-unless-iSCSI.patch
 create mode 100644 
debian/patches/lp-1894129-test-tool-OverwriteReserved-override-driver-queue_pd.patch
 create mode 100644 
debian/patches/lp-1894129-test-tool-Use-extern-int-in-headers.patch
 create mode 100644 
debian/patches/lp-1894129-test-tool-iSCSICmdSnTooHigh-override-driver-queue_pd.patch
 create mode 100644 
debian/patches/lp-1894129-test-tool-iSCSICmdSnTooLow-override-driver-queue_pdu.patch
 create mode 100644 
debian/patches/lp-1894129-test-tool-iSCSIDataSnInvalid-override-driver-queue_p.patch
 create mode 100644 
debian/patches/lp-1894129-test-tool-remove-unused-iscsi_queue_pdu-symbol-overl.patch

diff --git 
a/debian/patches/lp-1894129-test-tool-BlockEraseReserved-override-driver-queue_p.patch
 
b/debian/patches/lp-1894129-test-tool-BlockEraseReserved-override-driver-queue_p.patch
new file mode 100644
index 000..68def73
--- /dev/null
+++ 
b/debian/patches/lp-1894129-test-tool-BlockEraseReserved-override-driver-queue_p.patch
@@ -0,0 +1,74 @@
+From b705f9e5240583fb862f16d603e5cf2120e5d54c Mon Sep 17 00:00:00 2001
+From: David Disseldorp 
+Date: Mon, 16 Sep 2019 14:46:28 +0200
+Subject: [PATCH] test-tool/BlockEraseReserved: override driver queue_pdu()
+ callback
+
+In preparation for removing the test-tool iscsi_queue_pdu() dlsym
+overload hack, convert this test to use the regular transport driver
+callback for this purpose.
+
+Signed-off-by: David Disseldorp 
+
+Origin: upstream, https://github.com/sahlberg/libiscsi/commit/b705f9e5
+Bug-Ubuntu: https://bugs.launchpad.net/bugs/1894129
+Last-Update: 2020-09-08
+
+---
+ test-tool/test_sanitize_block_erase_reserved.c | 17 +++--
+ 1 file changed, 11 insertions(+), 6 deletions(-)
+
+diff --git a/test-tool/test_sanitize_block_erase_reserved.c 
b/test-tool/test_sanitize_block_erase_reserved.c
+index fcb862e..4a0d2cb 100644
+--- a/test-tool/test_sanitize_block_erase_reserved.c
 b/test-tool/test_sanitize_block_erase_reserved.c
+@@ -25,8 +25,9 @@
+ #include "iscsi-test-cu.h"
+ 
+ static int change_num;
++static struct iscsi_transport iscsi_drv_orig;
+ 
+-static int my_iscsi_queue_pdu(struct iscsi_context *iscsi _U_, struct 
iscsi_pdu *pdu)
++static int my_iscsi_queue_pdu(struct iscsi_context *iscsi, struct iscsi_pdu 
*pdu)
+ {
+ switch (change_num) {
+ case 1:
+@@ -43,12 +44,12 @@ static int my_iscsi_queue_pdu(struct iscsi_context *iscsi 
_U_, struct iscsi_pdu
+ break;
+ }
+ 
+-change_num = 0;
+-return 0;
++change_num = 0;
++return iscsi_drv_orig.queue_pdu(iscsi, pdu);
+ }
+ 
+ void test_sanitize_block_erase_reserved(void)
+-{ 
++{
+ int i;
+ 
+ logging(LOG_VERBOSE, LOG_BLANK_LINE);
+@@ -64,8 +65,9 @@ void test_sanitize_block_erase_reserved(void)
+ return;
+ }
+ 
+-local_iscsi_queue_pdu = my_iscsi_queue_pdu;
+-
++/* override transport queue_pdu callback for PDU manipulation */
++iscsi_drv_orig = *sd->iscsi_ctx->drv;
++sd->iscsi_ctx->drv->queue_pdu = my_iscsi_queue_pdu;
+ 
+ logging(LOG_VERBOSE, "Send SANITIZE command with the reserved "
+ "bit in byte 1 set to 1");
+@@ -81,4 +83,7 @@ void test_sanitize_block_erase_reserved(void)
+ SANITIZE(sd, 0, 0, SCSI_SANITIZE_BLOCK_ERASE, 0, NULL,
+  EXPECT_INVALID_FIELD_IN_CDB);
+ }
++
++/* restore transport callbacks */
++*(sd->iscsi_ctx->drv) = iscsi_drv_orig;
+ }
+-- 
+2.28.0
+
diff 

Bug#966921: marked as done (path in libdpdk.pc must be versioned with tooling version)

[Debian Bug Tracking System]

Your message dated Tue, 08 Sep 2020 12:49:50 +
with message-id 
and subject line Bug#966921: fixed in dpdk 19.11.4-1
has caused the Debian Bug report #966921,
regarding path in libdpdk.pc must be versioned with tooling version
to be marked as done.

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

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


-- 
966921: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966921
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openvswitch
Version: 2.13.0+dfsg1-12
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200802 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> checking whether RTE_IBVERBS_LINK_DLOPEN is declared... (cached) no
> checking for library containing mlx4dv_init_obj... -lmlx4
> checking for library containing verbs_init_cq... (cached) -libverbs
> checking for library containing dlopen... -ldl
> checking whether linking with dpdk works... no
> configure: error: Could not find DPDK library in default search path, Use 
> --with-dpdk to specify the DPDK library installed in non-standard location
> make[1]: *** [debian/rules:26: override_dh_auto_configure] Error 1
> make[1]: Leaving directory '/<>'

The full build log is available from:
   http://qa-logs.debian.net/2020/08/02/openvswitch_2.13.0+dfsg1-12_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!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: dpdk
Source-Version: 19.11.4-1
Done: Luca Boccassi 

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

Debian distribution maintenance software
pp.
Luca Boccassi  (supplier of updated dpdk package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 08 Sep 2020 09:57:19 +0100
Source: dpdk
Architecture: source
Version: 19.11.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian DPDK Maintainers 
Changed-By: Luca Boccassi 
Closes: 966921
Changes:
 dpdk (19.11.4-1) unstable; urgency=medium
 .
   [ Christian Ehrhardt ]
   * d/t/test-autotest: bump sse feature check
   * fix libfdt path in pkg-config (Closes: #966921)
   * d/librte-rawdev20.0.symbols: add new symbol rte_rawdev_dump
   * d/rules: lintian debian-rules-uses-unnecessary-dh-argument for systemd
   * d/copyright: fix duplicate-globbing-patterns
 .
   [ Luca Boccassi ]
   * New upstream version 19.11.4~rc1
   * Adjust dpdk-doc install path for guides
   * New upstream version 19.11.4
   * Drop fix-libfdt-path.patch, merged upstream
   * Rename Lintian override no-manual-page
Checksums-Sha1:
 017fe2130247d4fdc9de1e3e981859d2866eb723 17261 dpdk_19.11.4-1.dsc
 55af648597d94e76b8e6a08ff70c9ae1331657de 12433520 dpdk_19.11.4.orig.tar.xz
 b5c2a0993d2d2faebcb8c84f16e6d49c8313baf0 57116 dpdk_19.11.4-1.debian.tar.xz
 164c2a91e3e1443059792191ebc24180cef91ab0 20114 dpdk_19.11.4-1_source.buildinfo
Checksums-Sha256:
 4d1b7eb156626505caf813f5864fc06cc3818450cba06dd6997c528fddfd925a 17261 
dpdk_19.11.4-1.dsc
 657070a669364efef66b8b8bbe862f2611b367b6126969c43acdc06f2a172dbd 12433520 
dpdk_19.11.4.orig.tar.xz
 08080a2979252aa868358e2d916e487364bd2052c6bf01bbc00f1d2c759d5513 57116 
dpdk_19.11.4-1.debian.tar.xz
 1f64ae22cf91acbdccf85154760cad9e4d9cad5e9c10d1df14ac29601e605443 20114 
dpdk_19.11.4-1_source.buildinfo
Files:
 789328c8c79bce0c4489dbb1d61e56b8 17261 libs optional dpdk_19.11.4-1.dsc
 c23683b52bbc3e1844d9dd041c6242be 12433520 libs optional 
dpdk_19.11.4.orig.tar.xz
 7768a2eda40f6aa546c0c09ba2c56fa9 57116 libs optional 
dpdk_19.11.4-1.debian.tar.xz
 c2a71d78f3d971def7f52cd85765065d 20114 libs optional 
dpdk_19.11.4-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFFBAEBCgAvFiEE6g0RLAGYhL9yp9G8SylmgFB4UWIFAl9XeRARHGJsdWNhQGRl

Bug#969074: Reported upstream and partial fix exists already

[Christian Ehrhardt]

FYI:
- https://github.com/sahlberg/libiscsi/issues/340
- 
https://github.com/sahlberg/libiscsi/commit/dd17293bcc188dbefc420ee23b77bc9bb7c5e9a2

But that isn't everything.
I'm looking at this for
https://bugs.launchpad.net/ubuntu/+source/libiscsi/+bug/1894129 and
will send patches here once it works. Is there a salsa repo somewhere
this should go to (otherwise I'll submit changes here)?

(Ubuntu) Test builds at
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4256/+packages

-- 
Christian Ehrhardt
Staff Engineer, Ubuntu Server
Canonical Ltd

Bug#954855: php7.4-enchant: API/ABI change for enchant-2

[Tommy Wu]

Package: php7.4-enchant
Version: 7.4.9-2
Followup-For: Bug #954855

Dear Maintainer,

Error message like this:
PHP Warning:  PHP Startup: Unable to load dynamic library 'enchant.so' (tried: 
/usr/lib/php/20190902/enchant.so (/usr/lib/php/20190902/enchant.so: undefined 
symbol: enchant_dict_is_in_session), /usr/lib/php/20190902/enchant.so.so 
(/usr/lib/php/20190902/enchant.so.so: cannot open shared object file: No such 
file or directory)) in Unknown on line 0

I found this bug in PHP's open bug:
https://bugs.php.net/bug.php?id=76962

-- Package-specific info:
 Additional PHP 7.4 information 

 PHP @PHP_VERSION SAPI (php7.4query -S): 

 PHP 7.4 Extensions (php7.4query -M -v): 

 Configuration files: 
 /etc/php/7.4/mods-available/enchant.ini 
extension=enchant.so


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

Kernel: Linux 5.7.0-1-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=zh_TW.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages php7.4-enchant depends on:
ii  libc6   2.31-3
ii  libenchant-2-2  2.2.8-1
ii  php-common  2:76
ii  php7.4-common   7.4.9-2
ii  ucf 3.0043

php7.4-enchant recommends no packages.

php7.4-enchant suggests no packages.

Versions of packages php7.4-common depends on:
ii  libc6   2.31-3
ii  libffi7 3.3-4
ii  libssl1.1   1.1.1g-1
ii  php-common  2:76
ii  ucf 3.0043

Versions of packages php7.4-cli depends on:
ii  libargon2-1  0~20171227-0.2
ii  libc62.31-3
ii  libedit2 3.1-20191231-1
ii  libmagic11:5.38-5
ii  libpcre2-8-0 10.34-7
ii  libsodium23  1.0.18-1
ii  libssl1.11.1.1g-1
ii  libxml2  2.9.10+dfsg-6
ii  mime-support 3.64
ii  php7.4-common7.4.9-2
ii  php7.4-json  7.4.9-2
ii  php7.4-opcache   7.4.9-2
ii  php7.4-readline  7.4.9-2
ii  tzdata   2020a-1
ii  ucf  3.0043
ii  zlib1g   1:1.2.11.dfsg-2

Versions of packages php7.4-cli suggests:
ii  php-pear  1:1.10.9+submodules+notgz-1

Versions of packages php7.4-fpm depends on:
ii  libapparmor12.13.4-3
ii  libargon2-1 0~20171227-0.2
ii  libc6   2.31-3
ii  libmagic1   1:5.38-5
ii  libpcre2-8-010.34-7
ii  libsodium23 1.0.18-1
ii  libssl1.1   1.1.1g-1
ii  libsystemd0 246.4-1
ii  libxml2 2.9.10+dfsg-6
ii  mime-support3.64
ii  php7.4-cli  7.4.9-2
ii  php7.4-common   7.4.9-2
ii  php7.4-json 7.4.9-2
ii  php7.4-opcache  7.4.9-2
ii  procps  2:3.3.16-5
ii  systemd 246.4-1
ii  tzdata  2020a-1
ii  ucf 3.0043
ii  zlib1g  1:1.2.11.dfsg-2

Versions of packages php7.4-fpm suggests:
ii  php-pear  1:1.10.9+submodules+notgz-1

-- no debconf information

Bug#946733: marked as done (rust-curl: autopkgtest failure: no matching package named `openssl-probe` found)

[Debian Bug Tracking System]

Your message dated Tue, 8 Sep 2020 13:20:41 +0100
with message-id 
and subject line rust-curl: autopkgtest failure: no matching package named 
`openssl-probe` found
has caused the Debian Bug report #946733,
regarding rust-curl: autopkgtest failure: no matching package named 
`openssl-probe` found
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.)


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

Dear maintainers,

With a recent upload of rust-curl you added an autopkgtest to your
package, great. However, it fails. I copied some of the output at the
bottom of this report.

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

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-curl/3527290/log.gz

autopkgtest [09:36:59]: test command9: [---
debian cargo wrapper: options, profiles, parallel: ['parallel=2'] [] ['-j2']
debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu,
x86_64-linux-gnu
debian cargo wrapper: linking /usr/share/cargo/registry/* into
/tmp/tmp.VN0uRNJyf9/registry/
debian cargo wrapper: options, profiles, parallel: ['parallel=2'] [] ['-j2']
debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu,
x86_64-linux-gnu
debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1',
'/usr/bin/cargo', '-Zavoid-dev-deps', 'test', '--verbose', '--verbose',
'-j2', '--target', 'x86_64-unknown-linux-gnu', '--all-targets',
'--features', 'static-ssl'],) {}
error: no matching package named `openssl-probe` found
location searched: registry `https://github.com/rust-lang/crates.io-index`
required by package `curl v0.4.25 (/usr/share/cargo/registry/curl-0.4.25)`
autopkgtest [09:37:00]: test command9: ---]



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---

Version: 0.4.25-2

The autopkgtest now seems to be passing in both plain unstable tests and 
unstable->testing migration tests.--- End Message ---

Bug#969894: nvidia-legacy-390xx-driver: X will not start with nvidia-legacy-390.xx driver and 5.8 kernel

[allan grossman]

Package: nvidia-legacy-390xx-driver
Version: 390.138-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Upgraded Sid this morning and X will not start with 5.8 kernel with nvidia-
legacy-390xx-driver.  Works fine with 5.7.x kernel.



-- Package-specific info:
uname -a:
Linux wizard-laptop 5.7.0-3-amd64 #1 SMP Debian 5.7.17-1 (2020-08-23) x86_64 
GNU/Linux

/proc/version:
Linux version 5.7.0-3-amd64 (debian-ker...@lists.debian.org) (gcc version 9.3.0 
(Debian 9.3.0-17), GNU ld (GNU Binutils for Debian) 2.35) #1 SMP Debian 
5.7.17-1 (2020-08-23)

/proc/driver/nvidia/version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.138  Thu May 14 01:01:53 
PDT 2020
GCC version:  gcc version 9.3.0 (Debian 9.3.0-17) 

lspci 'display controller [030?]':
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK107GLM [Quadro 
K1100M] [10de:0ff6] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Dell GK107GLM [Quadro K1100M] [1028:05cc]
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: nvidia
Kernel modules: nvidia

dmesg:

Device node permissions:
crw-rw+ 1 root video  226,   0 Sep  8 07:11 /dev/dri/card0
crw-rw+ 1 root render 226, 128 Sep  8 07:11 /dev/dri/renderD128
crw-rw-rw-  1 root root   195, 254 Sep  8 07:11 /dev/nvidia-modeset
crw-rw-rw-  1 root root   195,   0 Sep  8 07:11 /dev/nvidia0
crw-rw-rw-  1 root root   195, 255 Sep  8 07:11 /dev/nvidiactl

/dev/dri/by-path:
total 0
lrwxrwxrwx 1 root root  8 Sep  8 07:11 pci-:01:00.0-card -> ../card0
lrwxrwxrwx 1 root root 13 Sep  8 07:11 pci-:01:00.0-render -> ../renderD128
video:x:44:wizard

OpenGL and NVIDIA library files installed:
lrwxrwxrwx 1 root root   15 Aug 29 11:01 /etc/alternatives/glx -> 
/usr/lib/nvidia
lrwxrwxrwx 1 root root   51 Aug 29 11:01 
/etc/alternatives/glx--libEGL.so.1-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libEGL.so.1
lrwxrwxrwx 1 root root   50 Aug 29 11:01 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1
lrwxrwxrwx 1 root root   50 Aug 29 11:01 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1
lrwxrwxrwx 1 root root   54 Aug 29 11:01 
/etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2
lrwxrwxrwx 1 root root   54 Aug 29 11:01 
/etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2
lrwxrwxrwx 1 root root   44 Aug 29 11:01 
/etc/alternatives/glx--libGLX_indirect.so.0-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/libGLX_nvidia.so.0
lrwxrwxrwx 1 root root   44 Aug 29 11:01 
/etc/alternatives/glx--libGLX_indirect.so.0-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/libGLX_nvidia.so.0
lrwxrwxrwx 1 root root   25 Aug 29 11:01 
/etc/alternatives/glx--linux-libglx.so -> /usr/lib/nvidia/libglx.so
lrwxrwxrwx 1 root root   42 Aug 29 11:01 
/etc/alternatives/glx--nvidia-blacklists-nouveau.conf -> 
/etc/nvidia/nvidia-blacklists-nouveau.conf
lrwxrwxrwx 1 root root   36 Aug 29 11:01 
/etc/alternatives/glx--nvidia-bug-report.sh -> 
/usr/lib/nvidia/nvidia-bug-report.sh
lrwxrwxrwx 1 root root   39 Aug 29 11:01 
/etc/alternatives/glx--nvidia-drm-outputclass.conf -> 
/etc/nvidia/nvidia-drm-outputclass.conf
lrwxrwxrwx 1 root root   28 Aug 29 11:01 
/etc/alternatives/glx--nvidia-load.conf -> /etc/nvidia/nvidia-load.conf
lrwxrwxrwx 1 root root   32 Aug 29 11:01 
/etc/alternatives/glx--nvidia-modprobe.conf -> /etc/nvidia/nvidia-modprobe.conf
lrwxrwxrwx 1 root root   29 Aug 29 11:01 
/etc/alternatives/glx--nvidia_drv.so -> /usr/lib/nvidia/nvidia_drv.so
lrwxrwxrwx 1 root root   28 Aug 29 11:01 /etc/alternatives/nvidia -> 
/usr/lib/nvidia/legacy-390xx
lrwxrwxrwx 1 root root   64 Aug 29 11:01 
/etc/alternatives/nvidia--libEGL_nvidia.so.0-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/legacy-390xx/libEGL_nvidia.so.0
lrwxrwxrwx 1 root root   64 Aug 29 11:01 
/etc/alternatives/nvidia--libGLX_nvidia.so.0-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/legacy-390xx/libGLX_nvidia.so.0
lrwxrwxrwx 1 root root   64 Aug 29 11:01 
/etc/alternatives/nvidia--libGLX_nvidia.so.0-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/legacy-390xx/libGLX_nvidia.so.0
lrwxrwxrwx 1 root root   38 Aug 29 11:01 
/etc/alternatives/nvidia--libglx.so -> /usr/lib/nvidia/legacy-390xx/libglx.so
lrwxrwxrwx 1 root root   63 Aug 29 11:01 
/etc/alternatives/nvidia--libnvidia-ml.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/legacy-390xx/libnvidia-ml.so.1
lrwxrwxrwx 1 root root   66 Aug 29 11:01 
/etc/alternatives/nvidia--libvdpau_nvidia.so.1-x86_64-linux-gnu -> 

Bug#964742: marked as done (src:binutils-mingw-w64: FTBFS on s390x: FAIL: objcopy executable (pr25662))

[Debian Bug Tracking System]

Your message dated Tue, 08 Sep 2020 12:18:27 +
with message-id 
and subject line Bug#964742: fixed in binutils-mingw-w64 8.11
has caused the Debian Bug report #964742,
regarding src:binutils-mingw-w64: FTBFS on s390x: FAIL: objcopy executable 
(pr25662)
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.)


-- 
964742: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964742
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:binutils-mingw-w64
Version: 8.10
Severity: serious
Justification: ftbfs

Dear Maintainer,

binutils-mingw-w64 FTBFS on s390x and other big-endian architectures;
the test suite fails with

FAIL: objcopy executable (pr25662)

Regards,

The Maintainer

-- System Information:
Debian Release: 10.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-debug'), (500, 'stable'), 
(100, 'unstable-debug'), (100, 'testing-debug'), (100, 'unstable'), (100, 
'testing'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-9-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: binutils-mingw-w64
Source-Version: 8.11
Done: Stephen Kitt 

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

Debian distribution maintenance software
pp.
Stephen Kitt  (supplier of updated binutils-mingw-w64 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 08 Sep 2020 13:56:45 +0200
Source: binutils-mingw-w64
Architecture: source
Version: 8.11
Distribution: unstable
Urgency: medium
Maintainer: Stephen Kitt 
Changed-By: Stephen Kitt 
Closes: 964742
Changes:
 binutils-mingw-w64 (8.11) unstable; urgency=medium
 .
   * Disable the PR/25662 test, it fails on big-endian platforms but the
 tested scenario is unlikely. Closes: #964742.
   * Lintian: rename “manpage-has-errors-from-man” to “groff-message”.
   * Replace debian/compat with a dependency on debhelper-compat.
   * Add more spelling fixes.
Checksums-Sha1:
 e7fbca16ef73ad5321da6af35a8c2ce27e3c5838 1910 binutils-mingw-w64_8.11.dsc
 883622dda6df6ea70f85ad9cf88e51106befe96d 11584 binutils-mingw-w64_8.11.tar.xz
 9f69a6d5d7c5f95600cb74477ab52450e1daf8c7 7146 
binutils-mingw-w64_8.11_source.buildinfo
Checksums-Sha256:
 2c0a954965f874d6acf5a6b9decdded5384b08ac622b41fcba2627f9b37ff13b 1910 
binutils-mingw-w64_8.11.dsc
 3dc8bbdfcf3dab7461bf3c4f8e65ccab13c35072c9c20dec84a86816f8583cce 11584 
binutils-mingw-w64_8.11.tar.xz
 9193c98cdfa85dd0ab0c8ecb325762861b9a81e2c5956b7e9f99701a714f2e4a 7146 
binutils-mingw-w64_8.11_source.buildinfo
Files:
 afb9b47dd1edbe9429a5abfedeb19f94 1910 devel optional 
binutils-mingw-w64_8.11.dsc
 32eaacedf560d0f8057ed56cd0a81c16 11584 devel optional 
binutils-mingw-w64_8.11.tar.xz
 59e2fe3533aab38261f558e162fa13bb 7146 devel optional 
binutils-mingw-w64_8.11_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEnPVX/hPLkMoq7x0ggNMC9Yhtg5wFAl9XcYoACgkQgNMC9Yht
g5zzSg/9E16yoewkr2Gl42zvkRTl9osa2M0qU7C9N+nTy+/5eYZs6woHHsjX9syv
3Kg4KYmlnk6XK8+nSyEdqX9dCHRihkS4NvTewdnBRxQbsexkTQ/9K/lePnPyB345
HNqfa3dKuB/ACF/FGnsngjYRHfVb8AslTHMzHtMGMuOoZfArP/KpEk8XVO5xVF78
lzrfqbxm1KelBm8CWLwCF0estSlc5EEiWSf4WUsI5PpB4VmVobzRJCcizg9066Gv
c6OMO5wVkPIeIjOYjoCCvUbDu13kgJEn2CgPwx+OB4VzlWIEozGhez2ETM2AsUIm
hHKNka+nXL8G+jv8PUmqTdNXiJQL6XNF8J9gGa0Mqe8v/t4kUHxD+lCHS2wAF1hj
Vb/4Dzv24FIGhsaGcEYs2twbIwApjzPIVySGc++kwxW0nU3OxQgB3THc1w4ed9Ej
b6h4K6DW4ALGpleWtqk1vq1CguxnaNZOWG4NIb6UMP7z81cicvBHyjdDZJSv6gvQ
aMjLMna7gpTKCl15OdWzdEO72nmAcNpp5zKrF9+BLBlWnWePjytjmTmpLFrtXP+N
jZy9G3k6yf0DTeZuYW5SVpse6Cf8XLxkMYSoJ3x7enhxDUxbzj3iHU1o6s72kDTY
hx6+j7XUUwmTW6ky62WafM0vOTGQuxVq7O9/EQsF1xSJL5xfi60=
=tQV1
-END PGP SIGNATURE End Message ---

Processed: Re: Bug#969889: linux-image-5.8.0-1-amd64: fails to load kernel modules, X does not work

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #969889 [src:linux] linux-image-5.8.0-1-amd64: fails to load kernel 
modules, X does not work
Added tag(s) moreinfo.
> severity -1 important
Bug #969889 [src:linux] linux-image-5.8.0-1-amd64: fails to load kernel 
modules, X does not work
Severity set to 'important' from 'grave'

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

Bug#969889: linux-image-5.8.0-1-amd64: fails to load kernel modules, X does not work

[Bastian Blank]

Control: tag -1 moreinfo
Control: severity -1 important

On Tue, Sep 08, 2020 at 01:36:45PM +0200, Vincent Lefevre wrote:
> This version fails to load kernel modules (no issues with previous
> Linux kernels provided by Debian). As a consequence, X does not work.

> ** Loaded modules:
> rfcomm
> ipt_REJECT

Your system have a lot of loaded modules.  Please provide the real error
message.

Bastian

-- 
Each kiss is as the first.
-- Miramanee, Kirk's wife, "The Paradise Syndrome",
   stardate 4842.6

Bug#969753: diffoscope: autopkgtest failures

[Chris Lamb]

Hi Gianfranco,

> Hello, autopkgtests looks sad, pytest-with-recommends works, while
> pytest doesn't, because of missing pgpdump
>
> I did add some @skip_unless_tools_exist("pgpdump") around the failing
> tests (attached the diff), however I don't know
> if this is the right solution, or something better has to be
> implemented.

Thanks. Adding the decorator in test_pgp.py looks fine at a first
glance, but needing PGP support to diff two directories (!) is a
symptom of a deeper problem with pgpdump integration.

Will investigate.


Regards,

--
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org  chris-lamb.co.uk
   `-

Processed: owner 969888

[Debian Bug Tracking System]

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

> owner 969888 woodrow.s...@gmail.com
Bug #969888 [src:pdf2djvu] pdf2djvu FTBFS with poppler 20
Owner recorded as woodrow.s...@gmail.com.
> thanks
Stopping processing here.

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

Bug#966982: Uploading disabling that test to DELAYED/2

[Thomas Goirand]

Hi,

Since nobody seem to care about this, I've uploaded disabling that
failing test to DELAYED/2. Indeed, to me, it looked like a broken test,
rather than a broken package. Otherwise, a long list of reverse
dependency will be removed from testing in 8 days.

Debdiff of the change attached. Let me know if you would like me to
cancel the upload.

Cheers,

Thomas Goirand (zigo)
diff -Nru wand-0.6.1/debian/changelog wand-0.6.1/debian/changelog
--- wand-0.6.1/debian/changelog 2020-05-20 17:40:01.0 +0200
+++ wand-0.6.1/debian/changelog 2020-09-08 13:29:49.0 +0200
@@ -1,3 +1,10 @@
+wand (0.6.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Removed failing test (Closes: #966982).
+
+ -- Thomas Goirand   Tue, 08 Sep 2020 13:29:49 +0200
+
 wand (0.6.1-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru wand-0.6.1/debian/patches/remove-failing-test.patch 
wand-0.6.1/debian/patches/remove-failing-test.patch
--- wand-0.6.1/debian/patches/remove-failing-test.patch 1970-01-01 
01:00:00.0 +0100
+++ wand-0.6.1/debian/patches/remove-failing-test.patch 2020-09-08 
13:29:44.0 +0200
@@ -0,0 +1,27 @@
+Description: Remove failing test
+Author: Thomas Goirand 
+Bug-Debian: https://bugs.debian.org/966982
+Forwarded: no
+Last-Update: 2020-09-08
+
+--- wand-0.6.1.orig/tests/image_properties_test.py
 wand-0.6.1/tests/image_properties_test.py
+@@ -42,18 +42,6 @@ def test_alpha_channel_set(fx_asset):
+ img.alpha_channel = 'watermark'
+ 
+ 
+-def test_artifacts():
+-with Image(filename='rose:') as img:
+-img.artifacts['key'] = 'value'
+-assert 'date:create' in img.artifacts
+-assert img.artifacts['key'] == 'value'
+-assert img.artifacts['novalue'] is None
+-assert len(img.artifacts) > 0
+-for key, value in img.artifacts.items():
+-pass
+-del img.artifacts['key']
+-
+-
+ def test_background_color_get(fx_asset):
+ """Gets the background color."""
+ with Image(filename=str(fx_asset.join('mona-lisa.jpg'))) as img:
diff -Nru wand-0.6.1/debian/patches/series wand-0.6.1/debian/patches/series
--- wand-0.6.1/debian/patches/series2020-05-20 17:40:01.0 +0200
+++ wand-0.6.1/debian/patches/series2020-09-08 13:28:58.0 +0200
@@ -1,3 +1,4 @@
 block_image_url.patch
 flask-sphinx-themes.patch
 no-intersphinx.patch
+remove-failing-test.patch

Bug#969889: linux-image-5.8.0-1-amd64: fails to load kernel modules, X does not work

[Vincent Lefevre]

Package: src:linux
Version: 5.8.7-1
Severity: grave
Justification: renders package unusable

This version fails to load kernel modules (no issues with previous
Linux kernels provided by Debian). As a consequence, X does not work.

I've attached the dmesg output.

-- Package-specific info:
** Version:
Linux version 5.8.0-1-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 
10.2.0-6) 10.2.0, GNU ld (GNU Binutils for Debian) 2.35) #1 SMP Debian 5.8.7-1 
(2020-09-05)

** Command line:
BOOT_IMAGE=/vmlinuz-5.8.0-1-amd64 root=/dev/mapper/zira--vg-root ro quiet

** Not tainted

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Model information
sys_vendor: Hewlett-Packard
product_name: HP ZBook 15 G2
product_version: A3008CD10003
chassis_vendor: Hewlett-Packard
chassis_version: 
bios_vendor: Hewlett-Packard
bios_version: M70 Ver. 01.08
board_vendor: Hewlett-Packard
board_name: 2253
board_version: KBC Version 03.10

** Loaded modules:
rfcomm
ipt_REJECT
nf_reject_ipv4
xt_multiport
nft_compat
nft_counter
nf_tables
nfnetlink
cmac
algif_hash
algif_skcipher
af_alg
cpufreq_conservative
cpufreq_userspace
cpufreq_powersave
bnep
btusb
btrtl
btbcm
iwlmvm
btintel
bluetooth
intel_rapl_msr
mac80211
libarc4
mei_wdt
intel_rapl_common
snd_hda_codec_realtek
jitterentropy_rng
binfmt_misc
iwlwifi
snd_hda_codec_generic
drbg
ledtrig_audio
x86_pkg_temp_thermal
snd_hda_codec_hdmi
ansi_cprng
intel_powerclamp
cfg80211
coretemp
ecdh_generic
hp_wmi
ecc
snd_hda_intel
sparse_keymap
rapl
snd_intel_dspcfg
uvcvideo
intel_cstate
snd_hda_codec
intel_uncore
videobuf2_vmalloc
videobuf2_memops
snd_hda_core
videobuf2_v4l2
videobuf2_common
iTCO_wdt
joydev
snd_hwdep
intel_pmc_bxt
videodev
snd_pcm
pcspkr
iTCO_vendor_support
serio_raw
mxm_wmi
wmi_bmof
mei_me
snd_timer
tpm_infineon
watchdog
sg
mc
rfkill
apple_mfi_fastcharge
at24
snd
mei
soundcore
evdev
tpm_tis
tpm_tis_core
tpm
hp_accel
lis3lv02d
hp_wireless
rng_core
ac
button
parport_pc
ppdev
drm
lp
parport
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
crc32c_generic
dm_crypt
dm_mod
sd_mod
sr_mod
cdrom
t10_pi
crc_t10dif
crct10dif_generic
hid_apple
hid_generic
usbhid
hid
crct10dif_pclmul
crct10dif_common
crc32_pclmul
crc32c_intel
ghash_clmulni_intel
rtsx_pci_sdmmc
mmc_core
ahci
libahci
libata
aesni_intel
xhci_pci
libaes
crypto_simd
xhci_hcd
cryptd
glue_helper
psmouse
ehci_pci
ehci_hcd
e1000e
i2c_i801
scsi_mod
i2c_smbus
usbcore
rtsx_pci
lpc_ich
ptp
pps_core
usb_common
battery
video
wmi

** Network status:
*** IP interfaces and addresses:
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host 
   valid_lft forever preferred_lft forever
2: eth0:  mtu 1500 qdisc pfifo_fast state UP 
group default qlen 1000
link/ether 30:8d:99:25:ad:3f brd ff:ff:ff:ff:ff:ff
inet 192.168.1.3/24 brd 192.168.1.255 scope global dynamic noprefixroute 
eth0
   valid_lft 86221sec preferred_lft 86221sec
inet6 fe80::b735:e72d:ac2d:f50/64 scope link noprefixroute 
   valid_lft forever preferred_lft forever
3: wlp61s0:  mtu 1500 qdisc noqueue state 
DOWN group default qlen 1000
link/ether cc:3d:82:a9:e3:ea brd ff:ff:ff:ff:ff:ff

*** Device statistics:
Inter-|   Receive|  Transmit
 face |bytespackets errs drop fifo frame compressed multicast|bytes
packets errs drop fifo colls carrier compressed
lo:   31682 360000 0  0 031682 
360000 0   0  0
  eth0:  9841141134000 0  0 4   217083 
945000 0   0  0
wlp61s0:   0   0000 0  0 00 
  0000 0   0  0

*** Protocol statistics:
Ip:
Forwarding: 2
1036 total packets received
1 with invalid addresses
0 forwarded
0 incoming packets discarded
1008 incoming packets delivered
1077 requests sent out
20 outgoing packets dropped
548 dropped because of missing route
2 reassemblies required
1 packets reassembled ok
Icmp:
46 ICMP messages received
0 input ICMP message failed
ICMP input histogram:
destination unreachable: 46
64 ICMP messages sent
0 ICMP messages failed
ICMP output histogram:
destination unreachable: 64
IcmpMsg:
InType3: 46
OutType3: 64
Tcp:
28 active connection openings
5 passive connection openings
9 failed connection attempts
2 connection resets received
0 connections established
648 segments received
721 segments sent out
9 segments retransmitted
0 bad segments received
31 resets sent
Udp:
412 packets received
40 packets to unknown port received
0 packet receive errors
463 packets sent
0 receive buffer errors
 

Bug#969888: pdf2djvu FTBFS with poppler 20

[peter green]

Source: pdf2djvu
Version: 0.9.17-1
Severity: serious
Tags: ftbfs, fixed-upstream

pdf2djvu's configure script fails to parse the poppler version with the newly 
released poppler 20.
This results in a bunch of errors.

This is fixed upstream in version 0.9.17.1

Bug#966653: Any progress?

[Thomas Goirand]

Hi,

I'm not seeing any progress on this bug. Is anyone working on this?
Without any action, this going to trigger the removal of most of
OpenStack from testing... :/

Cheers,

Thomas Goirand (zigo)

Bug#963827: [virtualbox] guests limited to 800x600

[Gianfranco Costamagna]

Hello,


On Sat, 27 Jun 2020 23:25:26 +0100 Lyndon Brown  wrote:
> Package: src:virtualbox
> Version: 6.1.10-dfsg-1
> Severity: important
> 
> After installing a handful of updates in a Sid guest and rebooting it,
> it's now stuck with an unusable display area of 800x600.
> 

should be fixed now

G.

Bug#969883: yowsup: autopkgtest should be marked superficial

[Sudip Mukherjee]

Source: yowsup
Severity: serious
Usertags: superficialtest
X-Debbugs-CC: elb...@debian.org

Hi,

The test done in the autopkgtest of 'yowsup' does not provide
significant test coverage and it should be marked with "Restrictions:
superficial".

Ref: https://people.debian.org/~eriberto/README.package-tests.html

Examples of tests which are not significant includes (its not a
complete list):

1) Executing the binary to check version

Test-Command: foo -v

Test-Command: foo -V

Test-Command: foo --version

2) Executing the binary to check help (foo -h)

Test-Command: foo -h

Test-Command: foo --help

3) checking for files installed with 'ls'.

Test-Command: ls -l /usr/lib/*/foo.so

4) A Python or Perl library runs import foo or require Foo; but does
not attempt to use the library beyond that.

Test-Command: python3 -c "import foo"

Please add "Restrictions: superficial" to 'debian/tests/control' of
'yowsup'.

--

Sudip 

Bug#969880: wig: autopkgtest should be marked superficial

[Sudip Mukherjee]

Source: wig
Severity: serious
Usertags: superficialtest
X-Debbugs-CC: elb...@debian.org

Hi,

The test done in the autopkgtest of 'wig' does not provide
significant test coverage and it should be marked with "Restrictions:
superficial".

Ref: https://people.debian.org/~eriberto/README.package-tests.html

Examples of tests which are not significant includes (its not a
complete list):

1) Executing the binary to check version

Test-Command: foo -v

Test-Command: foo -V

Test-Command: foo --version

2) Executing the binary to check help (foo -h)

Test-Command: foo -h

Test-Command: foo --help

3) checking for files installed with 'ls'.

Test-Command: ls -l /usr/lib/*/foo.so

4) A Python or Perl library runs import foo or require Foo; but does
not attempt to use the library beyond that.

Test-Command: python3 -c "import foo"

Please add "Restrictions: superficial" to 'debian/tests/control' of
'wig'.

--

Sudip 

Bug#969882: wmxres: autopkgtest should be marked superficial

[Sudip Mukherjee]

Source: wmxres
Severity: serious
Usertags: superficialtest
X-Debbugs-CC: elb...@debian.org

Hi,

The test done in the autopkgtest of 'wmxres' does not provide
significant test coverage and it should be marked with "Restrictions:
superficial".

Ref: https://people.debian.org/~eriberto/README.package-tests.html

Examples of tests which are not significant includes (its not a
complete list):

1) Executing the binary to check version

Test-Command: foo -v

Test-Command: foo -V

Test-Command: foo --version

2) Executing the binary to check help (foo -h)

Test-Command: foo -h

Test-Command: foo --help

3) checking for files installed with 'ls'.

Test-Command: ls -l /usr/lib/*/foo.so

4) A Python or Perl library runs import foo or require Foo; but does
not attempt to use the library beyond that.

Test-Command: python3 -c "import foo"

Please add "Restrictions: superficial" to 'debian/tests/control' of
'wmxres'.

--

Sudip 

Bug#969879: wifite: autopkgtest should be marked superficial

[Sudip Mukherjee]

Source: wifite
Severity: serious
Usertags: superficialtest
X-Debbugs-CC: elb...@debian.org

Hi,

The test done in the autopkgtest of 'wifite' does not provide
significant test coverage and it should be marked with "Restrictions:
superficial".

Ref: https://people.debian.org/~eriberto/README.package-tests.html

Examples of tests which are not significant includes (its not a
complete list):

1) Executing the binary to check version

Test-Command: foo -v

Test-Command: foo -V

Test-Command: foo --version

2) Executing the binary to check help (foo -h)

Test-Command: foo -h

Test-Command: foo --help

3) checking for files installed with 'ls'.

Test-Command: ls -l /usr/lib/*/foo.so

4) A Python or Perl library runs import foo or require Foo; but does
not attempt to use the library beyond that.

Test-Command: python3 -c "import foo"

Please add "Restrictions: superficial" to 'debian/tests/control' of
'wifite'.

--

Sudip 

Bug#969156: marked as done (rumur FTBFS on armel/armhf/mipsel/mips64el: test failures)

[Debian Bug Tracking System]

Your message dated Tue, 08 Sep 2020 10:49:24 +
with message-id 
and subject line Bug#969156: fixed in rumur 2020.09.06-1
has caused the Debian Bug report #969156,
regarding rumur FTBFS on armel/armhf/mipsel/mips64el: test failures
to be marked as done.

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

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


-- 
969156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969156
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rumur
Version: 2020.05.27-1
Severity: serious
Tags: ftbfs

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

...
FAIL   basic-sandbox.m
Unexpected checker exit status -31:
FAILX  basic-sandbox.m
Unexpected checker exit status -31:
FAIL   M   basic-sandbox.m
Unexpected checker exit status -31:
FAIL   MX  basic-sandbox.m
Unexpected checker exit status -31:
FAIL  Obasic-sandbox.m
Unexpected checker exit status -31:
FAIL  O X  basic-sandbox.m
Unexpected checker exit status -31:
FAIL  OM   basic-sandbox.m
Unexpected checker exit status -31:
FAIL  OMX  basic-sandbox.m
Unexpected checker exit status -31:
FAIL D basic-sandbox.m
Unexpected checker exit status -31:
FAIL D M   basic-sandbox.m
Unexpected checker exit status -31:
FAIL DObasic-sandbox.m
Unexpected checker exit status -31:
FAIL DOM   basic-sandbox.m
Unexpected checker exit status -31:
...
FAIL - exec strace-sandbox.sh
...
--- SIGSYS {si_signo=SIGSYS, si_code=SYS_SECCOMP, si_call_addr=0xb6e84bf8, 
si_syscall=__NR_clock_gettime64, si_arch=AUDIT_ARCH_ARM} ---
+++ killed by SIGSYS +++
/<>/tests/strace-sandbox.sh: line 69: 10391 Bad system call
 strace ./model.exe
...
2794 passed, 1918 skipped, 13 failed out of 4725 total tests
make[4]: *** [CMakeFiles/check.dir/build.make:60: CMakeFiles/check] Error 1


The version in testing also started failing:
https://tests.reproducible-builds.org/debian/history/armhf/rumur.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/armhf/rumur.html
--- End Message ---
--- Begin Message ---
Source: rumur
Source-Version: 2020.09.06-1
Done: Matthew Fernandez 

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

Debian distribution maintenance software
pp.
Matthew Fernandez  (supplier of updated rumur 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 07 Sep 2020 09:43:16 -0700
Source: rumur
Architecture: source
Version: 2020.09.06-1
Distribution: unstable
Urgency: medium
Maintainer: Matthew Fernandez 
Changed-By: Matthew Fernandez 
Closes: 969156
Changes:
 rumur (2020.09.06-1) unstable; urgency=medium
 .
   * New upstream release.
 .
   * Fix armel, armhf, mipsel, mips64el sandboxing. Closes: #969156.
Checksums-Sha1:
 fd5d099c531f6091119247b708e85e98fabb7378 2037 rumur_2020.09.06-1.dsc
 2866346dc56c66c8cfbb43ce0cf07407615f44d7 292330 rumur_2020.09.06.orig.tar.gz
 12cdd324b4673126b83c1a8e46bf57b2acbce2cd 5220 rumur_2020.09.06-1.debian.tar.xz
 b9ac26c78e29ac11bac68b6a93acf637f7f6c5a7 6490 
rumur_2020.09.06-1_source.buildinfo
Checksums-Sha256:
 5d34dd6b1422494de196bedc571485de37bd509659992bc43d61c42e2865f755 2037 
rumur_2020.09.06-1.dsc
 99ea8ad72a48210e5af9e1083cdb6d0da69da0ecb13385e18c204e0ed65e5502 292330 
rumur_2020.09.06.orig.tar.gz
 6e08991136498439a9a77599b3f80b1efab9c1c4868208406cbd05970f71ed70 5220 
rumur_2020.09.06-1.debian.tar.xz
 24def1c8125a09d5a16957af0717227175f6cdf2db58ddfc355719b7a8561b2b 6490 
rumur_2020.09.06-1_source.buildinfo
Files:
 36903311143dc8d33df415088349b6a0 2037 devel optional rumur_2020.09.06-1.dsc
 67235c17c8835f8adf3046a7b3e84341 292330 devel optional 
rumur_2020.09.06.orig.tar.gz
 53771238acaaa39ad8f307528ead1090 5220 devel optional 
rumur_2020.09.06-1.debian.tar.xz
 0a2bf61ea9e1484c4b6b547a688ce311 6490 devel optional 
rumur_2020.09.06-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl9XXhEACgkQweDZLphv
fH7c/w//XUUqdgKXoOVlUVhNb99TDfpBnkRDflxmSXR84wGKx63WYYs/pKMGKKW5
WroTFs9SIUkkYDwfncdmsFd4VdOeAgyuNida/zck/t6oDhoBFwyWdy/KqkdJLibk
GcR7priKKNagIzLYlXBdrwZFOVgB9Hb6HgXy8+1UZgXrCCkfUIg92EPoerc4HOA1

Bug#969878: virt-what: autopkgtest should be marked superficial

[Sudip Mukherjee]

Source: virt-what
Severity: serious
Usertags: superficialtest
X-Debbugs-CC: elb...@debian.org

Hi,

The test done in the autopkgtest of 'virt-what' does not provide
significant test coverage and it should be marked with "Restrictions:
superficial".

Ref: https://people.debian.org/~eriberto/README.package-tests.html

Examples of tests which are not significant includes (its not a
complete list):

1) Executing the binary to check version

Test-Command: foo -v

Test-Command: foo -V

Test-Command: foo --version

2) Executing the binary to check help (foo -h)

Test-Command: foo -h

Test-Command: foo --help

3) checking for files installed with 'ls'.

Test-Command: ls -l /usr/lib/*/foo.so

4) A Python or Perl library runs import foo or require Foo; but does
not attempt to use the library beyond that.

Test-Command: python3 -c "import foo"

Please add "Restrictions: superficial" to 'debian/tests/control' of
'virt-what'.

--

Sudip 

Bug#969788: nextcloud-desktop: Upgrade removed part of configuration

[Marek Straka]

I always synchronized only some directories from nextcloud server. After 
upgrade nextcloud client started to synchronize everything because all folders 
was checked.

Bug#969881: wmforecast: autopkgtest should be marked superficial

[Sudip Mukherjee]

Source: wmforecast
Severity: serious
Usertags: superficialtest
X-Debbugs-CC: elb...@debian.org

Hi,

The test done in the autopkgtest of 'wmforecast' does not provide
significant test coverage and it should be marked with "Restrictions:
superficial".

Ref: https://people.debian.org/~eriberto/README.package-tests.html

Examples of tests which are not significant includes (its not a
complete list):

1) Executing the binary to check version

Test-Command: foo -v

Test-Command: foo -V

Test-Command: foo --version

2) Executing the binary to check help (foo -h)

Test-Command: foo -h

Test-Command: foo --help

3) checking for files installed with 'ls'.

Test-Command: ls -l /usr/lib/*/foo.so

4) A Python or Perl library runs import foo or require Foo; but does
not attempt to use the library beyond that.

Test-Command: python3 -c "import foo"

Please add "Restrictions: superficial" to 'debian/tests/control' of
'wmforecast'.

--

Sudip 

Bug#969876: virt-top: autopkgtest should be marked superficial

[Sudip Mukherjee]

Source: virt-top
Severity: serious
Usertags: superficialtest
X-Debbugs-CC: elb...@debian.org

Hi,

The test done in the autopkgtest of 'virt-top' does not provide
significant test coverage and it should be marked with "Restrictions:
superficial".

Ref: https://people.debian.org/~eriberto/README.package-tests.html

Examples of tests which are not significant includes (its not a
complete list):

1) Executing the binary to check version

Test-Command: foo -v

Test-Command: foo -V

Test-Command: foo --version

2) Executing the binary to check help (foo -h)

Test-Command: foo -h

Test-Command: foo --help

3) checking for files installed with 'ls'.

Test-Command: ls -l /usr/lib/*/foo.so

4) A Python or Perl library runs import foo or require Foo; but does
not attempt to use the library beyond that.

Test-Command: python3 -c "import foo"

Please add "Restrictions: superficial" to 'debian/tests/control' of
'virt-top'.

--

Sudip 

Bug#969875: vinetto: autopkgtest should be marked superficial

[Sudip Mukherjee]

Source: vinetto
Severity: serious
Usertags: superficialtest
X-Debbugs-CC: elb...@debian.org

Hi,

The test done in the autopkgtest of 'vinetto' does not provide
significant test coverage and it should be marked with "Restrictions:
superficial".

Ref: https://people.debian.org/~eriberto/README.package-tests.html

Examples of tests which are not significant includes (its not a
complete list):

1) Executing the binary to check version

Test-Command: foo -v

Test-Command: foo -V

Test-Command: foo --version

2) Executing the binary to check help (foo -h)

Test-Command: foo -h

Test-Command: foo --help

3) checking for files installed with 'ls'.

Test-Command: ls -l /usr/lib/*/foo.so

4) A Python or Perl library runs import foo or require Foo; but does
not attempt to use the library beyond that.

Test-Command: python3 -c "import foo"

Please add "Restrictions: superficial" to 'debian/tests/control' of
'vinetto'.

--

Sudip 

Bug#969872: termineter: autopkgtest should be marked superficial

[Sudip Mukherjee]

Source: termineter
Severity: serious
Usertags: superficialtest
X-Debbugs-CC: elb...@debian.org

Hi,

The test done in the autopkgtest of 'termineter' does not provide
significant test coverage and it should be marked with "Restrictions:
superficial".

Ref: https://people.debian.org/~eriberto/README.package-tests.html

Examples of tests which are not significant includes (its not a
complete list):

1) Executing the binary to check version

Test-Command: foo -v

Test-Command: foo -V

Test-Command: foo --version

2) Executing the binary to check help (foo -h)

Test-Command: foo -h

Test-Command: foo --help

3) checking for files installed with 'ls'.

Test-Command: ls -l /usr/lib/*/foo.so

4) A Python or Perl library runs import foo or require Foo; but does
not attempt to use the library beyond that.

Test-Command: python3 -c "import foo"

Please add "Restrictions: superficial" to 'debian/tests/control' of
'termineter'.

--

Sudip 

Bug#969873: twython: autopkgtest should be marked superficial

[Sudip Mukherjee]

Source: twython
Severity: serious
Usertags: superficialtest
X-Debbugs-CC: elb...@debian.org

Hi,

The test done in the autopkgtest of 'twython' does not provide
significant test coverage and it should be marked with "Restrictions:
superficial".

Ref: https://people.debian.org/~eriberto/README.package-tests.html

Examples of tests which are not significant includes (its not a
complete list):

1) Executing the binary to check version

Test-Command: foo -v

Test-Command: foo -V

Test-Command: foo --version

2) Executing the binary to check help (foo -h)

Test-Command: foo -h

Test-Command: foo --help

3) checking for files installed with 'ls'.

Test-Command: ls -l /usr/lib/*/foo.so

4) A Python or Perl library runs import foo or require Foo; but does
not attempt to use the library beyond that.

Test-Command: python3 -c "import foo"

Please add "Restrictions: superficial" to 'debian/tests/control' of
'twython'.

--

Sudip