Processed: bug 901626 is forwarded to https://github.com/libtom/libtomcrypt/issues/407

[Debian Bug Tracking System]

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

> forwarded 901626 https://github.com/libtom/libtomcrypt/issues/407
Bug #901626 [src:libtomcrypt] libtomcrypt: CVE-2018-12437
Set Bug forwarded-to-address to 
'https://github.com/libtom/libtomcrypt/issues/407'.
> thanks
Stopping processing here.

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

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

[Debian Bug Tracking System]

Your message dated Fri, 15 Jun 2018 21:49:32 +
with message-id 
and subject line Bug#899455: fixed in bitcoin 0.16.1~dfsg-1
has caused the Debian Bug report #899455,
regarding bitcoin: Invalid maintainer address 
pkg-bitcoin-de...@lists.alioth.debian.org
to be marked as done.

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

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


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

Dear uploader of bitcoin,

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

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

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

Your options:

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

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

  More information about the new service can be found here:
  

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


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

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

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

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: bitcoin
Source-Version: 0.16.1~dfsg-1

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

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

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated bitcoin 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: Fri, 15 Jun 2018 23:09:21 +0200
Source: bitcoin
Binary: bitcoind bitcoin-qt bitcoin-tx
Architecture: source
Version: 0.16.1~dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Cryptocoin Team 
Changed-By: Jonas Smedegaard 
Description:
 bitcoin-qt - peer-to-peer network based digital currency - GUI
 bitcoin-tx - peer-to-peer network based digital currency - transaction tool
 bitcoind   - peer-to-peer network based digital currency - daemon
Closes: 883999 889118 899455
Changes:
 bitcoin (0.16.1~dfsg-1) unstable; urgency=medium
 .
   [ upstream ]
   * New release.
 .
   [ Jonas Smedegaard ]
   * Refresh patch 1002.
   * Drop build target get-orig-source: Obsolete.
   * Stop build and package shared library bitcoinconsensus:
 Apparently unused anywhere, and unstable API.
 Closes: Bug#889118. Thanks to Adrian Bunk.
   * Use tracker.debian team email as Maintainer.
 Closes: Bug#899455. Thanks to Christoph Biedl.
   * Improve long descriptions, based on Wikipedia description.
   * Use semantic newlines in long descriptions.
   * Fix typo in watch file usage comment.
   * Add patch 1003 to fix header sections of man pages.
 Closes: Bug#883999. Thanks to 積丹尼 Dan Jacobson.
Checksums-Sha1:
 

Bug#889118: marked as done (bitcoin FTBFS with gcc-7 7.3.0-1: symbols disappeared)

[Debian Bug Tracking System]

Your message dated Fri, 15 Jun 2018 21:49:32 +
with message-id 
and subject line Bug#889118: fixed in bitcoin 0.16.1~dfsg-1
has caused the Debian Bug report #889118,
regarding bitcoin FTBFS with gcc-7 7.3.0-1: symbols disappeared
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.)


-- 
889118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889118
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bitcoin
Version: 0.15.1~dfsg-1
Severity: serious

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

...
   debian/rules override_dh_makeshlibs
make[1]: Entering directory '/build/1st/bitcoin-0.15.1~dfsg'
dh_makeshlibs -- 
dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libbitcoinconsensus0/DEBIAN/symbols doesn't 
match completely debian/libbitcoinconsensus0.symbols
--- debian/libbitcoinconsensus0.symbols 
(libbitcoinconsensus0_0.15.1~dfsg-1_amd64)
+++ dpkg-gensymbolsk5YxNq   2019-03-05 21:13:06.499223011 -1200
@@ -38,7 +38,7 @@
  _Z14ArithToUint256RK13arith_uint256@Base 0.14.2~dfsg
 #MISSING: 0.15.0~~# _Z14GetBlockWeightRK6CBlock@Base 0.14.2~dfsg
  
_Z14SanitizeStringRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEi@Base 
0.14.2~dfsg
- 
(optional=templinst|arch-bits=64)_Z14Serialize_implI13CSizeComputer5CTxInSaIS1_ES1_EvRT_RKSt6vectorIT0_T1_ERKT2_@Base
 0.15.0~~
+#MISSING: 0.15.1~dfsg-1# 
(optional=templinst|arch-bits=64)_Z14Serialize_implI13CSizeComputer5CTxInSaIS1_ES1_EvRT_RKSt6vectorIT0_T1_ERKT2_@Base
 0.15.0~~
  (arch-bits=64)_Z14SipHashUint256mmRK7uint256@Base 0.14.2~dfsg
  (arch-bits=32)_Z14SipHashUint256yyRK7uint256@Base 0.14.2~dfsg
  _Z14UintToArith256RK7uint256@Base 0.14.2~dfsg
@@ -47,7 +47,7 @@
  
(arch-bits=64)_Z15FormatParagraphRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEmm@Base
 0.14.2~dfsg
  
(arch-bits=64)_Z15ParseFixedPointRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEiPl@Base
 0.14.2~dfsg
  
(arch-bits=32)_Z15ParseFixedPointRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEiPx@Base
 0.14.2~dfsg
-#MISSING: 0.15.0~~# 
(optional=templinst)_Z16GetSerializeSizeI6CBlockE{size_t}RKT_ii@Base 0.14.2~dfsg
+#MISSING: 0.15.1~dfsg-1# 
(optional=templinst)_Z16GetSerializeSizeI6CBlockE{size_t}RKT_ii@Base 0.14.2~dfsg
  _Z16SHA256AutoDetectB5cxx11v@Base 0.15.0~~
  
(optional=templinst|arch-bits=64)_Z16WriteCompactSizeI11CHashWriterEvRT_m@Base 
0.14.2~dfsg
  
(optional=templinst|arch-bits=32)_Z16WriteCompactSizeI11CHashWriterEvRT_y@Base 
0.14.2~dfsg
@@ -58,8 +58,8 @@
  _Z19ComputeMerkleBranchRKSt6vectorI7uint256SaIS0_EEj@Base 0.14.2~dfsg
  (subst)_Z19SipHashUint256Extra{uint64_t}{uint64_t}RK7uint256j@Base 0.15.0~~
 #MISSING: 0.15.0~~# _Z20GetTransactionWeightRK12CTransaction@Base 0.14.2~dfsg
-#MISSING: 0.15.0~~# 
(optional=templinst)_Z20SerializeTransactionI11CHashWriter12CTransactionEvRKT0_RT_@Base
 0.14.2~dfsg
-#MISSING: 0.15.0~~# 
(optional=templinst)_Z20SerializeTransactionI13CSizeComputer12CTransactionEvRKT0_RT_@Base
 0.14.2~dfsg
+#MISSING: 0.15.1~dfsg-1# 
(optional=templinst)_Z20SerializeTransactionI11CHashWriter12CTransactionEvRKT0_RT_@Base
 0.14.2~dfsg
+#MISSING: 0.15.1~dfsg-1# 
(optional=templinst)_Z20SerializeTransactionI13CSizeComputer12CTransactionEvRKT0_RT_@Base
 0.14.2~dfsg
  _Z22BlockWitnessMerkleRootRK6CBlockPb@Base 0.14.2~dfsg
  _Z22CheckSignatureEncodingRKSt6vectorIhSaIhEEjP13ScriptError_t@Base 
0.14.2~dfsg
  _Z27ComputeMerkleRootFromBranchRK7uint256RKSt6vectorIS_SaIS_EEj@Base 
0.14.2~dfsg
@@ -247,8 +247,8 @@
  (optional=templinst)_ZN9base_uintILj256EEmLERKS0_@Base 0.14.2~dfsg
  (optional=templinst)_ZN9base_uintILj256EEmLEj@Base 0.14.2~dfsg
  (optional=templinst)_ZN9base_uintILj256EErSEj@Base 0.14.2~dfsg
-#MISSING: 0.15.0~~# (optional=templinst)_ZN9prevectorILj28EhjiED1Ev@Base 
0.14.2~dfsg
-#MISSING: 0.15.0~~# (optional=templinst)_ZN9prevectorILj28EhjiED2Ev@Base 
0.14.2~dfsg
+#MISSING: 0.15.1~dfsg-1# (optional=templinst)_ZN9prevectorILj28EhjiED1Ev@Base 
0.14.2~dfsg
+#MISSING: 0.15.1~dfsg-1# (optional=templinst)_ZN9prevectorILj28EhjiED2Ev@Base 
0.14.2~dfsg
  _ZNK10CExtPubKey6DeriveERS_j@Base 0.11.0
  _ZNK10CExtPubKey6EncodeEPh@Base 0.11.0
  _ZNK10CSipHasher8FinalizeEv@Base 0.14.2~dfsg
@@ -314,14 +314,14 @@
  
(optional=templinst|arch-bits=32)_ZNSt6vectorI7uint256SaIS0_EE17_M_default_appendEj@Base
 0.14.2~dfsg
  
(optional=templinst|arch-bits=64)_ZNSt6vectorI7uint256SaIS0_EE17_M_default_appendEm@Base
 0.14.2~dfsg
  

Bug#901626: libtomcrypt: CVE-2018-12437

[Michael Stapelberg]

Filed https://github.com/libtom/libtomcrypt/issues/407, let’s see when
upstream comes up with a patch.

On Fri, Jun 15, 2018 at 9:22 PM, Salvatore Bonaccorso 
wrote:

> Source: libtomcrypt
> Version: 1.18.1-1
> Severity: grave
> Tags: security upstream
>
> Hi,
>
> The following vulnerability was published for libtomcrypt.
>
> CVE-2018-12437[0]:
> | LibTomCrypt through 1.18.1 allows a memory-cache side-channel attack on
> | ECDSA signatures, aka the Return Of the Hidden Number Problem or ROHNP.
> | To discover an ECDSA key, the attacker needs access to either the local
> | machine or a different virtual machine on the same physical host.
>
> 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-12437
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12437
>
> Please adjust the affected versions in the BTS as needed.
>
> Regards,
> Salvatore
>



-- 
Best regards,
Michael

Bug#901562: invesalius: Segmentation fault at startup

[Torquil Macdonald Sørensen]

Hi,

I'm using XFCE4, so that would be xfwm4. I did another thing:
/usr/bin/invesalius3 is a shell script, so I executed those commands
manuall in my shell. But instead of "python app.py", I ran gdb, and then
the gdb commands "file python", "set args app.py", "run". When
invesalius3 then crashed, I could then get a backtrace by running "bt",
It gave the following output:

(gdb) bt
#0  0x73106202 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#1  0x7313c47e in gdk_x11_window_get_xid () from
/usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#2  0x76021251 in ?? () from
/usr/lib/python2.7/dist-packages/wx-3.0-gtk3/wx/_core_.x86_64-linux-gnu.so
#3  0x5564f874 in PyEval_EvalFrameEx ()
#4  0x55646c7a in PyEval_EvalCodeEx ()
#5  0x5564edb4 in PyEval_EvalFrameEx ()
#6  0x5564e3e2 in PyEval_EvalFrameEx ()
#7  0x55646c7a in PyEval_EvalCodeEx ()
#8  0x55662b09 in ?? ()
#9  0x5567b2be in ?? ()
#10 0x5563290e in PyObject_Call ()
#11 0x556529f0 in PyEval_CallObjectWithKeywords ()
#12 0x75fa9e99 in wxPyCallback::EventThunker(wxEvent&) () from
/usr/lib/python2.7/dist-packages/wx-3.0-gtk3/wx/_core_.x86_64-linux-gnu.so
#13 0x744438ce in
wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const&,
wxEvtHandler*, wxEvent&) () from
/usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0
#14 0x74443cda in
wxEvtHandler::SearchDynamicEventTable(wxEvent&) () from
/usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0
#15 0x74443d6f in wxEvtHandler::TryHereOnly(wxEvent&) () from
/usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0
#16 0x74443e23 in wxEvtHandler::ProcessEventLocally(wxEvent&) ()
from /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0
#17 0x74443e85 in wxEvtHandler::ProcessEvent(wxEvent&) () from
/usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0
#18 0x74443be7 in wxEvtHandler::SafelyProcessEvent(wxEvent&) ()
from /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0
#19 0x74dd4557 in wxWindow::DoSetSize(int, int, int, int, int)
() from /usr/lib/x86_64-linux-gnu/libwx_gtk3u_core-3.0.so.0
#20 0x74f6329a in wxBoxSizer::RecalcSizes() () from
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_core-3.0.so.0
#21 0x74f6111e in wxSizer::Layout() () from
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_core-3.0.so.0
#22 0x74f60fb5 in wxSizerItem::SetDimension(wxPoint const&,
wxSize const&) () from /usr/lib/x86_64-linux-gnu/libwx_gtk3u_core-3.0.so.0
#23 0x74f6329a in wxBoxSizer::RecalcSizes() () from
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_core-3.0.so.0
#24 0x74f6111e in wxSizer::Layout() () from
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_core-3.0.so.0
#25 0x74f95436 in wxWindowBase::Layout() () from
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_core-3.0.so.0
#26 0x74f8fe66 in wxWindowBase::InternalOnSize(wxSizeEvent&) ()
from /usr/lib/x86_64-linux-gnu/libwx_gtk3u_core-3.0.so.0
#27 0x744438ce in
wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const&,
wxEvtHandler*, wxEvent&) () from
/usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0
#28 0x744439d3 in wxEventHashTable::HandleEvent(wxEvent&,
wxEvtHandler*) () from /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0
#29 0x74443d9b in wxEvtHandler::TryHereOnly(wxEvent&) () from
/usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0
#30 0x74443e23 in wxEvtHandler::ProcessEventLocally(wxEvent&) ()
from /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0
#31 0x74443e85 in wxEvtHandler::ProcessEvent(wxEvent&) () from
/usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0
#32 0x74443be7 in wxEvtHandler::SafelyProcessEvent(wxEvent&) ()
from /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0
#33 0x74dd4557 in wxWindow::DoSetSize(int, int, int, int, int)
() from /usr/lib/x86_64-linux-gnu/libwx_gtk3u_core-3.0.so.0
#34 0x74dd661d in wxWindow::DoSetClientSize(int, int) () from
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_core-3.0.so.0
#35 0x74f649a7 in wxSizer::Fit(wxWindow*) () from
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_core-3.0.so.0
#36 0x76043941 in ?? () from
/usr/lib/python2.7/dist-packages/wx-3.0-gtk3/wx/_core_.x86_64-linux-gnu.so
#37 0x5564f874 in PyEval_EvalFrameEx ()
#38 0x55646c7a in PyEval_EvalCodeEx ()
#39 0x5564edb4 in PyEval_EvalFrameEx ()
#40 0x5564e3e2 in PyEval_EvalFrameEx ()
#41 0x55646c7a in PyEval_EvalCodeEx ()
#42 0x55662b09 in ?? ()
#43 0x5567b2be in ?? ()
#44 0x5567aeca in ?? ()
#45 0x55637afb in ?? ()
#46 0x5564e5d0 in PyEval_EvalFrameEx ()
#47 0x5564e3e2 in PyEval_EvalFrameEx ()
#48 0x55646c7a in PyEval_EvalCodeEx ()
#49 0x55662b09 in ?? ()
#50 0x5567b2be in ?? ()
#51 0x5567aeca in ?? ()
#52 0x55637afb in ?? ()
#53 0x5564e5d0 in PyEval_EvalFrameEx ()
#54 0x5564e3e2 in PyEval_EvalFrameEx ()
#55 0x55646c7a in PyEval_EvalCodeEx 

Bug#901562: invesalius: Segmentation fault at startup

[Thiago Franco Moraes]

Hi,

What window manager are your using? I don't why yet, but this error
doesn't happen if you use KDE as window manager. It's happening also
with the git version (https://github.com/invesalius/invesalius3). If
you use the WXPython4 this doesn't happen, but you need to use the git
version.

Thanks for the bug report.
On Thu, Jun 14, 2018 at 3:27 PM Torquil Macdonald Sørensen
 wrote:
>
> Package: invesalius
> Version: 3.1.1-3
> Severity: grave
> Justification: renders package unusable
>
> When trying to run invesalius, I get this segmentation fault:
>
> torquil@lenovo-p51:~$ invesalius3
> /usr/share/invesalius/invesalius/data/transformations.py:1899: UserWarning: 
> failed to import module _transformations
>   warnings.warn("failed to import module %s" % name)
>   session mode:  0
>   Segmentation fault
> torquil@lenovo-p51:~$
>
> Best regards,
> Torquil Sørensen
>
> -- System Information:
> Debian Release: buster/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.16.0-2-amd64 (SMP w/8 CPU cores)
> Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
> LANGUAGE=en_GB:en (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages invesalius depends on:
> ii  invesalius-bin 3.1.1-3
> ii  python 2.7.15-3
> ii  python-concurrent.futures  3.2.0-1
> ii  python-configparser3.5.0-1
> ii  python-gdcm2.8.6-2
> ii  python-nibabel 2.3.0-1
> ii  python-numpy   1:1.14.5-1
> ii  python-pil 5.1.0-1
> ii  python-psutil  5.4.6-1
> ii  python-scipy   0.19.1-2
> ii  python-serial  3.4-3
> ii  python-skimage 0.13.1-3
> ii  python-vtk66.3.0+dfsg2-2+b2
> ii  python-vtkgdcm 2.8.6-2
> ii  python-wxgtk3.03.0.2.0+dfsg-8
> ii  python2.7  2.7.15-1
>
> invesalius recommends no packages.
>
> invesalius suggests no packages.
>
> -- no debconf information

Bug#901634: amide: Doesn't run due to linking error

[Torquil Macdonald Sørensen]

Package: amide
Version: 1.0.5-10
Severity: grave
Justification: renders package unusable

Amide doesn't start due to a library linkage issue:

$ amide
amide: error while loading shared libraries: libmdc.so.2: cannot open shared 
object file: No such file or directory

I have libmdc2 installer because it is a dependency, but the library file is 
libmdc.so.3, not libmdc.so.2.

Best regards
Torquil Sørensen

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

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

Versions of packages amide depends on:
ii  libavcodec577:3.4.2-2+b2
ii  libavutil55 7:3.4.2-2+b2
ii  libc6   2.27-3
ii  libdcmtk12  3.6.2-3+b1
ii  libgcc1 1:8.1.0-5
ii  libgdk-pixbuf2.0-0  2.36.11-2
ii  libglib2.0-02.56.1-2
ii  libgnomecanvas2-0   2.30.3-3
ii  libgsl232.4+dfsg-6
ii  libgslcblas02.4+dfsg-6
ii  libgtk2.0-0 2.24.32-1
ii  libmdc2 0.15.0-1
ii  libpango-1.0-0  1.42.1-1
ii  libstdc++6  8.1.0-5
ii  libvolpack1 1.0b3-6
ii  libxml2 2.9.4+dfsg1-7

amide recommends no packages.

Versions of packages amide suggests:
pn  yelp  

-- no debconf information

Bug#896726: marked as done (gedit-source-code-browser-plugin: missing build dependency on dh-python)

[Debian Bug Tracking System]

Your message dated Fri, 15 Jun 2018 20:46:41 +
with message-id 
and subject line Bug#896726: fixed in gedit-source-code-browser-plugin 3.0.3-5.1
has caused the Debian Bug report #896726,
regarding gedit-source-code-browser-plugin: 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.)


-- 
896726: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896726
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gedit-source-code-browser-plugin
Version: 3.0.3-5
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gedit-source-code-browser-plugin.html

...
 fakeroot debian/rules clean
dh clean --with python3
dh: Compatibility levels before 9 are deprecated (level 7 in use)
dh: unable to load addon python3: Can't locate 
Debian/Debhelper/Sequence/python3.pm in @INC (you may need to install the 
Debian::Debhelper::Sequence::python3 module) (@INC contains: /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.26.2 /usr/local/share/perl/5.26.2 
/usr/lib/x86_64-linux-gnu/perl5/5.26 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.26 /usr/share/perl/5.26 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at (eval 2) line 
1.
BEGIN failed--compilation aborted at (eval 2) line 1.

make: *** [debian/rules:5: clean] Error 2
--- End Message ---
--- Begin Message ---
Source: gedit-source-code-browser-plugin
Source-Version: 3.0.3-5.1

We believe that the bug you reported is fixed in the latest version of
gedit-source-code-browser-plugin, 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.
Adrian Bunk  (supplier of updated 
gedit-source-code-browser-plugin 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, 10 Jun 2018 16:42:35 +0300
Source: gedit-source-code-browser-plugin
Binary: gedit-source-code-browser-plugin
Architecture: source
Version: 3.0.3-5.1
Distribution: unstable
Urgency: medium
Maintainer: Pietro Battiston 
Changed-By: Adrian Bunk 
Description:
 gedit-source-code-browser-plugin - source code class and function browser 
plugin for Gedit
Closes: 896726
Changes:
 gedit-source-code-browser-plugin (3.0.3-5.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add the missing build dependency on dh-python. (Closes: #896726)
Checksums-Sha1:
 d37765291de7dcefcc73ca40407ffd4d1fa1b067 2158 
gedit-source-code-browser-plugin_3.0.3-5.1.dsc
 35d17e1ea3e915af3f91e95b1fcd30a1ce5f7210 4780 
gedit-source-code-browser-plugin_3.0.3-5.1.debian.tar.xz
Checksums-Sha256:
 5b9c0a0cf5902cc1e73fb82e85d73dca5c043ba1d1927bc25cb8c7f396dce176 2158 
gedit-source-code-browser-plugin_3.0.3-5.1.dsc
 bacaf87be257ce3874d29444056ce4fda502d3dab3286a3a918664a02f0e4ba7 4780 
gedit-source-code-browser-plugin_3.0.3-5.1.debian.tar.xz
Files:
 8a5fc4b1a7a7af965cf9b4a3b3ae5443 2158 gnome optional 
gedit-source-code-browser-plugin_3.0.3-5.1.dsc
 bbb3bf03cd6ce8d42c416eff5bf40dad 4780 gnome optional 
gedit-source-code-browser-plugin_3.0.3-5.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlsdKx4ACgkQiNJCh6LY
mLH/IQ/+O1RM1BBNNWJt7mgmE5ZSgynuHv1yyinjjzQX9yToEFQjwK/4sNJkKdNS
m0WikmwC4FkSxKHY7vPRMRJn5zLhKJvWoffyFjIsyF1tHvzWCoiIr1JZ+aVKQcc1
ZXIxjdqB7NqVPQ7CNttJ5qL2yeHDXan80p42xCYeIEJlEtQXQabCdJQLxJWKZnTN
/WTgrrtDDIEVtYD1Ly9poSA+cJjtBsga6cD4vAd4UDQxj0caBynAMHZDNGC8tNpB
rl8TmIE1yWIVluyT5Y/PPj1s1h9ksjqrtPDQM/IRfNkvUSIS8KDFyQ4oUJ9N/YXg
h5iHlj2AXFlO1DiXfpTe+5shNi5T6ztIuVOWNNvajCPOrtC9k2YD3o0rmY7aPegZ
r5Dq0PYIKqdFtNqcVWVuzBHRyMM3kqQpJydZzhxBA6CY0U40ju8WMkrEMqmkKY5s
0Q4Iri0zbZ8WpBHdOw9lgaOKabtgovNuJnoOFzjd2FFZDcIBJdLYhZsB9p4cCtEY
8lMqEMJjSsJ/8e+QIgw1Vy75t8flTZgwgsUQVV5jdVzcfurfj1/Z+CnfaKVRo3l/
1BFOgFm0rudyRiPT4GmrvM4u+hs9VrPdJvSV/GVFAr+irgv45mu58hi/HIvaZ3yZ
LusZUWY0iouJbznRWyRg+f1Rg0YewBeCP9de71qerCDLXUvKxoo=
=+fx2
-END PGP SIGNATURE End Message ---

Bug#901633: plastimatch: Uninstallable

[Torquil Macdonald Sørensen]

Package: plastimatch
Severity: grave
Justification: renders package unusable

It seems that plastimatch is uninstallable in Sid:

# apt-get install plastimatch
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 plastimatch : Depends: libdlib18 but it is not installable
E: Unable to correct problems, you have held broken packages.
#

Best regards
Torquil Sørensen

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

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

Versions of packages plastimatch depends on:
ii  libblas3 [libblas.so.3]  3.8.0-1
ii  libc62.27-3
pn  libdcmtk12   
pn  libdlib18
ii  libfftw3-double3 3.3.7-1+b1
ii  libgcc1  1:8.1.0-5
ii  libgdcm2.8   2.8.6-2
ii  libgomp1 8.1.0-5
pn  libinsighttoolkit4.12
ii  liblapack3 [liblapack.so.3]  3.8.0-1
ii  libstdc++6   8.1.0-5

plastimatch recommends no packages.

plastimatch suggests no packages.

Bug#901632: miniupnpd: Fails to upgrade from buster: postinst: sed: -e expression #1, char 82: unknown option to `s'

[Salvatore Bonaccorso]

Package: miniupnpd
Version: 2.1-1
Severity: serious
Justification: fails to upgrade from buster to sid

Hi

miniupnpd upgrade from buster (1.8.20140523-4.2) to sid (2.1-1) fails
with the following:

root@miniupnpd:~# apt-get install miniupnpd
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be upgraded:
  miniupnpd
1 upgraded, 0 newly installed, 0 to remove and 7 not upgraded.
Need to get 99.4 kB of archives.
After this operation, 25.6 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian sid/main amd64 miniupnpd amd64 2.1-1 [99.4 
kB]
Fetched 99.4 kB in 0s (475 kB/s)
debconf: delaying package configuration, since apt-utils is not installed
(Reading database ... 8892 files and directories currently installed.)
Preparing to unpack .../miniupnpd_2.1-1_amd64.deb ...
Migrating old "/etc/default/miniupnpd"...
Unpacking miniupnpd (2.1-1) over (1.8.20140523-4.2) ...
Processing triggers for systemd (238-5) ...
Setting up miniupnpd (2.1-1) ...

Configuration file '/etc/default/miniupnpd'
 ==> File on system created by you or by a script.
 ==> File also in package provided by package maintainer.
   What would you like to do about it ?  Your options are:
Y or I  : install the package maintainer's version
N or O  : keep your currently-installed version
  D : show the differences between the versions
  Z : start a shell to examine the situation
 The default action is to keep your current version.
*** miniupnpd (Y/I/N/O/D/Z) [default=N] ? Y
Installing new version of config file /etc/default/miniupnpd ...
Installing new version of config file /etc/init.d/miniupnpd ...
Installing new version of config file /etc/miniupnpd/ip6tables_init.sh ...
Installing new version of config file /etc/miniupnpd/ip6tables_removeall.sh ...
Installing new version of config file /etc/miniupnpd/iptables_init.sh ...
Installing new version of config file /etc/miniupnpd/iptables_removeall.sh ...
sed: -e expression #1, char 82: unknown option to `s'
dpkg: error processing package miniupnpd (--configure):
 installed miniupnpd package post-installation script subprocess returned error 
exit status 1
Processing triggers for systemd (238-5) ...
Errors were encountered while processing:
 miniupnpd
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@miniupnpd:~#

Regards,
Salvatore

Bug#864432: funcoeszz: depends on a transitional package lynx-cur

[Paulo Henrique de Lima Santana]

Control: tags + patch

Hi Eder,

I'm sending a patch to help to fix this bug (and this is a task to my DD
process too).

I changed lynx-cur to lynx on control file, and updated Standards-Version to
4.1.4

Best regards,

-- 
Paulo Henrique de Lima Santana (phls)
Curitiba - Brasil
Membro da Comunidade Curitiba Livre
Site: http://www.phls.com.br
GNU/Linux user: 228719  GPG ID: 0443C450

Apoie a campanha pela igualdade de gênero #HeForShe (#ElesPorElas)  
http://www.heforshe.org/pt
diff -Nru funcoeszz-15.5/debian/changelog funcoeszz-15.5/debian/changelog
--- funcoeszz-15.5/debian/changelog	2015-08-21 15:06:36.0 -0300
+++ funcoeszz-15.5/debian/changelog	2018-06-15 15:35:53.0 -0300
@@ -1,3 +1,12 @@
+funcoeszz (15.5-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/control:
+  - Bumped Standards-Version to 4.1.4.
+  - Changed lynx-cur to lynx. (Closes: #864432)
+
+ -- Paulo Henrique de Lima Santana (phls)   Fri, 15 Jun 2018 15:35:53 -0300
+
 funcoeszz (15.5-1) unstable; urgency=medium
 
   [ Eder Diego de Lima Marques ]
diff -Nru funcoeszz-15.5/debian/control funcoeszz-15.5/debian/control
--- funcoeszz-15.5/debian/control	2015-08-21 14:57:20.0 -0300
+++ funcoeszz-15.5/debian/control	2018-06-15 15:35:53.0 -0300
@@ -3,11 +3,11 @@
 Priority: optional
 Maintainer: Eder Diego de Lima Marques 
 Build-Depends: debhelper (>= 9.0.0)
-Standards-Version: 3.8.0
+Standards-Version: 4.1.4
 
 Package: funcoeszz
 Architecture: all
-Depends: lynx-cur, ${misc:Depends}
+Depends: lynx, ${misc:Depends}
 Homepage: http://funcoeszz.net/
 Description: script with 170+ useful mini applications
  Funcoes ZZ is a bash script that contains more than 170 useful applications,


pgpKeYlENCRhL.pgp
Description: PGP signature

Bug#901627: wolfssl: CVE-2018-12436

[Salvatore Bonaccorso]

Source: wolfssl
Version: 3.13.0+dfsg-1
Severity: grave
Tags: security upstream

Hi,

The following vulnerability was published for wolfssl.

CVE-2018-12436[0]:
| wolfcrypt/src/ecc.c in wolfSSL before 3.15.1.patch allows a
| memory-cache side-channel attack on ECDSA signatures, aka the Return Of
| the Hidden Number Problem or ROHNP. To discover an ECDSA key, the
| attacker needs access to either the local machine or a different
| virtual machine on the same physical host.

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-12436
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12436
[1] 
https://github.com/wolfSSL/wolfssl/commit/9b9568d500f31f964af26ba8d01e542e1f27e5ca
[2] https://www.wolfssl.com/wolfssh-and-rohnp/

Regards,
Salvatore

Bug#901626: libtomcrypt: CVE-2018-12437

[Salvatore Bonaccorso]

Source: libtomcrypt
Version: 1.18.1-1
Severity: grave
Tags: security upstream

Hi,

The following vulnerability was published for libtomcrypt.

CVE-2018-12437[0]:
| LibTomCrypt through 1.18.1 allows a memory-cache side-channel attack on
| ECDSA signatures, aka the Return Of the Hidden Number Problem or ROHNP.
| To discover an ECDSA key, the attacker needs access to either the local
| machine or a different virtual machine on the same physical host.

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-12437
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12437

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#901513: marked as done (slurm-client: fails to upgrade from 'wheezy' - trying to overwrite /usr/bin/sacctmgr, /usr/share/man/man1/sacctmgr.1.gz)

[Debian Bug Tracking System]

Your message dated Fri, 15 Jun 2018 19:04:41 +
with message-id 
and subject line Bug#901513: fixed in slurm-llnl 14.03.9-5+deb8u2
has caused the Debian Bug report #901513,
regarding slurm-client: fails to upgrade from 'wheezy' - trying to overwrite 
/usr/bin/sacctmgr, /usr/share/man/man1/sacctmgr.1.gz
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.)


-- 
901513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901513
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: slurm-client
Version: 14.03.9-5+deb8u1
Severity: serious
Tags: jessie
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'wheezy'.
It installed fine in 'wheezy', then the upgrade to 'jessie' 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...):

  Selecting previously unselected package slurm-client.
  Unpacking slurm-client (from .../slurm-client_14.03.9-5+deb8u1_amd64.deb) ...
  dpkg: error processing 
/var/cache/apt/archives/slurm-client_14.03.9-5+deb8u1_amd64.deb (--unpack):
   trying to overwrite '/usr/share/man/man1/sacctmgr.1.gz', which is also in 
package slurm-llnl-slurmdbd 2.3.4-2+b1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/slurm-client_14.03.9-5+deb8u1_amd64.deb

The conflicting files are:

  usr/bin/sacctmgr
  usr/share/man/man1/sacctmgr.1.gz

This should be fixable by adding
  Breaks+Replaces: slurm-llnl-slurmdbd (<< 14.03.9-5)
(The existing B+R: slurmdbd (<< 14.03.9-5) is probably incorrect and was
intended to do this, but better keep it in place ...)

Please note that the window for the final jessie point release closes
this weekend ...


cheers,

Andreas


slurm-llnl-slurmdbd=2.3.4-2+b1_slurm-client=14.03.9-5+deb8u1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: slurm-llnl
Source-Version: 14.03.9-5+deb8u2

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated slurm-llnl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 15 Jun 2018 15:58:33 +0200
Source: slurm-llnl
Binary: slurm-wlm slurm-client slurmd slurmctld libslurmdb27 libslurm27 libpmi0 
libslurm-dev libslurmdb-dev libpmi0-dev slurm-wlm-doc slurm-wlm-basic-plugins 
slurm-wlm-basic-plugins-dev sview slurmdbd libslurm-perl libslurmdb-perl 
slurm-wlm-torque libpam-slurm slurm-llnl slurm-llnl-slurmdbd
Architecture: source all
Version: 14.03.9-5+deb8u2
Distribution: jessie
Urgency: medium
Maintainer: Gennaro Oliva 
Changed-By: Andreas Beckmann 
Description:
 libpam-slurm - PAM module to authenticate using the SLURM resource manager
 libpmi0- SLURM PMI library implementation
 libpmi0-dev - SLURM PMI library implementation development files
 libslurm-dev - SLURM development files
 libslurm-perl - Perl API for SLURM
 libslurm27 - Runtime library files for SLURM
 libslurmdb-dev - SLURM DataBase Daemon development files
 libslurmdb-perl - Perl API for the SLURM database
 libslurmdb27 - Runtime library files for the SLURM DataBase Daemon
 slurm-client - SLURM client side commands
 slurm-llnl - transitional dummy package for slurm-wlm
 slurm-llnl-slurmdbd - transitional dummy package for slurmdbd
 slurm-wlm  - Simple Linux Utility for Resource Management
 slurm-wlm-basic-plugins - SLURM basic plugins
 slurm-wlm-basic-plugins-dev - SLURM basic plugins development files
 slurm-wlm-doc - SLURM docmentation
 slurm-wlm-torque - Torque compatibility wrappers for SLURM
 slurmctld  - SLURM central management daemon
 slurmd - SLURM compute node daemon
 slurmdbd   - Secure enterprise-wide interface to a database for SLURM
 sview  - GUI to view and modify SLURM state

Bug#901619: botan: CVE-2018-12435: memory-cache side-channel attack on ECDSA signatures

[Salvatore Bonaccorso]

Source: botan
Version: 2.6.0-1
Severity: grave
Tags: patch security upstream
Justification: user security hole
Forwarded: https://github.com/randombit/botan/pull/1604

Hi,

The following vulnerability was published for botan.

CVE-2018-12435[0]:
| Botan 2.5.0 through 2.6.0 allows a memory-cache side-channel attack on
| ECDSA signatures, aka the Return Of the Hidden Number Problem or
| ROHNP, related to dsa/dsa.cpp, ec_group/ec_group.cpp, and
| ecdsa/ecdsa.cpp. To discover an ECDSA key, the attacker needs access
| to either the local machine or a different virtual machine on the same
| physical host.

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-12435
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12435
[1] https://github.com/randombit/botan/pull/1604
[2] 
https://github.com/randombit/botan/pull/1604/commits/48fc8df51d99f9d8ba251219367b3d629cc848e3

Please adjust the affected versions in the BTS as needed.

Note please that initially the CVE for libgcrypt was reused. But the
above one and used here is the right one.

Regards,
Salvatore

Bug#899580: marked as done (libkkc-data: Invalid maintainer address pkg-ime-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Fri, 15 Jun 2018 16:37:17 +
with message-id 
and subject line Bug#899580: fixed in libkkc-data 0.2.7-2
has caused the Debian Bug report #899580,
regarding libkkc-data: Invalid maintainer address 
pkg-ime-de...@lists.alioth.debian.org
to be marked as done.

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

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


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

Dear uploader of libkkc-data,

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

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

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

Your options:

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

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

  More information about the new service can be found here:
  

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


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

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

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

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: libkkc-data
Source-Version: 0.2.7-2

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

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

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

Debian distribution maintenance software
pp.
Boyuan Yang <073p...@gmail.com> (supplier of updated libkkc-data package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 07 Jun 2018 21:31:37 +0800
Source: libkkc-data
Binary: libkkc-data
Architecture: source
Version: 0.2.7-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Input Method Team 
Changed-By: Boyuan Yang <073p...@gmail.com>
Description:
 libkkc-data - language model data for libkkc
Closes: 899580
Changes:
 libkkc-data (0.2.7-2) unstable; urgency=medium
 .
   * Team upload.
   * Set maintainer to debian-input-method@lists.d.o. Closes: #899580.
   * debian: Apply "wrap-and-sort -abst" for unified format.
   * debian/control:
 - Bump Standards-Version to 4.1.4.
 - Bump debhelper compat to v11.
 - Use "Optional" priority instead of "Extra" to comply with
   latest policy.
 - Use new upstream on GitHub for Homepage field.
 - Use packaging repo on Salsa for Vcs fields.
   * debian/copyright:
 - Add my contribution information.
 - Use the new GitHub upstream project for upstream url.
   * debian/docs: Removed, useless.
   * debian/rules:
 - Use "dh_missing --fail-missing".
   * debian/watch: Rewrite and watch GitHub project.
Checksums-Sha1:
 1d2a90a4fac0c34b9b15c28a0432819c22fd7807 1962 libkkc-data_0.2.7-2.dsc
 fee01839e8045798a88822db7ba90bfb3bd2badb 2048 

Bug#858819: 2.10.0-2 missing from package index of stable

[Kraus, Sebastian]

In addition to my last post and for the sake of

clarity:

The 2.10.0-2 version of the trac-email2trac

package has been apparently built for Debian

stable as 2.10.0-2_all, but it has not been pushed

to the official package index at main:


Package: trac-email2trac
Source: email2trac
Version: 2.10.0-1
Installed-Size: 137
Maintainer: W. Martin Borgert 
Architecture: all
Depends: python, python:any, trac
Suggests: getmail4
Description: Creates and amends Trac tickets from e-mail
Homepage: https://oss.trac.surfsara.nl/email2trac
Description-md5: 2edfde2600de0a44fd3071ab45935cc4
Tag: role::plugin, works-with::bugs, works-with::mail
Section: web
Priority: optional
Filename: pool/main/e/email2trac/trac-email2trac_2.10.0-1_all.deb
Size: 43822
MD5sum: f2f7181a33ec850a7c3652b213a76dff
SHA256: 737fca926ad6c4aca1d2d63e4c170dc989b4d140bbe6c4955a61d7570f1e8626



Also on packages.debian.org, the latest release for stable

remains at  2.10.0-1 . Would be just great to have it.



Thanks and Regards

Sebastian




Sebastian Kraus
Team IT am Institut für Chemie
Gebäude C, Straße des 17. Juni 115, Raum C7

Technische Universität Berlin
Fakultät II
Institut für Chemie
Sekretariat C3
Straße des 17. Juni 135
10623 Berlin

Email: sebastian.kr...@tu-berlin.de

Bug#901526: python-django: FTBFS: FAIL: test_invalid (migrations.test_loader.PycLoaderTests)

[Chris Lamb]

forwarded 901526 https://code.djangoproject.com/ticket/29498#ticket
thanks

I've identified the issue and forwarded it upstream here:

  https://code.djangoproject.com/ticket/29498


Regards,

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

Processed: Re: python-django: FTBFS: FAIL: test_invalid (migrations.test_loader.PycLoaderTests)

[Debian Bug Tracking System]

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

> forwarded 901526 https://code.djangoproject.com/ticket/29498#ticket
Bug #901526 [src:python-django] python-django: FTBFS: FAIL: test_invalid 
(migrations.test_loader.PycLoaderTests)
Set Bug forwarded-to-address to 
'https://code.djangoproject.com/ticket/29498#ticket'.
> thanks
Stopping processing here.

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

Bug#891755: marked as done (ruby-html-pipeline FTBFS with ruby 2.5: test failures)

[Debian Bug Tracking System]

Your message dated Fri, 15 Jun 2018 15:03:06 +
with message-id 
and subject line Bug#891755: fixed in ruby-html-pipeline 2.8.0+gh-1
has caused the Debian Bug report #891755,
regarding ruby-html-pipeline FTBFS with ruby 2.5: 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.)


-- 
891755: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891755
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-html-pipeline
Version: 1.11.0-1
Severity: serious

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

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

RUBYLIB=/build/1st/ruby-html-pipeline-1.11.0/debian/ruby-html-pipeline/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-html-pipeline/usr/share/rubygems-integration/all:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 -S rake -f debian/ruby-tests.rake
Run options: --seed 62382

# Running:

..F.F...

Finished in 0.099830s, 1081.8441 runs/s, 1763.0052 assertions/s.

  1) Failure:
HTML::Pipeline::TableOfContentsFilterTest#test_anchors_with_utf8_characters 
[/build/1st/ruby-html-pipeline-1.11.0/test/html/pipeline/toc_filter_test.rb:112]:
--- expected
+++ actual
@@ -1,3 +1,3 @@
 # encoding: UTF-8
 "
-\u0420\u0443\u0441\u0441\u043A\u0438\u0439"
+\u0420\u0443\u0441\u0441\u043A\u0438\u0439"


  2) Failure:
HTML::Pipeline::TableOfContentsFilterTest#test_toc_with_utf8_characters 
[/build/1st/ruby-html-pipeline-1.11.0/test/html/pipeline/toc_filter_test.rb:124]:
--- expected
+++ actual
@@ -1,5 +1,5 @@
 # encoding: UTF-8
 "
 \u65E5\u672C\u8A9E
-\u0420\u0443\u0441\u0441\u043A\u0438\u0439
+\u0420\u0443\u0441\u0441\u043A\u0438\u0439
 "


108 runs, 176 assertions, 2 failures, 0 errors, 0 skips
rake aborted!
Command failed with status (1)

Tasks: TOP => default => test
(See full trace by running task with --trace)
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install 
/build/1st/ruby-html-pipeline-1.11.0/debian/ruby-html-pipeline returned exit 
code 1
make: *** [debian/rules:18: binary] Error 1
--- End Message ---
--- Begin Message ---
Source: ruby-html-pipeline
Source-Version: 2.8.0+gh-1

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

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

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

Debian distribution maintenance software
pp.
Sruthi Chandran  (supplier of updated ruby-html-pipeline 
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: Fri, 15 Jun 2018 18:16:06 +0530
Source: ruby-html-pipeline
Binary: ruby-html-pipeline
Architecture: source
Version: 2.8.0+gh-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Sruthi Chandran 
Description:
 ruby-html-pipeline - GitHub HTML processing filters and utilities
Closes: 891755
Changes:
 ruby-html-pipeline (2.8.0+gh-1) experimental; urgency=medium
 .
   * Team upload
   * Use Github tarball (to get test files)
   * Tests passing (Closes: #891755)
Checksums-Sha1:
 3e2d37c3f94f29d8a745e94966a1803cb65749be 2300 ruby-html-pipeline_2.8.0+gh-1.dsc
 7c5cfd305cef452241043b6a558c0f7ae865c7bb 36007 
ruby-html-pipeline_2.8.0+gh.orig.tar.gz
 1b516a7d1698ccb199534902bd8dd80a5283cf82 3000 
ruby-html-pipeline_2.8.0+gh-1.debian.tar.xz
 25df9f155fef8b2a54b3dc0ff91a7dbddd37ccef 6845 
ruby-html-pipeline_2.8.0+gh-1_source.buildinfo
Checksums-Sha256:
 f74a6300b77671b8237969fb4e4de6bd669b567b2872a1de0f3f69a93e5ac632 2300 
ruby-html-pipeline_2.8.0+gh-1.dsc
 e48fbeb8b2c2d488cfa20bfa4871f5417261c547dda04dfa7031d178bde3759f 36007 
ruby-html-pipeline_2.8.0+gh.orig.tar.gz
 b27228f8847fa039c8b7bc46fce786be208ce09b0afeaedb2030abeef80d5c0a 3000 

Processed: Re: Bug#901513: Acknowledgement (slurm-client: fails to upgrade from 'wheezy' - trying to overwrite /usr/bin/sacctmgr, /usr/share/man/man1/sacctmgr.1.gz)

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #901513 [slurm-client] slurm-client: fails to upgrade from 'wheezy' - 
trying to overwrite /usr/bin/sacctmgr, /usr/share/man/man1/sacctmgr.1.gz
Added tag(s) pending.

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

Bug#901513: Acknowledgement (slurm-client: fails to upgrade from 'wheezy' - trying to overwrite /usr/bin/sacctmgr, /usr/share/man/man1/sacctmgr.1.gz)

[Andreas Beckmann]

Control: tag -1 pending

jessie-pu request: #901613


Andreas

Bug#901547: seabios: Source tarball ships compiled binaries

[Chris Lamb]

Michael Tokarev wrote:

> We ensure the pre-built files are not used during build, and the source
> of them is included, so we comply to DFSG.

Indeed, I don't see a DFSG violation here..  Vivia?

Whilst it might be "better" if upstream did not ship these, repacking
the tarball simply to remove them is unnecessary and involves other
compromises.

(As an aside, it might be clearer to explicitly remove the pre-built
files in the clean target — this way it guarantees they are always
rebuilt... but that's an entire adjunct remark.)


Regards,

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

Processed: sicherboot,dracut: conffile problems when installing both

[Debian Bug Tracking System]

Processing control commands:

> found -1 0.1.5
Bug #901610 [sicherboot,dracut] sicherboot,dracut: conffile problems when 
installing both
There is no source info for the package 'dracut' at version '0.1.5' with 
architecture ''
Marked as found in versions sicherboot/0.1.5.
> found -1 047+31-2
Bug #901610 [sicherboot,dracut] sicherboot,dracut: conffile problems when 
installing both
There is no source info for the package 'sicherboot' at version '047+31-2' with 
architecture ''
Marked as found in versions dracut/047+31-2.

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

Bug#901610: sicherboot,dracut: conffile problems when installing both

[Andreas Beckmann]

Package: sicherboot,dracut
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: found -1 0.1.5
Control: found -1 047+31-2

Hi,

during a test with piuparts I noticed your package failed the piuparts
upgrade test because dpkg detected a conffile as being modified and then
prompted the user for an action. As there is no user input, this fails.
But this is not the real problem, the real problem is that this prompt
shows up in the first place, as there was nobody modifying this conffile
at all, the package has just been installed and upgraded...

This is a violation of policy 10.7.3, see
https://www.debian.org/doc/debian-policy/#behavior,
which says "[These scripts handling conffiles] must not ask unnecessary
questions (particularly during upgrades), and must otherwise be good
citizens."

https://wiki.debian.org/DpkgConffileHandling should help with figuring
out how to do this properly.

In https://lists.debian.org/debian-devel/2009/08/msg00675.html and
followups it has been agreed that these bugs are to be filed with
severity serious.

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

[...]
  Setting up sicherboot (0.1.5) ...
[...]
  Setting up dracut (047+31-2) ...
  
  Configuration file '/etc/kernel/postinst.d/dracut.SecureBoot'
   ==> Deleted (by you or by a script) since installation.
   ==> Package distributor has shipped an updated version.
 What would you like to do about it ?  Your options are:
  Y or I  : install the package maintainer's version
  N or O  : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
   The default action is to keep your current version.
  *** dracut.SecureBoot (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing 
package dracut (--configure):
   end of file on stdin at conffile prompt
  Processing triggers for libc-bin (2.27-3) ...
  Errors were encountered while processing:
   dracut

and the other way around:

[...]
  Setting up dracut (047+31-2) ...
[...]
  Setting up sicherboot (0.1.5) ...
  
  Configuration file '/etc/kernel/postinst.d/dracut'
   ==> Deleted (by you or by a script) since installation.
   ==> Package distributor has shipped an updated version.
 What would you like to do about it ?  Your options are:
  Y or I  : install the package maintainer's version
  N or O  : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
   The default action is to keep your current version.
  *** dracut (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing package 
sicherboot (--configure):
   end of file on stdin at conffile prompt
  Processing triggers for libc-bin (2.27-3) ...
  Errors were encountered while processing:
   sicherboot


I haven't checked the packages, but this looks a little bit
like you are trying to dpkg-divert a conffile, which does not
work as you intended ... there are old dpkg bugs about it,
e.g. https://bugs.debian.org/363524 so don't do it.


cheers,

Andreas


dracut=047+31-2_sicherboot=0.1.5.log.gz
Description: application/gzip


sicherboot=0.1.5_dracut=047+31-2.log.gz
Description: application/gzip

Processed: block 897533 with 894969

[Debian Bug Tracking System]

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

> block 897533 with 894969
Bug #897533 [src:sunflow] sunflow: FTBFS: convert-im6.q16: unable to open file 
`/tmp/magick-22610UfLlJYiQTV4q': No such file or directory @ 
error/constitute.c/ReadImage/544.
897533 was not blocked by any bugs.
897533 was not blocking any bugs.
Added blocking bug(s) of 897533: 894969
> thanks
Stopping processing here.

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

Bug#880276: ruby-encryptor: FTBFS: ERROR: Bug is still present?

[Pirate Praveen]

On Wed, 28 Mar 2018 14:45:42 +0200
=?UTF-8?B?RGF2aWQgTMOzcGV6IFphamFyYSAoRXJfTWFxdWkp?=
 wrote:
> Hi,
> 
> Are this bug still present with ruby2.5?

Yes, fails in ruby 2.5. This has been open for a long time with no
response from upstream :(

Bug#892995: marked as done (systemtap: failes to compile scripts, implicit declaration of some functions)

[Debian Bug Tracking System]

Your message dated Fri, 15 Jun 2018 13:54:56 +
with message-id 
and subject line Bug#892995: fixed in systemtap 3.3-1
has caused the Debian Bug report #892995,
regarding systemtap: failes to compile scripts, implicit declaration of some 
functions
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.)


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

Dear Maintainer,

The error log of "stap -v -e 'probe vfs.read {printf("read performed\n"); 
exit()}'":


Pass 1: parsed user script and 466 library scripts using 
114224virt/47336res/6424shr/41108data kb, in 60usr/80sys/198real ms.
Pass 2: analyzed script: 1 probe, 1 function, 7 embeds, 0 globals using 
290116virt/224684res/7844shr/217000data kb, in 1310usr/120sys/1442real ms.
Pass 3: translated to C into 
"/tmp/stapmbSbnD/stap_93c22f4dd82758d8a2c6248ef9859b2a_2556_src.c" using 
290116virt/224876res/8036shr/217000data kb, in 0usr/0sys/5real ms.
In file included from /usr/share/systemtap/runtime/stp_utrace.c:30:0,
 from /usr/share/systemtap/runtime/linux/task_finder2.c:4,
 from /usr/share/systemtap/runtime/linux/task_finder.c:17,
 from /usr/share/systemtap/runtime/linux/runtime.h:222,
 from /usr/share/systemtap/runtime/runtime.h:26,
 from 
/tmp/stapmbSbnD/stap_93c22f4dd82758d8a2c6248ef9859b2a_2556_src.c:25:
/usr/share/systemtap/runtime/stp_helper_lock.h: In function 
‘stp_spin_unlock_wait’:
/usr/share/systemtap/runtime/stp_helper_lock.h:60:61: error: implicit 
declaration of function ‘spin_unlock_wait’; did you mean 
‘stp_spin_unlock_wait’? [-Werror=implicit-function-declaration]
 static inline void stp_spin_unlock_wait(spinlock_t *lock) { 
spin_unlock_wait(lock); }
 ^~~~
 
stp_spin_unlock_wait
In file included from /usr/share/systemtap/runtime/transport/transport.c:65:0,
 from /usr/share/systemtap/runtime/linux/print.c:17,
 from /usr/share/systemtap/runtime/print.c:17,
 from /usr/share/systemtap/runtime/runtime_context.h:22,
 from 
/tmp/stapmbSbnD/stap_93c22f4dd82758d8a2c6248ef9859b2a_2556_src.c:121:
/usr/share/systemtap/runtime/transport/relay_v2.c: In function 
‘__stp_relay_timer_init’:
/usr/share/systemtap/runtime/transport/relay_v2.c:154:2: error: implicit 
declaration of function ‘init_timer’; did you mean ‘init_timers’? 
[-Werror=implicit-function-declaration]
  init_timer(&_stp_relay_data.timer);
  ^~
  init_timers
/usr/share/systemtap/runtime/transport/relay_v2.c:156:33: error: assignment 
from incompatible pointer type [-Werror=incompatible-pointer-types]
  _stp_relay_data.timer.function = __stp_relay_wakeup_timer;
 ^
/usr/share/systemtap/runtime/transport/relay_v2.c:157:23: error: ‘struct 
timer_list’ has no member named ‘data’
  _stp_relay_data.timer.data = 0;
   ^
In file included from /usr/share/systemtap/runtime/linux/print.c:17:0,
 from /usr/share/systemtap/runtime/print.c:17,
 from /usr/share/systemtap/runtime/runtime_context.h:22,
 from 
/tmp/stapmbSbnD/stap_93c22f4dd82758d8a2c6248ef9859b2a_2556_src.c:121:
/usr/share/systemtap/runtime/transport/transport.c: In function ‘_stp_attach’:
/usr/share/systemtap/runtime/transport/transport.c:328:31: error: assignment 
from incompatible pointer type [-Werror=incompatible-pointer-types]
  _stp_ctl_work_timer.function = _stp_ctl_work_callback;
   ^
/usr/share/systemtap/runtime/transport/transport.c:329:21: error: ‘struct 
timer_list’ has no member named ‘data’
  _stp_ctl_work_timer.data= 0;
 ^
cc1: all warnings being treated as errors
make[3]: *** 
[/usr/src/linux-headers-4.15.0-1-common/scripts/Makefile.build:321: 
/tmp/stapmbSbnD/stap_93c22f4dd82758d8a2c6248ef9859b2a_2556_src.o] Error 1
make[2]: *** [/usr/src/linux-headers-4.15.0-1-common/Makefile:1523: 
_module_/tmp/stapmbSbnD] Error 2
make[1]: *** [Makefile:146: sub-make] Error 2
make: *** [Makefile:8: all] Error 2
WARNING: kbuild exited with status: 2
Pass 4: compiled C into "stap_93c22f4dd82758d8a2c6248ef9859b2a_2556.ko" in 
7750usr/1280sys/9054real ms.
Pass 4: compilation failed.  [man error::pass4]
Tip: 

Bug#901290: marked as done (chromium: version 68 arm build causes internal compiler error)

[Debian Bug Tracking System]

 -- a fast memory error detector (x32)
 libx32asan3-dbg - AddressSanitizer -- a fast memory error detector (x32 debug 
symbo
 libx32gcc-6-dev - GCC support library (x32 development files)
 libx32gfortran-6-dev - Runtime library for GNU Fortran applications (x32 
development fil
 libx32gfortran3 - Runtime library for GNU Fortran applications (x32)
 libx32gfortran3-dbg - Runtime library for GNU Fortran applications (x32 debug 
symbols)
 libx32go9  - Runtime library for GNU Go applications (x32)
 libx32go9-dbg - Runtime library for GNU Go applications (x32 debug symbols)
 libx32gphobos-6-dev - Phobos D standard library (x32 development files)
 libx32gphobos68 - Phobos D standard library (runtime library)
 libx32gphobos68-dbg - Phobos D standard library (debug symbols)
 libx32objc-6-dev - Runtime library for GNU Objective-C applications (x32 
development
 libx32stdc++-6-dev - GNU Standard C++ Library v3 (development files)
 libx32stdc++6-6-dbg - GNU Standard C++ Library v3 (debugging files)
Closes: 898901 901290
Changes:
 gcc-6 (6.4.0-18) unstable; urgency=medium
 .
   * Update to SVN 20180615 (r261625) from the gcc-6-branch.
 - Fix PR libstdc++/67554, PR libstdc++/85632, PR target/63177 (PPC),
   PR tree-optimization/85712, PR tree-optimization/85712, PR ipa/85655,
   PR target/85903 (x86), PR target/83687 (ARM), PR lto/85405,
   PR lto/85405, PR fortran/85138, PR fortran/85996, PR fortran/86051,
   PR fortran/85895, PR fortran/85780, PR fortran/85779, PR fortran/85543,
   PR fortran/83149, PR fortran/83898, PR fortran/68846, PR fortran/70864,
   PR fortran/85542, PR fortran/70870, PR fortran/85521, PR fortran/85687,
   PR fortran/85507, PR fortran/81773, PR fortran/83606, PR fortran/85520,
   PR lto/85248, PR bootstrap/86162.
   * Fix PR middle-end/86139, taken from the gcc-8-branch. Closes: #901290.
   * Fix build failure on hurd-i386. Closes: #898901.
Checksums-Sha1:
 e806104c4eaaee11214229f4cf6cceb3de1b974e 24107 gcc-6_6.4.0-18.dsc
 b110b5ba4bbefe4bd4d2e9d63dfdf4f3ae02696c 1886104 gcc-6_6.4.0-18.diff.gz
 478a1f7ba63160f36072623b12e516af906bacc1 9117 gcc-6_6.4.0-18_source.buildinfo
Checksums-Sha256:
 cf04efff191708f979cb994f1a63b60c81b06dbf179df692b64fff85b79f9010 24107 
gcc-6_6.4.0-18.dsc
 30c785fd9afeb584af70eca7e2b74ed43cdcbf610be67cee04cdb856d8657f5a 1886104 
gcc-6_6.4.0-18.diff.gz
 d2d7dc1b9c7b27bd533493ce327d59eb2d08014a34d08bcefaae5607aab5077c 9117 
gcc-6_6.4.0-18_source.buildinfo
Files:
 524909730a880f9eaca3151811bcd190 24107 devel optional gcc-6_6.4.0-18.dsc
 7f8cf9c775e440e6fbe737643b8fc67d 1886104 devel optional gcc-6_6.4.0-18.diff.gz
 68a32dd9798ac5921d1a39fd8845c631 9117 devel optional 
gcc-6_6.4.0-18_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAlsjtxMQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9aJjD/4hp0AHaonAD9zLUd4cYN9mowz3pjVY5K/d
6Yjfk9WgUGfo37XpbjzesN4MDPyfskYDGkh02JZ7Jucp4LgkjCBuuSspQXxWIUdy
u4Oqe9Azy7FqsJlh7+fx/rZuAihkLvuYYdIka7fbtv8UDYjaORbxLREp+b20Y/mM
kfS1Ckl0rU41EPLZ38qWSJcWKfbfYp2A7Xu8/kOhFomA8b7dfLMpkLq8hvmwuvnT
pUN7g1U8ernvT+r0FcQU1aMJ0kypDlnMxzlMHabONnEgpPhQ4ZIsOAIyQoVMwiyC
SibWYzN6P6mXY/bf4ipPn6MldWUExHbJ+YYuPUVN/vorQL59v4HEJJ7+c3w5uoy6
6CM7H/j0nmrmOosm1xZoApOzmQwuoIJnvHtwH4rgADM3rb5b4D15RnleLWeWk3hL
0zOW5Z+X16YvtDyIESiz3Nt5qdOzOpcUplUYQ+718er+aeDXad8KwztmdkaZBie6
sTTDAJTfHUwIHW2OYOy90BE29aBvGfSpQSRZLM5NCxfF28Yq2A34S5k54dcTWp+4
/7JGGVRsIgvZNflmLXA1ywvQCtJomSdagKuvcD0W8iStJyA9CzAJIeVPONXzZmz7
VoacH1n6z5WsXZaWERQvN6ObZDb8fHSLFJbEu7dArxpCg+ua5U3/bA7PDUBRbbrT
NCL26WVW5w==
=1ai7
-END PGP SIGNATURE End Message ---

Bug#892995: systemtap: failes to compile scripts, implicit declaration of some functions

[Ritesh Raj Sarraf]

Hello Emanuele,

On Fri, 2018-04-06 at 09:13 +0200, Emanuele Rocca wrote:
> Note that the failure is due to stapbpf/Makefile.am trying to add the
> stapusr group, and the systemtap Debian package does that in
> systemtap-runtime's postinst script already.
> 
> Perhaps it would make sense to patch stapbpf/Makefile.am to get rid
> of
> install-exec-hook, and add a dpkg-statoverride call to
> systemtap-runtime.postinst for the stapbpf binary?

Sorry for the late follow-up. I have made changes based on your
suggestion. An upload to the archive will follow soon.


Thanks,
Ritesh

-- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System

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

Bug#901575: marked as done (ln: '/usr/share/emacs/site-lisp/dictionaries-common/debian-ispell.el' and './debian-ispell.el' are the same file)

[Debian Bug Tracking System]

Your message dated Fri, 15 Jun 2018 12:50:02 +
with message-id 
and subject line Bug#901575: fixed in dictionaries-common 1.27.6
has caused the Debian Bug report #901575,
regarding ln: '/usr/share/emacs/site-lisp/dictionaries-common/debian-ispell.el' 
and './debian-ispell.el' are the same file
to be marked as done.

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

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


-- 
901575: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901575
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dictionaries-common
Version: 1.27.5
Severity: grave

Setting up dictionaries-common (1.27.5) ...
Install emacsen-common for emacs
emacsen-common: Handling install of emacsen flavor emacs
Install dictionaries-common for emacs
install/dictionaries-common: Byte-compiling for emacsen flavour emacs
ln: '/usr/share/emacs/site-lisp/dictionaries-common/debian-ispell.el' and 
'./debian-ispell.el' are the same file
ERROR: install script from dictionaries-common package failed
dpkg: error processing package dictionaries-common (--configure):
 installed dictionaries-common package post-installation script subprocess 
returned error exit status 1
Processing triggers for man-db (2.8.3-2) ...
Errors were encountered while processing:
 dictionaries-common
E: Sub-process /usr/bin/dpkg returned an error code (1)
--- End Message ---
--- Begin Message ---
Source: dictionaries-common
Source-Version: 1.27.6

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

Debian distribution maintenance software
pp.
Agustin Martin Domingo  (supplier of updated 
dictionaries-common package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 15 Jun 2018 14:20:01 +0200
Source: dictionaries-common
Binary: dictionaries-common dictionaries-common-dev
Architecture: source all
Version: 1.27.6
Distribution: unstable
Urgency: medium
Maintainer: Agustin Martin Domingo 
Changed-By: Agustin Martin Domingo 
Description:
 dictionaries-common - spelling dictionaries - common utilities
 dictionaries-common-dev - spelling dictionaries - developer files
Closes: 901575
Changes:
 dictionaries-common (1.27.6) unstable; urgency=medium
 .
   * Revert "debian/emacsen-*: No longer fail for plain 'emacs' flavour in
 preparation for unversioned emacs packages." (Closes: #901575).
Checksums-Sha1:
 c7494e45992fb3a589c9e29084451d388fc5cae2 1869 dictionaries-common_1.27.6.dsc
 a761fb5e9191200daa0b2be714147f4602e5c5d8 361666 
dictionaries-common_1.27.6.tar.gz
 9343bd5b292c9585cf8358a8c8597fb2b34f3067 143696 
dictionaries-common-dev_1.27.6_all.deb
 fe6e6ee2424d7958d877da8216873b91492d7093 237672 
dictionaries-common_1.27.6_all.deb
 dcc6d37bff3eec02876825746189d81d78c3c78b 6556 
dictionaries-common_1.27.6_amd64.buildinfo
Checksums-Sha256:
 29efc9150dedbaf206bc9178a0a866d320e14889fd0fc61af1064e0a64074402 1869 
dictionaries-common_1.27.6.dsc
 623e104288d4248812e06d0750004f4f1264df8e442aeb84f5bc4a581bd9f4e9 361666 
dictionaries-common_1.27.6.tar.gz
 28be72d10125dff7ae093bc06b3bec26ca5d571a76f9794378383022f98f6cdb 143696 
dictionaries-common-dev_1.27.6_all.deb
 5360537737748c2318e4fc6a6b1956eec46e813c90475e04383913e11fe544b4 237672 
dictionaries-common_1.27.6_all.deb
 8907a99dea071e6e61f583cf03e5c72227d63ef23f4959c6073a94c0aee571be 6556 
dictionaries-common_1.27.6_amd64.buildinfo
Files:
 5194ea52135a31d1b48ab21757dc668d 1869 text optional 
dictionaries-common_1.27.6.dsc
 556e3b494451149387082f5c0f1b1902 361666 text optional 
dictionaries-common_1.27.6.tar.gz
 1bd122499d4bf0703430c37be057e0ce 143696 devel extra 
dictionaries-common-dev_1.27.6_all.deb
 8f42af1f5106913515f42e41a43b9a79 237672 text optional 
dictionaries-common_1.27.6_all.deb
 6b8bab5bd7339298f514e85ff00a3510 6556 text optional 
dictionaries-common_1.27.6_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEEehey7p+gYd346SEFJrCLeiggvwFAlsjsIMACgkQFJrCLeig
gvyQZBAAtNILSIkxQxApAszxt2mr7aWq/ngK+HetmLXrrUNzTKov0IZQ9G6xnKA5
j8cmUaeuAWzua8Pv3KyTN2P7tpH5lMdoaRKxaW65QzKRhRJu3NEtECzU4PLzE6YO

Bug#899709: marked as done (targetcli-fb: Invalid maintainer address linux-target-packag...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Fri, 15 Jun 2018 11:57:38 +
with message-id 
and subject line Bug#899709: fixed in targetcli-fb 2.1.43-2
has caused the Debian Bug report #899709,
regarding targetcli-fb: Invalid maintainer address 
linux-target-packag...@lists.alioth.debian.org
to be marked as done.

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

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


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

Dear uploader of targetcli-fb,

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

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

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

Your options:

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

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

  More information about the new service can be found here:
  

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


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

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

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

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: targetcli-fb
Source-Version: 2.1.43-2

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

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

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

Debian distribution maintenance software
pp.
Ritesh Raj Sarraf  (supplier of updated targetcli-fb 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: Fri, 15 Jun 2018 17:14:27 +0545
Source: targetcli-fb
Binary: targetcli-fb
Architecture: source all
Version: 2.1.43-2
Distribution: unstable
Urgency: medium
Maintainer: Debian LIO Target Packagers 
Changed-By: Ritesh Raj Sarraf 
Description:
 targetcli-fb - Command shell for managing the Linux LIO kernel target
Closes: 858459 899709
Changes:
 targetcli-fb (2.1.43-2) unstable; urgency=medium
 .
   [ Christian Seiler ]
   * Make sure old config backup directory exists. (Closes: #858459)
 .
   [ Christophe Vu-Brugier ]
   * d/watch: fix the watch file to download from GitHub
   * d/watch: remove "fb" from the version number
 .
   [ Ritesh Raj Sarraf ]
   * Switch packaging to Salsa
   * Set maintainer address to tracker (Closes: #899709)
Checksums-Sha1:
 9744bc2a6e73a37d6ba1be4dd0b3d8d4e3395b20 2177 targetcli-fb_2.1.43-2.dsc
 867c161113691c1581b504c591355275968f1552 4968 
targetcli-fb_2.1.43-2.debian.tar.xz
 b07e29ac852d2fc8022b887b93f373749034da0d 27964 targetcli-fb_2.1.43-2_all.deb
 21704342639f5069520c8ab862c7ebc22b771997 6560 
targetcli-fb_2.1.43-2_amd64.buildinfo
Checksums-Sha256:
 34e753d4ebb0764288c9f90079b90eded43fd7b389e4a303273ee4630d3b9110 2177 
targetcli-fb_2.1.43-2.dsc
 

Bug#898902: marked as done (libgpars-groovy-java: FTBFS with Java 10 due to javadoc issue)

[Debian Bug Tracking System]

Your message dated Fri, 15 Jun 2018 11:56:25 +
with message-id 
and subject line Bug#898902: fixed in libgpars-groovy-java 1.2.1-9
has caused the Debian Bug report #898902,
regarding libgpars-groovy-java: FTBFS with Java 10 due to javadoc issue
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.)


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

libgpars-groovy-java fails to build with Java 10 due to a javadoc issue:

  Starting process 'command '/usr/lib/jvm/java-10-openjdk-amd64/bin/javadoc''. 
Working directory: /build/1st/libgpars-groovy-java-1.2.1 Command: 
/usr/lib/jvm/java-10-openjdk-amd64/bin/javadoc 
@/build/1st/libgpars-groovy-java-1.2.1/build/tmp/javadoc/javadoc.options
  Successfully started process 'command 
'/usr/lib/jvm/java-10-openjdk-amd64/bin/javadoc''
  javadoc: error - Error fetching URL: file:/usr/share/doc/default-jdk/api/
  javadoc: warning - You have not specified the version of HTML to use.
  The default is currently HTML 4.01, but this will change to HTML5
  in a future release. To suppress this warning, please specify the
  version of HTML used in your documentation comments and to be
  generated by this doclet, using the -html4 or -html5 options.
  1 error
  1 warning
--- End Message ---
--- Begin Message ---
Source: libgpars-groovy-java
Source-Version: 1.2.1-9

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

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

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated libgpars-groovy-java 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 15 Jun 2018 13:38:21 +0200
Source: libgpars-groovy-java
Binary: libgpars-groovy-java libgpars-groovy-java-doc
Architecture: source
Version: 1.2.1-9
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 libgpars-groovy-java - open-source concurrency library for Groovy
 libgpars-groovy-java-doc - documentation for libgpars-groovy-java
Closes: 898902
Changes:
 libgpars-groovy-java (1.2.1-9) unstable; urgency=medium
 .
   * Team upload.
   * Build depend exclusively on default-jdk (Closes: #898902)
Checksums-Sha1:
 3fd67e60db748edd555ec20af7c854b74ebe8a5f 2281 libgpars-groovy-java_1.2.1-9.dsc
 dbc2435598b4f0265e5bdae24338040d19261627 5700 
libgpars-groovy-java_1.2.1-9.debian.tar.xz
 42b4645ef91b20cc90394eada3514303b4c7a0cb 14977 
libgpars-groovy-java_1.2.1-9_source.buildinfo
Checksums-Sha256:
 6ec62fa9824a1966a8085cc9290f0e5a98eb2c614030cbeda5585df4faedff70 2281 
libgpars-groovy-java_1.2.1-9.dsc
 e16546c95bc53141d0646081c074a3159ad6ecdff7bcecd225283106a44a7725 5700 
libgpars-groovy-java_1.2.1-9.debian.tar.xz
 ab618a0ee311fab47bde075431b406e9f1378255fa07f5a058dccb945b9532c4 14977 
libgpars-groovy-java_1.2.1-9_source.buildinfo
Files:
 55e36334d1769f0df2e171855275d23d 2281 java optional 
libgpars-groovy-java_1.2.1-9.dsc
 d087060b639923f89b77837ed43dc55a 5700 java optional 
libgpars-groovy-java_1.2.1-9.debian.tar.xz
 7d4874b81ff3362f5ce7c2607544 14977 java optional 
libgpars-groovy-java_1.2.1-9_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAlsjpUASHGVib3VyZ0Bh
cGFjaGUub3JnAAoJEPUTxBnkudCsFhEQAIKfFmoEKJPl9Smd4fXHyOBxsfD2LG+u
ySExBfR55yg40qpOwTIcOVCXSPjhcBQNSdN8q3kZ6EauW59SRXLB3kQOsfgGDEeQ
HlLZSttwbmHZb9apYv+bL8PyUwCwk4STSVv1LXM7oaAKHxTZnuoXb+r4ou1eN5xu
yaWQayXzO5mnsbIFgdD9rrLYek3qkO2XiQelTadX6fvO7h1EREGk/aj+q1UgRGuW
nrsAClAr12RnKhKqL8P6QwZxRuaIOzGnuiJzcU0ZNgrZdk6hQIH+QZ7lbCg2Fe0D
9QE5voLBT2aGp8+pGUFbt0EjjNdGiwyyPNFnAn9cKM/jLXJh+NKolFoCLTgoN64x
8qdWkf7P0klaXfNulIScZfpPVyfA8kGfgB/PzibEwQVJydzLPnZc6VAplU0zNWGJ
kvYXY01UO7Nek0UPjqFgnbLWAb/CMN6WG9cWCNWOzJ9mJSHdT1PDrQg2husf0H1F
emjxLSKNjif1zNbRsycLeqSWiyeNDBN0aCOV83QitV17VhsTaZFEgXi7HAJYne0S
bBHN3z1wYQH0whRT8l2iNgvpH/2BNwJTP2ycp2Gxw0BNQKSTFO+70VQmk5ILKbe3

Bug#899672: marked as done (python-configshell-fb: Invalid maintainer address linux-target-packag...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Fri, 15 Jun 2018 11:57:01 +
with message-id 
and subject line Bug#899672: fixed in python-configshell-fb 1.1.20-2
has caused the Debian Bug report #899672,
regarding python-configshell-fb: Invalid maintainer address 
linux-target-packag...@lists.alioth.debian.org
to be marked as done.

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

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


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

Dear uploader of python-configshell-fb,

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

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

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

Your options:

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

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

  More information about the new service can be found here:
  

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


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

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

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

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: python-configshell-fb
Source-Version: 1.1.20-2

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

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

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

Debian distribution maintenance software
pp.
Christophe Vu-Brugier  (supplier of updated 
python-configshell-fb package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 14 Jun 2018 19:31:18 +0200
Source: python-configshell-fb
Binary: python-configshell-fb python3-configshell-fb python-configshell-fb-doc
Architecture: source all
Version: 1.1.20-2
Distribution: unstable
Urgency: medium
Maintainer: Linux Block Storage Team 
Changed-By: Christophe Vu-Brugier 
Description:
 python-configshell-fb - Python library for building configuration shells - 
Python 2
 python-configshell-fb-doc - Python library for building configuration shells - 
doc
 python3-configshell-fb - Python library for building configuration shells - 
Python 3
Closes: 899672 901484
Changes:
 python-configshell-fb (1.1.20-2) unstable; urgency=medium
 .
   [ Christophe Vu-Brugier ]
   * d/watch: fix the watch file to download from GitHub
   * d/watch: remove "fb" from the version number
   * d/control: Set Vcs-Git and Vcs-Browser to salsa.debian.org
   * d/control: update maintainer email address
   * d/patches: apply upstream patches to fix a "readline not defined"
 bug (Closes: #901484)
 .
   [ Ritesh Raj Sarraf ]
   * Set maintainer email address to the tracker one (Closes: #899672)
Checksums-Sha1:
 

Bug#899365: [Pkg-mozext-maintainers] Bug#899365: Same thing

[Michael Meskes]

> I have the same problem: the extension does not show up in the
> extension 
> list in Firefox.
> 
> Do you know how to debug?

what do you want to debug? The report gives a *reason* for this
behavior. 

However, I've had reports that this bug should only result in a warning
but haven't found time to look into it so far. If you mean that, be my
guest.

Michael
-- 
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org
Jabber: michael at xmpp dot meskes dot org
VfL Borussia! Força Barça! SF 49ers! Use Debian GNU/Linux, PostgreSQL

Bug#898902: Bug #898902 in libgpars-groovy-java marked as pending

[ebourg]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/java-team/libgpars-groovy-java/commit/c32c00769e79bb41302200d9603dc9370209782b


Build depend exclusively on default-jdk (Closes: #898902)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/898902

Processed: Bug #898902 in libgpars-groovy-java marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #898902 [src:libgpars-groovy-java] libgpars-groovy-java: FTBFS with Java 10 
due to javadoc issue
Added tag(s) pending.

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

Bug#896836: marked as done (ktexteditor: CVE-2018-10361: ktexteditor privilege escalation)

[Debian Bug Tracking System]

Your message dated Fri, 15 Jun 2018 11:22:25 +
with message-id 
and subject line Bug#896836: fixed in ktexteditor 5.47.0-1
has caused the Debian Bug report #896836,
regarding ktexteditor: CVE-2018-10361: ktexteditor privilege escalation
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.)


-- 
896836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896836
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ktexteditor
Version: 5.37.0-2
Severity: grave
Tags: security upstream

Hi

See http://www.openwall.com/lists/oss-security/2018/04/24/1 for
details (and proposed patch).

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: ktexteditor
Source-Version: 5.47.0-1

We believe that the bug you reported is fixed in the latest version of
ktexteditor, 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.
Maximiliano Curia  (supplier of updated ktexteditor 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: Fri, 15 Jun 2018 12:10:22 +0200
Source: ktexteditor
Binary: ktexteditor-data ktexteditor-katepart libkf5texteditor-bin 
libkf5texteditor-dev libkf5texteditor-doc libkf5texteditor5
Architecture: source
Version: 5.47.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian/Kubuntu Qt/KDE Maintainers 
Changed-By: Maximiliano Curia 
Description:
 ktexteditor-data - provide advanced plain text editing services
 ktexteditor-katepart - provide advanced plain text editing services
 libkf5texteditor-bin - provide advanced plain text editing services (binaries)
 libkf5texteditor-dev - provide advanced plain text editing services
 libkf5texteditor-doc - provide advanced plain text editing services 
(documentation)
 libkf5texteditor5 - provide advanced plain text editing services
Closes: 896836
Changes:
 ktexteditor (5.47.0-1) unstable; urgency=medium
 .
   * New upstream release (5.47.0).
   * Update build-deps and deps with the info from cmake
   * CVE-2018-10361: privilege escalation (Closes: 896836)
   * Release to unstable
Checksums-Sha1:
 8ad267366f79b7a7123f92876bc1462502ada561 3136 ktexteditor_5.47.0-1.dsc
 a5813f552e08c32e129b59471c41375dd0bb0cdd 2297056 ktexteditor_5.47.0.orig.tar.xz
 dec994c73303408532f17a6b752adf129eeaa3fa 25176 
ktexteditor_5.47.0-1.debian.tar.xz
 e574c503fc82bb151c4b0913d1f23dac7562512c 15086 
ktexteditor_5.47.0-1_source.buildinfo
Checksums-Sha256:
 1a7cac5ef004acb60f3ed8a98c93add37ca339a5e247b0acf3cac2dc3a98ff45 3136 
ktexteditor_5.47.0-1.dsc
 6b4ae2ea3c00dd2d7dc4c53f7760c750f8fee8aece4bcbc938064cadd34c08cc 2297056 
ktexteditor_5.47.0.orig.tar.xz
 178e44d8321f0c4cdcd3dc211b853bc8d0804068af19f48f0328a1007a25d5cd 25176 
ktexteditor_5.47.0-1.debian.tar.xz
 e42e57f5682c95cc25f897d826e841af20144564d5e90b73d220b884734bf390 15086 
ktexteditor_5.47.0-1_source.buildinfo
Files:
 704868ab3d406adf565b09435958394b 3136 libs optional ktexteditor_5.47.0-1.dsc
 ebf18cbfa331190fdce9ecb1f23877aa 2297056 libs optional 
ktexteditor_5.47.0.orig.tar.xz
 2b1d4fecb1f00a4593638b9a90c1e84d 25176 libs optional 
ktexteditor_5.47.0-1.debian.tar.xz
 3b52cae5115b4a68d3994677f8af0f5f 15086 libs optional 
ktexteditor_5.47.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE+JIdOnQEyG4RNSIVxxl2mbKbIyoFAlsjnN0ACgkQxxl2mbKb
Iyp9ow//baPviS1k4GLz50bPFT1a2fxWg8xthVdhbbMvalisVWlA9grTIQ86EcLb
88kYYlIJcgFl7rO8YZhrnJTAgtCxGyS17dK1qVWvA37XAD35Weam8SWvpxJtsihq
G1m95FGMXiP34f3PHlfm1lZ2cyAJQjaKOb8xjFm1ZS2XD4mxmhORd9j62AMCBlq0
54ec7ZHh0VEOicSbmSeJ87/ukEzAsFd1EH0SfkBwIk23Q5wESwxVDu+oWAaEgTur
1MDt5r5E16Qnwj2ytviXTFCaIA0PWMsvH1ha1fGmp6XdxJaYHS1PZSSE9yJmhdwW
ewgvGVLpqm0EgARo/5/mUZsL9EvoSWI0O+5SJ18R8YSPS23foZNH/0lIVHJICxJk
ug8sv//hwFquUpIymfptfpAfYqK60hLkXbT5Mqg48er7DWETpFD7BuQ51JZJ5d+C
iFrIJNwCZL2/Anr1hU3zxfAMkx9PgnClTuuSknVEzlJ81Mv9bLqE7qFmmqgXZba3
z4GFEf3EXWbgIDVsEDYL9c9tYjPs/78hP36Nd+dG3eewWMZlqEHFJVjFKpno1jbo
3/xbqErYeNx0RRwOzMMaee/xau74vGOK+Ze0mAvJzPybQTh4dcJDoOa+lR7T4jkx
/i/D/HQLmyWGc2Tw13IvuP8gMxBxx6KR7ZyqzMqFMYikG66CNjM=
=8vYm
-END PGP SIGNATURE End Message ---

Processed: tagging 901575

[Debian Bug Tracking System]

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

> tags 901575 + confirmed
Bug #901575 [dictionaries-common] ln: 
'/usr/share/emacs/site-lisp/dictionaries-common/debian-ispell.el' and 
'./debian-ispell.el' are the same file
Added tag(s) confirmed.
> thanks
Stopping processing here.

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

Bug#901601: python3-venv: Please remove python3-venv from archive

[Salvo Tomaselli]

Package: python3-venv
Version: 3.6.5-3
Severity: grave
Justification: renders package unusable

Dear Maintainer,

the manpage for the module states:
>   pyvenv-3.3 - create virtual python environments

However, currently, it can't do that because of this:

> The virtual environment was not created successfully because ensurepip is not
> available.  On Debian/Ubuntu systems, you need to install the python3-venv
> package using the following command.
>
> apt-get install python3-venv
>
> You may need to use sudo with that command.  After installing the python3-venv
> package, recreate your virtual environment.

But the issue is tagged as wontfix here: #816740

This means that the package is and will forever be totally useless, since it is
meant to create virtual environments and it cannot do so.

So please just drop it from archive, because there is no point in it existing.

Best


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

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

Versions of packages python3-venv depends on:
ii  python33.6.5-3
ii  python3-distutils  3.6.5-4
ii  python3.6-venv 3.6.6~rc1-1

python3-venv recommends no packages.

python3-venv suggests no packages.

-- no debconf information

Processed: Re: [Pkg-emacsen-addons] Bug#901564: cider: autopkgtest needs update for changes by clojure-mode/5.7.0-1

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 899124
Bug #901564 [src:cider] cider: autopkgtest needs update for changes by 
clojure-mode/5.7.0-1
901564 was not blocked by any bugs.
901564 was not blocking any bugs.
Added blocking bug(s) of 901564: 899124

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

Bug#901600: firefox: Please add the ffmpeg libraries as direct dependencies

[jim_p]

Package: firefox
Version: 60.0.2-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

So, a few days ago, apt autoremoved ffmpeg's libraries (libavcodec57,
libavdevice57, libavfilter6, libavformat57, libavutil55, libswresample2,
libswscale4 and a couple more) because they were no longer needed by any
package.
Actually, they were direct dependencies of chromium up to 67.0.3396.79-1, and,
after the upgrade to 67.0.3396.79-2, which makes chromium use its embedded
ffmpeg code, so they are no longer needed.

However, it seems that firefox also uses them for its html5 support, e.g. h264
video playback. And without them, firefox either switches to flash on sites
that do have flash as a fallback option, which is patheric in terms of
performance, or does not play the relevant media at all and pops up a message
like "unsuppored file format" or something. When lauched from a terminal, this
message comes up

 $ firefox
[Parent 19225, Gecko_IOThread] WARNING: pipe error (120): Connection reset by
peer: file
/build/firefox-6iUvb9/firefox-60.0.2/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
line 353

Reinstalling the above libraries brings back that precious html5 support, so
please make them as direct dependencies.

All of the above apply to firefox-esr of experimental as well, so please update
that package as well.

Thank you in advance.



-- Package-specific info:


-- Addons package information

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

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

Versions of packages firefox depends on:
ii  debianutils   4.8.6
ii  fontconfig2.13.0-5
ii  libatk1.0-0   2.28.1-1
ii  libc6 2.27-3
ii  libcairo-gobject2 1.15.10-3
ii  libcairo2 1.15.10-3
ii  libdbus-1-3   1.12.8-2
ii  libdbus-glib-1-2  0.110-2
ii  libevent-2.1-62.1.8-stable-4
ii  libffi6   3.2.1-8
ii  libfontconfig12.13.0-5
ii  libfreetype6  2.8.1-2
ii  libgcc1   1:8.1.0-5
ii  libgdk-pixbuf2.0-02.36.11-2
ii  libglib2.0-0  2.56.1-2
ii  libgtk-3-03.22.29-3
ii  libhunspell-1.6-0 1.6.2-1+b1
ii  libjsoncpp1   1.7.4-3
ii  libnspr4  2:4.19-3
ii  libnss3   2:3.37.1-1
ii  libpango-1.0-01.42.0-1
ii  libsqlite3-0  3.24.0-1
ii  libstartup-notification0  0.12-5
ii  libstdc++68.1.0-5
ii  libvpx5   1.7.0-3
ii  libx11-6  2:1.6.5-1
ii  libx11-xcb1   2:1.6.5-1
ii  libxcb-shm0   1.13-1
ii  libxcb1   1.13-1
ii  libxcomposite11:0.4.4-2
ii  libxdamage1   1:1.1.4-3
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.15-2
ii  zlib1g1:1.2.11.dfsg-1

firefox recommends no packages.

Versions of packages firefox suggests:
pn  fonts-lmodern  
pn  fonts-stix | otf-stix  
ii  libcanberra0   0.30-6
ii  libgssapi-krb5-2   1.16-2
ii  libgtk2.0-02.24.32-1

-- no debconf information

Processed: Re: Bug#901592: wicd-daemon: please remove the vulnerable dhcpcd5 from the OR'ed dependencies

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #901592 [wicd-daemon] wicd-daemon: please remove the vulnerable dhcpcd5 
from the OR'ed dependencies
Severity set to 'important' from 'serious'
> retitle -1 wicd-daemon: please don't list the vulnerable dhcpcd5 first in the 
> OR'ed dependencies
Bug #901592 [wicd-daemon] wicd-daemon: please remove the vulnerable dhcpcd5 
from the OR'ed dependencies
Changed Bug title to 'wicd-daemon: please don't list the vulnerable dhcpcd5 
first in the OR'ed dependencies' from 'wicd-daemon: please remove the 
vulnerable dhcpcd5 from the OR'ed dependencies'.

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

Bug#901592: wicd-daemon: please remove the vulnerable dhcpcd5 from the OR'ed dependencies

[Axel Beckert]

Control: severity -1 important
Control: retitle -1 wicd-daemon: please don't list the vulnerable dhcpcd5 first 
in the OR'ed dependencies

Hi,

Vincent Lefevre wrote:
> Due to bug 852343, wicd-daemon now depends on
> 
>   dhcpcd5 | isc-dhcp-client | pump | udhcpc

Hrm. That bug report never has been closed. Ah, no, you were wrong:
It's not due to #852343 (which is indeed still open), but due to
#783272.

> but dhcpcd5 has been vulnerable since at least 2014:
> 
>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846938
> 
> (dhcpcd5: CVE-2014-7913). And as a consequence, wicd has now been
> removed from testing:
> 
>   https://tracker.debian.org/news/965137/wicd-removed-from-testing/

For some reason unclear to me, it migrated back to testing less than a
day later:

https://packages.qa.debian.org/w/wicd/news/20180615T043913Z.html

Found no according hint in
https://release.debian.org/britney/hints/ and the bug has neither been
fixed nor has been dhcpcd5 removed from Debian.

> The unnecessary dependency on dhcpcd5 should be removed.

I disagree: Neither should the dependency be removed no is it
unnecessary.

In contrary: It would be a policy violation if I (just) remove that
dependency because wicd _has_ a relation with dhcpcd5 and hence
requires a package relation with it. And already alone because of that
it is surely not RC.

The only thing I likely will change in wicd is to not keep dhcpcd5 as
first of the alternative list of DHCP client dependencies, but move
isc-dhcp-client to the first position.

Retitling the bug report accordingly and lowering the severity.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Processed: reassign 846938 to dhcpcd5, found 846938 in 6.0.5-2, found 846938 in 6.10.1-1

[Debian Bug Tracking System]

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

> # reassign from source to binary package, this is not a FTBFS or similar
> reassign 846938 dhcpcd5
Bug #846938 [src:dhcpcd5] dhcpcd5: CVE-2014-7913
Bug reassigned from package 'src:dhcpcd5' to 'dhcpcd5'.
No longer marked as found in versions dhcpcd5/6.0.5-2 and dhcpcd5/6.10.1-1.
Ignoring request to alter fixed versions of bug #846938 to the same values 
previously set
> found 846938 6.0.5-2
Bug #846938 [dhcpcd5] dhcpcd5: CVE-2014-7913
Marked as found in versions dhcpcd5/6.0.5-2.
> found 846938 6.10.1-1
Bug #846938 [dhcpcd5] dhcpcd5: CVE-2014-7913
Marked as found in versions dhcpcd5/6.10.1-1.
> thanks
Stopping processing here.

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

Processed: Re: fix build failure with libcdio-2.0

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #901530 [src:fuse-umfuse-iso9660] fix build failure with libcdio-2.0
Severity set to 'serious' from 'normal'
> tags -1 + sid buster
Bug #901530 [src:fuse-umfuse-iso9660] fix build failure with libcdio-2.0
Added tag(s) buster and sid.

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

Bug#899365: Same thing

[Eugen Dedu]

Hi,

I have the same problem: the extension does not show up in the extension 
list in Firefox.


Do you know how to debug?

Cheers,
--
Eugen

Bug#901592: wicd-daemon: please remove the vulnerable dhcpcd5 from the OR'ed dependencies

[Vincent Lefevre]

Package: wicd-daemon
Version: 1.7.4+tb2-6
Severity: serious
Tags: security

Due to bug 852343, wicd-daemon now depends on

  dhcpcd5 | isc-dhcp-client | pump | udhcpc

but dhcpcd5 has been vulnerable since at least 2014:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846938

(dhcpcd5: CVE-2014-7913). And as a consequence, wicd has now been
removed from testing:

  https://tracker.debian.org/news/965137/wicd-removed-from-testing/

--
FYI: The status of the wicd source package
in Debian's testing distribution has changed.

  Previous version: 1.7.4+tb2-6
  Current version:  (not in testing)
  Hint: 
Bug #846938: dhcpcd5: CVE-2014-7913
# in dhcpcd5
--

The unnecessary dependency on dhcpcd5 should be removed.

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

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

Versions of packages wicd-daemon depends on:
ii  adduser   3.117
ii  dbus  1.12.8-3
ii  debconf   1.5.67
ii  iputils-ping  3:20161105-1
ii  isc-dhcp-client   4.3.5-4
ii  lsb-base  9.20170808
ii  psmisc23.1-1+b1
ii  python2.7.15-3
ii  python-dbus   1.2.8-2
ii  python-gobject-2  2.28.6-13+b1
ii  python-wicd   1.7.4+tb2-6+local1
ii  wireless-tools30~pre9-12+b1
ii  wpasupplicant 2:2.6-17

Versions of packages wicd-daemon recommends:
ii  rfkill 2.32-0.1
ii  wicd-curses [wicd-client]  1.7.4+tb2-6+local1
ii  wicd-gtk [wicd-client] 1.7.4+tb2-6+local1

Versions of packages wicd-daemon suggests:
pn  pm-utils  

Versions of packages wicd depends on:
ii  wicd-curses [wicd-client]  1.7.4+tb2-6+local1
ii  wicd-gtk [wicd-client] 1.7.4+tb2-6+local1

Versions of packages wicd-gtk depends on:
ii  python 2.7.15-3
ii  python-glade2  2.24.0-5.1+b1
ii  python-gtk22.24.0-5.1+b1

Versions of packages wicd-gtk recommends:
ii  menu   2.1.47+b1
ii  policykit-10.105-20
ii  python-notify  0.1.1-4

Versions of packages wicd-curses depends on:
ii  python2.7.15-3
ii  python-urwid  2.0.1-2

Versions of packages wicd-curses recommends:
ii  sudo  1.8.23-1

Versions of packages python-wicd depends on:
ii  net-tools  1.60+git20161116.90da8a0-2
ii  python 2.7.15-3

Versions of packages python-wicd suggests:
ii  ethtool   1:4.16-1
ii  iproute2  4.16.0-4

-- Configuration Files:
/etc/wicd/encryption/templates/active changed [not included]

-- debconf information excluded

Bug#887382: prevent Clojure 1.9.0 alpha from migrating to testing

[intrigeri]

Hi,

Elana Hashman:
> This alpha version of Clojure 1.9.0 was uploaded to facilitate packaging
> the official 1.9.0 release. As such, I need to prevent it from migrating
> to testing for now.

Now that 1.9.0 final is in sid, shall we close this bug so the
transition to testing can happen?

Cheers,
-- 
intrigeri

Bug#898086: libequinox-osgi-java: Does not install symlinks into /usr/lib/eclipse/plugins

[Giannino Stoppani]

I've issue starting eclipse on sid, but the symlink isn't solving for me.

=== Log file ===
This is the log file:
!SESSION Fri Jun 15 09:10:34 CEST 2018
-
!ENTRY org.eclipse.equinox.launcher 4 0 2018-06-15 09:10:34.504
!MESSAGE Exception launching the Eclipse Platform:
!STACK
java.lang.ClassNotFoundException:
org.eclipse.core.runtime.adaptor.EclipseStarter
at java.base/java.net.URLClassLoader.findClass(URLClassLoader.java:466)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:566)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:499)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:626)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
at org.eclipse.equinox.launcher.Main.main(Main.java:1414)
=== End of log file ===

'eclipse-platform' depends on 'eclipse-platform-data' and 'eclipse-rcp'.
'eclipse-rcp' depends on 'libequinox-osgi-java' >=3.9.1.
'eclipse-platform-data' is configured to expect 'libequinox-osgi-java'
3.8.1 (or better: it expects the 'osgi.framework' version 3.8.1, which is
contained in 'libequinox-osgi-java' 3.8.1).

% apt-cache show eclipse-platform | grep eclipse-platform-data
Replaces: eclipse-platform-data (<< 3.8.1-5)
Depends: ant (>= 1.8.2), ant-optional, default-jre | java5-runtime |
java6-runtime, eclipse-platform-data (>= 3.8.1-11), eclipse-rcp (=
3.8.1-11), java-common (>= 0.23), libcommons-codec-java (>= 1.4-2),
libcommons-httpclient-java (>= 3.1-9), libcommons-logging-java (>=
1.1.1-6), libjetty9-java (>= 9.2.19-2~), libjsch-java (>= 0.1.37-3),
liblucene2-java (>= 2.9.4+ds1-3~), liblucene2-java (<< 2.9.5),
libservlet3.1-java, sat4j (>= 2.3.0), sat4j (<< 2.4.0), gconf-service,
libc6 (>= 2.14), libgconf-2-4 (>= 3.2.5), libglib2.0-0 (>= 2.12.0)

% apt-cache show eclipse-rcp | grep libequinox-osgi-java
Depends: default-jre | java5-runtime | java6-runtime, libequinox-osgi-java
(>= 3.9.1), libfelix-gogo-command-java, libfelix-gogo-shell-java,
libicu4j-49-java (>= 49.1-2), libswt-gtk-3-java (<< 3.9.0~),
libswt-gtk-3-java (>= 3.8.0~), libswt-cairo-gtk-3-jni (>= 3.8.0~),
libswt-webkit-gtk-3-jni (>= 3.8.0~), libc6 (>= 2.14)

% dpkg -L eclipse-platform-data | grep config.ini | xargs cat | grep
osgi.framework=
osgi.framework=file\:plugins/org.eclipse.osgi_3.8.1.dist.jar
osgi.framework=file\:plugins/org.eclipse.osgi_3.8.1.dist.jar