Bug#925515: i2p: [INTL:sv] Swedish debconf strings

[Jonatan Nyberg]

package: i2p
severity: wishlist
tags: patch l10n

Please consider to update this file to translation of debconf. It has
some important changes to the translation.

Kind regards,
Jonatan
# SOME DESCRIPTIVE TITLE.
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the PACKAGE package.
#
# Translators:
# Anders Nilsson , 2015
# cacapo , 2015
# hottuna , 2013
# Jony, 2017
# Martin Svensson , 2011
msgid ""
msgstr ""
"Project-Id-Version: I2P\n"
"Report-Msgid-Bugs-To: i...@packages.debian.org\n"
"POT-Creation-Date: 2017-11-12 14:01+\n"
"PO-Revision-Date: 2019-03-26 06:10+0100\n"
"Last-Translator: Jonatan Nyberg \n"
"Language-Team: Swedish (Sweden) (http://www.transifex.com/otf/I2P/language/;
"sv_SE/)\n"
"Language: sv_SE\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
"X-Generator: Poedit 2.2.1\n"

#. Type: boolean
#. Description
#: ../i2p.templates:2001
msgid "Should the I2P router be started at boot?"
msgstr "Ska I2P-routern startas vid systemstart?"

#. Type: boolean
#. Description
#: ../i2p.templates:2001
msgid ""
"The I2P router can be run as a daemon that starts automatically when your "
"computer boots up. This is the recommended configuration."
msgstr ""
"I2P-routern kan köras som en tjänst (demon) som automatiskt startas när "
"datorn startas. Detta är den rekommenderade konfigurationen."

#. Type: string
#. Description
#: ../i2p.templates:3001
msgid "I2P daemon user:"
msgstr "I2P-demon användare:"

#. Type: string
#. Description
#: ../i2p.templates:3001
msgid ""
"By default I2P is configured to run under the account i2psvc when running as "
"a daemon. To use an **existing** I2P profile you may enter a different "
"account name here. For example, if your previous I2P installation is at /"
"home/user/i2p, you may enter 'user' here."
msgstr ""
"Som standard är I2P konfigurerad för att köras under användaren i2psvc när "
"det körs som tjänst. Om du vill använda en **befintlig** I2P-profil kan du "
"ange ett annat kontonamn här. Till exempel, om din tidigare I2P-installation "
"är på /home/user/I2P, kan du ange \"användare\" här."

#. Type: string
#. Description
#: ../i2p.templates:3001
msgid ""
"Very important: If a user other than the default of 'i2psvc' is entered "
"here, the chosen username *MUST* already exist."
msgstr ""
"Mycket viktigt: om en annan användare än standard 'i2psvc' anges här, "
"*MÅSTE* det valda användarnamnet *redan finnas."

#. Type: string
#. Description
#: ../i2p.templates:4001
msgid "Memory that can be allocated to I2P:"
msgstr "Minne som kan tilldelas I2P:"

#. Type: string
#. Description
#: ../i2p.templates:4001
msgid "By default, I2P will only be allowed to use up to 128MB of RAM."
msgstr "Som standard får I2P endast använda upp till 128 MB RAM."

#. Type: string
#. Description
#: ../i2p.templates:4001
msgid ""
"High bandwidth routers, as well as routers with a lot of active torrents / "
"plugins, may need to have this value increased."
msgstr ""
"För routrar med hög bandbredd samt routrar med en hel del aktiva torrenter / "
"insticksmoduler, kan detta värde behöva ökas."

#. Type: boolean
#. Description
#: ../i2p.templates:5001
msgid "Should the I2P daemon be confined with AppArmor?"
msgstr "Ska I2P-demonen vara begränsad med AppArmor?"

#. Type: boolean
#. Description
#: ../i2p.templates:5001
msgid ""
"With this option enabled I2P will be sandboxed with AppArmor, restricting "
"which files and directories may be accessed by I2P."
msgstr ""
"Med det här alternativet aktiverat kommer I2P att köras i sandlåda med "
"AppArmor, som begränsar vilka filer och mappar som kan kommas åt av I2P."

Bug#894187: autotools-dev: Update config.guess to recognize mips r6

[YunQiang Su]

On Tue, 27 Mar 2018 11:57:07 -0300 Henrique de Moraes Holschuh
 wrote:
> On Tue, 27 Mar 2018, YunQiang Su wrote:
> > On Tue, Mar 27, 2018 at 10:27 PM, Henrique de Moraes Holschuh
> >  wrote:
> > > On Tue, 27 Mar 2018, YunQiang Su wrote:
> > >> We add some new architectures for mips,
> > >> mipsisa{32,64}r6{el,}-unknown-linux-gnu{,abin32,abi64}
> > >>
> > >> These architectures are supported by config.sub,
> > >> while not supported by config.guess now.
>
> ...
>
> > > Have you already written to/talked to GNU config upstream?  Please
> ...
>
> > When I submit this bug report, I X-DEBUG-CC ed to the upstream mailing list,
>
> I see.
>
> > http://lists.gnu.org/archive/html/config-patches/2018-03/msg6.html
>
> Thanks.  Let's wait for the reply from the upstream maintainer.

http://git.savannah.gnu.org/cgit/config.git/commit/?id=fe616913d76ff410e4e316ce9570b22cc25edc1e
this patch has been merged upstream.
So, please consider to backport for Debian.

>
> --
>   Henrique Holschuh
>
>

Bug#925483: tilda: does not start (segfault)

[Gunter Grodotzki]

Thanks Bernhard for the help!

You are right, I am running Gnome/Wayland, and this seems to be
unsupported.

Bug#925514: updated archive.debian.org snapshot?

[Tianon Gravi]

Package: snapshot.debian.org
Severity: normal

It would seem https://snapshot.debian.org/archive/debian-archive/ hasn't
had a snapshot since 2016, which is especially relevant now given that
wheezy and jessie have been removed from the mirrors.

Any chance we could get a newer snapshot of http://archive.debian.org?
O:)

(Your work on snapshot.debian.org is very much appreciated! <3)

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Bug#925513: unblock: python-numpy/1:1.16.2-1

[Sandro Tosi]

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

Please unblock package python-numpy

it looks like i missed the deadline for an automatic transition to testing by a
few hours with the latest upload of numpy, hence opening this ticket (with
attached debdiff). it's a patch release, with only bugfixes (which you can find
documented in the debdiff as part of the upstream changes).

unblock python-numpy/1:1.16.2-1

-- System Information:
Debian Release: buster/sid
  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.14.0-3-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru python-numpy-1.16.1/debian/changelog 
python-numpy-1.16.2/debian/changelog
--- python-numpy-1.16.1/debian/changelog2019-01-31 22:21:17.0 
-0500
+++ python-numpy-1.16.2/debian/changelog2019-03-02 11:30:12.0 
-0500
@@ -1,3 +1,9 @@
+python-numpy (1:1.16.2-1) unstable; urgency=medium
+
+  * New upstream release
+
+ -- Sandro Tosi   Sat, 02 Mar 2019 11:30:12 -0500
+
 python-numpy (1:1.16.1-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru python-numpy-1.16.1/doc/changelog/1.16.2-changelog.rst 
python-numpy-1.16.2/doc/changelog/1.16.2-changelog.rst
--- python-numpy-1.16.1/doc/changelog/1.16.2-changelog.rst  1969-12-31 
19:00:00.0 -0500
+++ python-numpy-1.16.2/doc/changelog/1.16.2-changelog.rst  2019-02-26 
09:33:38.0 -0500
@@ -0,0 +1,25 @@
+
+Contributors
+
+
+A total of 5 people contributed to this release.  People with a "+" by their
+names contributed a patch for the first time.
+
+* Charles Harris
+* Eric Wieser
+* Matti Picus
+* Tyler Reddy
+* Tony LaTorre +
+
+Pull requests merged
+
+
+A total of 7 pull requests were merged for this release.
+
+* `#12909 `__: TST: fix vmImage 
dispatch in Azure
+* `#12923 `__: MAINT: remove 
complicated test of multiarray import failure mode
+* `#13020 `__: BUG: fix signed zero 
behavior in npy_divmod
+* `#13026 `__: MAINT: Add functions 
to parse shell-strings in the platform-native...
+* `#13028 `__: BUG: Fix regression 
in parsing of F90 and F77 environment variables
+* `#13038 `__: BUG: parse shell 
escaping in extra_compile_args and extra_link_args
+* `#13041 `__: BLD: Windows 
absolute path DLL loading
diff -Nru python-numpy-1.16.1/doc/release/1.16.2-notes.rst 
python-numpy-1.16.2/doc/release/1.16.2-notes.rst
--- python-numpy-1.16.1/doc/release/1.16.2-notes.rst1969-12-31 
19:00:00.0 -0500
+++ python-numpy-1.16.2/doc/release/1.16.2-notes.rst2019-02-26 
09:33:38.0 -0500
@@ -0,0 +1,70 @@
+==
+NumPy 1.16.2 Release Notes
+==
+
+NumPy 1.16.2 is a quick release fixing several problems encountered on Windows.
+The Python versions supported are 2.7 and 3.5-3.7. The Windows problems
+addressed are:
+
+- DLL load problems for NumPy wheels on Windows,
+- distutils command line parsing on Windows.
+
+There is also a regression fix correcting signed zeros produced by divmod, see
+below for details.
+
+Downstream developers building this release should use Cython >= 0.29.2 and, if
+using OpenBLAS, OpenBLAS > v0.3.4.
+
+If you are installing using pip, you may encounter a problem with older
+installed versions of NumPy that pip did not delete becoming mixed with the
+current version, resulting in an ``ImportError``. That problem is particularly
+common on Debian derived distributions due to a modified pip.  The fix is to
+make sure all previous NumPy versions installed by pip have been removed. See
+`#12736 `__ for discussion of the
+issue.
+
+
+Compatibility notes
+===
+
+Signed zero when using divmod
+-
+Starting in version 1.12.0, numpy incorrectly returned a negatively signed zero
+when using the ``divmod`` and ``floor_divide`` functions when the result was
+zero. For example::
+
+   >>> np.zeros(10)//1
+   array([-0., -0., -0., -0., -0., -0., -0., -0., -0., -0.])
+
+With this release, the result is correctly returned as a positively signed
+zero::
+
+   >>> np.zeros(10)//1
+   array([0., 0., 0., 0., 0., 0., 0., 0., 0., 0.])
+
+
+Contributors
+
+
+A total of 5 people contributed to this 

Bug#925440: Seriously?!

[Gong S.]

I'm on mobile, so forgive my formatting.

>The file ~/.mkshrc, prepopulated from /etc/skel/.mkshrc, loads /etc/mkshrc if 
>it is non-empty (in Debian and derivatives, as well as several other 
>packagings).
You should not require yet another hidden file in the user's home directory.
My home directory is already messy enough. I clearly do not want it to be even 
more messier.

publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc
Description: application/pgp-keys

Bug#923527: bliss: example segfaults in gmp

[David Bremner]

Bernhard Übelacker  writes:

> Hello David Bremner,
>
>
> I guess from frame 3 having debug information, you either installed
> the dbgsym package or rebuilt the bliss binary package locally?

I compiled /usr/share/doc/bliss-doc/examples/bliss.cc, aka bliss.cc in
the source.

Indeed /usr/bin/bliss works fine on the sample input.

Bug#925512: RFP: FreeFileSync -- Folder comparison and synchronization software

[iandeb]

Package: wnpp

Severity: wishlist

FreeFileSync is a folder comparison and synchronization software that
creates and manages backup copies of all your important files. Instead
of copying every file every time, FreeFileSync determines the
differences between a source and a target folder and transfers only the
minimum amount of data needed. FreeFileSync is Open Source software,
available for Windows, macOS, and Linux.
FreeFileSync works by comparing one or multiple folders on their
content, date or file size and subsequently synchronizing the content
according to user-defined settings. In addition to supporting local file
systems and network shares, FreeFileSync is able to sync to FTP, FTPS,
SFTP and MTP devices.

License: GNU GPLv3

https://freefilesync.org

Bug#922097: inkscape stops with message complaining about an internal illegal instruction on start

[Bernhard Übelacker]

Hello Mattia Rizzolo,
I am just looking at some random crashes, and
tried to detect at which exact instruction
in libgtkmm-2.4.so.1 we are in the given backtrace.

That function contains just two instructions.
But the backtrace from the core dump tells we crashed
at ...459, which is in the middle of the nopl instruction ...

Therefore gdb may not show the line information I guess.

Maybe you can please send the output of the disassemble
and x command from gdb having loaded the core dump?

Kind regards,
Bernhard


(gdb) disassemble $pc-30,$pc+20
Dump of assembler code from 0x7525b43b to 0x7525b46d:
...
   0x7525b447:  nopw   0x0(%rax,%rax,1)
   0x7525b450 :movq   
$0x0,(%rdi)
   0x7525b457 :retq   
   0x7525b458:  nopl   0x0(%rax,%rax,1)
   0x7525b460 :
mov%rsi,(%rdi)
...
End of assembler dump.

(gdb) x/64xb _ZN3Gtk16RadioButtonGroupC1Ev-32
0x7525b430: 0x890xc40xe90x210x940xf40xff0x49
0x7525b438: 0x890xc40xe90x310x940xf40xff0x49
0x7525b440: 0x890xc40xe90x190x940xf40xff0x66
0x7525b448: 0x0f0x1f0x840x000x000x000x000x00
0x7525b450: 0x480xc70x070x000x000x000x000xc3
0x7525b458: 0x0f0x1f0x840x000x000x000x000x00
0x7525b460: 0x480x890x370xc30x660x660x2e0x0f
0x7525b468: 0x1f0x840x000x000x000x000x000x90

Bug#924822: adms is marked for autoremoval from testing

[Felix Salfelder]

On Mon, Mar 25, 2019 at 04:39:08AM +, Debian testing autoremoval watch 
wrote:
> adms 2.3.6-1 is marked for autoremoval from testing on 2019-04-15
> 
> It is affected by these RC bugs:
> 924822: adms: FTBFS: admstpathYacc.y:14604: error: unterminated
> argument list invoking macro "adms_message_error"

possibly related to the perl/yaml upgrade in testing.

could not reproduce the reported issue. but found a similar issue. there
is a typo in admsXml/Makefile.am & FTBFS for me.

-verilogYacc.h: verilogYacc.c
+verilogaYacc.h: verilogaYacc.c

with this [1] it appears to work.

hth
felix

[1] 
https://salsa.debian.org/science-team/adms/commit/4852d662a19017eac73a6b518cedc5eff80a9ea6

Bug#925511: adduser: [INTL:pt] Update on Portuguese translation of manpage

[Américo Monteiro]

Package: adduser
Version: 3.118
3ags: l10n, patch-
Severity: wishlist

Updated Portuguese translation for  adduser's manpage
Translator: Américo Monteiro 
Feel free to use it.

For translation updates please contact 'Last Translator' 

-- 
Melhores cumprimentos/Best regards,

Américo Monteiro




adduser_3.118_pt.po.gz
Description: application/gzip

Bug#924192: ntpsec: at boot ntpsec starts before DNS is available

[Richard Laager]

> sudo apt update
> sudo apt install build-essential devscripts
> sudo apt build-dep ntpsec
> apt source ntpsec
> cd ntpsec-1.1.3+dfsg1
> patch -p1 < ~/ntpsec_1.1.3+dfsg1-3~1.gbpdde9c0.debdiff

I missed a step here, as `apt source` applies the existing patches, so
we apparently need to apply this patch too:

patch -p1 < debian/patches/0001-Fix-for-577-DNS-retry-sloth.patch

> debuild -uc -us
If you can try this and confirm this patch as packaged fixes your
problem, that would help me move forward with this.

-- 
Richard

Bug#925440: Are you sure?

[Thorsten Glaser]

Gong S. dixit:

>No, you did not. I created "/etc/mkshrc" and it is ignored by "mksh".

The file ~/.mkshrc, prepopulated from /etc/skel/.mkshrc,
loads /etc/mkshrc if it is non-empty (in Debian and derivatives,
as well as several other packagings).

If your user account was created before the mksh package
was installed, you need to do the population yourself, but
that’s common Unix knowledge:

cp /etc/skel/.mkshrc ~/

This is, additionally, documented very well in the *first*
bullet point under “Notes for the mksh binary package” in
/usr/share/doc/mksh//README.Debian.gz (preceded only by the
extra links and bug report information). So there. (This is
the customary location for these things in Debian.)


>>...and ASCII is not enough to represent almost all of the languages I
>>speak.

>...and I cannot type anything beyond 0x7F easily on a standard US
>keyboard.

You can, with the Meta key, it adds 128 to the Unicode.

>In a place like this, please use English.

Even if I do, English has quotation marks, apostrophe, etc.
which are not present in ASCII, and some English variants
have additional letters or diacritics.

The need for a common language to understand bugreports does
not necessitate an anglocentric world view.

bye,
//mirabilos
-- 
15:39⎜«mika:#grml» mira|AO: "mit XFree86® wär’ das nicht passiert" - muhaha
15:48⎜ also warum machen die xorg Jungs eigentlich alles
kaputt? :)15:49⎜ thkoehler: weil sie als Kinder nie den
gebauten Turm selber umschmeissen durften?  -- ~/.Xmodmap wonders…

Bug#925508: unblock: debian-edu-install/2.10.21

[Wolfgang Schweer]

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


Please unblock package debian-edu-install

This is a very tiny change needed to set the right Debian Edu version 
for the release. Holger Levsen uploaded the package already.

Full source debdiff against the version in testing attached.

Cced to debian-boot@ and Cyril Brulebois because an ack is needed due to 
udebs.

unblock debian-edu-install/2.10.21

Regards,
Wolfgang

No differences were encountered between the control files

diff -Nru debian-edu-install-2.10.20/debian/changelog 
debian-edu-install-2.10.21/debian/changelog
--- debian-edu-install-2.10.20/debian/changelog 2019-02-15 14:07:13.0 
+0100
+++ debian-edu-install-2.10.21/debian/changelog 2019-03-24 13:42:12.0 
+0100
@@ -1,3 +1,10 @@
+debian-edu-install (2.10.21) unstable; urgency=medium
+
+  [ Wolfgang Schweer ]
+  * Set version number to 10+edu0 in preparation of the Debian Buster release.
+
+ -- Holger Levsen   Sun, 24 Mar 2019 12:42:12 +
+
 debian-edu-install (2.10.20) unstable; urgency=medium
 
   * preseed-values/defaults.common:
diff -Nru debian-edu-install-2.10.20/version debian-edu-install-2.10.21/version
--- debian-edu-install-2.10.20/version  2019-02-15 14:07:13.0 +0100
+++ debian-edu-install-2.10.21/version  2019-03-24 13:42:12.0 +0100
@@ -1 +1 @@
-10+edu0~a0
+10+edu0


signature.asc
Description: PGP signature

Bug#923527: bliss: example segfaults in gmp

[Bernhard Übelacker]

Hello David Bremner,

>> Maybe something got lost in the input file,
>> so you could attach it to the email?
> ok

Thanks for the file, but unfortunately that makes no
difference - works fine in my test VM.


>> Is the backtrace you copied all of the output or
>> did you remove the frame in function main?
> Here is the full backtrace
> Program received signal SIGSEGV, Segmentation fault.
> 0x7fd9b3fea0f9 in __gmpz_set_si () from 
> /usr/lib/x86_64-linux-gnu/libgmp.so.10
> (gdb) bt
> #0  0x7fd9b3fea0f9 in __gmpz_set_si () from 
> /usr/lib/x86_64-linux-gnu/libgmp.so.10
> #1  0x7fd9b453ac10 in bliss::AbstractGraph::search(bool, bliss::Stats&) 
> () from /usr/lib/x86_64-linux-gnu/libbliss.so.2
> #2  0x7fd9b453da3c in 
> bliss::AbstractGraph::find_automorphisms(bliss::Stats&, void (*)(void*, 
> unsigned int, unsigned int const*), void*) () from 
> /usr/lib/x86_64-linux-gnu/libbliss.so.2
> #3  0x55d66f737cd0 in main (argc=2, argv=0x7ffc262cb408) at bliss.cc:297

I guess from frame 3 having debug information, you either installed
the dbgsym package or rebuilt the bliss binary package locally?

As the address offset ...cd0 does not appear in the current
debian binary package's main function, I guess you did a
rebuild with debug information enabled?

Just to be sure, what does a 'which bliss' return?

Can you reproduce the crash also with the official
debian package bliss?

If yes, possibly you can install these dbgsym packages [1]:
bliss-dbgsym libbliss2-dbgsym libgmp10-dbgsym

And forward the output of these gdb commands,
when the crash happened:
info reg
info share
bt full

Kind regards,
Bernhard

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

Bug#925510: netbeans: Netbeans not usable with java in Buster

[Wouter Wijsman]

Package: netbeans
Version: 10.0-3
Severity: important

Dear Maintainer,

I've installed the netbeans package on my Buster installation for Java
development and it is behaving is some very weird ways for me. I
installed it with apt-get.

I also installed Netbeans with Flatpak to see if that worked any
better.
I have not seen any of the issues I'm seeing with the version in the
repo
with that version. The issues I am seeing with the repo version also
very consistent. I can reboot and restart netbeans however many times I
want, they always happen. Updating the system didn't change anything
either.

The following issues have been happening:

Creating a project doesn't work like expected. When you click on finish
in the dialog, the loading screen finishes incredably fast, but then
nothing happens. When looking at the directory where the project should
have been created, you can see it is there. Loading the project doesn't
work well, though. Netbeans does not detect the files or even the
package found in a project created like this.

When I open a project which has been created by a working version of
netbeans, the project is loaded much slower than expected. Instead of
the usual couple of seconds, it takes more than 10 seconds. The
navigator never fills up and just shows please wait. Trying to run the
project doesn't do anything either.

Creating a new java class is weird too. When clicking Finish, the
loading bar goes very fast and the file is created, but I get an error
stating "The file newclass.java already exists". The dialog doesn't
close by itself.

I think it is very likely to all be caused by an error which show up at
the bottom of the screen. The red balloon in the bottom bar reveals an
"Unexpected Exception". The summary of the error is as follows:

A java.lang.NoSuchMethodError exception has occurred.
Please report this at
https://issues.apache.org/jira/projects/NETBEANS/issues,
including a copy of your messages.log file as an attachment.
The messages.log file is located in your
/home/wouter/.netbeans/10.0/var/log folder.

The full log can be found here: https://pastebin.com/0wgJNt15

I hope that helps. I can provide more information if needed.

Kind regards,
Wouter



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

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

Versions of packages netbeans depends on:
ii  default-jdk [java8-sdk] 2:1.11-71
ii  libnb-apisupport3-java  10.0-3
ii  libnb-ide14-java10.0-3
ii  libnb-java5-java10.0-3
ii  libnb-platform18-java   10.0-2
ii  openjdk-11-jdk [java8-sdk]  11.0.3+1-1

netbeans recommends no packages.

netbeans suggests no packages.

-- no debconf information

Bug#924938: unblock: healpix-java/3.40-1

[Ole Streicher]

Hi Jonathan

thanks for the offer! It will take a moment since javahelpr (jh_build)
is broken for the moment: #925507. When this is fixed, I am even not
sure whether we can keep the original since the problem that caused
#923752 seems to be fixed in javahelper as well, #923748

https://bugs.debian.org/925507
https://bugs.debian.org/923752
https://bugs.debian.org/923748

I will report back once the things look clearer.

Best

Ole

Bug#925509: netbeans: Netbeans not usable with java in Buster

[Wouter Wijsman]

Package: netbeans
Version: 10.0-3
Severity: important

Dear Maintainer,

I've installed the netbeans package on my Buster installation for Java
development and it is behaving is some very weird ways for me. I
installed it with apt-get.

I also installed Netbeans with Flatpak to see if that worked any
better.
I have not seen any of the issues I'm seeing with the version in the
repo
with that version. The issues I am seeing with the repo version also
very consistent. I can reboot and restart netbeans however many times I
want, they always happen. Updating the system didn't change anything
either.

The following issues have been happening:

Creating a project doesn't work like expected. When you click on finish
in the dialog, the loading screen finishes incredably fast, but then
nothing happens. When looking at the directory where the project should
have been created, you can see it is there. Loading the project doesn't
work well, though. Netbeans does not detect the files or even the
package found in a project created like this.

When I open a project which has been created by a working version of
netbeans, the project is loaded much slower than expected. Instead of
the usual couple of seconds, it takes more than 10 seconds. The
navigator never fills up and just shows please wait. Trying to run the
project doesn't do anything either.

Creating a new java class is weird too. When clicking Finish, the
loading bar goes very fast and the file is created, but I get an error
stating "The file newclass.java already exists". The dialog doesn't
close by itself.

I think it is very likely to all be caused by an error which show up at
the bottom of the screen. The red balloon in the bottom bar reveals an
"Unexpected Exception". The summary of the error is as follows:

A java.lang.NoSuchMethodError exception has occurred.
Please report this at 
https://issues.apache.org/jira/projects/NETBEANS/issues,
including a copy of your messages.log file as an attachment.
The messages.log file is located in your
/home/wouter/.netbeans/10.0/var/log folder.

The full log can be found here: https://pastebin.com/0wgJNt15

I hope that helps. I can provide more information if needed.

Kind regards,
Wouter

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

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

Versions of packages netbeans depends on:
ii  default-jdk [java8-sdk] 2:1.11-71
ii  libnb-apisupport3-java  10.0-3
ii  libnb-ide14-java10.0-3
ii  libnb-java5-java10.0-3
ii  libnb-platform18-java   10.0-2
ii  openjdk-11-jdk [java8-sdk]  11.0.3+1-1

netbeans recommends no packages.

netbeans suggests no packages.

-- no debconf information

--1553552508-eximdsn-479279952--

Bug#921471: Should pdf2htmlex be removed?

[Johannes Schauer]

Control: retitle -1 ROM: pdf2htmlex -- dead upstream
Control: reassign -1 ftp.debian.org

Quoting Moritz Mühlenhoff (2019-03-25 22:20:36)
> On Tue, Feb 05, 2019 at 11:18:01PM +0100, Johannes Schauer wrote:
> > On Tue, 05 Feb 2019 23:12:03 +0100 Moritz Muehlenhoff  
> > wrote:
> > > Should pdf2htmlex be removed? It's RC-buggy for over a year and upstream
> > > development seems to have stopped:
> > > http://pdf2htmlex.blogspot.de/2016/12/looking-for-new-maintainer.html
> > 
> > Yes, possibly.
> > 
> > Funny, that you are reporting this today because just a few hours ago, I
> > reached out to a fork that claims to continue development. Unfortunately,
> > things don't look rosy over there either:
> > 
> > https://github.com/pdf2htmlEX/pdf2htmlEX/issues/20
> 
> Johannes, seven weeks later, what's your take, shall we remove it or keep it?

Alright, I think it's time to pull the plug. :(

Reassigning and retitling accordingly.


signature.asc
Description: signature

Bug#925483: tilda: does not start (segfault)

[Bernhard Übelacker]

Hello Guenter Grodotzki,
I am not the maintainer for tilda, just got here and
tried to collect some more information.

For some reason your upstream report contains one
(interesting) lines more than made it into the debian report.

Just as a hint: the real important information has to be
queried from gdb by the "bt" or backtrace command.
For bug reports sometimes "bt full" might be helpful too.

Adding the debug symbol packages [1] would be even more helpful.


I have tried to reproduce in a minimal amd64 buster VM.
Tilda just run fine within a openbox or plasma X11 session.

I just received a crash when running within a gnome session:

(gdb) bt
#0  0x7fcc0191c4bb in require_socket (dpy=0x563f2b027810) at 
../../src/xcb_io.c:68
#1  0x7fcc0191cd05 in require_socket (dpy=0x563f2b027810) at 
../../src/xcb_io.c:518
#2  _XFlush (dpy=0x563f2b027810) at ../../src/xcb_io.c:515
#3  0x7fcc0191f7f5 in _XGetRequest (dpy=dpy@entry=0x563f2b027810, 
type=type@entry=119 'w', len=len@entry=4) at ../../src/XlibInt.c:1717
#4  0x7fcc0190b7dd in XGetModifierMapping (dpy=0x563f2b027810) at 
../../src/ModMap.c:42
#5  0x563f2ad6660a in reload_modmap (modmap=0x563f2b745cd0, 
keymap=0x563f2b046840) at src/eggaccelerators.c:82
#6  egg_keymap_get_modmap (keymap=0x563f2b046840) at 
src/eggaccelerators.c:173
#7  0x563f2ad66850 in egg_keymap_resolve_virtual_modifiers 
(keymap=0x563f2b046840, virtual_mods=EGG_VIRTUAL_LOCK_MASK, 
concrete_mods=0x563f2af81b44 ) at src/eggaccelerators.c:56
#8  0x563f2ad6c64a in lookup_ignorable_modifiers 
(keymap=0x563f2b046840) at src/tomboykeybinder.c:88
#9  0x563f2ad6cc1e in tomboy_keybinder_init () at 
src/tomboykeybinder.c:319
#10 0x563f2ad65635 in main (argc=, argv=) 
at src/tilda.c:842

At least the address offset from my frame 0 and your frame 0
is equal, therefore I guess you are running also
a gnome/wayland session?

This issue are describing in more detail
upstream issues [2] and [3].

Kind regards,
Bernhard

[1] https://wiki.debian.org/HowToGetABacktrace#Installing_the_debugging_symbols
[2] https://github.com/lanoxx/tilda/issues/150
[3] https://github.com/lanoxx/tilda/issues/314

# Buster amd64 qemu VM 2019-03-25

apt update
apt dist-upgrade

#

apt install systemd-coredump xserver-xorg lightdm openbox tilda

systemctl start lightdm

export DISPLAY=:0
tilda

-> no segfault

#

apt install systemd-coredump xserver-xorg sddm plasma-desktop dbus-x11 tilda

systemctl start sddm

export DISPLAY=:0
tilda

-> no segfault

#

apt install systemd-coredump gdb weston gdm3 gnome-session tilda

systemctl start gdm3

export DISPLAY=:0
tilda

-> segfaults

#


apt install dpkg-dev devscripts systemd-coredump gdb weston gdm3 gnome-session 
tilda tilda-dbgsym libx11-6-dbgsym



mkdir /tmp/source/libx11-6/orig -p
cd/tmp/source/libx11-6/orig
apt source libx11-6
cd


set width 0
set pagination off
directory /tmp/source/libx11-6/orig/libx11-1.6.7/debian/patches
bt


#

benutzer@debian:~$ tilda
Unable to open lock directory: /home/benutzer/.cache/tilda/locks
Erstelle Verzeichnis: '/home/benutzer/.config/tilda'
Speicherzugriffsfehler (Speicherabzug geschrieben)


dmesg
[  273.20] tilda[14800]: segfault at 40 ip 7fcc0191c4bb sp 
7ffc7815cce0 error 4 in libX11.so.6.3.0[7fcc018f5000+8a000]
[  273.208894] Code: 31 c9 48 89 fb 48 8d 35 f3 05 00 00 48 83 ec 10 64 48 8b 
04 25 28 00 00 00 48 89 44 24 08 31 c0 48 8b 87 30 0a 00 00 49 89 e0 <8b> 50 40 
85 d2 48 89 fa 48 8b 38 0f 95 c1 e8 32 a9 fd ff 85 c0 74


root@debian:~# coredumpctl list
TIMEPID   UID   GID SIG COREFILE  EXE
Mon 2019-03-25 22:29:54 CET   14800  1000  1000  11 present   /usr/bin/tilda


root@debian:~# coredumpctl gdb 14800
   PID: 14800 (tilda)
   UID: 1000 (benutzer)
   GID: 1000 (benutzer)
Signal: 11 (SEGV)
 Timestamp: Mon 2019-03-25 22:29:54 CET (1min 37s ago)
  Command Line: tilda
Executable: /usr/bin/tilda
 Control Group: /user.slice/user-1000.slice/session-5.scope
  Unit: session-5.scope
 Slice: user-1000.slice
   Session: 5
 Owner UID: 1000 (benutzer)
   Boot ID: 889af76e9cd9473da884a4f59630c55b
Machine ID: 32f43b50ac8c4b21941bc0b02f8e7811
  Hostname: debian
   Storage: 
/var/lib/systemd/coredump/core.tilda.1000.889af76e9cd9473da884a4f59630c55b.14800.155354939400.lz4
   Message: Process 14800 (tilda) of user 1000 dumped core.

Stack trace of thread 14800:
#0  0x7fcc0191c4bb n/a (libX11.so.6)
#1  0x7fcc0191cd05 _XFlush (libX11.so.6)
#2  0x7fcc0191f7f5 _XGetRequest (libX11.so.6)
#3  0x7fcc0190b7dd XGetModifierMapping (libX11.so.6)
#4  0x563f2ad6660a n/a (tilda)
#5  0x563f2ad66850 n/a (tilda)
#6  0x563f2ad6c64a 

Bug#919207: Bug#923711: squashfs-tools: Please apply frag_deflator_thread removal patch

[Alexander Couzens]

Hi Laszlo,

>  I'm playing with the different patched versions for hours now.
> Indeed, it seems with your latest patch the memory leak is bearable.

Nice to hear. I compressed a 8GB tree of toolchains and rootfs with
valgrind (took > 10h ;) without any noticable leaks.

> I've never tested CPU usage before. I've realized it's rhapsodical,
> sometimes all my CPU cores utilized on 100%, sometimes one on ~15%.
> Should I wait for other fix(es)?

No. I'ven't looked into it. But this is a long standing issue.

First of all, as squashfs-tools wasn't written in the last years, when
reproducible builds became more famous. So it's not written
with reproducible building in mind.
For me is reproducible builds more important than using all cpu cores.
But I don't use it with gigabytes images.

It got a bit worse with removing the frag_deflator thread, as there
is one workload thread less. The old frag_deflator thread has been
spawnd $cpus times. fragments are small files.

The cpu usage will also depend on the compression algorithm.
If you like to profile mksquashfs-tools, I'm happy to help to understand
the code base.

Maybe there is a different approach to do it reproducible. Create
first an index over all files, ensure a proper order through multiple
queues via an index. But I'm not sure, if this would be really faster
than it's now. Btw: even with `-processors 1` it will spawn multiple
threads which should use more than 1 core.

Best,
lynxis


pgpZwUTI6Rfzp.pgp
Description: OpenPGP digital signature

Bug#925507: jh_build fails when source files are specified

[Ole Streicher]

Package: javahelper
Version: 0.72.6
Severity: serious
Control: affects -1 src:healpix-java
Control: blocks -1 923752

The javahelper package fails when files are specified as src. The source 
package healpix-java has the following debian/javabuild:

healpix.jar src/healpix/essentials/*.java

When I compile this (healpix-java version 3.40-1), I get the following 
error (the files ofcourse exist):

jh_build
jh_build: Ignoring src/healpix/essentials/*.java because it does not exist

When I include the options in d/rules instead:

override_jh_build:
jh_build healpix.jar src/healpix/essentials/*.java
[...]

I get a very mystic error:

jh_build healpix.jar src/healpix/essentials/*.java
error: invalid flag: -quiet
Usage: javac  
use --help for a list of possible options
jh_build: /usr/lib/jvm/default-java/bin/javac -g -cp 
/usr/share/java/fits.jar:_jh_build.healpix -d debian/_jh_build.healpix -quiet 
-encoding ISO8859-1 -source 1.7 -target 1.7 
src/healpix/essentials/CircleFinder.java src/healpix/essentials/Compressor.java 
src/healpix/essentials/Constants.java src/healpix/essentials/FastMath.java 
src/healpix/essentials/FitsUtil.java src/healpix/essentials/Fxyf.java 
src/healpix/essentials/HealpixBase.java 
src/healpix/essentials/HealpixMapDouble.java 
src/healpix/essentials/HealpixMapFloat.java 
src/healpix/essentials/HealpixProc.java 
src/healpix/essentials/HealpixTables.java 
src/healpix/essentials/HealpixUtils.java src/healpix/essentials/Hploc.java 
src/healpix/essentials/Moc.java src/healpix/essentials/MocFitsIO.java 
src/healpix/essentials/MocQuery.java src/healpix/essentials/MocStringIO.java 
src/healpix/essentials/Pointing.java src/healpix/essentials/RangeSet.java 
src/healpix/essentials/Scheme.java src/healpix/essentials/Vec3.java 
src/healpix/essentials/Zphi.java src/healpix/essentials/package-info.java 
returned exit code 2

Looking into the sources show that the "-quiet" flag is indeed 
unconditionally added there, and seems to not work at least with the 
current openjdk-11-jdk-headless:amd64 (11.0.3+4-1).

https://salsa.debian.org/java-team/javatools/blob/master/jh_build#L229

Best regards

Ole

Bug#925506: stretch-pu: package java-common/0.58+deb9u1

[Moritz Muehlenhoff]

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

How about the following debdiff to address the fallout of
the Xul deprecation in icedtea-web (#921748) for the next
point update?

default-jre is the only reverse dependency of
default-java-plugin, so the patch also removes default-java-plugin
along.

Cheers,
Moritz

diff -Nru java-common-0.58/debian/changelog 
java-common-0.58+deb9u1/debian/changelog
--- java-common-0.58/debian/changelog   2017-01-06 13:55:31.0 +0100
+++ java-common-0.58+deb9u1/debian/changelog2019-03-25 21:49:32.0 
+0100
@@ -1,3 +1,10 @@
+java-common (0.58+deb9u1) stretch; urgency=medium
+
+  * Remove default-java-plugin as the icedtea-web Xul plugin is going away
+  * Also drop the Recommends: to default-java-plugin in default-jre
+
+ -- Moritz Mühlenhoff   Mon, 25 Mar 2019 21:49:32 +0100
+
 java-common (0.58) unstable; urgency=medium
 
   * Team upload.
diff -Nru java-common-0.58/debian/control java-common-0.58+deb9u1/debian/control
--- java-common-0.58/debian/control 2017-01-06 13:47:00.0 +0100
+++ java-common-0.58+deb9u1/debian/control  2019-03-25 21:49:32.0 
+0100
@@ -23,7 +23,6 @@
 Architecture: any
 Depends: default-jre-headless (= ${binary:Version}), ${jre},
  ${misc:Depends}
-Recommends: default-java-plugin
 Provides: ${jre:provides}
 Description: Standard Java or Java compatible Runtime
  This dependency package points to the Java runtime, or Java compatible
@@ -77,16 +76,6 @@
  kit, or Java compatible development kit recommended for Debian, which is
  ${doc} for ${jre:arch}.
 
-Package: default-java-plugin
-Architecture: any
-Depends: default-jre (= ${binary:Version}), ${plugin}, ${misc:Depends}
-Provides: icedtea-plugin
-Description: Default Java Plugin for running applets and Java Web Start 
applications
- This dependency package points to the default Java Plugin recommended
- for the ${jre:arch} architecture. The Java Plugin adds the ability to run
- Java applets from a web browser and launch Java Web Start applications using
- the Java Network Launch Protocol (JNLP).
-
 Package: gcj-native-helper
 Architecture: any
 Pre-Depends: ${misc:Pre-Depends}
diff -Nru java-common-0.58/debian/rules java-common-0.58+deb9u1/debian/rules
--- java-common-0.58/debian/rules   2017-01-04 09:52:35.0 +0100
+++ java-common-0.58+deb9u1/debian/rules2019-03-25 21:49:32.0 
+0100
@@ -28,10 +28,7 @@
   jvmdir   = java-gcj
 endif
 
-# Build default-java-plugin for the architectures supporting icedtea-web only
-ifeq (,$(filter $(_java_host_arch),$(java_plugin_architectures)))
-  p_plugin  =
-endif
+p_plugin  =
 
 jre_provides   = java-runtime, java2-runtime, $(shell seq --format 
java%.f-runtime --separator ', ' 5 $(java_default_version))
 jhl_provides   = java-runtime-headless, java2-runtime-headless, $(shell seq 
--format java%.f-runtime-headless --separator ', ' 5 $(java_default_version))

Bug#922157: "show hidden icons" menu is shown when left-click any icon in the system-tray

[Dennis Heddicke]

Everything works fine now. The bug seems to be fixed.

Bug#925505: RFS: dhcpoptinj/0.4.4-1 [ITP]

[Andreas Misje]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

 Package name: dhcpoptinj
 Version : 0.4.4-1
 Upstream Author : Andreas Misje 
 URL : https://github.com/misje/dhcpoptinj
 License : GPL-3
 Section : net

It builds those binary packages:

  dhcpoptinj - DHCP option injector

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

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


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

  dget -x 
https://mentors.debian.net/debian/pool/main/d/dhcpoptinj/dhcpoptinj_0.4.4-1.dsc

More information about dhcpoptinj can be obtained from
https://github.com/misje/dhcpoptinj

Changes since the last upload:

Initial release. Closes: #923605


Best regards
-- 
Andreas Misje

Bug#921471: Should pdf2htmlex be removed?

[Moritz Mühlenhoff]

On Tue, Feb 05, 2019 at 11:18:01PM +0100, Johannes Schauer wrote:
> On Tue, 05 Feb 2019 23:12:03 +0100 Moritz Muehlenhoff  wrote:
> > Should pdf2htmlex be removed? It's RC-buggy for over a year and upstream
> > development seems to have stopped:
> > http://pdf2htmlex.blogspot.de/2016/12/looking-for-new-maintainer.html
> 
> Yes, possibly.
> 
> Funny, that you are reporting this today because just a few hours ago, I
> reached out to a fork that claims to continue development. Unfortunately,
> things don't look rosy over there either:
> 
> https://github.com/pdf2htmlEX/pdf2htmlEX/issues/20

Johannes, seven weeks later, what's your take, shall we remove it
or keep it?

Cheers,
Moritz

Bug#925503: RM: tbdialout -- RoQA; broken with Thunderbird 60, unmaintained

[Moritz Muehlenhoff]

Package: ftp.debian.org
Severity: normal

Please remove tbdialout, it's broken with Thunderbird 60 (913443) without
maintainer followup and hasn't seen an upload for 1.5 years.

Cheers,
Moritz

Bug#918171: Broken with Thunderbird 60

[Moritz Mühlenhoff]

On Sat, Feb 09, 2019 at 11:41:39AM +0100, Daniel Baumann wrote:
> tag 918171 + fixed-upstream
> thanks
> 
> Hi,
> 
> upstream version is at 0.9 and works nicely with thunderbird 60 from
> sid/buster. It would be nice if you could update package in time to make
> it into buster.

The package seems unmaintained, Daniel are you interested in adopting
it? Otherwise I'd file a removal bug.

Cheers,
Moritz

Bug#925504: RM: timeline/0.5-4

[Moritz Muehlenhoff]

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

Please remove timeline/0.5-4 from stable, it's broken with Thunderbird 60 and 
dead upstream.
It was already removed from unstable.

Cheers,
Moritz

Bug#864017: release-notes: Assumes /etc/apt/sources.list is used (and not /etc/apt/sources.list.d/*.list or deb822) [general]

[Paul Gevers]

Hi Justin,

On 24-03-2019 23:27, Justin B Rye wrote:
> Paul Gevers wrote:
>>> Justin Rye (#863975):
 Incidentally, the release-notes mention /etc/apt/sources.list plenty
 of times but never /etc/apt/sources.list.d/*.list files; and soon
 we'll also have the option of deb822-style .sources files - see the
 sources.list(5) in stretch.  We'll need to come up with a generic term
 and use that instead; I'd suggest "APT source-list files".
>>
>> I gave this a first shot. What do you think of the attached patch
>> (should we do this via Salsa merge requests)?
> 
> (I know nothing of git, and am therefore finding salsa considerably
> harder to use than the old alioth setup, but I'm hoping to get it
> worked out in time to contribute with the release notes.)

Have you already looked at the web interface for commenting on merge
requests? No knowledge of git required what so ever.

> All of the changes in your diff look good to me, though there's a typo
> here:
> 
>>
>> -Lines in sources.list starting with deb ftp: and 
>> pointing to debian.org
>> -addresses should be changed into deb http: lines.
>> +Lines in APT source-list files starting with deb 
>> ftp: or
>> +URIs: ftp:and pointing to debian.org
> ^
>   extra space needed

Fixed (updated patch attached for the changes in the previous bug as well).

> More importantly, the FTP servers were shut down in April 2017, so
> this update was required for Jessie-to-Stretch, wasn't it?  At any
> rate, I find it hard to imagine very many machines as cobwebby as this
> would be using a deb822-format APT config with "URIs: ftp:"!

So, should we drop that paragraph altogether? I was wondering about that
as well.

> Also, when we first mention APT configuration we need to set out what
> we mean by "APT source-list files", if only by pointing at
> sources.list(5).

I wanted to link to that man page as well, so let's find a place. I'm
nearly of to bed now, so if you find a good spot before I do tomorrow,
don't hesitate to mail.

Paul
From 58b3e890479278d4ac5862c87beaf65f137e7f12 Mon Sep 17 00:00:00 2001
From: Paul Gevers 
Date: Sun, 24 Mar 2019 20:31:48 +0100
Subject: [PATCH] Generalize use of APT source-list files

Closes: #864017
---
 en/old-stuff.dbk | 25 +++--
 en/upgrading.dbk | 72 +---
 2 files changed, 53 insertions(+), 44 deletions(-)

diff --git a/en/old-stuff.dbk b/en/old-stuff.dbk
index 0a53d737..13583ab1 100644
--- a/en/old-stuff.dbk
+++ b/en/old-stuff.dbk
@@ -27,9 +27,9 @@ upgraded to the latest  point release.
 
 
 
-Checking your sources list
+Checking your APT source-list files
 
-If any of the lines in your /etc/apt/sources.list
+If any of the lines in your APT source-list files
 refer to stable, it effectively
 points to  already. This might not be what you want if
 you are not ready yet for the upgrade.  If you have already run
@@ -43,28 +43,35 @@ that case you will have to decide for yourself whether you want to continue or
 not.  It is possible to downgrade packages, but that is not covered here.
 
 
-Open the file /etc/apt/sources.list with your favorite
+  Open the relevant APT source-list file, e.g.
+  /etc/apt/sources.list, with your favorite
 editor (as root) and check all lines beginning with
 deb http:, deb https:,
-deb tor+http:, deb tor+https: or
-deb ftp: for a reference to
+deb tor+http:, deb tor+https:,
+deb ftp:, URIs: http:,
+URIs: https:,
+URIs: tor+http:, URIs: tor+https: or
+URIs: ftp: for a reference to
 stable.  If you find any, change
 stable to .
 
 
   
-Lines in sources.list starting with deb ftp: and pointing to debian.org
-addresses should be changed into deb http: lines.
+Lines in APT source-list files starting with deb ftp: or
+URIs: ftp: and pointing to debian.org
+addresses should be changed into deb http: lines.
   
 
 
-If you have any lines starting with deb file:, you will have
+  If you have any lines starting with deb file: or
+  URIs: file:, you will have
 to check for yourself if the location they refer to contains an
  or a  archive.
 
 
   
-Do not change any lines that begin with deb cdrom:.
+Do not change any lines that begin with deb cdrom: or
+URIs: cdrom:.
 Doing so would invalidate the line and you would have to
 run apt-cdrom again.  Do not be alarmed if a
 cdrom: source line refers to unstable.
diff --git a/en/upgrading.dbk b/en/upgrading.dbk
index a22924f3..5f9e6d8d 100644
--- a/en/upgrading.dbk
+++ b/en/upgrading.dbk
@@ -293,7 +293,7 @@ $ apt-forktracer | sort
   package manager aptitude.  If a package is scheduled for
   removal or update in the package manager, it might negatively impact the
   upgrade procedure.  Note that correcting this is only possible if your
-  sources.list still points to 
+  APT source-list files still point to 
   and not to stable or ; see .
 
@@ 

Bug#925502: ITP: golang-github-josephspurrier-goversioninfo -- Golang Microsoft Windows File Properties/Version Info and Icon Resource Generator

[Dawid Dziurla]

Package: wnpp
Severity: wishlist
Owner: Dawid Dziurla 

* Package name: golang-github-josephspurrier-goversioninfo
  Version : 0.0~git20190209.63e6d1a-1
  Upstream Author : Joseph Spurrier
* URL : https://github.com/josephspurrier/goversioninfo
* License : Expat
  Programming Lang: Go
  Description : Golang Microsoft Windows File Properties/Version Info and 
Icon Resource Generator

 Package creates a syso file which contains
 Microsoft Windows Version Information
 and an optional icon.
 When you run "go build",
 Go will embed the version information and
 an optional icon and
 an optional manifest in the executable.
 Go will automatically use the syso file if
 it's in the same directory as the main() function.

This package is a dependency of another package "golang-fyne-fyne" (#925466)

Bug#925499: bowtie2 arm64 (aarch64) package

[Jun Aruga]

Source: bowtie2
Severity: wishlist

Dear bowtie2 maintainer,

As the latest version bowtie2 2.3.5 started to support arm64 (aarch64) as a
experiment.
Is it possible for you to prepare bowtie2 arm64 (aarch64) deb pacakge?

Here is my contribution to support it on the bowtie2 upstream project.
https://github.com/BenLangmead/bowtie2/pull/216
You can refer how to build it by seeing Makefile.

We need a patch to the source code.
See 4 sed commands in the bottom part of Dockerfile-aarch64.

Thank you.





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

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

Bug#925501: unblock: horizon/14.0.2-3

[Thomas Goirand]

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

Please unblock package horizon

The changelog is self-explanatory:

horizon (3:14.0.2-3) unstable; urgency=medium

  * openstack-dashboard: Add Breaks against obsolete packages from Stretch:
python-app-catalog-ui, python-designate-dashboard, python-ironic-ui,
python-murano-dashboard, python-zaqar-ui (Closes: #925226). Thanks a lot
to Andreas Beckmann for his report, patch and tests.

 -- Thomas Goirand   Mon, 25 Mar 2019 21:44:52 +0100

So, according to Andreas and his tests, the above Breaks: are needed to
correctly perform an upgrade from Stretch to Buster.

Please unblock horizon/14.0.2-3 to allow this fix to enter Buster.

Bug#925500: ITP: shapeit4 -- fast and accurate method for estimation of haplotypes

[Dylan Aïssi]

Package: wnpp
Owner: Debian Med Packaging Team 
Severity: wishlist

Package name: shapeit4
Upstream Author : Olivier Delaneau
URL: https://odelaneau.github.io/shapeit4/
License: Expat
Description: fast and accurate method for estimation of haplotypes (phasing)
 Segmented HAPlotype Estimation and Imputation Tools version 4 (SHAPEIT4).
 SHAPEIT4 is a fast and accurate method for estimation of haplotypes (aka
 phasing) for SNP array and sequencing data.

This package will be maintained by the Debian Med Packaging Team at:
https://salsa.debian.org/med-team/shapeit4

Bug#925464: new upstream release (1.3rc1)

[Chris Knadle]

Hello again Antoine.  :)

Antoine Beaupre:
> Package: mumble
> Version: 1.2.18-1+deb9u1
> Severity: normal

Filed against stable rather than unstable; oops.  ;-)

> Upstream has finally got their act together and made a release on the
> 1.3 branch. It's just an rc1, but maybe it would be better to ship
> that with buster than the current git snapshot. That might need some
> convincing with the release team, but I think it's worth the trouble.
> 
> See:
> 
> https://github.com/mumble-voip/mumble/issues/2865
> 
> A.

Okay I've read through issue #2865 -- thank you for discussing the release
issues there.  I totally agree that it would be preferable to ship 1.3.0-rc1
rather than the release I had to do from git because:

  - the release from git doesn't come with a GPG signature,
so no GPG verification can be done
  - DFSG tarball repacking required due to non-free documents in git submodules
(which also wrecks GPG verification)
  - the release version numbers when shipping from git are terrible
  - the debian/watch file can't be used when making a tarball from git,
at least when also needing to make DFSG modifications afterwards,
AFAICT
  - when users write bug reports, they're for a version that doesn't exist
upstream  :(

I'm willing to do the work needed to release this to Buster, assuming the
Release Team are agreeable, due to all of the issues above.  What I'll do to
start with is have a look at the -rc1 tarball ASAP to see if it requires DFSG
repacking.

And thanks for your continued in Mumble, BTW.  It helps me to know that doing
the work I do helps others.

   -- Chris

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

Bug#919636: pelican: "make publish" with Atom feed yields "CRITICAL: TypeError: not all arguments converted during string formatting"

[Witold Baryluk]

Package: pelican
Version: 4.0.1+dfsg-1
Followup-For: Bug #919636

I also got this issue on a fresh install.

Using upstream fix https://github.com/getpelican/pelican/pull/2515 solved this 
for me.

Please include in the package. Thanks! :)

PS. Problem was also reported upstream, i.e.
https://github.com/getpelican/pelican/issues/2487 plus some similar other
issues.



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

Kernel: Linux 4.19.0-2-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 pelican depends on:
ii  python33.7.2-1
ii  python3-blinker1.4+dfsg1-0.2
ii  python3-dateutil   2.7.3-3
ii  python3-docutils   0.14+dfsg-4
ii  python3-feedgenerator  1.9-1
ii  python3-jinja2 2.10-1
ii  python3-markdown   3.0.1-3
ii  python3-pkg-resources  40.8.0-1
ii  python3-pygments   2.3.1+dfsg-1
ii  python3-six1.12.0-1
ii  python3-tz 2018.9-1
ii  python3-unidecode  1.0.23-1

pelican recommends no packages.

Versions of packages pelican suggests:
pn  pandoc   
pn  pelican-doc  
pn  python3-bs4  

-- no debconf information

Bug#925498: afterstep: v2.2.12-12 FTBFS due to patch#57 generates libAfterImage/Makefile incorrectly.

[Jim Turner]

Package: afterstep
Version: 2.2.12-12
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

Bug is actually against the latest Debian maintainer patch (patch#57)
by Robert Luberda , 30-Aug, 2018; which causes a FTBFS:

Issue 1:  (FTBFS) due to an extraneous, "@TTF_CFLAGS@" variable
appended to line 107 ("NCS_EXTRA=...") of libAfterImage/Makefile.in, which
is unreplaced in the generated Makefile, causing compile failure.

Issue 2:  The purpose of patch#57 was to remove the now-depreciated (and
now non-existing) "freetype-config" function once used to configure
truetype fonts, and instead use pkg-config.  Problem is that the patch
properly removes it from configure.in, but NOT from configure itself
causing "--with-ttf" to no longer work (effectively always "no").

I simply untacked the latest source package v2.2.12-12 from Debian Testing
(http://ftp.gr.debian.org/debian/) on March 25, 2019, ran:

./configure
make

and it fails to compile;
...
gcc -O3 -DNO_DEBUG_OUTPUT -fPIC  -c xwrap.c
/bin/rm -f libAfterBase.a
ar clq libAfterBase.a ashash.o aslist.o asvector.o audit.o fs.o layout.o
mystri$
ranlib libAfterBase.a
make[1]: Leaving directory '/tmp/pristine/afterstep-2.2.12/libAfterBase'
make[1]: Entering directory '/tmp/pristine/afterstep-2.2.12/libAfterImage'
 asimage.c
 gcc -O3 -DNO_DEBUG_OUTPUT -fPIC  -mmmx -Winline --param inline-unit-
growth=100$
 gcc: error: TTF_CFLAGS@: No such file or directory
 make[1]: *** [Makefile:381: asimage.o] Error 1
 make[1]: Leaving directory '/tmp/pristine/afterstep-2.2.12/libAfterImage'
 make: *** [Makefile:177: all] Error 1

 I was successful in building afterstep after applying the following patch
 I created to correct both these issues, please consider, and edit as
 necessary for a new "patch#58" to resolve these two issues.

 Thanks,

Jim Turner



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

Kernel: Linux 5.0.0-3.1-liquorix-amd64 (SMP w/4 CPU cores; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.iso88591, LC_CTYPE=en_US.iso88591 (charmap=ISO-8859-1), 
LANGUAGE=en_US.iso88591 (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages afterstep depends on:
ii  afterstep-data  2.2.12-12
ii  aterm   9.22-6
ii  imagemagick 8:6.9.10.23+dfsg-2
ii  imagemagick-6.q16 [imagemagick] 8:6.9.10.23+dfsg-2
ii  libafterimage0  2.2.12-12
ii  libafterstep1   2.2.12-12
ii  libc6   2.28-8
ii  libdbus-1-3 1.12.12-1.0nosystemd1
ii  libglib2.0-02.58.3-1
ii  libgtk2.0-0 2.24.32-3
ii  libreadline77.0-5
ii  libx11-62:1.6.7-1
ii  libxext62:1.3.3-1+b2
ii  lxterminal [x-terminal-emulator]0.3.2-1
ii  menu2.1.47
ii  menu-xdg0.6
ii  perl5.28.1-4
ii  roxterm-gtk3 [x-terminal-emulator]  2.9.5-1
ii  rxvt-unicode [x-terminal-emulator]  9.22-6
ii  sensible-utils  0.0.12
ii  ucf 3.0038+nmu1

Versions of packages afterstep recommends:
ii  gnome-themes-extra  3.28-1

Versions of packages afterstep suggests:
pn  asmail
ii  asmon 0.71-5.1+b1
ii  mc3:4.8.22-1
pn  wmcpuload 
ii  wmitime   0.5-2+b1
ii  xscreensaver  5.42+dfsg1-1

-- no debconf information
diff libAfterImage/configure libAfterImage/configure.NEW
index bc74bfe..9995dda 100755
--- libAfterImage/configure
+++ libAfterImage/configure.NEW
@@ -6443,210 +6443,257 @@ AFTERIMAGE_LIBS="$AFTERIMAGE_LIBS -lm"
 
 
 TTF_INCLUDES=
+have_ttf=
+if test "$with_ttf" = no; then
+   have_ttf=disabled
+else
+   if test -z "$PKG_CONFIG"; then
+   # Extract the first word of "pkg-config", so it can be a 
program name with args.
+set dummy pkg-config; ac_word=$2
+{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
+$as_echo_n "checking for $ac_word... " >&6; }
+if ${ac_cv_path_PKG_CONFIG+:} false; then :
+  $as_echo_n "(cached) " >&6
+else
+  case $PKG_CONFIG in
+  [\\/]* | ?:[\\/]*)
+  ac_cv_path_PKG_CONFIG="$PKG_CONFIG" # Let the user override the test with a 
path.
+  ;;
+  *)
+  as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
+for as_dir in $PATH
+do
+  IFS=$as_save_IFS
+  test -z "$as_dir" && as_dir=.
+for ac_exec_ext in '' $ac_executable_extensions; do
+  if { test -f "$as_dir/$ac_word$ac_exec_ext" && $as_test_x 
"$as_dir/$ac_word$ac_exec_ext"; }; then
+ac_cv_path_PKG_CONFIG="$as_dir/$ac_word$ac_exec_ext"
+$as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" 
>&5
+break 2
+  

Bug#902493: apache2-bin: Event MPM listener thread may get blocked by SSL shutdowns

[Martijn Grendelman]

On 3/25/19 8:25 PM, Sven Hartge wrote:
> On 24.03.19 02:02, Sven Hartge wrote:
> 
>> So far, so good. I have your packages running on the main webmail server
>> and the main web server for my university and so far everything is fine,
>> while default packages and the test1 packages with mpm_event would
>> normally start showing the symptoms after ~12 hours.
> 
> Still no problems here and both systems have seen some serious traffic
> the last days, with the new semester starting next week and all.

This is good news! I'll try and see if I can install the packages on a
few servers myself this week. Thanks!!

Kind regards,
Martijn.





signature.asc
Description: OpenPGP digital signature

Bug#924891: glibc: FTBFS: /<>/build-tree/amd64-libc/conform/UNIX98/ndbm.h/scratch/ndbm.h-test.c:1:10: fatal error: ndbm.h: No such file or directory

[Lucas Nussbaum]

On 22/03/19 at 17:30 +0100, Florian Weimer wrote:
> > About the archive rebuild: The rebuild was done on EC2 VM instances from
> > Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
> > failed build was retried once to eliminate random failures.
> 
> I believe the actual test failure is tst-pkey.
> 
> Presumably, this rebuild was performed on some Xeon SP CPU.  Do you
> know which model?  Do you have any information about the kernel and
> hypervisor used?
> 
> 32-bit protection key support has had issues from time to time.

Hi,

Below is /proc/cpuinfo on one of the VM. I believe that they are all the
same, but I'm not 100% sure.

I don't have any information about the kernel/hypervisor used on the
host system. In the VM, it's the current stretch kernel:
# uname -a
Linux ip-172-31-3-87 4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27) x86_64 
GNU/Linux

- Lucas

processor   : 0
vendor_id   : GenuineIntel
cpu family  : 6
model   : 85
model name  : Intel(R) Xeon(R) Platinum 8175M CPU @ 2.50GHz
stepping: 4
microcode   : 0x25a
cpu MHz : 2500.000
cache size  : 33792 KB
physical id : 0
siblings: 4
core id : 0
cpu cores   : 2
apicid  : 0
initial apicid  : 0
fpu : yes
fpu_exception   : yes
cpuid level : 13
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm 
constant_tsc rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq ssse3 
fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave 
avx f16c rdrand hypervisor lahf_lm abm 3dnowprefetch invpcid_single kaiser 
fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx avx512f 
avx512dq rdseed adx smap clflushopt clwb avx512cd avx512bw avx512vl xsaveopt 
xsavec xgetbv1 xsaves ida arat pku ospke
bugs: cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf
bogomips: 5000.00
clflush size: 64
cache_alignment : 64
address sizes   : 46 bits physical, 48 bits virtual
power management:

processor   : 1
vendor_id   : GenuineIntel
cpu family  : 6
model   : 85
model name  : Intel(R) Xeon(R) Platinum 8175M CPU @ 2.50GHz
stepping: 4
microcode   : 0x25a
cpu MHz : 2500.000
cache size  : 33792 KB
physical id : 0
siblings: 4
core id : 1
cpu cores   : 2
apicid  : 2
initial apicid  : 2
fpu : yes
fpu_exception   : yes
cpuid level : 13
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm 
constant_tsc rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq ssse3 
fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave 
avx f16c rdrand hypervisor lahf_lm abm 3dnowprefetch invpcid_single kaiser 
fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx avx512f 
avx512dq rdseed adx smap clflushopt clwb avx512cd avx512bw avx512vl xsaveopt 
xsavec xgetbv1 xsaves ida arat pku ospke
bugs: cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf
bogomips: 5000.00
clflush size: 64
cache_alignment : 64
address sizes   : 46 bits physical, 48 bits virtual
power management:

processor   : 2
vendor_id   : GenuineIntel
cpu family  : 6
model   : 85
model name  : Intel(R) Xeon(R) Platinum 8175M CPU @ 2.50GHz
stepping: 4
microcode   : 0x25a
cpu MHz : 2500.000
cache size  : 33792 KB
physical id : 0
siblings: 4
core id : 0
cpu cores   : 2
apicid  : 1
initial apicid  : 1
fpu : yes
fpu_exception   : yes
cpuid level : 13
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm 
constant_tsc rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq ssse3 
fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave 
avx f16c rdrand hypervisor lahf_lm abm 3dnowprefetch invpcid_single kaiser 
fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx avx512f 
avx512dq rdseed adx smap clflushopt clwb avx512cd avx512bw avx512vl xsaveopt 
xsavec xgetbv1 xsaves ida arat pku ospke
bugs: cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf
bogomips: 5000.00
clflush size: 64
cache_alignment : 64
address sizes   : 46 bits physical, 48 bits virtual
power management:

processor   : 3
vendor_id   : GenuineIntel
cpu family  : 6
model   : 85
model name  : Intel(R) Xeon(R) Platinum 8175M CPU @ 2.50GHz
stepping: 4
microcode   : 0x25a
cpu MHz : 2500.000
cache size  : 33792 KB
physical id : 0
siblings: 4
core id : 1

Bug#925487: Wrong attached file

[Jonatan Nyberg]

The attached file is wrong, I have made a new bug report with the right
one.

Bug#925496: linux-image-4.19.0-2-amd64: Latency increase with r8169 and default coalescing settings

[Mike Crowe]

Package: src:linux
Version: 4.19.16-1
Severity: normal

After upgrading the "server" from Stretch to Buster, performance of our
embedded client devices which mount their root filesystem over NFSv2 from
said server dropped considerably. The time from mount to full system
operation of these clients was previously approximately 20s when using
Stretch. After upgrading to Buster, this rose to over 100s.

Comparing packet captures from the network switch and the server appeared
to show discrepancies of up to 9ms between the time the switch claims the
packet was sent and the time the server claims to have seen it.

The default coalesce parameters with linux-image-4.19.0-2 4.19.16-1 for the
r8169 driver used on the affected machine are:

 Coalesce parameters for eth0:
 Adaptive RX: off  TX: off
 stats-block-usecs: 0
 sample-interval: 0
 pkt-rate-low: 0
 pkt-rate-high: 0

 rx-usecs: 200
 rx-frames: 4
 rx-usecs-irq: 0
 rx-frames-irq: 0

 tx-usecs: 200
 tx-frames: 4
 tx-usecs-irq: 0
 tx-frames-irq: 0

If I run:

 ethtool -C eth0 rx-frames 0

then performance returns to what we saw with Stretch's 4.9 kernel.

Booting from the Buster linux-image-4.19.0-2-amd64 kernel running on
machine using the tg3 driver did not show this problem. Although its
default coalesce parameters are slightly different (rx-usecs: 20,
rx-frames: 5), performance is still good on this machine if I set rx-usecs
to 200. Even if I set rx-usecs to 1000, I only see a small impact on
performance resulting in the above timing increasing to about 23s. I think
this means that the r8169 driver is misbehaving when receive coalescing is
enabled, and not just that the slowdown is due to the receive delay.

I also tested against a machine using the e1000e driver which defaults to
rx-usecs 3, rx-frames 0. Although I could set rx-usecs higher, I was unable
to increase rx-frames.

Here's a summary of these results in a more-easily digested form:

|-+-+--+---+---|
| linux-image version | Driver  | rx-usecs | rx-frames | Time  |
|-+-+--+---+---|
| 4.9.0-8-amd64   | r8169   |  N/A |   N/A | ~20s  |
|-+-+--+---+---|
| 4.19.0-2-amd64  | r8169 (default) |  200 | 4 | ~100s |
|-+-+--+---+---|
| 4.19.0-2-amd64  | r8169   |  200 | 0 | ~20s  |
|-+-+--+---+---|
| 4.19.0-2-amd64  | tg3 (default)   |   20 | 5 | ~20s  |
|-+-+--+---+---|
| 4.19.0-2-amd64  | tg3 |  200 | 5 | ~20s  |
|-+-+--+---+---|
| 4.19.0-2-amd64  | tg3 | 1000 | 5 | ~23s  |
|-+-+--+---+---|
| 4.19.0-2-amd64  | e1000e  |3 | 0 | ~20s  |
|-+-+--+---+---|

Thanks.

Mike.


-- Package-specific info:
** Version:
Linux version 4.19.0-2-amd64 (debian-ker...@lists.debian.org) (gcc version 
8.2.0 (Debian 8.2.0-14)) #1 SMP Debian 4.19.16-1 (2019-01-17)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.19.0-2-amd64 
root=UUID=cd3a93bd-1549-4619-8d6b-a0f7680082f4 ro quiet

** Not tainted

** Kernel log:
[0.00] microcode: microcode updated early to revision 0x25, date = 
2018-04-02
[0.00] Linux version 4.19.0-2-amd64 (debian-ker...@lists.debian.org) 
(gcc version 8.2.0 (Debian 8.2.0-14)) #1 SMP Debian 4.19.16-1 (2019-01-17)
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.19.0-2-amd64 
root=UUID=cd3a93bd-1549-4619-8d6b-a0f7680082f4 ro quiet
[0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point 
registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[0.00] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, 
using 'standard' format.
[0.00] BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0009d7ff] usable
[0.00] BIOS-e820: [mem 0x0009d800-0x0009] reserved
[0.00] BIOS-e820: [mem 0x000e-0x000f] reserved
[0.00] BIOS-e820: [mem 0x0010-0xc4a46fff] usable
[0.00] BIOS-e820: [mem 0xc4a47000-0xc4a4dfff] ACPI NVS
[0.00] BIOS-e820: [mem 0xc4a4e000-0xc4e98fff] usable
[0.00] BIOS-e820: [mem 0xc4e99000-0xc52b5fff] reserved
[0.00] BIOS-e820: [mem 0xc52b6000-0xd86a7fff] usable
[0.00] BIOS-e820: [mem 

Bug#925497: google-android-installers: [INTL:sv] Swedish debconf strings

[Jonatan Nyberg]

package: google-android-installers
severity: wishlist
tags: patch l10n

Please consider to add this file to translation of debconf. It has some
small fixes.

Regards,
Jonatan
# SOME DESCRIPTIVE TITLE.
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the google-android-platform-installers package.
# FIRST AUTHOR , YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: google-android-platform-installers\n"
"Report-Msgid-Bugs-To: google-android-platform-installers@packages.debian."
"org\n"
"POT-Creation-Date: 2016-07-19 20:36+\n"
"PO-Revision-Date: 2019-03-25 21:18+0100\n"
"Last-Translator: Jonatan Nyberg \n"
"Language-Team: \n"
"Language: sv\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Poedit 2.2.1\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"

#. Type: select
#. Description
#: ../google-android-platform-24-installer.templates:1001
#: ../google-android-platform-23-installer.templates:1001
#: ../google-android-platform-22-installer.templates:1001
msgid "Mirror to download packages ?"
msgstr "Spegel för att hämta paket?"

#. Type: select
#. Description
#: ../google-android-platform-24-installer.templates:1001
#: ../google-android-platform-23-installer.templates:1001
#: ../google-android-platform-22-installer.templates:1001
msgid ""
"Please select your prefered mirror to download Google's Android packages "
"from."
msgstr "Välj din föredragna spegel att hämta Googles Android-paket från."

Bug#925495: fookebox: [INTL:sv] Updates to Swedish debconf strings

[Jonatan Nyberg]

package: fookebox
severity: wishlist
tags: patch l10n

Please consider to add this file to translation of debconf. It has
small fixes.

Regards,
Jonatan
# SOME DESCRIPTIVE TITLE.
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the fookebox package.
# FIRST AUTHOR , YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: fookebox\n"
"Report-Msgid-Bugs-To: fooke...@packages.debian.org\n"
"POT-Creation-Date: 2014-11-02 06:06+0100\n"
"PO-Revision-Date: 2019-03-25 21:16+0100\n"
"Last-Translator: Jonatan Nyberg \n"
"Language: sv\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
"X-Generator: Poedit 2.2.1\n"
"Language-Team: \n"

#. Type: boolean
#. Description
#: ../templates:1001
msgid "Remove old fookebox database?"
msgstr "Radera gamla fookebox-databas?"

#. Type: boolean
#. Description
#: ../templates:1001
msgid "Previous versions of fookebox used a database to store schedule information. This database is no longer used and can be safely removed."
msgstr "Tidigare versioner av fookebox använde en databas för att lagra schemainformation. Denna databas används inte längre och raderas."

Bug#925493: openstreetmap-carto: [INTL:sv] Swedish debconf strings

[Sebastiaan Couwenberg]

Control: tags -1 pending

Hi Jonatan,

Thanks for the translation, it has been updated in git.

You may want to prioritize other packages that are still in testing though.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#925494: bilibop: [INTL:sv] Swedish debconf strings

[Jonatan Nyberg]

package: bilibop
severity: wishlist
tags: patch l10n

Please consider to add this file to translation of debconf. It has
small fixes.

Regards,
Jonatan
# Swedish debconf templates translation for bilibop.
# This file is distributed under the same license as the bilibop package.
# Jonatan Nyberg , 2016.
#
msgid ""
msgstr ""
"Project-Id-Version: bilibop 0.5.1\n"
"Report-Msgid-Bugs-To: quid...@poivron.org\n"
"POT-Creation-Date: 2013-11-23 10:14+\n"
"PO-Revision-Date: 2019-03-25 21:13+0100\n"
"Last-Translator: Jonatan Nyberg \n"
"Language: sv\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
"X-Generator: Poedit 2.2.1\n"
"Language-Team: \n"

#. Type: boolean
#. Description
#: ../bilibop-rules.templates:1001
msgid "Do you intend to install bilibop-rules on a Live System ?"
msgstr "Har du för avsikt att installera bilibop-regler på ett Live-system?"

#. Type: boolean
#. Description
#: ../bilibop-rules.templates:1001
msgid ""
"Some bilibop-rules settings can be useful on non-volatile Operating Systems, "
"when running from a removable and writable media (USB sticks, external HDD or "
"SD cards); but they are currently useless or even harmful for LiveCD or "
"LiveUSB systems."
msgstr ""
"Några bilibop-regel-inställningar kan vara användbara på icke-instabila "
"operativsystem, när de körs från ett borttagbart och skrivbart media (USB-"
"minnen, extern hårddisk eller SD-kort); men de är för närvarande onödiga eller "
"till och med skadliga för LiveCD- eller LiveUSB-system."

#. Type: boolean
#. Description
#: ../bilibop-rules.templates:1001
msgid ""
"If you choose this option, no other question will be asked; bilibop udev rules "
"will be applied but nothing else will be modified on your system. Note that in "
"that case, this package is overkill and you should probably replace it by the "
"lighter but as much as efficient bilibop-udev package."
msgstr ""
"Om du väljer det här alternativet, kommer ingen annan fråga ställas; bilibop "
"udev-reglerna kommer att tillämpas, men ingenting annat kommer att ändras i "
"systemet. Observera att i detta fall, är detta paket överdrivet och du bör "
"antagligen ersätta det med det lättare men lika effektivt bilibop-udev-paket."

#. Type: boolean
#. Description
#: ../bilibop-rules.templates:2001
msgid "Do you want to use custom bilibop rules and build them now ?"
msgstr "Vill du använda anpassade bilibop-regler och bygga dem nu?"

#. Type: boolean
#. Description
#: ../bilibop-rules.templates:2001
msgid ""
"If tens of removable media are plugged on the computer your system boots from, "
"bilibop udev rules can significantly increase boot time. This can be avoided "
"by using custom udev rules, which are specific to the device your system is "
"installed on."
msgstr ""
"Om tiotals flyttbara media är inkopplade på datorn ditt system startar upp "
"från, kan bilibop udev-regler avsevärt öka uppstarttiden. Detta kan undvikas "
"genom att använda anpassade udev-regler, som är specifika för enheten systemet "
"är installerat på."

#. Type: boolean
#. Description
#: ../bilibop-rules.templates:2001
msgid ""
"That said, if this device can boot from different hardware port types (as USB/"
"Firewire, USB/eSATA, USB/MMC/SD, etc.), you should check the resulting rules "
"by booting your system on the alternative port type, and if necessary by "
"running 'dpkg-reconfigure bilibop-rules' again with proper options, or even by "
"editing '/etc/udev/rules.d/66-bilibop.rules'."
msgstr ""
"Som sagt, om denna enhet kan starta från olika hårdvaruporttyper (som USB/"
"Firewire, USB/eSATA, USB/MMC/SD, osv.), bör du kontrollera de erhållna "
"reglerna genom att starta datorn på den alternativa porttypen, och om "
"nödvändigt genom att köra 'dpkg-reconfigure bilibop-rules' igen med rätta "
"valmöjligheter, eller till och med genom att redigera '/etc/udev/rules.d/66-"
"bilibop.rules'."

#. Type: select
#. Choices
#: ../bilibop-rules.templates:3001
msgid "keep existing custom rules"
msgstr "behåll befintliga anpassade regler"

#. Type: select
#. Choices
#: ../bilibop-rules.templates:3001
msgid "rebuild custom rules"
msgstr "bygg om anpassade regler"

#. Type: select
#. Choices
#: ../bilibop-rules.templates:3001
msgid "remove custom rules"
msgstr "radera anpassade regler"

#. Type: select
#. Description
#: ../bilibop-rules.templates:3002
msgid "What do you want to do with your custom rules ?"
msgstr "Vad vill du göra med dina anpassade regler?"

#. Type: select
#. Description
#: ../bilibop-rules.templates:3002
msgid ""
"The file '/etc/udev/rules.d/66-bilibop.rules' exists. It is specific to the "
"drive on which your system is installed and overrides the one, more generic, "
"that is provided by the bilibop-rules package (in '/lib/udev/rules.d')."
msgstr ""
"Filen '/etc/udev/rules.d/66-bilibop.rules' finns. Den är specifikt för den "
"enhet som systemet är installerat på och åsidosätter den mera 

Bug#919207: Bug#923711: squashfs-tools: Please apply frag_deflator_thread removal patch

[GCS]

On Mon, Mar 25, 2019 at 3:50 PM Alexander Couzens  wrote:
> Here is an updated patch to match debian's state of squashfs-tools.
 I'm playing with the different patched versions for hours now.
Indeed, it seems with your latest patch the memory leak is bearable.
I've never tested CPU usage before. I've realized it's rhapsodical,
sometimes all my CPU cores utilized on 100%, sometimes one on ~15%.
Should I wait for other fix(es)?

Thanks,
Laszlo/GCS

Bug#925493: openstreetmap-carto: [INTL:sv] Swedish debconf strings

[Jonatan Nyberg]

package: openstreetmap-carto
severity: wishlist
tags: patch l10n

Please consider to add this file to translation of debconf. It has
small fixes.

Regards,
Jonatan
# SOME DESCRIPTIVE TITLE.
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the openstreetmap-carto package.
# FIRST AUTHOR , YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: openstreetmap-carto\n"
"Report-Msgid-Bugs-To: openstreetmap-ca...@packages.debian.org\n"
"POT-Creation-Date: 2015-10-11 13:38+0200\n"
"PO-Revision-Date: 2019-03-25 21:05+0100\n"
"Last-Translator: Jonatan Nyberg \n"
"Language: sv\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
"X-Generator: Poedit 2.2.1\n"
"Language-Team: \n"

#. Type: boolean
#. Description
#: ../openstreetmap-carto-common.templates:2001
msgid "Download OpenStreetMap data files from the Internet?"
msgstr "Hämta OpenStreetMap-datafiler från Internet?"

#. Type: boolean
#. Description
#: ../openstreetmap-carto-common.templates:2001
msgid "The openstreetmap-carto stylesheet uses several data files that must be downloaded from the Internet."
msgstr "OpenStreetMap-carto-formatmall använder flera datafiler som måste hämtas från Internet."

#. Type: boolean
#. Description
#: ../openstreetmap-carto-common.templates:2001
msgid "If you choose not to do this now, it can be done manually later by running the \"get-shapefiles.sh\" script in the /usr/share/openstreetmap-carto-common directory."
msgstr "Om du väljer att inte göra det nu kan det göras manuellt senare genom att köra \"get-shapefiles.sh\"-skriptet i mappen /usr/share/openstreetmap-carto-common."

#. Type: string
#. Description
#: ../openstreetmap-carto.templates:2001
msgid "PostgreSQL database name:"
msgstr "PostgreSQL-databasnamn:"

#. Type: string
#. Description
#: ../openstreetmap-carto.templates:2001
msgid "The openstreetmap-carto stylesheet uses a PostgreSQL database to store OpenStreetMap data."
msgstr "OpenStreetMap-carto formatmall använder en PostgreSQL-databas för att lagra OpenStreetMap-data."

#. Type: string
#. Description
#: ../openstreetmap-carto.templates:2001
msgid "Please choose the name for this database."
msgstr "Välj namnet för denna databas."

Bug#925320: [Android-tools-devel] Bug#925320: Acknowledgement (android-platform-tools-apksig: apksigner fails to run on OpenJDK 8 due to UnsupportedClassVersionError)

[Hans-Christoph Steiner]

Can you tell me more about the use case for this?  my understanding is
that openjdk-8 will not be supported in buster.

.hc

Tiago Daitx:
> Hi,
> 
> Please consider my upload to mentors as a fix for this issue
> https://mentors.debian.net/package/android-platform-tools-apksig
> https://mentors.debian.net/debian/pool/main/a/android-platform-tools-apksig/android-platform-tools-apksig_0.8-3.dsc
> 
> Regards,
> Tiago
> 
> ___
> Android-tools-devel mailing list
> android-tools-de...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/android-tools-devel
> 

Bug#925492: neurodebian: [INTL:sv] Updates to Swedish debconf strings

[Jonatan Nyberg]

package: neurodebian
severity: wishlist
tags: patch l10n

Please consider to add this file to translation of debconf. It has
small fixes.

Regards,
Jonatan
# Swedish translation of NeuroDebian debconf templates.
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the NeuroDebian package.
# FIRST AUTHOR , YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: neurodebian\n"
"Report-Msgid-Bugs-To: neurodeb...@packages.debian.org\n"
"POT-Creation-Date: 2015-06-23 18:57+0200\n"
"PO-Revision-Date: 2019-03-25 21:01+0100\n"
"Last-Translator: Jonatan Nyberg \n"
"Language: sv\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
"X-Generator: Poedit 2.2.1\n"
"Language-Team: \n"

#. Type: title
#. Description
#: ../neurodebian.templates:2001
msgid "NeuroDebian APT repository installer"
msgstr "NeuroDebian APT förråd-installerare"

#. Type: boolean
#. Description
#: ../neurodebian.templates:3001
msgid "Enable the NeuroDebian package repository?"
msgstr "Aktivera NeuroDebian-paketsförrådet?"

#. Type: boolean
#. Description
#: ../neurodebian.templates:3001
msgid "The NeuroDebian project provides a separate APT repository with software that is not available in Debian, including datasets and backported new releases."
msgstr "NeuroDebian-projektet tillhandahåller ett separat APT-förråd med programvara som inte är tillgänglig i Debian, inklusive datauppsättningar och bakåtporterade nya utgåvor."

#. Type: boolean
#. Description
#: ../neurodebian.templates:3001
msgid "If you choose this option, these packages will be available for installation and upgrades."
msgstr "Om du väljer det här alternativet kommer dessa paket att vara tillgängliga för installation och uppgraderingar."

#. Type: boolean
#. Description
#: ../neurodebian.templates:3001
msgid "Even though these packages are closely maintained by the NeuroDebian team, enabling this additional archive may compromise the integrity of the system."
msgstr "Även om dessa paket är nära underhållna av NeuroDebian-teamet, kan aktivering av ytterligare detta förråd äventyra systemets integritet."

#. Type: select
#. Choices
#: ../neurodebian.templates:4001
msgid "automatic"
msgstr "automatisk"

#. Type: select
#. Choices
#: ../neurodebian.templates:4001
msgid "${releases}"
msgstr "${releases}"

#. Type: select
#. Description
#: ../neurodebian.templates:4002
msgid "Release name of the base system:"
msgstr "Bassystemets utgivningsnamn:"

#. Type: select
#. Description
#: ../neurodebian.templates:4002
msgid "Please specify the appropriate Debian or Ubuntu release codename (for instance \"stretch\" or \"trusty\")."
msgstr "Ange lämpligt Debian eller Ubuntu kodnamn (till exempel \"stretch\" eller \"trusty\")."

#. Type: select
#. Description
#: ../neurodebian.templates:4002
msgid "If this is set to \"automatic\"', the release name is chosen according to the output of \"apt-cache policy\". If the release name for this system is not \"${release}\", you should choose the specific one which matches best."
msgstr "Om detta är inställt på \"automatisk\" väljs utgivningsnamnet enligt utdata från \"apt-cache policy\". Om utgivningsnamnet för det här systemet inte är \"${release}\", bör du välja den specifika som matchar bäst."

#. Type: select
#. Description
#: ../neurodebian.templates:5001
msgid "NeuroDebian mirror to use:"
msgstr "NeuroDebian-spegel att använda:"

#. Type: select
#. Description
#: ../neurodebian.templates:5001
msgid "The NeuroDebian project has a number of community-maintained mirrors around the globe."
msgstr "NeuroDebian-projektet har ett antal gemensamt underhållna speglar runt om i världen."

#. Type: select
#. Description
#: ../neurodebian.templates:5001
msgid "If you do not know which mirror URL to choose, select one of:"
msgstr "Om du inte vet vilken spegelwebbadress att välja, välj en av:"

#. Type: select
#. Description
#: ../neurodebian.templates:5001
msgid ""
" * origin: the original NeuroDebian repository;\n"
" * best: will try to use netselect to select the \"closest\" mirror.\n"
"   This may fail depending on the current mirror setup and the\n"
"   configuration of the firewall. If netselect is not available, the\n"
"   default mirror will be used."
msgstr ""
"* ursprung: det ursprungliga NeuroDebian förrådet;\n"
"* bäst: kommer att försöka använda netselect att välja \"närmaste\" spegel.\n"
".   Detta kan misslyckas beroende på nuvarande spegel-inställningar och\n"
"   konfiguration av brandväggen. Om netselect inte är tillgänglig\n"
"   kommer standard spegel att användas."

#. Type: select
#. Description
#: ../neurodebian.templates:6001
msgid "NeuroDebian flavor to use:"
msgstr "NeuroDebian-flavor att använda:"

#. Type: select
#. Description
#: ../neurodebian.templates:6001
msgid "The NeuroDebian project adheres to the Debian Free Software Guidelines, and offers three packages areas, classified by license, for 

Bug#925491: debomatic: [INTL:pt] Updated Portuguese translation - prog messages

[Américo Monteiro]

Package: debomatic
Version: 0.24-1
Tags: l10n, patch
Severity: wishlist

Updated Portuguese translation for  debomatic's messages
Translator: Américo Monteiro 
Feel free to use it.

For translation updates please contact 'Last Translator' 

-- 
Melhores cumprimentos/Best regards,

Américo Monteiro

-


debomatic_0.24-1_pt.po.gz
Description: application/gzip

Bug#905309: nvidia-modeset: WARNING: GPU:0: Lost display notification (0:0x00000000); continuing

[Allan Wind]

I just observed this problem with (nvidia-kernel-dkms) 410.104-1.


/Allan
--
Allan Wind
Yaxto - Runs Your Business

Bug#925489: unblock: elogind/241.1-1+debian1

[Mark Hindley]

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

Please unblock package elogind.

Version 241.1-1+debian1 of src:elogind has been in unstable for 11 days with no
regressions reported.

I am aware that the debdiff against testing (239.3+20190131-1+debian1) is
significantly larger than you would normally want at this stage in the release
cycle. However, I believe it is warranted and ask for your consideration.

The benefits of migration centre around this version of elogind providing ABI
compatibility between libelogind0 and libsystemd0 (see #923244). This means that
packages compiled against libsystemd-dev headers work correctly with either
libsystemd0 or libelogind0 runtime libraries. This is particularly important for
policykit-1 authorization of many desktop functions (particularly restart, halt,
suspend and for pkexec which is essential for synaptic) on non-systemd init
installations.

It is also worth pointing out that as elogind is derived from systemd which is
alrelady at version 241-2 in testing. Therefore, much of the contained upstream
code is already in included in buster.

In addition, at the moment this is rather a niche area into which few 'regular'
users will dip their toes; systemd is not currently uninstallable by APT once it
is PID 1 and so elogind systems can only be installed from scratch and do not
happen without considerable knowledge and care.

Many thanks. I look forward to your thoughts.

Mark

-- System Information:
Debian Release: 8.11
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-7-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_GB.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Bug#925490: encfs: [INTL:sv] Swedish debconf strings

[Jonatan Nyberg]

package: encfs
severity: wishlist
tags: patch l10n

Please consider to add this file to translation of debconf. It has
small fixes.

Regards,
Jonatan
# SOME DESCRIPTIVE TITLE.
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the PACKAGE package.
# FIRST AUTHOR , YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: encfs\n"
"Report-Msgid-Bugs-To: en...@packages.debian.org\n"
"POT-Creation-Date: 2014-10-07 19:56+0200\n"
"PO-Revision-Date: 2019-03-25 20:46+0100\n"
"Last-Translator: Jonatan Nyberg \n"
"Language: sv\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
"X-Generator: Poedit 2.2.1\n"
"Language-Team: \n"

#. Type: error
#. Description
#: ../encfs.templates:1001
msgid "Encfs security information"
msgstr "Encfs-säkerhetsinformation"

#. Type: error
#. Description
#: ../encfs.templates:1001
msgid "According to a security audit by Taylor Hornby (Defuse Security), the current implementation of Encfs is vulnerable or potentially vulnerable to multiple types of attacks. For example, an attacker with read/write access to encrypted data might lower the decryption complexity for subsequently encrypted data without this being noticed by a legitimate user, or might use timing analysis to deduce information."
msgstr "Enligt en säkerhetsrevision av Taylor Hornby (Defuse Security), är de nuvarande utföranden av Encfs sårbara eller potentiellt sårbara för flera olika typer av attacker. Till exempel kan en angripare med läs/skrivåtkomst till krypterad data sänka dekrypteringskomplexiteten för senare krypterad data utan att detta noteras av en legitim användare eller kan använda tidsanalys för att härleda information."

#. Type: error
#. Description
#: ../encfs.templates:1001
msgid "Until these issues are resolved, encfs should not be considered a safe home for sensitive data in scenarios where such attacks are possible."
msgstr "Tills dessa frågor är lösta, bör encfs inte betraktas som ett säkert hem för känslig data i situationer där sådana attacker är möjliga."

Bug#925488: unattended-upgrades: [INTL:sv] Swedish debconf strings

[Jonatan Nyberg]

package: unattended-upgrades
severity: wishlist
tags: patch l10n

Please consider to add this file to translation of debconf. It has
small fixes.

Regards,
Jonatan
# translation of unattended-upgrades.po to swedish
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the PACKAGE package.
#
# Martin Bagge , 2008.
msgid ""
msgstr ""
"Project-Id-Version: unattended-upgrades\n"
"Report-Msgid-Bugs-To: unattended-upgra...@packages.debian.org\n"
"POT-Creation-Date: 2017-12-12 23:02+0100\n"
"PO-Revision-Date: 2019-03-25 20:43+0100\n"
"Last-Translator: Jonatan Nyberg \n"
"Language-Team: swedish \n"
"Language: sv\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Poedit 2.2.1\n"

#. Type: boolean
#. Description
#: ../templates:2001
msgid "Automatically download and install stable updates?"
msgstr "Hämta och installera stabila uppdateringar automatiskt?"

#. Type: boolean
#. Description
#: ../templates:2001
msgid ""
"Applying updates on a frequent basis is an important part of keeping systems "
"secure. By default, updates need to be applied manually using package  "
"management tools. Alternatively, you can choose to have this system  "
"automatically download and install important updates."
msgstr ""
"Att tillämpa uppdateringar ofta är en viktig del av att hålla system säkra. "
"Som standard måste uppdateringar tillämpas manuellt med hjälp av "
"pakethanteringsverktyg. Alternativt kan du välja att detta system "
"automatiskt hämtar och installerar viktiga uppdateringar."

#~ msgid "Origins-Pattern that packages must match to be upgraded:"
#~ msgstr "Origins-Pattern som paket måste matcha för att bli uppgraderade:"

#~ msgid "Please specify a value for the unattended-upgrades Origins-Pattern."
#~ msgstr "Ange ett värde för unattended-upgrades Origins-Pattern."

#~ msgid ""
#~ "A package will be upgraded only if its metadata values match all the "
#~ "supplied keywords in the origin line."
#~ msgstr ""
#~ "Ett paket kommer att uppgraderas endast om dess metadatavärden matchar "
#~ "alla medföljande nyckelord i origin linjen."

Bug#925487: unattended-upgrades: [INTL:sv] Swedish debconf strings

[Jonatan Nyberg]

package: unattended-upgrades
severity: wishlist
tags: patch l10n

Please consider to add this file to translation of debconf. It has
small fixes.

Regards,
Jonatan
# Translation of diaspora-installer debconf template to Swedish
# Copyright (C) 2015 Martin Bagge 
# This file is distributed under the same license as the diaspora-installer package.
#
# Martin Bagge , 2015
msgid ""
msgstr ""
"Project-Id-Version: diaspora-installer\n"
"Report-Msgid-Bugs-To: diaspora-instal...@packages.debian.org\n"
"POT-Creation-Date: 2017-04-27 12:48+0530\n"
"PO-Revision-Date: 2019-03-25 20:35+0100\n"
"Last-Translator: Jonatan Nyberg \n"
"Language-Team: Swedish \n"
"Language: sv\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Poedit 2.2.1\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"

#. Type: string
#. Description
#: ../diaspora-common.templates:1001
msgid "Host name for this instance of Diaspora:"
msgstr "Värdnamn för denna instansen av Diaspora:"

#. Type: string
#. Description
#: ../diaspora-common.templates:1001
msgid ""
"Please choose the host name which should be used to access this instance of "
"Diaspora."
msgstr ""
"Var god ange värdnamnet som ska anges för att få tillgång till den här "
"instansen av Diaspora."

#. Type: string
#. Description
#: ../diaspora-common.templates:1001
msgid ""
"This should be the fully qualified name as seen from the Internet, with the "
"domain name that will be used to access the pod."
msgstr ""
"Detta ska vara det fullt kvalificerade namnet som syns på Internet, med "
"domännamnet som behövs för att få tillgång till podden."

#. Type: string
#. Description
#: ../diaspora-common.templates:1001
msgid ""
"If a reverse proxy is used, give the hostname that the proxy server responds "
"to."
msgstr ""
"Om en omvänd proxy används, ange värdnamnet som proxyservern svarar på."

#. Type: string
#. Description
#: ../diaspora-common.templates:1001
msgid ""
"This host name should not be modified after the initial setup because it is "
"hard-coded in the database."
msgstr ""
"Det här värdnamnet ska inte ändras efter den första installationen eftersom "
"det är hårdkodat i databasen."

#. Type: note
#. Description
#: ../diaspora-common.templates:2001
msgid "PostgreSQL application password"
msgstr "PostgreSQL-applikationslösenord"

#. Type: note
#. Description
#: ../diaspora-common.templates:2001
msgid ""
"You can leave the PostgreSQL application password blank, as the \"ident\" "
"authentication method is used, allowing the diaspora user on the system to "
"connect to the Diaspora database without a password."
msgstr ""
"Du kan lämna PostgreSQL-applikationslösenordet tomt, eftersom \"ident\" "
"autentiseringsmetoden används tillåts diaspora-användaren på systemet "
"ansluta till Diaspora-databasen utan lösenord."

#. Type: boolean
#. Description
#: ../diaspora-common.templates:3001
msgid "Enable https?"
msgstr "Aktivera https?"

#. Type: boolean
#. Description
#: ../diaspora-common.templates:3001
msgid ""
"Enabling https means that an SSL/TLS certificate is required to access this "
"Diaspora instance (as Nginx will be configured to respond only to https "
"requests). A self-signed certificate is enough for local testing (and can be "
"generated using, for instance, the package easy-rsa), but will not be "
"accepted for federation with other Diaspora pods."
msgstr ""
"Att aktivera https innebär att ett SSL-certifikat krävs för att få tillgång "
"till denna Diaspora-instans (eftersom Nginx konfigureras till att endast "
"svara på https-förfrågningar). Ett självsignerat certifikat är tillräckligt "
"för lokal prövning (och kan genereras med, till exempel, paketet easy-rsa), "
"men kommer inte att accepteras för federation med andra diaspora-poddar."

#. Type: boolean
#. Description
#: ../diaspora-common.templates:3001
msgid ""
"Some certificate authorities like Let's Encrypt (letsencrypt.org), StartSSL "
"(startssl.com) offer free SSL/TLS certificates that work with Diaspora; "
"however, certificates provided by CAcert will not work with Diaspora."
msgstr ""
"Vissa certifikatutfärdare som Let's Encrypt (letsencrypt.org), StartSSL "
"(startssl.com) erbjuder gratis SSL-certifikat som fungerar med Diaspora; "
"dock kommer inte certifikat från CAcert att fungera med Diaspora."

#. Type: boolean
#. Description
#: ../diaspora-common.templates:3001
msgid ""
"Nginx must be reloaded after the certificate and key files are made "
"available at /etc/diaspora/ssl. letsencrypt package may be used to automate "
"interaction with Let's Encrypt to obtain a certificate."
msgstr ""
"Nginx måste läsas om efter certifikatet och nyckelfilerna görs tillgängliga "
"i /etc/diaspora/ssl. letsencrypt-paket kan användas för att automatisera "
"interaktion med Let's Encrypt för att erhålla ett certifikat."

#. Type: boolean
#. Description
#: ../diaspora-common.templates:3001
msgid ""
"You can disable https if you want to access Diaspora only locally or 

Bug#924938: unblock: healpix-java/3.40-1

[Jonathan Wiltshire]

Control: tag -1 moreinfo

On Mon, Mar 25, 2019 at 08:28:25AM +0100, Ole Streicher wrote:
> as there is already the new version with the version number in unstable,
> would you agree to manage an upload via testing-proposed-updates? The
> upload would be really small, containing mainly a change of the build
> dependency and an additional entry for the JAVA classpath in d/rules.

Yes, but we need to see a debdiff first before uploading please. (And I
will have to remember how to make the wheels go round...)

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#925486: diaspora-installer: [INTL:sv] Swedish debconf strings

[Jonatan Nyberg]

package: diaspora-installer
severity: wishlist
tags: patch l10n

Please consider to add this file to translation of debconf. It has
small fixes.

Regards,
Jonatan
# Translation of diaspora-installer debconf template to Swedish
# Copyright (C) 2015 Martin Bagge 
# This file is distributed under the same license as the diaspora-installer package.
#
# Martin Bagge , 2015
msgid ""
msgstr ""
"Project-Id-Version: diaspora-installer\n"
"Report-Msgid-Bugs-To: diaspora-instal...@packages.debian.org\n"
"POT-Creation-Date: 2017-04-27 12:48+0530\n"
"PO-Revision-Date: 2019-03-25 20:35+0100\n"
"Last-Translator: Jonatan Nyberg \n"
"Language-Team: Swedish \n"
"Language: sv\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Poedit 2.2.1\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"

#. Type: string
#. Description
#: ../diaspora-common.templates:1001
msgid "Host name for this instance of Diaspora:"
msgstr "Värdnamn för denna instansen av Diaspora:"

#. Type: string
#. Description
#: ../diaspora-common.templates:1001
msgid ""
"Please choose the host name which should be used to access this instance of "
"Diaspora."
msgstr ""
"Var god ange värdnamnet som ska anges för att få tillgång till den här "
"instansen av Diaspora."

#. Type: string
#. Description
#: ../diaspora-common.templates:1001
msgid ""
"This should be the fully qualified name as seen from the Internet, with the "
"domain name that will be used to access the pod."
msgstr ""
"Detta ska vara det fullt kvalificerade namnet som syns på Internet, med "
"domännamnet som behövs för att få tillgång till podden."

#. Type: string
#. Description
#: ../diaspora-common.templates:1001
msgid ""
"If a reverse proxy is used, give the hostname that the proxy server responds "
"to."
msgstr ""
"Om en omvänd proxy används, ange värdnamnet som proxyservern svarar på."

#. Type: string
#. Description
#: ../diaspora-common.templates:1001
msgid ""
"This host name should not be modified after the initial setup because it is "
"hard-coded in the database."
msgstr ""
"Det här värdnamnet ska inte ändras efter den första installationen eftersom "
"det är hårdkodat i databasen."

#. Type: note
#. Description
#: ../diaspora-common.templates:2001
msgid "PostgreSQL application password"
msgstr "PostgreSQL-applikationslösenord"

#. Type: note
#. Description
#: ../diaspora-common.templates:2001
msgid ""
"You can leave the PostgreSQL application password blank, as the \"ident\" "
"authentication method is used, allowing the diaspora user on the system to "
"connect to the Diaspora database without a password."
msgstr ""
"Du kan lämna PostgreSQL-applikationslösenordet tomt, eftersom \"ident\" "
"autentiseringsmetoden används tillåts diaspora-användaren på systemet "
"ansluta till Diaspora-databasen utan lösenord."

#. Type: boolean
#. Description
#: ../diaspora-common.templates:3001
msgid "Enable https?"
msgstr "Aktivera https?"

#. Type: boolean
#. Description
#: ../diaspora-common.templates:3001
msgid ""
"Enabling https means that an SSL/TLS certificate is required to access this "
"Diaspora instance (as Nginx will be configured to respond only to https "
"requests). A self-signed certificate is enough for local testing (and can be "
"generated using, for instance, the package easy-rsa), but will not be "
"accepted for federation with other Diaspora pods."
msgstr ""
"Att aktivera https innebär att ett SSL-certifikat krävs för att få tillgång "
"till denna Diaspora-instans (eftersom Nginx konfigureras till att endast "
"svara på https-förfrågningar). Ett självsignerat certifikat är tillräckligt "
"för lokal prövning (och kan genereras med, till exempel, paketet easy-rsa), "
"men kommer inte att accepteras för federation med andra diaspora-poddar."

#. Type: boolean
#. Description
#: ../diaspora-common.templates:3001
msgid ""
"Some certificate authorities like Let's Encrypt (letsencrypt.org), StartSSL "
"(startssl.com) offer free SSL/TLS certificates that work with Diaspora; "
"however, certificates provided by CAcert will not work with Diaspora."
msgstr ""
"Vissa certifikatutfärdare som Let's Encrypt (letsencrypt.org), StartSSL "
"(startssl.com) erbjuder gratis SSL-certifikat som fungerar med Diaspora; "
"dock kommer inte certifikat från CAcert att fungera med Diaspora."

#. Type: boolean
#. Description
#: ../diaspora-common.templates:3001
msgid ""
"Nginx must be reloaded after the certificate and key files are made "
"available at /etc/diaspora/ssl. letsencrypt package may be used to automate "
"interaction with Let's Encrypt to obtain a certificate."
msgstr ""
"Nginx måste läsas om efter certifikatet och nyckelfilerna görs tillgängliga "
"i /etc/diaspora/ssl. letsencrypt-paket kan användas för att automatisera "
"interaktion med Let's Encrypt för att erhålla ett certifikat."

#. Type: boolean
#. Description
#: ../diaspora-common.templates:3001
msgid ""
"You can disable https if you want to access Diaspora only locally or you 

Bug#902493: apache2-bin: Event MPM listener thread may get blocked by SSL shutdowns

[Sven Hartge]

On 24.03.19 02:02, Sven Hartge wrote:

> So far, so good. I have your packages running on the main webmail server
> and the main web server for my university and so far everything is fine,
> while default packages and the test1 packages with mpm_event would
> normally start showing the symptoms after ~12 hours.

Still no problems here and both systems have seen some serious traffic
the last days, with the new semester starting next week and all.

Grüße,
Sven.



signature.asc
Description: OpenPGP digital signature

Bug#925485: libengine-pkcs11-openssl: Remove unneeded .la file

[Timur Irikovich Davletshin]

Package: libengine-pkcs11-openssl
Version: 0.4.9-4
Severity: normal

Remove /usr/lib/x86_64-linux-gnu/engines-1.1/pkcs11.la from package. Not needed
for normal operation.



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

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

Versions of packages libengine-pkcs11-openssl depends on:
ii  libc6  2.28-8
ii  libssl1.1  1.1.1b-1
ii  p11-kit0.23.15-2

libengine-pkcs11-openssl recommends no packages.

libengine-pkcs11-openssl suggests no packages.

Bug#915706: 9.6.0 DVD and XFCE CD for mipsel are actually netinst

[seamlik]

> How did you make this work with qemu on mipsel?

Mostly based on the instructions at 
.

1. Download the files at 
.
2. Download a Debian image and assume it's "image.iso".
2. Run `qemu-img create -f qcow2 hda.qcow2 5G`
3. Run `qemu-system-mipsel -m 2G -hda hda.qcow2 -kernel vmlinux-* -initrd 
initrd.gz -append "root=/dev/sda1" -M malta -cdrom image.iso -nographic`



signature.asc
Description: OpenPGP digital signature

Bug#554167: Updating Mawk in Debian

[Gert Hulselmans]

Hi Guillem,

I would appreciate it a lot if mawk is finally updated.

I am already waiting for a new version from 2011 (ubuntu bug report):
  https://bugs.launchpad.net/ubuntu/+source/mawk/+bug/716920

Since then I always replace the package manager version of mawk with the
last version available on https://invisible-island.net/mawk/mawk.html
(Desktop and servers).

I regularity write big awk scripts to process files of several
gigabytes and use mawk daily.

e.g.: https://github.com/ghuls/multigrep/blob/master/multigrep.sh

Thanks,

Gert

> Hi!
>
> On Fri, 2018-12-28 at 11:24:44 -0800, Dima Kogan wrote:
> > I just hit a bug in Debian's mawk that turned out to have been fixed
> > upstream long ago. Can we please update the mawk we ship to our users?
> > Can I help? What needs to happen?
>
> At this point I think the best course of action is to start a Package
> Salvaging process. This is a pseudo-essential package that has seen
> no single upload since 2012, and no major activity on its bug reports
> either. CCing other people that have showed interest in the past.
>
> Thanks,
> Guillem

Bug#925484: [plasma-workspace] /usr/start/startkde not exporting correct XDG_DATA_DIR

[Stephen Lyons]

Package: plasma-workspace
Version: 4:5.8.6-2.1+deb9u1
Severity: normal

--- Please enter the report below this line. ---
It appears that plasma-workspace is replicating the bug recorded as
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782285 for the package
from an old Debian version of kde-workspace-bin. It does seem to be an
upstream bug in that the relevant line 196 in
https://cgit.kde.org/plasma-workspace.git/tree/startkde/startkde.cmake
is not respecting the XDG standards for XDG_DATA_DIR and insisting on
putting its CMake build time variable KDE_INSTALL_FULL_DATAROOTDIR in
the first (highest priority) position in that list.

Unfortunately for Debian builds this happens to correspond to an
existing directory so the value used is:
"/usr/share:/usr/share:/usr/local/share"

whereas it should be - IMHO - work out to be:
"/usr/local/share:/usr/share"

Whether the KDE people are taking coding shortcuts and ONLY using the
first directory listed or correctly considering them all in order I
cannot say...

--- System information. ---
Architecture: Kernel:   Linux 4.9.0-8-amd64

Debian Release: 9.8
  500 stable  security.debian.org
  500 stable  ftp.uk.debian.org
  500 stable  apt.spideroak.com
  100 stretch-backports deb.debian.org
--- Package information. ---
Depends
(Version) | Installed
=-+-==
dbus-x11
 | 1.10.26-0+deb9u1
frameworkintegration
 | 5.28.0-1
gdb-minimal
 |  OR gdb
| 7.12-6
iso-codes
 | 3.75-1
kactivitymanagerd
 | 5.8.4-1
kde-cli-tools
 | 4:5.8.4-2
kded5
 | 5.28.0-1
kinit
 | 5.28.0-1
kio
 | 5.28.0-2
libkf5globalaccel-bin  (>=
5.7.0) | 5.28.0-1
libkf5service-bin
 | 5.28.0-1
milou
 | 4:5.8.4-1
plasma-framework
 | 5.28.0-2
plasma-integration
 | 5.8.6-1
qdbus-qt5
 | 5.7.1-1
qml-module-org-kde-draganddrop
 | 5.28.0-1
qml-module-org-kde-extensionplugin
 | 5.28.0-1
qml-module-org-kde-kcoreaddons
 | 5.28.0-1
qml-module-org-kde-kholidays
 | 16.04.2-1
qml-module-org-kde-kquickcontrols
 | 5.28.0-1
qml-module-org-kde-kquickcontrolsaddons
 | 5.28.0-1
qml-module-org-kde-kwindowsystem
 | 5.28.0-1
qml-module-org-kde-solid
 | 5.28.0-3
qml-module-qt-labs-folderlistmodel
 | 5.7.1-2+b2
qml-module-qtgraphicaleffects
 | 5.7.1~20161021-3
qml-module-qtqml-models2
 | 5.7.1-2+b2
qml-module-qtquick-controls
 | 5.7.1~20161021-2
qml-module-qtquick-dialogs
 | 5.7.1~20161021-2
qml-module-qtquick-layouts
 | 5.7.1-2+b2
qml-module-qtquick-window2
 | 5.7.1-2+b2
qml-module-qtquick2
 | 5.7.1-2+b2
qttools5-dev-tools  (>=
5.7~) | 5.7.1-1
udisks2
 | 2.1.8-1
x11-utils
 | 7.7+3+b1
x11-xserver-utils
 | 7.7+7+b1
kpackagetool5
 | 5.28.1-1
libc6   (>=
2.15) | 2.24-11+deb9u4
libcln6
 | 1.3.4-2+b1
libdbusmenu-qt5-2  (>=
0.6.6) | 0.9.3+16.04.20160218-1
libgcc1(>=
1:3.0) | 1:6.3.0-18+deb9u1
libgps22 (>=
3.3) | 3.16-4
libice6  (>=
1:1.0.0) | 2:1.0.9-2
libkf5activities5 (>=
4.96.0) | 5.28.0-1
libkf5auth5   (>=
4.96.0) | 5.28.0-2
libkf5baloo5   (>=
5.3.0+git20150512) | 5.28.0-2
libkf5bookmarks5  (>=
4.96.0) | 5.28.0-1
libkf5calendarevents5
 | 5.28.0-1
libkf5completion5 (>=
4.97.0) | 5.28.0-1
libkf5configcore5 (>=
5.24.0) | 5.28.0-2
libkf5configgui5  (>=
4.97.0) | 5.28.0-2
libkf5configwidgets5  (>=
4.96.0) | 5.28.0-2
libkf5coreaddons5 (>=
5.20.0) | 5.28.0-2
libkf5crash5  (>=
4.96.0) | 5.28.0-1
libkf5dbusaddons5 (>=
4.99.0) | 5.28.0-1
libkf5declarative5(>=
5.12.0) | 5.28.0-1
libkf5globalaccel5(>=
5.10.0) | 5.28.0-1
libkf5guiaddons5  (>=
4.96.0) | 5.28.0-1
libkf5holidays5  (>=
15.12.0) | 16.04.2-1
libkf5i18n5   (>=
4.97.0) | 5.28.0-2
libkf5iconthemes5 (>=
5.25.0) | 5.28.0-2
libkf5idletime5   

Bug#925222: hplip: hp-plugin doesn't work (hp-diagnose_plugin[4665]: error: Failed to install Plug-in)

[Brian Potkin]

On Thu 21 Mar 2019 at 13:34:23 +0100, Mari Donkers wrote:

> The hplip/stable and hpgui/stable packages do *not* have the problem.
> But the hplip/testing and hpgui/testing packages do have the problem.
> The problem is as follows: when trying to download and install the
> required printer plugin (for HP m1217 printer) it does download the
> plugin, but fails to install it. It asks for the root password, which
> I supply correctly but then reports an error. As mentioned before this
> is only for the packages in testing, the stable packages work fine. So
> I have downgraded the packages to stable as a workaround (the
> automatically added information is for the working stable packages).
> The error is easily reproduced. Just run hp-plugin (or hp-setup).

Thank you for your report, Mari.

I have used 'hp-plugin -i' a number of times in the past few months
with hplip 3.18.12 and retested it today. It downloads the plugin,
presents a licence to agree to and asks for the root password and,
on giving it, installs the plugin files. Is there anything more you
could suggest for me to do to get the behaviour you describe?

If it is a matter of wanting the testing/unstable version, you could
see what

  https://wiki.debian.org/QuickPrintQueuesCUPS#mfd

does for you.

Regards,

Brian.

Bug#925141: Should rdma-core be a dependency of ibverbs-providers or libverb1

[Jason Gunthorpe]

On Thu, Mar 21, 2019 at 01:26:04PM -0500, Brian Smith wrote:
> On Thu, Mar 21, 2019 at 3:51 AM Christian Ehrhardt
>  wrote:
> >
> > > ibverbs is provided by rdma-core project.
> > > Is it a separate package in your case?
> >
> > No it is part of the same src package.
> >
> > > Yes, you need libmlx4, libmlx5 and libibverbs.
> > > It is described in the doc:
> > > http://doc.dpdk.org/guides/nics/mlx5.html#prerequisites
> >
> > Well that is the problem, we fulfill that prereq already.
> > libmlx4, libmlx5 and libibverbs are installed by dependencies already
> > and thought all the time that would be good enough.
> >
> > But we got told that we also need the package rdma-core [1] itself to
> > be installed to be useful.
> > That was a discussion with the subject "Please help us to verify DPDK
> > 17.11.5 for Ubuntu 18.04/18.10" with Mellanox test people.
> > Fortunately I keep you on CC on those - so maybe you can find it
> > somewhere in your inbox and contact the other Mellanox people on that
> > thread.
> > After that you might help to translate their request into our terms please?
> >
> > The question is:
> > a) what exactly is (binary package) rdma-core [1] needed for in that 
> > scenario
> > b) if (a) would be generally true we wondered why it had to be a dep
> > of the DPDK packages and not of e.g. libibverbs1 itself
> > That is why we opened this bug for discussions
> >
> > [1]: https://packages.debian.org/sid/rdma-core
> >
> 
> rdma-core configures modprobe for ib/rdma modules, installs some
> helper daemons and installs some udev rules. It certainly makes
> administration of the server an easier task, but it isn't *required*
> when configuring a Debian server for rdma and user-space ibverbs.

I didn't think it is required for mlx5 as the ethernet driver
autoloads the rdma modules itself..

At least, I wouldn't make rdma-core a hard dependency of dpdk.. At
worst that should be in libibverbs, as you say.

Jason

Bug#925483: tilda: does not start (segfault)

[Guenter Grodotzki]

Package: tilda
Version: 1.4.1-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

   * What led up to the situation?

starting tilda (either via menu or terminal)

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

was not able to get it to run

   * What was the outcome of this action?

"Segmentation fault"

   * What outcome did you expect instead?

Running application (tilda)


Upstream bug report:
https://github.com/lanoxx/tilda/issues/360#issuecomment-476309441


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

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

Versions of packages tilda depends on:
ii  libc6   2.28-8
ii  libconfuse2 3.2.2+dfsg-1
ii  libgdk-pixbuf2.0-0  2.38.1+dfsg-1
ii  libglib2.0-02.58.3-1
ii  libgtk-3-0  3.24.5-1
ii  libpango-1.0-0  1.42.4-6
ii  libvte-2.91-0   0.54.2-2
ii  libx11-62:1.6.7-1

tilda recommends no packages.

tilda suggests no packages.

-- no debconf information

*** /home/guenter/gdp-tilda.txt
~  gdb tilda
GNU gdb (Debian 8.2.1-2) 8.2.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from tilda...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/tilda
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Detaching after fork from child process 3404]
[New Thread 0x7427b700 (LWP 3406)]
[New Thread 0x73a7a700 (LWP 3407)]
[New Thread 0x73247700 (LWP 3408)]
[New Thread 0x72a3f700 (LWP 3409)]
[New Thread 0x71f58700 (LWP 3411)]
[New Thread 0x7170a700 (LWP 3412)]
[New Thread 0x70f09700 (LWP 3413)]
[New Thread 0x7fffdbfff700 (LWP 3414)]
[New Thread 0x7fffdb7fe700 (LWP 3415)]
[New Thread 0x7fffdaffd700 (LWP 3416)]
[New Thread 0x7fffda7fc700 (LWP 3417)]
[Detaching after fork from child process 3418]

Thread 1 "tilda" received signal SIGSEGV, Segmentation fault.

Bug#925475: clamav-freshclam.service is "inactive (dead)" after logrotate postrotate script execution

[Adam D. Barratt]

On 2019-03-25 15:39, Nils Fahldieck - Profihost AG wrote:

libc6 Version: 2.24-11+deb9u4
systemd Version: 232-25+deb9u9
Debian Version: Debian GNU/Linux 9 (stretch)

The `postrotate` script in `/etc/logrotate.d/clamav-freshclam` executes
this code if systemd is used:

$ cat /etc/logrotate.d/clamav-freshclam
 postrotate
 if [ -d /run/systemd/system ]; then
 systemctl -q is-active clamav-freshclam && systemctl kill
--signal=SIGHUP clamav-freshclam || true

Whenever logrotate rotates freshclam's logfile, the service is inactive
(dead) afterwards.

Reproducer:

$ systemctl is-active clamav-freshclam
active
$ systemctl -q is-active clamav-freshclam && systemctl kill
--signal=SIGHUP clamav-freshclam || true
$ systemctl is-active clamav-freshclam
inactive
$ systemctl status clamav-freshclam.service
● clamav-freshclam.service - ClamAV virus database updater
   Loaded: loaded (/lib/systemd/system/clamav-freshclam.service;
enabled; vendor preset: enabled)
  Drop-In: /etc/systemd/system/clamav-freshclam.service.d
   └─limits.conf
   Active: inactive (dead) since Mon 2019-03-25 16:28:25 CET; 2s ago
 Docs: man:freshclam(1)


fwiw, I can't reproduce this.

clamav-freshclam 0.100.2+dfsg-0+deb9u1
libc6 2.24-11+deb9u4
systemd 232-25+deb9u9

● clamav-freshclam.service - ClamAV virus database updater
   Loaded: loaded (/lib/systemd/system/clamav-freshclam.service; 
enabled; vendor preset: enabled)
   Active: active (running) since Sun 2019-03-10 19:07:03 GMT; 2 weeks 0 
days ago

..

-rw-r- 1 clamav adm   4754 Mar 11 06:25 
/var/log/clamav/freshclam.log.3.gz
-rw-r- 1 clamav adm   3544 Mar 17 06:25 
/var/log/clamav/freshclam.log.2.gz
-rw-r- 1 clamav adm 312142 Mar 24 06:25 
/var/log/clamav/freshclam.log.1
-rw-r- 1 clamav adm  65671 Mar 25 17:25 
/var/log/clamav/freshclam.log


also:

# systemctl is-active clamav-freshclam
active
# systemctl -q is-active clamav-freshclam && systemctl kill 
--signal=SIGHUP clamav-freshclam || true

# systemctl is-active clamav-freshclam
active

Aahhh... My guess would be that this is due to your local 
customisation:


 Drop-In: /etc/systemd/system/clamav-freshclam.service.d
   └─limits.conf
...
  Process: 15231 ExecStart=/usr/bin/cpulimit -f -l 5 --
/usr/bin/freshclam -d --foreground=true (code=killed, signal=HUP)

which means that the HUP will be being sent to cpulimit, not to 
freshclam.


I'm not a clamav maintainer, but I'd be inclined at this point to say 
that this is not a problem with the package, and "you get to keep the 
pieces", I'm afraid. From a quick bit of research, I would suggest that 
you want to be using systemd's built-in 
https://www.freedesktop.org/software/systemd/man/systemd.resource-control.html#CPUQuota= 
, which would entirely avoid this issue.


Regards,

Adam

Bug#925482: stretch-pu: package firmware-nonfree/20161130-5

[Ben Hutchings]

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

This update fixes CVE-2018-5383 in firmware for some Bluetooth
adapters.  The security team already triaged this as not requiring a
DSA.

Ben.

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

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

Bug#925481: ITA: qcomicbook -- viewer for comic books

[Fábio Junior]

Package: qcomicbook
Retitle: ITA

Fábio Junior
Linux user #464296
+55 11 97314-6368
 .~.
/ v \
  / (   ) \
   ^^-^^

Bug#925473: Bug#925454: RM: tomcat8 -- ROM; Replaced by tomcat9

[Thorsten Glaser]

On Mon, 25 Mar 2019, Emmanuel Bourg wrote:

> When it's ready please let me review the update before uploading.

OK.

> Not changing the maintainer scripts nor the configuration files in the
> process would be nice.

I agree; at the current point in time, this should be least-intrusive.

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

*

**!!! NEU !!!** Mit der **tarent Academy** bieten wir ab sofort auch Trainings
und Schulungen in den Bereichen Softwareentwicklung, Agiles Arbeiten und
Zukunftstechnologien an. Besuchen Sie uns
auf [www.tarent.de/academy](http://www.tarent.de/academy). Wir freuen uns auf
Ihren Kontakt.

*

Bug#925454: RM: tomcat8 -- ROM; Replaced by tomcat9

[Thorsten Glaser]

On Mon, 25 Mar 2019, Emmanuel Bourg wrote:

> We've got two serious security issues in the Tomcat init script in the

You told me this. I replied by:

• I’m active and willing to maintain it
• if I don’t realise there’s a bug you can ping me
• if even that fails, you can *still* remove it

You never replied to these.

> past. I'm not a big fan of systemd but this convinced me that a 40 lines
> declarative service file was much more maintainable than a 300 lines
> init script, and I'm unlikely to maintain one anymore.

Perhaps, but thankfully Policy prescribes the existence of one.
I’ll provide one and team-upload. You need not personally maintain it,
just don’t break it. That’s what a team is for.

> systemd brought other important benefits for the tomcat9 package and I
> don't want to go back on these features.

You don’t need to. The sysvinit script is not optional, but
systemd users need not use it.

We already realised (in that thread on d-java) that they will
most likely behave slightly differently, but that’s okay. (It
can be documented.)

> > To recall the justification I posted to the list that were,
> > IIRC, never replied:
> 
> I made the suggestion to package the init script in a separate package
> under your control, but you didn't follow up.

I’ve replied saying that such tiny packages aren’t liked by
ftpmasters and mirror admins.

Anyway, Policy solved the issue for us, the initscript will
be in the main tomcat9 package where it belongs. (Do note that
the option of removing it (from above) is no longer pertinent,
as one is required if a startup script for another init system
is present. However, I’ll do my best, and even if that fails,
I know at least one other DD at my employer’s who’s capable
enough to maintain complex shell scripts and fixing RC bugs.)

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

*

**!!! NEU !!!** Mit der **tarent Academy** bieten wir ab sofort auch Trainings
und Schulungen in den Bereichen Softwareentwicklung, Agiles Arbeiten und
Zukunftstechnologien an. Besuchen Sie uns
auf [www.tarent.de/academy](http://www.tarent.de/academy). Wir freuen uns auf
Ihren Kontakt.

*

Bug#925454: RM: tomcat8 -- ROM; Replaced by tomcat9

[Emmanuel Bourg]

Le 25/03/2019 à 16:33, Thorsten Glaser a écrit :

> Oh, goodie. I had not realised this is, as the init system diversity GR
> did not pass, still a “must”.
> 
> In this case it’s easy… I’m cloning this as RC bug against tomcat9 and
> will work within the next couple of days on fixing this by providing a
> proper init script, as team upload / RC squash.

When it's ready please let me review the update before uploading. Not
changing the maintainer scripts nor the configuration files in the
process would be nice.

Emmanuel Bourg

Bug#925454: RM: tomcat8 -- ROM; Replaced by tomcat9

[Emmanuel Bourg]

Le 25/03/2019 à 16:09, Thorsten Glaser a écrit :

> But somehow, I think the “let’s add a sensible init script to
> tomcat9 now” is the better solution for everyone. Emmanuel, can
> you please reconsider your rejection? Then we can ask SRM if
> they’d allow it.

We've got two serious security issues in the Tomcat init script in the
past. I'm not a big fan of systemd but this convinced me that a 40 lines
declarative service file was much more maintainable than a 300 lines
init script, and I'm unlikely to maintain one anymore.

systemd brought other important benefits for the tomcat9 package and I
don't want to go back on these features.


> To recall the justification I posted to the list that were,
> IIRC, never replied:

I made the suggestion to package the init script in a separate package
under your control, but you didn't follow up.

Emmanuel Bourg

Bug#925480: mirrors

[Dmitry]

Package: mirrors
Severity: normal

Dear Maintainer,

Some packages has gone from jessie-backports package index. I have found at 
least rsyslog, rsyslog-kafka, prometheus-node-exporter are gone.

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

Kernel: Linux 4.9.0-8-amd64 (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Bug#925479: unblock: debian-reference/2.76

[Osamu Aoki]

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

Please unblock package debian-reference

(explain the reason for the unblock here)
debian-reference (2.76) unstable; urgency=medium

  * Complete translation for de, it, ja, pt, and zh-cn.
Closes: #924863
  * Update filepath to comply with doc-base CGI script restrictions.
Closes: #900360, #924686
  * Add lintian override for missing-depends-on-sensible-utils,
  * Update package and popcon data entity.
  * Ready for buster release by setting buster as stable release.

 -- Osamu Aoki   Thu, 21 Mar 2019 23:23:38 +0900

By uploading this to unstable, www.debian.org pages of this document
start stating buster=stable.  :-)

(include/attach the debdiff against the package in testing)

This package build in 2 steps.
1. manual build with downloading popcondata etc to make debian-reference.raw.xml
   asciidoc/* used and *.ent updated
2. normal package build with package build script with po for
translation.

Thus following directory is excluded for debdiff for readability
  po:   excluded since trasnslation diff
  asciidoc: excluded since this is used to create debian-reference.raw.xml
  *.ent:excluded since update of pocon is not interesting diff

  (There are some diffs due to wrap-and-sort)

 $ debdiff --exclude po --exclude *.ent --exclude asciidoc 
debian-reference_2.75.dsc debian-reference_2.76.dsc >debian-reference_2.76.diff
diff -Nru --exclude po --exclude '*.ent' --exclude asciidoc 
debian-reference-2.75/bin/replace_package 
debian-reference-2.76/bin/replace_package
--- debian-reference-2.75/bin/replace_package   2018-07-02 00:49:45.0 
+0900
+++ debian-reference-2.76/bin/replace_package   2019-03-21 23:23:38.0 
+0900
@@ -1,5 +1,5 @@
 # This is autogenerated by Makefile.  Update this with "make rawxml"
 s/@emacs@/emacs25/g
-s/@libpoppler@/libpoppler74/g
+s/@libpoppler@/libpoppler82/g
 s/@libgstreamer@/libgstreamer1.0-0/g
 s/@libphonon@/libphonon4/g
diff -Nru --exclude po --exclude '*.ent' --exclude asciidoc 
debian-reference-2.75/debian/all.doc-base-in 
debian-reference-2.76/debian/all.doc-base-in
--- debian-reference-2.75/debian/all.doc-base-in2017-09-19 
20:53:04.0 +0900
+++ debian-reference-2.76/debian/all.doc-base-in2019-03-21 
23:23:38.0 +0900
@@ -6,9 +6,12 @@
 Section: Debian
 
 Format: text
-Files: /usr/share/debian-reference/debian-reference.@@.txt.gz
+Files: /usr/share/doc/debian-reference-@@/docs/debian-reference.@@.txt.gz
+
+Format: PDF
+Files: /usr/share/doc/debian-reference-@@/docs/debian-reference.@@.pdf
 
 Format: HTML
-Index: /usr/share/debian-reference/index.@@.html
-Files: /usr/share/debian-reference/*.@@.html
+Index: /usr/share/doc/debian-reference-@@/docs/index.@@.html
+Files: /usr/share/doc/debian-reference-@@/docs/*.@@.html
 
diff -Nru --exclude po --exclude '*.ent' --exclude asciidoc 
debian-reference-2.75/debian/all.lintian-overrides-in 
debian-reference-2.76/debian/all.lintian-overrides-in
--- debian-reference-2.75/debian/all.lintian-overrides-in   1970-01-01 
09:00:00.0 +0900
+++ debian-reference-2.76/debian/all.lintian-overrides-in   2019-03-21 
23:23:38.0 +0900
@@ -0,0 +1,4 @@
+debian-reference-@@: missing-depends-on-sensible-utils 
usr/share/debian-reference/pr01.@@.html
+debian-reference-@@: missing-depends-on-sensible-utils 
usr/share/debian-reference/ch02.@@.html
+debian-reference-@@: missing-depends-on-sensible-utils 
usr/share/debian-reference/ch09.@@.html
+
diff -Nru --exclude po --exclude '*.ent' --exclude asciidoc 
debian-reference-2.75/debian/changelog debian-reference-2.76/debian/changelog
--- debian-reference-2.75/debian/changelog  2019-03-10 22:27:19.0 
+0900
+++ debian-reference-2.76/debian/changelog  2019-03-21 23:23:38.0 
+0900
@@ -1,3 +1,15 @@
+debian-reference (2.76) unstable; urgency=medium
+
+  * Complete translation for de, it, ja, pt, and zh-cn.
+Closes: #924863
+  * Update filepath to comply with doc-base CGI script restrictions.
+Closes: #900360, #924686
+  * Add lintian override for missing-depends-on-sensible-utils,
+  * Update package and popcon data entity.
+  * Ready for buster release by setting buster as stable release.
+
+ -- Osamu Aoki   Thu, 21 Mar 2019 23:23:38 +0900
+
 debian-reference (2.75) unstable; urgency=medium
 
   [ Holger Wansing ]
@@ -5,7 +17,7 @@
 
   [ Osamu Aoki ]
   * Fixed broken symlink (in 2.74/unstable). Closes: #910153
-  * Fixed DEB_BUILD_OPTIONS.  Closes: #907779 
+  * Fixed DEB_BUILD_OPTIONS.  Closes: #907779
 
  -- Osamu Aoki   Sun, 10 Mar 2019 22:27:19 +0900
 
diff -Nru --exclude po --exclude '*.ent' --exclude asciidoc 
debian-reference-2.75/debian/control debian-reference-2.76/debian/control
--- debian-reference-2.75/debian/control2018-07-10 00:43:58.0 
+0900
+++ debian-reference-2.76/debian/control2019-03-21 23:23:38.0 
+0900
@@ -6,10 +6,10 @@
 

Bug#925316: TypeError: type.__new__(metaclass) is not safe

[Tobias Hansen]

Hi,

thanks for the bug report. Please do a aptitude full-upgrade, just looking at a 
few of the versions of your python packages revealed outdated packages. I can't 
reproduce this and we can't track every singled versioned dependency of 
sagemath. It has too many dependencies for that. The only supported scenario is 
that your packages are up-to-date from unstable or testing.

If we find out which package caused this, we could maybe add a versioned 
dependency for this case in the future.

Best,
Tobias

On 3/23/19 12:18 AM, Kingsley G. Morse Jr. wrote:
> Package: sagemath
> Version: 8.6-6
> Severity: important
>
> Dear Maintainer,
>
> Thank you for maintaining sage.
>
> I look forward to using it.
>
> The main reason I'm writing is to report a bug.
>
> I typed...
>
> root$ aptitude install sagemath
>
> on a computer with piecemeal updates from Debian's
> unstable distribution, and then
>
> kingsley$ sage
>
> and got  "kaBOOM!".
>
> The crash traceback is attached.
>
> It reminds me of
>
> https://trac.sagemath.org/ticket/18503
>
> So,
> Kingsley
>

Bug#925250: unblock: cron/3.0pl1-133

[Christian Kastner]

Hi,

brief update: Since the upload, one new bug has been reported for one of
the security fixes, which had been cherry-picked for jessie-security.
See below.

Otherwise, -133 has not triggered any new bug reports so far.

On 2019-03-21 20:19:01 +0100 Christian Kastner wrote:> I'd like to
request an unblock for cron/3.0pl1-133. The notable changes
> are smallish, and mainly concern security fixes that have been assigned
> CVE-2019-9704, -9705, and -9706 in the meantime. One of these fixes
> (limiting crontabs to 1000 lines) required a debian/NEWS entry.

Contrary to my expectations, it appears that users with crontabs longer
than 1000 lines do exist. In #925276, a user reported hitting this limit
with a programmatically generated crontab.

I would like to fix this by making the limit configurable, that is:
defaulting to 1.000 lines, but allowing a different limit in
/etc/default/cron, with a corresponding update to debian/NEWS.

However, I'd appreciate your feedback on the -133 changes, before adding
new ones on top of that.

> With regards to the security fixes, uploads for jessie and stretch are
> being or have been prepared.

FYI, cron 3.0pl1+deb8u2 was uploaded to jessie-security on 2019-03-21.

Regards,
Christian

Bug#925478: restart action breaks with systemd (Again)

[PICCORO McKAY Lenz]

Package: lighttpd
Version: 1.4.35-4+deb8u1
Version: 1.4.53-3
Severity: grave


The systemd (again) seems have problems iwth lighttpd..
when i try to restart the service aftyer some time.. service does not start
and a paralele service are in backgound..

that problem does not happen with wheeze , neither happen in Devuan
that used sysv-init

until that days, systemd seems are mor a pain in the ass rather a solution!

root@ip-10-101-2-11:/etc/# service lighttpd status
● lighttpd.service - Lighttpd Daemon
   Loaded: loaded (/lib/systemd/system/lighttpd.service; enabled)
   Active: failed (Result: exit-code) since Mon 2019-03-25 16:08:05 UTC; 4s ago
  Process: 3019 ExecStart=/usr/sbin/lighttpd -D -f
/etc/lighttpd/lighttpd.conf (code=exited, status=255)
  Process: 3011 ExecStartPre=/usr/sbin/lighttpd -t -f
/etc/lighttpd/lighttpd.conf (code=exited, status=0/SUCCESS)
 Main PID: 3019 (code=exited, status=255)

Mar 25 16:08:05 ip-10-101-2-11 lighttpd[3011]: Syntax OK
Mar 25 16:08:05 ip-10-101-2-11 systemd[1]: Started Lighttpd Daemon.
Mar 25 16:08:05 ip-10-101-2-11 lighttpd[3019]: 2019-03-25 16:08:05:
(network.c.409) can't bind to port:  80 Addre...n use
Mar 25 16:08:05 ip-10-101-2-11 systemd[1]: lighttpd.service: main
process exited, code=exited, status=255/n/a
Mar 25 16:08:05 ip-10-101-2-11 systemd[1]: Unit lighttpd.service
entered failed state.
Hint: Some lines were ellipsized, use -l to show in full.
root@ip-10-101-2-11:/etc/# ps -lxa | grep http
0 0  3032 32390  20   0  12728  2188 -  S+   pts/1  0:00
grep --color=auto http
133 20456 1  20   0  97324  2284 -  S?  0:17
/usr/sbin/lighttpd -f /etc/lighttpd/lighttpd.conf
root@ip-10-101-2-11:/etc/# kill -9 20456
root@ip-10-101-2-11:/etc/# service lighttpd start
root@ip-10-101-2-11:/etc/# service lighttpd status
● lighttpd.service - Lighttpd Daemon
   Loaded: loaded (/lib/systemd/system/lighttpd.service; enabled)
   Active: active (running) since Mon 2019-03-25 16:08:52 UTC; 11s ago
  Process: 3050 ExecStartPre=/usr/sbin/lighttpd -t -f
/etc/lighttpd/lighttpd.conf (code=exited, status=0/SUCCESS)
 Main PID: 3058 (lighttpd)
   CGroup: /system.slice/lighttpd.service
   └─3058 /usr/sbin/lighttpd -D -f /etc/lighttpd/lighttpd.conf

Mar 25 16:08:52 ip-10-101-2-11 lighttpd[3050]: Syntax OK
Mar 25 16:08:52 ip-10-101-2-11 systemd[1]: Started Lighttpd Daemon.
Mar 25 16:08:58 ip-10-101-2-11 systemd[1]: Started Lighttpd Daemon.
root@ip-10-101-2-11:/etc/#





Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com

Bug#925477: src:lirc: Uncoordinated removal of transitional packages during freeze breaks other packages

[Scott Kitterman]

Package: src:lirc
Version: 0.10.1-5.1
Severity: grave
Justification: renders package unusable

Removal of the obselete packages dropped in the most recent upload is
blocked by:

  - broken Build-Depends:
audacious-plugins: liblircclient-dev
bino: liblircclient-dev
geeqie: liblircclient-dev
gkrellm-radio: liblircclient-dev
gmpc-plugins: liblircclient-dev
kradio4: liblircclient-dev
lcdproc: liblircclient-dev
libirman: liblircclient-dev (>= 0.9.4)
lxmms2: liblircclient-dev
ncmpc: liblircclient-dev
pulseaudio: liblircclient-dev
pylirc: liblircclient-dev
rhythmbox: liblircclient-dev
rosegarden: liblircclient-dev
squeezelite: liblircclient-dev
totem: liblircclient-dev (>= 0.6.6)
xawtv: liblircclient-dev
xine-lib-1.2: liblircclient-dev
xine-ui: liblircclient-dev
zapping: liblircclient-dev

Breaking 20 other packages during freeze does not seem to be the best
approach.  I would suggest putting the transitional packages back until
Buster is released and then remove them again, after coordination with the
maintainers of the affected packages.

Scott K

Bug#925476: unblock: dwww/1.13.4+nmu3

[Osamu Aoki]

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

Please unblock package dwww

(explain the reason for the unblock here)
This is updated package to comply with RM question for +nmu1 upload
filed as #925028 (Closing it with this request with 925028-d...@bugs.debian.org)

Jonathan Wiltshire  said:
> This promotion of packages from Suggests to Recommends is not mentioned in
> the changelog. What is its purpose?

I took no response from my reply is NOT GOOD.  So I reverted
undocumented changes here.  No more dependency changes.

(include/attach the debdiff against the package in testing)

diff -Nru dwww-1.13.4/debian/changelog dwww-1.13.4+nmu3/debian/changelog
--- dwww-1.13.4/debian/changelog2017-06-21 05:13:20.0 +0900
+++ dwww-1.13.4+nmu3/debian/changelog   2019-03-26 00:39:01.0 +0900
@@ -1,3 +1,31 @@
+dwww (1.13.4+nmu3) UNRELEASED; urgency=medium
+
+  * NMU
+  * Really revert dependency changes to 1.13.4.
+
+ -- Osamu Aoki   Tue, 26 Mar 2019 00:39:01 +0900
+
+dwww (1.13.4+nmu2) unstable; urgency=medium
+
+  * NMU
+  * Revert dependency changes to 1.13.4. 
+
+ -- Osamu Aoki   Mon, 25 Mar 2019 23:36:13 +0900
+
+dwww (1.13.4+nmu1) unstable; urgency=medium
+
+  * NMU
+
+  [ Ondřej Nový ]
+  * d/control: Set Vcs-* to salsa.debian.org .  Closes: #924709
+
+  [ Osamu Aoki ]
+  * Document properly to enable CGI script.  Closes: #781987, #822323
+  * Apply patch from Daniel Reichelt to make sleep time after each file
+configurable for dwww-index++.  Closes: #881189
+
+ -- Osamu Aoki   Sun, 17 Mar 2019 00:01:51 +0900
+
 dwww (1.13.4) unstable; urgency=medium
 
   * dwww-txt2html.c:
diff -Nru dwww-1.13.4/debian/control dwww-1.13.4+nmu3/debian/control
--- dwww-1.13.4/debian/control  2017-06-21 05:13:20.0 +0900
+++ dwww-1.13.4+nmu3/debian/control 2019-03-25 23:47:03.0 +0900
@@ -5,8 +5,8 @@
 Build-Depends: debhelper (>= 10), dh-apache2, lsb-release, publib-dev
 Build-Conflicts: apache2-dev (<< 2.4.4-6~)
 Standards-Version: 4.0.0
-Vcs-Git: https://anonscm.debian.org/git/users/robert/dwww.git
-Vcs-Browser: https://anonscm.debian.org/cgit/users/robert/dwww.git
+Vcs-Git: https://salsa.debian.org/debian/dwww.git
+Vcs-Browser: https://salsa.debian.org/debian/dwww
 
 Package: dwww
 Architecture: any
@@ -27,6 +27,16 @@
 Suggests: doc-debian, dpkg-www, links | www-browser
 Description: Read all on-line documentation with a WWW browser
  All installed on-line documentation will be served via a local HTTP
- server. When possible, dwww converts the documentation to HTML.
- You need to install both a CGI-capable HTTP server and a WWW
- browser to read the documentation.
+ server at http://localhost/dwww/. This package runs cron scripts to
+ convert available resources to the HTML pages.  Executing the dwww
+ command starts a sensible WWW browser locally to access them.
+ .
+ You need to install a CGI-capable HTTP server and enable its CGI script
+ capability manually (CGI may be disabled by default for the security
+ consideration).  For apache2, do something along the following:
+ .
+  $ sudo a2enmod cgid
+  $ sudo systemctl restart apache2
+ .
+ The default for the HTTP/CGI access is limited to the local user for
+ the security consideration. 
diff -Nru dwww-1.13.4/man/dwww.7 dwww-1.13.4+nmu3/man/dwww.7
--- dwww-1.13.4/man/dwww.7  2017-06-21 05:13:20.0 +0900
+++ dwww-1.13.4+nmu3/man/dwww.7 2019-03-16 16:14:00.0 +0900
@@ -230,6 +230,14 @@
 .BR dwww\-index++ (8)
 will generate index of registered documentation.
 .\"
+.IP DWWW_INDEX_FULL_SLEEP_TIME
+In order to not impede regular server operation,
+.BR dwww\-index++ (8)
+sleeps for the specified amount of time (in seconds) before feeding the next 
file path to index to
+.BR index++ (1).
+The default value is
+.BR 0.15 .
+.\"
 .IP DWWW_INDEX_FULL_TIME_INTERVAL
 Specifies how often (in days) 
 .BR dwww\-index++ (8)
diff -Nru dwww-1.13.4/perl/Debian/Dwww/ConfigFile.pm 
dwww-1.13.4+nmu3/perl/Debian/Dwww/ConfigFile.pm
--- dwww-1.13.4/perl/Debian/Dwww/ConfigFile.pm  2017-06-21 05:13:20.0 
+0900
+++ dwww-1.13.4+nmu3/perl/Debian/Dwww/ConfigFile.pm 2019-03-16 
16:14:00.0 +0900
@@ -96,6 +96,11 @@
 defval => 28,
 descr  => 'How often (in days) dwww-index++(8) will generate full 
index of documentation.'
 },
+'DWWW_INDEX_FULL_SLEEP_TIME' => {
+sort   => 50,
+defval => 0.15,
+descr  => 'How long (in seconds) dwww-index++ should sleep after 
each file in order to not impact regular server operation.'
+},
 'DWWW_INDEX_INCREMENTAL_TIME_INTERVAL'  => {
 sort   => 50,
 defval => 7,
diff -Nru dwww-1.13.4/perl/Debian/Dwww/Initialize.pm 
dwww-1.13.4+nmu3/perl/Debian/Dwww/Initialize.pm
--- dwww-1.13.4/perl/Debian/Dwww/Initialize.pm  2017-06-21 05:13:20.0 
+0900
+++ dwww-1.13.4+nmu3/perl/Debian/Dwww/Initialize.pm 2019-03-16 

Bug#925475: clamav-freshclam.service is "inactive (dead)" after logrotate postrotate script execution

[Nils Fahldieck - Profihost AG]

Package: clamav-freshclam
Version: 0.100.2+dfsg-0+deb9u1
Severity: important

libc6 Version: 2.24-11+deb9u4
systemd Version: 232-25+deb9u9
Debian Version: Debian GNU/Linux 9 (stretch)

The `postrotate` script in `/etc/logrotate.d/clamav-freshclam` executes
this code if systemd is used:

$ cat /etc/logrotate.d/clamav-freshclam
 postrotate
 if [ -d /run/systemd/system ]; then
 systemctl -q is-active clamav-freshclam && systemctl kill
--signal=SIGHUP clamav-freshclam || true

Whenever logrotate rotates freshclam's logfile, the service is inactive
(dead) afterwards.

Reproducer:

$ systemctl is-active clamav-freshclam
active
$ systemctl -q is-active clamav-freshclam && systemctl kill
--signal=SIGHUP clamav-freshclam || true
$ systemctl is-active clamav-freshclam
inactive
$ systemctl status clamav-freshclam.service
● clamav-freshclam.service - ClamAV virus database updater
   Loaded: loaded (/lib/systemd/system/clamav-freshclam.service;
enabled; vendor preset: enabled)
  Drop-In: /etc/systemd/system/clamav-freshclam.service.d
   └─limits.conf
   Active: inactive (dead) since Mon 2019-03-25 16:28:25 CET; 2s ago
 Docs: man:freshclam(1)
   man:freshclam.conf(5)
   https://www.clamav.net/documents
  Process: 15231 ExecStart=/usr/bin/cpulimit -f -l 5 --
/usr/bin/freshclam -d --foreground=true (code=killed, signal=HUP)
 Main PID: 15231 (code=killed, signal=HUP)
  CPU: 57ms

Logrotate for freshclam runs once every week at 06:25. This run was on
2019-03-17, two days later at 2019-03-19 I used my config management to
ensure a highstate. During that run freshclam was started - as defined
in my states:

$ journalctl -x -u clamav-freshclam.service --since 2019-03-16
Mär 17 06:26:06 hostname cpulimit[8290]: Sun Mar 17 06:26:06 2019 ->
Update process terminated
Mär 19 06:22:52 hostname systemd[1]: Started ClamAV virus database updater.
-- Subject: Unit clamav-freshclam.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit clamav-freshclam.service has finished starting up.
-- 
-- The start-up result is done.
Mär 19 06:22:53 hostname cpulimit[29197]: Tue Mar 19 06:22:53 2019 ->
ClamAV update process started at Tue Mar 19 06:22:53 2019


I can just guess, that SIGHUP might be the wrong signal to tell
freshclam to re-open its log file.

This bug is in so far dangerous, as freshclam will not update clamav's
virus definitions anymore. Also clamav-freshclam.service is not failed.

Thank you, Nils

Bug#884648: Follow up on mate-panel crashes

[Mike Gabriel]

On  Mo 25 Mär 2019 15:17:12 CET, Alastair Irvine wrote:


On Mon, 25 March, 2019 at 12:02:13PM +, Mike Gabriel wrote:

Hi,

On  Mo 25 Mär 2019 12:06:57 CET, Alastair Irvine wrote:

>Hello.  On 02 May 2018, #884648 was updated with full backtrace info.
>
>Is there any chance you could take a look at this before the full freeze
>for Buster?

From the bug's history, I cannot see, if the issue happens on a
buster system or just on stretch systems.

Furthermore, the coredump shows that it is caused by
gtk_drag_finish. Both coredumps on the bug hint that your issue is
triggered by some drag'n'drop operation. Is that so?


I noticed it can happen not long after dragging a Window List icon to
reorder, but I've also seen it happen many times randomly when I was
doing something unrelated to the panel.

I saw this same behaviour under both stretch (1.16.2-1) and buster
(v1.20.5-1).

I think it would be worth fixing this, as it could be uploaded to
stretch-backports and potentially buster.  I am prepared to help with
the latter, e.g. apply for an exception to the freeze.


Unfortunately, I am not so deep into upstream coding to fix this. The  
freeze exception is not the problem, it is finding the right patch.


Please get in touch with upstream via  
github.com/mate-desktop/mate-panel/ and see if they made any progress  
there. Once I have a patch, getting the fix landed in Debian is not a  
problem.


Mike
--

DAS-NETZWERKTEAM
c\o Technik- und Ökologiezentrum Eckernförde
Mike Gabriel, Marienthaler str. 17, 24340 Eckernförde
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgpd1oxOokIq7.pgp
Description: Digitale PGP-Signatur

Bug#919207: Bug#923711: squashfs-tools: Please apply frag_deflator_thread removal patch

[Chris Lamb]

Dear lynxis,

> original, my patch had the problem, that it use the 
> same stream (compressor context) as the main thread. This seems to be
> ok, as long the compression is not lzo (I tested with lzma).
> 
> After your patch to fix lzo, the compressor will be initialized with a
> new context on every fragment instead only once for all fragments.
> Also important, all compressor_init's will leak, but since they are
> only called once, it's not a big problem to leak some kbs.

Ah!

Laszlo, would you like any assistance with a debdiff or is lynxis'
patch sufficient asis? You will have to patch the existing patch, if
you see what I mean...


Best wishes,

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

Bug#925448: libcache-fastmmap-perl: test integration with Compress::LZ4 and Compress::Snappy

[Andrius Merkys]

On Mon, 25 Mar 2019, 17:26 gregor herrmann,  wrote:

> in other words: if you add the
> two new build dependencies in the source package to B-D(-I) in
> debian/control, they will also be used for autopkgtests.
>

Great, thanks a lot for showing me how to do this. I will add the b-deps
and try out the autopkgtest.

Best,
Andrius

Bug#925474: unblock: python-aioxmpp/0.10.3-3

[Jonas Schäfer]

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

Please unblock package python-aioxmpp

Fixes the FTBFS issue #924801 by backporting an upstream commit.

diff -Nru python-aioxmpp-0.10.3/debian/changelog python-
aioxmpp-0.10.3/debian/changelog
--- python-aioxmpp-0.10.3/debian/changelog  2019-02-23 16:54:49.0
+0100
+++ python-aioxmpp-0.10.3/debian/changelog  2019-03-21 17:00:14.0
+0100
@@ -1,3 +1,15 @@
+python-aioxmpp (0.10.3-3) unstable; urgency=medium
+
+  * Fix test failure due to updated Python 3.7. This applies the
+unreleased upstream commit 13ab00d [1].
+
+[1]: https://github.com/horazont/aioxmpp/commit/
+ 13ab00d64094b9a13d9d6984d7509bb40efb1fce
+
+closes: #924801
+
+ -- Jonas Schäfer   Thu, 21 Mar 2019 17:00:14 +0100
+
 python-aioxmpp (0.10.3-2) unstable; urgency=medium

   * Use CI=true mode [1] for tests during package build, to prevent
diff -Nru python-aioxmpp-0.10.3/debian/patches/python37-tests-compat.patch
python-aioxmpp-0.10.3/debian/patches/python37-tests-compat.patch
--- python-aioxmpp-0.10.3/debian/patches/python37-tests-compat.patch
1970-01-01 01:00:00.0 +0100
+++ python-aioxmpp-0.10.3/debian/patches/python37-tests-compat.patch
2019-03-21 17:00:14.0 +0100
@@ -0,0 +1,20 @@
+diff --git a/tests/xso/test_model.py b/tests/xso/test_model.py
+index b6d2e29..b1a2a75 100644
+--- a/tests/xso/test_model.py
 b/tests/xso/test_model.py
+@@ -2200,13 +2200,9 @@ class TestXSO(XMLTestCase):
+ )
+
+ def test_init_takes_no_arguments(self):
+-with self.assertRaisesRegex(
+-TypeError,
+-r"takes no (parameters|arguments)"):
++with self.assertRaises(TypeError):
+ xso.XSO("foo")
+-with self.assertRaisesRegex(
+-TypeError,
+-r"takes no (parameters|arguments)"):
++with self.assertRaises(TypeError):
+ xso.XSO(bar="foo")
+
+ def test_init_forwards_to_base_class(self):
diff -Nru python-aioxmpp-0.10.3/debian/patches/series python-
aioxmpp-0.10.3/debian/patches/series
--- python-aioxmpp-0.10.3/debian/patches/series 2019-01-12 22:35:42.0
+0100
+++ python-aioxmpp-0.10.3/debian/patches/series 2019-03-21 17:00:14.0
+0100
@@ -1,3 +1,4 @@
 workaround-dh_python3-dep-issue.patch
 remove-github-button.patch
 remove-ci-buttons.patch
+python37-tests-compat.patch


unblock python-aioxmpp/0.10.3-3

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

Kernel: Linux 4.19.0-1-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Bug#925454: RM: tomcat8 -- ROM; Replaced by tomcat9

[Thorsten Glaser]

clone 925454 -1
reassign -1 tomcat9
found -1 9.0.16-3
retitle -1 tomcat9: sysvinit script missing (Policy §9.11¶2 “must”)
severity -1 serious
tags -1 = confirmed
outlook -1 working on it within the week --mirabilos
owner -1 t...@mirbsd.de
thanks

On Mon, 25 Mar 2019, Scott Kitterman wrote:

> Isn't one required by policy 9.11 (must is in the second paragraph of
> the main part).

Oh, goodie. I had not realised this is, as the init system diversity GR
did not pass, still a “must”.

In this case it’s easy… I’m cloning this as RC bug against tomcat9 and
will work within the next couple of days on fixing this by providing a
proper init script, as team upload / RC squash.

Then I’ll withdraw my objection against tomcat8 removal fully.

Thanks,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

*

**!!! NEU !!!** Mit der **tarent Academy** bieten wir ab sofort auch Trainings
und Schulungen in den Bereichen Softwareentwicklung, Agiles Arbeiten und
Zukunftstechnologien an. Besuchen Sie uns
auf [www.tarent.de/academy](http://www.tarent.de/academy). Wir freuen uns auf
Ihren Kontakt.

*

Bug#925448: libcache-fastmmap-perl: test integration with Compress::LZ4 and Compress::Snappy

[gregor herrmann]

On Mon, 25 Mar 2019 11:18:40 +0200, Andrius Merkys wrote:

> I suggest making the package build-depend on both libcompress-*-perl
> packages to run the tests during build. 

Sounds like a good idea to time.
I think you can just go ahead and add them in git.

> However, I don't know how to
> specify autopkgtest dependencies when test suite is specified as
> 'Testsuite: autopkgtest-pkg-perl'.

If you look at the output of autodep8 in a perl source package, you
see:

% autodep8
Test-Command: /usr/share/pkg-perl-autopkgtest/runner build-deps
Depends: @, @builddeps@, pkg-perl-autopkgtest
Features: test-name=autodep8-perl-build-deps

Test-Command: /usr/share/pkg-perl-autopkgtest/runner runtime-deps
Depends: @, pkg-perl-autopkgtest
Features: test-name=autodep8-perl

Test-Command: /usr/share/pkg-perl-autopkgtest/runner runtime-deps-and-recommends
Depends: @, pkg-perl-autopkgtest
Restrictions: needs-recommends
Features: test-name=autodep8-perl-recommends


and the first test has '@builddeps@'; in other words: if you add the
two new build dependencies in the source package to B-D(-I) in
debian/control, they will also be used for autopkgtests.


Cheers,
gregor

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


signature.asc
Description: Digital Signature

Bug#924176: apt-dater: broken symlink: /usr/share/doc/apt-dater/README -> README.md

[Patrick Matthäi]

tag #924176 + pending
thanks

Am 10.03.2019 um 03:50 schrieb Andreas Beckmann:
> Package: apt-dater
> Version: 1.0.4-1
> Severity: normal
> 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...):
>
> 0m22.7s ERROR: FAIL: Broken symlinks:
>   /usr/share/doc/apt-dater/README -> README.md (apt-dater)
>
>
> cheers,
>
> Andreas

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

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

Bug#925454: RM: tomcat8 -- ROM; Replaced by tomcat9

[Scott Kitterman]

On Monday, March 25, 2019 02:17:15 PM Thorsten Glaser wrote:
> On Mon, 25 Mar 2019, Emmanuel Bourg wrote:
> > Please remove the tomcat8 package from testing and unstable (not
> > experimental). This package has been replaced by tomcat9 for Buster.
> 
> Please don’t, tomcat9 has no sysvinit script, and you did
> not like any of my suggestions for it.

Isn't one required by policy 9.11 (must is in the second paragraph of the main 
part).

Scott K

Bug#883872: (no subject)

[Sean Whitton]

Hello Wilmer,

On Fri 02 Feb 2018 at 05:44AM GMT, Wilmer van der Gaast wrote:

> Please quote the part of
> https://www.debian.org/doc/debian-policy/#copyright-information that
> says "every single file must be mentioned in the copyright file". I
> don't see it there nor would I see the point as per-file info is best
> off stored in those very files.
>
> Let me know if there's something actually serious like a *licence* not
> being accounted for, or a (significant) author or group of authors (that
> is not the currently mentioned me/dx/BitlBee team or Gaim team) not
> mentioned.

You're correct that it is not the case that every single file must be
mentioned.  And /completely/ precise information about what "portions of
code a license refers to" is not required.  For example, if a file
contains code under multiple licenses, you do not have to give the line
numbers, just say that the file is under (e.g.) "GPL-2+ and MPL-2.0".

However, every single copyright holder must be given in d/copyright,
including the years for which they hold copyright, per [1] and Policy
2.3, "every package must be accompanied by a verbatim copy of its
copyright information."  Indeed, Policy was clarified in response to
[1], in release 4.3.0.

I'm not going to bounce the bug severity again, but if Michael is right
that all not copyright holders are listed, then this is RC.

[1]  https://lists.debian.org/debian-devel-announce/2018/10/msg4.html

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#925472: apache2: AuthLDAPBindPassword with exec: variant: child processes not properly destroyed

[Salvatore Bonaccorso]

Source: apache2
Version: 2.4.25-3+deb9u6
Severity: normal
Tags: upstream
Forwarded: https://bz.apache.org/bugzilla/show_bug.cgi?id=61817
Control: found -1 2.4.25-3

Hi

When using a setup using for mod_authnz_ldap the AuthLDAPBindPassword
directive specifically with the exec: variant as documented in [1], a
respective child process is not destroyed correctly.

To reproduce the issue within a .htaccess file (we managed to
reproduce in .htaccess context but not in a directory context)

> AuthType Basic
> AuthName "Restricted access"
> AuthBasicProvider ldap
> 
> AuthLDAPURL $url
> AuthLDAPBindDN $binddn
> AuthLDAPBindPassword "exec:/bin/cat /path/to/ldap/passwd"
> 
> Require valid-user

is enough, resulting in defunct processes

[...]
S www-data 145731  82080  0  80   0 13016 223273 - 13:50 ?00:00:00  
\_ /usr/sbin/apache2 -k start
Z www-data 151575 145731  0  80   0 0 0 -  14:21 ?00:00:00  
|   \_ [cat] 
S www-data 145732  82080  0  80   0 13980 223674 - 13:50 ?00:00:00  
\_ /usr/sbin/apache2 -k start
Z www-data 151686 145732  0  80   0 0 0 -  14:22 ?00:00:00  
\_ [cat] 
[...]

The issue has been submitted upstream already in [2] with a tentative
patch, but it looks the issue got not yet adressed upstream.

Regards,
Salvatore

 [1] 
http://httpd.apache.org/docs/2.4/mod/mod_authnz_ldap.html#AuthLDAPBindPassword 
 [2] https://bz.apache.org/bugzilla/show_bug.cgi?id=61817

Bug#919207: Bug#923711: squashfs-tools: Please apply frag_deflator_thread removal patch

[Chris Lamb]

Hi László,

> Am I right that this isn't going to be fixed soon? I will remove this 
> patch on Monday in the afternoon as the release of Buster is getting 
> close.

Alas, I don't think I will be able to get to writing a patch/fix today
as I don't fully understand the leak (or, actually, the original patch!)
just yet.

Lynxis, do you have any quick pointers, however?


Best wishes,,

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

Bug#925418: unblock: postfix/3.4.4-1

[Scott Kitterman]

On Sun, 24 Mar 2019 16:04:02 -0400 Scott Kitterman  
wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Please unblock package postfix
> 
> About the time we were switching to postfix 3.4 in Buster there were a 
series
> of bug reports/updates from upstream.  The first one (3.4.1 was caught in 
the
> transition from experimental to unstable/buster.  I decided to wait and see
> how things went upstream before uploading/asking for another unblock.
> 
> It looks like things have calmed down, so I'd like to get 3.4.4 into buster 
to
> address several bugs, two of which are significant.  Since this is a post-
> freeze bugfix update, I've taken to using the same level of detail in 
debian/
> changelog that I've used for the stretch pu uploads that we've been doing
> (3.1.6, 3.1.8, and 3.1.9).
> 
> These are all good bug fixes to have.  The broken DANE trust anchor file
> support is a serious regression in it's own right and the
> reject_multi_recipient_bounce bug, while not new, seems to be more frequent 
or
> more visible with BDAT.
> 
> Thanks for considering,
> 
> Scott K
> 
> unblock postfix/3.4.4-1

I've just realized that there is a Debian bug for the BDAT chunking bug 
(#925082).  I've adjusted it's severity appropriately and added it to debian/ 
changelog for the upload, so that's two Debian RC bugs this update fixes.

Scott K

Bug#924881: postgresql: buster upgrade breaks older postgresql (9.6) and newer postgresql (11) is also inoperative

[Christoph Berg]

Control: reassign -1 ssl-cert

Re: Boyd Stephen Smith Jr. 2019-03-23 <2814398.NhXIpRQrxM@monster>
> > My guess would be that the snakeoil key was generated a very long time
> > ago, when the key size defaults were less than they are today, and
> > buster's libssl is now rejecting the key.
> 
> Yes, I was able to run:
> 
> sudo make-ssl-cert generate-default-snakeoil --force-overwrite
> 
> to resolve the issue.  Note the `--force-overwrite`, which is not used by the 
> various postinst scripts.
> 
> It would be nice if the buster upgrade could so this for the user, but I 
> don't 
> know if that's reasonable for all Debian installations.  IMO, It would be a 
> good buster release note.  In any case, it's not a *PostgreSQL* bug.

Looking at ssl-cert's postinst script (where make-ssl-cert is from),
there is no code that would upgrade snakeoil certificates that have
been created using outdated standards.

ssl-cert maintainers: Please consider adding something that
regenerates "small" certificates, or at least informs the user that
something needs to be done. (If you think this is not a bug, please
close it.)

Thanks,
Christoph

Bug#884648: Follow up on mate-panel crashes

[Alastair Irvine]

On Mon, 25 March, 2019 at 12:02:13PM +, Mike Gabriel wrote:
> Hi,
> 
> On  Mo 25 Mär 2019 12:06:57 CET, Alastair Irvine wrote:
> 
> >Hello.  On 02 May 2018, #884648 was updated with full backtrace info.
> >
> >Is there any chance you could take a look at this before the full freeze
> >for Buster?
> 
> From the bug's history, I cannot see, if the issue happens on a
> buster system or just on stretch systems.
> 
> Furthermore, the coredump shows that it is caused by
> gtk_drag_finish. Both coredumps on the bug hint that your issue is
> triggered by some drag'n'drop operation. Is that so?

I noticed it can happen not long after dragging a Window List icon to
reorder, but I've also seen it happen many times randomly when I was 
doing something unrelated to the panel.

I saw this same behaviour under both stretch (1.16.2-1) and buster
(v1.20.5-1).

I think it would be worth fixing this, as it could be uploaded to
stretch-backports and potentially buster.  I am prepared to help with
the latter, e.g. apply for an exception to the freeze.

Bug#925454: RM: tomcat8 -- ROM; Replaced by tomcat9

[Thorsten Glaser]

On Mon, 25 Mar 2019, Emmanuel Bourg wrote:

> Hi Thorsten,
> 
> Le 25/03/2019 à 14:17, Thorsten Glaser a écrit :
> 
> > Please don’t, tomcat9 has no sysvinit script, and you did
> > not like any of my suggestions for it.
> 
> I don't mind if tomcat8 is released with Buster, but I won't be able to
> commit any time on the security fixes. Do you volunteer? The security
> team might want to have a say too.

I’d prefer if we could amend the tomcat9 package with a sysvinit
script. (Although we currently don’t have most inhouse software
tested with Tomcat 9, that can be done.) On the other hand, by
now, also the SRM need to agree to that upload.

I’d very happily maintain the init script.


If this is not possible, I’d agree to upload fixes for tomcat8,
if I get a hold of them. I see upstream has not published an
EOL date for 8.5, and the antecessor Tomcat 7 is still supported,
so this might be feasible. I have no problem doing this in the
experimental distribution. I would, however, appreciate a ping
whenever there’s something, as I have no means to know when
something relevant were to pop up.


But somehow, I think the “let’s add a sensible init script to
tomcat9 now” is the better solution for everyone. Emmanuel, can
you please reconsider your rejection? Then we can ask SRM if
they’d allow it.

To recall the justification I posted to the list that were,
IIRC, never replied:

I will happily maintain the init script. If there’s something,
ping me. I know shell scripting very well. And even if I don’t
respond for weeks on end (unlikely) you can still remove it if
it’s RC-buggy, but I’d prefer keeping it in.

(The only sad thing is that I had ideas of creating a better
init script concept, and that was not done obviously.)

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

*

**!!! NEU !!!** Mit der **tarent Academy** bieten wir ab sofort auch Trainings
und Schulungen in den Bereichen Softwareentwicklung, Agiles Arbeiten und
Zukunftstechnologien an. Besuchen Sie uns
auf [www.tarent.de/academy](http://www.tarent.de/academy). Wir freuen uns auf
Ihren Kontakt.

*

Bug#925082: postfix: "Chunk exceeds message size limit" when message_size_limit = 0

[Scott Kitterman]

On Mon, 25 Mar 2019 07:10:22 -0700 James Bottomley 
 wrote:
> On Tue, 19 Mar 2019 21:53:41 + Scott Kitterman  m> wrote:
> > This is fixed in a new upstream release that I expect to package
> > shortly.
> 
> Me too on being affected by this and waiting to the fixed version 3.4.4
> being packaged.  Since postfix is actually rejecting email permanently,
> shouldn't this be a grave bug?

Good point.  I've updated the severity.

I have 3.4.4 packaged and have requested from the release team to get it into 
Buster.  Once they (hopefully) approve the unblock, I'll upload to unstable 
and it'll be on it's way.

Scott K

Bug#925471: mokutil fails for all non-trivial operations

[Alois Wohlschlager]

Package: mokutil
Version: 0.2.0-1+b3
Severity: grave
Tags: patch
Justification: renders package unusable

Dear Maintainer,

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

   * What led up to the situation?
 - Trying to test Secure Boot support, as in
https://wiki.debian.org/SecureBoot/Testing.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 - Follow the guide until step 5.1 (which is the step where mokutil
 fails).
   * What was the outcome of this action?
 - After prompting for a password twice, mokutil fails with the
 following error message:
Failed to write MokAuth
Failed to unset MokNew
Failed to enroll new keys
   * What outcome did you expect instead?
 - mokutil does not fail.

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

The reason for the failure is that since some time ago, Linux started
creating EFI variables as immutable. Our old version of mokutil does
not care about this.
Thus, when mokutil attempts to write a second time (MokAuth) or unlink
(MokNew) a variable, the operation fails.



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

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

Versions of packages mokutil depends on:
ii  libc6  2.28-8
ii  libssl1.1  1.1.1b-1

mokutil recommends no packages.

mokutil suggests no packages.

-- no debconf information



immutable-variables
Description: Binary data

Bug#810985: Patch

[Thierry fa...@linux.ibm.com]

Hello,
As the fix for ppc64el is simple, couldn't it be integrated ... or
definitely no interest ?!
Thanks




On Thu, 21 Sep 2017 15:51:56 +0200 =?UTF-8?B?RnLDqWTDqXJpYw==?= Bonnard
 wrote:
> Hi,
> the message "dlopen of .../pl-tai.so failed with error libplstream.so:
> cannot open shared object file: No such file or directory" is not
> actually linked to the FTBFS as far as I understood : the same error
> message happens on other architecture builds, but the install works.
> The dlopen with RTLD_GLOBAL flag of pl-tai.so just doesn't find the 
> libplstream.so
> in the path as it is. For this message to disappear, one need to set the
> LD_LIBRARY_PATH to the same as YAPLIBDIR.
> 
> On debomatic-powerpc the package built fine, so that bug may also depend on 
> other things.
> On ppc64el, yap is just looping in some mmap/munmap related to allocation 
> code :
> (gdb) bt
> #0  0x3fffb784b768 in munmap () from /lib/powerpc64le-linux-gnu/libc.so.6
> #1  0x20043d6c in ExtendWorkSpace (s=3604480, fixed_allocation=16) at 
> ../C/alloc.c:1143
> #2  0x20044b08 in Yap_ExtendWorkSpaceThroughHole (s=3604480) at 
> ../C/alloc.c:1606
> #3  0x200b21fc in execute_growstack (size0=524288, from_trail=0, 
> in_parser=0, old_trp=0x0, tksp=0x0, vep=0x0) at ../C/grow.c:1493
> #4  0x200b2570 in growstack (size=524288) at ../C/grow.c:1604
> #5  0x200b3374 in Yap_growstack (size=) at 
> ../C/grow.c:1471
> #!/usr/bin/make -f
> #6  0x200ba274 in call_gc (gc_lim=4096, predarity=0, 
> current_env=0x10a33818, nextop=0x101ce7e0) at ../C/heapgc.c:4009
> #7  0x200ba52c in Yap_gc (predarity=, 
> current_env=, nextop=) at ../C/heapgc.c:4035
> #8  0x20024ac0 in Yap_absmi (inp=) at ../C/absmi.c:2957
> #9  0x2008d874 in exec_absmi (top=1) at ../C/exec.c:1007
> #10 0x2008de98 in do_goal (t=268551041, CodeAdr=0x100740e0, arity=0, 
> pt=0x0, top=1) at ../C/exec.c:1074
> #11 0x2009a244 in Yap_RunTopGoal (t=268551041) at ../C/exec.c:1292
> #12 0x2001bdf4 in YAP_RunGoalOnce (t=) at 
> ../C/c_interface.c:2037
> #13 0x20016cdc in do_top_goal (Goal=268551041) at ../console/yap.c:116
> #14 exec_top_level (iap=0x3210, BootMode=) at 
> ../console/yap.c:711
> #15 main (argc=, argv=) at ../console/yap.c:752
> 
> Redhat seemed to have that same issue : 
> https://sourceforge.net/p/yap/mailman/message/33828905/
> and using --enable-use-malloc helped.
> So here is a patch that makes the build use that option for powerpc and 
> ppc64el (it
> should work on ppc64, but this arch is not enabled for yap and I wanted the 
> patch
> to be minimal).
> 
> F.

-- 
Thierry Fauck @ fr.ibm.com

Bug#925354: [Debian-ha-maintainers] Bug#925354: pacemaker-dev: missing Breaks+Replaces: libcrmcluster1-dev

[Valentin Vidic]

On Mon, Mar 25, 2019 at 03:45:58PM +0100, Andreas Beckmann wrote:
> In that case you should probably add Breaks+Replaces against all of the
> old -dev packages that were merged, just to be on the safe side.

Yes, that is the plan. I think wferi will take care of it if he
has time?

-- 
Valentin

Bug#925470: ptpd uses 100% of its assigned CPU core

[Simon Hanisch]

Package: ptpd
Version: 2.3.0-dfsg-1
Severity: normal

Dear Maintainer,

I used ptpd to synchronize the clocks between two hosts (A and B). Both sync 
via multicast with 
a master. All three hosts are connected via a gigabit switch. I conducted a 
bandwith test 
with iperf to send traffic from A to B. After the test the ptpd daemon on host 
A started 
using 100% of its assgined CPU core. Since ptpd did not stop to run at a 100% I 
was forced to 
stop and restart the daemon. I was able to reproduce this behavior multiple 
times.

Best Regards
Simon

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

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

Versions of packages ptpd depends on:
ii  libc6   2.19-18+deb8u10
ii  libpcap0.8  1.6.2-2
ii  lsb-base4.1+Debian13+nmu1

ptpd recommends no packages.

ptpd suggests no packages.

-- Configuration Files:
/etc/default/ptpd changed:
START_DAEMON=yes
PTPD_OPTS="-i eth0"


-- no debconf information




smime.p7s
Description: S/MIME Cryptographic Signature