Bug#879175: marked as done (androidsdk-tools: Duplicate of android-platform-tools-swt)

2018-10-08 Thread Debian Bug Tracking System
Your message dated Tue, 09 Oct 2018 06:56:53 +
with message-id 
and subject line Bug#909450: Removed package(s) from unstable
has caused the Debian Bug report #879175,
regarding androidsdk-tools: Duplicate of android-platform-tools-swt
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.)


-- 
879175: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879175
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: androidsdk-tools
Version: 22.2+git20130830~92d25d6-4
Severity: serious

It looks like source:androidsdk-tools has been replaced by
source:android-platform-tools-swt.

Although a bit confusing, it looks like the newer
android-platform-tools-swt corresponds with version 25.

Can we go ahead and remove androidsdk-tools?

On the other hand, the newer android-platform-tools-swt hasn't been
buildable since January. But the tools are deprecated and apparently
removed in newer Android SDK versions anyway.

Thanks,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Version: 22.2+git20130830~92d25d6-4+rm

Dear submitter,

as the package androidsdk-tools has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/909450

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Ansgar Burchardt (the ftpmaster behind the curtain)--- End Message ---


Bug#907590: marked as done (grafana: CVE-2018-15727: authentication bypass flaw)

2018-10-08 Thread Debian Bug Tracking System
Your message dated Tue, 09 Oct 2018 06:55:39 +
with message-id 
and subject line Bug#909592: Removed package(s) from unstable
has caused the Debian Bug report #907590,
regarding grafana: CVE-2018-15727: authentication bypass flaw
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.)


-- 
907590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907590
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: grafana
Version: 2.6.0+dfsg-3
Severity: grave
Tags: security upstream

Hi,

The following vulnerability was published for grafana.

CVE-2018-15727[0]:
| Grafana 2.x, 3.x, and 4.x before 4.6.4 and 5.x before 5.2.3 allows
| authentication bypass because an attacker can generate a valid
| "remember me" cookie knowing only a username of an LDAP or OAuth user.

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-15727
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-15727
[1] 
https://grafana.com/blog/2018/08/29/grafana-5.2.3-and-4.6.4-released-with-important-security-fix/

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Version: 2.6.0+dfsg-3+rm

Dear submitter,

as the package grafana has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/909592

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Ansgar Burchardt (the ftpmaster behind the curtain)--- End Message ---


Bug#817126: marked as done (grafana: FTBFS when built with dpkg-buildpackage -A (unable to chdir to _build))

2018-10-08 Thread Debian Bug Tracking System
Your message dated Tue, 09 Oct 2018 06:55:39 +
with message-id 
and subject line Bug#909592: Removed package(s) from unstable
has caused the Debian Bug report #817126,
regarding grafana: FTBFS when built with dpkg-buildpackage -A (unable to chdir 
to _build)
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.)


-- 
817126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817126
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:grafana
Version: 2.6.0+dfsg-3
User: sanv...@debian.org
Usertags: binary-indep
Severity: important

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(i.e. only architecture-independent packages), and it failed:


[...]
 debian/rules build-indep
## Build CSS: http://lesscss.org/usage/index.html
mkdir -p public/css
cd public/css \
&& lessc --include-path=../less --include-path=../vendor/bootstrap/less 
../less/bootstrap.dark.less grafana.dark.min.css.tmp \
&& cat grafana.dark.min.css.tmp 
/usr/share/fonts-font-awesome/css/font-awesome.css > grafana.dark.min.css \
&& lessc --include-path=../less --include-path=../vendor/bootstrap/less 
../less/bootstrap.light.less grafana.light.min.css.tmp \
&& cat grafana.light.min.css.tmp 
/usr/share/fonts-font-awesome/css/font-awesome.css > grafana.light.min.css \
;
tsc --module amd public/test/lib/common.ts 
public/test/core/utils/rangeutil_specs.ts 
public/test/core/utils/datemath_specs.ts 
public/test/core/utils/flatten_specs.ts public/test/core/table_model_specs.ts 
public/app/headers/lodash/lodash.d.ts public/app/headers/moment/moment.d.ts 
public/app/headers/moment/moment-node.d.ts 
public/app/headers/angularjs/angularjs.d.ts public/app/headers/common.d.ts 
public/app/headers/jquery/jquery.d.ts public/app/headers/require/require.d.ts 
public/app/features/panel/panel_meta.ts 
public/app/features/dashboard/timepicker/timepicker.ts 
public/app/plugins/datasource/elasticsearch/specs/index_pattern_specs.ts 
public/app/plugins/datasource/elasticsearch/specs/query_ctrl_specs.ts 
public/app/plugins/datasource/elasticsearch/specs/query_def_specs.ts 
public/app/plugins/datasource/elasticsearch/specs/elastic_response_specs.ts 
public/app/plugins/datasource/elasticsearch/specs/query_builder_specs.ts 
public/app/plugins/datasource/elasticsearch/specs/datasource_specs
 .ts public/app/plugins/datasource/graphite/specs/gfunc_specs.ts 
public/app/plugins/datasource/graphite/specs/query_ctrl_specs.ts 
public/app/plugins/datasource/graphite/specs/datasource_specs.ts 
public/app/plugins/datasource/cloudwatch/specs/datasource_specs.ts 
public/app/plugins/datasource/prometheus/specs/datasource_specs.ts 
public/app/plugins/datasource/influxdb/influx_query.ts 
public/app/plugins/datasource/influxdb/specs/query_ctrl_specs.ts 
public/app/plugins/datasource/influxdb/specs/influx_series_specs.ts 
public/app/plugins/datasource/influxdb/specs/query_builder_specs.ts 
public/app/plugins/datasource/influxdb/specs/query_part_specs.ts 
public/app/plugins/datasource/influxdb/specs/influx_query_specs.ts 
public/app/plugins/datasource/influxdb/query_part.ts 
public/app/plugins/datasource/influxdb_08/specs/influx_series_specs.ts 
public/app/plugins/datasource/influxdb_08/specs/query_builder_specs.ts 
public/app/plugins/datasource/influxdb_08/specs/datasource-specs.ts 
public/app/core/ti
 me_series.ts public/app/core/directives/give_focus.ts 
public/app/core/directives/array_join.ts public/app/core/utils/rangeutil.ts 
public/app/core/utils/datemath.ts public/app/core/utils/flatten.ts 
public/app/core/controllers/signup_ctrl.ts public/app/core/core.ts 
public/app/core/routes/bundle_loader.ts public/app/core/table_model.ts 
public/app/core/filters/filters.ts public/app/core/core_module.ts 
public/app/panels/table/module.ts public/app/panels/table/editor.ts 
public/app/panels/table/specs/renderer_specs.ts 
public/app/panels/table/specs/table_model_specs.ts 
public/app/panels/table/specs/transformers_specs.ts 
public/app/panels/table/controller.ts public/app/panels/table/renderer.ts 
public/app/panels/table/transformers.ts
 fakeroot debian/rules binary-indep
dh binary-indep --buildsystem=golang --with=golang,systemd 
--builddirectory=_build --parallel
   debian/rules build-indep
make[1]: Entering directory '/<>/grafana-2.6.0+dfsg'
## Build CSS: http://lesscss.org/usage/index.html
mkdir -p public/css
cd public/css \
&& lessc --include-path=../less --include-path=../vendor/bootstrap/less 
../less/bootstrap.dark.

Bug#861551: marked as done (grafana: FTBFS with latest golang-go.crypto)

2018-10-08 Thread Debian Bug Tracking System
Your message dated Tue, 09 Oct 2018 06:55:39 +
with message-id 
and subject line Bug#909592: Removed package(s) from unstable
has caused the Debian Bug report #861551,
regarding grafana: FTBFS with latest golang-go.crypto
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.)


-- 
861551: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861551
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

Bug #859655 [3] has been fixed in unstable. This addresses a CVE bug, but also
requires all reverse build dependencies be rebuilt. After this package has
migrated to testing, there will be 62-64 packages that need rebuilding as well.

I have run build tests in both unstable and testing for this update using an
amd64 sbuild environment. For reference, the results:

testing:
  success: 62,  failed: 2 (being addressed)
unstable
  success: 107, failed: 7 (unchecked)


For the moment, I need the 107 packages in this list [1] to rebuilt in unstable.
... wanna build? :)

[1]

nmu mtail_0.0+git20161231.ae129e9-1 . ANY all . unstable . -m 'Rebuild against 
fixed golang-go.crypto; #859655'
nmu tendermint-ed25519_0.0~git20160723.0.1f52c6f-1 . ANY all . unstable . -m 
'Rebuild against fixed golang-go.crypto; #859655'
nmu golang-github-rsc-letsencrypt_0.0~git20160929.0.76104d2-2 . ANY all . 
unstable . -m 'Rebuild against fixed golang-go.crypto; #859655'
nmu golang-github-docker-leadership_0.1.0-1 . ANY all . unstable . -m 'Rebuild 
against fixed golang-go.crypto; #859655'
nmu sia_1.0.4-1 . ANY all . unstable . -m 'Rebuild against fixed 
golang-go.crypto; #859655'
nmu golang-github-samalba-dockerclient_0.0~git20160531.0.a303626-1 . ANY all . 
unstable . -m 'Rebuild against fixed golang-go.crypto; #859655'
nmu golang-golang-x-net-dev_1:0.0+git20160110.4fd4a9f-1 . ANY all . unstable . 
-m 'Rebuild against fixed golang-go.crypto; #859655'
nmu gocryptfs_1.2-2 . ANY all . unstable . -m 'Rebuild against fixed 
golang-go.crypto; #859655'
nmu golang-github-aelsabbahy-gonetstat_0.0~git20160428.0.edf89f7-2 . ANY all . 
unstable . -m 'Rebuild against fixed golang-go.crypto; #859655'
nmu golang-github-blevesearch-bleve_0.5.0+git20170324.202.4702785f-1 . ANY all 
. unstable . -m 'Rebuild against fixed golang-go.crypto; #859655'
nmu golang-github-endophage-gotuf_0.0~git20151020.0.2df1c8e-1 . ANY all . 
unstable . -m 'Rebuild against fixed golang-go.crypto; #859655'
nmu cadvisor_0.25.0+dfsg-1 . ANY all . unstable . -m 'Rebuild against fixed 
golang-go.crypto; #859655'
nmu dnss_0.0~git20161126.0.162090e-1 . ANY all . unstable . -m 'Rebuild against 
fixed golang-go.crypto; #859655'
nmu golang-gopkg-dancannon-gorethink.v2_2.0.4-1 . ANY all . unstable . -m 
'Rebuild against fixed golang-go.crypto; #859655'
nmu mongo-tools_3.2.11-1 . ANY all . unstable . -m 'Rebuild against fixed 
golang-go.crypto; #859655'
nmu golang-github-docker-go-connections_0.2.1+git20161115.12.4ccf312-1 . ANY 
all . unstable . -m 'Rebuild against fixed golang-go.crypto; #859655'
nmu golang-github-fsouza-go-dockerclient_0.0+git20160622-1 . ANY all . unstable 
. -m 'Rebuild against fixed golang-go.crypto; #859655'
nmu golang-github-go-macaron-macaron_1.2.1+git20170219.2.8be5635-1 . ANY all . 
unstable . -m 'Rebuild against fixed golang-go.crypto; #859655'
nmu rkt_1.21.0+dfsg-1 . ANY all . unstable . -m 'Rebuild against fixed 
golang-go.crypto; #859655'
nmu golang-github-coreos-go-systemd_14-1 . ANY all . unstable . -m 'Rebuild 
against fixed golang-go.crypto; #859655'
nmu chasquid_0.01+git20161124.6479138-2 . ANY all . unstable . -m 'Rebuild 
against fixed golang-go.crypto; #859655'
nmu minica_1.0-1 . ANY all . unstable . -m 'Rebuild against fixed 
golang-go.crypto; #859655'
nmu golang-github-pkg-sftp_0.0~git20160930.0.4d0e916-1 . ANY all . unstable . 
-m 'Rebuild against fixed golang-go.crypto; #859655'
nmu golang-github-spf13-afero_0.0~git20161226.0.90dd71e-1 . ANY all . unstable 
. -m 'Rebuild against fixed golang-go.crypto; #859655'
nmu golang-github-azure-go-ntlmssp_0.0~git20160412.e0b63eb-1 . ANY all . 
unstable . -m 'Rebuild against fixed golang-go.crypto; #859655'
nmu golang-github-opencontainers-image-spec_1.0.0~rc2+dfsg-1 . ANY all . 
unstable . -m 'Rebuild against fixed golang-go.crypto; #859655'
nmu golang-github-couchbase-moss_0.0~git20170330.0.d2258a2-1 . ANY all . 
unstable . -m 'Rebuild against fixed golang-go.crypto; #859655'
nmu tendermint-go-p2p_0.0~git20170113.0.3d98f67-1 . ANY all . unstable . -m 
'Rebuild against fixed golang-go.crypto; #8

Bug#908425: marked as done (grafana-data depends on libjs-twitter-bootstrap that will not be in buster)

2018-10-08 Thread Debian Bug Tracking System
Your message dated Tue, 09 Oct 2018 06:55:39 +
with message-id 
and subject line Bug#909592: Removed package(s) from unstable
has caused the Debian Bug report #908425,
regarding grafana-data depends on libjs-twitter-bootstrap that will not be 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.)


-- 
908425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908425
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: grafana-data
Version: 2.6.0+dfsg-3
Severity: serious
Control: block 907724 by -1

See #907724 for background.
--- End Message ---
--- Begin Message ---
Version: 2.6.0+dfsg-3+rm

Dear submitter,

as the package grafana has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/909592

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Ansgar Burchardt (the ftpmaster behind the curtain)--- End Message ---


Bug#828814: marked as done (grafana: FTBFS: sqlstore/sqlstore.go:96: cannot assign to x.Logger)

2018-10-08 Thread Debian Bug Tracking System
Your message dated Tue, 09 Oct 2018 06:55:39 +
with message-id 
and subject line Bug#909592: Removed package(s) from unstable
has caused the Debian Bug report #828814,
regarding grafana: FTBFS: sqlstore/sqlstore.go:96: cannot assign to x.Logger
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.)


-- 
828814: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828814
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: grafana
Version: 2.6.0+dfsg-3
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

grafana fails to build from source in unstable/amd64:

  [..]

  Unpacking golang-github-gosimple-slug-dev (1.0-1) ...
  Selecting previously unselected package golang-github-streadway-amqp-dev.
  Preparing to unpack 
.../golang-github-streadway-amqp-dev_0.0~git20150820.0.f4879ba-1_all.deb ...
  Unpacking golang-github-streadway-amqp-dev (0.0~git20150820.0.f4879ba-1) ...
  Selecting previously unselected package libprotobuf9v5:amd64.
  Preparing to unpack .../libprotobuf9v5_2.6.1-2_amd64.deb ...
  Unpacking libprotobuf9v5:amd64 (2.6.1-2) ...
  Selecting previously unselected package libprotoc9v5:amd64.
  Preparing to unpack .../libprotoc9v5_2.6.1-2_amd64.deb ...
  Unpacking libprotoc9v5:amd64 (2.6.1-2) ...
  Selecting previously unselected package protobuf-compiler.
  Preparing to unpack .../protobuf-compiler_2.6.1-2_amd64.deb ...
  Unpacking protobuf-compiler (2.6.1-2) ...
  Selecting previously unselected package golang-goprotobuf-dev.
  Preparing to unpack 
.../golang-goprotobuf-dev_0.0~git20160425.7cc19b7-1_amd64.deb ...
  Unpacking golang-goprotobuf-dev (0.0~git20160425.7cc19b7-1) ...
  Selecting previously unselected package golang-google-appengine-dev.
  Preparing to unpack .../golang-google-appengine-dev_0.0~git20150606-2_all.deb 
...
  Unpacking golang-google-appengine-dev (0.0~git20150606-2) ...
  Selecting previously unselected package 
golang-google-cloud-compute-metadata-dev.
  Preparing to unpack 
.../golang-google-cloud-compute-metadata-dev_0.0~git20160413-1_all.deb ...
  Unpacking golang-google-cloud-compute-metadata-dev (0.0~git20160413-1) ...
  Selecting previously unselected package golang-golang-x-oauth2-dev.
  Preparing to unpack 
.../golang-golang-x-oauth2-dev_0.0~git20160416.0.7e9cd5d-1_all.deb ...
  Unpacking golang-golang-x-oauth2-dev (0.0~git20160416.0.7e9cd5d-1) ...
  Selecting previously unselected package libuv1:amd64.
  Preparing to unpack .../libuv1_1.9.1-1_amd64.deb ...
  Unpacking libuv1:amd64 (1.9.1-1) ...
  Selecting previously unselected package nodejs.
  Preparing to unpack .../nodejs_4.4.6~dfsg-1_amd64.deb ...
  Unpacking nodejs (4.4.6~dfsg-1) ...
  Selecting previously unselected package node-typescript.
  Preparing to unpack .../node-typescript_1.8.10-1_all.deb ...
  Unpacking node-typescript (1.8.10-1) ...
  Selecting previously unselected package fonts-font-awesome.
  Preparing to unpack .../fonts-font-awesome_4.6.3~dfsg-1_all.deb ...
  Unpacking fonts-font-awesome (4.6.3~dfsg-1) ...
  Selecting previously unselected package node-less.
  Preparing to unpack .../node-less_1.6.3~dfsg-2_all.deb ...
  Unpacking node-less (1.6.3~dfsg-2) ...
  Processing triggers for man-db (2.7.5-1) ...
  Processing triggers for libc-bin (2.22-13) ...
  Setting up dh-golang (1.18) ...
  Setting up dh-systemd (1.35) ...
  Setting up golang-1.6-src (1.6.2-2) ...
  Setting up golang-1.6-go (1.6.2-2) ...
  Setting up golang-src (2:1.6.1+1) ...
  Setting up golang-go (2:1.6.1+1) ...
  Setting up golang-github-go-ini-ini-dev (1.8.6-2) ...
  Setting up golang-github-davecgh-go-spew-dev (0.0~git20151106.5215b55-1) ...
  Setting up golang-github-pmezard-go-difflib-dev (0.0~git20160110.0.792786c-2) 
...
  Setting up golang-github-stretchr-objx-dev (0.0~git20150928.0.1a9d0bb-1) ...
  Setting up golang-github-stretchr-testify-dev 
(1.1.3+git20160418.12.c5d7a69+ds-1) ...
  Setting up golang-github-jmespath-go-jmespath-dev (0.2.2-1) ...
  Setting up golang-github-shiena-ansicolor-dev (0.0~git20151119.0.a422bbe-1) 
...
  Setting up golang-github-lsegal-gucumber-dev (0.0~git20160110.0.44a4d7e-1) ...
  Setting up golang-github-jacobsa-oglematchers-dev (0.0~git20150320-1) ...
  Setting up golang-github-jtolds-gls-dev (4.2.0-1) ...
  Setting up golang-github-jacobsa-oglemock-dev (0.0~git20150428-2) ...
  Setting up golang-golang-x-text-dev (0.0~git20160606.0.a4d77b4-1) ...
  Setting up golang-x-text-dev (0.0~git20160606.0.a4d77b4-1) ...
  Setting

Bug#864793: marked as done (crashes with JavaScript errors)

2018-10-08 Thread Debian Bug Tracking System
Your message dated Tue, 09 Oct 2018 06:55:39 +
with message-id 
and subject line Bug#909592: Removed package(s) from unstable
has caused the Debian Bug report #843263,
regarding crashes with JavaScript errors
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.)


-- 
843263: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843263
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: grafana
Version: 2.6.0+dfsg-3
Severity: grave

Hi,

After making a default installation of Grafana, I went to localhost:3000.
I got redirected to http://localhost:3000/login, which is black and otherwise
entirely blank (Chrome 59). The developer console says:

  Uncaught TypeError: Cannot read property 'indexOf' of undefined
  at 
public/vendor/angular-native-dragdrop/draganddrop.js?bust=1497481640638:25
  at 
public/vendor/angular-native-dragdrop/draganddrop.js?bust=1497481640638:390
  jquery.js?bust=1497481640638:3855 Uncaught Error: [$injector:modulerr] Failed 
to instantiate module ang-drag-drop due to:
  Error: [$injector:nomod] Module 'ang-drag-drop' is not available! You either 
misspelled the module name or forgot to load it. If registering a module ensure 
that you specify the dependencies as the second argument.
  http://errors.angularjs.org/1.4.3/$injector/nomod?p0=ang-drag-drop
  at 
http://localhost:3000/public/vendor/angular/angular.js?bust=1497481640638:68:12
  at 
http://localhost:3000/public/vendor/angular/angular.js?bust=1497481640638:1958:17
  at ensure 
(http://localhost:3000/public/vendor/angular/angular.js?bust=1497481640638:1882:38)
  at module 
(http://localhost:3000/public/vendor/angular/angular.js?bust=1497481640638:1956:14)
  at 
http://localhost:3000/public/vendor/angular/angular.js?bust=1497481640638:4362:22
  at forEach 
(http://localhost:3000/public/vendor/angular/angular.js?bust=1497481640638:336:20)
  at loadModules 
(http://localhost:3000/public/vendor/angular/angular.js?bust=1497481640638:4346:5)
  at createInjector 
(http://localhost:3000/public/vendor/angular/angular.js?bust=1497481640638:4272:11)
  at doBootstrap 
(http://localhost:3000/public/vendor/angular/angular.js?bust=1497481640638:1630:20)
  at Object.bootstrap 
(http://localhost:3000/public/vendor/angular/angular.js?bust=1497481640638:1651:12)
  
http://errors.angularjs.org/1.4.3/$injector/modulerr?p0=ang-drag-drop&p1=Er…Fpublic%2Fvendor%2Fangular%2Fangular.js%3Fbust%3D1497481640638%3A1651%3A12)
  at 
http://localhost:3000/public/vendor/angular/angular.js?bust=1497481640638:68:12
  at 
http://localhost:3000/public/vendor/angular/angular.js?bust=1497481640638:1958:17
  at ensure 
(http://localhost:3000/public/vendor/angular/angular.js?bust=1497481640638:1882:38)
  at module 
(http://localhost:3000/public/vendor/angular/angular.js?bust=1497481640638:1956:14)
  at 
http://localhost:3000/public/vendor/angular/angular.js?bust=1497481640638:4362:22
  at forEach 
(http://localhost:3000/public/vendor/angular/angular.js?bust=1497481640638:336:20)
  at loadModules 
(http://localhost:3000/public/vendor/angular/angular.js?bust=1497481640638:4346:5)
  at createInjector 
(http://localhost:3000/public/vendor/angular/angular.js?bust=1497481640638:4272:11)
  at doBootstrap 
(http://localhost:3000/public/vendor/angular/angular.js?bust=1497481640638:1630:20)
  at Object.bootstrap 
(http://localhost:3000/public/vendor/angular/angular.js?bust=1497481640638:1651:12)
  
http://errors.angularjs.org/1.4.3/$injector/modulerr?p0=ang-drag-drop&p1=Er…Fpublic%2Fvendor%2Fangular%2Fangular.js%3Fbust%3D1497481640638%3A1651%3A12)
  at 
http://localhost:3000/public/vendor/angular/angular.js?bust=1497481640638:68:12
  at 
http://localhost:3000/public/vendor/angular/angular.js?bust=1497481640638:4385:15
  at forEach 
(http://localhost:3000/public/vendor/angular/angular.js?bust=1497481640638:336:20)
  at loadModules 
(http://localhost:3000/public/vendor/angular/angular.js?bust=1497481640638:4346:5)
  at createInjector 
(http://localhost:3000/public/vendor/angular/angular.js?bust=1497481640638:4272:11)
  at doBootstrap 
(http://localhost:3000/public/vendor/angular/angular.js?bust=1497481640638:1630:20)
  at Object.bootstrap 
(http://localhost:3000/public/vendor/angular/angular.js?bust=1497481640638:1651:12)
  at HTMLDocument. 
(http://localhost:3000/public/app/app.js?bust=1497481640638:85:19)
  at mightThrow 
(http://localhost:3000/public/vendor/jquery/dist/jquery.js?bust=1497481640638:3570:29)
  at process 
(http://localhost:3

Bug#843263: marked as done (grafana: Blank page on new install)

2018-10-08 Thread Debian Bug Tracking System
Your message dated Tue, 09 Oct 2018 06:55:39 +
with message-id 
and subject line Bug#909592: Removed package(s) from unstable
has caused the Debian Bug report #843263,
regarding grafana: Blank page on new install
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.)


-- 
843263: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843263
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: grafana
Version: 2.6.0+dfsg-3
Severity: normal

Dear Maintainer,

After a fresh install of grafana, I visited http://localhost:3000 and
only get a blank page.  The firefox console contains the following
error, but I don't know if it's the cause:

Error: [$injector:modulerr] Failed to instantiate module ang-drag-drop due to:
[$injector:nomod] Module 'ang-drag-drop' is not available! You either 
misspelled the module name or forgot to load it. If registering a module ensure 
that you specify the dependencies as the second argument.
http://errors.angularjs.org/1.4.3/$injector/nomod?p0=ang-drag-drop
minErr/<@http://localhost:3000/public/vendor/angular/angular.js?bust=1478362831860:68:12
module/<@http://localhost:3000/public/vendor/angular/angular.js?bust=1478362831860:1958:17
ensure@http://localhost:3000/public/vendor/angular/angular.js?bust=1478362831860:1882:38
module@http://localhost:3000/public/vendor/angular/angular.js?bust=1478362831860:1956:14
loadModules/<@http://localhost:3000/public/vendor/angular/angular.js?bust=1478362831860:4362:22
forEach@http://localhost:3000/public/vendor/angular/angular.js?bust=1478362831860:336:11
loadModules@http://localhost:3000/public/vendor/angular/angular.js?bust=1478362831860:4346:5
createInjector@http://localhost:3000/public/vendor/angular/angular.js?bust=1478362831860:4272:11
bootstrap/doBootstrap@http://localhost:3000/public/vendor/angular/angular.js?bust=1478362831860:1630:20
bootstrap@http://localhost:3000/public/vendor/angular/angular.js?bust=1478362831860:1651:12
app.boot/http://localhost:3000/public/app/app.js?bust=1478362831860:85:11
resolve/http://localhost:3000/public/vendor/jquery/dist/jquery.js?bust=1478362831860:3570:21
resolve/http://localhost:3000/public/vendor/jquery/dist/jquery.js?bust=1478362831860:3638:12


Ross


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

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

Versions of packages grafana depends on:
ii  adduser 3.115
ii  golang-go   2:1.7~1
ii  grafana-data2.6.0+dfsg-3
ii  init-system-helpers 1.45
ii  libc6   2.24-5
ii  libfontconfig1 [libfontconfig]  2.11.0-6.7
ii  libsqlite3-03.15.0-1

grafana recommends no packages.

grafana suggests no packages.

-- Configuration Files:
/etc/grafana/grafana.ini [Errno 13] Permission denied: 
u'/etc/grafana/grafana.ini'
/etc/grafana/ldap.toml [Errno 13] Permission denied: u'/etc/grafana/ldap.toml'

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 2.6.0+dfsg-3+rm

Dear submitter,

as the package grafana has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/909592

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Ansgar Burchardt (the ftpmaster behind the curtain)--- End Message ---


Bug#852903: marked as done (android-platform-tools-swt: FTBFS: ProfileProvider.java:92: error: cannot find symbol)

2018-10-08 Thread Debian Bug Tracking System
Your message dated Tue, 09 Oct 2018 06:56:13 +
with message-id 
and subject line Bug#909449: Removed package(s) from unstable
has caused the Debian Bug report #852903,
regarding android-platform-tools-swt: FTBFS: ProfileProvider.java:92: error: 
cannot find symbol
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.)


-- 
852903: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852903
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: android-platform-tools-swt
Version: 2.0.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170128 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):
> make[1]: Entering directory '/<>'
> dh_auto_build -- --settings-file debian/settings.gradle assemble
>   mkdir -p .gradle/init.d
>   cp /usr/share/gradle-debian-helper/init.gradle .gradle/init.d/
>   gradle --info --console plain --offline --stacktrace --no-daemon 
> --refresh-dependencies --gradle-user-home .gradle -Duser.home=. 
> -Duser.name=debian -Ddebian.package=android-platform-tools-swt --parallel 
> --max-workers=64 --settings-file debian/settings.gradle assemble
> Initialized native services in: /<>/.gradle/native
> Starting Build
> Compiling initialization script '/<>/.gradle/init.d/init.gradle' 
> using SubsetScriptTransformer.
> Compiling initialization script '/<>/.gradle/init.d/init.gradle' 
> using BuildScriptTransformer.
>   Loading the Maven rules...
> Compiling settings file '/<>/debian/settings.gradle' using 
> SubsetScriptTransformer.
> Compiling settings file '/<>/debian/settings.gradle' using 
> BuildScriptTransformer.
> Settings evaluated using settings file 
> '/<>/debian/settings.gradle'.
>   Settings file found (/<>/debian/settings.gradle), but 
> rootProject.name isn't defined
>   Root project name not defined in settings.gradle, defaulting to 
> 'android-platform-tools-swt' instead of the name of the root directory 
> 'debian'
> Projects loaded. Root project using build file 
> '/<>/build.gradle'.
> Included projects: [root project 'android-platform-tools-swt', project 
> ':swt', project ':swt:chimpchat', project ':swt:ddms', project 
> ':swt:ddmuilib', project ':swt:hierarchyviewer2', project 
> ':swt:hierarchyviewer2lib', project ':swt:monkeyrunner', project 
> ':swt:sdkstats', project ':swt:swtmenubar', project ':swt:traceview', project 
> ':swt:uiautomatorviewer']
>   Keep-alive timer started
>   Adding Debian repository to project 'android-platform-tools-swt'
>   Adding Debian repository to project 'swt'
>   Adding Debian repository to project 'chimpchat'
>   Adding Debian repository to project 'ddms'
>   Adding Debian repository to project 'ddmuilib'
>   Adding Debian repository to project 'hierarchyviewer2'
>   Adding Debian repository to project 'hierarchyviewer2lib'
>   Adding Debian repository to project 'monkeyrunner'
>   Adding Debian repository to project 'sdkstats'
>   Adding Debian repository to project 'swtmenubar'
>   Adding Debian repository to project 'traceview'
>   Adding Debian repository to project 'uiautomatorviewer'
> Parallel execution is an incubating feature.
> Evaluating root project 'android-platform-tools-swt' using build file 
> '/<>/build.gradle'.
> Compiling build file '/<>/build.gradle' using 
> SubsetScriptTransformer.
> Compiling build file '/<>/build.gradle' using 
> BuildScriptTransformer.
> Compiling script '/<>/debian/version.gradle' using 
> SubsetScriptTransformer.
> Compiling script '/<>/debian/version.gradle' using 
> BuildScriptTransformer.
> Compiling script '/<>/debian/generatePom.gradle' using 
> SubsetScriptTransformer.
> Compiling script '/<>/debian/generatePom.gradle' using 
> BuildScriptTransformer.
> Compiling script '/<>/debian/generateClasspath.gradle' using 
> SubsetScriptTransformer.
> Compiling script '/<>/debian/generateClasspath.gradle' using 
> BuildScriptTransformer.
> Evaluating project ':swt' using build file '/<>/build.gradle'.
> Evaluating project ':swt:chimpchat' using build file 
> '/<>/chimpchat/build.gradle'.
> Compiling build file '/<>/chimpchat/build.gradle' using 
> SubsetScriptTransformer.
> Compiling build file '/<>/chimpchat/build.gradle' using 
> BuildScriptTransformer.
>   Adding task debianMavenPom to project 'chimpchat'
>   Configuring javadoc links
> Evaluating project ':swt:ddms' using build file 
> '/<>/ddms/app/build.gradle'.
> Compiling build file '/<>/ddms/app/build.gra

Bug#906862: marked as done (xul-ext-openinbrowser no longer works with firefox-esr 60)

2018-10-08 Thread Debian Bug Tracking System
Your message dated Tue, 09 Oct 2018 06:50:35 +
with message-id 
and subject line Bug#910624: Removed package(s) from unstable
has caused the Debian Bug report #906862,
regarding xul-ext-openinbrowser no longer works with firefox-esr 60
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.)


-- 
906862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906862
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xul-ext-openinbrowser
Version: 1.17-1
Severity: serious

XUL addons are no longer supported.
--- End Message ---
--- Begin Message ---
Version: 1.17-1+rm

Dear submitter,

as the package openinbrowser has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/910624

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Ansgar Burchardt (the ftpmaster behind the curtain)--- End Message ---


Bug#910324: marked as done (freebayes parallel FTBFS)

2018-10-08 Thread Debian Bug Tracking System
Your message dated Tue, 09 Oct 2018 06:42:05 +
with message-id 
and subject line Bug#910324: fixed in freebayes 1.2.0-2
has caused the Debian Bug report #910324,
regarding freebayes parallel FTBFS
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.)


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

freebayes fails to build from source in sbuild on unstable/amd64 when
performing a parallel build. The linker invocation is run before all
relevant objects are compiled. A build log ends with:

| g++ -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -I../ttmath  
-I/usr/include/bamtools `pkg-config --cflags libvcflib` `pkg-config --cflags 
libseqlib` `pkg-config --cflags htslib` `pkg-config --cflags jsoncpp` 
bamleftalign.o BedReader.o CNV.o fastlz.o Fasta.o Parameters.o Allele.o 
Sample.o Result.o AlleleParser.o Utility.o Genotype.o DataLikelihood.o 
Multinomial.o Ewens.o ResultData.o Dirichlet.o Marginals.o split.o LeftAlign.o 
IndelAllele.o Bias.o Contamination.o NonCall.o SegfaultHandler.o -o 
../bin/bamleftalign -lbamtools -ltabixpp -lz -lm -lpthread `pkg-config --libs 
libvcflib` `pkg-config --libs htslib` `pkg-config --libs libseqlib` `pkg-config 
--libs jsoncpp`
| g++: error: AlleleParser.o: No such file or directory
| g++: error: Genotype.o: No such file or directory
| g++: error: ResultData.o: No such file or directory
| make[2]: *** [Makefile:81: ../bin/bamleftalign] Error 1
| make[2]: *** Waiting for unfinished jobs
| make[2]: Leaving directory '/<>/src'
| make[1]: *** [Makefile:2: all] Error 2
| make[1]: Leaving directory '/<>'
| dh_auto_build: make -j12 "INSTALL=install --strip-program=true" returned exit 
code 2
| make: *** [debian/rules:6: build] Error 2
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

The issue is also seen during reproducible builds:

https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/freebayes_1.2.0-1.rbuild.log.gz

Helmut
--- End Message ---
--- Begin Message ---
Source: freebayes
Source-Version: 1.2.0-2

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated freebayes package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 09 Oct 2018 07:56:21 +0200
Source: freebayes
Binary: freebayes
Architecture: source
Version: 1.2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 freebayes  - Bayesian haplotype-based polymorphism discovery and genotyping
Closes: 910324
Changes:
 freebayes (1.2.0-2) unstable; urgency=medium
 .
   * Standards-Version: 4.2.1
   * Versioned Build-Depends: libvcflib-dev (>= 1.0.0~rc2+dfsg-2~)
   * debian/rules:
  + --no-parallel
Closes: #910324
  + Respect DEB_BUILD_OPTIONS in override_dh_auto_test
Checksums-Sha1:
 264b0b942abc6274a1cf0d0f6b3945c8fb660aa9 2171 freebayes_1.2.0-2.dsc
 7ff12ab788e7865b025859c9eda94213a9b39915 10780 freebayes_1.2.0-2.debian.tar.xz
Checksums-Sha256:
 3f75bdb409afe1ef2004e460a7478e537a8f742bb01c1be197d10154e54cca8f 2171 
freebayes_1.2.0-2.dsc
 a8b8e2c729adffb8d7d347f06edce1cb3d866da99fc59feec7ff3531db09e4fe 10780 
freebayes_1.2.0-2.debian.tar.xz
Files:
 0523d4aa8d667e75a545f7deb7e692af 2171 science optional freebayes_1.2.0-2.dsc
 e0972cf8355275e1e775ed92235b7f34 10780 science optional 
freebayes_1.2.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlu8RVQRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtE1kg/+Kq+BfJ99buzqucq/kAGE4J/C8uxo7DXv
/bhPsnhZPJKzyTGg99ovT+enH8fZJfk0z3EiNvWNXN2FLQh9vjHyBzi21VBt7IIV
eybXG0+S7ryQP+kjPXM3cWvQHppOmelCU+WfCp0TAON9eyR1+XqZ4NDZcYd2Zh1s
H4B7NAVz5R0ZrxmWqDmI1sG1GanCC4i+xQfLCtsvrXUiY3ih9g9Y/Fj3NfrZ

Bug#910631: lightdm: first login hangs waiting for user-generated entropy

2018-10-08 Thread Yves-Alexis Perez
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

control: severity -1 normal

On Tue, 2018-10-09 at 03:04 +0200, Jules Bernable wrote:
> Package: lightdm
> Version: 1.26.0-3
> Severity: grave
> Justification: renders package unusable

This is not a correct severity, the system is not unusable.
> 
> Dear Maintainer,
> 
> On my buster/sid system, LightDM hangs indefinitely on first login until
> entropy is generated via mouse or keyboard input.
> The login process seems to be delayed by the kernel itself, until the
> following
> lines appear in journalctl:
> 
> kernel: random: crng init done
> kernel: random: 7 urandom warning(s) missed due to ratelimiting

To be honest, it's unlikely to be a problem in LightDM itself, I'd say it's
rather in generating the Xorg cookie.
> 
> 
> This issue also seems related to bug #897572

Inded I'd say it's the same cause (your system doesn't have enough entropy).
I'll try to find the Xorg bug.

Regards,
- -- 
Yves-Alexis
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAlu8R34ACgkQ3rYcyPpX
RFsPuwgAsF0BhCU1YP5180cxZC4fajeinrtQN3aExbPVazXk2ENzcJ8CQjKQ8mi2
ePF4ALahVVEKSV6MdlY+mzlwEUJ5VvMKkP/sw0TxRh5Jq290hN7v14WzNtOda74e
klcmY8MPUN2dfHsd9UelXpgNrNacKFTaQ1obHfI5uTAZAbBCDzRX2EbaEa5vofc9
lG4IXcON1Mby9mI7cXtys2EMAQFeTodFwIi9WVxZB+8BDyUWgL3NGntU5jrx8Jg6
pNvVMTUw9FSNVbjMZO39cnlS9FEo9DgnG2viXdK3ThCAfsIio5DTJ7D1NEqVPdHE
n3rtp3XOEmIkHnGkTsfsd3q6cPtdgA==
=6NyN
-END PGP SIGNATURE-



Processed: Re: Bug#910631: lightdm: first login hangs waiting for user-generated entropy

2018-10-08 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 normal
Bug #910631 [lightdm] lightdm: first login hangs waiting for user-generated 
entropy
Severity set to 'normal' from 'grave'

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



Bug#899522: marked as done (gauche-c-wrapper: Invalid maintainer address pkg-gauche-de...@lists.alioth.debian.org)

2018-10-08 Thread Debian Bug Tracking System
Your message dated Tue, 09 Oct 2018 04:50:36 +
with message-id 
and subject line Bug#899522: fixed in gauche-c-wrapper 0.6.1-9
has caused the Debian Bug report #899522,
regarding gauche-c-wrapper: Invalid maintainer address 
pkg-gauche-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.)


-- 
899522: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899522
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gauche-c-wrapper
Version: 0.6.1-8
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of gauche-c-wrapper,

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

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: gauche-c-wrapper
Source-Version: 0.6.1-9

We believe that the bug you reported is fixed in the latest version of
gauche-c-wrapper, 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.
NIIBE Yutaka  (supplier of updated gauche-c-wrapper package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 09 Oct 2018 10:39:08 +0900
Source: gauche-c-wrapper
Binary: gauche-c-wrapper
Architecture: source
Version: 0.6.1-9
Distribution: unstable
Urgency: medium
Maintainer: NIIBE Yutaka 
Changed-By: NIIBE Yutaka 
Description:
 gauche-c-wrapper - Foreign function interface for Gauche to C libraries
Closes: 790036 899522
Changes:
 gauche-c-wrapper (0.6.1-9) unstable; urgency=medium
 .
   * debian/control (Standards-Version): Conforms to 4.2.1.
   (Build-Depends): This is for new gauche-dev (>= 0.9.6).
   (Maintainer): Don't use mailing list (Closes: #899522).
   * debian/compat: Upgrade to 11.
   * debian/patches/06___glibc_macro_warning.patch: New.
   * debian/rules: Update.
   * New package lets build amd64 package (Closes: #790036).
Checksums-Sha1:
 6ba0b013ad764737ebbf58a39b1f032eabfdfd03 1704 gauche-c-wrapper_0.6.1-9.dsc
 77a465417a1c889ca5c622c2512d8edd9f5d5fe3 6528 
gauche-c-wrapper_0.6.1-9.debian.tar.xz
 e9bf48caa9bb4e2461eec775075953176fc2f021 6233 
gauche-c-wrapper_0.6.1-9_amd64.buildinfo
Checksums-Sha256:
 cb9d86f0d7cf45383833d154837cc67b139ecf283a045c3f837885dfa0fe9528 1704 
gauche-c-wrapper_0.6.1-9.dsc
 be7052a8167f8aa68b8537ad25c69fbd3fb71d86a3ba68daff6fcf519b088773 6528 
gauch

Bug#909941: Reverting your previous erlang upload until rabbitmq-server is fixed

2018-10-08 Thread Thomas Goirand
Dear Sergei,

The amount of work to package a new version of Rabbitmq-server is
non-trivial, there seems to be a lot of changes in the upstream code
organization. There's now a new rabbitmq-common package that is a
library for both the server and client. How should I name the library
package?

I know nothing about Erlang library packaging such as rabbitmq-common,
therefore, I'd very much appreciate your help doing it. Pointing at
example packages similar to that one would be very helpful, for example.

In the mean time, it'd be super nice of you if you could revert your
Erlang 21 upload until rabbitmq-server is fixed. Or is that too much
work to do also?

Also, (keep in mind I don't know much about Erlang, but did you think
about packaging multiple versions of Erlang in Debian, so we could
handle transitions better?

In anyways, can you say hello to me on IRC so we can discuss this?

Cheers,

Thomas Goirand (zigo)



Bug#910634: spice: FTBFS on all architectures

2018-10-08 Thread Salvatore Bonaccorso
Source: spice
Version: 0.14.0-1.1
Severity: serious
Justification: FTBFS everywhere

Hi

The NMU I uploaded as 0.14.0-1.1 FTBFS on *all* architectures. 

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

This was almost sure not the case when I prepared the NMU, at least
when building in my usual pbuilder envionment. Which possible change
or difference causes this?

Regards,
Salvatore



Bug#891299: marked as done (gauche-gtk: FTBFS with glibc 2.27: glgdGraph.c:25:42: error: 'HUGE' undeclared (first use in this function))

2018-10-08 Thread Debian Bug Tracking System
Your message dated Tue, 09 Oct 2018 03:00:42 +
with message-id 
and subject line Bug#891299: fixed in gauche-gtk 0.6+git20160927-2
has caused the Debian Bug report #891299,
regarding gauche-gtk: FTBFS with glibc 2.27: glgdGraph.c:25:42: error: 'HUGE' 
undeclared (first use in this function)
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.)


-- 
891299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891299
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gauche-gtk
Version: 0.6+git20160927-1
Severity: important
Tags: patch
User: debian-gl...@lists.debian.org
Usertags: 2.27

gauche-gtk 0.6+git20160927-1 fails to build with glibc 2.27 
(2.27-0experimental0 from
experimental):

| glgdGraph.c:850:9: warning: 'pango_ft2_get_context' is deprecated: Use 
'pango_font_map_create_context' instead [-Wdeprecated-declarations]
|  graph->pangoFT2Context = pango_ft2_get_context(_PANGO_DPI, 
_PANGO_DPI);
|  ^
| In file included from glgd.h:21:0,
|  from gauche-glgd.h:26,
|  from glgdGraph.c:12:
| /usr/include/pango-1.0/pango/pangoft2.h:122:20: note: declared here
|  PangoContext  *pango_ft2_get_context  (double dpi_x,
| ^
| glgdGraph.c: In function 'glgdGraphInit':
| glgdGraph.c:25:42: error: 'HUGE' undeclared (first use in this function)
|  #define _MAXFLT (HUGE)
|   ^
| glgdGraph.c:907:30: note: in expansion of macro '_MAXFLT'
|  graph->extents[0] = +_MAXFLT;
|   ^~~
| glgdGraph.c:25:42: note: each undeclared identifier is reported only once for 
each function it appears in
|  #define _MAXFLT (HUGE)
|   ^
| glgdGraph.c:907:30: note: in expansion of macro '_MAXFLT'
|  graph->extents[0] = +_MAXFLT;
|   ^~~
| glgdGraph.c: In function 'glgdGraphFini':
| glgdGraph.c:959:13: warning: 'pango_ft2_shutdown_display' is deprecated 
[-Wdeprecated-declarations]
|  pango_ft2_shutdown_display();
|  ^~
| In file included from glgd.h:21:0,
|  from gauche-glgd.h:26,
|  from glgdGraph.c:12:
| /usr/include/pango-1.0/pango/pangoft2.h:127:20: note: declared here
|  void   pango_ft2_shutdown_display (void);
| ^~
| glgdGraph.c:25:42: error: 'HUGE' undeclared (first use in this function)
|  #define _MAXFLT (HUGE)
|   ^
| glgdGraph.c:975:30: note: in expansion of macro '_MAXFLT'
|  graph->extents[0] = +_MAXFLT;
|   ^~~
| glgdGraph.c: In function 'glgdGraphTranslate':
| glgdGraph.c:25:42: error: 'HUGE' undeclared (first use in this function)
|  #define _MAXFLT (HUGE)
|   ^
| glgdGraph.c:1165:30: note: in expansion of macro '_MAXFLT'
|  graph->extents[0] = +_MAXFLT;
|   ^~~
| glgdGraph.c: In function 'glgdGraphAutoOrganize':
| glgdGraph.c:25:42: error: 'HUGE' undeclared (first use in this function)
|  #define _MAXFLT (HUGE)
|   ^
| glgdGraph.c:1205:30: note: in expansion of macro '_MAXFLT'
|  graph->extents[0] = +_MAXFLT;
|   ^~~
| : recipe for target 'glgdGraph.o' failed
| make[2]: *** [glgdGraph.o] Error 1
| make[2]: Leaving directory '/<>/gauche-gtk-0.6+git20160927/glgd'
| Makefile:43: recipe for target 'all' failed
| make[1]: *** [all] Error 2
| make[1]: Leaving directory '/<>/gauche-gtk-0.6+git20160927'
| dh_auto_build: make -j1 returned exit code 2
| debian/rules:9: recipe for target 'build-arch' failed
| make: *** [build-arch] Error 2
| dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2

A full build log is available there:
http://aws-logs.debian.net/2018/02/07/glibc-exp/gauche-gtk_0.6+git20160927-1_unstable_glibc-exp.log

Starting with glibc 2.27, support for SVID error handling has been
removed, including the corresponding HUGE constant. This causes this
package to FTBFS. The attached patch fixes that by always defining
_MAXFLT using HUGE_VAL instead of HUGE, like it is already the case
on mingw32.
diff -Nru gauche-gtk-0.6+git20160927/debian/patches/07-HUGE.patch 
gauche-gtk-0.6+git20160927/debian/patches/07-HUGE.patch
--- gauch

Bug#899521: marked as done (gauche-gtk: Invalid maintainer address pkg-gauche-de...@lists.alioth.debian.org)

2018-10-08 Thread Debian Bug Tracking System
Your message dated Tue, 09 Oct 2018 03:00:42 +
with message-id 
and subject line Bug#899521: fixed in gauche-gtk 0.6+git20160927-2
has caused the Debian Bug report #899521,
regarding gauche-gtk: Invalid maintainer address 
pkg-gauche-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.)


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

Dear uploader of gauche-gtk,

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

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: gauche-gtk
Source-Version: 0.6+git20160927-2

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 09 Oct 2018 09:27:26 +0900
Source: gauche-gtk
Binary: gauche-gtk
Architecture: source
Version: 0.6+git20160927-2
Distribution: unstable
Urgency: medium
Maintainer: NIIBE Yutaka 
Changed-By: NIIBE Yutaka 
Description:
 gauche-gtk - Gauche bindings for GTK+ GUI Toolkit
Closes: 891299 899521
Changes:
 gauche-gtk (0.6+git20160927-2) unstable; urgency=medium
 .
   * debian/control (Standards-Version): Conforms to 4.2.1.
   (Build-Depends): This is for new gauche-dev (>= 0.9.6).
   (Maintainer): Don't use mailing list (Closes: #899521).
   * debian/compat: Upgrade to 11.
   * debian/patches/07-HUGE.patch: Fix for HUGE.  Thanks
   to Aurelien Jarno (Closes: #891299).
   * debian/patches/08-configure-ac-fix.patch: New.
Checksums-Sha1:
 fc6a68ca06932b437b04569c80cc9fff11d937e1 1632 gauche-gtk_0.6+git20160927-2.dsc
 4d2a686101018d3978a8a758a7f6355277758479 13600 
gauche-gtk_0.6+git20160927-2.debian.tar.xz
 4b97de135d68390bbfa8c1def20db33c6951e269 12659 
gauche-gtk_0.6+git20160927-2_amd64.buildinfo
Checksums-Sha256:
 4e99c5c91e06a730c3bd760e487a42da2ef065076a14b5e131893f601d18f5b3 1632 
gauche-gtk_0.6+git20160927-2.dsc
 855e46940e3a4dc6585eaa37a678c1c3f94f4c9a3bf68e9643e03e4882e4f282 13600 
gauche-gtk_0.6+git20

Bug#899523: marked as done (gauche-gl: Invalid maintainer address pkg-gauche-de...@lists.alioth.debian.org)

2018-10-08 Thread Debian Bug Tracking System
Your message dated Tue, 09 Oct 2018 03:00:34 +
with message-id 
and subject line Bug#899523: fixed in gauche-gl 0.6-3
has caused the Debian Bug report #899523,
regarding gauche-gl: Invalid maintainer address 
pkg-gauche-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.)


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

Dear uploader of gauche-gl,

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

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: gauche-gl
Source-Version: 0.6-3

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 09 Oct 2018 09:05:18 +0900
Source: gauche-gl
Binary: gauche-gl
Architecture: source
Version: 0.6-3
Distribution: unstable
Urgency: medium
Maintainer: NIIBE Yutaka 
Changed-By: NIIBE Yutaka 
Description:
 gauche-gl  - Gauche bindings for OpenGL
Closes: 899523
Changes:
 gauche-gl (0.6-3) unstable; urgency=medium
 .
   * debian/control (Standards-Version): Conforms to 4.2.1.
   (Build-Depends): This is for new gauche-dev (>= 0.9.6).
   (Maintainer): Don't use mailing list (Closes: #899523).
   * debian/compat: Upgrade to 11.
   * debian/rules (GZIP): Remove.
   (override_dh_auto_clean): Remove.
   (override_dh_auto_configure): Remove.
Checksums-Sha1:
 0e54b214691e60722d289f0c468651bc1ebabfc2 1500 gauche-gl_0.6-3.dsc
 eda7acaba5915d69a74fe4ff87c60a6059adab5a 32292 gauche-gl_0.6-3.debian.tar.xz
 d2b39979058899f8a6fde5531a4d76038a121b65 8876 gauche-gl_0.6-3_amd64.buildinfo
Checksums-Sha256:
 5e500969adeb5843df94fde698ee4896ce59eb9f6acc6b635ec6997652d8be11 1500 
gauche-gl_0.6-3.dsc
 8b98cc5e709f2e21e20872a2a94ff6749c96a23f2db187f0014071e91c794325 32292 
gauche-gl_0.6-3.debian.tar.xz
 b3f039ecfec99b5ac55e3e24e8f7716d72f4943cb62e4efd7227be5f7ba77ecf 8876 
gauche-gl_0.6-3_amd64.buildinfo
Files:
 96d6ea0eee177c1be85a1197cdcebd2b 1500 lisp optional gauche

Bug#853363: marked as done (cyphesis-cpp: ftbfs with GCC-7)

2018-10-08 Thread Debian Bug Tracking System
Your message dated Tue, 09 Oct 2018 03:00:18 +
with message-id 
and subject line Bug#853363: fixed in cyphesis-cpp 0.6.2-3
has caused the Debian Bug report #853363,
regarding cyphesis-cpp: ftbfs with GCC-7
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.)


-- 
853363: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853363
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:cyphesis-cpp
Version: 0.6.2-2
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/cyphesis-cpp_0.6.2-2_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
 from PythonScriptFactory.cpp:28:
/usr/include/Atlas-C++-0.6/Atlas/Message/Element.h: At global scope:
/usr/include/Atlas-C++-0.6/Atlas/Message/Element.h:364:27: warning: dynamic 
exception specifications are deprecated in C++11; use 'noexcept' instead 
[-Wdeprecated]
 IntType asInt() const throw (WrongTypeException)
   ^
/usr/include/Atlas-C++-0.6/Atlas/Message/Element.h:374:31: warning: dynamic 
exception specifications are deprecated in C++11; use 'noexcept' instead 
[-Wdeprecated]
 FloatType asFloat() const throw (WrongTypeException)
   ^
/usr/include/Atlas-C++-0.6/Atlas/Message/Element.h:384:27: warning: dynamic 
exception specifications are deprecated in C++11; use 'noexcept' instead 
[-Wdeprecated]
 PtrType asPtr() const throw (WrongTypeException)
   ^
/usr/include/Atlas-C++-0.6/Atlas/Message/Element.h:394:29: warning: dynamic 
exception specifications are deprecated in C++11; use 'noexcept' instead 
[-Wdeprecated]
 FloatType asNum() const throw (WrongTypeException)
 ^
/usr/include/Atlas-C++-0.6/Atlas/Message/Element.h:401:41: warning: dynamic 
exception specifications are deprecated in C++11; use 'noexcept' instead 
[-Wdeprecated]
 const std::string& asString() const throw (WrongTypeException)
 ^
/usr/include/Atlas-C++-0.6/Atlas/Message/Element.h:407:29: warning: dynamic 
exception specifications are deprecated in C++11; use 'noexcept' instead 
[-Wdeprecated]
 std::string& asString() throw (WrongTypeException)
 ^
/usr/include/Atlas-C++-0.6/Atlas/Message/Element.h:421:34: warning: dynamic 
exception specifications are deprecated in C++11; use 'noexcept' instead 
[-Wdeprecated]
 const MapType& asMap() const throw (WrongTypeException)
  ^
/usr/include/Atlas-C++-0.6/Atlas/Message/Element.h:427:22: warning: dynamic 
exception specifications are deprecated in C++11; use 'noexcept' instead 
[-Wdeprecated]
 MapType& asMap() throw (WrongTypeException)
  ^
/usr/include/Atlas-C++-0.6/Atlas/Message/Element.h:441:36: warning: dynamic 
exception specifications are deprecated in C++11; use 'noexcept' instead 
[-Wdeprecated]
 const ListType& asList() const throw (WrongTypeException)
^
/usr/include/Atlas-C++-0.6/Atlas/Message/Element.h:447:24: warning: dynamic 
exception specifications are deprecated in C++11; use 'noexcept' instead 
[-Wdeprecated]
 ListType& asList() throw (WrongTypeException)
^
rm -f librulesetbase.a
ar cru librulesetbase.a LocatedEntity.o EntityProperties.o AtlasProperties.o 
Container.o Script.o 
ar: `u' modifier ignored since `D' is the default (see `U')
ranlib 

Bug#910631: lightdm: first login hangs waiting for user-generated entropy

2018-10-08 Thread Jules Bernable
Package: lightdm
Version: 1.26.0-3
Severity: grave
Justification: renders package unusable

Dear Maintainer,

On my buster/sid system, LightDM hangs indefinitely on first login until
entropy is generated via mouse or keyboard input.
The login process seems to be delayed by the kernel itself, until the following
lines appear in journalctl:

kernel: random: crng init done
kernel: random: 7 urandom warning(s) missed due to ratelimiting

Installing the haveged package fixes the issue, as mentioned in the following
thread:
https://unix.stackexchange.com/questions/442698/when-i-log-in-it-hangs-until-
crng-init-done

This issue also seems related to bug #897572



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

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

Versions of packages lightdm depends on:
ii  adduser3.118
ii  dbus   1.12.10-1
ii  debconf [debconf-2.0]  1.5.69
ii  libaudit1  1:2.8.4-2
ii  libc6  2.27-6
ii  libgcrypt201.8.3-1
ii  libglib2.0-0   2.58.1-2
ii  libpam-systemd 239-10
ii  libpam0g   1.1.8-3.8
ii  libxcb11.13-3
ii  libxdmcp6  1:1.1.2-3
ii  lightdm-gtk-greeter [lightdm-greeter]  2.0.5-1
ii  lsb-base   9.20170808

Versions of packages lightdm recommends:
ii  xserver-xorg  1:7.7+19

Versions of packages lightdm suggests:
pn  accountsservice  
ii  upower   0.99.8-2
pn  xserver-xephyr   

-- Configuration Files:
/etc/lightdm/lightdm.conf changed [not included]

-- debconf information:
* shared/default-x-display-manager: lightdm
  lightdm/daemon_name: /usr/sbin/lightdm



Bug#882108: marked as done (xmonad is almost entirely nonfunctional)

2018-10-08 Thread Debian Bug Tracking System
Your message dated Tue, 9 Oct 2018 00:07:36 +
with message-id <20181009000736.oorim6ije66w7...@scru.org>
and subject line rc
has caused the Debian Bug report #882108,
regarding xmonad is almost entirely nonfunctional
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.)


-- 
882108: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882108
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xmonad
Version: 0.13-6
Severity: important

Dear Maintainer,

I have been using xmonad for a long while, and today upgraded to Buster. While
xmonad worked at first, after making a change to my configuration file, it
stopped working:

1. I can't run xmonad --recompile; it just says "Use Stack!"
2. Previously, I put xmonad in my .xsession and started it like that. Trying to
   do so causes it to fail, again saying "Use Stack!" in .xsession-errors, and
   kicks me back to the login screen.
3. Switching to select Xmonad in LightDM's WM list lets me log in properly, but
   then xmonad crashes after executing the startup scripts.
4. Trying to manually recover it with --replace also says "Use Stack!"
5. Removing my .xmonad directory lets me log in and xmonad does not crash, but
   none of the keybinds work so I cannot open programs, dmenu, etc.

It is, as a result, completely unusable.

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

Kernel: Linux 4.13.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 /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages xmonad depends on:
ii  libc6 2.24-17
ii  libffi6   3.2.1-6
ii  libgmp10  2:6.1.2+dfsg-1.1
ii  libx11-6  2:1.6.4-3
ii  libxext6  2:1.3.3-1+b2
ii  libxinerama1  2:1.1.3-1+b3
ii  libxrandr22:1.5.1-1
ii  x11-utils 7.7+3+b1

Versions of packages xmonad recommends:
ii  libghc-xmonad-dev  0.13-6
ii  libghc-xmonad-doc  0.13-6
ii  xfonts-base1:1.0.4+nmu1

Versions of packages xmonad suggests:
pn  gnome-session-flashback  
ii  suckless-tools [dmenu]   43-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Please reopen if you can reproduce this without a ~/.xmonad/build
that prints out "Use Stack!"--- End Message ---


Bug#910553: nautilus-dropbox: FTBFS in sid: Package 'gl', required by 'epoxy', not found

2018-10-08 Thread Andreas Beckmann
On 2018-10-08 22:46, Adrian Bunk wrote:
> Why is it using a 3 weeks old version of libepoxy-dev?

I thought I had rerun the spurious looking test on the weekend, but
somehow the old logfile was still there ...


Andreas



Bug#874727: closed by Anton Gladky (Bug#874727: fixed in coin3 3.1.4~abc9f50+dfsg2-1)

2018-10-08 Thread mlampert
I've attached an xml tool table.

* start FreeCAD from the command line
* Create a new document
* switch to "Path" Workbench
* start "Path Manager" from the Path menu
* import attached tooltable (note the file type selection)

You'll get:
Program received signal SIGSEGV, Segmentation fault.
#0  /lib/x86_64-linux-gnu/libc.so.6(+0x35fc0) [0x7f75fc00ffc0]
#1  /lib/x86_64-linux-gnu/libexpat.so.1(XML_SetHashSalt+0x1b) [0x7f75f584095b]
#2  /usr/lib/python2.7/lib-dynload/pyexpat.x86_64-linux-gnu.so(+0x75b0) 
[0x7f75c08145b0]
#3  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x94d6) 
[0x7f7602316c66]
#4  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x8e5f) 
[0x7f76023165ef]
#5  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x8e5f) 
[0x7f76023165ef]
#6  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x732) 
[0x7f760230d032]


I don't think the file itself matters at all because it segfaults while trying 
to initialise libexpat, but in case the attachment gets filtered, this is the 
content:























On Fri, 5 Oct 2018 10:03:26 +0200
Christoph Berg  wrote:

> Re: markus 2018-10-05 <20181004193807.40af399c@yolanda>
> > it's a packaging bug - libcoin is statically linked with libexpat,
> > and the version being used is outdated. So anything that uses
> > libcoin and libexpat will run into a segfault.
> > 
> > I am not aware of any other application that uses libcoin.  
> 
> I noticed because PostGIS is affected via postgis B-D -> libsfcgal-dev
> -> libsfcgal-osg1 -> libopenscenegraph100v5 -> libcoin80v5. Looking
> at https://udd.debian.org/cgi-bin/autoremovals.cgi there's quite a few
> packages depending on coin3. So the question whether this affects
> freecad only or more packages is making quite a difference.
> 
> Do you have a recipe on how to reproduce the bug with freecad from
> experimental?
> 
> Christoph



tt.xml
Description: XML document


Bug#910630: varnish-modules depends on cruft package libvarnishapi1

2018-10-08 Thread peter green

package: varnish-modules
version: 0.12.1-1+b1
severity: serious
x-debbugs-cc: team+varnish-t...@tracker.debian.org

varnish-modules depends on libvarnishapi1 which is no longer built by varnish, 
it seems to have been replaced by libvarnishapi2

There does not seem to have been any attempt to re-build the package in Debian proper for 
this transition, however when we tried to rebuild it in raspbian the build failed. 
http://buildd.raspbian.org/status/fetch.php?pkg=varnish-modules&arch=armhf&ver=0.12.1-1%2Bb1&stamp=1539021262

Note: I placed the x-debbugs-cc because varnish-modules has a dead maintainer address and 
the "name" parts of the maintainer field are the same between varnish and 
varnish-modules.



Processed: tagging 910517

2018-10-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 910517 + ftbfs
Bug #910517 [src:monero] monero: FTBFS on i386: compiler runs our of memory
Warning: Unknown package 'src:monero'
Added tag(s) ftbfs.
Warning: Unknown package 'src:monero'
> thanks
Stopping processing here.

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



Bug#873993: marked as done (FTBFS with Java 9 due to -source/-target only)

2018-10-08 Thread Debian Bug Tracking System
Your message dated Mon, 08 Oct 2018 23:14:36 +
with message-id 
and subject line Bug#873993: fixed in munin 2.0.42-1
has caused the Debian Bug report #873993,
regarding FTBFS with Java 9 due to -source/-target only
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.)


-- 
873993: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873993
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: munin
Version: 2.0.33
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

An automated tool has decided that this package will build fine if the
-source and -target options are changed to 1.6; no additional changes
are required. This was done by building with a compiler that changed
the settings automatically, then the real compiler, and diffing the
results. This modified compiler will never be part of Debian.

ant and Maven are supposed to do this for you, and I've tried to check
that this package is not using ant or Maven correctly, but I might have
messed up.

Build log sample:

touch build-java-stamp
/usr/lib/jvm/default-java/bin/javac -sourcepath plugins/javalib -d 
build/plugins/javalib -g -source 1.5 -target 1.5 -Xlint 
plugins/javalib/org/munin/plugin/jmx/AbstractAnnotationGraphsProvider.java
warning: [options] bootstrap class path not set in conjunction with -source 1.5
error: Source option 1.5 is no longer supported. Use 1.6 or later.
error: Target option 1.5 is no longer supported. Use 1.6 or later.
Makefile:50: recipe for target 
'plugins/javalib/org/munin/plugin/jmx/AbstractAnnotationGraphsProvider.class' 
failed
make[2]: *** 
[plugins/javalib/org/munin/plugin/jmx/AbstractAnnotationGraphsProvider.class] 
Error 2

Cheers,
Chris.
--- End Message ---
--- Begin Message ---
Source: munin
Source-Version: 2.0.42-1

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

Debian distribution maintenance software
pp.
Holger Levsen  (supplier of updated munin 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: Mon, 08 Oct 2018 21:56:32 +0100
Source: munin
Binary: munin-node munin-plugins-core munin-plugins-extra munin-plugins-java 
munin munin-common munin-async munin-doc
Architecture: source
Version: 2.0.42-1
Distribution: unstable
Urgency: low
Maintainer: Munin Debian Maintainers 
Changed-By: Holger Levsen 
Description:
 munin  - network-wide graphing framework (grapher/gatherer)
 munin-async - network-wide graphing framework (async master/client)
 munin-common - network-wide graphing framework (common)
 munin-doc  - network-wide graphing framework (documentation)
 munin-node - network-wide graphing framework (node)
 munin-plugins-core - network-wide graphing framework (plugins for node)
 munin-plugins-extra - network-wide graphing framework (user contributed 
plugins for nod
 munin-plugins-java - network-wide graphing framework (java plugins for node)
Closes: 675318 693402 700025 700298 717287 730030 732149 767018 767200 783499 
790009 808988 831464 837788 862238 863534 864845 873993 885454 896440 901729
Changes:
 munin (2.0.42-1) unstable; urgency=low
 .
   [ Lars Kruse ]
   * New upstream version 2.0.42.
   * New upstream version 2.0.41, Closes: #717287
   * New upstream version 2.0.38, fixing various issues, including bugs in:
 - postfix_mailstats: incorrect delivered message count (Closes: #675318)
 - quota_usage_: documentation deviates from behaviour (Closes: #730030)
 - munin outputs malformed XHTML (Closes: #732149)
 - iostat_ios: plugin should support configuration (Closes: #767018)
 - mysql_innodb: improve version detection (Closes: #901729)
   * mysql plugins: switch the "mysqluser" from "debian-sys-maint" to "root"
 in the plugin configuration.
 See munin-node.NEWS entry for details.
 (Closes: #862238, #864845)
   * fix trivial spelling mistakes below debian/ (thanks "codespell")
   * explicit

Bug#874132: marked as done (FTBFS with Java 9: import sun.misc..)

2018-10-08 Thread Debian Bug Tracking System
Your message dated Mon, 08 Oct 2018 23:16:42 +
with message-id 
and subject line Bug#874132: fixed in triplea 1.9.0.0.7062-2
has caused the Debian Bug report #874132,
regarding FTBFS with Java 9: import sun.misc..
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.)


-- 
874132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874132
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: triplea
Version: 1.8.0.9+dfsg
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9
Tags: fixed-upstream

This package fails to build with default-jdk pointing to openjdk-9-jdk.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

sun.misc is gone. The class using it seems to be gone from upstream. I'm
pretty sure I raised a bug about this somewhere but can't find it. Sorry
if this is a duplicate.

Build log:

[javac] 
/build/triplea-1.8.0.9+dfsg/src/games/strategy/util/ClassLoaderUtil.java:16: 
error: cannot find symbol
[javac] import sun.misc.URLClassPath;
[javac]^
[javac]   symbol:   class URLClassPath
[javac]   location: package sun.misc



Cheers,
Chris.
--- End Message ---
--- Begin Message ---
Source: triplea
Source-Version: 1.9.0.0.7062-2

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated triplea 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: Mon, 08 Oct 2018 23:02:12 +0200
Source: triplea
Binary: triplea
Architecture: source
Version: 1.9.0.0.7062-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Markus Koschany 
Description:
 triplea- Turn based strategy game
Closes: 874132
Changes:
 triplea (1.9.0.0.7062-2) unstable; urgency=medium
 .
   * Team upload.
   * Fix FTBFS with OpenJFX 11. (Closes: #874132)
   * Switch to compat level 11.
   * Declare compliance with Debian Policy 4.2.1.
Checksums-Sha1:
 bffcdc1d00c12eed65ad0b0725087bc303b7f542 2492 triplea_1.9.0.0.7062-2.dsc
 27c57766fdfd9feb452a3db58b8dd4eec9e331ab 49044 
triplea_1.9.0.0.7062-2.debian.tar.xz
 3a94c63d1757c4087ed2d784774bf042bf186d57 16623 
triplea_1.9.0.0.7062-2_amd64.buildinfo
Checksums-Sha256:
 3634cbc2950553ccf69e4501bb3007129d1ad8a77da77fbb640ce5596e86e137 2492 
triplea_1.9.0.0.7062-2.dsc
 4ad69dcfca1a9aa71209e9bc36307854aad364348c2617dea91e1cd99225d047 49044 
triplea_1.9.0.0.7062-2.debian.tar.xz
 44c736f0eeb1f10fdf7ae0805e03e25a3c838347817d5f4a25e4139337c4 16623 
triplea_1.9.0.0.7062-2_amd64.buildinfo
Files:
 d5f028815f04ac8c6f431a18f54fca0f 2492 games optional triplea_1.9.0.0.7062-2.dsc
 7c4b8adc63d523fb1142bcd0b1f0d1d8 49044 games optional 
triplea_1.9.0.0.7062-2.debian.tar.xz
 b4473fd682614ff379cf11be37d7a04b 16623 games optional 
triplea_1.9.0.0.7062-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAlu7xxxfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD
RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp
YW4ub3JnAAoJENmtFLlRO1Hk7gIQAIpKfceQo6/UDPlnisAcEIMA41sUSun405Ks
fWBLUItdLuDlPGQwQuhSbonF8rZZQdddcQsvoQNLvrUqaShk+mTvYz2vGT8gSpUP
NO9MCy4cfOUdzntl9PNXSYBA6brdcNEXS58kUVg/lJ/bbLdkFTmQdrc88WX2eDpC
iLIqggH0U1D9juc73Y1jCGXbKSLEWOPmrWf3v01y2sr1ZN/8gPGLpBJaKb9pKWC0
jVgUDK+S87RBzItp69xQZ39tGQziZxcTHHTqkdSDzVhlFnK2uBcAbv9p5EnwdWTT
eWNaD68vDmJWSK94aJ4vulne4m7fj92MdAjDst63lvqhEHM/Ao6ckIlFYFaYh1tx
WXfhak3I9uTDeK6budESMWuIcDRGJhlrieBx12HFVH9p3EM31AqEHEd8xSTRZH5j
aG9nbLxxTdoQPJri/mXR7VfayIag2XCV1+tDukqP51GWWsp3fgsrf8+GGfhZjMgO
EbIt5olXVk0jtWiySrt0QGAqYRq/5wrxCKaiphotwrKjm2Urve+ZjKd9rXI73I8E
kPKqHn3llh62U3cvgvQIH0r3a3PpOROQS4XHCyk+CiXf/gXg6dKWGREgbG8SDFmZ
NsxRmfo3D9UIABZ7D3a+8omNH/W71wKzCEQFJA7hvA2kjWnfDIHP7tYuBvfMtOmI
yGSh2Aqr
=Ti1B
-END PGP SIGNATURE End Message ---


Bug#900265: marked as done (jaxrs-api: FTBFS with Java 9 due to javax.xml.bind removal)

2018-10-08 Thread Debian Bug Tracking System
Your message dated Mon, 08 Oct 2018 23:07:20 +
with message-id 
and subject line Bug#900265: fixed in jaxrs-api 2.1.2-1
has caused the Debian Bug report #900265,
regarding jaxrs-api: FTBFS with Java 9 due to javax.xml.bind removal
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.)


-- 
900265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900265
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jaxrs-api
Severity: serious
Tags: sid buster
User: debian-j...@lists.debian.org
Usertags: default-java9

jaxrs-api has a test failing with Java 9 and later
due to the removal of the javax.xml.bind package:

  [ERROR] Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.163 
s <<< FAILURE! - in javax.ws.rs.core.JaxbLinkTest 
  [ERROR] testSerializationOfJaxbLink(javax.ws.rs.core.JaxbLinkTest) Time 
elapsed: 0.153 s <<< ERROR! javax.xml.bind.JAXBException: 
  Package javax.ws.rs.core with JAXB class javax.ws.rs.core.Link$JaxbLink 
defined in a module java.ws.rs must be open to at least 
  java.xml.bind module.
at 
java.ws.rs/javax.ws.rs.core.JaxbLinkTest.testSerializationOfJaxbLink(JaxbLinkTest.java:70)
--- End Message ---
--- Begin Message ---
Source: jaxrs-api
Source-Version: 2.1.2-1

We believe that the bug you reported is fixed in the latest version of
jaxrs-api, 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.
Emmanuel Bourg  (supplier of updated jaxrs-api 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: Mon, 08 Oct 2018 23:42:53 +0200
Source: jaxrs-api
Binary: libjaxrs-api-java
Architecture: source
Version: 2.1.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 libjaxrs-api-java - Java API for RESTful Services (JAX-RS)
Closes: 900265
Changes:
 jaxrs-api (2.1.2-1) unstable; urgency=medium
 .
   * New upstream release
 - Fixes the test failure with Java 9 (Closes: #900265)
 - Relocated the old javax.ws.rs:javax.ws.rs-api coordinates to the new ones
 - New build dependency on libmockito-java
   * Install the jar in /usr/share/java as jaxrs-api.jar but keep a 
compatibility
 link for javax.ws.rs-api.jar
   * Track the new releases from the eclipse-ee4j GitHub repository
   * Standards-Version updated to 4.2.1
   * Switch to debhelper level 11
   * Use salsa.debian.org Vcs-* URLs
Checksums-Sha1:
 90ad950fade07652930e0fc1740d4b6a0061a38a 2060 jaxrs-api_2.1.2-1.dsc
 99c77bb0d5a3902224c551904463755a86a353a2 124416 jaxrs-api_2.1.2.orig.tar.xz
 35fca968d931a17a7f952d8d985842e20127be7e 8732 jaxrs-api_2.1.2-1.debian.tar.xz
 c97f58fc75c2ad42e86859e754bf8100e820d9de 15987 
jaxrs-api_2.1.2-1_source.buildinfo
Checksums-Sha256:
 274390d48d2178c301abcf61b659e5c65607f3499c4c33ba01b74cc21e6fd826 2060 
jaxrs-api_2.1.2-1.dsc
 3615b69e6382b4d3ee6d7b3f127ef88eea2a8d0012a6a8500067ce82d5a95430 124416 
jaxrs-api_2.1.2.orig.tar.xz
 06a8da1fc679be4ace685b07edb8cfa5d64d149f1cdf2256f956211826cefbf5 8732 
jaxrs-api_2.1.2-1.debian.tar.xz
 7ab1bf31315fb930da8f6e0663bdae0c38dbc4a5c8978644c7d5ff3e733ba411 15987 
jaxrs-api_2.1.2-1_source.buildinfo
Files:
 3d6d0727981c9fbbf889f3a5a1f61449 2060 java optional jaxrs-api_2.1.2-1.dsc
 72d95dee02949f2926548671c3d59a39 124416 java optional 
jaxrs-api_2.1.2.orig.tar.xz
 da1d6d4ccc8153480f6275a3cf4d0264 8732 java optional 
jaxrs-api_2.1.2-1.debian.tar.xz
 5d2bf059c308cb4900c0131e178f3378 15987 java optional 
jaxrs-api_2.1.2-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAlu7z28SHGVib3VyZ0Bh
cGFjaGUub3JnAAoJEPUTxBnkudCsOXYP/0eu5Yn7Is27VDBtUtahNq28Q8NNsyHt
1R9TvJrT6lVDr0ydrOd3jp6jmizarnPTXQbzjzv4L5NvP7+ZvwIgEvMO9LfczVYg
pBoHB/hFxaI9LXHGTe8hN8Csa/HH1idveETgX2OF7Uruhih07qWzwB4xU9dR7Ac+
g6e+acqFZ1BIDyc5FieoYrockUTpsU/EYHeqipo0MqI0xC6Zvejn0/eHR8+avgbg
mIpoyFmQmsL8w6eK1ni6sMh1A+1DrRtY7zjDZBUwzXnqByJQ7Jxdhz5ULLmaxbMo
K0rBMnTLlHNMAZgvMzcXepYYD4X5p9sudWFSne2UBM5b5tRK4X04FwBeaUObxrM9
4zu2EN8b/Tbv6kbojnDBiJb05OMCepJdhGIljpHHW0WeHp2uaZjdPRUtNcXppxSb
toNexN7SRfJTPJ4ctq22ZfL9R6VoN0uz2senTAh/b0zFs/

Bug#910593: marked as done (davmail: missing versioned dependency on init-script-helpers)

2018-10-08 Thread Debian Bug Tracking System
Your message dated Mon, 08 Oct 2018 23:06:03 +
with message-id 
and subject line Bug#910593: fixed in davmail 4.9.0.2652-2
has caused the Debian Bug report #910593,
regarding davmail: missing versioned dependency on init-script-helpers
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.)


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

Dear Maintainer,

davmail's postinst unconditionally uses a new feature of update-rc.d:

update-rc.d davmail defaults-disabled

'defaults-disabled' is only available in init-system-helpers in a version
newer than that in stretch. This means that upgrades from stretch to sid
will fail if init-system-helpers is not upgraded before davmail.

(This also renders the package uploaded to stretch-backports completely
broken; it cannot be installed.)

regards
Stuart
--- End Message ---
--- Begin Message ---
Source: davmail
Source-Version: 4.9.0.2652-2

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

Debian distribution maintenance software
pp.
Alexandre Rossi  (supplier of updated davmail 
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: Mon, 08 Oct 2018 23:41:01 +0200
Source: davmail
Binary: davmail
Architecture: source all
Version: 4.9.0.2652-2
Distribution: unstable
Urgency: medium
Maintainer: Alexandre Rossi 
Changed-By: Alexandre Rossi 
Description:
 davmail- POP/IMAP/SMTP/CalDav/LDAP to Microsoft Exchange gateway
Closes: 910593
Changes:
 davmail (4.9.0.2652-2) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/watch: Use https protocol
 .
   [ Alexandre Rossi ]
   * workaround ci hosts lacking binfmt_misc support
   * embed used private JDK APIs
   * depend on init-system-helpers with defaults-disabled arg (Closes: #910593)
Checksums-Sha1:
 bdffe5e2ef113fda077de5041c9ddbe66e2a757b 2280 davmail_4.9.0.2652-2.dsc
 9751232a706438a5df232bebd8ef29c9292a5649 5535861 davmail_4.9.0.2652.orig.tar.gz
 e6898ad79314b1c7063c027989202dc5e3b15e41 18864 
davmail_4.9.0.2652-2.debian.tar.xz
 467e7b802b81d9cdf9f0ce400e2083483aabf2ba 683668 davmail_4.9.0.2652-2_all.deb
 f42cb32018d206fed79c213fd970469fcee7387b 12110 
davmail_4.9.0.2652-2_amd64.buildinfo
Checksums-Sha256:
 808d6ca35b2f61b9f9604c6e483e9f376b66b571c3eb4c7a2b3edc89a34b23fc 2280 
davmail_4.9.0.2652-2.dsc
 b8aa2d94473482f07f51f36def8815edd86ad9218b9ecb74ec869df9507630ab 5535861 
davmail_4.9.0.2652.orig.tar.gz
 c84ab35f70dd8480a2b99cf93dcb00f76bb9b5605e05502dc6459727cdee094e 18864 
davmail_4.9.0.2652-2.debian.tar.xz
 94d9efe8d3bf1385465550d09d1c436bcd703bb8c0e91ab31cb5a59f53198690 683668 
davmail_4.9.0.2652-2_all.deb
 cfa62408d27ba5cb5e4322e1616c41727fe4a78079d035f2c46fd83892b4aea3 12110 
davmail_4.9.0.2652-2_amd64.buildinfo
Files:
 f975b53802284eff21424438afdb58b7 2280 net optional davmail_4.9.0.2652-2.dsc
 fa1dbc3b70afa11d79909e9c3fc12212 5535861 net optional 
davmail_4.9.0.2652.orig.tar.gz
 2dcc5f18764b8b867921c0559a0918b1 18864 net optional 
davmail_4.9.0.2652-2.debian.tar.xz
 c0f4a5e392be9a54945d16faf3a59c2f 683668 net optional 
davmail_4.9.0.2652-2_all.deb
 500b1a9b2258382da4ef43d760896933 12110 net optional 
davmail_4.9.0.2652-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEqURFrS/GV/h4cdpsWI+eupOKFo8FAlu705EACgkQWI+eupOK
Fo/ZEw//bFwxa3Oze4CtwpcrCOTlQHeEgZNzGGZ3z1XxEIJkIDYdFmZfeALeLvg3
NSgzpY820XkzGeYDO1Pv+eyYcgYr+5DyMMPYMX5IlVp5TXtY8tIiHEOTTAnHi44M
lb6AuEe2NRAW7BQblqdkSjqadBRly+XyxOKiBjbNZmK0dgqg2Q3Vu9texuAvBP/a
o3Y8IyLckQRiu3B4IIunZsesf7ioqoRQpG0XYlm5fIyB0kPtV8XpRrduVrZaaAGo
f8EfmK8ksRqYDYKv/ULBTGk34RpS3CISdQ9Wr+dVgmsNvYZkXmROeWzJY60aJnx9
S3TnNcY/W3Gumz8RlQ7rUxljm3O7L+LbkeuoEtrsUV9sjsuYArAdOcsBn5KpGcUs
6/C9TpNblaAlAzmNmO+Dc5pDu5Ux6Qhfg8uLKS9eti9AnIDuwY2d6nlAvN54WkMg
0T41mOI16gvX7NKf3huuTnXrgVhDktltsjr2TvmDv00ZjeNQxRGn4FRANIYu77zL
Bh9yoZ4cliFp4Sw05Laxa8QnWaf7NGcS5cgPftQ6skg9X0fZMS3a9d0QNef/h3Mm
0qo/2N0/FcBFXJmAVN4GiwewPOewVHnkWQmZFIAWUeglNIfoQLIRNx4GwENS8lQU
lD9MvNWro6sv+vRqvYBxyc

Bug#873973: marked as done (FTBFS with Java 9 due to -source/-target only)

2018-10-08 Thread Debian Bug Tracking System
Your message dated Mon, 08 Oct 2018 23:05:52 +
with message-id 
and subject line Bug#873973: fixed in coco-java 20110419-3.2
has caused the Debian Bug report #873973,
regarding FTBFS with Java 9 due to -source/-target only
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.)


-- 
873973: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873973
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: coco-java
Version: 20110419
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

An automated tool has decided that this package will build fine if the
-source and -target options are changed to 1.6; no additional changes
are required. This was done by building with a compiler that changed
the settings automatically, then the real compiler, and diffing the
results. This modified compiler will never be part of Debian.

ant and Maven are supposed to do this for you, and I've tried to check
that this package is not using ant or Maven correctly, but I might have
messed up.

Build log sample:

make[1]: Entering directory '/build/coco-java-20110419'
javac -d . -source 1.4 -target 1.4 Trace.java Scanner.java Tab.java DFA.java 
ParserGen.java Parser.java Coco.java
warning: [options] bootstrap class path not set in conjunction with -source 1.4
error: Source option 1.4 is no longer supported. Use 1.6 or later.

Cheers,
Chris.
--- End Message ---
--- Begin Message ---
Source: coco-java
Source-Version: 20110419-3.2

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated coco-java 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: Mon, 08 Oct 2018 23:52:26 +0200
Source: coco-java
Binary: coco-java
Architecture: source
Version: 20110419-3.2
Distribution: unstable
Urgency: medium
Maintainer: Markus Loeberbauer 
Changed-By: Emmanuel Bourg 
Description:
 coco-java  - Coco/R Compiler Generator (Java Version)
Closes: 873973
Changes:
 coco-java (20110419-3.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fixed the build failure with Java 9 (Closes: #873973)
Checksums-Sha1:
 726ce3d90b51bd21c7454f326f16eed00e306b5e 1792 coco-java_20110419-3.2.dsc
 b4c0880d66c847e5061d76534e84ced95a583600 16317 coco-java_20110419-3.2.diff.gz
 2422af347fbadd95aaea4e7f801c902dd101b594 10909 
coco-java_20110419-3.2_source.buildinfo
Checksums-Sha256:
 9fd8b1f692ece69bd75d9cad7672b2671f73902f31bca88fd6acb7f595354b5f 1792 
coco-java_20110419-3.2.dsc
 e8655a53fdd6a0786ae7b9f0e022cfc4faff75f4956c5d521eac4401a8f75d36 16317 
coco-java_20110419-3.2.diff.gz
 7cf6c27dade544ec4017ab5496581815379dde1f4a0ad2f468d05633a3a93b91 10909 
coco-java_20110419-3.2_source.buildinfo
Files:
 d1dfb85e1d122f9542a283f8b79e6f43 1792 devel optional coco-java_20110419-3.2.dsc
 40e5637270497de7586665fadf73deda 16317 devel optional 
coco-java_20110419-3.2.diff.gz
 240449ccb540cff61e5a61a493cdd586 10909 devel optional 
coco-java_20110419-3.2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAlu70goSHGVib3VyZ0Bh
cGFjaGUub3JnAAoJEPUTxBnkudCsK84QAJ1EHESQn5urg/p96D/s153i2HStTVSD
BcQFaRgaTefrNJi3tLUgSD/zYV+9BidtnoQ/NEtD6e0SCDAqUv+mcneKpc5NkaRl
QfSOAPh6MAtZs1kDF3dzck32/tuBdh5jLmOhOHM6FIBIj8ggcaVGSl0yAHz2dnBH
Pnt0lss2auzzng/y/uu8j5oz9aHD26ss9T1RaujOB2BiOnY4wPvGvyv7a8jvMrPj
+iS9G5V36rT2EMr66SFXq5NyFiZ+46uen6sVLK4UGEkpYnGseiRY0qbCMLIdyza8
tUPL9lKrshwXJOnxLvs2rPqD0PeLGPZ7S8gRHZyeOu8atyfYi1Zsn0DE29DwB5GB
xfwq2aoBKQb/hyRJhDeX5igmmWFheIttqqadQ9Ws7d1cqwuFTPJqdbuyxHRLsLbb
61U1opo6jDppuoTRwaufbRsROd/jbIZq5TO2AummM0HfzbdkXSSrAZD4vE9d2Jn+
Q7Kx69WCaxdK93WUhQWgg+4eSaAV19+lrF/9eYZB2cA28BtnuWukmsna9rBQDq1g
+kZrvnso21uiVJUmEP90ME4/dSQOv+9jZGlZOc6CHNVYhfObm6rf9fADeu/Rk6SD
5rb/4bP76YbkUIwmZ9fzOe3eRXyeMJlToAGsdI8xz1XZ4nhXkMIoKyhto/0L4Cqz
G94pLNKfu8v6
=xCqg
-END PGP SIGNATURE End Mess

Bug#910444: Filesystems listed in /etc/fstab are no more automatically mounted since switching to OpenRC

2018-10-08 Thread Axel Beckert
Hi Benda,

Benda Xu wrote:
> Thank you for raising this up.  Are you using openrc with sysvinit-core?

As mentioned: yes

> @Axel, what is the output of `rc-update` of the said system?

2ping |  default
   alsa-utils |  sysinit
  anacron |  default
 apparmor |  sysinit
 avahi-daemon |  default
 bootlogd |  sysinit
 console-setup.sh |  default
 cpufrequtils |  default
 cron |  default
   cryptdisks |  sysinit
 cryptdisks-early |  sysinit
 dbus |  default
  dnssec-triggerd |  default
  gpm |  default
   hwclock.sh |  sysinit
  iodined |  default
keyboard-setup.sh |  sysinit
 kmod |  sysinit
linuxlogo |  default
  loadcpufreq |  default
 lvm2 |  sysinit
 lvm2-lvmetad |  default
lvm2-lvmpolld |  default
   miredo |  default
   nethack-common |  default
   networking |  sysinit
   ntpsec |  default
  nvi |  default
  openvpn |  default
  postfix |  default
 pppd-dns |  sysinit
   procps |  sysinit
rsync |  default
  rsyslog |  default
savecache |off  
   screen-cleanup |  sysinit
smartmontools |  default
  ssh |  default
 sshguard |  default
stop-bootlogd |  default
 stop-bootlogd-single |  sysinit
  tor |  default
 udev |  sysinit
  unbound |  default
  uptimed |  default
  wdm |  default
 wicd |  default
   x11-common |  sysinit

There's especially no mountall.sh or similar listed.

On one of my older OpenRC ruunning systems, there are quite some
"mount" items listed:

[…]
 mountall-bootclean.sh |  sysinit
  mountall.sh |  sysinit
 mountdevsubfs.sh |  sysinit
   mountkernfs.sh |  sysinit
 mountnfs-bootclean.sh |  sysinit
  mountnfs.sh |  sysinit
[…]

Both machines are running Unstable and have sysvinit-core and e.g.
initscripts at version 2.88dsf-59.10, but the newly installed one is
amd64 with UEFI while the old one is i386 with classic BIOS. Not sure
if that should make a difference.

> /etc/init.d/mountall.sh from initscripts is called by OpenRC by default
> to handle /etc/fstab.
> 
> Confirmation check: if you execute `invoke-rc.d mountall.sh start`
> instead of `mount -a`, does it work as well?

Yes. And then even swap is activated:

# i

Processed: Re: cvc3: FTBFS in API tests

2018-10-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> user debian-j...@lists.debian.org
Setting user to debian-j...@lists.debian.org (was ebo...@apache.org).
> usertag 902386 + default-java10
There were no usertags set.
Usertags are now: default-java10.
> retitle 902386 cvc3: FTBFS in API tests with Java 10 due to -d64 option 
> removal
Bug #902386 [src:cvc3] cvc3: FTBFS in API tests
Changed Bug title to 'cvc3: FTBFS in API tests with Java 10 due to -d64 option 
removal' from 'cvc3: FTBFS in API tests'.
>
End of message, stopping processing here.

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



Bug#906848: [Pkg-mozext-maintainers] Bug#906848: Bug#906848: xul-ext-adblock-plus-element-hiding-helper no longer works with firefox-esr 60

2018-10-08 Thread David Prévot
Hi,

Le 08/10/2018 à 11:29, David Prévot a écrit :

> Le 08/10/2018 à 11:05, Moritz Mühlenhoff a écrit :
>> On Tue, Aug 21, 2018 at 08:54:05PM +0300, Adrian Bunk wrote:
>>> Package: xul-ext-adblock-plus-element-hiding-helper

Ooops.

>> Seems dead upstream, no update in 1.5 years, let's remove?`
> 
> Upstream seems very much alive

Apologies, I missed the “-element-hiding-helper” part. Doesn’t seem
available for current Firefox, so no objection for removal on my part.

Regards

David



signature.asc
Description: OpenPGP digital signature


Bug#873501: kivy FTBFS with Cython 0.26

2018-10-08 Thread Dean Serenevy

I'm sorry for the delay - I missed or didn't get your reply and just saw it 
this morning - I should have checked the bug report sooner!

Shashank Kumar wrote:
> I tried applying the patch on
> https://salsa.debian.org/python-team/modules/kivy.git but it's not working.
> Could you please specify the steps you took in order to get to the solution?

I've created a git repo from the latest on salsa with my changes:

   https://github.com/duelafn/deb-kivy-873501

Built / tested in docker via:

 docker run -it debian:buster
 cd
 apt-get update
 apt-get install git dpkg-dev pristine-tar
 git clone https://github.com/duelafn/deb-kivy-873501 kivy
 cd kivy
 dpkg-checkbuilddeps
 apt-get install cython3 debhelper dh-python libgl1-mesa-dev libgles2-mesa-dev 
libgstreamer1.0-dev libsdl2-dev libsdl2-image-dev libsdl2-mixer-dev 
libsdl2-ttf-dev pkg-config python3-all-dev
 pristine-tar checkout ../kivy_1.10.1.orig.tar.gz
 dpkg-buildpackage -rfakeroot --unsigned-changes --unsigned-source --post-clean 
--diff-ignore


Note: Also builds in stretch as long as you have debhelper from backports 
installed.



signature.asc
Description: OpenPGP digital signature


Bug#906848: [Pkg-mozext-maintainers] Bug#906848: xul-ext-adblock-plus-element-hiding-helper no longer works with firefox-esr 60

2018-10-08 Thread David Prévot
Hi,

Le 08/10/2018 à 11:05, Moritz Mühlenhoff a écrit :
> On Tue, Aug 21, 2018 at 08:54:05PM +0300, Adrian Bunk wrote:
>> Package: xul-ext-adblock-plus-element-hiding-helper

> Seems dead upstream, no update in 1.5 years, let's remove?`

Upstream seems very much alive (last update of the WebExt addon less
than a month ago) : https://adblockplus.org/releases/

I can confirm that it works with current version of Firefox, it “just”
need someone to do the busy work of preparing the new package(s).

Regards

David



signature.asc
Description: OpenPGP digital signature


Bug#906876: xul-ext-scrapbook no longer works with firefox-esr 60

2018-10-08 Thread Moritz Mühlenhoff
On Tue, Aug 21, 2018 at 09:51:34PM +0300, Adrian Bunk wrote:
> Package: xul-ext-scrapbook
> Version: 1.5.13-3
> Severity: serious
> 
> XUL addons are no longer supported. 

Seems dead upstream, no release in over two years, let's remove?

Cheers,
Moritz



Bug#906848: xul-ext-adblock-plus-element-hiding-helper no longer works with firefox-esr 60

2018-10-08 Thread Moritz Mühlenhoff
On Tue, Aug 21, 2018 at 08:54:05PM +0300, Adrian Bunk wrote:
> Package: xul-ext-adblock-plus-element-hiding-helper
> Version: 1.3.8-1
> Severity: serious
> 
> XUL addons are no longer supported.
> 
> If it is confirmed that this package works with thunderbird 60,
> it might be an option to change the dependency to only thunderbird.

Seems dead upstream, no update in 1.5 years, let's remove?`

Cheers,
Moritz



Bug#908644: [Rsbackup-maint] Bug#908644: rsbackup: diff for NMU version 5.0-2.1

2018-10-08 Thread Matthew Vernon

On 08/10/18 21:38, Adrian Bunk wrote:

On Mon, Oct 08, 2018 at 08:53:57PM +0100, Matthew Vernon wrote:

Hi,


Hi Matthew,


On 27/09/18 19:09, Adrian Bunk wrote:


I've prepared an NMU for rsbackup (versioned as 5.0-2.1) and uploaded
it to DELAYED/14. Please feel free to tell me if I should cancel it.


Thanks, but the right answer is to upload 5.1-1, which I will be doing
shortly.


fine for me, I've canceled my NMU.

Note that the fix does not look as if it would depend on the upstream
version, please check that the new package would not FTBFS again if a
different automake version (e.g. 1.15 from stable) is installed.


I build a stretch package for my own purposes :)

Regards,

Matthew



Bug#910625: netperf: log files are not rotated

2018-10-08 Thread sergio
Package: netperf
Version: 2.6.0-2.1
Severity: serious
Justification: Policy 10.8


Netperf creates unlimited number of /var/log/netserver.debug_PID files (really
about 65K limited).

Policy 10.8 says: "Log files must be rotated occasionally so that they don’t 
grow"

Moreover Policy 10.8 says: "log files should be named /var/log/netperf.log"


Moreover it's not possible to change log file name. Looks like it's
hard-coded. Related bug #904394.


Bug#909993: marked as done (python-google-auth: FTBFS (AssertionError: Pattern 'Incorrect padding' not found))

2018-10-08 Thread Debian Bug Tracking System
Your message dated Mon, 08 Oct 2018 20:58:20 +
with message-id 
and subject line Bug#909993: fixed in python-google-auth 1.5.1-1
has caused the Debian Bug report #909993,
regarding python-google-auth: FTBFS (AssertionError: Pattern 'Incorrect 
padding' not found)
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.)


-- 
909993: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909993
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-google-auth
Version: 1.3.0-2
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
dh build-indep --buildsystem=python_distutils --with python2,python3
   dh_update_autotools_config -i -O--buildsystem=python_distutils
   dh_autoreconf -i -O--buildsystem=python_distutils
   dh_auto_configure -i -O--buildsystem=python_distutils
dh_auto_configure: Please use the third-party "pybuild" build system instead of 
python-distutils
dh_auto_configure: This feature will be removed in compat 12.
   dh_auto_build -i -O--buildsystem=python_distutils
dh_auto_build: Please use the third-party "pybuild" build system instead of 
python-distutils
dh_auto_build: This feature will be removed in compat 12.
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions

[... snipped ...]

tests/transport/test_requests.py ..  [ 94%]
tests/transport/test_urllib3.py .[100%]

 243 passed, 4 skipped in 21.73 seconds 
= test session starts ==
platform linux -- Python 3.7.0, pytest-3.6.4, py-1.6.0, pluggy-0.6.0
rootdir: /<>, inifile:
plugins: localserver-0.3.7
collected 247 items

tests/test__cloud_sdk.py [  4%]
tests/test__default.py ..[ 15%]
tests/test__helpers.py ..[ 22%]
tests/test__oauth2client.py .[ 26%]
tests/test__service_account_info.py  [ 27%]
tests/test_app_engine.py .   [ 33%]
tests/test_credentials.py    [ 38%]
tests/test_iam.py    [ 39%]
tests/test_jwt.py ..F.   [ 57%]
tests/compute_engine/test__metadata.py   [ 62%]
tests/compute_engine/test_credentials.py [ 63%]
tests/crypt/test__python_rsa.py ..   [ 71%]
tests/crypt/test_crypt.py .. [ 72%]
tests/oauth2/test__client.py ..  [ 76%]
tests/oauth2/test_credentials.py [ 77%]
tests/oauth2/test_id_token.py .. [ 80%]
tests/oauth2/test_service_account.py ... [ 86%]
tests/transport/test__http_client.py ... [ 89%]
tests/transport/test_grpc.py [ 90%]
tests/transport/test_requests.py ..  [ 94%]
tests/transport/test_urllib3.py .[100%]

=== FAILURES ===
___ test_decode_bad_token_not_base64 ___

def test_decode_bad_token_not_base64():
with pytest.raises((ValueError, TypeError)) as excinfo:
jwt.decode('1.2.3', PUBLIC_CERT_BYTES)
>   assert excinfo.match(r'Incorrect padding')
E   AssertionError: Pattern 'Incorrect padding' not found in 'Invalid 
base64-encoded string: length cannot be 1 more than a multiple of 4'

tests/test_jwt.py:121: AssertionError
=== 1 failed, 242 passed, 4 skipped in 21.91 seconds ===
make[1]: *** [debian/rules:14: override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:7: build-indep

Bug#908644: marked as done (rsbackup FTBFS with automake 1.16)

2018-10-08 Thread Debian Bug Tracking System
Your message dated Mon, 08 Oct 2018 20:58:53 +
with message-id 
and subject line Bug#908644: fixed in rsbackup 5.1-1
has caused the Debian Bug report #908644,
regarding rsbackup FTBFS with automake 1.16
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.)


-- 
908644: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908644
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rsbackup
Version: 5.0-2
Severity: serious
Tags: ftbfs

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

...
/usr/bin/make
make[1]: Entering directory '/build/1st/rsbackup-5.0'
CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/bash 
/build/1st/rsbackup-5.0/config.aux/missing aclocal-1.15 
/build/1st/rsbackup-5.0/config.aux/missing: line 81: aclocal-1.15: command not 
found
WARNING: 'aclocal-1.15' is missing on your system.
 You should only need it if you modified 'acinclude.m4' or
 'configure.ac' or m4 files included by 'configure.ac'.
 The 'aclocal' program is part of the GNU Automake package:
 
 It also requires GNU Autoconf, GNU m4 and Perl in order to run:
 
 
 
make[1]: *** [Makefile:394: aclocal.m4] Error 127
--- End Message ---
--- Begin Message ---
Source: rsbackup
Source-Version: 5.1-1

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

Debian distribution maintenance software
pp.
Matthew Vernon  (supplier of updated rsbackup 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: Mon, 08 Oct 2018 20:26:07 +0100
Source: rsbackup
Binary: rsbackup rsbackup-graph
Architecture: i386 source
Version: 5.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian rsbackup maintainers 
Changed-By: Matthew Vernon 
Closes: 908644
Description:
 rsbackup-graph - Graphics for rsync-based backup utility
 rsbackup   - rsync-based backup utility
Changes:
 rsbackup (5.1-1) unstable; urgency=medium
 .
   * New upstream version (Closes: #908644)
 .
 rsbackup (5.1) stable; urgency=medium
 .
   * Release 5.1
Checksums-Sha1:
 1c6ab9dde8318814273d0d052fda803fa6dde2cd 2127 rsbackup_5.1-1.dsc
 a98f3908fdc52900f85d949816ebf33238529e31 22620 rsbackup_5.1-1.diff.gz
 5087e1148ff458a222db5e63d929a072a7765d99 197216 rsbackup-graph_5.1-1_i386.deb
 c7a88bbae9fb7aba0fae53f605d54f9a430b5438 8706 rsbackup_5.1-1_i386.buildinfo
 4592af04f7a8b6a3aef58c41682b8f4c23599c39 278376 rsbackup_5.1-1_i386.deb
 8d56ad8be734023110580811ca10881a418f2ab7 346929 rsbackup_5.1.orig.tar.gz
 8d56ad8be734023110580811ca10881a418f2ab7 346929 rsbackup_5.1.orig.tar.gz
Checksums-Sha256:
 2c5d1d1e5766ececbe5346ce4f3e5469b4f9154ac026bc68071e6f14fa32e01f 2127 
rsbackup_5.1-1.dsc
 338ed739a36e623e1ffcfe4fc885a74a8fd56fa9ea649e3c4b6f0c2473daface 22620 
rsbackup_5.1-1.diff.gz
 3368da8fe3bfeb5ba7e73ecb75ed66866505514f2bedd0e2ca547b8119100a44 197216 
rsbackup-graph_5.1-1_i386.deb
 6cdf1ff1871fed58ee9e3e85e2dd519d18cc824ca7c4f83ac10e21f06d746149 8706 
rsbackup_5.1-1_i386.buildinfo
 44d0ef017ae8b61083cf06e086d9d59c902d6b38d14a04851543ab25d5c3bc44 278376 
rsbackup_5.1-1_i386.deb
 a4504cff9c13baf5d767f3e6b7647e65ee940da9d3f8703202634c08b45a1a17 346929 
rsbackup_5.1.orig.tar.gz
 a4504cff9c13baf5d767f3e6b7647e65ee940da9d3f8703202634c08b45a1a17 346929 
rsbackup_5.1.orig.tar.gz
Files:
 bfafb627d18f2ba4b4200272c1436600 2127 admin optional rsbackup_5.1-1.dsc
 a3a399bdde1dfdfe09799bcfd4fdf410 22620 admin optional rsbackup_5.1-1.diff.gz
 7e0930a6027397d92a73c1fc14971417 197216 admin optional 
rsbackup-graph_5.1-1_i386.deb
 ccbf2c63f0ef91064ab601bfb48c1e3e 8706 admin optional 
rsbackup_5.1-1_i386.buildinfo
 deaf69da80d327b65c58c17c5f754d73 278376 admin optional rsbackup_5.1-1_i386.deb
 324d405198679a9c28c0b561c3c39285 346929 admin optional rsbackup_5.1.orig.tar.gz
 324d405198679a9c28c0b561c3c39285 346929 admin optional rsbackup_5.1.orig.tar.gz

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEEuk75yE35bTf

Bug#906315: marked as done (spice: CVE-2018-10873: Missing check in demarshal.py:write_validate_array_item() allows for buffer overflow and denial of service)

2018-10-08 Thread Debian Bug Tracking System
Your message dated Mon, 08 Oct 2018 20:59:12 +
with message-id 
and subject line Bug#906315: fixed in spice 0.14.0-1.1
has caused the Debian Bug report #906315,
regarding spice: CVE-2018-10873: Missing check in 
demarshal.py:write_validate_array_item() allows for buffer overflow and denial 
of service
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.)


-- 
906315: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906315
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: spice
Version: 0.14.0-1
Severity: grave
Tags: patch security upstream
Control: clone -1 -2
Control: reassign -2 src:spice-gtk 0.34-1.1
Control: retitle -2 spice-gtk: CVE-2018-10873: Missing check in 
demarshal.py:write_validate_array_item() allows for buffer overflow and denial 
of service

Hi,

The following vulnerability was published for spice.

CVE-2018-10873[0]:
|Missing check in demarshal.py:write_validate_array_item() allows for
|buffer overflow and denial of service

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-10873
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10873
[1] http://www.openwall.com/lists/oss-security/2018/08/17/1
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1596008
[3] 
https://gitlab.freedesktop.org/spice/spice-common/commit/bb15d4815ab586b4c4a20f4a565970a44824c42c

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: spice
Source-Version: 0.14.0-1.1

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated spice 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: Sat, 15 Sep 2018 09:15:28 +0200
Source: spice
Binary: libspice-server1 libspice-server-dev
Architecture: source
Version: 0.14.0-1.1
Distribution: unstable
Urgency: medium
Maintainer: Liang Guo 
Changed-By: Salvatore Bonaccorso 
Closes: 906315
Description: 
 libspice-server-dev - Header files and development documentation for 
spice-server
 libspice-server1 - Implements the server side of the SPICE protocol
Changes:
 spice (0.14.0-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix flexible array buffer overflow (CVE-2018-10873) (Closes: #906315)
Checksums-Sha1: 
 71ebe34255c4abcf52a41315f49eb1e8008f3e23 2797 spice_0.14.0-1.1.dsc
 1b16799e20b1ed19da6d9128d2439411cfce57cb 14580 spice_0.14.0-1.1.debian.tar.xz
Checksums-Sha256: 
 d562374db9d11204aa8e2473afb7a7cf868596f5cd6cae5d88f0de3b2ca68026 2797 
spice_0.14.0-1.1.dsc
 bd31e9f626f44ef703c7911a8818b0e48ef6b03d0e1b97e98713f134b9242132 14580 
spice_0.14.0-1.1.debian.tar.xz
Files: 
 62de5aac34be4280e7d27059e5b099d0 2797 misc optional spice_0.14.0-1.1.dsc
 77f17ab592ff4cfd2421f393a5dda9c6 14580 misc optional 
spice_0.14.0-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAlu5F0dfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89EzZoP/0sg4fyMngxmzuHojExSCAwH84x4IN0t
eWCmsFAa4yV6QYiWtiTvk1TDUmT15h8aH35ihHegmxZgdi8jClOEl9gKKzXXMPdG
yo/0qcLUa7hOPQdwMSwFRXUdn9vGxBg5BfI7ibDaZe3JWHrkbwUhLNWbRgM4um2C
Z/pyS5wAZYEoA52zpLWyOyaPXCO+nESEfECU/s075F6vrX4n3/tyAx7p3hZQB0YC
Uaqoqnoczutbin7+o58jjN2IfmPZ7TvJfk/Bi3iWtuU0wHYUk0fMa0pAaXlXOEPL
uTWkVJ35+hQ6Mfdf3gDd6DT9puk0xIsBdqGHCu9i5foiobG/bP+Me+98jj31VhrF
eaXwzNHN0fpwl8u2mArHHzTbGyhA/3m5LAsiK7ss4NexFBCyKapZ5FdF5snhTLT7
2HdSd2Bo5zIVE/pun88i+iNZd1LGdoW/VXKDO2ycxzX+KYtW4GXi26eQkF25+Fvj
Tj4nU1rDV/2VCs/Kg9qIteCOc37pRv32ziXBIRIsNfkI4ykEzBP0Ji/O06+HE8bS
wO6O0lxVqk9quH/HEkDFRF0dqw3Y2/03eOa/piSMb7w3RNLl4RYwhgNgAz7wC7hL
vzxcpnUoNGoKN4E9/46bEO/KZK5m6yNZ4gMJ3hI29VXp4qV9LwbXKRHsJeAMkLBL
P0zahIpMAJTi
=bfU7
-END PGP SIGNATURE End Message ---


Bug#910553: marked as done (nautilus-dropbox: FTBFS in sid: Package 'gl', required by 'epoxy', not found)

2018-10-08 Thread Debian Bug Tracking System
Your message dated Mon, 8 Oct 2018 23:46:15 +0300
with message-id <20181008204615.GA18588@localhost>
and subject line Re: Bug#910553: nautilus-dropbox: FTBFS in sid: Package 'gl', 
required by 'epoxy', not found
has caused the Debian Bug report #910553,
regarding nautilus-dropbox: FTBFS in sid: Package 'gl', required by 'epoxy', 
not found
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.)


-- 
910553: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910553
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nautilus-dropbox
Version: 2015.10.28-1
Severity: serious
Tags: sid buster
Justification: fails to build from source (but built successfully in the past)

Hi,

nautilus-dropbox cannot be built any longer in a current sid pbuilder
environment:

...
checking for NAUTILUS... no
configure: error: Package requirements (libnautilus-extension >= 2.16.0) were 
not met:

Package 'gl', required by 'epoxy', not found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables NAUTILUS_CFLAGS
and NAUTILUS_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.


Cheers,

Andreas


nautilus-dropbox_2015.10.28-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
On Mon, Oct 08, 2018 at 02:26:52AM +0200, Andreas Beckmann wrote:
> Source: nautilus-dropbox
> Version: 2015.10.28-1
> Severity: serious
> Tags: sid buster
> Justification: fails to build from source (but built successfully in the past)
> 
> Hi,
> 
> nautilus-dropbox cannot be built any longer in a current sid pbuilder
> environment:

Why is it using a 3 weeks old version of libepoxy-dev?

Selecting previously unselected package libepoxy-dev:amd64.
Preparing to unpack .../243-libepoxy-dev_1.5.2-0.1_amd64.deb ...
Unpacking libepoxy-dev:amd64 (1.5.2-0.1) ...

> ...
> checking for NAUTILUS... no
> configure: error: Package requirements (libnautilus-extension >= 2.16.0) were 
> not met:
> 
> Package 'gl', required by 'epoxy', not found
>...

This was #909173, closing.

> Cheers,
> 
> Andreas

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed--- End Message ---


Bug#906854: xul-ext-firexpath no longer works with firefox-esr 60

2018-10-08 Thread Moritz Mühlenhoff
On Tue, Aug 21, 2018 at 09:00:13PM +0300, Adrian Bunk wrote:
> Package: xul-ext-firexpath
> Version: 0.9.7.1-3
> Severity: serious
> 
> XUL addons are no longer supported.

Seems dead upstream, let's remove?

Cheers,
Moritz



Bug#906860: xul-ext-mozvoikko no longer works with firefox-esr 60

2018-10-08 Thread Moritz Mühlenhoff
On Tue, Aug 28, 2018 at 10:08:51AM +0300, Timo Jyrinki wrote:
> Unfortunately upstream has removed the API that makes it possible to add
> external spellcheckers, and the upstream selected library for
> spellchecking is unable to properly support a language with a structure
> of Finnish.
> 
> Currently there is no other option than to live without spell-checking
> support in Mozilla products, and eg copy-paste to and back from a text
> editor for spell checking. Or use a full Voikko library compiled into
> Javascript with dependencies like at
> https://www.puimula.org/htp/testing/js-libvoikko/js-libvoikko-demo.html

Let's remove mozvoikko from the archive, then?

Cheers,
Moritz



Bug#906851: xul-ext-firegestures no longer works with firefox-esr 60

2018-10-08 Thread Moritz Mühlenhoff
On Tue, Aug 21, 2018 at 08:57:15PM +0300, Adrian Bunk wrote:
> Package: xul-ext-firegestures
> Version: 1.10.9-1
> Severity: serious
> 
> XUL addons are no longer supported.

Seems dead upstream, let's remove?

Cheers,
Moritz
 



Bug#908644: [Rsbackup-maint] Bug#908644: rsbackup: diff for NMU version 5.0-2.1

2018-10-08 Thread Matthew Vernon

Hi,

On 27/09/18 19:09, Adrian Bunk wrote:


I've prepared an NMU for rsbackup (versioned as 5.0-2.1) and uploaded
it to DELAYED/14. Please feel free to tell me if I should cancel it.


Thanks, but the right answer is to upload 5.1-1, which I will be doing 
shortly.


Regards,

Matthew



Bug#908644: [Rsbackup-maint] Bug#908644: rsbackup: diff for NMU version 5.0-2.1

2018-10-08 Thread Adrian Bunk
On Mon, Oct 08, 2018 at 08:53:57PM +0100, Matthew Vernon wrote:
> Hi,

Hi Matthew,

> On 27/09/18 19:09, Adrian Bunk wrote:
> 
> > I've prepared an NMU for rsbackup (versioned as 5.0-2.1) and uploaded
> > it to DELAYED/14. Please feel free to tell me if I should cancel it.
> 
> Thanks, but the right answer is to upload 5.1-1, which I will be doing
> shortly.

fine for me, I've canceled my NMU.

Note that the fix does not look as if it would depend on the upstream 
version, please check that the new package would not FTBFS again if a
different automake version (e.g. 1.15 from stable) is installed.

> Regards,
> 
> Matthew

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed



Processed: Re: [Pkg-erlang-devel] erlang 21.1+dfsg-1 causes rabbitmq-server to fail to start/install

2018-10-08 Thread Debian Bug Tracking System
Processing control commands:

> clone -1 -2
Bug #909941 {Done: Sergei Golovan } [src:erlang] 
rabbitmq-server: Fails to start
Bug 909941 cloned as bug 910623
> reassign -2 rabbitmq-server 3.6.10-1
Bug #910623 {Done: Sergei Golovan } [src:erlang] 
rabbitmq-server: Fails to start
Bug reassigned from package 'src:erlang' to 'rabbitmq-server'.
No longer marked as found in versions erlang/1:21.1+dfsg-1.
No longer marked as fixed in versions erlang/1:21.1+dfsg-2.
Bug #910623 {Done: Sergei Golovan } [rabbitmq-server] 
rabbitmq-server: Fails to start
Marked as found in versions rabbitmq-server/3.6.10-1.
> reopen -2
Bug #910623 {Done: Sergei Golovan } [rabbitmq-server] 
rabbitmq-server: Fails to start
Bug reopened
Ignoring request to alter fixed versions of bug #910623 to the same values 
previously set
> severity -2 grave
Bug #910623 [rabbitmq-server] rabbitmq-server: Fails to start
Severity set to 'grave' from 'serious'
> retitle -2 rabbitmq-server needs update for current erlang
Bug #910623 [rabbitmq-server] rabbitmq-server: Fails to start
Changed Bug title to 'rabbitmq-server needs update for current erlang' from 
'rabbitmq-server: Fails to start'.

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



Bug#909941: [Pkg-erlang-devel] erlang 21.1+dfsg-1 causes rabbitmq-server to fail to start/install

2018-10-08 Thread Paul Gevers
Control: clone -1 -2
Control: reassign -2 rabbitmq-server 3.6.10-1
Control: reopen -2
Control: severity -2 grave
Control: retitle -2 rabbitmq-server needs update for current erlang

On Mon, 8 Oct 2018 07:37:25 +0300 Sergei Golovan  wrote:
> Hi Paul,
> 
> On Sun, Oct 7, 2018 at 9:56 PM Paul Gevers  wrote:
> >
> > On 07-10-18 19:26, Paul Gevers wrote:
> > > On Sun, 30 Sep 2018 12:54:10 +0100 Jose Antonio Ortega Ruiz
> > >  wrote:
> > >> This version of the server fails to start using systemd:
> > >
> > > Yes, but until recently it worked. So this is a regression caused by
> > > some other package.
> 
> According to [1] rabbitmq-server doesn't work with Erlang 21 prior to
> version 3.7.7,
> so I guess I can't do much with this bug except probably adding the
> 'breaks' header
> to debian/control.
> 
> It's just time to update rabbitmq-server.

So, cloning and reassigning back. It seems rabbitmq-server needs an
update to work.

Paul



signature.asc
Description: OpenPGP digital signature


Processed: [bts-link] source package meson

2018-10-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package meson
> # 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 #909851 (http://bugs.debian.org/909851)
> # Bug title: meson fails: AttributeError: 'list' object has no attribute 
> 'absolute_path'
> #  * https://github.com/mesonbuild/meson/pull/4308
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 909851 + fixed-upstream
Bug #909851 [meson] meson fails: AttributeError: 'list' object has no attribute 
'absolute_path'
Added tag(s) fixed-upstream.
> usertags 909851 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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



Processed: [bts-link] source package src:maven-plugin-tools

2018-10-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package src:maven-plugin-tools
> # 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 #898821 (http://bugs.debian.org/898821)
> # Bug title: maven-plugin-tools: FTBFS with Java 10 due to 
> com.sun.tools.doclets removal
> #  * http://issues.apache.org/jira/browse/MPLUGIN-339
> #  * remote status changed: Open -> Closed
> #  * remote resolution changed: (?) -> Won-t-Fix
> #  * closed upstream
> tags 898821 + fixed-upstream
Bug #898821 [src:maven-plugin-tools] maven-plugin-tools: FTBFS with Java 10 due 
to com.sun.tools.doclets removal
Added tag(s) fixed-upstream.
> usertags 898821 - status-Open
Usertags were: status-Open.
Usertags are now: .
> usertags 898821 + status-Closed resolution-Won-t-Fix
There were no usertags set.
Usertags are now: resolution-Won-t-Fix status-Closed.
> thanks
Stopping processing here.

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



Bug#909993: Bug #909993 in python-google-auth marked as pending

2018-10-08 Thread Christoph Berg
Control: tag -1 pending

Hello,

Bug #909993 in python-google-auth reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/openstack-team/python/python-google-auth/commit/2ea747767e77c899ce104fdf9e21bbe4d698ff4a


New upstream version 1.5.1

Fixes AssertionError: Pattern 'Incorrect padding' not found.
(Closes: #909993)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/909993



Processed: Bug #909993 in python-google-auth marked as pending

2018-10-08 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #909993 [src:python-google-auth] python-google-auth: FTBFS (AssertionError: 
Pattern 'Incorrect padding' not found)
Added tag(s) pending.

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



Processed: severity of 910593 is serious

2018-10-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 910593 serious
Bug #910593 [davmail] davmail: missing versioned dependency on 
init-script-helpers
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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



Bug#910216: marked as done (epoptes-client: removed shipped file: /etc/network/if-up.d/epoptes-client)

2018-10-08 Thread Debian Bug Tracking System
Your message dated Mon, 08 Oct 2018 19:34:02 +
with message-id 
and subject line Bug#910216: fixed in epoptes 1.0.1-2
has caused the Debian Bug report #910216,
regarding epoptes-client: removed shipped file: 
/etc/network/if-up.d/epoptes-client
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.)


-- 
910216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910216
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: epoptes-client
Version: 1.0.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package removes files that
it has shipped.

>From the attached log (scroll to the bottom...):

1m6.1s ERROR: FAIL: debsums reports modifications inside the chroot:
  debsums: missing file /etc/network/if-up.d/epoptes-client (from 
epoptes-client package)

This was observed after a stretch->buster upgrade.


cheers,

Andreas


epoptes-client_1.0.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: epoptes
Source-Version: 1.0.1-2

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

Debian distribution maintenance software
pp.
Vagrant Cascadian  (supplier of updated epoptes 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: Mon, 08 Oct 2018 12:14:26 -0700
Source: epoptes
Binary: epoptes epoptes-client
Architecture: source
Version: 1.0.1-2
Distribution: unstable
Urgency: medium
Maintainer: Epoptes Developers 
Changed-By: Vagrant Cascadian 
Description:
 epoptes- Computer lab management tool
 epoptes-client - Computer lab management tool (client)
Closes: 910095 910216
Changes:
 epoptes (1.0.1-2) unstable; urgency=medium
 .
   * Change Build-Depends to python3:any (Closes: #910095).
   * Remove conffiles using dpkg-maintscript-helper (Closes: #910216).
Checksums-Sha1:
 41d75815ea9fabc5f0b5f7db8f3b8fc47b6f853e 1481 epoptes_1.0.1-2.dsc
 19ad4ae48fff8183c002a39560a635f8c6622647 9520 epoptes_1.0.1-2.debian.tar.xz
 273503e80e9a51f9cccf71cc56db05f5e8bf098d 6360 epoptes_1.0.1-2_amd64.buildinfo
Checksums-Sha256:
 b85370eb5ada84d6118ac7e440d98d81d744f8a2dcd6f6f43eefa2abbb2a6931 1481 
epoptes_1.0.1-2.dsc
 a6d3c7fb628379c5c175d19b8b3a42b59dcc928865e21b882d447b393b97c1f1 9520 
epoptes_1.0.1-2.debian.tar.xz
 d2c7f86152ca255fbdaf9c0a3ba5869c0a31fe24aeae7aa1b2f0d12ed587c106 6360 
epoptes_1.0.1-2_amd64.buildinfo
Files:
 61771e4b2aa609821123983eb2632ea3 1481 admin optional epoptes_1.0.1-2.dsc
 b9f9baa573eaff0a121409fac0b9591b 9520 admin optional 
epoptes_1.0.1-2.debian.tar.xz
 ab45cb165c04f29a9bf45bcf92defc0b 6360 admin optional 
epoptes_1.0.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iIkEARYKADEWIQRlgHNhO/zFx+LkXUXcUY/If5cWqgUCW7utIhMcdmFncmFudEBk
ZWJpYW4ub3JnAAoJENxRj8h/lxaq5kQBAOsveud5WcVCUxVovi/kYGrNlr84OEuI
CcRFNpUGKCsCAP4uMPh7L/CCadwnMkbzorPziyfwVMRYTHiWYxjy0egQDw==
=qsRh
-END PGP SIGNATURE End Message ---


Processed: tagging 910447

2018-10-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 910447 + buster sid
Bug #910447 {Done: Thomas Goirand } [python-taskflow] glance 
FTBFS: tests fail?
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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



Processed: affects 910443

2018-10-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> affects 910443 src:gir-to-d
Bug #910443 [meson] gir-to-d FTBFS: Error: Expected argument to '-I'
Added indication that 910443 affects src:gir-to-d
> thanks
Stopping processing here.

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



Bug#910348: marked as done (linux-headers-4.19.0-rc6-amd64: File scripts/subarch.include is missing)

2018-10-08 Thread Debian Bug Tracking System
Your message dated Mon, 08 Oct 2018 19:00:11 +
with message-id 
and subject line Bug#910348: fixed in linux 4.19~rc7-1~exp1
has caused the Debian Bug report #910348,
regarding linux-headers-4.19.0-rc6-amd64: File scripts/subarch.include is 
missing
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.)


-- 
910348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910348
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-headers-4.19.0-rc6-amd64
Version: 4.19~rc6-1~exp1
Severity: normal

Dear Maintainer,

I try to recompile the virtualbox kernel module. But this did not happen. The
log file told me that:
DKMS make.log for virtualbox-5.2.18 for kernel 4.19.0-rc6-amd64 (x86_64)
Fri  5 Oct 08:05:30 CEST 2018
make: Entering directory '/usr/src/linux-headers-4.19.0-rc6-amd64'
/usr/src/linux-headers-4.19.0-rc6-common/Makefile:302: scripts/subarch.include:
No such file or directory
make[2]: *** No rule to make target 'scripts/subarch.include'.  Stop.
make[2]: *** Waiting for unfinished jobs
make[1]: *** [Makefile:146: sub-make] Error 2
make: *** [Makefile:8: all] Error 2
make: Leaving directory '/usr/src/linux-headers-4.19.0-rc6-amd64'

After install the file scripts/subarch.include it works.

It is new in rc5

Links:
https://fossies.org/diffs/linux/4.19-rc4_vs_4.19-rc5/Makefile-diff.html
https://patchwork.kernel.org/patch/10601895/






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

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

Versions of packages linux-headers-4.19.0-rc6-amd64 depends on:
ii  linux-compiler-gcc-8-x86 4.19~rc6-1~exp1
ii  linux-headers-4.19.0-rc6-common  4.19~rc6-1~exp1
ii  linux-kbuild-4.194.19~rc6-1~exp1

linux-headers-4.19.0-rc6-amd64 recommends no packages.

linux-headers-4.19.0-rc6-amd64 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 4.19~rc7-1~exp1

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

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated linux 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: Sun, 07 Oct 2018 23:48:27 +0100
Source: linux
Binary: linux-source-4.19 linux-support-4.19.0-rc7 linux-doc-4.19 
linux-cpupower libcpupower1 libcpupower-dev usbip hyperv-daemons lockdep 
liblockdep4.19 liblockdep-dev linux-kbuild-4.19 linux-perf-4.19 
linux-bootwrapper-4.19.0-rc7 linux-headers-4.19.0-rc7-common linux-libc-dev 
linux-headers-4.19.0-rc7-all linux-headers-4.19.0-rc7-all-alpha 
linux-config-4.19 kernel-image-4.19.0-rc7-alpha-generic-di 
nic-modules-4.19.0-rc7-alpha-generic-di 
nic-wireless-modules-4.19.0-rc7-alpha-generic-di 
nic-shared-modules-4.19.0-rc7-alpha-generic-di 
serial-modules-4.19.0-rc7-alpha-generic-di 
usb-serial-modules-4.19.0-rc7-alpha-generic-di 
ppp-modules-4.19.0-rc7-alpha-generic-di 
pata-modules-4.19.0-rc7-alpha-generic-di 
cdrom-core-modules-4.19.0-rc7-alpha-generic-di 
scsi-core-modules-4.19.0-rc7-alpha-generic-di 
scsi-modules-4.19.0-rc7-alpha-generic-di 
loop-modules-4.19.0-rc7-alpha-generic-di 
btrfs-modules-4.19.0-rc7-alpha-generic-di 
ext4-modules-4.19.0-rc7-alpha-generic-di
 isofs-modules-4.19.0-rc7-alpha-generic-di 
jfs-modules-4.19.0-rc7-alpha-generic-di xfs-modules-4.19.0-rc7-alpha-generic-di 
fat-modules-4.19.0-rc7-alpha-generic-di md-modules-4.19.0-rc7-alpha-generic-di 
multipath-modules-4.19.0-rc7-alpha-generic-di 
usb-modules-4.19.0-rc7-alpha-generic-di 
usb-storage-modules-4.19.0-rc7-alpha-generic-di 
input-modules-4.19.0-rc7-alpha-generic-di 
event-modules-4.19.0-rc7

Bug#909628: marked as done (thunderbird: illegal instruction on non-SSE2 system)

2018-10-08 Thread Debian Bug Tracking System
Your message dated Mon, 08 Oct 2018 19:00:24 +
with message-id 
and subject line Bug#909628: fixed in thunderbird 1:60.2.1-1
has caused the Debian Bug report #909628,
regarding thunderbird: illegal instruction on non-SSE2 system
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.)


-- 
909628: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909628
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: thunderbird
Version: 1:60.0-3~deb9u1
Severity: important

Dear Maintainer,

This crash occurs every time I try to start Thunderbird, even in
--safe-mode or with -P to try to set up a new profile.  It didn't
occur before the upgrade to Thunderbird 60.

I've run it through gdb, and saved a log, the most relevant part of
which is as follows:

Thread 1 "thunderbird" received signal SIGILL, Illegal instruction.
0xb352c79f in alloc::slice::hack::to_vec::h87940800129e8dc6 (s=...)
at liballoc/slice.rs:167

I've saved more of the backtrace, etc., which I can attach, but
running
  $ gdb -ex run /usr/lib/thunderbird/thunderbird
left my system unusable for about 6 hours (probably because I have
only about three quarters of a gigabyte of RAM), so I hope I won't
need to run it again.

I strongly suspect that this is related to bug #908449, where Rust
was putting SSE2 instructions into Firefox 60 for i386, which it
shouldn't have done for the Debian distribution.


-- System Information:
Debian Release: 9.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

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

Versions of packages thunderbird depends on:
ii  debianutils   4.8.1.1
ii  fontconfig2.11.0-6.7+b1
ii  libatk1.0-0   2.22.0-1
ii  libc6 2.24-11+deb9u3
ii  libcairo-gobject2 1.14.8-1
ii  libcairo2 1.14.8-1
ii  libdbus-1-3   1.10.26-0+deb9u1
ii  libdbus-glib-1-2  0.108-2
ii  libevent-2.0-52.0.21-stable-3
ii  libffi6   3.2.1-6
ii  libfontconfig12.11.0-6.7+b1
ii  libfreetype6  2.6.3-3.2
ii  libgcc1   1:6.3.0-18+deb9u1
ii  libgdk-pixbuf2.0-02.36.5-2+deb9u2
ii  libglib2.0-0  2.50.3-2
ii  libgtk-3-03.22.11-1
ii  libgtk2.0-0   2.24.31-2
ii  libjsoncpp1   1.7.4-3
ii  libpango-1.0-01.40.5-1
ii  libpangocairo-1.0-0   1.40.5-1
ii  libpangoft2-1.0-0 1.40.5-1
ii  libstartup-notification0  0.12-4+b2
ii  libstdc++66.3.0-18+deb9u1
ii  libvpx4   1.6.1-3+deb9u1
ii  libx11-6  2:1.6.4-3
ii  libx11-xcb1   2:1.6.4-3
ii  libxcb-shm0   1.12-1
ii  libxcb1   1.12-1
ii  libxext6  2:1.3.3-1+b2
ii  libxrender1   1:0.9.10-1
ii  libxt61:1.1.5-1
ii  psmisc22.21-2.1+b2
ii  x11-utils 7.7+3+b1
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages thunderbird recommends:
ii  hunspell-en-us [hunspell-dictionary]  20070829-7
ii  lightning 1:60.0-3~deb9u1

Versions of packages thunderbird suggests:
pn  apparmor  
pn  fonts-lyx 
ii  libgssapi-krb5-2  1.15-1+deb9u1

-- no debconf information
tim@lazarus:~$ thunderbird 
ExceptionHandler::GenerateDump cloned child 1275
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
ExceptionHandler::WaitForContinueSignal waiting for continue signal...
tim@lazarus:~$ thunderbird --safe-mode
ExceptionHandler::GenerateDump cloned child 1290
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
ExceptionHandler::WaitForContinueSignal waiting for continue signal...
tim@lazarus:~$ thunderbird -P
ExceptionHandler::GenerateDump cloned child 1305
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
ExceptionHandler::WaitForContinueSignal waiting for continue signal...
tim@lazarus:~$ gdb -ex run /usr/lib/thunderbird/thunderbird
GNU gdb (Debian 7.12-6) 7.12.0.20161007-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warra

Bug#909464: marked as done (thunderbird: Thunderbird crash : Fontconfig error: failed reading config file)

2018-10-08 Thread Debian Bug Tracking System
Your message dated Mon, 08 Oct 2018 19:00:24 +
with message-id 
and subject line Bug#909039: fixed in thunderbird 1:60.2.1-1
has caused the Debian Bug report #909039,
regarding thunderbird: Thunderbird crash : Fontconfig error: failed reading 
config file
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.)


-- 
909039: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909039
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: thunderbird
Version: 1:60.0-3~deb9u1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

After upgrading Thunderbird from version 1:52.9.1-1 to version 1:60.0-3~deb9u1, 
Thunderbird crash at startup with error message:

$ thunderbird --verbose
INFO  -> [[ ... using verbose mode ... ]]
DEBUG -> Found folder /home/toto/.icedove, found a symlink 
/home/toto/.thunderbird pointing to /home/toto/.icedove
DEBUG -> call '/usr/lib/thunderbird/thunderbird '
Fontconfig error: failed reading config file
alloc factor 0,90 0,90
alloc factor 0,90 0,90
ExceptionHandler::GenerateDump cloned child 4962
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
ExceptionHandler::WaitForContinueSignal waiting for continue signal...


Regards.


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

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

Versions of packages thunderbird depends on:
ii  debianutils   4.8.6
ii  fontconfig2.13.0-5
ii  libatk1.0-0   2.30.0-1
ii  libc6 2.27-6
ii  libcairo-gobject2 1.15.12-1
ii  libcairo2 1.15.12-1
ii  libdbus-1-3   1.12.10-1
ii  libdbus-glib-1-2  0.110-3
ii  libevent-2.0-52.0.21-stable-3
ii  libffi6   3.2.1-8
ii  libfontconfig12.13.0-5
ii  libfreetype6  2.8.1-2
ii  libgcc1   1:8.2.0-7
ii  libgdk-pixbuf2.0-02.38.0+dfsg-6
ii  libglib2.0-0  2.58.1-2
ii  libgtk-3-03.24.0-3
ii  libgtk2.0-0   2.24.32-3
ii  libjsoncpp1   1.7.4-3
ii  libpango-1.0-01.42.4-3
ii  libpangocairo-1.0-0   1.42.4-3
ii  libpangoft2-1.0-0 1.42.4-3
ii  libstartup-notification0  0.12-5
ii  libstdc++68.2.0-7
ii  libvpx4   1.6.1-3+deb9u1
ii  libx11-6  2:1.6.6-1
ii  libx11-xcb1   2:1.6.6-1
ii  libxcb-shm0   1.13-3
ii  libxcb1   1.13-3
ii  libxext6  2:1.3.3-1+b2
ii  libxrender1   1:0.9.10-1
ii  libxt61:1.1.5-1
ii  psmisc23.1-1+b1
ii  x11-utils 7.7+4
ii  zlib1g1:1.2.11.dfsg-1

Versions of packages thunderbird recommends:
ii  hunspell-en-gb [hunspell-dictionary] 1:6.1.0~rc2-3
ii  hunspell-en-us [hunspell-dictionary] 1:2018.04.16-1
ii  hunspell-fr-classical [hunspell-dictionary]  1:6.3-1
ii  lightning1:60.0-3~deb9u1

Versions of packages thunderbird suggests:
ii  apparmor  2.13-8
ii  fonts-lyx 2.3.1-2-1
ii  libgssapi-krb5-2  1.16-2

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: thunderbird
Source-Version: 1:60.2.1-1

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

Debian distribution maintenance software
pp.
Carsten Schoenert  (supplier of updated thunderbird 
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, 05 Oct 2018 17:43:49 +0200
Source: thunderbird
Binary: thunderbird lightning calendar-google-provider thunderbird-l10n-all 
thunderbird-l10n-ar thunderbird-l10n-ast thunderbird-l10n-be 

Bug#909039: marked as done (thunderbird: Crash when starting Thunderbird after latest security update to 1:60.0-3~deb9u1)

2018-10-08 Thread Debian Bug Tracking System
Your message dated Mon, 08 Oct 2018 19:00:24 +
with message-id 
and subject line Bug#909039: fixed in thunderbird 1:60.2.1-1
has caused the Debian Bug report #909039,
regarding thunderbird: Crash when starting Thunderbird after latest security 
update to 1:60.0-3~deb9u1
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.)


-- 
909039: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909039
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: thunderbird
Version: 1:60.0-3~deb9u1
Severity: grave
Tags: upstream
Justification: renders package unusable

After the latest security update for Stretch Thunderbird was no longer usable
for one family member because it crashed right after starting.

The reason and the fix are described here:
https://bugzilla.mozilla.org/show_bug.cgi?id=1482248

A local fix is removing or renaming all local mail files which use a wrong
encoding in their file name.



-- System Information:
Debian Release: 9.5
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 
'proposed-updates'), (10, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages thunderbird depends on:
ii  debianutils   4.8.1.1
ii  fontconfig2.11.0-6.7+b1
ii  libatk1.0-0   2.22.0-1
ii  libc6 2.24-11+deb9u3
ii  libcairo-gobject2 1.14.8-1
ii  libcairo2 1.14.8-1
ii  libdbus-1-3   1.10.26-0+deb9u1
ii  libdbus-glib-1-2  0.108-2
ii  libevent-2.0-52.0.21-stable-3
ii  libffi6   3.2.1-6
ii  libfontconfig12.11.0-6.7+b1
ii  libfreetype6  2.6.3-3.2
ii  libgcc1   1:6.3.0-18+deb9u1
ii  libgdk-pixbuf2.0-02.36.5-2+deb9u2
ii  libglib2.0-0  2.50.3-2
ii  libgtk-3-03.22.11-1
ii  libgtk2.0-0   2.24.31-2
ii  libjsoncpp1   1.7.4-3
ii  libpango-1.0-01.40.5-1
ii  libpangocairo-1.0-0   1.40.5-1
ii  libpangoft2-1.0-0 1.40.5-1
ii  libstartup-notification0  0.12-4+b2
ii  libstdc++66.3.0-18+deb9u1
ii  libvpx4   1.6.1-3+deb9u1
ii  libx11-6  2:1.6.4-3
ii  libx11-xcb1   2:1.6.4-3
ii  libxcb-shm0   1.12-1
ii  libxcb1   1.12-1
ii  libxext6  2:1.3.3-1+b2
ii  libxrender1   1:0.9.10-1
ii  libxt61:1.1.5-1
ii  psmisc22.21-2.1+b2
ii  x11-utils 7.7+3+b1
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages thunderbird recommends:
ii  hunspell-en-us [hunspell-dictionary] 20070829-7
ii  hunspell-fr-classical [hunspell-dictionary]  1:5.7-1
ii  lightning1:60.0-3~deb9u1
ii  myspell-de-at [myspell-dictionary]   20161207-1
ii  myspell-de-ch [myspell-dictionary]   20161207-1
ii  myspell-de-de [myspell-dictionary]   20161207-1

Versions of packages thunderbird suggests:
pn  apparmor  
ii  fonts-lyx 2.2.2-1
ii  libgssapi-krb5-2  1.15-1+deb9u1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: thunderbird
Source-Version: 1:60.2.1-1

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

Debian distribution maintenance software
pp.
Carsten Schoenert  (supplier of updated thunderbird 
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, 05 Oct 2018 17:43:49 +0200
Source: thunderbird
Binary: thunderbird lightning calendar-google-provider thunderbird-l10n-all 
thunderbird-l10n-ar thunderbird-l10n-ast thunderbird-l10n-be 
thunderbird-l10n-bg thunderbird-l10n-br thunderbird-l10n-ca thunderbird-l10n-cs 
thunderbird-l10n-cy thunderbird-l10n-da thunderbird-l1

Bug#910066: marked as done (Block PHP 7.0 from re-entering the testing)

2018-10-08 Thread Debian Bug Tracking System
Your message dated Mon, 08 Oct 2018 18:56:55 +
with message-id 
and subject line Bug#910071: Removed package(s) from unstable
has caused the Debian Bug report #910066,
regarding Block PHP 7.0 from re-entering the testing
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.)


-- 
910066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910066
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:php7.0
Version: 7.0.31-1
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

This is just a blocker bug to keep PHP 7.0 re-entering the testing.

Ondrej

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

Kernel: Linux 4.17.0-1-amd64 (SMP w/6 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_US.UTF-8), LANGUAGE=en_DK.UTF-8 (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

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEEw2Gx4wKVQ+vGJel9g3Kkd++uWcIFAluzOBRfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEMz
NjFCMUUzMDI5NTQzRUJDNjI1RTk3RDgzNzJBNDc3RUZBRTU5QzIACgkQg3Kkd++u
WcLjfA/+NBCr5FskG7FfnMey9Zo3/AOCSWJxeTtPKPl9OomOGnTVy+mJzLL86a9A
rUPXf2SDorLtiJ+p0yCfkhycuPIYqyhpBfZtyugmIYaf44V8zbRa99ITfDE1VX08
PYaR8IivGBuIb0n/oADQsNkAVHoseo2oS5F/qb9kDQg4VkqX5yF9bYhfr7dQc08G
+To2y/tBPls3/QDO67PDz5Tza6TQiDz7urPdzrqJmUpUq8wRYZU2JEPTI03V0AKr
h8mnWmR7aB7bjt4hYH3+BcLi4A7O2V8JYovGDtTXt+uIqctJ+xwRZLBuSQhfsiLr
lU8aKd2SIIPzHej2LRkB8YRiyJQFDm8hCfX3KTyc14acPo3pJuRsRrGqmBBMvFw1
L4uFPPODdsy7nyp3vuhcqh9KA7/kvbIa4F/lK6PN0gCcrAmY8U9/b2c68EvC0sOH
JZBrvGyzoeENFQZ7rTF0AHmoeHPYh1mVpTNiNgWSkCK72EG67MZRNg34O7WZqXou
Bf8lhPYt8idYBI/qjrT/OJFhLIXEjChjZXIVY9t8hLUebdqGJlxbAyNk3/GdAHU3
FCOyfUO+4Y679EMIoG+1L3gclF2a1InXAnsAwMTH01bZ4xKmlSb+POrdvgGLCmY/
vKewI8E83IyWIBkW5E6lzO3uMSzprRudSZpa6Lk2lJ7DYKFzVMc=
=xqFG
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Version: 7.0.32-1+rm

Dear submitter,

as the package php7.0 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/910071

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Ansgar Burchardt (the ftpmaster behind the curtain)--- End Message ---


Bug#910067: marked as done (Block PHP 7.1 from re-entering the testing)

2018-10-08 Thread Debian Bug Tracking System
Your message dated Mon, 08 Oct 2018 18:57:16 +
with message-id 
and subject line Bug#910072: Removed package(s) from unstable
has caused the Debian Bug report #910067,
regarding Block PHP 7.1 from re-entering the testing
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.)


-- 
910067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910067
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:php7.1
Version: 7.1.20-1
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

This is just a blocker bug to keep PHP 7.1 out of testing.

Ondrej

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

Kernel: Linux 4.17.0-1-amd64 (SMP w/6 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_US.UTF-8), LANGUAGE=en_DK.UTF-8 (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

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEEw2Gx4wKVQ+vGJel9g3Kkd++uWcIFAluzOFJfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEMz
NjFCMUUzMDI5NTQzRUJDNjI1RTk3RDgzNzJBNDc3RUZBRTU5QzIACgkQg3Kkd++u
WcK9qg//TNULMqndeXp6D4sAeuJvBTmUM/1fksiyEzeVRBOs3z5GumhpNEXqnB6O
0sHXCFkmXWnUVCzUNwNt/cR0soDHqbiV0QgjJ9PIcxD2si6lifRrYPUuQvC6IWNO
AQyBR/J8SOk1MEhcNqUrcou6KO54kDXP7W+/QJEpAkY0lF2uRB9yUn3WY5l37ok9
lS9f6fXdl4Mmg3XWKUxvxcYdc73qEGgWzQm2tpCgE6c/4lXvUKP6M4XuobDhe4QF
ZZKiQw3XCERk/9G38auBvAZO3XESehjpnX+PJRRNeAM6KJr9heX16Dcjj5oo+HDi
/o4dhvorwlh7fxUov/EFJ1gwIdzT7XnNivkmJr+DMgN8QysTq23IteWlq1c16VOB
bTfoneRhyxhYaJYFik9uzCnSkZZL1g4mZu7PZr4qOX0E0ze0RkDRNPKxS0SDRYQ4
riV6IY5kNGNaczpLIvOWkH4EtJOzYAaIxh1tjs+hLuitTy6dSRoO5rqmvKnibaw7
ATKTiufiPkMQZwV2r/O+oeHObtueEE8othVC3W3ZCXkAJFtGhYajUBhs8WEF0Viq
k3dHs3aWKnPT1SRc73vI34YTonaZQ0Zw30ifR3kppUTRle1VZ2lSMGLotkRpb0qt
gMVHlwQc5m0q/PHZ/WX4v8hRRPyIP0aWuwj9FS3An86GAz8g16w=
=JfBt
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Version: 7.1.20-1+rm

Dear submitter,

as the package php7.1 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/910072

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Ansgar Burchardt (the ftpmaster behind the curtain)--- End Message ---


Bug#899936: marked as done (file-rc: Invalid maintainer address file-rc-us...@lists.alioth.debian.org)

2018-10-08 Thread Debian Bug Tracking System
Your message dated Mon, 08 Oct 2018 18:55:21 +
with message-id 
and subject line Bug#904318: Removed package(s) from unstable
has caused the Debian Bug report #899936,
regarding file-rc: Invalid maintainer address 
file-rc-us...@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.)


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

Dear uploader of file-rc,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package file-rc since the list address
file-rc-us...@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
file-rc-us...@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 ---
Version: 0.8.18+rm

Dear submitter,

as the package file-rc has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/904318

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Ansgar Burchardt (the ftpmaster behind the curtain)--- End Message ---


Bug#892401: marked as done (squid3: build-depends on GCC 6)

2018-10-08 Thread Debian Bug Tracking System
Your message dated Mon, 08 Oct 2018 18:55:45 +
with message-id 
and subject line Bug#905172: Removed package(s) from unstable
has caused the Debian Bug report #892401,
regarding squid3: build-depends on GCC 6
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.)


-- 
892401: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892401
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: squid3
Severity: serious
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: gcc-6-rm

Hi,

squid3 build-depends on GCC 6. We now have GCC 7 (default) and GCC 8
in the archive, so please make your package build with a newer
compiler (preferably the default one) again, since we'd like to
remove GCC 6 from testing before the buster release.

Cheers, Emilio 
--- End Message ---
--- Begin Message ---
Version: 3.5.27-1+rm

Dear submitter,

as the package squid3 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/905172

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Ansgar Burchardt (the ftpmaster behind the curtain)--- End Message ---


Processed: Re: CVE-2018-12689

2018-10-08 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 + moreinfo
Bug #902186 [phpldapadmin] CVE-2018-12689
Added tag(s) moreinfo.
> severity -1 important
Bug #902186 [phpldapadmin] CVE-2018-12689
Severity set to 'important' from 'grave'

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



Bug#771778: marked as done (squid3: Pinger segfault with libc)

2018-10-08 Thread Debian Bug Tracking System
Your message dated Mon, 08 Oct 2018 18:55:45 +
with message-id 
and subject line Bug#905172: Removed package(s) from unstable
has caused the Debian Bug report #728144,
regarding squid3: Pinger segfault with libc
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.)


-- 
728144: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728144
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: squid3
Version: 3.4.8-2
Severity: critical
Justification: breaks the whole system

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

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

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


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

Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages squid3 depends on:
ii  adduser  3.113+nmu3
ii  libc62.13-38+deb7u6
ii  libcap2  1:2.22-1.2
ii  libcomerr2   1.42.5-1.1
ii  libdb5.1 5.1.29-5
ii  libecap2 0.2.0-1
ii  libexpat12.1.0-1+deb7u1
ii  libgcc1  1:4.7.2-5
ii  libgssapi-krb5-2 1.10.1+dfsg-5+deb7u2
ii  libk5crypto3 1.10.1+dfsg-5+deb7u2
ii  libkrb5-31.10.1+dfsg-5+deb7u2
ii  libldap-2.4-22.4.31-1+nmu2
ii  libltdl7 2.4.2-1.1
ii  libnetfilter-conntrack3  1.0.1-1
ii  libnettle4   2.7.1-3
ii  libpam0g 1.1.3-7.1
ii  libsasl2-2   2.1.25.dfsg1-6+deb7u1
ii  libstdc++6   4.7.2-5
ii  libxml2  2.8.0+dfsg1-7+wheezy2
ii  logrotate3.8.1-4
ii  lsb-base 4.1+Debian8+deb7u1
ii  netbase  5.0
ii  squid3-common3.4.8-2

squid3 recommends no packages.

Versions of packages squid3 suggests:
pn  resolvconf   
pn  smbclient
ii  squid-cgi3.4.8-2
ii  squid-purge  3.4.8-2
ii  squidclient  3.4.8-2
ii  ufw  0.31.1-2
pn  winbindd 

-- Configuration Files:
/etc/logrotate.d/squid3 changed:
/var/log/squid3/*.log {
daily
compress
delaycompress
rotate 14
missingok
nocreate
sharedscripts
postrotate
test ! -e /var/run/squid3.pid || test ! -x /usr/sbin/squid3 || 
/usr/sbin/squid3 -k rotate
endscript
}

/etc/squid3/errorpage.css changed:
/*
 Stylesheet for Squid Error pages
 Adapted from design by Free CSS Templates
 http://www.freecsstemplates.org
 Released for free under a Creative Commons Attribution 2.5 License
*/
/* Page basics */
* {
font-family: verdana, sans-serif;
}
html body {
margin: 0;
padding: 0;
background: #efefef;
font-size: 12px;
color: #1e1e1e;
}
/* Page displayed title area */
margin-left: 15px;
padding: 10px;
padding-left: 100px;
background: url('http://rtd-proxy1.rotterdam.bazuin.nl/Artwork/SN.png') 
no-repeat left;
}
/* initial title */
color: #00;
}
color: #00;
}
/* special event: FTP success page titles */
background-color:#00ff00;
width:100%;
}
/* Page displayed body content area */
padding: 10px;
background: #ff;
}
/* General text */
p {
}
/* error brief description */
}
/* some data which may have caused the problem */
}
/* the error message received from the system or other software */
}
pre {
font-family:sans-serif;
}
/* special event: FTP / Gopher directory listing */
font-family: courier;
color: black;
font-size: 10pt;
}
margin-left: 2%;
margin-right: 2%;
}
border-bottom: groove;
}
width: 50px;
text-align: right;
padding-right: 5px;
}
/* horizontal lines */
hr {
margin: 0;
}
/* page displayed footer area */
font-size: 9px;
padding-left: 10px;
}

/etc/squid3/squid.conf changed:
include /etc/squid3/conf.d/*.conf

/etc/ufw/applications.d/squid3 changed:
[Squid]
title=Squid proxy cache
description=Internet object cache (WWW proxy cache)
ports=2048,3128,3130,3401,4827,8080/tcp


-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 3.5.27-1+rm

Dear submitter,

as the package squid3 has just

Bug#902186: CVE-2018-12689

2018-10-08 Thread Dominik George
Control: tags -1 + moreinfo
Control: severity -1 important

Heisann,

On Sat, Jun 23, 2018 at 10:45:39AM +0200, Moritz Muehlenhoff wrote:
> Package: phpldapadmin
> Severity: grave
> Tags: security
> 
> Please see
> http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12689

I am triaging this bug report because of a request of a user to get
phpLDAPAdmin into testing again, and the maintainer seems to be unresponsive.

Doing so, I found that in my opinion, the CVE is invalid. Neither of the PoC
works.

 PoC 1 (server_id parameter) does not work because the parameter is verified
 using is_numeric before being passed on to anything special.

 PoC 2 makes phpLDAPAdmin simply display "Invalid DN syntax for user".

No matter what, I was not able to get anything out of phpLDAPAdmin with the
information in the CVE and the refereces exploit. Thus, I am lowering the
priority of this bug report to important and asking you to provide more
information on how to produce the behaviour claimed in the CVE report.

Ha det bra,
Nik



Bug#892191: marked as done (ruby-progressbar FTBFS with Ruby 2.5: Failure/Error: require 'mathn')

2018-10-08 Thread Debian Bug Tracking System
Your message dated Mon, 08 Oct 2018 18:51:11 +
with message-id 
and subject line Bug#892191: fixed in ruby-progressbar 1.9.0-1
has caused the Debian Bug report #892191,
regarding ruby-progressbar FTBFS  with Ruby 2.5: Failure/Error: require 'mathn'
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.)


-- 
892191: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892191
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-progressbar
Version: 1.4.2-1
Severity: serious
Tags: buster sid

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

...
┌──┐
│ Run tests for ruby2.5 from debian/ruby-tests.rake│
└──┘

RUBYLIB=/build/1st/ruby-progressbar-1.4.2/debian/ruby-progressbar/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-progressbar/usr/share/rubygems-integration/all:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 -S rake -f debian/ruby-tests.rake
/usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb

An error occurred while loading ./spec/lib/ruby-progressbar/base_spec.rb.
Failure/Error: require 'mathn'

LoadError:
  cannot load such file -- mathn
# ./spec/spec_helper.rb:1:in `'
# ./spec/lib/ruby-progressbar/base_spec.rb:1:in `'

An error occurred while loading 
./spec/lib/ruby-progressbar/components/bar_spec.rb.
Failure/Error: require 'mathn'

LoadError:
  cannot load such file -- mathn
# ./spec/spec_helper.rb:1:in `'
# ./spec/lib/ruby-progressbar/components/bar_spec.rb:1:in `'

An error occurred while loading 
./spec/lib/ruby-progressbar/components/elapsed_timer_spec.rb.
Failure/Error: require 'mathn'

LoadError:
  cannot load such file -- mathn
# ./spec/spec_helper.rb:1:in `'
# ./spec/lib/ruby-progressbar/components/elapsed_timer_spec.rb:1:in `'

An error occurred while loading 
./spec/lib/ruby-progressbar/components/estimated_timer_spec.rb.
Failure/Error: require 'mathn'

LoadError:
  cannot load such file -- mathn
# ./spec/spec_helper.rb:1:in `'
# ./spec/lib/ruby-progressbar/components/estimated_timer_spec.rb:1:in `'

An error occurred while loading 
./spec/lib/ruby-progressbar/components/progressable_spec.rb.
Failure/Error: require 'mathn'

LoadError:
  cannot load such file -- mathn
# ./spec/spec_helper.rb:1:in `'
# ./spec/lib/ruby-progressbar/components/progressable_spec.rb:1:in `'

An error occurred while loading 
./spec/lib/ruby-progressbar/components/throttle_spec.rb.
Failure/Error: require 'mathn'

LoadError:
  cannot load such file -- mathn
# ./spec/spec_helper.rb:1:in `'
# ./spec/lib/ruby-progressbar/components/throttle_spec.rb:1:in `'

An error occurred while loading 
./spec/lib/ruby-progressbar/format/molecule_spec.rb.
Failure/Error: require 'mathn'

LoadError:
  cannot load such file -- mathn
# ./spec/spec_helper.rb:1:in `'
# ./spec/lib/ruby-progressbar/format/molecule_spec.rb:1:in `'

An error occurred while loading 
./spec/lib/ruby-progressbar/running_average_calculator_spec.rb.
Failure/Error: require 'mathn'

LoadError:
  cannot load such file -- mathn
# ./spec/spec_helper.rb:1:in `'
# ./spec/lib/ruby-progressbar/running_average_calculator_spec.rb:1:in `'

An error occurred while loading ./spec/lib/ruby-progressbar/time_spec.rb.
Failure/Error: require 'mathn'

LoadError:
  cannot load such file -- mathn
# ./spec/spec_helper.rb:1:in `'
# ./spec/lib/ruby-progressbar/time_spec.rb:1:in `'
No examples found.


Finished in 0.00045 seconds (files took 0.54597 seconds to load)
0 examples, 0 failures, 9 errors occurred outside of examples

/usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb failed
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install 
/build/1st/ruby-progressbar-1.4.2/debian/ruby-progressbar returned exit code 1
make: *** [debian/rules:15: binary] Error 1
--- End Message ---
--- Begin Message ---
Source: ruby-progressbar
Source-Version: 1.9.0-1

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

Debian distribution maintenance so

Bug#910498: debian-edu: autopkgtest regression: education-menus_2.10.38_amd64.deb (--unpack):, trying to overwrite '/usr/share/tasksel/descs/debian-edu-tasks.desc

2018-10-08 Thread Holger Levsen
On Mon, Oct 08, 2018 at 08:31:56PM +0200, Paul Gevers wrote:
> Maybe a bug in one of the helper functions (debhelper, dpkg*)?

maybe, yes. this needs more investigation...

> > on a related note, why are you filing serious bugs about this, Paul?
> > (More concerned about your work load here than anything else...)
> > Because, shouldn't the autotesting-regression be enough, especially in the
> > soon-to-be-future?
> In the soon-to-be-future, yes, but we're not there yet. As I am filing
> these bug to let you know about the regression, I might as well try to
> put the right severity on it.

right. I do check tracker.d.o/$srcpkg after uploads regularily so I
would have noticed anyway, but I guess not everyone's doing that.

> About my work-load,

aehm, sorry, of course you know best about your work-load!

> I focus on autopkgtest regressions with multiple
> packages involved first. And only process the regression ones later.
> What I try to achieve is that I understand case that our infrastructure
> isn't handling properly yet.
 
very nice! thanks for all your work on autopkgtest & britney & all that.
very very nice, in fact!


-- 
cheers,
Holger

---
   holger@(debian|reproducible-builds|layer-acht).org
   PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C


signature.asc
Description: PGP signature


Bug#910319: marked as done (fast-histogram FTBFS: fast_histogram/_histogram_core.c:1:10: fatal error: Python.h: No such file or directory)

2018-10-08 Thread Debian Bug Tracking System
Your message dated Mon, 08 Oct 2018 18:34:04 +
with message-id 
and subject line Bug#910319: fixed in fast-histogram 0.5-1
has caused the Debian Bug report #910319,
regarding fast-histogram FTBFS: fast_histogram/_histogram_core.c:1:10: fatal 
error: Python.h: No such file or directory
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.)


-- 
910319: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910319
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fast-histogram
Version: 0.4-1
Severity: serious

fast-histogram fails to build from source in sbuild on unstable/amd64. A
build log ends with:

|dh_auto_build -O--buildsystem=pybuild
| I: pybuild base:217: /usr/bin/python3.7 setup.py build 
| running build
| running build_py
| creating 
/<>/.pybuild/cpython3_3.7_fast-histogram/build/fast_histogram
| copying fast_histogram/__init__.py -> 
/<>/.pybuild/cpython3_3.7_fast-histogram/build/fast_histogram
| copying fast_histogram/histogram.py -> 
/<>/.pybuild/cpython3_3.7_fast-histogram/build/fast_histogram
| creating 
/<>/.pybuild/cpython3_3.7_fast-histogram/build/fast_histogram/tests
| copying fast_histogram/tests/test_histogram.py -> 
/<>/.pybuild/cpython3_3.7_fast-histogram/build/fast_histogram/tests
| copying fast_histogram/tests/__init__.py -> 
/<>/.pybuild/cpython3_3.7_fast-histogram/build/fast_histogram/tests
| running build_ext
| building 'fast_histogram._histogram_core' extension
| creating build
| creating build/temp.linux-amd64-3.7
| creating build/temp.linux-amd64-3.7/fast_histogram
| x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-I/usr/include/python3.7m -I/usr/lib/python3/dist-packages/numpy/core/include 
-c fast_histogram/_histogram_core.c -o 
build/temp.linux-amd64-3.7/fast_histogram/_histogram_core.o
| fast_histogram/_histogram_core.c:1:10: fatal error: Python.h: No such file or 
directory
|  #include 
|   ^~
| compilation terminated.
| error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
| E: pybuild pybuild:338: build: plugin distutils failed with: exit code=1: 
/usr/bin/python3.7 setup.py build 
| dh_auto_build: pybuild --build -i python{version} -p "3.7 3.6" returned exit 
code 13
| make: *** [debian/rules:9: build] Error 25
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

It also fails to build during reproducible tests:

https://tests.reproducible-builds.org/debian/rbuild/unstable/i386/fast-histogram_0.4-1.rbuild.log.gz

Helmut
--- End Message ---
--- Begin Message ---
Source: fast-histogram
Source-Version: 0.5-1

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

Debian distribution maintenance software
pp.
Josue Ortega  (supplier of updated fast-histogram 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: Mon, 08 Oct 2018 11:59:51 -0600
Source: fast-histogram
Binary: python3-fast-histogram
Architecture: source amd64
Version: 0.5-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Astronomy Maintainers 

Changed-By: Josue Ortega 
Description:
 python3-fast-histogram - Fast 1D and 2D histogram functions in Python
Closes: 910319
Changes:
 fast-histogram (0.5-1) unstable; urgency=medium
 .
   * New upstream release 0.5.
   * debian/control:
 - Change python3-dev for python3-all-dev to support
 all python3 installed versions. (Closes: #910319)
 - Add python3-pytest as Build Dependency.
   * Bumps Standards-Version to 4.2.1, no changes required.
Checksums-Sha1:
 dac5f383978b93d5eb587082bf34f6ab19f9f78a 2153 fast-histogram_0.5-1.dsc
 a978753bc11c6b118578817dc8e9eb12100f76a4 12267 fast-histogram_0.5.orig.tar.gz
 d2ed3af87f04213937b1141eccad247414d64c22 2148 
fast-histogram_0.5-1.debian.tar.xz
 aa9bedaef18354304f0cfbbee884934378edc03a 7364 
fast-histogram_0.5-1_amd64.buildinfo
 aea8b5c65110f67fd42446decce7b3355263c7f4 44768 
python3-fast-histogram-dbgsym_0.5-1_amd64.de

Bug#910498: debian-edu: autopkgtest regression: education-menus_2.10.38_amd64.deb (--unpack):, trying to overwrite '/usr/share/tasksel/descs/debian-edu-tasks.desc

2018-10-08 Thread Paul Gevers
Hi,

On 08-10-18 12:54, Holger Levsen wrote:
> On Mon, Oct 08, 2018 at 12:39:13PM +0200, Wolfgang Schweer wrote:
>> Trying to reproduce this, I ran 'debuild -us -uc -ui' in a clean
>> debian-edu.git clone directory.
>> The output from
>> find debian/ -name '*tasks.desc' is
>> debian/education-tasks/usr/share/tasksel/descs/debian-edu-tasks.desc
>>
>> Also,
>> https://packages.debian.org/sid/amd64/education-menus/filelist
>> doesn't contain
>> /usr/share/tasksel/descs/debian-edu-tasks.desc
>>
>> I have no clue how to debug this further.
> 
> given the changes between those two src:debian-edu versions i'm also
> puzzled and clueless how this happened.

Maybe a bug in one of the helper functions (debhelper, dpkg*)?

> on a related note, why are you filing serious bugs about this, Paul?
> (More concerned about your work load here than anything else...)
> Because, shouldn't the autotesting-regression be enough, especially in the
> soon-to-be-future?

In the soon-to-be-future, yes, but we're not there yet. As I am filing
these bug to let you know about the regression, I might as well try to
put the right severity on it.

About my work-load, I focus on autopkgtest regressions with multiple
packages involved first. And only process the regression ones later.
What I try to achieve is that I understand case that our infrastructure
isn't handling properly yet.

Paul



signature.asc
Description: OpenPGP digital signature


Bug#906875: marked as done (xul-ext-lyz no longer works with firefox-esr 60)

2018-10-08 Thread Debian Bug Tracking System
Your message dated Mon, 08 Oct 2018 17:59:28 +
with message-id 
and subject line Bug#908532: Removed package(s) from unstable
has caused the Debian Bug report #906875,
regarding xul-ext-lyz no longer works with firefox-esr 60
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.)


-- 
906875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906875
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xul-ext-lyz
Version: 2.1.5-3-g895ff3a-1
Severity: serious

XUL addons are no longer supported. 
--- End Message ---
--- Begin Message ---
Version: 2.1.5-3-g895ff3a-1+rm

Dear submitter,

as the package lyz has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/908532

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Ansgar Burchardt (the ftpmaster behind the curtain)--- End Message ---


Bug#769441: marked as done (Does not work with Iceweasel 33)

2018-10-08 Thread Debian Bug Tracking System
Your message dated Mon, 08 Oct 2018 18:00:26 +
with message-id 
and subject line Bug#905125: Removed package(s) from unstable
has caused the Debian Bug report #769441,
regarding Does not work with Iceweasel 33
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.)


-- 
769441: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769441
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xul-ext-monkeysphere
Version: 0.8-1
Severity: important

Starting with Iceweasel 33 the monkeysphere extension no longer works. No
error messages are shown, but a cert that validates fine with msva-query-agent
is not accepted by Iceweasel.

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

Kernel: Linux 3.18.0-rc3 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages xul-ext-monkeysphere depends on:
ii  iceweasel  33.1-1

Versions of packages xul-ext-monkeysphere recommends:
ii  msva-perl [monkeysphere-validation-agent]  0.9.2-1

xul-ext-monkeysphere suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.8-2+rm

Dear submitter,

as the package xul-ext-monkeysphere has just been removed from the Debian 
archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/905125

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Ansgar Burchardt (the ftpmaster behind the curtain)--- End Message ---


Bug#823451: marked as done (libbitcoin fails to build on all archs except x86)

2018-10-08 Thread Debian Bug Tracking System
Your message dated Mon, 08 Oct 2018 17:54:09 +
with message-id 
and subject line Bug#906801: Removed package(s) from unstable
has caused the Debian Bug report #823451,
regarding libbitcoin fails to build on all archs except x86
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.)


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

Package: src:libbitcoin
Version: 2.11.0-1
Severity: serious
Tags: sid stretch

libbitcoin fails to build on all release archs except x86, where it built 
before.

see https://buildd.debian.org/status/package.php?p=libbitcoin
--- End Message ---
--- Begin Message ---
Version: 2.11.0-1+rm

Dear submitter,

as the package libbitcoin has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/906801

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Ansgar Burchardt (the ftpmaster behind the curtain)--- End Message ---


Bug#889190: marked as done (libbitcoin0v5 is empty)

2018-10-08 Thread Debian Bug Tracking System
Your message dated Mon, 08 Oct 2018 17:54:09 +
with message-id 
and subject line Bug#906801: Removed package(s) from unstable
has caused the Debian Bug report #889190,
regarding libbitcoin0v5 is empty
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.)


-- 
889190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889190
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libbitcoin0v5
Version: 2.11.0-1
Severity: grave


$ dpkg -L libbitcoin0v5
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/libbitcoin0v5
/usr/share/doc/libbitcoin0v5/AUTHORS
/usr/share/doc/libbitcoin0v5/NEWS.gz
/usr/share/doc/libbitcoin0v5/buildinfo_amd64.gz
/usr/share/doc/libbitcoin0v5/changelog.Debian.amd64.gz
/usr/share/doc/libbitcoin0v5/changelog.Debian.gz
/usr/share/doc/libbitcoin0v5/changelog.gz
/usr/share/doc/libbitcoin0v5/copyright
/usr/share/lintian
/usr/share/lintian/overrides
/usr/share/lintian/overrides/libbitcoin0v5
$
--- End Message ---
--- Begin Message ---
Version: 2.11.0-1+rm

Dear submitter,

as the package libbitcoin has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/906801

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Ansgar Burchardt (the ftpmaster behind the curtain)--- End Message ---


Bug#841620: marked as done (libbitcoin: FTBFS: aclocal: error: too many loops)

2018-10-08 Thread Debian Bug Tracking System
Your message dated Mon, 08 Oct 2018 17:54:09 +
with message-id 
and subject line Bug#906801: Removed package(s) from unstable
has caused the Debian Bug report #841620,
regarding libbitcoin: FTBFS: aclocal: error: too many loops
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.)


-- 
841620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841620
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libbitcoin
Version: 2.11.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161021 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
> CDBS WARNING:  copyright-check disabled - licensecheck is missing.
> sed -e 's/__LIBPKG__/libbitcoin0v5/g' debian/control.in
> test -x debian/rules
> mkdir -p "."
> CDBS WARNING:DEB_COPYRIGHT_CHECK_IGNORE_REGEX is deprecated since 0.4.133
> CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85
> 
> Scanning upstream source for new/changed copyright notices...
> 
> set -e; LC_ALL=C.UTF-8 /usr/bin/licensecheck --check '.*' --recursive 
> --copyright --deb-fmt --ignore 
> '^((.*/)?[^/]+\.(png)|debian/(changelog|copyright(|_hints|_newhints)))$' 
> --lines 0 * | /usr/lib/cdbs/licensecheck2dep5 > debian/copyright_newhints
> /bin/sh: 1: /usr/bin/licensecheck: not found
> find * -type f -regextype posix-extended \
>   -regex '.*\.(png)' \
>   -print0 | perl -0 debian/license-miner
> touch debian/stamp-extract-copyright
> 0 combinations of copyright and licensing found.
> No new copyright notices found - assuming no news is good news...
> touch debian/stamp-copyright-check
> mkdir -p "debian/upstream-cruft"
> mv "m4/ax_check_compile_flag.m4" 
> "debian/upstream-cruft/m4/ax_check_compile_flag.m4";  mv 
> "m4/ax_check_link_flag.m4" "debian/upstream-cruft/m4/ax_check_link_flag.m4";  
> mv "m4/ax_check_preproc_flag.m4" 
> "debian/upstream-cruft/m4/ax_check_preproc_flag.m4";  mv 
> "m4/ax_cxx_compile_stdcxx_11.m4" 
> "debian/upstream-cruft/m4/ax_cxx_compile_stdcxx_11.m4";  mv 
> "m4/ax_java_devel.m4" "debian/upstream-cruft/m4/ax_java_devel.m4";  mv 
> "m4/ax_jni_include_dir.m4" "debian/upstream-cruft/m4/ax_jni_include_dir.m4";  
> mv "m4/ax_prog_jar.m4" "debian/upstream-cruft/m4/ax_prog_jar.m4";  mv 
> "m4/ax_prog_javac.m4" "debian/upstream-cruft/m4/ax_prog_javac.m4";  mv 
> "m4/ax_prog_javac_works.m4" 
> "debian/upstream-cruft/m4/ax_prog_javac_works.m4";  mv 
> "m4/ax_prog_java.m4" "debian/upstream-cruft/m4/ax_prog_java.m4";  mv 
> "m4/ax_prog_java_works.m4" "debian/upstream-cruft/m4/ax_prog_java_works.m4";  
> mv "m4/ax_pthread.m4" "debian/upstream-cruft/m4/ax_pthread.m4";  mv 
> "m4/ax_python_devel.m4" "debian/upstream-cruft/m4/ax_python_devel.m4";  
> mv "m4/ax_boost_base.m4" "debian/upstream-cruft/m4/ax_boost_base.m4";  mv 
> "m4/ax_boost_chrono.m4" "debian/upstream-cruft/m4/ax_boost_chrono.m4";  
> mv "m4/ax_boost_date_time.m4" 
> "debian/upstream-cruft/m4/ax_boost_date_time.m4";  mv 
> "m4/ax_boost_filesystem.m4" 
> "debian/upstream-cruft/m4/ax_boost_filesystem.m4";  mv 
> "m4/ax_boost_locale.m4" "debian/upstream-cruft/m4/ax_boost_locale.m4";  
> mv "m4/ax_boost_program_options.m4" 
> "debian/upstream-cruft/m4/ax_boost_program_options.m4";  mv 
> "m4/ax_boost_regex.m4" "debian/upstream-cruft/m4/ax_boost_regex.m4";  mv 
> "m4/ax_boost_system.m4" "debian/upstream-cruft/m4/ax_boost_system.m4";  
> mv "m4/ax_boost_thread.m4" "debian/upstream-cruft/m4/ax_boost_thread.m4"; 
>  mv "m4/ax_boost_unit_test_framework.m4" 
> "debian/upstream-cruft/m4/ax_boost_unit_test_framework.m4";
> touch debian/stamp-upstream-cruft
> find -type f -name '*.metadata_dump' -delete
> cd . && libtoolize -c -f
> libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'.
> libtoolize: copying file 'build-aux/ltmain.sh'
> libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
> libtoolize: copying file 'm4/libtool.m4'
> libtoolize: copying file 'm4/ltoptions.m4'
> libtoolize: copying file 'm4/ltsugar.m4'
> libtoolize: copying file 'm4/ltversion.m4'
> libtoolize: copying file 'm4/lt~obsolete.m4'
> cd . &&  aclocal -Im4 --install --force
> aclocal: installing 'm4/ax_boost_base.m4' from 
> '/usr/share/aclocal/ax_boost_base.m4'
> aclocal: installing 'm4/ax_boost_chrono.m4' from 
> '/usr/share/aclocal/ax_boost_chrono.m4'
> aclocal: installing 'm4/ax_boost_date_time.m4' from 
> '/usr/share/aclocal/ax_boost_date_time.m4'

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

2018-10-08 Thread Debian Bug Tracking System
Your message dated Mon, 08 Oct 2018 17:54:09 +
with message-id 
and subject line Bug#906801: Removed package(s) from unstable
has caused the Debian Bug report #899569,
regarding libbitcoin: Invalid maintainer address 
pkg-bitcoin-de...@lists.alioth.debian.org
to be marked as done.

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

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


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

Dear uploader of libbitcoin,

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

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

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

Your options:

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

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

  More information about the new service can be found here:
  

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


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

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

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

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 2.11.0-1+rm

Dear submitter,

as the package libbitcoin has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/906801

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Ansgar Burchardt (the ftpmaster behind the curtain)--- End Message ---


Bug#870570: marked as done (libbitcoin: hardcoded Pre-Depends on multiarch-support)

2018-10-08 Thread Debian Bug Tracking System
Your message dated Mon, 08 Oct 2018 17:54:09 +
with message-id 
and subject line Bug#906801: Removed package(s) from unstable
has caused the Debian Bug report #870570,
regarding libbitcoin: hardcoded Pre-Depends on multiarch-support
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.)


-- 
870570: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870570
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libbitcoin
Version: 2.11.0-1
Severity: normal
Tags: sid buster patch
User: debian-gl...@lists.debian.org
Usertags: multiarch-support-removal

Dear Maintainer,

The multiarch-support package has been introduced with squeeze so that
packages using the multiarch libraries can Pre-Depends on it to make
sure the multiarch path ares supported by the dynamic linker. As
dist-upgrades from such a distant release are not supported, the
Pre-Depends can now be dropped and then the package removed from the
archive.

Most of the packages added this Pre-Depends through debhelper and the
misc:Pre-Depends substvar, so a change in debhelper [1] was enough to
get rid of it. However it appears that your package uses a hardcoded
Pre-Depends, thus it needs to be removed manually. You will find a
patch attached to do so.

Please apply it as soon as possible as the multiarch-support package
will be removed from the archive for buster. Failing to do so will 
therefore make your package uninstallable. In case you don't have
time to do so, don't hesitate to ask for a NMU.

Thanks,
Aurelien

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783898
diff -Nru libbitcoin-2.11.0/debian/changelog libbitcoin-2.11.0/debian/changelog
--- libbitcoin-2.11.0/debian/changelog  2016-04-30 12:46:11.0 +
+++ libbitcoin-2.11.0/debian/changelog  2017-08-02 22:20:08.0 +
@@ -1,3 +1,10 @@
+libbitcoin (2.11.0-3) UNRELEASED; urgency=medium
+
+  * 
+  * 
+
+ -- Aurelien Jarno   Wed, 02 Aug 2017 22:20:08 +
+
 libbitcoin (2.11.0-1) unstable; urgency=medium
 
   [ upstream ]
diff -Nru libbitcoin-2.11.0/debian/rules libbitcoin-2.11.0/debian/rules
--- libbitcoin-2.11.0/debian/rules  2016-04-30 12:34:01.0 +
+++ libbitcoin-2.11.0/debian/rules  2017-08-02 22:18:33.0 +
@@ -57,9 +57,6 @@
 
 CDBS_BUILD_DEPENDS +=, $(deps), $(deps-pkg)
 
-# Multiarch quirk (see also other uses of that variable in this file)
-CDBS_PREDEPENDS_$(libpkg) = $(if $(DEB_HOST_MULTIARCH),multiarch-support)
-
 # extract metadata from images before copyright check
 CDBS_BUILD_DEPENDS +=, libregexp-assemble-perl, libimage-exiftool-perl
 CDBS_BUILD_DEPENDS +=, libfont-ttf-perl
--- End Message ---
--- Begin Message ---
Version: 2.11.0-1+rm

Dear submitter,

as the package libbitcoin has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/906801

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Ansgar Burchardt (the ftpmaster behind the curtain)--- End Message ---


Bug#893194: marked as done (fontawesomefx FTBFS with openjdk-9)

2018-10-08 Thread Debian Bug Tracking System
Your message dated Mon, 08 Oct 2018 17:49:07 +
with message-id 
and subject line Bug#893194: fixed in fontawesomefx 9.1.2-1
has caused the Debian Bug report #893194,
regarding fontawesomefx FTBFS with openjdk-9
to be marked as done.

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

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


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

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

...
[INFO] -
[ERROR] COMPILATION ERROR : 
[INFO] -
[ERROR] 
/build/1st/fontawesomefx-8.9/src/main/java/de/jensd/fx/glyphs/GlyphsStack.java:[16,27]
 package javafx.scene.layout does not exist
[ERROR] 
/build/1st/fontawesomefx-8.9/src/main/java/de/jensd/fx/glyphs/GlyphsStack.java:[24,34]
 cannot find symbol
  symbol: class StackPane
[ERROR] 
/build/1st/fontawesomefx-8.9/src/main/java/de/jensd/fx/glyphs/GlyphIcon.java:[19,26]
 package com.sun.javafx.css does not exist
[ERROR] 
/build/1st/fontawesomefx-8.9/src/main/java/de/jensd/fx/glyphs/GlyphIcon.java:[20,33]
 package com.sun.javafx.css.parser does not exist
[ERROR] 
/build/1st/fontawesomefx-8.9/src/main/java/de/jensd/fx/glyphs/GlyphIcon.java:[27,29]
 package javafx.beans.property does not exist
[ERROR] 
/build/1st/fontawesomefx-8.9/src/main/java/de/jensd/fx/glyphs/GlyphIcon.java:[28,29]
 package javafx.beans.property does not exist
[ERROR] 
/build/1st/fontawesomefx-8.9/src/main/java/de/jensd/fx/glyphs/GlyphIcon.java:[29,29]
 package javafx.beans.property does not exist
[ERROR] 
/build/1st/fontawesomefx-8.9/src/main/java/de/jensd/fx/glyphs/GlyphIcon.java:[30,18]
 package javafx.css does not exist
[ERROR] 
/build/1st/fontawesomefx-8.9/src/main/java/de/jensd/fx/glyphs/GlyphIcon.java:[31,18]
 package javafx.css does not exist
[ERROR] 
/build/1st/fontawesomefx-8.9/src/main/java/de/jensd/fx/glyphs/GlyphIcon.java:[32,18]
 package javafx.css does not exist
[ERROR] 
/build/1st/fontawesomefx-8.9/src/main/java/de/jensd/fx/glyphs/GlyphIcon.java:[33,18]
 package javafx.css does not exist
[ERROR] 
/build/1st/fontawesomefx-8.9/src/main/java/de/jensd/fx/glyphs/GlyphIcon.java:[34,18]
 package javafx.css does not exist
[ERROR] 
/build/1st/fontawesomefx-8.9/src/main/java/de/jensd/fx/glyphs/GlyphIcon.java:[35,19]
 package javafx.fxml does not exist
[ERROR] 
/build/1st/fontawesomefx-8.9/src/main/java/de/jensd/fx/glyphs/GlyphIcon.java:[36,25]
 package javafx.scene.text does not exist
[ERROR] 
/build/1st/fontawesomefx-8.9/src/main/java/de/jensd/fx/glyphs/GlyphIcon.java:[37,25]
 package javafx.scene.text does not exist
[ERROR] 
/build/1st/fontawesomefx-8.9/src/main/java/de/jensd/fx/glyphs/GlyphIcon.java:[45,73]
 cannot find symbol
  symbol: class Text
[ERROR] 
/build/1st/fontawesomefx-8.9/src/main/java/de/jensd/fx/glyphs/GlyphIcon.java:[49,26]
 cannot find symbol
  symbol:   class CSSParser
  location: class de.jensd.fx.glyphs.GlyphIcon
[ERROR] 
/build/1st/fontawesomefx-8.9/src/main/java/de/jensd/fx/glyphs/GlyphIcon.java:[51,13]
 cannot find symbol
  symbol:   class StringProperty
  location: class de.jensd.fx.glyphs.GlyphIcon
[ERROR] 
/build/1st/fontawesomefx-8.9/src/main/java/de/jensd/fx/glyphs/GlyphIcon.java:[52,13]
 cannot find symbol
  symbol:   class ObjectProperty
  location: class de.jensd.fx.glyphs.GlyphIcon
[ERROR] 
/build/1st/fontawesomefx-8.9/src/main/java/de/jensd/fx/glyphs/GlyphIcon.java:[53,13]
 cannot find symbol
  symbol:   class ObjectProperty
  location: class de.jensd.fx.glyphs.GlyphIcon
[ERROR] 
/build/1st/fontawesomefx-8.9/src/main/java/de/jensd/fx/glyphs/GlyphIcon.java:[85,18]
 cannot find symbol
  symbol:   class StringProperty
  location: class de.jensd.fx.glyphs.GlyphIcon
[ERROR] 
/build/1st/fontawesomefx-8.9/src/main/java/de/jensd/fx/glyphs/GlyphIcon.java:[100,18]
 cannot find symbol
  symbol:   class ObjectProperty
  location: class de.jensd.fx.glyphs.GlyphIcon
[ERROR] 
/build/1st/fontawesomefx-8.9/src/main/java/de/jensd/fx/glyphs/GlyphIcon.java:[115,18]
 cannot find symbol
  symbol:   class ObjectProperty
  location: class de.jensd.fx.glyphs.GlyphIcon
[ERROR] 
/build/1st/fontawesomefx-8.9/src/main/java/de/jensd/fx/glyphs/GlyphIcon.java:[217,24]
 cannot find symbol
  symbol:   class CssMetaData
  location: class de.jensd.fx.glyphs.GlyphIcon
[ERROR] 
/build/1st/fontawesomefx-8.9/src/main/java/de/jensd/fx/glyphs/GlyphIcon.java:[217,46]
 cannot find symbol
  symbol:   class Styleable
  location: class de.jens

Processed (with 1 error): Re: Bug#910611: openjfx: draws mediathekview and pdfsam unusable

2018-10-08 Thread Debian Bug Tracking System
Processing control commands:

> forcemerge 910395 910611
Bug #910395 [mediathekview] mediathekview: No longer works due to "missing" 
openjfx
Unable to merge bugs because:
package of #910611 is 'openjfx' not 'mediathekview'
Failed to forcibly merge 910395: Did not alter merged bugs.


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



Bug#910395: Bug#910611: openjfx: draws mediathekview and pdfsam unusable

2018-10-08 Thread Markus Koschany
Control: forcemerge 910395 910611

Am 08.10.18 um 19:37 schrieb Philip Rinn:
> Package: openjfx
> Version: 11+26-3
> Severity: normal
> 
> Hi,
> 
> since some days (sadly I don't know it the 8 -> 11 update triggered this)
> mediathekview and pdfsam don't start anymore:

Hi,

we are aware of the current issues with OpenJFX 11 and applications like
MediathekView and PDFsam. I am very close to release an update for
MediathekView if we can fix Debian bug #910585. PDFsam will require more
time but hopefully it can be fixed soon.

Regards,

Markus



signature.asc
Description: OpenPGP digital signature


Processed: Forcemerge 910611 and 910395

2018-10-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 910611 mediathekview
Bug #910611 [openjfx] openjfx: draws mediathekview and pdfsam unusable
Bug reassigned from package 'openjfx' to 'mediathekview'.
No longer marked as found in versions openjfx/11+26-3.
Ignoring request to alter fixed versions of bug #910611 to the same values 
previously set
> forcemerge 910395 910611
Bug #910395 [mediathekview] mediathekview: No longer works due to "missing" 
openjfx
Bug #910611 [mediathekview] openjfx: draws mediathekview and pdfsam unusable
Severity set to 'serious' from 'normal'
Marked as found in versions mediathekview/13.0.6-1.
Merged 910395 910611
> thanks
Stopping processing here.

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



Processed (with 1 error): Re: Bug#910611: openjfx: draws mediathekview and pdfsam unusable

2018-10-08 Thread Debian Bug Tracking System
Processing control commands:

> forcemerge 910395 910611
Bug #910395 [mediathekview] mediathekview: No longer works due to "missing" 
openjfx
Unable to merge bugs because:
package of #910611 is 'openjfx' not 'mediathekview'
Failed to forcibly merge 910395: Did not alter merged bugs.


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



Bug#893194: Bug #893194 in fontawesomefx marked as pending

2018-10-08 Thread Markus Koschany
Control: tag -1 pending

Hello,

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

https://salsa.debian.org/java-team/fontawesomefx/commit/86c9fb46a71ef305572c90a9247d0afc0dee7b3e


Import Debian changes 9.1.2-1

fontawesomefx (9.1.2-1) unstable; urgency=medium

  * New upstream version 9.1.2.
- New build system: Gradle
  * Switch to compat level 11.
  * Declare compliance with Debian Policy 4.2.1.
  * Build-depend on libopenjfx-java instead of openjfx.
  * Fix FTBFS with OpenJFX 11. (Closes: #893194)
  * Remove get-orig-source target.
  * Add build.patch and use Debian's system libraries.
  * Install all icon font jars. Update the package description accordingly.



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/893194



Processed: Bug #893194 in fontawesomefx marked as pending

2018-10-08 Thread Debian Bug Tracking System
Processing control commands:

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

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



Processed: fixed 909719 in 2.18.5

2018-10-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> fixed 909719 2.18.5
Bug #909719 {Done: Mattia Rizzolo } [devscripts] dpkg breaks 
devscripts autopkgtest due to syntax/behavior change
Marked as fixed in versions devscripts/2.18.5.
> thanks
Stopping processing here.

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



Bug#906836: marked as done (xul-ext-self-destructing-cookies no longer works with firefox-esr 60)

2018-10-08 Thread Debian Bug Tracking System
Your message dated Mon, 08 Oct 2018 17:13:39 +
with message-id 
and subject line Bug#908342: Removed package(s) from unstable
has caused the Debian Bug report #906836,
regarding xul-ext-self-destructing-cookies no longer works with firefox-esr 60
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.)


-- 
906836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906836
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xul-ext-self-destructing-cookies
Version: 0.4.11-1
Severity: serious

XUL addons are no longer supported.
--- End Message ---
--- Begin Message ---
Version: 0.4.12-1+rm

Dear submitter,

as the package self-destructing-cookies has just been removed from the Debian 
archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/908342

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Ansgar Burchardt (the ftpmaster behind the curtain)--- End Message ---


Bug#906829: marked as done (xul-ext-classic-theme-restorer no longer works with firefox-esr 60)

2018-10-08 Thread Debian Bug Tracking System
Your message dated Mon, 08 Oct 2018 17:14:22 +
with message-id 
and subject line Bug#908343: Removed package(s) from unstable
has caused the Debian Bug report #906829,
regarding xul-ext-classic-theme-restorer no longer works with firefox-esr 60
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.)


-- 
906829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906829
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xul-ext-classic-theme-restorer
Version: 1.5.9-1
Severity: serious

XUL addons are no longer supported.
--- End Message ---
--- Begin Message ---
Version: 1.5.9-1+rm

Dear submitter,

as the package classic-theme-restorer has just been removed from the Debian 
archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/908343

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Ansgar Burchardt (the ftpmaster behind the curtain)--- End Message ---


Bug#906838: marked as done (xul-ext-y-u-no-validate no longer works with firefox-esr 60)

2018-10-08 Thread Debian Bug Tracking System
Your message dated Mon, 08 Oct 2018 17:12:24 +
with message-id 
and subject line Bug#908339: Removed package(s) from unstable
has caused the Debian Bug report #906838,
regarding xul-ext-y-u-no-validate no longer works with firefox-esr 60
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.)


-- 
906838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906838
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xul-ext-y-u-no-validate
Version: 2013052407-3
Severity: serious

XUL addons are no longer supported.
--- End Message ---
--- Begin Message ---
Version: 2013052407-3+rm

Dear submitter,

as the package y-u-no-validate has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/908339

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Ansgar Burchardt (the ftpmaster behind the curtain)--- End Message ---


Bug#906842: marked as done (xul-ext-downthemall no longer works with firefox-esr 60)

2018-10-08 Thread Debian Bug Tracking System
Your message dated Mon, 08 Oct 2018 17:11:19 +
with message-id 
and subject line Bug#908115: Removed package(s) from unstable
has caused the Debian Bug report #906842,
regarding xul-ext-downthemall no longer works with firefox-esr 60
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.)


-- 
906842: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906842
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xul-ext-downthemall
Version: 3.0.7-1
Severity: serious

XUL addons are no longer supported.
--- End Message ---
--- Begin Message ---
Version: 3.0.7-1+rm

Dear submitter,

as the package downthemall has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/908115

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Ansgar Burchardt (the ftpmaster behind the curtain)--- End Message ---


Bug#906826: marked as done (xul-ext-spdy-indicator no longer works with firefox-esr 60)

2018-10-08 Thread Debian Bug Tracking System
Your message dated Mon, 08 Oct 2018 17:09:15 +
with message-id 
and subject line Bug#910382: Removed package(s) from unstable
has caused the Debian Bug report #906826,
regarding xul-ext-spdy-indicator no longer works with firefox-esr 60
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.)


-- 
906826: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906826
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xul-ext-spdy-indicator
Version: 2.2-1
Severity: serious

XUL addons are no longer supported.
--- End Message ---
--- Begin Message ---
Version: 2.2-1+rm

Dear submitter,

as the package spdy-indicator has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/910382

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Ansgar Burchardt (the ftpmaster behind the curtain)--- End Message ---


Bug#906872: marked as done (xul-ext-flashgot no longer works with firefox-esr 60)

2018-10-08 Thread Debian Bug Tracking System
Your message dated Mon, 08 Oct 2018 17:11:53 +
with message-id 
and subject line Bug#908119: Removed package(s) from unstable
has caused the Debian Bug report #906872,
regarding xul-ext-flashgot no longer works with firefox-esr 60
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.)


-- 
906872: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906872
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xul-ext-flashgot
Version: 1.5.6.13+dfsg-1
Severity: serious

XUL addons are no longer supported. 

If it is confirmed that this package works with thunderbird 60,
it might be an option to change the dependency to only thunderbird.
--- End Message ---
--- Begin Message ---
Version: 1.5.6.13+dfsg-1+rm

Dear submitter,

as the package flashgot has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/908119

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Ansgar Burchardt (the ftpmaster behind the curtain)--- End Message ---


Bug#906887: marked as done (xul-ext-automatic-save-folder no longer works with firefox-esr 60)

2018-10-08 Thread Debian Bug Tracking System
Your message dated Mon, 08 Oct 2018 17:08:41 +
with message-id 
and subject line Bug#909594: Removed package(s) from unstable
has caused the Debian Bug report #906887,
regarding xul-ext-automatic-save-folder no longer works with firefox-esr 60
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.)


-- 
906887: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906887
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xul-ext-automatic-save-folder
Version: 1.0.5~20140831-4
Severity: serious

XUL addons are no longer supported. 
--- End Message ---
--- Begin Message ---
Version: 1.0.5~20140831-4+rm

Dear submitter,

as the package automatic-save-folder has just been removed from the Debian 
archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/909594

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Ansgar Burchardt (the ftpmaster behind the curtain)--- End Message ---


Processed: reassign 909719 to devscripts

2018-10-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 909719 devscripts 2.18.4
Bug #909719 {Done: Mattia Rizzolo } [src:dpkg, 
src:devscripts] dpkg breaks devscripts autopkgtest due to syntax/behavior change
Bug reassigned from package 'src:dpkg, src:devscripts' to 'devscripts'.
No longer marked as found in versions dpkg/1.19.1 and devscripts/2.18.4.
No longer marked as fixed in versions devscripts/2.18.5.
Bug #909719 {Done: Mattia Rizzolo } [devscripts] dpkg breaks 
devscripts autopkgtest due to syntax/behavior change
Marked as found in versions devscripts/2.18.4.
> thanks
Stopping processing here.

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



Bug#840569: marked as done (nosquint should not be in stretch)

2018-10-08 Thread Debian Bug Tracking System
Your message dated Mon, 08 Oct 2018 17:09:52 +
with message-id 
and subject line Bug#904375: Removed package(s) from unstable
has caused the Debian Bug report #840569,
regarding nosquint should not be in stretch
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.)


-- 
840569: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840569
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nosquint
Version: 2.1.9-4
Severity: important

Dear Maintainer,

Nosquint is dead, please remove it and if a replacement is needed
please add no-squint plus - see https://urandom.ca/nosquint about the
death of nosquint and
https://addons.mozilla.org/en-US/firefox/addon/nosquint-plus/ to get
info. about nosquint-plus.

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

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)


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

Dear submitter,

as the package nosquint has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/904375

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Ansgar Burchardt (the ftpmaster behind the curtain)--- End Message ---


Bug#906841: marked as done (xul-ext-firebug no longer works with firefox-esr 60)

2018-10-08 Thread Debian Bug Tracking System
Your message dated Mon, 08 Oct 2018 17:07:52 +
with message-id 
and subject line Bug#909538: Removed package(s) from unstable
has caused the Debian Bug report #906841,
regarding xul-ext-firebug no longer works with firefox-esr 60
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.)


-- 
906841: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906841
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xul-ext-firebug
Version: 2.0.17-1
Severity: serious

XUL addons are no longer supported.
--- End Message ---
--- Begin Message ---
Version: 2.0.17-1+rm

Dear submitter,

as the package firebug has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/909538

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Ansgar Burchardt (the ftpmaster behind the curtain)--- End Message ---


Bug#814563: marked as done (Abandoned upstream)

2018-10-08 Thread Debian Bug Tracking System
Your message dated Mon, 08 Oct 2018 17:06:45 +
with message-id 
and subject line Bug#909054: Removed package(s) from unstable
has caused the Debian Bug report #814563,
regarding Abandoned upstream
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.)


-- 
814563: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814563
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xul-ext-searchload-options
Version: 0.8.0-3
Severity: serious
Tag: sid stretch

[Filled as RC by the maintainer to see it autore-moved from testing if
 nobody disagrees. Please, do downgrade it with an explanation if you
 disagree.]

Hi,

As shown on the homepage, “This add-on has been removed by its author.”
If the situation doesn’t change, there is a priori little point shipping
it in the next stable release (Stretch). It may even stop being useful
in the current stable release (Jessie) since iceweasel is being updated
to more recent LTS versions once they become available (thus the current
tags may soon be useless).

I intend to follow up with an RM request in a few months if nobody
objects, ditto for Jessie if this add-on stops being useful (but feel
free to beat me to it).

Regards

David


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 0.8.0-3+rm

Dear submitter,

as the package searchload-options has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/909054

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Ansgar Burchardt (the ftpmaster behind the curtain)--- End Message ---


  1   2   >