Bug#900548: marked as done (slurm-llnl: CVE-2018-10995: Insecure handling of username and gid fields)

[Debian Bug Tracking System]

Your message dated Thu, 7 Jun 2018 07:17:10 +0200
with message-id <20180607051710.ga26...@lorien.valinor.li>
and subject line Re: Bug#900548: slurm-llnl: CVE-2018-10995: Insecure handling 
of username and gid fields
has caused the Debian Bug report #900548,
regarding slurm-llnl: CVE-2018-10995: Insecure handling of username and gid 
fields
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.)


-- 
900548: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900548
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: slurm-llnl
Version: 14.03.9-5
Severity: grave
Tags: security upstream

Hi,

The following vulnerability was published for slurm-llnl.

CVE-2018-10995[0]:
| SchedMD Slurm before 17.02.11 and 17.1x.x before 17.11.7 mishandles
| user names (aka user_name fields) and group ids (aka gid fields).

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-10995
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10995

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: slurm-llnl
Source-Version: 17.11.7-1

On Fri, Jun 01, 2018 at 09:51:28AM +0200, Salvatore Bonaccorso wrote:
> Source: slurm-llnl
> Version: 14.03.9-5
> Severity: grave
> Tags: security upstream
> 
> Hi,
> 
> The following vulnerability was published for slurm-llnl.
> 
> CVE-2018-10995[0]:
> | SchedMD Slurm before 17.02.11 and 17.1x.x before 17.11.7 mishandles
> | user names (aka user_name fields) and group ids (aka gid fields).
> 
> If you fix the vulnerability please also make sure to include the
> CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

This issue was adressed with the 17.11.7-1 upload to unstable, closing
the bug accordingly.

Regards,
Salvatore--- End Message ---

Bug#900548: slurm-llnl: CVE-2018-10995: Insecure handling of username and gid fields

[Salvatore Bonaccorso]

Source: slurm-llnl
Source-Version: 17.11.7-1

On Fri, Jun 01, 2018 at 09:51:28AM +0200, Salvatore Bonaccorso wrote:
> Source: slurm-llnl
> Version: 14.03.9-5
> Severity: grave
> Tags: security upstream
> 
> Hi,
> 
> The following vulnerability was published for slurm-llnl.
> 
> CVE-2018-10995[0]:
> | SchedMD Slurm before 17.02.11 and 17.1x.x before 17.11.7 mishandles
> | user names (aka user_name fields) and group ids (aka gid fields).
> 
> If you fix the vulnerability please also make sure to include the
> CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

This issue was adressed with the 17.11.7-1 upload to unstable, closing
the bug accordingly.

Regards,
Salvatore

Bug#892394: could somebody share the link of the new mailing list ?

[shirish शिरीष]

Dear all,

Was looking into this bug.  Can somebody share the link of the new
mailing list as the alioth lists have been archived and
lists.debian.org/completeindex.html doesn't tell or show any
pkg-boost-devel mailing list :(

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

Processed: tagging 900942

[Debian Bug Tracking System]

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

> tags 900942 + upstream
Bug #900942 [src:libpgobject-util-dbadmin-perl] CVE-2018-9246
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Processed: Adding found info...

[Debian Bug Tracking System]

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

> found 900942 0.100.0-1
Bug #900942 [src:libpgobject-util-dbadmin-perl] CVE-2018-9246
Marked as found in versions libpgobject-util-dbadmin-perl/0.100.0-1.
> thanks
Stopping processing here.

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

Processed: correcting bug title

[Debian Bug Tracking System]

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

> retitle 900942 CVE-2018-9246
Bug #900942 [src:libpgobject-util-dbadmin-perl] Fwd: [ledgersmb-announce] 
Security announcement for CVE-2018-9246 / PGObject::Util::DBAdmin
Changed Bug title to 'CVE-2018-9246' from 'Fwd: [ledgersmb-announce] Security 
announcement for CVE-2018-9246 / PGObject::Util::DBAdmin'.
> thanks
Stopping processing here.

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

Bug#900942: Fwd: [ledgersmb-announce] Security announcement for CVE-2018-9246 / PGObject::Util::DBAdmin

[Robert J. Clay]

Source: libpgobject-util-dbadmin-perl
Severity: grave
Tags: security

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-9246

-- Forwarded message -
From: Erik Huelsmann 
Date: Wed, Jun 6, 2018 at 6:36 PM
Subject: [ledgersmb-announce] Security announcement for CVE-2018-9246
/ PGObject::Util::DBAdmin
To: 


This mail is sent to this mailing list because PGObject::Util::DBAdmin
itself doesn't have a mailing list to send the disclosure to. We'll
update its repository to reflect the announcement below.


Please take note of the security advisory below, known as CVE-2018-9246

   Nick Prater discovered that the PGObject::Util::DBAdmin insufficiently
sanitizes or escapes variable values used as part of shell command
execution, resulting in shell code injection.
   The vulnerability allows an attacker to execute arbitrary code with the
same privileges as the running application through the create(), run_file(),
backup() and restore() functions.

Affected versions:
  PGObject::Util::DBAdmin versions 0.110.0 and lower.

Vulnerability type:
  Insufficiently sanitized arguments in external program invocation

Discoverer:
  Nick Prater (NP Broadcast LTD)

Resolution:
  Upgrade to PGObject::Util::DBAdmin 0.120.0 or newer. (0.130.0
available on CPAN).

Processed: downgrade severity until openjdk8 is actually removed

[Debian Bug Tracking System]

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

> severity 900299 important
Bug #900299 [src:leiningen-clojure] leiningen-clojure: depends on openjdk-8
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#900811: marked as done (libadios-dev: adios_config pkg-config typo: "adiso")

[Debian Bug Tracking System]

Your message dated Thu, 07 Jun 2018 00:49:39 +
with message-id 
and subject line Bug#900811: fixed in adios 1.13.1-2
has caused the Debian Bug report #900811,
regarding libadios-dev: adios_config pkg-config typo: "adiso"
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.)


-- 
900811: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900811
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libadios-dev
Version: 1.11.0-1+b1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

the file `adios_config` added in the Debian packages contains a typo in line
"83" reading:

if [ "$OPT_SEQ" == "yes" ]; then
CFLAGS=`pkg-config adiso --variable ADIOS_SEQ_INC`
else
CFLAGS=`pkg-config adios --variable ADIOS_INC`
fi

The first branch of the if should read `adios` as well, not `adiso`.

This typo makes the tool `adios_config` not usable for downstream developers
which call it.

Also, the script `adios_config` depends on `pkg-config` so `pkg-config` should
be a dependency for `libadios-dev`.


Best regards and thanks for your great support with packaging ADIOS!
Axel



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

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

libadios-dev depends on no packages.

Versions of packages libadios-dev recommends:
ii  libadios-bin  1.11.0-1+b1

libadios-dev suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: adios
Source-Version: 1.13.1-2

We believe that the bug you reported is fixed in the latest version of
adios, 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.
Alastair McKinstry  (supplier of updated adios package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 05 Jun 2018 16:39:47 +0100
Source: adios
Binary: libadios-dev libadios-examples libadios-bin python-adios python3-adios
Architecture: source amd64 all
Version: 1.13.1-2
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Description:
 libadios-bin - ADIOS Adaptable IO system for simulations - binaries
 libadios-dev - ADIOS Adaptable IO system for simulations
 libadios-examples - Examples for the ADIOS Adaptable IO system
 python-adios - Python interface to the ADIOS IO system
 python3-adios - Python3 interface to the ADIOS IO system
Closes: 894165 900811
Changes:
 adios (1.13.1-2) unstable; urgency=medium
 .
   * Drop obsolete X-Python-Version statements
   * Fix typo in adios_config that breaks operation. Closes: #900811.
   * Add pkg-config as dependency to libadios-dev
   * Set VERSIONSTRING in adios_config. Closes: #894165
Checksums-Sha1:
 38931e18c6791c2a1f65e56ddc922ee109fe94af 2476 adios_1.13.1-2.dsc
 23a87c8437b05248e2640521422775c021f03c79 34488 adios_1.13.1-2.debian.tar.xz
 f6f4fedb5c86ce380955e12d70832568b0fe5127 11751 adios_1.13.1-2_amd64.buildinfo
 f38452b48051b8387f4400b3a2ae51996641aa55 3509628 
libadios-bin-dbgsym_1.13.1-2_amd64.deb
 5c2390ed2de1c16b58da363aa3a1e7f0574344f3 499256 libadios-bin_1.13.1-2_amd64.deb
 7f20a62e69c77c099a4d261e304c57b1627f6197 465568 libadios-dev_1.13.1-2_amd64.deb
 bc5098201d921155febb9a0a3e145343cca1d7b2 45684380 
libadios-examples_1.13.1-2_all.deb
 173d48ebf0e31346d68eb7c5be33836439a0d4a6 2630824 
python-adios-dbgsym_1.13.1-2_amd64.deb
 f143ba521dbf5ec25aa77ae4e0f0d773142acfe0 699172 python-adios_1.13.1-2_amd64.deb
 b3f33ef4bce7eb5c73e3996d49d3a2de5b44a462 2860688 
python3-adios-dbgsym_1.13.1-2_amd64.deb
 ce114e0e75eb7da6d370b764aac76f4196c6b19c 742336 
python3-adios_1.13.1-2_amd64.deb
Checksums-Sha256:
 c9bd0c7d4b9f11c677d0a9b891db497445ca5bff3b35581dbaae2c6e1ddedf3d 2476 
adios_1.13.1-2.dsc
 b9db0f8f7526b1d962cbad21c99885fbf00a7ed642da5bf40ac65bfa3a5a9214 

Bug#900936: geoclue: Update to 2.4.10 breaks redshift

[James Tocknell]

Package: geoclue-2.0
Version: 2.4.10-1
Severity: critical
File: geoclue
Tags: upstream

Dear Maintainer,

The update to 2.4.10-1 causes redshift to immediately crash, with the error:

Failed to connect to GeoClue2 service: 
GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: 'redshift' disallowed, no 
agent for UID 1000

Starting the agent in the demo package manually appears to make no difference.
Additionally, I tried to use the where-am-i demo, which produced the same error
(again with the agent started).

I think the cause is this change referred to in the upstream changelog:
"Refuse location access if no app-auth agent is registered. This fixes a
security hole where an app requests location access before the agent gets to
register itself and we end up giving out locaiton access even though user has
disabled it."

Can the change be reverted until the agent works?

FYI, I make the report critical so that the change doesn't migrate to testing,
feel free to drop the severity if you think that's appropriate.


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

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

Versions of packages geoclue-2.0 depends on:
ii  adduser 3.117
ii  libavahi-client30.7-4
ii  libavahi-common30.7-4
ii  libavahi-glib1  0.7-4
ii  libc6   2.27-3
ii  libglib2.0-02.56.1-2
ii  libjson-glib-1.0-0  1.4.2-4
ii  libmm-glib0 1.7.990-1
ii  libsoup2.4-12.62.2-1

Versions of packages geoclue-2.0 recommends:
ii  avahi-daemon  0.7-4
ii  iio-sensor-proxy  2.4-2
ii  modemmanager  1.7.990-1
ii  wpasupplicant 2:2.6-16

geoclue-2.0 suggests no packages.

-- no debconf information

Bug#900930: CVE-2018-10057 CVE-2018-10058

[Luke Dashjr]

The severity is wrong on this. The first one is a very minor issue (only the 
admin can trigger it), and the second one is not a bug at all.

On Wednesday 06 June 2018 21:01:42 Moritz Muehlenhoff wrote:
> Package: bfgminer
> Severity: grave
> Tags: security
>
> http://www.openwall.com/lists/oss-security/2018/06/03/1

Bug#894292: jayway-jsonpath FTBFS with openjdk-9

[Emmanuel Bourg]

Control: retitle -1 jayway-jsonpath FTBFS: Cannot set the value of read-only 
property 'displayName'
Control: user debian-j...@lists.debian.org
Control: usertag -1 - default-java9

Le 28/03/2018 à 14:14, Adrian Bunk a écrit :

>> Cannot set the value of read-only property 'displayName' for project 
>> ':json-path' of type org.gradle.api.Project.

I get the same error with Java 8, so this is probably caused by
something else.

Processed (with 2 errors): Re: Bug#894292: jayway-jsonpath FTBFS with openjdk-9

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 jayway-jsonpath FTBFS: Cannot set the value of read-only property 
> 'displayName'
Bug #894292 [src:jayway-jsonpath] jayway-jsonpath FTBFS with openjdk-9
Changed Bug title to 'jayway-jsonpath FTBFS: Cannot set the value of read-only 
property 'displayName'' from 'jayway-jsonpath FTBFS with openjdk-9'.
> user debian-j...@lists.debian.org
Unknown command or malformed arguments to command.

> usertag -1 - default-java9
Unknown command or malformed arguments to command.


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

Bug#855942: anki: don't let the alpha version migrate to testing

[Julian Gilbey]

On Wed, Jun 06, 2018 at 03:09:13PM -0400, Alexandre Viau wrote:
> On 2018-06-06 02:38 AM, Julian Gilbey wrote:
> >
> > Unfortunately the program doesn't work: Qt 5.10 is apparently
> > sufficiently buggy in some respect that I don't understand that it
> > breaks Anki.  So we can't let it migrate until Qt 5.11 is released.
> > But I do appreciate your general point; at the same time, I don't
> > particularly want to annoy upstream.
> >
> 
> Oh, I had assumed that the program works from the bug title and last
> comment, thank you for correcting me.

Your assumption was correct: it worked fine with Qt 5.9.  But once Qt
5.10 entered unstable a little while back, anki stopped working (it
has a check for this specific Qt version).

> I currently the build from Anki's website and I must say that I find
> this program very effective, I am happy to see that it will be available
> in Debian eventually. I hope to see this happen sometimes soon and that
> you will consider letting it migrate if it is ever in a usable shape.

It's a pleasure!  Anki is very nice indeed.

Best wishes,

   Julian

Processed: Re: nexus FTBFS with openjdk-9

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #893383 [src:nexus] nexus FTBFS with openjdk-9
Added tag(s) patch.

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

Bug#893383: nexus FTBFS with openjdk-9

[Emmanuel Bourg]

Control: tags -1 + patch

I haven't been able to reproduce the error reported, but I got two
other errors due to the use of the now removed source/target level 1.5
in Java 9, and due to the removal of javah in Java 10. This simple
modification of JAVACFLAGS in debian/rules fixed these issues:

--- a/debian/rules
+++ b/debian/rules
@@ -41,7 +41,7 @@ endif
 ifneq "$(wildcard /usr/share/misc/config.guess)" ""
cp -f /usr/share/misc/config.guess config.guess
 endif
-   ./configure --host=$(DEB_HOST_GNU_TYPE) --build=$(DEB_BUILD_GNU_TYPE) 
--prefix=/usr --mandir=\$${prefix}/share/man --infodir=\$${prefix}/share/info 
--with-hdf5=$(HDF5_DIR) CFLAGS="$(CFLAGS)" LDFLAGS="$(LDFLAGS) -Wl,-z,defs" 
CPPFLAGS="$(CPPFLAGS)" CXXFLAGS="$(CXXFLAGS)" 
--with-java-home=/usr/lib/jvm/default-java --with-python=/usr 
JAVACFLAGS="-source 1.5 -target 1.5"
+   ./configure --host=$(DEB_HOST_GNU_TYPE) --build=$(DEB_BUILD_GNU_TYPE) 
--prefix=/usr --mandir=\$${prefix}/share/man --infodir=\$${prefix}/share/info 
--with-hdf5=$(HDF5_DIR) CFLAGS="$(CFLAGS)" LDFLAGS="$(LDFLAGS) -Wl,-z,defs" 
CPPFLAGS="$(CPPFLAGS)" CXXFLAGS="$(CXXFLAGS)" 
--with-java-home=/usr/lib/jvm/default-java --with-python=/usr 
JAVACFLAGS="-source 1.8 -target 1.8 -h native"
sed < libtool > libtool-2 -e 
's/^hardcode_libdir_flag_spec.*$$/hardcode_libdir_flag_spec=" 
-D__LIBTOOL_IS_A_FOOL__ "/' -e '/^archive_cmds="/s/"$$/ \\$$deplibs"/'
mv libtool-2 libtool
chmod 755 libtool

Bug#900929: CVE-2018-10057 CVE-2018-10058

[Moritz Muehlenhoff]

Package: cgminer
Severity: grave
Tags: security

http://www.openwall.com/lists/oss-security/2018/06/03/1

Bug#900930: CVE-2018-10057 CVE-2018-10058

[Moritz Muehlenhoff]

Package: bfgminer
Severity: grave
Tags: security

http://www.openwall.com/lists/oss-security/2018/06/03/1
 

Bug#900924: [Pkg-utopia-maintainers] Bug#900924: [network-manager-gnome] segfault after upgrade to 1.8.12-1

[Shin Ice]

Hi Michael,

On Wed, Jun 06, 2018 at 09:43:12PM +0200, Michael Biebl wrote:
>
> Please test 1.8.12-2 and report back. It was uploaded a couple of
> minutes ago and should hit the mirrors soon.
>
> Regards,
> Michael
>

thanks :)
And sorry, dunno why but I dind't saw in reportbug-ng the #900869, I
think they are relatad and could be linked.

Will report when I have the new version installed.

Greetings
Shin

--

I'm just a placeholder for a really awesome signature...
...that is still missing *sob*


signature.asc
Description: PGP signature

Bug#900924: [Pkg-utopia-maintainers] Bug#900924: [network-manager-gnome] segfault after upgrade to 1.8.12-1

[Michael Biebl]

Am 06.06.2018 um 20:54 schrieb Shin Ice:
> Package: network-manager-gnome
> Version: 1.8.12-1
> Severity: grave
> 
> --- Please enter the report below this line. ---
> 
> Hi,
> 
> after upgrading network-manager-gnome and libnma0 to 1.8.12-1 I receive
> a segfault every time I open the menu to enable my vpn connection (that
> is unfortunately a must have form me).
> 
> Doing a rollback of network-manager-gnome and libnma0 to 1.8.10-5 works
> well and I can connect without problems.

Please test 1.8.12-2 and report back. It was uploaded a couple of
minutes ago and should hit the mirrors soon.

Regards,
Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#900533: chromium 67.0.3396.62-1: youtube video, gif's, html5, and movies no longer work

[Mike Brodbelt]

Same problem as other reporters, also resolved by downgrading chromium, 
chromium-common, and chromium-l10n to 66.0.3359.181-1.

Bug#855942: anki: don't let the alpha version migrate to testing

[Alexandre Viau]

On 2018-06-06 02:38 AM, Julian Gilbey wrote:
>
> Unfortunately the program doesn't work: Qt 5.10 is apparently
> sufficiently buggy in some respect that I don't understand that it
> breaks Anki.  So we can't let it migrate until Qt 5.11 is released.
> But I do appreciate your general point; at the same time, I don't
> particularly want to annoy upstream.
>

Oh, I had assumed that the program works from the bug title and last
comment, thank you for correcting me.

I currently the build from Anki's website and I must say that I find
this program very effective, I am happy to see that it will be available
in Debian eventually. I hope to see this happen sometimes soon and that
you will consider letting it migrate if it is ever in a usable shape.

Thank you for your work,

-- 
Alexandre Viau
av...@debian.org




signature.asc
Description: OpenPGP digital signature

Bug#896706: marked as done (pcbnew: crashes with a failed assertion on i386, starts fine on amd64)

[Debian Bug Tracking System]

Your message dated Wed, 06 Jun 2018 19:05:43 +
with message-id 
and subject line Bug#896706: fixed in kicad 5.0.0~rc2+dfsg1-3
has caused the Debian Bug report #896706,
regarding pcbnew: crashes with a failed assertion on i386, starts fine on amd64
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.)


-- 
896706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896706
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kicad
Version: 5.0.0~rc1+dfsg1+20180318-3
Severity: normal

On the i386 architecture, I get this error when starting pcbnew:

pcbnew: 
/build/kicad-9PGPiJ/kicad-5.0.0~rc1+dfsg1+20180318/include/geometry/rtree.h:1642:
 void RTree::Classify(int, int, RTree::PartitionVars*) [with DATATYPE = KIGFX::VIEW_ITEM*; 
ELEMTYPE = int; int NUMDIMS = 2; ELEMTYPEREAL = float; int TMAXNODES = 8; int 
TMINNODES = 4]: Assertion `!a_parVars->m_taken[a_index]' failed.

Conversely, on an amd64 system, pcbnew starts fine.

Both systems are up-to-date installations of Debian buster,
with kicad pulled from Debian experimental.

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

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

Versions of packages kicad depends on:
ii  libc6   2.27-3
ii  libcairo2   1.15.10-1
ii  libcurl37.58.0-2
ii  libgcc1 1:8-20180414-1
ii  libgl1  1.0.0-2
ii  libglew2.0  2.0.0-5
ii  libglu1-mesa [libglu1]  9.0.0-2.1
ii  libgomp18-20180414-1
ii  libpixman-1-0   0.34.0-2
ii  libpython2.72.7.15~rc1-1
ii  libssl1.1   1.1.0h-2
ii  libstdc++6  8-20180414-1
ii  libwxbase3.0-0v53.0.4+dfsg-3
ii  libwxgtk3.0-gtk3-0v53.0.4+dfsg-3
ii  python  2.7.15~rc1-1
ii  python-wxgtk3.0 3.0.2.0+dfsg-7

Versions of packages kicad recommends:
ii  kicad-demos  5.0.0~rc1+dfsg1+20180318-3
ii  kicad-libraries  5.0.0~rc1+dfsg1+20180318-3
ii  xsltproc 1.1.29-5

Versions of packages kicad suggests:
pn  extra-xdg-menus   
ii  kicad-doc-en  5.0.0~rc1+dfsg1+20180318-3
pn  kicad-packages3d  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: kicad
Source-Version: 5.0.0~rc2+dfsg1-3

We believe that the bug you reported is fixed in the latest version of
kicad, 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 896...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Carsten Schoenert  (supplier of updated kicad 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, 06 Jun 2018 20:17:52 +0200
Source: kicad
Binary: kicad kicad-common kicad-demos kicad-doc-ca kicad-doc-de kicad-doc-en 
kicad-doc-es kicad-doc-fr kicad-doc-it kicad-doc-ja kicad-doc-nl kicad-doc-pl 
kicad-doc-ru kicad-libraries
Architecture: source
Version: 5.0.0~rc2+dfsg1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Electronics Team 

Changed-By: Carsten Schoenert 
Description:
 kicad  - Electronic schematic and PCB design software
 kicad-common - Old common files used by kicad - Transitional Package
 kicad-demos - Demo projects for kicad
 kicad-doc-ca - Kicad help files (Catalan)
 kicad-doc-de - Kicad help files (German)
 kicad-doc-en - Kicad help files (English)
 kicad-doc-es - Kicad help files (Spanish)
 kicad-doc-fr - Kicad help files (French)
 kicad-doc-it - Kicad help files (Italian)
 kicad-doc-ja - Kicad help files (Japanese)
 kicad-doc-nl - Kicad help files (Dutch)
 kicad-doc-pl - Kicad help files (Polish)
 kicad-doc-ru - Kicad help files (Russian)
 kicad-libraries - Virtual package providing common used libraries by kicad
Closes: 896706
Changes:
 kicad (5.0.0~rc2+dfsg1-3) unstable; urgency=medium
 .
   * [6a38e45] rebuild patch queue from patch-queue branch
 + added patch:
   

Bug#900924: [network-manager-gnome] segfault after upgrade to 1.8.12-1

[Shin Ice]

Package: network-manager-gnome
Version: 1.8.12-1
Severity: grave

--- Please enter the report below this line. ---

Hi,

after upgrading network-manager-gnome and libnma0 to 1.8.12-1 I receive
a segfault every time I open the menu to enable my vpn connection (that
is unfortunately a must have form me).

Doing a rollback of network-manager-gnome and libnma0 to 1.8.10-5 works
well and I can connect without problems.

Output from /var/log/messages:
Jun  6 20:40:05 kusanagi kernel: [  164.467043] nm-applet[1423]: segfault at 
2 ip 7fadd6faa509 sp 7ffeee5d7680 error 4 in 
libglib-2.0.so.0.5600.1[7fadd6f41000+113000]
Jun  6 20:40:54 kusanagi kernel: [  213.487060] nm-applet[3018]: segfault at 8 
ip 7f47ff2dfae3 sp 7ffd37922ee0 error 4 in 
libglib-2.0.so.0.5600.1[7f47ff277000+113000]
Jun  6 20:41:53 kusanagi kernel: [  273.201014] nm-applet[3112]: segfault at 
2 ip 7f32b5a73509 sp 7ffe3b82c640 error 4 in 
libglib-2.0.so.0.5600.1[7f32b5a0a000+113000]

Staring nm-applet from cli:
shin@kusanagi[~ ]139> nm-applet
zsh: segmentation fault  nm-applet
shin@kusanagi[~ ]139>

If you need more or different output, let me know :)

Thanks and greetings
Shin

--- System information. ---
Architecture:
Kernel:   Linux 4.16.0-2-amd64

Debian Release: buster/sid
  500 xenial  updates.signal.org
  500 unstableftp.de.debian.org
  500 sid-pgdgapt.postgresql.org

--- Package information. ---
Depends   (Version) | Installed
===-+-=
libatk1.0-0 (>= 1.12.4) | 2.28.1-1
libayatana-appindicator3-1  (>= 0.4.90) | 0.5.3-3
libc6 (>= 2.14) | 2.27-3
libcairo2(>= 1.2.4) | 1.15.10-3
libgdk-pixbuf2.0-0  (>= 2.22.0) | 2.36.11-2
libglib2.0-0(>= 2.43.2) | 2.56.1-2
libgtk-3-0(>= 3.10) | 3.22.30-1
libjansson4  (>= 2.0.1) | 2.11-1
libmm-glib0(>= 0.7.991) | 1.7.990-1
libnm0   (>= 1.8.0) | 1.10.8-1
libnma0(= 1.8.12-1) | 1.8.12-1
libnotify4   (>= 0.7.0) | 0.7.7-3
libpango-1.0-0  (>= 1.14.0) | 1.42.1-1
libpangocairo-1.0-0 (>= 1.14.0) | 1.42.1-1
libsecret-1-0  (>= 0.7) | 0.18.6-2
libselinux1  (>= 2.1.9) | 2.8-1
dconf-gsettings-backend | 0.28.0-2
 OR gsettings-backend   |
network-manager(>= 1.8) | 1.10.8-1
policykit-1-gnome   | 0.105-7
 OR polkit-1-auth-agent |
default-dbus-session-bus|
 OR dbus-session-bus|


Recommends  (Version) | Installed
=-+-===
notification-daemon   | 3.20.0-3
gnome-keyring | 3.28.2-1
mobile-broadband-provider-info| 20170903-1
iso-codes | 3.79-1


Suggests   (Version) | Installed
-+-===
network-manager-openconnect-gnome| 1.2.4-1
network-manager-openvpn-gnome|
network-manager-vpnc-gnome   |
network-manager-pptp-gnome   |





--

I'm just a placeholder for a really awesome signature...
...that is still missing *sob*


signature.asc
Description: PGP signature

Bug#893416: marked as done (sezpoz FTBFS with openjdk-9)

[Debian Bug Tracking System]

Your message dated Wed, 06 Jun 2018 18:43:41 +
with message-id 
and subject line Bug#893416: fixed in sezpoz 1.12-1
has caused the Debian Bug report #893416,
regarding sezpoz FTBFS with openjdk-9
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.)


-- 
893416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893416
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sezpoz
Version: 1.10-2
Severity: serious
Tags: buster sid

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

...
[INFO] ---
[INFO]  T E S T S
[INFO] ---
[INFO] Running net.java.sezpoz.IndexTest
warning: Supported source version 'RELEASE_6' from annotation processor 
'net.java.sezpoz.impl.Indexer6' less than -source '1.9'
/tmp/net.java.sezpoz.IndexTest/test1/src/x/A.java:5: warning: should be marked 
@Retention(RetentionPolicy.SOURCE)
public @interface A {}
^
error: java.nio.file.NoSuchFileException: 
/tmp/net.java.sezpoz.IndexTest/test1/clz/META-INF/annotations/x.A
1 error
2 warnings
warning: Supported source version 'RELEASE_6' from annotation processor 
'net.java.sezpoz.impl.Indexer6' less than -source '1.9'
/tmp/net.java.sezpoz.IndexTest/test2/src/x/A.java:6: warning: should be marked 
@Retention(RetentionPolicy.SOURCE)
public @interface A {
^
error: java.nio.file.NoSuchFileException: 
/tmp/net.java.sezpoz.IndexTest/test2/clz/META-INF/annotations/x.A
1 error
2 warnings
warning: Supported source version 'RELEASE_6' from annotation processor 
'net.java.sezpoz.impl.Indexer6' less than -source '1.9'
/tmp/net.java.sezpoz.IndexTest/test3/src/api/MenuItem.java:6: warning: should 
be marked @Retention(RetentionPolicy.SOURCE)
public @interface MenuItem {
^
error: java.nio.file.NoSuchFileException: 
/tmp/net.java.sezpoz.IndexTest/test3/clz/META-INF/annotations/api.MenuItem
1 error
2 warnings
warning: Supported source version 'RELEASE_6' from annotation processor 
'net.java.sezpoz.impl.Indexer6' less than -source '1.9'
/tmp/net.java.sezpoz.IndexTest/test4/src/x/A.java:5: warning: should be marked 
@Retention(RetentionPolicy.SOURCE)
public @interface A {
^
error: java.nio.file.NoSuchFileException: 
/tmp/net.java.sezpoz.IndexTest/test4/clz/META-INF/annotations/x.A
1 error
2 warnings
warning: Supported source version 'RELEASE_6' from annotation processor 
'net.java.sezpoz.impl.Indexer6' less than -source '1.9'
/tmp/net.java.sezpoz.IndexTest/test5/src/x/A.java:6: warning: should be marked 
@Retention(RetentionPolicy.SOURCE)
public @interface A {
^
error: java.nio.file.NoSuchFileException: 
/tmp/net.java.sezpoz.IndexTest/test5/clz/META-INF/annotations/x.A
1 error
2 warnings
warning: Supported source version 'RELEASE_6' from annotation processor 
'net.java.sezpoz.impl.Indexer6' less than -source '1.9'
error: java.nio.file.NoSuchFileException: 
/tmp/net.java.sezpoz.IndexTest/test6/clz/META-INF/annotations/net.java.sezpoz.IndexTest$Marker
1 error
1 warning
warning: Supported source version 'RELEASE_6' from annotation processor 
'net.java.sezpoz.impl.Indexer6' less than -source '1.9'
/tmp/net.java.sezpoz.IndexTest/test7/src/x/A.java:5: warning: should be marked 
@Retention(RetentionPolicy.SOURCE)
public @interface A {
^
error: java.nio.file.NoSuchFileException: 
/tmp/net.java.sezpoz.IndexTest/test7/clz/META-INF/annotations/x.A
1 error
2 warnings
warning: Supported source version 'RELEASE_6' from annotation processor 
'net.java.sezpoz.impl.Indexer6' less than -source '1.9'
/tmp/net.java.sezpoz.IndexTest/test8/src/x/A.java:5: warning: should be marked 
@Retention(RetentionPolicy.SOURCE)
public @interface A {}
^
error: java.nio.file.NoSuchFileException: 
/tmp/net.java.sezpoz.IndexTest/test8/clz/META-INF/annotations/x.A
1 error
2 warnings
[ERROR] Tests run: 8, Failures: 0, 
Errors: 8, Skipped: 0, Time elapsed: 3.751 s <<< 
FAILURE! - in net.java.sezpoz.IndexTest
[ERROR] multipleCodeSources(net.java.sezpoz.IndexTest)  Time elapsed: 
1.474 s  <<< ERROR!
net.java.sezpoz.impl.AptFailedException: processing failed with error code 1
at net.java.sezpoz.IndexTest.multipleCodeSources(IndexTest.java:209)

[ERROR] complexStructure(net.java.sezpoz.IndexTest)  Time elapsed: 
0.425 s  <<< ERROR!
net.java.sezpoz.impl.AptFailedException: processing failed with error code 1
at 

Bug#896741: themole: missing build dependency on dh-python

[Raúl Benencia]

tags 896741 + pending
thanks

Hi Adrian,

On Tue, Apr 24, 2018 at 09:57:04AM +0300, Adrian Bunk wrote:
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/themole.html
> 
> ...
>  fakeroot debian/rules clean
> dh clean --with python3
> dh: unable to load addon python3: Can't locate 
> Debian/Debhelper/Sequence/python3.pm in @INC (you may need to install the 
> Debian::Debhelper::Sequence::python3 module) (@INC contains: /etc/perl 
> /usr/local/lib/x86_64-linux-gnu/perl/5.26.2 /usr/local/share/perl/5.26.2 
> /usr/lib/x86_64-linux-gnu/perl5/5.26 /usr/share/perl5 
> /usr/lib/x86_64-linux-gnu/perl/5.26 /usr/share/perl/5.26 
> /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at (eval 7) 
> line 1.
> BEGIN failed--compilation aborted at (eval 7) line 1.
> 
> make: *** [debian/rules:5: clean] Error 2

Thanks for reporting this. A fix is on its way.

Cheers,
Raul

Processed: Re: Bug#896741: themole: missing build dependency on dh-python

[Debian Bug Tracking System]

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

> tags 896741 + pending
Bug #896741 [src:themole] themole: missing build dependency on dh-python
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#900869: marked as done (segfault when updating list of wireless networks)

[Debian Bug Tracking System]

Your message dated Wed, 06 Jun 2018 18:19:54 +
with message-id 
and subject line Bug#900869: fixed in network-manager-applet 1.8.12-2
has caused the Debian Bug report #900869,
regarding segfault when updating list of wireless networks
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.)


-- 
900869: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900869
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: network-manager-gnome
Version: 1.8.12-1
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hey!

Since the last update of nm-applet, it crashes for me when displaying
the regular menu (left-click). Here is a backtrace of the problem:

gdb$  bt full
#0  0x74f00509 in g_slice_alloc () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x74f01586 in g_slist_prepend () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x751c17cb in  () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#3  0x751c3992 in g_object_notify_by_pspec () at 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#4  0x769d87c1 in gtk_widget_unparent () at 
/lib/x86_64-linux-gnu/libgtk-3.so.0
#5  0x76768536 in  () at /lib/x86_64-linux-gnu/libgtk-3.so.0
#6  0x751c0149 in g_cclosure_marshal_VOID__OBJECTv () at 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#7  0x751bd1a6 in  () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#8  0x751d86df in g_signal_emit_valist () at 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#9  0x751d8e0f in g_signal_emit () at 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#10 0x767b5a26 in gtk_container_remove () at 
/lib/x86_64-linux-gnu/libgtk-3.so.0
#11 0x769cedb3 in  () at /lib/x86_64-linux-gnu/libgtk-3.so.0
#12 0x751c3648 in g_object_run_dispose () at 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#13 0x767b74de in  () at /lib/x86_64-linux-gnu/libgtk-3.so.0
#14 0x751bcf6d in g_closure_invoke () at 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#15 0x751cfeb2 in  () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#16 0x751d83f5 in g_signal_emit_valist () at 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#17 0x751d8e0f in g_signal_emit () at 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#18 0x769cee8c in  () at /lib/x86_64-linux-gnu/libgtk-3.so.0
#19 0x751c1e03 in g_object_unref () at 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#20 0x767b5a39 in gtk_container_remove () at 
/lib/x86_64-linux-gnu/libgtk-3.so.0
#21 0x5556928c in applet_update_menu (user_data=) at 
src/applet.c:2032
applet = 0x5583a290
children = 0x5597a1a0
elt = 0x55979e40
menu = 0x55b42590
#22 0x74ee30f5 in g_main_context_dispatch () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x74ee34c0 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x74ee354c in g_main_context_iteration () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x754a3cdd in g_application_run () at 
/lib/x86_64-linux-gnu/libgio-2.0.so.0
#26 0x55564551 in main (argc=, argv=) at 
src/main.c:81
applet = 0x5583a290
fake_args = {0x7fffe8f0 "/usr/bin/nm-applet"}
i = 
status = 

Disabling wireless makes the problem go away.

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

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

Versions of packages network-manager-gnome depends on:
ii  dbus-user-session [default-dbus-session-bus]  1.12.8-2
ii  dbus-x11 [dbus-session-bus]   1.12.8-2
ii  dconf-gsettings-backend [gsettings-backend]   0.28.0-2
ii  libatk1.0-0   2.28.1-1
ii  libayatana-appindicator3-10.5.3-3
ii  libc6 2.27-3
ii  libcairo2 1.15.10-3
ii  libgdk-pixbuf2.0-02.36.11-2
ii  libglib2.0-0  2.56.1-2
ii  libgtk-3-03.22.30-1
ii  libjansson4   2.11-1
ii  libmm-glib0   1.7.990-1
ii  libnm01.10.8-1
ii  

Processed: Bug #893416 in sezpoz marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #893416 [src:sezpoz] sezpoz FTBFS with openjdk-9
Added tag(s) pending.

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

Bug#893416: Bug #893416 in sezpoz marked as pending

[ebourg]

Control: tag -1 pending

Hello,

Bug #893416 in sezpoz 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/java-team/sezpoz/commit/6aa596554b783ff49efa9db8c74cfff44c0505df


Ignore the test failures to avoid the FTBFS with Java 9 (Closes: #893416)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/893416

Bug#895551: marked as done (haskell-gloss-rendering: upper bound on base older than ghc 8.2's)

[Debian Bug Tracking System]

Your message dated Wed, 6 Jun 2018 19:44:24 +0200
with message-id <2d758d0f-0147-4521-cecd-f2e6ed356...@debian.org>
and subject line Re: haskell-gloss-rendering: upper bound on base older than 
ghc 8.2's
has caused the Debian Bug report #895551,
regarding haskell-gloss-rendering: upper bound on base older than ghc 8.2's
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.)


-- 
895551: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895551
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-gloss-rendering
Version: 1.11.1.1-2
Severity: serious

https://github.com/Teaspot-Studio/gloss-rendering/issues/1
--- End Message ---
--- Begin Message ---
control: fixed -1 1.11.1.1-3
thanks

On Thu, 12 Apr 2018 13:53:42 + Clint Adams  wrote:
> Source: haskell-gloss-rendering
> Version: 1.11.1.1-2
> Severity: serious
> 
> https://github.com/Teaspot-Studio/gloss-rendering/issues/1
> 
> --- End Message ---

Processed: severity of 900869 is serious

[Debian Bug Tracking System]

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

> severity 900869 serious
Bug #900869 [network-manager-gnome] segfault when updating list of wireless 
networks
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#900855: [qtquickcontrols2-opensource-src] FTBFS font fontenello

[Lisandro Damián Nicanor Pérez Meyer]

On Wed, 6 Jun 2018 at 11:53, Bastien ROUCARIES
 wrote:
[snip]
> > Sorry, but I can't make sense of what you wrote
>
>
> Source of the file quoted are here https://github.com/fontello/fontelico.font
>
> it could not be build for now due to lack of depends.
>
> It is a policy violation to ship something that could not be built.
>
> They are a few solution:
> - repack and remove the files
> - wait, I am uploading a /fontelico.font

Sigh, please try harder. You first reported a FTBFS but I can't see
any FTBFS there. Then *I think* you are trying to report we are
shipping a file which does not has sources. And you don't even provide
a version.

Please pretty please use reportbug next time, and work harder on
preparing more detailed reports.


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

Bug#900533: chromium 67.0.3396.62-1: youtube video, gif's, html5, and movies no longer work

[jim_p]

Package: chromium
Version: 67.0.3396.62-1
Followup-For: Bug #900533

Dear Maintainer,

Is there any info on when this issue could be fixed? It has been a week since
this bug report was opened and there are no official comments here regarding
any progress, neither some newer source package suggesting there is a patch for
it or a fix.

I personally use chromium for its superb html5-based multimedia support. Now
that this support is completely broken, I have no reason to use it anymore and
I think of moving to chrome.



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

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

Versions of packages chromium depends on:
ii  chromium-common  67.0.3396.62-1
ii  libasound2   1.1.6-1
ii  libatk-bridge2.0-0   2.26.2-1
ii  libatk1.0-0  2.28.1-1
ii  libavcodec57 10:3.4.2-dmo3
ii  libavformat5710:3.4.2-dmo3
ii  libavutil55  10:3.4.2-dmo3
ii  libc62.27-3
ii  libcairo21.15.10-3
ii  libcups2 2.2.7-5
ii  libdbus-1-3  1.12.8-2
ii  libevent-2.1-6   2.1.8-stable-4
ii  libexpat12.2.5-3
ii  libflac8 1.3.2-3
ii  libfontconfig1   2.13.0-5
ii  libfreetype6 2.8.1-2
ii  libgcc1  1:8.1.0-5
ii  libgdk-pixbuf2.0-0   2.36.11-2
ii  libglib2.0-0 2.56.1-2
ii  libgtk-3-0   3.22.29-3
ii  libharfbuzz0b1.7.6-1+b1
ii  libicu60 60.2-6
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  liblcms2-2   2.9-1
ii  libminizip1  1.1-8+b1
ii  libnspr4 2:4.19-3
ii  libnss3  2:3.37.1-1
ii  libopenjp2-7 2.3.0-1
ii  libopus0 1.3~beta+20180518-1
ii  libpango-1.0-0   1.42.0-1
ii  libpangocairo-1.0-0  1.42.0-1
ii  libpng16-16  1.6.34-1
ii  libpulse011.1-5
ii  libre2-4 20180301+dfsg-1
ii  libsnappy1v5 1.1.7-1
ii  libstdc++6   8.1.0-5
ii  libvpx5  1.7.0-3
ii  libwebp6 0.6.1-2
ii  libwebpdemux20.6.1-2
ii  libwebpmux3  0.6.1-2
ii  libx11-6 2:1.6.5-1
ii  libx11-xcb1  2:1.6.5-1
ii  libxcb1  1.13-1
ii  libxcomposite1   1:0.4.4-2
ii  libxcursor1  1:1.1.15-1
ii  libxdamage1  1:1.1.4-3
ii  libxext6 2:1.3.3-1+b2
ii  libxfixes3   1:5.0.3-1
ii  libxi6   2:1.7.9-1
ii  libxml2  2.9.4+dfsg1-7
ii  libxrandr2   2:1.5.1-1
ii  libxrender1  1:0.9.10-1
ii  libxslt1.1   1.1.32-2
ii  libxss1  1:1.2.2-1+b2
ii  libxtst6 2:1.2.3-1
ii  zlib1g   1:1.2.11.dfsg-1

Versions of packages chromium recommends:
ii  fonts-liberation  1:1.07.4-7
ii  libgl1-mesa-dri   18.0.4-1

Versions of packages chromium suggests:
pn  chromium-driver  
pn  chromium-l10n
pn  chromium-shell   

-- no debconf information

Processed: tagging 849665

[Debian Bug Tracking System]

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

> tags 849665 + help
Bug #849665 [src:golang-github-coreos-go-tspi] golang-github-coreos-go-tspi: 
FTBFS on 32-bit: type [1073741824]C.struct_tdTSS_PCR_EVENT larger than address 
space
Added tag(s) help.
> thanks
Stopping processing here.

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

Bug#893604: marked as done (mumble: Add support to build with upcoming Ice 3.7.0 release)

[Debian Bug Tracking System]

Your message dated Wed, 6 Jun 2018 15:19:53 +
with message-id 
and subject line Bug done with mumble_1.2.19-2 upload, forgot to close in 
changelog
has caused the Debian Bug report #893604,
regarding mumble: Add support to build with upcoming Ice 3.7.0 release
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.)


-- 
893604: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893604
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mumble
Severity: normal

Dear Maintainer,

We are in the process of uploading an new Ice version (zeroc-ice 3.7.0-1)
and we have noticed that the mumble builds will not work and some minor
fixes are required

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

Kernel: Linux 4.15.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
I added the patch to the 1.2.19-2 upload that was just accepted, but forgot to
close the bug in the debian/changelog. Closing the bug manually.

(I've checked the resulting package to make sure the FTBFS bug is fixed, and
that both mumble and mumble-server work.)

  -- Chris

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

Bug#893101: marked as done (bridge-method-injector FTBFS with openjdk-9)

[Debian Bug Tracking System]

Your message dated Wed, 06 Jun 2018 15:04:22 +
with message-id 
and subject line Bug#893101: fixed in bridge-method-injector 1.18-2
has caused the Debian Bug report #893101,
regarding bridge-method-injector FTBFS with openjdk-9
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.)


-- 
893101: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893101
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bridge-method-injector
Version: 1.18-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/bridge-method-injector.html

...
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-antrun-plugin:1.8:run (default) on project 
bridge-method-injector: An Ant BuildException has occured: Compile failed; see 
the compiler error output for details.
[ERROR] around Ant part .. 
@ 17:125 in 
/build/1st/bridge-method-injector-1.18/injector/target/antrun/build-main.xml
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :bridge-method-injector
dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/build/1st/bridge-method-injector-1.18 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/build/1st/bridge-method-injector-1.18/debian/maven.properties
 org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Ddebian.dir=/build/1st/bridge-method-injector-1.18/debian 
-Dmaven.repo.local=/build/1st/bridge-method-injector-1.18/debian/maven-repo 
--batch-mode package javadoc:jar javadoc:aggregate -DskipTests 
-Dnotimestamp=true -Dlocale=en_US returned exit code 1
make: *** [debian/rules:4: build] Error 2
--- End Message ---
--- Begin Message ---
Source: bridge-method-injector
Source-Version: 1.18-2

We believe that the bug you reported is fixed in the latest version of
bridge-method-injector, 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 893...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated bridge-method-injector 
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: Wed, 06 Jun 2018 15:30:34 +0200
Source: bridge-method-injector
Binary: libbridge-method-injector-java libbridge-method-injector-java-doc
Architecture: source
Version: 1.18-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 libbridge-method-injector-java - Evolve Java classes without breaking 
compatibility
 libbridge-method-injector-java-doc - Documentation for Bridge Method Injector
Closes: 893101
Changes:
 bridge-method-injector (1.18-2) unstable; urgency=medium
 .
   * Team upload.
   * Fixed the build failure with Java 9 (Closes: #893101)
   * Standards-Version updated to 4.1.4
   * Switch to debhelper level 11
   * Use salsa.debian.org Vcs-* URLs
Checksums-Sha1:
 a4b353506e64fdf5333bc5816bc163f7eeedfab6 2442 bridge-method-injector_1.18-2.dsc
 0c34a2f944ed1328869718169326703e705e13f7 4828 
bridge-method-injector_1.18-2.debian.tar.xz
 2518030a85fae64dcdc55157eb6375f48f8b1ded 15126 
bridge-method-injector_1.18-2_source.buildinfo
Checksums-Sha256:
 1fe0e1ef1a7808e497e5e49a3dc25ea6954d7ec251c81afd710bf8c11126273e 2442 
bridge-method-injector_1.18-2.dsc
 e784846832ef005e905c45cd9c40972c598e66b7421b8302a4668ed4e7861acf 4828 
bridge-method-injector_1.18-2.debian.tar.xz
 1d079051a5c93b743ac1cbc3d8cb00762c2659a9cf27a886b8547419119626b1 15126 
bridge-method-injector_1.18-2_source.buildinfo
Files:
 20d39612e36d8c67a65c6cbe70ef39a3 2442 java optional 
bridge-method-injector_1.18-2.dsc
 

Processed: Bug #893101 in bridge-method-injector marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #893101 [src:bridge-method-injector] bridge-method-injector FTBFS with 
openjdk-9
Added tag(s) pending.

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

Bug#893101: Bug #893101 in bridge-method-injector marked as pending

[ebourg]

Control: tag -1 pending

Hello,

Bug #893101 in bridge-method-injector 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/java-team/bridge-method-injector/commit/cdc15a50947a4bb1c7495aaf16b73be1ee56e586


Fixed the build failure with Java 9 (Closes: #893101)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/893101

Bug#900855: [qtquickcontrols2-opensource-src] FTBFS font fontenello

[Bastien ROUCARIES]

Hi,

On Wed, Jun 6, 2018 at 2:34 PM, Lisandro Damián Nicanor Pérez Meyer
 wrote:
> Hi Bastien!
>
> El mar., 5 de jun. de 2018 19:12, Bastien ROUCARIÈS
>  escribió:
>>
>> Package: qtquickcontrols2-opensource-src
>> Severity: serious
>>
>> Hi,
>> examples/quickcontrols2/swipetoremove/fonts/fontello.ttf
>>
>> fail to build from source
>>
>> In your case I suppose they are no need to wait that I upload the package.
>>
>> A repack will be quicker
>
>
> Sorry, but I can't make sense of what you wrote


Source of the file quoted are here https://github.com/fontello/fontelico.font

it could not be build for now due to lack of depends.

It is a policy violation to ship something that could not be built.

They are a few solution:
- repack and remove the files
- wait, I am uploading a /fontelico.font

Bastien

Bug#900902: predict does not trap build command errors (policy 4.6)

[Helmut Grohne]

Source: predict
Version: 2.2.3-4
Severity: serious
Justification: Debian policy section 4.6

predict's debian/rules chains commands with ";" in a lot of places. This
covers simply "cd something; execute something else", but also longer
chains involving autoconf or the like. Such practise is prohibited by
Debian policy section 4.6 as it risks producing misbuilds and makes
debugging build failures unnecessarily hard.

Helmut

Bug#900897: missing dependency on pciutils

[Thomas Goirand]

Package: ladvd
Version: 1.1.1~pre1-2+b2
Severity: grave

Hi Marco,

ladvd, on startup, reads /usr/share/misc/pci.ids. If it can't read it, then it
segfaults. You probably have missed it because you've only used ladvd on
machines installed by d-i with recommends activated, which isn't my case (I
used a home-brewed installer that is simply using debootstrap).

In my book, this:

"makes the package in question unusable by most or all users"

which grants a severity: grave.

Please note that the issue is on both Sid and Stable, and it would be nice if
you could fix the package in Stretch as well.

Also, the /var/run/ladvd seemed missing on startup of ladvd. This also needs
investigation (though that's not the core of this bug report).

Cheers,

Thomas Goirand (zigo)

Bug#900629: debian-edu-install: breaks installation of samba

[Holger Levsen]

On Wed, Jun 06, 2018 at 03:12:27PM +0200, Wolfgang Schweer wrote:
> > > installation must not fail just because the hostname is
> > > profitbricks-build-amd64 or whatever.

^^ this is still valid. (and I ment: "installation of any package must
not fail…")

> > IMHO, this is a samba bug...
> 
> Depends on the POV, I guess:
> 
> Seen from Samba, the long hostname is an issue.
> Seen from Jenkins, Samba should do better.

jenkins is not a package, jenkins and ci are just (some kind of) "users"
which install packages, like an admin would do.

and as written above, packages must not fail to install just because a
system uses a strange hostname.

so, both samba and debian-edu-install used to install nicely on that
host using that hostname. since debian-edu-install 2.10.9 this fails.
samba still installs nicely alone.

> > I agree, but the fix needs to be in Samba.
> Might be better, yes. Maybe the Samba maintainers would accept something 
> like this:

well, maybe, you should ask them. just as laid out above, I think this
would be a different bug, with severity wishlist.

*this* bug here, still needs to be fixed in debian-edu-install.


-- 
cheers,
Holger


signature.asc
Description: PGP signature

Bug#900511: Another data point : libcurl4 causes problems with R packages.

[CHARPENTIER Emmanuel]

I have another bone of contention with that : some R packages (so far, I've 
found the problem with car and robCompositions) cannot be installed (from CRAN) 
if the symbol CURL_OPENSSL_3 isn't available at compilation time (this symbol  
is available with libcurl3 (in the file libcurl.so.4), but not with libcurl4).

Furthermore, one cannot (re-)install libcurl3 without losing a lot of packages 
(most notably r-base and r-base-core) :

charpent@p-202-021:~$ apt-get install -s libcurl3
NOTE: Ceci n'est qu'une simulation !
  apt-get a besoin des privilèges du superutilisateur
  pour pouvoir vraiment fonctionner.
  Veuillez aussi noter que le verrouillage est désactivé,
  et la situation n'est donc pas forcément représentative
  de la réalité !
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture des informations d'état... Fait
Les paquets suivants ont été installés automatiquement et ne sont plus 
nécessaires :
  libaprutil1-dbd-sqlite3 libaprutil1-ldap libbz2-dev liblzma-dev
  libminiupnpc17 libnatpmp1 libncurses-dev libncurses5-dev libreadline-dev
  minissdpd transmission-common
Veuillez utiliser « apt autoremove » pour les supprimer.
Les paquets suivants seront ENLEVÉS :
  apache2 apache2-bin clamav curl gnome gnome-core gnome-user-share
  libapache2-mod-dnssd libcurl4 libcurl4-openssl-dev
  libstrongswan-extra-plugins r-base r-base-core r-base-dev r-base-html
  r-cran-boot r-cran-class r-cran-codetools r-cran-kernsmooth r-cran-lattice
  r-cran-mass r-cran-matrix r-cran-mgcv r-cran-nlme r-cran-nnet r-cran-rpart
  r-cran-spatial r-cran-survival r-recommended transmission-gtk
Les NOUVEAUX paquets suivants seront installés :
  libcurl3
0 mis à jour, 1 nouvellement installés, 30 à enlever et 0 non mis à jour.
Remv apache2 [2.4.33-3+b1]
Remv gnome [1:3.22+9]
Remv gnome-core [1:3.22+9]
Remv gnome-user-share [3.18.3-3]
Remv libapache2-mod-dnssd [0.6-3.2]
Remv apache2-bin [2.4.33-3+b1]
Remv clamav [0.100.0+dfsg-1+b2]
Remv curl [7.60.0-2]
Remv libstrongswan-extra-plugins [5.6.2-2+b1]
Remv r-base [3.4.4-1]
Remv r-recommended [3.4.4-1]
Remv r-cran-rpart [4.1-13-1]
Remv r-cran-survival [2.42-3-1]
Remv r-cran-spatial [7.3-11-2+b1]
Remv r-base-core [3.4.4-1+b2] [r-cran-mgcv:amd64 r-base-html:amd64 
r-cran-class:amd64 r-cran-boot:amd64 r-cran-kernsmooth:amd64 
r-cran-codetools:amd64 r-base-dev:amd64 r-cran-lattice:amd64 r-cran-nnet:amd64 
r-cran-mass:amd64 ]
Remv libcurl4 [7.60.0-2] [r-cran-mgcv:amd64 r-base-html:amd64 
r-cran-class:amd64 r-cran-boot:amd64 r-cran-kernsmooth:amd64 
r-cran-codetools:amd64 libcurl4-openssl-dev:amd64 transmission-gtk:amd64 
r-base-dev:amd64 r-cran-lattice:amd64 r-cran-nnet:amd64 r-cran-mass:amd64 ]
Remv libcurl4-openssl-dev [7.60.0-2] [r-cran-mgcv:amd64 r-base-html:amd64 
r-cran-class:amd64 r-cran-boot:amd64 r-cran-kernsmooth:amd64 
r-cran-codetools:amd64 transmission-gtk:amd64 r-base-dev:amd64 
r-cran-lattice:amd64 r-cran-nnet:amd64 r-cran-mass:amd64 ]
Remv r-base-dev [3.4.4-1] [r-cran-mgcv:amd64 r-base-html:amd64 
r-cran-class:amd64 r-cran-boot:amd64 r-cran-kernsmooth:amd64 
r-cran-codetools:amd64 transmission-gtk:amd64 r-cran-lattice:amd64 
r-cran-nnet:amd64 r-cran-mass:amd64 ]
Remv r-base-html [3.4.4-1] [r-cran-mgcv:amd64 r-cran-class:amd64 
r-cran-boot:amd64 r-cran-kernsmooth:amd64 r-cran-codetools:amd64 
transmission-gtk:amd64 r-cran-lattice:amd64 r-cran-nnet:amd64 r-cran-mass:amd64 
]
Remv r-cran-boot [1.3-20-1.1] [r-cran-mgcv:amd64 r-cran-class:amd64 
r-cran-kernsmooth:amd64 r-cran-codetools:amd64 transmission-gtk:amd64 
r-cran-lattice:amd64 r-cran-nnet:amd64 r-cran-mass:amd64 ]
Remv r-cran-class [7.3-14-2+b1] [r-cran-mgcv:amd64 r-cran-kernsmooth:amd64 
r-cran-codetools:amd64 transmission-gtk:amd64 r-cran-lattice:amd64 
r-cran-nnet:amd64 r-cran-mass:amd64 ]
Remv r-cran-codetools [0.2-15-1.1] [r-cran-mgcv:amd64 r-cran-kernsmooth:amd64 
transmission-gtk:amd64 r-cran-lattice:amd64 r-cran-nnet:amd64 r-cran-mass:amd64 
]
Remv r-cran-kernsmooth [2.23-15-3+b2] [r-cran-mgcv:amd64 transmission-gtk:amd64 
r-cran-lattice:amd64 r-cran-nnet:amd64 r-cran-mass:amd64 ]
Remv r-cran-mgcv [1.8-23-1] [transmission-gtk:amd64 r-cran-lattice:amd64 
r-cran-nnet:amd64 r-cran-mass:amd64 ]
Remv r-cran-matrix [1.2-14-1] [transmission-gtk:amd64 r-cran-lattice:amd64 
r-cran-nnet:amd64 r-cran-mass:amd64 ]
Remv r-cran-nlme [3.1.137-1] [transmission-gtk:amd64 r-cran-lattice:amd64 
r-cran-nnet:amd64 r-cran-mass:amd64 ]
Remv r-cran-lattice [0.20-35-1+b1] [transmission-gtk:amd64 r-cran-nnet:amd64 
r-cran-mass:amd64 ]
Remv r-cran-mass [7.3-50-1] [transmission-gtk:amd64 r-cran-nnet:amd64 ]
Remv r-cran-nnet [7.3-12-2+b1] [transmission-gtk:amd64 ]
Remv transmission-gtk [2.94-1+b2]
Inst libcurl3 (7.60.0-1 Debian:testing, Debian:unstable [amd64])
Conf libcurl3 (7.60.0-1 Debian:testing, Debian:unstable [amd64])
charpent@p-202-021:~$ apt-cache search libcurl4
libcurl4 - bibliothèque de transfert par URL côté client et simple 
d'utilisation - avec OpenSSL
libcurl4-doc - 

Bug#900629: debian-edu-install: breaks installation of samba

[Wolfgang Schweer]

On Wed, Jun 06, 2018 at 12:02:47AM +, Mike Gabriel wrote:
> On  Di 05 Jun 2018 19:03:59 CEST, Holger Levsen wrote:
> > On Tue, Jun 05, 2018 at 01:06:52PM +0200, Wolfgang Schweer wrote:
> > > > netbios name PROFITBRICKS-BUILD10-AMD64 is not a valid netbios name
> > > > ERROR: Invalid smb.conf
> > > > dpkg: error processing package samba-common-bin (--configure):
> > > >  installed samba-common-bin package post-installation script subprocess
> > > >  returned error exit status 255
> > > IMO this bug should/could be fixed in jenkins.d.n by setting a valid
> > > netbios name via $(hostname).
> > 
> > no.
> > 
> > installation must not fail just because the hostname is
> > profitbricks-build-amd64 or whatever.
> 
> IMHO, this is a samba bug...

Depends on the POV, I guess:

Seen from Samba, the long hostname is an issue.
Seen from Jenkins, Samba should do better.

In the comparable samba/debci case, debci has a pending fix (netbios 
compliant hostname). The issue has been discussed at some length, see:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898875 
 
> > > For Debian Edu the netbios name is set to TJENER, but at the moment
> > > samba-common-bin gets installed, the vanilla smb.conf is tested (plus
> > > preseeded values w/ netbios name not preseedable), replaced with the
> > > Debian Edu one later (via Cfengine). So there's nothing Debian Edu can
> > > do to fix this bug (afaict).
> > 
> > we can shorten the netbios name if using the hostname for the netbios
> > name is problematic because its too long.
> > 
> > > Please check the attached patch.
> > 

> > NACK, see above :)
> 
> I agree, but the fix needs to be in Samba.
 
Might be better, yes. Maybe the Samba maintainers would accept something 
like this:

--- a/samba-common-bin.postinst 2018-06-06 14:13:40.612764675 +0200
+++ b/samba-common-bin.postinst 2018-06-06 14:28:30.645949184 +0200
@@ -3,7 +3,14 @@
 set -e
 
 echo "Checking smb.conf"
-samba-tool testparm -d1 --suppress-prompt > /dev/null
+if [ $(hostname|wc -m) -le 15 ] ; then
+samba-tool testparm -d1 --suppress-prompt > /dev/null
+else
+echo "WARNING: The hostname is too long to serve as netbios name."
+echo "Please set a valid netbios name, see man (5) smb.conf for details."
+testparm -d1 -s --option='netbios name = test' > /dev/null
+fi
 echo "Done"
 
 
+#DEBHELPER#
--

It would only warn instead of erroring out in case of too long 
hostnames. I figure this being enough to fix #816301, starting point for 
all this, see:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816301
and
https://salsa.debian.org/samba-team/samba/blob/648ea6aa3c191c20d67cb765abfee6e8993e394b/debian/samba-common-bin.postinst

Wolfgang


signature.asc
Description: PGP signature

Bug#900637: marked as done (python-catkin-pkg: catkin 0.7.12-2 and python-catkin-pkg 0.4.3-1 both provide /usr/bin/catkin_package_version)

[Debian Bug Tracking System]

Your message dated Wed, 06 Jun 2018 13:06:25 +
with message-id 
and subject line Bug#900637: fixed in ros-catkin-pkg 0.4.3-2
has caused the Debian Bug report #900637,
regarding python-catkin-pkg: catkin 0.7.12-2 and python-catkin-pkg 0.4.3-1 both 
provide /usr/bin/catkin_package_version
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.)


-- 
900637: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900637
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-catkin-pkg
Version: 0.4.3-5
Severity: grave
Justification: renders package uninstallable, so it should show up in 
apt-listbugs

Hi,

python-catkin-pkg 0.4.3-1 doesn't declare conflicts or breaks on catkin 
0.7.12-2, but they can't be installed together, and catkin 0.7.12-2 depends on 
python-catkin-pkg.

Unpacking python-catkin-pkg (0.4.3-1) over (0.4.2-3) ...
dpkg: error processing archive 
/var/cache/apt/archives/python-catkin-pkg_0.4.3-1_all.deb (--unpack):
 trying to overwrite '/usr/bin/catkin_package_version', which is also in 
package catkin 0.7.12-2
Errors were encountered while processing:
 /var/cache/apt/archives/python-catkin-pkg_0.4.3-1_all.deb


Versions of packages installed:
ii  catkin0.7.12-2
ii  python-catkin-pkg 0.4.2-3

I assume this is waiting for catkin 0.7.13 to be packaged, but please declare 
the versioned dependency.

Thanks,
Steve

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

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

Versions of packages python-catkin-pkg depends on:
ii  libpython2.7-stdlib [python-argparse]  2.7.15-1
ii  python 2.7.15~rc1-1
ii  python-dateutil2.6.1-1
ii  python-docutils0.14+dfsg-3
ii  python-pyparsing   2.2.0+dfsg1-2

python-catkin-pkg recommends no packages.

python-catkin-pkg suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: ros-catkin-pkg
Source-Version: 0.4.3-2

We believe that the bug you reported is fixed in the latest version of
ros-catkin-pkg, 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.
Jochen Sprickerhof  (supplier of updated ros-catkin-pkg 
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: Wed, 06 Jun 2018 13:59:45 +0200
Source: ros-catkin-pkg
Binary: python-catkin-pkg python3-catkin-pkg
Architecture: source
Version: 0.4.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jochen Sprickerhof 
Description:
 python-catkin-pkg - Low-level build system macros for Robot OS -- Python 2 
module
 python3-catkin-pkg - Low-level build system macros for Robot OS -- Python 3 
module
Closes: 900637
Changes:
 ros-catkin-pkg (0.4.3-2) unstable; urgency=medium
 .
   * Add breaks due to move of /usr/bin/catkin_package_version (Closes: #900637)
Checksums-Sha1:
 b885f35f5bccd9726c71be1d4fd38a4f63ac2196 2454 ros-catkin-pkg_0.4.3-2.dsc
 9ec9b02eed9ff65e28caf02f2307cdaba5da9075 5148 
ros-catkin-pkg_0.4.3-2.debian.tar.xz
 e25b81619cd7aac6407ce42a10f2410b2e37bf37 7156 
ros-catkin-pkg_0.4.3-2_source.buildinfo
Checksums-Sha256:
 c1d0085547165997e5a19ba47949fb8647e628de405a3148643bf5ede35e14d1 2454 
ros-catkin-pkg_0.4.3-2.dsc
 2ed873ea38a5c9be3e13da73c5be6e21e34e3fc509adf107ffd96474bc095423 5148 
ros-catkin-pkg_0.4.3-2.debian.tar.xz
 f5b51910b9923d6172643ac378e548e67720126c68d3f2381fe15835122f6e36 7156 
ros-catkin-pkg_0.4.3-2_source.buildinfo
Files:
 0634b3a98dd06e5c7d100999a6b1962c 2454 python optional 
ros-catkin-pkg_0.4.3-2.dsc
 751d3ba8d841e6ba70e23de732aebe27 5148 python optional 
ros-catkin-pkg_0.4.3-2.debian.tar.xz
 

Bug#900855: [qtquickcontrols2-opensource-src] FTBFS font fontenello

[Lisandro Damián Nicanor Pérez Meyer]

Hi Bastien!

El mar., 5 de jun. de 2018 19:12, Bastien ROUCARIÈS <
roucaries.bast...@gmail.com> escribió:

> Package: qtquickcontrols2-opensource-src
> Severity: serious
>
> Hi,
> examples/quickcontrols2/swipetoremove/fonts/fontello.ttf
>
> fail to build from source
>
> In your case I suppose they are no need to wait that I upload the package.
>
> A repack will be quicker
>

Sorry, but I can't make sense of what you wrote.

>

Bug#900618: Closing bug (Was: Broken versioned Depends on quantmod)

[Dirk Eddelbuettel]

On 6 June 2018 at 14:24, Graham Inggs wrote:
| On 06/06/2018 13:35, Dirk Eddelbuettel wrote:
| > Sounds good. The weirder issue that I _had_ in fact fixed that with
| > debian/patches file to alter the upstream DESCRIPTION. So I was mostly
| > perplexed that that seem to have been in vain.  Anyway, good now and Kurt
| > Hornik fixed it upstream.
| 
| It looks to me as if tseries 0.10-44-2 was never uploaded, so mystery 
| solved!

Yes -- it was waiting on quantmod which was not built yet.

Too many parallel threads...

Dirk

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#900618: Closing bug (Was: Broken versioned Depends on quantmod)

[Graham Inggs]

On 06/06/2018 13:35, Dirk Eddelbuettel wrote:

Sounds good. The weirder issue that I _had_ in fact fixed that with
debian/patches file to alter the upstream DESCRIPTION. So I was mostly
perplexed that that seem to have been in vain.  Anyway, good now and Kurt
Hornik fixed it upstream.


It looks to me as if tseries 0.10-44-2 was never uploaded, so mystery 
solved!

Bug#900750: thunderbird: Launching Thunderbird completely locks my Xwindow session

[G. L. Gragnani]

Removing AppArmor solves the problem.
Thank you.
Gigi.



On 06/05/18 20:25, Carsten Schoenert wrote:

Hi,

On Mon, Jun 04, 2018 at 10:41:04AM +0200, g.gragnani wrote:

f I launch thunderbird the whole xsession (XFCE) locks.
I'm only able to move the mouse arrow (without any effect)
and switching to a character console by using Cttrl-Alt-F1 etc.
Killing thhunderbird does not solve the problem.

The same happens in an other machine, with a different set of installed
packages, different hardware and running LXDE.

you have apparmor installed and it's likely it may causing issues.
Can you check the behaviour with a deactivated AppArmor profile and also
a removed AppAprmor package?


Versions of packages thunderbird suggests:
ii  apparmor  2.12-4

Other possible candidates are sometime the kernel. But without a small
set of logs it's quite impossible to track down the root of the issue.

Regards
Carsten



--
Gian Luigi Gragnani
Diten - University of Genoa
Via Opera Pia 11A, 16145 Genova, Italy
phone: + 39 010 353 2244

Bug#900618: marked as done (tseries: unsatisfiable versioned dependency on quantmod (>= 0.4.9))

[Debian Bug Tracking System]

Your message dated Wed, 6 Jun 2018 13:27:05 +0200
with message-id <20180606112705.mtxj42da2ywlp...@an3as.eu>
and subject line Closing bug (Was: Broken versioned Depends on quantmod)
has caused the Debian Bug report #900618,
regarding tseries: unsatisfiable versioned dependency on quantmod (>= 0.4.9)
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.)


-- 
900618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900618
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tseries
Version: 0.10-44-1
Severity: serious
Tags: patch
X-Debbugs-CC: r-pkg-t...@alioth-lists.debian.net

Hi Dirk

Due to some new magic in dh-r, r-cran-tseries gains a versioned
dependency on quantmod (>= 0.4.9), but we have 0.4-13-1 in the archive
and this makes r-cran-tseries not installable.

My guess is this was a typo upstream, and they meant 0.4-9 instead of 0.4.9.

Please consider including my patch, attached.

Regards
Graham
Description: Fix unsatisfiable versioned dependency on quantmod
Author: Graham Inggs 
Last-Update: 2018-06-02

--- a/DESCRIPTION
+++ b/DESCRIPTION
@@ -9,7 +9,7 @@
 comment = "BDS test code"))
 Description: Time series analysis and computational finance.
 Depends: R (>= 2.10.0)
-Imports: graphics, stats, utils, quadprog, zoo, quantmod (>= 0.4.9)
+Imports: graphics, stats, utils, quadprog, zoo, quantmod (>= 0.4-9)
 License: GPL-2
 NeedsCompilation: yes
 Packaged: 2018-04-15 15:14:39 UTC; hornik
--- End Message ---
--- Begin Message ---
On Wed, Jun 06, 2018 at 05:17:22AM -0500, Dirk Eddelbuettel wrote:
> 
> Yes, which upstream fixed (after I had set the bug to "forwarded") but I
> haven't gotten there yet.
> 
> So that was clearly planned and lined up, hence no need really for three
> emails in the space of a few minutes effectively before my day even started.

Sorry, I plainly assumed that the issue was just caused by my NMU and I
usually try to fix problems I caused as quickly as possible.  Closing
the according bug with this mail.
 
> Dirk, about to go for a run

Hope you had fun

   Andreas.

-- 
http://fam-tille.de--- End Message ---

Bug#900879: [Pkg-freeipa-devel] Bug#900879: bind9-dyndb-ldap: does not work with current bind9 anymore

[Timo Aaltonen]

On 06.06.2018 13:13, Dominik George wrote:
> On Wed, Jun 06, 2018 at 11:54:04AM +0200, Dominik George wrote:
>> This plugin only works with the old dyndb patch for BIND, but not with
>> the DynDB interface in the version now included in BIND upstream.
> 
> Seems that is not the case, but the plugin needs to be rebuilt against BIND
> 9.11.3, which seems not to work right now: 
> https://pagure.io/bind-dyndb-ldap/issue/176

If you had a look at the changelog, it would show that there was an
upload to fix the build against 9.11.3.. so it's pretty clear that the
plugin was built against it.

What's your issue? The upstream link says nothing.

-- 
t

Bug#900882: susv4: fails to install: ERROR 404: Not Found.

[Jakub Wilk]

Package: susv4
Version: 7.20161013
Severity: grave

# apt-get install -q susv4
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
  susv4 (7.20161013)
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/3278 B of archives.
After this operation, 15.4 kB of additional disk space will be used.
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package susv4.
(Reading database ... 11900 files and directories currently installed.)
Preparing to unpack .../susv4_7.20161013_all.deb ...
Unpacking susv4 (7.20161013) ...
Setting up susv4 (7.20161013) ...
Fetching file...
--2018-06-06 10:24:50--  
http://pubs.opengroup.org/onlinepubs/9699919799/download/susv4tc2.tar.bz2
Resolving pubs.opengroup.org (pubs.opengroup.org)... 69.80.200.148
Connecting to pubs.opengroup.org (pubs.opengroup.org)|69.80.200.148|:80... 
connected.
HTTP request sent, awaiting response... 404 Not Found
2018-06-06 10:24:52 ERROR 404: Not Found.

dpkg: error processing package susv4 (--configure):
installed susv4 package post-installation script subprocess returned error exit 
status 8
Errors were encountered while processing:
susv4
E: Sub-process /usr/bin/dpkg returned an error code (1)


--
Jakub Wilk

Bug#891957: marked as done (netbeans no starting "loading module" modules.netbinox NullPointerException)

[Debian Bug Tracking System]

Your message dated Wed, 06 Jun 2018 10:22:24 +
with message-id 
and subject line Bug#891957: fixed in netbeans 8.1+dfsg3-5
has caused the Debian Bug report #891957,
regarding netbeans no starting "loading module" modules.netbinox 
NullPointerException
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.)


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

Package: netbeans
Version: 8.1+dfsg3-4
Severity: critical
Justification: breaks unrelated software
Tags: a11y

Dear Maintainer,

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


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

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


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

Kernel: Linux 4.15.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=es_NI.UTF-8, LC_CTYPE=es_NI.UTF-8 (charmap=UTF-8), 
LANGUAGE=es_NI:es (charmap=UTF-8)

Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages netbeans depends on:
ii  default-jdk [java8-sdk]    2:1.8-59
ii  libnb-apisupport3-java 8.1+dfsg3-4
ii  libnb-ide14-java   8.1+dfsg3-4
ii  libnb-java5-java   8.1+dfsg3-4
ii  libnb-platform18-java  8.1+dfsg1-7
ii  openjdk-8-jdk [java8-sdk]  8u151-b12-1

netbeans recommends no packages.

netbeans suggests no packages.

-- no debconf information

>Log Session: Friday, March 2, 2018 10:19:51 PM CST
>System Info:
  Product Version = NetBeans IDE 8.1 (Build 20180221-debian-8.1)
  Operating System    = Linux version 4.15.0-1-amd64 running on amd64
  Java; VM; Vendor    = 1.8.0_151; OpenJDK 64-Bit Server VM 
25.151-b12; Oracle Corporation
  Runtime = OpenJDK Runtime Environment 
1.8.0_151-8u151-b12-1-b12

  Java Home   = /usr/lib/jvm/java-8-openjdk-amd64/jre
  System Locale; Encoding = es_NI (nb); UTF-8
  Home Directory  = /home/gacs
  Current Directory   = /home/gacs
  User Directory  = /home/gacs/.netbeans/8.1
  Cache Directory = /home/gacs/.cache/netbeans/8.1
  Installation    = /usr/share/netbeans/8.1/nb
    /usr/share/netbeans/8.1/ide
    /usr/share/netbeans/8.1/java
    /usr/share/netbeans/8.1/apisupport
    /usr/share/netbeans/8.1/harness
    /usr/share/netbeans/8.1/platform
  Boot & Ext. Classpath   = 
/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/resources.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/rt.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/sunrsasign.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/jsse.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/jce.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/charsets.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/jfr.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/classes:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/ext/localedata.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/ext/nashorn.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/ext/sunjce_provider.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/ext/cldrdata.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/ext/zipfs.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/ext/dnsns.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/ext/sunpkcs11.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/ext/icedtea-sound.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/ext/sunec.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/ext/jaccess.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/ext/java-atk-wrapper.jar
  Application Classpath   = 
/usr/share/java/jcodings.jar:/usr/share/netbeans/8.1/platform/lib/boot.jar:/usr/share/netbeans/8.1/platform/lib/org-openide-modules.jar:/usr/share/netbeans/8.1/platform/lib/org-openide-util.jar:/usr/share/netbeans/8.1/platform/lib/org-openide-util-lookup.jar:/usr/share/netbeans/8.1/platform/lib/org-openide-util-ui.jar:/usr/lib/jvm/java-8-openjdk-amd64/lib/dt.jar:/usr/lib/jvm/java-8-openjdk-amd64/lib/tools.jar
  Startup Classpath   = 

Bug#900879: bind9-dyndb-ldap: does not work with current bind9 anymore

[Dominik George]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Wed, Jun 06, 2018 at 11:54:04AM +0200, Dominik George wrote:
> This plugin only works with the old dyndb patch for BIND, but not with
> the DynDB interface in the version now included in BIND upstream.

Seems that is not the case, but the plugin needs to be rebuilt against BIND
9.11.3, which seems not to work right now: 
https://pagure.io/bind-dyndb-ldap/issue/176

- -nik
-BEGIN PGP SIGNATURE-

iQJlBAEBCABPFiEEPJ1UpHV1wCb7F/0mt5o8FqDE8pYFAlsXs7UxGmh0dHBzOi8v
d3d3LmRvbWluaWstZ2VvcmdlLmRlL2dwZy1wb2xpY3kudHh0LmFzYwAKCRC3mjwW
oMTyljzPD/49i+nyVE7DNFWyM/BRiMW4J7ZWUduUqLcoA9BUY9M0VLjQHjaWfdNk
k9l277SrwVaGHgpgOKau8StmsZOkEnhJW0MV6b4TUIiykglM6+4vjWukS+MK7Pxj
ErpBdwVpE30YL0/MVm+JnmUnbHgdX6qr7KPNU439bHNujBnHjW8o3Pj7aAKuYjFl
vq5I09awmcfPX+jt+NzAkkp6DGp+t0BFP+OYcdqHwBzLhL/XWeNzQnvu88OvwJwa
q2cgovXoiSgO6XmnuXZCMfJPVUE6YNULbljczCahtOHToFruqEE71J+z5we/cdfl
c6vwFHc7C7WupHSnZc9nbP3kGLinB2qZRoVdrxvSV23Y8/mKNHdG3e4y6k0SAUXP
aTP5xiudT7DWsL6dWVSDcpOZqBtv5CgT8eFkIYr64CbSECXZfHS1pZowK+SygQFH
SVy3pIJpWRyYd2fxJKfwYDF6vMgKae3UG+4zZftxhfld4n0ugr9CV/kZkH+i2c7r
jNmSZhjfWEIlL0/S9TceH9yCfKQWdPDRSKoStqAjTA8ZGvDd8B2E/u4RaylrDfZx
OsQtPjkUkuHR+onKJm+G3jsinD9HFRWcRT4JlbfykZBJQLya9NVxstSF6/rse53+
wj+4qrXgVVPpDGyZ82zKADN0AYgzV0NunWNXlc6WZde45+r8iz70oQ==
=jhea
-END PGP SIGNATURE-

Processed: submitter 900879

[Debian Bug Tracking System]

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

> submitter 900879 naturesha...@debian.org
Bug #900879 [bind9-dyndb-ldap] bind9-dyndb-ldap: does not work with current 
bind9 anymore
Changed Bug submitter to 'naturesha...@debian.org' from 'Dominik George 
'.
> thanks
Stopping processing here.

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

Bug#898940: marked as done (lastpass-cli: error: Peer certificate cannot be authenticated with given CA certificates)

[Debian Bug Tracking System]

Your message dated Wed, 06 Jun 2018 10:07:39 +
with message-id 
and subject line Bug#898940: fixed in lastpass-cli 1.3.1-1
has caused the Debian Bug report #898940,
regarding lastpass-cli: error: Peer certificate cannot be authenticated with 
given CA certificates
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.)


-- 
898940: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898940
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lastpass-cli
Version: 1.0.0-1.2
Severity: serious

Hi,

As of today, lpass is no longer working for me:

  $ lpass login f...@bar.com
  Error: Peer certificate cannot be authenticated with given CA certificates.

FYI the CHANGELOG.md mentions:

 # Version 0.8.1, 0.7.2, 0.6.1, 0.5.1
 * This update to all recent versions switches to the platform certificate
   store and adds pinning of LastPass public keys, in preparation for
   certificate changes at lastpass.com. Upgrade will be needed to avoid 
"Peer
   certificate cannot be authenticated with given CA certificates" errors
   when the cert changes are made.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: lastpass-cli
Source-Version: 1.3.1-1

We believe that the bug you reported is fixed in the latest version of
lastpass-cli, 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 898...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated lastpass-cli 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, 06 Jun 2018 10:31:22 +0100
Source: lastpass-cli
Binary: lastpass-cli
Architecture: source amd64
Version: 1.3.1-1
Distribution: unstable
Urgency: medium
Maintainer: Chris Lamb 
Changed-By: Chris Lamb 
Description:
 lastpass-cli - command line interface to LastPass.com
Closes: 842875 858991 898940
Changes:
 lastpass-cli (1.3.1-1) unstable; urgency=medium
 .
   * New upstream release. (Closes: #898940)
 - Use libssl-dev over libssl1.0-dev. (Closes: #858991)
 - Make the build reproducible. (Closes: #842875)
 - Add missing cmake and bash-completion to Build-Depends.
   * Take over maintenance of package - see 
 for blessing. Thanks to Troy Heber for his previous work on this package.
   * debian/rules:
 - Ensure full hardening even though we are using CMake by setting CFLAGS
   and CXXFLAGS from CPPFLAGS.
 - Install zsh completion script.
   * debian/control:
 - Drop Build-Depends on quilt; we are a 'quilt (3.0)' source format 
package.
 - Add Suggests: on xclip | xsel.
 - Add Recommends on pinentry-curses.
 - Add Vcs-{Git,Browser} & Homepage headers.
 - Bump Standards-Version to 4.1.4.
   * debian/patches:
 - Drop 0001-cipher-support-opaque-EVP_CIPHER_CTX,
   0002-cipher-drop-p8inf-broken-flag-check &
   0003-pbkdf2-support-openssl-1.1; applied upstream.
 - Replace 0004-build_manpage with an override in debian/rules to
   build lpass.1 manual page and fix location in debian/manpages.
   * Upstream are not providing signed tarballs so override the
 lintian warning debian-watch-does-not-check-gpg-signature.
   * Add some autopkgtest smoke tests.
   * Add a debian/watch file.
   * Bump to debhelper compatibility level 11.
   * Tidy debian/rules, drop empty debian/install file, apply "wrap-and-sort",
 drop whitespace from debian/changelog, re-order fields, drop trailing comma
 on DEB_BUILD_MAINT_OPTIONS line.
Checksums-Sha1:
 b20ee7b592addd72bb1c2ec40de9cf1a5578f224 2011 lastpass-cli_1.3.1-1.dsc
 0dfbecd1ac2a36af7cc24d714a0f3deb23a6e20f 114843 lastpass-cli_1.3.1.orig.tar.gz
 b76bd352742f10e40185c340c2394265e09f49e2 4788 
lastpass-cli_1.3.1-1.debian.tar.xz
 328d7343cfe69e8af531c172590990204c20c048 214420 
lastpass-cli-dbgsym_1.3.1-1_amd64.deb
 e9950dfc3f44a5a9bebf12b22b53bc0d97f5dfd7 8246 
lastpass-cli_1.3.1-1_amd64.buildinfo
 ee21a91c680b5071a4464358c9389686c5ce0d59 88792 lastpass-cli_1.3.1-1_amd64.deb
Checksums-Sha256:
 

Bug#858991: marked as done (lastpass-cli: Please migrate to openssl1.1 in buster)

[Debian Bug Tracking System]

Your message dated Wed, 06 Jun 2018 10:07:39 +
with message-id 
and subject line Bug#858991: fixed in lastpass-cli 1.3.1-1
has caused the Debian Bug report #858991,
regarding lastpass-cli: Please migrate to openssl1.1 in buster
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.)


-- 
858991: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858991
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lastpass-cli
Version: 1.0.0-1.1
Severity: grave
Tags: sid stretch

Hi,

Please use ssl1.0 for stretch.

We have requested the curl also reverts to ssl1.0 (please see
#850880). Since libapache2-mod-auth-cas is using a curl function exposing
SSL_CTX, it will have to use the same version libssl as curl itself.

Thanks,
~Niels
--- End Message ---
--- Begin Message ---
Source: lastpass-cli
Source-Version: 1.3.1-1

We believe that the bug you reported is fixed in the latest version of
lastpass-cli, 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 858...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated lastpass-cli 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, 06 Jun 2018 10:31:22 +0100
Source: lastpass-cli
Binary: lastpass-cli
Architecture: source amd64
Version: 1.3.1-1
Distribution: unstable
Urgency: medium
Maintainer: Chris Lamb 
Changed-By: Chris Lamb 
Description:
 lastpass-cli - command line interface to LastPass.com
Closes: 842875 858991 898940
Changes:
 lastpass-cli (1.3.1-1) unstable; urgency=medium
 .
   * New upstream release. (Closes: #898940)
 - Use libssl-dev over libssl1.0-dev. (Closes: #858991)
 - Make the build reproducible. (Closes: #842875)
 - Add missing cmake and bash-completion to Build-Depends.
   * Take over maintenance of package - see 
 for blessing. Thanks to Troy Heber for his previous work on this package.
   * debian/rules:
 - Ensure full hardening even though we are using CMake by setting CFLAGS
   and CXXFLAGS from CPPFLAGS.
 - Install zsh completion script.
   * debian/control:
 - Drop Build-Depends on quilt; we are a 'quilt (3.0)' source format 
package.
 - Add Suggests: on xclip | xsel.
 - Add Recommends on pinentry-curses.
 - Add Vcs-{Git,Browser} & Homepage headers.
 - Bump Standards-Version to 4.1.4.
   * debian/patches:
 - Drop 0001-cipher-support-opaque-EVP_CIPHER_CTX,
   0002-cipher-drop-p8inf-broken-flag-check &
   0003-pbkdf2-support-openssl-1.1; applied upstream.
 - Replace 0004-build_manpage with an override in debian/rules to
   build lpass.1 manual page and fix location in debian/manpages.
   * Upstream are not providing signed tarballs so override the
 lintian warning debian-watch-does-not-check-gpg-signature.
   * Add some autopkgtest smoke tests.
   * Add a debian/watch file.
   * Bump to debhelper compatibility level 11.
   * Tidy debian/rules, drop empty debian/install file, apply "wrap-and-sort",
 drop whitespace from debian/changelog, re-order fields, drop trailing comma
 on DEB_BUILD_MAINT_OPTIONS line.
Checksums-Sha1:
 b20ee7b592addd72bb1c2ec40de9cf1a5578f224 2011 lastpass-cli_1.3.1-1.dsc
 0dfbecd1ac2a36af7cc24d714a0f3deb23a6e20f 114843 lastpass-cli_1.3.1.orig.tar.gz
 b76bd352742f10e40185c340c2394265e09f49e2 4788 
lastpass-cli_1.3.1-1.debian.tar.xz
 328d7343cfe69e8af531c172590990204c20c048 214420 
lastpass-cli-dbgsym_1.3.1-1_amd64.deb
 e9950dfc3f44a5a9bebf12b22b53bc0d97f5dfd7 8246 
lastpass-cli_1.3.1-1_amd64.buildinfo
 ee21a91c680b5071a4464358c9389686c5ce0d59 88792 lastpass-cli_1.3.1-1_amd64.deb
Checksums-Sha256:
 1a42b4513bce4146cf35f7db987ea6900bf9fb0223ece829b9e54d7ad0001cf9 2011 
lastpass-cli_1.3.1-1.dsc
 25dc9a0c99a10ee70b5b3991d525448c25f312cc69fa0216d7ac70c4ae384b1b 114843 
lastpass-cli_1.3.1.orig.tar.gz
 f1afd0906566f0d00b690df65053b98421cc1537f6ae2661e4c60b1a780a817e 4788 
lastpass-cli_1.3.1-1.debian.tar.xz
 2ea273b6b0b387500e3842f4f25d39c26fcfcc1bef63b0a6e856b0291b404ffa 214420 
lastpass-cli-dbgsym_1.3.1-1_amd64.deb
 343afeb440fb6b9b5fec2a828fdb543fb982aff1a224d919c0c2b6900dd9a474 8246 

Bug#900879: bind9-dyndb-ldap: does not work with current bind9 anymore

[Dominik George]

Package: bind9-dyndb-ldap
Version: 11.1-3
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

This plugin only works with the old dyndb patch for BIND, but not with
the DynDB interface in the version now included in BIND upstream.

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

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

Versions of packages bind9-dyndb-ldap depends on:
ii  bind9  1:9.11.3+dfsg-1
ii  libc6  2.27-3
ii  libdns1100 1:9.11.3+dfsg-1
ii  libisc169  1:9.11.3+dfsg-1
ii  libkrb5-3  1.16-2
ii  libldap-2.4-2  2.4.46+dfsg-5
ii  libuuid1   2.32-0.1

bind9-dyndb-ldap recommends no packages.

bind9-dyndb-ldap suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQJ4BAEBCABiFiEEPJ1UpHV1wCb7F/0mt5o8FqDE8pYFAlsXrzQxGmh0dHBzOi8v
d3d3LmRvbWluaWstZ2VvcmdlLmRlL2dwZy1wb2xpY3kudHh0LmFzYxIcbmlrQG5h
dHVyYWxuZXQuZGUACgkQt5o8FqDE8pYSQRAA2BHdTJjrzalbFRsedVhMjBqAGYJc
TstiWl+x7MYZideTiy6FbvgazBTu/DJFioAmcn4jxo+4QV2t1HP3QjjhtNtD4h4Z
PZMVs7sfEUUP3dble0njZZUilhKShD82caWozcI1sfgxHelzZvaYRXfSUULuce41
PkayYQAwJrYr84rSPTdN2POYBP3dOj4oz7tZ1N9vVbelLWCdWYkXEWqWR572FUSX
TdgTvtIJ6gC8wXt1xJJaQ0NTh09X7wouk6oUJldh7ey1JA18lLC5MWqjar5FDPVR
UANFF8y68PCRj9WxyzyKHLmZPRnOrYgV4aMhUEstqAwQwwCPXFVMPRx/2nb8Er7l
ikKMMDvVbDWDdEt61sOksGb7QGUc25o8utKxzFlaFgdNbIZFTWBNRTwhDhfYaW/m
ccyS0CoIzULpqe8pcMewTQL4S4J8HnN1mx/QTgcVT8Z4c6c0rMn/ks/og4/DDzdq
ULKEwYxuwsQrCq5OSJso/OTGwORwTmhCXV4B/E6+KWhzjVRefkZNAXeCCQqEZOMA
oKECg1tHYM/2JSHN9a8/orLHIo457VlLOM6Wk6C6vkEBS33CqnT+FG+kG53pEWR/
3rnjfj0mvlgrsaGnvUPUAYbTCehF1DvCMjlsnRYQVN/Se7MzNAlPRbgy65fR13Fy
M5enAIfrwZCPJcs=
=iGc4
-END PGP SIGNATURE-

Bug#900399: It's confirmed: memtest86+ can kill lenovo mainboard

[Сергей Коган]

Hi!

Good news and a bad news. Both T500 laptops were examined. One was 
(almost) repaired. One is dead.


One-line summary:  Yes, memtest86+ killed them. No, it is not related to 
the embedded controller. It's a short-circuit in a power hub IC.


Details:

- It's important to note that power management logic in lenovo thinkpad 
laptops is quite sophisticated. The embedded controller provides a 
high-level signal, while special IC's issue signals to various gates to 
power up or power down specific parts of the system.


- One of those low-level IC's is a RIKNAN (U61 on lenovo schematics). 
The important part of the IC is the VCC3SW micro-power LDO (dc/dc 
converter). It provides a limited 3.3v power supply for the power button 
detection circuit, thermal protection logic and a power hub IC.


- The power hub PMH_7 (U28) is more intelligent then RINKAN, and has a 
SPI connection to the EC. It controls a lot of clocks and power signals 
on a main board. Note that PMH is used across different lenovo products, 
so some of it's outputs are left unused. It is a common practice to tie 
unused IC outputs to ground or VCC instead of leaving them unconnected.


- Coreboot developers discovered a method of accessing the internal 
registers of the PMH. The protocol is simple: write a register address 
to some memory-mapped EC address, then write desired value to the other 
EC address.


    outb(reg, EC_LENOVO_PMH7_ADDR);
    val = inb(EC_LENOVO_PMH7_DATA);
    outb(reg, EC_LENOVO_PMH7_ADDR);
    outb(val | (1 << bit), EC_LENOVO_PMH7_DATA);

- Now we are leaving the hard facts ground and start speculating.

- It seems be the case than either BIOS do not list memory-mapped EC 
registers as a reserved memory area, or memtest86+ fails to process this 
reservation correctly.


- The pattern of the memory writes by memtest is (unfortunately) 100% 
compatible with PMH internal register access protocol.


- It is very possible that by writing some moving ones and zeros or a 
random bytes, the memtest has pulled an unused (tied to ground or VCC) 
PMH pin high or low - thereby creating a short-circuit on VCC3SW line.


- This short-circuit would tend to overheat the RINKAN LDO as it's 
output transistor is in active mode, and is easily overloaded with a PMH 
output transistor (which is in conduction mode with a resistance of 
milli-ohms). It seems that RINKAN has no over-current or thermal 
protection built in.


- VCC3SW malfunction is not critical while the main board 3.3V/9А and 
5V/8A buses are powered by TPS51221 (U41) IC. Most components draw power 
from main buses and not from VCC3SW. But when the laptop is powered off, 
there is no VCC3SW bus to initiate the power-on process. The laptop is 
bricked.


Findings:

Both laptops were disassembled and main boards examined using a 
multi-meter and an oscilloscope. The main boards were of a different 
revisions (and different types: one with discrete graphics, one without) 
but both has the VCC3SW power bus malfunctioned. The first laptop 
provided around 1.2v over the VCC3SW and a measured resistance from 
VCC3SW to GND was around 400 Ohm. After cutting the VCC3SW pin on RINKAN 
IC and providing an external power to the VCC3SW line - the laptop 
powered up and attempted to boot. We ended up wiring up an external 
micro-power LDO (LP2930-3.3) to provide the power permanently. This 
laptop still has some minor problems (like refusing to power-up unless 
the battery is removed and AC-IN is plugged-in), but is still usable.


The second T500 RINKAN was not providing any power to the VCC3SW bus, 
and measured resistance was only ~50 Ohms. We had to cut both VCC3SW 
(output) and VREGIN20 (input) RINKAN pins to remove an over-current 
condition. After that we observed the power on main 3.3V and 5V buses, 
but RINKAN/PMH7 do not issue 'POWER GOOD' signals and prevent the system 
to become usable. No repair is possible.


It looks like T6x, T400/500, T410/510, T420/520 laptop families could be 
affected by this problem. Starting from the T430/530 series, a 
communication protocol with the EC was changed - breaking tp_smapi 
driver and fixing the described problem as a side effect.


I have a "revived" T500 on hands and I would be happy to provide any 
information to confirm or correct my findings.


I still think that it's appropriate to warn lenovo users of a 
possibility to brick their laptops with just a mere memory test.


---
Sincerely yours,
Sergey Kogan

Bug#899688: Bug#899851: schroot: Invalid maintainer address buildd-tools-de...@lists.alioth.debian.org

[Raphael Hertzog]

Hi Simon,

On Wed, 06 Jun 2018, Simon McVittie wrote:
> Since nobody seems to have objected to this and I found myself wanting to
> refer to up-to-date schroot/sbuild source code today, I've imported both
> projects into Salsa using `git push --mirror` from the archives in
> . They are now at
>  and
> . Please move or delete those
> repositories if they are not what you wanted.

Thanks for doing this. I enabled the integration with the package tracker
and the tagpending hook. 

> The RC bug regarding the Maintainer address remains open.

I just orphaned schroot to fix the maintainer email.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/

Bug#899205: marked as done (python-cogent: Test suite fails with latest matplotlib)

[Debian Bug Tracking System]

Your message dated Wed, 06 Jun 2018 09:39:40 +
with message-id 
and subject line Bug#899205: fixed in python-cogent 1.9-12
has caused the Debian Bug report #899205,
regarding python-cogent: Test suite fails with latest matplotlib
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.)


-- 
899205: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899205
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-cogent
Severity: serious
Justification: FTBFS
User: debian...@lists.debian.org

The package fails to build with latest matplotlib which became
obvious in the CI report[1].  It fails as well when building the
package.

The issue is reported upstream.[2]

Kind regards,

  Andreas.

[1] https://ci.debian.net/packages/p/python-cogent/testing/amd64/
[2] https://github.com/pycogent/pycogent/issues/112


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

Kernel: Linux 4.9.0-5-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)

Versions of packages python-cogent depends on:
ii  libc6  2.24-11+deb9u1
ii  python 2.7.13-2
pn  python-matplotlib  
pn  python-numpy   
pn  python-numpy-abi9  

Versions of packages python-cogent recommends:
pn  blast2
pn  bwa   
pn  cd-hit
pn  clearcut  
pn  dialign   
pn  muscle

Versions of packages python-cogent suggests:
pn  cdbfasta   
pn  clustalw   
pn  fasttree   
pn  infernal   
pn  mafft  
pn  mothur 
pn  parsinsert 
pn  python-cogent-doc  
pn  raxml  
pn  rdp-classifier 
pn  rtax   
--- End Message ---
--- Begin Message ---
Source: python-cogent
Source-Version: 1.9-12

We believe that the bug you reported is fixed in the latest version of
python-cogent, 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 899...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated python-cogent 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, 06 Jun 2018 11:10:01 +0200
Source: python-cogent
Binary: python-cogent python-cogent-doc
Architecture: source
Version: 1.9-12
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 python-cogent - framework for genomic biology
 python-cogent-doc - docs for python-cogent
Closes: 898334 899205
Changes:
 python-cogent (1.9-12) unstable; urgency=medium
 .
   * Add registry data
   * Testsuite: autopkgtest-pkg-python
   * honor "nocheck" in DEB_BUILD_OPTIONS
 Closes: #898334
   * debhelper 11
   * Point Vcs fields to salsa.debian.org
   * Standards-Version: 4.1.4
   * Fix suite fails with latest matplotlib
 Closes: #899205
   * Fix privacy issue in doc
   * Drop obsolete file debian/pyversions
   * Drop unneeded get-orig-source target
   * Do not parse d/changelog
   * Rename debian/tests/control to debian/tests/control.autodep8
   * Remove useless doctree files
Checksums-Sha1:
 effa4a96f1684f9a08627a991eafed2f87ed10cf 2456 python-cogent_1.9-12.dsc
 1664bd02c44083c2b3f434693aa83e23c501b20a 19744 
python-cogent_1.9-12.debian.tar.xz
Checksums-Sha256:
 7cb4a824f64b764165b99f81cb3b0d15438159fdf585b87bcd4c41249a7a5639 2456 
python-cogent_1.9-12.dsc
 433d4795567af0ab4262310784e4a9c23daabd2cd891a3ea5965c440abc3f2ef 19744 
python-cogent_1.9-12.debian.tar.xz
Files:
 a84028e54df837fe3c0274f3e2604004 2456 python optional python-cogent_1.9-12.dsc
 c313ec5eed64fa0a47ef3bc8e1b4b17b 19744 python optional 
python-cogent_1.9-12.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlsXptMRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtFg3Q/+N7UfDr0Ewg3WMbgyIncTA0/0ibeO9GTO
QiE6DKT5EXw0eA79kWW1BhsumBYXdbq6ex8LqDr/GjJNwS251ZkpEVLd/OVQEDFf
Se0hCLyhWBDrIJrrENSjowai3TtavXuJQAN2Z4kJ6QwWx/jJ6BU3nktw+viae2gn

Bug#899851: Bug #899851 in schroot marked as pending

[hertzog]

Control: tag -1 pending

Hello,

Bug #899851 in schroot 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/debian/schroot/commit/44af53b7b924ebf480421870b7a38d8b8101f792


Orphan packages and update VCS fields

* Orphan packages, this fixes the bouncing maintainer email.
* Update Vcs-* fields to point to salsa. Thanks to Simon McVittie for having
  imported the repositories.

Closes: #899851



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/899851

Processed: Bug #899851 in schroot marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #899851 [src:schroot] schroot: Invalid maintainer address 
buildd-tools-de...@lists.alioth.debian.org
Added tag(s) pending.

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

Bug#899076: marked as done (FTBFS: dh_missing: missing files, aborting)

[Debian Bug Tracking System]

Your message dated Wed, 06 Jun 2018 07:50:36 +
with message-id 
and subject line Bug#899076: fixed in ocaml-migrate-parsetree 1.0.10-1
has caused the Debian Bug report #899076,
regarding FTBFS: dh_missing: missing files, aborting
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.)


-- 
899076: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899076
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ocaml-migrate-parsetree
Version: 1.0.7-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi!
I'm afraid that during an archive rebuild on armhf, your package failed. 
Same happens on amd64:

   debian/rules override_dh_missing
make[1]: Entering directory '/<>'
dh_missing --fail-missing
dh_missing: usr/lib/ocaml/ocaml-migrate-parsetree/ocaml-migrate-parsetree.dune 
exists in debian/tmp but is not installed to anywhere
dh_missing: 
usr/lib/ocaml/ocaml-migrate-parsetree/driver-main/ocaml-migrate-parsetree.driver-main.dune
 exists in debian/tmp but is not installed to anywhere
dh_missing: 
usr/lib/ocaml/ocaml-migrate-parsetree-ocamlbuild/migrate_parsetree_ocamlbuild.ml
 exists in debian/tmp but is not installed to anywhere
dh_missing: 
usr/lib/ocaml/ocaml-migrate-parsetree-ocamlbuild/ocaml-migrate-parsetree-ocamlbuild.dune
 exists in debian/tmp but is not installed to anywhere
dh_missing: missing files, aborting
The following debhelper tools have reported what they installed (with 
files per package)
 * dh_install: libmigrate-parsetree-ocaml (9), 
libmigrate-parsetree-ocaml-dev (130), libmigrate-parsetree-ocaml-doc (0), 
libmigrate-parsetree-ocamlbuild-ocaml (6), 
libmigrate-parsetree-ocamlbuild-ocaml-dev (7)
 * dh_installdocs: libmigrate-parsetree-ocaml (0), 
libmigrate-parsetree-ocaml-dev (0), libmigrate-parsetree-ocaml-doc (0), 
libmigrate-parsetree-ocamlbuild-ocaml (0), 
libmigrate-parsetree-ocamlbuild-ocaml-dev (0)
If the missing files are installed by another tool, please file a bug 
against it.
When filing the report, if the tool is not part of debhelper itself, 
please reference the
"Logging helpers and dh_missing" section from the "PROGRAMMING" guide 
for debhelper (10.6.3+).
  (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz)
Be sure to test with dpkg-buildpackage -A/-B as the results may vary 
when only a subset is built
For a short-term work-around: Add the files to debian/not-installed
make[1]: *** [debian/rules:17: override_dh_missing] Error 2
make[1]: Leaving directory '/<>'


Full log attached.


Meow.
-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 
'experimental')
Architecture: armhf (armv7l)

Kernel: Linux 4.16.5-00026-gc10e6da81c74 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)


ocaml-migrate-parsetree_armhf.build
Description: inode/symlink
--- End Message ---
--- Begin Message ---
Source: ocaml-migrate-parsetree
Source-Version: 1.0.10-1

We believe that the bug you reported is fixed in the latest version of
ocaml-migrate-parsetree, 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 899...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andy Li  (supplier of updated ocaml-migrate-parsetree 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 05 Jun 2018 17:23:11 +0800
Source: ocaml-migrate-parsetree
Binary: libmigrate-parsetree-ocaml libmigrate-parsetree-ocaml-dev 
libmigrate-parsetree-ocamlbuild-ocaml libmigrate-parsetree-ocamlbuild-ocaml-dev 
libmigrate-parsetree-ocaml-doc
Architecture: source
Version: 1.0.10-1
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Andy Li 
Description:
 libmigrate-parsetree-ocaml - Convert OCaml parsetrees between different major 
versions (Runtim
 libmigrate-parsetree-ocaml-dev - Convert OCaml parsetrees between different 
major 

Bug#899688: Bug#899851: schroot: Invalid maintainer address buildd-tools-de...@lists.alioth.debian.org

[Simon McVittie]

On Thu, 24 May 2018 at 10:40:45 +0200, Raphael Hertzog wrote:
> As for git repositories, we should move them to salsa in the "debian"
> group I believe. I don't see the point of a dedicated team at this stage.

Since nobody seems to have objected to this and I found myself wanting to
refer to up-to-date schroot/sbuild source code today, I've imported both
projects into Salsa using `git push --mirror` from the archives in
. They are now at
 and
. Please move or delete those
repositories if they are not what you wanted.

The RC bug regarding the Maintainer address remains open.

smcv

Bug#900759:

[Dylan Aïssi]

tag 900759 pending
thanks

Fixed in git.

Processed: your mail

[Debian Bug Tracking System]

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

> tag 900759 pending
Bug #900759 [gemma] gemma: FTBFS in all architectures
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#895482: Bug#895473: Bug#895482: Fails to upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 4

[Thijs Kinkhorst]

On Wed, May 30, 2018 20:22, Michael Shuler wrote:
> On 05/30/2018 12:46 PM, Sebastian Andrzej Siewior wrote:
>>
>> I've read about this bug (and the other one) on d-devel. I uploaded
>> recently a new version of openssl to unstable (1.1.0h-3)which changes
>> the exit code of "openssl rehash" to zero in case of a duplicate or if a
>> certificate can no be open.
>> I left this bug open in case the maintainer of this package wants to
>> investigate why there are duplicates or non-existing certificates.
>
> Thanks for the update, Sebastian.
>
> OpenSSL commit for my own reference and for others, if interested:
> https://github.com/openssl/openssl/commit/e6a833cb97ed762408b57ea3efa83bd10c1d2a78

Given that this openssl update is now in testing, should we close or at
least downgrade this bug so ca-certificates can migrate?


Cheers,
Thijs

Bug#855942: anki: don't let the alpha version migrate to testing

[Julian Gilbey]

On Tue, Jun 05, 2018 at 04:33:48PM -0400, Alexandre Viau wrote:
> Do we really want to let upstream decide whether or not we should ship Anki?
> 
> The program works. It isn't really security critical so even if it has a
> few bugs it can be useful to our users.

Unfortunately the program doesn't work: Qt 5.10 is apparently
sufficiently buggy in some respect that I don't understand that it
breaks Anki.  So we can't let it migrate until Qt 5.11 is released.
But I do appreciate your general point; at the same time, I don't
particularly want to annoy upstream.

Best wishes,

   Julian

Bug#897516: Question about python-cram/python3-cram Debian/Ubuntu packages

[Andreas Tille]

Hi all,

On Wed, Jun 06, 2018 at 08:23:00AM +0200, László Böszörményi (GCS) wrote:
> Hi Brodie,
> 
> On Sun, Jun 3, 2018 at 10:34 AM Brodie Rao  wrote:
> > I'm the creator of Cram. On a whim, earlier today searched for "cram"
> > in the Ubuntu package repository, and was surprised to find the
> > python-cram and python3-cram packages. I see you're listed as the
> > original maintainer. Would you be able to help make changes to the
> > packages?
>  Please do note that Andreas Tille is the new maintainer, I no longer
> take care of the package.

That's not what the metadata of the package says.  The maintainer is

  Maintainer: Debian Python Modules Team 


(team in CC) and you are listed as

  Uploaders: Laszlo Boszormenyi (GCS) 

As I wrote you before I moved the package to DPMT to give it a wider
audience but I was not hijacking the package from you.  If you do not
plan to care for the package please declare so publicly.

The reason why I was steping in to cram packaging was that due to bug
#897516 [1] with severity serious is affecting three packages of the
Debian Med team (Uploader Afif Elghraoui in CC) and I wanted to make
sure that the packages remain in testing.  I hope that Afif might
volunteer to ad himself to Uploaders in case you will not be able to
work on this package.

> > I'm wondering if Cram can be deprecated or removed as Python 2/3
> > libraries, and instead be listed as a CLI program under the package
> > name "cram"—one that installs into /usr/bin/cram, uses Python 3, and
> > isn't in sys.path and isn't importable. This was my original intention
> > for Cram. Do you know if it'd be possible to make those changes?
>  Sure, this is possible now. The original idea was to have separate
> Cram for Python 2.x and Python 3.y so when someone needs only one
> variant then s/he doesn't need to pull in the other Python module
> variants as dependency.
> Now Python 2.7 is deprecated and python-cram can be dropped while the
> python3- prefix can be removed. Andreas can do it for you. He is
> already looking for you about package maintenance.

I need to discuss this issue with Afif who know the chain of
dependencies better than me.  Adding an additional CLI package using the
python3-cram package would be the cheapest way to cope with your plane
to make cram a command line application.  However, if there is software
out there that is using the python-cram (=Python2) interface we should
probably keep it as long as it is needed.
 
> > Or would it make more sense to have three packages? python-cram,
> > python3-cram, and "cram"?

As I said above I consider this the less invasive method for the moment.

> > With the latter installing into
> > /usr/bin/cram, and the former two making the program available as a
> > library (to preserve backwards compatibility).
>  Sure, dependent packages will need to be updated for the name change
> but there's no need for a metapackage. Of course, Andreas is the one
> to decide, this is only my point of view.

As I tried to express I do not really feel in the position to decide
just since I tried to work on a bug of the package, but I'll do my best
to sort this out and follow the wish of upstream.
 
> > One thing I'm not sure about is how to deal with python-cram currently
> > using /usr/bin/cram. I'd rather Cram not use Python 2 at all if
> > possible (it's ancient and hard to support—I was hoping to remove
> > Python 2 support in the future,

That's perfectly sensible.  Debian is also moving away from Python 2.

> > and maybe even use a different
> > implementation language at some point). Do you know how that issue
> > could be dealt with?
>  Please see above. I agree that Python 2 support needs to be removed.

ACK.  However, we somehow need to care for reverse dependencies and
as long as these are using Python 2 we try to keep this alife.

> > If there's any way you could help, or if you could point me to the
> > right person or in the right direction, I'd very much appreciate it.
>  I've added Andreas to this mail, you can continue with him on future matters.

As said above, the maintainer is

   python-modules-t...@lists.alioth.debian.org

and I'd prefer if Afif would take over the Uploaders role.
 
> > PS: I do appreciate your involvement with the package. I'm sorry if I
> > come across as unthankful of that—I don't mean any disrespect at all.
> > Thanks again for any help you might be able to provide!
>  You are welcome. Debian is a non-profit group of volunteers and we
> help when we are able to.
> Unfortunately the company I work for make it even more harder (now
> almost impossible) to use Linux as such my possibilities are degraded.

Thanks for the clarification.

Kind regards

   Andreas.
 

[1] https://bugs.debian.org/897516

-- 
http://fam-tille.de

Bug#899811: marked as done (litecoin: Invalid maintainer address pkg-bitcoin-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Wed, 06 Jun 2018 06:49:34 +
with message-id 
and subject line Bug#899811: fixed in litecoin 0.16.0-2
has caused the Debian Bug report #899811,
regarding litecoin: Invalid maintainer address 
pkg-bitcoin-de...@lists.alioth.debian.org
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.)


-- 
899811: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899811
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:litecoin
Version: 0.14.2-1
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of litecoin,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package litecoin since the list address
pkg-bitcoin-de...@lists.alioth.debian.org used in the Maintainer: field
was not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-bitcoin-de...@lists.alioth.debian.org is 11.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: litecoin
Source-Version: 0.16.0-2

We believe that the bug you reported is fixed in the latest version of
litecoin, 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 899...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dmitry Smirnov  (supplier of updated litecoin 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, 06 Jun 2018 16:03:05 +1000
Source: litecoin
Binary: litecoind litecoin-qt
Architecture: source amd64
Version: 0.16.0-2
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Smirnov 
Changed-By: Dmitry Smirnov 
Description:
 litecoin-qt - peer-to-peer network based digital currency - Qt GUI
 litecoind  - peer-to-peer network based digital currency - daemon
Closes: 899811
Changes:
 litecoin (0.16.0-2) unstable; urgency=medium
 .
   * set myself as Maintrainer (Closes: #899811).
Checksums-Sha1:
 3ec65792cc2d4ea30098954c6a1b2c6f5e1d2be8 2102 litecoin_0.16.0-2.dsc
 504defd12b156d13fc068b56ab08054c92ac1ca4 14204 litecoin_0.16.0-2.debian.tar.xz
 9a325adb704b2229c6a3d61191e32ff7f144fe40 44748648 
litecoin-qt-dbgsym_0.16.0-2_amd64.deb
 b775db839d3c188b4c24b9c2b46d74d03b400fc4 3952404 litecoin-qt_0.16.0-2_amd64.deb
 d354c06d1a68734f2ec10ebfb5b455809c222c98 18951 
litecoin_0.16.0-2_amd64.buildinfo
 497f54e0515d1218db5038b3d10b3193a8e3534f 31534008 
litecoind-dbgsym_0.16.0-2_amd64.deb
 6d1b96ee6bf8fceda4073a313b070ec7556b0717 1825204 litecoind_0.16.0-2_amd64.deb
Checksums-Sha256:
 7df2c8ba9ad8758857ff4473aea9c993deb0fb653e6ea5020b89bab58de786e8 2102 
litecoin_0.16.0-2.dsc
 d7e772998e0cfe9f424241443c2fd90e62eba0d061aab5ebf6170c7201bb8c13 14204 

Bug#900750: thunderbird: Launching Thunderbird completely locks my Xwindow session

[Jan Hovancik]

I'm having the same issue here.

Disabling apparmor profile (permanently) as described here 
(http://ask.xmodulo.com/disable-particular-apparmor-profile-ubuntu.html) 
helped.


On Tue, 5 Jun 2018 20:25:21 +0200 Carsten Schoenert 
 wrote:

> Hi,
>
> On Mon, Jun 04, 2018 at 10:41:04AM +0200, g.gragnani wrote:
> > f I launch thunderbird the whole xsession (XFCE) locks.
> > I'm only able to move the mouse arrow (without any effect)
> > and switching to a character console by using Cttrl-Alt-F1 etc.
> > Killing thhunderbird does not solve the problem.
> >
> > The same happens in an other machine, with a different set of installed
> > packages, different hardware and running LXDE.
>
> you have apparmor installed and it's likely it may causing issues.
> Can you check the behaviour with a deactivated AppArmor profile and also
> a removed AppAprmor package?
>
> > Versions of packages thunderbird suggests:
> > ii apparmor 2.12-4
>
> Other possible candidates are sometime the kernel. But without a small
> set of logs it's quite impossible to track down the root of the issue.
>
> Regards
> Carsten
>
>

Bug#900868: node-growl: CVE-2017-16042: Does not properly sanitize input before passing it to exec

[Salvatore Bonaccorso]

Source: node-growl
Version: 1.7.0-1
Severity: grave
Tags: security upstream
Forwarded: https://github.com/tj/node-growl/issues/60

Hi,

The following vulnerability was published for node-growl.

CVE-2017-16042[0]:
| Growl adds growl notification support to nodejs. Growl before 1.10.2
| does not properly sanitize input before passing it to exec, allowing
| for arbitrary command execution.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-16042
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16042
[1] https://github.com/tj/node-growl/issues/60

Regards,
Salvatore

Processed: Bug #899811 in litecoin marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #899811 [src:litecoin] litecoin: Invalid maintainer address 
pkg-bitcoin-de...@lists.alioth.debian.org
Added tag(s) pending.

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

Bug#899811: Bug #899811 in litecoin marked as pending

[onlyjob]

Control: tag -1 pending

Hello,

Bug #899811 in litecoin 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/debian/litecoin/commit/69db224a383a9006b3b07348e8e8dde574274c9c


set myself as Maintrainer (Closes: #899811).



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/899811

Bug#733180: marked as done (litecoin: not suitable for stable)

[Debian Bug Tracking System]

Your message dated Wed, 06 Jun 2018 16:07:16 +1000
with message-id <2218659.ZjixV9BoM4@deblab>
and subject line Done: litecoin: not suitable for stable
has caused the Debian Bug report #733180,
regarding litecoin: not suitable for stable
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.)


-- 
733180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733180
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: litecoin
Severity: serious

Similar to bitcoin bug #718272 this is to prevent "litecoin" migration
to "testing" as long as "litecoin" is considered unsuitable for "stable".
--- End Message ---
--- Begin Message ---
Source: litecoin

I consider Litecoin to be mature and stable enough for "stable".

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


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