date:20200829

On Thu, 2020-08-27 at 19:42 +0100, Sudip Mukherjee wrote:
> On Thu, Aug 27, 2020 at 7:37 PM 積丹尼 Dan Jacobson  > wrote:
> > Actually I am guessing the current maintainer isn't reading these
> > emails, and you Sudip, should consider non-maintainer uploads or
> > steps
> > on how to take over the project altogether from non-active
> > maintainers.
> 
> Thats package hijacking. And Osamu is an active developer. So, I
> can't do that.
> And besides, We are all at debconf now so please expect delayed
> reply.

Sudip

You can hijack if you are competent DM.  I am happy with this.


Osamu

Bug#969247: boinc-manager: New version of boinc-manager fails to start with gui_rpc_auth.cfg not readable

2020-08-29 Thread Dean Loros

Package: boinc-manager
Version: 7.16.15+dfsg.is.7.16.7+dfsg-2
Severity: important

Dear Maintainer,

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

   * What led up to the situation? Normal update to 7.16.15+dfsg is
7.16.10+dfsg+1. Afterwards, manager would not start with a error of
gui_rpc_auth.cfg file is unreadable -- permissions problem
   * What exactly did you do (or not do) that was effective (or
 ineffective)? I went into /etc/boinc-client & found that several of the
files were owned by /root, not by boinc. Corrected them & still had a problem
with boinc-manager. I removed all boinc files & downgraded to the prior version
to get boinc to work again.
   * What was the outcome of this action? boinc-manager would not start--still
had the same error message.
   * What outcome did you expect instead? I expected boinc-manager to work
normally.

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



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

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

Versions of packages boinc-manager depends on:
ii  boinc-client  7.16.15+dfsg.is.7.16.7+dfsg-2
ii  libboinc7 7.16.15+dfsg.is.7.16.7+dfsg-2
ii  libc6 2.31-3
ii  libgcc-s1 10.2.0-5
ii  libglib2.0-0  2.64.4-1
ii  libgtk-3-03.24.22-1
ii  libnotify40.7.9-1
ii  libsqlite3-0  3.33.0-1
ii  libstdc++610.2.0-5
ii  libwxbase3.0-0v5  3.0.5.1+dfsg-2
ii  libwxgtk-webview3.0-gtk3-0v5  3.0.5.1+dfsg-2
ii  libwxgtk3.0-gtk3-0v5  3.0.5.1+dfsg-2

boinc-manager recommends no packages.

Versions of packages boinc-manager suggests:
pn  libgl1-mesa-glx  
ii  libxt6   1:1.2.0-1

-- no debconf information

Bug#969244: libreoffice: crash upon opening "Advanced" tab in Options

2020-08-29 Thread JCGoran

Package: libreoffice
Version: 1:7.0.1~rc1-2
Severity: important
X-Debbugs-Cc: jcgo...@protonmail.com

Dear Maintainer,

Opening the "Advanced" tab in Tools > Options consistently causes a
crash in all LibreOffice components. I tried rebooting my machine and
deleting the LO profile, but the problem persists.
Using Safe mode, I can access the tab just fine, but exiting the 
Options window again causes a crash.

The only available option I can see in the tab is
"Use a Java runtime environment" (checked), version 11.0.8.
I'm currently unable to verify whether toggling it fixes the behavior
since the crash happens before I am able to do anything.



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

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

Versions of packages libreoffice depends on:
ii  libreoffice-base1:7.0.1~rc1-2
ii  libreoffice-calc1:7.0.1~rc1-2
ii  libreoffice-core1:7.0.1~rc1-2
ii  libreoffice-draw1:7.0.1~rc1-2
ii  libreoffice-impress 1:7.0.1~rc1-2
ii  libreoffice-math1:7.0.1~rc1-2
ii  libreoffice-report-builder-bin  1:7.0.0~rc2-1
ii  libreoffice-writer  1:7.0.1~rc1-2
ii  python3-uno 1:7.0.1~rc1-2

Versions of packages libreoffice recommends:
ii  fonts-crosextra-caladea 20130214-2
ii  fonts-crosextra-carlito 20130920-1
ii  fonts-dejavu2.37-2
ii  fonts-liberation1:1.07.4-11
ii  fonts-liberation2   2.1.1-1
ii  fonts-linuxlibertine5.3.0-4
ii  fonts-noto-core 20200323-1
ii  fonts-noto-extra20200323-1
ii  fonts-noto-mono 20200323-1
ii  fonts-noto-ui-core  20200323-1
ii  fonts-sil-gentium-basic 1.102-1
ii  libreoffice-java-common 1:7.0.1~rc1-2
ii  libreoffice-nlpsolver   0.9+LibO6.4.4-1
ii  libreoffice-report-builder  1:7.0.0~rc2-1
ii  libreoffice-script-provider-bsh 1:6.4.4-1
ii  libreoffice-script-provider-js  1:6.4.4-1
ii  libreoffice-script-provider-python  1:6.4.4-1
ii  libreoffice-sdbc-mysql  1:6.4.4-1
ii  libreoffice-sdbc-postgresql 1:7.0.0~rc2-1
ii  libreoffice-wiki-publisher  1.2.0+LibO6.4.4-1

Versions of packages libreoffice suggests:
ii  cups-bsd2.3.3-2
ii  default-jre [java8-runtime] 2:1.11-72
ii  firefox-esr 68.11.0esr-1
ii  ghostscript 9.52~dfsg-1
ii  gnupg   2.2.20-1
pn  gpa 
ii  gstreamer1.0-libav  1.16.2-2
ii  gstreamer1.0-plugins-bad1.16.2-2.1
ii  gstreamer1.0-plugins-base   1.16.2-4
ii  gstreamer1.0-plugins-good   1.16.2-3
ii  gstreamer1.0-plugins-ugly   1.16.2-2
ii  hunspell-bg [hunspell-dictionary]   1:7.0.0-1
ii  hunspell-bn [hunspell-dictionary]   1:7.0.0-1
ii  hunspell-bs [hunspell-dictionary]   1:7.0.0-1
ii  hunspell-ca [hunspell-dictionary]   3.0.6+repack1-1
ii  hunspell-cs [hunspell-dictionary]   1:7.0.0-1
ii  hunspell-da [hunspell-dictionary]   1:7.0.0-1
ii  hunspell-de-at [hunspell-dictionary]20161207-8
ii  hunspell-de-ch [hunspell-dictionary]20161207-8
ii  hunspell-de-de [hunspell-dictionary]20161207-8
ii  hunspell-en-gb [hunspell-dictionary]1:7.0.0-1
ii  hunspell-en-us [hunspell-dictionary]1:2019.10.06-1
ii  hunspell-eu [hunspell-dictionary]   0.5.20151110-5
ii  hunspell-fr-classical [hunspell-dictionary] 1:6.4.1-1
ii  hunspell-gl [hunspell-dictionary]   1:7.0.0-1
ii  hunspell-gu [hunspell-dictionary]   1:7.0.0-1
ii  hunspell-hi [hunspell-dictionary]   1:7.0.0-1
ii  hunspell-hr [hunspell-dictionary]   1:7.0.0-1
ii  hunspell-id [hunspell-dictionary]   1:7.0.0-1
ii  hunspell-is [hunspell-dictionary]   1:7.0.0-1
ii  hunspell-it [hunspell-dictionary]   1:7.0.0-1
ii  hunspell-kk [myspell-dictionary]1.1-2
ii  hunspell-kmr [hunspell-dictionary]  1:7.0.0-1
ii  hunspell-ko [hunspell-dictionary]   0.7.92-1
ii  hunspell-lt [hunspell-dictionary]   1:7.0.0-1
ii  hunspell-lv [hunspell-dictionary]

Bug#969227: FTBFS with new runc 1.0.0~rc92 and libcap2 2.43

2020-08-29 Thread Dmitry Smirnov

On Sunday, 30 August 2020 3:01:34 AM AEST Shengjing Zhu wrote:
> Please see the patches attached.

Thank you very much!

> BTW, is there any instruction to work with the docker.io git repo?
> It seems `gbp buildpackage` or `gbp pq` are hard to use with it.

Something like the following:

  https://salsa.debian.org/onlyjob/notes/-/wikis/bp

Start with "debian" directory, obtain and extract orig tarballs with
'origtargz' then build with your preferred method (e.g. pbuilder).

MUT and complex Golang packages are ridiculously difficult to maintain
with GBP...

See also https://salsa.debian.org/onlyjob/notes/-/wikis/no-gbp

-- 
Best wishes,
 Dmitry Smirnov.

---

Truth — Something somehow discreditable to someone.
-- H. L. Mencken, 1949

---

A study on infectivity of asymptomatic SARS-CoV-2 carriers, concludes weak
transmission. "The median contact time for patients was four days and that
for family members was five days."
-- https://pubmed.ncbi.nlm.nih.gov/32513410/

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

Bug#769107: debian-installer: grub-installer fails if more than 26 SCSI devices are present

2020-08-29 Thread Ben Hutchings

On Sun, 2020-08-23 at 13:38 +0200, Holger Wansing wrote:
> 
> Ben Hutchings  wrote (24 Nov 2014 04:09:01):
> > device_to_disk already knows how to do the mapping.  We have this
> > complicated wildcard here which doesn't match the regexp in
> > device_to_disk, only because no-one got round to clearing out the devfs
> > cruft which is the following '*' case.
> > 
> > So I propose this instead:
> > 
> > Subject: Remove devfs case for mapping partitions to whole disk names
> >  (Closes: #769107)
> > 
> > Rather than using an unmaintainable wildcard for non-devfs
> > partition device names, we should remove the obsolete devfs
> > case and use device_to_disk by default.
> > 
> > Also remove one of the many pointless uses of mapdevfs.
> 
> Hi, 
> 
> what's the status here?
> Should this be committed?
> Or should I file this bug as will-not-fix?

I think this should be fixed, but I don't know that I ever got as far
as testing that patch.  So this should probably wait until someone has
done that.

Ben.

-- 
Ben Hutchings
It is easier to change the specification to fit the program
than vice versa.




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

Bug#940002: wireguard-dkms: Failure with kernel 4.19.0-8

2020-08-29 Thread Alex

Package: wireguard-dkms
Version: 1.0.20200712-1
Followup-For: Bug #940002

Dear Maintainer,
here is the log for the failure with linux 4.19.0, which looks a bit different 
from the other build error:

DKMS make.log for wireguard-1.0.20200712 for kernel 4.19.0-8-amd64 (x86_64)
Sat Aug 29 21:33:56 CEST 2020
make: Entering directory '/usr/src/linux-headers-4.19.0-8-amd64'
  CC [M]  /var/lib/dkms/wireguard/1.0.20200712/build/main.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20200712/build/noise.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20200712/build/device.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20200712/build/peer.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20200712/build/timers.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20200712/build/queueing.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20200712/build/send.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20200712/build/receive.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20200712/build/socket.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20200712/build/peerlookup.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20200712/build/allowedips.o
  CC [M]  /var/lib/dkms/wireguard/1.0.20200712/build/ratelimiter.o
/var/lib/dkms/wireguard/1.0.20200712/build/socket.c: In function 'send6':
/var/lib/dkms/wireguard/1.0.20200712/build/socket.c:139:20: error: 'const 
struct ipv6_stub' has no member named 'ipv6_dst_lookup_flow'; did you mean 
'ipv6_dst_lookup'?
   dst = ipv6_stub->ipv6_dst_lookup_flow(sock_net(sock), sock, ,
^~~~
ipv6_dst_lookup
make[3]: *** 
[/usr/src/linux-headers-4.19.0-8-common/scripts/Makefile.build:308: 
/var/lib/dkms/wireguard/1.0.20200712/build/socket.o] Error 1
make[3]: *** Waiting for unfinished jobs
make[2]: *** [/usr/src/linux-headers-4.19.0-8-common/Makefile:1537: 
_module_/var/lib/dkms/wireguard/1.0.20200712/build] Error 2
make[1]: *** [Makefile:146: sub-make] Error 2
make: *** [Makefile:8: all] Error 2
make: Leaving directory '/usr/src/linux-headers-4.19.0-8-amd64'


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

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

Versions of packages wireguard-dkms depends on:
ii  dkms  2.6.1-4
ii  perl  5.28.1-6+deb10u1

Versions of packages wireguard-dkms recommends:
iu  wireguard1.0.20200820-1
ii  wireguard-tools  1.0.20200820-1

wireguard-dkms suggests no packages.

-- no debconf information

Bug#884592: [Pkg-fonts-devel] Bug#884592 fonts-fantasque-sans: variants use the same name, making them unusable in most programs

2020-08-29 Thread Walter Landry

Hello,

I just ran into this bug.  When set up by default, I get the
LargeLineHeight variant, which is definitely not what I want.  When
using Font Manager or Gnome Tweaks, it is really not clear to me how I
can even select other variants.  So, for what it is worth, my vote is to
have separate named variants.  Right now, running fc-list, I get the
font names

Fantasque Sans Mono:style=Bold
Fantasque Sans Mono:style=Bold Italic
Fantasque Sans Mono:style=Italic
Fantasque Sans Mono:style=Regular

To incorporate the NoLoopK and LargeLineHeight variants, I would propose
the names:

Fantasque Sans Mono:style=Regular
Fantasque Sans NoLoopK Mono:style=Regular
Fantasque Sans LargeLineHeight Mono:style=Regular
Fantasque Sans LargeLineHeight NoLoopK Mono:style=Regular

Fantasque Sans Mono:style=Bold Italic
Fantasque Sans NoLoopK Mono:style=Bold Italic
Fantasque Sans LargeLineHeight Mono:style=Bold Italic
Fantasque Sans LargeLineHeight NoLoopK Mono:style=Bold Italic

Fantasque Sans Mono:style=Italic
Fantasque Sans NoLoopK Mono:style=Italic
Fantasque Sans LargeLineHeight Mono:style=Italic
Fantasque Sans LargeLineHeight NoLoopK Mono:style=Italic

Fantasque Sans Mono:style=Regular
Fantasque Sans NoLoopK Mono:style=Regular
Fantasque Sans LargeLineHeight Mono:style=Regular
Fantasque Sans LargeLineHeight NoLoopK Mono:style=Regular

If it would be helpful, I could put together a patch.

Thanks,
Walter Landry

Bug#969246: RFP: coffeine -- CLI tool to keep your [device|mobile phone] from blanking or suspending

2020-08-29 Thread Sebastian Spaeth


Package: coffein
Version: 0.2; reported 2020-08-29
Severity: wishlist

* Package name : coffeine
Version : 0.2
Upstream Author : Sebastian Spaeth 
* URL : https://gitlab.com/sspaeth/coffeine/
* License : GPL-3+
Description : Keeps your computer awake at day (& night)

... as long as your desktop supports the org.freedesktop.ScreenSaver 
standard.


Just type 'coffeine YOURPROGRAMHERE' to prevent the screensaver from 
interrupting your video session or your system from suspending while you 
apt dist-upgrade it.


---

coffeine is a small CLI tool written in vala. A full-fledged "debian" 
directory which is used to build the package is already included in the 
main repository and it is included in the main "mobian" repository. I am 
the creator of coffeine and I am willing to maintain the "debian" 
metadata to keep the package building and to react to bugs that are 
filed against it.

Bug#880107: [RSVP] Re: Bug#880107: heimdall-flash: cannot flash RECOVERY on Samsung Note 3 (SM-N9005, hlte)

2020-08-29 Thread Thorsten Glaser

Dixi quod…

>Anyway, back to topic: the TWRP update went problemless,

Ah, forgot: the manpage is completely, utterly shot and
probably causes multiple lintian warnings as well ;-) it
doesn’t honour the manpage format and doesn’t help the
user much either. The description of the options is also
missing (which IIRC is a regression as it used to have
at least a little bit of that) and it mentions mostly a
frontend tool that isn’t even installed.

You might wish to do something about that some day…

bye,
//mirabilos
-- 
> Hi, does anyone sell openbsd stickers by themselves and not packaged
> with other products?
No, the only way I've seen them sold is for $40 with a free OpenBSD CD.
-- Haroon Khalid and Steve Shockley in gmane.os.openbsd.misc

Bug#880107: [RSVP] Re: Bug#880107: heimdall-flash: cannot flash RECOVERY on Samsung Note 3 (SM-N9005, hlte)

2020-08-29 Thread Thorsten Glaser

Nicholas D Steeves dixit:

>So it looks to me like this bug fell through the cracks during the
>process of changing submitter of your bugs from the former to the

I didn’t, because I have my From set to the mirbsd.de address for
historical reasons and mailing lists that check the Header-From :/
and changing the address for all bugs, plus the reportbug config
on way too many systems, isn’t worth it. Maintainers are encouraged
to use nn-submitter@b.d.o anyway.

>who use self-hosted email to work towards DD: eg, then users who
>aren't familiar with advanced BTS use can follow-up on bugs, and reach
>the pkg's maintainer, because the debian.org address forwards it.

No, the BTS can do this, see above.

>> >Would you please test 1.4.2+dfsg-1 currently available in testing and
>> >unstable?  I can provide a buster-backport for testing purposes if
>>
>> I can do that, but it’ll probably take me some days, first I
>> need to find that device… (and something to flash).
>
>Thanks, much appreciated!  I'm guessing that by now your device could
>use a TWRP upgrade, so maybe that?

It does, but I had to actually *find* it first. I mostly use the
HTC Desire instead because it both works better (especially GPS)
and is smaller than the Note 3.

>It sounds like your greylist could benefit from SPF Record
>updates--either supervised, or automatic, as you prefer.

No, greylisting takes (ip, HELO, MAIL From, RECV To) tuples
and requires them to match in the second connection, then it
updates the firewall so the third connection from that IP
will reach the MTA.

Anyway, back to topic: the TWRP update went problemless,
so the bug can be closed.

Thanks,
//mirabilos
-- 
  "Using Lynx is like wearing a really good pair of shades: cuts out
   the glare and harmful UV (ultra-vanity), and you feel so-o-o COOL."
 -- Henry Nelson, March 1999

Bug#969245: cinnamon: Network applet - List of Wireless Networks doesn't refresh properly when clicking the applet logo

2020-08-29 Thread Joshua Peisach

Package: cinnamon
Version: 4.6.7-1
Severity: normal
Tags: patch
X-Debbugs-Cc: itzswirlz2...@outlook.com

Dear Maintainer,

All the information for the bug is here:
https://github.com/linuxmint/cinnamon/issues/9531

When the list of wireless connections is displayed, the list of wireless
connections available don't refresh properly.

A patch here is now available for just that, from this commit:
https://github.com/linuxmint/cinnamon/commit/42960e3

Bug has already been reported and fixed upstream.



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

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

Versions of packages cinnamon depends on:
ii  cinnamon-common  4.6.7-1
ii  cinnamon-control-center  4.6.2-2
ii  cinnamon-desktop-data4.6.4-1
ii  cinnamon-screensaver 4.6.0-2
ii  cinnamon-session 4.6.2-1
ii  cinnamon-settings-daemon 4.6.4-1
ii  cjs  4.6.0-2
ii  cups-pk-helper   0.2.6-1+b1
ii  dconf-gsettings-backend [gsettings-backend]  0.36.0-1
ii  gir1.2-accountsservice-1.0   0.6.55-3
ii  gir1.2-caribou-1.0   0.4.21-7
ii  gir1.2-clutter-1.0   1.26.4+dfsg-1
ii  gir1.2-cmenu-3.0 4.6.1-1
ii  gir1.2-cogl-1.0  1.22.8-1
ii  gir1.2-cvc-1.0   4.6.4-1
ii  gir1.2-gdkpixbuf-2.0 2.40.0+dfsg-5
ii  gir1.2-gkbd-3.0  3.26.1-1
ii  gir1.2-glib-2.0  1.64.1-1
ii  gir1.2-gnomedesktop-3.0  3.36.4-1
ii  gir1.2-gtk-3.0   3.24.22-1
ii  gir1.2-gtkclutter-1.01.8.4-4
ii  gir1.2-keybinder-3.0 0.3.2-1+b1
ii  gir1.2-meta-muffin-0.0   4.6.3-1
ii  gir1.2-nemo-3.0  4.6.5-1
ii  gir1.2-nm-1.01.26.2-1
ii  gir1.2-nma-1.0   1.8.30-1
ii  gir1.2-notify-0.70.7.9-1
ii  gir1.2-pango-1.0 1.46.0-2
ii  gir1.2-polkit-1.00.105-29
ii  gir1.2-soup-2.4  2.70.0-1
ii  gir1.2-timezonemap-1.0   0.4.6-2
ii  gir1.2-upowerglib-1.00.99.11-2
ii  gir1.2-xapp-1.0  1.8.9-1
ii  gkbd-capplet 3.26.1-1
ii  gnome-backgrounds3.36.0-1
ii  gnome-themes-extra   3.28-1
ii  gsettings-desktop-schemas3.36.1-1
ii  iso-flags-png-320x2401.0.2-1
ii  libatk-bridge2.0-0   2.34.1-3
ii  libatk1.0-0  2.36.0-2
ii  libc62.31-3
ii  libcairo21.16.0-4
ii  libcinnamon-desktop4 4.6.4-1
ii  libcinnamon-menu-3-0 4.6.1-1
ii  libcjs0  4.6.0-2
ii  libcroco30.6.13-1
ii  libgdk-pixbuf2.0-0   2.40.0+dfsg-5
ii  libgirepository-1.0-11.64.1-1
ii  libgl1   1.3.2-1
ii  libglib2.0-0 2.64.4-1
ii  libglib2.0-bin   2.64.4-1
ii  libgstreamer1.0-01.16.2-2
ii  libgtk-3-0   3.24.22-1
ii  libmuffin0   4.6.3-1
ii  libpango-1.0-0   1.46.0-2
ii  libpangocairo-1.0-0  1.46.0-2
ii  libstartup-notification0 0.12-6
ii  libx11-6 2:1.6.10-3
ii  libxfixes3   1:5.0.3-2
ii  libxml2  2.9.10+dfsg-5+b1
ii  mesa-utils   8.4.0-1+b1
ii  muffin   4.6.3-1
ii  nemo 4.6.5-1
ii  network-manager-gnome1.18.0-1
ii  policykit-1-gnome0.105-7
ii  python3  3.8.2-3
ii  python3-dbus 1.2.16-3
ii  python3-distro   1.5.0-1
ii  python3-gi   3.36.0-4
ii  python3-gi-cairo 3.36.0-4
ii  python3-pampy

Bug#964444: systemd-timesyncd: time synchronization suddenly stopped working

2020-08-29 Thread Vincent Lefevre

On 2020-08-29 16:45:49 +0200, Michael Biebl wrote:
> I see that this has been addressed in
> https://github.com/systemd/systemd/pull/16624 which is part of v246, so
> closing the bug report accordingly.

Note that the upstream solution is a bit incomplete. It reduces
the maximum time before sync to 6 minutes. But that's still up
to 6 minutes to wait after sleep/resume.

I've solved this issue on my side with a script
/etc/network/if-up.d/timesyncd to restart systemd-timesyncd after
the network is up (which yields an immediate NTP connection):


#!/bin/sh

[ "$IFACE" != "lo" ] || exit 0
[ -d /run/systemd/system ] || exit 0
[ -x /lib/systemd/systemd-timesyncd ] || exit 0

cmd="systemctl try-restart systemd-timesyncd.service"
[ -x /usr/bin/logger ] && /usr/bin/logger -t "${0#/etc/network/}" "$cmd"
$cmd || true


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

Bug#953533: opensc: Fails to build due to missing bash_completion files

2020-08-29 Thread Ludovic Rousseau

severity 953533 normal
thank

On Tue, 10 Mar 2020 08:10:06 + "Cirujano Cuesta, Silvano" 
 wrote:
> Package: opensc
> Version: 0.20.0-3
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
> Tags: ftbfs
> 
> Trying to build fails. I've tried following two ways.
> 
> I've tried
>   apt-get source opensc ; debuild -b -uc -us
> and
>   apt-get --build source opensc
> 
> 
> The error message is:
> 
>   dh_install: warning: Cannot find (any matches for) 
> "debian/tmp/etc/bash_completion.d/*"
> (tried in ., debian/tmp)
>   dh_install: warning: opensc missing files: 
> debian/tmp/etc/bash_completion.d/*
>   dh_install: error: missing files,aborting
>   make: *** [debian/rules:4: binary] Error 25

I can reproduce your problem using "debuild" in testing.
But I can't reproduce it using "gbp buildpackage" and cowbuilder

When the package is built with debuild I have:
" OpenSC has been configured with the following options:

[...]
Bash completion: /usr/share/bash-completion/completions
[...] "

But when the package is built with gbp (or the Debian builders) I find:
" OpenSC has been configured with the following options:

[...]
Bash completion: /etc/bash_completion.d
[...] "

The problem is this piece of code in configure.ac:
if test "${completiondir}" = "detect"; then
echo completion ${completiondir}
PKG_CHECK_MODULES([BASH_COMPLETION], [bash-completion >= 2.0],
[completiondir="`pkg-config --variable=completionsdir 
bash-completion`"],
[completiondir="${sysconfdir}/bash_completion.d"])
fi

If bash-completion package is installed then the scipt uses:
$ pkg-config --variable=completionsdir bash-completion
that returns:
/usr/share/bash-completion/completions

But if bash-completion is NOT installed then
${sysconfdir}/bash_completion.d i.e. /etc/bash_completion.d is used instead.

If you remove the package bash-completion then the build will succeed.

I changed the priority of this bug since it fails to build only in some
cases.

I wanted to push my patch to https://salsa.debian.org/opensc-team/opensc
but I am not a member of the "opensc-team" group on Salsa.
https://salsa.debian.org/opensc-team

My patch is attached so Eric can apply it.
>From ee128132d5ea8644151d7aa180fe580847de3c28 Mon Sep 17 00:00:00 2001
From: Ludovic Rousseau 
Date: Sat, 29 Aug 2020 22:26:24 +0200
Subject: [PATCH] Fix "Fails to build due to missing bash_completion files"

Fix bash_completion path (Closes: #953533)
---
 debian/changelog  | 9 +
 debian/control| 3 ++-
 debian/opensc.install | 2 +-
 3 files changed, 12 insertions(+), 2 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index 404cedf5..6b72f71e 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+opensc (0.20.0-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "Fails to build due to missing bash_completion files"
+Build-Depends: bash-completion so the correct path is found
+(Closes: #953533)
+
+ -- Ludovic Rousseau   Sat, 29 Aug 2020 22:25:43 +0200
+
 opensc (0.20.0-3) unstable; urgency=medium
 
   * Fix patch to use /etc/opensc for opensc.conf (Closes: 949229)
diff --git a/debian/control b/debian/control
index 374a55f2..03c11d73 100644
--- a/debian/control
+++ b/debian/control
@@ -3,7 +3,8 @@ Priority: optional
 Section: utils
 Maintainer: Debian OpenSC Maintainers 
 Uploaders: Eric Dorland 
-Build-Depends: debhelper-compat (= 12),
+Build-Depends: bash-completion,
+   debhelper-compat (= 12),
docbook-xsl,
flex,
help2man,
diff --git a/debian/opensc.install b/debian/opensc.install
index 6213ab66..753806cb 100644
--- a/debian/opensc.install
+++ b/debian/opensc.install
@@ -1,5 +1,5 @@
 debian/tmp/usr/bin/*
-debian/tmp/etc/bash_completion.d/* usr/share/bash-completion/completions
+debian/tmp/usr/share/bash-completion/completions
 
 debian/tmp/usr/share/man/man1/*
 debian/tmp/usr/share/man/man5/*
-- 
2.28.0

Bug#969091: pdns-backend-mysql: Queries calling stored procedures broken with recent MariaDB/MySQL

Control: tags -1 - unreproducible
Control: tags -1 + confirmed

* Xan Charbonnet  [200828 23:40]:
> On the pdns mailing list, it's been requested I file an issue in the GitHub
> repository.  I've done so:
> https://github.com/PowerDNS/pdns/issues/9421

Great.

In the meantime, this CI pipeline shows the problem too:

https://salsa.debian.org/dns-team/pdns/-/jobs/966951

ci-242-9a9d6b1e pdns_server[2176]: Backend reported permanent error which 
prevented lookup (GSQLBackend get: Could not bind parameters to mysql 
statement: CALL basic_query(?, ?): Prepared statement contains no metadata), 
aborting

Chris

Bug#952536: Drop support for architectures not supported by upstream?

2020-08-29 Thread Jelmer Vernooĳ

I can see two options here:

 1) drop support for architectures not supported by upstream

 2) disable the unsupported architecture check somehow
  * either by setting the environment variable
  * by patching out the check in the source code

I'm not entirely sure what the right thing is for our users; does etcd
actually work on the other platforms and/or do we have the bandwidth
to get it to work there, or would it be safer to just exclude them for
the moment?

Since one can either way set the ETC_UNSUPPORTED_ARCH environment
variable, does this warrant severity serious rather than e.g.
important?

Jelmer

Bug#965998: xletters: diff for NMU version 1.1.1-5.1

Control: tags 965998 + patch
Control: tags 965998 + pending

Dear maintainer,

I've prepared an NMU for xletters (versioned as 1.1.1-5.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Best,
Chris

diff -Nru xletters-1.1.1/debian/changelog xletters-1.1.1/debian/changelog
--- xletters-1.1.1/debian/changelog 2015-09-29 14:58:48.0 +
+++ xletters-1.1.1/debian/changelog 2020-08-29 20:56:59.0 +
@@ -1,3 +1,11 @@
+xletters (1.1.1-5.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Use netcat-openbsd, as -l -p port seems to work properly now.
+(Closes: #965998)
+
+ -- Chris Hofstaedtler   Sat, 29 Aug 2020 20:56:59 +
+
 xletters (1.1.1-5) unstable; urgency=low
 
   * Team upload, with Ben's blessing.
diff -Nru xletters-1.1.1/debian/control xletters-1.1.1/debian/control
--- xletters-1.1.1/debian/control   2015-09-29 15:00:48.0 +
+++ xletters-1.1.1/debian/control   2020-08-29 20:56:55.0 +
@@ -12,7 +12,7 @@
 
 Package: xletters
 Architecture: any
-Depends: netcat-traditional,
+Depends: netcat-openbsd,
  wenglish | wordlist,
  ${misc:Depends},
  ${shlibs:Depends}
diff -Nru xletters-1.1.1/debian/patches/series 
xletters-1.1.1/debian/patches/series
--- xletters-1.1.1/debian/patches/series2015-09-29 14:08:09.0 
+
+++ xletters-1.1.1/debian/patches/series2020-08-29 20:56:45.0 
+
@@ -1,3 +1,2 @@
 xletters.patch
 remove-data-hook.patch
-use-nc-traditional.patch
diff -Nru xletters-1.1.1/debian/patches/use-nc-traditional.patch 
xletters-1.1.1/debian/patches/use-nc-traditional.patch
--- xletters-1.1.1/debian/patches/use-nc-traditional.patch  2015-09-30 
09:58:32.0 +
+++ xletters-1.1.1/debian/patches/use-nc-traditional.patch  1970-01-01 
00:00:00.0 +
@@ -1,8 +0,0 @@
-Description: use nc-traditional
-Bug-Debian: https://bugs.debian.org/490121
 xletters-1.1.1.orig/xletters-duel
-+++ xletters-1.1.1/xletters-duel
-@@ -1,2 +1,2 @@
- #!/bin/sh
--nc -l -p 9090 | xletters -duel | (sleep 5; nc $1 9090)
-+nc.traditional -l -p 9090 | xletters -duel | (sleep 5; nc.traditional $1 9090)

Bug#969243: mpdas FTCBFS: uses the build architecture pkg-config

2020-08-29 Thread Helmut Grohne

Source: mpdas
Version: 0.4.5-1
Tags: patch upstream
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

mpdas fails to cross build from source, because the upstream Makefile
hard codes the build architecture pkg-config. Please consider applying
the attached patch to make mpdas cross buildable.

Helmut
--- mpdas-0.4.5.orig/Makefile
+++ mpdas-0.4.5/Makefile
@@ -1,14 +1,15 @@
 VERSION = 0.4.5
 
 CXX	?= g++
+PKG_CONFIG ?= pkg-config
 OBJ	= main.o md5.o utils.o mpd.o audioscrobbler.o cache.o config.o ini.o
 OUT	= mpdas
 PREFIX ?= /usr/local
 MANPREFIX ?= ${PREFIX}/man/man1
 CONFIG ?= $(PREFIX)/etc
 
-CXXFLAGS	+= `pkg-config --cflags libmpdclient libcurl`
-LIBS		= `pkg-config --libs libmpdclient libcurl`
+CXXFLAGS	+= `$(PKG_CONFIG) --cflags libmpdclient libcurl`
+LIBS		= `$(PKG_CONFIG) --libs libmpdclient libcurl`
 
 CXXFLAGS	+= -DCONFDIR="\"$(CONFIG)\"" -DVERSION="\"$(VERSION)\""

Bug#957224: fped: diff for NMU version 0.1+201210-1.2

2020-08-29 Thread Sudip Mukherjee

Control: tags 957224 + patch
Control: tags 957224 + pending

Dear maintainer,

I've prepared an NMU for fped (versioned as 0.1+201210-1.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should cancel it.

--
Regards
Sudip

diff -Nru fped-0.1+201210/debian/changelog fped-0.1+201210/debian/changelog
--- fped-0.1+201210/debian/changelog2017-04-04 17:17:39.0 +0100
+++ fped-0.1+201210/debian/changelog2020-08-29 21:32:55.0 +0100
@@ -1,3 +1,10 @@
+fped (0.1+201210-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix ftbfs with GCC-10. (Closes: #957224)
+
+ -- Sudip Mukherjee   Sat, 29 Aug 2020 21:32:55 
+0100
+
 fped (0.1+201210-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru fped-0.1+201210/debian/patches/gcc-10.patch 
fped-0.1+201210/debian/patches/gcc-10.patch
--- fped-0.1+201210/debian/patches/gcc-10.patch 1970-01-01 01:00:00.0 
+0100
+++ fped-0.1+201210/debian/patches/gcc-10.patch 2020-08-29 21:27:13.0 
+0100
@@ -0,0 +1,20 @@
+Description: Fix ftbfs with GCC-10
+
+Author: Sudip Mukherjee 
+Bug-Debian: https://bugs.debian.org/957224
+Forwarded: no
+
+---
+
+--- fped-0.1+201210.orig/postscript.h
 fped-0.1+201210/postscript.h
+@@ -26,7 +26,8 @@ struct postscript_params {
+ int label_vecs;
+ int show_meas;
+   int show_key;
+-} postscript_params;
++};
++extern struct postscript_params postscript_params;
+ 
+ 
+ int postscript(FILE *file, const char *one);
diff -Nru fped-0.1+201210/debian/patches/series 
fped-0.1+201210/debian/patches/series
--- fped-0.1+201210/debian/patches/series   1970-01-01 01:00:00.0 
+0100
+++ fped-0.1+201210/debian/patches/series   2020-08-29 21:26:18.0 
+0100
@@ -0,0 +1 @@
+gcc-10.patch

Bug#969242: ITP: golang-github-willf-bloom -- Go package implementing Bloom filters

2020-08-29 Thread Alexandre Viau

Package: wnpp
Severity: wishlist
Owner: Alexandre Viau 

* Package name: golang-github-willf-bloom
  Version : 2.0.3-1
  Upstream Author : Will Fitzgerald
* URL : https://github.com/willf/bloom
* License : BSD-2-clause
  Programming Lang: Go
  Description : Go package implementing Bloom filters

 Bloom filters Master Build Status
 (https://travis-ci.org/willf/bloom?branch=master) Coverage Status
 (https://coveralls.io/github/willf/bloom?branch=master) Go Report
 Card (https://goreportcard.com/report/github.com/willf/bloom) GoDoc
 (http://godoc.org/github.com/willf/bloom)
 .
 A Bloom filter is a representation of a set of n items, where the main
 requirement is to make membership queries; i.e., whether an item is a
 member of a set.
 .

This is required for Syncthing.



signature.asc
Description: OpenPGP digital signature

Bug#969241: RFS: hydrapaper/1.12 [ITP]] -- sets desktop wallpaper on different monitors

2020-08-29 Thread Francisco M Neto

Package: hydrapaper
Version: 1.12-1
Severity: normal

Dear mentors,

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

 * Package name: hydrapaper
   Version : 1.12-1
   Upstream Author : Gabriele Musco 
 * URL : https://gitlab.com/gabmus/HydraPaper
 * License : GPL-3+
 * Vcs : https://salsa.debian.org/fmneto-guest/hydrapaper
   Section : graphics

It builds those binary packages:

  hydrapaper - Utility that sets background independently for each monitor

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

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

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

  dget -x
https://mentors.debian.net/debian/pool/main/h/hydrapaper/hydrapaper_1.12-1.dsc

Changes since the last upload:

hydrapaper (1.12-1) unstable; urgency=medium

  * Initial release (Closes: #969189)

 -- Francisco M Neto   Sat, 29 Aug 2020 12:51:53 +


Regards,
--
  Francisco M Neto



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

Kernel: Linux 5.7.0-7.1-liquorix-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.utf8), LANGUAGE=en_US.utf8
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages hydrapaper depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.36.0-1
ii  gir1.2-handy-1   0.90.0-1
ii  libhandy-1-0 0.90.0-1
ii  python3  3.8.2-3
ii  python3-gi   3.36.0-4

hydrapaper recommends no packages.

hydrapaper suggests no packages.

-- no debconf information

Bug#969240: playonlinux: please switch away from netcat

Source: playonlinux
Version: 4.3.4-2

Dear Maintainer,

playonlinux Depends on netcat. This is a transitional package on
netcat-openbsd, and the transitional package should go away sooner
than later, preferably in bullseye.

Please switch to netcat-openbsd, or ncat, or similar.

Thanks,
Chris

Bug#969239: debian-edu-config: please switch away from netcat

Source: debian-edu-config
Version: 2.11.29

Dear Maintainer,

debian-edu-config Depends on netcat. This is a transitional package
on netcat-openbsd, and the transitional package should go away
sooner than later, preferably in bullseye.

Please switch to netcat-openbsd, or ncat, or similar.

Thanks,
Chris

Bug#969237: ruby-moneta: please switch away from netcat

Source: ruby-moneta
Version: 1.0.0-6

Dear Maintainer,

ruby-moneta Build-Depends on netcat. This is a transitional package
on netcat-openbsd, and the transitional package should go away
sooner than later, preferably in bullseye.

Please switch to netcat-openbsd, or ncat, or similar.

Thanks,
Chris

Bug#969238: ifupdown-extra: please switch away from netcat

Source: ifupdown-extra
Version: 0.29

Dear Maintainer,

ifupdown-extra Depends on netcat. This is a transitional package on
netcat-openbsd, and the transitional package should go away sooner
than later, preferably in bullseye.

Please switch to netcat-openbsd, or ncat, or similar.

Thanks,
Chris

Bug#969236: libmonitoring-livestatus-perl: please switch away from netcat

Source: libmonitoring-livestatus-perl
Version: 0.80-1

Dear Maintainers,

libmonitoring-livestatus-perl Build-Depends on netcat. This is a
transitional package on netcat-openbsd, and the transitional package
should go away sooner than later, preferably in bullseye.

Please switch to netcat-openbsd, or ncat, or similar.

Thanks,
Chris

Bug#947182: libjpeg-turbo-progs: jpegexiforient fails if APP1 doesn't occur immediately after JFIF header

2020-08-29 Thread Akkana Peck

I know this bug was closed as wontfix, but it should be noted
that this means that exifautotran can no longer be used on
images that were resized with ImageMagick, GraphicsMagick, or PIL
(Python Imaging Library): they all produce files that exifautotrans
silently ignores, breaking scripts that have worked for many years.

Is there any scriptable or command-line option that resizes JPEGs
in a way that exifautotran will accept? Or an alternate way to
rotate these images losslessly?

Bug#966671: coturn: unlimited number of /var/log/turn_*.log are created

2020-08-29 Thread Salvatore Bonaccorso

Hi

Not the maintainer here, but given coturn is going to be removed from
testing otherwise I quickly looked at this. In default install this
does not seem to be a problem, turnserver uses the syslog option and
logfile settings are commented out.

So while there is probably some room of improvement (e.g. introducing
a logrotate file, when logfile, vebose and single-log are enabled) the
severity of RC might not be warranted.

Regards,
Salvatore

Bug#969235: sane-airscan: Please consider ipp-usb as a recommended package

2020-08-29 Thread Brian Potkin

Package: sane-airscan
Version: 0.99.15-1
Severity: wishlist


ipp-usb is recommended by cups-daemon, so a user with a default CUPS
installation will have it on the system. Scanning from an MFD device
should easily be possible when sane-escl (in libsane1) is also on the
system. A user should therefore have effortless use of driverless
printing and scanning.

It is possible that a user also installs sane-airscan. For an MFD, this
would give an alternative driverless scanning backend. This could be
beneficial and, in fact, is recommended on the wiki. All ok up to here.

Suppose CUPS is not installed. Installing sane-airscan does not get a
user easy access to a USB connected device unless ipp-usb is on the
system. I would suggest a recommended ipp-scan to sane-airscan would
enhance a user's experience.

Regards,

Brian.

Bug#969233: prometheus-homeplug-exporter: [INTL:de] initial German debconf translation

2020-08-29 Thread Helge Kreutzmann

Package: prometheus-homeplug-exporter
Version: 0.3.0-1
Severity: wishlist
Tags: patch l10n

Please find the initial German debconf translation for 
prometheus-homeplug-exporter
attached.

Please place this file in debian/po/ as de.po for your next upload.

If you update your template, please use 
'msgfmt --statistics '
to check the po-files for fuzzy or untranslated strings.

If there are such strings, please contact me so I can update the 
German translation.

Greetings
Helge
# SOME DESCRIPTIVE TITLE.
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the 
prometheus-homeplug-exporter package.
# Helge Kreutzmann , 2020.
#
msgid ""
msgstr ""
"Project-Id-Version: prometheus-homeplug-exporter 0.3.0-1\n"
"Report-Msgid-Bugs-To: prometheus-homeplug-expor...@packages.debian.org\n"
"POT-Creation-Date: 2020-05-16 20:01+\n"
"PO-Revision-Date: 2020-08-29 20:32+0200\n"
"Last-Translator: Helge Kreutzmann \n"
"Language-Team: German \n"
"Language: de\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Type: boolean
#. Description
#: ../templates:1001
msgid "Enable additional network privileges for PLC communication?"
msgstr "Zusätzliche Netzwerkprivilegien für PLC-Kommunikation aktivieren?"

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"prometheus-homeplug-exporter requires CAP_NET_RAW capabilities to be able to "
"send out raw Ethernet packets to the HomePlug/PLC devices."
msgstr ""
"Prometheus-homeplug-exporter benötigt die Capability CAP_NET_RAW, um rohe "
"Ethernet-Pakete an die HomePlug/PLC-Geräte zu senden."

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"prometheus-homeplug-exporter will not work at all unless this option is "
"enabled, or it runs as root."
msgstr ""
"Prometheus-homeplug-exporter wird nur dann funktionieren, wenn diese "
"Option aktiviert ist oder es unter root ausgeführt wird."

Bug#969234: knot-resolver: [INTL:de] initial German debconf translation

2020-08-29 Thread Helge Kreutzmann

Package: knot-resolver
Version: 5.1.2-3
Severity: wishlist
Tags: patch l10n

Please find the initial German debconf translation for knot-resolver
attached.

Please place this file in debian/po/ as de.po for your next upload.

If you update your template, please use 
'msgfmt --statistics '
to check the po-files for fuzzy or untranslated strings.

If there are such strings, please contact me so I can update the 
German translation.

Greetings
Helge
# SOME DESCRIPTIVE TITLE.
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the PACKAGE package.
# Helge Kreutzmann , 2020.
#
msgid ""
msgstr ""
"Project-Id-Version: knot-resolver 5.1.2-3\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-08-21 16:30+\n"
"PO-Revision-Date: 2020-08-29 20:33+0200\n"
"Last-Translator: Helge Kreutzmann \n"
"Language-Team: German \n"
"Language: de\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Type: note
#. Description
#: ../knot-resolver.templates:1001
msgid "Upgrading from Knot Resolver < 5.x"
msgstr "Upgrade von Knot Resolver < 5.x"

#. Type: note
#. Description
#: ../knot-resolver.templates:1001
msgid "Knot Resolver configuration file requires manual upgrade."
msgstr "Konfigurationsdatei von Knot Resolver benötigt manuelles Upgrade"

# FIXME: Up to → Before?
#. Type: note
#. Description
#: ../knot-resolver.templates:1001
msgid ""
"Up to Knot Resolver 4.x, network interface bindings and service start were "
"done by default via systemd sockets. These systemd sockets are no longer "
"supported, and upgrading from a 3.x version (as in Debian Buster) requires "
"manual action to (re)enable the service."
msgstr ""
"Bis Knot Resolver 4.x erfolgte die Anbindung der Netzwerkschnittstellen und "
"das Starten des Dienstes standardmäßig über Systemd-Sockets. Diese Systemd-"
"Sockets werden nicht mehr unterstützt und ein Upgrade von einer 3.x-Version "
"(wie in Debian Buster) benötigt einen manuellen Eingriff, um den Dienst "
"(wieder) zu aktivieren."

#. Type: note
#. Description
#: ../knot-resolver.templates:1001
msgid ""
"Please refer to kresd.systemd(7) and to the /usr/share/doc/knot-resolver/"
"upgrading.html file (from knot-resolver-doc). An online version of the "
"latter is available at https://knot-resolver.readthedocs.io/en/stable/;
"upgrading.html#x-to-5-x"
msgstr ""
"Bitte lesen Sie kresd.systemd(7) und die Datei /usr/share/doc/knot-resolver/"
"upgrading.html (aus knot-resolver-doc). Eine Online-Version Letzterer ist "
"unter https://knot-resolver.readthedocs.io/en/stable/upgrading.html#x-to-5-x "
"verfügbar."

#. Type: note
#. Description
#: ../knot-resolver.templates:1001
msgid ""
"For convenience, a suggested networking configuration can be found in the "
"file /var/lib/knot-resolver/.upgrade-4-to-5/kresd.conf.net"
msgstr ""
"Der Einfachheit halber kann eine vorgeschlagene Netzwerkkonfiguration in "
"der Datei /var/lib/knot-resolver/.upgrade-4-to-5/kresd.conf.net gefunden "
"werden."

Bug#969232: AttributeError: 'GTlsClientConnectionGnutls' object has no attribute 'set_advertised_protocols'

2020-08-29 Thread Johannes 'josch' Schauer

Package: python3-nbxmpp
Version: 1.0.1-1
Severity: normal

Hi,

when starting gajim I got the following traceback:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nbxmpp/tcp.py", line 140, in 
_on_connect_finished
self._on_connected()
  File "/usr/lib/python3/dist-packages/nbxmpp/tcp.py", line 143, in 
_on_connected
self.notify('connected')
  File "/usr/lib/python3/dist-packages/nbxmpp/util.py", line 491, in notify
func(self, signal_name, *args, **kwargs)
  File "/usr/lib/python3/dist-packages/nbxmpp/client.py", line 424, in 
_on_connected
self.set_state(StreamState.CONNECTED)
  File "/usr/lib/python3/dist-packages/nbxmpp/client.py", line 239, in set_state
self._xmpp_state_machine()
  File "/usr/lib/python3/dist-packages/nbxmpp/client.py", line 576, in 
_xmpp_state_machine
self._con.start_tls_negotiation()
  File "/usr/lib/python3/dist-packages/nbxmpp/tcp.py", line 175, in 
start_tls_negotiation
tls_client.set_advertised_protocols(['xmpp-client'])
AttributeError: 'GTlsClientConnectionGnutls' object has no attribute 
'set_advertised_protocols'

The problem got fixed by upgrading gir1.2-glib-2.0 on my system from
1.58.3-2 to 1.64.1-1. So somewhere a version constraint is missing.

Thanks!

cheers, josch

Bug#969231: modem-manager-gui: Missing icon in taskbar

2020-08-29 Thread Hans

On Sat, 29 Aug 2020 19:47:34 +0200 "Hans-J. Ullrich"  
wrote:

Sorry, set the wrong level at creation. Please set this level from "normal" to 
"minor".


Thanks!

Best

Hans

> Package: modem-manager-gui
> Version: 0.0.20-1
> Severity: minor
> 
> Dear Maintainer,
> 
> after my last upgrade in debian/testing (32-bit and 64-bit) the little icon 
in the taskbar has disappeared, which shows, that modem-manger-gui is running 
in background. This happens in LXDE and Plasma5 as well. Other Windowmanager 
might be touched, too.
> 
> It is not a big thing, but I think it is worthy you should know it. Maybe 
you will fix this for the next release.
> 
> Happy hacking!
> 
> Hans
> 
> 
> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers testing
>   APT policy: (500, 'testing'), (500, 'stable')
> Architecture: i386 (i686)
> 
> Kernel: Linux 5.7.0-2-686-pae (SMP w/2 CPU threads)
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not 
set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages modem-manager-gui depends on:
> ii  libayatana-appindicator3-1  0.5.5-2
> ii  libc6   2.31-3
> ii  libcairo2   1.16.0-4
> ii  libgdbm61.18.1-5.1
> ii  libgdk-pixbuf2.0-0  2.40.0+dfsg-5
> ii  libglib2.0-02.64.4-1
> ii  libgtk-3-0  3.24.22-1
> ii  libgtkspell3-3-03.0.10-1
> ii  mobile-broadband-provider-info  20190618-3
> ii  modemmanager1.14.2-0.1
> ii  policykit-1 0.105-29
> ii  ppp 2.4.7-2+4.1+deb10u1+b1
> 
> Versions of packages modem-manager-gui recommends:
> ii  modem-manager-gui-help  0.0.20-1
> ii  yelp3.36.0-1
> 
> Versions of packages modem-manager-gui suggests:
> ii  evolution-data-server  3.36.4-1
> ii  libindicate5   0.6.92-6
> ii  libnotify4 0.7.9-1
> 
> -- no debconf information
> 
> 
=<159872325466.29191.1268651738408774500.reportbug@localhost>

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

Bug#969231: modem-manager-gui: Missing icon in taskbar

2020-08-29 Thread Hans-J. Ullrich

Package: modem-manager-gui
Version: 0.0.20-1
Severity: minor

Dear Maintainer,

after my last upgrade in debian/testing (32-bit and 64-bit) the little icon in 
the taskbar has disappeared, which shows, that modem-manger-gui is running in 
background. This happens in LXDE and Plasma5 as well. Other Windowmanager might 
be touched, too.

It is not a big thing, but I think it is worthy you should know it. Maybe you 
will fix this for the next release.

Happy hacking!

Hans


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

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

Versions of packages modem-manager-gui depends on:
ii  libayatana-appindicator3-1  0.5.5-2
ii  libc6   2.31-3
ii  libcairo2   1.16.0-4
ii  libgdbm61.18.1-5.1
ii  libgdk-pixbuf2.0-0  2.40.0+dfsg-5
ii  libglib2.0-02.64.4-1
ii  libgtk-3-0  3.24.22-1
ii  libgtkspell3-3-03.0.10-1
ii  mobile-broadband-provider-info  20190618-3
ii  modemmanager1.14.2-0.1
ii  policykit-1 0.105-29
ii  ppp 2.4.7-2+4.1+deb10u1+b1

Versions of packages modem-manager-gui recommends:
ii  modem-manager-gui-help  0.0.20-1
ii  yelp3.36.0-1

Versions of packages modem-manager-gui suggests:
ii  evolution-data-server  3.36.4-1
ii  libindicate5   0.6.92-6
ii  libnotify4 0.7.9-1

-- no debconf information

Bug#969230: freecad crashes on wayland when opening FCStd files

2020-08-29 Thread Pedro Ângelo

Package: freecad
Version: 0.18.4+dfsg2-5
Severity: important
Tags: upstream

Dear Maintainer,

   * What led up to the situation?

On Debian testing, under the Sway window manager (which is Wayland-based), it
is not possible to read or write FCSstd files on Freecad. To reproduce:

 * use a wayland-based window manager
 * open a shell and execute `QT_QPA_PLATFORM=wayland freecad`
 * try to load an FCSstd file

this issue is known upstream:

https://forum.freecadweb.org/viewtopic.php?t=33359

the proper fix requires a patch recently merged to coin3d:

https://github.com/coin3d/coin/pull/404

I flagged this as important because it makes the package unusable on native
Wayland setups. A workaround is to set `QT_QPA_PLATFORM=xcb` before starting
Freecad.



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

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

Versions of packages freecad depends on:
ii  freecad-python3  0.18.4+dfsg2-5

Versions of packages freecad recommends:
ii  calculix-ccx  2.11-1+b3
ii  graphviz  2.42.2-4

Versions of packages freecad suggests:
pn  povray  

-- no debconf information

Bug#969198: msmtp-mta package should use update-alternatives for symlinking to msmtp

2020-08-29 Thread Heikki Orsila

On Sat, Aug 29, 2020 at 10:29:16AM -0400, Simon Deziel wrote:
> Hi Heikki,
> 
> On 2020-08-29 4:38 a.m., Heikki Orsila wrote:
> > msmtp-mta creates a symlink from "/usr/sbin/sendmail" to "../bin/msmtp".
> > It does not use update-alternatives which makes it difficult to install
> > msmtp-mta and another MTA on the same system.
> 
> In this case, you might want to use the msmtp package instead of
> msmtp-mta. The former doesn't creates the sendmail symlink.

In my case that works because I'm not using msmtpd. In general,
using update-alternatives would be consistent with exim4-* and other MTAs.
Feel free to close the bug.

-- 
Heikki Orsila
heikki.ors...@zakalwe.fi
http://www.iki.fi/shd

Bug#969229: new upstream version 4.0.4

2020-08-29 Thread Harald Dunkel


Package: lxc
Version: 1:4.0.2-1

There is a new version 4.0.4. Can I help to upgrade the LXC
package? This could help to get rid of #966998

2 weeks ago I have upgraded LXC on my Debian 10 systems from
4.0.2 to 4.0.4. Nothing unusual so far. The only issue was to
upgrade the symbol list.


Regards
Harri

Bug#969228: glaurung: Segmentation fault caused by out of bounds access

2020-08-29 Thread Asher Gordon

Package: glaurung
Version: 2.2-3
Severity: grave
Tags: patch
X-Debbugs-Cc: Asher Gordon 

Dear Maintainer,

Glaurung segfaults when the 'go' command is used, making it
unusable. For example:

$ glaurung
Glaurung 2.2.  Copyright (C) 2004-2008 Tord Romstad.
go
Segmentation fault

This is because of an out of bounds access, fixed by the following
patch:
From 62017d29d816d07513805500d498d8779343e074 Mon Sep 17 00:00:00 2001
From: Asher Gordon 
Date: Sat, 29 Aug 2020 12:53:56 -0400
Subject: [PATCH 1/3] Fix buffer overrun, causing a segfault

---
 src/evaluate.cpp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/evaluate.cpp b/src/evaluate.cpp
index 72032f0..ac303fa 100644
--- a/src/evaluate.cpp
+++ b/src/evaluate.cpp
@@ -1243,7 +1243,7 @@ namespace {
 SafetyTable[i] = Value((int)(100 * a * (i - b)));
 }
 
-for(i = 0; i < 100; i++)
+for(i = 0; i < 99; i++)
   if(SafetyTable[i+1] - SafetyTable[i] > maxSlope) {
 for(j = i + 1; j < 100; j++)
   SafetyTable[j] = SafetyTable[j-1] + Value(maxSlope);
-- 
2.28.0

I also attempted to send this patch upstream, but I don't know Tord's
current email address (it's not t...@glaurungchess.com; I tried). So I
sent it to Matthew Purland, since he had made the last commit on
https://github.com/phenri/glaurung.

So hopefully, he will be able to apply it upstream, but until then,
please apply this patch in Debian.

Thanks,
Asher

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

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

Versions of packages glaurung depends on:
ii  libc6   2.31-3
ii  libstdc++6  10.1.0-6

Versions of packages glaurung recommends:
ii  polyglot  2.0.4-2+b1
ii  xboard4.9.1-2

glaurung suggests no packages.

-- no debconf information

-- 
One picture is worth 128K words.
   
I prefer to send and receive mail encrypted. Please send me your
public key, and if you do not have my public key, please let me
know. Thanks.

GPG fingerprint: 38F3 975C D173 4037 B397  8095 D4C9 C4FC 5460 8E68


signature.asc
Description: PGP signature

Bug#963574: RFS: hcloud-python/1.8.0-1 [ITP] -- official client library for Hetzner Cloud

2020-08-29 Thread Leo Antunes

On Thu, 27 Aug 2020 16:28:32 +0200 Tobias Frost  wrote:
> thanks for the package, I've just uploaded it to the NEW queue…

\o/  thanks!

> One remark: Do you think it would be sensible to also package the 
> documentation?

Good idea. Hadn't thought about it. I'll check it out.

> Another one: It seems that the CI configuration on salsa is broken; please 
> check
> if the right yaml file is selected (I've forked the project to check it and on
> my site it looks ok: https://salsa.debian.org/tobi/hcloud-python/-/pipelines)

Ah, good catch! Thanks.


Cheers,
Leo

Bug#969227: FTBFS with new runc 1.0.0~rc92 and libcap2 2.43

2020-08-29 Thread Shengjing Zhu

Package: docker.io
Version: 19.03.12+dfsg1-3
Severity: serious

Please see the patches attached.

BTW, is there any instruction to work with the docker.io git repo?
It seems `gbp buildpackage` or `gbp pq` are hard to use with it.
Description: Fix build with runc 1.0.0~rc92
Author: Shengjing Zhu 

Forwarded: not-needed
Last-Update: 2020-08-29

--- docker.io-19.03.12+dfsg1.orig/containerd/vendor/github.com/containerd/cri/pkg/containerd/opts/spec.go
+++ docker.io-19.03.12+dfsg1/containerd/vendor/github.com/containerd/cri/pkg/containerd/opts/spec.go
@@ -421,7 +421,7 @@ func WithDevices(osi osinterface.OS, con
 Type:   string(dev.Type),
 Major:  ,
 Minor:  ,
-Access: dev.Permissions,
+Access: string(dev.Permissions),
 			})
 		}
 		return nil
--- docker.io-19.03.12+dfsg1.orig/engine/daemon/stats/collector_unix.go
+++ docker.io-19.03.12+dfsg1/engine/daemon/stats/collector_unix.go
@@ -8,14 +8,14 @@ import (
 	"strconv"
 	"strings"
 
-	"github.com/opencontainers/runc/libcontainer/system"
 	"golang.org/x/sys/unix"
 )
 
 // platformNewStatsCollector performs platform specific initialisation of the
 // Collector structure.
 func platformNewStatsCollector(s *Collector) {
-	s.clockTicksPerSecond = uint64(system.GetClockTicks())
+	// modified from https://github.com/moby/moby/pull/41186
+	s.clockTicksPerSecond = 100
 }
 
 const nanoSecondsPerSecond = 1e9
--- docker.io-19.03.12+dfsg1.orig/engine/oci/devices_linux.go
+++ docker.io-19.03.12+dfsg1/engine/oci/devices_linux.go
@@ -31,7 +31,7 @@ func deviceCgroup(d *configs.Device) spe
 		Type:   t,
 		Major:  ,
 		Minor:  ,
-		Access: d.Permissions,
+		Access: string(d.Permissions),
 	}
 }
 
--- docker.io-19.03.12+dfsg1.orig/containerd/sys/proc.go
+++ /dev/null
@@ -1,80 +0,0 @@
-// +build linux
-
-/*
-   Copyright The containerd Authors.
-
-   Licensed under the Apache License, Version 2.0 (the "License");
-   you may not use this file except in compliance with the License.
-   You may obtain a copy of the License at
-
-   http://www.apache.org/licenses/LICENSE-2.0
-
-   Unless required by applicable law or agreed to in writing, software
-   distributed under the License is distributed on an "AS IS" BASIS,
-   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-   See the License for the specific language governing permissions and
-   limitations under the License.
-*/
-
-package sys
-
-import (
-	"bufio"
-	"fmt"
-	"os"
-	"strconv"
-	"strings"
-
-	"github.com/opencontainers/runc/libcontainer/system"
-)
-
-const nanoSecondsPerSecond = 1e9
-
-var clockTicksPerSecond = uint64(system.GetClockTicks())
-
-// GetSystemCPUUsage returns the host system's cpu usage in
-// nanoseconds. An error is returned if the format of the underlying
-// file does not match.
-//
-// Uses /proc/stat defined by POSIX. Looks for the cpu
-// statistics line and then sums up the first seven fields
-// provided. See `man 5 proc` for details on specific field
-// information.
-func GetSystemCPUUsage() (uint64, error) {
-	var line string
-	f, err := os.Open("/proc/stat")
-	if err != nil {
-		return 0, err
-	}
-	bufReader := bufio.NewReaderSize(nil, 128)
-	defer func() {
-		bufReader.Reset(nil)
-		f.Close()
-	}()
-	bufReader.Reset(f)
-	err = nil
-	for err == nil {
-		line, err = bufReader.ReadString('\n')
-		if err != nil {
-			break
-		}
-		parts := strings.Fields(line)
-		switch parts[0] {
-		case "cpu":
-			if len(parts) < 8 {
-return 0, fmt.Errorf("bad format of cpu stats")
-			}
-			var totalClockTicks uint64
-			for _, i := range parts[1:8] {
-v, err := strconv.ParseUint(i, 10, 64)
-if err != nil {
-	return 0, fmt.Errorf("error parsing cpu stats")
-}
-totalClockTicks += v
-			}
-			return (totalClockTicks * nanoSecondsPerSecond) /
-clockTicksPerSecond, nil
-		}
-	}
-	return 0, fmt.Errorf("bad stats format")
-}
Description: Fix build against libcap2 2.43
Author: Shengjing Zhu 

Bug: https://github.com/moby/moby/issues/41398
Forwarded: no
Last-Update: 2020-08-29

--- docker.io-19.03.12+dfsg1.orig/engine/pkg/archive/archive_unix_test.go
+++ docker.io-19.03.12+dfsg1/engine/pkg/archive/archive_unix_test.go
@@ -264,7 +264,7 @@ func TestTarUntarWithXattr(t *testing.T)
 		}
 		out, err := exec.Command("getcap", filepath.Join(origin, "2")).CombinedOutput()
 		assert.NilError(t, err, string(out))
-		assert.Check(t, is.Contains(string(out), "= cap_block_suspend+ep"), "untar should have kept the 'security.capability' xattr")
+		assert.Check(t, is.Contains(string(out), "cap_block_suspend=ep"), "untar should have kept the 'security.capability' xattr")
 	}
 }

Bug#969177: debmake: cannot create deb for nodejs modeule

2020-08-29 Thread Pirate Praveen




On 2020, ഓഗസ്റ്റ് 29 8:50:53 PM IST, Osamu Aoki  wrote:
>Control: severity -1 important
>
>Hi,
>
>Thanks for the log which helps
>
>It only breaks for javascript/nodejs.  
>
>Javascript/nodejs support is new and needs help.  Besides

>(You shouldn't file a grave RC bug without throurough review against
>policy.)

Well, this was the core functionality of the program that was broken. It did 
not gracefully exit from the error and there was no work around available.

This happened during a tutorials on debmake during a debconf presentation, 
which worked fine when I recorded the tutorial. Finally we used dh-make.

>On Fri, 2020-08-28 at 21:39 +0530, Pirate Praveen wrote:
>> package: debmake
>> version: 4.3.2-1
>> severity: grave
>> 
>> Using pretty-ms node module as example. debmake 4.3.2-1 worked.
>
>I don"t know how people download such nodejs tarball from where.
> Please tell me how you did it.  Please tell me how so I can test.

The homepage/repo is found from npmjs.com for all node modules.

You can use latest release tarball from 
https://github.com/sindresorhus/pretty-ms/releases (given as repo URL at 
npmjs.com).

Or direct URL which you can wget, 
https://github.com/sindresorhus/pretty-ms/archive/v7.0.0.tar.gz

>> (debian-sid)pravi@ilvala2:~/packaging/node-pretty-ms-7.0.0$ debmake
>> I: set parameters
>> I: sanity check of parameters
>> I: pkg="node-pretty-ms", ver="7.0.0", rev="1"
>> I: *** start packaging in "node-pretty-ms-7.0.0". ***
>> I: provide node-pretty-ms_7.0.0.orig.tar.gz for non-native Debian 
>> package
>> I: pwd = "/home/pravi/packaging"
>> I: Use existing "node-pretty-ms_7.0.0.orig.tar.gz" as upstream
>> tarball
>...
>"debian/control", debmake.control.control(para), 
>> tutorial=para["tutorial"]
>>   File "/usr/lib/python3/dist-packages/debmake/control.py", line 60,
>> in 
>> control
>> desc_long_type = debmake.read.read(
>>   File "/usr/lib/python3/dist-packages/debmake/read.py", line 30, in 
>> read
>> with open(file, mode="r", encoding="utf-8") as f:
>> FileNotFoundError: [Errno 2] No such file or directory: 
>> '/usr/share/debmake/extra0desc_long/nodejs'
>
>Hahaha, that's my mistake.  I forgot to add place holder file.

OK, hope to see a fix soon.

Thanks
>
>Osamu

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Bug#969184: Re: Bug#969184: Upgrade fails when interface name has changed

2020-08-29 Thread martin . sturc


Hello all,

I came across a similar issue today during 'apt-get upgrade' on my 
Debian unstable amd64 machine. The system was installed back in 2014 as 
Debian Wheezy and through the years (dist-)upgraded until the current 
unstable. The minissdpd package was probably installed as part of the 
system installation at the beginning as it was completely unknown to me 
(and I have never dealt with its configuration). DPKG failed with the 
following message:

--
Nastavuje se balík minissdpd (1.5.20190824-1) …
Job for minissdpd.service failed because the control process exited with 
error code.
See "systemctl status minissdpd.service" and "journalctl -xe" for 
details.

invoke-rc.d: initscript minissdpd, action "restart" failed.
● minissdpd.service - keep memory of all UPnP devices that announced 
themselves
 Loaded: loaded (/lib/systemd/system/minissdpd.service; enabled; 
vendor preset: enabled)
 Active: failed (Result: exit-code) since Sat 2020-08-29 16:08:28 
CEST; 23ms ago

   Docs: man:minissdpd(1)
Process: 16207 
ExecCondition=/usr/lib/minissdpd/minissdpd-systemd-wrapper -t 
${MiniSSDPd_INTERFACE_ADDRESS} (code=exited, status=0/SUCCESS)
Process: 16208 
ExecStart=/usr/lib/minissdpd/minissdpd-systemd-wrapper 
${MiniSSDPd_INTERFACE_ADDRESS} $MiniSSDPd_OTHER_OPTIONS (code=exited, 
status=1/FAILURE)


srp 29 16:08:28 P01-MARTIN minissdpd-systemd-wrapper[16208]: Error 
parsing address/mask (or interface name) : eth0
srp 29 16:08:28 P01-MARTIN minissdpd-systemd-wrapper[16208]: can't parse 
"eth0" as a valid address or interface name
srp 29 16:08:28 P01-MARTIN minissdpd-systemd-wrapper[16208]: Usage: 
/usr/sbin/minissdpd [-d] [-6] [-s socket] [-p pidfile] [-t TTL] [-f 
device] -i  [-i ] ...
srp 29 16:08:28 P01-MARTIN minissdpd-systemd-wrapper[16208]:   
 is either an IPv4 address with mask such as
srp 29 16:08:28 P01-MARTIN minissdpd-systemd-wrapper[16208]:   
192.168.1.42/255.255.255.0, or an interface name such as eth0.
srp 29 16:08:28 P01-MARTIN minissdpd-systemd-wrapper[16208]:   By 
default, socket will be open as /var/run/minissdpd.sock
srp 29 16:08:28 P01-MARTIN minissdpd-systemd-wrapper[16208]:   and pid 
written to file /var/run/minissdpd.pid
srp 29 16:08:28 P01-MARTIN systemd[1]: minissdpd.service: Control 
process exited, code=exited, status=1/FAILURE
srp 29 16:08:28 P01-MARTIN systemd[1]: minissdpd.service: Failed with 
result 'exit-code'.
srp 29 16:08:28 P01-MARTIN systemd[1]: Failed to start keep memory of 
all UPnP devices that announced themselves.

dpkg: chyba při zpracovávání balíku minissdpd (--configure):
 installed minissdpd package post-installation script subprocess 
returned error exit status 1

--

After that, I tried changing the '/etc/default/minissdpd' config file to 
reflect my current interface name ('enp0s25'), but after running 
'apt-get upgrade' again, it was rewritten back to 'eth0' (like Dann 
wrote) and the same error was returned.


After finding this bug report, I tried the 'debconf-show minissdpd' 
which reported:

-
  minissdpd/ip6: false
* minissdpd/listen: eth0
* minissdpd/start_daemon: true
* minissdpd/why_I_am_here:
-
I changed it using a short script (as I don't know a better way as of 
now):

-
debconf-set-selections <<- 'END'
minissdpd   minissdpd/listen \
string enp0s25
END
-
And 'debconf-show minissdpd' reported:
-
* minissdpd/start_daemon: true
* minissdpd/listen: enp0s25
  minissdpd/ip6: false
* minissdpd/why_I_am_here:
-
After that, 'apt-get upgrade' finished successfully and also 'enp0s25' 
was written into the '/etc/default/minissdpd' config file (overwriting 
the 'eth0' left there from the attempt mentioned above).


Looking into the script '/var/lib/dpkg/info/minissdpd.config' (as Thomas 
pointed out) with my minimal bash knowledge, it seems to me, that it 
fetches the values from the '/etc/default/minissdpd' config file first 
(https://salsa.debian.org/miniupnp-team/minissdpd/-/blob/debian-sid/debian/minissdpd.config#L24) 
to overwrite them with values from debconf later 
(https://salsa.debian.org/miniupnp-team/minissdpd/-/blob/debian-sid/debian/minissdpd.config#L38).
I don't know, if this is the required behaviour to be able to use 
debconf, but it seems to me as the possible source of the reported 
problem.


Best regards

Martin Šturc

Bug#969226: [pkg-cryptsetup-devel] Bug#969226: cryptsetup-suspend: missing dependency on /bin/openvt (kbd)

2020-08-29 Thread Guilhem Moulin

Control: -1 severity -1 serious

Hi Jochen,

On Sat, 29 Aug 2020 at 18:24:44 +0200, Jochen Sprickerhof wrote:
> Severity: grave
> Justification: renders package unusable
> […r
> /lib/systemd/system/systemd-suspend.service.d/systemd_cryptsetup-suspend.conf
> tries to call /bin/openvt which is in the optional package kbd.

cryptsetup-initramfs has ‘Recommends: kbd’ so while the missing
dependency in cryptsetup-suspend is a policy violation, in practice
it'll work just fine on systems without --no-install-recommends (the
default). :-P

Cheers,
-- 
Guilhem.

signature.asc
Description: PGP signature

Bug#969226: cryptsetup-suspend: missing dependency on /bin/openvt (kbd)

2020-08-29 Thread Jochen Sprickerhof

Package: cryptsetup-suspend
Version: 2:2.3.3-3+exp1
Severity: grave
Justification: renders package unusable

Hi,

/lib/systemd/system/systemd-suspend.service.d/systemd_cryptsetup-suspend.conf
tries to call /bin/openvt which is in the optional package kbd. Please
add a dependency to make sure it's installed.

Thanks for working on this :).

Cheers Jochen

-- Package-specific info:
-- /proc/cmdline
root=LABEL=root rw quiet mitigations=off systemd.unified_cgroup_hierarchy=1 
add_efi_memmap initrd=\EFI\debian\initrd.img

-- /etc/crypttab
# 

-- lsmod
Module  Size  Used by
fuse  139264  3
dm_crypt   49152  1
dm_mod163840  3 dm_crypt
ctr16384  1
ccm20480  3
uvcvideo  114688  0
algif_aead 16384  0
videobuf2_vmalloc  20480  1 uvcvideo
videobuf2_memops   20480  1 videobuf2_vmalloc
videobuf2_v4l2 28672  1 uvcvideo
videobuf2_common   57344  2 videobuf2_v4l2,uvcvideo
cbc16384  0
videodev  266240  3 videobuf2_v4l2,uvcvideo,videobuf2_common
des_generic16384  0
libdes 24576  1 des_generic
ecb16384  0
mc 57344  4 
videodev,videobuf2_v4l2,uvcvideo,videobuf2_common
arc4   16384  0
algif_skcipher 16384  0
cmac   16384  0
sha512_ssse3   45056  0
sha512_generic 16384  1 sha512_ssse3
md416384  0
algif_hash 16384  0
af_alg 32768  3 algif_hash,algif_skcipher,algif_aead
snd_soc_skl_hda_dsp24576  1
snd_soc_hdac_hdmi  40960  1 snd_soc_skl_hda_dsp
snd_soc_dmic   16384  1
snd_hda_codec_hdmi 73728  1
snd_hda_codec_realtek   139264  1
snd_hda_codec_generic94208  1 snd_hda_codec_realtek
snd_sof_pci20480  0
snd_sof_intel_hda_common90112  1 snd_sof_pci
x86_pkg_temp_thermal20480  0
intel_powerclamp   20480  0
snd_sof_intel_hda  20480  1 snd_sof_intel_hda_common
snd_sof_intel_byt  20480  1 snd_sof_pci
coretemp   20480  0
snd_sof_intel_ipc  20480  1 snd_sof_intel_byt
snd_sof   126976  4 
snd_sof_pci,snd_sof_intel_hda_common,snd_sof_intel_byt,snd_sof_intel_ipc
snd_sof_xtensa_dsp 16384  2 snd_sof_intel_hda_common,snd_sof_intel_byt
intel_rapl_msr 20480  0
snd_soc_skl   184320  0
iwlmvm319488  0
kvm_intel 323584  0
kvm   811008  1 kvm_intel
snd_soc_hdac_hda   24576  2 snd_sof_intel_hda_common,snd_soc_skl
snd_hda_ext_core   36864  5 
snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_soc_hdac_hda,snd_soc_skl,snd_sof_intel_hda
snd_soc_sst_ipc20480  1 snd_soc_skl
snd_soc_sst_dsp40960  1 snd_soc_skl
snd_soc_acpi_intel_match45056  3 
snd_sof_pci,snd_sof_intel_hda_common,snd_soc_skl
snd_soc_acpi   16384  4 
snd_soc_acpi_intel_match,snd_sof_intel_hda_common,snd_sof_intel_byt,snd_soc_skl
mac80211  909312  1 iwlmvm
snd_soc_core  278528  7 
snd_sof,snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_soc_hdac_hda,snd_soc_skl,snd_soc_dmic,snd_soc_skl_hda_dsp
irqbypass  16384  1 kvm
snd_compress   32768  1 snd_soc_core
joydev 28672  0
rapl   16384  0
i915 2592768  4
intel_cstate   16384  0
binfmt_misc24576  1
libarc416384  2 mac80211,arc4
snd_hda_intel  57344  0
snd_intel_dspcfg   24576  4 
snd_hda_intel,snd_sof_pci,snd_sof_intel_hda_common,snd_soc_skl
snd_hda_codec 163840  6 
snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek,snd_soc_hdac_hda,snd_soc_skl_hda_dsp
iwlwifi   274432  1 iwlmvm
intel_uncore  163840  0
snd_hda_core  106496  12 
snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_ext_core,snd_hda_codec,snd_hda_codec_realtek,snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_soc_hdac_hda,snd_soc_skl,snd_sof_intel_hda,snd_soc_skl_hda_dsp
nls_ascii  16384  1
nls_cp437  20480  1
pcspkr 16384  0
efi_pstore 16384  0
snd_hwdep  16384  1 snd_hda_codec
evdev  28672  16
snd_pcm   131072  10 
snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_sof,snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_compress,snd_soc_core,snd_soc_skl,snd_hda_core
drm_kms_helper249856  1 i915
vfat   20480  1
serio_raw  20480  0
iTCO_wdt   16384  0
mei_me 45056  0
processor_thermal_device20480  0
cfg80211  872448  3 iwlmvm,iwlwifi,mac80211
fat86016  1 vfat
iTCO_vendor_support16384  1 iTCO_wdt
efivars20480  1 efi_pstore
wmi_bmof   16384  0
intel_rapl_common  32768  2 intel_rapl_msr,processor_thermal_device
intel_wmi_thunderbolt

Bug#969152: teckit FTBFS on most architectures: symbol differences

2020-08-29 Thread Hilmar Preuße

Am 28.08.2020 um 10:42 teilte Adrian Bunk mit:

Hi all,

> ...
> dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
> diff output below
> dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
> file: see diff output below
> dpkg-gensymbols: warning: debian/libteckit0/DEBIAN/symbols doesn't match 
> completely debian/libteckit0.symbols
> ...
> dh_makeshlibs: error: failing due to earlier errors
> make: *** [debian/rules:7: binary-arch] Error 25
> 
I changed the symbols file according to [1]. Now the build is fine on
i386, but fails on amd64. It was not that easy, sorry!

Hilmar

[1] https://www.eyrie.org/~eagle/journal/2012-01/008.html
-- 
sigfault
#206401 http://counter.li.org



signature.asc
Description: OpenPGP digital signature

Bug#969174: Additional info

2020-08-29 Thread Raúl Sánchez Siles

  Hi all:

  I also bump into this. I confirm that I can reenable the webext-* installed 
extensions going to the preferences, disabling the extension and enabling 
the extension again. As Christoph already stated that works up to the next 
firefox restart.

  I've also found that the extensions I installed from within firefox are 
working correctly as expected, unlike those installed from apt.

  I'm on Debian sid. Firefox is 80.0-1.

  Best regards,
-- 
Rául Sánchez Siles

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

Bug#969224: cdimage.debian.org: Error installing Debian 10.5 from flash stick with Extlinux

2020-08-29 Thread Lou Poppler

Please see the installation instructions:
https://www.debian.org/releases/stable/installmanual

It is not correct to pre-format your install media, and pre-copy other files
onto it, before copying the installation .iso

The correct instructions for writing a USB (or other) installation medium are in
section 4.3 of that installmanual.

In particular, the destination target of your dd command should be something
similar to /dev/sdb_NOT_  something like   /dev/sdb1
--- and don't forget to `sync` after the dd.

If you still have trouble, seek help at the #debian IRC channel at oftc.net.

On Sat, 2020-08-29 at 17:10 +0300, Сергей Фёдоров wrote:
> Package: cdimage.debian.org
> Severity: critical
> Justification: breaks the whole system
> 
> 
> 
> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 5.7.0-3-amd64 (SMP w/8 CPU threads)
> Locale: LANG=ru_RU.utf8, LC_CTYPE=ru_RU.utf8 (charmap=UTF-8), LANGUAGE not set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Created a USB flach stick using the" gparted " MBR-partition table.
> GPT-partition table failed to get a working version of the Debian 
> installation.
> Created an Ext4-partition and its label. Set the partition "boot" attribute.
> 
> Created a bootable flash drive:
> 
> # dd conv=notrunc bs=440 count=1 if=/usr/lib/EXTLINUX/mbr. bin of=/dev/xxx
> where xxx is the name of the u-VA, for example, sdf.
> # extlinux --install "folder path" (for example " /media/u1/UP1/"), where" 
> UP1 " is partition name
> 
> For Debian 10.4 copied from a folder:
> 
> http://ftp.nl.debian.org/debian/dists/Debian10.4/main/installer-amd64/current/images/hd-media/
> or from (for GTK)
> http://ftp.nl.debian.org/debian/dists/Debian10.4/main/installer-amd64/current/images/hd-media/gtk/
> 
> vmlinuz
> initrd.gz
> 
> and copied "debian-10.4.0-amd64-DVD-1.iso"
> 
> or
> 
> For Debian 10.5 copied from the folder:
> 
> http://ftp.nl.debian.org/debian/dists/Debian10.5/main/installer-amd64/current/images/hd-media/
> or from (for GTK)
> http://ftp.nl.debian.org/debian/dists/Debian10.5/main/installer-amd64/current/images/hd-media/gtk/
> 
> vmlinuz
> initrd.gz
> 
> and copied "debian-10.5.0-amd64-DVD-1.iso»
> 
> In both cases, when installing Debian from a flash drive, I received the 
> message:
> 
> Load installer components from an ISO installer.
> 
> No modules were found. This pfobably is due to a mismatch between the kernel
> by this version of the installer and the kernel version available in the
> archieve.
> 
> and the installation had to be stopped.
> 
> For Debian 10.3 copied from the folder:
> 
> http://ftp.nl.debian.org/debian/dists/Debian10.3/main/installer-amd64/current/images/hd-media/
> or from (for GTK)
> http://ftp.nl.debian.org/debian/dists/Debian10.3/main/installer-amd64/current/images/hd-media/gtk/
> 
> vmlinuz
> initrd.gz
> 
> and copied "debian-10.3.0-amd64-DVD-1.iso"
> 
> and everything was established without problems.
> 
> Copy Debian 10.3, 10.4, and 10.5 to a USB stick in the device root, download
> with it, the installation of Debian passes without problems.
> 
> For example:
> 
> dd if="./debian-10.5.0-amd64-DVD-1.iso" of=/dev/xxx bs=1M status=progress
> where xxx is the name of the u-VA, for example, sdf.
> 
> Installing Debian 10.3, 10.4, and 10.5 from a DVD does not cause these 
> problems.
>

Bug#959174: Summing up our IRC discussion on #959828

2020-08-29 Thread Gunnar Wolf

On 2020-08-16, the Technical Committee was informally (by the means of
a single IRC message) notified that we should probably look into bug
#959828. We thus discussed it in our monthly meeting, that was held
three days later.

During our last meeting, we all thought sharing the points we all
agreed upon in the meeting would be helpful at this point in the
disagreement; if it's not, that's fine, but hopefully it can help make
some progress. What follows is not a formal Technical Committee ruling
or opinion; full meeting logs can be followed at:


http://meetbot.debian.net/debian-ctte/2020/debian-ctte.2020-08-19-17.59.log.html#l-186

First of all, there was consensus amongst all tech-ctte members that
the 'systemctl' package (to which we will, for clarity, refer using
its full project name, 'docker-systemctl-replacement') declaring
"Provides: systemd" is not correct, as the interfaces that define
systemd clearly far exceed docker-systemctl-replacement.

Several amongst us also showed concern that the package name
"systemctl" might be misleading for some users; the package could
probably be renamed. For reference, upstream's project name is
"docker-systemctl-replacement".

Some ideas have been floated, although they might not be complete nor
fully discussed, regarding how systemd's functionality could be
expressed not only monolithically, but referring to its main
interfaces. An example can be found at:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959828#129

The use case for docker-systemctl-replacement is quite legitimate and
common; containers will often not need to support a full-fledged init
system. And given that php-fpm, the package in quesiton, closely fits
the container use case, we feel important to urge the php-fpm
maintainers to work constructively to find a suitable way to describe
the needed dependencies so that php-fpm can be installed in a
containerized system without a full init system.

For fullness of references, the bug report tracking the conflict
between the systemctl and php-fpm packages is #959174.

 - Gunnar Wolf
   Debian Technical Committee member


signature.asc
Description: PGP signature

Bug#969021: RFP: getmail6 -- Mail retriever with support for POP3, IMAP4 and SDPS

2020-08-29 Thread 積丹尼 Dan Jacobson

> "OA" == Osamu Aoki  writes:
OA> Hi,

OA> I am about to request for package removal of current getmail package.
OA> So whoever decide to package this new python3 getmail, please go ahead
OA> without worrying file conflict.

Maybe don't remove it, but just hand it over to Sudip for upgrade.

Bug#969209: reportbug: rejects Unicode in "email" setting

Python's bugtracker says that `email.utils.formataddr` is deprecated and
should not be used: https://bugs.python.org/issue25955#msg257039 and
gives an alternative (the email.headerregistry module with an
appropriate policy).

Ansgar

Bug#969021: RFP: getmail6 -- Mail retriever with support for POP3, IMAP4 and SDPS

Hi,

I am about to request for package removal of current getmail package.
So whoever decide to package this new python3 getmail, please go ahead
without worrying file conflict.

Please note there are some confusing situation over who the actual
upstream maintainer is etc.  So whoever take over this, please
carefully assess upstream situation.

Regards,

Osamu


On Thu, 2020-08-27 at 14:49 +0100, Sudip Mukherjee wrote:
> X-Debbugs-Cc: Osamu Aoki 
> 
> 
> On Wed, Aug 26, 2020 at 04:51:33PM +0800, Dan Jacobson wrote:
> > Package: wnpp
> > Severity: wishlist
> > X-Debbugs-Cc: 968...@bugs.debian.org
> > 
> > * Package name: getmail6
> >   Version : 6.4
> >   Upstream Author : roland.punta...@gmail.com
> > * URL : https://github.com/getmail6
> > * License : GNU GPL version 2
> >   Programming Lang: Python
> >   Description : Mail retriever with support for POP3, IMAP4 and
> > SDPS
> > 
> >  getmail is intended as a simple replacement for fetchmail. It
> > retrieves mail (either all messages, or only unread messages) from
> > one or more POP3/IMAP4/SDPS servers for one or more email accounts,
> > and reliably
> >  delivers into a qmail-style Maildir, mbox file or to a command
> > (pipe delivery) like maildrop or procmail, specified on a per-
> > account basis. getmail also has support for domain (multidrop)
> > mailboxes.
> > 
> > The current getmail package only works with python2.
> > 
> > But debian has moved to python3.
> > 
> > Therefore getmail6, which is designed to work with python3, should
> > be
> > added to Debian.
> > 
> > No need to update the current debian getmail package.
> > Just somebody should maintain a new independent getmail6 pacakge.
> 
> This getmail6 will install files like:
> /usr/bin/getmail
> /usr/bin/getmail_fetch
> /usr/bin/getmail_mbox
> /usr/bin/getmail_maildir
> /usr/bin/getmail-gmail-xoauth-tokens
> /usr/lib/python3/dist-packages/getmailcore
> 
> which are also installed by getmail.
> 
> So, I guess the best possible way might be if getmail maintainer
> updates
> to this source, else I can package getmail6 with a "Breaks: getmail".
> 
> 
> --
> Regards
> Sudip

Bug#969177: debmake: cannot create deb for nodejs modeule

Control: severity -1 important

Hi,

Thanks for the log which helps

It only breaks for javascript/nodejs.  

Javascript/nodejs support is new and needs help.  Besides

(You shouldn't file a grave RC bug without throurough review against
policy.)

On Fri, 2020-08-28 at 21:39 +0530, Pirate Praveen wrote:
> package: debmake
> version: 4.3.2-1
> severity: grave
> 
> Using pretty-ms node module as example. debmake 4.3.2-1 worked.

I don"t know how people download such nodejs tarball from where.
 Please tell me how you did it.  Please tell me how so I can test.

> (debian-sid)pravi@ilvala2:~/packaging/node-pretty-ms-7.0.0$ debmake
> I: set parameters
> I: sanity check of parameters
> I: pkg="node-pretty-ms", ver="7.0.0", rev="1"
> I: *** start packaging in "node-pretty-ms-7.0.0". ***
> I: provide node-pretty-ms_7.0.0.orig.tar.gz for non-native Debian 
> package
> I: pwd = "/home/pravi/packaging"
> I: Use existing "node-pretty-ms_7.0.0.orig.tar.gz" as upstream
> tarball
...
"debian/control", debmake.control.control(para), 
> tutorial=para["tutorial"]
>   File "/usr/lib/python3/dist-packages/debmake/control.py", line 60,
> in 
> control
> desc_long_type = debmake.read.read(
>   File "/usr/lib/python3/dist-packages/debmake/read.py", line 30, in 
> read
> with open(file, mode="r", encoding="utf-8") as f:
> FileNotFoundError: [Errno 2] No such file or directory: 
> '/usr/share/debmake/extra0desc_long/nodejs'

Hahaha, that's my mistake.  I forgot to add place holder file.


Osamu

Bug#969224: cdimage.debian.org: Error installing Debian 10.5 from flash stick with Extlinux

2020-08-29 Thread Andrew Cater

This is not a well supported method. Just use dd to write a netinst or a
DVD image straight to the stick and then boot from it directly.

dd if=debian-10.5.0-amd64-DVD-1.iso of=/dev/sdX bs=4M oflag=sync
status=progress

That will put a bootable partition on the stick and then the install will
proceed.

You may need to use parted / fdisk afterwards to make the USB usable for
any other purpose. This method is destructive of any data already on the
stick.



On Sat, Aug 29, 2020 at 2:18 PM Сергей Фёдоров  wrote:

> Package: cdimage.debian.org
> Severity: critical
> Justification: breaks the whole system
>
>
>
> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 5.7.0-3-amd64 (SMP w/8 CPU threads)
> Locale: LANG=ru_RU.utf8, LC_CTYPE=ru_RU.utf8 (charmap=UTF-8), LANGUAGE not
> set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Created a USB flach stick using the" gparted " MBR-partition table.
> GPT-partition table failed to get a working version of the Debian
> installation.
> Created an Ext4-partition and its label. Set the partition "boot"
> attribute.
>
> Created a bootable flash drive:
>
> # dd conv=notrunc bs=440 count=1 if=/usr/lib/EXTLINUX/mbr. bin of=/dev/xxx
> where xxx is the name of the u-VA, for example, sdf.
> # extlinux --install "folder path" (for example " /media/u1/UP1/"), where"
> UP1 " is partition name
>
> For Debian 10.4 copied from a folder:
>
>
> http://ftp.nl.debian.org/debian/dists/Debian10.4/main/installer-amd64/current/images/hd-media/
> or from (for GTK)
>
> http://ftp.nl.debian.org/debian/dists/Debian10.4/main/installer-amd64/current/images/hd-media/gtk/
>
> vmlinuz
> initrd.gz
>
> and copied "debian-10.4.0-amd64-DVD-1.iso"
>
> or
>
> For Debian 10.5 copied from the folder:
>
>
> http://ftp.nl.debian.org/debian/dists/Debian10.5/main/installer-amd64/current/images/hd-media/
> or from (for GTK)
>
> http://ftp.nl.debian.org/debian/dists/Debian10.5/main/installer-amd64/current/images/hd-media/gtk/
>
> vmlinuz
> initrd.gz
>
> and copied "debian-10.5.0-amd64-DVD-1.iso»
>
> In both cases, when installing Debian from a flash drive, I received the
> message:
>
> Load installer components from an ISO installer.
>
> No modules were found. This pfobably is due to a mismatch between the
> kernel
> by this version of the installer and the kernel version available in the
> archieve.
>
> and the installation had to be stopped.
>
> For Debian 10.3 copied from the folder:
>
>
> http://ftp.nl.debian.org/debian/dists/Debian10.3/main/installer-amd64/current/images/hd-media/
> or from (for GTK)
>
> http://ftp.nl.debian.org/debian/dists/Debian10.3/main/installer-amd64/current/images/hd-media/gtk/
>
> vmlinuz
> initrd.gz
>
> and copied "debian-10.3.0-amd64-DVD-1.iso"
>
> and everything was established without problems.
>
> Copy Debian 10.3, 10.4, and 10.5 to a USB stick in the device root,
> download
> with it, the installation of Debian passes without problems.
>
> For example:
>
> dd if="./debian-10.5.0-amd64-DVD-1.iso" of=/dev/xxx bs=1M status=progress
> where xxx is the name of the u-VA, for example, sdf.
>
> Installing Debian 10.3, 10.4, and 10.5 from a DVD does not cause these
> problems.
>
>

Bug#966896: fatsort: FTBFS: ld: entrylist.o:./src/options.h:38: multiple definition of `OPT_LOCALE'; fatsort.o:./src/options.h:38: first defined here

2020-08-29 Thread Alex Muntada

Upstream already fixed this issue in a newer version.

After asking Jordi his permission in private, I've prepared a NMU.

Cheers,
Alex

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



signature.asc
Description: PGP signature

Bug#613724: grub2-splashimages: README documentation needs update

Control: retitle -1 README documentation needs update

Since this gives beutiful boot screen and I have been using this
package, I kind of want this to be around in future.  But this does't
seem to be getting love. It is true this README needs update.  But
package update can't be offered as "it works for me" solution.

In this sense, updated README shouldn't suggest to edit files in /usr.
That kind of solution should never be in README.

Proper way is adding following line at the end of /etc/default/grub
GRUB_BACKGROUND="/usr/share/images/grub/Lake_mapourika_NZ.tga

Alternatively, you can drop Lake_mapourika_NZ.tga in /boot/grub and do
nothing for /etc/default/grub.

Either case, you need to run update-grub.

These are documented in grub but not so obvious.  So having this
example data with easy to use instruction in README is nice to have.

(The above mentioned approaches work on stable version of grub.  It
seems grub-efi-amd64 in testing doesn't handle tga format nicely at
this moment.  It works with PNG and JPG at least as I test it now.
This tga issue is my headache and beyongd me.  If this bug is fixed in
grub-efi-amd64, I may do NMU of grub2-splashimages describing this
proper method if no one objects.)

The updated README should be mostly on 
  https://bugs.debian.org/613724
  https://bugs.debian.org/635545

Other points for bugs on this package may also addressed by this simple
documenation update:

commons25ga.pl: https://bugs.debian.org/719311
The value of this fetch and tga format conversion program is gone.
 grub can handle jpeg, png,   So just download it to g
rub accessible directory and use GRUB_BACKGROUND or move it
to /boot/grub.

update-alternative: https://bugs.debian.org/673088
This is certainly an wishlist.  But looking at the amount of resources
available to keep this package in sync with grub package changes, I
think such effort is over engineering.  Let's keep it simple by this
above mentioned methods.

Additional images: https://bugs.debian.org/873629
I kinda like frog image in this bug report.  I actually tested grub
with one of the jpg in this bug report.  Since action needed is so
simple as just moving it to /boot/grub directory, my question is should
we need to make this package bigger?  What criteria to use to srlect
image.  I think adding text to README to point people to wikimedia
should be enough.  No more file format conversion is needed with
current grub.  I encourage this submitter to upload his image to
wikimedia site etc.:
 * 
https://commons.wikimedia.org/wiki/Category:Commons_featured_desktop_backgrounds
 * 
https://commons.wikimedia.org/wiki/Category:Commons_featured_widescreen_desktop_backgrounds

Bug#969225: python3-electrum: Please relax dependency on python3-qdarkstyle

2020-08-29 Thread intrigeri

Package: python3-electrum
Version: 4.0.2-1
Severity: normal
User: tails-...@boum.org
Usertags: misc-reported

Hi,

I see that electrum has "Recommends: python3-qdarkstyle"; so far,
so good.

On top of that, since 4.0.2-1, python3-electrum has "Depends:
python3-qdarkstyle". Is this absolute dependency needed?
(See Policy 7.2¹ for details.)

I'm asking because:

 - As far as I can tell, electrum and python3-electrum 4.0.2-0.1
   worked just fine without this dependency. So I'm wondering why
   4.0.2-1 differs in this respect.

 - python3-qdarkstyle depends on python3-qtpy, which itself pulls in
   a big pile of python3-pyqt5.*. This causes trouble in the context
   of Tails as this would make our live images and updates
   significantly larger.

[1] 
https://www.debian.org/doc/debian-policy/ch-relationships.html#binary-dependencies-depends-recommends-suggests-enhances-pre-depends

Thank you for maintaining Electrum in Debian,
cheers!

Bug#969198: msmtp-mta package should use update-alternatives for symlinking to msmtp

2020-08-29 Thread Simon Deziel

Hi Heikki,

On 2020-08-29 4:38 a.m., Heikki Orsila wrote:
> msmtp-mta creates a symlink from "/usr/sbin/sendmail" to "../bin/msmtp".
> It does not use update-alternatives which makes it difficult to install
> msmtp-mta and another MTA on the same system.

In this case, you might want to use the msmtp package instead of
msmtp-mta. The former doesn't creates the sendmail symlink.

HTH,
Simon

Bug#968509: Further crashes under linux-image-4.19.0-10-amd64

2020-08-29 Thread Salvatore Bonaccorso

Hi Richard,

On Sat, Aug 22, 2020 at 12:58:47PM +0100, Richard Kettlewell wrote:
> I've had further crashes under 4.19.0-10-amd64 on a second machine.
> Again, after reverting to 4.19.0-9-amd64 this second machine seems to be
> stable.
> 
> The full logs are at http://www.greenend.org.uk/rjk/junk/crashboth.log,
> a version without all the iptables clutter is attached.

I suspect this is possibly same as #966846. If so this was fixed in
4.19.134 upstream but followup commits were needed as up to commits in
4.19.140 upstream. 

Would you be able to test 4.19.142?

Regards,
Salvatore

Bug#968311: gnome-shell in stretch/buster as not affected by CVE-2020-17489

2020-08-29 Thread Mike Gabriel


Hi Simon,

thanks for your reply.

On  Sa 29 Aug 2020 12:47:00 CEST, Simon McVittie wrote:


On Sat, 29 Aug 2020 at 10:16:28 +, Mike Gabriel wrote:

here is a summary of what we discussed on IRC.

  * gnome-shell in stretch+buster reveal password length
  * CVE-2020-17489/buster -> bach to  (fix via buster-pu)
  * CVE-2020-17489/stretch -> back to "vulnerable" (fix via LTS in prep)

@smcv: please let me know if you are ok with me uploading to buster-pu or if
you'd rather like to have a .debdiff.


Thanks for looking into this. If you wouldn't mind
sending a debdiff to this bug (or a merge request to
https://salsa.debian.org/gnome-team/gnome-shell/-/tree/debian/buster,
your choice), it's probably best for someone from the GNOME team to have
the opportunity to check it before uploading to buster-pu - there's no
date planned for Debian 10.6 yet, so we're not on a tight schedule for
-pu uploads.

Thanks,
smcv


Here two MRs, one for buster, one for stretch:

https://salsa.debian.org/gnome-team/gnome-shell/-/merge_requests/40 (buster)
https://salsa.debian.org/gnome-team/gnome-shell/-/merge_requests/41 (stretch)

Looking forward to feedback. Let me know if I shall handle uploads,  
the buster-pu bug report, the DLA report, etc.


Mike
--

mike gabriel aka sunweaver (Debian Developer)
mobile: +49 (1520) 1976 148
landline: +49 (4351) 486 14 27

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: sunwea...@debian.org, http://sunweavers.net



pgpZzHC5euz2F.pgp
Description: Digitale PGP-Signatur

Bug#969014: [Pkg-rust-maintainers] Bug#969014: rustc: Crashes while building Firefox on ppc64el

2020-08-29 Thread Ximin Luo

This is most likely an upstream issue - other architectures are fine, and we 
don't carry any (significant) ppc64el-specific patches in Debian.

You can also try with 1.46.0 which I'm about to upload (and is already in 
experimental).

Best,
Ximin

Mike Hommey:
> Source: rustc
> Version: 1.45.0+dfsg1-2
> Severity: important
> 
> See 
> https://buildd.debian.org/status/fetch.php?pkg=firefox=ppc64el=80.0-1=1598405257=0
> 
> If failed with:
> 
>   process didn't exit successfully: 
> `LD_LIBRARY_PATH='/<>/build-browser/release/deps:/usr/lib' 
> CARGO_PKG_NAME=gkrust CARGO_PKG_HOMEPAGE= CARGO=/usr/bin/cargo 
> CARGO_PKG_VERSION_MAJOR=0 CARGO_PKG_DESCRIPTION='Rust code for libxul' 
> CARGO_MANIFEST_DIR=/<>/toolkit/library/rust 
> CARGO_PKG_VERSION_PATCH=0 CARGO_PKG_VERSION_PRE= CARGO_PKG_VERSION=0.1.0 
> CARGO_PKG_AUTHORS='nob...@mozilla.org' CARGO_PKG_VERSION_MINOR=1 
> CARGO_PKG_REPOSITORY= /usr/bin/rustc --crate-name gkrust 
> toolkit/library/rust/lib.rs --error-format=json 
> --json=diagnostic-rendered-ansi --crate-type staticlib --emit=dep-info,link 
> -C opt-level=2 -C panic=abort -Clto --cfg 'feature="cubeb-remoting"' --cfg 
> 'feature="cubeb_pulse_rust"' --cfg 'feature="moz_memory"' --cfg 
> 'feature="moz_places"' --cfg 'feature="new_cert_storage"' --cfg 
> 'feature="quantum_render"' --cfg 'feature="webgpu"' --cfg 'feature="webrtc"' 
> --cfg 'feature="with_dbus"' -C metadata=d4ec9ff2ad1887b0 -C 
> extra-filename=-d4ec9ff2ad1887b0 --out-dir 
> /<>/build-browser/powerpc64le-unknown-linux-gnu/release/deps 
> --target powerpc64le-unknown-linux-gnu -C 
> linker=/<>/build/cargo-linker -L 
> dependency=/<>/build-browser/powerpc64le-unknown-linux-gnu/release/deps
>  -L dependency=/<>/build-browser/release/deps --extern 
> gkrust_shared=/<>/build-browser/powerpc64le-unknown-linux-gnu/release/deps/libgkrust_shared-feb4fa78eb766296.rlib
>  --extern 
> mozglue_static=/<>/build-browser/powerpc64le-unknown-linux-gnu/release/deps/libmozglue_static-0fad88c66849e71c.rlib
>  --extern 
> mozilla_central_workspace_hack=/<>/build-browser/powerpc64le-unknown-linux-gnu/release/deps/libmozilla_central_workspace_hack-c5f434c402f5edbe.rlib
>  -C opt-level=2 -C debuginfo=2 --cap-lints warn 
> --remap-path-prefix=/<>=. -Cembed-bitcode=yes 
> -Cembed-bitcode=yes -C codegen-units=1 -L 
> native=/usr/lib/powerpc64le-linux-gnu -L 
> native=/<>/build-browser/powerpc64le-unknown-linux-gnu/release/build/lmdb-rkv-sys-fd10de76a837fd29/out
>  -L 
> native=/<>/build-browser/powerpc64le-unknown-linux-gnu/release/build/mozglue-static-d5af1b2a8b33b1ab/out
>  -L native=/<>/build-browser/dist/bin -L 
> native=/<>/build-browser/security/nss/lib/nss/nss_nss3 -L 
> native=/<>/build-browser/security/nss/lib/ssl/ssl_ssl3 -L 
> native=/<>/build-browser/config/external/nspr/pr -L 
> native=/<>/build-browser/powerpc64le-unknown-linux-gnu/release/build/swgl-edbaccb8c334575f/out
>  -L native=/usr/lib/powerpc64le-linux-gnu` (signal: 11, SIGSEGV: invalid 
> memory reference)
> 
> ___
> Pkg-rust-maintainers mailing list
> pkg-rust-maintain...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-rust-maintainers
> 


-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git

Bug#969224: cdimage.debian.org: Error installing Debian 10.5 from flash stick with Extlinux

2020-08-29 Thread Сергей Фёдоров

Package: cdimage.debian.org
Severity: critical
Justification: breaks the whole system

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

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

Created a USB flach stick using the" gparted " MBR-partition table.
GPT-partition table failed to get a working version of the Debian installation.
Created an Ext4-partition and its label. Set the partition "boot" attribute.

Created a bootable flash drive:

# dd conv=notrunc bs=440 count=1 if=/usr/lib/EXTLINUX/mbr. bin of=/dev/xxx
where xxx is the name of the u-VA, for example, sdf.
# extlinux --install "folder path" (for example " /media/u1/UP1/"), where" UP1
" is partition name

For Debian 10.4 copied from a folder:

http://ftp.nl.debian.org/debian/dists/Debian10.4/main/installer-amd64/current/images/hd-media/
or from (for GTK)
http://ftp.nl.debian.org/debian/dists/Debian10.4/main/installer-amd64/current/images/hd-media/gtk/

vmlinuz
initrd.gz

and copied "debian-10.4.0-amd64-DVD-1.iso"

For Debian 10.5 copied from the folder:

http://ftp.nl.debian.org/debian/dists/Debian10.5/main/installer-amd64/current/images/hd-media/
or from (for GTK)
http://ftp.nl.debian.org/debian/dists/Debian10.5/main/installer-amd64/current/images/hd-media/gtk/

vmlinuz
initrd.gz

and copied "debian-10.5.0-amd64-DVD-1.iso»

In both cases, when installing Debian from a flash drive, I received the
message:

Load installer components from an ISO installer.

No modules were found. This pfobably is due to a mismatch between the kernel
by this version of the installer and the kernel version available in the
archieve.

and the installation had to be stopped.

For Debian 10.3 copied from the folder:

http://ftp.nl.debian.org/debian/dists/Debian10.3/main/installer-amd64/current/images/hd-media/
or from (for GTK)
http://ftp.nl.debian.org/debian/dists/Debian10.3/main/installer-amd64/current/images/hd-media/gtk/

vmlinuz
initrd.gz

and copied "debian-10.3.0-amd64-DVD-1.iso"

and everything was established without problems.

Copy Debian 10.3, 10.4, and 10.5 to a USB stick in the device root, download
with it, the installation of Debian passes without problems.

For example:

dd if="./debian-10.5.0-amd64-DVD-1.iso" of=/dev/xxx bs=1M status=progress
where xxx is the name of the u-VA, for example, sdf.

Installing Debian 10.3, 10.4, and 10.5 from a DVD does not cause these problems.

Bug#969223: Can't rm directory on overlayfs in userns

2020-08-29 Thread Shengjing Zhu

Source: linux
Version: 5.7.10-1
Severity: normal

Hi,

After enabling overlayfs for userns, I find it doesn't work as expected.

$ cat /sys/module/overlay/parameters/permit_mounts_in_userns 
Y

zsj@debian:~/test$ pwd
/home/zsj/test
zsj@debian:~/test$ tree
.
├── lower
│   └── a
│   └── a
├── merged
├── upper
└── work

zsj@debian:~/test$ unshare -m -U -r
root@debian:~/test# mount -t overlay -o 
rw,lowerdir=/home/zsj/test/lower,upperdir=/home/zsj/test/upper,workdir=/home/zsj/test/work
 overlay /home/zsj/test/merged
root@debian:~/test# rm -rf merged/a
rm: cannot remove 'merged/a': Input/output error

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

Kernel: Linux 5.7.0-2-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_USER, TAINT_FIRMWARE_WORKAROUND
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Bug#969210: [Pkg-rust-maintainers] Bug#969210: rust-doc: Link to cargo documentation is wrong

2020-08-29 Thread Ximin Luo

Control: reassign -1 cargo-doc
Control: forcemerge 969210 -1

In fact the link would be correct, however the underlying problem is that the 
cargo documentation is currently not being built:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934938

I don't have time to fix it, but I describe the steps needed to fix it here:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934938#10

Patches welcome.

Best
Ximin

Michael Becker:
> Package: rust-doc
> Version: 1.45.0+dfsg1-2
> Severity: important
> 
> The rust documentation links to the cargo documentation by referencing file
> /usr/share/doc/cargo-doc/doc/index.html
> but the cargo documentation is stored in /usr/share/doc/cargo/doc.
> Beside that the package cargo-doc does not contain a file
> /usr/share/doc/cargo/doc/index.html
> 
> 
> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 5.7.0-2-amd64 (SMP w/8 CPU threads)
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not 
> set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages rust-doc depends on:
> ii  fonts-font-awesome  5.0.10+really4.7.0~dfsg-2
> ii  fonts-open-sans 1.11-1
> ii  libjs-highlight.js  9.12.0+dfsg1-5
> ii  libjs-jquery3.5.1+dfsg-4
> ii  libjs-mathjax   2.7.8+dfsg-1
> 
> Versions of packages rust-doc recommends:
> ii  cargo-doc  0.43.1-3
> 
> rust-doc suggests no packages.
> 
> -- no debconf information
> 
> ___
> Pkg-rust-maintainers mailing list
> pkg-rust-maintain...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-rust-maintainers
> 


-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git

Bug#969174: firefox: FF80 seems to have broken all add-ons on existing profiles

2020-08-29 Thread Christoph Anton Mitterer

On Sat, 2020-08-29 at 10:55 +0200, Jean-Marc wrote:
> One remark nevertheless : if I open the page about:support and click
> on the button "Refresh Firefox..." and then re-start Firefox, I got
> the icon of the add-ons I installed through Debian packages meaning
> noScript, privacy Badger and uBlock Origin in the FF bar.
> 
> Chris, can you try this ?

What (temporarily) worked for me was to disable/re-enable the addons
with the switch in the add-ons menu... but after restarting they were
all gone again.

IMO this is even a security issue, as it breaks security-relevant
plugins like noscript or https-everywhere.

> Chris, Mike, did you install add-ons from Debian or directly from FF
> repository ?

All from Debian, all unstable.

Cheers,
Chris.

Bug#891978: License of photoswipe

2020-08-29 Thread Dmitry Semenov

Hey David,

Yes, that's ok. The official license is on Github anyway
https://github.com/dimsemenov/PhotoSwipe/blob/master/LICENSE ,
sidenote about WP plugin is just a simple request on the demo website, I
don't think it has any legal power.

If you'll have some questions about Photoswipe itself - feel free to email
me directly.

-
Dmitry

сб, 29 авг. 2020 г. в 15:52, David Bremner :

>
> Hi Dmitry;
>
> We'd like to include PhotoSwipe in Debian (and hence also in Ubuntu,
> Mint, etc...), but the statement
>
>   Script is licensed under MIT license with one exception: Do not create a
>   public WordPress plugin based on it, as I will develop it. If you need
>   to use it for a public WordPress plugin right now, please ask me by
>   email first. Thanks!
>
> is currently blocking us, since it seems to impose specific licensing
> conditions that might not fit with the Debian Free Software
> Guidelines. Would a slightly weaker version be OK with you? I was
> thinking of something like:
>
>   PhotoSwipe is licensed under the MIT license.  Please contact me by
>   email before developing a public WordPress plugin based on PhotoSwipe.
>
> Thanks for considering,
>
> David
>
> P.S. I've copied this message to the public bug log. Be sure to remove
> the 891...@bugs.debian.org address if you don't want your reply to be
> public.
>

Bug#969222: cyrus-caldav: hhtp keep 100% CPU after access with Thunderbird

2020-08-29 Thread Hinrich

Package: cyrus-caldav
Version: 3.2.2-1~bpo10+1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

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

   * What led up to the situation?
Installation of cyrus (3.2.2-1~bpo10+1) including cyrus-caldav on (up-to-date) 
buster and accessing it with Thunderbird 68.11.0 (with build-in support for 
CalDAV and CardDAV support by Cardbook 45.1).
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
I created only the default INBOX for e-mail and the default addressbook and 
default calendar with Thunderbird (by opening the nonexistend address book and 
calendar with Thunderbird, which triggers an autocreation). Access both address 
booke and calendar (I tried both empty ones and with one entry each).
   * What was the outcome of this action?
Until Thunderbird was in usage, anything was ok. However, just after quiting it 
two httpd processes goes to 100% CPU each and stay until /etc/cyrus-imapd 
restart.
This did not happen using iPAD with Apple standard apps.
The is no error indication in syslog.
Deactivating Cardbook extension resulted in one httpd session with 100% CPU.
   * What outcome did you expect instead?
No httpd processes at all after quitting Thonderbird.
Using cyrus 3.0.8.6+deb10u4 works as expected. I wrote this report after 
installing it, therefore the template may show wrong information regarding 
cyrus version.

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


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

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

Versions of packages cyrus-caldav depends on:
ii  cyrus-common  3.0.8-6+deb10u4
ii  dpkg  1.19.7
ii  libc6 2.28-10
ii  libcom-err2   1.44.5-1+deb10u3
ii  libical3  3.0.4-3
ii  libjansson4   2.12-1
ii  libsasl2-22.1.27+dfsg-1+deb10u1
ii  libsqlite3-0  3.27.2-3
ii  libssl1.1 1.1.1d-0+deb10u3
ii  libwrap0  7.6.q-28
ii  libxml2   2.9.4+dfsg1-7+b3
ii  zlib1g1:1.2.11.dfsg-1

cyrus-caldav recommends no packages.

cyrus-caldav suggests no packages.

-- no debconf information

Bug#969221: gcc-10: Please disable Go backend on sh4

2020-08-29 Thread John Paul Adrian Glaubitz

Source: gcc-10
Severity: normal
User: debian-sup...@lists.debian.org
Usertags: sh4
X-Debbugs-Cc: debian-sup...@lists.debian.org

Hi!

The Go backend currently causes gcc on sh4 failing to build from source.

Could you disable the backend for the time being in gcc-9, gcc-10 and
gcc-snapshot until the issue has been resolved?

It's most likely a bug in glibc and not gcc itself but prevents the Go
backend from being built.

Thanks,
Adrian

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#969220: postgresql-common: [INTL:it] Italian translations updated

2020-08-29 Thread Luca Monducci

Package: postgresql-common
Severity: wishlist
Tags: l10n, patch

Hi,
updated Italian translation for debconf templates is attached.

Regards,
Luca






# Italian (it) translation of debconf templates for postgresql-common
# This file is distributed under the same license as the postgresql-common 
package.
# Luca Monducci , 2006-2020.
#
msgid ""
msgstr ""
"Project-Id-Version: postgresql-common 216 italian debconf templates\n"
"Report-Msgid-Bugs-To: postgresql-com...@packages.debian.org\n"
"POT-Creation-Date: 2016-03-05 11:47+0100\n"
"PO-Revision-Date: 2020-08-29 14:43+0200\n"
"Last-Translator: Luca Monducci \n"
"Language-Team: Italian \n"
"Language: it\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Type: error
#. Description
#: ../postgresql-common.templates:1001
msgid "Obsolete major version ${old}"
msgstr "La versione ${old} è obsoleta"

#. Type: error
#. Description
#: ../postgresql-common.templates:1001
msgid ""
"The PostgreSQL version ${old} is obsolete, but the server or client packages "
"are still installed. Please install the latest packages (postgresql-"
"${latest} and postgresql-client-${latest}) and upgrade the existing "
"${oldversion} clusters with pg_upgradecluster (see manpage)."
msgstr ""
"La versione ${old} di PostgreSQL è obsoleta ma alcuni dei pacchetti server "
"o client sono ancora installati. Installare i pacchetti più recenti "
"(postgresql-${latest} e postgresql-client-${latest}) e aggiornare i cluster "
"${oldversion} esistenti con pg_upgradecluster (consultare la pagina man)."

#. Type: error
#. Description
#: ../postgresql-common.templates:1001
msgid ""
"Please be aware that the installation of postgresql-${latest} will "
"automatically create a default cluster ${latest}/main. If you want to "
"upgrade the ${old}/main cluster, you need to remove the already existing "
"${latest} cluster (pg_dropcluster --stop ${latest} main, see manpage for "
"details)."
msgstr ""
"Attenzione: l'installazione di postgresql-${latest} crea automaticamente il "
"cluster predefinito ${latest}/main. Per aggiornare il cluster ${old}/main è "
"necessario rimuovere cluster ${latest} dopo la sua creazione (pg_dropcluster "
"--stop ${latest} main, consultare la pagina man per i dettagli)."

#. Type: error
#. Description
#: ../postgresql-common.templates:1001
msgid ""
"The old server and client packages are no longer supported. After the "
"existing clusters are upgraded, the postgresql-${old} and postgresql-client-"
"${old} packages should be removed."
msgstr ""
"I vecchi pacchetti di server e client non sono più supportati. Dopo aver "
"aggiornato i cluster esistenti è consigliabile rimuovere i pacchetti "
"postgresql-${old} e postgresql-client-${old}."

#. Type: error
#. Description
#: ../postgresql-common.templates:1001
msgid ""
"Please see /usr/share/doc/postgresql-common/README.Debian.gz for details."
msgstr ""
"Consultare /usr/share/doc/postgresql-common/README.Debian.gz per i dettagli."

#. Type: boolean
#. Description
#: ../postgresql-common.templates:2001
msgid "Enable SSL by default in new PostgreSQL clusters?"
msgstr "Attivare in modo predefinito SSL nei nuovi cluster PostgreSQL?"

#. Type: boolean
#. Description
#: ../postgresql-common.templates:2001
msgid ""
"PostgreSQL supports SSL-encrypted connections. This is usually a good thing. "
"However, if the database is solely accessed using TCP connections on "
"localhost, SSL can be turned off without introducing security issues."
msgstr ""
"PostgreSQL supporta connessioni cifrate con SSL e questa è una cosa buona, "
"tuttavia, se l'accesso al database avviene solo con connessioni TCP da "
"localhost allora è possibile disabilitare SSL senza il rischio di esporsi a "
"problemi di sicurezza."

#. Type: boolean
#. Description
#: ../postgresql-common.templates:2001
msgid ""
"UNIX domain socket connections (called \"local\" in pg_hba.conf) are not "
"affected by this setting. This setting concerns new PostgreSQL clusters "
"created during package install, or by using the pg_createcluster command. It "
"does not reconfigure existing clusters."
msgstr ""
"Le connessioni tramite socket di dominio locale UNIX (chiamate \"local\" in "
"pg_hba.conf) non sono influenzate da questa impostazione. Questa "
"impostazione riguarda solo i nuovi cluster PostgreSQL creati durante "
"l'installazione del pacchetto oppure utilizzando il comando pg_createcluster "
"e non modifica la configurazione di nessuno dei cluster esistenti."

#. Type: boolean
#. Description
#: ../postgresql-common.templates:2001
msgid "If unsure, enable SSL."
msgstr "Se non si è sicuri, attivare SSL."

#. Type: note
#. Description
#: ../postgresql-common.templates:3001
msgid "PostgreSQL ${version} catalog version changed"
msgstr "Nuova versione ${version} del catalogo PostgreSQL"

#. Type: note
#. Description
#: ../postgresql-common.templates:3001
msgid ""
"The PostgreSQL cluster ${version} ${cluster} was created using catalog "

Bug#891978: License of photoswipe

2020-08-29 Thread David Bremner



Hi Dmitry;

We'd like to include PhotoSwipe in Debian (and hence also in Ubuntu,
Mint, etc...), but the statement

  Script is licensed under MIT license with one exception: Do not create a
  public WordPress plugin based on it, as I will develop it. If you need
  to use it for a public WordPress plugin right now, please ask me by
  email first. Thanks!

is currently blocking us, since it seems to impose specific licensing
conditions that might not fit with the Debian Free Software
Guidelines. Would a slightly weaker version be OK with you? I was
thinking of something like:

  PhotoSwipe is licensed under the MIT license.  Please contact me by
  email before developing a public WordPress plugin based on PhotoSwipe.

Thanks for considering,

David

P.S. I've copied this message to the public bug log. Be sure to remove
the 891...@bugs.debian.org address if you don't want your reply to be
public.

Bug#969219: glibc: [INTL:it] Italian translations updated

2020-08-29 Thread Luca Monducci

Package: glibc
Severity: wishlist
Tags: l10n, patch

Hi,
updated Italian translation for debconf templates is attached.

Regards,
Luca




# Italian (it) translation of debconf templates for glibc
# This file is distributed under the same license as the glibc package.
# Luca Monducci , 2005-2020.
#
msgid ""
msgstr ""
"Project-Id-Version: glibc 2.31 debconf templates\n"
"Report-Msgid-Bugs-To: gl...@packages.debian.org\n"
"POT-Creation-Date: 2017-08-26 13:35+0200\n"
"PO-Revision-Date: 2020-08-29 14:41+0200\n"
"Last-Translator: Luca Monducci \n"
"Language-Team: Italian \n"
"Language: it\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Type: multiselect
#. Choices
#: ../debhelper.in/locales.templates:1001
msgid "All locales"
msgstr "Tutti i «locale»"

#. Type: multiselect
#. Description
#: ../debhelper.in/locales.templates:1002
msgid "Locales to be generated:"
msgstr "«Locale» da generare:"

#. Type: multiselect
#. Description
#: ../debhelper.in/locales.templates:1002
msgid ""
"Locales are a framework to switch between multiple languages and allow users "
"to use their language, country, characters, collation order, etc."
msgstr ""
"I «locale» sono l'infrastruttura che permette di passare da una lingua a "
"un'altra e consente agli utenti di utilizzare la propria lingua, paese, "
"caratteri, criteri di ordinamento, ecc."

#. Type: multiselect
#. Description
#: ../debhelper.in/locales.templates:1002
msgid ""
"Please choose which locales to generate. UTF-8 locales should be chosen by "
"default, particularly for new installations. Other character sets may be "
"useful for backwards compatibility with older systems and software."
msgstr ""
"Scegliere quali «locale» generare. È opportuno scegliere i «locale» UTF-8, "
"in particolare sulle nuove installazioni. Gli altri set di caratteri "
"potrebbero essere utili per risolvere problemi di compatibilità all'indietro "
"con sistemi o programmi più vecchi."

#. Type: select
#. Choices
#: ../debhelper.in/locales.templates:2001
msgid "None"
msgstr "Nessuno"

#. Type: select
#. Description
#: ../debhelper.in/locales.templates:2002
msgid "Default locale for the system environment:"
msgstr "«Locale» predefinito sul sistema:"

#. Type: select
#. Description
#: ../debhelper.in/locales.templates:2002
msgid ""
"Many packages in Debian use locales to display text in the correct language "
"for the user. You can choose a default locale for the system from the "
"generated locales."
msgstr ""
"Molti pacchetti Debian usano i «locale» per mostrare messaggi nella lingua "
"dell'utente. È possibile scegliere, fra quelli generati, un «locale» come "
"predefinito per il sistema."

#. Type: select
#. Description
#: ../debhelper.in/locales.templates:2002
msgid ""
"This will select the default language for the entire system. If this system "
"is a multi-user system where not all users are able to speak the default "
"language, they will experience difficulties."
msgstr ""
"Questo imposta la lingua predefinita per l'intero sistema. Se questo è un "
"sistema multi-utente e alcuni utenti non parlano la lingua predefinita, "
"quegli utenti potrebbero avere delle difficoltà."

#. Type: boolean
#. Description
#: ../debhelper.in/libc.templates:1001
msgid "Do you want to upgrade glibc now?"
msgstr "Aggiornare glibc adesso?"

#. Type: boolean
#. Description
#: ../debhelper.in/libc.templates:1001
msgid ""
"Running services and programs that are using NSS need to be restarted, "
"otherwise they might not be able to do lookup or authentication any more. "
"The installation process is able to restart some services (such as ssh or "
"telnetd), but other programs cannot be restarted automatically. One such "
"program that needs manual stopping and restart after the glibc upgrade by "
"yourself is xdm - because automatic restart might disconnect your active X11 "
"sessions."
msgstr ""
"I servizi e i programmi in esecuzione che usano NSS devono essere riavviati "
"altrimenti potrebbero non essere più in grado di effettuare ricerche o "
"autenticazioni. Il processo d'installazione è in grado di riavviare alcuni "
"servizi (come ssh o telnetd), ma altri programmi non possono essere "
"riavviati automaticamente. Uno dei programmi che devono essere fermati e "
"riavviati manualmente dopo l'aggiornamento di glibc è xdm perché il riavvio "
"automatico potrebbe disconnettere la propria sessione X11 attiva."

#. Type: boolean
#. Description
#: ../debhelper.in/libc.templates:1001
msgid ""
"This script detected the following installed services which must be stopped "
"before the upgrade: ${services}"
msgstr ""
"Questo script ha rilevato che i seguenti servizi devono essere fermati prima "
"dell'aggiornamento: ${services}"

#. Type: boolean
#. Description
#: ../debhelper.in/libc.templates:1001
msgid ""
"If you want to interrupt the upgrade now and continue later, please answer "
"No to the question below."
msgstr ""
"Per interrompere adesso l'aggiornamento

Bug#969174: firefox: FF80 seems to have broken all add-ons on existing profiles

2020-08-29 Thread Jean-Marc

On Fri, 28 Aug 2020 17:18:44 +0200 Christoph Anton Mitterer 
 wrote:
> Package: firefox
> Version: 80.0-1
> Severity: normal
> 
> 
> Hi.
> 
> It seems that with FF80 all addons are broken in existing profiles. They're 
> shown
> in the add-ons list, but e.g. their icons aren’t in the menu.
> 
> E.g. ublock origin, noscript also don't seem to work... so it's not just a 
> display
> issue.
> 
> Cheers,
> Chris

I am facing the same issue.  Add-ons installed, shown as active in the add-ons' 
menu but
not appearing in the FF bar as they were with FF79.

One remark nevertheless : if I open the page about:support and click on the 
button "Refresh Firefox..." and then re-start Firefox, I got the icon of the 
add-ons I installed through Debian packages meaning noScript, privacy Badger 
and uBlock Origin in the FF bar.

Chris, can you try this ?

But after browsing the web and re-starting FF, they disappeared again.

Chris, Mike, did you install add-ons from Debian or directly from FF repository 
?

Maybe the current versions are not compatible with FF80.

My installed packages:
Packages  Version
=-=
firefox   80.0-1
webext-noscript   10.1.9.6-2
webext-privacy-badger 2020.7.21-1
webext-ublock-origin  1.28.0+dfsg-1

Regards,

Jean-Marc 
https://6jf.be/keys/ED863AD1.txt
https://6jf.be/keys/ED0B8558.txt

pgpu5zBlp8Xi7.pgp
Description: PGP signature

Bug#969218: proposed-RM: paxctld -- RoQA; no longer useful

Package: paxctld
Severity: serious
Version: 1.2.1-1
Tags: bullseye sid

Hi,

as far as I understand, paxctld is only useful with the semi-proprietary
GRsec kernel patches.  As these are now more or less proprietary,
paxctld doesn't seem useful in Debian.

I therefore suggest to remove paxctld from Debian.

I'll reassign this removal request to the ftp.debian.org pseudopackage
after some time if there are no objections.

Ansgar

Bug#969217: adduser: [INTL:it] Italian translations updated

2020-08-29 Thread Luca Monducci

Package: adduser
Severity: wishlist
Tags: l10n, patch

Hi,
updated Italian translation for debconf templates is attached.

Regards,
Luca


msgid ""
msgstr ""
"Project-Id-Version: adduser 3.118 (debconf templates)\n"
"Report-Msgid-Bugs-To: addu...@packages.debian.org\n"
"POT-Creation-Date: 2018-09-15 15:13-0400\n"
"PO-Revision-Date: 2020-08-29 14:25+0200\n"
"Last-Translator: Luca Monducci \n"
"Language-Team: Italian \n"
"Language: it\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Type: title
#. Description
#: ../templates:2001
msgid "Adduser"
msgstr "Adduser"

#. Type: boolean
#. Description
#: ../templates:3001
msgid "Do you want system-wide readable home directories?"
msgstr "Si vuole che le directory home siano leggibili da tutti?"

#. Type: boolean
#. Description
#: ../templates:3001
msgid ""
"By default, users' home directories are readable by all users on the system. "
"If you want to increase security and privacy, you might want home "
"directories to be readable only for their owners. But if in doubt, leave "
"this option enabled."
msgstr ""
"Con la configurazione predefinita le directory home degli utenti sono "
"leggibili da tutti gli utenti del sistema. Per incrementare sicurezza e "
"privacy sul sistema è possibile rendere le directory home leggibili solo dai "
"legittimi proprietari. Se non si è sicuri, lasciare attiva questa opzione."

#. Type: boolean
#. Description
#: ../templates:3001
msgid ""
"This will only affect home directories of users added from now on with the "
"adduser command."
msgstr ""
"Questa modifica ha effetto solo sulle directory home degli utenti che "
"verranno creati con il comando adduser da adesso in poi."

Bug#969216: libubootenv: please add symbols file

2020-08-29 Thread Gianfranco Costamagna

Source: libubootenv
Version: 0.3-1
tags: patch

Hello,

The package is trivial, the symbols file too, I don't see any reason for not 
having one!

diff -pruN 0.2-1/debian/libubootenv0.1.symbols 
0.2-1ubuntu1/debian/libubootenv0.1.symbols
--- 0.2-1/debian/libubootenv0.1.symbols 1970-01-01 00:00:00.0 +
+++ 0.2-1ubuntu1/debian/libubootenv0.1.symbols  2020-07-02 11:38:52.0 
+
@@ -0,0 +1,14 @@
+libubootenv.so.0.2 libubootenv0.1 #MINVER#
+ libuboot_close@Base 0.2
+ libuboot_configure@Base 0.2
+ libuboot_env_store@Base 0.2
+ libuboot_exit@Base 0.2
+ libuboot_get_env@Base 0.2
+ libuboot_getname@Base 0.2
+ libuboot_getvalue@Base 0.2
+ libuboot_initialize@Base 0.2
+ libuboot_iterator@Base 0.2
+ libuboot_load_file@Base 0.2
+ libuboot_open@Base 0.2
+ libuboot_read_config@Base 0.2
+ libuboot_set_env@Base 0.2


This way we can trivially track new symbols and ABI changes!

cheers,

the patch has been contributed by Ubuntu, by Dave Jones 
 

Gianfranco

Bug#964308: RFS: geshi/1.0.9.1-1 [ITA] -- Generic Syntax Highlighter

2020-08-29 Thread Nick Gasson

Hi Adrian,

Thanks for looking at this. I've uploaded a new version to
mentors.debian.net (#4):

https://mentors.debian.net/debian/pool/main/g/geshi/geshi_1.0.9.1-1.dsc

>
> -Build-Depends: cdbs, debhelper (>= 9)
> +Build-Depends: debhelper (>= 9), debhelper-compat (= 13)
>
> On the nitpick side is that debhelper-compat (= 13) is sufficient.

Done.

>
> Slightly more serious that you should document the switch from cdbs in 
> the changelog.
>

OK, I've added a changelog entry about this.

>>...
>> +  * debian/tests/test.php: add a simple sanity test.
>>...
>
> Is anything running this test?
> This looks like an autopkgtest without the control file.
>

No, I was just running it manually before. I've added a
debian/tests/control file and expected output so autopkgtest can run it.

>
> More a question is whether the Homepage in debian/control still points 
> to the best place. The current URL points to an outdated location.

I think http://qbnz.com/highlighter/ is still the best homepage, even
though it's outdated. The other option would be the GitHub project page
but that doesn't contain the documentation and examples which would be
more useful to end users. I asked on their GH Issues if the homepage
could be updated.

--
Thanks,
Nick

Bug#969215: dkimpy-milter: doesn't sign header fields containing Unicode

Package: dkimpy-milter
Version: 1.2.1-1~bpo10+1
Severity: normal
Tags: upstream

I tried sending a mail with "From: @43-1.org", "To: @43-1.org",
but dkimpy-milter didn't sign the message (it signs other mails) and
the following error appeared in the log:

+---
| dkimpy-milter[454]: DKIM: The From header field MUST be signed
+---

If I use "From: {us-ascii-only}@43-1.org", "To: @43-1.org", then the
DKIM-Signature exists, but doesn't cover the "To" field:

+---
| DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=43-1.org;
|  i=@43-1.org; q=dns/txt; s=2019; t=1598699673; h=subject : mime-version
|  : content-type : content-transfer-encoding : message-id : from : date
|  : from; bh=UjN96cC7omIGsgVag4PTJFDc2e+vxauhwCLS/rjCqvg=;
+---

It looks like dkimpy-milter silently discards header fields containing
Unicode when signing.

The same might happen when verifying mails (dkimpy-milter couldn't
verify a signature where the signed "To" field contained unicode,
while Spamassassin's DKIM check reported DKIM_VALID; not including the
header when verifying the signature might be a possible explaination).

Ansgar

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

Kernel: Linux 5.7.0-0.bpo.2-cloud-amd64 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages dkimpy-milter depends on:
ii  adduser3.118
ii  python33.7.3-1
ii  python3-authres1.2.0-1~bpo10+1
ii  python3-dkim   1.0.3-1~bpo10+1
ii  python3-dns3.2.0-2
ii  python3-dnspython  1.16.0-1
ii  python3-milter 1.0.3-3
ii  python3-nacl   1.3.0-2
ii  python3-pkg-resources  40.8.0-1

dkimpy-milter recommends no packages.

Versions of packages dkimpy-milter suggests:
ii  lsb-base  10.2019051400
ii  postfix   3.4.14-0+deb10u1

-- Configuration Files:
/etc/dkimpy-milter.conf [Errno 2] No such file or directory: 
'/etc/dkimpy-milter.conf'
/etc/dkimpy-milter/dkimpy-milter.conf changed [not included]

-- no debconf information

Bug#969214: node-rollup-plugin-babel: Homepage is outdated

2020-08-29 Thread Jonas Smedegaard

Package: node-rollup-plugin-babel
Version: 4.4.0-8
Severity: minor

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Package node-rollup-plugin-babel points to
https://github.com/rollup/rollup-plugin-babel
as its homepage.

That page is the homepage for an archived project.

Seems the package previously used that project but
(indicated by its explicit dependency on node-babel7)
that current homepage is
https://github.com/rollup/plugins/tree/master/packages/babel

Please double-check if my reasoning is correct,
and if so, please update the homepage.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl9KREwACgkQLHwxRsGg
ASEKqw/8CacOyCiizIqu8vowQxXz5BIry3No2Uin9x8oJhusCvfPUvQyK3CdGNHX
RqaA5zNAWpjXLvL5EskAjAl51rOTwBrl0mQmTturvTjvr+tpmhZr0gTLerxEeakE
LYQn6IVsBCLwCg3j/dTOkHkfPbwjAEZI0n10yN81bMKWtqWwIDJMlA0igSwZa4t1
K10UX/ZpUi5fmVsms9RqQL+YgIW28K6hh3DCjA+svwLfjqGfCxG92uDBZKa2l7qE
/2yFS6vlGbaw+BSmnIQXy2Wc0M6WCxYaOcYsqaZ5fRSJZ+ZTf6IBX5Hov4BBqRdr
7VooCsyuYpYzxBocgkbHMOMU8YIu+Zhgv4lgkd1o8zLmRBXkyEuM4Vw+4IceIGVU
0OFHiaqAAORSsWrOKqVF+A34k7RTru+KtcO+j0QxJM0JjHYd8j6DmOxVsLUqArTq
r7ph39zsQpsz22jis2SSW+eAM8XbvM1BduBhdkAtLQTxWh9DDfNGnXLeFCK+rf7J
3LFc+3QLM8x/plGaplQU09XmXVAe39r00psCURshUo1Tz2WJ5fRe6e4xQhvnFCet
D8w9FixjKXMe4uVmotitkoXRzb+RygQbB0/YgsGFRfs+NzUCTj9j2NPr67Lk9K4k
89E5Dl19t47XfNeT1O2IQdQAe4FoMisS5O6Roz1r00hcRvhZXJk=
=h1RA
-END PGP SIGNATURE-

Bug#964973: mesa-opencl-icd: Applications using OpenCL crash with ": CommandLine Error: Option 'polly' registered more than once!".

2020-08-29 Thread michiaki ookawa

It seems both libMesaOpenCL.so and libLLVM-10.so links llvm-polly
statically, so its static constructor called twice.

Bug#966992: cause: sfdisk

2020-08-29 Thread Hilko Bengen

control: reassign -1 fdisk 2.36-2
control: retitle -1 Regression in sfdisk 

I have traced the cause fo the nbdkit build failures (e.g. [1] to what
seems to be a regression in sfdisk that manifests itself in a "No space
left on device" error when creating some trivial partitioned disk
images.

,
| $ truncate -s 1G diskfile
| $ /sbin/sfdisk diskfile <<"EOF"
| 2048 1023 L -
| 4096 4095 L -
| 8192 8191 L -
| EOF
| Checking that no-one is using this disk right now ... OK
| 
| Disk diskfile: 1 GiB, 1073741824 bytes, 2097152 sectors
| Units: sectors of 1 * 512 = 512 bytes
| Sector size (logical/physical): 512 bytes / 512 bytes
| I/O size (minimum/optimal): 512 bytes / 512 bytes
| 
| >>> Created a new DOS disklabel with disk identifier 0x2ac58cda.
| diskfile1: Created a new partition 1 of type 'Linux' and of size 511.5 KiB.
| diskfile2: Created a new partition 2 of type 'Linux' and of size 2 MiB.
| diskfile3: No free sectors available.
| Failed to add #3 partition: No space left on device
| Leaving.
`

This worked just fine on Debian/buster (fdisk/2.33.1-0.1).

I'll be investigating further.

Cheers,
-Hilko

[1] 
https://buildd.debian.org/status/fetch.php?pkg=nbdkit=amd64=1.20.6-1=1597140669=0

Bug#969213: rust-rgb: RUSTSEC-2020-0029: Allows viewing and modifying arbitrary structs as bytes

2020-08-29 Thread Salvatore Bonaccorso

Source: rust-rgb
Version: 0.8.11-1
Severity: important
Tags: security upstream
Forwarded: https://github.com/kornelski/rust-rgb/issues/35
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi

For detail see

https://rustsec.org/advisories/RUSTSEC-2020-0029.html
https://github.com/kornelski/rust-rgb/issues/35

Regards,
Salvatore

Bug#969162: checkit_tiff: new upstream available, changed main repository

2020-08-29 Thread Andrei POPESCU

Control: reassign -1 checkit-tiff

On Vi, 28 aug 20, 13:49:20, Andreas Romeyke wrote:
> Package: checkit_tiff
> Version: 0.5.4
> Severity: normal
> Tags: upstream
> 
> Dear Maintainer,
> 
> the main repository of the tool is changed to
> https://art1pirat.spdns.org/art1/checkit_tiff
> 
> the latest release is 0.6.0,see
> https://art1pirat.spdns.org/art1/checkit_tiff/releases for details.
> 
> The former repository is outdated.
> 
> With best regards
> 
> Andreas
> 
> 
> 
> -- System Information:
> Debian Release: 10.5
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 
> 'stable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 5.7.0-0.bpo.2-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 checkit_tiff depends on:
> ii  libc6 2.28-10
> ii  libpcre3  2:8.39-12
> 
> checkit_tiff recommends no packages.
> 
> checkit_tiff suggests no packages.
> 
> -- no debconf information

-- 
Looking after bugs assigned to unknown packages


signature.asc
Description: PGP signature

Bug#969212: libcmark-gfm-extensions-dev: cmark-gfm-core-extensions.h depends on missing config.h

2020-08-29 Thread Ilias Tsitsimpis

Package: libcmark-gfm-extensions-dev
Version: 0.29.0.gfm.0-5
Severity: grave
Justification: renders package unusable

Dear maintainer,

Thanks for fixing bug #968709. While trying to use
libcmark-gfm-extensions-dev (v0.29.0.gfm.0-5 from unstable) to build
haskell-cmark-gfm, it fails with:

/usr/include/cmark-gfm-core-extensions.h:10:10: fatal error: config.h: No such 
file or directory
   10 | #include "config.h" // for bool
  |  ^~
compilation terminated.

The problem is that cmark-gfm-core-extensions.h tries to include
"config.h" which is not available.

Best,

-- 
Ilias

Bug#965293: Please backport mesa to stable (buster)

2020-08-29 Thread Thomas Lamprecht

I'd second this request, it would also enable support for AMD RDNA 1.0 
based GPUs when using a kernel newer than 5.3 from backports.


I have rebuild the one from testing (atm. 20.1.5-1) here and it runs 
just fine, without it my X.org crashes and my whole system hangs.


So, please consider doing a build for buster-backport, it would allow
quite some people to run their HW again without the need to switch to 
testing or sid - which I just cannot do on some systems.


cheers,
Thomas

Bug#966218: firmware: failed to load iwl-debug-yoyo.bin (-2)

2020-08-29 Thread Jeremy L. Gaddis

Control: notfound -1 20200421-1
Control: reassign -1 src:linux
Control: found -1 5.5.13-1
Control: found -1 5.7.17-1
Control: forwarded -1
https://lore.kernel.org/linux-wireless/20200625165210.14904-1-...@kernel.org/
Control: severity -1 minor
Control: tags -1 + patch pending upstream fixed-upstream

--

An upstream patch [0] that suppresses this (harmless) error message
was merged in v5.9-rc1 [1] and should be available in 5.9 and later
kernels.

As a "workaround" (if the error message bothers you), you may set the
iwlwifi module's "enable_ini" parameter to false (e.g., "N"). This
will disable the (attempted) loading of the "iwl-debug-yoyo.bin" file
-- which fails, obviously, causing this error to be generated.

[0]: https://patchwork.kernel.org/patch/11625759/

[1]: https://github.com/torvalds/linux/commit/3f4600d

Bug#964668: fakechroot: FTBFS: dh_auto_test: error: make -j4 test VERBOSE=1 returned exit code 2

2020-08-29 Thread Johannes Schauer

Hi,

On Thu, 9 Jul 2020 13:10:03 +0200 Lucas Nussbaum  wrote:
> During a rebuild of all packages in sid, your package failed to build on
> amd64.

I backported a commit from upstream that fixes this issue:

https://github.com/dex4er/fakechroot/commit/b42d1fb9538f680af2f31e864c555414ccba842a

and prepared an NMU. Debdiff is attached. I uploaded with a delay, so that you
can still cancel it in case I messed up.

Thanks!

cheers, joschdiff -Nru fakechroot-2.19/debian/changelog fakechroot-2.19/debian/changelog
--- fakechroot-2.19/debian/changelog	2019-01-27 16:34:19.0 +0100
+++ fakechroot-2.19/debian/changelog	2020-08-29 13:06:33.0 +0200
@@ -1,3 +1,11 @@
+fakechroot (2.19-3.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add support for statx call by cherry-picking upstream commit (closes:
+#964668)
+
+ -- Johannes 'josch' Schauer   Sat, 29 Aug 2020 13:06:33 +0200
+
 fakechroot (2.19-3.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru fakechroot-2.19/debian/patches/0001-New-statx-function.patch fakechroot-2.19/debian/patches/0001-New-statx-function.patch
--- fakechroot-2.19/debian/patches/0001-New-statx-function.patch	1970-01-01 01:00:00.0 +0100
+++ fakechroot-2.19/debian/patches/0001-New-statx-function.patch	2020-08-29 13:01:36.0 +0200
@@ -0,0 +1,80 @@
+From b42d1fb9538f680af2f31e864c555414ccba842a Mon Sep 17 00:00:00 2001
+From: Piotr Roszatycki 
+Date: Mon, 10 Feb 2020 13:59:10 -0800
+Subject: [PATCH] New `statx` function
+
+---
+ NEWS.md |  1 +
+ configure.ac|  1 +
+ src/Makefile.am |  1 +
+ src/statx.c | 44 
+ 4 files changed, 47 insertions(+)
+ create mode 100644 src/statx.c
+
+--- a/configure.ac
 b/configure.ac
+@@ -265,6 +265,7 @@ AC_CHECK_FUNCS(m4_normalize([
+ statfs64
+ statvfs
+ statvfs64
++statx
+ stpcpy
+ strchrnul
+ strlcpy
+--- a/src/Makefile.am
 b/src/Makefile.am
+@@ -151,6 +151,7 @@ libfakechroot_la_SOURCES = \
+ statfs64.c \
+ statvfs.c \
+ statvfs64.c \
++statx.c \
+ stpcpy.c \
+ strchrnul.c \
+ strchrnul.h \
+--- /dev/null
 b/src/statx.c
+@@ -0,0 +1,44 @@
++/*
++libfakechroot -- fake chroot environment
++Copyright (c) 2010-2020 Piotr Roszatycki 
++
++This library 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.1 of the License, or (at your option) any later version.
++
++This library 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
++Lesser General Public License for more details.
++
++You should have received a copy of the GNU Lesser General Public
++License along with this library; if not, write to the Free Software
++Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307  USA
++*/
++
++
++#include 
++
++#ifdef HAVE_STATX
++
++#define _GNU_SOURCE
++#include 
++#include 
++#include 
++
++#include "libfakechroot.h"
++
++
++wrapper(statx, int, (int dirfd, const char * pathname, int flags, unsigned int mask, struct statx * statxbuf))
++{
++char fakechroot_abspath[FAKECHROOT_PATH_MAX];
++char fakechroot_buf[FAKECHROOT_PATH_MAX];
++debug("statx(%d, \"%s\", %d, %u, )", dirfd, pathname, flags, mask);
++expand_chroot_path_at(dirfd, pathname);
++return nextcall(statx)(dirfd, pathname, flags, mask, statxbuf);
++}
++
++#else
++typedef int empty_translation_unit;
++#endif
diff -Nru fakechroot-2.19/debian/patches/series fakechroot-2.19/debian/patches/series
--- fakechroot-2.19/debian/patches/series	2019-01-27 16:28:35.0 +0100
+++ fakechroot-2.19/debian/patches/series	2020-08-29 13:01:07.0 +0200
@@ -1,2 +1,3 @@
 renameat2.patch
 disable-jemalloc-test
+0001-New-statx-function.patch


signature.asc
Description: signature

Bug#812622: ITA: gpp -- A general-purpose preprocessor with

2020-08-29 Thread Leandro Cunha

Hello,

I am interested in adopting this package to continue providing future
versions, as I have already provided the last two.

Cheers,

Leandro Cunha
Debian Contributor

Bug#969211: RM: redmine/4.0.7-1

2020-08-29 Thread Pirate Praveen


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

redmine is not compatible with rails 6 (#969206). This is blocking
migration of rails 6 to testing. Please remove redmine from testing to
allow rails 6 to migrate to testing.

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

Kernel: Linux 4.19.0-10-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE=en_IN:en
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Bug#968311: gnome-shell in stretch/buster as not affected by CVE-2020-17489

2020-08-29 Thread Simon McVittie

On Sat, 29 Aug 2020 at 10:16:28 +, Mike Gabriel wrote:
> here is a summary of what we discussed on IRC.
> 
>   * gnome-shell in stretch+buster reveal password length
>   * CVE-2020-17489/buster -> bach to  (fix via buster-pu)
>   * CVE-2020-17489/stretch -> back to "vulnerable" (fix via LTS in prep)
> 
> @smcv: please let me know if you are ok with me uploading to buster-pu or if
> you'd rather like to have a .debdiff.

Thanks for looking into this. If you wouldn't mind
sending a debdiff to this bug (or a merge request to
https://salsa.debian.org/gnome-team/gnome-shell/-/tree/debian/buster,
your choice), it's probably best for someone from the GNOME team to have
the opportunity to check it before uploading to buster-pu - there's no
date planned for Debian 10.6 yet, so we're not on a tight schedule for
-pu uploads.

Thanks,
smcv

Bug#955304: debrebuild MR request

2020-08-29 Thread Niels Thykier

tags 955304 + patch
tags 955050 + patch
tags 961864 + patch
thanks

Added MR 202 with patches for these bugs:
https://salsa.debian.org/debian/devscripts/-/merge_requests/202

Thanks,
~Niels

Bug#902270: opgpcard: please make the build reproducible

Dear Maintainer,

> Source: opgpcard
> Version: 0.3.0-1
> Tags: patch

There hasn't seem to be any update on this bug in 797 days, in which
time the Reproducible Builds effort has come on a long way.

Would you consider applying this patch and uploading?


Regards,

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

Bug#862088: compass-h5bp-plugin: please make the build reproducible

Dear Maintainer,

> Source: compass-h5bp-plugin
> Version: 1.0.0-5
> Tags: patch

There hasn't seem to be any update on this bug in 1208 days, in which
time the Reproducible Builds effort has come on a long way.

Would you consider applying this patch and uploading?


Regards,

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

Bug#824533: mlterm: Bug still exists in current version in Debian Stable (Buster)

2020-08-29 Thread Axel Stammler

Package: mlterm
Version: 3.8.6-2
Followup-For: Bug #824533

Dear Maintainer,

even though Hebrew and Arabic seem to be working fine, lots of other UTF 
characters show
up as boxes.

man mlterm: “mlfc command generates ~/.mlterm/aafont automatically.” — The 
command is not
part of this package.

cat /etc/mlterm/aafont: “PLEASE READ /usr/share/doc/mlterm/README.Debian TO USE
ANTI-ALIAS.” — There is no such file.

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

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

Versions of packages mlterm depends on:
ii  libc6   2.28-10
ii  libfreetype62.9.1-3+deb10u1
ii  libgdk-pixbuf2.0-0  2.38.1+dfsg-1
ii  libglib2.0-02.58.3-2+deb10u2
ii  libx11-62:1.6.7-1
ii  mlterm-common   3.8.6-2

Versions of packages mlterm recommends:
ii  mlterm-tools  3.8.6-2

Versions of packages mlterm suggests:
ii  fonts-arphic-bsmi00lp   2.10-17
ii  fonts-arphic-gbsn00lp   2.11-15
ii  fonts-freefont-ttf  20120503-9
ii  fonts-nanum 20180306-1
ii  fonts-vlgothic [fonts-japanese-gothic]  20141206-5
pn  mlterm-im-m17nlib   
pn  mlterm-im-scim  
ii  mlterm-im-uim   3.8.6-2
ii  t1-cyrillic 4.17
ii  unifont 1:11.0.03-1
ii  xfonts-efont-unicode0.4.2-11

-- debconf-show failed

Bug#942006: squeak-plugins-scratch: please make the build reproducible

Dear Maintainer,

> Source: squeak-plugins-scratch
> Version: 1.4.0.2~svn.r83-3
> Tags: patch

There hasn't seem to be any update on this bug in 325 days, in which
time the Reproducible Builds effort has come on a long way.

Would you consider applying this patch and uploading?


Regards,

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

Bug#777401: sauce: please make the build reproducible

Chris Lamb wrote:

> Would you consider applying this patch and uploading?

Friendly ping on this? Looks like there hasn't been any update on this bug in
1273 days now (!).


Regards,

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

Bug#840741: http-icons: please make the build reproducible

Chris Lamb wrote:

> Would you consider applying this patch and uploading?

Friendly ping on this? Seems like there hasn't been any update on this bug in
1376 days now (!).


Regards,

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

Bug#969210: rust-doc: Link to cargo documentation is wrong

2020-08-29 Thread Michael Becker

Package: rust-doc
Version: 1.45.0+dfsg1-2
Severity: important

The rust documentation links to the cargo documentation by referencing file
/usr/share/doc/cargo-doc/doc/index.html
but the cargo documentation is stored in /usr/share/doc/cargo/doc.
Beside that the package cargo-doc does not contain a file
/usr/share/doc/cargo/doc/index.html


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

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

Versions of packages rust-doc depends on:
ii  fonts-font-awesome  5.0.10+really4.7.0~dfsg-2
ii  fonts-open-sans 1.11-1
ii  libjs-highlight.js  9.12.0+dfsg1-5
ii  libjs-jquery3.5.1+dfsg-4
ii  libjs-mathjax   2.7.8+dfsg-1

Versions of packages rust-doc recommends:
ii  cargo-doc  0.43.1-3

rust-doc suggests no packages.

-- no debconf information

Bug#969196: zimlib: symbols updates for architectures built with -O3

2020-08-29 Thread Sebastian Ramacher

Control: severity -1 important

On 2020-08-29 09:47:28 +0200, Gianfranco Costamagna wrote:
> Source: zimlib
> Version: 6.2.0-2
> Severity: serious
> tags: patch
> 
> Hello, zimlib symbols file seems to be really difficult to maintain, breaking 
> on each icu upload, each new gcc upload,
> different gcc optimization levels (such as -O2 and -O3) and so on.

This doesn't seem to affect the current upload as it built on all
release architectures. Why do you think that is a serious issue?

Cheers

> 
> Somebody thinks that symbols files for c++ applications are a waste of time, 
> but I'm sending you another patch that fixes the issue for now, by adding 
> some symbols, and marking some other as optional
> https://wiki.debian.org/UsingSymbolsFiles
> 
> 
> diff -Nru zimlib-6.2.0/debian/changelog zimlib-6.2.0/debian/changelog
> --- zimlib-6.2.0/debian/changelog 2020-08-28 07:35:20.0 +
> +++ zimlib-6.2.0/debian/changelog 2020-08-29 07:43:31.0 +
> @@ -1,3 +1,9 @@
> +zimlib (6.2.0-2ubuntu1) groovy; urgency=medium
> +
> +  * Refresh symbols
> +
> + -- Gianfranco Costamagna   Sat, 29 Aug 2020 
> 09:43:31 +0200
> +
>  zimlib (6.2.0-2) unstable; urgency=medium
>  
>* Upload to unstable
> diff -Nru zimlib-6.2.0/debian/libzim6.symbols 
> zimlib-6.2.0/debian/libzim6.symbols
> --- zimlib-6.2.0/debian/libzim6.symbols   2020-08-28 06:40:45.0 
> +
> +++ zimlib-6.2.0/debian/libzim6.symbols   2020-08-29 07:43:30.0 
> +
> @@ -138,7 +138,7 @@
>   _ZN3zim14TemplateParser15state_token_endEc@Base 6.0.2
>   _ZN3zim14TemplateParser5flushEv@Base 6.0.2
>   _ZN3zim14TemplateParser8state_ltEc@Base 6.0.2
> - _ZN3zim15search_iterator12InternalData11get_articleEv@Base 6.2.0
> + 
> (optional=templinst)_ZN3zim15search_iterator12InternalData11get_articleEv@Base
>  6.2.0
>   _ZN3zim15search_iteratorC1EOS0_@Base 6.0.2
>   _ZN3zim15search_iteratorC1EPNS0_12InternalDataE@Base 6.0.2
>   _ZN3zim15search_iteratorC1ERKS0_@Base 6.0.2
> @@ -185,9 +185,9 @@
>   
> _ZN3zim4unix2FS13makeDirectoryERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
>  6.0.2
>   
> _ZN3zim4unix2FS4joinERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES9_@Base
>  6.0.2
>   
> _ZN3zim4unix2FS6removeERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
>  6.0.2
> - 
> _ZN3zim4unix2FS6renameERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES9_@Base
>  6.0.2
> - 
> _ZN3zim4unix2FS8openFileERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
>  6.0.2
> - 
> _ZN3zim4unix2FS9removeDirERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
>  6.0.2
> + 
> (optional=templinst)_ZN3zim4unix2FS6renameERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES9_@Base
>  6.0.2
> + 
> (optional=templinst)_ZN3zim4unix2FS8openFileERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
>  6.0.2
> + 
> (optional=templinst)_ZN3zim4unix2FS9removeDirERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
>  6.0.2
>  #MISSING: 6.2.0# 
> (optional=templinst|arch=!riscv64)_ZN3zim5CacheINS_15article_index_tESt10shared_ptrIKNS_6DirentEEE3putERKS1_RKS5_@Base
>  6.0.2
>  #MISSING: 6.2.0# 
> (optional=templinst|arch=!riscv64)_ZN3zim5CacheINS_15cluster_index_tESt10shared_ptrINS_7ClusterEEE3putERKS1_RKS4_@Base
>  6.0.2
>   
> (optional=templinst)_ZN3zim5findxINS_8FileImplEEESt4pairIbNS_15article_index_tEERT_cRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
>  6.2.0
> @@ -343,6 +343,8 @@
>   
> _ZN3zim8FileImplC2ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
>  6.0.2
>   _ZN3zim8FileImplD1Ev@Base 6.0.2
>   _ZN3zim8FileImplD2Ev@Base 6.0.2
> + 
> (optional=templinst)_ZN3zim8FilePartINS_4unix2FSEEC1ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
>  6.2.0-2
> + 
> (optional=templinst)_ZN3zim8FilePartINS_4unix2FSEEC2ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
>  6.2.0-2
>  #MISSING: 6.1.3# _ZN3zim8ZIP_INFO4nameB5cxx11E@Base 6.0.2
>   _ZN3zim8envValueEPKcj@Base 6.0.2
>  #MISSING: 6.1.3# _ZN3zim9LZMA_INFO4nameB5cxx11E@Base 6.0.2
> @@ -377,6 +379,8 @@
>   (optional=templinst)_ZN5QueueIPN3zim6writer7ClusterEED0Ev@Base 6.1.3
>   (optional=templinst)_ZN5QueueIPN3zim6writer7ClusterEED1Ev@Base 6.1.3
>   (optional=templinst)_ZN5QueueIPN3zim6writer7ClusterEED2Ev@Base 6.1.3
> + (optional=templinst)_ZN6Xapian13LatLongCoordsC1ERKNS_12LatLongCoordE@Base 
> 6.2.0-2
> + (optional=templinst)_ZN6Xapian13LatLongCoordsC2ERKNS_12LatLongCoordE@Base 
> 6.2.0-2
>   
> (optional=templinst)_ZN6Xapian8Internal13intrusive_ptrINS_5Query8InternalEED1Ev@Base
>  6.2.0
>   
> (optional=templinst)_ZN6Xapian8Internal13intrusive_ptrINS_5Query8InternalEED2Ev@Base
>  6.2.0
>  #MISSING: 6.1.3# 
> (optional=templinst|arch=!amd64)_ZN6icu_6314StringByteSinkINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIc6AppendEPKci@Base
>  6.0.2
> @@ -651,7 +655,7 @@
>   (optional=templinst|arch=!armel 
>

Bug#969209: reportbug: rejects Unicode in "email" setting