Bug#953686: Add support for list-table :widths: and :header-rows: to rst2html?

[Petter Reinholdtsen]

[Dmitry Shachnev]
> I think the problem here is the indentation. The example in documentation [1]
> has the same indent level for directive options and for the content.

Aha.  But as far as I can tell from the specification in 
https://docutils.sourceforge.io/docs/ref/rst/restructuredtext.html#field-lists >
and
https://docutils.sourceforge.io/docs/ref/rst/restructuredtext.html#directives >
there is no requirement on how much indentation is used for directive
options, but perhaps I am reading it wrong.  Do you know why the
rst2html tool believe there is, while pandoc and xmlto do not?  Perhaps
they all should be made to agree on the syntax...

Anyway, thank you very much for the idea for a workaround.

-- 
Happy hacking
Petter Reinholdtsen

Bug#962080: iputils FTCBFS: does not pass a crossfile to meson

[Helmut Grohne]

Source: iputils
Version: 3:20190709-3
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

iputils fails to cross build from source, because it does not pass a
crossfile to meson. The easiest way of doing so - using
dh_auto_configure - makes iputils cross buildable. Please consider
applying the attached patch.

Helmut
diff --minimal -Nru iputils-20190709/debian/changelog 
iputils-20190709/debian/changelog
--- iputils-20190709/debian/changelog   2020-01-31 00:11:23.0 +0100
+++ iputils-20190709/debian/changelog   2020-06-03 06:50:22.0 +0200
@@ -1,3 +1,10 @@
+iputils (3:20190709-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Let dh_auto_configure pass a crossfile to meson. (Closes: #-1)
+
+ -- Helmut Grohne   Wed, 03 Jun 2020 06:50:22 +0200
+
 iputils (3:20190709-3) unstable; urgency=medium
 
   * Incorporate upstream fix for getaddrinfo handling. Thanks to Benjamin
diff --minimal -Nru iputils-20190709/debian/rules iputils-20190709/debian/rules
--- iputils-20190709/debian/rules   2020-01-16 01:46:33.0 +0100
+++ iputils-20190709/debian/rules   2020-06-03 06:50:22.0 +0200
@@ -13,8 +13,7 @@
dh $@ --buildsystem=meson+ninja --builddirectory=$(BUILD_DIR)
 
 override_dh_auto_configure:
-   meson $(BUILD_DIR) \
-   -Dprefix=/usr \
+   dh_auto_configure -- \
-DBUILD_RARPD=false \
-DBUILD_RDISC=false \
-DBUILD_TFTPD=false \

Bug#962079: Blacklist Expired Certificate: CN=Staat der Nederlanden Root CA - G2

[Michael Shuler]

Package: ca-certificates
Version: 20200601
Severity: normal

Follow up to #955038, expired certificate "Staat der Nederlanden Root CA 
- G2" remains in the Mozilla bundle. If the CA managed their migration 
to the same-named G3 cert, this could be a non-issue, however the 
expired certificate can be blacklisted to effectively remove it.


CCing #955038 (remove in later replies, please) and BCCing the original 
and secondary reporters to acknowledge. Thanks for report and follow up 
on the error.


Kind regards,
Michael Shuler

--
$ openssl x509 -noout -startdate -enddate -in 
/usr/share/ca-certificates/mozilla/Staat_der_Nederlanden_Root_CA_-_G2.crt

notBefore=Mar 26 11:18:17 2008 GMT
notAfter=Mar 25 11:03:10 2020 GMT
$ openssl x509 -noout -startdate -enddate -in 
/usr/share/ca-certificates/mozilla/Staat_der_Nederlanden_Root_CA_-_G3.crt

notBefore=Nov 14 11:28:42 2013 GMT
notAfter=Nov 13 23:00:00 2028 GMT

Bug#962028: ITP: python-rich -- Rich is a Python library for rich text and beautiful formatting in the terminal.

[Mo Zhou]

Hi Sandro,

I saw it. Looking forward to the package. Thanks!

On Tue, Jun 02, 2020 at 11:41:55AM -0400, Sandro Tosi wrote:
> I already filed an ITP for rich:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954301

Bug#962071: gnome: "blank screen" feature does not work

[Julien-Benjamin]

Package: gnome
Version: 1:3.30+1
Severity: important

Dear Maintainer,

With the current (stable) version of the GNOME environment, the power saving 
feature "blank screen"
does not work as intended.

Indeed, after fading out to black, the monitor is still active and displays the 
mouse cursor
and a black screen.

Best regards,

JB

-- System Information:
Debian Release: 10.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.4.0-0.bpo.2-amd64 (SMP w/16 CPU cores)
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.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gnome depends on:
ii  avahi-daemon 0.7-4+b1
ii  cheese   3.31.90-1
ii  cups-pk-helper   0.2.6-1+b1
ii  desktop-base 10.0.2
ii  evolution3.30.5-1.1
ii  evolution-plugins3.30.5-1.1
ii  file-roller  3.30.1-2
ii  gedit-plugins3.30.1-3
ii  gnome-calendar   3.30.1-2
ii  gnome-clocks 3.30.1-2
ii  gnome-color-manager  3.30.0-2
ii  gnome-core   1:3.30+1
ii  gnome-documents  3.31.92-1
ii  gnome-getting-started-docs   3.30.0-1
ii  gnome-maps   3.30.3-1
ii  gnome-music  3.30.2-1
ii  gnome-photos 3.30.1-2
ii  gnome-screenshot 3.30.0-2
ii  gnome-sound-recorder 3.28.2-2~deb10u1
ii  gnome-todo   3.28.1-2
ii  gnome-tweaks 3.30.2-1
ii  gnome-weather3.26.0-5
ii  gstreamer1.0-libav   1.15.0.1+git20180723+db823502-2
ii  gstreamer1.0-plugins-ugly1.14.4-1
ii  libgsf-bin   1.14.45-1
ii  libproxy1-plugin-networkmanager  0.4.15-5
ii  libreoffice-calc 1:6.1.5-3+deb10u6
ii  libreoffice-gnome1:6.1.5-3+deb10u6
ii  libreoffice-impress  1:6.1.5-3+deb10u6
ii  libreoffice-writer   1:6.1.5-3+deb10u6
ii  nautilus-sendto  3.8.6-3
ii  network-manager-gnome1.8.20-1.1
ii  orca 3.30.1-1
ii  rhythmbox3.4.3-2
ii  rhythmbox-plugin-cdrecorder  3.4.3-2
ii  rhythmbox-plugins3.4.3-2
ii  rygel-playbin0.36.2-4
ii  rygel-tracker0.36.2-4
ii  seahorse 3.30.1.1-1
ii  shotwell 0.30.1-1
ii  simple-scan  3.30.1.1-1+b1
ii  totem-plugins3.30.0-4
ii  vinagre  3.22.0-6
ii  vino 3.22.0-5
ii  xdg-user-dirs-gtk0.10-3

Versions of packages gnome recommends:
ii  gnome-games 1:3.30+1
ii  nautilus-extension-brasero  3.12.2-5
ii  transmission-gtk2.94-2

Versions of packages gnome suggests:
pn  alacarte 
pn  empathy  
pn  firefox-esr-l10n-all | firefox-l10n-all  
pn  gnome-remote-desktop 
pn  goobox | sound-juicer
ii  polari   3.30.2-1
pn  webext-ublock-origin 

Versions of packages gnome-core depends on:
ii  adwaita-icon-theme3.30.1-1
ii  at-spi2-core  2.30.0-7
ii  baobab3.30.0-2
ii  caribou   0.4.21-7
ii  chromium  80.0.3987.162-1~deb10u1
ii  dconf-cli 0.30.1-2
ii  dconf-gsettings-backend   0.30.1-2
ii  eog   3.28.4-2+b1
ii  evince3.30.2-3+deb10u1
ii  evolution-data-server 3.30.5-1
ii  firefox-esr   68.8.0esr-1~deb10u1
ii  fonts-cantarell   0.111-2
ii  gdm3  3.30.2-3
ii  gedit 3.30.2-2
ii  gkbd-capplet  3.26.1-1
ii  glib-networking   2.58.0-2
ii  gnome-backgrounds 3.30.0-1
ii  gnome-bluetooth   3.28.2-4~deb10u1
ii  gnome-calculator  3.30.1-2
ii  gnome-characters  3.30.0-2
ii  gnome-contacts3.30.2-1
ii  gnome-control-center  1:3.30.3-2~deb10u1
ii  gnome-disk-utility3.30.2-3
ii  gnome-font-viewer 3.30.0-2
ii  gnome-keyring 3.28.2-5
ii  gnome-logs3.30.0-2
ii  gnome-menus   3.31.4-3
ii  gnome-online-accounts 3.30.1-2
ii  gnome-online-miners   3.30.0-2
ii  gnome-session 3.30.1-2
ii  gnome-settings-daemon  

Bug#962078: apt-listchanges: feature request: combine identical changelog entries from multiple packages

[The Wanderer]

Package: apt-listchanges
Version: 3.22
Severity: wishlist

Dear Maintainer,

>From my perspective, this is technically not a new bug report; it is
another part of the wishlist item reported as bug #841837, which was not
addressed by the change which led that bug report to be closed.

The change made under that bug report resulted in identical binNMU
entries being folded together, and listed with one entry per identical
changelog, at the end of the list. This is a major improvement, and
addresses the large majority of cases where such identical entries made
change lists hard to read.

However, as mentioned in that wishlist bug report, binNMUs are not the
only context in which substantially-identical changelogs occur:

> (At the moment, I am also seeing a mass set of identical entries in
> an apparently maintainer-initiated update to set of KDE-related
> packages; a couple of dozen or so packages seem to have been updated
> simultaneously to the same version, with identical or near-identical
> changes in each. This sort of issue thus is not exclusive to such
> automatic rebuilds, it's just most common there.)

I am once again seeing this, albeit at a smaller scale, with a mass
update to KDE-related packages. Specifically (although I cannot
guarantee that this is the full set of affected packages, without
spending more time on analyzing each changelog entry than I want to
invest), kcrash, kdbusaddons, and kemoticons have changelog entries for
version 5.70.0-1 which differ only in the package name and the exact
timestamp.

(Some other packages involved in the same mass update seem to include a
changelog section for that version which is identical to the one from
the packages named, but also have an additional changelog section for
the same version to describe other changes which are specific to each
package. Otherwise, there would probably be closer to a dozen packages
which I could easily list. Splitting out such identical sections from
otherwise-differing changelog entries would clearly do more harm than
good.)

Part of the request made under that bug report was for all such
identical changelog entries to be folded together, much (if not
necessarily exactly) as is now done with binNMUs; whether the identical
changelog entries result from binNMUs or from something else is not
relevant to that purpose.

Please either extend the current binNMU folding to catch other types of
identical changelog entries and treat them similarly, or add an
additional feature (possibly requiring enablement via an option) to
cause such additional identical entries to be folded together in a
similar way.

(I can easily see that this may be a less commonly desired behavior, and
that indeed some people may prefer to have it not happen, given that it
would break up the orderly listing of package versions in cases where
other versions' changelog entries to the same packages are not similarly
identical. As such, making this an optional behavior which has to be
enabled would probably be more appropriate than making it the default.)

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

Kernel: Linux 5.6.0-1-amd64 (SMP w/12 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages apt-listchanges depends on:
ii  apt2.1.5
ii  debconf [debconf-2.0]  1.5.74
ii  python33.8.2-3
ii  python3-apt2.1.3
ii  python3-debconf1.5.74
ii  sensible-utils 0.0.12+nmu1
ii  ucf3.0042

apt-listchanges recommends no packages.

Versions of packages apt-listchanges suggests:
ii  chromium [www-browser] 81.0.4044.92-1
ii  dillo [www-browser]3.0.5-7
ii  elinks [www-browser]   0.13.1-4
ii  exim4-daemon-light [mail-transport-agent]  4.93-16
ii  iceweasel [www-browser]38.8.0esr-1~deb8u1
ii  kterm [x-terminal-emulator]6.2.0-46.2
ii  links [www-browser]2.20.2-1+b1
ii  lynx [www-browser] 2.9.0dev.5-1
ii  python3-gi 3.36.0-3
ii  w3m [www-browser]  0.5.3-38
ii  xterm [x-terminal-emulator]356-1

-- debconf information:
* apt-listchanges/save-seen: true
* apt-listchanges/which: both
* apt-listchanges/email-format: text
* apt-listchanges/email-address: root
* apt-listchanges/reverse: false
* apt-listchanges/no-network: false
* apt-listchanges/frontend: pager
* apt-listchanges/headers: false
* apt-listchanges/confirm: true

Bug#926409: lintian: autopkgtest takes very long to finish

[Mattia Rizzolo]

On Wed, 3 Jun 2020, 1:09 am Felix Lechner, 
wrote:

> Hi Chris,
>
> On Fri, Apr 5, 2019 at 4:33 AM Iain Lane  wrote:
> >
> > We do similar in some pkg-gnome packages, for example glib2.0 ships a
> > -tests package that contains "installed tests" which are compiled as
> > part of the package build and then executed during the autopkgtests.
>
> Should we ship all built test packages as part of our releases? I
> can't think of a better way to close this bug.


Now lintian autopkgtests take approximately 1 hour everywhere I checked.
Honestly, I believe 1 hour to be acceptable.


>

Bug#962077: audacity: Can't set italian language

[Teo]

Package: audacity
Version: 2.2.2-1+b1
Severity: important
Tags: l10n

Like the title, I can't use audacity in my language, because I don't find it in
the "interface->language" menu. I correctly see many languages, but not
italian.
ps: in debian for amd64 I use it in italian very well.



-- System Information:
Debian Release: 10.4
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

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

Versions of packages audacity depends on:
ii  audacity-data   2.2.2-1
ii  libasound2  1.1.8-1
ii  libavcodec587:4.1.4-1~deb10u1
ii  libavformat58   7:4.1.4-1~deb10u1
ii  libavutil56 7:4.1.4-1~deb10u1
ii  libc6   2.28-10
ii  libexpat1   2.2.6-2+deb10u1
ii  libflac++6v51.3.2-3
ii  libflac81.3.2-3
ii  libgcc1 1:8.3.0-6
ii  libgdk-pixbuf2.0-0  2.38.1+dfsg-1
ii  libglib2.0-02.58.3-2+deb10u2
ii  libgtk2.0-0 2.24.32-3
ii  libid3tag0  0.15.1b-14
ii  liblilv-0-0 0.24.2~dfsg0-2
ii  libmad0 0.15.1b-10
ii  libmp3lame0 3.100-2+b1
ii  libogg0 1.3.2-1+b1
ii  libportaudio2   19.6.0-1
ii  libportsmf0 0.1~svn20101010-5
ii  libsndfile1 1.0.28-6
ii  libsoundtouch1  2.1.2+ds1-1
ii  libsoxr00.1.2-3
ii  libstdc++6  8.3.0-6
ii  libsuil-0-0 0.10.0~dfsg0-1
ii  libtwolame0 0.3.13-4
ii  libvamp-hostsdk3v5  2.7.1~repack0-1
ii  libvorbis0a 1.3.6-2
ii  libvorbisenc2   1.3.6-2
ii  libvorbisfile3  1.3.6-2
ii  libwxbase3.0-0v53.0.4+dfsg-8
ii  libwxgtk3.0-0v5 3.0.4+dfsg-8

audacity recommends no packages.

Versions of packages audacity suggests:
pn  ladspa-plugin  

-- no debconf information

Bug#962076: clementine: Clementine crash

[Gleisson Jesuino Joaquim Cardoso]

Package: clementine
Version: 1.3.1+git609-g623a53681+dfsg-1
Severity: important

Dear Maintainer,

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

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

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


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

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

Versions of packages clementine depends on:
ii  gstreamer1.0-plugins-base   1.14.4-2
ii  gstreamer1.0-plugins-good   1.14.4-1
ii  gstreamer1.0-plugins-ugly   1.14.4-1
ii  libc6   2.28-10
ii  libcdio18   2.0.0-2
ii  libchromaprint1 1.4.3-3
ii  libcrypto++65.6.4-8
ii  libfftw3-double33.3.8-2
ii  libgcc1 1:8.3.0-6
ii  libgdk-pixbuf2.0-0  2.38.1+dfsg-1
ii  libglib2.0-02.58.3-2+deb10u2
ii  libgpod40.8.3-13
ii  libgstreamer-plugins-base1.0-0  1.14.4-2
ii  libgstreamer1.0-0   1.14.4-1
ii  libimobiledevice6   1.2.1~git20181030.92c5462-2
ii  liblastfm5-11.0.9-1+b11
ii  libmtp9 1.1.16-2
ii  libmygpo-qt5-1  1.1.0-3
ii  libplist3   2.0.1~git20190104.3f96731-1
ii  libprojectm2v5  2.1.0+dfsg-4+b4
ii  libprotobuf17   3.6.1.3-2
ii  libpulse0   12.2-4+deb10u1
ii  libqt5concurrent5   5.11.3+dfsg1-1+deb10u3
ii  libqt5core5a5.11.3+dfsg1-1+deb10u3
ii  libqt5dbus5 5.11.3+dfsg1-1+deb10u3
ii  libqt5gui5  5.11.3+dfsg1-1+deb10u3
ii  libqt5network5  5.11.3+dfsg1-1+deb10u3
ii  libqt5opengl5   5.11.3+dfsg1-1+deb10u3
ii  libqt5sql5  5.11.3+dfsg1-1+deb10u3
ii  libqt5widgets5  5.11.3+dfsg1-1+deb10u3
ii  libqt5x11extras55.11.3-2
ii  libqt5xml5  5.11.3+dfsg1-1+deb10u3
ii  libsqlite3-03.27.2-3
ii  libstdc++6  8.3.0-6
ii  libtag1v5   1.11.1+dfsg.1-0.3+deb10u1
ii  libx11-62:1.6.7-1
ii  projectm-data   2.1.0+dfsg-4
ii  zlib1g  1:1.2.11.dfsg-1

Versions of packages clementine recommends:
ii  gstreamer1.0-pulseaudio  1.14.4-1

Versions of packages clementine suggests:
ii  gstreamer1.0-plugins-bad  1.14.4-1+b1

-- no debconf information

Bug#961994: src:libcatmandu-perl: fails to migrate to testing for too long: causes autopkgtest regression

[Andreas Beckmann]

Hi Paul,

On Mon, 1 Jun 2020 19:54:29 +0200 Paul Gevers  wrote:
> Source: libcatmandu-perl
> Version: 1.2012-1
> Severity: serious
> Control: close -1 1.2012-1

the 'found' version is wrong. Script error?


Andreas

Bug#962075: adwaita-icon-theme: Missing same icon

[Teo]

Package: adwaita-icon-theme
Version: 3.36.1-2
Severity: normal
Tags: patch

Adwaita icon pack is missing same icon, like gnome-nettool and iso file that I
see as generic file.



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

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

Versions of packages adwaita-icon-theme depends on:
ii  gtk-update-icon-cache  3.24.20-1
ii  hicolor-icon-theme 0.17-2

Versions of packages adwaita-icon-theme recommends:
ii  librsvg2-common  2.48.4+dfsg-1

adwaita-icon-theme suggests no packages.

-- no debconf information

Bug#926409: lintian: autopkgtest takes very long to finish

[Felix Lechner]

Hi Chris,

On Fri, Apr 5, 2019 at 4:33 AM Iain Lane  wrote:
>
> We do similar in some pkg-gnome packages, for example glib2.0 ships a
> -tests package that contains "installed tests" which are compiled as
> part of the package build and then executed during the autopkgtests.

Should we ship all built test packages as part of our releases? I
can't think of a better way to close this bug.

Kind regards
Felix Lechner

Bug#961796: ITP: eclipse-linuxtools -- framework for profiling tools for Eclipse CDT

[Sudip Mukherjee]

Control: unblock -1 by 961891

On Fri, May 29, 2020 at 12:14:49PM +0100, Sudip Mukherjee wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Sudip Mukherjee 
> Control: block 943552 by -1
> 
> * Package name: eclipse-linuxtools
>   Version : v7.6.0

Correction: I will need v7.4.0 (for now) to package the tracecompass
I am trying to package. And eclipse-linuxtools_7.4.0 uses the old version
of swtcharts which is already in Debian and so, #961891 is not a blocker
for this.

--
Regards
Sudip

Bug#962074: blender: crash in an assertion and doubt about CMAKE_BUILD_TYPE

[Antonio Ospite]

Package: blender
Version: 2.82.a+dfsg-1+b2
Severity: normal
Tags: upstream

Dear Maintainer,

I ran into the upstream bug T75822[1] which is caused by an assertion.

TBH being able to reproduce that bug with the blender executable shipped
in Debian was a little surprising because it is supposed to only happen
in debug builds.

The assertion is enabled in Debian because dh runs cmake with
CMAKE_BUILD_TYPE=None which in particular results in NDEBUG not being
defined, which makes asserts() to run.

It turns out that  having CMAKE_BUILD_TYPE=None by default is on
purpose[2] to make sure that cmake does not blindly override global
compilation flags if the packager didn't ask that explicitly, some
discussion can be found in [3].

My direct concern would be to just have blender not crashing, and
upstream is working on a fix[4] for that.

However the issue also raised a question about whether a Release build
type should be used for the blender Debian executable; or if at least
assertions should be disabled by defining NDEBUG.

The upstream maintainer for the linux platform would also be
interested[5] in this.

Do you have an opinion?

Thanks,
   Antonio

[1] https://developer.blender.org/T75822
[2] 
https://sources.debian.org/src/debhelper/13.1/lib/Debian/Debhelper/Buildsystem/cmake.pm/#L16
[3] https://github.com/ros-infrastructure/bloom/issues/327
[4] https://developer.blender.org/D7595
[5] https://developer.blender.org/T75822#942660

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

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

Versions of packages blender depends on:
ii  blender-data  2.82.a+dfsg-1
ii  fonts-dejavu  2.37-2
ii  libavcodec58  7:4.2.2-1+b1
ii  libavdevice58 7:4.2.2-1+b1
ii  libavformat58 7:4.2.2-1+b1
ii  libavutil56   7:4.2.2-1+b1
ii  libboost-locale1.67.0 1.67.0-18
ii  libc6 2.30-8
ii  libfftw3-double3  3.3.8-2
ii  libfreetype6  2.10.1-2
ii  libgcc-s1 10.1.0-3
ii  libgl11.3.1-1
ii  libglew2.12.1.0-4+b1
ii  libgomp1  10.1.0-3
ii  libilmbase24  2.3.0-6
ii  libjack0 [libjack-0.125]  1:0.125.0-3+b1
ii  libjemalloc2  5.2.1-1
ii  libjpeg62-turbo   1:1.5.2-2+b1
ii  libopenal11:1.19.1-1+b1
ii  libopencolorio1v5 1.1.1~dfsg0-6+b1
ii  libopenexr24  2.3.0-6
ii  libopenimageio2.1 2.1.15.0~dfsg0-1
ii  libopenjp2-7  2.3.1-1
ii  libopenvdb7.0 7.0.0-3
ii  libosdcpu3.4.33.4.3-3
ii  libosdgpu3.4.33.4.3-3
ii  libpcre3  2:8.39-12+b1
ii  libpng16-16   1.6.37-2
ii  libpython3.8  3.8.3-1
ii  libsdl1.2debian   1.2.15+dfsg2-5
ii  libsndfile1   1.0.28-8
ii  libspnav0 0.2.3-1+b2
ii  libstdc++610.1.0-3
ii  libswscale5   7:4.2.2-1+b1
ii  libtbb2   2020.2-2
ii  libtiff5  4.1.0+git191117-2
ii  libx11-6  2:1.6.9-2+b1
ii  libxfixes31:5.0.3-2
ii  libxi62:1.7.9-1
ii  libxml2   2.9.10+dfsg-5
ii  libxrender1   1:0.9.10-1
ii  libxxf86vm1   1:1.1.4-1+b2
ii  zlib1g1:1.2.11.dfsg-2

blender recommends no packages.

blender suggests no packages.

-- no debconf information
-- 
Antonio Ospite
https://ao2.it
https://twitter.com/ao2it

A: Because it messes up the order in which people normally read text.
   See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?

Bug#962001: austin: autopkgtest regression: src/austin: No such file or directory

[Gabriele]

Hi Paul

Many thanks for your reply. I have had a look at the logs linked on this page

https://ci.debian.net/packages/a/austin/testing/amd64/

The only version that passes is v1.0.0 and by looking at the logs of
v0.7.0 and v1.0.1, which fail, it's a miracle that v1.0.0 even passes.
Indeed v0.7.0 and v1.0.1 fail for the very same reason: the binary
used for the tests, src/austin, is simply not there. Why it is there
for the v1.0.0 I don't know, so it looks like the problem is with
v1.0.0 paradoxically.

This is the diff inside the debian/ folder between v1.0.0 and v1.0.1
(TLDR: only debian/austin.1, debian/changelog and debian/copyright
have changed)

$ git diff v1.0.0 v1.0.1 debian/
diff --git a/debian/austin.1 b/debian/austin.1
index 95a8ab0..3452e92 100644
--- a/debian/austin.1
+++ b/debian/austin.1
@@ -1,7 +1,7 @@
 .\" DO NOT MODIFY THIS FILE!  It was generated by help2man 1.47.6.
-.TH AUSTIN "1" "October 2019" "austin 1.0.0" "User Commands"
+.TH AUSTIN "16" "May 2020" "austin 1.0.1" "User Commands"
 .SH NAME
-austin \- manual page for austin 1.0.0
+austin \- manual page for austin 1.0.1
 .SH SYNOPSIS
 .B austin
 [\fI\,OPTION\/\fR...] \fI\,command \/\fR[\fI\,ARG\/\fR...]
diff --git a/debian/changelog b/debian/changelog
index 6d31034..352af1a 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+austin (1.0.1-1) unstable; urgency=medium
+
+  * Fixed support for Python 3.8
+
+ -- Gabriele N. Tornetta   Sat, 16 May 2020
12:36:00 +0100
+
+
 austin (1.0.0-1) unstable; urgency=medium

   * Added support for multi-process Python applications
diff --git a/debian/copyright b/debian/copyright
index 954ddfd..2f08861 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -4,7 +4,7 @@ Upstream-Contact: Gabriele N. Tornetta 
 Source: https://github.com/P403n1x87/austin

 Files: *
-Copyright: 2018-2019 Gabriele N. Tornetta 
+Copyright: 2018-2020 Gabriele N. Tornetta 
 License: GPL-3+

 License: GPL-3+



This is the diff inside the test/ folder (TLDR: only a test condition
has changed, but the problem is that bats cannot find the binary
src/austin, so it can't even get to the point where the test logic has
changed).

$ git diff v1.0.0 v1.0.1 test/
diff --git a/test/test_fork_mp.bats b/test/test_fork_mp.bats
index 391563b..797e0d1 100644
--- a/test/test_fork_mp.bats
+++ b/test/test_fork_mp.bats
@@ -18,9 +18,8 @@ invoke_austin() {
 echo "   - Check expected number of processes."
 expected=3
 n_procs=$( echo "$output" | sed -r 's/Process ([0-9]+);.+/\1/' |
sort | uniq | wc -l )
-echo " Expected $expected and got $n_procs"
-if [ $n_procs != $expected ]
-then continue; fi
+echo " Expected at least $expected and got $n_procs"
+if [ $n_procs < $expected ]; then continue; fi

 echo "   - Check output contains frames."
 if echo "$output" | grep -q "do
(test/target_mp.py);L[[:digit:]]*;fact (test/target_mp.py);L"
@@ -39,7 +38,7 @@ invoke_austin() {
 echo ""
 echo
 echo "$output"
-echo
+echo
 false
   fi
 }



Hence, to the best of my knowledge, there are no changes in the
debian/ area that would cause the binary in src/ to be there unless it
accidentally ended up, say, in the source tarball.

My next question to you is then: where is the binary supposed to be
found during autopkgtest? Can I assume it will be on the PATH during
testing, so that I can invoke it simply with "austin"? Or do I need to
specify a precise path?

Thanks for your support thus far.

Cheers,
Gabriele

Bug#962073: alsa-info is calling home without asking

[Christoph Berg]

Package: alsa-utils
Version: 1.2.2-1
Severity: serious

Hi,

I just launched alsa-info and was surprised that it presented me with
this popup box:

┌───┐
│ Newer version of ALSA-Info has been   │
│ found │
│   │
│ Do you wish to download it?   │
├───┤
│ < Yes > < No  >   │
└───┘

Note that this box comes before it asks if the generated report should
be uploaded somewhere.

I don't think it is appropriate for a simple CLI utility to call home
without asking first.

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

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

Versions of packages alsa-utils depends on:
ii  kmod  27+20200310-2
ii  libasound21.2.2-2.1
ii  libatopology2 1.2.2-2.1
ii  libc6 2.30-8
ii  libfftw3-single3  3.3.8-2
ii  libncursesw6  6.2-1
ii  libsamplerate00.1.9-2
ii  libtinfo6 6.2-1
ii  lsb-base  11.1.0

alsa-utils recommends no packages.

Versions of packages alsa-utils suggests:
ii  dialog  1.3-20190808-1

-- no debconf information

Christoph

Bug#962072: boost1.71: Please add small change in debian/rules to fix FTBFS on m68k

[John Paul Adrian Glaubitz]

Source: boost1.71
Severity: normal
Tags: patch
User: debian-...@lists.debian.org
Usertags: m68k

Hi!

The build of src:boost1.71 currently fails on m68k with:

 dh_install --list-missing
 dh_install: warning: Please use dh_missing --list-missing/--fail-missing 
instead
 dh_install: warning: This feature will be removed in compat 12.
 dh_install: warning: Cannot find (any matches for) 
"debian/tmp/usr/lib/m68k-linux-gnu/libboost_stacktrace_backtrace.so.1.71.0" 
(tried in ., debian/tmp)
 dh_install: warning: libboost-stacktrace1.71.0 missing files: 
debian/tmp/usr/lib/m68k-linux-gnu/libboost_stacktrace_backtrace.so.1.71.0
 dh_install: warning: Cannot find (any matches for) 
"debian/tmp/usr/lib/m68k-linux-gnu/libboost_stacktrace_backtrace.a" (tried in 
., debian/tmp)
 dh_install: warning: libboost-stacktrace1.71-dev missing files: 
debian/tmp/usr/lib/m68k-linux-gnu/libboost_stacktrace_backtrace.a
 dh_install: error: missing files, aborting

This happens because libboost_stacktrace_backtrace.so is not build on m68k and
can be simply fixed with the following small change in debian/rules:

--- old/boost1.71-1.71.0/debian/rules   2020-02-04 22:08:14.0 +0100
+++ new/boost1.71-1.71.0/debian/rules   2020-06-02 18:43:19.458126971 +0200
@@ -16,7 +16,11 @@
 boost_lib_math := math_c99 math_c99f math_tr1 math_tr1f
 boost_lib_math_long_double := math_c99l math_tr1l
 boost_lib_serialization := serialization wserialization
+ifeq ($(DEB_BUILD_ARCH), m68k)
+boost_lib_stacktrace := stacktrace_noop stacktrace_addr2line stacktrace_basic
+else
 boost_lib_stacktrace := stacktrace_noop stacktrace_addr2line 
stacktrace_backtrace stacktrace_basic
+endif
 boost_lib_test := prg_exec_monitor test_exec_monitor unit_test_framework

Could you include that change in the next upload?

Thanks,
Adrian

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
--- old/boost1.71-1.71.0/debian/rules   2020-02-04 22:08:14.0 +0100
+++ new/boost1.71-1.71.0/debian/rules   2020-06-02 18:43:19.458126971 +0200
@@ -16,7 +16,11 @@
 boost_lib_math := math_c99 math_c99f math_tr1 math_tr1f
 boost_lib_math_long_double := math_c99l math_tr1l
 boost_lib_serialization := serialization wserialization
+ifeq ($(DEB_BUILD_ARCH), m68k)
+boost_lib_stacktrace := stacktrace_noop stacktrace_addr2line stacktrace_basic
+else
 boost_lib_stacktrace := stacktrace_noop stacktrace_addr2line 
stacktrace_backtrace stacktrace_basic
+endif
 boost_lib_test := prg_exec_monitor test_exec_monitor unit_test_framework
 
 pyversions = $(shell py3versions -rv)

Bug#892325: Outdated Linphone packets

[Bernhard Schmidt]

Hi Julien,

> I'm not fully aware about the packaging process on Debian but Linphone
> Desktop 4.2 will be based on 4.4 of SDK for sure.
> 
> Even it is currently on development, the 4.4 is near to be released and
> is enough stable to begin to work with. In addition, I think that you
> will have to use all 4.4 libraries because there is no point to mix
> versions. I can confirm you that the Doxygen issue is fixed on this
> version.

So if I get you correctly, the only supported way to build and run
linphone-desktop 4.2.x will with all of
bctoolbox/belle-sip/ortp/mediastreamer2/bzrtp/belr/belcard/liblinphone
4.4.x?

When updating your libraries, will newer versions (i.e. 4.4) either be
API/ABI compatible with the previous versions (i.e. 4.3) or have a
SONAME bump? Sid/Testing is basically a rolling distribution, we need to
be able to start upgrading for example belle-sip with the new upstream
version without fatally breaking the not-yet-updated part.

In other words, I have understood that building (for example) linphone
4.4 with belle-sip/mediastreamer 4.3 is not supported. Is building
liblinphone 4.3 with belle-sip/mediastreamer 4.4 supported?

Debian tries to have as relaxed dependencies as possible. If for example
liblinphone would be built with belle-sip 4.4 present, but only use
library symbols that are already present in belle-sip 4.3.1, the build
system would express a dependency of "libbellesip0 (>= 4.3.1)". In
general Debian would allow a partial upgrade, a runtime error would be a
bug. So if that's the case we need to make sure all libraries migrate at
once and have very tight relationships (both at build-time and for the
binary packages).

https://wiki.debian.org/UpstreamGuide has a lot of information.

> By the way, an Appimage on the last version of the application is based
> on 4.4.0-beta-13 and can be found here :
> https://www.linphone.org/snapshots/AppImages/Linphone-4.2.0-alpha.63+59c4cc1.AppImage

If your whole development model is catered around AppImage (or snaps)
and basically only supports atomically replacing the whole stack and
building it from a single repository I would rather not have linphone in
Debian at all. After all we have to support it for several years after
release.

Bernhard

Bug#962051: segfault when locking screen

[Stefano Zacchiroli]

forcemerge 959883 962051
thanks

On Tue, Jun 02, 2020 at 09:54:15PM +0100, Simon McVittie wrote:
> On Tue, 02 Jun 2020 at 17:22:54 +0200, Stefano Zacchiroli wrote:
> > heya, since yesterday under Debian/testing gnome-shell crashes (and then
> > restarts) when trying to lock screen.
> 
> This seems like #959883. Please try disabling any extensions you have
> enabled, and/or upgrading to the snapshot in experimental.

Yup, that was it! I guess I missed it because I've only looked at open
bugs, my apologies. Upgrading to the experimental snapshot fixed the
issue for me too.

Merging/closing.

Thanks for your super quick solution!
Cheers
-- 
Stefano Zacchiroli . z...@upsilon.cc . upsilon.cc/zack . . o . . . o . o
Computer Science Professor . CTO Software Heritage . . . . . o . . . o o
Former Debian Project Leader & OSI Board Director  . . . o o o . . . o .
« the first rule of tautology club is the first rule of tautology club »

Bug#962070: regina-normal: FTBFS with boost 1.71

[Sebastian Ramacher]

Source: regina-normal
Version: 5.1-6
Severity: serious
Tags: ftbfs sid bullseye
Justification: fails to build from source (but built successfully in the past)
User: team+bo...@tracker.debian.org
Usertags: boost1.71
Control: block 961995 by -1

regina-normal FTBFS with boost 1.71:
| /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libboost_python38.so.1.71.0: undefined 
reference to `PyUnicode_InternFromString'
| /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libboost_python38.so.1.71.0: undefined 
reference to `_Py_Dealloc'
| /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libboost_python38.so.1.71.0: undefined 
reference to `PyModule_Create2'
| /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libboost_python38.so.1.71.0: undefined 
reference to `PyType_GetFlags'
| /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libboost_python38.so.1.71.0: undefined 
reference to `_Py_fopen'
| /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libboost_python38.so.1.71.0: undefined 
reference to `PyUnicode_FromString'
| /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libboost_python38.so.1.71.0: undefined 
reference to `PyBytes_AsString'
| /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libboost_python38.so.1.71.0: undefined 
reference to `PyBytes_Size'
| /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libboost_python38.so.1.71.0: undefined 
reference to `PyUnicode_AsWideChar'
| /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libboost_python38.so.1.71.0: undefined 
reference to `PyUnicode_FromEncodedObject'
| /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libboost_python38.so.1.71.0: undefined 
reference to `PyUnicode_AsUTF8'
| /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libboost_python38.so.1.71.0: undefined 
reference to `PyUnicode_AsUTF8String'
| /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libboost_python38.so.1.71.0: undefined 
reference to `PyUnicode_FromFormat'
| /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libboost_python38.so.1.71.0: undefined 
reference to `_Py_tracemalloc_config'
| /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libboost_python38.so.1.71.0: undefined 
reference to `PyUnicode_FromStringAndSize'
| /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libboost_python38.so.1.71.0: undefined 
reference to `_PyTraceMalloc_NewReference'
| collect2: error: ld returned 1 exit status
| make[4]: *** [qtui/src/CMakeFiles/regina-gui.dir/build.make:1779: 
qtui/src/regina-gui] Error 1

See
https://buildd.debian.org/status/fetch.php?pkg=regina-normal=amd64=5.1-6%2Bb4=1591128985=0

This looks like the package is trying to embed the Python interpreter,
so it is supposed to link with it itself.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#962051: segfault when locking screen

[Simon McVittie]

On Tue, 02 Jun 2020 at 17:22:54 +0200, Stefano Zacchiroli wrote:
> heya, since yesterday under Debian/testing gnome-shell crashes (and then
> restarts) when trying to lock screen.

This seems like #959883. Please try disabling any extensions you have
enabled, and/or upgrading to the snapshot in experimental.

smcv

Bug#962069: synfig: FTBFS with icu 67

[Sebastian Ramacher]

Source: synfig
Version: 1.2.2+dfsg-2
Severity: serious
Tags: ftbfs sid bullseye
Justification: fails to build from source (but built successfully in the past)
Control: block 960193 by -1

synfig fails to build with icu 67:
| In file included from /usr/include/unicode/uenum.h:23,
|  from /usr/include/unicode/ucnv.h:53,
|  from /usr/include/libxml2/libxml/encoding.h:31,
|  from /usr/include/libxml2/libxml/parser.h:810,
|  from /usr/include/libxml2/libxml/globals.h:18,
|  from /usr/include/libxml2/libxml/threads.h:35,
|  from /usr/include/libxml2/libxml/xmlmemory.h:218,
|  from /usr/include/libxml2/libxml/tree.h:1307,
|  from savecanvas.cpp:75:
| /usr/include/unicode/localpointer.h:67:1: error: template with C linkage
|67 | template
|   | ^~~~
| savecanvas.cpp:74:1: note: ‘extern "C"’ linkage started here
|74 | extern "C" {
|   | ^~

See
https://buildd.debian.org/status/fetch.php?pkg=synfig=amd64=1.2.2%2Bdfsg-2%2Bb1=1591129855=0

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#962068: stretch-pu: package dbus/1.10.30-0+deb9u1

[Simon McVittie]

Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu

dbus 1.10.30 fixes a local denial of service vulnerability for which
the Security Team have indicated they do not intend to issue a DSA
(the same one as 1.12.18).

If possible I would like to continue to fix dbus issues in stretch via
new upstream releases; this one only contains the CVE fix, plus its
regression test and the usual Autotools noise.

Proposed diff (modulo `dch -r`) attached, filtered through:

git diff --stat -p origin/debian/stretch.. | \
filterdiff -p1 \
--exclude=Makefile.in --exclude='**/Makefile.in' \
--exclude=aclocal.m4 \
--exclude=aminclude_static.am \
--exclude=build-aux/compile \
--exclude=build-aux/depcomp \
--exclude=build-aux/install-sh \
--exclude=build-aux/ltmain.sh \
--exclude=build-aux/missing \
--exclude=build-aux/tap-driver.sh \
--exclude=configure \
--exclude=m4/libtool.m4

Thanks,
smcv
 Makefile.in| 39 --
 NEWS   | 33 +
 aclocal.m4 | 52 --
 build-aux/compile  |  6 +++---
 build-aux/depcomp  |  2 +-
 build-aux/install-sh   | 13 +++-
 build-aux/ltmain.sh| 10 +
 build-aux/missing  |  2 +-
 build-aux/tap-driver.sh|  2 +-
 bus/Makefile.in|  4 ++--
 bus/connection.c   |  7 ---
 configure  | 36 +---
 configure.ac   |  4 ++--
 dbus/Makefile.in   |  4 ++--
 dbus/dbus-sysdeps-unix.c   | 32 +---
 debian/changelog   |  8 +++
 doc/Makefile.in|  4 ++--
 m4/libtool.m4  |  6 +++---
 test/Makefile.in   |  4 ++--
 test/fdpass.c  | 14 +
 test/name-test/Makefile.in |  4 ++--
 tools/Makefile.in  |  4 ++--
 22 files changed, 189 insertions(+), 101 deletions(-)

diff --git a/NEWS b/NEWS
index 46652396..9b33a786 100644
--- a/NEWS
+++ b/NEWS
@@ -1,3 +1,36 @@
+dbus 1.10.x end-of-life plans
+==
+
+The dbus 1.10.x branch was originally released in 2015. It currently
+receives security-fix releases whenever necessary, but it is planned to
+reach end-of-life status at the end of Debian 9's official security
+support (approximately July 2020). If you are a dbus downstream
+maintainer in a long-lived OS distribution and you want to use the
+upstream dbus-1.10 git branch as a place to share backported security
+fixes with other distributions, please contact the dbus maintainers via
+the dbus-security mailing list on lists.freedesktop.org.
+
+dbus 1.10.30 (2020-06-02)
+==
+
+The “centaur bus” release.
+
+Denial of service fixes:
+
+• CVE-2020-12049: If a message contains more file descriptors than can
+  be sent, close those that did get through before reporting error.
+  Previously, a local attacker could cause the system dbus-daemon (or
+  another system service with its own DBusServer) to run out of file
+  descriptors, by repeatedly connecting to the server and sending fds that
+  would get leaked.
+  Thanks to Kevin Backhouse of GitHub Security Lab.
+  (dbus#294, GHSL-2020-057; Simon McVittie)
+
+Other fixes:
+
+• Fix a crash when the dbus-daemon is terminated while one or more
+  monitors are active (dbus#291, dbus!140; Simon McVittie)
+
 dbus 1.10.28 (2019-06-11)
 ==
 
diff --git a/bus/connection.c b/bus/connection.c
index 31ed6be7..05daa6a4 100644
--- a/bus/connection.c
+++ b/bus/connection.c
@@ -540,9 +540,6 @@ bus_connections_unref (BusConnections *connections)
 
   _dbus_assert (connections->n_incomplete == 0);
 
-  /* drop all monitors */
-  _dbus_list_clear (>monitors);
-
   /* drop all real connections */
   while (connections->completed != NULL)
 {
@@ -558,6 +555,10 @@ bus_connections_unref (BusConnections *connections)
 
   _dbus_assert (connections->n_completed == 0);
 
+  /* disconnecting all the connections should have emptied the list of
+   * monitors (each link is removed in bus_connection_disconnected) */
+  _dbus_assert (connections->monitors == NULL);
+
   bus_expire_list_free (connections->pending_replies);
   
   _dbus_loop_remove_timeout (bus_context_get_loop (connections->context),
diff --git a/configure.ac b/configure.ac
index 04ebae5f..ee3da6a9 100644
--- a/configure.ac
+++ b/configure.ac
@@ -3,7 +3,7 @@ AC_PREREQ([2.63])
 
 m4_define([dbus_major_version], [1])
 m4_define([dbus_minor_version], [10])
-m4_define([dbus_micro_version], [28])
+m4_define([dbus_micro_version], [30])
 m4_define([dbus_version],
   [dbus_major_version.dbus_minor_version.dbus_micro_version])
 AC_INIT([dbus],[dbus_version],[https://bugs.freedesktop.org/enter_bug.cgi?product=dbus],[dbus])
@@ -38,7 +38,7 @@ LT_CURRENT=17
 
 ## increment any time the source changes; set to
 ##  0 if you increment CURRENT
-LT_REVISION=16

Bug#962067: buster-pu: package dbus/1.12.18-0+deb10u1

[Simon McVittie]

Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu

dbus 1.12.18 fixes a local denial of service vulnerability for which
the Security Team have indicated they do not intend to issue a DSA.

If possible I would like to use upstream 1.12.x versions of dbus for
buster (security and) stable updates, similar to the policy used in
stretch and jessie. This branch includes security fixes and selected
non-intrusive bug fixes (and unfortunately also the usual Autotools
noise).

Proposed diff (modulo `dch -r -D buster`) attached, filtered through:

git diff --stat -p origin/debian/buster.. | \
filterdiff -p1 \
--exclude=Makefile.in --exclude='**/Makefile.in' \
--exclude=aclocal.m4 \
--exclude=aminclude_static.am \
--exclude=build-aux/compile \
--exclude=build-aux/depcomp \
--exclude=build-aux/install-sh \
--exclude=build-aux/ltmain.sh \
--exclude=build-aux/missing \
--exclude=build-aux/tap-driver.sh \
--exclude=configure \
--exclude=m4/libtool.m4

Thanks,
smcv
 Makefile.in|  42 ++--
 NEWS   |  39 
 aclocal.m4 | 240 ++---
 aminclude_static.am|   2 +-
 build-aux/compile  |   6 +-
 build-aux/depcomp  |   2 +-
 build-aux/install-sh   |  13 +-
 build-aux/ltmain.sh|  10 +-
 build-aux/missing  |   2 +-
 build-aux/tap-driver.sh|   2 +-
 bus/Makefile.in|   6 +-
 bus/connection.c   |   7 +-
 cmake/tools/CMakeLists.txt |   1 +
 configure  |  70 +++---
 configure.ac   |   4 +-
 dbus/Makefile.in   |   6 +-
 dbus/dbus-message.c|  14 +-
 dbus/dbus-sysdeps-unix.c   |  32 +--
 debian/changelog   |  11 +
 debian/gbp.conf|   2 +-
 ...-Don-t-test-fd-limits-if-in-an-unprivileg.patch |  83 ---
 debian/patches/series  |   1 -
 doc/Makefile.in|   6 +-
 doc/dbus-daemon.1.xml.in   |   2 +-
 doc/dbus-send.1.xml.in |  12 +-
 m4/libtool.m4  |   6 +-
 test/Makefile.in   |   6 +-
 test/dbus-daemon.c |  30 ++-
 test/fdpass.c  |  14 ++
 test/name-test/Makefile.in |   4 +-
 tools/Makefile.in  |   4 +-
 31 files changed, 314 insertions(+), 365 deletions(-)

diff --git a/NEWS b/NEWS
index 07a933a4..a38c5992 100644
--- a/NEWS
+++ b/NEWS
@@ -1,3 +1,42 @@
+dbus 1.12.18 (2020-06-02)
+=
+
+The “telepathic vines” release.
+
+Denial of service fixes:
+
+• CVE-2020-12049: If a message contains more file descriptors than can
+  be sent, close those that did get through before reporting error.
+  Previously, a local attacker could cause the system dbus-daemon (or
+  another system service with its own DBusServer) to run out of file
+  descriptors, by repeatedly connecting to the server and sending fds that
+  would get leaked.
+  Thanks to Kevin Backhouse of GitHub Security Lab.
+  (dbus#294, GHSL-2020-057; Simon McVittie)
+
+Other fixes:
+
+• Fix a crash when the dbus-daemon is terminated while one or more
+  monitors are active (dbus#291, dbus!140; Simon McVittie)
+
+• The dbus-send(1) man page now documents --bus and --peer instead of
+  the old --address synonym for --peer, which has been deprecated since
+  the introduction of --bus and --peer in 1.7.6
+  (fd.o #48816, dbus!115; Chris Morin)
+
+• Fix a wrong environment variable name in dbus-daemon(1)
+  (dbus#275, dbus!122; Mubin, Philip Withnall)
+
+• Fix formatting of dbus_message_append_args example
+  (dbus!126, Felipe Franciosi)
+
+• Avoid a test failure on Linux when built in a container as uid 0, but
+  without the necessary privileges to increase resource limits
+  (dbus!58, Debian #908092; Simon McVittie)
+
+• When building with CMake, cope with libX11 in a non-standard location
+  (dbus!129, Tuomo Rinne)
+
 dbus 1.12.16 (2019-06-11)
 =
 
diff --git a/bus/connection.c b/bus/connection.c
index 53605fa3..b3583433 100644
--- a/bus/connection.c
+++ b/bus/connection.c
@@ -537,9 +537,6 @@ bus_connections_unref (BusConnections *connections)
 
   _dbus_assert (connections->n_incomplete == 0);
 
-  /* drop all monitors */
-  _dbus_list_clear (>monitors);
-
   /* drop all real connections */
   

Bug#962000: Duplicated news for php-horde-image

[Raphael Hertzog]

Control: forcemerge 884933 -1

On Mon, 01 Jun 2020, s3v wrote:
> I have noticed that tracker.debian.org reports duplicated news for
> php-horde-image package [1] and others packages in php-horde ecosystem
> (php-horde-data, php-horde-cache, php-horde-crypt, et al.).

This was already documented in 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884933
but I pushed some improvement in git that should only generate the news for
the email that we just received (and not for all packages that we can
identify within the mail).

And since dak should be smarter nowadays (#884931 is fixed), this should be 
fixed.

I must still do something to get rid of old duplicate news items.

Cheers,
-- 
  ⢀⣴⠾⠻⢶⣦⠀   Raphaël Hertzog 
  ⣾⠁⢠⠒⠀⣿⡁
  ⢿⡄⠘⠷⠚⠋The Debian Handbook: https://debian-handbook.info/get/
  ⠈⠳⣄   Debian Long Term Support: https://deb.li/LTS

Bug#962066: bugs.debian.org: Done information badly mistreats names with non-ASCII characters

[Adrian Bunk]

Package: bugs.debian.org
Severity: normal

Example: #961302
Done: =?utf-8?q?J=C3=B6rg_Frings-F=C3=BCrst?= 

Please do RFC 2047 decoding of the name, e.g. with Encode::MIME::Header
perl -e 'binmode(STDOUT, ":utf8");
  use Encode qw(decode);
  print decode("MIME-Header", "=?utf-8?q?J=C3=B6rg_Frings-F=C3=BCrst?=");'

Bug#962065: rdist: Non-free license

[Joao Eriberto Mota Filho]

Package: rdist
Version: 6.1.5
Severity: serious
Tags: upstream
Justification: Policy 2.1

The current version of rdist in Debian says in Copyright file and in every
headers:

/*
 * Copyright (c) 1992-1998 Michael A. Cooper.
 * This software may be freely used and distributed provided it is not
 * sold for profit or used in part or in whole for commercial gain
 * without prior written agreement, and the author is credited
 * appropriately.
 */
/*
 * Copyright (c) 1983 Regents of the University of California.
 * All rights reserved.
 *
 * Redistribution and use in source and binary forms, with or without
 * modification, are permitted provided that the following conditions
 * are met:
 * 1. Redistributions of source code must retain the above copyright
 *notice, this list of conditions and the following disclaimer.
 * 2. Redistributions in binary form must reproduce the above copyright
 *notice, this list of conditions and the following disclaimer in the
 *documentation and/or other materials provided with the distribution.
 * 3. All advertising materials mentioning features or use of this software
 *must display the following acknowledgement:
 *  This product includes software developed by the University of
 *  California, Berkeley and its contributors.
 * 4. Neither the name of the University nor the names of its contributors
 *may be used to endorse or promote products derived from this software
 *without specific prior written permission.
 *
 * THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
 * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
 * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
 * ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
 * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
 * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
 * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
 * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
 * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
 * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 * SUCH DAMAGE.
 */


It sounds like a multi-licensed source code, as "Special and BSD-4-Clause". The
Special slice (Copyright (c) 1992-1998 Michael A. Cooper) is non-DFSG
compliant.

Regards,

Eriberto



-- System Information:
Debian Release: 10.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages rdist depends on:
ii  libc6  2.28-10

rdist recommends no packages.

rdist suggests no packages.

Bug#962037: [Pkg-javascript-devel] Bug#962037: Bug#962037: Bug#962037: Plan B for not being able to replicate upstream exports exactly

[Pirate Praveen]

On Wed, Jun 3, 2020 at 12:29 am, Pirate Praveen 
 wrote:



On Tue, Jun 2, 2020 at 10:33 pm, Pirate Praveen 
 wrote:
I'm trying to close the gap between upstream build and our builds by 
using rollup to generate cjs file as well, but build fails with 
this error.


/usr/bin/node -e require\(\"./.\"\)
/home/pravi/forge/js-team/less.js/dist/less.cjs.js:17699
const { Barrett } = BigInteger.prototype;
  ^

TypeError: Cannot read property 'prototype' of undefined
   at Object. 
(/home/pravi/forge/js-team/less.js/dist/less.cjs.js:17699:32)


This code comes from node-ecc-jsbn and it looks like a bug there, 
its package.json wants jsbn 0.1 but we already have 1.0


This was caused when copied the rollup.config.js for umd to build 
cjs, it had BUNDLE = true which created this issue. Also there was no 
need to use babel except for ES module to CJS conversion which rollup 
alone can do. Hopefully this will fix the issue. Running the tests 
now.


Now I think we are closer to how upstream ships these files, but 
rainloop still fails to build


(node:423913) UnhandledPromiseRejectionWarning: TypeError 
[ERR_INVALID_ARG_TYPE]: The first argument must be one of type string, 
Buffer, ArrayBuffer, Array, or Array-like Object. Received type object

   at Function.from (buffer.js:231:9)
   at new Buffer (buffer.js:181:17)
   at /<>/debian/build/gulp-less.js:40:23
   at parse (/usr/share/nodejs/less/dist/less.cjs.js:11461:17)
   at Parser.parse (/usr/share/nodejs/less/dist/less.cjs.js:11711:21)
   at ImportVisitor.finish [as _finish] 
(/usr/share/nodejs/less/dist/less.cjs.js:7701:28)
   at ImportVisitor._onSequencerEmpty 
(/usr/share/nodejs/less/dist/less.cjs.js:5832:14)
   at ImportSequencer.tryRun 
(/usr/share/nodejs/less/dist/less.cjs.js:5797:18)

   at /usr/share/nodejs/less/dist/less.cjs.js:5766:29
   at fileParsedFunc (/usr/share/nodejs/less/dist/less.cjs.js:11331:21)
(node:423913) UnhandledPromiseRejectionWarning: Unhandled promise 
rejection. This error originated either by throwing inside of an async 
function without a catch block, or by rejecting a promise which was not 
handled with .catch(). (rejection id: 1)

[19:54:10] Finished '' after 18 s
[19:54:10] Starting 'jsLibs'...
[19:54:10] Starting 'jsApp'...
[19:54:10] Starting 'jsAdmin'...
[19:54:10] 'jsLibs' errored after 17 ms
[19:54:10] Error: File not found with singular glob: 
/usr/lib/nodejs/autolinker/dist/Autolinker.js (if this was purposeful, 
use `allowEmpty` option)
   at Glob. 
(/usr/share/nodejs/glob-stream/readable.js:84:17)

   at Object.onceWrapper (events.js:286:20)
   at Glob.emit (events.js:198:13)
   at Glob.EventEmitter.emit (domain.js:448:20)
   at Glob._finish (/usr/share/nodejs/glob/glob.js:197:8)
   at done (/usr/share/nodejs/glob/glob.js:182:14)
   at Glob._processSimple2 (/usr/share/nodejs/glob/glob.js:688:12)
   at /usr/share/nodejs/glob/glob.js:676:10
   at Glob._stat2 (/usr/share/nodejs/glob/glob.js:772:12)
   at lstatcb_ (/usr/share/nodejs/glob/glob.js:764:12)
[19:54:10] 'rainloop' errored after 18 s
[19:54:10] The following tasks did not complete: , , 
cssMainBuild, jsApp, jsAdmin

[19:54:10] Did you forget to signal async completion?

We could try building rainloop with npm version of less 3.11.2 to 
confirm if it is rainloop that needs updating or less that needs fixing.

Bug#962001: austin: autopkgtest regression: src/austin: No such file or directory

[Paul Gevers]

Hi Gabriele,

On 02-06-2020 01:47, Gabriele wrote:
> Thanks for the report. Please note that nothing has changed in the way
> Austin is built and packaged in-between version 1.0.0 and 1.0.1. From
> what I can tell from the log, the tests are failing because src/austin
> is not found, which would be the case if it's not being compiled from
> sources using autotools. Indeed, in the linked logs I have spotted
> 
> autopkgtest [18:07:10]: build not needed

That's because the autopkgtest is not requested to do a build. But it's
not doing that because build-needed is not listed in the test
restrictions. (But please read on).

> My guess is that a build is not needed for a binary package because
> the binary should already be there? If so, it probably won't be in
> src/, hence the failure.

But an autopkgtest should test the installed binaries, not build
artifacts. And, your previous versions didn't need it either.

> As I said, the way of testing, building, and packaging Austin hasn't
> changed across releases, which leads me to think that perhaps
> something has changed in the Debian publication pipeline? Having said
> that, I'd be happy to try and fix this if you could point me in the
> right direction.

As I have no clue what austin does and how its tests work, I don't think
I can help you much. You'll have to figure out what changed between
1.0.0 and 1.0.1 as the change should really be there. If 1.0.0 is
tested, it passes, if 1.0.1 is tested, it fails. Both of them are
retried repeatedly, so it's not the "publication pipeline". Once you
find out which test got changed/updated, you can probably patch it to
test the installed binary. Or, if its also part of the build-time
testsuite, you'll have to change the test during autopkgtest. Please
avoid adding the build-needed restriction if you can.

Paul

By the way: you're package also fails to build from source on multiple
architectures, see https://qa.debian.org/excuses.php?package=austin



signature.asc
Description: OpenPGP digital signature

Bug#962064: "--extra-package" option not respecting relative paths

[Samuel Henrique]

Package: sbuild
Severity: normal

The "--extra-package" option only works if an absolute path is passed,
that is confusing as generally speaking command line tools don't have
issues with relative paths (when they do, it's called out in the
docs).

I looked at the source code of sbuild to see if I could provide a
patch for it but unfortunately I don' t work with perl and I lack the
time to learn it for this right now.

So this is a feature request to make "extra-package" accept relative
paths as input.

FWIW this is the input that didn't work: "--extra-package=../build-area/"

Thanks,

-- 
Samuel Henrique 

Bug#932499: Workaround for TigerVNC on aarch64

[Joachim Falk]

Hi RussianNeuroMancer,

Am 31.05.20 um 14:31 schrieb russianneuroman...@ya.ru:
> Hi, Joachim!
> 
> Is there a chance you could apply workaround for aarch64 described in latest 
> message of this thread?
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932499
there is now a fix for this committed to the master branch.
(Repo https://salsa.debian.org/debian-remote-team/tigervnc.git)
Please build from source for arm64 and maybe armel and armhf
and report back.

Best,

Joachim



signature.asc
Description: OpenPGP digital signature

Bug#962063: src:gulkan: fails to migrate to testing for too long

[Paul Gevers]

Source: gulkan
Version: 0.13.2-2
Severity: serious
Control: close -1 0.14.0-2
Tags: sid bullseye
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:gulkan in its
current version in unstable has been trying to migrate for 61 days [2].
Hence, I am filing this bug.

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

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

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

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

Paul

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




signature.asc
Description: OpenPGP digital signature

Bug#962062: src:wav2cdr: fails to migrate to testing for too long: autopkgtest regression on arm64

[Paul Gevers]

Source: wav2cdr
Version: 2.3.4-2
Severity: serious
Control: close -1 2.3.4-3
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 958578
X-Debbugs-CC: eribe...@debian.org

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

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

Paul

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




signature.asc
Description: OpenPGP digital signature

Bug#955038: Staat_der_Nederlanden_Root_CA_-_G2.crt still in package

[Hanno Böck]

The ca-certificates version 20200601 removes various old/obsolete
certificates, but still contains one expired certificate:

Staat_der_Nederlanden_Root_CA_-_G2.crt

This expired on March 25 2020 and should probably also be removed.

-- 
Hanno Böck
https://hboeck.de/

Bug#881719: libcdio 2.1.0 and lubcdio++

[Vasyl Gello]

Hi Gabriel, Balint!

Please check merge request to debian/cdio. Reprotest still fails at a first 
glance, but lintian warnings have gone.
I will try fixing it but I need to install reprotest hook inside my pbuilder.

If you manage to fix reprotest, please let me know.
-- 
Vasyl Gello
==
Certified SolidWorks Expert

Mob.:+380 (98) 465 66 77

E-Mail: vasek.ge...@gmail.com

Skype: vasek.gello
==
호랑이는 죽어서 가죽을 남기고 사람은 죽어서 이름을 남긴다

signature.asc
Description: PGP signature

Bug#962037: [Pkg-javascript-devel] Bug#962037: Bug#962037: Plan B for not being able to replicate upstream exports exactly

[Pirate Praveen]

On Tue, Jun 2, 2020 at 10:33 pm, Pirate Praveen 
 wrote:
I'm trying to close the gap between upstream build and our builds by 
using rollup to generate cjs file as well, but build fails with this 
error.


/usr/bin/node -e require\(\"./.\"\)
/home/pravi/forge/js-team/less.js/dist/less.cjs.js:17699
const { Barrett } = BigInteger.prototype;
  ^

TypeError: Cannot read property 'prototype' of undefined
   at Object. 
(/home/pravi/forge/js-team/less.js/dist/less.cjs.js:17699:32)


This code comes from node-ecc-jsbn and it looks like a bug there, its 
package.json wants jsbn 0.1 but we already have 1.0


This was caused when copied the rollup.config.js for umd to build cjs, 
it had BUNDLE = true which created this issue. Also there was no need 
to use babel except for ES module to CJS conversion which rollup alone 
can do. Hopefully this will fix the issue. Running the tests now.

Bug#962061: RM: phantomjs -- RoQA; Depends on Python 2, orphaned

[Moritz Muehlenhoff]

Package: ftp.debian.org
Severity: normal

Please remove phantomjs. It depends on Python 2, is orphaned since 2017 without 
an
adopter. Plus, it depends on qtwebkit, which isn't covered by security support.

Cheers,
Moritz

Bug#961813: the missing firmware

[Ben Hutchings]

On Tue, 2020-06-02 at 14:40 +0200, permondes - sagen wrote:
> installed are:
> - firmware-linux-free 3.4 (there is a newer version in testing:
> 20200122-1)
> - firmware-linux 20190717-2~bpo10+1
> - firmware-linux-nonfree 20190717-2~bpo10+1
> 
> I realized the missing firmware is available at git.kernel.org. Are
> these included already in the free package in testing? If so, are there
> any plans to backport them (I am running on stable and would rather
> wait for that)? Would it harm to fetch just this package from testing
> (I presume no)?

The i915 firmware is non-free.

I've done some work toward a new version of firmware-nonfree, but it's
not quite ready yet.

Ben.

-- 
Ben Hutchings
73.46% of all statistics are made up.




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

Bug#962059: buster-pu: package python-markdown2/2.3.7-2

[Pierre-Elliott Bécue]

Le mardi 02 juin 2020 à 20:46:16+0200, Salvatore Bonaccorso a écrit :
> Hi
> 
> [disclaimer, not part of the SRM so this is purely
> informational/commenting]
> 
> On Tue, Jun 02, 2020 at 08:30:45PM +0200, Pierre-Elliott Bécue wrote:
> > +python-markdown2 (2.3.7-2+deb10u1) buster; urgency=medium
> > +
> > +  * Add d/p/0001 To fix CVE-2020-11888, thanks to Gareth Simpson
> 
> As you can close a bug with multiple versions you might add as well
> the bug closure for #959445 as well here so once the fix enters buster
> the BTS will update the fixed versions accordingly.

Thanks! Here's the adapted debdiff!

-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.
diff -Nru python-markdown2-2.3.7/debian/changelog python-markdown2-2.3.7/debian/changelog
--- python-markdown2-2.3.7/debian/changelog	2019-02-02 18:27:36.0 +0100
+++ python-markdown2-2.3.7/debian/changelog	2020-06-02 20:23:22.0 +0200
@@ -1,3 +1,11 @@
+python-markdown2 (2.3.7-2+deb10u1) buster; urgency=medium
+
+  * Add d/p/0001 To fix CVE-2020-11888, thanks to Gareth Simpson
+Closes: #959445
+  * Add a d/gbp.conf file to ease-up gbp's mind
+
+ -- Pierre-Elliott Bécue   Tue, 02 Jun 2020 20:23:22 +0200
+
 python-markdown2 (2.3.7-2) unstable; urgency=medium
 
   * Team upload
diff -Nru python-markdown2-2.3.7/debian/gbp.conf python-markdown2-2.3.7/debian/gbp.conf
--- python-markdown2-2.3.7/debian/gbp.conf	1970-01-01 01:00:00.0 +0100
+++ python-markdown2-2.3.7/debian/gbp.conf	2020-06-02 20:23:22.0 +0200
@@ -0,0 +1,3 @@
+[DEFAULT]
+pristine-tar = True
+debian-branch = debian/buster
diff -Nru python-markdown2-2.3.7/debian/patches/0001-Incomplete-tags-with-punctuation-after-as-part-of-th.patch python-markdown2-2.3.7/debian/patches/0001-Incomplete-tags-with-punctuation-after-as-part-of-th.patch
--- python-markdown2-2.3.7/debian/patches/0001-Incomplete-tags-with-punctuation-after-as-part-of-th.patch	1970-01-01 01:00:00.0 +0100
+++ python-markdown2-2.3.7/debian/patches/0001-Incomplete-tags-with-punctuation-after-as-part-of-th.patch	2020-06-02 20:23:22.0 +0200
@@ -0,0 +1,73 @@
+From: Gareth Simpson 
+Date: Tue, 2 Jun 2020 20:14:30 +0200
+Subject: Incomplete tags with punctuation after as part of the tag name are a
+ source of XSS
+Bug: https://github.com/trentm/python-markdown2/issues/348
+
+Fixes CVE-2020-11888.
+
+python-markdown2 through 2.3.8 allows XSS because element names are
+mishandled unless a \w+ match succeeds. For example, an attack might use
+elementname@ or elementname- with an onclick attribute.
+---
+ lib/markdown2.py   | 9 ++---
+ test/tm-cases/issue348_incomplete_tag.html | 1 +
+ test/tm-cases/issue348_incomplete_tag.opts | 1 +
+ test/tm-cases/issue348_incomplete_tag.text | 1 +
+ 4 files changed, 9 insertions(+), 3 deletions(-)
+ create mode 100644 test/tm-cases/issue348_incomplete_tag.html
+ create mode 100644 test/tm-cases/issue348_incomplete_tag.opts
+ create mode 100644 test/tm-cases/issue348_incomplete_tag.text
+
+diff --git a/lib/markdown2.py b/lib/markdown2.py
+index 16672f5..bd9fe0c 100755
+--- a/lib/markdown2.py
 b/lib/markdown2.py
+@@ -1772,7 +1772,7 @@ class Markdown(object):
+ lexer_name = lexer_name[3:].strip()
+ codeblock = rest.lstrip("\n")   # Remove lexer declaration line.
+ formatter_opts = self.extras['code-color'] or {}
+-
++
+ # Use pygments only if not using the highlightjs-lang extra
+ if lexer_name and "highlightjs-lang" not in self.extras:
+ def unhash_code(codeblock):
+@@ -2134,12 +2134,15 @@ class Markdown(object):
+ text = self._naked_gt_re.sub('', text)
+ return text
+ 
+-_incomplete_tags_re = re.compile("<(/?\w+[\s/]+?)")
++_incomplete_tags_re = re.compile("<(/?\w+?(?!\w).+?[\s/]+?)")
+ 
+ def _encode_incomplete_tags(self, text):
+ if self.safe_mode not in ("replace", "escape"):
+ return text
+-
++
++if text.endswith(">"):
++return text  # this is not an incomplete tag, this is a link in the form 
++
+ return self._incomplete_tags_re.sub("\\1", text)
+ 
+ def _encode_backslash_escapes(self, text):
+diff --git a/test/tm-cases/issue348_incomplete_tag.html b/test/tm-cases/issue348_incomplete_tag.html
+new file mode 100644
+index 000..46059cc
+--- /dev/null
 b/test/tm-cases/issue348_incomplete_tag.html
+@@ -0,0 +1 @@
++lol@/ //id="pwn"//onclick="alert(1)"//abc
+diff --git a/test/tm-cases/issue348_incomplete_tag.opts b/test/tm-cases/issue348_incomplete_tag.opts
+new file mode 100644
+index 000..ad487c0
+--- /dev/null
 b/test/tm-cases/issue348_incomplete_tag.opts
+@@ -0,0 +1 @@
++{"safe_mode": "escape"}
+diff --git a/test/tm-cases/issue348_incomplete_tag.text b/test/tm-cases/issue348_incomplete_tag.text
+new file mode 100644
+index 

Bug#962059: buster-pu: package python-markdown2/2.3.7-2

[Salvatore Bonaccorso]

Hi

[disclaimer, not part of the SRM so this is purely
informational/commenting]

On Tue, Jun 02, 2020 at 08:30:45PM +0200, Pierre-Elliott Bécue wrote:
> +python-markdown2 (2.3.7-2+deb10u1) buster; urgency=medium
> +
> +  * Add d/p/0001 To fix CVE-2020-11888, thanks to Gareth Simpson

As you can close a bug with multiple versions you might add as well
the bug closure for #959445 as well here so once the fix enters buster
the BTS will update the fixed versions accordingly.

Regards,
Salvatore

Bug#962060: josm: java.lang.NoClassDefFoundError: Could not initialize class org.openstreetmap.josm.data.cache.JCSCacheManager

[Bas Couwenberg]

Source: josm
Version: 0.0.svn16538+dfsg-1
Severity: serious
Justification: makes the package in question unusable or mostly so
Control: forwarded -1 https://josm.openstreetmap.de/ticket/19335

Dear Maintainer,

Adding the Bing Layer in JOSM 16538 causes an exception, as does loading the 
wikipedia plugin.

Something is wrong with JCS.

An issue has been filed upstream to help resolve this issue:

 https://josm.openstreetmap.de/ticket/19335

Until the issue is resolved, josm should not migrated to testing.

Kind Regards,

Bas

Bug#960072: Mailman3 3.2.2-1 incompatible with Python 3.8.2-3

[Pierre-Elliott Bécue]

Le vendredi 08 mai 2020 à 19:21:51-0700, Mark Sapiro a écrit :
> Package: mailman3
> Version 3.2.2-1
> 
> Both Bullseye and Sid package mailman3 3.2.2-1 with Python3 3.8.2-3.
> 
> Mailman 3.2.2 is incompatible with Python3 3.8. Python 3 3.8 support is
> not implemented in Mailman 3 <= 3.3.0
> 
> This causes the issue discussed at
> 

Hey Mark,

Thanks for that report. I'm working on packaging 3.3.1 but it's delayed
until I can have zope.interface 5 into Debian, which needs me to have
coverage 5.1 first. Coverage is Ben Finney's scope, and he waits or the
ftpmasters to include sphinx-tabs into the archive.

All of this should unfold at some point.

-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature

Bug#962059: buster-pu: package python-markdown2/2.3.7-2

[Pierre-Elliott Bécue]

Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu

Dear Release Managers,

I'd like to have python-markdown2 updated in Buster, due to a CVE:
CVE-2020-11888.

I attached a debdiff with the bug report, and the update is the
simple adding of debian/patches/0001.

I've also added a gbp.conf to have gbp stop complaining when I don't
give it the proper branch to build, this addition doesn't change the
binary packages.

Note that I've uploaded python-markdown2 2.3.9-1 to unstable 15 minutes
ago. It ships the CVE fix, and should be visible in the archive soon.

Thanks a lot for your work! :)

-- System Information:
Debian Release: 10.4
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-8-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_USER
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to fr_FR.UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to fr_FR.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru python-markdown2-2.3.7/debian/changelog 
python-markdown2-2.3.7/debian/changelog
--- python-markdown2-2.3.7/debian/changelog 2019-02-02 18:27:36.0 
+0100
+++ python-markdown2-2.3.7/debian/changelog 2020-06-02 20:23:22.0 
+0200
@@ -1,3 +1,10 @@
+python-markdown2 (2.3.7-2+deb10u1) buster; urgency=medium
+
+  * Add d/p/0001 To fix CVE-2020-11888, thanks to Gareth Simpson
+  * Add a d/gbp.conf file to ease-up gbp's mind
+
+ -- Pierre-Elliott Bécue   Tue, 02 Jun 2020 20:23:22 +0200
+
 python-markdown2 (2.3.7-2) unstable; urgency=medium
 
   * Team upload
diff -Nru python-markdown2-2.3.7/debian/gbp.conf 
python-markdown2-2.3.7/debian/gbp.conf
--- python-markdown2-2.3.7/debian/gbp.conf  1970-01-01 01:00:00.0 
+0100
+++ python-markdown2-2.3.7/debian/gbp.conf  2020-06-02 20:23:18.0 
+0200
@@ -0,0 +1,3 @@
+[DEFAULT]
+pristine-tar = True
+debian-branch = debian/buster
diff -Nru 
python-markdown2-2.3.7/debian/patches/0001-Incomplete-tags-with-punctuation-after-as-part-of-th.patch
 
python-markdown2-2.3.7/debian/patches/0001-Incomplete-tags-with-punctuation-after-as-part-of-th.patch
--- 
python-markdown2-2.3.7/debian/patches/0001-Incomplete-tags-with-punctuation-after-as-part-of-th.patch
   1970-01-01 01:00:00.0 +0100
+++ 
python-markdown2-2.3.7/debian/patches/0001-Incomplete-tags-with-punctuation-after-as-part-of-th.patch
   2020-06-02 20:22:52.0 +0200
@@ -0,0 +1,73 @@
+From: Gareth Simpson 
+Date: Tue, 2 Jun 2020 20:14:30 +0200
+Subject: Incomplete tags with punctuation after as part of the tag name are a
+ source of XSS
+Bug: https://github.com/trentm/python-markdown2/issues/348
+
+Fixes CVE-2020-11888.
+
+python-markdown2 through 2.3.8 allows XSS because element names are
+mishandled unless a \w+ match succeeds. For example, an attack might use
+elementname@ or elementname- with an onclick attribute.
+---
+ lib/markdown2.py   | 9 ++---
+ test/tm-cases/issue348_incomplete_tag.html | 1 +
+ test/tm-cases/issue348_incomplete_tag.opts | 1 +
+ test/tm-cases/issue348_incomplete_tag.text | 1 +
+ 4 files changed, 9 insertions(+), 3 deletions(-)
+ create mode 100644 test/tm-cases/issue348_incomplete_tag.html
+ create mode 100644 test/tm-cases/issue348_incomplete_tag.opts
+ create mode 100644 test/tm-cases/issue348_incomplete_tag.text
+
+diff --git a/lib/markdown2.py b/lib/markdown2.py
+index 16672f5..bd9fe0c 100755
+--- a/lib/markdown2.py
 b/lib/markdown2.py
+@@ -1772,7 +1772,7 @@ class Markdown(object):
+ lexer_name = lexer_name[3:].strip()
+ codeblock = rest.lstrip("\n")   # Remove lexer declaration 
line.
+ formatter_opts = self.extras['code-color'] or {}
+-
++
+ # Use pygments only if not using the highlightjs-lang extra
+ if lexer_name and "highlightjs-lang" not in self.extras:
+ def unhash_code(codeblock):
+@@ -2134,12 +2134,15 @@ class Markdown(object):
+ text = self._naked_gt_re.sub('', text)
+ return text
+ 
+-_incomplete_tags_re = re.compile("<(/?\w+[\s/]+?)")
++_incomplete_tags_re = re.compile("<(/?\w+?(?!\w).+?[\s/]+?)")
+ 
+ def _encode_incomplete_tags(self, text):
+ if self.safe_mode not in ("replace", "escape"):
+ return text
+-
++
++if text.endswith(">"):
++return text  # this is not an incomplete tag, this is a link in 
the form 
++
+ return self._incomplete_tags_re.sub("\\1", text)
+ 
+ def _encode_backslash_escapes(self, text):
+diff --git a/test/tm-cases/issue348_incomplete_tag.html 
b/test/tm-cases/issue348_incomplete_tag.html
+new file mode 100644
+index 000..46059cc
+--- /dev/null
 b/test/tm-cases/issue348_incomplete_tag.html
+@@ -0,0 

Bug#962058: homebank: new upstream 5.4.2

[Jonatan Nyberg]

Package: homebank
Version: 5.4.2
Severity: Normal

Please consider to upgrade to the current upstream version (5.4.2).

Regards
Jonatan

Bug#962057: ITP: covtobed -- convert the coverage track from a BAM file into a BED file

[Shayan Doust]

Package: wnpp
Severity: wishlist

Subject: ITP: covtobed -- convert the coverage track from a BAM file into a BED 
file
Package: wnpp
Owner: Shayan Doust 
Severity: wishlist

* Package name: covtobed
  Version : 1.1.2
  Upstream Author : Giovanni Birolo and Andrea Telatin
* URL : https://github.com/telatin/covtobed
* License : Expat
  Programming Lang: C
  Description : convert the coverage track from a BAM file into a BED file
 Reads one (or more) alignment files (sorted BAM) and prints a BED with
 the coverage. It will join consecutive bases with the same coverage, and
 can be used to only print a BED file with the regions having a specific
 coverage range.

Remark: This package is maintained by Debian Med Packaging Team at
   https://salsa.debian.org/med-team/covtobed

Bug#961584: lxc-stop fails with exit code 1

[Pierre-Elliott Bécue]

Le mardi 26 mai 2020 à 12:55:10+0200, Inaki Malerba a écrit :
> Source: lxc
> Version: 1:4.0.2-1
> Severity: important
> 
> Dear Maintainer,
> 
> Since version 1:4.0.2-1, we've found a change on the behavior of
> lxc-stop when running on the Salsa-CI pipeline.
> 
> debci calls `lxc-stop --quiet --kill --name $NAME` and it's returning
> exit code 1.
> 
> This can be reproduced on salsa-ci pipeline, which calls `debci localtest`.
> 
> https://salsa.debian.org/salsa-ci-team/pipeline/-/jobs/765946
> 
> : failure: ['sudo', 'timeout', '600', 'lxc-stop',
> '--quiet', '--kill', '--name', 'ci-147-3f089355'] failed (exit status 1,
> stderr '')

Could you remove the --quiet bit to see if lxc-stop gives us a bit more
intel?

If possible, have your testbed call lxc-stop --kill --logpriority trace
--logfile /dev/stdout --name ${NAME}, so we can have the most expressive
output. But if it's an error, removing the quiet bit could be enough.

Thanks.

-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature

Bug#962056: firefox-esr: Firefoz-esr doesn't apply scale factor of system

[Teo]

Package: firefox-esr
Version: 68.8.0esr-1
Severity: normal
Tags: a11y

When I enlarge the text through the scale factor, for example setting it on
1.25, I can see all app with enlarged text, except firefox.
Searching on internet I see that this is a known bug, like you can see here
https://bugzilla.mozilla.org/show_bug.cgi?id=1604761
I read that it has already been fixed in version 73.0b2, and indeed I tried the
newest version (76.0.1) through flatpak, and firefox scale correctly.



-- Package-specific info:

-- Extensions information
Name: Amazon.co.uk
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled

Name: Amazon.com
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled

Name: Bing
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled

Name: Dark theme
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: user-disabled

Name: Default theme
Location: /usr/lib/firefox-esr/omni.ja
Package: firefox-esr
Status: enabled

Name: DuckDuckGo
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled

Name: eBay
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled

Name: Firefox Monitor
Location: /usr/lib/firefox-esr/browser/features/fxmoni...@mozilla.org.xpi
Package: firefox-esr
Status: enabled

Name: Firefox Screenshots
Location: /usr/lib/firefox-esr/browser/features/screensh...@mozilla.org.xpi
Package: firefox-esr
Status: enabled

Name: Form Autofill
Location: /usr/lib/firefox-esr/browser/features/formautof...@mozilla.org.xpi
Package: firefox-esr
Status: enabled

Name: GNOME Shell integration
Location: ${PROFILE_EXTENSIONS}/chrome-gnome-sh...@gnome.org.xpi
Status: enabled

Name: Google
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled

Name: Hotspot Shield Free VPN Proxy - Unlimited VPN
Location: ${PROFILE_EXTENSIONS}/hotspot-shi...@anchorfree.com.xpi
Status: enabled

Name: Light theme
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: user-disabled

Name: Twitter
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled

Name: uBlock Origin
Location: ${PROFILE_EXTENSIONS}/ublo...@raymondhill.net.xpi
Status: enabled

Name: Web Compat
Location: /usr/lib/firefox-esr/browser/features/webcom...@mozilla.org.xpi
Package: firefox-esr
Status: enabled

Name: WebCompat Reporter
Location: 
/usr/lib/firefox-esr/browser/features/webcompat-repor...@mozilla.org.xpi
Package: firefox-esr
Status: user-disabled

Name: Wikipedia (en)
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled

-- Plugins information

-- Addons package information
ii  firefox-esr68.8.0esr-1  amd64Mozilla Firefox web browser - 
Extended Support Release (ESR)

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

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

Versions of packages firefox-esr depends on:
ii  debianutils   4.9.1
ii  fontconfig2.13.1-4.2
ii  libasound21.2.2-2.1
ii  libatk1.0-0   2.36.0-2
ii  libc6 2.30-8
ii  libcairo-gobject2 1.16.0-4
ii  libcairo2 1.16.0-4
ii  libdbus-1-3   1.12.16-2
ii  libdbus-glib-1-2  0.110-5
ii  libevent-2.1-72.1.11-stable-1
ii  libffi7   3.3-4
ii  libfontconfig12.13.1-4.2
ii  libfreetype6  2.10.1-2
ii  libgcc-s1 10.1.0-1
ii  libgdk-pixbuf2.0-02.40.0+dfsg-4
ii  libglib2.0-0  2.64.2-1
ii  libgtk-3-03.24.20-1
ii  libjsoncpp1   1.7.4-3.1
ii  libnspr4  2:4.25-1
ii  libnss3   2:3.49.1-1
ii  libpango-1.0-01.44.7-4
ii  libsqlite3-0  3.31.1-5
ii  libstartup-notification0  0.12-6
ii  libstdc++610.1.0-1
ii  libx11-6  2:1.6.9-2+b1
ii  libx11-xcb1   2:1.6.9-2+b1
ii  libxcb-shm0   1.14-2
ii  libxcb1   1.14-2
ii  libxcomposite11:0.4.5-1
ii  libxdamage1   1:1.1.5-2
ii  libxext6  2:1.3.3-1+b2
ii  libxfixes31:5.0.3-2
ii  libxrender1   1:0.9.10-1
ii  libxt61:1.1.5-1+b3
ii  procps2:3.3.16-5
ii  zlib1g1:1.2.11.dfsg-2

Versions of packages firefox-esr recommends:
ii  libavcodec58  7:4.2.2-1+b1

Versions of packages firefox-esr suggests:
pn  fonts-lmodern  
pn  fonts-stix | otf-stix  
ii  libcanberra0   0.30-7
ii  libgssapi-krb5-2   

Bug#923826: python-blessed: FTBFS randomly (failing tests)

[Pierre-Elliott Bécue]

Le mardi 26 mai 2020 à 17:35:25+0200, Santiago Vila a écrit :
> On Tue, May 26, 2020 at 05:19:28PM +0200, Pierre-Elliott Bécue wrote:
> > Dear Santiago,
> > 
> > Blessed 1.17.6 will enter unstable soon, and its testing framework has
> > been reworked by upstream.
> > 
> > Could you check if things ae running better now?
> 
> Sorry, it is extremely complex for me to try packages not in unstable with my
> current setup, but I could try again once the package is in unstable.
> 
> Thanks a lot.

It is in unstable. :)

-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature

Bug#942457:

[debian]

Dear Maintainer,

Clearly, the bug submitted by Francesco is unpleasant.

I have the same problem today after updated to bullseye.

My config file for msmtp is in a directory synchronized with nextcloud and I 
have a symlink towards ~/.config/msmtp/config. It is pretty convenient for my 
use.

This config file is not a config file of root user but of a simple user. So we 
wouldn't have to modify something in /etc.

The use of symlink is a convenient way to manage all the config files on my two 
PCs. Here, it brokes all for mstmp. Not very fun for a program used each day...


Moreover, I find that the configuration of Apparmor is not an easy task. Just 
for using a simple symlink for a personal configuration file, it needs a deep 
investigation for understand what can be done to solve the problem. Ouch !!! 
The NEWS.Debian file does not help much, for me at least.


If something can be done to eliminate this problem ou to give more explanations 
ou example in NEWS.Debian, please do it.


Anyway, thanks for maintening this package.
Jean-Philippe

Bug#868220: ifupdown should support vlan-aware bridges

[Gianluigi Tiesi]

Package: bridge-utils
Followup-For: Bug #868220

Looks like bridge-utils already does it in:
/lib/bridge-utils/ifupdown.sh

# Activate VLAN filtering on VLAN aware bridges
  if [ "$IF_BRIDGE_VLAN_AWARE" = "yes" ]; then
ip link set dev $IFACE type bridge vlan_filtering 1
  else
ip link set dev $IFACE type bridge vlan_filtering 0
  fi


the problem is I get operation not supported when setting vlan_filtering 0
on my bridge, does the else really make sense here?


Regards


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

Kernel: Linux 4.19.0-9-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages bridge-utils depends on:
ii  libc6  2.30-8

bridge-utils recommends no packages.

Versions of packages bridge-utils suggests:
ii  ifupdown  0.8.35+b1

Bug#956940: EC2 images should install compatibility symlinks for NVME drives

[Noah Meyerhans]

The amazon-ec2-utils package is currently in the NEW queue and will
provide the necessary tools for examining the instance NVME
configuration and creating the requested links.

Details of that package are tracked in the ITP at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959066.

Bug#962037: [Pkg-javascript-devel] Bug#962037: Plan B for not being able to replicate upstream exports exactly

[Pirate Praveen]

On Tue, Jun 2, 2020 at 6:56 pm, Pirate Praveen 
 wrote:

Control: tags -1 help

Hi Daniel,

Would it be possible to skip using gulp-less and use lessc command 
directly, like I did in node-katex (skipped less-loader and used 
lessc command) ?


See the following commands,

https://salsa.debian.org/js-team/node-katex/-/commit/475b47a08c73f2cf108fcb47c49dc845f7ec7e1a

https://salsa.debian.org/js-team/node-katex/-/commit/b4412f7f7cadc32714290ee2ca4caef01e141c41

The exports seems a bit convoluted to get it right. I need help to 
provide the same exports as upstream still using just babeljs command 
or get the upstream build script to work correctly.


I'm trying to close the gap between upstream build and our builds by 
using rollup to generate cjs file as well, but build fails with this 
error.


/usr/bin/node -e require\(\"./.\"\)
/home/pravi/forge/js-team/less.js/dist/less.cjs.js:17699
const { Barrett } = BigInteger.prototype;
  ^

TypeError: Cannot read property 'prototype' of undefined
   at Object. 
(/home/pravi/forge/js-team/less.js/dist/less.cjs.js:17699:32)


This code comes from node-ecc-jsbn and it looks like a bug there, its 
package.json wants jsbn 0.1 but we already have 1.0

Bug#958302: /etc/services: add entries for redis and ircd

[Marco d'Itri]

On Apr 20, Christian Göttsche  wrote:

> > > ircd   6665/tcp
> > Why? I have a fair experience of managing IRC server and networks and
> > this port is not really widely used.
> quasselcore connects to freenode by default on port 6665.
> The client has the configuration "chat.freenode.net:6665" before
> "char.freenode.net:7000".
Not relevant, and this is not the name listed by IANA anyway.

-- 
ciao,
Marco


signature.asc
Description: PGP signature

Bug#960149: kmod: Enable support for gzip compressed kernel modules

[Vagrant Cascadian]

Control: reopen 960149
Control: tags 960149 wontfix
Control: block 960152 by 960149

On 2020-06-02, Marco d'Itri wrote:
> On May 10, Vagrant Cascadian  wrote:
>
>> I see xz-compressed modules are supported, which is definitely useful,
>> but gzip compressed modules are also widely used, and have different CPU
>> vs. storage space tradeoffs.
> No. This was already discussed in #952590, I do not want to add another 
> dependency to the initramfs.

And as said in that bug report as well, libz and numerous other
compression libraries are already added with a default initramfs-tools.

$ lsinitramfs /boot/initrd.img-5.6.0-2-arm64 | grep -E 'libz|liblz'
usr/lib/aarch64-linux-gnu/liblz4.so.1
usr/lib/aarch64-linux-gnu/liblz4.so.1.8.3
usr/lib/aarch64-linux-gnu/liblzma.so.5
usr/lib/aarch64-linux-gnu/liblzma.so.5.2.4
usr/lib/aarch64-linux-gnu/liblzo2.so.2
usr/lib/aarch64-linux-gnu/liblzo2.so.2.0.0
usr/lib/aarch64-linux-gnu/libz.so.1
usr/lib/aarch64-linux-gnu/libz.so.1.2.11
usr/lib/aarch64-linux-gnu/libzstd.so.1
usr/lib/aarch64-linux-gnu/libzstd.so.1.3.8

Your argument that only if it uses plymouth doesn't appear to be
correct:

$ dpkg -l '*plymouth*'
dpkg-query: no packages found matching *plymouth*


Given that this issue keeps coming up, I'm reopening and marking it as
"wontfix", and marking which bugs it blocks moving forward.


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#962055: synaptic: debconf: (Can't locate Gtk3.pm in @INC (you may need to install the Gtk3 module)

[paul345]

Package: synaptic
Version: 0.84.6
Severity: normal

Dear Maintainer,

I have installed debian from debian-live-10.4.0-amd64-kde.iso on a new SSD.

Then I installed synaptic with this command: apt-get install synaptic.
I installed with synaptic some programs. I opened the "info-window" to see
what's going on and
I saw this:
debconf: kann Oberfläche nicht initialisieren: Gnome
debconf: (Can't locate Gtk3.pm in @INC (you may need to install the Gtk3
module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.28.1
/usr/local/share/perl/5.28.1 /usr/lib/x86_64-linux-gnu/perl5/5.28
/usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.28 /usr/share/perl/5.28
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at
/usr/share/perl5/Debconf/FrontEnd/Gnome.pm line 151, <> line 3.)
debconf: greife zurück auf die Oberfläche: Dialog
debconf: kann Oberfläche nicht initialisieren: Dialog
debconf: (TERM ist nicht gesetzt, die Dialog-Oberfläche kann daher nicht
verwendet werden.)
debconf: greife zurück auf die Oberfläche: Readline
Vormals nicht ausgewähltes Paket libcairo-gobject-perl wird gewählt.
(Lese Datenbank ... 295773 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von .../libcairo-gobject-perl_1.004-3+b1_amd64.deb
...
Entpacken von libcairo-gobject-perl (1.004-3+b1) ...
Vormals nicht ausgewähltes Paket libglib-object-introspection-perl wird
gewählt.
Vorbereitung zum Entpacken von .../libglib-object-introspection-
perl_0.047-1_amd64.deb ...
Entpacken von libglib-object-introspection-perl (0.047-1) ...
Vormals nicht ausgewähltes Paket libgtk3-perl wird gewählt.
Vorbereitung zum Entpacken von .../libgtk3-perl_0.034-2_all.deb ...
Entpacken von libgtk3-perl (0.034-2) ...
libglib-object-introspection-perl (0.047-1) wird eingerichtet ...
libcairo-gobject-perl (1.004-3+b1) wird eingerichtet ...
libgtk3-perl (0.034-2) wird eingerichtet ...
Trigger für man-db (2.8.5-2) werden verarbeitet ...

This example shows the solution for this error-message. I installed
libgtk3-perl and this message, that synaptic can't locate Gtk3.pm was gone.

You can fix this problem easily,add libgtk3-perl as hard dependency and it will
work immediately without this error-message.

That's all.

Yours sincerely
paul345




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

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

Versions of packages synaptic depends on:
ii  hicolor-icon-theme   0.17-2
ii  libapt-inst2.0   1.8.2.1
ii  libapt-pkg5.01.8.2.1
ii  libatk1.0-0  2.30.0-2
ii  libc62.28-10
ii  libcairo-gobject21.16.0-4
ii  libcairo21.16.0-4
ii  libept1.5.0  1.1+nmu3+b1
ii  libgcc1  1:8.3.0-6
ii  libgdk-pixbuf2.0-0   2.38.1+dfsg-1
ii  libglib2.0-0 2.58.3-2+deb10u2
ii  libgnutls30  3.6.7-4+deb10u3
ii  libgtk-3-0   3.24.5-1
ii  libpango-1.0-0   1.42.4-8~deb10u1
ii  libpangocairo-1.0-0  1.42.4-8~deb10u1
ii  libpcre2-8-0 10.32-5
ii  libstdc++6   8.3.0-6
ii  libvte-2.91-00.54.2-2
ii  libx11-6 2:1.6.7-1
ii  libxapian30  1.4.11-1
ii  policykit-1  0.105-25
ii  zenity   3.30.0-2
ii  zlib1g   1:1.2.11.dfsg-1

Versions of packages synaptic recommends:
ii  libgtk2-perl  2:1.24992-1+b2
ii  xdg-utils 1.1.3-1+deb10u1

Versions of packages synaptic suggests:
pn  apt-xapian-index 
pn  deborphan
pn  dwww 
pn  menu 
pn  software-properties-gtk  
ii  tasksel  3.53

-- no debconf information

Bug#962046: d-shlibs: deal with libwoff error

[Hideki Yamane]

On Tue, 02 Jun 2020 17:48:05 +0200
Jonas Smedegaard  wrote:
> For the record, d-shlibs quirks are regexes, so your proposed patch 
> won't work:
> 
>   s/libwoff2*-dev/libwoff-dev/
> 
> Instead I applied this:
> 
>   s/libwoff2.*-dev/libwoff-dev/

 Ouch, it should be... thanks!

-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp

Bug#962054: [INTL:es] Spanish translation of the debconf template

[Camaleón]

Package: wdm
Severity: wishlist
Tags: patch l10n

Hello,

You can find enclosed the Spanish translation template to be uploaded
with the latest package build.

Greetings,

-- 
Camaleón 


es.po.gz
Description: application/gzip

Bug#962053: [INTL:es] Spanish translation of the debconf template

[Camaleón]

Package: cltl
Severity: wishlist
Tags: patch l10n

Hello,

You can find enclosed the Spanish translation template to be uploaded
with the latest package build.

Greetings,

-- 
Camaleón 


es.po.gz
Description: application/gzip

Bug#962052: [INTL:es] Spanish translation of the debconf template

[Camaleón]

Package: b43-fwcutter
Severity: wishlist
Tags: patch l10n

Hello,

You can find enclosed the Spanish translation template to be uploaded
with the latest package build.

Greetings,

-- 
Camaleón 


es.po.gz
Description: application/gzip

Bug#953686: Add support for list-table :widths: and :header-rows: to rst2html?

[Dmitry Shachnev]

Hi Petter!

On Thu, Mar 12, 2020 at 11:05:10AM +0100, Petter Reinholdtsen wrote:
> The rst2html tool in python3-docutils do not handle list-table the same
> pandoc and xmlto, spesifically it do not understand the :widths: and
> :header-rows: statements.  I found the format documented in
> https://sublime-and-sphinx-guide.readthedocs.io/en/latest/tables.html >,
> and the PDFs I generate look good using these statements, but the HTML
> edition generated by rst2html do not.
>
> Here is an RST example:
>
> .. list-table:: **Overordnede krav til arkivstrukturen**
>:widths: 1 8 1 4
>:header-rows: 1
>
>   * - Krav nr.
> - Overordnede krav til arkivstrukturen
> - Type
> - Merknad
>   * - 2.1.1
> - For at en løsning skal kunne godkjennes etter Noark 5 må den
>   koseptuelle modellen av arkivstrukturen og de funksjonelle
>   mulighetene den gir, kunne implemenenteres i det aktuelle
>   systemets (fysiske) datastrukturer.
> - O
> - Innebærer at det må implementeres slik at data skal kunne
>   presenteres og hentes ut på den måten.
>   * - 2.1.2
> - Arkivdokumenter skal inngå i en arkivstruktur som minst
>   inneholder følgende arkivenheter:
> 
>   *arkiv*, *arkivdel*, *registrering*, *dokumentbeskrivelse* og
>   *dokumentobjekt*.
> - O
> -
>
> [...]
> 
> I expected the widths to be different and the first line to be handled
> as a header.

I think the problem here is the indentation. The example in documentation [1]
has the same indent level for directive options and for the content.

If you indent the table content by one more space, then it works fine:

.. list-table:: **Overordnede krav til arkivstrukturen**
   :widths: 1 8 1 4
   :header-rows: 1

   * - Krav nr.
 - Overordnede krav til arkivstrukturen
 - Type
 - Merknad
   * - 2.1.1
 - For at en løsning skal kunne godkjennes etter Noark 5 må den
   koseptuelle modellen av arkivstrukturen og de funksjonelle
   mulighetene den gir, kunne implemenenteres i det aktuelle
   systemets (fysiske) datastrukturer.
 - O
 - Innebærer at det må implementeres slik at data skal kunne
   presenteres og hentes ut på den måten.
   [...]

[1]: https://docutils.sourceforge.io/docs/ref/rst/directives.html#list-table

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#962046: d-shlibs: deal with libwoff error

[Jonas Smedegaard]

Quoting Hideki Yamane (2020-06-02 16:32:07)
>  During fontforge package build, got some error with d-shlibs,
>  could you check attached patch, please?

Thanks!

For the record, d-shlibs quirks are regexes, so your proposed patch 
won't work:

  s/libwoff2*-dev/libwoff-dev/

Instead I applied this:

  s/libwoff2.*-dev/libwoff-dev/


 - 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#962028: ITP: python-rich -- Rich is a Python library for rich text and beautiful formatting in the terminal.

[Sandro Tosi]

I already filed an ITP for rich:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954301

On Tue, Jun 2, 2020 at 3:39 AM Mo Zhou  wrote:
>
> Package: wnpp
> Severity: wishlist
> Owner: Mo Zhou 
>
> * Package name: python-rich
> * URL : https://github.com/willmcgugan/rich
> * License : MIT
>   Programming Lang: Python
>   Description : Rich is a Python library for rich text and beautiful 
> formatting in the terminal.
>
> will be maintained under DPMT
>


-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

Bug#961990: libgcc1 : Depends: gcc-10-base (= 10.1.0-1) but 10.1.0-2 is to be installed

[Luis Alejandro Martínez Faneyth]

Nope, doesn't work. Tried installing libgcc-s1 first and then apt is still
asking for libgcc1 when I try to install Node.js.

I guess that is because there's still a physical libgcc1 on the sid
archive, right? Shouldn't that be removed?

https://packages.debian.org/search?keywords=libgcc1

El mar., 2 de jun. de 2020 a la(s) 10:00, Luis Alejandro Martínez Faneyth (
l...@luisalejandro.org) escribió:

> Oh wait, I get it, libgcc-s1 *Provides* libgcc1. I'll try it, thanks.
>
> El mar., 2 de jun. de 2020 a la(s) 09:13, Luis Alejandro Martínez Faneyth (
> l...@luisalejandro.org) escribió:
>
>> I wish I could, but there are several third party apps that depend on
>> libgcc1, for example:
>>
>> Node.js
>>
>> https://deb.nodesource.com/node_13.x/dists/buster/main/binary-amd64/Packages
>>
>> MongoDB
>>
>> http://repo.mongodb.org/apt/debian/dists/buster/mongodb-org/4.2/main/binary-amd64/Packages
>>
>> I suppose there are more, but I haven't tested them.
>>
>>
>>
>> El mar., 2 de jun. de 2020 a la(s) 03:50, Matthias Klose (d...@debian.org)
>> escribió:
>>
>>> On 6/1/20 5:34 PM, Luis Alejandro Martínez Faneyth wrote:
>>> > Package: libgcc1
>>> > Version: 10.1.0-1
>>> > X-Debbugs-CC: debian-...@lists.debian.org
>>> >
>>> > Hello everyone. I have been getting this installation error with GCC
>>> 10 on
>>> > Debian Sid, here's the full log:
>>> >
>>> >
>>> > + apt-get install -d ca-certificates libc6 libgcc1 libnode64 libstdc++6
>>> > python-minimal
>>> >
>>> > Reading package lists...
>>> > Building dependency tree...
>>> > Reading state information...
>>> > ca-certificates is already the newest version (20190110).
>>> > libstdc++6 is already the newest version (10.1.0-2).
>>> > libc6 is already the newest version (2.30-8).
>>> > Some packages could not be installed. This may mean that you have
>>> > requested an impossible situation or if you are using the unstable
>>> > distribution that some required packages have not yet been created
>>> > or been moved out of Incoming.
>>> > The following information may help to resolve the situation:
>>> >
>>> > The following packages have unmet dependencies:
>>> >  libgcc1 : Depends: gcc-10-base (= 10.1.0-1) but 10.1.0-2 is to be
>>> installed
>>> >
>>> >
>>> > This has something to do with the auto-libgc transition? what possible
>>> > workarounds do I have? Because of this I can't install a number of apps
>>> > depending on libgcc (mongo, node, etc).
>>>
>>> just remove libgcc1, it's provided by libgcc-s1.
>>>
>>
>>
>> --
>> Luis Alejandro Martínez Faneyth
>> Blog: https://luisalejandro.org
>> Github: https://github.com/LuisAlejandro
>> 
>> Twitter: https://twitter.com/LuisAlejandro
>> 
>>
>> CODE IS POETRY
>>
>
>
> --
> Luis Alejandro Martínez Faneyth
> Blog: https://luisalejandro.org
> Github: https://github.com/LuisAlejandro 
> Twitter: https://twitter.com/LuisAlejandro
> 
>
> CODE IS POETRY
>


-- 
Luis Alejandro Martínez Faneyth
Blog: https://luisalejandro.org
Github: https://github.com/LuisAlejandro 
Twitter: https://twitter.com/LuisAlejandro


CODE IS POETRY

Bug#962036: quodlibet: Ending a call in Microsoft Teams causes Quod Libet to start playing music.

[Christoph Reiter]

pulseaudio can also request the stream to pause/resume. My guess would
be in that direction.

Bug#962036: quodlibet: Ending a call in Microsoft Teams causes Quod Libet to start playing music.

[Martin]

Control: retitle -1 quodlibet: Ending a call causes Quod Libet to start playing 
music

Note, that this happens with other software, too, e.g. linphone.
I assume, that most soft phones send (DBus?) signals when one
takes or ends a call. Quodlibet pauses and resumes accordingly,
which is nice. However, it should probably not resume
automatically when being paused manually.

Bug#962051: segfault when locking screen

[Stefano Zacchiroli]

Package: gnome-shell
Version: 3.36.2-1
Severity: important

heya, since yesterday under Debian/testing gnome-shell crashes (and then
restarts) when trying to lock screen. Here's the diagnostic I can find under
journalctl:

  giu 02 17:17:32 noziere kernel: gnome-shell[106365]: segfault at 0 ip 
7fb2305fd467 sp 7ffd001db960 error 4 in libst-1.0.so[7fb2305de000+4a000]
  giu 02 17:17:32 noziere kernel: Code: 00 00 00 48 83 c3 01 41 39 9f 30 01 00 
00 0f 8e 2f 01 00 00 49 8b 87 28 01 00 00 48 8d 35 d6 f5 02 00 48 8b 2c d8 48 
8b 45 00 <48> 8b 00 4c 8b 20 4c 89 e7 e8 3b 28 fe ff 85 c0 74 c7 41 80 7c 24
  giu 02 17:17:32 noziere polkitd(authority=local)[718]: Unregistered 
Authentication Agent for unix-session:2 (system bus name :1.168, object path 
/org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) 
(disconnected from bus)
  giu 02 17:17:32 noziere gsd-media-keys[2202]: Couldn't lock screen: 
GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected 
from message bus without replying
  giu 02 17:17:32 noziere systemd[1768]: gnome-shell-x11.service: Main process 
exited, code=killed, status=11/SEGV
  giu 02 17:17:32 noziere systemd[1768]: gnome-shell-x11.service: Failed with 
result 'signal'.
  giu 02 17:17:32 noziere systemd[1768]: gnome-shell-x11.service: Scheduled 
restart job, restart counter is at 11.
  giu 02 17:17:32 noziere systemd[1768]: Stopped target GNOME X11 Session 
(session: gnome).
  giu 02 17:17:32 noziere systemd[1768]: Stopping GNOME X11 Session (session: 
gnome).
  giu 02 17:17:32 noziere systemd[1768]: Stopped target GNOME X11 Session.
  giu 02 17:17:32 noziere systemd[1768]: Stopping GNOME X11 Session.
  giu 02 17:17:32 noziere systemd[1768]: Stopped target GNOME Shell on X11.
  giu 02 17:17:32 noziere systemd[1768]: Stopping GNOME Shell on X11.
  giu 02 17:17:32 noziere systemd[1768]: Stopped GNOME Shell on X11.
  giu 02 17:17:32 noziere systemd[1768]: Starting GNOME Shell on X11...

It happens systematically, both when trying to lock screen on demand
(Ctrl+Alt+L) and when the laptop suspends (meaning that when it wakes up the
desktop is happily unlocked... this might make this bug warrant a security +
severity bump: I'll let this up to the maintainers to decide).

As shown above the shell immediately restarts afterwards, without causing any
session disruption/logout/etc.

Thanks for maintaining GNOME in Debian!

Cheers

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

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

Versions of packages gnome-shell depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.36.0-1
ii  evolution-data-server3.36.2-1
ii  gir1.2-accountsservice-1.0   0.6.55-2
ii  gir1.2-atspi-2.0 2.36.0-2
ii  gir1.2-freedesktop   1.64.1-1
ii  gir1.2-gcr-3 3.36.0-2
ii  gir1.2-gdesktopenums-3.0 3.36.1-1
ii  gir1.2-gdm-1.0   3.34.1-3
ii  gir1.2-geoclue-2.0   2.5.6-1
ii  gir1.2-glib-2.0  1.64.1-1
ii  gir1.2-gnomebluetooth-1.03.34.1-1
ii  gir1.2-gnomedesktop-3.0  3.36.2-1
ii  gir1.2-gtk-3.0   3.24.20-1
ii  gir1.2-gweather-3.0  3.36.0-1
ii  gir1.2-ibus-1.0  1.5.22-5
ii  gir1.2-mutter-6  3.36.2-3
ii  gir1.2-nm-1.01.24.0-1
ii  gir1.2-nma-1.0   1.8.28-2
ii  gir1.2-pango-1.0 1.44.7-4
ii  gir1.2-polkit-1.00.105-26
ii  gir1.2-rsvg-2.0  2.48.4+dfsg-1
ii  gir1.2-soup-2.4  2.70.0-1
ii  gir1.2-upowerglib-1.00.99.11-2
ii  gjs  1.64.2-1
ii  gnome-backgrounds3.36.0-1
ii  gnome-settings-daemon3.36.1-1
ii  gnome-shell-common   3.36.2-1
ii  gsettings-desktop-schemas3.36.1-1
ii  libatk-bridge2.0-0   2.34.1-3
ii  libatk1.0-0  2.36.0-2
ii  libc62.30-8
ii  libcairo21.16.0-4
ii  libecal-2.0-13.36.2-1
ii  libedataserver-1.2-243.36.2-1
ii  libgcr-base-3-1  3.36.0-2
ii  libgdk-pixbuf2.0-0   2.40.0+dfsg-4
ii  

Bug#962050: sasmodels: regression in debian/patches/reproducible-c-models.patch

[Chris Lamb]

Package: sasmodels
Version: 1.0.2-1
Severity: wishlist
User: reproducible-bui...@lists.alioth.debian.org
Usertags: randomness
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Hi,

There appears to be a regression in the handling of the
debian/patches/reproducible-c-models.patch patch to make the build
reproducible:

  - /usr/lib/sasmodels/compiled_models/sas64_constrained_ellipsoid_23EC36B6.so
  - /usr/lib/sasmodels/compiled_models/sas64_constrained_ellipsoid_C3C21C46.so
  + /usr/lib/sasmodels/compiled_models/sas64_constrained_ellipsoid_19FD229F.so
  + /usr/lib/sasmodels/compiled_models/sas64_constrained_ellipsoid_F9D3086F.so

ie. we are back to using the `tempfile.mkstemp` filenames again.
Filing a bug (without a patch) as you will likely be able to fixup
your existing patch quicker than me (and the presence of that patch
implies you are already invested in having a reproducible build.)


Regards,

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

Bug#945117: ITP: matiec -- IEC 61131-3 to C translator

[Philip Rinn]

Control: retitle 945117 RFP: matiec -- IEC 61131-3 to C translator
Control: noowner 945117

Hi,

I still think it would be good to have matiec in Debian but I'm not using it
anymore and lost interest in packaging it myself.

Best,
Philip

Bug#962048: [Piuparts-devel] Bug#962048: piuparts.d.o: exclude udebs from reports

[Andreas Beckmann]

On 02/06/2020 16.41, Adam D. Barratt wrote:
> As discussed with Nicolas on IRC a little while ago, pages like 
> https://piuparts.debian.org/buster2next/source/l/linux.html should
> exclude udebs.
> 
> Currently they are listed, with the status "unknown package", which
> makes for a fairly noisy and potentially confusing output.

piuparts gets the package list from the Binary field in the sources list
which does not have this information. Maybe we could parse Package-List
(and fall back to Binary in case old distros don't have that).


Andreas

Bug#962049: anarchism: update available

[David Kleuker]

Package: anarchism
Version: 15.3-1

Upstream has version 15.4 available 
https://anarchism.pageabode.com/afaq/new.html 
http://www.anarchism.pageabode.com/afaq/index.html

kind regards
davidak

Bug#652465: apt: --fix-policy not documented in man page

[David Kalnischkies]

Hi,

On Sun, May 31, 2020 at 11:45:23AM +0200, Baptiste BEAUPLAT wrote:
> On Sat, 17 Dec 2011 15:56:22 +0200 =?utf-8?q?Martin-=C3=89ric_Racine?=
>  wrote:
> > The --fix-policy option is not documented in the apt-get man page.
> 
> Please consider applying the following patch that documents the
> --fix-policy option.

The problem with this option and hence the documentation is that
"policy" is a very bad word here. I said on IRC then I mentioned
& explained that option that it is 'apt-speak', but I meant that this is
something only the code & debug messages use – and even those aren't
uniformly using it as the code calls these dependencies also "important"
(vs. "critical"). In the code this makes sort of sense, but I wouldn't
like to expose a user to the notion of "important" as we use that word
for yet more other confusing things (which is probably why the code
isn't using it all the time either).

From a user point of view "policy" refers to apt_preferences, at least
that is what we have taught them via "apt{-cache,} policy" for years and
the code happily uses it in that sense everywhere as well.

A --fix-policy suggests hence it does something with apt_preferences
which it doesn't as the "configured policy" there is not at all about
Recommends/Suggests.


So, instead of documenting, I would like to "remove" this option:
The functionality as-is is not that great as it is all-or-nothing which
is rarely useful. I would prefer a command which will act on given
packages instead (and only if non are given on all) with a more sensible
name.

Sadly I have no idea how to call it.
I would have called it 'reinstall' as that is sort-of what the code
does… but that should make it obvious that I shouldn't be naming things.

(Famous last words: On the upside, the code for that shouldn't be hard)


Sidenote: "configured policy" suggests there is something you can
configure far above "install recommends". More like "install recommends
if they are related to bluetooth, not related to gnome and included in
the last stable release" – that would be a handy policy sometimes, but
I don't see us getting there any time soon. And even then --fix-policy
would need a few changes….


Beste regards

David Kalnischkies


signature.asc
Description: PGP signature

Bug#962048: piuparts.d.o: exclude udebs from reports

[Adam D. Barratt]

Package: piuparts.debian.org

Hi,

As discussed with Nicolas on IRC a little while ago, pages like 
https://piuparts.debian.org/buster2next/source/l/linux.html should
exclude udebs.

Currently they are listed, with the status "unknown package", which
makes for a fairly noisy and potentially confusing output.

Regards,

Adam

Bug#746658: sdd

[Jeffrey Roger]

*I am Mr. Jeffrey Roger from West African Ghana am the **Foreign Remittance
Department Manager of Commercial bank of Ghana Did you receive the
message i sent to you please let me know..*

Bug#962046: d-shlibs: deal with libwoff error

[Hideki Yamane]

Package: d-shlibs
Severity: normal
Tags: patch

Hi,

 During fontforge package build, got some error with d-shlibs,
 could you check attached patch, please?


-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp
>From b5d35bbf42e177d60b93d90863c06fac5ac83000 Mon Sep 17 00:00:00 2001
From: Hideki Yamane 
Date: Tue, 2 Jun 2020 23:27:00 +0900
Subject: workaround for libwoff*-dev

During fontforge built, found devlibs error as below

Library package automatic movement utility
 --> libfreetype6-dev package exists.
 --> libgif-dev package exists.
 --> libglib2.0-dev package exists.
 --> libjpeg-dev package exists.
 --> libpng-dev package exists.
 --> libpython3.8-dev package exists.
 --> libreadline-dev package exists.
 --> libspiro-dev package exists.
 --> libtiff5-dev package exists.
 --> libuninameslist-dev package exists.
devlibs error: There is no package matching [libwoff2dec1.0.2-dev] and noone provides it, please report bug to d-shlibs maintainer
devlibs error: There is no package matching [libwoff2enc1.0.2-dev] and noone provides it, please report bug to d-shlibs maintainer
 --> libxml2-dev package exists.
 --> zlib1g-dev package exists.
---
 d-devlibdeps | 1 +
 1 file changed, 1 insertion(+)

diff --git a/d-devlibdeps b/d-devlibdeps
index aef6bfa..e8e48f8 100755
--- a/d-devlibdeps
+++ b/d-devlibdeps
@@ -197,6 +197,7 @@ overridedevlibdeps() {
 		-e 's/libvo-amrwbenc0-dev/libvo-amrwbenc-dev/' \
 		-e 's/libvorbis0-dev/libvorbis-dev/' \
 		-e 's/libvorbisenc2-dev/libvorbis-dev/' \
+		-e 's/libwoff2*-dev/libwoff-dev/' \
 		-e 's/libX11-6-dev/libx11-dev/' \
 		-e 's/libX\([a-z]\+\)[0-9]-dev/libx\1-dev/' \
 		-e 's/libxml2-2-dev/libxml2-dev/' \
-- 
2.27.0.rc2

Bug#962019: perl: arch:all build fails on buildd (transient error?)

[Niko Tyni]

Control: clone -1 -2
Control: reassign -2 libio-socket-ip-perl 0.39-1
Control: tag -2 bullseye sid
Control: retitle -2 libio-socket-ip-perl: fails to build on IPv6-only buildds
Control: found -1 5.30.2-1
Control: block -1 with -2

On Tue, Jun 02, 2020 at 11:04:28AM +0200, Julien Cristau wrote:
> Control: tag -1 patch
> 
> On Tue, Jun 02, 2020 at 08:09:43AM +0200, Salvatore Bonaccorso wrote:
> > On Tue, Jun 02, 2020 at 06:40:41AM +0200, Salvatore Bonaccorso wrote:
> > > Source: perl
> > > Version: 5.30.3-1
> > > Severity: serious
> > > Justification: FTBFS
> > > 
> > > Hi Dom an Niko
> > > 
> > > Guess you have seen it but filling a bug for tracking. arch:all build
> > > failed on buildd:
> > > 
> > > https://buildd.debian.org/status/fetch.php?pkg=perl=all=5.30.3-1=1591057198=0
> > 
> > FTR, the issue is that the build got picked up by a IPv6-only enabled
> > buildd.
> 
> FWIW, it seems IO::Socket::IP passes AI_ADDRCONFIG to getaddrinfo, which
> then doesn't return ipv4 addresses because the host doesn't have
> non-local ones, even though the address we're trying to resolve is
> "127.0.0.1".
> 
> Passing either GetAddrInfoFlags => AI_NUMERICHOST or GetAddrInfoFlags =>
> 0 to both IO::Socket::IP->new calls in the test file lets it pass, by
> turning off the smarts in getaddrinfo.

Thanks.

The immediate concern has been solved by rescheduling the failed builds on
different buildd hosts.

As this wasn't broken by a change in perl, I'm marking it found in the
current version in testing too so as not to block testing migration
of 5.30.3-1. It still needs to be fixed, of course.

I'm also cloning a separate bug for libio-socket-ip-perl, which has the
same tests. I've verified that it also fails to build in the same way.

FWIW, an easy way to test this is

# unshare -n
# ip li set lo up
# ip dev add dummy0 type dummy
# ip li set dummy0 up

It's probably best to fix libio-socket-ip-perl first as it's self
contained, and then copy the fix over to src:perl.

-- 
Niko Tyni   nt...@debian.org

Bug#961993: Undelivered Mail Returned to Sender

[Bernhard Übelacker]

Am 02.06.20 um 16:06 schrieb Mail Delivery System:
>The mail system
> 
> : host mx.wowway.com[64.8.71.111] said: 550 5.1.1 [R2]
> Recipient n...@wideopenwest.com does not exist here. (in reply to RCPT TO
> command)

My email could not be delivered to the submitter.

Bug#782540: dash: wait returns whenever a child process is stopped/continued

[Herbert Xu]

This is fixed in dash 0.5.11.
-- 
Email: Herbert Xu 
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

Bug#961993: gimp crashes on start up

[Bernhard Übelacker]

Hello nbi,
I am not involved in packaging gimp, but
this might be related to the debian-multimedia
packages you have installed:

> ii  libbabl-0.1-01:0.1.74-dmo1
> ii  libgegl-0.4-01:0.4.16-dmo1

Is this error also visible when using these packages
from the debian testing repository?
(Or is there at least for these two packages an update in the
debian-multimedia repo?)

Kind regards,
Bernhard

Bug#961990: libgcc1 : Depends: gcc-10-base (= 10.1.0-1) but 10.1.0-2 is to be installed

[Luis Alejandro Martínez Faneyth]

Oh wait, I get it, libgcc-s1 *Provides* libgcc1. I'll try it, thanks.

El mar., 2 de jun. de 2020 a la(s) 09:13, Luis Alejandro Martínez Faneyth (
l...@luisalejandro.org) escribió:

> I wish I could, but there are several third party apps that depend on
> libgcc1, for example:
>
> Node.js
>
> https://deb.nodesource.com/node_13.x/dists/buster/main/binary-amd64/Packages
>
> MongoDB
>
> http://repo.mongodb.org/apt/debian/dists/buster/mongodb-org/4.2/main/binary-amd64/Packages
>
> I suppose there are more, but I haven't tested them.
>
>
>
> El mar., 2 de jun. de 2020 a la(s) 03:50, Matthias Klose (d...@debian.org)
> escribió:
>
>> On 6/1/20 5:34 PM, Luis Alejandro Martínez Faneyth wrote:
>> > Package: libgcc1
>> > Version: 10.1.0-1
>> > X-Debbugs-CC: debian-...@lists.debian.org
>> >
>> > Hello everyone. I have been getting this installation error with GCC 10
>> on
>> > Debian Sid, here's the full log:
>> >
>> >
>> > + apt-get install -d ca-certificates libc6 libgcc1 libnode64 libstdc++6
>> > python-minimal
>> >
>> > Reading package lists...
>> > Building dependency tree...
>> > Reading state information...
>> > ca-certificates is already the newest version (20190110).
>> > libstdc++6 is already the newest version (10.1.0-2).
>> > libc6 is already the newest version (2.30-8).
>> > Some packages could not be installed. This may mean that you have
>> > requested an impossible situation or if you are using the unstable
>> > distribution that some required packages have not yet been created
>> > or been moved out of Incoming.
>> > The following information may help to resolve the situation:
>> >
>> > The following packages have unmet dependencies:
>> >  libgcc1 : Depends: gcc-10-base (= 10.1.0-1) but 10.1.0-2 is to be
>> installed
>> >
>> >
>> > This has something to do with the auto-libgc transition? what possible
>> > workarounds do I have? Because of this I can't install a number of apps
>> > depending on libgcc (mongo, node, etc).
>>
>> just remove libgcc1, it's provided by libgcc-s1.
>>
>
>
> --
> Luis Alejandro Martínez Faneyth
> Blog: https://luisalejandro.org
> Github: https://github.com/LuisAlejandro 
> Twitter: https://twitter.com/LuisAlejandro
> 
>
> CODE IS POETRY
>


-- 
Luis Alejandro Martínez Faneyth
Blog: https://luisalejandro.org
Github: https://github.com/LuisAlejandro 
Twitter: https://twitter.com/LuisAlejandro


CODE IS POETRY

Bug#962045: some plugins do not work anymore

[di dit]

Package: gramps
Version: 5.1.2-1
Severity: normal

Since a few weeks (months?) some plugins do not work anymore.

1/ Verifying data:
Using the menu Tools->Utilities->Verify the data ...
and then clicking the button Run, I get the following error:

46335: ERROR: grampsapp.py: line 156: Unhandled exception
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/gramps/plugins/tool/verify.py",
line 367, in on_apply_clicked
self.v_r = VerifyResults(self.dbstate, self.uistate, self.track,
  File "/usr/lib/python3/dist-packages/gramps/plugins/tool/verify.py",
line 545, in __init__
self.sort_model = self.filt_model.sort_new_with_model()
AttributeError: 'TreeModelFilter' object has no attribute 'sort_new_with_model'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/gramps/plugins/tool/verify.py",
line 374, in on_apply_clicked
self.v_r.ignores = {}
AttributeError: 'NoneType' object has no attribute 'ignores'


2/ Removing unused objects:
Using the following menu Tools->Family tree repair->Remove unused objects
I get the following error:

140333: ERROR: tool.py: line 257: Failed to start tool.
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/gramps/gui/plug/tool.py", line
251, in gui_tool
tool_class(dbstate = dbstate, user = user,
  File "/usr/lib/python3/dist-packages/gramps/plugins/tool/removeunused.py",
line 127, in __init__
self.init_gui()
  File "/usr/lib/python3/dist-packages/gramps/plugins/tool/removeunused.py",
line 175, in init_gui
self.sort_model = self.real_model.sort_new_with_model()
AttributeError: 'ListStore' object has no attribute 'sort_new_with_model'

Regards


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

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

Versions of packages gramps depends on:
ii  gir1.2-gtk-3.03.24.20-1
ii  librsvg2-22.48.4+dfsg-1
ii  python3   3.8.2-3
ii  python3-bsddb36.2.7-1.1+b1
ii  python3-gi3.36.0-3
ii  python3-gi-cairo  3.36.0-3
ii  xdg-utils 1.1.3-2

Versions of packages gramps recommends:
ii  gir1.2-geocodeglib-1.0  3.26.2-2
ii  gir1.2-gexiv2-0.10  0.12.0-2
ii  gir1.2-osmgpsmap-1.01.1.0-7
ii  graphviz2.42.2-4
ii  python3-icu 2.2-3+b1


Versions of packages gramps suggests:
ii  fonts-freefont-ttf20120503-10
pn  gir1.2-goocanvas-2.0  
pn  gir1.2-gtkspell3-3.0  
ii  python3-numpy 1:1.18.4-1
ii  python3-pil   7.0.0-4+b1
pn  rcs   

-- no debconf information

Bug#962037: Plan B for not being able to replicate upstream exports exactly

[Pirate Praveen]

Control: tags -1 help

Hi Daniel,

Would it be possible to skip using gulp-less and use lessc command 
directly, like I did in node-katex (skipped less-loader and used lessc 
command) ?


See the following commands,

https://salsa.debian.org/js-team/node-katex/-/commit/475b47a08c73f2cf108fcb47c49dc845f7ec7e1a

https://salsa.debian.org/js-team/node-katex/-/commit/b4412f7f7cadc32714290ee2ca4caef01e141c41

The exports seems a bit convoluted to get it right. I need help to 
provide the same exports as upstream still using just babeljs command 
or get the upstream build script to work correctly.

Bug#961990: libgcc1 : Depends: gcc-10-base (= 10.1.0-1) but 10.1.0-2 is to be installed

[Luis Alejandro Martínez Faneyth]

I wish I could, but there are several third party apps that depend on
libgcc1, for example:

Node.js
https://deb.nodesource.com/node_13.x/dists/buster/main/binary-amd64/Packages

MongoDB
http://repo.mongodb.org/apt/debian/dists/buster/mongodb-org/4.2/main/binary-amd64/Packages

I suppose there are more, but I haven't tested them.



El mar., 2 de jun. de 2020 a la(s) 03:50, Matthias Klose (d...@debian.org)
escribió:

> On 6/1/20 5:34 PM, Luis Alejandro Martínez Faneyth wrote:
> > Package: libgcc1
> > Version: 10.1.0-1
> > X-Debbugs-CC: debian-...@lists.debian.org
> >
> > Hello everyone. I have been getting this installation error with GCC 10
> on
> > Debian Sid, here's the full log:
> >
> >
> > + apt-get install -d ca-certificates libc6 libgcc1 libnode64 libstdc++6
> > python-minimal
> >
> > Reading package lists...
> > Building dependency tree...
> > Reading state information...
> > ca-certificates is already the newest version (20190110).
> > libstdc++6 is already the newest version (10.1.0-2).
> > libc6 is already the newest version (2.30-8).
> > Some packages could not be installed. This may mean that you have
> > requested an impossible situation or if you are using the unstable
> > distribution that some required packages have not yet been created
> > or been moved out of Incoming.
> > The following information may help to resolve the situation:
> >
> > The following packages have unmet dependencies:
> >  libgcc1 : Depends: gcc-10-base (= 10.1.0-1) but 10.1.0-2 is to be
> installed
> >
> >
> > This has something to do with the auto-libgc transition? what possible
> > workarounds do I have? Because of this I can't install a number of apps
> > depending on libgcc (mongo, node, etc).
>
> just remove libgcc1, it's provided by libgcc-s1.
>


-- 
Luis Alejandro Martínez Faneyth
Blog: https://luisalejandro.org
Github: https://github.com/LuisAlejandro 
Twitter: https://twitter.com/LuisAlejandro


CODE IS POETRY

Bug#962027: please include x42-avldrums

[Olivier Humbert]

Le 2020-06-02 09:28, Bastian Venthur a écrit :

Hi Bastian.

Since x42-avldrums isn't a part of x42-plugins upstream package, it 
wouldn't be a good idea to add it to the x42-plugins package in Debian. 
Please, have a look at 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849786 instead.


Happy drumming!
Olivier

Bug#962043: calibre: [ebook-viewer] missing dependency python-unrardll - cannot open cbr/cbz

[F. M.]

Package: calibre
Version: 3.39.1+dfsg-3
Severity: normal

Dear Maintainer,

under Debian 10, Calibre's ebook-viewer cannot oper cbr/cbz files.
This is due to a missing dependency on Debian 10 when installing Calibre.
python-unrardll (possibly python3-unrardll) is missing: it should be installed
when installing Calibre.

Do you mind updating the dependency of the package?

Thanks and best regards,



-- System Information:
Debian Release: 10.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages calibre depends on:
ii  calibre-bin  3.39.1+dfsg-3
ii  fonts-liberation 1:1.07.4-9
ii  imagemagick  8:6.9.10.23+dfsg-2.1
ii  imagemagick-6.q16 [imagemagick]  8:6.9.10.23+dfsg-2.1
ii  libjpeg-turbo-progs  1:1.5.2-2+b1
ii  libjs-coffeescript   1.12.8~dfsg-4
ii  libjs-mathjax2.7.4+dfsg-1
ii  optipng  0.7.7-1
ii  poppler-utils0.71.0-5
ii  python-apsw  3.24.0-r1-1
ii  python-chardet   3.0.4-3
ii  python-cherrypy3 8.9.1-2
ii  python-css-parser1.0.4-1
ii  python-cssselect 1.0.3-1
ii  python-cssutils  1.0.2-2
ii  python-dateutil  2.7.3-3
ii  python-dbus  1.2.8-3
ii  python-feedparser5.2.1-1
ii  python-html5-parser  0.4.5-1
ii  python-html5lib  1.0.1-1
ii  python-lxml  4.3.2-1
ii  python-markdown  3.0.1-3
ii  python-mechanize 1:0.2.5-3
ii  python-msgpack   0.5.6-1+b1
ii  python-netifaces 0.10.4-1+b1
ii  python-pil   5.4.1-2+deb10u1
ii  python-pkg-resources 40.8.0-1
ii  python-pyparsing 2.2.0+dfsg1-2
ii  python-pyqt5 5.11.3+dfsg-1+b3
ii  python-pyqt5.qtsvg   5.11.3+dfsg-1+b3
ii  python-pyqt5.qtwebkit5.11.3+dfsg-1+b3
ii  python-regex 0.1.20190207-1
ii  python-routes2.4.1-1
ii  python2.72.7.16-2+deb10u1
ii  xdg-utils1.1.3-1+deb10u1

Versions of packages calibre recommends:
ii  python-dnspython  1.16.0-1

Versions of packages calibre suggests:
ii  python-unrardll  0.1.3-2

-- no debconf information

Bug#962042: smuxi-frontend-gnome: clicking on a link does not open it in the web browser

[Raphaël Hertzog]

Package: smuxi-frontend-gnome
Version: 1.0.7-5
Severity: important

I have been a happy smuxi user for years but for a few months now I'm no
longer able to click on links... I can left click but nothing happens, the URL
no longer opens in the web browser. Same goes with right click + selecting
the open menu entry.

I tried to strace it and saw this:
[pid 779574] access("/usr/bin/xdg-open", X_OK) = 0
[pid 779574] write(1, "2020-06-02 14:33:45,415 [Thread Pool Worker] ERROR 
Smuxi.Frontend.Gnome.Frontend - OpenLink(): opening URL: 
'https://pbs.twimg.com/media/ESpweBhXgAAefGF?format=jpg=small' 
failed\nSystem.ComponentModel.Win32Exception (0x80004005): Cannot find the 
specified file\n  at System.Diagnostics.Process.StartWithShellExecuteEx 
(System.Diagnostics.ProcessStartInfo startInfo) [0x00129] in 
:0 \n  at System.Diagnostics.Process.Start () 
[0x00038] in :0 \n  at (wrapper 
remoting-invoke-with-check) System.Diagnostics.Process.Start()\n  at 
System.Diagnostics.Process.Start (System.Diagnostics.ProcessStartInfo 
startInfo) [0x0001e] in :0 \n  at 
System.Diagnostics.Process.Start (System.String fileName) [0x6] in 
:0 \n  at 
Smuxi.Frontend.Gnome.Frontend+c__AnonStorey6.<>m__0 (System.Object ) 
[0xf] in /build/smuxi-1.0.7/src/Frontend-GNOME/Frontend.cs:945 \n", 992 


I have no idea why the code is generating this exception.

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

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

Versions of packages smuxi-frontend-gnome depends on:
ii  libdbus-glib2.0-cil 0.6.0-1
ii  libdbus2.0-cil  0.8.1-2
ii  libglade2.0-cil 2.12.40-3
ii  libglib2.0-02.64.2-1
ii  libglib2.0-cil  2.12.40-3
ii  libgtk2.0-0 2.24.32-4
ii  libgtk2.0-cil   2.12.40-3
ii  libgtkspell02.0.16-1.3
ii  liblog4net1.2-cil   1.2.10+dfsg-7
ii  libmessagingmenu12.10-cil   1.0.1-1
ii  libmono-corlib4.5-cil   6.8.0.105+dfsg-3
ii  libmono-posix4.0-cil6.8.0.105+dfsg-3
ii  libmono-system-core4.0-cil  6.8.0.105+dfsg-3
ii  libmono-system-web4.0-cil   6.8.0.105+dfsg-3
ii  libmono-system4.0-cil   6.8.0.105+dfsg-3
ii  libnotify0.4-cil0.4.0~r3032-7
ii  librsvg2-common 2.48.4+dfsg-1
ii  mono-runtime6.8.0.105+dfsg-3
ii  smuxi-engine1.0.7-5

Versions of packages smuxi-frontend-gnome recommends:
ii  gnome-shell [notification-daemon]  3.36.2-1
ii  notification-daemon3.20.0-4
ii  ssh-askpass-gnome [ssh-askpass]1:8.2p1-4

smuxi-frontend-gnome suggests no packages.

-- no debconf information

Bug#934809: opus 1.3.1 available

[Alexander Volkov]

Please, package the new version.
opus 1.3.1 is needed for qtwebengine 5.15.

Bug#961813: the missing firmware

[permondes - sagen]

installed are:
- firmware-linux-free 3.4 (there is a newer version in testing:
20200122-1)
- firmware-linux 20190717-2~bpo10+1
- firmware-linux-nonfree 20190717-2~bpo10+1

I realized the missing firmware is available at git.kernel.org. Are
these included already in the free package in testing? If so, are there
any plans to backport them (I am running on stable and would rather
wait for that)? Would it harm to fetch just this package from testing
(I presume no)?


Am Dienstag, den 02.06.2020, 14:43 +0300 schrieb alexandros:
> install firmware-linux and firmware-linux-free
> 
> On 6/2/20 2:20 PM, permondes - sagen wrote:
> > Missing firmware is:
> > 
> > W: Possible missing firmware /lib/firmware/i915/icl_dmc_ver1_09.bin for
> > module i915
> > W: Possible missing firmware /lib/firmware/i915/tgl_dmc_ver2_04.bin for
> > module i915
> > 
> > W: Possible missing firmware /lib/firmware/i915/skl_huc_2.0.0.bin for
> > module i915
> > 
> > W: Possible missing firmware /lib/firmware/i915/bxt_huc_2.0.0.bin for
> > module i915
> > 
> > W: Possible missing firmware /lib/firmware/i915/kbl_huc_4.0.0.bin for
> > module i915
> > 
> > W: Possible missing firmware /lib/firmware/i915/glk_huc_4.0.0.bin for
> > module i915
> > 
> > W: Possible missing firmware /lib/firmware/i915/kbl_huc_4.0.0.bin for
> > module i915
> > 
> > W: Possible missing firmware /lib/firmware/i915/cml_huc_4.0.0.bin for
> > module i915
> > 
> > W: Possible missing firmware /lib/firmware/i915/cml_guc_33.0.0.bin for
> > module i915
> > 
> > W: Possible missing firmware /lib/firmware/i915/icl_huc_9.0.0.bin for
> > module i915
> > 
> > W: Possible missing firmware /lib/firmware/i915/ehl_huc_9.0.0.bin for
> > module i915
> > 
> > W: Possible missing firmware /lib/firmware/i915/ehl_guc_33.0.4.bin for
> > module i915
> > 
> > W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.0.3.bin for
> > module i915
> > 
> > W: Possible missing firmware /lib/firmware/i915/tgl_guc_35.2.0.bin for
> > module i915
> > 

Bug#716789: dash: Dash sometimes misbehaves when backticks are included after an || operator

[Herbert Xu]

This has been fixed in dash 0.5.11.
-- 
Email: Herbert Xu 
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

Bug#962041: opensurgsim: FTBFS on i386/mipsel/mips64el

[Adrian Bunk]

Source: opensurgsim
Version: 0.7.0-10
Severity: serious
Tags: patch

https://buildd.debian.org/status/logs.php?pkg=opensurgsim=0.7.0-10

The patch below contains the following changes:
- fix FTBFS on i386
 12 - SurgSimMathTest (Failed)
- fix/workaround FTBFS on mipsel
  cc1plus: out of memory allocating 5399924 bytes after a total of 73105408 
bytes
- fix/workaround FTBFS on mips64el
  E: Build killed with signal TERM after 150 minutes of inactivity
- stop ignoring test failures on armhf, I haven't seen the error
  in any recent build logs


--- debian/rules.old2020-05-26 19:34:35.609162184 +
+++ debian/rules2020-05-26 19:34:52.869462911 +
@@ -3,10 +3,18 @@
 export DEB_BUILD_MAINT_OPTIONS = hardening=-format,+bindnow
 export GOOGLEMOCK_DIR = /usr/src/googletest/googlemock
 
+ifneq (,$(filter $(DEB_HOST_ARCH), i386))
+export DEB_CXXFLAGS_MAINT_APPEND += -ffloat-store
+endif
+
+ifneq (,$(filter $(DEB_HOST_ARCH), mipsel mips64el))
+export DEB_CXXFLAGS_MAINT_APPEND += -g1
+endif
+
 %:
dh $@
 
-ifeq (,$(filter $(DEB_BUILD_ARCH),i386 arm64 armel armhf powerpc ppc64el 
ppc64))
+ifeq (,$(filter $(DEB_HOST_ARCH),i386 arm64 armel armhf mipsel powerpc ppc64el 
ppc64))
 EIGEN_ALIGNMENT=ON
 else
 EIGEN_ALIGNMENT=OFF
@@ -36,12 +44,5 @@
 
 override_dh_auto_test:
 ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
-ifeq (,$(filter $(DEB_BUILD_ARCH), armhf))
-   @echo "Do normal testing for all architectures except armhf"
dh_auto_test
-else
-   @echo "ignore test failures for armhf but leave it as output in the 
logs"
-   # see https://bugs.debian.org/847321
-   dh_auto_test || true
-endif
 endif

Bug#962040: boost1.67: Can not (and should not) fulfill the build dependencies

[Adrian Bunk]

Source: boost1.67
Version: 1.67.0-18
Severity: serious
Tags: ftbfs

The following packages have unmet dependencies:
 builddeps:boost1.67 : Depends: libicu-dev (< 64) but 67.1-2 is to be installed

This is intentional, see #960623 for background.

Bug#881719: libcdio 2.1.0 and lubcdio++

[Gabriel F. T. Gomes]

On Tue, 02 Jun 2020, Bálint Réczey wrote:
>
> Done. I've omitted the last commit because I suggest using -1~exp0
> Debian version for the upload to experimental. IMO looks nicer when
> the upload to unstable has -1.

Thanks for the review. I'll fix this, then upload again to mentors.

Bug#936129: Bug #936129: apr-util: Python2 removal in sid/bullseye

[Thomas Goirand]

If Aron is right, then the python:any dependency in apr-util should be
completely removed, and libapr1-dev must add a runtime dependency on
Python3, because that's the one using Python3.

Dear maintainer, there's only 154 packages in Testing needing Python 2.
Could we get this bug fixed?

Cheers,

Thomas Goirand (zigo)

Bug#961813: the missing firmware

[alexandros]

install firmware-linux and firmware-linux-free

On 6/2/20 2:20 PM, permondes - sagen wrote:

Missing firmware is:

W: Possible missing firmware /lib/firmware/i915/icl_dmc_ver1_09.bin for
module i915
W: Possible missing firmware /lib/firmware/i915/tgl_dmc_ver2_04.bin for
module i915

W: Possible missing firmware /lib/firmware/i915/skl_huc_2.0.0.bin for
module i915

W: Possible missing firmware /lib/firmware/i915/bxt_huc_2.0.0.bin for
module i915

W: Possible missing firmware /lib/firmware/i915/kbl_huc_4.0.0.bin for
module i915

W: Possible missing firmware /lib/firmware/i915/glk_huc_4.0.0.bin for
module i915

W: Possible missing firmware /lib/firmware/i915/kbl_huc_4.0.0.bin for
module i915

W: Possible missing firmware /lib/firmware/i915/cml_huc_4.0.0.bin for
module i915

W: Possible missing firmware /lib/firmware/i915/cml_guc_33.0.0.bin for
module i915

W: Possible missing firmware /lib/firmware/i915/icl_huc_9.0.0.bin for
module i915

W: Possible missing firmware /lib/firmware/i915/ehl_huc_9.0.0.bin for
module i915

W: Possible missing firmware /lib/firmware/i915/ehl_guc_33.0.4.bin for
module i915

W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.0.3.bin for
module i915

W: Possible missing firmware /lib/firmware/i915/tgl_guc_35.2.0.bin for
module i915

Bug#961596: Acknowledgement (rebar: Remove -lerl_interface from ERL_LDFLAGS for Erlang 23)

[Sergei Golovan]

Hi Nobuhiro,

I've prepared an updated rebar package at
https://salsa.debian.org/erlang-team/packages/rebar/-/tree/master
It includes a patch which makes generating ERL_LDFLAGS dynamically: it
includes -lerl_interface if it's available.
Also, I've updated the formal packagig stuff (VCS headers, debhelper
compatibility level, standards version).
So, If the changes are good enough for you, I could upload the package.

Cheers!
-- 
Sergei Golovan

Bug#961813: the missing firmware

[permondes - sagen]

Missing firmware is:

W: Possible missing firmware /lib/firmware/i915/icl_dmc_ver1_09.bin for
module i915
W: Possible missing firmware /lib/firmware/i915/tgl_dmc_ver2_04.bin for
module i915

W: Possible missing firmware /lib/firmware/i915/skl_huc_2.0.0.bin for
module i915

W: Possible missing firmware /lib/firmware/i915/bxt_huc_2.0.0.bin for
module i915

W: Possible missing firmware /lib/firmware/i915/kbl_huc_4.0.0.bin for
module i915

W: Possible missing firmware /lib/firmware/i915/glk_huc_4.0.0.bin for
module i915

W: Possible missing firmware /lib/firmware/i915/kbl_huc_4.0.0.bin for
module i915

W: Possible missing firmware /lib/firmware/i915/cml_huc_4.0.0.bin for
module i915

W: Possible missing firmware /lib/firmware/i915/cml_guc_33.0.0.bin for
module i915

W: Possible missing firmware /lib/firmware/i915/icl_huc_9.0.0.bin for
module i915

W: Possible missing firmware /lib/firmware/i915/ehl_huc_9.0.0.bin for
module i915

W: Possible missing firmware /lib/firmware/i915/ehl_guc_33.0.4.bin for
module i915

W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.0.3.bin for
module i915

W: Possible missing firmware /lib/firmware/i915/tgl_guc_35.2.0.bin for
module i915

Bug#961660: DebHelper dh_bash-completion broken since Stretch OS, Bash Completion scripts not installed anymore into Path according to debian/.bash-completion

[Jürgen Kuri]

On Sun, 31 May 2020 15:00:46 -0300 "Gabriel F. T. Gomes" 
 wrote:
> On the other, you are saying that the completions do not work from this
> location, and that's puzzling me. Could you provide more details about
> the problem you are actually getting? Bash-completion is supposed to
> work with files in this location.

One detail is, if you invoke the program fsmtool2 or fsmtool2_mtest for which I 
have the completion scripts, the directory listing of $PWD is shown if I press 
TAB two times consecutively.

As another detail find attached the completion script.


Thanks
Jürgen
have fsmtool2 && {
_fsmtool2_commands() {
COMPREPLY=( $(compgen -W "help showconfig showfiles showfileslex deleteall" 
-- $1) )
}

_fsmtool2()
{
local areas command cur
cur=${COMP_WORDS[COMP_CWORD]}
command=${COMP_WORDS[1]}
case $COMP_CWORD in
1)
_fsmtool2_commands $cur
;;
2)
case $command in
help)
_fsmtool2_commands $cur
;;
showconfig|showfiles|showfileslex|deleteall)
areas=$(grep '^\s*AREA' /etc/fsmd2/fsmd2.conf | awk '{print 
$2}')
COMPREPLY=( $(compgen -W "$areas" -- $cur) )
;;
esac
;;
3)
case $command in
showfiles|showfileslex)
COMPREPLY=-n
;;
esac
;;
esac
}
complete -F _fsmtool2 fsmtool2
}


0xA811F9F222306A1E.asc
Description: application/pgp-keys

Bug#962037: [Pkg-javascript-devel] Bug#962037: Acknowledgement (rainloop: FTBFS with node-less in experimental - TypeError: less.render is not a function)

[Pirate Praveen]

Control: clone -1 -2
Control: reassign -1 less.js
Control: found -1 3.11.1-1
Control: reassign -2 rainloop
Control: retitle -1 less.js: causes FTBFS in rainloop - TypeError: 
less.render is not a function

Control: retitle -2 rainloop: include package.json in embedded modules

On Tue, Jun 2, 2020 at 4:30 pm, Pirate Praveen 
 wrote:
While at it, please also use components via watch + uscan or add them 
to debian/build_modules (both of the moethods will have the modules 
linked to node_modules directory during build when pkg-js-tools is 
used) so we can easily track their versions and update them when 
required. Currently we have no information about the versions of 
these components in debian/build.


I have split this into 2 separate bugs now.

After using add-module-exports plugin in babel, the error now changed 
to,


gulp rainloop
[11:11:47] Local modules not found in /<>
[11:11:47] Try running: npm install
[11:11:47] Using globally installed gulp
[11:11:48] Using gulpfile /<>/gulpfile.js
[11:11:48] Starting 'rainloop'...
[11:11:48] Starting ''...
[11:11:48] Finished '' after 5.87 ms
[11:11:48] Starting 'assetsCopy'...
[11:11:48] Finished 'assetsCopy' after 71 ms
[11:11:48] Starting 'jsClean'...
[11:11:48] Starting 'cssClean'...
[11:11:48] Starting 'momentLocalesClear'...
[11:11:48] Starting 'ckeditorClear'...
[11:11:48] Starting 'fontasticFontsClear'...
[11:11:48] Starting 'lightgalleryFontsClear'...
[11:11:48] Finished 'ckeditorClear' after 2.6 ms
[11:11:48] Starting 'ckeditorCopyPlugins'...
[11:11:48] Finished 'jsClean' after 7.24 ms
[11:11:48] Starting ''...
[11:11:48] Finished 'cssClean' after 147 ms
[11:11:48] Starting 'cssMainBuild'...
[11:11:48] Starting 'cssSocialBuild'...
[11:11:48] Finished 'momentLocalesClear' after 152 ms
[11:11:48] Starting 'momentLocales'...
[11:11:48] Finished 'fontasticFontsClear' after 153 ms
[11:11:48] Starting 'fontasticFontsCopy'...
[11:11:48] Finished 'lightgalleryFontsClear' after 154 ms
[11:11:48] Starting 'lightgalleryFontsCopy'...
[11:11:48] Finished 'momentLocales' after 13 ms
[11:11:48] Finished 'cssSocialBuild' after 123 ms
[11:11:49] Finished 'lightgalleryFontsCopy' after 495 ms
[11:11:49] Finished 'fontasticFontsCopy' after 892 ms
[11:11:52] Finished 'ckeditorCopyPlugins' after 4.29 s
(node:170700) UnhandledPromiseRejectionWarning: TypeError 
[ERR_INVALID_ARG_TYPE]: The first argument must be one of type string, 
Buffer, ArrayBuffer, Array, or Array-like Object. Received type object

   at Function.from (buffer.js:231:9)
   at new Buffer (buffer.js:181:17)
   at /<>/debian/build/gulp-less.js:40:23
   at /usr/share/nodejs/less/dist/less/render.js:49:9
   at /usr/share/nodejs/less/dist/less/parse.js:97:9
   at ImportVisitor.finish [as _finish] 
(/usr/share/nodejs/less/dist/less/parser/parser.js:263:18)
   at ImportVisitor._onSequencerEmpty 
(/usr/share/nodejs/less/dist/less/visitors/import-visitor.js:50:10)
   at ImportSequencer.tryRun 
(/usr/share/nodejs/less/dist/less/visitors/import-sequencer.js:82:14)
   at 
/usr/share/nodejs/less/dist/less/visitors/import-sequencer.js:43:25
   at fileParsedFunc 
(/usr/share/nodejs/less/dist/less/import-manager.js:102:13)
(node:170700) UnhandledPromiseRejectionWarning: Unhandled promise 
rejection. This error originated either by throwing inside of an async 
function without a catch block, or by rejecting a promise which was not 
handled with .catch(). (rejection id: 1)

[11:12:01] Finished '' after 13 s
[11:12:01] Starting 'jsLibs'...
[11:12:01] Starting 'jsApp'...
[11:12:01] Starting 'jsAdmin'...
[11:12:01] 'jsLibs' errored after 12 ms
[11:12:01] Error: File not found with singular glob: 
/usr/lib/nodejs/autolinker/dist/Autolinker.js (if this was purposeful, 
use `allowEmpty` option)
   at Glob. 
(/usr/share/nodejs/glob-stream/readable.js:84:17)

   at Object.onceWrapper (events.js:286:20)
   at Glob.emit (events.js:198:13)
   at Glob.EventEmitter.emit (domain.js:448:20)
   at Glob._finish (/usr/share/nodejs/glob/glob.js:197:8)
   at done (/usr/share/nodejs/glob/glob.js:182:14)
   at Glob._processSimple2 (/usr/share/nodejs/glob/glob.js:688:12)
   at /usr/share/nodejs/glob/glob.js:676:10
   at Glob._stat2 (/usr/share/nodejs/glob/glob.js:772:12)
   at lstatcb_ (/usr/share/nodejs/glob/glob.js:764:12)
[11:12:01] 'rainloop' errored after 13 s
[11:12:01] The following tasks did not complete: , , 
cssMainBuild, jsApp, jsAdmin

[11:12:01] Did you forget to signal async completion?

Just for the record, using @babel/proposal-export-default-from does not 
work. So we will need to tweak more to get closer to upstream built 
less.

Bug#962038: raspi-firmware: Add Bluetooth firmware

[Bastian Germann]

Package: raspi-firmware
Severity: wishlist

Hi,

The firmware for the Raspberry Pi 3 Bluetooth chip is missing from
Debian non-free. On Raspbian, it is packaged as part of bluez-firmware
(https://github.com/RPi-Distro/bluez-firmware).
Ubuntu put it in their linux-firmware-raspi2 pkg with the eoan release
(https://bugs.launchpad.net/bugs/1824338).

Please consider importing the Bluetooth firmware for raspi-firmware as
well. I guess this is a better option than to add it to Debian's
bluez-firmware.

For the current firmware version, please have a look at the Raspbian
package and for the license information, please refer to the Ubuntu
package's copyright file.

Cheers,
Bastian

Bug#961594: Connection failed [IP: 151.101.112.204 80]

[Christoph Berg]

Re: Julien Cristau 2020-05-27 <20200527130809.GA1144124@chou>
> > 26 11:58  11:53:34 Err http://security.debian.org/debian-security 
> > stretch/updates/main
> > amd64 libldap-common all 2.4.44+dfsg-5+deb9u4
> > 26 11:58  11:53:34   Connection failed [IP: 151.101.112.204 80]

It just happened again, this time on jessie (for the first time I
think):

12:05:42 E: Failed to fetch 
http://security.debian.org/debian-security/pool/updates/main/k/krb5/libkrb5support0_1.12.1+dfsg-19+deb8u5_amd64.deb
  Connection failed [IP: 151.101.64.204 80]

Source IP in range 176.9.80.32 - 176.9.80.63
netname:HETZNER-fsn1-dc6

> I wonder if turning on apt's Debug::Acquire::http would give more of a
> clue on where things go wrong?  OTOH given this is highly intermittent
> it'd be quite noisy...  Christoph, would you be able to give that a try?

I'll do that now. The first two retries with that setting didn't
reproduce the problem, though.

Christoph

Bug#881719: libcdio 2.1.0 and lubcdio++

[Bálint Réczey]

Hi Gabriel,

Gabriel F. T. Gomes  ezt írta (időpont:
2020. jún. 2., K, 0:46):
>
> On 01 Jun 2020, Bálint Réczey wrote:
> >
> >I've checked the package and it refers to
> >https://salsa.debian.org/debian/libcdio as the packaging repo while it
> >is not present.
> >I fyou agree let me clone your packaging repo there, then I can review
> >the changes.
>
> Oh, please. And thank you. :)

Done. I've omitted the last commit because I suggest using -1~exp0
Debian version for the upload to experimental. IMO looks nicer when
the upload to unstable has -1.
I've also added Salsa CI configuration, please see the results at:
https://salsa.debian.org/debian/libcdio/pipelines

In general the changes look good and I'll sponsor the upload when I
get my keys updated (unless Mattia or someone else does it earlier).
Going forward I recommend converting debian/rules to modern debhelper
style and fixing reprotest would also be nice.

Cheers,
Balint


> >I can't upload in the next few days (weeks?) because my keys are
> >expired and I'm waiting for the next keyring push to get them
> >refreshed.
>
> No problem.
>
>
> Cheers,
> Gabriel