Bug#926182: Patch: Use alternatives system for guile-2.2-dev binaries

[Thibaut Paumard]

Le 25/05/2019 à 01:18, Rob Browning a écrit :
> Rob Browning  writes:
> 
>> I'm not certain, but I'm planning to work on guile over the next week.
>> If so, I should be able to take a look.
> 
> Just as an update, I obviously didn't get to it earlier this week, but
> I'm looking in to it now.
> 
> After I poke around a bit, I suspect the next step will be to contact
> the release managers to see what they think about any proposed changes
> because of course if they're not in favor, then the changes may have to
> wait.
> 
> I expect I'll be able to report back in a couple of days.

Dear Rob,

Since this change would be revertible in sid, you can safely upload
already and then contact the release team with the unblock request and a
source debdiff.

Kind regards, Thibaut.



signature.asc
Description: OpenPGP digital signature

Bug#884999: debhelper: Please default Rules-Require-Root to no

[Niels Thykier]

Hideki Yamane:
> Hi,
> 
> On Fri, 24 May 2019 10:47:22 -0700
> Sean Whitton  wrote:
>> (surely we are a very long way from r-r-r: no for every package?)
> 
>  I don't think so since lintian info about 
> "should-specify-rules-requires-root"
>  containts only 98 packages.
>  https://lintian.debian.org/tags/should-specify-rules-requires-root.html
> 
>  mandatory "r-r-r: no" in dpkg-dev and full rebuild shows exact numbers
>  to be dealt with, IMO.
> 
> 

The use of "r-r-r: no" will also disable dpkg-buildpackage detection of
missing build-{arch,indep} targets.  IOW, you need to add

https://lintian.debian.org/tags/debian-rules-missing-recommended-target.html

To your list of packages needing a fix before "r-r-r: no" can be the
default.

Additionally, lintian cannot/does not detect cases where a package use
(fake)root during the install step (e.g. upstream) but then later
"undoes" the ownership to root:root (e.g. dh_fixperms).  Just as an FYI,
so you know the lintian check is incomplete (I have no idea how many
instances we have of that - so it might be a non-issue).

Thanks,
~Niels

Bug#929508: lsblk doesn't show correct model when disk is converted to LVM Physical Volume

[Brian Wengel]

Package: util-linux
Version: 2.33.1



Example:

# lsblk -o +model
NAMEMAJ:MIN RM   SIZE RO TYPE MOUNTPOINT MODEL
sda   8:00 931.5G  0 diskLVM PV
8PrJ75-1Vo9-L9xM-TWAE-WRMn-Jcd3-G8oT9T on /dev/sda
└─VG_HDD-LV_HDD 253:00   300G  0 lvm  /mnt/VG_HDD-LV_HDD
sdb   8:16   0 465.8G  0 disk
HGST_HTS725050A7E630
sdc   8:32   0 298.1G  0 disk
WDC_WD3200BEKT-00F3T0
sdd   8:48   0 931.5G  0 disk
ST1000LM048-2E7172
nvme0n1 259:00 238.5G  0 diskSAMSUNG
MZVLB256HAHQ-0
├─nvme0n1p1 259:1071M  0 part /boot/efi
├─nvme0n1p2 259:20   1.4G  0 part
└─nvme0n1p3 259:30 4G  0 part /

It doesn't show the model, but a non-model property of the disk, in this
case some LVM informations.

The model is "*ST1000LM048-2E7172*" and it should show "*ST1000LM048-2E7172*"
for the model property!

If you want to know if the disk is a PV, put it in another lsblk
column/field or the user could use a LVM tool.

Don't hijack the model property! This is crazy, no matter how nice
something think it is to have this information in the model property. It's
just wrong!


Best regards

Brian Wengel

Denmark

Bug#929116: fixed in systemd 241-4

[Hugo Lefeuvre]

Hi,

241-5 reverted the patch for this issue, so I guess this bug report should
be reopened.

Salvatore: tracker should be updated as well, right?

regards,
Hugo

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


signature.asc
Description: PGP signature

Bug#929509: unblock: flycheck/31-3

[Denis Danilov]

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

Please unblock package flycheck

This minor release contains bugfix for #929232.  The fix disables two sphinx
extentions used during the build of the documentation for flycheck.
If enabled, they can lead to failure of build process as described in #929232.

(the debdiff against the package in testing is attached)

unblock flycheck/31-3


diff -Nru flycheck-31/debian/changelog flycheck-31/debian/changelog
--- flycheck-31/debian/changelog2019-01-03 20:20:26.0 +0100
+++ flycheck-31/debian/changelog2019-05-21 22:23:38.0 +0200
@@ -1,3 +1,12 @@
+flycheck (31-3) unstable; urgency=medium
+
+  * Team upload.
+
+  [ Denis Danilov ]
+  * disable intersphinx and info extensions (Closes: #929232)
+
+ -- Sean Whitton   Tue, 21 May 2019 13:23:38 -0700
+
 flycheck (31-2) unstable; urgency=medium
 
   * enable GitLab CI at salsa.d.o
diff -Nru 
flycheck-31/debian/patches/disable-intersphinx-and-info-extensions.patch 
flycheck-31/debian/patches/disable-intersphinx-and-info-extensions.patch
--- flycheck-31/debian/patches/disable-intersphinx-and-info-extensions.patch
1970-01-01 01:00:00.0 +0100
+++ flycheck-31/debian/patches/disable-intersphinx-and-info-extensions.patch
2019-05-21 22:23:38.0 +0200
@@ -0,0 +1,32 @@
+From: Denis Danilov 
+Date: Tue, 21 May 2019 20:12:52 +0200
+Subject: disable intersphinx and info extensions
+
+The intersphinx and info extensions use network during the build. The info
+extension may even fail the build if network is available (Bug #929232).
+
+Forwarded: not-needed
+---
+ doc/conf.py | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/doc/conf.py b/doc/conf.py
+index 968a7a6..5aa7d36 100644
+--- a/doc/conf.py
 b/doc/conf.py
+@@ -33,13 +33,13 @@ ON_RTD = os.environ.get('READTHEDOCS', None) == 'True'
+ 
+ needs_sphinx = '1.3'
+ extensions = [
+-'sphinx.ext.intersphinx',
++#'sphinx.ext.intersphinx',
+ 'sphinx.ext.extlinks',
+ 'sphinx.ext.todo',
+ # Domain for Emacs Lisp
+ 'elisp',
+ # Cross-references to info nodes
+-'info'
++#'info'
+ ]
+ 
+ # Project metadata
diff -Nru flycheck-31/debian/patches/series flycheck-31/debian/patches/series
--- flycheck-31/debian/patches/series   2019-01-03 20:20:26.0 +0100
+++ flycheck-31/debian/patches/series   2019-05-21 22:23:38.0 +0200
@@ -3,3 +3,4 @@
 disable-MELPA-tests.patch
 disable-rpmlint-test.patch
 disable-flaky-tests.patch
+disable-intersphinx-and-info-extensions.patch

Bug#929508: ...and no model info the the actual LV where it would make sense

[Brian Wengel]

But It would make a lot of sense to assign a model value for LV device
itself, but this is omitted!
E.g. "LVM LV"

Bug#929116: fixed in systemd 241-4

[Salvatore Bonaccorso]

Hi Hugo,

On Sat, May 25, 2019 at 09:20:59AM +0200, Hugo Lefeuvre wrote:
> Salvatore: tracker should be updated as well, right?

Yes indeed, actually just commited the change and reflecting in a note
that the fix was reverted with 241-5.

Regards,
Salvatore

Bug#929433: lintian: warn on suspicious usage of dpkg-architecture variables

[Graham Inggs]

Hi Chris, Helmut

Thanks for your comments.

I think this tag would be more useful for maintainers preparing new
packages, than for finding existing problems in the archive.  We can
just use codesearch.d.n for that.

On Thu, 23 May 2019 at 17:37, Helmut Grohne  wrote:
> https://codesearch.debian.net/search?q=--libdir%3D.*DEB_BUILD
>
> These should all be using DEB_HOST_MULTIARCH.

How about emitting an info level tag when one of the less common
dpkg-architecture variables is used, and proving some hints regarding
the correct usage?

> Graham, maybe you can send patches for each of these?

I'll do that.

Regards
Graham

Bug#929510: apache2-dev: make the build more reproducible

[Helmut Grohne]

Package: apache2-dev
Version: 2.4.38-3
Tags: patch

I was looking into apache2-dev, because it cannot satisfy foreign
architecture dependencies. While doing so, I noticed that it is not
reproducible. I'm submitting a partial fix here. It is to be understood
as an incremental improvement.

A major reason for not being reproducible is
/usr/share/apache2/build/config.nice. It's a convenience script to later
configure apache in the same way. Fortunately, nothing uses this file.
To verify that, I rebuilt all build-rdeps of apache2-dev and I only
encountered one failure: #929506. We can simply drop the file.

I also noticed that config_vars.mk embeds AWK=mawk or AWK=gawk. That can
be easily canonicalized to AWK=awk.

After this patch, I see two issues:
 * config_vars.mk embeds -fdebug-prefix-map. (reproducible)
 * config_vars.mk is architecture-dependent and installed to /usr/share
   (fhs violation).

Please just close this bug after applying the patch despite those other
issues.

Helmut
diff --minimal -Nru apache2-2.4.38/debian/apache2-dev.install 
apache2-2.4.38/debian/apache2-dev.install
--- apache2-2.4.38/debian/apache2-dev.install   2019-04-02 21:55:20.0 
+0200
+++ apache2-2.4.38/debian/apache2-dev.install   2019-05-25 08:43:23.0 
+0200
@@ -1,6 +1,7 @@
 /usr/bin/apxs
 /usr/include/apache2
-/usr/share/apache2/build
+/usr/share/apache2/build/*.sh
+/usr/share/apache2/build/*.mk
 debian/debhelper/apache2.pm
/usr/share/perl5/Debian/Debhelper/Sequence/
 debian/debhelper/dh_apache2/usr/bin
 debian/debhelper/postinst-apache2  /usr/share/debhelper/autoscripts/
diff --minimal -Nru apache2-2.4.38/debian/changelog 
apache2-2.4.38/debian/changelog
--- apache2-2.4.38/debian/changelog 2019-04-07 20:15:40.0 +0200
+++ apache2-2.4.38/debian/changelog 2019-05-25 08:43:27.0 +0200
@@ -1,3 +1,11 @@
+apache2 (2.4.38-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Do not install /usr/share/apache2/build/config.nice. (Closes: #-1)
+  * Make config_vars.mk reproducible wrt. AWK.
+
+ -- Helmut Grohne   Sat, 25 May 2019 08:43:27 +0200
+
 apache2 (2.4.38-3) unstable; urgency=high
 
   [ Marc Deslauriers ]
diff --minimal -Nru apache2-2.4.38/debian/rules apache2-2.4.38/debian/rules
--- apache2-2.4.38/debian/rules 2019-04-02 21:55:20.0 +0200
+++ apache2-2.4.38/debian/rules 2019-05-25 08:43:27.0 +0200
@@ -103,6 +103,7 @@
 
 override_dh_auto_configure: configure-stamp
 configure-stamp: prebuild-checks-stamp support/suexec-custom.c
+   AWK=awk \
./configure --host=$(DEB_HOST_GNU_TYPE) --build=$(DEB_BUILD_GNU_TYPE) \
--enable-layout=Debian --enable-so --with-program-name=apache2 \
--enable-suexec --with-suexec-caller=www-data \

Bug#929511: qtcreator: Segfault on start

[Martin Haase]

Package: qtcreator
Version: 4.8.2-1
Severity: grave
Tags: upstream
Justification: renders package unusable

This is what I get when I try to start qtcreator:

Program received signal SIGSEGV, Segmentation fault.
0x7fffe6091e3c in llvm::SmallPtrSetImplBase::Grow(unsigned int) ()
from /usr/lib/x86_64-linux-gnu/libLLVM-3.7.so.1

Complete backtrace, as from gdb:

#0  0x7fffe6091e3c in llvm::SmallPtrSetImplBase::Grow(unsigned int) () from 
/usr/lib/x86_64-linux-gnu/libLLVM-3.7.so.1
#1  0x7fffe6091ff3 in llvm::SmallPtrSetImplBase::insert_imp(void const*) () 
from /usr/lib/x86_64-linux-gnu/libLLVM-3.7.so.1
#2  0x7fffe6060d24 in llvm::cl::OptionCategory::registerCategory() () from 
/usr/lib/x86_64-linux-gnu/libLLVM-3.7.so.1
#3  0x7fffd7602082 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-7.so.1
#4  0x77fe439a in call_init (l=, argc=argc@entry=1, 
argv=argv@entry=0x7fffe498, env=env@entry=0x7fffe4a8)
at dl-init.c:72
#5  0x77fe4496 in call_init (env=0x7fffe4a8, argv=0x7fffe498, 
argc=1, l=) at dl-init.c:30
#6  _dl_init (main_map=main_map@entry=0x55909600, argc=1, 
argv=0x7fffe498, env=0x7fffe4a8) at dl-init.c:119
#7  0x77fe8303 in dl_open_worker (a=a@entry=0x7fffda10) at 
dl-open.c:517
#8  0x76447f8f in __GI__dl_catch_exception (exception=, 
operate=, args=) at dl-error-skeleton.c:196
#9  0x77fe7bea in _dl_open (file=0x55909538 
"/usr/lib/x86_64-linux-gnu/qtcreator/plugins/libClangTools.so",
mode=-2147479551, caller_dlopen=0x76ceffac, nsid=, 
argc=1, argv=0x7fffe498, env=0x7fffe4a8) at dl-open.c:599
#10 0x7630f256 in dlopen_doit (a=a@entry=0x7fffdc30) at dlopen.c:66
#11 0x76447f8f in __GI__dl_catch_exception 
(exception=exception@entry=0x7fffdbd0, operate=,
args=)
at dl-error-skeleton.c:196
#12 0x7644801f in __GI__dl_catch_error (objname=0x5558cd00, 
errstring=0x5558cd08, mallocedp=0x5558ccf8,
operate=, args=) at
dl-error-skeleton.c:215
#13 0x7630f975 in _dlerror_run (operate=operate@entry=0x7630f200 
,
args=args@entry=0x7fffdc30) at dlerror.c:163
#14 0x7630f2e6 in __dlopen (file=, mode=) 
at dlopen.c:87
#15 0x76ceffac in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x76ce9c25 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x76cea1d3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x77fad5dc in 
ExtensionSystem::Internal::PluginSpecPrivate::loadLibrary() ()
from /usr/bin/../lib/x86_64-linux-gnu/qtcreator/libExtensionSystem.so.4
#19 0x77fa54cd in 
ExtensionSystem::Internal::PluginManagerPrivate::loadPlugin(ExtensionSystem::PluginSpec*,
ExtensionSystem::PluginSpec::State) () from 
/usr/bin/../lib/x86_64-linux-gnu/qtcreator/libExtensionSystem.so.4
#20 0x77fa6650 in 
ExtensionSystem::Internal::PluginManagerPrivate::loadPlugins() ()
from /usr/bin/../lib/x86_64-linux-gnu/qtcreator/libExtensionSystem.so.4
#21 0xeeb6 in ?? ()
#22 0x7633709b in __libc_start_main (main=0xca40, argc=1, 
argv=0x7fffe498, init=, fini=,
rtld_fini=, stack_end=0x7fffe488) at 
../csu/libc-start.c:308
#23 0xf50a in ?? ()

I tried the crude hack renaming the lib and symlinking to a newer
version, but that made things even worse. Besides, other programs
will be affected, too.


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

Kernel: Linux 4.19.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.ISO-8859-15, LC_CTYPE=en_GB.ISO-8859-15 
(charmap=ISO-8859-15) (ignored: LC_ALL set to en_GB.ISO-8859-15)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages qtcreator depends on:
ii  libbotan-2-9   2.9.0-2
ii  libc6  2.28-1
ii  libclang1-71:7.0.1-8
ii  libgcc11:8.3.0-7
ii  libgl1-mesa-glx [libgl1]   13.0.6-1+b2
ii  libllvm7   1:7.0.1-8
ii  libqbscore1.12 1.12.2+dfsg-2
ii  libqbsqtprofilesetup1.12   1.12.2+dfsg-2
ii  libqt5concurrent5  5.11.3+dfsg1-1
ii  libqt5core5a [qtbase-abi-5-11-3]   5.11.3+dfsg1-1
ii  libqt5designer55.11.3-4
ii  libqt5designercomponents5  5.11.3-4
ii  libqt5gui5 5.11.3+dfsg1-1
ii  libqt5help55.11.3-4
ii  libqt5network5 5.11.3+dfsg1-1
ii  libqt5printsupport55.11.3+dfsg1-1
ii  libqt5qml5 [qtdeclarative-abi-5-11-2]  5.11.3-4
ii  libqt5quick5   5.11.3-4
ii  libqt5quickwidgets55.11.3-4
ii  libqt5script5  5.11.3+dfsg-3
ii  libqt5serialport5  5.11.

Bug#926180: scilab: FTBFS on all

[Rebecca N. Palmer]

On 23/05/2019 22:35, Rebecca N. Palmer wrote:
It now looks like these are actually "valgrind doesn't understand Java 
memory allocation"


The Valgrind documentation says --smc-check=all should fix this, but it 
doesn't.


Ubuntu has a 6.0.2 package that builds in Debian, but it still has this 
bug.  (Same stacktrace as 6.0.1 under gdb; once a different one (below) 
under valgrind --smc-check=all --error-limit=no 
--log-file=scilab_valgrind%n .)


WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.scilab.modules.jvm.LibraryPath 
(file:/home/rnpalmer/Debian/builds/stackbuild/scilab-6.0.2/modules/jvm/jar/org.scilab.modules.jvm.jar) 
to field java.lang.ClassLoader.sys_paths
WARNING: Please consider reporting this to the maintainers of 
org.scilab.modules.jvm.LibraryPath
WARNING: Use --illegal-access=warn to enable warnings of further illegal 
reflective access operations

WARNING: All illegal access operations will be denied in a future release
terminate called after throwing an instance of 
'GiwsException::JniCallMethodException'

  what():  Exception when calling Java method :
 at java.base/java.util.TreeMap.getEntry(TreeMap.java:350)
 at java.base/java.util.TreeMap.containsKey(TreeMap.java:231)
 at java.base/java.util.TreeSet.contains(TreeSet.java:234)
 at 
org.scilab.modules.graphic_objects.utils.MenuBarBuilder$MenuBarConfigurationHandler.invoke(Unknown 
Source)

 at com.sun.proxy.$Proxy0.addMenus(Unknown Source)
 at 
org.scilab.modules.graphic_objects.utils.MenuBarBuilder.buildMenuBar(Unknown 
Source)
 at 
org.scilab.modules.graphic_objects.utils.MenuBarBuilder.buildFigureMenuBar(Unknown 
Source)
 at 
org.scilab.modules.graphic_objects.CallGraphicController.buildFigureMenuBar(Unknown 
Source)


 at java.base/java.util.TreeMap.getEntry(TreeMap.java:350)
 at java.base/java.util.TreeMap.containsKey(TreeMap.java:231)
 at java.base/java.util.TreeSet.contains(TreeSet.java:234)
 at 
org.scilab.modules.graphic_objects.utils.MenuBarBuilder$MenuBarConfigurationHandler.invoke(Unknown 
Source)

 at com.sun.proxy.$Proxy0.addMenus(Unknown Source)
 at 
org.scilab.modules.graphic_objects.utils.MenuBarBuilder.buildMenuBar(Unknown 
Source)
 at 
org.scilab.modules.graphic_objects.utils.MenuBarBuilder.buildFigureMenuBar(Unknown 
Source)
 at 
org.scilab.modules.graphic_objects.CallGraphicController.buildFigureMenuBar(Unknown 
Source)


A fatal error has been detected by Scilab.
Please check your user-defined functions (or external module ones) 
should they appear in the stack trace.

Otherwise you can report a bug on http://bugzilla.scilab.org/ with:
 * a sample code which reproduces the issue
 * the result of [a, b] = getdebuginfo()
 * the following information:
[rnpalmer-laptop:05275] Signal: Aborted (6)
[rnpalmer-laptop:05275] Signal code:  (-6)

Call stack:
   1: 0x377bb   
(/lib/x86_64-linux-gnu/libc.so.6)
   2: 0x22535   
(/lib/x86_64-linux-gnu/libc.so.6)
   3: 0x8c983  < > 
(/usr/lib/x86_64-linux-gnu/libstdc++.so.6)
   4: 0x928c6  < > 
(/usr/lib/x86_64-linux-gnu/libstdc++.so.6)
   5: 0x92901  < > 
(/usr/lib/x86_64-linux-gnu/libstdc++.so.6)
   6: 0x92b34  < > 
(/usr/lib/x86_64-linux-gnu/libstdc++.so.6)
   7: 0x1e0d6 
int)> 
(/home/rnpalmer/Debian/builds/stackbuild/scilab-6.0.2/modules/graphic_objects/.libs/libscigraphic_objects.so.6)
   8: 0x6525e   
(/home/rnpalmer/Debian/builds/stackbuild/scilab-6.0.2/modules/graphics/.libs/libscigraphics.so.6)
   9: 0x66180   
(/home/rnpalmer/Debian/builds/stackbuild/scilab-6.0.2/modules/graphics/.libs/libscigraphics.so.6)
  10: 0x49c33   
(/home/rnpalmer/Debian/builds/stackbuild/scilab-6.0.2/modules/graphics/.libs/libscigraphics.so.6)
  11: 0x1b9694  
(/home/rnpalmer/Debian/builds/stackbuild/scilab-6.0.2/modules/.libs/libscilab-cli.so.6)
  12: 0x2360
(/home/rnpalmer/Debian/builds/stackbuild/scilab-6.0.2/.libs/scilab-bin)
  13: 0x2409b  <__libc_start_main> 
(/lib/x86_64-linux-gnu/libc.so.6)
  14: 0x2dfa   < > 
(/home/rnpalmer/Debian/builds/stackbuild/scilab-6.0.2/.libs/scilab-bin)

End of stack

Last error (of ~10,000) in the Valgrind log:
==5275== Invalid write of size 4
==5275==at 0x2D810AE8: ???
==5275==by 0x5907680: ??? (in 
/usr/lib/jvm/java-11-openjdk-amd64/lib/server/libjvm.so)
==5275==by 0x5976F8C: ??? (in 
/usr/lib/jvm/java-11-openjdk-amd64/lib/server/libjvm.so)
==5275==by 0x597874D: ??? (in 
/usr/lib/jvm/java-11-openjdk-amd64/lib/server/libjvm.so)
==5275==by 0x4EA1C12: JNIEnv_::CallObjectMethod(_jobject*, 
_jmethodID*, ...) (jni.h:906)
==5275==by 0x4EA0CBB: 
GiwsException::JniException::retrieveExceptionName[abi:cxx11](JNIEnv_*) 
(GiwsException.cpp:217)
==5275==by 0x4EA0F6F: 
GiwsException::JniException::JniException(JNIEnv_*) (GiwsException.cpp:37)
==5275==by 0x4EA1830: 
GiwsException::JniCallMethodException::JniCallMethodException(JNIEnv_*) 
(GiwsException.cpp:288)
==5275==by 0x4FF50BF: 
org_scilab_modules_graphic_objects::CallGraphicController::buildFigureMenuBar(JavaVM_*, 
int)

Bug#929512: calibre: Kobo database version 152 not supported

[Vincas Dargis]

Package: calibre
Version: 3.39.1+dfsg-3
Severity: normal
Tags: upstream

Dear Maintainer,

Recently I have update my Kobo Glo software to 4.14.12777 (5ef5fd856f,
5/3/19) and now Calibre shows this message:

```
calibre, version 3.39.1
WARNING: Failed: Kobo database version unsupported - See details

Your Kobo is running an updated firmware/database version. As calibre
does not know about this updated firmware, database editing is disabled,
to prevent corruption. You can still send books to your Kobo with
calibre,  but deleting books and managing collections is disabled. If
you are willing to experiment and know how to reset your Kobo to Factory
defaults, you can override this check by right clicking the device icon
in calibre and selecting "Configure this device" and then the  "Attempt
to support newer firmware" option. Doing so may require you to perform a
factory reset of your Kobo.
Device database version: 152.
Device firmware version: (4, 14, 12777)
```

I am able to upload books though.


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

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

Versions of packages calibre depends on:
ii  calibre-bin  3.39.1+dfsg-3
ii  fonts-liberation 1:1.07.4-9
ii  imagemagick  8:6.9.10.23+dfsg-2.1
ii  imagemagick-6.q16 [imagemagick]  8:6.9.10.23+dfsg-2.1
ii  libjpeg-turbo-progs  1:1.5.2-2+b1
ii  libjs-coffeescript   1.12.8~dfsg-4
ii  libjs-mathjax2.7.4+dfsg-1
ii  optipng  0.7.7-1
ii  poppler-utils0.71.0-4
ii  python-apsw  3.27.2-r1-1
ii  python-chardet   3.0.4-3
ii  python-cherrypy3 8.9.1-2
ii  python-css-parser1.0.4-1
ii  python-cssselect 1.0.3-1
ii  python-cssutils  1.0.2-2
ii  python-dateutil  2.7.3-3
ii  python-dbus  1.2.8-3
ii  python-feedparser5.2.1-1
ii  python-html5-parser  0.4.5-1
ii  python-html5lib  1.0.1-1
ii  python-lxml  4.3.3-2
ii  python-markdown  3.0.1-3
ii  python-mechanize 1:0.2.5-3
ii  python-msgpack   0.5.6-1+b1
ii  python-netifaces 0.10.4-1+b1
ii  python-pil   5.4.1-2
ii  python-pkg-resources 40.8.0-1
ii  python-pyparsing 2.2.0+dfsg1-2
ii  python-pyqt5 5.11.3+dfsg-1+b3
ii  python-pyqt5.qtsvg   5.11.3+dfsg-1+b3
ii  python-pyqt5.qtwebkit5.11.3+dfsg-1+b3
ii  python-regex 0.1.20190207-1
ii  python-routes2.4.1-1
ii  python2.72.7.16-2
ii  xdg-utils1.1.3-1

Versions of packages calibre recommends:
ii  python-dnspython  1.16.0-1

Versions of packages calibre suggests:
pn  python-unrardll  

-- no debconf information

Bug#929297: minissdpd: CVE-2019-12106

[Chris Lamb]

Hey,

> > The following vulnerability was published for minissdpd.
> > 
> > CVE-2019-12106[0]:
> > | The updateDevice function in minissdpd.c in MiniUPnP MiniSSDPd 1.4 and
> > | 1.5 allows a remote attacker to crash the process due to a Use After
> > | Free vulnerability.
[…]
> Chris, thanks for your proposal to update Stretch, I very much
> appreciate it.

Another gentle ping, security team?


Best wishes,

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

Bug#929482: cacti: After apt-get install cacti, the installation stated something old version DB(?) and does not proceed.

[Paul Gevers]

Control: tags -1 moreinfo

Hi ISHIKAWA,

Thanks for reporting issues you encounter.

On 24-05-2019 13:00, ISHIKAWA,chiaki wrote:

dbconfig-generate-include is part of dbconfig-common. Can you check that
you have a file
/usr/sbin/dbconfig-generate-include?

Are you by any chance running a usr-merged setup?

Paul



signature.asc
Description: OpenPGP digital signature

Bug#929513: marsshooter: Segfaults a few seconds after starting

[Jacob Nevins]

Package: marsshooter
Version: 0.7.6-3
Severity: important

When I start marsshooter, either from the desktop menu or command line,
it runs for a few seconds (13-18s in my tests), and then segfaults.

Before it dies it's displaying the main menu with a game demo in the
background, and playing music. I haven't spotted a pattern to when it
dies.

If I manage to start a tutorial before it segfaults, it seems I can
carry on playing that as long as I like until I go back to the main menu
(shortly after which, it will segfault). Being in the options menu, or
trying to start a new proper game, is not sufficient. (I've not
succeeded in getting past the game setup screen fast enough to see if
being in a proper game would stop the segfault.)

My screen is 1680x1050 (but it still segfaults if I'm running it in a
small window). I'm running Xfce. My graphics setup is as follows:

$ inxi -G
Graphics:
  Device-1: AMD RV710 [Radeon HD 4550] driver: radeon v: kernel 
  Display: x11 server: X.Org 1.20.3 driver: ati,radeon 
  unloaded: fbdev,modesetting,vesa resolution: 1680x1050~60Hz 
  OpenGL: renderer: AMD RV710 (DRM 2.50.0 / 4.19.0-5-amd64 LLVM 7.0.1) 
  v: 3.3 Mesa 18.3.4 

Here is a rubbish backtrace with no debug symbols, in case it's useful.
I'll try to get one with debug symbols later, if I remember.

(gdb) bt full
#0  0x7f50157c27f4 in ?? () from /lib/x86_64-linux-gnu/libgcc_s.so.1
No symbol table info available.
#1  0x7f50157c2ca6 in ?? () from /lib/x86_64-linux-gnu/libgcc_s.so.1
No symbol table info available.
#2  0x7f50157c35c7 in _Unwind_Resume ()
   from /lib/x86_64-linux-gnu/libgcc_s.so.1
No symbol table info available.
#3  0x5568ad09def0 in NoSpecial::radius() const ()
No symbol table info available.
#4  0xbf7ca95e439b58b8 in ?? ()
No symbol table info available.
#5  0x4223e3a2be24d537 in ?? ()
No symbol table info available.
#6  0x43d72748c297b58e in ?? ()
No symbol table info available.
#7  0xbfeec96cc2af18c8 in ?? ()
No symbol table info available.
#8  0x3ebea57bbdf2df33 in ?? ()
No symbol table info available.
#9  0x422437eebf307a55 in ?? ()
No symbol table info available.
#10 0x3ebf078a40270722 in ?? ()
No symbol table info available.
#11 0x3f3ed6823cc24c29 in ?? ()
No symbol table info available.
#12 0x3f80bf2a67f4 in ?? ()
No symbol table info available.
#13 0xa1b90e8dcbd98500 in ?? ()
No symbol table info available.
#14 0x5568ad143b90 in ?? ()
No symbol table info available.
#15 0x5568adc24728 in ?? ()
No symbol table info available.
#16 0x5568adc110a0 in ?? ()
No symbol table info available.
#17 0x7ffe773a7a90 in ?? ()
No symbol table info available.
#18 0x0001 in ?? ()
No symbol table info available.
#19 0x in ?? ()
No symbol table info available.

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

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

Versions of packages marsshooter depends on:
ii  fonts-dejavu 2.37-1
ii  fonts-gargi  2.0-4
ii  fonts-tlwg-waree 1:0.7.1-1
ii  fonts-wqy-microhei   0.2.0-beta-3
ii  libc62.28-10
ii  libfribidi0  1.0.5-3.1
ii  libgcc1  1:8.3.0-6
ii  libgl1   1.1.0-1
ii  libsfml-audio2.5 2.5.1+dfsg-1
ii  libsfml-graphics2.5  2.5.1+dfsg-1
ii  libsfml-system2.52.5.1+dfsg-1
ii  libsfml-window2.52.5.1+dfsg-1
ii  libstdc++6   8.3.0-6
ii  libtag1v51.11.1+dfsg.1-0.3
ii  marsshooter-data 0.7.6-3

marsshooter recommends no packages.

marsshooter suggests no packages.

-- no debconf information

Bug#929514: csmash FTCBFS: configures for the build architecture

[Helmut Grohne]

Source: csmash
Version: 0.6.6-6.8
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

csmash fails to cross build from source, because it does not pass --host
to ./configure. The easiest way of fixing that - using dh_auto_configure
- gets a long way. But csmash still uses a broken, oudated, embedded
copy of AM_PATH_GTK_2_0. Please remove that copy or update and register
it. The attached patch solves the --host part.

Helmut
diff --minimal -Nru csmash-0.6.6/debian/changelog csmash-0.6.6/debian/changelog
--- csmash-0.6.6/debian/changelog   2016-09-28 20:17:03.0 +0200
+++ csmash-0.6.6/debian/changelog   2019-05-23 18:13:30.0 +0200
@@ -1,3 +1,10 @@
+csmash (0.6.6-6.9) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Address FTCBFS: Use dh_auto_configure.
+
+ -- Helmut Grohne   Thu, 23 May 2019 18:13:30 +0200
+
 csmash (0.6.6-6.8) unstable; urgency=medium
 
   * Non-maintainer upload.
diff --minimal -Nru csmash-0.6.6/debian/rules csmash-0.6.6/debian/rules
--- csmash-0.6.6/debian/rules   2016-09-28 20:17:03.0 +0200
+++ csmash-0.6.6/debian/rules   2019-05-23 18:13:29.0 +0200
@@ -19,12 +19,7 @@
CFLAGS="-O2" \
CXXFLAGS="-O2" \
LIBS="-lpthread" \
-   ./configure \
-   --prefix=/usr   \
-   --bindir=/usr/games \
-   --sysconfdir=/etc   \
-   --infodir=/usr/share/info   \
-   --mandir=/usr/share/man
+   dh_auto_configure -- --bindir=/usr/games
 
$(MAKE)
 

Bug#929433: lintian: warn on suspicious usage of dpkg-architecture variables

[Mattia Rizzolo]

On Sat, May 25, 2019 at 09:56:15AM +0200, Graham Inggs wrote:
> How about emitting an info level tag when one of the less common
> dpkg-architecture variables is used, and proving some hints regarding
> the correct usage?

No, please don't.

tags of kind "this is unusual, are you really sure you want to do just
that?" are god only if the rate of false positives is really low.  This
is not the case.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#927348: unblock: salt/2018.3.4+dfsg1-2

[Paul Gevers]

Control: tags -1 confirmed moreinfo

Hi Benjamin,

On 24-05-2019 15:38, Benjamin Drung wrote:
> I would like to upload that proposed version to unstable.

Please go ahead and remove the moreinfo tag when the package is build
and installed.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#929017: mutt: undefined behavior on huge integer in a RFC 2231 header

[Chris Lamb]

tags 929017 + pending patch
thanks

I've uploaded mutt 1.10.1-2.1 to DELAYED/5:
  
  mutt (1.10.1-2.1) unstable; urgency=medium
  
* Non-maintainer upload.
* Apply patch from upstream to prevent undefined behaviour when
  parsing invalid Content-Disposition mail headers. The atoi() function was
  being called on a number which can potentially overflow and thus can have
  security implications depending on the atoi() implementation.
  (Closes: #929017)

The full debdiff is attached.


Regards,

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

 changelog |   11 +++
 patches/series|1 +
 patches/upstream/929017-atoi-undefined-behavior.patch |   18 ++
 3 files changed, 30 insertions(+)

diff -Nru mutt-1.10.1/debian/changelog mutt-1.10.1/debian/changelog
--- mutt-1.10.1/debian/changelog2018-08-07 09:31:52.0 +0100
+++ mutt-1.10.1/debian/changelog2019-05-25 09:57:12.0 +0100
@@ -1,3 +1,14 @@
+mutt (1.10.1-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Apply patch from upstream to prevent undefined behaviour when
+parsing invalid Content-Disposition mail headers. The atoi() function was
+being called on a number which can potentially overflow and thus can have
+security implications depending on the atoi() implementation.
+(Closes: #929017)
+
+ -- Chris Lamb   Sat, 25 May 2019 09:57:12 +0100
+
 mutt (1.10.1-2) unstable; urgency=low
 
   [ Jonathan Nieder ]
diff -Nru mutt-1.10.1/debian/patches/series mutt-1.10.1/debian/patches/series
--- mutt-1.10.1/debian/patches/series   2018-08-07 09:31:15.0 +0100
+++ mutt-1.10.1/debian/patches/series   2019-05-25 09:57:12.0 +0100
@@ -12,3 +12,4 @@
 upstream/905551-oauthbearer-imap.patch
 upstream/905551-oauthbearer-smtp.patch
 upstream/905551-oauthbearer-refresh.patch
+upstream/929017-atoi-undefined-behavior.patch
diff -Nru 
mutt-1.10.1/debian/patches/upstream/929017-atoi-undefined-behavior.patch 
mutt-1.10.1/debian/patches/upstream/929017-atoi-undefined-behavior.patch
--- mutt-1.10.1/debian/patches/upstream/929017-atoi-undefined-behavior.patch
1970-01-01 01:00:00.0 +0100
+++ mutt-1.10.1/debian/patches/upstream/929017-atoi-undefined-behavior.patch
2019-05-25 09:57:12.0 +0100
@@ -0,0 +1,18 @@
+https://gitlab.com/muttmua/mutt/commit/3b6f6b829718ec8a7cf3eb6997d86e83e6c38567
+
+--- mutt-1.10.1.orig/rfc2231.c
 mutt-1.10.1/rfc2231.c
+@@ -147,7 +147,12 @@ void rfc2231_decode_parameters (PARAMETE
+   encoded = (*t == '*');
+   *t = '\0';
+ 
+-  index = atoi (s);
++  /* RFC 2231 says that the index starts at 0 and increments by 1,
++ thus an overflow should never occur in a valid message, thus
++ the value INT_MAX in case of overflow does not really matter
++ (the goal is just to avoid undefined behavior). */
++  if (mutt_atoi (s, &index))
++index = INT_MAX;
+ 
+   conttmp = rfc2231_new_parameter ();
+   conttmp->attribute = p->attribute;

Bug#929515: smokeping: CSS and js files not found

[Keith Edmunds]

Package: smokeping
Version: 2.7.3-2
Severity: important

System was upgraded from Stretch to Buster, with smokeping working on Stretch.

After the upgrade, it's evident from the display that there is a CSS problem.

Chrome devtools reports:

GET http://ws.midnighthax.com/cgi-bin/css/smokeping-screen.css net::ERR_ABORTED 
404 (Not Found)

...and more, similar.

The file exists:

$ ls -l $(locate smokeping-screen.css)
-rw-r--r-- 1 root root 4596 Feb 24 00:54 
/usr/share/smokeping/www/css/smokeping-screen.css

So, this appears to be some kind of path issue.

Keith

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

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

Versions of packages smokeping depends on:
ii  adduser3.118
ii  debianutils4.8.6.1
ii  exim4-daemon-light [mail-transport-agent]  4.92-7
ii  fping  4.2-1
ii  libcgi-fast-perl   1:2.13-1
ii  libconfig-grammar-perl 1.12-2
ii  libdigest-hmac-perl1.03+dfsg-2
ii  libjs-cropper  1.2.2-1
ii  libjs-prototype1.7.1-3
ii  libjs-scriptaculous1.9.0-2
ii  librrds-perl   1.7.1-1
ii  libsnmp-session-perl   1.14~git20130523.186a005-4
ii  liburi-perl1.76-1
ii  libwww-perl6.36-2
ii  lsb-base   10.2019031300
ii  perl   5.28.1-6
ii  ucf3.0038+nmu1

Versions of packages smokeping recommends:
ii  apache2 [httpd-cgi]  2.4.38-3
ii  dnsutils 1:9.11.5.P4+dfsg-5
ii  echoping 6.0.2-10
ii  libsocket6-perl  0.29-1+b1

Versions of packages smokeping suggests:
ii  curl   7.64.0-3
pn  libauthen-radius-perl  
ii  libio-socket-ssl-perl  2.060-3
ii  libnet-dns-perl1.19-1
pn  libnet-ldap-perl   
pn  libnet-telnet-perl 
ii  openssh-client 1:7.9p1-10

-- Configuration Files:
/etc/smokeping/config.d/Alerts changed:
*** Alerts ***
to = k...@midnighthax.com
from = r...@midnighthax.com
+someloss
type = loss
pattern = >0%,*12*,>0%,*12*,>0%
comment = loss 3 times  in a row

/etc/smokeping/config.d/General changed:
*** General ***
owner= Keith Edmunds
contact  = k...@midnighthax.com
mailhost = 10.0.0.1
cgiurl   = http://ws.midnighthax.com/cgi-bin/smokeping.cgi
syslogfacility = local0
@include /etc/smokeping/config.d/pathnames

/etc/smokeping/config.d/Targets changed:
*** Targets ***
probe = FPing
menu = Top
title = Network Latency Grapher
remark = Welcome to the SmokePing website of The Cage
+ Local
menu = Local
title = Local Network
++ LocalMachine
title = ws.midnighthax.com
host = localhost
++ Firewall
title = Firewall
host = 10.0.0.2
alerts = someloss
++ Woodlands
title = Woodlands
host = 10.0.0.1
alerts = someloss
++ ddwrt
title = ddwrt   
host = 10.0.0.43
alerts = someloss
+ Remote
menu = Remote Systems
title = Remote Systems
++ Google
title = Google
host = google.com
++ Eden
title = Icinga Monitor
host = eden.tiger-computing.co.uk
alerts = someloss
++ BBC
title = BBC
host = bbc.co.uk
alerts = someloss

/etc/smokeping/smokeping_secrets [Errno 13] Permission denied: 
'/etc/smokeping/smokeping_secrets'

-- no debconf information

Bug#929487: unblock: dmarc-cat/0.9.2-4

[Paul Gevers]

Control: tags -1 moreinfo confirmed

On Fri, 24 May 2019 10:54:24 -0400 =?utf-8?Q?Antoine_Beaupr=C3=A9?=
 wrote:
> unblock dmarc-cat/0.9.2-4

That isn't available to unblock at the moment.

Please upload to unstable and remove the moreinfo tag when it is build
and installed.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#929516: [project] Please provide onion services using next-gen (v3) onion addresses

[Dirk Heinrichs]

Package: project
Version: current
adresses
Severity: normal

--- Please enter the report below this line. ---
Some time ago the tor project introduced 56 character long, next-gen
(v3) onion addresses, which also utilize stronger cryptography.
However, Debian is still using v2 onion addresses for its onion
services.

Please (also) provide the onion services using v3 addresses.

--- System information. ---
Architecture: 
Kernel:   Linux 4.19.0-4-amd64

Debian Release: 10.0
  500 testing vwakviie2ienjx6t.onion 
  500 testing sgvtcaew4bxjd7ln.onion 

--- Package information. ---
Package's Depends field is empty.

Package's Recommends field is empty.

Package's Suggests field is empty.




-- 
Dirk Heinrichs
GPG Public Key: D01B367761B0F7CE6E6D81AAD5A2E54246986015
Sichere Internetkommunikation: http://www.retroshare.org
Privacy Handbuch: https://www.privacy-handbuch.de 


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

Bug#929511: qtcreator: Segfault on start

[Alexander Kernozhitsky]

Hello,

I am using Qt Creator on Buster and don't see any problems on start.

BTW, why do you have /usr/lib/x86_64-linux-gnu/libLLVM-3.7.so.1? I searched on 
packages.debian.org and I didn't find the package with such library for amd64. 
Is it the old package that was manually installed or it didn't get removed on 
updates?

-- 
Alexander Kernozhitsky

Bug#929518: quodlibet: Quodlibet ignores usb devices

[Olivier]

Package: quodlibet
Version: 4.2.1-1
Severity: normal

Dear Maintainer,

Quodlibet ignores usb devices, (can't be scanned neither music transfered)



-- System Information:
Debian Release: 10.0
  APT prefers testing
  APT policy: (990, 'testing'), (980, 'stable'), (100, 'unstable')
Architecture: amd64 (x86_64)

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

Versions of packages quodlibet depends on:
ii  exfalso  4.2.1-1
ii  gir1.2-gst-plugins-base-1.0  1.14.4-1
ii  gir1.2-gstreamer-1.0 1.14.4-1
ii  gir1.2-keybinder-3.0 0.3.2-1
ii  gstreamer1.0-alsa1.14.4-1
ii  gstreamer1.0-plugins-base1.14.4-1
ii  gstreamer1.0-plugins-good1.14.4-1
ii  gstreamer1.0-plugins-ugly1.14.4-1
ii  gstreamer1.0-pulseaudio  1.14.4-1
ii  python3  3.7.2-1

Versions of packages quodlibet recommends:
ii  gir1.2-gtksource-3.0   3.24.9-2
ii  gir1.2-webkit2-4.0 2.24.1-2
ii  gnome-shell [notification-daemon]  3.30.2-9
ii  notification-daemon3.20.0-4
ii  python3-dbus   1.2.8-3
ii  python3-pyinotify  0.9.6-1

Versions of packages quodlibet suggests:
ii  gstreamer1.0-plugins-bad  1.14.4-1+b1

-- no debconf information

Bug#929517: unblock: gpsd/3.17-7

[Bernd Zeimetz]

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

Hi release-team,

please unblock package gpsd

Lisandro Damián Nicanor Pérez Meyer reported, that it is unnecessary
hard for an admin to enable gpsd to start at boot time (instead
of relying on udev to handle it).

I think this should be fixed for buster.

Patch is attached.

Thanks,

bernd


unblock gpsd/3.17-7

-- 
 Bernd ZeimetzDebian GNU/Linux Developer
 http://bzed.dehttp://www.debian.org
 GPG Fingerprint: ECA1 E3F2 8E11 2432 D485  DD95 EB36 171A 6FF9 435F
diff --git a/debian/changelog b/debian/changelog
index 16bb69795..4d554b0d0 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,13 @@
+gpsd (3.17-7) unstable; urgency=medium
+
+  [ Lisandro Damián Nicanor Pérez Meyer ]
+  * [ffb32ff8] Allow gpsd.service to be enabled by the admin at boot time.
+Be sure to keep it disabled. The admin needs to explicitely start
+it if needed.
+Closes: #928681
+
+ -- Bernd Zeimetz   Sat, 25 May 2019 11:55:30 +0200
+
 gpsd (3.17-6) unstable; urgency=medium
 
   * [0a8e4e18] Pull json fixes from upstream to fix a stack-based
diff --git a/debian/patches/full-systemd-support 
b/debian/patches/full-systemd-support
index 4624e110a..0fd20724c 100644
--- a/debian/patches/full-systemd-support
+++ b/debian/patches/full-systemd-support
@@ -1,6 +1,6 @@
 --- a/systemd/gpsd.service
 +++ b/systemd/gpsd.service
-@@ -7,9 +7,7 @@ After=chronyd.service
+@@ -7,8 +7,7 @@ After=chronyd.service
  [Service]
  Type=forking
  EnvironmentFile=-/etc/default/gpsd
@@ -9,5 +9,4 @@
 +ExecStart=/usr/sbin/gpsd $GPSD_OPTIONS $DEVICES
  
  [Install]
--WantedBy=multi-user.target
- Also=gpsd.socket
+ WantedBy=multi-user.target
diff --git a/debian/rules b/debian/rules
index e458b9ca1..7e7e5a6fe 100755
--- a/debian/rules
+++ b/debian/rules
@@ -190,7 +190,8 @@ binary: install-stamp
dh_installdocs 
dh_installman 
dh_installmenu 
-   dh_systemd_enable -pgpsd
+   dh_installsystemd -pgpsd --restart-after-upgrade gpsdctl@.service 
gpsd.socket
+   dh_installsystemd -pgpsd --no-enable --no-start gpsd.service
dh_installinit
dh_systemd_start -pgpsd --restart-after-upgrade
dh_installexamples 

Bug#926481: stretch-pu: package open-vm-tools/2:10.1.5-5055683-4+deb9u2

[Bernd Zeimetz]

Hi Salvatore,

On 4/26/19 10:06 PM, Salvatore Bonaccorso wrote:
> Hi Bernd,
> 
> On Sat, Apr 13, 2019 at 09:56:16PM +0100, Adam D. Barratt wrote:
>> Control: tags -1 + confirmed
>>
>> On Fri, 2019-04-05 at 23:15 +0200, Bernd Zeimetz wrote:
>>> as discuassed with the security team, I'd like to fix #925959
>>> with the next stable pointrelease. The proposed debdiff is attached.
>>>
>>
>> Please go ahead.
> 
> Did you saw the the ack from Adam? It is now unfortunately too late
> for this upcoming point release, but would then be possible for the
> next one.

yes, unfortunately I was pretty busy, so it took some time :(

Uploaded a few seconds ago.

Bernd


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

Bug#926242: jenkins.debian.org: Please test reproducibility status of Debian Installer images

[Colin Watson]

On Fri, May 24, 2019 at 06:56:35PM -0700, Vagrant Cascadian wrote:
> Colin Watson removed it back in 2011:
> 
>   
> https://salsa.debian.org/installer-team/debian-installer/commit/fa965c32ca8bfa2ff14886c6f0dca131532815c7
> 
> commit fa965c32ca8bfa2ff14886c6f0dca131532815c7
> Author: Colin Watson 
> Date:   Mon Mar 14 18:08:25 2011 +
> 
> Skip the option field in sources.list lines, if present.  
>  
> 
> diff --git a/build/util/gen-sources.list.udeb 
> b/build/util/gen-sources.list.udeb   
> index e86b4fa66..9f140100e 100755
> --- a/build/util/gen-sources.list.udeb
> +++ b/build/util/gen-sources.list.udeb
> @@ -36,6 +36,7 @@ get_mirrors() {
> [ -s $file ] || continue
> grep '^deb[[:space:]]' $file | \
>grep -v '^deb[[:space:]]\+cdrom:' | \  
>  
> +  sed 's,^deb \[[^]]*\] ,deb ,' | \
>grep -v 
> '\(security.debian.org\|volatile.debian.\(net\|org\)\)' | \   
>   
>grep '[[:space:]]main' | \
>awk '{print $1 " " $2}' | \
> 
> 
> Happen to remember what it breaks to have these present? If it was a
> workaround, perhaps it is no longer needed?

I'm not certain even after going through my IRC and email logs around
that time, but given the timing I suspect that it was a workaround for
multiarch systems where sources.list contained some lines with
[arch=...] options to limit them to only some architectures.  I don't
remember exactly how this broke the d-i build; I assume it must have
done at the time or I wouldn't have made that change.

It would be worth somebody trying out a d-i build on a system with this
kind of configuration to see if it still breaks, but otherwise I suspect
we can drop this.

-- 
Colin Watson   [cjwat...@debian.org]

Bug#929511: qtcreator: Segfault on start

[subhuman]

For some reason unknown to me there are several packages still depending on 
this special version of libLLVM. When I try to remove it, qtcreator is listed 
among them. As is xorg - which prevents me from performing the `apt-get remove`.


On Sat, 25 May 2019 12:59:16 +0300 Alexander Kernozhitsky  
wrote:
> Hello,
>
> I am using Qt Creator on Buster and don't see any problems on start.
>
> BTW, why do you have /usr/lib/x86_64-linux-gnu/libLLVM-3.7.so.1? I searched on
> packages.debian.org and I didn't find the package with such library for amd64.
> Is it the old package that was manually installed or it didn't get removed on
> updates?
>
> --
> Alexander Kernozhitsky
>
>
>
>

Bug#929519: unblock: matrix-synapse/0.99.5.1-2

[Andrej Shadura]

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

Please unblock package matrix-synapse.

Originally, 0.99 was meant to be the last version before 1.0, but due
to a bunch of issues discovered since then, some of them
security-related, new incompatible room format was introduced in 0.99.5.
This is going to mean 0.99.2 currently in Debian buster is going to only
see limited usefulness, as users would basically need to immediately
upgrade it to a version from backports to be able to federate with other
servers.

Since matrix-synapse is a leaf package used only by people running their
own Matrix homeservers, I believe the impact of such a late upstream
version bump is going to be minimal; I also believe than rather than
leaving an old version in buster, it might make sense to remove it, if
the newer one doesn’t get in.

I’m attaching a git diff between patches-applied trees of 0.99.2-5
currently in buster and 0.99.5.1-1 currently in experimental (the
version in testing ships with a few security fixes backported from
0.99.3). The proposed 0.99.5.1-2 would be a no-change upload with just
a changelog bump.

Thanks for considering this.

unblock matrix-synapse/0.99.5.1-2

References:

[1]: https://matrix.org/blog/2019/05/21/synapse-0-99-5-1-released
[2]: https://matrix.org/blog/2019/05/24/final-countdown-to-1-0

-- 
Cheers,
  Andrej

Bug#929151: netdata-core: version in stretch-backports newer than version in buster

[Paul Gevers]

Hi backports team,

On Sat, 18 May 2019 10:22:10 +0200 Andreas Beckmann  wrote:
> Package: netdata-core
> Version: 1.12.0-1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> Control: close -1 1.12.1-2
> 
> Hi,
> 
> during a test with piuparts I noticed your package fails to upgrade from
> 'stretch-backports' to 'buster' due to a version oerdering violation.
> 
> netdata-core | 1.12.0-1| testing   | amd64, arm64, armel, 
> armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
> netdata-core | 1.12.1-2~bpo9+1 | stretch-backports | amd64, arm64, armel, 
> armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
> netdata-core | 1.12.2-2| unstable  | amd64, arm64, armel, 
> armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
> netdata-core | 1.14.0-1| experimental  | amd64, arm64, armel, 
> armhf, i386, mips, mips64el, mipsel, ppc64el, s390x

The current version of netdata-core in unstable is very unlikely to get
unblocked. What do you suggest to do in such a case, remove the package
from stretch-backports? It doesn't comply with the backports policy.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#928911: grub-efi-amd64: destroys EFI partition despite being told not to

[Colin Watson]

Control: reassign -1 grub-installer

On Mon, May 13, 2019 at 12:10:07AM +0200, Adam Borowski wrote:
> Just did a d-i bare-metal test run; installing to another disk, with the
> obvious requirement of not damaging the primary system.  Thus, I explicitly
> marked all relevant partitions (EFI, sys, and swap) as "do not use".
> 
> Yet the newly installed system overwrote the ESP anyway.  It also did so in
> a way that neither the old nor new system could be booted (no entries for
> any of the existing two systems were created, and I did not succeed booting
> manually).
> 
> Disks present in the system:
> * NVME-SSD:
>   [all "do not use"] ESP (fat), sys (btrfs), swap
> * 4x NVME-Optane:
>   MD RAID0 <- new system (d-i test) was installed here
> * HDD:
>   * another old system (ext4) -- x32, BIOS-boot
>   * boot partition for the d-i test run
>   * data partition (btrfs)
> 
> It can be argued that the setup above may be a bit overcomplicated (thus
> the installer being confused might be understandable).
> But I insist that disregarding the explicit "do not use" and scribbling
> over anyway is a severe bug.

This seems as though it can only reasonably be fixed in grub-installer,
since it's what explicitly calls grub-install here.
grub-efi-amd64.postinst won't independently call grub-install in this
setup (since /boot/efi won't be mounted in the installed system, so the
-d "/boot/efi/EFI/$bootloader_id" test will fail).  Reassigning.

When installing in grub-efi* mode, I think it would probably be
reasonable for grub-installer to only call grub-install if
$ROOT/boot/efi is a mountpoint.

-- 
Colin Watson   [cjwat...@debian.org]

Bug#928756: debian-edu-config | Hand out all subdomains configured by default to all LTSP clients. (ca3b521f)

[Wolfgang Schweer]

On Fri, May 24, 2019 at 01:49:02PM +, Holger Levsen wrote:
> looks ok, though for getting it into Buster there should be a bug 
> report, severity normal or wishlist..

IMO this change should be reconsidered.

The search-domain entry is missing in the LTSP client's /etc/resolv.conf 
in this case (dedicated LTSP client network), because LTSP uses 
'ipappend 3' in its PXE configuration.

Debian Edu uses 'ipappend 2' for the main network.

So if out of site specific wishes LTSP clients in their dedicated subnet 
should be added via GOsa with also DNS enabled, 'ipappend 2' should be 
used instead of 'ipappend 3'.

This can be set permanently by editing the default file 
/opt/ltsp//boot/pxelinux.cfg/ltsp-NBD and adjusting 
/opt/ltsp//etc/ltsp/update-kernels.conf (last line) and finally 
running 'ltsp-update-kernels'.

Please check.

Wolfgang


signature.asc
Description: PGP signature

Bug#928756: debian-edu-config | Hand out all subdomains configured by default to all LTSP clients. (ca3b521f)

[Dominik George]

>So if out of site specific wishes LTSP clients in their dedicated
>subnet 
>should be added via GOsa with also DNS enabled, 'ipappend 2' should be 
>used instead of 'ipappend 3'.

I strongly believe that every single host on a network should have a DNS record.

-nik

Bug#929520: mariadb-server-10.1: does not start after upgrade to 10.1.38 deb9u1

[harrim4n]

Package: mariadb-server-10.1
Version: 10.1.38-0+deb9u1
Severity: important

Dear Maintainer,

after an upgrade from 10.1.37-0+deb9u1 to 10.1.38-0+deb9u1, the mysql
server does not start anymore via systemd.
Manually starting the mysql server works fine.
systemctl status mariadb.service displays

● mariadb.service - MariaDB 10.1.38 database server
   Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor
   preset: enabled)
  Active: failed (Result: exit-code) since Sat 2019-05-25 14:58:09
  CEST; 1s ago
   Docs: man:mysqld(8)
  https://mariadb.com/kb/en/library/systemd/
Process: 17160 ExecStartPre=/usr/bin/install -m
755 -o mysql -g root -d /var/run/mysqld
(code=exited, status=127)
 Main PID: 12930 (code=exited, status=127)
   CPU: 0

   May 25 14:58:09 webconfire systemd[1]:
   Starting MariaDB 10.1.38 database
   server...
   May 25 14:58:09 webconfire systemd[1]:
   mariadb.service: Control process exited,
   code=exited status=127
   May 25 14:58:09 webconfire systemd[1]:
   Failed to start MariaDB 10.1.38 database
   server.
   May 25 14:58:09 webconfire systemd[1]:
   mariadb.service: Unit entered failed
   state.
   May 25 14:58:09 webconfire systemd[1]:
   mariadb.service: Failed with result
   'exit-code'.

Manually editing the systemd service file in /lib/systemd/system/ to
remove all ExecStartPre lines also does not work.
The service file is not modified, the same issue occurs even after
removing the service file and forcing a reinstall.
This user (
https://unix.stackexchange.com/questions/490916/systemd-status-127-for-usr-bin-install-when-trying-to-start-mariadb)
had the same issue, but apparently no fix was found.

-- System Information:
Debian Release: 9.9
  APT prefers stable
  APT policy: (900, 'stable'), (500, 'testing')
Architecture: amd64 (x86_64)

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

Versions of packages mariadb-server-10.1 depends on:
ii  adduser   3.115
ii  debconf [debconf-2.0] 1.5.61
ii  galera-3  25.3.19-2
ii  gawk  1:4.1.4+dfsg-1
ii  init-system-helpers   1.48
ii  iproute2  4.9.0-1+deb9u1
ii  libaio1   0.3.110-3
ii  libc6 2.28-10
ii  libdbi-perl   1.636-1+b1
ii  libpam0g  1.1.8-3.6
ii  libstdc++66.3.0-18+deb9u1
ii  libsystemd0   232-25+deb9u11
ii  lsb-base  9.20161125
ii  lsof  4.89+dfsg-0.1
ii  mariadb-client-10.1   10.1.38-0+deb9u1
ii  mariadb-common10.1.38-0+deb9u1
ii  mariadb-server-core-10.1  10.1.38-0+deb9u1
ii  passwd1:4.4-4.1
ii  perl  5.24.1-3+deb9u5
ii  psmisc22.21-2.1+b2
ii  rsync 3.1.2-1+deb9u2
ii  socat 1.7.3.1-2+deb9u1
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages mariadb-server-10.1 recommends:
ii  libhtml-template-perl  2.95-2

Versions of packages mariadb-server-10.1 suggests:
pn  mailx   
pn  mariadb-test
pn  netcat-openbsd  
pn  tinyca  

-- debconf information:
  mariadb-server-10.1/old_data_directory_saved:
  mariadb-server-10.1/nis_warning:
  mariadb-server-10.1/postrm_remove_databases: false

Bug#928756: debian-edu-config | Hand out all subdomains configured by default to all LTSP clients. (ca3b521f)

[Wolfgang Schweer]

On Sat, May 25, 2019 at 03:02:16PM +0200, Dominik George wrote:
> >So if out of site specific wishes LTSP clients in their dedicated
> >subnet 
> >should be added via GOsa with also DNS enabled, 'ipappend 2' should be 
> >used instead of 'ipappend 3'.

> I strongly believe that every single host on a network should have a 
> DNS record.

My mail wasn't about DNS record yes/no. It's about PXE configuration to 
propagate DHCP settings properly in the dedicated LTSP network if a DNS 
record is available.

Wolfgang


signature.asc
Description: PGP signature

Bug#929521: Conficts in upgrade to 418.74-1 with optimus setup

[ghisvail]

Package: src:nvidia-graphics-drivers
Version: 418.74-1
Severity: important

Dear Debian NVIDIA maintainers,

I attempted to upgrade my laptop (a Dell Inspiron 7580 with a GeForce
MX150) running Debian Buster and configured with nvidia-driver,
bumblebee-nvidia and primus, plus the necessary 32-bit libs to run
Steam. So far, upgrades have been smooth until version 418.56-2.

Sadly, version 418.74-1 is a different story. Running `apt upgrade`
shows the following output:

```
Les paquets suivants contiennent des dépendances non satisfaites :
 nvidia-nonglvnd-vulkan-common : Est en conflit avec: libgl1-nvidia-
legacy-390xx-glvnd-glx mais 390.116-1 devra être installé
 Est en conflit avec: libgl1-nvidia-
legacy-390xx-glvnd-glx:i386 mais 390.116-1 devra être installé
 primus : Casse: libgl1-nvidia-legacy-390xx-glvnd-glx (>= 0) mais
390.116-1 devra être installé
  Casse: libgl1-nvidia-legacy-390xx-glvnd-glx:i386 (>= 0) mais
390.116-1 devra être installé
```

Which indicates conflicts for nvidia-nonglvnd-vulkan-common and
breakage
for Primus. What surprises me is the upgrade wishing to pull part of
the
legacy nvidia driver, whilst I am definitely using the current one.

I have also tried to just remove the whole NVIDIA stack and start over
as when I initially setup the machine. Running `apt get install
bumblebee-nvidia` shows the following output :

```
Les paquets suivants ont été installés automatiquement et ne sont plus
nécessaires :
  libegl-mesa0:i386 libegl1:i386 libgbm1:i386 libopengl0
libopengl0:i386 libwayland-server0:i386 libxcb-xfixes0:i386 nvidia-egl-
common nvidia-egl-icd nvidia-egl-icd:i386
Veuillez utiliser « sudo apt autoremove » pour les supprimer.
Les paquets supplémentaires suivants seront installés :
  bbswitch-dkms bumblebee libegl-nvidia-legacy-390xx0:i386 libegl1-
nvidia libegl1-nvidia:i386 libegl1-nvidia-legacy-390xx:i386 libgl1-
nvidia-glx libgl1-nvidia-glx:i386 libgl1-nvidia-legacy-390xx-glx:i386
  libgles-nvidia-legacy-390xx1:i386 libgles-nvidia-legacy-390xx2:i386
libglx-nvidia-legacy-390xx0:i386 libnvidia-legacy-390xx-cfg1 libnvidia-
legacy-390xx-cfg1:i386 libnvidia-legacy-390xx-eglcore:i386
  libnvidia-legacy-390xx-glcore libnvidia-legacy-390xx-glcore:i386
libnvidia-legacy-390xx-ml1 nvidia-driver-libs-nonglvnd nvidia-driver-
libs-nonglvnd:i386 nvidia-driver-libs-nonglvnd-i386:i386
  nvidia-legacy-390xx-alternative nvidia-legacy-390xx-driver-libs-
nonglvnd:i386 nvidia-legacy-390xx-kernel-dkms nvidia-legacy-390xx-
kernel-support nvidia-legacy-390xx-nonglvnd-vulkan-icd:i386
  nvidia-legacy-390xx-vdpau-driver nvidia-nonglvnd-vulkan-common
nvidia-nonglvnd-vulkan-icd nvidia-nonglvnd-vulkan-icd:i386 nvidia-
settings-legacy-390xx primus primus-libs primus-libs-ia32:i386 socat
  xserver-xorg-video-nvidia-legacy-390xx
Paquets suggérés :
  vulkan-utils:i386 vulkan-utils
Paquets recommandés :
  nvidia-legacy-390xx-driver | libnvidia-legacy-390xx-cuda1 libgl1-
nvidia-legacy-390xx-glvnd-glx | libgl1-nvidia-legacy-390xx-glx nvidia-
legacy-390xx-driver
Les paquets suivants seront ENLEVÉS :
  libgl1-nvidia-glvnd-glx libgl1-nvidia-glvnd-glx:i386 nvidia-driver-
libs nvidia-driver-libs:i386 nvidia-driver-libs-i386:i386 nvidia-
vulkan-common nvidia-vulkan-icd nvidia-vulkan-icd:i386
Les NOUVEAUX paquets suivants seront installés :
  bbswitch-dkms bumblebee bumblebee-nvidia libegl-nvidia-legacy-
390xx0:i386 libegl1-nvidia libegl1-nvidia:i386 libegl1-nvidia-legacy-
390xx:i386 libgl1-nvidia-glx libgl1-nvidia-glx:i386
  libgl1-nvidia-legacy-390xx-glx:i386 libgles-nvidia-legacy-390xx1:i386 
libgles-nvidia-legacy-390xx2:i386 libglx-nvidia-legacy-390xx0:i386
libnvidia-legacy-390xx-cfg1 libnvidia-legacy-390xx-cfg1:i386
  libnvidia-legacy-390xx-eglcore:i386 libnvidia-legacy-390xx-glcore
libnvidia-legacy-390xx-glcore:i386 libnvidia-legacy-390xx-ml1 nvidia-
driver-libs-nonglvnd nvidia-driver-libs-nonglvnd:i386
  nvidia-driver-libs-nonglvnd-i386:i386 nvidia-legacy-390xx-alternative 
nvidia-legacy-390xx-driver-libs-nonglvnd:i386 nvidia-legacy-390xx-
kernel-dkms nvidia-legacy-390xx-kernel-support
  nvidia-legacy-390xx-nonglvnd-vulkan-icd:i386 nvidia-legacy-390xx-
vdpau-driver nvidia-nonglvnd-vulkan-common nvidia-nonglvnd-vulkan-icd
nvidia-nonglvnd-vulkan-icd:i386 nvidia-settings-legacy-390xx primus
  primus-libs primus-libs-ia32:i386 socat xserver-xorg-video-nvidia-
legacy-390xx
0 mis à jour, 37 nouvellement installés, 8 à enlever et 0 non mis à
jour.
```

Once again, it is very suprising that apt now wants to install all
these
legacy nvidia driver packages, yet even remove `nvidia-driver-libs`.

Looking at the change log of version 418.74-1, the only item that may
be
causing this issue is : "Tune Recommends to smoothen some upgrade paths
on i386."

Should you need further information, please ask.

Cheers,
Ghislain

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

Kernel: Linux 

Bug#929433: lintian: warn on suspicious usage of dpkg-architecture variables

[Chris Lamb]

Hi Graham,

> I think this tag would be more useful for maintainers preparing new
> packages, than for finding existing problems in the archive.

They could still be false-positives for new packages, no? As in, I'm
not really seeing your distinction here between fresh vs. existing
packaging.

> How about emitting an info level tag when one of the less common
> dpkg-architecture variables is used, and proving some hints regarding
> the correct usage?

Mmm, but unless I'm missing something these could still have false-
positives too? Can you give some concrete examples for this so we
aren't talking too much in the abstract here?


Regards,

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

Bug#926509: keepassxc: Please update to Version 2.4.0

[Felix Zielcke]

Am Samstag, den 06.04.2019, 12:28 +0200 schrieb Julian Andres Klode:
> On Sat, Apr 06, 2019 at 11:23:29AM +0200, Philipp Kolmann wrote:
> > Package: keepassxc
> > Version: 2.3.4+dfsg.1-1
> > Severity: wishlist
> > 
> > Hi,
> > 
> > could you please update keepassxc to the latest release 2.4.0.
> > 
> > https://keepassxc.org/blog/2019-03-19-2.4.0-released/
> 
> No, we're in freeze.
> 

Hi,

it would be nice if you could make an upload to experimental. That
would be independent of the freeze.

Thanks
Felix

Bug#928756: debian-edu-config | Hand out all subdomains configured by default to all LTSP clients. (ca3b521f)

[Dominik George]

>My mail wasn't about DNS record yes/no.

Yes, it was, when you said that the wish for working DNS were site-specific :).

-nik

Bug#929522: yuma123: homepage is wrong (points to source repository)

[Jonas Smedegaard]

Source: yuma123
Version: 2.11-1
Severity: minor

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Homepage points to https://sourceforge.net/projects/yuma123/
which is not really the _homepage_ but the source repository.

Please update package metadata to instead point to the homepage
which according to http://yuma123.org/wiki/index.php/Yuma_Installation_Guide is
http://www.netconfcentral.org/

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlzpUTgACgkQLHwxRsGg
ASEjbw//SRwK4TVNSG3EA9MrvvTJpEIFTOW/iOTUENWSYLAAopVmjkT+LlpYB8Jk
Tcc9ndT/MfMQDQK38FG1fjkX6GcAg0CrPdmhuASfw8Z901fkMUTUZb4Nxoj2oIER
rp4IcbsvBW1FxtvHqa67swLdKafh+1kVOE01MZp/zu1j6PFEs5oq+T/0RZiUujDv
9Cna3DVTXr48c6UOAMxW8D9qq40DQReFpsOG7pSQUiZanlhsdn9+fslvv+vuOqct
tI6HhUfvAPtDq+XBjvb3tFzdUxbhFjQjb5B5J7aWeq7s/qUAeLSHqX4m2Rngpnl0
Y8Yc4pr3ddx4IcoQwpZf42nmFue2cJpJa5rK7Gyf6kOK5HauXtR9D3cE4frdi5Iq
D4VcQyF60zUKSoDglIXsQBugdJJDuo/UFoFNDIl/oJwQZAyDz6EDbUMH05v4E2Z/
V10D1VcyieCg7Datlx2kuOp8lqDYmMQWoYAhkVFp63SRuek8pIDhc9r58N7PLcE5
cmtkDu4lowprSXhLDljtC6fWR47fK7ed+4S6BuorYrLZ0Ra8op8lJB4SsdiUixfi
sBsXGvHESyNBzqN4KIB4bLgxiNOtnUhHEtLnUsXOjaQvJz9f/MxWhpkBJFkkIf+6
rZWABF98FHr9idvBiCmJZO3ubgYd7oD85gPWg2FsbNjq1uOTZUY=
=buCY
-END PGP SIGNATURE-

Bug#929433: lintian: warn on suspicious usage of dpkg-architecture variables

[Graham Inggs]

On Sat, 25 May 2019 at 10:48, Mattia Rizzolo  wrote:
> tags of kind "this is unusual, are you really sure you want to do just
> that?" are god only if the rate of false positives is really low.  This
> is not the case.

Per one of Helmut's examples, all occurrences of --libdir=.*DEB_BUILD
were incorrect and should have used DEB_HOST_MULTIARCH instead.

Bug#924403: modem-manager-gui: "double free or corruption (out)" after enabling mobile broadband

[Graham Inggs]

Hi

Neither Alex (upstream) nor I have been able to reproduce this problem.

Please try with modem-manager-gui 0.0.19.1-2, which includes the fix
for #922608 and let us know if you are still experiencing it.

Regards
Graham

Bug#929487: unblock: dmarc-cat/0.9.2-4

[Antoine Beaupré]

Control: tags -1 -moreinfo

On 2019-05-25 11:27:28, Paul Gevers wrote:
> That isn't available to unblock at the moment.

Oops. Somehow forgot to upload.

> Please upload to unstable and remove the moreinfo tag when it is build
> and installed.

It's been "ACCEPTED" so i presume it will trickle down everywhere...

a.
-- 
The illusion of freedom will continue as long as it's profitable to
continue the illusion. At the point where the illusion becomes too
expensive to maintain, they will just take down the scenery, they will
pull back the curtains, they will move the tables and chairs out of
the way and you will see the brick wall at the back of the theater.
 - Frank Zappa

Bug#929523: rhythmbox: Rhythmbox doesn't display mpc files tag

[Olivier]

Package: rhythmbox
Version: 3.4.3-2
Severity: normal

Dear Maintainer,

Rhythmbox doesn't display mpc files tag



-- System Information:
Debian Release: 10.0
  APT prefers testing
  APT policy: (990, 'testing'), (980, 'stable'), (100, 'unstable')
Architecture: amd64 (x86_64)

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

Versions of packages rhythmbox depends on:
ii  dbus1.12.12-1
ii  gstreamer1.0-plugins-base   1.14.4-1
ii  gstreamer1.0-plugins-good   1.14.4-1
ii  gstreamer1.0-x  1.14.4-1
ii  libc6   2.28-10
ii  libglib2.0-02.58.3-1
ii  libgstreamer-plugins-base1.0-0  1.14.4-1
ii  libgstreamer1.0-0   1.14.4-1
ii  libgtk-3-0  3.24.5-1
ii  libpeas-1.0-0   1.22.0-4
ii  librhythmbox-core10 3.4.3-2
ii  libx11-62:1.6.7-1
ii  media-player-info   24-2
ii  rhythmbox-data  3.4.3-2

Versions of packages rhythmbox recommends:
ii  avahi-daemon   0.7-4+b1
ii  gnome-shell [notification-daemon]  3.30.2-9
ii  gstreamer1.0-plugins-ugly  1.14.4-1
ii  gstreamer1.0-pulseaudio1.14.4-1
ii  gvfs-backends  1.38.1-3
ii  notification-daemon3.20.0-4
ii  rhythmbox-plugins  3.4.3-2
ii  yelp   3.31.90-1

Versions of packages rhythmbox suggests:
pn  gnome-codec-install  
ii  gnome-control-center 1:3.30.3-1
ii  gstreamer1.0-plugins-bad 1.14.4-1+b1
ii  rhythmbox-plugin-cdrecorder  3.4.3-2

-- no debconf information

Bug#929524: clementine: Clementine doesn't detect usb devices

[Olivier]

Package: clementine
Version: 1.3.1+git609-g623a53681+dfsg-1
Severity: normal

Dear Maintainer,

Clementine can't see usb devices, ntfs ot vfat partitions. Using a
".is_audio_player" file has no effect on its behaviour



-- System Information:
Debian Release: 10.0
  APT prefers testing
  APT policy: (990, 'testing'), (980, 'stable'), (100, 'unstable')
Architecture: amd64 (x86_64)

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

Versions of packages clementine depends on:
ii  gstreamer1.0-plugins-base   1.14.4-1
ii  gstreamer1.0-plugins-good   1.14.4-1
ii  gstreamer1.0-plugins-ugly   1.14.4-1
ii  libc6   2.28-10
ii  libcdio18   2.0.0-2
ii  libchromaprint1 1.4.3-3
ii  libcrypto++65.6.4-8
ii  libfftw3-double33.3.8-2
ii  libgcc1 1:8.3.0-6
ii  libgdk-pixbuf2.0-0  2.38.1+dfsg-1
ii  libglib2.0-02.58.3-1
ii  libgpod40.8.3-13
ii  libgstreamer-plugins-base1.0-0  1.14.4-1
ii  libgstreamer1.0-0   1.14.4-1
ii  libimobiledevice6   1.2.1~git20181030.92c5462-1
ii  liblastfm5-11.0.9-1+b11
ii  libmtp9 1.1.16-2
ii  libmygpo-qt5-1  1.1.0-3
ii  libplist3   2.0.1~git20190104.3f96731-1
ii  libprojectm2v5  2.1.0+dfsg-4+b4
ii  libprotobuf17   3.6.1.3-2
ii  libpulse0   12.2-4
ii  libqt5concurrent5   5.11.3+dfsg1-1
ii  libqt5core5a5.11.3+dfsg1-1
ii  libqt5dbus5 5.11.3+dfsg1-1
ii  libqt5gui5  5.11.3+dfsg1-1
ii  libqt5network5  5.11.3+dfsg1-1
ii  libqt5opengl5   5.11.3+dfsg1-1
ii  libqt5sql5  5.11.3+dfsg1-1
ii  libqt5widgets5  5.11.3+dfsg1-1
ii  libqt5x11extras55.11.3-2
ii  libqt5xml5  5.11.3+dfsg1-1
ii  libsqlite3-03.27.2-2
ii  libstdc++6  8.3.0-6
ii  libtag1v5   1.11.1+dfsg.1-0.3
ii  libx11-62:1.6.7-1
ii  projectm-data   2.1.0+dfsg-4
ii  zlib1g  1:1.2.11.dfsg-1

Versions of packages clementine recommends:
ii  gstreamer1.0-alsa1.14.4-1
ii  gstreamer1.0-pulseaudio  1.14.4-1

Versions of packages clementine suggests:
ii  gstreamer1.0-plugins-bad  1.14.4-1+b1

-- no debconf information

Bug#929525: primus: brakes libgl1-nvidia-legacy-390xx-glvnd-glx

[Stefan Tsanev]

Package: primus
Version: 0~20150328-7

Hi,

Currently after apt update && apt upgrade primus brakes these packages
(which i don't have installed on the system anyway):

primus : Brakes: libgl1-nvidia-legacy-390xx-glvnd-glx (>= 0) but it
will be installed 390.116-1
  Brakes: libgl1-nvidia-legacy-390xx-glvnd-glx:i386 (>= 0) but
it will be installed 390.116-1

Also these packages are conflicting:

nvidia-nonglvnd-vulkan-common : In conflict with:
libgl1-nvidia-legacy-390xx-glvnd-glx but it will be installed
390.116-1
 In conflict with:
libgl1-nvidia-legacy-390xx-glvnd-glx:i386 but it will be installed
390.116-1


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

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

Versions of packages primus depends on:
ii  bumblebee 3.2.1-20
ii  primus-libs   0~20150328-7
ii  socat 1.7.3.2-2
ii  xserver-xorg-core 2:1.20.3-1
ii  xserver-xorg-video-intel  2:2.99.917+git20180925-2

Versions of packages primus recommends:
ii  primus-libs-ia32  0~20150328-7

Versions of packages primus suggests:
ii  nvidia-driver-libs-nonglvnd  418.56-2


Here is my dpkg -l | grep nvidia :

ii  bumblebee-nvidia3.2.1-20
 amd64NVIDIA Optimus support using the proprietary NVIDIA
driver
ii  glx-alternative-nvidia  1.0.0
 amd64allows the selection of NVIDIA as GLX provider
ii  libegl-nvidia0:amd64418.56-2
 amd64NVIDIA binary EGL library
ii  libegl-nvidia0:i386 418.56-2
 i386 NVIDIA binary EGL library
ii  libegl1-nvidia:amd64418.56-2
 amd64NVIDIA binary EGL library (non-GLVND variant)
ii  libegl1-nvidia:i386 418.56-2
 i386 NVIDIA binary EGL library (non-GLVND variant)
ii  libgl1-nvidia-glx:amd64 418.56-2
 amd64NVIDIA binary OpenGL/GLX library (non-GLVND variant)
ii  libgl1-nvidia-glx:i386  418.56-2
 i386 NVIDIA binary OpenGL/GLX library (non-GLVND variant)
ii  libgles-nvidia1:amd64   418.56-2
 amd64NVIDIA binary OpenGL|ES 1.x library
ii  libgles-nvidia1:i386418.56-2
 i386 NVIDIA binary OpenGL|ES 1.x library
ii  libgles-nvidia2:amd64   418.56-2
 amd64NVIDIA binary OpenGL|ES 2.x library
ii  libgles-nvidia2:i386418.56-2
 i386 NVIDIA binary OpenGL|ES 2.x library
ii  libglx-nvidia0:amd64418.56-2
 amd64NVIDIA binary GLX library
ii  libglx-nvidia0:i386 418.56-2
 i386 NVIDIA binary GLX library
ii  libnvidia-cbl:amd64 418.56-2
 amd64NVIDIA binary Vulkan ray tracing (cbl) library
ii  libnvidia-cfg1:amd64418.56-2
 amd64NVIDIA binary OpenGL/GLX configuration library
ii  libnvidia-eglcore:amd64 418.56-2
 amd64NVIDIA binary EGL core libraries
ii  libnvidia-eglcore:i386  418.56-2
 i386 NVIDIA binary EGL core libraries
ii  libnvidia-fatbinaryloader:amd64 418.56-2
 amd64NVIDIA FAT binary loader
ii  libnvidia-glcore:amd64  418.56-2
 amd64NVIDIA binary OpenGL/GLX core libraries
ii  libnvidia-glcore:i386   418.56-2
 i386 NVIDIA binary OpenGL/GLX core libraries
ii  libnvidia-glvkspirv:amd64   418.56-2
 amd64NVIDIA binary Vulkan Spir-V compiler library
ii  libnvidia-glvkspirv:i386418.56-2
 i386 NVIDIA binary Vulkan Spir-V compiler library
ii  libnvidia-ml1:amd64 418.56-2
 amd64NVIDIA Management Library (NVML) runtime library
ii  libnvidia-ptxjitcompiler1:amd64 418.56-2
 amd64NVIDIA PTX JIT Compiler
ii  libnvidia-rtcore:amd64  418.56-2
 amd64NVIDIA binary Vulkan ray tracing (rtcore) library
ii  nvidia-alternative  418.56-2
 amd64allows the selection of NVIDIA as GLX provider
ii  nvidia-driver-libs-nonglvnd:amd64   418.56-2
 amd64NVIDIA metapackage (non-GLVND OpenGL/GLX/EGL/GLES
libraries)
ii  nvidia-driver-libs-nonglvnd:i386418.56-2
 i386 NVIDIA metapackage (non-GLVND OpenGL/GLX/EGL/GLES
libraries)
ii  nvidia-driver-libs-nonglvnd-i386:i386   418.56-2
 i386 NVIDIA metapackage (non-GLVND OpenGL/EGL/etc. 32-bit
libraries)
ii  

Bug#927108: [ftp.debian.org] Release file for jessie-updates is incomplete

[Fabian Pietsch]

Package: ftp.debian.org
Followup-For: Bug #927108

It also contains a broken Version: field which leads to "unusual"
ouput from "apt-cache policy", (which confuses my custom
nagios/icinga2 check).

* http://ftp.debian.org/debian/dists/jessie-updates/InRelease
> Origin: Debian
> Label: Debian
> Suite: oldstable-updates
> Version: label=Debian
> Codename: jessie-updates
> Date: Sat, 25 May 2019 14:30:54 UTC
> Architectures: amd64 armel armhf i386
> Components: 
> Description: Updated packages for Debian 8

The

> Version: label=Debian

becomes:

| release 
v=label=Debian,o=Debian,a=oldstable-updates,n=jessie-updates,l=Debian,c=main

(The v=label=Debian is where my check breaks. But,)
I guess the Version: field is simply broken. (?)

Regards, Fabian

Bug#929432: dpkg-source -b . command does not identify a module when it contains "."

[Pirate Praveen]

On Thu, 23 May 2019 16:00:06 +0200 Guillem Jover  wrote:
> You could simply symlink them instead?

Yes, there are workarounds but this will have to be done for every such case 
and everyone will have to do it as well.

> > I hope this can be fixed.
> 
> I think I'd rather not change the current behavior. But I guess could
> perhaps be otherwise convinced with solid arguments. Otherwise I'm
> planning on marking this wontfix and close in a bit.
> 
> 
> Thinking about this a bit more, I guess one option could be to make
> dpkg-source map these automatically. Say after #577113 is implemented,
> you'd list the component there as «foo.bar», and then dpkg-source
> would know to look for «.orig-foo-bar.» and then unpack as «foo.bar».
> I guess that would solve your problem w/o needing to change the
> accepted filename pattern. It would still be backwards incompatible
> though.

Yes, this will be a perfect solution.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Bug#929433: lintian: warn on suspicious usage of dpkg-architecture variables

[Graham Inggs]

On Sat, 25 May 2019 at 16:07, Chris Lamb  wrote:

> They could still be false-positives for new packages, no? As in, I'm
> not really seeing your distinction here between fresh vs. existing
> packaging.
>

Yes, there's definitely a risk of false positives.
But if a maintainer were about to upload a new package, or introduced
changes to an existing package, that used DEB_BUILD* or DEB_TARGET* instead
of DEB_HOST_MULTIARCH, I suspect the usage is most likely incorrect.

Mmm, but unless I'm missing something these could still have false-
> positives too? Can you give some concrete examples for this so we
> aren't talking too much in the abstract here?
>

Here are a couple I was able to find quickly:

https://salsa.debian.org/debichem-team/nwchem/commit/96a2bd29073d5f25c97fdf9ce0493857b31fcae0
https://salsa.debian.org/r-pkg-team/r-bioc-rhdf5lib/commit/00bd8caa6689bf048d4f0f654993b0402a74cedb

Bug#929526: xfonts-scalable: fails to install in lenny/i386: fmt: invalid width: `63482'

[Andreas Beckmann]

Package: xfonts-scalable
Version: 1:1.0.0-6
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts


Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Setting up xfonts-scalable (1:1.0.0-6) ...
  fmt: invalid width: `63482'
  fmt: invalid width: `63482'
  fmt: invalid width: `63482'
  dpkg: error processing xfonts-scalable (--configure):
   subprocess post-installation script returned error exit status 1
  Errors were encountered while processing:
   xfonts-scalable

It installs fine in squeeze/i386 with the version from squeeze.


cheers,

Andreas


xfonts-scalable_1:1.0.0-6.log.gz
Description: application/gzip

Bug#929216: RM: algotutor/0.8.6-2

[Georges Khaznadar]

Dear Paul, dear ftpmasters,

@Paul:
thank you for controlling this bug: reassigning it, adding moreinfo tag,
retitling it.

You are writing below that I should update the bug, "until then the bug
can be tagged as moreinfo".

But I fear that this bug is already tagged moreinfo.

@all:
I probably misunderstood something, so I beg your pardon if the next
lines are not appropriate.

To sum it up, my request was to remove the package algotutor from
unstable and testing, because during a recent check, I could not run
algotutor right like explained in the packaged documentation. Now it has
been removed from testing, and I am discovering that it can remain in
unstable:

I am checking it again; I discover that algotutor is working as
announced when the working directory is /usr/share/algotutor (which was
not clearly documented).

So, the removal of algotutor from testing is correct, since it cannot be
used by a random user who reads the manual page right now. However, the
removal from unstable is not necessary: I will fix the documentation to
make it clear how to run examples, and push a new version when Buster
will become the new stable release.

Best regards,   Georges.




Paul Gevers a écrit :
> Control: reassing -1 ftp.debian.org
> Control: tags -1 moreinfo
> Control: retitle -1 RM: algotutor -- ROM; abandoned upstream
> 
> On 20-05-2019 21:24, Paul Gevers wrote:
> > On 19-05-2019 12:22, Georges Khaznadar wrote:
> >> Package: release.debian.org
> >> Severity: normal
> >> User: release.debian@packages.debian.org
> >> Usertags: rm
> >>
> >> Unmaintained upstream, not usable inside debian/buster, low popcon
> > 
> > I notice you are the maintainer. You don't have any bugs against this
> > package, so what makes it unusable, i.e. what is the problem of shipping
> > this with buster? Do you really only want it out of buster, or removed
> > from Debian unstable as well? In the later case, this bug should be
> > reassigned to the ftp.debian.org pseudo package.
> 
> I got a private reply and I removed the package from buster. I asked
> Georges to update the bug with his rational for full removal (which he
> desires), until then the bug can be tagged as moreinfo.
> 
> Paul
> 




-- 
Georges KHAZNADAR et Jocelyne FOURNIER
22 rue des mouettes, 59240 Dunkerque France.
Téléphone +33 (0)3 28 29 17 70



signature.asc
Description: PGP signature

Bug#929527: /usr/sbin/xtables-nft-multi: restoring IP Tables with an self-defined chain segfaults in libnftnl.so

[Thomas Lamprecht]

Package: iptables
Version: 1.8.2-4
Severity: grave
File: /usr/sbin/xtables-nft-multi
Justification: renders package unusable by segfaulting on usage

Dear Maintainer,

First, it may be that this should be actually filed against nftables,
so I'd like to say sorry in advance if made noise to the wrong people.

Anyway, on a Debian Stretch system installed from latest weekly ISO
restoring a relative simple IP Table with a single "intermediate" chain
causes a segfaul and no restoration of said table.

Reproducer:
# cat simple-segv-table
*filter
:NEW-OUTPUT - [0:0]
-A OUTPUT -j NEW-OUTPUT
-F NEW-OUTPUT
-A NEW-OUTPUT -j ACCEPT
COMMIT

# iptables ./simple-segv-table
Segmentation fault

# dmesg | tail -1
[12860.813350] traps: iptables-restor[19173] general protection ip:7f4894682793 
sp:7ffcedc177d0 error:0 in libnftnl.so.11.0.0[7f4894677000+17000]

# addr2line -e /usr/lib/x86_64-linux-gnu/libnftnl.so.11.0.0  -fCi $(printf "%x" 
$[0x7f2cb9882793 - 0x7f2cb9877000])
nftnl_batch_is_supported
??:?

(hope that my addr2line foo isn't to much off)

Above example works just fine on a Debian Stretch 9.9 based machine.
As intially I produced this on a, let's say, far from minimal and a bit
Frankenstein'ed Buster, I installed the netinst weekly ISO again in a
QEMU/KVM backed VM, same outcome.

As said, this may well be an issue in the linked libnftnl shared
library, but could also be an issue from how iptables uses it, as I
produced the error by calling into a iptables provided binary I choose
to report it here (not sure if one can report against multiple
packages).

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

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

Versions of packages iptables depends on:
ii  libc62.28-10
ii  libip4tc01.8.2-4
ii  libip6tc01.8.2-4
ii  libiptc0 1.8.2-4
ii  libmnl0  1.0.4-2
ii  libnetfilter-conntrack3  1.0.7-1
ii  libnfnetlink01.0.1-3+b1
ii  libnftnl11   1.1.2-2
ii  libxtables12 1.8.2-4

Versions of packages iptables recommends:
ii  nftables  0.9.0-2

Versions of packages iptables suggests:
ii  kmod  26-1

-- no debconf information

Bug#924029: poppler: diff for NMU version 0.71.0-4.1

[Jonathan Wiltshire]

Control: tags 924029 + pending patch

Dear maintainer,

I've prepared an NMU for poppler (versioned as 0.71.0-4.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.


-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51

diff -Nru poppler-0.71.0/debian/changelog poppler-0.71.0/debian/changelog
--- poppler-0.71.0/debian/changelog	2019-05-23 21:18:49.0 +0100
+++ poppler-0.71.0/debian/changelog	2019-05-25 17:10:35.0 +0100
@@ -1,3 +1,11 @@
+poppler (0.71.0-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Prevent a crash due to null pointer dereferencing in
+goo/GooString.h (Closes: #924029)
+
+ -- Jonathan Wiltshire   Sat, 25 May 2019 17:10:35 +0100
+
 poppler (0.71.0-4) unstable; urgency=medium
 
   * CVE-2018-16646 (Closes: #909802)
diff -Nru poppler-0.71.0/debian/patches/bug924029-goostring-null-pointers.patch poppler-0.71.0/debian/patches/bug924029-goostring-null-pointers.patch
--- poppler-0.71.0/debian/patches/bug924029-goostring-null-pointers.patch	1970-01-01 01:00:00.0 +0100
+++ poppler-0.71.0/debian/patches/bug924029-goostring-null-pointers.patch	2019-05-25 17:09:50.0 +0100
@@ -0,0 +1,97 @@
+Subject: Make GooString constructible and assignable from null pointers again
+ since some of the code expects it.
+Origin: https://gitlab.freedesktop.org/poppler/poppler/commit/8f158da92c53ae16a368f844965f57ba8ffed77d
+Bug: https://gitlab.freedesktop.org/poppler/poppler/commit/8f158da92c53ae16a368f844965f57ba8ffed77d
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924029
+Reviewed-by: Jonathan Wiltshire 
+Applied-Upstream: yes
+Last-Update: 2019-05-25
+
+--- poppler-0.71.0.orig/goo/GooString.h
 poppler-0.71.0/goo/GooString.h
+@@ -60,7 +60,7 @@
+   GooString& operator=(const GooString &other) = delete;
+ 
+   // Create a string from a C string.
+-  explicit GooString(const char *sA) : std::string(sA) {}
++  explicit GooString(const char *sA) : std::string(sA ? sA : "") {}
+ 
+   // Zero-cost conversion from and to std::string
+   explicit GooString(const std::string& str) : std::string(str) {}
+@@ -70,18 +70,18 @@
+ 
+   // Create a string from  chars at .  This string
+   // can contain null characters.
+-  GooString(const char *sA, int lengthA) : std::string(sA, lengthA) {}
++  GooString(const char *sA, int lengthA) : std::string(sA ? sA : "", sA ? lengthA : 0) {}
+ 
+   // Create a string from  chars at  in .
+   GooString(const GooString *str, int idx, int lengthA) : std::string(*str, idx, lengthA) {}
+ 
+   // Set content of a string to .
+-  GooString* Set(const GooString *newStr) { assign(*newStr); return this; }
+-  GooString* Set(const char *newStr) { assign(newStr); return this; }
+-  GooString* Set(const char *newStr, int newLen) { assign(newStr, newLen); return this; }
++  GooString* Set(const GooString *newStr) { assign(newStr ? static_cast(*newStr) : std::string{}); return this; }
++  GooString* Set(const char *newStr) { assign(newStr ? newStr : ""); return this; }
++  GooString* Set(const char *newStr, int newLen) { assign(newStr ? newStr : "", newStr ? newLen : 0); return this; }
+ 
+   // Copy a string.
+-  explicit GooString(const GooString *str) : std::string(*str) {}
++  explicit GooString(const GooString *str) : std::string(str ? static_cast(*str) : std::string{}) {}
+   GooString *copy() const { return new GooString(this); }
+ 
+   // Concatenate two strings.
+--- poppler-0.71.0.orig/qt5/tests/check_goostring.cpp
 poppler-0.71.0/qt5/tests/check_goostring.cpp
+@@ -11,6 +11,7 @@
+ void testInsertData();
+ void testInsert();
+ void testFormat();
++void testFromNullptr();
+ };
+ 
+ void TestGooString::testInsertData_data()
+@@ -122,6 +123,42 @@
+ }
+ }
+ 
++void TestGooString::testFromNullptr()
++{
++  {
++GooString str{static_cast(nullptr)};
++QCOMPARE(str.getLength(), 0);
++  }
++
++  {
++GooString str;
++str.Set(static_cast(nullptr));
++QCOMPARE(str.getLength(), 0);
++  }
++
++  {
++GooString str{static_cast(nullptr)};
++QCOMPARE(str.getLength(), 0);
++  }
++
++  {
++GooString str{static_cast(nullptr), 0};
++QCOMPARE(str.getLength(), 0);
++  }
++
++  {
++GooString str;
++str.Set(static_cast(nullptr));
++QCOMPARE(str.getLength(), 0);
++  }
++
++  {
++GooString str;
++str.Set(static_cast(nullptr), 0);
++QCOMPARE(str.getLength(), 0);
++  }
++}
++
+ QTEST_GUILESS_MAIN(TestGooString)
+ #include "check_goostring.moc"
+ 
diff -Nru poppler-0.71.0/debian/patches/series poppler-0.71.0/debian/patches/series
--- poppler-0.71.0/debian/patches/series	2019-05-23 21:18:49.0 +0100
+++ poppler-0.71.0/debian/patches/series	2019-05-25 17:03:52.0 +0100
@@ -11,3 +11,4 @@
 CVE-2019-9200.patch
 CVE-2019-9631.patch
 CVE-2019-10873.patch
+bug9

Bug#929528: [arm64] Enable support for SCPI sensors

[Markus Geimer]

Package: src:linux
Version: 4.19.37-3
Severity: wishlist

Dear Maintainer,

Please consider adding the following Kconfig options for ARM64:

CONFIG_ARM_SCPI_PROTOCOL=m
CONFIG_SENSORS_ARM_SCPI=m
CONFIG_PLATFORM_MHU=m

This change has been successfully tested based on 4.19.37-3 on an Hardkernel
Odroid-C2 and makes the CPU temperature sensors available on that platform.
(Note that I don't have any other board to test this, but since it's all
modules it's probably quite safe.)

Thanks,
Markus

-- System Information:
Debian Release: 10.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: arm64 (aarch64)

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

Bug#929527: /usr/sbin/xtables-nft-multi: restoring IP Tables with an self-defined chain segfaults in libnftnl.so

[Thomas Lamprecht]

> [snip]
> Anyway, on a Debian Stretch system installed from latest weekly ISO
> restoring a relative simple IP Table with a single "intermediate" chain
> causes a segfaul and no restoration of said table.

sorry, above I meant: s/Stretch/Buster/

Bug#924787: Bug#926556: unblock: yubikey-personalization/1.19.3-3

[Bill Blough]

It appears that the needed changes are located in Salsa [1], and that the
release was prepared but not uploaded (since it's nowhere to be found).

This package is team maintained, and since it's not clear to me if the
rest of the team is aware of this issue, I'm CC'ing the team address in
this message.

If there's no response from nicoo or the rest of the team, I would like to go
ahead with an NMU, assuming that's permissible under these circumstances.


[1] 
https://salsa.debian.org/auth-team/yubikey-personalization/commits/debian/master



-- 
GPG: 5CDD 0C9C F446 BC1B 2509  8791 1762 E022 7034 CF84

Bug#929342: unblock: aqemu/0.9.2-2.2

[Jonathan Wiltshire]

Control: tag -1 moreinfo

Hi,

On Wed, May 22, 2019 at 09:49:33AM +0530, Abhijith PA wrote:
> I reported a RC bug (#927126) against aqemu. Though its actual
> maintainer is not active for years, a debian contributor (Alexis
> Murzeau) fixed and filed a RFS(#929180) for a NMU. I've tested the
> package and uploaded to the unstable.
> 
> diff:
> https://salsa.debian.org/amurzeau-guest/aqemu/commit/5ce9cf29186a1f5d6ddcd8994351161de5ec76a7.diff

>From that diff:

+@@ -761,37 +749,37 @@
+
+ void Network_Widget::on_TB_Help_clicked()
+ {
+-  // -net nic[,vlan=n][,macaddr=addr][,model=type][,name=name]
++  // -net nic[,macaddr=addr][,model=type][,name=name]
+   if( ui.CB_Network_Type->currentText() == "nic" )
+-  QMessageBox::information( this, tr("nic"), tr("-net 
nic[,vlan=n][,macaddr=addr][,model=type][,name=name] \nCreate a new Network 
Interface Card and connect it to VLAN n (n = 0 is the default). The NIC is an 
ne2k_pci by default on the PC target. Optionally, the MAC address can be 
changed to addr and a name can be assigned for use in monitor commands. If no 
\'-net\' option is specified, a single NIC is created. Qemu can emulate several 
different models of network card. Valid values for type are i82551, i82557b, 
i82559er, ne2k_pci, ne2k_isa, pcnet, rtl8139, e1000, smc91c111, lance and 
mcf_fec. Not all devices are supported on all targets. Use -net nic,model=? for 
a list of available devices for your target.") );
++  QMessageBox::information( this, tr("nic"), tr("-net 
nic[,macaddr=addr][,model=type][,name=name] \nCreate a new Network Interface 
Card and connect it to Virtual LAN n (n = 0 is the default). The NIC is an 
ne2k_pci by default on the PC target. Optionally, the MAC address can be 
changed to addr and a name can be assigned for use in monitor commands. If no 
\'-net\' option is specified, a single NIC is created. Qemu can emulate several 
different models of network card. Valid values for type are i82551, i82557b, 
i82559er, ne2k_pci, ne2k_isa, pcnet, rtl8139, e1000, smc91c111, lance and 
mcf_fec. Not all devices are supported on all targets. Use -net nic,model=? for 
a list of available devices for your target.") );

This might benefit from another read; it seems to remove the vlan parameter
but still refer to it in the text? It's worth checking through for any
other similar instances.

Thanks,

-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51

Bug#619409: insserv: /etc/init.d/.depend.* represent state, not configuration; please move to /lib

[Jesse Smith]

On Wed, 23 Mar 2011 09:33:46 -0700 Josh Triplett wrote:
>
> insserv generates makefile snippets in /etc/init.d/.depend.* with
> dependency information for init scripts. This doesn't represent
> configuration information, nor can the user modify it. Thus, it should
> go somewhere else on the root filesystem, such as /lib/insserv/depend.*
> .. That would avoid the need to ignore them in etckeeper, or care about
> the differences between successive versions.
>

After some consideration and debate, I believe this bug should be closed
as wontfix. For several reasons:

1. The makefiel-style dependency information is configuration data, not
a library or executable, so it doesn't belong in /lib. It may not belong
in /etc, but /lib would be a clear violation of FHS.

2. Despite the above claim, it is configuration information.

3. Despite the initial concern, the user can modify the data, it's
completely editable and human-readable.

I'm open to trying another location that might better suite everyone's
needs and FHS, but /lib is not a good match.

- Jesse

Bug#601054: Move /etc/init.d/.depend.* files under /var

[Jesse Smith]

As an update on this bug, since /var may not be mounted at boot time,
causing startpar to fail, this change has been reverted upstream. I am
going to suggest this bug can be closed.

- Jesse

Bug#549260: Appears to be fixed

[Jesse Smith]

This issue appears to be fixed in recent versions of Debian, such as
Jessie and Stretch. Suggest it can be closed.

- Jesse

Bug#929405: ITP: pveclib -- power vector library

[Gabriel F. T. Gomes]

On Fri, May 24 2019, Steven Munroe wrote:
> In the current state, these libraries are only required for unit tests, but
> could be used for applications that need those constant values.

OK, if it can be useful for applications, than it's probably better to
distribute it, right away.

> [...] So the current build is looking ahead to a configuration
> that provides a space vs performance trade-off.
> 
> Fro example muludq <
> https://munroesj52.github.io/vec__int128__ppc_8h.html#aee5c5b2998ef105b4c6f39739748ffa8>
> where the POWER8 implementation runs 132 bytes. It is even bigger for
> POWER7 and only 80 bytes for POWER9.
> 
> The threshold for in-lining is a matter of some debate.
> 
> So I expect that eventually pveclib will need the option to move some
> operations for some -mcpu= values to use library calls. And some
> performance oriented applications will want to inline every thing
> regardless.

OK.  All good points to ship the shared library.

> For now I want to make pveclib available as-is to users. Then if someone
> complains about code size we can add the controls/configuration to adjust.

As-is sounds good to me. :)

With this information, I think the package is ready to be submitted to
the Debian Archive.  However, since we are under the freeze, that might
take a while, but I'll get the process started.

Thanks, Steve!

Cheers,
Gabriel.

Bug#927723: sway: Please upload new upstream version

[iskrenx2]

Hi, thank you for your effort! 
But this missmatch and waiting for *next* version can go on forever ? 
Why we can't have Sway 1.0 _now_ or it will be skipped entirely ? 
I'm disappointed I can't help and wIll just have to wait. 
Wish you best of luck. 


Best Regards.


-

П.П. Разбра ли, че Яна щала да си прави сайт? Яна, от онази реклама. Виж сайт 
билдъра на СуперХостинг.БГ, за да си направиш сайт и ти.
 
https://www.superhosting.bg/site-builder.php?utm_source=mbg&utm_medium=cpm&utm_content=mail_footer&utm_campaign=newuser_campaign2019

Bug#929455: mark dmidecode Multi-Arch: foreign

[Jörg Frings-Fürst]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

tags 929455 + pending
thanks

Hello Helmut,

thank you for spending your time helping to make Debian better with
this bug report. 

I have applied your patch for the next release.

Many thanks

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

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

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


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

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


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

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAlzpi+QACgkQCfifPIyh
0l3s3w/+LeuAnImQi8+lzwdJJMLb3wKciITfjBBij7OR9Q/u8WvFdqqhRMgJvjqR
gyeSCnS8SJEkPu/OI7rkietCd40q0MFEyTiaS1pHavfX9j8cUdsUpdyLjOqvFcMc
7OgxvwNB07v9TTsdeL2i3fukTLhrKbaKRJ8mUrZfvl3VsYrmRrH/xxsC6fPIQDi5
G3Y89ZCCqeK5tzo7Gr0O9KHdNi4GhsEeeCI005HEuvkLxWe5+2aS74sN8gR7uNKd
HAFcPM3lxJaJIY1r02+R2/P+PFDWS3pdrmQKYZKKwwn7BTziELknLjskYC33xaOx
WXiC+IGdqQIFBZJc9DmBsL//kMvKMbqYmn+joSMwSrPe3iwo3jh0NP6Lqf786q8y
xCm9GMPvZ059NoRyFLig+Ebxabuzzun2iLSa7WD4yaXKmVmcYKqrXLtwGJXDMN68
y5KyV8QLDTA3Sq68HhWQfjYUr4GgYmyCt4ADJMyaixM/GGUbS+3ZbfhM1EJckAlN
lB3V28L6+vGMyJwd8snttSchYvzGPkbQ/Abej3BeuA/k7tOZfqbbjfElzbDTr3NN
s3SEtuF+TiDBLg7YoU6vmNYIG1HPL/1KCUvoc6K0cdlTErPD3xEU+CRaYKxp23AS
qMf6W4yFTRxXoI18uJwdbBVimVHHpCZJNWhxzpbKg3Mta8nRGoA=
=EaWB
-END PGP SIGNATURE-

Bug#924132: runit: Add support for runit in init-system-helpers

[Lorenz]

Sure, here is the link

https://salsa.debian.org/debian/init-system-helpers/merge_requests/10

Thanks

Il giorno ven 24 mag 2019 alle ore 19:59 Felipe Sateler 
ha scritto:

> Hi Lorenz
>
> On Tue, May 21, 2019, 11:42 Lorenzo Puliti  wrote:
>
>> Control: reassign 924132 init-system-helpers
>>
>> Dear init-system-helpers Maintainers,
>>
>>  here are a series of 5 commits that add support for runit-init into
>>  'update-rc.d', 'invoke-rc.d' and 'service' scripts.
>>
>>
>> https://salsa.debian.org/Lorenzo.ru.g-guest/init-system-helpers/commits/runit
>>
>>  This has been already reviewed by Dmitry Bogatov.
>>  If you don't have further question or requirements, can you upload to
>> experimental
>>  and then, after Buster release, to unstable?
>>
>
> Could you post the patches as a salsa MR? It would make for easier review.
>
>
> Saludos
>

Bug#928770: sqlite3: CVE-2019-5018: Window Function Remote Code Execution Vulnerability

[Robert Scott]

> Alternatively, it could be related to:
> https://www.sqlite.org/src/info/4feb3159c6bc3f7e33959
> 
> This was released as a part of 3.27.2 and looks like it has the right
> text as well.  What concerns me is that the ticket[0] is almost a week
> before TALOS's timeline for "Vendor patched" plus it mentioned "free
> that has not been malloc'ed" rather than "use after free".  That said,
> the test case examples for both issue are similar.

This looks like a promising candidate. If you have the actual test case 
examples (I don't seem to be able to find them) it's surely "just" a matter of 
trying the PoC against this revision and its parent. Or going a bit further, 
using it to bisect between 3.27 and 3.28 (using a git mirror of the source).


robert.

Bug#929529: gufw: Version 17.04.1-1.1 removes characters from interface name rendering rules invalid.fixed in testing

[Richard Kaufhold]

Package: gufw
Version: 17.04.1-1.1
Severity: important

Dear Maintainer,

the current stable version 17.04.1-1.1 removes characters from interface name
(showing enp0s31f instead of enp0s31f6) rendering rules invalid.

Reproduce:
1. Open gufw
2. Go to "Rules" tab.
3. Klick on "+" to add a new rule.
4. Go to "Advanced" tab.
5. Klick on the "All Interfaces" drop down menu. For me this shows enp0s31f but
my interface name is enp0s31f6 (shown in `ls /sys/class/net`).

This renders the stable version of gufw useless for me as the iptables rules
generated won't apply to any packets.

This is fixed in testing version 18.10.0-1.



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

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

Versions of packages gufw depends on:
ii  gir1.2-gtk-3.0  3.22.11-1
ii  gir1.2-webkit2-4.0  2.18.6-1~deb9u1
ii  net-tools   1.60+git20161116.90da8a0-1
ii  policykit-1 0.105-18+deb9u1
ii  python3 3.5.3-1
ii  python3-gi  3.22.0-2
ii  ufw 0.35-4

gufw recommends no packages.

gufw suggests no packages.

-- no debconf information

Bug#929530: libsis-base-java: unaligned access on armhf

[Steve Langasek]

Source: libsis-base-java
Version: 18.09~pre1+git20180827.fe4953e+dfsg-1
Severity: important
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu eoan

Dear maintainers,

In Ubuntu, libsis-base-java fails to build on armhf with an unaligned access
error (SIGBUS):

Running testIntToByteToInt
 Arguments: [0, 0]
 Arguments: [0, 1]
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGBUS (0x7) at pc=0xf6bd95a4, pid=17199, tid=17200
#
# JRE version: OpenJDK Runtime Environment (11.0.3+5) (build 
11.0.3+5-Ubuntu-1ubuntu2)
# Java VM: OpenJDK Server VM (11.0.3+5-Ubuntu-1ubuntu2, mixed mode, g1 gc, 
linux-)
# Problematic frame:
# V  [libjvm.so+0x48c5a4]
#
# Core dump will be written. Default location: Core dumps may be processed with 
"/usr/share/apport/apport %p %s %c %d %P" (or dumping to 
/<>/libsis-base-java-18.09~pre1+git20180827.fe4953e+dfsg/core.17199)
#
# An error report file with more information is saved as:
# 
/<>/libsis-base-java-18.09~pre1+git20180827.fe4953e+dfsg/hs_err_pid17199.log
#
# If you would like to submit a bug report, please visit:
#   https://bugs.launchpad.net/ubuntu/+source/openjdk-lts
#
Aborted (core dumped)
make[1]: *** [debian/rules:47: override_dh_auto_test-arch] Error 134

  
(https://launchpad.net/ubuntu/+source/libsis-base-java/18.09~pre1+git20180827.fe4953e+dfsg-1/+build/15630858)

Further investigation shows that this is a result of libsis-base-java
passing an unaligned pointer as the 'buf' argument to the JNI function
GetIntArrayRegion().

On ARM, unaligned memory access is not guaranteed to succeed; depending on
the CPU and the kernel configuration, it may raise SIGBUS instead.

This problem is reproducible on amdahl, the Debian arm64 porter machine, in
an armhf chroot.  It will also affect some number of users running Debian
armhf on a 64-bit kernel, and will likely become a serious build failure in
Debian in the future when the autobuilders are transitioned to 64-bit CPUs.

I am not sure if it should be considered a bug in libsis-base-java for
passing an unaligned address to GetIntArrayRegion(), or a bug in openjdk for
performing unaligned access when passed an unaligned address.  But I am
inclined to think the bug is in libsis-base-java, because technically the
value it's passing as an int* argument is not valid on this architecture as
a pointer to an int.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#754513: Paper Submission - Thailand IRED International Conference - August 2019

[Stefania Wilson]

Dear Friends,


We would like to invite you to submit research article in the 9th Joint 
International Conference organised by Institute of Research Engineers and 
Doctors at Bangkok, Thailand. The theme for the 2019 Thailand conference is to 
bring together innovative academics and industrial experts to a common forum. 
We would be delighted to have you present at this conference to hear what the 
technology experts and researchers have to share about the technology 
advancements and their impact on our daily lives.


Joint International Conference Consists of following tracks:




Track 1: 9th International Conference on Advances in Computing, Electronics and 
Communication - ACEC


Official Website: www.acec.theired.org




Track 2: 9th International Conference On Advances in Civil, Structural and 
Environmental Engineering - ACSEE


Official Website: www.acsee.theired.org




Track 3: 9th International Conference On Advances in Mechanical and Robotics 
Engineering - AMRE


Official Website: www.amre.theired.org




Track 4: 9th International Conference On Advances in Social Science, Management 
and Human Behaviour - SMHB


Official Website: www.smhb.theired.org


Conference Venue: Hotel Lebua at State Tower, Bangkok, Thailand


Conference Date: 03 - 04 August 2019


Abstract/ Full Paper Submission For Review: 10 June 2019




About Publication:

All the registered papers will proudly be published by IRED-CPS and stored in 
the SEEK digital Library 

(www.seekdl.org). Each Paper will be assigned DOI (Digital Object Identifier) 
from CROSSREF. The Proc. will be submitted to ISI Thomson for Review and 
Indexing. Proc. will also be published in International Journals with ISSN 
Numbers.


Remote Presentation via Skype can also be arranged.


We would also like to share some conference photographs of previous held 
International conference that has been worldwide.


Kindly refer to the below link to access the conference photographs.




https://gallery.theired.org/previous-conferences/



We Request you to forward this email to your colleagues/Researchers/students in 
order to promote the conference.


The aim of the conference is to provide a platform to the researchers and 
practitioners from both academia as well as industry to meet and share 
cutting-edge development in the field.
Please take the time to explore the website for more details, check on 
important dates, and keep yourself up to date on recent changes. 



Registered Papers (IRED Extended paper guidelines applicable) will be published 
in the various issues of International journals.
Prospective authors are invited to submit full (original) research papers; 
which are NOT submitted or published or under consideration anywhere in other 
conferences or journals; in electronic format via email. 




Thanks Much 
Stefania Wilson
NEWS Division 
IRED
 If you no longer wish to receive mail from us, you can 

unsubscribe
IRED H

Bug#929531: grub-pc: grub2 fat_test fails with 4.19.0-5-amd64 kernel if one ensure it does not gets auto-skipped

[Thomas Lamprecht]

Package: grub-pc
Version: 2.02+dfsg1-18
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

while grub2 build fine as common users, i.e., the one created by the
Debian Installer with the addition that it's added to the 'kvm' group,
it does currently not as root depending on the Linux Kernel booted as
with some the fat_test fail.

Reproducer:

* installing Debian from recent weekly testing ISO, boot, install
  build-essentials and devscripts
* # uname -a
  Linux bussard 4.19.0-5-amd64 #1 SMP Debian 4.19.37-3 (2019-05-15)
  x86_64 GNU/Linux
* # apt source grub2
* # apt buil-dep grub2
* # cd grub2-2.02+dfsg1/
* # debuild -b -uc -us
  ...
   mkdir: cannot create directory
   ‘/tmp/tmp.gfJAxp7sgv/vfat12a_rw///0//1/2/3//4/5’: Input/output error

  (full test-suite.log inlined below)

kernel logged:
> May 25 20:27:51 bussard kernel: FAT-fs (loop0): error, corrupted directory 
> (invalid entries)
> May 25 20:27:51 bussard kernel: FAT-fs (loop0): Filesystem has been set 
> read-only
> May 25 20:27:51 bussard kernel: FAT-fs (loop0): error, fat_get_cluster: 
> invalid cluster chain (i_pos 0)

I tried multiple times, most of them with a reboot plus a complete
cleanup and re-download of the source inbetween, but did not always saw
the same error, different directories

As I had build this in the past sucessfully I was a bit thrown-off
first, reverting back to and older Kernel (first one I had lying arround
was linux-image-4.16.0-1-amd64) it worked again, and build successfully.

So, IMHO, there's an issue with either VFAT in the kernel itself, or how
GRUB2 (test) uses VFAT under current Kernels, which just does not shows
up as those FS test get skipped as common, unpriviledged, user, as the
mkfs and loop device handling is normally not allowed for them.

While yes, building as root is far from nice, it's the simplest way to
actually ensure those FS test get run and thus show up an issue.

I tested out some Kernels, most from the Ubuntu Mainline kernel ppa:
https://kernel.ubuntu.com/~kernel-ppa/mainline/

I had varying results, it seems that 4.19.1-041901-generic always
worked, but 4.19.37-041937-generic worked once, then on two different
VMs I got errors too, so a bit strange, a 4.19.28-041928-generic failed
to here, I did not invest more time into bisectin the issue because I
had not much available and was a bit confused by the behaviour..

Below the test-suite log output. I hope I got this to the correct
package people, as may have suited better on the kernel package, but as
I only could trigger this by building grub with the test running I
choose to initially report it here, sorry if it wasn't correct.
 
### BEGIN /root/grub2-2.02+dfsg1/obj/grub-pc/test-suite.log ###
==
   GRUB 2.02+dfsg1-18: ./test-suite.log
   ==

   # TOTAL: 81
   # PASS:  63
   # SKIP:  17
   # XFAIL: 0
   # FAIL:  1
   # XPASS: 0
   # ERROR: 0

   .. contents:: :depth: 2

   SKIP: squashfs_test
   ===

   mksquashfs not installed; cannot test squashfs.

   SKIP: hfsplus_test
   ==

   mkfs.hfsplus not installed; cannot test hfsplus.

   SKIP: ntfs_test
   ===

   mkfs.ntfs not installed; cannot test ntfs.

   SKIP: reiserfs_test
   ===

   mkfs.reiserfs not installed; cannot test reiserfs.

   FAIL: fat_test
   ==

   mkfs.fat 4.1 (2017-01-24)
   Warning: More than 32765 sector need TOS 1.04 or higher.
   Device proc: Filesystem type procfs - Sector size 512B - Total size
   0KiB
   Device loop0: Filesystem type fat - Label `GRUBTEST ;_', UUID
   - - Sector size 512B - Total size 3KiB
   Device host: Filesystem type hostfs - Sector size 512B - Total size
   0KiB

   umount: /tmp/tmp.wcIfohU4Fn/vfat16a_rw: not mounted.
   mkfs.fat 4.1 (2017-01-24)
   Warning: More than 32765 sector need TOS 1.04 or higher.
   Device proc: Filesystem type procfs - Sector size 512B - Total size
   0KiB
   Device loop0: Filesystem type fat - Label `GRUBTEST ;_', UUID
   - - Sector size 512B - Total size 3KiB
   Device host: Filesystem type hostfs - Sector size 512B - Total size
   0KiB

   umount: /tmp/tmp.wcIfohU4Fn/vfat16a_rw: not mounted.
   mkfs.fat 4.1 (2017-01-24)
   Warning: More than 32765 sector need TOS 1.04 or higher.
   Device proc: Filesystem type procfs - Sector size 512B - Total size
   0KiB
   Device loop0: Filesystem type fat - Label `GRUBTEST ;_', UUID
   - - Sector size 512B - Total size 3KiB
   Device host: Filesystem type hostfs - Sector size 512B - Total size
   0KiB

   umount: /tmp/tmp.wcIfohU4Fn/vfat16a_rw: not mounted.
   mkfs.fat 4.1 (2017-01-24)
   Warning: More than 32765 sector need TOS 1.04 or higher.
   Device proc: Filesystem type procfs - Sector size 512B - Total size
   0KiB
   Device loop0: Filesystem type fat - Label `GRUBTEST ;_', UUID
   - - Sector size 512B -

Bug#929532: mtd: spi-nor: Add support for N25Q256A11

[Matt Sickler]

Source: linux-4.9
Severity: wishlist
Tags: patch

Dear Maintainer,

We have a system that uses the n25q256a11 SPI flash device which is not
marked as supported in the 4.9 kernel series.
This is the same problem as I had in deb bug #843650.  In that bug report I
stated that the patch wasn't necessary as it was added upstream in 4.7.
That is incorrect, I'm not sure what I was thinking back then.
It *was* added upstream for 4.12 as seen in commit 835ed7bf12609c [1].
Anyway, we're thinking of using the backported linux-4.9 with Jessie for a
little while, and I'd like to avoid having to keep patching the packages myself.

[1] 
https://github.com/torvalds/linux/commit/835ed7bf12609ce23d42956e74206cc539a0ce5f

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

Kernel: Linux 4.9.0-0.bpo.9-amd64 (SMP w/16 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
Adds support for the SPI Flash chip on the P2K card.
--- a/drivers/mtd/spi-nor/spi-nor.c
+++ b/drivers/mtd/spi-nor/spi-nor.c
@@ -892,6 +892,7 @@ static const struct spi_device_id spi_no
 	{ "n25q128a11",  INFO(0x20bb18, 0, 64 * 1024,  256, SECT_4K | SPI_NOR_QUAD_READ) },
 	{ "n25q128a13",  INFO(0x20ba18, 0, 64 * 1024,  256, SECT_4K | SPI_NOR_QUAD_READ) },
 	{ "n25q256a",INFO(0x20ba19, 0, 64 * 1024,  512, SECT_4K | SPI_NOR_QUAD_READ) },
+	{ "n25q256ax1",  INFO(0x20bb19, 0, 64 * 1024,  512, SECT_4K | SPI_NOR_QUAD_READ) },
 	{ "n25q512a",INFO(0x20bb20, 0, 64 * 1024, 1024, SECT_4K | USE_FSR | SPI_NOR_QUAD_READ) },
 	{ "n25q512ax3",  INFO(0x20ba20, 0, 64 * 1024, 1024, SECT_4K | USE_FSR | SPI_NOR_QUAD_READ) },
 	{ "n25q00",  INFO(0x20ba21, 0, 64 * 1024, 2048, SECT_4K | USE_FSR | SPI_NOR_QUAD_READ) },

Bug#929466: FreeRADIUS opinion of this issue

[Alan DeKok]

  Here's what we sent CVE.  In short, there is no actual "exploit".

---
We disagree with this CVE.  In the GitHub report [1], the RedHat
reporter claims:

> we are aware of a way to exploit this,

No description of this alleged exploit has been shared with us.

Our security contact is "secur...@freeradius.org", which has been
active for almost 20 years.  This address and security instructions
are available on our web site at:

https://freeradius.org/security/

It is not clear why RedHat would refuse to share information about
this issue, as is normal practice.

In the GitHub report, RedHat further claims that exploitation

>  ... requires the attacker to already have "high privileges" (that is, he 
> needs to have access to the radiusd user)

Which demonstrates that this issue is largely nonsense.  A full explanation 
follows.

While the FreeRADIUS server runs as user/group "radiusd/radiusd", that
account has no login shell, no home directory, and no default
password.  The account is used solely to run the FreeRADIUS server,
and to control ownership of configuration files and log files.  These
files are typically administered solely by the "root" user.

As such, the CVE can be better stated as "if the root user
misconfigures FreeRADIUS, then the RADIUS server can later elevate
privileges to root".

We have to ask why the "root" user would need to leverage a
less-privileged account in order to gain "root" permissions.

Further, anyone who can operate as the RADIUS server can perform all
RADIUS authentication and authorization.  i.e. authenticating all
users on the network, including unknown and malicious users.

There is at this time no known exploit which would let malicious users
gain access to the "radiusd" user.  Therefore as discussed here, there
is simply no way for anyone to *gain* privileges through this alleged
issue.

In addition, there also appears to be disagreement within RedHat about
the severity and scope of this issue.  The original reporter [2]
states:

> The su directive to logrotate ensures that log rotation happens under the
> owner of the logs. Otherwise, logrotate runs as root:root, potentially
> enabling privilege escalation if a RCE is discovered against the
> FreeRADIUS daemon.
>
> This attack avenue seems quite unlikely to me.

We agree.  We take great care in securing FreeRADIUS.  We use multiple
source code analyzers and fuzzing tests.

Even the most charitable interpretation of this issue shows that the
vulnerability is theoretical in nature, and is not currently
exploitable.

As such, we disagree with the issuance of this CVE.  We also express
dismay at the process by which this CVE was issued.  We recommend that
security "experts" follow best practices in discussing issues with
authors prior to requesting spurious CVEs.


[1] 
https://github.com/FreeRADIUS/freeradius-server/pull/2666#issuecomment-495511510
[2] https://github.com/FreeRADIUS/freeradius-server/pull/2666#issue-276755666

---


signature.asc
Description: Message signed with OpenPGP

Bug#929511: qtcreator: Segfault on start

[Lisandro Damián Nicanor Pérez Meyer]

tag 929511 unreproducible moreinfo
severity 929511 important
thanks

Hi Martin!

On Sat, 25 May 2019 at 05:06, Martin Haase  wrote:
>
> Package: qtcreator
> Version: 4.8.2-1
> Severity: grave
> Tags: upstream
> Justification: renders package unusable

I can't reproduce the behavior and I have also just installed buster
and unstable system in which to use qtcreator this very same week
without issues (it happens to be one of my principal tools for $job).
In none of those cases I could see a crash, so it's clearly not
happening to everyone and thus I'm lowering the severity.

It is however something we need to triage for buster.

> This is what I get when I try to start qtcreator:
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x7fffe6091e3c in llvm::SmallPtrSetImplBase::Grow(unsigned int) ()
> from /usr/lib/x86_64-linux-gnu/libLLVM-3.7.so.1

OK, so LLVM involved.

> Complete backtrace, as from gdb:
>
> #0  0x7fffe6091e3c in llvm::SmallPtrSetImplBase::Grow(unsigned int) () 
> from /usr/lib/x86_64-linux-gnu/libLLVM-3.7.so.1
> #1  0x7fffe6091ff3 in llvm::SmallPtrSetImplBase::insert_imp(void const*) 
> () from /usr/lib/x86_64-linux-gnu/libLLVM-3.7.so.1
> #2  0x7fffe6060d24 in llvm::cl::OptionCategory::registerCategory() () 
> from /usr/lib/x86_64-linux-gnu/libLLVM-3.7.so.1
> #3  0x7fffd7602082 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-7.so.1
> #4  0x77fe439a in call_init (l=, argc=argc@entry=1, 
> argv=argv@entry=0x7fffe498, env=env@entry=0x7fffe4a8)
> at dl-init.c:72
> #5  0x77fe4496 in call_init (env=0x7fffe4a8, argv=0x7fffe498, 
> argc=1, l=) at dl-init.c:30
> #6  _dl_init (main_map=main_map@entry=0x55909600, argc=1, 
> argv=0x7fffe498, env=0x7fffe4a8) at dl-init.c:119
> #7  0x77fe8303 in dl_open_worker (a=a@entry=0x7fffda10) at 
> dl-open.c:517
> #8  0x76447f8f in __GI__dl_catch_exception (exception= out>, operate=, args= out>) at dl-error-skeleton.c:196
> #9  0x77fe7bea in _dl_open (file=0x55909538 
> "/usr/lib/x86_64-linux-gnu/qtcreator/plugins/libClangTools.so",
> mode=-2147479551, caller_dlopen=0x76ceffac, nsid=, 
> argc=1, argv=0x7fffe498, env=0x7fffe4a8) at dl-open.c:599
> #10 0x7630f256 in dlopen_doit (a=a@entry=0x7fffdc30) at 
> dlopen.c:66
> #11 0x76447f8f in __GI__dl_catch_exception 
> (exception=exception@entry=0x7fffdbd0, operate=,
> args=)
> at dl-error-skeleton.c:196
> #12 0x7644801f in __GI__dl_catch_error (objname=0x5558cd00, 
> errstring=0x5558cd08, mallocedp=0x5558ccf8,
> operate=, args=) at
> dl-error-skeleton.c:215
> #13 0x7630f975 in _dlerror_run (operate=operate@entry=0x7630f200 
> ,
> args=args@entry=0x7fffdc30) at dlerror.c:163
> #14 0x7630f2e6 in __dlopen (file=, mode= out>) at dlopen.c:87
> #15 0x76ceffac in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
> #16 0x76ce9c25 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
> #17 0x76cea1d3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
> #18 0x77fad5dc in 
> ExtensionSystem::Internal::PluginSpecPrivate::loadLibrary() ()
> from /usr/bin/../lib/x86_64-linux-gnu/qtcreator/libExtensionSystem.so.4
> #19 0x77fa54cd in 
> ExtensionSystem::Internal::PluginManagerPrivate::loadPlugin(ExtensionSystem::PluginSpec*,
> ExtensionSystem::PluginSpec::State) () from 
> /usr/bin/../lib/x86_64-linux-gnu/qtcreator/libExtensionSystem.so.4
> #20 0x77fa6650 in 
> ExtensionSystem::Internal::PluginManagerPrivate::loadPlugins() ()
> from /usr/bin/../lib/x86_64-linux-gnu/qtcreator/libExtensionSystem.so.4
> #21 0xeeb6 in ?? ()
> #22 0x7633709b in __libc_start_main (main=0xca40, argc=1, 
> argv=0x7fffe498, init=, fini=,
> rtld_fini=, stack_end=0x7fffe488) at 
> ../csu/libc-start.c:308
> #23 0xf50a in ?? ()
>
> I tried the crude hack renaming the lib and symlinking to a newer
> version, but that made things even worse. Besides, other programs
> will be affected, too.

I would expect that, yes.

I need some extra info:

- Which video card are you using?
- Please create a new user and try starting qtcreator there. Moving
out Qt creator's config is also possible, but more involved: you need
to move ~/.config/QtCreatorrc *and* ~/.config/QtProject/qtcreator/
*and* ~/.config/QtProject/QtCreator* (without qtcreator running) and
then start it.
- Have you installed any third party plugin? The crash seems to come
from loading a plugin.

Thanks for your report and your help, Lisandro.


-- 
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/

Bug#929532: mtd: spi-nor: Add support for N25Q256A11

[Matt Sickler]

Hello Debian Kernel Team,

I just submitted this bug to Debian via reportbug.  It looks like the linux-4.9 
package doesn't have a maintainer, so I'm forwarding the bug in the hope that 
someone will see it.

Regards,
Matt

On Sat, 25 May 2019 14:58:33 -0500 Matt Sickler  
wrote: 
> Source: linux-4.9 
> Severity: wishlist 
> Tags: patch 
> 
> Dear Maintainer, 
> 
> We have a system that uses the n25q256a11 SPI flash device which is not 
> marked as supported in the 4.9 kernel series. 
> This is the same problem as I had in deb bug #843650.  In that bug report I 
> stated that the patch wasn't necessary as it was added upstream in 4.7. 
> That is incorrect, I'm not sure what I was thinking back then. 
> It *was* added upstream for 4.12 as seen in commit 835ed7bf12609c [1]. 
> Anyway, we're thinking of using the backported linux-4.9 with Jessie for a 
> little while, and I'd like to avoid having to keep patching the packages 
> myself. 
> 
> [1] 
> https://github.com/torvalds/linux/commit/835ed7bf12609ce23d42956e74206cc539a0ce5f
>  
> 
> -- System Information: 
> Debian Release: 8.11 
>   APT prefers oldstable 
>   APT policy: (500, 'oldstable') 
> Architecture: amd64 (x86_64) 
> 
> Kernel: Linux 4.9.0-0.bpo.9-amd64 (SMP w/16 CPU cores) 
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) 
> Shell: /bin/sh linked to /bin/bash 
> Init: systemd (via /run/systemd/system) 

Bug#929433: lintian: warn on suspicious usage of dpkg-architecture variables

[Helmut Grohne]

Hi Graham,

On Sat, May 25, 2019 at 06:06:08PM +0200, Graham Inggs wrote:
> But if a maintainer were about to upload a new package, or introduced
> changes to an existing package, that used DEB_BUILD* or DEB_TARGET* instead
> of DEB_HOST_MULTIARCH, I suspect the usage is most likely incorrect.

Your suspicion may mislead you. A number of packages disable tests on
mips and mipsel, because its address space is so limited. This would be
a case where you would use DEB_BUILD_* as it is the address space of the
machine you are building on that is relevant here. For this reason
alone, I think "most likely incorrect" is incorrect.

> Here are a couple I was able to find quickly:
> 
> https://salsa.debian.org/debichem-team/nwchem/commit/96a2bd29073d5f25c97fdf9ce0493857b31fcae0
> https://salsa.debian.org/r-pkg-team/r-bioc-rhdf5lib/commit/00bd8caa6689bf048d4f0f654993b0402a74cedb

Beyond confusing build and host, these confuse *_GNU_TYPE and
*_MULTIARCH. This used to be a relevant pattern indeed. We can turn it
into a codesearch query:

https://codesearch.debian.net/search?q=lib%2F%5C%24%5B%7B%28%5DDEB_%28BUILD%7CHOST%29_GNU_TYPE

The corresponding apt-file query does not yield any results however,
which suggests that we've fixed all of them.

apt-file search -x lib/i686-linux-gnu

I'm not sure what glibc and perl-cross-debian do in the codesearch
result, but the other occurrences look like they're either old changelog
entries or should use *_MULTIARCH. So using DEB_*_GNU_TYPE in a path
directly below lib is something that could reasonably be flagged with
few false positives. And it's also a mistake that can go unnoticed for a
while, because it only matters on i386.

And again the fingers of two hands almost suffice to enumerate all
packages matching this pattern. Again I question whether the effort of
turning this into a lintian check is well spent.

Graham, can I ask you to actually send those patches before continuing
this lintian discussion? I don't think this is moving us forward. Let it
rest a few days and gain more experience with the matter please.

Helmut

Bug#929512: calibre: Kobo database version 152 not supported

[Norbert Preining]

Version: 3.42.0+dfsg-1

> calibre, version 3.39.1
> WARNING: Failed: Kobo database version unsupported - See details

Yes, support out of the box was added later in Calibre.
But since we are in freeze, we cannot update to a later version of
Calibre.

You can do ...

> defaults, you can override this check by right clicking the device icon
> in calibre and selecting "Configure this device" and then the  "Attempt
> to support newer firmware" option. Doing so may require you to perform a

though.

Closing this bug since it is already fixed in the most recent version in
experimental.

Best

Norbert

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

Bug#927970: lintian: false positives for missing-systemd-timer-for-cron-script?

[Francesco Poli]

Control: found -1 lintian/2.14.0


On Thu, 25 Apr 2019 22:29:28 +0200 Francesco Poli wrote:

> On Thu, 25 Apr 2019 13:43:23 -0400 Chris Lamb wrote:
> 
> [...]
> > You are, of course, entirely right. Fixed in Git, now pending upload
> 
> I am glad to help!   :-)
> 
> Thanks for your prompt reaction.
> Bye.

Hello again,
I still get the false positive...
I am therefore reopening the bug report.


I have a doubt: should the following line

  if any { m,^/lib/systemd/system/[^\/]+\.timer$, } $info->sorted_index;

drop the "/" at the beginning?

Or are the false positives caused by something else?

Please clarify.
Thanks for your time again!


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


pgpZcz4TEOJ53.pgp
Description: PGP signature

Bug#926130: e2fsck returns 1 which makes e2scrub fails

[Theodore Ts'o]

On Tue, May 14, 2019 at 09:42:58AM +0200, Laurent Bigonville wrote:
> 
> I've attached the requested logs. I don't see anything weird here.

Yeah, I'm not seeing anything in the logs either.  :-(

Would you be willing to send me a compressed e2image file?  The
commands to generate are:

e2image -Q /dev/fornost/docker docker.qcow2
xz docker.qcow2

.. and then send me the docker.qcow2.xz file.  It will include only
the metadata blocks of the file system.  See the e2image man page for
more details.  This *will* include filenames in the directory blocks,
so if that makes you uncomfortable, you can use the -S option --- but
if it's all the same to you, it would be more convenient if you could
send it to me w/o using -S option.  The file will hopefully be small
enough that you can just e-mail it to me, or put it someplace where I
can download it (perhaps encrypted using GPG).

Thanks!!

- Ted

Bug#619757: Bug #619757 breaks DVD reading by default now

[David Given]

I've just run into this myself with a Bluray drive:

$ uname -a
Linux hilfy 4.19.0-5-amd64 #1 SMP Debian 4.19.37-3 (2019-05-15) x86_64
GNU/Linux

$ smartctl -i /dev/cdrom
smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.19.0-5-amd64] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:   HL-DT-ST
Product:  BD-RE  BH16NS55
Revision: 1.02
User Capacity:24,220,008,448 bytes [24.2 GB]
Logical block size:   2048 bytes
Device type:  CD/DVD

The workflow with me was:

- install brand new drive
- burn an image to the drive
- attempt to verify the image
- drive only returns the first 1073741312 bytes of data, causing the
verification to fail

This then resulted in me panicing that my brand new drive was faulty!

Is this an important enough bug to warrant having the packet driver stuff
disabled by default? I never heard of anyone who uses it, and I've tried
and failed myself; and the failure mode is pretty severe (non-CD writable
optical media simply fails to work).

-- 
┌─── http://www.cowlark.com ───
│ "I have always wished for my computer to be as easy to use as my
│ telephone; my wish has come true because I can no longer figure out
│ how to use my telephone." --- Bjarne Stroustrup

Bug#929533: package 0.7.0 rc for Debian experimental

[W. Martin Borgert]

Package: qelectrotech
Version: 1:0.6.1-1
Severity: wishlist

Having 0.7.0 release candidate in experimental would be nice and useful.

Bug#929366: linux-image-4.19.0-5-octeon: usercopy: Kernel memory overwrite attempt detected (in systemd-timedated)

[Paul Burton]

Hi YunQiang,

Could you try the following kernel patch & let me know if it works for
you?

My theory is that this is fallout from commit 517e1fbeb65f
("mm/usercopy: Drop extra is_vmalloc_or_module() check") which went into
Linux v4.12. I guess this shows our test systems don't have hardened
usercopy enabled - I'll go change that!

Thanks,
Paul

---
diff --git a/arch/mips/mm/mmap.c b/arch/mips/mm/mmap.c
index 2f616ebeb7e0..01b2eadd28bd 100644
--- a/arch/mips/mm/mmap.c
+++ b/arch/mips/mm/mmap.c
@@ -203,6 +203,11 @@ unsigned long arch_randomize_brk(struct mm_struct *mm)
 
 int __virt_addr_valid(const volatile void *kaddr)
 {
+   unsigned long vaddr = (unsigned long)vaddr;
+
+   if ((vaddr < PAGE_OFFSET) || (vaddr >= MAP_BASE))
+   return false;
+
return pfn_valid(PFN_DOWN(virt_to_phys(kaddr)));
 }
 EXPORT_SYMBOL_GPL(__virt_addr_valid);

Bug#929538: O: jpegpixi -- suppression de taches lumineuses d’images JPEG avec une perte minimale de qualité

[Pierre-Elliott Bécue]

Package: wnpp

The current maintainer of jpegpixi, Kevin Coyner ,
is apparently not active anymore.  Therefore, I orphan this package now.

Maintaining a package requires time and skills. Please only adopt this
package if you will have enough time and attention to work on it.

If you want to be the new maintainer, please see
https://www.debian.org/devel/wnpp/#howto-o for detailed
instructions how to adopt a package properly.

Some information about this package:

Package: jpegpixi
Binary: jpegpixi
Version: 1.1.1-4.1
Maintainer: Kevin Coyner 
Build-Depends: cdbs, debhelper (>= 5), libjpeg-dev
Architecture: any
Standards-Version: 3.7.3
Format: 1.0
Files:
 ffc47a1ea1f60be67fd84af6384dfeb8 1719 jpegpixi_1.1.1-4.1.dsc
 c888abdb58ff63d634215d4d5b160d5d 155045 jpegpixi_1.1.1.orig.tar.gz
 f5f21eb467b8abe29166b66001608ec9 3497 jpegpixi_1.1.1-4.1.diff.gz
Checksums-Sha256:
 de11d02cdc8c3179ef428e828c723e2a8819e60360dd0a4f2a30a6d609449dea 1719 
jpegpixi_1.1.1-4.1.dsc
 e8507e07383d7b30b8ea9a7958f307b7a4ef38c80e6e2615460b07afd3407bed 155045 
jpegpixi_1.1.1.orig.tar.gz
 7975592014d9c4bcb2a98ffd5f52ee3cbdf037d3b7ef0f16122043afada3d85a 3497 
jpegpixi_1.1.1-4.1.diff.gz
Homepage: http://www.zero-based.org/software/jpegpixi/
Package-List: 
 jpegpixi deb graphics optional
Directory: pool/main/j/jpegpixi
Priority: source
Section: graphics

Package: jpegpixi
Source: jpegpixi (1.1.1-4.1)
Version: 1.1.1-4.1+b3
Installed-Size: 153
Maintainer: Kevin Coyner 
Architecture: amd64
Depends: libc6 (>= 2.14), libjpeg62-turbo (>= 1.3.1)
Description-fr: suppression de taches lumineuses d’images JPEG avec une perte 
minimale de qualité
 Jpegpixi est un raccourci pour « JPEG pixel interpolator » (interpolateur
 de pixels JPEG). C’est un utilitaire en ligne de commande interpolant les
 pixels dans des images JFIF (communément appelées des « images JPEG »). Il
 est utile pour corriger des images d’un appareil photographique avec des
 imperfections de capteur (CCD).
 .
 Jpegpixi essaie autant que possible de conserver la qualité de l’image
 JFIF. La plupart des programmes graphiques décodent les images JFIF lors
 de leur chargement et les réencodent lors de leur enregistrement, ce qui
 conduit à une perte globale de qualité. Jpegpixi, à l’opposé, ne décode ni
 ne réencode l’image, mais manipule les données encodées de l’image. En
 faisant cela, il préserve les métadonnées EXIF.
Description-md5: 87496cf9310f616d2ff56ef6548573ec
Homepage: http://www.zero-based.org/software/jpegpixi/
Tag: field::astronomy, implemented-in::c, interface::commandline,
 role::program, scope::utility, works-with-format::jpg,
 works-with::image, works-with::image:raster
Section: graphics
Priority: optional
Filename: pool/main/j/jpegpixi/jpegpixi_1.1.1-4.1+b3_amd64.deb
Size: 64446
MD5sum: 74ac55abd96712c0d6ac46533c5427ae
SHA256: 31a2312743c5a658ef332c99b9992687df8e13e62d786095344e8b724f5964b9


-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature

Bug#929539: O: mailcheck -- recherche de courriels dans plusieurs boîtes aux lettres ou répertoires

[Pierre-Elliott Bécue]

Package: wnpp

The current maintainer of mailcheck, Kevin Coyner ,
is apparently not active anymore.  Therefore, I orphan this package now.

Maintaining a package requires time and skills. Please only adopt this
package if you will have enough time and attention to work on it.

If you want to be the new maintainer, please see
https://www.debian.org/devel/wnpp/#howto-o for detailed
instructions how to adopt a package properly.

Some information about this package:

Package: mailcheck
Binary: mailcheck
Version: 1.91.2-2
Maintainer: Kevin Coyner 
Build-Depends: debhelper (>= 5.0), dpatch
Architecture: any
Standards-Version: 3.7.2
Format: 1.0
Files:
 3751d7628e505ad64fcb871e9ddf3180 578 mailcheck_1.91.2-2.dsc
 d2a3a22a65b1006d213d8cb3f4738070 15885 mailcheck_1.91.2.orig.tar.gz
 1fef8cb8ec2468845f355565f589905f 11163 mailcheck_1.91.2-2.diff.gz
Checksums-Sha256:
 335208cfa50599ca7b4085244b3dfc640e162cb043faabf4eda75a526d1d651c 578 
mailcheck_1.91.2-2.dsc
 30c8db7249e5780dc4d500a4dcb2da1f67139bb66585971f6448ac090b2dded0 11163 
mailcheck_1.91.2-2.diff.gz
 6ca6da5c9f8cc2361d4b64226c7d9486ff0962602c321fc85b724babbbfa0a5c 15885 
mailcheck_1.91.2.orig.tar.gz
Directory: pool/main/m/mailcheck
Priority: source
Section: mail

Package: mailcheck
Source: mailcheck (1.91.2-2)
Version: 1.91.2-2+b2
Installed-Size: 47
Maintainer: Kevin Coyner 
Architecture: amd64
Depends: libc6 (>= 2.14)
Description-fr: recherche de courriels dans plusieurs boîtes aux lettres ou 
répertoires
 Mailcheck est un outil simple et configurable qui permet de rechercher
 parmi de nombreuses boîtes aux lettres l’existence de nouveaux courriels.
 Il gère les boîtes aux lettres de style mbox et maildir pour la
 compatibilité avec la plupart des agents de transport de courriels. Il
 prend en charge aussi les boîtes aux lettres POP3 et IMAP distantes.
 .
 Page d’accueil : http://mailcheck.sourceforge.net/
Description-md5: 1686a353979e58dc7700d4ecd6a5ed19
Tag: implemented-in::c, interface::commandline, mail::notification,
 mail::pop, protocol::imap, protocol::pop3, role::program,
 scope::utility, works-with::mail
Section: mail
Priority: optional
Filename: pool/main/m/mailcheck/mailcheck_1.91.2-2+b2_amd64.deb
Size: 14082
MD5sum: 0caf18ff88ce5ed728dd46db6d935807
SHA256: 73e6da478072df1218c3c5fc771d28ba6f040b29a0511013792d1e8da8ec5600


-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature

Bug#929542: O: photon -- générateur de galeries HTML statiques

[Pierre-Elliott Bécue]

Package: wnpp

The current maintainer of photon, Kevin Coyner ,
is apparently not active anymore.  Therefore, I orphan this package now.

Maintaining a package requires time and skills. Please only adopt this
package if you will have enough time and attention to work on it.

If you want to be the new maintainer, please see
https://www.debian.org/devel/wnpp/#howto-o for detailed
instructions how to adopt a package properly.

Some information about this package:

Package: photon
Binary: photon
Version: 0.4.6-3.1
Maintainer: Kevin Coyner 
Build-Depends: debhelper (>= 8), python-all (>= 2.6.6-3~), quilt (>= 0.48)
Architecture: all
Standards-Version: 3.9.1
Format: 3.0 (quilt)
Files:
 0e0226916165a5e4ce852983f34ff8c6 1756 photon_0.4.6-3.1.dsc
 d7836593c4ffb8fb5bba8ecb8b670d12 62754 photon_0.4.6.orig.tar.gz
 bdb2bbb6767591f4c18cd7a4f8af09a0 8650 photon_0.4.6-3.1.debian.tar.gz
Checksums-Sha256:
 adbf5e0f0b16398d78a02f7af516d00fa97655f1b4d85b14373bfcdff06b734a 1756 
photon_0.4.6-3.1.dsc
 f309a97541137cb8d25764ff951e59100d108897149d62f77ebce5f6d481728b 62754 
photon_0.4.6.orig.tar.gz
 1ef0085beede835d6c4d2541822e98262bc2f02af672b625e6dbfcd4b4e9af91 8650 
photon_0.4.6-3.1.debian.tar.gz
Homepage: http://www.saillard.org/programs_and_patches/photon/
Package-List: 
 photon deb graphics optional
Directory: pool/main/p/photon
Priority: source
Section: graphics

Package: photon
Version: 0.4.6-3.1
Installed-Size: 286
Maintainer: Kevin Coyner 
Architecture: all
Depends: python (>= 2.7), python (<< 2.8), python-imaging
Recommends: gimp, dcraw
Description-fr: générateur de galeries HTML statiques
 Il s’agit d’un générateur d'album de photos en Python de conception claire,
 exécuté à partir de la ligne de commande. La sortie HTML peut être
 configurée grâce à des modèles.
 .
 Fonctionnalités :
  – création de pages HTML statiques ;
  – présentation (utilisation de javascript optionnelle) ;
  – utilisation possible de Gimp pour redimensionner les images ;
  – navigation au clavier entre les images ;
  – fonctionnement dans n'importe quel navigateur (Mozilla, Netscape
Navigator 4.x, Konqueror, Opera) ;
  – commentaire possible pour chaque image (avec des balises HTML) ;
  – affichage possible d’informations sur l'image (si prise avec un appareil
photo numérique) ;
  – choix de la taille des vignettes par l'utilisateur ;
  – images produites pouvant être rapetissées ;
  – contrôle du nombre de vignettes par page.
Description-md5: 903f98430cd6523f520d1bb499a6ef3e
Homepage: http://www.saillard.org/programs_and_patches/photon/
Tag: implemented-in::python, interface::commandline, role::program,
 scope::utility
Section: graphics
Priority: optional
Filename: pool/main/p/photon/photon_0.4.6-3.1_all.deb
Size: 65160
MD5sum: 3e564d16eea2ef1185a8e14aa85453ee
SHA256: 1f15accce745485c48cf14bfcb9467990e746cacd868c9a816ffc8b2ee054ba5


-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature

Bug#929537: O: htmlgen -- Python library for the generation of HTML

[Pierre-Elliott Bécue]

Package: wnpp

The current maintainer of htmlgen, Kevin Coyner ,
is apparently not active anymore.  Therefore, I orphan this package now.

Maintaining a package requires time and skills. Please only adopt this
package if you will have enough time and attention to work on it.

If you want to be the new maintainer, please see
https://www.debian.org/devel/wnpp/#howto-o for detailed
instructions how to adopt a package properly.

Some information about this package:

Package: htmlgen
Binary: python-htmlgen
Version: 2.2.2-12.3
Maintainer: Kevin Coyner 
Build-Depends: debhelper (>= 5.0.37.2)
Build-Depends-Indep: dh-python, python-all-dev (>= 2.3.5-11), quilt
Architecture: all
Standards-Version: 3.7.2
Format: 1.0
Files:
 ed11f2620d977f54c3ff8134c58d851b 1735 htmlgen_2.2.2-12.3.dsc
 613306fb2533ffee114f247c7bca4dc9 316483 htmlgen_2.2.2.orig.tar.gz
 0bb1a6ae0713a2cf36e657923e139fc4 7964 htmlgen_2.2.2-12.3.diff.gz
Checksums-Sha256:
 9f270ad71e97b0f0f96908aa40e44595f81e07085c13ce19161d9411ce2f1a50 1735 
htmlgen_2.2.2-12.3.dsc
 8b9b4e92a68f31f22c95649e52eb1d7433c726897f6b1fc623e81b4c0659d3a0 316483 
htmlgen_2.2.2.orig.tar.gz
 f5008e0bec5620a326407cef769c18a5012a2266f41cb5112289e2a9276f54c0 7964 
htmlgen_2.2.2-12.3.diff.gz
Package-List: 
 python-htmlgen deb python optional arch=all
Python-Version: all
Directory: pool/main/h/htmlgen
Priority: source
Section: python

Package: python-htmlgen
Source: htmlgen
Version: 2.2.2-12.3
Installed-Size: 1326
Maintainer: Kevin Coyner 
Architecture: all
Replaces: htmlgen (<< 2.2.2-8.2), python2.3-htmlgen (<< 2.2.2-11), 
python2.4-htmlgen (<< 2.2.2-11)
Provides: python2.7-htmlgen
Depends: python:any (<< 2.8), python:any (>= 2.7.5-5~)
Recommends: python-imaging
Conflicts: htmlgen (<< 2.2.2-8.2), python2.3-htmlgen (<< 2.2.2-11), 
python2.4-htmlgen (<< 2.2.2-11)
Description-en: Python library for the generation of HTML
 HTMLgen is a class library for the generation of HTML documents with
 Python scripts. It's used when you want to create HTML pages
 containing information which changes from time to time. For example
 you might want to have a page which provides an overall system summary
 of data collected nightly. Or maybe you have a catalog of data and
 images that you would like formed into a spiffy set of web pages for
 the world to browse. Python is a great scripting language for these
 tasks and with HTMLgen it's very straightforward to construct objects
 which are rendered into consistently structured web pages. Of course,
 CGI scripts written in Python can take advantage of these classes as
 well.
Description-md5: 4a8ee938aba79cbd46c738877f614c96
Tag: devel::lang:python, devel::library, implemented-in::python,
 interface::commandline, role::devel-lib, role::program, scope::utility,
 works-with-format::html, works-with::text
Section: python
Priority: optional
Filename: pool/main/h/htmlgen/python-htmlgen_2.2.2-12.3_all.deb
Size: 252088
MD5sum: 2fe4b273f5c43128bcd483778d4f6370
SHA256: 8f0692fb0a92d03a3de3a2e054b3fd62e53a621c606381edd362d7adf9202a2a


-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature

Bug#929535: O: bbrun -- outil pour exécuter des commandes avec Blackbox/Fluxbox

[Pierre-Elliott Bécue]

Package: wnpp

The current maintainer of bbrun, Kevin Coyner ,
is apparently not active anymore.  Therefore, I orphan this package now.

Maintaining a package requires time and skills. Please only adopt this
package if you will have enough time and attention to work on it.

If you want to be the new maintainer, please see
https://www.debian.org/devel/wnpp/#howto-o for detailed
instructions how to adopt a package properly.

Some information about this package:

Package: bbrun
Binary: bbrun
Version: 1.6-6.1
Maintainer: Kevin Coyner 
Build-Depends: debhelper (>= 8), libxpm-dev, libgtk2.0-dev, dpatch
Architecture: any
Standards-Version: 3.9.1
Format: 1.0
Files:
 55dd4f17ed32740e8d291f78f2cdec17 1789 bbrun_1.6-6.1.dsc
 820960e3d52ddf2d5cf7e4ba51821bfd 21132 bbrun_1.6.orig.tar.gz
 e0b7fc39f8e9f6cd2c90e7e90152ca11 5564 bbrun_1.6-6.1.diff.gz
Checksums-Sha256:
 40f4ee84006c5413574ecb9cd6bc1752600b9f187a7136d7ea94414875eff385 1789 
bbrun_1.6-6.1.dsc
 d0af57276ec9191a94f8d20a2da69dc1818f410f23478f041334aef2d707559a 21132 
bbrun_1.6.orig.tar.gz
 165bd23e89902b15844dcace8f9d28c9104bd1bbd21ff33f9f5eb7a72820c04b 5564 
bbrun_1.6-6.1.diff.gz
Homepage: http://www.darkops.net/bbrun/
Package-List: 
 bbrun deb x11 optional arch=any
Directory: pool/main/b/bbrun
Priority: source
Section: x11

Package: bbrun
Source: bbrun (1.6-6.1)
Version: 1.6-6.1+b1
Installed-Size: 59
Maintainer: Kevin Coyner 
Architecture: amd64
Depends: libatk1.0-0 (>= 1.12.4), libc6 (>= 2.7), libcairo2 (>= 1.2.4), 
libfontconfig1 (>= 2.11), libfreetype6 (>= 2.2.1), libgdk-pixbuf2.0-0 (>= 
2.22.0), libglib2.0-0 (>= 2.16.0), libgtk2.0-0 (>= 2.8.0), libpango-1.0-0 (>= 
1.14.0), libpangocairo-1.0-0 (>= 1.14.0), libpangoft2-1.0-0 (>= 1.14.0), 
libx11-6, libxext6, libxpm4
Suggests: blackbox (>= 0.60.1) | fluxbox
Description-fr: outil pour exécuter des commandes avec Blackbox/Fluxbox
 L'application bbrun est un outil petit mais très pratique. Il permet
 d'exécuter une commande rapidement dans un gestionnaire de fenêtres comme
 Blackbox. bbrun est très proche de la boîte de dialogue d'exécution de
 commande de KDE obtenue avec Alt+F2. Une fois lancé, il ne prend que très
 peu d'espace sur le bureau et s'accroche tout seul sur la partie droite de
 l'écran. Le dialogue pour exécuter une commande s'ouvre en cliquant sur la
 petite icône bbrun.
 .
 Il n'est pas indispensable d'avoir Blackbox pour faire fonctionner ce
 programme. Il sera semblable dans fluxbox mais aura un aspect différent
 dans les autres gestionnaires de fenêtres.
Description-md5: 15dd702ba73ba6d85ee2830acbdd54f5
Homepage: http://www.darkops.net/bbrun/
Tag: implemented-in::c, interface::graphical, interface::x11, role::program,
 scope::utility, uitoolkit::gtk, works-with::software:running,
 x11::applet
Section: x11
Priority: optional
Filename: pool/main/b/bbrun/bbrun_1.6-6.1+b1_amd64.deb
Size: 17722
MD5sum: ed94bc4bd3652fd42a3170c619600902
SHA256: 9ae5077e86054e823f12d052b2ca0e8d3220f5229c9c1a04ac27c3a072ab0f6d


-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature

Bug#929543: O: pyexcelerator -- module for reading/writing Excel spreadsheet files

[Pierre-Elliott Bécue]

Package: wnpp

The current maintainer of pyexcelerator, Kevin Coyner ,
is apparently not active anymore.  Therefore, I orphan this package now.

Maintaining a package requires time and skills. Please only adopt this
package if you will have enough time and attention to work on it.

If you want to be the new maintainer, please see
https://www.debian.org/devel/wnpp/#howto-o for detailed
instructions how to adopt a package properly.

Some information about this package:

Package: pyexcelerator
Binary: python-excelerator
Version: 0.6.4.1-3
Maintainer: Kevin Coyner 
Uploaders: Debian Python Modules Team 

Build-Depends: debhelper (>= 10), dh-exec, dh-python, python-all
Architecture: all
Standards-Version: 3.9.8
Format: 3.0 (quilt)
Files:
 bc91f48c4ba50026c0d5cce988c71974 2074 pyexcelerator_0.6.4.1-3.dsc
 c4a7fd6c110113df24d04f6b2e7d752e 135431 pyexcelerator_0.6.4.1.orig.tar.gz
 e7069322094b363ee22eaecb7a789a15 5392 pyexcelerator_0.6.4.1-3.debian.tar.xz
Vcs-Browser: 
https://anonscm.debian.org/cgit/python-modules/packages/pyexcelerator.git
Vcs-Git: 
https://anonscm.debian.org/git/python-modules/packages/pyexcelerator.git
Checksums-Sha256:
 4f9977d9b7ba02bdb3a51143fcbbf55b5c118dc5d86b38a7e270872bc0f88bc6 2074 
pyexcelerator_0.6.4.1-3.dsc
 13f5239746a7727d1b19512f558aff06b0659e004b34358ec0a08f32a14a5a39 135431 
pyexcelerator_0.6.4.1.orig.tar.gz
 774cb34a088d5defe1625cf96c9774fa3ddd539a172b9abad486cf15baea8a7a 5392 
pyexcelerator_0.6.4.1-3.debian.tar.xz
Homepage: http://sourceforge.net/projects/pyexcelerator
Package-List: 
 python-excelerator deb python optional arch=all
Directory: pool/main/p/pyexcelerator
Priority: source
Section: python

Package: python-excelerator
Source: pyexcelerator
Version: 0.6.4.1-3
Installed-Size: 520
Maintainer: Kevin Coyner 
Architecture: all
Depends: python:any (<< 2.8), python:any (>= 2.7.5-5~), python-antlr
Description-en: module for reading/writing Excel spreadsheet files
 pyExcelerator is a Python module that can generate Excel 97/2000/XP/2003
 spreadsheet files. It can also extract data from these files.  It supports
 Unicode in Excel files, and can use a variety of formatting features and
 printing options. It can dump Excel and OLE2 compound files.  Included are
 simple conversion tools py_xls2html, py_xls2csv and py_xls2txt.
Description-md5: 464f07ec307932753b64d97f0d26119f
Homepage: http://sourceforge.net/projects/pyexcelerator
Tag: devel::lang:python, devel::library, implemented-in::python,
 interface::commandline, role::devel-lib, role::program,
 role::shared-lib, scope::utility, works-with-format::html,
 works-with-format::plaintext, works-with::spreadsheet, works-with::text
Section: python
Priority: optional
Filename: pool/main/p/pyexcelerator/python-excelerator_0.6.4.1-3_all.deb
Size: 97432
MD5sum: b5a201c017e9af8269791484dd34f978
SHA256: 2e647a3c245326f696031a3d997bc40bb3b80ebdde2dd8d392cd068b31df281d


-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature

Bug#929534: O: bbpager -- Pageur pour les gestionnaires de fenêtres blackbox et fluxbox

[Pierre-Elliott Bécue]

Package: wnpp

The current maintainer of bbpager, Kevin Coyner ,
is apparently not active anymore.  Therefore, I orphan this package now.

Maintaining a package requires time and skills. Please only adopt this
package if you will have enough time and attention to work on it.

If you want to be the new maintainer, please see
https://www.debian.org/devel/wnpp/#howto-o for detailed
instructions how to adopt a package properly.

Some information about this package:

Package: bbpager
Binary: bbpager
Version: 0.4.7-5
Maintainer: Kevin Coyner 
Build-Depends: debhelper (>= 9), libsm-dev, libx11-dev, libice-dev, libxt-dev, 
libbt-dev, libxext-dev, autotools-dev, quilt (>= 0.63)
Architecture: any
Standards-Version: 3.9.8
Format: 3.0 (quilt)
Files:
 0be8a52ca4b1b3325f63d14c00509f27 1416 bbpager_0.4.7-5.dsc
 4eaa91a4d66130af2f7a09c25f917386 170575 bbpager_0.4.7.orig.tar.gz
 92555971340c81bc1d78113a36a33bb1 5940 bbpager_0.4.7-5.debian.tar.xz
Checksums-Sha256:
 fb8328664d59ab943cac04c450b5eef756b83208eb1a4e40098cdc29c161df63 1416 
bbpager_0.4.7-5.dsc
 e7063a8d65c25663f44e2769132053bd3f1b90f0d4b19a8d8aa2e5f028f0679d 170575 
bbpager_0.4.7.orig.tar.gz
 e446bba99feb2b6113284838a1e1f032c8c0ee68f9fe0da9f748eeedbe358878 5940 
bbpager_0.4.7-5.debian.tar.xz
Homepage: http://bbtools.sourceforge.net
Package-List: 
 bbpager deb x11 optional arch=any
Directory: pool/main/b/bbpager
Priority: source
Section: x11

Package: bbpager
Source: bbpager (0.4.7-5)
Version: 0.4.7-5+b1
Installed-Size: 118
Maintainer: Kevin Coyner 
Architecture: amd64
Depends: libbt0 (>= 0.70.1), libc6 (>= 2.14), libgcc1 (>= 1:3.0), libice6 (>= 
1:1.0.0), libsm6, libstdc++6 (>= 5.2), libx11-6, libxext6
Suggests: blackbox (>= 0.70) | openbox | fluxbox
Description-fr: Pageur pour les gestionnaires de fenêtres blackbox et fluxbox
 Pageur pour le gestionnaire de fenêtres Blackbox ou un de ses dérivés. Il
 supporte les styles habituels de Blackbox, déplace les fenêtres entre les
 bureaux et le placement optionnel dans la glissière Blackbox. Il est
 également possible de définir comment les bureaux sont affichés en
 définissant le nombre de lignes ou colonnes à utiliser.
Description-md5: bb8c06a4199066f36632b681cb5026f7
Homepage: http://bbtools.sourceforge.net
Tag: implemented-in::c++, interface::graphical, interface::x11,
 role::program, scope::utility, uitoolkit::xlib,
 works-with::software:running, x11::applet, x11::application
Section: x11
Priority: optional
Filename: pool/main/b/bbpager/bbpager_0.4.7-5+b1_amd64.deb
Size: 38768
MD5sum: ee0bdbf6c28204cf8295bbf9320e4224
SHA256: de2752552f56d4516dc96e41c73e63e0b65b9fc31a3c885da9e05c5bd73f534d


-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature

Bug#929541: O: nmzmail -- indexation et recherche dans des courriels dans des dossiers « maildir »

[Pierre-Elliott Bécue]

Package: wnpp

The current maintainer of nmzmail, Kevin Coyner ,
is apparently not active anymore.  Therefore, I orphan this package now.

Maintaining a package requires time and skills. Please only adopt this
package if you will have enough time and attention to work on it.

If you want to be the new maintainer, please see
https://www.debian.org/devel/wnpp/#howto-o for detailed
instructions how to adopt a package properly.

Some information about this package:

Package: nmzmail
Binary: nmzmail
Version: 1.1-2
Maintainer: Kevin Coyner 
Build-Depends: debhelper (>= 9.2~), autotools-dev, dpkg-dev (>= 1.16.1~), 
libreadline-dev
Architecture: any
Standards-Version: 3.9.3
Format: 1.0
Files:
 f625292a4d7675740b0bcd7bebc40665 1382 nmzmail_1.1-2.dsc
 d049f3d54e4ef77a582a16e33d7ad560 94326 nmzmail_1.1.orig.tar.gz
 49b0471b73d243411830aad460feb59f 4181 nmzmail_1.1-2.diff.gz
Checksums-Sha256:
 1da4af9c2ad65424d35b87ed9de186e8987427aada5e2d1e84ac0531b22f4cce 1382 
nmzmail_1.1-2.dsc
 5cfddc89b4e99c8a320d5db655d3153e35bc4455f07c83f1978811477705c428 94326 
nmzmail_1.1.orig.tar.gz
 f1f0f9809fe1cf0c6274bd6c0911e5420c9f0f9be789bf72b343d5f6d61c6190 4181 
nmzmail_1.1-2.diff.gz
Homepage: http://www.ecademix.com/JohannesHofmann/nmzmail.html
Package-List: 
 nmzmail deb mail optional
Directory: pool/main/n/nmzmail
Priority: source
Section: mail

Package: nmzmail
Source: nmzmail (1.1-2)
Version: 1.1-2+b1
Installed-Size: 30
Maintainer: Kevin Coyner 
Architecture: amd64
Depends: libc6 (>= 2.4), libreadline7 (>= 6.0), namazu2, namazu2-index-tools
Suggests: mutt
Enhances: mutt
Description-fr: indexation et recherche dans des courriels dans des dossiers « 
maildir »
 Le programme nmzmail est un outil, essentiellement destiné à être
 utilisé avec mutt, pour indexer et effectuer des recherches dans des
 dossiers « maildir ». Sur la base des résultats de requêtes à l'aide
 du moteur de recherche namazu2, nmzmail crée un dossier maildir
 contenant des liens symboliques vers les courriels correspondant à la
 recherche. Une macro mutt facilite l'utilisation depuis ce
 programme. Le programme nmzmail est analogue à mairix mais
 probablement plus simple d'utilisation car sa syntaxe de requête est
 celle de namazu2.
 .
 Fonctionnalités :
  - recherche rapide même dans de grandes quantités de courriels ;
  - construction incrémentale des index ;
  - intégration avec mutt ;
  - langage de requêtes riche mais simple, avec expressions régulières ;
  - historique des requêtes.
Description-md5: 8e18e71f0cd6d220de9b538d1eca6afc
Homepage: http://www.ecademix.com/JohannesHofmann/nmzmail.html
Tag: implemented-in::c, interface::text-mode, role::plugin, role::program,
 use::searching, works-with::mail
Section: mail
Priority: optional
Filename: pool/main/n/nmzmail/nmzmail_1.1-2+b1_amd64.deb
Size: 9554
MD5sum: 062e87ea3226a138aa8aa8e2ee93ea72
SHA256: d1151bc95f5b76728cbfe17c12813320902084650a26dd5f1bbecb4e14bd3985


-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature

Bug#929540: O: mrename -- outil pour simplement et automatiquement renommer plusieurs fichiers

[Pierre-Elliott Bécue]

Package: wnpp

The current maintainer of mrename, Kevin Coyner ,
is apparently not active anymore.  Therefore, I orphan this package now.

Maintaining a package requires time and skills. Please only adopt this
package if you will have enough time and attention to work on it.

If you want to be the new maintainer, please see
https://www.debian.org/devel/wnpp/#howto-o for detailed
instructions how to adopt a package properly.

Some information about this package:

Package: mrename
Binary: mrename
Version: 1.2-13
Maintainer: Kevin Coyner 
Build-Depends: debhelper (>= 9), quilt (>= 0.63)
Architecture: all
Standards-Version: 3.9.8
Format: 3.0 (quilt)
Files:
 d229016cab2ddf92494bc76e4c56a9e2 1332 mrename_1.2-13.dsc
 c10df409a45290381efccfd656a34d57 2036 mrename_1.2.orig.tar.gz
 c55061cbacd1b690e96efbed9cd394af 4812 mrename_1.2-13.debian.tar.xz
Checksums-Sha256:
 e7d0b69f95bc9046a7acbf2f69bda9dc338556a2a0b64d95cbc3717fff6ab690 1332 
mrename_1.2-13.dsc
 90526d151bd777540915020c3e9a76083a6f1552601d2a43f8a25b50828643d3 2036 
mrename_1.2.orig.tar.gz
 61850013b51fb4822583b22c88e7ea3ab3b398d9cb9d0140b1009480ace99b84 4812 
mrename_1.2-13.debian.tar.xz
Homepage: http://alfalinux.sourceforge.net/mrename.php3
Package-List: 
 mrename deb utils optional arch=all
Directory: pool/main/m/mrename
Priority: source
Section: utils

Package: mrename
Version: 1.2-13
Installed-Size: 23
Maintainer: Kevin Coyner 
Architecture: all
Description-fr: outil pour simplement et automatiquement renommer plusieurs 
fichiers
 Mass Rename est un simple jeu de deux scripts shell qui facilitent le
 déplacement, renommage ou la copie de plusieurs fichiers à la fois. Il
 permet essentiellement de renommer de manière simple et automatique de
 nombreux fichiers en utilisant un préfixe et un nombre progressif,
 personnalisables. Il permet également de modifier le format de renommage en
 modifiant simplement un des scripts. Il est simple, complet et efficace, et
 n'utilise que du code shell.
Description-md5: 514c4f318a159c36d2a7e87b0f7750d3
Homepage: http://alfalinux.sourceforge.net/mrename.php3
Tag: implemented-in::shell, interface::commandline, role::program,
 scope::utility, works-with::file
Section: utils
Priority: optional
Filename: pool/main/m/mrename/mrename_1.2-13_all.deb
Size: 6410
MD5sum: 9720c032fbf7ad00ffecaa6a18084f94
SHA256: 2e32cd94c9c2d53b184cf2204185a9c0a01df00e600b62961d0c4a1e55bcc8d8


-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature

Bug#929536: O: bcrypt -- utilitaire multiplate-forme de chiffrement de fichier, utilisant blowfish (uniquement déchiffrement)

[Pierre-Elliott Bécue]

Package: wnpp

The current maintainer of bcrypt, Kevin Coyner ,
is apparently not active anymore.  Therefore, I orphan this package now.

Maintaining a package requires time and skills. Please only adopt this
package if you will have enough time and attention to work on it.

If you want to be the new maintainer, please see
https://www.debian.org/devel/wnpp/#howto-o for detailed
instructions how to adopt a package properly.

Some information about this package:

Package: bcrypt
Binary: bcrypt
Version: 1.1-8.1
Maintainer: Kevin Coyner 
Build-Depends: debhelper (>= 7.4~), libz-dev, dpatch
Architecture: any
Standards-Version: 3.8.3
Format: 1.0
Files:
 dd6914e40875c304ed48e5a398624a1f 1021 bcrypt_1.1-8.1.dsc
 1070660c40b574158d4c19a24f6dc6ae 36536 bcrypt_1.1.orig.tar.gz
 f4adb033c3113a8be8b4914770451430 7857 bcrypt_1.1-8.1.diff.gz
Checksums-Sha256:
 16b36eb90f343e236fef95110a886e89c02968d07032eb3c7b84b435c0d74dd3 1021 
bcrypt_1.1-8.1.dsc
 12c05b77c4a80a6d5ecda2ed9742627344c1729bc39b139059f435a47edebfbc 36536 
bcrypt_1.1.orig.tar.gz
 c3ec02e25d2eb1a9baa6d545b3193bd418c69f352eedd2f0c22163c156adc63e 7857 
bcrypt_1.1-8.1.diff.gz
Homepage: http://bcrypt.sourceforge.net/
Package-List: 
 bcrypt deb utils optional arch=any
Directory: pool/main/b/bcrypt
Priority: source
Section: utils

Package: bcrypt
Source: bcrypt (1.1-8.1)
Version: 1.1-8.1+b1
Installed-Size: 41
Maintainer: Kevin Coyner 
Architecture: amd64
Depends: libc6 (>= 2.14), zlib1g (>= 1:1.1.4)
Description-fr: utilitaire multiplate-forme de chiffrement de fichier, 
utilisant blowfish (uniquement déchiffrement)
 AVERTISSEMENT : uniquement pour le déchiffrement de paquet, le chiffrement
 étant
 désactivé. Consultez http://bugs.debian.org/700758.
 Bcrypt est un utilitaire multiplate-forme de chiffrement de fichier. Les
 fichiers chiffrés sont portables pour tous les processeurs et systèmes
 d’exploitation pris en charge. En plus des données chiffrées, bcrypt, par
 défaut écrasera le fichier d’entrée original avec n’importe quoi, trois fois de
 suite avant de le supprimer, dans le but de contrecarrer tout essai de
 récupération de données par des personnes pouvant accéder à votre ordinateur.
 Bcrypt utilise l’algorithme de chiffrement conçu par Bruce Schneier en 1993.
Description-md5: f8886897c7841e20a4ffaca10174c1c1
Homepage: http://bcrypt.sourceforge.net/
Tag: implemented-in::c, interface::commandline, role::program,
 scope::utility, security::cryptography
Section: utils
Priority: optional
Filename: pool/main/b/bcrypt/bcrypt_1.1-8.1+b1_amd64.deb
Size: 18862
MD5sum: 8be9c9f9b52f4392a484d91fa1bb1172
SHA256: a219aa6818b3b5de6ef48ff68e60a4f267b05413de711700ff536f0fdda22588


-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature

Bug#929544: O: urlgrabber -- high-level URL transfer library

[Pierre-Elliott Bécue]

Package: wnpp

The current maintainer of urlgrabber, Kevin Coyner ,
is apparently not active anymore.  Therefore, I orphan this package now.

Maintaining a package requires time and skills. Please only adopt this
package if you will have enough time and attention to work on it.

If you want to be the new maintainer, please see
https://www.debian.org/devel/wnpp/#howto-o for detailed
instructions how to adopt a package properly.

Some information about this package:

Package: urlgrabber
Binary: python-urlgrabber
Version: 3.10.2-1
Maintainer: Kevin Coyner 
Uploaders: Debian Python Modules Team 

Build-Depends: debhelper (>= 9), dh-python, python-all (>= 2.6.6-3~), 
python-pycurl
Architecture: all
Standards-Version: 4.1.1
Format: 3.0 (quilt)
Files:
 f660b8aee06b35fc6097a644a49f37ab 2204 urlgrabber_3.10.2-1.dsc
 9fcf77af476a69da2718e827ea628c6f 84700 urlgrabber_3.10.2.orig.tar.gz
 5e0243d88dc3c191a096716c057b7399 8044 urlgrabber_3.10.2-1.debian.tar.xz
Vcs-Browser: 
https://anonscm.debian.org/cgit/python-modules/packages/urlgrabber.git
Vcs-Git: https://anonscm.debian.org/git/python-modules/packages/urlgrabber.git
Checksums-Sha256:
 9ee5a9652a2f628fbd2c97e08ce04f8bf2e2b44b9b8b358f867fbbf8834891ca 2204 
urlgrabber_3.10.2-1.dsc
 53691185e3d462bb0fa8db853a205ee79cdd4089687cddd22cabb8b3d4280142 84700 
urlgrabber_3.10.2.orig.tar.gz
 02d4c00ad05969ef374a3e354afb33f2748b675fb136eddfb9d14d75f87a3099 8044 
urlgrabber_3.10.2-1.debian.tar.xz
Homepage: http://urlgrabber.baseurl.org/
Dgit: c790fce2265c8e640d7284c941ae2c69b2d43b49 debian archive/debian/3.10.2-1 
https://git.dgit.debian.org/urlgrabber
Package-List: 
 python-urlgrabber deb python optional arch=all
Python-Version: >= 2.5
Directory: pool/main/u/urlgrabber
Priority: source
Section: python

Package: python-urlgrabber
Source: urlgrabber
Version: 3.10.2-1
Installed-Size: 218
Maintainer: Kevin Coyner 
Architecture: all
Provides: python2.7-urlgrabber
Depends: python:any (<< 2.8), python:any (>= 2.7.5-5~), python-pycurl
Description-en: high-level URL transfer library
 urlgrabber dramatically simplifies the fetching of files. It is designed to
 be used in programs that need common (but not necessarily simple)
 url-fetching features. This package provides both a binary and a module, both
 of the name urlgrabber.
 .
 It supports identical behavior for http://, ftp:// and file:/// URIs. It
 provides HTTP keepalive, byte ranges, regets, progress meters, throttling,
 retries, access to authenticated http/ftp servers, and proxies. Additionally
 it has the ability to treat a list of mirrors as a single source and to
 automatically switch mirrors if there is a failure.
Description-md5: ed0376fa018e769af685bd19feaa5af9
Homepage: http://urlgrabber.baseurl.org/
Tag: implemented-in::python, protocol::ftp, protocol::http, role::program,
 role::shared-lib, use::downloading
Section: python
Priority: optional
Filename: pool/main/u/urlgrabber/python-urlgrabber_3.10.2-1_all.deb
Size: 55280
MD5sum: 773d1a36b0c47ff01452e1c967a0788b
SHA256: c91553f50f9b68e9c4c752eff53e4799624c579a6b8a541edc88e49c1c7fb014


-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature

Bug#929545: webext-browserpass: broken symlinks: /usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/browserp...@maximbaz.com/fonts/OpenSans-*.ttf

[Andreas Beckmann]

Package: webext-browserpass
Version: 3.1.1-2
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

>From the attached log (scroll to the bottom...):

0m50.1s ERROR: FAIL: Broken symlinks:
  
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/browserp...@maximbaz.com/fonts/OpenSans-Regular.ttf
 -> ../../../../../fonts/truetype/open-sans/OpenSans-Regular.ttf 
(webext-browserpass)
  
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/browserp...@maximbaz.com/fonts/OpenSans-Light.ttf
 -> ../../../../../fonts/truetype/open-sans/OpenSans-Light.ttf 
(webext-browserpass)

Is webext-browserpass missing a Depends/Recommends/Suggests: fonts-open-sans ?


cheers,

Andreas


webext-browserpass_3.1.1-2.log.gz
Description: application/gzip

Bug#929547: Fails for local addresses

[積丹尼 Dan Jacobson]

Package: libemail-mime-perl
Version: 1.946-1

Suddenly this is failing

use Email::MIME;
my $email = Email::MIME->create(
header_str => [
From => 'casey',
To   => [ 'us...@host.com', 'Name ' ],
],
);
print $email->as_string;

With


Argument contains empty address at /usr/share/perl5/Email/MIME/Encode.pm 
line 70.
From: 
To: us...@host.com, Name 
Date: Sun, 26 May 2019 07:43:41 +0800
MIME-Version: 1.0

That it is a bug is proven by the "empty address" error.

If it objected that there was no "@" then it would have said that instead.

Bug#929546: O: tnef -- outil pour décompresser les pièces jointes de type MIME application/ms-tnef

[Pierre-Elliott Bécue]

Package: wnpp

The current maintainer of tnef, Kevin Coyner ,
is apparently not active anymore.  Therefore, I orphan this package now.

Maintaining a package requires time and skills. Please only adopt this
package if you will have enough time and attention to work on it.

If you want to be the new maintainer, please see
https://www.debian.org/devel/wnpp/#howto-o for detailed
instructions how to adopt a package properly.

Some information about this package:

Package: tnef
Binary: tnef
Version: 1.4.12-1.2
Maintainer: Kevin Coyner 
Build-Depends: debhelper (>= 9), autotools-dev, quilt, dh-autoreconf
Architecture: any
Standards-Version: 3.9.8
Format: 3.0 (quilt)
Files:
 14b2ab5d0c32a43e0dbe094298d71b3c 1884 tnef_1.4.12-1.2.dsc
 59d96464d8aa10349c02ca1edd47f0ac 8463407 tnef_1.4.12.orig.tar.gz
 cd3ca26f77e916f98b45601bd7186988 7380 tnef_1.4.12-1.2.debian.tar.xz
Checksums-Sha256:
 520449bdf8a10d7e8373df7c6bfa3c10ee0ba23f64fdea0d0ffc9d44435b84ba 1884 
tnef_1.4.12-1.2.dsc
 f7dea4c806d2263948ed027dbb8c593191f321b79c73816bb5608c957bc70254 8463407 
tnef_1.4.12.orig.tar.gz
 203994e6fe84fe1454e8e93e440cfe38bc8615bd78773f2f29883ab65c61c546 7380 
tnef_1.4.12-1.2.debian.tar.xz
Homepage: https://github.com/verdammelt/tnef
Package-List: 
 tnef deb text optional arch=any
Directory: pool/main/t/tnef
Priority: source
Section: text

Package: tnef
Version: 1.4.12-1.2
Installed-Size: 98
Maintainer: Kevin Coyner 
Architecture: amd64
Depends: libc6 (>= 2.14)
Recommends: mime-support
Description-fr: outil pour décompresser les pièces jointes de type MIME 
application/ms-tnef
 TNEF est un programme pour décompresser les pièces jointes de type MIME
 application/ms-tnef. C’est typiquement une pièce jointe de seulement Microsoft.
 .
 Le programme TNEF permet de décompresser les pièces jointes encapsulées
 dans une pièce jointe TNEF, en évitant par conséquent la nécessité
 d’utiliser Microsoft Outlook pour afficher la pièce jointe.
Description-md5: b00b9af822a5a170742b5f2da1b92ccd
Homepage: https://github.com/verdammelt/tnef
Tag: implemented-in::c, interface::commandline, role::program,
 scope::utility, use::converting, use::viewing, works-with::mail
Section: text
Priority: optional
Filename: pool/main/t/tnef/tnef_1.4.12-1.2_amd64.deb
Size: 42432
MD5sum: d7897556350def3eca0810cdd7ec592d
SHA256: 4e59c945851e144efd471a306b81f89f1da1e379a6f8e5244400f4599409e25a


-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature

Bug#929548: Updating the libphp-phpmailer Uploaders list

[Pierre-Elliott Bécue]

Source: libphp-phpmailer
Version: 6.0.6-0.1
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

kcoyner has not been working on
the libphp-phpmailer package for quite some time.

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature

Bug#929549: confess $! does not work

[Ian Jackson]

Package: src:dgit
Version: 8.3
Severity: important

Fairly recently I changed a lot of die to confess.

However, confess is less good than die in one important respect:

$ perl -e 'use Carp; open X, ">/dev/eacces" or die $!'
Permission denied at -e line 1.
$ perl -e 'use Carp; open X, ">/dev/eacces" or confess $!'
 at -e line 1.
$

I think this may have something to do with Carp's attempt to save and
restore $!.  Only literally
  confess $!
is affected:

$ perl -e 'use Carp; open X, ">/dev/eacces" or confess "$!"'
Permission denied at -e line 1.
$

so the fix, while textually huge, is simple.

*sigh*

Ian.

-- 
Ian JacksonThese opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.

Bug#929550: O: rpl -- utilitaire de recherche/remplacement récursif intelligent

[Pierre-Elliott Bécue]

Package: wnpp

The current maintainer of rpl, Kevin Coyner ,
is apparently not active anymore.  Therefore, I orphan this package now.

Maintaining a package requires time and skills. Please only adopt this
package if you will have enough time and attention to work on it.

If you want to be the new maintainer, please see
https://www.debian.org/devel/wnpp/#howto-o for detailed
instructions how to adopt a package properly.

Some information about this package:

Package: rpl
Binary: rpl
Version: 1.5.7-1
Maintainer: Kevin Coyner 
Build-Depends: debhelper (>= 9), dh-python, python3-all, python3-setuptools
Architecture: all
Standards-Version: 3.9.8
Format: 3.0 (quilt)
Files:
 78fe1639c108f7966b2e27d4777dbb3c 1352 rpl_1.5.7-1.dsc
 c578307a893ead5b0158cf0fb2bdfdda 12546 rpl_1.5.7.orig.tar.gz
 f627aa77f22be8c74e9cad8eb2510ff0 2932 rpl_1.5.7-1.debian.tar.xz
Checksums-Sha256:
 af86ec53ef6bfdd5d7e979f1fc0018a0cde6eee8cc4d68f20bfa05c3445957d5 1352 
rpl_1.5.7-1.dsc
 53e9ac5e82e034b7f58cf384eb435b5ddfbfa88695184c06947596f3bc1ce58d 12546 
rpl_1.5.7.orig.tar.gz
 cfa436203b8796e8c3970f3ba3675af673a170c954c95bfeef9c0d960d81ebb7 2932 
rpl_1.5.7-1.debian.tar.xz
Homepage: https://github.com/kcoyner/rpl/
Package-List: 
 rpl deb python optional arch=all
Directory: pool/main/r/rpl
Priority: source
Section: utils

Package: rpl
Version: 1.5.7-1
Installed-Size: 34
Maintainer: Kevin Coyner 
Architecture: all
Depends: python3:any (>= 3.2~)
Description-fr: utilitaire de recherche/remplacement récursif intelligent
 rpl est un utilitaire de remplacement de texte. Il remplace des chaînes de
 caractères par d'autres dans de multiples fichiers texte. Il peut travailler
 récursivement sur des répertoires et gère les limitations de recherche
 à des suffixes de fichiers.
Description-md5: cbe1606e04a37f556a7ac9f4b81cfcec
Homepage: https://github.com/kcoyner/rpl/
Tag: implemented-in::python, interface::commandline, role::program,
 scope::utility, works-with::text
Section: utils
Priority: optional
Filename: pool/main/r/rpl/rpl_1.5.7-1_all.deb
Size: 8522
MD5sum: 638ce6ffba6c9082641899a665ddde0b
SHA256: 41d5223b2c85fc6ae5f2b17ecb5d3dc0d8c650999f9b28955ef7fe493dafb07a


-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature

Bug#929551: Updating the pyparsing Uploaders list

[Pierre-Elliott Bécue]

Source: pyparsing
Version: 2.2.0+dfsg1-2
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

kcoyner has not been working on
the pyparsing package for quite some time.

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature

Bug#929552: g++-x86-64-linux-gnu: broken symlink: /usr/share/doc/g++-x86_64-linux-gnu -> cpp-x86_64-linux-gnu

[Andreas Beckmann]

Package: g++-x86-64-linux-gnu
Version: 4:8.3.0-1
Severity: normal
User: debian...@lists.debian.org
Usertags: piuparts
Control: found -1 g++-x86-64-linux-gnu/4:8.3.0-1

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

>From the attached log (scroll to the bottom...):

0m30.7s ERROR: FAIL: Broken symlinks:
  /usr/share/doc/g++-x86_64-linux-gnu -> cpp-x86_64-linux-gnu 
(g++-x86-64-linux-gnu)


Note that the incorrect link uses '_' instead of '-' in source and target.

There were similar bugs in other packages in the past,
e.g. #915678 in gcc-x86-64-linux-gnux32


cheers,

Andreas


g++-x86-64-linux-gnu_4:8.3.0-1.log.gz
Description: application/gzip

Bug#929516: Debian: please provide onion services using next-gen (v3) onion addresses

[Paul Wise]

Control: clone -1 -2
Control: reassign -2 onionbalance
Control: retitle -2 onionbalance: add support for version 3 onion addresses
Control: severity -2 wishlist
Control: forwarded -2 https://github.com/DonnchaC/onionbalance/issues/69
Control: block -1 by -2

On Sat, 2019-05-25 at 11:33 +0200, Dirk Heinrichs wrote:

> Some time ago the tor project introduced 56 character long, next-gen
> (v3) onion addresses, which also utilize stronger cryptography.
> However, Debian is still using v2 onion addresses for its onion
> services.
> 
> Please (also) provide the onion services using v3 addresses.

This is blocked on support for v3 onion addresses in onionbalance
upstream and then in Debian stable or backports.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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