Bug#870635: mutt package is not using the official mutt tarball

[Antonio Radici]

On Wed, Nov 08, 2017 at 09:52:06AM +, Jonathan Dowland wrote:
> On Thu, Aug 03, 2017 at 10:21:51PM +, Antonio Radici wrote:
> > as I said on the original thread I'm planning to fix this, and as you
> > can see there have been no new releases until the fix is in place.
> 
> It would be great if you could summarize *in this bug* what's your plan of
> action.
> 
> We are packaging neomutt, but calling it mutt. The obvious solution is to
> rename the package.  "mutt" could be used as transitional name to smoothly
> handle upgrades. This would not need to live for more than one release.
> 
> This would not proclude someone else from packaging "vanilla" mutt if they
> wanted to.

Sorry for the delay, my plan of action is to stop packaging neomutt with this
name, I'll create a new neomutt package (TBD by end of the month) and I'll think
if there is the need of a transitional package, the problem of a transitional
package is that mutt won't be packaged as mutt in stretch. To prevent that from
happening we will need two packages (mutt and neomutt) from two different
upstream sources.

So far the only thing which is certainly going to happen is the creation of the
neomutt package, then I could package the newest mutt as 'mutt' and think about
whether mutt needs to become a transitional package (which in that case will
remove mutt).

This is roughly my plan of action

Bug#876937: node-findit2: missing build dependency on node-mkdirp

[Petter Reinholdtsen]

Hi.  Any plans to upload a fix?  This bug just threw groovebasin out of
testing...
-- 
Happy hacking
Petter Reinholdtsen

Bug#881389: lintian: Incomplete solution to whitespace errors in file-contains-trailing-whitespace

[Stuart Prescott]

Package: lintian
Version: 2.5.59
Severity: normal

Dear Maintainer,

In lintian's tag file-contains-trailing-whitespace, the maintainer is told
that they can remove the offending whitespace with:

  sed -i -e 's@[ ]*$@@g' path/to/filename

However, that only removes trailing spaces, while trailing tabs will also
trigger the warning. The following sed would do better:

  sed -i -e 's@[[:space:]]*$@@g' path/to/filename

(it's also not obvious to me that the maintainer should be encouraged to edit
old changelog entries in this fashion)

cheers
Stuart

Bug#881301: gnome-shell: intermittent "invalid unclassed pointer in cast to 'ClutterText'" + segfault

[Lucas Dyer]

On Fri, 10 Nov 2017 at 14:03:23 +, Simon McVittie wrote:
> Are you using any GNOME Shell extensions? If so, which ones?

The following enabled gnome-shell-extensions and git tracked extensions:

Applications menu: gnome-shell-extensions (= 3.26.2-1)
Dash to dock:  (#e564630)
Native window placement: gnome-shell-extensions (= 3.26.2-1)
Topicons plus:  (#f265f17)
Volume mixer:  (#2bb8474)
System-monitor: 
 
(#61b0a60)

> Approximately how often does this crash occur?

Once or twice a day.

> We are very unlikely to be able to solve this without a backtrace. The bug
> appears to be that an invalid pointer is used where a ClutterText object
> is expected (most likely a use-after-free or a null pointer somewhere),
> but that isn't something that can be fixed without knowing where/how it
> happens.

Stack trace of thread 2528:
#0  0x7fc5bbf35db2 in g_type_check_instance_cast 
(type_instance=0x55ad84d82970, iface_type=94203710922992) at 
../../../../gobject/gtype.c:4057
#1  0x7fc5b96d67d8 in st_label_set_text (label=0x55ad84d82300 [StLabel], 
text=0x55ad87c75800 "100") at ../src/st/st-label.c:331
#2  0x7fc5bbf17a4e in object_set_property (nqueue=0x55ad854cd880, 
value=, pspec=0x55ad835365f0 [GParamString], 
object=0x55ad84d82300 [StLabel]) at ../../../../gobject/gobject.c:1439
#3  0x7fc5bbf17a4e in g_object_setv (object=0x55ad84d82300 [StLabel], 
n_properties=, names=, values=) at 
../../../../gobject/gobject.c:2245
#4  0x7fc5bbf189de in g_object_set_property (object=, 
property_name=, value=value@entry=0x7ffdbb82b058) at 
../../../../gobject/gobject.c:2529
#5  0x7fc5bac044b7 in set_g_param_from_prop (priv=0x55ad84cb8030, 
result=..., value_p=..., was_set=: , 
name=0x55ad82f75ae0 "text", context=0x55ad82f75ae0) at gi/object.cpp:446
#6  0x7fc5bac044b7 in object_instance_set_prop(JSContext*, 
JS::HandleObject, JS::HandleId, JS::MutableHandleValue, JS::ObjectOpResult&) 
(context=context@entry=0x55ad82eb1000, obj=..., id=..., id@entry=..., 
value_p=value_p@entry=..., result=...) at gi/object.cpp:521
#7  0x7fc5b1cb76c6 in js::CallJSSetterOp(JSContext*, bool (*)(JSContext*, 
JS::Handle, JS::Handle, JS::MutableHandle, 
JS::ObjectOpResult&), JS::Handle, JS::Handle, 
JS::MutableHandle, JS::ObjectOpResult&) (result=..., vp=..., id=..., 
obj=..., op=, cx=0x55ad82eb1000) at ./js/src/jscntxtinlines.h:323
#8  0x7fc5b1cb76c6 in NativeSetExistingDataProperty(JSContext*, 
js::HandleNativeObject, js::HandleShape, JS::HandleValue, JS::ObjectOpResult&) 
(cx=cx@entry=0x55ad82eb1000, obj=..., obj@entry=..., shape=..., v=..., 
v@entry=..., result=..., receiver=...) at ./js/src/vm/NativeObject.cpp:2198
#9  0x7fc5b1cccfeb in SetExistingProperty (result=..., shape=..., pobj=..., 
receiver=..., v=..., id=..., obj=..., cx=0x55ad82eb1000) at 
./js/src/vm/NativeObject.cpp:2406
#10 0x7fc5b1cccfeb in js::NativeSetProperty(JSContext*, 
JS::Handle, JS::Handle, JS::Handle, 
JS::Handle, js::QualifiedBool, JS::ObjectOpResult&) 
(cx=0x55ad82eb1000, obj=..., id=..., value=..., receiver=..., 
qualified=qualified@entry=js::Qualified, result=...) at 
./js/src/vm/NativeObject.cpp:2469
#11 0x7fc5b1cd9cbe in js::SetProperty(JSContext*, JS::Handle, 
JS::Handle, JS::Handle, JS::Handle, 
JS::ObjectOpResult&) (cx=, obj=..., id=..., v=..., receiver=..., 
result=...) at ./js/src/vm/NativeObject.h:1540
#12 0x7fc5b1cbd8f1 in SetPropertyOperation (rval=..., id=..., lval=..., 
op=, cx=) at ./js/src/vm/Interpreter.cpp:259
#13 0x7fc5b1cbd8f1 in Interpret(JSContext*, js::RunState&) 
(cx=0x55ad82eb1000, state=...) at ./js/src/vm/Interpreter.cpp:2715
#14 0x7fc5b1cc8846 in js::RunScript(JSContext*, js::RunState&) 
(cx=cx@entry=0x55ad82eb1000, state=...) at ./js/src/vm/Interpreter.cpp:405
#15 0x7fc5b1cc8e1f in js::InternalCallOrConstruct(JSContext*, JS::CallArgs 
const&, js::MaybeConstruct) (cx=cx@entry=0x55ad82eb1000, args=..., 
construct=construct@entry=js::NO_CONSTRUCT) at ./js/src/vm/Interpreter.cpp:477
#16 0x7fc5b1cc9099 in InternalCall(JSContext*, js::AnyInvokeArgs const&) 
(cx=cx@entry=0x55ad82eb1000, args=...) at ./js/src/vm/Interpreter.cpp:504
#17 0x7fc5b1cc90f9 in js::Call(JSContext*, JS::Handle, 
JS::Handle, js::AnyInvokeArgs const&, JS::MutableHandle) 
(cx=cx@entry=0x55ad82eb1000, fval=..., fval@entry=..., thisv=..., 
thisv@entry=..., args=..., rval=rval@entry=...) at 
./js/src/vm/Interpreter.cpp:523
#18 0x7fc5b1abb079 in js::jit::InvokeFunction(JSContext*, 
JS::Handle, bool, unsigned int, JS::Value*, 
JS::MutableHandle) (cx=0x55ad82eb1000, obj=..., 
constructing=, argc=, argv=0x7ffdbb82bc10, 
rval=...) at ./js/src/jit/VMFunctions.cpp:114
#19 0x2d2f6b08d3c6 in  ()
#20 0x in  ()

Bug#881388: qtxmlpatterns-opensource-src FTCBFS: does not pass cross tools to qmake

[Helmut Grohne]

Source: qtxmlpatterns-opensource-src
Version: 5.9.2-3
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

qtxmlpatterns-opensource-src fails to cross build from source, because
it does not pass cross tools to qmake. Letting dh_auto_configure doing
so makes the configure step (but not the build step) succeeed. Please
consider applying the attached patch and closing this bug when doing so.

Helmut
diff --minimal -Nru qtxmlpatterns-opensource-src-5.9.2/debian/changelog 
qtxmlpatterns-opensource-src-5.9.2/debian/changelog
--- qtxmlpatterns-opensource-src-5.9.2/debian/changelog 2017-10-26 
22:34:51.0 +0200
+++ qtxmlpatterns-opensource-src-5.9.2/debian/changelog 2017-11-11 
07:17:44.0 +0100
@@ -1,3 +1,10 @@
+qtxmlpatterns-opensource-src (5.9.2-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Let dh_auto_configure pass cross tools to qmake. (Closes: #-1)
+
+ -- Helmut Grohne   Sat, 11 Nov 2017 07:17:44 +0100
+
 qtxmlpatterns-opensource-src (5.9.2-3) unstable; urgency=medium
 
   * Really upload to unstable.
diff --minimal -Nru qtxmlpatterns-opensource-src-5.9.2/debian/rules 
qtxmlpatterns-opensource-src-5.9.2/debian/rules
--- qtxmlpatterns-opensource-src-5.9.2/debian/rules 2017-10-26 
22:34:51.0 +0200
+++ qtxmlpatterns-opensource-src-5.9.2/debian/rules 2017-11-11 
07:17:43.0 +0100
@@ -14,7 +14,7 @@
dh $@ --with pkgkde_symbolshelper
 
 override_dh_auto_configure:
-   qmake QT_BUILD_PARTS+=tests
+   dh_auto_configure -- QT_BUILD_PARTS+=tests
 
 override_dh_auto_build-indep:
dh_auto_build -- docs

Bug#881387: Please remove, this is a duplicate of 881386

[Michael Serafino]

Hello,

I accidentally submitted this twice. The first submission is 881386. Please
remove this (881387) report.

Thanks,

-- 
Michael

Bug#881387: installation-reports: Successful install of debian-live-9.2.0-amd64-gnome.iso on Clevo N130WU laptop

[Michael Serafino]

Package: installation-reports
Severity: wishlist

Dear Maintainer,

Hardware:

1. Barebones Clevo N130WU

Purchased November 2017

Barebones = does not have hard drive, ram, wifi card.

2. Samsung 850 EVO 500GB 2.5-Inch SATA III Internal SSD (MZ-75E500B/AM)

3. Crucial 32GB Kit (16GBx2) DDR4 2400 MT/s (PC4-19200) DR x8 Unbuffered SODIMM
260-Pin Memory - CT2K16G4SFD824A

4. Intel Wifi Wireless-AC 8265 8265.NGWMG Dual Band 2x2 AC + BlueTooth M.2

This required manual driver installation. There may be some existing
packages containing these drivers. I did not look very hard.

Wifi:

Seached here first:

https://www.intel.com/content/www/us/en/support/articles/05511/network-and-
i-o/wireless-networking.html

Link to driver I downloaded:

https://wireless.wiki.kernel.org/_media/en/users/drivers/iwlwifi-8265-ucode-22.361476.0.tgz

Bluetooth:

https://github.com/wkennington/linux-
firmware/blob/master/intel/ibt-12-16.sfi

Important installation notes:

1. I had to disable the UEFI boot option, otherwise the live usb stick
was never detected.

1.a. Press F2 to enter the BIOS.

2. Trackpad did not work during installation.

Features tested and functional:

1. Trackpad. I only tested two finger scrolling.

2. Keyboard key backlight adjustment.

3. Keyboard screen backlight adjustment.

4. Keyboard sleep button.

5. Clamshell sleep (close laptop). Suspend/resume appears to work (has
not crashed yet).

6. HDMI port.

7. Webcam and microphone (tested/saved video with cheese).

8. Keyboard volume/mute buttons.

Features not tested:

1. Mini display port.

2. usb-c port.

3. SD card reader.

4. Keyboard 'airplane mode' button.

5. Microphone and headphone jack inputs.



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

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

Bug#881386: installation-reports: Successful install of debian-live-9.2.0-amd64-gnome.iso on Clevo N130WU laptop

[Michael Serafino]

Package: installation-reports
Severity: wishlist

Dear Maintainer,

Hardware:

1. Barebones Clevo N130WU

Purchased November 2017

Barebones = does not have hard drive, ram, wifi card.

2. Samsung 850 EVO 500GB 2.5-Inch SATA III Internal SSD (MZ-75E500B/AM)

3. Crucial 32GB Kit (16GBx2) DDR4 2400 MT/s (PC4-19200) DR x8 Unbuffered SODIMM
260-Pin Memory - CT2K16G4SFD824A

4. Intel Wifi Wireless-AC 8265 8265.NGWMG Dual Band 2x2 AC + BlueTooth M.2

This required manual driver installation. There may be some existing
packages containing these drivers. I did not look very hard.

Wifi:

Seached here first:

https://www.intel.com/content/www/us/en/support/articles/05511/network-and-
i-o/wireless-networking.html

Link to driver I downloaded:

https://wireless.wiki.kernel.org/_media/en/users/drivers/iwlwifi-8265-ucode-22.361476.0.tgz

Bluetooth:

https://github.com/wkennington/linux-
firmware/blob/master/intel/ibt-12-16.sfi

Important installation notes:

1. I had to disable the UEFI boot option, otherwise the live usb stick
was never detected.

1.a. Press F2 to enter the BIOS.

2. Trackpad did not work during installation.

Features tested and functional:

1. Trackpad. I only tested two finger scrolling, I'm not sure what else
to do.

2. Keyboard key backlight adjustment.

3. Keyboard screen backlight adjustment.

4. Keyboard sleep button.

5. Clamshell sleep (close laptop). Suspend/resume appears to work (has
not crashed yet).

6. HDMI port.

7. Webcam and microphone (tested/saved video with cheese).

8. Keyboard volume/mute buttons.

Features not tested:

1. Mini display port.

2. usb-c port.

3. SD card reader.

4. Keyboard 'airplane mode' button.

5. Microphone and headphone jack inputs.



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

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

Bug#881385: RFS: cligh/0.3-1.1 [ITA] -- Command-line interface to GitHub

[eamanu15 .]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "cligh"

 * Package name: cligh
   Version : 0.3-1.1
 * URL :  https://github.com/eamanu/cligh

 * License :  Copyright (c) 2010 Christopher M. Brannon

This upload fixes thr RFA (#851186),
so please consider sponsoring it soon.


The package can be found on mentors.d.n:

  https://mentors.debian.net/package/cligh


Alternatively, one can download the package with dget using this command:

dget -x
https://mentors.debian.net/debian/pool/main/c/cligh/cligh_0.3-1.1.dsc


For more information you can visit:
http://the-brannons.com/software/cligh.html

Regards
Emmanuel
-- 
Arias Emmanuel
http://eamanu.com

Bug#879718: aptly: Aptly can't handle deb packages built using dpkg 1.19.0+

[Boyuan Yang]

Control: tags -1 - buster

Hello,

Glad to see that this bug is fixed in Debian unstable/testing.

However, aptly in Stretch and Jessie are still left unfixed. Will you backport 
the patch and provide stable updates later?

Regards,
Boyuan Yang

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

Bug#881100: [Pkg-samba-maint] Bug#881100: libnss-winbind is not multiarch safe

[Matthew Gabeler-Lee]

On Fri, 10 Nov 2017, Mathieu Parent wrote:


This looks similar to #647430 which was solved in 2:4.6.5+dfsg-6.

Can you test from sid?


While that is likely a necessary component to fixing this, it is not 
sufficient.  That fixes a script error, this ticket is about package 
dependency errors between the various binary packages from the Samba 
source package.


Trying to install both "PC" architectures of libnss-winbind produces 
this error when targeting sid (which is basically the same as when targeting

stable or buster, just different package versions referenced):

The following packages have unmet dependencies:
 libnss-winbind : Depends: samba-libs (= 2:4.7.1+dfsg-1) but it is not going to 
be installed
  Depends: winbind (= 2:4.7.1+dfsg-1) but it is not going to be 
installed
 libnss-winbind:i386 : Depends: samba-libs:i386 (= 2:4.7.1+dfsg-1) but it is 
not going to be installed
   Depends: winbind:i386 (= 2:4.7.1+dfsg-1) but it is not 
going to be installed

You can't co-install multiple architectures of the winbind daemon, of
course.  I'm not an expert on Debian packaging, but I believe that could be
solved by changing the dependency there to be "arch any", since it just
needs to have the daemon be installed to communicate with it, not
necessarily have the daemon of the same architecture be running.  Though I
don't know if the local socket/pipe protocol it uses is maybe
architecture-specific (e.g. binary packed stuff that is dependent on the
cpu arch), so there might still be problems there.

The samba-libs problem seems to be related to samba-libs depending on
python-talloc, which is #862338.  As I noted before I'm not sure
libnss-winbind actually needs to depend on samba-libs at all, though I'm not
really sure of that.  Running strings on the shared libs shipped in
libnss-winbind doesn't find anything that looks like it's trying to dlopen
libraries from samba-libs, nor does it link against them directly.

--
-Matt
"Reality is that which, when you stop believing in it, doesn't go away".
-- Philip K. Dick
GPG fingerprint: 0061 15DF D282 D4A9 57CE  77C5 16AF 1460 4A3C C4E9

Bug#881384: dpkg man page contains a typo in "--validate-thing string" option description

[Alex]

Package: dpkg
Version: 1.18.24
Severity: minor

Hey

"--validate-thing string" option of dpkg man page lists "pkgname" twice for
package name and architecture name. This is probably a typo.
Will try to attach a screenshot.

Found in 'stable' dpkg version 1.18.24. Haven't checked in 'testing' and
'unstable'.

Best Regards,
Alex.




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

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

Versions of packages dpkg depends on:
ii  libbz2-1.0   1.0.6-8.1
ii  libc62.24-11+deb9u1
ii  liblzma5 5.2.2-1.2+b1
ii  libselinux1  2.6-3+b3
ii  tar  1.29b-1.1
ii  zlib1g   1:1.2.8.dfsg-5

dpkg recommends no packages.

Versions of packages dpkg suggests:
ii  apt1.4.8
pn  debsig-verify  

-- no debconf information

Bug#881310: systemd-container: systemd-nspawn containers get non-functioning /etc/resolv.conf

[Michael Biebl]

Control: fixed -1 234-1

Am 11.11.2017 um 00:33 schrieb Alex King:
> Looking at the code ("src/nspawn/nspawn.c" in v232), it appears that the 
> existence of /usr/lib/systemd/resolv.conf, which exists on the 
> problematic system, is triggering the problem.

Ok, I had another look. In v232, the check if resolved is active is

if (access("/usr/lib/systemd/resolv.conf", F_OK) >= 0) {

in later releases it is

if (access("/usr/lib/systemd/resolv.conf", F_OK) >= 0 &&
resolved_listening() > 0) {

The mere existence of resolve.conf is not sufficient to determine,
whether systemd-resolved is active or not. The only reason why other
systems are not afficient is the broken check which tests for the
resolv.conf in /usr (I've filed
https://github.com/systemd/systemd/issues/7302 for that). You simply
dodged that bullet by not having a /usr/lib/systemd/resolv.conf.

So, this particular stretch system of yours seems to be in a strange
state, if it has a /usr/lib/systemd/resolv.conf.

That said, there are two bugs in systemd-nspawn:

a/ the hard-coded path for the resolv.conf check
https://github.com/systemd/systemd/issues/7302

b/ not checking whether resolved is actually active
Fixed by
https://github.com/systemd/systemd/commit/7357272ed1c2c7a139c9ecbc8f3b8f63f71dd0b0

I'm thus marking this particular issue as fixed in v234

a/ still needs to be addressed.

Thanks for your detailed reply.

Michael

-- 
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#881310: systemd-container: systemd-nspawn containers get non-functioning /etc/resolv.conf

[Michael Biebl]

Am 11.11.2017 um 00:33 schrieb Alex King:
> Looking at the code ("src/nspawn/nspawn.c" in v232), it appears that the 
> existence of /usr/lib/systemd/resolv.conf, which exists on the 
> problematic system, is triggering the problem.

Actually, that points at another problem:
With split-usr (as Debian/Ubuntu uses), the location of resolv.conf is
/lib/systemd/resolv.conf. Which in turn means, systemd-nspawn should not
hard-code that and use /lib/systemd/resolv.conf for split-usr systems.
Either that, or we need to fix the build system to always install
resolv.conf at /usr/lib/systemd/resolv.conf.

As for your question, how this file got there: Did you install systemd
from source in the past?


-- 
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#881310: systemd-container: systemd-nspawn containers get non-functioning /etc/resolv.conf

[Michael Biebl]

Am 11.11.2017 um 00:58 schrieb Michael Biebl:

> As for your question, how this file got there: Did you install systemd
> from source in the past?

What does dpkg -S /usr/lib/systemd/resolv.conf say?


-- 
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#881383: systemsettings: Touchpad settings don't actually work

[Ben Longbons]

Package: systemsettings
Version: 4:5.8.4-1
Severity: normal

Dear Maintainer,

In Hardware->Input Devices->Touchpad->Enable/Disable Touchpad:

There is a checkbox "Disable touchpad while typing". However,
even when unchecked (and the system restarted), the touchpad
still disables itself whenever any key is pressed.


Debugging on IRC produced the following observations:

evtest *does* show touchpad events when keys are pressed
but xev does not
and libinput-debug-events does not
(libinput-debug-events --disable-dwt does, however).

libinput-list-devices mentions: Disable-w-typing: enabled

So apparently this is a driver switch or something? Where KDE is only
applying the settings to the driver that isn't actually used anymore.


-- 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/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages systemsettings depends on:
ii  kio   5.28.0-2
ii  libc6 2.24-11+deb9u1
ii  libkf5auth5   5.28.0-2
ii  libkf5completion5 5.28.0-1
ii  libkf5configcore5 5.28.0-2
ii  libkf5configgui5  5.28.0-2
ii  libkf5configwidgets5  5.28.0-2
ii  libkf5coreaddons5 5.28.0-2
ii  libkf5dbusaddons5 5.28.0-1
ii  libkf5i18n5   5.28.0-2
ii  libkf5iconthemes5 5.28.0-2
ii  libkf5itemviews5  5.28.0-1
ii  libkf5kcmutils5   5.28.0-2
ii  libkf5khtml5  5.28.0-2
ii  libkf5kiowidgets5 5.28.0-2
ii  libkf5service-bin 5.28.0-1
ii  libkf5service55.28.0-1
ii  libkf5widgetsaddons5  5.28.0-3
ii  libkf5windowsystem5   5.28.0-2
ii  libkf5xmlgui5 5.28.0-1
ii  libqt5core5a  5.7.1+dfsg-3+b1
ii  libqt5dbus5   5.7.1+dfsg-3+b1
ii  libqt5gui55.7.1+dfsg-3+b1
ii  libqt5widgets55.7.1+dfsg-3+b1
ii  libstdc++66.3.0-18

systemsettings recommends no packages.

systemsettings suggests no packages.

-- no debconf information

Bug#881310: systemd-container: systemd-nspawn containers get non-functioning /etc/resolv.conf

[Alex King]

Looking at the code ("src/nspawn/nspawn.c" in v232), it appears that the 
existence of /usr/lib/systemd/resolv.conf, which exists on the 
problematic system, is triggering the problem.


Not sure how that resolv.conf file got there.

$ ls /usr/lib/systemd/
boot  systemd-hostnamed systemd-shutdown
catalog   systemd-import systemd-sleep
import-pubring.gpg    systemd-importd systemd-socket-proxyd
libsystemd-shared-232.so  systemd-initctl systemd-sysctl
network   systemd-journald systemd-sysv-install
ntp-units.d   systemd-localed systemd-timedated
resolv.conf   systemd-logind systemd-timesyncd
system    systemd-machined systemd-udevd
systemd   systemd-modules-load systemd-update-utmp
systemd-ac-power  systemd-networkd systemd-user-sessions
systemd-backlight systemd-networkd-wait-online system-generators
systemd-binfmt    systemd-pull system-preset
systemd-cgroups-agent systemd-quotacheck system-shutdown
systemd-cryptsetup    systemd-random-seed   system-sleep
systemd-export    systemd-remount-fs    user
systemd-fsck  systemd-reply-password user-generators
systemd-fsckd systemd-resolved
systemd-hibernate-resume  systemd-rfkill

looks like everything that should be in /lib/systemd and 
/usr/lib/systemd is duplicated in both places?!  I guess that is most 
likely a sysadmin typo, although the system was reloaded relatively 
recently and I have no idea how this could have happened.


So I guess this bug could be closed.

Thanks for your help.

Alex

On 11/11/17 11:37, Michael Biebl wrote:

Am 10.11.2017 um 23:05 schrieb Alex King:

$ sudo systemctl status systemd-resolved.service
● systemd-resolved.service - Network Name Resolution
    Loaded: loaded (/lib/systemd/system/systemd-resolved.service;
disabled; vendo
   Drop-In: /usr/lib/systemd/system/systemd-resolved.service.d
    └─resolvconf.conf

Hm, where is this file coming from? It's certainly not from systemd. It
doesn't seem to be coming from Debian either (at least apt-file search
/usr/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf does
not yield any results).

Do you have any custom packages/software in that VPS which might interfere?

Michael

Bug#879783: Removing dino from multimedia-blends

[Ralf Jung]

Hi Ross,

On 10.11.2017 20:18, Ross Gammon wrote:
> Control: tags -1 pending
> 
> Hi Ralf,
> 
> I have pushed a change to git removing dino from multimedia-blends. I
> will do an upload sometime soon.

Thanks!

> But don't you think it is a bit early to introduce a new/different
> package with the same name as dino?

That was also the opinion of others, so the package is now called
dino-im: 

Kind regards,
Ralf

Bug#852127: qcontrol on Qnap TS-219P+

[basti]

Hello,
i have found this and try files from git Release 0.5.5-2.

On my device it won't start correctly. See Attachment.
System is stretch 9.2.

Best Regards,
Basti

--- qcontrold.service.orig	2017-11-10 23:38:22.0 +0100
+++ qcontrold.service	2017-11-10 23:39:02.190230094 +0100
@@ -1,9 +1,11 @@
 [Unit]
 Description=qcontrold
-Requires=dev-input-by\x2dpath-platform\x2dgpio\x2dkeys\x2devent.device
-After=dev-input-by\x2dpath-platform\x2dgpio\x2dkeys\x2devent.device
+Requires=dev-input\x2dby-path\x2dplatform-gpio_keys-event.device
 # If the config file is there, we assume qcontrol works on this machine.
 ConditionPathExists=/etc/qcontrol.conf
 
 [Service]
 ExecStart=/usr/sbin/qcontrol -f
+
+[Install]
+WantedBy=multi-user.target
--- qcontrol.service.orig	2017-11-10 23:30:59.0 +0100
+++ qcontrol.service	2017-11-10 23:14:21.0 +0100
@@ -2,6 +2,7 @@
 Description=qcontrol
 # If the config file is there, we assume qcontrol works on this machine.
 ConditionPathExists=/etc/qcontrol.conf
+After=multi-user.target qcontrold.service
 
 [Service]
 Type=oneshot

Bug#881336: dockerization of sympa impossible with current packaging

[Marc Chantreux]

hello,

thanks to the help of racke and kolter on the freenode #sympa channel,
i have a sympa installed from buster packages in a docker.

https://github.com/sympa-community/sympa-docker/tree/master/registry/sympa:buster

i also tried to help about the invoke-rc.d thing. see the pactch in
attachement

many thanks for help

regards
diff --git a/debian/sympa.logrotate b/debian/sympa.logrotate
index 2a7ca96..c5380dc 100644
--- a/debian/sympa.logrotate
+++ b/debian/sympa.logrotate
@@ -7,11 +7,13 @@
 delaycompress
 create 640 sympa adm
 postrotate
-if [ -e /proc/1/exe ] && readlink -f /proc/1/exe | grep -q 'systemd' ; then
-systemctl try-reload-or-restart sympa
-else
-invoke-rc.d --quiet sympa reload > /dev/null
-fi
-invoke-rc.d --quiet rsyslog rotate > /dev/null || true
+grep -q /docker /proc/self/cgroup || {
+if [ -e /proc/1/exe ] && readlink -f /proc/1/exe | grep -q 'systemd' ; then
+systemctl try-reload-or-restart sympa
+else
+invoke-rc.d --quiet sympa reload > /dev/null
+fi
+invoke-rc.d --quiet rsyslog rotate > /dev/null || true
+}
 endscript
 }
diff --git a/debian/sympa.postinst b/debian/sympa.postinst
index fa1618d..324e9c0 100644
--- a/debian/sympa.postinst
+++ b/debian/sympa.postinst
@@ -78,13 +78,15 @@ fi
 # Stop the daemon if it has already been started This is necessary when you run
 # dpkg-reconfigure
 if [ "$1" = "configure" ]; then
-if [ -f /etc/init.d/sympa ]; then
-if which invoke-rc.d >/dev/null 2>&1; then
-invoke-rc.d sympa stop || true
-else
-/etc/init.d/sympa stop || true
+grep -q /docker /proc/self/cgroup || {
+if [ -f /etc/init.d/sympa ]; then
+if which invoke-rc.d >/dev/null 2>&1; then
+invoke-rc.d sympa stop || true
+else
+/etc/init.d/sympa stop || true
+fi
 fi
-fi
+}
 fi
 
 # Install sympa.conf

Bug#828960: closed by Dmitry Smirnov <only...@debian.org> (Bug#828960: fixed in gnumeric 1.12.35-1)

[Antonio Ospite]

On Tue, 07 Nov 2017 04:21:04 +
ow...@bugs.debian.org (Debian Bug Tracking System) wrote:

> This is an automatic notification regarding your Bug report
> which was filed against the gnumeric package:
> 
> #828960: gnumeric: missing-pkgconfig-dependency libspreadsheet-1.12 => 
> libgsf-1
> 
> It has been closed by Dmitry Smirnov .
> 
[...]
>* Suggests += "libgsf-1-dev" (Closes: #828960).

Just a comment: the change improves the situation as it suggests a
solution, however by default adequate still gives the message.

I guess it's not worth spending too much time to fix this, so I am
accepting the resolution.

Thanks Dmitry.

Ciao,
   Antonio

-- 
Antonio Ospite
https://ao2.it
https://twitter.com/ao2it

A: Because it messes up the order in which people normally read text.
   See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?

Bug#881126: Hostname Change

[Info Pretecs]

Hello,

The hostname for this mirror has been changed to 
debian.ca-west.mirror.fullhost.com.

Archive-http: http://debian.ca-west.mirror.fullhost.com/debian/

Thanks,

Bug#881382: libtool-bin: --mode=execute overwrites rather than prepends to LD_LIBRARY_PATH

[Paul "LeoNerd" Evans]

Package: libtool-bin
Version: 2.4.6-2
Severity: normal

I am developing a C library, which executes its unit tests as C files
using

  libtool --mode=execute ...

This has to affect the value of LD_LIBRARY_PATH to ensure the executable
for the test uses the newly-compiled library. Fair enough.

Problem is, it doesn't respect an existing value for this variable and
instead totally overwrites the old value, causing things that should be
findable to not be.

This matters, because I am in fact developing two C libraries, one that
depends on the other. When I

  make install PREFIX=$HOME

the lower library it lives in $HOME/lib and therefore I have to use
LD_LIBRARY_PATH to make sure the second library can find it at runtime.
Real programs can find it, but the unit tests for the second library
cannot, because `libtool --mode=execute` has overwritten the value
there.

To fix this, it simply has to ensure that it prepends to, rather than
overwrites, during its setup shell script.


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
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: systemd (via /run/systemd/system)

Versions of packages libtool-bin depends on:
ii  libtool  2.4.6-2

libtool-bin recommends no packages.

libtool-bin suggests no packages.

-- no debconf information


-- 
Paul "LeoNerd" Evans

leon...@leonerd.org.uk  |  https://metacpan.org/author/PEVANS
http://www.leonerd.org.uk/  |  https://www.tindie.com/stores/leonerd/

Bug#881381: O: jeepyb -- tools for managing gerrit projects and external sources

[Mathieu Parent]

Package: wnpp
Severity: normal
Control: block -1 by 881380

I intend to orphan the jeepyb package.

The package description is:
 jeepyb is a collection of tools which make managing a gerrit easier.
 .
 Specifically, management of gerrit projects and their associated upstream
 integration with things like github, launchpad, and storyboard.

I don't use gerrit anymore (moved to gitlab).

Note that jeepyb depends on gerritlib which I have also orphaned in #881380
and which is RC-buggy with #880230.

Regards

Mathieu Parent

Bug#880230: gerritlib: build depends on python{,3}-pbr (< 2.0) but 3.1.1-2 is to be installed

[Mathieu Parent]

2017-11-07 13:12 GMT+01:00 Adrian Bunk :
> On Tue, Nov 07, 2017 at 09:45:49AM +0100, Mathieu Parent wrote:
[...]
>> I will ask for a removal (of gerritlib and jeepyb) unless someone step
>> in within a month as max(popcon[2 years])=4.
>
> People tend to not step up based on a comment made in some bug.
>
> Orphaning packages is the proper way to make it visible that a new
> maintainer is required (this also automatically lists them in the
> weekly WNPP email sent to debian-devel).

You are right. Done "O" in #881380.

Regards

-- 
Mathieu Parent

Bug#881380: O: gerritlib

[Mathieu Parent]

Package: wnpp
Severity: normal

Hello,

I don't use gerrit anymore. This python module was packaged as a dependency of
jeepyb.

Given the RC bug #880230, I will remove this package before buster if no one
adopt it.

Regards

Mathieu Parent

Bug#881310: systemd-container: systemd-nspawn containers get non-functioning /etc/resolv.conf

[Michael Biebl]

Am 10.11.2017 um 23:05 schrieb Alex King:
> $ sudo systemctl status systemd-resolved.service
> ● systemd-resolved.service - Network Name Resolution
>    Loaded: loaded (/lib/systemd/system/systemd-resolved.service;
> disabled; vendo
>   Drop-In: /usr/lib/systemd/system/systemd-resolved.service.d
>    └─resolvconf.conf

Hm, where is this file coming from? It's certainly not from systemd. It
doesn't seem to be coming from Debian either (at least apt-file search
/usr/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf does
not yield any results).

Do you have any custom packages/software in that VPS which might interfere?

Michael

-- 
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#881352: [Pkg-utopia-maintainers] Bug#881352: udisks2: Breaks installation with kernel panic

[Michael Biebl]

Am 10.11.2017 um 23:09 schrieb André Esteves:
> Every time I do 'dpkg --configure -a' he starts by installing udisks2
> package it breaks and the kernel panics...

Can you provide a more complete kernel log from around the crash


-- 
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#881310: systemd-container: systemd-nspawn containers get non-functioning /etc/resolv.conf

[Alex King]

Interesting.

I tried to reproduce this myself on another machine and could not.  It 
may be peculiar to this machine which is a VPS in xen.


Neither host nor guest is running resolved:

$ sudo systemctl status systemd-resolved.service
● systemd-resolved.service - Network Name Resolution
   Loaded: loaded (/lib/systemd/system/systemd-resolved.service; 
disabled; vendo

  Drop-In: /usr/lib/systemd/system/systemd-resolved.service.d
   └─resolvconf.conf
   Active: inactive (dead)
 Docs: man:systemd-resolved.service(8)
http://www.freedesktop.org/wiki/Software/systemd/resolved
http://www.freedesktop.org/wiki/Software/systemd/writing-network-conf
http://www.freedesktop.org/wiki/Software/systemd/writing-resolver-cli

(in the "host")

In the guest:

# cat /etc/resolv.conf
# This is a static resolv.conf file for connecting local clients to
# systemd-resolved via its DNS stub listener on 127.0.0.53.
#
# Third party programs must not access this file directly, but only 
through the

# symlink at /etc/resolv.conf. To manage resolv.conf(5) in a different way,
# replace this symlink by a static file or a different symlink.
#
# See systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.

nameserver 127.0.0.53

I'll dig further to find out how nspawn determines whether it should 
replace resolv.conf


Thanks,
Alex


On 10/11/17 15:28, Michael Biebl wrote:

Control: tags -1 + moreinfo

Am 10.11.2017 um 01:10 schrieb Alex King:

After installing the package to get systemd-nspawnd, I created an etch
image with:

# cd /var/lib/machines
# debootstrap --variant=minbase --no-check-gpg --arch=i386 etch etchruby \
http://archive.debian.org/debian/

This system can't resolve DNS names:

# systemd-nspawn --directory etchruby/
Spawning container etchruby on /var/lib/machines/etchruby.
Press ^] three times within 1s to kill container.
etchruby:~# apt-get update
Err http://archive.debian.org etch Release.gpg
   Temporary failure resolving 'archive.debian.org'
Failed to fetch http://archive.debian.org/debian/dists/etch/Release.gpg  
Temporary failure resolving 'archive.debian.org'
Reading package lists... Done
E: Some index files failed to download, they have been ignored, or old ones 
used instead.

/etc/resolv.conf inside the container is apparently bind-mounted from the
host's /lib/systemd/resolv.conf, and cannot be modified inside the container.

I can't reproduce the problem. I don't have systemd-resolved enabled
though. My guess is that you have resolved enabled (but not properly
configured), that's why systemd-nspawn picks up /lib/systemd/resolv.conf

How does your /etc/resolv.conf look like in the container?

Bug#881379: RFP: xul-ext-cardbook -- Thunderbird address book based on the CardDAV and vCard

[W. Martin Borgert]

Package: wnpp
Severity: wishlist

* Package name: xul-ext-cardbook
  Version : 23.6
  Upstream Author : Philippe Vigneau
* URL : https://github.com/CardBook/CardBook
* License : MPL-2.0
  Programming Lang: JavaScript
  Description : Thunderbird address book based on the CardDAV and vCard

Features
 - Autocompletion in mail address fields and Lightning calendar fields
 - Easy CardDAV synchronisation!
 - Access to all vCard data!
 - Customizable data fields!

Note: This is similar to xul-ext-sogo-connector, but some users
say, that cardbook were more reliable and had more features.

Bug#860743: [Pkg-samba-maint] Processed: #860743

[Will Aoki]

On Fri, Nov 10, 2017 at 11:12:18PM +0100, Mathieu Parent wrote:
> Is this reproducible on Debian stretch?

I don't know yet, as I haven't gotten that particular system upgraded
yet, but I plan to do so before the year is out.

Bug#881378: ITP: benchmark -- Microbenchmark support library

[Anton Gladky]

Package: wnpp
Severity: wishlist
Owner: Anton Gladky 

* Package name: benchmark
  Version : 1.3.0
* URL : https://github.com/google/benchmark
* License : Apache-2.0
  Programming Lang: C++
  Description : Microbenchmark support library

Library to support the benchmarking of functions, similar to unit-tests.
https://github.com/google/benchmark/blob/master/README.md

The package will be maintained under the roof of Debian Science Team.

Anton

Bug#860743: [Pkg-samba-maint] Processed: #860743

[Mathieu Parent]

2017-11-10 19:21 GMT+01:00 Debian Bug Tracking System :
> Processing commands for cont...@bugs.debian.org:
>
>> found #860743 2:4.2.14+dfsg-0+deb8u8
> Bug #860743 [samba] samba: smbd fails to reap a few zombie processes
> Marked as found in versions samba/2:4.2.14+dfsg-0+deb8u8.

Hello Will Aoki,

Is this reproducible on Debian stretch?

Regards

-- 
Mathieu Parent

Bug#734862: [git-buildpackage/master] git-pbuilder: handle --help

[Guido Günther]

tag 734862 pending
thanks

Date:   Fri Nov 10 22:47:50 2017 +0100
Author: Guido Günther 
Commit ID: 876ebb35af7be82e0878d4d698984b82fb095391
Commit URL: 
https://git.sigxcpu.org/cgit/git-buildpackage//commit/?id=876ebb35af7be82e0878d4d698984b82fb095391
Patch URL: 
https://git.sigxcpu.org/cgit/git-buildpackage//patch/?id=876ebb35af7be82e0878d4d698984b82fb095391

git-pbuilder: handle --help

Closes: #734862

  

Bug#881353: [Pkg-samba-maint] Bug#881353: smb.conf: client max protocol = default limits connections to SMB1

[Mathieu Parent]

Control: fixed -1

2017-11-10 18:06 GMT+01:00 wolfgang :
> Package: samba-common
> Version: 2:4.5.12+dfsg-2
> Severity: normal
>
> Dear Maintainer,

Hello,
[...]
> According to the man page: "The value default refers to NT1."
> AFAIK NT1 means SMB1, so the default setting limits the client to SMB1.
> And if the server doesn't support SMB1 the connection doesn't work.
>
> A soulution is to set "client max protocol = SMB3" in /etc/samba/smb.conf (or 
> in ~/.smb/smb.conf.append).

Yes.

> However this only works if samba-common is installed. In my case it wasn't 
> installed.
> I think Thunar doesn't need it since it uses libsmbclient.

You only need a two lines smb.conf (created by hand, without samba-common):
  [global]
  client max protocol = SMB3

> So for network shares to work out of the box I think this needs to be fixed, 
> ideally in a way
> that makes libsmbclient work without the need for /etc/samba/smb.conf 
> (samba-common).

This is fixed in 4.7 by commit
1199907cbe2f003a7df6f56e6cf3878d0732344d and is in Debian testing. We
won't do this for stretch as this is not a stability or security fix.

Regards

Mathieu Parent

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

[Aaron M. Ucko]

Nicholas D Steeves  writes:

> I've uploaded irony-mode_1.2.0-2~exp1_amd64.  I'm giving LLVM+Clang a
> try with the new package, as I've read that MacOS users must use Clang
> rather than GCC...and I suspect that switching to LLVM+Clang might
> close this bug (hypothesis: error on mips64 and arm64 only exists when
> building with GCC).  Also, I suspect that upstream intends
> irony-server to be compiled with clang ;-)

Interesting idea.

This change does seem to have helped for arm64, but the jury's still out
on mips64el.  However, I see new failures on amd64 and s390x, and builds
for many architectures (albeit all non-release ones) can no longer even
start because clang is unavailable there.  As such, I'd recommend
building with (and build-depending on) clang only on those architectures
on which GCC builds hit errors.

On the Mac front, Clang has indeed been the only compiler Apple's
official Development Tools package supports for years (briefly preceded
by LLVM GCC), but GCC does still support the platform and is available
through third-party package managers such as Fink.

At any rate, thanks for looking into the errors!

-- 
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#881377: override: libqtav1:libs/optional, libqtavwidgets1:libs/optional

[Pino Toscano]

Package: ftp.debian.org
Severity: normal

Hi,

please change the overrides for these two libraries of src:qtav.

Thanks,
-- 
Pino

Bug#881376: O: sipcrack -- SIP login dumper/cracker

[Tobias Frost]

Package: wnpp

The current maintainer of sipcrack, Sebastian Castillo Builes 
,
is apparently not active anymore.  Therefore, I orphan this package now.

Maintaining a package requires time and skills. Please only adopt this
package if you will have enough time and attention to work on it.

If you want to be the new maintainer, please see
https://www.debian.org/devel/wnpp/#howto-o for detailed
instructions how to adopt a package properly.

Some information about this package:

Package: sipcrack
Binary: sipcrack
Version: 0.2-2
Maintainer: Sebastian Castillo Builes 
Build-Depends: debhelper (>= 5), cdbs, libpcap0.8-dev (>= 0.9.8-3), libssl-dev 
(>= 0.9.8g-8)
Architecture: any
Standards-Version: 3.7.3
Format: 1.0
Files:
 e202651ce0726ab94edffd331ab5f828 1004 sipcrack_0.2-2.dsc
 b9096c8d537fc231c7d74b759831a4c7 18771 sipcrack_0.2.orig.tar.gz
 73a93ccb11bdaa4d5847443d5be0fb6d 3772 sipcrack_0.2-2.diff.gz
Checksums-Sha256:
 ac1a123db812608a7c6c413d365044a3f3755adcf176738f7f4f5d3b6fa7797c 1004 
sipcrack_0.2-2.dsc
 5f356dbce7d09c009005af1a49c55e05ae66c8db4e44de862c5191898c49ae6e 18771 
sipcrack_0.2.orig.tar.gz
 c2afc095690fb6920608c024c03836f744c5f4df4932da4201b0178c2d056ca9 3772 
sipcrack_0.2-2.diff.gz
Directory: pool/main/s/sipcrack
Priority: source
Section: net

Package: sipcrack
Source: sipcrack (0.2-2)
Version: 0.2-2+b3
Installed-Size: 61
Maintainer: Sebastian Castillo Builes 
Architecture: amd64
Depends: libc6 (>= 2.3), libpcap0.8 (>= 0.9.8), libssl1.1 (>= 1.1.0)
Suggests: john
Description-en: SIP login dumper/cracker
 The tools contained in this package offer support for pcap files,
 wordlists and many more to extract all needed information and
 bruteforce the passwords for the sniffed accounts.
 .
  * sipdump-  Dump SIP digest authentications to a file.
  * sipcrack   -  Bruteforce the user password using the dump file
  generated by sipdump.
Description-md5: 197c4bfc7eead0914cda23ef0e804621
Homepage: http://www.remote-exploit.org/codes_sipcrack.html
Tag: implemented-in::c, interface::commandline, protocol::voip,
 role::program, security::TODO, security::authentication,
 security::cryptography
Section: net
Priority: optional
Filename: pool/main/s/sipcrack/sipcrack_0.2-2+b3_amd64.deb
Size: 17900
MD5sum: d53d10df64b1e722a9da0a4467672ef7
SHA256: a79f4b7bcf9f7e082ca5cb2133eceb91309582312cd7cc0d991ea2fe29ccb72c



signature.asc
Description: PGP signature

Bug#880669: irony-mode: tests do not reliably pass for several archs

[Nicholas D Steeves]

Please keep an eye on:
https://buildd.debian.org/status/package.php?p=irony-mode=experimental

for up-to-date info on if this is fixed in experimental.  2~exp2 is
the release I hope will do the trick

Cheers,
Nicholas


signature.asc
Description: PGP signature

Bug#824606: Resolution request

[Zbynek Michl]

Dear Maintainers,

How does it look with fixing this issue? It is more than year from
reporting it here and nothing happened so far.

Could you fix it, please? Unfortunately there is no activity from the
upstream developers.

I believe that this FileChooser behaviour is really annoying for many
Debian users!

Thanks
Zbynek

Bug#881341: webkit2gtk FTCBFS: debian/rules confuses build and host

[Helmut Grohne]

On Fri, Nov 10, 2017 at 08:25:59PM +0100, Alberto Garcia wrote:
> Both those flags (--no-keep-memory and --no-relax) plus the -g1 that
> you're changing in your patch were added because the build was failing
> (not enough memory, at least in the 1st and the 3rd case).

Thanks for your attention to detail. Yes, at least --no-keep-memory
should keep being conditional of the build architecture. That part of my
patch is wrong then.

> If the build machine is able to compile webkit without those flags
> then there's no need to add them, so if I'm understanding it right it
> doesn't depend on the target architecture but on the machine where
> you're doing the build.

For --no-relax, the question is harder as it influences the object file
generated. Given your reasoning though, maybe checking build is still
better.

> For the -g1 case we probably want to do it depending on the target
> architecture anyway, but for the --no-keep-memory case I don't see
> why.

I stand corrected.

> And now that we're at it, I'm not sure if --no-relax is even necessary
> anymore. This was added for alpha in 2008 to work around a binutils
> bug, which I guess has been already fixed ? It would be nice to test
> that, but I don't have access to an alpha machine.

You could try cross building from amd64. ;)

Helmut

Bug#881352: [Pkg-utopia-maintainers] Bug#881352: udisks2: Breaks installation with kernel panic

[Michael Biebl]

Am 10.11.2017 um 17:53 schrieb André Esteves:
> Subject: udisks2: Breaks installation with kernel panic
> Package: udisks2
> Version: 2.7.4-1
> Severity: critical
> Justification: breaks the whole system
> 
> Dear Maintainer,
> 
> 
> What led up to the situation?
> 
> Upgrading system tyhrough ssh then it broke in udisks2 install
> 
> with last screen messages:
> 
> -A instalar udisks2 (2.7.4-1) ...
> -
> -Message from syslogd@fw at Nov 10 16:17:08 ...
> - kernel:[339385.530851] CPU: 1 PID: 16 Comm: ksoftirqd/1 Not tainted
> 4.13.0-1-686-pae #1 Debian 4.13.4-2
> 
> -Message from syslogd@fw at Nov 10 16:17:08 ...
> - kernel:[339385.536447] Hardware name: System manufacturer System
> Product Name/P5G41T-M LX, BIOS 090207/27/2011
> 
> system terminal Kernel panic photo appended to message.

This is a kernel crash, so should probably be re-assigned (which an
appropriate severity).

Can you reproduce the problem by re-installing the udisks2 package?


-- 
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#881375: sen FTBFS with python-docker 2.5.1-1

[Adrian Bunk]

Source: sen
Version: 0.5.0-1
Severity: serious
Tags: buster sid

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

...
=== FAILURES ===
 test_short_id _

def test_short_id():
>   mock()

tests/test_container_info.py:7: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

def mock():
>   flexmock(docker.Client, images=images_response)
E   AttributeError: module 'docker' has no attribute 'Client'

tests/real.py:482: AttributeError
___ test_images_call ___

def test_images_call():
>   mock()

tests/test_docker_backend.py:6: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

def mock():
>   flexmock(docker.Client, images=images_response)
E   AttributeError: module 'docker' has no attribute 'Client'

tests/real.py:482: AttributeError
_ test_containers_call _

def test_containers_call():
>   mock()

tests/test_docker_backend.py:19: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

def mock():
>   flexmock(docker.Client, images=images_response)
E   AttributeError: module 'docker' has no attribute 'Client'

tests/real.py:482: AttributeError
 test_short_id _

def test_short_id():
>   mock()

tests/test_docker_backend.py:35: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

def mock():
>   flexmock(docker.Client, images=images_response)
E   AttributeError: module 'docker' has no attribute 'Client'

tests/real.py:482: AttributeError
__ test_stats __

def test_stats():
>   mock()

tests/test_docker_backend.py:47: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

def mock():
>   flexmock(docker.Client, images=images_response)
E   AttributeError: module 'docker' has no attribute 'Client'

tests/real.py:482: AttributeError
=== warnings summary ===
.pybuild/pythonX.Y_3.6/build/tests/test_util.py::test_log_traceback
  'caplog.records()' syntax is deprecated, use 'caplog.records' property (or 
caplog.clear()) instead
  'caplog.records()' syntax is deprecated, use 'caplog.records' property (or 
caplog.clear()) instead
  'caplog.records()' syntax is deprecated, use 'caplog.records' property (or 
caplog.clear()) instead

.pybuild/pythonX.Y_3.6/build/tests/test_util.py::test_log_traceback_without_tb
  'caplog.records()' syntax is deprecated, use 'caplog.records' property (or 
caplog.clear()) instead
  'caplog.records()' syntax is deprecated, use 'caplog.records' property (or 
caplog.clear()) instead

.pybuild/pythonX.Y_3.6/build/tests/test_util.py::test_log_traceback_threaded
  'caplog.records()' syntax is deprecated, use 'caplog.records' property (or 
caplog.clear()) instead
  'caplog.records()' syntax is deprecated, use 'caplog.records' property (or 
caplog.clear()) instead
  'caplog.records()' syntax is deprecated, use 'caplog.records' property (or 
caplog.clear()) instead

-- Docs: http://doc.pytest.org/en/latest/warnings.html
=== 5 failed, 54 passed, 8 warnings in 7.79 seconds 
E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: cd 
/build/1st/sen-0.5.0/.pybuild/pythonX.Y_3.6/build; python3.6 -m pytest tests
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.6 returned 
exit code 13
debian/rules:7: recipe for target 'build' failed
make: *** [build] Error 25

Bug#881374: mesa-va-drivers: enhances obsolete libva1 (should be libva2)

[Jonas Smedegaard]

Package: mesa-va-drivers
Version: 17.2.4-1+b1
Severity: minor

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Binary package mesa-va-drivers declares that it enhances libva1.

Nowadays it enhances libva2.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAloF7MkACgkQLHwxRsGg
ASH/5hAAnXTu+FzqxGIZU1lHubFSbD491bqtATLNs36s5iHwzkj8ThmyxTT2xUlJ
cHHgiaoN0+xfja6rLcV/GqfEwIRJITuO7fPCRS4T26XhMNrPEy0tZEjmXhJlg4z5
y3Xf6HjQhQTNPuZRdWOAzYwZ2sMBQS9C7ByidfEePjJ44tYsrWHHHhG5WESYG4y9
2zlBkTYSULBKb8WBTzwHDPdh+bcNZrrL+KiiHGq9BG6gaTnauOWvHvFlu885yq7U
ZcQAP8lbEwe0HLyIX9ZawBbJUcX82wuPG2QbLKBQClkKNDurR0UXz14e5aGKl0wj
PFeqpqqxLcFieBX/s1WpebQgQi0uW15HstXErEu5B4jPcFzQ/mPOAbbLvCdQWf4e
1TsIpKM3WIntNWtqAjjoXpzooneAbFEmsZP+xQ1lzpX/s0kc5wu1fl+swLnRmmJo
YJXzUcnLjdORxAkoc5D8c0IzZc2hneCcpLbjgr5N9Vmjt4FaizHLuKc+GJrMiTmZ
847abX+vAPOAyAEoInnpfye5b8V6ccSAWm/MfqKVzjokcguwUKTV7cUBR4dQfrTb
kvyxfB8i3TO5xzUYekeexhMFriS5FX91grVYPeDefQr6ML9EBnL7+rs3dMfkh0Fv
tzs/TTX5130umSZr6d1CvAjDnN/RjiOhhlXX7S6eLDnWHdbcq2M=
=T3x0
-END PGP SIGNATURE-

Bug#880011: csound: Macro system on csound make segfault

[Mickael Viey]

Hi,


After another test, It seems that the m statement which cause the segfault.

Consider the two attached csd files. One contains a "m" statement and 
make a segfault, the other doesn't contain it and work as expected.


a link toward documentation about this, I think I use it correctly (the 
file worked on my previous csound version on Debian Jessy):


http://www.csounds.com/manual/html/m.html


Best,

Mik


Le 10/11/2017 à 01:10, Felipe Sateler a écrit :

Control: forwarded -1 https://github.com/csound/csound/issues/871

2017-11-08 16:45 GMT-03:00 Mickael Viey >:


Le 08/11/2017 à 14:19, Felipe Sateler a écrit :

Control: forcemerge -1 880010
Control: tags -1 moreinfo

On Sat, Oct 28, 2017 at 7:54 AM, Mickael Viey
> wrote:

Package: csound

Version: 1:6.08.0~dfsg-1
Severity: normal

Dear Maintainer,


I have some csd files I made on another platforms which
generate
segfault when running with this version of csound. After
diagnostic It
appears that the macro system which is responsible.

By example, this macro works:
#define TIME # 0.25 #
#define freq # 146 #


#define T # $freq #
#define Am # $freq * 17 / 16 #
#define AM # $freq * 9/8 #

But If I had this after te last line:

#define E # $freq #

I get a segfault. I will join the complete csd file I used
for my tests.

Weird. I can reproduce on a stretch docker container, but I can't
reproduce on sid, either with 6.09 or rebuilding 6.08 . I ran
out of
time, but could you try rebuilding csound and see if the problem
persists?

Hi,

I am not sure what you mean by "rebuild" but this is what I done:


Thanks, but I meant recompile the csound sources, not just reinstall.

Anyway, I have debugged some more. Turns out the error in sid is still 
present, it just doesn't cause a crash. I have forwarded upstream to 
the above url.


The error is not due to the macro, but due to the 3/2 p7. This is 
invalid syntax, and that triggers the crash/malfunction (the crash is 
in the error printing code, heh). You can work around the problem by 
fixing the syntax error and passing 1.5.



--

Saludos,
Felipe Sateler




nobug_without_m.csd
Description: audio/csound


bug_with_m.csd
Description: audio/csound

Bug#881373: Wishlist: Banshee Download from Internet Archive

[Joshua Blagden]

Package: banshee
  Severity: wishlist

Dear Debian developers and maintainers,

On one hand, I appreciate being able to play media from Internet Archive, but I 
would also like to have the ability to download content from that resource so I 
can have offline access to it.

 * Package name: Banshee
   Version : 2.6.2





Regards,
Joshua Blagden 

Bug#881372: gcc-7: gccgo runtime fails to build on ia64

[Jason Duerstock]

Package: gcc-7
Version: 7.2.0-12
Severity: normal

Dear Maintainer,

When trying to build the gccgo runtime on ia64, the build fails with undefined 
references to 'lfstackPack' and 'lfstackUnpack'.

I believe this is fixed by the attached patch.

-- System Information:
Debian Release: 7.11
  APT prefers oldoldstable
  APT policy: (500, 'oldoldstable')
Architecture: ia64

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

Versions of packages gcc-7 depends on:
ii  binutils  2.25-5+deb8u1
ii  cpp-7 7.2.0-12
ii  gcc-7-base7.2.0-12
ii  libc6.1   2.13-38+deb7u10
ii  libcc1-0  7.2.0-12
ii  libgcc-7-dev  7.2.0-12
ii  libgcc1   1:7.2.0-12
ii  libgmp10  2:6.1.2+dfsg-1.1
ii  libisl15  0.18-1
ii  libmpc3   1.0.3-2
ii  libmpfr4  3.1.6-1
ii  libstdc++67.2.0-12
ii  libunwind70.99-0.3
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages gcc-7 recommends:
ii  libc6.1-dev  2.13-38+deb7u10

Versions of packages gcc-7 suggests:
pn  gcc-7-doc 
pn  gcc-7-locales 
pn  libasan4-dbg  
pn  libatomic1-dbg
pn  libcilkrts5-dbg   
pn  libgcc1-dbg   
pn  libgomp1-dbg  
pn  libitm1-dbg   
pn  liblsan0-dbg  
pn  libmpx2-dbg   
pn  libquadmath0-dbg  
pn  libtsan0-dbg  
pn  libubsan0-dbg 

-- debconf information excluded
--- src/libgo/go/runtime/lfstack_64bit.go.orig	2017-11-10 14:19:42.699987069 -0500
+++ src/libgo/go/runtime/lfstack_64bit.go	2017-11-10 14:19:52.635987138 -0500
@@ -2,7 +2,7 @@
 // Use of this source code is governed by a BSD-style
 // license that can be found in the LICENSE file.
 
-// +build amd64 arm64 mips64 mips64le ppc64 ppc64le s390x arm64be alpha sparc64
+// +build amd64 arm64 mips64 mips64le ppc64 ppc64le s390x arm64be alpha sparc64 ia64
 
 package runtime
 

Bug#881110: cacti: CVE-2017-16641: arbitrary execution of os commands via path_rrdtool parameter in an action=save request

[Paul Gevers]

Control: severity -1 important
Control: tags -1 pending

Hi all,

On 07-11-17 22:17, Salvatore Bonaccorso wrote:
> Severity: grave
> CVE-2017-16641[0]:
> | lib/rrd.php in Cacti 1.1.27 allows remote authenticated administrators
> | to execute arbitrary OS commands via the path_rrdtool parameter in an
> | action=save request to settings.php.

Although this is true, and this parameter is not meant to be used like
this, the cacti *admin* has always had this possibility via the "Data
Input Method" freedom, which caused CVE-2009-4112 / bug 561339 to be
raised. I just confirmed that I could indeed still do the via that
(trivial) route.

So just to be clear (and I don't particularly like it), the power of the
cacti *admin* has been long known and has been accepted as unfixed for
multiple Debian releases. Therefor I lower the severity of this bug.

Unfortunately the upstream patch for this bug does not simply apply to
pre 1.x versions of cacti. I am not comfortable (yet) with creating a
patch for those versions, and due to CVE-2009-4112, I don't think it is
worth fixing this in stable and older.

Paul

PS on other option is to raise the severity of 561339 again, but I don't
expect the patch to then miraculously turn up.



signature.asc
Description: OpenPGP digital signature

Bug#881371: Banshee - Green Line Under Playing Video

[Joshua Blagden]

Package: banshee
  Severity: minor

Dear Debian developers and maintainers,

I have been having an issue with Banshee where there is a green line underneath 
a playing video. Banshee is otherwise operational, but this irritating bug does 
exist.

 * Package name: Banshee
   Version : 2.6.2





Regards,
Joshua Blagden 

Bug#880669: irony-mode: tests do not reliably pass for several archs

[Nicholas D Steeves]

Update:

My LLVM-3.8+Clang-5 experiment revealed this sometimes also affects
amd64:
https://buildd.debian.org/status/fetch.php?pkg=irony-mode=amd64=1.2.0-2~exp1=1510272887=0

Never on my amd64 development box, and only on the buildd.

Also, good news!  Upstream has committed a fix that I believe will
probably do the trick.

Cheers,
Nicholas


signature.asc
Description: PGP signature

Bug#881370: nmu: directfb_1.7.7-6

[Harald Jenny]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

Hello,

in the 17.2 versions of the mesa package libegl1-mesa is just a
transitional package so a rebuild of directfb would remove this
unnecessary dependency.

nmu directfb_1.7.7-6 . ANY . unstable . -m "Rebuild against mesa > 17.1.5-1 to 
remove dependency on transitional libegl1-mesa package"

Thanks.

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

Kernel: Linux 4.14.0-rc7-amd64 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C), 
LANGUAGE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Bug#881369: wodim: Request for Intenationalisation of documentation file of wodim

[Markus Hiereth]

Package: wodim
Version: 9:1.1.11-3
Severity: normal

Dear Maintainer,

please prepare the sources for an integration of localised versions of 
the wodim (1) manual page.

Maybe, a template for the message catalogue, created with 

   po4a-gettextize -f man --option groff_code=verbatim -m wodim.1 -p wodim.1.pot

is helpful. You will find it attached here.

I am subscriber of the mailing list of the German language team and 
would consider providing a localised message catalogue.

Best regards
Markus


-- System Information:
Debian Release: 8.9
  APT prefers oldstable
  APT policy: (500, 'oldstable')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core)
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages wodim depends on:
ii  libc62.19-18+deb8u10
ii  libcap2  1:2.24-8

Versions of packages wodim recommends:
ii  genisoimage  9:1.1.11-3

Versions of packages wodim suggests:
pn  cdrkit-doc  

-- no debconf information
# SOME DESCRIPTIVE TITLE
# Copyright (C) YEAR Free Software Foundation, Inc.
# This file is distributed under the same license as the PACKAGE package.
# FIRST AUTHOR , YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2017-11-10 20:34+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME \n"
"Language-Team: LANGUAGE \n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=CHARSET\n"
"Content-Transfer-Encoding: 8bit\n"

#. type: TH
#: wodim.1:37
#, no-wrap
msgid "wodim"
msgstr ""

#. type: TH
#: wodim.1:37
#, no-wrap
msgid "Version 2.0"
msgstr ""

#. type: SH
#: wodim.1:38
#, no-wrap
msgid "NAME"
msgstr ""

#. type: Plain text
#: wodim.1:40
msgid "wodim - write data to optical disk media"
msgstr ""

#. type: SH
#: wodim.1:40
#, no-wrap
msgid "SYNOPSIS"
msgstr ""

#. type: Plain text
#: wodim.1:43
msgid "B [I] I.\\|.\\|.I"
msgstr ""

#. type: SH
#: wodim.1:43
#, no-wrap
msgid "NOTE"
msgstr ""

#. type: Plain text
#: wodim.1:50
msgid ""
"There may be similarities and differences between this program and other "
"disk recording application(s). See the B and B sections "
"below to learn about the origin of B"
msgstr ""

#. type: SH
#: wodim.1:51
#, no-wrap
msgid "DESCRIPTION"
msgstr ""

#. type: Plain text
#: wodim.1:55
msgid ""
"B is used to record data or audio Compact Discs on an Orange Book "
"CD-Recorder or to write DVD media on a DVD-Recorder."
msgstr ""

#. type: Plain text
#: wodim.1:72
msgid ""
"The I is the device file or label offered by the operating system to "
"access the recorder with SCSI GENERIC (sg) interface. Note that some "
"operating systems may provide separate device nodes for block-oriented and "
"sg access. For example, on older I systems, the sg access was "
"available through I files while the block oriented access was "
"done through associated (but not identical)  I and I "
"(or I ) files."
msgstr ""

#. type: Plain text
#: wodim.1:84
msgid ""
"In any case, the user running B needs read and write access to the "
"particular device file on a Linux system. It is recommended to be root or "
"install the application as suid-root, because certain versions of Linux "
"(kernel) limit the set of SCSI commands allowed for non-root users. Even if "
"usage without root identity is possible in many cases, some device drivers "
"still may fail, show unexplainable problems and generally the problems "
"become harder to debug. The risk for buffer-underruns is also increased. See "
"the I section below for more details."
msgstr ""

#. type: Plain text
#: wodim.1:96
msgid ""
"There is an alternative way of specifying the device, using the traditional "
"SCSI descriptions in form of I "
"specification. However, the success of this method is not guaranteed since "
"it requires an adaptation scheme for your architecture, and the numbers may "
"vary depending on the hardware-internal numbering or on the order of "
"hot-plug device detection. If your operating system does not provide a "
"sufficient framework for keeping this numbers persistent, don't rely on "
"them. See B<-scanbus> and B<--devices> options below for details."
msgstr ""

#. type: Plain text
#: wodim.1:103
msgid ""
"There are emulated SCSI compatible device systems, using the SCSI protocols "
"transported over various hardware/media types. The most known examples is "
"ATAPI (\"IDE burners\") or USB storage (\"external USB case\"). If the "
"pseudo-SCSI b/t/l device address specification is used instead of the native "
"one, you need to prepend the \"devicetype:\" description to the emulated "
"\"bus/target/lun\" device address."
msgstr ""

#. type: Plain text
#: wodim.1:107
msgid ""
"If a file /etc/wodim.conf exists, the parameter to the 

Bug#881363: RFS: xerces-c/3.2.0+debian-2

[Tobias Frost]

Control: owner -1 !

Will take care.

Bug#881368: fis-gtm: please switch build-dep from libconfig8-dev to libconfig-dev

[Mattia Rizzolo]

Source: fis-gtm
Version: 6.3-002-3
Severity: serious

I'm about to upload a libconfig dropping this transitional package,
please update fis-gtm.

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

Bug#881366: qwo: please switch build-dep from libconfig8-dev to libconfig-dev

[Mattia Rizzolo]

Source: qwo
Version: 0.5-2.1
Severity: serious

I'm about to upload a libconfig dropping this transitional package,
please update qwo.

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

Bug#872721: hplip 3.17.7: Will not print colors correctly using my HP LaserJet M452dn printer

[Brian Potkin]

On Fri 10 Nov 2017 at 16:26:56 +0100, Adrian Immanuel Kieß wrote:

> Dear Brian,
> 
> the problem persits using up-to-date Debian/testing installation. Now
> even the colors from LaTeX printouts are missing which was the last
> colors the printer printed.
> 
> Printing color pictures or color PDF fails completely. 
> 
> I will attach a sample printout of a picture and screenshot of HPLIP
> version used to this message.

adrian-hplip-debian-bug-sample-image-2017-11-10.jpg shows a young man in
a reddish shirt and a black-white background with cars and buildings.
The only other coloured object is a sign in red behind the man. Are we
seeing the same thing?

> Additionally, please note: This error also applies to the windows hp
> printer driver.

The only thing that would imply to me is that the printer is at
fault. But I could be completely wrong. (People usually say Windows
works but Linux doesn't!).

> As written before, only altering the print density settings of the
> printer helps to have black and white working but in bad quality.
> 
> I used both HPLIP (hp://) and CUPS to setup a printer entry. Both
> installations issue the same errors described before.

CUPS can also use hp://... to set up the printer. If you did that,
it is no wonder you got the same outcome.

> Can you keep me informed when the error is fixed because it's the only
> printing device I own and I need the printer to get my work done.

Fixing any error in the Debian printing system requires co-operation
from you. You have the printer and there is only so much we can do.

Your print queue has a PPD in /etc/cups/ppd. Do (as root):

  cupsfilter -p /etc/cups/ppd/ -m printer/foo -e --list-filters > 
filters

Post filters to the bug as an attachment.

Now use the original of adrian-hplip-debian-bug-sample-image-2017-11-10.jpg
to do:

  cupsfilter -p /etc/cups/ppd/ -m printer/foo -e  > 
adrian.ps

Examine adrian.ps with a PostScript viewer. Post it to the bug. What do
you think of its quality?

Thanks in advance,

Brian.

Bug#881367: viva: please switch build-dep from libconfig8-dev to libconfig-dev

[Mattia Rizzolo]

Source: viva
Version:
Severity: serious

I'm about to upload a libconfig dropping this transitional package,
please update viva as well.

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

Bug#881365: Synaptic Does Not Work on XFCE Unless Launched from Terminal.

[Joshua Blagden]

Package: synaptic
  Severity: urgent

Dear Debian developers and maintainers, I have recently switched from GNOME to 
XFCE due to speed. 
However, Synaptic does not work in XFCE. Synaptic works in XFCE, but only when 
launched from Terminal with the help of sudo. 
To be more precise, there is no graphical way to launch Synaptic, likely 
because XFCE does not know how to deal with Synaptic's password request.

 * Package name: Synaptic
   Version : 0.84.2





Regards,
Joshua Blagden 

Bug#881364: cdparanoia: l18n / Please prepare manual page for localisation

[Markus Hiereth]

Package: cdparanoia
Version: 3.10.2+debian-11
Severity: normal

Dear Maintainer,

please prepare cdparanoia source files tree to accept as well localised 
versions of the manual page.

Maybe the attached template created with po4a-gettextize helps, it has 
been derived from 3.10.2+debian-11. 

Thereafter, I could provide a message catalogue for a German manual page 
version.

Best regards
Markus Hiereth

-- System Information:
Debian Release: 8.9
  APT prefers oldstable
  APT policy: (500, 'oldstable')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core)
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages cdparanoia depends on:
ii  libc6   2.19-18+deb8u10
ii  libcdparanoia0  3.10.2+debian-11

cdparanoia recommends no packages.

cdparanoia suggests no packages.

-- no debconf information
# SOME DESCRIPTIVE TITLE
# Copyright (C) YEAR Free Software Foundation, Inc.
# This file is distributed under the same license as the PACKAGE package.
# FIRST AUTHOR , YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2017-11-10 20:20+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME \n"
"Language-Team: LANGUAGE \n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=CHARSET\n"
"Content-Transfer-Encoding: 8bit\n"

#. type: TH
#: cdparanoia.1:1
#, no-wrap
msgid "CDPARANOIA"
msgstr ""

#. type: TH
#: cdparanoia.1:1
#, no-wrap
msgid "11 Sep 2008"
msgstr ""

#. type: SH
#: cdparanoia.1:2
#, no-wrap
msgid "NAME"
msgstr ""

#. type: Plain text
#: cdparanoia.1:4
msgid ""
"cdparanoia - an audio CD reading utility which includes extra data "
"verification features"
msgstr ""

#. type: SH
#: cdparanoia.1:4
#, no-wrap
msgid "SYNOPSIS"
msgstr ""

#. type: Plain text
#: cdparanoia.1:10
msgid "B [B] B [B] |B<-B>"
msgstr ""

#. type: SH
#: cdparanoia.1:10
#, no-wrap
msgid "DESCRIPTION"
msgstr ""

#. type: Plain text
#: cdparanoia.1:18
msgid ""
"B retrieves audio tracks from CDDA-capable CDROM drives.  The "
"data can be saved to a file or directed to standard output in WAV, AIFF, "
"AIFF-C or raw format.  Most ATAPI and SCSI and several proprietary CDROM "
"drive makes are supported; B can determine if the target drive "
"is CDDA capable."
msgstr ""

#. type: Plain text
#: cdparanoia.1:23
msgid ""
"In addition to simple reading, B adds extra-robust data "
"verification, synchronization, error handling and scratch reconstruction "
"capability."
msgstr ""

#. type: SH
#: cdparanoia.1:23
#, no-wrap
msgid "OPTIONS"
msgstr ""

#. type: TP
#: cdparanoia.1:25
#, no-wrap
msgid "B<-A --analyze-drive>"
msgstr ""

#. type: Plain text
#: cdparanoia.1:30
msgid ""
"Run and log a complete analysis of drive caching, timing and reading "
"behavior; verifies that cdparanoia is correctly modelling a specific drive's "
"cache and read behavior. Implies -vQL."
msgstr ""

#. type: TP
#: cdparanoia.1:31
#, no-wrap
msgid "B<-v --verbose>"
msgstr ""

#. type: Plain text
#: cdparanoia.1:35
msgid ""
"Be absurdly verbose about the auto-sensing and reading process. Good for "
"setup and debugging."
msgstr ""

#. type: TP
#: cdparanoia.1:36
#, no-wrap
msgid "B<-q --quiet>"
msgstr ""

#. type: Plain text
#: cdparanoia.1:39
msgid "Do not print any progress or error information during the reading process."
msgstr ""

#. type: TP
#: cdparanoia.1:40
#, no-wrap
msgid "B<-e --stderr-progress>"
msgstr ""

#. type: Plain text
#: cdparanoia.1:43
msgid "Force output of progress information to stderr (for wrapper scripts)."
msgstr ""

#. type: TP
#: cdparanoia.1:44
#, no-wrap
msgid "B<-l --log-summary [file]>"
msgstr ""

#. type: Plain text
#: cdparanoia.1:47
msgid "Save result summary to file, default filename cdparanoia.log."
msgstr ""

#. type: TP
#: cdparanoia.1:48
#, no-wrap
msgid "B<-L --log-debug [file]>"
msgstr ""

#. type: Plain text
#: cdparanoia.1:51
msgid ""
"Save detailed device auto-sense and debugging output to a file, default "
"filename cdparanoia.log."
msgstr ""

#. type: TP
#: cdparanoia.1:52
#, no-wrap
msgid "B<-V --version>"
msgstr ""

#. type: Plain text
#: cdparanoia.1:55
msgid "Print the program version and quit."
msgstr ""

#. type: TP
#: cdparanoia.1:56
#, no-wrap
msgid "B<-Q --query>"
msgstr ""

#. type: Plain text
#: cdparanoia.1:60
msgid ""
"Perform CDROM drive auto-sense, query and print the CDROM table of contents, "
"then quit."
msgstr ""

#. type: TP
#: cdparanoia.1:61
#, no-wrap
msgid "B<-s --search-for-drive>"
msgstr ""

#. type: Plain text
#: cdparanoia.1:64
msgid ""
"Forces a complete search for a CDROM drive, even if the /dev/cdrom link "
"exists."
msgstr ""

#. type: TP
#: cdparanoia.1:65
#, no-wrap
msgid "B<-h --help>"
msgstr ""

#. type: Plain text
#: cdparanoia.1:70
msgid "Print a brief synopsis of B usage and options."
msgstr ""

#. type: TP
#: cdparanoia.1:71
#, no-wrap

Bug#878722: bts reassign 878722 partman-auto

[Cyril Brulebois]

Nicholas D Steeves  (2017-11-10):
> 1) get a list of disks
> 2) identify the disk used by the installer
> 3) exclude the disk found at #2

How do you do 2?

Last I touched this, nothing obvious appeared in d-i to know what the
installer was booted from. ISTR having suggested at the time that
bootloaders could set something to help d-i figure out where it booted
from, but I don't think anything happened in this area since then.

> 4) present modified list as target disks for installation
> 5) unless in expert mode, where a user could use one partition of a
> disk as the installation source and another partition as the
> installation target.  I'm not sure how important #5 is, but maybe some
> users want to be able to do this?


KiBi.


signature.asc
Description: PGP signature

Bug#878722: Final Notice : Nixia jf

[Nixia Ramos]

I won't participate in this

On Nov 10, 2017 11:25 AM, "Amazon Notification" 
wrote:

> Final Notice for: Amazon Rewards
>
> 
>
> 
>
> 
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> control: reassign -1 partman-auto Dear maintainers, I think this bug is
> specific to partman-auto. Partman should allow rescanning devices and
> recognize NVMe devices when preconfigured with /dev/sda. Alternatively,
> there should be an installation target "largest disk" or something similar.
> Best wishes Michael

Bug#881363: RFS: xerces-c/3.2.0+debian-2

[Bill Blough]

Package: sponsorship-requests
Severity: normal

  Dear mentors,

  I am looking for a sponsor and/or someone to grant upload permissions (I am
  a DM) for my package "xerces-c"

  NOTE: This is the unstable upload for a SONAME transition.  The package has
  already been uploaded to experimental and upload to unstable has been
  approved.  The transition bug is viewable at the following URL -

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

 * Package name: xerces-c
   Version : 3.2.0+debian-2
   Upstream Author : Apache Xerces Team
 * URL : https://xerces.apache.org/xerces-c
 * License : Apache 2.0
   Section : libs

  It builds those binary packages:

libxerces-c-dev - validating XML parser library for C++ (development files)
libxerces-c-doc - validating XML parser library for C++ (documentation)
libxerces-c-samples - validating XML parser library for C++ (compiled 
samples)
libxerces-c3.2 - validating XML parser library for C++

  To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/xerces-c


  Alternatively, one can download the package with dget using this command:

dget -x 
https://mentors.debian.net/debian/pool/main/x/xerces-c/xerces-c_3.2.0+debian-2.dsc

  More information about xerces-c can be obtained from 
https://xerces.apache.org/xerces-c

  Changes since the last upload:

* Upload to unstable


  Regards,
   Bill Blough



signature.asc
Description: PGP signature

Bug#878722: bts reassign 878722 partman-auto

[Ben Hutchings]

On Fri, 2017-11-10 at 12:32 -0500, Lennart Sorensen wrote:
> On Fri, Nov 10, 2017 at 04:19:14PM +, Ben Hutchings wrote:
> > This is true, but I don't think it's a good reason not to implement a
> > mostly-reliable heuristic.
> > 
> > If there are multiple disks, there are usually going to be just 2 of
> > them, one of which contains the installer.  In any installer build
> > other than netboot, it will look for its own disk in order to load
> > udebs.  Once it has done that, it can determine that the other disk is
> > the one to install on.  That's a pretty good heuristic.
> 
> I think more than one disk in the machine isn't that unusual.

The context of this bug is that Michael wants to partition a single
disk - not set up a RAID.  I think it *is* unusual that Debian would be
installed on a single disk of a system that contains multiple internal
disks.  If someone really wants to pre-seed partman in that case then
they would have to specify the device name just as they do now
(presumably using /dev/disk/by-path/...).

> > Aside from that, we can also make a guess based on the bus type:
> > 
> > - ATA: probably internal
> 
> eSATA is not that unusual.
>
> > - NVMe: probably internal
> > - USB: probably external
> > - MMC/SD: ambiguous (eMMC must be internal, and Linux has a notion of
> > 'non-removable' slots, but I don't think userland has this info)
> > 
> > If we could get more information about MMC/SD slots then we should be
> > able to implement an heuristic that would work for >99% of cases.
> 
> You can certainly try to make a good guess, but it certainly still needs
> to be confirmed.

That seems to defeat the point of pre-seeding.

Ben.

-- 
Ben Hutchings
Who are all these weirdos? - David Bowie, reading IRC for the first
time



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

Bug#881362: libpjlib-util2: resolution of DNS SRV targets fails if target has no AAAA record

[Joachim Förster]

Package: libpjlib-util2
Version: 2.5.5~dfsg-6
Severity: important
Tags: patch upstream


While trying to use Asterisk with its newer PJSIP-based SIP channel 
support, it turned out that registering to a SIP server fails if the SRV 
targets do not have an  record, but only an A record.


The effect, which can be seen via Wireshark, is that essentially no SIP 
registration is taking place at all, after all necessary DNS requests 
have been sent out. Asterisk then just says:


No response received from 'sip:xxx' on registration attempt to 
'sip:xxx@xxx', retrying in '30'


After some debugging it became clear, that the DNS resolution is 
successful as far as resolving the A records of the SRV targets. However 
in case a SIP server does not have an  record, libpjlib-util2 
skips/aborts the whole resolution and treats it as failed, no matter if 
an A record has been found or not.


Applying upstream's GitHub commit 4ab1838 (part of pjproject 2.6) onto 
Debian stable's version 2.5.5 solves the problem.


https://github.com/pjsip/pjproject/commit/4ab1838

Conclusion: Please apply the mentioned patch and release a new stable 
version.



-- 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/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)

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

Versions of packages libpjlib-util2 depends on:
ii  libavcodec577:3.2.8-1~deb9u1
ii  libavdevice57   7:3.2.8-1~deb9u1
ii  libavformat57   7:3.2.8-1~deb9u1
ii  libavutil55 7:3.2.8-1~deb9u1
ii  libc6   2.24-11+deb9u1
ii  libopencore-amrnb0  0.1.3-2.1+b2
ii  libpj2  2.5.5~dfsg-6
ii  libsdl2-2.0-0   2.0.5+dfsg1-2
ii  libswscale4 7:3.2.8-1~deb9u1
ii  libv4l-01.12.3-1

libpjlib-util2 recommends no packages.

libpjlib-util2 suggests no packages.

-- no debconf information

Bug#881361: webkit2gtk FTCBFS: uses the build architecture pkg-config for finding the host architecture geoclue-2.0.pc

[Helmut Grohne]

Source: webkit2gtk
Version: 2.18.2-1
Tags: upstream patch
User: helm...@debian.org
Usertags: rebootstrap

webkit2gtk also fails to cross build from source, because it searches
for geoclue-2.0.pc with the build architecture pkg-config which is
simply hard coded in the upstream build system. After turning it
substitutable, it uses the cross pkg-config and finds geoclue-2.0.pc.
Please consider applying the attached patch and closing this bug when
doing so, even though it still doesn't cross build after applying it.

Helmut
Index: webkit2gtk-2.18.2/Source/WebCore/PlatformGTK.cmake
===
--- webkit2gtk-2.18.2.orig/Source/WebCore/PlatformGTK.cmake
+++ webkit2gtk-2.18.2/Source/WebCore/PlatformGTK.cmake
@@ -188,7 +188,8 @@
 list(APPEND WebCore_DERIVED_SOURCES
 ${DERIVED_SOURCES_WEBCORE_DIR}/Geoclue2Interface.c
 )
-execute_process(COMMAND pkg-config --variable dbus_interface geoclue-2.0 OUTPUT_VARIABLE GEOCLUE_DBUS_INTERFACE)
+include(FindPkgConfig)
+execute_process(COMMAND ${PKG_CONFIG_EXECUTABLE} --variable dbus_interface geoclue-2.0 OUTPUT_VARIABLE GEOCLUE_DBUS_INTERFACE)
 add_custom_command(
  OUTPUT ${DERIVED_SOURCES_WEBCORE_DIR}/Geoclue2Interface.c ${DERIVED_SOURCES_WEBCORE_DIR}/Geoclue2Interface.h
  COMMAND gdbus-codegen --interface-prefix org.freedesktop.GeoClue2. --c-namespace Geoclue --generate-c-code ${DERIVED_SOURCES_WEBCORE_DIR}/Geoclue2Interface ${GEOCLUE_DBUS_INTERFACE}

Bug#881348: libgcc-7-dev-armhf-cross: unmet dependencies

[Matthias Klose]

On 10.11.2017 16:53, Héctor Orón Martínez wrote:
> Source: gcc-7-cross
> Severity: normal
> 
> Dear Maintainer,
> 
> In armhf chroot, trying to install cross compiler from amd64, using
> multiarch, I get:
> 
> The following packages have unmet dependencies:
> gcc-7-arm-linux-gnueabihf:amd64 : Depends:
> libgcc-7-dev-armhf-cross:amd64 (>= 7.2.0-11cross1)
> 
> I have been suggested at #debian-bootstrap channel that is a bug and
> libgcc-7-dev-armhf-cross should be marked multiarch foreign.

why would you want to install that package in an armhf chroot?

Bug#880011: csound: Macro system on csound make segfault

[Mickael Viey]

Le 10/11/2017 à 01:10, Felipe Sateler a écrit :

Control: forwarded -1 https://github.com/csound/csound/issues/871

2017-11-08 16:45 GMT-03:00 Mickael Viey >:


Le 08/11/2017 à 14:19, Felipe Sateler a écrit :

Control: forcemerge -1 880010
Control: tags -1 moreinfo

On Sat, Oct 28, 2017 at 7:54 AM, Mickael Viey
> wrote:

Package: csound

Version: 1:6.08.0~dfsg-1
Severity: normal

Dear Maintainer,


I have some csd files I made on another platforms which
generate
segfault when running with this version of csound. After
diagnostic It
appears that the macro system which is responsible.

By example, this macro works:
#define TIME # 0.25 #
#define freq # 146 #


#define T # $freq #
#define Am # $freq * 17 / 16 #
#define AM # $freq * 9/8 #

But If I had this after te last line:

#define E # $freq #

I get a segfault. I will join the complete csd file I used
for my tests.

Weird. I can reproduce on a stretch docker container, but I can't
reproduce on sid, either with 6.09 or rebuilding 6.08 . I ran
out of
time, but could you try rebuilding csound and see if the problem
persists?

Hi,

I am not sure what you mean by "rebuild" but this is what I done:


Thanks, but I meant recompile the csound sources, not just reinstall.

Anyway, I have debugged some more. Turns out the error in sid is still 
present, it just doesn't cause a crash. I have forwarded upstream to 
the above url.


The error is not due to the macro, but due to the 3/2 p7. This is 
invalid syntax, and that triggers the crash/malfunction (the crash is 
in the error printing code, heh). You can work around the problem by 
fixing the syntax error and passing 1.5.



--

Saludos,
Felipe Sateler


That's right. In fact I can write expressions in score file but I must 
write them like this:


[  3 / 2 ]

On my previous install I doesn't have an error but I realize that the 
expression was interpreted like a 3 and not 3 / 2 .



If I reduce the number of space characters in the score I get the 
previous behavior (but I get 3 not 1.5).



I join the two versions of the score. One with a bad syntax but without 
seg fault when rendering, the other with the correct syntax.



Hoping they help you, (I really want have the time to debug this with you),


Thanks a lot for your help,

Best,





bad_syntax_wihout_segfault.csd
Description: audio/csound


correct_syntax.csd
Description: audio/csound

Bug#881341: webkit2gtk FTCBFS: debian/rules confuses build and host

[Alberto Garcia]

On Fri, Nov 10, 2017 at 07:07:00PM +0100, Helmut Grohne wrote:

> > > ifeq ($(DEB_HOST_ARCH_BITS),32)
> > >   LDFLAGS += -Wl,--no-keep-memory
> > >  endif
> > >  
> > > -ifeq ($(DEB_BUILD_ARCH),alpha)
> > > +ifeq ($(DEB_HOST_ARCH),alpha)
> > >   LDFLAGS += -Wl,--no-relax
> > >  endif
> > 
> > Wait a minute, why do you change this to DEB_HOST_ARCH here? Shouldn't
> > we be using the DEB_BUILD_* variables in these two cases?
> 
> I think you are confusing build and host again.
> 
> If you check DEB_BUILD_ARCH, then you will pass -Wl,--no-relax when
> building for amd64 on alpha. Since --no-relax is machine-dependent,
> that seems wrong to me. In general, changing the build architecture
> should not affect the resulting binary packages. Passing different
> flags for different build architectures often breaks that.

Both those flags (--no-keep-memory and --no-relax) plus the -g1 that
you're changing in your patch were added because the build was failing
(not enough memory, at least in the 1st and the 3rd case).

If the build machine is able to compile webkit without those flags
then there's no need to add them, so if I'm understanding it right it
doesn't depend on the target architecture but on the machine where
you're doing the build.

For the -g1 case we probably want to do it depending on the target
architecture anyway, but for the --no-keep-memory case I don't see
why.

And now that we're at it, I'm not sure if --no-relax is even necessary
anymore. This was added for alpha in 2008 to work around a binutils
bug, which I guess has been already fixed ? It would be nice to test
that, but I don't have access to an alpha machine.

Berto

Bug#879783: Removing dino from multimedia-blends

[Ross Gammon]

Control: tags -1 pending

Hi Ralf,

I have pushed a change to git removing dino from multimedia-blends. I
will do an upload sometime soon.

But don't you think it is a bit early to introduce a new/different
package with the same name as dino?

Dino is still in old-stable and Ubuntu Trusty which are still both
supported. It might be better to rename the package (e.g. to dino-im)
for now, and then rename it back to dino once Buster is released, and
Ubuntu Trusty is dropped.

Regards,

Ross



signature.asc
Description: OpenPGP digital signature

Bug#880308: Info received (CLA Diet is the end of obesity zj)

[Channel K.E.N.E]

Stop sending me emails

On Nov 10, 2017 2:03 PM, "Debian Bug Tracking System" 
wrote:

> Thank you for the additional information you have supplied regarding
> this Bug report.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  TigerVNC Packaging Team 
>
> If you wish to submit further information on this problem, please
> send it to 880...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 880308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880308
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>

Bug#881170: Private HTSlib internals packaged in libhts-dev

[Mattia Rizzolo]

Control: clone -1 -2 -3
Control: retitle -1 htslib: please do not package cram/*.h headers
Control: severity -1 important
Control: summary -1 cram headers are considered private and other projects 
shouldn't be interested in them
Control: retitle -2 htslib: please revert pkg-config change in 
fix_pkg-config.patch
Control: summary -2  HTSlib's convention is that its headers are included via 
#include  etc, to avoid confusion with any other packages' 
headers named sam.h. So a Cflags value of -I${includedir}/htslib is incorrect.
Control: outlook -2 This was done for libseqlib's sake: libseqlib needs to be 
patched/fixed instead to work correctly with an unpatched htslib.
Control: retitle -3 htslib: please do not package htslib*.mk makefile fragments
Control: summary -3 These provide rules and dependencies that are useful when 
building client software against an in-development HTSlib source tree, so 
should not be used by anything when htslib is in a packaged format.
Control: outlook -3 debian/changelog suggests these are installed for 
bcftools's sake. If these are needed when building bcftools against an 
installed HTSlib, either you are configuring bcftools incorrectly or there is a 
bug in bcftools.



Hello everybody!

So, I'm splitting this bug in multiple parts, because they are different
things, that need different actions and some even changes in external
packages, and they definitely need not to be done in one shot.
They also have different severity for how Debian is concerned
(https://www.debian.org/Bugs/Developer#severities).

Please look up the appropriate number
(https://bugs.debian.org/src:htslib) that got assigned to each issue and
carry on separate conversations in the appropriate bug because they
really are orthogonal.  Consider also changing the subject for the first
reply.

On Wed, Nov 08, 2017 at 12:31:47PM +, John Marshall wrote:
> There are several packaging infelicities in testing/unstable libhts-dev:

Thank you so much for rising this issue.
Whilst I'm not directly involved in htslib and related packages (I got
poked because I forced a slighly broken version of pysam through just to
complete the python3.5→python3.6 transition), I can tell you that is
very very helpful whenever upstream involves himself in the
distribution, and there is an healthy cooperation between us and them.
Sadly most of the time this is not true (and I believe that's the source
of all there is in this bug: somebody not even bothering asking you for
changes due to their past experience with other developers).

> 1. The cram/*.h headers are private and should not be packaged

Let's track this in -1 (i.e. this very bug)

> 2. debian/patches/fix_pkg-config.patch is incorrect

Let's track this in -2.

> 3. The htslib*.mk makefile fragments should not be packaged

Let's track this in -3

> In general, upstream's "make install" rule reflects what upstream
> thinks should be installed. If you find yourselves desiring to
> install other things too, it would be good to contact upstream so
> that a solution can be reached that fixes the problem for everyone.

YES.
I wholeheartedly agree with this.
I just hope whoever find themselves doing it in the future will think
about it :)
Also, if you see something else is off in our package please file a bug
report!

Thank you again for report and for caring about Debian!


ps: I know I used some commands above that most people don't even know
about.  If you feel like you are not supposed to understand them, then
probably you indeed need not :)
-- 
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

Bug#881162: Pending fixes for bugs in the tomcat7 package

[pkg-java-maintainers]

tag 881162 + pending
thanks

Some bugs in the tomcat7 package are closed in revision
9ec56770ae1c0aef52bcfeb22205456959269a13 in branch '  wheezy' by
Roberto C. Sanchez

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/tomcat7.git/commit/?id=9ec5677

Commit message:

Import Debian changes 7.0.28-4+deb7u17

tomcat7 (7.0.28-4+deb7u17) wheezy-security; urgency=high

  * Non-maintainer upload by the LTS Security Team.
  * Fix regression introduced by patch for CVE-2017-12617 (Closes: #881162)

Bug#880308: CLA Diet is the end of obesity zj

[kayess59]

Stop sending me emails 


Sent from my MetroPCS 4G LTE Android Device
 Original message From: CLA Diet  Date: 
11/10/17  1:00 PM  (GMT-05:00) To: 880...@bugs.debian.org Subject: CLA Diet is 
the end of obesity zj 













































































































































































































































On 2017-10-30, Lucas Nussbaum wrote:
>>  /bin/bash ../../libtool   --mode=install /usr/bin/install -c   libvnc.la 
>> '/<>/tigervnc-1.7.0+dfsg/debian/tmp//lib/xorg/modules/extensions'
>> libtool: install: /usr/bin/install -c .libs/libvnc.so 
>> /<>/tigervnc-1.7.0+dfsg/debian/tmp//lib/xorg/modules/extensions/libvnc.so
...
>> dh_install: Cannot find (any matches for) 
>> "usr/lib/xorg/modules/extensions/libvnc.so" (tried in ., debian/tmp)
>> 
>> dh_install: tigervnc-xorg-extension missing files: 
>> usr/lib/xorg/modules/extensions/libvnc.so
>> dh_install: missing files, aborting
>> /usr/share/cdbs/1/rules/debhelper.mk:233: recipe for target 
>> 'binary-install/tigervnc-xorg-extension' failed
>> make: ***  Error 25

The install target appears to be dropping /usr for this particular file
on sid, but rebuilding the same sources on stretch /usr is included...


This suggests a deeper problem, such as something in the build process
ignoring CMAKE_INSTALL_PREFIX ... but can be worked around in the
package:

diff --git a/debian/tigervnc-xorg-extension.install 
b/debian/tigervnc-xorg-extension.install
index 8d6fffa..f74dabd 100644
--- a/debian/tigervnc-xorg-extension.install
+++ b/debian/tigervnc-xorg-extension.install
@@ -1 +1 @@
-usr/lib/xorg/modules/extensions/libvnc.so usr/lib/xorg/modules/extensions
+lib/xorg/modules/extensions/libvnc.so usr/lib/xorg/modules/extensions


I've only test that the package successfully builds with this patch; I
haven't tested that it actually works.


live well,
  vagrant

Bug#880308:

[Joe Distin]

Please take me out of your mailing list thank you

Bug#881358: nvidia_drv_video.so has no function __vaDriverInit_1_0

[Anthony DeRobertis]

Package: vdpau-va-driver
Version: 0.7.4-6
Severity: grave

anthony@Zia:~ [$?=3]$ vainfo 
libva info: VA-API version 1.0.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/nvidia_drv_video.so
libva error: /usr/lib/x86_64-linux-gnu/dri/nvidia_drv_video.so has no function 
__vaDriverInit_1_0
libva info: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error),exit

And indeed, it does not:

anthony@Zia:~$ nm --demangle -D 
/usr/lib/x86_64-linux-gnu/dri/nvidia_drv_video.so  | grep vaDriverInit
6320 T __vaDriverInit_0_31
6d40 T __vaDriverInit_0_39


-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'testing'), (200, 'unstable'), (150, 'stable'), (100, 'experimental'), (1, 
'experimental-debug')
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:en_GB (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages vdpau-va-driver depends on:
ii  libc6   2.24-17
ii  libgl1  0.2.999+git20170802-5
ii  libgl1-mesa-glx 17.2.4-1+b1
ii  libva1 [libva-driver-abi-0.39]  1.8.3-2
ii  libvdpau1   1.1.1-8
ii  libx11-62:1.6.4-3

vdpau-va-driver recommends no packages.

vdpau-va-driver suggests no packages.

-- no debconf information

Bug#880308: CLA Diet is the end of obesity CMDJ

[Joe Distin]

Please delete me from your mailing list thank you

On Nov 10, 2017 1:52 PM, "CLA Diet"  wrote:

>
> 
>
> 
>
> 
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> On 2017-10-30, Lucas Nussbaum wrote: >> /bin/bash ../../libtool
> --mode=install /usr/bin/install -c libvnc.la '/<>/tigervnc-1.7.0+dfsg/
> debian/tmp//lib/xorg/modules/extensions' >> libtool: install:
> /usr/bin/install -c .libs/libvnc.so /<>/tigervnc-1.7.0+dfsg/
> debian/tmp//lib/xorg/modules/extensions/libvnc.so ... >> dh_install:
> Cannot find (any matches for) "usr/lib/xorg/modules/extensions/libvnc.so"
> (tried in ., debian/tmp) >> >> dh_install: tigervnc-xorg-extension missing
> files: usr/lib/xorg/modules/extensions/libvnc.so >> dh_install: missing
> files, aborting >> /usr/share/cdbs/1/rules/debhelper.mk:233: recipe for
> target 'binary-install/tigervnc-xorg-extension' failed >> make: *** Error
> 25 The install target appears to be dropping /usr for this particular file
> on sid, but rebuilding the same sources on stretch /usr is included... This
> suggests a deeper problem, such as something in the build process ignoring
> CMAKE_INSTALL_PREFIX ... but can be worked around in the package: diff
> --git a/debian/tigervnc-xorg-extension.install 
> b/debian/tigervnc-xorg-extension.install
> index 8d6fffa..f74dabd 100644 --- a/debian/tigervnc-xorg-extension.install
> +++ b/debian/tigervnc-xorg-extension.install @@ -1 +1 @@
> -usr/lib/xorg/modules/extensions/libvnc.so usr/lib/xorg/modules/extensions
> +lib/xorg/modules/extensions/libvnc.so usr/lib/xorg/modules/extensions
> I've only test that the package successfully builds with this patch; I
> haven't tested that it actually works. live well, vagrant

Bug#880308:

[Elizabeth Little]

Send info

Bug#881110: cacti: CVE-2017-16641: arbitrary execution of os commands via path_rrdtool parameter in an action=save request

[Paul Gevers]

Control: found 881110 0.8.8a+dfsg-5+deb7u10

On 07-11-17 22:17, Salvatore Bonaccorso wrote:
> Please adjust the affected versions in the BTS as needed, only did
> check unstable's version for now source-wise.

All versions in Debian are affected.

Unfortunately the upstream commit contains much unneeded changes to fix
the issue. Additionally for pre-buster fixes, the code in settings.php
is seriously different.

Paul




signature.asc
Description: OpenPGP digital signature

Bug#878722: bts reassign 878722 partman-auto

[Nicholas D Steeves]

On Fri, Nov 10, 2017 at 12:32:59PM -0500, Lennart Sorensen wrote:
> On Fri, Nov 10, 2017 at 04:19:14PM +, Ben Hutchings wrote:
> > This is true, but I don't think it's a good reason not to implement a
> > mostly-reliable heuristic.
> > 
> > If there are multiple disks, there are usually going to be just 2 of
> > them, one of which contains the installer.  In any installer build
> > other than netboot, it will look for its own disk in order to load
> > udebs.  Once it has done that, it can determine that the other disk is
> > the one to install on.  That's a pretty good heuristic.
> 
> I think more than one disk in the machine isn't that unusual.

Is there any reason why the following method wouldn't be an
improvement?:

1) get a list of disks
2) identify the disk used by the installer
3) exclude the disk found at #2
4) present modified list as target disks for installation
5) unless in expert mode, where a user could use one partition of a
disk as the installation source and another partition as the
installation target.  I'm not sure how important #5 is, but maybe some
users want to be able to do this?

Cheers,
Nicholas


signature.asc
Description: PGP signature

Bug#881357: runit: Please remove -x from preinst

[Christoph Biedl]

Package: runit
Version: 2.1.2-9.2
Severity: minor
# for lack of Severity: nitpicking

Dear Maintainer,

runit.preinst runs with the -x option set, presumably for debugging.
Although in general it's just one additional line of internals shown,
please remove this again when convenient,

Christoph


signature.asc
Description: Digital signature

Bug#740894: gmsh: please make tetgen an optional feature for gmsh

[Francesco Poli]

On Sat, 29 Oct 2016 18:17:29 +0200 Francesco Poli wrote:

> On Fri, 30 Sep 2016 19:23:38 +0200 Francesco Poli wrote:
> 
> > On Wed, 05 Mar 2014 23:44:24 +0100 Francesco Poli (wintermute) wrote:
> > 
> > [...]
> > > Since I think the GNU AfferoGPL v3 is non-free, I would like to kindly
> > > ask you to make tetgen support in gmsh an optional feature, so that
> > > libtet1.5 may be downgraded from the Depends to the Recommends control
> > > field.
> > > 
> [...]
> > > I really hope this can be done.
> > > Thanks for your time and patience.
> > 
> > Hello,
> > is there any progress on this issue?
> > 
> > Is what I ask feasible?
> > Has my feature request been forwarded upstream?
> > 
> > Please let me know, thanks for your time!
> 
> Ping?

Second ping?


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpIbBWGOLE5q.pgp
Description: PGP signature

Bug#881293: [Pkg-libvirt-maintainers] Bug#881293: libvirt-daemon: libvirtd sefgfault when disconnect and reconnect iso

[Guido Günther]

Hi,
On Fri, Nov 10, 2017 at 10:14:27AM -0700, Jeff Ketchum wrote:
> It does it for any windows vm I have tested it on.
> I am not sure of the commands, I am using virt-manager to manage these, Is
> there an easy way to get the commands?
> When this happens, virt-manager also loses connectivity to the local
> hypervisor.

See

https://wiki.debian.org/libvirt/Debugging#Virt-manager

If s.th. is unclear let me know and I'll update the docs.

Cheers,
 -- Guido

> 
> On Thu, Nov 9, 2017 at 11:55 PM, Guido Günther  wrote:
> 
> > Hi,
> > On Thu, Nov 09, 2017 at 11:47:01AM -0700, Jeff Ketchum wrote:
> > > Package: libvirt-daemon
> > > Version: 3.9.0-1
> > > Severity: important
> > >
> > >
> > > [  271.168779] libvirtd[1177]: segfault at 10 ip 7f2cae6d9208 sp
> > 7f2cb80049a0 error 4 in libvirt_driver_qemu.so[7f2cae64d000+173000]
> >
> > Domain XML and virsh commands you use for disconnect / reconnect
> > please.
> > Cheers,
> >  -- Guido
> >
> > >
> > > -- System Information:
> > > Debian Release: buster/sid
> > >   APT prefers unstable
> > >   APT policy: (500, 'unstable')
> > > Architecture: amd64 (x86_64)
> > > Foreign Architectures: i386
> > >
> > > Kernel: Linux 4.13.0-1-amd64 (SMP w/8 CPU cores)
> > > Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8),
> > LANGUAGE=en_US.utf8 (charmap=UTF-8)
> > > Shell: /bin/sh linked to /bin/dash
> > > Init: systemd (via /run/systemd/system)
> > >
> > > Versions of packages libvirt-daemon depends on:
> > > ii  libacl1 2.2.52-3+b1
> > > ii  libapparmor12.11.1-3
> > > ii  libaudit1   1:2.8.1-2
> > > ii  libavahi-client30.7-3
> > > ii  libavahi-common30.7-3
> > > ii  libblkid1   2.30.2-0.1
> > > ii  libc6   2.24-17
> > > ii  libcap-ng0  0.7.7-3.1+b1
> > > ii  libcurl3-gnutls 7.56.1-1
> > > ii  libdbus-1-3 1.12.0-1
> > > ii  libdevmapper1.02.1  2:1.02.145-1
> > > ii  libfuse22.9.7-1
> > > ii  libgnutls30 3.5.16-1
> > > ii  libnetcf1   1:0.2.8-1+b2
> > > ii  libnl-3-200 3.2.27-2
> > > ii  libnl-route-3-200   3.2.27-2
> > > ii  libnuma12.0.11-2.1
> > > ii  libparted2  3.2-18
> > > ii  libpcap0.8  1.8.1-5
> > > ii  libpciaccess0   0.13.4-1+b2
> > > ii  libsasl2-2  2.1.27~101-g0780600+dfsg-3
> > > ii  libselinux1 2.7-2
> > > ii  libssh2-1   1.8.0-1
> > > ii  libudev1235-2
> > > ii  libvirt03.9.0-1
> > > ii  libxen-4.8  4.8.1-1+deb9u3
> > > ii  libxenstore3.0  4.8.1-1+deb9u3
> > > ii  libxml2 2.9.4+dfsg1-5+b1
> > > ii  libyajl22.1.0-2+b3
> > >
> > > Versions of packages libvirt-daemon recommends:
> > > ii  libxml2-utils   2.9.4+dfsg1-5+b1
> > > ii  netcat-openbsd  1.178-3
> > > ii  qemu1:2.10.0+dfsg-2
> > > ii  qemu-kvm1:2.10.0+dfsg-2
> > >
> > > Versions of packages libvirt-daemon suggests:
> > > pn  libvirt-daemon-driver-storage-gluster   
> > > pn  libvirt-daemon-driver-storage-rbd   
> > > pn  libvirt-daemon-driver-storage-sheepdog  
> > > pn  libvirt-daemon-driver-storage-zfs   
> > > ii  libvirt-daemon-system   3.9.0-1
> > > pn  numad   
> > >
> > > -- no debconf information
> > >
> > > ___
> > > Pkg-libvirt-maintainers mailing list
> > > pkg-libvirt-maintain...@lists.alioth.debian.org
> > > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/
> > pkg-libvirt-maintainers
> > >
> >

Bug#881354: beancounter: Updates fail since 2017-11-01

[Dirk Eddelbuettel]

On 10 November 2017 at 19:02, Lars Bensmann wrote:
| Package: beancounter
| Version: 0.8.10
| Severity: important
| 
| On November 11, 2017 beancounter quote updates stopped working and have
| not been working since.

Yes.

Yahoo! stopped providing data in the format / as the service which the
Finance::YahooQuote module depends upon.

So this package will be retired.  One day I'll write a new one in R.

Dirk
 
| $ beancounter update
| Argument "html>" isn't numeric in division (/) at 
/usr/share/perl5/Finance/BeanCounter.pm line 1622.
| Argument "finance.yahoo.com.<" isn't numeric in division (/) at 
/usr/share/perl5/Finance/BeanCounter.pm line 1622.
| Illegal division by zero at /usr/share/perl5/Finance/BeanCounter.pm line 1622.
| 
| 
| -- System Information:
| Debian Release: 9.1
|   APT prefers stable-updates
|   APT policy: (500, 'stable-updates'), (500, 'stable')
| Architecture: amd64 (x86_64)
| Foreign Architectures: i386
| 
| Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
| Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
| Shell: /bin/sh linked to /bin/dash
| Init: systemd (via /run/systemd/system)
| 
| Versions of packages beancounter depends on:
| ii  libdate-manip-perl 6.57-1
| ii  libdbd-mysql-perl  4.041-2
| ii  libdbd-sqlite3-perl1.54-1
| ii  libdbi-perl1.636-1+b1
| ii  libfinance-yahooquote-perl 0.25
| ii  libstatistics-descriptive-perl 3.0612-1
| ii  perl   5.24.1-3+deb9u2
| ii  postgresql-client-9.2 [postgresql-client]  9.2.4-2.pgdg70+1
| ii  postgresql-client-9.4 [postgresql-client]  9.4.12-0+deb8u1
| ii  postgresql-client-9.6 [postgresql-client]  9.6.4-0+deb9u1
| ii  sqlite 2.8.17-14
| ii  sqlite33.16.2-5
| 
| beancounter recommends no packages.
| 
| beancounter suggests no packages.
| 
| -- no debconf information
| 
| -- debsums errors found:
| debsums: changed file /usr/bin/beancounter (from beancounter package)
| debsums: changed file /usr/share/perl5/Finance/BeanCounter.pm (from 
beancounter package)

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#881356: libportmidi-dev: Provide portmidi.pc file

[Jaromír Mikeš]

Package: libportmidi-dev
Version: 1:217-6
Severity: normal

Hi,

while trying build Audacity package with as many as possible system libs we
found a problem ...
portmidi library cannot be found by
audacity when passing --with-portmidi=system to the configure script.

Providing portmidi.pc file by libportmidi-dev should fix this issue.

best regards

mira



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

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

Versions of packages libportmidi-dev depends on:
ii  libportmidi0  1:217-6

libportmidi-dev recommends no packages.

libportmidi-dev suggests no packages.

-- no debconf information

Bug#878804: RFS: shotwell/0.26.3-1

[Jeremy Bicha]

On Sun, Oct 22, 2017 at 5:08 PM, Ghislain Vaillant  wrote:
> On 22/10/17 21:12, Jeremy Bicha wrote:
>> 3. I'm attaching a patch to fix the install of appstream metadata.
>> You'll also need to modify debian/shotwell.install to install the
>> metadata.
>>
>> --- debian/shotwell.install2017-09-22 17:26:18.0 -0400
>> +++ ../debian/shotwell.install2017-10-22 15:59:36.667571371 -0400
>> @@ -1,3 +1,4 @@
>>   usr/bin
>>   usr/lib
>>   usr/share/applications
>> +usr/share/appdata
>
>
> From the AppStream guidelines [1], the metadata are to be installed under
> /usr/share/metainfo not /usr/share/appdata. Otherwise, Lintian will trigger
> a warning [2].

That's a warning that in my opinion ought to be fixed upstream instead
of just working around it in the Debian packaging. So I filed

https://bugzilla.gnome.org/790185

There's a new upstream version 0.26.4 which includes the patch I
proposed last month.

But as a workaround for now, if you want to install the metadata to
/usr/share/metainfo/ you can add this to the header in
debian/copyright before using uscan to fetch the new version:

Files-Excluded: m4

And add Build-Depends on autoconf-archive, libglib2.0-dev-bin and
yelp-tools. That should probably be done anyway to avoid code
duplication and ensure we are building with the latest versions of the
autoconf macros.

Thanks,
Jeremy Bicha

Bug#881355: eztrace FTBFS on armel: undefined reference to `trace_read'

[Adrian Bunk]

Source: eztrace
Version: 1.1-7-1
Severity: serious
Tags: patch

https://buildd.debian.org/status/fetch.php?pkg=eztrace=armel=1.1-7-3=1510079529=0

...
../pptrace/eztrace-isize.o: In function `opcode_get_overridden_size':
./build-mpich/src/core/../../../src/core/../pptrace/arch/armv7/opcode.c:33: 
undefined reference to `trace_read'
collect2: error: ld returned 1 exit status
Makefile:838: recipe for target 'eztrace' failed
make[3]: *** [eztrace] Error 1


Fix is attached.
Description: Fix FTBFS on armel
 __arm__ is not a test for >= ARMv7.
Author: Adrian Bunk 

--- eztrace-1.1-7.orig/configure.ac
+++ eztrace-1.1-7/configure.ac
@@ -112,6 +112,7 @@ case "$host" in
AC_MSG_WARN([ARCH: ARM])
arch_str="ARM"
CFLAGS="$CFLAGS -marm"
+   AC_DEFINE([HAVE_ARM], [1], [Using ARM support])
;;
*)
AC_MSG_WARN([unknown architecture: falling back to x86_64])
--- eztrace-1.1-7.orig/src/pptrace/isize.c
+++ eztrace-1.1-7/src/pptrace/isize.c
@@ -27,7 +27,7 @@
 #include "arch/x86_64/trace.c"
 #endif // ! (__PPTRACE_ISIZE_TYPE == PPTRACE_ISIZE_TYPE_OPCODE)
 #endif // !defined(__PPTRACE_ISIZE_TYPE)
-#elif __arm__
+#elif HAVE_ARM
 // ARMv7
 
 #ifdef HAVE_LIBOPCODE

Bug#881354: beancounter: Updates fail since 2017-11-01

[Lars Bensmann]

Package: beancounter
Version: 0.8.10
Severity: important

On November 11, 2017 beancounter quote updates stopped working and have
not been working since.

$ beancounter update
Argument "html>" isn't numeric in division (/) at 
/usr/share/perl5/Finance/BeanCounter.pm line 1622.
Argument "finance.yahoo.com.<" isn't numeric in division (/) at 
/usr/share/perl5/Finance/BeanCounter.pm line 1622.
Illegal division by zero at /usr/share/perl5/Finance/BeanCounter.pm line 1622.


-- System Information:
Debian Release: 9.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages beancounter depends on:
ii  libdate-manip-perl 6.57-1
ii  libdbd-mysql-perl  4.041-2
ii  libdbd-sqlite3-perl1.54-1
ii  libdbi-perl1.636-1+b1
ii  libfinance-yahooquote-perl 0.25
ii  libstatistics-descriptive-perl 3.0612-1
ii  perl   5.24.1-3+deb9u2
ii  postgresql-client-9.2 [postgresql-client]  9.2.4-2.pgdg70+1
ii  postgresql-client-9.4 [postgresql-client]  9.4.12-0+deb8u1
ii  postgresql-client-9.6 [postgresql-client]  9.6.4-0+deb9u1
ii  sqlite 2.8.17-14
ii  sqlite33.16.2-5

beancounter recommends no packages.

beancounter suggests no packages.

-- no debconf information

-- debsums errors found:
debsums: changed file /usr/bin/beancounter (from beancounter package)
debsums: changed file /usr/share/perl5/Finance/BeanCounter.pm (from beancounter 
package)

Bug#881341: webkit2gtk FTCBFS: debian/rules confuses build and host

[Helmut Grohne]

On Fri, Nov 10, 2017 at 05:08:53PM +0200, Alberto Garcia wrote:
> On Fri, Nov 10, 2017 at 03:49:58PM +0100, Helmut Grohne wrote:
> > ifeq ($(DEB_HOST_ARCH_BITS),32)
> > LDFLAGS += -Wl,--no-keep-memory
> >  endif
> >  
> > -ifeq ($(DEB_BUILD_ARCH),alpha)
> > +ifeq ($(DEB_HOST_ARCH),alpha)
> > LDFLAGS += -Wl,--no-relax
> >  endif
> 
> Wait a minute, why do you change this to DEB_HOST_ARCH here? Shouldn't
> we be using the DEB_BUILD_* variables in these two cases?

I think you are confusing build and host again.

If you check DEB_BUILD_ARCH, then you will pass -Wl,--no-relax when
building for amd64 on alpha. Since --no-relax is machine-dependent, that
seems wrong to me. In general, changing the build architecture should
not affect the resulting binary packages. Passing different flags for
different build architectures often breaks that.

Helmut

Bug#878685: stretch-pu: package udftools/1.3-2

[Adam D. Barratt]

On Fri, 2017-11-10 at 12:17 +0100, Pali Rohár wrote:
> On Thursday 02 November 2017 21:55:54 Pali Rohár wrote:
> > On Sunday 29 October 2017 18:19:53 Adam D. Barratt wrote:
> > > Please prepare an upload built and tested on stable, using
> > > "stretch" as
> > > the changelog distribution, and versioned as either 1.3-1+deb9u1
> > > or
> > > 1.3-2~deb9u1, depending on how the changelog is structured, and
> > > attach
> > > the debdiff to this bug log.
> > 
> > Ok. I uploaded package version 1.3-2~deb9u1 to mentors, it is
> > there:
> > https://mentors.debian.net/package/udftools
> > 
> > debdiff between current version in stretch and 1.3-2~deb9u1 is
> > attached.
> 
> Can you review it?

It will be, when someone next goes through the stable-new queue.

> According to highvoltage comment, Package has been uploaded to
> Debian,

Correct. However, it preferably shouldn't have been, because the upload
wasn't agreed yet; CCing the uploader.

Particularly, I'd have pointed out that the changelog is illogical - it
should either be 1.3-1, then the 1.3-2 unstable changes, then 1.3-
2~deb9u1, or 1.3-1 then 1.3-1+deb9u1.

> but still is not available in the stable

Also correct. Packages only get added to stable during point releases,
and there hasn't been one of those since before you filed the request.

> and link to the new queue
> "stable-new: 1.3-2~deb9u1" on package
> https://qa.debian.org/developer.php?login=pali.rohar%40gmail.com
> generate just 404 Not Found.
> 
> Was package lost that it generates 404?

No, the link on the QA side is broken, so it's not surprising that it
generates a 404.

Specifically, it points to the NEW queue managed by ftp-master, which
is not related to stable-new (which is a holding queue in front of
proposed-updates and managed by the Release Team).

Regards,

Adam

Bug#880308: tigervnc: FTBFS: dh_install: missing files, aborting

[Vagrant Cascadian]

On 2017-10-30, Lucas Nussbaum wrote:
>>  /bin/bash ../../libtool   --mode=install /usr/bin/install -c   libvnc.la 
>> '/<>/tigervnc-1.7.0+dfsg/debian/tmp//lib/xorg/modules/extensions'
>> libtool: install: /usr/bin/install -c .libs/libvnc.so 
>> /<>/tigervnc-1.7.0+dfsg/debian/tmp//lib/xorg/modules/extensions/libvnc.so
...
>> dh_install: Cannot find (any matches for) 
>> "usr/lib/xorg/modules/extensions/libvnc.so" (tried in ., debian/tmp)
>> 
>> dh_install: tigervnc-xorg-extension missing files: 
>> usr/lib/xorg/modules/extensions/libvnc.so
>> dh_install: missing files, aborting
>> /usr/share/cdbs/1/rules/debhelper.mk:233: recipe for target 
>> 'binary-install/tigervnc-xorg-extension' failed
>> make: *** [binary-install/tigervnc-xorg-extension] Error 25

The install target appears to be dropping /usr for this particular file
on sid, but rebuilding the same sources on stretch /usr is included...


This suggests a deeper problem, such as something in the build process
ignoring CMAKE_INSTALL_PREFIX ... but can be worked around in the
package:

diff --git a/debian/tigervnc-xorg-extension.install 
b/debian/tigervnc-xorg-extension.install
index 8d6fffa..f74dabd 100644
--- a/debian/tigervnc-xorg-extension.install
+++ b/debian/tigervnc-xorg-extension.install
@@ -1 +1 @@
-usr/lib/xorg/modules/extensions/libvnc.so usr/lib/xorg/modules/extensions
+lib/xorg/modules/extensions/libvnc.so usr/lib/xorg/modules/extensions


I've only test that the package successfully builds with this patch; I
haven't tested that it actually works.


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#880576: targetcli-fb: Cannot create PSCSI backend for SCSI tape drive

[Christian Seiler]

Hi,

On 11/10/2017 05:37 PM, Herbert Nachtnebel wrote:
> I can confirm that using the tape drive from another host does work
> like a charm after manually creating the pscsi backend using
> configfs, yeah!

Fantastic!

> Thanks Christian for your input solving this issue!
> If you already have a patch for targetcli to use sysfs'
> /bus/scsi/devices/... for detecting the real device paths, I am eager
> to test it.

I don't have one yet because I wanted to wait for your feedback (and
was quite busy with other things this week), but I'll work on one
during the weekend. I'll post an update to this bug report once I've
got a fixed package, and if you say it works for you I'll take care
of getting that into Debian.

Regards,
Christian

Bug#878722: bts reassign 878722 partman-auto

[Lennart Sorensen]

On Fri, Nov 10, 2017 at 04:19:14PM +, Ben Hutchings wrote:
> This is true, but I don't think it's a good reason not to implement a
> mostly-reliable heuristic.
> 
> If there are multiple disks, there are usually going to be just 2 of
> them, one of which contains the installer.  In any installer build
> other than netboot, it will look for its own disk in order to load
> udebs.  Once it has done that, it can determine that the other disk is
> the one to install on.  That's a pretty good heuristic.

I think more than one disk in the machine isn't that unusual.

> Aside from that, we can also make a guess based on the bus type:
> 
> - ATA: probably internal

eSATA is not that unusual.

> - NVMe: probably internal
> - USB: probably external
> - MMC/SD: ambiguous (eMMC must be internal, and Linux has a notion of
> 'non-removable' slots, but I don't think userland has this info)
> 
> If we could get more information about MMC/SD slots then we should be
> able to implement an heuristic that would work for >99% of cases.

You can certainly try to make a good guess, but it certainly still needs
to be confirmed.

-- 
Len Sorensen

Bug#881293: [Pkg-libvirt-maintainers] Bug#881293: libvirt-daemon: libvirtd sefgfault when disconnect and reconnect iso

[Jeff Ketchum]

It does it for any windows vm I have tested it on.
I am not sure of the commands, I am using virt-manager to manage these, Is
there an easy way to get the commands?
When this happens, virt-manager also loses connectivity to the local
hypervisor.

On Thu, Nov 9, 2017 at 11:55 PM, Guido Günther  wrote:

> Hi,
> On Thu, Nov 09, 2017 at 11:47:01AM -0700, Jeff Ketchum wrote:
> > Package: libvirt-daemon
> > Version: 3.9.0-1
> > Severity: important
> >
> >
> > [  271.168779] libvirtd[1177]: segfault at 10 ip 7f2cae6d9208 sp
> 7f2cb80049a0 error 4 in libvirt_driver_qemu.so[7f2cae64d000+173000]
>
> Domain XML and virsh commands you use for disconnect / reconnect
> please.
> Cheers,
>  -- Guido
>
> >
> > -- System Information:
> > Debian Release: buster/sid
> >   APT prefers unstable
> >   APT policy: (500, 'unstable')
> > Architecture: amd64 (x86_64)
> > Foreign Architectures: i386
> >
> > Kernel: Linux 4.13.0-1-amd64 (SMP w/8 CPU cores)
> > Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8),
> LANGUAGE=en_US.utf8 (charmap=UTF-8)
> > Shell: /bin/sh linked to /bin/dash
> > Init: systemd (via /run/systemd/system)
> >
> > Versions of packages libvirt-daemon depends on:
> > ii  libacl1 2.2.52-3+b1
> > ii  libapparmor12.11.1-3
> > ii  libaudit1   1:2.8.1-2
> > ii  libavahi-client30.7-3
> > ii  libavahi-common30.7-3
> > ii  libblkid1   2.30.2-0.1
> > ii  libc6   2.24-17
> > ii  libcap-ng0  0.7.7-3.1+b1
> > ii  libcurl3-gnutls 7.56.1-1
> > ii  libdbus-1-3 1.12.0-1
> > ii  libdevmapper1.02.1  2:1.02.145-1
> > ii  libfuse22.9.7-1
> > ii  libgnutls30 3.5.16-1
> > ii  libnetcf1   1:0.2.8-1+b2
> > ii  libnl-3-200 3.2.27-2
> > ii  libnl-route-3-200   3.2.27-2
> > ii  libnuma12.0.11-2.1
> > ii  libparted2  3.2-18
> > ii  libpcap0.8  1.8.1-5
> > ii  libpciaccess0   0.13.4-1+b2
> > ii  libsasl2-2  2.1.27~101-g0780600+dfsg-3
> > ii  libselinux1 2.7-2
> > ii  libssh2-1   1.8.0-1
> > ii  libudev1235-2
> > ii  libvirt03.9.0-1
> > ii  libxen-4.8  4.8.1-1+deb9u3
> > ii  libxenstore3.0  4.8.1-1+deb9u3
> > ii  libxml2 2.9.4+dfsg1-5+b1
> > ii  libyajl22.1.0-2+b3
> >
> > Versions of packages libvirt-daemon recommends:
> > ii  libxml2-utils   2.9.4+dfsg1-5+b1
> > ii  netcat-openbsd  1.178-3
> > ii  qemu1:2.10.0+dfsg-2
> > ii  qemu-kvm1:2.10.0+dfsg-2
> >
> > Versions of packages libvirt-daemon suggests:
> > pn  libvirt-daemon-driver-storage-gluster   
> > pn  libvirt-daemon-driver-storage-rbd   
> > pn  libvirt-daemon-driver-storage-sheepdog  
> > pn  libvirt-daemon-driver-storage-zfs   
> > ii  libvirt-daemon-system   3.9.0-1
> > pn  numad   
> >
> > -- no debconf information
> >
> > ___
> > Pkg-libvirt-maintainers mailing list
> > pkg-libvirt-maintain...@lists.alioth.debian.org
> > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/
> pkg-libvirt-maintainers
> >
>

  win2k12r2
  8e3b48c5-14d8-4430-aa94-be8901f0d33d
  1048576
  1048576
  1
  
hvm
/usr/share/OVMF/OVMF_CODE.fd
/var/lib/libvirt/qemu/nvram/win2k12r2_VARS.fd

  
  



  
  
  


  
  
Haswell-noTSX
  
  




  
  destroy
  restart
  destroy
  


  
  
/usr/bin/kvm

  


  
  


  
  


  
  



  


  
  
  
  


  


  


  
  


  




  
  


  


  
  


  


  


  

  

Bug#875233: [pkg-wpa-devel] Bug#875233: [wpa] Future Qt4 removal from Buster

[Andrew Shadura]

On 10 November 2017 at 17:24, Reiner Herrmann  wrote:
> Control: tags -1 + patch
>
> The attached patch against 2:2.6-5 builds wpa_gui with Qt5.

Ack! Thanks, will apply ~soon.

-- 
Cheers,
  Andrew

Bug#881353: smb.conf: client max protocol = default limits connections to SMB1

[wolfgang]

Package: samba-common
Version: 2:4.5.12+dfsg-2
Severity: normal

Dear Maintainer,

I was trying to access the shares on my LibreELEC box which was recently 
upgraded to v8.2.0.
This upgrade disabled SMB1 support on LibreELEC. Trying to access the shares 
with Thunar
gave me a "Failed to retrieve share list from server" error.

Running "smbclient -L libreelec" shows:
protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE

After some research I think I found the problem:
In smb.conf the option 'client max protocol' is not set (and according to the 
smb.conf man page it shouldn't be).

"testparm -v | grep protocol" shows:

client ipc max protocol = default
client ipc min protocol = default
client max protocol = default
client min protocol = CORE
server max protocol = SMB3
server min protocol = LANMAN1


According to the man page: "The value default refers to NT1."
AFAIK NT1 means SMB1, so the default setting limits the client to SMB1.
And if the server doesn't support SMB1 the connection doesn't work.

A soulution is to set "client max protocol = SMB3" in /etc/samba/smb.conf (or 
in ~/.smb/smb.conf.append).
However this only works if samba-common is installed. In my case it wasn't 
installed.
I think Thunar doesn't need it since it uses libsmbclient.

So for network shares to work out of the box I think this needs to be fixed, 
ideally in a way
that makes libsmbclient work without the need for /etc/samba/smb.conf 
(samba-common).


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

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

Versions of packages samba-common depends on:
ii  debconf [debconf-2.0]  1.5.61
ii  dpkg   1.18.24
ii  ucf3.0036

Versions of packages samba-common recommends:
ii  samba-common-bin  2:4.5.12+dfsg-2

samba-common suggests no packages.

-- debconf information excluded

Bug#881351: ldtp: Please depend on python-pyatspi instead of python-pyatspi2

[Samuel Thibault]

Source: ldtp
Version: 2.3.1-1
Severity: important

Hello,

python-pyatspi2 was a transition package since some time, we plan to
remove it in Buster, so please switch to python-pyatspi as the attached
patch suggests.

Samuel

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

Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- debian/control.orig 2017-11-10 17:43:26.628063130 +0100
+++ debian/control  2017-11-10 17:43:30.200047024 +0100
@@ -17,7 +17,7 @@
  gir1.2-gtk-3.0,
  gir1.2-wnck-3.0,
  python-gobject,
- python-pyatspi2,
+ python-pyatspi,
  python-twisted-web
 Description: Linux Desktop Testing Project (LDTP)
  Linux Desktop Testing Project is aimed at producing high quality test
@@ -34,7 +34,7 @@
  gir1.2-gtk-3.0,
  gir1.2-wnck-3.0,
  python-gobject,
- python-pyatspi2,
+ python-pyatspi,
  python-twisted-web
 Provides: ${python:Provides}
 Description: Python bindings for LDTP

Bug#880576: targetcli-fb: Cannot create PSCSI backend for SCSI tape drive

[Herbert Nachtnebel]

Hi Folks!

I can confirm that using the tape drive from another host does work like 
a charm after manually creating the pscsi backend using configfs, yeah! 
Thanks Christian for your input solving this issue! If you already have 
a patch for targetcli to use sysfs' /bus/scsi/devices/... for detecting 
the real device paths, I am eager to test it.


Sincerely,
Herbert.

Bug#881350: first line of Android backup pushed off the screen

[積丹尼 Dan Jacobson]

X-Debbugs-Cc: bug-l...@gnu.org
Package: less
Version: 481-2.1
File: /bin/less

https://nelenkov.blogspot.tw/2012/06/unpacking-android-backups.html says
Android backus start with

ANDROID BACKUP
1
1
none
...

The problem is, in less the first line flies off the top. One would
never notice the file starts with ANDROID BACKUP unless one used hd, od,
etc.

Must be less counting wrongly the number of rows on the terminal due to
binary data.

$ env|grep LESS
LESS=-iRXM
SYSTEMD_LESS=-iRXM

As Android backups contain personal data, perhaps the developer could try
$ adb backup ... && less backup.ab
on his own. Or I can send the first part of one to some private email address.

Bug#879027: libtomcrypt: FTBFS on x32: final link failed: Bad value

[Michael Stapelberg]

You can get a guest account on Debian porter machines (we have one for
each architecture which Debian supports). Please follow
https://dsa.debian.org/doc/guest-account/, I’m happy to sponsor your
request.

On Fri, Nov 10, 2017 at 5:26 PM, Steffen Jaeckel  wrote:
> On 10/18/2017 05:31 PM, Michael Stapelberg wrote:
>> [+cc steffen, karel]
>>
>> Any clues about this build failure?
>>
>> On Wed, Oct 18, 2017 at 8:22 AM, Aaron M. Ucko  wrote:
>>> Source: libtomcrypt
>>> Version: 1.18-1
>>> Severity: important
>>> Justification: fails to build from source (but built successfully in the 
>>> past)
>>> User: debian-...@lists.debian.or
>>>
>>> The latest build of libtomcrypt for x32 (admittedly not a release
>>> architecture) failed per the below excerpts from
>>> https://buildd.debian.org/status/fetch.php?pkg=libtomcrypt=x32=1.18.0-1=1508165690=0:
>>>
>>>   libtool: compile:  gcc -I./src/headers/ -Wall -Wsign-compare -Wshadow 
>>> -DLTC_SOURCE -Wextra -Wsystem-headers -Wbad-function-cast -Wcast-align 
>>> -Wstrict-prototypes -Wpointer-arith -Wdeclaration-after-statement 
>>> -Wwrite-strings -Wno-type-limits -O3 -funroll-loops -fomit-frame-pointer 
>>> -DGIT_VERSION=\"1.18.0\" -g -O2 -fdebug-prefix-map=/<>=. 
>>> -specs=/usr/share/dpkg/pie-compile.specs -fstack-protector-strong -Wformat 
>>> -Werror=format-security -DGMP_DESC -DLTM_DESC -DUSE_LTM -Wdate-time 
>>> -D_FORTIFY_SOURCE=2 -specs=/usr/share/dpkg/pie-link.specs -Wl,-z,relro 
>>> -Wl,-z,now -c src/ciphers/aes/aes.c  -fPIC -DPIC -o 
>>> src/ciphers/aes/.libs/aes.o
>>>   [...]
>>>   libtool --mode=link --tag=CC gcc -I./src/headers/ -Wall -Wsign-compare 
>>> -Wshadow -DLTC_SOURCE -Wextra -Wsystem-headers -Wbad-function-cast 
>>> -Wcast-align -Wstrict-prototypes -Wpointer-arith 
>>> -Wdeclaration-after-statement -Wwrite-strings -Wno-type-limits -O3 
>>> -funroll-loops -fomit-frame-pointer -DGIT_VERSION=\"1.18.0\" -g -O2 
>>> -fdebug-prefix-map=/<>=. 
>>> -specs=/usr/share/dpkg/pie-compile.specs -fstack-protector-strong -Wformat 
>>> -Werror=format-security -DGMP_DESC -DLTM_DESC -DUSE_LTM -Wdate-time 
>>> -D_FORTIFY_SOURCE=2  -specs=/usr/share/dpkg/pie-link.specs -Wl,-z,relro 
>>> -Wl,-z,now src/ciphers/aes/aes.lo src/ciphers/aes/aes_enc.lo 
>>> src/ciphers/anubis.lo [...] src/stream/sober128/sober128_test.lo -lgmp 
>>> -ltommath -o libtomcrypt.la -rpath /usr/local/lib -version-info 1:0
>>>   libtool: link: gcc -shared  -fPIC -DPIC  src/ciphers/aes/.libs/aes.o 
>>> src/ciphers/aes/.libs/aes_enc.o src/ciphers/.libs/anubis.o [...] 
>>> src/stream/sober128/.libs/sober128_test.o   -lgmp -ltommath  -O3 -g -O2 
>>> -specs=/usr/share/dpkg/pie-compile.specs -fstack-protector-strong 
>>> -specs=/usr/share/dpkg/pie-link.specs -Wl,-z -Wl,relro -Wl,-z -Wl,now   
>>> -Wl,-soname -Wl,libtomcrypt.so.1 -o .libs/libtomcrypt.so.1.0.0
>>>   /usr/bin/ld: src/ciphers/aes/.libs/aes.o: relocation R_X86_64_PC32 
>>> against symbol `rijndael_setup' can not be used when making a shared 
>>> object; recompile with -fPIC
>>>   /usr/bin/ld: final link failed: Bad value
>>>   collect2: error: ld returned 1 exit status
>>>
>>> I'm not sure why the linker's complaining about missing an option you
>>> did in fact supply, but perhaps the use of pie-*.specs is somehow
>>> throwing things off; please try forgoing PIE on x32 for now.
>>>
>>> Thanks!
>>>
>>> --
>>> 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
>
> Any updates on this?
>
> I built the library with x32 support on my local machine and that
> works as expected
>
>> $ file .libs/test
>> .libs/test: ELF 32-bit LSB executable, x86-64, version 1 (SYSV),
> dynamically linked, interpreter /libx32/ld-linux-x32.so.2, for GNU/Linux
> 3.4.0, BuildID[sha1]=e747673ddc8a354679b2e0f97b12886a7c6273c2, not stripped
>> $ gcc -dumpversion
>> 5.4.0
>
>
> Can I somehow create this exact environment locally so I can try to
> reproduce?
>
> --
> Steffen Jaeckel - s_jaec...@gmx.de
> GnuPG fingerprint:  C438 6A23 7ED4 3A47 5541 B942 7B2C D0DD 4BCF F59B
> My OTR key has changed on 30. Sept. 2015!
> jabber: jaec...@jabber.ccc.de F052DE29 4FA9A02D 44A794E5 AE5AC0FB C5865C64



-- 
Best regards,
Michael

Bug#880245: ipython/jupyter issue [Was: RuntimeError: Kernel died before replying to kernel_info (#4116)]

[Andreas Tille]

Hi,

On Thu, Nov 09, 2017 at 08:48:02PM +0100, Gordon Ball wrote:
> 
> I just built statsmodels 0.8.0-6 in and amd64 sbuild chroot without
> encountering this issue.
> 
> Looking at the trace in #880245, it looks like the key error is
> 
> zmq.error.ZMQError: Address already in use
> 
> and the other
> 
> RuntimeError: Kernel died before replying to kernel_info
> 
> are just caused by the other process not being able to communicate. My
> guess is that this is an environment heisenbug - container network
> issues/socket exhaustion...

IMHO this would be a good reason to lower the severity of the bug, isn't
it?
 
> It might be possible to get `ExecutePreprocessor` in
> `tools/nbgenerate.py` to use IPC instead of TCP transport, which might
> be more reliable for this sort of use (although it probably doesn't get
> tested as much, so might have its own problems); this is a supported
> option when invoking some CLI tools (eg, `jupyter console --transport
> ipc --kernel python3`), but it's not obvious to me how to do it in this
> case.

Any further hits?

Kind regards

 Andreas. 

-- 
http://fam-tille.de