Bug#962813: does not build with ghc 8.8

[Mike Gabriel]

Hi,

On  So 14 Jun 2020 16:41:31 CEST, Picca Frédéric-Emmanuel wrote:


Source: haskell-tree-monad
Severity: critical

Hello,

this package does not build with the up-comming ghc 8.8 version.
It is not part of stackage LTS, and it was not updated by upstream  
since 2009.

It means that there is few chance to see the upstream fix this issue.

so it is considere to remove it from Debian.

Someone can salvage it by providing a patch (prefereably to the  
upstream first).


Cheers


I have pinged upstream (off-list, off-bts) on this issue and will  
provide feedback once I hear from them.


Mike
--

DAS-NETZWERKTEAM
c\o Technik- und Ökologiezentrum Eckernförde
Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde
mobile: +49 (1520) 1976 148
landline: +49 (4351) 850 8940

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgpLUecv6ascY.pgp
Description: Digitale PGP-Signatur

Bug#962844: mdadm: Assembling RAID using IMSM in initrd fails due to lack of module efivarfs

[Colin Fowler]

Package: mdadm
Version: 4.1-1
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

I created a RAID 5 volume over 4 disks using the BIOS support for Intel
RST. Install proceeded correctly, however after a reboot in to the
installed system, the root device was not found. Investigation in the
init shell found that the mdamd device had not been assembled correctly

The following error was encountered when looking for imsm capabilies on
the controller. 

mdadm --detail-platform
mdadm: imsm capabilities not found for controller: 
/sys/devices/pci:00/:00:1f.2 (type SATA)

I found that this occurred when mdadm could not read from 
/sys/firmware/efi/efivars/ due to it not being mounted. The efivarfs module was 
not found in the initrd

To resolve this, I booted in to a rescue CD and added efivarfs and
efivars to /etc/initramfs.conf/modules and ran an update-initramfs

This allowed the system to boot correctly

I suggest that mdadm ensures that these modules are added to the initrd
when the RAID array is using IMSM.


-- Package-specific info:
--- mdadm.conf
ARRAY metadata=imsm UUID=56bed0cd:2b07c313:c4651474:3a6b990c
ARRAY /dev/md/Volume0 container=56bed0cd:2b07c313:c4651474:3a6b990c member=0 
UUID=d0f942e0:fb69f9d0:bca65978:774a6c88
MAILADDR root

--- /etc/default/mdadm
AUTOCHECK=true
START_DAEMON=true
DAEMON_OPTIONS="--syslog"
VERBOSE=false

--- /proc/mdstat:
Personalities : [raid6] [raid5] [raid4] [linear] [multipath] [raid0] [raid1] 
[raid10] 
md126 : active raid5 sda[3] sdb[2] sdc[1] sdd[0]
  5567516672 blocks super external:/md127/0 level 5, 64k chunk, algorithm 0 
[4/4] []
  
md127 : inactive sdb[3](S) sdd[2](S) sdc[1](S) sda[0](S)
  20804 blocks super external:imsm
   
unused devices: 

--- /proc/partitions:
major minor  #blocks  name

   8   48 1953514584 sdd
   8   32 1953514584 sdc
   8   16 1953514584 sdb
   80 1953514584 sda
   9  126 5567516672 md126
 2590 525391 md126p1
 2591 5533714844 md126p2
 2592   33276403 md126p3

--- LVM physical volumes:
LVM does not seem to be used.
--- mount output
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs 
(rw,nosuid,relatime,size=16317648k,nr_inodes=4079412,mode=755)
devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=3266568k,mode=755)
/dev/md126p2 on / type ext4 (rw,relatime,errors=remount-ro,stripe=48)
securityfs on /sys/kernel/security type securityfs 
(rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup2 on /sys/fs/cgroup/unified type cgroup2 
(rw,nosuid,nodev,noexec,relatime,nsdelegate)
cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
efivarfs on /sys/firmware/efi/efivars type efivarfs 
(rw,nosuid,nodev,noexec,relatime)
bpf on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma)
cgroup on /sys/fs/cgroup/cpuset type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/freezer type cgroup 
(rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/memory type cgroup 
(rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/blkio type cgroup 
(rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/devices type cgroup 
(rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/perf_event type cgroup 
(rw,nosuid,nodev,noexec,relatime,perf_event)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs 
(rw,relatime,fd=27,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=12482)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
mqueue on /dev/mqueue type mqueue (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
/dev/md126p1 on /boot/efi type vfat 
(rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /run/user/1000 type tmpfs 
(rw,nosuid,nodev,relatime,size=3266564k,mode=700,uid=1000,gid=1000)

--- initrd.img-4.19.0-9-amd64:
178049 blocks
192ccafcfe38eabf0f5184786764c4a9  ./scripts/local-bottom/mdadm
f3b648ca1c912da30940f0b821b7e9e6  ./scripts/local-block/mdadm
371839b6f84393a2c8d2988933b99f80  ./etc/mdadm/mdadm.conf
d3be82c0f275d6c25b04d388baf9e836  

Bug#962323: python-django: CVE-2020-13254 CVE-2020-13596

[Chris Lamb]

Chris Lamb wrote:

> I will wait a few days to see what upstream says. I will also have to
> re-release for jessie LTS, alas.

Okay, this is now fixed in the following versions (without and with
the regression fix):

  DistributionUpload with regressionUpload with regression fixed
  
  jessie  1.7.11-1+deb8u9   1.7.11-1+deb8u10
  stretch n/a   1:1.10.7-2+deb9u9 (pending)
  buster  n/a   1:1.11.29-1~deb10u1 (pending)
  unstable2:2.2.13-12:2.2.13-2
  experimental2:3.0.7-1 2:3.0.7-2
  


The two pending uploads (ie. needing your approval) to upload are:

  python-django (1:1.10.7-2+deb9u9) stretch-security; urgency=high

* CVE-2020-13254: Potential a data leakage via malformed memcached keys.

  In cases where a memcached backend does not perform key validation, 
passing
  malformed cache keys could result in a key collision, and potential data
  leakage. In order to avoid this vulnerability, key validation is added to
  the memcached cache backends.

* CVE-2020-13596: Possible XSS via admin ForeignKeyRawIdWidget.

  Query parameters to the admin ForeignKeyRawIdWidget were not properly URL
  encoded, posing an XSS attack vector. ForeignKeyRawIdWidget now ensures
  query parameters are correctly URL encoded.

   -- Chris Lamb   Sat, 13 Jun 2020 15:47:14 +0100


and

python-django (1:1.11.29-1~deb10u1) buster-security; urgency=high

  * New upstream security release (postponed from March 2020):

- CVE-2020-9402: Potential SQL injection via tolerance parameter in GIS
  functions and aggregates on Oracle

Note that Django 1.11.x left upstream's extended security support on 
April
1st 2020. For more information, please see:

  https://www.djangoproject.com/download/

  * This upload also fixes the following security issues:

- CVE-2020-13254: Potential a data leakage via malformed memcached keys.

  In cases where a memcached backend does not perform key validation,
  passing malformed cache keys could result in a key collision, and
  potential data leakage. In order to avoid this vulnerability, key
  validation is added to the memcached cache backends.

- CVE-2020-13596: Possible XSS via admin ForeignKeyRawIdWidget.

  Query parameters to the admin ForeignKeyRawIdWidget were not properly 
URL
  encoded, posing an XSS attack vector. ForeignKeyRawIdWidget now 
ensures
  query parameters are correctly URL encoded.

 -- Chris Lamb   Sun, 14 Jun 2020 12:15:26 +0100


The full debdiffs are attached. Can you especially check the
versioning scheme and distribution fields for me? I often get this
wrong and end up confusing myself. Really appreciated.


Regards,

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

Bug#962841: python3-nanomath: ships /usr/LICENSE

[Andreas Beckmann]

Package: python3-nanomath
Version: 0.23.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files ... but a file like
/usr/LICENSE should be shipped by *no* package at all.


cheers,

Andreas

Bug#962840: python3-nanoget: ships /usr/LICENSE

[Andreas Beckmann]

Package: python3-nanoget
Version: 1.12.2-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files ... but a file like
/usr/LICENSE should be shipped by *no* package at all.


cheers,

Andreas

Bug#962685: marked as done (wordpress 5.4.2 security release)

[Debian Bug Tracking System]

Your message dated Sun, 14 Jun 2020 22:19:42 +
with message-id 
and subject line Bug#962685: fixed in wordpress 5.4.2+dfsg1-1
has caused the Debian Bug report #962685,
regarding wordpress 5.4.2 security release
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.)


-- 
962685: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962685
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wordpress
Version: 5.4.1+dfsg1-1
Severity: grave
Tags: security upstream
Justification: user security hole

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

WordPress 5.4.2 is out and fixes the following vulnerabilities:

Props to Sam Thomas (jazzy2fives) for finding an XSS issue where authenticated 
users with low privileges are able to add JavaScript to posts in the block 
editor.
https://core.trac.wordpress.org/changeset/47948
All releases

Props to Luigi – (gubello.me) for discovering an XSS issue where authenticated 
users with upload permissions are able to add JavaScript to media files.
https://core.trac.wordpress.org/changeset/47947 (I think)
All releases

Props to Ben Bidner of the WordPress Security Team for finding an open redirect 
issue in wp_validate_redirect().
https://core.trac.wordpress.org/changeset/47949
All releases

Props to Nrimo Ing Pandum for finding an authenticated XSS issue via theme 
uploads.
https://core.trac.wordpress.org/changeset/47950
All releases

Props to Simon Scannell of RIPS Technologies for finding an issue where 
set-screen-option can be misused by plugins leading to privilege escalation.
https://core.trac.wordpress.org/changeset/47951
All releases

Props to Carolina Nymark for discovering an issue where comments from 
password-protected posts and pages could be displayed under certain conditions.
https://core.trac.wordpress.org/changeset/47984
All releases

There is also a fix for unmoderated comments visible to indexers which
will be backported. WordPress say its not a security issue, but seems
like you are getting the site to do something that it shouldn't.
https://make.wordpress.org/core/2020/06/09/wordpress-5-4-2-prevent-unmoderated-comments-from-search-engine-indexation/
https://core.trac.wordpress.org/ticket/49956
https://core.trac.wordpress.org/changeset/47887
https://core.trac.wordpress.org/changeset/47889
Present: 5.4 only (5.1 onwards, see the ticket)


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

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

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEXT3w9TizJ8CqeneiAiFmwP88hOMFAl7iwOsSHGNzbWFsbEBk
ZWJpYW4ub3JnAAoJEAIhZsD/PITjYIAP/R+4+bSwUXz0IPSijvsH4PkIICe3k1wj
dBSgFWWjFcVyYZwbpQ5SqgyspGG5aFhQPNWiSAvv0BILWY///jbPmsSoqz0s58xC
QcjBkUiif1GDZq60IaA8igy2eotD90FQxr8Y16iDFSbkC0U3x4sV1UW3WlDEyxnW
ILRusFo8m0L9J+rTQUxu0SGHK4WM2nvCGNp1U3l5/JreKZxlLIeoy+y44GsCPktn
8wDIqZ91bUpfhUcyL7BZu7g94cUnC8RhZxX//TiVYlH54pXneascPuedZAGV/qi6
0TMTuSvdPd9/pKtKhCo2jUb70CRWiP4r3QDgRM7oqcx8jLaLvBcvWmaAQjpc6eZB
jgRX6HAEkm2CVFor4VtwRH/726RLLm34IokYnXU74Wp+LVjtXIYMLoP/fkbEvJW4
ClrMMEUe/+bkWLmWu6iGdbNM325eFsTvkDOngCNV/g/lsEp5gzHZwCwzL+0J21ds
/KglCuE+BRn4XSCCxOEU+HS7EM8A+NWrO95elryeVE2SRQb/11F8s6TkIMMMqFPD
B4m8+J5Ooj7LzS3dErVuXlOOVX0YXFVOL6AThfitW9SHOn37NmRsvOuSJCySKdI6
60A7WJvuH460JcpASDSR4XoJpBy+NnAkA4uTJ9ihlLKbZBkhy+vS/E/6M73yL9Aw
QCZSPwT6j/lX
=E8qn
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: wordpress
Source-Version: 5.4.2+dfsg1-1
Done: Craig Small 

We believe that the bug you reported is fixed in the latest version of
wordpress, 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.
Craig Small  (supplier of updated wordpress 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, 15 Jun 2020 07:53:44 +1000
Source: wordpress

Processed: tagging 961490

[Debian Bug Tracking System]

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

> tags 961490 + buster
Bug #961490 [fwupd] fwupd: version in stable too old, no updates possible
Added tag(s) buster.
> thanks
Stopping processing here.

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

Bug#946068: marked as done (lv2dynparam1 FTCBFS: lv2core.pc not found)

[Debian Bug Tracking System]

Your message dated Sun, 14 Jun 2020 21:03:50 +
with message-id 
and subject line Bug#946068: fixed in lv2dynparam1 2-6.1
has caused the Debian Bug report #946068,
regarding lv2dynparam1 FTCBFS: lv2core.pc not 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.)


-- 
946068: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946068
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lv2dynparam1
Version: 2-6
Severity: serious
Tags: ftbfs

lv2dynparam1 fails to build from source in unstable, because it fails
finding lv2core.pc using pkg-config:

| checking for LV2... no
| configure: error: Package requirements (lv2core >= 1) were not met:
| 
| No package 'lv2core' found
| 
| Consider adjusting the PKG_CONFIG_PATH environment variable if you
| installed software in a non-standard prefix.
| 
| Alternatively, you may set the environment variables LV2_CFLAGS
| and LV2_LIBS to avoid the need to call pkg-config.
| See the pkg-config man page for more details.
|  tail -v -n \+0 config.log

Reproduced by reproducible builds:
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/lv2dynparam1_2-6.rbuild.log.gz

Reproduced by crossqa since about a month:
http://crossqa.debian.net/src/lv2dynparam1
http://crossqa.debian.net/build/lv2dynparam1_2-6_s390x_20191102055910.log

Helmut
--- End Message ---
--- Begin Message ---
Source: lv2dynparam1
Source-Version: 2-6.1
Done: Sudip Mukherjee 

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 14 Jun 2020 18:57:30 +0100
Source: lv2dynparam1
Architecture: source
Version: 2-6.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Sudip Mukherjee 
Closes: 946068
Changes:
 lv2dynparam1 (2-6.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix FTCBFS. (Closes: #946068)
Checksums-Sha1:
 22576b8d0af9e12f9f2c408bd3dde0765bd901dc 2224 lv2dynparam1_2-6.1.dsc
 87d350eb6f76dc5818e6b6348cafe0a51cc1db9f 4936 lv2dynparam1_2-6.1.debian.tar.xz
 89dbcd80909dbfe13ccfe8f0963ec2eb9b0cf7c8 5292 
lv2dynparam1_2-6.1_source.buildinfo
Checksums-Sha256:
 47cc4e447176d4dec14c32e08b685e7478349cb83901517ec43ac48ae681bc46 2224 
lv2dynparam1_2-6.1.dsc
 d8e3d793a961ba87d3b510d25532669ce0712679a9097f11e17e35a9d815c3ab 4936 
lv2dynparam1_2-6.1.debian.tar.xz
 93bbe66d1126db41295982c11122ce3a8167f7f593464fb47b9867ef00be313d 5292 
lv2dynparam1_2-6.1_source.buildinfo
Files:
 58810be6055ca720f520491874a60153 2224 sound optional lv2dynparam1_2-6.1.dsc
 751b619d67436670abad57a447fe8038 4936 sound optional 
lv2dynparam1_2-6.1.debian.tar.xz
 d68304d46977a9d4f14c28547674d468 5292 sound optional 
lv2dynparam1_2-6.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl7mjkMACgkQweDZLphv
fH4EKg//SxW0hzi6qd8BaPPdYXxxzwfiS0VbQMzVZMHoiPoeUX651IL13pwadwd3
DXUadF8NOoutEu5gLFiRuxWqVfx+9sGFgv8vY+KG1Wh0TSRvVvQXNMe/Qw/PLEUS
NHwT9WhX7FhAyDfEtAkIQgfr7crbMttjdqsfRsxitEFQhb1xtgnaCHKDTvtljwmB
i/H7Qyx5tiFSxS6o0kTLeMRGVgiuwHsmdgHBbhnbhIoqnnO3SfBhGn9vxmq4HaMl
+Iy7lQP1DNk9AT1O+rmb3j2hiXdXQH0knbhJCFNI2V82eers1RY19+ODIwDGwY0B
54/gzciTro7MhqBQV+wXnNi1wkaLZ4dhXYraIzJbGIPWT1GnH11p1xh9ceKU//jM
RhJ9dQ9BYiDaB9JKiwBzAv+f/2sOh1XJfZ759FM9ilyRisBjtTjG9cIHKNpFWvWa
sIMXicSWGFHVdGCrHCaLOjT4k80/Rx+NOxgBxoIWXp3/fR51nXxOyVysxYdYizab
pc0PJCTgkgjv0JrlpOw0vDdJPMwXxKcC2KHU2uBfxzJX3IQvts/aKq3dM/84abd1
vYylHawscd7q46AAFGHqh0DOuJ/uBRgEle/5L08BT/dkjFNNex0yDXzEvz3ReY/N
MWfAGStKhCgC1ceD7iSAHarhmcCDlE8mZIZtnVaeemrEAIg5S+c=
=O4W3
-END PGP SIGNATURE End Message ---

Bug#959386: php-imagick: diff for NMU version 3.4.4-4.1

[Ondřej Surý]

Adrian,

please do a direct upload to unstable and thanks for the fix. No need to wait 
15 days.

--
Ondřej Surý 

> On 14 Jun 2020, at 18:51, Adrian Bunk  wrote:
> 
> Control: tags 959386 + patch
> Control: tags 959386 + pending
> 
> Dear maintainer,
> 
> I've prepared an NMU for php-imagick (versioned as 3.4.4-4.1) and
> uploaded it to DELAYED/15. Please feel free to tell me if I should 
> cancel it.
> 
> cu
> Adrian
> 

Bug#962824: marked as done (r-cran-v8: FTBFS against nodejs 12.18.0)

[Debian Bug Tracking System]

Your message dated Sun, 14 Jun 2020 20:49:52 +
with message-id 
and subject line Bug#962824: fixed in r-cran-v8 3.1.0+dfsg-2
has caused the Debian Bug report #962824,
regarding r-cran-v8: FTBFS against nodejs 12.18.0
to be marked as done.

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

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


-- 
962824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962824
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: r-cran-v8
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi,

this package cannot be built against nodejs 12.18.0.
this blocks nodejs migration to testing.

I pinged upstream about that:
https://github.com/jeroen/V8/pull/87

Cheers,
Jérémy

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

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

Versions of packages r-cran-v8 depends on:
ii  libc6 2.30-8
ii  libgcc-s1 10.1.0-3
ii  libjs-underscore  1.9.1~dfsg-1
ii  libnode64 10.21.0~dfsg-1
ii  libstdc++610.1.0-3
pn  r-api-4.0 
pn  r-base-core   
pn  r-cran-curl   
pn  r-cran-jsonlite   
pn  r-cran-rcpp   

Versions of packages r-cran-v8 recommends:
pn  r-cran-testthat  

Versions of packages r-cran-v8 suggests:
pn  r-cran-knitr  
pn  r-cran-rmarkdown  
--- End Message ---
--- Begin Message ---
Source: r-cran-v8
Source-Version: 3.1.0+dfsg-2
Done: =?utf-8?b?SsOpcsOpbXkgTGFs?= 

We believe that the bug you reported is fixed in the latest version of
r-cran-v8, 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.
Jérémy Lal  (supplier of updated r-cran-v8 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 14 Jun 2020 21:31:12 +0200
Source: r-cran-v8
Architecture: source
Version: 3.1.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers 
Changed-By: Jérémy Lal 
Closes: 962824
Changes:
 r-cran-v8 (3.1.0+dfsg-2) unstable; urgency=medium
 .
   * Team upload.
   * Upstream patch fix pointer compression test with node 12
 Closes: #962824.
Checksums-Sha1:
 ef9653e1ad754ab11a17d133fdd3d30f301193b4 2155 r-cran-v8_3.1.0+dfsg-2.dsc
 85979ea6c64da552b4b5cf2d7ff467f73cb45841 3836 
r-cran-v8_3.1.0+dfsg-2.debian.tar.xz
 f0275c37527ce99c397ae7ce7fb1e1a886c3b1d1 9371 
r-cran-v8_3.1.0+dfsg-2_source.buildinfo
Checksums-Sha256:
 95beab18fd8066865aba8cfc676ef509ecd9077b0cf5673346645b7529a0fd89 2155 
r-cran-v8_3.1.0+dfsg-2.dsc
 eea881c7e21b7d5394e3c0f8a2fd393dfd2d7b9b8c07d1ab2ac47c78c48313f3 3836 
r-cran-v8_3.1.0+dfsg-2.debian.tar.xz
 7a175219a319b5d4d6b810bf1551fa132063499f4eb2cd213f701eea0bbe302f 9371 
r-cran-v8_3.1.0+dfsg-2_source.buildinfo
Files:
 deabe6ea601fae5122ecf86ae50fae9a 2155 gnu-r optional r-cran-v8_3.1.0+dfsg-2.dsc
 d50cb04cc58369b1acc57178c53b0a6b 3836 gnu-r optional 
r-cran-v8_3.1.0+dfsg-2.debian.tar.xz
 f81151508334068f518adf50aebb07d7 9371 gnu-r optional 
r-cran-v8_3.1.0+dfsg-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEA8Tnq7iA9SQwbkgVZhHAXt0583QFAl7miucSHGthcG91ZXJA
bWVsaXgub3JnAAoJEGYRwF7dOfN04Q8QAJ67jxhIJIccdabPi6j5IjXjeujVx2jZ
K5u3k/9fs7O+KJHD0JkBLlQgCM1xqvz9LtXuIDtQ1ypIdtdgQZSHr6Z2T+eOB+KM
yGz2hxjn4lZcAwXbRIM8rjutufzw9FMs5RVb485PG0VfN0SvKAZas85+T7jb6w1M
IgJnsCZCKbMw5P0MvLMQX5jOCmm2S2BY+/f8k4zAiNhtsb7utrTMeJxVQVxIa2qJ
qcbDEKRP8T1z/+mXpi6gHMXFQ+9uF1fg+tfAHQ+BKQY18t9sNYlbfhvT1iuMAOKY
Ery5U+c5mgrG4s/S6muFWyMn5dtgtLrwS3+D4rxXo4pS8ymzyNHUz4A9QtQPuvZr
zGTFTCP3LLZ+UmHwJ04NvWQywORDDa2MKi+Y0mpkPPMp/Cfg3zHgN0OxAYeshymx
TS/F2cDYvaSGQbyDTE3C3lkQXZRaHpwqnD432Zwghrc/ld5vD+yAJUyQdNOaA6g2
GR+76f2FFxCMG7vTDrlAxYVj8sN7XxPjM4+DwaavScoc/Dp/sQIwx8IeO0B1+mMo
4ftQKLN5pvKGfo4ABGX86GFCYSwB8mZXH14aUc7tMedvTbAaOabkTuqjz+kdw5Si

Bug#962518: marked as done (cegui-mk2 FTBFS on mipsel/mips64el: symbol differences)

[Debian Bug Tracking System]

Your message dated Sun, 14 Jun 2020 20:48:30 +
with message-id 
and subject line Bug#962518: fixed in cegui-mk2 0.8.7-9
has caused the Debian Bug report #962518,
regarding cegui-mk2 FTBFS on mipsel/mips64el: symbol differences
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.)


-- 
962518: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962518
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cegui-mk2
Version: 0.8.7-8
Severity: serious
Tags: ftbfs patch
Control: block 961995 by -1

https://buildd.debian.org/status/package.php?p=cegui-mk2

...
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libcegui-mk2-0.8.7/DEBIAN/symbols doesn't 
match completely debian/libcegui-mk2-0.8.7.symbols
...
+#MISSING: 0.8.7-8# (arch=!amd64 !arm64 !armel !armhf !i386 !ppc64el !riscv64 
!s390x)_ZN5boost6system14error_category12std_categoryD0Ev@Base 0.8.7
+#MISSING: 0.8.7-8# (arch=!amd64 !arm64 !armel !armhf !i386 !ppc64el !riscv64 
!s390x)_ZN5boost6system14error_category12std_categoryD1Ev@Base 0.8.7
+#MISSING: 0.8.7-8# (arch=!amd64 !arm64 !armel !armhf !i386 !ppc64el !riscv64 
!s390x)_ZN5boost6system14error_category12std_categoryD2Ev@Base 0.8.7
...
+#MISSING: 0.8.7-8# (arch=!amd64 !arm64 !armel !armhf !i386 !ppc64el !riscv64 
!s390x)_ZNK5boost6system14error_category12std_category10equivalentERKSt10error_codei@Base
 0.8.7
+#MISSING: 0.8.7-8# (arch=!amd64 !arm64 !armel !armhf !i386 !ppc64el !riscv64 
!s390x)_ZNK5boost6system14error_category12std_category10equivalentEiRKSt15error_condition@Base
 0.8.7
+#MISSING: 0.8.7-8# (arch=!amd64 !arm64 !armel !armhf !i386 !ppc64el !riscv64 
!s390x)_ZNK5boost6system14error_category12std_category23default_error_conditionEi@Base
 0.8.7
+#MISSING: 0.8.7-8# (arch=!amd64 !arm64 !armel !armhf !i386 !ppc64el !riscv64 
!s390x)_ZNK5boost6system14error_category12std_category4nameEv@Base 0.8.7
+#MISSING: 0.8.7-8# (arch=!amd64 !arm64 !armel !armhf !i386 !ppc64el !riscv64 
!s390x)_ZNK5boost6system14error_category12std_category7messageB5cxx11Ei@Base 
0.8.7
...
+#MISSING: 0.8.7-8# (arch=!amd64 !arm64 !armel !armhf !i386 !ppc64el !riscv64 
!s390x)_ZTIN5boost6system14error_category12std_categoryE@Base 0.8.7
...
+#MISSING: 0.8.7-8# (arch=!amd64 !arm64 !armel !armhf !i386 !ppc64el !riscv64 
!s390x)_ZTSN5boost6system14error_category12std_categoryE@Base 0.8.7
...
+#MISSING: 0.8.7-8# (arch=!amd64 !arm64 !armel !armhf !i386 !ppc64el !riscv64 
!s390x)_ZTVN5boost6system14error_category12std_categoryE@Base 0.8.7
...
dh_makeshlibs: error: failing due to earlier errors
make: *** [debian/rules:10: binary-arch] Error 25


Fix:

--- debian/libcegui-mk2-0.8.7.symbols.old   2020-06-08 20:45:48.993830179 
+
+++ debian/libcegui-mk2-0.8.7.symbols   2020-06-08 20:46:55.314908115 +
@@ -13054,9 +13054,6 @@
  (arch=!armel !armhf)_ZN5boost6system12system_errorD0Ev@Base 0.8.7
  (arch=!armel !armhf)_ZN5boost6system12system_errorD1Ev@Base 0.8.7
  (arch=!armel !armhf)_ZN5boost6system12system_errorD2Ev@Base 0.8.7
- (arch=!amd64 !arm64 !armel !armhf !i386 !ppc64el !riscv64 
!s390x)_ZN5boost6system14error_category12std_categoryD0Ev@Base 0.8.7
- (arch=!amd64 !arm64 !armel !armhf !i386 !ppc64el !riscv64 
!s390x)_ZN5boost6system14error_category12std_categoryD1Ev@Base 0.8.7
- (arch=!amd64 !arm64 !armel !armhf !i386 !ppc64el !riscv64 
!s390x)_ZN5boost6system14error_category12std_categoryD2Ev@Base 0.8.7
  (arch=!armel !armhf !mips64el 
!mipsel)_ZN5boost6system6detail12std_categoryD0Ev@Base 0.8.7
  (arch=!armel !armhf !mips64el 
!mipsel)_ZN5boost6system6detail12std_categoryD1Ev@Base 0.8.7
  (arch=!armel !armhf !mips64el 
!mipsel)_ZN5boost6system6detail12std_categoryD2Ev@Base 0.8.7
@@ -13116,11 +13113,6 @@
  (arch=!armel !armhf)_ZNK5boost6system12system_error4whatEv@Base 0.8.7
  (arch=!armel 
!armhf)_ZNK5boost6system14error_category10equivalentERKNS0_10error_codeEi@Base 
0.8.7
  (arch=!armel 
!armhf)_ZNK5boost6system14error_category10equivalentEiRKNS0_15error_conditionE@Base
 0.8.7
- (arch=!amd64 !arm64 !armel !armhf !i386 !ppc64el !riscv64 
!s390x)_ZNK5boost6system14error_category12std_category10equivalentERKSt10error_codei@Base
 0.8.7
- (arch=!amd64 !arm64 !armel !armhf !i386 !ppc64el !riscv64 
!s390x)_ZNK5boost6system14error_category12std_category10equivalentEiRKSt15error_condition@Base
 0.8.7
- (arch=!amd64 !arm64 !armel !armhf !i386 !ppc64el !riscv64 

Bug#962832: openms-doc: missing Breaks+Replaces: openms (<< 2.5)

[Andreas Beckmann]

Package: openms-doc
Version: 2.5.0+cleaned1-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

This test intentionally skipped 'testing' to find file overwrite
problems before packages migrate from 'unstable' to 'testing'.

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

  Preparing to unpack .../openms-doc_2.5.0+cleaned1-3_all.deb ...
  Unpacking openms-doc (2.5.0+cleaned1-3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/openms-doc_2.5.0+cleaned1-3_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/openms/AUTHORS', which is also in 
package openms 2.4.0-real-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/openms-doc_2.5.0+cleaned1-3_all.deb


cheers,

Andreas


openms=2.4.0-real-1_openms-doc=2.5.0+cleaned1-3.log.gz
Description: application/gzip

Bug#962831: libmumps-headers-dev: missing Breaks+Replaces: libmumps-seq-dev (<= 5.3.1-2)

[Andreas Beckmann]

Package: libmumps-headers-dev
Version: 5.3.1-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Preparing to unpack .../libmumps-headers-dev_5.3.1-3_all.deb ...
  Unpacking libmumps-headers-dev (5.3.1-3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libmumps-headers-dev_5.3.1-3_all.deb (--unpack):
   trying to overwrite '/usr/include/mumps_seq/elapse.h', which is also in 
package libmumps-seq-dev:amd64 5.3.1-2
  Errors were encountered while processing:
   /var/cache/apt/archives/libmumps-headers-dev_5.3.1-3_all.deb

cheers,

Andreas


libmumps-seq-dev=5.3.1-2_libmumps-headers-dev=5.3.1-3.log.gz
Description: application/gzip

Bug#817954: Does this bug prevent firefox from entering backports also?

[Mike Hommey]

On Sun, Jun 14, 2020 at 08:25:10PM +0530, Pirate Praveen wrote:
> 
> 
> On Sun, Jun 14, 2020 at 7:31 am, Mike Hommey  wrote:
> > On Thu, Jun 11, 2020 at 03:22:40PM +0530, Pirate Praveen wrote:
> > >  On Thu, 25 Jul 2019 12:10:45 +0200 Johannes Rohr 
> > > wrote:
> > >  > It would be great to have firefox (or the next firefox-esr) in
> > >  > buster-backports, as it has important new functionality relevant
> > > for
> > >  > privacy and data protection, such as the multi account containers
> > >  > function. However, this bug prevents firefox from entering
> > > testing,
> > >  > which in my understanding implies, that it cannot make it into
> > > backports
> > >  > as well. Is there some way of getting an up-to-date firefox
> > > version into
> > >  > stable? For now I work with the binary directly downloaded from
> > >  > mozilla.org, but this is a kludge.
> > >  >
> > > 
> > >  We have created https://fasttrack.debian.net for packages like this
> > >  which cannot go with stable releases and hence blocked from entering
> > >  testing and backports as well.
> > > 
> > >  Mike,
> > > 
> > >  Would you like to maintain firefox in buster-fasttrack?
> > > 
> > >  I'm part of the team that maintain this unofficial service and
> > > maintains
> > >  gitlab there. If you are okay with the idea, but does not want to
> > > do the
> > >  extra work, I'd be happy to maintain it in fasttrack.
> > 
> > The package in unstable can be built for stable as long as its version
> > contains a ~bpo thing. That could be changed to also support fto. But
> > the bigger problem is that it requires new versions of rustc, cargo and
> > cbindgen, which in turn requires a new version of llvm. And it requires
> > new versions of these quite regularly.
> > 
> > So, no, I'm not really interested in maintaining that.
> > 
> 
> Thanks for the reply. I will ask around if more people are willing to take
> on the challenge and will try it if there is an interest. Things like webRTC
> suport (jitsi video conferencing) needs recent versions of firefox to work
> well and which is my main interest to take on this.

Stable is going to be updated to 78 in a few weeks.

Mike

Bug#956694: marked as done (spdlog refers to header files that it does not ship)

[Debian Bug Tracking System]

Your message dated Sun, 14 Jun 2020 19:48:54 +
with message-id 
and subject line Bug#956694: fixed in spdlog 1:1.5.0+ds-4
has caused the Debian Bug report #956694,
regarding spdlog refers to header files that it does not ship
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.)


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

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

...
cd /build/1st/sopt-3.0.1/obj-x86_64-linux-gnu/cpp/sopt && /usr/bin/c++  
-Dsopt_EXPORTS -I/build/1st/sopt-3.0.1/cpp/sopt/.. 
-I/build/1st/sopt-3.0.1/obj-x86_64-linux-gnu/include -isystem 
/usr/include/eigen3 -isystem /usr/lib/x86_64-linux-gnu/openmpi/include/openmpi 
-isystem /usr/lib/x86_64-linux-gnu/openmpi/include  -g -O2 
-ffile-prefix-map=/build/1st/sopt-3.0.1=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -std=gnu++11 -fPIC   
-fopenmp -o CMakeFiles/sopt.dir/wavelets/sara.cc.o -c 
/build/1st/sopt-3.0.1/cpp/sopt/wavelets/sara.cc
In file included from 
/build/1st/sopt-3.0.1/cpp/tests/../sopt/logging.enabled.h:5,
 from /build/1st/sopt-3.0.1/cpp/tests/../sopt/logging.h:7,
 from /build/1st/sopt-3.0.1/cpp/tests/common_catch_main.cc:7:
/usr/include/spdlog/fmt/ostr.h:17:10: fatal error: 
spdlog/fmt/bundled/ostream.h: No such file or directory
   17 | #include 
  |  ^~
compilation terminated.
--- End Message ---
--- Begin Message ---
Source: spdlog
Source-Version: 1:1.5.0+ds-4
Done: Nilesh Patra 

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

Debian distribution maintenance software
pp.
Nilesh Patra  (supplier of updated spdlog package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 14 Jun 2020 20:46:53 +0200
Source: spdlog
Architecture: source
Version: 1:1.5.0+ds-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Nilesh Patra 
Closes: 956694
Changes:
 spdlog (1:1.5.0+ds-4) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Michael R. Crusoe ]
   * Update Michael's email address
 .
   [ Nilesh Patra ]
   * Use system libfmt by default
 Closes: #956694
 .
   [ Andreas Tille ]
   * Add salsa-ci.yml
Checksums-Sha1:
 3450d507fe59aadc177f6cdd9b9ebc21364f172d 2135 spdlog_1.5.0+ds-4.dsc
 6d2ee37446f1b1cc21f1327ac872e5cbb8c5c94f 15780 spdlog_1.5.0+ds-4.debian.tar.xz
 00b22a2481a0fa86d852a402a9d4b58804557d2b 15020 
spdlog_1.5.0+ds-4_source.buildinfo
Checksums-Sha256:
 2ea5ddf183a00c936523fb08cc51d50cd4434acdc07afaaa3caa0574bcf65796 2135 
spdlog_1.5.0+ds-4.dsc
 3785b4b7233cbe684ce4de85f7d8f2f5c31fe96b024486d23ab3726b8a3a7e38 15780 
spdlog_1.5.0+ds-4.debian.tar.xz
 d0073180df5e19f85441ff5df114a52efdfd9c44fe7efc0e96774bee87716516 15020 
spdlog_1.5.0+ds-4_source.buildinfo
Files:
 462a7dca6ff5e07e6282b20825ac2b97 2135 libdevel optional spdlog_1.5.0+ds-4.dsc
 16a25d5708aba45250a67fae4fb09442 15780 libdevel optional 
spdlog_1.5.0+ds-4.debian.tar.xz
 7e283a5b9ec75531fdcae77e976ab991 15020 libdevel optional 
spdlog_1.5.0+ds-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJCBAEBCAAsFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl7meZ4OHHRpbGxlYUBy
a2kuZGUACgkQV4oElNHGRtEQUw/+LEQ+Bppg7xJMvUpWtgsIR+IeXxJnE77vyNXF
uj0mFGDS2MUgO8GgXxUACLG/pNEMnzi0LtR1hm3Wo5lJvmKoLdWZD0GPHq28UbLC
C+0AOD8ij7oSBWc+UuCdGYVChuejojchA64gSBsNRDQekbhWb/uZXqeqiFd/HZy8
b/5hv4v+BFN+CQQtXTKsrTvC8+K3JgvV5W97ukwu1nPL0o8M5QNSjrYIdCFDQ824
2n3k2Hpc841Ac6YacC/5DCnkTd3EXvwZjEBPBwZ4qzVKvjcOuv0U1+y0NFrEYKw8
0TiImYYf6YoQSjbm8oJo9p09EVAQ0CTr96FGMeP78+d2ZNOPDpRRlU3u1GKByq0E
CdcgKg1t28COm7Xd+K/8zXY7iHBi6OB3UxOxsAtRY6x1teFVc724nBoZWKa+ncEv
qYzlDq5uvn0d8zSsiJQiaTtmh7fcNX0mRbLNn9cY/g36PNcOwIW6O/4zA1JtcCxg
IaCz8AtP/9JrLiGvhxvEetuuiDc6lA+4WZRKTMrBOKl3YXj868OfaFVQXfcx3nap
aK+B74lKeddGyAMJEElJ873khZq2Dxlj27ftpiedyZX40MHrz1HqmDS6/l/7UKEU

Bug#962804: marked as done (wfmath: autopkgtest failure: no acceptable C compiler found in $PATH)

[Debian Bug Tracking System]

Your message dated Sun, 14 Jun 2020 19:34:28 +
with message-id 
and subject line Bug#962804: fixed in wfmath 1.0.2+dfsg1-9
has caused the Debian Bug report #962804,
regarding wfmath: autopkgtest failure: no acceptable C compiler found in $PATH
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.)


-- 
962804: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962804
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wfmath
Version: 1.0.2+dfsg1-8
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 wfmath, great.
However, it fails. 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. Are you
missing a test dependency?

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

https://ci.debian.net/data/autopkgtest/testing/amd64/w/wfmath/5792572/log.gz

autopkgtest [10:33:44]: test command1: ./configure && make check
autopkgtest [10:33:44]: test command1: [---
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether make supports nested variables... (cached) yes
checking how to print strings... printf
checking for style of include used by make... GNU
checking for gcc... no
checking for cc... no
checking for cl.exe... no
configure: error: in `/tmp/autopkgtest-lxc.nwce0fke/downtmp/build.tAZ/src':
configure: error: no acceptable C compiler found in $PATH
See `config.log' for more details
autopkgtest [10:33:46]: test command1: ---]



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: wfmath
Source-Version: 1.0.2+dfsg1-9
Done: Olek Wojnar 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 14 Jun 2020 15:03:07 -0400
Source: wfmath
Architecture: source
Version: 1.0.2+dfsg1-9
Distribution: unstable
Urgency: high
Maintainer: Debian Games Team 
Changed-By: Olek Wojnar 
Closes: 962804
Changes:
 wfmath (1.0.2+dfsg1-9) unstable; urgency=high
 .
   * Declare correct autopkgtest depends (Closes: #962804)
Checksums-Sha1:
 ba1cb68bb843204650cbb9576d03cfcdd04d7980 2221 wfmath_1.0.2+dfsg1-9.dsc
 06515e24d11a61957090c0755c805567921782b3 15348 
wfmath_1.0.2+dfsg1-9.debian.tar.xz
 b8ed2a0c3a8c093893231ba95eda3a78ae99abd0 6876 
wfmath_1.0.2+dfsg1-9_amd64.buildinfo
Checksums-Sha256:
 31292da06683c12bc99fdb642b5fb4c6af67fea9a9a34aff05014194f41f4098 2221 
wfmath_1.0.2+dfsg1-9.dsc
 43797ce07cd291a2630f98e26b83721cb490cad5c6e50bb5bc2bd2e83ed71c5f 15348 
wfmath_1.0.2+dfsg1-9.debian.tar.xz
 8d1d84f5bd170549d2ac0b5682351402c86aa905d6b105910a3b3395ed14992d 6876 
wfmath_1.0.2+dfsg1-9_amd64.buildinfo
Files:
 81ea289f94a62dbc7113d13e70529369 2221 libs optional wfmath_1.0.2+dfsg1-9.dsc
 975055b9231724a900f72ca7b3eaf389 15348 libs optional 
wfmath_1.0.2+dfsg1-9.debian.tar.xz
 1541c17967cd1933126f18502c8aea80 6876 libs optional 
wfmath_1.0.2+dfsg1-9_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEELejiDiSiH9jtG0ynfYPUBqCdweQFAl7mdzEACgkQfYPUBqCd
weR1RQ/8CwPhZIfksC+HMVC3NuEB+O1pwxPSxkBXKOGzzQjAqwCMBb41wdNbMXyK
r+aw7FDL83LB33vI+NnJkES68pEnN69aPSUnyUWm73516lnNelfI71JQ8FJfFaH7

Processed: libphp-phpmailer: CVE-2020-13625

[Debian Bug Tracking System]

Processing control commands:

> found -1 6.0.6-0.1
Bug #962827 [src:libphp-phpmailer] libphp-phpmailer: CVE-2020-13625
Marked as found in versions libphp-phpmailer/6.0.6-0.1.
> found -1 5.2.14+dfsg-2.3+deb9u1
Bug #962827 [src:libphp-phpmailer] libphp-phpmailer: CVE-2020-13625
Marked as found in versions libphp-phpmailer/5.2.14+dfsg-2.3+deb9u1.
> found -1 5.2.14+dfsg-2.3
Bug #962827 [src:libphp-phpmailer] libphp-phpmailer: CVE-2020-13625
Marked as found in versions libphp-phpmailer/5.2.14+dfsg-2.3.

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

Bug#962827: libphp-phpmailer: CVE-2020-13625

[Salvatore Bonaccorso]

Source: libphp-phpmailer
Version: 6.1.5-0.1
Severity: grave
Tags: security upstream
Control: found -1 6.0.6-0.1
Control: found -1 5.2.14+dfsg-2.3+deb9u1
Control: found -1 5.2.14+dfsg-2.3

Hi,

The following vulnerability was published for libphp-phpmailer.

Filling as RC severity as currently as libphp-phpmailer seems
currently without maintainer. Bullseye should ideally be released with
an active maintainer for libphp-phpmailer.

CVE-2020-13625[0]:
| PHPMailer before 6.1.6 contains an output escaping bug when the name
| of a file attachment contains a double quote character. This can
| result in the file type being misinterpreted by the receiver or any
| mail relay processing the message.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2020-13625
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-13625
[1] 
https://github.com/PHPMailer/PHPMailer/security/advisories/GHSA-f7hx-fqxw-rvvj
[2] 
https://github.com/PHPMailer/PHPMailer/commit/c2796cb1cb99d7717290b48c4e6f32cb6c60b7b3

Regards,
Salvatore

Bug#962825: node-opencv: FTBFS against nodejs 12.18 - fixed in upstream version 7.0.0

[Jérémy Lal]

Package: node-opencv
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi
this package fails to build against node 12.18,
and upstream has already version 7.0.0 fixing the issue.

However, upstream forgot to push git tags:
https://github.com/peterbraden/node-opencv/issues/652#issuecomment-643807293

Jérémy

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

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

Versions of packages node-opencv depends on:
ii  libc6   2.30-8
ii  libgcc-s1   10.1.0-3
ii  libnode64   10.21.0~dfsg-1
pn  libopencv-calib3d4.2
pn  libopencv-contrib4.2
pn  libopencv-core4.2   
pn  libopencv-highgui4.2
pn  libopencv-imgcodecs4.2  
pn  libopencv-imgproc4.2
pn  libopencv-objdetect4.2  
pn  libopencv-video4.2  
pn  libopencv-videoio4.2
ii  libstdc++6  10.1.0-3
pn  node-buffers
pn  node-istanbul   
ii  node-nan2.14.0-1
ii  node-pre-gyp0.10.2-3
hi  nodejs  10.21.0~dfsg-1

node-opencv recommends no packages.

node-opencv suggests no packages.

Bug#962804: wfmath: autopkgtest failure: no acceptable C compiler found in $PATH

[Olek Wojnar]

Ah, ok. Good to know and that makes sense. Thanks to you both. I'm still a
bit new to this autopkgtest thing but it seems worthwhile to get it figured
out. I'll add build-essential explicitly since none of the other build
dependencies should be necessary to compile the test.

-Olek

Bug#962824: r-cran-v8: FTBFS against nodejs 12.18.0

[Jérémy Lal]

Package: r-cran-v8
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi,

this package cannot be built against nodejs 12.18.0.
this blocks nodejs migration to testing.

I pinged upstream about that:
https://github.com/jeroen/V8/pull/87

Cheers,
Jérémy

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

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

Versions of packages r-cran-v8 depends on:
ii  libc6 2.30-8
ii  libgcc-s1 10.1.0-3
ii  libjs-underscore  1.9.1~dfsg-1
ii  libnode64 10.21.0~dfsg-1
ii  libstdc++610.1.0-3
pn  r-api-4.0 
pn  r-base-core   
pn  r-cran-curl   
pn  r-cran-jsonlite   
pn  r-cran-rcpp   

Versions of packages r-cran-v8 recommends:
pn  r-cran-testthat  

Versions of packages r-cran-v8 suggests:
pn  r-cran-knitr  
pn  r-cran-rmarkdown  

Bug#962518: cegui-mk2 FTBFS on mipsel/mips64el: symbol differences

[Olek Wojnar]

Thanks to all of you for taking a look at this and for your insights and
advice!I think I've definitely learned a couple things about how to
do symbols better in the future.

In the near term, I'm going to take the advice to just get rid of the
symbols file. I've been so busy with Bazel [1] recently that I just don't
have the time to work through this right now. But I'm keeping this email
flagged for follow-up because I would definitely like to implement a
visibility patch in the future. It looks like it will make the symbols file
MUCH more manageable! Thanks again!

-Olek

[1] https://salsa.debian.org/bazel-team/meta/-/wikis/Workplan-Part-1

Bug#962804: wfmath: autopkgtest failure: no acceptable C compiler found in $PATH

[Simon McVittie]

On Sun, 14 Jun 2020 at 14:15:02 -0400, Olek Wojnar wrote:
> Hmm, is build-essential not automatically installed in the CI environment? 
> That
> seems to be the most likely reason for this failure. I assumed that all
> packages (e.g. build-essential) that we assume to be present for packaging
> would be present here as well. Is that not the case?

No, as with ordinary packaging you can only rely on having the
Essential:yes set, plus their hard dependencies, plus the hard
dependencies you declare (recursively). (In practice testbeds will
usually have a few extra packages, such as an init system, but don't
rely on those.)

Some tests compile what they need from scratch, but some don't. In
particular, this means maintainers are able to verify with reasonable
confidence that a package's dependencies are sufficient to make it work.

smcv

Bug#962804: wfmath: autopkgtest failure: no acceptable C compiler found in $PATH

[Paul Gevers]

Hi Olek,

On 14/06/2020 20.15, Olek Wojnar wrote:
> checking for gcc... no
> checking for cc... no
> checking for cl.exe... no
> configure: error: in
> `/tmp/autopkgtest-lxc.nwce0fke/downtmp/build.tAZ/src':
> configure: error: no acceptable C compiler found in $PATH
> 
> 
> Hmm, is build-essential not automatically installed in the CI
> environment? That seems to be the most likely reason for this failure. I
> assumed that all packages (e.g. build-essential) that we assume to be
> present for packaging would be present here as well. Is that not the
> case? If so, this will likely be a very easy fix.

No, as per specification, you need @builddeps@ for that:
https://salsa.debian.org/ci-team/autopkgtest/-/blob/master/doc/README.package-tests.rst


Paul



signature.asc
Description: OpenPGP digital signature

Processed: lv2dynparam1: diff for NMU version 2-6.1

[Debian Bug Tracking System]

Processing control commands:

> tags 946068 + patch
Bug #946068 [src:lv2dynparam1] lv2dynparam1 FTCBFS: lv2core.pc not found
Added tag(s) patch.
> tags 946068 + pending
Bug #946068 [src:lv2dynparam1] lv2dynparam1 FTCBFS: lv2core.pc not found
Added tag(s) pending.

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

Bug#946068: lv2dynparam1: diff for NMU version 2-6.1

[Sudip Mukherjee]

Control: tags 946068 + patch
Control: tags 946068 + pending

Dear maintainer,

I've prepared an NMU for lv2dynparam1 (versioned as 2-6.1) and
uploaded it to mentors for sponsoring. Please feel free to tell me if I
should remove it.

--
Regards
Sudip

diff -Nru lv2dynparam1-2/debian/changelog lv2dynparam1-2/debian/changelog
--- lv2dynparam1-2/debian/changelog 2016-11-07 22:56:45.0 +
+++ lv2dynparam1-2/debian/changelog 2020-06-14 18:57:30.0 +0100
@@ -1,3 +1,10 @@
+lv2dynparam1 (2-6.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS. (Closes: #946068)
+
+ -- Sudip Mukherjee   Sun, 14 Jun 2020 18:57:30 
+0100
+
 lv2dynparam1 (2-6) unstable; urgency=medium
 
   * Remove DMUA.
diff -Nru lv2dynparam1-2/debian/patches/fix_ftbfs.patch 
lv2dynparam1-2/debian/patches/fix_ftbfs.patch
--- lv2dynparam1-2/debian/patches/fix_ftbfs.patch   1970-01-01 
01:00:00.0 +0100
+++ lv2dynparam1-2/debian/patches/fix_ftbfs.patch   2020-06-14 
18:48:57.0 +0100
@@ -0,0 +1,20 @@
+Description: Use lv2.pc
+ The dependency was changed to lv2-dev previously but lv2-dev provides lv2.pc,
+ not lv2core.pc.
+
+Author: Sudip Mukherjee 
+Bug-Debian: https://bugs.debian.org/946068
+
+---
+
+--- lv2dynparam1-2.orig/configure.ac
 lv2dynparam1-2/configure.ac
+@@ -32,7 +32,7 @@ AC_PROG_LIBTOOL
+ #AC_HEADER_STDC
+ #AC_CHECK_HEADERS([stddef.h stdint.h stdlib.h string.h])
+ 
+-PKG_CHECK_MODULES(LV2, lv2core >= 1)
++PKG_CHECK_MODULES(LV2, lv2 >= 1)
+ 
+ # Checks for typedefs, structures, and compiler characteristics.
+ #AC_C_CONST
diff -Nru lv2dynparam1-2/debian/patches/series 
lv2dynparam1-2/debian/patches/series
--- lv2dynparam1-2/debian/patches/series2013-10-30 20:45:07.0 
+
+++ lv2dynparam1-2/debian/patches/series2020-06-14 18:43:17.0 
+0100
@@ -1 +1,2 @@
 0001-buildsystem.patch
+fix_ftbfs.patch

Bug#962804: wfmath: autopkgtest failure: no acceptable C compiler found in $PATH

[Olek Wojnar]

Hi Paul,

Thanks for the bug report. I'd noticed the error on DDPO but hadn't had
time to investigate.

On Sun, Jun 14, 2020 at 7:18 AM Paul Gevers  wrote:

> I copied some of the output at the bottom of this report. Are you
> missing a test dependency?
>




> checking for gcc... no
> checking for cc... no
> checking for cl.exe... no
> configure: error: in `/tmp/autopkgtest-lxc.nwce0fke/downtmp/build.tAZ/src':
> configure: error: no acceptable C compiler found in $PATH


Hmm, is build-essential not automatically installed in the CI environment?
That seems to be the most likely reason for this failure. I assumed that
all packages (e.g. build-essential) that we assume to be present for
packaging would be present here as well. Is that not the case? If so, this
will likely be a very easy fix.

-Olek

Processed: php-imagick: diff for NMU version 3.4.4-4.1

[Debian Bug Tracking System]

Processing control commands:

> tags 959386 + patch
Bug #959386 {Done: Paul Gevers } [src:php-imagick] 
src:php-imagick: fails to migrate to testing for too long: FTBFS on armel
Added tag(s) patch.
> tags 959386 + pending
Bug #959386 {Done: Paul Gevers } [src:php-imagick] 
src:php-imagick: fails to migrate to testing for too long: FTBFS on armel
Added tag(s) pending.

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

Bug#959386: php-imagick: diff for NMU version 3.4.4-4.1

[Adrian Bunk]

Control: tags 959386 + patch
Control: tags 959386 + pending

Dear maintainer,

I've prepared an NMU for php-imagick (versioned as 3.4.4-4.1) and 
uploaded it to DELAYED/15. Please feel free to tell me if I should 
cancel it.

cu
Adrian
diff -Nru php-imagick-3.4.4/debian/changelog php-imagick-3.4.4/debian/changelog
--- php-imagick-3.4.4/debian/changelog	2020-03-02 11:04:48.0 +0200
+++ php-imagick-3.4.4/debian/changelog	2020-06-14 12:26:18.0 +0300
@@ -1,3 +1,10 @@
+php-imagick (3.4.4-4.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Skip tests that fail with PHP 7.4 on armel. (Closes: #959386)
+
+ -- Adrian Bunk   Sun, 14 Jun 2020 12:26:18 +0300
+
 php-imagick (3.4.4-4) unstable; urgency=medium
 
   [ Ondřej Surý ]
diff -Nru php-imagick-3.4.4/debian/patches/armel.patch php-imagick-3.4.4/debian/patches/armel.patch
--- php-imagick-3.4.4/debian/patches/armel.patch	1970-01-01 02:00:00.0 +0200
+++ php-imagick-3.4.4/debian/patches/armel.patch	2020-06-14 12:26:18.0 +0300
@@ -0,0 +1,44 @@
+Description: Skip tests that fail with PHP 7.4 on armel
+Author: Adrian Bunk 
+Bug-Debian: https://bugs.debian.org/959386
+
+--- php-imagick-3.4.4.orig/imagick-3.4.4/tests/064_cropThumbNailImage.phpt
 php-imagick-3.4.4/imagick-3.4.4/tests/064_cropThumbNailImage.phpt
+@@ -2,6 +2,7 @@
+ Test for round issues
+ --SKIPIF--
+ 
+--- php-imagick-3.4.4.orig/imagick-3.4.4/tests/072_Imagick_evaluateImage_basic.phpt
 php-imagick-3.4.4/imagick-3.4.4/tests/072_Imagick_evaluateImage_basic.phpt
+@@ -2,6 +2,7 @@
+ Test Imagick, evaluateImage
+ --SKIPIF--
+ 
diff -Nru php-imagick-3.4.4/debian/patches/series php-imagick-3.4.4/debian/patches/series
--- php-imagick-3.4.4/debian/patches/series	2020-03-02 11:04:48.0 +0200
+++ php-imagick-3.4.4/debian/patches/series	2020-06-14 12:23:59.0 +0300
@@ -3,3 +3,4 @@
 no-openmp-threads.patch
 0003-Disable-test-014-which-fails-due-to-system-resources.patch
 0004-Disable-remaining-tests-failing-with-7.4.patch
+armel.patch

Bug#962805: marked as done (python-geotiepoints: autopkgtest regression: No module named 'h5py)

[Debian Bug Tracking System]

Your message dated Sun, 14 Jun 2020 16:34:43 +
with message-id 
and subject line Bug#962805: fixed in python-geotiepoints 1.2.0-2
has caused the Debian Bug report #962805,
regarding python-geotiepoints: autopkgtest regression: No module named 'h5py
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.)


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

Dear maintainer(s),

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

   passfail
python-geotiepointsfrom testing1.2.0-1
all others from testingfrom testing

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

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it? It seems like you're
missing a (test) dependency.

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-geotiepoints/5889557/log.gz

autopkgtest [19:08:51]: test python3: [---
=== python3.8 ===
tests (unittest.loader._FailedTest) ... ERROR

==
ERROR: tests (unittest.loader._FailedTest)
--
ImportError: Failed to import test module: tests
Traceback (most recent call last):
  File "/usr/lib/python3.8/unittest/loader.py", line 154, in
loadTestsFromName
module = __import__(module_name)
  File "/usr/lib/python3/dist-packages/geotiepoints/tests/__init__.py",
line 27, in 
from geotiepoints.tests import (test_geointerpolator,
  File
"/usr/lib/python3/dist-packages/geotiepoints/tests/test_modis.py", line
7, in 
import h5py
ModuleNotFoundError: No module named 'h5py'


--
Ran 1 test in 0.000s

FAILED (errors=1)
autopkgtest [19:08:51]: test python3: ---]



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: python-geotiepoints
Source-Version: 1.2.0-2
Done: Antonio Valentino 

We believe that the bug you reported is fixed in the latest version of
python-geotiepoints, 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.
Antonio Valentino  (supplier of updated 
python-geotiepoints package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 14 Jun 2020 15:30:49 +
Source: python-geotiepoints
Architecture: source
Version: 1.2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project 
Changed-By: Antonio Valentino 
Closes: 962805
Changes:
 python-geotiepoints (1.2.0-2) unstable; urgency=medium
 .
   * Add missing dependencies to debian/tests/control (Closes: 962805).
Checksums-Sha1:
 b8017613c9c09e5476fdc189e398d1bdb0922307 2269 python-geotiepoints_1.2.0-2.dsc
 3d7d30ac90fc1c6067f33264e581680782384d69 4844 
python-geotiepoints_1.2.0-2.debian.tar.xz
 9cc4a532a2c4bbd4fcf1ade9e9adcbeeb5e7f435 8095 
python-geotiepoints_1.2.0-2_amd64.buildinfo
Checksums-Sha256:
 f4de2e9a1c839d615e0c9182d10b667d3df609d92966d005e95c79673335fcda 2269 
python-geotiepoints_1.2.0-2.dsc
 cccb1a0c03be1c4155c73284c31526484f6dbc43a297b101f901324195e29960 4844 
python-geotiepoints_1.2.0-2.debian.tar.xz
 59ba97ca0dbb20e26e3b2d611db778123b892a5c56f093f8356c85159611be52 8095 
python-geotiepoints_1.2.0-2_amd64.buildinfo
Files:
 c009ffa02040b66b3e0324e5cbfb6a55 2269 python optional 

Bug#962784: [Pkg-puppet-devel] Bug#962784: facter aborts with free(): invalid pointer

[Russ Allbery]

Stig Sandbeck Mathisen  writes:

> Looks like the same bug as http://bugs.debian.org/962692 and related to
> https://bugs.debian.org/962320

Ah, indeed, thank you!  Somehow I missed those.  #962320 seems like it
should be assigned to facter and merged with this bug; I don't think it's
Boost's fault that a binary links with two versions of the same shared
library (unless the contention is that symbol versioning should make this
safe, which can be quite challenging for C++ libraries).

> A quick workaround to get facter to run is to create the three
> directories:

> /etc/facter/facts.d
> /etc/puppetlabs/facter/facts.d
> /opt/puppetlabs/facter/facts.d

Yup, confirmed that works.  Thank you!

-- 
Russ Allbery (r...@debian.org)  

Bug#956694: Clarification: [RFS] spdlog

[Nilesh Patra]

> For sopt, the build fails with the logs same as what Ole sharedearlier - but 
> looking at them, it seems that spdlog is probably not responsible for the 
> failure.


By same logs, I do not mean the one in the original bug report, but the
logs which Ole got after workaround: #953855

cd /build/sopt-3.0.1/obj-x86_64-linux-gnu/cpp/tests && /usr/bin/cmake -E
cmake_link_script CMakeFiles/test_padmm.dir/link.txt --verbose=1
/usr/lib/ccache/c++  -g -O2 -fdebug-prefix-map=/build/sopt-3.0.1=.
-fstack-protector-strong -Wformat -Werror=format-security
-DSPDLOG_FMT_EXTERNAL -Wdate-time -D_FORTIFY_SOURCE=2  -std=gnu++11
-Wl,-z,relro >
/usr/bin/ld: CMakeFiles/copy_tiff.dir/copy_tiff.cc.o: in function
`fmt::v6::basic_format_context
>, char>::on_error(char const*)':
/usr/include/fmt/core.h:1169: undefined reference to
`fmt::v6::internal::error_handler::on_error(char const*)'

Here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956694#10

I suspect this is due to a missing flag like I said earlier.

Regards,
Nilesh

Bug#817954: Does this bug prevent firefox from entering backports also?

[Pirate Praveen]

On Sun, Jun 14, 2020 at 7:31 am, Mike Hommey  wrote:

On Thu, Jun 11, 2020 at 03:22:40PM +0530, Pirate Praveen wrote:
 On Thu, 25 Jul 2019 12:10:45 +0200 Johannes Rohr  
wrote:

 > It would be great to have firefox (or the next firefox-esr) in
 > buster-backports, as it has important new functionality relevant 
for

 > privacy and data protection, such as the multi account containers
 > function. However, this bug prevents firefox from entering 
testing,
 > which in my understanding implies, that it cannot make it into 
backports
 > as well. Is there some way of getting an up-to-date firefox 
version into

 > stable? For now I work with the binary directly downloaded from
 > mozilla.org, but this is a kludge.
 >

 We have created https://fasttrack.debian.net for packages like this
 which cannot go with stable releases and hence blocked from entering
 testing and backports as well.

 Mike,

 Would you like to maintain firefox in buster-fasttrack?

 I'm part of the team that maintain this unofficial service and 
maintains
 gitlab there. If you are okay with the idea, but does not want to 
do the

 extra work, I'd be happy to maintain it in fasttrack.


The package in unstable can be built for stable as long as its version
contains a ~bpo thing. That could be changed to also support fto. But
the bigger problem is that it requires new versions of rustc, cargo 
and
cbindgen, which in turn requires a new version of llvm. And it 
requires

new versions of these quite regularly.

So, no, I'm not really interested in maintaining that.



Thanks for the reply. I will ask around if more people are willing to 
take on the challenge and will try it if there is an interest. Things 
like webRTC suport (jitsi video conferencing) needs recent versions of 
firefox to work well and which is my main interest to take on this.



Mike

Bug#962813: does not build with ghc 8.8

[Picca Frédéric-Emmanuel]

Source: haskell-tree-monad
Severity: critical

Hello,

this package does not build with the up-comming ghc 8.8 version.
It is not part of stackage LTS, and it was not updated by upstream since 2009.
It means that there is few chance to see the upstream fix this issue.

so it is considere to remove it from Debian.

Someone can salvage it by providing a patch (prefereably to the upstream first).

Cheers
 


-- System Information:
Debian Release: bullseye/sid
  APT prefers stable-debug
  APT policy: (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 
'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#956694: [RFS] spdlog

[Nilesh]

Hi,

I've pushed a patch to the team repo[1] to fix this. I patched
./include/spdlog/tweakme.h: Since this file wasn't getting included to
other .h files, I included this bit.
It looks fine to me.

To test this, I did the following:

1. I wrote my own sample code to just include the libs, and it seems to
work.
2. For purify package: Since Ole did a workaround and uploaded, I
checked out the version w/o those workarounds, and it works.

I did the following:
    $ git checkout debian/2.0.0-4
    $ quilt push remove-GreatCMakeCookOff-dependency.patch
   
Append the following lines to cpp/purify/CMakeLists.txt

++if(logging)
++  target_link_libraries(libpurify "-lspdlog -lfmt")
++endif()

So as to include relevant flags. When build this with my changes to
spdlog applied, build passes! \o/

3. For sopt, the build fails with the logs same as what Ole shared
earlier - but looking at them, it seems that spdlog is probably not
responsible for the failure.
    Maybe something else - I'm not sure here. The fmt errors look like
there's a missing flag "-lfmt" and maybe this will do the trick? I
didn't investigate this further.

Andreas, Please take a look at my changes, if you feel it's good to go,
could you please upload?
That'd be great!

[1]: https://salsa.debian.org/med-team/spdlog

Kind Regards,

Nilesh

Bug#948074: marked as done (din FTBFS: cannot find X11/X.h)

[Debian Bug Tracking System]

Your message dated Sun, 14 Jun 2020 13:15:58 +0100
with message-id 

and subject line Re: Bug#948074: din FTBFS: cannot find X11/X.h
has caused the Debian Bug report #948074,
regarding din FTBFS: cannot find X11/X.h
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.)


-- 
948074: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948074
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: din
Version: 5.2.1-6
Severity: serious
Tags: ftbfs

din fails to build from source in unstable on amd64. A build log ends
with:

| dh_auto_build
| make -j1
| make[2]: Entering directory '/<>'
| Making all in include
| make[3]: Entering directory '/<>/include'
| make[3]: Nothing to be done for 'all'.
| make[3]: Leaving directory '/<>/include'
| Making all in src
| make[3]: Entering directory '/<>/src'
| g++ -DPACKAGE_NAME=\"din\" -DPACKAGE_TARNAME=\"din\" 
-DPACKAGE_VERSION=\"5.2.1\" -DPACKAGE_STRING=\"din\ 5.2.1\" 
-DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"din\" 
-DVERSION=\"5.2.1\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 
-DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 
-DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_GL_GL_H=1 
-DHAVE_TCL8_6_TCL_H=1 -DHAVE_LIBIRCCLIENT_H=1 -I.   -Wdate-time 
-D_FORTIFY_SOURCE=2-I /usr/include -I /usr/local/include -I /opt/include 
-I/usr/include/tcl8.6 -I/usr/local/include/tcl8.6 -I /opt/include/tcl8.6 -I 
../include  -Wall -O3 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o main.o main.cc
| main.cc:22:9: fatal error: X11/X.h: No such file or directory
|22 | #include
|   | ^
| compilation terminated.
| make[3]: *** [Makefile:517: main.o] Error 1
| make[3]: Leaving directory '/<>/src'
| make[2]: *** [Makefile:350: all-recursive] Error 1
| make[2]: Leaving directory '/<>'
| dh_auto_build: make -j1 returned exit code 2
| make[1]: *** [debian/rules:12: override_dh_auto_build] Error 255
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:4: build] Error 2
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

Helmut
--- End Message ---
--- Begin Message ---
On Sun, Jun 14, 2020 at 12:29 AM Mattia Rizzolo  wrote:
>
> I know that at the start of the year some reorganization within the X11 
> packages caused down FTBFS while files where being moving around.
>
> I recommend you just close this bug.  FTR, it also builds in 
> reproducible-builds testing.

Thanks Mattia.
Closing now.


-- 
Regards
Sudip--- End Message ---

Bug#914369: marked as done (haskell-simple-templates: FTBFS with ghc-8.4)

[Debian Bug Tracking System]

Your message dated Sun, 14 Jun 2020 14:59:39 +0300
with message-id <20200614115939.d3be523o7cqp7...@iliastsi.net>
and subject line Re: Bug#914369: haskell-simple-templates: FTBFS with ghc-8.4
has caused the Debian Bug report #914369,
regarding haskell-simple-templates: FTBFS with ghc-8.4
to be marked as done.

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

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


-- 
914369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914369
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-simple-templates
Version: 0.8.0.1-4
Severity: serious
Justification: fails to build from source (but built successfully in the past)

It should be patched to build with ghc-8.4.

-- 
Ilias
--- End Message ---
--- Begin Message ---
Version: 0.9.0.0-1

-- 
Ilias--- End Message ---

Processed: notfound 914369 in haskell-simple-templates/0.11.2-2

[Debian Bug Tracking System]

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

> notfound 914369 haskell-simple-templates/0.11.2-2
Bug #914369 [src:haskell-simple-templates] haskell-simple-templates: FTBFS with 
ghc-8.4
The source haskell-simple-templates and version 0.11.2-2 do not appear to match 
any binary packages
No longer marked as found in versions haskell-simple-templates/0.11.2-2.
> thanks
Stopping processing here.

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

Bug#944265: marked as done (mailutils: local privilege escalation in maidag utility (fixed in 3.8) (CVE-2019-18862))

[Debian Bug Tracking System]

Your message dated Sun, 14 Jun 2020 13:34:12 +0200
with message-id <20200614113411.ga17...@debian.org>
and subject line Re: Bug#944265: mailutils: local privilege escalation in 
maidag utility (fixed in 3.8)
has caused the Debian Bug report #944265,
regarding mailutils: local privilege escalation in maidag utility (fixed in 
3.8) (CVE-2019-18862)
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.)


-- 
944265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944265
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mailutils
Severity: serious
Tags: security fixed-upstream

There is a local privilege escalation in the maidag utility:

https://savannah.gnu.org/forum/forum.php?forum_id=9586

   This version fixes important security flow. The maidag utility has
   been withdrawn and three new programs have been included to provide
   its functionality: local mail delivery agent mda, LMTP daemon lmtpd,
   and user mail delivery tool putmail. 

https://git.savannah.gnu.org/cgit/mailutils.git/plain/NEWS

   * The maidag utility is withdrawn

   The main purpose of this utility was to work as local mail delivery
   agent (MDA), a program responsible for final delivery of email messages
   to the recipient's mailbox.  As such it required suid privileges.

   In parallel with its main purpose, it also was able to work in two
   other modes: the 'url' mode, designed to deliver mails to arbitrary
   mailbox URLs, and 'lmtp' mode, in which it acted as local mail
   transport daemon.  Neither of these needed suid privileges.

   The unfortunate design decision to combine the three modes in a single
   versatile tool resulted in local privilege escalation threat in 'url'
   mode.

   To fix this, maidag has been replaced by three different utilities,
   each one with a precisely defined purpose and carefully designed
   privileges: mda, lmtpd, and putmail.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Version: 1:3.8-1

Hi,

On Sat, Nov 23, 2019 at 10:13:46AM +0100, Salvatore Bonaccorso wrote:
> On Fri, Nov 22, 2019 at 02:22:00PM +0100, Jordi Mallach wrote:
> > Hi all,
> > 
> > El dl. 11 de 11 de 2019 a les 21:32 +0100, en/na Salvatore Bonaccorso
> > va escriure:
> > > Control: retitle -1 mailutils: local privilege escalation in maidag
> > > utility (fixed in 3.8) (CVE-2019-18862)

As this is listed as 'fixed in 3.8', it should be fixed in the 3.8 upload.
However, the upload didn't close this bug or mention the CVE. Closing the bug
now.

Thanks for the upload!

Ivo--- End Message ---

Bug#962805: python-geotiepoints: autopkgtest regression: No module named 'h5py

[Paul Gevers]

Source: python-geotiepoints
Version: 1.2.0-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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

   passfail
python-geotiepointsfrom testing1.2.0-1
all others from testingfrom testing

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

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it? It seems like you're
missing a (test) dependency.

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-geotiepoints/5889557/log.gz

autopkgtest [19:08:51]: test python3: [---
=== python3.8 ===
tests (unittest.loader._FailedTest) ... ERROR

==
ERROR: tests (unittest.loader._FailedTest)
--
ImportError: Failed to import test module: tests
Traceback (most recent call last):
  File "/usr/lib/python3.8/unittest/loader.py", line 154, in
loadTestsFromName
module = __import__(module_name)
  File "/usr/lib/python3/dist-packages/geotiepoints/tests/__init__.py",
line 27, in 
from geotiepoints.tests import (test_geointerpolator,
  File
"/usr/lib/python3/dist-packages/geotiepoints/tests/test_modis.py", line
7, in 
import h5py
ModuleNotFoundError: No module named 'h5py'


--
Ran 1 test in 0.000s

FAILED (errors=1)
autopkgtest [19:08:51]: test python3: ---]



signature.asc
Description: OpenPGP digital signature

Bug#962804: wfmath: autopkgtest failure: no acceptable C compiler found in $PATH

[Paul Gevers]

Source: wfmath
Version: 1.0.2+dfsg1-8
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 wfmath, great.
However, it fails. 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. Are you
missing a test dependency?

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

https://ci.debian.net/data/autopkgtest/testing/amd64/w/wfmath/5792572/log.gz

autopkgtest [10:33:44]: test command1: ./configure && make check
autopkgtest [10:33:44]: test command1: [---
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether make supports nested variables... (cached) yes
checking how to print strings... printf
checking for style of include used by make... GNU
checking for gcc... no
checking for cc... no
checking for cl.exe... no
configure: error: in `/tmp/autopkgtest-lxc.nwce0fke/downtmp/build.tAZ/src':
configure: error: no acceptable C compiler found in $PATH
See `config.log' for more details
autopkgtest [10:33:46]: test command1: ---]



signature.asc
Description: OpenPGP digital signature

Bug#962803: rust-csv: autopkgtest failure: could not compile `csv`

[Paul Gevers]

Source: rust-csv
Version: 1.1.3-1
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 rust-csv, great.
However, it fails. 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=rust-csv

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

 Running `CARGO_MANIFEST_DIR=/usr/share/cargo/registry/csv-1.1.3
CARGO_PKG_VERSION=1.1.3
CARGO_PKG_REPOSITORY='https://github.com/BurntSushi/rust-csv'
CARGO_PKG_VERSION_MAJOR=1 CARGO_PKG_VERSION_PRE=
CARGO_PKG_VERSION_PATCH=3 CARGO_PKG_NAME=csv
CARGO_PKG_HOMEPAGE='https://github.com/BurntSushi/rust-csv'
CARGO_PKG_DESCRIPTION='Fast CSV parsing with support for serde.'
CARGO_PKG_AUTHORS='Andrew Gallant '
CARGO_PKG_VERSION_MINOR=1
LD_LIBRARY_PATH='/tmp/tmp.5fF0MMXKFR/target/debug/deps:/usr/lib'
CARGO=/usr/bin/cargo rustc --crate-name cookbook_read_colon
--edition=2018 examples/cookbook-read-colon.rs --error-format=json
--json=diagnostic-rendered-ansi --emit=dep-info,link -C debuginfo=2
--test -C metadata=98c6dd6c57a87f8b -C extra-filename=-98c6dd6c57a87f8b
--out-dir
/tmp/tmp.5fF0MMXKFR/target/x86_64-unknown-linux-gnu/debug/examples
--target x86_64-unknown-linux-gnu -C
incremental=/tmp/tmp.5fF0MMXKFR/target/x86_64-unknown-linux-gnu/debug/incremental
-L
dependency=/tmp/tmp.5fF0MMXKFR/target/x86_64-unknown-linux-gnu/debug/deps
-L dependency=/tmp/tmp.5fF0MMXKFR/target/debug/deps --extern
bstr=/tmp/tmp.5fF0MMXKFR/target/x86_64-unknown-linux-gnu/debug/deps/libbstr-2c0cf4055cf1f260.rlib
--extern
csv=/tmp/tmp.5fF0MMXKFR/target/x86_64-unknown-linux-gnu/debug/deps/libcsv-923bd41be0db7cc6.rlib
--extern
csv_core=/tmp/tmp.5fF0MMXKFR/target/x86_64-unknown-linux-gnu/debug/deps/libcsv_core-8f96475e9851770d.rlib
--extern
itoa=/tmp/tmp.5fF0MMXKFR/target/x86_64-unknown-linux-gnu/debug/deps/libitoa-18ec922b937f216f.rlib
--extern
ryu=/tmp/tmp.5fF0MMXKFR/target/x86_64-unknown-linux-gnu/debug/deps/libryu-562a5218e32671cf.rlib
--extern
serde=/tmp/tmp.5fF0MMXKFR/target/x86_64-unknown-linux-gnu/debug/deps/libserde-df896d28cb66ae5b.rlib
-C debuginfo=2 --cap-lints warn -C linker=x86_64-linux-gnu-gcc -C
link-arg=-Wl,-z,relro --remap-path-prefix
/usr/share/cargo/registry/csv-1.1.3=/usr/share/cargo/registry/csv-1.1.3`
error[E0554]: `#![feature]` may not be used on the stable release channel
 --> benches/bench.rs:1:1
  |
1 | #![feature(test)]
  | ^

error: aborting due to previous error

For more information about this error, try `rustc --explain E0554`.
error: could not compile `csv`.



signature.asc
Description: OpenPGP digital signature

Bug#935614: marked as done (libinfinity: FTBFS on all architectures)

[Debian Bug Tracking System]

Your message dated Sun, 14 Jun 2020 09:48:37 +
with message-id 
and subject line Bug#935614: fixed in libinfinity 0.7.1-2
has caused the Debian Bug report #935614,
regarding libinfinity: FTBFS on all architectures
to be marked as done.

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

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


-- 
935614: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935614
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: src:libinfinity
version: 0.7.1-1
severity: serious
tags: ftbfs

Hi,

A binnmu of libinfinity in unstable failed on all architectures:

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

Cheers,

Ivo
--- End Message ---
--- Begin Message ---
Source: libinfinity
Source-Version: 0.7.1-2
Done: Philipp Kern 

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

Debian distribution maintenance software
pp.
Philipp Kern  (supplier of updated libinfinity package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 14 Jun 2020 11:27:09 +0200
Source: libinfinity
Architecture: source
Version: 0.7.1-2
Distribution: sid
Urgency: medium
Maintainer: Philipp Kern 
Changed-By: Philipp Kern 
Closes: 935614
Changes:
 libinfinity (0.7.1-2) unstable; urgency=medium
 .
   * Fix unstable user list ordering.  (Closes: #935614)
 Thanks to Sunil Mohan Adapa for spending the time to track down and
 fixing the issue!
   * Bump debhelper version to 13 and apply various package cleanups
 along the way.
Checksums-Sha1:
 3c4380c50e83348afd0425a6db061c577927d43c 2121 libinfinity_0.7.1-2.dsc
 a34fc8b716c99379f819d9f601b35894d77f0872 17256 
libinfinity_0.7.1-2.debian.tar.xz
 1b48c8f802881b328e8883209b14ace24f36c432 16371 
libinfinity_0.7.1-2_amd64.buildinfo
Checksums-Sha256:
 ff8cfd5e511a443f2201d94ae7f0420666ed75b3cf08ce2de5ed039ad9ef3752 2121 
libinfinity_0.7.1-2.dsc
 9e060d42638344037f3d52a5f8e0f97f5a4e16294194014cb51b35d170859502 17256 
libinfinity_0.7.1-2.debian.tar.xz
 85d536127239845e9fb91b414ea58e89ff383a4ac5232bc13041759a19eb5b99 16371 
libinfinity_0.7.1-2_amd64.buildinfo
Files:
 4816d0eb92855d95b86896ab36b301ae 2121 libs optional libinfinity_0.7.1-2.dsc
 06c7cb68cd29ce3716fd021b706acd58 17256 libs optional 
libinfinity_0.7.1-2.debian.tar.xz
 ba5eeb9444aaf36eb238d3c9b4ecb3cf 16371 libs optional 
libinfinity_0.7.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQFFBAEBCgAvFiEEPzuChCNsw7gPxr3/RG4lRTXQVuwFAl7l7/gRHHBrZXJuQGRl
Ymlhbi5vcmcACgkQRG4lRTXQVuzN5Af9Eh99FLJbVWS/IZAEeGzwgTaZfjZfGqzO
VhQ/Suf3u3q1kKvRxqOmLIi1d5ZlSIdz8c0tAHBhSYyPThpOss8sC3PZqtvxhVpF
Bv3wLNkwhzrq0Tcsv4aXX1i/g7HILhcnl8QW5VDgN4Ec7IjI7tkj0EXQg8y+7yE7
AiczKi+lnR4v0SEZGeHm/OCAiqCvKZiShSX7UHtrwcRkVHZ3P2ntZHo0/gEiaDws
9QpaOxiE+xltsdugBr3mw+15Oa987BAKbeJ881QHIE/JbfQBCtYyq5VRc9GfE0NM
ZHwKht2ReGLivqtOIZnZiz8R+iqtnMSMcosomfKOzc+iHnnQVK93Dg==
=8ZwZ
-END PGP SIGNATURE End Message ---

Bug#962796: r-cran-dplyr: breaks multiple autopkgtests

[Graham Inggs]

Source: r-cran-dplyr
Version: 1.0.0-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks

Hi Maintainer

The recent upload of r-cran-dplyr causes the autopkgtests of multiple
packages to fail [1][2][3][4], including its own.
This prevents the migration of r-cran-dplyr to testing for 13 days already.

The failures all seem to be different, but some seem to be missing
(test) dependencies, e.g.
r-cran-dplyr:
there is no package called ‘lobstr’
r-cran-rsample:
Failed with error:  ‘there is no package called ‘xml2’’

Regards
Graham


[1] https://ci.debian.net/packages/r/r-cran-bayesplot/testing/amd64/
[2] https://ci.debian.net/packages/r/r-cran-dplyr/testing/amd64/
[3] https://ci.debian.net/packages/r/r-cran-rsample/testing/amd64/
[4] https://ci.debian.net/packages/r/r-cran-sf/testing/amd64/

Bug#962794: r-cran-stanheaders: breaks r-cran-rstanarm autopkgtests

[Graham Inggs]

Source: r-cran-stanheaders
Version: 2.21.0-3-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks

Hi Maintainer

The recent upload of r-cran-stanheaders causes the autopkgtests of
r-cran-rstanarm to fail [1].
This prevents the migration of r-cran-stanheaders to testing for 8 days already.

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

Regards
Graham


[1] https://ci.debian.net/packages/r/r-cran-rstanarm/testing/amd64/


 *** caught segfault ***
address 0x9b377c, cause 'memory not mapped'

Traceback:
 1: 
dyn.load("/tmp/RtmpFHXEap/sourceCpp-x86_64-pc-linux-gnu-1.0.4.6/sourcecpp_15d03ae3f182/sourceCpp_2.so")
 2: eval(ei, envir)
 3: eval(ei, envir)
 4: withVisible(eval(ei, envir))
 5: source(scriptPath, local = env)
 6: Rcpp::sourceCpp(code = paste(code, collapse = "\n"), ...)
 7: withCallingHandlers(expr, warning = function(w) if (inherits(w,
 classes)) tryInvokeRestart("muffleWarning"))
 8: suppressWarnings(Rcpp::sourceCpp(code = paste(code, collapse =
"\n"), ...))
 9: doTryCatch(return(expr), name, parentenv, handler)
10: tryCatchOne(expr, names, parentenv, handlers[[1L]])
11: tryCatchList(expr, classes, parentenv, handlers)
12: tryCatch(expr, error = function(e) {call <- conditionCall(e)
 if (!is.null(call)) {if (identical(call[[1L]],
quote(doTryCatch))) call <- sys.call(-4L)dcall <-
deparse(call)[1L]prefix <- paste("Error in", dcall, ": ")
  LONG <- 75Lsm <- strsplit(conditionMessage(e), "\n")[[1L]]
 w <- 14L + nchar(dcall, type = "w") + nchar(sm[1L], type = "w")
 if (is.na(w)) w <- 14L + nchar(dcall, type = "b") +
nchar(sm[1L], type = "b")if (w > LONG)
prefix <- paste0(prefix, "\n  ")}else prefix <- "Error : "
   msg <- paste0(prefix, conditionMessage(e), "\n")
.Internal(seterrmessage(msg[1L]))if (!silent &&
isTRUE(getOption("show.error.messages"))) {cat(msg, file =
outFile).Internal(printDeferredWarnings())}
invisible(structure(msg, class = "try-error", condition = e))})
13: try(suppressWarnings(Rcpp::sourceCpp(code = paste(code, collapse =
"\n"), ...)), silent = TRUE)
14: pkgbuild::with_build_tools(try(suppressWarnings(Rcpp::sourceCpp(code
= paste(code, collapse = "\n"), ...)), silent = TRUE), required =
rstan_options("required") && identical(Sys.getenv("WINDOWS"),
"TRUE") && !identical(Sys.getenv("R_PACKAGE_SOURCE"), ""))
15: expose_stan_functions(stanc_ret, rebuild = TRUE)
16: eval(code, test_env)
17: eval(code, test_env)
18: withCallingHandlers({eval(code, test_env)if (!handled &&
!is.null(test)) {skip_empty()}}, expectation =
handle_expectation, skip = handle_skip, warning = handle_warning,
message = handle_message, error = handle_error)
19: doTryCatch(return(expr), name, parentenv, handler)
20: tryCatchOne(expr, names, parentenv, handlers[[1L]])
21: tryCatchList(expr, names[-nh], parentenv, handlers[-nh])
22: doTryCatch(return(expr), name, parentenv, handler)
23: tryCatchOne(tryCatchList(expr, names[-nh], parentenv,
handlers[-nh]), names[nh], parentenv, handlers[[nh]])
24: tryCatchList(expr, classes, parentenv, handlers)
25: tryCatch(withCallingHandlers({eval(code, test_env)if
(!handled && !is.null(test)) {skip_empty()}}, expectation
= handle_expectation, skip = handle_skip, warning = handle_warning,
 message = handle_message, error = handle_error), error =
handle_fatal, skip = function(e) {})
26: test_code(NULL, exprs, env)
27: source_file(path, new.env(parent = env), chdir = TRUE, wrap = wrap)
28: force(code)
29: doWithOneRestart(return(expr), restart)
30: withOneRestart(expr, restarts[[1L]])
31: withRestarts(testthat_abort_reporter = function() NULL, force(code))
32: with_reporter(reporter = reporter, start_end_reporter =
start_end_reporter, {reporter$start_file(basename(path))
 lister$start_file(basename(path))source_file(path,
new.env(parent = env), chdir = TRUE, wrap = wrap)
reporter$.end_context()reporter$end_file()})
33: FUN(X[[i]], ...)
34: lapply(paths, test_file, env = env, reporter = current_reporter,
  start_end_reporter = FALSE, load_helpers = FALSE, wrap = wrap)
35: force(code)
36: doWithOneRestart(return(expr), restart)
37: withOneRestart(expr, restarts[[1L]])
38: withRestarts(testthat_abort_reporter = function() NULL, force(code))
39: with_reporter(reporter = current_reporter, results <-
lapply(paths, test_file, env = env, reporter = current_reporter,
start_end_reporter = FALSE, load_helpers = FALSE, wrap = wrap))
40: test_files(paths, reporter = reporter, env = env, stop_on_failure
= stop_on_failure, stop_on_warning = stop_on_warning, wrap = wrap)
41: test_dir(path = test_path, reporter = reporter, env = env, filter
= filter, ..., stop_on_failure = stop_on_failure, stop_on_warning
= stop_on_warning, wrap = wrap)
42: 

Bug#962784: [Pkg-puppet-devel] Bug#962784: facter aborts with free(): invalid pointer

[Stig Sandbeck Mathisen]

Russ Allbery  writes:

> Package: facter
> Version: 3.11.0-4.1
> Severity: grave
>
> facter no longer works at all on amd64.  When invoked, it dies with
> an invalid pointer error:

Looks like the same bug as http://bugs.debian.org/962692 and related to
https://bugs.debian.org/962320

A quick workaround to get facter to run is to create the three
directories:

/etc/facter/facts.d
/etc/puppetlabs/facter/facts.d
/opt/puppetlabs/facter/facts.d


root@bts962784-facter:~# facter
free(): invalid pointer
Aborted

root@bts962784-facter:~# mkdir -p /opt/puppetlabs/facter/facts.d 
/etc/facter/facts.d /etc/puppetlabs/facter/facts.d

root@bts962784-facter:~# facter
disks => {
  nvme0n1 => {
[...]

-- 
Stig Sandbeck Mathisen
Debian Developer

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> reassign 959543 src:pbcopper
Bug #959543 [src:pbdagcon] pbdagcon: FTBFS: ld: 
/usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libblasr.so: 
undefined reference to `PacBio::Data::QualityValues::cend() const'
Bug reassigned from package 'src:pbdagcon' to 'src:pbcopper'.
No longer marked as found in versions pbdagcon/0.3+git20180411.c14c422+dfsg-1.
Ignoring request to alter fixed versions of bug #959543 to the same values 
previously set
> forcemerge 959409 959543
Bug #959409 {Done: Andreas Tille } [src:pbcopper] pbcopper 
breaks pbbam (autopkgtest): libpbcopper.so.1.3.0: cannot open shared object 
file: No such file or directory
Bug #959409 {Done: Andreas Tille } [src:pbcopper] pbcopper 
breaks pbbam (autopkgtest): libpbcopper.so.1.3.0: cannot open shared object 
file: No such file or directory
Added tag(s) ftbfs.
Bug #959543 [src:pbcopper] pbdagcon: FTBFS: ld: 
/usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libblasr.so: 
undefined reference to `PacBio::Data::QualityValues::cend() const'
Marked Bug as done
Added indication that 959543 affects src:pbbam
Marked as fixed in versions pbcopper/1.6.0+dfsg-2.
Marked as found in versions pbcopper/1.4.0+dfsg-1.
Merged 959409 959543
> affects 959409 src:pbdagcon
Bug #959409 {Done: Andreas Tille } [src:pbcopper] pbcopper 
breaks pbbam (autopkgtest): libpbcopper.so.1.3.0: cannot open shared object 
file: No such file or directory
Bug #959543 {Done: Andreas Tille } [src:pbcopper] pbdagcon: 
FTBFS: ld: 
/usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libblasr.so: 
undefined reference to `PacBio::Data::QualityValues::cend() const'
Added indication that 959409 affects src:pbdagcon
Added indication that 959543 affects src:pbdagcon
> thanks
Stopping processing here.

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

Bug#961076: marked as done (NXNS Attack (CVE-2020-12667))

[Debian Bug Tracking System]

Your message dated Sun, 14 Jun 2020 07:03:29 +
with message-id 
and subject line Bug#961076: fixed in knot-resolver 5.1.1-0.1
has caused the Debian Bug report #961076,
regarding NXNS Attack (CVE-2020-12667)
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.)


-- 
961076: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961076
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: knot
Severity: serious
Tag: security

Hi,

it would be nice if you could upgrade to the current upstream version of
knot-resolver (5.1.1) which mitigates CVE-2020-12667 aka NXNS Attack.

Regards,
Daniel
--- End Message ---
--- Begin Message ---
Source: knot-resolver
Source-Version: 5.1.1-0.1
Done: Daniel Baumann 

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

Debian distribution maintenance software
pp.
Daniel Baumann  (supplier of updated 
knot-resolver package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 14 Jun 2020 06:24:58 +0200
Source: knot-resolver
Architecture: source
Version: 5.1.1-0.1
Distribution: unstable
Urgency: medium
Maintainer: knot-resolver packagers 
Changed-By: Daniel Baumann 
Closes: 961076
Changes:
 knot-resolver (5.1.1-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream release:
 - mitigation for NXNSAttack DNS protocol vulnerability
   [CVE-2020-12667] (Closes: #961076)
Checksums-Sha1:
 e13edfe272a1b337577c72c4b1ade7c7da7b070f 2730 knot-resolver_5.1.1-0.1.dsc
 59cd5b722d9e690b2c7447505f308ec400c83a32 1744544 
knot-resolver_5.1.1.orig.tar.xz
 ac4a0212546decdc0c2e85bc927815ad10bb1062 405288 
knot-resolver_5.1.1-0.1.debian.tar.xz
 17011edd6072e73aeeefd0f6cc6a14f4ad697bbb 9799 
knot-resolver_5.1.1-0.1_amd64.buildinfo
Checksums-Sha256:
 3fa49d88f06bdd472e95a52eb2999dc3470c3e2c603e2b0544d6a1343f136446 2730 
knot-resolver_5.1.1-0.1.dsc
 f72214046df8aae2b1a5c6d1ad0bc8b166aa060df5b008f6e88b4f6ba79cbf4e 1744544 
knot-resolver_5.1.1.orig.tar.xz
 393ad77406c632e60ed1e5c8f977675924d6f82524ca47b6fef2acde29c44420 405288 
knot-resolver_5.1.1-0.1.debian.tar.xz
 db34d15eee219581869e5bbf54107c1d9d20b2af4996c8c0bf44b2f1941d2a8c 9799 
knot-resolver_5.1.1-0.1_amd64.buildinfo
Files:
 5d68b3d173fb4376ccc60dea9ec7318e 2730 net optional knot-resolver_5.1.1-0.1.dsc
 0895b0b6e2d8af9c93bb7ca00acea355 1744544 net optional 
knot-resolver_5.1.1.orig.tar.xz
 89a64a7cc62a4c51b4f388f11f6d69e1 405288 net optional 
knot-resolver_5.1.1-0.1.debian.tar.xz
 1825234bbbf52d9c174bcaefeadc387c 9799 net optional 
knot-resolver_5.1.1-0.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEgTbtJcfWfpLHSkKSVc8b+YaruccFAl7lxVwACgkQVc8b+Yar
ucfTNxAAiTU4R8c/DaprWE1bj8puxRvCOrM6U7f5tc4FHV8/4fEme/nVIjz24pR4
tCRKl0XVnAWg2/qbc2t7oEOdqPQpfxzSM7AxzAAp/g+7uIiN76pbfdnjGcJhDAHk
owLhY5mrNc6rPl/GjrviIqbQNpPMyft5x/R7J/+r88FwiBUrUZ0lJZHYnfGc7VBm
6ji1MEWuvVzE2YOwdA0S3W69xrG/RpfYF/RG6g1nhp5ZHgn+m1CmiUVBO6ReNvbM
LjQZ5KYagHKsGoxR8NJO3jxpqOPxKx6rtPYClH81XIwFUkuBz/1+PNIadyzqXjEo
w5iT7Fu4SP9gHpueZu4owNK7yO/PsMFsRYX8rGdYQ1HmH57bT15+5Bxz+wCNKR0f
mzvEZSnoB8sd7xUDxcV2zfihtP+5Vsp7mEmVc6hhqtc94i9/BypsrfW0Y+kadqIE
b+G7MET4MfYh+hsS4BLnY5qYkBHd0Na18/p7pAfjyc5/3Tp0bEL2iMEFx46IAytu
ubNkqiDIoGDNlh1B7bkJ4JgP7f16Ojf6TejQ1W7fSRV/EvGRhd+oSY1NLSXIZbkp
rU/Mud+Rtm3MLrnsCtjQZZdp9L2Gw4pyDSDCDlwTMgqwpTaTl05gfkO1QhHA2fp+
FI9gCdJgnfn4dE3Lr9vzYNUMcTJkkeH9c+UxiNQNuHdYs4sbb1w=
=bABP
-END PGP SIGNATURE End Message ---