Bug#930534: Bug#930521: release.debian.org: provide machine-readable information about the freeze period for each release

[Paul Gevers]

Hi,

On 29-03-2020 08:45, Paul Gevers wrote:
>> I would suggest putting it at a per-release URL:
>>
>> https://release.debian.org/bullseye/freeze-and-release-dates.yaml
> 
> But wouldn't that be harder to find for tracker and other consumers?
> After all, the release name is also in there, so the scheme even
> supports multiple releases to be there at the same time.

Wait, that second part isn't true. But the first question still holds.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#930534: Bug#930521: release.debian.org: provide machine-readable information about the freeze period for each release

[Paul Gevers]

Hi Paul,

On 29-03-2020 01:29, Paul Wise wrote:
> On Sat, 2020-03-28 at 22:21 +0100, Paul Gevers wrote:
> 
>> I have stripped some more from template in the other bug;
> 
> Looks good, but the quiet_period URL points at a buster mail.

Ack.

>> the first version should appear soon at
>> https://release.debian.org/freeze-and-release-dates.yaml
> 
> I would suggest putting it at a per-release URL:
> 
> https://release.debian.org/bullseye/freeze-and-release-dates.yaml

But wouldn't that be harder to find for tracker and other consumers?
After all, the release name is also in there, so the scheme even
supports multiple releases to be there at the same time.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#937521: pyrit: Python2 removal in sid/bullseye

[Sandro Tosi]

> My work was unsuccessful.  With this patch, the package FTBFS and i am
> not in a position to fix this problem.
>
> Keep in mind that patch submiter highlights the need for more testing
> but nobody else steps forward for two months, even upstream developer.
>
> I am afraid that i cannot provide a Python3 pyrit in a timely manner.

Thanks for the update!

so maybe it's time to drop pyrit and it's only reverse dependency
wifite? they are the last rdep of python-scapy, which in turn is the
last rdep of ipython, which could then be dropped entirely, "freeing"
its 14 packages it depends on from a dependency.

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

Bug#945636: discus package python 3 compatibility

[Nicolas CARRIER]

Hello,
I have published a first version of discus, which is now compatible with
python 3.
You can find it at this address:
https://github.com/ncarrier/discus/releases

Best regards.

Bug#955209: xss-lock: dumps core when X shuts down

[Ian Campbell]

On Sat, 2020-03-28 at 14:39 +0100, Tomas Janousek wrote:
> 
> (I also opened this as a merge request on salsa a few months ago:

Sorry, it appears I don't get notifications for these (a common problem
with Salsa I believe, since I really only intended to use it as a
simple git server so I never thought to check anything more). The BTS
remains the default/guaranteed way to contact a maintainer I believe.

I'll take care of this bug/patch shortly, thanks for sending it.

Ian.

Bug#955273: [destroyed object]: error 7: failed to import supplied dmabufs: Unsupported buffer format 808669784

[Josh Triplett]

Package: mpv
Version: 0.32.0-1
Severity: important

As of quite recently, I get the following error when attempting to play
any video under Wayland:

[destroyed object]: error 7: failed to import supplied dmabufs: Unsupported 
buffer format 808669784
[vo/gpu/wayland] Error occurred on the display fd, closing

Potentially relevant: I did just upgrade to Mesa 10.

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

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

Versions of packages mpv depends on:
ii  libarchive13  3.4.0-2
ii  libasound21.2.2-2.1
ii  libass9   1:0.14.0-2
ii  libavcodec58  7:4.2.2-1+b1
ii  libavdevice58 7:4.2.2-1+b1
ii  libavfilter7  7:4.2.2-1+b1
ii  libavformat58 7:4.2.2-1+b1
ii  libavutil56   7:4.2.2-1+b1
ii  libbluray21:1.1.2-2
ii  libc6 2.30-4
ii  libcaca0  0.99.beta19-2.1
ii  libcdio-cdda2 10.2+2.0.0-1+b1
ii  libcdio-paranoia2 10.2+2.0.0-1+b1
ii  libcdio18 2.0.0-2
ii  libdrm2   2.4.100-4
ii  libdvdnav46.1.0-1
ii  libegl1   1.3.1-1
ii  libgbm1   20.0.2-1
ii  libgl11.3.1-1
ii  libjack-jackd2-0 [libjack-0.125]  1.9.12~dfsg-2+b1
ii  libjpeg62-turbo   1:1.5.2-2+b1
ii  liblcms2-22.9-4+b1
ii  liblua5.2-0   5.2.4-1.1+b3
ii  libpulse0 13.0-5
ii  librubberband21.8.2-1
ii  libsdl2-2.0-0 2.0.10+dfsg1-2
ii  libsmbclient  2:4.11.5+dfsg-1+b1
ii  libsndio7.0   1.5.0-3
ii  libswresample37:4.2.2-1+b1
ii  libswscale5   7:4.2.2-1+b1
ii  libuchardet0  0.0.6-3
ii  libva-drm22.7.0~pre1-1
ii  libva-wayland22.7.0~pre1-1
ii  libva-x11-2   2.7.0~pre1-1
ii  libva22.7.0~pre1-1
ii  libvdpau1 1.3-1
ii  libwayland-client01.18.0-1
ii  libwayland-cursor01.18.0-1
ii  libwayland-egl1   1.18.0-1
ii  libx11-6  2:1.6.9-2
ii  libxext6  2:1.3.3-1+b2
ii  libxinerama1  2:1.1.4-2
ii  libxkbcommon0 0.10.0-1
ii  libxrandr22:1.5.1-1
ii  libxss1   1:1.2.3-1
ii  libxv12:1.0.11-1
ii  zlib1g1:1.2.11.dfsg-2

Versions of packages mpv recommends:
ii  xdg-utils   1.1.3-2
ii  youtube-dl  2020.01.24-0.1

mpv suggests no packages.

-- no debconf information

Bug#797733: Please support dynamically disabling audio pitch correction

[Josh Triplett]

Package: mpv
Version: 0.32.0-1
Followup-For: Bug #797733

Thank you, that addresses the issue for me.

It might be nice to have a default keybinding for that; I personally use
'\' as it lies next to '[' and ']'.

Bug#855203: The 2nd Notice

[thetrust]

After several failed attempts, we are reaching again you as regards the estate 
of our deceased client who made you one of the beneficiaries of his estate. Do 
get back to me at your earliest convenience. The Trustees
  

Bug#955272: libreoffice: unable to sign existing PDFs: foo.tmp doesn't exist

[John Scott]

Package: libreoffice
Version: 1:6.4.1-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Unlike #955271 which I just filed about digital signing, this issue doesn't
seem to arise out of the AppArmor profile.

 1. Open LibreOffice and navigate to File -> Digital Signatures -> Sign 
Existing PDF
 2. Choose a PDF, and in the Writer window that opens choose 'Sign Document'
 3. A message appears saying something like
'/home/john/Documents/lu97947ceyaav.tmp does not exist.'
and if one clicks OK, the dialog appears once more.

This issue appears in 1:6.4.2-2 also, and please do let me know if I
should explore some avenues for clues.

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

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

Versions of packages libreoffice depends on:
ii  libreoffice-base1:6.4.2-2
ii  libreoffice-calc1:6.4.2-2
ii  libreoffice-core1:6.4.2-2
ii  libreoffice-draw1:6.4.2-2
ii  libreoffice-impress 1:6.4.2-2
ii  libreoffice-math1:6.4.2-2
ii  libreoffice-report-builder-bin  1:6.4.2-2
ii  libreoffice-writer  1:6.4.2-2
ii  python3-uno 1:6.4.2-2

Versions of packages libreoffice recommends:
ii  fonts-crosextra-caladea 20130214-2
ii  fonts-crosextra-carlito 20130920-1
ii  fonts-dejavu2.37-1
ii  fonts-liberation1:1.07.4-11
ii  fonts-liberation2   2.1.0-1
ii  fonts-linuxlibertine5.3.0-4
ii  fonts-noto-core 20200103-3
ii  fonts-noto-extra20200103-3
ii  fonts-noto-mono 20200103-3
ii  fonts-noto-ui-core  20200103-3
ii  fonts-sil-gentium-basic 1.102-1
ii  libreoffice-java-common 1:6.4.2-2
ii  libreoffice-nlpsolver   0.9+LibO6.4.2-2
ii  libreoffice-report-builder  1:6.4.2-2
ii  libreoffice-script-provider-bsh 1:6.4.2-2
ii  libreoffice-script-provider-js  1:6.4.2-2
ii  libreoffice-script-provider-python  1:6.4.2-2
ii  libreoffice-sdbc-mysql  1:6.4.2-2
ii  libreoffice-sdbc-postgresql 1:6.4.2-2
ii  libreoffice-wiki-publisher  1.2.0+LibO6.4.2-2

Versions of packages libreoffice suggests:
ii  cups-bsd2.3.1-11
ii  default-jre [java8-runtime] 2:1.11-72
ii  firefox 72.0-1
ii  firefox-esr 68.6.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-2
ii  gstreamer1.0-plugins-good   1.16.2-2
ii  gstreamer1.0-plugins-ugly   1.16.2-2
ii  hunspell-en-us [hunspell-dictionary]1:2018.04.16-1
ii  hyphen-en-us [hyphen-hyphenation-patterns]  2.8.8-7
ii  imagemagick 8:6.9.10.23+dfsg-2.1+b2
ii  imagemagick-6.q16 [imagemagick] 8:6.9.10.23+dfsg-2.1+b2
ii  libgl1  1.3.1-1
pn  libofficebean-java  
pn  libreoffice-grammarcheck
ii  libreoffice-help-en-us [libreoffice-help]   1:6.4.2-2
pn  libreoffice-l10n
ii  libreoffice-librelogo   1:6.4.2-2
ii  libreoffice-plasma  1:6.4.2-2
ii  libsane 1.0.27-3.2+b1
ii  libxrender1 1:0.9.10-1
pn  myspell-dictionary  
ii  mythes-en-us [mythes-thesaurus] 1:6.4.0~rc2-1
pn  openclipart2-libreoffice | openclipart-libreoffice  
ii  openjdk-11-jre [java8-runtime]  11.0.6+10-2
ii  pstoedit3.75-1
pn  unixodbc

Versions of packages libreoffice-core depends on:
ii  fontconfig  2.13.1-2+b1
ii  fonts-opensymbol2:102.11+LibO6.4.2-2
ii  libboost-date-time1.71.01.71.0-6
ii  libboost-locale1.71.0   1.71.0-6
ii 

Bug#955271: libreoffice-common: AppArmor profile blocks gpg's tofu.db, causes hang opening Options

[John Scott]

Package: libreoffice-common
Version: 1:6.4.1-1
Severity: minor
User: pkg-apparmor-t...@lists.alioth.debian.org
Usertags: buggy-profile
Control: affects -1 gpg

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

The AppArmor profile doesn't allow reading GnuPG's tofu.db:
apparmor="DENIED" operation="file_lock" profile="libreoffice-soffice//gpg" 
name="/home/john/.gnupg/tofu.db" pid=94210 comm="gpg" requested_mask="k" 
denied_mask="k" fsuid=1000 ouid=1000

This does have a material impact. Opening Tools -> Options makes LibreOffice
and GnuPG hang indefinitely. The latter excessively uses the CPU, but
LibreOffice resumes when it is killed.

This is observed in 1:6.4.2-2 also. It's probably dependent on me using the
tofu trust model, and I'm not sure whether it would affect someone not having
this setting. Specifically, I have in my ~/.gnupg/gpg.conf
  trust-model tofu+pgp
and hopefully this is sufficient to reproduce the issue.

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

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

Versions of packages libreoffice-common depends on:
ii  libnumbertext-data 1.0.5-3
ii  libreoffice-style-colibre  1:6.4.2-2
ii  libreoffice-style-tango1:6.4.2-2
ii  ure1:6.4.2-2

Versions of packages libreoffice-common recommends:
ii  apparmor2.13.3-7
ii  fonts-liberation2   2.1.0-1
ii  libexttextcat-data  3.4.5-1
ii  python3-uno 1:6.4.2-2
ii  xdg-utils   1.1.3-2

Versions of packages libreoffice-common suggests:
ii  libreoffice-style-breeze [libreoffice-style]   1:6.4.2-2
ii  libreoffice-style-colibre [libreoffice-style]  1:6.4.2-2
ii  libreoffice-style-tango [libreoffice-style]1:6.4.2-2

Versions of packages python3-uno depends on:
ii  libc62.30-2
ii  libgcc-s110-20200324-1
ii  libpython3.8 3.8.2-1
ii  libreoffice-core 1:6.4.2-2
ii  libstdc++6   10-20200324-1
ii  libuno-cppu3 1:6.4.2-2
ii  libuno-cppuhelpergcc3-3  1:6.4.2-2
ii  libuno-sal3  1:6.4.2-2
ii  libuno-salhelpergcc3-3   1:6.4.2-2
ii  python3  3.8.2-2
ii  python3.83.8.2-1
ii  uno-libs-private 1:6.4.2-2
ii  ure  1:6.4.2-2

- -- Configuration Files:
/etc/apparmor.d/usr.lib.libreoffice.program.soffice.bin changed [not included]
 * I had set it to complain mode

- -- no debconf information

-BEGIN PGP SIGNATURE-

iHUEARYIAB0WIQT287WtmxUhmhucNnhyvHFIwKstpwUCXoACrQAKCRByvHFIwKst
p3MSAP0cz2FiDMFiCC4wbSnsvYZCqLDf81/dSPc1vWkiHqOVbwEAysYhder368UF
z1E6TeePMY9k2bb/tL3RUy+ftbyrEwU=
=Lg5N
-END PGP SIGNATURE-

Bug#955270: hurd: fails to update file mtime

[Thorsten Glaser]

Package: hurd
Version: 1:0.9.git20191228-1
Severity: normal

I first reported this on the mailing list:
https://lists.debian.org/debian-hurd/2020/03/msg00023.html

Now I logged in on the porterbox (exodar.debian.net) to try and
reproduce, and voilà, I can:

tg@exodar:~$ rm a b
tg@exodar:~$ :>a
tg@exodar:~$ sleep 1
tg@exodar:~$ :>b
tg@exodar:~$ stat a b | grep ^Mod
Modify: 2020-03-29 03:54:03.0 +0200
Modify: 2020-03-29 03:54:09.0 +0200
tg@exodar:~$ sleep 1
tg@exodar:~$ :>a
tg@exodar:~$ stat a b | grep ^Mod
Modify: 2020-03-29 03:54:03.0 +0200
Modify: 2020-03-29 03:54:09.0 +0200

For comparison, this is how it looks on GNU/Linux:

tglase@tglase-nb:~ $ rm a b
tglase@tglase-nb:~ $ :>a
tglase@tglase-nb:~ $ sleep 1
tglase@tglase-nb:~ $ :>b
tglase@tglase-nb:~ $ stat a b | grep ^Mod
Modify: 2020-03-29 03:58:04.989345171 +0200
Modify: 2020-03-29 03:58:05.993371946 +0200
tglase@tglase-nb:~ $ sleep 1
tglase@tglase-nb:~ $ :>a
tglase@tglase-nb:~ $ stat a b | grep ^Mod
Modify: 2020-03-29 03:58:07.001398828 +0200
Modify: 2020-03-29 03:58:05.993371946 +0200

Sub-second timestamps aside, you’ll notice how the first of the
two stat(1) lines updated. This is the common expectation for the
command true, redirected to a file.

Please reassign to the correct package, should I be mistaken.

-- System Information:
Debian Release: bullseye/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 'unstable')
Architecture: hurd-i386 (i686-AT386)

Kernel: GNU-Mach 1.8+git20191117-486-dbg/Hurd-0.9
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages hurd depends on:
ii  hurd-libs0.3   1:0.9.git20191228-1
ii  libblkid1  2.34-0.1
ii  libc0.32.29-10
ii  libdaemon0 0.14-7
ii  libgcrypt201.8.5-5
ii  liblwip0   2.1.2+dfsg1-6
ii  libncursesw6   6.2-1
ii  libpciaccess0  0.16-1+hurd.1
ii  libtinfo6  6.2-1
ii  libx11-6   2:1.6.9-2
ii  lsb-base   11.1.0
ii  sysv-rc2.96-2.1
ii  xkb-data   2.29-2

Versions of packages hurd recommends:
ii  bf-utf-source  0.08
ii  netdde 0.0.20150828-8

Versions of packages hurd suggests:
pn  hurd-doc  

-- no debconf information

Bug#954478: Acknowledgement (src:python-pbkdf2: Autopkgtest failure due to use of py3versions -i)

[Scott Kitterman]

I intend to upload an NMU to address this issue.  NMU diff attached.

Scott Kdiff -Nru python-pbkdf2-1.3+20110613.git2a0fb15~ds0/debian/changelog python-pbkdf2-1.3+20110613.git2a0fb15~ds0/debian/changelog
--- python-pbkdf2-1.3+20110613.git2a0fb15~ds0/debian/changelog	2019-12-23 16:51:11.0 -0500
+++ python-pbkdf2-1.3+20110613.git2a0fb15~ds0/debian/changelog	2020-03-28 17:45:23.0 -0400
@@ -1,3 +1,11 @@
+python-pbkdf2 (1.3+20110613.git2a0fb15~ds0-3.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix autopkgtest to reliably test all supported python3 versions (Closes:
+#954478)
+
+ -- Scott Kitterman   Sat, 28 Mar 2020 17:45:23 -0400
+
 python-pbkdf2 (1.3+20110613.git2a0fb15~ds0-3.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru python-pbkdf2-1.3+20110613.git2a0fb15~ds0/debian/tests/control python-pbkdf2-1.3+20110613.git2a0fb15~ds0/debian/tests/control
--- python-pbkdf2-1.3+20110613.git2a0fb15~ds0/debian/tests/control	2019-12-23 16:51:04.0 -0500
+++ python-pbkdf2-1.3+20110613.git2a0fb15~ds0/debian/tests/control	2020-03-28 17:45:23.0 -0400
@@ -1,2 +1,2 @@
 Tests: python3-pbkdf2
-Depends: python3-pbkdf2
+Depends: python3-all, python3-pbkdf2
diff -Nru python-pbkdf2-1.3+20110613.git2a0fb15~ds0/debian/tests/python3-pbkdf2 python-pbkdf2-1.3+20110613.git2a0fb15~ds0/debian/tests/python3-pbkdf2
--- python-pbkdf2-1.3+20110613.git2a0fb15~ds0/debian/tests/python3-pbkdf2	2013-07-05 16:07:24.0 -0400
+++ python-pbkdf2-1.3+20110613.git2a0fb15~ds0/debian/tests/python3-pbkdf2	2020-03-28 17:45:23.0 -0400
@@ -6,6 +6,6 @@
 cp -r test "$WORKDIR/"
 cd "$WORKDIR/"
 
-for python in $(py3versions -i); do
+for python in $(py3versions -s); do
PYTHONWARNINGS=d $python -m unittest discover -s test/ 2>&1
 done


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

Bug#954291: close the right bug

[Thorsten Glaser]

Oh, sorry, there was something.

Yes, the fix works. Thanks!

bye,
//mirabilos

Bug#207419: [bug-inetutils] Fwd: Bug#207419: SSL support

[Marcos Marado]

Hi there,

On Wed, 27 Aug 2003 17:35:47 + Robert Millan  wrote:
> On Wed, Aug 27, 2003 at 06:23:05PM +0300, Sergey Poznyakoff wrote:
> > Robert Millan  wrote:
> >
> > > I bet the BSD telnet-ssl uses libssl so we can't simply steal the code
> > > they non-copylefted for us [1].. shouldn't be hard to hack gtelnet for 
> > > using
> > > gnutls though. Any takers?
> >
> > OK, I'll add it to my TODO.
>
> nice, thanks.

AFAICS, this ended up never happening. However, someone else worked on a set
of patches that, supposedly, implement this: more info at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=143559 , if you wish to take a
look.

Best regards,
-- 
Marcos Marado

Bug#930534: Bug#930521: release.debian.org: provide machine-readable information about the freeze period for each release

[Paul Wise]

On Sat, 2020-03-28 at 22:21 +0100, Paul Gevers wrote:

> I have stripped some more from template in the other bug;

Looks good, but the quiet_period URL points at a buster mail.

> the first version should appear soon at
> https://release.debian.org/freeze-and-release-dates.yaml

I would suggest putting it at a per-release URL:

https://release.debian.org/bullseye/freeze-and-release-dates.yaml

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#932597: some sites with SSL don't work; reassigning to Qt

[John Scott]

Control: reassign -1 src:qtwebengine-opensource-src
Control: affects -1 konqueror kaccounts-config

I've now noticed this appears to affect kaccounts-config also. I'm still
unable to identify the specific cause of the bug, but my attempts to get
at it with gdb indicate the culprit is probably Qt (not necessarily
QtWebEngine).

I wonder if anyone else can reproduce this or would have a hint?

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

Bug#955269: RFS: gtk-chtheme/0.3.1-6.1 [NMU, RC] -- GTK+ 2.0 theme changer and previewer utility

[Sudip Mukherjee]

Package: sponsorship-requests
Severity: important

Dear mentors,

I am looking for a sponsor for my package "gtk-chtheme"

 * Package name: gtk-chtheme
   Version : 0.3.1-6.1
   Upstream Author : Aristotle Pagaltzis 
 * URL : http://plasmasturm.org/code/gtk-chtheme/
 * License : GPL-2
 * Vcs : None
   Section : x11

It builds those binary packages:

  gtk-chtheme - GTK+ 2.0 theme changer and previewer utility

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

  https://mentors.debian.net/package/gtk-chtheme

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

  dget -x 
https://mentors.debian.net/debian/pool/main/g/gtk-chtheme/gtk-chtheme_0.3.1-6.1.dsc

Changes since the last upload:

   * Non-maintainer upload.
   * Fix ftbfs with GCC. (Closes: #925710)


-- 
Regards
Sudip

Bug#925710: gtk-chtheme: diff for NMU version 0.3.1-6.1

[Sudip Mukherjee]

Control: tags 925710 + patch
Control: tags 925710 + pending

Dear maintainer,

I've prepared an NMU for gtk-chtheme (versioned as 0.3.1-6.1) and
uploaded it to mentors for sponsoring. Please feel free to tell me if I
should remove it.

--
Regards
Sudip

diff -Nru gtk-chtheme-0.3.1/debian/changelog gtk-chtheme-0.3.1/debian/changelog
--- gtk-chtheme-0.3.1/debian/changelog  2018-07-23 19:58:48.0 +0100
+++ gtk-chtheme-0.3.1/debian/changelog  2020-03-28 23:40:09.0 +
@@ -1,3 +1,10 @@
+gtk-chtheme (0.3.1-6.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix ftbfs with GCC. (Closes: #925710)
+
+ -- Sudip Mukherjee   Sat, 28 Mar 2020 23:40:09 
+
+
 gtk-chtheme (0.3.1-6) unstable; urgency=medium
 
   [ Helmut Grohne ]
diff -Nru gtk-chtheme-0.3.1/debian/patches/fix_ftbfs.patch 
gtk-chtheme-0.3.1/debian/patches/fix_ftbfs.patch
--- gtk-chtheme-0.3.1/debian/patches/fix_ftbfs.patch1970-01-01 
01:00:00.0 +0100
+++ gtk-chtheme-0.3.1/debian/patches/fix_ftbfs.patch2020-03-28 
23:35:24.0 +
@@ -0,0 +1,17 @@
+Description: Fix ftbfs with GCC
+
+Author: Sudip Mukherjee 
+
+---
+
+--- gtk-chtheme-0.3.1.orig/Makefile
 gtk-chtheme-0.3.1/Makefile
+@@ -18,7 +18,7 @@ EXTRAS = $(addprefix $(EXENAME), .spec .
+ all: $(EXENAME) $(EXENAME).1
+ 
+ $(EXENAME): $(addsuffix .o, $(SRC))
+-  $(CC) $(LDFLAGS) $^ -o $@
++  $(CC) $^ -o $@ $(LDFLAGS)
+ 
+ $(EXENAME).1: $(EXENAME).pod
+   pod2man $< | sed 's/^\.TH .*/.TH $(EXENAME) 1/' > $@
diff -Nru gtk-chtheme-0.3.1/debian/patches/series 
gtk-chtheme-0.3.1/debian/patches/series
--- gtk-chtheme-0.3.1/debian/patches/series 2018-07-23 19:58:48.0 
+0100
+++ gtk-chtheme-0.3.1/debian/patches/series 2020-03-28 23:34:21.0 
+
@@ -1,3 +1,4 @@
 backup-gtkrc-implementation.patch
 deprecated-on-gtk3+.patch
 cross.patch
+fix_ftbfs.patch

Bug#955268: udd watch: "429 too many requests" from GitHub

[Rebecca N. Palmer]

Package: qa.debian.org
User: qa.debian@packages.debian.org
Usertags: udd

Some packages have a dash in the watch column of 
qa.debian.org/developer.php and this error message on tracker.debian.org:


uscan had problems while searching for a new upstream version:

In watchfile debian/watch, reading webpage
  https://github.com/statsmodels/statsmodels/tags failed: 429 too many 
requests


Which packages have this error seems to vary over time, but it seems to 
be common (~50-90% of GitHub upstreams - e.g. see 
https://qa.debian.org/developer.php?email=pkg-go-maintainers%40lists.alioth.debian.org 
but note that a dash can also mean "no debian/watch" or another error).


I don't know if this was triggered by GitHub introducing/lowering their 
limit, by a bug on our end making more requests than we intended to, or 
by our generally increasing size.  (Currently 9490 GitHub-hosted 
packages each checked every 3 days, according to 
https://salsa.debian.org/qa/udd/-/blob/master/rimporters/upstream.rb#L174 
 and codesearch github\.com path:debian/watch.)

Bug#955268: udd watch: "429 too many requests" from GitHub

[Adam Borowski]

On Sat, Mar 28, 2020 at 11:00:51PM +, Rebecca N. Palmer wrote:
> In watchfile debian/watch, reading webpage
>   https://github.com/statsmodels/statsmodels/tags failed: 429 too many
> requests
> 
> Which packages have this error seems to vary over time, but it seems to be
> common (~50-90% of GitHub upstreams - e.g. see 
> https://qa.debian.org/developer.php?email=pkg-go-maintainers%40lists.alioth.debian.org
> but note that a dash can also mean "no debian/watch" or another error).
> 
> I don't know if this was triggered by GitHub introducing/lowering their
> limit, by a bug on our end making more requests than we intended to, or by
> our generally increasing size.  (Currently 9490 GitHub-hosted packages each
> checked every 3 days

IIRC with an access token the limit is 5000 queries per hour.  Without a
token, much, much less.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ in the beginning was the boot and root floppies and they were good.
⢿⡄⠘⠷⠚⠋⠀   --  on #linux-sunxi
⠈⠳⣄

Bug#941755: libclang1-10: Can't coinstall i386 and amd64 of libclang1-10

[Nicholas D Steeves]

Hi Gianfranco and Helmut,

On Sun, Feb 16, 2020 at 09:52:48AM +0100, Gianfranco Costamagna wrote:
> Hello, libclang1 has never been multiarch, because it shares files in 
> non-multiarch locations.
> 
> I don't think it is a trivial task to fix, but I think we can consider 
> patches!
> 

I noticed this:

  libclc/CMakeLists.txt
  4:include( GNUInstallDirs )

  clang/tools/scan-build/CMakeLists.txt
  3:include(GNUInstallDirs)

but I wonder if libclang's existing GNUInstallDirs support is broken
and/or incomplete, because--if I understand correctly what Lisandro
has told me about GNUInstallDirs--this module should provide the
correct triplet prefix automatically.

The following is also speculation, but maybe upstream's GNUInstallDirs
support isn't working properly because we don't follow the FHS/LSB/Red
Hat/SuSE convention?

  https://wiki.debian.org/Multiarch/TheCaseForMultiarch

Helmut, I've CCed you because I imagine the solution will be
immediately evident to you, because of all your work on cross building
:-)


Cheers,
Nicholas


signature.asc
Description: PGP signature

Bug#954287: libfiu: FTBFS on amd64/unstable: Segmentation fault (core dumped)

[Chris Lamb]

Hi Alberto,

> If you try the patch above, please let me know how it goes.

Works for me here — uploading now. :)


Best wishes,

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

Bug#955267: gnome-calendar: 'All Day' events are displayed over mutliple days within the month when viewed in Week View.

[Joe Aczel]

Package: gnome-calendar
Version: 3.36.0-1
Severity: important
Tags: upstream

Dear Maintainer,

Please note that this bug has been reported upstream:
https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/550

I am currently using Debian Testing (Bullseye) with the latest gnome-
calendar (3.36). When viewing my events in Week mode, events that are stored as
'All Day' span backwards across the month. E.g. an event saved as 'All Day' for
the 3rd of March will appear on the 1st, 2nd and 3rd of March.

   * What led up to the situation?
1) Installed Debian Testing
2) Opened gnome-calendar
3) Switched to week view
4) Created a new event by clicking on a time slot
5) Edit Details...
6) Selected 'All Day' toggle
7) Selected the 3rd of April
7) Entered a Title
8) Selected 'Done'
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
- I have attempted creating new events at different times of different
months. The same outcome occurs: the event will be visible in week view from
the first day of the month until the day the event takes place.
   * What was the outcome of this action?
Within Week View, the event will take place from either the first day
of the month. If the first day of the month is not visible within the currently
viewed week, the event will seem to take place from the first day of the week
until the time the event takes place.
   * What outcome did you expect instead?
The event will appear only on the day that the event takes place.

Please be aware that I have only reported a few bugs before. If you need any
technical information please be specific as to how I should go about obtaining
it.
If this bug does not need to be reported because it has already been reported
upstream please let me know and I can remove this bug report.

Joe



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

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

Versions of packages gnome-calendar depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.36.0-1
ii  gsettings-desktop-schemas3.36.0-1
ii  libc62.30-2
ii  libcairo21.16.0-4
ii  libdazzle-1.0-0  3.36.0-1
ii  libecal-2.0-13.36.0-1
ii  libedataserver-1.2-243.36.0-1
ii  libedataserverui-1.2-2   3.36.0-1
ii  libgeoclue-2-0   2.5.6-1
ii  libglib2.0-0 2.64.1-1
ii  libgoa-1.0-0b3.36.0-1
ii  libgtk-3-0   3.24.14-1
ii  libgweather-3-16 3.36.0-1
ii  libhandy-0.0-0   0.0.13-2
ii  libical3 3.0.8-1
ii  libpango-1.0-0   1.42.4-8
ii  libpangocairo-1.0-0  1.42.4-8
ii  libsoup2.4-1 2.70.0-1

Versions of packages gnome-calendar recommends:
ii  evolution-data-server  3.36.0-1

gnome-calendar suggests no packages.

-- no debconf information

Bug#937394: fixed in pybluez 0.22+really0.22-2

[Nobuhiro Iwamatsu]

Hi Moritz,

2020年3月28日(土) 3:38 Moritz Mühlenhoff :
>
> On Mon, Oct 21, 2019 at 01:34:11AM +, Nobuhiro Iwamatsu wrote:
> > Source: pybluez
> > Source-Version: 0.22+really0.22-2
> >
> > Format: 1.8
> > Date: Fri, 18 Oct 2019 16:59:51 +0900
> > Source: pybluez
> > Architecture: source
> > Version: 0.22+really0.22-2
> > Distribution: experimental
> > Urgency: medium
> > Maintainer: Debian Bluetooth Maintainers 
> > 
> > Changed-By: Nobuhiro Iwamatsu 
> > Closes: 937394
> > Changes:
> >  pybluez (0.22+really0.22-2) experimental; urgency=medium
> >  .
> >* Remove Python2 support (Closes: #937394)
>
> Hi Nobuhiro,
> there are now no longer any reverse dependencies of python-bluez in the 
> archive,
> can you please upload that version to unstable?

Oh,I forgot this. Thank you for telling this to me.
I will check immediately and upload if there is no problem.

>
> Cheers,
> Moritz

Best regards,
  Nobuhiro

-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6

Bug#955266: RFS: faifa/0.2~svn82-2 [QA] -- manage HomePlug 1.0/AV devices via ethernet frames

[Sudip Mukherjee]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name: faifa
   Version : 0.2~svn82-2
   Upstream Author : Xavier Carcelle 
 Nicolas Thill 
 Florian Fainelli 
 * URL : https://dev.open-plc.org/
 * License : GPL-2.0+
 * Vcs : https://salsa.debian.org/debian/faifa
   Section : net

It builds those binary packages:

  faifa - manage HomePlug 1.0/AV devices via ethernet frames
  libfaifa-dev - manage HomePlug 1.0/AV devices via ethernet frames - devel 
library
  libfaifa0 - manage HomePlug 1.0/AV devices via ethernet frames - library

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/f/faifa/faifa_0.2~svn82-2.dsc

Changes since the last upload:

   * QA upload.
   * Orphan the package. (See: #881004)
   * Update Standards-Version to 4.5.0
 - Change Priority to optional.
   * Update compat level to 12.
 - Install from multiarch directory.
   * Link libfaifa.so with libfaifa.so.0.
   * Install libfaifa.a in libfaifa-dev.
   * Add libfaifa0.symbols.
   * Add salsa as Vcs.
   * Use DEB_VERSION from dpkg.


-- 
Regards
Sudip

Bug#954856: Please add option to install signed grub bootloader

[Cyril Brulebois]

Ben Hutchings  (2020-03-28):
> It is definitely a bug that we automatically install shim-signed
> without grub-efi-amd64-signed.  That combination doesn't make any
> sense.

Bugs, bugs everywhere!

Feel free to file a separate bug if you want this to get tracked, but
I'm not sure I would spend time on it.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#954856: Please add option to install signed grub bootloader

[Ben Hutchings]

On Sat, 2020-03-28 at 22:50 +0100, Cyril Brulebois wrote:
> Hallo Bernhard,
> 
> Bernhard  (2020-03-28):
> > My system don't start in case of Secure Boot is enabled.
> > 
> > In Debian Wiki: https://wiki.debian.org/SecureBoot
> > The package grub-efi-amd64-signed is not installed.
> > This is a recommended package.
> > But this package is necessary for Secure Boot.
> > 
> > If i install a standard Debian installation, my system boot with Secure 
> > Boot.
> > With a standard Debian installation, the recommended packages will be 
> > installed also.
> 
> Oh, we do install grub-efi-amd64 which Depends: grub-efi-amd64-bin which
> itself Recommends: grub-efi-amd64-signed.
> 
> So either stop disabling Recommends (you're working against the default
> setting, you're supposed to be dealing with the consequences on your
> own), or additionally install grub-efi-amd64-signed through appropriate
> parameters in your preseed file.
> 
> This seems to me like a not-a-bug situation.

It is definitely a bug that we automatically install shim-signed
without grub-efi-amd64-signed.  That combination doesn't make any
sense.

Ben.

> Leaving this open for other members of the installer team to comment,
> but as far as I can tell, this bug report could likely be closed right
> away.
> 
> 
> Cheers,
-- 
Ben Hutchings
This sentence contradicts itself - no actually it doesn't.




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

Bug#955210: kernel-wedge: regression causes kfreebsd-10 FTBFS

[Ben Hutchings]

On Sat, 2020-03-28 at 13:41 +, Steven Chamberlain wrote:
[...]
>
kfreebsd-10 FTBFS, due to probably this change in kernel-wedge:
> 
https://salsa.debian.org/installer-team/kernel-wedge/-/commit/3827f1ee9f53540b104c592a8a2695f78d8629ed
[...]

On Sat, 2020-03-28 at 18:29 +, Steven Chamberlain wrote:
> tags -1 + patch
> thanks

Sorry about that.  I knew this was a relatively risky change, but
thought I had test cases covering everything.  Would you mind adding a
regression test for this case?

Ben.

-- 
Ben Hutchings
This sentence contradicts itself - no actually it doesn't.



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

Bug#878231: Upstream Seems Alive

[Eriberto Mota]

Thanks a lot for your help. The first link is down but the last URL is alive.

Regards,

Eriberto

Bug#955265: ITP: python-bel-resources -- Python3 utilities for BEL resource files

[Andreas Tille]

Package: wnpp
Severity: wishlist

Subject: ITP: python-bel-resources -- Python3 utilities for BEL resource files
Package: wnpp
Owner: Andreas Tille 
Severity: wishlist

* Package name: python-bel-resources
  Version : 0.0.3
  Upstream Author : Charles Tapley Hoyt
* URL : https://github.com/cthoyt/bel-resources
* License : MIT
  Programming Lang: Python
  Description : Python3 utilities for BEL resource files
 This package provides a Python3 interface and utilities
 for BEL resource files.

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

Bug#955264: librsvg: FTBFS on all architectures: needs to link with -lharfbuzz

[Andreas Beckmann]

Source: librsvg
Version: 2.48.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi,

librsvg/experimental FTBFS everywhere:
https://buildd.debian.org/status/package.php?p=librsvg&suite=experimental

/usr/bin/ld: test-utils.o: undefined reference to symbol 'hb_version_string'
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libharfbuzz.so.0: error adding symbols: 
DSO missing from command line


Andreas

Bug#955263: pbuilder: add --extra-depends option

[Andreas Beckmann]

Package: pbuilder
Version: 0.230.4
Severity: wishlist
Tags: patch

Hi,

it would be nice if pbuilder had an "--extra-depends" (or similar)
option to dynamically modify the build-depends of a package, e.g. for
testing transition rebuilds by requiring a package version from
experimental. The argument should allow anything that is also allowed in
d/control, i.e. comma-separated lists of packages with optional version
constraints in parentheses.
The --extrapackages option is not usable for this purpose, since it
does not allow specifying version constraints.

Attached patch is a proof-of-concept solution (successfully tested on
one package build for a transition test), it lacks documentation and
tests.

One could also look how sbuild does this.

Andreas
>From 478d4374f648d1925d9ffeadcf5f900120d9b3b3 Mon Sep 17 00:00:00 2001
From: Andreas Beckmann 
Date: Sat, 28 Mar 2020 00:15:38 +0100
Subject: [PATCH] add --extra-depends option

---
 pbuilder-buildpackage-funcs | 1 +
 pbuilder-checkparams| 4 
 pbuilder-satisfydepends-checkparams | 5 +
 pbuilder-satisfydepends-funcs   | 3 ++-
 4 files changed, 12 insertions(+), 1 deletion(-)

diff --git a/pbuilder-buildpackage-funcs b/pbuilder-buildpackage-funcs
index 59600908..ae776d1f 100644
--- a/pbuilder-buildpackage-funcs
+++ b/pbuilder-buildpackage-funcs
@@ -115,6 +115,7 @@ function checkbuilddep () {
 --control "$control" \
 --chroot "${BUILDPLACE}" \
 --internal-chrootexec "${CHROOTEXEC}" \
+${EXTRA_DEPENDS:+--extra-depends "${EXTRA_DEPENDS}"} \
 "${BUILDOPT}" \
 "${PBUILDERSATISFYDEPENDSOPT[@]}"); \
 then
diff --git a/pbuilder-checkparams b/pbuilder-checkparams
index a5ea5c7c..ea976f32 100755
--- a/pbuilder-checkparams
+++ b/pbuilder-checkparams
@@ -173,6 +173,10 @@ while [ -n "$1" ]; do
 EXTRA_CONFIGFILE[${#EXTRA_CONFIGFILE[@]}]="$2";
 shift; shift;
 ;;
+--extra-depends)
+EXTRA_DEPENDS="${EXTRA_DEPENDS:+$EXTRA_DEPENDS, }$2";
+shift; shift;
+;;
 --extrapackages)
 EXTRAPACKAGES="${EXTRAPACKAGES:+$EXTRAPACKAGES }$2";
 shift; shift;
diff --git a/pbuilder-satisfydepends-checkparams 
b/pbuilder-satisfydepends-checkparams
index 6f7e3846..f8a28781 100755
--- a/pbuilder-satisfydepends-checkparams
+++ b/pbuilder-satisfydepends-checkparams
@@ -31,6 +31,7 @@ CONTINUE_FAIL="no"
 CHROOTEXEC_AFTER_INTERNAL_CHROOTEXEC=no
 ALLOWUNTRUSTED=no
 EATMYDATA=no
+EXTRA_DEPENDS=""
 
 while [ -n "$1" ]; do
 case "$1" in
@@ -101,6 +102,10 @@ while [ -n "$1" ]; do
 HOST_ARCH=$2
 shift 2
 ;;
+--extra-depends)
+EXTRA_DEPENDS=$2
+shift 2
+;;
--help|-h|*)
print_help
exit 1
diff --git a/pbuilder-satisfydepends-funcs b/pbuilder-satisfydepends-funcs
index d64e9a95..c710187e 100755
--- a/pbuilder-satisfydepends-funcs
+++ b/pbuilder-satisfydepends-funcs
@@ -103,7 +103,8 @@ p'
 get_build_deps() {
 local output
 
-output="$(get_build_depends_field "Build-Depends")"
+output="${EXTRA_DEPENDS}"
+output="${output:+$output, }$(get_build_depends_field "Build-Depends")"
 output="${output%, }"
 case "$BINARY_ARCH" in
 any)
-- 
2.20.1

Bug#955262: ITP: python-multisplitby -- split an iterable into multiple using arbitrary predicates

[Andreas Tille]

Package: wnpp
Severity: wishlist

Subject: ITP: python-multisplitby -- split an iterable into multiple using 
arbitrary predicates
Package: wnpp
Owner: Andreas Tille 
Severity: wishlist

* Package name: python-multisplitby
  Version : 0.0.1
  Upstream Author : Charles Tapley Hoyt
* URL : https://github.com/cthoyt/multisplitby
* License : MIT
  Programming Lang: Python
  Description : split an iterable into multiple using arbitrary predicates
 This package provides a Python3 module to split an iterable into multiple
 using arbitrary predicates.  It comes with a single function:
 multisplitby.multi_split_by.

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

Bug#954253: python3-pybel: Missing dependency on unpackaged bel_resources

[Andreas Tille]

Hi Adrian,

thanks for this bug report.

On Thu, Mar 19, 2020 at 12:50:12PM +0200, Adrian Bunk wrote:
> ModuleNotFoundError: No module named 'bel_resources'

Initial packaging for python3-bel-resources is commited at
   https://salsa.debian.org/med-team/python-bel-resources

Kind regards

 Andreas.

-- 
http://fam-tille.de

Bug#955261: pcsc-tools: gscriptor causes GUI stack to be installed on headless server

[Jeremy Jackson]

Package: pcsc-tools
Version: 1.5.4-1
Severity: normal

Dear Maintainer,

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

   * What led up to the situation?
I was cleaning unnecessary packages off the server, but pcsc_scan is a basic 
troubleshooting tool for SmartCard support on a system, such as a Certificate 
Authority (CA)
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 I tried to remove all GUI x11/wayland packages.
   * What was the outcome of this action?
 Cleanup caused it to be removed due to dependency on libgtk3-perl
   * What outcome did you expect instead?
   A separate package for gscriptor component would be one opiton, to allow 
headless servers and embedded systems to omit GUI packages.

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


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

Kernel: Linux 4.19.0-8-amd64 (SMP w/1 CPU core)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=en_CA, LC_CTYPE=en_CA (charmap=ISO-8859-1), LANGUAGE=en_CA 
(charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages pcsc-tools depends on:
ii  libc6 2.28-10
pn  libgtk3-perl  
ii  libpcsc-perl  1.4.14-4+b1
ii  libpcsclite1  1.8.24-1

pcsc-tools recommends no packages.

pcsc-tools suggests no packages.

-- no debconf information

Bug#955210: kernel-wedge: regression causes kfreebsd-10 FTBFS

[Cyril Brulebois]

Hi Steven,

Steven Chamberlain  (2020-03-28):
> tags -1 + patch
> thanks

Feel free to push/upload as you see fit; thanks.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#954856: Please add option to install signed grub bootloader

[Cyril Brulebois]

Hallo Bernhard,

Bernhard  (2020-03-28):
> My system don't start in case of Secure Boot is enabled.
> 
> In Debian Wiki: https://wiki.debian.org/SecureBoot
> The package grub-efi-amd64-signed is not installed.
> This is a recommended package.
> But this package is necessary for Secure Boot.
> 
> If i install a standard Debian installation, my system boot with Secure Boot.
> With a standard Debian installation, the recommended packages will be 
> installed also.

Oh, we do install grub-efi-amd64 which Depends: grub-efi-amd64-bin which
itself Recommends: grub-efi-amd64-signed.

So either stop disabling Recommends (you're working against the default
setting, you're supposed to be dealing with the consequences on your
own), or additionally install grub-efi-amd64-signed through appropriate
parameters in your preseed file.

This seems to me like a not-a-bug situation.

Leaving this open for other members of the installer team to comment,
but as far as I can tell, this bug report could likely be closed right
away.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#954220: dialog: program aborts on resize (not fixed by 1.3-20190808-1)

[Thomas Dickey]

fixed in dialog 1.3 20200327

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


signature.asc
Description: PGP signature

Bug#954185: dialog: backtitle disappears on resize

[Thomas Dickey]

fixed in dialog 1.3 20200327

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


signature.asc
Description: PGP signature

Bug#954856: Please add option to install signed grub bootloader

[Bernhard]

Hello Cyril

My system don't start in case of Secure Boot is enabled.

In Debian Wiki: https://wiki.debian.org/SecureBoot
The package grub-efi-amd64-signed is not installed.
This is a recommended package.
But this package is necessary for Secure Boot.

If i install a standard Debian installation, my system boot with Secure Boot.
With a standard Debian installation, the recommended packages will be installed 
also.

Please let me know, if you need further informations.

Best regards
Bernhard


Am Samstag, den 28.03.2020, 21:51 +0100 schrieb Cyril Brulebois:
> Hallo wieder,
> 
> Bernhard  (2020-03-28):
> > Hello Cyril
> > 
> > Thank you for feedback.
> > Attached, there is the Syslog.
> 
> Thanks.
> 
> Then I think I'm not sure your bug report is correct:
> 
> Mar 20 08:07:18 in-target: Paketlisten werden gelesen...
> Mar 20 08:07:18 in-target:
> Mar 20 08:07:18 in-target: Abhängigkeitsbaum wird aufgebaut
> Mar 20 08:07:18 in-target:
> Mar 20 08:07:18 in-target: Statusinformationen werden eingelesen
> Mar 20 08:07:18 in-target:
> Mar 20 08:07:18 in-target: Die folgenden zusätzlichen Pakete werden 
> installiert:
> Mar 20 08:07:18 in-target:   grub-efi-amd64-bin grub2-common
> Mar 20 08:07:18 in-target: Empfohlene Pakete:
> Mar 20 08:07:18 in-target:   grub-efi-amd64-signed
> Mar 20 08:07:18 in-target: Die folgenden NEUEN Pakete werden installiert:
> Mar 20 08:07:18 in-target:   grub-efi-amd64 grub-efi-amd64-bin 
> grub2-common
> Mar 20 08:07:18 in-target: 0 aktualisiert, 3 neu installiert, 0 zu 
> entfernen und 0 nicht aktualisiert.
> Mar 20 08:07:18 in-target: Es müssen 1.243 kB an Archiven heruntergeladen 
> werden.
> Mar 20 08:07:18 in-target: Nach dieser Operation werden 9.393 kB 
> Plattenplatz zusätzlich benutzt.
> Mar 20 08:07:18 in-target: Holen:1 http://192.168.178.2/debian 
> buster/main amd64 grub2-common amd64 2.02+dfsg1-20 [538 kB]
> Mar 20 08:07:18 in-target: Holen:2 http://192.168.178.2/debian 
> buster/main amd64 grub-efi-amd64-bin amd64 2.02+dfsg1-20 [665 kB
> […]
> Mar 20 08:07:25 grub-installer: info: Additionally installing shim-signed 
> to go with grub-efi-amd64
> Mar 20 08:07:25 in-target: Paketlisten werden gelesen...
> Mar 20 08:07:25 in-target:
> Mar 20 08:07:25 in-target: Abhängigkeitsbaum wird aufgebaut
> Mar 20 08:07:25 in-target:
> Mar 20 08:07:25 in-target: Statusinformationen werden eingelesen
> Mar 20 08:07:25 in-target:
> Mar 20 08:07:25 in-target: Die folgenden zusätzlichen Pakete werden 
> installiert:
> Mar 20 08:07:25 in-target:   mokutil shim-helpers-amd64-signed 
> shim-signed-common shim-unsigned
> Mar 20 08:07:25 in-target: Empfohlene Pakete:
> Mar 20 08:07:25 in-target:   secureboot-db
> Mar 20 08:07:25 in-target: Die folgenden NEUEN Pakete werden installiert:
> Mar 20 08:07:25 in-target:   mokutil shim-helpers-amd64-signed 
> shim-signed shim-signed-common
> Mar 20 08:07:25 in-target:   shim-unsigned
> Mar 20 08:07:25 in-target: 0 aktualisiert, 5 neu installiert, 0 zu 
> entfernen und 0 nicht aktualisiert.
> Mar 20 08:07:25 in-target: Es müssen 1.380 kB an Archiven heruntergeladen 
> werden.
> Mar 20 08:07:25 in-target: Nach dieser Operation werden 7.743 kB 
> Plattenplatz zusätzlich benutzt.
> Mar 20 08:07:25 in-target: Holen:1 http://192.168.178.2/debian 
> buster/main amd64 mokutil amd64 0.3.0+1538710437.fb6250f-1 [22,6 kB]
> Mar 20 08:07:25 in-target: Holen:2 http://192.168.178.2/debian 
> buster/main amd64 shim-unsigned amd64 15+1533136590.3beb971-7 [579 kB]
> Mar 20 08:07:25 in-target: Holen:3 http://192.168.178.2/debian 
> buster/main amd64 shim-helpers-amd64-signed amd64 1+15+1533136590.3beb971+7 
> [431 kB]
> Mar 20 08:07:25 in-target: Holen:4 http://192.168.178.2/debian 
> buster/main amd64 shim-signed-common all 1.33+15+1533136590.3beb971-7 [13,3 
> kB]
> Mar 20 08:07:25 in-target: Holen:5 http://192.168.178.2/debian 
> buster/main amd64 shim-signed amd64 1.33+15+1533136590.3beb971-7 [335 kB]
> 
> so you should have all needed bits to have Secure Boot up and running.
> 
> See
> https://debamax.com/blog/2019/04/19/an-overview-of-secure-boot-in-debian/
> for some overview on Debian vs. Secure Boot, including bits about GRUB
> packages.
> 
> 
> Cheers,


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

Bug#947672: lists.debian.org: Javier Serrano Polo is banned

[Javier Serrano Polo]

Empty words from a politician.

smime.p7s
Description: S/MIME cryptographic signature

Bug#953760: check-service autopkgtest fails while parsing systemctl output

[Bernd Zeimetz]

Hi,

just uploaded.

Sorry for the delay!


Bernd


On 3/28/20 8:36 AM, Michael Biebl wrote:
> Hi Bernd
> 
> On Fri, 13 Mar 2020 03:03:25 +0100 Michael Biebl  wrote:
>>
>> the autopkgtest shipped by gpsd fails with the latest systemd v245
>> version:
>>
> 
> As autopkgtest results are used nowadays to gate testing migration, this
> issue now blocks systemd from entering testing. Do you have any plans to
> upload gpsd with a fix in the near future?
> 
> Michael
> 

-- 
 Bernd ZeimetzDebian GNU/Linux Developer
 http://bzed.dehttp://www.debian.org
 GPG Fingerprint: ECA1 E3F2 8E11 2432 D485  DD95 EB36 171A 6FF9 435F



signature.asc
Description: OpenPGP digital signature

Bug#936239: brian: Python2 removal in sid/bullseye

[Andreas Beckmann]

Followup-For: Bug #936239
Control: severity -1 serious

src:brian's Build-Depends are no longer satisfiable in sid:

The following packages have unmet dependencies:
 builddeps:brian : Depends: python-matplotlib (>= 0.90.1) but it is not 
installable
   Depends: python-scipy (>= 0.7.0) but it is not installable
   Depends: python-sympy but it is not installable
   Depends: python-sphinx but it is not going to be installed

Andreas

Bug#955256: RFS: minidb/2.0.3-1

[Adam Borowski]

On Sat, Mar 28, 2020 at 08:15:21PM +0100, Maxime Werlen wrote:
> * Package name: minidb
>   Version : 2.0.3-1

> minidb (2.0.3-1) unstable; urgency=medium
> 
>   * New upstream version 2.0.3 (Closes: #955221)
>   * Update Standards version to 4.5.0
>   * Update debhelper compat to version 12
>   * Configured to use gbp

Hi!
I'm afraid the package fails to build its source:

dh clean --with python3 --buildsystem=pybuild
dh: error: unable to load addon python3: Can't locate 
Debian/Debhelper/Sequence/python3.pm in @INC (you may need to install the 
Debian::Debhelper::Sequence::python3 module) (@INC contains: /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.30.0 /usr/local/share/perl/5.30.0 
/usr/lib/x86_64-linux-gnu/perl5/5.30 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.30 /usr/share/perl/5.30 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at (eval 12) line 
1.
BEGIN failed--compilation aborted at (eval 12) line 1.

The cause is missing Build-Depends on dh-python.  It's included in
B-D-Indep, but the "clean" target installs only base B-D.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ in the beginning was the boot and root floppies and they were good.
⢿⡄⠘⠷⠚⠋⠀   --  on #linux-sunxi
⠈⠳⣄

Bug#954856: Please add option to install signed grub bootloader

[Cyril Brulebois]

Hallo wieder,

Bernhard  (2020-03-28):
> Hello Cyril
> 
> Thank you for feedback.
> Attached, there is the Syslog.

Thanks.

Then I think I'm not sure your bug report is correct:

Mar 20 08:07:18 in-target: Paketlisten werden gelesen...
Mar 20 08:07:18 in-target:
Mar 20 08:07:18 in-target: Abhängigkeitsbaum wird aufgebaut
Mar 20 08:07:18 in-target:
Mar 20 08:07:18 in-target: Statusinformationen werden eingelesen
Mar 20 08:07:18 in-target:
Mar 20 08:07:18 in-target: Die folgenden zusätzlichen Pakete werden 
installiert:
Mar 20 08:07:18 in-target:   grub-efi-amd64-bin grub2-common
Mar 20 08:07:18 in-target: Empfohlene Pakete:
Mar 20 08:07:18 in-target:   grub-efi-amd64-signed
Mar 20 08:07:18 in-target: Die folgenden NEUEN Pakete werden installiert:
Mar 20 08:07:18 in-target:   grub-efi-amd64 grub-efi-amd64-bin grub2-common
Mar 20 08:07:18 in-target: 0 aktualisiert, 3 neu installiert, 0 zu 
entfernen und 0 nicht aktualisiert.
Mar 20 08:07:18 in-target: Es müssen 1.243 kB an Archiven heruntergeladen 
werden.
Mar 20 08:07:18 in-target: Nach dieser Operation werden 9.393 kB 
Plattenplatz zusätzlich benutzt.
Mar 20 08:07:18 in-target: Holen:1 http://192.168.178.2/debian buster/main 
amd64 grub2-common amd64 2.02+dfsg1-20 [538 kB]
Mar 20 08:07:18 in-target: Holen:2 http://192.168.178.2/debian buster/main 
amd64 grub-efi-amd64-bin amd64 2.02+dfsg1-20 [665 kB
[…]
Mar 20 08:07:25 grub-installer: info: Additionally installing shim-signed 
to go with grub-efi-amd64
Mar 20 08:07:25 in-target: Paketlisten werden gelesen...
Mar 20 08:07:25 in-target:
Mar 20 08:07:25 in-target: Abhängigkeitsbaum wird aufgebaut
Mar 20 08:07:25 in-target:
Mar 20 08:07:25 in-target: Statusinformationen werden eingelesen
Mar 20 08:07:25 in-target:
Mar 20 08:07:25 in-target: Die folgenden zusätzlichen Pakete werden 
installiert:
Mar 20 08:07:25 in-target:   mokutil shim-helpers-amd64-signed 
shim-signed-common shim-unsigned
Mar 20 08:07:25 in-target: Empfohlene Pakete:
Mar 20 08:07:25 in-target:   secureboot-db
Mar 20 08:07:25 in-target: Die folgenden NEUEN Pakete werden installiert:
Mar 20 08:07:25 in-target:   mokutil shim-helpers-amd64-signed shim-signed 
shim-signed-common
Mar 20 08:07:25 in-target:   shim-unsigned
Mar 20 08:07:25 in-target: 0 aktualisiert, 5 neu installiert, 0 zu 
entfernen und 0 nicht aktualisiert.
Mar 20 08:07:25 in-target: Es müssen 1.380 kB an Archiven heruntergeladen 
werden.
Mar 20 08:07:25 in-target: Nach dieser Operation werden 7.743 kB 
Plattenplatz zusätzlich benutzt.
Mar 20 08:07:25 in-target: Holen:1 http://192.168.178.2/debian buster/main 
amd64 mokutil amd64 0.3.0+1538710437.fb6250f-1 [22,6 kB]
Mar 20 08:07:25 in-target: Holen:2 http://192.168.178.2/debian buster/main 
amd64 shim-unsigned amd64 15+1533136590.3beb971-7 [579 kB]
Mar 20 08:07:25 in-target: Holen:3 http://192.168.178.2/debian buster/main 
amd64 shim-helpers-amd64-signed amd64 1+15+1533136590.3beb971+7 [431 kB]
Mar 20 08:07:25 in-target: Holen:4 http://192.168.178.2/debian buster/main 
amd64 shim-signed-common all 1.33+15+1533136590.3beb971-7 [13,3 kB]
Mar 20 08:07:25 in-target: Holen:5 http://192.168.178.2/debian buster/main 
amd64 shim-signed amd64 1.33+15+1533136590.3beb971-7 [335 kB]

so you should have all needed bits to have Secure Boot up and running.

See
https://debamax.com/blog/2019/04/19/an-overview-of-secure-boot-in-debian/
for some overview on Debian vs. Secure Boot, including bits about GRUB
packages.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#955260: libkqueue: fails to build on most my boxes

[Adam Borowski]

Source: libkqueue
Version: 2.0.3-1.2
Severity: important
Tags: ftbfs
Justification: fails to build from source

Hi!
I've just uploaded Sudip's NMU to fix a FTBFS, but the package fails its
testsuite on most machines I tried:

✗ 64-thread 2990WX, kernel 5.6.0-rc6-00085-ge6fd0e58416e 
✗ 6-core Phenom 2, kernels:
5.5.13-00041-g677eee050e0c
4.19-0-8 (packaged, buster)
4.18.0-rc1-cjk-debug-00028-g91e4a47950da
✓ 4-thread Braswell, kernel 4.19-0-8 (packaged, buster)
✗ 8-thread Skylake, kernel 5.5.13-00032-g845e62e65337
✓ barriere.d.n: 4-vthread 4.19-0-8 (packaged, buster)

All of these but barriere have exactly the same sbuild setup;
DEB_BUILD_OPTIONS=parallel=1 doesn't help so it's not a matter of
parallelism.


FAIL: kqtest


/usr/lib/x86_64-linux-gnu/libeatmydata.so(+0x53c)[0x7fa774e5353c]
[0x3a]
[0x3a]
[0x5340d]
[0x1]
[0x81a4]
[0x0]
[0x0]
[0x3900]
[0x0]
[0x63]
[0x5e7d2f44]
[0x0]
[0x5e7b5518]
[0x0]
[0x1000]
[0x1c745ce6]
[0x0]
[0x0]
[0x40]
[0x700101]
[0x0]
[0x1]
[0x8]
[0x77007c]
[0x63006f]
[0x0]
[0xff]
[0x1000]
[0xca88]
/lib/x86_64-linux-gnu/libc.so.6(_IO_file_jumps+0x0)[0x7fa774e1d4a0]
[0x8]
Running 1 iterations
1: test_peer_close_detection()  
2: test_kqueue()
3: test_kevent()
4: test_ev_receipt()
5: test_kevent_socket_add() 
6: test_kevent_socket_del() 
7: test_kevent_socket_add_without_ev_add()  
8: test_kevent_socket_get() 
9: test_kevent_socket_disable_and_enable()  
10: test_kevent_socket_oneshot()
11: test_kevent_socket_clear()  
12: test_kevent_socket_dispatch()   
13: test_kevent_socket_listen_backlog() 
14: test_kevent_socket_eof()
15: test_kevent_regular_file()  
* ERROR: Program received signal 6 *
 *** TEST FAILED ***
FAIL kqtest (exit status: 1)


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

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

Bug#922553: Bug #922553: Make link to the last release point announcement in the index page of each release, fix 2

[Laura Arjona Reina]

Applied, thanks!

I have added (empty) tags for bullseye and bookworm releases, so we
remember to update them when we publish those releases :-)

Now, I think the only remaining thing is to sync translations.

Kind regards,

-- 
Laura Arjona Reina
https://wiki.debian.org/LauraArjona

Bug#955259: libjcat: Please add consider adding autopkgtest coverage

[Simon McVittie]

Source: libjcat
Version: 0.1.0-1
Severity: wishlist
Tags: patch
Control: block -1 by 955258

I noticed that libjcat has GNOME-style installed-tests, which in principle
make it easy to add autopkgtest coverage, so I tried to contribute a
trivial patch to do so. Unfortunately, the installed-tests don't actually
work when run installed (they rely on the original source tree), so it
turned out to be less trivial than I'd hoped.

I've attached patches, but the patch added in debian/patches should probably
be discussed with upstream. As well as making the test pass, it also fixes a
source of non-reproducibility.

For it to pass, the test for libjcat-dev requires the patches I attached
to #955258.

smcv
>From c33068507c34a1416ee023f4064f19015f9b9c75 Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Sat, 28 Mar 2020 17:37:36 +
Subject: [PATCH 7/9] Install test data so that the installed-tests can pass

---
 ...est-data-next-to-the-test-executable.patch | 273 ++
 debian/patches/series |   1 +
 2 files changed, 274 insertions(+)
 create mode 100644 debian/patches/Install-test-data-next-to-the-test-executable.patch

diff --git a/debian/patches/Install-test-data-next-to-the-test-executable.patch b/debian/patches/Install-test-data-next-to-the-test-executable.patch
new file mode 100644
index 000..6a8d473
--- /dev/null
+++ b/debian/patches/Install-test-data-next-to-the-test-executable.patch
@@ -0,0 +1,273 @@
+From: Simon McVittie 
+Date: Sat, 28 Mar 2020 17:35:46 +
+Subject: Install test data next to the test executable
+
+This is conventional for GNOME-style installed-tests, and lets us find
+it with g_test_build_filename() (which uses the G_TEST_SRCDIR and
+G_TEST_BUILDDIR environment variables, or looks near the executable).
+
+The environment variables avoiding the need to hard-code the
+build directory into the test executable, which isn't suitable for
+reproducible builds.
+
+Signed-off-by: Simon McVittie 
+---
+ data/tests/colorhug/meson.build |  5 +++--
+ data/tests/meson.build  |  5 +
+ data/tests/pki/meson.build  |  6 ++
+ libjcat/jcat-self-test.c| 40 
+ libjcat/meson.build | 13 -
+ 5 files changed, 42 insertions(+), 27 deletions(-)
+
+diff --git a/data/tests/colorhug/meson.build b/data/tests/colorhug/meson.build
+index 1851fbf..475bf46 100644
+--- a/data/tests/colorhug/meson.build
 b/data/tests/colorhug/meson.build
+@@ -1,8 +1,9 @@
+ install_data([
+ 'firmware.bin',
+ 'firmware.bin.asc',
++'firmware.bin.p7b',
+   ],
+-  install_dir: installed_test_datadir,
++  install_dir: installed_test_bindir / 'colorhug',
+ )
+ 
+ if get_option('pkcs7')
+@@ -17,6 +18,6 @@ if get_option('pkcs7')
+ '--infile', '@INPUT@',
+ '--outfile', '@OUTPUT@'],
+ install: true,
+-install_dir: installed_test_datadir,
++install_dir: installed_test_bindir / 'colorhug',
+   )
+ endif
+diff --git a/data/tests/meson.build b/data/tests/meson.build
+index 5bfca03..617edf2 100644
+--- a/data/tests/meson.build
 b/data/tests/meson.build
+@@ -15,5 +15,10 @@ pkcs7_privkey = custom_target('test-privkey.pem',
+ subdir('pki')
+ subdir('colorhug')
+ 
++install_data(
++  'meson.build',
++  install_dir: installed_test_bindir,
++)
++
+ testdatadir_src = meson.current_source_dir()
+ testdatadir_dst = meson.current_build_dir()
+diff --git a/data/tests/pki/meson.build b/data/tests/pki/meson.build
+index f35f2a9..f5bf31d 100644
+--- a/data/tests/pki/meson.build
 b/data/tests/pki/meson.build
+@@ -7,4 +7,10 @@ pkcs7_certificate = custom_target('test.pem',
+   '--template', pkcs7_config,
+   '--load-privkey', '@INPUT@',
+   '--outfile', '@OUTPUT@'],
++  install_dir: installed_test_bindir / 'pki',
++)
++install_data(
++  'GPG-KEY-Linux-Vendor-Firmware-Service',
++  'LVFS-CA.pem',
++  install_dir: installed_test_bindir / 'pki',
+ )
+diff --git a/libjcat/jcat-self-test.c b/libjcat/jcat-self-test.c
+index 7c3558b..f7a8375 100644
+--- a/libjcat/jcat-self-test.c
 b/libjcat/jcat-self-test.c
+@@ -216,7 +216,7 @@ jcat_sha1_engine_func (void)
+ 	g_assert_cmpint (jcat_engine_get_verify_kind (engine), ==, JCAT_ENGINE_VERIFY_KIND_CHECKSUM);
+ 
+ 	/* verify checksum */
+-	fn_pass = g_build_filename (TESTDATADIR_SRC, "colorhug", "firmware.bin", NULL);
++	fn_pass = g_test_build_filename (G_TEST_DIST, "colorhug", "firmware.bin", NULL);
+ 	data_fwbin = jcat_get_contents_bytes (fn_pass, &error);
+ 	g_assert_no_error (error);
+ 	g_assert_nonnull (data_fwbin);
+@@ -230,7 +230,7 @@ jcat_sha1_engine_func (void)
+ 	g_assert_cmpstr (jcat_result_get_authority (result_pass), ==, NULL);
+ 
+ 	/* verify will fail */
+-	fn_fail = g_build_filename (TESTDATADIR_SRC, "meson.build",NULL);
++	fn_fail = g_test_build_filename (G_TEST_DIST, "meson.build",NULL);
+ 	data_fail = jcat_get_contents_bytes (fn_fail,

Bug#955258: libjcat-dev: -dev package missing some required dependencies

[Simon McVittie]

Package: libjcat-dev
Version: 0.1.0-1
Severity: important
Tags: patch

I tried adding some basic autopkgtests to libjcat. One useful thing to do
in an autopkgtest for a library is to compile a "hello world" program
against the library. This often reveals missing -dev dependencies,
and in the case of libjcat that's exactly what happened.

Please see attached.

smcv
>From 33144e96f92834fc96b23f5a7fd40ba70859dd7b Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Sat, 28 Mar 2020 17:15:31 +
Subject: [PATCH 4/9] libjcat-dev: Add missing -dev dependencies

Without these, building a trivial program against libjcat fails with
errors like:

+ pkg-config --cflags --libs jcat
Package gio-2.0 was not found in the pkg-config search path.

Signed-off-by: Simon McVittie 
---
 debian/control | 8 +++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/debian/control b/debian/control
index 7790953..fdecfbf 100644
--- a/debian/control
+++ b/debian/control
@@ -41,7 +41,13 @@ Section: libdevel
 Architecture: any
 Multi-Arch: same
 Pre-Depends: ${misc:Pre-Depends}
-Depends: ${misc:Depends}, ${shlibs:Depends}, gir1.2-jcat-1.0 (= ${binary:Version})
+Depends: ${misc:Depends},
+ ${shlibs:Depends},
+ gir1.2-jcat-1.0 (= ${binary:Version}),
+ gnutls-dev,
+ libglib2.0-dev,
+ libgpgme11-dev,
+ libjson-glib-dev,
 Description: development files for libjcat
  This package provides development libraries for libjcat.
  .
-- 
2.26.0

>From 35d9f740892e63c76cf77246643ca246b86b1ce8 Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Sat, 28 Mar 2020 19:40:15 +
Subject: [PATCH 5/9] libjcat-dev: Add missing dependency on a matching
 libjcat1

Signed-off-by: Simon McVittie 
---
 debian/control | 1 +
 1 file changed, 1 insertion(+)

diff --git a/debian/control b/debian/control
index fdecfbf..9dff12e 100644
--- a/debian/control
+++ b/debian/control
@@ -47,6 +47,7 @@ Depends: ${misc:Depends},
  gnutls-dev,
  libglib2.0-dev,
  libgpgme11-dev,
+ libjcat1 (= ${binary:Version}),
  libjson-glib-dev,
 Description: development files for libjcat
  This package provides development libraries for libjcat.
-- 
2.26.0

>From b9fe0a03b92b51db3cbc9340817147bdd4b48a99 Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Sat, 28 Mar 2020 19:41:09 +
Subject: [PATCH 6/9] d/control: Enable gir debhelper sequence

Otherwise ${gir:Depends} won't be generated.

Signed-off-by: Simon McVittie 
---
 debian/control | 1 +
 1 file changed, 1 insertion(+)

diff --git a/debian/control b/debian/control
index 9dff12e..c187197 100644
--- a/debian/control
+++ b/debian/control
@@ -5,6 +5,7 @@ Maintainer: Debian EFI team 
 Uploaders: Steve McIntyre <93...@debian.org>,
Mario Limonciello 
 Build-Depends: debhelper-compat (=12),
+	   dh-sequence-gir,
 	   help2man,
 	   gnutls-bin,
 	   gnutls-dev,
-- 
2.26.0

Bug#955234: FTBFS: help2man missing, /etc/machine-id not available by default on buildds

[Simon McVittie]

On Sat, 28 Mar 2020 at 17:05:07 +, Simon McVittie wrote:
> Fixed here: https://salsa.debian.org/efi-team/libjcat/-/merge_requests/1

salsa seems to have some maintenance downtime at the moment, so here are
the patches in a more traditional format.

smcv
>From 5608512c17487448427c8779e7185afe3652 Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Sat, 28 Mar 2020 16:33:05 +
Subject: [PATCH 1/9] Add missing B-D on help2man

Signed-off-by: Simon McVittie 
---
 debian/control | 1 +
 1 file changed, 1 insertion(+)

diff --git a/debian/control b/debian/control
index fe2c064..7790953 100644
--- a/debian/control
+++ b/debian/control
@@ -5,6 +5,7 @@ Maintainer: Debian EFI team 
 Uploaders: Steve McIntyre <93...@debian.org>,
Mario Limonciello 
 Build-Depends: debhelper-compat (=12),
+	   help2man,
 	   gnutls-bin,
 	   gnutls-dev,
 	   gobject-introspection,
-- 
2.26.0

>From 45e388cfa4cdb5ded858c4a166ac4ba02ea4889f Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Sat, 28 Mar 2020 16:47:58 +
Subject: [PATCH 2/9] jcat-self-test: Sign /etc/os-release instead of
 /etc/machine-id

The autobuilders use a minimal chroot that doesn't necessarily have
a machine ID, but base-files gives us /etc/os-release.

Signed-off-by: Simon McVittie 
Closes: #955234
---
 ...tc-os-release-instead-of-etc-machine.patch | 25 +++
 debian/patches/series |  1 +
 2 files changed, 26 insertions(+)
 create mode 100644 debian/patches/jcat-self-test-Sign-etc-os-release-instead-of-etc-machine.patch
 create mode 100644 debian/patches/series

diff --git a/debian/patches/jcat-self-test-Sign-etc-os-release-instead-of-etc-machine.patch b/debian/patches/jcat-self-test-Sign-etc-os-release-instead-of-etc-machine.patch
new file mode 100644
index 000..0dc89db
--- /dev/null
+++ b/debian/patches/jcat-self-test-Sign-etc-os-release-instead-of-etc-machine.patch
@@ -0,0 +1,25 @@
+From: Simon McVittie 
+Date: Sat, 28 Mar 2020 16:46:44 +
+Subject: jcat-self-test: Sign /etc/os-release instead of /etc/machine-id
+
+Containers and minimal autobuilder environments don't always have
+a systemd machine ID, but os-release is fairly ubiquitous.
+
+Signed-off-by: Simon McVittie 
+---
+ libjcat/jcat-self-test.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/libjcat/jcat-self-test.c b/libjcat/jcat-self-test.c
+index 93de1fd..7c3558b 100644
+--- a/libjcat/jcat-self-test.c
 b/libjcat/jcat-self-test.c
+@@ -486,7 +486,7 @@ jcat_pkcs7_engine_self_signed_func (void)
+ 	g_assert_no_error (error);
+ 	g_assert_nonnull (engine);
+ 
+-	payload = jcat_get_contents_bytes ("/etc/machine-id", &error);
++	payload = jcat_get_contents_bytes ("/etc/os-release", &error);
+ 	g_assert_no_error (error);
+ 	g_assert_nonnull (payload);
+ 	signature = jcat_engine_self_sign (engine, payload, JCAT_SIGN_FLAG_ADD_TIMESTAMP, &error);
diff --git a/debian/patches/series b/debian/patches/series
new file mode 100644
index 000..d685412
--- /dev/null
+++ b/debian/patches/series
@@ -0,0 +1 @@
+jcat-self-test-Sign-etc-os-release-instead-of-etc-machine.patch
-- 
2.26.0

>From bbff070bf43ebc0d1c0f06f7e2ea545fc42686ab Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Sat, 28 Mar 2020 16:48:35 +
Subject: [PATCH 3/9] Update changelog

Signed-off-by: Simon McVittie 
---
 debian/changelog | 11 +++
 1 file changed, 11 insertions(+)

diff --git a/debian/changelog b/debian/changelog
index 54b9ad3..525b60a 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,14 @@
+libjcat (0.1.0-2) UNRELEASED; urgency=medium
+
+  * Fix FTBFS:
+- Add missing B-D on help2man
+- jcat-self-test: Sign /etc/os-release instead of /etc/machine-id.
+  The autobuilders use a minimal chroot that doesn't necessarily have
+  a machine ID, but base-files gives us /etc/os-release.
+(Closes: #955234)
+
+ -- Simon McVittie   Sat, 28 Mar 2020 16:48:23 +
+
 libjcat (0.1.0-1) unstable; urgency=medium
 
   * Initial release (Closes: #953565)
-- 
2.26.0

Bug#955257: neomutt: Creates broken mbox headers when saving from Maildir

[Andreas Bombe]

Package: neomutt
Version: 20191207+dfsg.1-1.1
Severity: important

While reading a Maildir folder with neomutt I accidentally saved mails
into an existing mbox file rather than another Maildir as I meant to,
but when I opened that mbox file I could not see these mails (and not
with mutt either).

Debug log shows that the date in the header is wrong:

[2020-03-28 20:16:18]<1> is_from()  expected weekday, got: Sa Mär 28 02:33:48 
2020

[2020-03-28 20:16:18]<1> is_from()  expected weekday, got: Mi Feb 12 11:45:21 
2020

[2020-03-28 20:16:18]<1> is_from()  expected weekday, got: Mi Feb 12 05:07:36 
2020

[2020-03-28 20:16:18]<1> is_from()  expected weekday, got: Do Feb 13 13:45:56 
2020

As you can see, the dates are localized to German which they aren't
supposed to be. This does not happen when I save with mutt instead, or
when I use neomutt to save from mbox to mbox.

I'm not sure about the timing, but the same mbox contains good messages
from when I saved to it earlier, so possibly this bug appeared only in
the latest neomutt upload.

Marked this as important since it constitutes a sort of silent data
loss. The messages aren't really lost (they can be restored by manual
editing of the mbox), but neither mutt nor neomutt even make any mention
that they are not displaying messages because of errors outside the
debug log.


-- Package-specific info:
NeoMutt 20191207
Copyright (C) 1996-2016 Michael R. Elkins and others.
NeoMutt comes with ABSOLUTELY NO WARRANTY; for details type 'neomutt -vv'.
NeoMutt is free software, and you are welcome to redistribute it
under certain conditions; type 'neomutt -vv' for details.

System: Linux 5.4.0-4-amd64 (x86_64)
ncurses: ncurses 6.2.20200212 (compiled with 6.2.20200212)
libidn: 1.33 (compiled with 1.33)
GPGme: 1.13.1-unknown
libnotmuch: 5.2.0
hcache backends: tokyocabinet

Configure options: --build=x86_64-linux-gnu --prefix=/usr 
{--includedir=${prefix}/include} {--mandir=${prefix}/share/man} 
{--infodir=${prefix}/share/info} --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules {--libdir=${prefix}/lib/x86_64-linux-gnu} 
{--libexecdir=${prefix}/lib/x86_64-linux-gnu} --disable-maintainer-mode 
--disable-dependency-tracking --mandir=/usr/share/man --libexecdir=/usr/libexec 
--with-mailpath=/var/mail --gpgme --lua --notmuch --with-ui --gnutls --gss 
--idn --mixmaster --sasl --tokyocabinet

Compilation CFLAGS: -g -O2 
-fdebug-prefix-map=/build/neomutt-bCiSXv/neomutt-20191207+dfsg.1=. 
-fstack-protector-strong -Wformat -Werror=format-security -std=c99 
-D_ALL_SOURCE=1 -D_GNU_SOURCE=1 -D__EXTENSIONS__ -I/usr/include 
-I/usr/include/lua5.3 -DNCURSES_WIDECHAR -isystem /usr/include/mit-krb5

Default options:
  +attach_headers_color +compose_to_sender +compress +cond_date +debug 
  +encrypt_to_self +forgotten_attachments +forwref +ifdef +imap +index_color 
  +initials +limit_current_thread +multiple_fcc +nested_if +new_mail +nntp +pop 
  +progress +quasi_delete +regcomp +reply_with_xorig +sensible_browser +sidebar 
  +skip_quoted +smtp +status_color +timeout +tls_sni +trash 

Compile options:
  -autocrypt +bkgdset +color +curs_set +fcntl -flock -fmemopen +futimens 
  +getaddrinfo +gnutls +gpgme +gss +hcache -homespool +idn +inotify 
  -locales_hack +lua +meta +mixmaster +nls +notmuch -openssl +pgp +sasl +smime 
  -sqlite +start_color +sun_attachment +typeahead 
MAILPATH="/var/mail"
MIXMASTER="mixmaster"
PKGDATADIR="/usr/share/neomutt"
SENDMAIL="/usr/sbin/sendmail"
SYSCONFDIR="/etc"

To learn more about NeoMutt, visit: https://neomutt.org
If you find a bug in NeoMutt, please raise an issue at:
https://github.com/neomutt/neomutt/issues
or send an email to: 

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

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

Versions of packages neomutt depends on:
ii  libc6 2.30-4
ii  libgnutls30   3.6.12-2
ii  libgpg-error0 1.37-1
ii  libgpgme111.13.1-7
ii  libgssapi-krb5-2  1.17-7
ii  libidn11  1.33-2.2
ii  liblua5.3-0   5.3.3-1.1+b1
ii  libncursesw6  6.2-1
ii  libnotmuch5   0.29.3-1+b2
ii  libsasl2-22.1.27+dfsg-2
ii  libtinfo6 6.2-1
ii  libtokyocabinet9  1.4.48-12

Versions of packages neomutt recommends:
ii  libsasl2-modules  2.1.27+dfsg-2
ii  locales   2.30-4
ii  mime-support  3.64

Versions of packages neomutt suggests:
ii  aspell 0.60.8-1
ii  ca-certificates20190110
ii  exim4-daemon-light [mail-transport-agent]  4.93-13
ii  gnupg   

Bug#688438:

[Tawa Balikie]

Greetings! I wish to bring to your notice a profitable financial deal
i want to discuss with you, Please confirm the receipt of this email
for more details.
Thanks

Bug#922553: Bug #922553: Make link to the last release point announcement in the index page of each release, fix 2

[jukav]

Hi there
We continue to contribute to correcting the error.
Attached are patches for launch pages that use these tags.
Thank you!
From 66bf613f9891bcbb1b88fdb5db2b4308f0abaefa Mon Sep 17 00:00:00 2001
From: jukav 
Date: Sat, 28 Mar 2020 21:00:39 +0100
Subject: [PATCH] Create tags index files to latest release point announcement.
 Bug: #922553

---
 english/releases/bullseye/index.wml | 2 +-
 english/releases/buster/index.wml   | 2 +-
 english/releases/etch/index.wml | 2 +-
 english/releases/jessie/index.wml   | 2 +-
 english/releases/lenny/index.wml| 2 +-
 english/releases/potato/index.wml   | 2 +-
 english/releases/squeeze/index.wml  | 2 +-
 english/releases/stretch/index.wml  | 2 +-
 english/releases/wheezy/index.wml   | 2 +-
 9 files changed, 9 insertions(+), 9 deletions(-)

diff --git a/english/releases/bullseye/index.wml b/english/releases/bullseye/index.wml
index 959bfb4376b..d91b7724a6f 100644
--- a/english/releases/bullseye/index.wml
+++ b/english/releases/bullseye/index.wml
@@ -6,7 +6,7 @@
 
 
 Debian  was
-released on .
+released on .
 "
   "Debian 11.0 was initially released on <:=spokendate(''):>."
 />
diff --git a/english/releases/buster/index.wml b/english/releases/buster/index.wml
index 99fe1137f86..a9058ab222e 100644
--- a/english/releases/buster/index.wml
+++ b/english/releases/buster/index.wml
@@ -6,7 +6,7 @@
 
 
 Debian  was
-released on .
+released on .
 "
   "Debian 10.0 was initially released on <:=spokendate('2019-07-06'):>."
 />
diff --git a/english/releases/etch/index.wml b/english/releases/etch/index.wml
index d65cc125043..a3d6eafd888 100644
--- a/english/releases/etch/index.wml
+++ b/english/releases/etch/index.wml
@@ -5,7 +5,7 @@
 
 
 Debian GNU/Linux  was
-released on .
+released on .
 Debian 4.0 was initially released on <:=spokendate('2007-04-08'):>.
 The release included many major changes, described in 
 our press release and 
diff --git a/english/releases/jessie/index.wml b/english/releases/jessie/index.wml
index 3ab1cd8ac9f..85b0b973e62 100644
--- a/english/releases/jessie/index.wml
+++ b/english/releases/jessie/index.wml
@@ -4,7 +4,7 @@
 #include "$(ENGLISHDIR)/releases/arches.data"
 
 Debian  was
-released .
+released .
 "
   "Debian 8.0 was initially released on <:=spokendate('2015-04-26'):>."
 />
diff --git a/english/releases/lenny/index.wml b/english/releases/lenny/index.wml
index 864faf2e826..c24cc340b1b 100644
--- a/english/releases/lenny/index.wml
+++ b/english/releases/lenny/index.wml
@@ -5,7 +5,7 @@
 
 
 Debian GNU/Linux  was
-released on .
+released on .
 Debian 5.0.0 was initially released on <:=spokendate('2009-02-14'):>.
 The release included many major
 changes, described in 
diff --git a/english/releases/potato/index.wml b/english/releases/potato/index.wml
index 7a53b5a7370..8e4c4c6545a 100644
--- a/english/releases/potato/index.wml
+++ b/english/releases/potato/index.wml
@@ -7,7 +7,7 @@
 
 Debian GNU/Linux 2.2 (a.k.a. Potato) was released on
 <:=spokendate ("2000-08-14"):>.  The latest point release of Debian 2.2 is
-, released on .
+, released on .
 
 Debian GNU/Linux 2.2 has been obsoleted by
 Debian GNU/Linux 3.0 ("woody").
diff --git a/english/releases/squeeze/index.wml b/english/releases/squeeze/index.wml
index c4c1d6d3898..21e72032e30 100644
--- a/english/releases/squeeze/index.wml
+++ b/english/releases/squeeze/index.wml
@@ -4,7 +4,7 @@
 #include "$(ENGLISHDIR)/releases/arches.data"
 
 Debian  was
-released on .
+released on .
 "
   "Debian 6.0.0 was initially released on <:=spokendate('2011-02-06'):>."
 />
diff --git a/english/releases/stretch/index.wml b/english/releases/stretch/index.wml
index 1534b5e2615..0e196a2aa60 100644
--- a/english/releases/stretch/index.wml
+++ b/english/releases/stretch/index.wml
@@ -4,7 +4,7 @@
 #include "$(ENGLISHDIR)/releases/arches.data"
 
 Debian  was
-released .
+released .
 "
   "Debian 9.0 was initially released on <:=spokendate('2017-06-17'):>."
 />
diff --git a/english/releases/wheezy/index.wml b/english/releases/wheezy/index.wml
index 75e12311d05..fb880cafc09 100644
--- a/english/releases/wheezy/index.wml
+++ b/english/releases/wheezy/index.wml
@@ -6,7 +6,7 @@
 
 
 Debian  was
-released .
+released .
 "
   "Debian 7.0 was initially released on <:=spokendate('2013-05-04'):>."
 />
-- 
2.20.1

Bug#954344: debian installer don't sets PermitRootLogin to yes in ssh config when no regular user are created

[Steven Chamberlain]

Hello Ilya,

Илья Пащук wrote:
> if I add key to root's authorized_keys file with default debian sshd
> configuration, what I will get?

I think the default setting is:
PermitRootLogin prohibit-password

so if you add a key to authorized_keys (and chmod -R go-rwx /root/.ssh)
then you should be able to log in.

Maybe a better feature for the installer, would be if it asked you for
an SSH key for the default user (or for the root user)?

Regards,
-- 
Steven Chamberlain
ste...@pyro.eu.org


signature.asc
Description: Digital signature

Bug#922553: Bug #922553: Make link to the last release point announcement in the index page of each release

[Laura Arjona Reina]

Hi jukav,

Thanks for your contribution! I just applied the patch you provided.

Now it would be needed to include the new tags in the corresponding
english/releases/XXX/index.wml so the date actually links to the
announcements.

I know you're working on it, so thanks in advance, I'll review and apply
the next patch as soon as I can :-)

Kind regards,
-- 
Laura Arjona Reina
https://wiki.debian.org/LauraArjona

Bug#954344: debian installer don't sets PermitRootLogin to yes in ssh config when no regular user are created

[Илья Пащук]

I used the network console feature in install process, so I probably 
will use ssh after installation.


and one other question:

if I add key to root's authorized_keys file with default debian sshd 
configuration, what I will get?

Bug#955221: minidb.py:144: SyntaxWarning: "is" with a literal. Did you mean "=="?

[Maxime Werlen]

Control: tags -1 fixed-upstream

Thanks Paul,

Upstream developers recently released a new version to fix this specific issue.
I've just packaged this update and pushed it on mentors.
RFS #955256 opened.

Regards,

Maxime



Le sam. 28 mars 2020 à 16:54, Paul Wise  a écrit :
>
> Package: python3-minidb
> Version: 2.0.2-3
> Severity: normal
> File: /usr/lib/python3/dist-packages/minidb.py
> Usertags: warnings
>
> Since the upgrade to Python 3.8 I get this warning from urlwatch
> whenever I run it. The warning comes from minidb.py though.
>
> $ urlwatch
> /usr/lib/python3/dist-packages/minidb.py:144: SyntaxWarning: "is" with a 
> literal. Did you mean "=="?
>   if (exc_type, exc_value, traceback) is (None, None, None):
>
> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers testing-debug
>   APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
> 'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
> 'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores)
> Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, 
> TAINT_UNSIGNED_MODULE
> Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), 
> LANGUAGE=en_AU:en (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages python3-minidb depends on:
> ii  python3  3.8.2-2
>
> python3-minidb recommends no packages.
>
> python3-minidb suggests no packages.
>
> -- no debconf information
>
> --
> bye,
> pabs
>
> https://wiki.debian.org/PaulWise

Bug#954296: RFS: libkqueue/2.0.3-1.2 [NMU, RC] -- cross-platform library for kernel event notification

[Sudip Mukherjee]

On Sat, Mar 28, 2020 at 7:15 PM Adam Borowski  wrote:
>
> On Sat, Mar 28, 2020 at 08:09:39PM +0100, Adam Borowski wrote:
> > On Sat, Mar 28, 2020 at 03:59:07PM +, Sudip Mukherjee wrote:
> > > On Thu, Mar 19, 2020 at 09:42:49PM +0100, Adam Borowski wrote:
> > > > On Thu, Mar 19, 2020 at 08:34:16PM +, Sudip Mukherjee wrote:
> > > > >  * Package name: libkqueue
> > > > >Version : 2.0.3-1.2
> > > > >* Non-maintainer upload.
> > > > >* Fix FTBFS with GCC. (Closes: #831076)
> > > > Alas, the testsuite fails for me:
>
> > > Kernel: Linux 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2+deb10u2 (2019-11-11) 
> > > amd64 (x86_64)
> > ^^
> > I tried a bunch of different machines, each with a different kernel:
> >
> > ✗ 5.6.0-rc6-00085-ge6fd0e58416e amd64
> > ✗ 5.5.13-00041-g677eee050e0c amd64
> > ✗ 4.4.167-1213-rockchip-ayufan-g34ae07687fce arm64
> > ✓ 4.19.0-8-amd64 amd64
> > ✗ 5.5.1-00053-g39149fc6f728 arm64
>
> Oops, the arm64 failure is at compile step (not a regression -- the package
> was always broken there), on amd64 it's during tests.

Do you see the same problem on "barriere" ? I think as a DC I can
request for access to that porterbox and if the problem is
reproducible there then I can have a look.


-- 
Regards
Sudip

Bug#922553: Bug #922553: Make link to the last release point announcement in the index page of each release

[jukav]

Hi
I'd like to contribute to fix this bug.
I'm attaching a patch for release_info.wml including new tags for the
last release announcement for each release. Later I will send patches
for the release pages using these tags.
Thanks!
From b5affe3abdba600d8211fcb057e310fdf93464e3 Mon Sep 17 00:00:00 2001
From: jukav 
Date: Sat, 28 Mar 2020 19:15:23 +0100
Subject: [PATCH] Create tags to latest release point announcement. Bug:
 #922553

---
 english/template/debian/release_info.wml | 10 ++
 1 file changed, 10 insertions(+)

diff --git a/english/template/debian/release_info.wml b/english/template/debian/release_info.wml
index 8d2bb2eaefc..afb0522ad46 100644
--- a/english/template/debian/release_info.wml
+++ b/english/template/debian/release_info.wml
@@ -19,24 +19,34 @@
 
 2.2r7
 <:=spokendate('2002-07-13'):>
+2002/20020713
 3.0r6
 <:=spokendate('2005-06-02'):>
+2005/20050602
 3.1r8
 <:=spokendate('2008-04-13'):>
+2008/20080413
 4.0r9
 <:=spokendate('2010-05-22'):>
+2010/20100522
 5.0.10
 <:=spokendate('2012-03-10'):>
+2012/20120310
 6.0.10
 <:=spokendate('2014-07-19'):>
+2014/20140719
 7.11
 <:=spokendate('2016-06-04'):>
+2016/2016060402
 8.11
 <:=spokendate('2018-06-23'):>
+2018/20180623
 9.12
 <:=spokendate('2020-02-08'):>
+2020/2020020802
 10.3
 <:=spokendate('2020-02-08'):>
+2020/20200208
 11.0
 TBA
 12.0
-- 
2.20.1

Bug#955216: [Pkg-libvirt-maintainers] Bug#955216: upgrading libvirt-daemon-system stops VMs without asking

[Guido Günther]

Hi,
On Sat, Mar 28, 2020 at 03:21:14PM +0100, Marc Haber wrote:
> Package: libvirt-daemon-system
> Version: 6.0.0-4
> Severity: important
> 
> Hi,
> 
> since a few package versions, VMs get stopped when libvirt-daemon-system
> upgrade. This is new behavior. In past versions, it was possible to
> upgrade the host system without affecting the virtual machines.

Stopped in what sense? Shutodwn, paused? Which hypervisor URL? Does this
also happen when restarting libvirt?
Cheers,
 -- Guido

Bug#954296: RFS: libkqueue/2.0.3-1.2 [NMU, RC] -- cross-platform library for kernel event notification

[Adam Borowski]

On Sat, Mar 28, 2020 at 08:09:39PM +0100, Adam Borowski wrote:
> On Sat, Mar 28, 2020 at 03:59:07PM +, Sudip Mukherjee wrote:
> > On Thu, Mar 19, 2020 at 09:42:49PM +0100, Adam Borowski wrote:
> > > On Thu, Mar 19, 2020 at 08:34:16PM +, Sudip Mukherjee wrote:
> > > >  * Package name: libkqueue
> > > >Version : 2.0.3-1.2
> > > >* Non-maintainer upload.
> > > >* Fix FTBFS with GCC. (Closes: #831076)
> > > Alas, the testsuite fails for me:

> > Kernel: Linux 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2+deb10u2 (2019-11-11) 
> > amd64 (x86_64)
> ^^
> I tried a bunch of different machines, each with a different kernel:
> 
> ✗ 5.6.0-rc6-00085-ge6fd0e58416e amd64
> ✗ 5.5.13-00041-g677eee050e0c amd64
> ✗ 4.4.167-1213-rockchip-ayufan-g34ae07687fce arm64
> ✓ 4.19.0-8-amd64 amd64
> ✗ 5.5.1-00053-g39149fc6f728 arm64

Oops, the arm64 failure is at compile step (not a regression -- the package
was always broken there), on amd64 it's during tests.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ in the beginning was the boot and root floppies and they were good.
⢿⡄⠘⠷⠚⠋⠀   --  on #linux-sunxi
⠈⠳⣄

Bug#955256: RFS: minidb/2.0.3-1

[Maxime Werlen]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

* Package name: minidb
  Version : 2.0.3-1
  Upstream Author : Thomas Perl 
* URL : https://thp.io/2010/minidb/
* License : ISC
  Section : libs

It builds those binary packages:
  python3-minidb - simple SQLite3-based store for Python objects

To access further information about this package, please visit the
following URL:
  https://mentors.debian.net/package/minidb

Alternatively, one can download the package with dget using this command:
  dget -x 
https://mentors.debian.net/debian/pool/main/m/minidb/minidb_2.0.3-1.dsc

More information about minidb can be obtained from
https://github.com/thp/minidb.

Changes since the last upload:

minidb (2.0.3-1) unstable; urgency=medium

  * New upstream version 2.0.3 (Closes: #955221)
  * Update Standards version to 4.5.0
  * Update debhelper compat to version 12
  * Configured to use gbp

Regards,
Maxime Werlen

Bug#928119: closed by Debian FTP Masters (reply to Andreas Beckmann ) (Bug#928119: fixed in bumblebee 3.2.1-21)

[Alex Thiessen]

I confirm that the issue is fixed now, the new _stretch-backports_ version
works for me.

On Tue, Mar 10, 2020 at 2:21 PM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> This is an automatic notification regarding your Bug report
> which was filed against the bumblebee package:
>
> #928119: bumblebee: Fails to install on a domain-joined machine
>
> It has been closed by Debian FTP Masters 
> (reply to Andreas Beckmann ).
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Debian FTP Masters <
> ftpmas...@ftp-master.debian.org> (reply to Andreas Beckmann <
> a...@debian.org>) by
> replying to this email.
>
>
> --
> 928119: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928119
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
>
> -- Forwarded message --
> From: Debian FTP Masters 
> To: 928119-cl...@bugs.debian.org
> Cc:
> Bcc:
> Date: Tue, 10 Mar 2020 13:19:27 +
> Subject: Bug#928119: fixed in bumblebee 3.2.1-21
> Source: bumblebee
> Source-Version: 3.2.1-21
> Done: Andreas Beckmann 
>
> We believe that the bug you reported is fixed in the latest version of
> bumblebee, which is due to be installed in the Debian FTP archive.
>
> A summary of the changes between this version and the previous one is
> attached.
>
> Thank you for reporting the bug, which will now be closed.  If you
> have further comments please address them to 928...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
>
> Debian distribution maintenance software
> pp.
> Andreas Beckmann  (supplier of updated bumblebee package)
>
> (This message was generated automatically at their request; if you
> believe that there is a problem with it please contact the archive
> administrators by mailing ftpmas...@ftp-master.debian.org)
>
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Format: 1.8
> Date: Tue, 10 Mar 2020 13:58:32 +0100
> Source: bumblebee
> Architecture: source
> Version: 3.2.1-21
> Distribution: unstable
> Urgency: medium
> Maintainer: Debian NVIDIA Maintainers <
> pkg-nvidia-de...@lists.alioth.debian.org>
> Changed-By: Andreas Beckmann 
> Closes: 928119 946556 947661
> Changes:
>  bumblebee (3.2.1-21) unstable; urgency=medium
>  .
>[ Andreas Beckmann ]
>* Recommend primus-libs instead of primus.
>* Downgrade bbswitch dependency to Recommends.
>* Add only local users to the bumblebee group.  (Closes: #928119)
>* Generate vendor-specific driver dependency lists for bumblebee-nvidia.
>* Add alternative dependency on Tesla driver.  (Closes: #946556)
>* Move bumblebeed manpage to section 8.
>* Fall back to /usr/lib//libGL.so.1 as the "nvidia" libGL.so.1
> for
>  glvnd-enabled nvidia drivers that no longer provide a proprietary
>  libGL.so.1 replacement.  (Closes: #947661)
>* Stop manipulating the glx alternative (Debian).
>* Add Ubuntu's dependencies for 418, 430, 435, and 440 driver series.
>* Bump Standards-Version to 4.5.0, no changes needed.
>* Add myself to Uploaders.
>  .
>[ Debian Janitor ]
>* Set upstream metadata fields: Repository.
> Checksums-Sha1:
>  c394d6eae49349e7cad1e197a654ee9c8151f09b 2251 bumblebee_3.2.1-21.dsc
>  9f6368b5fb801725ca1431382b253893d3da0799 19272
> bumblebee_3.2.1-21.debian.tar.xz
>  40d2f6388869d11d2565df25661a89756f9fcbb0 6861
> bumblebee_3.2.1-21_source.buildinfo
> Checksums-Sha256:
>  4e3fec49304968624f35ffe781f1b08a4acfbde7644c273117ddd68446925b65 2251
> bumblebee_3.2.1-21.dsc
>  b016a6641edb99e1a8d832682bfa74e961126ee9ae3639d4417422380c5ccfd6 19272
> bumblebee_3.2.1-21.debian.tar.xz
>  e9eb007fc698244a94cf2862f64c7ef218da87e77162a7e488ccb27d1d6d0b6e 6861
> bumblebee_3.2.1-21_source.buildinfo
> Files:
>  7f9d2b7a0a339d9ed458268c2df1d74c 2251 utils optional
> bumblebee_3.2.1-21.dsc
>  661cc6595d03d47a95f5324021163726 19272 utils optional
> bumblebee_3.2.1-21.debian.tar.xz
>  135f7abafed16f1031bd63919f70a254 6861 utils optional
> bumblebee_3.2.1-21_source.buildinfo
>
> -BEGIN PGP SIGNATURE-
>
> iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAl5nj+cQHGFuYmVAZGVi
> aWFuLm9yZwAKCRBfsz+TWentCM5tD/4pi+Nqk8avpZEUs+SwZrEtDKlYkqXm5fZZ
> uQ5a4SNSxtZRYllnjXmYE1aw33ieYNlsDt19ph4/HHEpmO0cudpGFBiY6QjyQBq4
> 87p3kAhcCRZoOsK3lOPX6oo7m7Zlkcbx2HncbeMa4Wr2tHY6jb8Qn2mQQU0uQS4K
> AgLget98jZWX6M8OjY2ORomYAxUZEUKQrUUe8G5DxrcAEdG1FZzRH7ShYkWodDfv
> JexA5lIboN8l/E5YedLRDSYIbVFMyCsBzrys2z3InJ1JrGDd1XeMsKrNUPVEraeY
> a9cLFkUKsGDEumX4Q2IRsQYSGseW+WMwGCTFjWmw2jSekhd4nRXLArGZSR+4ISmy
> 1oBs7Sfm0BNH36CYEgxxdZwtxU2fhFrIb2JFsbNlq+pBUpouIKiJBc0WUq2sEPpe
> JMhRikfl+atCZtxysdj5FukAYYG+XlG7EnnNn/TB4eD8EVX5N8xIY23xQ3FAX2K7
> QPwQIr6sHvoMmalGhOjcZTPaTlYvi7egGgjrvqR1K3SKj/DoO3W4aTX8al2UvhgA
> eAyi/0dlYHckvi6d+ZEYYo41m0MRgg8AkcD+xIefwM0pMqCuUGGZXLQBIe+yBTzD
> xAO1HP5+ALClYvf29Ytgykc57bIbe9c21PNFOkP7FS+CRG1U11+OKC9RpAw4ZOOh
> Uil6MRY

Bug#954296: RFS: libkqueue/2.0.3-1.2 [NMU, RC] -- cross-platform library for kernel event notification

[Adam Borowski]

On Sat, Mar 28, 2020 at 03:59:07PM +, Sudip Mukherjee wrote:
> On Thu, Mar 19, 2020 at 09:42:49PM +0100, Adam Borowski wrote:
> > On Thu, Mar 19, 2020 at 08:34:16PM +, Sudip Mukherjee wrote:
> > >  * Package name: libkqueue
> > >Version : 2.0.3-1.2

> > >* Non-maintainer upload.
> > >* Fix FTBFS with GCC. (Closes: #831076)
> > 
> > Alas, the testsuite fails for me:
> > 
> > FAIL: kqtest
> > ===
> >libkqueue 2.0.3: ./test-suite.log
> > ===
> > 
> > # TOTAL: 1
> > # PASS:  0
> > # SKIP:  0
> > # XFAIL: 0
> > # FAIL:  1
> > # XPASS: 0
> > # ERROR: 0
> 
> I am confused now. I built it again now and I am not seeing any failure.

> PASS: kqtest

> Kernel: Linux 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2+deb10u2 (2019-11-11) 
> amd64 (x86_64)
^^
I tried a bunch of different machines, each with a different kernel:

✗ 5.6.0-rc6-00085-ge6fd0e58416e amd64
✗ 5.5.13-00041-g677eee050e0c amd64
✗ 4.4.167-1213-rockchip-ayufan-g34ae07687fce arm64
✓ 4.19.0-8-amd64 amd64
✗ 5.5.1-00053-g39149fc6f728 arm64

The setup is otherwise 100% identical (sbuild, btrfs, even directory names),
differing by nothing but CPU and amount of memory.

Got nothing else so far.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ in the beginning was the boot and root floppies and they were good.
⢿⡄⠘⠷⠚⠋⠀   --  on #linux-sunxi
⠈⠳⣄

Bug#955255: The URI ‘ghelp:viking’ does not point to a valid page

[積丹尼 Dan Jacobson]

Package: viking
Version: 1.7-2

https://github.com/viking-gps/viking/issues/59

Bug#955210: kernel-wedge: regression causes kfreebsd-10 FTBFS

[Steven Chamberlain]

tags -1 + patch
thanks
From 03477bf089926f7a599bbe89f67df53080b69bfa Mon Sep 17 00:00:00 2001
From: Steven Chamberlain 
Date: Sat, 28 Mar 2020 18:12:35 +
Subject: [PATCH] preprocess: If source directory is a symlink, follow it

Closes: #955210
---
 commands/preprocess | 9 +
 debian/changelog| 7 +++
 2 files changed, 12 insertions(+), 4 deletions(-)

diff --git a/commands/preprocess b/commands/preprocess
index b60c0d7..0c77e52 100755
--- a/commands/preprocess
+++ b/commands/preprocess
@@ -25,15 +25,16 @@ my %loaded;
 sub find_all_modules {
 	my ($moddir) = @_;
 
-	File::Find::find(
-		sub {
+	File::Find::find({
+		follow => 1, # If $moddir is a symlink, follow it.
+		wanted => sub {
 			if (/\.ko$/) {
 push @module_files,
 File::Spec->abs2rel($File::Find::name,
 			$moddir);
 			}
-		},
-		$moddir);
+		}
+	}, $moddir);
 
 	if ($os eq 'linux') {
 		if (open(my $builtin, "$moddir/modules.builtin")) {
diff --git a/debian/changelog b/debian/changelog
index cf26ea1..46ffe4c 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+kernel-wedge (2.103) UNRELEASED; urgency=medium
+
+  * preprocess: If source directory is a symlink, follow it
+(Closes: #955210)
+
+ -- Steven Chamberlain   Sat, 28 Mar 2020 18:08:28 +
+
 kernel-wedge (2.102) unstable; urgency=medium
 
   * debian/tests: Correct expected exit code for preprocess missingdir case
-- 
2.1.4



signature.asc
Description: Digital signature

Bug#953477: netkit-telnet: CVE-2020-10188

[Marcos Marado]

Did anyone confirm this against Debian's netkit?

At least on 0.17.24 (the earlier version on debian I could get my
hands on) or later, the nextitem function has this check:

>if (current >= end) {
> current = next;
>if (!current) {
>return 0;
>}
>end = nextend;
>next = 0;
>}

>From my understanding of the CVE (and brief analysis), this should be
enough to avoid any possible exploitation, so I installed telnetd and
tried to run the exploit against it. And, indeed, the result I got
was:

> ⛤ Connecting to 0:23
> infoleak unsuccessful.

I might be missing something here, but I suspect that debian's
netkit-telnet (and netkit-telnet-ssl) are not affected by this CVE.

Best regards,
-- 
Marcos Marado

Bug#947844: Same bug!

[Markus Koschany]

Am 28.03.20 um 17:53 schrieb Ronny Buelund:
> I have also experinced the exact same bug. Upgrading from a fresh Debian
> 9 install. Any chance of getting this fixed ??

I will upload new packages to stable-proposed tomorrow but it may take a
few days until they will be accepted.



signature.asc
Description: OpenPGP digital signature

Bug#935358: salutatoi: Please port to Python 3 and/or drop Python 2 package (rdep of python-progressbar)

[Moritz Mühlenhoff]

On Wed, Aug 21, 2019 at 04:48:12PM -0400, mo...@debian.org wrote:
> Package: salutatoi
> Severity: normal
> User: debian-pyt...@lists.debian.org
> Usertags: py2removal
> 
> Hello, please port salutatoi to Python3 and/or drop the python 2
> package. This will help the goal of removing Python 2 from Debian,
> and would also (more immediately) allow to remove packages currently
> dependencies of this one.

This is fixed in the current Mercurial repo, starting with
https://repos.goffi.org/sat/rev/ab2696e34d29 and a few followup
commits.

Cheers,
Moritz

Bug#936459: dvcs-autosync: Python2 removal in sid/bullseye

[René Mayrhofer]

Hi Moritz,

The state on Github is unfortunately incomplete, as I got stuck in the
process of converting to Python 3. The problem is that the XMPP library
I used before hasn't been ported to Python 3 and I would either need to
change to a different XMPP support or to another protocol - considering
MQTT as a lightweight alternative. However, I haven't found time to
actually finish that part, and the current situation isn't helping.

Most of the other code should be Python 3 ready and working right now
(although I haven't tested in depth), but the sync protocol support
isn't there yet. If anybody who is using it has some spare time and want
to create a patch to use another XMPP library, I am ok pulling this in.
If anybody can invest more time to port over to use MQTT instead, that
would be even more welcome :)

Am 27.03.20 um 22:32 schrieb Moritz Mühlenhoff:
> On Fri, Aug 30, 2019 at 07:16:06AM +, Matthias Klose wrote:
>> Package: src:dvcs-autosync
>> Version: 0.5+nmu1
>> Severity: normal
>> Tags: sid bullseye
>> User: debian-pyt...@lists.debian.org
>> Usertags: py2removal
>>
>> Python2 becomes end-of-live upstream, and Debian aims to remove
>> Python2 from the distribution, as discussed in
>> https://lists.debian.org/debian-python/2019/07/msg00080.html
> Hi Rene,
> the debian/ directory in your repository on github seems to have
> fixed this, can you upload this to archive?
>
> Cheers,
> Moritz

Bug#955254: matrix-synapse: add systemd sandboxing options to service file

[jvalleroy]

Package: matrix-synapse
Version: 1.11.1-1
Severity: wishlist

Dear Maintainer,

In FreedomBox, we have added these sandboxing options:

[Service]
ConfigurationDirectory=matrix-synapse
LockPersonality=yes
LogsDirectory=matrix-synapse
NoNewPrivileges=yes
PrivateDevices=yes
PrivateTmp=yes
ProtectControlGroups=yes
ProtectHome=yes
ProtectKernelLogs=yes
ProtectKernelModules=yes
ProtectKernelTunables=yes
ProtectSystem=strict
RestrictAddressFamilies=AF_UNIX AF_INET AF_INET6
RestrictRealtime=yes
StateDirectory=matrix-synapse
SystemCallArchitectures=native

Please consider adding any of these to the service file included in the package.


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

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

Versions of packages matrix-synapse depends on:
ii  adduser3.118
ii  debconf [debconf-2.0]  1.5.73
ii  libjs-jquery   3.3.1~dfsg-3
ii  libpython3-stdlib  3.8.2-2
ii  lsb-base   11.1.0
ii  python33.8.2-2
ii  python3-attr   19.3.0-2
ii  python3-bcrypt 3.1.7-2+b1
ii  python3-bleach 3.1.3-1
ii  python3-canonicaljson  1.1.4-3
ii  python3-daemonize  2.4.7-4
ii  python3-distutils  3.8.2-2
ii  python3-frozendict 1.2-2
ii  python3-idna   2.8-1
ii  python3-jinja2 2.10.1-2
ii  python3-jsonschema 3.0.2-4
ii  python3-lxml   4.5.0-1
ii  python3-msgpack0.6.2-1
ii  python3-nacl   1.3.0-5
ii  python3-netaddr0.7.19-4
ii  python3-openssl19.0.0-1
ii  python3-phonenumbers   8.9.10-2
ii  python3-pil6.2.1-2+b1
ii  python3-prometheus-client  0.7.1-1.1
ii  python3-pyasn1 0.4.2-3
ii  python3-pyasn1-modules 0.2.1-0.2
ii  python3-pymacaroons0.13.0-3
ii  python3-service-identity   18.1.0-5
ii  python3-signedjson 1.1.0-1
ii  python3-six1.14.0-2
ii  python3-sortedcontainers   2.1.0-2
ii  python3-systemd234-3+b1
ii  python3-treq   18.6.0-0.2
ii  python3-twisted18.9.0-8
ii  python3-typing-extensions  3.7.4.1-1
ii  python3-unpaddedbase64 1.1.0-5
ii  python3-yaml   5.3.1-1

Versions of packages matrix-synapse recommends:
ii  python3-psycopg2  2.8.4-2

Versions of packages matrix-synapse suggests:
pn  python3-txacme  

-- Configuration Files:
/etc/matrix-synapse/homeserver.yaml changed [not included]

-- debconf information excluded

Bug#955253: RM: asterisk-testsuite -- RoQA; Depends on Python 2, unmaintained, dropped from testing for 1.5 years

[Moritz Muehlenhoff]

Package: ftp.debian.org
Severity: normal

Please remove asterisk-testsuite. It hasn't been updated since 2014, depends on 
Python 2
and has already been removed from testing since October 2018 (and thus missed 
testing)

Cheers,
Moritz

Bug#944181: [Pkg-electronics-devel] Bug#944181: ghdl: non-standard gcc/g++ used for build (gcc-8)

[Jonathan McDowell]

Control: block -1 with 954826

On Thu, Mar 26, 2020 at 10:48:27PM +0100, Emilio Pozuelo Monfort wrote:
> On Tue, 05 Nov 2019 13:23:02 + Matthias Klose  wrote:
> > Package: ghdl
> > Severity: important
> > Tags: sid bullseye
> > User: debian-...@lists.debian.org
> > Usertags: non-standard-compiler, gcc-8, gcc-8-legacy
> > 
> > This package builds with a non standard compiler version; please check
> > if this package can be built with the default version of gcc/g++, or
> > with gcc-9/g++-9.
> > 
> > Please keep this report open until the package uses the default
> > compiler version (or gcc-9) for the package build.
> > 
> > If the package cannot be built anymore, please file a bug report for
> > ftp.debian.org, asking for the removal of the package.
> > 
> > The severity of this report is likely to be raised before the release,
> > so that the gcc-8 package can be removed for the release.
> 
> GCC 8 is being removed, so this is now serious.

I started pulling in 0.37 from upstream and switching to GCC 9, but
unfortunately #954826 currently means GHDL can't compile as it wants
LLVM which then wants libgcc-8-dev which is now uninstallable.

J.

-- 
Is it real, or is it Mimozine?

Bug#937391: pybitcointools: Python2 removal in sid/bullseye

[Moritz Mühlenhoff]

On Fri, Aug 30, 2019 at 07:32:52AM +, Matthias Klose wrote:
> Package: src:pybitcointools
> Version: 1.1.42-1
> Severity: normal
> Tags: sid bullseye
> User: debian-pyt...@lists.debian.org
> Usertags: py2removal
> 
> Python2 becomes end-of-live upstream, and Debian aims to remove
> Python2 from the distribution, as discussed in
> https://lists.debian.org/debian-python/2019/07/msg00080.html
> 
> Your package either build-depends, depends on Python2, or uses Python2
> in the autopkg tests.  Please stop using Python2, and fix this issue
> by one of the following actions.

Hi Ben,
upstream retired the repo stating "I don't have time to maintain this
library further". Shall we remove it from the archive or do you plan
to port it to Python 3 yourself?

Cheers,
Moritz

Bug#955252: RM: identicurse -- RoQA; Depends on Python 2, dead upstream, unmaintained

[Moritz Muehlenhoff]

Package: ftp.debian.org
Severity: normal

Please remove identicurse. It depends on Python 2, it's dead upstream (last 
commit
from 2014) and unmaintained (last maintainer upload in 2012)

Cheers,
Moritz

Bug#955251: RM: python-stompy -- RoQA; Depends on Python 2, dead upstream, unmaintained, no reverse deps

[Moritz Muehlenhoff]

Package: ftp.debian.org
Severity: normal

Please remove python-stompy. It depends on Python 2, is dead upstream (last 
release in 2010),
the last maintainer upload was in 2011 and there are no reverse deps.

Cheers,
Moritz

Bug#920371: telnetd-ssl: SSL_CTX_use_certificate, ee key too small

[Marcos Marado]

Hi there,

A tested fix can be seen found here:
https://github.com/marado/netkit-telnet-ssl/commit/196297b250181159e8c9f975eb71d45046235c79

Best regards,
-- 
Marcos Marado

Bug#810865: infinoted: Add service file

[James Valleroy]

As of policy version 4.5.0, init scripts are now completely optional.

I have attached the latest service file that we are using in FreedomBox. This 
one enables various systemd sandboxing features.
[Unit]
Description=collaborative text editor service
Documentation=man:infinoted(1)
After=network.target

[Service]
User=infinoted
Group=infinoted
ExecStart=/usr/bin/infinoted
ConfigurationDirectory=infinoted
ConfigurationDirectoryMode=0750
LockPersonality=yes
NoNewPrivileges=yes
PrivateDevices=yes
PrivateMounts=yes
PrivateTmp=yes
ProtectControlGroups=yes
ProtectHome=yes
ProtectKernelLogs=yes
ProtectKernelModules=yes
ProtectKernelTunables=yes
ProtectSystem=full
RestrictAddressFamilies=AF_UNIX AF_INET AF_INET6
RestrictRealtime=yes
StateDirectory=infinoted
SystemCallArchitectures=native

[Install]
WantedBy=multi-user.target


signature.asc
Description: OpenPGP digital signature

Bug#954862: checkstyle 8.15-1+deb10u1 flagged for acceptance

[Adam D Barratt]

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

Hi,

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

Thanks for your contribution!

Upload details
==

Package: checkstyle
Version: 8.15-1+deb10u1

Explanation: fix XML External Entity injection issue [CVE-2019-9658 
CVE-2019-10782]

Bug#954269: manila 7.0.0-1+deb10u1 flagged for acceptance

[Adam D Barratt]

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

Hi,

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

Thanks for your contribution!

Upload details
==

Package: manila
Version: 7.0.0-1+deb10u1

Explanation: fix misisng access permissions check [CVE-2020-9543]

Bug#954985: node-knockout 3.4.2-2+deb10u1 flagged for acceptance

[Adam D Barratt]

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

Hi,

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

Thanks for your contribution!

Upload details
==

Package: node-knockout
Version: 3.4.2-2+deb10u1

Explanation: fix escaping with older Internet Explorer versions [CVE-2019-14862]

Bug#954398: node-dot 1.1.1-1+deb10u1 flagged for acceptance

[Adam D Barratt]

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

Hi,

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

Thanks for your contribution!

Upload details
==

Package: node-dot
Version: 1.1.1-1+deb10u1

Explanation: prevent code execution after prototype pollution [CVE-2020-8141]

Bug#954835: node-yargs-parser 11.1.1-1+deb10u1 flagged for acceptance

[Adam D Barratt]

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

Hi,

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

Thanks for your contribution!

Upload details
==

Package: node-yargs-parser
Version: 11.1.1-1+deb10u1

Explanation: fix prototype pollution [CVE-2020-7608]

Bug#955249: ITP: libxs-parse-sublike-perl -- XS functions to assist in parsing sub-like syntax

[gregor herrmann]

Package: wnpp
Owner: gregor herrmann 
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org, debian-p...@lists.debian.org

* Package name: libxs-parse-sublike-perl
  Version : 0.06
  Upstream Author : Paul Evans 
* URL : https://metacpan.org/release/XS-Parse-Sublike
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : XS functions to assist in parsing sub-like syntax

XS::Parse::Sublike provides some XS functions to assist in writing parsers
for sub-like syntax, primarily for authors of keyword plugins using the
PL_keyword_plugin hook mechanism. It is unlikely to be of much use to anyone
else; and highly unlikely to be any use when writing perl code using these.
Unless you are writing a keyword plugin using XS, this module is not for you.

The package will be maintained under the umbrella of the Debian Perl Group.

--
Generated with the help of dpt-gen-itp(1) from pkg-perl-tools.


signature.asc
Description: Digital Signature

Bug#955250: ocaml-fdkaac: FTBFS against fdk-aac 2.0.1

[Sebastian Ramacher]

Source: ocaml-fdkaac
Version: 0.3.1-3
Severity: serious
Tags: ftbfs sid bullseye
Justification: fails to build from source

ocaml-fdkaac fails to build against the new fdk-aac version available in
unstable:
| checking whether pkg-config knows about fdk-aac... configure: error: requires 
version <= 0.1.6, found 2.0.1
| [snip]
| configure: exit 1
| dh_auto_configure: error: ./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu 
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run 
--disable-maintainer-mode --disable-dependency-tracking returned exit code 1
| make: *** [debian/rules:8: build] Error 25

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#955248: fdkaac: FTBFS against fdk-aac 2.0.1-1

[Sebastian Ramacher]

Source: fdkaac
Version: 0.6.3-1
Severity: serious
Tags: ftbfs sid bullseye
Justification: fails to build from source

fdkaac fails to build against the new fdk-aac version available in
unstable:
| gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o src/main.o src/main.c
| src/main.c: In function ‘main’:
| src/main.c:849:32: error: ‘AACENC_InfoStruct’ {aka ‘struct ’} has 
no member named ‘encoderDelay’
|   849 | if (scale_shift && (aacinfo.encoderDelay & 1)) {
|   |^
| src/main.c:863:33: error: ‘AACENC_InfoStruct’ {aka ‘struct ’} has 
no member named ‘encoderDelay’
|   863 | uint32_t delay = aacinfo.encoderDelay;
|   | ^
| make[3]: *** [Makefile:564: src/main.o] Error 1

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#955247: amavisd-new: upgrade of amavis fails to start daemon

[james.bottom...@hansenpartnership.com]

Package: amavisd-new
Version: 1:2.11.1-1
Severity: grave
Justification: renders package unusable

After upgrading to the latest amavisd-new in testing, it fails to start.
This is the error from the logs

Mar 28 10:22:18 bedivere amavis[3095]: (!)Net::Server: 2020/03/28-10:22:18 
Couldn't open pid file "/var/run/amavis/amavisd.pid" [No such file or 
directory].\n\n  at line 177 in file /usr/share/perl5/Net/Server.pm
Mar 28 10:22:20 bedivere systemd[1]: amavis.service: Main process exited, 
code=exited, status=1/FAILURE
Mar 28 10:22:20 bedivere systemd[1]: amavis.service: Failed with result 
'exit-code'.

It looks like the package transitioned to depending on files in /run, but
no-one told systemd, so the fix is to add

RuntimeDirectory=amavis

To amavis.service

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

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

Versions of packages amavisd-new depends on:
ii  adduser3.118
ii  debconf [debconf-2.0]  1.5.73
ii  file   1:5.38-4
ii  init-system-helpers1.57
pn  libarchive-tar-perl
ii  libarchive-zip-perl1.68-1
ii  libberkeleydb-perl 0.62-1+b1
ii  libcompress-raw-zlib-perl  2.093-1
ii  libconvert-tnef-perl   0.18-1
ii  libconvert-uulib-perl  1:1.5~dfsg-1+b2
pn  libdigest-md5-perl 
ii  libio-stringy-perl 2.111-3
ii  libmail-dkim-perl  0.58-1
ii  libmailtools-perl  2.21-1
pn  libmime-base64-perl
ii  libmime-tools-perl 5.509-1
ii  libnet-libidn-perl 0.12.ds-3+b2
ii  libnet-server-perl 2.009-1
ii  libunix-syslog-perl1.1-3+b2
ii  lsb-base   11.1.0
ii  pax1:20190825-1
ii  perl [libtime-hires-perl]  5.30.0-9

Versions of packages amavisd-new recommends:
ii  altermime 0.3.10-10
pn  libnet-patricia-perl  
ii  ripole0.2.0+20081101.0215-4

Versions of packages amavisd-new suggests:
ii  apt-listchanges  3.22
ii  arj  3.10.22-23
ii  cabextract   1.9-3
ii  clamav   0.102.2+dfsg-2
ii  clamav-daemon0.102.2+dfsg-2
ii  cpio 2.13+dfsg-2
ii  dspam3.10.2+dfsg-13
pn  lhasa
ii  libauthen-sasl-perl  2.1600-1
ii  libdbi-perl  1.643-1
ii  libmail-dkim-perl0.58-1
ii  libnet-ldap-perl 1:0.6600+dfsg-1
ii  libsnmp-perl 5.8+dfsg-2
pn  libzeromq-perl   
ii  lzop 1.04-1
ii  nomarch  1.4-3+b2
ii  p7zip16.02+dfsg-7
ii  rpm  4.14.2.1+dfsg1-1.1
ii  spamassassin 3.4.4-1
ii  unrar1:5.6.6-2

-- Configuration Files:
/etc/amavis/en_US/template-virus-sender.txt changed [not included]
/etc/cron.daily/amavisd-new changed [not included]

-- debconf information excluded

-- debsums errors found:
debsums: changed file /lib/systemd/system/amavis.service (from amavisd-new 
package)

Bug#954856: Please add option to install signed grub bootloader

[Cyril Brulebois]

Hallo Bernhard,

Bernhard  (2020-03-24):
> Comments/Problems:
> 
> After installation in UEFI mode, everything works fine.
> No problems detected.
> 
> One wish regarding GRUB Bootloader:
> 
> Here, my preseed-file for installing GRUB:
> 
> > # ==
> > # GRUB-Installer
> > # ==
> > 
> > # Bootloader
> > d-i grub-installer/only_debian   boolean true
> > d-i grub-installer/with_other_os boolean true
> > 
> > # Install GRUB Bootloader to /dev/sda
> > d-i grub-installer/bootdev string /dev/sda
> 
> If possible, please add an option for preseed-file to decide for install 
> signed or unsigned GRUB installer.
> This is for Secure Boot.
> 
> Currently, the signed GRUB Bootloader is not installed on my system, because 
> the recommended packages are not installed:
> > d-i base-installer/install-recommends boolean false

Please attach /var/log/installer/syslog (compressed).

If you're booting in UEFI mode, you should *not* get grub-pc but the
right GRUB EFI package, which is signed. Its being installed should
result in the installation of shim-signed, despite install-recommends
being disabled (see the grub-installer script in the grub-installer
package).


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#955246: ibus-zhuyin: Migrate from /usr/lib/ibus to /usr/libexec

[Changwoo Ryu]

Package: ibus-zhuyin
Version: 0.1.0-2
Severity: wishlist


Hello,

ibus-zhuyin uses --libexec-dir=/usr/lib/ibus configure flag. But it is
not needed anymore. Please remove the --libexec-dir flag in the next 
uploads.

ibus-zhuyin doesn't have setup in /usr/lib/ibus so you don't have to change 
other things.


Details:

ibus used /usr/lib/ibus as "libexec" dir for FHS 2.x compliance.
And all the ibus engine packages also used the same libexec dir
/usr/lib/ibus, because ibus-setup searched ibus-setup-NAME in libexec 
dir as fallback.

But FHS 3.0 allows using /usr/libexec, so the newer ibus 1.5.22-2
just uses /usr/libexec. ibus-setup provides compatibility with the old
fallback setup path /usr/lib/ibus/ibus-setup-NAME. When ibus-setup 
uses such a fallback, it will display a warning like this:

  Warning: Using old FHS 2.x path /usr/lib/ibus/ibus-setup-NAME

This FHS 2.x compatibility is to be removed after some time.

If your ibus-NAME package have explicit  in 
your /usr/share/ibus/NAME.xml, you don't have to worry and just remove 
--libexec-dir=/usr/lib/ibus flag in the next uploads.

If your package does not have  in /usr/share/ibus/.xml,
it is encouraged to patch your package to have  in the XML. 
Then it will work with older versions of ibus package. For example:

https://salsa.debian.org/input-method-team/ibus-hangul/blob/master/debian/patches/specify-setup-in-ibus-component.patch

Please don't forget to upstream the changes.

Without  or --libexec-dir flag, /usr/libexec/ibus-setup-NAME will 
work only with the newer versions of ibus. If it's too difficult to patch 
and you decided not to patch, don't forget to add the versioned dependency 
"ibus (>= 1.5.22-2)" to Depends.


Thanks,

Bug#955245: ibus-unikey: Migrate from /usr/lib/ibus to /usr/libexec

[Changwoo Ryu]

Package: ibus-unikey
Version: 0.6.1-1.1+b1
Severity: wishlist
Control: block 955219 by -1


Hello,

ibus-unikey uses --libexec-dir=/usr/lib/ibus configure flag. But it is
not needed anymore. Please remove the --libexec-dir flag in the next 
uploads.

ibus-unikey has setup in /usr/lib/ibus and it was not specified in the XML,
/usr/share/ibus/component/unikey.xml. Please specify the setup command
path  in the XML if possible. Or, if it's too difficult to patch, 
add versioned dependency ibus (>= 1.5.22-2).


Details:

ibus used /usr/lib/ibus as "libexec" dir for FHS 2.x compliance.
And all the ibus engine packages also used the same libexec dir
/usr/lib/ibus, because ibus-setup searched ibus-setup-NAME in libexec 
dir as fallback.

But FHS 3.0 allows using /usr/libexec, so the newer ibus 1.5.22-2
just uses /usr/libexec. ibus-setup provides compatibility with the old
fallback setup path /usr/lib/ibus/ibus-setup-NAME. When ibus-setup 
uses such a fallback, it will display a warning like this:

  Warning: Using old FHS 2.x path /usr/lib/ibus/ibus-setup-NAME

This FHS 2.x compatibility is to be removed after some time.

If your ibus-NAME package have explicit  in 
your /usr/share/ibus/NAME.xml, you don't have to worry and just remove 
--libexec-dir=/usr/lib/ibus flag in the next uploads.

If your package does not have  in /usr/share/ibus/.xml,
it is encouraged to patch your package to have  in the XML. 
Then it will work with older versions of ibus package. For example:

https://salsa.debian.org/input-method-team/ibus-hangul/blob/master/debian/patches/specify-setup-in-ibus-component.patch

Please don't forget to upstream the changes.

Without  or --libexec-dir flag, /usr/libexec/ibus-setup-NAME will 
work only with the newer versions of ibus. If it's too difficult to patch 
and you decided not to patch, don't forget to add the versioned dependency 
"ibus (>= 1.5.22-2)" to Depends.


Thanks,

Bug#926539: rootskel: steal-ctty no longer works on at least sparc64

[John Paul Adrian Glaubitz]

Control: reopen -1

On 3/28/20 6:16 PM, John Paul Adrian Glaubitz wrote:
> On 3/28/20 5:39 PM, Ivo De Decker wrote:
>> This bug wasn't fixed in time for buster. Is it still present in bullseye? If
>> so, it might be good to try to fix it this time.
> 
> I fixed the bug upstream [1], so we can safely close the issue here.

Ah, I just realized this bug also affected s390x. Sorry, I will reopen it.

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#952088: fixed in ruby-tins 1.1.0-2

[Ivo De Decker]

Hi,

On Wed, Feb 26, 2020 at 05:08:54PM +, Debian FTP Masters wrote:
>[ Lucas Kanashiro ]
>* Add b-d on ruby-sync, it is not bundled in ruby anymore (Closes: #952088)

Please note that ruby-tins is not migrating to testing, because ruby-sync
needs a new source-only upload.

Cheers,

Ivo

Bug#955244: ITP: sphinxcontrib-devhelp -- sphinx extension which outputs Devhelp document

[Sandro Tosi]

Package: wnpp
Severity: wishlist
Owner: Sandro Tosi 

* Package name: sphinxcontrib-devhelp
  Version : 1.0.2
  Upstream Author : Georg Brandl
* URL : https://github.com/sphinx-doc/sphinxcontrib-devhelp/
* License : BSD
  Programming Lang: Python
  Description : sphinx extension which outputs Devhelp document

Now a separate extension, needed to upload sphinx 2.* to unstable

Bug#955243: ITP: sphinxcontrib-qthelp -- sphinx extension which outputs QtHelp document

[Sandro Tosi]

Package: wnpp
Severity: wishlist
Owner: Sandro Tosi 

* Package name: sphinxcontrib-qthelp
  Version : 1.0.3
  Upstream Author : Georg Brandl
* URL : https://github.com/sphinx-doc/sphinxcontrib-qthelp
* License : BSD
  Programming Lang: Python
  Description : sphinx extension which outputs QtHelp document

now that's an external extension, is needed to upload sphinx 2.*

Bug#955058: speedcrunch: FTBFS with Sphinx 2.4: Could not import extension qtkeyword (exception: No module named 'sphinxcontrib')

[Sandro Tosi]

> On Sat, Mar 28, 2020 at 05:40:05PM +0100, Felix Krull wrote:
> > I do have a question: this is caused by the qthelp builder being
> > deprecated and moved to sphinxcontrib (but with a shim in the main
> > package). Are there existing plans to package
> > https://github.com/sphinx-doc/sphinxcontrib-qthelp or do I need to
> > take care of it myself?
>
> Either I or Sandro (CCed) will take care of it soon.

yep i'll take care of it

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

Bug#955241: ibus-sunpinyin: Migrate from /usr/lib/ibus to /usr/libexec

[Changwoo Ryu]

Package: ibus-sunpinyin
Version: 2.0.3+git20181120-5
Severity: wishlist


Hello,

ibus-sunpinyin uses --libexec-dir=/usr/lib/ibus configure flag. But it is
not needed anymore. Please remove the --libexec-dir flag in the next 
uploads.

ibus-sunpinyin has setup in /usr/lib/ibus but it was specified in the  in
the XML so you don't have to change other things.


Details:

ibus used /usr/lib/ibus as "libexec" dir for FHS 2.x compliance.
And all the ibus engine packages also used the same libexec dir
/usr/lib/ibus, because ibus-setup searched ibus-setup-NAME in libexec 
dir as fallback.

But FHS 3.0 allows using /usr/libexec, so the newer ibus 1.5.22-2
just uses /usr/libexec. ibus-setup provides compatibility with the old
fallback setup path /usr/lib/ibus/ibus-setup-NAME. When ibus-setup 
uses such a fallback, it will display a warning like this:

  Warning: Using old FHS 2.x path /usr/lib/ibus/ibus-setup-NAME

This FHS 2.x compatibility is to be removed after some time.

If your ibus-NAME package have explicit  in 
your /usr/share/ibus/NAME.xml, you don't have to worry and just remove 
--libexec-dir=/usr/lib/ibus flag in the next uploads.

If your package does not have  in /usr/share/ibus/.xml,
it is encouraged to patch your package to have  in the XML. 
Then it will work with older versions of ibus package. For example:

https://salsa.debian.org/input-method-team/ibus-hangul/blob/master/debian/patches/specify-setup-in-ibus-component.patch

Please don't forget to upstream the changes.

Without  or --libexec-dir flag, /usr/libexec/ibus-setup-NAME will 
work only with the newer versions of ibus. If it's too difficult to patch 
and you decided not to patch, don't forget to add the versioned dependency 
"ibus (>= 1.5.22-2)" to Depends.


Thanks,

Bug#955242: ibus-table: Migrate from /usr/lib/ibus to /usr/libexec

[Changwoo Ryu]

Package: ibus-table
Version: 1.9.25-1
Severity: wishlist


Hello,

ibus-table uses --libexec-dir=/usr/lib/ibus configure flag. But it is
not needed anymore. Please remove the --libexec-dir flag in the next 
uploads.

ibus-table has setup in /usr/lib/ibus but it was specified in the  in
the XML so you don't have to change other things.


Details:

ibus used /usr/lib/ibus as "libexec" dir for FHS 2.x compliance.
And all the ibus engine packages also used the same libexec dir
/usr/lib/ibus, because ibus-setup searched ibus-setup-NAME in libexec 
dir as fallback.

But FHS 3.0 allows using /usr/libexec, so the newer ibus 1.5.22-2
just uses /usr/libexec. ibus-setup provides compatibility with the old
fallback setup path /usr/lib/ibus/ibus-setup-NAME. When ibus-setup 
uses such a fallback, it will display a warning like this:

  Warning: Using old FHS 2.x path /usr/lib/ibus/ibus-setup-NAME

This FHS 2.x compatibility is to be removed after some time.

If your ibus-NAME package have explicit  in 
your /usr/share/ibus/NAME.xml, you don't have to worry and just remove 
--libexec-dir=/usr/lib/ibus flag in the next uploads.

If your package does not have  in /usr/share/ibus/.xml,
it is encouraged to patch your package to have  in the XML. 
Then it will work with older versions of ibus package. For example:

https://salsa.debian.org/input-method-team/ibus-hangul/blob/master/debian/patches/specify-setup-in-ibus-component.patch

Please don't forget to upstream the changes.

Without  or --libexec-dir flag, /usr/libexec/ibus-setup-NAME will 
work only with the newer versions of ibus. If it's too difficult to patch 
and you decided not to patch, don't forget to add the versioned dependency 
"ibus (>= 1.5.22-2)" to Depends.


Thanks,

Bug#955058: speedcrunch: FTBFS with Sphinx 2.4: Could not import extension qtkeyword (exception: No module named 'sphinxcontrib')

[Felix Krull]

On Sat, 28 Mar 2020 at 17:56, Dmitry Shachnev  wrote:
> Either I or Sandro (CCed) will take care of it soon.
>
> It will have to pass the NEW queue, though. But if that takes long, I can
> delay sphinx upload to unstable.
>
> --
> Dmitry Shachnev

Great, thanks!

Bug#955240: ibus-skk: Migrate from /usr/lib/ibus to /usr/libexec

[Changwoo Ryu]

Package: ibus-skk
Version: 1.4.3-1
Severity: wishlist
Control: block 955219 by -1


Hello,

ibus-skk uses --libexec-dir=/usr/lib/ibus configure flag. But it is
not needed anymore. Please remove the --libexec-dir flag in the next 
uploads.

ibus-skk has setup in /usr/lib/ibus and it was not specified in the XML,
/usr/share/ibus/component/skk.xml. Please specify the setup command
path  in the XML if possible. Or, if it's too difficult to patch, 
add versioned dependency ibus (>= 1.5.22-2).


Details:

ibus used /usr/lib/ibus as "libexec" dir for FHS 2.x compliance.
And all the ibus engine packages also used the same libexec dir
/usr/lib/ibus, because ibus-setup searched ibus-setup-NAME in libexec 
dir as fallback.

But FHS 3.0 allows using /usr/libexec, so the newer ibus 1.5.22-2
just uses /usr/libexec. ibus-setup provides compatibility with the old
fallback setup path /usr/lib/ibus/ibus-setup-NAME. When ibus-setup 
uses such a fallback, it will display a warning like this:

  Warning: Using old FHS 2.x path /usr/lib/ibus/ibus-setup-NAME

This FHS 2.x compatibility is to be removed after some time.

If your ibus-NAME package have explicit  in 
your /usr/share/ibus/NAME.xml, you don't have to worry and just remove 
--libexec-dir=/usr/lib/ibus flag in the next uploads.

If your package does not have  in /usr/share/ibus/.xml,
it is encouraged to patch your package to have  in the XML. 
Then it will work with older versions of ibus package. For example:

https://salsa.debian.org/input-method-team/ibus-hangul/blob/master/debian/patches/specify-setup-in-ibus-component.patch

Please don't forget to upstream the changes.

Without  or --libexec-dir flag, /usr/libexec/ibus-setup-NAME will 
work only with the newer versions of ibus. If it's too difficult to patch 
and you decided not to patch, don't forget to add the versioned dependency 
"ibus (>= 1.5.22-2)" to Depends.


Thanks,

Bug#955239: ibus-pinyin: Migrate from /usr/lib/ibus to /usr/libexec

[Changwoo Ryu]

Package: ibus-pinyin
Version: 1.5.0-6+b1
Severity: wishlist



Hello,

ibus-pinyin uses --libexec-dir=/usr/lib/ibus configure flag. But it is
not needed anymore. Please remove the --libexec-dir flag in the next 
uploads.

ibus-pinyin has setup in /usr/lib/ibus but it was specified in the  in
the XML so you don't have to change other things.


Details:

ibus used /usr/lib/ibus as "libexec" dir for FHS 2.x compliance.
And all the ibus engine packages also used the same libexec dir
/usr/lib/ibus, because ibus-setup searched ibus-setup-NAME in libexec 
dir as fallback.

But FHS 3.0 allows using /usr/libexec, so the newer ibus 1.5.22-2
just uses /usr/libexec. ibus-setup provides compatibility with the old
fallback setup path /usr/lib/ibus/ibus-setup-NAME. When ibus-setup 
uses such a fallback, it will display a warning like this:

  Warning: Using old FHS 2.x path /usr/lib/ibus/ibus-setup-NAME

This FHS 2.x compatibility is to be removed after some time.

If your ibus-NAME package have explicit  in 
your /usr/share/ibus/NAME.xml, you don't have to worry and just remove 
--libexec-dir=/usr/lib/ibus flag in the next uploads.

If your package does not have  in /usr/share/ibus/.xml,
it is encouraged to patch your package to have  in the XML. 
Then it will work with older versions of ibus package. For example:

https://salsa.debian.org/input-method-team/ibus-hangul/blob/master/debian/patches/specify-setup-in-ibus-component.patch

Please don't forget to upstream the changes.

Without  or --libexec-dir flag, /usr/libexec/ibus-setup-NAME will 
work only with the newer versions of ibus. If it's too difficult to patch 
and you decided not to patch, don't forget to add the versioned dependency 
"ibus (>= 1.5.22-2)" to Depends.


Thanks,