Bug#946145: 946145 fixed upstream

[Louis-Philippe Véronneau]

tag 946145 fixed-upstream
thanks

I've fixed this bug upstream and I plan to make a new release tomorrow.
I'll package this new release in Debian at the same time.

Cheers,

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄



signature.asc
Description: OpenPGP digital signature

Bug#949826: buster-pu: package haproxy/1.8.19-1

[Salvatore Bonaccorso]

Hi,

On Sun, Jan 26, 2020 at 01:00:31PM +0100, Vincent Bernat wrote:
>  ❦ 26 janvier 2020 05:50 +01, Moritz Mühlenhoff :
> 
> >> The logrotate configuration file for HAProxy doesn't signal rsyslog
> >> correctly. Therefore, logs are not really rotated and on a moderately
> >> busy site, this can fill up a log partition. When running with
> >> systemd, rsyslog doesn't write a PID file and there fore, the SysV
> >> init script invoked to rotate logs does not work. Instead, rsyslog
> >> package provides an helper for this purpose.
> >> 
> >> The change has been applied to 2.0.12-1 currently in unstable and
> >> testing. I would like to push it for the next point release next week.
> >
> > If we're doing a Buster update anyway, could we also piggyback the fix
> > for https://nathandavison.com/blog/haproxy-http-request-smuggling 
> > (CVE-2019-18277),
> > https://git.haproxy.org/?p=haproxy-2.0.git;a=commit;h=196a7df44d8129d1adc795da020b722614d6a581
> > ?
> 
> Ack! I have pulled the patch from the 1.8 branch. Here is the updated
> debdiff. It compiles and simple tests pass too. I'll be checking with
> upstream if they have an opinion around this.
> 

> diff --git a/debian/changelog b/debian/changelog
> index 978702081baa..7139318a49cf 100644
> --- a/debian/changelog
> +++ b/debian/changelog
> @@ -1,3 +1,12 @@
> +haproxy (1.8.19-1+deb10u1) buster; urgency=medium
> +
> +  * d/logrotate.conf: use rsyslog helper instead of SysV init script.
> +Closes: #946973.
> +  * d/patches: reject messages where "chunked" is missing from
> +transfer-encoding. CVE-2019-18277.
> +
> + -- Vincent Bernat   Sun, 26 Jan 2020 12:54:30 +0100

This needs to be rebased to the 1.8.19-1+deb10u1 which was released as
DSA 4577-1 AFAICT.

Regards,
Salvatore

Bug#947758: buster-pu: package node-handlebars/3:4.1.0-1+deb10u1

[Xavier]

Le 07/02/2020 à 20:16, Adam D. Barratt a écrit :
> On Sat, 2020-01-25 at 20:40 +, Adam D. Barratt wrote:
>> Control: tags -1 + confirmed
>>
>> On Mon, 2019-12-30 at 07:51 +0100, Xavier Guimard wrote:
>>> node-handlebars is vulnearable to prototype pollution (CVE-2019-
>>> 19919).
>>>
>>
>> Please go ahead.
> 
> This apparently causes regressions in the autopkgtests of node-
> markdown-it-html5-embed, which you also most recently uploaded - see 
> https://ci.debian.net/user/britney/jobs?package=node-markdown-it-html5-embed[]=stable[]=amd64
> 
> Is this enough of an issue to not include the node-handlebars update?
> 
> Regards,
> 
> Adam

Hi,

then please defer node-handlebars update until I understand what happens.

Cheers,
Xavier

Bug#949029: has to be fixed in brial

[Matthias Klose]

Control: reassign -1 src:brial

this has to be fixed in brial.  Changing the standard library just for the
distro isn't going to work.  Yes, it's unfortunate that such a change was
released, but IMO it's too late to fix there.

Bug#950723: debhelper: dh_installsystemd doesn't install template unit files by default

[Niels Thykier]

Control: tags -1 -d-i
Control: retitle -1 dh_installsystemd: NOOP promise is unsafe

Badreddin Aboubakr:
> Package: debhelper
> Version: 12
> Severity: normal
> Tags: d-i
> 
> Hello,
> i was trying to build Serf locally for stretch using debhelper 12.
> I started with golang-github-hashicorp-serf
> (0.8.1+git20171021.c20a0b1~ds1-4~bpo9+1),
> which is on the offical debain repo and did the following:
> 
> * Renamed `serf.service` inside debian/ to `serf@.service`
> * in `debian/rules` i added `override_dh_installinit:`
> 
> When building the package it built but it didn't copy the templete unit
> file `serf@.service`.
> In DH_INSTALLSYSTEMD(1) is wriiten if `debian/package@.service` it
> should be installed into lib/systemd/system/.
> 
> Then this was tested against unstable it didn't copy the templete
> unit.
> 
> Adding :
> ```override_dh_installsystemd:
>   dh_installsystemd -pserf serf@.service
> ```
> to `debian\rules` fixed the issue.
> 
> Thanks.
> 

Hi,

Thanks for the bug report.

I think this is caused by an optimization that enables dh to skip
dh_installsystemd.  You can confirm this by removing the arguments given
to dh_installsystemd in your example above.

This should still work (i.e. install serf@.service) without you
explicitly having to reference the service name.


~Niels

Bug#950574: sundials: Should ship pkgconfig files

[James Tocknell]

The pkg-config files were an additional thing added in the debian packaging
to make it easier to use sundials (upstream didn't distribute them as far
as I know). Presumably they were dropped in one of the transitions to a
newer version of sundials. The pkg-config modifications should still be in
the git history somewhere, but will probably take some work to update them.

James


On Tue, 4 Feb 2020 at 05:03, Andreas Kloeckner  wrote:

> Source: sundials
> Version: 4.1.0+dfsg-1+b2
> Severity: wishlist
>
> Dear Maintainer,
>
> From https://github.com/bmcage/odes I gather that sundials installs
> pkgconfig files, however those don't seem to be included in the -dev
> packages, which makes sundials harder than necessary to build.
>
> Thanks,
> Andreas
>
> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers testing
>   APT policy: (990, 'testing'), (500, 'unstable-debug'), (500,
> 'stable-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 5.5.0-rc5 (SMP w/8 CPU cores)
> Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
> LANGUAGE=de_DE:de (charmap=UTF-8)
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
>

-- 
Don't send me files in proprietary formats (.doc(x), .xls, .ppt etc.). It
isn't good enough for Tim Berners-Lee
,
and it isn't good enough for me either. For more information visit
http://www.gnu.org/philosophy/no-word-attachments.html.

Truly great madness cannot be achieved without significant intelligence.
 - Henrik Tikkanen

If you're not messing with your sanity, you're not having fun.
 - James Tocknell

In theory, there is no difference between theory and practice; In practice,
there is.

Bug#950910: wcc ftbfs with glibc-2.30

[Matthias Klose]

Package: src:wcc
Version: 0.0.2+dfsg-4
Severity: important
Tags: sid bullseye

wcc ftbfs with glibc-2.30:

mkdir -p bin
cd src && make CFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2 -W -Wall
-Wno-discarded-qualifiers -Wno-int-conversion -Wno-unused-parameter
-Wno-unused-function -Wno-unused-result -fpie -pie -fPIC -g3 -ggdb
-I../../include  -I./include/sflib/ -I./include -I../../include/
-Wno-incompatible-pointer-types  -fstack-protector-all -Wl,-z,relro,-z,now
-DPACKAGE -DPACKAGE_VERSION -masm=intel -rdynamic -D_fORTIFY_SOURCE=2 -O2"
make[2]: Entering directory '/<>/wcc-0.0.2+dfsg/src'
make[2]: warning: jobserver unavailable: using -j1.  Add '+' to parent make 
rule.
cd wcc && make CFLAGS=" -Wdate-time -D_FORTIFY_SOURCE=2 -W -Wall
-Wno-discarded-qualifiers -Wno-int-conversion -Wno-unused-parameter
-Wno-unused-function -Wno-unused-result -fpie -pie -fPIC -g3 -ggdb
-I../../include  -I./include/sflib/ -I./include -I../../include/
-Wno-incompatible-pointer-types  -fstack-protector-all -Wl,-z,relro,-z,now
-DPACKAGE -DPACKAGE_VERSION -masm=intel -rdynamic -D_fORTIFY_SOURCE=2 -O2"
make[3]: Entering directory '/<>/wcc-0.0.2+dfsg/src/wcc'
cc -Wdate-time -D_FORTIFY_SOURCE=2 -W -Wall -Wno-discarded-qualifiers
-Wno-int-conversion -Wno-unused-parameter -Wno-unused-function
-Wno-unused-result -fpie -pie -fPIC -g3 -ggdb -I../../include
-I./include/sflib/ -I./include -I../../include/  -Wno-incompatible-pointer-types
 -fstack-protector-all -Wl,-z,relro,-z,now -DPACKAGE -DPACKAGE_VERSION
-masm=intel -rdynamic -D_fORTIFY_SOURCE=2 -O2 wcc.c -o wcc -l:libbfd.a -lz -ldl
-liberty -lelf -lcapstone
cp wcc ../../bin/
make[3]: Leaving directory '/<>/wcc-0.0.2+dfsg/src/wcc'
cd wld && make CFLAGS=" -Wdate-time -D_FORTIFY_SOURCE=2 -W -Wall
-Wno-discarded-qualifiers -Wno-int-conversion -Wno-unused-parameter
-Wno-unused-function -Wno-unused-result -fpie -pie -fPIC -g3 -ggdb
-I../../include  -I./include/sflib/ -I./include -I../../include/
-Wno-incompatible-pointer-types  -fstack-protector-all -Wl,-z,relro,-z,now
-DPACKAGE -DPACKAGE_VERSION -masm=intel -rdynamic -D_fORTIFY_SOURCE=2 -O2"
make[3]: Entering directory '/<>/wcc-0.0.2+dfsg/src/wld'
cc -Wdate-time -D_FORTIFY_SOURCE=2 -W -Wall -Wno-discarded-qualifiers
-Wno-int-conversion -Wno-unused-parameter -Wno-unused-function
-Wno-unused-result -fpie -pie -fPIC -g3 -ggdb -I../../include
-I./include/sflib/ -I./include -I../../include/  -Wno-incompatible-pointer-types
 -fstack-protector-all -Wl,-z,relro,-z,now -DPACKAGE -DPACKAGE_VERSION
-masm=intel -rdynamic -D_fORTIFY_SOURCE=2 -O2 wld.c -o wld -l:libbfd.a -lz -ldl
-liberty
wld.c: In function ‘print_version’:
wld.c:110:57: warning: macro "__TIME__" might prevent reproducible builds
[-Wdate-time]
  110 |   printf("%s version:%s(%s %s)\n", WNAME, WVERSION, WTIME, WDATE);
  | ^
wld.c:110:64: warning: macro "__DATE__" might prevent reproducible builds
[-Wdate-time]
  110 |   printf("%s version:%s(%s %s)\n", WNAME, WVERSION, WTIME, WDATE);
  |^
cp wld ../../bin/
make[3]: Leaving directory '/<>/wcc-0.0.2+dfsg/src/wld'
cd wsh && make CFLAGS=" -Wdate-time -D_FORTIFY_SOURCE=2 -W -Wall
-Wno-discarded-qualifiers -Wno-int-conversion -Wno-unused-parameter
-Wno-unused-function -Wno-unused-result -fpie -pie -fPIC -g3 -ggdb
-I../../include  -I./include/sflib/ -I./include -I../../include/
-Wno-incompatible-pointer-types  -fstack-protector-all -Wl,-z,relro,-z,now
-DPACKAGE -DPACKAGE_VERSION -masm=intel -rdynamic -D_fORTIFY_SOURCE=2 -O2"
make[3]: Entering directory '/<>/wcc-0.0.2+dfsg/src/wsh'
cc -Wdate-time -D_FORTIFY_SOURCE=2 -W -Wall -Wno-discarded-qualifiers
-Wno-int-conversion -Wno-unused-parameter -Wno-unused-function
-Wno-unused-result -fpie -pie -fPIC -g3 -ggdb -I../../include
-I./include/sflib/ -I./include -I../../include/  -Wno-incompatible-pointer-types
 -fstack-protector-all -Wl,-z,relro,-z,now -DPACKAGE -DPACKAGE_VERSION
-masm=intel -rdynamic -D_fORTIFY_SOURCE=2 -O2 wsh.c -o wsh.o -c -fpie -fPIC -ldl
-lreadline
In file included from wsh.c:32:
./include/libwitch/wsh.h:69:10: fatal error: stropts.h: No such file or 
directory
   69 | #include 
  |  ^~~
compilation terminated.
make[3]: *** [Makefile:19: all] Error 1
make[3]: Leaving directory '/<>/wcc-0.0.2+dfsg/src/wsh'

Bug#950909: breezy-loom has stderr output with python3.8 in the autopkg tests

[Matthias Klose]

Package: src:breezy-loom
Version: 3.0.0-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.8

The current upload is a binary upload, and therefore doesn't migrate to testing.

When you re-upload, please consider to expect stderr output in the autopkg tests
with python3.8, or else the tests will fail:

[...]
breezy.plugins.loom.tests.blackbox.TestUp.test_up_with_clean_merge_leaving_thread_empty
  OK  935ms
/usr/lib/python3.8/os.py:1021: RuntimeWarning: line buffering (buffering=1)
isn't supported in binary mode, the default buffer size will be used
  return io.open(fd, *args, **kwargs)
--
Ran 145 tests in 21.626s

OK
autopkgtest [23:32:22]: test testsuite: ---]
autopkgtest [23:32:25]: test testsuite:  - - - - - - - - - - results - - - - - -
- - - -
testsuiteFAIL stderr: /usr/lib/python3.8/os.py:1021: RuntimeWarning:
line buffering (buffering=1) isn't supported in binary mode, the default buffer
size will be used

Bug#950824: RFS: sayonara/1.5.2-beta3~1 -- Small and lightweight music player

[Ko Ko Ye`]

some fix is done.

E: sayonara: \python-script-but-no-python-dep\ usr/bin/sayonara-ctl
#!python3
E: sayonara: \python-script-but-no-python-dep\
usr/bin/sayonara-query #!python3

update version is "sayonara_1.6.0~exp1"

also add source dependency to
   dh-python,
   doxygen,
   taglib,
   python3:any
and package dependencies
 doxygen,
 libtagc0,libtag1v5,libtag1v5-vanilla,
   ${python3:Depends},
for
E: sayonara: \embedded-library\ usr/bin/sayonara: taglib

taglib dependency still check in CMake


with regards.






On Sat, Feb 8, 2020 at 12:47 AM Boyuan Yang  wrote:

> Hi,
>
> 在 2020-02-07五的 11:14 +0630，Ko Ko Ye`写道：
> > I am looking for a sponsor for my package "sayonara"
> >
> > Sayonara is a small, clear and fast audio player for Linux written in
> C++,
> > supported by the Qt framework.
> > It uses GStreamer as audio backend. Sayonara is open source and uses the
> > GPLv3 license.
> > more at https://sayonara-player.com [1],
> > https://gitlab.com/luciocarreras/sayonara-player [2]
>
> Could you fix those lintian errors?
>
> E: sayonara: \embedded-library\ usr/bin/sayonara: taglib
> E: sayonara: \python-script-but-no-python-dep\ usr/bin/sayonara-ctl
> #!python3
> E: sayonara: \python-script-but-no-python-dep\ usr/bin/sayonara-query
> #!python3
>
> Besides, the version string is also buggy.
>   * The debian revision should be -1 and never be ~1.
>   * If upstream is releasing a beta version with version string as "1.5.2-
> beta3", you should consider mangling it back to "1.5.2~beta3" since
> "1.5.2-"
> is considered a higher version than "1.5.2" in Debian.
>
> Final result should be "1.5.2~beta3-1". Plese read deb-version(5) man page
> for
> information about Debian's versioning.
>
> Another thing is that you should drop historical changelog entries in
> debian/changelog. They are useless in Debian.
>
> --
> Thanks,
> Boyuan Yang
>


-- 

with regards *Ko Ko Ye`*

+95 97989 22022
+95 94500 22022
+95 9731 47907
kokoye2...@gmail.com
kokoye2...@ubuntu.com

skype: kokoye2007
jitsi: kokoye2007

http://ubuntu-mm.net
http://wiki.ubuntu.com/kokoye2007
http://wiki.ubuntu.com/MyanmarTeam http://loco.ubuntu.com/teams/ubuntu-mm

Bug#950572: libgcc-s1: Upgrading to GCC 10 with i386 and amd64 versions installed break applications loading

[Yannick Le Pennec]

Package: libgcc1
Version: 1:10-20200204-1
Followup-For: Bug #950572

Dear Maintainer,

It seems indeed that recent libgcc1 packages are no longer marked `Multi-Arch: 
same`.
This breaks multi-arch support as the package manager will keep either
amd64 or i386 libraries. This breaks Wine on my system, notably.

Regards.

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

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

Versions of packages libgcc1 depends on:
ii  gcc-10-base  10-20200204-1
ii  libc62.29-10
ii  libgcc-s110-20200204-1

libgcc1 recommends no packages.

libgcc1 suggests no packages.

-- no debconf information

Bug#950221: Taking over natsort into Debian Python Modules Team (Was: natsort 6.0 doesn't support Python 3.8)

[Andreas Tille]

Hi Agustin,

Matthias Klose wrote
> natsort 6.0 doesn't support Python 3.8, 6.2 is the first version supporting 
> it.
> There's also a 7.0 release.

I wonde whether you agree to move natsort to Debian Python Modules team
to support simple team uploads.  Seems the solution would be to upgrade
natsort to a later version.

Kind regards

   Andreas.

-- 
http://fam-tille.de

Bug#949795: mime-support: x-pascal mime type misses an extension

[Charles Plessy]

Dear Michael,

> > Le Sat, Jan 25, 2020 at 09:06:43AM +0100, Michael Van Canneyt a écrit :
> > > 
> > > Please consider changing the registration of text/x-pascal to
> > > 
> > > text/x-pascal   p pas pp

> On Tue, 28 Jan 2020, Charles Plessy wrote:
> > 
> > I can do this, but would you consider registering an official media type to 
> > the IANA ?
> > 
> > https://www.iana.org/form/media-types

Le Tue, Jan 28, 2020 at 04:30:35PM +0100, Michael Van Canneyt a écrit :
> 
> But I found no way to get x-pascal modified: the only possibilities were
> registering vnd.freepascal or so or text/pascal.

Indeed, the "x-" prefix is in general deprecated
(https://tools.ietf.org/html/rfc6648).

Note that there is nothing wrong with the vendor tree in principle.  If
freepascal would produce or use files in a format that is not found in
other implementations, that would be a good way to go. And this does not
prevent its use by others.  But if most Pascal implementations use the
same file formats with the same suffixes, then text/pascal would make
sense.

> I would think that text/pascal is an option, although maybe
> application/pascal (seeing that application/json exists) will be accepted
> easier.

I think that application/pascal would only be more meaningful than
text/pascal if the contents were meant to be executed on the fly, like
application/javascript, or if they were formatted in a way where the
main goal is to help freepascal to process the file, while readability
by human being with other tools (text editors, etc.) would be secondary.
In conclusion, I think that text/pascal would be more suitable.

> Also I'm not sure how the existing x-pascal and a vnd.pascal will cooperate
> if they register the same extension. (.pas, .pp, .inc are all valid
> extensions for the freepascal compiler.)

In principle, if you register text/pascal for instance, you can declare
text/x-pascal as a deprecated alias, but in practice, this media type is
not going to dissapear anytime soon.

Nevertheless, it is not likely to cause problems, except perhaps if it
pascal source code has to send it over HTTP to a remote application or
in similar contexts where the contents are not going to be loaded from a
file that has a name with an  extension.  In that case, if the remote
application is old and the server is more recent, it may sent a
content-type text/pascal to an application that would only accept
text/x-pascal.  But from what I understand about Pascal, this is not
likely to happen.

Altogether, it seems to me that what you want is that users who have
files that contain Pascal source code can be hinted by their desktop
environment or their operating system  about 1) the nature of the files
and 2) which programs can open them.

For 1) there are the file suffixes, which are only good enough as long
as nobody else start to use them concurrently for different purposes,
and databases of file signatures (think !#/bin/sh).  If Pascal source
code files have such a signature, a properly declared media type may
help the world to be aware of it, but it is not strictly necessary.  In
any case, co-existence of text/pascal and text/x-pascal would not be
problematic.

For 2) the main issue is to decide which choices go on top of the list,
and in Linux this is mainly a question of integration, user
configuration, or last-installed-at-the-top in the worst case
scenario...  Typically, if Free Pascal would prefer text/pascal over
text/x-pascal, then at installation time it would declare to the OS that
text/pascal exists, that file extensions .p .pas and .pp pertain to it,
and which program is able to open them in a meaningful way.  (Note that
on modern destkotp systems, /etc/mime.types is not the main source of
information anyway...).

> I assume you have more knowledge about this than I do, so any advice
> you have on this is welcome !

I think that registering a proper media type can be an interesting
experience.  When I registered the application/vnd.debian.binary-package
type for Debian, I actually learned a lot when I collected insights
about security.

https://www.iana.org/assignments/media-types/application/vnd.debian.binary-package

In the case of Pascal as well, it can be useful to document security
considerations.  For instance, if freepascal is given source files that
the operating system has identified as text/x-pascal, to what extent
will it trust this information?  Will it take them blindly without
checking for non-text characters purposed for crashing the program ?

Another useful point to document in the declaration of the media type
is how character encoding is handled.  Does Freepascal accept Unicode,
or only ASCII, etc. ?

Well, this mail is getting long and I have to go.  I hope you found it
useful.  Sorry for not proofreading myself, but I just exhausted my
one-hour-of-free-time-on-Saturday.  Please feel free to collect other
point of views (I would be interested to hear about them), and let me
know 

Bug#950908: RFS: opensurge/0.5.1.2-1 [ITP] -- Fun 2D retro platformer inspired by Sonic games

[Carlos Donizete Froes]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "opensurge"

 * Package name: opensurge
   Version : 0.5.1.2-1
   Upstream Author : Alexandre Martins 
 * URL : https://opensurge2d.org
 * License : GPL-3+
 * Vcs : https://salsa.debian.org/games-team/opensurge
   Section : games

It builds those binary packages:

  opensurge - Fun 2D retro platformer inspired by Sonic games
  opensurge-data - Fun 2D retro platformer inspired by Sonic games (data file)

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/o/opensurge/opensurge_0.5.1.2-1.dsc

Changes since the last upload:

   * Initial release (Closes: #943676)

Regards,

--
  Carlos Donizete Froes [a.k.a coringao]

Bug#947744: installation-reports: Debian Live Testing LXQt + nonfree - install fails with: "Bad unsquash configuration" Date: Wed, 1 Jan 2020 04:54:06 +0000 (UTC)

[scott092707]

>I'm wondering exactly what the effect of "with persistence" is, for example. 

Persistence is a very useful feature, whereby a certain amount of storage is 
reserved
on the media that is used when a change is made from the .iso , so that when it 
is again
booted, that change is still there.
For example:  I use a live session to back up my hard drive to another drive.
The back up program is not part of the .iso, so it must be installed.
Without persistence, each time I back up the drive, I must again install that
program.  With persistence, after the first time installed, it is as if it were 
part
of the .iso, and is usable immediately after boot.
Also, for instance, I happen to like the main panel on the top of the screen, 
not the bottom,
and my window-control buttons on the left, not on the right.
With persistence, after I first change these preferences, every time I boot, 
the panel
is at the top, and the window buttons on the left.
In effect, one can make a "custom" live session.
It is, of course, more useful, the more packages one needs to install, and the 
more
customizations one makes to the UI.

>Could you try again without that and see if that makes a difference for you, 
>please?
Yes... well... booting the live-usb without persistence solved the problem.

I can only speculate, that Calamares (or something Calamares calls) refers to
/run/live/medium/live/filesystem.squashfs
two different ways in two (or more) different locations of the code.
Without persistence, the two ways point to the same place, and all is good.
With persistence, the two ways point to two different places, and it fails.

Perhaps a symlink is involved...?

Bug#950907: RFP: git-repo-updater -- A console script that allows you to easily update multiple git repositories at once

[Alessandro Barbieri]

Package: wnpp
Severity: wishlist

* Package name: github-earwig-git-repo-updater
  Version : 0.5.1
  Upstream Author : Ben Kurtovic 
* URL : https://github.com/earwig/git-repo-updater
* License : MIT
  Programming Lang: Python
  Description : A console script that allows you to easily update multiple 
git repositories at once

gitup (the git-repo-updater)

gitup is a tool for updating multiple git repositories at once. It is smart 
enough to handle several remotes, dirty working directories, diverged local 
branches, detached HEADs, and more. It was originally created to manage a large 
collection of projects and deal with sporadic internet access.

gitup should work on macOS, Linux, and Windows. You should have the latest 
version of git and either Python 2.7 or Python 3 installed.

Bug#950906: RFP: zsh-history-substring-search -- ZSH port of Fish history search (up arrow)

[Alessandro Barbieri]

Package: wnpp
Severity: wishlist

* Package name: zsh-history-substring-search
  Version : 1.0.2
  Upstream Author : Suraj N. Kurapati
* URL : https://github.com/zsh-users/zsh-history-substring-search
* License : BSD
  Programming Lang: ZSH
  Description : ZSH port of Fish history search (up arrow)

This is a clean-room implementation of the Fish shell's history search feature, 
where you can type in any part of any command from history and then press 
chosen keys, such as the UP and DOWN arrows, to cycle through matches.

Bug#950905: RFP: ruby-whole-history-rating -- A pure ruby implementation of Rémi Coulom's Whole-History Rating (WHR) algorithm.

[Alessandro Barbieri]

Package: wnpp
Severity: wishlist

* Package name: whole-history-rating
  Version : 0.1.2
  Upstream Author : Pete Schwamb
* URL : https://rubygems.org/gems/whole_history_rating
* License : MIT
  Programming Lang: Ruby
  Description : A pure ruby implementation of Rémi Coulom's Whole-History 
Rating (WHR) algorithm.

A system for ranking game players by skill, based on Rémi Coulom's Whole 
History Rating algorithm, with modifications to support handicaps.

Developed for use on GoShrine, but the code is not go specific. It can support 
any two player game, as long as the outcome is a simple win/loss.

This gem provides a library and executables that take as input as set of games 
and output a set of skill rankings for the players of those games.

Bug#950904: RFP: mod-tile -- Renders and serves map tiles using apache

[Alessandro Barbieri]

Package: wnpp
Severity: wishlist

* Package name: mod-tile
  Version : 0.4
  Upstream Author : 
* URL : https://github.com/openstreetmap/mod_tile
* License : GPL-2.0
  Programming Lang: C, C++
  Description : Renders and serves map tiles using apache

mod_tile is a system to serve raster tiles for example to use within a slippy 
map. It provides a dynamic combination of efficient caching and on the fly 
rendering. Due to its dynamic rendering, only a small fraction of overall tiles 
need to be kept on disk, reducing the resources required. At the same time, its 
caching strategy allows for a high performance serving and can support several 
thousand requests per second.

Mod_tile was originally written for serving the tiles of the main OSM map 
(Mapnik layer), but since is being used on a variety of different servers 
providing maps ontop of OpenStreetMap data. 

Bug#950832: ITP: ospd -- Open Scanner Protocol daemon (OSPd)

[Ben Hutchings]

On Fri, 2020-02-07 at 09:46 +0100, Sophie Brun wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Sophie Brun 
> 
> * Package name: ospd
>   Version : 2.0.0
>   Upstream Author : Greenbone Networks GmbH
> * URL : https://github.com/greenbone/ospd
> * License : GPL-2+
>   Programming Lang: Python3
>   Description : Open Scanner Protocol daemon (OSPd)
> 
> OSPD is a base class for scanner wrappers which share the same
> communication protocol: OSP (Open Scanner Protocol). OSP creates a unified
> interface for different security scanners and makes their control flow and
> scan results consistently available under the central Greenbone
> Vulnerability Manager service.

I would suggest using "security scanners" instead of just "scanners" at
the *first* mention in the long description.  That way, the reader can
tell whether it is the right kind of scanning software a few seconds
earlier. :-)

Ben.

> This package is required for ospd-openvas, an openvas/greenbone
> tool.
> 
> I plan to maintain this package within the pkg-security team with the
> other openvas/ greenbone packages.
> 
-- 
Ben Hutchings
It's easier to fight for one's principles than to live up to them.




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

Bug#950903: ITP: liburing -- Linux kernel io_uring access library

[Guillem Jover]

Package: wnpp
Severity: wishlist
Owner: Guillem Jover 

* Package name: liburing
  Version : 0.4
  Upstream Author : Jens Axboe 
* URL : https://git.kernel.dk/cgit/liburing/
* License : LGPL and MIT/X
  Programming Lang: C
  Description : Linux kernel io_uring access library

 liburing provides helpers to setup and teardown io_uring instances,
 and also a simplified interface for applications that don't need (or
 want) to deal with the full kernel side implementation.


The liburing library is supposed so supercede the libaio library which
I maintain too, so it makes sense to handle both. :)

Thanks,
Guillem

Bug#830307: virt-manager: Virt-manager uses qemu-system-i386 /usr/lib/xen/bin

[Dave Hill]

Confirming this is still a problem in 10.2. Also, virt-manager appears 
to specify the wrong emulator in its optional configuration page. It 
says it's going to use qemu-system-i386, even though the architecture to 
be installed is x86_64. However, it will use a softlink to 
/usr/bin/qemu-system-x86_64 to create a new vm.



On Wed, 13 Mar 2019 12:32:36 +0100 Dejan Muhamedagic 
 wrote:> Package: virtinst


> Version: 1:2.0.0-3
> Followup-For: Bug #830307
>
> Just to report that this is still an issue on Buster. Apparently
> creating the links (ln -s) helps, just like RH did as shown in
> that bugzilla.
>
> Thanks!
>
>
> -- System Information:
> Debian Release: buster/sid
> APT prefers testing
> APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.19.0-2-rt-amd64 (SMP w/4 CPU cores; PREEMPT)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)

> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages virtinst depends on:
> ii e2fsprogs 1.44.5-1
> ii genisoimage 9:1.1.11-3+b2
> ii gir1.2-libosinfo-1.0 1.2.0-1
> ii python3 3.7.2-1
> ii python3-distutils 3.7.2-3
> ii python3-gi 3.30.4-1
> ii python3-libvirt 5.0.0-1
> ii python3-libxml2 2.9.4+dfsg1-7+b3
> ii python3-requests 2.20.0-2
>
> Versions of packages virtinst recommends:
> ii qemu-utils 1:3.1+dfsg-4
> ii virt-viewer 7.0-1
>
> virtinst suggests no packages.
>
> -- no debconf information
>
>

Bug#950902: projectile: please import upstream v2.1.0

[Nicholas D Steeves]

Source: projectile
Severity: normal

Hi Sean,

Would you please import upstream v2.1.0 and rebase the patches?  I
don't use git-debrebase and I don't know if a 'gbp pq rebase' will
disrupt your workflow, which is why I'm asking.  See changelog TODO at
commit:601ecc824071ba1d815623b67e27c325c7527683 for the change I'd
like to make after v2.1.0 is imported.

If the patches can be treated as a standard quilt series please let me
know and I'd be happy to merge the tag and rebase the patches myself
:-)


Thanks,
Nicholas

P.S. my motivation for this work is enabling the projectile-based
alternative back-end for Elpy, to allow users who eschew Ivy to have a
fully-functional IDE with comparable performance to the
find-file-in-project methods.

Bug#950901: ruby-fakefs: missing ruby2.7 support

[Cédric Boutillier]

Package: ruby-fakefs
Version: 0.20.1-1
Severity: important
Tags: upstream
Control: forwarded -1 https://github.com/fakefs/fakefs/issues/437

Dear Maintainer,

This library still does not support ruby2.7.
More investigation is needed.

Bug#944538: buster-pu: package ganeti-instance-debootstrap/0.16-6.1

[Antoine Beaupré]

On 2019-11-24 12:13:20, Antoine Beaupré wrote:
> On 2019-11-23 18:34:25, Julien Cristau wrote:
>> On Mon, Nov 11, 2019 at 10:40:58AM -0500, Antoine Beaupre wrote:
>>> diff -Nru ganeti-instance-debootstrap-0.16/debian/changelog 
>>> ganeti-instance-debootstrap-0.16/debian/changelog
>>> --- ganeti-instance-debootstrap-0.16/debian/changelog   2018-06-20 
>>> 06:57:18.0 -0400
>>> +++ ganeti-instance-debootstrap-0.16/debian/changelog   2019-11-01 
>>> 19:01:50.0 -0400
>>> @@ -1,3 +1,10 @@
>>> +ganeti-instance-debootstrap (0.16-6.1) unstable; urgency=medium
>>
>> Version number and distribution don't look right.
>
> Ah yes, that would be 0.16-6+deb10u1, right?
>

[...]

Attached a new debdiff with a better version number.

>> I'm a bit uneasy about a blanket "include all", to be honest.  It's
>> probably harmless since it's all coming straight out of debootstrap, but
>> I'd have been happier with something like "include security.*" if that's
>> what we expect to see.
>
> What kind of problems would you expect with including too many ACLs?
>
> A.
>
> -- 
> Qui vit sans folie n'est pas si sage qu'il croit.
> - François de La Rochefoucauld

-- 
Information is not knowledge. Knowledge is not wisdom.
Wisdom is not truth. Truth is not beauty.
Beauty is not love. Love is not music.
Music is the best.  - Frank Zappa

Bug#950900: llvm-toolchain-10: FTBFS on s390x invalid instructions

[Dimitri John Ledkov]

Package: llvm-toolchain-10
Severity: important

Dear Maintainer,

llvm-toolchain-10 ftbfs on s390x with

fatal error: error in backend: Not supported instr:  >
make[8]: *** [lib/Target/X86/CMakeFiles/LLVMX86CodeGen.dir/build.make:326: 
lib/Target/X86/CMakeFiles/LLVMX86CodeGen.dir/X86ISelLowering.cpp.o] Error 70
make[8]: Leaving directory 
'/<>/llvm-toolchain-10-10.0.0~+rc1/build-llvm/tools/clang/stage2-bins'
make[7]: *** [CMakeFiles/Makefile2:30692: 
lib/Target/X86/CMakeFiles/LLVMX86CodeGen.dir/all] Error 2
make[7]: *** Waiting for unfinished jobs


Please note that normally on Ubuntu Focal we default to -march=z13 and
we do build on z13 instructions capable mainframe.

Full build log at 
https://launchpad.net/ubuntu/+source/llvm-toolchain-10/1:10.0.0~+rc1-1~exp1/+build/18674202/+files/buildlog_ubuntu-focal-s390x.llvm-toolchain-10_1%3A10.0.0~+rc1-1~exp1_BUILDING.txt.gz

Regards,

Dimitr.

Bug#950899: llvm-toolchain-10: FTBFS on ppc64el fail-missing hwasan_symbolize

[Dimitri John Ledkov]

Package: llvm-toolchain-10
Version: 1:10.0.0~+rc1-1~exp1
Severity: important

Dear Maintainer,

llvm-toolchain-10 FTBFS on ppc64el due to fail-missing:

dh_install --fail-missing
dh_install: warning: Please use dh_missing --list-missing/--fail-missing instead
dh_install: warning: This feature will be removed in compat 12.
dh_install: warning: Cannot find (any matches for) 
"usr/lib/llvm-10/lib/clang/10.0.0/bin/hwasan_symbolize" (tried in ., debian/tmp)

dh_install: warning: clang-tools-10 missing files: 
usr/lib/llvm-10/lib/clang/10.0.0/bin/hwasan_symbolize
dh_install: error: missing files, aborting

Full Ubuntu Focal build log at:
https://launchpadlibrarian.net/464010057/buildlog_ubuntu-focal-ppc64el.llvm-toolchain-10_1%3A10.0.0~+rc1-1~exp1_BUILDING.txt.gz

Regards,

Dimitri.

Bug#854490: RFP: xva-img -- Citrix XenServer .xva disk extraction tool

[Francisco]

Hi, I'm working on xva-img, apparently I built the package.
This is my first job with packaging.
I wonder if I can pack it or does anyone else want to do it?

-- 
Francisco Vilmar Cardoso Ruviaro 
4096R: 1B8C F656 EF3B 8447 2F48 F0E7 82FB F706 0B2F 7D00

Bug#944538: buster-pu: package ganeti-instance-debootstrap/0.16-6.1

[Antoine Beaupré]

[sorry for the dupe, hit send by mistake :(]

On 2019-11-24 12:13:20, Antoine Beaupré wrote:
> On 2019-11-23 18:34:25, Julien Cristau wrote:
>> On Mon, Nov 11, 2019 at 10:40:58AM -0500, Antoine Beaupre wrote:
>>> diff -Nru ganeti-instance-debootstrap-0.16/debian/changelog 
>>> ganeti-instance-debootstrap-0.16/debian/changelog
>>> --- ganeti-instance-debootstrap-0.16/debian/changelog   2018-06-20 
>>> 06:57:18.0 -0400
>>> +++ ganeti-instance-debootstrap-0.16/debian/changelog   2019-11-01 
>>> 19:01:50.0 -0400
>>> @@ -1,3 +1,10 @@
>>> +ganeti-instance-debootstrap (0.16-6.1) unstable; urgency=medium
>>
>> Version number and distribution don't look right.
>
> Ah yes, that would be 0.16-6+deb10u1, right?

Attached a better debdiff with the right version number. I'm now part of
the ganeti team so this is actually a team upload now, and the patch has
been merged in the salsa repo.

[...]

>>
>> I'm a bit uneasy about a blanket "include all", to be honest.  It's
>> probably harmless since it's all coming straight out of debootstrap, but
>> I'd have been happier with something like "include security.*" if that's
>> what we expect to see.
>
> What kind of problems would you expect with including too many ACLs?

I'm still curious to hear what kind of problems you expect here. I've
been running this patch in production for months now and would really
like to see this land in buster (and hopefully stretch next).

Can I upload the package now?

Thanks!
-- 
Men are taught to apologize for their weaknesses, women for their
strengths.
- Lois Wyse
diff -Nru ganeti-instance-debootstrap-0.16/debian/changelog ganeti-instance-debootstrap-0.16/debian/changelog
--- ganeti-instance-debootstrap-0.16/debian/changelog	2018-06-20 06:57:18.0 -0400
+++ ganeti-instance-debootstrap-0.16/debian/changelog	2020-02-07 17:11:06.0 -0500
@@ -1,3 +1,10 @@
+ganeti-instance-debootstrap (0.16-6+deb10u1) buster; urgency=medium
+
+  * Team upload.
+  * add patch to respect linux caps (Closes: #942114)
+
+ -- Antoine Beaupré   Fri, 07 Feb 2020 17:11:06 -0500
+
 ganeti-instance-debootstrap (0.16-6) unstable; urgency=medium
 
   * Bump Standards-Version to 4.1.4; no changes needed
diff -Nru ganeti-instance-debootstrap-0.16/debian/patches/respect-Linux-capabilities-7-in-cache.patch ganeti-instance-debootstrap-0.16/debian/patches/respect-Linux-capabilities-7-in-cache.patch
--- ganeti-instance-debootstrap-0.16/debian/patches/respect-Linux-capabilities-7-in-cache.patch	1969-12-31 19:00:00.0 -0500
+++ ganeti-instance-debootstrap-0.16/debian/patches/respect-Linux-capabilities-7-in-cache.patch	2020-02-07 17:11:06.0 -0500
@@ -0,0 +1,48 @@
+From cd34bcc48a2af92f484535b81fba2d46dad1dbb6 Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Antoine=20Beaupr=C3=A9?= 
+Date: Thu, 10 Oct 2019 11:07:51 -0400
+Subject: [PATCH] respect Linux capabilities(7) in cache
+
+The default GNU tar configuration does not carry fancy extended
+attributes and that is where, among other things, stuff like Linux
+capabilities(7) are stored. This is kind of important because that's
+how ping(8) works for regular users.
+
+We shove --selinux and --acls in there while we're at it, because why
+not. We never know what the future might bring, and it seems
+silly *not* to create a complete archive.
+
+Note that --xattrs-include='*' is important because, by default, GNU
+tar will not include capabilities /even/ if --xattrs is specified on
+the commandline, see this bug report for details:
+
+https://bugzilla.redhat.com/show_bug.cgi?id=771927
+---
+ create | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/create b/create
+index 607bab2..7526e71 100755
+--- a/create
 b/create
+@@ -83,7 +83,7 @@ if [ "$CLEAN_CACHE" -a -d "$CACHE_DIR" ]; then
+ fi
+ 
+ if [ -f "$CACHE_FILE" ]; then
+-  tar xf "$CACHE_FILE" -C $TMPDIR
++  tar --acls --selinux --xattrs --xattrs-include='*' -x -f "$CACHE_FILE" -C $TMPDIR
+ else
+   if [ "$PROXY" ]; then
+ export http_proxy="$PROXY"
+@@ -109,7 +109,7 @@ else
+ 
+   if [ "$GENERATE_CACHE" = "yes" ]; then
+ TMP_CACHE=`mktemp "${CACHE_FILE}.XX"`
+-tar cf "$TMP_CACHE" -C $TMPDIR .
++tar --acls --selinux --xattrs --xattrs-include='*' -c -f "$TMP_CACHE" -C $TMPDIR .
+ mv -f "$TMP_CACHE" "$CACHE_FILE"
+   fi
+ fi
+-- 
+2.20.1
+
diff -Nru ganeti-instance-debootstrap-0.16/debian/patches/series ganeti-instance-debootstrap-0.16/debian/patches/series
--- ganeti-instance-debootstrap-0.16/debian/patches/series	2018-06-20 06:57:18.0 -0400
+++ ganeti-instance-debootstrap-0.16/debian/patches/series	2020-02-07 17:11:06.0 -0500
@@ -1 +1,2 @@
+respect-Linux-capabilities-7-in-cache.patch
 fix-sfdisk-BLKRRPART.patch

Bug#950898: ansible/buster: flatpak_remote: IndexError: list index out of range

[Hector Oron Martinez]

Package: ansible
Version: 2.7.7+dfsg-1
Severity: important
Tags: patch

Hello,

Note this issue only happens in stable, Buster 10.2 with ansible 2.7.7

When using ansible with flatpak_remote, it breaks. The following snippet:
```
- name: Add the flathub flatpak repository remote to the user 
installation
  flatpak_remote:
name: flathub
state: present
flatpakrepo_url: https://dl.flathub.org/repo/flathub.flatpakrepo
method: user
```

causes:

```
TASK [Add the flathub flatpak repository remote to the user installation] 
*
fatal: [127.0.0.1]: FAILED! => {"changed": false, "module_stderr": 
"/home/zumbi/.ansible/tmp/ansible-tmp-1581109559.271161-112064566806002/AnsiballZ_flatpak_remote.py:17:
 DeprecationWarning: the imp module is deprecated in favour of importlib; see 
the module's documentation for alternative uses\n  import imp\nTraceback (most 
recent call last):\n  File 
\"/home/zumbi/.ansible/tmp/ansible-tmp-1581109559.271161-112064566806002/AnsiballZ_flatpak_remote.py\",
 line 113, in \n_ansiballz_main()\n  File 
\"/home/zumbi/.ansible/tmp/ansible-tmp-1581109559.271161-112064566806002/AnsiballZ_flatpak_remote.py\",
 line 105, in _ansiballz_main\ninvoke_module(zipped_mod, temp_path, 
ANSIBALLZ_PARAMS)\n  File 
\"/home/zumbi/.ansible/tmp/ansible-tmp-1581109559.271161-112064566806002/AnsiballZ_flatpak_remote.py\",
 line 48, in invoke_module\nimp.load_module('__main__', mod, module, 
MOD_DESC)\n  File \"/usr/lib/python3.7/imp.py\", line 234, in load_module\n
return load_source(name, filename, file)\n  File \"/usr/lib/python3.7/imp.py\", 
line 169, in load_source\nmodule = _exec(spec, sys.modules[name])\n  File 
\"\", line 630, in _exec\n  File \"\", line 728, in exec_module\n  File \"\", line 219, in _call_with_frames_removed\n  File 
\"/tmp/ansible_flatpak_remote_payload_3i68y3ku/__main__.py\", line 241, in 
\n  File \"/tmp/ansible_flatpak_remote_payload_3i68y3ku/__main__.py\", 
line 230, in main\n  File 
\"/tmp/ansible_flatpak_remote_payload_3i68y3ku/__main__.py\", line 172, in 
remote_exists\nIndexError: list index out of range\n", "module_stdout": "", 
"msg": "MODULE FAILURE\nSee stdout/stderr for the exact error", "rc": 1}
to retry, use: --limit 
@/home/zumbi/SCM/GITAuth/local/ansible/playbook.retry
```

The issue has been reported upstream at:
https://github.com/ansible/ansible/issues/51481

And a pull request has been merged:
https://github.com/ansible/ansible/pull/54103

I am attaching a debdiff I have tested and fixes the issue above.
Please, consider fixing this issue in Buster, via stable-updates. If you
need help, please let me know, I am willing to proceed with the upload
if you wish.

Regards

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

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

Versions of packages ansible depends on:
ii  python33.7.3-1
ii  python3-crypto 2.6.1-9+b1
ii  python3-cryptography   2.6.1-3+deb10u2
ii  python3-httplib2   0.11.3-2
ii  python3-jinja2 2.10-2
ii  python3-netaddr0.7.19-1
ii  python3-paramiko   2.4.2-0.1
ii  python3-pkg-resources  40.8.0-1
ii  python3-yaml   3.13-2

Versions of packages ansible recommends:
ii  python3-jmespath   0.9.4-1
ii  python3-kerberos   1.1.14-2
ii  python3-libcloud   2.4.0-1
ii  python3-selinux2.8-1+b1
ii  python3-winrm  0.3.0-2
ii  python3-xmltodict  0.11.0-2

Versions of packages ansible suggests:
pn  cowsay   
pn  sshpass  

-- no debconf information
diff -Nru ansible-2.7.7+dfsg/debian/changelog 
ansible-2.7.7+dfsg/debian/changelog
--- ansible-2.7.7+dfsg/debian/changelog 2019-02-21 08:44:57.0 +0100
+++ ansible-2.7.7+dfsg/debian/changelog 2020-02-07 22:07:29.0 +0100
@@ -1,3 +1,12 @@
+ansible (2.7.7+dfsg-1local1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Local test of upstream patch to fix flatpak module:
+https://github.com/ansible/ansible/issues/51481
+https://github.com/ansible/ansible/pull/54103
+
+ -- Hector   Fri, 07 Feb 2020 22:07:29 +0100
+
 ansible (2.7.7+dfsg-1) unstable; urgency=high
 
   * New upstream release
diff -Nru 
ansible-2.7.7+dfsg/debian/patches/d78b3424dd9e72132df9b52ee4e5422cd3094bd6.patch
 
ansible-2.7.7+dfsg/debian/patches/d78b3424dd9e72132df9b52ee4e5422cd3094bd6.patch
--- 
ansible-2.7.7+dfsg/debian/patches/d78b3424dd9e72132df9b52ee4e5422cd3094bd6.patch
1970-01-01 01:00:00.0 +0100
+++ 
ansible-2.7.7+dfsg/debian/patches/d78b3424dd9e72132df9b52ee4e5422cd3094bd6.patch
2020-02-07 22:07:29.0 +0100
@@ -0,0 

Bug#949322: python-pysaml2: CVE-2020-5390

[Moritz Mühlenhoff]

On Fri, Feb 07, 2020 at 09:59:58AM +0100, Thomas Goirand wrote:
> On 1/19/20 9:05 PM, Salvatore Bonaccorso wrote:
> > Source: python-pysaml2
> > Version: 4.5.0-5
> > Severity: grave
> > Tags: security upstream
> > Justification: user security hole
> > Control: found -1 4.5.0-4
> > 
> > Hi,
> > 
> > The following vulnerability was published for python-pysaml2.
> > 
> > CVE-2020-5390[0]:
> > | PySAML2 before 5.0.0 does not check that the signature in a SAML
> > | document is enveloped and thus signature wrapping is effective, i.e.,
> > | it is affected by XML Signature Wrapping (XSW). The signature
> > | information and the node/object that is signed can be in different
> > | places and thus the signature verification will succeed, but the wrong
> > | data will be used. This specifically affects the verification of
> > | assertion that have been signed.
> > 
> > 
> > If you fix the vulnerability please also make sure to include the
> > CVE (Common Vulnerabilities & Exposures) id in your changelog entry.
> > 
> > For further information see:
> > 
> > [0] https://security-tracker.debian.org/tracker/CVE-2020-5390
> > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-5390
> > [1] 
> > https://github.com/IdentityPython/pysaml2/commit/5e9d5acbcd8ae45c4e736ac521fd2df5b1c62e25
> > 
> > Please adjust the affected versions in the BTS as needed.
> > 
> > Regards,
> > Salvatore
> > 
> 
> Hi Salvatore,
> 
> Please find attached the debdiff for fixing this CVE. I've already
> uploaded the fix to Sid. Please let me know if it's ok to upload to
> buster-security. BTW, are source-only uploads fine for security-master?

Ack. Let's fix this via security.debian.org, the debdiff looks fine. 
source-uploads
are fine, but please consider #869184 (and note that python-pysaml2 is new
in buster-security, so it needs a -sa upload as ftp.debian.org and 
security.debian.org
don't share tarballs.

stretch-security seems also affected, I'll prepare an update for it.

Cheers,
Moritz

Bug#950897: gopher FTCBFS: does not pass --host to ./configure

[Helmut Grohne]

Source: gopher
Version: 3.0.17.3
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

gopher fails to cross build from source, because it does not pass --host
to ./configure. The easiest way of doing so - using dh_auto_configure -
makes gopher cross buildable. Please consider applying the attached
patch.

Helmut
diff --minimal -Nru gopher-3.0.17.3/debian/changelog 
gopher-3.0.17.3+nmu1/debian/changelog
--- gopher-3.0.17.3/debian/changelog2019-10-11 18:09:18.0 +0200
+++ gopher-3.0.17.3+nmu1/debian/changelog   2020-02-07 17:10:55.0 
+0100
@@ -1,3 +1,10 @@
+gopher (3.0.17.3+nmu1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Let dh_auto_configure pass --host to ./configure. (Closes: #-1)
+
+ -- Helmut Grohne   Fri, 07 Feb 2020 17:10:55 +0100
+
 gopher (3.0.17.3) unstable; urgency=medium
 
   * Remove empty directories.  Closes: #942181.
diff --minimal -Nru gopher-3.0.17.3/debian/rules 
gopher-3.0.17.3+nmu1/debian/rules
--- gopher-3.0.17.3/debian/rules2019-10-11 18:09:07.0 +0200
+++ gopher-3.0.17.3+nmu1/debian/rules   2020-02-07 17:10:54.0 +0100
@@ -19,10 +19,7 @@
autoconf
autoheader
ln -vs /usr/share/gnulib/lib/getloadavg.c .
-   ./configure --prefix=/usr --mandir=\$${prefix}/share/man \
-   --infodir=\$${prefix}/share/info --disable-auth \
-   --sysconfdir=/etc
-
+   dh_auto_configure -- --disable-auth
touch configure-stamp
 
 build: build-stamp

Bug#950896: screen: out of bounds access when setting w_xtermosc after OSC 49

[Salvatore Bonaccorso]

Source: screen
Version: 4.7.0-1
Severity: important
Tags: security upstream fixed-upstream

Hi

There is a new upstream release 4.8.0 which fixes as well an out of
bounds access issue:

https://www.openwall.com/lists/oss-security/2020/02/06/3

Regards,
Salvatore

Bug#950895: freecad: autopkgtest fails on arm64 but not on amd64

[Lisandro Damián Nicanor Pérez Meyer]

Source: freecad
Version: 0.18.4+dfsg1-2
Severity: important

Hi! With the latest qtbase-opensource-src upload freecad's arm64 autopkgtests 
fail:



As you can see in the Pin-Packages column the tests also fail if only zlib is
changed. That alone would indicate that there is a problem with the test on
arm64.

Now with my Qt maintainer hat on: I sincerely doubt that the changes in the
latest Qt upload could be the issue for this, as the changes should not reflect
a change in the tests.

Of course please feel free to ping me if you need help on the Qt side.

Regards, Lisandro.

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

Kernel: Linux 5.4.0-3-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), 
LANGUAGE=es_AR:es (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#950894: mawk: numeric comparison on 'sub()' resulted ${n} vars does not work properly

[Stephen Dowdy]

Package: mawk
Version: 1.3.3-17+b3
Severity: normal

Dear Maintainer,

NOTE: this affects both 'mawk' and 'gawk' equally, so i'm not sure if this is 
some utterly esoteric behavior i'm just not "getting", but my expectations are 
definitely not being met.
(i also am unaware if a bug can be co-assigned to different packages)

Attempting to do a search for filesystems > 90% inode % or size % was giving 
anomolous results. (hair-pulling time)

I was using 'sub("%","",$1) to strip the % symbol off the results from:
df --output=ipcent,pcent,target /var /var/log
e.g.:
$ df --output=ipcent,pcent,target -t ext4  | mawk 
'NR>1{sub("%","",$1);sub("%","",$2); if (($1>30)||($2>30)) print}'
40 79 /
6 30 /var
1 7 /opt
20 78 /home
1 89 /d1
(clearly /opt doesn't meet the reporting criteria)

I narrowed this down to what appears to be a field-size truncation comparison 
issue with the result from the sub() against the comparison numeric on the 
right-side of the relop:

# The following all work as expected: (no output)
$ for i in $(seq 20 29); do echo "$i%" | mawk '{if (int($1)>100) print}'; done
$ for i in $(seq 20 29); do echo "$i%" | gawk '{if (int($1)>100) print}'; done
$ for i in $(seq 20 29); do echo "$i%" | mawk '{if (($1+0)>100) print}'; done
$ for i in $(seq 20 29); do echo "$i%" | gawk '{if (($1+0)>100) print}'; done

This does NOT work, though it should: (none of these values should print, they 
are all < 100, which is the comparison being made)
$ for i in $(seq 20 29); do echo "$i%" | mawk '{sub("%","",$1);if ($1>100) 
printf("[%s][%d]\n",$1,$1)}'; done
[20][20]
[21][21]
[22][22]
[23][23]
[24][24]
[25][25]
[26][26]
[27][27]
[28][28]
[29][29]

The man pages clearly state that a dual-type (numeric) variable SHOULD 
be implicitly cast to numeric if a comparison is against a numeric.

I also did this against a single digit input and a two-digit RHS value, and it 
shows the same issue, where only the same number of digits of the RHS that the 
input value contain are being compared.
$ for i in $(seq 0 20); do echo "$i%" | gawk '{sub("%","",$1);if ($1>40) 
printf("[%s][%d]\n",$1,$1)}'; done
[5][5]
[6][6]
[7][7]
[8][8]
[9][9]

Using an RHS of a float also fails:
$ for i in $(seq 0 20); do echo "$i%" | gawk '{sub("%","",$1);if ($1>40.0) 
printf("[%s][%d]\n",$1,$1)}'; done
[5][5]
[6][6]
[7][7]
[8][8]
[9][9]

I don't know how if there's a way to evaluate the internal data-type 
representation for $1 here, so i printed it with printf both as string and 
integer, and they report identical.

Thanks,
--stephen


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

Kernel: Linux 4.19.0-7-amd64 (SMP w/16 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

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

mawk recommends no packages.

mawk suggests no packages.

-- no debconf information

Bug#925251: stretch-pu: package file/1:5.30-1+deb9u2

[Salvatore Bonaccorso]

Hi,

On Tue, Aug 20, 2019 at 11:26:33PM +0100, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
> 
> On Thu, 2019-07-18 at 05:07 +0200, Christoph Biedl wrote:
> > Adam D. Barratt wrote...
> > 
> > > Assuming I count correctly, your mail was from approximately 6
> > > weeks
> > > before the date of the upcoming 9.9 point release.
> > 
> > This story has a tendency to fall off radar repeatedly. Perhaps we
> > can
> > eventually find a solution for this in the next days?
> 
> I guess we should just get on with it.
> 
> FWIW, we're currently about 2.5 weeks from the next point release. I
> realise that {c,sh}ould have been longer.

Is this still something it is worth to pursue and adress those two
CVEs pending for stretch or is the regression risk to high?

Regards,
Salvatore

Bug#834716: bundler: man-pages in wrong directory

[Utkarsh Gupta]

close 834716
thanks

On Thu, 18 Aug 2016 11:08:57 +0200 Paul van Tilburg  
wrote:

Package: bundler
Version: 1.12.5-3
Severity: normal

Dear Maintainer,

The man-pages are installed in the Ruby library directory,
as a result, they are unavailable to the user.
See the following partial file listing of ruby-bundler:

$ dpkg -L ruby-bundler | grep man
/usr/lib/ruby/vendor_ruby/bundler/man
/usr/lib/ruby/vendor_ruby/bundler/man/bundle
/usr/lib/ruby/vendor_ruby/bundler/man/bundle-config
/usr/lib/ruby/vendor_ruby/bundler/man/bundle-config.txt
/usr/lib/ruby/vendor_ruby/bundler/man/bundle-exec
/usr/lib/ruby/vendor_ruby/bundler/man/bundle-exec.txt
/usr/lib/ruby/vendor_ruby/bundler/man/bundle-gem
/usr/lib/ruby/vendor_ruby/bundler/man/bundle-gem.txt
/usr/lib/ruby/vendor_ruby/bundler/man/bundle-install
/usr/lib/ruby/vendor_ruby/bundler/man/bundle-install.txt
/usr/lib/ruby/vendor_ruby/bundler/man/bundle-lock
/usr/lib/ruby/vendor_ruby/bundler/man/bundle-lock.txt
/usr/lib/ruby/vendor_ruby/bundler/man/bundle-package
/usr/lib/ruby/vendor_ruby/bundler/man/bundle-package.txt
/usr/lib/ruby/vendor_ruby/bundler/man/bundle-platform
/usr/lib/ruby/vendor_ruby/bundler/man/bundle-platform.txt
/usr/lib/ruby/vendor_ruby/bundler/man/bundle-update
/usr/lib/ruby/vendor_ruby/bundler/man/bundle-update.txt
/usr/lib/ruby/vendor_ruby/bundler/man/bundle.txt
/usr/lib/ruby/vendor_ruby/bundler/man/gemfile.5
/usr/lib/ruby/vendor_ruby/bundler/man/gemfile.5.txt
[...]


This has been fixed already.

Please feel free to re-open if you think otherwise :)


Best,
Utkarsh

Bug#950892: kdenlive: please use the kf5 dh addon

[Pino Toscano]

Source: kdenlive
Version: 19.12.2-1
Severity: wishlist
Tags: patch

Hi,

kdenlive is a KF5-based application. While it builds fine as it is,
it is recommended to use the kf5 dh addon, as it takes care of few
things, e.g.:
- passing extra arguments to cmake
- excluding files from dh_compress
- and more

Hence, use the kf5 dh addon, and remove unneeded overrides.

Thanks,
-- 
Pino
--- a/debian/rules
+++ b/debian/rules
@@ -11,10 +11,10 @@ ifeq ($(DEB_BUILD_ARCH_OS),kfreebsd)
 endif
 
 %:
-   dh $@
+   dh $@ --with kf5
 
 override_dh_auto_configure:
-   dh_auto_configure -- $(EXTRAFLAGS)
+   dh_auto_configure -Skf5 -- $(EXTRAFLAGS)
 
 override_dh_install:
dh_install
@@ -22,8 +22,5 @@ override_dh_install:
 
 override_dh_auto_test:
 
-override_dh_compress:
-   dh_compress -X.docbook
-
 override_dh_gencontrol: l10npkgs_firstversion_ok
dh_gencontrol

Bug#950891: kdenlive: fix installation of appdata files

[Pino Toscano]

Source: kdenlive
Version: 19.12.2-1
Severity: normal
Tags: patch

Hi,

the appdata XML files are currently shipped in the kdenlive-data.
OTOH, they must be in the same package of the binary/artifact they
represent, so the kdenlive executable.

Hence, move them from kdenlive-data to kdenlive, with proper
breaks/replaces.

Thanks,
-- 
Pino
--- a/debian/kdenlive-data.install
+++ b/debian/kdenlive-data.install
@@ -3,7 +3,6 @@ usr/share/mime
 etc/xdg
 usr/share/kxmlgui5
 usr/share/kservices5
-usr/share/metainfo
 usr/share/knotifications5
 usr/share/kdenlive
 usr/share/config.kcfg
--- a/debian/kdenlive.install
+++ b/debian/kdenlive.install
@@ -2,3 +2,4 @@ usr/lib usr/
 usr/share/man
 usr/bin usr/
 usr/share/applications
+usr/share/metainfo
--- a/debian/control
+++ b/debian/control
@@ -70,6 +70,8 @@ Recommends: swh-plugins,
  dvdauthor,
  genisoimage
 Suggests: khelpcenter
+Breaks: kdenlive-data (<< 19.12.2-2~)
+Replaces: kdenlive-data (<< 19.12.2-2~)
 Description: non-linear video editor
  Kdenlive is a non-linear video editing suite, which supports DV, HDV and many
  more formats.

Bug#950889: debootstrap: chroot no longer builds with user-owned target dir

[Roberto C. Sanchez]

Package: debootstrap
Version: 1.0.114
Severity: normal

It seems that with the latest change to the systemd journaling
configuration, that chroots no longer build with a user-owned target
directory.

For example:

git clone https://salsa.debian.org/installer-team/debootstrap.git 
debootstrap.git
export DEBOOTSTRAP_DIR=`pwd`/debootstrap.git
mkdir unstable-chroot
sudo -E ./debootstrap.git/debootstrap unstable ./unstable-chroot/ 
http://mirrors.linode.com/debian

Ends with:

W: Failure trying to run: chroot "/home/roberto/unstable-chroot" dpkg 
--force-overwrite --forc
e-confold --skip-same-version --install 
/var/cache/apt/archives/libapparmor1_2.13.3-7_amd64.de
b /var/cache/apt/archives/libargon2-1_0~20171227-0.2_amd64.deb 
/var/cache/apt/archives/libcryp
tsetup12_2%3a2.2.2-3_amd64.deb 
/var/cache/apt/archives/libip4tc2_1.8.4-2_amd64.deb /var/cache/
apt/archives/libjson-c4_0.13.1+dfsg-6_amd64.deb 
/var/cache/apt/archives/libkmod2_26+20191223-1
_amd64.deb /var/cache/apt/archives/libcap2_1%3a2.27-1_amd64.deb 
/var/cache/apt/archives/dmsetu
p_2%3a1.02.167-1_amd64.deb 
/var/cache/apt/archives/libdevmapper1.02.1_2%3a1.02.167-1_amd64.deb
 /var/cache/apt/archives/libssl1.1_1.1.1d-2_amd64.deb 
/var/cache/apt/archives/systemd_244.1-3_
amd64.deb
W: See /home/roberto/unstable-chroot/debootstrap/debootstrap.log for details 
(possibly the pac
kage systemd is at fault)

The end of debootstrap.log, then contains:

Detected unsafe path transition / -> /var during canonicalization of 
/var/log/journal.
Detected unsafe path transition / -> /var during canonicalization of 
/var/log/journal.
Detected unsafe path transition / -> /var during canonicalization of 
/var/log/journal.
Detected unsafe path transition / -> /var during canonicalization of 
/var/log/journal.
dpkg: error processing package systemd (--install):
 installed systemd package post-installation script subprocess returned error 
exit status 73
Processing triggers for libc-bin (2.29-9) ...
Errors were encountered while processing:
 systemd

However, prefixing the 'mkdir' command with 'sudo' or simply choosing to
let debootstrap create the directory results in a successful chroot
creation.

Perhaps debootstrap should give a meaningful/helpful error message if
the user attempts to create a chroot into a target directory that is not
owned by root (or that has whatever attributes seem to be upsetting
systemd here).

Regards,

-Roberto

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

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

Versions of packages debootstrap depends on:
ii  wget  1.20.1-1.1

Versions of packages debootstrap recommends:
pn  arch-test   
ii  debian-archive-keyring  2019.1
ii  gnupg   2.2.12-1+deb10u1

Versions of packages debootstrap suggests:
pn  squid-deb-proxy-client  
pn  ubuntu-archive-keyring  

-- no debconf information


signature.asc
Description: PGP signature

Bug#950890: xserver-xorg-core: X segfaults when displaying a big image with xzgv

[Frédéric Brière]

Package: xserver-xorg-core
Version: 2:1.20.7-2
Severity: important

I can (reliably) get X to segfault when displaying a big image (say,
over 1x1) with xzgv.  And since that viewer allows doubling the
scale of an image with a single keystroke, this can easily be triggered
with any image (which is how I accidentally ran into it in the first
place).

Steps to reproduce:

  - View any image (the bigger the better) with xzgv
  - Repeatedly press "d" until the server segfaults

The error message is identical to #912325, although I am using the
radeon driver:

  [ 94509.215] (EE) glamor0: GL error: GL_OUT_OF_MEMORY in glBufferData
  [ 94509.215] (EE) glamor0: GL error: GL_INVALID_OPERATION in glReadPixels(out 
of bounds PBO access)
  [ 94509.215] (EE) glamor0: GL error: GL_INVALID_OPERATION in 
glMapBuffer(length = 0)

This was encountered with 2:1.20.7-2, and confirmed to be still present
in -3.

Full log and backtrace with symbols are attached.  Let me know if there
is anything else I can do to help.  Thanks!


-- Package-specific info:
X server symlink status:

lrwxrwxrwx 1 root root 13 Dec 21  2010 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 274 Feb  5 11:27 /usr/bin/Xorg

VGA-compatible devices on PCI bus:
--
01:05.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] RS880 [Radeon HD 4250] [1002:9715]

/etc/X11/xorg.conf does not exist.

Contents of /etc/X11/xorg.conf.d:
-
total 4
-rw-r--r-- 1 root root 57 Sep  6  2015 debug.conf

KMS configuration files:

/etc/modprobe.d/radeon-kms.conf:
  options radeon modeset=1

Kernel version (/proc/version):
---
Linux version 4.9.0-11-amd64 (debian-ker...@lists.debian.org) (gcc version 
6.3.0 20170516 (Debian 6.3.0-18+deb9u1) ) #1 SMP Debian 4.9.189-3+deb9u2 
(2019-11-11)

Xorg X server log files on system:
--
-rw-r--r-- 1 fbriere fbriere  26405 Feb 19  2016 
/home/fbriere/.local/share/xorg/Xorg.2.log
-rw-r--r-- 1 rootroot779168 Dec 23  2018 /var/log/Xorg.3.log
-rw-r--r-- 1 rootroot515287 Dec 23  2018 /var/log/Xorg.2.log
-rw-r--r-- 1 rootroot 45230 Jan 13  2019 /var/log/Xorg.4.log
-rw-r--r-- 1 rootroot 82916 Feb  7 14:02 /var/log/Xorg.1.log
-rw-r--r-- 1 rootroot 38765 Feb  7 14:05 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[79.258] 
X.Org X Server 1.20.7
X Protocol Version 11, Revision 0
[79.258] Build Operating System: Linux 4.19.0-6-amd64 x86_64 Debian
[79.258] Current Operating System: Linux fabul 4.9.0-11-amd64 #1 SMP Debian 
4.9.189-3+deb9u2 (2019-11-11) x86_64
[79.259] Kernel command line: BOOT_IMAGE=/vmlinuz-4.9.0-11-amd64 
root=/dev/mapper/root ro vsyscall=emulate
[79.259] Build Date: 05 February 2020  04:27:36PM
[79.259] xorg-server 2:1.20.7-3 (https://www.debian.org/support) 
[79.259] Current version of pixman: 0.36.0
[79.259]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[79.259] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[79.260] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Feb  7 14:05:33 
2020
[79.261] (==) Using config directory: "/etc/X11/xorg.conf.d"
[79.262] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[79.264] (==) No Layout section.  Using the first Screen section.
[79.264] (==) No screen section available. Using defaults.
[79.264] (**) |-->Screen "Default Screen Section" (0)
[79.264] (**) |   |-->Monitor ""
[79.266] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[79.266] (**) Option "NoTrapSignals"
[79.266] (==) Automatically adding devices
[79.266] (==) Automatically enabling devices
[79.266] (==) Automatically adding GPU devices
[79.266] (==) Max clients allowed: 256, resource mask: 0x1f
[79.268] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[79.268]Entry deleted from font path.
[79.275] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[79.275] (==) ModulePath set to "/usr/lib/xorg/modules"
[79.275] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[79.275] (II) Loader magic: 0x560e44cbbe40
[79.275] (II) Module 

Bug#950760: RFS: libbpf/0.0.6-1 -- eBPF helper library (development files)

[Sudip Mukherjee]

On Fri, Feb 7, 2020 at 10:17 AM Sudip Mukherjee
 wrote:
>
> On Thu, Feb 6, 2020 at 10:53 PM Christian Barcenas
>  wrote:
> >
> > I just noticed that your packaging repo is currently empty.
> > Would you be able to push your current progress to Github
> > so that it's easier to review the source package?
>
> Pushed now. Its without any epoch in the version. I will add the epoch
> and push again tonight after back from $dayjob.

Also pushed in wip/epoch branch with the epoch in only binary packages
for your review. I have not yet uploaded to mentors.

-- 
Regards
Sudip

Bug#950873: libwireshark-dev: Missing a header file required by present header

[Balint Reczey]

Control: merge  950871 -1
Control: tags -1 confirmed pending

On Fri, Feb 7, 2020 at 4:51 PM Thorsten Schulz
 wrote:
>
> Package: libwireshark-dev
> Version: 3.2.1-1
> Severity: normal
>
> Dear Maintainer,
>
> While trying to build an external dissector, I am including 
> . (FYI: 
> https://github.com/T12z/TCNopen/tree/master/trdp/spy/src/trdp_spy -- I am 
> working on adding deb-packaging ;) )
> However, the included epan/plugin_if.h itself includes , which is 
> not packaged by any non-source package. Thus, compilation is impossible w/o 
> pulling the full source of wireshark.
>
> It would be nice for easy packaging, to have that dependent header cfile.h 
> included in some *-dev package.

Thanks, will be fixed in next upload.

Cheers,
Balint

--
Balint Reczey
Ubuntu & Debian Developer

Bug#950885: RFS: scons-doc/3.1.2+repack-2 -- Documentation for SCons, a replacement for Make

[Adam Borowski]

On Fri, Feb 07, 2020 at 07:16:07PM +0100, Jörg Frings-Fürst wrote:
>Package name: scons-doc
>Version : 3.1.2+repack-2

> Changes since the last upload:
> 
>* debian/watch: Add repacksuffix.
>* debian/copyright:
>  - Add year 2020 to debian/*.
>* Declare compliance with Debian Policy 4.5.0 (No changes needed).
>* upload to unstable (Closes: #943200).

Alas, it fails at the "clean" stage:

dh clean
   debian/rules override_dh_auto_clean
make[1]: Entering directory '/<>'
scons -c
*** Error loading site_init file './site_scons/site_init.py':
*** cannot import site init file './site_scons/site_init.py':
ModuleNotFoundError: No module named 'distutils.util':
  File "/usr/lib/scons/SCons/Script/Main.py", line 1396:
_exec_main(parser, values)
  File "/usr/lib/scons/SCons/Script/Main.py", line 1359:
_main(parser)
  File "/usr/lib/scons/SCons/Script/Main.py", line 971:
_load_all_site_scons_dirs(d.get_internal_path())
  File "/usr/lib/scons/SCons/Script/Main.py", line 817:
_load_site_scons_dir(d)
  File "/usr/lib/scons/SCons/Script/Main.py", line 751:
exec(compile(fp.read(), fp.name, 'exec'), site_m)
  File "./site_scons/site_init.py", line 2:
from Utilities import is_windows, whereis, platform, deb_date
  File "/<>/site_scons/Utilities.py", line 4:
import distutils.util
make[1]: *** [debian/rules:7: override_dh_auto_clean] Error 2


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ The ill-thought conversion to time64_t will make us suffer from
⣾⠁⢠⠒⠀⣿⡁ the Y292B problem.  So let's move the Epoch by 43545140006400
⢿⡄⠘⠷⠚⠋⠀ (plus a safety margin in case of bad physicists) and make it
⠈⠳⣄ unsigned -- that'll almost double the range.

Bug#851639: ITP: alacritty -- A cross-platform, GPU-accelerated terminal emulator

[Félix Sipma]

Hi Johan,

Debian Rust team uses debcargo to package rust crates. As far as I know, it 
needs the crates to be on crates.io. See the README.md on 
https://salsa.debian.org/rust-team/debcargo/


Regards,

--
Félix


signature.asc
Description: PGP signature

Bug#950888: lots of entries in vmware-vmsvc-root.log "[ warning] [guestinfo] GuestInfoGetDiskDevice: Missing disk device name;

[Oliver Kurth]

Package: open-vm-tools
Version: 2:11.0.5-1

When using the LSI Logic Parallel SCSI controller lots of log messages are 
generated. These are benign but may fill up logs quickly. We are working on 
fixing the root cause.

This was first reported at SuSE, see 
https://bugzilla.suse.com/show_bug.cgi?id=1162435 and also on github: 
https://github.com/vmware/open-vm-tools/issues/404 . We have a patch that 
degrades the warning messages to debug messages in 
https://github.com/vmware/open-vm-tools/commits/stable-11.0.5-suse-bug-1162435 .

Thanks,
Oliver

Bug#950887: satpy: autopkgtest failures

[Bas Couwenberg]

Source: satpy
Version: 0.19.1-1
Severity: serious
Justification: makes the package in question unusable or mostly so

Dear Maintainer,

With python-xarray (0.15.0-2) the autopkgtest of satpy still fail:

 ==
 ERROR: test_aggregate (satpy.tests.test_scene.TestScene)
 Test the aggregate method.
 --
 Traceback (most recent call last):
   File "/usr/lib/python3/dist-packages/satpy/tests/test_scene.py", line 543, 
in test_aggregate
 scene2 = scene1.aggregate(func='sum', x=2, y=2)
   File "/usr/lib/python3/dist-packages/satpy/scene.py", line 668, in aggregate
 res = self[ds_id].coarsen(boundary=boundary, side=side, func=func, 
**dim_kwargs)
   File "/usr/lib/python3/dist-packages/xarray/core/common.py", line 908, in 
coarsen
 return self._coarsen_cls(
   File "/usr/lib/python3/dist-packages/xarray/core/rolling.py", line 547, in 
__init__
 raise ValueError(
 ValueError: Dimensions ['func'] not found in DataArray.
 
 ==
 FAIL: test_basic_default_not_provided 
(satpy.tests.compositor_tests.TestSunZenithCorrector)
 Test default limits when SZA isn't provided.
 --
 Traceback (most recent call last):
   File 
"/usr/lib/python3/dist-packages/satpy/tests/compositor_tests/__init__.py", line 
271, in test_basic_default_not_provided
 self.assertNotIn('y', res.coords)
 AssertionError: 'y' unexpectedly found in Coordinates:
   * y(y) int64 0 1
   * x(x) int64 0 1
 
 --
 Ran 658 tests in 83.901s
 
 FAILED (failures=1, errors=1, skipped=6)

https://ci.debian.net/data/autopkgtest/testing/amd64/s/satpy/4225105/log.gz

Kind Regards,

Bas

Bug#950609: systemd: backlight service messes with screen brightness

[Valerio Passini]

Hi Michael,

Il Ven 7 Feb 2020, 19:05 Michael Biebl  ha scritto:

> Control: tags -1 = moreinfo
>
> What exactly was not working? What did you do, what did you expect, what
> did (not) happen.
>

Screen brightness controls (the two keyboard buttons designed to tune
brightness and the sliders in GNOME and KDE) are ineffective. If I press
the buttons or I move the slider, the OSD shows that brightness is changing
while actually it's not. I expect that brightness is being regulated by my
actions.

systemd-backlight@.service simply stores the current backlight value on
> shutdown and restores it on boot.
> It reads from /sys/class/backlight/*/brightness and writes accordingly.
> If that somehow confuses the hardware, this smells like a driver/kernel
> issue.
>
> Michael
>

I know that it seems unrelated to systemd-backlight, that service should
store and restore brightness through reboots, but here:
https://devtalk.nvidia.com/default/topic/1061387/linux/screen-brightness-resets-to-max-after-reboot-linux-/
I have found that systemd-backlight is keeping brightness to maximum and so
I tried to disable it just to see if my problem would be fixed, and so it
is.
The real culprit might be something else as you said previously, but at the
moment it is a decent workaround for me and it might be worth investigating
it further.

Tell me if you need more info. Best regards

Valerio

Bug#946145: isbg tests are failing

[Louis-Philippe Véronneau]

forwarded 946145 https://gitlab.com/isbg/isbg/issues/144
thanks

Thanks for reporting this. I opened a bug upstream a while ago, but
forgot to create one here.

It seems the testsuite behaves differently when spamassassin is
installed then when it's not.

I'll try to work on this soonish.

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄



signature.asc
Description: OpenPGP digital signature

Bug#947758: buster-pu: package node-handlebars/3:4.1.0-1+deb10u1

[Adam D. Barratt]

On Sat, 2020-01-25 at 20:40 +, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
> 
> On Mon, 2019-12-30 at 07:51 +0100, Xavier Guimard wrote:
> > node-handlebars is vulnearable to prototype pollution (CVE-2019-
> > 19919).
> > 
> 
> Please go ahead.

This apparently causes regressions in the autopkgtests of node-
markdown-it-html5-embed, which you also most recently uploaded - see 
https://ci.debian.net/user/britney/jobs?package=node-markdown-it-html5-embed[]=stable[]=amd64

Is this enough of an issue to not include the node-handlebars update?

Regards,

Adam

Bug#922587: FTBFS against opencv 4.0.1 (exp)

[Ying-Chun Liu (PaulLiu)]

Hi all,


OK. I made a patch to address this issue. Will upload the patch soon.


Yours,
Paul


Description: Porting to OpenCV4
 We need to port to OpenCV4 because Debian is now using OpenCV4
Author: Ying-Chun Liu (PaulLiu) 
Bug-Debian: https://bugs.debian.org/922587
Last-Update: 2020-02-07

Index: node-opencv-6.0.0+git20180416.cfc96ba0/utils/find-opencv.js
===
--- node-opencv-6.0.0+git20180416.cfc96ba0.orig/utils/find-opencv.js
+++ node-opencv-6.0.0+git20180416.cfc96ba0/utils/find-opencv.js
@@ -16,6 +16,7 @@ var flag = flags[process.argv[2]] || '--
 // the same machine, the opencv.pc for 3.y can be installed as opencv3.pc and
 // then selected by |export PKG_CONFIG_OPENCV3=1| before building node-opencv.
 var opencv = process.env.PKG_CONFIG_OPENCV3 === "1" ? "opencv3" : ' "opencv >= 2.3.1"';
+opencv = process.env.PKG_CONFIG_OPENCV4 === "1" ? "opencv4" : opencv;
 
 function main(){
 //Try using pkg-config, but if it fails and it is on Windows, try the fallback
Index: node-opencv-6.0.0+git20180416.cfc96ba0/src/OpenCV.h
===
--- node-opencv-6.0.0+git20180416.cfc96ba0.orig/src/OpenCV.h
+++ node-opencv-6.0.0+git20180416.cfc96ba0/src/OpenCV.h
@@ -24,6 +24,8 @@
 
 #if ((CV_MAJOR_VERSION <= 2) && (CV_MINOR_VERSION <= 4) && (CV_MINOR_VERSION < 10))
 #include 
+#elif CV_MAJOR_VERSION >= 4
+#include 
 #else
 #include 
 #endif
Index: node-opencv-6.0.0+git20180416.cfc96ba0/src/Point.h
===
--- node-opencv-6.0.0+git20180416.cfc96ba0.orig/src/Point.h
+++ node-opencv-6.0.0+git20180416.cfc96ba0/src/Point.h
@@ -1,6 +1,7 @@
 // Template class for 2D points
 
 #include "OpenCV.h"
+#include 
 
 class Point: public Nan::ObjectWrap {
 public:
Index: node-opencv-6.0.0+git20180416.cfc96ba0/src/Matrix.cc
===
--- node-opencv-6.0.0+git20180416.cfc96ba0.orig/src/Matrix.cc
+++ node-opencv-6.0.0+git20180416.cfc96ba0/src/Matrix.cc
@@ -3,6 +3,9 @@
 #include "OpenCV.h"
 #include 
 #include 
+#include 
+#include 
+
 
 Nan::Persistent Matrix::constructor;
 
@@ -1608,7 +1611,9 @@ NAN_METHOD(Matrix::Canny) {
   int lowThresh = info[0]->NumberValue();
   int highThresh = info[1]->NumberValue();
 
-  cv::Canny(self->mat, self->mat, lowThresh, highThresh);
+  cv::Mat newMat;
+  cv::Canny(self->mat, newMat, lowThresh, highThresh);
+  newMat.copyTo(self->mat);
 
   info.GetReturnValue().Set(Nan::Null());
 }
Index: node-opencv-6.0.0+git20180416.cfc96ba0/src/CascadeClassifierWrap.cc
===
--- node-opencv-6.0.0+git20180416.cfc96ba0.orig/src/CascadeClassifierWrap.cc
+++ node-opencv-6.0.0+git20180416.cfc96ba0/src/CascadeClassifierWrap.cc
@@ -2,6 +2,7 @@
 #include "OpenCV.h"
 #include "Matrix.h"
 #include 
+#include 
 
 #ifdef HAVE_OPENCV_OBJDETECT
 
@@ -73,7 +74,7 @@ public:
 gray = this->im->mat;
   }
   this->cc->cc.detectMultiScale(gray, objects, this->scale, this->neighbors,
-  0 | CV_HAAR_SCALE_IMAGE, cv::Size(this->minw, this->minh));
+  0 | cv::CASCADE_SCALE_IMAGE, cv::Size(this->minw, this->minh));
   res = objects;
 } catch (cv::Exception& e) {
   SetErrorMessage(e.what());
Index: node-opencv-6.0.0+git20180416.cfc96ba0/src/VideoCaptureWrap.cc
===
--- node-opencv-6.0.0+git20180416.cfc96ba0.orig/src/VideoCaptureWrap.cc
+++ node-opencv-6.0.0+git20180416.cfc96ba0/src/VideoCaptureWrap.cc
@@ -3,6 +3,7 @@
 #include "OpenCV.h"
 
 #include  
+#include 
 
 #ifdef HAVE_OPENCV_VIDEOIO
 
Index: node-opencv-6.0.0+git20180416.cfc96ba0/src/VideoWriterWrap.cc
===
--- node-opencv-6.0.0+git20180416.cfc96ba0.orig/src/VideoWriterWrap.cc
+++ node-opencv-6.0.0+git20180416.cfc96ba0/src/VideoWriterWrap.cc
@@ -1,6 +1,7 @@
 #include "VideoWriterWrap.h"
 #include "Matrix.h"
 #include "OpenCV.h"
+#include 
 
 #include  
 
Index: node-opencv-6.0.0+git20180416.cfc96ba0/src/CamShift.cc
===
--- node-opencv-6.0.0+git20180416.cfc96ba0.orig/src/CamShift.cc
+++ node-opencv-6.0.0+git20180416.cfc96ba0/src/CamShift.cc
@@ -8,6 +8,8 @@
 #include 
 #endif
 
+#include 
+
 #define CHANNEL_HUE 0
 #define CHANNEL_SATURATION 1
 #define CHANNEL_VALUE 2
Index: node-opencv-6.0.0+git20180416.cfc96ba0/src/FaceRecognizer.cc
===
--- node-opencv-6.0.0+git20180416.cfc96ba0.orig/src/FaceRecognizer.cc
+++ node-opencv-6.0.0+git20180416.cfc96ba0/src/FaceRecognizer.cc
@@ -4,9 +4,9 @@
 #include "FaceRecognizer.h"
 #include "Matrix.h"
 #include 
+#include 
 
-#if CV_MAJOR_VERSION < 3
-#elif CV_MINOR_VERSION < 3
+#if CV_MAJOR_VERSION < 3 || (CV_MAJOR_VERSION == 3 && CV_MINOR_VERSION < 3)
 namespace 

Bug#950886: libruby2.5: Fails with "version `XCRYPT_2.0' not found"

[Henrik Lundberg]

Package: libruby2.5
Version: 2.5.7-1+b1
Severity: important

Dear Maintainer,

Running ruby or any application invoking ruby results in the following
error message and aborts.

/lib/x86_64-linux-gnu/libcrypt.so.1: version `XCRYPT_2.0' not found
(required by /usr/lib/x86_64-linux-gnu/libruby-2.5.so.2.5)

If I downgrade to 2.5.5-3+deb10u1 the issue is gone.

I'd be happy to provide you with further information about the local
environment.

KR
/Henrik

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

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

Versions of packages libruby2.5 depends on:
ii  libc6  2.29-9
ii  libcrypt1  1:4.4.10-10
ii  libffi73.3-3
ii  libgdbm-compat41.18.1-5
ii  libgdbm6   1.18.1-5
ii  libgmp10   2:6.1.2+dfsg-4
ii  libreadline8   8.0-3
ii  libssl1.1  1.1.1d-2
ii  libyaml-0-20.2.2-1
ii  rake   12.3.3-1
ii  ruby-did-you-mean  1.2.1-1
ii  ruby-minitest  5.13.0-1
ii  ruby-net-telnet0.1.1-2
ii  ruby-test-unit 3.3.4-1
ii  ruby-xmlrpc0.3.0-2
ii  zlib1g 1:1.2.11.dfsg-1+b1

libruby2.5 recommends no packages.

libruby2.5 suggests no packages.

-- no debconf information

Bug#949751: debian-installer does not create efiboot record

[Steve McIntyre]

Hi again,

Please accept my apologies for the very long delay in responding to
you. I've had a really busy time with 3 back-to-back conferences and
I'm just catching up on mail now. :-/

On Mon, Jan 27, 2020 at 06:21:32PM +0200, Leonid Khorolets wrote:
>сб, 25 січ. 2020 о 17:03 Steve McIntyre  пише:
>>
>> Hi Leonid,
>>
>> On Sat, Jan 25, 2020 at 03:55:45PM +0200, Leonid Khorolets wrote:
>> >пʼятниця, 24 січня 2020 р. Steve McIntyre  пише:
>> >
>> >OK, that's odd. This normally works fine for other people. Can you
>> >tell me a little more about your system please? Do you have logs from
>> >the installation still? Did the installer report problems?
>> >
>> >i can reinstall this is vm(gen-2) at hyper-v .
>> >
>> >no errors during installation.
>> >
>> >could you tell me where can i find installation logs?
>>
>> After the installation is complete and you have reinstalled, the logs
>> should be in /var/log/installer. The main useful file there is the syslog.
>
>find next strange logs at /var/log/installer/syslog:
>"Jan 27 15:54:47 grub-installer: info: Installing grub on 'dummy'
>Jan 27 15:54:47 grub-installer: info: grub-install does not support --no-floppy
>Jan 27 15:54:47 grub-installer: info: Running chroot /target
>grub-install  --force "dummy"
>Jan 27 15:54:47 grub-installer: Installing for x86_64-efi platform.
>Jan 27 15:54:50 grub-installer: grub-install: warning:
>vars_get_variable:
>open(/sys/firmware/efi/vars/blk0-47c7b225-c42a-11d2-8e57-00a0c969723b/raw_var,
>O_RDONLY) failed: No such file or directory.
>Jan 27 15:54:50 grub-installer: grub-install: warning:
>efi_get_variable: ops->get_variable failed: No such file or directory.
>Jan 27 15:54:50 grub-installer: grub-install: warning: device_get:
>Cannot parse device link segment "h^A@<9C> <94>f
><90>`RF09hn^[^D<82>E^GK
><95>E:+^P<87>sR\ء?^CV^P<94>ڠ<95>c<9C>A+^SfL
>Jan 27 15:54:50 grub-installer:
>C^?q{3,ԃϪ^A<8A>,B}<8F>ϗ0T^Lm_
>": Success.
>Jan 27 15:54:50 grub-installer: grub-install: warning:
>efi_va_generate_file_device_path_from_esp: could not get ESP disk
>info: Success.
>Jan 27 15:54:50 grub-installer: grub-install: warning:
>efi_generate_file_device_path_from_esp: could not generate File DP
>from ESP: Success.
>Jan 27 15:54:50 grub-installer: Installation finished. No error reported.
>Jan 27 15:54:50 grub-installer: info: grub-install ran successfully
>"

OK, these are error messages from Colin's new grub-install code. He
might be able to help some more with that. I've added him in CC so
he's aware of the problem here.

>I tested debian9 installation - all ok. In /var/log/installer/syslog
>the command "grub-install --force dummy" was runned without errors:
>Jan 27 10:55:15 grub-installer: info: Installing grub on 'dummy'
>Jan 27 10:55:15 grub-installer: info: grub-install does not support --no-floppy
>Jan 27 10:55:15 grub-installer: info: Running chroot /target
>grub-install  --force "dummy"
>Jan 27 10:55:15 grub-installer: Installing for x86_64-efi platform.
>Jan 27 10:55:19 grub-installer: Installation finished. No error reported.
>Jan 27 10:55:19 grub-installer: info: grub-install ran successfully

ACK. Debian 9 used a different code path here, and that clearly
behaved differently on your setup. Thanks for the extra information -
that could be really useful.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"C++ ate my sanity" -- Jon Rabone

Bug#784688: Bank Director

[westernuniondirecto...@gmail.com]

Bug#950885: RFS: scons-doc/3.1.2+repack-2 -- Documentation for SCons, a replacement for Make

[Jörg Frings-Fürst]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "scons-doc"

   Package name: scons-doc
   Version : 3.1.2+repack-2
   Upstream Author : Steven Knight 
   URL : https://www.scons.org/
   License : Expat
   Vcs : https://salsa.debian.org/debian/scons-doc
   Section : doc

It builds those binary packages:

  scons-doc - Documentation for SCons, a replacement for Make

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

  https://mentors.debian.net/package/scons-doc

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

 dget -x 
https://mentors.debian.net/debian/pool/main/s/scons-doc/scons-doc_3.1.2+repack-2.dsc

or from git 

 https://salsa.debian.org/debian/scons-doc/tree/release/debian/3.1.2+repack-2


Changes since the last upload:

   * debian/watch: Add repacksuffix.
   * debian/copyright:
 - Add year 2020 to debian/*.
   * Declare compliance with Debian Policy 4.5.0 (No changes needed).
   * upload to unstable (Closes: #943200).

CU
Jörg Frings-Fürst

-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser


git:  https://jff.email/cgit/

Threema:  SYR8SJXB
Wire: @joergfringsfuerst
Skype:joergpenguin
Ring: jff
Telegram: @joergfringsfuerst


My wish list: 
 - Please send me a picture from the nature at your home.



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

Bug#950824: RFS: sayonara/1.5.2-beta3~1 -- Small and lightweight music player

[Boyuan Yang]

Hi,

在 2020-02-07五的 11:14 +0630，Ko Ko Ye`写道：
> I am looking for a sponsor for my package "sayonara"
> 
> Sayonara is a small, clear and fast audio player for Linux written in C++,
> supported by the Qt framework. 
> It uses GStreamer as audio backend. Sayonara is open source and uses the
> GPLv3 license. 
> more at https://sayonara-player.com [1], 
> https://gitlab.com/luciocarreras/sayonara-player [2]

Could you fix those lintian errors?

E: sayonara: \embedded-library\ usr/bin/sayonara: taglib
E: sayonara: \python-script-but-no-python-dep\ usr/bin/sayonara-ctl #!python3
E: sayonara: \python-script-but-no-python-dep\ usr/bin/sayonara-query
#!python3

Besides, the version string is also buggy.
  * The debian revision should be -1 and never be ~1.
  * If upstream is releasing a beta version with version string as "1.5.2-
beta3", you should consider mangling it back to "1.5.2~beta3" since "1.5.2-"
is considered a higher version than "1.5.2" in Debian.

Final result should be "1.5.2~beta3-1". Plese read deb-version(5) man page for
information about Debian's versioning.

Another thing is that you should drop historical changelog entries in
debian/changelog. They are useless in Debian.

-- 
Thanks,
Boyuan Yang


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

Bug#950684: systemd: upgrade fails in a chroot where /var/log/ owner is not root:root

[Michael Biebl]

Am 05.02.20 um 18:26 schrieb Andrey Rahmatullin:
> On Wed, Feb 05, 2020 at 06:15:34PM +0100, Michael Biebl wrote:
>> Now, the question: How should systemd postinst behave in this case?
> I think failing is fine. I'd ask the sbuild maintainers what do they think
> about this situation, and why such chroots exist (and/or maybe ask some
> other people if theis chroots have the same perms).

I asked Johannes. He is not aware or remembers any such issue.

My proposal would be to keep this bug report open for a while. If we
have other users running into this issue and commenting on this bug
report, we might consider looking for a workaround.
Otherwise I'll probably just going to keep the current status quo.

Michael



signature.asc
Description: OpenPGP digital signature

Bug#950822: systemd-sysusers hangs if nis is enabled in a systemd-nspawn container

[Michael Biebl]

Am 07.02.20 um 08:14 schrieb Ryutaroh Matsumoto:
>> Do you have nscd installed inside the container (looking at the strace
>> it appears you might have not).
> 
> I installed "unscd" instead of "nscd", as "unscd" is said to be less buggy.
> 
>> Is nscd installed outside of the container where you don't see the problem?
> 
> The host running container also uses "unscd".
> Its log is as below. Interestingly, I do not find TCP communication to
> the Sun RPC port 111... Why???

Last time I used NIS was 15 years ago, so I doubt I can really help you
with answering any NIS related questions.




signature.asc
Description: OpenPGP digital signature

Bug#950609: systemd: backlight service messes with screen brightness

[Michael Biebl]

Control: tags -1 = moreinfo

On Tue, 04 Feb 2020 09:26:58 +0100 Valerio Passini
 wrote:
> Package: systemd
> Version: 244.1-2
> Severity: normal
> Tags: patch
> 
> Dear Maintainer,
> 
> Brightness controls on keyboard (and any other mean except xrandr) have not 
> been working reliably since the day I installed Debian on my laptop: sometime 
> it was possible to tune brightness after a fresh boot, sometime only after a 
> S2R and resume.

What exactly was not working? What did you do, what did you expect, what
did (not) happen.

> Trying to find a solution, I have discovered that masking the backlight 
> service fixes the problem:
> 
> sudo systemctl mask systemd-backlight@backlight:nvidia_0.service
> 
> I have double checked that enabling the service again restores the issue.
> The relevant information on my system are:
> Laptop model: HP Omen 15-dh0002nl, GPU Nvidia
> Software: Debian/Unstable Xorg Nvidia proprietary drivers (don't mind about my
> custom kernel, the issue is the same with Debian stock kernel)
> 

systemd-backlight@.service simply stores the current backlight value on
shutdown and restores it on boot.
It reads from /sys/class/backlight/*/brightness and writes accordingly.
If that somehow confuses the hardware, this smells like a driver/kernel
issue.

Michael



signature.asc
Description: OpenPGP digital signature

Bug#950072: python-asttokens FTBFS with Python 3.8 as supported version

[Boyuan Yang]

X-Debbugs-CC: di...@moreda.io naturesha...@debian.org
Control: tags -1 + pending

On Wed, 29 Jan 2020 13:43:52 +0100 "Diego M. Rodriguez" 
wrote:
> It seems the issues were also identified upstream and fixed (via [1] and
> other 3.8-related commits), and made it into a new upstream release
> (the 2.x line [2]) - I have updated the VCS preparing the new version.
> 
> [1] https://github.com/gristlabs/asttokens/pull/36
> [2] https://github.com/gristlabs/asttokens/releases

This one looks good to me. I am looking into uploading this version onto
DELAYED/7 first.

The only reverse-dependencies are src:eric and src:thonny. I am listed as the
maintainer of src:eric and will take care of this; for src:thonny, 
https://bugs.debian.org/950884 has been filed and the package won't be broken
as long as its new upstream release is packaged in Debian.

-- 
Thanks,
Boyuan Yang


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

Bug#947744: installation-reports: Debian Live Testing LXQt + nonfree - install fails with: "Bad unsquash configuration" Date: Wed, 1 Jan 2020 04:54:06 +0000 (UTC)

[Steve McIntyre]

Hi Scott,

On Fri, Feb 07, 2020 at 02:47:56AM +, scott092...@aol.com wrote:
>>What media are you using for the image, out of curiosity?
>16GB PNY USB 2.0 Flash drive ("Attache 4"), in a USB 3.0 hub in a USB 3.0 port.
>
>Installed with mkusb 12.3.9-1ubuntu1 with persistence
>(I've had very good results getting bootable USB drives with mkusb).
>
>Are you thinking that there may be some sort of media flaw in the drive?

It's *possible*, yes.. It's also possible that mkusb is doing
something odd that's causing problems with the filesystem. I'm
wondering exactly what the effect of "with persistence" is, for
example. Could you try again without that and see if that makes a
difference for you, please?

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
Can't keep my eyes from the circling sky,
Tongue-tied & twisted, Just an earth-bound misfit, I...

Bug#950884: thonny: Please package new upstream version 3.2.7 (for python3.8 compatiblity)

[Boyuan Yang]

Source: thonny
Version: 3.2.1-1
Severity: important
X-Debbugs-CC: naturesha...@debian.org aivar.anna...@gmail.com

Dear thonny maintainers,

When trying to solve https://bugs.debian.org/950072 in package python-
asttokens, I found that the compatibility of asttokens was fixed in a new
upstream release that made a backward-incompatible change. Fortunately the
thonny upstream has already made updates in a new upstream version considering
this. Please package the new thonny upstream version to ensure that the
python3.8 compatibility issue is kept and that no package is broken due to the
version bump.

-- 
Thanks,
Boyuan Yang


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

Bug#950883: ITP: ruby-thwait -- watches for termination of multiple threads

[Balasankar "Balu" C]

Package: wnpp
Owner: "Balasankar \"Balu\" C" 
Severity: wishlist
Usertags: ruby2.7-transition

* Package name: ruby-thwait
  Version : 0.1.0
  Upstream Author : Keiju ISHITSUKA 
* URL : https://github.com/ruby/thwait
* License : BSD-2-Clause
  Programming Lang: Ruby
  Description : watches for termination of multiple threads

Provides thwait, which was split off from Ruby core in Ruby 2.7.
Required for making ruby-innertube support Ruby 2.7

Bug#950881: patch v2

[Jean-Michel Nirgal Vourgère]

Hi

The awk patch above set the uppercase version of the fingerprint $1 in $2 
before continuing. This is wrong. Attached is a better version.

Note that GPG always print fingerprints in uppercase, so that  
"$1=toupper($1);" could simply be removed ...

-- 
- - Nirgal Vourgère ☮ GP France
-   xmpp:nir...@nirgal.com ☮ gpg 0x5405aef07c52c135
Be the change you want to see in the world -- Gandhi--- /usr/bin/duply.orig	2018-11-17 22:27:30.0 +
+++ /usr/bin/duply	2020-02-07 17:06:22.683721081 +
@@ -1100,7 +1100,7 @@
 
 # see 'How to specify a user ID' on gpg manpage
 function gpg_fingerprint {
-  local PRINT=$(gpg $GPG_OPTS --fingerprint "$1" 2>&1|awk -F= 'NR==2{gsub(/ /,"",$2);$2=toupper($2); if ( $2 ~ /^[A-F0-9]+$/ && length($2) == 40 ) print $2; else exit 1}') \
+  local PRINT=$(gpg $GPG_OPTS --fingerprint "$1" 2>&1|awk -F= 'NR==2{gsub(/ /,"",$1);$1=toupper($1); if ( $1 ~ /^[A-F0-9]+$/ && length($1) == 40 ) print $1; else exit 1}') \
 && [ -n "$PRINT" ] && echo $PRINT && return 0
   return 1
 }


smime.p7s
Description: S/MIME cryptographic signature

Bug#950879: Add missing patch

[Benedikt Spranger]

Add missing patch.
--- debian/ifupdown.sh.old	2019-01-16 10:27:42.0 +0100
+++ debian/ifupdown.sh	2020-02-07 13:10:50.822365528 +0100
@@ -31,6 +31,12 @@
   if [ "$IF_BRIDGE_HW" ]; then
 ip link set dev $IFACE address $IF_BRIDGE_HW
   fi
+# Activate VLAN filtering on VLAN aware bridges
+  if [ "$IF_BRIDGE_VLAN_AWARE" = "yes" ]; then
+ip link set dev $IFACE type bridge vlan_filtering 1
+  else
+ip link set dev $IFACE type bridge vlan_filtering 0
+  fi
 # Wait for the ports to become available
   if [ "$IF_BRIDGE_WAITPORT" ]
   then

Bug#851639: ITP: alacritty -- A cross-platform, GPU-accelerated terminal emulator

[Johan Fleury]

Hi Félix.

I’m not really into Rust nor Rust packaging in Debian, could you elaborate a 
bit more on why Debian requires Alacritty to be hosted on crates.io? According 
to the discussion in alacritty#357 [1], upstream can’t or won't publish to 
crates.io.

It seems that there hasn't been any progress on this RFP/ITP since 2017, is 
there any way one can help (I couldn't find any repo on salsa)?

[1] https://github.com/jwilm/alacritty/issues/357

-- 

Johan Fleury
PGP Key ID : 0x5D404386805E56E6

signature.asc
Description: OpenPGP digital signature

Bug#950882: contextfree: Please make another source-only upload to allow testing migration

[Boyuan Yang]

Source: contextfree
Severity: important
Version: 3.2+dfsg1-1
X-Debbugs-CC: pau...@debian.org j...@glyphic.com

Dear contextfree maintainers,

The last upload of package contextfree in Debian was not a source-only upload.
As a result, this upload will never migrate to Debian Testing. Please consider
making another source-only upload to fix this problem.

More information about source-only upload can be found at 
https://wiki.debian.org/SourceOnlyUpload .

-- 
Regards,
Boyuan Yang


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

Bug#950881: duply: Autoset trust of keys always fails

[Jean-Michel Vourgère]

Package: duply
Version: 2.1-1
Severity: normal
Tags: patch

Dear Maintainer,

I occasionally restore servers by installing a basic Debian server,
recovering the /root/.duply and then use duply restore.
However, then, I don't have a gnupg home, so that that keys are imported on
first run. This works fine.
However, then, the key needs to be trusted, and it *always* fail.

Step to reproduce:

mv .gnupg .gnupg.bak
duply ... status

You then get something like:
> Encryption public key 'DEBF3E88927A9346' not found.
> Import keyfile '/root/.duply/hosname/gpgkey.DEBF3E88927A9346.pub.asc' to 
> keyring (OK)
> Import keyfile '/root/.duply/hosname/gpgkey.DEBF3E88927A9346.sec.asc' to 
> keyring (OK)
> Autoset trust of key 'DEBF3E88927A9346' to ultimate (FAILED)
> For duply to work you have to set the trust level
> with the command "trust" to "ultimate" (5) now.
> Exit the edit mode of gpg with "quit".
> Running gpg to manually edit key 'D790F566D0CC0472'Secret key is available.

This is really annoying.

I traced back the issue to the function gpg_fingerprint that's not working.

The attached patch fixes the issue.

Thank you for taking care of duply :)

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

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

Versions of packages duply depends on:
ii  duplicity  0.7.18.2-1
ii  gnupg  2.2.12-1+deb10u1

duply recommends no packages.

Versions of packages duply suggests:
ii  openssh-client  1:7.9p1-10+deb10u2

-- no debconf information--- /usr/bin/duply.orig	2018-11-17 22:27:30.0 +
+++ /usr/bin/duply	2020-02-07 16:07:04.261144459 +
@@ -1100,7 +1100,7 @@
 
 # see 'How to specify a user ID' on gpg manpage
 function gpg_fingerprint {
-  local PRINT=$(gpg $GPG_OPTS --fingerprint "$1" 2>&1|awk -F= 'NR==2{gsub(/ /,"",$2);$2=toupper($2); if ( $2 ~ /^[A-F0-9]+$/ && length($2) == 40 ) print $2; else exit 1}') \
+  local PRINT=$(gpg $GPG_OPTS --fingerprint "$1" 2>&1|awk -F= 'NR==2{gsub(/ /,"",$1);$2=toupper($1); if ( $1 ~ /^[A-F0-9]+$/ && length($1) == 40 ) print $1; else exit 1}') \
 && [ -n "$PRINT" ] && echo $PRINT && return 0
   return 1
 }


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

Bug#950880: devscripts: uscan: --download-current-version fails to pick tags from github

[ghostbar]

Package: devscripts
Version: 2.20.2
Severity: important
Usertags: uscan

I'm trying to rebuild an old version of capstone. For the source orig I 
tried to use uscan to get the tar.gz with --download-current-version but 
it failed to find it. Tried to debian/watch files, the current one:


```
version=3
https://github.com/aquynh/capstone/releases .*/archive/(3\..*)\.tar\.gz
```

And one with version 4:

```
version=4
opts="filenamemangle=s%(?:.*?)?v?(\d[\d.]*)\.tar\.gz%capstone-$1.tar.gz%" \
  https://github.com/aquynh/capstone/tags \
  (?:.*?/)?v?(\d[\d.]*)\.tar\.gz debian uupdate
```

Both failed in the same way, they work without parameters, downloading 
the latest version, but when it comes to use --download-current-version 
give the same "no matching hrefs for version", but the tag for version 
3.0.4 does exist in github[1]:


```
root@c7e7c30e65ea:/opt/src# uscan
uscan: Newest version of capstone on remote site is 4.0.1, local version 
is 3.0.4

uscan:=> Newer package available from
  https://github.com/aquynh/capstone/archive/4.0.1.tar.gz
Successfully symlinked ../capstone-4.0.1.tar.gz to 
../capstone_4.0.1.orig.tar.gz.

uupdate: debian/source/format is "3.0 (quilt)".
uupdate: Auto-generating capstone_3.0.4-0.3.debian.tar.xz
uupdate: -> Copy to  capstone_4.0.1-1.debian.tar.xz

root@c7e7c30e65ea:/opt/src# uscan --download-current-version
uscan warn: In debian/watch no matching hrefs for version 3.0.4 in watch 
line
  https://github.com/aquynh/capstone/tags 
(?:.*?/)?v?(\d[\d.]*)\.tar\.gz debian uupdate

```

[1]: https://github.com/aquynh/capstone/releases/tag/3.0.4

Bug#934019: Maintaining cmph Request

[Christian Kastner]

Hi Brett,

On 16.08.19 07:35, Brett D wrote:
> I would like to commit to being the maintainer of the cmph package.
> I am new to Debian, but I understand the very basics of package
> maintenance, UNIX-like infrastructure, and C development.
> Please let me know what further actions need be taken; I suppose that
> upon preliminary approval, I would then have to find a team to sponsor
> me in maintaining this package.

The Debian Developer's Reference [1] lists the most important workflows
for a contributor.

Teams are good, however if you can't find one (for example, this package
doesn't really scream like a great fit to anything), you can find
mentorship and sponsorship through debian-mentors [2].

Seeing as this package has been RFA'ed (and not orphaned), I'd try to
contact the maintainer directly and see if he would be willing to sponsor.

[1] https://www.debian.org/doc/manuals/developers-reference/

[2] https://mentors.debian.net/

Bug#950879: bridge-utils: DSA and other VLAN aware bridges needs VLAN filtering

[Benedikt Spranger]

Package: bridge-utils
Version: 1.6-2
Severity: wishlist
Tags: patch

Dear Maintainer,

while configuring a DSA supported switch with ifupdown I face the
problem, that VLAN filtering is not set.

Documentation/networking/dsa/configuration.rst in the linux kernel tree
describes what is nessesary to setup such a DSA supported switch.

Except for the

ip link set dev br0 type bridge vlan_filtering 1

the whole configuration can be easiely done by ifupdown like:

auto br0
iface br0 inet static
address 172.16.0.1
netmask 255.255.255.0
bridge_ports lan1 lan2 lan3 lan4 eth0.100
bridge_vlan_aware yes
bridge_maxwait 5
up bridge vlan add dev lan1 vid 100 pvid untagged
up bridge vlan add dev lan2 vid 100 pvid untagged
up bridge vlan add dev lan3 vid 100 pvid untagged
up bridge vlan add dev lan4 vid 100 pvid untagged
up bridge vlan del dev lan1 vid 1
up bridge vlan del dev lan2 vid 1
up bridge vlan del dev lan3 vid 1
up bridge vlan del dev lan4 vid 1

The attached patch adds the missing bridge_vlan_aware aka
enable VLAN filtering support.

Regards
Benedikt Spranger

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

Kernel: Linux 5.2.0-2-amd64 (SMP w/4 CPU cores)
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=de_DE.\
UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages bridge-utils depends on:
ii  libc6  2.29-10

bridge-utils recommends no packages.

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

-- no debconf information

Bug#950571: znc: ZNC is unable to connect to IRC with default oidentd configuration

[Patrick Matthäi]

Am 03.02.2020 um 17:21 schrieb Richard:
> Package: znc
> Version: 1.7.5-1~bpo10+1
> Severity: important
>
> Dear Maintainer,
>
> The ZNC package now ships with a system user called `_znc`, rather than
> `znc`. This is causes an issue when oidentd is installed and the default
> configuration is not overridden. Most IRC networks will treat `_znc` as
> an invalid username, and refuse connection. For example, freenode:
>
> 17:16:59 <*status> Error from server: Closing Link: cadoth.net (Invalid 
> username [_znc])
>
>
Hi,

I don't know if it is such a good idea (and Debian rules confirm) to
provide a default oidentd config (also you are free to use other identd
services?). So my first idea would be to provide a working oidentd
config as example file. The other pro would be, that the admin of the
system has to know, what he is doing :-)

-- 
/*
Mit freundlichem Gruß / With kind regards,
 Patrick Matthäi
 GNU/Linux Debian Developer

  Blog: https://www.linux-dev.org/
E-Mail: pmatth...@debian.org
patr...@linux-dev.org
*/

Bug#950878: gumbo-parser: please replace gumbo-parser by the sigil-gumbo fork

[Vincent Lefevre]

Source: gumbo-parser
Version: 0.10.1+dfsg-2.4
Severity: normal

gumbo-parser is dead upstream (no longer updated since June 2016),
and cannot really be used to transform HTML5 to XHTML5 (for instance,
it can generate invalid attribute names, which make the HTML::Gumbo
Perl module crash).

Please replace it by sigil-gumbo:

  https://github.com/Sigil-Ebook/sigil-gumbo

described as a "fork of google/gumbo-parser to support xhtml parsing
rules and allow for editing".

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

Kernel: Linux 5.4.0-3-amd64 (SMP w/12 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=POSIX 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

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

Bug#950877: ITP: ruby-dry-types -- Flexible type system for Ruby with coercions and constraints

[Utkarsh Gupta]

Package: wnpp
Severity: wishlist
Owner: Utkarsh Gupta 

* Package name : ruby-dry-types
  Version : 1.2.2
  Upstream Author : dry team
* URL :  https://github.com/dry-rb/dry-types
* License : Expat
  Programming Lang : Ruby
  Description: Flexible type system for Ruby with coercions and constraints
 dry-types is a simple and extendable type system for Ruby; useful for value
 coercions, applying constraints, defining complex structs or value objects
 and more.
 .
 It was created as a successor to Virtus.

Bug#950875: RM: superiotool -- ROM; see #381727

[Gürkan Myczko]

Package: ftp.debian.org
Severity: normal

Bug#950874: RM: msrtool -- ROM; see #381727

[Gürkan Myczko]

Package: ftp.debian.org
Severity: normal

Bug#950872: gnome-control-center: Cannot add new VPN connection without admin rights

[Rike-Benjamin Schuppner]

Package: gnome-control-center
Version: 1:3.30.3-2~deb10u1
Severity: normal

Dear Maintainer,

in Debian 9, it used to be possible to create new VPN connections as a non-
admin by importing from file or setting up the data in the GUI (gateway, type,
certificates) and then unticking ‘Make available to other users’ before
pressing ‘Add’.
This tick box is not available anymore on Debian 10, which not only means that
admin rights are required to create a new VPN connection, it also means that
the VPN will be available to everyone else automatically, which is not the best
situation for a shared computer.

Note that the tick box is still available for existing VPNs, on the ‘Details’
tab (this tab is completely missing when creating a new VPN).

I’d also be happy if anyone knew a workaround that made all new VPN connections
per default per-user only; then I could live without this tick box.



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

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

Versions of packages gnome-control-center depends on:
ii  accountsservice0.6.45-2
ii  apg2.2.3.dfsg.1-5
ii  colord 1.4.3-4
ii  desktop-base   10.0.2
ii  desktop-file-utils 0.23-4
ii  gnome-control-center-data  1:3.30.3-2~deb10u1
ii  gnome-desktop3-data3.30.2.1-2
ii  gnome-settings-daemon  3.30.2-3
ii  gsettings-desktop-schemas  3.28.1-1
ii  libaccountsservice00.6.45-2
ii  libatk1.0-02.30.0-2
ii  libc6  2.28-10
ii  libcairo-gobject2  1.16.0-4
ii  libcairo2  1.16.0-4
ii  libcanberra-gtk3-0 0.30-7
ii  libcanberra0   0.30-7
ii  libcheese-gtk253.31.90-1
ii  libcheese8 3.31.90-1
ii  libclutter-1.0-0   1.26.2+dfsg-10
ii  libclutter-gtk-1.0-0   1.8.4-4
ii  libcolord-gtk1 0.1.26-2
ii  libcolord2 1.4.3-4
ii  libcups2   2.2.10-6+deb10u1
ii  libfontconfig1 2.13.1-2
ii  libgdk-pixbuf2.0-0 2.38.1+dfsg-1
ii  libglib2.0-0   2.58.3-2+deb10u2
ii  libgnome-bluetooth13   3.28.2-4~deb10u1
ii  libgnome-desktop-3-17  3.30.2.1-2
ii  libgoa-1.0-0b  3.30.1-2
ii  libgoa-backend-1.0-1   3.30.1-2
ii  libgrilo-0.3-0 0.3.7-1
ii  libgtk-3-0 3.24.5-1
ii  libgtop-2.0-11 2.38.0-4
ii  libgudev-1.0-0 232-2
ii  libibus-1.0-5  1.5.19-4+deb10u1
ii  libkrb5-3  1.17-3
ii  libmm-glib01.10.0-1
ii  libnm0 1.14.6-2+deb10u1
ii  libnma01.8.20-1.1
ii  libpango-1.0-0 1.42.4-7~deb10u1
ii  libpangocairo-1.0-01.42.4-7~deb10u1
ii  libpolkit-gobject-1-0  0.105-25
ii  libpulse-mainloop-glib012.2-4+deb10u1
ii  libpulse0  12.2-4+deb10u1
ii  libpwquality1  1.4.0-3
ii  libsecret-1-0  0.18.7-1
ii  libsmbclient   2:4.9.5+dfsg-5+deb10u1
ii  libsoup2.4-1   2.64.2-2
ii  libupower-glib30.99.10-1
ii  libwacom2  0.32-1
ii  libwayland-server0 1.16.0-1
ii  libx11-6   2:1.6.7-1
ii  libxi6 2:1.7.9-1
ii  libxml22.9.4+dfsg1-7+b3

Versions of packages gnome-control-center recommends:
ii  cracklib-runtime  2.9.6-2
ii  cups-pk-helper0.2.6-1+b1
ii  gkbd-capplet  3.26.1-1
ii  gnome-online-accounts 3.30.1-2
ii  gnome-user-docs   3.30.2-1
ii  gnome-user-share  3.28.0-2
ii  iso-codes 4.2-1
ii  libcanberra-pulse 0.30-7
ii  libnss-myhostname 241-7~deb10u2
ii  mousetweaks   3.12.0-5
ii  network-manager-gnome 1.8.20-1.1
ii  policykit-1   0.105-25
ii  pulseaudio-module-bluetooth   12.2-4+deb10u1
ii  realmd0.16.3-2
ii  rygel 0.36.2-4
ii  system-config-printer-common  1.5.11-4

Versions of packages gnome-control-center suggests:
ii  gnome-software   3.30.6-5
ii  gstreamer1.0-pulseaudio  1.14.4-1
ii  libcanberra-gtk-module   0.30-7
ii  libcanberra-gtk3-module  0.30-7
ii  x11-xserver-utils7.7+8

Bug#950873: libwireshark-dev: Missing a header file required by present header

[Thorsten Schulz]

Package: libwireshark-dev
Version: 3.2.1-1
Severity: normal

Dear Maintainer,

While trying to build an external dissector, I am including
. (FYI:
https://github.com/T12z/TCNopen/tree/master/trdp/spy/src/trdp_spy -- I am
working on adding deb-packaging ;) )
However, the included epan/plugin_if.h itself includes , which is
not packaged by any non-source package. Thus, compilation is impossible w/o
pulling the full source of wireshark.

It would be nice for easy packaging, to have that dependent header cfile.h
included in some *-dev package.

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

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

Versions of packages libwireshark-dev depends on:
ii  libwireshark13  3.2.1-1
ii  libwiretap-dev  3.2.1-1
ii  libwsutil-dev   3.2.1-1

libwireshark-dev recommends no packages.

libwireshark-dev suggests no packages.

-- no debconf information

Bug#950876: ITP: ruby-colored2 -- library to add colors or attributes to text

[Georg Faerber]

Package: wnpp
Owner: Georg Faerber 
Severity: wishlist

Package name: ruby-colored2
Version : 3.1.2
Upstream Author : Konstantin Gredeskoul 
URL : https://github.com/kigster/colored2/
License : Expat
Programming Lang: Ruby
Description : library to add colors or attributes to text

This library extends the String class with methods to add ANSI colors
and bold, underline or reverse attributes to strings. It can be used to
emphasize messages on the console output or in logs.

This package will be maintained within the Debian Ruby team.

Bug#950871: libwireshark-dev: Missing a header file required by present header

[Thorsten]

Package: libwireshark-dev
Version: 3.2.1-1
Severity: normal

Dear Maintainer,

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

   * What led up to the situation?

While trying to build an external dissector, I am including . 
(FYI: https://github.com/T12z/TCNopen/tree/master/trdp/spy/src/trdp_spy -- I am 
working on adding deb-packaging ;) )
However, the included epan/plugin_if.h itself includes , which is not 
packaged by any non-source package. Thus, compilation is impossible w/o pulling 
the full source of wireshark.

It would be nice for easy packaging, to have that dependent header cfile.h 
included in some *-dev package.


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


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

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

Versions of packages libwireshark-dev depends on:
ii  libwireshark13  3.2.1-1
ii  libwiretap-dev  3.2.1-1
ii  libwsutil-dev   3.2.1-1

libwireshark-dev recommends no packages.

libwireshark-dev suggests no packages.

-- no debconf information

Bug#950833: Missing Breaks/Replaces between libreoffice-help-common and libreoffice-help-fr?

[Rene Engelhard]

Hi,

On Fri, Feb 07, 2020 at 10:10:24AM +0100, rene.engelh...@mailbox.org wrote:
> >Looks like there is a missing Breaks/Replaces between
> >libreoffice-help-common and libreoffice-help-fr?
> 
> Looks like those localized pngs moved packages unexpectedly...
> 
> Will look...

Caused by
https://cgit.freedesktop.org/libreoffice/help/commit/?h=libreoffice-6-4-1=191058eba782a34dad89959d5a20d6f2edd4bc3a

(and I don't check help/ routinely, while I check core/ for commits.)

Regards,

Rene

Bug#950870: ITP: ruby-dry-container -- Simple, configurable object container implemented in Ruby

[Utkarsh Gupta]

Package: wnpp
Severity: wishlist
Owner: Utkarsh Gupta 

* Package name : ruby-dry-container
  Version : 0.7.2
  Upstream Author : dry team
* URL :  https://github.com/dry-rb/dry-container
* License : Expat
  Programming Lang : Ruby
  Description: Simple, configurable object container implemented in Ruby
 dry-container is a simple, thread-safe container, intended to be one half
 of a dependency injection system, possibly in combination with
dry-auto_inject.
 .
 At its most basic, dependency injection is a simple technique that makes it
 possible to implement patterns or principles of code design that rely on
object
 composition, such as the SOLID principles.

Bug#939756: mercurial: FTBFS on hppa - test-hghave.t timed out

[Julien Cristau]

Control: tag -1 upstream patch
Control: forwarded -1 https://phab.mercurial-scm.org/D8092

On Sun, Sep 08, 2019 at 09:51:42AM -0400, John David Anglin wrote:
> See for example this build log:
> https://buildd.debian.org/status/fetch.php?pkg=mercurial=hppa=5.1.1-1=1567811172=0
> 
> I had a successful build on hppa by increasing the timeout settings in
> debian/rules:
> override_dh_auto_test:
> ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
> # test-pull-pull-corruption tries to execute two hg commands at the
> # same time to test for corruption.  It does so by running an hg
> # command in the background, sleeping one second and running the
> # second command.  In architectures with slow buildds, one second is
> # not enough and the second test starts before the first one has
> # started printing.  This is hacky and we just enhance the hack by
> # incrementing the sleep time in those architectures.
> ifneq ($(or $(ARCH_IS_MIPS), $(ARCH_IS_KFREEBSD-i386), $(ARCH_IS_ARMEL), 
> $(ARCH_
> IS_SPARC)),)
> sed -i.deb-backup -e 's/sleep 1/sleep 2/' 
> $(CURDIR)/tests/test-p
> ull-pull-corruption.t
> endif
> 
> http_proxy='' dh_auto_test -- TESTFLAGS="--verbose --timeout 12000 
> --slowtimeout 36000 $(PARALLEL_TEST_JOBS) --blacklist 
> $(CURDIR)/debian/mercurial.test_blacklist"
> file-rename 's/\.deb-backup$$//' $(CURDIR)/tests/*
> # run blacklisted tests but ignore their results
> -cd tests && python run-tests.py --verbose `grep ^test 
> ../debian/mercurial.test_blacklist`
> endif
> 
> Here is full log:
> https://buildd.debian.org/status/fetch.php?pkg=mercurial=hppa=5.1.1-1=1567919941=0
> 
Thanks for reporting this.  Rather than increasing the timeout I'm
hoping we can just make the test faster.  Sent a patch upstream for
feedback.

Cheers,
Julien

Bug#950869: Subject: ITP: ruby-e2mmap -- define custom exceptions with specific messages

[Balasankar "Balu" C]

Package: wnpp
Severity: wishlist
Owner: "Balasankar \"Balu\" C" 

* Package name: ruby-e2mmap
  Version : 0.0.1
  Upstream Author : Keiju ISHITSUKA 
* URL : https://github.com/ruby/e2mmap
* License : BSD-2-Clause
  Programming Lang: Ruby
  Description : define custom exceptions with specific messages

Was split off from Ruby core in Ruby 2.7 -
https://www.ruby-lang.org/en/news/2019/12/25/ruby-2-7-0-released/

This gem is required to package `thwait` gem, which in turn is required
to add Ruby 2.7 support to existing ruby-innertube package.



signature.asc
Description: OpenPGP digital signature

Bug#949530: network-manager 1.22.4 still failing dhcp on some wifi networks

[Benjamin Redelings]

Hi,

OK, 1.22.6 works for the same router that 1.22.4 didn't work. This is on 
a new laptop, but it seems unlikely that the hardware was causing the 
problem.


-BenRI

On 1/31/20 7:49 PM, Michael Biebl wrote:

On Tue, 21 Jan 2020 12:44:17 -0500 Benjamin Redelings
 wrote:

Package: network-manager
Version: 1.22.4-1
Severity: important

Dear Maintainer,

For some wifi networks, network-manager fails to join the network.  1.22.4 was 
a big improvement over 1.22.2, but there are still some problems.
It logs lines like these:

NetworkManager[854]:   [1578839858.0531] device (p2p-dev-wlp4s0): supplicant 
management interface state: associated -> complet>
NetworkManager[854]:   [1578839858.0534] device (wlp4s0): state change: config 
-> ip-config (reason 'none', sys-iface-state: '>
NetworkManager[854]:   [1578839858.0551] dhcp4 (wlp4s0): activation: 
beginning transaction (timeout in 45 seconds)
NetworkManager[854]:   [1578839861.0781] dhcp4 (wlp4s0): selecting lease 
failed: 12
NetworkManager[854]:   [1578839864.7164] dhcp4 (wlp4s0): selecting lease 
failed: 12
NetworkManager[854]:   [1578839873.5769] dhcp4 (wlp4s0): selecting lease 
failed: 12
NetworkManager[854]:   [1578839892.0217] dhcp4 (wlp4s0): selecting lease 
failed: 12
NetworkManager[854]:   [1578839901.4961] manager: sleep: sleep requested 
(sleeping: no  enabled: yes)
NetworkManager[854]:   [1578839901.4965] device (enp0s31f6): state change: 
unavailable -> unmanaged (reason 'sleeping', sys-if>

I used to be able to join this network with previous versions of 
network-manager.

The gitlab issue links a commit after 1.22.4.

Issue: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/324
Commit: 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/c19eefc6ec9d0a52f4d3ce75e70cfd6dab60aa2f

I've seen the log message "Activation: Stage 5 of 5 (IPv4 Commit) error accepting 
lease: failed to accept lease: Cannot allocate memory"
but I don't get this every time.

If you roll an update that includes commit c19eefc6, I will check whether this 
fixes the problem.

Please test with 1.22.6 and report back

Bug#949710: /usr/bin/plasmashell: segfaults sporadically but only when using app dropdown menu

[Bernhard Übelacker]

Hello Sarah,
I am sorry, but the given information might not be enough
for the maintainers to solve the crash.

Usually when a segfault happens in 'dmesg' output should
appear two lines about this event. Maybe you could forward
these to the report too.

If it is possible to install systemd-coredump a backtrace
would be automatically added to the journal, which could
be viewed by 'journalctl --no-pager'.

'coredumpctl gdb' could also show these information and if
the package gdb is also installed a '(gdb)' prompt should
appear, where the command 'thread apply all bt full'
should provide detailed information where the crash happened.

This information would be much better if the package
plasma-workspace-dbgsym and maybe some for shared libraries
get installed from the repository described here [1].
(If output gets too much pages, maybe attach as file.)


Kind regards
Bernhard

[1] https://wiki.debian.org/HowToGetABacktrace#Installing_the_debugging_symbols

Bug#950845: Flags cannot be created on scoped enums

[Denis Rouzaud]

Hi Lisandro,

Many thanks for taking care of this!


Le ven. 7 févr. 2020 à 16:06, Lisandro Damián Nicanor Pérez Meyer <
perezme...@gmail.com> a écrit :

> tag 950845 moreinfo
> thanks
>
> Hi Denis!
>
> First of all, thanks for filing the bug. In this way is easier for us to
> track
> issues.
>
> Secondly: I'm keeping this bug open for now, even if it's already fixed in
> testing/unstable, as I clearly see you need it solved in Debian stable.
>
> On 20/02/07 12:21, Denis Rouzaud wrote:
> > Package: qtbase-default
> > Version: 5.11.5
> >
> > Flags cannot be created on scoped enums
> >
> > See issue: https://bugreports.qt.io/browse/QTBUG-47652
> >
> > This has been fixed in Qt 5.12
> > https://codereview.qt-project.org/c/qt/qtbase/+/235284
>
> In you [original mail] you say this bug needs to get solved in order to
> use it
> in QGIS. The fix is already in the archive in testing/unstable, only
> stable is
> still affected. So if you are requesting this change is (at least) because
> of:
>
> - You are preparing binary uploads for Debian stable, possibly non-official
>   (Debian stable has qgis compiled against Qt 4).
>

Yes this is it.
We are willing to increase the minimum Qt version to allow using scoped
enums for flags (because it provides way better API documentation).
Increasing to 5.12 but 5.11+fix on debian would be enough for us.
It would be hard to justify not to support Buster (or to package Qt
ourselves).


> - You need to update qgis in stable (I doubt so, as per the above comment).
> - You are preparing a backport.
>
> From a Qt point of view is indeed a rather important bug to be fixed, but
> from a
> Debian stable point of view is not so:
>
> - Code already in stable does not suffers from this: it's clearly working.
> - The bug has been present since Qt 5.5.
>

I see this. The bug isn't that bad indeed, and explained above it's mainly
for documentation purpose we're looking to have it fixed.

>
> I think it will be difficult to convince the stable release team to accept
> the
> patch if the use case is not directly involved in Debian itself.
>
> However I'll try to add the patch and try it myself on a stable system to
> check
> it does not breaks something obvious. For what I can tell from the patch it
> shouldn't, but...
>

I understand that. In any case, thanks a lot for giving it some time.

>
> Whatever extra information you can provide us to justify the stable upload
> would
> certainly help.
>
>
> [original mail] <
> https://lists.debian.org/debian-qt-kde/2020/02/msg00055.html>
>
>
> Regards, Lisandro.
>


Best wishes,

Denis

Bug#950868: ITP: ruby-dry-inflector -- Inflector for Ruby

[Utkarsh Gupta]

Package: wnpp
Severity: wishlist
Owner: Utkarsh Gupta 

* Package name : ruby-dry-inflector
  Version : 0.2.0
  Upstream Author : dry team
* URL :  https://github.com/dry-rb/dry-inflector
* License : Expat
  Programming Lang : Ruby
  Description: Inflector for Ruby
 dry-inflector is an inflector gem for Ruby, which provides a configurable
 inflector object, rather than using a singleton.
 .
 It started with the extlib inflecto originated from active_support, then
 dm-core inflector originated from extlib. Later, inflecto was extracted
 from dm-core as a standalone inflector. Now, we resurrect inflecto and
 merged flexus, with some inflection rules from hanami-utils.
 This is dry-inflector.

Bug#950845: Flags cannot be created on scoped enums

[Lisandro Damián Nicanor Pérez Meyer]

tag 950845 moreinfo
thanks

Hi Denis!

First of all, thanks for filing the bug. In this way is easier for us to track
issues.

Secondly: I'm keeping this bug open for now, even if it's already fixed in
testing/unstable, as I clearly see you need it solved in Debian stable.

On 20/02/07 12:21, Denis Rouzaud wrote:
> Package: qtbase-default
> Version: 5.11.5
> 
> Flags cannot be created on scoped enums
> 
> See issue: https://bugreports.qt.io/browse/QTBUG-47652
> 
> This has been fixed in Qt 5.12
> https://codereview.qt-project.org/c/qt/qtbase/+/235284

In you [original mail] you say this bug needs to get solved in order to use it
in QGIS. The fix is already in the archive in testing/unstable, only stable is
still affected. So if you are requesting this change is (at least) because of:

- You are preparing binary uploads for Debian stable, possibly non-official
  (Debian stable has qgis compiled against Qt 4).
- You need to update qgis in stable (I doubt so, as per the above comment).
- You are preparing a backport.

>From a Qt point of view is indeed a rather important bug to be fixed, but from 
>a
Debian stable point of view is not so:

- Code already in stable does not suffers from this: it's clearly working.
- The bug has been present since Qt 5.5.

I think it will be difficult to convince the stable release team to accept the
patch if the use case is not directly involved in Debian itself.

However I'll try to add the patch and try it myself on a stable system to check
it does not breaks something obvious. For what I can tell from the patch it
shouldn't, but...

Whatever extra information you can provide us to justify the stable upload would
certainly help.


[original mail] 


Regards, Lisandro.

Bug#949887: munin autopkgtest failure for sysvinit based tests

[Michael Biebl]

Control: reassign -1 munin 2.0.51-1

Am 07.02.20 um 15:10 schrieb Holger Levsen:
> hi, 
> 
> thanks for your analysis but this is already fixed in git and the upload
> is just waiting for the upstream tarball to be released, the git tag is
> there..

Thank you both.
Reassigning the bug report accordingly



signature.asc
Description: OpenPGP digital signature

Bug#950867: ITP: ruby-dry-configurable -- Simple mixin to make Ruby classes configurable

[Utkarsh Gupta]

Package: wnpp
Severity: wishlist
Owner: Utkarsh Gupta 

* Package name : ruby-dry-configurable
  Version : 0.9.0
  Upstream Author : dry team
* URL :  https://github.com/dry-rb/dry-configurable
* License : Expat
  Programming Lang : Ruby
  Description: Simple mixin to make Ruby classes configurable
 dry-configurable is a simple mixin to add thread-safe configuration
 behaviour to your classes. There are many libraries that make use of
 configuration, and each seemed to have their own implementation with
 a similar or duplicate interface, so it was strange that
 this behaviour had not already been encapsulated into a reusable gem,
 hence dry-configurable was born.

Bug#950866: Update pyserial homepage

[Grzegorz Szymaszek]

Package: pyserial
Version: 3.4-5.1

Hello,

the homepage of the pyserial project should be updated. The old one[1]
points to the new URL: [2].

Thanks!

[1]: http://pyserial.sourceforge.net/
[2]: https://github.com/pyserial/pyserial

-- 
Grzegorz Szymaszek


signature.asc
Description: PGP signature

Bug#950865: RM: msrtool -- ROM; RM: see #381727

[Gürkan Myczko]

Package: ftp.debian.org
Severity: normal

Bug#950864: RM: inteltool -- ROM; RM: see #381727

[Gürkan Myczko]

Package: ftp.debian.org
Severity: normal

Bug#950718: RFS: depthcharge-tools/0.3.0-1 [ITP] -- Tools for ChromeOS firmware/bootloader integration

[Andrej Shadura]

On Wed, 5 Feb 2020 13:54:26 +0300 Alper Nebi Yasak
 wrote:
> I am looking for a sponsor for my package "depthcharge-tools":
> 
>  * Package name: depthcharge-tools
>Version : 0.3.0-1
>Upstream Author : Alper Nebi Yasak 
>  * URL : https://github.com/alpernebbi/depthcharge-tools
>  * License : GPL-2.0+
>  * Vcs : 
> https://salsa.debian.org/alpernebbi-guest/depthcharge-tools
>Section : admin
> 
> It builds those binary packages:
> 
>   depthcharge-tools - Tools for ChromeOS firmware/bootloader integration
>   depthcharge-support - ChromeOS firmware/bootloader integration
>   depthcharge-support-installer - Make this ChromeOS machine bootable (udeb)
> 
> To access further information about this package, please visit the following 
> URL:
> 
>   https://mentors.debian.net/package/depthcharge-tools
> 
> Alternatively, one can download the package with dget using this command:
> 
>   dget -x 
> https://mentors.debian.net/debian/pool/main/d/depthcharge-tools/depthcharge-tools_0.3.0-1.dsc
> 
> Changes since the last upload:
> 
>* Initial release. (Closes: #950687)

Same here as with #950717: how about talking to the DI team and
team-maintaining it and hosting it under
https://salsa.debian.org/installer-team?

P.S. I had a look at the package and apart from the fact I call the GPL
"GPL-2+" not "GPL-2.0+", I don’t have any nitpicks, but then I don’t
know anything about how the d-i integration should work.

-- 
Cheers,
  Andrej

Bug#950863: ITP: ruby-dry-logic -- Predicate logic with rule composition

[Utkarsh Gupta]

Package: wnpp
Severity: wishlist
Owner: Utkarsh Gupta 

* Package name : ruby-dry-logic
  Version : 1.0.5
  Upstream Author : dry team
* URL :  https://github.com/dry-rb/dry-logic
* License : Expat
  Programming Lang : Ruby
  Description: Predicate logic with rule composition
 Predicate logic and rule composition used by:
 - dry-types for constrained types.
 - dry-validation for composing validation rules.

Bug#950717: RFS: partman-cros/1 [ITP] -- Add partman support for ChromeOS kernel partitions

[Andrej Shadura]

On Wed, 5 Feb 2020 13:52:11 +0300 Alper Nebi Yasak
 wrote:
> I am looking for a sponsor for my package "partman-cros":
> 
>  * Package name: partman-cros
>Version : 1
>Upstream Author : Alper Nebi Yasak 
>  * URL : https://salsa.debian.org/alpernebbi-guest/partman-cros
>  * License : GPL-2.0+
>  * Vcs : https://salsa.debian.org/alpernebbi-guest/partman-cros
>Section : debian-installer
> 
> It builds those binary packages:
> 
>   partman-cros - Add partman support for ChromeOS kernel partitions (udeb)
> 
> To access further information about this package, please visit the following 
> URL:
> 
>   https://mentors.debian.net/package/partman-cros
> 
> Alternatively, one can download the package with dget using this command:
> 
>   dget -x 
> https://mentors.debian.net/debian/pool/main/p/partman-cros/partman-cros_1.dsc

How about talking to the DI team and team-maintaining it and hosting it
under https://salsa.debian.org/installer-team?

-- 
Cheers,
  Andrej

Bug#950862: exa: hardcoded weird 7-bit collation

[Adam Borowski]

Package: exa
Version: 0.9.0-2
Severity: normal

Hi!
I'm afraid that exa uses a hard-coded collation no matter what you try to
configure.  It uppercases every byte's value then sorts as bytes.

Thus:
* LC_COLLATE=C.UTF-8 nor LC_COLLATE=C don't produce traditional order
* non-ASCII letters behave differently from 7-bit (only latter are uppercased)
* Turkic locales don't get ı↔I i↔ İ
* language specific collation isn't obeyed (a<ą

Bug#950516: file: please backport 5.38 to stable for removal of python2

[Felix Lechner]

Hi Christoph,

On Thu, Feb 6, 2020 at 11:17 PM Christoph Biedl
 wrote:
>
> Yeah, or something else confused me. Sorry if I appeared stubborn, I
> just want to understand what I do.

Please do not worry. Thank you for maintaining such an important
package. Lintian could not exist without you.

> will you need support for Python 3.8 as
> well², now or at least before the Debian 11 ("bullseye") release?

There are advantages to having support for Python 3.8. For example,
lintian.d.o could issue tags related to those binaries. The Debian
community relies on that service, which runs on stable, for packages
uploaded to unstable and experimental (which are most likely to see
newer Python versions).

> I just need
> someone who is willing to do the upload.

I do not have those privileges but know people who do.

Kind regards
Felix

Bug#950839: reprounzip autopkg test fails with python 3.8

[Rémi Rampin]

This appears to be a duplicate of #943442.

Upstream version 1.0.16 fixes the problem. It seems that there have
been uploads of reprozip but not reprounzip, I'm not sure why.

Bug#949887: munin autopkgtest failure for sysvinit based tests

[Holger Levsen]

hi, 

thanks for your analysis but this is already fixed in git and the upload
is just waiting for the upstream tarball to be released, the git tag is
there..


-- 
cheers,
Holger

---
   holger@(debian|reproducible-builds|layer-acht).org
   PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C

Some people say that the climate crisis  is something that we all have created,
but  that is not true,  because if everyone is guilty  then no one is to blame.
And someone is to blame.  Some people, some companies,  some decision-makers in
particular, have known exactly what priceless values they have been sacrificing
to continue making unimaginable amounts of money.


signature.asc
Description: PGP signature