Bug#941895: (no subject)

[Sergey B Kirpichev]

cont...@bugs.debian.org
Bcc: 
Subject: Re: Bug#941895: monit: invalid CSRF check causes login issues
Reply-To: skirpic...@gmail.com
In-Reply-To: <20191009143716.GA17535@note>
X-Debbugs-No-Ack: no, please

tags 941895 +moreinfo
thanks

Ok, I'll wait for feedback for 2 weeks.

On Wed, 9 Oct 2019 17:37:16 +0300 Sergey B Kirpichev  
wrote:
> On Mon, Oct 07, 2019 at 12:15:13PM +0100, Jonathan Wiltshire wrote:
> > I'm happy to sponsor uploads to the stable suites, certainly. You will
> > need approval from the stable release managers first then, and I will
> > avoid wearing that hat for this case in order to avoid a conflict of
> > interest.
> 
> I think, I can handle stable uploads myself, as I did previously.  But
> if not (release managers may be unhappy with changes) - backports is
> only option.
> 
> Meanwhile, I'll raise issue severity (only important+ bugfixes
> can enter point releases).
> 
> > I don't monitor monit (haha) or sponsorship-requests generally, so drop
> > me a mail when you are ready for it to be uploaded.
> 
> I've cherry-picked
> https://bitbucket.org/tildeslash/monit/commits/f9a9a7a92
> - please test package.  It was uploaded to the mentors.d.n:
> https://mentors.debian.net/package/monit
> 
> Please test.
> 
> 

Bug#942259: rollup 1.x transition: node-locate-character build fails with Error: You must supply options.input to rollup

[Pirate Praveen]

package: node-locate-character
version: 2.0.1-6
severity: important

With rollup 1.0 in experimental, build failed with this error, please 
fix this error before uploading rollup 1.0 to unstable.


rollup -c
(!) You have passed an unrecognized option
Unknown input option: entry, moduleName, targets. Allowed options: 
acorn, acornInjectPlugins, cache, chunkGroupingSize, context, 
experimentalCacheExpiry, experimentalOptimizeChunks, 
experimentalTopLevelAwait, external, inlineDynamicImports, input, 
manualChunks, moduleContext, onwarn, perf, plugins, preserveModules, 
preserveSymlinks, shimMissingExports, treeshake, watch


undefined → stdout...
[!] Error: You must supply options.input to rollup
Error: You must supply options.input to rollup
   at new Graph (/usr/share/nodejs/rollup/src/Graph.js:90:19)
   at Object.rollup 
(/usr/share/nodejs/rollup/src/rollup/index.js:129:23)
   at Object.build [as default] 
(/usr/share/nodejs/rollup/bin/src/run/build.js:41:10)

   at /usr/share/nodejs/rollup/bin/src/run/index.js:117:39
   at process._tickCallback (internal/process/next_tick.js:68:7)
   at Function.Module.runMain (internal/modules/cjs/loader.js:834:11)
   at startup (internal/bootstrap/node.js:283:19)
   at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)

Bug#942055: version in oldstable not affected

[Alexander Reichle-Schmehl]

notfound 942055 9.26a~dfsg-0+deb9u5
thanks

Version in oldstable is not affected by this regression.

Bug#941655: libreoffice-impress: Exported html pages have black backgrounds

[Frank B. Brokken]

Dear Rene Engelhard, you wrote:
> 
> [ always keep the bug in the Cc so that discussions about the bug are
> recorded ]

You're absolutely right: I simply did a reply in my previous answer. Sorry
about that.

> On Sat, Oct 12, 2019 at 05:38:38PM +0200, Frank B. Brokken wrote:
> > By desktop you mean window manager? That's afterstep (2.2.12-12+b1). There's
> 
> No, I mean desktop.

Oh. Well, in that case: the computer I used, and have been using previously
when everything worked fine, is an Acer travelmate P 276, but see also below:
my office's desktop also shows the bug.


> ...
> And here I actually meant vcl, not vlc. Aka libreoffice-gtk, -gtk3,
> -qt5, -kde5.
> 
> But given yu use afterstep I believe you have neither installed not
> explicitely choosen one of those.

Correct. Since installing libreoffice doesn't automatically install that
package as well, it's apparently not required. Also, since it hasn't been
installed before when exporting html worked OK, I guess it's unlikely that
that's the cause of the problem. 

> Which makes this definitely unreproducible here, since that "gen"eric
> one was what I tried in my chroot.

That's a pity (i.e., that you can't reproduce the problem). At my office I
have an ordinary desktop computer (I don't have its brand name handy) and that
one I used to file the bug. So there are two completely different computer
systems that produced the bug, which previously wasn't encountered. 

Any suggestions as to how to proceed from here?

-- 
Frank B. Brokken
(+31) 6 5353 2509
PGP Key Fingerprint: DF32 13DE B156 7732 E65E  3B4D 7DB2 A8BE EAE4 D8AA

Bug#941655: libreoffice-impress: Exported html pages have black backgrounds

[Frank B. Brokken]

Dear Rene Engelhard, you wrote:

> On Sat, Oct 12, 2019 at 01:37:50PM +0200, Rene Engelhard wrote:
> > On Sat, Oct 12, 2019 at 01:34:44PM +0200, Rene Engelhard wrote:
> > > See http://people.debian.org/~rene/libreoffice/6.3
> > > (apt-gettable via "deb http://people.debian.org/~rene/libreoffice/6.3 ./"
> > > in sources.list, but you should know that..)
> > 
> > Sorry, sent too fast, it's building and I forgot I deleted the older
> > snapshot which was there. Will be there if the build finishes and I
> > uploaded it, though.
> 
> It's now there.

OK, after removing the current Debian testing version and installing the 
snapshot versions everything looks good again.

Many thanks for your help!

-- 
Frank B. Brokken
(+31) 6 5353 2509
PGP Key Fingerprint: DF32 13DE B156 7732 E65E  3B4D 7DB2 A8BE EAE4 D8AA

Bug#942252: lintian: t/scripts/pod-synopsis.t: (Wstat: 256 Tests: 66 Failed: 1)

[Sebastian Ramacher]

Source: lintian
Version: 2.26.0
Severity: serious
Tags: ftbfs sid bullseye
Justification: fails to build from source

lintian 2.26.0 failed to build on the arch all buildd:

| Test Summary Report
| ---
| t/scripts/pod-synopsis.t  
  (Wstat: 256 Tests: 66 Failed: 1)
|   Failed test:  29
|   Non-zero exit status: 1
| Files=1017, Tests=35989, 654 wallclock secs ( 8.61 usr  5.30 sys + 2139.84 
cusr 389.91 csys = 2543.66 CPU)
| Result: FAIL

| make[1]: *** [debian/rules:50: runtests] Error 1
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:120: binary-indep] Error 2
| dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit 
status 2


See
https://buildd.debian.org/status/fetch.php?pkg=lintian=all=2.26.0=1570670200=0
for the full build log

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#875219: Should we file a removal bug?

[Moritz Mühlenhoff]

On Tue, Sep 17, 2019 at 12:06:20PM -0300, Lisandro Damián Nicanor Pérez Meyer 
wrote:
> Hi! We have seen no activity in this bug, should we file a removal bug?
> 
> Cheers, Lisandro.

I've filed a removal bug now.

Cheers,
Moritz

Bug#942264: RM: unixodbc-gui-qt -- RoQA; Depends on Qt4

[Moritz Muehlenhoff]

Package: ftp.debian.org
Severity: normal

Please remove unixodbc-gui-qt, it depends on Qt4 which is being
removed and hasn't seen an upload since 5.5 years.

Cheers,
Moritz

Bug#942224: asymptote: VIM addon cannot be managed with vim-addons and fails to enable syntax highlighting

[Francesco Poli]

On Sun, 13 Oct 2019 21:26:28 +0900 Norbert Preining wrote:

> Hi Francesco,
> 
> On Sun, 13 Oct 2019, Francesco Poli wrote:
> > I am a newbie myself, I learned the basics by looking at other packages
> > shipping VIM addons (such as package vim-scripts) and by reading the
> > vim-addons(1) and vim-registry(5) man pages (shipped in package
> > vim-addon-manager).
> 
> Aren't there different ways to activate packages in Vim? I have always
> had problems with all the differen packages managers in vim.

I am only aware of addons handled by vim-addon-manager and of files
placed directly into the /usr/share/vim/vim81/ tree (by src:vim binary
packages, I think).
But, as I said, I am no expert, hence there may be other ways...



-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpbYamCTTRml.pgp
Description: PGP signature

Bug#942122: does not fallback to ipv4 when ipv6 fails

[Antoine Beaupré]

On 2019-10-13 12:11:51, Eduard Bloch wrote:
> Hallo,
> * Antoine Beaupre [Thu, Oct 10 2019, 12:36:21PM]:
>> Package: apt-cacher-ng
>> Version: 3.2-2
>> Severity: normal
>> Tags: ipv6
>>
>> apt-cacher-ng does not deal well with dual-stack failures. At home I
>> regularly have trouble with my IPv6 connexions, which just hang. Most
>> applications are able to recover from this and fallback to IPv4, which
>> just works. This is therefore mostly transparent to users, at worst
>> there's a slight delay during the switchover.
>
> Okay, I agree. I also experience such situations, rarely, when the
> crap modem from my provider gets upset and fails to route IPv6 (but
> still reports full IPv6 connectivity in its diagnostics).
>
>> The way to deal with this is documented in RFC 8305 and is generally
>> refered to as "happy eyeballs":
>>
>> https://en.wikipedia.org/wiki/Happy_Eyeballs
>
> Not sure this is feasible exactly the way they describe there. This RFC
> is apparently mostly by DNS timing behavior but ACNG currently uses
> getaddrinfo which delivers all collected DNS data at once.
>
> What I intend to implement instead is a similar scheme:
>
> a) get all DNS records like ATM
> b) filter to IPv4 or IPv6 or both (depending on user preference in 
>  setting)
> c) auto-sort the list so that the first entry is v4 or v6 (depending on 
>  preference) and the following ones are alternativing
> d) start connecting on the first entry
> e) when nothing happened after N seconds, start a second connection attempt 
> in parallel (using the second address, which is of different family then)
> f) if the second background connect attmpt fails after N, abort it, try the 
> next DNS entry in the sequence, etc. etc. (while the first connect attempt is 
> still ongoing, until  seconds is reached)
>
> Questions:
>
> a) do you consider this reasonable enough?

That seems reasonable, and actually pretty close to RFC8305.

> b) would you like to become a tester for this, in case you can reproduce
> this regularly? (I can fake the test case but nothing beats the real
> thing)

I can try! it can take up to a month for this situation to occur and I
haven't tried reproducing it manually, but I'm definitely happy to help.

> c) any good name proposal for N? I think about "FastTimeout"
> (vs. NetworkTimeout)

The RFC calls this a "Connection Attempt Delay".

> d) good default value for N? I'd consider 5s (while NetworkTimeout: 60s 
> currently)

"N" is 250ms in the rfc, fwiw, which seems more reasonable than (say)
something large than 1s, let alone one *minute*. :)

It also says that connexion attempts should be spaced out by at least
10ms, preferably 100ms. This is all in section 5.

A.
-- 
You are absolutely deluded, if not stupid, if you think that a
worldwide collection of software engineers who can't write operating
systems or applications without security holes, can then turn around
and suddenly write virtualization layers without security holes.
- Theo de Raadt

Bug#942227: fish: "unreachable" state reached when redirecting to/from an unopenable file with `exec'

[David Adam]

On Sat, 12 Oct 2019, Asher Gordon wrote:
> 
>   $ fish -c 'exec cat < /dev/mem'
>   An error occurred while redirecting file '/dev/mem'
>   open: Permission denied
>fish: src/exec.cpp:1032: failed assertion: this should be unreachable
>fish: Backtrace:
>   [...]
> 
> Note the `exec' and the `<'. Without the `<', `cat' tries to open
> /dev/mem, not `fish', so the bug does not appear.

I am pleased to report that this problem is fixed in the upcoming 3.1.0
release:

https://github.com/fish-shell/fish-shell/pull/5643

Kind regards,

David Adam
fish committer
zanc...@ucc.gu.uwa.edu.au

Bug#891877: Have either synaptic removed or have it rebuilt with libgtk3-perl in it recommends.

[shirish शिरीष]

at bottom :-

On 13/10/2019, intrigeri  wrote:



>
> Jeremy Bicha filed #891877 a while ago, requesting that Synaptic's
> dependencies are updated accordingly. I believe the actions Jeremy
> suggested on #891877 will solve the problem shirish is raising here,
> improve the life of Synaptic's users, and make it clearer what is the
> status of libgtk2-perl in the archive.
>
> Thoughts?
>
> (Oh my, so many words for a bug that can be fixed by s/2/3/ in one
> single place :)
>
> Cheers,
> --
> intrigeri
>

My bad. While I had looked at synaptic bugs but there are so many and
there wasn't an RC  bug or something which in my view should have .
Anyways, have subscribed to the bug and am looking forward to see if
Michael Vogt  (the maintainer of Synaptic) addresses the bug report
soonish.

Looking forward to see it fixed.

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com

E493 D466 6D67 59F5 1FD0 930F 870E 9A5B 5869 609C

Bug#942251: rtkit: The rtkit-daemon running on 2 instances.

[Corcodel Marian]

Package: rtkit
Version: 0.11-4+deb9u1
Severity: normal

How to detect this situations
Run from term lsof>list_to_read
Read vim list_to_read.
>From list see how to rtkit-daemon is child of same program and access same
resources, this is bad.



-- System Information:
Debian Release: 9.11
  APT prefers oldstable
  APT policy: (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.0.0-rc6+ (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages rtkit depends on:
ii  adduser  3.115
ii  dbus 1.10.28-0+deb9u1
ii  init-system-helpers  1.48
ii  libc62.24-11+deb9u4
ii  libcap2  1:2.25-1
ii  libdbus-1-3  1.10.28-0+deb9u1
ii  policykit-1  0.105-18+deb9u1

rtkit recommends no packages.

rtkit suggests no packages.

-- no debconf information

Bug#941655: libreoffice-impress: Exported html pages have black backgrounds

[Rene Engelhard]

Hi,

On Sat, Oct 12, 2019 at 01:37:50PM +0200, Rene Engelhard wrote:
> On Sat, Oct 12, 2019 at 01:34:44PM +0200, Rene Engelhard wrote:
> > See http://people.debian.org/~rene/libreoffice/6.3
> > (apt-gettable via "deb http://people.debian.org/~rene/libreoffice/6.3 ./"
> > in sources.list, but you should know that..)
> 
> Sorry, sent too fast, it's building and I forgot I deleted the older
> snapshot which was there. Will be there if the build finishes and I
> uploaded it, though.

It's now there.

Regards,
 
Rene

Bug#942254: vips: CVE-2019-17534

[Salvatore Bonaccorso]

Source: vips
Version: 8.7.4-1
Severity: important
Tags: security upstream

Hi,

The following vulnerability was published for vips.

CVE-2019-17534[0]:
| vips_foreign_load_gif_scan_image in foreign/gifload.c in libvips
| before 8.8.2 tries to access a color map before a DGifGetImageDesc
| call, leading to a use-after-free.


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-2019-17534
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17534
[1] https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=16796
[2] 
https://github.com/libvips/libvips/commit/ce684dd008532ea0bf9d4a1d89bacb35f4a83f4d

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#927154: aborts on window size change

[Paul Wise]

On Sun, 2019-10-13 at 15:14 +0800, Paul Wise wrote:

> Did you manage to work out how to bisect this?

I managed to get a little bit further in the bisect using the attached
script but I hit a point where the commit isn't easily backportable,
I'll try to continue the backporting another day, spent too long today.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


bisect-run.sh
Description: application/shellscript


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

Bug#942224: asymptote: VIM addon cannot be managed with vim-addons and fails to enable syntax highlighting

[Francesco Poli]

On Sun, 13 Oct 2019 09:29:37 +0900 Norbert Preining wrote:

[...]
> On Sat, 12 Oct 2019, Francesco Poli (wintermute) wrote:
> > But there seem to be two issues: there's no registry file (hence
> 
> Thanks for the explanation - not that I have any idea how to package vim
> addons ;-)

I am a newbie myself, I learned the basics by looking at other packages
shipping VIM addons (such as package vim-scripts) and by reading the
vim-addons(1) and vim-registry(5) man pages (shipped in package
vim-addon-manager).

> 
> I simply followed your advice now and the changes are alread in git,
> see
> https://github.com/debian-tex/asymptote/commit/22616928ec5da97cf1965b9fbaa01d0b0a78d8ad
> 
> Hope that is enough!

Looks OK to me.
Thanks a lot for your very prompt reaction (I wish all bug reports of
mine were acted upon this quickly!).

> 
> All the best

Have a nice evening (in the +0900 time zone...)!


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgp5bCl5fTlMJ.pgp
Description: PGP signature

Bug#942172: clamav-daemon: After upgrade, clamd cannon create /var/run/clamav/clamd.ctl and stop.

[Stefan Hornburg (Racke)]

On 10/12/19 6:32 PM, Hugo Lefeuvre wrote:
> Hi,
> 
> I did not notice this bug during my tests. I have just tried to reproduce
> it by upgrading a jessie system from 0.100.3+dfsg-0+deb8u1 to
> 0.101.4+dfsg-0+deb8u1 and did not experience any issue restarting
> clamav-daemon.
> 
> Furthermore, /var/run/clamav/ belonging to root:root or clamav:root does
> not seem to change anything on my system. My understanding is that
> /var/run/clamav/clamd.ctl is created by systemd, not by the daemon itself.
> 
> Also, I don't think chown clamav /var/run/clamav should survive a restart.
> 
> Filipe: did you also experience this bug?
> 
> Thanks.
> 
> regards,
> Hugo
> 

Hello,

I noticed this problem as well on a few Jessie servers. It looks like it takes 
ClamAV a long time
to read/update the virus definitions and thus hits a timeout set by systemd.

Regards
 Racke

-- 
Ecommerce and Linux consulting + Perl and web application programming.
Debian and Sympa administration. Provisioning with Ansible.



signature.asc
Description: OpenPGP digital signature

Bug#942172: clamav-daemon: After upgrade, clamd cannon create /var/run/clamav/clamd.ctl and stop.

[Sebastian]

Hi Hugo,

On Sun, 13 Oct 2019 10:25:37 +0200 Hugo Lefeuvre  wrote:>
> I have prepared a regression update addressing this issue. It would be a
> true benefit for the quality of this upload if somebody could give it
a try
> before I go on with uploading. You can find (UNRELEASED) amd64 builds,
> signed by myself on my Debian webpage:
>

> https://people.debian.org/~hle/lts/clamav/

I experienced the same bug and these packages are fixing the issue for
me. Many thanks for your efforts!

Sebastian




signature.asc
Description: OpenPGP digital signature

Bug#942266: pulseaudio: Please exclude user root when enable pulseaudio service.

[Corcodel Marian]

Package: pulseaudio
Version: 10.0-1+deb9u1
Severity: normal

Hi
Suppose to enable pulseaudio service
$systemctl --global enable pulseaudio.service, but systemd not know exception
in user 0
and create one instance of pulseaudio inspect
§systemctl --global status pulseaudio.service for more info.



-- Package-specific info:
File '/etc/default/pulseaudio' does not exist


-- System Information:
Debian Release: 9.11
  APT prefers oldstable
  APT policy: (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.0.0-rc6+ (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages pulseaudio depends on:
ii  adduser  3.115
ii  libasound2   1.1.3-5
ii  libasound2-plugins   1.1.1-1
ii  libc62.24-11+deb9u4
ii  libcap2  1:2.25-1
ii  libdbus-1-3  1.10.28-0+deb9u1
ii  libgcc1  1:6.3.0-18+deb9u1
ii  libice6  2:1.0.9-2
ii  libltdl7 2.4.6-2
ii  liborc-0.4-0 1:0.4.26-2
ii  libpulse010.0-1+deb9u1
ii  libsm6   2:1.2.2-1+b3
ii  libsndfile1  1.0.27-3
ii  libsoxr0 0.1.2-2
ii  libspeexdsp1 1.2~rc1.2-1+b2
ii  libstdc++6   6.3.0-18+deb9u1
ii  libsystemd0  232-25+deb9u12
ii  libtdb1  1.3.11-2
ii  libudev1 232-25+deb9u12
ii  libwebrtc-audio-processing1  0.3-1
ii  libx11-6 2:1.6.4-3+deb9u1
ii  libx11-xcb1  2:1.6.4-3+deb9u1
ii  libxcb1  1.12-1
ii  libxtst6 2:1.2.3-1
ii  lsb-base 9.20161125
ii  pulseaudio-utils 10.0-1+deb9u1

Versions of packages pulseaudio recommends:
ii  rtkit  0.11-4+deb9u1

Versions of packages pulseaudio suggests:
pn  paman
pn  paprefs  
ii  pavucontrol  3.0-3.1
pn  pavumeter
ii  udev 232-25+deb9u12

-- no debconf information
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for PulseAudio clients. See pulse-client.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; default-sink =
; default-source =
; default-server =
; default-dbus-server =

; autospawn = yes
; daemon-binary = /usr/bin/pulseaudio
; extra-arguments = --log-target=syslog

; cookie-file =

; enable-shm = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB

; auto-connect-localhost = no
; auto-connect-display = no
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for the PulseAudio daemon. See pulse-daemon.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; daemonize = no
; fail = yes
; allow-module-loading = yes
; allow-exit = yes
; use-pid-file = yes
; system-instance = no
; local-server-type = user
; enable-shm = yes
; enable-memfd = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB
; lock-memory = no
; cpu-limit = no

; high-priority = yes
; nice-level = -11

; realtime-scheduling = yes
; realtime-priority = 5

; exit-idle-time = 20
; scache-idle-time = 20

; dl-search-path = (depends on architecture)

; load-default-script-file = yes
; default-script-file = /etc/pulse/default.pa

; log-target = auto
; log-level = notice
; log-meta = no
; log-time = no
; log-backtrace = 0

; resample-method = speex-float-1
; enable-remixing = yes
; enable-lfe-remixing = no
; 

Bug#942134: dh_shlibdeps: Generating strict local shlibs on packages

[Niels Thykier]

Control: tags -1 moreinfo

On Thu, 10 Oct 2019 20:49:11 +0200 =?utf-8?q?Sandro_Knau=C3=9F?=
 wrote:
> Package: debhelper
> Version: 12.6.1
> Severity: wishlist
> 
> You may end up in a situation, where you want a very strict dependency
> the binary packages of a related packages. This feature is currently
> developed in pkg-kde-tools, but may also be interesting for other
> library packages.
> 
> The code is developed here:
> https://salsa.debian.org/qt-kde-team/pkg-kde-tools/blob/master/qt-kde-team/3/library-packages.mk
> 
> the usage for d/rules:
> 
> include /usr/share/pkg-kde-tools/qt-kde-team/3/library-packages.mk
> 
> libpkgs_gen_strict_local_shlibs = $(libpkgs_all_packages)
> 
> codesearch give following results:
> 
> https://codesearch.debian.net/search?q=libpkgs_gen_strict_local_shlibs=1=1
> 
> Regards,
> 
> hefee
> 
> [...]


Hi,

Can you expand a bit on the use case here or the problem you want to
solve?  At the moment, I cannot see how it is different from having the
following in your d/control file

"""
Depends: other-package (= ${binary:Version}), ...
"""

(Except this one goes in d/control and the case you point to goes in
d/rules)

Thanks,
~Niels

Bug#938169: python-setuptools-git: diff for NMU version 1.2-2.1

[GCS]

Hi Sandro,

On Sun, Oct 13, 2019 at 5:03 AM Sandro Tosi  wrote:
> I've prepared an NMU for python-setuptools-git (versioned as 1.2-2.1) and
> uploaded it to DELAYED/7. Please feel free to tell me if I
> should delay it longer.
 Expect the non-removal of "X-Python-Version" this is fine. With other
changes I'm going to upload it soon.

Thanks,
Laszlo/GCS

Bug#942256: libgloox17: gloox was working on debian stretch but not connecting to server with debian buster

[DebXWoody]

Package: libgloox17
Version: 1.0.22-0.1
Severity: normal

Dear Maintainer,

I'm running a Server with Debian Buster and XMPP Server prosody 0.11.2-1.
Since upgrade from Debian stretch (prosody from Backports) to Debian Buster I'm
not able to connect the Server via gloox. 

Find details on bug tracker of upstream:
https://bugs.camaya.net/ticket/?id=287

-- System Information:
Debian Release: 10.1
  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)
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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libgloox17 depends on:
ii  libc62.28-10
ii  libgcc1  1:8.3.0-6
ii  libgnutls30  3.6.7-4
ii  libidn11 1.33-2.2
ii  libstdc++6   8.3.0-6
ii  zlib1g   1:1.2.11.dfsg-1

libgloox17 recommends no packages.

libgloox17 suggests no packages.

-- no debconf information

Bug#916467: Also seems to affect bridged interfaces

[Alex DEKKER]

I suspect this issue affects bridged interfaces as well. Watching the 
boot process, I can see the DAD attempt being sent before any interfaces 
have transitioned to Forwarding state.  I don't see how this is any use 
because no neighbours would ever see the ND packets!

Bug#927154: aborts on window size change

[Paul Wise]

On Sun, 2019-10-13 at 16:37 +0800, Paul Wise wrote:

> I managed to get a little bit further in the bisect using the attached
> script but I hit a point where the commit isn't easily backportable,
> I'll try to continue the backporting another day, spent too long today.

I thought about it a bit more logically and I went back to the first
commit that added support for using IO::Pty::Easy to supervise the
output of the command and added a new commit to make it just use read
instead of read and is_active. The result was that I could reproduce
the bug even with that commit. So when running on bullseye the issue
appears to have been there from the beginning.

I guess the next step would be to bisect the dependencies between
stretch and buster, so I guess that is basically Perl only?

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#942258: ifupdown: Failure to bring up br0 causes pppd to be terminated

[Alex DEKKER]

Package: ifupdown
Version: 0.8.35+b1
Severity: normal

Dear Maintainer,

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

   * What led up to the situation?

IPv6 DAD "fails" on br0. ifupdown then terminates the PPPoE client running on 
eth3 [eth3 is not part of br0]


   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?
I expect that failure to bring up one interface will not cause the ifupdown to 
terminate pppd on a different interface. 


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


-- Package-specific info:
--- /etc/network/interfaces:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback


# from https://wiki.debian.org/BridgeNetworkConnections

#iface eth7 inet manual
# br0, LAN
auto br0
iface br0 inet static
bridge_ports eth7 enp3s0f0 enp3s0f1 enp4s0f0 enp4s0f1
address 192.168.1.3
netmask 255.255.255.0
bridge_stp on
#   bridge_maxwait 0
#   bridge_fd 0

iface br0 inet6 static
address 2001:db8::1
netmask 64
dad-attempts 0
# without the above, br0 will fail to come up



## eth3, connected to NTE

auto ppp0
iface ppp0 inet ppp
pre-up /bin/ip link set eth3 mtu 1508
pre-up /bin/ip link set eth3 up
provider provider
post-up sh /root/firewall/delayed-post-up.sh
#   post-up sleep 10

--- up and down scripts installed:
/etc/network/if-down.d:
total 4
-rwxr-xr-x 1 root root 289 Jan 17  2018 bind9

/etc/network/if-post-down.d:
total 0
lrwxrwxrwx 1 root root 29 Jan 27  2019 bridge -> /lib/bridge-utils/ifupdown.sh

/etc/network/if-pre-up.d:
total 4
lrwxrwxrwx 1 root root  29 Jan 27  2019 bridge -> /lib/bridge-utils/ifupdown.sh
-rwxr-xr-x 1 root root 344 Jun  7  2010 ethtool

/etc/network/if-up.d:
total 16
-rwxr-xr-x 1 root root  289 Jan 17  2018 bind9
-rwxr-xr-x 1 root root 1685 Sep 22  2014 ethtool
-rwxr-xr-x 1 root root 4937 Aug 22 16:39 mountnfs


-- 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.2.0-3-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1), 
LANGUAGE=en_GB:en_US:en_GB:en (charmap=ISO-8859-1)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages ifupdown depends on:
ii  adduser   3.118
ii  iproute2  5.3.0-1
ii  libc6 2.29-2
ii  lsb-base  11.1.0

Versions of packages ifupdown recommends:
pn  isc-dhcp-client | dhcp-client  

Versions of packages ifupdown suggests:
ii  ppp 2.4.7-2+4.1+b1
pn  rdnssd  

-- Configuration Files:
/etc/default/networking changed:
VERBOSE=yes


-- debconf information:
  ifupdown/convert-interfaces: true

Bug#942200: rollup 1.0 transition: node-d3 built with rollup 1.0 gives error in test

[Pirate Praveen]

On Sat, 12 Oct 2019 13:04:10 +0530 Pirate Praveen
 wrote:
> package: node-d3
> version: 4.13.0-10

With node-d3 5.12, build succeeds and one test fails,

# version matches package.json
ok 1 should be equal
# d3.event is a getter for d3Selection.event
ok 2 should be equal
not ok 3 should be equal
  ---
operator: equal
expected: 42
actual:   null
at: Test. (/<>/test/d3-test.js:15:10)
stack: |-
  Error: should be equal
  at Test.assert [as _assert]
(/usr/lib/nodejs/tape/lib/test.js:235:54)
  at Test.bound [as _assert]
(/usr/lib/nodejs/tape/lib/test.js:87:32)
  at Test.equal (/usr/lib/nodejs/tape/lib/test.js:395:10)
  at Test.bound [as equal] (/usr/lib/nodejs/tape/lib/test.js:87:32)
  at Test. (/<>/test/d3-test.js:15:10)
  at Test.bound [as _cb] (/usr/lib/nodejs/tape/lib/test.js:87:32)
  at Test.run (/usr/lib/nodejs/tape/lib/test.js:106:10)
  at Test.bound [as run] (/usr/lib/nodejs/tape/lib/test.js:87:32)
  at Immediate.next [as _onImmediate]
(/usr/lib/nodejs/tape/lib/results.js:71:15)
  at runCallback (timers.js:705:18)
  ...

Bug#940815: zathura: Mouse wheel zoom inconsistent with girara >= 0.3.3

[Sebastian Ramacher]

Control: forwarded -1 https://git.pwmt.org/pwmt/zathura/issues/114
Control: tags -1 + upstream fixed-upstream

On 2019-09-20 09:43:57, Jakob Haufe wrote:
> Package: zathura
> Version: 0.4.4-1
> Severity: normal
> 
> With girara 0.3.3 enabling smooth-scroll reporting by default, mouse wheel
> zooming in zathura became inconsistent for me (in comparison to
> keyboard zooming).
> 
> The first issue is the zooming direction being inverted, the other is
> the zoom level jumping to minimum when going below 1.0.

This issue was fixed upstream.

Cheers

> 
> On my system, event.y is either -1 or +1.
> 
> Please see the following table for resulting zoom values (calculated
> manually given zoom-step==10).
> 
> old_zoom  ZOOM_IN  ZOOM_OUT  SMOOTH -1  SMOOTH +1
> 0,1   0,11 0,09  -1 1,2
> 0,2   0,22 0,18  -0,9   1,3
> 0,3   0,33 0,27  -0,8   1,4
> 0,4   0,44 0,36  -0,7   1,5
> 0,5   0,55 0,45  -0,6   1,6
> 0,6   0,66 0,55  -0,5   1,7
> 0,7   0,77 0,64  -0,4   1,8
> 0,8   0,88 0,73  -0,3   1,9
> 0,9   0,99 0,82  -0,2   2
> 1 1,1  0,91  -0,1   2,1
> 1,1   1,21 1 0  2,2
> 1,2   1,32 1,09  0,12,3
> 1,3   1,43 1,18  0,22,4
> 1,4   1,54 1,27  0,32,5
> 1,5   1,65 1,36  0,42,6
> 1,6   1,76 1,45  0,52,7
> 1,7   1,87 1,55  0,62,8
> 1,8   1,98 1,64  0,72,9
> 1,9   2,09 1,73  0,83
> 2 2,2  1,82  0,93,1
> 2,1   2,31 1,91  1  3,2
> 2,2   2,42 2 1,13,3
> 2,3   2,53 2,09  1,23,4
> 2,4   2,64 2,18  1,33,5
> 2,5   2,75 2,27  1,43,6
> 2,6   2,86 2,36  1,53,7
> 2,7   2,97 2,45  1,63,8
> 2,8   3,08 2,55  1,73,9
> 2,9   3,19 2,64  1,84
> 3 3,3  2,73  1,94,1
> 
> Downgrading to libgirara-gtk3-3=0.3.3-1 and zathura=0.4.3-1 (from
> buster) hides the problem, but even those versions can show it when
> setting smooth-scroll to true in zathurarc.
> 
> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers testing
>   APT policy: (990, 'testing'), (500, 'testing-debug'), (500, 
> 'stable-debug'), (500, 'unstable'), (500, 'stable'), (1, 
> 'experimental-debug'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 5.2.0-2-amd64 (SMP w/2 CPU cores)
> Kernel taint flags: TAINT_PROPRIETARY_MODULE, 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: systemd (via /run/systemd/system)
> 
> Versions of packages zathura depends on:
> ii  libc62.29-1
> ii  libcairo21.16.0-4
> ii  libgirara-gtk3-3 0.3.3-1
> ii  libglib2.0-0 2.60.6-2
> ii  libgtk-3-0   3.24.11-1
> ii  libmagic11:5.37-5
> ii  libpango-1.0-0   1.42.4-7
> ii  libseccomp2  2.4.1-2
> ii  libsqlite3-0 3.29.0-2
> ii  libsynctex2  2019.20190605.51237-2
> ii  zathura-pdf-poppler  0.2.9-1
> 
> zathura recommends no packages.
> 
> Versions of packages zathura suggests:
> ii  dillo [www-browser]3.0.5-5+b1
> ii  firefox [www-browser]  69.0-1
> ii  links [www-browser]2.20.1-1
> ii  lynx [www-browser] 2.9.0dev.4-1
> ii  w3m [www-browser]  0.5.3-37+b1
> ii  zathura-cb 0.1.8-2
> ii  zathura-djvu   0.2.8-1
> ii  zathura-ps 0.2.6-1
> 
> -- no debconf information



-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#942262: transition: x265

[Emilio Pozuelo Monfort]

On 13/10/2019 13:47, Sebastian Ramacher wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> Control: forwarded -1 
> https://release.debian.org/transitions/html/auto-x265.html
> 
> x265 bumped its SONAME to 179 and the new upstream release is staged in
> experimental. All reverse dependencies build fine against the new
> version.

If the package builds fine in the remaining release architectures (I have just
bumped the build prio) you can go ahead.

Cheers,
Emilio

Bug#942126: (no subject)

[bert]

thanks for investigating, Mad Horse.
For me to get things working, all I did was install fuse3, which
provides /bin/fusermount as well as /bin/fusermount3.
So I guess all that was missing was the fuse3 dependency.

Bug#942200: [Pkg-javascript-devel] Bug#942200: rollup 1.0 transition: node-d3 built with rollup 1.0 gives error in test

[Pirate Praveen]

On Sun, Oct 13, 2019 at 20:15, Pirate Praveen 
 wrote:
This seems like a bug in rollup 1.0.2. Using with rollup 1.0.2 in 
package.json, npm i; npm run test also fails. Works fine with rollup 
1.8.


Now trying to update to 1.10.1 (which also works).

Found debian/nodejs/./build
cd ./. && sh -e debian/nodejs/./build
src/Module.ts:5:34 - error TS2307: Cannot find module 
'rollup-pluginutils/src/extractAssignedNames'.


5 import extractAssignedNames from 
'rollup-pluginutils/src/extractAssignedNames';
  
~


src/watch/index.ts:4:26 - error TS2307: Cannot find module 
'rollup-pluginutils/src/createFilter'.


4 import createFilter from 'rollup-pluginutils/src/createFilter';
  ~


Found 4 errors.

We'll need to update node-rollup-pluginutils to 2.6 and drop src_babel 
generation as tsc can consume ES module directly. I'm going to try this 
tomorrow.

Bug#942260: pulseaudio: The pulseaudio use id for normal user.

[Corcodel Marian]

Package: pulseaudio
Version: 10.0-1+deb9u1
Severity: normal

Inspect /etc/passwd and see on user pulse uid and guid number upper 1000 , this
is bad wich in not normal user, i replaced with 999 on both places , solved on
kdm manager to hide user pulse on login.



-- Package-specific info:
File '/etc/default/pulseaudio' does not exist


-- System Information:
Debian Release: 9.11
  APT prefers oldstable
  APT policy: (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.0.0-rc6+ (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages pulseaudio depends on:
ii  adduser  3.115
ii  libasound2   1.1.3-5
ii  libasound2-plugins   1.1.1-1
ii  libc62.24-11+deb9u4
ii  libcap2  1:2.25-1
ii  libdbus-1-3  1.10.28-0+deb9u1
ii  libgcc1  1:6.3.0-18+deb9u1
ii  libice6  2:1.0.9-2
ii  libltdl7 2.4.6-2
ii  liborc-0.4-0 1:0.4.26-2
ii  libpulse010.0-1+deb9u1
ii  libsm6   2:1.2.2-1+b3
ii  libsndfile1  1.0.27-3
ii  libsoxr0 0.1.2-2
ii  libspeexdsp1 1.2~rc1.2-1+b2
ii  libstdc++6   6.3.0-18+deb9u1
ii  libsystemd0  232-25+deb9u12
ii  libtdb1  1.3.11-2
ii  libudev1 232-25+deb9u12
ii  libwebrtc-audio-processing1  0.3-1
ii  libx11-6 2:1.6.4-3+deb9u1
ii  libx11-xcb1  2:1.6.4-3+deb9u1
ii  libxcb1  1.12-1
ii  libxtst6 2:1.2.3-1
ii  lsb-base 9.20161125
ii  pulseaudio-utils 10.0-1+deb9u1

Versions of packages pulseaudio recommends:
ii  rtkit  0.11-4+deb9u1

Versions of packages pulseaudio suggests:
pn  paman
pn  paprefs  
ii  pavucontrol  3.0-3.1
pn  pavumeter
ii  udev 232-25+deb9u12

-- no debconf information
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for PulseAudio clients. See pulse-client.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; default-sink =
; default-source =
; default-server =
; default-dbus-server =

; autospawn = yes
; daemon-binary = /usr/bin/pulseaudio
; extra-arguments = --log-target=syslog

; cookie-file =

; enable-shm = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB

; auto-connect-localhost = no
; auto-connect-display = no
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for the PulseAudio daemon. See pulse-daemon.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; daemonize = no
; fail = yes
; allow-module-loading = yes
; allow-exit = yes
; use-pid-file = yes
; system-instance = no
; local-server-type = user
; enable-shm = yes
; enable-memfd = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB
; lock-memory = no
; cpu-limit = no

; high-priority = yes
; nice-level = -11

; realtime-scheduling = yes
; realtime-priority = 5

; exit-idle-time = 20
; scache-idle-time = 20

; dl-search-path = (depends on architecture)

; load-default-script-file = yes
; default-script-file = /etc/pulse/default.pa

; log-target = auto
; log-level = notice
; log-meta = no
; log-time = no
; log-backtrace = 0

; resample-method = speex-float-1
; enable-remixing = yes
; enable-lfe-remixing = no
; lfe-crossover-freq = 0

; flat-volumes = 

Bug#942258: Logs from boot

[Alex DEKKER]

This is what happens without dad-attempts 0 on br0:


Oct 13 10:31:30 westogre pppd[2055]: rcvd [IPCP ConfAck id=0x2 81.x.x.x>]

Oct 13 10:31:30 westogre pppd[2055]: local  IP address 81.x.x.x
Oct 13 10:31:30 westogre pppd[2055]: remote IP address 81.187.81.187
Oct 13 10:31:30 westogre pppd[2055]: Script /etc/ppp/ip-up started (pid 
2087)
Oct 13 10:31:30 westogre pppd[2055]: rcvd [IPV6CP ConfReq id=0x0 fe80::0203:97ff:fe40:4000>]
Oct 13 10:31:30 westogre pppd[2055]: sent [IPV6CP ConfAck id=0x0 fe80::0203:97ff:fe40:4000>]
Oct 13 10:31:30 westogre pppd[2055]: local  LL address 
fe80::4094:d1c2:9863:b1a5
Oct 13 10:31:30 westogre pppd[2055]: remote LL address 
fe80::0203:97ff:fe40:4000
Oct 13 10:31:30 westogre pppd[2055]: Script /etc/ppp/ipv6-up started 
(pid 2088)
Oct 13 10:31:30 westogre pppd[2055]: Script /etc/ppp/ipv6-up finished 
(pid 2088), status = 0x0
Oct 13 10:31:31 westogre ifup[1521]: /bin/run-parts --exit-on-error 
--verbose /etc/network/if-up.d
Oct 13 10:31:31 westogre ifup[1521]: run-parts: executing 
/etc/network/if-up.d/bind9
Oct 13 10:31:31 westogre ifup[1521]: run-parts: executing 
/etc/network/if-up.d/ethtool
Oct 13 10:31:31 westogre ifup[1521]: run-parts: executing 
/etc/network/if-up.d/mountnfs
Oct 13 10:31:31 westogre ifup[1521]: /bin/run-parts --exit-on-error 
--verbose /etc/network/if-up.d
Oct 13 10:31:31 westogre ifup[1521]: run-parts: executing 
/etc/network/if-up.d/bind9
Oct 13 10:31:31 westogre ifup[1521]: run-parts: executing 
/etc/network/if-up.d/ethtool
Oct 13 10:31:31 westogre ifup[1521]: run-parts: executing 
/etc/network/if-up.d/mountnfs
Oct 13 10:31:31 westogre systemd[1]: networking.service: Main process 
exited, code=exited, status=1/FAILURE

Oct 13 10:31:31 westogre pppd[2055]: Terminating on signal 15
Oct 13 10:31:31 westogre pppd[2055]: Connect time 0.1 minutes.
Oct 13 10:31:31 westogre pppd[2055]: Sent 242 bytes, received 0 bytes.
Oct 13 10:31:31 westogre pppd[2055]: Script /etc/ppp/ipv6-down started 
(pid 2170)
Oct 13 10:31:31 westogre pppd[2055]: sent [LCP TermReq id=0x2 "User 
request"]
Oct 13 10:31:31 westogre pppd[2055]: Child process /etc/ppp/ip-up (pid 
2087) terminated with signal 15
Oct 13 10:31:31 westogre pppd[2055]: Script /etc/ppp/ip-down started 
(pid 2171)
Oct 13 10:31:31 westogre pppd[2055]: Script /etc/ppp/ipv6-down finished 
(pid 2170), status = 0x0

Oct 13 10:31:31 westogre pppd[2055]: rcvd [LCP TermAck id=0x2]
Oct 13 10:31:31 westogre pppd[2055]: Connection terminated.
Oct 13 10:31:31 westogre pppd[2055]: Connect time 0.1 minutes.
Oct 13 10:31:31 westogre pppd[2055]: Sent 242 bytes, received 0 bytes.
Oct 13 10:31:31 westogre pppd[2055]: Send PPPOE Discovery V1T1 PADT 
session 0x214 length 20
Oct 13 10:31:31 westogre pppd[2055]:  dst 28:8a:1c:e9:c0:52  src 
00:19:99:ed:01:9a
Oct 13 10:31:31 westogre pppd[2055]:  [AC-cookie  33 58 9a 5b 57 42 46 
f7 fc e5 5e 6f d0 b3 47 8c]

Oct 13 10:31:31 westogre pppd[2055]: Sent PADT
Oct 13 10:31:31 westogre pppd[2055]: Waiting for 1 child processes...
Oct 13 10:31:31 westogre pppd[2055]:   script /etc/ppp/ip-down, pid 2171
Oct 13 10:31:31 westogre pppd[2055]: Script /etc/ppp/ip-down finished 
(pid 2171), status = 0x1

Oct 13 10:31:31 westogre pppd[2055]: Exit.
Oct 13 10:31:31 westogre systemd[1]: networking.service: Failed with 
result 'exit-code'.
Oct 13 10:31:31 westogre systemd[1]: Failed to start Raise network 
interfaces.

Oct 13 10:31:31 westogre systemd[1]: Reached target Network.

The irony of this is that br0 is configured absolutely fine, it's ppp0 
that suffers!

Bug#941078: transition: postgresql-12

[Christoph Berg]

Re: Emilio Pozuelo Monfort 2019-10-12 
<09c44ee4-1bee-bc9a-43fd-64fbbdf5c...@debian.org>
> Go ahead.

Thanks. We'll start as soon as postgresql-12 is in testing to minimize
any possible entanglement with other transitions.

Christoph

Bug#942055: ghostscript in buster partly broken on armel?

[Alexander Reichle-Schmehl]

reassign 942055 ghostscript
severity 942055 important
found 942055 9.27~dfsg-2+deb10u1
thanks


Dear Maintainer,

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

   * What led up to the situation?
 I upgraded my server running on armel from stretch to buster. Since
 then I was unable to print pictures via my cups server installed on
 the armel system.
   * What exactly did you do (or not do) that was effective (or
   * What was the outcome of this action?
 ineffective)?
 Printing the cups test page results in just the test being printed,
 not the images. Same for other documents.
   * What outcome did you expect instead?
 Testpage should print with images :)

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

After the upgrade from stretch to buster, I noticed that I can't images
anymore. When printing pages with images, the part of the page is
usually left empty.  Same problem with text containing special
characters.

Installing cups on my amd64 notebook, I can print without problems
anymore, so it doesn't seem to be a general problem.

Downgrading the ghostscript pagages to the version in Debian 9 solved my
issues.


Please feel free to contact me for futher tests or debugg output.  I
grant that this issue might not be easy to reproduce ;)


Best regards,
  Alexander


-- System Information:
Debian Release: 10.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: armel (armv5tel)

Kernel: Linux 4.19.0-5-marvell
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: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages cups-filters depends on:
ii  bc 1.07.1-2+b1
ii  cups-filters-core-drivers  1.21.6-5
hi  ghostscript9.26a~dfsg-0+deb9u5
ii  libc6  2.28-10
ii  libcups2   2.2.10-6+deb10u1
ii  libcupsfilters11.21.6-5
ii  libcupsimage2  2.2.10-6+deb10u1
ii  libfontconfig1 2.13.1-2
ii  libfontembed1  1.21.6-5
ii  libgcc11:8.3.0-6
ii  libqpdf21  8.4.0-2
ii  libstdc++6 8.3.0-6
ii  poppler-utils  0.71.0-5

Versions of packages cups-filters recommends:
ii  colord 1.4.3-4
ii  liblouisutdml-bin  2.7.0-5+b1

Versions of packages cups-filters suggests:
pn  antiword   
pn  docx2txt   
ii  foomatic-db-compressed-ppds [foomatic-db]  20181217-2
ii  imagemagick8:6.9.10.23+dfsg-2.1
ii  imagemagick-6.q16 [imagemagick]8:6.9.10.23+dfsg-2.1

-- no debconf information

Bug#939364: stretch-pu: package python-acme/0.28.0-1~deb9u2

[Adam D. Barratt]

Control: tags -1 + confirmed

On Tue, 2019-09-03 at 22:16 -0400, Harlan Lieberman-Berg wrote:
> We have a proposed update for acme in stretch (oldstable).  This is
> necessary to prevent the package, and all its dependencies, stopping
> to work due to changes to the web service that the acme module is
> primarily used for.  (Let's Encrypt)
> 

Apologies for the delay. Please go ahead.

Regards,

Adam

Bug#942258: Logs from boot

[Guus Sliepen]

On Sun, Oct 13, 2019 at 11:05:23AM +0100, Alex DEKKER wrote:

> This is what happens without dad-attempts 0 on br0:
> 
[...]
> Oct 13 10:31:31 westogre ifup[1521]: run-parts: executing
> /etc/network/if-up.d/mountnfs
> Oct 13 10:31:31 westogre systemd[1]: networking.service: Main process
> exited, code=exited, status=1/FAILURE
> Oct 13 10:31:31 westogre pppd[2055]: Terminating on signal 15
[...]
> Oct 13 10:31:31 westogre pppd[2055]: Exit.
> Oct 13 10:31:31 westogre systemd[1]: networking.service: Failed with result
> 'exit-code'.

I think the issue is that systemd kills the pppd process when ifup
reports an error bringing up br0. And that's probably because ppp0 was
brought up during startup of the networking service, and thus systemd
keeps track of all processes spawned at that time.

A possible workaround is to make ppp0 bringup not part of the network
initialization, but rather during the "hotplug" event of eth3. So
instead of having:

auto ppp0
iface ppp0 inet ppp
...

Write this:

allow-hotplug eth3

iface eth3 inet manual
mtu 1508
up ifup ppp0
down ifdown ppp0

iface ppp0 inet ppp
provider provider
post-up sh /root/firewall/delayed-post-up.sh

Note that hotplug doesn't mean when the cable is plugged in, it means
when the system detects the network card hardware. And for a built-in
network card, it detects it at boot time. So effectively you still get
ppp0 brought up at boot time this way.

-- 
Met vriendelijke groet / with kind regards,
  Guus Sliepen 


signature.asc
Description: PGP signature

Bug#942261: reportbug: When searching for executables in packages, consider full PATH not first match

[Witold Baryluk]

Package: reportbug
Version: 7.5.3
Severity: normal

Hi,

I just noticed this issue with reportbug;

$ reportbug date
*** Welcome to reportbug.  Use ? for help at prompts. ***
Note: bug reports are publicly archived (including the email address of the 
submitter).
Detected character set: UTF-8
Please change your locale if this is incorrect.

Using 'Witold Baryluk ' as your from address.
Getting status for date...
W: Unable to locate package date
No matching source or binary packages.
A package named "date" does not appear to be installed; do you want to search 
for a similar-looking filename in an installed
package [Y|n|q|?]? 
Finding package for 'date'...
Resolved as '/usr/bin/date'.
No packages match.
This package does not appear to be installed; continue with this report 
[y|N|q|?]? 
reportbug: exiting due to user interrupt.
$

$ echo $PATH
/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
$


$ dpkg -S /usr/bin/date
dpkg-query: no path found matching pattern /usr/bin/date
$

$ dpkg -S /bin/date
coreutils: /bin/date
$

$ ls -l / | grep bin
lrwxrwxrwx   1 root root7 Oct 10 14:23 bin -> usr/bin
lrwxrwxrwx   1 root root8 Oct 10 14:23 sbin -> usr/sbin
$


reportbug can probably be smarter here about this.

There might be multiple ways to solve this problem, but one of the
simpler ones might be to inspect all elements of PATH, or add special
cases for {/usr,}/bin and {/usr,}/sbin.

Best regards,
Witold


-- Package-specific info:
** Environment settings:
INTERFACE="text"

** /home/user/.reportbugrc:
reportbug_version "7.5.3"
mode standard
ui text
realname "Witold Baryluk"
email "witold.bary...@gmail.com"
no-cc
list-cc-me
smtphost reportbug.debian.org

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

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

Versions of packages reportbug depends on:
ii  apt1.8.4
ii  python33.7.5-1
ii  python3-reportbug  7.5.3
ii  sensible-utils 0.0.12

reportbug recommends no packages.

Versions of packages reportbug suggests:
ii  claws-mail 3.17.4-1+b1
pn  debconf-utils  
ii  debsums2.2.3
pn  dlocate
ii  emacs-bin-common   1:26.3+1-1
ii  exim4-daemon-light [mail-transport-agent]  4.92.2-3+b1
ii  file   1:5.37-5
ii  gnupg  2.2.17-3
ii  python3-urwid  2.0.1-2+b1
pn  reportbug-gtk  
ii  xdg-utils  1.1.3-1

Versions of packages python3-reportbug depends on:
ii  apt1.8.4
ii  file   1:5.37-5
ii  python33.7.5-1
ii  python3-apt1.8.4
ii  python3-debian 0.1.36
ii  python3-debianbts  2.8.2
ii  python3-requests   2.21.0-1
ii  sensible-utils 0.0.12

python3-reportbug suggests no packages.

-- no debconf information

Bug#942126: gvfs-fuse: /run/user/ID/gvfs/ empty after upgrade

[Mad Horse]

Hello Cesare,

If I try to invoke $ /usr/lib/gvfs/gvfsd-fuse /run/user/${myuid}/gvfs , it 
reports:

> fuse: failed to exec fusermount3: No such file or directory

So, the real problem is that gvfs-fuse is hardcoded to call fusermount3 instead 
fusermount.

It may be walked around by creating an alternative with

> # update-alternatives --install /bin/fusermount3 fusermount3 /bin/fusermount 
> 10

which may means it had better use the alternative system to provide 
/bin/fusermount

between fuse"2" and fuse3, and let gvfsd-fuse and other fuse mounters call 
/bin/fusermount directly.

Best regard,

Mad Horse

Bug#927154: aborts on window size change

[Paul Wise]

On Tue, 16 Apr 2019 13:03:28 -0400 Antoine Beaupré wrote:

> Okay, so here's an interesting data point. On Debian stretch, I can't
> reproduce the bug, even when running from git, using on current master
> (1.20180726-30-g6cf8003).
> 
> So maybe something else is going on here, outside of myrepos itself...
> 
> I'll try to reproduce with the cherry-picking when I get back home on
> that buster machine later.

Did you manage to work out how to bisect this?

Did you manage to figure out the stretch/buster difference?
I see that libio-pty-perl libio-pty-easy-perl are the same version.

I've found a workaround:

   my $pty = IO::Pty::Easy->new(handle_pty_size => 0);

After editing the IO::Pty::Easy code I found that when IO::Pty::Easy
sets $SIG{WINCH} then the error happens, even if the function it sets
as SIGWINCH handler does nothing at all.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#941917: nginx: FTBFS on several architectures: luajit.h: No such file or directory

[Christos Trochalakis]

On Mon, Oct 07, 2019 at 06:16:48PM +0300, Niko Tyni wrote:

This package failed to build from source on arm64, mips64el, ppc64el
and s390x, but earlier versions built there successfully in the past.

This is preventing 1.16.1-1 testing migration and is a blocker for
the ongoing Perl 5.30 transition.

See https://buildd.debian.org/status/package.php?p=nginx=unstable

From the arm64 log:

 cc -c -fPIC -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC -Wdate-time -D_FORTIFY_SOURCE=2 -DNDK_SET_VAR -I src/core -I src/event -I src/event/modules -I src/os/unix -I 
src/http/modules/perl -I /<>/debian/modules/http-ndk/objs -I objs/addon/ndk -I /<>/debian/modules/http-ndk/src -I 
/<>/debian/modules/http-ndk/objs -I objs/addon/ndk -I /<>/debian/modules/nchan/src -I 
/<>/debian/modules/http-lua/src/api -I /usr/include/lua5.1 -I /<>/debian/modules/rtmp -I /usr/include/libxml2 -I objs -I src/http -I 
src/http/modules -I src/http/v2 -I /<>/debian/modules/http-ndk/src -I src/mail -I src/stream \
-o objs/addon/src/ngx_http_lua_log.o \
/<>/debian/modules/http-lua/src/ngx_http_lua_log.c
 In file included from 
/<>/debian/modules/http-lua/src/ngx_http_lua_script.h:11,
  from 
/<>/debian/modules/http-lua/src/ngx_http_lua_script.c:13:
 /<>/debian/modules/http-lua/src/ngx_http_lua_common.h:20:10: 
fatal error: luajit.h: No such file or directory
20 | #include 
   |  ^~
 compilation terminated.
 make[3]: *** [objs/Makefile:2443: objs/addon/src/ngx_http_lua_script.o] Error 1



Sorry for the long delay. I uploaded 1.16.1-2 yesterday which downgrades
http-lua to v0.0.13, the last working version, to unblock the perl
transition.

Copying from the http-lua's README (master, not yet released v0.0.16):
https://github.com/openresty/lua-nginx-module


Since version v0.10.16 of this module, the standard Lua interpreter
(also known as "PUC-Rio Lua") is not supported anymore.


So I am working on a patch that skips building the module for non luajit
archs.

Bug#942172: clamav-daemon: After upgrade, clamd cannon create /var/run/clamav/clamd.ctl and stop.

[Hugo Lefeuvre]

Hi Filipe,

> I did strike this in three boxes. Straight upgrade but opted not to touch
> config when asked. Don't know if it matters. However I did not find any
> reference to /etc/systemd/system/clamav-daemon.service.d/extend.conf in the
> package scripts as in stretch.
> 
> The chown did make the difference. And the extend.conf prior to the upgrade
> on further two boxes got the upgrade working, AFAICT.

thanks for your answer.

After further investigations, I have found a probable cause for this issue:
debian/patches/clamd_dont_depend_on_clamav_demon_socket.patch was
mistakenly backported from the stretch upload.

This should not have been backported, because the jessie package is still
providing the systemd socket, which was removed from the stretch package in
0.99.2+dfsg-3 because of #824042[0].

I did not backport this removal because I considered it too intrusive for a
security upload. Looking back, this was maybe a mistake because it
increased the complexity of the backport.

I have prepared a regression update addressing this issue. It would be a
true benefit for the quality of this upload if somebody could give it a try
before I go on with uploading. You can find (UNRELEASED) amd64 builds,
signed by myself on my Debian webpage:

https://people.debian.org/~hle/lts/clamav/

regards,
Hugo

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

-- 
Hugo Lefeuvre (hle)|www.owl.eu.com
RSA4096_ 360B 03B3 BF27 4F4D 7A3F D5E8 14AA 1EB8 A247 3DFD
ed25519_ 37B2 6D38 0B25 B8A2 6B9F 3A65 A36F 5357 5F2D DC4C


signature.asc
Description: PGP signature

Bug#942255: libmatio: CVE-2019-17533

[Salvatore Bonaccorso]

Source: libmatio
Version: 1.5.17-3
Severity: important
Tags: security upstream

Hi,

The following vulnerability was published for libmatio.

CVE-2019-17533[0]:
| Mat_VarReadNextInfo4 in mat4.c in MATIO 1.5.17 omits a certain '\0'
| character, leading to a heap-based buffer over-read in strdup_vprintf
| when uninitialized memory is accessed.


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-2019-17533
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17533
[1] https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=16856
[2] 
https://github.com/tbeu/matio/commit/651a8e28099edb5fbb9e4e1d4d3238848f446c9a

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#940168: libreoffice-writer: Display black frame when importing a png-image.

[Rene Engelhard]

Hi,

On Fri, Sep 13, 2019 at 11:02:53AM +0200, Johann Spies wrote:
> *** Reporter, please consider answering these questions, where appropriate ***
> 
>* What led up to the situation?
> 
>I had to import my signature (png) into a document sent to me.
> 
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> 
>  I have checked the image with Gimp and could successfully import
>  it into Abiword.
>  
>* What was the outcome of this action?
> 
>The image displayed as solid black in the writer document.
>
>* What outcome did you expect instead?
> 
>The image to show my signature.
> 
> *** End of the template - remove these template lines ***

I recall some fixes wrt this in 6.3.3 rc1? Can you please test?

See http://people.debian.org/~rene/libreoffice/6.3  

(apt-gettable via "deb http://people.debian.org/~rene/libreoffice/6.3 ./"   

in sources.list, but you should know that..)

Regards,

Rene

Bug#942122: does not fallback to ipv4 when ipv6 fails

[Eduard Bloch]

Hallo,
* Antoine Beaupre [Thu, Oct 10 2019, 12:36:21PM]:
> Package: apt-cacher-ng
> Version: 3.2-2
> Severity: normal
> Tags: ipv6
>
> apt-cacher-ng does not deal well with dual-stack failures. At home I
> regularly have trouble with my IPv6 connexions, which just hang. Most
> applications are able to recover from this and fallback to IPv4, which
> just works. This is therefore mostly transparent to users, at worst
> there's a slight delay during the switchover.

Okay, I agree. I also experience such situations, rarely, when the
crap modem from my provider gets upset and fails to route IPv6 (but
still reports full IPv6 connectivity in its diagnostics).

> The way to deal with this is documented in RFC 8305 and is generally
> refered to as "happy eyeballs":
>
> https://en.wikipedia.org/wiki/Happy_Eyeballs

Not sure this is feasible exactly the way they describe there. This RFC
is apparently mostly by DNS timing behavior but ACNG currently uses
getaddrinfo which delivers all collected DNS data at once.

What I intend to implement instead is a similar scheme:

a) get all DNS records like ATM
b) filter to IPv4 or IPv6 or both (depending on user preference in 
 setting)
c) auto-sort the list so that the first entry is v4 or v6 (depending on 
 preference) and the following ones are alternativing
d) start connecting on the first entry
e) when nothing happened after N seconds, start a second connection attempt in 
parallel (using the second address, which is of different family then)
f) if the second background connect attmpt fails after N, abort it, try the 
next DNS entry in the sequence, etc. etc. (while the first connect attempt is 
still ongoing, until  seconds is reached)

Questions:

a) do you consider this reasonable enough?
b) would you like to become a tester for this, in case you can reproduce
this regularly? (I can fake the test case but nothing beats the real
thing)
c) any good name proposal for N? I think about "FastTimeout" (vs. 
NetworkTimeout)
d) good default value for N? I'd consider 5s (while NetworkTimeout: 60s 
currently)

Best regards,
Eduard.

Bug#941432: [pkg-uWSGI-devel] Bug#941432: Bug#941432: Bug#941432: Bug#941432: Bug#941432: uwsgi-core: Dependency libmatheval is getting out of bullseye

[Alexandre Rossi]

Le 13 octobre 2019 01:04:46 GMT+02:00, "Pierre-Elliott Bécue"  
a écrit :
>Le jeudi 03 octobre 2019 à 11:50:48+0200, Jonas Smedegaard a écrit :
>> Quoting Alexandre Rossi (2019-10-02 15:04:54)
>> > > > > > Do you have plans/solutions regarding this issue? Is it
>possible 
>> > > > > > to drop uwsgi-core dependency on libmatheval1?
>> > > > > 
>> > > > > It should be as simple as not building the matheval plugin
>which is 
>> > > > > not critical to uwsgi. Should I go on with this?
>> > > > 
>> > > > Yeah, I just wasn't sure that it'd be an acceptable solution
>for you.
>> > > > 
>> > > > But it's perfectly fine with me. :)
>> > > 
>> > > Well, I would say "tolerable" rather than "acceptable" - it is a
>real 
>> > > annoyance since it will directly remove features now offered in
>uwsgi.
>> > 
>> > upstream says in 1.9.20 changelog:
>> > 
>> > The matheval support has been removed, while a generic
>“matheval” plugin
>> > (for internal routing) is available (but not compiled in by
>default).
>> > See below for the new way for making “math” in config files.
>> > 
>> > > @Alexandre: Make sure to add a NEWS entry warning users of the
>removal 
>> > > of matheval - ideally enumerating explicitly all uwsgi options
>which has 
>> > > disappeared and may silently wreak havoc on local systems.
>> > > 
>> > > Also, better check e.g. with codesearch.debian.net if any
>packages rely 
>> > > on matheval-related uwsgi config options, and if so alert them
>with 
>> > > bugreports.
>> > 
>> > Search on "uwsgi matheval" or "uwsgi math" yields no result.
>> 
>> Ah well, seems you got better knowledge here than me, Alex :-)
>
>Thanks for taking the time to answer.
>
>Do you require some assistance regarding a new upload of uwsgi? I'm
>eager to dedicate some time to it if you can't do so. :)

I have a patch but I have not been able to test it yet because the py2 removal 
makes the package FTBS... I'm close to fix it though. I'll post an update here 
by wednesday.

Alex

Bug#942224: asymptote: VIM addon cannot be managed with vim-addons and fails to enable syntax highlighting

[Norbert Preining]

Hi Francesco,

On Sun, 13 Oct 2019, Francesco Poli wrote:
> I am a newbie myself, I learned the basics by looking at other packages
> shipping VIM addons (such as package vim-scripts) and by reading the
> vim-addons(1) and vim-registry(5) man pages (shipped in package
> vim-addon-manager).

Aren't there different ways to activate packages in Vim? I have always
had problems with all the differen packages managers in vim.

> Have a nice evening (in the +0900 time zone...)!

Thanks, now that the Taifun has more or less passed...

Norbert

--
PREINING Norbert   http://www.preining.info
Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#942253: buster-pu: package picard/2.1.2-1+deb10u1

[Sebastian Ramacher]

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

picard currently crashes when launched with a Spanish locale after
opening the "About" dialog. This crash is caused by an error in the
Spanish translation. (see #941464)

I have uploaded picard 2.1.2-1+deb10u1 which addresses this issue by
applying upstream's fix which also includes updates to the Finnish
translation. The debdiff is attached.

Cheers
-- 
Sebastian Ramacher
diff --git a/debian/changelog b/debian/changelog
index 0118762..1160082 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+picard (2.1.2-1+deb10u1) buster; urgency=medium
+
+  * debian/gbp.conf: Work in buster branch
+  * debian/patches: Update translations to fix crash with Spanish locale 
(Closes: #941464)
+
+ -- Sebastian Ramacher   Sun, 13 Oct 2019 10:02:04 +0200
+
 picard (2.1.2-1) unstable; urgency=medium
 
   * New upstream release.
diff --git a/debian/gbp.conf b/debian/gbp.conf
new file mode 100644
index 000..97fc827
--- /dev/null
+++ b/debian/gbp.conf
@@ -0,0 +1,2 @@
+[DEFAULT]
+debian-branch = buster
diff --git a/debian/patches/0001-Pulled-updated-translations.patch 
b/debian/patches/0001-Pulled-updated-translations.patch
new file mode 100644
index 000..3405d26
--- /dev/null
+++ b/debian/patches/0001-Pulled-updated-translations.patch
@@ -0,0 +1,150 @@
+From: Philipp Wolfer 
+Date: Fri, 1 Feb 2019 08:44:05 +0100
+Subject: Pulled updated translations.
+
+Fixes PICARD-1461
+---
+ po/attributes/es.po |  9 +
+ po/es.po| 14 --
+ po/fi.po|  8 
+ 3 files changed, 17 insertions(+), 14 deletions(-)
+
+diff --git a/po/attributes/es.po b/po/attributes/es.po
+index b5b50ba..c3adebd 100644
+--- a/po/attributes/es.po
 b/po/attributes/es.po
+@@ -15,6 +15,7 @@
+ # Héctor Arroyo , 2012,2015
+ # Héctor Arroyo , 2012
+ # Ismael Olea , 2013-2015
++# Jaime Marquínez Ferrándiz, 2019
+ # Jeremias Brown , 2018
+ # Juan Acuña , 2016
+ # Kevin Doncam Demian López Brante , 2016
+@@ -34,8 +35,8 @@
+ msgid ""
+ msgstr ""
+ "Project-Id-Version: MusicBrainz\n"
+-"PO-Revision-Date: 2019-01-22 20:58+\n"
+-"Last-Translator: yvanz\n"
++"PO-Revision-Date: 2019-01-29 16:24+\n"
++"Last-Translator: Jaime Marquínez Ferrándiz\n"
+ "Language-Team: Spanish 
(http://www.transifex.com/musicbrainz/musicbrainz/language/es/)\n"
+ "MIME-Version: 1.0\n"
+ "Content-Type: text/plain; charset=UTF-8\n"
+@@ -2447,7 +2448,7 @@ msgctxt "gender"
+ msgid ""
+ "For cases where gender just doesn't apply at all (like companies entered as "
+ "artists)."
+-msgstr ""
++msgstr "Para casos en los que el género no es aplicable de ningún modo (por 
ejemplo compañías introducidas como artistas)."
+ 
+ #: DB:work_attribute_type/name:16
+ msgctxt "work_attribute_type"
+@@ -4686,7 +4687,7 @@ msgstr "Ninguno"
+ #: DB:gender/name:4
+ msgctxt "gender"
+ msgid "Not applicable"
+-msgstr ""
++msgstr "No aplicable"
+ 
+ #: DB:work_attribute_type_allowed_value/value:491
+ msgctxt "work_attribute_type_allowed_value"
+diff --git a/po/es.po b/po/es.po
+index 311cc54..32840ab 100644
+--- a/po/es.po
 b/po/es.po
+@@ -1,7 +1,7 @@
+ # Translations template for picard.
+ # Copyright (C) 2019 ORGANIZATION
+ # This file is distributed under the same license as the picard project.
+-# 
++#
+ # Translators:
+ # Andriu Haynes , 2017-2018
+ # Antonio Larrosa , 2017
+@@ -10,17 +10,19 @@
+ # Fermin Rodriguez , 2018
+ # Ismael Olea , 2011-2015
+ # Jaime Marquínez Ferrándiz, 2018
++# Jaime Marquínez Ferrándiz, 2019
+ # Jeremias Brown , 2018
+ # Nicolás Tamargo , 2012
+ # Peter Cuevas H , 2017
++# Philipp Wolfer , 2019
+ # Robert Schneider , 2019
+ msgid ""
+ msgstr ""
+ "Project-Id-Version: MusicBrainz\n"
+ "Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
+ "POT-Creation-Date: 2019-01-23 11:57+0100\n"
+-"PO-Revision-Date: 2019-01-23 13:16+\n"
+-"Last-Translator: Michael Wiencek \n"
++"PO-Revision-Date: 2019-02-01 07:25+\n"
++"Last-Translator: Philipp Wolfer \n"
+ "Language-Team: Spanish 
(http://www.transifex.com/musicbrainz/musicbrainz/language/es/)\n"
+ "MIME-Version: 1.0\n"
+ "Content-Type: text/plain; charset=UTF-8\n"
+@@ -409,11 +411,11 @@ msgstr "Ucraniano"
+ 
+ #: picard/const/languages.py:74
+ msgid "Chinese (China)"
+-msgstr ""
++msgstr "Chino (China)"
+ 
+ #: picard/const/languages.py:75
+ msgid "Chinese (Taiwan)"
+-msgstr ""
++msgstr "Chino (Taiwan)"
+ 
+ #: picard/coverart/__init__.py:105
+ #, python-format
+@@ -2134,7 +2136,7 @@ msgid ""
+ "Copyright © %(copyright-years)s %(authors-credits)s and 
others%(translator-credits)s\n"
+ "%(icons-credits)s\n"
+ "Official website%(picard-doc-url)s\n"
+-msgstr "MusicBrainz 
Picard\nVersión%(version)s\n\n%(third_parties_versions)s\n\nFormatos compatibles%(formats)s\nPor favor, haga una donación\nGracias 
por usar Picard. Picard se basa en la base de datos MusicBrainz, que es operada 
por la Fundación MetaBrainz con la ayuda de miles de voluntarios. Si le gusta 

Bug#934754: upload geary 3.32 to unstable

[Pirate Praveen]

On Sat, Oct 12, 2019 at 15:07, Jeremy Bicha  wrote:
On Wed, Aug 14, 2019 at 9:03 AM Pirate Praveen 
mailto:prav...@onenetbeyond.org>> wrote:
 mail client being a very important software for a desktop, I think 
geary

 should be available in buster backports. I was able to rebuild geary
 3.32 on buster without any changes in dependencies. Please upload 
geary

 3.32 to unstable so it can reach testing and backports.


Uploaded to unstable now.



Thanks.


I think at the moment we don't have people in the Debian GNOME team
maintaining backports. I guess you could give it a try if you commit
to maintaining the backported packages.



Yes, I already maintain many ruby and node packages in backports so I'm 
familiar with the process. I have to maintain a personal backport of 
geary anyway (I'm already using my personal backport on a daily basis), 
so it won't be any extra effort for me to maintain it officially. I 
have already requested access to gnome-team on salsa, please approve or 
at least add me to geary repo so I can maintain a branch there for 
backports.



Note that geary's build tests fail on s390x (so we will be removing
geary/s390x from Bullseye). Also note that geary 3.34 requires
libhandy which is not available in Buster. There is a libhandy git
subproject available, but we remove it for Bullseye to avoid an
"embedded code copy".



I have already backported libhandy and it is in backports-new.


Jeremy

Bug#942172: clamav-daemon: After upgrade, clamd cannon create /var/run/clamav/clamd.ctl and stop.

[Filipe Fonseca]

Hello,

I can test it but probably only in half a day time or so. I'll get back to 
you then. Many thanks.


Regards,
Filipe

On October 13, 2019 09:33:17 Hugo Lefeuvre  wrote:


Hi Filipe,


I did strike this in three boxes. Straight upgrade but opted not to touch
config when asked. Don't know if it matters. However I did not find any
reference to /etc/systemd/system/clamav-daemon.service.d/extend.conf in the
package scripts as in stretch.

The chown did make the difference. And the extend.conf prior to the upgrade
on further two boxes got the upgrade working, AFAICT.


thanks for your answer.

After further investigations, I have found a probable cause for this issue:
debian/patches/clamd_dont_depend_on_clamav_demon_socket.patch was
mistakenly backported from the stretch upload.

This should not have been backported, because the jessie package is still
providing the systemd socket, which was removed from the stretch package in
0.99.2+dfsg-3 because of #824042[0].

I did not backport this removal because I considered it too intrusive for a
security upload. Looking back, this was maybe a mistake because it
increased the complexity of the backport.

I have prepared a regression update addressing this issue. It would be a
true benefit for the quality of this upload if somebody could give it a try
before I go on with uploading. You can find (UNRELEASED) amd64 builds,
signed by myself on my Debian webpage:

https://people.debian.org/~hle/lts/clamav/

regards,
Hugo

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

--
   Hugo Lefeuvre (hle)|www.owl.eu.com
RSA4096_ 360B 03B3 BF27 4F4D 7A3F D5E8 14AA 1EB8 A247 3DFD
ed25519_ 37B2 6D38 0B25 B8A2 6B9F 3A65 A36F 5357 5F2D DC4C


--
filipe.fons...@farmingbits.com
+351.914593743

Bug#942055: cups-filters: ghostscript on armel partly broken?

[Alexander Reichle-Schmehl]

reassign 942055 ghostscript
severity 942055 important
found 942055 9.27~dfsg-2+deb10u1
thanks


Dear Maintainer,

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

   * What led up to the situation?
 I upgraded my server running on armel from stretch to buster. Since
 then I was unable to print pictures via my cups server installed on
 the armel system.
   * What exactly did you do (or not do) that was effective (or
   * What was the outcome of this action?
 ineffective)?
 Printing the cups test page results in just the test being printed,
 not the images. Same for other documents.
   * What outcome did you expect instead?
 Testpage should print with images :)

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

After the upgrade from stretch to buster, I noticed that I can't images
anymore. When printing pages with images, the part of the page is
usually left empty.  Same problem with text containing special
characters.

Installing cups on my amd64 notebook, I can print without problems
anymore, so it doesn't seem to be a general problem.

Downgrading the ghostscript pagages to the version in Debian 9 solved my
issues.


Please feel free to contact me for futher tests or debugg output.  I
grant that this issue might not be easy to reproduce ;)


Best regards,
  Alexander


-- System Information:
Debian Release: 10.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: armel (armv5tel)

Kernel: Linux 4.19.0-5-marvell
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: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages cups-filters depends on:
ii  bc 1.07.1-2+b1
ii  cups-filters-core-drivers  1.21.6-5
hi  ghostscript9.26a~dfsg-0+deb9u5
ii  libc6  2.28-10
ii  libcups2   2.2.10-6+deb10u1
ii  libcupsfilters11.21.6-5
ii  libcupsimage2  2.2.10-6+deb10u1
ii  libfontconfig1 2.13.1-2
ii  libfontembed1  1.21.6-5
ii  libgcc11:8.3.0-6
ii  libqpdf21  8.4.0-2
ii  libstdc++6 8.3.0-6
ii  poppler-utils  0.71.0-5

Versions of packages cups-filters recommends:
ii  colord 1.4.3-4
ii  liblouisutdml-bin  2.7.0-5+b1

Versions of packages cups-filters suggests:
pn  antiword   
pn  docx2txt   
ii  foomatic-db-compressed-ppds [foomatic-db]  20181217-2
ii  imagemagick8:6.9.10.23+dfsg-2.1
ii  imagemagick-6.q16 [imagemagick]8:6.9.10.23+dfsg-2.1

-- no debconf information

Bug#942262: transition: x265

[Sebastian Ramacher]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Control: forwarded -1 https://release.debian.org/transitions/html/auto-x265.html

x265 bumped its SONAME to 179 and the new upstream release is staged in
experimental. All reverse dependencies build fine against the new
version.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#942263: RM: rlplot -- RoQA; Dead upstream, depends on Qt4

[Moritz Muehlenhoff]

Package: ftp.debian.org
Severity: normal

Please remove rlplot, it depends on Qt4 and is dead upstream.

Cheers,
Moritz

Bug#875172: [rlplot] Future Qt4 removal from Buster

[Moritz Mühlenhoff]

On Sun, Sep 29, 2019 at 10:41:07PM +0200, Moritz Mühlenhoff wrote:
> On Sat, Sep 09, 2017 at 11:09:19PM +0200, Lisandro Damián Nicanor Pérez Meyer 
> wrote:
> > Source: rlplot
> > Version: 1.5-3
> > Severity: wishlist
> > User: debian-qt-...@lists.debian.org
> > Usertags: qt4-removal
> > 
> > 
> > Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
> > as [announced] in:
> > 
> > [announced] 
> > 
> > 
> > Currently Qt4 has been dead upstream and we are starting to have problems
> > maintaining it, like for example in the [OpenSSL 1.1 support] case.
> > 
> > [OpenSSL 1.1 support] 
> > 
> > 
> > In order to make this move, all packages directly or indirectly depending on
> > the Qt4 libraries have to either get ported to Qt5 or eventually get
> > removed from the Debian repositories.
> > 
> > Therefore, please take the time and:
> > - contact your upstream (if existing) and ask about the state of a Qt5
> > port of your application
> > - if there are no activities regarding porting, investigate whether there 
> > are
> > suitable alternatives for your users
> > - if there is a Qt5 port that is not yet packaged, consider packaging it
> > - if both the Qt4 and the Qt5 versions already coexist in the Debian
> > archives, consider removing the Qt4 version
> 
> rlplot is dead upstream, does anyone intend to port it themselves? Otherwise
> let's remove it, we're moving forward with the Qt4 removal.

I've filed a removal bug now.

Cheers,
Moritz

Bug#942267: please remove me from uploaders

[Mo Zhou]

Package: nvidia-cuda-toolkit
Version: 10.1.105-3+b1

Dear co-maintainers,

Please remove me from the uploader list. I'm tired of
taking care of suckware from NVIDIA. I'm still interested
in maintaining some open-source packages related to nvidia,
but I shall never do anything for upstream:nvidia.

Bug#938962: Bug#941720: linux-headers-4.19.0-0.bpo.6-amd64 depends on linux-headers-4.19.0-0.bpo.6-common=4.19.67-2+deb10u1~bpo9+1 but only linux-headers-4.19.0-0.bpo.6-amd64=4.19.67-2~bpo9+1 is avail

[Ritesh Raj Sarraf]

Hi.

On Sun, 2019-10-06 at 18:18 +0100, Ben Hutchings wrote:
> On Sun, 2019-10-06 at 15:35 +, Scott Kitterman wrote:
> > The reason it's still there is in the cruft report:
> 
> Sorry, I didn't realise that was something I could look up.
> 
> >   - broken Build-Depends:
> > user-mode-linux: linux-source-4.19
> > 
> > Is user-mode-linux maintained?  This seems to come up somewhat
> > regularly.

It is maintained. It is just that the latest upload is blocked by DBug:
#938962


-- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System


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

Bug#942200: rollup 1.0 transition: node-d3 built with rollup 1.0 gives error in test

[Pirate Praveen]

Control: reassign -1 rollup
Control: found -1 1.0.2-1
Control: retitle -1 rollup 1.0.2 creates broken bundle for node-d3

On Sun, Oct 13, 2019 at 16:48, Pirate Praveen 
 wrote:

On Sat, 12 Oct 2019 13:04:10 +0530 Pirate Praveen
mailto:prav...@onenetbeyond.org>> wrote:

 package: node-d3
 version: 4.13.0-10


With node-d3 5.12, build succeeds and one test fails,

# version matches package.json
ok 1 should be equal
# d3.event is a getter for d3Selection.event
ok 2 should be equal
not ok 3 should be equal
  ---
operator: equal
expected: 42
actual:   null
at: Test. (/<>/test/d3-test.js:15:10)
stack: |-
  Error: should be equal
  at Test.assert [as _assert]
(/usr/lib/nodejs/tape/lib/test.js:235:54)
  at Test.bound [as _assert]
(/usr/lib/nodejs/tape/lib/test.js:87:32)
  at Test.equal (/usr/lib/nodejs/tape/lib/test.js:395:10)
  at Test.bound [as equal] 
(/usr/lib/nodejs/tape/lib/test.js:87:32)

  at Test. (/<>/test/d3-test.js:15:10)
  at Test.bound [as _cb] 
(/usr/lib/nodejs/tape/lib/test.js:87:32)

  at Test.run (/usr/lib/nodejs/tape/lib/test.js:106:10)
  at Test.bound [as run] 
(/usr/lib/nodejs/tape/lib/test.js:87:32)

  at Immediate.next [as _onImmediate]
(/usr/lib/nodejs/tape/lib/results.js:71:15)
  at runCallback (timers.js:705:18)
  ...


This seems like a bug in rollup 1.0.2. Using with rollup 1.0.2 in 
package.json, npm i; npm run test also fails. Works fine with rollup 
1.8.

Bug#942268: spamassassin: FROM_EXCESS_BASE64 always gives false positive

[Evgeniy Berdnikov]

Package: spamassassin
Version: 3.4.2-1
Severity: normal

Dear Maintainer,

file /usr/share/spamassassin/20_head_tests.cf contains:

--
header __FROM_NEEDS_MIMEFrom:name:raw =~ 
/[\x00-\x08\x0b\x0c\x0e-\x1f\x7f-\xff]/
header __FROM_ENCODED_QPFrom:raw =~ /=\?\S+\?Q\?/i
header __FROM_ENCODED_B64   From:raw =~ /=\?\S+\?B\?/i


meta FROM_EXCESS_BASE64 __FROM_ENCODED_B64 && !__FROM_NEEDS_MIME
describe FROM_EXCESS_BASE64 From: base64 encoded unnecessarily
--

It results in false positive for every properly encoded From header.
All the incoming mails in my box are marked with FROM_EXCESS_BASE64.
Please, fix it.


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

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

Versions of packages spamassassin depends on:
ii  adduser 3.118
ii  init-system-helpers 1.57
ii  libhtml-parser-perl 3.72-3+b3
ii  libhttp-date-perl   6.02-1
ii  libmail-dkim-perl   0.56-1
ii  libnet-dns-perl 1.20-1
ii  libnetaddr-ip-perl  4.079+dfsg-1+b3
ii  libsocket6-perl 0.29-1+b1
ii  libsys-hostname-long-perl   1.5-1
ii  libwww-perl 6.39-1
ii  lsb-base11.1.0
ii  perl [libarchive-tar-perl]  5.28.1-6

Versions of packages spamassassin recommends:
ii  gnupg  2.2.17-3
ii  libio-socket-inet6-perl2.72-2
ii  libmail-spf-perl   2.9.0-4
ii  perl [libsys-syslog-perl]  5.28.1-6
pn  sa-compile 
ii  spamc  3.4.2-1

Versions of packages spamassassin suggests:
pn  libdbi-perl   
pn  libencode-detect-perl 
pn  libgeo-ip-perl
ii  libio-socket-ssl-perl 2.066-1
pn  libnet-patricia-perl  
ii  perl [libcompress-zlib-perl]  5.28.1-6
pn  pyzor 
pn  razor 

-- Configuration Files:
/etc/default/spamassassin changed [not included]

-- no debconf information

Bug#935042: Program phones home by default

[Birger Schacht]

Hi,

On 8/18/19 3:21 PM, Robie Basak wrote:
> Package: lynis
> Version: 2.6.2-1
> Severity: serious

https://www.debian.org/Bugs/Developer#severities says:
> serious is a severe violation of Debian policy (roughly, it violates a
> "must" or "required" directive)"

Robie, could you please point out the part of the Debian policy that
this package is violating?

thanks,
Birger

Bug#942262: transition: x265

[Sebastian Ramacher]

On 2019-10-13 14:28:32, Emilio Pozuelo Monfort wrote:
> On 13/10/2019 13:47, Sebastian Ramacher wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packages.debian.org
> > Usertags: transition
> > Control: forwarded -1 
> > https://release.debian.org/transitions/html/auto-x265.html
> > 
> > x265 bumped its SONAME to 179 and the new upstream release is staged in
> > experimental. All reverse dependencies build fine against the new
> > version.
> 
> If the package builds fine in the remaining release architectures (I have just
> bumped the build prio) you can go ahead.

It built everywhere, so I've uploaded it to unstable.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#942277: vim: Please consider replacing dh_install --list-missing with dh_missing --list-missing

[Boyuan Yang]

Source: vim
Version: 2:8.1.2136-1
Severity: minor

Dear vim maintainer,

For debian/rules file, the "--list-missing" option in dh_install(1) has been
deprecated in debhelper compat v11 and will be removed in debhelper compat
v12. Please consider using "dh_missing --list-missing" instead.

Best,
Boyuan Yang


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

Bug#941078: transition: postgresql-12

[Paul Gevers]

Hi Christoph,

On 13-10-2019 12:04, Christoph Berg wrote:
> Re: Emilio Pozuelo Monfort 2019-10-12 
> <09c44ee4-1bee-bc9a-43fd-64fbbdf5c...@debian.org>
>> Go ahead.
> 
> Thanks. We'll start as soon as postgresql-12 is in testing to minimize
> any possible entanglement with other transitions.

The migration is currently blocked on the regression of repmgr. I just
triggered a reference run as I think the postgresql-11 migration in the
perl transition will have caused the current state in testing to be bad
already. If that's not the case, and it's really postgresql-12 related,
how do you propose we treat the situation?

Paul
PS: I am aware of the discussion on IRC, but the outcome for
postgresql-12 isn't clear to me and I like it to be logged in this bug.



signature.asc
Description: OpenPGP digital signature

Bug#941078: transition: postgresql-12

[Christoph Berg]

Re: Paul Gevers 2019-10-13 
> The migration is currently blocked on the regression of repmgr. I just
> triggered a reference run as I think the postgresql-11 migration in the
> perl transition will have caused the current state in testing to be bad
> already. If that's not the case, and it's really postgresql-12 related,
> how do you propose we treat the situation?

Fwiw, I believe the situation is as follows: libpq5 didn't break ABI,
so the existing postgresql-11-repmgr packages are fine, both in
testing and in unstable.

What did change however is that some API juggling happened, which
means repmgr needs to be updated to cope with mixed PostgreSQL
versions in postgresql-server-dev-11 and libpq-dev 12.

Unfortunately repmgr's autopkgtest is marked "build-needed" so we get
to see the API problem, while there's no actual problem with the
binaries. I've pushed a change to git to fix that.

Christoph

Bug#935042: Privacy Breach is not in policy

[Marcos Fouces]

Hello

Similar issues were discussed in: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726998

You could also find that Lintian folks uses several levels of error
tags to describe this problem, for instance:

* 
https://lintian.debian.org/tags/privacy-breach-statistics-website.html.
It is considered as "serious"

* https://lintian.debian.org/tags/privacy-breach-generic.html. It is
considered as "important"

Both tags are related to the present issue.

AFAIK, there is nothing in Debian Policy about this but it is plain
common sense to avoid this kind of privacy breaches.

Greetings, 

Marcos

Bug#556893: #556893,say which 'defaults' are which better

[Michael Biebl]

Control: tags -1 - patch

Am 13.10.19 um 21:41 schrieb Jesse Smith:
> On 10/13/19 4:33 PM, Michael Biebl wrote:
>> Control: tags -1 + moreinfo

>> Will insserv fail if the version is too old, i.e. do we need a versioned
>> dependency (or rather versioned Breaks)?
> 
> Yes, older versions of insserv will fail if --silent is specified as it
> will not be a recognized option. There should probably be a version
> check. Or a check in the calling script to try with insserv --silent and
> if it fails, try again without the flag.

Ok, thanks.

Removing the patch tag then.

>> What exactly is suppressed by -q/--silent?
>> Only this specific error about "defaults" or other error messages as
>> well? Do we want to suppress all error messages?
> 
> The --silent flag suppresses warnings (non-fatal errors). Basically
> anything that is a "heads up" warning is suppressed. Fatal errors and
> issues which require user attention are still printed.

Ok, good.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#900253: nslcd: disabling ppolicy breaks authentication

[Arthur de Jong]

On Sun, 2019-09-22 at 01:01 +0900, Marc Dequènes wrote:
> As I can see this part of the code did not change in 0.9.10.

Hi Marc,

Sorry for not responding sooner.

There are two nslcd implementations: nslcd and pynslcd. The pynslcd
implementation is more experimental and does not handle
pam_authc_ppolicy properly.

The nslcd implementation for which you filed the bug should handle the
option properly, e.g. see 
https://arthurdejong.org/git/nss-pam-ldapd/tree/nslcd/myldap.c#n587

This option has been in nss-pam-ldapd since 0.9.7 so if you are seeing
this with nslcd, could you report the exact error your LDAP server is
logging?

The pynslcd implementation does not yet support this in a released
version but I just pushed a fix to Git:
https://arthurdejong.org/git/nss-pam-ldapd/commit/?id=fea0f5e

Thanks,

-- 
-- arthur - art...@arthurdejong.org - https://arthurdejong.org/ --



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

Bug#934134: seabios: Unable to install FreeDOS

[Harald Welte]

I can confirm this problem.  It also happens here, when trying to install
FreeDOS 1.2 from CDROM on debian unstable (seabios 1.12.0-1)
-- 
- Harald Welte http://laforge.gnumonks.org/

"Privacy in residential applications is a desirable marketing option."
  (ETSI EN 300 175-7 Ch. A6)

Bug#942265: systemd: Missing subdir. sockets.target.wants

[Michael Biebl]

Control: tags -1 + moreinfo unreproducible

Am 13.10.19 um 15:12 schrieb Corcodel Marian:
> Package: systemd
> Version: 232-25+deb9u12
> Severity: normal
> 
> Hi, when try to enable global pulseaudio.socket missing subdir
> etc/systemd/user/socket.target.wants and need create manual.
> $systemctl --global enable pulseaudio.socket fail.
> 

Please provide the exact error message you are getting from systemctl
and the exact command line you used.
Output of
ls -la /etc/systemd/user/
before and after you run the systemctl command.

Fwiw, I can't reproduce the failure on stretch.



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#942219: systemd-backlight@backlight:dell_backlight.service fails at boot for dell d600, d620, d820

[Michael Biebl]

Control: tags -1 + moreinfo

Am 12.10.19 um 15:56 schrieb Rado Q:
> Package: systemd
> Version: 241-7~deb10u1
> 
> Dear Maintainer,
>* What led up to the situation?
> Installation of debian10.
> 
>* What exactly did you do (or not do) that was effective (or ineffective)?
> Boot.
> 
>* What was the outcome of this action?
> Failed systemd-backlight@backlight:dell_backlight.service .
> 
>* What outcome did you expect instead?
> Startup without failure.
> 
> 
> This happens with dell d600, d620, d820.
> It works OK for dell vostro 1520.
> 
> How to get more info?

Please attach the output of (run as root)
systemctl status systemd-backlight@backlight:dell_backlight.service
journalctl -alb

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#942280: linux-image-4.19.0-6-amd64: Mouse wheel does not work

[Rafał Rutkowski]

Package: src:linux
Version: 4.19.67-2+deb10u1
Severity: important

Dear Maintainer,
The mouse wheel does not work, if the machine is booted with this kernel.
By not working, I mean the windows do not scroll (I use GNOME on X11); no
mouse
wheel events are registered in xev.

The above problem does not exist, if the machine is booted with 4.19.0-5.

Below is the mouse info from lsusb:

Bus 003 Device 005: ID 09da:000a A4Tech Co., Ltd. Optical Mouse Opto 510D /
OP-620D
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   1.10
  bDeviceClass0
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize0 8
  idVendor   0x09da A4Tech Co., Ltd.
  idProduct  0x000a Optical Mouse Opto 510D / OP-620D
  bcdDevice0.17
  iManufacturer   1 A4Tech
  iProduct2 USB Mouse
  iSerial 0
  bNumConfigurations  1



-- Package-specific info:
** Version:
Linux version 4.19.0-6-amd64 (debian-ker...@lists.debian.org) (gcc version
8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.67-2+deb10u1 (2019-09-20)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.19.0-6-amd64
root=UUID=0a662727-41e2-4786-8765-c0b222edc576 ro quiet iommu=pt
ignore_msrs=1

** Tainted: W (512)
 * Taint on warning.

** Kernel log:
[4.586935] CR2: 56192c487268 CR3: 00042b772000 CR4:
003406e0
[4.586936] Call Trace:
[4.586993]  dce110_apply_ctx_to_hw+0x62d/0x690 [amdgpu]
[4.587051]  ? hubbub1_verify_allow_pstate_change_high+0xdd/0x180
[amdgpu]
[4.587106]  dc_commit_state+0x2c6/0x550 [amdgpu]
[4.587161]  ? set_freesync_on_streams.part.6+0x4d/0x230 [amdgpu]
[4.587215]  ? mod_freesync_set_user_enable+0x11f/0x150 [amdgpu]
[4.587273]  amdgpu_dm_atomic_commit_tail+0x384/0xe00 [amdgpu]
[4.587323]  ? amdgpu_bo_pin_restricted+0x60/0x280 [amdgpu]
[4.587380]  ? amdgpu_dm_atomic_commit_tail+0xe00/0xe00 [amdgpu]
[4.587436]  ? dm_plane_helper_prepare_fb+0x1ee/0x300 [amdgpu]
[4.587443]  commit_tail+0x3d/0x70 [drm_kms_helper]
[4.587449]  drm_atomic_helper_commit+0xb4/0x120 [drm_kms_helper]
[4.587454]  restore_fbdev_mode_atomic+0x170/0x1d0 [drm_kms_helper]
[4.587460]  drm_fb_helper_restore_fbdev_mode_unlocked+0x45/0x90
[drm_kms_helper]
[4.587466]  drm_fb_helper_set_par+0x29/0x50 [drm_kms_helper]
[4.587467]  fbcon_init+0x488/0x600
[4.587469]  visual_init+0xd5/0x130
[4.587470]  do_bind_con_driver+0x1db/0x2d0
[4.587471]  do_take_over_console+0x113/0x190
[4.587473]  do_fbcon_takeover+0x58/0xb0
[4.587474]  notifier_call_chain+0x47/0x70
[4.587475]  blocking_notifier_call_chain+0x3e/0x60
[4.587476]  register_framebuffer+0x257/0x340
[4.587482]  __drm_fb_helper_initial_config_and_unlock+0x216/0x440
[drm_kms_helper]
[4.587533]  amdgpu_fbdev_init+0xc4/0xf0 [amdgpu]
[4.587588]  amdgpu_device_init.cold.28+0x1142/0x129e [amdgpu]
[4.587637]  amdgpu_driver_load_kms+0x86/0x2d0 [amdgpu]
[4.587648]  drm_dev_register+0x109/0x140 [drm]
[4.587697]  amdgpu_pci_probe+0x1aa/0x230 [amdgpu]
[4.587699]  local_pci_probe+0x41/0x90
[4.587700]  pci_device_probe+0xf5/0x1b0
[4.587702]  really_probe+0x23e/0x390
[4.587703]  driver_probe_device+0xb3/0xf0
[4.587704]  __driver_attach+0xea/0x110
[4.587705]  ? driver_probe_device+0xf0/0xf0
[4.587706]  bus_for_each_dev+0x77/0xc0
[4.587708]  ? klist_add_tail+0x3b/0x70
[4.587709]  bus_add_driver+0x152/0x230
[4.587710]  ? 0xc0f42000
[4.587711]  driver_register+0x6b/0xb0
[4.587712]  ? 0xc0f42000
[4.587713]  do_one_initcall+0x46/0x1c3
[4.587714]  ? _cond_resched+0x15/0x30
[4.587715]  ? kmem_cache_alloc_trace+0x155/0x1d0
[4.587717]  do_init_module+0x5a/0x210
[4.587718]  load_module+0x2118/0x2390
[4.587720]  ? __do_sys_finit_module+0xad/0x110
[4.587721]  __do_sys_finit_module+0xad/0x110
[4.587723]  do_syscall_64+0x53/0x110
[4.587724]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[4.587725] RIP: 0033:0x7f351b7b1f59
[4.587726] Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48
89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05
<48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 07 6f 0c 00 f7 d8 64 89 01 48
[4.587726] RSP: 002b:7fffc0ba4468 EFLAGS: 0246 ORIG_RAX:
0139
[4.587727] RAX: ffda RBX: 5635e0c7c080 RCX:
7f351b7b1f59
[4.587728] RDX:  RSI: 7f351b6b6cad RDI:
0014
[4.587728] RBP: 7f351b6b6cad R08:  R09:

[4.587729] R10: 0014 R11: 0246 R12:

[4.587729] R13: 5635e0c64be0 R14: 0002 R15:
5635e0c7c080
[4.587730] ---[ end trace 365537b8fab10f42 ]---
[4.595392] Console: switching to colour frame buffer device 240x75
[4.597130] EDAC amd64: Node 0: DRAM ECC disabled.
[4.597132] EDAC amd64: ECC 

Bug#942272: gnome-shell: numlock state is reversed

[EdiD]

Package: gnome-shell
Version: 3.34.0-2
Severity: normal

Numlock state is reversed after system boot

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

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

Versions of packages gnome-shell depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.34.0-1
ii  evolution-data-server3.34.1-1
ii  gir1.2-accountsservice-1.0   0.6.45-2
ii  gir1.2-atspi-2.0 2.34.0-3
ii  gir1.2-freedesktop   1.62.0-2
ii  gir1.2-gcr-3 3.33.4-2
ii  gir1.2-gdesktopenums-3.0 3.34.0-2
ii  gir1.2-gdm-1.0   3.34.1-1
ii  gir1.2-geoclue-2.0   2.5.5-1
ii  gir1.2-glib-2.0  1.62.0-2
ii  gir1.2-gnomebluetooth-1.03.34.0-1
ii  gir1.2-gnomedesktop-3.0  3.34.0-2
ii  gir1.2-gtk-3.0   3.24.12-1
ii  gir1.2-gweather-3.0  3.28.3-2
ii  gir1.2-ibus-1.0  1.5.19-4+b1
ii  gir1.2-mutter-5  3.34.0-4
ii  gir1.2-nm-1.01.20.4-2
ii  gir1.2-nma-1.0   1.8.22-2
ii  gir1.2-pango-1.0 1.42.4-7
ii  gir1.2-polkit-1.00.105-26
ii  gir1.2-rsvg-2.0  2.44.14-1
ii  gir1.2-soup-2.4  2.68.1-2
ii  gir1.2-upowerglib-1.00.99.11-1
ii  gjs  1.58.1-1
ii  gnome-backgrounds3.34.0-1
ii  gnome-settings-daemon3.34.0-3
ii  gnome-shell-common   3.34.0-2
ii  gsettings-desktop-schemas3.34.0-2
ii  libatk-bridge2.0-0   2.34.1-1
ii  libatk1.0-0  2.34.1-1
ii  libc62.29-2
ii  libcairo21.16.0-4
ii  libcroco30.6.13-1
ii  libecal-2.0-13.34.1-1
ii  libedataserver-1.2-243.34.1-1
ii  libgcr-base-3-1  3.33.4-2
ii  libgdk-pixbuf2.0-0   2.40.0+dfsg-1
ii  libgirepository-1.0-11.62.0-2
ii  libgjs0g 1.58.1-1
ii  libgles2 1.1.0-1+b1
ii  libglib2.0-0 2.62.1-1
ii  libglib2.0-bin   2.62.1-1
ii  libgnome-autoar-0-0  0.2.3-2
ii  libgstreamer1.0-01.16.1-1
ii  libgtk-3-0   3.24.12-1
ii  libical3 3.0.5-2
ii  libjson-glib-1.0-0   1.4.4-2
ii  libmutter-5-03.34.0-4
ii  libnm0   1.20.4-2
ii  libpango-1.0-0   1.42.4-7
ii  libpangocairo-1.0-0  1.42.4-7
ii  libpolkit-agent-1-0  0.105-26
ii  libpolkit-gobject-1-00.105-26
ii  libpulse-mainloop-glib0  13.0-2
ii  libpulse013.0-2
ii  libsecret-1-00.19.1-1
ii  libsystemd0  242-7
ii  libwayland-server0   1.17.0-1
ii  libx11-6 2:1.6.8-1
ii  libxfixes3   1:5.0.3-1
ii  mutter   3.34.0-4
ii  python3  3.7.5-1

Versions of packages gnome-shell recommends:
ii  bolt  0.8-4
ii  chrome-gnome-shell10.1-5
ii  gdm3  3.34.1-1
ii  gkbd-capplet  3.26.1-1
ii  gnome-control-center  1:3.34.1-1
ii  gnome-user-docs   3.34.0-2
ii  ibus  1.5.19-4+b1
ii  iio-sensor-proxy  2.4-2+b1
ii  switcheroo-control1.3.1-2
ii  unzip 6.0-25

Versions of packages gnome-shell suggests:
pn  gir1.2-telepathyglib-0.12   
pn  gir1.2-telepathylogger-0.2  

Versions of packages gnome-session depends on:
ii  gnome-session-bin  3.34.1-1
ii  gnome-session-common   3.34.1-1
ii  gnome-settings-daemon  3.34.0-3

Versions of packages gnome-session suggests:
ii  desktop-base   10.0.3
ii  gnome-keyring  3.34.0-1

Bug#942273: drkonqi: I keep getting "drkonqi Closed Unexpectedly" messages every 30 seconds or so

[Gary Dale]

Package: drkonqi
Version: 5.14.5-1
Severity: important

Dear Maintainer,

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

   * What led up to the situation?
this has been happening for last few days. I full-updgrade every day so that 
probably 
triggered it.

   * What exactly did you do (or not do) that was effective (or ineffective)?
I don't know what drkonqi does but it doesn't seem to impact my system other 
than 
continually throwing up annoying messages

   * What was the outcome of this action?
   * What outcome did you expect instead?

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


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

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

Versions of packages drkonqi depends on:
ii  kio   5.62.1-1
ii  libc6 2.29-2
ii  libkf5completion5 5.62.0-1
ii  libkf5configcore5 5.62.0-1
ii  libkf5configgui5  5.62.0-1
ii  libkf5configwidgets5  5.62.0-1
ii  libkf5coreaddons5 5.62.0-1
ii  libkf5crash5  5.62.0-1
ii  libkf5i18n5   5.62.0-1
ii  libkf5idletime5   5.62.0-1
ii  libkf5jobwidgets5 5.62.0-1
ii  libkf5kiocore55.62.1-1
ii  libkf5notifications5  5.62.0-1
ii  libkf5service-bin 5.62.0-1
ii  libkf5service55.62.0-1
ii  libkf5wallet-bin  5.62.0-1
ii  libkf5wallet5 5.62.0-1
ii  libkf5widgetsaddons5  5.62.0-1
ii  libkf5xmlrpcclient5   5.62.0-1
ii  libqt5core5a  5.11.3+dfsg1-4
ii  libqt5dbus5   5.11.3+dfsg1-4
ii  libqt5gui55.11.3+dfsg1-4
ii  libqt5widgets55.11.3+dfsg1-4
ii  libqt5x11extras5  5.11.3-2
ii  libqt5xml55.11.3+dfsg1-4
ii  libstdc++69.2.1-8

drkonqi recommends no packages.

drkonqi suggests no packages.

-- no debconf information

Bug#942200: [Pkg-javascript-devel] Bug#942200: Bug#942200: rollup 1.0 transition: node-d3 built with rollup 1.0 gives error in test

[Xavier]

Thanks a lot for your work !

Le 13 octobre 2019 17:02:20 GMT+02:00, Pirate Praveen 
 a écrit :
>
>
>On Sun, Oct 13, 2019 at 20:15, Pirate Praveen 
> wrote:
>> This seems like a bug in rollup 1.0.2. Using with rollup 1.0.2 in 
>> package.json, npm i; npm run test also fails. Works fine with rollup 
>> 1.8.
>
>Now trying to update to 1.10.1 (which also works).
>
>Found debian/nodejs/./build
>   cd ./. && sh -e debian/nodejs/./build
>src/Module.ts:5:34 - error TS2307: Cannot find module 
>'rollup-pluginutils/src/extractAssignedNames'.
>
>5 import extractAssignedNames from 
>'rollup-pluginutils/src/extractAssignedNames';
>   
>~
>
>src/watch/index.ts:4:26 - error TS2307: Cannot find module 
>'rollup-pluginutils/src/createFilter'.
>
>4 import createFilter from 'rollup-pluginutils/src/createFilter';
>   ~
>
>
>Found 4 errors.
>
>We'll need to update node-rollup-pluginutils to 2.6 and drop src_babel 
>generation as tsc can consume ES module directly. I'm going to try this
>
>tomorrow.

-- 
Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma 
brièveté.

Bug#941338: spek: Should spek be removed from Debian?

[Olly Betts]

Control: reassign -1 ftp.debian.org
Control: retitle -1 RM: spek -- RoQA; dead upstream; unmaintained; low popcon; 
RC-buggy

On Sun, Sep 29, 2019 at 05:28:49PM +1300, Olly Betts wrote:
> I think it's time to remove the spek package:
> 
> * last upstream release was 6.5 years ago 
> * last package update was 3.5 years ago
> * has low popcon - inst:331 vote:57
> * has no reverse dependencies (according to dak rm)
> * 2 open bugs, neither with any maintainer response
> * I had to NMU for the last wxWidgets transition 5 years ago, and
>   it's now a blocker for the current wxwidgets3.0-gtk3 transition.
> 
> If there are no objections within two weeks, I'll turn this into an RM
> bug.

I've had no response, so doing so now.

Cheers,
Olly

Bug#940476: tmpreaper 1.6.14+deb10u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 940476 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: tmpreaper
Version: 1.6.14+deb10u1

Explanation: add `--protect '/tmp/systemd-private*/*'` to cron job to prevent 
breaking systemd services that have PrivateTmp=true

Bug#939313: swi-prolog 8.0.2+dfsg-3+deb10u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 939313 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: swi-prolog
Version: 8.0.2+dfsg-3+deb10u1

Explanation: use HTTPS when contacting upstream pack servers

Bug#939526: inn2 2.6.3-1+deb10u2 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 939526 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: inn2
Version: 2.6.3-1+deb10u2

Explanation: fix negotiation of DHE ciphersuites

Bug#941227: node-set-value 0.4.0-1+deb10u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 941227 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: node-set-value
Version: 0.4.0-1+deb10u1

Explanation: fix prototype pollution [CVE-2019-10747]

Bug#942075: cyrus-imapd 3.0.8-6+deb10u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 942075 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: cyrus-imapd
Version: 3.0.8-6+deb10u1

Explanation: fix data loss on upgrade from version 3.0.0 or earlier

Bug#941168: postfix 3.4.7-0+deb10u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 941168 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: postfix
Version: 3.4.7-0+deb10u1

Explanation: new upstream stable release; work around poor TCP loopback 
performance

Bug#885265: Bug#936299: chirp: Python2 removal in sid/bullseye

[Chris Knadle]

There has been some discussion about #936299 on the upstream mailing list, and
there have been a few upstream commits starting to port the code to Python3.

http://intrepid.danplanet.com/pipermail/chirp_devel/2019-August/005580.html

  -- Chris, KB2IQN

-- 
Chris Knadle
chris.kna...@coredump.us

Bug#556893: #556893,say which 'defaults' are which better

[Michael Biebl]

Control: tags -1 + moreinfo

On Sat, 28 Sep 2019 15:21:17 -0300 Jesse Smith
 wrote:
> This has been addressed upstream in insserv by allowing the program to
> accept changes like this silently. All we need now is for update-rc.d to
> be updated to use the new behaviour (enabled with the -q flag) and this
> issue can be closed.

Is it -q or --silent? Or are they the same?

Will insserv fail if the version is too old, i.e. do we need a versioned
dependency (or rather versioned Breaks)?

What exactly is suppressed by -q/--silent?
Only this specific error about "defaults" or other error messages as
well? Do we want to suppress all error messages?

Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#942266: Try to exclude root

[Corcodel Marian]

On atach is 1 patch wich prevent to run pulseaudio on root user.


---
Last-Update: 2019-10-13

--- pulseaudio-10.0.orig/src/daemon/main.c
+++ pulseaudio-10.0/src/daemon/main.c
@@ -646,6 +646,12 @@ int main(int argc, char *argv[]) {
 goto finish;
 }
 
+#if defined (HAVE_GETUID) && defined (HAVE_SYSTEMD_DAEMON)
+if (getuid() == 0 && !conf->system_instance) {
+	pa_log(_("THIS program is not intended to be as root (unless --system is specified), exitting."));
+	goto finish;
+}
+#endif
 #ifdef HAVE_GETUID
 if (getuid() == 0 && !conf->system_instance)
 pa_log_warn(_("This program is not intended to be run as root (unless --system is specified)."));

Bug#942279: golang-github-hashicorp-go-retryablehttp breaks golang-github-circonus-labs-circonus-gometrics autopkgtest

[Paul Gevers]

Source: golang-github-hashicorp-go-retryablehttp, 
golang-github-circonus-labs-circonus-gometrics
Control: found -1 golang-github-hashicorp-go-retryablehttp/0.6.2-1
Control: found -1 golang-github-circonus-labs-circonus-gometrics/2.0.0-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainers,

With a recent upload of golang-github-hashicorp-go-retryablehttp the
autopkgtest of golang-github-circonus-labs-circonus-gometrics fails in
testing when that autopkgtest is run with the binary packages of
golang-github-hashicorp-go-retryablehttp from unstable. It passes when
run with only packages from testing. In tabular form:
pass fail
golang-github-hashicorp-go-retryablehttpfrom testing 0.6.2-1
golang-github-circonus-labs-circonus-gometrics  from testing 2.0.0-1
all others  from testing from testing

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

Currently this regression is blocking the migration of
golang-github-hashicorp-go-retryablehttp to testing [1]. Due to the
nature of this issue, I filed this bug report against both packages. Can
you please investigate the situation and reassign the bug to the right
package?

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

Paul

[1]
https://qa.debian.org/excuses.php?package=golang-github-hashicorp-go-retryablehttp

https://ci.debian.net/data/autopkgtest/testing/amd64/g/golang-github-circonus-labs-circonus-gometrics/3160364/log.gz

# github.com/circonus-labs/circonus-gometrics
src/github.com/circonus-labs/circonus-gometrics/submit.go:133:24: cannot
use func literal (type func(*log.Logger, *http.Request, int)) as type
retryablehttp.RequestLogHook in assignment
dh_auto_build: cd obj-x86_64-linux-gnu && go install
-gcflags=all=\"-trimpath=/tmp/autopkgtest-lxc.ikh1z671/downtmp/autopkgtest_tmp/obj-x86_64-linux-gnu/src\"
-asmflags=all=\"-trimpath=/tmp/autopkgtest-lxc.ikh1z671/downtmp/autopkgtest_tmp/obj-x86_64-linux-gnu/src\"
-v -p 2 github.com/circonus-labs/circonus-gometrics
github.com/circonus-labs/circonus-gometrics/api
github.com/circonus-labs/circonus-gometrics/api/config
github.com/circonus-labs/circonus-gometrics/checkmgr returned exit code 2
make: *** [debian/rules:4: build] Error 255



signature.asc
Description: OpenPGP digital signature

Bug#556893: #556893,say which 'defaults' are which better

[Jesse Smith]

On 10/13/19 4:33 PM, Michael Biebl wrote:
> Control: tags -1 + moreinfo
>
> On Sat, 28 Sep 2019 15:21:17 -0300 Jesse Smith
>  wrote:
>> This has been addressed upstream in insserv by allowing the program to
>> accept changes like this silently. All we need now is for update-rc.d to
>> be updated to use the new behaviour (enabled with the -q flag) and this
>> issue can be closed.
> Is it -q or --silent? Or are they the same?

-q and --silent do the same thing. These are now documented in the
manual page for insserv.

>
> Will insserv fail if the version is too old, i.e. do we need a versioned
> dependency (or rather versioned Breaks)?

Yes, older versions of insserv will fail if --silent is specified as it
will not be a recognized option. There should probably be a version
check. Or a check in the calling script to try with insserv --silent and
if it fails, try again without the flag.

> What exactly is suppressed by -q/--silent?
> Only this specific error about "defaults" or other error messages as
> well? Do we want to suppress all error messages?

The --silent flag suppresses warnings (non-fatal errors). Basically
anything that is a "heads up" warning is suppressed. Fatal errors and
issues which require user attention are still printed.

Bug#942269: ossim: FTBFS with GEOS 3.8.0 (error: no matching function for call)

[Bas Couwenberg]

Source: ossim
Version: 2.9.1-1
Severity: serious
Tags: upstream
Justification: makes the package in question unusable or mostly so
Control: forwarded -1 https://github.com/ossimlabs/ossim/issues/243

Dear Maintainer,

Your package FTBFS with GEOS 3.8.0:

 /build/ossim-2.9.1/src/base/ossimPolyArea2d.cpp: In member function 'void 
OssimPolyArea2dPrivate::setGeometry(const ossimPolygon&, const 
std::vector&)':
 /build/ossim-2.9.1/src/base/ossimPolyArea2d.cpp:152:64: error: no matching 
function for call to 
'geos::geom::GeometryFactory::createPolygon(geos::geom::LinearRing*&, 
std::vector*&)'
   152 |  m_geometry = geomFactory()->createPolygon(shell, holes);
   |^
 ...
 /build/ossim-2.9.1/src/base/ossimPolyArea2d.cpp:778:109: error: no matching 
function for call to 
'geos::geom::GeometryFactory::createMultiPolygon(std::vector&)
 const'
   778 |
m_privateData->setGeometry(m_privateData->m_geometry->getFactory()->createMultiPolygon(values));
   |
 ^
 ...
 /build/ossim-2.9.1/src/base/ossimPolyArea2d.cpp: In member function 'bool 
ossimPolyArea2d::loadState(const ossimKeywordlist&, const char*)':
 /build/ossim-2.9.1/src/base/ossimPolyArea2d.cpp:848:64: error: no matching 
function for call to 
'OssimPolyArea2dPrivate::setGeometry(std::unique_ptr)'
   848 | m_privateData->setGeometry(reader.read(wkt.c_str()));
   |^

Kind Regards,

Bas

Bug#942271: RM: darcsweb -- RoQA; depends on Python 2, unmaintained, dead upstream

[Moritz Muehlenhoff]

Package: ftp.debian.org
Severity: normal

Please remove darcsweb. It's dead upstream, unmaintained (last maintainer upload
in 2010) and depends on Python 2.

Cheers,
Moritz

Bug#942053: dh-runit: generates dangling symlinks

[Dmitry Bogatov]

[2019-10-09 18:01] Sven Joachim 
> Package: dh-runit
> Version: 2.8.14
>
> The fix for bug #934500 has the side effect of introducing broken
> symlinks[1] into packages using it, causing complaints by tools that
> report such oddities, e.g. adequate(1) or symlinks(1):

As I recall, dangling symlink is not violation of Policy (correct me if
I am wrong), so the best route is to teach these tools about this
special case, like we teach lintian.

So, I think adequate(1) need to be patched. Something else?

> I find that quite annoying.

Sorry, this is not enough. Debian strives to be universal operating
system, and pays the price for it: on every system there is something
that is not needed for how this system is used.

You can use dpkg-exclude to alleviate this particular issue somewhat.
-- 
Note, that I send and fetch email in batch, once in a few days.
Please, mention in body of your reply when you add or remove recepients.

Bug#941924: runit-helper: Remove log directory on purge

[Dmitry Bogatov]

control: tags -1 +pending

[2019-10-07 17:50] Lorenzo Puliti 
> Hi,

Hi,

> I think runit-helper should remove log directories when
> called with purge. See Debian Policy 10.8.
> Patch attached.

Yes, this is true. Thank you. Applied in git, not uploading yet due perl
transition.
-- 
Note, that I send and fetch email in batch, once in a few days.
Please, mention in body of your reply when you add or remove recepients.

Bug#556893: #556893,say which 'defaults' are which better

[Dmitry Bogatov]

control: reassign -1 init-system-helpers
control: tags -1 +patch

[2019-09-28 15:21] Jesse Smith 
> This has been addressed upstream in insserv by allowing the program to
> accept changes like this silently. All we need now is for update-rc.d to
> be updated to use the new behaviour (enabled with the -q flag) and this
> issue can be closed.

Thank you for bug triaging, Jesse. Reassigning back to
init-system-helpers.

Dear init-system-helpers maintainer, please consider applying following
patch:

From 638717158f50fa24a119b69ee0888158d306f492 Mon Sep 17 00:00:00 2001
From: Dmitry Bogatov 
Date: Sat, 12 Oct 2019 13:55:45 +
Subject: [PATCH] Prevent insserv(8) from printing too much debug

Closes: #556893
---
 script/update-rc.d | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/script/update-rc.d b/script/update-rc.d
index 71fb1a6..03d21cf 100755
--- a/script/update-rc.d
+++ b/script/update-rc.d
@@ -181,7 +181,7 @@ sub create_sequence {
 $insserv = "/sbin/insserv" if ( -x "/sbin/insserv");
 # If insserv is not configured it is not fully installed
 my $insserv_installed = -x $insserv && -e "/etc/insserv.conf";
-my @opts;
+my @opts = ('--silent');
 push(@opts, '-f') if $force;
 # Add force flag if initscripts is not installed
 # This enables inistcripts-less systems to not fail when a facility is 
missing


-- 
Note, that I send and fetch email in batch, once in a few days.
Please, mention in body of your reply when you add or remove recepients.

Bug#942275: libmoox-options-perl: test failure

[gregor herrmann]

Source: libmoox-options-perl
Version: 4.103-1
Severity: serious
Tags: ftbfs sid bullseye
Justification: fails to build from source

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

As first seen on ci.debian.net, libmoox-options-perl has a test
failure which also makes the package FTBFS:

https://ci.debian.net/data/autopkgtest/unstable/amd64/libm/libmoox-options-perl/3150674/log.gz

t/16-namespace_clean.t .. 
ok 1 - TestNamespaceClean is a package
Can't locate object method "__" via package "TestNamespaceClean" at 
/usr/share/perl5/MooX/Options/Role.pm line 352.
# Tests were run but no plan was declared and done_testing() was not seen.
# Looks like your test exited with 255 just after 1.
Dubious, test returned 255 (wstat 65280, 0xff00)
All 1 subtests passed 


Currently this only happens in unstable, and I haven't yet seen why.


Cheers,
gregor

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAl2jWF9fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgYIqw//XGnU4dpmTGHf/zNwzGrxbtXxwtCws0FycziVOMyibaHrsSnfWo1z4q9x
S2l9SRolRx6QdzS0iXdege9Ay0tqAvE+ae6lGkHsb6zg8fe1oGGkh8B35TMx6U0j
jhjjtJU0iruB0mMr783TKH/4kWlAOfTprq6C0MPbiJ5WBm3v+sCe2JArfKIJhcW6
GheUF+lH2zsXR9u6AcZK5uOlxo/Bjawak6akbxbNfPxxcpOWKmUz9V1h8iaElim6
qqgiAJRXMDty0+tNP3tYYK4ta4cwUzj2cGevfBIBlNYhUMsK7sRlLjO2Rb6e22mU
wwr5HGcEjkr1o//h7wZ1bYU/yK5GDtrw0lnbluG9qHu1cO0kIYF0Cut8wTWisw9q
aPYau5b6xE+70swsRiArrA3UPrmWKgUK2lRhZC1MVzpakFT01uaINwaMyCL606bG
jB4/g7+BbKmLCyTSOx0uWaRIG5KgtFQTm8Dm7agjQdsLVMTmOXzRQi7saP0slHCT
ak80F2h4LY3PtlNWK9+T1RBHkC0FaZxOqWVEVUVXC+U4kSQzF8F5ir8NwiDPKr1E
+kYXOdecvcKw1nC+SKQIJLrAt2ibTjogd33v5QXIjRNd+/lHtZeHANV5m5TeNqWK
uNEo2qrVys+d2RAWBjvboxJgtW7K24cMnUTYIw6C9kc2UJc7/K4=
=vx9q
-END PGP SIGNATURE-

Bug#942276: libmessage-passing-perl: test failure

[gregor herrmann]

Source: libmessage-passing-perl
Version: 0.116-4
Severity: serious
Tags: ftbfs sid bullseye
Justification: fails to build from source

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

As seen on 
https://ci.debian.net/data/autopkgtest/unstable/amd64/libm/libmessage-passing-perl/3150247/log.gz
we have a test failure which also happens at build time and makes the
package FTBFS:

t/configfile.t .. 
ok 1 - use Message::Passing;
Can't locate object method "_options_prog_name" via package "Message::Passing" 
at /usr/share/perl5/MooX/Options/Role.pm line 348.
# Tests were run but no plan was declared and done_testing() was not seen.
# Looks like your test exited with 25 just after 1.
Dubious, test returned 25 (wstat 6400, 0x1900)
All 1 subtests passed 


Cheers,
gregor

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAl2jWdFfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgapGA//UnAloNglGDbKd6YCFqojZkoe690l2Nxkiv9g2Y1vnGxVD+X8kU3jaWb8
btnYiy2j5IUG6hfZkrK8beDaB9zozu3/UOg/QgARYI+n2WXnqhufNqS7XRBrmg6e
RupIB5Yi/c3lmPzzW2rNG7QyjudvjeoncNX05uxGK98tS7Rv9cGyVOLB3AHBnxPD
/WkQPtJu0myhOF0SrQMZ2mzbw5+JQlXAUNs3bi20mDP6YG5ISJB108cOnFe6lfRt
OX8Gwl0ZeHLeoVrbqo9wOVtDxU4qtFJH4v6hItM7271NpFv76PDEpdhIGi1xsTx3
51uH/lLvfSuKV5xKCb2RevgG8q5JCqzXoqtov0JOtu7eO8kGCCOOLAUvlDtjyW7i
zZlxj/Z2IhPUwvG1xitMGMu2/t37jXfRxoSTW532RlHrMf2UqOxlv9wgY/ygexwT
arzWOvGX5fFfiHuyULYiP7Fxis/5KttCd2wnICe+I8u9dVURlFWRSUDnoQ1PC9my
fw8KNF7/J9a+LkrHsb3rFwEVzDy8sizAimYnJyuz63SeEzBnnavEuFLLsmf6Bqdw
akeXO28zlwN3PC8RlkrOmPzZPH+F1wuC+L6SzTH2A97fG8eKlogkczs8UXSA5PsI
IEynKsJPZSbEUz/tRNJUPuE5v63vLK2scganIuXGwMoj+KDOeGE=
=Yfoi
-END PGP SIGNATURE-

Bug#942275: libmoox-options-perl: test failure

[gregor herrmann]

On Sun, 13 Oct 2019 19:01:19 +0200, gregor herrmann wrote:

> Currently this only happens in unstable, and I haven't yet seen why.

Maybe yesterday's upload of libnamespace-autoclean-perl?


Cheers,
gregor
-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Peter Ratzenbeck: Bonnie Bessie Logan


signature.asc
Description: Digital Signature

Bug#932456: (no subject)

[Robert Niederreiter]

Hi,

I encountered the same problem.

It looks like libvirt denies write access to guest base image by 
modifying the guest related apparmor profile once the guest runs on a 
snapshot referring to this base image.


Here's what i tried:

Guest runs on base image:

root@host/storage/vm# virsh domblklist test
 Target   Source

 vda  /storage/vm/test.img

Generated aa profile not contains deny rule for base image:

root@host/storage/vm# cat /etc/apparmor.d/libvirt/libvirt-.files
# DO NOT EDIT THIS FILE DIRECTLY. IT IS MANAGED BY LIBVIRT.
  "/var/log/libvirt/**/test.log" w,
  "/var/lib/libvirt/qemu/domain-test/monitor.sock" rw,
  "/var/lib/libvirt/qemu/domain-8-test/*" rw,
  "/var/run/libvirt/**/test.pid" rwk,
  "/run/libvirt/**/test.pid" rwk,
  "/var/run/libvirt/**/*.tunnelmigrate.dest.test" rw,
  "/run/libvirt/**/*.tunnelmigrate.dest.test" rw,
  "/storage/vm/test.img" rwk,  <---
  "/dev/vhost-net" rw,
  "/var/lib/libvirt/qemu/domain-8-test/{,**}" rwk,
  "/var/lib/libvirt/qemu/channel/target/domain-8-test/{,**}" rwk,
  "/var/lib/libvirt/qemu/domain-8-test/master-key.aes" rwk,
  "/dev/net/tun" rwk,

After generating the snapshot, there's still no deny rule (but we also not 
tried to merge back to base image yet):

root@host/storage/vm# virsh snapshot-create-as --domain test --name 
backup_overlay --no-metadata --atomic --disk-only --diskspec 
vda,snapshot=external
Domain snapshot backup_overlay created

root@host/storage/vm# cat /etc/apparmor.d/libvirt/libvirt-.files
# DO NOT EDIT THIS FILE DIRECTLY. IT IS MANAGED BY LIBVIRT.
  "/var/log/libvirt/**/test.log" w,
  "/var/lib/libvirt/qemu/domain-test/monitor.sock" rw,
  "/var/lib/libvirt/qemu/domain-8-test/*" rw,
  "/var/run/libvirt/**/test.pid" rwk,
  "/run/libvirt/**/test.pid" rwk,
  "/var/run/libvirt/**/*.tunnelmigrate.dest.test" rw,
  "/run/libvirt/**/*.tunnelmigrate.dest.test" rw,
  "/storage/vm/test.img" rwk,  <---
  "/dev/pts/2" rw,
  "/dev/pts/2" rw,
  
"/var/lib/libvirt/qemu/channel/target/domain-8-test/org.qemu.guest_agent.0" rw,
  "/dev/vhost-net" rw,
  "/storage/vm/test.backup_overlay" rwk,

When shutting down and starting guest again, host specific aa profile gets 
regenerated.
Now the deny rule is present. Note that guest runs on snapshot:

root@host/storage/vm# virsh domblklist test
 Target   Source
---
 vda  /storage/vm/test.backup_overlay

root@host/storage/vm# virsh shutdown test
Domain test is being shutdown

root@host/storage/vm# virsh start test
Domain test started

root@host/storage/vm# cat /etc/apparmor.d/libvirt/libvirt-.files
# DO NOT EDIT THIS FILE DIRECTLY. IT IS MANAGED BY LIBVIRT.
  ...
  "/storage/vm/test.img" rk,   <---
  # don't audit writes to readonly files
  deny "/storage/vm/test.img" w,  <
  "/dev/vhost-net" rw,
  ...

And it seems like this rule prevents us from merging snapshot back to base 
image:

root@host/storage/vm# virsh blockcommit test vda --active --pivoterror: 
internal error: unable to execute QEMU command 'block-commit': Could not reopen 
file: Permission denied

As soon as the guest aa profile gets disabled, blockcommit works as expected:

root@host/storage/vm# aa-disable /etc/apparmor.d/libvirt/libvirt-
Disabling /etc/apparmor.d/libvirt/libvirt-.

root@host/storage/vm# virsh blockcommit test vda --active --pivot
Successfully pivoted

After merge, stop and start guest, the deny rule is gone again:

root@host/storage/vm# virsh shutdown test
Domain test is being shutdown

root@host/storage/vm# virsh start test
Domain test started

root@host/storage/vm# cat /etc/apparmor.d/libvirt/libvirt-.files
# DO NOT EDIT THIS FILE DIRECTLY. IT IS MANAGED BY LIBVIRT.
  ...
  "/storage/vm/test.img" rwk,
  "/dev/vhost-net" rw,
  ...

root@host/storage/vm# virsh domblklist test
 Target   Source

 vda  /storage/vm/test.img

As stated above, the deny rule is not created immediately when creating the 
snapshot
if guest not gets stopped/started. But it gets added as soon as we try to merge 
back
to the base image:

root@host/storage/vm# virsh snapshot-create-as --domain test --name 
backup_overlay --no-metadata --atomic --disk-only --diskspec 
vda,snapshot=external
Domain snapshot backup_overlay created

root@host/storage/vm# cat /etc/apparmor.d/libvirt/libvirt-.files
# DO NOT EDIT THIS FILE DIRECTLY. IT IS MANAGED BY LIBVIRT.
  ...
  "/storage/vm/test.img" rwk,
  ...

root@host/storage/vm# virsh blockcommit test vda --active --pivoterror: 
internal error: 

Bug#941078: transition: postgresql-12

[Christoph Berg]

Re: Paul Gevers 2019-10-13 
> The migration is currently blocked on the regression of repmgr. I just
> triggered a reference run as I think the postgresql-11 migration in the
> perl transition will have caused the current state in testing to be bad
> already. If that's not the case, and it's really postgresql-12 related,
> how do you propose we treat the situation?

Marco said there would be a new repmgr release tomorrow. That can
transition to testing independently first, and then PG12 will be good
to go.

Christoph

Bug#906578: [makehuman] Future Qt4 removal

[Boyuan Yang]

Looks like makehuman upstream is working on the Qt5 version but it hasn't
finished yet. There's only alpha versions at 
https://github.com/makehumancommunity/makehuman . I guess we should move on
and have it removed if upstream is acting that slowly.

Muammar: if you have any other thoughts, please let us know now. Otherwise a
removal before 2020 should be reasonable.

Regards,
Boyuan Yang

在 2019-10-11五的 23:14 +0200，Moritz Mühlenhoff写道：
> Hi,
> there hasn't been any followup on this bug since over a year and we're now
> moving
> forward with the Qt4 removal, are there immediate plans to port makehuman to
> Qt5 or
> should we remove it from the archive?
> 
> Cheers,
> Moritz


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

Bug#937303: Please port to Python3 (#48)

[Olly Betts]

On Tue, Sep 17, 2019 at 02:29:45PM +, Alex Mestiashvili wrote:
> plip is actually python3 compatible, however it depends on
> python3-openbabel which is not yet in the archive, but some work is
> already done on the salsa repository. Once python3-openbabel is
> accepted into unstable I'll update plip packaging.

python3-openbabel is now in unstable:

$ rmadison python3-openbabel
python3-openbabel | 2.4.1+dfsg-4  | buildd-unstable | amd64, arm64, armel, 
armhf, i386, mips64el, mipsel, ppc64el, s390x
python3-openbabel | 2.4.1+dfsg-4  | unstable| amd64, arm64, armel, 
armhf, i386, mips64el, mipsel, ppc64el, s390x

Cheers,
Olly

Bug#939526: inn2 2.6.3-1+deb10u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 939526 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: inn2
Version: 2.6.3-1+deb10u1

Explanation: fix negotiation of DHE ciphersuites

Bug#941468: plasma-applet-redshift-control 1.0.18-2+deb10u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 941468 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: plasma-applet-redshift-control
Version: 1.0.18-2+deb10u1

Explanation: fix manual mode when used with redshift versions above 1.12

Bug#941348: fence-agents 4.3.3-2+deb10u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 941348 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: fence-agents
Version: 4.3.3-2+deb10u1

Explanation: fix incomplete removal of fence_amt_ws