Bug#926928: fetchmail: Server CommonName mismatch

[Jochen Hein]

Source: fetchmail
Followup-For: Bug #926928

I've checked the manpage for fetchmail. There was the following in the
stretch package:

   --sslcommonname 
  (Keyword: sslcommonname; since v6.3.9)
  Use of this option is discouraged. Before using it,
  contact the administrator of your upstream server and
  ask for a proper SSL certificate to be used. If that
  cannot be attained, this option can be used to specify
  the name (CommonName) that fetchmail expects on the
  server certificate.  A correctly configured server will
  have this set to the hostname by which it is reached,
  and by default fetchmail will expect as much. Use this
  option when the CommonName is set to some other value,
  to avoid the "Server CommonName mismatch" warning, and
  only if the upstream server can't be made to use proper
  certificates.

Beside that I think that the bug should be downgraded...

Jochen

Bug#900912: marked as done (openjdk-11: Accessibility does not get loaded)

[Debian Bug Tracking System]

Your message dated Wed, 17 Apr 2019 03:22:45 +
with message-id 
and subject line Bug#900912: fixed in openjdk-11 11.0.3+7-1
has caused the Debian Bug report #900912,
regarding openjdk-11: Accessibility does not get loaded
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
900912: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900912
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openjdk-10
Version: 10.0.1+10-4
Severity: important
Tags: a11y

Hello,

Like with openjdk-9, accessibility does not work in the openjdk-10
packages, the libatk-wrapper and java-atk-wrapper do not get loaded.

See Bug#822642 for my researches at the time, I gues things haven't
improved since then. I have pasted it for conveniency:

“
In previous versions there were symlinks for java-atk-wrapper.jar and
libatk-wrapper.so in
/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/ext
but with openjdk-9 this directory seems to be disabled. I see that it's
where the class gets loaded from with openjdk-8: -verbose:class show:

[Loaded org.GNOME.Accessibility.AtkWrapper from 
file:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/ext/java-atk-wrapper.jar]

and removing that file brings

Exception in thread "main" java.awt.AWTError: Assistive Technology not found: 
org.GNOME.Accessibility.AtkWrapper
at java.awt.Toolkit.loadAssistiveTechnologies(Toolkit.java:807)
at java.awt.Toolkit.getDefaultToolkit(Toolkit.java:886)
at java.awt.Window.getToolkit(Window.java:1362)

I tried to look for the equivalent code in openjdk-9, but I don't see
where the binary is supposed to be: in openjdk-8, it was in rt.jar, but
I can't find this in openjdk-9. The source code of getDefaultToolkit
seems to be the same, except that it also checks for running headless.
Perhaps that's the test that fails?
”

I guess openjdk-8 will be phased out in Buster, so this is a really
important issue: people needing accessibility will not be able to use
java applications at all any more if openjdk-10 does not properly load
accessibility support.

Samuel

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

Kernel: Linux 4.17.0 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: openjdk-11
Source-Version: 11.0.3+7-1

We believe that the bug you reported is fixed in the latest version of
openjdk-11, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 900...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated openjdk-11 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 17 Apr 2019 04:16:16 +0200
Source: openjdk-11
Architecture: source
Version: 11.0.3+7-1
Distribution: unstable
Urgency: high
Maintainer: OpenJDK Team 
Changed-By: Matthias Klose 
Closes: 900912
Changes:
 openjdk-11 (11.0.3+7-1) unstable; urgency=high
 .
   * OpenJDK 11.0.3+7 build.
   * Support using the Java ATK wrapper (Samuel Thibault). Closes: #900912.
 - patches/jaw-classpath.diff: Fix finding the Java ATK wrapper.
 - patches/jaw-optional.diff: Make failing to load the Java ATK wrapper
   non-fatal.
Checksums-Sha1:
 d03f38c212413bc7cdc057640c64372251c831a2 4692 openjdk-11_11.0.3+7-1.dsc
 20f390f7ac9302e81343af05d7a0a3fbc7bf8d1a 75355240 
openjdk-11_11.0.3+7.orig.tar.xz
 c0dac923f4b8256b79aca173ff3411b5552b6108 172508 
openjdk-11_11.0.3+7-1.debian.tar.xz
 cc62d1a773daca21df5d90382ade758f43dfcbab 17320 
openjdk-11_11.0.3+7-1_source.buildinfo
Checksums-Sha256:
 ca2940b9bef4ec82dd3bbd048ac2a0d4fc99e24ad21383831347fed6a5071705 4692 
openjdk-11_11.0.3+7-1.dsc
 

Bug#926565: marked as done (cantor-backend-scilab: scilab is no longer available on armel, mips, mipsel)

[Debian Bug Tracking System]

Your message dated Wed, 17 Apr 2019 00:03:35 +
with message-id 
and subject line Bug#926565: fixed in cantor 4:18.12.0-2
has caused the Debian Bug report #926565,
regarding cantor-backend-scilab: scilab is no longer available on armel, mips, 
mipsel
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
926565: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926565
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cantor-backend-scilab
Version: 4:18.12.0-1
Severity: serious

Hi,

scilab is no longer built for armel, mips, mipsel (in addition to
mips64el), due to uninstallability of libjogl2-java.
Please drop these architectures from the cantor-backend-scilab
binary package.


Andreas
--- End Message ---
--- Begin Message ---
Source: cantor
Source-Version: 4:18.12.0-2

We believe that the bug you reported is fixed in the latest version of
cantor, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 926...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Simon Quigley  (supplier of updated cantor package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 16 Apr 2019 18:44:00 -0500
Source: cantor
Architecture: source
Version: 4:18.12.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian/Kubuntu Qt/KDE Maintainers 
Changed-By: Simon Quigley 
Closes: 926565
Changes:
 cantor (4:18.12.0-2) unstable; urgency=medium
 .
   * Team upload.
   * Do not build the scilab backend on armel, mips, and mipsel
 (Closes: #926565).
Checksums-Sha1:
 cde567a283cc68deb47723ce93def527ba528809 3914 cantor_18.12.0-2.dsc
 8ccd3a115516708bcfd2d3888e5f0909a420a5b0 15896 cantor_18.12.0-2.debian.tar.xz
 6866f2e050837fdde3495f926bbfec4557ffaf74 15688 
cantor_18.12.0-2_source.buildinfo
Checksums-Sha256:
 b16a236390e59a51b348a498a972b7e88cac0a38b2f65857a2e9ce9c22b17971 3914 
cantor_18.12.0-2.dsc
 3163a8fbb03074809e5b4345b51937ce55f7e2b83a0e6b84100788e3f1b74c7f 15896 
cantor_18.12.0-2.debian.tar.xz
 0783fa7e81ee0a2703eeffe3f7ba3f71371924646fa36c2ef92837abedbd5009 15688 
cantor_18.12.0-2_source.buildinfo
Files:
 1cddfa75dc879bc9bc699a340d673886 3914 kde optional cantor_18.12.0-2.dsc
 066a4cb83308e0ec777170783f7e9fb3 15896 kde optional 
cantor_18.12.0-2.debian.tar.xz
 61669f40cc534498c171e077b1066ea7 15688 kde optional 
cantor_18.12.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEXHq+og+GMEWcyMi14n8s+EWML6QFAly2aPsACgkQ4n8s+EWM
L6TJJg/9GaD4xSwMDUXumwRfWpuKpxAfhWbfPMgJ2hbN6e1QL+MJfmjQkyfcZOUS
CnirJeSJedN7OzVLOSCUoP12t4k4BJuCWm2aU7n6Rkz6x5ohmvCCGVzBXl7VE/TX
9HExwUt1zPAcKqp7cDkRffm0UpkSMBJ7oMjnIOaAwABofvJx8lbP9c/dRDh00rOH
1zENP/K2SCDt8UWb3DtAIZITLXFPl0nXvPLLlcHZha5knfYnc1ariGOZPaD0lzbF
HVrIvqqU1Uv76rgRCVFveWv43IRRLsgUCWvPzaBSjY/CsWUf0miJ5AfqlU5Pypx5
+ciBJV23EL/oD/b9hh3iIpT2kCd8ASKXbggAs8Ao/i2e9LuOP66vQqiOMM/UAmOA
SeYR3DHEqYtoykmBRorWKmh7IkL6vUUNLEGT19pUnKvZF9DoIZSN9g9KeKKBZ/WN
wHfROFpAh251HJTkEWJbD2I0SRBxUO03B6q8qOg8+hIRmj/tb4WEtB0ODo0biTWh
9Nnl47AP4uOyW0dlT5prnANQEEkegefeUf2vIId/dp6Y1uCwLBpxOzb0P3l6zeFs
68PY4jHWZIvK+wgUFx8NH6OeRRfvG+qmYg/ynQQVtPXWSmzu3BC4cxGuD6dzbZLb
r7+Guv185ffZMPu4BJkS/eCZZRbNIC4E/G6y48y75VOMI3Ry7Lo=
=5hMJ
-END PGP SIGNATURE End Message ---

Bug#910964: libprotobuf17 might need Breaks: libprotobuf10

[GCS]

On Sat, Apr 13, 2019 at 12:02 PM Niels Thykier  wrote:
> From a release team PoV, we would very much like to see this be fixed
> with a Breaks as well.
 I've prepared the change and attached to this email. This will make
libarcus3 and cura-engine need to be upgraded in the same time to
package versions which was built with libprotobuf17.

> On the flip side, having libprotobuf10 remain on some systems during
> upgrades will spell trouble for us later.  Each release, we see a number
> of upgrade issues related to old, long obsolete packages that were
> removed releases ago.  Lets ensure libprotobuf10 does not become one of
> them for bullseye or later.
 In the last five years (I can remember about protobuf) upstream only
increased the soname - I don't think it will change. But I'll try to
remember and with the new upstream release (targeting Bullseye) add a
break to libprotobuf10.

Regards,
Laszlo/GCS
diff -Nru protobuf-3.6.1.3/debian/control protobuf-3.6.1.3/debian/control
--- protobuf-3.6.1.3/debian/control	2018-12-09 12:45:11.0 +
+++ protobuf-3.6.1.3/debian/control	2019-04-16 22:12:03.0 +
@@ -66,6 +66,7 @@
 Multi-Arch: same
 Section: libs
 Depends: ${shlibs:Depends}, ${misc:Depends}
+Breaks: libarcus3 (<< 3.3.0-2), cura-engine (<< 1:3.3.0-2.1+b1)
 Description: protocol buffers C++ library
  Protocol buffers are a flexible, efficient, automated mechanism for
  serializing structured data - similar to XML, but smaller, faster, and

Bug#926212: gnome-shell crashed: segfault in libgnome-shell.so after printing email from evolution

[Bernhard Übelacker]

On Tue, 16 Apr 2019 22:47:14 +0100 Simon McVittie  wrote:
> How sure are you that the virtual memory area starting at 0x7fd4fa6a6000
> starts with .init and not .text?

Unfortunately I am not completely sure, but I caused a crash while
knowing the memory layout and found there also the dmesg line
containing start of .init.
At least this calculation worked later in 927142 too.

Kind regards,
Bernhard

Bug#927162: gnome-shell segfaults in libst-1.0.so

[Simon McVittie]

On Tue, 16 Apr 2019 at 15:13:56 -0700, Eloston wrote:
> After looking at the TopIcons code at the line indicated in journalctl, I am
> able to reproduce the crash with the following:
> 
> 1. Open Looking Glass (lg)
> 2. Run the following:
> 
>   a = new St.Widget();
>   a.destroy();
>   a.get_theme_node();
> 
> After running the third line, gnome-shell will crash.

This is undefined behaviour (i.e. incorrect code): nothing should be
calling methods on a widget that has been destroyed. Ideally, it
would just log a warning and carry on, instead of crashing (and that's
what the upstream patch that I'm testing does), but nothing is going to
make this correct.

Looking at line 121 in the top-icons-plus extension, what I would expect
should happen is that in response to the destroy signal emitted by the
icon's destroy() method, everything else stops trying to do anything with
the icon (in particular, stops trying to draw it, which would involve
calling get_theme_node() on it). I'm not sure yet why that doesn't happen.
It might be a bug in the top-icons-plus extension, or a bug elsewhere in
GNOME Shell.

smcv

Processed: powerpc-utils is uninstallable

[Debian Bug Tracking System]

Processing control commands:

> affects -1 grub-ieee1275
Bug #927255 [powerpc-utils] powerpc-utils is uninstallable
Added indication that 927255 affects grub-ieee1275

-- 
927255: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927255
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#927255: powerpc-utils is uninstallable

[Daniel Kahn Gillmor]

Package: powerpc-utils
Version: 1.3.2-1.1
Severity: grave
Justification: renders package unusable
Control: affects -1 grub-ieee1275

powerpc-utils Depends: pmac-utils, but pmac-utils is no longer in
debian.

This makes powerpc-utils uninstallable, which in turn makes
grub-ieee1275 uninstallatble.

--dkg

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: powerpc (ppc)

Kernel: Linux 5.0.0-trunk-powerpc-smp (SMP w/1 CPU core)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages powerpc-utils depends on:
ii  pmac-utils 1.1.3-27
ii  powerpc-ibm-utils  1.3.2-1.1

powerpc-utils recommends no packages.

powerpc-utils suggests no packages.

-- no debconf information


signature.asc
Description: PGP signature

Processed: Re: Bug#926212: gnome-shell crashed (segfault)

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/497
Bug #926212 [gnome-shell] gnome-shell crashed: segfault in libgnome-shell.so 
after printing email from evolution
Changed Bug forwarded-to-address to 
'https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/497' from 
'https://gitlab.gnome.org/GNOME/gnome-shell/issues/750'.

-- 
926212: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926212
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#926212: gnome-shell crashed (segfault)

[Simon McVittie]

Control: forwarded -1 
https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/497

On Sun, 07 Apr 2019 at 20:00:23 +0200, Bernhard Übelacker wrote:
> PS.: My untested change in message 10 might not crash, but lead to an
> infinitive loop, as app->running_state might not change anymore...

Yeah, let's not do that.

If line 1485 of shell_app_dispose() is indeed what's crashing,
then that would mean that app->running_state is non-NULL but
app->running_state->windows is NULL. This doesn't seem to be meant to
happen: we can see that in window_backed_app_get_window(), there's an
assertion that if app->running_state is non-NULL, then
app->running_state->windows is meant to be non-NULL too.

A common feature of upstream bugs 750 and 822 is that
_shell_app_remove_window() line 1110 is in the stack trace: this means
the ShellApp is being disposed while shell_app_sync_running_state() is
still running. At this point in _shell_app_remove_window(), window has
already been removed from app->running_state->windows, but
app->running_state has not yet been cleared: so the invariant that
app->running_state is only non-NULL if app->running_state->windows is also
non-NULL does not hold, and indeed in both those upstream bugs we seem
to have a violation of that invariant, causing a crash when user code
disposes the ShellApp in response to one of its signals.

I think the solution is probably to stop believing that
app->running_state != NULL implies app->running_state->windows != NULL,
and check for the latter whenever we need it; but the refcounting of the
ShellApp still seems suspicious, so I'm hoping for input from upstream
before uploading anything for this.

smcv

Bug#927162: gnome-shell segfaults in libst-1.0.so

[Eloston]

After looking at the TopIcons code at the line indicated in journalctl, I am
able to reproduce the crash with the following:

1. Open Looking Glass (lg)
2. Run the following:

a = new St.Widget();
a.destroy();
a.get_theme_node();

After running the third line, gnome-shell will crash.

The second line was borrowed from the TopIcons code at line 121 of
/usr/share/gnome-shell/extensions/topic...@phocean.net/extension.js

On Tue, 2019-04-16 at 22:00 +0100, Simon McVittie wrote:
> Control: retitle -1 gnome-shell: intermittent segfault in
> st_widget_get_theme_node() at st-widget.c:603
> Control: forwarded -1 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1018
>
> On Mon, 15 Apr 2019 at 12:12:36 -0700, Eloston wrote:
> > Just using GNOME normally causes the crash to happen.
>
> This is probably going to make it hard to fix the crash or know whether
> it's been fixed, unfortunately. Is there anything you can do that seems
> to make it more likely to happen?
>
> Roughly how often is this happening, in how much use of GNOME?
>
> Is there anything (for instance an upgrade of a package or some packages)
> that coincides with this starting to happen?
>
> > It seems to happen randomly, more so on Wayland. I haven't been able
> > to
> > pinpoint any specific application, extension, or setting.
>
> Does this still happen if you disable all Shell extensions?
>
> What extensions are you normally using?
>
> > I have had this crash happen multiple times on Wayland and X11; this is the
> > first crash where I was able to get a coredump.
>
> Are you using a core-dump-capturing service like systemd-coredump? If
> not, please install systemd-coredump, gdb, gnome-shell-dbgsym (see
> ;) and debug symbols for any
> libraries that appear in the stack trace after you get one. After a crash,
> you should be able to use "coredumpctl gdb" to inspect the core dump,
> and "bt" to get a C-level backtrace (not the same as the Javascript
> backtrace that was logged).
>
> > different each time the crash occurs, e.g. this is the first time I've
> > seen TopIcons show up in the trace. Everything else looks the same.
>
> Please could you quote a few of these things that look the same so that
> we have an overview of what's happening, how the crashes are similar and
> how they're different?
>
> There's a limit to how much information I can extract from the core
> dump, because I'm not running the same versions of everything that you
> are, but this is a start:
>
> (gdb) bt
> #0  0x7f1af86f5ae8 in st_widget_get_theme_node (widget=) at
> ../src/st/st-widget.c:603
> #1  0x7ffdf9b077e0 in  ()
> #2  0x7ffdf9b07908 in  ()
> #3  0x7ffdf9b077e0 in  ()
> #4  0x in  ()
>
> Line 603 is this:
>
> StThemeNode *
> st_widget_get_theme_node (StWidget *widget)
> {
>   StWidgetPrivate *priv = st_widget_get_instance_private (widget);
>
>   if (priv->theme_node == NULL)<--- 603
> {
>   StThemeContext *context;
>
> so presumably something is calling st_widget_get_theme_node() on a widget
> that has been freed or is an invalid pointer - but gdb couldn't decode the
> rest of the stack, so I can't tell what called it.
>
> There's an upstream patch
>  that
> should make this less likely to crash, although it isn't really a full
> solution (something somewhere is still wrong, but we can't tell what).
>
> smcv

Bug#927250: golang-github-getlantern-errors: FTBFS in sid (missing build-depends)

[Santiago Vila]

Package: src:golang-github-getlantern-errors
Version: 0.0~git20190325.abdb3e3-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in sid but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=golang --with=golang
   dh_update_autotools_config -i -O--buildsystem=golang
   dh_autoreconf -i -O--buildsystem=golang
   dh_auto_configure -i -O--buildsystem=golang
   dh_auto_build -i -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go install 
-gcflags=all=\"-trimpath=/<>/golang-github-getlantern-errors-0.0\~git20190325.abdb3e3/obj-x86_64-linux-gnu/src\"
 
-asmflags=all=\"-trimpath=/<>/golang-github-getlantern-errors-0.0\~git20190325.abdb3e3/obj-x86_64-linux-gnu/src\"
 -v -p 1 github.com/getlantern/errors
src/github.com/getlantern/hidden/hidden.go:11:2: cannot find package 
"github.com/getlantern/hex" in any of:
/usr/lib/go-1.11/src/github.com/getlantern/hex (from $GOROOT)
/<>/obj-x86_64-linux-gnu/src/github.com/getlantern/hex 
(from $GOPATH)
dh_auto_build: cd obj-x86_64-linux-gnu && go install 
-gcflags=all=\"-trimpath=/<>/golang-github-getlantern-errors-0.0\~git20190325.abdb3e3/obj-x86_64-linux-gnu/src\"
 
-asmflags=all=\"-trimpath=/<>/golang-github-getlantern-errors-0.0\~git20190325.abdb3e3/obj-x86_64-linux-gnu/src\"
 -v -p 1 github.com/getlantern/errors returned exit code 1
make: *** [debian/rules:4: build-indep] Error 1
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


Looks like a missing build-depends to me.

Thanks.

Bug#927251: golang-github-getlantern-hidden: FTBFS in sid (missing build-depends)

[Santiago Vila]

Package: src:golang-github-getlantern-hidden
Version: 0.0~git20190325.f02dbb0-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in sid but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=golang --with=golang
   dh_update_autotools_config -i -O--buildsystem=golang
   dh_autoreconf -i -O--buildsystem=golang
   dh_auto_configure -i -O--buildsystem=golang
   dh_auto_build -i -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go install 
-gcflags=all=\"-trimpath=/<>/golang-github-getlantern-hidden-0.0\~git20190325.f02dbb0/obj-x86_64-linux-gnu/src\"
 
-asmflags=all=\"-trimpath=/<>/golang-github-getlantern-hidden-0.0\~git20190325.f02dbb0/obj-x86_64-linux-gnu/src\"
 -v -p 1 github.com/getlantern/hidden
src/github.com/getlantern/hidden/hidden.go:11:2: cannot find package 
"github.com/getlantern/hex" in any of:
/usr/lib/go-1.11/src/github.com/getlantern/hex (from $GOROOT)
/<>/obj-x86_64-linux-gnu/src/github.com/getlantern/hex 
(from $GOPATH)
dh_auto_build: cd obj-x86_64-linux-gnu && go install 
-gcflags=all=\"-trimpath=/<>/golang-github-getlantern-hidden-0.0\~git20190325.f02dbb0/obj-x86_64-linux-gnu/src\"
 
-asmflags=all=\"-trimpath=/<>/golang-github-getlantern-hidden-0.0\~git20190325.f02dbb0/obj-x86_64-linux-gnu/src\"
 -v -p 1 github.com/getlantern/hidden returned exit code 1
make: *** [debian/rules:4: build-indep] Error 1
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


Looks like a missing build-depends to me.

Thanks.

Bug#926212: gnome-shell crashed: segfault in libgnome-shell.so after printing email from evolution

[Simon McVittie]

Control: retitle -1 gnome-shell crashed: segfault in libgnome-shell.so after 
printing email from evolution
Control: tags -1 + moreinfo
Control: forwarded -1 https://gitlab.gnome.org/GNOME/gnome-shell/issues/750

I'm retitling this bug to try to stop other people using it to represent
different segfaults, because after someone starts doing that it becomes
really difficult to disentangle who has which bug and which bugs have
been solved.

Upstream bug 750 seems particularly similar.

On Tue, 02 Apr 2019 at 08:11:23 +0200, Guenter Grodotzki wrote:
> [39719.061358] gnome-shell[1279]: segfault at 0 ip 7fd4fa6ae3bf sp
> 7ffcf4dbaea0 error 4 in libgnome-shell.so[7fd4fa6a6000+1f000]

How often has this happened? Is it reproducible, or is it something
that happened once and has not recurred?

On Fri, 05 Apr 2019 at 22:01:58 +0200, Bernhard Übelacker wrote:
> As this information is still kind of small, you might consider
> to install a coredump collector like systemd-coredump.
> That way you could list crashes of the current boot by:
> coredumpctl list
> And some more information is entered into journal that would
> help a lot to triage such crashes ("Stack trace of thread...".
> journalctl --no-pager
> 
> Even better would be if you could install the debug symbol
> packages e.g. gnome-shell-dbgsym like described in [1].
> Then following commands should print a backtrace
> with source line information.

This would be very useful information.

> Nevertheless, I tried if that little information brings
> us somewhere and I think it leads into function
> shell_app_dispose. There, I assume, we reach line 1485,
> unfortunately dereferencing a null pointer
> in app->running_state->windows.
>
> crash instruction  - start .init== diff
> 0x7fd4fa6ae3bf - 0x7fd4fa6a6000 == 0x83BF

How sure are you that the virtual memory area starting at 0x7fd4fa6a6000
starts with .init and not .text?

smcv

Processed: Re: Bug#926212: gnome-shell crashed: segfault in libgnome-shell.so after printing email from evolution

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 gnome-shell crashed: segfault in libgnome-shell.so after printing 
> email from evolution
Bug #926212 [gnome-shell] gnome-shell crashed (segfault)
Changed Bug title to 'gnome-shell crashed: segfault in libgnome-shell.so after 
printing email from evolution' from 'gnome-shell crashed (segfault)'.
> tags -1 + moreinfo
Bug #926212 [gnome-shell] gnome-shell crashed: segfault in libgnome-shell.so 
after printing email from evolution
Added tag(s) moreinfo.
> forwarded -1 https://gitlab.gnome.org/GNOME/gnome-shell/issues/750
Bug #926212 [gnome-shell] gnome-shell crashed: segfault in libgnome-shell.so 
after printing email from evolution
Set Bug forwarded-to-address to 
'https://gitlab.gnome.org/GNOME/gnome-shell/issues/750'.

-- 
926212: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926212
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#927162: gnome-shell segfaults in libst-1.0.so

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 gnome-shell: intermittent segfault in st_widget_get_theme_node() 
> at st-widget.c:603
Bug #927162 [gnome-shell] gnome-shell segfaults in libst-1.0.so
Changed Bug title to 'gnome-shell: intermittent segfault in 
st_widget_get_theme_node() at st-widget.c:603' from 'gnome-shell segfaults in 
libst-1.0.so'.
> forwarded -1 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1018
Bug #927162 [gnome-shell] gnome-shell: intermittent segfault in 
st_widget_get_theme_node() at st-widget.c:603
Set Bug forwarded-to-address to 
'https://gitlab.gnome.org/GNOME/gnome-shell/issues/1018'.

-- 
927162: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927162
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#927162: gnome-shell segfaults in libst-1.0.so

[Simon McVittie]

Control: retitle -1 gnome-shell: intermittent segfault in 
st_widget_get_theme_node() at st-widget.c:603
Control: forwarded -1 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1018

On Mon, 15 Apr 2019 at 12:12:36 -0700, Eloston wrote:
> Just using GNOME normally causes the crash to happen.

This is probably going to make it hard to fix the crash or know whether
it's been fixed, unfortunately. Is there anything you can do that seems
to make it more likely to happen?

Roughly how often is this happening, in how much use of GNOME?

Is there anything (for instance an upgrade of a package or some packages)
that coincides with this starting to happen?

> It seems to happen randomly, more so on Wayland. I haven't been able 
> to
> pinpoint any specific application, extension, or setting.

Does this still happen if you disable all Shell extensions?

What extensions are you normally using?

> I have had this crash happen multiple times on Wayland and X11; this is the
> first crash where I was able to get a coredump.

Are you using a core-dump-capturing service like systemd-coredump? If
not, please install systemd-coredump, gdb, gnome-shell-dbgsym (see
) and debug symbols for any
libraries that appear in the stack trace after you get one. After a crash,
you should be able to use "coredumpctl gdb" to inspect the core dump,
and "bt" to get a C-level backtrace (not the same as the Javascript
backtrace that was logged).

> different each time the crash occurs, e.g. this is the first time I've
> seen TopIcons show up in the trace. Everything else looks the same.

Please could you quote a few of these things that look the same so that
we have an overview of what's happening, how the crashes are similar and
how they're different?

There's a limit to how much information I can extract from the core
dump, because I'm not running the same versions of everything that you
are, but this is a start:

(gdb) bt
#0  0x7f1af86f5ae8 in st_widget_get_theme_node (widget=) at 
../src/st/st-widget.c:603
#1  0x7ffdf9b077e0 in  ()
#2  0x7ffdf9b07908 in  ()
#3  0x7ffdf9b077e0 in  ()
#4  0x in  ()

Line 603 is this:

StThemeNode *
st_widget_get_theme_node (StWidget *widget)
{
  StWidgetPrivate *priv = st_widget_get_instance_private (widget);

  if (priv->theme_node == NULL)<--- 603
{
  StThemeContext *context;

so presumably something is calling st_widget_get_theme_node() on a widget
that has been freed or is an invalid pointer - but gdb couldn't decode the
rest of the stack, so I can't tell what called it.

There's an upstream patch
 that
should make this less likely to crash, although it isn't really a full
solution (something somewhere is still wrong, but we can't tell what).

smcv

Bug#926315: marked as done (openssl: wget https://google.com fails in d-i)

[Debian Bug Tracking System]

Your message dated Tue, 16 Apr 2019 20:39:11 +
with message-id 
and subject line Bug#926315: fixed in openssl 1.1.1b-2
has caused the Debian Bug report #926315,
regarding openssl: wget https://google.com fails in d-i
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
926315: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926315
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openssl
Version: 1.1.1b-1
Severity: important

Dear Maintainer,

$ wget https://google.com

fails in Buster alpha installer, when used from a booted netinst iso
in a tty. It also means that fetch-url fails, and thus one cannot use
https preseeding.

A fix/workaround, is $ touch /usr/lib/ssl/openssl.cnf it appears that
openssl requires for that file to be present, and it cannot be a
dangling symlink. However, in udeb environment such file does not
exists. I guess that maybe libssl1.1-udeb should ship an empty
openssl.cnf there, or ship the regular deb's /etc/ssl/openssl.cnf in
/usr/lib/ssl/openssl.cnf in the udeb.

Regards,

Dimitri.
--- End Message ---
--- Begin Message ---
Source: openssl
Source-Version: 1.1.1b-2

We believe that the bug you reported is fixed in the latest version of
openssl, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 926...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Kurt Roeckx  (supplier of updated openssl package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 16 Apr 2019 21:31:11 +0200
Source: openssl
Architecture: source
Version: 1.1.1b-2
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenSSL Team 
Changed-By: Kurt Roeckx 
Closes: 923516 926315
Changes:
 openssl (1.1.1b-2) unstable; urgency=medium
 .
   * Fix BUF_MEM regression (Closes: #923516)
   * Fix error when config can't be opened (Closes: #926315)
   * Ship an openssl.cnf in libssl1.1-udeb.dirs
Checksums-Sha1:
 b188b210cd0138d919ca730ad7cb7dc253f1d436 2614 openssl_1.1.1b-2.dsc
 f74b62e6645be8db6c3f7a9e95a6f904f5be4292 87392 openssl_1.1.1b-2.debian.tar.xz
 d05412d063d01c067414bdf3b8840d1dd992b733 6983 openssl_1.1.1b-2_source.buildinfo
Checksums-Sha256:
 4596cc5147ce07cc9504c2ed65076f1556ced9b31c3d035b049035af0e72f6b4 2614 
openssl_1.1.1b-2.dsc
 2f29be77334f597dd0ffc59be036fe5ae9e01c760b38e1fbe92197eae6d90752 87392 
openssl_1.1.1b-2.debian.tar.xz
 2655e4cf5fa3f072d3c51a14471e531ff19e70cc790797059aca0532a44e07a3 6983 
openssl_1.1.1b-2_source.buildinfo
Files:
 603c59d73fa9eaf266b704b4b2a09e3f 2614 utils optional openssl_1.1.1b-2.dsc
 2ffa90b8210c33157e9e63ca8a3c2dd2 87392 utils optional 
openssl_1.1.1b-2.debian.tar.xz
 47c925025f3c51d635abb5f3516a76b8 6983 utils optional 
openssl_1.1.1b-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEUWHm1ANgDdycoJP748TdzR5MEkQFAly2Nq4ACgkQ48TdzR5M
EkQoyhAAs7tBfAz73ltpdNzdmsRiFbG21aDwNbI0bWyXBYEOxSHSla59gd4aE3Iy
pKAFr8R8vwJ7qKGR2S/L9Y+47KQbDWvCBTr/4PYRWgS7BjAw65PgvLX5IWBuHONR
UcAnc2SvvD2q4+876ybeo2HNh8KI6ciTIJcb9H6wced9fdEWicZ6KYZCJIjz99i0
WPCAVbw6B+LlN+fvO05TN3bPauqmLm0XAT9dNsh7k8m2FBhu9KY3x3/5KzkXHDjO
cm7AGCINNEF9u8WDJuKDM/kMpFR+wVeZSHEdm2PQj+kdCteBBcx5AyW2EyhANAf0
XsORI3NUn+8UxTpGxEnCa/Pn4wigzZZEBZASZMjmHz2IUsbIW0wkfVFsn4s9ZXZY
nmYLhoSMbi9/ug1BweZAKr9O/+c/emISS0eTVqTu8iUrtyVmE7sD0Fg/Fxo3kGu/
ztLmh4nIJo4tTMIfESup57M12ammkNrGl+obVDJthnFRKf9dzyNC/kaivdVCPBiE
+iWks7XXd56XN+Y1gF3V3FCh0hVwfLPtAy8j7HDI87oerlodP6ZKcV0T9WQvT97p
jvm/0UpDK1S1Gmo3PARyCcInT1yR9ciiRARVBy+xdIdzIxKvqaze1myQJesfDgax
HcaAEaopLBUhNC8BKkaZ+J2MpEj9JSoi3QnBRolm5VgiVc7B+Po=
=lwuV
-END PGP SIGNATURE End Message ---

Processed: reassign 927243 to javahelper ..., affects 927243, reassign 927245 to javahelper ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 927243 javahelper
Bug #927243 [src:jtb] jtb: FTBFS (jh_build: Cannot find "EDU")
Bug reassigned from package 'src:jtb' to 'javahelper'.
No longer marked as found in versions jtb/1.4.12-1.1.
Ignoring request to alter fixed versions of bug #927243 to the same values 
previously set
> retitle 927243 jh_build: Regression in handling directories in d/javabuild
Bug #927243 [javahelper] jtb: FTBFS (jh_build: Cannot find "EDU")
Changed Bug title to 'jh_build: Regression in handling directories in 
d/javabuild' from 'jtb: FTBFS (jh_build: Cannot find "EDU")'.
> affects 927243 jtb caveconverter
Bug #927243 [javahelper] jh_build: Regression in handling directories in 
d/javabuild
Added indication that 927243 affects jtb and caveconverter
> reassign 927245 javahelper
Bug #927245 [src:caveconverter] caveconverter: FTBFS (jh_build: Cannot find 
"caveconverter")
Bug reassigned from package 'src:caveconverter' to 'javahelper'.
No longer marked as found in versions caveconverter/0~20170114-4.
Ignoring request to alter fixed versions of bug #927245 to the same values 
previously set
> forcemerge 927243 927245
Bug #927243 [javahelper] jh_build: Regression in handling directories in 
d/javabuild
Bug #927245 [javahelper] caveconverter: FTBFS (jh_build: Cannot find 
"caveconverter")
Added indication that 927245 affects jtb,caveconverter
Merged 927243 927245
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
927243: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927243
927245: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927245
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#927245: caveconverter: FTBFS (jh_build: Cannot find "caveconverter")

[Santiago Vila]

Package: src:caveconverter
Version: 0~20170114-4
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules binary-indep
dh --with javahelper binary-indep
dh: Compatibility levels before 9 are deprecated (level 7 in use)
   dh_update_autotools_config -i
   dh_auto_configure -i
dh_auto_configure: Compatibility levels before 9 are deprecated (level 7 in use)
   jh_linkjars -i
   dh_auto_build -i
dh_auto_build: Compatibility levels before 9 are deprecated (level 7 in use)
ant -Duser.name debian
Buildfile: /<>/build.xml

clean.tests:

clean:

init:
 [echo] JAVA_HOME = /usr/lib/jvm/default-java
[mkdir] Created dir: /<>/build/classes
[mkdir] Created dir: /<>/dist
[mkdir] Created dir: /<>/build/test/data/private

compile:
[javac] Compiling 24 source files to /<>/build/classes
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 6
[javac] warning: [options] source value 6 is obsolete and will be removed 
in a future release
[javac] warning: [options] target value 1.6 is obsolete and will be removed 
in a future release
[javac] warning: [options] To suppress warnings about obsolete options, use 
-Xlint:-options.
[javac] Note: 
/<>/src/footleg/cavesurvey/data/reader/PocketTopoParser.java uses 
or overrides a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] 4 warnings
 [copy] Copying 9 files to 
/<>/build/classes/footleg/cavesurvey/gui/swing/images
 [copy] Copying 1 file to 
/<>/build/classes/footleg/cavesurvey/gui

jar:

makejar:
  [jar] Building jar: /<>/build/CaveConverter.jar

guijar:

makejar:
  [jar] Building jar: /<>/build/CaveConverterGUI.jar

zip:
  [zip] Building zip: /<>/dist/CaveConverter.zip

zipsrc:
  [zip] Building zip: /<>/dist/CaveConverter-src.zip

instrument.java:
[cobertura-instrument] 00:15:17,186 |-INFO in 
ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource 
[logback-test.xml]
[cobertura-instrument] 00:15:17,187 |-INFO in 
ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource 
[logback.groovy]
[cobertura-instrument] 00:15:17,187 |-INFO in 
ch.qos.logback.classic.LoggerContext[default] - Found resource [logback.xml] at 
[jar:file:/usr/share/java/cobertura-2.1.1.jar!/logback.xml]
[cobertura-instrument] 00:15:17,189 |-WARN in 
ch.qos.logback.classic.LoggerContext[default] - Resource [logback.xml] occurs 
multiple times on the classpath.
[cobertura-instrument] 00:15:17,189 |-WARN in 
ch.qos.logback.classic.LoggerContext[default] - Resource [logback.xml] occurs 
at [jar:file:/usr/share/java/cobertura-2.1.1.jar!/logback.xml]
[cobertura-instrument] 00:15:17,189 |-WARN in 
ch.qos.logback.classic.LoggerContext[default] - Resource [logback.xml] occurs 
at [jar:file:/usr/share/java/cobertura.jar!/logback.xml]
[cobertura-instrument] 00:15:17,221 |-INFO in 
ch.qos.logback.core.joran.spi.ConfigurationWatchList@6393bf8b - URL 
[jar:file:/usr/share/java/cobertura-2.1.1.jar!/logback.xml] is not of type file
[cobertura-instrument] 00:15:17,274 |-INFO in 
ch.qos.logback.classic.joran.action.ConfigurationAction - debug attribute not 
set
[cobertura-instrument] 00:15:17,276 |-INFO in 
ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender 
of type [ch.qos.logback.core.ConsoleAppender]
[cobertura-instrument] 00:15:17,292 |-INFO in 
ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [STDOUT]
[cobertura-instrument] 00:15:17,302 |-INFO in 
ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default 
type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] 
property
[cobertura-instrument] 00:15:17,381 |-INFO in 
ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger 
[net.sourceforge.cobertura] to INFO
[cobertura-instrument] 00:15:17,381 |-INFO in 
ch.qos.logback.classic.joran.action.RootLoggerAction - Setting level of ROOT 
logger to DEBUG
[cobertura-instrument] 00:15:17,381 |-INFO in 
ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named 
[STDOUT] to Logger[ROOT]
[cobertura-instrument] 00:15:17,385 |-INFO in 
ch.qos.logback.classic.joran.action.ConfigurationAction - End of configuration.
[cobertura-instrument] 00:15:17,387 |-INFO in 
ch.qos.logback.classic.joran.JoranConfigurator@76d7881e - Registering current 
configuration as safe fallback point
[cobertura-instrument] 
[cobertura-instrument] Cobertura 2.1.1 - GNU GPL License (NO WARRANTY) - See 
COPYRIGHT file
[cobertura-instrument] [INFO] Cobertura: Saved information on 55 classes.
[cobertura-instrument] [INFO] Cobertura: Saved information on 55 classes.

init.tests:
[mkdir] Created dir: /<>/build/test_classes
[mkdir] Created dir: /<>/build/reports

compile.test:
[javac] Compiling 18 source files to 

Bug#927244: mina: FTBFS (Unknown option: source 1.7 -target 1.7)

[Santiago Vila]

Package: src:mina
Version: 1.1.7.dfsg-12
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --with javahelper
   dh_update_autotools_config -i
   dh_autoreconf -i
   jh_linkjars -i
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
# Build the packages
( CLASSPATH=/usr/share/java/slf4j-api.jar jh_build -J -o"-source 1.7 -target 
1.7" mina-core.jar core/src/main/java/  )
Unknown option: source 1.7 -target 1.7
jh_build: unknown option or error during option parsing; aborting
make[1]: *** [debian/rules:43: override_dh_auto_build] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:39: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/mina.html

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.

Bug#921232: Tracking it down

[Jo Shields]

Seems fixed in cd70e9cf2adc03681dbb919d97063d8ad84b0a4c, will apply this
against Debian packaging & upload

On 15/04/2019 22:55, Joseph Shields wrote:
> This is fine in master, but I can repro it with an otherwise clean upstream 
> git tag w/ our 4 s390x backports. Bisecting.

Bug#927243: jtb: FTBFS (jh_build: Cannot find "EDU")

[Santiago Vila]

Package: src:jtb
Version: 1.4.12-1.1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --with javahelper
   dh_update_autotools_config -i
   dh_auto_configure -i
   jh_linkjars -i
   dh_auto_build -i
ant -Duser.name debian
Buildfile: /<>/build.xml

echo_jtb_props:
 [echo] jtb_proj_dir=/<>
 [echo] jtb_last_version=1.4.11
 [echo] jtb_curr_version=1.4.12
 [echo] jtb_bs_jar=/<>/lib/jtb132.jar
 [echo] jtblv=/<>/lib/jtb-1.4.11.jar
 [echo] jtb_last_jar=/<>/lib/jtb-1.4.11.jar
 [echo] jtb_new_jar=/<>/lib/new_jtb-1.4.12.jar
 [echo] jtb_prev_jar=/<>/lib/jtb-1.4.12.jar
 [echo] jtb_ok_jar=/<>/lib/jtb-1.4.12.jar

echo_javacc_props:
 [echo] 
javacc_imp_dir=/usr/share/maven-repo/net/java/dev/javacc/javacc/debian
 [echo] 
javacc_ok_jar=/usr/share/maven-repo/net/java/dev/javacc/javacc/debian/javacc-debian.jar
 [echo] javacc_main=org.javacc.parser.Main

echo_all_props:

clean_javacc_gen_files:

clean_jtb_gen_files:

clean_all_gen_files:

process_jtbgram.jtb:
 [java] JTB version 1.4.12
 [java] JTB:  Reading jtb input file 
/<>/src/EDU/purdue/jtb/jtbgram.jtb...
 [java] JTB:  jtb input file parsed successfully.
 [java] JTB:  jj output file 
"/<>/src/EDU/purdue/jtb/jtb.out.jj" generated.
 [java] JTB:  base node class files generated into directory 
"/<>/src/EDU/purdue/jtb/syntaxtree".
 [java] JTB:  134 syntax tree node class files generated into directory 
"/<>/src/EDU/purdue/jtb/syntaxtree".
 [java] 
 [java] JTB:  Visitor interface "IRetArguVisitor.java" generated into 
directory "/<>/src/EDU/purdue/jtb/visitor".
 [java] JTB:  Visitor interface "IVoidVisitor.java" generated into 
directory "/<>/src/EDU/purdue/jtb/visitor".
 [java] JTB:  Visitor interface "IRetVisitor.java" generated into directory 
"/<>/src/EDU/purdue/jtb/visitor".
 [java] JTB:  Visitor interface "IVoidArguVisitor.java" generated into 
directory "/<>/src/EDU/purdue/jtb/visitor".
 [java] JTB:  Visitor class "DepthFirstRetArguVisitor.java" generated into 
directory "/<>/src/EDU/purdue/jtb/visitor".
 [java] JTB:  Visitor class "DepthFirstRetVisitor.java" generated into 
directory "/<>/src/EDU/purdue/jtb/visitor".
 [java] JTB:  Visitor class "DepthFirstVoidArguVisitor.java" generated into 
directory "/<>/src/EDU/purdue/jtb/visitor".
 [java] JTB:  Visitor class "DepthFirstVoidVisitor.java" generated into 
directory "/<>/src/EDU/purdue/jtb/visitor".
 [java] 

process_jtb.out.jj:
 [java] Java Compiler Compiler Version 5.0 (Parser Generator)
 [java] (type "javacc" with no arguments for help)
 [java] Reading from file /<>/src/EDU/purdue/jtb/jtb.out.jj . 
. .
 [java] Warning: Line 119, Column 1: Command line setting of 
"OUTPUT_DIRECTORY" modifies option value in file.
 [java] File "TokenMgrError.java" does not exist.  Will create one.
 [java] File "ParseException.java" does not exist.  Will create one.
 [java] File "Token.java" does not exist.  Will create one.
 [java] File "JavaCharStream.java" does not exist.  Will create one.
 [java] Parser generated with 0 errors and 1 warnings.

copy_specific_token_for_jtb:
 [copy] Copying 1 file to /<>/src/EDU/purdue/jtb/parser

generate_all:

generate_all+compile_java:

compile_java:
[javac] Compiling 234 source files to /<>/bin
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 7
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] 1 warning

build_new_jtb_jar:

check_jtb_jar:

make_new_jtb_jar:
  [jar] Building jar: /<>/lib/new_jtb-1.4.12.jar

test_process_jtbgram.jtb:
 [java] JTB version 1.4.12
 [java] JTB:  Reading jtb input file 
/<>/src/EDU/purdue/jtb/jtbgram.jtb...
 [java] java.lang.NullPointerException
 [java] at 
EDU.purdue.jtb.parser.JTBToolkit.makeNodeToken(JTBParser.java:12271)
 [java] at 
EDU.purdue.jtb.parser.JTBParser.JavaCCOptions(JTBParser.java:288)
 [java] at 
EDU.purdue.jtb.parser.JTBParser.JavaCCInput(JTBParser.java:206)
 [java] at EDU.purdue.jtb.JTB.do_main(JTB.java:168)
 [java] at EDU.purdue.jtb.JTB.main(JTB.java:136)
 [java] 
 [java] /<>/src/EDU/purdue/jtb/jtbgram.jtb:  unexpected 
program error:  null
 [java] Please report this to JTB support 
(https://github.com/jtb-javacc/JTB)
 [java] 
 [java] java.lang.NullPointerException
 [java] at 
EDU.purdue.jtb.parser.JTBToolkit.makeNodeToken(JTBParser.java:12271)
 [java] at 
EDU.purdue.jtb.parser.JTBParser.JavaCCOptions(JTBParser.java:288)
 [java] at 
EDU.purdue.jtb.parser.JTBParser.JavaCCInput(JTBParser.java:206)
 [java] at EDU.purdue.jtb.JTB.do_main(JTB.java:168)
 [java] at 

Bug#925546: How to reproduce?

[Joonas Kylmälä]

Hi,

you can reproduce the issue by creating a file main.go with the content:


package main

import (
"html/template"
"net/http"
)


and then running in the same directory:

$ gocode -f=json --in=main.go autocomplete 12

Then to see the error log first kill the running gocode server and run

$ nohup gocode -s debug &

The error will be printed then to nohup.out file when you run "gocode
-f=json --in=main.go autocomplete 12"

I remember reading somewhere on the online that this issue is caused
because the library dependencies are compiled with a different golang
version than this binary. So yeah, I have not yet tried but maybe this
is fixed by just uploading a new compilation of the binary.

Joonas

Hilko Bengen:
> control: tag -1 moreinfo
> 
> Hi Joonas,
> 
> could you describe in more detail how I might be able to reproduce the
> error? Does it happen with any file?
> 
> Cheers,
> -Hilko
> 

Bug#926952: sa-exim: Unbuildable/uninstallable in sid

[Andreas Metzler]

On 2019-04-15 Magnus Holmgren  wrote:
> måndag 15 april 2019 kl. 19:46:14 CEST skrev  Andreas Metzler:
[l...]
> > I have not tested it but I suspect it might break even more when
> > spool_wireformat is set.

> Isn't it the case that if CHUNKING has been offered AND spool_wireformat is 
> set, then the body files are in an alternate format?

Yes that is true.

[...]
> So it seems that everything should work unless spool_wireformat=true
> *and* SARewriteBody: 1. How do I detect in sa-exim whether wire format
> is used for a given body file though?

-spool_file_wireformat in the -H file?

I just do not think the reports of breakage where with
spool_wireformat=true, true though. - Nobody mentioned it and it is not
something one set accidentaly.

I have just uploaded exim 4.92-6 to exoerimental which /should/
work with sa-exim, allowing you to debug properly.

cu Andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Processed: How to reproduce?

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #925546 [gocode] panic: Can't find the package clause
Ignoring request to alter tags of bug #925546 to the same tags previously set

-- 
925546: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925546
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#925546: How to reproduce?

[Hilko Bengen]

control: tag -1 moreinfo

Hi Joonas,

could you describe in more detail how I might be able to reproduce the
error? Does it happen with any file?

Cheers,
-Hilko

Processed: How to reproduce?

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #925546 [gocode] panic: Can't find the package clause
Added tag(s) moreinfo.

-- 
925546: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925546
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#921952: [Pkg-sass-devel] Bug#921952: Don't include in buster without proper commitment to update in stable

[Jonas Smedegaard]

control: severity -1 important

Quoting Aljoscha Lautenbach (2019-04-09 23:03:06)
> during the BSP in Gothenburg last weekend I discussed with Jonas how I 
> could help to put libsass back on track regarding its security status. 
> We agreed that the best move is to start with triaging the existing 
> Debian bugs and by identifying the CVE status in upstream's issue 
> tracker. [0]

@Aljoscha: Thanks for your initial work and - more so - for committing 
to help generally looking after these security issues in libsaass.

Due to the expansion of the libsass team with Aljoscha, I am lowering 
severity of this bugreport.

If the security team or others disagree, then please elaborate what you 
consider is needed.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Processed: Re: [Pkg-sass-devel] Bug#921952: Don't include in buster without proper commitment to update in stable

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #921952 [src:libsass] Don't include in buster without proper commitment to 
update in stable
Severity set to 'important' from 'serious'

-- 
921952: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921952
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#921952: [Pkg-sass-devel] Bug#921952: Don't include in buster without proper commitment to update in stable

[Jonas Smedegaard]

Quoting Xavier (2019-04-16 15:52:53)
> Hi all,
> 
> Some fixes proposed in
> https://salsa.debian.org/sass-team/libsass/merge_requests/1 :
> CVE-2018-19827, CVE-2019-6283, CVE-2019-6284 and CVE-2019-6286

Thanks for your help, Xavier.

This bugreport is however not to track specific bugs in libsass but to 
track the meta-issue of the general "health" of the maintenance.

Therefore, it is more helpful if you post concrete bugfixes not here but 
at bugreports for the concrete bugs (i.e. locate existing bugreports or 
file new bugreports for CVEs without a bugreport in Debian yet).

If you are interested in stepping up to help generally maintain libsass, 
then that wold be great - and we can talk about that in this bugreport.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Processed: cross-gcc-dev: gcc-9 patch application failure

[Debian Bug Tracking System]

Processing control commands:

> fixed 925950 230
Bug #925950 {Done: Helmut Grohne } [cross-gcc-dev] patches 
no longer apply for gcc-8 and gcc-9
Ignoring request to alter fixed versions of bug #925950 to the same values 
previously set

-- 
925950: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925950
927230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927230
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#927229: exadrums: FTBFS on armel mips mipsel because of missing -latomic

[Nicolas Boulenguez]

Package: exadrums
Version: 0.3.0-1
Severity: serious
Justification: failure to build from scratch on release architecture

Hello.

The package source fails to build from scratch on armel mips mipsel
(as well as other non released architectures)

https://buildd.debian.org/status/package.php?p=exadrums=experimental

with the following message

/usr/bin/ld: /usr/lib/gcc/.../libexadrums.so: undefined reference to 
`__atomic_store_8'
/usr/bin/ld: /usr/lib/gcc/.../libexadrums.so: undefined reference to 
`__atomic_load_8'
/usr/bin/ld: /usr/lib/gcc/.../libexadrums.so: undefined reference to 
`__atomic_exchange_8'

The solution is most probably to add -pthread to both CXXFLAGS and
LDFLAGS. In LDFLAGS, it should come after --as-needed so the
dependency is only effective on architectures actually using these 3
symbols.

Bug#927227: golang-gopkg-sourcemap.v1: attempts internet communication during build?

[Gianfranco Costamagna]

Package: golang-gopkg-sourcemap.v1
Version: 1.0.5-1
Severity: serious

Hello, looks like the package is truing to communicate to internet during the 
build process...
this is forbidden by policy.

encoding/json
gopkg.in/sourcemap.v1
   dh_auto_test -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 
gopkg.in/sourcemap.v1 gopkg.in/sourcemap.v1/base64vlq
panic: Get http://code.jquery.com/jquery-2.0.3.min.map: dial tcp: lookup 
code.jquery.com on 10.222.128.2:53: no such host

goroutine 1 [running]:
gopkg.in/sourcemap%2ev1_test.init.0()

/<>/obj-x86_64-linux-gnu/src/gopkg.in/sourcemap.v1/consumer_test.go:20
 +0x161
FAILgopkg.in/sourcemap.v1   0.011s
=== RUN   TestEncodeDecode
--- PASS: TestEncodeDecode (0.00s)
PASS
ok  gopkg.in/sourcemap.v1/base64vlq 0.002s
dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 
gopkg.in/sourcemap.v1 gopkg.in/sourcemap.v1/base64vlq returned exit code 1
make: *** [debian/rules:4: build] Error 1
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2


(I discovered in Ubuntu, where the network is more strictly controlled)

thanks for having a look,

Gianfranco

Processed: Re: plymouth: upgrade fails: /usr/share/initramfs-tools/hooks/plymouth failed with return 134

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 fontconfig 2.12.6-0.1
Bug #927153 [plymouth] plymouth: upgrade fails: 
/usr/share/initramfs-tools/hooks/plymouth failed with return 134
Bug reassigned from package 'plymouth' to 'fontconfig'.
No longer marked as found in versions plymouth/0.9.4-1.1.
Ignoring request to alter fixed versions of bug #927153 to the same values 
previously set
Bug #927153 [fontconfig] plymouth: upgrade fails: 
/usr/share/initramfs-tools/hooks/plymouth failed with return 134
Marked as found in versions fontconfig/2.12.6-0.1.
> retitle -1 fontconfig: fc-cache with -y option is broken
Bug #927153 [fontconfig] plymouth: upgrade fails: 
/usr/share/initramfs-tools/hooks/plymouth failed with return 134
Changed Bug title to 'fontconfig: fc-cache with -y option is broken' from 
'plymouth: upgrade fails: /usr/share/initramfs-tools/hooks/plymouth failed with 
return 134'.
> affects -1 plymouth
Bug #927153 [fontconfig] fontconfig: fc-cache with -y option is broken
Added indication that 927153 affects plymouth

-- 
927153: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927153
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#927153: plymouth: upgrade fails: /usr/share/initramfs-tools/hooks/plymouth failed with return 134

[Vincent Lefevre]

Control: reassign -1 fontconfig 2.12.6-0.1
Control: retitle -1 fontconfig: fc-cache with -y option is broken
Control: affects -1 plymouth

On 2019-04-16 15:33:04 +0200, Sven Hartge wrote:
> On 16.04.19 15:12, Vincent Lefevre wrote:
> 
> > access("/var/tmp/mkinitramfs_0BRFs9//etc/fonts/conf.d/60-latin.conf", R_OK) 
> > = 0
> > stat("/var/tmp/mkinitramfs_0BRFs9//var/tmp/mkinitramfs_0BRFs9//etc/fonts/conf.d/60-latin.conf",
> >  0x7ffc35e33b50) = -1 ENOENT (No such file or directory)
> > openat(AT_FDCWD, 
> > "/var/tmp/mkinitramfs_0BRFs9//var/tmp/mkinitramfs_0BRFs9//etc/fonts/conf.d/60-latin.conf",
> >  O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
> > writev(2, [{iov_base="free(): double free detected in "..., iov_len=40}, 
> > {iov_base="\n", iov_len=1}], 2) = 41
> 
> My uneducated guess is, the problem is here. See how the prefix
> "/var/tmp/mkinitramfs_0BRFs9/" is applied twice, somehow?
> 
> I think this bug should be reassigned to fontconfig, with plymouth being
> affected by it.

OK.

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

Bug#921952: Don't include in buster without proper commitment to update in stable

[Xavier]

Hi all,

Some fixes proposed in
https://salsa.debian.org/sass-team/libsass/merge_requests/1 :
CVE-2018-19827, CVE-2019-6283, CVE-2019-6284 and CVE-2019-6286

Cheers,
Xavier

Bug#916347: epiphany-browser: Don't include in Buster

[Simon McVittie]

On Tue, 12 Mar 2019 at 18:54:32 -0400, Jeremy Bicha wrote:
> The current plan is to provide security updates for webkit2gtk for
> Debian 10 similar to how security support has been offered for Ubuntu
> 16.04 LTS and 18.04 LTS. It's best-effort: there is no guarantee that
> Debian will be able to provide security updates for the full normal
> life of Debian 10, but we'll try to do the updates as long as it seems
> practical to the ones doing the work.

Who is the "we" in this plan? (The GNOME team? The webkit2gtk maintainers?
The release team? The security team?)

How confident can we be that the necessary starting-point version is
going to get unblocked and included in buster? Is webkit2gtk 2.24 unblock
request  considered to be a prerequisite
for being able to do ongoing security updates to webkit2gtk in buster?

At the moment I'm not sure whether the desired solution to
epiphany-browser unblock request  is to
update epiphany-browser to 3.32.x, or to have it removed from buster.
I'm reasonably sure 3.31.x is not what we want to be shipping for 2 years,
though.

smcv

Bug#919868: marked as done (hebcal FTBFS on big endian: FAIL: hebcal-1 Segmentation fault)

[Debian Bug Tracking System]

Your message dated Tue, 16 Apr 2019 13:48:33 +
with message-id 
and subject line Bug#919868: fixed in hebcal 4.17-1
has caused the Debian Bug report #919868,
regarding hebcal FTBFS on big endian: FAIL: hebcal-1 Segmentation fault
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
919868: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919868
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hebcal
Version: 4.16-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=hebcal

...
FAIL: hebcal-1
==

Segmentation fault
...

Testsuite summary for hebcal 4.16

# TOTAL: 11
# PASS:  1
# SKIP:  0
# XFAIL: 0
# FAIL:  10
# XPASS: 0
# ERROR: 0

See tests/test-suite.log
Please report to hebcal-b...@sadinoff.com

make[5]: *** [Makefile:593: test-suite.log] Error 1



(m68k and powerpcspe are building with nocheck)
--- End Message ---
--- Begin Message ---
Source: hebcal
Source-Version: 4.17-1

We believe that the bug you reported is fixed in the latest version of
hebcal, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 919...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Barak A. Pearlmutter  (supplier of updated hebcal package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 16 Apr 2019 14:06:48 +0100
Source: hebcal
Binary: hebcal hebcal-dbgsym
Architecture: source amd64
Version: 4.17-1
Distribution: unstable
Urgency: medium
Maintainer: Shaya Potter 
Changed-By: Barak A. Pearlmutter 
Description:
 hebcal - A Perpetual Jewish Calendar
Closes: 919868
Changes:
 hebcal (4.17-1) unstable; urgency=medium
 .
   * remove upstreamed quilt patches
   * new upstream release (closes: #919868)
Checksums-Sha1:
 e02ca8be6af9edf4defd15cbfd0cba0c4af4459a 1839 hebcal_4.17-1.dsc
 c519a1778fc6d4038f00de4ae67e4b15810cd82d 321796 hebcal_4.17.orig.tar.xz
 967ad33f1498531de140a26272b1b1529df520e0 2092 hebcal_4.17-1.debian.tar.xz
 65bdf44b15831b32ab9eb02515b524191e4c409e 71680 hebcal-dbgsym_4.17-1_amd64.deb
 b8f10226ca2cd6bd405f38b109912d41b094a3e8 5625 hebcal_4.17-1_amd64.buildinfo
 5af0c20232af6924ff75e88b574966f742a8f686 158552 hebcal_4.17-1_amd64.deb
Checksums-Sha256:
 d6a81953f76dba8d94186660fd6d0eb5dbb81f0107458015542aef865478 1839 
hebcal_4.17-1.dsc
 5325de52bb132de5905283476b184e52d595d3d4618395bd6c7a7fff62aa085e 321796 
hebcal_4.17.orig.tar.xz
 eef93af48df44b061da310d921e8421e7a338b484f83df0453ae145a4f43eaca 2092 
hebcal_4.17-1.debian.tar.xz
 1f0178675ec6ebea5254bdd65336a6b5d040eea8c7600f35a65eb7286dace676 71680 
hebcal-dbgsym_4.17-1_amd64.deb
 94936434026d4a922f5204ff7785d39589a779aa00ba8bfdb12b87e2f13aa258 5625 
hebcal_4.17-1_amd64.buildinfo
 6f3ca80d3577fbec4241de45c788a6e5c2913fe085dd95db35a708d684f94b00 158552 
hebcal_4.17-1_amd64.deb
Files:
 def383136cefd604f80cbc906c64a2aa 1839 utils optional hebcal_4.17-1.dsc
 16bb4845f8f6ce7726183f662ce38f11 321796 utils optional hebcal_4.17.orig.tar.xz
 3771aabf7650c6b5a21d09decea8bb3e 2092 utils optional 
hebcal_4.17-1.debian.tar.xz
 7a2b005d22be9bc8c495ac9067bc38fb 71680 debug optional 
hebcal-dbgsym_4.17-1_amd64.deb
 5846ee6bd35bd16f7c0a64915918e89a 5625 utils optional 
hebcal_4.17-1_amd64.buildinfo
 5bec9cb69207229eff7d393805763f50 158552 utils optional hebcal_4.17-1_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEZPQp426hHMLZZlRvEltXR14ZDRgFAly12Q0ACgkQEltXR14Z
DRgVHxAAhuRZyFbAQPbf8+/UdYiELH9t2etWJ3LfDP19o5Ma+jpqgV+Rs5RcBshC
AhHRVRo0Y8FP4pk9Zu+txGkNffODUH1VViEspM9WlbRon0qLDU9kBHgyoQwclB/4
MKcbP9GcBSDeZ94KbOO72UCfM6Y8SySRjM4yAWKh/C+yHuK5D4GR1KP4YBp39Ijt
skF2Gx8zFbiO56ezEiHZ4n6iVoTMoufU/SSlDTq/Vn2gD2hQvDGwM92EZ5EzbcsX
2smeHRhWDb0YdMzJp3xPAR+43+bZ1p1hsQE58pxaI+hZMMajSpTSn9MTfxkRJNbr
MvenVqA6jBMDgfUYhnR3IK00cVwE9K0TuChdTEP6KfEGc7uehdx9+fDeaBCb/+4k
D2pR+bLKKgtz2oyLwIVHjaa5noEozTKgyXIcpdtesPGAkCLAv9e5APeFQsfkl1ty

Processed: unarchiving 916347

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> unarchive 916347
Bug #916347 {Done: Jeremy Bicha } [src:epiphany-browser] 
epiphany-browser: Don't include in Buster
Unarchived Bug 916347
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
916347: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916347
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#927153: plymouth: upgrade fails: /usr/share/initramfs-tools/hooks/plymouth failed with return 134

[Sven Hartge]

On 16.04.19 15:12, Vincent Lefevre wrote:

> access("/var/tmp/mkinitramfs_0BRFs9//etc/fonts/conf.d/60-latin.conf", R_OK) = > 0
> stat("/var/tmp/mkinitramfs_0BRFs9//var/tmp/mkinitramfs_0BRFs9//etc/fonts/conf.d/60-latin.conf",
>  0x7ffc35e33b50) = -1 ENOENT (No such file or directory)
> openat(AT_FDCWD, 
> "/var/tmp/mkinitramfs_0BRFs9//var/tmp/mkinitramfs_0BRFs9//etc/fonts/conf.d/60-latin.conf",
>  O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
> writev(2, [{iov_base="free(): double free detected in "..., iov_len=40}, 
> {iov_base="\n", iov_len=1}], 2) = 41

My uneducated guess is, the problem is here. See how the prefix
"/var/tmp/mkinitramfs_0BRFs9/" is applied twice, somehow?

I think this bug should be reassigned to fontconfig, with plymouth being
affected by it.

Grüße,
Sven.




signature.asc
Description: OpenPGP digital signature

Bug#927153: plymouth: upgrade fails: /usr/share/initramfs-tools/hooks/plymouth failed with return 134

[Vincent Lefevre]

On 2019-04-16 14:56:12 +0200, Sven Hartge wrote:
> Interesting. Care to run it with strace to see exactly where it barfs?

execve("/usr/bin/fc-cache", ["fc-cache", "-v", "-s", "-y", 
"/var/tmp/mkinitramfs_0BRFs9"], 0x7ffed17f88b0 /* 131 vars */) = 0
brk(NULL)   = 0x56509ca3d000
access("/etc/ld.so.preload", R_OK)  = 0
openat(AT_FDCWD, "/etc/ld.so.preload", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
close(3)= 0
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=176506, ...}) = 0
mmap(NULL, 176506, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fb7b8e52000
close(3)= 0
openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/libfontconfig.so.1", 
O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0Pn\0\0\0\0\0\0"..., 832) 
= 832
fstat(3, {st_mode=S_IFREG|0644, st_size=282016, ...}) = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7fb7b8e5
mmap(NULL, 2377768, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0x7fb7b8c0b000
mprotect(0x7fb7b8c49000, 2097152, PROT_NONE) = 0
mmap(0x7fb7b8e49000, 28672, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x3e000) = 0x7fb7b8e49000
close(3)= 0
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libpthread.so.0", O_RDONLY|O_CLOEXEC) = 
3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0@l\0\0\0\0\0\0"..., 832) 
= 832
fstat(3, {st_mode=S_IFREG|0755, st_size=146968, ...}) = 0
mmap(NULL, 132288, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7fb7b8bea000
mmap(0x7fb7b8bf, 61440, PROT_READ|PROT_EXEC, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x6000) = 0x7fb7b8bf
mmap(0x7fb7b8bff000, 24576, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 
0x15000) = 0x7fb7b8bff000
mmap(0x7fb7b8c05000, 8192, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1a000) = 0x7fb7b8c05000
mmap(0x7fb7b8c07000, 13504, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7fb7b8c07000
close(3)= 0
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\260A\2\0\0\0\0\0"..., 
832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=1824496, ...}) = 0
mmap(NULL, 1837056, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7fb7b8a29000
mprotect(0x7fb7b8a4b000, 1658880, PROT_NONE) = 0
mmap(0x7fb7b8a4b000, 1343488, PROT_READ|PROT_EXEC, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x22000) = 0x7fb7b8a4b000
mmap(0x7fb7b8b93000, 311296, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 
0x16a000) = 0x7fb7b8b93000
mmap(0x7fb7b8be, 24576, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1b6000) = 0x7fb7b8be
mmap(0x7fb7b8be6000, 14336, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7fb7b8be6000
close(3)= 0
openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/libfreetype.so.6", 
O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0`\1\1\0\0\0\0\0"..., 
832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=716728, ...}) = 0
mmap(NULL, 2811792, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0x7fb7b877a000
mprotect(0x7fb7b8822000, 2097152, PROT_NONE) = 0
mmap(0x7fb7b8a22000, 28672, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xa8000) = 0x7fb7b8a22000
close(3)= 0
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libexpat.so.1", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\A\0\0\0\0\0\0"..., 
832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=243840, ...}) = 0
mmap(NULL, 245920, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7fb7b873d000
mprotect(0x7fb7b8741000, 221184, PROT_NONE) = 0
mmap(0x7fb7b8741000, 135168, PROT_READ|PROT_EXEC, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x4000) = 0x7fb7b8741000
mmap(0x7fb7b8762000, 81920, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 
0x25000) = 0x7fb7b8762000
mmap(0x7fb7b8777000, 12288, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x39000) = 0x7fb7b8777000
close(3)= 0
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libz.so.1", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\320#\0\0\0\0\0\0"..., 
832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=121280, ...}) = 0
mmap(NULL, 2216336, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0x7fb7b851f000
mprotect(0x7fb7b853b000, 2097152, PROT_NONE) = 0
mmap(0x7fb7b873b000, 8192, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1c000) = 0x7fb7b873b000
close(3)= 0
openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/libpng16.so.16", 
O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0Pi\0\0\0\0\0\0"..., 832) 
= 832

Bug#927153: plymouth: upgrade fails: /usr/share/initramfs-tools/hooks/plymouth failed with return 134

[Sven Hartge]

On 16.04.19 14:32, Vincent Lefevre wrote:
> On 2019-04-16 01:53:03 +0200, Sven Hartge wrote:
>> Try running the following commands as root:
>>
>> mkdir -p /var/tmp/mkinitramfs_0BRFs9/etc/fonts/conf.d
>> cp -a /etc/fonts/fonts.conf /var/tmp/mkinitramfs_0BRFs9/etc/fonts
>> cp -rL /etc/fonts/conf.d/60-latin.conf 
>> /var/tmp/mkinitramfs_0BRFs9/etc/fonts/conf.d
>> mkdir -p /var/tmp/mkinitramfs_0BRFs9/var/cache/fontconfig
>> mkdir -p /var/tmp/mkinitramfs_0BRFs9/usr/local/share/fonts
>> mkdir -p /var/tmp/mkinitramfs_0BRFs9/usr/share/fonts/truetype/dejavu
>> cp -a /usr/share/fonts/truetype/dejavu/DejaVuSerif.ttf 
>> /var/tmp/mkinitramfs_0BRFs9/usr/share/fonts/truetype/dejavu
>> cp -a /usr/share/fonts/truetype/dejavu/DejaVuSans.ttf 
>> /var/tmp/mkinitramfs_0BRFs9/usr/share/fonts/truetype/dejavu
>> fc-cache -v -s -y /var/tmp/mkinitramfs_0BRFs9
> 
> [...]
> # fc-cache -v -s -y /var/tmp/mkinitramfs_0BRFs9
> free(): double free detected in tcache 2
> Aborted

Interesting. Care to run it with strace to see exactly where it barfs?

Grüße,
Sven.




signature.asc
Description: OpenPGP digital signature

Bug#927153: plymouth: upgrade fails: /usr/share/initramfs-tools/hooks/plymouth failed with return 134

[Vincent Lefevre]

On 2019-04-16 01:53:03 +0200, Sven Hartge wrote:
> Try running the following commands as root:
> 
> mkdir -p /var/tmp/mkinitramfs_0BRFs9/etc/fonts/conf.d
> cp -a /etc/fonts/fonts.conf /var/tmp/mkinitramfs_0BRFs9/etc/fonts
> cp -rL /etc/fonts/conf.d/60-latin.conf 
> /var/tmp/mkinitramfs_0BRFs9/etc/fonts/conf.d
> mkdir -p /var/tmp/mkinitramfs_0BRFs9/var/cache/fontconfig
> mkdir -p /var/tmp/mkinitramfs_0BRFs9/usr/local/share/fonts
> mkdir -p /var/tmp/mkinitramfs_0BRFs9/usr/share/fonts/truetype/dejavu
> cp -a /usr/share/fonts/truetype/dejavu/DejaVuSerif.ttf 
> /var/tmp/mkinitramfs_0BRFs9/usr/share/fonts/truetype/dejavu
> cp -a /usr/share/fonts/truetype/dejavu/DejaVuSans.ttf 
> /var/tmp/mkinitramfs_0BRFs9/usr/share/fonts/truetype/dejavu
> fc-cache -v -s -y /var/tmp/mkinitramfs_0BRFs9

[...]
# fc-cache -v -s -y /var/tmp/mkinitramfs_0BRFs9
free(): double free detected in tcache 2
Aborted

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

Processed: Bug #920854 in mariadb-10.1 marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #920854 [src:mariadb-10.1] mariadb-10.1: FTBFS on s390x (test failure)
Added tag(s) pending.

-- 
920854: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920854
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#920854: Bug #920854 in mariadb-10.1 marked as pending

[Otto Kekäläinen]

Control: tag -1 pending

Hello,

Bug #920854 in mariadb-10.1 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/mariadb-team/mariadb-10.1/commit/e6e45334fbeb9565b0c49db419398e872eacd4cf


Limit build test suite to 'main' like in mariadb-10.3 (Closes: #920854)

Also skip unstable rpl tests, as is also done in mariadb-10.3 packaging.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/920854

Bug#920855: [debian-mysql] Bug#920855: mariadb-10.1: FTBFS on mips{, {, 64}el}: linker failures

[Julien Cristau]

On Tue, Apr 16, 2019 at 14:18:12 +0300, Otto Kekäläinen wrote:

> We also already have this patch, do you Julien think it fixes the same 
> problem?
> https://salsa.debian.org/mariadb-team/mariadb-10.1/blob/stretch/debian/patches/mips-compilation-failure-__bss_start-symbol-miss.patch
> 
I've no idea.  It sounds similar, I guess?  That patch certainly wasn't
there in 10.1.37-0+deb9u1.

Cheers,
Julien

Bug#920854: [debian-mysql] Bug#920854: mariadb-10.1: FTBFS on s390x (test failure)

[Otto Kekäläinen]

It seems this was fixed in
https://salsa.debian.org/mariadb-team/mariadb-10.1/commit/60b9d396b7712c46924564c6a73a0c02ff88f0ed

Bug#920854: [debian-mysql] Bug#920854: mariadb-10.1: FTBFS on s390x (test failure)

[Julien Cristau]

On Tue, Apr 16, 2019 at 01:55:31PM +0300, Otto Kekäläinen wrote:
> > Justification: fails to build from source (but built successfully in the 
> > past)
> > The mariadb-10.1 package on security.d.o doesn't build on s390x, one test 
> > fails:
> 
> Unfortunately there are no public build logs of this available at
> https://buildd.debian.org/status/package.php?p=mariadb-10.1=stretch
> Last build log for Stretch official s390x at
> https://buildd.debian.org/status/logs.php?pkg=mariadb-10.1=s390x
> is too old to be useful here, the test wasn't even attempted at in
> 10.1.23-9+deb9u1.
> 
https://people.debian.org/~carnil/buildd-logs/mariadb-10.1/ has the relevant 
log.

Cheers,
Julien

Bug#920854: [debian-mysql] Bug#920854: mariadb-10.1: FTBFS on s390x (test failure)

[Otto Kekäläinen]

> Justification: fails to build from source (but built successfully in the past)
> The mariadb-10.1 package on security.d.o doesn't build on s390x, one test 
> fails:

Unfortunately there are no public build logs of this available at
https://buildd.debian.org/status/package.php?p=mariadb-10.1=stretch
Last build log for Stretch official s390x at
https://buildd.debian.org/status/logs.php?pkg=mariadb-10.1=s390x
is too old to be useful here, the test wasn't even attempted at in
10.1.23-9+deb9u1.

In 
https://launchpadlibrarian.net/417117661/buildlog_ubuntu-xenial-s390x.mariadb-10.1_10.1.38-0+deb9u1~ubuntu16.04.1~1553970696.2efba5470d_BUILDING.txt.gz
this is disabled:

unit.pcre_test   [ disabled ]  MDEV-17865

It is one of the tests disabled by upstream, so it should not even run.

Upstream unstable tests have been skipped since
https://salsa.debian.org/mariadb-team/mariadb-10.1/commit/22e773ffa3eb23058543caa83b23cbc8596bb587
and this has been as is both in 10.1.26-0+deb9u1 and .38.

So it is quite strange why this test runs on s390x in stretch-security.

I will now limit the test suite to main as has been done in
mariadb-10.3 packaging, so it should take care of this issue as well.

Processed: severity of 926315 is serious, severity of 927165 is serious ..., usertagging 926315 ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 926315 serious
Bug #926315 [openssl] openssl: wget https://google.com fails in d-i
Severity set to 'serious' from 'important'
> severity 927165 serious
Bug #927165 [debian-installer] debian-installer: improve support for LUKS
Severity set to 'serious' from 'important'
> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was ni...@thykier.net).
> usertags 926315 buster-is-blocker
There were no usertags set.
Usertags are now: buster-is-blocker.
> usertags 927165 buster-is-blocker
There were no usertags set.
Usertags are now: buster-is-blocker.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
926315: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926315
927165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927165
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: found 927215 in 8.7.0-2

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 927215 8.7.0-2
Bug #927215 [kopano-search] kopano-search: AppArmor profile does not account 
for usrmerge
Marked as found in versions kopanocore/8.7.0-2.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
927215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927215
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#927215: kopano-search: AppArmor profile does not account for usrmerge

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 kopano-search
Bug #927215 [kopanocore] kopano-search: AppArmor profile does not account for 
usrmerge
Bug reassigned from package 'kopanocore' to 'kopano-search'.
No longer marked as found in versions 8.7.0-2.
Ignoring request to alter fixed versions of bug #927215 to the same values 
previously set

-- 
927215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927215
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#927215: kopano-search: AppArmor profile does not account for usrmerge

[Julian Andres Klode]

Control: reassign -1 kopano-search

On Tue, Apr 16, 2019 at 01:24:04PM +0200, Julian Andres Klode wrote:
> Package: kopanocore
> Version: 8.7.0-2
> Severity: serious
> Tags: patch
> User: ubuntu-de...@lists.ubuntu.com
> Usertags: origin-ubuntu disco ubuntu-patch
> 
> In Ubuntu, the attached patch was applied to achieve the following:
> 
> 
>   * kopano-search apparmor profile: Account for usrmerge
> 
> This was breaking autopkgtest for kopano-search --help with magic import 
> errors;
> and will have the same effect on real usrmerged systems.
> 

Assigning to the correct binary.

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en

Bug#927215: kopano-search: AppArmor profile does not account for usrmerge

[Julian Andres Klode]

Package: kopanocore
Version: 8.7.0-2
Severity: serious
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu disco ubuntu-patch

In Ubuntu, the attached patch was applied to achieve the following:


  * kopano-search apparmor profile: Account for usrmerge

This was breaking autopkgtest for kopano-search --help with magic import errors;
and will have the same effect on real usrmerged systems.


Thanks for considering the patch.

diff -Nru kopanocore-8.7.0/debian/apparmor/usr.sbin.kopano-search 
kopanocore-8.7.0/debian/apparmor/usr.sbin.kopano-search
--- kopanocore-8.7.0/debian/apparmor/usr.sbin.kopano-search 2019-02-19 
18:58:02.0 +0100
+++ kopanocore-8.7.0/debian/apparmor/usr.sbin.kopano-search 2019-04-16 
11:59:16.0 +0200
@@ -21,8 +21,8 @@
 
   deny /usr/lib/python{3,2.?}/dist-packages/kopano_search/*.pyc w,
 
-  /bin/dash Pix,
-  /bin/rm Pix,
+  {,/usr}/bin/dash Pix,
+  {,/usr}/bin/rm Pix,
 
   # FIXME: it would be nice if search would use search- like pa
   /dev/shm/* rwl,
@@ -38,7 +38,7 @@
 
   /lib/@{multiarch}/ld-*.so mr,
 
-  /sbin/ldconfig Pix,
+  {,/usr}/sbin/ldconfig Pix,
 
   /run/kopano/search.pid rw,
   /run/kopano/search.pid.lock lrw,


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

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

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en

Bug#920855: [debian-mysql] Bug#920855: mariadb-10.1: FTBFS on mips{, {, 64}el}: linker failures

[Otto Kekäläinen]

> The mariadb-10.1 on security.debian.org fails to build on all mipsen, with 
> similar errors:
>
> > [ 99%] Linking CXX executable explain_filename-t
> > cd /<>/builddir/unittest/sql && /usr/bin/cmake -E 
> > cmake_link_script CMakeFiles/explain_filename-t.dir/link.txt --verbose=1
> > /usr/bin/mips-linux-gnu-g++   -g -O2 -fdebug-prefix-map=/<>=. 
> > -specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong 
> > -Wformat -Werror=format-security -pie -fPIC -Wl,-z,relro,-z,now 
> > -fstack-protector --param=ssp-buffer-size=4 -DWITH_INNODB_DISALLOW_WRITES 
> > -fno-exceptions -fno-rtti -O3 -g -static-libgcc -fno-omit-frame-pointer 
> > -fno-strict-aliasing -Wno-uninitialized -D_FORTIFY_SOURCE=2 -DDBUG_OFF  
> > -specs=/usr/share/dpkg/no-pie-link.specs -Wl,-z,relro -Wl,-z,now 
> > CMakeFiles/explain_filename-t.dir/explain_filename-t.cc.o  -o 
> > explain_filename-t  -lpthread ../../sql/libsql.a ../mytap/libmytap.a 
> > ../../storage/csv/libcsv.a ../../storage/heap/libheap.a 
> > ../../storage/maria/libaria.a ../../storage/myisam/libmyisam.a 
> > ../../storage/myisammrg/libmyisammrg.a 
> > ../../storage/perfschema/libperfschema.a 
> > ../../storage/sequence/libsequence.a ../../storage/xtradb/libxtradb.a -laio 
> > ../../plugin/auth_socket/libauth_socket.a 
> > ../../plugin/feedback/libfeedback.a ../../plugin/userstat/libuserstat.a 
> > ../../sql/libpartition.a ../../mysys/libmysys.a 
> > ../../mysys_ssl/libmysys_ssl.a ../../dbug/libdbug.a ../../mysys/libmysys.a 
> > ../../mysys_ssl/libmysys_ssl.a ../../dbug/libdbug.a -lz -lm 
> > ../../extra/yassl/libyassl.a ../../extra/yassl/taocrypt/libtaocrypt.a 
> > ../../strings/libstrings.a ../../vio/libvio.a ../../pcre/libpcre.a -lcrypt 
> > -ldl ../../wsrep/libwsrep.a -lsystemd -latomic -lpthread
> > /usr/bin/ld: ../../mysys/libmysys.a(stacktrace.c.o): undefined reference to 
> > symbol '__bss_start'
> > //lib/mips-linux-gnu/libselinux.so.1: error adding symbols: DSO missing 
> > from command line
> > collect2: error: ld returned 1 exit status

Found upstream commit
https://github.com/mariadb/server/commit/057c560ee45c61d172ed0ed762b0b33b37349e5c
and issue https://jira.mariadb.org/browse/MDEV-10943 which have the
same error message.

We also already have this patch, do you Julien think it fixes the same problem?
https://salsa.debian.org/mariadb-team/mariadb-10.1/blob/stretch/debian/patches/mips-compilation-failure-__bss_start-symbol-miss.patch

Bug#927159: marked as done (libqb: Insecure Temporary Files)

[Debian Bug Tracking System]

Your message dated Tue, 16 Apr 2019 10:18:54 +
with message-id 
and subject line Bug#927159: fixed in libqb 1.0.4-1
has caused the Debian Bug report #927159,
regarding libqb: Insecure Temporary Files
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
927159: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927159
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libqb
Version: 1.0.3-2
Severity: grave
Tags: patch upstream security
Justification: user security hole
Forwarded: https://github.com/ClusterLabs/libqb/issues/338
Control: found -1 0.11.1-2

Libqb creates files in world-writable directories (/dev/shm, /tmp) with
rather predictable file names (for example in case of USBGuard with names
like /dev/shm/qb-usbguard-request-7096-835-12-data). Also O_EXCL flag is
not used when opening the files. This could be exploited by a local
attacker to overwrite privileged system files (if not restricted by
sandboxing, MAC or symlinking policies).
--- End Message ---
--- Begin Message ---
Source: libqb
Source-Version: 1.0.4-1

We believe that the bug you reported is fixed in the latest version of
libqb, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 927...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ferenc Wágner  (supplier of updated libqb package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 16 Apr 2019 11:32:02 +0200
Source: libqb
Architecture: source
Version: 1.0.4-1
Distribution: unstable
Urgency: high
Maintainer: Debian HA Maintainers 

Changed-By: Ferenc Wágner 
Closes: 902104 927159
Changes:
 libqb (1.0.4-1) unstable; urgency=high
 .
   * [021333b] New patch: Reduce stress test lengths to help weak buildds
 (Closes: #902104)
   * [dc825fb] New upstream security release (1.0.4)
 Libqb creates files in world-writable directories (/dev/shm, /tmp) with
 rather predictable file names. Also O_EXCL flag is not used when opening
 the files.  This could be exploited by a local attacker to overwrite
 privileged system files.  (CVE not assigned yet. Closes: #927159)
   * [e36e34a] Refresh our patches
   * [0823bf1] Acknowledge new internal symbol
   * [88aafa5] Update Standards-Version to 4.3.0 (no changes required)
   * [174d210] New patch: Fix garbled Doxygen markup
Checksums-Sha1:
 710f93c4bac969ce0ae0796ddb484637e016e3ef 2423 libqb_1.0.4-1.dsc
 b8078893be6c2c355313fe71cf006da7713ea43e 488536 libqb_1.0.4.orig.tar.xz
 a0c36c968b98ff62fb2e08d1676068f074bc22da 490 libqb_1.0.4.orig.tar.xz.asc
 597140cbb986bae40feabd146485cac13b732061 14660 libqb_1.0.4-1.debian.tar.xz
 7ad39ccc76987a16c2557887a4ef38d59fd17c74 8994 libqb_1.0.4-1_amd64.buildinfo
Checksums-Sha256:
 f6baa06c325116c25dfb6e268b1f26c4c0cbe1440c5466e8bb15aa31a5f4d291 2423 
libqb_1.0.4-1.dsc
 0064575151b11135a68a15f01da0ab1eaef4279b07e7059a10c748c12f28c14f 488536 
libqb_1.0.4.orig.tar.xz
 10029fa1da3752b9c28ac2a7530108671a084fa80f37c5b211aeec2de74744ae 490 
libqb_1.0.4.orig.tar.xz.asc
 23c9517fb3f746f50ce7bd99deb48d03ab88521ba1801ceeb2a501dd54311fae 14660 
libqb_1.0.4-1.debian.tar.xz
 4c61f83a9a0fa365561fb7ddd2300f5ed09cf1dcef1fa763eba658b46d40c69a 8994 
libqb_1.0.4-1_amd64.buildinfo
Files:
 254a63658735dcb207be357b4c2b3e6c 2423 libs optional libqb_1.0.4-1.dsc
 07dc93433a295f45dd16293a4b63389e 488536 libs optional libqb_1.0.4.orig.tar.xz
 22d567fc789da092b0e14e1c9d625ac5 490 libs optional libqb_1.0.4.orig.tar.xz.asc
 61a49b2f90a1bbe677275238cd107213 14660 libs optional 
libqb_1.0.4-1.debian.tar.xz
 3d70e4dc9e8d7c4d71204c670a3e11c5 8994 libs optional 
libqb_1.0.4-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIyBAEBCgAdFiEEwddEx0RNIUL7eugtOsj3Fkd+2yMFAly1pF0ACgkQOsj3Fkd+
2yM2Bw/2JzHPYzWM71U7xw9/rYefEfzigmRTofej16IQtx4dGEmGs5wy2lkDrY/Y
lmho1aPv8dpV46Xz4oTGhi9n1L02b9hD3eVJ0CsJ6YCFQaBJ9CcXPM+TQSLCjYN8
syGl/jqKknAfRNJG50NnQUXnACHmgJ79CVaXyiZh132V28kOYJBgGJi0ayqznd9r
G8eHoYYdmk0zV+SdaQ6fTeg8pitu6QWLHQ73qfVlaLO+uCeRZUgJl8Ah9raHPqgi
DA7OPoPWdlsrQc0kRKI3vQ0KMkphjzsymy+TsXD0zomXp7X6tJ97rx1q3yylO528
lX86UNll+aY84dejFu+LxJG7UBFW1ADlgd830qEUVR0SbL97pVKZCwwJ4k/Z9zN0

Bug#927166: libbiod0: not installable in sid

[Andreas Tille]

On Mon, Apr 15, 2019 at 09:39:17PM +0200, Ralf Treinen wrote:
> Package: libbiod0
> Version: 0.2.1-1
> Severity: serious
> User: trei...@debia.org
^
@Ralf: Are you sure there is no typo in one of your scripts?

> libbiod0 is not installable on amd64 or i386 (the only architectures
> for which this binary package exists) in sid, at least since
> 2018-10-30 : it depends on libphobos2-ldc-shared81 which does 
> not exist in sid.

My guess is that this can be simply solved by a rebuild which
is fixed by a new changelog entry in Git.

@Matthias:

When I try to build the current state in Git I get:

...
ldc2 -wi -g -relocation-model=pic -unittest -main -Icontrib/undead -L-lz -O0 
-d-debug -link-debuglib contrib/undead/cstream.o contrib/undead/stream.o 
contrib/undead/doformat.o contrib/ undead/utf.o contrib/undead/*/*.o 
bio/core/sequence.o bio/core/kmer.o bio/core/genotype.o bio/core/tinymap.o 
bio/core/base.o bio/core/decompress.o bio/core/call.o bio/core/region.o bio/
core/bgzf/inputstream.o bio/core/bgzf/constants.o bio/core/bgzf/block.o 
bio/core/bgzf/virtualoffset.o bio/core/bgzf/compress.o bio/core/bgzf/chunk.o 
bio/core/bgzf/outputstream.o bio/core/  utils/format.o 
bio/core/utils/exception.o bio/core/utils/outbuffer.o bio/core/utils/stream.o 
bio/core/utils/algo.o bio/core/utils/tmpfile.o bio/core/utils/memoize.o 
bio/core/utils/ switchendianness.o bio/core/utils/roundbuf.o 
bio/core/utils/zlib.o bio/core/utils/bylinefast.o bio/core/utils/range.o 
bio/std/file/fastq.o bio/std/file/fasta.o bio/std/file/fai.o bio/std/  
genotype/maf.o bio/std/genotype/snp.o bio/std/range/splitter.o 
bio/std/sff/writer.o bio/std/sff/readrange.o bio/std/sff/index.o 
bio/std/sff/reader.o bio/std/sff/read.o bio/std/sff/ constants.o 
bio/std/maf/reader.o bio/std/maf/block.o bio/std/maf/parser.o 
bio/std/experimental/hts/logger.o bio/std/experimental/hts/pileup.o 
bio/std/experimental/hts/bgzf_writer.o bio/std/experimental/hts/reads.o 
bio/std/experimental/hts/bgzf.o bio/std/experimental/hts/unpack.o 
bio/std/experimental/hts/constants.o bio/std/experimental/hts/hashing.o 
bio/std/sff/utils/roundup.o bio/std/hts/iontorrent/flowcall.o 
bio/std/hts/iontorrent/flowindex.o bio/std/hts/sam/reader.o 
bio/std/hts/sam/header.o bio/std/hts/snpcallers/maq.o 
bio/std/hts/snpcallers/simple.o bio/   std/hts/bam/abstractreader.o 
bio/std/hts/bam/randomaccessmanager.o bio/std/hts/bam/baifile.o 
bio/std/hts/bam/writer.o bio/std/hts/bam/pileup.o bio/std/hts/bam/splitter.o 
bio/std/hts/bam/   tagvalue.o bio/std/hts/bam/constants.o 
bio/std/hts/bam/reference.o bio/std/hts/bam/baseinfo.o 
bio/std/hts/bam/readrange.o bio/std/hts/bam/referenceinfo.o 
bio/std/hts/bam/multireader.o bio/ std/hts/bam/reader.o bio/std/hts/bam/read.o 
bio/std/hts/bam/cigar.o bio/std/hts/bam/region.o 
bio/std/hts/thirdparty/msgpack.o bio/std/hts/utils/array.o 
bio/std/hts/utils/value.o bio/std/   hts/utils/samheadermerger.o 
bio/std/hts/utils/graph.o bio/std/experimental/hts/bam/reader.o 
bio/std/experimental/hts/bam/writer.o bio/std/experimental/hts/bam/header.o 
bio/std/hts/sam/ utils/recordparser.o 
bio/std/hts/sam/utils/fastrecordparser.o bio/std/hts/bam/md/core.o 
bio/std/hts/bam/md/operation.o bio/std/hts/bam/md/reconstruct.o 
bio/std/hts/bam/md/parse.o bio/std/  hts/bam/bai/bin.o 
bio/std/hts/bam/bai/indexing.o bio/std/hts/bam/validation/alignment.o 
bio/std/hts/bam/validation/samheader.o -of=bin/biod_tests
/usr/bin/ld: bin/biod_tests.o:(.data._d_execBssBegAddr+0x0): multiple 
definition of `_d_execBssBegAddr'; 
contrib/undead/*/__main.o:(.data._d_execBssBegAddr+0x0): first defined here
/usr/bin/ld: bin/biod_tests.o:(.data._d_execBssEndAddr+0x0): multiple 
definition of `_d_execBssEndAddr'; 
contrib/undead/*/__main.o:(.data._d_execBssEndAddr+0x0): first defined here
collect2: error: ld returned 1 exit status
Error: /usr/bin/gcc failed with status: 1


As usual I have no idea how to fix this. :-(

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#905772: [Pkg-libvirt-maintainers] Bug#905772: libvirtd upgrade broken stretch->buster

[Niels Thykier]

On Mon, 15 Apr 2019 22:27:57 +0200 Guido =?iso-8859-1?Q?G=FCnther?=
 wrote:
> Hi,
> On Mon, Apr 15, 2019 at 10:18:18PM +0200, Michael Biebl wrote:
> > Hi Sam
> > 
> > Am 15.04.2019 um 20:38 schrieb Sam Hartman:
> > > control: severity -1 serious
> > > 
> > > justification: libvirtd upgrades from stretch to buster break causing
> > > apt to fail and requiring the admin to get the systemd units into a
> > > consistent state before things can continue
> > > 
> > > 
> > > Unfortunately based on discussion so far this is a complex bug to fix.
> > > Ubuntu's solution is to drop the sysv scripts and to drop  Also= lines
> > > in some of the units.
> > > 
> > > The systemd maintainers proposed that dropping Also as well as some
> > > changes to move toward dh_systemd_start being used even when sysvinit
> > > scripts are present would help this situation.  Unfortunately it at
> > > least doesn't look like those changes are in debhelper for buster.
> > > Systemd folks, do you have any suggestions  on how to approach this for
> > > buster?
> > 
> > Using debhelper compat level 12, you are able to completely decouple
> > dh_installinit and dh_installsystemd which would give you the ability to
> > implement what you want afaics.
> 
> So let's move libvirt from 8 to 12 for stretch? I'm all for it but it'll
> be a couple of days until I can set time aside for this.
> cheers,
>  -- Guido
> 
> [...]
Hi,

I think we should keep libvirt at compat 8 in general for now and then
leave a full bump to compat 12 for bullseye.  The reason here being that
the compat changes documented in debhelper(7) amounts to 3-4 screens
worth of changes across all of debhelper's tools.

Instead, we can do a mixed compat setup, where the package remains at
compat 8 in general but we force selected tools to run in compat 12.  I
have made a PoC of that in
https://salsa.debian.org/libvirt-team/libvirt/merge_requests/21/diffs

Note that change set is only meant as inspiration; I have not tried to
understand the problem nor the solution fully (nor have I tested that it
actually still builds).

Thanks,
~Niels

Bug#927201: dep: fonts-glyphicons-halflings Package not available

[Magnus Frühling]

Package: knot-resolver-module-http
Version: 3.2.1-3~bpo9+1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

One can not install / update knot-resolver-module-http because 
fonts-glyphicons-halflings is missing for stretch(-backports).


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

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


knot-resolver-module-http recommends no packages.

knot-resolver-module-http suggests no packages.

-- no debconf information

Bug#926788: gauche-c-wrapper: FTBFS randomly (autobuilder hangs)

[Santiago Vila]

Thanks a lot for looking at this issue.

One minor comment:

> In my opinion, your patch is hiding a problem.  I'm afraid it is against
> our social contract #3 (We will not hide problems).  With it, there will
> be no information if it build well or not.

You are interpreting the Social Contract in a very wide sense.

Social Contract #3 really refers to our BTS being public (please read
it in full).

We can also of course interpret it as a general guideline, not related
to the BTS, but then it could be done in several contradictory ways.
For example, packages in stable must build from source. If we had
downgraded this, we could also say that we are hiding the problem.

Thanks.

Processed: adjusting severity

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 926182 926676
Bug #926182 [guile-2.2-dev] guile-2.2-dev: autoreconf'ed scripts using guile.m4 
cannot find guild & guile-config/tools
Bug #926676 [guile-2.2-dev] guile-2.2-dev: Missing binary symlink `guild-2.2` 
(and others)
885200 was blocked by: 885193 926182 885206
885200 was not blocking any bugs.
Added blocking bug(s) of 885200: 926676
Added indication that 926676 affects gwave
Merged 926182 926676
> severity 926182 serious
Bug #926182 [guile-2.2-dev] guile-2.2-dev: autoreconf'ed scripts using guile.m4 
cannot find guild & guile-config/tools
Bug #926676 [guile-2.2-dev] guile-2.2-dev: Missing binary symlink `guild-2.2` 
(and others)
Severity set to 'serious' from 'normal'
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
885200: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885200
926182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926182
926676: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926676
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems