Bug#970753: apertium-ind-zlm: Wrong e-mail address in Maintainer field

[Tino Didriksen]

Upstream packaging fixed this for all Apertium and related packages in May,
and this will come through to Debian this week and weekend when I redo all
Apertium packaging.

https://github.com/apertium/apertium-packaging/commit/11357cf6325363a2b4127b0f5fd1bdaaf3726232

-- Tino Didriksen


On Wed, 23 Sep 2020 at 00:38, Alex Muntada  wrote:

> Package: apertium-ind-zlm
> Version: 0.1.2-2
> Severity: serious
> Usertags: alioth-lists.debian.org
> X-Debbugs-Cc: kar...@debian.org, t...@didriksen.cc
>
> The Maintainer of this package uses the alioth-lists.debian.org
> domain, which does not exist. This breaks policy §3.3[1] that
> requires a working e-mail address. You should be using the
> alioth-lists.debian.net domain instead.
>
> After reporting[2] the issue to debian-science-maintainers list,
> I'm filing this bug as suggested[3] there.
>
> Cheers,
> Alex
>
>   [1] https://www.debian.org/doc/debian-policy/ch-binary.html#s-maintainer
>   [2]
> https://alioth-lists.debian.net/pipermail/debian-science-maintainers/2020-September/085266.html
>   [3]
> https://alioth-lists.debian.net/pipermail/debian-science-maintainers/2020-September/085350.html
>
> --
>   ⢀⣴⠾⠻⢶⣦⠀
>   ⣾⠁⢠⠒⠀⣿⡁   Alex Muntada 
>   ⢿⡄⠘⠷⠚⠋   Debian Developer  log.alexm.org
>   ⠈⠳⣄
>
>

Bug#970664: libvte-2.91-0: Terminal not displaying correctly

[Fabián Inostroza]

Hi,

The issue happens with some themes, normally I use Numix from the
repositories, when using HighContrast or HighContrastInverse the issue
also happens. With adwaita it works fine.

Regards.

El lun., 21 sept. 2020 a las 11:51, Fabián Inostroza
() escribió:
>
> Hi,
>
> When I take a screenshot of the whole screen the background of the
> terminal is transparent, that is, if there is another window behind
> then the content of that window is captured, the text of the terminal
> is kept.
> If I take a screenshot of the terminal window then the background is
> transparent, nothing is shown, except text, the alpha channel is zero.
> In both cases I see some other corrupt content on the screen.
>
> The only warning I get when launching gnome-terminal from xterm is
> $ gnome-terminal -v
> # Warning: DESKTOP_STARTUP_ID not set and no fallback available.
>
> then the program detaches from the console.
>
> No related warnings shown on journal or dmesg.
>
> I'm using GNOME with X11 and intel modesetting driver. I've tried all
> combinations of X11, wayland, intel and modesetting driver with the
> same results. My hardware is a thinkpad x230.
>
> Until now I'm not seeing corruption in other applications, just
> gnome-terminal and the gedit terminal plugin. Other terminal
> applications work fine (I've tried xterm and terminator).
>
> Regards.
>
>
>
> El lun., 21 sept. 2020 a las 5:53, Simon McVittie () 
> escribió:
> >
> > Control: tags -1 + moreinfo
> >
> > On Sun, 20 Sep 2020 at 19:29:19 -0300, Fabian Inostroza wrote:
> > > After an upgrade of libvte gnome-terminal and other software using
> > > the library (gedit terminal plugin) doesn't work.
> > > Where the console should be there is some transparency and a effect
> > > similar to when you record a screen that shows what
> > > the camera sees (feedback).
> >
> > If you take a screenshot (please try both a screenshot of the window and
> > a full-screen screenshot), does the display corruption appear in the
> > screenshot, or does the screenshot show what it *should* have looked
> > like?
> >
> > If you run gnome-terminal or another program using vte from a different
> > terminal such as xterm, are warnings shown?
> >
> > Are any warnings logged in the systemd journal when you run a program
> > that uses vte for the first time in a session?
> >
> > What desktop environment are you using? If it's GNOME, are you in Wayland
> > or Xorg mode?
> >
> > What graphics hardware are you using? If both open-source and proprietary
> > drivers are available, which one are you using? (Some common graphics
> > hardware on PC: Intel integrated graphics with DRI/Mesa open-source
> > drivers, AMD Radeon series with DRI/Mesa open-source drivers, NVIDIA
> > with DRI/Mesa "nouveau" open-source drivers, or NVIDIA with proprietary
> > "nvidia-driver".)
> >
> > Do you see similar graphical corruption anywhere else?
> >
> > gnome-terminal is working fine for me in GNOME 3.36 in a qemu virtual
> > machine with QXL graphics, and in GNOME 3.38 from experimental on real
> > hardware (a Lenovo Thinkpad) with Intel graphics, so I'm not going to
> > be able to debug this unless we can isolate what is happening differently
> > on your system.
> >
> > smcv

Processed: Bug#970762 in package pciutils marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag 970762 pending
Bug #970762 {Done: Guillem Jover } [pciutils] virt-manger 
fails to open vm console/info with: Error launching details: g-io-error-quark: 
Error opening file /usr/share/misc/pci.ids: No such file or directory
Added tag(s) pending.

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

Bug#970762: in package pciutils marked as pending

[Guillem Jover]

Control: tag 970762 pending

Hi!

Bug #970762 in package pciutils reported by you has been fixed in
the debian/pkgs/pciutils.git Git repository. You can see the changelog below, 
and
you can check the diff of the fix at:

https://git.hadrons.org/cgit/debian/pkgs/pciutils.git/diff/?id=c2c2854

---
commit c2c28549a513b93898d8c49f6eb8cefc1670a1e2
Author: Guillem Jover 
Date:   Wed Sep 23 03:00:35 2020 +0200

Force the hardlink for the backup pci.ids database in update-pciids

Closes: #970762, #970762

diff --git a/debian/changelog b/debian/changelog
index f288704..56849fd 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+pciutils (1:3.7.0-3) UNRELEASED; urgency=medium
+
+  * Force the hardlink for the backup pci.ids database in update-pciids.
+Closes: #970762, #970762
+
+ -- Guillem Jover   Wed, 23 Sep 2020 02:58:44 +0200
+
 pciutils (1:3.7.0-2) unstable; urgency=medium
 
   * Fix build failure on Hurd, by taking a patch from upstream git.

Bug#970762: marked as done (virt-manger fails to open vm console/info with: Error launching details: g-io-error-quark: Error opening file /usr/share/misc/pci.ids: No such file or directory)

[Debian Bug Tracking System]

Your message dated Wed, 23 Sep 2020 01:19:08 +
with message-id 
and subject line Bug#970762: fixed in pciutils 1:3.7.0-3
has caused the Debian Bug report #970762,
regarding virt-manger fails to open vm console/info with: Error launching 
details: g-io-error-quark: Error opening file /usr/share/misc/pci.ids: No such 
file or directory
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.)


-- 
970762: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970762
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pciutils
Version: 1:3.7.0-2
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

The recent update-pciutils command seems to remove /usr/share/misc/pci.ids. This
leads to the error described in the subject and also removes a file distributed 
by
the pci.ids Debian package which is a clear policy violation.

Please fix this asap. Also #950812 should be fixed with this upload. Forcing the
link creation solves this issue.

Regards, Daniel


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

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

Versions of packages pciutils depends on:
ii  libc6 2.31-3
ii  libkmod2  27+20200310-2
ii  libpci3   1:3.7.0-2

pciutils recommends no packages.

Versions of packages pciutils suggests:
ii  bzip2  1.0.8-4
ii  curl   7.72.0-1
ii  wget   1.20.3-1+b3

- -- no debconf information

- -- debsums errors found:
debsums: changed file /usr/sbin/update-pciids (from pciutils package)

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAl9qjZUACgkQS80FZ8KW
0F0g6RAA2hoYUaAhp34nZUDlBfHONgtHTzNt2sbGEfKO2q/CaBIbH6vem0W0osgX
au6dvtR0hGN2vAImC7T7gLb7rqGMHafQxhZMuTA5thsKBW4pm6Tb+IGg0XRU3QFt
4wp4XqAPrnfoFEzMEZIqkAeRVXLtboD7opHBgfbZdaYuuSumZo/P5ftBss9esCpz
JYXbv1dCw7nbaWnOioe93prypyi+coBd0AkP7piJCA9Tl6ybKDxES6UZE+QkdDQ5
0ssVD3HyV5DG80Y/vONQ6t6hSkNYtDTtUhuqUPE+Q+Mvlce43Igogln6Hbu54QaO
f8rYBpzyWfBOuRw6Ol6ODoFTqmmc0i8YUjJ/0jxbRlZGAqfk9SrxMpx18ZzC2uu3
yd2GCtmw/owhIrV4BUTTW06WpE+mwSwzbtDDdfRsH+oRLCk1NGNzmc4F8zTPj33j
akjWysiM8/YClkEP4fo9YNWQxLcFUr3T+6TLWvUG7EqSUQj4R4lKBND8VDTiS7L9
1UJ86SeiujfnAx8+eWM/mDiSynXgFLRoQ9Uv/5tXXieOweTUPxbl+Q9TV7u7m+Ja
VnMAxpHRrDsk3jO1sJlVcvzZ6OPD6LY0K6I7fBFQ8TpioGZxB+Uupws0vXBjtAaz
8KV3m/ZUTaGHlsANriQSmdmeAMTwDgfL2xlOn+0ywXP0fxCE6bA=
=42bX
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: pciutils
Source-Version: 1:3.7.0-3
Done: Guillem Jover 

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

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

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

Debian distribution maintenance software
pp.
Guillem Jover  (supplier of updated pciutils package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 23 Sep 2020 03:00:51 +0200
Source: pciutils
Architecture: source
Version: 1:3.7.0-3
Distribution: unstable
Urgency: medium
Maintainer: Guillem Jover 
Changed-By: Guillem Jover 
Closes: 970762
Changes:
 pciutils (1:3.7.0-3) unstable; urgency=medium
 .
   * Force the hardlink for the backup pci.ids database in update-pciids.
 Closes: #970762, #970762
Checksums-Sha1:
 01c1adce737757ee67e9f2981dcf75a90716855b 2515 pciutils_3.7.0-3.dsc
 90d3e4fab494cf783254342d600ac3b6f6045922 21376 pciutils_3.7.0-3.debian.tar.xz
 58daed7d39e13f9f60c3338f76011c1bf509f11b 7045 pciutils_3.7.0-3_amd64.buildinfo
Checksums-Sha256:
 18674b9747679f173b9c3f4952a9954ec8761a51929dc91d410c0923b31cee56 2515 
pciutils_3.7.0-3.dsc
 f6a73af583392ba24f2bd92300402a149b54f75563b3f0ea23a764b626be8370 21376 
pciutils_3.7.0-3.debian.tar.xz
 eb12328c12eadaeddf7e7557b2a7abb0ec7ecda4e723539c671339cd1d4e5831 7045 
pciutils_3.7.0-3_amd64.buildinfo
Files:
 5c8df6ea895c8507fb4b8f5c0a3e5080 2515 admin optional pciutils_3.7.0-3.dsc
 

Bug#970764: python3-venv: /usr/bin/pyvenv is a dangling symlink, man page, too

[Norbert Preining]

Package: python3-venv
Version: 3.8.2-3
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: norb...@preining.info

Hi

something seems to have gone a bit wrong with the venv packaging, since
both the actual binary pyvenv in /usr/bin, as well as the man page are
both dangling symlinks, rendering the package unusable.

Thanks

Norbert

-- 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.8.10 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages python3-venv depends on:
ii  python33.8.2-3
ii  python3-distutils  3.8.5-1
ii  python3.8-venv 3.8.6~rc1-2

python3-venv recommends no packages.

python3-venv suggests no packages.

-- no debconf information

Bug#970763: wminput immedinately exits with Segmentation Fault on use

[Ryan Armstrong]

Package: wminput
Version: 0.6.91-1+b1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

With the most recent version of wminput, the application fails to start
immediately, raising a Segmentation Fault. This occurrs on both of my
machines that currently track Debian Testing. It does not matter what
command-line arguments are used, even --version causes this behaviour.

I attempted to rebuild the package with debug symbols in order to get a
useful stack trace. While I was able to build and install the package +
dbgsym packages, the backtrace in gdb was not useful. Here it is for
reference anyways:

$ gdb wminput
GNU gdb (Debian 9.2-1) 9.2
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later

This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from wminput...
Reading symbols from
/usr/lib/debug/.build-id/87/07b22dc522a1bffe98fc49614410ec12d85b05.debug...
(gdb) run
Starting program: /usr/bin/wminput 

Program received signal SIGSEGV, Segmentation fault.
0x0001 in ?? ()
(gdb) bt
#0  0x0001 in ?? ()
#1  0x7fffe4b2 in ?? ()
#2  0x in ?? ()

And here is LDD's output:

$ ldd /usr/bin/wminput
linux-vdso.so.1 (0x7ffc5dbc2000)
libcwiid.so.1 => /usr/lib/libcwiid.so.1 (0x7f3439bdb000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f3439bd5000)
libbluetooth.so.3 => /usr/lib/x86_64-linux-gnu/libbluetooth.so.3 
(0x7f3439bb)
libpython3.8.so.1.0 => /usr/lib/x86_64-linux-gnu/libpython3.8.so.1.0 
(0x7f3439667000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f3439645000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f343948)
/lib64/ld-linux-x86-64.so.2 (0x7f3439c4c000)
libexpat.so.1 => /lib/x86_64-linux-gnu/libexpat.so.1 
(0x7f3439451000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f3439434000)
libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 (0x7f343942f000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f34392eb000)

I'm hoping this should be trivial for anyone else to reproduce. 
If you'd like me to try anything else, please let me know.

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

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

Versions of packages wminput depends on:
ii  libbluetooth3  5.54-1
ii  libc6  2.31-3
ii  libcwiid1  0.6.91-1+b1
ii  libpython3.8   3.8.5-2
ii  python3-cwiid  0.6.91-1+b1

wminput recommends no packages.

wminput suggests no packages.

-- no debconf information

Processed: affects 970762

[Debian Bug Tracking System]

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

> affects 970762 + pci.ids virt-manager
Bug #970762 [pciutils] virt-manger fails to open vm console/info with: Error 
launching details: g-io-error-quark: Error opening file 
/usr/share/misc/pci.ids: No such file or directory
Added indication that 970762 affects pci.ids and virt-manager
> thanks
Stopping processing here.

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

Bug#970762: virt-manger fails to open vm console/info with: Error launching details: g-io-error-quark: Error opening file /usr/share/misc/pci.ids: No such file or directory

[Daniel Leidert]

Package: pciutils
Version: 1:3.7.0-2
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

The recent update-pciutils command seems to remove /usr/share/misc/pci.ids. This
leads to the error described in the subject and also removes a file distributed 
by
the pci.ids Debian package which is a clear policy violation.

Please fix this asap. Also #950812 should be fixed with this upload. Forcing the
link creation solves this issue.

Regards, Daniel


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

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

Versions of packages pciutils depends on:
ii  libc6 2.31-3
ii  libkmod2  27+20200310-2
ii  libpci3   1:3.7.0-2

pciutils recommends no packages.

Versions of packages pciutils suggests:
ii  bzip2  1.0.8-4
ii  curl   7.72.0-1
ii  wget   1.20.3-1+b3

- -- no debconf information

- -- debsums errors found:
debsums: changed file /usr/sbin/update-pciids (from pciutils package)

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAl9qjZUACgkQS80FZ8KW
0F0g6RAA2hoYUaAhp34nZUDlBfHONgtHTzNt2sbGEfKO2q/CaBIbH6vem0W0osgX
au6dvtR0hGN2vAImC7T7gLb7rqGMHafQxhZMuTA5thsKBW4pm6Tb+IGg0XRU3QFt
4wp4XqAPrnfoFEzMEZIqkAeRVXLtboD7opHBgfbZdaYuuSumZo/P5ftBss9esCpz
JYXbv1dCw7nbaWnOioe93prypyi+coBd0AkP7piJCA9Tl6ybKDxES6UZE+QkdDQ5
0ssVD3HyV5DG80Y/vONQ6t6hSkNYtDTtUhuqUPE+Q+Mvlce43Igogln6Hbu54QaO
f8rYBpzyWfBOuRw6Ol6ODoFTqmmc0i8YUjJ/0jxbRlZGAqfk9SrxMpx18ZzC2uu3
yd2GCtmw/owhIrV4BUTTW06WpE+mwSwzbtDDdfRsH+oRLCk1NGNzmc4F8zTPj33j
akjWysiM8/YClkEP4fo9YNWQxLcFUr3T+6TLWvUG7EqSUQj4R4lKBND8VDTiS7L9
1UJ86SeiujfnAx8+eWM/mDiSynXgFLRoQ9Uv/5tXXieOweTUPxbl+Q9TV7u7m+Ja
VnMAxpHRrDsk3jO1sJlVcvzZ6OPD6LY0K6I7fBFQ8TpioGZxB+Uupws0vXBjtAaz
8KV3m/ZUTaGHlsANriQSmdmeAMTwDgfL2xlOn+0ywXP0fxCE6bA=
=42bX
-END PGP SIGNATURE-

Bug#919595: marked as done (zsnapd: must be in contrib as it depends on contrib package)

[Debian Bug Tracking System]

Your message dated Tue, 22 Sep 2020 23:22:04 +
with message-id 
and subject line Bug#919595: fixed in zsnapd 0.8.11h-3
has caused the Debian Bug report #919595,
regarding zsnapd: must be in contrib as it depends on contrib package
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.)


-- 
919595: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919595
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: zsnapd
Version: 0.5.2-1
Severity: serious
Justification: Policy 2.2.1

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

zsnapd depends on zfsutils-linux, which is in contrib.

Debian Policy § 2.2.1 says:

> In addition, the packages in *main*
>
> * must not require or recommend a package outside of *main* for
>   compilation or execution (thus, the package must not declare a "Pre-
>   Depends", "Depends", "Recommends", "Build-Depends", "Build-Depends-
>   Indep", or "Build-Depends-Arch" relationship on a non-*main* package
>   unless that package is only listed as a non-default alternative for
>   a package in *main*),

Please move zsnapd to contrib.


 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlxAxMoACgkQLHwxRsGg
ASHgJxAAgY68xpUJvi+9DjRLnUM7H9jt+x5/lhamaa2Del1YEakhIk9m4yctYAWm
3YI+aODptqAlY21kBDDB+ekRxjIBQCYSpBUp7bXdWCCMjGDMYIWpFq/T8BixsLmq
LB08YTuvbP5xc3xTjngeP9pGe+51nmRlCliUE/dkjhgSNDp21dKzNrHnuMjaYzI6
pPPsDiRWpusVKEgFRBrrx4IICQk0Q6zyDdXfy0ZBwyvm7x9cxikohYK76PZ7vOVJ
0XijHJC9dtDDumIIOxqsRvdRtumh7VRErnAoG73HW/7/ERvZDoGlfGAB/xvsaW0U
foxxJkK/P7vNCEVCNpQ67/SD+U4OkCXk2oaB+E/BcVC5EF2KGpP0O7syisXM3MBE
pNc0+l7GgqD6CChT+RAMuhU1nWxpTNfv8xL6w/Y6rewZT/uEtNF3sNGp+Gj/OtXP
e8nZyDS9C2XS5jWtjy0dwdkw0zO2kd2W4mECpXzgORpBDATE7cI4ApkUlltb1Wo6
5w9EP/yx/OU1ItNbS+ijOtwtQNkBv0guawL1FE1NI5IIQWCUA1OUjC7UUSoRz1+2
YBDgCehnvOmFFGQYb7UOAW9MhiYk9urK/fduDIgMYZZOOzroqyknHnGsnZK+IEJ9
dl713UH3oJLnMH2DGWfGhiVnYQiiIU0ZLQ9jxmjyWKI1tK8t3ms=
=8DoW
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: zsnapd
Source-Version: 0.8.11h-3
Done: Matthew Grant 

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

Debian distribution maintenance software
pp.
Matthew Grant  (supplier of updated zsnapd 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: Wed, 23 Sep 2020 10:58:27 +1200
Source: zsnapd
Architecture: source
Version: 0.8.11h-3
Distribution: unstable
Urgency: medium
Maintainer: Matthew Grant 
Changed-By: Matthew Grant 
Closes: 919595 943302
Changes:
 zsnapd (0.8.11h-3) unstable; urgency=medium
 .
   * Really fix bug about being in wrong section. (Closes: #943302)
   * Source only upload. (Closes: #919595)
Checksums-Sha1:
 6d3e0edb7a9f9b0443bc8308cf7c965310ea19cb 1873 zsnapd_0.8.11h-3.dsc
 8d749f12eec3e731bf2f04d39c5278025b37adaf 30505 zsnapd_0.8.11h.orig.tar.gz
 91d66a18a5daa081ff3ff23ef7cb00b64dcbb928 7232 zsnapd_0.8.11h-3.debian.tar.xz
 4d6737b60b2f96fea05db9746e0ddfcb80f7fade 6959 zsnapd_0.8.11h-3_amd64.buildinfo
Checksums-Sha256:
 b9d8783d9338839e789310a01eee4f8416dfb418355f0233ba726dee1f910200 1873 
zsnapd_0.8.11h-3.dsc
 9d94872008b37a821ccdb9eb50d5eb9db8f1c4aa00d31f38e14f1eaf7d4f8b84 30505 
zsnapd_0.8.11h.orig.tar.gz
 3cb220289d4b3c0d31e8ca789ccfc04f2c8559fb037e7bf3274cc9ce2126da10 7232 
zsnapd_0.8.11h-3.debian.tar.xz
 4c82e4d66f2d6ee77461ec844b5f5b11f320dff035e7a4f15f13239a62fa7d5d 6959 
zsnapd_0.8.11h-3_amd64.buildinfo
Files:
 d213dc7859dbba2e6007140bda8d1ede 1873 contrib/admin optional 
zsnapd_0.8.11h-3.dsc
 fd180bc642aee902d3941f49d8a773ea 30505 contrib/admin optional 
zsnapd_0.8.11h.orig.tar.gz
 54bc236a3328e6cdc70bb7fb2d0212ba 7232 contrib/admin optional 
zsnapd_0.8.11h-3.debian.tar.xz
 9cbae295cb99cfee2bf3b2f9062ff4a3 6959 contrib/admin optional 
zsnapd_0.8.11h-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJKBAEBCAA0FiEEwaHD8RNdvgk2cFzjxE5f/BM1w6IFAl9qgbMWHG1hdHRAbWF0
dGdyYW50Lm5ldC5uegAKCRDETl/8EzXDonhzD/4jwIVhEXoNg6+kK5L3EnbHmfzR
1UVhjo0dHGqYG+6YAUBeg5kXRDx6edqtTI6iXkVGZf15dMSOudLdATUnPKjqbhJg
FwlRRmciLNhetGPxF9vMmBzC9ff9D9b9aNtyW73lJtB2N0d9Bz1NIMxUboCyrUm0

Bug#943302: marked as done (zsnapd: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 22 Sep 2020 23:22:04 +
with message-id 
and subject line Bug#943302: fixed in zsnapd 0.8.11h-3
has caused the Debian Bug report #943302,
regarding zsnapd: Python2 removal in sid/bullseye
to be marked as done.

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

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


-- 
943302: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943302
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zsnapd
Version: 0.8.9a-1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests (the specific reason can be found searching this
source package in
https://people.debian.org/~morph/mass-bug-py2removal_take2.txt ).
Please stop using Python2, and fix this issue by one of the following
actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: zsnapd
Source-Version: 0.8.11h-3
Done: Matthew Grant 

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

Debian distribution maintenance software
pp.
Matthew Grant  (supplier of updated zsnapd 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: Wed, 23 Sep 2020 10:58:27 +1200
Source: zsnapd
Architecture: source
Version: 0.8.11h-3
Distribution: unstable
Urgency: medium
Maintainer: Matthew Grant 
Changed-By: Matthew Grant 
Closes: 919595 943302
Changes:
 zsnapd (0.8.11h-3) unstable; urgency=medium
 .
   * Really fix bug about being in wrong section. (Closes: #943302)
   * Source only upload. (Closes: #919595)
Checksums-Sha1:
 6d3e0edb7a9f9b0443bc8308cf7c965310ea19cb 1873 zsnapd_0.8.11h-3.dsc
 8d749f12eec3e731bf2f04d39c5278025b37adaf 30505 zsnapd_0.8.11h.orig.tar.gz
 91d66a18a5daa081ff3ff23ef7cb00b64dcbb928 7232 zsnapd_0.8.11h-3.debian.tar.xz
 4d6737b60b2f96fea05db9746e0ddfcb80f7fade 6959 zsnapd_0.8.11h-3_amd64.buildinfo
Checksums-Sha256:
 b9d8783d9338839e789310a01eee4f8416dfb418355f0233ba726dee1f910200 1873 
zsnapd_0.8.11h-3.dsc
 9d94872008b37a821ccdb9eb50d5eb9db8f1c4aa00d31f38e14f1eaf7d4f8b84 30505 
zsnapd_0.8.11h.orig.tar.gz
 3cb220289d4b3c0d31e8ca789ccfc04f2c8559fb037e7bf3274cc9ce2126da10 7232 
zsnapd_0.8.11h-3.debian.tar.xz
 4c82e4d66f2d6ee77461ec844b5f5b11f320dff035e7a4f15f13239a62fa7d5d 6959 
zsnapd_0.8.11h-3_amd64.buildinfo
Files:
 

Bug#970759: normaliz: Wrong e-mail address in Maintainer field

[Alex Muntada]

Package: normaliz
Version: 3.8.5+ds-1
Severity: serious
Usertags: alioth-lists.debian.org
X-Debbugs-Cc: calcu...@rezozer.net

The Maintainer of this package uses the alioth-lists.debian.org
domain, which does not exist. This breaks policy §3.3[1] that
requires a working e-mail address. You should be using the
alioth-lists.debian.net domain instead.

After reporting[2] the issue to debian-science-maintainers list,
I'm filing this bug as suggested[3] there.

Cheers,
Alex

  [1] https://www.debian.org/doc/debian-policy/ch-binary.html#s-maintainer
  [2] 
https://alioth-lists.debian.net/pipermail/debian-science-maintainers/2020-September/085266.html
  [3] 
https://alioth-lists.debian.net/pipermail/debian-science-maintainers/2020-September/085350.html

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁   Alex Muntada 
  ⢿⡄⠘⠷⠚⠋   Debian Developer  log.alexm.org
  ⠈⠳⣄



signature.asc
Description: PGP signature

Bug#970727: marked as done (python-magcode-core needs a source-only upload.)

[Debian Bug Tracking System]

Your message dated Tue, 22 Sep 2020 23:05:23 +
with message-id 
and subject line Bug#970727: fixed in python-magcode-core 1.5.4-3
has caused the Debian Bug report #970727,
regarding python-magcode-core needs a source-only upload.
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.)


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

Source: python-magcode-core
Version: 1.5.4-2
Severity: serious

The release team have decreed that non-buildd binaries can no longer migrate to 
testing, please make a source-only
upload so your package can migrate.
--- End Message ---
--- Begin Message ---
Source: python-magcode-core
Source-Version: 1.5.4-3
Done: Matthew Grant 

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

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

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

Debian distribution maintenance software
pp.
Matthew Grant  (supplier of updated python-magcode-core 
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: Wed, 23 Sep 2020 10:47:34 +1200
Source: python-magcode-core
Architecture: source
Version: 1.5.4-3
Distribution: unstable
Urgency: medium
Maintainer: Matthew Grant 
Changed-By: Matthew Grant 
Closes: 970727
Changes:
 python-magcode-core (1.5.4-3) unstable; urgency=medium
 .
   * Source code only upload. (Closes: #970727)
Checksums-Sha1:
 c445a1b8f370affaab10daff2ff0e04c087d7399 2020 python-magcode-core_1.5.4-3.dsc
 89270eb024ea70dc034b5c521a69deb1f5e890c8 50211 
python-magcode-core_1.5.4.orig.tar.gz
 a2fabafe58009b4ab2bb7ad679cd0ea4a0cdc39d 4788 
python-magcode-core_1.5.4-3.debian.tar.xz
 ad2d1097848885a87fcc7aaab42105222f7b9bc4 6525 
python-magcode-core_1.5.4-3_amd64.buildinfo
Checksums-Sha256:
 777d9d176d64625332a36f1dda893b98f6e049fd275b6d1617efc963b2932258 2020 
python-magcode-core_1.5.4-3.dsc
 00468a8e1a77a32bcc15e4291fcc1636544ff3d7975f033003968c991794d9ba 50211 
python-magcode-core_1.5.4.orig.tar.gz
 c6f271579c1786c9b8d061d4a48cc46bf896d9823b2d6ea8ea090c3bd71f428f 4788 
python-magcode-core_1.5.4-3.debian.tar.xz
 5876177400ee12b0a011b2466b2d0a3beed4bff18dfb55246c4f502c6a0d749b 6525 
python-magcode-core_1.5.4-3_amd64.buildinfo
Files:
 fb59cdf5f48c754b683d9c124bf4be84 2020 python optional 
python-magcode-core_1.5.4-3.dsc
 0adacaefe9f359b71982eab5e5446d2f 50211 python optional 
python-magcode-core_1.5.4.orig.tar.gz
 9e7f7e727cf165a41292bc2d0d72a59d 4788 python optional 
python-magcode-core_1.5.4-3.debian.tar.xz
 97d3e2259e0523244f85e18f934be1d9 6525 python optional 
python-magcode-core_1.5.4-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJKBAEBCAA0FiEEwaHD8RNdvgk2cFzjxE5f/BM1w6IFAl9qf2gWHG1hdHRAbWF0
dGdyYW50Lm5ldC5uegAKCRDETl/8EzXDoqMTD/9QlBoGReiydnVbN17sJuuLS0bu
q8hUixAvLFA+0uO3WzfAzUm0XmUnztePRrDGzuSbu00rTqELMIX3hN2c1iD5CDb/
Ar2+19AQirvWbGegEliD/UgAalLxGwOUEwpiBWhR8yzgSZpn6iv8ueu/lzXxw6YM
SJA8g5X7KtTvS/EZMfn5/fjFXs6KCBMet+FRAri2tQesfcz/4tnsQxagCY+K+Alg
ljg6rdEQDY1nmgm7lTGg3HchiAjHKfDBtsyvVvJBDpiQNh4U9id57npywNozPo85
ADJOt0FztZM8HpyZHBGpDBHv9+k+yVqReD8W7N7ZCuaZh4nFl3lXz33carmNsXu4
SJZdePH9ReuinOOvJP+wJ3GZo8MVWHNTPKzrpbPbnh1B6Nu1RHCf7Pmq4r9VLLOF
i5HMylii/hNK8SUcyEJTvasugyVZmkoPOosCi1IFLjd0UW3eSnsTt5slM2xhrGHM
gvyzcH69SkQEo5vnWqA1l3wUqjDa7COLTIYILPGDGIr8LCOAMosww1ESf0+9p6Hj
IQwuaM9FH7A/n/v6IOBpqj+CPCQ1MQ4pL9dfSctaJZwUDzr7muSt2fQplPaee6zx
c4AC5DIot8jOuPrR1lQBPzZSKbGGpmlIntJz6S4vZ93PhXXV4FceZBJw4s/pFOw/
j0YN95uVsJLR5Zw7jA==
=NTOb
-END PGP SIGNATURE End Message ---

Bug#970758: mpfi: Wrong e-mail address in Maintainer field

[Alex Muntada]

Package: mpfi
Version: 1.5.3+ds-4
Severity: serious
Usertags: alioth-lists.debian.org
X-Debbugs-Cc: calcu...@rezozer.net, lfou...@debian.org

The Maintainer of this package uses the alioth-lists.debian.org
domain, which does not exist. This breaks policy §3.3[1] that
requires a working e-mail address. You should be using the
alioth-lists.debian.net domain instead.

After reporting[2] the issue to debian-science-maintainers list,
I'm filing this bug as suggested[3] there.

Cheers,
Alex

  [1] https://www.debian.org/doc/debian-policy/ch-binary.html#s-maintainer
  [2] 
https://alioth-lists.debian.net/pipermail/debian-science-maintainers/2020-September/085266.html
  [3] 
https://alioth-lists.debian.net/pipermail/debian-science-maintainers/2020-September/085350.html

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁   Alex Muntada 
  ⢿⡄⠘⠷⠚⠋   Debian Developer  log.alexm.org
  ⠈⠳⣄



signature.asc
Description: PGP signature

Bug#970757: gap-scscp: Wrong e-mail address in Maintainer field

[Alex Muntada]

Package: gap-scscp
Version: 2.3.1+ds-1
Severity: serious
Usertags: alioth-lists.debian.org
X-Debbugs-Cc: calcu...@rezozer.net

The Maintainer of this package uses the alioth-lists.debian.org
domain, which does not exist. This breaks policy §3.3[1] that
requires a working e-mail address. You should be using the
alioth-lists.debian.net domain instead.

After reporting[2] the issue to debian-science-maintainers list,
I'm filing this bug as suggested[3] there.

Cheers,
Alex

  [1] https://www.debian.org/doc/debian-policy/ch-binary.html#s-maintainer
  [2] 
https://alioth-lists.debian.net/pipermail/debian-science-maintainers/2020-September/085266.html
  [3] 
https://alioth-lists.debian.net/pipermail/debian-science-maintainers/2020-September/085350.html

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁   Alex Muntada 
  ⢿⡄⠘⠷⠚⠋   Debian Developer  log.alexm.org
  ⠈⠳⣄



signature.asc
Description: PGP signature

Bug#970755: gap-guava: Wrong e-mail address in Maintainer field

[Alex Muntada]

Package: gap-guava
Version: 3.15+ds-2
Severity: serious
Usertags: alioth-lists.debian.org
X-Debbugs-Cc: calcu...@rezozer.net

The Maintainer of this package uses the alioth-lists.debian.org
domain, which does not exist. This breaks policy §3.3[1] that
requires a working e-mail address. You should be using the
alioth-lists.debian.net domain instead.

After reporting[2] the issue to debian-science-maintainers list,
I'm filing this bug as suggested[3] there.

Cheers,
Alex

  [1] https://www.debian.org/doc/debian-policy/ch-binary.html#s-maintainer
  [2] 
https://alioth-lists.debian.net/pipermail/debian-science-maintainers/2020-September/085266.html
  [3] 
https://alioth-lists.debian.net/pipermail/debian-science-maintainers/2020-September/085350.html

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁   Alex Muntada 
  ⢿⡄⠘⠷⠚⠋   Debian Developer  log.alexm.org
  ⠈⠳⣄



signature.asc
Description: PGP signature

Bug#970756: gap-openmath: Wrong e-mail address in Maintainer field

[Alex Muntada]

Package: gap-openmath
Version: 11.5.0+ds-1
Severity: serious
Usertags: alioth-lists.debian.org
X-Debbugs-Cc: calcu...@rezozer.net

The Maintainer of this package uses the alioth-lists.debian.org
domain, which does not exist. This breaks policy §3.3[1] that
requires a working e-mail address. You should be using the
alioth-lists.debian.net domain instead.

After reporting[2] the issue to debian-science-maintainers list,
I'm filing this bug as suggested[3] there.

Cheers,
Alex

  [1] https://www.debian.org/doc/debian-policy/ch-binary.html#s-maintainer
  [2] 
https://alioth-lists.debian.net/pipermail/debian-science-maintainers/2020-September/085266.html
  [3] 
https://alioth-lists.debian.net/pipermail/debian-science-maintainers/2020-September/085350.html

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁   Alex Muntada 
  ⢿⡄⠘⠷⠚⠋   Debian Developer  log.alexm.org
  ⠈⠳⣄



signature.asc
Description: PGP signature

Bug#970754: e-antic: Wrong e-mail address in Maintainer field

[Alex Muntada]

Package: e-antic
Version: 0.1.5+ds-2.1
Severity: serious
Usertags: alioth-lists.debian.org
X-Debbugs-Cc: plugw...@raspbian.org, calcu...@rezozer.net

The Maintainer of this package uses the alioth-lists.debian.org
domain, which does not exist. This breaks policy §3.3[1] that
requires a working e-mail address. You should be using the
alioth-lists.debian.net domain instead.

After reporting[2] the issue to debian-science-maintainers list,
I'm filing this bug as suggested[3] there.

Cheers,
Alex

  [1] https://www.debian.org/doc/debian-policy/ch-binary.html#s-maintainer
  [2] 
https://alioth-lists.debian.net/pipermail/debian-science-maintainers/2020-September/085266.html
  [3] 
https://alioth-lists.debian.net/pipermail/debian-science-maintainers/2020-September/085350.html

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁   Alex Muntada 
  ⢿⡄⠘⠷⠚⠋   Debian Developer  log.alexm.org
  ⠈⠳⣄



signature.asc
Description: PGP signature

Bug#970753: apertium-ind-zlm: Wrong e-mail address in Maintainer field

[Alex Muntada]

Package: apertium-ind-zlm
Version: 0.1.2-2
Severity: serious
Usertags: alioth-lists.debian.org
X-Debbugs-Cc: kar...@debian.org, t...@didriksen.cc

The Maintainer of this package uses the alioth-lists.debian.org
domain, which does not exist. This breaks policy §3.3[1] that
requires a working e-mail address. You should be using the
alioth-lists.debian.net domain instead.

After reporting[2] the issue to debian-science-maintainers list,
I'm filing this bug as suggested[3] there.

Cheers,
Alex

  [1] https://www.debian.org/doc/debian-policy/ch-binary.html#s-maintainer
  [2] 
https://alioth-lists.debian.net/pipermail/debian-science-maintainers/2020-September/085266.html
  [3] 
https://alioth-lists.debian.net/pipermail/debian-science-maintainers/2020-September/085350.html

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁   Alex Muntada 
  ⢿⡄⠘⠷⠚⠋   Debian Developer  log.alexm.org
  ⠈⠳⣄



signature.asc
Description: PGP signature

Processed: Bug#963637 marked as pending in rdkit

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #963637 [src:rdkit] rdkit: FTBFS with Sphinx 3.1: ! LaTeX Error: Too deeply 
nested.
Added tag(s) pending.

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

Processed: Bug#964656 marked as pending in rdkit

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #964656 [src:rdkit] rdkit: FTBFS: elog.h:224:34: error: format not a string 
literal and no format arguments [-Werror=format-security]
Added tag(s) pending.

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

Bug#964656: marked as pending in rdkit

[Michael Banck]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/debichem-team/rdkit/-/commit/36dae00f103235e4c35de6afbd0f6c7f41ec2f74


* debian/patches/postgres_compile_fixes.patch: New patch, fixes compile
errors on PostgreSQL-12 (Closes: #964656).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/964656

Bug#963637: marked as pending in rdkit

[Michael Banck]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/debichem-team/rdkit/-/commit/77291d6e55566f0d9e8a91d5ca9887ad15b9490c


* debian/patches/sphinx_compile_fixes.patch: New patch, fixes build failures
with Sphinx-3.1 (Closes: #963637).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/963637

Bug#970747: liblinphone-dev: should depend on liblinphone++10

[Andres Salomon]

Package: liblinphone-dev
Version: 4.4.0-1
Severity: serious

While building linphone-desktop, I hit the following build error:


CMake Error at /usr/share/LinphoneCxx/cmake/LinphoneCxxTargets.cmake:70 
(message):

 The imported target "linphone++" references the file

"/usr/lib/x86_64-linux-gnu/liblinphone++.so.10"

 but this file does not exist.  Possible reasons include:

 * The file was deleted, renamed, or moved to another location.

 * An install or uninstall procedure did not complete successfully.

 * The installation package was faulty and contained

"/usr/share/LinphoneCxx/cmake/LinphoneCxxTargets.cmake"

 but not all the files it references.

Call Stack (most recent call first):
 /usr/share/LinphoneCxx/cmake/LinphoneCxxConfig.cmake:33 (include)
 CMakeLists.txt:165 (find_package)



dilinger@e7470:/home/dev/linphone-desktop-4.2.2$ dpkg -S 
/usr/lib/x86_64-linux-gnu/liblinphone*so

liblinphone-dev: /usr/lib/x86_64-linux-gnu/liblinphone++.so
liblinphone-dev: /usr/lib/x86_64-linux-gnu/liblinphone.so

dilinger@e7470:/home/dev/linphone-desktop-4.2.2$ ls -lh 
/usr/lib/x86_64-linux-gnu/liblinphone*so
lrwxrwxrwx 1 root root 19 Aug 31 19:03 
/usr/lib/x86_64-linux-gnu/liblinphone++.so -> liblinphone++.so.10
lrwxrwxrwx 1 root root 17 Aug 31 19:03 
/usr/lib/x86_64-linux-gnu/liblinphone.so -> liblinphone.so.10


dilinger@e7470:/home/dev/linphone-desktop-4.2.2$ ls -lh 
/usr/lib/x86_64-linux-gnu/liblinphone*so.10
-rw-r--r-- 1 root root 3.6M Aug 31 19:03 
/usr/lib/x86_64-linux-gnu/liblinphone.so.10



As you can see, liblinphone++.so.10 is missing. It seems like
liblinphone-dev should depend on both liblinphone10 AND
liblinphone++10, but right now it only depends on
liblinphone10.

Bug#964621: marked as done (fakeroot: statx function not wrapped, causing FTBFS)

[Debian Bug Tracking System]

Your message dated Tue, 22 Sep 2020 21:19:29 +
with message-id 
and subject line Bug#964621: fixed in fakeroot 1.25-1
has caused the Debian Bug report #964621,
regarding fakeroot: statx function not wrapped, causing FTBFS
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.)


-- 
964621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964621
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fakeroot
Version: 1.24-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[5]: Entering directory '/<>/obj-sysv/test'
> FAIL: t.chmod_dev
> PASS: t.cp-a
> PASS: t.echoarg
> PASS: t.falsereturn
> FAIL: t.mknod
> PASS: t.no_ld_preload
> PASS: t.no_ld_preload_link
> PASS: t.option
> PASS: t.tar
> FAIL: t.touchinstall
> PASS: t.truereturn
> PASS: t.xattr
> 
> Testsuite summary for fakeroot 1.24
> 
> # TOTAL: 12
> # PASS:  9
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  3
> # XPASS: 0
> # ERROR: 0
> 
> See test/test-suite.log
> Please report to cl...@debian.org
> 
> make[5]: *** [Makefile:549: test-suite.log] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/07/09/fakeroot_1.24-1_unstable.log

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

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

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

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

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

Debian distribution maintenance software
pp.
Clint Adams  (supplier of updated fakeroot package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 22 Sep 2020 16:58:02 -0400
Source: fakeroot
Architecture: source
Version: 1.25-1
Distribution: unstable
Urgency: medium
Maintainer: Clint Adams 
Changed-By: Clint Adams 
Closes: 940056 962413 964621 968868
Changes:
 fakeroot (1.25-1) unstable; urgency=medium
 .
   * test/t.xattr: adapt to changed getcap output.
   * Wrap statx().  closes: #940056, #964621, #968868.
   * Updated Portuguese man page translation from Américo Monteiro.  closes: 
#962413.
Checksums-Sha1:
 e3e7fa86a91adea35a5dad90a0403cae6ecbf2ff 1960 fakeroot_1.25-1.dsc
 3c9ba23511b21b44e6793058359956edd9f5 126853 fakeroot_1.25.orig.tar.gz
 1c192ea93d03686d81e1db29bec55cce37e5da14 239864 fakeroot_1.25-1.debian.tar.xz
 29fdd72b2323f85a71148a2d54ae36be35acf002 5595 fakeroot_1.25-1_source.buildinfo
Checksums-Sha256:
 a5f08f17f04cdea1f0a9ca7367c93894a3e03860d17bfc4e45379eded48b2e63 1960 
fakeroot_1.25-1.dsc
 fc59597f508263c46a321bc33429eb07420f16533b33367b9e7a221adb1491da 126853 
fakeroot_1.25.orig.tar.gz
 a31b4ceb54ff5668627021e020782b0c25e2c8cbb43b046eb472935c40b56f75 239864 
fakeroot_1.25-1.debian.tar.xz
 20af14ce3445e7b2bac525ddcb042810198e87aadddce29db9c129fa08cf7021 5595 
fakeroot_1.25-1_source.buildinfo
Files:
 7b92cb6981875c332f642d188d67d5e0 1960 utils optional fakeroot_1.25-1.dsc
 fdc40bffdcf796677dbe3a169895ba98 126853 utils optional 
fakeroot_1.25.orig.tar.gz
 554578a7f0f98d632ff2325a363fb075 239864 utils optional 
fakeroot_1.25-1.debian.tar.xz
 cbe62f970e39e3235529196498e1e8c4 5595 utils optional 
fakeroot_1.25-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEdYHsh0BT5sgHeRubVZIzHhmdOKgFAl9qZcIRHGNsaW50QGRl
Ymlhbi5vcmcACgkQVZIzHhmdOKjoQA//bwdLXrKXygNwfRn7sIsbb5/ylwmtPQ5K

Bug#855541: purple-matrix: Not ready for release yet

[Alex ARNAUD]

On Mon, 20 Feb 2017 00:12:35 +0100 Kurt Roeckx  wrote:
> Package: purple-matrix
> Version: 0.0.0+git20170105-1
> Severity: serious
>
> Hi,
>
> I think this version shouldn't be shipped with the next
> release. Like the description says, it's "somewhat alpha".
>
> It works some times, but then stops working, it crashes,
> and so on.

I've used the package purple-matrix on Debian 10 since at least 6 months 
through Pidgin. It's not a perfect tool, have issues but in my opinion 
it is usable. Sometimes purple-matrix is disconnected or makes Pidgin to 
crash but it's quite rare. It's sufficient to restart Pidgin to make it 
working again.


I have two points why I think we should have it into next stable:

 * This is very difficult for a stable user to use purple-matrix. In my
   case, I have had to rebuilt the package due to dependencies and it's
   clearly something not easy for all.
 * As a visual-impaired person, purple-matrix through Pidgin is the
   most accessible Matrix client I've used.


There are still reasons why we would like to keep it in unstable:

 * There are no commits in 2020
 * The project doesn't publish new release and "just" push commits


In my humble opinion, the drawbacks of keeping it to unstable are more 
important.



@Kurt: I let you decide if you prefer to keep close or not but since the 
creation of this issue in 2017 many commits come to the project.



Thanks in advance.

Bug#964621: fakeroot: statx function not wrapped, causing FTBFS

[jhcha54008]

Le lundi 21 septembre à 23h 11mn 37s (+), Clint Adams a écrit :
> On Mon, Sep 21, 2020 at 12:48:25PM +0200, jhcha54008 wrote:
> > should this bug be merged with #940056 and #968868 ?
> 
> If statx is the only reason for the failures.

Hi,

Oops, you're right : the test 't.xattr' keeps failing but statx
is not the culprit. 
It seems that the output format of getcap has changed (if I 
understand correctly) : the test code expects
 
$tmp/foo = cap_net_raw+ep

but gets instead

$tmp/foo cap_net_raw=ep

However, one may build successfully version 1.24.1-1 if t.xattr is 
corrected and statx is wrapped.
(actually, I tested with dpkg-buildpackage in a sid chroot on 
amd64/stretch and add libfakestatx.so.0.0 from [1] to LD_PRELOAD
in fakeroot)

I hope it will help to find a solution !

Regards,
JH Chatenet

[1] : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940056#10

Bug#970741: rhythmbox build-depends unsatisfiable in testing

[peter green]

Source: rhythmbox
Version: 3.4.4-2
Severity: serious

rhythmbox build-depends on gstreamer1.0-doc which is no longer built by the 
gstreamer1.0 source package.
It still seems to be present in unstable as a cruft package, but is completely 
gone from testing.

Bug#970740: farstream-0.2 build-depends unsatisfiable in testing

[peter green]

Source: farstream-0.2
Version: 0.2.8-5
Severity: serious

farstream-0.2 build-depends on gstreamer1.0-doc which is no longer built by the 
gstreamer1.0 source package.
It still seems to be present in unstable as a cruft package, but is completely 
gone from testing.

Bug#970739: clutter-gst-3.0 build-depends unsatisfiable in testing

[peter green]

Source: clutter-gst-3.0
Version: 3.0.27-1
Severity: serious

clutter-gst-3.0 build-depends on gstreamer1.0-doc which is no longer built by 
the gstreamer1.0 source package.
It still seems to be present in unstable as a cruft package, but is completely 
gone from testing.

Bug#969493: marked as done (src:nanook: fails to migrate to testing for too long: maintainer built arch:all binaries)

[Debian Bug Tracking System]

Your message dated Tue, 22 Sep 2020 19:03:31 +
with message-id 
and subject line Bug#969493: fixed in nanook 1.33+dfsg-2.1
has caused the Debian Bug report #969493,
regarding src:nanook: fails to migrate to testing for too long: maintainer 
built arch:all binaries
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.)


-- 
969493: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969493
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nanook
Version: 1.33+dfsg-1
Severity: serious
Control: close -1 1.33+dfsg-2
Tags: sid bullseye pending
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:nanook in its
current version in unstable has been trying to migrate for 59 days [2].
Hence, I am filing this bug.

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

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

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

Your package is only blocked because the arch:all binary package(s)
aren't built on a buildd. Unfortunately the Debian infrastructure
doesn't allow arch:all packages to be properly binNMU'ed. Normally I
would do a no-changes source-only upload to DELAYED/15, closing this
bug, but I'm very limited on Internet at the moment.

Paul

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




signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: nanook
Source-Version: 1.33+dfsg-2.1
Done: Paul Gevers 

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 07 Sep 2020 20:12:17 +0200
Source: nanook
Architecture: source
Version: 1.33+dfsg-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Paul Gevers 
Closes: 969493
Changes:
 nanook (1.33+dfsg-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * source only upload to enable migration (Closes: #969493)
Checksums-Sha1:
 9d397df1647c9ddd2d5a3cf2d5063051d942a773 1856 nanook_1.33+dfsg-2.1.dsc
 3eb759819fcb8d82ac693621fc78ebf5bd7dee5d 1817928 
nanook_1.33+dfsg-2.1.debian.tar.xz
Checksums-Sha256:
 fb1b5a6726b06052b03e4c07732f9621fcd3da3094ea16e9200209baf7920af8 1856 
nanook_1.33+dfsg-2.1.dsc
 2ef1a44506d31b6e398970736a1371851cf1295b3d815ae16ea18375235a63b2 1817928 
nanook_1.33+dfsg-2.1.debian.tar.xz
Files:
 8d831f32434167b2b1be2247235c0d8d 1856 science optional nanook_1.33+dfsg-2.1.dsc
 03b0a8cac832d5d98e3bccd6d89377e9 1817928 science optional 
nanook_1.33+dfsg-2.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl9WeCEACgkQnFyZ6wW9
dQoTfQgAzJ4YYpnIl22mbAFLoU5NVlCjljeQw3k+Sen2FDg9SXPs986NjYidnXPG
7zPaONB9/5Lc8CgRwPilypVD6jeN8NS+9TdVblStncsgsTkjfhPoP/LgfW149N8m
K203vpKaJuFg/XXLUKq3hxkMdWFKMvTVJSoFwIZ5O3QskR4ARtCPCUh2JgH638Lr
Zu4SjOWcky2xtrhtHHLtoaEc0hdxK8oVMHmTgesVyxcjTWwyjUqPYKqB4Br/Mnxx
7gAX9UBsnSPobYJc81hYVfkZbbprGRpoy+FcRGro3wAzmIR2KBwWN63UyqlNXru1

Bug#970735: mpdecimal FTBFS in bullseye: symbol differences

[Helmut Grohne]

Source: mpdecimal
Version: 2.5.0-4
Severity: serious
Tags: ftbfs patch
User: helm...@debian.org
Usertags: rebootstrap

mpdecimal has a number of symbols whose appearance is quite dependent on
the precise compiler version. These tend to be symbols for inlined
functions and template instantiations. This presently causes FTBFS in
bullseye, e.g.:

https://tests.reproducible-builds.org/debian/rbuild/bullseye/amd64/mpdecimal_2.5.0-4.rbuild.log.gz
https://tests.reproducible-builds.org/debian/rbuild/bullseye/arm64/mpdecimal_2.5.0-4.rbuild.log.gz
https://tests.reproducible-builds.org/debian/rbuild/bullseye/armhf/mpdecimal_2.5.0-4.rbuild.log.gz

This happens, because the bullseye toolchain was not exactly the same as
the unstable toolchain at the time of the build and the compiler decided
to instantiate symbols differently. Instead of changing symbols back and
forth, I suggest simply marking them as optional.

Beyond this, you can use arch-bits=32 and arch-bits=64 to remove the
need for interpolating the symbol file since that feature is now present
in oldstable.

I'm attaching a patch for the optional stuff for your convenience.

Helmut
diff --minimal -Nru mpdecimal-2.5.0/debian/changelog 
mpdecimal-2.5.0/debian/changelog
--- mpdecimal-2.5.0/debian/changelog2020-08-06 15:33:23.0 +0200
+++ mpdecimal-2.5.0/debian/changelog2020-09-22 19:35:08.0 +0200
@@ -1,3 +1,10 @@
+mpdecimal (2.5.0-4.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Mark optional symbols as optional. (Closes: #-1)
+
+ -- Helmut Grohne   Tue, 22 Sep 2020 19:35:08 +0200
+
 mpdecimal (2.5.0-4) unstable; urgency=medium
 
   * Update symbols files.
diff --minimal -Nru mpdecimal-2.5.0/debian/libmpdec.symbols.in 
mpdecimal-2.5.0/debian/libmpdec.symbols.in
--- mpdecimal-2.5.0/debian/libmpdec.symbols.in  2020-08-06 15:33:23.0 
+0200
+++ mpdecimal-2.5.0/debian/libmpdec.symbols.in  2020-09-22 19:35:08.0 
+0200
@@ -416,22 +416,22 @@
  _ZN7decimal9UnderflowD2Ev@Base 2.5
  _ZN7decimallsERSoRKNS_7ContextE@Base 2.5
  _ZN7decimallsERSoRKNS_7DecimalE@Base 2.5
- 
(arch=ia64)_ZN9__gnu_cxx12__to_xstringINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEcEET_PFiPT0_mPKS8_PvEmSB_z@Base
 2.5
+ 
(optional=templinst)_ZN9__gnu_cxx12__to_xstringINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEcEET_PFiPT0_mPKS8_PvEmSB_z@Base
 2.5
  _ZNK7decimal10ValueError4whatEv@Base 2.5
  _ZNK7decimal11MallocError4whatEv@Base 2.5
  _ZNK7decimal12RuntimeError4whatEv@Base 2.5
  _ZNK7decimal16DecimalException4whatEv@Base 2.5
  _ZNK7decimal7Context4reprB5cxx11Ev@Base 2.5
  _ZNK7decimal7Decimal4reprB5cxx11Eb@Base 2.5
- (arch=!ia64 !ppc64el !kfreebsd-amd64 
!kfreebsd-i386)_ZNK7decimal7Decimal6to_sciB5cxx11Eb@Base 2.5
- 
(arch=ia64)_ZNSt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE2EE10_M_releaseEv@Base
 2.5
- (arch=!armel 
!riscv64)_ZNSt19_Sp_counted_deleterIPKcZN7decimal4util9shared_cpES1_EUlS1_E_SaIvELN9__gnu_cxx12_Lock_policyE2EE10_M_destroyEv@Base
 2.5
- (arch=!armel 
!riscv64)_ZNSt19_Sp_counted_deleterIPKcZN7decimal4util9shared_cpES1_EUlS1_E_SaIvELN9__gnu_cxx12_Lock_policyE2EE10_M_disposeEv@Base
 2.5
- (arch=!armel 
!riscv64)_ZNSt19_Sp_counted_deleterIPKcZN7decimal4util9shared_cpES1_EUlS1_E_SaIvELN9__gnu_cxx12_Lock_policyE2EE14_M_get_deleterERKSt9type_info@Base
 2.5
- (arch=!armel 
!riscv64)_ZNSt19_Sp_counted_deleterIPKcZN7decimal4util9shared_cpES1_EUlS1_E_SaIvELN9__gnu_cxx12_Lock_policyE2EED0Ev@Base
 2.5
- (arch=!armel 
!riscv64)_ZNSt19_Sp_counted_deleterIPKcZN7decimal4util9shared_cpES1_EUlS1_E_SaIvELN9__gnu_cxx12_Lock_policyE2EED1Ev@Base
 2.5
- 
(arch=ia64)_ZNSt19_Sp_counted_deleterIPKcZN7decimal4util9shared_cpES1_EUlS1_E_SaIvELN9__gnu_cxx12_Lock_policyE2EED2Ev@Base
 2.5
- 
(arch=ia64)_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE12_M_constructIPcEEvT_S7_St20forward_iterator_tag@Base
 2.5
+ (optional=inline)_ZNK7decimal7Decimal6to_sciB5cxx11Eb@Base 2.5
+ 
(optional=templinst)_ZNSt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE2EE10_M_releaseEv@Base
 2.5
+ 
(optional=templinst)_ZNSt19_Sp_counted_deleterIPKcZN7decimal4util9shared_cpES1_EUlS1_E_SaIvELN9__gnu_cxx12_Lock_policyE2EE10_M_destroyEv@Base
 2.5
+ 
(optional=templinst)_ZNSt19_Sp_counted_deleterIPKcZN7decimal4util9shared_cpES1_EUlS1_E_SaIvELN9__gnu_cxx12_Lock_policyE2EE10_M_disposeEv@Base
 2.5
+ 
(optional=templinst)_ZNSt19_Sp_counted_deleterIPKcZN7decimal4util9shared_cpES1_EUlS1_E_SaIvELN9__gnu_cxx12_Lock_policyE2EE14_M_get_deleterERKSt9type_info@Base
 2.5
+ 
(optional=templinst)_ZNSt19_Sp_counted_deleterIPKcZN7decimal4util9shared_cpES1_EUlS1_E_SaIvELN9__gnu_cxx12_Lock_policyE2EED0Ev@Base
 2.5
+ 
(optional=templinst)_ZNSt19_Sp_counted_deleterIPKcZN7decimal4util9shared_cpES1_EUlS1_E_SaIvELN9__gnu_cxx12_Lock_policyE2EED1Ev@Base
 2.5
+ 
(optional=templinst)_ZNSt19_Sp_counted_deleterIPKcZN7decimal4util9shared_cpES1_EUlS1_E_SaIvELN9__gnu_cxx12_Lock_policyE2EED2Ev@Base
 2.5
+ 

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

[Shayan Doust]

Hello Andreas,

Yes, this does seem like a local issue to r-cran-rcppparallel.

tbb and variants are loaded when r-cran-rcppparallel is imported, as seen in
[hooks.R]. The function of interest is 'tbbLibPath()', which seems to depict tbb
library path.

With some more investigation, you can see this function within [build.R]. You
can see for all supported platforms apart from Windows and Sparc systems, it
seems like it expects the library to be situated under lib/ (due to the first
argument used within system.file()).

I'll try to write a simple patch for this hook file. For a Debian package, this
assumption for library location is plain wrong.

Kind regards,
Shayan Doust


[hooks.R]:
https://github.com/RcppCore/RcppParallel/blob/b216ba27dcbd3c523932bd918b6dd0b1b08d3566/R/hooks.R#L8
[build.R]:
https://github.com/RcppCore/RcppParallel/blob/b216ba27dcbd3c523932bd918b6dd0b1b08d3566/R/build.R#L66

On Tue, 8 Sep 2020 20:32:53 +0200 Andreas Tille  wrote:
> Control: tags -1 help
> 
> Hi,
> 
> any help why TBB is not found?  I think this issue is actually causes by
> r-cran-rcppparallel since the code copy of libtbb was removed there -
> but it seems to not provide the Debian packaged lib properly.
> 
> Kind regards
> 
> Andreas.
> 
> -- 
> http://fam-tille.de
> 
> 


0x6D7D441919D02395.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

Bug#970717: kubernetes: abuse of "embedded code copies" | hundreds of vendored libraries

[Janos LENART]

Hi Elana,

Thank you for looking into this.

I've believed the vendor/ directory is thoroughly vetted, and I have also
checked every single directory, sometimes even files. I do not think there
is a DFSG issue here. Dmitry does not agree with the fact that vendor/ is
boundled in the Debian packages. It is not actually against the Debian
Policy either, only his interpretation of it. There was a flamewar on this
on debian-devel. Long story short, Dmitry did not maintain and did not want
to maintain the package, I've adopted it and repackaged it boundling the
vendor/ directory, Dmitry was upset because of the technical disagreement.
Nobody with actual powers had a problem with this. Marking this as a
serious bug is his latest attempt at sabotage.

Granted, the current solution is not ideal.

Janos

On Tue, Sep 22, 2020 at 6:09 PM Elana Hashman  wrote:

> On Tue, Sep 22, 2020 at 08:56:25PM +1000, Dmitry Smirnov wrote:
> >
> > As discussed in debian-devel, Kubernetes package abuses Debian practices
> > and Golang team policies by needlessly vendoring hundreds(!) of
> libraries,
> > most of which are available in Debian.
> >
> > For a complex package like Kubernetes, _some_ strategic vendoring would
> be
> > understandable for practical reasons. But not everything.
> >
> > Maintainer circumvented packaging practices and introduced re-packaged
> > Kubernetes in a state that would have never been accepted by ftp-masters.
> >
> > Please consider removing redundant libraries from "vendor".
> > In the current state, the package is unsuitable for "stable".
>
> It's not entirely clear to me if the policy concerns are around
> licensing compliance or simply the volume of vendored dependencies.
>
>
> Wearing my Kubernetes SIG Chair/upstream hat:
>
> I believe that the license compliance of everything in vendor/ has been
> thoroughly vetted, but that information may not have been adequately
> surfaced for downstream projects to use. In this case, any violations
> are surface-level/paperwork as opposed to fundamental issues with DFSG
> compliance. I've requested that upstream better surfaces this
> information in order to be able to build Kubernetes in a
> policy-compliant way in Debian:
> https://github.com/kubernetes/kubernetes/issues/94976
>
> Thanks,
>
> - e
>


-- 
LÉNÁRT, János

Processed: your mail

[Debian Bug Tracking System]

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

> severity 970717 normal
Bug #970717 [src:kubernetes] kubernetes: abuse of "embedded code copies" | 
hundreds of vendored libraries
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#970717: kubernetes: abuse of "embedded code copies" | hundreds of vendored libraries

[Elana Hashman]

On Tue, Sep 22, 2020 at 08:56:25PM +1000, Dmitry Smirnov wrote:
> 
> As discussed in debian-devel, Kubernetes package abuses Debian practices 
> and Golang team policies by needlessly vendoring hundreds(!) of libraries,
> most of which are available in Debian.
> 
> For a complex package like Kubernetes, _some_ strategic vendoring would be
> understandable for practical reasons. But not everything.
> 
> Maintainer circumvented packaging practices and introduced re-packaged
> Kubernetes in a state that would have never been accepted by ftp-masters.
> 
> Please consider removing redundant libraries from "vendor".
> In the current state, the package is unsuitable for "stable".

It's not entirely clear to me if the policy concerns are around
licensing compliance or simply the volume of vendored dependencies.


Wearing my Kubernetes SIG Chair/upstream hat:

I believe that the license compliance of everything in vendor/ has been
thoroughly vetted, but that information may not have been adequately
surfaced for downstream projects to use. In this case, any violations
are surface-level/paperwork as opposed to fundamental issues with DFSG
compliance. I've requested that upstream better surfaces this
information in order to be able to build Kubernetes in a
policy-compliant way in Debian:
https://github.com/kubernetes/kubernetes/issues/94976

Thanks,

- e


signature.asc
Description: PGP signature

Bug#970726: patch uploaded in deferred/7

[Gianfranco Costamagna]

control: tags -1 patch pending

The following debdiff has been uploaded in deferred/7, feel free to 
reschedule/cancel it

diff -Nru rpi.gpio-0.7.0/debian/changelog rpi.gpio-0.7.0/debian/changelog
--- rpi.gpio-0.7.0/debian/changelog 2020-01-16 17:20:40.0 +0100
+++ rpi.gpio-0.7.0/debian/changelog 2020-09-22 18:16:04.0 +0200
@@ -1,3 +1,13 @@
+rpi.gpio (0.7.0-0.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Grab workaround from meta-raspberrypi to add fcommon and fix gcc-10 build
+failure (Closes: #970726)
+  * Fix README.txt installation, by fixing typo in debian/rpio.gpio-common.docs
+(Closes: #970728) (patch from Ubuntu Dave Jones )
+
+ -- Gianfranco Costamagna   Tue, 22 Sep 2020 
18:16:04 +0200
+
 rpi.gpio (0.7.0-0.1) unstable; urgency=medium

   * Non-maintainer upload.
diff -Nru rpi.gpio-0.7.0/debian/rpi.gpio-common.docs 
rpi.gpio-0.7.0/debian/rpi.gpio-common.docs
--- rpi.gpio-0.7.0/debian/rpi.gpio-common.docs  1970-01-01 01:00:00.0 
+0100
+++ rpi.gpio-0.7.0/debian/rpi.gpio-common.docs  2020-09-22 18:16:02.0 
+0200
@@ -0,0 +1 @@
+README.txt
diff -Nru rpi.gpio-0.7.0/debian/rpio.gpio-common.docs 
rpi.gpio-0.7.0/debian/rpio.gpio-common.docs
--- rpi.gpio-0.7.0/debian/rpio.gpio-common.docs 2018-06-12 14:22:46.0 
+0200
+++ rpi.gpio-0.7.0/debian/rpio.gpio-common.docs 1970-01-01 01:00:00.0 
+0100
@@ -1 +0,0 @@
-README.txt
diff -Nru rpi.gpio-0.7.0/debian/rules rpi.gpio-0.7.0/debian/rules
--- rpi.gpio-0.7.0/debian/rules 2020-01-16 17:20:40.0 +0100
+++ rpi.gpio-0.7.0/debian/rules 2020-09-22 18:16:02.0 +0200
@@ -7,7 +7,7 @@

 export DEB_BUILD_MAINT_OPTIONS = hardening=+all

-DEB_CFLAGS_MAINT_APPEND += $(shell getconf LFS_CFLAGS)
+DEB_CFLAGS_MAINT_APPEND += $(shell getconf LFS_CFLAGS) -fcommon
 DEB_LDFLAGS_MAINT_APPEND += $(shell getconf LFS_LDFLAGS)
 DEB_LDFLAGS_MAINT_APPEND += -Wl,--as-needed
 export DEB_CFLAGS_MAINT_APPEND DEB_LDFLAGS_MAINT_APPEND


diff -Nru rpi.gpio-0.7.0/debian/changelog rpi.gpio-0.7.0/debian/changelog
--- rpi.gpio-0.7.0/debian/changelog 2020-01-16 17:20:40.0 +0100
+++ rpi.gpio-0.7.0/debian/changelog 2020-09-22 18:16:04.0 +0200
@@ -1,3 +1,13 @@
+rpi.gpio (0.7.0-0.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Grab workaround from meta-raspberrypi to add fcommon and fix gcc-10 build
+failure (Closes: #970726)
+  * Fix README.txt installation, by fixing typo in debian/rpio.gpio-common.docs
+(Closes: #970728) (patch from Ubuntu Dave Jones )
+
+ -- Gianfranco Costamagna   Tue, 22 Sep 2020 
18:16:04 +0200
+
 rpi.gpio (0.7.0-0.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru rpi.gpio-0.7.0/debian/rpi.gpio-common.docs 
rpi.gpio-0.7.0/debian/rpi.gpio-common.docs
--- rpi.gpio-0.7.0/debian/rpi.gpio-common.docs  1970-01-01 01:00:00.0 
+0100
+++ rpi.gpio-0.7.0/debian/rpi.gpio-common.docs  2020-09-22 18:16:02.0 
+0200
@@ -0,0 +1 @@
+README.txt
diff -Nru rpi.gpio-0.7.0/debian/rpio.gpio-common.docs 
rpi.gpio-0.7.0/debian/rpio.gpio-common.docs
--- rpi.gpio-0.7.0/debian/rpio.gpio-common.docs 2018-06-12 14:22:46.0 
+0200
+++ rpi.gpio-0.7.0/debian/rpio.gpio-common.docs 1970-01-01 01:00:00.0 
+0100
@@ -1 +0,0 @@
-README.txt
diff -Nru rpi.gpio-0.7.0/debian/rules rpi.gpio-0.7.0/debian/rules
--- rpi.gpio-0.7.0/debian/rules 2020-01-16 17:20:40.0 +0100
+++ rpi.gpio-0.7.0/debian/rules 2020-09-22 18:16:02.0 +0200
@@ -7,7 +7,7 @@
 
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 
-DEB_CFLAGS_MAINT_APPEND += $(shell getconf LFS_CFLAGS)
+DEB_CFLAGS_MAINT_APPEND += $(shell getconf LFS_CFLAGS) -fcommon
 DEB_LDFLAGS_MAINT_APPEND += $(shell getconf LFS_LDFLAGS)
 DEB_LDFLAGS_MAINT_APPEND += -Wl,--as-needed
 export DEB_CFLAGS_MAINT_APPEND DEB_LDFLAGS_MAINT_APPEND

Processed: patch uploaded in deferred/7

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch pending
Bug #970726 [src:rpi.gpio] rpi.gpio: FTBFS in sid (gcc-10)
Added tag(s) pending.

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

Bug#970730: spice-gtk build-depends unsatisfiable in testing

[peter green]

Source: spice-gtk
Version: 0.38-2
Severity: serious

spice-gtk build-depends on gstreamer1.0-doc which is no longer built by the 
gstreamer1.0 source package.
It still seems to be present in unstable as a cruft package, but is completely 
gone from testing.

Bug#970726: rpi.gpio: FTBFS in sid (gcc-10)

[Gianfranco Costamagna]

control: tags -1 patch


This works...

--- rpi.gpio-0.7.0/debian/rules 2020-01-16 17:20:40.0 +0100
+++ rpi.gpio-0.7.0/debian/rules 2020-09-22 18:03:46.0 +0200
@@ -7,7 +7,7 @@
 
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 
-DEB_CFLAGS_MAINT_APPEND += $(shell getconf LFS_CFLAGS)
+DEB_CFLAGS_MAINT_APPEND += $(shell getconf LFS_CFLAGS) -fcommon
 DEB_LDFLAGS_MAINT_APPEND += $(shell getconf LFS_LDFLAGS)
 DEB_LDFLAGS_MAINT_APPEND += -Wl,--as-needed
 export DEB_CFLAGS_MAINT_APPEND DEB_LDFLAGS_MAINT_APPEND


G.

On Tue, 22 Sep 2020 17:58:36 +0200 Gianfranco Costamagna 
 wrote:
> Source: rpi.gpio
> Version: 0.7.0-0.1
> Severity: serious
> 
> Hello, looks like gcc-10 broke the rpi-gpio build (obviously only on arm*).
> 
> 
> people from meta-raspberrypi workarounded with the fcommon flag...
> # ignore issues with -fno-common from gcc-10 until it's fixed in upstream:
> # https://sourceforge.net/p/raspberry-gpio-python/tickets/187/
> CFLAGS += "-fcommon"
> 
> 
> aarch64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g 
> -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat 
> -Werror=format-security -g -fwrapv -O2 -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
> -I/usr/include/python3.8 -c source/soft_pwm.c -o 
> build/temp.linux-arm64-3.8/source/soft_pwm.o
> aarch64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g 
> -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat 
> -Werror=format-security -g -fwrapv -O2 -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
> -I/usr/include/python3.8 -c source/py_pwm.c -o 
> build/temp.linux-arm64-3.8/source/py_pwm.o
> aarch64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g 
> -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat 
> -Werror=format-security -g -fwrapv -O2 -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
> -I/usr/include/python3.8 -c source/common.c -o 
> build/temp.linux-arm64-3.8/source/common.o
> aarch64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g 
> -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat 
> -Werror=format-security -g -fwrapv -O2 -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
> -I/usr/include/python3.8 -c source/constants.c -o 
> build/temp.linux-arm64-3.8/source/constants.o
> aarch64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions 
> -Wl,-Bsymbolic-functions -Wl,-z,relro -g -fwrapv -O2 -Wl,-Bsymbolic-functions 
> -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
> build/temp.linux-arm64-3.8/source/py_gpio.o 
> build/temp.linux-arm64-3.8/source/c_gpio.o 
> build/temp.linux-arm64-3.8/source/cpuinfo.o 
> build/temp.linux-arm64-3.8/source/event_gpio.o 
> build/temp.linux-arm64-3.8/source/soft_pwm.o 
> build/temp.linux-arm64-3.8/source/py_pwm.o 
> build/temp.linux-arm64-3.8/source/common.o 
> build/temp.linux-arm64-3.8/source/constants.o -o 
> /<>/.pybuild/cpython3_3.8_rpi.gpio/build/RPi/_GPIO.cpython-38-aarch64-linux-gnu.so
> /usr/bin/ld: 
> build/temp.linux-arm64-3.8/source/soft_pwm.o:./source/soft_pwm.c:28: multiple 
> definition of `threads'; 
> build/temp.linux-arm64-3.8/source/event_gpio.o:./source/event_gpio.c:60: 
> first defined here
> /usr/bin/ld: build/temp.linux-arm64-3.8/source/py_pwm.o:./source/common.h:38: 
> multiple definition of `gpio_direction'; 
> build/temp.linux-arm64-3.8/source/py_gpio.o:./source/common.h:38: first 
> defined here
> /usr/bin/ld: build/temp.linux-arm64-3.8/source/py_pwm.o:./source/py_pwm.h:23: 
> multiple definition of `PWMType'; 
> build/temp.linux-arm64-3.8/source/py_gpio.o:./source/py_pwm.h:23: first 
> defined here
> /usr/bin/ld: build/temp.linux-arm64-3.8/source/py_pwm.o:./source/common.h:41: 
> multiple definition of `module_setup'; 
> build/temp.linux-arm64-3.8/source/py_gpio.o:./source/common.h:41: first 
> defined here
> /usr/bin/ld: build/temp.linux-arm64-3.8/source/py_pwm.o:./source/common.h:40: 
> multiple definition of `setup_error'; 
> build/temp.linux-arm64-3.8/source/py_gpio.o:./source/common.h:40: first 
> defined here
> /usr/bin/ld: build/temp.linux-arm64-3.8/source/py_pwm.o:./source/common.h:39: 
> multiple definition of `rpiinfo'; 
> build/temp.linux-arm64-3.8/source/py_gpio.o:./source/common.h:39: first 
> defined here
> /usr/bin/ld: build/temp.linux-arm64-3.8/source/py_pwm.o:./source/common.h:37: 
> multiple definition of `pin_to_gpio'; 
> build/temp.linux-arm64-3.8/source/py_gpio.o:./source/common.h:37: first 
> defined here
> /usr/bin/ld: build/temp.linux-arm64-3.8/source/py_pwm.o:./source/common.h:36: 
> 

Processed: Re: rpi.gpio: FTBFS in sid (gcc-10)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #970726 [src:rpi.gpio] rpi.gpio: FTBFS in sid (gcc-10)
Added tag(s) patch.

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

Bug#970727: python-magcode-core needs a source-only upload.

[peter green]

Source: python-magcode-core
Version: 1.5.4-2
Severity: serious

The release team have decreed that non-buildd binaries can no longer migrate to 
testing, please make a source-only
upload so your package can migrate.

Bug#970726: rpi.gpio: FTBFS in sid (gcc-10)

[Gianfranco Costamagna]

Source: rpi.gpio
Version: 0.7.0-0.1
Severity: serious

Hello, looks like gcc-10 broke the rpi-gpio build (obviously only on arm*).


people from meta-raspberrypi workarounded with the fcommon flag...
# ignore issues with -fno-common from gcc-10 until it's fixed in upstream:
# https://sourceforge.net/p/raspberry-gpio-python/tickets/187/
CFLAGS += "-fcommon"


aarch64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g 
-fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security 
-g -fwrapv -O2 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.8 -c source/soft_pwm.c -o 
build/temp.linux-arm64-3.8/source/soft_pwm.o
aarch64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g 
-fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security 
-g -fwrapv -O2 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.8 -c source/py_pwm.c -o 
build/temp.linux-arm64-3.8/source/py_pwm.o
aarch64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g 
-fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security 
-g -fwrapv -O2 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.8 -c source/common.c -o 
build/temp.linux-arm64-3.8/source/common.o
aarch64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g 
-fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security 
-g -fwrapv -O2 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.8 -c source/constants.c -o 
build/temp.linux-arm64-3.8/source/constants.o
aarch64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions 
-Wl,-Bsymbolic-functions -Wl,-z,relro -g -fwrapv -O2 -Wl,-Bsymbolic-functions 
-Wl,-z,relro -Wl,-z,now -Wl,--as-needed -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
build/temp.linux-arm64-3.8/source/py_gpio.o 
build/temp.linux-arm64-3.8/source/c_gpio.o 
build/temp.linux-arm64-3.8/source/cpuinfo.o 
build/temp.linux-arm64-3.8/source/event_gpio.o 
build/temp.linux-arm64-3.8/source/soft_pwm.o 
build/temp.linux-arm64-3.8/source/py_pwm.o 
build/temp.linux-arm64-3.8/source/common.o 
build/temp.linux-arm64-3.8/source/constants.o -o 
/<>/.pybuild/cpython3_3.8_rpi.gpio/build/RPi/_GPIO.cpython-38-aarch64-linux-gnu.so
/usr/bin/ld: 
build/temp.linux-arm64-3.8/source/soft_pwm.o:./source/soft_pwm.c:28: multiple 
definition of `threads'; 
build/temp.linux-arm64-3.8/source/event_gpio.o:./source/event_gpio.c:60: first 
defined here
/usr/bin/ld: build/temp.linux-arm64-3.8/source/py_pwm.o:./source/common.h:38: 
multiple definition of `gpio_direction'; 
build/temp.linux-arm64-3.8/source/py_gpio.o:./source/common.h:38: first defined 
here
/usr/bin/ld: build/temp.linux-arm64-3.8/source/py_pwm.o:./source/py_pwm.h:23: 
multiple definition of `PWMType'; 
build/temp.linux-arm64-3.8/source/py_gpio.o:./source/py_pwm.h:23: first defined 
here
/usr/bin/ld: build/temp.linux-arm64-3.8/source/py_pwm.o:./source/common.h:41: 
multiple definition of `module_setup'; 
build/temp.linux-arm64-3.8/source/py_gpio.o:./source/common.h:41: first defined 
here
/usr/bin/ld: build/temp.linux-arm64-3.8/source/py_pwm.o:./source/common.h:40: 
multiple definition of `setup_error'; 
build/temp.linux-arm64-3.8/source/py_gpio.o:./source/common.h:40: first defined 
here
/usr/bin/ld: build/temp.linux-arm64-3.8/source/py_pwm.o:./source/common.h:39: 
multiple definition of `rpiinfo'; 
build/temp.linux-arm64-3.8/source/py_gpio.o:./source/common.h:39: first defined 
here
/usr/bin/ld: build/temp.linux-arm64-3.8/source/py_pwm.o:./source/common.h:37: 
multiple definition of `pin_to_gpio'; 
build/temp.linux-arm64-3.8/source/py_gpio.o:./source/common.h:37: first defined 
here
/usr/bin/ld: build/temp.linux-arm64-3.8/source/py_pwm.o:./source/common.h:36: 
multiple definition of `pin_to_gpio_rev3'; 
build/temp.linux-arm64-3.8/source/py_gpio.o:./source/common.h:36: first defined 
here
/usr/bin/ld: build/temp.linux-arm64-3.8/source/py_pwm.o:./source/common.h:35: 
multiple definition of `pin_to_gpio_rev2'; 
build/temp.linux-arm64-3.8/source/py_gpio.o:./source/common.h:35: first defined 
here
/usr/bin/ld: build/temp.linux-arm64-3.8/source/py_pwm.o:./source/common.h:34: 
multiple definition of `pin_to_gpio_rev1'; 
build/temp.linux-arm64-3.8/source/py_gpio.o:./source/common.h:34: first defined 
here
/usr/bin/ld: build/temp.linux-arm64-3.8/source/py_pwm.o:./source/common.h:33: 
multiple definition of `gpio_mode'; 
build/temp.linux-arm64-3.8/source/py_gpio.o:./source/common.h:33: first defined 
here
/usr/bin/ld: 

Processed: Re: Bug#970580: licenseutils: Memory access error

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://savannah.nongnu.org/bugs/?59157
Bug #970580 [licenseutils] licenseutils: Memory access error
Set Bug forwarded-to-address to 'https://savannah.nongnu.org/bugs/?59157'.

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

Bug#970580: licenseutils: Memory access error

[Mattia Rizzolo]

Control: forwarded -1 https://savannah.nongnu.org/bugs/?59157

On Sat, Sep 19, 2020 at 10:24:38AM +0200, Mechtilde Stehmann wrote:
> At the first start I got
> 
> licensing gpl: got unexpected response code 302 from
> www.gnu.org/licenses/gpl.txt
> 
> I also tested more options and get "Memory access error"
> 
> No option gives a result


thank you, forwarded upstream at the above URL.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#966449: marked as done (coreutils 8.32-3 FTBFS on arm64 (and proposed fix))

[Debian Bug Tracking System]

Your message dated Tue, 22 Sep 2020 12:48:53 +
with message-id 
and subject line Bug#966449: fixed in coreutils 8.32-4
has caused the Debian Bug report #966449,
regarding coreutils 8.32-3 FTBFS on arm64 (and proposed fix)
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.)


-- 
966449: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966449
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: coreutils
Version: 8.32-3
Severity: serious
Tags: patch ftbfs

Hi,

The current coreutils version FTBFS on arm64:

src/ls.c: In function 'print_dir':
src/ls.c:3026:24: error: 'SYS_getdents' undeclared (first use in this 
function); did you mean 'SYS_getdents64'?
 3026 |   if (syscall (SYS_getdents, dirfd (dirp), NULL, 0) == -1
  |^~~~
  |SYS_getdents64
src/ls.c:3026:24: note: each undeclared identifier is reported only once for 
each function it appears in

This has been reported upstream in
.
The fix upstream adopted is to restore the behaviour of ls on removed
directories back to what it was on 8.31.

I've backported the patches needed to fix the issue, so I'm proposing
them here.  Ubuntu coreutils is already carrying these patches and the
ARM64 build passes there.

Thanks!

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
https://sergiodj.net/

diff -Nru coreutils-8.32/debian/changelog coreutils-8.32/debian/changelog
--- coreutils-8.32/debian/changelog	2020-07-20 14:09:06.0 -0400
+++ coreutils-8.32/debian/changelog	2020-07-28 10:50:52.0 -0400
@@ -1,3 +1,16 @@
+coreutils (8.32-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS on ARM64.
+- d/p/restore-ls-behavior-8.31.patch: Upstream patch to restore
+  coreutils ls' 8.31 behavior on removed directories, which is
+  necessary to prevent using SYS_getdents that doesn't exist on
+  ARM64.
+- d/p/improve-removed-directory-test.patch: Upstream patch to
+  improve ls' removed-directory test.
+
+ -- Sergio Durigan Junior   Tue, 28 Jul 2020 10:50:52 -0400
+
 coreutils (8.32-3) unstable; urgency=low
 
   * build with libgmp now that apt pulls it in anyway (Closes: #64527)
diff -Nru coreutils-8.32/debian/patches/improve-removed-directory-test.patch coreutils-8.32/debian/patches/improve-removed-directory-test.patch
--- coreutils-8.32/debian/patches/improve-removed-directory-test.patch	1969-12-31 19:00:00.0 -0500
+++ coreutils-8.32/debian/patches/improve-removed-directory-test.patch	2020-07-28 10:50:23.0 -0400
@@ -0,0 +1,49 @@
+From: Paul Eggert 
+Date: Sat, 7 Mar 2020 10:29:51 -0800
+Subject: ls: improve removed-directory test
+
+* tests/ls/removed-directory.sh: Remove host_triplet test.
+Skip this test if one cannot remove the working directory.
+From a suggestion by Bernhard Voelker (Bug#39929).
+
+Author: Paul Eggert 
+Origin: upstream, https://git.savannah.gnu.org/cgit/coreutils.git/commit/?id=672819c73f2e94e61386dc0584bddf9da860cc26
+Bug: https://lists.gnu.org/archive/html/bug-coreutils/2020-03/msg5.html
+Last-Updated: 2020-07-24
+Reviewed-By: Sergio Durigan Junior 
+---
+ tests/ls/removed-directory.sh | 13 -
+ 1 file changed, 4 insertions(+), 9 deletions(-)
+
+diff --git a/tests/ls/removed-directory.sh b/tests/ls/removed-directory.sh
+index fe8f929..63b209d 100755
+--- a/tests/ls/removed-directory.sh
 b/tests/ls/removed-directory.sh
+@@ -1,7 +1,7 @@
+ #!/bin/sh
+-# If ls is asked to list a removed directory (e.g. the parent process's
+-# current working directory that has been removed by another process), it
+-# emits an error message.
++# If ls is asked to list a removed directory (e.g., the parent process's
++# current working directory has been removed by another process), it
++# should not emit an error message merely because the directory is removed.
+ 
+ # Copyright (C) 2020 Free Software Foundation, Inc.
+ 
+@@ -21,15 +21,10 @@
+ . "${srcdir=.}/tests/init.sh"; path_prepend_ ./src
+ print_ver_ ls
+ 
+-case $host_triplet in
+-  *linux*) ;;
+-  *) skip_ 'non linux kernel' ;;
+-esac
+-
+ cwd=$(pwd)
+ mkdir d || framework_failure_
+ cd d || framework_failure_
+-rmdir ../d || framework_failure_
++rmdir ../d || skip_ "can't remove working directory on this platform"
+ 
+ ls >../out 2>../err || fail=1
+ cd "$cwd" || framework_failure_
diff -Nru coreutils-8.32/debian/patches/restore-ls-behavior-8.31.patch 

Bug#921697: marked as done (libcxx-serial-dev: /usr/include/v8stdint.h is already provided by libv8-dev)

[Debian Bug Tracking System]

Your message dated Tue, 22 Sep 2020 12:03:31 +
with message-id 
and subject line Bug#921697: fixed in libcxx-serial 1.2.1-2
has caused the Debian Bug report #921697,
regarding libcxx-serial-dev: /usr/include/v8stdint.h is already provided by 
libv8-dev
to be marked as done.

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

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


-- 
921697: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921697
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcxx-serial-dev
Version: 1.2.1-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.

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

  Selecting previously unselected package libcxx-serial-dev:amd64.  

   Preparing to unpack 
.../libcxx-serial-dev_1.2.1-1_amd64.deb ... 

 Unpacking libcxx-serial-dev:amd64 (1.2.1-1) 
... 

 dpkg: error processing archive 
/var/cache/apt/archives/libcxx-serial-dev_1.2.1-1_amd64.deb (--unpack): 

   trying to overwrite '/usr/include/v8stdint.h', which is 
also in package libv8-dev 3.14.5.8-11   

dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

 Errors were encountered 
while processing:   

  
/var/cache/apt/archives/libcxx-serial-dev_1.2.1-1_amd64.deb 

  

Same conflict with libv8-3.14-dev.


From the synopsis of the packages I don't think that libv8 and libcxx-serial
are related ...


cheers,

Andreas


libv8-dev=3.14.5.8-11_libcxx-serial-dev=1.2.1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libcxx-serial
Source-Version: 1.2.1-2
Done: Alec Leamas 

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

Debian distribution maintenance software
pp.
Alec Leamas  (supplier of updated libcxx-serial package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 19 Sep 2020 12:13:27 +0200
Source: libcxx-serial
Architecture: source
Version: 1.2.1-2
Distribution: unstable
Urgency: medium
Maintainer: Alec Leamas 
Changed-By: Alec Leamas 
Closes: 921697
Changes:
 libcxx-serial (1.2.1-2) unstable; urgency=medium
 .
   * Drop v8stdint.h header (not used in Debian). Closes: #921697
   * Update python-catkin-pkg BR to python3.
   * Standards-version -> 4.5.0, no changes.
   * Update dephelper-compat -> 12
   * Set Rules-Requires-Root
   * Add d/upstream/metadata
   * Handle DEB_BUILD_OPTIONS when overriding test target.
   * Clean up test target in d/rules,
   * Simplify d/rules using --buildsystem=cmake.
   * Reorganize repo branches according to dep-14.
   * Fix lingering templates in d/watch.
   * New local patches:
  - Drop v8stdint.h header (above)
   * Cherry-picked upstream bugfix patches:
  - Fix SerialImpl constructor resource leak.
  - Handle 500kpbs serial ports.
  - Plug memory leak in exceptions.
  - Use 

Bug#970651: [Pkg-javascript-devel] Bug#970651: Bug#970651: Bug#970651: rollup: Unable to build with current tsc

[Pirate Praveen]

On Tue, Sep 22, 2020 at 13:21, Xavier  wrote:

Looks good to me too. We could perhaps list the "bigger transitions"
(nodejs, babel, bubble, rollup)


Included a link to that page already :)

Bug#970651: [Pkg-javascript-devel] Bug#970651: Bug#970651: rollup: Unable to build with current tsc

[Xavier]

Le 22/09/2020 à 13:10, Jonas Smedegaard a écrit :
> Quoting Pirate Praveen (2020-09-22 13:03:53)
>>
>>
>> On Mon, Sep 21, 2020 at 11:53, Jonas Smedegaard  wrote:
>>> If you simply mean a loose "don't break reverse dependencies!" and 
>>> write some suggestions down on a wiki page, then I fully agree: That 
>>> is common for Debian in general.  What might be notable about 
>>> node.js is the likelyhood of complying with semantic versioning, and 
>>> it might be helpful to emphasize that in this team.
>>
>> I have started a wiki page by copying from ruby teams policy at 
>> https://wiki.debian.org/Javascript/Transitions/Policy
>>
>> Please go through and suggest if we need to change anything.
>>
>>> If you propose a formal screening process, then I am sceptical both 
>>> how to practically enforce that and whether it is the right 
>>> approach.
>>
>> ok, lets start with documenting our expectation and forget this option 
>> for now. If we see a lot of uploads not following the policy, we can 
>> think about this or other options later.
> 
> Current wiki text looks fine to me.
> 
> Thanks for driving this!
> 
>  - Jonas

Looks good to me too. We could perhaps list the "bigger transitions"
(nodejs, babel, bubble, rollup)

Thanks !

Bug#970651: [Pkg-javascript-devel] Bug#970651: Bug#970651: rollup: Unable to build with current tsc

[Jonas Smedegaard]

Quoting Pirate Praveen (2020-09-22 13:03:53)
> 
> 
> On Mon, Sep 21, 2020 at 11:53, Jonas Smedegaard  wrote:
> > If you simply mean a loose "don't break reverse dependencies!" and 
> > write some suggestions down on a wiki page, then I fully agree: That 
> > is common for Debian in general.  What might be notable about 
> > node.js is the likelyhood of complying with semantic versioning, and 
> > it might be helpful to emphasize that in this team.
> 
> I have started a wiki page by copying from ruby teams policy at 
> https://wiki.debian.org/Javascript/Transitions/Policy
> 
> Please go through and suggest if we need to change anything.
> 
> > If you propose a formal screening process, then I am sceptical both 
> > how to practically enforce that and whether it is the right 
> > approach.
> 
> ok, lets start with documenting our expectation and forget this option 
> for now. If we see a lot of uploads not following the policy, we can 
> think about this or other options later.

Current wiki text looks fine to me.

Thanks for driving this!

 - Jonas

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

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

signature.asc
Description: signature

Bug#970651: [Pkg-javascript-devel] Bug#970651: Bug#970651: rollup: Unable to build with current tsc

[Pirate Praveen]

On Mon, Sep 21, 2020 at 11:53, Jonas Smedegaard  wrote:

Quoting Pirate Praveen (2020-09-21 09:15:46)
If you simply mean a loose "don't break reverse dependencies!" and 
write
some suggestions down on a wiki page, then I fully agree: That is 
common

for Debian in general.  What might be notable about node.js is the
likelyhood of complying with semantic versioning, and it might be
helpful to emphasize that in this team.


I have started a wiki page by copying from ruby teams policy at
https://wiki.debian.org/Javascript/Transitions/Policy

Please go through and suggest if we need to change anything.

If you propose a formal screening process, then I am sceptical both 
how

to practically enforce that and whether it is the right approach.


ok, lets start with documenting our expectation and forget this option 
for now. If we see a lot of uploads not following the policy, we can 
think about this or other options later.

Bug#970717: kubernetes: abuse of "embedded code copies" | hundreds of vendored libraries

[Dmitry Smirnov]

Source: kubernetes
Version: 1.17.4-1
Severity: serious
X-Debbugs-CC: debian-c...@lists.debian.org

As discussed in debian-devel [1], Kubernetes package abuses Debian practices 
and Golang team policies by needlessly vendoring hundreds(!) of libraries,
most of which are available in Debian.

For a complex package like Kubernetes, _some_ strategic vendoring would be
understandable for practical reasons. But not everything.

Maintainer circumvented packaging practices and introduced re-packaged
Kubernetes in a state that would have never been accepted by ftp-masters.

Please consider removing redundant libraries from "vendor".
In the current state, the package is unsuitable for "stable".

[1]: https://lists.debian.org/debian-devel/2020/03/msg00359.html

See also: https://wiki.debian.org/EmbeddedCopies

-- 
Best wishes,
 Dmitry Smirnov

---

We often refuse to accept an idea merely because the way in which it has
been expressed is unsympathetic to us.
-- Friedrich Nietzsche


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

Bug#970497: igraph: FTBFS on mips64el

[Peter Ji]

At 2020-09-18 03:28:29, "Andreas Tille"  wrote:
>Hi,
>
>it would be really great if some porter with access to mips64el would
>try to build the package igraph and send the content of
>tests/testsuite.dir to the upstream bug report
>
>   https://github.com/igraph/igraph/issues/1469
>Hi:
 I build the package igraph on my mips64el computer with src " latest master 
branch" 、“released igraph 0.8.2.tar.gz ” and "igraph_0.8.2+ds-2.dsc"
There is no "tests ERROR" you mentioned，I don't know why but  result of the 
command " make -j4 check VERBOSE=1 " are:


" latest master branch":
## - ##
## Test results. ##
## - ##

265 tests were successful.
2 tests were skipped.
make[2]: Leaving directory '/home/igraph/igraph/tests'
make[1]: Leaving directory '/home/igraph/igraph/tests'
make[1]: Entering directory '/home/igraph/igraph'
make[1]: Leaving directory '/home/igraph/igraph'

---
“released igraph 0.8.2.tar.gz ”:
## - ##
## Test results. ##
## - ##

262 tests were successful.
2 tests were skipped.
make[2]: Leaving directory '/home/igraph/igraph-0.8.2/tests'
make[1]: Leaving directory '/home/igraph/igraph-0.8.2/tests'
make[1]: Entering directory '/home/igraph/igraph-0.8.2'
make[1]: Leaving directory '/home/igraph/igraph-0.8.2'
---
"igraph_0.8.2+ds-2.dsc":
## - ##
## Test results. ##
## - ##

260 tests were successful.
2 tests were skipped.
make[3]: Leaving directory '/home/igraph/debtest/igraph-0.8.2+ds/tests'
make[2]: Leaving directory '/home/igraph/debtest/igraph-0.8.2+ds/tests'
make[2]: Entering directory '/home/igraph/debtest/igraph-0.8.2+ds'
make[2]: Leaving directory '/home/igraph/debtest/igraph-0.8.2+ds'
make[1]: Leaving directory '/home/igraph/debtest/igraph-0.8.2+ds'



I don't know what happened when you build，Maybe it's not a code error.
if you want  to try on a mips64el computer, Let me know, You can connect to my 
Cloud Platforms using ssh.


Hoping to help

Peter Ji

Processed: fixed 962616 in 2.30.1-1

[Debian Bug Tracking System]

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

> fixed 962616 2.30.1-1
Bug #962616 {Done: Alberto Garcia } [src:webkit2gtk] 
webkit2gtk: FTBFS on mipsel
Marked as fixed in versions webkit2gtk/2.30.1-1.
> thanks
Stopping processing here.

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

Bug#953770: bluez: CVE-2020-0556

[Aurelien Jarno]

control: fixed -1 5.54-1

This bug has been fixed upstream in version 5.54, thus marking it has
fixed in Debian version 5.54-1.

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Processed: Bug#953770: bluez: CVE-2020-0556

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 5.54-1
Bug #953770 {Done: Salvatore Bonaccorso } [src:bluez] bluez: 
CVE-2020-0556
Marked as fixed in versions bluez/5.54-1.

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

Bug#968719: marked as done (popplerkit.framework FTBFS with poppler 0.85)

[Debian Bug Tracking System]

Your message dated Tue, 22 Sep 2020 09:05:09 +
with message-id 
and subject line Bug#968719: fixed in popplerkit.framework 0.0.20051227svn-8.1
has caused the Debian Bug report #968719,
regarding popplerkit.framework FTBFS with poppler 0.85
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.)


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

Package: popplerkit.framework
Version: 0.0.20051227svn-8
Severity: serious
Tags: bullseye sid patch

popplerkit.framework FTBFS with poppler 0.85 because globalParams is now a 
std::unique_ptr
https://github.com/freedesktop/poppler/commit/759d190581f8ff069ecee9155313a8e69a2ca9c6

I have whipped up a patch adjusting popplerkit.framework in the same way the 
code in poppler
itself was adjusted. I have uploaded said patch to raspbian, a debdiff should 
appear soon
at https://debdiffs.raspbian.org/main/p/popplerkit.framework
--- End Message ---
--- Begin Message ---
Source: popplerkit.framework
Source-Version: 0.0.20051227svn-8.1
Done: Sebastian Ramacher 

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

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

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated 
popplerkit.framework package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 20 Sep 2020 10:30:28 +0200
Source: popplerkit.framework
Architecture: source
Version: 0.0.20051227svn-8.1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNUstep maintainers 

Changed-By: Sebastian Ramacher 
Closes: 968719
Changes:
 popplerkit.framework (0.0.20051227svn-8.1) unstable; urgency=medium
 .
   * Non-maintainer upload
 .
   [ Peter Michael Green ]
   * Fix build with poppler 0.85 (Closes: #968719)
Checksums-Sha1:
 abad06955169e978d7e4f61c3990abf9abf79b2e 2243 
popplerkit.framework_0.0.20051227svn-8.1.dsc
 89aa851d990527bf08ffb4cd27574e9930242d50 8608 
popplerkit.framework_0.0.20051227svn-8.1.debian.tar.xz
Checksums-Sha256:
 ee4f0131055ef86f7f79f494e4c5a8647ee6a1cd21cb875bf15c0c8942cb547a 2243 
popplerkit.framework_0.0.20051227svn-8.1.dsc
 c24fea6e20dc2e935f65d1a268302fee6939670596c8d3c450b8bee95806c975 8608 
popplerkit.framework_0.0.20051227svn-8.1.debian.tar.xz
Files:
 24eb8d4cbf7e844d53215bab7ccb36bb 2243 libs optional 
popplerkit.framework_0.0.20051227svn-8.1.dsc
 7172936aee00902b01def8cab0467099 8608 libs optional 
popplerkit.framework_0.0.20051227svn-8.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAl9nFN0ACgkQafL8UW6n
GZOtFw/+OUlOFMmApXdDRDOhBvdYjDmyO21NBxRLOfN/jzo0dDhwj4q1o6CTiuZQ
tUZuUn2bNcwoK07wER6wEnEZeYVjCdTHrOO/0ayFAaohRVm2+c3ZtdmULg1VotTA
qcgUqjpYkttxiKPeT0TGY5umfHj9PyWApzHQ4DDZKopQC88R4QnqRFrgYAFXVvc2
JEF6VU2wtG8NGHB0OlxlLFlda1m901/fXToC/EbC8lmv8o2zTG6mqQH4Xc8mCMp5
FQ3RcSDhUun9Mk2bq70AijUTSgD6S5a/OSQlGnO3fMrz9Reu5PZNP4XLbCMhsFxu
rPUGvLfQS54URsXPILEf/Am348J1clTCpjGBWIGocvde1+3pkbq2iSG36I7xmcjN
rKlqpIHwLGj134XKFzd35CjUbjmWyMcu+TrBU+6cl4QCGT5t/SHGsIrNuteFiKlQ
DHXtZn8zDw93EdLZnkdMNA1x/yleGiCW7RS/E9HRHSCo42HFIUn2xGsumxiPPUwR
b7C/+4YvuckfRKLN5BUC2npUaiILdnxghv/OAT+lyRtaAjrWYDLdFAI707gkyqNk
ERCGZXRPrQkvcyp02z2bJpOvafloXDRUrfMS9o7v6WKlPEMcyznrT73TVC18nObh
y7IguqUyXLvUHTliaOsgi3HfI4tZNhjLrQch+V+cdvOS2ujpRAc=
=3Rhc
-END PGP SIGNATURE End Message ---

Bug#966851: marked as done (intel-graphics-compiler: FTBFS: igax.hpp:501:30: error: argument to ‘alloca’ may be too large [-Werror=alloca-larger-than=])

[Debian Bug Tracking System]

Your message dated Tue, 22 Sep 2020 09:04:52 +
with message-id 
and subject line Bug#966851: fixed in intel-graphics-compiler 1.0.5064-1
has caused the Debian Bug report #966851,
regarding intel-graphics-compiler: FTBFS: igax.hpp:501:30: error: argument to 
‘alloca’ may be too large [-Werror=alloca-larger-than=]
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.)


-- 
966851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966851
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: intel-graphics-compiler
Version: 1.0.3627-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200802 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> cd /<>/build/IGC/visa && /usr/bin/c++  -DCL_KHR_FP64_EXT 
> -DDISABLE_ENCODER_EXCEPTIONS -DGHAL3D=USC -DICBE_LINUX -DIGC_CMAKE 
> -DIGC_EXPORTS=1 -DIGC_SPIRV_ENABLED -DINSIDE_PLUGIN -DISTDLIB_UMD -DLINUX 
> -DNDEBUG -DNOMINMAX -DSTANDALONE_MODE -DSTD_CALL -DUSC_EXPORTS=1 -DUSE_MMX 
> -DUSE_SSE -DUSE_SSE2 -DUSE_SSE3 -DUSE_SSSE3 -D_AMD64_ -D_COMPILER_DLL_ 
> -D_CRT_SECURE_NO_WARNINGS -D_HAS_EXCEPTIONS=0 -D_IGC_ 
> -D_SCL_SECURE_NO_WARNINGS -D__STDC_CONSTANT_MACROS -D__STDC_LIMIT_MACROS 
> -I/<>/IGC/WrapperLLVM/include 
> -I/<>/build/IGC/autogen -I/<>/IGC 
> -I/<>/IGC/common -I/<>/IGC/.. 
> -I/<>/IGC/../Common -I/<>/IGC/../3d/common 
> -I/<>/IGC/../inc -I/<>/IGC/../inc/common 
> -I/<>/IGC/../inc/common/Compiler 
> -I/<>/IGC/../inc/common/Compiler/API 
> -I/<>/IGC/../visa/include -I/<>/build/IGC/Release 
> -I/<>/IGC/AdaptorOCL/ocl_igc_shared/executable_format 
> -I/<>/IGC/AdaptorOCL 
> -I/<>/IGC/../inc/common/Compiler/common 
> -I/<>/IGC/AdaptorOCL/cif/cif/.. -I/usr/lib/llvm-10/include 
> -I/<>/build/IGC/visa -I/<>/visa 
> -I/<>/visa/include  -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -fno-exceptions -fdata-sections -ffunction-sections -O2 
> -pipe -fmessage-length=0 -march=corei7 -mstackrealign -fms-extensions -Werror 
> -Wno-unused-parameter -Wno-missing-field-initializers -Wwrite-strings 
> -Wno-long-long -Wswitch -Wno-sign-compare -Wno-unused-result 
> -Wno-enum-compare -Wno-type-limits -Wno-ignored-qualifiers -Wformat-security 
> -Wno-extra -Wno-write-strings -finline -fno-strict-aliasing -msse -msse2 
> -msse3 -mssse3 -msse4 -msse4.1 -msse4.2 -Wno-unknown-pragmas -fPIC 
> -fstack-protector -finline-functions -funswitch-loops 
> -Wno-maybe-uninitialized -lrt -fno-rtti -fvisibility=hidden 
> -fvisibility-inlines-hidden -DNDEBUG -g   -std=gnu++17 -o 
> CMakeFiles/GenX_IR_Exe.dir/BinaryEncodingCNL.cpp.o -c 
> /<>/visa/BinaryEncodingCNL.cpp
> In file included from /<>/visa/iga/IGAExe/fatal.hpp:33,
>  from /<>/visa/iga/IGAExe/iga_main.hpp:29,
>  from /<>/visa/iga/IGAExe/list_ops.cpp:26:
> /<>/visa/iga/IGAExe/../IGALibrary/api/igax.hpp: In member 
> function ‘std::string igax::OpSpec::menmonic() const’:
> /<>/visa/iga/IGAExe/../IGALibrary/api/igax.hpp:501:30: error: 
> argument to ‘alloca’ may be too large [-Werror=alloca-larger-than=]
>   501 | strPtr = (char *)alloca(strCap); \
>   |  ^~
> /<>/visa/iga/IGAExe/../IGALibrary/api/igax.hpp:507:1: note: in 
> expansion of macro ‘IGA_OPSPEC_STRING_GETTER’
>   507 | IGA_OPSPEC_STRING_GETTER(iga_opspec_mnemonic, 16);
>   | ^~~~
> /<>/visa/iga/IGAExe/../IGALibrary/api/igax.hpp: In member 
> function ‘std::string igax::OpSpec::name() const’:
> /<>/visa/iga/IGAExe/../IGALibrary/api/igax.hpp:501:30: error: 
> argument to ‘alloca’ may be too large [-Werror=alloca-larger-than=]
>   501 | strPtr = (char *)alloca(strCap); \
>   |  ^~
> /<>/visa/iga/IGAExe/../IGALibrary/api/igax.hpp:509:1: note: in 
> expansion of macro ‘IGA_OPSPEC_STRING_GETTER’
>   509 | IGA_OPSPEC_STRING_GETTER(iga_opspec_name, 32);
>   | ^~~~
> /<>/visa/iga/IGAExe/../IGALibrary/api/igax.hpp: In member 
> function ‘std::string igax::OpSpec::description() const’:
> /<>/visa/iga/IGAExe/../IGALibrary/api/igax.hpp:501:30: error: 
> argument to ‘alloca’ may be too large [-Werror=alloca-larger-than=]
>   501 | strPtr = (char *)alloca(strCap); \
>   |  ^~
> /<>/visa/iga/IGAExe/../IGALibrary/api/igax.hpp:511:1: note: in 
> expansion of macro ‘IGA_OPSPEC_STRING_GETTER’
>   511 | IGA_OPSPEC_STRING_GETTER(iga_opspec_description, 128);
>   | 

Bug#969711: marked as done (src:debmake: fails to migrate to testing for too long: maintainer built arch:all binaries)

[Debian Bug Tracking System]

Your message dated Tue, 22 Sep 2020 07:48:27 +
with message-id 
and subject line Bug#969711: fixed in debmake 4.3.2-1.1
has caused the Debian Bug report #969711,
regarding src:debmake: fails to migrate to testing for too long: maintainer 
built arch:all binaries
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.)


-- 
969711: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969711
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: debmake
Version: 4.3.1-1
Severity: serious
Control: close -1 4.3.2-1
Tags: sid bullseye pending
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:debmake in
its current version in unstable has been trying to migrate for 60 days
[2]. Hence, I am filing this bug.

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

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

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

Your package is only blocked because the arch:all binary package(s)
aren't built on a buildd. Unfortunately the Debian infrastructure
doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will
shortly do a no-changes source-only upload to DELAYED/15, closing this
bug. Please let me know if I should delay or cancel that upload.

Paul

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




signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: debmake
Source-Version: 4.3.2-1.1
Done: Paul Gevers 

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 07 Sep 2020 08:40:24 +0200
Source: debmake
Architecture: source
Version: 4.3.2-1.1
Distribution: unstable
Urgency: medium
Maintainer: Osamu Aoki 
Changed-By: Paul Gevers 
Closes: 969711
Changes:
 debmake (4.3.2-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * source only upload to enable migration (Closes: #969711)
Checksums-Sha1:
 0bc21d3e13bb0ca094b53492536e96230b6c68c2 1614 debmake_4.3.2-1.1.dsc
 9fe5380cac12235329795ae29d6b5ce0e9d98e43 6840 debmake_4.3.2-1.1.debian.tar.xz
Checksums-Sha256:
 71902e70fdd161ddfc2291d82f5faac3cd2cc90806abf08cf454b8cdf156594e 1614 
debmake_4.3.2-1.1.dsc
 3325eaa794da1a77819444158fb89d3f5e9247e50f94a1e8f78bf8f4a8636095 6840 
debmake_4.3.2-1.1.debian.tar.xz
Files:
 60bebb357ce3e09cafad2cbafcd77699 1614 devel optional debmake_4.3.2-1.1.dsc
 bbffa64256c2026ebe5320ad9126fd9d 6840 devel optional 
debmake_4.3.2-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl9V1fgACgkQnFyZ6wW9
dQqSGQf+PQoXmylkmCCQtfYfiAlTDAgYoe4qy+LZbD/aNo1+n5ML5FHKGezEtP+w
OpnU0bnmhTc9VwGhanOhcT/lbie52aGXWV+ivC6VJq9ucuF1Iy/n6HXR2BLtfVdf
bkfGN5GsCJgh/sChIyR/SRoBJmWdSLy1a/IdCjGuwhnDaJcwlNCV4zfqXf/b4PVd
V3KdOq5TL5/qGN972TauqTczVGqWAas9QtlUlCWo2+e3NJu0oW2MZkYbHqcEQjpA
Sya0wZsbVBoKSePshdC6rC/cF4WsoA4KiXltQa5A4vFsaABcgEXIn+4gvmKBP9k/
12/JMQa/PPr38a0WyA6hskc0FxtIpA==
=DkxX