Bug#987759: RFS: color-picker/1.0.1-1 [ITP] -- Powerful screen color picker based on Qt

[Hugo Torres]

debian/tests/control has been removed because it does not provide any
useful tests, avoiding errors with autopkgtest.


--
Hugo Torres de Lima
GPG: 4AF1 1173 DCAD 0380 CC43 A5C6 365C 8CEF 4233 E3D8

Sent with ProtonMail Secure Email.

‐‐‐ Original Message ‐‐‐
On Sunday, May 16, 2021 3:14 AM, Adam Borowski  wrote:

> On Thu, Apr 29, 2021 at 01:02:08AM -0300, Hugo Torres de Lima wrote:
> 

> > -   Package name : color-picker
> > Version : 1.0.1-1
> > 

> 

> > color-picker (1.0.1-1) experimental; urgency=medium
> > .
> > 

> > -   Initial release (Closes: #987756)
> 

> Hi!
> The autopkgtest sometimes fails:
> autopkgtest [22:06:30]: test command1: xvfb-run -a color-picker &
> autopkgtest [22:06:30]: test command1: [---
> QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kilobyte'
> autopkgtest [22:06:30]: test command1: ---]
> autopkgtest [22:06:30]: test command1: - - - - - - - - - - results - - - - - 
> - - - - -
> command1 FAIL stderr: QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to 
> '/tmp/runtime-kilobyte'
> autopkgtest [22:06:31]: test command1: - - - - - - - - - - stderr - - - - - - 
> - - - -
> QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kilobyte'
> autopkgtest [22:06:31]:  summary
> command1 FAIL stderr: QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to 
> '/tmp/runtime-kilobyte'
> 

> But, what it is even supposed to do?
> Save from racey stderr messages from very early startup, this won't fail
> even if the package is completely broken, due to '&':
> Test-Command: false &
> succeeds. I see where you copied this from -- a bunch of GUI packages
> also have such bogus autopkgtests, but they do nothing useful. Eg.
> Test-Command: xvfb-run -a /usr/bin/gcrytsal &
> (package gnome-chemistry-utils) doesn't catch even the obvious typo.
> 

> Meow!
> 

> --
> ⢀⣴⠾⠻⢶⣦⠀ The oldest dated printed book includes the following license grant:
> ⣾⠁⢠⠒⠀⣿⡁ Reverently made for universal free distribution by Wang Jie
> ⢿⡄⠘⠷⠚⠋⠀ on behalf of his two parents on the 15th of the 4th moon of
> ⠈⠳⣄ the 9th year of Xiantong [11 May 868].



signature.asc
Description: OpenPGP digital signature

Bug#988431: RFS: open-invaders/0.3-6 [QA] -- Space Invaders clone

[Hugo Torres]

debian/tests/control has been removed because it does not provide any
useful tests, avoiding errors with autopkgtest.


--
Hugo Torres de Lima
GPG: 4AF1 1173 DCAD 0380 CC43 A5C6 365C 8CEF 4233 E3D8

Sent with ProtonMail Secure Email.

‐‐‐ Original Message ‐‐‐
On Sunday, May 16, 2021 10:46 AM, Adam Borowski  wrote:

> On Wed, May 12, 2021 at 06:38:28PM -0300, Hugo Torres wrote:
> 

> > -   Package name : open-invaders
> > Version : 0.3-6
> > 

> 

> > Changes since the last upload:
> > open-invaders (0.3-6) experimental; urgency=medium
> > .
> > 

> > -   QA upload.
> > -   debian/control:
> > -   Added 'Rules-Requires-Root: no' to source stanza.
> > -   Added Vcs-* URLs to salsa.debian.org.
> > -   Bumped DH level format to 13.
> > -   Bumped Standards-Version to 4.5.1.
> > -   Updated homepage.
> > -   debian/copyright: Updated for format 1.0.
> > -   debian/lintian-overrides: Created for false positive.
> > -   debian/debian/open-invaders-data.docs renamed for open-invaders.docs.
> > -   debian/open-invaders.desktop: Added Keywords.
> > -   debian/patches/doc_directory_commented.patch: Created.
> > -   debian/patches/fix_ftbfs_gcc45.patch: Added header.
> > -   debian/patches/fix_pmask_amd64.patch: Added header.
> > -   debian/patches/format_security.patch: Added date in header.
> > -   debian/rules: Added the DEB_BUILD_MAINT_OPTIONS, 
> > DEB_CXXFLAGS_MAINT_APPEND,
> > DEB_CFLAGS_MAINT_APPEND and DEB_LDFLAGS_MAINT_APPEND variable
> > to improve the GCC hardening.
> > 

> > -   debian/salsa-ci.yml: Added to provide CI tests for Salsa.
> > -   debian/tests/control: Created for basic CI testing.
> > -   debian/upstream/metadata: Created.
> > -   debian/watch:
> > -   Bumped to version 4.
> > -   Updated the source address.
> 

> Alas, the autopkgtest fails -- and is bogus.
> 

> autopkgtest [15:02:01]: test command1: xvfb-run -a open-invaders &
> autopkgtest [15:02:01]: test command1: [---
> /usr/share
> ALSA lib confmisc.c:767:(parse_card) cannot find card '0'
> ALSA lib conf.c:4745:(_snd_config_evaluate) function snd_func_card_driver 
> returned error: No such file or directory
> ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings
> ALSA lib conf.c:4745:(_snd_config_evaluate) function snd_func_concat returned 
> error: No such file or directory
> ALSA lib confmisc.c:1246:(snd_func_refer) error evaluating name
> ALSA lib conf.c:4745:(_snd_config_evaluate) function snd_func_refer returned 
> error: No such file or directory
> ALSA lib conf.c:5233:(snd_config_expand) Evaluate error: No such file or 
> directory
> ALSA lib pcm.c:2660:(snd_pcm_open_noupdate) Unknown PCM default
> autopkgtest [15:02:01]: test command1: ---]
> autopkgtest [15:02:01]: test command1: - - - - - - - - - - results - - - - - 
> - - - - -
> command1 FAIL stderr: ALSA lib confmisc.c:767:(parse_card) cannot find card 
> '0'
> autopkgtest [15:02:01]: test command1: - - - - - - - - - - stderr - - - - - - 
> - - - -
> ALSA lib confmisc.c:767:(parse_card) cannot find card '0'
> ALSA lib conf.c:4745:(_snd_config_evaluate) function snd_func_card_driver 
> returned error: No such file or directory
> ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings
> ALSA lib conf.c:4745:(_snd_config_evaluate) function snd_func_concat returned 
> error: No such file or directory
> ALSA lib confmisc.c:1246:(snd_func_refer) error evaluating name
> ALSA lib conf.c:4745:(_snd_config_evaluate) function snd_func_refer returned 
> error: No such file or directory
> ALSA lib conf.c:5233:(snd_config_expand) Evaluate error: No such file or 
> directory
> ALSA lib pcm.c:2660:(snd_pcm_open_noupdate) Unknown PCM default
> autopkgtest [15:02:01]:  summary
> command1 FAIL stderr: ALSA lib confmisc.c:767:(parse_card) cannot find card 
> '0'
> 

> But that failure happened only due to luck. The '&' at the end stops
> most of errors from causing a failure, even "Test-Command: false &"
> succeeds.
> 

> Meow!
> 

> --
> ⢀⣴⠾⠻⢶⣦⠀ The oldest dated printed book includes the following license grant:
> ⣾⠁⢠⠒⠀⣿⡁ Reverently made for universal free distribution by Wang Jie
> ⢿⡄⠘⠷⠚⠋⠀ on behalf of his two parents on the 15th of the 4th moon of
> ⠈⠳⣄ the 9th year of Xiantong [11 May 868].



signature.asc
Description: OpenPGP digital signature

Bug#988583: elpa-debian-el: Cannot report any bugs at all. It is broken.

[Nicholas D Steeves]

Hi Salman,

Salman Mohammadi  writes:

> I could reproduce this bug under this environment:
>
>    1. clean install debian stable in a vm
>
>    2. upgrade debian to sid
>
>    3. install emacs and debian-el: $ sudo apt -y install emacs 
> elpa-debian-el
>
>
> Now, M-x debian-bug command does not work correctly.
>

I think there's something missing from your steps to reproduce.

I tried this:
1. With a clean chroot, 'sudo apt install emacs-nox elpa-debian-el'
   * Given that Emacs was not installed in the stable VM until
 post-upgrade, I don't think my digression is a relevant variable.
2. Start Emacs
3. M-x debian-bug
4. Everything appears to work fine.  After composing the full text of
   the bug, I hit C-c C-c, and then see the *Emacs Mail Setup Help*
   window appear, along with a minibuffer prompt.  From the original bug
   report email it sounds like this is farther along then you were able
   to get?

a. My hostname is a real FQDN (however no longer functional due to
expired dyndns subscription--post-Oracle acquisition is a rip-off).
It's possible that this bug only exists on hosts that don't have a FQDN
hostname.
b. Reportbug has not been configured.

Regards,
Nicholas


signature.asc
Description: PGP signature

Bug#988629: mariadb-10.5: FTBFS on armel: selected processor does not support `isb' in ARM mode

[Otto Kekäläinen]

Source: mariadb-10.5
Version: 1:10.5.10-1
Tags: confirmed, help, ftbfs
Severity: important
Justification: armel is an official Debian architecture, regression
must be fixed ASAP
User: debian-...@lists.debian.org
Usertags: armel, arm

After uploading MariaDB 10.5.10 to Debian I noticed the armel build regressed:
https://buildd.debian.org/status/package.php?p=mariadb-10.5

*
Full log: 
https://buildd.debian.org/status/fetch.php?pkg=mariadb-10.5=armel=1%3A10.5.10-1=1621221941=0
*
[ 14%] Built target todo-t
[ 14%] Building CXX object wsrep-lib/src/CMakeFiles/wsrep-lib.dir/logger.cpp.o
cd /<>/builddir/wsrep-lib/src && /usr/bin/c++ -DNDEBUG
-I/<>/wsrep-lib/include
-I/<>/wsrep-lib/wsrep-API/v26
-I/<>/wsrep-lib/wsrep-API -g -O2
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time
-D_FORTIFY_SOURCE=2 -pie -fPIC -fstack-protector
--param=ssp-buffer-size=4 -Wall -Wextra -Woverloaded-virtual
-Wconversion -g -Wsuggest-override -O2 -g -static-libgcc
-fno-omit-frame-pointer -fno-strict-aliasing -Wno-uninitialized
-fno-omit-frame-pointer -D_FORTIFY_SOURCE=2   -Wdate-time
-D_FORTIFY_SOURCE=2 -std=gnu++11 -o
CMakeFiles/wsrep-lib.dir/logger.cpp.o -c
/<>/wsrep-lib/src/logger.cpp
/usr/bin/make  -f
unittest/examples/CMakeFiles/no_plan-t.dir/build.make
unittest/examples/CMakeFiles/no_plan-t.dir/depend
make[4]: Entering directory '/<>/builddir'
cd /<>/builddir && /usr/bin/cmake -E cmake_depends "Unix
Makefiles" /<> /<>/unittest/examples
/<>/builddir /<>/builddir/unittest/examples
/<>/builddir/unittest/examples/CMakeFiles/no_plan-t.dir/DependInfo.cmake
--color=
Dependee 
"/<>/builddir/unittest/examples/CMakeFiles/no_plan-t.dir/DependInfo.cmake"
is newer than depender
"/<>/builddir/unittest/examples/CMakeFiles/no_plan-t.dir/depend.internal".
Dependee 
"/<>/builddir/unittest/examples/CMakeFiles/CMakeDirectoryInformation.cmake"
is newer than depender
"/<>/builddir/unittest/examples/CMakeFiles/no_plan-t.dir/depend.internal".
Scanning dependencies of target no_plan-t
make[4]: Leaving directory '/<>/builddir'
/usr/bin/make  -f
unittest/examples/CMakeFiles/no_plan-t.dir/build.make
unittest/examples/CMakeFiles/no_plan-t.dir/build
make[4]: Entering directory '/<>/builddir'
[ 14%] Building C object
unittest/examples/CMakeFiles/no_plan-t.dir/no_plan-t.c.o
cd /<>/builddir/unittest/examples && /usr/bin/cc
-DDBUG_TRACE -DHAVE_CONFIG_H -D_FILE_OFFSET_BITS=64
-I/<>/wsrep-lib/include
-I/<>/wsrep-lib/wsrep-API/v26
-I/<>/builddir/include -I/<>/include
-I/<>/unittest/mytap -g -O2
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time
-D_FORTIFY_SOURCE=2 -pie -fPIC -fstack-protector
--param=ssp-buffer-size=4 -O2 -g -static-libgcc
-fno-omit-frame-pointer -fno-strict-aliasing  -Wno-uninitialized
-fno-omit-frame-pointer -D_FORTIFY_SOURCE=2 -DDBUG_OFF -Wall
-Wdeclaration-after-statement -Wextra -Wformat-security
-Wno-format-truncation -Wno-init-self -Wno-nonnull-compare
-Wno-unused-parameter -Wvla -Wwrite-strings   -Wdate-time
-D_FORTIFY_SOURCE=2 -o CMakeFiles/no_plan-t.dir/no_plan-t.c.o -c
/<>/unittest/examples/no_plan-t.c
/tmp/cc3B6r4f.s: Assembler messages:
/tmp/cc3B6r4f.s:312: Error: selected processor does not support `isb'
in ARM mode
/tmp/cc3B6r4f.s:1487: Error: selected processor does not support `isb'
in ARM mode
make[4]: *** [mysys/CMakeFiles/mysys.dir/build.make:1255:
mysys/CMakeFiles/mysys.dir/lf_alloc-pin.c.o] Error 1
make[4]: Leaving directory '/<>/builddir'
make[3]: *** [CMakeFiles/Makefile2:9892: mysys/CMakeFiles/mysys.dir/all] Error 2
*

Bug#988603: Technical details of CVE-2021-3541

[Sebastian Pipping]

Hi!

> Technical details for the vulnerability are unfortunately not public,

I have blogged about the technical details of CVE-2021-3541 at:
https://blog.hartwork.org/posts/cve-2021-3541-parameter-laughs-fixed-in-libxml2-2-9-11/
.

Best, Sebastian

Bug#988217: bootefi causes boot failure with boot.scr

[Vagrant Cascadian]

Control: severity 988217 serious

On 2021-05-07, Vagrant Cascadian wrote:
> On 2021-04-16, Bastian Germann wrote:
>> On a Lamobo R1, I can verify 2021.01 versions not to boot with a
>> default environment. However, 2020.10+dfsg-2 boots. Even though the
>> original issue has the same outcome, I guess it is caused by something
>> else.
>
> Different enough to warrant it's own bug, cloning...
>
>
>> I figured out my problem is caused by
>> https://github.com/u-boot/u-boot/commit/f3866909e35074ea6f50226d40487a180de1132f.
>>  The
>> boot_efi_bootmgr will run and read a bad dtb, which makes a boot.scr
>> boot fail.
>
> This would definitely be good to fix in bullseye, but this is quite late
> in the release cycle.

After recently upgrading several more systems that turned out to be
affected by this, I'm bumping the severity of this bug...


> Will need to test failure and success cases with and without EFI as well
> as boot.scr and extlinux.conf to make sure this doesn't cause
> regressions in other boot paths...

This still needs some work!


> An ugly workaround in the meantime would be to add a no-op boot.scr on
> the media (e.g. mmc0) and then fall back to the other boot methods.

I'm not sure this workaround is viable in a variety of situations...


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#877763: linux: Still occuring in linux-4.19.0-2-amd64: fs/btrfs/ctree.h:1588 btrfs_update_device

[Matthew Goff]

No, I am not. Currently running 5.10.0-6-amd64 without this issue.

On Sat, May 15, 2021 at 1:50 PM Salvatore Bonaccorso 
wrote:

> Control: tags -1 + moreinfo
>
> Hi,
>
> On Sun, Mar 03, 2019 at 07:31:34AM -0600, Matthew Goff wrote:
> > Source: linux
> > Followup-For: Bug #877763
> >
> > Dear Maintainer,
> >
> > I'm still seeing these btrfs trace messages on 4.19.0-2-amd64
>
> Are you still experiencing the issues with a kernel from unstable or
> buster-backports?
>
> If yes, can you please report this upstream, keeping this bug in the
> loop?
>
> Regards,
> Salvatore
>

Bug#988608: RFS: scrollz/2.2.3-2 - advanced ircII-based IRC client

[Mike Markley]

Package: sponsorship-requests
Severity: normal

I'm seeking assistance uploading a new version of the ScrollZ IRC client
to unstable that addresses an outstanding CVE:
https://security-tracker.debian.org/tracker/CVE-2021-29376.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986215

Changes:
 scrollz (2.2.3-2) unstable; urgency=high
 .
   * Applied patch to ctcp.c to fix CVE-2021-29376 from
 https://github.com/ScrollZ/ScrollZ/pull/26 (Closes: #986215)
   * Applied minor patch from upstream to the above fix

I'm listed as the maintainer in this package's control file, but I haven't
had a key in the keyring for several years.

This should be the minimum change required to fix this issue. I anticipate
there will also be stable and possibly oldstable uploads, as well.

Post-freeze, I do plan to update the source package to a newer upstream
version.

-- 
Mike Markley 

Bug#983095: pidgin: 5353/udp probe every 2 sec

[Richard Laager]

On 5/16/21 3:21 AM, Slavko wrote:

I didn't see it, pidgin.log attached, but tcpdump shows them. Then i
tried it with -f option to strace:


Good thinking. So it's happening in a child process.

A good next step is to use gdb, but the fork will complicate things. I 
think you can do "set detach-on-fork off", but I'm not sure.


If that doesn't work, then you probably need to figure out how many 
child processes it forks off before the child that we are interested in. 
From the strace, it looks like it's the second child that we care 
about. So try this:

  gdb pidgin
  set args -c pidgin-test
  set pagination off
  set logging file pidgin-gdb.txt
  set logging on
  watch fork
  run

  # When it forks the first time:
  continue

  # When it forks the second time, set it to follow the child:
  set follow-fork-mode child

  break socket
  commands
  bt
  continue
  end

  break sendto
  commands
  bt
  continue
  end

  continue

The goal here is to get a backtrace of it opening the socket() and/or 
sendto() on the socket.



Since you're on sid, you should be able to use debuginfod (though I
have never used it personally):


I am on testing, are the instructions still relevant?


I think debuginfod will work. If not you can follow the instructions to 
install dbgsym packages for pidgin & libpurple0.


--
Richard

Bug#988628: unblock: six/1.16.0-1

[Stefano Rivera]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: cjwat...@debian.org
Control: block 988418 with -1

Please unblock package six

There is a new six in unstable that python-pip built against, it needs
to migrate for pip to be able to.

[ Reason ]
New upstream release, with minor improvement for Python 3.10.

[ Impact ]
python-pip won't migrate (#988418).

[ Tests ]
Upstream tests are run at build. But the changed code isn't covered by
any new tests.

[ Risks ]
Minimal changes in a very stable library.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

unblock six/1.16.0-1
diff -Nru six-1.15.0/CHANGES six-1.16.0/CHANGES
--- six-1.15.0/CHANGES  2020-05-21 11:25:33.0 -0400
+++ six-1.16.0/CHANGES  2021-05-05 10:17:58.0 -0400
@@ -3,6 +3,12 @@
 
 This file lists the changes in each six version.
 
+1.16.0
+--
+
+- Pull request #343, issue #341, pull request #349: Port _SixMetaPathImporter 
to
+  Python 3.10.
+
 1.15.0
 --
 
@@ -100,7 +106,7 @@
 
 - Issue #98: Fix `six.moves` race condition in multi-threaded code.
 
-- Pull request #51: Add `six.view(keys|values|itmes)`, which provide dictionary
+- Pull request #51: Add `six.view(keys|values|items)`, which provide dictionary
   views on Python 2.7+.
 
 - Issue #112: `six.moves.reload_module` now uses the importlib module on
@@ -227,7 +233,7 @@
 - Issue #40: Add import mapping for the Python 2 gdbm module.
 
 - Issue #35: On Python versions less than 2.7, print_ now encodes unicode
-  strings when outputing to standard streams. (Python 2.7 handles this
+  strings when outputting to standard streams. (Python 2.7 handles this
   automatically.)
 
 1.4.1
diff -Nru six-1.15.0/debian/changelog six-1.16.0/debian/changelog
--- six-1.15.0/debian/changelog 2020-11-09 20:16:45.0 -0400
+++ six-1.16.0/debian/changelog 2021-05-09 06:40:54.0 -0400
@@ -1,3 +1,9 @@
+six (1.16.0-1) unstable; urgency=medium
+
+  * New upstream release.
+
+ -- Colin Watson   Sun, 09 May 2021 11:40:54 +0100
+
 six (1.15.0-2) unstable; urgency=medium
 
   [ Ondřej Nový ]
diff -Nru six-1.15.0/PKG-INFO six-1.16.0/PKG-INFO
--- six-1.15.0/PKG-INFO 2020-05-21 11:25:53.508234700 -0400
+++ six-1.16.0/PKG-INFO 2021-05-05 10:18:16.777235000 -0400
@@ -1,6 +1,6 @@
 Metadata-Version: 1.2
 Name: six
-Version: 1.15.0
+Version: 1.16.0
 Summary: Python 2 and 3 compatibility utilities
 Home-page: https://github.com/benjaminp/six
 Author: Benjamin Peterson
diff -Nru six-1.15.0/six.egg-info/PKG-INFO six-1.16.0/six.egg-info/PKG-INFO
--- six-1.15.0/six.egg-info/PKG-INFO2020-05-21 11:25:53.0 -0400
+++ six-1.16.0/six.egg-info/PKG-INFO2021-05-05 10:18:16.0 -0400
@@ -1,6 +1,6 @@
 Metadata-Version: 1.2
 Name: six
-Version: 1.15.0
+Version: 1.16.0
 Summary: Python 2 and 3 compatibility utilities
 Home-page: https://github.com/benjaminp/six
 Author: Benjamin Peterson
diff -Nru six-1.15.0/six.py six-1.16.0/six.py
--- six-1.15.0/six.py   2020-05-21 11:25:33.0 -0400
+++ six-1.16.0/six.py   2021-05-05 10:17:58.0 -0400
@@ -29,7 +29,7 @@
 import types
 
 __author__ = "Benjamin Peterson "
-__version__ = "1.15.0"
+__version__ = "1.16.0"
 
 
 # Useful for very coarse version differentiation.
@@ -71,6 +71,11 @@
 MAXSIZE = int((1 << 63) - 1)
 del X
 
+if PY34:
+from importlib.util import spec_from_loader
+else:
+spec_from_loader = None
+
 
 def _add_doc(func, doc):
 """Add documentation to a function."""
@@ -186,6 +191,11 @@
 return self
 return None
 
+def find_spec(self, fullname, path, target=None):
+if fullname in self.known_modules:
+return spec_from_loader(fullname, self)
+return None
+
 def __get_module(self, fullname):
 try:
 return self.known_modules[fullname]
@@ -223,6 +233,12 @@
 return None
 get_source = get_code  # same as get_code
 
+def create_module(self, spec):
+return self.load_module(spec.name)
+
+def exec_module(self, module):
+pass
+
 _importer = _SixMetaPathImporter(__name__)
 
 

Bug#988627: unblock: broadcom-sta/6.30.223.271-16.1

[Ben Hutchings]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: bl...@debian.org, clac...@easter-eggs.com, r...@debian.org

Please unblock package broadcom-sta

[ Reason ]
Fix the unusable broadcom-sta-source package.

[ Impact ]
It is not possible to build a package using module-assistant and the
version of broadcom-sta-source in bullseye.  However, dkms and
broadcom-sta-dkms can be used as an alternative.

[ Tests ]
Only the build processes are being changed.  I tested that:
- broadcom-sta can be built from source
- module-assistant can build a module package from broadcom-sta-source
  for the current kernel version in bullseye (5.10.0-6-amd64)
- the resulting binary module package looks like a module package
  built from broadcom-sta-source in buster, modulo version changes

[ Risks ]
This seems like a low-risk change.

[ Checklist ]
  [X] all changes are documented in the d/changelog
  [X] I reviewed all changes and I approve them
  [X] attach debdiff against the package in testing

[ Other info ]

unblock broadcom-sta/6.30.223.271-16.1
diff -Nru broadcom-sta-6.30.223.271/debian/changelog 
broadcom-sta-6.30.223.271/debian/changelog
--- broadcom-sta-6.30.223.271/debian/changelog  2021-05-04 11:11:49.0 
+0200
+++ broadcom-sta-6.30.223.271/debian/changelog  2021-05-17 01:06:42.0 
+0200
@@ -1,3 +1,14 @@
+broadcom-sta (6.30.223.271-16.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * debian/control.modules.in:
+- Declare debhelper compat level through a build-dependency
+  (Closes: #988562)
+  * debian/rules:
+- Fix copying of Debian files in install-source rule
+
+ -- Ben Hutchings   Mon, 17 May 2021 01:06:42 +0200
+
 broadcom-sta (6.30.223.271-16) unstable; urgency=medium
 
   * Upload to unstable.
diff -Nru broadcom-sta-6.30.223.271/debian/control.modules.in 
broadcom-sta-6.30.223.271/debian/control.modules.in
--- broadcom-sta-6.30.223.271/debian/control.modules.in 2021-05-04 
11:11:49.0 +0200
+++ broadcom-sta-6.30.223.271/debian/control.modules.in 2021-05-17 
00:56:52.0 +0200
@@ -2,7 +2,7 @@
 Section: non-free/kernel
 Priority: optional
 Maintainer: Cyril Lacoux 
-Build-Depends: debhelper (>= 8)
+Build-Depends: debhelper-compat (= 12)
 Standards-Version: 3.9.4
 Homepage: http://www.broadcom.com/support/802.11/linux_sta.php
 
diff -Nru broadcom-sta-6.30.223.271/debian/rules 
broadcom-sta-6.30.223.271/debian/rules
--- broadcom-sta-6.30.223.271/debian/rules  2021-05-04 11:11:49.0 
+0200
+++ broadcom-sta-6.30.223.271/debian/rules  2021-05-17 00:56:28.0 
+0200
@@ -45,8 +45,8 @@

# Copy Debian files
install -D -m 0755 debian/rules.modules $(source_debdir)/rules
-   for file in changelog compat control control.modules.in copyright; do \
-   install -m 644 debian/$$file $(source_debdir); \
+   for file in changelog control control.modules.in copyright; do \
+   install -m 644 debian/$$file $(source_debdir) || exit; \
done

# Make suitable tarball for module-assisant and kernel-package

Bug#988474: [Fwd: Bug#988474: RFS: freefem++/3.61.1+dfsg1-5.2 [NMU] [RC] -- Provides the binaries of the FreeFem++ FE suite]

[François Mazen]

Hello Anton,

> When the package is successfully built on all relevant platforms,
> you can ask the release team to unblock it. But it will unlikely
> happen
> due to release policy.

I've requested the unblock, see [1]. Let me know if I've missed
something.

Thanks again for the sponsoring!

Have a nice day,
François

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



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

Bug#988583: elpa-debian-el: Cannot report any bugs at all. It is broken.

[Salman Mohammadi]

On 5/16/21 3:04 PM, David Bremner wrote:

Salman Mohammadi  writes:


I have no .reportbugrc bit instead use the following configuration in my
.emacs:

    (setq user-mail-address "sal...@smoha.org"
          user-full-name "Salman Mohammadi")

    (setq send-mail-function 'mailclient-send-it)


I tried setting send-mail-function to mailclient-send-it (which by the
way tends to mangle attachements, but I guess that's not the issue here)
I still can't duplicate your issue.

You can try duplicating the problem with "emacs -q". You will
need to run M-x load-library  debian-el-autoloads .

If that works, then your issue is most likely an interaction with some
other emacs addon package. You can try removing them one by one, or
loading them manually into emacs -q.


Dear David,

I could reproduce this bug under this environment:

  1. clean install debian stable in a vm

  2. upgrade debian to sid

  3. install emacs and debian-el: $ sudo apt -y install emacs 
elpa-debian-el



Now, M-x debian-bug command does not work correctly.


Thanks, Salman

Bug#988554: xterm does not render U+A7BA ... U+A7F6

[Thomas Dickey]

On Sat, May 15, 2021 at 04:11:12PM +0200, Uwe Waldmann wrote:
> Package: xterm
> Version: 344-1+deb10u1
> Severity: important
> 
> Dear Maintainer,
> 
> xterm renders all characters between U+A7BA and U+A7F6 with width zero,
> that is, not at all, even if they are present in the chosen font.
> For instance,

According to https://unicodeplus.com/U+A7BA

The character Ꞻ (Latin Capital Letter Glottal A) is represented by the
Unicode codepoint U+A7BA.  It is encoded in the Latin Extended-D block,
which belongs to the Basic Multilingual Plane.  It was added to Unicode
in version 12.0 (March, 2019).  It is HTML encoded as .
 
xterm #344 is a little earlier than that.  Its fallback copy of wcwidth
doesn't list that range (I updated the table to Unicode 12 in #345,
and added a test-driver around that time).

The system wcwidth doesn't cover that range either.

Characters which aren't known to wcwidth are treated as nonprinting...

>   printf '<\uA7B9>\n'
> 
> displays "" with a slash through "u" (correct), whereas
> 
>   printf '<\uA7BA>\n'
> 
> displays "<>" (incorrect) instead of "" with an apostrophe before
> "A". The problem shows up with arbitrary fonts (both pcf and otb are
> affected). Using -mk_width does not change the situation.
> 
> (In Debian 9.1, it still worked correctly.)

hmm - which version of xterm was that?

I'm guessing that it was #327

(it should not have worked, but there's always the possibility that I
fixed a bug which was making it appear to work)

-- 
Thomas E. Dickey 
https://invisible-island.net
ftp://ftp.invisible-island.net


signature.asc
Description: PGP signature

Bug#988540: im-config: breaks the keyboard configuration

[Gunnar Hjalmarsson]

I pushed this commit:

https://salsa.debian.org/input-method-team/im-config/-/commit/47941de4

So, Vincent, this bug report has resulted in a tiny improvement at least. ;)

As regards the main topic I don't think it's really an im-config 
specific issue. im-config is run as an Xsession script, and possibly 
your setup with fvwm and an xkbcomp call in ~/.xsession is a rather 
special combo where things happen in the wrong order. Fortunately you 
were able to figure out the sleep() workaround.


Keeping the bug open for now to see if more users experience the same issue.

Rgds,
Gunnar Hjalmarsson

Bug#988562: broadcom-sta: diff for NMU version 6.30.223.271-16.1

[Ben Hutchings]

Control: tags 988562 + patch
Control: tags 988562 + pending

Dear maintainer,

I've prepared an NMU for broadcom-sta (versioned as 6.30.223.271-16.1)
and uploaded it.

The changes are attached as a debdiff, but you can also merge the
"debian" branch of .

Ben.

-- 
Ben Hutchings
Never attribute to conspiracy what can adequately be explained
by stupidity.
diff -Nru broadcom-sta-6.30.223.271/debian/changelog broadcom-sta-6.30.223.271/debian/changelog
--- broadcom-sta-6.30.223.271/debian/changelog	2021-05-04 11:11:49.0 +0200
+++ broadcom-sta-6.30.223.271/debian/changelog	2021-05-17 01:06:42.0 +0200
@@ -1,3 +1,14 @@
+broadcom-sta (6.30.223.271-16.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * debian/control.modules.in:
+- Declare debhelper compat level through a build-dependency
+  (Closes: #988562)
+  * debian/rules:
+- Fix copying of Debian files in install-source rule
+
+ -- Ben Hutchings   Mon, 17 May 2021 01:06:42 +0200
+
 broadcom-sta (6.30.223.271-16) unstable; urgency=medium
 
   * Upload to unstable.
diff -Nru broadcom-sta-6.30.223.271/debian/control.modules.in broadcom-sta-6.30.223.271/debian/control.modules.in
--- broadcom-sta-6.30.223.271/debian/control.modules.in	2021-05-04 11:11:49.0 +0200
+++ broadcom-sta-6.30.223.271/debian/control.modules.in	2021-05-17 00:56:52.0 +0200
@@ -2,7 +2,7 @@
 Section: non-free/kernel
 Priority: optional
 Maintainer: Cyril Lacoux 
-Build-Depends: debhelper (>= 8)
+Build-Depends: debhelper-compat (= 12)
 Standards-Version: 3.9.4
 Homepage: http://www.broadcom.com/support/802.11/linux_sta.php
 
diff -Nru broadcom-sta-6.30.223.271/debian/rules broadcom-sta-6.30.223.271/debian/rules
--- broadcom-sta-6.30.223.271/debian/rules	2021-05-04 11:11:49.0 +0200
+++ broadcom-sta-6.30.223.271/debian/rules	2021-05-17 00:56:28.0 +0200
@@ -45,8 +45,8 @@
 	
 	# Copy Debian files
 	install -D -m 0755 debian/rules.modules $(source_debdir)/rules
-	for file in changelog compat control control.modules.in copyright; do \
-		install -m 644 debian/$$file $(source_debdir); \
+	for file in changelog control control.modules.in copyright; do \
+		install -m 644 debian/$$file $(source_debdir) || exit; \
 	done
 	
 	# Make suitable tarball for module-assisant and kernel-package


signature.asc
Description: PGP signature

Bug#988089: [debian-mysql] Bug#988089: Bug#988089: mariadb-server: MariaDB uninstalled on dist-upgrade Debian 10 -> 11

[Otto Kekäläinen]

> > But as said, the bug #988089 can only be fixed by a change in galera-4
> > debian/control. Changing the mariadb-10.5 debian/control to
> > recommends:galera-4 is a separate change.
> Ok but I have no idea how this should be handled then.
>

I outlined the exact galera-4 debugging steps in my email on May 13th. The
solution can be found and also tested/validated easily with those steps.

Bug#988615: unblock: kodi-inputstream-adaptive/2.6.14+ds1-1

[Sebastian Ramacher]

Control: tags -1 moreinfo
Control: tags 988615 moreinfo
Control: tags 988616 moreinfo
Control: tags 988617 moreinfo
Control: tags 988618 moreinfo
Control: tags 988619 moreinfo
Control: tags 988620 moreinfo
Control: tags 988621 moreinfo
Control: tags 988622 moreinfo
Control: tags 988623 moreinfo
Control: tags 988624 moreinfo
Control: tags 988625 moreinfo

On 2021-05-16 22:35:16 +, vasek.ge...@gmail.com wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> X-Debbugs-Cc: mat...@debian.org
> 
> Please unblock package kodi-inputstream-adaptive
> 
> [ Reason ]
> 
> The bugfix point release companion to Kodi 19.1 and
> linked against its API provides.

And which bugs does that fix? Security issues? Please explain how
unblocking this package improves bullseye. This question also includes
all the other kodi-* unblock requests.

Cheers

> 
> [ Impact ]
> 
> Every point release brings several dozen bugfixes.
> No new functionality is added or breaking changes allowed.
> 
> [ Tests ]
> 
> Automated tests + manual testing by Kodi users
> 
> [ Risks ]
> 
> The struct release policy of upstream ensures no breaking
> changes are allowed past BETA releases. Point releases
> bring only bugfixes and security fixes.
> 
> [ Checklist ]
>   [x] all changes are documented in the d/changelog
>   [x] I reviewed all changes and I approve them
>   [x] attach debdiff against the package in testing
> 
> [ Other info ]
> 
> unblock kodi-inputstream-adaptive/2.6.14+ds1-1



-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#988581: emacs-gtk: Emacs hangs with 100% cpu if started within a current directory that has a name ending with ".tar"

[Rob Browning]

[When possible/appropriate, please preserve the 988581-forwarded address
 in replies.]

Recently reported, and I can reproduce it locally with -Q (and with the
lucid flavor) too.

Thomas Lundqvist  writes:

> Package: emacs-gtk
> Version: 1:27.1+1-3.1
> Severity: normal
>
> Dear Maintainer,
>
> My emacs get stuck with 100% cpu when started from a directory ending with
> ".tar".
>
> For example, the following commands trigger the error:
> - mkdir test.tar
> - cd test.tar
> - emacs


-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

Bug#988558: leds-alix: diff for NMU version 0.0.1-1.3

[Ben Hutchings]

Control: tags 988558 + pending

Dear maintainer,

I've prepared an NMU for leds-alix (versioned as 0.0.1-1.3) and
uploaded it.

Ben.

-- 
Ben Hutchings
Never attribute to conspiracy what can adequately be explained
by stupidity.
diff -u leds-alix-0.0.1/debian/changelog leds-alix-0.0.1/debian/changelog
--- leds-alix-0.0.1/debian/changelog
+++ leds-alix-0.0.1/debian/changelog
@@ -1,3 +1,10 @@
+leds-alix (0.0.1-1.3) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * Fix build after removal of SUBDIRS support in Linux 5.3 (Closes: #988558)
+
+ -- Ben Hutchings   Mon, 17 May 2021 00:42:59 +0200
+
 leds-alix (0.0.1-1.2) unstable; urgency=medium
 
   * Non maintainer upload by the Reproducible Builds team.
only in patch2:
unchanged:
--- leds-alix-0.0.1.orig/Makefile
+++ leds-alix-0.0.1/Makefile
@@ -19,10 +19,10 @@
 all: $(MODULE)
 
 $(MODULE): $(SOURCE)
-	$(MAKE) -C $(KERNEL_DIR) SUBDIRS=$(PWD) modules
+	$(MAKE) -C $(KERNEL_DIR) M=$(PWD) modules
 
 install: $(MODULE)
-	$(MAKE) -C $(KERNEL_DIR) SUBDIRS=$(PWD) INSTALL_MOD_DIR=$(INSTALL_MOD_DIR) modules_install
+	$(MAKE) -C $(KERNEL_DIR) M=$(PWD) INSTALL_MOD_DIR=$(INSTALL_MOD_DIR) modules_install
 	depmod -ae
 
 uninstall:


signature.asc
Description: PGP signature

Bug#988626: vpb-driver: diff for NMU version 4.2.61-1.2

[Ben Hutchings]

Package: vpb-driver
Version: 4.2.61-1.1
Severity: normal
Tags: patch  pending

Dear maintainer,

I've prepared an NMU for vpb-driver (versioned as 4.2.61-1.2) and
uploaded it.

Ben.

-- 
Ben Hutchings
Never attribute to conspiracy what can adequately be explained
by stupidity.
diff -u vpb-driver-4.2.61/debian/changelog vpb-driver-4.2.61/debian/changelog
--- vpb-driver-4.2.61/debian/changelog
+++ vpb-driver-4.2.61/debian/changelog
@@ -1,3 +1,15 @@
+vpb-driver (4.2.61-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * Use struct proc_ops for proc file operations on Linux 5.6+
+(Closes: #988564)
+  * Use ioremap() instead of (formerly equivalent, now removed)
+ioremap_nocache()
+  * Pass target kernel version to depmod (Closes: #917865)
+  * Only run depmod or modprobe if installing modules to host filesystem
+
+ -- Ben Hutchings   Mon, 17 May 2021 00:36:41 +0200
+
 vpb-driver (4.2.61-1.1) unstable; urgency=medium
 
   * Non maintainer upload by the Reproducible Builds team.
only in patch2:
unchanged:
--- vpb-driver-4.2.61.orig/src/vpb/Makefile
+++ vpb-driver-4.2.61/src/vpb/Makefile
@@ -46,7 +46,9 @@
 		echo "installing $$m --> $(MODULEDIR)";	\
 		install -m 644 $$m $(MODULEDIR);	\
 	done
-	/sbin/depmod
+ifeq ($(DESTDIR),)
+	/sbin/depmod $(KVERS)
+endif
 
 clean distclean:
 	$(RM) *.o *.ko *~ core *.mod.c .*.cmd
only in patch2:
unchanged:
--- vpb-driver-4.2.61.orig/src/vpb/vpb.c
+++ vpb-driver-4.2.61/src/vpb/vpb.c
@@ -279,7 +279,7 @@
 			printk(KERN_INFO NAME ": tmp [0x%lx] dev->res2 [0x%lx]\n",
   tmp, (unsigned long)dev->resource[2].start);
 
-base2[numPCI] = ioremap_nocache(dev->resource[2].start &
+base2[numPCI] = ioremap(dev->resource[2].start &
 PCI_BASE_ADDRESS_MEM_MASK,
 sizeof(short)*SIZE_WD);
 
only in patch2:
unchanged:
--- vpb-driver-4.2.61.orig/src/vtcore/Makefile
+++ vpb-driver-4.2.61/src/vtcore/Makefile
@@ -50,8 +50,10 @@
 		echo "installing $$m --> $(MODULEDIR)";	\
 		install -m 644 $$m $(MODULEDIR);	\
 	done
-	/sbin/depmod
+ifeq ($(DESTDIR),)
+	/sbin/depmod $(KVERS)
 	@modprobe -r netjet > /dev/null 2>&1 || true
+endif
 
 clean distclean:
 	rm -f *.o *.ko *~ core *.mod.c .*.cmd
only in patch2:
unchanged:
--- vpb-driver-4.2.61.orig/src/vtcore/vtcore_main.c
+++ vpb-driver-4.2.61/src/vtcore/vtcore_main.c
@@ -213,6 +213,34 @@
 	}
 } //}}}
 
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(5,6,0)
+#define VT_DEFINE_PROC_OPS(storage, name, _owner, _open, _write)	\
+storage const struct proc_ops name = {	\
+	.proc_open	= _open,	\
+	.proc_read	= seq_read,	\
+	.proc_lseek	= seq_lseek,	\
+	.proc_release	= single_release,\
+	.proc_write	= _write,	\
+}
+#else  /* LINUX_VERSION_CODE < KERNEL_VERSION(5,6,0) */
+#define VT_DEFINE_PROC_OPS(storage, name, _owner, _open, _write)	\
+storage const struct file_operations name = {\
+	.owner		= _owner,	\
+	.open		= _open,	\
+	.read		= seq_read,	\
+	.llseek		= seq_lseek,	\
+	.release	= single_release,\
+	.write		= _write,	\
+}
+#endif
+
+#define VT_DEFINE_PROC_OPS_OPEN(storage, name)\
+	VT_DEFINE_PROC_OPS(storage, name ## _proc_fops, NULL,		\
+			   name ## _proc_open, NULL)
+
+#define VT_DEFINE_PROC_OPS_OPEN_WRITE(storage, name)			\
+	VT_DEFINE_PROC_OPS(storage, name ## _proc_fops, THIS_MODULE,	\
+			   name ## _proc_open, name ## _proc_write)
 
 static int vt_int_proc_show(struct seq_file *m, void *v)
 { //{{{
@@ -225,12 +253,8 @@
 	return single_open(file, vt_int_proc_show, PDE_DATA(inode));
 }
 
-const struct file_operations vt_int_proc_fops = {
-	.open		= vt_int_proc_open,
-	.read		= seq_read,
-	.llseek		= seq_lseek,
-	.release	= single_release,
-}; //}}}
+VT_DEFINE_PROC_OPS_OPEN(, vt_int);
+//}}}
 
 static int vt_string_proc_show(struct seq_file *m, void *v)
 { //{{{
@@ -243,12 +267,8 @@
 	return single_open(file, vt_string_proc_show, PDE_DATA(inode));
 }
 
-const struct file_operations vt_string_proc_fops = {
-	.open		= vt_string_proc_open,
-	.read		= seq_read,
-	.llseek		= seq_lseek,
-	.release	= single_release,
-}; //}}}
+VT_DEFINE_PROC_OPS_OPEN(, vt_string);
+//}}}
 
 
 int __init vtcore_init(void)
@@ -1081,14 +1101,8 @@
 	return ret;
 }
 
-static const struct file_operations vt_country_proc_fops = {
-	.owner		= THIS_MODULE,
-	.open		= vt_country_proc_open,
-	.read		= seq_read,
-	.llseek		= seq_lseek,
-	.release	= single_release,
-	.write		= vt_country_proc_write,
-}; //}}}
+VT_DEFINE_PROC_OPS_OPEN_WRITE(static, vt_country);
+//}}}
 
 // Template definitions for port ops that communicate a single integer value.
 // {{{
@@ -1161,25 +1175,13 @@
 #define PROC_READ_PORT(attrib)			\
 	PROC_READ_PORT_(attrib)			\
 		\
-static const struct file_operations vt_##attrib##_proc_fops = {			\
-	.open		= vt_##attrib##_proc_open,\
-	.read		= seq_read,		\
-	.llseek		= seq_lseek,		\
-	

Bug#988625: unblock: kodi-vfs-libarchive/2.0.1+ds1-1

[vasek . gello]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: mat...@debian.org

Please unblock package kodi-vfs-libarchive

[ Reason ]

The bugfix point release companion to Kodi 19.1 and
linked against its API provides.

[ Impact ]

Every point release brings several dozen bugfixes.
No new functionality is added or breaking changes allowed.

[ Tests ]

Automated tests + manual testing by Kodi users

[ Risks ]

The struct release policy of upstream ensures no breaking
changes are allowed past BETA releases. Point releases
bring only bugfixes and security fixes.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

[ Other info ]

unblock kodi-vfs-libarchive/2.0.1+ds1-1


kodi-vfs-libarchive_2.0.0+ds1-2_2.0.1+ds1-1.debdiff
Description: kodi-vfs-libarchive_2.0.0+ds1-2_2.0.1+ds1-1.debdiff

Bug#988624: unblock: kodi-pvr-zattoo/19.7.9+ds1-1

[vasek . gello]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: mat...@debian.org

Please unblock package kodi-pvr-zattoo

[ Reason ]

The bugfix point release companion to Kodi 19.1 and
linked against its API provides.

[ Impact ]

Every point release brings several dozen bugfixes.
No new functionality is added or breaking changes allowed.

[ Tests ]

Automated tests + manual testing by Kodi users

[ Risks ]

The struct release policy of upstream ensures no breaking
changes are allowed past BETA releases. Point releases
bring only bugfixes and security fixes.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

[ Other info ]

unblock kodi-pvr-zattoo/19.7.9+ds1-1


kodi-pvr-zattoo_19.7.3+ds1-1_19.7.9+ds1-1.debdiff
Description: kodi-pvr-zattoo_19.7.3+ds1-1_19.7.9+ds1-1.debdiff

Bug#988623: unblock: kodi-pvr-waipu/2.8.4+ds1-1

[vasek . gello]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: mat...@debian.org

Please unblock package kodi-pvr-waipu

[ Reason ]

The bugfix point release companion to Kodi 19.1 and
linked against its API provides.

[ Impact ]

Every point release brings several dozen bugfixes.
No new functionality is added or breaking changes allowed.

[ Tests ]

Automated tests + manual testing by Kodi users

[ Risks ]

The struct release policy of upstream ensures no breaking
changes are allowed past BETA releases. Point releases
bring only bugfixes and security fixes.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

[ Other info ]

unblock kodi-pvr-waipu/2.8.4+ds1-1


kodi-pvr-waipu_2.6.1+ds1-1_2.8.4+ds1-1.debdiff
Description: kodi-pvr-waipu_2.6.1+ds1-1_2.8.4+ds1-1.debdiff

Bug#988622: unblock: kodi-pvr-vuplus/7.4.3+ds1-1

[vasek . gello]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: mat...@debian.org

Please unblock package kodi-pvr-vuplus

[ Reason ]

The bugfix point release companion to Kodi 19.1 and
linked against its API provides.

[ Impact ]

Every point release brings several dozen bugfixes.
No new functionality is added or breaking changes allowed.

[ Tests ]

Automated tests + manual testing by Kodi users

[ Risks ]

The struct release policy of upstream ensures no breaking
changes are allowed past BETA releases. Point releases
bring only bugfixes and security fixes.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

[ Other info ]

unblock kodi-pvr-vuplus/7.4.3+ds1-1


kodi-pvr-vuplus_7.4.0+ds1-1_7.4.3+ds1-1.debdiff
Description: kodi-pvr-vuplus_7.4.0+ds1-1_7.4.3+ds1-1.debdiff

Bug#988621: unblock: kodi-pvr-nextpvr/8.2.3+ds1-1

[vasek . gello]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: mat...@debian.org

Please unblock package kodi-pvr-nextpvr

[ Reason ]

The bugfix point release companion to Kodi 19.1 and
linked against its API provides.

[ Impact ]

Every point release brings several dozen bugfixes.
No new functionality is added or breaking changes allowed.

[ Tests ]

Automated tests + manual testing by Kodi users

[ Risks ]

The struct release policy of upstream ensures no breaking
changes are allowed past BETA releases. Point releases
bring only bugfixes and security fixes.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

[ Other info ]

unblock kodi-pvr-nextpvr/8.2.3+ds1-1


kodi-pvr-nextpvr_8.2.1+ds1-1_8.2.3+ds1-1.debdiff
Description: kodi-pvr-nextpvr_8.2.1+ds1-1_8.2.3+ds1-1.debdiff

Bug#988620: unblock: kodi-pvr-mediaportal-tvserver/8.1.2+ds1-1

[vasek . gello]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: mat...@debian.org

Please unblock package kodi-pvr-mediaportal-tvserver

[ Reason ]

The bugfix point release companion to Kodi 19.1 and
linked against its API provides.

[ Impact ]

Every point release brings several dozen bugfixes.
No new functionality is added or breaking changes allowed.

[ Tests ]

Automated tests + manual testing by Kodi users

[ Risks ]

The struct release policy of upstream ensures no breaking
changes are allowed past BETA releases. Point releases
bring only bugfixes and security fixes.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

[ Other info ]

unblock kodi-pvr-mediaportal-tvserver/8.1.2+ds1-1


kodi-pvr-mediaportal-tvserver_8.1.0+ds1-1_8.1.2+ds1-1.debdiff
Description: kodi-pvr-mediaportal-tvserver_8.1.0+ds1-1_8.1.2+ds1-1.debdiff

Bug#988619: unblock: kodi-pvr-mythtv/7.3.1+ds1-1

[vasek . gello]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: mat...@debian.org

Please unblock package kodi-pvr-mythtv

[ Reason ]

The bugfix point release companion to Kodi 19.1 and
linked against its API provides.

[ Impact ]

Every point release brings several dozen bugfixes.
No new functionality is added or breaking changes allowed.

[ Tests ]

Automated tests + manual testing by Kodi users

[ Risks ]

The struct release policy of upstream ensures no breaking
changes are allowed past BETA releases. Point releases
bring only bugfixes and security fixes.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

[ Other info ]

unblock kodi-pvr-mythtv/7.3.1+ds1-1


kodi-pvr-mythtv_7.3.0+ds1-1_7.3.1+ds1-1.debdiff
Description: kodi-pvr-mythtv_7.3.0+ds1-1_7.3.1+ds1-1.debdiff

Bug#988618: unblock: kodi-pvr-iptvsimple/7.6.5+ds1-1

[vasek . gello]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: mat...@debian.org

Please unblock package kodi-pvr-iptvsimple

[ Reason ]

The bugfix point release companion to Kodi 19.1 and
linked against its API provides.

[ Impact ]

Every point release brings several dozen bugfixes.
No new functionality is added or breaking changes allowed.

[ Tests ]

Automated tests + manual testing by Kodi users

[ Risks ]

The struct release policy of upstream ensures no breaking
changes are allowed past BETA releases. Point releases
bring only bugfixes and security fixes.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

[ Other info ]

unblock kodi-pvr-iptvsimple/7.6.5+ds1-1


kodi-pvr-iptvsimple_7.4.3+ds1-1_7.6.5+ds1-1.debdiff
Description: kodi-pvr-iptvsimple_7.4.3+ds1-1_7.6.5+ds1-1.debdiff

Bug#988617: unblock: kodi-pvr-hts/8.3.0+ds1-1

[vasek . gello]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: mat...@debian.org

Please unblock package kodi-pvr-hts

[ Reason ]

The bugfix point release companion to Kodi 19.1 and
linked against its API provides.

[ Impact ]

Every point release brings several dozen bugfixes.
No new functionality is added or breaking changes allowed.

[ Tests ]

Automated tests + manual testing by Kodi users

[ Risks ]

The struct release policy of upstream ensures no breaking
changes are allowed past BETA releases. Point releases
bring only bugfixes and security fixes.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

[ Other info ]

unblock kodi-pvr-hts/8.3.0+ds1-1


kodi-pvr-hts_8.2.2+ds1-1_8.3.0+ds1-1.debdiff
Description: kodi-pvr-hts_8.2.2+ds1-1_8.3.0+ds1-1.debdiff

Bug#988616: unblock: kodi-inputstream-ffmpegdirect/1.21.3+ds1-1

[vasek . gello]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: mat...@debian.org

Please unblock package kodi-inputstream-ffmpegdirect

[ Reason ]

The bugfix point release companion to Kodi 19.1 and
linked against its API provides.

[ Impact ]

Every point release brings several dozen bugfixes.
No new functionality is added or breaking changes allowed.

[ Tests ]

Automated tests + manual testing by Kodi users

[ Risks ]

The struct release policy of upstream ensures no breaking
changes are allowed past BETA releases. Point releases
bring only bugfixes and security fixes.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

[ Other info ]

unblock kodi-inputstream-ffmpegdirect/1.21.3+ds1-1


kodi-inputstream-ffmpegdirect_1.19.2+ds1-1_1.21.3+ds1-1.debdiff
Description: kodi-inputstream-ffmpegdirect_1.19.2+ds1-1_1.21.3+ds1-1.debdiff

Bug#988614: unblock: kodi-imagedecoder-heif/1.4.0+ds1-1

[vasek . gello]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: mat...@debian.org

Please unblock package kodi-imagedecoder-heif

[ Reason ]

The bugfix point release companion to Kodi 19.1 and
linked against its API provides.

[ Impact ]

Every point release brings several dozen bugfixes.
No new functionality is added or breaking changes allowed.

[ Tests ]

Automated tests + manual testing by Kodi users

[ Risks ]

The struct release policy of upstream ensures no breaking
changes are allowed past BETA releases. Point releases
bring only bugfixes and security fixes.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

[ Other info ]

unblock kodi-imagedecoder-heif/1.4.0+ds1-1


kodi-imagedecoder-heif_1.3.0+ds1-2_1.4.0+ds1-1.debdiff
Description: kodi-imagedecoder-heif_1.3.0+ds1-2_1.4.0+ds1-1.debdiff

Bug#988613: gnumeric: SIGSEGV, Segmentation fault from /usr/lib/goffice/0.10.44/plugins/plot_surface/surface.so

[Kingsley G. Morse Jr.]

Package: gnumeric
Version: 1.12.44-1
Severity: normal

Dear Dmitry,

Thanks again for maintaining the very cool and
useful gnumeric package for Debian's epic
distribution.

   * What led up to the situation?

 A head wind of bugs mightier than a biblical
 plague of locust swarming through a computer
 buggier than Maine in June.

 corrupted_workbook.gnumeric is a Gnumeric
 workbook with many sheets, one of which is
 corrupted. 

 Where once a mighty sheet was filled with
 data, now only 

comments,

empty charts and

the last number entered

 remain!


   * What exactly did you do (or not do) that was effective (or
 ineffective)?

 Typing this at the command line

$ gnumeric corrupted_workbook.gnumeric


   * What was the outcome of this action?

An almighty "Segmentation fault".

 Here's the back trace from gdb:

Starting program: /usr/bin/gnumeric 
Using host libthread_db library 
"/lib/x86_64-linux-gnu/libthread_db.so.1".
Thread 1 "gnumeric" received signal SIGSEGV, Segmentation fault.
0x70056339 in ?? () from 
/usr/lib/goffice/0.10.44/plugins/plot_surface/surface.so
#0  0x70056339 in ?? () from 
/usr/lib/goffice/0.10.44/plugins/plot_surface/surface.so
#1  0x76fdaac4 in ?? () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x76fda8b4 in ?? () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x76fda8a6 in ?? () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x76fda8a6 in ?? () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x76fda8a6 in ?? () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x76fda8a6 in ?? () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x76fda8a6 in ?? () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x76fda8a6 in ?? () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x76fda8a6 in ?? () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x76fda8a6 in ?? () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x76fda8a6 in ?? () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x76fdad2f in ?? () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#13 0x7005786f in ?? () from 
/usr/lib/goffice/0.10.44/plugins/plot_surface/surface.so
#14 0x70056cb4 in ?? () from 
/usr/lib/goffice/0.10.44/plugins/plot_surface/surface.so
#15 0x77957314 in gog_object_update () from 
/lib/libgoffice-0.10.so.10
#16 0x779572b4 in gog_object_update () from 
/lib/libgoffice-0.10.so.10
#17 0x779572b4 in gog_object_update () from 
/lib/libgoffice-0.10.so.10
#18 0x77960387 in gog_graph_force_update () from 
/lib/libgoffice-0.10.so.10
#19 0x77c28ab0 in workbook_update_graphs () from 
/lib/libspreadsheet-1.12.44.so
#20 0x77c27104 in workbook_view_new_from_input () from 
/lib/libspreadsheet-1.12.44.so
#21 0x77c2734d in workbook_view_new_from_uri () from 
/lib/libspreadsheet-1.12.44.so
#22 0x77b73cba in gui_file_read () from 
/lib/libspreadsheet-1.12.44.so
#23 0x77b746ae in gui_file_open () from 
/lib/libspreadsheet-1.12.44.so
#24 0x770acc8d in g_closure_invoke () from 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#25 0x770c0365 in ?? () from 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#26 0x770c92be in g_signal_emit_valist () from 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#27 0x770c997f in g_signal_emit () from 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#28 0x7729a7e0 in ?? () from 
/lib/x86_64-linux-gnu/libgtk-3.so.0
#29 0x770acec6 in ?? () from 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#30 0x770c938d in g_signal_emit_valist () from 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#31 0x770c997f in g_signal_emit () from 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#32 0x7756888a in gtk_widget_activate () from 
/lib/x86_64-linux-gnu/libgtk-3.so.0
#33 0x7743ba86 in gtk_menu_shell_activate_item () from 
/lib/x86_64-linux-gnu/libgtk-3.so.0
#34 0x7743bd23 in ?? () from 
/lib/x86_64-linux-gnu/libgtk-3.so.0
#35 0x775b8274 in ?? () from 
/lib/x86_64-linux-gnu/libgtk-3.so.0
#36 0x770acec6 in ?? () from 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#37 0x770c8d74 in g_signal_emit_valist () from 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#38 0x770c997f in g_signal_emit () from 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#39 

Bug#987537: RM: scrollz -- RoQA unmaintained, dead upstream, has security issues

[Mike Markley]

On Mon, May 03, 2021 at 07:58:06AM +0200, Tobias Frost  wrote:
> I just gave upstream a pointer to the ircii code that fixes this CVE. Maybe
> they have tested it?

I reached out via email yesterday and I'm awaiting a response.

> (MIA Team hat partly on) That sounds a bit like the package should be
> orphaned or some RFH/RFA bug being filed? Or join efforts in some team?
> As said, you can use mentors.debian.net for uploading. The only hard
> point I can't give you advice is the time issue…

Well, there was a time issue and a potential employer issue (and I can't
expect advice from you on either :). I've spoken with my employer and
confirmed that there actually isn't an issue there.

> But maybe you'll find a bit of time working to update your package;
> But note, we are currently frozen, uploads to unstable should be
> minimal and targeted fixes only…

Understood; I've updated the 2.2.3-1 package from the PR and from a small
patch upstream made to that, and, as noted above, just want to make sure
it's tested before bugging mentors.debian.net for assistance uploading.
(I'm still unclear on if the package version should be updated to indicate
that this is a security fix, but that's obviously a very small detail
overall that can be dealt with at any point before upload.)

On Thu, May 13, 2021 at 02:10:05PM +0300, Adrian Bunk  wrote:
> https://security-tracker.debian.org/tracker/CVE-2021-29376
> [buster] - scrollz  (Minor issue)
> 
> So the correct instructions are in this case
> https://www.debian.org/doc/manuals/developers-reference/pkgs.html#special-case-uploads-to-the-stable-and-oldstable-distributions

I can build/test on a stable and an oldstable system, but per those
instructions, I'll first focus on getting a 2.2.3-2 uploaded to unstable
that contains just the fix that would then go into 2.2.3-1+deb10u1 (and
potentially 2.2.3-1+deb9u1, if that even makes sense timing-wise anymore).

Given the existence of a CVE and a security-tracker entry, what is the
appropriate urgency for these uploads? (I'm happy to reach out to the team
if that's more appropriate.)

-- 
Mike Markley 

Bug#988612: unblock: freerdp2/2.3.0+dfsg1-2

[Mike Gabriel]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package freerdp2

This upload brings various stability improvements cherry-picked from
upstream (and discussed with upstream).

  * debian/watch:
+ Fix Github watch URL.

-> Enables watching of new upstream releases again.

  * debian/patches:
+ Backport changes from 2.3.2 (bound checks, API compat fixes, Smartcard
  issues fixes, etc.).
  - 0001-Added-compatibility-define.patch
  - 0003-Reverted-connectErrorCode-removal.patch
  - 0004-Fixed-a-leak-on-mouse-cursor-updates.patch
  - 0007-Fixed-format-string-in-smartcard_trace_state_return.patch
  - 0008-Fixed-linking-dependencies-for-client-geometry-chann.patch
  - 0010-Fixed-smartcard_convert_string_list-with-0-length.patch
  - 0012-Parse-on-a-copy-of-the-argument-string-for-printer.patch
  - 0015-Fix-xf_Pointer_SetPosition-with-smart-sizing.patch
  - 0017-Backported-6865-Disable-websockets-command-line-opti.patch
  - 0019-Check-smartcard_convert_string_list-for-NULL-string.patch
  - 0020-Use-specific-names-for-drive-hotplug-special-values.patch
  - 0021-Filter-RDPDR-types-other-than-drives-on-windows-hotp.patch
  - 0023-use-tlsOut-BIO-when-using-websocket-in-rdg_bio_ctrl.patch
  - 0024-Added-bounds-checks-to-gfx-commands.patch
  - 0025-Added-bounds-check-in-rdpgfx_recv_wire_to_surface_1_.patch
  - 0026-Added-fuzzying-test-for-planar-decoder.patch
  - 0027-Added-missing-bounds-check.patch
  - 0028-Fixed-mac-issues-with-smartcard-context-cleanup-6890.patch
  - 0031-Fix-monitor-list.patch
  - 0032-Fixed-CodeQL-warnings.patch
  - 0033-Reverted-winpr_BinToHexString-argument-change.patch

-> Dearly recommended changes by FreeRDP upstream. Various bounds checks, 
memleaks, etc.

  * debian/patches:
+ Add 0034-Fixed-6938-Remote-app-mode-clipboard-fix.patch. In remote app
  mode the _FREERDP_TIMESTAMP_PROPERTY does not work. Therefore ignore it.
+ Add 0035-Fixed-6989-Use-X509_STORE_set_default_paths.patch. Fix Windows
  10 logon when using an internal trusted root CA.

-> Two upcoming upstream stable backports (pending for FreeRDP 2.3.3).
For production setups both are a must have.

[ Reason ]
The changeset provides more stability to the FreeRDP binaries and
libraries. Clipboard in seamless RDP application are fixed, Windows
logon in corporate environments are fixes by this version.

[ Impact ]
Users of FreeRDP would be recommended to switch over to FreeRDP from
bullseye-backports (once they are available).

[ Tests ]
Manual tests against Windows 2012 Server, Windows 10 VM and Windows 2016 Server.

[ Risks ]
The chanages have also been tested with xRDP. The xRDP Server behaves well with 
these
changes installed on the server, also logons against xRDP work ok.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

[ Other info ]
The changeset has been discussed with and approved by upstream FreeRPD
developers Bernhard Miklautz and  akallabeth (IRC nick, real name not
known).

unblock freerdp2/2.3.0+dfsg1-2
diff -Nru freerdp2-2.3.0+dfsg1/debian/changelog 
freerdp2-2.3.0+dfsg1/debian/changelog
--- freerdp2-2.3.0+dfsg1/debian/changelog   2021-02-25 16:14:52.0 
+0100
+++ freerdp2-2.3.0+dfsg1/debian/changelog   2021-05-16 23:42:19.0 
+0200
@@ -1,3 +1,39 @@
+freerdp2 (2.3.0+dfsg1-2) unstable; urgency=medium
+
+  * debian/watch:
++ Fix Github watch URL.
+  * debian/patches:
++ Backport changes from 2.3.2 (bound checks, API compat fixes, Smartcard
+  issues fixes, etc.).
+  - 0001-Added-compatibility-define.patch
+  - 0003-Reverted-connectErrorCode-removal.patch
+  - 0004-Fixed-a-leak-on-mouse-cursor-updates.patch
+  - 0007-Fixed-format-string-in-smartcard_trace_state_return.patch
+  - 0008-Fixed-linking-dependencies-for-client-geometry-chann.patch
+  - 0010-Fixed-smartcard_convert_string_list-with-0-length.patch
+  - 0012-Parse-on-a-copy-of-the-argument-string-for-printer.patch
+  - 0015-Fix-xf_Pointer_SetPosition-with-smart-sizing.patch
+  - 0017-Backported-6865-Disable-websockets-command-line-opti.patch
+  - 0019-Check-smartcard_convert_string_list-for-NULL-string.patch
+  - 0020-Use-specific-names-for-drive-hotplug-special-values.patch
+  - 0021-Filter-RDPDR-types-other-than-drives-on-windows-hotp.patch
+  - 0023-use-tlsOut-BIO-when-using-websocket-in-rdg_bio_ctrl.patch
+  - 0024-Added-bounds-checks-to-gfx-commands.patch
+  - 0025-Added-bounds-check-in-rdpgfx_recv_wire_to_surface_1_.patch
+  - 0026-Added-fuzzying-test-for-planar-decoder.patch
+  - 0027-Added-missing-bounds-check.patch
+  - 0028-Fixed-mac-issues-with-smartcard-context-cleanup-6890.patch
+  - 0031-Fix-monitor-list.patch
+  - 

Bug#988610: unblock: libwebm/1.0.0.28-1

[Vasyl Gello]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: mat...@debian.org

Please unblock package libwebm

[ Reason ]

This is a bigfix release fixing several buffer overflows, finally
tagged after 5 years of upstream marinade.

[ Impact ]

Several flaws with security vulnerability potential will not be
addressed. However, no CVEs allocated to the date.

[ Tests ]

Automatic testsuite + mwnual checks by Kodi users (including myself)

[ Risks ]

This package is used primarily by kodi-inputstream-adaptive, so risk
is low.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

[ Other info ]

unblock libwebm/1.0.0.28-1
diff -Nru libwebm-1.0.0.27+git20201124.485fb67/build/cxx_flags.cmake 
libwebm-1.0.0.28/build/cxx_flags.cmake
--- libwebm-1.0.0.27+git20201124.485fb67/build/cxx_flags.cmake  2020-11-24 
23:40:20.0 +
+++ libwebm-1.0.0.28/build/cxx_flags.cmake  2021-04-23 23:34:08.0 
+
@@ -5,7 +5,6 @@
 ##  tree. An additional intellectual property rights grant can be found
 ##  in the file PATENTS.  All contributing project authors may
 ##  be found in the AUTHORS file in the root of the source tree.
-cmake_minimum_required(VERSION 3.2)
 
 include(CheckCXXCompilerFlag)
 
diff -Nru libwebm-1.0.0.27+git20201124.485fb67/build/msvc_runtime.cmake 
libwebm-1.0.0.28/build/msvc_runtime.cmake
--- libwebm-1.0.0.27+git20201124.485fb67/build/msvc_runtime.cmake   
2020-11-24 23:40:20.0 +
+++ libwebm-1.0.0.28/build/msvc_runtime.cmake   2021-04-23 23:34:08.0 
+
@@ -5,7 +5,6 @@
 ##  tree. An additional intellectual property rights grant can be found
 ##  in the file PATENTS.  All contributing project authors may
 ##  be found in the AUTHORS file in the root of the source tree.
-cmake_minimum_required(VERSION 2.8)
 
 if (MSVC)
   # CMake defaults to producing code linked to the DLL MSVC runtime. In libwebm
diff -Nru libwebm-1.0.0.27+git20201124.485fb67/CMakeLists.txt 
libwebm-1.0.0.28/CMakeLists.txt
--- libwebm-1.0.0.27+git20201124.485fb67/CMakeLists.txt 2020-11-24 
23:40:20.0 +
+++ libwebm-1.0.0.28/CMakeLists.txt 2021-04-23 23:34:08.0 +
@@ -25,7 +25,8 @@
 option(ENABLE_WERROR "Enable warnings as errors." OFF)
 option(ENABLE_WEBM_PARSER "Enables new parser API." OFF)
 
-if(WIN32)
+if(WIN32 OR CYGWIN OR MSYS)
+  # Allow use of rand_r() / fdopen() and other POSIX functions.
   require_cxx_flag_nomsvc("-std=gnu++11")
 else()
   require_cxx_flag_nomsvc("-std=c++11")
diff -Nru libwebm-1.0.0.27+git20201124.485fb67/CONTRIBUTING.md 
libwebm-1.0.0.28/CONTRIBUTING.md
--- libwebm-1.0.0.27+git20201124.485fb67/CONTRIBUTING.md1970-01-01 
00:00:00.0 +
+++ libwebm-1.0.0.28/CONTRIBUTING.md2021-04-23 23:34:08.0 +
@@ -0,0 +1,29 @@
+# How to Contribute
+
+We'd love to accept your patches and contributions to this project. There are
+just a few small guidelines you need to follow.
+
+## Contributor License Agreement
+
+Contributions to this project must be accompanied by a Contributor License
+Agreement. You (or your employer) retain the copyright to your contribution;
+this simply gives us permission to use and redistribute your contributions as
+part of the project. Head over to  to see
+your current agreements on file or to sign a new one.
+
+You generally only need to submit a CLA once, so if you've already submitted 
one
+(even if it was for a different project), you probably don't need to do it
+again.
+
+## Code reviews
+
+All submissions, including submissions by project members, require review. We
+use a [Gerrit](https://www.gerritcodereview.com) instance hosted at
+https://chromium-review.googlesource.com for this purpose. See the
+[WebM Project 
page](https://www.webmproject.org/code/contribute/submitting-patches/)
+for additional details.
+
+## Community Guidelines
+
+This project follows
+[Google's Open Source Community 
Guidelines](https://opensource.google.com/conduct/).
diff -Nru libwebm-1.0.0.27+git20201124.485fb67/debian/changelog 
libwebm-1.0.0.28/debian/changelog
--- libwebm-1.0.0.27+git20201124.485fb67/debian/changelog   2021-01-21 
20:25:40.0 +
+++ libwebm-1.0.0.28/debian/changelog   2021-05-08 21:47:39.0 +
@@ -1,3 +1,11 @@
+libwebm (1.0.0.28-1) unstable; urgency=medium
+
+  * New upstream version 1.0.0.28
+  * Switch to git tags in d/watch
+  * Bump library version in patch
+
+ -- Vasyl Gello   Sat, 08 May 2021 21:47:39 +
+
 libwebm (1.0.0.27+git20201124.485fb67-2) unstable; urgency=medium
 
   * Remove duplicated inclusion of -lpthread and -latomic
diff -Nru 
libwebm-1.0.0.27+git20201124.485fb67/debian/patches/0003-Provide-SOVERSION.patch
 libwebm-1.0.0.28/debian/patches/0003-Provide-SOVERSION.patch
--- 

Bug#988609: unblock: vinagre/3.22.0-8.1

[Mike Gabriel]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: Simon McVittie 

Please unblock package vinagre

[ Reason ]
Resolves hanging black screen when connecting to an RDP server.

[ Impact ] Users of vinagre from buster will not be able to use the
application anymore. The vinagre package should then be removed from
bullseye.

[ Tests ]
Manually tested against a Windows 2016 Server OS.

[ Risks ]
Leaf package, no risk.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

[ Other info ]
None

unblock vinagre/3.22.0-8.1
diff -Nru vinagre-3.22.0/debian/changelog vinagre-3.22.0/debian/changelog
--- vinagre-3.22.0/debian/changelog 2021-01-01 01:09:52.0 +0100
+++ vinagre-3.22.0/debian/changelog 2021-05-16 23:11:19.0 +0200
@@ -1,3 +1,14 @@
+vinagre (3.22.0-8.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/patches:
++ Add 0003-fix-hangs-with-recent-FreeRDP-version.patch and
+  0004-fix-FreeRDP-API-usage.patch. This resolves vinagre hanging endlessly
+  with a black screen when connecting to a remote RDP server (Closes:
+  #983533).
+
+ -- Mike Gabriel   Sun, 16 May 2021 23:11:19 +0200
+
 vinagre (3.22.0-8) unstable; urgency=medium
 
   * Team upload.
diff -Nru 
vinagre-3.22.0/debian/patches/0003-fix-hangs-with-recent-FreeRDP-version.patch 
vinagre-3.22.0/debian/patches/0003-fix-hangs-with-recent-FreeRDP-version.patch
--- 
vinagre-3.22.0/debian/patches/0003-fix-hangs-with-recent-FreeRDP-version.patch  
1970-01-01 01:00:00.0 +0100
+++ 
vinagre-3.22.0/debian/patches/0003-fix-hangs-with-recent-FreeRDP-version.patch  
2021-02-26 10:32:02.0 +0100
@@ -0,0 +1,78 @@
+From 404a56a11469ef24a1df632847465030d81db091 Mon Sep 17 00:00:00 2001
+From: Ondrej Holy 
+Date: Fri, 15 May 2020 15:43:37 +0200
+Subject: [PATCH] plugins/rdp: Fix hangs with recent FreeRDP versions
+
+Connection to all my testing servers fails with "SERVER BUG: The support
+for this feature was not announced! Use /relax-order-checks to ignore"
+currently. This happens always with current FreeRDP versions after
+https://github.com/FreeRDP/FreeRDP/pull/4926 has been merged. This can be
+fixed by the usage of /relax-order-checks option, however, this option
+should be used only if necessary needed and it should not be needed in
+most of the cases. This currenlty happens always as it interfere with our
+custom OrderSupports settings. Let's use the default OrderSupports
+settings to fix this issue, which is possible thanks to
+https://github.com/FreeRDP/FreeRDP/pull/5057.
+
+See: https://gitlab.gnome.org/GNOME/gtk-frdp/-/issues/27
+---
+ configure.ac  |  2 +-
+ plugins/rdp/vinagre-rdp-tab.c | 27 ---
+ 2 files changed, 1 insertion(+), 28 deletions(-)
+
+--- a/configure.ac
 b/configure.ac
+@@ -58,7 +58,7 @@
+ AM_CONDITIONAL([VINAGRE_ENABLE_SSH], [test "x$have_ssh" = "xyes"])
+ 
+ # Whether to enable support for RDP.
+-RDP_DEPS="freerdp2 x11"
++RDP_DEPS="freerdp2 >= 2.0.0 x11"
+ AC_ARG_ENABLE([rdp],
+   [AS_HELP_STRING([--disable-rdp],
+ [Disable Remote Desktop Protocol (RDP) support])])
+--- a/plugins/rdp/vinagre-rdp-tab.c
 b/plugins/rdp/vinagre-rdp-tab.c
+@@ -524,32 +524,7 @@ frdp_pre_connect (freerdp *instance)
+ {
+   rdpSettings *settings = instance->settings;
+
+-#if HAVE_FREERDP_1_1
+-  settings->OrderSupport[NEG_DSTBLT_INDEX] = TRUE;
+-  settings->OrderSupport[NEG_PATBLT_INDEX] = TRUE;
+-  settings->OrderSupport[NEG_SCRBLT_INDEX] = TRUE;
+-  settings->OrderSupport[NEG_OPAQUE_RECT_INDEX] = TRUE;
+-  settings->OrderSupport[NEG_DRAWNINEGRID_INDEX] = FALSE;
+-  settings->OrderSupport[NEG_MULTIDSTBLT_INDEX] = FALSE;
+-  settings->OrderSupport[NEG_MULTIPATBLT_INDEX] = FALSE;
+-  settings->OrderSupport[NEG_MULTISCRBLT_INDEX] = FALSE;
+-  settings->OrderSupport[NEG_MULTIOPAQUERECT_INDEX] = TRUE;
+-  settings->OrderSupport[NEG_MULTI_DRAWNINEGRID_INDEX] = FALSE;
+-  settings->OrderSupport[NEG_LINETO_INDEX] = TRUE;
+-  settings->OrderSupport[NEG_POLYLINE_INDEX] = TRUE;
+-  settings->OrderSupport[NEG_MEMBLT_INDEX] = TRUE;
+-  settings->OrderSupport[NEG_MEM3BLT_INDEX] = FALSE;
+-  settings->OrderSupport[NEG_MEMBLT_V2_INDEX] = TRUE;
+-  settings->OrderSupport[NEG_MEM3BLT_V2_INDEX] = FALSE;
+-  settings->OrderSupport[NEG_SAVEBITMAP_INDEX] = FALSE;
+-  settings->OrderSupport[NEG_GLYPH_INDEX_INDEX] = TRUE;
+-  settings->OrderSupport[NEG_FAST_INDEX_INDEX] = TRUE;
+-  settings->OrderSupport[NEG_FAST_GLYPH_INDEX] = FALSE;
+-  settings->OrderSupport[NEG_POLYGON_SC_INDEX] = FALSE;
+-  settings->OrderSupport[NEG_POLYGON_CB_INDEX] = FALSE;
+-  settings->OrderSupport[NEG_ELLIPSE_SC_INDEX] = FALSE;
+-  settings->OrderSupport[NEG_ELLIPSE_CB_INDEX] = FALSE;
+-#else
++#if !HAVE_FREERDP_1_1
+   settings->order_support[NEG_DSTBLT_INDEX] = true;
+   

Bug#988474: [Fwd: Bug#988474: RFS: freefem++/3.61.1+dfsg1-5.2 [NMU] [RC] -- Provides the binaries of the FreeFem++ FE suite]

[François Mazen]

Hi Nilesh,

thanks for the pointer to the freeze policy. I understand that it's too
late and I'm closing the unblock request.

Best Regards,
François



Le lundi 17 mai 2021 à 00:30 +0530, Nilesh Patra a écrit :
> Hi,
> 
> On Mon, 17 May 2021 at 00:10, François Mazen  wrote:
> > Hello Anton,
> > 
> > > When the package is successfully built on all relevant platforms,
> > > you can ask the release team to unblock it. But it will unlikely
> > > happen
> > > due to release policy.
> > 
> > I've requested the unblock, see [1]. Let me know if I've missed
> > something.
> 
> As you might see freefem++ is not in testing, and as per the release
> policy[1] the packages not in testing cannot re-enter testing at this
> stage.
> The deadline for such packages to enter testing was Feb 12 and we are
> months away from that date.
> 
> Nevertheless, it can definitely be a part of bookworm and bullseye-
> backports. Thanks a lot for your work on
> freefem++ :-)
> 
> [1]: https://release.debian.org/bullseye/freeze_policy.html#soft
> 
> Nilesh

Bug#988604: plocate: autopkgtest regression: plocate and mlocate can't be co-installed anymore

[Steinar H. Gunderson]

On Sun, May 16, 2021 at 10:46:30PM +0200, Paul Gevers wrote:
>> Thanks for noticing. Given how annoying everything in autopkgtest is,
>> perhaps the easiest thing is just deleting the tests. (1.1.7-3 wouldn't
>> migrate to bullseye, then, but that's fine.)
> As it stands, you'd only need to remove the third test, not all three.

This is true, but the ergonomics of autopkgtest have been a huge
disappointment for me in general (plocate was the first, and so far only,
package I've tried it on), and I'm not convinced they are likely to catch
any real bugs in the package.

/* Steinar */
-- 
Homepage: https://www.sesse.net/

Bug#988604: plocate: autopkgtest regression: plocate and mlocate can't be co-installed anymore

[Paul Gevers]

Hi Steinar,

On 16-05-2021 21:41, Steinar H. Gunderson wrote:
> On Sun, May 16, 2021 at 09:17:57PM +0200, Paul Gevers wrote:
>> With a recent upload of plocate the autopkgtest of plocate fails in
>> testing when that autopkgtest is run with the binary packages of plocate
>> from unstable. It passes when run with only packages from testing. In
>> tabular form:
> 
> Thanks for noticing. Given how annoying everything in autopkgtest is,
> perhaps the easiest thing is just deleting the tests. (1.1.7-3 wouldn't
> migrate to bullseye, then, but that's fine.)

As it stands, you'd only need to remove the third test, not all three.

Paul



OpenPGP_signature
Description: OpenPGP digital signature

Bug#988607: unblock: openldap/2.4.57+dfsg-3

[Ryan Tandy]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package openldap

[ Reason ]

Fix bug #988565: slapd-smbk5pwd crashes when initializing Kerberos.

smbk5pwd is a contributed plugin for slapd. It extends LDAP password 
change operations to also update the attributes used by Samba and 
Heimdal when their databases are stored in the LDAP directory.


At some point slapd picked up a transitive dependency on libkrb5-3 (via 
libwrap0). This caused the crash because at runtime smbk5pwd would call 
the MIT implementation of krb5_init_context and then pass the same 
context to Heimdal functions.


The two libkrb5 implementations do use symbol versioning, however, 
smbk5pwd contained references to the bare/unversioned symbols because it 
was not linking -lkrb5.


The fix is just to add -lkrb5 to the link line for smbk5pwd, which lets 
it correctly use the versioned symbols such as  
"krb5_init_context@HEIMDAL_KRB5_2.0". The symbols can be manually 
inspected via "nm -D /usr/lib/ldap/smbk5pwd.so".


One of the changed lines also occurs as context in another patch, which 
had to be refreshed to avoid fuzz.


[ Impact ]

slapd crashes on startup, if the smbk5pwd plugin is loaded and its 
Heimdal integration is enabled. Regression since it works in buster.


[ Tests ]

Upstream has an extensive test suite which runs at build time, however 
it does not cover the contrib modules such as smbk5pwd.


There is a superficial autopkgtest, which only tests whether the core 
slapd runs and answers a trivial query.


I manually tested the smbk5pwd plugin with the Samba and Kerberos 
integrations enabled.


[ Risks ]

I think this is a low risk change. The contrib modules each have their 
own individual build systems, so the change only affects the smbk5pwd 
Makefile and not any other component. It should be impossible for this 
change to impact any core component such as libldap or slapd.


[ Checklist ]

 [✓] all changes are documented in the d/changelog
 [✓] I reviewed all changes and I approve them
 [✓] attach debdiff against the package in testing

unblock openldap/2.4.57+dfsg-3

Thank you,
Ryan
diff -Nru openldap-2.4.57+dfsg/debian/changelog 
openldap-2.4.57+dfsg/debian/changelog
--- openldap-2.4.57+dfsg/debian/changelog   2021-02-14 09:26:41.0 
-0800
+++ openldap-2.4.57+dfsg/debian/changelog   2021-05-15 16:03:34.0 
-0700
@@ -1,3 +1,9 @@
+openldap (2.4.57+dfsg-3) unstable; urgency=medium
+
+  * Link smbk5pwd with -lkrb5. (Closes: #988565)
+
+ -- Ryan Tandy   Sat, 15 May 2021 16:03:34 -0700
+
 openldap (2.4.57+dfsg-2) unstable; urgency=medium
 
   * Fix slapd assertion failure in Certificate List Exact Assertion validation
diff -Nru openldap-2.4.57+dfsg/debian/patches/contrib-makefiles 
openldap-2.4.57+dfsg/debian/patches/contrib-makefiles
--- openldap-2.4.57+dfsg/debian/patches/contrib-makefiles   2021-02-14 
09:26:41.0 -0800
+++ openldap-2.4.57+dfsg/debian/patches/contrib-makefiles   2021-05-15 
16:03:34.0 -0700
@@ -76,8 +76,8 @@
  
 -HEIMDAL_INC = -I/usr/heimdal/include
 -HEIMDAL_LIB = -L/usr/heimdal/lib -lkrb5 -lkadm5srv
-+HEIMDAL_INC = $(shell krb5-config.heimdal --cflags kadm-server)
-+HEIMDAL_LIB = $(shell krb5-config.heimdal --libs kadm-server)
++HEIMDAL_INC = $(shell krb5-config.heimdal --cflags krb5 kadm-server)
++HEIMDAL_LIB = $(shell krb5-config.heimdal --libs krb5 kadm-server)
  
  LIBTOOL = $(LDAP_BUILD)/libtool
  CC = gcc
diff -Nru openldap-2.4.57+dfsg/debian/patches/smbk5pwd-makefile-manpage 
openldap-2.4.57+dfsg/debian/patches/smbk5pwd-makefile-manpage
--- openldap-2.4.57+dfsg/debian/patches/smbk5pwd-makefile-manpage   
2021-02-14 09:26:41.0 -0800
+++ openldap-2.4.57+dfsg/debian/patches/smbk5pwd-makefile-manpage   
2021-05-15 16:03:34.0 -0700
@@ -18,7 +18,7 @@
 --- a/contrib/slapd-modules/smbk5pwd/Makefile
 +++ b/contrib/slapd-modules/smbk5pwd/Makefile
 @@ -25,6 +25,7 @@
- HEIMDAL_LIB = $(shell krb5-config.heimdal --libs kadm-server)
+ HEIMDAL_LIB = $(shell krb5-config.heimdal --libs krb5 kadm-server)
  
  LIBTOOL = $(LDAP_BUILD)/libtool
 +INSTALL = /usr/bin/install

Bug#988598: RFS: vnstat/2.7-1 -- console-based network traffic monitor

[Christian Göttsche]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "vnstat":

 * Package name: vnstat
   Version : 2.7-1
   Upstream Author : Teemu Toivola 
 * URL : https://humdi.net/vnstat/
 * License : GPL-any, GPL-2
 * Vcs : https://salsa.debian.org/debian/vnstat
   Section : net

It builds those binary packages:

  vnstat - console-based network traffic monitor
  vnstati - image output support for vnStat

To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/vnstat/

Alternatively, one can download the package with dget using this command:

  dget -x https://mentors.debian.net/debian/pool/main/v/vnstat/vnstat_2.7-1.dsc

Changes since the last upload:

 vnstat (2.7-1) experimental; urgency=medium
 .
   * New upstream version 2.7
 .
   * debian: drop vnstatd systemd service link, vnstat.service is now the
 single systemd service name
   * d/patches:
 - add patches for correct format length specifiers on 32-bit systems
   and const correctness
 - rebase and drop upstream-applied ones
   * d/vnstat.docs: install upstream CHANGES file
   * d/copyright: update years
   * d/salsa-ci.yml: use Debian recipe

Regards,

Bug#988606: logrotate script creates logfile with wrong group

[Adam L Jacobs]

Package: clamav-freshclam
Version: 0.103.2


postinst creates a logrotate config that creates new log files with group 
"adm".  That used to be fine, but newer versions of clam
seem to update the group of the log file to the clam process' group whenever clam 
restarts.  That group is usually "clamav" and
almost always isn't "adm".

the result is that the log file gets created with one group by logrotate, but 
then gets changed when clam restarts.  this
confuses IDS tools like AIDE.

postinst should be changed so that the newly created logfile has the user and 
group of the user that clam runs as.



smime.p7s
Description: S/MIME Cryptographic Signature

Bug#988605: logrotate config creates log file with wrong group

[Adam L Jacobs]

Package: clamav-daemon
Version: 0.103.2


postinst creates a logrotate config that creates new log files with group 
"adm".  That used to be fine, but newer versions of clam
seem to update the group of the log file to the clam process' group whenever clam 
restarts.  That group is usually "clamav" and
almost always isn't "adm".

the result is that the log file gets created with one group by logrotate, but 
then gets changed when clam restarts.  this
confuses IDS tools like AIDE.

postinst should be changed so that the newly created logfile has the user and 
group of the user that clam runs as.



smime.p7s
Description: S/MIME Cryptographic Signature

Bug#976147: [debian-mysql] Bug#988089: Bug#988089: mariadb-server: MariaDB uninstalled on dist-upgrade Debian 10 -> 11

[Faustin Lammler]

Hi Otto!

Otto Kekäläinen ,
15/05/2021 – 12:56:58 (-0700):

> Yes we consider doing that. Note however that it does not fix this bug
> in question, we still want the dist-upgrade for Galera users to
> succeed. It also needs to be debugged and a MR submitted on how to
> change Galera-4 debian/control file for the upgrade to pass
> flawlessly.
It's not clear to me what the upgrade path for Galera would be given the
fact that both galera-3 and galera-4 packages exists in Bullseye. Should
a dist-upgrade upgrade galera-3 to galera-4 or does the user explicitly
have to ask for galera-4?

Also, removing the dependency to galera resolves the fact that
mariadb-server-10.3 is removed on a dist-upgrade (galera-3 is not
removed and mariadb-server-10.3 is upgraded to mariadb-server-10.5). So
if the deadline to upload mariadb is short (you spoke about tomorrow), I
find this solution valid until we find also a solution for Galera of
course...

> > The salsa CI is still green when doing so:
> > https://salsa.debian.org/faust/mariadb-10.5/-/pipelines/254990
> 
> Good. Did you also test upstream buildbot?
I have just created a WIP PR for that:
https://github.com/MariaDB/server/pull/1829

> Revert:
> https://github.com/MariaDB/server/commit/6bd94cf54274d54521ece1e50d534777122ff29e
You mean:
https://github.com/MariaDB/server/commit/b9fee60871264ea56a5582ca7a436aabdabea6fc

> But as said, the bug #988089 can only be fixed by a change in galera-4
> debian/control. Changing the mariadb-10.5 debian/control to
> recommends:galera-4 is a separate change.
Ok but I have no idea how this should be handled then. See my previous
comment and https://packages.debian.org/bullseye/galera-3 and
https://packages.debian.org/bullseye/galera-4.

-- 
Faustin


signature.asc
Description: PGP signature

Bug#988604: plocate: autopkgtest regression: plocate and mlocate can't be co-installed anymore

[Steinar H. Gunderson]

On Sun, May 16, 2021 at 09:17:57PM +0200, Paul Gevers wrote:
> With a recent upload of plocate the autopkgtest of plocate fails in
> testing when that autopkgtest is run with the binary packages of plocate
> from unstable. It passes when run with only packages from testing. In
> tabular form:

Thanks for noticing. Given how annoying everything in autopkgtest is,
perhaps the easiest thing is just deleting the tests. (1.1.7-3 wouldn't
migrate to bullseye, then, but that's fine.)

/* Steinar */
-- 
Homepage: https://www.sesse.net/

Bug#988604: plocate: autopkgtest regression: plocate and mlocate can't be co-installed anymore

[Paul Gevers]

Source: plocate
Version: 1.1.7-2
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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

   passfail
plocatefrom testing1.1.7-2
all others from testingfrom testing

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

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it? It seems you forgot
that one of your tests tries to coinstall both mlocate and plocate. With
your latest changes, that's not intended to be possible, making the test
fail. Please drop the test, or fix it. I think you could just depend on
mlocate and run apt-get install plocate in the test.

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

Paul

[1] https://qa.debian.org/excuses.php?package=plocate

https://ci.debian.net/data/autopkgtest/testing/amd64/p/plocate/12377970/log.gz




OpenPGP_signature
Description: OpenPGP digital signature

Bug#988596: akonadi-server: akonadi crashes permanently; akonadiconsole does not start

[andrei]

Package: akonadi-server
Version: 4:20.08.3-3
Severity: important
X-Debbugs-Cc: 99and...@mail.ru

Dear Maintainer,

in Plasma, all time I see the error window pops up regularly: "Akonadiserver
aborted".

In order to understand I start akonadiconsole but have

$ akonadiconsole
QSqlQuery::prepare: database not open
QSqlDatabasePrivate::removeDatabase: connection 'qt_sql_default_connection' is
still in use, all queries will cease to work.
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 961, resource
id: 12583504, major code: 40 (TranslateCoords), minor code: 0
org.kde.pim.akonadicore: Job error:  "" for collection: QVector()

$ akonadictl status
Akonadi Control: stopped
Akonadi Server: stopped
Akonadi Server Search Support: available (Remote Search, Akonadi Search Plugin)
Available Agent Types: akonadi_akonotes_resource, akonadi_archivemail_agent,
akonadi_birthdays_resource, akonadi_contacts_resource,
akonadi_davgroupware_resource, akonadi_ews_resource, akonadi_ewsmta_resource,
akonadi_followupreminder_agent, akonadi_google_resource, akonadi_ical_resource,
akonadi_icaldir_resource, akonadi_imap_resource, akonadi_indexing_agent,
akonadi_kalarm_dir_resource, akonadi_kalarm_resource, akonadi_kolab_resource,
akonadi_maildir_resource, akonadi_maildispatcher_agent,
akonadi_mailfilter_agent, akonadi_mbox_resource, akonadi_migration_agent,
akonadi_mixedmaildir_resource, akonadi_newmailnotifier_agent,
akonadi_notes_agent, akonadi_notes_resource, akonadi_openxchange_resource,
akonadi_pop3_resource, akonadi_sendlater_agent, akonadi_tomboynotes_resource,
akonadi_unifiedmailbox_agent, akonadi_vcard_resource, akonadi_vcarddir_resource

$ akonadictl start
org.kde.pim.akonadictl: Starting Akonadi Server...
org.kde.pim.akonadicontrol: Service org.freedesktop.Akonadi.Control.lock
already registered, terminating now.
Error: akonadi_control was started but didn't register at D-Bus session bus.
Make sure your system is set up correctly!


-- System Information:
Debian Release: 11.0
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-6-amd64 (SMP w/12 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE=ru
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages akonadi-server depends on:
ii  akonadi-backend-mysql4:20.08.3-3
ii  libaccounts-qt5-11.16-2
ii  libc62.31-11
ii  libgcc-s110.2.1-6
ii  libkf5akonadiprivate5abi2 [libkf5akonadiprivate5-20.08]  4:20.08.3-3
ii  libkf5akonadiwidgets5abi1 [libkf5akonadiwidgets5-20.08]  4:20.08.3-3
ii  libkf5configcore55.78.0-4
ii  libkf5coreaddons55.78.0-4
ii  libkf5crash5 5.78.0-3
ii  libkf5i18n5  5.78.0-2
ii  libqt5core5a 5.15.2+dfsg-5
ii  libqt5dbus5  5.15.2+dfsg-5
ii  libqt5gui5   5.15.2+dfsg-5
ii  libqt5network5   5.15.2+dfsg-5
ii  libqt5sql5   5.15.2+dfsg-5
ii  libqt5widgets5   5.15.2+dfsg-5
ii  libqt5xml5   5.15.2+dfsg-5
ii  libstdc++6   10.2.1-6

akonadi-server recommends no packages.

Versions of packages akonadi-server suggests:
ii  akonadi-backend-mysql   4:20.08.3-3
pn  akonadi-backend-postgresql  
pn  akonadi-backend-sqlite  

Bug#988603: libxml2: CVE-2021-3541: Exponential entity expansion attack bypasses all existing protection mechanisms

[Salvatore Bonaccorso]

Source: libxml2
Version: 2.9.10+dfsg-6.6
Severity: important
Tags: security upstream
Forwarded: https://gitlab.gnome.org/GNOME/libxml2/-/issues/228
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for libxml2.

CVE-2021-3541[0]:
| Exponential entity expansion attack bypasses all existing protection
| mechanisms

Technical details for the vulnerability are unfortunately not public,
but it looks that the flaw is essentially a variant of the billion
laughts attack (CVE-2003-1564) which can lead to denial of service for
applications using libxml2.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2021-3541
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3541
[1] https://gitlab.gnome.org/GNOME/libxml2/-/issues/228
[2] 
https://gitlab.gnome.org/GNOME/libxml2/-/commit/8598060bacada41a0eb09d95c97744ff4e428f8e

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#988474: [Fwd: Bug#988474: RFS: freefem++/3.61.1+dfsg1-5.2 [NMU] [RC] -- Provides the binaries of the FreeFem++ FE suite]

[Nilesh Patra]

Hi,

On Mon, 17 May 2021 at 00:10, François Mazen  wrote:

> Hello Anton,
>
> > When the package is successfully built on all relevant platforms,
> > you can ask the release team to unblock it. But it will unlikely
> > happen
> > due to release policy.
>
> I've requested the unblock, see [1]. Let me know if I've missed
> something.
>

As you might see freefem++ is not in testing, and as per the release
policy[1] the packages not in testing cannot re-enter testing at this stage.
The deadline for such packages to enter testing was Feb 12 and we are
months away from that date.

Nevertheless, it can definitely be a part of bookworm and
bullseye-backports. Thanks a lot for your work on
freefem++ :-)

[1]: https://release.debian.org/bullseye/freeze_policy.html#soft

Nilesh

Bug#986012: fatrace: autopkgtest regression: ^rm(.*): D /tmp/autopkgtest-lxc.yky1gevw/downtmp/build.jzI/src$ not found in log

[Martin Pitt]

Control: tag -1 pending

Paul Gevers [2021-03-27 21:43 +0100]:
> https://ci.debian.net/data/autopkgtest/testing/amd64/f/fatrace/11288159/log.gz
> 
> autopkgtest [23:08:44]: test fatrace-currentmount: [---
> ^rm(.*): D /tmp/autopkgtest-lxc.yky1gevw/downtmp/build.jzI/src$ not
> found in log

I finally found some time to reproduce this with [1]. I tested fatrace
manually, and I don't find any way any more to get open_by_handle_at() or
fanotify to work in an LXC container with the default security profile any
more. As I don't have any influence over the container setting in production
debci, I'm afraid my only way out is to apply "isolation-machine" to
fatrace-currentmount as well.

At least all the tests are runnning both in upstream and Ubuntu CI.

Thanks,

Martin

[1] https://ci.debian.net/doc/file.MAINTAINERS.html

Bug#988089: [debian-mysql] Bug#988089: Bug#988089: mariadb-server: MariaDB uninstalled on dist-upgrade Debian 10 -> 11

[Faustin Lammler]

Otto Kekäläinen ,
15/05/2021 – 12:50:24 (-0700):

> What you do in
> https://salsa.debian.org/faust/galera-4/-/commit/d0119633bd42ebcedb300fb7423035de4f91f1bc
> with aptly and tmux and printf 'X\n' seems overly complex. To make a
> local repo for testing you can simply run:

> apt install apt-utils
> cd /path/to/deb/files
> apt-ftparchive release . > Release
> echo 'deb [trusted=yes] file:/path/to/deb/files ./' >> /etc/apt/sources.list
> apt update
> apt dist-upgrade

Indeed! I guess that I was looking for an excuse to play with aptly
(understanding how this tool works was in my todo list for too long).

But yeah, completely overkill in that case, thanks!

-- 
Faustin


signature.asc
Description: PGP signature

Bug#584808: lldpd : adding a way to pick the running mode (tx/rx/tx_rx).

[Vincent Bernat]

 ❦  6 juin 2010 21:13 +02, Fabrice Lorrain:

> Using lldp with HP procurve switches, I've been using the posibility
> of configuring LLDP in <> ways on each port :
> - TX = transmit only mode
> - RX = receive only mode
> - TX_RX = mixte mode, TX & RX
>
> lldpd doesn't seem to provide such features.
>
> I would appreciate if it could be added in a next release.

This is possible since 0.8.0!
-- 
Don't diddle code to make it faster - find a better algorithm.
- The Elements of Programming Style (Kernighan & Plauger)

Bug#988602: Include babel-plugin-module-resolver with node-babel7

[Pirate Praveen]

Package: node-babel7
Version: 7.12.12+~cs150.141.84-6
Severity: wishlist

babel-plugin-module-resolver is a build dependency of cssnano

Bug#988596: Acknowledgement (akonadi-server: akonadi crashes permanently; akonadiconsole does not start)

[A L]

This akonadi problem arises after full-upgrade debian 10 up to debian 11 
... I saw it on two machines.


WBR,
A.

Bug#988595: stty: Doesn't work when flow control is on

[Pádraig Brady]

On 16/05/2021 16:00, Matthias Urlichs wrote:

Package: coreutils
Version: 8.32-4+b1
Severity: important
X-Debbugs-Cc: sm...@smurf.noris.de

If terminal output cannot drain, e.g. because of flow control, "stty" does
no longer work because it's using TCSETSW instead of TCSETS.
See ioctl_tty(2).

Fix: use TCSETS.


This is an option in stty, use "-drain" if you want to disable the default 
drain behavior.

cheers,
Pádraig

Bug#988596: akonadi-server: akonadi crashes permanently; akonadiconsole does not start

[A L]

This akonadi problem arises after dist-upgrade from debian 10 ...
I see it on two my machines.

WBR, 
Andrei

Bug#975270: rdiff-backup: Can't talk to the version from buster

[Samuel Thibault]

Hello,

Gregor Zattler, le dim. 16 mai 2021 18:50:42 +0200, a ecrit:
> * Samuel Thibault  [13. Mai. 2021]:
> > Kurt Roeckx, le jeu. 19 nov. 2020 20:40:05 +0100, a ecrit:
> >> I recently found out that my backup has broken for months.
> >
> > Not for month, but this does break my backups now that I try to upgrade
> > some machines, and I don't have another solution than to either
> > downgrade the package, or upgrade all my machines at the same time (!?)
> > to get my backups working again.
> 
> the rdiff-backup project provides a helpful document
> regarding this:
> 
> https://github.com/rdiff-backup/rdiff-backup/blob/master/docs/migration.md
> 
> providing this document in the NEWS.Debian file might be
> enough in order to close this bug?

Perhaps we could have a buster-backports package, so that before
upgrading machines to bullseye, we first just upgrade rdiff-backup on
all buster machines?

Samuel

Bug#988574: linux-image-armmp-lpae: ethernet on orange pi plus does not work

[Salvatore Bonaccorso]

Control: tags -1 - moreinfo
Control: forwarded -1 
https://lore.kernel.org/linux-arm-kernel/1243888060.510560.1612783497...@ichabod.co-bxl/

Hi

On Sun, May 16, 2021 at 05:05:25PM +0200, Salvatore Bonaccorso wrote:
> Control: tags -1 + moreinfo
> 
> Hi Vagrant,
> 
> On Sat, May 15, 2021 at 07:55:37PM -0700, Vagrant Cascadian wrote:
> > Source: linux
> > Version: 5.10.28-1
> > Severity: normal
> > Tags: patch
> > X-Debbugs-Cc: vagr...@reproducible-builds.org
> > 
> > When upgrading the reproducible builds infrastructure to bullseye, on
> > the orange pi plus ethernet stopped working with 5.10.x.
> > 
> > Applying a fix from upstream for a similar board appears to fix the
> > issue:
> > 
> > a900cac3750b9f0b8f5ed0503d9c6359532f644d
> > ARM: dts: sun7i: a20: bananapro: Fix ethernet phy-mode
> > 
> > 
> > dtdiff sun8i-h3-orangepi-plus-orig.dtb sun8i-h3-orangepi-plus.dtb
> > --- /dev/fd/63  2021-05-16 02:52:30.519751297 +
> > +++ /dev/fd/62  2021-05-16 02:52:30.523751128 +
> > @@ -364,7 +364,7 @@
> > interrupt-names = "macirq";
> > interrupts = <0x00 0x52 0x04>;
> > phy-handle = <0x14>;
> > -   phy-mode = "rgmii";
> > +   phy-mode = "rgmii-id";
> > phy-supply = <0x16>;
> > pinctrl-0 = <0x15>;
> > pinctrl-names = "default";
> > 
> > 
> 
> Can you please report this upstream and keep the Debian bug or me in
> the loop please?

Oh, actually this probably has been already done as per
https://lore.kernel.org/linux-arm-kernel/1243888060.510560.1612783497...@ichabod.co-bxl/
.

Regards,
Salvatore

Bug#985127: zopfli: please provide a VCS for zopfli packaging

[Victor Westerhuis]

Package: zopfli
Followup-For: Bug #985127

Hi Rogério,

I actually had the same issue, so I imported all existing versions using 
debsnap into a private Salsa repository at

https://salsa.debian.org/viccie30/zopfli.
It includes the full upstream git history from
https://github.com/google/zopfli.

The current Debian version is on debian/sid which is at tag 
debian/1.0.3-1. I've added a new version I built myself, on the 
debian/latest tag.


Regards,


Victor Westerhuis

-- System Information:
Debian Release: 11.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (100, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.12.4-personal (SMP w/4 CPU threads)
Locale: LANG=en_NL.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en_US:en:nl_NL:nl

Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages zopfli depends on:
ii  libc6   2.31-11
ii  libgcc-s1   10.2.1-6
ii  libstdc++6  10.2.1-6
ii  libzopfli1  1.0.3+git201125-0.2

zopfli recommends no packages.

zopfli suggests no packages.

-- no debconf information

Bug#975270: rdiff-backup: Can't talk to the version from buster

[Gregor Zattler]

Hi Samuel, debian developers,
* Samuel Thibault  [13. Mai. 2021]:
> Control: severity -1 serious
>
> Kurt Roeckx, le jeu. 19 nov. 2020 20:40:05 +0100, a ecrit:
>> I recently found out that my backup has broken for months.
>
> Not for month, but this does break my backups now that I try to upgrade
> some machines, and I don't have another solution than to either
> downgrade the package, or upgrade all my machines at the same time (!?)
> to get my backups working again.

the rdiff-backup project provides a helpful document
regarding this:

https://github.com/rdiff-backup/rdiff-backup/blob/master/docs/migration.md

providing this document in the NEWS.Debian file might be
enough in order to close this bug?


Ciao; Gregor

Bug#988601: unblock: eiskaltdcpp/2.4.2-1

[Boris Pek]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: tehn...@debian.org

Please unblock package eiskaltdcpp

This was a bugfix release of program with small amount of changes.
The most important one:
* Fix search on ADC hubs. (It was accidentally broken in 2.4.1 release.)

Notes:
Hub is just server software in terms of Direct Connect (DC aka NMDC) and
Advanced Direct Connect (ADC) protocols. For example, in Debian we have uhub
program which is ADC hub (without support of old DC protocol).

[ Reason ]
Bugfix release + updated translations.

Package was uploaded at 2021-03-03 01:02:49 +0300, almost ten days before
Hard Freeze (2021-03-12), but did not migrate to testing and I forgot to
check its status...

[ Impact ]
> What is the impact for the user if the unblock isn't granted?

Users connected only to ADC hubs will not be able to search files. All other
features (public and private chats, file exchange, observing file list, etc.)
work fine.

[ Tests ]
> What automated or manual tests cover the affected code?

There are no automated tests for code, but this version of program has been
successfully checked by a lot of users (including me) during long time
(since 2021-03-03).

[ Risks ]
There are no known risks.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

[ Other info ]
* I am upstream developer of program as well.
* Important patch: https://github.com/eiskaltdcpp/eiskaltdcpp/commit/e1717a8e
* Full diff: https://github.com/eiskaltdcpp/eiskaltdcpp/compare/v2.4.1...v2.4.2

unblock eiskaltdcpp/2.4.2-1



__debdiff.changes.diff
Description: Binary data

Bug#988600: ITP: tb-goodies - Useful Add-Ons for Thunderbird

[Mechtilde Stehmann]

Package: wnpp
Severity: wishlist

* Package name : 
  Version : x.y.z
  Upstream Author : Name 
* URL : http://www.example.org/
* License : (GPL, LGPL, BSD, MIT/X, etc.)
  Programming Lang: (C, C++, C#, Perl, Python, etc.)
  Description : Useful Add-Ons for Thunderbird

 It includes Add-Ons which helps to organize everyday work
 in the office.
 .
 This package will install the following Add-Ons:
   * View selective HTML-Mail (webext-allow-html-temp)
   * Reminder for emails (webext-mailmindr)
   * Create and use templates for autotext (webext-quicktext)
   * Persistent sticky notes for Thunderbird (webext-xnote)
 .
 Thunderbird/Lightning Add-On to support MS Exchange Calendar etc.
 (webext-tbsync) is only suggested.



* Why is this package useful/relevant?
  It helps to install relevant packages
* Is it a dependency for another package?
  No
* Do you use it yourself?
  Yse
* If there are other packages providing similar functionality,
  how does it compare?
  No
* How do you plan to maintain it? Do you plan to maintain it
  inside a packaging team?
  webext-team
  (check list at https://wiki.debian.org/Teams)
* Are you looking for co-maintainers? Do you need a sponsor?
  No

...--
Mechtilde Stehmann
## Debian Developer
## PGP encryption welcome
## F0E3 7F3D C87A 4998 2899  39E7 F287 7BBA 141A AD7F



OpenPGP_signature
Description: OpenPGP digital signature

Bug#988599: ITP: kata-containers -- secure container runtime with lightweight virtual machines

[Shengjing Zhu]

Package: wnpp
Severity: wishlist
Owner: Shengjing Zhu 
X-Debbugs-Cc: debian-de...@lists.debian.org, z...@debian.org

* Package name: kata-containers
  Version : 2.1.0
  Upstream Author : Kata Containers
* URL : https://katacontainers.io/
* License : Apache-2.0
  Programming Lang: Go, Rust
  Description : secure container runtime with lightweight virtual machines

Kata Containers is an open source project and community working to build a
standard implementation of lightweight Virtual Machines (VMs) that feel and
perform like containers, but provide the workload isolation and security
advantages of VMs.

Bug#988597: trash-cli version too old

[Andrea Francia]

Package: trash-cli
Version: 0.17.1.14-5

The trash-cli packages uses a four years old sources (0.17.1.14-5).
The latest version of trash-cli is 0.21.5.11.

The new versions uses the 'psutils' python package as a runtime dependency
and does not require anymore the '02_fs_encodingtype' patch (
https://salsa.debian.org/debian/trash-cli/-/blob/master/debian/patches/02_fs_encodingtype.patch
)
Also the a21b80d1e69783bb09376c3f60dd2f2a10578805.patch is no more needed.

I've seen in https://salsa.debian.org/debian/trash-cli that I can also send
a Merge Request, I could try do it by myself but I don't know yet how
importing from sources from upstream works and which check I've to do after
the source code modifications to check the packages.

Thank you
--
Andrea Francia http://andreafrancia.it

Bug#987353: CVE-2020-8903 CVE-2020-8907 CVE-2020-8933

[Theodore Y. Ts'o]

On Thu, May 13, 2021 at 09:56:53PM +0100, Marcin Kulisz wrote:
> 
> I hope that we're be able to change it, but for me fundamental
> question is if Google is interested in participating in effort to
> keep those packages in Debian main and if so what resources can be
> committed to do so.  From my side I can say that I'll try to find
> time to work on the relevant packages or to sponsor uploads if
> somebody else want to take on this task.

I'd be interested in helping; while I happen to work for Google, this
would only be in my personal compacity.  One caveat, though, which is
why I've hesitated in replying, is I don't have any experience
packaging Python applications.

In particular, if the Google SDK requires python packages that are
either newer or older than what is packaged in Debian, Debian's
prohibition of private copies of dependencies could make this quite
painful (if nothing else, just simply testing to make sure things
still work with variations in the Python packages available in
Debian)

- Ted

Bug#987359: RFS: sfxr-qt/1.3.0+git20210422-1 [ITP] -- sound effect generator, QtQuick port of sfxr

[Adam Borowski]

On Sun, May 16, 2021 at 05:25:19PM +0200, Gürkan Myczko wrote:
> On 15.05.2021 21:58, Adam Borowski wrote:
> > On Thu, Apr 22, 2021 at 11:58:08AM +0200, Gürkan Myczko wrote:
> > >  * Package name: sfxr-qt

> > It builds, but on trying to start:
> 
> during my test, after a small change how it builds, installs and starts.
> 
> > QQmlApplicationEngine failed to load component
> > qrc:/main.qml:288:9: Type FileActions unavailable
> > qrc:/FileActions.qml:27:9: Type FileDialog unavailable
> > file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Dialogs/DefaultFileDialog.qml:42:1:
> > module "QtQuick.Controls" version 1.2 is not installed
> 
> Mind retrying? #3
> https://mentors.debian.net/debian/pool/main/s/sfxr-qt/sfxr-qt_1.3.0+git20210422-1.dsc

QQmlApplicationEngine failed to load component
qrc:/main.qml:288:9: Type FileActions unavailable
qrc:/FileActions.qml:27:9: Type FileDialog unavailable
file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Dialogs/DefaultFileDialog.qml:42:1:
 module "QtQuick.Controls" version 1.2 is not installed

which is same as the above...


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ The oldest dated printed book includes the following license grant:
⣾⠁⢠⠒⠀⣿⡁   Reverently made for universal free distribution by Wang Jie
⢿⡄⠘⠷⠚⠋⠀   on behalf of his two parents on the 15th of the 4th moon of
⠈⠳⣄   the 9th year of Xiantong [11 May 868].

Bug#988346: RFS: fpart/1.3.0-1

[Ganael Laplanche]

Le 15/05/2021 à 08:15, Tobias Frost a écrit :

Hello Tobias,

Thanks a lot for taking care of my bug report.


Well, Debian is frozen – it is strongly discouraged to upload inapproppiate [1]
changes to unstable at this time.

So you should either target experimental or wait until bullseye is released.

(Below is assuming to either to wait or target experimental; Because of the
potential mess a upload to sid might create, I generally do not upload to sid
if it is clearly outside of [1])


Oh, right, thanks. I'll probably fix the remaining issues and come back 
with a fresh update once the freeze is over.


Thanks *a lot* for your detailed review ! (I'll take time to have a look 
at each point and come back to you).


Cheers,

--
Ganael Laplanche

Bug#987359: RFS: sfxr-qt/1.3.0+git20210422-1 [ITP] -- sound effect generator, QtQuick port of sfxr

[Gürkan Myczko]

On 15.05.2021 21:58, Adam Borowski wrote:

On Thu, Apr 22, 2021 at 11:58:08AM +0200, Gürkan Myczko wrote:

 * Package name: sfxr-qt



 sfxr-qt (1.3.0+git20210422-1) experimental; urgency=medium
 .
   * Initial release. (Closes: #931030)


It builds, but on trying to start:


during my test, after a small change how it builds, installs and starts.


QQmlApplicationEngine failed to load component
qrc:/main.qml:288:9: Type FileActions unavailable
qrc:/FileActions.qml:27:9: Type FileDialog unavailable
file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Dialogs/DefaultFileDialog.qml:42:1:
module "QtQuick.Controls" version 1.2 is not installed


Mind retrying? #3
https://mentors.debian.net/debian/pool/main/s/sfxr-qt/sfxr-qt_1.3.0+git20210422-1.dsc


Meow!

Bug#988326: libboost-python-dev: Linking against boost_python requires the python version number ex: -lboost_python39

[Anton Gladky]

Control: tags -1 wontfix

Hi, I am closing this bug. See an explanation above.

Best regards

Anton

Bug#988573: linux-image-5.10.0-6-alpha-smp dereferences a null pointer on boot

[Rich]

Sure, I'll try 5.12.4 once I'm done with the build I'm running. (I
have no idea how long that'll be, though, I've never built it
before...)

- Rich

On Sun, May 16, 2021 at 11:08 AM Salvatore Bonaccorso  wrote:
>
> Control: tags -1 + moreinfo
>
> Hi,
>
> On Sat, May 15, 2021 at 10:01:32PM -0400, Rich wrote:
> > Package: src:linux
> > Version: 5.10.28-1
> > Severity: normal
> > X-Debbugs-Cc: rincebr...@gmail.com
> >
> > Dear Maintainer,
> >
> > (This might also affect upstream, I haven't built a vanilla kernel to
> > experiment.)
> >
> > On my (qemu-provided) alpha system, attempting to boot with the SMP kernel
> > yields the following message during boot:
> >
> >
> > [   17.538076] Unable to handle kernel paging request at virtual address 
> > 
> > [   17.539053] CPU 3
> > [   17.539053] kworker/3:1(39): Oops -1
> > [   17.539053] pc = [<>]  ra = [<>]  ps = 
> > Tainted: GE
> > [   17.539053] pc is at 0x0
> > [   17.541983] ra is at 0x0
> > [   17.542959] v0 = 0007  t0 = fc00026b8fc0  t1 = 
> > 
> > [   17.542959] t2 = 0002  t3 =   t4 = 
> > 644e
> > [   17.543936] t5 = 4000  t6 = 0001  t7 = 
> > fc0004aac000
> > [   17.544912] s0 = fc00026b8fc0  s1 = fc00026b8fc0  s2 = 
> > fc0002731290
> > [   17.544912] s3 = fc0002731290  s4 = fc0002741290  s5 = 
> > fc00026b9178
> > [   17.545889] s6 = fc00010c9b80
> > [   17.545889] a0 =   a1 =   a2 = 
> > 0040
> > [   17.546866] a3 = 0040  a4 =   a5 = 
> > 
> > [   17.548819] t8 = 0001  t9 = 014bbcf4  t10= 
> > 0a546000
> > [   17.548819] t11= b938  pv = fc000193c640  at = 
> > 0001
> > [   17.550772] gp = fc0002721290  sp = 9468c7b6
> > [   17.550772] Disabling lock debugging due to kernel taint
> > [   17.550772] Trace:
> > [   17.551748] [] wait_rcu_exp_gp+0x20/0x50
> > [   17.551748] [] process_one_work+0x20c/0x520
> > [   17.552725] [] worker_thread+0x90/0x770
> > [   17.552725] [] kthread+0x1c4/0x1e0
> > [   17.553701] [] worker_thread+0x0/0x770
> > [   17.553701] [] ret_from_kernel_thread+0x18/0x20
> > [   17.554678] [] kthread+0x0/0x1e0
> > [   17.555655]
> > [   17.555655] Code:
> > [   17.555655]  
> > [   17.555655]  
> > [   17.556631]  00063301
> > [   17.556631]  13d5
> > [   17.556631]  
> > [   17.556631]  52a3
> > [   17.556631]
> >
> > which is not especially informative. I _suspect_ this may be somewhere in
> > the network stack, because the boot process shortly thereafter blocks
> > indefinitely on systemd-timesyncd starting...
> >
> > Since it could conceivably be relevant, my qemu command line for spawning
> > this VM is:
> >
> > qemu-system-alpha -m 4096 -vnc :12 -net nic,model=virtio-net-pci -net 
> > user,hostfwd=tcp::2-:22 -drive file=alpha,format=raw -smp 4 -kernel 
> > vmlinux-5.10.0-6-alpha-generic -initrd initrd.img-5.10.0-6-alpha-generic 
> > -append console=ttyS0 root=UUID=f5487547-65eb-4330-8644-39e494b5d972 
> > -nographic
> >
> > (with s/-generic/-smp/g for when it breaks)
> >
> > (I also have tried nic,model=e1000 and nic,model=ne2k_pci, it does not
> > change the printout.)
> >
> > The qemu version is qemu-system misc 5.2+dfsg-9~bpo10+1 from
> > buster-backports, on an x86_64 buster host.
>
> Can you please try to verify upstream as well and then report the
> issue directly to upstream (keep the Debian bug in the loop).
>
> Regards,
> Salvatore

Bug#988573: linux-image-5.10.0-6-alpha-smp dereferences a null pointer on boot

[Salvatore Bonaccorso]

Control: tags -1 + moreinfo

Hi,

On Sat, May 15, 2021 at 10:01:32PM -0400, Rich wrote:
> Package: src:linux
> Version: 5.10.28-1
> Severity: normal
> X-Debbugs-Cc: rincebr...@gmail.com
> 
> Dear Maintainer,
> 
> (This might also affect upstream, I haven't built a vanilla kernel to
> experiment.)
> 
> On my (qemu-provided) alpha system, attempting to boot with the SMP kernel
> yields the following message during boot:
> 
> 
> [   17.538076] Unable to handle kernel paging request at virtual address 
> 
> [   17.539053] CPU 3
> [   17.539053] kworker/3:1(39): Oops -1
> [   17.539053] pc = [<>]  ra = [<>]  ps = 
> Tainted: GE
> [   17.539053] pc is at 0x0
> [   17.541983] ra is at 0x0
> [   17.542959] v0 = 0007  t0 = fc00026b8fc0  t1 = 
> 
> [   17.542959] t2 = 0002  t3 =   t4 = 
> 644e
> [   17.543936] t5 = 4000  t6 = 0001  t7 = 
> fc0004aac000
> [   17.544912] s0 = fc00026b8fc0  s1 = fc00026b8fc0  s2 = 
> fc0002731290
> [   17.544912] s3 = fc0002731290  s4 = fc0002741290  s5 = 
> fc00026b9178
> [   17.545889] s6 = fc00010c9b80
> [   17.545889] a0 =   a1 =   a2 = 
> 0040
> [   17.546866] a3 = 0040  a4 =   a5 = 
> 
> [   17.548819] t8 = 0001  t9 = 014bbcf4  t10= 
> 0a546000
> [   17.548819] t11= b938  pv = fc000193c640  at = 
> 0001
> [   17.550772] gp = fc0002721290  sp = 9468c7b6
> [   17.550772] Disabling lock debugging due to kernel taint
> [   17.550772] Trace:
> [   17.551748] [] wait_rcu_exp_gp+0x20/0x50
> [   17.551748] [] process_one_work+0x20c/0x520
> [   17.552725] [] worker_thread+0x90/0x770
> [   17.552725] [] kthread+0x1c4/0x1e0
> [   17.553701] [] worker_thread+0x0/0x770
> [   17.553701] [] ret_from_kernel_thread+0x18/0x20
> [   17.554678] [] kthread+0x0/0x1e0
> [   17.555655]
> [   17.555655] Code:
> [   17.555655]  
> [   17.555655]  
> [   17.556631]  00063301
> [   17.556631]  13d5
> [   17.556631]  
> [   17.556631]  52a3
> [   17.556631]
> 
> which is not especially informative. I _suspect_ this may be somewhere in
> the network stack, because the boot process shortly thereafter blocks
> indefinitely on systemd-timesyncd starting...
> 
> Since it could conceivably be relevant, my qemu command line for spawning
> this VM is:
> 
> qemu-system-alpha -m 4096 -vnc :12 -net nic,model=virtio-net-pci -net 
> user,hostfwd=tcp::2-:22 -drive file=alpha,format=raw -smp 4 -kernel 
> vmlinux-5.10.0-6-alpha-generic -initrd initrd.img-5.10.0-6-alpha-generic 
> -append console=ttyS0 root=UUID=f5487547-65eb-4330-8644-39e494b5d972 
> -nographic
> 
> (with s/-generic/-smp/g for when it breaks)
> 
> (I also have tried nic,model=e1000 and nic,model=ne2k_pci, it does not
> change the printout.)
> 
> The qemu version is qemu-system misc 5.2+dfsg-9~bpo10+1 from
> buster-backports, on an x86_64 buster host.

Can you please try to verify upstream as well and then report the
issue directly to upstream (keep the Debian bug in the loop).

Regards,
Salvatore

Bug#988574: linux-image-armmp-lpae: ethernet on orange pi plus does not work

[Salvatore Bonaccorso]

Control: tags -1 + moreinfo

Hi Vagrant,

On Sat, May 15, 2021 at 07:55:37PM -0700, Vagrant Cascadian wrote:
> Source: linux
> Version: 5.10.28-1
> Severity: normal
> Tags: patch
> X-Debbugs-Cc: vagr...@reproducible-builds.org
> 
> When upgrading the reproducible builds infrastructure to bullseye, on
> the orange pi plus ethernet stopped working with 5.10.x.
> 
> Applying a fix from upstream for a similar board appears to fix the
> issue:
> 
> a900cac3750b9f0b8f5ed0503d9c6359532f644d
> ARM: dts: sun7i: a20: bananapro: Fix ethernet phy-mode
> 
> 
> dtdiff sun8i-h3-orangepi-plus-orig.dtb sun8i-h3-orangepi-plus.dtb
> --- /dev/fd/63  2021-05-16 02:52:30.519751297 +
> +++ /dev/fd/62  2021-05-16 02:52:30.523751128 +
> @@ -364,7 +364,7 @@
> interrupt-names = "macirq";
> interrupts = <0x00 0x52 0x04>;
> phy-handle = <0x14>;
> -   phy-mode = "rgmii";
> +   phy-mode = "rgmii-id";
> phy-supply = <0x16>;
> pinctrl-0 = <0x15>;
> pinctrl-names = "default";
> 
> 

Can you please report this upstream and keep the Debian bug or me in
the loop please?

the right people/lists would proably be:

Rob Herring  (maintainer:OPEN FIRMWARE AND FLATTENED DEVICE 
TREE BINDINGS)
Maxime Ripard  (maintainer:ARM/Allwinner sunXi SoC support)
Chen-Yu Tsai  (maintainer:ARM/Allwinner sunXi SoC support)
Jernej Skrabec  (reviewer:ARM/Allwinner sunXi SoC 
support)
devicet...@vger.kernel.org (open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE 
BINDINGS)
linux-arm-ker...@lists.infradead.org (moderated list:ARM/Allwinner sunXi SoC 
support)
linux-ker...@vger.kernel.org (open list)

Regards,
Salvatore

Bug#678065: debian-cd: Include brltty and espeakup in netinst

[Samuel Thibault]

Hello,

Steve McIntyre, le dim. 16 mai 2021 15:55:20 +0100, a ecrit:
> This morning's bullseye build for amd64:
> 
> -rw-r--r-- 1 debian-cd debian-cd 377487360 May 16 08:56 
> debian-testing-amd64-netinst.iso
> 
> and the build I've just triggered by hand:
> 
> -rw-r--r-- 1 debian-cd debian-cd 395313152 May 16 14:45 
> debian-testing-amd64-netinst.iso
> 
> the difference is just under 18MB for the netinst, I think that's
> OK. All the other larger images won't see any change here.
> 
> Marking this bug as closed now, as the change is in git and we're
> using it for builds now.

Thanks!

Samuel

Bug#988595: stty: Doesn't work when flow control is on

[Matthias Urlichs]

Package: coreutils
Version: 8.32-4+b1
Severity: important
X-Debbugs-Cc: sm...@smurf.noris.de

If terminal output cannot drain, e.g. because of flow control, "stty" does
no longer work because it's using TCSETSW instead of TCSETS.
See ioctl_tty(2).

Fix: use TCSETS.

-- System Information:
Debian Release: bullseye/sid
  APT prefers stable
  APT policy: (700, 'stable'), (650, 'testing'), (500, 'unstable'), (450, 
'focal'), (350, 'oldstable'), (300, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64

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

Versions of packages coreutils depends on:
ii  libacl1  2.2.53-10
ii  libattr1 1:2.4.48-6
ii  libc62.31-11
ii  libgmp10 2:6.2.1+dfsg-1
ii  libselinux1  3.1-3

coreutils recommends no packages.

coreutils suggests no packages.

-- debconf-show failed

Bug#985956: #985956 - missing kernel module in installer

[Salvatore Bonaccorso]

Control: tags -1 + pending confirmed

Hi,

On Fri, May 14, 2021 at 12:44:17PM +0100, Pete Batard wrote:
> Hi Wookey,
> 
> Thanks a lot for looking into this!
> 
> On 2021.05.14 03:08, Wookey wrote:
> 
> > I've done this, and if you want to test the mini.iso image at: 
> > http://wookware.org/software/rpi4-test.iso
> > That would be good. (I don't have an rpi4 to test on)
> 
> Just tested it, and I can confirm it fixes the NIC setup in the installer.
> 
> Just a small note that, because your image is ISOHybrid and only had EFI
> support when copied in DD mode (basically, it was missing formal
> /EFI/Boot/bootaa64.efi and /EFI/Boot/grubaa64.efi in the ISO9660 file system
> structure) I had to add those manually for boot to work, since we can't use
> straight DD copy for Pi boot.
> 
> In case you are interested, some information about how an installation media
> can be created for the Pi 4, and why a mere dd copy of an ISOHybrid won't
> do, can be found at:
> https://www.raspberrypi.org/forums/viewtopic.php?f=50=282839#p1713105.
> 
> > The one thing I'm not clear about is whether making the
> > mdio-bcm-unimac module available in the nic-modules-5.10.0-6-arm64-di
> > package on the installer image is sufficient, or if something needs to
> > be done about the initramfs too?
> 
> For the Pi 4 netint purpose, the fix you applied should be enough.
> For good measure, I went through a full system install using your ISO and
> saw no issues. Especially I validated that networking in the resulting
> installed system also worked fine.
> 
> > So I _think_ that means we don't need to change the initrd because
> > both the installer and normal boot have the ethernet mdio driver
> > available on localmedia, but I may be misunderstanding things.
> 
> My testing indicates that the assumption above should be correct.
> 
> > Right at the start of this bug you said:
> > > Note that this is a rather critical regression (since it used to work
> > > fine with previous bullseye ISOs)
> > 
> > I don't understand this. This module has presumably been missing from
> > the installer packages all along, so I don't see how it could have
> > worked before?
> 
> My guess is that kernel must have split Genet into Genet + MDIO recently
> because myself and a bunch of other people validated that the Bullseye
> testing netinst ISOs worked fine up to January this year, and we started to
> get "Unable to find mii" kernel messages with the 2021.01.04 ISO:
> https://www.raspberrypi.org/forums/viewtopic.php?f=50=282839=50#p1791942
> 
> > If it really is a regression
> 
> From our perspective it is, though it does not appear to be one that was
> introduced by Debian, but something that was most likely inherited from
> kernel.
> 
> > then this could be deemed an RC bug and
> > it is possible that it will get fixed for stable,
> 
> That would really help, because we spent a lot of time last year ironing
> things out to make sure that a distro like Bullseye could be installed
> easily on the Raspberry Pi 4 on release day (by fixing bugs such as
> #967918), and it's been very disappointing to see that what looks like a
> relatively straightforward issue to fix, such as adding a missing module,
> could bring us short of that goal. Once Bullseye is released, I expect a lot
> more people than the ones we had for testing, to want to give it a go, and
> having to tell them to wait for -r1 may just make them switch to a different
> distro.
> 
> But of course, it's up to Debian maintainership to decide the pros and cons
> of delaying the integration of this fix.
> 
> At any rate, thanks a lot for figuring out a proper fix.

FTR, commited the change for the next upload:
https://salsa.debian.org/kernel-team/linux/-/commit/bb0dbee4901603637d817736dbbb8e900b445d08

Regards,
Salvatore

Bug#678065: debian-cd: Include brltty and espeakup in netinst

[Steve McIntyre]

Hey Samuel!

Sorry for not responding earlier, I've been swamped with other
things. :-/

On Thu, Apr 29, 2021 at 11:43:39PM +0200, Samuel Thibault wrote:
>Samuel Thibault, le sam. 27 mars 2021 17:24:25 +0100, a ecrit:
>> Samuel wrote:
>> > Currently, the netinst images do not contain brltty and espeakup.. This
>> > means that blind users who install Debian without a network mirror end
>> > up with an unusable installed system, lacking brltty and espeakup to
>> > show braille or talk to them.
>> 
>> Steve McIntyre, le mar. 26 juin 2012 17:28:35 +0100, a ecrit:
>> > On Tue, Jun 26, 2012 at 01:20:57PM -0300, Samuel Thibault wrote:
>> > >Steve McIntyre, le Tue 26 Jun 2012 15:51:20 +0100, a écrit :
>> > >> Looking at this, it adds another ~20MB:
>> > >> ...
>> > >> CD 1: GUESS_TOTAL is 96183 after adding amd64:main:libicu48:8138068
>> > >
>> > >That's the main culprit and was the reason why
>> > >FJP removed brltty from the netinst CD (see
>> > >http://lists.debian.org/debian-cd/2008/10/msg00013.html). It seems the
>> > >effect has just worsened.
>> > 
>> > Yup, it's only going to get worse over time AFAICS.
>> 
>> Can we reconsider this for bullseye? Nowadays the netinst image already
>> includes libicu, so adding brltty and espeakup won't add much to the
>> image size. We have had at least one user who was really surprised
>> that he didn't get braille working in the installed system only
>> because he didn't have Internet available because of missing firmware.
>> Telling people to download the DVD-1 image for that case is not going to
>> fly :)

I've just moved espeakup, brltty and alsa-utils from the "forcd1" config
into tools/generate_di+k_list so they'll get pulled in for every build
including the netinst. Let's see how much of a size difference that makes.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
Who needs computer imagery when you've got Brian Blessed?

Bug#947085: cdebconf: Please omit cdebconf-{gtk,newt}-udeb on Ubuntu/i386

[Simon McVittie]

On Fri, 20 Dec 2019 at 12:11:44 -0600, Steve Langasek wrote:
> In Ubuntu, we are in the process of moving the i386 architecture to a
> compatibility-only layer on amd64. ... We would like to drop [some] udebs

Do I understand correctly that Ubuntu now builds all packages with the
noudeb build-profile, and therefore this change is no longer necessary
if the package is instead made to respect the noudeb build-profile using
the patch from #983518?

Thanks,
smcv

Bug#988594: ITP: allow-html-temp - View selective HTML-Mail

[Mechtilde Stehmann]

Package: wnpp
Severity: wishlist

* Package name : webext-allow-html-temp
  Version : 6.3.3
  Upstream Author : Name 
* URL :
https://addons.thunderbird.net/en-US/thunderbird/addon/allow-html-temp
* License : MPL-2.0
  Programming Lang: JavaScript
  Description :  View selective HTML-Mail

Allows one to have HTML temporarily allowed in the currently displayed
message by only one click.
 .
 When switching to another message, it'll be shown automatically again
in plain text or simple html mode (according to your default mode).




* Why is this package useful/relevant?
You can switch to read HTML-Mails, after checking sender.

* Is it a dependency for another package?
No
* Do you use it yourself?
Yes
* If there are other packages providing similar functionality,
  how does it compare?
No other package available
* How do you plan to maintain it? Do you plan to maintain it
  inside a packaging team?
inside the webext-team
  (check list at https://wiki.debian.org/Teams)
* Are you looking for co-maintainers? Do you need a sponsor?
No

...--
Mechtilde Stehmann
## Debian Developer
## PGP encryption welcome
## F0E3 7F3D C87A 4998 2899  39E7 F287 7BBA 141A AD7F



OpenPGP_signature
Description: OpenPGP digital signature

Bug#988593: foot: A new version of foot is available

[Nicolas Évrard]

Package: foot
Version: 1.6.4-1
Severity: wishlist

Dear Maintainer,

Hello,

I started using foot and I'd like to thank you for packaging it.

I noticed that a new version of foot is available, you might not have been
warned because uscan seems broken for packages on https://codeberg.org/ (maybe
a gitea update that broke it). Anyway it would be cool if that version is
available on debian (I must say the URL feature looks quite neat :D).

Regards,

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

Kernel: Linux 5.10.0-6-amd64 (SMP w/8 CPU threads)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages foot depends on:
ii  foot-terminfo   1.6.4-1
ii  libc6   2.31-12
ii  libfcft32.3.1-1
ii  libfontconfig1  2.13.1-4.2
ii  libpixman-1-0   0.40.0-1
ii  libwayland-client0  1.19.0-2
ii  libwayland-cursor0  1.19.0-2
ii  libxkbcommon0   1.0.3-2

foot recommends no packages.

foot suggests no packages.

-- no debconf information

Bug#988592: waybar: Missing dependency for module "custom/media"

[Peymaneh Nejad]

Package: waybar
Version: 0.9.5-2
Severity: normal

Dear Maintainer,

I would get an error when using the custom mediaplayer module, a python 
script at that is shipped with waybar (resources/custom_modules/mediaplayer.py) 

Turns out the script depends on gir1.2-playerctl-2.0 to be installed. 
I'm using ubuntu but it seems to me this applies for debian already.

I would suggest adding gir1.2-playerctl-2.0 to recommended or suggested
packages.

best regards,
Peymaneh

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

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

Versions of packages waybar depends on:
ii  init-system-helpers   1.60
ii  libc6 2.33-0ubuntu5
ii  libdbusmenu-gtk3-416.04.1+18.10.20180917-0ubuntu6
ii  libfmt7   7.1.3+ds1-5
ii  libgcc-s1 11.1.0-1ubuntu1~21.04
ii  libglib2.0-0  2.68.0-1
ii  libglibmm-2.4-1v5 2.64.2-2
ii  libgtk-3-03.24.25-1ubuntu4
ii  libgtk-layer-shell0   0.5.2-1
ii  libgtkmm-3.0-1v5  3.24.2-2
ii  libjsoncpp24  1.9.4-4
ii  libmpdclient2 2.19-1
ii  libnl-3-200   3.4.0-1build2
ii  libnl-genl-3-200  3.4.0-1build2
ii  libpulse0 1:14.2-1ubuntu1
ii  libsigc++-2.0-0v5 2.10.4-2ubuntu1
ii  libspdlog1 [libspdlog1-fmt7]  1:1.8.1+ds-2.1
ii  libstdc++611.1.0-1ubuntu1~21.04
ii  libudev1  247.3-3ubuntu3
ii  libwayland-client01.18.0-2~exp1.1

waybar recommends no packages.

Versions of packages waybar suggests:
ii  fonts-font-awesome  5.0.10+really4.7.0~dfsg-4
ii  libappindicator3-1  12.10.1+20.10.20200706.1-0ubuntu1
ii  sway1.5.1-2

-- no debconf information

Bug#988431: RFS: open-invaders/0.3-6 [QA] -- Space Invaders clone

[Adam Borowski]

On Wed, May 12, 2021 at 06:38:28PM -0300, Hugo Torres wrote:
>  * Package name: open-invaders
>Version : 0.3-6

> Changes since the last upload:
> 
>  open-invaders (0.3-6) experimental; urgency=medium
>  .
>* QA upload.
>* debian/control:
>- Added 'Rules-Requires-Root: no' to source stanza.
>- Added Vcs-* URLs to salsa.debian.org.
>- Bumped DH level format to 13.
>- Bumped Standards-Version to 4.5.1.
>- Updated homepage.
>* debian/copyright: Updated for format 1.0.
>* debian/lintian-overrides: Created for false positive.
>* debian/debian/open-invaders-data.docs renamed for open-invaders.docs.
>* debian/open-invaders.desktop: Added Keywords.
>* debian/patches/doc_directory_commented.patch: Created.
>* debian/patches/fix_ftbfs_gcc45.patch: Added header.
>* debian/patches/fix_pmask_amd64.patch: Added header.
>* debian/patches/format_security.patch: Added date in header.
>* debian/rules: Added the DEB_BUILD_MAINT_OPTIONS, 
> DEB_CXXFLAGS_MAINT_APPEND,
>DEB_CFLAGS_MAINT_APPEND and DEB_LDFLAGS_MAINT_APPEND 
> variable
>to improve the GCC hardening.
>* debian/salsa-ci.yml: Added to provide CI tests for Salsa.
>* debian/tests/control: Created for basic CI testing.
>* debian/upstream/metadata: Created.
>* debian/watch:
>- Bumped to version 4.
>- Updated the source address.

Alas, the autopkgtest fails -- and is bogus.

autopkgtest [15:02:01]: test command1: xvfb-run -a open-invaders &
autopkgtest [15:02:01]: test command1: [---
/usr/share
ALSA lib confmisc.c:767:(parse_card) cannot find card '0'
ALSA lib conf.c:4745:(_snd_config_evaluate) function snd_func_card_driver 
returned error: No such file or directory
ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings
ALSA lib conf.c:4745:(_snd_config_evaluate) function snd_func_concat returned 
error: No such file or directory
ALSA lib confmisc.c:1246:(snd_func_refer) error evaluating name
ALSA lib conf.c:4745:(_snd_config_evaluate) function snd_func_refer returned 
error: No such file or directory
ALSA lib conf.c:5233:(snd_config_expand) Evaluate error: No such file or 
directory
ALSA lib pcm.c:2660:(snd_pcm_open_noupdate) Unknown PCM default
autopkgtest [15:02:01]: test command1: ---]
autopkgtest [15:02:01]: test command1:  - - - - - - - - - - results - - - - - - 
- - - -
command1 FAIL stderr: ALSA lib confmisc.c:767:(parse_card) cannot 
find card '0'
autopkgtest [15:02:01]: test command1:  - - - - - - - - - - stderr - - - - - - 
- - - -
ALSA lib confmisc.c:767:(parse_card) cannot find card '0'
ALSA lib conf.c:4745:(_snd_config_evaluate) function snd_func_card_driver 
returned error: No such file or directory
ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings
ALSA lib conf.c:4745:(_snd_config_evaluate) function snd_func_concat returned 
error: No such file or directory
ALSA lib confmisc.c:1246:(snd_func_refer) error evaluating name
ALSA lib conf.c:4745:(_snd_config_evaluate) function snd_func_refer returned 
error: No such file or directory
ALSA lib conf.c:5233:(snd_config_expand) Evaluate error: No such file or 
directory
ALSA lib pcm.c:2660:(snd_pcm_open_noupdate) Unknown PCM default
autopkgtest [15:02:01]:  summary
command1 FAIL stderr: ALSA lib confmisc.c:767:(parse_card) cannot 
find card '0'

But that failure happened only due to luck.  The '&' at the end stops
most of errors from causing a failure, even "Test-Command: false &"
succeeds.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ The oldest dated printed book includes the following license grant:
⣾⠁⢠⠒⠀⣿⡁   Reverently made for universal free distribution by Wang Jie
⢿⡄⠘⠷⠚⠋⠀   on behalf of his two parents on the 15th of the 4th moon of
⠈⠳⣄   the 9th year of Xiantong [11 May 868].

Bug#982569: virtuoso-opensource: diff for NMU version 7.2.5.1+dfsg-3.1

[Adrian Bunk]

Control: tags 982569 + pending
Control: tags 982628 + pending
Control: tags 983414 + pending
Control: tags 986293 + patch
Control: tags 986293 + pending

Dear maintainer,

I've prepared an NMU for virtuoso-opensource (versioned as 7.2.5.1+dfsg-3.1)
and uploaded it to DELAYED/7. Please feel free to tell me if I should 
cancel it.

The proper fix for the part of #986293 that is not a duplicate of 
#986275 would be fixing whatever made libvirtuoso5.5-cil lose its
dependencies, Debian Mono Group copied in case someone has an idea
what broke that.

cu
Adrian
diff -Nru virtuoso-opensource-7.2.5.1+dfsg/debian/changelog virtuoso-opensource-7.2.5.1+dfsg/debian/changelog
--- virtuoso-opensource-7.2.5.1+dfsg/debian/changelog	2021-02-08 16:33:53.0 +0200
+++ virtuoso-opensource-7.2.5.1+dfsg/debian/changelog	2021-05-16 16:11:30.0 +0300
@@ -1,3 +1,14 @@
+virtuoso-opensource (7.2.5.1+dfsg-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop the libvirtuoso5.5-cil package. (Closes: #986293)
+  * Updated debconf translations:
+- Dutch from Frans Spiesschaert. (Closes: #983414)
+- German from Helge Kreutzmann. (Closes: #982628)
+- Portuguese from Américo Monteiro. (Closes: #982569)
+
+ -- Adrian Bunk   Sun, 16 May 2021 16:11:30 +0300
+
 virtuoso-opensource (7.2.5.1+dfsg-3) unstable; urgency=medium
 
   [ Debian Janitor ]
diff -Nru virtuoso-opensource-7.2.5.1+dfsg/debian/control virtuoso-opensource-7.2.5.1+dfsg/debian/control
--- virtuoso-opensource-7.2.5.1+dfsg/debian/control	2021-02-08 16:33:53.0 +0200
+++ virtuoso-opensource-7.2.5.1+dfsg/debian/control	2021-05-16 16:09:41.0 +0300
@@ -5,7 +5,6 @@
 Section: database
 Priority: optional
 Build-Depends: bison,
-   cli-common-dev [amd64 arm64 armel armhf i386 kfreebsd-amd64 kfreebsd-i386 mipsel ppc64 ppc64el s390x],
debhelper (>= 12~),
docbook2x,
docbook-xml,
@@ -21,7 +20,6 @@
libwbxml2-dev,
libxml2-dev,
m4,
-   mono-devel [amd64 arm64 armel armhf i386 kfreebsd-amd64 kfreebsd-i386 mipsel ppc64 ppc64el s390x],
net-tools,
pkg-kde-tools,
po-debconf,
@@ -350,16 +348,16 @@
  .
  This package contains the Virtuoso ODBC client libraries.
 
-Package: libvirtuoso5.5-cil
-Architecture: amd64 arm64 armel armhf i386 kfreebsd-amd64 kfreebsd-i386 mipsel ppc64 ppc64el s390x
-Section: cli-mono
-Depends: ${cli:Depends},
- ${misc:Depends}
-Description: high-performance database - Mono assemblies
- OpenLink Virtuoso is a high-performance object-relational SQL database.
- It provides transactions, a smart SQL compiler, hot backup, SQL:1999
- support, a powerful stored-procedure language supporting server-side
- Java or .NET, and more. It supports all major data-access interfaces,
- including ODBC, JDBC, ADO.NET, and OLE/DB.
- .
- This package contains Virtuoso's ADO.NET data provider for Mono.
+#Package: libvirtuoso5.5-cil
+#Architecture: amd64 arm64 armel armhf i386 kfreebsd-amd64 kfreebsd-i386 mipsel ppc64 ppc64el s390x
+#Section: cli-mono
+#Depends: ${cli:Depends},
+# ${misc:Depends}
+#Description: high-performance database - Mono assemblies
+# OpenLink Virtuoso is a high-performance object-relational SQL database.
+# It provides transactions, a smart SQL compiler, hot backup, SQL:1999
+# support, a powerful stored-procedure language supporting server-side
+# Java or .NET, and more. It supports all major data-access interfaces,
+# including ODBC, JDBC, ADO.NET, and OLE/DB.
+# .
+# This package contains Virtuoso's ADO.NET data provider for Mono.
diff -Nru virtuoso-opensource-7.2.5.1+dfsg/debian/po/de.po virtuoso-opensource-7.2.5.1+dfsg/debian/po/de.po
--- virtuoso-opensource-7.2.5.1+dfsg/debian/po/de.po	2021-02-08 16:33:53.0 +0200
+++ virtuoso-opensource-7.2.5.1+dfsg/debian/po/de.po	2021-05-16 16:11:30.0 +0300
@@ -3,20 +3,20 @@
 # package.
 #
 # Martin Eberhard Schauer , 2010.
+# Helge Kreutzmann , 2021.
 #
 msgid ""
 msgstr ""
-"Project-Id-Version: virtuoso-opensource6.1.0+dfsg2-2\n"
+"Project-Id-Version: virtuoso-opensource 7.2.5.1+dfsg-3\n"
 "Report-Msgid-Bugs-To: virtuoso-opensou...@packages.debian.org\n"
 "POT-Creation-Date: 2018-08-24 07:47+0200\n"
-"PO-Revision-Date: 2010-03-27 14:12+\n"
-"Last-Translator: Martin Eberhard Schauer \n"
-"Language-Team:  \n"
-"Language: \n"
+"PO-Revision-Date: 2021-02-12 17:19+0100\n"
+"Last-Translator: Helge Kreutzmann \n"
+"Language-Team:  German \n"
+"Language: de\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"X-Generator: KBabel 1.11.4\n"
 
 #. Type: password
 #. Description
@@ -153,6 +153,16 @@
 #. Description
 #: ../virtuoso-opensource-7.templates:7001
 msgid ""
+"The /var/lib/virtuoso-opensource-7 directory which contains the Virtuoso "
+"databases is about to be removed."
+msgstr ""
+"Das Verzeichnis 

Bug#988591: lintian: please error if Test-Command ends with an

[Adam Borowski]

Package: lintian
Version: 2.104.0
Severity: wishlist

Hi!
I found that a lot of packages declare an autopkgtest where the Test-Command
backgrounds itself.  This does nothing useful, as eg:
Test-Command: false &
passes successfully.  As the return value is ignored, any way such a test
can possibly fail is due to a stderr message that wins a race with
autopkgtest harness finishing.  But even that rarely does work:
Test-Command: xvfb-run -a /usr/bin/gcrytsal &
hasn't failed "for real" yet.

In most cases, this seems to be copy-pasta of xvfb-run for GUI programs.

There's no way to reliably spot un-waited-for backgroundings in long-form
tests (ie, ones shipped in a separate file), but checking for Test-Command
ending in an & should catch current crop of offenders.

Bug#988590: RFS: filezilla/3.54.1-1 [Team] -- Full-featured graphical FTP/FTPS/SFTP client

[Philip Wyett]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "filezilla":

 * Package name: filezilla
   Version : 3.54.1-1
   Upstream Author : Tim Kosse 
 * URL : https://filezilla-project.org/
 * License : BSD-like, permissive, MIT, GPL-2+, CC0-1.0
 * Vcs : https://salsa.debian.org/debian/filezilla
   Section : net

It builds those binary packages:

  filezilla - Full-featured graphical FTP/FTPS/SFTP client
  filezilla-common - Architecture independent files for filezilla

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/filezilla/

Alternatively, one can download the package with dget using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/f/filezilla/filezilla_3.54.1-1.dsc

Changes since the last upload:

 filezilla (3.54.1-1) experimental; urgency=medium
 .
   * Team upload
   * New upstream version 3.54.1

Regards

Phil

-- 
*** Playing the game for the games own sake. ***

WWW: https://kathenas.org

Twitter: @kathenasorg

Instagram: @kathenasorg

IRC: kathenas

GPG: 724AA9B52F024C8B


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

Bug#988583: elpa-debian-el: Cannot report any bugs at all. It is broken.

[David Bremner]

Salman Mohammadi  writes:

>
> I have no .reportbugrc bit instead use the following configuration in my 
> .emacs:
>
>    (setq user-mail-address "sal...@smoha.org"
>          user-full-name "Salman Mohammadi")
>
>    (setq send-mail-function 'mailclient-send-it)
>

I tried setting send-mail-function to mailclient-send-it (which by the
way tends to mangle attachements, but I guess that's not the issue here)
I still can't duplicate your issue.

You can try duplicating the problem with "emacs -q". You will
need to run M-x load-library  debian-el-autoloads .

If that works, then your issue is most likely an interaction with some
other emacs addon package. You can try removing them one by one, or
loading them manually into emacs -q.

Bug#988578: unblock: dmidecode/3.3-2

[Sebastian Ramacher]

Control: tags -1 moreinfo

On 2021-05-16 10:01:26, Jörg Frings-Fürst wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> X-Debbugs-Cc: Adrian Bunk 
> 
> Please unblock package dmidecode
> 
> [ Reason ]
> This release fixes the bug that causes a segmentation fault (Debian Bug
> #987033).
> 
> [ Impact ]
> Dmidecode terminates with a segmentation fault when certain parameters are
> used.
> 
> [ Tests ]
> Before the fix dmidecode -u fails.
> After the fix, dmidecode -u runs as expected.
> 
> [ Risks ]
> The changes aree trival.
> 
> [ Checklist ]
>   [X] all changes are documented in the d/changelog
>   [X] I reviewed all changes and I approve them
>   [X] attach debdiff against the package in testing
> 
> [ Other info ]
> I ask about the unblock after a hint from Adrian Bunk.
> 
> 
> unblock dmidecode/3.3-2

> diff -Nru dmidecode-3.3/debian/changelog dmidecode-3.3/debian/changelog
> --- dmidecode-3.3/debian/changelog2020-10-17 10:31:23.0 +0200
> +++ dmidecode-3.3/debian/changelog2021-05-07 09:13:05.0 +0200
> @@ -1,3 +1,15 @@
> +dmidecode (3.3-2) unstable; urgency=medium
> +
> +  * Add upstream recommended patches (Closes: #987033):
> +- New debian/patches/0145-Fix_condition_error_in_ascii_filter.patch.
> +- New debian/patches/0150-Fix_crash.patch.
> +  * Declare compliance with Debian Policy 4.5.1 (No changes needed).
> +  * debian/copyright:
> +- Add year 2021 to myself.
> +  * Remove longer not used patches.

I'd prefer an upload without the additional noise.

Please remove the moreinfo tag once the new version is available in
unstable.

Cheers

> +
> + -- Jörg Frings-Fürst   Fri, 07 May 2021 09:13:05 +0200
> +
>  dmidecode (3.3-1) unstable; urgency=medium
>  
>* New upstream release.
> diff -Nru dmidecode-3.3/debian/control dmidecode-3.3/debian/control
> --- dmidecode-3.3/debian/control  2020-10-17 09:58:18.0 +0200
> +++ dmidecode-3.3/debian/control  2021-05-07 08:54:34.0 +0200
> @@ -3,7 +3,7 @@
>  Priority: optional
>  Maintainer: Jörg Frings-Fürst 
>  Build-Depends: debhelper-compat (= 13)
> -Standards-Version: 4.5.0
> +Standards-Version: 4.5.1
>  Rules-Requires-Root: no
>  Vcs-Git: git://jff.email/opt/git/dmidecode.git
>  Vcs-Browser: https://jff.email/cgit/dmidecode.git/
> diff -Nru dmidecode-3.3/debian/copyright dmidecode-3.3/debian/copyright
> --- dmidecode-3.3/debian/copyright2020-10-17 10:14:51.0 +0200
> +++ dmidecode-3.3/debian/copyright2021-05-07 08:56:16.0 +0200
> @@ -13,7 +13,7 @@
>  Files: debian/*
>  Copyright: 2003-2007 Petter Reinholdtsen 
> 2011-2012 Daniel Baumann 
> 
> -   2014-2020 Jörg Frings-Fürst 
> +   2014-2021 Jörg Frings-Fürst 
>  License: GPL-2+
>  
>  License: GPL-2+
> diff -Nru dmidecode-3.3/debian/patches/0005-build.patch 
> dmidecode-3.3/debian/patches/0005-build.patch
> --- dmidecode-3.3/debian/patches/0005-build.patch 2015-09-28 
> 12:36:46.0 +0200
> +++ dmidecode-3.3/debian/patches/0005-build.patch 1970-01-01 
> 01:00:00.0 +0100
> @@ -1,25 +0,0 @@
> -Author: Daniel Baumann 
> -Description: Avoid overwriting build environment rather than to just extend 
> it.
> -
> -Index: trunk/Makefile
> -===
>  trunk.orig/Makefile
> -+++ trunk/Makefile
> -@@ -13,7 +13,7 @@
> - #
> - 
> - CC  = gcc
> --CFLAGS  = -W -Wall -Wshadow -Wstrict-prototypes -Wpointer-arith -Wcast-qual 
> \
> -+CFLAGS += -W -Wall -Wshadow -Wstrict-prototypes -Wpointer-arith -Wcast-qual 
> \
> -   -Wcast-align -Wwrite-strings -Wmissing-prototypes -Winline -Wundef
> - 
> - # Let lseek and mmap support 64-bit wide offsets
> -@@ -27,7 +27,7 @@ CFLAGS += -O2
> - #CFLAGS += -g
> - 
> - # Pass linker flags here
> --LDFLAGS =
> -+#LDFLAGS =
> - 
> - DESTDIR =
> - prefix  = /usr/local
> diff -Nru dmidecode-3.3/debian/patches/0105-dmidecode-avoid-sigbus.patch 
> dmidecode-3.3/debian/patches/0105-dmidecode-avoid-sigbus.patch
> --- dmidecode-3.3/debian/patches/0105-dmidecode-avoid-sigbus.patch
> 2015-10-01 06:33:47.0 +0200
> +++ dmidecode-3.3/debian/patches/0105-dmidecode-avoid-sigbus.patch
> 1970-01-01 01:00:00.0 +0100
> @@ -1,50 +0,0 @@
> -Description: Avoid SIGBUS on mmap failure
> - mmap will fail with SIGBUS if trying to map a non-existent portion of
> - a file. While this should never happen with /dev/mem, it can happen if
> - passing a regular file with option -d. While people should no longer
> - do that, failure gracefully seems better than crashing. So check for
> - the file size before calling mmap.
> -Author: Jean Delvare 
> -Origin: https://savannah.nongnu.org/bugs/download.php?file_id=35008
> -Bug: https://savannah.nongnu.org/bugs/index.php?46066
> -Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796963
> -Last-Update: 2015-10-01
> -
> -This patch header follows DEP-3: 

Bug#988589: cdebconf-gtk: should capture GLib structured logging to syslog in d-i

[Simon McVittie]

Package: cdebconf-gtk
Version: 0.257
Severity: normal
Tags: patch d-i

If a library like Pango is using the structured logging API in GLib 2.50+,
its logging messages are not caught by cdebconf-gtk's log handler.

Patch attached, also available at
.

smcv
>From f66ecc20da5f265cecf361f6983d92670a723bf8 Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Sun, 16 May 2021 13:04:08 +0100
Subject: [PATCH] gtk: Capture new-style GLib structured logging messages under
 d-i

GLib 2.50 replaced the non-machine-readable, text-based logging that
uses g_log_set_default_handler() with a more structured logging
framework inspired by systemd-journal. Each library can either use the
structured or unstructured logging framework; unstructured messages are
received by structured log handlers, but the opposite is not true.

For the purposes of this debconf frontend, the interesting libraries
include GLib and Pango (which use structured logging) and GTK 2
(which does not). As a result, GLib and Pango debug messages did not
go to the syslog in d-i; now they do.

Signed-off-by: Simon McVittie 
---
 debian/control|  2 +-
 src/modules/frontend/gtk/di.c | 36 ++-
 2 files changed, 36 insertions(+), 2 deletions(-)

diff --git a/debian/control b/debian/control
index f9c59227..caf9ead8 100644
--- a/debian/control
+++ b/debian/control
@@ -8,7 +8,7 @@ Build-Depends:
  libnewt-dev,
  libtextwrap-dev (>= 0.1-5),
  libdebian-installer4-dev (>= 0.41) | libdebian-installer-dev,
- libglib2.0-dev (>= 2.31),
+ libglib2.0-dev (>= 2.50),
  libgtk2.0-dev (>= 2.24) ,
  libcairo2-dev (>= 1.8.10-3) ,
  libselinux1-dev (>= 2.3) [linux-any] | libselinux-dev [linux-any],
diff --git a/src/modules/frontend/gtk/di.c b/src/modules/frontend/gtk/di.c
index 3dc5d38c..a6cb38f1 100644
--- a/src/modules/frontend/gtk/di.c
+++ b/src/modules/frontend/gtk/di.c
@@ -142,6 +142,40 @@ static void log_glib_to_syslog(const gchar * log_domain,
 g_free(string);
 }
 
+/** Implementation of GLogFunc for the GTK+ frontend.
+ *
+ * This will log messages going through the glib log system to the standard
+ * syslog.
+ *
+ * @param log_domain the log domain of the message
+ * @param log_level the log level of the message
+ * @param message the message to process
+ * @param user_data user data, set in g_log_set_handler()
+ */
+static GLogWriterOutput log_glib_structured_to_syslog(GLogLevelFlags log_level,
+  const GLogField *fields,
+  gsize n_fields,
+  gpointer user_data)
+{
+const char *domain = NULL;
+const char *message = "(no message)";
+gsize i;
+
+for (i = 0; i < n_fields; i++) {
+  const GLogField *field = [i];
+
+  if (g_strcmp0(field->key, "MESSAGE") == 0) {
+  message = field->value;
+  }
+  else if (g_strcmp0(field->key, "GLIB_DOMAIN") == 0) {
+  domain = field->value;
+  }
+}
+
+log_glib_to_syslog(domain, log_level, message, NULL);
+return G_LOG_WRITER_HANDLED;
+}
+
 /** Make the given window fullscreen.
  *
  * @param window main window
@@ -287,7 +321,7 @@ gboolean cdebconf_gtk_di_setup(struct frontend * fe)
 fe_data->di_data = di_data;
 
 (void) g_set_printerr_handler(print_to_syslog);
-(void) g_log_set_default_handler(log_glib_to_syslog,  NULL);
+g_log_set_writer_func(log_glib_structured_to_syslog, NULL, NULL);
 
 make_fullscreen(fe_data->window);
 set_shortcuts(fe);
-- 
2.31.1

Bug#988588: ftp.debian.org: please REJECT rust-rustls-native-certs from NEW queue

[Jan Niehusmann]

Package: ftp.debian.org
Severity: normal

The package rust-rustls-native-certs I uploaded 3 days ago contains a
diff from upstream which may be a bad idea (changing a dependency to an
older version).

I'm currently not sure what's the best way to fix the issue, so I can't
just upload an updated version.

Therefore, please REJECT the upload.

Bug#988434: (Future) FTBFS cups-filters with OpenLDAP 2.5

[Didier 'OdyX' Raboud]

Control: tags -1 +patch +pending

Hello Sergio, and thanks for your bugreport!

Le jeudi, 13 mai 2021, 03.17:54 h CEST Sergio Durigan Junior a écrit :
> We are working towards getting the new OpenLDAP version ready (2.5,
> which will soon be uploaded to experimental) and noticed that
> cups-filters FTBFS with it.  Upstream also noticed it and promptly fixed
> the problem.  I took the liberty to grab the patch, apply to the current
> version of cups-filters that is in experimental, and now I'm sending you
> the debdiff :-).

Excellent, thanks!

> FWIW, I was planning to create a Merge Request against the project on
> salsa, but it looks like the git repository hasn't been updated and
> doesn't reflect the current state of the package, so I thought it'd be
> better to open this bug.  Let me know if you prefer an MR and I will be
> happy to provide it after the repository is updated.

Hrm. The repository _is_ up-to-date, when looking at the correct branches :-)

https://salsa.debian.org/printing-team/cups-filters/-/tree/debian/experimental

In any case, I have now cherry-picked the patch and will upload to Debian 
experimental after a local test-build.

Best regards, and thanks for your work!
-- 
OdyX

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

Bug#477714: This should be closed

[Anders Jackson]

This bug isn't valid anymore.

Bug#988583: elpa-debian-el: Cannot report any bugs at all. It is broken.

[Salman Mohammadi]

On 5/16/21 1:31 PM, David Bremner wrote:

Control: tag -1 unreproducible
Control: severity -1 normal

Salman Mohammadi  writes:


Package: elpa-debian-el
Version: 37.10
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: sal...@smoha.org

Dear Maintainer,

I cannot report any bugs using M-x debian-bug at all. After entering the bug
summary, I get the following error message, and cannot correctly reach the page
where I should write the actual bug report.

   Getting package information from reportbug...
   debian-bug-prefill-report: Reportbug did not produce expected output!
Bailing out.
   Reportbug may have sent an empty report!

I can't reproduce this behaviour. I guess it might be related to
something in your reportbug configuration. Can you share your .reportbugrc?

By the way, this bug by itself does not "render package unusable", since
the package provides other functionality.


I have no .reportbugrc bit instead use the following configuration in my 
.emacs:


  (setq user-mail-address "sal...@smoha.org"
        user-full-name "Salman Mohammadi")

  (setq send-mail-function 'mailclient-send-it)


I had no problem in Debian 10 (stable) but as I upgraded to Sid, I get 
the mentioned error message.



Thanks, Salman

Bug#988547: apt: Apt seems to keep back galera-3 without reason

[Olaf van der Spek]

Op za 15 mei 2021 om 18:10 schreef David Kalnischkies :
> So upgrading mariadb will bring you galera-4 which conflicts with
> galera-3. Package removals are not allowed in 'upgrade' so this mariadb
> upgrade will be reverted and you will get it in the next step with
> a full-upgrade – which will remove galera-3.

That seems to be another problem, it does actually upgrade galera-3
and remove mariadb 10.3, but it does NOT install mariadb 10.5:

# apt dist-upgrade
The following packages will be REMOVED:
  libpython-stdlib mariadb-client-10.3 mariadb-client-core-10.3
mariadb-server mariadb-server-10.3 mariadb-server-core-10.3 python
python-minimal
The following packages will be upgraded:
  galera-3 libpython2-stdlib libpython2.7-minimal libpython2.7-stdlib
python2 python2-minimal python2.7 python2.7-minimal
8 upgraded, 0 newly installed, 8 to remove and 0 not upgraded.


> In regards to the mariadb versioned packages and the potential for
> upgrade problems they produce I had recently talked to its maintainer,
> so I doubt that will change any time soon…
> https://lists.debian.org/debian-devel/2021/03/msg00239.html

If it's okay with you I'd like to talk about that, but I think that'll
be for Debian 12.


-- 
Olaf

Bug#988584: manpages-hu: Contains undistributable content - All rights reserved

[Mario Blättermann]

Hello,

Helge Kreutzmann  schrieb am So., 16. Mai 2021, 12:27:

> Package: manpages-hu
> Version: 20010119-7
> Severity: serious
> Justification: Policy 2.3
> X-Debbugs-Cc: Mario Blättermann 
>
> Short:
> man8/ssh.8 states:
> .\" Copyright (c) 1995 Tatu Ylonen , Espoo, Finland
> .\"All rights reserved
>
> Long:
> The copyright situation is very unclear. I reviewed some files and besides
> the above one some are "GNU licensed" (without version), some require
> redistribution of copyright information in binary versions (I'm not sure
> if
> 2.3 Nr.3 remedies this), while others don't come with any statement at all.
> And debian/copyright places the burden of proof on the users in case
> comercial
> distribution is intended (e.g. Debian downstreams like Ubuntu). I wonder
> how
> this passed debian-legal?
>
> (This is just a selection, e.g. man.7,tsort.1,as.1 are interesting as
> well…)
>
> I tried looking at the mentioned upstream homepage, i.e.
> http://lme.linux.hu/forditas/index.html
> but this page is down atm.
>
> To resolve this bug, I suggest the following:
> 1. Remove all pages like ssh.8 which are clearly not distributable
>(After contacting with upstream or the respective authors they might
> be included in later versions again, if the license is updated)
>
> 2. Create a machine readable copyright including all authors (both of the
>english version and the respective translators) and the respective
> licenses.
>
> 3. Get the copyrights reviewed, e.g. on debian-legal, possibly catching
> more pages
>which cannot be distributed.
>
> 4. Check with upstream about a newer version. The pages are *old*. Is this
> really a
>service to your users?


See below for the plans to get rid of this outdated stuff.


> 5. Talk to manpages-l10n for integration of those pages, where copyright
> allows so.
>This way the maintance both for legal reasons and for updating (we use
> po4a) is
>vastly improved. Bonus if some translators are available, who could
> update the
>pages (its much easier with po4a).
>

We are planning to merge the remaining outdated manpages-* packages into
manpages-l10n anyway. So manpages-hu will be the next candidate for the
import. I will create a framework for Hungarian soon, and import the old
files step by step. The creation of the translated versions remains
disabled until the import is finished; once it is done, manpages-hu needs
to be removed from Debian to avoid package conflicts.

Best Regards,
Mario

Bug#988587: ITP: XNote - Persistent sticky notes for Thunderbird

[Mechtilde Stehmann]

Package: wnpp
Severity: wishlist

* Package name : webext-xnote
  Version : 3.1.3
  Upstream Author : xnote-us...@googlegroups.com
* URL : https://addons.thunderbird.net/en-US/thunderbird/addon/xnotepp/
* License : LGPL-2.1, MPL, MIT
  Programming Lang: Javascript
  Description :  Persistent sticky notes for Thunderbird

  You can define the note position in the settings. If you have a
  large screen, you can even display the notes outside of TB's main window,
  so it won't hide anything.



* Why is this package useful/relevant?
  It helps to manage e-mails which you are working on
  You can notice what you have done and what you want to do
  after you get some more information.
* Is it a dependency for another package?
  no
* Do you use it yourself?
  Yes it is necessary for my daily work
* If there are other packages providing similar functionality,
  how does it compare?
  There is no other similar package
* How do you plan to maintain it? Do you plan to maintain it
  inside a packaging team?
  I want to manage it in the webext-Team
* Are you looking for co-maintainers? Do you need a sponsor?
  No

...--
Mechtilde Stehmann
## Debian Developer
## PGP encryption welcome
## F0E3 7F3D C87A 4998 2899  39E7 F287 7BBA 141A AD7F



OpenPGP_signature
Description: OpenPGP digital signature

Bug#988583: elpa-debian-el: Cannot report any bugs at all. It is broken.

[David Bremner]

Control: tag -1 unreproducible
Control: severity -1 normal

Salman Mohammadi  writes:

> Package: elpa-debian-el
> Version: 37.10
> Severity: grave
> Justification: renders package unusable
> X-Debbugs-Cc: sal...@smoha.org
>
> Dear Maintainer,
>
> I cannot report any bugs using M-x debian-bug at all. After entering the bug
> summary, I get the following error message, and cannot correctly reach the 
> page
> where I should write the actual bug report.
>
>   Getting package information from reportbug...
>   debian-bug-prefill-report: Reportbug did not produce expected output!
> Bailing out.
>   Reportbug may have sent an empty report!

I can't reproduce this behaviour. I guess it might be related to
something in your reportbug configuration. Can you share your .reportbugrc?

By the way, this bug by itself does not "render package unusable", since
the package provides other functionality.

Bug#988586: RFS: radsecproxy/1.9.0~rc1-1~exp1 -- RADIUS protocol proxy supporting RadSec

[Sven Hartge]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "radsecproxy":

 * Package name: radsecproxy
   Version : 1.9.0~rc1-1~exp1
   Upstream Author : Fabian Mauchle 
 * URL : https://radsecproxy.github.io/
 * License : BSD-3-clause
 * Vcs : https://salsa.debian.org/debian/radsecproxy
   Section : net

It builds those binary packages:

  radsecproxy - RADIUS protocol proxy supporting RadSec

To access further information about this package, please visit the 
following URL:


  https://mentors.debian.net/package/radsecproxy/

Alternatively, one can download the package with dget using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/r/radsecproxy/radsecproxy_1.9.0~rc1-1~exp1.dsc


Changes since the last upload:

 radsecproxy (1.9.0~rc1-1~exp1) experimental; urgency=medium
 .
   * New upstream version 1.9.0-rc1
   * Add gbp.conf for experimental branch
   * Remove patches applied upstream

Grüße,
Sven.



OpenPGP_signature
Description: OpenPGP digital signature

Bug#988567: cubicsdr: crashes on first launch after install, lookes like not linked to right so

[Adrian Musceac]

Bug not related to cubicsdr, instead should be raised on librfspacesupport (ABI 
mismatch with Soapy 0.7).
Link to upstream ticket:
https://github.com/pothosware/SoapySDR/issues/305

Thanks.

On May 15, 2021 10:25:27 PM UTC, "Mr. T"  wrote:
>Package: cubicsdr
>Version: 0.2.5+dfsg-3+b1
>Severity: important
>X-Debbugs-Cc: t...@treaki.tk
>
>hi,
>i just apt install'ed it and then tried to launch it:
>
>~ $ CubicSDR Loaded 256 rig models via hamlib.
>
>Audio Device #0 PulseAudio
>Default Output? Yes
>Default Input? Yes
>Input channels: 2
>Output channels: 2
>Duplex channels: 2
>Native formats:
>16-bit signed integer.
>32-bit signed integer.
>32-bit float normalized between plus/minus 1.0.
>Supported sample rates:
>8000hz
>16000hz
>22050hz
>32000hz
>44100hz
>48000hz
>96000hz
>
>SDR enumerator starting.
>SoapySDR init..
>API Version: v0.7.1
>ABI Version: v0.7
>Install root: /usr
>Loading modules... [ERROR] 
>SoapySDR::loadModule(/usr/lib/x86_64-linux-gnu/SoapySDR/modules0.7/librfspaceSupport.so)
>dlopen() failed: 
>/usr/lib/x86_64-linux-gnu/SoapySDR/modules0.7/librfspaceSupport.so: 
>undefined symbol: _ZN5boost6chrono12steady_clock3nowEv
>Available factories...airspy, audio, bladerf, hackrf, lime, miri, null,
>
>osmosdr, redpitaya, remote, rtlsdr, uhd
>[INFO] [UHD] linux; GNU C++ version 10.2.1 20201207; Boost_107400; 
>UHD_3.15.0.0-4+b1
>Hash collision!!! Fatal error!!
>Segmentation fault
>~ $
>but as you see its just crashing...
>
>regards
>
>
>-- System Information:
>Debian Release: bullseye/sid
>APT prefers testing-security
>APT policy: (500, 'testing-security'), (500, 'testing')
>Architecture: amd64 (x86_64)
>
>Kernel: Linux 5.10.0-6-amd64 (SMP w/4 CPU threads)
>Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
>Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
>LANGUAGE=en_US:en
>Shell: /bin/sh linked to /usr/bin/dash
>Init: systemd (via /run/systemd/system)
>LSM: AppArmor: enabled
>
>Versions of packages cubicsdr depends on:
>ii libc6 2.31-11
>ii libgcc-s1 10.2.1-6
>ii libglx0 1.3.2-1
>ii libhamlib4 4.0-4
>ii libliquid2d 1.3.2-2
>ii libopengl0 1.3.2-1
>ii librtaudio6 5.1.0~ds1-1
>ii libsoapysdr0.7 0.7.2-2
>ii libstdc++6 10.2.1-6
>ii libtinyxml2.6.2v5 2.6.2-4
>ii libwxbase3.0-0v5 3.0.5.1+dfsg-2
>ii libwxgtk3.0-gtk3-0v5 3.0.5.1+dfsg-2
>
>Versions of packages cubicsdr recommends:
>ii soapysdr-module-all 0.7.2-2
>
>cubicsdr suggests no packages.
>
>-- no debconf information

Bug#988585: unblock: grub2/2.04-18

[Colin Watson]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock grub2 2.04-18.  This is mostly fixes from Steve to sort
out UEFI Secure Boot on i386.  The upstream patch to fix section size
calculation *seems* to only fix a problem on ia64 right now, which of
course wouldn't be release-critical by itself, but having
potentially-incorrect section sizes gives me the shivers so I thought it
best to include this as well.

You may need to manually unblock grub-efi-{amd64,arm64,ia32}-signed as
well to match, since these four source packages must all have matching
versions - I'm not sure exactly how the tools work from your end.

diff -Nru grub2-2.04/debian/.git-dpm grub2-2.04/debian/.git-dpm
--- grub2-2.04/debian/.git-dpm  2021-03-19 10:41:41.0 +
+++ grub2-2.04/debian/.git-dpm  2021-04-25 16:20:17.0 +0100
@@ -1,6 +1,6 @@
 # see git-dpm(1) from git-dpm package
-3d246c561a2c6aa18b78eae69e5100a2347dc7aa
-3d246c561a2c6aa18b78eae69e5100a2347dc7aa
+0eae44daa60c3f0ce8fdb349ba71b869a6738efd
+0eae44daa60c3f0ce8fdb349ba71b869a6738efd
 578bb115fbd47e1c464696f1f8d6183e5443975d
 578bb115fbd47e1c464696f1f8d6183e5443975d
 grub2_2.04.orig.tar.xz
diff -Nru grub2-2.04/debian/build-efi-images grub2-2.04/debian/build-efi-images
--- grub2-2.04/debian/build-efi-images  2021-03-19 10:41:41.0 +
+++ grub2-2.04/debian/build-efi-images  2021-04-25 16:20:17.0 +0100
@@ -150,12 +150,6 @@
cpuid
linuxefi
play
-   "
-   ;;
-esac
-case $platform in
-x86_64-efi)
-   CD_MODULES="$CD_MODULES
tpm
"
;;
@@ -197,6 +191,7 @@
"
 
 # CD boot image
+echo "Including modules $CD_MODULES in $outdir/gcd$efi_name.efi"
 "$grub_mkimage" -O "$platform" -o "$outdir/gcd$efi_name.efi" \
-d "$grub_core" \
-c "$workdir/grub-bootstrap.cfg" -m "$workdir/memdisk.fat" \
@@ -205,12 +200,14 @@
$CD_MODULES
 
 # Normal disk boot image
+echo "Including modules $GRUB_MODULES in $outdir/grub$efi_name.efi"
 "$grub_mkimage" -O "$platform" -o "$outdir/grub$efi_name.efi" \
-d "$grub_core" -p "/EFI/$efi_vendor" \
--sbat "$sbat_csv" \
$GRUB_MODULES
 
 # Normal network boot image
+echo "Including modules $NET_MODULES in $outdir/grubnet$efi_name.efi"
 "$grub_mkimage" -O "$platform" -o "$outdir/grubnet$efi_name.efi" \
-d "$grub_core" -c "$workdir/grub-bootstrap.cfg" \
-m "$workdir/memdisk-netboot.fat" \
@@ -221,6 +218,7 @@
 # Special network boot image for d-i to use. Just the same as the
 # normal network boot image, but with a different value baked in for
 # the prefix setting
+echo "Including modules $NET_MODULES in $outdir/grubnet$efi_name-installer.efi"
 "$grub_mkimage" -O "$platform" -o "$outdir/grubnet$efi_name-installer.efi" \
-d "$grub_core" -c "$workdir/grub-bootstrap.cfg" \
-m "$workdir/memdisk-netboot.fat" \
diff -Nru grub2-2.04/debian/changelog grub2-2.04/debian/changelog
--- grub2-2.04/debian/changelog 2021-03-19 10:41:41.0 +
+++ grub2-2.04/debian/changelog 2021-04-25 16:20:17.0 +0100
@@ -1,3 +1,18 @@
+grub2 (2.04-18) unstable; urgency=medium
+
+  [ Steve McIntyre ]
+  * Enable the shim_lock and tpm modules for i386-efi too. Ensure that
+tpm is included in our EFI images.
+  * List the modules we include the EFI images - make it easier to
+debug things.
+  * Add debug to display what's going on with verifiers
+
+  [ Colin Watson ]
+  * util/mkimage: Some fixes to PE binaries section size calculation
+(closes: #987103).
+
+ -- Colin Watson   Sun, 25 Apr 2021 16:20:17 +0100
+
 grub2 (2.04-17) unstable; urgency=medium
 
   * Pass --sbat when building the d-i netboot image as well.
diff -Nru grub2-2.04/debian/patches/debug_verifiers.patch 
grub2-2.04/debian/patches/debug_verifiers.patch
--- grub2-2.04/debian/patches/debug_verifiers.patch 1970-01-01 
01:00:00.0 +0100
+++ grub2-2.04/debian/patches/debug_verifiers.patch 2021-04-25 
16:20:17.0 +0100
@@ -0,0 +1,28 @@
+From bb6fe7f81818b8d102ca92b174d79aebb62469a0 Mon Sep 17 00:00:00 2001
+From: Steve McIntyre <93...@debian.org>
+Date: Sat, 17 Apr 2021 22:05:47 +0100
+Subject: Add debug to display what's going on with verifiers
+
+Patch-Name: debug_verifiers.patch
+---
+ grub-core/kern/verifiers.c | 2 ++
+ 1 file changed, 2 insertions(+)
+
+diff --git a/grub-core/kern/verifiers.c b/grub-core/kern/verifiers.c
+index 58dbe152a..ff984c8d8 100644
+--- a/grub-core/kern/verifiers.c
 b/grub-core/kern/verifiers.c
+@@ -100,11 +100,13 @@ grub_verifiers_open (grub_file_t io, enum grub_file_type 
type)
+   FOR_LIST_ELEMENTS(ver, grub_file_verifiers)
+ {
+   enum grub_verify_flags flags = 0;
++  grub_dprintf ("verify", "trying verifier %s\n", ver->name);
+   err = ver->init (io, type, , );
+   if (err)
+   goto fail_noclose;
+   if (flags & GRUB_VERIFY_FLAGS_DEFER_AUTH)
+   {
++grub_dprintf ("verify", 

Bug#988455: buster-pu: package velocity/1.7-5+deb10u1

[Chris Lamb]

Adam D. Barratt wrote:

> > Please consider velocity (1.7-5+deb10u1) for buster:
> >   
> >   velocity (1.7-5+deb10u1) buster; urgency=medium
> >   .
> > * CVE-2020-13936: Prevent a potential arbitrary code execution 
> > vulnerability
> >   that can be exploited by applications that allow untrusted users to
> >   upload/modify Velocity templates. (Closes: #985220)
>
> Please go ahead.

Thanks — I've uploaded velocity_1.7-5+deb10u1_amd64.changes for this.


Best wishes,

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