Bug#907662: marked as done (python-tvrage: useless after TVRage.com shut down?)

[Debian Bug Tracking System]

Your message dated Sun, 04 Nov 2018 06:12:46 +
with message-id 
and subject line Bug#908401: Removed package(s) from unstable
has caused the Debian Bug report #907662,
regarding python-tvrage: useless after TVRage.com shut down?
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.)


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

http://www.tvrage.com/
TVRage.com website has shut down (2005-2015) 
--- End Message ---
--- Begin Message ---
Version: 0.4.1-1+rm

Dear submitter,

as the package python-tvrage 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/908401

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.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#912828: exiv2: CVE-2018-18915

[Salvatore Bonaccorso]

Source: exiv2
Version: 0.26-1
Severity: grave
Tags: security upstream
Forwarded: https://github.com/Exiv2/exiv2/issues/511

Hi,

The following vulnerability was published for exiv2, only affecting
the experimental version. The severity as such is not warranted but is
to make sure the 0.26 affecting issues do not enter an upcoming stable
release. If you disagree on that approach I would not object to
downgrade to important.

CVE-2018-18915[0]:
| There is an infinite loop in the Exiv2::Image::printIFDStructure
| function of image.cpp in Exiv2 0.27-RC1. A crafted input will lead to a
| remote denial of service attack.

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-18915
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-18915
[1] https://github.com/Exiv2/exiv2/issues/511

Regards,
Salvatore

Bug#840305: libatteanx-store-memorytriplestore-perl: depends on unavailable AtteanX::RDFQueryTranslator

[intrigeri]

Jonas Smedegaard:
> Please drop it.  Thanks!

Thanks for the quick reply! Filed #912830.

Cheers,
-- 
intrigeri

Bug#912834: Fix typo

[Teus Benschop]

There was a typo in my bug report.
I feel it's good to fix this, so the bug report remains clear.

The sentence "libsword is not going into auto-transition mode soon" should
have been written with "now" rather than "not". So it was going to be meant
to mean this:

"libsword is now going into auto-transition mode soon"



-- 
Teus Benschop
teusjanne...@gmail.com
0318 712046

Bug#912552: marked as done (gringo ftbfs with Python 3.7)

[Debian Bug Tracking System]

Your message dated Sun, 04 Nov 2018 10:34:04 +
with message-id 
and subject line Bug#912552: fixed in gringo 5.2.3-3
has caused the Debian Bug report #912552,
regarding gringo ftbfs with Python 3.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.)


-- 
912552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912552
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gringo
Version: 5.2.3-2
Severity: serious
Tags: sid buster

gringo ftbfs with Python 3.7:

STDERR:
*** Warn : (clingo): Oversubscription: #Threads=8 exceeds logical CPUs=4.
*** ERROR: (clingo):
/<>/app/clingo/tests/python/interrupt.lp:1:1-15:6: error: error
executing python code:
File ">/app/clingo/tests/python/interrupt.lp:1:1-15:6>", 
line 11
  with prg.solve(async=True) as handle:
 ^
  SyntaxError: invalid syntax
--- End Message ---
--- Begin Message ---
Source: gringo
Source-Version: 5.2.3-3

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

Debian distribution maintenance software
pp.
Thomas Krennwallner  (supplier of updated gringo 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, 04 Nov 2018 08:34:30 +0100
Source: gringo
Binary: gringo
Architecture: source
Version: 5.2.3-3
Distribution: experimental
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Thomas Krennwallner 
Description:
 gringo - grounding tools for (disjunctive) logic programs
Closes: 912552 912582
Changes:
 gringo (5.2.3-3) experimental; urgency=medium
 .
   * debian/control: bump Standards-Version to 4.2.1
   * Bug fix: "gringo build-depends on legacy compiler g++-7", thanks to
 Matthias Klose (Closes: #912582).
 - debian/control: Build-Depends on g++-8
   * debian/symbols: update amd64 symbols for g++-8
   * Bug fix: "gringo ftbfs with Python 3.7", thanks to Matthias Klose
 (Closes: #912552).
 - debian/control: Build-Depends on python3.7
 - gringo-python37-async.patch: rename async keyword to async_
Checksums-Sha1:
 68a6b4126903fa86a1f87fa2de041c6835f99b11 2093 gringo_5.2.3-3.dsc
 3d3f6bcbf4ea016a27b5fc364f1b0ab7b524583e 17296 gringo_5.2.3-3.debian.tar.xz
 eba3cca4e6a0118990679d686f3705f2768c6169 8472 gringo_5.2.3-3_amd64.buildinfo
Checksums-Sha256:
 0232b593d6cb358201ef79eff8d110495d63843077baf5d72ee66641403e2269 2093 
gringo_5.2.3-3.dsc
 964d954db081a540360347510136320315b3912cba6649f8f47139d4b35e66f2 17296 
gringo_5.2.3-3.debian.tar.xz
 10e66ba52c4e2a24925c7268adb80ab515ace359e2dba1ab5ee39514ada20118 8472 
gringo_5.2.3-3_amd64.buildinfo
Files:
 2ae8b2535e0be344ddd056c70dee61da 2093 interpreters optional gringo_5.2.3-3.dsc
 6128b19fe32a0965d1a0ae94614d2f95 17296 interpreters optional 
gringo_5.2.3-3.debian.tar.xz
 0646ceaa09c2319ad4f69adc1ea088e1 8472 interpreters optional 
gringo_5.2.3-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEzH7vLECGZFUde0TKJ5ffdKZmmqkFAlvexm4ACgkQJ5ffdKZm
mqliIQ/9HdgX+XpCGS0O2kXmwCYubhuAL2CEMKvDBzsMnakL/lvDgWBvbnlMBD6g
jFevs2SdNfIK+GWzljcDu+SGM5nAWgKMcybsAtWva1sdy80DjVYdJlRtEYypZIeK
PKhPSITEVuvfNXWp9xBHEtIZBlAAOA7FjteIkg2g/ARqDhl6pWtzQve8/8TAhaGY
e62Bq8AV31JRX6pNMZIH6SpFkOCa+GOwgOfaSahodJakHEVe3cT173jkLOQ+Ziig
D5SUsPCdNGIZlf2/93Yy5nIv6ZvrwHBZph+sUHo+l1KVQWNpua4jM2hd4HtoXGPM
3ycyi9sRghDIC5IBZyGt6PeMVqCku7oWmL/kdJkpad9Chv4E0ude0A0c91m7zAq9
tG3t45ebi2UeP8jJKvJvxnJIAW+HVtDcPm3+JzONSLxVpXVslu3si9O6MzheFx5R
m6FEe1TvmYVNUnwtXNfhfixTAqirmF1n4XOd040i6G4TGqaEgg7/O5mrcYNFqbYW
SyO0FF/nRZXHQSIMFvq3K1JJ/tigIBhSMnhQd2Sg+e60M5hVXo4KRH16/5YI7HbR
gf12vXyUF+hOLTglJ+ddSOvhyJemhbK47L7KcgAmpJ3vKH43OqFjVgn0qdN6Anjo
oySK2ZDliXw2lHA95zZfB1YaGN2+scz7Jb8XZrNXRIHCP4ydE78=
=Ajb0
-END PGP SIGNATURE End Message ---

Processed: Bug #896618 in bcfg2 marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #896618 [src:bcfg2] FTBFS with sphinx 1.7.2: exception: cannot import name 
'Directive'
Added tag(s) pending.

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

Bug#896618: Bug #896618 in bcfg2 marked as pending

[Arto Jantunen]

Control: tag -1 pending

Hello,

Bug #896618 in bcfg2 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/bcfg2-team/bcfg2/commit/928fc81bace7042963bfe1fdd51924494bd34b65


Apply patch to support later versions of Sphinx (Closes: #896618)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/896618

Bug#912646: marked as done (trac-tags: missing build dependency on dh-python)

[Debian Bug Tracking System]

Your message dated Sun, 04 Nov 2018 11:36:44 +
with message-id 
and subject line Bug#912646: fixed in trac-tags 0.9-2
has caused the Debian Bug report #912646,
regarding trac-tags: missing build dependency on dh-python
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.)


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

https://buildd.debian.org/status/fetch.php?pkg=trac-tags=all=0.9-1=1541014390=0

...
   dh_auto_clean -O--buildsystem=pybuild
dh_auto_clean: unable to load build system class 'pybuild': Can't locate 
Debian/Debhelper/Buildsystem/pybuild.pm in @INC (you may need to install the 
Debian::Debhelper::Buildsystem::pybuild module) (@INC contains: /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.26.2 /usr/local/share/perl/5.26.2 
/usr/lib/x86_64-linux-gnu/perl5/5.26 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.26 /usr/share/perl/5.26 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at (eval 2) line 
1.
BEGIN failed--compilation aborted at (eval 2) line 1.

make: *** [debian/rules:3: clean] Error 2
--- End Message ---
--- Begin Message ---
Source: trac-tags
Source-Version: 0.9-2

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

Debian distribution maintenance software
pp.
Daniel Kahn Gillmor  (supplier of updated trac-tags 
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, 04 Nov 2018 18:20:06 +0700
Source: trac-tags
Binary: trac-tags
Architecture: source
Version: 0.9-2
Distribution: unstable
Urgency: medium
Maintainer: Daniel Kahn Gillmor 
Changed-By: Daniel Kahn Gillmor 
Description:
 trac-tags  - Tagging plugin for Trac wiki and issue tracking system
Closes: 912646
Changes:
 trac-tags (0.9-2) unstable; urgency=medium
 .
   * Rules-Requires-Root: no
   * added build-dep on dh-python (Closes: #912646)
Checksums-Sha1:
 d9bf07fe5f64443059ab20473bd004fcb3ae174a 1331 trac-tags_0.9-2.dsc
 ceb7228e0427df1e55ff44cd7d7356fa9d44b329 3528 trac-tags_0.9-2.debian.tar.xz
 e1abd77e15c02ae81ca4907c1656018253ad04ab 6305 trac-tags_0.9-2_source.buildinfo
Checksums-Sha256:
 e0a11b84912b0a13c65c26c30c3e5ce3b3b0a0b432ced3eb35353b0af530abbf 1331 
trac-tags_0.9-2.dsc
 ca651e9ce4bb27defb0abc39e6f7e4b169d48dfc6be8b58d772551c8e42a8ce7 3528 
trac-tags_0.9-2.debian.tar.xz
 89fdb415556cc0eab3fea125bd4b557b5a0da6e4f6e697fbbacd49295546b2ae 6305 
trac-tags_0.9-2_source.buildinfo
Files:
 0feff0a2913b6c8ef2a7d87e27b8864b 1331 web optional trac-tags_0.9-2.dsc
 88924f49ef3eb202e5ad5bf9dbe2e887 3528 web optional 
trac-tags_0.9-2.debian.tar.xz
 79d000dbd7d75a1f6fb089664be65e58 6305 web optional 
trac-tags_0.9-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQTTaP514aqS9uSbmdJsHx7ezFD6UwUCW97WKgAKCRBsHx7ezFD6
U/3gAQChWo4gRrI9576sbsjoSfF56IJGVMHl8iHAchmflkwkkgD8Ds4aGy8rAj35
U58x+OGEPrP7qxNnrGbDZIJatgz42AQ=
=CxY9
-END PGP SIGNATURE End Message ---

Bug#893861: thawab: Intent to remove from Debian

[Jeremy Bicha]

There has been a lot of progress recently on packaging a newer eclipse
that won't require the old webkitgtk.

I'm going to convert this bug into a thawab removal bug in a week
unless I hear otherwise from you.

I'm sorry for the inconvenience, but I think it's a bit more polite to
start the removal now rather than waiting until the freezes start when
release team policy won't generally allow "new" packages in to
Testing.

I did ping upstream again at https://github.com/ojuba-org/thawab/issues/14

Thanks,
Jeremy Bicha

Processed: Re: python-poppler: Don't release with buster

[Debian Bug Tracking System]

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

> retitle 884935 python-poppler: Don't release with buster
Bug #884935 [python-poppler] python-popper: Don't release with buster
Changed Bug title to 'python-poppler: Don't release with buster' from 
'python-popper: Don't release with buster'.
> block 884935 by 879034
Bug #884935 [python-poppler] python-poppler: Don't release with buster
884935 was not blocked by any bugs.
884935 was not blocking any bugs.
Added blocking bug(s) of 884935: 879034
>
End of message, stopping processing here.

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

Bug#790207: marked as done (luakit: depends on libwebkitgtk-1.0-0 which is deprecated)

[Debian Bug Tracking System]

Your message dated Sun, 04 Nov 2018 06:05:08 +
with message-id 
and subject line Bug#893870: Removed package(s) from unstable
has caused the Debian Bug report #790207,
regarding luakit: depends on libwebkitgtk-1.0-0 which is deprecated
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.)


-- 
790207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790207
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: luakit
Severity: important
Tags: sid stretch
User: pkg-webkit-maintain...@lists.alioth.debian.org
Usertags: oldlibs libwebkitgtk-1.0-0 webkit1

Hi,

luakit depends on libwebkitgtk-1.0-0, which is deprecated in favor of
libwebkit2gtk-4.0-37. luakit should be ported to the new webkitgtk
version so we can remove the old, unmaintained one.

As an intermediate step you can port luakit to libwebkitgtk-3.0-0,
which has a similar API to libwebkitgtk-1.0-0 but is based on GTK+
3.0. Thus you'd be porting luakit to GTK+ 3.0 first, using
libwebkitgtk-3.0-0, and you could then port to libwebkit2gtk-4.0-37
later. But note that libwebkitgtk-3.0-0 is also deprecated.

Please try to do this before the Stretch release as we're going to
try to remove libwebkitgtk-1.0-0 this cycle.

We'll bump this to serious when the list of rdeps is small and we're
getting ready to removing libwebkitgtk-1.0-0 completely.

If you have any question don't hesitate to ask.

Emilio 
--- End Message ---
--- Begin Message ---
Version: 2012.09.13-r1-8+rm

Dear submitter,

as the package luakit 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/893870

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.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#912834: xiphos: missing build on ppc64el: suggestion to remove it there

[Teus Benschop]

Source: xiphos
Version: 4.0.7.1-4
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Dear Maintainers,

The package xiphos currently does not build on architecture ppc64el.

There is a patch for it, and this patch is in libsword.
But this libsword is not going into auto-transition mode soon.

In the mean time package xiphos as is now in testing is not linked to the 
correct libsword version.
So it won't run on testing right now.
And this was due to me not following the proper route of the transition.

A new build of xiphos was made.
That new build links to the correct libsword.
So Xiphos works with that new build.

But now a missing build on ppc64el will prevent this correctly working xiphos 
package
from being migrated to testing.

See this link:
https://qa.debian.org/excuses.php?package=xiphos

My suggestion is to now request removal of xiphos version 4.0.7.1-4
from architecture ppc64el.
So the remaining xiphos binaries will migrate to testing soon.

Is there a problem with this approach?

If there's no problem with this, I intend to move on with this.

This bug is actually to keep track of this issue.


-- 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=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US:en (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

Bug#911898: firefox-esr: firefox do not start

[john]

Package: firefox-esr
Version: 60.3.0esr-1~deb9u1
Followup-For: Bug #911898

Dear Maintainer,

there is some link you could find usefull for firefox build

talospace.com/2018/09/more-power-in-firefox-62.html
talospace.con/2018/10/patches-needed-for-firefox-63.html

i hope you will fix it asap because firefox is the only browser on ppc64le and 
do not work, and the fix seems easy 
you should consider it critical because ppc64le is tier1 arch on debian and 
right now is not possible to access the web

thank you 


-- Package-specific info:


-- Addons package information

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

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

Versions of packages firefox-esr depends on:
ii  debianutils   4.8.1.1
ii  fontconfig2.11.0-6.7+b1
ii  libasound21.1.3-5
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  libjsoncpp1   1.7.4-3
ii  libpango-1.0-01.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  libxcomposite11:0.4.4-2
ii  libxdamage1   1:1.1.4-2+b3
ii  libxext6  2:1.3.3-1+b2
ii  libxfixes31:5.0.3-1
ii  libxrender1   1:0.9.10-1
ii  libxt61:1.1.5-1
ii  procps2:3.3.12-3+deb9u1
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages firefox-esr recommends:
ii  libavcodec57  7:3.2.12-1~deb9u1

Versions of packages firefox-esr suggests:
pn  fonts-lmodern  
pn  fonts-stix | otf-stix  
ii  libcanberra0   0.30-3
ii  libgssapi-krb5-2   1.15-1+deb9u1
ii  libgtk2.0-02.24.31-2
ii  pulseaudio 10.0-1+deb9u1

-- no debconf information

Bug#891690: marked as done (libclang-common-4.0-dev: /usr/lib/llvm-4.0/lib/clang/4.0.1/lib/ is empty on mipsel)

[Debian Bug Tracking System]

Your message dated Sun, 04 Nov 2018 06:04:17 +
with message-id 
and subject line Bug#893401: Removed package(s) from unstable
has caused the Debian Bug report #891690,
regarding libclang-common-4.0-dev: /usr/lib/llvm-4.0/lib/clang/4.0.1/lib/ is 
empty on mipsel
to be marked as done.

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

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


-- 
891690: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891690
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libclang-common-4.0-dev
Version: 1:4.0.1-10
Severity: serious

Hi,

while analyzing this pocl failure:

https://buildd.debian.org/status/fetch.php?pkg=pocl=mipsel=1.1%7Erc2-1=1519758612=0

  /usr/bin/ld: cannot find
  
/usr/lib/llvm-4.0/bin/../lib/clang/4.0.1/lib/linux/libclang_rt.builtins-mipsel.a:
  No such file or directory

  clang: error: linker command failed with exit code 1 (use -v to see
  invocation)

I found that libclang-common-4.0-dev should contain libclang_rt.builtins-*.a
according to
https://packages.debian.org/sid/mipsel/libclang-common-4.0-dev/filelist
but the last version that actually shipped these files was 1:4.0.1-1.

libclang_rt.builtins-*.a is missing for several other architectures, too,
(the pocl build logs for these architectures mention it:
  armel, mips, mips64el, mipsel, powerpc, ppc64, ppc64el, s390x)
but I didn't dig into the details there.


Andreas
--- End Message ---
--- Begin Message ---
Version: 1:4.0.1-10+rm

Dear submitter,

as the package llvm-toolchain-4.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/893401

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.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#903866: marked as done (python-{clang,lldb}-4.0: missing Breaks+Replaces against python-clang-3.[45], python-lldb-3.5)

[Debian Bug Tracking System]

Your message dated Sun, 04 Nov 2018 06:04:17 +
with message-id 
and subject line Bug#893401: Removed package(s) from unstable
has caused the Debian Bug report #903866,
regarding python-{clang,lldb}-4.0: missing Breaks+Replaces against 
python-clang-3.[45], python-lldb-3.5
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.)


-- 
903866: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903866
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-clang-4.0,python-lldb-4.0
Version: 1:4.0.1-10~deb9u2
Severity: serious
Tags: stretch
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'jessie'.
It installed fine in 'jessie', then the upgrade to 'stretch' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

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

  Preparing to unpack .../python-clang-4.0_1%3a4.0.1-10~deb9u2_amd64.deb ...
  Unpacking python-clang-4.0 (1:4.0.1-10~deb9u2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python-clang-4.0_1%3a4.0.1-10~deb9u2_amd64.deb 
(--unpack):
   trying to overwrite '/usr/lib/python2.7/dist-packages/clang/__init__.py', 
which is also in package python-clang-3.4 1:3.4.2-13
  Errors were encountered while processing:
   /var/cache/apt/archives/python-clang-4.0_1%3a4.0.1-10~deb9u2_amd64.deb

  Preparing to unpack .../python-clang-4.0_1%3a4.0.1-10~deb9u2_amd64.deb ...
  Unpacking python-clang-4.0 (1:4.0.1-10~deb9u2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python-clang-4.0_1%3a4.0.1-10~deb9u2_amd64.deb 
(--unpack):
   trying to overwrite '/usr/lib/python2.7/dist-packages/clang/__init__.py', 
which is also in package python-clang-3.5 1:3.5-10
  Errors were encountered while processing:
   /var/cache/apt/archives/python-clang-4.0_1%3a4.0.1-10~deb9u2_amd64.deb

  Selecting previously unselected package python-lldb-4.0.
  Preparing to unpack .../python-lldb-4.0_1%3a4.0.1-10~deb9u2_amd64.deb ...
  Unpacking python-lldb-4.0 (1:4.0.1-10~deb9u2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python-lldb-4.0_1%3a4.0.1-10~deb9u2_amd64.deb 
(--unpack):
   trying to overwrite '/usr/lib/python2.7/dist-packages/lldb', which is also 
in package python-lldb-3.5 1:3.5-10

The inclusion of llvm-4.0 in stretch brought it into proximity of the
old packages from jessie (that predate the virtual python-{clang,lldb}-x.y
packages), which might remain after an upgrade from jessie to stretch.



cheers,

Andreas


python-clang-3.4=1%3.4.2-13_python-clang-4.0=1%4.0.1-10~deb9u2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 1:4.0.1-10+rm

Dear submitter,

as the package llvm-toolchain-4.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/893401

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.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#897804: marked as done (llvm-toolchain-4.0: ftbfs with GCC-8)

[Debian Bug Tracking System]

Your message dated Sun, 04 Nov 2018 06:04:17 +
with message-id 
and subject line Bug#893401: Removed package(s) from unstable
has caused the Debian Bug report #897804,
regarding llvm-toolchain-4.0: ftbfs with GCC-8
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.)


-- 
897804: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897804
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:llvm-toolchain-4.0
Version: 1:4.0.1-10
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-8

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-8/g++-8, but succeeds to build with gcc-7/g++-7. The
severity of this report will be raised before the buster release.

The full build log can be found at:
http://aws-logs.debian.net/2018/05/01/gcc8/llvm-toolchain-4.0_4.0.1-10_unstable_gcc8.log.gz
The last lines of the build log are at the end of this report.

To build with GCC 8, either set CC=gcc-8 CXX=g++-8 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-8/porting_to.html

[...]
   for (i = 0; i < arg3; i++) {
   ~~^~
cc1plus: warning: unrecognized command line option '-Wno-vla-extension'
cc1plus: warning: unrecognized command line option '-Wno-deprecated-register'
/<>/build-llvm/tools/lldb/scripts/LLDBWrapPython.cpp: In function 
'void SWIG_Python_FixMethods(PyMethodDef*, swig_const_info*, swig_type_info**, 
swig_type_info**)':
/<>/build-llvm/tools/lldb/scripts/LLDBWrapPython.cpp:75338:22: 
warning: 'char* strncpy(char*, const char*, size_t)' output truncated before 
terminating nul copying 10 bytes from a string of the same length 
[-Wstringop-truncation]
   strncpy(buff, "swig_ptr: ", 10);
   ~~~^~~~
In file included from /<>/include/llvm/Support/Allocator.h:24,
 from /<>/include/llvm/ADT/StringMap.h:18,
 from /<>/include/llvm/Support/Host.h:17,
 from /<>/include/llvm/ADT/Hashing.h:49,
 from /<>/include/llvm/ADT/ArrayRef.h:13,
 from 
/<>/tools/lldb/include/lldb/lldb-private-types.h:17,
 from 
/<>/tools/lldb/include/lldb/lldb-private.h:18,
 from 
/<>/tools/lldb/include/lldb/Core/ConstString.h:19,
 from 
/<>/tools/lldb/source/./Plugins/ScriptInterpreter/Python/PythonDataObjects.h:22,
 from 
/<>/tools/lldb/source/./Plugins/ScriptInterpreter/Python/ScriptInterpreterPython.h:27,
 from 
/<>/tools/lldb/source/API/SystemInitializerFull.cpp:19:
/<>/include/llvm/ADT/SmallVector.h: In instantiation of 'void 
llvm::SmallVectorTemplateBase::push_back(const T&) [with T = 
std::pair]':
/<>/include/llvm/Support/Allocator.h:241:33:   required from 
'void* llvm::BumpPtrAllocatorImpl::Allocate(size_t, size_t) [with AllocatorT = 
llvm::MallocAllocator; long unsigned int SlabSize = 4096; long unsigned int 
SizeThreshold = 4096; size_t = long unsigned int]'
/<>/tools/clang/include/clang/AST/ASTContext.h:616:42:   required 
from here
/<>/include/llvm/ADT/SmallVector.h:309:11: warning: 'void* 
memcpy(void*, const void*, size_t)' writing to an object of type 'struct 
std::pair' with no trivial copy-assignment; use 
copy-assignment or copy-initialization instead [-Wclass-memaccess]
 memcpy(this->end(), , sizeof(T));
 ~~^~
In file included from /usr/include/c++/8/bits/stl_algobase.h:64,
 from /usr/include/c++/8/memory:62,
 from 
/<>/tools/lldb/include/lldb/API/SBCommandInterpreter.h:15,
 from 
/<>/tools/lldb/source/API/SystemInitializerFull.cpp:16:
/usr/include/c++/8/bits/stl_pair.h:198:12: note: 'struct std::pair' declared here
 struct pair
^~~~
cc1plus: warning: unrecognized command line option '-Wno-vla-extension'
cc1plus: warning: unrecognized command line option '-Wno-deprecated-register'
At global scope:
cc1plus: warning: unrecognized command line option 

Bug#857653: marked as done (liblld-4.0: missing liblld-4.0.so.1)

[Debian Bug Tracking System]

Your message dated Sun, 04 Nov 2018 06:04:17 +
with message-id 
and subject line Bug#893401: Removed package(s) from unstable
has caused the Debian Bug report #857653,
regarding liblld-4.0: missing liblld-4.0.so.1
to be marked as done.

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

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


-- 
857653: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857653
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: liblld-4.0
Version: missing liblld-4.0.so.1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

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

0m24.5s ERROR: FAIL: Broken symlinks:
  /usr/lib/llvm-4.0/lib/liblld.so.1 -> ../../x86_64-linux-gnu/liblld-4.0.so.1
  /usr/lib/x86_64-linux-gnu/liblld-4.0.so -> liblld-4.0.so.1
  /usr/lib/python2.7/dist-packages/lld-4.0/_lld.so -> 
../../../x86_64-linux-gnu/liblld-4.0.so

liblld-4.0.so.1 does not seem to exist anywhere, I could only find
  /usr/lib/llvm-4.0/lib/liblld.so.1

liblld-5.0 has the same problems.


cheers,

Andreas


liblld-4.0_1:4.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 1:4.0.1-10+rm

Dear submitter,

as the package llvm-toolchain-4.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/893401

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.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#891102: marked as done (python-tvrage: python-beautifulsoup is replaced with python-bs4)

[Debian Bug Tracking System]

Your message dated Sun, 04 Nov 2018 06:12:46 +
with message-id 
and subject line Bug#908401: Removed package(s) from unstable
has caused the Debian Bug report #891102,
regarding python-tvrage: python-beautifulsoup is replaced with python-bs4
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.)


-- 
891102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891102
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-tvrage
Version: 0.4.1-1
Severity: important
Control: block 891087 by -1

beautifulsoup version 4 was replaced as a new package, bs4, which has
been in Debian for over 5 years now. beautfiulsoup (3.x) hasn't seen any
maintenance since then. It's high time to remove it from the archive.

Most code written against Beautiful Soup 3 will work against Beautiful
Soup 4 with one simple change. All you should have to do is change the
package name from BeautifulSoup to bs4, and depend on python-bs4 instead
of python-beautifulsoup.

There is some documentation on the migration here:
https://www.crummy.com/software/BeautifulSoup/bs4/doc/#porting-code-to-bs4

Thanks,

SR
--- End Message ---
--- Begin Message ---
Version: 0.4.1-1+rm

Dear submitter,

as the package python-tvrage 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/908401

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.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#896618: marked as done (FTBFS with sphinx 1.7.2: exception: cannot import name 'Directive')

[Debian Bug Tracking System]

Your message dated Sun, 04 Nov 2018 11:49:03 +
with message-id 
and subject line Bug#896618: fixed in bcfg2 1.4.0~pre2+git141-g6d40dace6358-2
has caused the Debian Bug report #896618,
regarding FTBFS with sphinx 1.7.2: exception: cannot import name 'Directive'
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.)


-- 
896618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896618
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sphinx
Version: 1.7.2-1
Severity: serious
Control: affects -1 src:alembic src:bcfg2 src:bottleneck src:dipy src:heat 
src:julia src:mako src:prospector src:pyevolve src:pymvpa2 
src:python-cryptography src:python-expyriment src:python-numpy src:python-scipy

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/alembic.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/bcfg2.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/bottleneck.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/dipy.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/heat.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/julia.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/mako.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/prospector.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pyevolve.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pymvpa2.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/python-cryptography.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-expyriment.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-numpy.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-scipy.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/arm64/sqlalchemy.html

Example (from alembic):

...
   debian/rules override_dh_sphinxdoc
make[1]: Entering directory '/build/1st/alembic-0.9.7'
sphinx-build -b html docs/build 
/build/1st/alembic-0.9.7/debian/alembic/usr/share/doc/alembic/html
Running Sphinx v1.7.2

Extension error:
Could not import extension changelog (exception: cannot import name 'Directive')
make[1]: *** [debian/rules:13: override_dh_sphinxdoc] Error 2
--- End Message ---
--- Begin Message ---
Source: bcfg2
Source-Version: 1.4.0~pre2+git141-g6d40dace6358-2

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

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

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

Debian distribution maintenance software
pp.
Arto Jantunen  (supplier of updated bcfg2 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, 04 Nov 2018 13:19:47 +0200
Source: bcfg2
Binary: bcfg2 bcfg2-server bcfg2-web bcfg2-doc
Architecture: source
Version: 1.4.0~pre2+git141-g6d40dace6358-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Arto Jantunen 
Description:
 bcfg2  - Configuration management client
 bcfg2-doc  - Configuration management system documentation
 bcfg2-server - Configuration management server
 bcfg2-web  - Configuration management web interface
Closes: 896618
Changes:
 bcfg2 (1.4.0~pre2+git141-g6d40dace6358-2) unstable; urgency=medium
 .
   * Point VCS urls to Salsa
   * Orphan the package
   * Apply patch to support later versions of Sphinx (Closes: #896618)
Checksums-Sha1:
 adee443c06a845f7cac0f9799825f005f5cba417 2396 
bcfg2_1.4.0~pre2+git141-g6d40dace6358-2.dsc
 bbf4335cea16e156a0dd3dbb0b17a45d39eb 40312 
bcfg2_1.4.0~pre2+git141-g6d40dace6358-2.debian.tar.xz
 c3de6132f7fd62c7b3644d1e0306d99407a371d7 9292 
bcfg2_1.4.0~pre2+git141-g6d40dace6358-2_amd64.buildinfo
Checksums-Sha256:
 e6011ad603a54bb439abd2df50e40cf327dd088648f2c4931bb5156419acadec 2396 
bcfg2_1.4.0~pre2+git141-g6d40dace6358-2.dsc
 8086f3d84e577dedc9410c4f00bf66847cf12a0a49d972e87871c53a81d282ea 40312 
bcfg2_1.4.0~pre2+git141-g6d40dace6358-2.debian.tar.xz
 9113c19623998ca94050afd2a9e92f5ab996678dacef4480ab56ef292836d36a 9292 

Bug#895599: marked as done (ganeti-2.15 - Fails to export vm: certificate is valid but its commonName does not match hostname)

[Debian Bug Tracking System]

Your message dated Sun, 04 Nov 2018 11:47:10 +
with message-id 
and subject line Bug#895599: fixed in ganeti 2.15.2-7+deb9u3
has caused the Debian Bug report #895599,
regarding ganeti-2.15 - Fails to export vm: certificate is valid but its 
commonName does not match hostname
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.)


-- 
895599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895599
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ganeti
Version: 2.15.2-7+deb9u1
Severity: grave

All vm exports fail with:

| 2018-04-13 09:23:25,650: socat: E certificate is valid but its commonName 
does not match hostname

This is fixed in 2.16.

Bastian

-- 
Bastian Blank
Berater
Telefon: +49 2166 9901-194
E-Mail: bastian.bl...@credativ.de
credativ GmbH, HRB Mönchengladbach 12080, USt-ID-Nummer: DE204566209
Trompeterallee 108, 41189 Mönchengladbach
Geschäftsführung: Dr. Michael Meskes, Jörg Folz, Sascha Heuer
--- End Message ---
--- Begin Message ---
Source: ganeti
Source-Version: 2.15.2-7+deb9u3

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

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

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

Debian distribution maintenance software
pp.
Apollon Oikonomopoulos  (supplier of updated ganeti 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: Sat, 08 Sep 2018 20:22:03 +0300
Source: ganeti
Binary: ganeti2 ganeti ganeti-2.15 ganeti-haskell-2.15 ganeti-htools 
ganeti-htools-2.15 ganeti-doc python-ganeti-rapi
Architecture: source all amd64
Version: 2.15.2-7+deb9u3
Distribution: stretch
Urgency: medium
Maintainer: Debian Ganeti Team 
Changed-By: Apollon Oikonomopoulos 
Description:
 ganeti - cluster virtualization manager
 ganeti-2.15 - cluster virtualization manager - Python components
 ganeti-doc - cluster virtualization manager - documentation
 ganeti-haskell-2.15 - cluster virtualization manager - Haskell components
 ganeti-htools - cluster virtualization manager - tools (stand-alone)
 ganeti-htools-2.15 - cluster virtualization manager - tools for Ganeti 2.15
 ganeti2- transitional dummy package
 python-ganeti-rapi - cluster virtualization manager - RAPI client library
Closes: 864755 895599 907569 908112
Changes:
 ganeti (2.15.2-7+deb9u3) stretch; urgency=medium
 .
   * Properly verify SSL certificates during VM export (#2) (Closes: #895599, 
#908112)
   * Sign generated certificates using SHA256 instead of SHA1 (Closes: #907569)
 + d/NEWS: ask users to run gnt-cluster renew-crypto
 + cluster verify: warn about weak certificates
   * Make bash completions autoloadable (Closes: #864755)
 + Cleanup obsolete /etc/bash_completion.d/ganeti
Checksums-Sha1:
 698adc077e5485a9e2cb610704e17fd52ddec18e 3430 ganeti_2.15.2-7+deb9u3.dsc
 376e394aedcd66f0fd6902a3522279455b34aac3 73984 
ganeti_2.15.2-7+deb9u3.debian.tar.xz
 2838c855bdf5075cb40f862a9606980246930ad6 867840 
ganeti-2.15_2.15.2-7+deb9u3_all.deb
 3de542471160d220b19d455bacd2e18e9391a1b5 962242 
ganeti-doc_2.15.2-7+deb9u3_all.deb
 21ced4c59b3e4ba9852b2eceeec815b8c06d59a4 7535684 
ganeti-haskell-2.15-dbgsym_2.15.2-7+deb9u3_amd64.deb
 22fb178762747dd096b6e61d5e99767d9c02aeb0 14178452 
ganeti-haskell-2.15_2.15.2-7+deb9u3_amd64.deb
 37aec67b54dc8d6e14acca02dedf244911127940 1626058 
ganeti-htools-2.15-dbgsym_2.15.2-7+deb9u3_amd64.deb
 0386c7c5fa3eb394fdeef83074214f70c0a9f1bc 2697280 
ganeti-htools-2.15_2.15.2-7+deb9u3_amd64.deb
 9b3454ed56aa55ba5d9aaf2cacdb99c1bedc8dc2 21712 
ganeti-htools_2.15.2-7+deb9u3_all.deb
 b083e57713f64ffd159264719c74c31e3fdde255 77948 ganeti2_2.15.2-7+deb9u3_all.deb
 4d119acb265b6d95669b2842b61e9a27029e69a8 98830 ganeti_2.15.2-7+deb9u3_all.deb
 237521612ed57391aae8e6d8fba9aef5a2c914e3 15885 
ganeti_2.15.2-7+deb9u3_amd64.buildinfo
 fbe3c62508b3b806a1f2506649c8ec93b9bf7207 34228 
python-ganeti-rapi_2.15.2-7+deb9u3_all.deb
Checksums-Sha256:
 b0bb5204c202006698fd4d0b02847aa2fb4210ffda4b21df3837aeb8f59ad029 3430 
ganeti_2.15.2-7+deb9u3.dsc
 7b7ec7a457f32b44c317bf2b349041ad73727b579c2674a4b1612401e3cf5043 73984 
ganeti_2.15.2-7+deb9u3.debian.tar.xz
 

Bug#908112: marked as done (ganeti: Unable to move an instance to an other node)

[Debian Bug Tracking System]

Your message dated Sun, 04 Nov 2018 11:47:10 +
with message-id 
and subject line Bug#908112: fixed in ganeti 2.15.2-7+deb9u3
has caused the Debian Bug report #908112,
regarding ganeti: Unable to move an instance to an other node
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.)


-- 
908112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908112
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ganeti
Version: 2.15.2-7+deb9u2
Severity: important

Dear Maintainer,

   * What led up to the situation?
I tried to move an instance to an other node:
```
gnt-instance move -n node2.foo.org instance_to_move.foo.org
```

It failed at disk copy with:
```
Thu Sep  6 08:45:15 2018  - WARNING: export 
'export-disk0-2018-09-06_08_45_14-AczCFY' on node1.foo.org failed: Unhandled 
error occurred: global name 'SOCAT_PATH' is not defined
Thu Sep  6 08:45:15 2018 disk/0 failed to send data: Unhandled error occurred: 
global name 'SOCAT_PATH' is not defined (recent output: )
Thu Sep  6 08:45:16 2018  - WARNING: Aborting import 
'import-disk0-2018-09-06_08_45_09-hsDCKv' on 
54c96f74-2ea7-461a-90f6-8652fac2942f
```

I added this in /usr/share/ganeti/2.15/ganeti/impexpd/__init__.py, line
68
```
SOCAT_PATH = '/usr/bin/socat'
```

Then it still failed with:
```
Thu Sep  6 08:49:20 2018  - WARNING: export 
'export-disk0-2018-09-06_08_49_19-vDGWD9' on node1.foo.org failed: Unhandled 
error occurred: global name 'm' is not defined
Thu Sep  6 08:49:20 2018 disk/0 failed to send data: Unhandled error occurred: 
global name 'm' is not defined (recent output: )
Thu Sep  6 08:49:20 2018  - WARNING: Aborting import 
'import-disk0-2018-09-06_08_49_14-2WLKY4' on 
54c96f74-2ea7-461a-90f6-8652fac2942f
```

I managed to move my instance by downgrading ganeti, ganeti-2.15,
ganeti-haskell-2.15 and ganeti-htools-2.15 to the previous version
(2.15.2-7+deb9u1)

-- Package-specific info:
Version symlinks:
  /etc/ganeti/share -> /usr/share/ganeti/2.15
  /etc/ganeti/lib -> /usr/lib/ganeti/2.15
Cluster config version: 2.15.2
Address family: IPv4
Enabled hypervisors: kvm
kvm hypervisor parameters:
  acpi=True
  boot_order=disk
  cpu_cores=0
  cpu_mask=all
  cpu_sockets=0
  cpu_threads=0
  disk_aio=threads
  disk_cache=default
  disk_type=paravirtual
  kernel_args=ro
  kernel_path=/boot/vmlinuz-3-kvmU
  kvm_path=/usr/bin/kvm
  migration_bandwidth=32
  migration_downtime=30
  migration_mode=live
  migration_port=8102
  nic_type=paravirtual
  reboot_behavior=reboot
  root_path=/dev/vda1
  security_model=none
  serial_console=True
  serial_speed=38400
  spice_ip_version=0
  spice_playback_compression=True
  spice_tls_ciphers=HIGH:-DES:-3DES:-EXPORT:-ADH
  spice_use_tls=False
  spice_use_vdagent=True
  use_chroot=False
  use_localtime=False
  user_shutdown=False
  vhost_net=False
  virtio_net_queues=1
  vnc_tls=False
  vnc_x509_verify=False
  vnet_hdr=True

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

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

Versions of packages ganeti depends on:
ii  adduser  3.115
ii  ganeti-2.15  2.15.2-7+deb9u2
ii  ganeti-haskell-2.15  2.15.2-7+deb9u2
ii  ganeti-htools-2.15   2.15.2-7+deb9u2
ii  lsb-base 9.20161125
ii  python   2.7.13-2

Versions of packages ganeti recommends:
ii  drbd-utils   8.9.10-2
ii  drbd8-utils  2:8.9.10-2
ii  ganeti-instance-debootstrap  0.16-2.1
ii  ndisc6   1.0.3-3
ii  qemu-kvm 1:2.8+dfsg-6+deb9u4

Versions of packages ganeti suggests:
pn  blktap-dkms  
ii  ganeti-doc   2.15.2-7+deb9u2
pn  molly-guard  

-- Configuration Files:
/etc/default/ganeti changed [not included]

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: ganeti
Source-Version: 2.15.2-7+deb9u3

We believe that the bug you reported is fixed in the latest version of
ganeti, 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.
Apollon Oikonomopoulos  (supplier of updated 

Processed: bug 912630 is forwarded to https://github.com/lens/lens-aeson/issues/30

[Debian Bug Tracking System]

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

> forwarded 912630 https://github.com/lens/lens-aeson/issues/30
Bug #912630 [src:haskell-lens-aeson] haskell-lens-aeson: FTBFS on various archs
Set Bug forwarded-to-address to 'https://github.com/lens/lens-aeson/issues/30'.
> thanks
Stopping processing here.

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

Bug#912297: ansible: CVE-2018-16837

[Chris Lamb]

Chris Lamb wrote:

> Security team: This still affects stretch and jessie [unless]
> I'm missing something - would you like me to prepare an upload for
> stable? I'm happy to take the LTS side of things.

Gentle ping on this?


Regards,

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

Bug#885678: marked as done (gmysqlcc: Depends on unmaintained gtksourceview2)

[Debian Bug Tracking System]

Your message dated Mon, 05 Nov 2018 05:52:25 +
with message-id 
and subject line Bug#911253: Removed package(s) from unstable
has caused the Debian Bug report #885678,
regarding gmysqlcc: Depends on unmaintained gtksourceview2
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.)


-- 
885678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885678
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gmysqlcc
Version: 0.3.0-6
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs gtksourceview2
Tags: sid buster

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. These libraries have been
deprecated and unmaintained for several years.

Your package depends on gtksourceview2 which has not had a new release
since 2010.

Please port your package to GTK3 and gtksourceview3 and related
maintained libraries. Otherwise, please consider requesting that your
package be removed from Debian to help us complete this goal.

[1] https://lists.debian.org/debian-devel/2017/10/msg00299.html

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Version: 0.3.0-6+rm

Dear submitter,

as the package gmysqlcc 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/911253

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.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#871191: marked as done (eclipse-mylyn-tasks-github: FTBFS: java.io.FileNotFoundException: /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/${eclipse.pdebuild.scripts}/

[Debian Bug Tracking System]

Your message dated Mon, 05 Nov 2018 05:58:58 +
with message-id 
and subject line Bug#911317: Removed package(s) from unstable
has caused the Debian Bug report #871191,
regarding eclipse-mylyn-tasks-github: FTBFS: java.io.FileNotFoundException: 
/usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/${eclipse.pdebuild.scripts}/genericTargets.xml
 (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.)


-- 
871191: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871191
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: eclipse-mylyn-tasks-github
Version: 3.3.0-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 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 '/<>'
> jh_compilefeatures --build-opts '-Dbuild.compiler=modern -DjavacSource=1.7 
> -DjavacTarget=1.7'
> mkdir -p /<>/debian/.eclipse-build/build
> mkdir -p /<>/debian/.eclipse-build/build/home
> mkdir -p /<>/debian/.eclipse-build/build/home/workspace
> Building feature = org.eclipse.mylyn.github.feature.
> Symlinking SDK and "mylyn egit" into 
> /<>/debian/.eclipse-build/build/SDK directory.
> /bin/sh /usr/lib/eclipse/buildscripts/copy-platform 
> /<>/debian/.eclipse-build/build/SDK /usr/lib/eclipse mylyn egit
> ls: cannot access '/usr/lib/eclipse/dropins/jdt/plugins/*': No such file or 
> directory
> ls: cannot access '/usr/lib/eclipse/dropins/jdt/features/*': No such file or 
> directory
> ln: failed to create symbolic link 'icon.xpm': File exists
> ln: failed to create symbolic link 'notice.html': File exists
> ln: failed to create symbolic link 'readme': File exists
> ln: failed to create symbolic link 'swt-gtk-3.8.1.jar': File exists
> ln: failed to create symbolic link 'swt-gtk.jar': File exists
> ln: failed to create symbolic link 'swt.jar': File exists
> Starting build:
> Buildfile: 
> /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/build.xml
> 
> main:
> 
> preBuild:
>  [copy] Copying 1 file to /<>/debian/.eclipse-build/build
> 
> preSetup:
> 
> getMapFiles:
> 
> postSetup:
> 
> processRepos:
> 
> fetch:
> 
> generate:
> 
> preGenerate:
>  [exec] preparing files in /<>/debian/.eclipse-build for 
> buildfile generation ...
>  [exec]   making the 'features' and 'plugins' directories
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.eclipse.mylyn.github.feature
>  -> /<>/debian/.eclipse-build/org.eclipse.mylyn.github-feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/plugins/org.eclipse.egit.github.core.tests
>  -> /<>/debian/.eclipse-build/org.eclipse.egit.github.core.tests/
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/plugins/org.eclipse.egit.github.core
>  -> /<>/debian/.eclipse-build/org.eclipse.egit.github.core/
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/plugins/org.eclipse.mylyn.github.core
>  -> /<>/debian/.eclipse-build/org.eclipse.mylyn.github.core/
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/plugins/org.eclipse.mylyn.github.doc
>  -> /<>/debian/.eclipse-build/org.eclipse.mylyn.github.doc/
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/plugins/org.eclipse.mylyn.github.tests
>  -> /<>/debian/.eclipse-build/org.eclipse.mylyn.github.tests/
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/plugins/org.eclipse.mylyn.github.ui
>  -> /<>/debian/.eclipse-build/org.eclipse.mylyn.github.ui/
>  [exec] done
> 
> symlinkDeps:
> [apply] Applied ln to 1 file and 0 directories.
> 
> allElements:
> 
> BUILD FAILED
> /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/build.xml:35:
>  The following error occurred while executing this line:
> /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/build.xml:91:
>  The following error occurred while executing this line:
> /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/templates/package-build/customTargets.xml:19:
>  The following error occurred while executing this line:
> java.io.FileNotFoundException: 
> /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/${eclipse.pdebuild.scripts}/genericTargets.xml
>  (No such file or directory)
>   at java.io.FileInputStream.open0(Native Method)
>   at java.io.FileInputStream.open(FileInputStream.java:195)
>

Bug#871205: marked as done (eclipse-ptp: FTBFS: java.io.FileNotFoundException: /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/${eclipse.pdebuild.scripts}/genericTargets.

[Debian Bug Tracking System]

Your message dated Mon, 05 Nov 2018 05:58:35 +
with message-id 
and subject line Bug#911318: Removed package(s) from unstable
has caused the Debian Bug report #871205,
regarding eclipse-ptp: FTBFS: java.io.FileNotFoundException: 
/usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/${eclipse.pdebuild.scripts}/genericTargets.xml
 (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.)


-- 
871205: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871205
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: eclipse-ptp
Version: 8.1.1-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 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 '/<>'
> jh_compilefeatures --build-opts="-DjavacTarget=1.6 -DjavacSource=1.6 
> -DbuildId=dist -DforceContextQualifier=dist"
> mkdir -p /<>/debian/.eclipse-build/build
> mkdir -p /<>/debian/.eclipse-build/build/home
> mkdir -p /<>/debian/.eclipse-build/build/home/workspace
> Building feature = org.eclipse.ptp.core.
> Symlinking SDK into /<>/debian/.eclipse-build/build/SDK 
> directory.
> /bin/sh /usr/lib/eclipse/buildscripts/copy-platform 
> /<>/debian/.eclipse-build/build/SDK /usr/lib/eclipse
> ls: cannot access '/usr/lib/eclipse/dropins/jdt/plugins/*': No such file or 
> directory
> ls: cannot access '/usr/lib/eclipse/dropins/jdt/features/*': No such file or 
> directory
> ln: failed to create symbolic link 'icon.xpm': File exists
> ln: failed to create symbolic link 'notice.html': File exists
> ln: failed to create symbolic link 'readme': File exists
> ln: failed to create symbolic link 'swt-gtk-3.8.1.jar': File exists
> ln: failed to create symbolic link 'swt-gtk.jar': File exists
> ln: failed to create symbolic link 'swt.jar': File exists
> Starting build:
> Buildfile: 
> /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/build.xml
> 
> main:
> 
> preBuild:
>  [copy] Copying 1 file to /<>/debian/.eclipse-build/build
> 
> preSetup:
> 
> getMapFiles:
> 
> postSetup:
> 
> processRepos:
> 
> fetch:
> 
> generate:
> 
> preGenerate:
>  [exec] preparing files in /<>/debian/.eclipse-build for 
> buildfile generation ...
>  [exec]   making the 'features' and 'plugins' directories
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.eclipse.ptp.core -> 
> /<>/debian/.eclipse-build/org.eclipse.ptp.core-feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.eclipse.ptp.remotetools
>  -> /<>/debian/.eclipse-build/org.eclipse.ptp.remotetools-feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.eclipse.ptp.rdt -> 
> /<>/debian/.eclipse-build/org.eclipse.ptp.rdt-feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.eclipse.ptp.remote.remotetools
>  -> 
> /<>/debian/.eclipse-build/org.eclipse.ptp.remote.remotetools-feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.eclipse.ptp.rdt.editor
>  -> /<>/debian/.eclipse-build/org.eclipse.ptp.rdt.editor-feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.eclipse.ptp.remote 
> -> /<>/debian/.eclipse-build/org.eclipse.ptp.remote-feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.eclipse.ptp.services
>  -> /<>/debian/.eclipse-build/org.eclipse.ptp.services-feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.eclipse.ptp.remote.rse
>  -> /<>/debian/.eclipse-build/org.eclipse.ptp.remote.rse-feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/plugins/org.eclipse.ptp.core -> 
> /<>/debian/.eclipse-build/org.eclipse.ptp.core/
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/plugins/org.eclipse.ptp.rdt.core 
> -> /<>/debian/.eclipse-build/org.eclipse.ptp.rdt.core/
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/plugins/org.eclipse.ptp.rdt.doc.user
>  -> /<>/debian/.eclipse-build/org.eclipse.ptp.rdt.doc.user/
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/plugins/org.eclipse.ptp.rdt.editor
>  -> /<>/debian/.eclipse-build/org.eclipse.ptp.rdt.editor/
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/plugins/org.eclipse.ptp.rdt.make.ui
>  -> /<>/debian/.eclipse-build/org.eclipse.ptp.rdt.make.ui/
>  [exec]   

Bug#871212: marked as done (eclipse-mercurialeclipse: FTBFS: java.io.FileNotFoundException: /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/${eclipse.pdebuild.scripts}/ge

[Debian Bug Tracking System]

Your message dated Mon, 05 Nov 2018 05:57:23 +
with message-id 
and subject line Bug#911315: Removed package(s) from unstable
has caused the Debian Bug report #871212,
regarding eclipse-mercurialeclipse: FTBFS: java.io.FileNotFoundException: 
/usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/${eclipse.pdebuild.scripts}/genericTargets.xml
 (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.)


-- 
871212: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871212
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: eclipse-mercurialeclipse
Version: 1.9.4-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 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 '/<>'
> jh_compilefeatures --build-opts '-DjavacTarget=1.5 -DjavacSource=1.5 
> -DforceContextQualifier=dist'
> jh_compilefeatures: Compatibility levels before 9 are deprecated (level 8 in 
> use)
> mkdir -p /<>/debian/.eclipse-build/build
> mkdir -p /<>/debian/.eclipse-build/build/home
> mkdir -p /<>/debian/.eclipse-build/build/home/workspace
> Building feature = mercurialeclipse.
> Symlinking SDK and "mylyn" into 
> /<>/debian/.eclipse-build/build/SDK directory.
> /bin/sh /usr/lib/eclipse/buildscripts/copy-platform 
> /<>/debian/.eclipse-build/build/SDK /usr/lib/eclipse mylyn
> ls: cannot access '/usr/lib/eclipse/dropins/jdt/plugins/*': No such file or 
> directory
> ls: cannot access '/usr/lib/eclipse/dropins/jdt/features/*': No such file or 
> directory
> ln: failed to create symbolic link 'icon.xpm': File exists
> ln: failed to create symbolic link 'notice.html': File exists
> ln: failed to create symbolic link 'readme': File exists
> ln: failed to create symbolic link 'swt-gtk-3.8.1.jar': File exists
> ln: failed to create symbolic link 'swt-gtk.jar': File exists
> ln: failed to create symbolic link 'swt.jar': File exists
> Starting build:
> Buildfile: 
> /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/build.xml
> 
> main:
> 
> preBuild:
>  [copy] Copying 1 file to /<>/debian/.eclipse-build/build
> 
> preSetup:
> 
> getMapFiles:
> 
> postSetup:
> 
> processRepos:
> 
> fetch:
> 
> generate:
> 
> preGenerate:
>  [exec] preparing files in /<>/debian/.eclipse-build for 
> buildfile generation ...
>  [exec]   making the 'features' and 'plugins' directories
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/mercurialeclipse -> 
> /<>/debian/.eclipse-build/feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/plugins/com.vectrace.MercurialEclipse
>  -> /<>/debian/.eclipse-build/plugin/
>  [exec] done
> 
> symlinkDeps:
> 
> allElements:
> 
> BUILD FAILED
> /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/build.xml:35:
>  The following error occurred while executing this line:
> /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/build.xml:91:
>  The following error occurred while executing this line:
> /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/templates/package-build/customTargets.xml:19:
>  The following error occurred while executing this line:
> java.io.FileNotFoundException: 
> /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/${eclipse.pdebuild.scripts}/genericTargets.xml
>  (No such file or directory)
>   at java.io.FileInputStream.open0(Native Method)
>   at java.io.FileInputStream.open(FileInputStream.java:195)
>   at java.io.FileInputStream.(FileInputStream.java:138)
>   at 
> org.apache.tools.ant.helper.ProjectHelper2.parse(ProjectHelper2.java:250)
>   at 
> org.apache.tools.ant.helper.ProjectHelper2.parse(ProjectHelper2.java:178)
>   at 
> org.apache.tools.ant.ProjectHelper.configureProject(ProjectHelper.java:93)
>   at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:392)
>   at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:293)
>   at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
>   at org.apache.tools.ant.Task.perform(Task.java:348)
>   at 

Bug#871341: marked as done (eclipse-mylyn: FTBFS: debian/ecoreToJava.xml:16: Problem: failed to create task or type emf.Ecore2Java)

[Debian Bug Tracking System]

Your message dated Mon, 05 Nov 2018 05:58:00 +
with message-id 
and subject line Bug#911316: Removed package(s) from unstable
has caused the Debian Bug report #871341,
regarding eclipse-mylyn: FTBFS: debian/ecoreToJava.xml:16: Problem: failed to 
create task or type emf.Ecore2Java
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.)


-- 
871341: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871341
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: eclipse-mylyn
Version: 3.12.0-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170807 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 '/<>'
> # Regenerate org.eclipse.mylyn.builds.core code from model
> /usr/lib/eclipse/eclipse \
> -application org.eclipse.ant.core.antRunner  \
> -configuration debian/.eclipse-build/.platform/configuration \
> -buildfile debian/ecoreToJava.xml\
> -data debian/.eclipse-build  \
> -Dosgi.sharedConfiguration.area=debian/.eclipse-build/build/home \
> -consoleLog -noSplash
> OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support 
> was removed in 8.0
> Buildfile: debian/ecoreToJava.xml
> 
> default:
> 
> BUILD FAILED
> /<>/debian/ecoreToJava.xml:16: Problem: failed to create task or 
> type emf.Ecore2Java
> Cause: The name is undefined.
> Action: Check the spelling.
> Action: Check that any custom tasks/types have been declared.
> Action: Check that any / declarations have taken place.
> 
> 
> Total time: 0 seconds
> !SESSION 2017-08-07 11:26:31.669 
> ---
> eclipse.buildId=debbuild
> java.version=1.8.0_141
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments:  -application org.eclipse.ant.core.antRunner -buildfile 
> debian/ecoreToJava.xml 
> -Dosgi.sharedConfiguration.area=debian/.eclipse-build/build/home
> Command-line arguments:  -os linux -ws gtk -arch x86_64 -application 
> org.eclipse.ant.core.antRunner -buildfile debian/ecoreToJava.xml -data 
> debian/.eclipse-build 
> -Dosgi.sharedConfiguration.area=debian/.eclipse-build/build/home -consoleLog
> 
> !ENTRY org.eclipse.osgi 2 0 2017-08-07 11:26:35.287
> !MESSAGE One or more bundles are not resolved because the following root 
> constraints are not resolved:
> !SUBENTRY 1 org.eclipse.osgi 2 0 2017-08-07 11:26:35.287
> !MESSAGE Bundle 
> reference:file:plugins/org.eclipse.ecf.provider.filetransfer.httpclient.ssl_1.0.0.dist.jar
>  was not resolved.
> !SUBENTRY 2 org.eclipse.ecf.provider.filetransfer.httpclient.ssl 2 0 
> 2017-08-07 11:26:35.287
> !MESSAGE Missing required capability Require-Capability: osgi.ee; 
> filter="(|(&(osgi.ee=CDC/Foundation)(version=1.1))(&(osgi.ee=JavaSE)(version=1.4)))".
> !SUBENTRY 1 org.eclipse.osgi 2 0 2017-08-07 11:26:35.287
> !MESSAGE Bundle 
> reference:file:plugins/org.eclipse.ecf.provider.filetransfer.httpclient_4.0.200.dist.jar
>  was not resolved.
> !SUBENTRY 2 org.eclipse.ecf.provider.filetransfer.httpclient 2 0 2017-08-07 
> 11:26:35.287
> !MESSAGE Missing imported package 
> org.apache.commons.httpclient.auth_[3.0.1,3.1.0].
> !SUBENTRY 2 org.eclipse.ecf.provider.filetransfer.httpclient 2 0 2017-08-07 
> 11:26:35.287
> !MESSAGE Missing imported package 
> org.apache.commons.httpclient.protocol_[3.0.1,3.1.0].
> !SUBENTRY 2 org.eclipse.ecf.provider.filetransfer.httpclient 2 0 2017-08-07 
> 11:26:35.288
> !MESSAGE Missing imported package 
> org.apache.commons.httpclient.methods_[3.0.1,3.1.0].
> !SUBENTRY 2 org.eclipse.ecf.provider.filetransfer.httpclient 2 0 2017-08-07 
> 11:26:35.288
> !MESSAGE Missing imported package org.apache.commons.httpclient_[3.0.1,3.1.0].
> !SUBENTRY 2 org.eclipse.ecf.provider.filetransfer.httpclient 2 0 2017-08-07 
> 11:26:35.288
> !MESSAGE Missing imported package 
> org.apache.commons.httpclient.params_[3.0.1,3.1.0].
> !SUBENTRY 2 org.eclipse.ecf.provider.filetransfer.httpclient 2 0 2017-08-07 
> 11:26:35.288
> !MESSAGE Missing imported package 
> org.apache.commons.httpclient.util_[3.0.1,3.1.0].
> 
> !ENTRY org.eclipse.osgi 2 0 2017-08-07 11:26:35.293
> !MESSAGE The following is a complete list of bundles which are not resolved, 
> see the prior log entry for the root cause if it exists:
> !SUBENTRY 1 

Bug#871192: marked as done (eclipse-remote-services-api: FTBFS: java.io.FileNotFoundException: /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/${eclipse.pdebuild.scripts}

[Debian Bug Tracking System]

Your message dated Mon, 05 Nov 2018 05:59:50 +
with message-id 
and subject line Bug#911346: Removed package(s) from unstable
has caused the Debian Bug report #871192,
regarding eclipse-remote-services-api: FTBFS: java.io.FileNotFoundException: 
/usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/${eclipse.pdebuild.scripts}/genericTargets.xml
 (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.)


-- 
871192: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871192
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: eclipse-remote-services-api
Version: 8.0.0-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 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 '/<>'
> jh_compilefeatures --build-opts="-DjavacTarget=1.7 -DjavacSource=1.7 
> -DbuildId=dist -DforceContextQualifier=dist"
> mkdir -p /<>/debian/.eclipse-build/build
> mkdir -p /<>/debian/.eclipse-build/build/home
> mkdir -p /<>/debian/.eclipse-build/build/home/workspace
> Building feature = org.eclipse.remote.
> Symlinking SDK into /<>/debian/.eclipse-build/build/SDK 
> directory.
> /bin/sh /usr/lib/eclipse/buildscripts/copy-platform 
> /<>/debian/.eclipse-build/build/SDK /usr/lib/eclipse
> ls: cannot access '/usr/lib/eclipse/dropins/jdt/plugins/*': No such file or 
> directory
> ls: cannot access '/usr/lib/eclipse/dropins/jdt/features/*': No such file or 
> directory
> ln: failed to create symbolic link 'icon.xpm': File exists
> ln: failed to create symbolic link 'notice.html': File exists
> ln: failed to create symbolic link 'readme': File exists
> ln: failed to create symbolic link 'swt-gtk-3.8.1.jar': File exists
> ln: failed to create symbolic link 'swt-gtk.jar': File exists
> ln: failed to create symbolic link 'swt.jar': File exists
> Starting build:
> Buildfile: 
> /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/build.xml
> 
> main:
> 
> preBuild:
>  [copy] Copying 1 file to /<>/debian/.eclipse-build/build
> 
> preSetup:
> 
> getMapFiles:
> 
> postSetup:
> 
> processRepos:
> 
> fetch:
> 
> generate:
> 
> preGenerate:
>  [exec] preparing files in /<>/debian/.eclipse-build for 
> buildfile generation ...
>  [exec]   making the 'features' and 'plugins' directories
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.eclipse.remote -> 
> /<>/debian/.eclipse-build/org.eclipse.remote-feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/plugins/org.eclipse.remote.core 
> -> /<>/debian/.eclipse-build/org.eclipse.remote.core/
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/plugins/org.eclipse.remote.jsch.core
>  -> /<>/debian/.eclipse-build/org.eclipse.remote.jsch.core/
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/plugins/org.eclipse.remote.jsch.ui
>  -> /<>/debian/.eclipse-build/org.eclipse.remote.jsch.ui/
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/plugins/org.eclipse.remote.ui -> 
> /<>/debian/.eclipse-build/org.eclipse.remote.ui/
>  [exec] done
> 
> symlinkDeps:
> 
> allElements:
> 
> BUILD FAILED
> /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/build.xml:35:
>  The following error occurred while executing this line:
> /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/build.xml:91:
>  The following error occurred while executing this line:
> /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/templates/package-build/customTargets.xml:19:
>  The following error occurred while executing this line:
> java.io.FileNotFoundException: 
> /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/${eclipse.pdebuild.scripts}/genericTargets.xml
>  (No such file or directory)
>   at java.io.FileInputStream.open0(Native Method)
>   at java.io.FileInputStream.open(FileInputStream.java:195)
>   at java.io.FileInputStream.(FileInputStream.java:138)
>   at 
> org.apache.tools.ant.helper.ProjectHelper2.parse(ProjectHelper2.java:250)
>   at 
> org.apache.tools.ant.helper.ProjectHelper2.parse(ProjectHelper2.java:178)
>   at 
> org.apache.tools.ant.ProjectHelper.configureProject(ProjectHelper.java:93)
>   at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:392)
>   at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:293)

Bug#871211: marked as done (eclipse-pydev: FTBFS: java.io.FileNotFoundException: /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/${eclipse.pdebuild.scripts}/genericTarget

[Debian Bug Tracking System]

Your message dated Mon, 05 Nov 2018 05:59:25 +
with message-id 
and subject line Bug#911319: Removed package(s) from unstable
has caused the Debian Bug report #871211,
regarding eclipse-pydev: FTBFS: java.io.FileNotFoundException: 
/usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/${eclipse.pdebuild.scripts}/genericTargets.xml
 (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.)


-- 
871211: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871211
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: eclipse-pydev
Version: 3.9.2-5
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 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 '/<>'
> jh_compilefeatures -i --build-opts="-DjavacTarget=1.7 -DjavacSource=1.7 
> -DbuildId=dist -DforceContextQualifier=dist"
> mkdir -p /<>/debian/.eclipse-build/build
> mkdir -p /<>/debian/.eclipse-build/build/home
> mkdir -p /<>/debian/.eclipse-build/build/home/workspace
> Building feature = org.python.pydev.feature.
> Symlinking SDK into /<>/debian/.eclipse-build/build/SDK 
> directory.
> /bin/sh /usr/lib/eclipse/buildscripts/copy-platform 
> /<>/debian/.eclipse-build/build/SDK /usr/lib/eclipse
> ls: cannot access '/usr/lib/eclipse/dropins/jdt/plugins/*': No such file or 
> directory
> ls: cannot access '/usr/lib/eclipse/dropins/jdt/features/*': No such file or 
> directory
> ln: failed to create symbolic link 'icon.xpm': File exists
> ln: failed to create symbolic link 'notice.html': File exists
> ln: failed to create symbolic link 'readme': File exists
> ln: failed to create symbolic link 'swt-gtk-3.8.1.jar': File exists
> ln: failed to create symbolic link 'swt-gtk.jar': File exists
> ln: failed to create symbolic link 'swt.jar': File exists
> Starting build:
> Buildfile: 
> /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/build.xml
> 
> main:
> 
> preBuild:
>  [copy] Copying 1 file to /<>/debian/.eclipse-build/build
> 
> preSetup:
> 
> getMapFiles:
> 
> postSetup:
> 
> processRepos:
> 
> fetch:
> 
> generate:
> 
> preGenerate:
>  [exec] preparing files in /<>/debian/.eclipse-build for 
> buildfile generation ...
>  [exec]   making the 'features' and 'plugins' directories
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.python.pydev.mylyn.feature
>  -> 
> /<>/debian/.eclipse-build/features/org.python.pydev.mylyn.feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.python.pydev.feature
>  -> /<>/debian/.eclipse-build/features/org.python.pydev.feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/plugins/com.python.pydev.analysis
>  -> /<>/debian/.eclipse-build/plugins/com.python.pydev.analysis/
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/plugins/com.python.pydev.codecompletion
>  -> 
> /<>/debian/.eclipse-build/plugins/com.python.pydev.codecompletion/
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/plugins/com.python.pydev.debug 
> -> /<>/debian/.eclipse-build/plugins/com.python.pydev.debug/
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/plugins/com.python.pydev.fastparser
>  -> 
> /<>/debian/.eclipse-build/plugins/com.python.pydev.fastparser/
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/plugins/com.python.pydev.refactoring
>  -> 
> /<>/debian/.eclipse-build/plugins/com.python.pydev.refactoring/
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/plugins/com.python.pydev.runalltests
>  [exec]  -> 
> /<>/debian/.eclipse-build/plugins/com.python.pydev.runalltests/  
> making symlink: 
> /<>/debian/.eclipse-build/build/plugins/com.python.pydev -> 
> /<>/debian/.eclipse-build/plugins/com.python.pydev/
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/plugins/org.python.pydev.ast -> 
> /<>/debian/.eclipse-build/plugins/org.python.pydev.ast/
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/plugins/org.python.pydev.core -> 
> /<>/debian/.eclipse-build/plugins/org.python.pydev.core/
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/plugins/org.python.pydev.customizations
>  -> 
> /<>/debian/.eclipse-build/plugins/org.python.pydev.customizations/
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/plugins/org.python.pydev.debug 
> -> 

Bug#878240: marked as done (eclipse-pydev: Eclipse doesn't show the ability to create a Python project anymore)

[Debian Bug Tracking System]

Your message dated Mon, 05 Nov 2018 05:59:25 +
with message-id 
and subject line Bug#911319: Removed package(s) from unstable
has caused the Debian Bug report #878240,
regarding eclipse-pydev: Eclipse doesn't show the ability to create a Python 
project anymore
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.)


-- 
878240: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878240
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: eclipse-pydev
Version: 3.9.2-5
Severity: grave
Justification: renders package unusable

Hi.

After a period of not using Eclipse for Python development, I saw that
jython was updated and, then, I tried to import a project that I wanted
restart working on.

Upon start, eclipse hung when I told it to use the old workspace. I gave up
and, then, started with a new workspace. Then, eclipse showed up, but when I
tried to either create or import a Python project, nothing was recognized as
a Python project.

I removed eclipse's configuration and started fresh, with the same results.
I even grabbed jython 2.5 from stable and redid the same steps and no Pydev
was in sight.

Is this reproducible? If yes, then I think that the severity of this bug is
granted.  Otherwise, if you can make pydev work in the current
circumstances, please, feel free to lower the severity of the bug.

If there is any extra information that you would like me to supply, please
let me know and I will try my best.


Thanks,

Rogério Brito.


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

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

Versions of packages eclipse-pydev depends on:
ii  eclipse-pydev-data  3.9.2-5
ii  libc6   2.24-17
ii  libgcc1 1:7.2.0-8
ii  libstdc++6  7.2.0-8

Versions of packages eclipse-pydev recommends:
ii  gdb  7.12-6

eclipse-pydev suggests no packages.

-- no debconf information

-- 
Rogério Brito : rbrito@{ime.usp.br,gmail.com} : GPG key 4096R/BCFC
http://cynic.cc/blog/ : github.com/rbrito : profiles.google.com/rbrito
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br
--- End Message ---
--- Begin Message ---
Version: 3.9.2-5+rm

Dear submitter,

as the package eclipse-pydev 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/911319

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.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#912814: Messes up newsreader cache and history

[Yangfl]

On Sun, 4 Nov 2018 00:10:16 +0100 vitaminx  wrote:
> Package: wallstreet
> Version: 1.14-1
> Severity: grave
>
> I just installed this package out of curiosity and found that it messes up my 
> newsreader's cache (I'm using newsbeuter).
> All downloaded newsfeeds are completely gone and everything new appears as 
> unread.
>
Not using any newsreader so can't figure out why. Any suggestion?

The command wallstreet invokes is `newsbeuter -r -C
/usr/share/wallstreet/newsbeuter.config -u
/usr/share/wallstreet/newsbeuter.urls`

Thanks

Bug#871200: marked as done (eclipse-eclox: FTBFS: java.io.FileNotFoundException: /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/${eclipse.pdebuild.scripts}/genericTarget

[Debian Bug Tracking System]

Your message dated Mon, 05 Nov 2018 05:55:33 +
with message-id 
and subject line Bug#911307: Removed package(s) from unstable
has caused the Debian Bug report #871200,
regarding eclipse-eclox: FTBFS: java.io.FileNotFoundException: 
/usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/${eclipse.pdebuild.scripts}/genericTargets.xml
 (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.)


-- 
871200: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871200
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: eclipse-eclox
Version: 0.10.1-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --with eclipse-helper
>dh_update_autotools_config
>dh_auto_configure
>dh_auto_build
>jh_setupenvironment
>jh_generateorbitdir
>jh_compilefeatures
> mkdir -p /<>/debian/.eclipse-build/build
> mkdir -p /<>/debian/.eclipse-build/build/home
> mkdir -p /<>/debian/.eclipse-build/build/home/workspace
> Building feature = org.gna.eclox.
> Symlinking SDK into /<>/debian/.eclipse-build/build/SDK 
> directory.
> /bin/sh /usr/lib/eclipse/buildscripts/copy-platform 
> /<>/debian/.eclipse-build/build/SDK /usr/lib/eclipse
> ls: cannot access '/usr/lib/eclipse/dropins/jdt/plugins/*': No such file or 
> directory
> ls: cannot access '/usr/lib/eclipse/dropins/jdt/features/*': No such file or 
> directory
> ln: failed to create symbolic link 'icon.xpm': File exists
> ln: failed to create symbolic link 'notice.html': File exists
> ln: failed to create symbolic link 'readme': File exists
> ln: failed to create symbolic link 'swt-gtk-3.8.1.jar': File exists
> ln: failed to create symbolic link 'swt-gtk.jar': File exists
> ln: failed to create symbolic link 'swt.jar': File exists
> Starting build:
> Buildfile: 
> /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/build.xml
> 
> main:
> 
> preBuild:
>  [copy] Copying 1 file to /<>/debian/.eclipse-build/build
> 
> preSetup:
> 
> getMapFiles:
> 
> postSetup:
> 
> processRepos:
> 
> fetch:
> 
> generate:
> 
> preGenerate:
>  [exec] preparing files in /<>/debian/.eclipse-build for 
> buildfile generation ...
>  [exec]   making the 'features' and 'plugins' directories
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.gna.eclox -> 
> /<>/debian/.eclipse-build/eclox.feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/plugins/org.gna.eclox.core -> 
> /<>/debian/.eclipse-build/eclox.core/
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/plugins/org.gna.eclox.help -> 
> /<>/debian/.eclipse-build/eclox.help/
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/plugins/org.gna.eclox.ui -> 
> /<>/debian/.eclipse-build/eclox.ui/
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/plugins/org.gna.eclox -> 
> /<>/debian/.eclipse-build/eclox/
>  [exec] done
> 
> symlinkDeps:
> 
> allElements:
> 
> BUILD FAILED
> /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/build.xml:35:
>  The following error occurred while executing this line:
> /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/build.xml:91:
>  The following error occurred while executing this line:
> /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/templates/package-build/customTargets.xml:19:
>  The following error occurred while executing this line:
> java.io.FileNotFoundException: 
> /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/${eclipse.pdebuild.scripts}/genericTargets.xml
>  (No such file or directory)
>   at java.io.FileInputStream.open0(Native Method)
>   at java.io.FileInputStream.open(FileInputStream.java:195)
>   at java.io.FileInputStream.(FileInputStream.java:138)
>   at 
> org.apache.tools.ant.helper.ProjectHelper2.parse(ProjectHelper2.java:250)
>   at 
> org.apache.tools.ant.helper.ProjectHelper2.parse(ProjectHelper2.java:178)
>   at 
> org.apache.tools.ant.ProjectHelper.configureProject(ProjectHelper.java:93)
>   at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:392)
>   at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:293)
>   at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
>   at 
> 

Bug#871201: marked as done (eclipse-cdt: FTBFS: java.io.FileNotFoundException: /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/${eclipse.pdebuild.scripts}/genericTargets.

[Debian Bug Tracking System]

Your message dated Mon, 05 Nov 2018 05:55:01 +
with message-id 
and subject line Bug#911305: Removed package(s) from unstable
has caused the Debian Bug report #871201,
regarding eclipse-cdt: FTBFS: java.io.FileNotFoundException: 
/usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/${eclipse.pdebuild.scripts}/genericTargets.xml
 (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.)


-- 
871201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871201
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: eclipse-cdt
Version: 8.6.0-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 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 '/<>'
> jh_compilefeatures --build-opts="-DjavacTarget=1.7 -DjavacSource=1.7 
> -DbuildId=dist -DforceContextQualifier=dist";
> mkdir -p /<>/debian/.eclipse-build/build
> mkdir -p /<>/debian/.eclipse-build/build/home
> mkdir -p /<>/debian/.eclipse-build/build/home/workspace
> Building feature = org.eclipse.cdt.native.
> Symlinking SDK into /<>/debian/.eclipse-build/build/SDK 
> directory.
> /bin/sh /usr/lib/eclipse/buildscripts/copy-platform 
> /<>/debian/.eclipse-build/build/SDK /usr/lib/eclipse
> ls: cannot access '/usr/lib/eclipse/dropins/jdt/plugins/*': No such file or 
> directory
> ls: cannot access '/usr/lib/eclipse/dropins/jdt/features/*': No such file or 
> directory
> ln: failed to create symbolic link 'icon.xpm': File exists
> ln: failed to create symbolic link 'notice.html': File exists
> ln: failed to create symbolic link 'readme': File exists
> ln: failed to create symbolic link 'swt-gtk-3.8.1.jar': File exists
> ln: failed to create symbolic link 'swt-gtk.jar': File exists
> ln: failed to create symbolic link 'swt.jar': File exists
> Starting build:
> Buildfile: 
> /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/build.xml
> 
> main:
> 
> preBuild:
>  [copy] Copying 1 file to /<>/debian/.eclipse-build/build
> 
> preSetup:
> 
> getMapFiles:
> 
> postSetup:
> 
> processRepos:
> 
> fetch:
> 
> generate:
> 
> preGenerate:
>  [exec] preparing files in /<>/debian/.eclipse-build for 
> buildfile generation ...
>  [exec]   making the 'features' and 'plugins' directories
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.eclipse.cdt.qt -> 
> /<>/debian/.eclipse-build/org.eclipse.cdt.qt-feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.eclipse.cdt.gnu.dsf 
> -> /<>/debian/.eclipse-build/org.eclipse.cdt.gnu.dsf-feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.eclipse.cdt.build.crossgcc
>  -> 
> /<>/debian/.eclipse-build/org.eclipse.cdt.build.crossgcc-feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.eclipse.cdt.source 
> -> 
> /<>/debian/.eclipse-build/org.eclipse.cdt.build.crossgcc-feature/sourceTemplateFeature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.eclipse.cdt.debug.ui.memory
>  -> 
> /<>/debian/.eclipse-build/org.eclipse.cdt.debug.ui.memory-feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.eclipse.cdt.gnu.multicorevisualizer
>  -> 
> /<>/debian/.eclipse-build/org.eclipse.cdt.gnu.multicorevisualizer-feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.eclipse.cdt.autotools
>  -> /<>/debian/.eclipse-build/org.eclipse.cdt.autotools-feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.eclipse.cdt.debug.ui.memory.source
>  -> 
> /<>/debian/.eclipse-build/org.eclipse.cdt.debug.ui.memory.source-feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.eclipse.cdt.gnu.build
>  -> /<>/debian/.eclipse-build/org.eclipse.cdt.gnu.build-feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.eclipse.cdt.testsrunner.source.feature
>  -> 
> /<>/debian/.eclipse-build/org.eclipse.cdt.testsrunner.source.feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.eclipse.cdt.visualizer
>  -> /<>/debian/.eclipse-build/org.eclipse.cdt.visualizer-feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.eclipse.cdt.launch.remote
>  -> 
> /<>/debian/.eclipse-build/org.eclipse.cdt.launch.remote-feature
>  

Bug#869089: marked as done (eclipse-gef FTBFS: FileNotFoundException: /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/${eclipse.pdebuild.scripts}/genericTargets.xml (No s

[Debian Bug Tracking System]

Your message dated Mon, 05 Nov 2018 05:56:31 +
with message-id 
and subject line Bug#911309: Removed package(s) from unstable
has caused the Debian Bug report #869089,
regarding eclipse-gef FTBFS: FileNotFoundException: 
/usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/${eclipse.pdebuild.scripts}/genericTargets.xml
 (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.)


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

Some recent change in unstable makes eclipse-gef FTBFS:

https://tests.reproducible-builds.org/debian/history/eclipse-gef.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/eclipse-gef.html

...
allElements:

BUILD FAILED
/usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/build.xml:35:
 The following error occurred while executing this line:
/usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/build.xml:91:
 The following error occurred while executing this line:
/usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/templates/package-build/customTargets.xml:19:
 The following error occurred while executing this line:
java.io.FileNotFoundException: 
/usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/${eclipse.pdebuild.scripts}/genericTargets.xml
 (No such file or directory)
at java.io.FileInputStream.open0(Native Method)
at java.io.FileInputStream.open(FileInputStream.java:195)
at java.io.FileInputStream.(FileInputStream.java:138)
at 
org.apache.tools.ant.helper.ProjectHelper2.parse(ProjectHelper2.java:250)
at 
org.apache.tools.ant.helper.ProjectHelper2.parse(ProjectHelper2.java:178)
at 
org.apache.tools.ant.ProjectHelper.configureProject(ProjectHelper.java:93)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:392)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:293)
at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:435)
at org.apache.tools.ant.Target.performTasks(Target.java:456)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1405)
at 
org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
at 
org.eclipse.ant.internal.core.ant.EclipseSingleCheckExecutor.executeTargets(EclipseSingleCheckExecutor.java:30)
at org.apache.tools.ant.Project.executeTargets(Project.java:1260)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:441)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:293)
at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:435)
at org.apache.tools.ant.Target.performTasks(Target.java:456)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1405)
at 
org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
at 
org.eclipse.ant.internal.core.ant.EclipseSingleCheckExecutor.executeTargets(EclipseSingleCheckExecutor.java:30)
at org.apache.tools.ant.Project.executeTargets(Project.java:1260)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:441)
at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:105)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:293)
at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 

Bug#871189: marked as done (eclipse-egit: FTBFS: java.io.FileNotFoundException: /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/${eclipse.pdebuild.scripts}/genericTargets

[Debian Bug Tracking System]

Your message dated Mon, 05 Nov 2018 05:56:00 +
with message-id 
and subject line Bug#911308: Removed package(s) from unstable
has caused the Debian Bug report #871189,
regarding eclipse-egit: FTBFS: java.io.FileNotFoundException: 
/usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/${eclipse.pdebuild.scripts}/genericTargets.xml
 (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.)


-- 
871189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871189
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: eclipse-egit
Version: 3.7.0-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --with eclipse-helper
>dh_update_autotools_config
>dh_auto_configure
>dh_auto_build
>jh_setupenvironment
>jh_generateorbitdir
>jh_compilefeatures
> mkdir -p /<>/debian/.eclipse-build/build
> mkdir -p /<>/debian/.eclipse-build/build/home
> mkdir -p /<>/debian/.eclipse-build/build/home/workspace
> Building feature = org.eclipse.egit.
> Symlinking SDK into /<>/debian/.eclipse-build/build/SDK 
> directory.
> /bin/sh /usr/lib/eclipse/buildscripts/copy-platform 
> /<>/debian/.eclipse-build/build/SDK /usr/lib/eclipse
> ls: cannot access '/usr/lib/eclipse/dropins/jdt/plugins/*': No such file or 
> directory
> ls: cannot access '/usr/lib/eclipse/dropins/jdt/features/*': No such file or 
> directory
> ln: failed to create symbolic link 'icon.xpm': File exists
> ln: failed to create symbolic link 'notice.html': File exists
> ln: failed to create symbolic link 'readme': File exists
> ln: failed to create symbolic link 'swt-gtk-3.8.1.jar': File exists
> ln: failed to create symbolic link 'swt-gtk.jar': File exists
> ln: failed to create symbolic link 'swt.jar': File exists
> Starting build:
> Buildfile: 
> /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/build.xml
> 
> main:
> 
> preBuild:
>  [copy] Copying 1 file to /<>/debian/.eclipse-build/build
> 
> preSetup:
> 
> getMapFiles:
> 
> postSetup:
> 
> processRepos:
> 
> fetch:
> 
> generate:
> 
> preGenerate:
>  [exec] preparing files in /<>/debian/.eclipse-build for 
> buildfile generation ...
>  [exec]   making the 'features' and 'plugins' directories
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.eclipse.egit.mylyn 
> -> /<>/debian/.eclipse-build/org.eclipse.egit.mylyn-feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.eclipse.egit.source 
> -> /<>/debian/.eclipse-build/org.eclipse.egit.source-feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.eclipse.egit -> 
> /<>/debian/.eclipse-build/org.eclipse.egit-feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/plugins/org.eclipse.egit.core.test
>  -> /<>/debian/.eclipse-build/org.eclipse.egit.core.test/
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/plugins/org.eclipse.egit.core -> 
> /<>/debian/.eclipse-build/org.eclipse.egit.core/
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/plugins/org.eclipse.egit.doc -> 
> /<>/debian/.eclipse-build/org.eclipse.egit.doc/
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/plugins/org.eclipse.egit.mylyn.ui.test
>  -> /<>/debian/.eclipse-build/org.eclipse.egit.mylyn.ui.test/
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/plugins/org.eclipse.egit.mylyn.ui
>  -> /<>/debian/.eclipse-build/org.eclipse.egit.mylyn.ui/
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/plugins/org.eclipse.egit.target 
> -> /<>/debian/.eclipse-build/org.eclipse.egit.target/
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/plugins/org.eclipse.egit.ui.test 
> -> /<>/debian/.eclipse-build/org.eclipse.egit.ui.test/
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/plugins/org.eclipse.egit.ui -> 
> /<>/debian/.eclipse-build/org.eclipse.egit.ui/
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/plugins/org.eclipse.egit -> 
> /<>/debian/.eclipse-build/org.eclipse.egit/
>  [exec] done
> 
> symlinkDeps:
> [apply] Applied ln to 4 files and 0 directories.
> 
> allElements:
> 
> BUILD FAILED
> /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/build.xml:35:
>  The following error 

Bug#871193: marked as done (eclipse-linuxtools: FTBFS: java.io.FileNotFoundException: /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/${eclipse.pdebuild.scripts}/genericT

[Debian Bug Tracking System]

Your message dated Mon, 05 Nov 2018 05:56:58 +
with message-id 
and subject line Bug#911314: Removed package(s) from unstable
has caused the Debian Bug report #871193,
regarding eclipse-linuxtools: FTBFS: java.io.FileNotFoundException: 
/usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/${eclipse.pdebuild.scripts}/genericTargets.xml
 (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.)


-- 
871193: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871193
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: eclipse-linuxtools
Version: 3.1.0-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 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 '/<>'
> jh_compilefeatures --build-opts="-DjavacTarget=1.7 -DjavacSource=1.7 
> -DbuildId=dist -DforceContextQualifier=dist";
> jh_compilefeatures: Compatibility levels before 9 are deprecated (level 8 in 
> use)
> mkdir -p /<>/debian/.eclipse-build/build
> mkdir -p /<>/debian/.eclipse-build/build/home
> mkdir -p /<>/debian/.eclipse-build/build/home/workspace
> Building feature = org.eclipse.linuxtools.profiling.
> Symlinking SDK and "cdt cdt-autotools remote-services-api" into 
> /<>/debian/.eclipse-build/build/SDK directory.
> /bin/sh /usr/lib/eclipse/buildscripts/copy-platform 
> /<>/debian/.eclipse-build/build/SDK /usr/lib/eclipse cdt 
> cdt-autotools remote-services-api
> ls: cannot access '/usr/lib/eclipse/dropins/jdt/plugins/*': No such file or 
> directory
> ls: cannot access '/usr/lib/eclipse/dropins/jdt/features/*': No such file or 
> directory
> ln: failed to create symbolic link 'icon.xpm': File exists
> ln: failed to create symbolic link 'notice.html': File exists
> ln: failed to create symbolic link 'readme': File exists
> ln: failed to create symbolic link 'swt-gtk-3.8.1.jar': File exists
> ln: failed to create symbolic link 'swt-gtk.jar': File exists
> ln: failed to create symbolic link 'swt.jar': File exists
> Starting build:
> Buildfile: 
> /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/build.xml
> 
> main:
> 
> preBuild:
>  [copy] Copying 1 file to /<>/debian/.eclipse-build/build
> 
> preSetup:
> 
> getMapFiles:
> 
> postSetup:
> 
> processRepos:
> 
> fetch:
> 
> generate:
> 
> preGenerate:
>  [exec] preparing files in /<>/debian/.eclipse-build for 
> buildfile generation ...
>  [exec]   making the 'features' and 'plugins' directories
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.eclipse.linuxtools.changelog
>  -> 
> /<>/debian/.eclipse-build/org.eclipse.linuxtools.changelog-feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.eclipse.linuxtools.rpm
>  -> /<>/debian/.eclipse-build/org.eclipse.linuxtools.rpm-feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.eclipse.linuxtools.dataviewers.feature
>  -> 
> /<>/debian/.eclipse-build/org.eclipse.linuxtools.dataviewers-feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.eclipse.linuxtools.valgrind
>  -> 
> /<>/debian/.eclipse-build/org.eclipse.linuxtools.valgrind-feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.eclipse.linuxtools.perf.remote.feature
>  -> 
> /<>/debian/.eclipse-build/org.eclipse.linuxtools.perf.remote-feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.eclipse.linuxtools.profiling.remote
>  -> 
> /<>/debian/.eclipse-build/org.eclipse.linuxtools.profiling.remote-feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.eclipse.linuxtools.changelog.java
>  -> 
> /<>/debian/.eclipse-build/org.eclipse.linuxtools.changelog.java-feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.eclipse.linuxtools.perf.feature
>  -> /<>/debian/.eclipse-build/org.eclipse.linuxtools.perf-feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.eclipse.linuxtools.valgrind.remote
>  -> 
> /<>/debian/.eclipse-build/org.eclipse.linuxtools.valgrind.remote-feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.eclipse.linuxtools.changelog.c
>  -> 
> /<>/debian/.eclipse-build/org.eclipse.linuxtools.changelog.c-feature
>  [exec]   making symlink: 
> 

Bug#874727: OSG changing VRML renderer away from coin3

[Sebastiaan Couwenberg]

On 11/5/18 12:45 AM, Manuel A. Fernandez Montecelo wrote:
> 2018-11-04 18:28 Christoph Berg:
>> Re: To markus 2018-10-05 <20181005080326.gb13...@msg.df7cb.de>
>>> > 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.
>>
>> There is some indirect progress on this, Sebastiaan Couwenberg has
>> submitted patches to change OSG's VRML renderer to SGI Inventor:
>>
>> | Patches for both OSG packages have been submitted to use SGI Inventor
>> | instead of COIN:
>> |
>> |  https://bugs.debian.org/912866 (openscenegraph)
>> |  https://bugs.debian.org/912867 (openscenegraph-3.4)
> 
> I am not totally opposed to that, and thanks to Bas for the patches.
> But it looks to me that the proper solution is something like what
> Bernhard posted just minutes before this message that I am replying to
> (that perhaps Christoph didn't notice, due to the timing):
> 
>  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874727#96

Yes, the proper solution is to fix coin3. The OSG patches are meant as
an interim solution to remove the coin3 dependency from the OSG packages
and remove the threat of testing autoremoval.

OSG will also need to be patched to support the CMake builds of coin3,
so more work is needed to get OSG to work with the fixed coin3.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#912097: marked as done (yapps2: missing build dependencies on python-setuptools and python3-setuptools)

[Debian Bug Tracking System]

Your message dated Mon, 05 Nov 2018 06:49:38 +
with message-id 
and subject line Bug#912097: fixed in yapps2 2.2.1-2
has caused the Debian Bug report #912097,
regarding yapps2: missing build dependencies on python-setuptools and 
python3-setuptools
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.)


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

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

...
dh clean --with python2,python3 --buildsystem=pybuild
   dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:217: python2.7 setup.py clean 
Traceback (most recent call last):
  File "setup.py", line 3, in 
from setuptools import setup
ImportError: No module named setuptools
E: pybuild pybuild:338: clean: plugin distutils failed with: exit code=1: 
python2.7 setup.py clean 
dh_auto_clean: pybuild --clean -i python{version} -p 2.7 returned exit code 13
make: *** [debian/rules:6: clean] Error 25
--- End Message ---
--- Begin Message ---
Source: yapps2
Source-Version: 2.2.1-2

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

Debian distribution maintenance software
pp.
Matthias Urlichs  (supplier of updated yapps2 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, 05 Nov 2018 07:26:11 +0100
Source: yapps2
Binary: yapps2 python-yapps python3-yapps
Architecture: source all
Version: 2.2.1-2
Distribution: unstable
Urgency: medium
Maintainer: Matthias Urlichs 
Changed-By: Matthias Urlichs 
Description:
 python-yapps - Yet Another Python Parser System
 python3-yapps - Yet Another Python Parser System
 yapps2 - Yet Another Python Parser System
Closes: 912097
Changes:
 yapps2 (2.2.1-2) unstable; urgency=medium
 .
   * Add setuptools dependencies (closes: #912097).
Checksums-Sha1:
 a67271fac69242dfc759b3438e78792b0e044632 1854 yapps2_2.2.1-2.dsc
 48706337d0bcb4a81abfec28574b966b722e9c1c 26670 yapps2_2.2.1-2.diff.gz
 fa1805198fe98739f806afb2184fa37c8ce8f0b3 18784 python-yapps_2.2.1-2_all.deb
 85c2350d474615a2374a547d29f236ff816cec54 18836 python3-yapps_2.2.1-2_all.deb
 75231656d1d8733f1a3f90bc8278ed3636dcfddd 44032 yapps2_2.2.1-2_all.deb
 2e8996762c28fa4f699654c910aeaace17ceb603 9745 yapps2_2.2.1-2_amd64.buildinfo
Checksums-Sha256:
 1f79040dcbe3c2b88aab49ef74f5dafc00ecb9d9f6f52c3bcc43c9e41d73c831 1854 
yapps2_2.2.1-2.dsc
 c206ef11e2d35b4ff714fa834087b945aff83fd4f6d39532355f21a99c009609 26670 
yapps2_2.2.1-2.diff.gz
 b8a55b2e7ec9f405a503643f0973917893d3c692810b4d2cab4e77d71bb0b500 18784 
python-yapps_2.2.1-2_all.deb
 51f2e0cd6fcfbb34b704cd1cfd8c392a27e8d1a00d820f17dd0b4c9abb69bd46 18836 
python3-yapps_2.2.1-2_all.deb
 e95e7d45b68eb6b3c38e0b8a906b89e55d0e00f5d55406ee502bcbd2a8bd934a 44032 
yapps2_2.2.1-2_all.deb
 a965fc0db82b2884663f562631037d465d191cff1c0a206a1dd9c00f96257f92 9745 
yapps2_2.2.1-2_amd64.buildinfo
Files:
 73424bac7b2ce3afb6d57158d4b7d1a9 1854 python optional yapps2_2.2.1-2.dsc
 58c3e1258d94081ab267ee0b4e2ac454 26670 python optional yapps2_2.2.1-2.diff.gz
 a6ce5921411c834ea61349027ae1594e 18784 python optional 
python-yapps_2.2.1-2_all.deb
 5c279a356ea9e83de76c762d18eb0e9d 18836 python optional 
python3-yapps_2.2.1-2_all.deb
 c2e36a4274205b000859f409f6a259a3 44032 python optional yapps2_2.2.1-2_all.deb
 71e1d3c88723d2d09f7d2069cf138b8d 9745 python optional 
yapps2_2.2.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEr9eXgvO67AILKKGfcs+OXiW0wpMFAlvf47YACgkQcs+OXiW0
wpOuDQ/5AdncfZ3i/lym6b0wAxIq/OJtIy4D/t8T3mj3ofEocLuUsZX6g9JQzpFq
gjMPlqGcaIcD6cLKqjELyjQNmYuhIEOSidkFuWwMi1oBr2Kyqj5SIpHombzzmEbC
xNII2pVwtPjA8pR54sPY/addZpeoqvARdJy4S4J3jUWRNnJzU18d7JAZl0+qc1WH
9G6+oaYuZpftmEdSPLX7mieaf6kzEGb1CPCEBnreDoH7fowzRlWRXvvyWks8ATOs
SkilkDsQ7x6WTElHmRuYVCL0Zwi51ihIn22H1ti65BTJlw9kETfSo9zlTzC9vK0a
1+BjHJgGluDo1X5wL3gQBjYw0zsQRKspuoHFNQFempgIr8Z0odXX4cR5ONguhBF6
J+c60ZK6a/AkEprvSbk0ZU4E3qc4EF7ZZ5qiiIC7m8O+isetF4dLtfV86RdTTyyA

Processed: fixed 912116 in 0.6.0.6+ds-1

[Debian Bug Tracking System]

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

> fixed 912116 0.6.0.6+ds-1
Bug #912116 {Done: Kay Hayen } [src:nuitka] nuitka FTBFS: 
test failures
Marked as fixed in versions nuitka/0.6.0.6+ds-1.
> thanks
Stopping processing here.

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

Processed: fixed 912848 in 1:10.1.37-1

[Debian Bug Tracking System]

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

> fixed 912848 1:10.1.37-1
Bug #912848 [src:mariadb-10.1] mariadb-10.1: CVE-2018-3282 CVE-2018-3174 
CVE-2018-3143 CVE-2018-3156 CVE-2018-3251
Marked as fixed in versions mariadb-10.1/1:10.1.37-1.
> thanks
Stopping processing here.

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

Bug#867780: marked as done (eclipse-subclipse: Subclipse not properly integrated into Eclipse)

[Debian Bug Tracking System]

Your message dated Mon, 05 Nov 2018 06:00:50 +
with message-id 
and subject line Bug#911349: Removed package(s) from unstable
has caused the Debian Bug report #867780,
regarding eclipse-subclipse: Subclipse not properly integrated into Eclipse
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.)


-- 
867780: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867780
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: eclipse-subclipse
Version: 1.10.3-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I installed this package which brought in all the necessary dependencies
(libsvn-java, libsvnclientadapter-java). Despite 1.10.12-1 of
libsvnclientadapter-java being installed I get this when running Eclipse:

Incompatible JavaHL library loaded.  1.8.x or later required.

I've added the -Djava.library.path entry as suggested in bug 730813, but still
get the note error.



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

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

Versions of packages eclipse-subclipse depends on:
ii  eclipse-platform  3.8.1-10
ii  libsvn-java   1.9.5-1
ii  libsvnclientadapter-java  1.10.12-1

eclipse-subclipse recommends no packages.

eclipse-subclipse suggests no packages.

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

Dear submitter,

as the package eclipse-subclipse 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/911349

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.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#871188: marked as done (eclipse-subclipse: FTBFS: java.io.FileNotFoundException: /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/${eclipse.pdebuild.scripts}/genericTa

[Debian Bug Tracking System]

Your message dated Mon, 05 Nov 2018 06:00:50 +
with message-id 
and subject line Bug#911349: Removed package(s) from unstable
has caused the Debian Bug report #871188,
regarding eclipse-subclipse: FTBFS: java.io.FileNotFoundException: 
/usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/${eclipse.pdebuild.scripts}/genericTargets.xml
 (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.)


-- 
871188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871188
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: eclipse-subclipse
Version: 1.10.3-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --with eclipse-helper
> dh: Compatibility levels before 9 are deprecated (level 8 in use)
>dh_update_autotools_config
>dh_auto_configure
> dh_auto_configure: Compatibility levels before 9 are deprecated (level 8 in 
> use)
>dh_auto_build
> dh_auto_build: Compatibility levels before 9 are deprecated (level 8 in use)
>jh_setupenvironment
> jh_setupenvironment: Compatibility levels before 9 are deprecated (level 8 in 
> use)
>jh_generateorbitdir
> jh_generateorbitdir: Compatibility levels before 9 are deprecated (level 8 in 
> use)
>jh_compilefeatures
> jh_compilefeatures: Compatibility levels before 9 are deprecated (level 8 in 
> use)
> mkdir -p /<>/debian/.eclipse-build/build
> mkdir -p /<>/debian/.eclipse-build/build/home
> mkdir -p /<>/debian/.eclipse-build/build/home/workspace
> Building feature = org.tigris.subversion.clientadapter.feature.
> Symlinking SDK into /<>/debian/.eclipse-build/build/SDK 
> directory.
> /bin/sh /usr/lib/eclipse/buildscripts/copy-platform 
> /<>/debian/.eclipse-build/build/SDK /usr/lib/eclipse
> ls: cannot access '/usr/lib/eclipse/dropins/jdt/plugins/*': No such file or 
> directory
> ls: cannot access '/usr/lib/eclipse/dropins/jdt/features/*': No such file or 
> directory
> ln: failed to create symbolic link 'icon.xpm': File exists
> ln: failed to create symbolic link 'notice.html': File exists
> ln: failed to create symbolic link 'readme': File exists
> ln: failed to create symbolic link 'swt-gtk-3.8.1.jar': File exists
> ln: failed to create symbolic link 'swt-gtk.jar': File exists
> ln: failed to create symbolic link 'swt.jar': File exists
> Starting build:
> Buildfile: 
> /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/build.xml
> 
> main:
> 
> preBuild:
>  [copy] Copying 1 file to /<>/debian/.eclipse-build/build
> 
> preSetup:
> 
> getMapFiles:
> 
> postSetup:
> 
> processRepos:
> 
> fetch:
> 
> generate:
> 
> preGenerate:
>  [exec] preparing files in /<>/debian/.eclipse-build for 
> buildfile generation ...
>  [exec]   making the 'features' and 'plugins' directories
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.tigris.subversion.subclipse.mylyn
>  -> 
> /<>/debian/.eclipse-build/org.tigris.subversion.subclipse.mylyn.feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.tigris.subversion.subclipse
>  -> 
> /<>/debian/.eclipse-build/org.tigris.subversion.subclipse.feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.tigris.subversion.clientadapter.svnkit.feature
>  -> 
> /<>/debian/.eclipse-build/org.tigris.subversion.clientadapter.svnkit.feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.tigris.subversion.clientadapter.javahl.feature
>  -> 
> /<>/debian/.eclipse-build/org.tigris.subversion.clientadapter.javahl.feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.tigris.subversion.subclipse.graph.feature
>  -> 
> /<>/debian/.eclipse-build/org.tigris.subversion.subclipse.graph.feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.tigris.subversion.clientadapter.feature
>  -> 
> /<>/debian/.eclipse-build/org.tigris.subversion.clientadapter.feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/plugins/org.tigris.subversion.clientadapter.javahl.win32
>  -> 
> /<>/debian/.eclipse-build/org.tigris.subversion.clientadapter.javahl.win32/
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/plugins/org.tigris.subversion.clientadapter.javahl.win64
>  [exec]  -> 
> 

Bug#879123: marked as done (glee: source for configure is missing)

[Debian Bug Tracking System]

Your message dated Mon, 05 Nov 2018 06:02:26 +
with message-id 
and subject line Bug#911520: Removed package(s) from unstable
has caused the Debian Bug report #879123,
regarding glee: source for configure 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.)


-- 
879123: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879123
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glee
Version: 5.4.0-2
Severity: serious
Justification: missing source

The configure file claims that it was generated using autoconf. Yet the
corresponding source configure.in or configure.ac is missing from the
source package. This makes the package unsuitable for main in principle.

Fortunately, the packaging does not appear to be using configure. So
repacking the tarball and removing configure looks like a viable option.

Helmut
--- End Message ---
--- Begin Message ---
Version: 5.4.0-2+rm

Dear submitter,

as the package glee 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/911520

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.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#871359: marked as done (eclipse-wtp: FTBFS: debian/emfRegenerate.xml:18: Problem: failed to create task or type emf.Ecore2Java)

[Debian Bug Tracking System]

Your message dated Mon, 05 Nov 2018 06:01:15 +
with message-id 
and subject line Bug#911350: Removed package(s) from unstable
has caused the Debian Bug report #871359,
regarding eclipse-wtp: FTBFS: debian/emfRegenerate.xml:18: Problem: failed to 
create task or type emf.Ecore2Java
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.)


-- 
871359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871359
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: eclipse-wtp
Version: 3.6.3-3
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170807 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 '/<>'
> # Regenerate classes from EMF models
> /usr/lib/eclipse/eclipse \
>   -application org.eclipse.ant.core.antRunner  \
>   -configuration debian/.eclipse-build/.platform/configuration \
>   -buildfile debian/emfRegenerate.xml  \
>   -data debian/.eclipse-build  \
>   -Dosgi.sharedConfiguration.area=debian/.eclipse-build/build/home \
>   -consoleLog -noSplash
> OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support 
> was removed in 8.0
> Buildfile: debian/emfRegenerate.xml
> 
> default:
> 
> BUILD FAILED
> /<>/debian/emfRegenerate.xml:18: Problem: failed to create task 
> or type emf.Ecore2Java
> Cause: The name is undefined.
> Action: Check the spelling.
> Action: Check that any custom tasks/types have been declared.
> Action: Check that any / declarations have taken place.
> 
> 
> Total time: 0 seconds
> !SESSION 2017-08-07 11:18:05.703 
> ---
> eclipse.buildId=debbuild
> java.version=1.8.0_141
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments:  -application org.eclipse.ant.core.antRunner -buildfile 
> debian/emfRegenerate.xml 
> -Dosgi.sharedConfiguration.area=debian/.eclipse-build/build/home
> Command-line arguments:  -os linux -ws gtk -arch x86_64 -application 
> org.eclipse.ant.core.antRunner -buildfile debian/emfRegenerate.xml -data 
> debian/.eclipse-build 
> -Dosgi.sharedConfiguration.area=debian/.eclipse-build/build/home -consoleLog
> 
> !ENTRY org.eclipse.osgi 2 0 2017-08-07 11:18:09.276
> !MESSAGE One or more bundles are not resolved because the following root 
> constraints are not resolved:
> !SUBENTRY 1 org.eclipse.osgi 2 0 2017-08-07 11:18:09.277
> !MESSAGE Bundle 
> reference:file:plugins/org.eclipse.ecf.provider.filetransfer.httpclient_4.0.200.dist.jar
>  was not resolved.
> !SUBENTRY 2 org.eclipse.ecf.provider.filetransfer.httpclient 2 0 2017-08-07 
> 11:18:09.277
> !MESSAGE Missing imported package 
> org.apache.commons.httpclient.auth_[3.0.1,3.1.0].
> !SUBENTRY 2 org.eclipse.ecf.provider.filetransfer.httpclient 2 0 2017-08-07 
> 11:18:09.277
> !MESSAGE Missing imported package 
> org.apache.commons.httpclient.protocol_[3.0.1,3.1.0].
> !SUBENTRY 2 org.eclipse.ecf.provider.filetransfer.httpclient 2 0 2017-08-07 
> 11:18:09.277
> !MESSAGE Missing imported package 
> org.apache.commons.httpclient.methods_[3.0.1,3.1.0].
> !SUBENTRY 2 org.eclipse.ecf.provider.filetransfer.httpclient 2 0 2017-08-07 
> 11:18:09.277
> !MESSAGE Missing imported package org.apache.commons.httpclient_[3.0.1,3.1.0].
> !SUBENTRY 2 org.eclipse.ecf.provider.filetransfer.httpclient 2 0 2017-08-07 
> 11:18:09.277
> !MESSAGE Missing imported package 
> org.apache.commons.httpclient.params_[3.0.1,3.1.0].
> !SUBENTRY 2 org.eclipse.ecf.provider.filetransfer.httpclient 2 0 2017-08-07 
> 11:18:09.277
> !MESSAGE Missing imported package 
> org.apache.commons.httpclient.util_[3.0.1,3.1.0].
> !SUBENTRY 1 org.eclipse.osgi 2 0 2017-08-07 11:18:09.277
> !MESSAGE Bundle 
> reference:file:plugins/org.eclipse.ecf.provider.filetransfer.httpclient.ssl_1.0.0.dist.jar
>  was not resolved.
> !SUBENTRY 2 org.eclipse.ecf.provider.filetransfer.httpclient.ssl 2 0 
> 2017-08-07 11:18:09.278
> !MESSAGE Missing required capability Require-Capability: osgi.ee; 
> filter="(|(&(osgi.ee=CDC/Foundation)(version=1.1))(&(osgi.ee=JavaSE)(version=1.4)))".
> 
> !ENTRY org.eclipse.osgi 2 0 2017-08-07 11:18:09.283
> !MESSAGE The following is a complete list of bundles which are not resolved, 
> see the prior log entry for the root cause if it exists:
> !SUBENTRY 1 org.eclipse.osgi 2 0 

Bug#912373: marked as done (libswingx1-java: FTBFS with Java 11 due to ambiguous Collection.toArray() method)

[Debian Bug Tracking System]

Your message dated Mon, 05 Nov 2018 06:03:18 +
with message-id 
and subject line Bug#911679: Removed package(s) from unstable
has caused the Debian Bug report #912373,
regarding libswingx1-java: FTBFS with Java 11 due to ambiguous 
Collection.toArray() method
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.)


-- 
912373: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912373
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libswingx1-java
Version: 1:1.0-1
Severity: serious
Tags: ftbfs buster sid

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

...
compile:
[mkdir] Created dir: 
/build/1st/libswingx1-java-1.0/swingx-core/build/generated-sources
[javac] /usr/share/maven-ant-helper/maven-build.xml:357: warning: 
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to 
false for repeatable builds
[javac] Using javac -source 1.5 is no longer supported, switching to 6
[javac] Using javac -target 1.5 is no longer supported, switching to 6
[javac] Compiling 396 source files to 
/build/1st/libswingx1-java-1.0/swingx-core/build/classes
[javac] 
/build/1st/libswingx1-java-1.0/src/java/org/jdesktop/swingx/error/ErrorSupport.java:71:
 error: reference to toArray is ambiguous
[javac] return listeners.toArray(null);
[javac] ^
[javac]   both method toArray(IntFunction) in Collection and 
method toArray(T#2[]) in List match
[javac]   where T#1,T#2 are type-variables:
[javac] T#1 extends Object declared in method 
toArray(IntFunction)
[javac] T#2 extends Object declared in method toArray(T#2[])
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
[javac] 1 error

BUILD FAILED
/build/1st/libswingx1-java-1.0/debian/build.xml:37: The following error 
occurred while executing this line:
/build/1st/libswingx1-java-1.0/debian/build.xml:21: The following error 
occurred while executing this line:
/usr/share/maven-ant-helper/maven-build.xml:357: Compile failed; see the 
compiler error output for details.

Total time: 8 seconds
make: *** [/usr/share/cdbs/1/class/ant.mk:39: debian/stamp-ant-build] Error 1
--- End Message ---
--- Begin Message ---
Version: 1:1.0-1+rm

Dear submitter,

as the package libswingx1-java 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/911679

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.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#869221: marked as done (eclipse-xsd FTBFS: Problem: failed to create task or type emf.Ecore2Java)

[Debian Bug Tracking System]

Your message dated Mon, 05 Nov 2018 06:01:41 +
with message-id 
and subject line Bug#911351: Removed package(s) from unstable
has caused the Debian Bug report #869221,
regarding eclipse-xsd FTBFS: Problem: failed to create task or type 
emf.Ecore2Java
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.)


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

Some recent change in unstable makes eclipse-xsd FTBFS:

https://tests.reproducible-builds.org/debian/history/eclipse-xsd.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/eclipse-xsd.html

...
# Regenerate java code from ecore model
/usr/lib/eclipse/eclipse \
-application org.eclipse.ant.core.antRunner  \
-configuration debian/.eclipse-build/.platform/configuration \
-buildfile debian/ecoreToJava.xml\
-data debian/.eclipse-build/plugins  \
-Dosgi.sharedConfiguration.area=debian/.eclipse-build/build/home \
-consoleLog -noSplash
OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was 
removed in 8.0
Buildfile: debian/ecoreToJava.xml

ecore.regenerate:

BUILD FAILED
/build/1st/eclipse-xsd-2.9.0/debian/ecoreToJava.xml:22: The following error 
occurred while executing this line:
/build/1st/eclipse-xsd-2.9.0/debian/ecoreToJava.xml:18: Problem: failed to 
create task or type emf.Ecore2Java
Cause: The name is undefined.
Action: Check the spelling.
Action: Check that any custom tasks/types have been declared.
Action: Check that any / declarations have taken place.


Total time: 0 seconds
!SESSION 2017-07-19 18:15:08.522 ---
eclipse.buildId=debbuild
java.version=1.8.0_131
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Framework arguments:  -application org.eclipse.ant.core.antRunner -buildfile 
debian/ecoreToJava.xml 
-Dosgi.sharedConfiguration.area=debian/.eclipse-build/build/home
Command-line arguments:  -os linux -ws gtk -arch x86_64 -application 
org.eclipse.ant.core.antRunner -buildfile debian/ecoreToJava.xml -data 
debian/.eclipse-build/plugins 
-Dosgi.sharedConfiguration.area=debian/.eclipse-build/build/home -consoleLog

!ENTRY org.eclipse.osgi 2 0 2017-07-19 18:15:16.580
!MESSAGE One or more bundles are not resolved because the following root 
constraints are not resolved:
!SUBENTRY 1 org.eclipse.osgi 2 0 2017-07-19 18:15:16.581
!MESSAGE Bundle 
reference:file:plugins/org.eclipse.ecf.provider.filetransfer.httpclient_4.0.200.dist.jar
 was not resolved.
!SUBENTRY 2 org.eclipse.ecf.provider.filetransfer.httpclient 2 0 2017-07-19 
18:15:16.581
!MESSAGE Missing imported package 
org.apache.commons.httpclient.protocol_[3.0.1,3.1.0].
!SUBENTRY 2 org.eclipse.ecf.provider.filetransfer.httpclient 2 0 2017-07-19 
18:15:16.582
!MESSAGE Missing imported package 
org.apache.commons.httpclient.methods_[3.0.1,3.1.0].
!SUBENTRY 2 org.eclipse.ecf.provider.filetransfer.httpclient 2 0 2017-07-19 
18:15:16.583
!MESSAGE Missing imported package 
org.apache.commons.httpclient.util_[3.0.1,3.1.0].
!SUBENTRY 2 org.eclipse.ecf.provider.filetransfer.httpclient 2 0 2017-07-19 
18:15:16.583
!MESSAGE Missing imported package org.apache.commons.httpclient_[3.0.1,3.1.0].
!SUBENTRY 2 org.eclipse.ecf.provider.filetransfer.httpclient 2 0 2017-07-19 
18:15:16.584
!MESSAGE Missing imported package 
org.apache.commons.httpclient.auth_[3.0.1,3.1.0].
!SUBENTRY 2 org.eclipse.ecf.provider.filetransfer.httpclient 2 0 2017-07-19 
18:15:16.585
!MESSAGE Missing imported package 
org.apache.commons.httpclient.params_[3.0.1,3.1.0].
!SUBENTRY 1 org.eclipse.osgi 2 0 2017-07-19 18:15:16.586
!MESSAGE Bundle 
reference:file:plugins/org.eclipse.ecf.provider.filetransfer.httpclient.ssl_1.0.0.dist.jar
 was not resolved.
!SUBENTRY 2 org.eclipse.ecf.provider.filetransfer.httpclient.ssl 2 0 2017-07-19 
18:15:16.586
!MESSAGE Missing required capability Require-Capability: osgi.ee; 
filter="(|(&(osgi.ee=CDC/Foundation)(version=1.1))(&(osgi.ee=JavaSE)(version=1.4)))".

!ENTRY org.eclipse.osgi 2 0 2017-07-19 18:15:16.604
!MESSAGE The following is a complete list of bundles which are not resolved, 
see the prior log entry for the root cause if it exists:
!SUBENTRY 1 org.eclipse.osgi 2 0 2017-07-19 18:15:16.604
!MESSAGE Bundle 

Bug#879905: marked as done (glee: source for GLee.c and GLee.h is missing)

[Debian Bug Tracking System]

Your message dated Mon, 05 Nov 2018 06:02:26 +
with message-id 
and subject line Bug#911520: Removed package(s) from unstable
has caused the Debian Bug report #879905,
regarding glee: source for GLee.c and GLee.h 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.)


-- 
879905: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879905
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glee
Severity: serious
Justification: missing source (GLeeGen), missing source (GL ext specs)

GLee already has serious bug #879123, and the auto-removal email
for dependencies was sent this morning. Most of the discussion in
#879123 looks as if a .dsfg tarball would just need to remove the
configure file, I'm logging a new bug so that this doesn't get
missed:

On Thu, 19 Oct 2017 22:47:00, Ximin Luo wrote:
> Unfortunately we have a bigger problem:
>
> - rwxrwxr-x   1,105,245   GLee.c
> - rwxrwxr-x   955,258 GLee.h
>
> * [This file was automatically generated by GLeeGen 7.0
>
> These files are clearly not source code. But luckily it should
> be possible to regenerate them from the git repo I mentioned:
>
> > [..] https://github.com/kallisti5/glee

It seems that repo is also not the complete source, the build
steps in CMakeLists.txt download specs for the GL extensions from
http://www.opengl.org/registry/

The Readme.txt mentions a graball.bat, which no longer exists,
but seems likely to have grabbed from the same place.

Steve
--- End Message ---
--- Begin Message ---
Version: 5.4.0-2+rm

Dear submitter,

as the package glee 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/911520

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.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#911154: netkit-ntalk misses the generator for configure

[Christoph Biedl]

[
Cc'ing *all* affected packages. Noisy, but all parties involved
should be aware of the progress.
]

Helmut Grohne wrote...

> I'm not sure that adding our own confgen is maintainable in the long
> run. We already have very many build systems in Debian. We've learned
> the hard way that supporting many different build and packaging tools is
> expensive. Nowadays, most packages use debhelper and that kind of
> centralization bears benefits in modifiability. So I wonder whether
> outright replacing confgen usage (effectively reimplementing the build
> system for <= 15 packages) would be more maintainable in the long run.
> Most likely, that would make cross building just work. On the other
> hand, we'd have to extend the prospective confgen to support that use
> case.
>
> I'm suggesting that rewriting all those build systems using one of the
> standard tools (e.g. autotools, cmake, meson, maybe not qmake, ...)
> could mean less work.

Switching to e.g. cmake means a one-time more-or-less complex manual
transition but afterwards the packaging should be in a sane state for
quite some time.

After thinking about this for a few days I agree this is the sanest way
to go. For the current build system, there are already some extra
kludges (check out debian/rules if you really want to), and setting up a
confgen emulation, probably as a debhelper extension ... while this was
a faszinating project, it would certainly eat up some ressources to set
up and to maintain. Also, since confgen upstream (see below) described
the program as a hack and I subscribe to that point of view, it's
really better to look forward, even for these old packages.

Still I assume this will be my job - however, the changes will go
beyond a sound NMU size. So I'll send out patches, and eventually go
the package salvaging way.

For two packages, I did the migration already. Seems it's not very
difficult, but worth it¹. Most time was spent in identifying the
meaning of the 29 symbols found in the MCONFIG.in files. Second-biggest
task is learning cmake, but this has been on my agenda for some time
anyway :) Also, good news, old upstream answered my question *and*
provided a copy of confgen - which will help a lot trying to understand
the internals.

If someone more experienced in cmake wants to help, please get in
touch. Otherwise, allow me until end of November to create the fixes -
there is something called "real life" out there. Still my plan is to
salvage *all* packages. The expensive part is the thing called "setup
fee" somewhere else, and I'm mostly done with it.

Cheers,
Christoph

¹ For example for bsd-finger:

CMakeLists.txt:
| cmake_minimum_required (VERSION 3.7)
| project (bsd-finger)
|
| set(BIN_DIR "${CMAKE_INSTALL_PREFIX}/bin")
| set(MAN_DIR "${CMAKE_INSTALL_PREFIX}/share/man")
|
| add_subdirectory(finger)
| add_subdirectory(fingerd)

finger/CMakeLists.txt:
| file(GLOB SRCS "*.c")
| add_executable(
| finger
| ${SRCS}
| )
| install(
| TARGETS finger
| DESTINATION ${BIN_DIR}
| )
| install(
| FILES finger.1
| DESTINATION ${MAN_DIR}/man1/
| )

fingerd/CMakeLists.txt:
| file(GLOB SRCS "*.c")
| add_executable(
| in.fingerd
| ${SRCS}
| )
| install(
| TARGETS in.fingerd
| DESTINATION ${SBIN_DIR}
| )
| install(
| FILES fingerd.8
| DESTINATION ${MAN_DIR}/man8/
| RENAME in.fingerd.8
| )

debian/rules:
| #!/usr/bin/make -f
|
| %:
|   dh $@ --buildsystem=cmake

... and several more files in debian/ shortened or entirely removed.


signature.asc
Description: PGP signature

Bug#912116: marked as done (nuitka FTBFS: test failures)

[Debian Bug Tracking System]

Your message dated Mon, 5 Nov 2018 07:57:51 +0100
with message-id 

and subject line Closing bug manually
has caused the Debian Bug report #912116,
regarding nuitka FTBFS: test failures
to be marked as done.

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

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


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

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

...
--- /usr/bin/python3.7-dbg (stdout)
+++ nuitka (stdout)

@@ -18,7 +18,7 @@

 simpleFunction18: PASSED
 simpleFunction19: PASSED
 simpleFunction20: PASSED
-simpleFunction21: PASSED
+simpleFunction21: FAILED 125836 125872 leaked 36
 simpleFunction22: PASSED
 simpleFunction23: PASSED
 simpleFunction24: PASSED
@@ -35,8 +35,8 @@

 simpleFunction35: PASSED
 simpleFunction36: PASSED
 simpleFunction37: PASSED
-simpleFunction38: PASSED
-simpleFunction39: PASSED
+simpleFunction38: FAILED 126209 126239 leaked 30
+simpleFunction39: FAILED 126251 126252 leaked 1
 simpleFunction40: PASSED
 simpleFunction41: PASSED
 simpleFunction42: PASSED
@@ -67,8 +67,8 @@

 simpleFunction73: PASSED
 simpleFunction74: PASSED
 simpleFunction75: PASSED
-simpleFunction76: PASSED
-simpleFunction77: PASSED
+simpleFunction76: FAILED 126641 126642 leaked 1
+simpleFunction77: FAILED 126659 126660 leaked 1
 simpleFunction78: PASSED
 simpleFunction79: PASSED
 simpleFunction80: PASSED
Exit codes 0 (CPython) != 1 (Nuitka)
Error, outputs differed.
Error exit! 1
make[1]: *** [debian/rules:21: override_dh_auto_test] Error 1
--- End Message ---
--- Begin Message ---
Hello,

this has been fixed in the 0.6.0.6 upload recently done. Had to wait
for 3.7.1 to enter Debian.

Yours,
Kay--- End Message ---

Processed: limit source to fontconfig, tagging 877162, tagging 912699

[Debian Bug Tracking System]

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

> limit source fontconfig
Limiting to bugs with field 'source' containing at least one of 'fontconfig'
Limit currently set to 'source':'fontconfig'

> tags 877162 + pending
Bug #877162 [fontconfig-config] fontconfig-config: Configuration fails on 
upgrade from <2.12
Added tag(s) pending.
> tags 912699 + pending
Bug #912699 [fontconfig] fontconfig: FTBFS on hurd-i386
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#871196: marked as done (eclipse-rse: FTBFS: java.io.FileNotFoundException: /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/${eclipse.pdebuild.scripts}/genericTargets.

[Debian Bug Tracking System]

Your message dated Mon, 05 Nov 2018 06:00:15 +
with message-id 
and subject line Bug#911348: Removed package(s) from unstable
has caused the Debian Bug report #871196,
regarding eclipse-rse: FTBFS: java.io.FileNotFoundException: 
/usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/${eclipse.pdebuild.scripts}/genericTargets.xml
 (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.)


-- 
871196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871196
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: eclipse-rse
Version: 3.4.2-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 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 '/<>'
> jh_compilefeatures --build-opts '-DjavacTarget=1.5 -DjavacSource=1.5 
> -DgenerateFeatureVersionSuffix=true' --jvm-args 
> '-DJ2SE_1.5=/usr/lib/jvm/default-java/java/jre/lib/rt.jar'
> mkdir -p /<>/debian/.eclipse-build/build
> mkdir -p /<>/debian/.eclipse-build/build/home
> mkdir -p /<>/debian/.eclipse-build/build/home/workspace
> Building feature = org.eclipse.rse.
> Symlinking SDK into /<>/debian/.eclipse-build/build/SDK 
> directory.
> /bin/sh /usr/lib/eclipse/buildscripts/copy-platform 
> /<>/debian/.eclipse-build/build/SDK /usr/lib/eclipse
> ls: cannot access '/usr/lib/eclipse/dropins/jdt/plugins/*': No such file or 
> directory
> ls: cannot access '/usr/lib/eclipse/dropins/jdt/features/*': No such file or 
> directory
> ln: failed to create symbolic link 'icon.xpm': File exists
> ln: failed to create symbolic link 'notice.html': File exists
> ln: failed to create symbolic link 'readme': File exists
> ln: failed to create symbolic link 'swt-gtk-3.8.1.jar': File exists
> ln: failed to create symbolic link 'swt-gtk.jar': File exists
> ln: failed to create symbolic link 'swt.jar': File exists
> Starting build:
> Buildfile: 
> /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/build.xml
> 
> main:
> 
> preBuild:
>  [copy] Copying 1 file to /<>/debian/.eclipse-build/build
> 
> preSetup:
> 
> getMapFiles:
> 
> postSetup:
> 
> processRepos:
> 
> fetch:
> 
> generate:
> 
> preGenerate:
>  [exec] preparing files in /<>/debian/.eclipse-build for 
> buildfile generation ...
>  [exec]   making the 'features' and 'plugins' directories
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.eclipse.tm.terminal.serial
>  -> 
> /<>/debian/.eclipse-build/org.eclipse.tm.terminal.serial-feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.eclipse.tm.terminal.ssh
>  -> /<>/debian/.eclipse-build/org.eclipse.tm.terminal.ssh-feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.eclipse.rse.core -> 
> /<>/debian/.eclipse-build/org.eclipse.rse.core-feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.eclipse.rse.useractions
>  -> /<>/debian/.eclipse-build/org.eclipse.rse.useractions-feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.eclipse.tm.terminal 
> -> /<>/debian/.eclipse-build/org.eclipse.tm.terminal-feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.eclipse.rse.ssh -> 
> /<>/debian/.eclipse-build/org.eclipse.rse.ssh-feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.eclipse.rse -> 
> /<>/debian/.eclipse-build/org.eclipse.rse-feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.eclipse.rse.dstore 
> -> /<>/debian/.eclipse-build/org.eclipse.rse.dstore-feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.eclipse.rse.local 
> -> /<>/debian/.eclipse-build/org.eclipse.rse.local-feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.eclipse.rse.examples
>  -> /<>/debian/.eclipse-build/org.eclipse.rse.examples-feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.eclipse.tm.terminal.test
>  -> 
> /<>/debian/.eclipse-build/org.eclipse.tm.terminal.test-feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.eclipse.rse.tests 
> -> /<>/debian/.eclipse-build/org.eclipse.rse.tests-feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/org.eclipse.rse.scp -> 
> 

Bug#871209: marked as done (eclipse-anyedit: FTBFS: java.io.FileNotFoundException: /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/${eclipse.pdebuild.scripts}/genericTarg

[Debian Bug Tracking System]

Your message dated Mon, 05 Nov 2018 05:53:36 +
with message-id 
and subject line Bug#911304: Removed package(s) from unstable
has caused the Debian Bug report #871209,
regarding eclipse-anyedit: FTBFS: java.io.FileNotFoundException: 
/usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/${eclipse.pdebuild.scripts}/genericTargets.xml
 (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.)


-- 
871209: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871209
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: eclipse-anyedit
Version: 2.4.4-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 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 '/<>'
> jh_compilefeatures --build-opts="-DjavacTarget=1.5 -DjavacSource=1.5 
> -DbuildId=dist -DforceContextQualifier=dist"
> jh_compilefeatures: Compatibility levels before 9 are deprecated (level 8 in 
> use)
> mkdir -p /<>/debian/.eclipse-build/build
> mkdir -p /<>/debian/.eclipse-build/build/home
> mkdir -p /<>/debian/.eclipse-build/build/home/workspace
> Building feature = AnyEditTools.
> Symlinking SDK into /<>/debian/.eclipse-build/build/SDK 
> directory.
> /bin/sh /usr/lib/eclipse/buildscripts/copy-platform 
> /<>/debian/.eclipse-build/build/SDK /usr/lib/eclipse
> ls: cannot access '/usr/lib/eclipse/dropins/jdt/plugins/*': No such file or 
> directory
> ls: cannot access '/usr/lib/eclipse/dropins/jdt/features/*': No such file or 
> directory
> ln: failed to create symbolic link 'icon.xpm': File exists
> ln: failed to create symbolic link 'notice.html': File exists
> ln: failed to create symbolic link 'readme': File exists
> ln: failed to create symbolic link 'swt-gtk-3.8.1.jar': File exists
> ln: failed to create symbolic link 'swt-gtk.jar': File exists
> ln: failed to create symbolic link 'swt.jar': File exists
> Starting build:
> Buildfile: 
> /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/build.xml
> 
> main:
> 
> preBuild:
>  [copy] Copying 1 file to /<>/debian/.eclipse-build/build
> 
> preSetup:
> 
> getMapFiles:
> 
> postSetup:
> 
> processRepos:
> 
> fetch:
> 
> generate:
> 
> preGenerate:
>  [exec] preparing files in /<>/debian/.eclipse-build for 
> buildfile generation ...
>  [exec]   making the 'features' and 'plugins' directories
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/features/AnyEditTools -> 
> /<>/debian/.eclipse-build/AnyEditTools-feature
>  [exec]   making symlink: 
> /<>/debian/.eclipse-build/build/plugins/de.loskutov.anyedit.AnyEditTools
>  -> /<>/debian/.eclipse-build/AnyEditTools/
>  [exec] done
> 
> symlinkDeps:
> 
> allElements:
> 
> BUILD FAILED
> /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/build.xml:35:
>  The following error occurred while executing this line:
> /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/build.xml:91:
>  The following error occurred while executing this line:
> /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/templates/package-build/customTargets.xml:19:
>  The following error occurred while executing this line:
> java.io.FileNotFoundException: 
> /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/${eclipse.pdebuild.scripts}/genericTargets.xml
>  (No such file or directory)
>   at java.io.FileInputStream.open0(Native Method)
>   at java.io.FileInputStream.open(FileInputStream.java:195)
>   at java.io.FileInputStream.(FileInputStream.java:138)
>   at 
> org.apache.tools.ant.helper.ProjectHelper2.parse(ProjectHelper2.java:250)
>   at 
> org.apache.tools.ant.helper.ProjectHelper2.parse(ProjectHelper2.java:178)
>   at 
> org.apache.tools.ant.ProjectHelper.configureProject(ProjectHelper.java:93)
>   at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:392)
>   at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:293)
>   at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
>   at org.apache.tools.ant.Task.perform(Task.java:348)
>   at 

Bug#874849: marked as done ([cortina] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Sun, 04 Nov 2018 17:02:23 +
with message-id 
and subject line Bug#910599: Removed package(s) from unstable
has caused the Debian Bug report #874849,
regarding [cortina] Future Qt4 removal from 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.)


-- 
874849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874849
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cortina
Version: 1.1.1-1
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Version: 1.1.1-1+rm

Dear submitter,

as the package cortina 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/910599

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.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#852532: marked as done (olvwm: source code not 64-bit clean, SIGSEGV everywhere)

[Debian Bug Tracking System]

Your message dated Sun, 04 Nov 2018 17:16:39 +
with message-id 
and subject line Bug#911787: Removed package(s) from unstable
has caused the Debian Bug report #852532,
regarding olvwm: source code not 64-bit clean, SIGSEGV everywhere
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.)


-- 
852532: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852532
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: olvwm
Version: 4.4.3.2p1.4-28.2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

The latest version (4.4.3.2p1.4-28.2) immediately crashes with SIGSEGV
on my x86_64 system.  I tried building it from source with debug
symbols, and discovered that it is not 64-bit clean (examples below).

The previous version (4.4.3.2p1.4-28.1), which was built 4 years ago,
works.  It can no longer be built (because glibc no longer supports some
old APIs), but I'm guessing that the build tools from 4 years ago must
have produced machine code where all the addresses fall in the bottom
4GB of the virtual address space, so that the 64-bit uncleanliness is
hidden.

I'm not sure what to do about this.  Fixing all the source code is
likely to be a large project.  Is there a way to tell today's build
tools to produce machine code confined to the bottom 4GB of the virtual
address space?

Example SIGSEGVs:

In clients/olvwm-4.1/cursors.c in InitCursors() there is a gratuitous
cast of a pointer to an int before it is passed to a function that takes
a pointer:

st_insert(cursorTable, (int) p->name, (char *) p->num);

After I fixed that, there was SIGSEGV in image.c in this line:

b = (Button *) MemAlloc(sizeof(Button));

The problem is that mem.h is not included, so the compiler assumes that
MemAlloc() returns an int rather than a pointer, so the pointer gets
truncated to 32 bits.

After I fixed that, there was a SIGSEGV in states.c in this line:

cli->wmState = initstate;

but gdb said cli was optimized out, so I don't know what's going on
there.  I suspect that these 64-bit issues are pervasive.

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

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

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


-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'stable'), (600, 'unstable')
Architecture: amd64 (x86_64)

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

Versions of packages olvwm depends on:
ii  libc6 2.24-8
ii  libx11-6  2:1.6.4-2
ii  libxext6  2:1.3.3-1
ii  libxpm4   1:3.5.12-1

olvwm recommends no packages.

Versions of packages olvwm suggests:
pn  menu   
pn  olwm   
pn  xview-clients  

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 4.4.3.2p1.4-28.2+rm

Dear submitter,

as the package xview 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/911787

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.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Processed: severity of 912561 is serious

[Debian Bug Tracking System]

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

> severity 912561 serious
Bug #912561 [castxml] castxml FTBFS with llvm/clang 7
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: tagging 912561

[Debian Bug Tracking System]

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

> tags 912561 + ftbfs buster sid
Bug #912561 [castxml] castxml FTBFS with llvm/clang 7
Added tag(s) buster, ftbfs, and sid.
> thanks
Stopping processing here.

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

Bug#892738: marked as done (consolekit: consolekit removal causes a regression)

[Debian Bug Tracking System]

Your message dated Sun, 04 Nov 2018 17:15:24 +
with message-id 
and subject line Bug#911416: Removed package(s) from unstable
has caused the Debian Bug report #892738,
regarding consolekit: consolekit removal causes a regression
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.)


-- 
892738: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892738
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: consolekit
Version: 0.4.6-6
Severity: serious

Dear Maintainer,

please readd consolekit to the archive. Without consolekit the
dependency to libpam-systemd as alternative to consolekit forces me to
install systemd without any further benefit.

Since my systems works fine before (and till now, since consolekit
0.4.6-6 is installed) the removal of consolekit from the archive causes
a regression. As my understanding of init system dependencies this is a
serious bug, since it forces a dependency to a special system init
system without any need. So please readd consolekit to the archive.

Sincerly yours
Bene

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

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

Versions of packages consolekit depends on:
ii  dbus   1.12.6-2
ii  libacl12.2.52-3+b1
ii  libc6  2.27-1
ii  libck-connector0   0.4.6-6
ii  libdbus-1-31.12.6-2
ii  libdbus-glib-1-2   0.110-2
ii  libglib2.0-0   2.54.3-2
ii  libpolkit-gobject-1-0  0.105-18
ii  libudev1   237-4
ii  libx11-6   2:1.6.4-3
ii  zlib1g 1:1.2.8.dfsg-5

Versions of packages consolekit recommends:
pn  libpam-ck-connector  

consolekit suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.4.6-6.1+rm

Dear submitter,

as the package consolekit 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/911416

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.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#885040: marked as done (gconfmm2.6: Please don't release with buster)

[Debian Bug Tracking System]

Your message dated Sun, 04 Nov 2018 17:15:59 +
with message-id 
and subject line Bug#911566: Removed package(s) from unstable
has caused the Debian Bug report #885040,
regarding gconfmm2.6: Please don't release with 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.)


-- 
885040: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885040
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gconfmm2.6
Version: 2.28.3-1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs gconf gconfmm
Tags: sid buster

gconf's last release was about 5 years ago. It has been replaced by
dconf / gsettings. gconfmm is the C++ port of gconf.

gconfmm2.6 has only a handful of reverse dependencies with low
popularity. We shouldn't release gconfmm2.6 with Debian 10 "Buster".

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Version: 2.28.3-1+rm

Dear submitter,

as the package gconfmm2.6 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/911566

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.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#855168: marked as done (olvwm crashes traying to log in X)

[Debian Bug Tracking System]

Your message dated Sun, 04 Nov 2018 17:16:39 +
with message-id 
and subject line Bug#911787: Removed package(s) from unstable
has caused the Debian Bug report #855168,
regarding olvwm crashes traying to log in X
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.)


-- 
855168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855168
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: olvwm
Version: 4.4.3.2p1.4-28.2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Olvwm crashes trying to log in X, using startx or wdm. No trace of it in 
xsession-errors/Xorg logs.

I only found the following in /var/log/syslog and journalctl:

- syslog: kernel: [  151.441615] olvwm[1112]: segfault at 44c51dd0 ip 
55634411d3ed sp 7ffc19538b50 error 6 in olvwm[556344107000+62000]

- journalctl: kernel: olvwm[1112]: segfault at 44c51dd0 ip 55634411d3ed sp 
7ffc19538b50 error 6 in olvwm[556344107000+62000]

Note that I'm not an olwm user; no clue on how to debug it.

Cheers,

Awtul

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

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

Versions of packages olvwm depends on:
ii  libc6 2.24-9
ii  libx11-6  2:1.6.4-3
ii  libxext6  2:1.3.3-1
ii  libxpm4   1:3.5.12-1

olvwm recommends no packages.

Versions of packages olvwm suggests:
ii  menu   2.1.47
ii  olwm   3.2p1.4-28.2
pn  xview-clients  

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 4.4.3.2p1.4-28.2+rm

Dear submitter,

as the package xview 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/911787

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.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#855167: marked as done (olwm crashes trying to log in X)

[Debian Bug Tracking System]

Your message dated Sun, 04 Nov 2018 17:16:39 +
with message-id 
and subject line Bug#911787: Removed package(s) from unstable
has caused the Debian Bug report #855167,
regarding olwm crashes trying to log in X
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.)


-- 
855167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855167
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: olwm
Version: 3.2p1.4-28.2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Olwm crashes trying to log in X, using startx or wdm. No trace of it in 
xsession-errors/Xorg logs.

I only found the following in /var/log/syslog and journalctl:

- syslog: kernel: [ 1548.393919] olwm[7906]: segfault at 1fe16138 ip 
7f1e6f4234c7 sp 7fff3bf47f10 error 4 in 
libX11.so.6.3.0[7f1e6f394000+13a000]

- journalctl: kernel: olwm[983]: segfault at 82233138 ip 7f64327a84c7 sp 
7ffe9cd18a80 error 4 in libX11.so.6.3.0[7f6432719000+13a000]

Note that I'm not an olwm user; no clue on how to debug it.

Cheers,

Awtul



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

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

Versions of packages olwm depends on:
ii  libc6 2.24-9
ii  libx11-6  2:1.6.4-3
ii  libxext6  2:1.3.3-1
ii  xviewg3.2p1.4-28.2

olwm recommends no packages.

Versions of packages olwm suggests:
ii  menu   2.1.47
pn  xview-clients  

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 4.4.3.2p1.4-28.2+rm

Dear submitter,

as the package xview 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/911787

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.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#887648: marked as done (xview FTBFS with glibc 2.26)

[Debian Bug Tracking System]

Your message dated Sun, 04 Nov 2018 17:16:39 +
with message-id 
and subject line Bug#911787: Removed package(s) from unstable
has caused the Debian Bug report #887648,
regarding xview FTBFS with glibc 2.26
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.)


-- 
887648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887648
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xview
Version: 3.2p1.4-28.2
Severity: serious

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

...
filter.c: In function 'xv_free_filter_table':
filter.c:205:2: warning: implicit declaration of function 'cfree'; did you mean 
'free'? [-Wimplicit-function-declaration]
  cfree((char *) table[i]->call);
  ^
  free
...
gcc -o clock -g -O2 -fno-strict-aliasing 
-L/build/1st/xview-3.2p1.4/lib/libolgx -L/build/1st/xview-3.2p1.4/lib/libxview  
-L/usr/lib   clock.o -L/usr/lib -lxview -L/usr/lib -lolgx -lXext  -lX11-lm  
  
/build/1st/xview-3.2p1.4/lib/libxview/libxview.so: undefined reference to 
`cfree'
collect2: error: ld returned 1 exit status
Makefile:1178: recipe for target 'clock' failed
make[4]: *** [clock] Error 1
--- End Message ---
--- Begin Message ---
Version: 4.4.3.2p1.4-28.2+rm

Dear submitter,

as the package xview 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/911787

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.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#874727: OSG changing VRML renderer away from coin3

[Christoph Berg]

Re: To markus 2018-10-05 <20181005080326.gb13...@msg.df7cb.de>
> > 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.

There is some indirect progress on this, Sebastiaan Couwenberg has
submitted patches to change OSG's VRML renderer to SGI Inventor:

| Patches for both OSG packages have been submitted to use SGI Inventor
| instead of COIN:
|
|  https://bugs.debian.org/912866 (openscenegraph)
|  https://bugs.debian.org/912867 (openscenegraph-3.4)

Christoph

Bug#891103: marked as done (uicilibris: python-beautifulsoup is replaced with python-bs4)

[Debian Bug Tracking System]

Your message dated Sun, 04 Nov 2018 16:59:39 +
with message-id 
and subject line Bug#908949: Removed package(s) from unstable
has caused the Debian Bug report #891103,
regarding uicilibris: python-beautifulsoup is replaced with python-bs4
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.)


-- 
891103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891103
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: uicilibris
Version: uicilibris
Severity: important
Control: block 891087 by -1

beautifulsoup version 4 was replaced as a new package, bs4, which has
been in Debian for over 5 years now. beautfiulsoup (3.x) hasn't seen any
maintenance since then. It's high time to remove it from the archive.

Most code written against Beautiful Soup 3 will work against Beautiful
Soup 4 with one simple change. All you should have to do is change the
package name from BeautifulSoup to bs4, and depend on python-bs4 instead
of python-beautifulsoup.

There is some documentation on the migration here:
https://www.crummy.com/software/BeautifulSoup/bs4/doc/#porting-code-to-bs4

Thanks,

SR
--- End Message ---
--- Begin Message ---
Version: 1.13-1+rm

Dear submitter,

as the package uicilibris 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/908949

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.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#912684: marked as done (perl-modules-5.28 needs versioned Provides for modules it bundles)

[Debian Bug Tracking System]

Your message dated Sun, 4 Nov 2018 19:12:53 +0200
with message-id <20181104171253.GA18054@estella.local.invalid>
and subject line Re: Bug#912684: perl-modules-5.28 needs versioned Provides for 
modules it bundles
has caused the Debian Bug report #912684,
regarding perl-modules-5.28 needs versioned Provides for modules it bundles
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.)


-- 
912684: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912684
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: perl-modules-5.28
Version: 5.28.0-3
Severity: serious

perl-modules-5.28 has
  Replaces+Breaks: libextutils-parsexs-perl (<< 3.39)

This makes libextutils-parsexs-perl in unstable not installable.

libextutils-parsexs-perl does have reverse dependencies
in unstable, including revers dependencies with versioned
dependencies.

Versioned Provides for such modules are required.
--- End Message ---
--- Begin Message ---
On Sat, Nov 03, 2018 at 03:23:07AM +0100, gregor herrmann wrote:
> On Fri, 02 Nov 2018 22:03:43 +0200, Adrian Bunk wrote:

> > libextutils-parsexs-perl does have reverse dependencies
> > in unstable, including revers dependencies with versioned
> > dependencies.
> 
> I checked all reverse (build) dependencies and didn't see any
> problems; all of them are either unversioned or have the form "perl
> (>= 5.x) | libextutils-parsexs-perl [(>= 3.x]).
> So I think we have no actual problem here.

Indeed. This is standard practice and predates versioned Provides
support in dpkg and apt.

> > Versioned Provides for such modules are required.

Versioned Provides are not even in policy yet (tracked as #761219).
Not using them at this stage is certainly not a release critical bug.

> That's a long story:
> https://bugs.debian.org/758100

Right. We do want to move to using versioned Provides at some point,
as it would simplify things. Not sure if that will happen for buster or
bullseye yet.

Closing this.
-- 
Niko--- End Message ---

Bug#911363: marked as done (RM: patchelf [mips64el] -- ROM; ANAIS; Does not work)

[Debian Bug Tracking System]

Your message dated Sun, 04 Nov 2018 17:14:14 +
with message-id 
and subject line Bug#911363: Removed package(s) from unstable
has caused the Debian Bug report #911363,
regarding RM: patchelf [mips64el] -- ROM; ANAIS; Does not work
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.)


-- 
911363: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911363
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: patchelf
Version: 0.9+52.20180509-1
Severity: serious
Tags: ftbfs

Dear maintainer,

patchelf fails to build on the buildds [1] for mips64el, but previously did.
Please note that this impairs migration of your dependencies, so it
would be great if an solution can be found, or maybe temporarily remove
the mips64el packages to have at least the other release archs.

The failurse seems to be testsuite failures.

[1] https://buildd.debian.org/status/package.php?p=patchelf

Many thanks!

-- 
tobi



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

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

Versions of packages patchelf depends on:
ii  libc6   2.27-6
ii  libgcc1 1:8.2.0-7
ii  libstdc++6  8.2.0-7

patchelf recommends no packages.

patchelf suggests no packages.
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

  patchelf |  0.8-4 | mips64el

--- Reason ---
ROM; ANAIS; Does not work
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

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

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 911...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/911363

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.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#911877: marked as done (crossroads: CVE-2018-18654: package build vulnerable to insecure use of /tmp)

[Debian Bug Tracking System]

Your message dated Sun, 04 Nov 2018 17:17:07 +
with message-id 
and subject line Bug#911966: Removed package(s) from unstable
has caused the Debian Bug report #911877,
regarding crossroads: CVE-2018-18654: package build vulnerable to insecure use 
of /tmp
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.)


-- 
911877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911877
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: crossroads
Version: 2.81-2
Severity: serious
Tags: security

crossroads's xr/Makefile has:

| $(BINDIR)/xr: $(BIN)
|   cp $(BIN) $(TMPXR)
|   install $(TMPXR) $(BINDIR)/xr
|   rm -f $(TMPXR)

where

| TMPXR = /tmp/xr-$(shell whoami)

Jakub Wilk observed that a malicious user could create /tmp/xr-root as a
directory with mode 777 and replace the directory with an arbitrary file
after the cp (via inotify) thus injecting an arbitrary binary into the
build.

Helmut
--- End Message ---
--- Begin Message ---
Version: 2.81-2+rm

Dear submitter,

as the package crossroads 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/911966

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.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

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

[Debian Bug Tracking System]

Your message dated Sun, 04 Nov 2018 13:02:08 +
with message-id 
and subject line Bug#898940: fixed in lastpass-cli 1.0.0-1.2+deb9u1
has caused the Debian Bug report #898940,
regarding lastpass-cli: error: Peer certificate cannot be authenticated with 
given CA certificates
to be marked as done.

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

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


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

Hi,

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

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

FYI the CHANGELOG.md mentions:

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


Regards,

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

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

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

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

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated lastpass-cli package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 24 Oct 2018 10:40:01 -0400
Source: lastpass-cli
Binary: lastpass-cli
Architecture: source amd64
Version: 1.0.0-1.2+deb9u1
Distribution: stable
Urgency: medium
Maintainer: Troy Heber 
Changed-By: Chris Lamb 
Description:
 lastpass-cli - command line interface to LastPass.com
Closes: 898940
Changes:
 lastpass-cli (1.0.0-1.2+deb9u1) stable; urgency=medium
 .
   * Backport hardcoded certificate pins from lastpass-cli 1.3.1 to reflect
 changes in hosted Lastpass.com service. (Closes: #898940)
   * Add missing ca-certificates to Depends.
Checksums-Sha1:
 d275ae26713eaf8d80e08a7d68f73a662ffd0277 1851 lastpass-cli_1.0.0-1.2+deb9u1.dsc
 ea51c8d5574fa8a8c4804e3eed2fa2911e2afa63 6900 
lastpass-cli_1.0.0-1.2+deb9u1.debian.tar.xz
 5c2120626e310a3c8536a8d13869dadd8a39e273 213044 
lastpass-cli-dbgsym_1.0.0-1.2+deb9u1_amd64.deb
 f2d29654ba8b0b62520326326e89c78443420d94 7707 
lastpass-cli_1.0.0-1.2+deb9u1_amd64.buildinfo
 790882540530bf8a88a02e6440f2b3c58643532c 70502 
lastpass-cli_1.0.0-1.2+deb9u1_amd64.deb
Checksums-Sha256:
 254df83a392042244785203a8d7825dc5386414061cb6ee088cb25d7f7594952 1851 
lastpass-cli_1.0.0-1.2+deb9u1.dsc
 39f74287c398e0988079dc44ac1c6f8464ac2d43ec996420b8cbd47946ca89cb 6900 
lastpass-cli_1.0.0-1.2+deb9u1.debian.tar.xz
 ee2ea4ad9d19f31a8f7926ec4e88e65daf0a28e2b9a9fde0e4662f6cd24897eb 213044 
lastpass-cli-dbgsym_1.0.0-1.2+deb9u1_amd64.deb
 e8dbe06798a7a628392ca96ee1c7f0ba8220ff392161de0752c72ef050ea2f79 7707 
lastpass-cli_1.0.0-1.2+deb9u1_amd64.buildinfo
 1ff1f72301444baa4e261a5217687cda0ab314f24a1478949aea632ac395393f 70502 
lastpass-cli_1.0.0-1.2+deb9u1_amd64.deb
Files:
 ae37cce9a234161eef7f77f32dce6b1b 1851 utils optional 
lastpass-cli_1.0.0-1.2+deb9u1.dsc
 f1fa6325e4a89d0962b27b7c9fcb185a 6900 utils optional 
lastpass-cli_1.0.0-1.2+deb9u1.debian.tar.xz
 5dea65e1119af071a1c571abd5605dd7 213044 debug extra 
lastpass-cli-dbgsym_1.0.0-1.2+deb9u1_amd64.deb
 ecb93fc474d4d8e0a27c76aa90847f79 7707 utils optional 
lastpass-cli_1.0.0-1.2+deb9u1_amd64.buildinfo
 36e32883b21dabb2212ef59ea194e9df 70502 utils optional 
lastpass-cli_1.0.0-1.2+deb9u1_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEwv5L0nHBObhsUz5GHpU+J9QxHlgFAlve1sMACgkQHpU+J9Qx
HljQXA//bT8yiCK5OHRy+HKt7LOb2NwxV28uGj/58WDhnp62oeHTW+SHM1WUCoSH
/VNAn8JFBr50GKtnt2IuV+TyZja27Cnz2M4nSpDJDa9bpmDo7OnVynS7rR6t6BbK
vWIVPlawq3Dvn2n8sbxJ78kNYwnvaZSxFvWFy+ByrLv+7mGbAQuwJ3vTdDaePOba
6Fm9VdvPp2qD1KqC9ue+opCO/TSbvG+oHnxa7zNDJr7G+JXtklKkTFjUxP4WwP88

Processed: found 912848 in 1:10.1.35-1, found 912848 in 10.1.26-0+deb9u1

[Debian Bug Tracking System]

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

> found 912848 1:10.1.35-1
Bug #912848 [src:mariadb-10.1] mariadb-10.1: CVE-2018-3282 CVE-2018-3174 
CVE-2018-3143 CVE-2018-3156 CVE-2018-3251
Marked as found in versions mariadb-10.1/1:10.1.35-1.
> found 912848 10.1.26-0+deb9u1
Bug #912848 [src:mariadb-10.1] mariadb-10.1: CVE-2018-3282 CVE-2018-3174 
CVE-2018-3143 CVE-2018-3156 CVE-2018-3251
Marked as found in versions mariadb-10.1/10.1.26-0+deb9u1.
> thanks
Stopping processing here.

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

Bug#912617: libsdl2-image: CVE-2018-3977: do_layer_surface code execution vulnerability

[Manuel A. Fernandez Montecelo]

Hi Chris,

Em dom, 4 de nov de 2018 às 15:48, Chris Lamb  escreveu:
>
> Hi SDL maintainers & security team,
>
> > libsdl2-image: CVE-2018-3977: do_layer_surface code execution
> > vulnerability
>
> The attached patches apply cleanly to jessie, stretch and sid
> respectfully. (Looks like they reformatted their code later on.)
>
> I am happy to upload handle jessie, but I can also work on the
> stable/sid releases too if you wish; please let me know.

I am enjoying a kind of a "long weekend" / mini-holidays, could not
work on it so far and will not at least for another 3 or 4 days, and
since the rest of the team did not reply to the original report I
suppose that it's better that you go ahead unless they reply between
now and you reading this e-mail.

Thanks the several people involved in the work, both for the report
and patches and offer to fix!


Cheers.
-- 
Manuel A. Fernandez Montecelo 

Bug#912157: marked as done (kexi FTBFS with PostgreSQL 11)

[Debian Bug Tracking System]

Your message dated Sun, 04 Nov 2018 16:51:29 +
with message-id 
and subject line Bug#912157: fixed in kexi 1:3.1.0-4
has caused the Debian Bug report #912157,
regarding kexi FTBFS with PostgreSQL 11
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.)


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

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

...
-- Could NOT find PostgreSQL (missing: PostgreSQL_TYPE_INCLUDE_DIR) (found 
version "11.0")
...
   dh_install
dh_install: Cannot find (any matches for) 
"usr/lib/*/qt5/plugins/kexi/3.*/migrate/keximigrate_postgresql.so" (tried in ., 
debian/tmp)

dh_install: kexi-postgresql-driver missing files: 
usr/lib/*/qt5/plugins/kexi/3.*/migrate/keximigrate_postgresql.so
dh_install: missing files, aborting
make: *** [debian/rules:18: binary] Error 25
--- End Message ---
--- Begin Message ---
Source: kexi
Source-Version: 1:3.1.0-4

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

Debian distribution maintenance software
pp.
Pino Toscano  (supplier of updated kexi 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, 04 Nov 2018 17:14:23 +0100
Source: kexi
Binary: kexi kexi-data kexi-mysql-driver kexi-postgresql-driver 
kexi-web-form-widget
Architecture: source
Version: 1:3.1.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Pino Toscano 
Description:
 kexi   - visual database applications builder
 kexi-data  - data files for kexi
 kexi-mysql-driver - MySQL support for kexi
 kexi-postgresql-driver - PostgreSQL support for kexi
 kexi-web-form-widget - web form widget for Kexi
Closes: 912157
Changes:
 kexi (1:3.1.0-4) unstable; urgency=medium
 .
   * Backport upstream commit 54b2bcfb2ff1af6e7cbf7bdd60aef3d7c50b2785 to find
 PostgreSQL 11; patch upstream_cmake-find-PostgreSQL-11.patch.
 (Closes: #912157)
Checksums-Sha1:
 92201195d44fa5fc86766d9c78789519e1dd8d56 3036 kexi_3.1.0-4.dsc
 3cbdaa62bc4c005fab779fbff9a1b52fbb3d8816 8756 kexi_3.1.0-4.debian.tar.xz
 56fbfc13c7861b46fca753738c024dcd570b9dcd 21044 kexi_3.1.0-4_source.buildinfo
Checksums-Sha256:
 df81e8906a350617fb28b3df3ba032f048b9adb7affa8ab9bbcbb607a3e0e16b 3036 
kexi_3.1.0-4.dsc
 21ce6bd70054cf7910faef50930f2390c54e448c6a1e0f8b9dcc203da1363bad 8756 
kexi_3.1.0-4.debian.tar.xz
 d52e0503d3e958d50dcdeb6b044e31c11e5565277fb9287ed198eea943394878 21044 
kexi_3.1.0-4_source.buildinfo
Files:
 1764d98f2ce91cbb1f509067f300ebdc 3036 kde optional kexi_3.1.0-4.dsc
 e1a610b7a7ac45ce0917882d3c1fb99a 8756 kde optional kexi_3.1.0-4.debian.tar.xz
 60e210663f09449883e30fb25b56a072 21044 kde optional 
kexi_3.1.0-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEXyqfuC+mweEHcAcHLRkciEOxP00FAlvfGwkACgkQLRkciEOx
P02Jrg//RwifrGYCqU8GFBzNCHUf8zqD5Vy7Vv27qDwJDiA36pG9uIm2by8ENTTr
rYvd5byqmUEOAiR+IqSBNjnwWYlE5lx5RuGiunGi3a4RzAP1D4nRqRVpeWnTguHr
qztFkhRFP3Ikxvc4RFDSb0Ymf0dx2bK0E8DTggGrUbmICGVxSt3/G5qzVn0jXGZD
3hFCr5imEgGSQEHEAmrK6vKE0pKdHwpw7W8ttjiDkKHU8hsuUjpKO8Fax01GvWcs
+GNAANgjHvDDYyrEBspizCYoqNCjDnWKGn+ZFBcsA+23KaXEEZhEj2nR1nHnROYR
PdKvZXEnhEyRVX8eTvt6/bTH5M43LxTulqsr2H6xLMcZAJlBniT9UkW7iuKPKuCI
dTbWrMyOiBjHS96CGAJEqf4LazwndHMnoZGIsRnSYTY3Y6duyi7kBIz48np+ruSI
/uTozXOzJmdZAIhp2EzOcglZnE002bWW9u7BVzbitKOSGkVGH0wpRSmu8eNdMubs
BNSOgn9BxT2nRv2Z+gB2gRKEn6h+5L5U2azAaGZmtkYzqDv30uNvwuQgwlwPtTjS
UJZOzZupRIDvXpOztOvyPIW25TP5L6s5ZIagpD44a6v0GORtnZS5SlMfS6vnFYLP
lqvgJHgpfZsxQxQElxLZKHMkrdOHTk+XRsOxrFtb8RCEvhw1UJY=
=kOPt
-END PGP SIGNATURE End Message ---

Bug#817363: marked as done (asterisk-prompt-es: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Sun, 04 Nov 2018 17:10:26 +
with message-id 
and subject line Bug#911214: Removed package(s) from unstable
has caused the Debian Bug report #817363,
regarding asterisk-prompt-es: Removal of debhelper compat 4
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.)


-- 
817363: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817363
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: asterisk-prompt-es
Severity: important
Usertags: compat-4-removal

Hi,

The package asterisk-prompt-es uses debhelper with a compat level of 4,
which is deprecated and scheduled for removal.

 * Please bump the debhelper compat at your earliest convenience.
   on the 15th of June.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum
   - If the package has been relying on dh_install being lenient about
 missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * Compat level 4 will be removed on the first debhelper upload after
   the 15th of June.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Version: 1.4-1+rm

Dear submitter,

as the package asterisk-prompt-es 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/911214

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.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#885739: marked as done (gnome-color-chooser: Depends on libgnomeui)

[Debian Bug Tracking System]

Your message dated Sun, 04 Nov 2018 17:09:57 +
with message-id 
and subject line Bug#911196: Removed package(s) from unstable
has caused the Debian Bug report #885057,
regarding gnome-color-chooser: Depends on libgnomeui
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.)


-- 
885057: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885057
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-color-chooser
Version: 0.2.5-1.1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs libgnomeui
Tags: sid buster

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. These libraries have been
deprecated and unmaintained for several years.

Your package depends and or build-depends on libgnomeui.

Please port your package to GTK3 and related maintained libraries.
Otherwise, please consider requesting that your package be removed from
Debian to help us complete this goal.

[1] https://lists.debian.org/debian-devel/2017/10/msg00299.html

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Version: 0.2.5-1.1+rm

Dear submitter,

as the package gnome-color-chooser 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/911196

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.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#912695: apt-show-versions: breaks "apt-get update" and uninstallable after Perl 5.28 upgrade

[Salvatore Bonaccorso]

Hi

This is likely due to the perl upstream change around/with
https://perl5.git.perl.org/perl.git/commitdiff/c0e3b4b51cabf15ed8fc5f564dfeea31c25f5239
.

It can be workarounded by either setting higher limits for
recursion_limit/recursion_limit_hash or disable it with -1

$Storable::recursion_limit=-1;
$Storable::recursion_limit_hash=-1;

but I'm not sure this will be the right solution.

Regards,
Salvatore

Bug#885057: marked as done (gnome-color-chooser: Depends on old GNOME libraries)

[Debian Bug Tracking System]

Your message dated Sun, 04 Nov 2018 17:09:57 +
with message-id 
and subject line Bug#911196: Removed package(s) from unstable
has caused the Debian Bug report #885057,
regarding gnome-color-chooser: Depends on old GNOME libraries
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.)


-- 
885057: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885057
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-color-choser
Version: 0.2.5-1.1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs gconf libgnome libgnomeui libglade
Tags: sid buster

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. These libraries have been
deprecated and unmaintained for several years.

Your package depends and or build-depends on these libraries:

- libglademm-2.4-1v5 
- libgnomeui-0
- libgnome2-0

Please port your package to GTK3 and related maintained libraries.
Otherwise, please consider requesting that your package be removed from
Debian to help us complete this goal.

[1] https://lists.debian.org/debian-devel/2017/10/msg00299.html

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Version: 0.2.5-1.1+rm

Dear submitter,

as the package gnome-color-chooser 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/911196

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.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#857294: marked as done (asterisk-prompt-es: should be removed from the archive?)

[Debian Bug Tracking System]

Your message dated Sun, 04 Nov 2018 17:10:26 +
with message-id 
and subject line Bug#911214: Removed package(s) from unstable
has caused the Debian Bug report #857294,
regarding asterisk-prompt-es: should be removed from the archive?
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.)


-- 
857294: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857294
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: asterisk-prompt-es
Version: 1.4-1
Severity: serious

Dear maintainer,

asterisk-prompt-es is not seeing an upload since 2008.
Somehow it made all this way without any bug, but now it had a RC bug
filed one year ago, without a single reply from any maintainer.

There is an easy patch attached to fix that particular bug, but I wonder
if instead it would be wise to just remove it from the archive.

The very low popcon (22 installation, recent 0) also makes me propend to
this way.

Please reply, as one day I might come back and file the RM myself.

Thanks for maintaining asterisk-prompt-es so far.

-- 
regards,
Mattia Rizzolo

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


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

Dear submitter,

as the package asterisk-prompt-es 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/911214

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.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#909545: python-boto: diff for NMU version 2.44.0-1.1

[Sebastian Andrzej Siewior]

Control: tags 909545 + patch
Control: tags 909545 + pending


Dear maintainer,

I've prepared an NMU for python-boto (versioned as 2.44.0-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
Sebastian
diff -u python-boto-2.44.0/debian/changelog python-boto-2.44.0/debian/changelog
--- python-boto-2.44.0/debian/changelog
+++ python-boto-2.44.0/debian/changelog
@@ -1,3 +1,10 @@
+python-boto (2.44.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add SNI support. Thanks to Witold Baryluk for testing (Closes: #909545).
+
+ -- Sebastian Andrzej Siewior   Sun, 04 Nov 2018 12:37:23 +0100
+
 python-boto (2.44.0-1) unstable; urgency=medium
 
   * New upstream release.
only in patch2:
unchanged:
--- python-boto-2.44.0.orig/boto/connection.py
+++ python-boto-2.44.0/boto/connection.py
@@ -821,23 +821,24 @@
 h = http_client.HTTPConnection(host)
 
 if self.https_validate_certificates and HAVE_HTTPS_CONNECTION:
+context = ssl.create_default_context()
+context.verify_mode = ssl.CERT_REQUIRED
+context.check_hostname = True
+
 msg = "wrapping ssl socket for proxied connection; "
 if self.ca_certificates_file:
 msg += "CA certificate file=%s" % self.ca_certificates_file
+context.load_verify_locations(cafile=self.ca_certificates_file)
 else:
 msg += "using system provided SSL certs"
+context.load_default_certs()
 boto.log.debug(msg)
 key_file = self.http_connection_kwargs.get('key_file', None)
 cert_file = self.http_connection_kwargs.get('cert_file', None)
-sslSock = ssl.wrap_socket(sock, keyfile=key_file,
-  certfile=cert_file,
-  cert_reqs=ssl.CERT_REQUIRED,
-  ca_certs=self.ca_certificates_file)
-cert = sslSock.getpeercert()
-hostname = self.host.split(':', 0)[0]
-if not https_connection.ValidateCertificateHostname(cert, hostname):
-raise https_connection.InvalidCertificateException(
-hostname, cert, 'hostname mismatch')
+if key_file:
+context.load_cert_chain(certfile=cert_file, keyfile=key_file)
+
+sslSock = context.wrap_socket(sock, server_hostname=host)
 else:
 # Fallback for old Python without ssl.wrap_socket
 if hasattr(http_client, 'ssl'):
only in patch2:
unchanged:
--- python-boto-2.44.0.orig/boto/https_connection.py
+++ python-boto-2.44.0/boto/https_connection.py
@@ -119,20 +119,20 @@
 sock = socket.create_connection((self.host, self.port), self.timeout)
 else:
 sock = socket.create_connection((self.host, self.port))
+
+context = ssl.create_default_context()
+context.verify_mode = ssl.CERT_REQUIRED
+context.check_hostname = True
+if self.key_file:
+context.load_cert_chain(certfile=self.cert_file, keyfile=self.key_file)
+
 msg = "wrapping ssl socket; "
 if self.ca_certs:
 msg += "CA certificate file=%s" % self.ca_certs
+context.load_verify_locations(cafile=self.ca_certs)
 else:
 msg += "using system provided SSL certs"
+context.load_default_certs()
 boto.log.debug(msg)
-self.sock = ssl.wrap_socket(sock, keyfile=self.key_file,
-certfile=self.cert_file,
-cert_reqs=ssl.CERT_REQUIRED,
-ca_certs=self.ca_certs)
-cert = self.sock.getpeercert()
-hostname = self.host.split(':', 0)[0]
-if not ValidateCertificateHostname(cert, hostname):
-raise InvalidCertificateException(hostname,
-  cert,
-  'remote hostname "%s" does not match '
-  'certificate' % hostname)
+
+self.sock = context.wrap_socket(sock, server_hostname=self.host)
only in patch2:
unchanged:
--- python-boto-2.44.0.orig/debian/patches-for-reference/boto-try-to-add-SNI-support-v2.patch
+++ python-boto-2.44.0/debian/patches-for-reference/boto-try-to-add-SNI-support-v2.patch
@@ -0,0 +1,92 @@
+From: Sebastian Andrzej Siewior 
+Date: Sat, 29 Sep 2018 21:47:11 +0200
+Subject: [PATCH] boto: try to add SNI support
+
+Add SNI support. Newer OpenSSL (with TLS1.3) fail to connect if the
+hostname is missing.
+
+Link: https://bugs.debian.org/909545
+Tested-by: Witold Baryluk 
+Signed-off-by: Sebastian Andrzej Siewior 
+---
+ boto/connection.py   | 19 ++-
+ boto/https_connection.py | 22 +++---
+ 2 files changed, 21 insertions(+), 20 deletions(-)
+
+diff --git a/boto/connection.py 

Bug#912617: libsdl2-image: CVE-2018-3977: do_layer_surface code execution vulnerability

[Chris Lamb]

Hi SDL maintainers & security team,

> libsdl2-image: CVE-2018-3977: do_layer_surface code execution
> vulnerability

The attached patches apply cleanly to jessie, stretch and sid
respectfully. (Looks like they reformatted their code later on.)

I am happy to upload handle jessie, but I can also work on the
stable/sid releases too if you wish; please let me know.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- libsdl2-image-2.0.1+dfsg.orig/IMG_xcf.c
+++ libsdl2-image-2.0.1+dfsg/IMG_xcf.c
@@ -637,6 +637,9 @@ static int do_layer_surface (SDL_Surface
   p16 = (Uint16 *) p8;
   p   = (Uint32 *) p8;
   for (y=ty; y < ty+oy; y++) {
+if ((ty >= surface->h) || ((tx+ox) > surface->w)) {
+break;
+}
 row = (Uint32 *)((Uint8 *)surface->pixels + y*surface->pitch + tx*4);
 switch (hierarchy->bpp) {
 case 4:
--- libsdl2-image-2.0.3+dfsg1.orig/IMG_xcf.c
+++ libsdl2-image-2.0.3+dfsg1/IMG_xcf.c
@@ -638,6 +638,9 @@ do_layer_surface(SDL_Surface * surface,
 p16 = (Uint16 *) p8;
 p = (Uint32 *) p8;
 for (y = ty; y < ty + oy; y++) {
+if ((ty >= surface->h) || ((tx+ox) > surface->w)) {
+break;
+}
 row = (Uint32 *) ((Uint8 *) surface->pixels + y * surface->pitch + tx * 4);
 switch (hierarchy->bpp) {
 case 4:
--- libsdl2-image-2.0.0+dfsg.orig/IMG_xcf.c
+++ libsdl2-image-2.0.0+dfsg/IMG_xcf.c
@@ -637,6 +637,9 @@ static int do_layer_surface (SDL_Surface
   p16 = (Uint16 *) p8;
   p   = (Uint32 *) p8;
   for (y=ty; y < ty+oy; y++) {
+if ((ty >= surface->h) || ((tx+ox) > surface->w)) {
+break;
+}
 row = (Uint32 *)((Uint8 *)surface->pixels + y*surface->pitch + tx*4);
 switch (hierarchy->bpp) {
 case 4:

Bug#912737: [Pkg-openssl-devel] Bug#912737: openssl: SSL_read: error:1408F119:SSL routines:ssl3_get_record:decryption failed

[Julien Lecomte]

Hello

Thanks to your remark I tried connecting my computer directly to the 
set-top box.


Connected directly, the file downloads fine (verified via md5sum).
Connected indirectly, the download shows the issues I encountered.

The "indirect" route is desktop <-> ubiquiti unifi switch <-> ubiquiti 
unifi security gateway <-> set-top box.


I'll move the issue directly to ubiquiti to figure out what is going wrong.

Thanks
Julien



On 11/03/2018 11:45 AM, Kurt Roeckx wrote:

On Sat, Nov 03, 2018 at 11:12:37AM +0100, Julien Lecomte wrote:

Package: openssl
Version: 1.1.1-2
Severity: serious
Justification: makes unrelated software on the system (or the whole system) 
break

Dear Maintainer,

On a fresh install of Debian/Buster via the alpha3 dvd ISO, when I try to 
access some SSL URLs, openssl fails to download said resource.

~~~bash
julien@desktop:/tmp$ curl  
https://download.lenovo.com/pccbbs/mobiles/n1wuj23w.exe --output file
   % Total% Received % Xferd  Average Speed   TimeTime Time  Current
  Dload  Upload   Total   SpentLeft  Speed
   0 8169k0 278000 0   268k  0  0:00:30 --:--:--  0:00:30  268k
curl: (56) OpenSSL SSL_read: error:1408F119:SSL 
routines:ssl3_get_record:decryption failed or bad record mac, errno 0
~~~

URL above issues error "/tmp/mozilla_julien0/5wQP3KKa.bin.part could not be saved, 
because the source file could not be read." under firefox-esr.


It works for me.

Are you saying it gives an error both with firefox and curl? Then
it would be 2 different TLS implementaitons saying something is
wrong.

Does it work when you add --tls-max 1.2?

I suspect there is some middlebox that breaks things for you.


Kurt

Bug#912115: marked as done (kdb FTBFS with PostgreSQL 11)

[Debian Bug Tracking System]

Your message dated Sun, 04 Nov 2018 16:04:21 +
with message-id 
and subject line Bug#912115: fixed in kdb 3.1.0-4
has caused the Debian Bug report #912115,
regarding kdb FTBFS with PostgreSQL 11
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.)


-- 
912115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912115
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kdb
Version: 3.1.0-3
Severity: serious
Tags: ftbfs

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

...
-- The following features have been disabled:
...
 * BUILD_POSTGRESQL_DB_DRIVER, PostgreSQL database driver (because C API to 
PostgreSQL not found)
...
  dh_install
dh_install: Cannot find (any matches for) 
"usr/lib/*/qt5/plugins/kdb3/kdb_postgresqldriver.so" (tried in ., debian/tmp)

dh_install: libkdb3-driver-postgresql missing files: 
usr/lib/*/qt5/plugins/kdb3/kdb_postgresqldriver.so
dh_install: missing files, aborting
make: *** [debian/rules:6: binary] Error 25
--- End Message ---
--- Begin Message ---
Source: kdb
Source-Version: 3.1.0-4

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

Debian distribution maintenance software
pp.
Pino Toscano  (supplier of updated kdb 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, 04 Nov 2018 16:51:56 +0100
Source: kdb
Binary: libkdb3-4 libkdb-data libkdb3-dev libkdb3-driver-sqlite 
libkdb3-driver-mysql libkdb3-driver-postgresql
Architecture: source
Version: 3.1.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Pino Toscano 
Description:
 libkdb-data - data files for KDb
 libkdb3-4  - database connectivity and creation framework -- shared library
 libkdb3-dev - development files for KDb
 libkdb3-driver-mysql - MySQL driver for KDb
 libkdb3-driver-postgresql - PostgreSQL driver for KDb
 libkdb3-driver-sqlite - SQLite driver for KDb
Closes: 912115
Changes:
 kdb (3.1.0-4) unstable; urgency=medium
 .
   * Backport upstream commit 675d51d86b377992aacdb8253cb7c3b8a80474c0 to find
 PostgreSQL 11; patch upstream_cmake-find-PostgreSQL-11.patch.
 (Closes: #912115)
   * Update Vcs-* fields.
   * Bump Standards-Version to 4.2.1, no changes required.
   * Small update to the symbols file.
Checksums-Sha1:
 a6ae653c89582dc268c4f40e6bcb56774d9286a0 2505 kdb_3.1.0-4.dsc
 5d7c3e7e492f12c0738b58387ab1a6c89fc36673 18832 kdb_3.1.0-4.debian.tar.xz
 2d07036c4d82b25e852733300639aacbbc77ac17 12625 kdb_3.1.0-4_source.buildinfo
Checksums-Sha256:
 e7d03009402d6adb9d65ed6034dd0ca7ee00dd962a2e3c149895c0efeb30af13 2505 
kdb_3.1.0-4.dsc
 90db788db7c8cb96079053385da7e1d03c130db575eef3b251bbe19ba3d0 18832 
kdb_3.1.0-4.debian.tar.xz
 1b119b6b543a3d39234e44d113d7f3140b440e358018317e439a4f24d6ef2f29 12625 
kdb_3.1.0-4_source.buildinfo
Files:
 fc727af36fb5f8aa8dbb0e40e87630c3 2505 libs optional kdb_3.1.0-4.dsc
 327fec924fdc8c6342524b4c033cd3d2 18832 libs optional kdb_3.1.0-4.debian.tar.xz
 2f1c03680766783ffdec4bafb5e0c4b5 12625 libs optional 
kdb_3.1.0-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEXyqfuC+mweEHcAcHLRkciEOxP00FAlvfFeoACgkQLRkciEOx
P031Ww//eQ2MN9ibnj6ViGLxsmUKIIDPAodxZIuAVmK1sf+c0apv99FUKoRhjZl/
b0Z1X16/TkqMlYmjnPWHhnz1iYgFUP5YSG05Iyu5+7KG4Yqbsux4s4N2UjDXctv6
Dbbllo0vDL462Nm3FtcURl85WbQUqBRNxXMTTVNbA67cBOE4bzqIZmghzpi1v3nt
1KWJH68XIHCdZeM9hdQbGWFMfIQ6SmRDn3WiZmppnlX3+LRtOw1qZfiv0yq1LHFr
A4003dPC3m7t301+dozRaSYQGeZ0ldIEEc8i+bskfiFEWfecbRnIn31KJVkdDrVz
2NfXlVJ3UKm6zW1Ds27ptuBt6Ol3WC2WEgiBrrSnS03aCvSJYcTIbXm59EAUjxAE
0+s0xqGpT4vVevUG1d/SOYXAXO+HTfZQnMtdS1ybAXxNkCIroyzoilh3UIX99uH7
j/jjyQPeLYakz4X5OK2m75LTlVOg2PAr17N/Qr6uKTLosJmcGKLYWPLe6p9vHQ6u
FEAmeQd54GnyXY/2xXgnrLKOTT5DYWMaLi1gx71XgMkraEq5F3NWthtw+iVC65+r
+74l6Kni7nMYG/ZavC1vFV8GWYfjKR/i17PuE0fkO2doO47Sjh7k49iZllmBclZZ
Yl5AW8NpCBnFI9q+z9NXDDs8GduZRGneqXED1ocMKyu713HFIA0=
=ir+1
-END PGP SIGNATURE End Message ---

Bug#912617: libsdl2-image: CVE-2018-3977: do_layer_surface code execution vulnerability

[Chris Lamb]

Hi Manuel,

> I suppose that it's better that you go ahead unless they reply
> between now and you reading this e-mail.

Sure. From this I will go ahead and upload to sid. I've requested
access to the Salsa group so I can push my changes.

(I still await the Security Team on stable.)


Regards,

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

Bug#912847: marked as done (ghostscript ftbfs on amd64, not installable, breaking many binary-all builds)

[Debian Bug Tracking System]

Your message dated Sun, 04 Nov 2018 18:19:31 +
with message-id 
and subject line Bug#912847: fixed in ghostscript 9.25~dfsg-7
has caused the Debian Bug report #912847,
regarding ghostscript ftbfs on amd64, not installable, breaking many binary-all 
builds
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.)


-- 
912847: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912847
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ghostscript
Version: 9.25~dfsg-6
Severity: serious
Tags: sid buster

ghostscript ftbfs on amd64, not installable, breaking many binary-all builds

https://buildd.debian.org/status/fetch.php?pkg=ghostscript=amd64=9.25~dfsg-6=1541195477=0


make[4]: Entering directory '/<>'
make[4]: 'soobj/aux/genarch' is up to date.
make[4]: Leaving directory '/<>'
/usr/bin/make -f Makefile GS_DOT_O= REALMAIN_OBJ= GS_XE=./sobin/libgs.so.9.25
GPCL_XE=./sobin/libno_gpcl6.so.9.25 GXPS_XE=./sobin/libno_gxps.so.9.25
GPDL_XE=./sobin/libno_gpdl.so.9.25 DISPLAY_DEV=./soobj/display.dev
STDIO_IMPLEMENTATION=c BUILDDIRPREFIX=so GENOPT='' GS_LDFLAGS='-Wl,-z,relro
-shared -Wl,-soname=libgs.so.9'\
 PCL_LDFLAGS='-Wl,-z,relro   -shared -Wl,-soname=libno_gpcl6.so.9'
XPS_LDFLAGS='-Wl,-z,relro   -shared -Wl,-soname=libno_gxps.so.9' \
 PDL_LDFLAGS='-Wl,-z,relro   -shared -Wl,-soname=libno_gpdl.so.9'
CFLAGS='-fPIC  -O2 -fPIC \
 -Wdate-time -D_FORTIFY_SOURCE=2  -Wall -Wstrict-prototypes -Wundef
-Wmissing-declarations -Wmissing-prototypes -Wwrite-strings -fno-strict-aliasing
-Werror=declaration-after-statement -fno-builtin -fno-common -Werror=return-type
-DHAVE_STDINT_H=1 -DHAVE_DIRENT_H=1 -DHAVE_SYS_DIR_H=1 -DHAVE_SYS_TIME_H=1
-DHAVE_SYS_TIMES_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_LIBDL=1
-DGX_COLOR_INDEX_TYPE="unsigned long long" -D__USE_UNIX98=1  -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -DHAVE_RESTRICT=1 -DUSE_LIBPAPER
-I/usr/include/x86_64-linux-gnu  -fno-strict-aliasing -DHAVE_POPEN_PROTO=1
-DGS_DEVS_SHARED -DGS_DEVS_SHARED_DIR=\"/usr/lib/ghostscript/9.25\" ' 
prefix=/usr
make[4]: Entering directory '/<>'
make[4]: Leaving directory '/<>'
/usr/bin/make -f Makefile DISPLAY_DEV=./soobj/display.dev STDIO_IMPLEMENTATION=c
BUILDDIRPREFIX=so GENOPT='' LDFLAGS='-Wl,-z,relro  '\
 CFLAGS='-fPIC  -O2 -Wdate-time -D_FORTIFY_SOURCE=2  -Wall -Wstrict-prototypes
-Wundef -Wmissing-declarations -Wmissing-prototypes -Wwrite-strings
-fno-strict-aliasing -Werror=declaration-after-statement -fno-builtin
-fno-common -Werror=return-type -DHAVE_STDINT_H=1 -DHAVE_DIRENT_H=1
-DHAVE_SYS_DIR_H=1 -DHAVE_SYS_TIME_H=1 -DHAVE_SYS_TIMES_H=1 -DHAVE_INTTYPES_H=1
-DHAVE_LIBDL=1 -DGX_COLOR_INDEX_TYPE="unsigned long long" -D__USE_UNIX98=1  -g
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -DHAVE_RESTRICT=1 -DUSE_LIBPAPER
-I/usr/include/x86_64-linux-gnu  -fno-strict-aliasing -DHAVE_POPEN_PROTO=1
-DGS_DEVS_SHARED -DGS_DEVS_SHARED_DIR=\"/usr/lib/ghostscript/9.25\" ' 
prefix=/usr\
 ./sobin/gsc ./sobin/gsx -so-loader -so-loader -so-loader
make[4]: Entering directory '/<>'
/usr/bin/ld: ./soobj/dxmainc.o: file not recognized: file truncated
collect2: error: ld returned 1 exit status
make[4]: *** [base/unix-dll.mak:178: sobin/gsx] Error 1
make[4]: *** Waiting for unfinished jobs
make[4]: Leaving directory '/<>'
make[3]: *** [base/unix-dll.mak:296: so-subtarget] Error 2
make[3]: Leaving directory '/<>'
make[2]: *** [base/unix-dll.mak:301: install-so] Error 2
make[2]: Leaving directory '/<>'
make[1]: *** [base/unix-dll.mak:327: soinstall] Error 2
make[1]: Leaving directory '/<>'
make: *** [/usr/share/cdbs/1/class/makefile.mk:103:
debian/stamp-makefile-install] Error 2
dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2
--- End Message ---
--- Begin Message ---
Source: ghostscript
Source-Version: 9.25~dfsg-7

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated ghostscript 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 

Bug#911177: marked as done (dlm: does not trap errors from make)

[Debian Bug Tracking System]

Your message dated Sun, 04 Nov 2018 18:48:59 +
with message-id 
and subject line Bug#911177: fixed in dlm 4.0.7-3
has caused the Debian Bug report #911177,
regarding dlm: does not trap errors from make
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.)


-- 
911177: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911177
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dlm
Version: 4.0.7-2
Severity: serious
Justification: policy 4.6
Tags: upstream

The upstream Makefile runs submakes in a for loop without any error
trapping. Thus it continues building even in the presence of failures.
Doing so violates the Debian policy section 4.6. The recommended
solution is adding "set -e".

Helmut
--- End Message ---
--- Begin Message ---
Source: dlm
Source-Version: 4.0.7-3

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

Debian distribution maintenance software
pp.
Valentin Vidic  (supplier of updated dlm 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, 04 Nov 2018 19:01:58 +0100
Source: dlm
Binary: dlm-controld libdlm3 libdlm-dev libdlmcontrol3 libdlmcontrol-dev
Architecture: source
Version: 4.0.7-3
Distribution: unstable
Urgency: medium
Maintainer: Debian HA Maintainers 

Changed-By: Valentin Vidic 
Description:
 dlm-controld - Distributed Lock Manager control daemon
 libdlm-dev - Distributed Lock Manager library development
 libdlm3- Distributed Lock Manager library
 libdlmcontrol-dev - Distributed Lock Manager control library development
 libdlmcontrol3 - Distributed Lock Manager control library
Closes: 911177
Changes:
 dlm (4.0.7-3) unstable; urgency=medium
 .
   * [a517b75] Add patch for gcc warning
   * [7af1126] Add patch to fix Makefile exit code (Closes: #911177)
   * [ff4c1c8] Update my email address in Uploaders
   * [fb72494] Update Standards-Version to 4.2.1
   * [36e9ac4] Add missing Build-Depends-Package to libdlmcontrol3.symbols
Checksums-Sha1:
 9f4756bcebe9f2713a437999dedecbd6fe77d013 2344 dlm_4.0.7-3.dsc
 33635df99d3f2cbef0a87cc114a973cb1f0079f6 8184 dlm_4.0.7-3.debian.tar.xz
 9798f78a99df59ef3591352cbe200860533dabfb 7388 dlm_4.0.7-3_source.buildinfo
Checksums-Sha256:
 faa38c9d316b070c8ecc34f7ed34fa7afa7cd73e76841b753489e15ac7f8e2f2 2344 
dlm_4.0.7-3.dsc
 906ac7d922d38e257628f577d7fec9f5521928f8eef446da466365810970711e 8184 
dlm_4.0.7-3.debian.tar.xz
 189b3d435b0948efe5f0a4f4166ab287bfa5f4382234f8a49e8bd3b92017ae22 7388 
dlm_4.0.7-3_source.buildinfo
Files:
 b6a8a550dd3ba8001e7fd8a9e71dccd0 2344 admin optional dlm_4.0.7-3.dsc
 3ef6d6696699c9f33491225e055a364f 8184 admin optional dlm_4.0.7-3.debian.tar.xz
 a5bbb71288b2b234e0c146d7e64957a1 7388 admin optional 
dlm_4.0.7-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEExaW53cM9k/u2PWfIMofYmpfNqHsFAlvfPCcSHHZ2aWRpY0Bk
ZWJpYW4ub3JnAAoJEDKH2JqXzah7V68QAIYtuAQgRFYddgALpEBrCpm00CPAY+ct
BUCoA9bjGmcd0jMdS+hPJ7wvoNiXPF2OAHwlj4SllR3fKi1ZXFlJ6sijksCkQdAb
SnFP02z6yJRVO+xzjfe9IgJh9TYiPq+1XOF8sYQxGw5EN+BLJCyhvGlyoGgJWjjN
k28OPKZfliwX/OWjCy9qCDKIRrSKRVf4hw60CAfrjkMpX1vCcv5h7D22zh40BKTo
Vr6q3zZjxcjaWB6pblaM7asYH+SoECWQmRb58QcFQIO0ospSXp63TghRAg7NvxD5
BVDmHuX8G43CPS9F176roBU1RyWSsvvNi/RCO62D5Koo4SUenkpt1a1rMxY2IUFU
DcAXaU3UPYYkafl/TncFLt2slHqsvaFTtUKNfrkFszRlMZ5pmR59LaCMYtyiwHFm
syDpD02Gk/m4KY4QXxACYF60HjPkhfpkSscqH1T0/XJl+Pg0qAXVtoxB1fO7mYC1
lEW+oMRHOsOOwAyB/A/76YbpxalsgbYHyNRqChyNi6QlzsR6FXKgwchvyy/uOkqO
ejN0+sGjdEOrpJqHMStwcutol8Lrzgh4ojfE0FcX3tv3Nw6m+9vL15PXUgoPkrj/
btw3NqoHT+oaeD9W4tMyBBe24GTWoNjcbU0UUnU0v9wwOrUx1FUVrXeuDHaSdj3v
nGopJswyX4LR
=30Sb
-END PGP SIGNATURE End Message ---

Bug#912270: Bug #912270 in writer2latex marked as pending

[Rene Engelhard]

Control: tag -1 pending

Hello,

Bug #912270 in writer2latex 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/libreoffice-team/extensions/writer2latex/commit/e7299efb8127265fafd269d66626801de0b3bbae


  * build-depend on libjaxb-java and add jaxb-api.jar to main.class.path,
thanks Emmanuel Bourg for the hint (closes: #912270)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/912270

Processed: Bug #912270 in writer2latex marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #912270 [src:writer2latex] writer2latex: FTBFS with Java 11 due to JAXB 
removal
Added tag(s) pending.

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

Bug#911120: espeakup: Does not fully install

[Samuel Thibault]

Samuel Thibault, le ven. 02 nov. 2018 00:52:55 +0100, a ecrit:
> Alex ARNAUD, le jeu. 01 nov. 2018 20:27:23 +0100, a ecrit:
> > >  espeakup
> > > E: Sub-process /usr/bin/dpkg returned an error code (1)
> > 
> > Could it be possible to backport the fix to Stretch release?
> 
> Ah, right, the systemd service was already in Stretch, so we'd have to
> backport the fix, I have proposed this in #912629.

That got accepted, will be in 9.6 :)

Samuel

Bug#902459: marked as done (faumachine: FTBFS in buster/sid (error: 'faum_dsdt' undeclared))

[Debian Bug Tracking System]

Your message dated Sun, 04 Nov 2018 19:34:37 +
with message-id 
and subject line Bug#902459: fixed in faumachine 20180503-2
has caused the Debian Bug report #902459,
regarding faumachine: FTBFS in buster/sid (error: 'faum_dsdt' undeclared)
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.)


-- 
902459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:faumachine
Version: 20180503-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh_testdir
./autogen.sh
configure.ac:140: installing 'scripts/compile'
configure.ac:142: installing 'scripts/config.guess'
configure.ac:142: installing 'scripts/config.sub'
configure.ac:20: installing 'scripts/install-sh'
configure.ac:20: installing 'scripts/missing'
chips/Makefile.am: installing 'scripts/depcomp'
lib/Makefile.am:174: warning: source file 'pattern-matcher/patternm.c' is in a 
subdirectory,
lib/Makefile.am:174: but option 'subdir-objects' is disabled
automake: warning: possible forward-incompatibility.
automake: At least a source file is in a subdirectory, but the 'subdir-objects'

[... snipped ...]

../../scripts/gcc.pl "gcc -Wchar-subscripts -Wcomment -Wformat -Wnonnull 
-Wimplicit-int -Wimplicit-function-declaration -Wimplicit -Wmain 
-Wmissing-braces -Wparentheses -Wsequence-point -Wreturn-type -Wswitch 
-Wtrigraphs -Wunused-function -Wunused-label -Wunused-variable -Wunused-value 
-Wuninitialized -Wunknown-pragmas -Wundef -Wendif-labels -Wshadow 
-Wpointer-arith -Wcast-qual -Wcast-align -Wwrite-strings -Waggregate-return 
-Wstrict-prototypes -Wmissing-noreturn -Wnested-externs -Wunused-local-typedefs 
-Wredundant-decls -Wno-pointer-sign" -DHAVE_CONFIG_H -I. -I../..-DINIT_RM 
--sec-prefix=.init.rm -I../.. --freestanding -fno-pic -fno-PIC -fno-pie 
-fno-PIE  -fno-dse -fno-pie -no-pie -Os -fomit-frame-pointer 
-mpreferred-stack-boundary=2 --freestanding -falign-functions=15 
-I../mb_template_bios -I.. -I../../lib -DCONFIG_APM_SUPPORT 
-DCONFIG_MOUSE_SUPPORT -DCONFIG_PCI_SUPPORT -DCONFIG_PNP_SUPPORT 
-DCONFIG_SMI_SUPPORT -DCONFIG_SMP_SUPPORT -DCONFIG_ACPI_SUPPORT 
-DCONFIG_MB_GA_686DLX_SU
 PPORT -DCONFIG_INTEL_7180 -m32 -march=i386 -MT libinit_rm_a-print.o -MD -MP 
-MF .deps/libinit_rm_a-print.Tpo -c -o libinit_rm_a-print.o `test -f 
'../mb_template_bios/print.c' || echo './'`../mb_template_bios/print.c
mv -f .deps/libinit_rm_a-print.Tpo .deps/libinit_rm_a-print.Po
../../scripts/gcc.pl "gcc -Wchar-subscripts -Wcomment -Wformat -Wnonnull 
-Wimplicit-int -Wimplicit-function-declaration -Wimplicit -Wmain 
-Wmissing-braces -Wparentheses -Wsequence-point -Wreturn-type -Wswitch 
-Wtrigraphs -Wunused-function -Wunused-label -Wunused-variable -Wunused-value 
-Wuninitialized -Wunknown-pragmas -Wundef -Wendif-labels -Wshadow 
-Wpointer-arith -Wcast-qual -Wcast-align -Wwrite-strings -Waggregate-return 
-Wstrict-prototypes -Wmissing-noreturn -Wnested-externs -Wunused-local-typedefs 
-Wredundant-decls -Wno-pointer-sign" -DHAVE_CONFIG_H -I. -I../..-DINIT_RM 
--sec-prefix=.init.rm -I../.. --freestanding -fno-pic -fno-PIC -fno-pie 
-fno-PIE  -fno-dse -fno-pie -no-pie -Os -fomit-frame-pointer 
-mpreferred-stack-boundary=2 --freestanding -falign-functions=15 
-I../mb_template_bios -I.. -I../../lib -DCONFIG_APM_SUPPORT 
-DCONFIG_MOUSE_SUPPORT -DCONFIG_PCI_SUPPORT -DCONFIG_PNP_SUPPORT 
-DCONFIG_SMI_SUPPORT -DCONFIG_SMP_SUPPORT -DCONFIG_ACPI_SUPPORT 
-DCONFIG_MB_GA_686DLX_SU
 PPORT -DCONFIG_INTEL_7180 -m32 -march=i386 -MT libinit_rm_a-vsprintf.o -MD -MP 
-MF .deps/libinit_rm_a-vsprintf.Tpo -c -o libinit_rm_a-vsprintf.o `test -f 
'../mb_template_bios/vsprintf.c' || echo './'`../mb_template_bios/vsprintf.c
mv -f .deps/libinit_rm_a-vsprintf.Tpo .deps/libinit_rm_a-vsprintf.Po
../../scripts/gcc.pl "gcc -Wchar-subscripts -Wcomment -Wformat -Wnonnull 
-Wimplicit-int -Wimplicit-function-declaration -Wimplicit -Wmain 
-Wmissing-braces -Wparentheses -Wsequence-point -Wreturn-type -Wswitch 
-Wtrigraphs -Wunused-function -Wunused-label -Wunused-variable -Wunused-value 
-Wuninitialized -Wunknown-pragmas -Wundef -Wendif-labels -Wshadow 
-Wpointer-arith -Wcast-qual -Wcast-align -Wwrite-strings -Waggregate-return 
-Wstrict-prototypes -Wmissing-noreturn -Wnested-externs -Wunused-local-typedefs 
-Wredundant-decls -Wno-pointer-sign" -DHAVE_CONFIG_H -I. -I../..-DINIT_RM 
--sec-prefix=.init.rm -I../.. --freestanding 

Bug#912044: pbuilder config

[Thorsten Alteholz]

Hi Daniel,

thanks for your report. Can you please be a bit more verbose on how your 
pbuilder and chroot is configured? At the moment I am not able to 
reproduce the failure.


Thanks!
 Thorsten

Bug#912695: apt-show-versions: breaks "apt-get update" and uninstallable after Perl 5.28 upgrade

[Niko Tyni]

On Sun, Nov 04, 2018 at 06:09:36PM +0100, Salvatore Bonaccorso wrote:
 
> This is likely due to the perl upstream change around/with
> https://perl5.git.perl.org/perl.git/commitdiff/c0e3b4b51cabf15ed8fc5f564dfeea31c25f5239
> .
> 
> It can be workarounded by either setting higher limits for
> recursion_limit/recursion_limit_hash or disable it with -1
> 
> $Storable::recursion_limit=-1;
> $Storable::recursion_limit_hash=-1;
> 
> but I'm not sure this will be the right solution.

Thanks. I've filed #912900 about this on the Perl side. Christoph:
please use these workarounds at least for now. Apologies for the trouble.

Also, please let us know at p...@packages.debian.org when a workaround
is in Debian. We can then add dependency metadata on the perl side to
make sure apt-show-versions gets always upgraded before perl.

Longer term, I'm not sure Storable is the best tool for this (a cache
of apt list contents.) AFAICS you're reading the whole data structure
in memory even when you need just one entry? You might want to look at
the various Cache / CHI modules, or even just plain GDBM_File.
-- 
Niko Tyni   nt...@debian.org

Bug#912910: boost1.67: for loops without set -e

[Mattia Rizzolo]

Source: boost1.67
Version: 1.67.0-9
Severity: serious
Control: clone -1 -2 boost1.62 1.62.0+dfsg-10
Control: retitle -2 boost1.62: for loops without set -e
Justification: Policy §4.6


Hi boost maintainers,

I've noticed that your for loops in your rules files are buggy.
This things:

for pyver in $(pyversions); do \
echo "Building Boost.Python for python version $$pyver"; \
$(JAM) --build-dir=build-$$pyver --stagedir=stage-$$pyver 
--user-config=$(CURDIR)/user-config-$$pyver.jam --with-python --with-mpi 
python=$$pyver; \
done

is buggy, as it wouldn't cause a build failure in the instance $(JAM)
failed.

you should prepend `set -e` in your for loops, like this:

set -e ; for pyver in $(pyversions); do \ 

in *all* the loops.  Alternatively you could appropriatly set SHELL,
but I somewhat recommend against, as I tend to prefer explicit errors
checking in my makefiles.

To be honest, I'd actually recommend you don't use shell loops in
makefiles, but instead prefer the facilities provided by makefiles
itself, which would also provide you with an increased parallelism
during the execution.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Processed: fixed 906198 in 1.1.0-2

[Debian Bug Tracking System]

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

> fixed 906198 1.1.0-2
Bug #906198 [python-scipy] [python-scipy] causes FTBFS on of imexam: 
scipy.optimize.leastsq fails on S390x
Bug #910729 [python-scipy] imexan: FTBFS on s390x: test failures
Bug #910781 [python-scipy] imexam: FTBFS on s390x
Bug #912150 [python-scipy] imexam: FTBFS in s390x: AssertionError during tests
There is no source info for the package 'python-scipy' at version '1.1.0-2' 
with architecture ''
Unable to make a source version for version '1.1.0-2'
Marked as fixed in versions 1.1.0-2.
Marked as fixed in versions 1.1.0-2.
Marked as fixed in versions 1.1.0-2.
Marked as fixed in versions 1.1.0-2.
> outlook 906198 the issue is currently workarounded by using gfortran-7 on 
> s390x.  See #912150
Outlook recorded from message bug 906198 message 
Outlook recorded from message bug 906198 message 
Outlook recorded from message bug 906198 message 
Outlook recorded from message bug 906198 message 
> thanks
Stopping processing here.

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

Bug#912270: marked as done (writer2latex: FTBFS with Java 11 due to JAXB removal)

[Debian Bug Tracking System]

Your message dated Sun, 04 Nov 2018 19:07:38 +
with message-id 
and subject line Bug#912270: fixed in writer2latex 1.4-6
has caused the Debian Bug report #912270,
regarding writer2latex: FTBFS with Java 11 due to JAXB 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.)


-- 
912270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912270
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: writer2latex
Version: 1.4-5
Severity: serious
Tags: ftbfs

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

...
compile:
[mkdir] Created dir: /build/1st/writer2latex-1.4/target/classes
[javac] Compiling 203 source files to 
/build/1st/writer2latex-1.4/target/classes
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 6
[javac] warning: [options] source value 6 is obsolete and will be removed 
in a future release
[javac] warning: [options] target value 1.6 is obsolete and will be removed 
in a future release
[javac] warning: [options] To suppress warnings about obsolete options, use 
-Xlint:-options.
[javac] 
/build/1st/writer2latex-1.4/source/java/writer2latex/base/ImageConverter.java:37:
 error: package javax.xml.bind does not exist
[javac] import javax.xml.bind.DatatypeConverter;
[javac]  ^
[javac] 
/build/1st/writer2latex-1.4/source/java/writer2latex/base/ImageConverter.java:351:
 error: cannot find symbol
[javac] return DatatypeConverter.printHexBinary(md.digest(blob))
[javac]^
[javac]   symbol:   variable DatatypeConverter
[javac]   location: class ImageConverter
[javac] 
/build/1st/writer2latex-1.4/source/java/writer2latex/base/ImageConverter.java:352:
 error: cannot find symbol
[javac] 
+DatatypeConverter.printHexBinary(Arrays.copyOf(blob, 10));
[javac]  ^
[javac]   symbol:   variable DatatypeConverter
[javac]   location: class ImageConverter
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] 3 errors
[javac] 4 warnings

BUILD FAILED
/build/1st/writer2latex-1.4/build.xml:78: Compile failed; see the compiler 
error output for details.

Total time: 5 seconds
make: *** [debian/rules:37: build-indep-stamp] Error 1
--- End Message ---
--- Begin Message ---
Source: writer2latex
Source-Version: 1.4-6

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

Debian distribution maintenance software
pp.
Rene Engelhard  (supplier of updated writer2latex 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: Sun, 04 Nov 2018 18:47:00 +
Source: writer2latex
Binary: writer2latex writer2latex-manual libwriter2latex-java-doc 
libwriter2latex-java libreoffice-writer2latex libreoffice-writer2xhtml
Architecture: source
Version: 1.4-6
Distribution: unstable
Urgency: medium
Maintainer: Debian LibreOffice Maintainers 
Changed-By: Rene Engelhard 
Description:
 libreoffice-writer2latex - Writer/Calc to LaTeX converter extension for 
LibreOffice
 libreoffice-writer2xhtml - Writer/Calc to XHTML converter extension for 
LibreOffice
 libwriter2latex-java - OpenOffice.org Writer/Calc to LaTeX/XHTML converter -- 
library
 libwriter2latex-java-doc - OpenOffice.org Writer/Calc to LaTeX/XHTML converter 
-- javadoc
 writer2latex - OpenOffice.org Writer/Calc to LaTeX/XHTML converter
 writer2latex-manual - OpenOffice.org Writer/Calc to LaTeX/XHTML converter -- 
manual
Closes: 912270
Changes:
 writer2latex (1.4-6) unstable; urgency=medium
 .
   * build-depend on libjaxb-java and add jaxb-api.jar to main.class.path,
 thanks Emmanuel Bourg for the hint (closes: #912270)
   * remove code changes of no_JSON.diff and use libandroid-json-java
   * java2-runtime -> java6-runtime in Depends:...
Checksums-Sha1:
 c20f97e162693cb72fae536f2d31269d50498071 2603 writer2latex_1.4-6.dsc
 

Processed: tagging 903698

[Debian Bug Tracking System]

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

> tags 903698 - pending
Bug #903698 [dh-python] sphinxbase: build appears broken for multiple python3 
versions
Removed tag(s) pending.
> thanks
Stopping processing here.

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

Bug#912679: marked as done (libmagickcore-6.q16-dev missing Depends: libmagickcore-6-arch-config)

[Debian Bug Tracking System]

Your message dated Sun, 04 Nov 2018 20:43:51 +
with message-id 
and subject line Bug#912679: fixed in imagemagick 8:6.9.10.14+dfsg-6
has caused the Debian Bug report #912679,
regarding libmagickcore-6.q16-dev missing Depends: libmagickcore-6-arch-config
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.)


-- 
912679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912679
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libmagickcore-6.q16-dev
Version: 8:6.9.10.14+dfsg-5
Severity: serious
Justification: missing dependency
Control: affects -1 + src:gem

libmagickcore-6.q16-dev does not depend on libmagickcore-6-arch-config.
It does depend on libmagickcore-6-headers, which depends on
libmagickcore-6-arch-config, but libmagickcore-6-headers is Multi-Arch:
foreign. So you get some libmagickcore-6-arch-config and not necessarily
one with matching architecture. The dependency is too weak.

When building gem, this can become fatal:

| /bin/bash ../../libtool  --tag=CXX   --mode=compile aarch64-linux-gnu-g++ 
-DHAVE_CONFIG_H -I. -I../../src  -I../../src -Wdate-time -D_FORTIFY_SOURCE=2 
-DGEM_VERSION_CODENAME='""Debian/1:0.93.3-18""' -DPD -I/usr/include/pd -fopenmp 
-DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 -fopenmp 
-DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 -fopenmp 
-DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 
-I/usr/include/aarch64-linux-gnu//ImageMagick-6 -I/usr/include/ImageMagick-6 
-I/usr/include/aarch64-linux-gnu//ImageMagick-6 -I/usr/include/ImageMagick-6 
-I/usr/include/aarch64-linux-gnu//ImageMagick-6 -I/usr/include/ImageMagick-6  
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -freg-struct-return -O3 -falign-loops -falign-functions 
-falign-jumps -funroll-loops -ffast-math -c -o 
gem_imageMAGICK_la-imageMAGICK.lo `test -f 'imageMAGICK.cpp' || echo 
'./'`imageMAGICK.cpp
| libtool: compile:  aarch64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I../../src 
-I../../src -Wdate-time -D_FORTIFY_SOURCE=2 
-DGEM_VERSION_CODENAME=\"\"Debian/1:0.93.3-18\"\" -DPD -I/usr/include/pd 
-fopenmp -DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 -fopenmp 
-DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 -fopenmp 
-DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 
-I/usr/include/aarch64-linux-gnu//ImageMagick-6 -I/usr/include/ImageMagick-6 
-I/usr/include/aarch64-linux-gnu//ImageMagick-6 -I/usr/include/ImageMagick-6 
-I/usr/include/aarch64-linux-gnu//ImageMagick-6 -I/usr/include/ImageMagick-6 -g 
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -freg-struct-return -O3 -falign-loops -falign-functions 
-falign-jumps -funroll-loops -ffast-math -c imageMAGICK.cpp  -fPIC -DPIC -o 
.libs/gem_imageMAGICK_la-imageMAGICK.o
| In file included from /usr/include/ImageMagick-6/Magick++/Include.h:14,
|  from /usr/include/ImageMagick-6/Magick++.h:10,
|  from imageMAGICK.cpp:21:
| /usr/include/ImageMagick-6/magick/magick-config.h:21:10: fatal error: 
magick/magick-baseconfig.h: No such file or directory
|  #include "magick/magick-baseconfig.h"
|   ^~~~
| compilation terminated.
| make[3]: *** [Makefile:613: gem_imageMAGICK_la-imageMAGICK.lo] Error 1
| make[3]: Leaving directory '/<>/plugins/imageMAGICK'
| make[2]: *** [Makefile:489: all-recursive] Error 1
| make[2]: Leaving directory '/<>/plugins'
| make[1]: *** [Makefile:598: all-recursive] Error 1
| make[1]: Leaving directory '/<>'
| dh_auto_build: make -j1 returned exit code 2
| make: *** [debian/rules:82: binary-arch] Error 2
| dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2

The dependency from libmagickcore-6-headers on
libmagickcore-6-arch-config should be removed. It is always too week and
needs to be lifted to a higher level.

What can be done though is flipping the dependency. Have
libmagickcore-6-arch-config depend on libmagickcore-6-headers and then
replace any dependency on libmagickcore-6-headers with one on
libmagickcore-6-arch-config. That should be fine, because both packages
are considered implementation detail and do not have any reverse
dependencies outside imagemagick.

Helmut
--- End Message ---
--- Begin Message ---
Source: imagemagick
Source-Version: 8:6.9.10.14+dfsg-6

We believe that the bug you reported is fixed in the latest version of
imagemagick, 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 

Bug#902036: marked as done (pygame FTBFS on s390x, testsuite failure.)

[Debian Bug Tracking System]

Your message dated Sun, 04 Nov 2018 18:21:55 +
with message-id 
and subject line Bug#902036: fixed in pygame 1.9.4.post1+dfsg-2
has caused the Debian Bug report #902036,
regarding pygame FTBFS on s390x, testsuite failure.
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.)


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

Package: pygame
Severity: serious
Version: 1.9.3+dfsg2

The two most recent attempts to build pygame on s390x failed with the following 
error.



==
ERROR: test_write (pygame.tests.bufferproxy_test.BufferProxyLegacyTest)
--
Traceback (most recent call last):
  File 
"/<>/pygame-1.9.3+dfsg2/.pybuild/cpython2_2.7_pygame/build/pygame/tests/bufferproxy_test.py",
 line 469, in test_write
bp.write(data[:3], 2)
IndexError: 'offset' is out of range
--- End Message ---
--- Begin Message ---
Source: pygame
Source-Version: 1.9.4.post1+dfsg-2

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

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated pygame 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, 04 Nov 2018 18:48:21 +0100
Source: pygame
Binary: python-pygame python3-pygame python-pygame-doc
Architecture: source
Version: 1.9.4.post1+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Mattia Rizzolo 
Description:
 python-pygame - SDL bindings for games development (Python 2)
 python-pygame-doc - SDL bindings for games development in Python 
(documentation)
 python3-pygame - SDL bindings for games development (Python 3)
Closes: 902036
Changes:
 pygame (1.9.4.post1+dfsg-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Peter Michael Green ]
   * Fix a typo that breaks bufferproxy on 64-bit big endian.  Closes: #902036
Checksums-Sha1:
 45eb2b04f35e451673ec9280f69e8ac55351f50e 2774 pygame_1.9.4.post1+dfsg-2.dsc
 21772a071c4914fe6e96316f887d9015f75413b6 21972 
pygame_1.9.4.post1+dfsg-2.debian.tar.xz
 278deb1a2079aa3b3da8da8924372a8b026d2919 15672 
pygame_1.9.4.post1+dfsg-2_amd64.buildinfo
Checksums-Sha256:
 ec9f6bcc491fca6ff58c2bd312fcd72f1f63046d8696b81566fc6c52b7f94b2a 2774 
pygame_1.9.4.post1+dfsg-2.dsc
 6d279288c56dd39b71230e85d277d02b04449172bb2304c1cb5da6cb2d3bb935 21972 
pygame_1.9.4.post1+dfsg-2.debian.tar.xz
 f87eaa8074dc07851f85972f447e048f9b2cda2be3945a2237a2537861b56a5d 15672 
pygame_1.9.4.post1+dfsg-2_amd64.buildinfo
Files:
 224cb60612075d9f15cbcd44f5cd77d2 2774 python optional 
pygame_1.9.4.post1+dfsg-2.dsc
 aaa1bb5fbb5df82d1337d812fc4eddf9 21972 python optional 
pygame_1.9.4.post1+dfsg-2.debian.tar.xz
 c90bf043af5d3d4d8ee7f8e5bea8319e 15672 python optional 
pygame_1.9.4.post1+dfsg-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAlvfM+MACgkQCBa54Yx2
K60EPg/8DCHhRNAWGnqOY/CrGLsbOtsj/wrm/uQMKr9chLVdIgGICDk2PaU8TdD1
/9vcpkY1//S6/4CZLXYvzoHWbNnih0HHDjj4HC49WozIKBSnA/fprsfltwQI7FL2
GS+PMvCQBPbRcnveFSRigkanbp1MX4O47TX0uJIlQ0zfpR5ZFCdWI7bPtXei62ZV
SeU3aEzCdP4aRrNw6bEKpZD26NZf8tgTYBXQw2BpcImxejJAST+9dooqlsXzMGOG
oz1+s0lO1+lfK91OFusw0is0ZDZgYQCKOoFaNvgr6Ghtv0/8oTKyLvEGyMRN5Qrq
oBMfz5chaPRFK0XQB09uqQYpWIaMW36w8vyE8AEHqf3MxQ1UviZKFEl/x3gc8+/U
22Kr7/+wnN5hUBmxqPTZGPR3GBYGn+R+cadZh8+xPBpt3Wi+nkQenPOrO2FwWVVL
PJUCSsiYQjQKYTf0IF/mC7dNJwRMOaR3IPc2m4JjuQm20QPp3ilgCGLpxg6uPZ1z
nvNdeelcr5zK26Z2FZ3qxvVYj25JQYsm40BVz41SdsEey10mQe6+m+geEA0eKB7S
zWsymzBSVrX43/yZ0XY7v2ZcOfleM4Ht2tHUsfIPe6jCkmPLQQ8PmDXaM1TXiGCI
VO19KMcsriSLH+go+mYVV+FOuojYuJPp+Zw1sXVMW2FUwsY4Gso=
=8wl2
-END PGP SIGNATURE End Message ---

Bug#850438: marked as done (teckit: license problem with SFconv/ConvertUTF.[ch])

[Debian Bug Tracking System]

Your message dated Mon, 5 Nov 2018 10:03:48 +0700
with message-id 

and subject line SFconv/ConvertUTF.[ch] is not in teckit any more
has caused the Debian Bug report #850438,
regarding teckit: license problem with SFconv/ConvertUTF.[ch]
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.)


-- 
850438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850438
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: teckit
Version: 2.5.4~svn140+ds2-1
Severity: serious
Tags: upstream

Hello,

According to Lintian, there is a problem with this file, which is
licensed by Unicode:

Tag: license-problem-convert-utf-code
Severity: serious
Certainty: possible
Info: The following file source files include material under a
 non-free license from Unicode Inc. Therefore, it is
 not possible to ship this in main or contrib.
 .
 This license does not grant any permission
 to modify the files (thus failing DFSG#3). Moreover, the license grant
 to attempt to restrict use to "products supporting the Unicode
 Standard" (thus failing DFSG#6).
 .
 In this case a solution is to use libicu and to remove this code
 by repacking.
 .
 If this is a false-positive, please report a bug against Lintian.
Ref: #823100

The bug report referenced (#823100) has more discussion on this
point.

I'm also going to drop a line to the upstream maintainers to see
whether they could write their own replacement for this pair of files,
or liaise with the Unicode Consortium to relicense them.

Best wishes,

   Julian
--- End Message ---
--- Begin Message ---
Version: 2.5.8+ds2-4

Hi,
SFconv/ConvertUTF.[ch] has been replaced by SFconv/UtfCodec.[ch] which is
licensed LGPL-2.1+ or GPL-2+ or MPL-1.1

Thanks,
Daniel
--- End Message ---

Bug#814238: marked as done (teckit: conflicts with texlive-binaries 2015.20150524.37493-7+b1 (teckit_compile))

[Debian Bug Tracking System]

Your message dated Mon, 5 Nov 2018 10:05:20 +0700
with message-id 

and subject line teckit texlive-binaries conflicts updated and changed to 
breaks/replace
has caused the Debian Bug report #814238,
regarding teckit: conflicts with texlive-binaries 2015.20150524.37493-7+b1 
(teckit_compile)
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.)


-- 
814238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814238
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: teckit
Version: 2.5.4~svn140+ds2-1
Severity: serious
Justification: Policy 7.4

Dear Maintainer,

teckit ships /usr/bin/teckit_compile, which is also installed by
texlive-binaries 2015.20150524.37493-7+b1. The "Conflicts" stanza in
teckit was foiled by texlive-binaries' binNMU...

Regards,

Stephen


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

Kernel: Linux 4.3.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Version: 2.5.8+ds2-4

The new version of teckit that is now in unstable now has breaks/replaces
against texlive-binaries (<< 2018.20180907.48586-3~)

Regards,
Daniel
--- End Message ---

Bug#912190: Bug #912190 in mixxx marked as pending

[Matteo F. Vescovi]

Control: tag -1 pending

Hello,

Bug #912190 in mixxx 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/multimedia-team/mixxx/commit/5b0ab7b1be9ae960d3c07f2a32330f2c294dbbe8


debian/patches/: patchset updated

- 0004-remove-inappropriate-arm-compiler-flags.patch added

Closes: #912190



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/912190

Processed: Bug #912190 in mixxx marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #912190 [mixxx] mixx uses inappropriate compiler flags on arm.
Added tag(s) pending.

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

Processed: Bug #912468 in java3d marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #912468 [src:java3d] java3d: FTBFS with Java 11 due to 
sun.applet.AppletAudioClip removal
Added tag(s) pending.

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