Bug#827343: siproxd: Plugins cannot be loaded

[Richard van den Berg]

Package: siproxd
Version: 1:0.8.1-4+b1
Severity: important

siproxd can't load it's plugins:

Jun 12 22:15:18 majoron siproxd[30035]: plugins.c:88 ERROR:plugin
plugin_logcall.so not found - skipped

This plugin is installed in /usr/lib/x86_64-linux-gnu/siproxd but siproxd
looks for it in /usr/lib/siproxd :

14822 open("/usr/lib/siproxd/plugin_logcall.so", O_RDONLY|O_CLOEXEC) = -1
ENOENT (No such file or directory)

I fixed this with:
ln -s /usr/lib/x86_64-linux-gnu/siproxd /usr/lib/

Now all is good:

Jun 15 09:00:09 majoron siproxd[14870]: plugins.c:112 INFO:Plugin
'plugin_logcall' [Logs calls to syslog] loaded with success, exemask=0x40

-- System Information:
Debian Release: 8.4
  APT prefers stable
  APT policy: (990, 'stable'), (400, 'testing'), (300, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (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
Init: systemd (via /run/systemd/system)

Versions of packages siproxd depends on:
ii  adduser  3.113+nmu3
ii  libc62.19-18+deb8u4
ii  libltdl7 2.4.2-1.11
ii  libosip2-11  4.1.0-2

siproxd recommends no packages.

siproxd suggests no packages.

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

-- no debconf information

Bug#827342: linux-image-4.5.0-2-amd64: luks rootfs not recognized at boot after upgrade to linux-image 4.5.5

[Sander van Grieken]

Package: src:linux
Version: 4.5.5-1
Severity: important

Upgrading linux kernel from 4.5.4 to 4.5.5 broke my boot.

I have a LUKS rootfs on top of a mdadm managed raid0. Starting from 4.5.5 it
doesn't recognize the luks volume at boot. The same happens with 4.6.1

The raid0 is not explicitly made with mdadm, it was previously handled by
dmraid I believe (fakeraid?)




-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: Sony Corporation
product_name: VPCZ21C5E
product_version: J004NLAK
chassis_vendor: Sony Corporation
chassis_version: N/A
bios_vendor: INSYDE
bios_version: R0170H5
board_vendor: Sony Corporation
board_name: VAIO
board_version: N/A

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core Processor 
Family DRAM Controller [8086:0104] (rev 09)
Subsystem: Sony Corporation 2nd Generation Core Processor Family DRAM 
Controller [104d:9084]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core 
Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 
00 [VGA controller])
Subsystem: Sony Corporation 2nd Generation Core Processor Family 
Integrated Graphics Controller [104d:9084]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR-  [disabled]
Capabilities: 
Kernel driver in use: i915
Kernel modules: i915

00:16.0 Communication controller [0780]: Intel Corporation 6 Series/C200 Series 
Chipset Family MEI Controller #1 [8086:1c3a] (rev 04)
Subsystem: Sony Corporation 6 Series/C200 Series Chipset Family MEI 
Controller [104d:9084]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: mei_me
Kernel modules: mei_me

00:1a.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset 
Family USB Enhanced Host Controller #2 [8086:1c2d] (rev 04) (prog-if 20 [EHCI])
Subsystem: Sony Corporation 6 Series/C200 Series Chipset Family USB 
Enhanced Host Controller [104d:9084]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: ehci-pci
Kernel modules: ehci_pci

00:1b.0 Audio device [0403]: Intel Corporation 6 Series/C200 Series Chipset 
Family High Definition Audio Controller [8086:1c20] (rev 04)
Subsystem: Sony Corporation 6 Series/C200 Series Chipset Family High 
Definition Audio Controller [104d:9084]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

00:1c.0 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset 
Family PCI Express Root Port 1 [8086:1c10] (rev b4) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport
Kernel modules: shpchp

00:1c.1 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset 
Family PCI Express Root Port 2 [8086:1c12] (rev b4) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport
Kernel modules: shpchp

00:1c.2 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset 
Family PCI Express Root Port 3 [8086:1c14] (rev b4) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport
Kernel modules: shpchp

00:1c.3 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset 
Family PCI Express Root Port 4 [8086:1c16] (rev b

Bug#797886: muon-notifier: no update notifications from icon in KDE system tray

[MAG4 Piemonte]

Hi, upgrading to version 4:5.6.4-1 Transitional package (muon-notifier -> 
plasma-discover-updater) solve the problem.
Regards!

Guido

Bug#827016: plasma-desktop: unable to install simultaneously kde-l10n-* and plasma-desktop-data

[MAG4 Piemonte]

Hi, we also confirm the same problem ...
Regards!

Guido

Bug#767905: kwallet: after upgrade from jessie to stretch kwalletmanager doesn't see my old wallets

[Martin Steigerwald]

On Montag, 13. Juni 2016 20:41:18 CEST Paul Gevers wrote:
> Package: kwalletmanager
> Version: 4:16.04.1-1
> Followup-For: Bug #767905
> Control: severity -1 serious
> 
> I just upgraded my system from jessie (with only jessie-backports as
> additional archive) to stretch and now, after reboot, my old wallets aren't
> available. Would be good if the new kwalletmanager would pick up my old
> wallets automatically.

As I upgraded a migrator was run, which migrated all KDE SC 4 wallets to the 
KF/Plasma 5 one. Yet, it can´t run completely without user interaction if you 
used master password(s) to encrypt your wallet with. So you need to enter your 
old master password(s).

I bet you can have it have another go at it by setting alreadyMigrated to 
false

martin@merkaba:~/.config> grep Migr kwalletrc
[Migration]
alreadyMigrated=true

and restarting KWallet. You may need to restart your Plasma session in order 
to do that, or restart the kwallet service manually (but I didn´t find it in 
background services kcm).

There might be another way to trigger the migration again by DBUS or what have 
you, but I didn´t find it easily.

[…]
-- 
Martin

Bug#827344: nmu: sogo_2.2.17a-1.1

[Mattia Rizzolo]

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

the binNMU there picked up libgnutls-deb0-28, so it needs another one.

nmu sogo_2.2.17a-1.1 . hurd-i386 . unstable . -m "Rebuild against libgnutls30"

-- 
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#827306: general: won't open file browser/manager if several other programs are already open

[Alberto Luaces]

Hi Luben,

Can you tell us which desktop environment are you using?
Can you run the file browser program from the console in order to see
any relevant error messages?

-- 
Alberto

Bug#827345: RM: aghermann [mips64el] -- RoQA; FTBFS; holds decruft

[Mattia Rizzolo]

package: ftp.debian.org

please remove this binary, I can't figure what's causing the FTBFS much
less fix it, and it's the only thing blocking old gnutls binaries in
mips64el.

-- 
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#825672: Issues with libacr38 and gpg

[Laurent Bigonville]

Hi,

Apparently you both have some issues with the last upload of libacr38 
and gpg.


I don't think that upstream is really maintaining this driver anymore, 
however it seems they are maintaining (and even in debian!) libacsccid1 
instead.


Could you please give a try to this other driver and see if it's working 
better for you?


If it's the case I'm thinking about asking to RM this package from the 
archive.


Regards,

Laurent Bigonville

Bug#827219: [pkg-go] Bug#827219: dh-golang: Built-Using calculation crashes on "golang-google-cloud"

[Dmitry Smirnov]

On Tuesday, 14 June 2016 4:19:59 PM AEST Michael Hudson-Doyle wrote:
> Oh, sorry, I see that the failure is when building something that
> depends on golang-google-cloud. I don't have time to test it now, but
> I have pushed a proposed fix to
> https://anonscm.debian.org/cgit/pkg-go/packages/dh-golang.git/log/?h=bug-82
> 7219. I'd be interested to hear if it helps!

It works better now but when I built docker.io/experimental "golang-google-
cloud" appeared twice in "misc:Built-Using" so I think it needs de-
duplication...

Thanks.

-- 
Best wishes,
 Dmitry Smirnov.

---

The choice for mankind lies between freedom and happiness and for the great
bulk of mankind, happiness is better.
-- George Orwell, 1984


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

Bug#816389: transition: php7.0

[Ondřej Surý]

Sure.

TL;DR

libkolab and libkolabxml needs to be resolved with KDE team.

Longer version:

The transition is almost complete, but there are few remaining packages
that are stuck because of swig, where upstream is dormant on the issue:
https://github.com/swig/swig/issues/571

Broken due swig are: redland-bindings, swig, *libkolab* and
*libkolabxml*.

redland-bindings should be easy - just remove php5-librdf as nothing
depends on it. I will do an NMU as  there was no maintainer activity
since 2014.

The rest of packages reported by dak -s testing:

- zeroc-ice - negotiated with upstream to take over the package; the
maintainers are MIA :(; the fixed upload has made it to unstable and
Chris needs to rebuild mumble on top of it.

- graphviz - fixed in unstable, Lazslo did update few days ago

- php-swiftmailer - fix uploaded few days ago

- galette - marked for autoremoval on 30 June (could be removed by hand
earlier)

- php-guzzle - seems fixed to me, but dak still wants to remove the
package

- php-json - needs to be removed together with php5

Cheers,
-- 
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
Knot Resolver (https://www.knot-resolver.cz/) – secure, privacy-aware,
fast DNS(SEC) resolver

On Tue, Jun 14, 2016, at 19:42, Emilio Pozuelo Monfort wrote:
> On 01/03/16 14:19, Ondřej Surý wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packages.debian.org
> > Usertags: transition
> > 
> > Hi,
> > 
> > this is a ben file for src:php5 to src:php7.0 transition.  I tried to
> > remove src:php5.6, src:php5.6-json and src:php7.0 from affected list
> > to only track packages that depend on main packages.
> 
> Can you give us a status update?
> 
> Emilio

Bug#816389: transition: php7.0

[Ondřej Surý]

Just re-checked libkolab* and it's same as with redland-binding, just
php-kolab and php-kolabxml binary packages needs to be removed and they
have no r-deps.

Cheers,
-- 
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
Knot Resolver (https://www.knot-resolver.cz/) – secure, privacy-aware,
fast DNS(SEC) resolver

On Wed, Jun 15, 2016, at 09:56, Ondřej Surý wrote:
> Sure.
> 
> TL;DR
> 
> libkolab and libkolabxml needs to be resolved with KDE team.
> 
> Longer version:
> 
> The transition is almost complete, but there are few remaining packages
> that are stuck because of swig, where upstream is dormant on the issue:
> https://github.com/swig/swig/issues/571
> 
> Broken due swig are: redland-bindings, swig, *libkolab* and
> *libkolabxml*.
> 
> redland-bindings should be easy - just remove php5-librdf as nothing
> depends on it. I will do an NMU as  there was no maintainer activity
> since 2014.
> 
> The rest of packages reported by dak -s testing:
> 
> - zeroc-ice - negotiated with upstream to take over the package; the
> maintainers are MIA :(; the fixed upload has made it to unstable and
> Chris needs to rebuild mumble on top of it.
> 
> - graphviz - fixed in unstable, Lazslo did update few days ago
> 
> - php-swiftmailer - fix uploaded few days ago
> 
> - galette - marked for autoremoval on 30 June (could be removed by hand
> earlier)
> 
> - php-guzzle - seems fixed to me, but dak still wants to remove the
> package
> 
> - php-json - needs to be removed together with php5
> 
> Cheers,
> -- 
> Ondřej Surý 
> Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
> Knot Resolver (https://www.knot-resolver.cz/) – secure, privacy-aware,
> fast DNS(SEC) resolver
> 
> On Tue, Jun 14, 2016, at 19:42, Emilio Pozuelo Monfort wrote:
> > On 01/03/16 14:19, Ondřej Surý wrote:
> > > Package: release.debian.org
> > > Severity: normal
> > > User: release.debian@packages.debian.org
> > > Usertags: transition
> > > 
> > > Hi,
> > > 
> > > this is a ben file for src:php5 to src:php7.0 transition.  I tried to
> > > remove src:php5.6, src:php5.6-json and src:php7.0 from affected list
> > > to only track packages that depend on main packages.
> > 
> > Can you give us a status update?
> > 
> > Emilio

Bug#827341: transition: octomap

[Emilio Pozuelo Monfort]

Control: tags -1 confirmed

On 15/06/16 08:50, Leopold Palomo-Avellaneda wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> 
> Dear Release Team,
> 
> I'm filing this bug for a transition of octomap. It is 
> in experimental. It builds on all architectures in testing, where it built 
> previously. 
> 
> 
> Ben file:
> 
> title = "octomap";
> is_affected = .depends ~ 
> /\b(libdynamicedt3d1\.8|liboctomap1\.8|liboctovis1\.8|libdynamicedt3d1\.6|libdynamicedt3d1\.6\-dbg|liboctomap1\.6v5|liboctomap1\.6v5\-dbg|liboctovis1\.6v5|liboctovis1\.6v5\-dbg)\b/
> is_good = .depends ~ /\b(libdynamicedt3d1\.8|liboctomap1\.8|liboctovis1\.8)\b/
> is_bad = .depends ~ 
> /\b(libdynamicedt3d1\.6|libdynamicedt3d1\.6\-dbg|liboctomap1\.6v5|liboctomap1\.6v5\-dbg|liboctovis1\.6v5|liboctovis1\.6v5\-dbg)\b/
> 
> All reverse dependencies test rebuilds. All rdepends are listed here:
> 
> https://release.debian.org/transitions/html/auto-octomap.html

Go ahead.

Emilio

Bug#814862: fix for qt4 Conflicts

[Ian Haywood]

Ok, I have patched the detection routine in Gambas so if both Qt4 and 
Qt5 are present then Qt5 is loaded.
This means the IDE will actually work (given qt4-webkit is gone, and the 
IDE needs webkit to display the online documentation), but the Conflicts 
isn't required anymore,


I have tested the build and checked the IDE runs.

Gianfranco, can you take a look at this in alioth git and upload the 
package if you are happy?


Thanks

Ian Haywood

Bug#790102: swig choke on -Wdate-time, makes packages FTBFS

[Ondřej Surý]

Control: severity -1 important

I don't think that severity serious is justifiable in swig directly.
While it would be nice if swig didn't choke on -Wdate-time, it's not
unreasonable for it to fail when unknown options are passed to it.

Cheers,
-- 
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
Knot Resolver (https://www.knot-resolver.cz/) – secure, privacy-aware,
fast DNS(SEC) resolver
Vše pro chleba (https://vseprochleba.cz) – Potřeby pro pečení chleba
všeho druhu

Bug#827323: linux: Regression v4.5 -> v4.6: system freeze after suspend/resume due to iAMT watchdog

[Usyskin, Alexander]

Hi

I assume that "This happened with 4.6, but not with v4.5.", yes?

Do you have vPro system? Have you provisioned your ME device?
If not, the iAMT watchdog should not be exposed to user-space and should not 
affect systemd.
Do you have /dev/watchdog* with identity "iamt_wdt" at you system?

Thanks
--
Sasha


-Original Message-
From: Sebastian Reichel [mailto:s...@debian.org] 
Sent: Wednesday, June 15, 2016 02:44
To: Debian Bug Tracking System 
Subject: Bug#827323: linux: Regression v4.5 -> v4.6: system freeze after 
suspend/resume due to iAMT watchdog

Source: linux
Version: 4.5.5-1
Severity: normal

Hi,

My Lenovo Thinkpad X250 freezes a couple of seconds after resuming from 
suspend. This happened with 4.5, but not with v4.6. I bisected the problem 
using mainline kernel with Debian config to the following commit:

sre@earth ~/src/linux (git)-[fdd9b86...|bisect] % git bisect bad 
fdd9b8655933c3eb3154fe1ed351c17b654258bd is the first bad commit commit 
fdd9b8655933c3eb3154fe1ed351c17b654258bd
Author: Alexander Usyskin 
Date:   Fri Jan 8 00:49:21 2016 +0200

mei: wd: drop the watchdog code from the core mei driver

Instead of integrating the iAMT watchdog in the mei core driver
we will create a watchdog device on the mei client bus and
create a driver for it.

This patch removes the watchdog code from the mei core driver.

Signed-off-by: Alexander Usyskin 
Signed-off-by: Tomas Winkler 
Signed-off-by: Greg Kroah-Hartman 

My system was configured to use the watchdog via "RuntimeWatchdogSec=30"
in "/etc/systemd/system.conf". After disabling the feature no system freeze 
happens after suspend/resume cycle.

-- Sebastian

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

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

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

Bug#787241: xserver-xorg-video-intel: VT never returns from powersave on Haswell

[Tim Small]

Package: xserver-xorg-video-intel
Followup-For: Bug #787241

Could you try:

. Switch to VT
. Log in as same use as X session on VT
. run 'sleep 6 ; DISPLAY=:0 xrandr' on VT
. switch to X VT before 6 seconds have elapsed, then switch back after 6
seconds have elapsed
. Check output to see what mode your display is reporting
. Possibly fix with 'xrandr --display FOO --auto'

?

Bug#827348: qtscript-opensource-src FTBFS on Alpha; double value incorrect in last bit in test suite

[Michael Cree]

Source: qtscript-opensource-src
Version: 5.6.1+dfsg-2
Severity: important
Justification: fails to build from source but built in past
Tags: patch
User: debian-al...@lists.debian.org
Usertags: alpha

qtscript-opensource-src FTBFS on Alpha due to a test suite failure [1]:

FAIL!  : tst_QScriptJsTestSuite::ecma_2/RegExp(/\B/.lastIndex) Compared values 
are not the same
   Actual   (actual): "1.7976931348623155e+308"
   Expected (expect): "1.7976931348623157e+308"
   Loc: [ecma_2/RegExp/properties-002.js(583)]

This is the result of a double precision calculation that has rounded
the last bit of the calculation in the wrong direction.  That does not
seem sufficient reason to completely fail the build so I attach a
patch that disables this test and hope you would consider including
it in the next upload of qtscript-opensource-src.

Cheers
Michael.

[1] 
https://buildd.debian.org/status/fetch.php?pkg=qtscript-opensource-src&arch=alpha&ver=5.6.1%2Bdfsg-2&stamp=1465838369
Index: qtscript-opensource-src-5.6.1+dfsg/tests/auto/qscriptjstestsuite/skip.txt
===
--- qtscript-opensource-src-5.6.1+dfsg.orig/tests/auto/qscriptjstestsuite/skip.txt
+++ qtscript-opensource-src-5.6.1+dfsg/tests/auto/qscriptjstestsuite/skip.txt
@@ -7,6 +7,7 @@ regress-322135-03.js | takes forever
 regress-322135-04.js | takes forever
 ecma/Expressions/11.4.7-02.js | Fails on some architectures
 ecma/TypeConversion/9.3.1-3.js | Fails on some architectures
+ecma_2/RegExp/properties-002.js | Fails on Alpha
 ecma_3/Array/regress-387501.js | Produces wrong error message
 ecma_3/RegExp/regress-375715-04.js | bug
 ecma_3/RegExp/regress-289669.js | Can fail due to relying on wall-clock time

Bug#827346: install-sh: insecure use of /tmp

[Petter Reinholdtsen]

Control: found -1 1:1.11.6-1

[Alex Vong]
> A patch fixing the bug authored by Pavel Raiskup is available
> from Red Hat Bugzilla. The patch has been forwarded to upstream,
> but it has not been merged yet.

I checked, and this bug existed as early as Wheezy in the automake1.11 package.
It still exist in Jessie and Sid.
-- 
Happy hacking
Petter Reinholdtsen

Bug#816389: PHP 7.0 transition - PHP bindings removed and uploaded to DELAYED/2

[Ondřej Surý]

Dear maintainers,

in an effort to finally finish PHP 7.0 transition started in April, I
removed PHP bindings from swig as it doesn't look like swig will support
PHP 7.0 anytime soon and also from the remaining packages using swig to
build PHP bindings.

I uploaded these fixed packages to DELAYED/2 parallel to writing this
email.

Please let me know if you intend to proceed differently, so we can
coordinate the upload and finish the transition in timely manner.

Cheers,
-- 
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
Knot Resolver (https://www.knot-resolver.cz/) – secure, privacy-aware,
fast DNS(SEC) resolver
Vše pro chleba (https://vseprochleba.cz) – Potřeby pro pečení chleba
všeho druhu

Bug#827219: [pkg-go] Bug#827219: Bug#827219: dh-golang: Built-Using calculation crashes on "golang-google-cloud"

[Michael Hudson-Doyle]

On 15 June 2016 at 17:40, Dmitry Smirnov  wrote:
> On Wednesday, 15 June 2016 9:55:34 AM AEST Michael Hudson-Doyle wrote:
>> Where can I get docker.io_1.11.1~ds1.orig.tar.{bz2,gz,lzma,xz} ?
>
> ?? Is something wrong with "uscan"?
>
> You should be able to generate tarball by something like:
>
> uscan --destdir=. --compression xz --repack --download-current-version

Just unfamiliarity! Thanks for the tip.

Bug#827347: install-sh: insecure use of /tmp

[Petter Reinholdtsen]

Control: found -1 1:1.14.1-4

[Alex Vong]
> A patch fixing the bug authored by Pavel Raiskup is available
> from Red Hat Bugzilla. The patch has been forwarded to upstream,
> but it has not been merged yet.

I checked, and this problem still exist in automake-1.14 in Jessie.
-- 
Happy hacking
Petter Reinholdtsen

Bug#827219: [pkg-go] Bug#827219: Bug#827219: dh-golang: Built-Using calculation crashes on "golang-google-cloud"

[Michael Hudson-Doyle]

On 15 June 2016 at 19:57, Dmitry Smirnov  wrote:
> On Tuesday, 14 June 2016 4:19:59 PM AEST Michael Hudson-Doyle wrote:
>> Oh, sorry, I see that the failure is when building something that
>> depends on golang-google-cloud. I don't have time to test it now, but
>> I have pushed a proposed fix to
>> https://anonscm.debian.org/cgit/pkg-go/packages/dh-golang.git/log/?h=bug-82
>> 7219. I'd be interested to hear if it helps!
>
> It works better now but when I built docker.io/experimental "golang-google-
> cloud" appeared twice in "misc:Built-Using" so I think it needs de-
> duplication...

Ah, good point. Fix for that push to the bug-827219 branch, tested
with docker with reasonable-seeming results. Merge to master and
upload if it looks good to you?

Cheers,
mwh

Bug#827349: viva: FTBFS: Parse error at "BOOST_JOIN"

[Emilio Pozuelo Monfort]

Package: viva
Version: 1.1+git20150820.1a3d1f680f-1
Severity: serious

Your package failed to build everywhere:

[ 60%] Generating src/vv_treemap/moc_VTApplication.cxx
cd 
/«BUILDDIR»/viva-1.1+git20150820.1a3d1f680f/obj-x86_64-linux-gnu/src/vv_treemap 
&& /usr/lib/x86_64-linux-gnu/qt4/bin/moc 
@/«BUILDDIR»/viva-1.1+git20150820.1a3d1f680f/obj-x86_64-linux-gnu/src/vv_treemap/moc_VTApplication.cxx_parameters
usr/include/boost/type_traits/detail/has_binary_operator.hp:50: Parse error at 
"BOOST_JOIN"
CMakeFiles/vv_treemap.dir/build.make:65: recipe for target 
'src/vv_treemap/moc_VTApplication.cxx' failed
make[3]: *** [src/vv_treemap/moc_VTApplication.cxx] Error 1

Logs at https://buildd.debian.org/status/package.php?p=viva

Emilio

Bug#826968: mercurial-buildpackage rebuild issue

[Emilio Pozuelo Monfort]

On Fri, 10 Jun 2016 17:56:13 + (UTC) Gianfranco Costamagna
 wrote:
> source: mercurial-buildpackage
> severity: serious
> version: 0.10-1
> tags: patch
> 
> Hi Darren,
> I had to patch the package on Ubuntu, because you have a parsechangelog that 
> doesn't take care of rebuilds, NMUs, or whatever.
> 
> In Ubuntu it seems fine now, the following patch
> diff -Nru mercurial-buildpackage-0.10.1/debian/changelog 
> mercurial-buildpackage-0.10.1ubuntu1/debian/changelog
> --- mercurial-buildpackage-0.10.1/debian/changelog  2014-10-28 
> 03:27:29.0 +0100
> +++ mercurial-buildpackage-0.10.1ubuntu1/debian/changelog   2016-06-10 
> 19:43:53.0 +0200
> @@ -1,3 +1,10 @@
> +mercurial-buildpackage (0.10.1ubuntu1) yakkety; urgency=medium
> +
> +  * Rebuild against libneko2.
> +  * Strip the "build*" and "ubuntu*" from changelog
> +
> + -- Gianfranco Costamagna   Tue, 07 Jun 2016 
> 16:23:35 +0200
> +
> mercurial-buildpackage (0.10.1) unstable; urgency=low
> 
> * Fix ‘class not found’ FTBFS. (Closes: #719405)
> diff -Nru mercurial-buildpackage-0.10.1/debian/rules 
> mercurial-buildpackage-0.10.1ubuntu1/debian/rules
> --- mercurial-buildpackage-0.10.1/debian/rules  2012-02-25 20:10:58.0 
> +0100
> +++ mercurial-buildpackage-0.10.1ubuntu1/debian/rules   2016-06-07 
> 20:11:01.0 +0200
> @@ -2,7 +2,7 @@
> # debian/rules for mercurial-buildpackage.
> 
> PACKAGE := $(shell dpkg-parsechangelog | head -1 | cut -c9-)
> -CHANGELOG := $(shell dpkg-parsechangelog | sed -e '/^Version: /! d; s/^.* 
> //')
> +CHANGELOG := $(shell dpkg-parsechangelog | sed -e '/^Version: /! d; s/^.* 
> //' | sed '-e s/build.*//' | sed '-e s/ubuntu.*//')
> 
> clean:
> dh_testdir
> 
> 
> 
> of course something more appropriate is needed, but this should become 
> shortly an RC bug in Debian too.
> 
> Can you please give it a look?
> 
> the failure is:
> 
> ./macro-expand < MercurialImportDsc.man > mercurial-importdsc.1
> ./macro-expand < MercurialPristineTar.man > mercurial-pristinetar.1
> ./macro-expand < MercurialPort.man > mercurial-port.1
> make[1]: Leaving directory '/«PKGBUILDDIR»'
> touch build-stamp
> [ "0.10.1build1" = 0.10.1 ]
> debian/rules:22: recipe for target 'build-arch' failed
> make: *** [build-arch] Error 1
> dpkg-buildpackage: error: debian/rules build gave error exit status 2

This broke in Debian because of binNMUs:

[ "0.10.1+b1" = 0.10.1 ]
debian/rules:22: recipe for target 'build-arch' failed

What is that check needed for anyway?

Emilio

Bug#827219: [pkg-go] Bug#827219: Bug#827219: dh-golang: Built-Using calculation crashes on "golang-google-cloud"

[Dmitry Smirnov]

On Wednesday, 15 June 2016 8:26:43 PM AEST Michael Hudson-Doyle wrote:
> Ah, good point. Fix for that push to the bug-827219 branch, tested
> with docker with reasonable-seeming results. Merge to master and
> upload if it looks good to you?

Yes, let's upload please. Unfortunately I don't have time to review code or 
do more extensive testing now... However providing that you respond to bugs 
so promptly I'm confident that you will rapidly fix whatever regressions is 
introduced (if any).  :))

Thank you.

-- 
Cheers,
 Dmitry Smirnov.

---

In questions of science, the authority of a thousand is not worth the
humble reasoning of a single individual.
-- Galileo Galilei


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

Bug#827219: [pkg-go] Bug#827219: Bug#827219: dh-golang: Built-Using calculation crashes on "golang-google-cloud"

[Michael Hudson-Doyle]

On 15 June 2016 at 20:36, Dmitry Smirnov  wrote:
> On Wednesday, 15 June 2016 8:26:43 PM AEST Michael Hudson-Doyle wrote:
>> Ah, good point. Fix for that push to the bug-827219 branch, tested
>> with docker with reasonable-seeming results. Merge to master and
>> upload if it looks good to you?
>
> Yes, let's upload please. Unfortunately I don't have time to review code or
> do more extensive testing now... However providing that you respond to bugs
> so promptly I'm confident that you will rapidly fix whatever regressions is
> introduced (if any).  :))

OK, I've pushed to master, but I can't upload (my Debian Maintainer
application is stuck in the usual Debian limbo).

Cheers,
mwh

Bug#827350: kupfer: Please recommend gnome-icon-theme

[Itaï BEN YAACOV]

Package: kupfer
Version: 0+v208-6.2
Severity: minor

Dear Maintainer,

With various recent changes in icon package dependencies,
nothing on my system depends on, or even recommends,
gnome-icon-theme.
With this package out, kupfer is missing some action icons, so it
should recommend it, if not even depend on it (or on a group of
packages providing equivalent icons).

Cheers,
Itaï.



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

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

Versions of packages kupfer depends on:
ii  dbus  1.10.8-1
ii  python-dbus   1.2.4-1
ii  python-gobject3.20.1-1
ii  python-gtk2   2.24.0-4
ii  python-keybinder  0.3.1-1
ii  python-xdg0.25-4
pn  python:any

Versions of packages kupfer recommends:
pn  python-keyring  
ii  python-wnck 2.32.0+dfsg-3

Versions of packages kupfer suggests:
pn  python-cjson 
pn  python-gdata 
pn  python-qrencode  

-- no debconf information

Bug#827351: gnuplot-qt: x window resizing is broken

[Jörg-Volker Peetz]

Package: gnuplot-qt
Version: 5.0.3+dfsg3-5
Severity: normal

Dear Maintainer(s),

trying to resize a gnuplot x window terminates the program.

Using as example a file "gpex.dat" with content

#
set xdata time
set timefmt "%d.%m.%Y"
set format x"%d.%m.%Y"
plot '-' using 1:2 with lines ; pause -1 "Hit return to continue"
#
15.01.2011  1507
15.02.2011  1786
15.03.2011  2036
15.04.2011  2278
16.05.2011  2520
#

and commanding

$ gnuplot gpex.dat

opens a new window. With version 4, this window could be resized but now,
trying to do that terminates gnuplot.

Regards,
jvp.


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (600, 'testing'), (500, 'unstable'), (5, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.6.2 (SMP w/2 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages gnuplot-qt depends on:
ii  gnuplot-data 5.0.3+dfsg3-5
ii  libc62.22-9
ii  libcairo21.14.6-1+b1
ii  libedit2 3.1-20150325-1+b1
ii  libgcc1  1:6.1.1-6
ii  libgd3   2.2.1-1
ii  libglib2.0-0 2.48.1-1
ii  liblua5.1-0  5.1.5-8
ii  libpango-1.0-0   1.40.1-1
ii  libpangocairo-1.0-0  1.40.1-1
ii  libqt5core5a 5.6.1+dfsg-2
ii  libqt5gui5   5.6.1+dfsg-2
ii  libqt5network5   5.6.1+dfsg-2
ii  libqt5printsupport5  5.6.1+dfsg-2
ii  libqt5svg5   5.6.1-2
ii  libqt5widgets5   5.6.1+dfsg-2
ii  libstdc++6   6.1.1-6
ii  libwxbase3.0-0v5 3.0.2+dfsg-1.4
ii  libwxgtk3.0-0v5  3.0.2+dfsg-1.4
ii  libx11-6 2:1.6.3-1

gnuplot-qt recommends no packages.

Versions of packages gnuplot-qt suggests:
ii  gnuplot-doc  5.0.3+dfsg3-5

-- no debconf information

Bug#790102: swig choke on -Wdate-time, makes packages FTBFS

[Mattia Rizzolo]

On Wed, Jun 15, 2016 at 10:12:06AM +0200, Ondřej Surý wrote:
> Control: severity -1 important
> 
> I don't think that severity serious is justifiable in swig directly.
> While it would be nice if swig didn't choke on -Wdate-time, it's not
> unreasonable for it to fail when unknown options are passed to it.

yes.
The reason I rised to serious back in time was because it was causing
other packages to FTBFS.  Since then those packages implemented
workaround/fixes (depends on how you want to look at them).

-- 
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#827219: [pkg-go] Bug#827219: Bug#827219: Bug#827219: dh-golang: Built-Using calculation crashes on "golang-google-cloud"

[Dmitry Smirnov]

On Wednesday, 15 June 2016 8:42:51 PM AEST Michael Hudson-Doyle wrote:
> OK, I've pushed to master, but I can't upload (my Debian Maintainer
> application is stuck in the usual Debian limbo).

No worries, I'll upload for you. Thank you for your help.

-- 
Regards,
 Dmitry Smirnov.

---

It is no use saying, 'We are doing our best.' You have got to succeed
in doing what is necessary.
-- Winston Churchill


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

Bug#790102: swig choke on -Wdate-time, makes packages FTBFS

[Ondřej Surý]

On Wed, Jun 15, 2016, at 10:59, Mattia Rizzolo wrote:
> On Wed, Jun 15, 2016 at 10:12:06AM +0200, Ondřej Surý wrote:
> > Control: severity -1 important
> > 
> > I don't think that severity serious is justifiable in swig directly.
> > While it would be nice if swig didn't choke on -Wdate-time, it's not
> > unreasonable for it to fail when unknown options are passed to it.
> 
> yes.
> The reason I rised to serious back in time was because it was causing
> other packages to FTBFS.  Since then those packages implemented
> workaround/fixes (depends on how you want to look at them).

Cool, I need to push fix for PHP 7.0 transition (in DELAYED/2) and this
would block the transition.

Cheers,
-- 
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
Knot Resolver (https://www.knot-resolver.cz/) – secure, privacy-aware,
fast DNS(SEC) resolver
Vše pro chleba (https://vseprochleba.cz) – Potřeby pro pečení chleba
všeho druhu

Bug#827353: elpa-pdf-tools: epdfinfo wrong path at install

[Grégory Mounié]

Package: elpa-pdf-tools
Version: 0.70-1
Severity: important

Dear Maintainer,

When using (pdf-tools-install) in the .emacs, the function try, and 
failed, to

build the server (epdfinfo ?)

After customizing the epdfinfo path to /usr/bin/epdfinfo, the package work
flawlessly.

Thanks a lot for providing this wonderful package



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

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

Versions of packages elpa-pdf-tools depends on:
ii  elpa-let-alist 1.0.4-1
ii  elpa-pdf-tools-server  0.70-1
ii  elpa-tablist   0.70-1
ii  emacs  46.1
ii  emacsen-common 2.0.8

elpa-pdf-tools recommends no packages.

elpa-pdf-tools suggests no packages.

-- debconf-show failed

Bug#827352: jessie-pu: package automake-1.14/1.14.1-4+deb8u1

[Petter Reinholdtsen]

Package: release.debian.org
Severity: normal
Tags: jessie
User: release.debian@packages.debian.org
Usertags: pu

On my Debian Jessie machine, I would like to fix a security problem with
automake-1.14 that show up the debsecan report, see
https://security-tracker.debian.org/tracker/source-package/automake-1.14 
>.
The issue never got a CVE (no reply to the request), so I point to the
source package entry instead of the some times changing TEMP reference.

The issue is fixed in automake-1.15, but not in automake-1.14 that is in
stable but removed from unstable.

The issue is unsafe use of /tmp/.  The patch is similar to the code in
version 1.15.

OK to upload?

-- 
Happy hacking
Petter Reinholdtsen
diff -Nru automake-1.14-1.14.1/debian/changelog automake-1.14-1.14.1/debian/changelog
--- automake-1.14-1.14.1/debian/changelog	2014-10-27 02:52:07.0 +
+++ automake-1.14-1.14.1/debian/changelog	2016-06-15 08:56:21.0 +
@@ -1,3 +1,11 @@
+automake-1.14 (1:1.14.1-4+deb8u1) unstable; urgency=medium
+
+  * Non-maintainer upload to fix security issue.
+  * Avoid insecure use of /tmp/ in install-sh (Closes: #827347).
+Based on patch from RedHat and Pavel Raiskup.
+
+ -- Petter Reinholdtsen   Wed, 15 Jun 2016 10:56:14 +0200
+
 automake-1.14 (1:1.14.1-4) unstable; urgency=medium
 
   * debian/patches/03-ensure-ac_aux_dir-set.diff: Add patch to ensure
diff -Nru automake-1.14-1.14.1/debian/patches/CVE-bug-827347.diff automake-1.14-1.14.1/debian/patches/CVE-bug-827347.diff
--- automake-1.14-1.14.1/debian/patches/CVE-bug-827347.diff	1970-01-01 00:00:00.0 +
+++ automake-1.14-1.14.1/debian/patches/CVE-bug-827347.diff	2016-06-15 08:55:04.0 +
@@ -0,0 +1,60 @@
+Fix security problem.  The patch is based on fix found in
+ https://bugzilla.redhat.com/show_bug.cgi?id=1140725 > and
+ verified to be identical to the code in automake 1.15.
+From: Petter Reinholdtsen 
+Last-Update: 2016-06-15
+Debian-Bug: https://bugs.debian.org/827347
+
+Index: automake-1.14-1.14.1/lib/install-sh
+===
+--- automake-1.14-1.14.1.orig/lib/install-sh	2016-06-15 10:44:49.0 +0200
 automake-1.14-1.14.1/lib/install-sh	2016-06-15 10:48:18.924178517 +0200
+@@ -345,34 +345,41 @@
+ 	# is incompatible with FreeBSD 'install' when (umask & 300) != 0.
+ 	;;
+ 	  *)
++# $RANDOM is not portable (e.g. dash);  use it when possible to
++# lower collision chance
+ 	tmpdir=${TMPDIR-/tmp}/ins$RANDOM-$$
+-	trap 'ret=$?; rmdir "$tmpdir/d" "$tmpdir" 2>/dev/null; exit $ret' 0
++	trap 'ret=$?; rmdir "$tmpdir/a/b" "$tmpdir/a" "$tmpdir" 2>/dev/null; exit $ret' 0
+ 
++	 # As "mkdir -p" follows symlinks and we work in /tmp possibly;  so
++	 # create the $tmpdir first (and fail if unsuccessful) to make sure
++	 # that nobody tries to guess the $tmpdir name.
+ 	if (umask $mkdir_umask &&
+-		exec $mkdirprog $mkdir_mode -p -- "$tmpdir/d") >/dev/null 2>&1
++		$mkdirprog $mkdir_mode "$tmpdir" &&
++		exec $mkdirprog $mkdir_mode -p -- "$tmpdir/a/b") >/dev/null 2>&1
+ 	then
+ 	  if test -z "$dir_arg" || {
+ 		   # Check for POSIX incompatibilities with -m.
+ 		   # HP-UX 11.23 and IRIX 6.5 mkdir -m -p sets group- or
+ 		   # other-writable bit of parent directory when it shouldn't.
+ 		   # FreeBSD 6.1 mkdir -m -p sets mode of existing directory.
+-		   ls_ld_tmpdir=`ls -ld "$tmpdir"`
++		   test_tmpdir="$tmpdir/a"
++		   ls_ld_tmpdir=`ls -ld "$test_tmpdir"`
+ 		   case $ls_ld_tmpdir in
+ 		 d-?r-*) different_mode=700;;
+ 		 d-?--*) different_mode=755;;
+ 		 *) false;;
+ 		   esac &&
+-		   $mkdirprog -m$different_mode -p -- "$tmpdir" && {
+-		 ls_ld_tmpdir_1=`ls -ld "$tmpdir"`
++		   $mkdirprog -m$different_mode -p -- "$test_tmpdir" && {
++		 ls_ld_tmpdir_1=`ls -ld "$test_tmpdir"`
+ 		 test "$ls_ld_tmpdir" = "$ls_ld_tmpdir_1"
+ 		   }
+ 		 }
+ 	  then posix_mkdir=:
+ 	  fi
+-	  rmdir "$tmpdir/d" "$tmpdir"
++	  rmdir "$tmpdir/a/b" "$tmpdir/a" "$tmpdir"
+ 	else
+ 	  # Remove any dirs left behind by ancient mkdir implementations.
+-	  rmdir ./$mkdir_mode ./-p ./-- 2>/dev/null
++	  rmdir ./$mkdir_mode ./-p ./-- "$tmpdir" 2>/dev/null
+ 	fi
+ 	trap '' 0;;
+ 	esac;;
diff -Nru automake-1.14-1.14.1/debian/patches/series automake-1.14-1.14.1/debian/patches/series
--- automake-1.14-1.14.1/debian/patches/series	2014-10-27 02:52:07.0 +
+++ automake-1.14-1.14.1/debian/patches/series	2016-06-15 08:51:33.0 +
@@ -1,3 +1,4 @@
 01-texi-rename.diff
 02-init-m4-newline.diff
 03-ensure-ac_aux_dir-set.diff
+CVE-bug-827347.diff

Bug#827224: targetcli: On upgrade "Value of wwn attribute is not set for"

[Tim Small]

On 14/06/16 16:08, Ritesh Raj Sarraf wrote:
> Control: tag -1 moreinfo
>
> Hello Tim,
>
> We never had a version released for Debian Jessie. There were just too
many
> issues back then. For Stretch, I hope we have the current ones in the
> repository.
>
> Assuming you have interest in LIO, I'd suggest you try out the latest
versions
> that are targeted for Debian Stretch. I just pushed some fixes
yesterday, so
> either you pick them from Unstable, or wait around a week, and
hopefully it'll
> migrate to Debian Testing by then.

Yes, you're right sorry, I must have installed a package from testing
manually soon after the Jessie release.

Anyhow, this upgrade:

Unpacking targetcli (1:3.0~pre4.1~ga55d018-2) over (3.0+git0.7e32595e-2)

broke with the wwn error detailed as above, but I suppose this could
have been because of the recently closed rtslib bug, which would have
prevented the running config from being saved by the new targetcli version?

Tim.


-- 
South East Open Source Solutions Limited
Registered in England and Wales with company number 06134732.
Registered Office: 2 Powell Gardens, Redhill, Surrey, RH1 1TQ
VAT number: 900 6633 53  http://seoss.co.uk/ +44-(0)1273-808309



signature.asc
Description: OpenPGP digital signature

Bug#827266: Sources for python-setuptools include a debian/changelog.dch file

[Matthias Klose]

On 14.06.2016 14:45, Thomas Goirand wrote:
> Package: python-setuptools
> Version: 18.8-1~bpo8+1
> Severity: important
> 
> Hi Matthias,
> 
> After extracting python-setuptools_20.10.1-1.dsc, I get a debian/changelog.dch
> file, which is breaking my automated backport script (which is using dch 
> --bpo).
> Please remove that file and re-upload.

Please ask the uploader of this package.

Matthias

Bug#827354: ITP: splat-vo -- Spectral Analysis Tool for Virtual Observatory

[Paul Sladen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: wnpp
Owner: Paul Sladen 
Severity: Wishlist

* Package Name: splat-vo
* Version:  3.11-3
* Upstream Author:  Margarida Castro Neves; Petr Skoda
* URL:  http://www.g-vo.org/pmwiki/About/SPLAT
* Programming Language: Java
* License:  GPL-2+
* Description:  Spectral Analysis Tool for Virtual Observatory

Aladin is an desktop client for viewing and analysis of Virtual
Observatory (VO) spectral data.  This graphical tool can display,
analyse, compare and modify already extracted spectra stored in FITS,
TEXT, and NDF/NDX formats.  It can also interact with the Virtual
Observatory registery and data-centres to dynamically query and
download data for a particular section of the sky on-demand.

Splat-VO can work in multiple coordinate systems and can plot and
overlay multiple spectra at the same time.  Plots are displayed in a
visually rich format.  Analysis can be performed by selecting and
zooming multiple, and fitting to emission and absorption lines.

An example tutorial can be found at:

  http://www.euro-vo.org/sites/default/files/documents/GAVO_splat-tutorial.pdf

As of 2016 upstream work is in the 'Splat-VO/Starjava' branch at:

  https://github.com/SPLAT-VO/starjava/tree/splatmaster/splat

In the top-level of this repository also contains the rest of
dependencies, collectly known as 'Starjava', after the collaboration
project which created them.  The Starjava master repo is at:

  https://github.com/Starlink/starjava

There are a large number of dependencies on libraries contained in
the rest of Starjava, and these will need packaging first.  Splat also
contains some JNI native code optimisation functions, with
pure-Java fallback implementations.

Licensing information is found in 'SPLAT_CONDITIONS' and 'COPYING':

  
https://github.com/SPLAT-VO/starjava/blob/splatmaster/splat/src/docs/SPLAT_CONDITIONS

And states that it is GPL-2+:

 1. The Software is owned by the Council for the Central Laboratory
 of the Research Councils ("CCLRC").
 .
 2. This program is free software; you can redistribute it and/or
 modify it under the terms of the GNU General Public License as
 published by the Free Software Foundation; either version 2 of the
 License, or (at your option) any later version.
 .
 The GNU General Public License text is included in the file COPYING
 which should be found in the same directory as this file.

There are several copyrights given, in the documentation at:

  http://star-www.dur.ac.uk/~pdraper/splat/sun243.htx/node50.html

This is given as at least:

 Copyright (C) 2001-2005 Council for the Central Laboratory of the Research 
Councils
 Copyright (C) 2006-2007 Particle Physics and Astronomy Research Council
 Copyright (C) 2007-2009 Science and Technology Facilities Council
 Copyright (C) 2010-2013 Peter W. Draper
 Copyright (C) 2013 German Astrophysical Virtual Observatory (GAVO)

Upstream-Name: SPLAT-VO
Upstream-Author: Margarida Castro Neves 
Source: https://github.com/SPLAT-VO/starjava/tree/splatmaster/splat

Section: science
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iD8DBQFXYRrcc444tukM+iQRAvPAAJ9JD9JkIalfueKCV01vtyjkqdQzRQCgpATQ
XgiFQKO3H2KKDWG8E7o1+68=
=ubil
-END PGP SIGNATURE-

Bug#827219: [pkg-go] Bug#827219: Bug#827219: Bug#827219: dh-golang: Built-Using calculation crashes on "golang-google-cloud"

[Martín Ferrari]

On 15/06/16 09:36, Dmitry Smirnov wrote:

> Yes, let's upload please. Unfortunately I don't have time to review code or 
> do more extensive testing now... However providing that you respond to bugs 
> so promptly I'm confident that you will rapidly fix whatever regressions is 
> introduced (if any).  :))

Actually, please don't.

All of the team's work depends on dh-golang, so uploading without proper
testing is definitely *not ok*.

-- 
Martín Ferrari (Tincho)

Bug#827355: RFS: burp/1.4.40-1 [QA] -- Simple cross-platform network BackUp and Restore Program

[Sean Whitton]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a QA upload of burp.

* Package name: burp
  Version : 1.4.40-1
  Upstream Author : Graham Keeling 
* URL : http://burp.grke.net/
* License : AGPL-3
  Section : utils

Changes since the last upload:

  * QA upload.
  * Set maintainer to QA team.
  * Package new upstream release (Closes: #774715).
Upstream identifies version 1.4.40 as their "stable" release.
  * Apply patch from Svante Signell to fix build on the GNU Hurd
(Closes: #675761, #747672).
  * Add Recommends: openssl (Closes: #745376).
  * Repair d/copyright:
- Move 'Files: *' paragraph to the top of the file
- Move src/win32/compat/getopt.c and src/win32/compat/sys/mtio.h
  paragraphs to end of file
- Add myself to paragraph for debian/ subdir
- Correct invalid shortname agplv3 -> AGPL-3
- Factor out AGPL-3 license to a License: paragraph.
- Correct invalid shortname Troy D. Hanson License -> custom1
- Correct copyright years for src/win32/compat/sys/mtio.h
- Correct some indentation and trailing whitespace
  * Replace burp-dbg with automatically generated burp-dbgsym.
- Drop obsolete rules target override_dh_strip.
- Drop obsolete burp.install.
- Drop obsolete burp.dirs.
- Drop obsolete burp-dbg.maintscript.
  * Drop endian.patch.
Merged upstream.
  * Drop wait_for_backup_to_finish.patch.
Merged upstream.
  * Refresh a patch.
  * Bump standards version to 3.9.8 (no changes required).
  * Update Vcs-* URIs.
  * Add gbp.conf.

Download with dget:

dget -x http://mentors.debian.net/debian/pool/main/b/burp/burp_1.4.40-1.dsc

Or build it with gbp:

gbp clone --pristine-tar --debian-branch=debian 
https://git.spwhitton.name/burp
cd burp
git checkout debian/1.4.40-1
git verify-tag debian/1.4.40-1 # if you have my key
gbp buildpackage

Notes:

1. I am using a branch called 'debian' because the master branch in the
   collab-maint repo seems to be used for experimental, not sid.  I
   added a gbp.conf so everything should work in the expected way.

2. I have an application for collab-maint pending.  When it goes through
   I intend to push my work there; the above git clone URI is temporary.

3. Successful sbuild: 
http://debomatic-i386.debian.net/distribution#unstable/burp/1.4.40-1/buildlog

Thanks.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#827356: faulthandler: please package new upstream release, 2.4

[Sandro Tosi]

Source: faulthandler
Severity: wishlist

Hello,
2.4 has been released back in May, please update this package to it (or any
later release at the time of the update).

Regards,
Sandro

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

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

Bug#827219: [pkg-go] Bug#827219: Bug#827219: Bug#827219: dh-golang: Built-Using calculation crashes on "golang-google-cloud"

[Dmitry Smirnov]

On Wednesday, 15 June 2016 10:37:57 AM AEST Martín Ferrari wrote:
> Actually, please don't.
> 
> All of the team's work depends on dh-golang, so uploading without proper
> testing is definitely *not ok*.

Martin, I don't need to be reminded how painful it is to have dh-golang 
broken -- last time when it was unusable I fell a week behind my schedule 
because I could not upload...

I did some testing and I believe changes are good enough for upload.
I already uploaded short time ago.
I appreciate your concerns. if anything goes wrong please let us know and 
we'll address the problem, if any.

-- 
Cheers,
 Dmitry Smirnov.

---

If forty million people say a foolish thing it does not become a wise one.
-- W. Somerset Maugham, 1901


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

Bug#827357: ITP: lacme -- ACME client written with process isolation and minimal privileges in mind

[Guilhem Moulin]

Package: wnpp
Severity: wishlist
Owner: Guilhem Moulin 

* Package name: lacme
  Version : 0.1
  Upstream Author : Guilhem Moulin 
* URL : https://git.guilhem.org/lacme/about/
* License : GPL-3+
  Programming Lang: Perl
  Description : ACME client written with process isolation and minimal 
privileges in mind

lacme is divided into four components, each with its own executable:

  * A process to manage the account key and issue SHA-256 signatures
needed for each ACME command.  (This process binds to a UNIX-domain
socket to reply to signature requests from the ACME client.)  One
can use the UNIX-domain socket forwarding facility of OpenSSH 6.7
and later to run this process on a different host.

  * A "master" process, which runs as root and is the only component
with access to the private key material of the server keys.  It is
used to fork the ACME client (and optionally the ACME webserver)
after dropping root privileges.  For certificate issuances, it also
generates Certificate Signing Requests, then verifies the validity
of the issued certificate, and optionally reloads or restarts
services.

  * An actual ACME client, which builds ACME commands and dialogues with
the remote ACME server.  Since ACME commands need to be signed with
the account key, the "master" process passes the UNIX-domain socket
of the account key manager to the ACME client: data signatures are
requested by writing the data to be signed to the socket.

  * For certificate issuances, an optional webserver, which is spawned
by the "master" process when no service is listening on the HTTP
port.  (The only challenge type currently supported is "http-01",
which requires a webserver to answer challenges.)  That webserver
only processes GET and HEAD requests under the
"/.well-known/acme-challenge/" URI.  By default some iptables(8)
rules are automatically installed to open the HTTP port, and removed
afterwards.

-- 
Guilhem.


signature.asc
Description: PGP signature

Bug#827358: ITP: lacme-accountd -- lacme account key manager

[Guilhem Moulin]

Package: wnpp
Severity: wishlist
Owner: Guilhem Moulin 

* Package name: lacme-accountd
  Version : 0.1
  Upstream Author : Guilhem Moulin 
* URL : https://git.guilhem.org/lacme/about/
* License : GPL-3+
  Programming Lang: Perl
  Description : lacme account key manager

lacme is an ACME client written with process isolation and minimal
privileges in mind.  It is divided into four components, each with its
own executable:

  * A process to manage the account key and issue SHA-256 signatures
needed for each ACME command.  (This process binds to a UNIX-domain
socket to reply to signature requests from the ACME client.)  One
can use the UNIX-domain socket forwarding facility of OpenSSH 6.7
and later to run this process on a different host.

  * A "master" process, which runs as root and is the only component
with access to the private key material of the server keys.  It is
used to fork the ACME client (and optionally the ACME webserver)
after dropping root privileges.  For certificate issuances, it also
generates Certificate Signing Requests, then verifies the validity
of the issued certificate, and optionally reloads or restarts
services.

  * An actual ACME client, which builds ACME commands and dialogues with
the remote ACME server.  Since ACME commands need to be signed with
the account key, the "master" process passes the UNIX-domain socket
of the account key manager to the ACME client: data signatures are
requested by writing the data to be signed to the socket.

  * For certificate issuances, an optional webserver, which is spawned
by the "master" process when no service is listening on the HTTP
port.  (The only challenge type currently supported is "http-01",
which requires a webserver to answer challenges.)  That webserver
only processes GET and HEAD requests under the
"/.well-known/acme-challenge/" URI.  By default some iptables(8)
rules are automatically installed to open the HTTP port, and removed
afterwards.

lacme-accountd is the first (account key manager) component.  It is the
only component with access to the account key.

-- 
Guilhem.


signature.asc
Description: PGP signature

Bug#827359: ooniprobe: post-install script gives confusing output

[Iain R. Learmonth]

Package: ooniprobe
Severity: normal
Control: forwarded -1 https://github.com/TheTorProject/ooni-probe/issues/539
Control: owner -1 !

Hi,

After installing ooniprobe the uses is being instructed to run the
default deck from a non existent path. This is because we install the
decks in a different place in the Debian package.

The fix for this will be to redirect the output of oonideckgen to
/dev/null. We could also add a message with the correct path.

Thanks,
Iain.

-- 

Bug#816389: transition: php7.0

[David Prévot]

Hi,

Le 15/06/2016 à 03:56, Ondřej Surý a écrit :
> - php-guzzle - seems fixed to me, but dak still wants to remove the
> package

Code is PHP5-specific, it’s superseded by php-guzzlehttp. None of them
should be released in Stretch, so it’s perfectly fine to see it go away.

Regards

David



signature.asc
Description: OpenPGP digital signature

Bug#827355: RFS: burp/1.4.40-1 [QA] -- Simple cross-platform network BackUp and Restore Program

[Mattia Rizzolo]

control: tag -1 moreinfo
control: owner -1 !

continuing over IRC :)

On Wed, Jun 15, 2016 at 06:36:20PM +0900, Sean Whitton wrote:
> Package: sponsorship-requests
> Severity: normal
> 
> Dear mentors,
> 
> I am looking for a QA upload of burp.
> 
> * Package name: burp
>   Version : 1.4.40-1
>   Upstream Author : Graham Keeling 
> * URL : http://burp.grke.net/
> * License : AGPL-3
>   Section : utils
> 
> Changes since the last upload:
> 
>   * QA upload.
>   * Set maintainer to QA team.
>   * Package new upstream release (Closes: #774715).
> Upstream identifies version 1.4.40 as their "stable" release.
>   * Apply patch from Svante Signell to fix build on the GNU Hurd
> (Closes: #675761, #747672).
>   * Add Recommends: openssl (Closes: #745376).
>   * Repair d/copyright:
> - Move 'Files: *' paragraph to the top of the file
> - Move src/win32/compat/getopt.c and src/win32/compat/sys/mtio.h
>   paragraphs to end of file
> - Add myself to paragraph for debian/ subdir
> - Correct invalid shortname agplv3 -> AGPL-3
> - Factor out AGPL-3 license to a License: paragraph.
> - Correct invalid shortname Troy D. Hanson License -> custom1
> - Correct copyright years for src/win32/compat/sys/mtio.h
> - Correct some indentation and trailing whitespace
>   * Replace burp-dbg with automatically generated burp-dbgsym.
> - Drop obsolete rules target override_dh_strip.
> - Drop obsolete burp.install.
> - Drop obsolete burp.dirs.
> - Drop obsolete burp-dbg.maintscript.
>   * Drop endian.patch.
> Merged upstream.
>   * Drop wait_for_backup_to_finish.patch.
> Merged upstream.
>   * Refresh a patch.
>   * Bump standards version to 3.9.8 (no changes required).
>   * Update Vcs-* URIs.
>   * Add gbp.conf.
> 
> Download with dget:
> 
> dget -x 
> http://mentors.debian.net/debian/pool/main/b/burp/burp_1.4.40-1.dsc
> 
> Or build it with gbp:
> 
> gbp clone --pristine-tar --debian-branch=debian 
> https://git.spwhitton.name/burp
> cd burp
> git checkout debian/1.4.40-1
> git verify-tag debian/1.4.40-1 # if you have my key
> gbp buildpackage
> 
> Notes:
> 
> 1. I am using a branch called 'debian' because the master branch in the
>collab-maint repo seems to be used for experimental, not sid.  I
>added a gbp.conf so everything should work in the expected way.
> 
> 2. I have an application for collab-maint pending.  When it goes through
>I intend to push my work there; the above git clone URI is temporary.
> 
> 3. Successful sbuild: 
> http://debomatic-i386.debian.net/distribution#unstable/burp/1.4.40-1/buildlog
> 
> Thanks.
> 
> -- 
> Sean Whitton



-- 
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#827360: RM: synce-serial -- RoM; unmaintained

[Jonny Lamb]

Package: ftp.debian.org
Severity: normal

Hi,

synce-serial stopped being useful for real-world devices many years ago. 
Its replacement, synce-hal, was removed from the archive a while ago 
too. Let's get rid of this one finally.


Thanks,

--
Jonny Lamb

Bug#827362: RM: librtfcomp -- RoM; unmaintained

[Jonny Lamb]

Package: ftp.debian.org
Severity: normal

Hi,

This used to be useful but all the SynCE parts that used it have been 
removed from the archive so let's get rid of this too.


Thanks,
--
Jonny Lamb

Bug#827361: matplotlib: please honour SOURCE_DATE_EPOCH to allow reproducible output

[Alexis Bienvenüe]

Package: matplotlib
Version: 1.5.2~rc2-1
Severity: wishlist
Tags: patch upstream
User: reproducible-bui...@lists.alioth.debian.org
Usertags: toolchain
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

While working on the "reproducible builds" effort [1], we have noticed
that some packages (like python-shapely) use matplotlib in their
building process, leading to unreproducible builds (due to the
timestamps inserted in PS/PDF files).

To solve this kind of issues, it would be nice to make matplotlib
support the SOURCE_DATE_EPOCH environment variable [2], so that the
sources last modification date can be used for the timestamps in these
PS and PDF files.

See the attached patch for a proposed solution.

Regards,
Alexis Bienvenüe.

[1] https://wiki.debian.org/ReproducibleBuilds
[2] https://reproducible-builds.org/specs/source-date-epoch/




diff -Nru matplotlib-1.5.2~rc2/debian/changelog matplotlib-1.5.2~rc2/debian/changelog
--- matplotlib-1.5.2~rc2/debian/changelog	2016-05-30 20:36:55.0 +0200
+++ matplotlib-1.5.2~rc2/debian/changelog	2016-06-14 19:42:45.0 +0200
@@ -1,3 +1,9 @@
+matplotlib (1.5.2~rc2-1.0~reproducible1) UNRELEASED; urgency=medium
+
+  * Reproducible PS/PDF output, using SOURCE_DATE_EPOCH (when set)
+
+ -- Alexis Bienvenüe   Tue, 14 Jun 2016 19:42:45 +0200
+
 matplotlib (1.5.2~rc2-1) unstable; urgency=medium
 
   [ Sandro Tosi ]
diff -Nru matplotlib-1.5.2~rc2/debian/patches/honour-SOURCE_DATE_EPOCH.patch matplotlib-1.5.2~rc2/debian/patches/honour-SOURCE_DATE_EPOCH.patch
--- matplotlib-1.5.2~rc2/debian/patches/honour-SOURCE_DATE_EPOCH.patch	1970-01-01 01:00:00.0 +0100
+++ matplotlib-1.5.2~rc2/debian/patches/honour-SOURCE_DATE_EPOCH.patch	2016-06-14 23:27:09.0 +0200
@@ -0,0 +1,99 @@
+Description: Honour SOURCE_DATE_EPOCH
+ Honour the SOURCE_DATE_EPOCH environment variable, to build timestamps
+ in PS/PDF outputs. This allows reproducible output.
+ See https://reproducible-builds.org/specs/source-date-epoch/
+Author: Alexis Bienvenüe 
+
+Index: matplotlib-1.5.2~rc2/lib/matplotlib/backends/backend_pdf.py
+===
+--- matplotlib-1.5.2~rc2.orig/lib/matplotlib/backends/backend_pdf.py
 matplotlib-1.5.2~rc2/lib/matplotlib/backends/backend_pdf.py
+@@ -23,7 +23,7 @@ import numpy as np
+ from matplotlib.externals.six import unichr
+ 
+ 
+-from datetime import datetime
++from datetime import datetime, tzinfo, timedelta
+ from math import ceil, cos, floor, pi, sin
+ 
+ import matplotlib
+@@ -134,6 +134,20 @@ def _string_escape(match):
+ assert False
+ 
+ 
++# tzinfo class for UTC
++class UTCtimezone(tzinfo):
++"""UTC"""
++
++def utcoffset(self, dt):
++return timedelta(0)
++
++def tzname(self, dt):
++return "UTC"
++
++def dst(self, dt):
++return timedelta(0)
++
++
+ def pdfRepr(obj):
+ """Map Python objects to PDF syntax."""
+ 
+@@ -201,10 +215,14 @@ def pdfRepr(obj):
+ # A date.
+ elif isinstance(obj, datetime):
+ r = obj.strftime('D:%Y%m%d%H%M%S')
+-if time.daylight:
+-z = time.altzone
++z = obj.utcoffset()
++if z is not None:
++z = z.seconds
+ else:
+-z = time.timezone
++if time.daylight:
++z = time.altzone
++else:
++z = time.timezone
+ if z == 0:
+ r += 'Z'
+ elif z < 0:
+@@ -457,10 +475,19 @@ class PdfFile(object):
+ self.writeObject(self.rootObject, root)
+ 
+ revision = ''
++# get source date from SOURCE_DATE_EPOCH, if set
++# See https://reproducible-builds.org/specs/source-date-epoch/
++source_date_epoch = os.getenv("SOURCE_DATE_EPOCH")
++if source_date_epoch:
++source_date = datetime.utcfromtimestamp(int(source_date_epoch))
++source_date = source_date.replace(tzinfo=UTCtimezone())
++else:
++source_date = datetime.today()
++
+ self.infoDict = {
+ 'Creator': 'matplotlib %s, http://matplotlib.org' % __version__,
+ 'Producer': 'matplotlib pdf backend%s' % revision,
+-'CreationDate': datetime.today()
++'CreationDate': source_date
+ }
+ 
+ self.fontNames = {} # maps filenames to internal font names
+Index: matplotlib-1.5.2~rc2/lib/matplotlib/backends/backend_ps.py
+===
+--- matplotlib-1.5.2~rc2.orig/lib/matplotlib/backends/backend_ps.py
 matplotlib-1.5.2~rc2/lib/matplotlib/backends/backend_ps.py
+@@ -1126,7 +1126,14 @@ class FigureCanvasPS(FigureCanvasBase):
+ if title: print("%%Title: "+title, file=fh)
+ print(("%%Creator: matplotlib version "
+  +__version__+", http://matplotlib.org/";), file=fh)
+-print("%%CreationDate: "+time.ctime(time.time()), file=fh)
++#

Bug#805990: acpica-unix: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

[Santiago Vila]

Any progress on this? I provided a patch. It does not work?

Thanks.

Bug#817963: possible workaround

[dmanye]

hello,

i found the same bug as niko. casually i found out that removing and 
installing again the package solves the problem: pointing the browser to 
localhost/wims works as expected.


i attach gzipped the installation log in case it may help.

i'm using an imaging system, so i can reproduce the bug easily if you 
want me to test.


thanks for packaging wims.

salut.

Bug#817963: possible workaround

[dmanye]

El 15/06/16 a les 12:46, dmanye ha escrit:

hello,

i found the same bug as niko. casually i found out that removing and 
installing again the package solves the problem: pointing the browser 
to localhost/wims works as expected.


i attach gzipped the installation log in case it may help.

i'm using an imaging system, so i can reproduce the bug easily if you 
want me to test.


thanks for packaging wims.

salut.


oops, i forgot to attach the log!


apt-get-install-wims.log.gz
Description: application/gzip

Bug#827361: matplotlib: please honour SOURCE_DATE_EPOCH to allow reproducible output

[Sandro Tosi]

Hello Alexis,
can you please send this upstream? thanks!

On Wed, Jun 15, 2016 at 11:44 AM, Alexis Bienvenüe  wrote:
> Package: matplotlib
> Version: 1.5.2~rc2-1
> Severity: wishlist
> Tags: patch upstream
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: toolchain
> X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
>
> Dear Maintainer,
>
> While working on the "reproducible builds" effort [1], we have noticed
> that some packages (like python-shapely) use matplotlib in their
> building process, leading to unreproducible builds (due to the
> timestamps inserted in PS/PDF files).
>
> To solve this kind of issues, it would be nice to make matplotlib
> support the SOURCE_DATE_EPOCH environment variable [2], so that the
> sources last modification date can be used for the timestamps in these
> PS and PDF files.
>
> See the attached patch for a proposed solution.
>
> Regards,
> Alexis Bienvenüe.
>
> [1] https://wiki.debian.org/ReproducibleBuilds
> [2] https://reproducible-builds.org/specs/source-date-epoch/
>
>
>
>



-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

Bug#827363: Erlang 18.3.4 is out

[Alexey Lebedeff]

Package: erlang
Version: 1:18.3-dfsg-1

Erlang/OTP minor releases are not released as a tarballs at
http://erlang.org/download/

But nevertheless they can contain important fixes.
E.g.:
- 18.3.1 contains an important mnesia fix that is affecting rabbitmq
- 18.3.1-18.3.4 contains several SSL/TLS fixes that are also affecting
users (there were several threads in different mailing lists)

So I suggest updating get-orig-source target in debian/rules to use
downloads at https://github.com/erlang/otp/archive/OTP-$(REL).tar.gz and
then build the latest minor release - 18.3.4 at the time of reporting this
bug.

Bug#827010: Iceweasel & netbock

[Holger Levsen]

On Tue, Jun 14, 2016 at 11:05:00AM +0200, Wolfgang Schweer wrote:
> On Sat, Jun 11, 2016 at 10:02:16AM +0200, Petter Reinholdtsen wrote:
> > Also, when Jessie yesterday switched to Firefox from Iceweasel,  our
> > Iceweasel setup is ignored.  It is these files:
> > 
> >   /etc/iceweasel/profile/cert_override.txt
> >   /etc/iceweasel/pref/debian-edu-homepage-ldap.js
> > 
> > I believe they must be moved to take effect.
> 
> The 'profile' and 'pref' subdir locations seem to have lost any effect.
> Instead /usr/share/firefox-esr/browser/defaults/ is used, I guess.
> 
> As far as /etc/iceweasel/profile/cert_override.txt is concerned:
> 
> Even creating /usr/share/firefox-esr/browser/defaults/profile and 
> moving the override file to this subdir is of no avail. In this case the 
> override file is copied into a newly added user profile dir but the 
> content is zero.
> However, the override file is also present in 
> /etc/skel/.mozilla/firefox/debian-edu.default/
> and this is enough to get it into the user profile.
> 
> The file /etc/iceweasel/pref/debian-edu-homepage-ldap.js could be moved 
> to /etc/firefox-esr/ but then the ability to provide the homepage URL 
> via LDAP is lost.
> 
> To keep the LDAP feature, I used this script as a workaround (might be 
> smarter, I guess):
 
For the purpose of better tracking this, I think we need a new bug, at
least I'm lost in #827010 which is said to be fixed in debian-edu-config
1.901, but only partially it seems. (And not at all in jessie.)

We first need to fix this new bug in unstable and the cherry-pick/backport
this fix into jessie (and maybe/probably wheezy…) and to do the latter, we
need a bug report. (And a bug report also helps fixing this in sid.)

> BTW, wheezy has got firefox-esr as well via security update.

Let's fix sid and jessie first and then see, if someone has the time and
energy to get this fix into wheezy too…

-- 
cheers,
Holger


signature.asc
Description: Digital signature

Bug#827342: linux-image-4.5.0-2-amd64: luks rootfs not recognized at boot after upgrade to linux-image 4.5.5

[Ben Hutchings]

Control: tag -1 moreinfo

On Wed, 2016-06-15 at 08:56 +0200, Sander van Grieken wrote:
> Package: src:linux
> Version: 4.5.5-1
> Severity: important
> 
> Upgrading linux kernel from 4.5.4 to 4.5.5 broke my boot.
> 
> I have a LUKS rootfs on top of a mdadm managed raid0. Starting from 4.5.5 it
> doesn't recognize the luks volume at boot. The same happens with 4.6.1

LUKS volumes are recognised and set uo by userland, so are you sure
this is due to the kernel upgrade?

> The raid0 is not explicitly made with mdadm, it was previously handled by
> dmraid I believe (fakeraid?)

I'm assuming that after a delay you see an '(initramfs)' shell prompt.
Do you see any error messages before that?  If you then enter 'cat
/proc/partitions', which devices does it show?

Ben.

-- 
Ben Hutchings
Reality is just a crutch for people who can't handle science fiction.


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

Bug#826712: im a little too late to the party

[alberto fuentes]

Control: severity -1 grave


im a little too late to the party since this already migrated to testing
and now im affected.

New version is in new queue yet :(

thanks for working on this!

Bug#827364: apt update: appearing and disappearing local-apt-repository sources

[Paul Wise]

Package: apt
Version: 1.2.12
Severity: normal

Whenever I run `apt update`, the packages from the repo I setup
using local-apt-repository disappear from `apt policy test-package`.
Then when I run `apt update` again they reappear. And so on and so
forth. This happens both in my main system and in a chdist.
I've attached logs from the test that I did with chdist:

pabs@chianamo ~ $ chdist create test
Now edit /home/pabs/.chdist/test/etc/apt/sources.list
Run chdist apt-get test update
And enjoy.
pabs@chianamo ~ $ ln -sf /etc/apt/sources.list.d/local-apt-repository.list 
/home/pabs/.chdist/test/etc/apt/sources.list
pabs@chianamo ~ $ chdist apt-get test update -o Debug::pkgAcquire::Worker=1 &> 
log ; chdist apt-cache test policy test-package
test-package:
  Installed: (none)
  Candidate: 999
  Version table:
 999 500
    500 file:/var/lib/local-apt-repository ./ Packages
pabs@chianamo ~ $ mv log good.log
pabs@chianamo ~ $ chdist apt-get test update -o Debug::pkgAcquire::Worker=1 &> 
log ; chdist apt-cache test policy test-package
N: Unable to locate package test-package
pabs@chianamo ~ $ mv log bad.log
pabs@chianamo ~ $ tar Jcf logs.tar.xz good.log bad.log 

-- System Information:
Debian Release: stretch/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

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

Versions of packages apt depends on:
ii  adduser 3.114
ii  debian-archive-keyring  2014.3
ii  gnupg   1.4.20-6
ii  gnupg2  2.1.11-7
ii  gpgv1.4.20-6
ii  init-system-helpers 1.34
ii  libapt-pkg5.0   1.2.12
ii  libc6   2.22-11
ii  libgcc1 1:6.1.1-4
ii  libstdc++6  6.1.1-4

apt recommends no packages.

Versions of packages apt suggests:
pn  apt-doc 
ii  aptitude0.8.1-1
ii  dpkg-dev1.18.7
ii  python-apt  1.1.0~beta2

-- 

bye,
pabs

https://wiki.debian.org/PaulWise


logs.tar.xz
Description: application/xz-compressed-tar


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

Bug#648033: iputils: support cross-building

[Dave Chiluk]

Package: iputils
Version: 3:20150815-2
Followup-For: Bug #648033
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu yakkety ubuntu-patch

This is still needed with the latest version 3:20150815-2, although the
patch needed to be updated to Depend on sgmlspl:any.  Please could you
review this, as iputils is part of the base system and useful to
cross-build?

Thanks for considering the patch.
Dave Chiluk

-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial-proposed'), (500, 'xenial'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-24-generic (SMP w/12 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru iputils-20150815/debian/control iputils-20150815/debian/control
--- iputils-20150815/debian/control	2016-03-01 08:47:42.0 -0600
+++ iputils-20150815/debian/control	2016-06-15 06:14:05.0 -0500
@@ -3,7 +3,7 @@
 Priority: extra
 Maintainer: Noah Meyerhans 
 Standards-Version: 3.9.7
-Build-Depends: debhelper (>= 7), sp, sgmlspl, docbook, libcap-dev, libgnutls-openssl-dev, bash (>= 3)
+Build-Depends: debhelper (>= 7), sp, sgmlspl:any, docbook, libcap-dev, libgnutls-openssl-dev, bash (>= 3)
 Vcs-Git: https://anonscm.debian.org/git/collab-maint/iputils.git
 Vcs-Browser: https://anonscm.debian.org/cgit/collab-maint/iputils.git
 
diff -Nru iputils-20150815/debian/rules iputils-20150815/debian/rules
--- iputils-20150815/debian/rules	2016-03-01 08:47:42.0 -0600
+++ iputils-20150815/debian/rules	2016-06-14 05:48:31.0 -0500
@@ -10,6 +10,14 @@
 # This has to be exported to make some magic below work.
 export DH_OPTIONS
 
+DEB_BUILD_GNU_TYPE := $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE)
+DEB_HOST_GNU_TYPE  := $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE)
+ifeq ($(DEB_BUILD_GNU_TYPE),$(DEB_HOST_GNU_TYPE))
+	CROSS :=
+else
+	CROSS := CC=$(DEB_HOST_GNU_TYPE)-gcc
+endif
+
 TARGETS=ping tracepath tracepath6 traceroute6 clockdiff arping
 
 configure:
@@ -17,7 +25,7 @@
 
 build-arch: configure
 	dh_testdir
-	$(MAKE) $(TARGETS)
+	$(MAKE) $(CROSS) $(TARGETS)
 
 build-indep: configure
 	dh_testdir

Bug#827363: [Pkg-erlang-devel] Bug#827363: Erlang 18.3.4 is out

[Sergei Golovan]

severity 827363 wishlist
thanks

Hi Alexey,

On Wed, Jun 15, 2016 at 2:09 PM, Alexey Lebedeff  wrote:
>
> So I suggest updating get-orig-source target in debian/rules to use
> downloads at https://github.com/erlang/otp/archive/OTP-$(REL).tar.gz and
> then build the latest minor release - 18.3.4 at the time of reporting this
> bug.

It's funny that you asked for this exactly at the moment when I'm working on
packaging Erlang using its sources from github.

So, I intend to upload 18.3.4 in a few days.

Cheers!
-- 
Sergei Golovan

Bug#827323: linux: Regression v4.5 -> v4.6: system freeze after suspend/resume due to iAMT watchdog

[Sebastian Reichel]

Hi,

On Wed, Jun 15, 2016 at 08:00:30AM +, Usyskin, Alexander wrote:
> I assume that "This happened with 4.6, but not with v4.5.", yes?

Yes, sorry.

> Do you have vPro system?

Yes, my CPU is i7-5600U.

> Have you provisioned your ME device?

No, I don't think so.

> If not, the iAMT watchdog should not be exposed to user-space and
> should not affect systemd. Do you have /dev/watchdog* with identity
> "iamt_wdt" at you system?

# ls /sys/class/watchdog 
watchdog0
# wd_identify
iTCO_wdt

That's also, what was used by systemd:

Jun 15 01:24:49 earth kernel: iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
Jun 15 01:24:49 earth kernel: iTCO_wdt: Found a Wildcat Point_LP TCO device 
(Version=2, TCOBASE=0x1860)
Jun 15 01:24:49 earth kernel: iTCO_wdt: initialized. heartbeat=30 sec 
(nowayout=0)
Jun 15 01:24:49 earth systemd[1]: Hardware watchdog 'iTCO_wdt', version 0
Jun 15 01:24:49 earth systemd[1]: Set hardware watchdog to 30s.

I have checked with wd_keepalive and I have a few more observations:

 * The freeze did not appear when wd_keepalive is used instead of systemd
 * The freeze appears, if I kill wd_keepalive, so the freeze itself seems
   to be a bug in the iTCO_wdt driver/hardware.

So looks like fdd9b8655933 somehow results in systemd being too slow to
ping the watchdog in time.

-- Sebastian

> -Original Message-
> From: Sebastian Reichel [mailto:s...@debian.org] 
> Sent: Wednesday, June 15, 2016 02:44
> To: Debian Bug Tracking System 
> Subject: Bug#827323: linux: Regression v4.5 -> v4.6: system freeze after 
> suspend/resume due to iAMT watchdog
> 
> Source: linux
> Version: 4.5.5-1
> Severity: normal
> 
> Hi,
> 
> My Lenovo Thinkpad X250 freezes a couple of seconds after resuming
> from suspend. This happened with 4.5, but not with v4.6. I
> bisected the problem using mainline kernel with Debian config to
> the following commit:
> 
> sre@earth ~/src/linux (git)-[fdd9b86...|bisect] % git bisect bad
> fdd9b8655933c3eb3154fe1ed351c17b654258bd is the first bad commit commit 
> fdd9b8655933c3eb3154fe1ed351c17b654258bd
> Author: Alexander Usyskin 
> Date:   Fri Jan 8 00:49:21 2016 +0200
> 
> mei: wd: drop the watchdog code from the core mei driver
> 
> Instead of integrating the iAMT watchdog in the mei core driver
> we will create a watchdog device on the mei client bus and
> create a driver for it.
> 
> This patch removes the watchdog code from the mei core driver.
> 
> Signed-off-by: Alexander Usyskin 
> Signed-off-by: Tomas Winkler 
> Signed-off-by: Greg Kroah-Hartman 
> 
> My system was configured to use the watchdog via "RuntimeWatchdogSec=30"
> in "/etc/systemd/system.conf". After disabling the feature no system freeze
> happens after suspend/resume cycle.
> 
> -- Sebastian
> 
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers testing
>   APT policy: (1000, 'testing'), (500, 'unstable'), (200, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386, armhf
> 
> Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> -
> Intel Israel (74) Limited
> 
> This e-mail and any attachments may contain confidential material for
> the sole use of the intended recipient(s). Any review or distribution
> by others is strictly prohibited. If you are not the intended
> recipient, please contact the sender and delete all copies.
> 


signature.asc
Description: PGP signature

Bug#812533: ITP: plugn -- hook system for shell programs

[Antonio Terceiro]

On Sun, 24 Jan 2016 18:49:14 + Alessio Treglia  wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Alessio Treglia 
> 
> * Package name: plugn
>   Version : 0.2.1
>   Upstream Author : Jeff Lindsay
> * URL : http://github.com/dokku/plugn
> * License : BSD
>   Programming Lang: Go
>   Description : hook system for shell programs
> 
> The plugn command loops through all enabled plugins'
> directories found in the path defined by the environment
> variable PLUGIN_PATH and passes the same arguments to
> any hook scripts by that name.
> 
> plugn provides a mechanism for arguments broadcasting,
> it could accept streams and pass them through each plugin
> as well.

Hi, what is the status of this ITP? dokku seems insteresting, and
depends on this. :)


signature.asc
Description: PGP signature

Bug#802889: please don't depend on all python3 versions

[Mattia Rizzolo]

control: tag -1 -moreinfo
control: severity -1 serious

On Sun, Oct 25, 2015 at 06:27:50PM +1100, Ben Finney wrote:
> On 24-Oct-2015, Matthias Klose wrote:
> > please don't depend on all python3 versions, forcing the
> > installation of all python versions shouldn't be enforced for a
> > module.
> 
> The dependencies on Python 3 interpreter packages are determined by
> ‘dh_python3’, via the “${python3:depends}” substitution variable.
> 
> Are you saying ‘dh_python3’ has done the wrong thing for this package?

dunno and I haven't checked, but now python3.4 is going away, and this
is one of the last 2 blockers, so somehow get rid of python3.4
dependency (after making it build, I guess)

> The Python 3.4 → 3.5 transition is currently underway in Sid, and
> presumably ‘dh_python3’ sets dependencies accordingly. Does that
> explain what you're seeing?

ftr, that transition finished months ago.

-- 
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#827365: apt: Failure with repository on sourceforge

[Michael Lange]

Package: apt
Version: 1.0.9.8.3
Severity: normal

Dear Maintainer,

since sourceforge changed some technical details of their service a few months
ago, debian repositories hosted on sourceforge are no longer handled correctly
by apt-get.
With the following line enabled in /etc/apt/sources.list

deb https://sourceforge.net/projects/un-applet/files/debian debian main

when trying to do "apt-get update" the following error occurs:

(...)
Ign https://sourceforge.net debian Release.gpg
Ign https://sourceforge.net debian Release
Get:17 https://sourceforge.net debian/main amd64 Packages [14.2 kB]
Get:18 https://sourceforge.net debian/main Translation-en_US [14.2 kB]
Get:19 https://sourceforge.net debian/main Translation-en [14.2 kB]
Get:20 https://sourceforge.net debian/main Translation-de [14.2 kB]
Get:21 https://sourceforge.net debian/main Translation-de_DE [14.2 kB]
Get:22 https://sourceforge.net debian/main amd64 Packages [14.2 kB]
Get:23 https://sourceforge.net debian/main Translation-en_US [14.2 kB]
Get:24 https://sourceforge.net debian/main Translation-en [14.2 kB]
Get:25 https://sourceforge.net debian/main Translation-de [14.2 kB]
Get:26 https://sourceforge.net debian/main Translation-de_DE [14.2 kB]
Get:27 https://sourceforge.net debian/main amd64 Packages [14.2 kB]
Get:28 https://sourceforge.net debian/main Translation-en_US [14.2 kB]
Get:29 https://sourceforge.net debian/main Translation-en [14.2 kB]
Get:30 https://sourceforge.net debian/main Translation-de [14.2 kB]
Get:31 https://sourceforge.net debian/main Translation-de_DE [14.2 kB]
Get:32 https://sourceforge.net debian/main Translation-en_US [14.2 kB]
Get:33 https://sourceforge.net debian/main Translation-en [14.2 kB]
Get:34 https://sourceforge.net debian/main Translation-de [14.2 kB]
Get:35 https://sourceforge.net debian/main Translation-de_DE [14.2 kB]
Err https://sourceforge.net debian/main amd64 Packages
  Protocol "http" not supported or disabled in libcurl
Get:36 https://sourceforge.net debian/main Translation-en_US [14.2 kB]
Ign https://sourceforge.net debian/main Translation-en_US
Get:37 https://sourceforge.net debian/main Translation-en [14.2 kB]
Ign https://sourceforge.net debian/main Translation-en
Get:38 https://sourceforge.net debian/main Translation-de [14.2 kB]
Ign https://sourceforge.net debian/main Translation-de
Get:39 https://sourceforge.net debian/main Translation-de_DE [14.2 kB]
Ign https://sourceforge.net debian/main Translation-de_DE
Fetched 175 kB in 35s (4,905 B/s)
W: Failed to fetch https://sourceforge.net/projects/un-
applet/files/debian/dists/debian/main/binary-amd64/Packages  Protocol "http"
not supported or disabled in libcurl

E: Some index files failed to download. They have been ignored, or old ones
used instead.


This is apparently the same problem as described at:
https://sourceforge.net/p/forge/site-support/12143/

I can only guess about the reasons for this, I suppose it might have something
to do with some fancy http(s) redirections sourceforge does, which maybe apt in
not able to handle correctly.
Interestingly the bug does not occur on an outdated system which still has an
old LMDE install running, which has not been supported for about two years
(which is basically Jessie as testing, "frozen" on a state somewhere in 2014).
This system still uses apt-0.9.12.1 which handles the sources.list entry
mentioned above correctly, allowing to perform "apt-get update" and afterwards
installing packages from this repository.

Another try on debian testing with apt-1.2.12 again failed, but this time with
a different error message:

(...)
Ign:5 https://sourceforge.net/projects/un-applet/files/debian debian InRelease
Ign:6 https://sourceforge.net/projects/un-applet/files/debian debian Release
Ign:7 https://sourceforge.net/projects/un-applet/files/debian debian/main amd64
Packages
Ign:8 https://sourceforge.net/projects/un-applet/files/debian debian/main i386
Packages
Ign:9 https://sourceforge.net/projects/un-applet/files/debian debian/main all
Packages
Ign:10 https://sourceforge.net/projects/un-applet/files/debian debian/main
Translation-en
Ign:11 https://sourceforge.net/projects/un-applet/files/debian debian/main
Translation-de
Ign:12 https://sourceforge.net/projects/un-applet/files/debian debian/main
Translation-de_DE
Ign:7 https://sourceforge.net/projects/un-applet/files/debian debian/main amd64
Packages
Ign:8 https://sourceforge.net/projects/un-applet/files/debian debian/main i386
Packages
Ign:9 https://sourceforge.net/projects/un-applet/files/debian debian/main all
Packages
Ign:10 https://sourceforge.net/projects/un-applet/files/debian debian/main
Translation-en
Ign:11 https://sourceforge.net/projects/un-applet/files/debian debian/main
Translation-de
Ign:12 https://sourceforge.net/projects/un-applet/files/debian debian/main
Translation-de_DE
Ign:7 https://sourceforge.net/projects/un-applet/files/debian debian/main amd64
Packages
Ign:8 https://sourceforge.net/projects/un-applet/files/debian debian/main i386
Packages
I

Bug#827366: RM: python3.4 -- RoQA; obsolete; superseded by python3.5

[Mattia Rizzolo]

package: ftp.debian.org
tags: moreinfo
control: block -1 by 802889 820186

Time to get rid of another python version.

The migration to python3.5 completed successfully, and according to dak
there are only 2 rdeps not yet fixed.

-- 
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#827367: vagrant-cachier: Configuring cache bucket fails for Fedora 23 box

[Olivier Berger]

Package: vagrant-cachier
Version: 1.2.1-2
Severity: normal
Tags: upstream

Dear Maintainer,

The provisionning goes like this :

==> default: Mounting shared folders...
default: /vagrant => 
/home/olivier/git/github.com/kaorimatz/packer-templates/tests
default: /tmp/vagrant-cache => 
/home/olivier/.vagrant.d/cache/fedora-23-x86_64
==> default: Configuring cache buckets...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

sed -i 's/keepcache=0/keepcache=1/g' /etc/yum.conf

Stdout from the command:



Stderr from the command:

sed: impossible de lire /etc/yum.conf: Aucun fichier ou dossier de ce type

(french variant of "no such file or directory").

Which happens since Fedora has migrated from yum to dnf, and vagrant-cachier 
hasn't adapted.

Thus it would be great that patches floating upstream can be integrated. 

Thanks in advance.

Best regards,

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

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

Versions of packages vagrant-cachier depends on:
ii  jruby [ruby-interpreter]1.7.22-2
ii  ruby1:2.3.0+4
ii  ruby2.1 [ruby-interpreter]  2.1.5-4
ii  ruby2.2 [ruby-interpreter]  2.2.4-1

vagrant-cachier recommends no packages.

vagrant-cachier suggests no packages.

-- no debconf information

Bug#827302: v4l-utils: FTBFS: jpeg_memsrcdest.h:6:1: error: conflicting types for 'jpeg_mem_src'

[Gregor Jasny]

Hello Bill and Ondřej,

Do you know how to properly detect jpeg_mem_src presence in libjpeg(turbo)?

Since the transition to jpegturbo my package FTBFS:

On 14/06/16 20:42, Chris Lamb wrote:

  In file included from jpeg.c:28:0:
  jpeg_memsrcdest.h:6:1: error: conflicting types for 'jpeg_mem_src'
   jpeg_mem_src (j_decompress_ptr cinfo, unsigned char * buffer,
   ^
  In file included from libv4lconvert-priv.h:31:0,
   from jpeg.c:26:
  /usr/include/jpeglib.h:923:14: note: previous declaration of 'jpeg_mem_src' 
was here
   EXTERN(void) jpeg_mem_src (j_decompress_ptr cinfo,
^


Would it make sense to change the check in the emulation layer [1] from

#if JPEG_LIB_VERSION < 80

to

#if JPEG_LIB_VERSION < 80 && !defined(MEM_SRCDST_SUPPORTED)

or should I add a check during autoconf?

Thanks,
Gregor

[1] 
https://git.linuxtv.org/v4l-utils.git/tree/lib/libv4lconvert/jpeg_memsrcdest.h

Bug#827368: openstack-pkg-tools: /usr/share/openstack-pkg-tools/pkgos_func:pkgos_inifile get - does not work

[Turbo Fredriksson]

Package: openstack-pkg-tools
Version: 50
Severity: minor

Sourcing /usr/share/openstack-pkg-tools/pkgos_func in the shell and then
trying to use the "get" part of it does not work:

- s n i p -
bladeA01b:~# . /usr/share/openstack-pkg-tools/pkgos_func
bladeA01b:~# export PKGOS_VERBOSE=yes
bladeA01b:~# pkgos_inifile get /etc/cinder/cinder.conf DEFAULT enabled_backends
pkgos_inifile: Getting value in 
/etc/cinder/cinder.conf:[DEFAULT]/enabled_backends
bladeA01b:~# grep ^enabled_backends /etc/cinder/cinder.conf
enabled_backends = lvm
- s n i p -

The "set" part works like a charm though!

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

Kernel: Linux 3.16.0-4-amd64 (SMP w/16 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages openstack-pkg-tools depends on:
ii  autopkgtest4.0
ii  libxml-xpath-perl  1.36-1
ii  madison-lite   0.21
ii  pristine-tar   1.34

openstack-pkg-tools recommends no packages.

openstack-pkg-tools suggests no packages.

-- no debconf information

Bug#827369: apm_emu: Failed to start Load Kernel Modules

[Mathieu Malaterre]

Package: hw-detect
Version: 1.118

When installing from Debian Installer Stretch Alpha 6 release on
PowerPC (Mac Mini G4), the /etc/modules files gets populated with

[...]
apm_emu
[...]


AFAIK this module does not exist anymore:

$ sudo modprobe apm_emu
modprobe: FATAL: Module apm_emu not found in directory
/lib/modules/4.5.0-2-powerpc

It would be nice to remove the old fix for
https://bugs.debian.org/279212, since it now generates an error
message in systemd logs: https://bugs.debian.org/784636.

Thanks

Bug#827037: RFS: xpad/4.8.0-1 [ITA]

[JCF Ploemen]

On Mon, 13 Jun 2016 13:01:19 +0900
Sean Whitton  wrote:

> I suggest that you continue installing AUTHORS and THANKS (if they
> contain what I guess they contain) -- it's nice to include credits for
> upstream's hard work.

Thanks for your comment.

As much as I understand the sentiment, I don't think installing these
files purely as a nicety does justice to the interests of end users
expecting to find actual documentation in that very place.

A quick read of their comments and frustration on the launchpad bug
referenced in the package changelog clearly shows there's no better way
to acknowledge upstream's hard work than simply keeping the debian
package up-to-date.

Bug#827370: php5-common: mail clutter from sessionclean cronjob

[Daniel Reichelt]

Package: php5-common
Version: 5.6.22+dfsg-0+deb8u1
Severity: normal

Hi,

since the most recent security upgrade, I keep receiving cronjob mails saying

8<-
find: `/proc/14918/fd': No such file or directory
8<-

The count of these entries variies of course, and whether or not that
race-conditions triggers depends on the server load. At least during daytime
it's pretty constant - and annoying...



Thanks
Daniel


8<-

-- Package-specific info:
 Additional PHP 5 information 

 PHP 5 SAPI (php5query -S): 
cli
cgi
apache2

 PHP 5 Extensions (php5query -M -v): 
mysqlnd (Enabled for cli by maintainer script)
mysqlnd (Enabled for cgi by maintainer script)
mysqlnd (Enabled for apache2 by maintainer script)
apcu (Enabled for cli by maintainer script)
apcu (Enabled for cgi by maintainer script)
apcu (Enabled for apache2 by maintainer script)
mysql (Enabled for cli by maintainer script)
mysql (Enabled for cgi by maintainer script)
mysql (Enabled for apache2 by maintainer script)
pdo (Enabled for cli by maintainer script)
pdo (Enabled for cgi by maintainer script)
pdo (Enabled for apache2 by maintainer script)
pspell (Enabled for cli by maintainer script)
pspell (Enabled for cgi by maintainer script)
pspell (Enabled for apache2 by maintainer script)
json (Enabled for cli by maintainer script)
json (Enabled for cgi by maintainer script)
json (Enabled for apache2 by maintainer script)
mysqli (Enabled for cli by maintainer script)
mysqli (Enabled for cgi by maintainer script)
mysqli (Enabled for apache2 by maintainer script)
gd (Enabled for cli by maintainer script)
gd (Enabled for cgi by maintainer script)
gd (Enabled for apache2 by maintainer script)
opcache (Enabled for cli by maintainer script)
opcache (Enabled for cgi by maintainer script)
opcache (Enabled for apache2 by maintainer script)
curl (Enabled for cli by maintainer script)
curl (Enabled for cgi by maintainer script)
curl (Enabled for apache2 by maintainer script)
mcrypt (Enabled for cli by maintainer script)
mcrypt (Enabled for cgi by maintainer script)
mcrypt (Enabled for apache2 by maintainer script)
pdo_mysql (Enabled for cli by maintainer script)
pdo_mysql (Enabled for cgi by maintainer script)
pdo_mysql (Enabled for apache2 by maintainer script)
intl (Enabled for cli by maintainer script)
intl (Enabled for cgi by maintainer script)
intl (Enabled for apache2 by maintainer script)

 Configuration files: 
 /etc/php5/mods-available/pdo.ini 
extension=pdo.so

 /etc/php5/mods-available/opcache.ini 
zend_extension=opcache.so


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

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)

Versions of packages php5-common depends on:
ii  libc6   2.19-18+deb8u4
ii  lsof4.86+dfsg-1
ii  psmisc  22.21-2
ii  sed 4.2.2-4+b1
ii  ucf 3.0030

php5-common recommends no packages.

Versions of packages php5-common suggests:
ii  php5-apcu [php5-user-cache]  4.0.7-1

Versions of packages php5-cli depends on:
ii  libbz2-1.01.0.6-7+b3
ii  libc6 2.19-18+deb8u4
ii  libcomerr21.42.12-1.1
ii  libdb5.3  5.3.28-9
ii  libedit2  3.1-20140620-2
ii  libgssapi-krb5-2  1.12.1+dfsg-19+deb8u2
ii  libk5crypto3  1.12.1+dfsg-19+deb8u2
ii  libkrb5-3 1.12.1+dfsg-19+deb8u2
ii  libmagic1 1:5.22+15-2+deb8u1
ii  libonig2  5.9.5-3.2
ii  libpcre3  2:8.35-3.3+deb8u4
ii  libqdbm14 1.8.78-5+b1
ii  libssl1.0.0   1.0.1t-1+deb8u2
ii  libxml2   2.9.1+dfsg1-5+deb8u2
ii  mime-support  3.58
ii  php5-json 1.3.6-1
ii  tzdata2016d-0+deb8u1
ii  ucf   3.0030
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages php5-cli recommends:
pn  php5-readline  

Versions of packages php5-cli suggests:
ii  php-pear  5.6.22+dfsg-0+deb8u1

Versions of packages libapache2-mod-php5 depends on:
ii  apache2 2.4.10-10+deb8u4
ii  apache2-bin [apache2-api-20120211]  2.4.10-10+deb8u4
ii  libbz2-1.0  1.0.6-7+b3
ii  libc6   2.19-18+deb8u4
ii  libcomerr2  1.42.12-1.1
ii  libdb5.35.3.28-9
ii  libgssapi-krb5-21.12.1+dfsg-19+deb8u2
ii  libk5crypto31.12.1+dfsg-19+deb8u2
ii  libkrb5-3   1.12.1+dfsg-19+deb8u2
ii  libmagic1   1:5.22+15-2+deb8u1
ii  libonig25.9.5-3.2
ii  libpcre32:8.35-3.3+deb8u4
ii  libqdbm14   1.8.78-5+b1
ii  libssl1.0.0 1.0.1t-1+deb8u2
ii  libstdc++6  

Bug#827371: letsencrypt.sh: Use hook.d folder?

[Elrond]

Package: letsencrypt.sh
Version: 0.1.0-3
Severity: wishlist

Hi,

I am starting to test hook scripts to deploy the
certificates into appropiate places. One idea I got while
doing that: Have a hook.d folder with scripts that get all
executed.

Plan:
- Add the attached script to /etc/letsencrypt.sh
- Add HOOK="/etc/letsencrypt.sh/run-hookd.sh" to the main
  config or a conf.d/00-debian.sh.
- Create a /etc/letsencrypt.sh/hook.d
- I am not entirely sure about the options to run-parts.

What do you think?


Cheers

Elrond


run-hookd.sh
Description: Bourne shell script

Bug#827372: gnash-dev: please add dependency “Suggests: gnash-doc”

[Ben Finney]

Package: gnash-dev
Version: 0.8.11~git20160608-1
Severity: minor

Dear Maintainer,

Working with the ‘gnash-dev’ package requires understanding how it
works and what it does.

The documentation package is primarily developer documentation. Please
set a “Suggests: gnash-doc” dependency to the developer library
package ‘gnash-dev’.

This will mean that administrators choosing to install it will receive
the suggestion.

-- 
 \   “The lift is being fixed for the day. During that time we |
  `\regret that you will be unbearable.” —hotel, Bucharest |
_o__)  |
Ben Finney 


signature.asc
Description: PGP signature

Bug#826712: im a little too late to the party

[Luca Boccassi]

On Wed, 2016-06-15 at 13:20 +0200, alberto fuentes wrote:
> Control: severity -1 grave
> 
> 
> im a little too late to the party since this already migrated to testing
> and now im affected.
> 
> New version is in new queue yet :(
> 
> thanks for working on this!

Wouldn't have made a difference, a package in non-free cannot block the
migration of a package in the main archive.
And we wouldn't want to block the migration of the kernel even if it
would be possible.

There is nothing we can do, the packages are in the NEW queue, so it's
up to the FTP masters.

https://ftp-master.debian.org/new.html

Kind regards,
Luca Boccassi


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

Bug#812533: ITP: plugn -- hook system for shell programs

[Alessio Treglia]

Hi Antonio!

On Wed, Jun 15, 2016 at 12:29 PM, Antonio Terceiro  wrote:
> Hi, what is the status of this ITP? dokku seems insteresting, and
> depends on this. :)

I'm not making much progress on this. Although I'm still interested in
this, TBH I can't allocate much time for it right now, so please feel
free to take over and include me in the Uploaders list.

Cheers!

-- 
Alessio Treglia  | www.alessiotreglia.com
Debian Developer | ales...@debian.org
Ubuntu Core Developer|  quadris...@ubuntu.com
0416 0004 A827 6E40 BB98 90FB E8A4 8AE5 311D 765A

Bug#792201: not fixed upstream

[Ximin Luo]

Forwarding this exchange to the correct bug so future people don't get confused.

To be clear, it should be fine to mark this fixed for the next version 1.8.12 
and later.

X

Ximin Luo:
> Holger Levsen:
>> Hi,
>>
>> according to the bug log in
>> https://bugzilla.gnome.org/show_bug.cgi?id=751984 this bug aint fixed
>> upstream, but Ximin couldn't reopen it, so that's why it looks like it's
>> fixed upstrean…
>>
> 
> Hi, I could indeed not reopen that bug, but I filed a PR later which was 
> accepted:
> 
> https://github.com/doxygen/doxygen/pull/477
> 
> So now "the upstream bug is fixed" is correct.
> 
> X
> 


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

Bug#827348: qtscript-opensource-src FTBFS on Alpha; double value incorrect in last bit in test suite

[Lisandro Damián Nicanor Pérez Meyer]

tag 827348 - patch
thanks

Hi Michael!  I don't consider turning off the test a good solution. The
test needs a proper fix. Take a look at qFuzzyCompare, for example.

Happy hacking!

-- 
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/
El jun 15, 2016 5:21 AM, "Michael Cree"  escribió:

> Source: qtscript-opensource-src
> Version: 5.6.1+dfsg-2
> Severity: important
> Justification: fails to build from source but built in past
> Tags: patch
> User: debian-al...@lists.debian.org
> Usertags: alpha
>
> qtscript-opensource-src FTBFS on Alpha due to a test suite failure [1]:
>
> FAIL!  : tst_QScriptJsTestSuite::ecma_2/RegExp(/\B/.lastIndex) Compared
> values are not the same
>Actual   (actual): "1.7976931348623155e+308"
>Expected (expect): "1.7976931348623157e+308"
>Loc: [ecma_2/RegExp/properties-002.js(583)]
>
> This is the result of a double precision calculation that has rounded
> the last bit of the calculation in the wrong direction.  That does not
> seem sufficient reason to completely fail the build so I attach a
> patch that disables this test and hope you would consider including
> it in the next upload of qtscript-opensource-src.
>
> Cheers
> Michael.
>
> [1]
> https://buildd.debian.org/status/fetch.php?pkg=qtscript-opensource-src&arch=alpha&ver=5.6.1%2Bdfsg-2&stamp=1465838369
>

Bug#825753: /usr/bin/kubectl: hardcoded API server (or missing documentation)

[Dmitry Smirnov]

Hi Florian,

Thank you for trying packaged Kubernetes. I appreciate your feedback and 
expertise.


On Sunday, 29 May 2016 4:27:04 PM AEST Florian Ernst wrote:
> BTW, upstream's v1.2.3 won't accept '-v42' ("Error: unknown shorthand
> flag: 'v' in -v42") as Debian's v1.2.3 does but insists on '--v=42'
> instead. Such differences between seemingly equal versions will raise
> eyebrows.

This could be explained by different versions of some dependency libraries.
On Debian Kubernetes is built from reusable packages unlike messy upstream 
source tree that is used to produce official binaries... Packaged libraries 
may be of different versions than ones that upstream uses.


> Still, I'd expect kubectl to basically work. I might be missing some
> adjustment that Debian's version of kubectl needs to actually connect to
> GCE-backed clusters, yet I couldn't find anything. Thus, I'm filing this
> bug at "important", but please adjust as you see fit.

How do you configure Kubernetes? Perhaps it should be obvious but did you 
check "/etc/default/kube*" files as well as "/etc/kubernetes/config"?

Please let me know where original Kubernetes expects configuration files.

Thanks.

-- 
Cheers,
 Dmitry Smirnov
 GPG key : 4096R/53968D1B

---

Not a lack of belief, but adherence to false knowledge is the enemy of
progress. And certain that we have found everything worth searching for,
we see no point in further search and inquiry. Believing what is
unworthy of belief, believing falsehood as if it were incontrovertible
truth, and sure that we know everything we will ever need to know, we
are worse than ignorant.
-- Chester Dolan, "Blind Faith"


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

Bug#827302: v4l-utils: FTBFS: jpeg_memsrcdest.h:6:1: error: conflicting types for 'jpeg_mem_src'

[Ondřej Surý]

Hi Gregor,

[removing Bill Allombert from Cc as he was not involved in the
transition to LJT]

$ grep -r MEM_SRCDST_SUPPORTED /usr/include
/usr/include/x86_64-linux-gnu/jconfig.h:#define MEM_SRCDST_SUPPORTED 1

so

#if JPEG_LIB_VERSION < 80 && !defined(MEM_SRCDST_SUPPORTED)

should be sufficient.

Cheers,
-- 
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
Knot Resolver (https://www.knot-resolver.cz/) – secure, privacy-aware,
fast DNS(SEC) resolver

On Wed, Jun 15, 2016, at 14:09, Gregor Jasny wrote:
> Hello Bill and Ondřej,
> 
> Do you know how to properly detect jpeg_mem_src presence in
> libjpeg(turbo)?
> 
> Since the transition to jpegturbo my package FTBFS:
> 
> On 14/06/16 20:42, Chris Lamb wrote:
> >   In file included from jpeg.c:28:0:
> >   jpeg_memsrcdest.h:6:1: error: conflicting types for 'jpeg_mem_src'
> >jpeg_mem_src (j_decompress_ptr cinfo, unsigned char * buffer,
> >^
> >   In file included from libv4lconvert-priv.h:31:0,
> >from jpeg.c:26:
> >   /usr/include/jpeglib.h:923:14: note: previous declaration of 
> > 'jpeg_mem_src' was here
> >EXTERN(void) jpeg_mem_src (j_decompress_ptr cinfo,
> > ^
> 
> Would it make sense to change the check in the emulation layer [1] from
> 
> #if JPEG_LIB_VERSION < 80
> 
> to
> 
> #if JPEG_LIB_VERSION < 80 && !defined(MEM_SRCDST_SUPPORTED)
> 
> or should I add a check during autoconf?
> 
> Thanks,
> Gregor
> 
> [1] 
> https://git.linuxtv.org/v4l-utils.git/tree/lib/libv4lconvert/jpeg_memsrcdest.h

Bug#792201: not fixed upstream

[Holger Levsen]

Hi,

according to the bug log in
https://bugzilla.gnome.org/show_bug.cgi?id=751984 this bug aint fixed
upstream, but Ximin couldn't reopen it, so that's why it looks like it's
fixed upstrean…


-- 
cheers,
Holger


signature.asc
Description: Digital signature

Bug#827373: mailman should use cron.{daily,weekly,monthly}, not cron.d

[Ian Jackson]

Package: mailman
Version: 1:2.1.18-2

In (at least some) previous versions of the Debian mailman package,
the regular tasks were done by dropping files into /etc/cron.monthly/
and so on.

Now, this is done by creating a file /etc/cron.d/mailman.

Using cron.{monthly,weekly,daily} has the following advantages:

 * The timing of regular cron jobs can be adjusted once by the system
   administrator by adjusting the timing of the run-parts invocations.

 * Regular cron jobs are (generally) scheduled sequentially with
   other cron jobs, avoiding multiple cron jobs at once (which can be
   confusing and perhaps even cause lossage)

 * There is less of a problem with conffile edit conflicts, as there
   isn't a single schedule file (cron.d/mailman) which is constantly
   edited and updated.

Please can you switch this back the way it was ?

Also, please can you, for at least one release, ship a dummy file for
cron.d/mailman (with a comment explaining where the contents have
gone).  If you simply delete this conffile, the conffile processing
will retain it, resulting in all the cron jobs running twice.

Thanks,
Ian.

-- 
Ian JacksonThese opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.

Bug#666175: Processed: Re: Bug#666175 closed by Debian FTP Masters (Bug#760986: Removed package(s) from unstable)

[Ian Jackson]

Control: found -1 2.0.11+1-9

Debian Bug Tracking System writes:
> > reopen 666175
...
> Bug reopened
> No longer marked as fixed in versions 1.8.8+1-10+rm.

Interesting.  Was a patch dropped when moving from 1.8 to 2.0 ?

Thanks,
Ian.

Bug#792201: not fixed upstream]

[Holger Levsen]

control: forward -1 https://github.com/doxygen/doxygen/pull/477
thanks

I mailed the wrong Debian bug initially…

- Forwarded message from Ximin Luo  -

Date: Wed, 15 Jun 2016 14:18:45 +0200
From: Ximin Luo 
To: Holger Levsen , 751...@bugs.debian.org
Subject: Re: not fixed upstream

Holger Levsen:
> Hi,
> 
> according to the bug log in
> https://bugzilla.gnome.org/show_bug.cgi?id=751984 this bug aint fixed
> upstream, but Ximin couldn't reopen it, so that's why it looks like it's
> fixed upstrean…
> 

Hi, I could indeed not reopen that bug, but I filed a PR later which was 
accepted:

https://github.com/doxygen/doxygen/pull/477

So now "the upstream bug is fixed" is correct.

X

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

- End forwarded message -

-- 
cheers,
Holger


signature.asc
Description: Digital signature

Bug#827374: gitlab: fails to install: Could not find gem 'addressable (~> 2.3.8)'

[Andreas Beckmann]

Package: gitlab
Version: 8.8.2+dfsg-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

  Selecting previously unselected package gitlab.
  Preparing to unpack .../gitlab_8.8.2+dfsg-4_all.deb ...
  Unpacking gitlab (8.8.2+dfsg-4) ...
  Setting up gitlab (8.8.2+dfsg-4) ...
  Creating/updating gitlab user account...
  adduser: Warning: The home directory `/var/lib/gitlab' does not belong to the 
user you are currently creating.
  Creating runtime directories for gitlab...
  Updating file permissions...
  Configuring hostname and email...
  Registering /etc/gitlab/gitlab.yml via ucf
  
  Creating config file /etc/gitlab/gitlab.yml with new version
  Registering /etc/gitlab/gitlab-debian.conf via ucf
  
  Creating config file /etc/gitlab/gitlab-debian.conf with new version
  
  Creating config file /etc/nginx/sites-available/localhost with new version
  Reloading nginx configuration...
  /usr/sbin/invoke-rc.d: 1: /usr/sbin/invoke-rc.d: /sbin/runlevel: not found
  invoke-rc.d: could not determine current runlevel
  invoke-rc.d: policy-rc.d denied execution of reload.
  Create database if not present
  psql: FATAL:  database "gitlab_production" does not exist
  psql: FATAL:  role "gitlab" does not exist
  Create gitlab user with create database privillege...
  CREATE ROLE
  Make gitlab user owner of gitlab_production database...
  ALTER DATABASE
  Grant all privileges to gitlab user...
  GRANT
  CREATE EXTENSION
  Verifying we have all required libraries...
  Could not find gem 'addressable (~> 2.3.8)' in any of the gem sources 
listed in
  your Gemfile or available on this machine.
  dpkg: error processing package gitlab (--configure):
   subprocess installed post-installation script returned error exit status 7
  Errors were encountered while processing:
   gitlab


cheers,

Andreas


gitlab_8.8.2+dfsg-4.log.gz
Description: application/gzip

Bug#827375: ITP: auto-apt-proxy -- automatic detector of common APT proxy settings

[Antonio Terceiro]

Package: wnpp
Severity: wishlist
Owner: Antonio Terceiro 

* Package name: auto-apt-proxy
  Version : 1
  Upstream Author : Antonio Terceiro 
* URL : 
https://anonscm.debian.org/git/users/terceiro/auto-apt-proxy.git
* License : GPLv3
  Programming Lang: Shell
  Description : automatic detector of common APT proxy settings

Description: automatic detector of common APT proxy settings
 auto-apt-proxy installs itself as an APT proxy autodetector, and detects
 common setups by checking localhost and the network default gateway for
 well-known APT proxies such as apt-cacher-ng.
 .
 This package is most useful for development environments, and will Do The
 Right Thing for:
 .
   * build chroots, with a proxy running on the host system.
   * docker/lxc containers, with a proxy running on the host system.
   * Virtual machines with NAT networking, with a proxy running on the host
   * system.
   * any other system, with a proxy running on its default gateway.
 .
 The following APT proxy servers are supported and automatically detected:
   * apt-cacher-ng
 .
 This package has a minimal set of dependencies in order to minimize the
 influence on systems where it is installed.
 .
 For corporate desktop/server deployments, where the APT proxy can be located
 at any arbitrary host, you should probably try the `squid-deb-proxy-client`
 package instead.

This was born when I got tired of automating over and over to make my chroots,
containers and VMs use my local APT proxy by creating
/etc/apt/apt.conf.d/01proxy with the correct configuration bits. Instead of all
that, I can now just install this simple package and it "Just Works". My idea
is being open for extending the tool to correctly detect other reasonable
scenarios, and specially proxies other than the one I use (apt-cacher-ng).

I did some research and TTBOMK there is no similar solution, so I plan to get
it in the archive so others can benefit, and also to make my life easier with
it. ;-)

-- 
Antonio Terceiro 


signature.asc
Description: PGP signature

Bug#826712: im a little too late to the party

[alberto fuentes]

On Wed, Jun 15, 2016 at 2:21 PM, Luca Boccassi 
wrote:

> Wouldn't have made a difference, a package in non-free cannot block the
> migration of a package in the main archive.
> And we wouldn't want to block the migration of the kernel even if it
> would be possible.
>

Oh, I didnt check it and assume this was the package migrating and breaking

Thanks for your work!

Lets offer some of our crops to the ftp masters so this and the rest of the
nvidia drivers make it soon to the archive :)

Bug#827376: init-system-helpers: invoke-rc.d unconditionally uses /sbin/runlevel without depending on a package providing it

[Andreas Beckmann]

Package: init-system-helpers
Version: 1.34
Severity: important

Hi,

I just noticed this in a piuparts log (#827374):

  /usr/sbin/invoke-rc.d: 1: /usr/sbin/invoke-rc.d: /sbin/runlevel: not found
  invoke-rc.d: could not determine current runlevel
  invoke-rc.d: policy-rc.d denied execution of reload.

/sbin/runlevel is provided by several packages:

https://packages.debian.org/search?mode=path&suite=sid§ion=all&arch=any&searchon=contents&keywords=sbin%2Frunlevel

so I'm not sure what the correct Depends would be ...


Andreas

Bug#827302: v4l-utils: FTBFS: jpeg_memsrcdest.h:6:1: error: conflicting types for 'jpeg_mem_src'

[Bill Allombert]

On Wed, Jun 15, 2016 at 02:09:05PM +0200, Gregor Jasny wrote:
> Hello Bill and Ondřej,
> 
> Do you know how to properly detect jpeg_mem_src presence in libjpeg(turbo)?
> 
> Since the transition to jpegturbo my package FTBFS:
> 
> On 14/06/16 20:42, Chris Lamb wrote:
> >  In file included from jpeg.c:28:0:
> >  jpeg_memsrcdest.h:6:1: error: conflicting types for 'jpeg_mem_src'
> >   jpeg_mem_src (j_decompress_ptr cinfo, unsigned char * buffer,
> >   ^
> >  In file included from libv4lconvert-priv.h:31:0,
> >   from jpeg.c:26:
> >  /usr/include/jpeglib.h:923:14: note: previous declaration of 
> > 'jpeg_mem_src' was here
> >   EXTERN(void) jpeg_mem_src (j_decompress_ptr cinfo,
> >^
> 
> Would it make sense to change the check in the emulation layer [1] from
> 
> #if JPEG_LIB_VERSION < 80

As far as IJG jpeg  is converned, the above is correct.
I do not know for turbo.

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 

Bug#827377: file: CVE-2015-8865: file_check_mem() misbehaves on some input

[Petter Reinholdtsen]

Package: src:file
Version: 1:5.22+15-2
Severity: important

According to
https://security-tracker.debian.org/tracker/CVE-2015-8865 >, the
file package in Jessie have an open security hole.  The description look
like this:

  The file_check_mem function in funcs.c in file before 5.23, as used in
  the Fileinfo component in PHP before 5.5.34, 5.6.x before 5.6.20, and
  7.x before 7.0.5, mishandles continuation-level jumps, which allows
  context-dependent attackers to cause a denial of service (buffer
  overflow and application crash) or possibly execute arbitrary code via
  a crafted magic file.

The problem was fixed in Wheezy (DLA-460-1), but is not listed as fixed
in Jessie.  Is there problem still around in Jessie?  If not, would you
be willing to upload a update to Jessie?

As the problem is said to be fixed in version 5.23, it is no longer
present in Stretch and Sid.

-- 
Happy hacking
Petter Reinholdtsen

Bug#826931: gitlab: page with diffs (commits) - error 500

[Libor Klepáč]

Package: gitlab
Followup-For: Bug #826931

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hello,
i had to upgrade ruby-gitlab-git to 10.1.2, because gitlab needs method 
"tag_exists".
You cannot push commits with tags without it.

So upstream Gemfile is totally wrong expecting version 10.0

Libor

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

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

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJXYVLNAAoJEPDvjG7Cn0eOL7EP/1EC2CcZrhfubtEMaqQ1NLnL
eVmHSan4qJ6GzhhuIKsrDlPzoGzAkgDSIA9E8Lskp4HRPNLVGu1LwfT8VH6LDRsK
O/JOkHXMihukG8EHILknTTCmrW99laCMDeIxMELRdudbgCXNooRo69TROV4kZ3UQ
y3wzdy41ey/aOvRGxgqU3Z2HugasbQYw4fjuxFktuz6e/GCVpCsMHYXRU59zTQEA
N0jWlrQ+NRGtMHPH/SUMyc0UVSkPa9FqXVa3WmOKa4wXHzY3UV5/UpLwwPeyuAY5
IcqwWeB3IXJi2lqEqq/tU+PbW2uDrJlkyJ75467Nnyu4ScswA35KQa1RyvbxFL7y
kEdmtCC+s4kjd4zLV3ttE1AqYFxLHLuvGemgMYKnOVkStlt+bvr/OWJd7CwMx0e5
dwYJIj9gVNh/93uWYhYliRYQoxY/CWCN2mmg8ZM/rj8FDh/Oxv3TrXyRrF0Ym69V
jAp4MTTcHreC5k+/hu7KlW6WwKMK3fl79Xk4kWUKxVx/co8MprnQJZ7+j7PEolNh
ZPXW9LQ1OpaoLMBngmUvHbKqMmNJG5gbxk79xF+RfEmuUdKvk9JghgmPD2MzEoYD
POuqipSO6omLvwkuJanV2YU+4EVyC09hXgEu45myJz4ZiY9UZh8FB1LyuRa8Esp3
S1HpMe1M/4RX02/QFma5
=JOzJ
-END PGP SIGNATURE-

Bug#821148: Fwd: Re: License for CDAT software

[Alastair McKinstry]

For records.


 Forwarded Message 
Subject:Re: License for CDAT software
Date:   Mon, 13 Jun 2016 11:40:24 -0700
From:   Denis Nadeau 
To: Williams, Dean N. , Alastair McKinstry
, Rogers, Leah L. ,
dr...@llnl.gov 
CC: Taylor, Karl E. 



Hi Alastair,


I should be releasing cmor 3.1 this week for CMIP6 project.  You can
take a loot at the "beta" code here:

https://github.com/PCMDI/cmor/tree/cmor3


I am still working on the documentation and will make sure that the
copyright has been refreshed.

I'll  get the announcement for the 3.1 release.

Regards,
Denis
On 6/13/16 6:34 AM, Williams, Dean N. wrote:
> Dear Alastair:
>
> Both Leah and Bob have left LLNL. Denis is now in charge of the
> development of CMOR. I am surprised to see the 1996 copyright and Bob
> Drach as the author.
>
> In any case, it is okay to use CMOR independent of UV-CDAT. It is
> still under the same BSD open-souruce license agreement.
>
> Best regards,
> Dean 
>
> From: Alastair McKinstry  >
> Date: Monday, June 13, 2016 at 4:25 AM
> To: "Rogers, Leah L." mailto:roger...@llnl.gov>>,
> Dean Williams mailto:william...@llnl.gov>>,
> "dr...@llnl.gov "  >
> Subject: Re: License for CDAT software
>
> Dear Leah,
>
> Some time ago you gave some reassurances (below) on the distribution
> of the CMOR software. Thank you for this.  However two questions have
> arisen that I hope you can clarify.
>
> (1) A user has pointed out certain files included in CMOR have the header:
>
> c  Copyright:   1996, Regents of the University of California
> c   This software may not be distributed to others without
> c   permission of the author.
> c
> c  Author:  Bob Drach, Lawrence Livermore National Laboratory
> c   dr...@llnl.gov
>
> Can you confirm that it is acceptable to distribute these with the
> assurance / caveat given previously?
>
> (2) The libcmor library is also usable independent of CDAT and some
> users have started linking against it in their applications; eg. the
> popular 'cdo' climate data operators utility has experimental
> functionality to to 'cmorization' using the libcmor library.  Unless a
> copy of CDAT is shipped with 'cdo' this would technically be a breach
> of the licensing terms, which is unlikely to be what anyone intends.
>
> Would it be possible then to state that (1) is covered by the previous
> agreement  and that (2) shipping a copy of CDAT with libcmor is not
> required?
>
> Best regards
> Alastair McKinstry
>
>
> On 04/06/2010 00:40, Rogers, Leah L. wrote:
>>
>> Dear Alistair,
>>
>> Dean tells me that you also are interested in distributing CMOR as
>> well as CDAT.  CMOR is approved for unrestricted release which is not
>> an official open source license, but from our institution’s
>> perspective we are supportive of it being included in your Debian
>> distribution along with CDAT. I will be happy to work with you to
>> achieve this. Feel free to call me at 925 422 3538 if you would like
>> to discuss it by phone. All the best, Leah
>>
>>  
>>
>> *From:*Dean N. Williams [mailto:william...@llnl.gov]
>> *Sent:* Saturday, May 29, 2010 6:50 PM
>> *To:* Alastair McKinstry
>> *Cc:* Rogers, Leah L.
>> *Subject:* Re: License for CDAT software
>>
>>  
>>
>> I'll have Leah Rogers get back to you after next week.
>>
>>  
>>
>> Best regards,
>>
>> Dean
>>
>>  
>>
>> On May 29, 2010, at 1:25 PM, Alastair McKinstry wrote:
>>
>>
>>
>> Hi Dean,
>>
>> Thanks for replying so quickly! I would be very happy if it can be
>> confirmed that CDAT is available
>> under the BSD license. From:
>> *http://*www2-pcmdi.llnl.gov/cdat/docs/cdat-license/?searchterm=None
>> *I was afraid that the "No commercialisation" clause would conflict
>> with the "Free distribution" clause
>> of the Debian (and Ubuntu) Free software guidelines:
>> http://*www.*debian.org/social_contract#guidelines
>>
>> If an appropriate legal person at LLNL can say they are happy that
>> CDAT is distributed with
>> Debian (and derivatives) as per the DFSG pointed to, then thats great
>>
>> Best regards
>> Alastair
>>
>> On 2010-05-29 19:13, Dean N. Williams wrote:
>>
>> Hi Alastair,
>>
>>  
>>
>>  CDAT is BSD licensed, so I don't understand your question. I cc'ed
>> our LLNL legal person to confirm this. 
>>
>>  
>>
>>  Also, I would like to thank you for including CDAT in the
>> distribution of Debian, and Ubuntu...
>>
>>  
>>
>> Best regards,
>>
>>  Dean
>>
>>  
>>
>> On May 29, 2010, at 6:13 AM, Alastair McKinstry wrote:
>>
>>

Bug#827376: init-system-helpers: invoke-rc.d unconditionally uses /sbin/runlevel without depending on a package providing it

[Michael Biebl]

Hi Andreas

Am 15.06.2016 um 15:02 schrieb Andreas Beckmann:
> I just noticed this in a piuparts log (#827374):
> 
>   /usr/sbin/invoke-rc.d: 1: /usr/sbin/invoke-rc.d: /sbin/runlevel: not found
>   invoke-rc.d: could not determine current runlevel
>   invoke-rc.d: policy-rc.d denied execution of reload.
> 
> /sbin/runlevel is provided by several packages:
> 
> https://packages.debian.org/search?mode=path&suite=sid§ion=all&arch=any&searchon=contents&keywords=sbin%2Frunlevel
> 
> so I'm not sure what the correct Depends would be ...

We recently changed "init" to no longer be essential. This means
/sbin/runlevel is no longer guaranteed to be around.
In case of invoke-rc.d it's probably best to have a sensible fallback if
runlevel can't be found.

That said, we probably have more places where those binaries provided by
systemd-sysv (halt, telinit, runlevel etc) are used. So there might be
some more fallout from that change.

Any idea how we can users of
https://packages.debian.org/sid/alpha/systemd-sysv/filelist
?





-- 
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#827378: open-infrastructure-container-tools: missing Depends: lsb-release

[Andreas Beckmann]

Package: open-infrastructure-container-tools
Version: 20160615-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

  Selecting previously unselected package open-infrastructure-container-tools.
  (Reading database ... 
(Reading database ... 7482 files and directories currently installed.)
  Preparing to unpack 
.../open-infrastructure-container-tools_20160615-1_all.deb ...
  Unpacking open-infrastructure-container-tools (20160615-1) ...
  Setting up open-infrastructure-container-tools (20160615-1) ...
  dpkg: error processing package open-infrastructure-container-tools 
(--configure):
   subprocess installed post-installation script returned error exit status 127
  Errors were encountered while processing:
   open-infrastructure-container-tools


Debugging this a bit further, I found that the .config script dies here:

DISTRIBUTOR="$(lsb_release -is 2>/dev/null)"

since lsb_release is not found.


cheers,

Andreas


open-infrastructure-container-tools_20160615-1.log.gz
Description: application/gzip

Bug#825809: unclutter alternatives

[Ian Jackson]

Axel Beckert writes ("Re: unclutter alternatives"):
> So I'm actually very glad that someone else also has interest in
> packaging unclutter-xfixes.

I'm a user of unclutter.  I run it with `-noevents'.  I have no idea
whether the new approach is going to be a good replacement but I guess
it probably is.

I do wonder why this needed a whole new fresh rewrite, with a new
name, and everything.  Oh well.

> 1) Package unclutter-xfixes with an unclutter transitional package and
>upload to experimental first. That way, people who use unclutter
>can test unclutter-xfixes to see if anything needs to be fixed
>there to make unclutter-xfixes a drop-in replacement for unclutter.

This ia a good plan.

Thanks,
Ian.

Bug#827379: nailgun-common: unowned directory after purge: /var/log/nailgun/

[Andreas Beckmann]

Package: nailgun-common
Version: 9.0+dfsg1-3
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package left unowned
directories on the system after purge, which is a violation of
policy 6.8:

https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails

Filing this as important as having a piuparts clean archive is a release
goal since lenny.

The maintainer scripts create (and later remove) a file in that
directory. Manual directory removal may be not appropriate as this
directory is shared between several packages.

If the package would ship this as an empty directory, dpkg would take
care of the creation and removal (if it's empty).

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

2m18.8s ERROR: FAIL: Package purging left files on system:
  /var/log/nailgun/  not owned


cheers,

Andreas


nailgun-common_9.0+dfsg1-3.log.gz
Description: application/gzip

Bug#827376: init-system-helpers: invoke-rc.d unconditionally uses /sbin/runlevel without depending on a package providing it

[Michael Biebl]

Am 15.06.2016 um 15:15 schrieb Michael Biebl:

> Any idea how we can users of
> https://packages.debian.org/sid/alpha/systemd-sysv/filelist

... how we can *identify* users of ...

-- 
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#827323: linux: Regression v4.5 -> v4.6: system freeze after suspend/resume due to iAMT watchdog

[Usyskin, Alexander]

Hi

It may be that fdd9b8655933 uncovered the bug in iTCO_wdt because it actually 
removes iAMT watchdog and new
implementation does not creates one for not provisioned ME.
So before that patch there was two watchdog devices and systemd maybe worked 
with iAMT one.
After that patch only one watchdog exists in the system - iTCO and system works 
with it.


Thanks
--
Sasha



-Original Message-
From: Sebastian Reichel [mailto:s...@debian.org] 
Sent: Wednesday, June 15, 2016 14:30
To: Usyskin, Alexander 
Cc: 827...@bugs.debian.org
Subject: Re: Bug#827323: linux: Regression v4.5 -> v4.6: system freeze after 
suspend/resume due to iAMT watchdog

Hi,

On Wed, Jun 15, 2016 at 08:00:30AM +, Usyskin, Alexander wrote:
> I assume that "This happened with 4.6, but not with v4.5.", yes?

Yes, sorry.

> Do you have vPro system?

Yes, my CPU is i7-5600U.

> Have you provisioned your ME device?

No, I don't think so.

> If not, the iAMT watchdog should not be exposed to user-space and 
> should not affect systemd. Do you have /dev/watchdog* with identity 
> "iamt_wdt" at you system?

# ls /sys/class/watchdog
watchdog0
# wd_identify
iTCO_wdt

That's also, what was used by systemd:

Jun 15 01:24:49 earth kernel: iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11 
Jun 15 01:24:49 earth kernel: iTCO_wdt: Found a Wildcat Point_LP TCO device 
(Version=2, TCOBASE=0x1860) Jun 15 01:24:49 earth kernel: iTCO_wdt: 
initialized. heartbeat=30 sec (nowayout=0) Jun 15 01:24:49 earth systemd[1]: 
Hardware watchdog 'iTCO_wdt', version 0 Jun 15 01:24:49 earth systemd[1]: Set 
hardware watchdog to 30s.

I have checked with wd_keepalive and I have a few more observations:

 * The freeze did not appear when wd_keepalive is used instead of systemd
 * The freeze appears, if I kill wd_keepalive, so the freeze itself seems
   to be a bug in the iTCO_wdt driver/hardware.

So looks like fdd9b8655933 somehow results in systemd being too slow to ping 
the watchdog in time.

-- Sebastian

> -Original Message-
> From: Sebastian Reichel [mailto:s...@debian.org]
> Sent: Wednesday, June 15, 2016 02:44
> To: Debian Bug Tracking System 
> Subject: Bug#827323: linux: Regression v4.5 -> v4.6: system freeze 
> after suspend/resume due to iAMT watchdog
> 
> Source: linux
> Version: 4.5.5-1
> Severity: normal
> 
> Hi,
> 
> My Lenovo Thinkpad X250 freezes a couple of seconds after resuming 
> from suspend. This happened with 4.5, but not with v4.6. I bisected 
> the problem using mainline kernel with Debian config to the following 
> commit:
> 
> sre@earth ~/src/linux (git)-[fdd9b86...|bisect] % git bisect bad 
> fdd9b8655933c3eb3154fe1ed351c17b654258bd is the first bad commit 
> commit fdd9b8655933c3eb3154fe1ed351c17b654258bd
> Author: Alexander Usyskin 
> Date:   Fri Jan 8 00:49:21 2016 +0200
> 
> mei: wd: drop the watchdog code from the core mei driver
> 
> Instead of integrating the iAMT watchdog in the mei core driver
> we will create a watchdog device on the mei client bus and
> create a driver for it.
> 
> This patch removes the watchdog code from the mei core driver.
> 
> Signed-off-by: Alexander Usyskin 
> Signed-off-by: Tomas Winkler 
> Signed-off-by: Greg Kroah-Hartman 
> 
> My system was configured to use the watchdog via "RuntimeWatchdogSec=30"
> in "/etc/systemd/system.conf". After disabling the feature no system 
> freeze happens after suspend/resume cycle.
> 
> -- Sebastian
> 
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers testing
>   APT policy: (1000, 'testing'), (500, 'unstable'), (200, 
> 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386, armhf
> 
> Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> -
> Intel Israel (74) Limited
> 
> This e-mail and any attachments may contain confidential material for 
> the sole use of the intended recipient(s). Any review or distribution 
> by others is strictly prohibited. If you are not the intended 
> recipient, please contact the sender and delete all copies.
> 
-
Intel Israel (74) Limited

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

Bug#825672: Issues with libacr38 and gpg

[Giovanni Mascellani]

Hi.

Il 15/06/2016 09:45, Laurent Bigonville ha scritto:
> Hi,
> 
> Apparently you both have some issues with the last upload of libacr38
> and gpg.
> 
> I don't think that upstream is really maintaining this driver anymore,
> however it seems they are maintaining (and even in debian!) libacsccid1
> instead.

Yes, my problems disappeared after removing libacs38 and libccid1 and
installing libacsccid1. Thanks for the hints!

> Could you please give a try to this other driver and see if it's working
> better for you?
> 
> If it's the case I'm thinking about asking to RM this package from the
> archive.

Yes, to me you can RM the package and close the bug.

Thanks, Giovanni.
-- 
Giovanni Mascellani 
PhD Student - Scuola Normale Superiore, Pisa, Italy

http://poisson.phc.unipi.it/~mascellani



signature.asc
Description: OpenPGP digital signature

Bug#814862: fix for qt4 Conflicts

[Gianfranco Costamagna]

control: tags -1 pending


Hi Ian!
>Gianfranco, can you take a look at this in alioth git and upload the 

>package if you are happy?


I added a patch to fix a build failure, rebased the changelog, tested, signed
and uploaded :)

thanks!

G.

Bug#802916: python-coverage: post-build tests fail: “coverage.misc.CoverageException: No data to report.”

[Ben Finney]

On 14-Jun-2016, Emilio Pozuelo Monfort wrote:
> So can you update coverage to 4.1 and hopefully fix #802801 with
> that? Or is there still blocking the update?

The last blocker of bug#799629 was resolved a few days ago, hooray! I
am now working on the new release.

-- 
 \  “The best mind-altering drug is truth.” —Jane Wagner, via Lily |
  `\Tomlin |
_o__)  |
Ben Finney 


signature.asc
Description: PGP signature