Bug#824827: mixmaster: hold on..

[Anonymous]

Package: mixmaster
Version: 3.0.0-8.1
Followup-For: Bug #824827

Dear Maintainer,

> Mixmaster does not support 4k keys.
> 
> It is not designed to support 4k keys.
> 
> Closing the bug.

Hold on.. even if the project has decided that 1k keys is the way
forward, 2 bugs still remain:

bug 1: mixmaster autonomously chooses to use a (so-called) unsupported
   chain.  If 4k keys are not supported, the tool shouldn't
   attempt to chain through unusable nodes in the first place.

bug 2: the error message "encryption failed" is absurdly vague.  In
the absence of a fix for bug 1, the tool should say something
meaningful like:

  "cannot route through dizum because its keys are too large"

Please reopen.

Note this is my *6th* attempt to send this reply -- I am sending it
using mixmaster.

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

Kernel: Linux 4.9.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=1508766057 WARNING 
torsocks[12002]: [syscall] Unsupported syscall number 217. Denying the call (in 
tsocks_syscall() at syscall.c:488)
UTF-8), LANGUAGE=en_US.UTF-8 (charmap=1508766057 WARNING torsocks[12004]: 
[syscall] Unsupported syscall number 217. Denying the call (in tsocks_syscall() 
at syscall.c:488)
UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages mixmaster depends on:
ii  adduser3.115
ii  debconf [debconf-2.0]  1.5.61
ii  libc6  2.24-11+deb9u1
ii  libmailtools-perl  2.18-1
ii  libncurses56.0+20161126-1+deb9u1
ii  libpcre3   2:8.39-3
ii  libssl1.0.21.0.2l-2
ii  libtinfo5  6.0+20161126-1+deb9u1
ii  libwww-perl6.15-1
ii  zlib1g 1:1.2.8.dfsg-5

Versions of packages mixmaster recommends:
ii  postfix [mail-transport-agent]  3.1.6-0+deb9u1

Versions of packages mixmaster suggests:
ii  mutt  1.7.2-1

-- Configuration Files:
/etc/mixmaster/allpingers.txt changed:
[austria]
base= https://www.tahina.priv.at/~cm/stats/
rlist   = https://www.tahina.priv.at/~cm/stats/rlist.txt
mlist   = https://www.tahina.priv.at/~cm/stats/mlist.txt
rlist2  = https://www.tahina.priv.at/~cm/stats/rlist2.txt
mlist2  = https://www.tahina.priv.at/~cm/stats/mlist2.txt
rlist_html  = https://www.tahina.priv.at/~cm/stats/rlist.html
mlist_html  = https://www.tahina.priv.at/~cm/stats/mlist.html
rlist2_html = https://www.tahina.priv.at/~cm/stats/rlist2.html
mlist2_html = https://www.tahina.priv.at/~cm/stats/mlist2.html
pgpring = https://www.tahina.priv.at/~cm/stats/pgp-all.asc
pgpring_rsa = https://www.tahina.priv.at/~cm/stats/pgp-rsa.asc
mixring = https://www.tahina.priv.at/~cm/stats/pubring.mix
type2list   = https://www.tahina.priv.at/~cm/stats/type2.list
[deuxpi]
base= http://www.deuxpi.ca/echolot/
rlist   = http://www.deuxpi.ca/echolot/rlist.txt
mlist   = http://www.deuxpi.ca/echolot/mlist.txt
rlist2  = http://www.deuxpi.ca/echolot/rlist2.txt
mlist2  = http://www.deuxpi.ca/echolot/mlist2.txt
rlist_html  = http://www.deuxpi.ca/echolot/rlist.html
mlist_html  = http://www.deuxpi.ca/echolot/mlist.html
rlist2_html = http://www.deuxpi.ca/echolot/rlist2.html
mlist2_html = http://www.deuxpi.ca/echolot/mlist2.html
pgpring = http://www.deuxpi.ca/echolot/pgp-all.asc
pgpring_rsa = http://www.deuxpi.ca/echolot/pgp-rsa.asc
mixring = http://www.deuxpi.ca/echolot/pubring.mix
type2list   = http://www.deuxpi.ca/echolot/type2.list
[frell]
base= http://echolot.theremailer.net/
rlist   = http://echolot.theremailer.net/rlist.txt
mlist   = http://echolot.theremailer.net/mlist.txt
rlist2  = http://echolot.theremailer.net/rlist2.txt
mlist2  = http://echolot.theremailer.net/mlist2.txt
rlist_html  = http://echolot.theremailer.net/rlist.html
mlist_html  = http://echolot.theremailer.net/mlist.html
rlist2_html = http://echolot.theremailer.net/rlist2.html
mlist2_html = http://echolot.theremailer.net/mlist2.html
pgpring = http://echolot.theremailer.net/pgp-all.asc
pgpring_rsa = http://echolot.theremailer.net/pgp-rsa.asc
mixring = http://echolot.theremailer.net/pubring.mix
type2list   = http://echolot.theremailer.net/type2.list
[hermetix]
base= http://www.hermetix.org/echolot/
rlist   = http://www.hermetix.org/echolot/rlist.txt
mlist   = http://www.hermetix.org/echolot/mlist.txt
rlist2  = http://www.hermetix.org/echolot/rlist2.txt
mlist2  = http://www.hermetix.org/echolot/mlist2.txt
rlist_html  = http://www.hermetix.org/echolot/rlist.html
mlist_html  = http://www.hermetix.org/echolot/mlist.html
rlist2_html = http://www.hermetix.org/echolot/rlist2.html
mlist2_html = http://www.hermetix.org/echolot/mlist2.html
pgpring = http://www.hermetix.org/echolot/pgp-all.asc
pgpring_rsa = http://www.hermetix.org/echolot/pgp-rsa.asc
mixring = 

Bug#880703: test-suite failure on s390x

[Michael Biebl]

Source: json-glib
Version: 1.4.2-1
Severity: serious
Forwarded: https://gitlab.gnome.org/GNOME/json-glib/issues/28

The test-suite fails on s390x:

 1/14 array   OK   0.01 s
 2/14 boxed   OK   0.01 s
 3/14 builder OK   0.01 s
 4/14 generator   OK   0.01 s
 5/14 gvariantOK   0.01 s
 6/14 invalid OK   0.00 s
 7/14 nodeFAIL 0.01 s
 8/14 object  OK   0.00 s
 9/14 parser  OK   0.01 s
10/14 pathOK   0.01 s
11/14 reader  OK   0.00 s
12/14 serialize-simpleOK   0.00 s
13/14 serialize-complex   OK   0.00 s
14/14 serialize-full  OK   0.00 s

OK:13
FAIL:   1
SKIP:   0
TIMEOUT:0


The output from the failed tests:

 7/14 nodeFAIL 0.01 s

--- command ---
G_TEST_SRCDIR='/<>/json-glib/tests' 
G_TEST_BUILDDIR='/<>/obj-s390x-linux-gnu/json-glib/tests' 
/<>/obj-s390x-linux-gnu/json-glib/tests/node --tap -k
--- stdout ---
# random seed: R02Scd9cf85c8a3182658ed0f0a8ffed8b47
1..27
# Start of nodes tests
ok 1 /nodes/gvalue
# Start of init tests
ok 2 /nodes/init/int
ok 3 /nodes/init/double
ok 4 /nodes/init/boolean
ok 5 /nodes/init/string
ok 6 /nodes/init/null
# End of init tests
# Start of copy tests
ok 7 /nodes/copy/null
ok 8 /nodes/copy/value
ok 9 /nodes/copy/object
# End of copy tests
# Start of get tests
ok 10 /nodes/get/int
ok 11 /nodes/get/double
# End of get tests
# Start of gvalue tests
# Json:ERROR:../json-glib/tests/node.c:235:test_gvalue_autopromotion: assertion 
failed ((float) g_value_get_double () == 3.14159f): (3.14159012 == 
3.14159)
--- stderr ---
**
Json:ERROR:../json-glib/tests/node.c:235:test_gvalue_autopromotion: assertion 
failed ((float) g_value_get_double () == 3.14159f): (3.14159012 == 
3.14159)
---

The full build log is available at 
https://buildd.debian.org/status/fetch.php?pkg=json-glib=s390x=1.4.2-1=1509747369=0


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

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

Bug#880704: bumblebee-nvidia: Upgrading mesa and nvidia drivers with bumblebee-nvidia installed breaks the desktop

[JWM]

Package: bumblebee-nvidia
Version: 3.2.1-16
Severity: grave
Justification: renders package unusable

Dear Maintainer,

My system is a Thinkpad T440p, with both an Intel and an NVIDIA Optimus cards.
On Wednesday, upgrading both the Mesa libraries and the NVIDIA driver broke the
desktop ---i.e., after reboot, the GDM target never showed up due to a Clutter
error.

Synaptic's history shows the following as installed/upgraded/removed on that
day:


Commit Log for Wed Nov  1 08:23:33 2017


Removed the following packages:
libegl1-glvnd-nvidia
libegl1-mesa-dev
libgl1-mesa-glx:i386
libgtk-3-dev
primus
primus-libs-ia32:i386
primus-libs:i386

Upgraded the following packages:
debconf (1.5.63) to 1.5.64
debconf-i18n (1.5.63) to 1.5.64
eog-plugin-map (3.25.92-1) to 3.26.1-1
epiphany-browser (3.24.3-1) to 3.26.1-1
epiphany-browser-data (3.24.3-1) to 3.26.1-1
giada (0.14.1~dfsg1-1) to 0.14.3~dfsg1-1
gir1.2-javascriptcoregtk-4.0 (2.16.6-1) to 2.18.1-1
gir1.2-webkit2-4.0 (2.16.6-1) to 2.18.1-1
gnome-maps (3.25.91-1) to 3.26.1-1
gnome-session (3.24.1-2) to 3.26.1-1
gnome-session-bin (3.24.1-2) to 3.26.1-1
gnome-session-common (3.24.1-2) to 3.26.1-1
gnome-software (3.22.5-1) to 3.26.1-2
gnome-software-common (3.22.5-1) to 3.26.1-2
gnome-software-plugin-flatpak (3.22.5-1) to 3.26.1-2
gstreamer1.0-plugins-bad (1.12.2-1+b1) to 1.12.3-2
libegl-nvidia0 (375.82-5) to 375.82-7
libegl1-mesa (13.0.6-1+b2) to 17.2.3-1
libgbm1 (13.0.6-1+b2) to 17.2.3-1
libgl1-glvnd-nvidia-glx (375.82-5) to 375.82-7
libgl1-mesa-dri (13.0.6-1+b2) to 17.2.3-1
libgl1-mesa-dri:i386 (13.0.6-1+b2) to 17.2.3-1
libgl1-mesa-glx (13.0.6-1+b2) to 17.2.3-1
libgl1-nvidia-glvnd-glx (375.82-5) to 375.82-7
libglapi-mesa (13.0.6-1+b2) to 17.2.3-1
libglapi-mesa:i386 (13.0.6-1+b2) to 17.2.3-1
libgles-nvidia1 (375.82-5) to 375.82-7
libgles-nvidia2 (375.82-5) to 375.82-7
libgles1-glvnd-nvidia (375.82-5) to 375.82-7
libgles1-nvidia (375.82-5) to 375.82-7
libgles2-glvnd-nvidia (375.82-5) to 375.82-7
libgles2-mesa (13.0.6-1+b2) to 17.2.3-1
libgles2-nvidia (375.82-5) to 375.82-7
libglx-nvidia0 (375.82-5) to 375.82-7
libglx0-glvnd-nvidia (375.82-5) to 375.82-7
libgstreamer-plugins-bad1.0-0 (1.12.2-1+b1) to 1.12.3-2
libharfbuzz-dev (1.5.1-1) to 1.6.2-1
libharfbuzz-gobject0 (1.5.1-1) to 1.6.2-1
libharfbuzz-icu0 (1.5.1-1) to 1.6.2-1
libharfbuzz0b (1.5.1-1) to 1.6.2-1
libjavascriptcoregtk-4.0-18 (2.16.6-1) to 2.18.1-1
libnetcdf-c++4 (4.2-7) to 4.2-7+b1
libnvidia-cfg1 (375.82-5) to 375.82-7
libnvidia-eglcore (375.82-5) to 375.82-7
libnvidia-glcore (375.82-5) to 375.82-7
libnvidia-ml1 (375.82-5) to 375.82-7
libosmesa6 (13.0.6-1+b2) to 17.2.3-1
libwayland-egl1-mesa (13.0.6-1+b2) to 17.2.3-1
libwebkit2gtk-4.0-37 (2.16.6-1) to 2.18.1-1
libwebkit2gtk-4.0-37-gtk2 (2.16.6-1) to 2.18.1-1
libxatracker2 (13.0.6-1+b2) to 17.2.3-1
mesa-vdpau-drivers (13.0.6-1+b2) to 17.2.3-1
netcdf-bin (1:4.4.1.1-2) to 1:4.5.0-1
nvidia-alternative (375.82-5) to 375.82-7
nvidia-driver (375.82-5) to 375.82-7
nvidia-driver-bin (375.82-5) to 375.82-7
nvidia-driver-libs (375.82-5) to 375.82-7
nvidia-egl-icd (375.82-5) to 375.82-7
nvidia-kernel-support (375.82-5) to 375.82-7
nvidia-smi (375.82-5) to 375.82-7
nvidia-vdpau-driver (375.82-5) to 375.82-7
nvidia-vulkan-icd (375.82-5) to 375.82-7
primus-libs (0~20150328-4) to 0~20150328-5
xserver-xorg-video-nvidia (375.82-5) to 375.82-7
xwayland (2:1.19.3-2) to 2:1.19.5-1

Installed the following packages:
gir1.2-harfbuzz-0.0 (1.6.2-1)
libegl1 (0.2.999+git20170802-5)
libfwupd2 (1.0.0-4)
libglvnd-core-dev (0.2.999+git20170802-5)
libglvnd0:i386 (0.2.999+git20170802-5)
libglx-mesa0 (17.2.3-1)
libglx-mesa0:i386 (17.2.3-1)
libllvm5.0 (1:5.0~+rc2-1)
libllvm5.0:i386 (1:5.0~+rc2-1)
libnetcdf13 (1:4.5.0-1)
librtmidi4 (3.0.0~ds1-2)
libxcb-xfixes0:i386 (1.12-1)
python3-debconf (1.5.64)




In order to solved the issue, I uninstalled all the NVIDIA-related packages,
reinstalled GDM and blacklisted nouveau.

After that, I tried installing bumblebee-nvidia again, which effectively broke
the system once again.

So it seems the bumblebee-nvidia package is not compatible with the newest mesa
and NVIDIA drivers.




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

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

Versions of packages bumblebee-nvidia depends on:
pn  bumblebee
ii  glx-alternative-nvidia   0.8.0
pn  nvidia-driver | nvidia-legacy-340xx-driver | nvidia-legacy-304xx-dr  

bumblebee-nvidia recommends no packages.

Bug#880702: test-suite failures on i386

[Michael Biebl]

Source: json-glib
Version: 1.4.2-1
Severity: serious
Forwarded: https://gitlab.gnome.org/GNOME/json-glib/issues/27

The test-suite fails on i386:

 1/14 array   FAIL 0.01 s
 2/14 boxed   OK   0.01 s
 3/14 builder OK   0.01 s
 4/14 generator   OK   0.01 s
 5/14 gvariantOK   0.01 s
 6/14 invalid OK   0.01 s
 7/14 nodeFAIL 0.00 s
 8/14 object  OK   0.00 s
 9/14 parser  FAIL 0.00 s
10/14 pathOK   0.01 s
11/14 reader  FAIL 0.00 s
12/14 serialize-simpleOK   0.00 s
13/14 serialize-complex   OK   0.00 s
14/14 serialize-full  OK   0.00 s

OK:10
FAIL:   4
SKIP:   0
TIMEOUT:0


The output from the failed tests:

 1/14 array   FAIL 0.01 s

--- command ---
G_TEST_SRCDIR='/<>/json-glib/tests' 
G_TEST_BUILDDIR='/<>/obj-i686-linux-gnu/json-glib/tests' 
/<>/obj-i686-linux-gnu/json-glib/tests/array --tap -k
--- stdout ---
# random seed: R02S5e6d53faa488d2a4b87a417cf49ed92b
1..4
# Start of array tests
ok 1 /array/empty-array
# Json:ERROR:../json-glib/tests/array.c:40:test_add_element: assertion failed 
(json_array_get_double_element (array, 2) == 3.14): (3.14 == 3.14)
--- stderr ---
**
Json:ERROR:../json-glib/tests/array.c:40:test_add_element: assertion failed 
(json_array_get_double_element (array, 2) == 3.14): (3.14 == 3.14)
---

 7/14 nodeFAIL 0.00 s

--- command ---
G_TEST_SRCDIR='/<>/json-glib/tests' 
G_TEST_BUILDDIR='/<>/obj-i686-linux-gnu/json-glib/tests' 
/<>/obj-i686-linux-gnu/json-glib/tests/node --tap -k
--- stdout ---
# random seed: R02S52f04c643cbae08bdba2de4c7274d1f4
1..27
# Start of nodes tests
ok 1 /nodes/gvalue
# Start of init tests
ok 2 /nodes/init/int
# Json:ERROR:../json-glib/tests/node.c:22:test_init_double: assertion failed 
(json_node_get_double (node) == 3.14159): (3.14159 == 3.14159)
--- stderr ---
**
Json:ERROR:../json-glib/tests/node.c:22:test_init_double: assertion failed 
(json_node_get_double (node) == 3.14159): (3.14159 == 3.14159)
---

 9/14 parser  FAIL 0.00 s

--- command ---
G_TEST_SRCDIR='/<>/json-glib/tests' 
G_TEST_BUILDDIR='/<>/obj-i686-linux-gnu/json-glib/tests' 
/<>/obj-i686-linux-gnu/json-glib/tests/parser --tap -k
--- stdout ---
# random seed: R02Scedda0d35f14df8a2ae97df7062aa61c
1..12
# Start of parser tests
ok 1 /parser/empty-string
# Json:ERROR:../json-glib/tests/parser.c:47:verify_negative_double_value: 
assertion failed (-3.14 == json_node_get_double (node)): (-3.14 == -3.14)
--- stderr ---
**
Json:ERROR:../json-glib/tests/parser.c:47:verify_negative_double_value: 
assertion failed (-3.14 == json_node_get_double (node)): (-3.14 == -3.14)
---

11/14 reader  FAIL 0.00 s

--- command ---
G_TEST_SRCDIR='/<>/json-glib/tests' 
G_TEST_BUILDDIR='/<>/obj-i686-linux-gnu/json-glib/tests' 
/<>/obj-i686-linux-gnu/json-glib/tests/reader --tap -k
--- stdout ---
# random seed: R02Sb9558b796993f6397530a2d5d259b007
1..4
# Start of reader tests
ok 1 /reader/base-array
# Json:ERROR:../json-glib/tests/reader.c:81:test_base_object: assertion failed 
(json_reader_get_double_value (reader) == 42.47): (42.47 == 42.47)
--- stderr ---
**
Json:ERROR:../json-glib/tests/reader.c:81:test_base_object: assertion failed 
(json_reader_get_double_value (reader) == 42.47): (42.47 == 42.47)
---



Full build log at 
https://buildd.debian.org/status/fetch.php?pkg=json-glib=i386=1.4.2-1=1509747453=0



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

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

Bug#879886: [Debian-med-packaging] libhts2: libhts2 needs to handle ABI changes

[Mattia Rizzolo]

On Fri, Nov 03, 2017 at 02:52:11PM -0700, Diane Trout wrote:
> I restored it with git-revert and rebuilt 1.4.1 and 1.5 and discovered
> there were #MISSING# symbols in each rebuild

That's at most to be expected, there was a SONAME bump in the meantime.

> 1.2 -> 1.4.1 had missing symbols but there was a package name &
> soversion bump from libhts1 to libhts2

Exactly.

> There was also symbols removed between 1.4.1 to 1.5 but upstream didn't
> change their SOVERSION.

This is one of the real problem.  So if those symbols that were removed
were actually supposed to be part of a private API and not exported, and
nobody were supposed to try to reach them, then perahps they might be
marked as optional.  But it needs to be evaluated accurately on a
symbol-by-symbols basis.
Personally, from the very quick look I had at them the other day, they
didn't look like some "private API".

> As an aside while I was looking at the missing symbols I found mfprintf
> was still listed in htslib 1.5's cram/mFILE.h, but the implementation
> had been removed from cram/mFILE.c

mh what the..

> Should we be patching the SOVERSION?
> File a bug upstream to have them update SOVERSION?

Depending on the kind of upstream, I'd either try to reach out to them
and see what are their plan for the next release where they could bump
the version, or rename the binary package to get things rebuilt
appropriately (unless we decide to declare those symbols as optional…).



Diane: thank you for dealing with this bug.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Processed: mixmaster bug 824827 grave

[Debian Bug Tracking System]

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

> package mixmaster
Limiting to bugs with field 'package' containing at least one of 'mixmaster'
Limit currently set to 'package':'mixmaster'

> unarchive 824827
Bug #824827 {Done: Colin Tuckley } [mixmaster] Error: 
Encryption failed!
Unarchived Bug 824827
> reopen 824827
Bug #824827 {Done: Colin Tuckley } [mixmaster] Error: 
Encryption failed!
Bug reopened
Ignoring request to alter fixed versions of bug #824827 to the same values 
previously set
> severity 824827 grave
Bug #824827 [mixmaster] Error: Encryption failed!
Severity set to 'grave' from 'important'
> tags 824827 security stretch
Bug #824827 [mixmaster] Error: Encryption failed!
Added tag(s) security and stretch.
> found 824827 3.0
Bug #824827 [mixmaster] Error: Encryption failed!
There is no source info for the package 'mixmaster' at version '3.0' with 
architecture ''
Unable to make a source version for version '3.0'
Marked as found in versions 3.0.
> thanks
Stopping processing here.

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

Bug#880694: myspell-de-de: package is not installable

[Sven Joachim]

Package: myspell-de-de
Version: 20161207-2
Severity: grave

The transitional package myspell-de-de is not installable because its
dependency hunspell-de-de has an unversioned Conflicts with it.  This
very much defeats the purpose of a transitional package. 


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

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

Bug#877191: marked as done (Package is not installing)

[Debian Bug Tracking System]

Your message dated Fri, 3 Nov 2017 19:58:39 -0200
with message-id <20171103195839.1d038dd8d314cec6ac48a...@softwarelivre.org>
and subject line 
has caused the Debian Bug report #877191,
regarding Package is not installing
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.)


-- 
877191: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877191
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-openflow
Version: 2017.2b1
Severity: critical

The package is not installing because it has some code problem.
So, I'm holding it because It can't go to "testing".
I'm already talking to upstream to fix it.

File "/usr/lib/python3/dist-packages/pyof/foundation/basic_types.py", line 459
raise ValueError(f"BinaryData can't be {type(value)} = '{value}'")
^
SyntaxError: invalid syntax

File 
"/usr/lib/python3/dist-packages/pyof/v0x01/controller2switch/packet_out.py", 
line 131
raise ValidationError(f'{self.in_port} is not a valid input port.')
^
SyntaxError: invalid syntax

File "/usr/lib/python3/dist-packages/pyof/v0x04/common/flow_match.py", line 356
raise PackException(f'Match can't unpack "{value}".')
^
SyntaxError: invalid syntax


-- 
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


pgpA1acEafxHG.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
I waited few days and after a dist-upgrade the package was installed without 
problems.
Probably some new feature in python solved the bug.

-- 
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


pgp_ht5rT6ZXh.pgp
Description: PGP signature
--- End Message ---

Bug#877193: marked as done (Package is not installing)

[Debian Bug Tracking System]

Your message dated Fri, 3 Nov 2017 19:48:38 -0200
with message-id <20171103194838.8c93866b71d759ca89188...@softwarelivre.org>
and subject line 
has caused the Debian Bug report #877193,
regarding Package is not installing
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.)


-- 
877193: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877193
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kytos-utils
Version: 2017.2b1
Severity: critical

The package is not installing because it has some code problem.
So, I'm holding it because It can't go to "testing".
I'm already talking to upstream to fix it.

File "/usr/lib/python3/dist-packages/kytos/cli/commands/napps/api.py", line 211
napp_id = f'{user}/{name}'
^
SyntaxError: invalid syntax

-- 
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


pgpl9n9R9zhbT.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
I waited few days and after a dist-upgrade the package was installed without 
problems.
Probably some new feature in python solved the bug.

-- 
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


pgpFpmjJFByR7.pgp
Description: PGP signature
--- End Message ---

Bug#879886: [Debian-med-packaging] libhts2: libhts2 needs to handle ABI changes

[Diane Trout]

> I believe that adding the symbols file back in is the correct
solution.
>  It should allow dpkg-shlibdeps to generate the correct libhst2
> dependencies version.
> 
> Diane
> 
> 

Graham pointed out there was a symbols file from 1.2 that was removed.

I restored it with git-revert and rebuilt 1.4.1 and 1.5 and discovered
there were #MISSING# symbols in each rebuild

1.2 -> 1.4.1 had missing symbols but there was a package name &
soversion bump from libhts1 to libhts2

There was also symbols removed between 1.4.1 to 1.5 but upstream didn't
change their SOVERSION.

As an aside while I was looking at the missing symbols I found mfprintf
was still listed in htslib 1.5's cram/mFILE.h, but the implementation
had been removed from cram/mFILE.c

Should we be patching the SOVERSION? 
File a bug upstream to have them update SOVERSION?

Diane

Bug#880490: tor: Does not start when the AppArmor LSM is enabled but the apparmor package is not installed

[intrigeri]

Viktor Jägersküpper:
> I confirm that with this change tor starts normally without apparmor 
> installed.

Thanks a lot for testing & reporting back!

Bug#880490: tor: Does not start when the AppArmor LSM is enabled but the apparmor package is not installed

[intrigeri]

Hi Laurent,

Laurent Bigonville:
> My 2¢ here. Why is AppArmorProfile even needed here? Shouldn't apparmor 
> figureout
> itself that it need to migrate to the system_tor domain(?)?

Good question, glad you're asking! :)

It's technically doable to have an AppArmor profile that will be
applied to any /usr/bin/tor process automatically. This is actually
how AppArmor is used in the overwhelming majority of cases. But tor is
special in that it is commonly run in different ways:

 - as a system service (instances of tor@.service)
 - run directly by users, which is not so uncommon a use case here

It's not feasible to have a single AppArmor profile cover both cases:
we know what paths the system service will access 99% of the time,
but we cannot possibly guess how a tor run by the user manually
is configured.

IIRC this is why weasel chose this implementation and I fully concur.

Cheers,
-- 
intrigeri

Processed: bug 879002 is not forwarded, tagging 879002

[Debian Bug Tracking System]

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

> notforwarded 879002
Bug #879002 [src:libpam4j] Should the package be removed?
Unset Bug forwarded-to-address
> # added to the wrong bug should have been only for 879001
> tags 879002 - patch upstream
Bug #879002 [src:libpam4j] Should the package be removed?
Removed tag(s) upstream and patch.
> thanks
Stopping processing here.

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

Bug#879001: Bug#879002: Patch for CVE-2017-12197

[Markus Koschany]

Am 03.11.2017 um 21:48 schrieb Salvatore Bonaccorso:
[...]
> It's likely that Red Hat just used the approeach as
> https://github.com/letonez/libpam4j/commit/84f32f4001fc6bdcc125ccc959081de022d18b6d
> and referenced from https://github.com/kohsuke/libpam4j/issues/18 .
> 
> The issue arises because "PAM.authentication() does not call
> pam_acct_mgmt(). As a consequence, the PAM account is not properly
> verified. Any user with a valid password but with deactivated or
> disabled account is able to log in.".
> 
> The above commit should address that.

Hi Salvatore,

Thanks for pointing this out. I asked Red Hat for a clarification
though. It would be interesting to know why this line was commented out
in the first place.

Regards,

Markus



signature.asc
Description: OpenPGP digital signature

Bug#879001: Bug#879002: Patch for CVE-2017-12197

[Salvatore Bonaccorso]

Control: forwarded -1 https://github.com/kohsuke/libpam4j/issues/18
Control: tags -1 + patch upstream

Hi Raphael, Emmanuel and Markus,

On Fri, Nov 03, 2017 at 09:19:56PM +0100, Markus Koschany wrote:
> On Wed, 18 Oct 2017 13:29:19 +0200 Emmanuel Bourg  wrote:
> > Upstream has moved to GitHub [1] and the last update was released in
> > 2014 but the security issue is still not fixed [2].
> > 
> > This was a dependency of Jenkins which is now gone. There is a slim
> > chance that this package could be useful again in the future since it's
> > a dependency of some Apache projects (Zeppelin, Atlas, Ranger and Knox).
> > 
> > Emmanuel Bourg
> > 
> > [1] https://github.com/kohsuke
> > [2] https://github.com/kohsuke/libpam4j/issues/18
> 
> Apparently Red Hat patched their libpam4j package but they didn't
> forward the patch upstream.
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1503103

It's likely that Red Hat just used the approeach as
https://github.com/letonez/libpam4j/commit/84f32f4001fc6bdcc125ccc959081de022d18b6d
and referenced from https://github.com/kohsuke/libpam4j/issues/18 .

The issue arises because "PAM.authentication() does not call
pam_acct_mgmt(). As a consequence, the PAM account is not properly
verified. Any user with a valid password but with deactivated or
disabled account is able to log in.".

The above commit should address that.

Regards,
Salvatore

Processed: Bug#879002: Patch for CVE-2017-12197

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/kohsuke/libpam4j/issues/18
Bug #879002 [src:libpam4j] Should the package be removed?
Set Bug forwarded-to-address to 'https://github.com/kohsuke/libpam4j/issues/18'.
> tags -1 + patch upstream
Bug #879002 [src:libpam4j] Should the package be removed?
Added tag(s) patch and upstream.

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

Processed: Bug#879002: Patch for CVE-2017-12197

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/kohsuke/libpam4j/issues/18
Bug #879001 [src:libpam4j] CVE-2017-12197: libpam4j: Account check bypass
Set Bug forwarded-to-address to 'https://github.com/kohsuke/libpam4j/issues/18'.
> tags -1 + patch upstream
Bug #879001 [src:libpam4j] CVE-2017-12197: libpam4j: Account check bypass
Added tag(s) upstream and patch.

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

Bug#718272: [Pkg-bitcoin-devel] Bug#718272: Bitcoin still not ready for stable release in Debian

[Luke Dashjr]

On Friday 03 November 2017 1:27:24 PM Jonas Smedegaard wrote:
> Quoting Luke Dashjr (2017-11-03 11:25:23)
> 
> > On Friday 03 November 2017 9:10:37 AM you wrote:
> >> I believe Bitcoin is now stable enough for stable release.
> > 
> > Things have only gotten less stable upstream since 2013...
> 
> Please provide references supporting that.

Back in 2013 (0.8.0 release), I was still supporting stable versions 0.4.x 
(originally released in 2011), 0.5.x (OR 2011), 0.6.x (OR 2012), and
0.7.x (OR 2012). No such long-term support is provided anymore - we only 
maintain the most recent 2 versions (with a 6 month release schedule), which 
gives approximately 1 year of support to any particular release.

Furthermore, with increasing miner hostilities to Bitcoin in the last few 
years, the importance of timely deployment of softforks is even more crucial 
to security than previously. This past August, there was a fear that miners 
would violate the new softfork rules, causing a chainsplit. If that had 
occurred, obsolete nodes would have been vulnerable.

> > What is the plan for getting security and protocol change updates
> > backported to Debian stable?
> 
> Debian standard procedures for updating stable packages.

In my experience, that has been "never update, even when fixes are available" 
except for highly-visible security issues. :(

Luke

Bug#879001: Bug#879002: Should the package be removed?

[Markus Koschany]

On Wed, 18 Oct 2017 13:29:19 +0200 Emmanuel Bourg  wrote:
> Upstream has moved to GitHub [1] and the last update was released in
> 2014 but the security issue is still not fixed [2].
> 
> This was a dependency of Jenkins which is now gone. There is a slim
> chance that this package could be useful again in the future since it's
> a dependency of some Apache projects (Zeppelin, Atlas, Ranger and Knox).
> 
> Emmanuel Bourg
> 
> [1] https://github.com/kohsuke
> [2] https://github.com/kohsuke/libpam4j/issues/18

Apparently Red Hat patched their libpam4j package but they didn't
forward the patch upstream.

https://bugzilla.redhat.com/show_bug.cgi?id=1503103

Actually I agree with Raphael. The software is unmaintained upstream and
unused in Debian. It's rather scary that other projects depend on it,
especially when it comes to security sensitive matters like PAM. In the
end it can always be reintroduced if someone really intends to maintain it.






signature.asc
Description: OpenPGP digital signature

Bug#880039: marked as done (beara fails without en_US.UTF-8 locale)

[Debian Bug Tracking System]

Your message dated Fri, 03 Nov 2017 19:48:54 +
with message-id 
and subject line Bug#880039: fixed in bear 2.3.9-1
has caused the Debian Bug report #880039,
regarding beara fails without en_US.UTF-8 locale
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.)


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

Dear Maintainer,


   A recent update to bear has caused execution of any subprocess to
   fail on my system:

> bear sh -c /bin/echo
bear: newlocale: No such file or directory

It seems this is caused by an inability to load the "en_US.UTF-8"
locale which is not installed on my system (see libear/ear.c:434).

It looks like this has been already been reported, and fixed
upstream in [this

commit](https://github.com/rizsotto/Bear/commit/b5d831ea158a8eff0b5dcb3d863e0046528189e6)

Without this commit it seems like any user of `bear` will have to have
en_US.UTF-8 installed.

Is there any possibilty debian can backport this fix, or do a
version bump?

All the Best

Luke


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

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

Versions of packages bear depends on:
ii  libear   2.3.7-1
ii  python3  3.6.3-2

bear recommends no packages.

bear suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: bear
Source-Version: 2.3.9-1

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated bear 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, 03 Nov 2017 14:31:30 -0500
Source: bear
Binary: bear libear
Architecture: source
Version: 2.3.9-1
Distribution: unstable
Urgency: medium
Maintainer: Sebastian Ramacher 
Changed-By: Sebastian Ramacher 
Description:
 bear   - generate compilation database for Clang tooling
 libear - generate compilation database for Clang tooling (wrapper library)
Closes: 880039
Changes:
 bear (2.3.9-1) unstable; urgency=medium
 .
   * New upstream release.
 - Fix locales handling. (Closes: #880039)
Checksums-Sha1:
 f62dd158f21a048a7a653ab74d4e54240f56d5e2 1901 bear_2.3.9-1.dsc
 ec13fedd814b8ee79b613df27a3725af0b48fa59 42987 bear_2.3.9.orig.tar.gz
 e6701056b36ff4adb5290ce802c4d6c3af8c3275 3500 bear_2.3.9-1.debian.tar.xz
Checksums-Sha256:
 7cc898d4973398fe8bd81afe940a35f0cd53f3c31320ad9632fa39006d8636e6 1901 
bear_2.3.9-1.dsc
 9adad7e6a028c2dbce7ddb5515a2804d938a3ab0d1e1f669dd6371c8fd8aa4e4 42987 
bear_2.3.9.orig.tar.gz
 b309be5f3649c8df597ed537bbbfbe5a34546d77b1b05371ad6d070b867eda1e 3500 
bear_2.3.9-1.debian.tar.xz
Files:
 57c803d2e4e48647a376e607b9220984 1901 devel optional bear_2.3.9-1.dsc
 e0ec02a038b8602a5c4cfa4b00111ce5 42987 devel optional bear_2.3.9.orig.tar.gz
 46720762837559c98665e8fbb621c00f 3500 devel optional bear_2.3.9-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIyBAEBCAAcBQJZ/MW0FRxzcmFtYWNoZXJAZGViaWFuLm9yZwAKCRBp8vxRbqcZ
k/qgD/9gq+T7/w8VkPbSmZ3C+Z3AM/FcSfhAUxDvm7ljsmXAboMtdJ9bgubKvqnL
YZ8M5j4ozxHA4IBmuRuIszqmBss2rKBf+peFOg1ZNXyq48V+UpYX6RUBISb4pBNc
IRymo6Ag9Fh+POR6FupAEV/ixFBEmPRvqPU63uuDdliU2DAisLei9K/WkdQcofdL
UF3Nw1Y46+cs4VojkXdKjhwBhDEF/5FiSaSzlf9tNhr+f8l5V3VIES5+kEe08mmf
2FqTR61e/dlj8yzODzGfVkciUPObN1MiMFMA3PILbUmYVK1tF+xcxlveHoEQ0Czg
s9csVMKROK8QPyoD45x+PT41MC47aaMXSIWxzNAWEGhZX6uN9OAwrQH1xYzJVMgx

Bug#879984: libgcrypt20: copyright does not mention OCB patent license

[Andreas Metzler]

On 2017-11-03 Jan Kiszka  wrote:
> Has this topics also been brought up upstream already? Didn't find a
> reference so far.

No, I have not yet done so. The OCB licenses is listed in GIT's LICENSES
file, it is just not listed in EXTRA_DIST and therefore missing in the
tarball.

Re Debian I think we 'll just need to update the copyright file, there
are multiple OCB implementatios in Debian/main and some are using the
genneric opensource license grant.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#879886: [Debian-med-packaging] libhts2: libhts2 needs to handle ABI changes

[Diane Trout]

> Would adding a symbols file back to the htslib packaging be an
> alternative solution to manually overriding ${shlibs:Depends} in
> samtools, bcftools, and python-pysam? The build-depends in these
> packages are always versioned appropriately.
> 

I believe that adding the symbols file back in is the correct solution.
 It should allow dpkg-shlibdeps to generate the correct libhst2
dependencies version.

Diane

Bug#880674: libpango-1.0-0: Thai word break stops working since 1.40.13

[Theppitak Karoonboonyanan]

On Fri, Nov 3, 2017 at 11:31 PM, Michael Biebl  wrote:
> Am 03.11.2017 um 17:25 schrieb Michael Biebl:
>
>> It's a known issue, see https://bugzilla.gnome.org/show_bug.cgi?id=789625
>
> Let me rephrase that a little: I'm pretty sure it's the same underlying
> issue and it would be great if you can give the patch in the upstream
> bug tracker a try.

Yes, I have tried it and I confirm that it fixes this bug, too.

Thanks,
-- 
Theppitak Karoonboonyanan
http://linux.thai.net/~thep/

Bug#877567: marked as done (llvm-toolchain-3.9 FTBFS on mipsel)

[Debian Bug Tracking System]

Your message dated Fri, 03 Nov 2017 17:06:12 +
with message-id 
and subject line Bug#877567: fixed in llvm-toolchain-5.0 1:5.0.1~+rc1-1~exp1
has caused the Debian Bug report #877567,
regarding llvm-toolchain-3.9 FTBFS on mipsel
to be marked as done.

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

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


-- 
877567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877567
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: llvm-toolchain-3.9
Version: 1:3.9.1-17
Severity: serious

https://buildd.debian.org/status/logs.php?pkg=llvm-toolchain-3.9=mipsel

...
/usr/bin/ld: BFD (GNU Binutils for Debian) 2.29.1 internal error, aborting at 
../../bfd/merge.c:910 in _bfd_merged_section_offset

/usr/bin/ld: Please report this bug.

collect2: error: ld returned 1 exit status
tools/llvm-shlib/CMakeFiles/LLVM.dir/build.make:274: recipe for target 
'lib/libLLVM-3.9.so.1' failed
make[4]: *** [lib/libLLVM-3.9.so.1] Error 1


In #874674 it was discovered that this is just a bad
error handling for "out of memory" in ld.


llvm-toolchain-3.9 (1:3.9.1-16) unstable; urgency=medium
...
  [ Matthias Klose ]
...
  * On amd64, s390x, arm64 and ppc64el, build with -g1 instead of -g.
...
 -- Sylvestre Ledru   Fri, 08 Sep 2017 11:57:07 +0200

This is also what debian/rules does, and it is pretty weird:

ifneq (,$(filter $(DEB_HOST_ARCH),amd64 arm64 ppc64el s390x))
  opt_flags += -g1
else
  opt_flags += -g
endif

-g is equal to -g2, so this change reduces the amount of debug
information generated on some 64bit architectures - these are
architectures where -g is supposed to not cause any problems.


mipsel being the only failing release architecture makes sense
considering that -g is used on 32bit, and mipsel is missing in
the list of gsplit dwarf architectures.


There are three alternative approaches, either would make sense
and should fix the mipsel build (untested):

1. go back to -g everywhere and remove ENABLE_SPLIT_DWARF_ARCHS,
   that's then actually required on all 32bit architectures:

ifeq ($(DEB_HOST_ARCH_BITS),32)
  CXXFLAGS_EXTRA += -gsplit-dwarf
endif

2. remove all gsplit dwarf usage and reverse the -g1 handling
   so that it makes sense:

ifeq ($(DEB_HOST_ARCH_BITS),32)
  opt_flags += -g1
else
  opt_flags += -g
endif


3. remove all gsplit dwarf usage and use -g1 on all architectures:

opt_flags += -g1
--- End Message ---
--- Begin Message ---
Source: llvm-toolchain-5.0
Source-Version: 1:5.0.1~+rc1-1~exp1

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

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

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

Debian distribution maintenance software
pp.
Sylvestre Ledru  (supplier of updated llvm-toolchain-5.0 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 03 Nov 2017 15:30:19 +0100
Source: llvm-toolchain-5.0
Binary: clang-5.0 clang-format-5.0 clang-tidy-5.0 clang-5.0-doc libclang1-5.0 
libclang1-5.0-dbg libclang-5.0-dev libclang-common-5.0-dev libfuzzer-5.0-dev 
python-clang-5.0 clang-5.0-examples libllvm5.0 libllvm5.0-dbg llvm-5.0 
llvm-5.0-runtime llvm-5.0-dev llvm-5.0-tools llvm-5.0-doc llvm-5.0-examples 
lld-5.0 liblld-5.0 liblld-5.0-dbg liblld-5.0-dev lldb-5.0 liblldb-5.0 
liblldb-5.0-dbg python-lldb-5.0 liblldb-5.0-dev
Architecture: source amd64 all
Version: 1:5.0.1~+rc1-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: LLVM Packaging Team 
Changed-By: Sylvestre Ledru 
Description:
 clang-5.0  - C, C++ and Objective-C compiler (LLVM based)
 clang-5.0-doc - C, C++ and Objective-C compiler (LLVM based) - Documentation
 clang-5.0-examples - Clang examples
 clang-format-5.0 - Tool to format C/C++/Obj-C code
 clang-tidy-5.0 - clang-based C++ linter tool
 libclang-5.0-dev - clang library - Development package
 libclang-common-5.0-dev - clang library - Common development package
 libclang1-5.0 - C interface to the clang library
 libclang1-5.0-dbg - clang library
 libfuzzer-5.0-dev - Library for coverage-guided fuzz testing
 

Bug#876533: hol-light FTBFS with OCaml 4.05.0

[Ximin Luo]

Hendrik Tews:
> 
>> Hi Hendrik, any progress on this? I notice in the ocaml transition tracker:
> 
> I really spend more than 4 weeks in discussions with upstream
> about license and copyright clarifications. Now it is finished. I
> uploaded a new hol-light version to DOM git yesterday. Please
> review and upload.
> 

Ouch, well here are some comments:

dpkg-gencontrol: warning: package hol-light: unused substitution variable 
${ocaml:Provides}
dpkg-gencontrol: warning: package hol-light: unused substitution variable 
${perl:Depends}

These are quite important, you should never ignore them. You need to add an 
extra Provides: ${ocaml:Provides}, and add ${perl: Depends} to the 
already-existing Depends field.

(I actually don't know why dpkg-gencontrol doesn't just fail the build instead 
of emitting a warning. Perhaps for backwards-compat or something.)

The rest of the package looks fine, except that I am not sure about installing 
everything in /usr/share/hol-light.

If hol-light allows itself to be used as an importable ocaml library for other 
programs and code, then it should be installed in /usr/lib/ocaml/hol-light - 
AFAIU extrapolating the (out-of-date) Debian Ocaml packaging policy. I am not 
sure our Debian ocaml toolchain will pick up libraries installed into 
/usr/share - and you will have to move it into /usr/lib anyway if the project 
eventually provides native shared libs, since /usr/share must only contain 
architecture-independent files.

It would be good if someone else from the team less new than me, could explain 
this issue properly and/or confirm what I'm suspecting here.

If there are good reasons for installing it in /usr/share/hol-light (which 
seems to be inconsistent with the packaging policy, as I mentioned) please 
describe them in debian/README.Debian. For example, I can see that upstream 
does not have a proper "make install" target for this stuff, and you specify 
/usr/share yourself in d/rules. So perhaps it is not supposed to be used by 
other ocaml code, and you include stuff in /usr/share merely "for reference". 
If that is correct, please add this explanation to the README.

X

-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git

Bug#880674: libpango-1.0-0: Thai word break stops working since 1.40.13

[Michael Biebl]

Am 03.11.2017 um 17:25 schrieb Michael Biebl:

> It's a known issue, see https://bugzilla.gnome.org/show_bug.cgi?id=789625

Let me rephrase that a little: I'm pretty sure it's the same underlying
issue and it would be great if you can give the patch in the upstream
bug tracker a try.


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



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#880674: libpango-1.0-0: Thai word break stops working since 1.40.13

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=789625
Bug #880674 [libpango-1.0-0] libpango-1.0-0: Thai word break stops working 
since 1.40.13
Set Bug forwarded-to-address to 
'https://bugzilla.gnome.org/show_bug.cgi?id=789625'.
> tags -1 + patch
Bug #880674 [libpango-1.0-0] libpango-1.0-0: Thai word break stops working 
since 1.40.13
Added tag(s) patch.

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

Bug#880674: libpango-1.0-0: Thai word break stops working since 1.40.13

[Michael Biebl]

Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=789625
Control: tags -1 + patch

Am 03.11.2017 um 16:36 schrieb Jeremy Bicha:
> Control: severity -1 serious
> 
> On Fri, Nov 3, 2017 at 11:25 AM, Theppitak Karoonboonyanan
>  wrote:
>> Since Pango 1.40.13, Thai word break appears to be broken. This affects
>> all GTK+-based text editors like gedit, mousepad, leafpad, etc. as well as
>> Mozilla Firefox.
> 
> Thank you for your detailed bug report. Please forward this to GNOME
> and let us know the bug number here.
> 

It's a known issue, see https://bugzilla.gnome.org/show_bug.cgi?id=789625

The patch in the bug report seems to fix the issue but I'd wait until it
has been committed to git.



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



signature.asc
Description: OpenPGP digital signature

Bug#879624: Similar issue, also X1 carbon

[Michael Hanke]

Hi,

same here, after upgrade to buster no X anymore. Normal start works, but
ends at terminal login. Manual startx makes the screen flicker briefly,
then back to terminal. X log contain no errors (EE).

Downgrade to stretch didn't change the situation in any way. Going back
from linux 4.13 to 4.8 had no effect either.

During downgrade gconf2 choked (triggers hung and never completed). During
upgrade I think I saw some gconf error message too, but I cannot find a
trace of them anywhere.

Any advice would be highly appreciated.

Thanks in advance

Michael

Processed: tagging 867254

[Debian Bug Tracking System]

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

> # this is caused by python-django 1.11 in buster/sid, which now has a breaks 
> against the o-d version from stretch
> tags 867254 + sid buster
Bug #867254 {Done: Thomas Goirand } [openstack-dashboard] 
openstack-dashboard: fails to install: 
django.core.exceptions.ImproperlyConfigured: AUTH_USER_MODEL refers to model 
'openstack_auth.User' that has not been installed
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Processed: Re: Bug#880674: libpango-1.0-0: Thai word break stops working since 1.40.13

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #880674 [libpango-1.0-0] libpango-1.0-0: Thai word break stops working 
since 1.40.13
Severity set to 'serious' from 'important'

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

Bug#880669: [Pkg-emacsen-addons] Bug#880669: irony-mode: FTBFS on arm64: timeout in irony-iotask-schedule/task-update/invalid-msg

[Nicholas D Steeves]

Hi Aaron,

Thank you for reporting this.  Autopkgtest's were not run in previous
versions of this package, and this shows that the new tests are
working :-) I have forwarded this bug upstream along with a couple of
questions about how to proceed.

Regards,
Nicholas


signature.asc
Description: PGP signature

Bug#880670: [Pkg-emacsen-addons] Bug#880670: irony-mode: FTBFS on mips64el: FAILED 22/41 irony-iotask-schedule/task-update/invalid-msg

[Nicholas D Steeves]

Hi Aaron,

Thank you for reporting this.  Autopkgtest's were not run in previous
versions of this package, and this shows that the new tests are
working :-) I have forwarded this bug upstream along with a couple of
questions about how to proceed.

Regards,
Nicholas


signature.asc
Description: PGP signature

Processed: bug 880670 is forwarded to https://github.com/Sarcasm/irony-mode/issues/449

[Debian Bug Tracking System]

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

> forwarded 880670 https://github.com/Sarcasm/irony-mode/issues/449
Bug #880670 [src:irony-mode] irony-mode: FTBFS on mips64el: FAILED  22/41  
irony-iotask-schedule/task-update/invalid-msg
Set Bug forwarded-to-address to 
'https://github.com/Sarcasm/irony-mode/issues/449'.
> thanks
Stopping processing here.

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

Processed: bug 880669 is forwarded to https://github.com/Sarcasm/irony-mode/issues/449

[Debian Bug Tracking System]

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

> forwarded 880669 https://github.com/Sarcasm/irony-mode/issues/449
Bug #880669 [src:irony-mode] irony-mode: FTBFS on arm64: timeout in 
irony-iotask-schedule/task-update/invalid-msg
Set Bug forwarded-to-address to 
'https://github.com/Sarcasm/irony-mode/issues/449'.
> thanks
Stopping processing here.

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

Bug#880670: irony-mode: FTBFS on mips64el: FAILED 22/41 irony-iotask-schedule/task-update/invalid-msg

[Aaron M. Ucko]

Source: irony-mode
Version: 1.2.0-1
Severity: serious
Tags: upstream
Justification: fails to build from source (but built successfully in the past)
User: debian-m...@lists.debian.org
Usertags: mips64el

The latest build of irony-mode for mips64el encountered a test suite
failure in irony-iotask-schedule/task-update/invalid-msg ("the error
signaled did not have the expected type"), per the below excerpts from
https://buildd.debian.org/status/fetch.php?pkg=irony-mode=mips64el=1.2.0-1=1509635728=0

Could you please take a look?

Thanks!



Test irony-iotask-schedule/task-update/invalid-msg backtrace:
  ert--should-error-handle-error((lambda nil form-description-168) (ir
  (condition-case -condition- (unwind-protect (setq value-166 (apply f
  (let ((errorp169 nil) (form-description-fn-170 (function (lambda nil
  (let (form-description-168) (let ((errorp169 nil) (form-description-
  (let ((value-166 (quote ert-form-evaluation-aborted-167))) (let (for
  (let ((fn-164 (function irony-iotask-run)) (args-165 (list process t
  (progn (irony-iotask-setup-process process) (let ((fn-164 (function 
  (unwind-protect (progn (irony-iotask-setup-process process) (let ((f
  (let ((process-connection-type nil) (process-adaptive-read-buffering
  (let ((task (irony-iotask-package-task irony-iotask/task-invalid-msg
  (lambda nil (let ((task (irony-iotask-package-task irony-iotask/task
  ert--run-test-internal([cl-struct-ert--test-execution-info [cl-struc
  ert-run-test([cl-struct-ert-test irony-iotask-schedule/task-update/i
  ert-run-or-rerun-test([cl-struct-ert--stats t [[cl-struct-ert-test c
  ert-run-tests(t #[385 "\30\307\"\203G\211\211G\310U\2063\211@\20
  ert-run-tests-batch(nil)
  ert-run-tests-batch-and-exit()
  eval((ert-run-tests-batch-and-exit))
  command-line-1(("-l" "package" "--eval" "(add-to-list 'package-direc
  command-line()
  normal-top-level()
Test irony-iotask-schedule/task-update/invalid-msg condition:
(ert-test-failed
 ((should-error
   (irony-iotask-run process task)
   :type 'irony-iotask-bad-data)
  :form
  (irony-iotask-run #
   [cl-struct-irony-iotask-packaged-task
  (:start ... :update ...)
nil

  [cl-struct-irony-iotask-result error nil irony-iotask-bad-data ...]

 nil nil])
  :condition
  (irony-iotask-filter-error "spurious output" "
")
  :fail-reason "the error signaled did not have the expected type"))
   FAILED  22/41  irony-iotask-schedule/task-update/invalid-msg
emacs-irony-test process stopped!
[...]
Ran 41 tests, 40 results as expected, 1 unexpected (2017-11-02 15:15:20+)

1 unexpected results:
   FAILED  irony-iotask-schedule/task-update/invalid-msg

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#880669: irony-mode: FTBFS on arm64: timeout in irony-iotask-schedule/task-update/invalid-msg

[Aaron M. Ucko]

Source: irony-mode
Version: 1.2.0-1
Severity: serious
Tags: upstream
Justification: fails to build from source (but built successfully in the past)
User: debian-...@lists.debian.org
Usertags: arm64

The latest build of irony-mode for arm64 hit the autobuilder's
generous 150-minute inactivity timeout while running
irony-iotask-schedule/task-update/invalid-msg (presumably due to
hanging or spinning somewhere), per the below excerpt from
https://buildd.debian.org/status/fetch.php?pkg=irony-mode=arm64=1.2.0-1=1509629187=0

Could you please take a look?

Thanks!



Test irony-iotask-schedule/task-update/invalid-msg backtrace:
  (if (unwind-protect (setq value-97 (apply fn-95 args-96)) (setq form
  (let (form-description-99) (if (unwind-protect (setq value-97 (apply
  (let ((value-97 (quote ert-form-evaluation-aborted-98))) (let (form-
  (let ((fn-95 (function string=)) (args-96 (list (buffer-string) "exi
  (progn (let ((fn-95 (function string=)) (args-96 (list (buffer-strin
  (if (>= (buffer-size) (length "exit\n")) (progn (let ((fn-95 (functi
  (save-current-buffer (set-buffer (process-buffer process)) (goto-cha
  (progn (save-current-buffer (set-buffer (process-buffer process)) (g
  (if (buffer-live-p (process-buffer process)) (progn (save-current-bu
  irony-iotask-echo-process-exit-filter(# "e
  sleep-for(0.05)
  sit-for(0.05)
  (while (process-live-p process) (sit-for 0.05))
  (progn (while (process-live-p process) (sit-for 0.05)))
  (unwind-protect (progn (while (process-live-p process) (sit-for 0.05
  (let* ((-with-timeout-timer- (run-with-timer 1 nil (function (lambda
  (catch (quote timeout) (let* ((-with-timeout-timer- (run-with-timer 
  (let ((-with-timeout-value- (catch (quote timeout) (let* ((-with-tim
  (unwind-protect (progn (irony-iotask-setup-process process) (let ((f
  (let ((process-connection-type nil) (process-adaptive-read-buffering
  (let ((task (irony-iotask-package-task irony-iotask/task-invalid-msg
  (lambda nil (let ((task (irony-iotask-package-task irony-iotask/task
  ert--run-test-internal([cl-struct-ert--test-execution-info [cl-struc
  ert-run-test([cl-struct-ert-test irony-iotask-schedule/task-update/i
  ert-run-or-rerun-test([cl-struct-ert--stats t [[cl-struct-ert-test c
  ert-run-tests(t #[385 "\30\307\"\203G\211\211G\310U\2063\211@\20
  ert-run-tests-batch(nil)
  ert-run-tests-batch-and-exit()
  eval((ert-run-tests-batch-and-exit))
  command-line-1(("-l" "package" "--eval" "(add-to-list 'package-direc
  command-line()
  normal-top-level()
Test irony-iotask-schedule/task-update/invalid-msg condition:
(ert-test-failed
 ((should
   (string=
   (buffer-string)
   "exit
"))
  :form
  (string= "
exit" "exit
")
  :value nil))
   FAILED  22/41  irony-iotask-schedule/task-update/invalid-msg
emacs-irony-test process stopped!
E: Build killed with signal TERM after 150 minutes of inactivity

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#880566: Fix for crash

[Teus Benschop]

The crash mentioned in this bug report has been fixed after packaging the
newest upstream source, version 2.11.1.

The new package is available from the code repository.

https://anonscm.debian.org/gitweb/?p=pkg-crosswire/bibletime.git

I will be asking for sponsorship for uploading this package.

Bug#718272: [Pkg-bitcoin-devel] Bug#718272: Bitcoin still not ready for stable release in Debian

[Jonas Smedegaard]

Quoting Luke Dashjr (2017-11-03 11:25:23)
> On Friday 03 November 2017 9:10:37 AM you wrote:
>> I believe Bitcoin is now stable enough for stable release.
>
> Things have only gotten less stable upstream since 2013...

Please provide references supporting that.


> What is the plan for getting security and protocol change updates 
> backported to Debian stable?

Debian standard procedures for updating stable packages.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

Bug#879984: libgcrypt20: copyright does not mention OCB patent license

[Jan Kiszka]

Has this topics also been brought up upstream already? Didn't find a
reference so far.

Bug#880566: OK in newer version

[Teus Benschop]

The crash reported in this bug does not occur when building the newer
upstream version from source. That newer version, built from source,
behaves as expected.

Processed: libmstoolkit: diff for NMU version 77.0.0-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 853351 + pending
Bug #853351 [src:libmstoolkit] comet-ms: ftbfs with GCC-7
Bug #853498 [src:libmstoolkit] libmstoolkit: ftbfs with GCC-7
Added tag(s) pending.
Added tag(s) pending.

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

Bug#853351: libmstoolkit: diff for NMU version 77.0.0-1.1

[Gilles Filippini]

Control: tags 853351 + pending

Dear maintainer,

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

Regards,

_g.

diff -Nru libmstoolkit-77.0.0/debian/changelog 
libmstoolkit-77.0.0/debian/changelog
--- libmstoolkit-77.0.0/debian/changelog2015-09-25 15:20:00.0 
+0200
+++ libmstoolkit-77.0.0/debian/changelog2017-11-02 22:42:31.0 
+0100
@@ -1,3 +1,10 @@
+libmstoolkit (77.0.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * New patch gcc-7.patch: fix FTBFS with GCC-7 (closes: #853351)
+
+ -- Gilles Filippini   Thu, 02 Nov 2017 22:42:31 +0100
+
 libmstoolkit (77.0.0-1) unstable; urgency=medium
 
   * New upstream version;
diff -Nru libmstoolkit-77.0.0/debian/patches/gcc-7.patch 
libmstoolkit-77.0.0/debian/patches/gcc-7.patch
--- libmstoolkit-77.0.0/debian/patches/gcc-7.patch  1970-01-01 
01:00:00.0 +0100
+++ libmstoolkit-77.0.0/debian/patches/gcc-7.patch  2017-10-12 
21:39:30.0 +0200
@@ -0,0 +1,26 @@
+Index: libmstoolkit/include/MSReader.h
+===
+--- libmstoolkit.orig/include/MSReader.h
 libmstoolkit/include/MSReader.h
+@@ -82,7 +82,7 @@ class MSReader {
+   void setPrecisionInt(int i);
+   void setPrecisionMZ(int i);
+   void writeFile(const char* c, bool text, MSObject& m);
+-  void writeFile(const char* c, MSFileFormat ff, MSObject& m, char* 
sha1Report='\0');
++  void writeFile(const char* c, MSFileFormat ff, MSObject& m, char* 
sha1Report=NULL);
+ 
+   bool readMSTFile(const char* c, bool text, Spectrum& s, int scNum=0);
+   bool readMZPFile(const char* c, Spectrum& s, int scNum=0);
+Index: libmstoolkit/src/MSToolkit/MSReader.cpp
+===
+--- libmstoolkit.orig/src/MSToolkit/MSReader.cpp
 libmstoolkit/src/MSToolkit/MSReader.cpp
+@@ -688,7 +688,7 @@ void MSReader::writeSqlite(const char* c
+   string instrumentType="=";
+   for(int i=0; i<16; i++)
+ {
+-  if(m.getHeader().header[i] != '\0')
++  if(m.getHeader().header[i] != NULL)
+   {
+ string headerLine = m.getHeader().header[i];
+ if(headerLine.find("CreationDate") != string::npos)
diff -Nru libmstoolkit-77.0.0/debian/patches/series 
libmstoolkit-77.0.0/debian/patches/series
--- libmstoolkit-77.0.0/debian/patches/series   2015-09-25 15:20:00.0 
+0200
+++ libmstoolkit-77.0.0/debian/patches/series   2017-10-12 21:39:30.0 
+0200
@@ -1,2 +1,3 @@
 makefile.patch
 
+gcc-7.patch

Bug#879848: marked as done (cappuccino: missing dependency on gir1.2-gtk-3.0)

[Debian Bug Tracking System]

Your message dated Fri, 03 Nov 2017 12:19:05 +
with message-id 
and subject line Bug#879848: fixed in cappuccino 0.5.1-7
has caused the Debian Bug report #879848,
regarding cappuccino: missing dependency on gir1.2-gtk-3.0
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.)


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

Dear Maintainer,

I installed and tried to start cappuccino, but it didn't launch:

$ cappuccino 
Traceback (most recent call last):
  File "/usr/bin/cappuccino", line 11, in 
gi.require_version('Gtk', '3.0')
  File "/usr/lib/python3/dist-packages/gi/__init__.py", line 118, in 
require_version
raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace Gtk not available

After installing gir1.2-gtk-3.0 it successfully starts, so this should
be added to the dependencies.

Kind regards,
  Reiner


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: cappuccino
Source-Version: 0.5.1-7

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

Debian distribution maintenance software
pp.
Breno Leitao  (supplier of updated cappuccino 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, 03 Nov 2017 07:52:46 -0400
Source: cappuccino
Binary: cappuccino
Architecture: source all
Version: 0.5.1-7
Distribution: unstable
Urgency: medium
Maintainer: Breno Leitao 
Changed-By: Breno Leitao 
Description:
 cappuccino - utility to let your boss think that you're working hard
Closes: 879848
Changes:
 cappuccino (0.5.1-7) unstable; urgency=medium
 .
   * Adding gir1.2-gtk-3.0 as a dependency. Closes: #879848
   * Adding a link to /usr/games/cappuccino
Checksums-Sha1:
 884fb4a93387074d8e6d89af40c3dffe8db63f0c 1739 cappuccino_0.5.1-7.dsc
 f0edecc44c0a2b191b00bd8b5b8cbe92316edcaa 3840 cappuccino_0.5.1-7.diff.gz
 edf857d43bcf0cedf113b55088af95ba03d85d24 91582 cappuccino_0.5.1-7_all.deb
 417a96975ed79705ed115a83b5cb0100f4092cfe 6178 
cappuccino_0.5.1-7_ppc64el.buildinfo
Checksums-Sha256:
 7bccaf8dd93a0bfd14efb624bb51359df04b981545b85cd704fe054bacf9f1fd 1739 
cappuccino_0.5.1-7.dsc
 5cf939b87be2048aa8b6882a0b7a620e8b9b532db9d17f03d78238b258738531 3840 
cappuccino_0.5.1-7.diff.gz
 6a0ba924210d1896ae04a5ed0c4e85e1f734a3598a77527447349d31acbb55f2 91582 
cappuccino_0.5.1-7_all.deb
 0913679255d77cb66fd9578d4eaba56c8fa34d14ce5040a25f8e85f8c4dfb468 6178 
cappuccino_0.5.1-7_ppc64el.buildinfo
Files:
 af29bf9674f0410d2ced88b55616a7c1 1739 games optional cappuccino_0.5.1-7.dsc
 ead67407eaf01337fe4e8ac59af84380 3840 games optional cappuccino_0.5.1-7.diff.gz
 a6e5facc42169ce663a54eb769243674 91582 games optional 
cappuccino_0.5.1-7_all.deb
 6706f3ab480b8a6aad8c5fc35e78c737 6178 games optional 
cappuccino_0.5.1-7_ppc64el.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEErIU5puj0ZwLKSkObNaOTn/x4d20FAln8W2gACgkQNaOTn/x4
d22nnRAAkBsPXX2tP50GIRrNhtCPuV6x/AzjH5lyXejNyss3yTuaohZCE+G8yfWf
SbrO96yTCCQ9v9uK9NtfWTiLz0Grm9oaJG5fsmUDYExTLIfpBtDjSlAqjOevgEin
55pVfH6S4HltJO0jgkE3Tel0mMRMc/mNjfzodZG348b69s8Jl0EWcQqgAXEN9JYE
C6DrCH23VLcK719Ci2RrTTMFBKisTH+TkMl428jsznmIyOaqCu+G7PxaQdtENWay
rPhBuXorUy1v9thccFWWrMpfhhd4XNdpS6WfLIquOnEZcFYdZl8mvDl5UgvMsuDy
VYDk7oz8EeZm4QOHPEmhdYpArz5kfiHjqG+gwP+vw/WgaDO6Ps93wOQzFzJ4w84q
UJcFYHaDT+98KtugtIHGiIInOb9cs08s69zY382x4B0TViAk5jAlYTPf5fc7xZMz
gZhhyNX/89NvstdtlQBvqHo39blMAGngk5RU+vkZTWqKqdoFcHoiaLrt63Flv/OC
1dX1aQ7D/4SnHTYVv69mvwfnyfD80M8tHwVqVDXPupOyO8hOIQTxv6E0oDFtPoLX
PQg7jbMR1RQ1Vo5sjZ4RTYSvsCDwFRYiMGqTqpxOoFM5maRYUu6b3wlkGxTCWiYw
K80FcrWh9/mvcKhwu70jTPDP9kB7eSh3B2xpiLz73e2GRGWQELE=
=1EEM
-END PGP SIGNATURE End Message ---

Bug#878498: snakemake FTBFS with Python 3.6 as default

[chrysn]

Package: src:snakemake
Followup-For: Bug #878498

The test also fails with the 3.13.3 version in the team repository.

I've had a short look at whether upgrading to 4.3.0 helps (minimal patch
refreshing and new build dependency on python3-configargparse as well as
the unpackaged ratelimiter module), but the same condition shows up
there as well.

I'll probably need to fix this, but as I'm new to snakemake: Will this
need keeping the 3 version around, or can I just go ahead and proceed
with 4.3.0?

Best regards
chrysn

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

Kernel: Linux 4.14.0-rc7-amd64 (SMP w/4 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)

-- 
To use raw power is to make yourself infinitely vulnerable to greater powers.
  -- Bene Gesserit axiom


signature.asc
Description: PGP signature

Bug#880652: appstream.debian.org: silent archive breakage from appstream-generator

[Julien Cristau]

On 11/03/2017 11:25 AM, Julien Cristau wrote:
> Package: appstream
> Severity: grave
> X-Debbugs-Cc: ftpmas...@ftp-master.debian.org
> 
> [filing this against the appstream package as a substitute for
> appstream.debian.org, feel free to reassign if there's a better place]
> 
> Hi,
> 
> there's some archive breakage because
> dists/sid/non-free/dep11/Components-amd64.yml.xz and
> dists/sid/non-free/dep11/Components-amd64.yml.gz are out of sync.  It
> looks like appstream-generator silently failed to write the xz version
> and left a mess in
> /srv/appstream.debian.org/workspace/public/data/sid/non-free/ on mekeel.
>  This should be made more robust, and any failure should mean nothing
> gets published rather than risking out of sync metadata.
> 

from the log (reordered for clarity):

2017-11-02 21:20:13 - INFO: Writing metadata for sid/non-free [amd64]
object.Exception@../src/asgen/zarchive.d(448): Unable to open file
'/srv/appstream.debian.org/workspace/public/data/sid/non-free/Components-amd64.yml.xz.new':
lzma compression failed: lzma_code() call returned status 11

??:? [0xdff26c07]
??:? [0xdff5638a]
??:? [0xdff5742a]
??:? [0xdff15d23]
??:? _D2rt6dmain211_d_run_mainUiPPaPUAAaZiZ6runAllMFZ9__lambda1MFZv
[0x9af8e90e]
??:? void rt.dmain2._d_run_main(int, char**, extern (C) int
function(char[][])*).tryExec(scope void delegate()) [0x9af8e84d]
??:? _d_run_main [0x9af8e744]
??:? __libc_start_main [0x9a52b2b0]
??:? [0xdff15909]

Cheers,
Julien

Bug#718272: Bitcoin still not ready for stable release in Debian

[Luke Dashjr]

On Friday 03 November 2017 9:10:37 AM you wrote:
> I believe Bitcoin is now stable enough for stable release.

Things have only gotten less stable upstream since 2013...

What is the plan for getting security and protocol change updates backported 
to Debian stable?

Luke

Bug#877106: pinta: Pinta 1.6-2 crashes on image scaling and other image manipulation.

[Colin Alston]

Package: pinta
Version: 1.6-2
Followup-For: Bug #877106

Dear Maintainer,

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

   * What led up to the situation?
Using the paintbrush tool

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?

Application crash

*** Error in `/usr/bin/mono': double free or corruption (out):
0x560ecad3ca80 ***
=== Backtrace: =
/lib/x86_64-linux-gnu/libc.so.6(+0x70bcb)[0x7fba3ae54bcb]
/lib/x86_64-linux-gnu/libc.so.6(+0x76f96)[0x7fba3ae5af96]
/lib/x86_64-linux-gnu/libc.so.6(+0x777de)[0x7fba3ae5b7de]
[0x415ea7e0]
=== Memory map: 
414ad000-415f1000 rwxp  00:00 0
41672000-41682000 rwxp  00:00 0
560ec8b0c000-560ec8ea9000 r-xp  08:01 1601399
/usr/bin/mono-sgen
560ec90a8000-560ec90ad000 r--p 0039c000 08:01 1601399
/usr/bin/mono-sgen
560ec90ad000-560ec90b7000 rw-p 003a1000 08:01 1601399
/usr/bin/mono-sgen
560ec90b7000-560ec90ea000 rw-p  00:00 0
560ec9ff1000-560ecb2d3000 rw-p  00:00 0  [heap]
7fba-7fba00022000 rw-p  00:00 0
7fba00022000-7fba0400 ---p  00:00 0
7fba07457000-7fba077ff000 rw-p  00:00 0
7fba077ff000-7fba0780 ---p  00:00 0
7fba0780-7fba0800 rw-p  00:00 0
7fba0800-7fba08022000 rw-p  00:00 0
7fba08022000-7fba0c00 ---p  00:00 0
7fba0c00-7fba0c022000 rw-p  00:00 0
7fba0c022000-7fba1000 ---p  00:00 0
7fba1000-7fba10022000 rw-p  00:00 0
7fba10022000-7fba1400 ---p  00:00 0
7fba1400-7fba14022000 rw-p  00:00 0
7fba14022000-7fba1800 ---p  00:00 0
7fba1800-7fba18022000 rw-p  00:00 0
7fba18022000-7fba1c00 ---p  00:00 0
7fba1c00-7fba1c022000 rw-p  00:00 0
7fba1c022000-7fba2000 ---p  00:00 0
7fba201e8000-7fba2059 rw-p  00:00 0
7fba2059-7fba20591000 ---p  00:00 0
7fba20591000-7fba20d91000 rw-p  00:00 0
7fba20ea8000-7fba20f28000 rw-p  00:00 0
7fba20f2c000-7fba21592000 rw-p  00:00 0
7fba21592000-7fba215fb000 r-xp  08:01 1580021
/usr/lib/x86_64-linux-gnu/libjpeg.so.62.2.0
7fba215fb000-7fba217fb000 ---p 00069000 08:01 1580021
/usr/lib/x86_64-linux-gnu/libjpeg.so.62.2.0
7fba217fb000-7fba217fc000 r--p 00069000 08:01 1580021
/usr/lib/x86_64-linux-gnu/libjpeg.so.62.2.0
7fba217fc000-7fba217fd000 rw-p 0006a000 08:01 1580021
/usr/lib/x86_64-linux-gnu/libjpeg.so.62.2.0
7fba217fd000-7fba217fe000 ---p  00:00 0
7fba217fe000-7fba21ffe000 rw-p  00:00 0
7fba21ffe000-7fba21fff000 ---p  00:00 0
7fba21fff000-7fba227ff000 rw-p  00:00 0
7fba227ff000-7fba2280 ---p  00:00 0
7fba2280-7fba2300 rw-p  00:00 0
7fba2300-7fba2400 rw-s  00:05 1212422
/SYSV (deleted)
7fba2400-7fba24021000 rw-p  00:00 0
7fba24021000-7fba2800 ---p  00:00 0
7fba2805-7fba280d rw-p  00:00 0
7fba280d1000-7fba2817e000 r--p  08:01 1836258
/usr/share/fonts/truetype/dejavu/DejaVuSans-Bold.ttf
7fba2817e000-7fba28183000 r-xp  08:01 1710178
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-jpeg.so
7fba28183000-7fba28383000 ---p 5000 08:01 1710178
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-jpeg.so
7fba28383000-7fba28384000 r--p 5000 08:01 1710178
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-jpeg.so
7fba28384000-7fba28385000 rw-p 6000 08:01 1710178
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-jpeg.so
7fba28385000-7fba2839e000 r-xp  08:01 1589817
/usr/lib/x86_64-linux-gnu/gio/modules/libgioremote-volume-monitor.so
7fba2839e000-7fba2859e000 ---p 00019000 08:01 1589817
/usr/lib/x86_64-linux-gnu/gio/modules/libgioremote-volume-monitor.so
7fba2859e000-7fba285a1000 r--p 00019000 08:01 1589817
/usr/lib/x86_64-linux-gnu/gio/modules/libgioremote-volume-monitor.so
7fba285a1000-7fba285a2000 rw-p 0001c000 08:01 1589817
/usr/lib/x86_64-linux-gnu/gio/modules/libgioremote-volume-monitor.so
7fba285a2000-7fba28603000 rw-p  00:00 0
7fba28644000-7fba286c4000 rw-p  00:00 0
7fba286c8000-7fba28748000 rw-p  00:00 0
7fba2874b000-7fba287ab000 rw-s  00:05 1179653
/SYSV (deleted)
7fba287cb000-7fba2882b000 rw-s  00:05 1245188
/SYSV (deleted)
7fba2882b000-7fba28b0 rw-p  00:00 0
7fba28b04000-7fba28eae000 rw-p  00:00 0
7fba28eae000-7fba28f0 r--p  08:01 2359563
/usr/lib/mono/gac/Mono.Security/4.0.0.0__0738eb9f132ed756/Mono.Security.dll
7fba28f0-7fba2900 rw-p  00:00 0
7fba29001000-7fba29018000 rw-p  00:00 0
7fba29018000-7fba2901f000 r--s  08:01 1630947
/usr/lib/x86_64-linux-gnu/gconv/gconv-modules.cache
7fba2901f000-7fba2902f000 rwxp  00:00 0

Bug#880652: appstream.debian.org: silent archive breakage from appstream-generator

[Julien Cristau]

Package: appstream
Severity: grave
X-Debbugs-Cc: ftpmas...@ftp-master.debian.org

[filing this against the appstream package as a substitute for
appstream.debian.org, feel free to reassign if there's a better place]

Hi,

there's some archive breakage because
dists/sid/non-free/dep11/Components-amd64.yml.xz and
dists/sid/non-free/dep11/Components-amd64.yml.gz are out of sync.  It
looks like appstream-generator silently failed to write the xz version
and left a mess in
/srv/appstream.debian.org/workspace/public/data/sid/non-free/ on mekeel.
 This should be made more robust, and any failure should mean nothing
gets published rather than risking out of sync metadata.

See also bug#880645, which we can use to track either fixing the
immediate issue, or making dak validate the data it gets from mekeel
some more.

Cheers,
Julien

Bug#718272: marked as done (upstream does not support stable releases (block migration to testing))

[Debian Bug Tracking System]

Your message dated Fri, 03 Nov 2017 10:10:37 +0100
with message-id <150970023769.11303.14727396047278104...@auryn.jones.dk>
and subject line Re: Bitcoin still not ready for stable release in Debian
has caused the Debian Bug report #718272,
regarding upstream does not support stable releases (block migration to testing)
to be marked as done.

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

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


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

The bitcoin network requires on strict adherence to consensus between nodes.
Small changes to underlying libraries, even justified security changes,
threaten to break consensus and could possible cause accidental forks.

For example, it is possible for bug fix in libleveldb to cause a fork in the
network if existing nodes expect buggy behaviour.

Therefore, bitcoin upstream developers have strongly encouraged downstream
packagers to use the exact version of libleveldb included with their source
code.  However, upstream does not backport or support previously released
versions of bitcoind/bitcoin-qt.

For example: if we release Debian Jessie with version 0.8 of bitcoin, and a
security bug is found in that version and fixed upstream, the fix may be based
on top of version 0.10 and unable to be ported to 0.8. Upstream will, in that
case, release version 0.10 and not backport the fix to 0.8. This is especially
tricky now that Debian is using the bitcoin packaged version of leveldb.

Because of the sensitivity of this situation (lots of money can be lost), I
believe we should block migration to testing until either upstream supports
stable releases or we have a volunteer that works closely enough with upstream
code (an upstream developer) that is will to backport security and network-
related fixes.


There has been some work on multibit and electrum packages in Debian, these may
be better choices for wallets. If we keep bitcoin in unstable, we'll be able to
update as needed and users will understand that these packages are not stable
and will need to be updated often.



-- System Information:
Debian Release: wheezy/sid
  APT prefers raring-updates
  APT policy: (500, 'raring-updates'), (500, 'raring-security'), (500, 
'raring-proposed'), (500, 'raring'), (100, 'raring-backports')
Architecture: i386 (i686)

Kernel: Linux 3.8.0-27-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
I believe Bitcoin is now stable enough for stable release.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private--- End Message ---

Processed: Re: diffoscope: FTBFS: Test failures

[Debian Bug Tracking System]

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

> tags 880279 + pending
Bug #880279 [src:diffoscope] diffoscope: FTBFS: Test failures
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#880279: diffoscope: FTBFS: Test failures

[Chris Lamb]

tags 880279 + pending
thanks

Fixed in Git:

  
https://anonscm.debian.org/git/reproducible/diffoscope.git/commit/?id=d4ce05062e0368549ffe34276233f48f9ab68900


Regards,

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

Bug#877854: marked as done (bitcoin-qt: symbol lookup error: bitcoin-qt: undefined symbol: _ZNK8UniValueixEj)

[Debian Bug Tracking System]

Your message dated Fri, 03 Nov 2017 09:54:18 +0100
with message-id <150969925873.11303.7933683725030876...@auryn.jones.dk>
and subject line Re: Bug#877854: [Pkg-bitcoin-devel] Bug#877854: bitcoin-qt: 
symbol lookup error: bitcoin-qt: undefined symbol: _ZNK8UniValueixEj
has caused the Debian Bug report #877854,
regarding bitcoin-qt: symbol lookup error: bitcoin-qt: undefined symbol: 
_ZNK8UniValueixEj
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.)


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

X-Reportbug-Version: 7.1.7
X-Debbugs-Cc: phil...@marek.priv.at
X-Clacks-Overhead: GNU Terry Pratchett
Package: bitcoin-qt
Version: 0.15.0.1~dfsg-1
Severity: normal


# bitcoin-qt
bitcoin-qt: symbol lookup error: bitcoin-qt: undefined symbol: 
_ZNK8UniValueixEj



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

Architecture: amd64 (x86_64)

Kernel: Linux 4.12.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_AT:de (charmap=UTF-8)

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

Versions of packages bitcoin-qt depends on:
ii  libboost-chrono1.62.0   1.62.0+dfsg-4+b1
ii  libboost-filesystem1.62.0   1.62.0+dfsg-4+b1
ii  libboost-program-options1.62.0  1.62.0+dfsg-4+b1
ii  libboost-system1.62.0   1.62.0+dfsg-4+b1
ii  libboost-thread1.62.0   1.62.0+dfsg-4+b1
ii  libc6   2.24-17
ii  libdb5.3++  5.3.28-13.1
ii  libevent-2.1-6  2.1.8-stable-4
ii  libevent-pthreads-2.1-6 2.1.8-stable-4
ii  libgcc1 1:7.2.0-7
ii  libleveldb1v5   1.20-1
ii  libminiupnpc10  1.9.20140610-4
ii  libprotobuf10   3.0.0-9
ii  libqrencode33.4.4-1+b2
ii  libqt5core5a5.9.1+dfsg-9
ii  libqt5dbus5 5.9.1+dfsg-9
ii  libqt5gui5  5.9.1+dfsg-9
ii  libqt5network5  5.9.1+dfsg-9
ii  libqt5widgets5  5.9.1+dfsg-9
ii  libsecp256k1-0  0.1~20170810-1
ii  libssl1.1   1.1.0f-5
ii  libstdc++6  7.2.0-7
ii  libunivalue01.0.3-4
ii  libzmq5 4.2.2-1

bitcoin-qt recommends no packages.

bitcoin-qt suggests no packages.
--- End Message ---
--- Begin Message ---
Quoting Adrian Bunk (2017-10-08 23:47:31)
> Control: reassign -1 libunivalue0 1.0.3-4
> Control: affects -1 bitcoin-qt
> 
> On Fri, Oct 06, 2017 at 09:53:29AM +0200, Jonas Smedegaard wrote:
> >...
> > Quoting Philipp Marek (2017-10-06 09:37:08)
> > 
> > > # bitcoin-qt
> > > bitcoin-qt: symbol lookup error: bitcoin-qt: undefined symbol: 
> > > _ZNK8UniValueixEj
> > 
> > Thanks for reporting this!
> > 
> > Needs to be recompiled against latest libunivalue.
> >...
> 
> This bug did already become visible when the symbols files required 
> changes indicating that symbols were removed (at least on 64bit).
> 
> The backported unsigned int -> size_t changes are an ABI break that 
> cannot be made without a new soname (which should come from a new
> upstream release).

Upstream do not maintain a SONAME, and I maintain a symbols file to 
track changes more granularly.

Both reverse dependencies now have been rebuilt, so I believe this 
concrete bug is fixed (and I will keep in mind to be more cautious in 
the future cherry-picking ABI-changing patches).


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private--- End Message ---

Bug#880251: marked as done (duplicity: FTBFS: Test failures)

[Debian Bug Tracking System]

Your message dated Fri, 03 Nov 2017 08:49:30 +
with message-id 
and subject line Bug#880251: fixed in duplicity 0.7.14-2
has caused the Debian Bug report #880251,
regarding duplicity: FTBFS: Test failures
to be marked as done.

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

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


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

Hi,

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

Relevant part (hopefully):
> DeletedFiles 5
> ChangedFiles 7
> ChangedFileSize 8 (8 bytes)
> ChangedDeltaSize 9 (9 bytes)
> DeltaEntries 10
> RawDeltaSize 11 (11 bytes)
> TotalDestinationSizeChange 12 (12 bytes)
> '
> 
> --
> Ran 419 tests in 830.091s
> 
> FAILED (failures=1, skipped=8)
> Test failed: 
> error: Test failed:  failures=1>
> debian/rules:11: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2017/10/30/duplicity_0.7.14-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: duplicity
Source-Version: 0.7.14-2

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

Debian distribution maintenance software
pp.
Alexander Zangerl  (supplier of updated duplicity 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, 03 Nov 2017 16:50:12 +1000
Source: duplicity
Binary: duplicity
Architecture: source amd64
Version: 0.7.14-2
Distribution: unstable
Urgency: medium
Maintainer: Alexander Zangerl 
Changed-By: Alexander Zangerl 
Description:
 duplicity  - encrypted bandwidth-efficient backup
Closes: 880251
Changes:
 duplicity (0.7.14-2) unstable; urgency=medium
 .
   * adjusted testsuite to not bother with TZ-dependent
 time/date assertion, which seems to fail under sbuild/schroot
 (closes: #880251)
Checksums-Sha1:
 8f8d2b16d6459c6ab8682037343f09e3a01be2b4 1877 duplicity_0.7.14-2.dsc
 ee64bd1b865f5eb0cb5213352dbdf2b543d5bfee 14296 duplicity_0.7.14-2.debian.tar.xz
 44b4a409247cf30d50500330ab3df514241a0b27 14356 
duplicity-dbgsym_0.7.14-2_amd64.deb
 0bb9c86f1eaa50b19e3bdc3196b3d89e3e572d98 8211 
duplicity_0.7.14-2_amd64.buildinfo
 73472bd303f401d14222686343e18e1427d3855f 331192 duplicity_0.7.14-2_amd64.deb
Checksums-Sha256:
 acceaebb3a6b75dad254dcd6d80cad921c4d1e69a4e6d7a4f3b25e5636fe0f04 1877 
duplicity_0.7.14-2.dsc
 8eadf540a1d82c84063b1abc7daa8acebc6021fa0bca47a9459a80022a6c9aec 14296 
duplicity_0.7.14-2.debian.tar.xz
 d2d5b1cc02c114124ec06539521d06e3a11fc5db2d08d9baaf604f71a2ae9be3 14356 
duplicity-dbgsym_0.7.14-2_amd64.deb
 8ad375095a2680f83bcf9db933a222e9d5eadbd4a88a497ae877f04677367f2b 8211 
duplicity_0.7.14-2_amd64.buildinfo
 f1c5dda5ceb8b64b72e76b6da7e151053bde444c6771a5a2b3bc962441a8fef8 331192 
duplicity_0.7.14-2_amd64.deb
Files:
 6330daf093f6230f427464f8743a4958 1877 utils optional duplicity_0.7.14-2.dsc
 e3eb6d7c99257d5ebf47d4dd6e1ccb19 14296 utils optional 
duplicity_0.7.14-2.debian.tar.xz
 04eb9b8d99ef4f3881b62cd74ba3977c 14356 debug optional 
duplicity-dbgsym_0.7.14-2_amd64.deb
 09823d6c0bdc0808993247e315656b55 8211 utils optional 
duplicity_0.7.14-2_amd64.buildinfo
 69deb48159c4bc2d22ef60487978f40b 331192 utils optional 
duplicity_0.7.14-2_amd64.deb

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJZ/BfbAAoJED06g4g30PqNJWoP/RMfsLJHLGjEZGv7WJLzIzwH

Bug#868975: marked as done (horizon: FTBFS: Test failures)

[Debian Bug Tracking System]

Your message dated Fri, 03 Nov 2017 07:19:40 +
with message-id 
and subject line Bug#868975: fixed in horizon 3:12.0.0-2
has caused the Debian Bug report #868975,
regarding horizon: FTBFS: Test failures
to be marked as done.

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

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


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

Hi,

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

Relevant part (hopefully):
>   File "/<>/openstack_dashboard/usage/base.py", line 22, in 
> 
> from horizon import forms
>   File "/<>/horizon/forms/__init__.py", line 29, in 
> from horizon.forms.fields import DynamicChoiceField  # noqa
>   File "/<>/horizon/forms/fields.py", line 363, in 
> class ThemableCheckboxChoiceInput(widgets.CheckboxChoiceInput):
> AttributeError: 'module' object has no attribute 'CheckboxChoiceInput'
> 
> --
> Ran 752 tests in 1.126s
> 
> FAILED (SKIP=1, errors=751)
>  OK
> Destroying test database for alias 'default' (':memory:')...
> Tests failed.
> debian/rules:60: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2017/07/19/horizon_10.0.1-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: horizon
Source-Version: 3:12.0.0-2

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated horizon package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 28 Oct 2017 21:14:53 +
Source: horizon
Binary: horizon-doc openstack-dashboard openstack-dashboard-apache 
python-django-horizon
Architecture: source all
Version: 3:12.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Description:
 horizon-doc - web application to control an OpenStack cloud - doc
 openstack-dashboard - web application to control an OpenStack cloud
 openstack-dashboard-apache - web application to control an OpenStack cloud - 
Apache support
 python-django-horizon - Django module providing web interaction with OpenStack
Closes: 862387 867254 868975
Changes:
 horizon (3:12.0.0-2) unstable; urgency=medium
 .
   * Uploading to unstable:
 - Fixes FTBFS (Closes: #868975).
 - Can be installed (Closes: #867254).
 - Delete instance in table works (Closes: #862387).
Checksums-Sha1:
 598d1d3cec452dbb2c2715bf666a9df3b3f51526 4588 horizon_12.0.0-2.dsc
 cfe12b62a1c504b0c19053128d69107cb86f0094 25360 horizon_12.0.0-2.debian.tar.xz
 0442fcf0fa64f5526c75c00646afb396c2894910 1869700 horizon-doc_12.0.0-2_all.deb
 78b7b68d4d945c75aa0c1d98629ea2e88365ebb9 18511 horizon_12.0.0-2_amd64.buildinfo
 4d5d3f80fdda91944849ccb52fcdbf6671951dce 13940 
openstack-dashboard-apache_12.0.0-2_all.deb
 18e71f21c74ca018566574d63d694de1ccbff02c 2230304 
openstack-dashboard_12.0.0-2_all.deb
 42bb31dd9d51d74391900b9b6049fb05bf0339ee 1995024 
python-django-horizon_12.0.0-2_all.deb
Checksums-Sha256:
 6afd551a624703aa758aee27ce67d8035efcdda14e6537d07558d00a4836f889 4588 
horizon_12.0.0-2.dsc
 0503e3e11d9dc6e0f4e7897dbc437fe2f22da488fa45e2d58fe6f13658b10e4f 25360 
horizon_12.0.0-2.debian.tar.xz
 e5d9e01abece91efab248e7fd3f7cfc180d4365360cad3d16ac798007a001338 1869700 
horizon-doc_12.0.0-2_all.deb

Bug#867254: marked as done (openstack-dashboard: fails to install: django.core.exceptions.ImproperlyConfigured: AUTH_USER_MODEL refers to model 'openstack_auth.User' that has not been installed)

[Debian Bug Tracking System]

Your message dated Fri, 03 Nov 2017 07:19:40 +
with message-id 
and subject line Bug#867254: fixed in horizon 3:12.0.0-2
has caused the Debian Bug report #867254,
regarding openstack-dashboard: fails to install: 
django.core.exceptions.ImproperlyConfigured: AUTH_USER_MODEL refers to model 
'openstack_auth.User' that has not been installed
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.)


-- 
867254: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867254
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openstack-dashboard
Version: 3:10.0.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + python-murano-dashboard python-sahara-dashboard 
python-zaqar-ui

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Setting up openstack-dashboard (3:10.0.1-1) ...
  Traceback (most recent call last):
File "/usr/share/openstack-dashboard/manage.py", line 25, in 
  execute_from_command_line(sys.argv)
File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", 
line 363, in execute_from_command_line
  utility.execute()
File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", 
line 337, in execute
  django.setup()
File "/usr/lib/python2.7/dist-packages/django/__init__.py", line 27, in 
setup
  apps.populate(settings.INSTALLED_APPS)
File "/usr/lib/python2.7/dist-packages/django/apps/registry.py", line 108, 
in populate
  app_config.import_models()
File "/usr/lib/python2.7/dist-packages/django/apps/config.py", line 202, in 
import_models
  self.models_module = import_module(models_module_name)
File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module
  __import__(name)
File "/usr/lib/python2.7/dist-packages/openstack_auth/models.py", line 15, 
in 
  from openstack_auth.user import User# noqa
File "/usr/lib/python2.7/dist-packages/openstack_auth/user.py", line 26, in 

  from openstack_auth import utils
File "/usr/lib/python2.7/dist-packages/openstack_auth/utils.py", line 20, 
in 
  from django.contrib.auth import middleware
File "/usr/lib/python2.7/dist-packages/django/contrib/auth/middleware.py", 
line 4, in 
  from django.contrib.auth.backends import RemoteUserBackend
File "/usr/lib/python2.7/dist-packages/django/contrib/auth/backends.py", 
line 6, in 
  UserModel = get_user_model()
File "/usr/lib/python2.7/dist-packages/django/contrib/auth/__init__.py", 
line 198, in get_user_model
  "AUTH_USER_MODEL refers to model '%s' that has not been installed" % 
settings.AUTH_USER_MODEL
  django.core.exceptions.ImproperlyConfigured: AUTH_USER_MODEL refers to model 
'openstack_auth.User' that has not been installed
  dpkg: error processing package openstack-dashboard (--configure):
   subprocess installed post-installation script returned error exit status 1


cheers,

Andreas


python-murano-dashboard_1:3.0.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: horizon
Source-Version: 3:12.0.0-2

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated horizon package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 28 Oct 2017 21:14:53 +
Source: horizon
Binary: horizon-doc openstack-dashboard openstack-dashboard-apache 
python-django-horizon
Architecture: source all
Version: 3:12.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Description:
 horizon-doc - web application to control an OpenStack cloud - doc
 openstack-dashboard - web application to control an OpenStack 

Bug#880251: duplicity: FTBFS: Test failures

[Alexander Zangerl]

On Mon, 30 Oct 2017 20:30:40 +0100, Lucas Nussbaum writes:
>About the archive rebuild: The rebuild was done on EC2 VM instances from
>Amazon Web Services, using a clean, minimal and up-to-date chroot.

hmm. the test suite code in question does set an appropriate $TZ
at the very start. i have no diea how that could have failed in
the chroot that you used for the archive build?

the very same code survives the tests just fine in a sid chroot
under pbuilder.

regards
az


-- 
Alexander Zangerl + GPG Key 2FCCF66BB963BD5F + http://snafu.priv.at/
"Militant *BSD users are frequently in favour of gnu control." -- Nix


signature.asc
Description: Digital Signature