Bug#804579: Ncurses

[olivier sallou]

Ncurses dep must be set by swi prolog compiler, when creating a binary from
logol prolog files. Logol itself does nothing related to this lib.

If compiler adds some unused deps, can't really fix that.

Why setting this to serious?

Olivier

Bug#899789: marked as done (erlang-cowboy: Invalid maintainer address pkg-leofs-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Fri, 01 Jun 2018 05:19:30 +
with message-id 
and subject line Bug#899789: fixed in erlang-cowboy 2.0.0~pre.1+dfsg1-3
has caused the Debian Bug report #899789,
regarding erlang-cowboy: Invalid maintainer address 
pkg-leofs-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.)


-- 
899789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899789
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:erlang-cowboy
Version: 2.0.0~pre.1+dfsg1-2
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of erlang-cowboy,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package erlang-cowboy since the list address
pkg-leofs-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-leofs-de...@lists.alioth.debian.org is 14.

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: erlang-cowboy
Source-Version: 2.0.0~pre.1+dfsg1-3

We believe that the bug you reported is fixed in the latest version of
erlang-cowboy, 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.
Nobuhiro Iwamatsu  (supplier of updated erlang-cowboy 
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: Fri, 01 Jun 2018 08:53:25 +0900
Source: erlang-cowboy
Binary: erlang-cowboy erlang-cowboy-examples erlang-cowboy-doc
Architecture: source all amd64
Version: 2.0.0~pre.1+dfsg1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Erlang Packagers 
Changed-By: Nobuhiro Iwamatsu 
Description:
 erlang-cowboy - Cowboy is a small, fast and modular HTTP server written in 
Erlang
 erlang-cowboy-doc - Documentation files for erlang-cowboy
 erlang-cowboy-examples - Examples for erlang-cowboy
Closes: 899789
Changes:
 erlang-cowboy (2.0.0~pre.1+dfsg1-3) unstable; urgency=medium
 .
   * Update debian/control.
 - Change maintainer address to Debian Erlang Packagers
   . (Closes: #899789)
 - Bump Standards-Version to 4.1.4.
 - Change Vcs-Browser and Vcs-Git to salsa.
 - Update debhelper to 11.
 - Update Homepage field.
   * Update debian/copyright.
 - Update source field.
 - Get rid of lintian 'insecure-copyright-format-uri'.
Checksums-Sha1:
 b9caa873eff6f4d765b59d01a4db1a994a3e1120 2475 
erlang-cowboy_2.0.0~pre.1+dfsg1-3.dsc
 2ae3e326443da23aeebc70cca731cc235b3ceed5 5332 
erlang-cowboy_2.0.0~pre.1+dfsg1-3.debian.tar.xz
 

Bug#898391:

[Jorge Moraleda]

What is the state of this? I​ am on stretch backports trying to upgrade
from ​390.48-2~bpo9+1 (everything working fine) to ​390.48-2~bpo9+3. I am
experiencing something which is another symptom of this bug. Many packets
are held back. I believe the fundamental problem lies with

 nvidia-driver : Depends: nvidia-driver-libs (= 390.48-2~bpo9+3) but it is
not going to be installed or
  nvidia-driver-libs-nonglvnd (= 390.48-2~bpo9+3)
but it is not going to be installed


​I am on stretch backports trying to upgrade from ​390.48-2~bpo9+1
(everything working fine) to ​390.48-2~bpo9+3

Bug#899491: marked as done (erlang-ranch: Invalid maintainer address pkg-leofs-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Fri, 01 Jun 2018 00:34:25 +
with message-id 
and subject line Bug#899491: fixed in erlang-ranch 1.3.0-1
has caused the Debian Bug report #899491,
regarding erlang-ranch: Invalid maintainer address 
pkg-leofs-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.)


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

Dear uploader of erlang-ranch,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package erlang-ranch since the list address
pkg-leofs-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-leofs-de...@lists.alioth.debian.org is 14.

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: erlang-ranch
Source-Version: 1.3.0-1

We believe that the bug you reported is fixed in the latest version of
erlang-ranch, 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.
Nobuhiro Iwamatsu  (supplier of updated erlang-ranch 
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: Fri, 01 Jun 2018 08:00:29 +0900
Source: erlang-ranch
Binary: erlang-ranch erlang-ranch-doc
Architecture: source all amd64
Version: 1.3.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Erlang Packagers 
Changed-By: Nobuhiro Iwamatsu 
Description:
 erlang-ranch - socket acceptor pool for TCP protocols in Erlang
 erlang-ranch-doc - Documentation of erlang-ranch
Closes: 899491
Changes:
 erlang-ranch (1.3.0-1) unstable; urgency=medium
 .
   * New upstream release.
   * Remove debian/patches.
 Applied to upstream.
   * Update debian/contorol.
 - Change maintainer address to Debian Erlang Packagers
   . (Closes: #899491)
 - Bump Standards-Version to 4.1.4.
 - Update debhelper to 11.
 - Change Vcs-Browser and Vcs-Git to salsa.
 - Update Homepage field.
 - Remove whitespace.
 - Get rid of lintian 'binary-control-field-duplicates-source'.
 - Add erlang-asciideck and asciidoc-dblatex to B-D.
   * Update debian/copyright.
 - Update Source field.
 - Get rid of lintian 'insecure-copyright-format-uri'.
   * Update debian/rules.
 - Get rid of lintian 'debian-rules-parses-dpkg-parsechangelog'.
Checksums-Sha1:
 db63c9f38d3c415806ec211414c7f68894c373ec 2299 

Bug#899564: marked as done (ledgersmb: Invalid maintainer address pkg-sql-ledger-discuss...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Fri, 01 Jun 2018 00:20:24 +
with message-id 
and subject line Bug#899564: fixed in ledgersmb 1.4.42+ds-2
has caused the Debian Bug report #899564,
regarding ledgersmb: Invalid maintainer address 
pkg-sql-ledger-discuss...@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.)


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

Dear uploader of ledgersmb,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package ledgersmb since the list address
pkg-sql-ledger-discuss...@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-sql-ledger-discuss...@lists.alioth.debian.org is 1.

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: ledgersmb
Source-Version: 1.4.42+ds-2

We believe that the bug you reported is fixed in the latest version of
ledgersmb, 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.
Robert James Clay  (supplier of updated ledgersmb 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: Thu, 31 May 2018 16:52:03 -0400
Source: ledgersmb
Binary: ledgersmb
Architecture: source all
Version: 1.4.42+ds-2
Distribution: unstable
Urgency: medium
Maintainer: LedgerSMB Core Team 
Changed-By: Robert James Clay 
Description:
 ledgersmb  - financial accounting and ERP program
Closes: 899564
Changes:
 ledgersmb (1.4.42+ds-2) unstable; urgency=medium
 .
   * Declare compliance with Debian Policy 4.1.4.
   * Change the Priority in debian/control from "extra" back to "optional".
   * Correct 'neccessary' as 'necessary' in debian/patches/05_confdir.patch.
   * Change 'Maintainer' to "LedgerSMB Core Team " in
 debian/control. (Closes: #899564)
Checksums-Sha1:
 14ab73e9d7cf26f6a22834433c6d7b4ec138a602 1923 ledgersmb_1.4.42+ds-2.dsc
 8c47ed1756820436ea90045e0ee9304469498cc6 4670428 
ledgersmb_1.4.42+ds.orig.tar.gz
 8bc223ca283325326b58208b8493e92b3978939d 28116 
ledgersmb_1.4.42+ds-2.debian.tar.xz
 17c1ade00ef61628f279f371d7d70d20fdf0c9b5 1925092 ledgersmb_1.4.42+ds-2_all.deb
 9d489603d9d0a7f28e1fc1476cbf23404910dd13 6078 
ledgersmb_1.4.42+ds-2_amd64.buildinfo
Checksums-Sha256:
 b404c4c4992eda83e47dec432b6902d65489f6d341f6ca63c4a0528e5816a66d 1923 
ledgersmb_1.4.42+ds-2.dsc
 

Bug#900460: ephoto: fails to start

[Norbert Preining]

Hi Ross,

thanks for coming back ..

> Can you provide the output of "dpkg -l | grep libevas1-engine"?  It

ii  libevas1-engines-wayland:amd64  1.20.7-4
amd64Evas module providing the Wayland engine

> looks like ephoto can't find a working evas engine.  Probably you're
> using X11 but the dependencies only installed the wayland engine, or
> vice versa.

What else do I need to check?

All the best

Norbert

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

Bug#897515: marked as done (golang-github-influxdata-influxql: FTBFS: dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 github.com/influxdata/influxql github.com/influxdata/influxql/in

[Debian Bug Tracking System]

Your message dated Thu, 31 May 2018 23:53:42 +
with message-id 
and subject line Bug#897515: fixed in golang-github-influxdata-influxql 
0.0~git20180330.145e067-2
has caused the Debian Bug report #897515,
regarding golang-github-influxdata-influxql: FTBFS: dh_auto_test: cd 
obj-x86_64-linux-gnu && go test -vet=off -v -p 8 github.com/influxdata/influxql 
github.com/influxdata/influxql/internal returned exit code 1
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.)


-- 
897515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897515
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-influxdata-influxql
Version: 0.0~git20180330.145e067-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20180502 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=golang --with=golang
>dh_update_autotools_config -O--buildsystem=golang
>dh_autoreconf -O--buildsystem=golang
>dh_auto_configure -O--buildsystem=golang
>dh_auto_build -O--buildsystem=golang
>   cd obj-x86_64-linux-gnu && go install 
> -gcflags=\"-trimpath=/<>/golang-github-influxdata-influxql-0.0\~git20180330.145e067/obj-x86_64-linux-gnu/src\"
>  
> -asmflags=\"-trimpath=/<>/golang-github-influxdata-influxql-0.0\~git20180330.145e067/obj-x86_64-linux-gnu/src\"
>  -v -p 8 github.com/influxdata/influxql 
> github.com/influxdata/influxql/internal
> github.com/gogo/protobuf/proto
> github.com/influxdata/influxql/internal
> github.com/influxdata/influxql
>dh_auto_test -O--buildsystem=golang
>   cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 
> github.com/influxdata/influxql github.com/influxdata/influxql/internal
> panic: open /usr/lib/go-1.10/lib/time/zoneinfo.zip: no such file or directory
> 
> goroutine 1 [running]:
> github.com/influxdata/influxql_test.mustLoadLocation(0x78a024, 0x13, 
> 0xc4200a6060)
>   
> /<>/obj-x86_64-linux-gnu/src/github.com/influxdata/influxql/parser_test.go:4041
>  +0x6f
> FAIL  github.com/influxdata/influxql  0.004s
> ? github.com/influxdata/influxql/internal [no test files]
> dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 
> github.com/influxdata/influxql github.com/influxdata/influxql/internal 
> returned exit code 1

The full build log is available from:
   
http://aws-logs.debian.net/2018/05/02/golang-github-influxdata-influxql_0.0~git20180330.145e067-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: golang-github-influxdata-influxql
Source-Version: 0.0~git20180330.145e067-2

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

Debian distribution maintenance software
pp.
Alexandre Viau  (supplier of updated 
golang-github-influxdata-influxql 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: Thu, 31 May 2018 19:30:52 -0400
Source: golang-github-influxdata-influxql
Binary: golang-github-influxdata-influxql-dev
Architecture: source
Version: 0.0~git20180330.145e067-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Alexandre Viau 
Description:
 golang-github-influxdata-influxql-dev - parser for the InfluxDB query language
Closes: 897515
Changes:
 golang-github-influxdata-influxql (0.0~git20180330.145e067-2) unstable; 
urgency=medium
 .
   * Depend on tzdata (Closes: #897515)
Checksums-Sha1:
 f9381646687078012f045a85bbc47561d4482537 2460 
golang-github-influxdata-influxql_0.0~git20180330.145e067-2.dsc
 5d78890468d46f6f7a69b312776a9bedd6a2cbe3 2592 

Bug#895556: marked as done (golang-github-influxdb-influxdb-dev depends on cruft package)

[Debian Bug Tracking System]

Your message dated Thu, 31 May 2018 23:34:44 +
with message-id 
and subject line Bug#895556: fixed in influxdb 1.5.3-1
has caused the Debian Bug report #895556,
regarding golang-github-influxdb-influxdb-dev depends on cruft package
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.)


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

Package: golang-github-influxdb-influxdb-dev
Version: 1.1.1+dfsg1-4
Severity: serious

golang-github-influxdb-influxdb-dev depends on golang-go.crypto-dev which is no 
longer built by golang-go.crypto
--- End Message ---
--- Begin Message ---
Source: influxdb
Source-Version: 1.5.3-1

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

Debian distribution maintenance software
pp.
Alexandre Viau  (supplier of updated influxdb 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: Thu, 31 May 2018 19:15:29 -0400
Source: influxdb
Binary: golang-github-influxdb-influxdb-dev influxdb influxdb-client
Architecture: source
Version: 1.5.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Alexandre Viau 
Description:
 golang-github-influxdb-influxdb-dev - Scalable datastore for metrics, events, 
and real-time analytics.
 influxdb   - Scalable datastore for metrics, events, and real-time analytics
 influxdb-client - command line interface for InfluxDB
Closes: 880270 895556
Changes:
 influxdb (1.5.3-1) unstable; urgency=medium
 .
   [ Alexandre Viau ]
   * New upstream snapshot.
   * Dependencies:
 +golang-go.uber-zap-dev
 +golang-github-cespare-xxhash-dev
 +golang-github-influxdata-influxql-dev
   * Move to salsa.debian.org.
   * Remove golang-go.crypto-dev dependency. (Closes: #895556)
   * New upload should fix FTBFS. (Closes: #880270)
   * Create use-debian-yarpc.patch.
   * Refresh patches.
   * Depend on debhelper >= 9.20160709 instead of dh_systemd.
   * Fix insecure-copyright-format-uri.
   * Priority extra -> optional.
   * Removed transitional package.
 .
   [ Paul Tagliamonte ]
   * Remove Built-Using from arch:all -dev package
Checksums-Sha1:
 eb25265173b66abdee6e7e19be6e6270def456f1 3537 influxdb_1.5.3-1.dsc
 0d3382514b679b9023057b30ce07f04748084711 1230063 influxdb_1.5.3.orig.tar.gz
 cb2ff10b379a359bf43a6a373722acee20eb47b0 15772 influxdb_1.5.3-1.debian.tar.xz
 ab74fc7f9e2957964a8748cc92f054956be95763 3 
influxdb_1.5.3-1_source.buildinfo
Checksums-Sha256:
 471c274d67c0bcc9e04b2c0e428b4d48ff8d9d7bd5f3770af0ecd1a3d36f04e8 3537 
influxdb_1.5.3-1.dsc
 2ff2fb0952ef2be2c67a96df103f3b2f8c1cb2542e0a1a4329c803d95a01c9e7 1230063 
influxdb_1.5.3.orig.tar.gz
 63a9ffa197e8903262ead6030dfeb93f17c6d73a6f5b97338d3e43a85a5aa2b7 15772 
influxdb_1.5.3-1.debian.tar.xz
 55aa745e2285abb60e0663c5bf8ab8f231c54ef8caa6919318c3853a2ded61a1 3 
influxdb_1.5.3-1_source.buildinfo
Files:
 84bd10a5e155624d61f0453128ccf4d7 3537 database optional influxdb_1.5.3-1.dsc
 c375cb846f3d331a3c976eebea4c075e 1230063 database optional 
influxdb_1.5.3.orig.tar.gz
 65f5a718f7027bc0dd0f034a11251799 15772 database optional 
influxdb_1.5.3-1.debian.tar.xz
 c719040031b2b238fe32b85882d9367e 3 database optional 
influxdb_1.5.3-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEB0B3ii38SjnAyLyMjysRPGU1xacFAlsQgikACgkQjysRPGU1
xadrTg/8DI/teJWLkxngfyuwPyJFfiRT+UYyIUSa9RL+GIfyclefdmmPTlvziSPA
UXFpsUaan4eybxsonCOEHwiAFubAZvtzMXl+N0oq2rNrgWtIwzlO+O3hz7Jvxv34
BFr5W3flGBvG0q7BopTGXPcfm5P/PU1MmgNGxHzVESlL1m46oYWhHVsmw5UGrzw9
uoX1zbD4MIkqhMSykG+n0HsENzcrMwSttvaMeOwpB9Sy21FWAPFxh26Jqu/NnvpX
dlzGPUmYAqpjpBY+oUYSBx4OPrUQEpZZLmvOVSskIC4vE7suZ7io3ZkBdcLWSiMy
pWc6XEUPTFeVClGPvIhf37rAJ9fVMFb4gJId0u4TER6frIG7tqinTmJdDCwqPM8U
kp77fv0Ov+uXpZV+4H0K2wOj3VHR9FVl5e+dhvOy4LZmHH3Sm6G8YUt/lpIiB3ee
6xzeML7pUqqNqspxbqyQnUf07AhTgDJIi+mWKrUHTK98X5282/uPe9QBC+9OpANI
069FQ5/98gcCtBzM1ApZtosZn8o4vfzXojl35m5173d1Sno8XZCnfVKfxCy2lofv
gSL3JHcTLa084empNBy8Q04QUy09PSycldAIscihSl2LY8+dkqAGHdLCKaU58e85

Bug#880270: marked as done (influxdb: FTBFS: Test failures)

[Debian Bug Tracking System]

Your message dated Thu, 31 May 2018 23:34:44 +
with message-id 
and subject line Bug#880270: fixed in influxdb 1.5.3-1
has caused the Debian Bug report #880270,
regarding influxdb: FTBFS: Test failures
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.)


-- 
880270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880270
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: influxdb
Version: 1.1.1+dfsg1-4
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20171030 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> === RUN   TestTSMWriter_Write_MaxKey
> --- PASS: TestTSMWriter_Write_MaxKey (0.58s)
> [tsm1] 2017/10/30 15:37:12 Snapshot for path /tmp/tsm1-783841729/data written 
> in 3.890572ms
> [tsm1] 2017/10/30 15:37:12 Snapshot for path /tmp/tsm1-837189676/data written 
> in 4.814572ms
> --- PASS: TestEngine_CreateIterator_Aux (1.00s)
> --- PASS: TestEngine_CreateIterator_TSM_Descending (2.00s)
> --- PASS: TestEngine_CreateIterator_TSM_Ascending (2.00s)
> --- PASS: TestEngine_CreateIterator_Cache_Ascending (2.00s)
> --- PASS: TestEngine_CreateIterator_Cache_Descending (2.00s)
> --- PASS: TestEngine_CreateIterator_Condition (2.00s)
> PASS
> okgithub.com/influxdata/influxdb/tsdb/engine/tsm1 37.904s
> ? github.com/influxdata/influxdb/tsdb/internal[no test files]
> ? github.com/influxdata/influxdb/uuid [no test files]
> dh_auto_test: cd _build && go test -v -p 1 -timeout 12000s 
> github.com/influxdata/influxdb github.com/influxdata/influxdb/client 
> github.com/influxdata/influxdb/client/v2 github.com/influxdata/influxdb/cmd 
> github.com/influxdata/influxdb/cmd/influx 
> github.com/influxdata/influxdb/cmd/influx/cli 
> github.com/influxdata/influxdb/cmd/influx_inspect 
> github.com/influxdata/influxdb/cmd/influx_inspect/dumptsm 
> github.com/influxdata/influxdb/cmd/influx_inspect/export 
> github.com/influxdata/influxdb/cmd/influx_inspect/help 
> github.com/influxdata/influxdb/cmd/influx_inspect/report 
> github.com/influxdata/influxdb/cmd/influx_inspect/verify 
> github.com/influxdata/influxdb/cmd/influx_stress 
> github.com/influxdata/influxdb/cmd/influx_tsm 
> github.com/influxdata/influxdb/cmd/influx_tsm/b1 
> github.com/influxdata/influxdb/cmd/influx_tsm/bz1 
> github.com/influxdata/influxdb/cmd/influx_tsm/stats 
> github.com/influxdata/influxdb/cmd/influx_tsm/tsdb 
> github.com/influxdata/influxdb/cmd/influx_tsm/tsdb/internal 
> github.com/influxdata/influxdb/cmd/influxd 
> github.com/influxdata/influxdb/cmd/influxd/backup 
> github.com/influxdata/influxdb/cmd/influxd/help 
> github.com/influxdata/influxdb/cmd/influxd/restore 
> github.com/influxdata/influxdb/cmd/influxd/run 
> github.com/influxdata/influxdb/coordinator 
> github.com/influxdata/influxdb/importer/v8 
> github.com/influxdata/influxdb/influxql 
> github.com/influxdata/influxdb/influxql/internal 
> github.com/influxdata/influxdb/influxql/neldermead 
> github.com/influxdata/influxdb/internal github.com/influxdata/influxdb/models 
> github.com/influxdata/influxdb/monitor 
> github.com/influxdata/influxdb/monitor/diagnostics 
> github.com/influxdata/influxdb/pkg/deep 
> github.com/influxdata/influxdb/pkg/escape 
> github.com/influxdata/influxdb/pkg/limiter 
> github.com/influxdata/influxdb/pkg/pool 
> github.com/influxdata/influxdb/pkg/slices 
> github.com/influxdata/influxdb/services/admin 
> github.com/influxdata/influxdb/services/admin/statik 
> github.com/influxdata/influxdb/services/collectd 
> github.com/influxdata/influxdb/services/collectd/test_client 
> github.com/influxdata/influxdb/services/continuous_querier 
> github.com/influxdata/influxdb/services/graphite 
> github.com/influxdata/influxdb/services/httpd 
> github.com/influxdata/influxdb/services/meta 
> github.com/influxdata/influxdb/services/meta/internal 
> github.com/influxdata/influxdb/services/opentsdb 
> github.com/influxdata/influxdb/services/precreator 
> github.com/influxdata/influxdb/services/retention 
> github.com/influxdata/influxdb/services/snapshotter 
> github.com/influxdata/influxdb/services/subscriber 
> github.com/influxdata/influxdb/services/udp 
> github.com/influxdata/influxdb/stress 
> github.com/influxdata/influxdb/stress/stress_test_server 
> github.com/influxdata/influxdb/stress/v2 
> github.com/influxdata/influxdb/stress/v2/statement 
> github.com/influxdata/influxdb/stress/v2/stress_client 
> github.com/influxdata/influxdb/stress/v2/stressql 
> 

Bug#899823: marked as done (erlang-proper: Invalid maintainer address pkg-leofs-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Thu, 31 May 2018 23:19:30 +
with message-id 
and subject line Bug#899823: fixed in erlang-proper 1.2+git988ea0ed9f+dfsg-2
has caused the Debian Bug report #899823,
regarding erlang-proper: Invalid maintainer address 
pkg-leofs-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.)


-- 
899823: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899823
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:erlang-proper
Version: 1.2+git988ea0ed9f+dfsg-1
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of erlang-proper,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package erlang-proper since the list address
pkg-leofs-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-leofs-de...@lists.alioth.debian.org is 14.

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: erlang-proper
Source-Version: 1.2+git988ea0ed9f+dfsg-2

We believe that the bug you reported is fixed in the latest version of
erlang-proper, 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.
Nobuhiro Iwamatsu  (supplier of updated erlang-proper 
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: Fri, 01 Jun 2018 07:43:12 +0900
Source: erlang-proper
Binary: erlang-proper erlang-proper-dev erlang-proper-doc
Architecture: source amd64 all
Version: 1.2+git988ea0ed9f+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Erlang Packagers 
Changed-By: Nobuhiro Iwamatsu 
Description:
 erlang-proper - QuickCheck-inspired property-based testing tool for Erlang
 erlang-proper-dev - QuickCheck-inspired property-based testing tool for Erlang 
- deve
 erlang-proper-doc - QuickCheck-inspired property-based testing tool for Erlang 
- docu
Closes: 899823
Changes:
 erlang-proper (1.2+git988ea0ed9f+dfsg-2) unstable; urgency=medium
 .
   * Change maintainer address to Debian Erlang Packagers
 . (Closes: #899823)
   * Bump Standards-Version to 4.1.4.
   * Change Vcs-Browser and Vcs-Git to salsa.
   * Update debhelper to 11.
   * Update debian/copyright.
 - Add Upstream-Name and Upstream-Contact.
 - Update Format field in copyright.
Checksums-Sha1:
 2bdf2d2d9b1360a2b463dca5230ec583194fc272 2353 
erlang-proper_1.2+git988ea0ed9f+dfsg-2.dsc
 b75167704108f2bce309fd965d1e2f72230a50b2 3288 
erlang-proper_1.2+git988ea0ed9f+dfsg-2.debian.tar.xz
 

Bug#900535: Binary Independent build seems to have FTBFS

[Diane Trout]

Package: src:python3-stdlib-extensions
Version: 3.6.4-4
Severity: serious
X-Debbugs-CC: debian-pyt...@lists.debian.org


Hello,

python3-distutils is currently unavailable in unstable, it appears that
python3-stdlib-extensions was intended to provided it, but the all
architecture package is failing to build because of a missing
dependency on distutils.

https://buildd.debian.org/status/fetch.php?pkg=python3-stdlib-extension
s=all=3.6.5-4=1527781937=0

Thank you,
Diane

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

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

[Justin P.]

Package: chromium
Version: 67.0.3396.62-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

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

   * What led up to the situation?

Can't use video on youtube. Gif's no longer work. And I cannot get media to 
play. This started after upgrading from 66.0.3359.181-1 to 67.0.3396.62-1

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

Reverting the package was the only solution I could find. It appears the app 
build may be missing some flags in the build. I found this that had similar 
errors to my situation 
https://groups.google.com/a/chromium.org/forum/?nomobile=true#!msg/android-webview-dev/oVjyFhhxOQ8/ns8q9uPrCAAJ

   * What was the outcome of this action?

chromium 66.0.3359.181-1 was reinstalled, video is working again.

   * What outcome did you expect instead?

chromium 67.0.3396.62-1 video should work after install.

Chromium Log while trying to play files
[129:160:0531/181749.318090:ERROR:render_media_log.cc(30)] MediaEvent: 
MEDIA_ERROR_LOG_ENTRY {"error":"FFmpegDemuxer: open context failed"}
[129:129:0531/181749.320645:ERROR:render_media_log.cc(30)] MediaEvent: 
PIPELINE_ERROR DEMUXER_ERROR_COULD_NOT_OPEN
[129:160:0531/181749.352209:ERROR:render_media_log.cc(30)] MediaEvent: 
MEDIA_ERROR_LOG_ENTRY {"error":"FFmpegDemuxer: open context failed"}
[129:129:0531/181749.354280:ERROR:render_media_log.cc(30)] MediaEvent: 
PIPELINE_ERROR DEMUXER_ERROR_COULD_NOT_OPEN
[129:160:0531/181749.551754:ERROR:render_media_log.cc(30)] MediaEvent: 
MEDIA_ERROR_LOG_ENTRY {"error":"audio decoder initialization failed"}
[129:129:0531/181749.559473:ERROR:render_media_log.cc(30)] MediaEvent: 
PIPELINE_ERROR DECODER_ERROR_NOT_SUPPORTED
[129:160:0531/181750.431299:ERROR:render_media_log.cc(30)] MediaEvent: 
MEDIA_ERROR_LOG_ENTRY {"error":"audio decoder initialization failed"}
[129:129:0531/181750.433293:ERROR:render_media_log.cc(30)] MediaEvent: 
PIPELINE_ERROR DECODER_ERROR_NOT_SUPPORTED
libpng warning: iCCP: known incorrect sRGB profile


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

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

Versions of packages 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 7:3.4.2-2+b1
ii  libavformat577:3.4.2-2+b1
ii  libavutil55  7:3.4.2-2+b1
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-4
ii  libgdk-pixbuf2.0-0   2.36.11-2
ii  libglib2.0-0 2.56.1-2
ii  libgtk-3-0   3.22.30-1
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.1-1
ii  libpangocairo-1.0-0  1.42.1-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-4
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

Bug#833692: pinot: links GPLv2+ code with OpenSSL

[Olly Betts]

On Thu, May 31, 2018 at 12:22:58AM +0200, Sebastian Andrzej Siewior wrote:
> pinot has currently two RC bugs and failed to build during the curl4
> transition / binNMU.
> Does it make sense to add the two patches (Olly pointed to) and upload
> it or would a RM make sense?

Popcon suggests pinot usage is low:

https://qa.debian.org/popcon.php?package=pinot

I'm not sure there's really a direct equivalent though, so it seems
worth uploading with at least the RC fixes.  I can prepare an upload
(or happy for someone else to).

Jonas: Are you still interested in maintaining pinot?  I ask because
it's had RC bugs open for a long time without any maintainer response,
and the last maintainer upload was over five years ago now.

Let me know and if not I can orphan or adopt in my upload.

Cheers,
Olly

Bug#900528: marked as done (does not install in buster)

[Debian Bug Tracking System]

Your message dated Thu, 31 May 2018 21:49:23 +
with message-id 
and subject line Bug#900528: fixed in ghub-plus-el 0.2.1-2
has caused the Debian Bug report #900528,
regarding does not install 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.)


-- 
900528: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900528
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: elpa-ghub+
Version: 0.2.1-1
Severity: serious

postinst fails:

In ghubp-base-html-url:
ghub+.el:240:8:Warning: ‘(host (magit-get "github" "host"))’ is a malformed
function
ghub+.el:243:65:Warning: reference to free variable ‘host’
ghub+.el:745:1:Error: :condition-case must be a list of error handlers; see the 
documentation: ((ghub-404 nil))
ERROR: install script from elpa-ghub+ package failed
dpkg: error processing package elpa-ghub+ (--configure):
 installed elpa-ghub+ package post-installation script subprocess returned 
error exit status 1


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

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

Versions of packages elpa-ghub+ depends on:
ii  elpa-apiwrap0.4-1
ii  elpa-ghub   2.0.0-1
ii  emacsen-common  2.0.8

Versions of packages elpa-ghub+ recommends:
ii  emacs  47.0

elpa-ghub+ suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: ghub-plus-el
Source-Version: 0.2.1-2

We believe that the bug you reported is fixed in the latest version of
ghub-plus-el, 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.
Matteo F. Vescovi  (supplier of updated ghub-plus-el 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: Thu, 31 May 2018 23:28:28 +0200
Source: ghub-plus-el
Binary: elpa-ghub+
Architecture: source
Version: 0.2.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Emacsen team 
Changed-By: Matteo F. Vescovi 
Description:
 elpa-ghub+ - thick GitHub API client built on ghub
Closes: 900528
Changes:
 ghub-plus-el (0.2.1-2) unstable; urgency=medium
 .
   * debian/patches/: patchset updated
 - 0001-Fix_900528.patch added (Closes: #900528)
   * debian/control:
 - S-V bump 4.1.3 -> 4.1.4 (no changes needed)
 - Vcs-* fields updated pointing to salsa
 - Maintainer field updated
Checksums-Sha1:
 48514bd3b3a42cce447fd3d5076860990f13c6f5 2132 ghub-plus-el_0.2.1-2.dsc
 3597775a89769eb96dba12dedc419955a108eb90 2928 
ghub-plus-el_0.2.1-2.debian.tar.xz
 bcdac426423d0f9c064aeebf5e43902ac49da00f 12840 
ghub-plus-el_0.2.1-2_source.buildinfo
Checksums-Sha256:
 ed5c270fc4e49924797a8a769ea9784f9c62714e6d60e25208ec16ecb9658b69 2132 
ghub-plus-el_0.2.1-2.dsc
 099a52380759980dac5ff3f1675e5011227b85eaecf0747120537f41ca972112 2928 
ghub-plus-el_0.2.1-2.debian.tar.xz
 8af44690ee956de26cabdc8b24070ee6226606ca9f3f1b2d2612d490e3627e8f 12840 
ghub-plus-el_0.2.1-2_source.buildinfo
Files:
 c60c8a24dc095ebdfa6994c9c355752a 2132 lisp optional ghub-plus-el_0.2.1-2.dsc
 d77eada9f0cffd61755b5d782359918e 2928 lisp optional 
ghub-plus-el_0.2.1-2.debian.tar.xz
 bea2bcb76d2067aed9c220257d517b41 12840 lisp optional 
ghub-plus-el_0.2.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-
Comment: Debian powered!

iQKTBAEBCgB9FiEE890J+NqH0d9QRsmbBhL0lE7NzVoFAlsQaqJfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEYz
REQwOUY4REE4N0QxREY1MDQ2Qzk5QjA2MTJGNDk0NEVDRENENUEACgkQBhL0lE7N
zVqUaw//bKHL32CnJRrCCf8Wf/bRrMXoacCM2/rLiNe8pou/mMBDJVDWLyOna9/4
/nTPlCbaRGe4QSKnMx9anp2VN9z6xJnr+/KV51ZOzYN1EB0Jl3wSQ0hEX+1wsA3K
0GGx3KVy7Iho1yALHUyC4Mc6Q4vncQm1BOBxO2Ut3TOjKKs8usI6XiQheMz5pKIF
C/dGTcA3Mk8NU2OcSveYvjmjQr7rZpKrlE0xMWgcQVHroxoIr2VCGciCmBjCmrae
UfwxpjPJJSZJi2+XkjWneYg4T9ebsW4Os7ikctq0OzlJMBOQEDOgLOqqRyTFmRFS
P7AfX23azDlUi1EnElp6174tXAr+GgDl4TIayPSJAVtBqss2aw0DhRjYojxhd4Ar

Bug#899357: marked as done (fails to configure without snakeoil cert)

[Debian Bug Tracking System]

Your message dated Thu, 31 May 2018 21:34:40 +
with message-id 
and subject line Bug#899357: fixed in prosody 0.10.2-1
has caused the Debian Bug report #899357,
regarding fails to configure without snakeoil cert
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.)


-- 
899357: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899357
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: prosody
Version: 0.10.1-1~bpo9+1
Severity: serious
User: debian-ad...@lists.debian.org
Usertags: needed-by-DSA-Team

| vogler:~# dpkg --configure -a
| Setting up prosody (0.10.1-1~bpo9+1) ...
| install: cannot stat '/etc/ssl/certs/ssl-cert-snakeoil.pem': No such file or 
directory
| dpkg: error processing package prosody (--configure):
|  subprocess installed post-installation script returned error exit status 1
| Errors were encountered while processing:
|  prosody
| vogler:~# echo $?
| 1

We, of course, don't have snakeoil certs anymore.
-- 
|  .''`.   ** Debian **
  Peter Palfrader   | : :' :  The  universal
 https://www.palfrader.org/ | `. `'  Operating System
|   `-https://www.debian.org/
--- End Message ---
--- Begin Message ---
Source: prosody
Source-Version: 0.10.2-1

We believe that the bug you reported is fixed in the latest version of
prosody, 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.
W. Martin Borgert  (supplier of updated prosody 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: Thu, 31 May 2018 20:57:00 +
Source: prosody
Binary: prosody
Architecture: source amd64
Version: 0.10.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian XMPP Maintainers 
Changed-By: W. Martin Borgert 
Description:
 prosody- Lightweight Jabber/XMPP server
Closes: 899352 899357 899359 900524
Changes:
 prosody (0.10.2-1) unstable; urgency=medium
 .
   * Team upload.
   * Set Debian XMPP team as maintainer.
   * Reverting fix for #851669, because it introduced other bugs
 (closes: #899352, #899357, #899359).
   * New upstream release (Closes: #900524), which fixes
 CVE-2018-10847: insufficient stream header validation.
Checksums-Sha1:
 c90a216899a7ab1fb4877a5b8e80328b031fe3e3 2359 prosody_0.10.2-1.dsc
 1d51e542475c3f3e712eace29537b042c941d6ab 331874 prosody_0.10.2.orig.tar.gz
 9f0e064685f8894b60852c9d14f1a37ec8526dca 801 prosody_0.10.2.orig.tar.gz.asc
 895b0628ffe0d73cad4adb9251a017a58baa93ed 15160 prosody_0.10.2-1.debian.tar.xz
 6250a1d77bd76ec8c115e38d92dcc3422d82346d 46728 
prosody-dbgsym_0.10.2-1_amd64.deb
 e81bd914d9e89bfd568d0320e1a4918320f6890a 6259 prosody_0.10.2-1_amd64.buildinfo
 bf3eb0134b6627acbee6c88521337cb668e02f4a 249680 prosody_0.10.2-1_amd64.deb
Checksums-Sha256:
 4127c5741c480db9cfc77e6d6bdbf7af5b95526fff73b1c83354f8be76a3e960 2359 
prosody_0.10.2-1.dsc
 75b5f035e7a74d5f208eeeaf8419b94a85d09b40252d444cff8033fde3c9768e 331874 
prosody_0.10.2.orig.tar.gz
 af8b6256ca9ceaec276d5a8ebe0f22c8da6baf0b08981be442445e5c0a508daf 801 
prosody_0.10.2.orig.tar.gz.asc
 c63dec38aa98b8c2e4b573150517caac28c9be2270a8507c921ac3e6711d31b1 15160 
prosody_0.10.2-1.debian.tar.xz
 9cbd409976b82c022d5e43896ef7642931a3f199745a931f8d608046afaa9af2 46728 
prosody-dbgsym_0.10.2-1_amd64.deb
 92f84d9ccb8a65d31e747e1a2580faf6c5318fbd59531c5b17f9559abdb6dc49 6259 
prosody_0.10.2-1_amd64.buildinfo
 9de5a8ef8cf73814de50f436027ac3c45698e645b8a13c3ba89f75cf0d23aa30 249680 
prosody_0.10.2-1_amd64.deb
Files:
 00e974c8d720a8b4ea2ac27b0f0735cd 2359 net optional prosody_0.10.2-1.dsc
 4cb1ac0db2b739b933ded5038551d7c2 331874 net optional prosody_0.10.2.orig.tar.gz
 45621204690b30337df68e2c12617905 801 net optional 
prosody_0.10.2.orig.tar.gz.asc
 2864934a58fae82f69532623ac8bbf39 15160 net optional 
prosody_0.10.2-1.debian.tar.xz
 eb6fd18bb0301e22d757dc2bada0eb6d 46728 debug optional 
prosody-dbgsym_0.10.2-1_amd64.deb
 ad1db41a556f981be99757194ee9c8a1 6259 net optional 
prosody_0.10.2-1_amd64.buildinfo
 a05b1504e9c9d80f7bce272c4608c889 249680 net optional prosody_0.10.2-1_amd64.deb

-BEGIN 

Bug#900524: marked as done (prosody: CVE-2018-10847: insufficient stream header validation)

[Debian Bug Tracking System]

Your message dated Thu, 31 May 2018 21:34:40 +
with message-id 
and subject line Bug#900524: fixed in prosody 0.10.2-1
has caused the Debian Bug report #900524,
regarding prosody: CVE-2018-10847: insufficient stream header validation
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.)


-- 
900524: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900524
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: prosody
Version: 0.9.7-2
Severity: grave
Tags: security upstream
Justification: user security hole
Control: found -1 0.10.1-1
Control: forwarded -1 https://issues.prosody.im/1147


Hi,

The following vulnerability was published for prosody.

CVE-2018-10847[0]:
insufficient stream header validation

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-10847
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10847
[1] https://issues.prosody.im/1147
[2] https://blog.prosody.im/prosody-0-10-2-security-release/

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: prosody
Source-Version: 0.10.2-1

We believe that the bug you reported is fixed in the latest version of
prosody, 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.
W. Martin Borgert  (supplier of updated prosody 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: Thu, 31 May 2018 20:57:00 +
Source: prosody
Binary: prosody
Architecture: source amd64
Version: 0.10.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian XMPP Maintainers 
Changed-By: W. Martin Borgert 
Description:
 prosody- Lightweight Jabber/XMPP server
Closes: 899352 899357 899359 900524
Changes:
 prosody (0.10.2-1) unstable; urgency=medium
 .
   * Team upload.
   * Set Debian XMPP team as maintainer.
   * Reverting fix for #851669, because it introduced other bugs
 (closes: #899352, #899357, #899359).
   * New upstream release (Closes: #900524), which fixes
 CVE-2018-10847: insufficient stream header validation.
Checksums-Sha1:
 c90a216899a7ab1fb4877a5b8e80328b031fe3e3 2359 prosody_0.10.2-1.dsc
 1d51e542475c3f3e712eace29537b042c941d6ab 331874 prosody_0.10.2.orig.tar.gz
 9f0e064685f8894b60852c9d14f1a37ec8526dca 801 prosody_0.10.2.orig.tar.gz.asc
 895b0628ffe0d73cad4adb9251a017a58baa93ed 15160 prosody_0.10.2-1.debian.tar.xz
 6250a1d77bd76ec8c115e38d92dcc3422d82346d 46728 
prosody-dbgsym_0.10.2-1_amd64.deb
 e81bd914d9e89bfd568d0320e1a4918320f6890a 6259 prosody_0.10.2-1_amd64.buildinfo
 bf3eb0134b6627acbee6c88521337cb668e02f4a 249680 prosody_0.10.2-1_amd64.deb
Checksums-Sha256:
 4127c5741c480db9cfc77e6d6bdbf7af5b95526fff73b1c83354f8be76a3e960 2359 
prosody_0.10.2-1.dsc
 75b5f035e7a74d5f208eeeaf8419b94a85d09b40252d444cff8033fde3c9768e 331874 
prosody_0.10.2.orig.tar.gz
 af8b6256ca9ceaec276d5a8ebe0f22c8da6baf0b08981be442445e5c0a508daf 801 
prosody_0.10.2.orig.tar.gz.asc
 c63dec38aa98b8c2e4b573150517caac28c9be2270a8507c921ac3e6711d31b1 15160 
prosody_0.10.2-1.debian.tar.xz
 9cbd409976b82c022d5e43896ef7642931a3f199745a931f8d608046afaa9af2 46728 
prosody-dbgsym_0.10.2-1_amd64.deb
 92f84d9ccb8a65d31e747e1a2580faf6c5318fbd59531c5b17f9559abdb6dc49 6259 
prosody_0.10.2-1_amd64.buildinfo
 9de5a8ef8cf73814de50f436027ac3c45698e645b8a13c3ba89f75cf0d23aa30 249680 
prosody_0.10.2-1_amd64.deb
Files:
 00e974c8d720a8b4ea2ac27b0f0735cd 2359 net optional prosody_0.10.2-1.dsc
 4cb1ac0db2b739b933ded5038551d7c2 331874 net optional prosody_0.10.2.orig.tar.gz
 45621204690b30337df68e2c12617905 801 net optional 
prosody_0.10.2.orig.tar.gz.asc
 2864934a58fae82f69532623ac8bbf39 15160 net optional 
prosody_0.10.2-1.debian.tar.xz
 eb6fd18bb0301e22d757dc2bada0eb6d 46728 debug optional 
prosody-dbgsym_0.10.2-1_amd64.deb
 ad1db41a556f981be99757194ee9c8a1 6259 net optional 
prosody_0.10.2-1_amd64.buildinfo
 a05b1504e9c9d80f7bce272c4608c889 249680 net optional prosody_0.10.2-1_amd64.deb

-BEGIN PGP SIGNATURE-

Bug#899359: marked as done (fails to configure without /etc/prosody/certs/localhost.*)

[Debian Bug Tracking System]

Your message dated Thu, 31 May 2018 21:34:40 +
with message-id 
and subject line Bug#899359: fixed in prosody 0.10.2-1
has caused the Debian Bug report #899359,
regarding fails to configure without /etc/prosody/certs/localhost.*
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.)


-- 
899359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899359
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: prosody
Version: 0.10.1-1~bpo9+1
Severity: serious
User: debian-ad...@lists.debian.org
Usertags: needed-by-DSA-Team

[fixing the snakeoil stuff, we then run into:]

| # dpkg --configure -a
| Setting up prosody (0.10.1-1~bpo9+1) ...
| chown: cannot access '/etc/prosody/certs/localhost.crt': No such file or 
directory
| dpkg: error processing package prosody (--configure):
|  subprocess installed post-installation script returned error exit status 1
| Errors were encountered while processing:
|  prosody

and then the same with the .key.

-- 
|  .''`.   ** Debian **
  Peter Palfrader   | : :' :  The  universal
 https://www.palfrader.org/ | `. `'  Operating System
|   `-https://www.debian.org/
--- End Message ---
--- Begin Message ---
Source: prosody
Source-Version: 0.10.2-1

We believe that the bug you reported is fixed in the latest version of
prosody, 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.
W. Martin Borgert  (supplier of updated prosody 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: Thu, 31 May 2018 20:57:00 +
Source: prosody
Binary: prosody
Architecture: source amd64
Version: 0.10.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian XMPP Maintainers 
Changed-By: W. Martin Borgert 
Description:
 prosody- Lightweight Jabber/XMPP server
Closes: 899352 899357 899359 900524
Changes:
 prosody (0.10.2-1) unstable; urgency=medium
 .
   * Team upload.
   * Set Debian XMPP team as maintainer.
   * Reverting fix for #851669, because it introduced other bugs
 (closes: #899352, #899357, #899359).
   * New upstream release (Closes: #900524), which fixes
 CVE-2018-10847: insufficient stream header validation.
Checksums-Sha1:
 c90a216899a7ab1fb4877a5b8e80328b031fe3e3 2359 prosody_0.10.2-1.dsc
 1d51e542475c3f3e712eace29537b042c941d6ab 331874 prosody_0.10.2.orig.tar.gz
 9f0e064685f8894b60852c9d14f1a37ec8526dca 801 prosody_0.10.2.orig.tar.gz.asc
 895b0628ffe0d73cad4adb9251a017a58baa93ed 15160 prosody_0.10.2-1.debian.tar.xz
 6250a1d77bd76ec8c115e38d92dcc3422d82346d 46728 
prosody-dbgsym_0.10.2-1_amd64.deb
 e81bd914d9e89bfd568d0320e1a4918320f6890a 6259 prosody_0.10.2-1_amd64.buildinfo
 bf3eb0134b6627acbee6c88521337cb668e02f4a 249680 prosody_0.10.2-1_amd64.deb
Checksums-Sha256:
 4127c5741c480db9cfc77e6d6bdbf7af5b95526fff73b1c83354f8be76a3e960 2359 
prosody_0.10.2-1.dsc
 75b5f035e7a74d5f208eeeaf8419b94a85d09b40252d444cff8033fde3c9768e 331874 
prosody_0.10.2.orig.tar.gz
 af8b6256ca9ceaec276d5a8ebe0f22c8da6baf0b08981be442445e5c0a508daf 801 
prosody_0.10.2.orig.tar.gz.asc
 c63dec38aa98b8c2e4b573150517caac28c9be2270a8507c921ac3e6711d31b1 15160 
prosody_0.10.2-1.debian.tar.xz
 9cbd409976b82c022d5e43896ef7642931a3f199745a931f8d608046afaa9af2 46728 
prosody-dbgsym_0.10.2-1_amd64.deb
 92f84d9ccb8a65d31e747e1a2580faf6c5318fbd59531c5b17f9559abdb6dc49 6259 
prosody_0.10.2-1_amd64.buildinfo
 9de5a8ef8cf73814de50f436027ac3c45698e645b8a13c3ba89f75cf0d23aa30 249680 
prosody_0.10.2-1_amd64.deb
Files:
 00e974c8d720a8b4ea2ac27b0f0735cd 2359 net optional prosody_0.10.2-1.dsc
 4cb1ac0db2b739b933ded5038551d7c2 331874 net optional prosody_0.10.2.orig.tar.gz
 45621204690b30337df68e2c12617905 801 net optional 
prosody_0.10.2.orig.tar.gz.asc
 2864934a58fae82f69532623ac8bbf39 15160 net optional 
prosody_0.10.2-1.debian.tar.xz
 eb6fd18bb0301e22d757dc2bada0eb6d 46728 debug optional 
prosody-dbgsym_0.10.2-1_amd64.deb
 ad1db41a556f981be99757194ee9c8a1 6259 net optional 
prosody_0.10.2-1_amd64.buildinfo
 a05b1504e9c9d80f7bce272c4608c889 249680 net optional prosody_0.10.2-1_amd64.deb

Bug#899352: marked as done (removes prosody role from ssl-cert)

[Debian Bug Tracking System]

Your message dated Thu, 31 May 2018 21:34:40 +
with message-id 
and subject line Bug#899352: fixed in prosody 0.10.2-1
has caused the Debian Bug report #899352,
regarding removes prosody role from ssl-cert
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.)


-- 
899352: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899352
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: prosody
Version: 0.10.1-1~bpo9+1
Severity: serious
User: debian-ad...@lists.debian.org
Usertags: needed-by-DSA-Team

The prosody package removes the prosody role from ssl-cert at configure
time.  If the admin added the prosody user to the ssl-cert group, this
undoes local configuration changes.

-- 
|  .''`.   ** Debian **
  Peter Palfrader   | : :' :  The  universal
 https://www.palfrader.org/ | `. `'  Operating System
|   `-https://www.debian.org/
--- End Message ---
--- Begin Message ---
Source: prosody
Source-Version: 0.10.2-1

We believe that the bug you reported is fixed in the latest version of
prosody, 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.
W. Martin Borgert  (supplier of updated prosody 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: Thu, 31 May 2018 20:57:00 +
Source: prosody
Binary: prosody
Architecture: source amd64
Version: 0.10.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian XMPP Maintainers 
Changed-By: W. Martin Borgert 
Description:
 prosody- Lightweight Jabber/XMPP server
Closes: 899352 899357 899359 900524
Changes:
 prosody (0.10.2-1) unstable; urgency=medium
 .
   * Team upload.
   * Set Debian XMPP team as maintainer.
   * Reverting fix for #851669, because it introduced other bugs
 (closes: #899352, #899357, #899359).
   * New upstream release (Closes: #900524), which fixes
 CVE-2018-10847: insufficient stream header validation.
Checksums-Sha1:
 c90a216899a7ab1fb4877a5b8e80328b031fe3e3 2359 prosody_0.10.2-1.dsc
 1d51e542475c3f3e712eace29537b042c941d6ab 331874 prosody_0.10.2.orig.tar.gz
 9f0e064685f8894b60852c9d14f1a37ec8526dca 801 prosody_0.10.2.orig.tar.gz.asc
 895b0628ffe0d73cad4adb9251a017a58baa93ed 15160 prosody_0.10.2-1.debian.tar.xz
 6250a1d77bd76ec8c115e38d92dcc3422d82346d 46728 
prosody-dbgsym_0.10.2-1_amd64.deb
 e81bd914d9e89bfd568d0320e1a4918320f6890a 6259 prosody_0.10.2-1_amd64.buildinfo
 bf3eb0134b6627acbee6c88521337cb668e02f4a 249680 prosody_0.10.2-1_amd64.deb
Checksums-Sha256:
 4127c5741c480db9cfc77e6d6bdbf7af5b95526fff73b1c83354f8be76a3e960 2359 
prosody_0.10.2-1.dsc
 75b5f035e7a74d5f208eeeaf8419b94a85d09b40252d444cff8033fde3c9768e 331874 
prosody_0.10.2.orig.tar.gz
 af8b6256ca9ceaec276d5a8ebe0f22c8da6baf0b08981be442445e5c0a508daf 801 
prosody_0.10.2.orig.tar.gz.asc
 c63dec38aa98b8c2e4b573150517caac28c9be2270a8507c921ac3e6711d31b1 15160 
prosody_0.10.2-1.debian.tar.xz
 9cbd409976b82c022d5e43896ef7642931a3f199745a931f8d608046afaa9af2 46728 
prosody-dbgsym_0.10.2-1_amd64.deb
 92f84d9ccb8a65d31e747e1a2580faf6c5318fbd59531c5b17f9559abdb6dc49 6259 
prosody_0.10.2-1_amd64.buildinfo
 9de5a8ef8cf73814de50f436027ac3c45698e645b8a13c3ba89f75cf0d23aa30 249680 
prosody_0.10.2-1_amd64.deb
Files:
 00e974c8d720a8b4ea2ac27b0f0735cd 2359 net optional prosody_0.10.2-1.dsc
 4cb1ac0db2b739b933ded5038551d7c2 331874 net optional prosody_0.10.2.orig.tar.gz
 45621204690b30337df68e2c12617905 801 net optional 
prosody_0.10.2.orig.tar.gz.asc
 2864934a58fae82f69532623ac8bbf39 15160 net optional 
prosody_0.10.2-1.debian.tar.xz
 eb6fd18bb0301e22d757dc2bada0eb6d 46728 debug optional 
prosody-dbgsym_0.10.2-1_amd64.deb
 ad1db41a556f981be99757194ee9c8a1 6259 net optional 
prosody_0.10.2-1_amd64.buildinfo
 a05b1504e9c9d80f7bce272c4608c889 249680 net optional prosody_0.10.2-1_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEftHeo0XZoKEY1KdA4+Chwoa5Y+oFAlsQZnoACgkQ4+Chwoa5
Y+pR7w//ZO//36qLRja+6n9NjovQRlbOGyaT/t9CLvPx9k3arNq1Ix0fFuldLuzG
Qw5s+m38ThCenvgqRCNAJg5Z+CKp1zkvkr/nViVlr64pd3DQ6/JJN6+LIH4VhDOf

Processed: Re: kazam: Binding 'R' failed!

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #896550 [kazam] kazam: Binding 'R' failed!
Severity set to 'important' from 'grave'
> retitle -1 kazam does not work under Wayland
Bug #896550 [kazam] kazam: Binding 'R' failed!
Changed Bug title to 'kazam does not work under Wayland' from 'kazam: Binding 
'R' failed!'.

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

Bug#896550: kazam: Binding 'R' failed!

[James Lu]

Control: severity -1 important
Control: retitle -1 kazam does not work under Wayland

Hi everyone,

I did some digging on this issue in a VM running buster/testing + GNOME,
only to find that Kazam does not work at all on Wayland.

The keybinding errors are caused by Keybinder not supporting
Wayland[1][2], but I've also found several other problems. Some of these
can be worked around by running kazam with GDK_BACKEND=x11 set, but
others are not.

- Screenshots fail under Wayland unless GDK_BACKEND=x11 is set:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/kazam/app.py", line 567, in
cb_counter_finished
self.grabber.grab()
  File "/usr/lib/python3/dist-packages/kazam/backend/grabber.py", line
146, in grab
c_picbuf.composite(self.pixbuf, 0, 0, w - 1, h - 1,
AttributeError: 'NoneType' object has no attribute 'composite'

- Choosing to record a window under Wayland fails because libwnck only
supports X11 (worked around with GDK_BACKEND=x11):

(kazam:3789): Wnck-WARNING **: 13:08:48.693: libwnck is designed to work
in X11 only, no valid display found
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/kazam/frontend/window_select.py",
line 111, in cb_button_press_event
screen.force_update()
AttributeError: 'NoneType' object has no attribute 'force_update'

- Screen recording under Wayland shows a black screen with only the
cursor, even when GDK_BACKEND=x11 is set

In this case, no explicit errors are shown.



All of these issues are Wayland specific and do not affect GNOME on Xorg
or other X11-based desktops. I'm therefore lowering the severity.

Best,
James

[1]: https://github.com/kupferlauncher/keybinder/issues/11
[2]: https://github.com/Guake/guake/issues/1109



signature.asc
Description: OpenPGP digital signature

Bug#900528: does not install in buster

[David Bremner]

Package: elpa-ghub+
Version: 0.2.1-1
Severity: serious

postinst fails:

In ghubp-base-html-url:
ghub+.el:240:8:Warning: ‘(host (magit-get "github" "host"))’ is a malformed
function
ghub+.el:243:65:Warning: reference to free variable ‘host’
ghub+.el:745:1:Error: :condition-case must be a list of error handlers; see the 
documentation: ((ghub-404 nil))
ERROR: install script from elpa-ghub+ package failed
dpkg: error processing package elpa-ghub+ (--configure):
 installed elpa-ghub+ package post-installation script subprocess returned 
error exit status 1


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

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

Versions of packages elpa-ghub+ depends on:
ii  elpa-apiwrap0.4-1
ii  elpa-ghub   2.0.0-1
ii  emacsen-common  2.0.8

Versions of packages elpa-ghub+ recommends:
ii  emacs  47.0

elpa-ghub+ suggests no packages.

-- no debconf information

Bug#900524: prosody: CVE-2018-10847: insufficient stream header validation

[Salvatore Bonaccorso]

Source: prosody
Version: 0.9.7-2
Severity: grave
Tags: security upstream
Justification: user security hole
Control: found -1 0.10.1-1
Control: forwarded -1 https://issues.prosody.im/1147


Hi,

The following vulnerability was published for prosody.

CVE-2018-10847[0]:
insufficient stream header validation

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-10847
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10847
[1] https://issues.prosody.im/1147
[2] https://blog.prosody.im/prosody-0-10-2-security-release/

Regards,
Salvatore

Processed: prosody: CVE-2018-10847: insufficient stream header validation

[Debian Bug Tracking System]

Processing control commands:

> found -1 0.10.1-1
Bug #900524 [src:prosody] prosody: CVE-2018-10847: insufficient stream header 
validation
Marked as found in versions prosody/0.10.1-1.
> forwarded -1 https://issues.prosody.im/1147
Bug #900524 [src:prosody] prosody: CVE-2018-10847: insufficient stream header 
validation
Set Bug forwarded-to-address to 'https://issues.prosody.im/1147'.

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

Processed: gitlab: Security Release: 10.8.2, 10.7.5, and 10.6.6

[Debian Bug Tracking System]

Processing control commands:

> found -1 10.7.3+dfsg-1
Bug #900522 [src:gitlab] gitlab: Security Release: 10.8.2, 10.7.5, and 10.6.6
Marked as found in versions gitlab/10.7.3+dfsg-1.

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

Bug#900522: gitlab: Security Release: 10.8.2, 10.7.5, and 10.6.6

[Salvatore Bonaccorso]

Source: gitlab
Version: 10.6.5+dfsg-2
Severity: grave
Tags: security upstream
Justification: user security hole
Control: found -1 10.7.3+dfsg-1

Hi

There was a new gitlab security update, as per 
https://about.gitlab.com/2018/05/29/security-release-gitlab-10-dot-8-dot-2-released/

(Unfortunately, there are no CVE assigned yet, which would ease the
tracking in any case).

Regards,
Salvatore

Bug#900282: marked as done (webkitgtk FTBFS with new ICU)

[Debian Bug Tracking System]

Your message dated Thu, 31 May 2018 18:20:13 +
with message-id 
and subject line Bug#900282: fixed in webkitgtk 2.4.11-4
has caused the Debian Bug report #900282,
regarding webkitgtk FTBFS with new ICU
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.)


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

package: webkitgtk
version: 2.4.11-3
severity: serious

Webkitgtk seems to be failing to build, failures have been seen with binnmus in 
Debian and Raspbian and also on the reproducible builds service. I had a look 
at the insanely large build log from reproducible builds and found the 
following error, there are likely many others.

../Source/JavaScriptCore/API/JSStringRef.cpp:86:30: error: invalid conversion 
from 'const UChar* {aka const char16_t*}' to 'const JSChar* {aka const short 
unsigned int*}' [-fpermissive]
 return string->characters();

It seems ubuntu already have a fix 
https://launchpad.net/ubuntu/+source/webkitgtk/2.4.11-3ubuntu3 I am trying to 
build that fix in raspbian now.
--- End Message ---
--- Begin Message ---
Source: webkitgtk
Source-Version: 2.4.11-4

We believe that the bug you reported is fixed in the latest version of
webkitgtk, 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.
Alberto Garcia  (supplier of updated webkitgtk 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: Thu, 31 May 2018 19:38:40 +0200
Source: webkitgtk
Binary: libjavascriptcoregtk-1.0-0 libjavascriptcoregtk-1.0-dev 
libwebkitgtk-1.0-0 libwebkitgtk-dev libjavascriptcoregtk-3.0-0 
libjavascriptcoregtk-3.0-dev libjavascriptcoregtk-3.0-bin 
gir1.2-javascriptcoregtk-3.0 libwebkitgtk-3.0-0 libwebkitgtk-3.0-dev 
libwebkitgtk-doc gir1.2-webkit-3.0
Architecture: source
Version: 2.4.11-4
Distribution: unstable
Urgency: medium
Maintainer: Debian WebKit Maintainers 

Changed-By: Alberto Garcia 
Description:
 gir1.2-javascriptcoregtk-3.0 - JavaScript engine library from WebKitGTK+ - 
GObject introspection
 gir1.2-webkit-3.0 - Web content engine library for GTK+ - GObject 
introspection data
 libjavascriptcoregtk-1.0-0 - JavaScript engine library from WebKitGTK+
 libjavascriptcoregtk-1.0-dev - JavaScript engine library from WebKitGTK+ - 
development files
 libjavascriptcoregtk-3.0-0 - JavaScript engine library from WebKitGTK+
 libjavascriptcoregtk-3.0-bin - JavaScript engine library from WebKitGTK+ - 
command-line interpre
 libjavascriptcoregtk-3.0-dev - JavaScript engine library from WebKitGTK+ - 
development files
 libwebkitgtk-1.0-0 - Web content engine library for GTK+
 libwebkitgtk-3.0-0 - Web content engine library for GTK+
 libwebkitgtk-3.0-dev - Web content engine library for GTK+ - development files
 libwebkitgtk-dev - Web content engine library for GTK+ - development files
 libwebkitgtk-doc - Web content engine library for GTK+ - documentation
Closes: 900282
Changes:
 webkitgtk (2.4.11-4) unstable; urgency=medium
 .
   * debian/patches/fix-build-icu.patch:
 + Fix build with ICU 5.91 (Closes: #900282).
   * debian/patches/gtk-doc-fix[123].patch:
 + Cherry pick some upstream patches to be able to build with recent
   versions of gtk-doc.
   * debian/rules:
 + Build with -Wno-expansion-to-defined in order to reduce the large
   amount of warnings with GCC 7.
 + Don't call dh_install for the -dbg packages, they have all been
   replaced with their -dbgsym equivalents.
 + Include /usr/share/dpkg/architecture.mk instead of defining all
   DEB_* variables.
   * debian/control:
 + Remove all 'Priority' fields from the binary packages. The 'extra'
   priority is deprecated and all packages are 'optional' now.
 + Update Vcs fields to point at https://salsa.debian.org/
 + Use https version of the upstream home page.
   * Bump debhelper compat to 10:
 + debian/compat:
   - Update version number:
 + debian/control:
   - Bump build dependency on debhelper.
   - Remove build dependencies on dh-autoreconf and autotools-dev.

Processed: [bts-link] source package src:ruby-slim

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:ruby-slim
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #895500 (http://bugs.debian.org/895500)
> # Bug title: ruby-slim FTBFS with ruby-tilt 2.0.8-1
> #  * https://github.com/slim-template/slim/issues/742
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 895500 + fixed-upstream
Bug #895500 [src:ruby-slim] ruby-slim FTBFS with ruby-tilt 2.0.8-1
Added tag(s) fixed-upstream.
> usertags 895500 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:h5py

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:h5py
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #898526 (http://bugs.debian.org/898526)
> # Bug title: h5py: FTBFS - FAIL: test_out_of_order_offsets
> #  * https://github.com/h5py/h5py/issues/1037
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 898526 + fixed-upstream
Bug #898526 [src:h5py] h5py: FTBFS - FAIL: test_out_of_order_offsets
Added tag(s) fixed-upstream.
> usertags 898526 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:blitz++

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:blitz++
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #85 (http://bugs.debian.org/85)
> # Bug title: blitz++: ftbfs with GCC-7
> #  * https://github.com/blitzpp/blitz/issues/17
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 85 + fixed-upstream
Bug #85 [src:blitz++] blitz++: ftbfs with GCC-7
Added tag(s) fixed-upstream.
> usertags 85 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package general

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package general
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #694308 (http://bugs.debian.org/694308)
> # Bug title: A lot of type 1 fonts include Adobe all right reserved code
> #  * https://github.com/adobe-type-tools/afdko/issues/172
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 694308 + fixed-upstream
Bug #694308 [general] A lot of type 1 fonts include Adobe all right reserved 
code
Added tag(s) fixed-upstream.
> usertags 694308 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package pymediainfo

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package pymediainfo
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #896313 (http://bugs.debian.org/896313)
> # Bug title: python-pymediainfo: pymediainfo fails to import
> #  * https://github.com/sbraz/pymediainfo/pull/50
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 896313 + fixed-upstream
Bug #896313 [python-pymediainfo] python-pymediainfo: pymediainfo fails to import
Added tag(s) fixed-upstream.
> usertags 896313 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:ruby-riot

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:ruby-riot
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #888171 (http://bugs.debian.org/888171)
> # Bug title: ruby-riot: FTBFS on ruby2.5: expected "\"hope\"", not "hope"
> #  * https://github.com/thumblemonks/riot/pull/54
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 888171 + fixed-upstream
Bug #888171 [src:ruby-riot] ruby-riot: FTBFS on ruby2.5: expected "\"hope\"", 
not "hope"
Added tag(s) fixed-upstream.
> usertags 888171 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#900517: courier-imap: Doesn't start: imapd/etc/init.d/courier-imap: xrealloc: .././print_cmd.c:1557: cannot allocate 512 bytes (376832 bytes allocated)

[Mehdi Amin]

Package: courier-imap
Version: 4.15-1.6
Severity: grave
Justification: renders package unusable

Dear Maintainer,

   * What led up to the situation?

  apt-get update
  apt-get -y -V upgrade
  apt-get -V -y install ntpdate wget sudo dnsutils aptitude apt-utils 
lsb-release bash-completion
  aptitude -V -y install telnet psmisc fuse tcpdump open-vm-tools 
iptables-persistent
  aptitude -V -y install putty-tools p7zip p7zip-full pbzip2 pigz 
apt-transport-https ntpdate
  aptitude -y -V install heirloom-mailx apt-show-versions curl make 
mysql-client sshpass bc unrar-free
  aptitude install -V -P courier-imap courier-pop courier-webadmin 
couriergraph

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

 Use the latest Debian 8.x stable version with latest updates till May 
31,2018
 Increase RAM upto 32GB - was ineffective
 Increase CPU core upto 4 - was ineffective
 Our filesystem is XFS (LVM). Might not be related

   * What was the outcome of this action?

 Starting Courier IMAP server: imapd/etc/init.d/courier-imap: xrealloc: 
.././print_cmd.c:1557: cannot allocate 512 bytes (376832 bytes allocated)

   * What outcome did you expect instead?

 Start service normaly.



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

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

Versions of packages courier-imap depends on:
ii  courier-authlib 0.66.1-1+b1
ii  courier-base0.73.1-1.6
ii  debconf 1.5.56+deb8u1
ii  libc6   2.19-18+deb8u10
ii  libfam0 2.7.0-17.1
ii  libgdbm31.8.3-13.1
ii  postfix [mail-transport-agent]  2.11.3-1+deb8u2

courier-imap recommends no packages.

Versions of packages courier-imap suggests:
pn  courier-doc   
pn  courier-imap-ssl  
ii  heirloom-mailx [imap-client]  12.5-4

-- no debconf information

Processed: [bts-link] source package libyaml-libyaml-perl

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package libyaml-libyaml-perl
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #862373 (http://bugs.debian.org/862373)
> # Bug title: libyaml-libyaml-perl: Unconditionally instantiates objects from 
> yaml data
> #  * https://github.com/ingydotnet/yaml-pm/issues/176
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 862373 + fixed-upstream
Bug #862373 [libyaml-libyaml-perl] libyaml-libyaml-perl: Unconditionally 
instantiates objects from yaml data
Added tag(s) fixed-upstream.
> usertags 862373 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:flif

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:flif
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #896109 (http://bugs.debian.org/896109)
> # Bug title: flif FTBFS: bouncing-ball-frame01.png is not the same image as 
> decoded-test-frame-000.pam
> #  * https://github.com/FLIF-hub/FLIF/issues/498
> #  * remote status changed: (?) -> open
> usertags 896109 + status-open
There were no usertags set.
Usertags are now: status-open.
> # remote status report for #898406 (http://bugs.debian.org/898406)
> # Bug title: flif: CVE-2018-10971
> #  * https://github.com/FLIF-hub/FLIF/issues/501
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 898406 + fixed-upstream
Bug #898406 [src:flif] flif: CVE-2018-10971
Warning: Unknown package 'src:flif'
Added tag(s) fixed-upstream.
Warning: Unknown package 'src:flif'
> usertags 898406 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> # remote status report for #898407 (http://bugs.debian.org/898407)
> # Bug title: flif: CVE-2018-10972
> #  * https://github.com/FLIF-hub/FLIF/issues/503
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 898407 + fixed-upstream
Bug #898407 [src:flif] flif: CVE-2018-10972
Warning: Unknown package 'src:flif'
Added tag(s) fixed-upstream.
Warning: Unknown package 'src:flif'
> usertags 898407 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:docker.io

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:docker.io
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #900140 (http://bugs.debian.org/900140)
> # Bug title: docker.io: CVE-2017-16539: The DefaultLinuxSpec function does 
> not block /proc/scsi pathnames
> #  * https://github.com/moby/moby/pull/35399
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 900140 + fixed-upstream
Bug #900140 [src:docker.io] docker.io: CVE-2017-16539: The DefaultLinuxSpec 
function does not block /proc/scsi pathnames
Added tag(s) fixed-upstream.
> usertags 900140 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:node-define-property

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:node-define-property
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #892656 (http://bugs.debian.org/892656)
> # Bug title: node-define-property: FTBFS and Debci failure
> #  * https://github.com/jonschlinkert/define-property/issues/3
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 892656 + fixed-upstream
Bug #892656 [src:node-define-property] node-define-property: FTBFS and Debci 
failure
Added tag(s) fixed-upstream.
> usertags 892656 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:mysql-workbench

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:mysql-workbench
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #867943 (http://bugs.debian.org/867943)
> # Bug title: mysql-workbench: Build-Depends on deprecated libgnome-keyring-dev
> #  * http://bugs.mysql.com/bug.php?format=xml=89898
> #  * remote status changed: (?) -> Closed
> #  * closed upstream
> tags 867943 + fixed-upstream
Bug #867943 [src:mysql-workbench] mysql-workbench: Build-Depends on deprecated 
libgnome-keyring-dev
Added tag(s) fixed-upstream.
> usertags 867943 + status-Closed
There were no usertags set.
Usertags are now: status-Closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:tripleo-heat-templates

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:tripleo-heat-templates
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #900176 (http://bugs.debian.org/900176)
> # Bug title: tripleo-heat-templates: CVE-2017-12155
> #  * https://bugs.launchpad.net/bugs/1720787
> #  * remote status changed: (?) -> Fix-Released
> #  * closed upstream
> tags 900176 + fixed-upstream
Bug #900176 [src:tripleo-heat-templates] tripleo-heat-templates: CVE-2017-12155
Added tag(s) fixed-upstream.
> usertags 900176 + status-Fix-Released
There were no usertags set.
Usertags are now: status-Fix-Released.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:ruby-net-ssh

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:ruby-net-ssh
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #888163 (http://bugs.debian.org/888163)
> # Bug title: ruby-net-ssh: FTBFS on ruby2.5: OpenSSL::Digest::DSS1
> #  * https://github.com/net-ssh/net-ssh/issues/503
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 888163 + fixed-upstream
Bug #888163 [src:ruby-net-ssh] ruby-net-ssh: FTBFS on ruby2.5: 
OpenSSL::Digest::DSS1
Added tag(s) fixed-upstream.
> usertags 888163 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:ruby-rails-admin

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:ruby-rails-admin
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #900178 (http://bugs.debian.org/900178)
> # Bug title: ruby-rails-admin: CVE-2017-12098
> #  * https://github.com/sferik/rails_admin/issues/2985
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 900178 + fixed-upstream
Bug #900178 [src:ruby-rails-admin] ruby-rails-admin: CVE-2017-12098
Added tag(s) fixed-upstream.
> usertags 900178 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> owner 892508 !
Bug #892508 [src:ruby-psych] ruby-psych FTBFS with Ruby 2.5
Owner recorded as Miguel Landaeta .
> block 895837 by 900515
Bug #895837 [src:jruby] jruby: Please package 9.1.16.0 or more recent releases
895837 was blocked by: 900376
895837 was blocking: 893244 895778
Added blocking bug(s) of 895837: 900515
> block 895837 by 900516
Bug #895837 [src:jruby] jruby: Please package 9.1.16.0 or more recent releases
895837 was blocked by: 900515 900376
895837 was blocking: 893244 895778
Added blocking bug(s) of 895837: 900516
> thanks
Stopping processing here.

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

Processed: Re: Bug#900460: ephoto: fails to start

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo
Bug #900460 [ephoto] ephoto: fails to start
Added tag(s) moreinfo.

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

Bug#900460: ephoto: fails to start

[Ross Vandegrift]

Control: tags -1 moreinfo

Hello,

Can you provide the output of "dpkg -l | grep libevas1-engine"?  It
looks like ephoto can't find a working evas engine.  Probably you're
using X11 but the dependencies only installed the wayland engine, or
vice versa.

Thanks,
Ross

On Thu, May 31, 2018 at 03:43:25PM +0900, Norbert Preining wrote:
> Package: ephoto
> Version: 1.5-1
> Severity: grave
> Justification: renders package unusable
> 
> Bot invocations
>   ephoto
> or
>   ephoto foo.jpg
> end with
> 
> ERR<25953>:ecore_evas lib/elementary/efl_ui_win.c:5005 
> _elm_win_finalize_internal() Cannot create window.
> ## Copy & Paste the below (until EOF) into a terminal, then hit Enter
> 
> eina_btlog << EOF
> /usr/lib/x86_64-linux-gnu/libeina.so.1 0x7fb89cd406cc 0x7fb89cd19000
> /usr/lib/x86_64-linux-gnu/libeina.so.1 0x7fb89cd413f1 0x7fb89cd19000
> /usr/lib/x86_64-linux-gnu/libeina.so.1 0x7fb89cd427c3 0x7fb89cd19000
> /usr/lib/x86_64-linux-gnu/libelementary.so.1   0x7fb89b38956c 0x7fb89b109000
> /usr/lib/x86_64-linux-gnu/libelementary.so.1   0x7fb89b38b470 0x7fb89b109000
> /usr/lib/x86_64-linux-gnu/libeo.so.1   0x7fb89b8b630e 0x7fb89b8a6000
> /usr/lib/x86_64-linux-gnu/libeo.so.1   0x7fb89b8ae9ac 0x7fb89b8a6000
> /usr/lib/x86_64-linux-gnu/libelementary.so.1   0x7fb89b385142 0x7fb89b109000
> /usr/bin/ephoto0x55b70128b564 0x55b70126f000
> /usr/bin/ephoto0x55b701278a4f 0x55b70126f000
> /usr/bin/ephoto0x55b70127873c 0x55b70126f000
> /lib/x86_64-linux-gnu/libc.so.60x7fb898e3ba87 0x7fb898e1a000
> /usr/bin/ephoto0x55b70127877a 0x55b70126f000
> EOF
> 
> ERR<25953>:eo lib/eo/eo.c:949 _efl_add_internal_end() Object of class 
> 'Efl.Ui.Win' - Not all of the object constructors have been executed.
> ## Copy & Paste the below (until EOF) into a terminal, then hit Enter
> 
> eina_btlog << EOF
> /usr/lib/x86_64-linux-gnu/libeina.so.1 0x7fb89cd406cc 0x7fb89cd19000
> /usr/lib/x86_64-linux-gnu/libeina.so.1 0x7fb89cd413f1 0x7fb89cd19000
> /usr/lib/x86_64-linux-gnu/libeina.so.1 0x7fb89cd427c3 0x7fb89cd19000
> /usr/lib/x86_64-linux-gnu/libeo.so.1   0x7fb89b8aea8c 0x7fb89b8a6000
> /usr/lib/x86_64-linux-gnu/libelementary.so.1   0x7fb89b385142 0x7fb89b109000
> /usr/bin/ephoto0x55b70128b564 0x55b70126f000
> /usr/bin/ephoto0x55b701278a4f 0x55b70126f000
> /usr/bin/ephoto0x55b70127873c 0x55b70126f000
> /lib/x86_64-linux-gnu/libc.so.60x7fb898e3ba87 0x7fb898e1a000
> /usr/bin/ephoto0x55b70127877a 0x55b70126f000
> EOF
> 
> ERR<25953>:evas_main lib/evas/canvas/evas_object_smart.c:646 
> _efl_canvas_group_efl_object_destructor() efl_canvas_group_del() was not 
> called on this object: 0x400105da (Efl.Ui.Win)
> ## Copy & Paste the below (until EOF) into a terminal, then hit Enter
> 
> eina_btlog << EOF
> /usr/lib/x86_64-linux-gnu/libeina.so.1 0x7fb89cd406cc 0x7fb89cd19000
> /usr/lib/x86_64-linux-gnu/libeina.so.1 0x7fb89cd413f1 0x7fb89cd19000
> /usr/lib/x86_64-linux-gnu/libeina.so.1 0x7fb89cd427c3 0x7fb89cd19000
> /usr/lib/x86_64-linux-gnu/libevas.so.1 0x7fb89c71a237 0x7fb89c689000
> /usr/lib/x86_64-linux-gnu/libeo.so.1   0x7fb89b8b61ea 0x7fb89b8a6000
> /usr/lib/x86_64-linux-gnu/libeo.so.1   0x7fb89b8b61ea 0x7fb89b8a6000
> /usr/lib/x86_64-linux-gnu/libelementary.so.1   0x7fb89b36ee44 0x7fb89b109000
> /usr/lib/x86_64-linux-gnu/libeo.so.1   0x7fb89b8b61ea 0x7fb89b8a6000
> /usr/lib/x86_64-linux-gnu/libeo.so.1   0x7fb89b8b61ea 0x7fb89b8a6000
> /usr/lib/x86_64-linux-gnu/libeo.so.1   0x7fb89b8ae8a4 0x7fb89b8a6000
> /usr/lib/x86_64-linux-gnu/libeo.so.1   0x7fb89b8b5642 0x7fb89b8a6000
> /usr/lib/x86_64-linux-gnu/libeo.so.1   0x7fb89b8aeaa7 0x7fb89b8a6000
> /usr/lib/x86_64-linux-gnu/libelementary.so.1   0x7fb89b385142 0x7fb89b109000
> /usr/bin/ephoto0x55b70128b564 0x55b70126f000
> /usr/bin/ephoto0x55b701278a4f 0x55b70126f000
> /usr/bin/ephoto0x55b70127873c 0x55b70126f000
> /lib/x86_64-linux-gnu/libc.so.60x7fb898e3ba87 0x7fb898e1a000
> /usr/bin/ephoto0x55b70127877a 0x55b70126f000
> EOF
> 
> 
> 
> 
> 
> -- System Information:
> Debian Release: buster/sid
>   APT prefers unstable-debug
>   APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 4.16.11 (SMP w/8 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 ephoto depends on:
> ii  libc6 2.27-3
> ii  libecore-con1 1.20.7-4
> ii  libecore-evas11.20.7-4
> ii  libecore-file11.20.7-4
> ii  libecore-imf1 1.20.7-4
> ii  libecore-input1   1.20.7-4
> ii  libecore-ipc1 1.20.7-4
> ii  libecore1 1.20.7-4
> ii  libedje1  1.20.7-4
> ii  libeet1   1.20.7-4
> ii  

Processed: [bts-link] source package src:ruby-fakefs

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:ruby-fakefs
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #888186 (http://bugs.debian.org/888186)
> # Bug title: ruby-fakefs: FTBFS on ruby2.5: pread method is not available in 
> File :(
> #  * https://github.com/fakefs/fakefs/issues/390
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 888186 + fixed-upstream
Bug #888186 [src:ruby-fakefs] ruby-fakefs: FTBFS on ruby2.5: pread method is 
not available in File :(
Added tag(s) fixed-upstream.
> usertags 888186 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#900511: libcurl4 Conflicts: libcurl3

[Marvin Renich]

Package: libcurl4
Version: 7.60.0-2
Severity: serious

libcurl4 conflicts with libcurl3, which violates the stated purpose of
the "must" clause at Policy 8.1 (to allow multiple versions of a shared
library to be co-installable), even though it doesn't violate the letter
of the must (binary package name must change when SONAME changes).
Without the second sentence at Policy 8.1, the MUST requirement serves
no purpose, so I have given this severity serious.

This means that, regardless of what Debian does with packages depending
on libcurl, libcurl4 cannot be installed if the user has third party or
home brew software that requires libcurl3.

I found this because I have netsurf-gtk installed, which Depends:
libcurl3.  netsurf-gtk is currently the same version in stable and
unstable, but has been removed from testing.

...Marvin

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

Kernel: Linux 4.15.0-2-amd64 (SMP w/8 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: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Bug#898561: marked as done (libmarc-transform-perl: FTBFS with libyaml-perl >= 1.25-1 (test failures))

[Debian Bug Tracking System]

Your message dated Thu, 31 May 2018 15:20:17 +
with message-id 
and subject line Bug#898561: fixed in libmarc-transform-perl 0.003006-3
has caused the Debian Bug report #898561,
regarding libmarc-transform-perl: FTBFS with libyaml-perl >= 1.25-1 (test 
failures)
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.)


-- 
898561: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898561
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libmarc-transform-perl
Version: 0.003006-2
Severity: serious
Tags: upstream buster sid
Justification: fails to build from source

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

libmarc-transform-perl's testsuite fails, both during build and
autopkgtest, with libyaml-perl >= 1.25-1:


perl Build test --verbose 1
Hexadecimal number > 0x non-portable at (eval 28) line 1.
Number found where operator expected at (eval 29) line 8, near ""I want) 
{$boolcond=1;$boolcondint=1; eval{ create("605"
(Missing operator before 605?)
String found where operator expected at (eval 29) line 8, near "605",{""
(Missing operator before ",{"?)
Bareword found where operator expected at (eval 29) line 8, near "",{"a"
(Missing operator before a?)
String found where operator expected at (eval 29) line 8, near "a"=>""
Hexadecimal number > 0x non-portable at (eval 58) line 1.
Number found where operator expected at (eval 59) line 8, near ""I want) 
{$boolcond=1;$boolcondint=1; eval{ create("605"
(Missing operator before 605?)
String found where operator expected at (eval 59) line 8, near "605",{""
(Missing operator before ",{"?)
Bareword found where operator expected at (eval 59) line 8, near "",{"a"
(Missing operator before a?)
String found where operator expected at (eval 59) line 8, near "a"=>""

#   Failed test ''
#   at t/test.t line 177.
#  got: 
'optionnalaleader006:UTF-8||007:controlfield_content8b||008:controlfield_content8a||008:controlfield_content8b||106:
  |a:VaLuE||401:  |b:new value of the 401 conditions field||501:  
|a:foao|a:foo|b:baoar|b:update only the first b in condition's field 
501|c:updated value of all c in condition's field||501:  |c:1||502:  |a:I want 
"$"||502:  |a:this is the value of a subfield of a new 502 field||503:  
|a:babar|a:fee|b:mandatory b in condition's field||504:  |a:updated value of 
all 504a if exists|a:updated value of all 504a if exists||600:  |a:a 
string|a:first a subfield of this new 600 field|a:second a subfield of this new 
600 field|b:the 600b value||602: 2|a:a402a2||602:1 |a:a402a1||604:  
|a:foo|a:update only the first a in 604|b:openbar|c:New York||700:  |a:the a 
subfield of this mandatory 700 
field|b:beberoptionnalaleader006:UTF-8||007:controlfield_content8b||008:controlfield_content8a||008:controlfield_content8b||106:
  |a:VaLuE||401:  |b:new value of the 401 conditions field||501:  
|a:foao|a:foo|b:baoar|b:update only the first b in condition's field 
501|c:updated value of all c in condition's field||501:  |c:1||502:  |a:I want 
"$"||502:  |a:this is the value of a subfield of a new 502 field||503:  
|a:babar|a:fee|b:mandatory b in condition's field||504:  |a:updated value of 
all 504a if exists|a:updated value of all 504a if exists||600:  |a:a 
string|a:first a subfield of this new 600 field|a:second a subfield of this new 
600 field|b:the 600b value||602: 2|a:a402a2||602:1 |a:a402a1||604:  
|a:foo|a:update only the first a in 604|b:openbar|c:New York||700:  |a:the a 
subfield of this mandatory 700 field|b:beber'
# expected: 
'optionnalaleader006:UTF-8||007:controlfield_content8b||008:controlfield_content8a||008:controlfield_content8b||106:
  |a:VaLuE||401:  |b:new value of the 401 conditions field||501:  
|a:foao|a:foo|b:baoar|b:update only the first b in condition's field 
501|c:updated value of all c in condition's field||501:  |c:1||502:  |a:I want 
"$"||502:  |a:this is the value of a subfield of a new 502 field||503:  
|a:babar|a:fee|b:mandatory b in condition's field||504:  |a:updated value of 
all 504a if exists|a:updated value of all 504a if exists||600:  |a:a 
string|a:first a subfield of this new 600 field|a:second a subfield of this new 
600 field|b:the 600b value||602: 2|a:a402a2||602:1 |a:a402a1||604:  
|a:foo|a:update only the first a in 604|b:openbar|c:New York||605:  |a:"I want 
"$"" contain a $ sign||700:  |a:the a subfield of this mandatory 700 
field|b:beberoptionnalaleader006:UTF-8||007:controlfield_content8b||008:controlfield_content8a||008:controlfield_content8b||106:
  |a:VaLuE||401:  |b:new value 

Bug#899727: marked as done (wxwidgets3.0: Invalid maintainer address freewx-ma...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Thu, 31 May 2018 14:50:46 +
with message-id 
and subject line Bug#899727: fixed in wxwidgets3.0 3.0.4+dfsg-4
has caused the Debian Bug report #899727,
regarding wxwidgets3.0: Invalid maintainer address 
freewx-ma...@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.)


-- 
899727: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899727
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:wxwidgets3.0
Version: 3.0.4+dfsg-3
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of wxwidgets3.0,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package wxwidgets3.0 since the list address
freewx-ma...@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
freewx-ma...@lists.alioth.debian.org is 3.

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: wxwidgets3.0
Source-Version: 3.0.4+dfsg-4

We believe that the bug you reported is fixed in the latest version of
wxwidgets3.0, 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.
Scott Talbert  (supplier of updated wxwidgets3.0 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, 30 May 2018 23:39:39 -0400
Source: wxwidgets3.0
Binary: libwxbase3.0-0v5 libwxbase3.0-dev libwxgtk3.0-0v5 libwxgtk3.0-dev 
libwxgtk-media3.0-0v5 libwxgtk-media3.0-dev libwxgtk3.0-gtk3-0v5 
libwxgtk3.0-gtk3-dev libwxgtk-media3.0-gtk3-0v5 libwxgtk-media3.0-gtk3-dev 
libwxgtk-webview3.0-gtk3-0v5 libwxgtk-webview3.0-gtk3-dev wx-common 
wx3.0-headers wx3.0-i18n wx3.0-examples wx3.0-doc
Architecture: source
Version: 3.0.4+dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: wxWidgets Maintainers 
Changed-By: Scott Talbert 
Description:
 libwxbase3.0-0v5 - wxBase library (runtime) - non-GUI support classes of 
wxWidgets t
 libwxbase3.0-dev - wxBase library (development) - non-GUI support classes of 
wxWidge
 libwxgtk-media3.0-0v5 - wxWidgets Cross-platform C++ GUI toolkit (GTK+ media 
library runt
 libwxgtk-media3.0-dev - wxWidgets Cross-platform C++ GUI toolkit (GTK+ media 
library deve
 libwxgtk-media3.0-gtk3-0v5 - wxWidgets Cross-platform C++ GUI toolkit (GTK+ 3 
media library ru
 libwxgtk-media3.0-gtk3-dev - wxWidgets Cross-platform C++ GUI toolkit (GTK+ 3 
media library de
 libwxgtk-webview3.0-gtk3-0v5 - wxWidgets Cross-platform C++ GUI toolkit (GTK+ 
3 webview library
 libwxgtk-webview3.0-gtk3-dev - 

Bug#898561: libmarc-transform-perl: FTBFS with libyaml-perl >= 1.25-1 (test failures)

[gregor herrmann]

On Thu, 31 May 2018 13:57:04 +0200, Tina Müller wrote:

> It seems that MARC::Transform itself is fine, and only its test suite
> needs a tiny patch. Nodes containing '#' just need to be quoted.
> I attached the patch to this email.

Thanks!
Patch applied, package uploaded.


Cheers,
greor

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


signature.asc
Description: Digital Signature

Bug#898591: marked as done (lptools: Intent to remove from Debian)

[Debian Bug Tracking System]

Your message dated Thu, 31 May 2018 10:39:01 -0400
with message-id 

and subject line Re: Bug#898591: lptools: Intent to remove from Debian
has caused the Debian Bug report #898591,
regarding lptools: Intent to remove from Debian
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.)


-- 
898591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898591
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lptools
Version: 0.2.0-2
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster
X-Debbugs-CC: x...@debian.org, jel...@debian.org

lptools depends on the unmaintained pygtk which the Debian GNOME team is trying 
to remove from Debian.

It looks like lptools itself is unmaintained. Therefore, I intend to file a 
removal bug for lptools. Please reply immediately to let me know if you approve 
or object.

References
--
https://bugs.debian.org/885518
https://lists.debian.org/debian-devel/2018/02/msg00169.html

Thanks,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
On Fri, May 25, 2018 at 5:17 PM, Jelmer Vernooij  wrote:
> On Mon, May 14, 2018 at 09:14:47AM -0400, Jeremy Bicha wrote:
>> On Mon, May 14, 2018 at 7:30 AM, Jelmer Vernooij  wrote:
>> > On Sun, May 13, 2018 at 08:25:39PM -0400, Jeremy Bicha wrote:
>> >> lptools depends on the unmaintained pygtk which the Debian GNOME team is 
>> >> trying to remove from Debian.
>> >>
>> >> It looks like lptools itself is unmaintained. Therefore, I intend to file 
>> >> a removal bug for lptools. Please reply immediately to let me know if you 
>> >> approve or object.
>> > Huh, what suggests it's unmaintained? It hasn't been changed in the
>> > last couple of years, but it's also been functioning well and there
>> > are no open critical bugs against it.
>> >
>> > There are just two scripts (out of 18) in lptools that use pygtk. We
>> > could probably just drop those.
>>
>> There was an RC bug [1] that resulted in lptools being removed from
>> Testing since January, but that bug was recently downgraded and
>> lptools re-entered Testing.
>>
>> Ubuntu also has some updates that should probably be in the Debian package 
>> too.
>>
>> Anyway, I'll go ahead and close this bug since we won't actually be
>> removing pygtk from Debian until Bullseye so you have some time.
>
> It looks like the BTS didn't pick up the email to -done, so retrying..

And once more, with the correct bug number. Sorry about that!

Jeremy Bicha--- End Message ---

Bug#900497: libgl1-mesa-dri: Causes random freezes in plasmashell

[Vivia Nikolaidou]

Package: libgl1-mesa-dri
Severity: critical
Tags: patch upstream
Justification: breaks unrelated software

Dear Maintainer,

Currently, with the mesa driver and xorg 1.20, plasmashell randomly freezes 
every few seconds.

The bug has been reported as:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900352
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900149

but it is actually a bug in mesa. It is fixed by this upstream commit:
https://cgit.freedesktop.org/mesa/mesa/commit/?id=fe2edb25dd5628c395a65b60998f11e839d2b458

I just applied said patch locally and rebuilt mesa, and I can confirm that it 
fixes the issue.

Best regards,

Vivia Nikolaidou

-- Package-specific info:
glxinfo:

name of display: :0
display: :0  screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
server glx extensions:
GLX_ARB_create_context, GLX_ARB_create_context_no_error, 
GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, 
GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_multisample, 
GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, 
GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, 
GLX_EXT_import_context, GLX_EXT_libglvnd, GLX_EXT_no_config_context, 
GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, 
GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_OML_swap_method, 
GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, 
GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, 
GLX_SGI_swap_control
client glx vendor string: Mesa Project and SGI
client glx version string: 1.4
client glx extensions:
GLX_ARB_context_flush_control, GLX_ARB_create_context, 
GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, 
GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, 
GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_buffer_age, 
GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, 
GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, 
GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, 
GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, 
GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, 
GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, 
GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, 
GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, 
GLX_SGI_swap_control, GLX_SGI_video_sync
GLX version: 1.4
GLX extensions:
GLX_ARB_create_context, GLX_ARB_create_context_profile, 
GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, 
GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, 
GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, 
GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, 
GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, 
GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, 
GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, 
GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, 
GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, 
GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, 
GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, 
GLX_SGI_swap_control, GLX_SGI_video_sync
Extended renderer info (GLX_MESA_query_renderer):
Vendor: Intel Open Source Technology Center (0x8086)
Device: Mesa DRI Intel(R) HD Graphics 5300 (Broadwell GT2)  (0x161e)
Version: 18.1.0
Accelerated: yes
Video memory: 3072MB
Unified memory: yes
Preferred profile: core (0x1)
Max core profile version: 4.5
Max compat profile version: 3.0
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.1
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 5300 (Broadwell GT2) 
OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.1.0
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
GL_3DFX_texture_compression_FXT1, GL_AMD_conservative_depth, 
GL_AMD_draw_buffers_blend, GL_AMD_seamless_cubemap_per_texture, 
GL_AMD_shader_trinary_minmax, GL_AMD_vertex_shader_layer, 
GL_AMD_vertex_shader_viewport_index, GL_ANGLE_texture_compression_dxt3, 
GL_ANGLE_texture_compression_dxt5, GL_APPLE_object_purgeable, 
GL_ARB_ES2_compatibility, GL_ARB_ES3_1_compatibility, 
GL_ARB_ES3_2_compatibility, GL_ARB_ES3_compatibility, 
GL_ARB_arrays_of_arrays, GL_ARB_base_instance, GL_ARB_blend_func_extended, 
GL_ARB_buffer_storage, GL_ARB_clear_buffer_object, GL_ARB_clear_texture, 
GL_ARB_clip_control, GL_ARB_compressed_texture_pixel_storage, 
GL_ARB_compute_shader, GL_ARB_conditional_render_inverted, 

Bug#899838: gst-fluendo-mp3: Invalid maintainer address pkg-gstreamer-maintain...@lists.alioth.debian.org

[Iain Lane]

retitle 899838 RM: gst-fluendo-mp3: ROM; Obsolete - superseded by mpg123 in 
gstreamer1.0-plugins-good
reassign 899838 ftp.debian.org
thanks

Hi,

On Thu, May 24, 2018 at 09:43:58AM +0200, Christoph Biedl wrote:
> […]
> 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.

Thanks for the bug.

We think this package should instead be removed - it's not needed any
more with current gstreamer 1.0.

Cheers,

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]


signature.asc
Description: PGP signature

Processed: Re: Bug#899838: gst-fluendo-mp3: Invalid maintainer address pkg-gstreamer-maintain...@lists.alioth.debian.org

[Debian Bug Tracking System]

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

> retitle 899838 RM: gst-fluendo-mp3: ROM; Obsolete - superseded by mpg123 in 
> gstreamer1.0-plugins-good
Bug #899838 [src:gst-fluendo-mp3] gst-fluendo-mp3: Invalid maintainer address 
pkg-gstreamer-maintain...@lists.alioth.debian.org
Changed Bug title to 'RM: gst-fluendo-mp3: ROM; Obsolete - superseded by mpg123 
in gstreamer1.0-plugins-good' from 'gst-fluendo-mp3: Invalid maintainer address 
pkg-gstreamer-maintain...@lists.alioth.debian.org'.
> reassign 899838 ftp.debian.org
Bug #899838 [src:gst-fluendo-mp3] RM: gst-fluendo-mp3: ROM; Obsolete - 
superseded by mpg123 in gstreamer1.0-plugins-good
Bug reassigned from package 'src:gst-fluendo-mp3' to 'ftp.debian.org'.
No longer marked as found in versions gst-fluendo-mp3/0.10.32.debian-1.
Ignoring request to alter fixed versions of bug #899838 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#900443: [Pkg-emacsen-addons] Bug#900443: error: Unable to activate package ‘use-package’. Required package ‘bind-key-1.0’ is unavailable

[David Bremner]

Axel Beckert  writes:

>
> ... and replacing emacs-gtk from experimental again with emacs25 from
> unstable made both errors go away, I assume that's an issue with
> emacs(-gtk) from experimental.
>
> Reassigning accordingly.

I haven't had time to investigate, but it's quite possibly bugs in two
different addons.  We're transitioning to unversioned emacs packages,
and some elpa-foo packages may need a rebuild with current dh-elpa to
handle that. elpa-powerline looks particularly likely to be one of those
since there are no uploads since stretch was released.

d

Bug#898561: libmarc-transform-perl: FTBFS with libyaml-perl >= 1.25-1 (test failures)

[Tina Müller]

Hi,

It seems that MARC::Transform itself is fine, and only its test suite
needs a tiny patch. Nodes containing '#' just need to be quoted.

I attached the patch to this email.
I also wanted to post on
https://rt.cpan.org/Public/Bug/Display.html?id=125307
but it seems unreachable at the moment.

cheers,
tinadiff --git a/t/test.t b/t/test.t
index d742771..387c668 100644
--- a/t/test.t
+++ b/t/test.t
@@ -97,7 +97,7 @@ create :
   b : the 600b value
 execute : \()
 ---
-condition : $f502a eq "I want #_dbquote_##_dollars_##_dbquote_#"
+condition : \'$f502a eq "I want #_dbquote_##_dollars_##_dbquote_#"\'
 create :
  f605a : "#_dbquote_#$f502a#_dbquote_# contain a #_dollars_# sign"
 ---
@@ -549,7 +549,7 @@ $record17->insert_fields_ordered( MARC::Field->new( '501', '', '', 'a' => 'I wan
 #print "--init record--\n". $record17->as_formatted;
 my $yaml17 = '
 ---
-condition : $f501a eq "I want #_dbquote_##_dollars_##_dbquote_#"
+condition : \'$f501a eq "I want #_dbquote_##_dollars_##_dbquote_#"\'
 create :
  f604a : "#_dbquote_#$f501a#_dbquote_# contain a #_dollars_# sign"
 ';

Bug#900486: python-pydap: FTBFS and Debci failure with NumPy 1.14

[Graham Inggs]

Source: python-pydap
Version: 3.2.2+ds1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: needs-update

Hi Maintainer

Since the recent upload of python-numpy on 2018-05-05, python-pydap has 
been failing its autopkgtests [1] and has now also started to FTBFS in

unstable [2] with several errors similar to the following:

return obj.view(dtype=(self.dtype.type, obj.dtype))
  /usr/lib/python3/dist-packages/numpy/core/records.py:513: 
FutureWarning: Numpy has detected that you may be viewing or writing to 
an array returned by selecting multiple fields in a structured array.


  This code may break in numpy 1.15 because this will return a view 
instead of a copy -- see release notes for details.

return obj.view(dtype=(self.dtype.type, obj.dtype))

-- Docs: http://doc.pytest.org/en/latest/warnings.html
== 2 tests deselected 
==
= 7 failed, 343 passed, 7 skipped, 2 deselected, 222 warnings in 5.68 
seconds ==
E: pybuild pybuild:336: test: plugin distutils failed with: exit code=1: 
cd /build/1st/python-pydap-3.2.2+ds1/.pybuild/cpython3_3.6_pydap/build; 
python3.6 -m pytest -k "not server"
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.6 
returned exit code 13

make: *** [debian/rules:16: build] Error 25
dpkg-buildpackage: error: debian/rules build subprocess returned exit 
status 2


Regards
Graham


[1] https://ci.debian.net/packages/p/python-pydap/unstable/amd64/
[2] 
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-pydap.html

Bug#900393: marked as done (runit 2.1.2-14 breaks git-daemon-run)

[Debian Bug Tracking System]

Your message dated Thu, 31 May 2018 10:35:57 +
with message-id 
and subject line Bug#900393: fixed in runit 2.1.2-15
has caused the Debian Bug report #900393,
regarding runit 2.1.2-14 breaks git-daemon-run
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.)


-- 
900393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900393
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: runit
Version: 2.1.2-14
Severity: serious
Justification: breaks upgrades

The changelog to runit 2.1.2-14 explains:

   * Do not install `update-service' script.

but it doesn't give any more context than that.  This breaks the
git-daemon-run package, as noticed e.g. by piuparts:

  https://piuparts.debian.org/sid/fail/git-daemon-run_1:2.17.1-1.log

Moreover, debian/runit.NEWS doesn't say anything about the change.
https://codesearch.debian.net/search?q=update-service=1 finds
some other callers.  Where can I read more about how to handle this,
and can you roll back the change for now to unblock updates?

Thanks,
Jonathan
--- End Message ---
--- Begin Message ---
Source: runit
Source-Version: 2.1.2-15

We believe that the bug you reported is fixed in the latest version of
runit, 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.
Dmitry Bogatov  (supplier of updated runit 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: Thu, 31 May 2018 07:58:42 +0300
Source: runit
Binary: runit runit-systemd runit-sysv getty-run runit-init
Architecture: source all amd64
Version: 2.1.2-15
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Bogatov 
Changed-By: Dmitry Bogatov 
Description:
 getty-run  - runscripts to supervise getty processes
 runit  - system-wide service supervision
 runit-init - system-wide service supervision (as init system)
 runit-systemd - system-wide service supervision (systemd integration)
 runit-sysv - system-wide service supervision (sysv integration)
Closes: 878476 900393
Changes:
 runit (2.1.2-15) unstable; urgency=medium
 .
   * Fix spin lock on systems with poor clock (Closes: #878476)
   * Bring back `update-service`, since it is actually used programmatically
 (Closes: #900393)
Checksums-Sha1:
 32552eb739557100686f7b8333c73fd49683665a 2116 runit_2.1.2-15.dsc
 9407da7211ad0a3b09de1ce66cad2d627165a8dd 24828 runit_2.1.2-15.debian.tar.xz
 97cf1c759f151dd29cc967b51b8cf3930df5b21a 17360 getty-run_2.1.2-15_all.deb
 07d775283738351d563cfacbd261e0cf9ea2327b 141092 runit-dbgsym_2.1.2-15_amd64.deb
 ed22254daa3479838c6174e7e03b719e37623112 25892 
runit-init-dbgsym_2.1.2-15_amd64.deb
 d3360e41fa1474f339402b51ad9d867e6fa63d1a 38092 runit-init_2.1.2-15_amd64.deb
 aab87b6c12d425bb52071fbf1fe130f76d7591af 16380 runit-systemd_2.1.2-15_all.deb
 90b49a7c25c6bdb6c1e632abfb87613cf44cdef9 15972 runit-sysv_2.1.2-15_all.deb
 c941286da45f0ea8d200bdbd6d7344826f48707a 6991 runit_2.1.2-15_amd64.buildinfo
 38d3d20c07d5ce442508f3c01fda32e713d13ddb 108872 runit_2.1.2-15_amd64.deb
Checksums-Sha256:
 8438b77bc14cba26c2cf20ffe26e794ba533dba882320f94c5eebc07e8672649 2116 
runit_2.1.2-15.dsc
 7f9dc5ce54e17bdbe4fe5bdb4c1f53481b2f94a63e4af2938e8058c8c53b2664 24828 
runit_2.1.2-15.debian.tar.xz
 f5a41577f34f26e4d6428dccc54b7c073874ade149775800c8472a308c20204e 17360 
getty-run_2.1.2-15_all.deb
 9c33689d09e32b090d05f75fe66a161c99338dd3e4672ab1385191074fb40169 141092 
runit-dbgsym_2.1.2-15_amd64.deb
 c384eb99b6bb58cab81e4e405994ff574f29005e0206561b468c4f6fec634116 25892 
runit-init-dbgsym_2.1.2-15_amd64.deb
 107cd35f1fd72ab9507390fe85ee9d0b2f08599c4c4cdb3fa97ab9b185f550fc 38092 
runit-init_2.1.2-15_amd64.deb
 cbedb12f26da8ec900d1daa9fd5136366011b6ff4a452eaa762ef93a90f29d4a 16380 
runit-systemd_2.1.2-15_all.deb
 f29a1a58b95053413b78d245de836bb3de97af573bc62fde124705a29ec307f1 15972 
runit-sysv_2.1.2-15_all.deb
 f969ff44df5fe8b857c0d6b2bba23378945163c8fc6eb4e57371af167dcbfe24 6991 
runit_2.1.2-15_amd64.buildinfo
 2918401558a86a3d6925358520647e8158a2c75900ef58db98f2f35a7a380568 108872 
runit_2.1.2-15_amd64.deb
Files:
 8f54fa00697a99ddfc6cf413396d3e19 2116 admin optional 

Bug#900485: python-pbcore: FTBFS and Debci failure with NumPy 1.14

[Graham Inggs]

Source: python-pbcore
Version: 1.2.11+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: needs-update

Hi Maintainer

Since the recent upload of python-numpy on 2018-05-05, python-pbcore has 
been failing its autopkgtests [1] and has now also started to FTBFS in 
unstable [2] with several errors similar to the following:


FAIL: test_referenceInfo (test_pbdataset.TestDataSet)
--
Traceback (most recent call last):
  File "/build/1st/python-pbcore-1.2.11+dfsg/tests/test_pbdataset.py", 
line 1407, in test_referenceInfo

"(27, 27, 'E.faecalis.1', 'E.faecalis.1', 1482, "
AssertionError: "(27, 27, 'E.faecalis.1', 'E.faecalis.1', 1482, 
'a1a59c267ac1341e5a12bce7a7d37bcb', 0, 0)" != "(27, 27, 'E.faecalis.1', 
'E.faecalis.1', 1482, 'a1a59c267ac1341e5a12bce7a7d37bcb', 0L, 0L)"

 >> begin captured logging << 
pbcore.io.dataset.DataSetIO: DEBUG: Opening ReadSet resources
pbcore.io.dataset.DataSetIO: DEBUG: Done opening resources
pbcore.io.dataset.DataSetIO: DEBUG: Updating counts
pbcore.io.dataset.DataSetIO: DEBUG: Populating index
pbcore.io.dataset.DataSetIO: DEBUG: Processing resource indices
pbcore.io.dataset.DataSetIO: DEBUG: Filtering reference entries
pbcore.io.dataset.DataSetIO: DEBUG: Done populating index

Regards
Graham


[1] https://ci.debian.net/packages/p/python-pbcore/unstable/amd64/
[2] 
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-pbcore.html

Bug#900393: runit 2.1.2-14 breaks git-daemon-run

[KAction]

--21882_ĵaŭ_Maj_31_13_32_22_MSK_2018
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


[2018-05-29 23:53] Jonathan Nieder 
> part   text/plain 646
> Package: runit
> Version: 2.1.2-14
> Severity: serious
> Justification: breaks upgrades
> =

> The changelog to runit 2.1.2-14 explains:
> =

>* Do not install `update-service' script.
> =

> but it doesn't give any more context than that.  This breaks the
> git-daemon-run package, as noticed e.g. by piuparts:
> =

>   https://piuparts.debian.org/sid/fail/git-daemon-run_1:2.17.1-1.log
> =

> Moreover, debian/runit.NEWS doesn't say anything about the change.
> https://codesearch.debian.net/search?q=3Dupdate-service=3D1 finds
> some other callers. =


Yes, my fault -- I forgot to check codesearch. Sorry, I will revert it.

> Where can I read more about how to handle this, and can you roll back
> the change for now to unblock updates?

In this change I wanted to phase out `update-service` script, but was
not so careful about it. `update-service' functionality is better served
by dh-runit and coreutils instead:

 * installing all required symbolic links and, maybe, enabling service
   by default, is handled by `dh-runit'
 * --add: ln -sf /etc/sv/$name /etc/service
 * --remove: unlink /etc/service/$name (`rm -f' is fine too)
 * --list: ls -1 /etc/service
 * --check: sv status $name

--21882_ĵaŭ_Maj_31_13_32_22_MSK_2018
Content-Type: application/pgp-signature

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEhnHVzDbtdH7ktKj4SBLY3qgmEeYFAlsPzzYACgkQSBLY3qgm
EeZKGQ//UH/8NtAYsZo06M2QglY/3Sl1vJZxsk6KKAcHZ3QIqDLl9OvCVyhL2y9W
lvIRdF218nPIvP2IYQnno0NIAuEMarYkbt7gCHIMUhkrbNkqJH2AYa2vQfmn6sUH
ucjsahtswNbKsydvYWhi98OkwUAa3fVosuuYTBKKkDkjT+flJJhBSnfOJIeEJhDI
5upK1kd+UtAKalarXDdEWOHTaZWpk8MdQN0S/NcyaPjT0kNu/WyJHpD1YiWeBS8v
oxdGEm0wzffOhPvnO0kxVk5w5g/i6RuH12Y7q3zuiEx1vhi4XSQ1MT+4zvZAT9H6
GZiM9YdHJGNVlbrftl+yrO1TvW6xcaWH8nvJ5EneXby+b/rOwxJwP/r23P/uCtHJ
ye797ZIr6OMPboLga0sqQBfnd0FVhFKJeggJy1cIDAOdKduKPTJ7hqqeJKhkCHEr
FDDW5e+UY9O+oE0XRNLbmboiCXtgZfXlEMBx0MlAm3HbZay9YlBat42J6p3q8omx
O+9AAomEf5hcBMMF3TT0rRnsoMuNEXTqjKFouRwvm9yzDZSszqcBy6L53mpPdrZM
OKPo8LH7RSOgViz9pFwolyTpS2JHut+2B68nbjXk9E1xtz+VFznQ60LxGmQG8xSL
r+Wp58PhHKrwMUy4xE9l5OINcQhg0s9oVV3KkK/D2Q5LddsiAc4=
=RoM3
-END PGP SIGNATURE-

--21882_ĵaŭ_Maj_31_13_32_22_MSK_2018--

Bug#900239: marked as done (libprocps-dev: symlink to libprocps.so broken in /usr/lib)

[Debian Bug Tracking System]

Your message dated Thu, 31 May 2018 10:20:17 +
with message-id 
and subject line Bug#900239: fixed in procps 2:3.3.15-2
has caused the Debian Bug report #900239,
regarding libprocps-dev: symlink to libprocps.so broken in /usr/lib
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.)


-- 
900239: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900239
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libprocps-dev
Version: 2:3.3.15-1
Severity: normal

Hey,

The libprocps-dev package depends on `libprocps7' but contains a broken
symlink to `libprocps.so.6' in the /usr/lib search path.

Otherwise the compiler picks up `libprocps.a' from the same directory,
that fails since it's not built with -fPIC.

I believe the original intention was to have a non-broken symlink to
`libprocps.so.7'.

cheers,
sh

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

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

Versions of packages libprocps-dev depends on:
ii  libprocps7  2:3.3.15-1

libprocps-dev recommends no packages.

libprocps-dev suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: procps
Source-Version: 2:3.3.15-2

We believe that the bug you reported is fixed in the latest version of
procps, 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.
Craig Small  (supplier of updated procps 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: Thu, 31 May 2018 19:42:46 +1000
Source: procps
Binary: procps libprocps7 libprocps-dev
Architecture: source amd64
Version: 2:3.3.15-2
Distribution: unstable
Urgency: medium
Maintainer: Craig Small 
Changed-By: Craig Small 
Description:
 libprocps-dev - library for accessing process information from /proc
 libprocps7 - library for accessing process information from /proc
 procps - /proc file system utilities
Closes: 899346 900239
Changes:
 procps (2:3.3.15-2) unstable; urgency=medium
 .
   * Fix link in libprocps-dev Closes: 900239
   * Fix typo in license Closes: #899346
Checksums-Sha1:
 499fb7cb1b424674f2c8967b25b7264f4ebdc329 2104 procps_3.3.15-2.dsc
 074539c79985d7624eaaf5e9dc4f05d5861369ce 28060 procps_3.3.15-2.debian.tar.xz
 9d30239c90a304680442943e5615f7071fa04431 73832 libprocps-dev_3.3.15-2_amd64.deb
 4c220ed08c94f1530a7a8023214d6d554facbfea 77152 
libprocps7-dbgsym_3.3.15-2_amd64.deb
 3d7cfe97f14dcb8cca1921ff180edcfcb3e4c5c4 61704 libprocps7_3.3.15-2_amd64.deb
 c60e8efd125870c7bc874e60e4d54c30988334b5 365788 
procps-dbgsym_3.3.15-2_amd64.deb
 849bbe0d4ddb646be380c69048553ce70263e087 6896 procps_3.3.15-2_amd64.buildinfo
 1e19b47e406993836ca177378fcb1289d61cc231 259204 procps_3.3.15-2_amd64.deb
Checksums-Sha256:
 c7f695ddba2fdf0c3b9de5c38de22713a7046dd9e4a141d59155f4dd62008b32 2104 
procps_3.3.15-2.dsc
 4e90c4129744b726929990239139fde29ab4e438d65d75f5d4c479ead2001aed 28060 
procps_3.3.15-2.debian.tar.xz
 2f80cc86cc30ac406c97d51f8e5239971c49395fc0fd2bc612d41a44e29e6b0d 73832 
libprocps-dev_3.3.15-2_amd64.deb
 164dbb5d1a13ce3debcec42f37c6d3fa1523e66dc03e341df311680f3d590ac7 77152 
libprocps7-dbgsym_3.3.15-2_amd64.deb
 3d3b623a2155b06cd523d45247fdb86dcc415684f5e64b72e04a5c2dd5fb684a 61704 
libprocps7_3.3.15-2_amd64.deb
 c8f82c300651b9040cab5bbba37a794317f9f28f25828b5232a6df21b9bc9b4d 365788 
procps-dbgsym_3.3.15-2_amd64.deb
 f7ec3706dc9a1d3ede2ef421273bee41cbb0ee9c0df519a6d160ffbac25b8d04 6896 
procps_3.3.15-2_amd64.buildinfo
 8d86e2fed0ac0d15750dc68158b0c0f74c9d9454b780da4e023d6c3aabdff62c 259204 
procps_3.3.15-2_amd64.deb
Files:
 f73b698ef3e19479f0b8530cfa301a7d 2104 admin optional procps_3.3.15-2.dsc
 bd5385a7d4f21a079960eaaef1769490 28060 admin optional 
procps_3.3.15-2.debian.tar.xz
 

Bug#900479: attal-themes: Should this package be removed?

[Simon McVittie]

Source: attal-themes
Severity: serious
User: debian...@lists.debian.org
Usertags: proposed-removal
Control: block -1 by 900468

attal fails to build from source since 2016, and depends on Qt 4 which
is no longer maintained. It was not released with stretch. attal-themes
appears to be a data package for attal, so is useless without attal.
It might be time for these packages to be removed from unstable.

If you agree, please reassign this bug to the archive administrators
with control commands similar to these:

severity xx normal
reassign xx ftp.debian.org
retitle xx RM: attal-themes -- RoQA; useless without attal

(This package cannot be removed unless attal is: see #900468.)

Conversely, if you think this package should remain in Debian, please
close this bug, and fix attal's RC bugs.

Please note that Games Team svn is no longer used and will soon be archived.
If this package continues to be in Debian, it should be imported into
salsa.debian.org git.

Thanks,
smcv

Processed: attal-themes: Should this package be removed?

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 900468
Bug #900479 [src:attal-themes] attal-themes: Should this package be removed?
900479 was not blocked by any bugs.
900479 was not blocking any bugs.
Added blocking bug(s) of 900479: 900468

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

Bug#899566: marked as done (libauthcas-perl: Invalid maintainer address pkg-cas-maintain...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Thu, 31 May 2018 09:49:43 +
with message-id 
and subject line Bug#899566: fixed in libauthcas-perl 1.7-1
has caused the Debian Bug report #899566,
regarding libauthcas-perl: Invalid maintainer address 
pkg-cas-maintain...@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.)


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

Dear uploader of libauthcas-perl,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package libauthcas-perl since the list address
pkg-cas-maintain...@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-cas-maintain...@lists.alioth.debian.org is 2.

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: libauthcas-perl
Source-Version: 1.7-1

We believe that the bug you reported is fixed in the latest version of
libauthcas-perl, 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.
Thijs Kinkhorst  (supplier of updated libauthcas-perl 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: Thu, 31 May 2018 09:01:03 +
Source: libauthcas-perl
Binary: libauthcas-perl
Architecture: source all
Version: 1.7-1
Distribution: unstable
Urgency: medium
Maintainer: Thijs Kinkhorst 
Changed-By: Thijs Kinkhorst 
Description:
 libauthcas-perl - Client library for CAS 2.0
Closes: 899566
Changes:
 libauthcas-perl (1.7-1) unstable; urgency=medium
 .
   * New upstream release.
   * Set self as sole maintainer (Closes: #899566).
   * Update upstream and Vcs Urls; update copyright.
   * Switch to source format 3.0 (quilt).
   * Update to debhelper level 10 and dh sequencer.
   * Checked for policy 4.1.4, no changes.
Checksums-Sha1:
 85d6e2e7a8af340793f355713f04bf658da5c46a 1583 libauthcas-perl_1.7-1.dsc
 023d2ec6e167b223926aa571fd438845688fb37e 21087 libauthcas-perl_1.7.orig.tar.gz
 28169c707bc374419c996a02b91e87598d895fab 1748 
libauthcas-perl_1.7-1.debian.tar.xz
 66758cf92f47099c5f65854623773ac5605c408a 14304 libauthcas-perl_1.7-1_all.deb
 6e3671f26cf98cbbefe96080e560da2b2d649933 5163 
libauthcas-perl_1.7-1_amd64.buildinfo
Checksums-Sha256:
 099ec5b408e51ed31849baf1c469920bae20975a16e915fe17beed4b2b38870b 1583 
libauthcas-perl_1.7-1.dsc
 

Processed: forcibly merging 888321 900447

[Debian Bug Tracking System]

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

> forcemerge 888321 900447
Bug #888321 [src:guacamole-server] guacamole-server: migrate to freerdp2
Bug #900447 [src:guacamole-server] Build against freerdp2
Set Bug forwarded-to-address to 
'https://issues.apache.org/jira/browse/GUACAMOLE-249'.
896780 was blocked by: 888321
896780 was not blocking any bugs.
Added blocking bug(s) of 896780: 900447
Marked as found in versions guacamole-server/0.9.9-2.
Added tag(s) sid and buster.
Merged 888321 900447
> thanks
Stopping processing here.

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

Bug#900248: nvidia-driver: update to 390.59 breaks direct rendering

[Luca Boccassi]

On Thu, 2018-05-31 at 11:07 +0200, Peter De Wachter wrote:
> > Fortunately another user reported a possible alternative, if you
> > have
> > time could you please try to drop a nvidia.conf in
> > /usr/share/X11/xorg.conf.d with the following content:
> > 
> > Section "OutputClass"
> > Identifier  "Nvidia Modules"
> > MatchDriver "nvidia-drm"
> > Driver  "nvidia"
> > Option  "AllowEmptyInitialConfiguration" "true"
> > ModulePath  "/usr/lib/nvidia"
> > EndSection
> > 
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900428
> > 
> > As before also restore the original libglx.so in modules/extension,
> > and
> > remove the Nvidia symlink altogether.
> 
> Yes, that works.
> 
> I noted that there was already a similar config file,
> nvidia-drm-outputclass.conf, that also has a MatchDriver "nvidia-drm"
> line. I don't know how X handles that: were they merged, or was one
> of
> them ignored?

Not sure, I'll have a look

> Also it looks like /usr/lib/nvidia might contain multiple
> incompatible
> libglx.so files:
> xserver-xorg-video-nvidia: /usr/lib/nvidia/current/libglx.so
> xserver-xorg-video-nvidia-legacy-304xx: /usr/lib/nvidia/legacy-
> 304xx/libglx.so
> xserver-xorg-video-nvidia-legacy-340xx: /usr/lib/nvidia/legacy-
> 340xx/libglx.so
> 
> I don't know if these packages can be installed together. If they
> can,
> there will be random failures again.
> 
> Best regards,usual
> Peter

Yes, same problem with the recursive search - each series will point to
 its directory instead of /usr/lib/nvidia, to avoid that problem.

Andreas, does adding this xorg file and removing the libglx.so
registration sound like a good plan to you?

-- 
Kind regards,
Luca Boccassi

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

Bug#900248: nvidia-driver: update to 390.59 breaks direct rendering

[Peter De Wachter]

> Fortunately another user reported a possible alternative, if you have
> time could you please try to drop a nvidia.conf in
> /usr/share/X11/xorg.conf.d with the following content:
>
> Section "OutputClass"
> Identifier  "Nvidia Modules"
> MatchDriver "nvidia-drm"
> Driver  "nvidia"
> Option  "AllowEmptyInitialConfiguration" "true"
> ModulePath  "/usr/lib/nvidia"
> EndSection
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900428
>
> As before also restore the original libglx.so in modules/extension, and
> remove the Nvidia symlink altogether.

Yes, that works.

I noted that there was already a similar config file,
nvidia-drm-outputclass.conf, that also has a MatchDriver "nvidia-drm"
line. I don't know how X handles that: were they merged, or was one of
them ignored?

Also it looks like /usr/lib/nvidia might contain multiple incompatible
libglx.so files:
xserver-xorg-video-nvidia: /usr/lib/nvidia/current/libglx.so
xserver-xorg-video-nvidia-legacy-304xx: /usr/lib/nvidia/legacy-304xx/libglx.so
xserver-xorg-video-nvidia-legacy-340xx: /usr/lib/nvidia/legacy-340xx/libglx.so

I don't know if these packages can be installed together. If they can,
there will be random failures again.

Best regards,
Peter

Bug#891395: marked as done (libfabric1: improperly packaged library support files)

[Debian Bug Tracking System]

Your message dated Thu, 31 May 2018 09:00:20 +
with message-id 
and subject line Bug#891395: fixed in libfabric 1.6.1-1
has caused the Debian Bug report #891395,
regarding libfabric1: improperly packaged library support files
to be marked as done.

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

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


-- 
891395: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891395
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libfabric1
Version: 1.5.3-1
Severity: serious
Justification: policy 8.2

libfabric1 ships /usr/bin/fi_{info,pingpong,strerror}. These files are
independent of the soname of the library. Debian policy section 8.2
prohibits such files from being shipped in the shared library package.
The typical solution is to split them out into a package named e.g.
libfabric-bin. Thus when libfabric bumps its soname, libfabric-bin would
get taken over by the newer package while libfabric1 and e.g. libfabric2
would remain coinstallable.

Helmut
--- End Message ---
--- Begin Message ---
Source: libfabric
Source-Version: 1.6.1-1

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

Debian distribution maintenance software
pp.
Roland Fehrenbacher  (supplier of updated libfabric 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, 30 May 2018 10:37:32 +0200
Source: libfabric
Binary: libfabric-bin libfabric1 libfabric-dev
Architecture: source amd64
Version: 1.6.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian HPC Team 
Changed-By: Roland Fehrenbacher 
Description:
 libfabric-bin - Diagnosis programs for the libfabric communication library
 libfabric-dev - Development files for libfabric1
 libfabric1 - libfabric communication library
Closes: 891395
Changes:
 libfabric (1.6.1-1) unstable; urgency=medium
 .
   * New upstream release.
   * Add package libfabric-bin (Closes: #891395)
   * Add psm2 provider
   * Drop obsolete patches
Checksums-Sha1:
 7b47f9c3aad1c66295412d5df121bf258cff53fa 2198 libfabric_1.6.1-1.dsc
 f7ba6d265a5dae4c1786a22052bac6489f22be8a 1026948 libfabric_1.6.1.orig.tar.xz
 82cd8109bee921b749b9db15d6a37e244808ebdb 6704 libfabric_1.6.1-1.debian.tar.xz
 a596031264a26984d7868b60d12b0124b606bfe0 63340 
libfabric-bin-dbgsym_1.6.1-1_amd64.deb
 20ee5e106d67203af224af48e2bcfa476a3a24f7 30468 libfabric-bin_1.6.1-1_amd64.deb
 fc7632dd5b4efaf2e38f7a9f41534e6f781fe80d 568252 libfabric-dev_1.6.1-1_amd64.deb
 8a9df547125d2c72797793cf7ee69883605fa5f8 2608748 
libfabric1-dbgsym_1.6.1-1_amd64.deb
 41dd8012ef9c9c0951660d0bd5221ec48f23850c 417944 libfabric1_1.6.1-1_amd64.deb
 97621664c871c3d10a1cff9580dc673756ee622e 6263 libfabric_1.6.1-1_amd64.buildinfo
Checksums-Sha256:
 9d30fd46de96d68852afb5810163aa27e6b3121cdbd7e3c8e7a83f326278fbac 2198 
libfabric_1.6.1-1.dsc
 a750d1890434ac400afb63f4ef6cc3f5ae4b0dd49395ef31b307928afc51969b 1026948 
libfabric_1.6.1.orig.tar.xz
 3bb3ef9c91fe9f40711a2ec6deb9cd433b2960d30a8558a352a3a715ba0ace5e 6704 
libfabric_1.6.1-1.debian.tar.xz
 c1198dab7cc10812f388a6fc0195f15275735137bf8cf14fbaaf344f32381e71 63340 
libfabric-bin-dbgsym_1.6.1-1_amd64.deb
 e16d725c1dbd3e7df86b776ffe09f74f9eec900b1d5e1d64289f3674bc173add 30468 
libfabric-bin_1.6.1-1_amd64.deb
 485233e25f80abd3eab3969155c5bedd5aa2aba45d44603522051896c69835ad 568252 
libfabric-dev_1.6.1-1_amd64.deb
 a13241a0549256b75c14a5d1e748038b53ae1fec5674e8abc61b02f91bc48cc6 2608748 
libfabric1-dbgsym_1.6.1-1_amd64.deb
 506680651bc18147fc100f8d565f4eefb2e364df7bbcc6aee42edad2cdf28acc 417944 
libfabric1_1.6.1-1_amd64.deb
 e0f2dcdc2e9e0e1ed14dbfb3acd3e4aa218f134b7db0d5ccc726be7320d20848 6263 
libfabric_1.6.1-1_amd64.buildinfo
Files:
 3cca4045ea34ad4e0f3965d79aeb6993 2198 libs optional libfabric_1.6.1-1.dsc
 387d984fee1d8e895c6963f83454c7bf 1026948 libs optional 
libfabric_1.6.1.orig.tar.xz
 98a2e4b90202b4e8c1ccd1a82f14b08d 6704 libs optional 
libfabric_1.6.1-1.debian.tar.xz
 c657b60e7f428f11d46007215ac825c9 63340 debug optional 
libfabric-bin-dbgsym_1.6.1-1_amd64.deb
 e961227647261e84f637bfdccbda79d9 30468 libs optional 
libfabric-bin_1.6.1-1_amd64.deb
 

Processed: reassign 900447 to src:guacamole-server

[Debian Bug Tracking System]

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

> reassign 900447 src:guacamole-server
Bug #900447 [guacamole-server] Build against freerdp2
Bug reassigned from package 'guacamole-server' to 'src:guacamole-server'.
Ignoring request to alter found versions of bug #900447 to the same values 
previously set
Ignoring request to alter fixed versions of bug #900447 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#900468: attal: Should this package be removed?

[Simon McVittie]

Source: attal
Severity: serious
User: debian...@lists.debian.org
Usertags: proposed-removal

attal fails to build from source since 2016, and depends on Qt 4 which
is no longer maintained. It was not released with stretch. I think it
might be time for this package to be removed from unstable.

If you agree, please reassign this bug to the archive administrators
with control commands similar to these:

severity xx normal
reassign xx ftp.debian.org
retitle xx RM: attal -- RoQA; FTBFS, depends on obsolete Qt 4, not in 
stretch

Conversely, if you think this package should remain in Debian, please
close this bug, and fix its other RC bugs.

Please note that Games Team svn is no longer used and will soon be archived.
If this package continues to be in Debian, it should be imported into
salsa.debian.org git.

Thanks,
smcv

Processed: Re: Bug#804579: logol-bin: bogus hardcoded dependency on libncursesw5

[Debian Bug Tracking System]

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

> severity 804579 serious
Bug #804579 [logol-bin] logol-bin: bogus hardcoded dependency on libncursesw5
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#900181: [Debian-med-packaging] Bug#900181: camp: FTBFS on mips: check metaclass->function("f4").call(object, camp::Args(1, 4, 15)).to() == 20 has failed

[Flavien Bridault]

Hi,

Thanks for the report. I am afraid this is the same king of bug that I
tried to fix few weeks ago (#876147).

mips is 32bits only right ?

Would that be possible to have access to a mips porterbox (my GPG key is
signed by a debian developer) ? That would really be of great help in
order to fix this.

Cheers,


Le 27/05/2018 à 09:50, Emilio Pozuelo Monfort a écrit :
> Source: camp
> Version: 0.8.2-1
> Severity: serious
>
> Hi,
>
> Your package failed to build on mips:
>
> 1/2 Test #2: camptest-qt ..***Failed0.05 sec
> Running 11 test cases...
> /<>/test/qt/functionmapping.cpp(95): error: in 
> "FUNCTIONMAPPING/call": check metaclass->function("f4").call(object, 
> camp::Args(1, 4, 15)).to() == 20 has failed [0 != 20]
>
> *** 1 failure is detected in the test module "CAMP testqt"
>
> 2/2 Test #1: camptest .   Passed0.09 sec
>
> 50% tests passed, 1 tests failed out of 2
>
> Full logs at 
> https://buildd.debian.org/status/package.php?p=camp=unstable
>
> Emilio
>
> ___
> Debian-med-packaging mailing list
> debian-med-packag...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging

-- 
*Flavien BRIDAULT*
Ingénieur de Recherche

fbrida...@ircad.fr

*IRCAD France*
1, place de l'Hôpital - 67091 Strasbourg Cedex - FRANCE

http://www.ircad.fr/ 




signature.asc
Description: OpenPGP digital signature

Processed (with 1 error): forcibly merging 888321 900447

[Debian Bug Tracking System]

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

> forcemerge 888321 900447
Bug #888321 [src:guacamole-server] guacamole-server: migrate to freerdp2
Unable to merge bugs because:
package of #900447 is 'guacamole-server' not 'src:guacamole-server'
Failed to forcibly merge 888321: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Bug#900447: Build against freerdp2

[Dominik George]

Control: reassign -1 guacamole-server
Control: merge 888321 -1

Hi,

> This bug is for tracking the efforts of porting guacamole-client to
> FreeRDP v2.

guacamole-client has nothing to do with freerdp.  ITYM guacamole-server,
which also already has a bug for that ☺.

-nik


signature.asc
Description: PGP signature

Processed (with 1 error): Re: Bug#900447: Build against freerdp2

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 guacamole-server
Bug #900447 [src:guacamole-client] Build against freerdp2
Bug reassigned from package 'src:guacamole-client' to 'guacamole-server'.
No longer marked as found in versions guacamole-client/0.9.9+dfsg-1.
Ignoring request to alter fixed versions of bug #900447 to the same values 
previously set
> merge 888321 -1
Bug #888321 [src:guacamole-server] guacamole-server: migrate to freerdp2
Unable to merge bugs because:
forwarded of #900447 is '' not 
'https://issues.apache.org/jira/browse/GUACAMOLE-249'
blocks of #900447 is '' not '896780'
package of #900447 is 'guacamole-server' not 'src:guacamole-server'
Failed to merge 888321: Did not alter merged bugs.


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

Bug#897100: marked as done (kicad FTBFS with cmake 3.11.1)

[Debian Bug Tracking System]

Your message dated Thu, 31 May 2018 07:19:46 +
with message-id 
and subject line Bug#897100: fixed in kicad 5.0.0~rc2+dfsg1-2
has caused the Debian Bug report #897100,
regarding kicad FTBFS with cmake 3.11.1
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.)


-- 
897100: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897100
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kicad
Version: 4.0.7+dfsg1-1
Severity: serious

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

...
-- Looking for strtok_r
-- Looking for strtok_r - found
CMake Error at CMakeModules/CheckCXXSymbolExists.cmake:41 
(_CHECK_SYMBOL_EXISTS):
  Unknown CMake command "_CHECK_SYMBOL_EXISTS".
Call Stack (most recent call first):
  CMakeModules/PerformFeatureChecks.cmake:86 (check_cxx_symbol_exists)
  CMakeLists.txt:141 (perform_feature_checks)
--- End Message ---
--- Begin Message ---
Source: kicad
Source-Version: 5.0.0~rc2+dfsg1-2

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 897...@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: Thu, 31 May 2018 07:27:13 +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-2
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: 897100
Changes:
 kicad (5.0.0~rc2+dfsg1-2) unstable; urgency=medium
 .
   * rebuild for unstable
 (Closes: #897100)
Checksums-Sha1:
 2be1df934dd08814b8bd83d31acc7916e6ae0c07 4483 kicad_5.0.0~rc2+dfsg1-2.dsc
 6ea3deb78e745ff7dddc635b952868593f8d5bcd 65104 
kicad_5.0.0~rc2+dfsg1-2.debian.tar.xz
 d43e2705dc049e58894355f2c1548e7e5285af14 24132 
kicad_5.0.0~rc2+dfsg1-2_amd64.buildinfo
Checksums-Sha256:
 6002d37b0e15fc6e640b511df867d769ae53560e3bed9bdc8fd59c82b007b583 4483 
kicad_5.0.0~rc2+dfsg1-2.dsc
 b8af6f4d5709d146cff0a572c617493a0760e46d6931031bfb2eaddf3f80ed2e 65104 
kicad_5.0.0~rc2+dfsg1-2.debian.tar.xz
 23fbf27d433da3d911b9da78efc8d550ba04274a64046af8fe6b3fed80d2b08e 24132 
kicad_5.0.0~rc2+dfsg1-2_amd64.buildinfo
Files:
 5928b135bd7e36852f12deb423e03c97 4483 electronics optional 
kicad_5.0.0~rc2+dfsg1-2.dsc
 f19657a7e655c07d60695e33158a757a 65104 electronics optional 
kicad_5.0.0~rc2+dfsg1-2.debian.tar.xz
 acb5a3bd1392f4712a029ce7dba50e3b 24132 electronics optional 
kicad_5.0.0~rc2+dfsg1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEtw38bxNP7PwBHmKqgwFgFCUdHbAFAlsPnXUACgkQgwFgFCUd
HbCwLQ//eh6iy2K90lBCxQaPBojg8RYovSxXrx1RTcS5iBw9hDSCV/pcBml24jYZ
tjYSM5ox1LoHF4grmxCslP9F2sxgV5lsA7vjIJ51L0vz/D2hBxdec5c+DnZHtoWe
Sqi1Uct53gG1U6oNfB7WPrzhomio5TG2QkI7wE7k5PpoXUhWd69s0wl4GoxzNeD6
NQTSoeiZwlY2gNAO+O3Y7Fse/PmboH04Ju3DcmblJ5aZpaSi6bEM+lfFSxNWmlK7
zql+ebSwhSbLnXKBj/UyBhYfE9Dotecm3ltEBOg2YenhC1IIWWWqm7vilILu/mAy
7EFQICKoJmEAxRaoVamQuXOyj/go0jjLQlE7BX6O7BswvxLKRRsLIdN5zTS+B9lu
GuvuVd8uRgb3d0FMMDikMFpuNlrW7dlh22AHl9hkUpkiQLMVtF03CasSirUQrm3R
wmLEZUCJCoJgwRbYTakRJl2is6dv/0eUTDcnREGLyO/a9TwAAWQT0Lm1GW+lRGGp
94oONj1cG+9T4PSw1+dQ8HhDEK7OtAV5A7Hk0xCQFbVvIP94/KVn2HfBxScEwrUP

Bug#842815: Help needed for HDF5 1.10 transition of libsis-jhdf5-java

[Andreas Tille]

Hi,

On Tue, May 29, 2018 at 07:24:55PM +0200, Gilles Filippini wrote:
> > is there anybody out there who can help with some HDF5 1.10 transition?
> > 
> > I admit I have no experience with HDF5 neither with Java - but the
> > migration would help a lot.
> 
> As already stated in this thread [1] I think patching libsis-jhdf5-java
> is a huge task beyond my available time.
> 
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842815#55

I remember you sad this - but I was hoping for other people here. :-)
 
> >>> Hello Bernd,
> >>>
> >>> sorry for nagging again but we now have another Dependency from
> >>> sis-jhdf5 which makes a fix for this issue even more interesting.  As I
> 
> Have you considered using libhdf5-java or libjhdf5-java instead?

The problem is: The applications I'm dealing with in the Debian Med team
(currently fastqc but more to come) are simply using the
libsis-jhdf5-java interface.  I would rather ask the upstream authors to
switch to those alternative interfaces.  Unfortunately I have basically
no Java knowledge and I have only a rudimentary idea what HDF5 might be.
That makes me a perfectly incompetent person to give good reasons
against something that might have been a well thought decision.

Bernd, could you possibly elaborate on the differences between
libsis-jhdf5-java and the other implementations and do you see any
chances to may be join forces with the other projects?

Kind regards

Andreas.

-- 
http://fam-tille.de

Bug#900460: ephoto: fails to start

[Norbert Preining]

Package: ephoto
Version: 1.5-1
Severity: grave
Justification: renders package unusable

Bot invocations
  ephoto
or
  ephoto foo.jpg
end with

ERR<25953>:ecore_evas lib/elementary/efl_ui_win.c:5005 
_elm_win_finalize_internal() Cannot create window.
## Copy & Paste the below (until EOF) into a terminal, then hit Enter

eina_btlog << EOF
/usr/lib/x86_64-linux-gnu/libeina.so.1   0x7fb89cd406cc 0x7fb89cd19000
/usr/lib/x86_64-linux-gnu/libeina.so.1   0x7fb89cd413f1 0x7fb89cd19000
/usr/lib/x86_64-linux-gnu/libeina.so.1   0x7fb89cd427c3 0x7fb89cd19000
/usr/lib/x86_64-linux-gnu/libelementary.so.1 0x7fb89b38956c 0x7fb89b109000
/usr/lib/x86_64-linux-gnu/libelementary.so.1 0x7fb89b38b470 0x7fb89b109000
/usr/lib/x86_64-linux-gnu/libeo.so.1 0x7fb89b8b630e 0x7fb89b8a6000
/usr/lib/x86_64-linux-gnu/libeo.so.1 0x7fb89b8ae9ac 0x7fb89b8a6000
/usr/lib/x86_64-linux-gnu/libelementary.so.1 0x7fb89b385142 0x7fb89b109000
/usr/bin/ephoto  0x55b70128b564 0x55b70126f000
/usr/bin/ephoto  0x55b701278a4f 0x55b70126f000
/usr/bin/ephoto  0x55b70127873c 0x55b70126f000
/lib/x86_64-linux-gnu/libc.so.6  0x7fb898e3ba87 0x7fb898e1a000
/usr/bin/ephoto  0x55b70127877a 0x55b70126f000
EOF

ERR<25953>:eo lib/eo/eo.c:949 _efl_add_internal_end() Object of class 
'Efl.Ui.Win' - Not all of the object constructors have been executed.
## Copy & Paste the below (until EOF) into a terminal, then hit Enter

eina_btlog << EOF
/usr/lib/x86_64-linux-gnu/libeina.so.1   0x7fb89cd406cc 0x7fb89cd19000
/usr/lib/x86_64-linux-gnu/libeina.so.1   0x7fb89cd413f1 0x7fb89cd19000
/usr/lib/x86_64-linux-gnu/libeina.so.1   0x7fb89cd427c3 0x7fb89cd19000
/usr/lib/x86_64-linux-gnu/libeo.so.1 0x7fb89b8aea8c 0x7fb89b8a6000
/usr/lib/x86_64-linux-gnu/libelementary.so.1 0x7fb89b385142 0x7fb89b109000
/usr/bin/ephoto  0x55b70128b564 0x55b70126f000
/usr/bin/ephoto  0x55b701278a4f 0x55b70126f000
/usr/bin/ephoto  0x55b70127873c 0x55b70126f000
/lib/x86_64-linux-gnu/libc.so.6  0x7fb898e3ba87 0x7fb898e1a000
/usr/bin/ephoto  0x55b70127877a 0x55b70126f000
EOF

ERR<25953>:evas_main lib/evas/canvas/evas_object_smart.c:646 
_efl_canvas_group_efl_object_destructor() efl_canvas_group_del() was not called 
on this object: 0x400105da (Efl.Ui.Win)
## Copy & Paste the below (until EOF) into a terminal, then hit Enter

eina_btlog << EOF
/usr/lib/x86_64-linux-gnu/libeina.so.1   0x7fb89cd406cc 0x7fb89cd19000
/usr/lib/x86_64-linux-gnu/libeina.so.1   0x7fb89cd413f1 0x7fb89cd19000
/usr/lib/x86_64-linux-gnu/libeina.so.1   0x7fb89cd427c3 0x7fb89cd19000
/usr/lib/x86_64-linux-gnu/libevas.so.1   0x7fb89c71a237 0x7fb89c689000
/usr/lib/x86_64-linux-gnu/libeo.so.1 0x7fb89b8b61ea 0x7fb89b8a6000
/usr/lib/x86_64-linux-gnu/libeo.so.1 0x7fb89b8b61ea 0x7fb89b8a6000
/usr/lib/x86_64-linux-gnu/libelementary.so.1 0x7fb89b36ee44 0x7fb89b109000
/usr/lib/x86_64-linux-gnu/libeo.so.1 0x7fb89b8b61ea 0x7fb89b8a6000
/usr/lib/x86_64-linux-gnu/libeo.so.1 0x7fb89b8b61ea 0x7fb89b8a6000
/usr/lib/x86_64-linux-gnu/libeo.so.1 0x7fb89b8ae8a4 0x7fb89b8a6000
/usr/lib/x86_64-linux-gnu/libeo.so.1 0x7fb89b8b5642 0x7fb89b8a6000
/usr/lib/x86_64-linux-gnu/libeo.so.1 0x7fb89b8aeaa7 0x7fb89b8a6000
/usr/lib/x86_64-linux-gnu/libelementary.so.1 0x7fb89b385142 0x7fb89b109000
/usr/bin/ephoto  0x55b70128b564 0x55b70126f000
/usr/bin/ephoto  0x55b701278a4f 0x55b70126f000
/usr/bin/ephoto  0x55b70127873c 0x55b70126f000
/lib/x86_64-linux-gnu/libc.so.6  0x7fb898e3ba87 0x7fb898e1a000
/usr/bin/ephoto  0x55b70127877a 0x55b70126f000
EOF





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

Kernel: Linux 4.16.11 (SMP w/8 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 ephoto depends on:
ii  libc6 2.27-3
ii  libecore-con1 1.20.7-4
ii  libecore-evas11.20.7-4
ii  libecore-file11.20.7-4
ii  libecore-imf1 1.20.7-4
ii  libecore-input1   1.20.7-4
ii  libecore-ipc1 1.20.7-4
ii  libecore1 1.20.7-4
ii  libedje1  1.20.7-4
ii  libeet1   1.20.7-4
ii  libefreet-bin 1.20.7-4
ii  libefreet1a   1.20.7-4
ii  libeina1a 1.20.7-4
ii  libeio1   1.20.7-4
ii  libelementary11.20.7-4
ii  libemotion1   1.20.7-4
ii  libethumb-client-bin  1.20.7-4
ii  libethumb-client1 1.20.7-4
ii  libevas1  1.20.7-4

ephoto recommends no packages.

ephoto suggests no packages.

-- no debconf information