Bug#923706: quilt annotate requires ed

[Christian Kastner]

On 2019-03-04 08:29:29 Christian Kastner wrote:
>   # Create the first patch
>   $ quilt new short.patch && quilt add short.txt
>   $ sed -i '5d' short.txt && quilt refresh

Addendum: if you instead add a line,

  $ echo "addition" >> short.txt && quilt refresh

then `quilt annotate` prints the aforementioned error and just the diff,
but with missing line numbering, where the number indicates which patch
modified the line.

Installing ed solved these issues for me.

Regards,
Christian

Bug#853035: fixed in node-liftoff 2.3.0-3

[Chris Lamb]

Chris Lamb wrote:

> > I didn't find other ways to fix these FTBFS than:
> 
> 
> 
> Thank you. However, can I just underline:
> 
> > > If this was the "only" way to fix the problem, that should be
> > > documented in the package and in the changelog, not simply on
> > > this issue.

Gentle ping on this? :)


Regards,

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

Bug#923707: statsmodels FTBFS: array |= frame now returns frame

[Rebecca N. Palmer]

Source: pandas
Version: 0.23+dfsg-2
Severity: serious
Control: affects -1 src:statsmodels
Control: tags -1 patch

The fix for #918206 (setting __array_priority__ to make np.array @ 
DataFrame work) is technically API breaking: in-place operators


arr = np.array(...)
df = pd.DataFrame(...)
arr += df

used to leave arr as an np.array (though this does not appear to have 
been documented), but now turn it into a DataFrame.


The only known [0] place where this fails a test is in statsmodels: as 
[1] now returns a DataFrame rather than a Series, it is now an exception 
for data passed to statsmodels.formula.api.OLS to contain both missing 
(NaN) values and duplicate index labels.  As 
statsmodels.regression.tests.test_regression.test_missing_formula_predict 
contains such data, statsmodels 0.8.0-9 hence failed to build on the 
architectures where pandas was built first [2].


pandas upstream don't appear to have noticed this: they don't mention it 
in the discussion or release notes of the fix [3].  statsmodels 
upstream's response was to make this test stop using duplicate index 
names (without explicit comment) [4].


An alternative fix for #918206 that doesn't do this is

pandas/core/generic.py
 def __array_wrap__(self, result, context=None):
 d = self._construct_axes_dict(self._AXIS_ORDERS, copy=False)
+if context is not None and context[0]==np.matmul
+and not hasattr(context[1][0],'index'):
+del d['index']
 return self._constructor(result, **d).__finalize__(self)

 # ideally we would define this to avoid the getattr checks, but

but this has not yet been tested in a full build.

[0] autopkgtest results - https://release.debian.org/britney/excuses.yaml
[1] 
https://sources.debian.org/src/patsy/0.5.0+git13-g54dcf7b-1/patsy/missing.py/#L136
[2] 
https://buildd.debian.org/status/fetch.php?pkg=statsmodels&arch=amd64&ver=0.8.0-9&stamp=1551564937&raw=0
[3] https://github.com/pandas-dev/pandas/pull/23114 
https://github.com/pandas-dev/pandas/commit/ad2a14f4bec8a004b2972c12f12ed3e4ce37ff52
[4] (please *do not upload* this without discussion, or we may lose my 
other statsmodels work to the freeze) 
https://github.com/statsmodels/statsmodels/commit/30c9ddbff8a072cbc1bebc7550b667e760cb386a#diff-2708847815406a7890933a960465d8e8

Bug#923706: quilt annotate requires ed

[Christian Kastner]

Package: quilt
Version: 0.65-3
Severity: important

Executing `quilt annotate`, at somepoint, apparently requires ed to be
installed.

Steps to reproduce:

  # Create a test directory
  $ mkdir /tmp/quiltbug && cd /tmp/quiltbug

  # Create a short test file
  $ for file in /etc/cron.*; do echo $file >> short.txt; done

  # Create the first patch
  $ quilt new short.patch && quilt add short.txt
  $ sed -i '5d' short.txt && quilt refresh

  # Bug
  $ quilt annotate
  sh: 1: ed: not found
  patch:  ed FAILED
  [...]


Regards,
Christian

Bug#915050: (gitlab) Re: Bug#915050: Keep out of testing

[Pirate Praveen]

On 2019, മാർച്ച് 3 10:45:19 PM IST, Justin Hallett  
wrote:
>Well I hope it comes to that personally, cause I think you have been
>doing a great job, it’s a TON of work to maintain all the depends you
>do for gitlab and honestly there are rarely issues and when they are
>you fix them very quickly after a report.
>
>It’s very upsetting that I now have 10 tickets in my queue because of
>things I can’t do on gitlab since this ticket broke everything!
>
>I have it working but barely and lots of important tasks like PRs
>aren’t working at all.  Let me know if there is anything I can do, test
>or help with in any way.
>

Currently the blocker is rails 5.2 support, tracked in this upstream issue.

https://gitlab.com/gitlab-org/gitlab-ce/issues/48392

If you can help with that anyway, that'd be great.

>And thank you for all your hard work on this project!
>

Thanks for your kind words.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Bug#923705: RFP: node-parse5 -- HTML parsing/serialization toolset for Node.js

[Jeff Cliff]

Package: wnpp
Severity: wishlist

* Package name: node-parse5
  Version : 437d060b 
  Upstream Author :  Ivan Nikulin 
* URL : https://salsa.debian.org/themusicgod1-guest/parse5/
* License : MIT
  Programming Lang: javascript
  Description : HTML parsing/serialization toolset for Node.js

parse5 is a spec-compliant HTML parser for Nodejs.  It claims to be the fastest 
one, and that it "nearly everything you may need when dealing with HTML."

It claims to parses HTML the way "the latest version of your browser does".
It has proven itself reliable in such projects as jsdom, Angular2, Polymer 
and many more.

It is a dependency of node-prettier (#879665)

Bug#900895: kmail: KMail malfunctioning: Red email folders, no emails can be viewed; "Unable to fetch item from backend (collection-1): Unable to contact resource"

[Jens Radloff]

Hi hefee,

I strongly assume that it makes no sense if I _currently_ would test my PIM 
environment in the current Debian testing release because the behavior 
described in this bug issue did not occur anymore since the last time I 
updated this bug issue on Wed, 27 Feb 2019. 

This is now the 5th day after Wed, 27 Feb 2019 that the behavior did not occur 
again. Before that, between Sunday, 24th 2019 and Wed, 27 Feb 2019, the 
behavior occurred very often. let's say about 30 times.

Since Wed, 27 Feb 2019 I installed at least one system update via apt-get, 
could it be that this update resolved the behavior? I cannot remember which 
package this update updated.

Or could it be that a misconfiguration of one of the remote mail servers which 
I am utilizing, or a erroneous software environment the respective mail server 
is running in, temporary could caused the behavior?

I will report new occurrences of the behavior in this bug issue, but I do not 
know when these occurrences will happen again.

Regards,

Jens


Am Sonntag, 3. März 2019, 22:41:51 CET schrieb Sandro Knauß:
> Control: tags -1 +moreinfo
> Control: reassign -1 kdepim-runtime 4:16.04.2-2+b2
> Control: forcemerge -1 900957
> 
> Thanks for reporting the issue and sorry for not responding for so long
> time.
> 
> The bug is actually in the maildir_resource that is shipped within kdepim-
> runtime package, that why reassign the bug.
> 
> It would be super great if you could test your setup with kmail on Debian
> Buster, that is currently in testing. Because kdepim fixed serveral issues
> for maildir resource.
> 
> hefee

Bug#922650: [pkg-opensc-maint] Bug#922650: opensc-pkcs11: fails to work with dual CAC PIV cards

[Eric Dorland]

Hi,

I'm a bit reluctant to take sure a significant patch set that hasn't
been in a release. Can you elaborate on the consequences of not taking
it? 

* A. Maitland Bottoms (bott...@debian.org) wrote:
> Package: opensc-pkcs11
> Version: 0.19.0-1
> Severity: important
> Tags: patch
> 
> Dear Maintainer,
> 
> Recent PIV enabled CAC cards are not handled by the opensc 0.19.0
> release. Yet all current CAC cards are scheduled to enable PIV
> authentication by March 31, 2019.
> 
> For users of these cards, this bug is of grave severity.
> 
> This problem has been solved recently upstream
> https://github.com/OpenSC/OpenSC
> although the fixes have not yet been included in an upstream release.
> 
> I have cherry-picked from upstream commits a small set that provides
> working card support. It works for me using
> pkcs11-tool --module /usr/lib/x86_64-linux-gnu/opensc-pkcs11.so -l -t
> ssh-keygen -D /usr/lib/x86_64-linux-gnu/opensc-pkcs11.so
> ssh -I /usr/lib/x86_64-linux-gnu/opensc-pkcs11.so
> and Firefox browser smart card token support.
> 
> Attached is a debdiff of my test package.
> 
> I think Buster will be much better if we can release it with support
> for this use case.
> 
> Thanks,
> -Maitland
> 
> enc: opensc-pkcs11-Dual-CAC-PIV-and-PIVK-support.debdiff


> ___
> pkg-opensc-maint mailing list
> pkg-opensc-ma...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-opensc-maint


-- 
Eric Dorland 
43CF 1228 F726 FD5B 474C  E962 C256 FBD5 0022 1E93

Bug#923704: netcat6: compiled without support for -C (crlf)

[Russell Coker]

Package: netcat6
Version: 1.0-8
Severity: normal


Please compile nc with support for -C for the situations where servers want
that sort of thing.

# nc -C localhost 25
nc: internal error: invalid option -- C (netcat was compiled with 
--disable-crlfoption)
 (please report this error to nc6 authors)
Aborted (core dumped)

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

Kernel: Linux 4.19.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Enforcing - Policy name: default

Versions of packages netcat6 depends on:
ii  libc6  2.28-7

netcat6 recommends no packages.

netcat6 suggests no packages.

-- no debconf information

Bug#923703: bash: Path not set correctly when using su command

[patrick]

Package: bash
Version: 5.0-2
Severity: important

Dear Maintainer,

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

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?


using the command shell logged in as root using the su command
most usual commands work as expected but dpkg is failing as below
dpkg: warning: 'ldconfig' not found in PATH or not executable
dpkg: warning: 'start-stop-daemon' not found in PATH or not executable
dpkg: error: 2 expected programs not found in PATH or not executable
Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin and /sbin

from the set command the output includes
PATH=/home/patrick/.local/share/umake/bin:/home/patrick/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games


-- 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_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_NZ:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages bash depends on:
ii  base-files   10.1
ii  debianutils  4.8.6.1
ii  libc62.28-7
ii  libtinfo66.1+20181013-2

Versions of packages bash recommends:
ii  bash-completion  1:2.8-5

Versions of packages bash suggests:
pn  bash-doc  

-- no debconf information

Bug#648625: Close save-meta dialog after opening the next dialog

[martin f krafft]

Quoting "Jeffrey Ratcliffe", who wrote on 2017-09-22 at 18:09 Uhr +0200:
This bug has been open for a long time. It is time I did something, one 
way or the other.


What would like to happen if the "cancel" is pressed on the "save-file" 
dialogue?


Should the file type/metadata dialogue then reopen or not?


Oh wow, I just found this ;)

So uh, is there any reason that the two cannot be combined into one 
dialog? Bonus points for providing a means to automatically navigate 
folders and preseed the filename based on certain metadata entered.


And hey, I don't say this often enough, but gscan2pdf is in daily 
use here, and I'm surveying the entire doc management space all the 
time, but nothing other even comes close to this for me, so THANK 
YOU VERY MUCH FOR IT!!!


--
.''`.   martin f. krafft  @martinkrafft
: :'  :  proud Debian developer
`. `'`   http://people.debian.org/~madduck
 `-  Debian - when you have better things to do than fixing systems

one has to multiply thoughts to the point
where there aren't enough policemen to control them.
-- stanislaw jerzey lec


digital_signature_gpg.asc
Description: Digital GPG signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)

Bug#914794: libmspack fails tests on big endian architectures (s390x, mips)

[duck]

Quack,

On 2019-03-04 10:40, Stuart Caie wrote:

I've released libmspack 0.10 and cabextract 1.9.1. They contain only 
fixes.


Thanks a lot for being so fast.

Unfortunately there is a build problem:
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I./mspack -I./test 
-Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra -Wno-unused-parameter 
-Wno-unused-result -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c 
mspack/oabd.c  -fPIC -DPIC -o mspack/.libs/oabd.o

mspack/oabd.c:375:12: error: conflicting types for ‘copy_fh’
 static int copy_fh(struct mspack_system *sys, struct mspack_file *infh,
^~~
mspack/oabd.c:37:12: note: previous declaration of ‘copy_fh’ was here
 static int copy_fh(struct mspack_system *sys, struct mspack_file *infh,
^~~

Indeed `bytes_to_copy` is not of the same type.

Regards.

--
Marc Dequènes

Bug#923702: swaks lacks support for the SMTPUTF8 command.

[Russell Coker]

Package: swaks
Version: 20181104.0-1
Severity: normal
Tags: upstream

Below is a transcript of my attempt to forge mail from my own domain by
replacing a Roman E character with a Cyrillic character that looks the same.

Postfix rejects the connection due to the lack of a SMTPUTF8 on the mail from
line.

With the current situation a bare minimum would be to mitigate this issue by
detcting non-ascii characters in the sender and recipient addresses and
aborting instead of trying to send a non-compliant message.  It should not
just quietly send non-compliant messages and wait for the server to report a
problem.

# swaks -s localhost -f russell@cokеr.com.au -t russ...@coker.com.au
=== Trying localhost:25...
=== Connected to localhost.
<-  220 smtp.sws.net.au ESMTP Postfix - by sending email to this server you 
agree to the conditions at this URL: 
http://doc.coker.com.au/legal/conditions-of-sending-email/
 -> EHLO smtp
<-  250-smtp.sws.net.au
<-  250-PIPELINING
<-  250-SIZE 5120
<-  250-ETRN
<-  250-STARTTLS
<-  250-AUTH PLAIN LOGIN
<-  250-AUTH=PLAIN LOGIN
<-  250-ENHANCEDSTATUSCODES
<-  250-8BITMIME
<-  250-DSN
<-  250 SMTPUTF8
 -> MAIL FROM:
<** 501 5.1.7 Bad sender address syntax
 -> QUIT
<-  221 2.0.0 Bye
=== Connection closed with remote host.
# idn2 cokеr.com.au
xn--cokr-x4d.com.au


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

Kernel: Linux 4.19.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Enforcing - Policy name: default

Versions of packages swaks depends on:
ii  perl  5.28.1-4

Versions of packages swaks recommends:
ii  libio-socket-inet6-perl  2.72-2
ii  libnet-dns-perl  1.19-1
ii  libnet-ssleay-perl   1.85-2+b1

Versions of packages swaks suggests:
pn  libauthen-ntlm-perl  
ii  libauthen-sasl-perl  2.1600-1
pn  perl-doc 

-- no debconf information

Bug#923701: Black rectangles appears at top-left of window when using a tiling WM.

[Michael Gilbert]

control: tag -1 pending
control: severity -1 minor

This should be fixed when chromium 73 is uploaded.

Best wishes,
Mike

On Sun, Mar 3, 2019 at 9:51 PM Gong S.  wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Package: chromium
> Version: 72.0.3626.96-1~deb9u2
>
> When launched in a tiling windowing manager, there is a black rectangle 
> appearing randomly in the title bar.
> Moving the mouse will cause the rectangle to disappear-it looks like that it 
> is related to the mouse position.
> It happens regardless of the theme and the GTK2 config.
> This only happens when Chromium is in tiling mode; it does not affect 
> floating windows.
> -BEGIN PGP SIGNATURE-
> Version: ProtonMail
> Comment: https://protonmail.com
>
> wsBcBAEBCAAGBQJcfJGRAAoJENi1YDlFXXQfmagIAKtN8CJruMfz2/fgwsgO
> Y7pCu7anVxngSLPtv+CP/xVoViFKhfi4f1Zjvjoiwygs63KDzZAu2SazSuyU
> xj+ELOf0F+2/7azXoBv1ATxVjFINDoz/yy2IcICYFqASmK5iuDo646bx+2+U
> J4OgS74SKimZT7VjBIv6kbaimE2jqX2HDijpxPlO9OgMXgmn8u/YgLRANiRo
> AVS0noM2eimjtr+GdOUQADnLwC4cZew8w102aMc3NvYgUSHbBywzpcp90eio
> C2cpIxqDpWx/USkEAh6SlichfX5rnrDBJP7GytpaX7Wg3RPgii+zLXwN3+yx
> xI5glwKTXkF3gHTb3OpnXSI=
> =tnzV
> -END PGP SIGNATURE-
>

Bug#923603: Drop continuity cli to reduce the Build-Depends

[Arnaud Rebillout]

On Sun, 3 Mar 2019 01:45:01 +0800 Shengjing Zhu  wrote:
> Source: continuity
> Severity: wishlist
>
> Hi Arnaud and team,
>

> I want to know if you object to drop the continuity cli from this package.

Hi Shengjing Zhu,

no objection for me.

Initially I packaged continuity as a dependency of containerd, with the
ultimate goal to package docker.io. In the end it turns out that we
can't use it to package docker.io due to circular dependencies.
'continuity', 'containerd' and a bunch of containerd dependencies are
leftovers of this work, but I really don't use or care about these
packages anymore. Feel free to do whatever needs to be done!

  Arnaud

Bug#923699: bibtool: please update my email address

[Jerome BENOIT]

Hello Norbert,

On 04/03/2019 04:17, Norbert Preining wrote:
> Package: bibtool
> Version: 2.67+ds-5
> Severity: normal
> 
> Hi Jerome
> 
> could you please update my email address in the bibtool package
> to norb...@preining.info, since the @d.o is not functional,


before the freeze ?

> and I cannot do it myself since I don't have access to salsa.

Sorry for that.

> 
> Thanks a lot
> 
> Norbert
> 

Thanks,
Jerome

> 
> -- System Information:
> Debian Release: buster/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (200, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 4.20.13 (SMP w/4 CPU cores)
> Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
> LANGUAGE=en_US:en (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages bibtool depends on:
> ii  libc6 2.28-8
> ii  libkpathsea6  2018.20181218.49446-2
> ii  tex-common6.11
> 
> Versions of packages bibtool recommends:
> ii  texlive-base  2018.20190227-2
> 
> bibtool suggests no packages.
> 
> -- no debconf information
> 

-- 
Jerome BENOIT | calculus+at-rezozer^dot*net
https://qa.debian.org/developer.php?login=calcu...@rezozer.net
AE28 AE15 710D FF1D 87E5  A762 3F92 19A6 7F36 C68B



signature.asc
Description: OpenPGP digital signature

Bug#923699: bibtool: please update my email address

[Norbert Preining]

Hi Jerome

On Mon, 04 Mar 2019, Jerome BENOIT wrote:
> > to norb...@preining.info, since the @d.o is not functional,
> 
> before the freeze ?

Not necessarily. Whenever it is convenient for you.

I have moved all the packages where I am the responsible off to github
and update email and vcs fields accordingly, and uploaded so that in
buster the correct information is included.

But since you are the main responsible for bibtool it is up to you
how/when/what. No need to change anything for now.

Thanks

Norbert

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

Bug#887159:

[Peto Mica]

petom...@azet.sk

Bug#887159:

[Peto Mica]

petom...@azet.sk

Bug#914794: libmspack fails tests on big endian architectures (s390x, mips)

[Stuart Caie]

On 03/03/2019 04:47, Marc Dequènes (duck) wrote:

Quack,

On 2018-12-04 19:02, Stuart Caie wrote:


This is fixed in the repository, it just hasn't been released. I'll
release it in the near future.


I was myself busy and we missed the Debian freeze deadline. Maybe 
there is still some hope to convince the release team for an 
exception, as long as we push fixes only. Any plan to release shortly?


I've released libmspack 0.10 and cabextract 1.9.1. They contain only fixes.

Regards
Stuart

Bug#921518: flash-kernel: [PATCHv2] Adding-definition-of-Raspberry-Pi-Family

[Vagrant Cascadian]

Control: tags 921518 -patch

On 2019-02-06, Ben Hutchings wrote:
> On Wed, 2019-02-06 at 13:45 +0100, Alexandre GRIVEAUX wrote:
>> With adding correction of Raspberry pi 1 to use ARMEL flavour from feedback.
> [...]
>
> "armel" is the name of the Debian architecture that can run on the Pi
> 0/1, not the name of a kernel flavour.  We do not yet have any kernel
> flavour for these yet, and it is unlikely to be "armel".  We tend to
> use the architecture name as a kernel flavour name only if it can
> support most hardware for that architecture.


signature.asc
Description: PGP signature

Bug#923700: can't even find the file should be an error

[積丹尼 Dan Jacobson]

Package: perl
Version: 5.28.1-4
Severity: wishlist

Please make perl return a reasonable exit status like sed in this case:

$ sed 's/a/b/' /tmp/z; echo $?
sed: can't read /tmp/z: No such file or directory
2
$ perl -pwe 's/a/b/' /tmp/z; echo $?
Can't open /tmp/z: No such file or directory.
0
$ perl -pwe 'BEGIN{use warnings FATAL => q(all);} s/a/b/' /tmp/z; echo $?
Can't open /tmp/z: No such file or directory.
0
$ perl -pwe 'BEGIN{use warnings FATAL => q(all); $$SIG{__WARN__} = sub { die @_ 
};} s/a/b/' /tmp/z; echo $?
Can't open /tmp/z: No such file or directory.
0

FORGET IT.
$ test -f /tmp/z && perl ...

Bug#923699: bibtool: please update my email address

[Norbert Preining]

Package: bibtool
Version: 2.67+ds-5
Severity: normal

Hi Jerome

could you please update my email address in the bibtool package
to norb...@preining.info, since the @d.o is not functional,
and I cannot do it myself since I don't have access to salsa.

Thanks a lot

Norbert


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

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

Versions of packages bibtool depends on:
ii  libc6 2.28-8
ii  libkpathsea6  2018.20181218.49446-2
ii  tex-common6.11

Versions of packages bibtool recommends:
ii  texlive-base  2018.20190227-2

bibtool suggests no packages.

-- no debconf information

Bug#923591: It would be nice to have a keyboard shortcut to restore window in featherpad

[Alf Gaida]

Currently there is no way to have a keyboard shortcut for restoring
window. I looked at the shortcuts and didn't find a way. Could you
please see if such an option is also available, instead of just using
the mouse.


What should restoring a window mean? Bringing a minimized Window to 
front? In that case it would be Window-Manager functionality - aka 
taskswitcher.

Bug#890817: kernel-package: make-kpkg stalls indefinitely on linux-4.16-rc* in silentoldconfig stage

[Nicholas Humfrey]

Hi,

I also found that these patches helped stop the compile getting blocked 
- but they only seem to treat the symptoms, not the cause. As with 
David, my configuration seems to get modified / overwritten during the 
build.


I traced the problem down to
- a dependency on the target: debian/stamp/conf/vars
- Which executes: make -f ./debian/ruleset/kernel_version.mk 
debian_conf_var

- kernel_version.mk includes the main Linux kernel Makefile
- For some reason this causes the Linux Makefile to run `make 
syncconfig`


At which point it starts asking questions and changes the kernel 
configuration.


Linux source version: 4.19.20.
Note that I also only have problems when compiling for x86, not amd64.


nick.

Bug#523979: #523979 atftpd: please add generated content patch

[Paul Wise]

On Sun, 2019-03-03 at 23:07 +0100, Reiner Herrmann wrote:

> I just noticed that you suggested a patch for atftp,
> but it is no longer available.

There is a HTML-only copy of the patch on archive.org, it would require
some pre-processing but it could potentially be applied.

https://web.archive.org/web/20090502165734/http://www.kaarsemaker.net/downloads/code/atftp.patch

Looks like there may be a git repo containing the patch, but the web
server is returning an internal server error for it.

https://git.kaarsemaker.net/
https://git.kaarsemaker.net/atftp/

The author of the patch seems to be on IRC and also lists their email
address so they should be easily contactable, I've CCed them.

https://www.kaarsemaker.net/contact/

Dennis, we are discussing your old dynamic content patch for atftpd,
which I proposed to add to the Debian package in this bug report:

https://bugs.debian.org/523979

> Do you by chance still have the patch and could attach it
> to the bug? Otherwise I would suggest to close it.

I don't have a copy of the patch file.

BTW, atftpd upstream looks like they need help, you might want to
consider working on atftpd upstream. There is also a newer upstream
release and git commits than what is in Debian.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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

Bug#923698: gcc-mingw-w64 miscompiles PARI

[Bill Allombert]

Package: gcc-mingw-w64-x86-64
Version: 8.2.0-21+21.1
Severity: normal

Dear Stephen,

Since the upgrade to 8.2.0-17, gcc-mingw-w64-x86-64 miscompiles PARI/GP.


The native linux version is fine though.
The bug is caused by longjmp causing wine to crash with

0198:err:seh:setup_exception stack overflow 320 bytes in thread 0198 eip 
7bc9a41c esp 001314d0 stack 0x13-0x131000-0x33

when called in a function doing an unrelated setjmp _after_ the longjmp
(in other functions longjmp work fine), and it does not occurs with the debug
build.

One of the logs for the broken version is at

(the test-suite fails under wine).
I use the following kit to crossbuild:
https://pari.math.u-bordeaux.fr/pub/pari/windows/paricrossmingwkit.tgz

So if you have a suggestion...

Cheers,
Bill.

Bug#720456: [vim-scripts] Please include the solarized colorscheme

[Marco Villegas]

Thanks for the feedback!

I will be happy to re-attempt this after the restructuring.
I will try to git fetch periodically, but an announce here would be
great too.

Best,

-Marco


On Sun, 3 Mar 2019 14:20:06 -0500
James wrote:
> On Fri, Mar 01, 2019 at 10:26:45PM -0500, Marco Villegas wrote:
> > I have used https://github.com/altercation/solarized repository as
> > the base to add the solarized color scheme to the package.  
> 
> Thanks for working on this.
> 
> > I am not entirely sure of the urls on metadata at
> > debian/vim-scripts.status, but I guess that they are OK. It is
> > important to notice that there is a vim.org page, i.e.
> > https://www.vim.org/scripts/script.php?script_id=3520, for the color
> > scheme, but sadly the code there contains an older version of what I
> > find at the repository, and that is why I decided to use the version
> > from the repository.
> > 
> > I was a bit worried on how debian/vim-scripts.pl will handle the
> > github url, but both doc and update actions seems to finish OK,
> > naturally suggesting a false positive on the case of the new
> > solarized addon.  
> 
> All of this is going to be reworked as I'm in the process of changing
> this package from using vim-addon-manager to dh-vim-addon.
> vim-addon-manager had various problems that were holding me back from
> updating vim-scripts.  I haven't been actively working on this since
> it will have to wait until after Buster is released anyway.
> 
> > Another detail I am not sure about is the value of disabledby at
> > debian/vim-scripts.status for this new addon, so I have just
> > skipped it.  
> 
> For a colorscheme, it's not needed.  The user has to explicitly use
> the colorscheme anyway.
> 
> > Also, I have started by updating the html documentation for all
> > addons, since I could not figure out a way to only do it for the
> > new addon. It is in a separate commit, just in case that change is
> > not a good idea.  
> 
> Agreed, that's not necessary right now.
> 
> I would suggest holding off until the package gets restructured.  I'll
> try to make some time for that again so at the very least there's an
> experimental branch this could be merged into.
> 
> Cheers,

Bug#823037: ITP: flatbuffers -- efficient cross platform serialization library

[Bálint Réczey]

Hi,

With the following changes IMO the package would be ready for upload:
https://salsa.debian.org/debian/flatbuffers/merge_requests/1

Cheers,
Balint

Bálint Réczey  ezt írta (időpont: 2019. febr.
21., Cs, 11:25):
>
> Hi,
>
> Bálint Réczey  ezt írta (időpont: 2019. febr.
> 21., Cs, 10:37):
> >
> > Hi Maximiliano,
> >
> > Maximiliano Curia  ezt írta (időpont: 2019.
> > febr. 10., V, 14:15):
> > >
> > > ¡Hola Bálint!
> > >
> > > El 2019-02-10 a las 20:00 +0700, Bálint Réczey escribió:
> > > > On Wed, 30 May 2018 10:25:01 +0900 Nobuhiro Iwamatsu 
> > > > <[1]iwama...@debian.org>
> > > > wrote:
> > > >> 2018-05-29 17:44 GMT+09:00 Maximiliano Curia 
> > > >> <[2]m...@gnuservers.com.ar>:
> > > >>> ¡Hola!
> > >
> > > >>> El 2018-05-29 a las 09:56 +0200, Maximiliano Curia escribió:
> > >
> > >  I created a packaging salsa project here:
> > >  [3]https://salsa.debian.org/debian/flatbuffers
> > >
> > >
> > > >>> Ups, that was a lie, the project was created by Nobuhiro Iwamatsu. I 
> > > >>> was
> > > >>> checking the flatbuffers, sink and kube code base last week and I 
> > > >>> today,
> > > >>> when I found that an empty project was already present, I tought I 
> > > >>> created
> > > >>> the repository and forgot about it.
> > >
> > > >>> Nobushiro, sorry to meddle with this package. Please let me know if 
> > > >>> you are
> > > >>> willing to group maintain this package, if not, please take the 
> > > >>> ownership
> > > > of
> > > >>> this bug.
> > >
> > > >> No problem.
> > >
> > > >> I am planning to packaging apache/arrow.
> > > >> This package depends flatbuffers, if I can, I want to maintain this 
> > > >> package.
> > > >> Coulld you add me to flatbuffers team ?
> > >
> > > > Kodi 18 needs flatbuffers, too.
> > > > I see there is recent activity in the Salsa repo and I'd love to see an 
> > > > upload
> > > > to experimental at least and I'm ready to give a helping hand if 
> > > > something is
> > > > missing from the packaging.
> > >
> > > Any help is welcome, please send merge requests as you see fit. 
> > > Currently, I
> > > don't have any real piece of software that uses flatbuffers, so I can't 
> > > really
> > > test it. Care to give it a try using the packages generated from the salsa
> > > repo to build kodi 18?
> >
> > The package looks fine, and kodi built with it but I have not run the
> > built Kodi yet.
> > I also uploaded the package from salsa to Ubuntu (with the standard
> > lower version number) because today is feature freeze there.
> >
> > I think you can safely upload the package to unstable, too.
>
> To correct myself here the package is _not_ ready for upload in the
> current form:
>
> $ lintian --pedantic -I flatbuffers_1.10.0-1~_amd64.changes
> I: flatbuffers source: duplicate-short-description
> flatbuffers-compiler flatbuffers-compiler-dev libflatbuffers1
> P: flatbuffers source: source-contains-prebuilt-doxygen-documentation
> docs/header.html
> P: flatbuffers source: source-contains-prebuilt-java-object
> android/gradle/wrapper/gradle-wrapper.jar
> P: flatbuffers source: source-contains-prebuilt-java-object
> samples/android/gradle/wrapper/gradle-wrapper.jar
> I: flatbuffers source: composer-package-without-pkg-php-tools-builddep
> I: flatbuffers source: testsuite-autopkgtest-missing
> I: libflatbuffers1: no-symbols-control-file
> usr/lib/x86_64-linux-gnu/libflatbuffers.so.1.10.0
> I: flatbuffers-compiler: spelling-error-in-binary usr/bin/flatc
> overrided overridden
> W: flatbuffers-compiler: binary-without-manpage usr/bin/flatc
>
> Cheers,
> Balint

Bug#923641: dvorak7min FTCBFS: does not pass cross tools to make

[Martin Kelly]

On 3/3/19 1:40 AM, Helmut Grohne wrote:

Source: dvorak7min
Version: 1.6.1+repack-3
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

dvorak7min fails to cross build from source, because it does not pass
cross tools to make. The easiest way of fixing that - using
dh_auto_build - makes dvorak7min cross buildable. Please consider
applying the attached patch.

Helmut



Thanks for the patch! I have put it in git and requested an upload from 
Francois Marier, so it should go in soon.

Bug#813176: "Checking in progress on 1 disk. (0.0%)" doesn't update

[Pierre Ynard]

reassign 813176 systemd
thanks

This line is, or was, part of the systemd-fsckd source code:

https://github.com/systemd/systemd/blob/e7a3aa3df640993ce9aace39b946543305f3af53/src/fsckd/fsckd.c#L343

Reassigning to systemd maintainers, they will be better able to answer
about these progress reporting issues.

Thanks,

-- 
Pierre Ynard

Bug#730048: kmail does not properly quote From field when replying

[Sandro Knauß]

Control: tags -1 -moreinfo
Control: found -1 4:18.08.1-1
Control: found -1 4:4.14.1-1+deb8u1

Hey,

well the bug is an upstream one, so please report back there, that you can 
reproduce it with a new version. It is too much work for me to forward your 
input.

https://bugs.kde.org/show_bug.cgi?id=343812

hefee

--
On Dienstag, 15. Januar 2019 18:43:49 CET LeJacq, Jean Pierre wrote:
> Here's an update for kmail in buster which is at the following version:
> 
> $ apt-cache policy kmail
> kmail:
>   Installed: 4:18.08.1-1
>   Candidate: 4:18.08.1-1
>   Version table:
>  *** 4:18.08.1-1 500
> 500 http://ftp.us.debian.org/debian buster/main amd64 Packages
>   2 http://ftp.us.debian.org/debian unstable/main amd64 Packages
> 100 /var/lib/dpkg/status
> 
> The bug continues to exist. Unfortunately, the option to make the identity
> sticky is gone rendering my workaround unusable.



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

Bug#923655: Provide db entry for the Pine A64 LTS board

[Vagrant Cascadian]

On 2019-03-03, Heinrich Schuchardt wrote:
> The Pine A64 LTS is supported in Linux upstream since v4.20 and the
> relevant device tree is contained in package linux-image-4.20.0-trunk-arm64
> (4.20-1~exp1).

The device-tree for Pine A64 LTS might be a good candidate to backport
to 4.19.x and get it working for buster; the SoC support and most or all
drivers may already be present in 4.19.x.

live well,
  vagrant


signature.asc
Description: PGP signature

Bug#923696: lintian: Bad examples in Lintian::Tutorial::TestSuite

[Felix Lechner]

Hi Xavier,

On Sun, Mar 3, 2019 at 2:27 PM Xavier Guimard  wrote:

>
> To launch part of the tests, Lintian::Tutorial::Testsuite proposes to
> use either:
>
>   $ debian/rules runtests onlyrun=tag:$tag
>   $ t/bin/runtests --dump-logs -k t debian/test-out tag:$tag
>
> None of these examples work (all test launched or error). Looking at
> source code, I ran with success:
>
>   $ t/bin/runtests --unattended --work-dir=debian/test-out --onlyrun
> tag:$tag t
>
> Same for other examples ($check,...)
>

Thanks for reporting this. I saw your note on #debian-qa, but you were gone
when I got there. I will work on the documentation very soon.

In most cases, you should be able to drop the work-dir and and the test
base 't', like so

t/bin/runtests --onlyrun=tag:$tag

-k will run all selected tests even if the code quality scripts or the
internal harness tests have failed.

--unattended will never prompt for user input, for example to offer to
re-calibrate tests when new tags appeared or some disappeared.

Bug#921624: kmail: Crash during/after filtering inbox, probably related to Qt WebEngine integration

[Sandro Knauß]

Control: forwarded -1 https://bugs.kde.org/404052

Hey,

it does not looks like a packaging issue so far. It may a duplicate of 
#923490.

hefee

--
On Donnerstag, 7. Februar 2019 13:08:17 CET Martin Steigerwald wrote:
> Dear Sandro,
> 
> Better late than never, I managed to report the KMail crashes during/after
> filtering inbox upstream. See:
> 
> Bug 404052 - Crash during/after filtering inbox, probably related to Qt
> WebEngine integration https://bugs.kde.org/404052
> 
> This may or may not be a packaging related issue.
> 
> Thanks,
> Martin

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

Bug#893912: stretch-backports doesnt help either

[living proof]

for as well stretch-backports does not fix the problem

Bug#923562: kmail: fails to copy sent email to sent mail folder

[Sandro Knauß]

Control: tags -1 +moreinfo

Hey,

for what resource this happens? maildir, imap, google imap?
did you checked akonadiconsole also logging tab may be interessed.

hefee

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

Bug#922270: kmail - "Name" column in message window can not made smaller

[Sandro Knauß]

Control: tags -1 +moreinfo

Hey Hans,

> I got into a minor problem. In the window (where the "Kmail-folder",
> "Inbox", "Sent" etc. folders appear), it is not possible, to resize the
> firs column (called "name").
> 
> The first column is very, very, very large and on the buttom of the window
> there appeared a slider.

I can resize with the mouse by slide to the far right and than use the mouse  
when the cursor changes to the "change size cursor" and than keep the left 
mouse button pressend and move the mouse to the left. Than the mouse jumps 
back to the first position but keep moving to the left.  That makes the name 
column smaller and smaller. Yes it looks visually completly broken ;D

hefee

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

Bug#923606: beancount: FTBFS randomly (gpg-related race condition)

[Stefano Zacchiroli]

severity -1 important
thanks

Hi Santiago,

On Sat, Mar 02, 2019 at 06:03:10PM +, Santiago Vila wrote:
> I tried to build this package in buster but it failed:
> [...]
> try:
> >   os.unlink(entry.name, dir_fd=topfd)
> E   FileNotFoundError: [Errno 2] No such file or directory: 
> 'S.gpg-agent.browser'
[...]
> The above is just how the build ends and not necessarily the most relevant 
> part,
> so I've put a bunch of failed build logs here:
> 
> https://people.debian.org/~sanvila/build-logs/beancount/
> 
> The failure happens randomly. Sometimes it happens, sometimes it does not,
> but the failure rate is so high that we can't really say that the package
> "builds from source and without failure".

thanks for this bug report, I had no idea about this flakiness in the
build.

> This failure is similar to another one which I reported before in another 
> package:
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906335
> 
> but I'm not really sure if that helps.
> 
> If you need a test machine where this happens almost all the time, please 
> contact me
> privately and I will gladly offer ssh access.

Similarly to the other bug you mention, I think the incidence of this
FTBFS is low... at least elsewhere w.r.t. your build environment. I've
personal never witnessed this, and I'm aware of a bunch of other people
who have built from scratch without issues. More to the point,
reproducible building the package is working fine on at least four
architectures, including the one you are testing on:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/beancount.html

On that basis, I'm lowering the priority to important.

Still, I think the bug should be fixed, and I will do so (most likely
ignoring the rm error, as that means no cleanup is needed). But I will
not necessarily do this in time for the next release.

Cheers.
-- 
Stefano Zacchiroli . z...@upsilon.cc . upsilon.cc/zack . . o . . . o . o
Computer Science Professor . CTO Software Heritage . . . . . o . . . o o
Former Debian Project Leader & OSI Board Director  . . . o o o . . . o .
« the first rule of tautology club is the first rule of tautology club »


signature.asc
Description: PGP signature

Bug#914897: tech-ctte: Should debootstrap disable merged /usr by default?

[Philip Hands]

Didier 'OdyX' Raboud  writes:

> Dear Technical Committee members,
>
> I call for vote immediately on the following resolution.
>
> === Resolution ===
>
> The Technical Committee resolves to decline to override the debootstrap
> maintainers.
>
> Furthermore, using its §6.1.5 "Offering advice" power, the Technical
> Committee considers that the desirable solution at the time of `bullseye` is:
>
> * W: `weak`: both directory schemes are allowed, but packages should only
>  be built on hosts with classical directory schemes (or in such
>  chroots)
>
> * M: `middle`: both directory schemes are allowed, and packages (including
>official packages) can be built on hosts with either classical
>or "merged `/usr`" directory schemes
>
> * H: `hard`: both directory schemes are allowed, but packages should only
>  be built on hosts with "merged `/usr`" directory schemes (or in
>  such chroots)
>
> * FD: Further Discussion
>
> === End Resolution ===

I vote:

  H > M > FD > W

Cheers, Phil.
-- 
|)|  Philip Hands  [+44 (0)20 8530 9560]  HANDS.COM Ltd.
|-|  http://www.hands.com/http://ftp.uk.debian.org/
|(|  Hugo-Klemm-Strasse 34,   21075 Hamburg,GERMANY


signature.asc
Description: PGP signature

Bug#923559: systemd-udevd: writes to kernel log

[Thorsten Glaser]

tags 923559 + patch
thanks

On Sat, 2 Mar 2019, Michael Biebl wrote:

> The only other option you have is to disable logging in udevd completely.

How about the attached patch? I’ve verified it, as since recently
(re)starting udev always produces an uninteresting/tautologic warning:

Mar  3 23:20:49 tglase vmunix: [8820159.381621] systemd-udevd[14028]: Network 
interface NamePolicy= disabled on kernel command line, ignoring.
Mar  3 23:20:54 tglase sudo:   tglase : TTY=pts/3 ; 
PWD=/var/cache/pbuilder/result-dpo ; USER=root ; COMMAND=/usr/bin/dpkg -i 
udev_241-1.1_x32.deb
Mar  3 23:20:54 tglase sudo: pam_unix(sudo:session): session opened for user 
root by tglase(uid=0)
Mar  3 23:21:00 tglase systemd-udevd[14168]: Network interface NamePolicy= 
disabled on kernel command line, ignoring.

(Before this I hacked /var/lib/dpkg/status to set all versions from 241-1
to 241-1.1 so this dpkg command could succeed.)

> >>> This is expected behaviour. udevd uses the journal for logging and falls
> >>> back to log to the kernel ring buffer if the journal is not available.
> >
> > Make it fall back to syslog first, then, please.

> We won't develop and maintain a downstream patch for that and I'm pretty
> sure upstream is not interested in that either since they have a
> perfectly working solution for that.

Could you please, at least, forward the attached patch upstream,
if you’re not willing to maintain it downstream? It turns out
that the fix was really trivial. (I think it goes without saying
that it’s better if I don’t interact directly with upstream.)

Thanks,
//mirabilos
-- 
[17:15:07] Lukas Degener: Kleines Asterix-Latinum für Softwaretechniker:
   veni, vidi, fixi(t) ;-)diff -Nru systemd-241/debian/changelog systemd-241/debian/changelog
--- systemd-241/debian/changelog2019-02-22 00:10:15.0 +0100
+++ systemd-241/debian/changelog2019-03-03 23:00:57.0 +0100
@@ -1,3 +1,10 @@
+systemd (241-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add patch to prefer syslog over kmsg for auto logging. (Closes: #923559)
+
+ -- Thorsten Glaser   Sun, 03 Mar 2019 23:00:57 +0100
+
 systemd (241-1) unstable; urgency=medium
 
   [ Adam Borowski ]
diff -Nru 
systemd-241/debian/patches/debian/Use-syslog-for-AUTO-logging-before-klog.patch 
systemd-241/debian/patches/debian/Use-syslog-for-AUTO-logging-before-klog.patch
--- 
systemd-241/debian/patches/debian/Use-syslog-for-AUTO-logging-before-klog.patch 
1970-01-01 01:00:00.0 +0100
+++ 
systemd-241/debian/patches/debian/Use-syslog-for-AUTO-logging-before-klog.patch 
2019-03-03 23:00:54.0 +0100
@@ -0,0 +1,32 @@
+# DP: make LOG_TARGET_AUTO fall back to syslog before kernel message buffer
+# DP: fixes #923559
+
+--- a/src/basic/log.c
 b/src/basic/log.c
+@@ -257,6 +257,7 @@ int log_open(void) {
+ 
+ if (!prohibit_ipc &&
+ IN_SET(log_target, LOG_TARGET_SYSLOG_OR_KMSG,
++   LOG_TARGET_AUTO,
+LOG_TARGET_SYSLOG)) {
+ r = log_open_syslog();
+ if (r >= 0) {
+@@ -603,6 +604,7 @@ int log_dispatch_internal(
+ }
+ 
+ if (IN_SET(log_target, LOG_TARGET_SYSLOG_OR_KMSG,
++   LOG_TARGET_AUTO,
+LOG_TARGET_SYSLOG)) {
+ 
+ k = write_to_syslog(level, error, file, line, func, 
buffer);
+--- a/src/basic/log.h
 b/src/basic/log.h
+@@ -30,7 +30,7 @@ typedef enum LogTarget{
+ LOG_TARGET_JOURNAL_OR_KMSG,
+ LOG_TARGET_SYSLOG,
+ LOG_TARGET_SYSLOG_OR_KMSG,
+-LOG_TARGET_AUTO, /* console if stderr is tty, JOURNAL_OR_KMSG 
otherwise */
++LOG_TARGET_AUTO, /* console if stderr is tty, journal or syslog or 
kmsg otherwise */
+ LOG_TARGET_NULL,
+ _LOG_TARGET_MAX,
+ _LOG_TARGET_INVALID = -1
diff -Nru systemd-241/debian/patches/series systemd-241/debian/patches/series
--- systemd-241/debian/patches/series   2019-02-22 00:10:15.0 +0100
+++ systemd-241/debian/patches/series   2019-03-03 22:58:11.0 +0100
@@ -21,3 +21,4 @@
 debian/Add-env-variable-for-machine-ID-path.patch
 debian/Revert-udev-rules-Permission-changes-for-dev-dri-renderD.patch
 debian/Drop-seccomp-system-call-filter-for-udev.patch
+debian/Use-syslog-for-AUTO-logging-before-klog.patch

Bug#923292: kmail randomly crashes when closing windows

[Sandro Knauß]

Control: tags -1 +moreinfo

Please start kmail from console and enable Qt logging before like I described 
at #923288. Please attach a backtrace of the crash, so we can analyse what is 
going on.

hefee

On Montag, 25. Februar 2019 23:24:54 CET Juha Jäykkä wrote:
> Package: kmail
> Version: 4:18.08.3-1
> Severity: normal
> 
> Dear Maintainer,
> 
> I do not like the "message preview pane", so I open each message in a
> separate window to read them. Sometimes, and as far as I can tell, at
> random, kmail will crash with a SIGSEGV when such message window OR compose
> message window is closed. It does not matter what causes the window to
> close, even sending a message sometimes causes a crash.
> 
> Cheers,
> Juha
> 
> -- System Information:
> Debian Release: buster/sid
>   APT prefers unstable-debug
>   APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1,
> 'experimental') Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.18.0-2-amd64 (SMP w/2 CPU cores)
> Kernel taint flags: TAINT_WARN
> Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored:
> LC_ALL set to en_GB.UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) (ignored:
> LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages kmail depends on:
> ii  akonadi-server   4:18.08.3-4
> ii  kdepim-runtime   4:18.08.3-1
> ii  kio  5.54.1-1
> ii  libc62.28-7
> ii  libgcc1  1:8.2.0-21
> ii  libgpgmepp6  1.12.0-6
> ii  libkf5akonadiagentbase5  4:18.08.3-4
> ii  libkf5akonadicontact54:18.08.3-1
> ii  libkf5akonadicore5abi2   4:18.08.3-4
> ii  libkf5akonadimime5   4:18.08.3-1
> ii  libkf5akonadisearch-bin  4:18.08.3-1
> ii  libkf5akonadisearch-plugins  4:18.08.3-1
> ii  libkf5akonadisearchdebug54:18.08.3-1
> ii  libkf5akonadisearchpim5  4:18.08.3-1
> ii  libkf5akonadiwidgets5abi14:18.08.3-4
> ii  libkf5bookmarks5 5.54.0-1
> ii  libkf5calendarcore5abi2  4:18.08.3-1
> ii  libkf5calendarutils5 4:18.08.3-2
> ii  libkf5codecs55.54.0-1
> ii  libkf5completion55.54.0-1
> ii  libkf5configcore55.54.0-1
> ii  libkf5configgui5 5.54.0-1
> ii  libkf5configwidgets5 5.54.0-1
> ii  libkf5contacts5  4:18.08.3-1
> ii  libkf5coreaddons55.54.0-1
> ii  libkf5crash5 5.54.0-1
> ii  libkf5dbusaddons55.54.0-1
> ii  libkf5followupreminder5  4:18.08.3-2
> ii  libkf5grantleetheme-plugins  18.08.3-1
> ii  libkf5gravatar5abi2  4:18.08.3-1
> ii  libkf5guiaddons5 5.54.0-1
> ii  libkf5i18n5  5.54.0-1
> ii  libkf5iconthemes55.54.0-1
> ii  libkf5identitymanagement518.08.3-2
> ii  libkf5itemmodels55.54.0-1
> ii  libkf5itemviews5 5.54.0-1
> ii  libkf5jobwidgets55.54.0-1
> ii  libkf5kcmutils5  5.54.0-1
> ii  libkf5kiocore5   5.54.1-1
> ii  libkf5kiofilewidgets55.54.1-1
> ii  libkf5kiowidgets55.54.1-1
> ii  libkf5kontactinterface5  18.08.3-1
> ii  libkf5ksieveui5  4:18.08.3-2
> ii  libkf5libkdepim-plugins  4:18.08.3-2
> ii  libkf5libkdepim5 4:18.08.3-2
> ii  libkf5libkdepimakonadi5  4:18.08.3-2
> ii  libkf5libkleo5   4:18.08.3-2
> ii  libkf5mailcommon5abi24:18.08.3-2
> ii  libkf5mailtransport5 18.08.3-2
> ii  libkf5mailtransportakonadi5  18.08.3-2
> ii  libkf5messagecomposer5abi1   4:18.08.3-1
> ii  libkf5messagecore5abi1   4:18.08.3-1
> ii  libkf5messagelist5abi1   4:18.08.3-1
> ii  libkf5messageviewer5abi1 4:18.08.3-1
> ii  libkf5mime5abi1  18.08.3-1
> ii  libkf5mimetreeparser5abi14:18.08.3-1
> ii  libkf5notifications5 5.54.0-1
> ii  libkf5notifyconfig5  5.54.0-1
> ii  libkf5parts5 5.54.0-1
> ii  libkf5pimcommon5abi2 4:18.08.3-2
> ii  libkf5pimcommonakonadi5abi1  4:18.08.3-2
> ii  libkf5pimtextedit5abi2   18.08.3-1
> ii  libkf5sendlater5 4:18.08.3-2
> ii  libkf5service-bin5.54.0-1
> ii  libkf5service5   5.54.0-1
> ii  libkf5sonnetui5  5.54.0-1
> ii  libkf5templateparser54:18.08.3-1
> ii  libkf5textwidgets5   5.54.0-1
> ii  libkf5tnef5  4:18.08.3-1
> ii  libkf5wallet-bin 5.54.0-1
> ii  libkf5wallet55.54.0-1
> ii  libkf5webengineviewer5abi1   4:18.08.3-1
> ii  libkf5widgetsaddons5 5.54.0-1
> ii  libkf5windowsystem5  5.54.0-1
> ii  libkf5xmlgui55.54.0-1
> ii  libqgpgme7   1.12.0-6
> ii  libqt5core5a 5.11.3+dfsg-5
> ii  libqt5dbus5  5.11.3+dfsg-5
> ii  libqt5gui5   5.11.3+dfsg-5
> ii  libqt5network5   5.11.3+dfsg-5
> ii  libqt5widgets

Bug#893912: im affected as well on debian stretch 9

[living proof]

[2.574742] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin
[2.575137] bluetooth hci0: firmware: failed to load 
rtl_bt/rtl8821a_config.bin (-2)
[2.575143] bluetooth hci0: Direct firmware load for 
rtl_bt/rtl8821a_config.bin failed with error -2
[2.575145] Bluetooth: hci0: Failed to load rtl_bt/rtl8821a_config.bin

copying rtl8723a_config.bin from https://github.com/lwfinger/rtl8723au_bt/ to  
/lib/firmware/rtl_bt/ does NOT solve the issue. You are actually pointing to a 
config file for a completly different device.

We are using the rtl8821a this config file is for the rtl8723au_bt...

Bug#923697: imagemagick-6.q16: evaluate-sequence on different size images: crash in Buster, fine in Stretch

[Gert]

Package: imagemagick-6.q16
Version: 8:6.9.10.23+dfsg-2
Severity: normal

Dear Maintainer,
When I take 2 images of differing size, and run the following:

$ convert-im6.q16 small.pbm large.pbm -evaluate-sequence mean -verbose info:

I get an error+crash.
It only seems to happen when the small image is specified first.
What the error is, can vary depending on the width difference.
Some that I have seen:

convert: malloc.c:4028: _int_malloc: Assertion `(unsigned long) (size) >=
(unsigned long) (nb)' failed.
free(): invalid next size (normal)
double free or corruption (!prev)
free(): invalid pointer

I ran 1 image combination (see attachments) in gdb:

$ gdb convert-im6.q16
- - - 8< - - -
Reading symbols from convert-im6.q16...Reading symbols from
/usr/lib/debug/.build-
id/2b/5e71c569934692f8816b4709c5f9f068648044.debug...done.
done.
(gdb) set pagination 0
(gdb) run small.pbm large.pbm -evaluate-sequence mean -verbose info:
Starting program: /usr/bin/convert-im6.q16 small.pbm large.pbm -evaluate-
sequence mean -verbose info:
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
free(): invalid pointer

Program received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
50  ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) quit

It worked fine when I was running Stretch, when I downgrade imagemagick-6.q16
to the Stretch version it still works.
Thank you,
Gert



-- Package-specific info:
ImageMagick program version
---
animate:  ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org
compare:  ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org
convert:  ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org
composite:  ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org
conjure:  ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org
display:  ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org
identify:  ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org
import:  ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org
mogrify:  ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org
montage:  ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org
stream:  ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org

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

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=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8), 
LANGUAGE=nl_NL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages imagemagick-6.q16 depends on:
ii  hicolor-icon-theme 0.17-2
ii  libc6  2.28-7
ii  libmagickcore-6.q16-6  8:6.9.10.23+dfsg-2
ii  libmagickwand-6.q16-6  8:6.9.10.23+dfsg-2

Versions of packages imagemagick-6.q16 recommends:
ii  ghostscript  9.26a~dfsg-2
pn  libmagickcore-6.q16-6-extra  
ii  netpbm   2:10.0-15.3+b2

Versions of packages imagemagick-6.q16 suggests:
pn  autotrace   
pn  cups-bsd | lpr | lprng  
ii  curl7.64.0-1
pn  enscript
ii  ffmpeg  7:4.1.1-1
ii  gimp2.10.8-2
pn  gnuplot 
pn  grads   
pn  graphviz
ii  groff-base  1.22.4-2
pn  hp2xx   
pn  html2ps 
pn  imagemagick-doc 
pn  libwmf-bin  
ii  mplayer 2:1.3.0-8+b4
pn  povray  
pn  radiance
ii  sane-utils  1.0.27-3.1
pn  texlive-base-bin
pn  transfig
pn  ufraw-batch 
ii  xdg-utils   1.1.3-1

-- no debconf information

Bug#923293: kmail: mailbox contents displayed wrong

[Sandro Knauß]

Control: tags -1 +moreinfo

Please use the Notification Monitor and Job tracker tab in akonadiconsole to 
find out more information about what is going on. You have to enabled both 
before the issue happen, so see if the needed jobs/notifications are triggerd.

In the end of this, it will not be a Debian issue, so you need to to 
report the bug upstream: https://bugs.kde.org. Please leave a note about the 
concrete link to the upstream bugreport, so we can track the state inhere.

hefee

--

On Montag, 25. Februar 2019 23:22:48 CET Juha Jäykkä wrote:
> Package: kmail
> Version: 4:18.08.3-1
> Severity: normal
> 
> Dear Maintainer,
> 
> kmail will often show mailbox contents wrong: it will show the correct
> number of unread messages in the folders pane, but the actual messages
> displayed do not show all those unread messages (presumably not all read
> messages are shown either but not sure).
> 
> Checking the akonadi status from akonadiconsole shows all the messages,
> including the ones kmail does not show, so kmail somehow gets out of sync
> with akonadi.
> 
> This can be worked around by restarting kmail, but given the frequency that
> this happens, several times a day, it makes kmail's usability quite
> abysmal.


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

Bug#923696: lintian: Bad examples in Lintian::Tutorial::TestSuite

[Xavier Guimard]

Package: lintian
Version: 2.9.1
Severity: minor

Hi all,

To launch part of the tests, Lintian::Tutorial::Testsuite proposes to
use either:

  $ debian/rules runtests onlyrun=tag:$tag
  $ t/bin/runtests --dump-logs -k t debian/test-out tag:$tag

None of these examples work (all test launched or error). Looking at
source code, I ran with success:

  $ t/bin/runtests --unattended --work-dir=debian/test-out --onlyrun tag:$tag t

Same for other examples ($check,...)

Cheers,
Xavier

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

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

Versions of packages lintian depends on:
ii  binutils   2.31.1-11
ii  bzip2  1.0.6-9
ii  diffstat   1.62-1
ii  dpkg   1.19.5
ii  dpkg-dev   1.19.5
ii  file   1:5.35-2
ii  gettext0.19.8.1-9
ii  gpg2.2.12-1
ii  intltool-debian0.35.0+20060710.5
ii  libapt-pkg-perl0.1.34+b1
ii  libarchive-zip-perl1.64-1
ii  libcapture-tiny-perl   0.48-1
ii  libcgi-pm-perl 4.40-1
ii  libclass-accessor-perl 0.51-1
ii  libclone-perl  0.41-1+b1
ii  libdigest-sha-perl 6.02-1+b1
ii  libdpkg-perl   1.19.5
ii  libemail-valid-perl1.202-1
ii  libfile-basedir-perl   0.08-1
ii  libio-async-perl   0.72-1
ii  libipc-run-perl20180523.0-1
ii  liblist-moreutils-perl 0.416-1+b4
ii  libparse-debianchangelog-perl  1.2.0-13
ii  libpath-tiny-perl  0.108-1
ii  libtext-levenshtein-perl   0.13-1
ii  libtimedate-perl   2.3000-2
ii  libtry-tiny-perl   0.30-1
ii  liburi-perl1.76-1
ii  libxml-simple-perl 2.25-1
ii  libyaml-libyaml-perl   0.76+repack-1
ii  man-db 2.8.5-2
ii  patchutils 0.3.4-2
ii  perl   5.28.1-4
ii  t1utils1.41-3
ii  xz-utils   5.2.4-1

Versions of packages lintian recommends:
ii  libperlio-gzip-perl  0.19-1+b5

Versions of packages lintian suggests:
ii  binutils-multiarch 2.31.1-11
ii  libhtml-parser-perl3.72-3+b3
ii  libtext-template-perl  1.54-1

-- no debconf information

Bug#923695: libczmq-dev: pkg-config --cflags libczmq.pc fails without uuid-dev and libsystemd-dev installed

[Luca Boccassi]

Package: libczmq-dev
Version: 4.2.0-1
Severity: grave
Justification: rdeps FTBFS due to missing dependencies and pkg-config

libczmq.pc lists the dependencies for static linking in
Requires.private, which means pkg-config --cflags libczmq will fail if
these dependencies (uuid-dev and libsystemd-dev [linux-any]) are not
installed.
This will cause reverse dependencies to fail to build in minimal chroot
that pull in only required dependencies.

The fix is very simple, just add uuid-dev and libsystemd-dev [linux-
any] to the list of libczmq-dev's dependencies.

-- 
Kind regards,
Luca Boccassi

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

Bug#923291: kmail: syncing inbox(es) never finishes

[Sandro Knauß]

Control: tags -1 +moreinfo
Control: reassign -1 akonadi-server 4:18.08.3-4
Control: affects -1 kmail

Hey Juha,

thanks for giving input about the current state of kmail. Unfortunately these 
are not enough information to tackle down the issue.

Your issue sounds that  a Akonadi Resource is stuck. Please use akonadiconsole 
for debugging. At frist enable logging at the logging tab.

go to the Agent tab select the resource that got stuck and select "Show task 
list" and print the output. The queues should all be empty if the sync was 
successful.

We may properly to distinguish the issue for google, as goolge's imap 
implementation is wired, so let's focus on opensource mailserver dovecot first.

> Steps to reprocude: start kmail, let it run for a while, checking inboxes
> either manually or letting the automatic interval check do it for you. In
> less than 15 minutes at least one of the inboxes gets stuck.

I can't reproduce it on my setup. And I use 5 different accounts dovecot and 
kolab.

Do you have stable inet for your tests? If inet went away while syncing, than 
sometime Akonadi don't recover. Also putting my laptop to sleep while 
currently if syncing breaks Akonadi sometimes.

But in the end of this, it will not be a Debian issue, so you need to to 
report the bug upstream: https://bugs.kde.org. Please leave a note about the 
concrete link to the upstream bugreport, so we can track the state inhere.

hefee

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

Bug#523979: #523979 atftpd: please add generated content patch

[Reiner Herrmann]

Control: tags -1 + moreinfo - patch

Hi Paul,

I just noticed that you suggested a patch for atftp,
but it is no longer available.
Do you by chance still have the patch and could attach it
to the bug? Otherwise I would suggest to close it.

Kind regards,
  Reiner


signature.asc
Description: PGP signature

Bug#923694: unblock: gnome-documents/3.31.92-1

[Jeremy Bicha]

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

Please unblock package gnome-documents..

The source debdiff is at
https://bicha.net/gnome-documents-buster-unblock.debdiff Sorry for the
size. (Some of the changes were in unstable for several weeks but were
held up the s390x situation, mentioned below.)

gnome-books has been split from gnome-documents. This allows for a
user to install just one of the apps if they want instead of being
forced to install or uninstall both In particular, AppStream clients
such as the GNOME Software app assume that there is only one app per
primary AppStream metadata file and the UI did not correctly handle
installing or uninstalling either of these apps. (It wouldn't indicate
that install/uninstall actions affect both apps.)

This was delayed because we had to update debian/copyright to fix a
gnome-books RC bug that was added by FTP Masters when this NEW source
package was accepted into Debian. gnome-books & gnome-documents were
uploaded before the soft freeze.

There will be one more upload (3.32.0) that we will want for Buster
since 3.31.90 is a pre-release. 3.32.0 is expected in about 9 days.

gnome-documents is affected by the gjs removal from s390x so we may
need manual hinting to ensure that the package migrates to Testing.
There is a very long discussion at https://bugs.debian.org/906016
about the s390x issue.

The corresponding gnome-books unblock bug is https://bugs.debian.org/923693

unblock gnome-documents/3.31.92-1

Thanks,
Jeremy Bicha

Bug#923693: unblock: gnome-books/3.31.90-3

[Jeremy Bicha]

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

Please unblock package gnome-books.

gnome-books has been split from gnome-documents. This allows for a
user to install just one of the apps if they want instead of being
forced to install or uninstall both In particular, AppStream clients
such as the GNOME Software app assume that there is only one app per
primary AppStream metadata file and the UI did not correctly handle
installing or uninstalling either of these apps. (It wouldn't indicate
that install/uninstall actions affect both apps.)

I don't think a source debdiff will be very helpful here since many of
the changes are renaming gnome-documents to gnome-books and removing
code that isn't needed for the gnome-books app. Let me know if you
really want the source debdiff here.

This was delayed because we had to update debian/copyright to fix a RC
bug that was added by FTP Masters when this NEW source package was
accepted into Debian. gnome-books was uploaded before the soft freeze.

There will be one more upload (3.32.0) that we will want for Buster
since 3.31.90 is a pre-release. 3.32.0 is expected in about 9 days.

unblock gnome-books/3.31.90-3

Thanks,
Jeremy Bicha

Bug#923288: kmail does not exit

[Sandro Knauß]

Control: tags -1 +moreinfo

Hey Juha,

thanks for giving input about the current state of kmail. Unfortunately these 
are not enough information to tackle down the issue. Enable logging for Qt:

~/.config/QtProject/qtlogging.ini 
[Rules]
*.warning=true
*.critical=true
*=true
qt.*=false
sonnet.*=false

and start kmail form a konsole. That may gives us the needed information.
After the debug session replace *=true with *=false otherwise your .xsessions-
errors will get big very soon.

is Ctrl+C in konsole enough to stop kmail in that situation?

hefee

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

Bug#900895: kmail: KMail malfunctioning: Red email folders, no emails can be viewed; "Unable to fetch item from backend (collection-1): Unable to contact resource"

[Sandro Knauß]

Control: tags -1 +moreinfo
Control: reassign -1 kdepim-runtime 4:16.04.2-2+b2
Control: forcemerge -1 900957

Thanks for reporting the issue and sorry for not responding for so long time.

The bug is actually in the maildir_resource that is shipped within kdepim-
runtime package, that why reassign the bug. 

It would be super great if you could test your setup with kmail on Debian 
Buster, that is currently in testing. Because kdepim fixed serveral issues for 
maildir resource.

hefee


On Mittwoch, 27. Februar 2019 05:33:12 CET Jens Radloff wrote:
> I recorded another occurrence of this behaviour with the debugger in the
> Akonadi Console. This time, below the output field on the "All" tab, the
> following additional error messages gets displayed:
> 
> --- Quote Beginning ---
> 
> AgentBase(akonadi_maildir_resource_0): Verbindung zum Akonadi-Dienst kann
> nicht hergestellt werden. => Can be translated as "Cannot establish
> connection to Akonadi service"
> NotificationManager::notify ( { Type: "Items" Operation: "Modify" Items: { {
> ID: "32532" RemoteID: "1551182744.R329.punk" Remote Revision: "" Mime Type:
> "message/rfc822" } } Session: "akonadi_maildir_resource_0" Resource:
> "akonadi_maildir_resource_0" Destination Resource: "" Parent Collection:
> "9" Parent Destination Collection: "-1" Parts: "QSet(PLD:HEAD, PLD:RFC822,
> PLD:ENVELOPE)" Added Flags: "QSet()" Removed Flags: "QSet()" Added Tags:
> "QSet()" Removed Tags: "QSet()" } )
> NotificationManager::notify ( { Type: "Items" Operation: "Modify" Items: { {
> ID: "32536" RemoteID: "1551196645.R430.punk:2,S" Remote Revision: "" Mime
> Type: "message/rfc822" } } Session: "akonadi_maildir_resource_0" Resource:
> "akonadi_maildir_resource_0" Destination Resource: "" Parent Collection:
> "7" Parent Destination Collection: "-1" Parts: "QSet(PLD:HEAD, PLD:RFC822,
> PLD:ENVELOPE)" Added Flags: "QSet()" Removed Flags: "QSet()" Added Tags:
> "QSet()" Removed Tags: "QSet()" }
> 
> -- Quote End 
> 
> Then I restarted Akonadi with "akonadictl restart" in a command shell window
> and did not close this window, but provoked the behavior again. The console
> window returned the following debugging information about the time when the
> behaviour occurred again:
> 
> --- Quote Beginning ---
> 
> akonadicore_log: Invalid command, the world is going to end!
> QIODevice::read (QLocalSocket): device not open
> akonadi_maildir_resource: /build/akonadi-EKz4jf/akonadi-16.04.3/src/private/
> protocol.cpp:1590: Akonadi::Protocol::HelloResponse::HelloResponse(const
> Akonadi::Protocol::Command&): Zusicherung »d_func()->commandType ==
> Command::Invalid || d_func()->commandType == (Command::Hello |
> Command::_ResponseBit)« nicht erfüllt.
> void Akonadi::Server::NotificationSource::serviceUnregistered(const
> QString&) Notification source "akonadi_maildir_resource_0_4955_mdI52n" now
> serving: () ProcessControl: Application /usr/bin/akonadi_maildir_resource
> stopped unexpectedly ( "Der Prozess ist abgestürzt" ) => Can be translated
> as "The process has crashed"
> Application '/usr/bin/akonadi_maildir_resource' crashed too often. Giving
> up! Shutting down "/subscriber/akonadi_maildir_resource_0_4955_mdI52n" ...
> Lost connection to resource
> "org.freedesktop.Akonadi.Resource.akonadi_maildir_resource_0" , discarding
> cached interface
> Shutting down "akonadi_maildir_resource_0" ...
> Shutting down "0x55b505adb7b0" ...
> 
> --- Quote End ---
> 
> This bug issue is a duplicate of
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900957



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

Bug#923692: jed-common: Switch to snapshots?

[Chris Chiappa]

Package: jed-common
Version: 1:0.99.20pre135-1
Severity: wishlist

jed 0.99.19 was released over 9 years ago.  Regular 0.99.20 "pre"
snapshots have been released over the ensueing time period.  Maybe
it's worth considering tracking snapshots if real releases don't
really happen anymore?  As an experiment, I dropped the debian/
directory from the current jed package into 0.99.20pre135 and
'debuild' worked without a hitch.

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

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

Versions of packages jed-common depends on:
ii  slsh  2.3.2-2

Versions of packages jed-common recommends:
ii  jed   1:0.99.20pre135-1
ii  xjed  1:0.99.20pre135-1

Versions of packages jed-common suggests:
ii  emacs-gtk [info-browser]  1:26.1+1-3.2
ii  info [info-browser]   6.5.0.dfsg.1-4+b1
ii  jed [info-browser]1:0.99.20pre135-1
ii  jed-extra [info-browser]  2.5.7-2
ii  xjed [info-browser]   1:0.99.20pre135-1

-- no debconf information

Bug#923096: consider porting to Breezy

[Vagrant Cascadian]

On 2019-02-24, Jelmer Vernooij wrote:
> bzr has long been dormant upstream. It will be replaced in Debian (in
> buster+1) with Breezy (www.breezy-vcs.org), which is actively
> maintained and has a Python 3 port. Breezy has a command-line that is
> backwards compatible with Bazaar.
>
> Please consider porting git-remote-bzr to the 'breezy' Python module
> instead of using Bazaar's 'bzrlib'. Most of the porting process should
> be a matter of running s/bzrlib/breezy/ on your code.

Given that git-remote-bzr provides a git frontend to a bzr repository,
I'm not sure the backwards compatible command-line interface sounds too
exciting... :)

I don't personally work with many bzr repositorys anymore, so I would be
inclined to orphan git-remote-bzr to someone with a more vested interest
if bzr/bzrlib was dropped for buster+1.

Upstream on git-remote-bzr hasn't been terribly active either:

  https://github.com/felipec/git-remote-bzr

Though it's largely continued to work, which isn't a bad sign.


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#922965: Bug#923220: DFSG compliance concerns

[Russ Allbery]

Philipp Meisberger  writes:

> What about the java-package and DFSG? It is very similar to my package
> and also does not build a .deb from source but is contained in Debian.

java-package is not in Debian.  It's in the contrib distribution, which is
a set of packages provided alongside Debian for working with non-free
software.

This sort of upstream repackager, if it itself is released under a free
software license, is in general acceptable for contrib if someone is
willing to sponsor it.  (I haven't looked at the details of this specific
package.)

-- 
Russ Allbery (r...@debian.org)   

Bug#923691: RM: rssh -- ROM; orphaned upstream, flawed security model

[Russ Allbery]

Package: ftp.debian.org
Severity: normal

rssh has been orphaned upstream and has had a chain of security
vulnerabilities in stable that indicate that its security model
is fundamentally unsound.  Attempting to do whitelist filtering of
the arguments of various programs to protect against them running
arbitrary code is proving too challenging in practice to safely
maintain.

Upstream now recommends against further use of the program, and we
should follow that advice.

Please remove rssh from both unstable and testing so that it is not
released with the next stable release of Debian.

I'll continue to attempt to provide security support for the lifetime
of the current Debian stable.

Bug#922273: [hexchat] Thread 1 closes for missing raise.c

[Synthea]

I got more informations while putting my hands randomly on hexchat.
This bug happens if the following conditions are satisfied:
1- Hexchat tries to connect to a server, gets a DNS answer, tries to
contact the server ip and the server won't answer, but the connection
attempt won't end either
2- The connection attempt is terminated manually (Server > Disconnect)
3- Another server is chosen and the connection is successful
4- (Not certain but seems in 90% of cases to be related) Hexchat
receives a message which triggers a dbus notification
Something makes me suspect that in this particular situation the
notification method isn't handled correctly, resulting in dbus closing
the connection and libdbus-glib killing hexchat

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

Bug#923619: coreutils: FTBFS on hppa - Unknown error 252

[John David Anglin]

On 2019-03-03 3:47 p.m., Helge Deller wrote:
> On 03.03.19 19:53, Helge Deller wrote:
>> On 03.03.19 00:45, John David Anglin wrote:
>>> The error doesn't occur if I do a simple "configure
>>> --prefix=somewhere", make and make install.
> fakeroot is the culprit. 
Makes sense.  I wonder why we didn't see this before.

-- 
John David Anglin  dave.ang...@bell.net

Bug#923690: asterisk: CVE-2019-7251: Remote crash vulnerability with SDP protocol violation

[Salvatore Bonaccorso]

Source: asterisk
Version: 1:16.2.0~dfsg-1
Severity: important
Tags: security upstream

Hi,

The following vulnerability was published for asterisk.

CVE-2019-7251[0]:
Remote crash vulnerability with SDP protocol violation

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-7251
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-7251
[1] https://downloads.asterisk.org/pub/security/AST-2019-001.html

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#923490: kmail: random segfaults while idle

[Sandro Knauß]

Control: reassign -1 qtwebengine 5.11.3+dfsg-2
Control: affects -1 kmail
Control: retitle -1 QtWebEnigne make kmail random segfault while idle

The complete backtrace looks not to be complete, as I don't see any reference 
to any libkf5X nor to kmail. For me it looks like an issue in qtwebegine, 
that's why I reassign it to qtwebengine.

hefee

On Donnerstag, 28. Februar 2019 23:15:06 CET Juha Jäykkä wrote:
> Package: kmail
> Version: 4:18.08.3-1
> Severity: important
> 
> Dear Maintainer,
> 
> Kmail sometimes sigsegvs while (seemingly) idle. Needless to say this
> seriously degrades its usability. I think this has only ever happened while
> moving the mouse pointer across the window. Just moving, not clicking
> anything, not using mouse scroll wheel, just moving the pointer, not even
> stopping while kmail window is focused, so tooltip texts etc should not be
> activating.
> 
> Backtrace follows.
> 
> Application: KMail (kmail), signal: Segmentation fault
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> [Current thread is 1 (Thread 0x7f7c358dbf00 (LWP 7560))]
> 
> Thread 39 (Thread 0x7f7b44bec700 (LWP 9712)):
> #0  0x7f7c4afc63a9 in futex_reltimed_wait_cancelable (private=0,
> reltime=0x7f7b44beb400, expected=0, futex_word=0x7f7b44beb5e8) at
> ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1  0x7f7c4afc63a9 in
> __pthread_cond_wait_common (abstime=0x7f7b44beb4a0, mutex=0x7f7b44beb598,
> cond=0x7f7b44beb5c0) at pthread_cond_wait.c:533 #2  0x7f7c4afc63a9 in
> __pthread_cond_timedwait (cond=0x7f7b44beb5c0, mutex=0x7f7b44beb598,
> abstime=0x7f7b44beb4a0) at pthread_cond_wait.c:667 #3  0x7f7c4480fa37
> in base::ConditionVariable::TimedWait(base::TimeDelta const&) () at
> /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4  0x7f7c4481230a
> in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () at
> /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5  0x7f7c448123f2
> in base::WaitableEvent::TimedWait(base::TimeDelta const&) () at
> /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6  0x7f7c44816981
> in
> base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*
> ) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 
> 0x7f7c44817c7f in base::internal::SchedulerWorker::Thread::ThreadMain()
> () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 
> 0x7f7c44820c81 in base::(anonymous namespace)::ThreadFunc(void*) () at
> /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9  0x7f7c4afbffa3
> in start_thread (arg=) at pthread_create.c:486 #10
> 0x7f7c4d78680f in clone () at
> ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
> 
> Thread 38 (Thread 0x7f7b453ed700 (LWP 9711)):
> #0  0x7f7c4afc63a9 in futex_reltimed_wait_cancelable (private=0,
> reltime=0x7f7b453ec400, expected=0, futex_word=0x7f7b453ec5e8) at
> ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1  0x7f7c4afc63a9 in
> __pthread_cond_wait_common (abstime=0x7f7b453ec4a0, mutex=0x7f7b453ec598,
> cond=0x7f7b453ec5c0) at pthread_cond_wait.c:533 #2  0x7f7c4afc63a9 in
> __pthread_cond_timedwait (cond=0x7f7b453ec5c0, mutex=0x7f7b453ec598,
> abstime=0x7f7b453ec4a0) at pthread_cond_wait.c:667 #3  0x7f7c4480fa37
> in base::ConditionVariable::TimedWait(base::TimeDelta const&) () at
> /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4  0x7f7c4481230a
> in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () at
> /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5  0x7f7c448123f2
> in base::WaitableEvent::TimedWait(base::TimeDelta const&) () at
> /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6  0x7f7c44816981
> in
> base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*
> ) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 
> 0x7f7c44817e61 in base::internal::SchedulerWorker::Thread::ThreadMain()
> () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 
> 0x7f7c44820c81 in base::(anonymous namespace)::ThreadFunc(void*) () at
> /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9  0x7f7c4afbffa3
> in start_thread (arg=) at pthread_create.c:486 #10
> 0x7f7c4d78680f in clone () at
> ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
> 
> Thread 37 (Thread 0x7f7b4df11700 (LWP 9710)):
> #0  0x7f7c4afc63a9 in futex_reltimed_wait_cancelable (private=0,
> reltime=0x7f7b4df10400, expected=0, futex_word=0x7f7b4df105e8) at
> ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1  0x7f7c4afc63a9 in
> __pthread_cond_wait_common (abstime=0x7f7b4df104a0, mutex=0x7f7b4df10598,
> cond=0x7f7b4df105c0) at pthread_cond_wait.c:533 #2  0x7f7c4afc63a9 in
> __pthread_cond_timedwait (cond=0x7f7b4df105c0, mutex=0x7f7b4df10598,
> abstime=0x7f7b4df104a0) at pthread_cond_wait.c:667 #3  0x7f7c4480fa37
> in base::ConditionVariable::TimedWait(base::TimeDelta const&) () at
> /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4  0x7f7c4481230a
> in base::WaitableEvent:

Bug#923619: coreutils: FTBFS on hppa - Unknown error 252

[Helge Deller]

On 03.03.19 21:47, Helge Deller wrote:
> fakeroot is the culprit. 
> It uses ENOTSUP and the binary is still old and thus may use 252 for ENOTSUP.

I've just triggered an NMU of fakeroot.
As soon as this finished, building of coreutils should finish without errors.

Helge 

Bug#923689: update to version 1.9.4

[Sylwester Arabas]

Package: libthrust-dev
Version: 1.9.3~10.0.130-2

There's a new version of Thrust available: 1.9.4

BTW, Thrust is still in the non-free, while it's genuinely useful in a
fully open-source context, is licensed under Apache license, is hosted
on github... why not move it to main?

HTH,
Sylwester

Bug#923688: [keepassxc] KeepassXC not showing in the icon bar

[Synthea]

Package: keepassxc
Version: 2.3.4+dfsg.1-1~bpo9+1
Severity: normal
Reproducible: Always

This behaviour was found on plasma. If "Show a system tray icon" and
"Hide window to system tray when minimized" are set, if you minimize
the window the icon in the system tray won't appear and there will be
no means of interacting with keepassxc


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

Debian Release: 9.8
  500 stable-updates  deb.debian.org 
  500 stable  security.debian.org 
  500 stable  repo.skype.com 
  500 stable  dl.google.com 
  500 stable  deb.debian.org 
  500 newstable   deb.i2p2.de 
  100 stretch-backports deb.debian.org 

--- Package information. ---
Depends (Version) | Installed
=-+-=
libargon2-0  (>= 0~20160406~) | 0~20160821-1+b1
libc6   (>= 2.14) | 
libgcrypt20(>= 1.7.0) | 
libqt5core5a   (>= 5.7.0) | 
libqt5dbus5(>= 5.0.2) | 
libqt5gui5 (>= 5.7.0) | 
libqt5network5 (>= 5.0.2) | 
libqt5widgets5(>= 5.6.0~beta) | 
libqt5x11extras5   (>= 5.6.0) | 
libsodium18(>= 1.0.8) | 
libstdc++6   (>= 5.2) | 
libx11-6  | 
libxi6| 
libxtst6  | 
libykpers-1-1 (>= 1.12.0) | 
libzxcvbn0(>= 0.20150103) | 
zlib1g   (>= 1:1.1.4) | 


Package's Recommends field is empty.

Package's Suggests field is empty.




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

Bug#923687: Add qttranslations5-l10n as recommend

[Alf Gaida]

Package: featherpad
Version: 0.9.4-1
Severity: normal

Featherpad should recommend qttranslations5-l10n until the translations are 
splitted out.

Without qttranslations5-l10n there are no menu shortcuts in non-english 
installations.

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

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

Versions of packages featherpad depends on:
ii  libc62.28-8
ii  libgcc1  1:8.3.0-2
ii  libqt5core5a 5.11.3+dfsg-5
ii  libqt5gui5   5.11.3+dfsg-5
ii  libqt5network5   5.11.3+dfsg-5
ii  libqt5printsupport5  5.11.3+dfsg-5
ii  libqt5svg5   5.11.3-2
ii  libqt5widgets5   5.11.3+dfsg-5
ii  libqt5x11extras5 5.11.3-2
ii  libstdc++6   8.3.0-2
ii  libx11-6 2:1.6.7-1

Versions of packages featherpad recommends:
ii  libglib2.0-bin  2.58.3-1

featherpad suggests no packages.

-- no debconf information

Bug#923686: kubernetes: CVE-2019-1002100: kube-apiserver: DoS with crafted patch of type json-patch

[Salvatore Bonaccorso]

Source: kubernetes
Version: 1.7.16+dfsg-1
Severity: grave
Tags: security upstream
Justification: user security hole
Forwarded: https://github.com/kubernetes/kubernetes/issues/74534

Hi,

The following vulnerability was published for kubernetes.

CVE-2019-1002100[0]:
kube-apiserver: DoS with crafted patch of type json-patch

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-1002100
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1002100
[1] https://github.com/kubernetes/kubernetes/issues/74534

Regards,
Salvatore

Bug#808839:

[Gilles Filippini]

Hi,

On Wed, 28 Nov 2018 10:32:51 +0100 Mathieu Malaterre  wrote:
> Correct backtrace:
> 
> change nwalsh into docbook-xsl to find:
> /usr/share/xml/docbook/stylesheet/docbook-xsl/fo/docbook.xsl
> 
> Then:
> 
> $ fop -xsl ./jlatexmath-fop/examples/latex.xsl -c
> ./jlatexmath-fop/examples/conf.xml -xml
> ./jlatexmath-fop/examples/latex_docbook.xml -pdf /tmp/bla.pdf
> [INFO] FopConfParser - Default page-height set to: 11in
> [INFO] FopConfParser - Default page-width set to: 8.26in
> [WARN] InputHandler - Note: namesp. cut : stripped namespace before
> processing   Very simple book with mathematical formulas
> [WARN] InputHandler - Making portrait pages on USletter paper (8.5inx11in)
> [WARN] FOUserAgent - Font "Symbol,normal,700" not found. Substituting
> with "Symbol,normal,400".
> [WARN] FOUserAgent - Font "ZapfDingbats,normal,700" not found.
> Substituting with "ZapfDingbats,normal,400".
> [INFO] FOUserAgent - Rendered page #1.
> [WARN] FOUserAgent - Hyphenation pattern not found. URI: en.
> [INFO] FOUserAgent - Rendered page #2.
> Exception in thread "main" java.lang.NoClassDefFoundError:
> org/scilab/forge/jlatexmath/TeXFormula
[...]

Given that TexFormula is in /usr/share/java/jlatexmath.jar, how about that?

$ export 
FOP_HYPHENATION_PATH=/usr/share/java/jlatexmath-fop.jar:/usr/share/java/jlatexmath.jar
$ fop -xsl ./libjlatexmath-java-1.0.7/jlatexmath-fop/examples/latex.xsl \
-c ./libjlatexmath-java-1.0.7/jlatexmath-fop/examples/conf.xml \
-xml ./libjlatexmath-java-1.0.7/jlatexmath-fop/examples/latex_docbook.xml \
-pdf blah.pdf

It seems it works here:
[warning] /usr/bin/fop: JVM flavor 'sun' not understood
[warning] /usr/bin/fop: Unable to locate 
/usr/share/java/jlatexmath-fop.jar:/usr/share/java/jlatexmath.jar in 
/usr/share/java
[INFO] FopConfParser - Default page-height set to: 11in
[INFO] FopConfParser - Default page-width set to: 8.26in
[WARN] InputHandler - Note: namesp. cut : stripped namespace before processing  
 Very simple book with mathematical formulas
[WARN] InputHandler - Making portrait pages on USletter paper (8.5inx11in)
[WARN] FOUserAgent - Font "Symbol,normal,700" not found. Substituting with 
"Symbol,normal,400".
[WARN] FOUserAgent - Font "ZapfDingbats,normal,700" not found. Substituting 
with "ZapfDingbats,normal,400".
[INFO] FOUserAgent - Rendered page #1.
[WARN] FOUserAgent - Hyphenation pattern not found. URI: en.
[INFO] FOUserAgent - Rendered page #2.
[WARN] FOUserAgent - Unknown formatting object 
"{http://forge.scilab.org/p/jlatexmath}latex"; encountered (a child of 
fo:instream-foreign-object}. (No context info available)
[ERROR] FOUserAgent - The intrinsic dimensions of an instream-foreign-object 
could not be determined. (No context info available)
[WARN] FOUserAgent - Glyph "M" (0x4d, M) not available in font "Symbol".
[WARN] FOUserAgent - Glyph "i" (0x69, i) not available in font "Symbol".
[WARN] FOUserAgent - Glyph "v" (0x76, v) not available in font "Symbol".
[WARN] FOUserAgent - Unknown formatting object 
"{http://forge.scilab.org/p/jlatexmath}latex"; encountered (a child of 
fo:instream-foreign-object}. (No context info available)
[WARN] FOUserAgent - Unknown formatting object 
"{http://forge.scilab.org/p/jlatexmath}latex"; encountered (a child of 
fo:instream-foreign-object}. (No context info available)
[WARN] FOUserAgent - Unknown formatting object 
"{http://forge.scilab.org/p/jlatexmath}latex"; encountered (a child of 
fo:instream-foreign-object}. (No context info available)
[WARN] FOUserAgent - Unknown formatting object 
"{http://forge.scilab.org/p/jlatexmath}latex"; encountered (a child of 
fo:instream-foreign-object}. (No context info available)
[WARN] FOUserAgent - Unknown formatting object 
"{http://forge.scilab.org/p/jlatexmath}latex"; encountered (a child of 
fo:instream-foreign-object}. (No context info available)
[WARN] FOUserAgent - Unknown formatting object 
"{http://forge.scilab.org/p/jlatexmath}latex"; encountered (a child of 
fo:instream-foreign-object}. (No context info available)
[WARN] FOUserAgent - Unknown formatting object 
"{http://forge.scilab.org/p/jlatexmath}latex"; encountered (a child of 
fo:instream-foreign-object}. (No context info available)
[WARN] FOUserAgent - Unknown formatting object 
"{http://forge.scilab.org/p/jlatexmath}latex"; encountered (a child of 
fo:instream-foreign-object}. (No context info available)
[WARN] FOUserAgent - Unknown formatting object 
"{http://forge.scilab.org/p/jlatexmath}latex"; encountered (a child of 
fo:instream-foreign-object}. (No context info available)
[WARN] FOUserAgent - Unknown formatting object 
"{http://forge.scilab.org/p/jlatexmath}latex"; encountered (a child of 
fo:instream-foreign-object}. (No context info available)
[WARN] FOUserAgent - Unknown formatting object 
"{http://forge.scilab.org/p/jlatexmath}latex"; encountered (a child of 
fo:instream-foreign-object}. (No context info available)
[WARN] FOUserAgent - Unknown formatting object 
"{http://forge.scilab.org/p/jlatex

Bug#923619: coreutils: FTBFS on hppa - Unknown error 252

[Helge Deller]

On 03.03.19 19:53, Helge Deller wrote:
> On 03.03.19 00:45, John David Anglin wrote:
>> The error doesn't occur if I do a simple "configure
>> --prefix=somewhere", make and make install.

fakeroot is the culprit. 
It uses ENOTSUP and the binary is still old and thus may use 252 for ENOTSUP.
Still need to understand if triggering nmu build of fakeroot is enough to fix 
it.

Helge

Bug#919977: security-tracker: https://security-tracker.debian.org/tracker/data/json returns stale data

[Salvatore Bonaccorso]

Hi Julien,

On Tue, Feb 19, 2019 at 09:29:35PM +0100, Salvatore Bonaccorso wrote:
> Hi Julien,
> 
> On Tue, Feb 12, 2019 at 10:28:54AM +0100, Julien Cristau wrote:
> > On 2/12/19 7:18 AM, Salvatore Bonaccorso wrote:
> > > Agreed on leaving the bug open until clearer what is going on?
> > 
> > Ack.
> 
> Right now this seem to be again stalled, at least from some locations.

Did anyone had a chance to look into it? The data right now is still
stalled (at least from some paths).

Regards,
Salvatore

Bug#890817: kernel-package: make-kpkg stalls indefinitely on linux-4.16-rc* in silentoldconfig stage

[David Lechner]

FWIW, I've tried the patches suggested so far. While they fix the lock up, my 
.config still gets written over at some point (see below), so make-kpkg is 
still broken for me (using 4.19 kernel source).


== making target debian/stamp/conf/kernel-conf [new prereqs: ]==
make 
CROSS_COMPILE=/usr/lib/x86_64-linux-gnu/gcc-linaro-6.4.1-2017.11-x86_64_arm-linux-gnueabihf/bin/arm-linux-gnueabihf-
 ARCH=arm \
    oldconfig;
make[2]: Entering directory 
'/home/david/work/ev3dev-dpkg/ev3dev-kpkg/ev3-kernel'
scripts/kconfig/conf  --oldconfig Kconfig
#
# configuration written to .config
#

Bug#884553: live-build: Foreign architecture package support for linux kernel flavours in Stretch

[adrian15]

El 20/11/18 a las 14:19, Raphael Hertzog escribió:

Sorry for the delay in answering but I have been busy.

> Hi,
> 
> On Sun, 18 Nov 2018, adrian15 wrote:
>> After testing this change the Grub menu which should have two kernel
>> entries has only one. It might be other of my patches are pending of
>> applying or somewhat I messed up with this patch.
> 
> It's up to you to figure this. I won't do it for you. And I won't merge
> the patch until you have something working entirely.

I understand.
I think I was talking aloud because I wish I had no difference from my
live-build fork to the upstream one (The Debian one) but there are still
differences nowadays.

I will try the patch as an standalone patch without merging it with my
other patches. That way I can prove the modifications are right.

Anyways let's continue answering the email.

> 
>> I know modifying the live-manual package is pending. I prefer waiting
>> for your feedback on my new implementation before commiting work on
>> live-manual.
> 
> The attached patch looks acceptable. The only small comments are below:

Ok.

> 
>> Once you have done this thanks to this commit
>> now you can set linux flavours ( --linux-flavours ) as:
>>
>> "i386 amd64:amd64"
>>
>> in a i386 system and it will install the amd64 kernel alongside the i386 
>> system.
> 
> This should really be part of the documentation (manual page) because
> right now the explanation is not clear on what it brings:
> 
>>  .IP "\-k|\fB\-\-linux\-flavours\fR \fIFLAVOUR\fR|""\fIFLAVOURS\fR""" 4
>> -sets the kernel flavours to be installed. Note that in case you specify 
>> more than that the first will be configured the default kernel that gets 
>> booted.
>> +sets the kernel flavours to be installed. Note that in case you specify 
>> more than that the first will be configured the default kernel that gets 
>> booted. Optionally you can use an architecture qualifier, e.g. amd64:amd64, 
>> so that it works ok when you add a foreign architecture to your build system.
> 
> That's the part to be expanded.

Ok, I'll try to do something on it.

> 
>> --- a/scripts/build/config
>> +++ b/scripts/build/config
>> @@ -1133,7 +1133,7 @@ LB_KEYRING_PACKAGES="${LB_KEYRING_PACKAGES}"
>>  
>>  # \$LB_LINUX_FLAVOURS: set kernel flavour to use
>>  # (Default: autodetected)
>> -LB_LINUX_FLAVOURS="${LB_LINUX_FLAVOURS}"
>> +LB_LINUX_FLAVOURS_WITH_ARCH="${LB_LINUX_FLAVOURS}"
> 
> I think you need to update all 3 occurences of LB_LINUX_FLAVOURS in this
> hunk... not only the name of the variable being assigned.

The reason why I didn't renamed everything to
LB_LINUX_FLAVOURS_WITH_ARCH was so that any project relying on the old
variable LB_LINUX_FLAVORUS did work without having to update its
configuration.


I don't have too much time so I will use the long name as you suggested
and probably update some related documentation, changelog or something.


> 
> Cheers,
> 

adrian15
-- 
Support free software. Donate to Super Grub Disk. Apoya el software
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/donate/

Bug#923685: pylint3: pylink3 crash on startup

[Boyd Stephen Smith Jr.]

Package: pylint3
Version: 2.2.2-1
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Dear Maintainer,

- ---8<---
% python3 --version
Python 3.7.2+
% pylint3 --version
Traceback (most recent call last):
  File "/usr/bin/pylint3", line 11, in 
load_entry_point('pylint==2.2.2', 'console_scripts', 'pylint')()
  File "/usr/lib/python3/dist-packages/pylint/__init__.py", line 17, in 
run_pylint
from pylint.lint import Run
  File "/usr/lib/python3/dist-packages/pylint/lint.py", line 76, in 
import astroid
  File "/usr/lib/python3/dist-packages/astroid/__init__.py", line 63, in 

from astroid.nodes import *
  File "/usr/lib/python3/dist-packages/astroid/nodes.py", line 23, in 
from astroid.node_classes import (
  File "/usr/lib/python3/dist-packages/astroid/node_classes.py", line 38, in 

from astroid import bases
  File "/usr/lib/python3/dist-packages/astroid/bases.py", line 33, in 
MANAGER = manager.AstroidManager()
  File "/usr/lib/python3/dist-packages/astroid/util.py", line 26, in 
lambda: importlib.import_module("." + module_name, "astroid")
  File "/usr/lib/python3.7/importlib/__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
  File "/usr/lib/python3/dist-packages/astroid/manager.py", line 25, in 
from astroid import modutils
  File "/usr/lib/python3/dist-packages/astroid/modutils.py", line 35, in 

from distutils.sysconfig import get_python_lib  # pylint: 
disable=import-error
ModuleNotFoundError: No module named 'distutils.sysconfig'
- --->8---

I'm guessing a missing dependency, but I'm not sure.

- -- System Information:
Debian Release: 9.8
  APT prefers stable-updates
  APT policy: (900, 'stable-updates'), (900, 'stable'), (850, 
'proposed-updates'), (700, 'testing'), (500, 'unstable'), (300, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages pylint3 depends on:
ii  python3 3.7.2-1
ii  python3-astroid 2.1.0-2
ii  python3-isort   4.2.5+ds1-2+deb9u1
ii  python3-logilab-common  1.3.0-1
ii  python3-mccabe  0.5.3-1
ii  python3-setuptools  33.1.1-1

Versions of packages pylint3 recommends:
ii  python3-tk  3.7.2-3

Versions of packages pylint3 suggests:
pn  pylint-doc  

- -- no debconf information

-BEGIN PGP SIGNATURE-

iHQEARECADQWIQTFhn3a8g2plxzZYyjnmmovsbVAWQUCXHwv/BYcYnNzQGlndWFu
YXN1aWNpZGUubmV0AAoJEOeaai+xtUBZeXkAn06vAV2jNnu9rtBwVq7ALORnJq65
AJ9cVx/r0SY3Mw3PDsNpke3zSueSsw==
=4IhQ
-END PGP SIGNATURE-

Bug#923684: nmu: galax_1.1-15

[Kyle Robbertze]

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

Hello,

There was a bug in how camomile < 1.0.1-3 was packaged that prevented
packages from building against it. This has been fixed, but requires
r-deps to be rebuilt using the fixed version.

Thanks

nmu galax_1.1-15 . ANY . unstable . -m "Rebuild against fixed camomile"
nmu ocaml-gettext_0.3.7-1 . ANY . unstable . -m "Rebuild against fixed camomile"
nmu lambda-term_1.10.1-2 . ANY . unstable . -m "Rebuild against fixed camomile"
nmu utop_1.19.3-2 . ANY . unstable . -m "Rebuild against fixed camomile"
nmu zed_1.4-3 . ANY . unstable . -m "Rebuild against fixed camomile"

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

Kernel: Linux 4.19.0-3-amd64 (SMP w/4 CPU cores)
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 /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#901251: IP multicast extended regular expression does not match some matchable lines which are matched online (regexr.com & regextester.com)

[Hannes von Haugwitz]

Hi,

On Sun, Jun 10, 2018 at 05:28:42PM +0200, jean-christophe manciot wrote:
> The rule *ulogd* described below (*IP multicast: 224.0.0.0 <-->
> 239.255.255.255*) does not match some matchable lines:
> ^.*? DST=2(?:2[4-9]|3\d)(?:\.(?:25[0-5]|2[0-4]\d|1\d\d|[1-9]\d?|0)){3} .*$

logcheck uses POSIX extended regular expression (ERE).

Your regular expression contains non-capturing group notation ('?:'),
which is not supported in ERE.

You can use `rgxg` to generate an extended regular expression for
'224.0.0.0/4':

$ rgxg cidr 224.0.0.0/4
(23[0-9]|22[4-9])(\.(25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9]?[0-9])){3}

With this regular expression `logcheck-test` matches your example log
lines.

If that solves your issue please close this bug report.

Best regards

Hannes

Bug#923637: ffindex FTCBFS: uses mpicc

[Michael Crusoe]

Thank you Helmut for your testing and your patch.

I've applied it at
https://salsa.debian.org/med-team/ffindex/commit/5a7eeb53972e97ee264eb67d9df2f6c7089e4e14

However I'm just a Debian Maintainer, so I'll need a DD to grant me upload
permission:

dcut dm --uid 724D609337113C710550D7473C26763F6C67E6E2 --allow ffindex

În dum., 3 mar. 2019 la 10:36, Helmut Grohne  a scris:

> Source: ffindex
> Version: 0.9.9.9-1
> Tags: upstream patch
> User: helm...@debian.org
> Usertags: rebootstrap
>
> ffindex fails to cross build from source, because it uses mpicc. mpicc
> is unfixable in terms of cross building, which is why it is being moved
> to pkg-config upstream. Rather than wrap your build in mpicc, you can
> compute the relevant flags using pkg-config just like any other library.
> The attached patch implements that and makes ffindex cross buildable
> once you add pkg-config to Build-Depends. Please consider applying it.
>
> Helmut
>


-- 
Michael R. Crusoe
Co-founder & Lead, Common Workflow Language project

Direktorius, VšĮ "Darbo eigos", Vilnius, Lithuania
https://orcid.org/-0002-2961-9670

m...@commonwl.org
+1 480 627 9108 / +370 653 11125

Bug#923650: Bug #923650 in x265 marked as pending

[Michael Cree]

Note that disabling altivec does not fix the baseline issue for
ppc64, namely that x265 is compiling with -mcpu=power8 on ppc64.

The baseline is power5.

Cheers,
Michael.

Bug#921266: Same crash with linphone 4.1.1 (flatpak)

[Alf]

I just tried to setup linphone in Buster by installing flatpak and the
latest version of linphone 4.1.1. Installation went smooth and it starts
without any configuration (alltogether roughly ½ GB of disk space).

However trying to configure my SIP-account results in the same (or very
similar) crash and segfault when password is entered:

tux kernel: [ 4866.131680] linphone[6107]: segfault at 0 ip
003153a8f37a sp 7ffe572604c8 error 4 in
libc-2.24.so[3153a0+194000]
Mar  3 18:17:33 tux kernel: [ 4866.131690] Code: 89 e6 5b 4c 89 ef 5d 41
5c 41 5d e9 e0 49 ff ff 89 f8 31 d2 66 0f ef ff 09 f0 25 ff 0f 00 00 3d
c0 0f 00 00 0f 8f 78 02 00 00  0f 6f 0f f3 0f 6f 06 66 0f 74 c1 66
0f da c1 66 0f ef c9 66 0f

So my conclusion is that this problem is more general and probably
related to some function/configuration in the Debian system?

Desktop environment is XFCE4.
Remark: my SIP-account (Telekom) requires for registration 2
authentication cycles to register and thus to supply the password twice.

Bug#923682: RFS: postfix-mta-sts-resolver/0.2.7-1 [ITP] -- Daemon providing MTA-STS map to Postfix

[Benjamin Hof]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "postfix-mta-sts-resolver":

 * Package name: postfix-mta-sts-resolver
   Version : 0.2.7-1
   Upstream Author : Vladislav Yarmak 
 * URL : https://github.com/Snawoot/postfix-mta-sts-resolver
 * License : Expat
   Section : mail

It builds those binary packages:

postfix-mta-sts-resolver - Daemon providing MTA-STS map to Postfix

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

  https://mentors.debian.net/package/postfix-mta-sts-resolver


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

dget -x 
https://mentors.debian.net/debian/pool/main/p/postfix-mta-sts-resolver/postfix-mta-sts-resolver_0.2.7-1.dsc
 

I have provided the packaging repository at 
https://salsa.debian.org/benjamin-guest/postfix-mta-sts-resolver

The Vcs-Browser and Vcs-Git fields point to salsa.debian.org/debian,
where I suggest the repository could live.


Kind regards,
Benjamin

Bug#720456: [vim-scripts] Please include the solarized colorscheme

[James McCoy]

On Fri, Mar 01, 2019 at 10:26:45PM -0500, Marco Villegas wrote:
> I have used https://github.com/altercation/solarized repository as the
> base to add the solarized color scheme to the package.

Thanks for working on this.

> I am not entirely sure of the urls on metadata at
> debian/vim-scripts.status, but I guess that they are OK. It is
> important to notice that there is a vim.org page, i.e.
> https://www.vim.org/scripts/script.php?script_id=3520, for the color
> scheme, but sadly the code there contains an older version of what I
> find at the repository, and that is why I decided to use the version
> from the repository.
> 
> I was a bit worried on how debian/vim-scripts.pl will handle the github
> url, but both doc and update actions seems to finish OK, naturally
> suggesting a false positive on the case of the new solarized addon.

All of this is going to be reworked as I'm in the process of changing
this package from using vim-addon-manager to dh-vim-addon.
vim-addon-manager had various problems that were holding me back from
updating vim-scripts.  I haven't been actively working on this since it
will have to wait until after Buster is released anyway.

> Another detail I am not sure about is the value of disabledby at
> debian/vim-scripts.status for this new addon, so I have just skipped it.

For a colorscheme, it's not needed.  The user has to explicitly use the
colorscheme anyway.

> Also, I have started by updating the html documentation for all addons,
> since I could not figure out a way to only do it for the new addon. It
> is in a separate commit, just in case that change is not a good idea.

Agreed, that's not necessary right now.

I would suggest holding off until the package gets restructured.  I'll
try to make some time for that again so at the very least there's an
experimental branch this could be merged into.

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB

Bug#923683: RFS: python-pynetstring/0.1~dev2+git20180925.40cd4a61-1 [ITP] -- netstring library for Python 3

[Benjamin Hof]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "python-pynetstring":

 * Package name: python-pynetstring
   Version : 0.1~dev2+git20180925.40cd4a61-1
   Upstream Author : Robert Johansson 
 * URL : https://github.com/rj79/pynetstring
 * License : Expat
   Section : python

It builds those binary packages:

python3-pynetstring - netstring library for Python 3

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

https://mentors.debian.net/package/python-pynetstring


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

dget -x 
https://mentors.debian.net/debian/pool/main/p/python-pynetstring/python-pynetstring_0.1~dev2+git20180925.40cd4a61-1.dsc


I have provided the packaging repository at
https://salsa.debian.org/benjamin-guest/pynetstring

The Vcs-Browser and Vcs-Git fields point to salsa.debian.org/debian,
where I suggest the repository could live.


Kind regards,
Benjamin

Bug#923681: RM: debian-installer-9-netboot-amd64 debian-installer-9-netboot-arm64 debian-installer-9-netboot-armel debian-installer-9-netboot-armhf debian-installer-9-netboot-i386 debian-installer-9-n

[Mattia Rizzolo]

Package: ftp.debian.org

SSIA.
TIA.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#923679: libglib2.0-0: gettext-desktopfiles patches cause memory leak

[Tim Newby]

Package: libglib2.0-0
Version: 2.56.3-0ubuntu0.18.04.1
Severity: normal

Dear Maintainer,

The patches '01-gettext-desktopfiles.patch' and '02-gettext-desktopfiles-
ubuntu.patch'
cause a memory leak as the fcn 'g_key_file_load_from_file' calls the fcn
'g_key_file_load_from_fd'
This causes a leak of memory allocated for string 'key_file->gettext_domain'.

Because 'g_key_file_load_from_file' calls the fcn 'g_key_file_load_from_fd' the
patch code
modifying 'key_file->gettext_domain' should probably ONLY be located in
'g_key_file_load_from_fd'?

The '01-gettext-desktopfiles.patch' actually causes the leak as in both the
mentioned fcns
we have

   key_file->gettext_domain = g_key_file_get_string (key_file,
G_KEY_FILE_DESKTOP_GROUP,
G_KEY_FILE_DESKTOP_KEY_GETTEXT_DOMAIN,
NULL);

A possible fix would be to change both patches to only apply modified code to
fcn 'g_key_file_load_from_fd'?



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

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

Versions of packages libglib2.0-0 depends on:
ii  libc62.27-3ubuntu1
ii  libffi6  3.2.1-8
ii  libmount12.31.1-0.4ubuntu3.3
ii  libpcre3 2:8.39-9
ii  libselinux1  2.7-2build2
ii  zlib1g   1:1.2.11.dfsg-0ubuntu2

Versions of packages libglib2.0-0 recommends:
ii  libglib2.0-data   2.56.3-0ubuntu0.18.04.1
ii  shared-mime-info  1.9-2
ii  xdg-user-dirs 0.17-1ubuntu1

libglib2.0-0 suggests no packages.

-- no debconf information

Bug#801328: crontab(5) has incorrect information about bash's $PATH handling

[Christian Kastner]

Tag: + confirmed pending

Hi Tim,

On 2015-10-08 16:36:26 Tim Landscheidt wrote:

> |An alternative for setting up the commands path is using  the
> |fact that many shells will treat the tilde(~) as substitution
> |of $HOME, so if you use bash for your tasks you can use this:
> 
> | SHELL=/bin/bash
> | PATH=~/bin:/usr/bin/:/bin
> 
> Specifically bash (and probably other shells as well) only treats the
> tilde in this way when expanding the command line that /sets/ the
> environment variable, not when /reading/ it for the path of an
> executable.  I. e., in a shell session/script, the second line would
> cause $PATH to be set to (for example) "/home/tim/bin:/usr/bin/:/bin",
> while if it is set in this manner in a crontab, in the shell it is set
> to "~/bin:/usr/bin/:/bin" (and thus wouldn't find executables in
> /home/tim/bin, but only in the subdirectory "bin" of the subdirectory
> "~" of the current directory (and /usr/bin and /bin)).
> 
> The paragraph should be removed completely.

thank you for your report. Your reasoning is sound, and I have verified
this for the bash shell.

I've reversed the documentation on this, and moved this example to the
examples that won't work.

Thanks,
Christian

Bug#923619: coreutils: FTBFS on hppa - Unknown error 252

[Helge Deller]

On 03.03.19 00:45, John David Anglin wrote:
> The error doesn't occur if I do a simple "configure
> --prefix=somewhere", make and make install.

I think it depends on the kernel version you are running.
Kernel 4.19 includes the ENOTSUP change, I assume you build
on an older kernel without this change.
Additionally I triggered a nmu-build of liblinux package
on march-1st, which might have some impact.
Anyway, I just returned from a short weekend-vacation and
started looking into it now again.

Helge

Bug#920042: lua-nvim: autopkgtest times out since 2019-01-10

[Paul Gevers]

Hi James,

On 03-03-2019 18:41, James McCoy wrote:
> It actually was caused by a test dependency (via @builddeps@) -- neovim.
> I don't see a migration check that ran lua-nvim's tests as part of
> neovim's migration.

The migration software doesn't process @builddeps@ yet as that is a
recent addition to the changes file and I haven't had the time to
implement it.

Paul




signature.asc
Description: OpenPGP digital signature

Bug#571241: checkroot.sh: should not try to fsck rootfs on ubifs

[Pierre Ynard]

Also discussing the more general issue of selective bootup fsck in
#408954 as of recently.

> Is it ok for you, to create a dummy fsck.ubifs in parallel to
> fsck.nfs?

If we decide to go that way, I think it would be better to modify
the fsck.nfs script to make it generic, and just symlink it for any
filesystem that we need to cope with.

You could also modify /etc/fstab to set the pass field to 0, since
I suppose it's fixed now. Which brings the question, why would the
installer write an /etc/fstab requesting fsck of ubifs, which is
impossible? Should the installer be modified to be more selective about
filesystems when writing /etc/fstab?

Or as mentioned in #408954, we could also modify initscripts to add
checks and logic that disable fsck on ubifs by default in some way or
another.

-- 
Pierre Ynard

Bug#923392: Try to launch /usr/lib/bluetooth/bluetoothd without plugin autopair

[Corcodel Marian]

I put as parameter --noplugin=autopair but still connect without auth.

Repeat on info file on LinkKey section param Key do not change after 
restart, device is connected but without key valid.


User must remove audio bluetooth from list and try again in order to 
create new Key.

Bug#923678: libjs-leaflet-markercluster: not a transitional package for apt

[Thorsten Glaser]

Package: libjs-leaflet-markercluster
Version: 1.4.1~dfsg-5
Severity: important

When removing the libjs-leaflet-markercluster “transitional” package,
apt also clears the new one for removal:


$ sudo apt-get purge libjs-leaflet-markercluster
Reading package lists... Done
Building dependency tree
Reading state information... Done
Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
The following package was automatically installed and is no longer required:
  libjs-leaflet.markercluster
Use 'sudo apt autoremove' to remove it.
The following packages will be REMOVED:
  libjs-leaflet-markercluster*
0 upgraded, 0 newly installed, 1 to remove and 2 not upgraded.
After this operation, 65.5 kB disk space will be freed.
Do you want to continue? [Y/n] n


This is because libjs-leaflet-markercluster is not in Section oldlibs
(used to also require Priority extra, but please recheck with apt docs).

Proper transitional packages make apt transfer the “manually installed”
bit to the depended-on packages.


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

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

Versions of packages libjs-leaflet-markercluster depends on:
ii  libjs-leaflet.markercluster  1.4.1~dfsg-5

libjs-leaflet-markercluster recommends no packages.

libjs-leaflet-markercluster suggests no packages.

-- no debconf information

Bug#895024: Error: bad hour; while reading /etc/crontab makes the cron do nothing

[Christian Kastner]

Tags: + unreproducible moreinfo

Hi Salvo,

On 2018-06-04 12:57:37 Salvo Tomaselli wrote:
> I had made a mistake while writing crontab, and had reversed hours and 
> minutes.
> 
> This happened:
> Error: bad hour; while reading /etc/crontab
> 
> Hoewver, cron then doesn't run any job at all. In this case it should just
> terminate with error, so I would see that the service is not running at all.

The service should be running. The cron daemon just skips the broken
crontab.

I just tested this by first creating a valid crontab

  * * * * * root date >> /tmp/datestamp

and later by adding an invalid one

  * 25 * * * root date >> /tmp/foostamp

and the following is logged to the cron facility:

Mar  3 18:58:01 devel CRON[22663]: (root) CMD (date >> /tmp/datestamp)
Mar  3 18:59:01 devel CRON[22721]: (root) CMD (date >> /tmp/datestamp)
Mar  3 19:00:01 devel cron[3870]: Error: bad hour; while reading 
/etc/cron.d/bar
Mar  3 19:00:01 devel cron[3870]: (*system*bar) ERROR (Syntax error, this 
crontab file will be ignored)
Mar  3 19:00:01 devel CRON[22751]: (root) CMD (date >> /tmp/datestamp)
Mar  3 19:01:01 devel CRON[22755]: (root) CMD (date >> /tmp/datestamp)

As you can see, the crontab /etc/cron.d/bar is skipped because of a
syntax error, but cron continues executing the other crontab.

Could you please re-check if cron is indeed not processing any other
tabs (for example, with the above examples).

Note that I have enabled logging for every priority of the cron
facility to /var/log/cron.log (/etc/rsyslog.conf has a commented-
out example for this).

Regards,
Christian

Bug#923444: bacula: autopkgtest regressed in buster

[Sven Hartge]

On 03.03.19 18:31, Carsten Leonhardt wrote:

> I haven't used triggers yet so I'm not aware of all the details. If we
> can be sure that the setup will be executed even when no local database
> server will be installed because a remote server is used, then I'm all
> for doing it at the end.

I see one problem here: postinst will start the director at its end,
because up until now, the database is configured and ready before.

If we change this, the (re)start of the director has to also be done in
the trigger and not in the postinst.

Question is: is the trigger system designed to be used like this?

Or are we trying to fix a problem at the whole wrong level?

Maybe apt/dpkg needs a change, where if a package is Recommends: but
installed in the same action as the package recommending it, it should
be treated as if it where a Depends:?

Grüße,
Sven.



signature.asc
Description: OpenPGP digital signature

Bug#923511: [pkg-bacula-devel] Bug#923511: make_catalog_backup.pl doesn't sanitize $args{db_name}

[Carsten Leonhardt]

Control: tags -1 upstream
Control: forwarded -1 https://bugs.bacula.org/view.php?id=2458

Hi Sergio,

> /etc/bacula/scripts/make_catalog_backup.pl uses a temporary file with a name
> based on $args{db_name}. This fails if the database name contains / 
> characters,
> as it well might if it is a URI like
> postgresql://host/db?sslmode=verify-full&sslrootcert=/etc/ssl/certs/host-ca.crt

I've written a patch to base the filename on the catalog name as you
suggested (although I'm not good at perl), but the script
"delete_catalog_backup" needs to be changed too.

I've submitted your bug report upstream.

Regards,

Carsten

--- make_catalog_backup-orig.pl	2018-09-22 20:24:38.0 +0200
+++ make_catalog_backup.pl	2019-03-03 12:48:04.217637851 +0100
@@ -30,11 +30,15 @@
 my $dir_conf='/usr/sbin/dbcheck -B -c /etc/bacula/bacula-dir.conf';
 my $wd = "/var/lib/bacula";
 
+# sanitize catalog name for use as filename
+my $dump_filename = $cat;
+$dump_filename =~ s/[^A-Za-z0-9_\-]//g;
+
 sub dump_sqlite3
 {
 my %args = @_;
 
-exec("echo .dump | sqlite3 '$wd/$args{db_name}.db' > '$wd/$args{db_name}.sql'");
+exec("echo .dump | sqlite3 '$wd/$args{db_name}.db' > '$wd/$dump_filename.sql'");
 print "Error while executing sqlite dump $!\n";
 return 1;
 }
@@ -69,7 +73,7 @@
 {
 my %args = @_;
 setup_env_pgsql(%args);
-exec("HOME='$wd' pg_dump -c > '$wd/$args{db_name}.sql'");
+exec("HOME='$wd' pg_dump -c > '$wd/$dump_filename.sql'");
 print "Error while executing postgres dump $!\n";
 return 1;   # in case of error
 }
@@ -117,7 +121,7 @@
 my %args = @_;
 
 setup_env_mysql(%args);
-exec("HOME='$wd' mysqldump -f --opt $args{db_name} > '$wd/$args{db_name}.sql'");
+exec("HOME='$wd' mysqldump -f --opt $args{db_name} > '$wd/$dump_filename.sql'");
 print "Error while executing mysql dump $!\n";
 return 1;
 }

Bug#920042: lua-nvim: autopkgtest times out since 2019-01-10

[James McCoy]

On Mon, Jan 21, 2019 at 09:17:00PM +0100, Paul Gevers wrote:
> Since 2019-01-10 the autopkgtest of your package times out (after 2:47h)
> on ci.debian.net. Unfortunately, this most likely isn't caused by any of
> your direct (test) dependencies, otherwise the integration with our
> migration software should have caught it. The timeout also happens in
> testing. If the content of our log is correct, the following files may
> hint at the culprit:
> https://ci.debian.net/data/packages/testing/amd64/l/lua-nvim/1696673.log
> https://ci.debian.net/data/packages/unstable/amd64/l/lua-nvim/1675059.log

It actually was caused by a test dependency (via @builddeps@) -- neovim.
I don't see a migration check that ran lua-nvim's tests as part of
neovim's migration.

I'll be committing the attached patch upstream.

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB
>From 24fe448aa406b0aa2267044a9858e3d2e5963b61 Mon Sep 17 00:00:00 2001
From: James McCoy 
Date: Sun, 3 Mar 2019 11:49:54 -0500
Subject: [PATCH] Use --embed --headless for Socket/TcpStream session tests

After neovim/neovim#9024, "nvim --embed" waits for a UI to attach.
"nvim --embed --headless" is required if there is not going to be a UI.
---
 test/session_spec.lua | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/test/session_spec.lua b/test/session_spec.lua
index d5d705c..1fc289d 100644
--- a/test/session_spec.lua
+++ b/test/session_spec.lua
@@ -155,7 +155,7 @@ end)
 -- Session using SocketStream
 test_session(string.format("Session using SocketStream [%s]", socket_file), function ()
   child_session = Session.new(ChildProcessStream.spawn({
-nvim_prog, '-u', 'NONE', '--embed',
+nvim_prog, '-u', 'NONE', '--embed', '--headless',
 '--cmd', string.format('call serverstart("%s")', socket_file)
   }))
   child_session:request('vim_eval', '1') -- wait for nvim to start
@@ -193,7 +193,7 @@ end)
 -- Session using TcpStream
 test_session("Session using TcpStream", function ()
   child_session = Session.new(ChildProcessStream.spawn({
-nvim_prog, '-u', 'NONE', '--embed',
+nvim_prog, '-u', 'NONE', '--embed', '--headless',
 '--cmd', 'call serverstart("127.0.0.1:")'
   }))
 
-- 
2.20.1

Bug#923675: debian-installer: delays when using an https mirror due to rng

[Colin Watson]

I don't have much advice on fixing it, but I expect that network-console
has a similar problem since it also needs randomness in order to deal
with SSH.

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

Bug#923677: gcp: Importing dbus.glib to use the GLib main loop with dbus-python is deprecated.

[gcp:42: DeprecationWarning: Importing dbus.glib to use the GLib main loop with dbus-python is deprecated]

Package: gcp
Version: 0.2.0-1
Severity: normal

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

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

Versions of packages gcp depends on:
ii  dbus-user-session [default-dbus-session-bus]  1.12.12-1
ii  dbus-x11 [dbus-session-bus]   1.12.12-1
ii  python3   3.7.2-1
ii  python3-dbus  1.2.8-3
ii  python3-gi3.30.4-1

Versions of packages gcp recommends:
ii  python3-progressbar  2.5-1

gcp suggests no packages.

-- no debconf information

Bug#923676: ITP: python-pynetstring -- netstring library for Python 3

[Benjamin Hof]

Package: wnpp
Severity: wishlist
Owner: Benjamin Hof 

* Package name: python-pynetstring
  Version : 0.1~dev2+git20180925.40cd4a61-1
  Upstream Author : Robert Johansson 
* URL : https://github.com/rj79/pynetstring
* License : Expat
  Programming Lang: Python
  Description : netstring library for Python 3

A Python 3 module for encoding and decoding netstrings, a
serialisation method designed for network transfer and safe parsing.
The netstring format is defined at
https://cr.yp.to/proto/netstrings.txt.

This package is a dependency of postfix-mta-sts-resolver (ITP:
#917366).

Bug#923444: bacula: autopkgtest regressed in buster

[Carsten Leonhardt]

Hi Paul,

Paul Gevers  writes:

> On 02-03-2019 15:34, Carsten Leonhardt wrote:
>> maybe using a trigger can help us:
>
> This sounds like an idea we should try to implement in dbconfig-common,
> to enable other packages to benefit from it as well. If done, this is
> for after buster release though.

I already found that we're not the first to run into this problem.

>> In bacula-director-psql/mysql postinst, pseudo code:
>> 
>> 1 if (database server is being installed in the same run)
>> 2   then (install trigger to postpone database setup)
>> 3   else (setup database now)
>> 4 if triggered: (setup database now)
>>
>> Thoughts/explanations:
>> Step 1: I haven't researched yet if it's possible to reliably detect
>> that
>> Step 3: set up now as we won't get triggered later
>> Step 4: But what to trigger on exactly? 
>
> Why not delay configuration until the end in all cases? I don't like the
> added complexity much, unless it has real value.

I haven't used triggers yet so I'm not aware of all the details. If we
can be sure that the setup will be executed even when no local database
server will be installed because a remote server is used, then I'm all
for doing it at the end.

>> An simple but stupid and unelegant alternative would be to generate meta
>> packages "bacula-director-local-psql/mysql" that _depend_ on the database
>> server packages.
>
> I rather propose that we accept the current regression of the bacula
> autopkgtest and we fix the situation properly (in autopkgtest and/or
> dbconfig-common) after the buster release. Can you live with that?

Yes, we can live with that as long as the CI-people can, as Sven
already said.

Would you like me to file a wishlist bug against dbconfig-common?

 - Carsten

Bug#893575: crontab.5: Some fixes in the manual

[Christian Kastner]

Tags: + pending

Hi Bjarni,

On 2018-03-20 00:38 Bjarni Ingi Gislason  wrote:
> Package: cron
> Version: 3.0pl1-130
> Severity: minor
> Tags: patch

Thank you very much for these fixes! I just applied them, and will
include them in the next release.

Regards,
Christian

Bug#923675: debian-installer: delays when using an https mirror due to rng

[Cyril Brulebois]

Package: debian-installer
Severity: important

Spotted with the netboot-gtk-french-with-https playbook of the tiny d-i
test suite, that sets a few command line parameters:

mirror/protocol=https
mirror/https/hostname=deb.debian.org
mirror/https/directory=/debian

the initial choose-mirror scanning of the repository takes ages (up to
several minutes, if one doesn't interact with the VM):

Mar  3 17:09:12 syslogd started: BusyBox v1.27.2
[…]
Mar  3 17:09:31 choose-mirror[1710]: DEBUG: command: wget --no-verbose 
https://deb.debian.org/debian/dists/oldstable/Release -O - | grep -E 
'^(Suite|Codename|Architectures):'
Mar  3 17:11:51 kernel: [  161.130075] random: crng init done
Mar  3 17:11:51 kernel: [  161.130086] random: 7 urandom warning(s) missed 
due to ratelimiting
Mar  3 17:11:52 choose-mirror[1710]: DEBUG: command: wget --no-verbose 
https://deb.debian.org/debian/dists/jessie/Release -O - | grep -E 
'^(Suite|Codename|Architectures):'
Mar  3 17:11:53 choose-mirror[1710]: DEBUG: command: wget --no-verbose 
https://deb.debian.org/debian/dists/stable/Release -O - | grep -E 
'^(Suite|Codename|Architectures):'
Mar  3 17:11:53 choose-mirror[1710]: DEBUG: command: wget --no-verbose 
https://deb.debian.org/debian/dists/stretch/Release -O - | grep -E 
'^(Suite|Codename|Architectures):'
Mar  3 17:11:54 choose-mirror[1710]: DEBUG: command: wget --no-verbose 
https://deb.debian.org/debian/dists/testing/Release -O - | grep -E 
'^(Suite|Codename|Architectures):'
Mar  3 17:11:54 choose-mirror[1710]: DEBUG: command: wget --no-verbose 
https://deb.debian.org/debian/dists/buster/Release -O - | grep -E 
'^(Suite|Codename|Architectures):'
Mar  3 17:11:55 choose-mirror[1710]: DEBUG: command: wget --no-verbose 
https://deb.debian.org/debian/dists/unstable/Release -O - | grep -E 
'^(Suite|Codename|Architectures):'
Mar  3 17:11:56 choose-mirror[1710]: DEBUG: command: wget --no-verbose 
https://deb.debian.org/debian/dists/sid/Release -O - | grep -E 
'^(Suite|Codename|Architectures):'
Mar  3 17:11:56 choose-mirror[1710]: INFO: suite/codename set to: 
testing/buster

Any advice on how to fix/mitigate this appreciated.


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

Bug#913965: dak: Please ignore build-profile packages from Package-List

[Samuel Thibault]

Bastian Blank, le dim. 03 mars 2019 17:21:53 +0100, a ecrit:
> On Sat, Nov 17, 2018 at 05:52:01PM +0100, Guillem Jover wrote:
> > But as dak uses the entire Package-List from the .dsc for its "seen"
> > tracking this is problematic, because these require NEW processing,
> > or these uploads are not accepted as part of a source-only upload,
> > and even if they get processed once (AFAIR) these get garbage
> > collected as they are never seen in practice, which means they will
> > trigger NEW processing or REJECTs again.
> 
> Could you please propose an algorithm to determine which packages are
> allowed to show up in any upload to the archive?

AIUI, the idea is that in the Package-List field, if a line contains
a "profile=" part, it needs to contain at least an alternative with only
negations to be kept, i.e. something like

if ~= "profile="
{
  if ! ~= "profile=(.*\+)?(![^,]*(,![^,]*)*)(\+.*)?"
drop line
}

so that
- profile=!noudeb is not dropped,
- profile=!noudeb,!stage1,!stage2 is not dropped,
- profile=!noudeb,!stage1,!stage2+foobar is not dropped,
- profile=!noudeb,!stage1,!stage2+foobar+!bat is not dropped,
- profile=foobar is dropped,
- profile=blah,foobar+baz is dropped,

Samuel

Bug#915050: (gitlab) Re: Bug#915050: Keep out of testing

[Justin Hallett]

Well I hope it comes to that personally, cause I think you have been doing a 
great job, it’s a TON of work to maintain all the depends you do for gitlab and 
honestly there are rarely issues and when they are you fix them very quickly 
after a report.

It’s very upsetting that I now have 10 tickets in my queue because of things I 
can’t do on gitlab since this ticket broke everything!

I have it working but barely and lots of important tasks like PRs aren’t 
working at all.  Let me know if there is anything I can do, test or help with 
in any way.

And thank you for all your hard work on this project!

> On Mar 3, 2019, at 3:40 AM, Pirate Praveen  wrote:
> 
> On Mon, 25 Feb 2019 07:45:36 -0700 Justin Hallett  
> wrote:
> > This ticket is bogus and should be closed and removed so that gitlab can be 
> > fixed in testing and restore the faith of its users.
> 
> I think we have not received the same level of respect from the rest of the 
> project. Since everyone is pushing for strict interpretation of rules with no 
> regards to our contribution, I'm also forced to go by the strict 
> interpretation of rules. Once we get gitlab working with rails 5.2, and if 
> this bug is the only blocker, I will close this bug as bogus asserting my 
> rights as the maintainer.
> 
> -- 
> Sent from my Android device with K-9 Mail. Please excuse my brevity.