Bug#844788: hibernate: suspends ok but hangs on restore after decompressing with stretch kernel on macbook pro

[Andrew Worsley]

Just tested out the latest testing linux-image-amd64:amd64 4.8+76 with
exactly the same results.

Perhaps this is a kernel bug?

Bug#844018: libcurl3: Building with OpenSSL 1.1 breaks packages using both OpenSSL 1.0 and curl

[Stepan Golosunov]

22.11.2016 в 22:57:30 +0200 Adrian Bunk написал:
> 23:14 < bunk> Q_: If you come up with a better patch than mine in #844018, 
>   please post to that bug. I know that my patch is not pretty, 
> but 
>   I did not find any better short-term solution.

Search for CURLOPT_SSL_CTX_FUNCTION on codesearch.debian.net produces
the following list of potentially affected packages:
cargo
chromium-browser
cmake
criticalmass
curl
curlpp
firefox
firefox-esr
fpc
hhvm
icedove
lastpass-cli
libapache2-mod-auth-cas
libwww-curl-perl
lua-curl
netcdf
netsurf
openjfx
r-cran-curl
r-cran-rcurl
ruby-curb
slcurl
sx
tclcurl
wpa
xmltooling
zurl

So the the alternative to you patch looks like:

fixing #828564 (fixed-upstream, new upstream version available),
fixing #828608 or removing xmltooling out of testing,
checking whether last apache2 upload fixed #844799,
fixing or ignoring #828259 (not in testing, fixed upstream version
available),
fixing #828371 (untested patch available) or removing lastpass-cli,
removing 3 characters from zurl's debian/control,
binnmu-ing affected packages that still depend on libssl1.0.2,
no need to ensure that applications (even if they are linked with
libcurl3 indirectly) are linked with the same libssl as libcurl3
(unlike with the patch),
more compatibility with applications from jessie than with the patch.

Bug#844922: [Pkg-javascript-devel] Bug#844922: Node-string-decoder

[Jérémy Lal]

2016-11-23 8:53 GMT+01:00 Ross Gammon :
> Hi,
>
> This node module was originally packaged as it was a dependency of something
> (I can't remember).
>
> If there is nothing depending on it, we should probably remove it from the
> archive. The string-decoder function from the core nodejs should be used
> instead (patching the module that needs it if required). Node-string-decoder
> is mainly used when a nodejs project wants to stick to an old version of
> this function.
>
> Regards,

All right, can you fill the ftp.debian.org RM request please ?

Jérémy

Bug#844856: flightcrew: FTBFS: CheckSymbolExists.cxx:8:19: error: 'Q_WS_WIN' was not declared in this scope

[Gianfranco Costamagna]

control: tags -1 patch

> Relevant part (hopefully):
> > /usr/bin/c++-I/usr/include/qt4  -g -O2 
> > -fdebug-prefix-map=/<>/flightcrew-0.7.2+dfsg=. 
> > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> > -D_FORTIFY_SOURCE=2-o CMakeFiles/cmTC_aec35.dir/CheckSymbolExists.cxx.o 
> > -c 
> > /<>/flightcrew-0.7.2+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.cxx
> > /<>/flightcrew-0.7.2+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.cxx:
> >  In function 'int main(int, char**)':
> > /<>/flightcrew-0.7.2+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.cxx:8:19:
> >  error: 'Q_WS_WIN' was not declared in this scope
> >return ((int*)(&Q_WS_WIN))[argc];
> >^~~~
> > CMakeFiles/cmTC_aec35.dir/build.make:65: recipe for target 
> > 'CMakeFiles/cmTC_aec35.dir/CheckSymbolExists.cxx.o' failed
> > make[3]: *** [CMakeFiles/cmTC_aec35.dir/CheckSymbolExists.cxx.o] Error 1
> 

it wasn't the relevant part :p

CMake Error at src/FlightCrew/tests/CMakeLists.txt:67 (add_library):
  Cannot find source file:

/usr/src/gtest/src/gtest-all.cc

  Tried extensions .c .C .c++ .cc .cpp .cxx .m .M .mm .h .hh .h++ .hm .hpp
  .hxx .in .txx


CMake Error: Cannot determine link language for target "GOOGLE_MOCK_LIB".
CMake Error: CMake can not determine linker language for target: GOOGLE_MOCK_LIB

this is the correct one.

Adding libgtest-dev to build-dependencies solves the issue and brings that file 
back.
(this is probably something due to the recent introduction of the new 
src:googletest package.

cheers,

G.



signature.asc
Description: OpenPGP digital signature

Bug#811907: music: FTBFS with GCC 6: invalid conversion

[Graham Inggs]

Control: tags -1 patch

The patch below fixes the FTBFS with GCC 6.


--- a/src/connectivity.cc
+++ b/src/connectivity.cc
@@ -89,7 +89,7 @@
 std::map::iterator info
   = connectivityMap.find (portName);
 if (info == connectivityMap.end ())
-  return NO_CONNECTIVITY;
+  return (ConnectivityInfo*)NO_CONNECTIVITY;
 else
   return &connections_[info->second];
   }

Bug#845419: RM: zynaddsubfx [armel] -- ROM; uses std::future

[Sebastian Ramacher]

Package: ftp.debian.org
Severity: normal

Please remove zynaddsubfx from armel. It uses std::future which is known to be
broken there.

Regards
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#842291: notmuch processes frequently stuck in select()

[David Bremner]

Brian May  writes:
> strace shows notmuch looping in select.
>
> select(10, [9], [], NULL, {1, 0})   = 0 (Timeout)
> select(10, [9], [], NULL, {1, 0})   = 0 (Timeout)
> select(10, [9], [], NULL, {1, 0})   = 0 (Timeout)
> select(10, [9], [], NULL, {1, 0})   = 0 (Timeout)
> select(10, [9], [], NULL, {1, 0})   = 0 (Timeout)
> select(10, [9], [], NULL, {1, 0})   = 0 (Timeout)
> select(10, [9], [], NULL, {1, 0})   = 0 (Timeout)
> select(10, [9], [], NULL, {1, 0})   = 0 (Timeout)
> select(10, [9], [], NULL, {1, 0})   = 0 (Timeout)
> select(10, [9], [], NULL, {1, 0})   = 0 (Timeout)
> select(10, [9], [], NULL, {1, 0})   = 0 (Timeout)
> select(10, [9], [], NULL, {1, 0})   = 0 (Timeout)
> select(10, [9], [], NULL, {1, 0})   = 0 (Timeout)
> select(10, [9], [], NULL, {1, 0})   = 0 (Timeout)
> select(10, [9], [], NULL, {1, 0})   = 0 (Timeout)
> etc
>

a backtrace would be helpful.

d

Bug#836722: [Pkg-javascript-devel] Bug#836722: Bug#836722: needs yargs as a dependency

[Jonas Smedegaard]

Quoting Pirate Praveen (2016-11-23 08:37:39)
> On Tuesday 22 November 2016 10:53 PM, Jonas Smedegaard wrote:
>> Ah, I understand you now: You present breakage when using code not in 
>> Debian.  Quite confusing - please *always* mention explicitly in 
>> bugports when using non-Debian packages!
>
> Sorry, that was mostly meant a self note (I should have explicitly 
> mentioned it).
>
> I ran uscan, imported the new upstream release, built the package and
> got the error when running it.

Makes sense (now that I what sense to make of it) :-)


>> I only asked whether or not it was related - I did not imply it was 
>> not.
>>
>> I was genuinely confused by your terse writing style.
>>
>> Another point of confusion was that a different topic was used in the 
>> email than in original bugreport topic.  I was unaware (until digging 
>> into archive, when in above latest post you still didn't elaborate 
>> much) that was a wishlist bug, so assumed that your presenting code 
>> failing was to be treated seriously.
>>
>>
>> With the best of intentions,
>
> Sorry about doubting your intentions, but that came as a result of so 
> much comments on -devel about packaging so many tiny node modules. 
> Since you already commented before to start with packaging yargs I 
> thought it would be enough.

I can understand how might have seen the clues as being "right around 
the corner".

Keepup the good work,

 - Jonas

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

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

Bug#845085: docker.io: Some commands do not work on some images with kernel version 4.8

[Pitxyoki]

Hi Ian,

Thanks for your attention to this.

I just tried out the following combinations:
Linux Kernel v4.7:
vsyscall=emulate
vsyscall=native
vsyscall=none

Linux Kernel v4.8
vsyscall=emulate
vsyscall=native
vsyscall=none

The commands work every time, except when vsyscall=none is set, for
both kernel versions. With that, docker returns error code 139.


Regards,

On 22/11/2016, Ian Campbell  wrote:
> On Tue, 2016-11-22 at 12:17 +, Ian Campbell wrote:
>> On Sun, 2016-11-20 at 09:57 +, Luís Picciochi Oliveira wrote:
>> >
>> > While using Docker, some commands on some images stopped working.
>> > For
>> > example:
>> >
>> >   $ docker run -it --rm centos:centos6  bash
>> > This does not work. It always returns with code 139:
>> >
>> >   $ echo $?
>> > 139
>>
>> FYI something similar (but with Wheezy container) was reported
>> in https
>> ://github.com/docker/docker/issues/28705 too.
>
> Please could you try the command line options described in https://gith
> ub.com/docker/docker/issues/28705#issuecomment-262226229
>
> Thanks,
> Ian
>


-- 
Luís Picciochi Oliveira
Unimos - Associação Tecnológica

Bug#780543: upstream status

[Alexandre Rossi]

It seems this is moving forward upstream.

https://github.com/oetiker/rrdtool-1.x/pull/755

Alex

Bug#845420: can't add IRC nicks to a contact, Jabber is a trademark

[Daniel Pocock]

Package: evolution
Version: 3.12.9~git20141130.241663-1+b1
Severity: serious

Editing a contact in Evolution, there is a section on the first tab,
"Instant Messaging" where it allows people to select options like "MSN"
or "Skype".

There is no apparent way to specify other contact types here.

Given that Debian and GNOME have a strong emphasis on using IRC, it
seems silly that IRC is not one of the options.

Jabber[1] is a Cisco trademark, this option could become "XMPP" or maybe
"XMPP (Jabber^TM)"

It would also be very desirable to permit SIP and Ring[2] addresses here
too.



1. https://xmpp.org/about/xsf/jabber-trademark
2. https://ring.cx/en/documentation/faq#node-88

Bug#844018: libcurl3: Building with OpenSSL 1.1 breaks packages using both OpenSSL 1.0 and curl

[Adrian Bunk]

On Wed, Nov 23, 2016 at 11:59:16AM +0400, Stepan Golosunov wrote:
> 22.11.2016 в 22:57:30 +0200 Adrian Bunk написал:
> > 23:14 < bunk> Q_: If you come up with a better patch than mine in #844018, 
> >   please post to that bug. I know that my patch is not pretty, 
> > but 
> >   I did not find any better short-term solution.
> 
> Search for CURLOPT_SSL_CTX_FUNCTION on codesearch.debian.net produces
> the following list of potentially affected packages:
> cargo
> chromium-browser
> cmake
> criticalmass
> curl
> curlpp
> firefox
> firefox-esr
> fpc
> hhvm
> icedove
> lastpass-cli
> libapache2-mod-auth-cas
> libwww-curl-perl
> lua-curl
> netcdf
> netsurf
> openjfx
> r-cran-curl
> r-cran-rcurl
> ruby-curb
> slcurl
> sx
> tclcurl
> wpa
> xmltooling
> zurl
> 
> So the the alternative to you patch looks like:
>...
> fixing #828608 or removing xmltooling out of testing,
>...

"removing xmltooling out of testing" is not an option.

Either *all* packages in this cluster get fixes to work with 1.1,
or the whole cluster must stay at 1.0.2 in stretch.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#844788: Just also tried the latest unstable and the latest experimental with the same results.

[Andrew Worsley]

linux-image-4.8.0-1-amd64-unsigned_4.8.7-1_amd64
.deb

and

linux-image-4.9.0-rc5-amd64-unsigned_4.9~rc5-1~e
xp1_amd64.deb

Bug#845421: ITP: node-grunt-contrib-concat -- Concatenate files

[Pirate Praveen]

Package: wnpp
Severity: wishlist
Owner: Pirate Praveen 
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name: node-grunt-contrib-concat
  Version : 1.0.1
  Upstream Author : Grunt Team (http://gruntjs.com/)
* URL : https://github.com/gruntjs/grunt-contrib-concat#readme
* License : Expat
  Programming Lang: JavaScript
  Description : Concatenate files



signature.asc
Description: OpenPGP digital signature

Bug#845422: [PATCH] Please add BCM2835 MMC driver for Raspberry Pi 3

[Michael Stapelberg]

Source: linux
Severity: wishlist
Tags: patch

Thank you for your work on maintaining the Linux kernel in Debian, I really
appreciate it!

I am interested in running Debian on the Raspberry Pi 3.

As per https://github.com/anholt/linux/wiki/Raspberry-Pi-3, the mainline Linux
kernel in version 4.8 includes support for the Raspberry Pi 3, so we are in
pretty good shape already.

However, when trying to boot linux-image-4.8.0-1-arm64 version 4.8.5-1, I
noticed that the kernel can’t find any block devices (and hence no root file
system). This is because the bcm2835-sdhost MMC driver has not actually made it
into Linux 4.8; it is still under review:
https://www.spinics.net/lists/arm-kernel/msg513433.html

The driver is based on the work by Phil Elwell (from Raspberry Pi Ltd.), shipped
in https://github.com/raspberrypi/linux, i.e. used by Raspbian and other
distributions. Eric Anholt and Gerd Hoffmann are working upstreaming the driver.

In the meantime, Gerd Hoffmann has included the current patches in his
Raspberry Pi Fedora images; the source of the kernel RPMs can be found at
https://www.kraxel.org/repos/rpi2/kernel-main/kernel-main-4.9-0.4.src.rpm

I have applied these patches as-is to the Debian linux 4.8.5-1 package and can
confirm that the resulting kernel boots on the Raspberry Pi 3 and seems to work
perfectly fine.

Therefore, could you please:

  1. Add the attached patch series to the linux-image-4.8.0-1-arm64 build.
  2. Enable the CONFIG_MMC_BCM2835=y option.

Let me know whether you’d prefer me to squash these patches into a single patch
file. I chose to attach the patch series as-is because that should make it
easier to compare it with upstream and update it (should that become necessary).

It would be brilliant to get this in before the freeze, so that people can soon
run Debian stable on their Raspberry Pi 3s and get security updates :).

Thank you so much!

P.S.: In case you are interested, I am using the following parameters in
config.txt on the FAT32 boot partition to make the Raspberry Pi bootloader load
my kernel:

# Switch the CPU from ARMv7 into ARMv8 (aarch64) mode
arm_control=0x200

# From /usr/lib/linux-image-4.8.0-1-arm64/broadcom/bcm2837-rpi-3-b.dtb
device_tree=bcm2837-rpi-3-b.dtb

kernel=vmlinuz-4.8.0-1-arm64

# For details on the initramfs directive, see
# https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=10532
initramfs initrd.img-4.8.0-1-arm64

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

Kernel: Linux 4.6.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
>From 48ec9c44ea4d650d0d673c3a9df918152007e8e7 Mon Sep 17 00:00:00 2001
From: Eric Anholt 
Date: Mon, 22 Feb 2016 12:44:55 -0800
Subject: [PATCH 23/43] mmc: bcm2835-sdhost: Add new driver for the internal SD
 controller.

The 2835 has two SD controllers: The Arasan SDHCI controller that we
currently use, and a custom SD controller.  The custom one runs faster

The code was originally written by Phil Elwell in the downstream
Rasbperry Pi tree, and I did a major cleanup on it (+319, -707 lines
out of the original 2055) for inclusion.

Signed-off-by: Eric Anholt 
---
 drivers/mmc/host/Kconfig  |9 +
 drivers/mmc/host/Makefile |1 +
 drivers/mmc/host/bcm2835-sdhost.c | 1666 +
 3 files changed, 1676 insertions(+)
 create mode 100644 drivers/mmc/host/bcm2835-sdhost.c

diff --git a/drivers/mmc/host/Kconfig b/drivers/mmc/host/Kconfig
index 5274f50..e928160 100644
--- a/drivers/mmc/host/Kconfig
+++ b/drivers/mmc/host/Kconfig
@@ -769,6 +769,15 @@ config MMC_TOSHIBA_PCI
 	depends on PCI
 	help
 
+config MMC_BCM2835_SDHOST
+	tristate "platform support for the BCM2835 SDHOST MMC Controller"
+	depends on ARCH_BCM2835 || COMPILE_TEST
+	help
+	  This selects the BCM2835 SDHOST MMC controller. If you have a BCM2835
+	  platform with SD or MMC devices, say Y or M here.
+
+	  If unsure, say N.
+
 config MMC_MTK
 	tristate "MediaTek SD/MMC Card Interface support"
 	depends on HAS_DMA
diff --git a/drivers/mmc/host/Makefile b/drivers/mmc/host/Makefile
index e2bdaaf4..2fb3f36 100644
--- a/drivers/mmc/host/Makefile
+++ b/drivers/mmc/host/Makefile
@@ -57,6 +57,7 @@ obj-$(CONFIG_MMC_MOXART)	+= moxart-mmc.o
 obj-$(CONFIG_MMC_SUNXI)		+= sunxi-mmc.o
 obj-$(CONFIG_MMC_USDHI6ROL0)	+= usdhi6rol0.o
 obj-$(CONFIG_MMC_TOSHIBA_PCI)	+= toshsd.o
+obj-$(CONFIG_MMC_BCM2835_SDHOST)	+= bcm2835-sdhost.o
 
 obj-$(CONFIG_MMC_REALTEK_PCI)	+= rtsx_pci_sdmmc.o
 obj-$(CONFIG_MMC_REALTEK_USB)	+= rtsx_usb_sdmmc.o
diff --git a/drivers/mmc/host/bcm2835-sdhost.c b/drivers/mmc/host/bcm2835-sdhost.c
new file mode 100644
index 000..cafe6ad
--- /dev/null
+++ b/drivers/mmc/host/bcm2835-sdhost.c
@@ -0,0 +1,1666 @@
+/*
+ * BCM2835 SD host driver.
+ *
+ * Aut

Bug#845302: systemd: 232-6:Failed to boot, makes kernel panic when starting /sbin/init.

[Michael Biebl]

Am 23.11.2016 um 04:20 schrieb Michael Biebl:
> Fwiw, I suspect your problem might be, that / and /usr are on different
> drives. initramfs-tools is not event based, so maybe sde (your HDD) is
> not available yet when it attempts to mount /usr.

Assuming this is the case, initramfs-tools should probably retry a few
times to mount /usr, similar to how it handles nfs_mount_root() as in
https://anonscm.debian.org/cgit/kernel/initramfs-tools.git/tree/scripts/nfs#n77


It would also be interesting to know, if your problem is solved by
installing dracut, which will replace initramfs-tools with an event
based initramfs.


-- 
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#842291: notmuch processes frequently stuck in select()

[David Bremner]

David Bremner  writes:

> Brian May  writes:
>> strace shows notmuch looping in select.
>>
>> select(10, [9], [], NULL, {1, 0})   = 0 (Timeout)
>> select(10, [9], [], NULL, {1, 0})   = 0 (Timeout)
>> select(10, [9], [], NULL, {1, 0})   = 0 (Timeout)
>> select(10, [9], [], NULL, {1, 0})   = 0 (Timeout)
>> etc
>>
>
> a backtrace would be helpful.
>
> d

Nevermind, I managed to download the list archive for debian-devel and
replicate the bug.

The bug seems to be related to smime signature verification. After
adding the attached mail message (and running notmuch-new), to replicate
the hang it suffices to run

% notmuch show --decrypt id:20161116t143809.ga.21721.s...@fsing.rootsland.net  

As far as workarounds, turning off decryption / signature verification
should allow you to at least view the thread.



20161116T143809.GA.21721.stse@fsing.rootsland.net.eml:2,
Description: Binary data

Bug#845358: cupt: please switch to libreadline7

[Sven Joachim]

Control: tags -1 + patch

On 2016-11-22 20:10 +0100, Sven Joachim wrote:

> Package: cupt
> Version: 2.9.8
>
> Your package has a hardcoded Suggests on libreadline6 which is scheduled
> for removal (see #840397), please switch to libreadline7.

Attached is a patch against git master which does that.  Of course, if
you want to support systems which don't have the latest readline…

> Would it not be better to just link against libreadline, rather than
> playing dlopen tricks which need to be adjusted on every readline soname
> bump?

…this would be better.

Cheers,
   Sven

>From 2007f9f7ce27bb19d4268f98a09620fc6bc69d4d Mon Sep 17 00:00:00 2001
From: Sven Joachim 
Date: Wed, 23 Nov 2016 09:33:24 +0100
Subject: [PATCH] Switch to libreadline7

---
 cpp/console/handlers/shell.cpp | 4 ++--
 debian/control | 6 +++---
 doc/tutorial.t2t   | 4 ++--
 po/da.po   | 4 ++--
 po/de.po   | 4 ++--
 po/fr.po   | 4 ++--
 po/pl.po   | 4 ++--
 po/sk.po   | 4 ++--
 8 files changed, 17 insertions(+), 17 deletions(-)

diff --git a/cpp/console/handlers/shell.cpp b/cpp/console/handlers/shell.cpp
index 29c64b3..15500ec 100644
--- a/cpp/console/handlers/shell.cpp
+++ b/cpp/console/handlers/shell.cpp
@@ -91,10 +91,10 @@ class Readline
 
 	static void init()
 	{
-		auto handle = dlopen("libreadline.so.6", RTLD_NOW);
+		auto handle = dlopen("libreadline.so.7", RTLD_NOW);
 		if (!handle)
 		{
-			warn2(__("unable to dynamically find libreadline.so.6: dlopen: %s"), dlerror());
+			warn2(__("unable to dynamically find libreadline.so.7: dlopen: %s"), dlerror());
 			return;
 		}
 
diff --git a/debian/control b/debian/control
index 12a39ee..760733f 100644
--- a/debian/control
+++ b/debian/control
@@ -11,7 +11,7 @@ Build-Depends:
 # runtime libraries
   libboost-program-options-dev (>= 1.42),
   libboost-dev (>= 1.42),
-  libreadline6-dev,
+  libreadline-dev,
   libcurl4-gnutls-dev (>= 7.19.4),
   libgcrypt11-dev,
 # documentation
@@ -101,7 +101,7 @@ Package: cupt
 Architecture: any
 Depends: ${misc:Depends}, ${shlibs:Depends}, libcupt4-1 (>= ${binary:Version})
 Breaks: daptup (<< 0.12.2~)
-Suggests: sensible-utils, libreadline6
+Suggests: sensible-utils, libreadline7
 Description: flexible package manager -- console interface
  This package provides a console interface to Cupt library, which implements
  high-level package manager for Debian and derivatives. Cupt is written with
@@ -122,7 +122,7 @@ Description: flexible package manager -- console interface
   - support of LZMA-compressed indexes;
   - source versions synchronization;
   - 'shell' subcommand (to get command history, search etc. working, install
-the package 'libreadline6');
+the package 'libreadline7');
   - integration with debdelta (to get it, install the package 'debdelta');
   - system snapshots (needs packages 'dpkg-dev' and 'dpkg-repack').
  .
diff --git a/doc/tutorial.t2t b/doc/tutorial.t2t
index 0eb869f..4581384 100644
--- a/doc/tutorial.t2t
+++ b/doc/tutorial.t2t
@@ -723,10 +723,10 @@ Install the package ``lightspark``, remove the packae ``gnash``, and make sure t
 Install the package ``sieve-connect``, upgrade or remove the package ``iceweasel``
 if it is installed and has the version lower than ``3.5.20``.
 
-- ``cupt install libv4l-0 cupt --iii libreadline6 vlc*``
+- ``cupt install libv4l-0 cupt --iii libreadline7 vlc*``
 
 Install packages ``libv4l-0`` and ``cupt``, install the preferred version of
-``libreadline6`` if it's installed already, install the preferred versions of
+``libreadline7`` if it's installed already, install the preferred versions of
 packages which names start with ``vlc`` and which are installed already .
 
 - ``cupt remove youtube-dl --install clive --satisfy "iceweasel (>= 4)" --purge cvs subversion --install git --unsatisfy "xinput (<< 1.5)"``
diff --git a/po/da.po b/po/da.po
index bf9b4cc..e188ff5 100644
--- a/po/da.po
+++ b/po/da.po
@@ -765,8 +765,8 @@ msgstr "ugyldigt regulært udtryk »%s«"
 
 #: console/handlers/shell.cpp:98
 #, c-format
-msgid "unable to dynamically find libreadline.so.6: dlopen: %s"
-msgstr "kan ikke dynamsik finde libreadline.so.6: dlopen: %s"
+msgid "unable to dynamically find libreadline.so.7: dlopen: %s"
+msgstr "kan ikke dynamsik finde libreadline.so.7: dlopen: %s"
 
 #: console/handlers/shell.cpp:105 console/handlers/shell.cpp:111
 #, c-format
diff --git a/po/de.po b/po/de.po
index 7446c33..b8658b1 100644
--- a/po/de.po
+++ b/po/de.po
@@ -778,8 +778,8 @@ msgstr "ungültiger regulärer Ausdruck »%s«"
 
 #: console/handlers/shell.cpp:98
 #, c-format
-msgid "unable to dynamically find libreadline.so.6: dlopen: %s"
-msgstr "libreadline.so.6 kann nicht dynamisch gefunden werden: dlopen: %s"
+msgid "unable to dynamically find libreadline.so.7: dlopen: %s"
+msgstr "libreadline.so.7 kann nicht dynamisch gefunden werden: dlopen: %s"
 
 #: console/handlers/shell.cpp:105 console/handlers

Bug#845401: debian-installer: auto=true not working

[Андрей Ярков]

> A series of short
> options for the kernel commandline, see its documentation. If you set
> them, it will run without asking anything.

I'm aware of those, thank you. But the point is that "auto=true" (or just 
"auto")
parameter was conceived just to avoid putting locale and keyboard
configuration to kernel boot arguments and take them from preseed file instead.

Bug#845423: virtualbox-ext-pack: hash mismatch Oracle_VM_VirtualBox_Extension_Pack-5.1.10.vbox-extpack

[Martin Steigerwald]

Package: virtualbox-ext-pack
Version: 5.1.10-1
Severity: normal

Dear Maintainer,

on upgrading to the new version I receive:

1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] 
Setting up virtualbox-ext-pack (5.1.10-1) ...
virtualbox-ext-pack: downloading: 
http://download.virtualbox.org/virtualbox/5.1.10/Oracle_VM_VirtualBox_Extension_Pack-5.1.10.vbox-extpack
The file will be downloaded into /usr/share/virtualbox-ext-pack
Hash mismatch Oracle_VM_VirtualBox_Extension_Pack-5.1.10.vbox-extpack
dpkg: error processing package virtualbox-ext-pack (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 virtualbox-ext-pack

Thank you,
Martin

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

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

Versions of packages virtualbox-ext-pack depends on:
ii  debconf [debconf-2.0]  1.5.59
ii  virtualbox 5.1.10-dfsg-1
ii  wget   1.18-4

virtualbox-ext-pack recommends no packages.

virtualbox-ext-pack suggests no packages.

-- debconf information:
* virtualbox-ext-pack/license: true

Bug#784070: Newly-created arrays don't auto-assemble - related to hostname change?

[Michael Tokarev]

23.11.2016 05:34, NeilBrown wrote:
> On Tue, Nov 22 2016, Andy Smith wrote:
> 
>> Hi Neil,
>>
>> On Tue, Nov 22, 2016 at 09:56:28AM +1100, NeilBrown wrote:
>>> Thanks.  Sorry this is taking a lot of back-and-forth...
>>
>> No worries. This is very interesting to me and I'd also like to know
>> what is going wrong even if I have a work-around.
> 
> Thanks.
> I tried this on a scratch Debian VM I had lying around, and found I
> could exactly reproduce your symptoms.
> I found that, unlike on the first Debian system I looked at, there is a
> line in  /lib/udev/rules.d/64-md-raid-assembly.rules 
> 
>   # Disable incremental assembly to fix Debian bug #784070
>   GOTO="md_inc_end"
> 
> Remove that and the problem goes away.  Arrgg...
> 
> I wish people maintainers would *ask* upstream when they don't
> understand, rather than just breaking things.

Neil, with all my respect, this is a bit over-reaction :)

It was long ago when we disabled incremental assembly when
you turned it on by default, and kept old static way to
assemble arrays, because neither our initrd nor regular
userpsace weren't ready for that.  At the time jessie come
out, we didn't have enough time to sort it out, so we kept
it for jessie too.

After restoring your (upstream) rules, things WILL break in
other place.  Someone already tried that and had to revert
it back to what we have now. Initrd should have some
initial infrastructure for event-based work before this will
be possible.

I wanted to fix it all for stretch. But once I had a conflict
with the d-i team I don't work on mdadm (or any other package
touching d-i) anymore.

Thanks,

/mjt

Bug#845302: systemd: 232-6:Failed to boot, makes kernel panic when starting /sbin/init.

[K.Ohta]

Dear Michel,

/usr entry /etc/fstab (will attach) of my box was set below, not to mount:
> UUID=c9d2e9cb-c214-4ca0-bdc9-40d39233e700 /usr ext4
> rw,noatime,suid,dev,exec,auto,nouser,async 0 2

But, change to below, mount /usr and boot:
> UUID=c9d2e9cb-c214-4ca0-bdc9-40d39233e700 /usr ext4 defaults,noatime   0  
>  2

(I changed mount option to keep health of SSD using for /usr .)

I also attach output of ls -al foo of before mail, disks.txt is correct 
booting, 
disk_notboot.txt is not correct booting (not mounted /usr).

Regards,
Ohta.

On Wed, 23 Nov 2016 09:41:58 +0100
Michael Biebl  wrote:

> Am 23.11.2016 um 04:20 schrieb Michael Biebl:
> > Fwiw, I suspect your problem might be, that / and /usr are on
> > different drives. initramfs-tools is not event based, so maybe sde
> > (your HDD) is not available yet when it attempts to mount /usr.  
> 
> Assuming this is the case, initramfs-tools should probably retry a few
> times to mount /usr, similar to how it handles nfs_mount_root() as in
> https://anonscm.debian.org/cgit/kernel/initramfs-tools.git/tree/scripts/nfs#n77
> 
> 
> It would also be interesting to know, if your problem is solved by
> installing dracut, which will replace initramfs-tools with an event
> based initramfs.
> 
> 



fstab
Description: Binary data
brw--- 1 root root 8,   0 Nov 23 17:34 /dev/sda
brw--- 1 root root 8,   1 Nov 23 17:34 /dev/sda1
brw--- 1 root root 8,   2 Nov 23 17:34 /dev/sda2
brw--- 1 root root 8,   3 Nov 23 17:34 /dev/sda3
brw--- 1 root root 8,   5 Nov 23 17:34 /dev/sda5
brw--- 1 root root 8,   6 Nov 23 17:34 /dev/sda6
brw--- 1 root root 8,   7 Nov 23 17:34 /dev/sda7
brw--- 1 root root 8,  16 Nov 23 17:34 /dev/sdb
brw--- 1 root root 8,  17 Nov 23 17:34 /dev/sdb1
brw--- 1 root root 8,  32 Nov 23 17:34 /dev/sdc
brw--- 1 root root 8,  33 Nov 23 17:34 /dev/sdc1
brw--- 1 root root 8,  34 Nov 23 17:34 /dev/sdc2
brw--- 1 root root 8,  35 Nov 23 17:34 /dev/sdc3
brw--- 1 root root 8,  36 Nov 23 17:34 /dev/sdc4
brw--- 1 root root 8,  37 Nov 23 17:34 /dev/sdc5
brw--- 1 root root 8,  48 Nov 23 17:34 /dev/sdd
brw--- 1 root root 8,  58 Nov 23 17:34 /dev/sdd10
brw--- 1 root root 8,  59 Nov 23 17:34 /dev/sdd11
brw--- 1 root root 8,  51 Nov 23 17:34 /dev/sdd3
brw--- 1 root root 8,  52 Nov 23 17:34 /dev/sdd4
brw--- 1 root root 8,  53 Nov 23 17:34 /dev/sdd5
brw--- 1 root root 8,  54 Nov 23 17:34 /dev/sdd6
brw--- 1 root root 8,  55 Nov 23 17:34 /dev/sdd7
brw--- 1 root root 8,  56 Nov 23 17:34 /dev/sdd8
brw--- 1 root root 8,  57 Nov 23 17:34 /dev/sdd9
brw--- 1 root root 8,  64 Nov 23 17:34 /dev/sde
brw--- 1 root root 8,  65 Nov 23 17:34 /dev/sde1
brw--- 1 root root 8,  66 Nov 23 17:34 /dev/sde2
brw--- 1 root root 8,  67 Nov 23 17:34 /dev/sde3
brw--- 1 root root 8,  68 Nov 23 17:34 /dev/sde4
brw--- 1 root root 8,  69 Nov 23 17:34 /dev/sde5
brw--- 1 root root 8,  80 Nov 23 17:34 /dev/sdf
brw--- 1 root root 8,  81 Nov 23 17:34 /dev/sdf1
brw--- 1 root root 8,  96 Nov 23 17:34 /dev/sdg
brw--- 1 root root 8,  97 Nov 23 17:34 /dev/sdg1
brw--- 1 root root 8, 112 Nov 23 17:34 /dev/sdh
brw--- 1 root root 8, 113 Nov 23 17:34 /dev/sdh1
brw--- 1 root root 8, 128 Nov 23 17:34 /dev/sdi
brw--- 1 root root 8, 129 Nov 23 17:34 /dev/sdi1
brw--- 1 root root 8, 130 Nov 23 17:34 /dev/sdi2
brw--- 1 root root 8, 144 Nov 23 17:34 /dev/sdj
brw--- 1 root root 8, 145 Nov 23 17:34 /dev/sdj1
brw--- 1 root root 8, 146 Nov 23 17:34 /dev/sdj2
brw--- 1 root root 8, 147 Nov 23 17:34 /dev/sdj3
brw--- 1 root root 8, 148 Nov 23 17:34 /dev/sdj4
brw--- 1 root root 8, 149 Nov 23 17:34 /dev/sdj5
brw--- 1 root root 8, 150 Nov 23 17:34 /dev/sdj6
brw--- 1 root root 8, 151 Nov 23 17:34 /dev/sdj7
brw--- 1 root root 8, 160 Nov 23 17:34 /dev/sdk
brw--- 1 root root 8, 161 Nov 23 17:34 /dev/sdk1
/dev/disk/by-id:
total 0
drwxr-xr-x 2 root root 1880 Nov 23 17:34 .
drwxr-xr-x 8 root root  160 Nov 23 17:34 ..
lrwxrwxrwx 1 root root9 Nov 23 17:34 ata-ADATA_SP550_2G3020013209 -> 
../../sde
lrwxrwxrwx 1 root root   10 Nov 23 17:34 ata-ADATA_SP550_2G3020013209-part1 -> 
../../sde1
lrwxrwxrwx 1 root root   10 Nov 23 17:34 ata-ADATA_SP550_2G3020013209-part2 -> 
../../sde2
lrwxrwxrwx 1 root root   10 Nov 23 17:34 ata-ADATA_SP550_2G3020013209-part3 -> 
../../sde3
lrwxrwxrwx 1 root root   10 Nov 23 17:34 ata-ADATA_SP550_2G3020013209-part4 -> 
../../sde4
lrwxrwxrwx 1 root root   10 Nov 23 17:34 ata-ADATA_SP550_2G3020013209-part5 -> 
../../sde5
lrwxrwxrwx 1 root root9 Nov 23 17:34 ata-TOSHIBA_DT01ACA300_66H11W8AS -> 
../../sdf
lrwxrwxrwx 1 root root   10 Nov 23 17:34 ata-TOSHIBA_DT01ACA300_66H11W8AS-part1 
-> ../../sdf1
lrwxrwxrwx 1 root root9 Nov 23 17:34 ata-TOSHIBA_DT01ACA300_X3J800VGS -> 
../../sdd
lrwxrwxrwx 1 root root   11 Nov 23 17:34 
ata-TOSHIBA_DT01ACA300_X3J800VGS-part10 -> ../../sdd10
lrwxrwxrwx 1 root root   11 Nov 23 17:34

Bug#845423: virtualbox-ext-pack: hash mismatch Oracle_VM_VirtualBox_Extension_Pack-5.1.10.vbox-extpack

[Gianfranco Costamagna]

thanks Martin!,
fixing now

G.





Il Mercoledì 23 Novembre 2016 10:03, Martin Steigerwald  
ha scritto:
Package: virtualbox-ext-pack
Version: 5.1.10-1
Severity: normal

Dear Maintainer,

on upgrading to the new version I receive:

1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] 
Setting up virtualbox-ext-pack (5.1.10-1) ...
virtualbox-ext-pack: downloading: 
http://download.virtualbox.org/virtualbox/5.1.10/Oracle_VM_VirtualBox_Extension_Pack-5.1.10.vbox-extpack
The file will be downloaded into /usr/share/virtualbox-ext-pack
Hash mismatch Oracle_VM_VirtualBox_Extension_Pack-5.1.10.vbox-extpack
dpkg: error processing package virtualbox-ext-pack (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
virtualbox-ext-pack

Thank you,
Martin

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

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

Versions of packages virtualbox-ext-pack depends on:
ii  debconf [debconf-2.0]  1.5.59
ii  virtualbox 5.1.10-dfsg-1
ii  wget   1.18-4

virtualbox-ext-pack recommends no packages.

virtualbox-ext-pack suggests no packages.

-- debconf information:
* virtualbox-ext-pack/license: true

Bug#845401: debian-installer: auto=true not working

[Philip Hands]

Cyril Brulebois  writes:

> Control: severity -1 normal
> Control: tag -1 - d-i
>
> Andrey Yarkov  (2016-11-23):
>> Package: debian-installer
>> Severity: grave
>> Tags: d-i
>> Justification: renders package unusable
>
> Sorry, but I'm going to disagree here…
>
>> Dear Maintainer,
>> 
>> I added the following to kernel parameters on Jessie-8.6.0 official
>> installation DVD-1
>> 
>> auto=true url=http://my.ip.addr.ess/preseed.cfg
>> 
>> but I got asked keyboard or locale related questions anyway.
>> 
>> Could it be that the delaying functionality got lost?
>
> I think that's documented in the installation guide:
>
> “B.4.1. Localization
> 
> Setting localization values will only work if you are using initrd
> preseeding. With all other methods the preconfiguration file will only
> be loaded after these questions have been asked.”
>
> See: https://www.debian.org/releases/stable/amd64/apbs04.html.en
>
> Leaving this open for the time being, but I think it should be closed as
> not a bug.

Erm, I think that is a bug -- the auto=true should ensure that the
keyboard question is only asked after the network came up and gave the
chance for the preseed file to be loaded.

I don't see what's changed recently though, and I normally only test
this with netinsts which obviously bring the network up sooner.

Andrey, is this also broken if you use CD#1?  Also, you normally want to
specify priority=critical as well, but I doubt that's the cause of your problem.

Cheers, Phil.
-- 
|)|  Philip Hands  [+44 (0)20 8530 9560]  HANDS.COM Ltd.
|-|  http://www.hands.com/http://ftp.uk.debian.org/
|(|  Hugo-Klemm-Strasse 34,   21075 Hamburg,GERMANY


signature.asc
Description: PGP signature

Bug#784070: Newly-created arrays don't auto-assemble - related to hostname change?

[SOUBEYRAND Yann - externe]

Le mercredi 23 novembre 2016 à 13:34 +1100, ne...@suse.com a écrit :
> On Tue, Nov 22 2016, Andy Smith wrote:
> 
> > Hi Neil,
> >
> > On Tue, Nov 22, 2016 at 09:56:28AM +1100, NeilBrown wrote:
> >> Thanks.  Sorry this is taking a lot of back-and-forth...
> >
> > No worries. This is very interesting to me and I'd also like to know
> > what is going wrong even if I have a work-around.
> 
> Thanks.
> I tried this on a scratch Debian VM I had lying around, and found I
> could exactly reproduce your symptoms.
> I found that, unlike on the first Debian system I looked at, there is a
> line in  /lib/udev/rules.d/64-md-raid-assembly.rules 
> 
>   # Disable incremental assembly to fix Debian bug #784070
>   GOTO="md_inc_end"
> 
> Remove that and the problem goes away.  Arrgg...
> 
> I wish people maintainers would *ask* upstream when they don't
> understand, rather than just breaking things.
> 
> NeilBrown

Hi Neil,

I encourage you to have a look at the full history of this bug to see
why this line was introduced. You will then see that it has been removed
in Stretch.

Regards

Yann



Ce message et toutes les pièces jointes (ci-après le 'Message') sont établis à 
l'intention exclusive des destinataires et les informations qui y figurent sont 
strictement confidentielles. Toute utilisation de ce Message non conforme à sa 
destination, toute diffusion ou toute publication totale ou partielle, est 
interdite sauf autorisation expresse.

Si vous n'êtes pas le destinataire de ce Message, il vous est interdit de le 
copier, de le faire suivre, de le divulguer ou d'en utiliser tout ou partie. Si 
vous avez reçu ce Message par erreur, merci de le supprimer de votre système, 
ainsi que toutes ses copies, et de n'en garder aucune trace sur quelque support 
que ce soit. Nous vous remercions également d'en avertir immédiatement 
l'expéditeur par retour du message.

Il est impossible de garantir que les communications par messagerie 
électronique arrivent en temps utile, sont sécurisées ou dénuées de toute 
erreur ou virus.


This message and any attachments (the 'Message') are intended solely for the 
addressees. The information contained in this Message is confidential. Any use 
of information contained in this Message not in accord with its purpose, any 
dissemination or disclosure, either whole or partial, is prohibited except 
formal approval.

If you are not the addressee, you may not copy, forward, disclose or use any 
part of it. If you have received this message in error, please delete it and 
all copies from your system and notify the sender immediately by return message.

E-mail communication cannot be guaranteed to be timely secure, error or 
virus-free.

Bug#845302: systemd: 232-6:Failed to boot, makes kernel panic when starting /sbin/init.

[Michael Biebl]

Am 23.11.2016 um 10:02 schrieb K.Ohta:
> Dear Michel,
> 
> /usr entry /etc/fstab (will attach) of my box was set below, not to mount:
>> UUID=c9d2e9cb-c214-4ca0-bdc9-40d39233e700 /usr ext4
>> rw,noatime,suid,dev,exec,auto,nouser,async 0 2
> 
> But, change to below, mount /usr and boot:
>> UUID=c9d2e9cb-c214-4ca0-bdc9-40d39233e700 /usr ext4 defaults,noatime   0 
>>   2
> 


Can you edit /usr/share/initramfs-tools/init, go to line 232, add a line
"sleep 10", then run "update-initramfs -u".

Is /usr then mouned properly in the initramfs?
Which log messages do you get on the console?


-- 
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#845424: freetype: Not renderable font in Debian

[Maximiliano Curia]

Source: freetype
Version: 2.5.2-3
Severity: important

Hi,

After some minor changes in a forum of a lug, I found that I could no longer 
read it in Debian (neither with chromium, nor firefox, neither in jessie nor 
in sid), while the text was readable in Ubuntu, Arch and other distros (used 
among the other lug members).  The forum changed to a different font so the 
page is readable in Debian again, but the issue is reproducible with: 
https://fonts.google.com/specimen/Fira+Sans which is showing the character 
list blank and the only preview that seems to work is the Light Italic one, 
compare this to https://fonts.google.com/specimen/Source+Sans+Pro which shows 
the full output.

Using the chromium inspect object, I manage to obtain the corresponding woff2 
url: 
https://fonts.gstatic.com/s/firasans/v6/EjsrzDkQUQCDwsBtLpcVQVtXRa8TVwTICgirnJhmVJw.woff2

Using: https://github.com/google/woff2 I converted the woff2 font to ttf and 
the decompressed ttf showed the same behaviour (It can't be rendered in Debian, 
but it renders fine in Ubuntu).

Using fontforge the font can be edited with no problems in any distro.

For convenience I've left the decompressed ttf file in: 
 http://freak.gnuservers.com.ar/~maxy/debian/fira.ttf

I'm not completely sure if the problem is really a bug in freetype or in some 
other library. Please reassign as you see fit.

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

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

Bug#828481: ori: staying with libssl1.0

[Afif Elghraoui]

Control: severity -1 important
Control: unblock 827061 by -1

This path of staying behind with openssl 1.0 was approved by the release
team [1]. Upstream has not moved on to openssl 1.1 and we aren't
equipped to make and test the required changes.

1. https://lists.debian.org/debian-release/2016/11/msg00573.html

-- 
Afif Elghraoui | عفيف الغراوي
http://afif.ghraoui.name

Bug#845302: systemd: 232-6:Failed to boot, makes kernel panic when starting /sbin/init.

[Michael Biebl]

Am 23.11.2016 um 10:25 schrieb Michael Biebl:
> Can you edit /usr/share/initramfs-tools/init, go to line 232, add a line
> "sleep 10", then run "update-initramfs -u".

Choose a longer sleep, if you have a slow system/lots of hard
disks/controllers.


-- 
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#845401: debian-installer: auto=true not working

[Philip Hands]

Joerg Jaspert  writes:

> On 14500 March 1977, Andrey Yarkov wrote:
>> I added the following to kernel parameters on Jessie-8.6.0 official 
>> installation DVD-1
>> auto=true url=http://my.ip.addr.ess/preseed.cfg
>> but I got asked keyboard or locale related questions anyway.
>
> As expected, happens to network boot installs too.
>
>> Could it be that the delaying functionality got lost?
>
> I've always had to preseed the various questions asked before network is
> available too. d-i offers a feature just for this: A series of short
> options for the kernel commandline, see its documentation. If you set
> them, it will run without asking anything.

While it's true that you can do it that way, you should also be able to
delay the pre-network questions with auto=true, and then preseed them in
the network file.

Here's a video of that working, using a d-i mini.iso, and typing (rather
a lot of weirdness, but none of it to set the keyboard) at the boot
prompt:

  
https://jenkins.debian.net/view/lvc/job/lvc_debian-miniiso/331/artifact/results/Preseed_using_hands.com_with_checksum.mpg

Cheers, Phil.
-- 
|)|  Philip Hands  [+44 (0)20 8530 9560]  HANDS.COM Ltd.
|-|  http://www.hands.com/http://ftp.uk.debian.org/
|(|  Hugo-Klemm-Strasse 34,   21075 Hamburg,GERMANY


signature.asc
Description: PGP signature

Bug#845379: [Pkg-javascript-devel] Bug#845379: node-fuzzaldrin-plus: FTBFS: Npm module "grunt-contrib-coffee" not found.

[Chris Lamb]

Pirate Praveen wrote:

> Control: tags -1 pending
> 
> On Wednesday 23 November 2016 03:04 AM, Chris Lamb wrote:
> >   Warning: Task "coffee" not found. Use --force to continue.
> 
> missed builddeps on node-grunt-contrib-coffee. Fixed. But
> node-grunt-contrib-coffee needs to clear NEW.

ACCEPTED.


Regards,

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

Bug#845379: [Pkg-javascript-devel] Bug#845379: node-fuzzaldrin-plus: FTBFS: Npm module "grunt-contrib-coffee" not found.

[Pirate Praveen]

Control: tags -1 pending

On Wednesday 23 November 2016 03:04 AM, Chris Lamb wrote:
>   Warning: Task "coffee" not found. Use --force to continue.

missed builddeps on node-grunt-contrib-coffee. Fixed. But
node-grunt-contrib-coffee needs to clear NEW.




signature.asc
Description: OpenPGP digital signature

Bug#845425: DataSource no longer accessible since jessie security update

[Arne Nordmark]

Package: tomcat7
Version: 7.0.56-3+deb8u5
Severity: normal

After the security update 7.0.56-3+deb8u5, I get an error message:

ALLVARLIG: Servlet.service() for servlet [Faces Servlet] in context with
path [/mech] threw exception [Filter execution threw an exception] with
root cause
org.hibernate.HibernateException: Unable to determine appropriate
DataSource to use

This seems likely to be connected with the fix for bug #842666, but I am
not expert enough to determine whether this is due to misconfiguration,
a problem with the fix, a problem in Hibernate, or ...

It used to work with 7.0.56-3+deb8u4, and downgrading to 7.0.56-3+deb8u3
from stable also restores the functionality.

/etc/tomcat7/server.xml:
...
  
...
   
   
...
  
...

webapp/META-INF/context.xml:

  


Thanks,
Arne

Bug#845426: munin-c: please make the build reproducible (buildpath)

[Daniel Shahaf]

Source: munin-c
Version: 0.0.9-1
Severity: wishlist
Tags: upstream patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: buildpath

Hi!

While working on the “reproducible builds” effort [1], we have noticed
that munin-c could not be built reproducibly.

Specifically, ./getversion outputs "unknown" if the last component of
the build path is not of the form munin-c-* (as with 'sbuild
--build-path /tmp/foobar').

Patch attached.

Cheers,

Daniel

 [1]: https://wiki.debian.org/ReproducibleBuilds
diff --git a/debian/patches/reproducible-build.diff b/debian/patches/reproducible-build.diff
index e69de29..2cb08b9 100644
--- a/debian/patches/reproducible-build.diff
+++ b/debian/patches/reproducible-build.diff
@@ -0,0 +1,25 @@
+Description: Make the build reproducible
+  Make the build independent of the value of $(pwd).
+Author: Daniel Shahaf 
+Bug-Debian: https://bugs.debian.org/-1
+Last-Update: 2016-11-23
+
+--- a/getversion
 b/getversion
+@@ -64,10 +64,16 @@
+ 	basename $(pwd) | grep -e '^munin-c' | cut -c9-
+ }
+ 
++generate_version_string_from_packaging() {
++dpkg-parsechangelog -SVersion
++}
++
+ if [ -s "RELEASE" ]; then
+ cat RELEASE
+ elif [ "$(git rev-parse --is-inside-work-tree 2>/dev/null)" = "true" ]; then
+ generate_version_string
++elif [ ! -z "$(generate_version_string_from_packaging 2>/dev/null)" ]; then
++	generate_version_string_from_packaging
+ elif [ ! -z "$(generate_version_string_from_dir)" ]; then
+ 	generate_version_string_from_dir
+ else
diff --git a/debian/patches/series b/debian/patches/series
index e69de29..f64d497 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -0,0 +1 @@
+reproducible-build.diff

Bug#845427: python-pywcs: ROM; dead upstream; superceded by python-astropy

[Ole Streicher]

Package: ftp.debian.org
Severity: normal
X-Debbugs-CC: debian-as...@lists.debian.org

Dear ftpmasters,

please remove python-pywcs. It is not maintained upstream anymore since
years and completely superceded by python-astropy. Without major
efforts, it is unusable because of incompatibilities to its
dependencies. CI tests fail.

People should just move to astropy and replace

import pywcs

with

import astropy.wcs as pywcs

There are no reverse dependencies.

Best regards

Ole

Bug#838495: RFS: python-cartopy/0.14.2-1 [ITP] -> to be canceled

[Ghislain Vaillant]

control: reopen -1

On 22/11/16 20:38, Gianfranco Costamagna wrote:

Hi,


I have uploaded a new version of python-cartopy/0.14.2+dfsg1-1 [1] for



you to review and sponsor.



in deferred/5, let me know if it is ok or I need to cancel it, thanks you both!
G.


Hi Gianfranco,

Please cancel it, as I did some significant reworking since.

I'll ping you when the new release is ready.

By the way, congrats for your appointment to the Ubuntu team [1].

[1] https://lists.ubuntu.com/archives/ubuntu-devel/2016-November/039550.html

Ghis

Bug#844788: suspending from VGA makes no difference - stuck at the same place.

[Andrew Worsley]

Also just wanted to add that running all kernels with command lines:
nomodeset nointremap acpi=none vga=0x34c


Also all the modes in /sys/power/pm_test (except none) are fine in the
problematic 4.7.0 kernel - even with "nomodeset nointremap acpi=none"
kernel options removed.

Still hangs on resuming in 4.7.0

In the 3.16.7-ckt25 kernel is the only one that is fine for resume...
(except it also wants these "nomodeset nointremap acpi=none" boot
options otherwise I get kernel complaints...

dmidecode:1012 freeing invalid memtype [me
m 0x3fff8ad1b000-0x3fff8ad1bfff]
Nov 23 21:01:14 localhost kernel: [   10.122979] dmidecode: Corrupted
page table at address
7f10d9da7000
Nov 23 21:01:14 localhost kernel: [   10.122982] PGD 45c7c7067 PUD
45c774067 PMD 45d95f067
PTE 8ad1b225
Nov 23 21:01:14 localhost kernel: [   10.122985] Bad pagetable: 000d [#3] SMP

Bug#845428: fai-diskimage does not run if host uses LVM

[Thomas Lange]

Package: fai-setup-storage
Version: 5.2

If fai-diskimage is run on a host that is using LVM partitions,
setup-storage tries to disable (vgchange -a n) the volumes groups of
the host. But all info about the LVM of the host should be ignored.
vgchange is called in Commands.pm.


-
   Fully Automatic Installation  -  FAI

   5.2   (c) 1999-2016
   Thomas Lange  
 -
Starting FAI execution - 20161103_140608
Hostname set to gce-test

Using configuration files from /etc/fai
Calling task_confdir
FAI_FLAGS: 
Setting SERVER=. Value extracted from FAI_CONFIG_SRC.
No monitor daemon defined.
FAI_CONFIG_SRC is set to file:///srv/fai/config
Using local path /srv/fai/config as config space.
Calling task_setup
FAI_FLAGS: 
Calling task_defclass
List of all classes:  DEBIAN AMD64 FAIBASE GRUB_PC CLOUD GCE
Calling task_defvar
++ CONSOLEFONT=
++ KEYMAP=us-latin1
++ MODULESLIST='usbhid psmouse'
++ flag_initial=1
++ FAI_ALLOW_UNSIGNED=1
++ UTC=yes
++ TIMEZONE=America/Los_Angeles
++ ROOTPW=X
++ STOP_ON_ERROR=700
++ MAXPACKAGES=800
++ release=jessie
++ TIMEZONE=UTC
++ NTPSRVS=metadata.google.internal
Calling task_action
FAI_ACTION: install
Performing FAI installation. All data may be overwritten!
Calling task_install
Calling task_partition
Starting setup-storage 2.0
Using config file: /srv/fai/config/disk_config/CLOUD
Parted could not read a disk label (new disk?)
Executing: parted -s /dev/loop0 mklabel msdos
Don't know how to check preservation of /dev/dm-0
Executing: parted -s /dev/loop0 mklabel msdos
Executing: parted -s /dev/loop0 mkpart primary "ext3" 1048576B 9759096831B
Executing: parted -s /dev/loop0 set 1 boot on
Executing: parted -s /dev/loop0 mkpart primary "ext3" 9759096832B 10737418239B
Executing: mkfs.ext4  /dev/loop0p1
Executing: tune2fs -c 0 -i 0 /dev/loop0p1
Executing: mkfs.ext4 -L home -m 1 /dev/loop0p2
Executing: tune2fs -c 0 -i 0 /dev/loop0p2
Executing: vgchange -a n gymnast
(STDERR)   Logical volume gymnast/root contains a filesystem in use.
(STDERR)   Can't deactivate volume group "gymnast" with 2 open logical volume(s)
Command had non-zero exit code

This is your disk_config file:
# config for a disk image for a VM
#
#

disk_config disk1 disklabel:msdos bootable:1 fstabkey:uuid align-at:1M

primary /  300-  ext4  rw,barrier=0,noatime,errors=remount-ro 
tuneopts="-c 0 -i 0"
primary /home  50-10%ext4  rw,barrier=0,noatime,nosuid,nodev createopts="-L 
home -m 1" tuneopts="-c 0 -i 0"

Error in task partition. Code: 710
Traceback: task_error task_partition task task_install task task_action task 
main
$LOGUSER is undefined. Not saving log files to remote.
FATAL ERROR. Installation stopped.


-- 
regards Thomas

Bug#844789: [Debian-science-sagemath] Bug#844789: iS: issue related to compressed manual.six

[Bill Allombert]

On Wed, Nov 23, 2016 at 04:57:45AM +, Jerome BENOIT wrote:
> It appears that atomic_write is not involved:
> I was confused by the fact the test-command runs several gap sessions
> that log to the same file, hence the confusion.
> If to each processed gap session is associated a specific log file,
> the issue remain but atomic_write appears not involved.

Can you generate a full strace dump ?

> Let open an other front:
> my understanding is that six files are generated, why obsolete six files are 
> still around ?

There are two generators: 
1) the old ones are generated by etc/gapmacro.tex using TeX
2) the new ones are generated by GAPdoc using GAP.

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 

Bug#845372: qtbase-opensource-src: Please enable m68k in double-conversion

[John Paul Adrian Glaubitz]

On 11/23/2016 11:10 AM, Dmitry Shachnev wrote:
> We will be better using the system double-conversion instead of the bundled
> one. This was the case in Qt 5.6, but in 5.7 the relevant code has been
> moved from qtdeclarative to qtbase, and I somehow forgot about that.

Could this be done for qtwebkit-opensource-src and qtwebkit as well? They
also have the same issue on m68k, although they need a little more patching
to build fine on m68k.

Thanks,
Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913



signature.asc
Description: OpenPGP digital signature

Bug#845372: qtbase-opensource-src: Please enable m68k in double-conversion

[Dmitry Shachnev]

Hi Adrian,

On Tue, Nov 22, 2016 at 09:43:44PM +0100, John Paul Adrian Glaubitz wrote:
> With the update to 5.7.x, qtbase-opensource-src now fails to build
> from source on Linux/m68k. This is because the embedded third-party
> package 'double-conversion' in qtbase is too old to support m68k.
> Support for m68k was on May 18, 2014 [1].
>
> The attached diff patches the embedded double-conversion code the
> same way it was patched in the previously mentioned commit [1].
>
> Please include the patch in the next upload of qtbase-opensource-src
> so that the package can be built on m68k again.

We will be better using the system double-conversion instead of the bundled
one. This was the case in Qt 5.6, but in 5.7 the relevant code has been
moved from qtdeclarative to qtbase, and I somehow forgot about that.

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#844275: [debian-mysql] Bug#844275: mysql_config injects build flags which breaks the build for other packages

[Norvald H. Ryeng]

mysql_config and mysqlclient.pc pick up compile flags from the build
environment. We have a fix for this upstream, and I've backported it to
5.7.16 (see attachment).

I haven't tested it with sbuild/dpkg, so when applying this, please
verify that mysql_config and mysqlclient.pc don't pick up any flags
they shouldn't.

Regards,

Norvalddiff -rup a/scripts/CMakeLists.txt b/scripts/CMakeLists.txt
--- a/scripts/CMakeLists.txt	2016-09-28 19:02:44.0 +0200
+++ b/scripts/CMakeLists.txt	2016-11-23 10:35:45.547116146 +0100
@@ -170,78 +170,42 @@ IF(MALLOC_LIB)
   INSTALL(FILES ${MALLOC_LIB} DESTINATION ${INSTALL_LIBDIR} OPTIONAL)
 ENDIF()
 
-IF(CMAKE_GENERATOR MATCHES "Makefiles")
-  # Strip maintainer mode options if necessary
-  STRING(REPLACE "${MY_C_WARNING_FLAGS}" "" CFLAGS
-"${CMAKE_C_FLAGS} ${CMAKE_C_FLAGS_RELWITHDEBINFO}")
-  STRING(REPLACE "${MY_CXX_WARNING_FLAGS}" "" CXXFLAGS
-"${CMAKE_CXX_FLAGS} ${CMAKE_CXX_FLAGS_RELWITHDEBINFO}")
-  FOREACH(ARCH ${CMAKE_OSX_ARCHITECTURES})
-SET(CFLAGS   "${CFLAGS} -arch ${ARCH}")
-SET(CXXFLAGS "${CXXFLAGS} -arch ${ARCH}")
-  ENDFOREACH()
-ELSE()
-  # Strip maintainer mode options if necessary
-  STRING(REPLACE "${MY_C_WARNING_FLAGS}" "" CFLAGS
-"${CMAKE_C_FLAGS_RELWITHDEBINFO}")
-  STRING(REPLACE "${MY_CXX_WARNING_FLAGS}" "" CXXFLAGS
-"${CMAKE_CXX_FLAGS_RELWITHDEBINFO}")
-ENDIF()
-
-# Add trailing whitespace, before substitution below.
-SET(CFLAGS "${CFLAGS} ")
-SET(CXXFLAGS "${CXXFLAGS} ")
-
-SET(REPLACE_OPTIONS
-  "-DDBUG_OFF "
-  "-DEXTRA_DEBUG "
-  "-DHAVE_VALGRIND "
-  "-DSAFE_MUTEX "
-  "-fPIC "
-  "-fno-inline "
-  "-fno-strict-aliasing "
-  "-fstack-protector-strong "
-  "-g "
-  "-grecord-gcc-switches "
-  "-ip "
-  "-mp "
-  "-pipe "
-  "-restrict "
-  "-unroll2 "
+SET(COMPILE_DEFINITIONS_WHITELIST
 )
 
-# Note sequence of -W options here, most specific first.
-SET(REPLACE_REGEX_OPTIONS
-  "-Wp,[-=_A-Za-z0-9]*"
-  "-Werror=[-A-Za-z]*"
-  "-W[-A-Za-z]*"
-  "--param=[-=a-z0-9]*"
-  "-O[0-9]"
-  "-march=[-A-Za-z0-9]*"
-  "-mcpu=[-A-Za-z0-9]*"
-  "-mtune=[-A-Za-z0-9]*"
-  "-specs=[-A-Za-z0-9/]*"
-  "-xO[0-9]"
+# In practice: only in use on Solaris
+SET(CMAKE_C_FLAGS_WHITELIST
+  "-m32"
+  "-m64"
 )
 
-FOREACH(option ${REPLACE_REGEX_OPTIONS})
-  STRING(REGEX REPLACE "${option}" "" CFLAGS   "${CFLAGS}")
-  STRING(REGEX REPLACE "${option}" "" CXXFLAGS "${CXXFLAGS}")
-ENDFOREACH()
+SET(CFLAGS "")
+SET(CXXFLAGS "")
 
-FOREACH(option ${REPLACE_OPTIONS})
-  STRING(REPLACE "${option}" " " CFLAGS   "${CFLAGS}")
-  STRING(REPLACE "${option}" " " CXXFLAGS "${CXXFLAGS}")
+GET_PROPERTY(cwd_definitions DIRECTORY PROPERTY COMPILE_DEFINITIONS)
+FOREACH(white_flag ${COMPILE_DEFINITIONS_WHITELIST})
+  FOREACH(flag ${cwd_definitions})
+IF (${flag} MATCHES ${white_flag})
+  SET(CFLAGS "-D${white_flag} ${CFLAGS}")
+  SET(CXXFLAGS "-D${white_flag} ${CXXFLAGS}")
+ENDIF()
+  ENDFOREACH()
 ENDFOREACH()
-STRING(REPLACE "-fexceptions " " " CFLAGS "${CFLAGS}")
 
-# Finally: strip away whitespace.
-STRING(REGEX REPLACE "[ ]+" " " CFLAGS   "${CFLAGS}")
-STRING(REGEX REPLACE "[ ]+" " " CXXFLAGS "${CXXFLAGS}")
-STRING(REGEX REPLACE "^[ ]+" "" CFLAGS   "${CFLAGS}")
-STRING(REGEX REPLACE "^[ ]+" "" CXXFLAGS "${CXXFLAGS}")
-STRING(REGEX REPLACE "[ ]+$" "" CFLAGS   "${CFLAGS}")
-STRING(REGEX REPLACE "[ ]+$" "" CXXFLAGS "${CXXFLAGS}")
+IF(CMAKE_BUILD_TYPE AND CMAKE_GENERATOR MATCHES "Makefiles")
+  STRING(TOUPPER "${CMAKE_BUILD_TYPE}" CMAKEBT)
+  SET(CMAKEBT_FLAGS "${CMAKE_C_FLAGS_${CMAKEBT}} ${CMAKE_C_FLAGS}")
+  SEPARATE_ARGUMENTS(CMAKEBT_FLAGS)
+ENDIF()
+
+FOREACH(white_flag ${CMAKE_C_FLAGS_WHITELIST})
+  FOREACH(flag ${CMAKEBT_FLAGS})
+IF (${flag} STREQUAL ${white_flag})
+  SET(CFLAGS "${white_flag} ${CFLAGS}")
+  SET(CXXFLAGS "${white_flag} ${CXXFLAGS}")
+ENDIF()
+  ENDFOREACH()
+ENDFOREACH()
 
 IF(UNIX)
   # FIND_PROC and CHECK_PID are used by mysqld_safe
@@ -387,6 +351,16 @@ IF(QUOTED_CMAKE_CXX_LINK_FLAGS)
   SET(CONFIG_EMBEDD_LIBS "${CONFIG_EMBEDD_LIBS} ${QUOTED_CMAKE_CXX_LINK_FLAGS}")
 ENDIF()
 
+SET(CONFIG_LIBS_PRIVATE "${CLIENT_LIBS}")
+SET(CONFIG_REQUIRES_PRIVATE "")
+# ssl.cmake should have used pkg-config rather than cmake to locate ssl
+IF (WITH_SSL STREQUAL "system")
+  SET(CONFIG_REQUIRES_PRIVATE "openssl")
+  STRING(REPLACE "-lssl" "" CONFIG_LIBS_PRIVATE "${CONFIG_LIBS_PRIVATE}")
+  STRING(REPLACE "-lcrypto" "" CONFIG_LIBS_PRIVATE "${CONFIG_LIBS_PRIVATE}")
+  STRING(REGEX REPLACE "[ ]+" " " CONFIG_LIBS_PRIVATE "${CONFIG_LIBS_PRIVATE}")
+ENDIF()
+
 SET(LIBMYSQLD_LIBS_USAGE "
 --libmysqld-libs [$embedded_libs]")
 SET(DISABLE_EMBEDDED_SH "")
diff -rup a/scripts/mysqlclient.pc.in b/scripts/mysqlclient.pc.in
--- a/scripts/mysqlclient.pc.in	2016-09-28 19:02:44.0 +0200
+++ b/scripts/mysqlclient.pc.in	2016-11-23 10:29:27.372897342 +0100
@@ -1,4 +1,4 @@
-# Copyright (c) 2015, Oracle and/or its affiliates. All rights reserved.
+# Copyright (c) 2015, 2016, Oracle and/or its affiliates. All rights reserved.
 #
 # This

Bug#845428: fai-diskimage does not run if host uses LVM

[Thomas Lange]

In FAI 5.3 I've add a test, to prevent fai-diskimage to run if a LVM
partition is detected on the host system.

https://github.com/faiproject/fai/commit/dce458cfc7c6b3bf20b5f235f08f8c68fd875644
-- 
regards Thomas

Bug#827339: Please revert patch for cmd, and fix default pattern

[Stephan Sürken]

Hi Patrick,

On Di, 2016-11-22 at 11:33 +0100, Patrick Matthäi wrote:

(...)

> > S
> Thanks for your effort! I have just uploaded 1.0.3-3.

ok, thx!

> Would you (Stephan) be so kindly and upload it to jessie-bpo, if
> there
> are no new problems with it? I will be on vacation before it may
> enter
> testing.

ok, I will do that if I don't forget ;).

@evgeni: Would be nice if you could retest this.

Fwiw, to properly test matches, I emulated some "error logs" on hosts
using s.th. like this

---
DPkg::Pre-Install-Pkgs {"/usr/bin/printf 'E: apt-dater\n'";};
DPkg::Pre-Install-Pkgs {"/usr/bin/printf 'apt-dater ERROR\n'";};
DPkg::Pre-Install-Pkgs {"/usr/bin/printf 'W: apt-dater\n'";};
---

as extra apt.conf (this still needs an actual package upgrade to take
place to see these logs).

Hth!

S

Bug#845372: qtbase-opensource-src: Please enable m68k in double-conversion

[Dmitry Shachnev]

On Wed, Nov 23, 2016 at 11:14:07AM +0100, John Paul Adrian Glaubitz wrote:
> > We will be better using the system double-conversion instead of the bundled
> > one. This was the case in Qt 5.6, but in 5.7 the relevant code has been
> > moved from qtdeclarative to qtbase, and I somehow forgot about that.
>
> Could this be done for qtwebkit-opensource-src and qtwebkit as well? They
> also have the same issue on m68k, although they need a little more patching
> to build fine on m68k.

For qtwebkit-opensource-src — I will try (will need some patching probably).

For qtwebkit (4.x) — the goal is to remove it soon [1], so I don’t think it
is worth the effort.

[1]: https://lists.debian.org/debian-devel-announce/2015/05/msg1.html

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#845302: systemd: 232-6:Failed to boot, makes kernel panic when starting /sbin/init.

[K.Ohta]

Dear Michael,

Not mounted /usr and made kernel panic still longer sleep.

Then booting with "init=/bin/bash" , check dmesg (attached).
Below message was wrote when trying to mount /usr :
>[   15.958645] EXT4-fs (sde3): Unrecognized mount option "auto" or missing 
>value

If this message is correct, mount program included by initramfs
has not recognized "auto" (or some another) option(s), regardless
/bin/mount (or /sbin/mount/ext4) recognize this option(s) :-(

Regards,
Ohta.

On Wed, 23 Nov 2016 10:29:24 +0100
Michael Biebl  wrote:

> Am 23.11.2016 um 10:25 schrieb Michael Biebl:
> > Can you edit /usr/share/initramfs-tools/init, go to line 232, add a
> > line "sleep 10", then run "update-initramfs -u".  
> 
> Choose a longer sleep, if you have a slow system/lots of hard
> disks/controllers.
> 
> 

[0.00] Linux version 4.8.0-1-amd64 (debian-ker...@lists.debian.org) 
(gcc version 5.4.1 20161019 (Debian 5.4.1-3) ) #1 SMP Debian 4.8.7-1 
(2016-11-13)
[0.00] Command line: BOOT_IMAGE=/vmlinuz-4.8.0-1-amd64 
root=UUID=040b41b0-26fe-4064-af0a-3619f3112096 ro single vga=0x3d4 
video=vesafb:yrap,noresume init=/bin/bash
[0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point 
registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[0.00] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, 
using 'standard' format.
[0.00] x86/fpu: Using 'eager' FPU context switches.
[0.00] e820: BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0009] usable
[0.00] BIOS-e820: [mem 0x0010-0xbdf00fff] usable
[0.00] BIOS-e820: [mem 0xbdf01000-0xbe4defff] reserved
[0.00] BIOS-e820: [mem 0xbe4df000-0xbe8d2fff] ACPI NVS
[0.00] BIOS-e820: [mem 0xbe8d3000-0xbede8fff] reserved
[0.00] BIOS-e820: [mem 0xbede9000-0xbee25fff] type 20
[0.00] BIOS-e820: [mem 0xbee26000-0xbee26fff] usable
[0.00] BIOS-e820: [mem 0xbee27000-0xbf02cfff] ACPI NVS
[0.00] BIOS-e820: [mem 0xbf02d000-0xbf452fff] usable
[0.00] BIOS-e820: [mem 0xbf453000-0xbf7f3fff] reserved
[0.00] BIOS-e820: [mem 0xbf7f4000-0xbf7f] usable
[0.00] BIOS-e820: [mem 0xfec0-0xfec00fff] reserved
[0.00] BIOS-e820: [mem 0xfec1-0xfec10fff] reserved
[0.00] BIOS-e820: [mem 0xfec2-0xfec20fff] reserved
[0.00] BIOS-e820: [mem 0xfed0-0xfed00fff] reserved
[0.00] BIOS-e820: [mem 0xfed61000-0xfed70fff] reserved
[0.00] BIOS-e820: [mem 0xfed8-0xfed8] reserved
[0.00] BIOS-e820: [mem 0xfef0-0x] reserved
[0.00] BIOS-e820: [mem 0x00011000-0x00043eff] usable
[0.00] NX (Execute Disable) protection: active
[0.00] efi: EFI v2.31 by American Megatrends
[0.00] efi:  ACPI=0xbe8c2000  ACPI 2.0=0xbe8c2000  SMBIOS=0xf04c0  
MPS=0xfd550 
[0.00] SMBIOS 2.7 present.
[0.00] DMI: To Be Filled By O.E.M. To Be Filled By O.E.M./990FX 
Extreme4, BIOS P2.70 06/05/2014
[0.00] e820: update [mem 0x-0x0fff] usable ==> reserved
[0.00] e820: remove [mem 0x000a-0x000f] usable
[0.00] AGP: No AGP bridge found
[0.00] e820: last_pfn = 0x43f000 max_arch_pfn = 0x4
[0.00] MTRR default type: uncachable
[0.00] MTRR fixed ranges enabled:
[0.00]   0-9 write-back
[0.00]   A-B write-through
[0.00]   C-D6FFF write-protect
[0.00]   D7000-D uncachable
[0.00]   E-F write-protect
[0.00] MTRR variable ranges enabled:
[0.00]   0 base  mask 8000 write-back
[0.00]   1 base 8000 mask C000 write-back
[0.00]   2 base BF80 mask FF80 uncachable
[0.00]   3 disabled
[0.00]   4 disabled
[0.00]   5 disabled
[0.00]   6 disabled
[0.00]   7 disabled
[0.00] TOM2: 00043f00 aka 17392M
[0.00] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WC  UC- WT  
[0.00] e820: update [mem 0xbf80-0x] usable ==> reserved
[0.00] e820: last_pfn = 0xbf800 max_arch_pfn = 0x4
[0.00] found SMP MP-table at [mem 0x000fda20-0x000fda2f] mapped at 
[8926400fda20]
[0.00] Base memory trampoline at [892640097000] 97000 size 24576
[0.00] Using GB pages for direct mapping
[0.00] BRK [0x88f4c000, 0x88f4cfff] PGTABLE
[0.00] BRK [0x88f4d000, 0x88f4df

Bug#842605: sane-utils depends on update-inetd but it should not (anymore)

[Darshaka Pathirana]

Hi Jörg,

Yes, DEP9 is marked obsolete. I somehow missed that. But still: do
we need to depend on "update-inetd"?

Regards,
 - Darsha

On 2016-11-01 08:26, Jörg Frings-Fürst wrote:
> Hello Darahaka,
> 
> thank you for spending your time helping to make Debian better with
> this bug report.
> 
> From [1]:
> 
> As of Feb 2014: With a dynamic init system in Debian finally being
> adopted, inetd is irrelevant, hence reconf-inetd too, so I mark this
> DEP as obsolete, since it's not worth the migration effort.
> 
> 
> So I close this bug.
> 
> CU
> Jörg
> 
> [1] http://dep.debian.net/deps/dep9/
> 
> 



signature.asc
Description: OpenPGP digital signature

Bug#845372: qtbase-opensource-src: Please enable m68k in double-conversion

[John Paul Adrian Glaubitz]

On 11/23/2016 11:22 AM, Dmitry Shachnev wrote:
> For qtwebkit-opensource-src — I will try (will need some patching probably).

I have attached a patch to the appropriate bug report:

> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780430#27

> For qtwebkit (4.x) — the goal is to remove it soon [1], so I don’t think it
> is worth the effort.

I know, but I also prepared a patch for that in the meantime:

> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844722#5

I'm aware that qtwebkit is deprecated but it's still currently a reverse
dependency to quite a number of packages and therefore it would be good
to have it build on m68k automatically. Otherwise I constantly have to
do manual builds for every package upload :(.

Thanks,
Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913



signature.asc
Description: OpenPGP digital signature

Bug#845171: wine-development: FTBFS: ld aborts or segfaults

[Matthias Klose]

Control: tags -1 + help moreinfo

according to the logs, -Wl,--enable-new-dtags is already passed into the linker,
so I don't assume the defaults change in binutils is the root cause.

I'm unable to trigger the malloc error.  If you can, please run gcc with -v, and
then re-run the collect2/ld command and provide the object files and libraries
for the link.

Bug#681234: Extended November Printed Flag Offers

[Richard - Central Flags]

View online version 
http://gyt2.mjt.lu/nl2/gyt2/1qyj4.html?m=AEkAFpIvtx0AAUlJNS4AAGmMNpUAARpaV6oAGf6kAAdlMQBYNW9DrYFG_jcSTqWxhF0hFMIPngAHDG0&b=b6eabab3&e=df2bf4ec&email=681...@bugs.debian.org[http://gyt2.mjt.lu/img/gyt2/b/1q375/0yyio.jpeg]
 [http://centralflags.co.uk/]FORECOURT FLAGS - OCTOBER OFFERSWe are pleased 
toofferan amazing 1 free Printed Flag with every order of 
3printed printed flags until 25th Novembersaving you a massive 25%.To 
order of for more information simplyclick 
here[http://centralflags.us14.list-manage1.com/track/click?u=b3e015d7389d0c454fbd2e56f&id=35d394fb8f&e=91c22b2a59]and
 we will be more than happy to help. Or call us on0121 667 
8701today.[http://gyt2.mjt.lu/img/gyt2/b/1q375/0yyi7.jpeg][http://www.centralflags.co.uk/printed-flags/offer-buy-3-flags-get-1-free/]
 This e-mail has been sent to 681...@bugs.debian.org, click here to 
unsubscribehttp://gyt2.mjt.lu/unsub2?hl=en&m=AEkAFpIvtx0AAUlJNS4AAGmMNpUAARpaV6oAGf6kAAdlMQBYNW9DrYFG_jcSTqWxhF0hFMIPngAHDG0&b=b6eabab3&e=df2bf4ec&email=681...@bugs.debian.org. Woodville
 Road, Kings Heath B14 7AH Birmingham GB

Bug#845429: grass: v.net.iso - Segmentation fault

[Eduardo Corbelle Rico]

Package: grass
Version: 7.0.5-2
Severity: normal
Tags: newcomer

Dear Maintainer,

It happened to me that the use of v.net.iso command results in a
segmentation fault. I could replicate the error in two different
machines, with my own data and with both examples shown in the online
manual ( https://grass.osgeo.org/grass70/manuals/v.net.iso.html )
using the Spearfish dataset for GRASS 7.

After consultation in the GRASS-user list, it seems that this is
specific of the pre-compiled package (installed via apt-get), as the
error does not appear when GRASS 7.0 is compiled from source in the
same machine.

Greetings,

Eduardo Corbelle

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

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

Versions of packages grass depends on:
ii  grass-core  7.0.5-2+b1
ii  grass-gui   7.0.5-2+b1

Versions of packages grass recommends:
ii  grass-doc  7.0.5-2

Versions of packages grass suggests:
pn  grass-dev  

-- no debconf information

Bug#827339: Please revert patch for cmd, and fix default pattern

[Evgeni Golov]

Hi,

On Wed, Nov 23, 2016 at 11:21:02AM +0100, Stephan Sürken wrote:
> @evgeni: Would be nice if you could retest this.

tbh, I stopped using apt-dater, so I'd rather not :)

Bug#845302: systemd: 232-6:Failed to boot, makes kernel panic when starting /sbin/init.

[Michael Biebl]

Am 23.11.2016 um 11:25 schrieb K.Ohta:
> Dear Michael,
> 
> Not mounted /usr and made kernel panic still longer sleep.
> 
> Then booting with "init=/bin/bash" , check dmesg (attached).
> Below message was wrote when trying to mount /usr :
>> [   15.958645] EXT4-fs (sde3): Unrecognized mount option "auto" or missing 
>> value

That error message doesn't make sense.
The fstab you attached contains

> UUID=c9d2e9cb-c214-4ca0-bdc9-40d39233e700   /usr   ext4 
> defaults,noatime   0   2

There is no "auto" keyword there. Have you attached the correct fstab?




-- 
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#845372: qtbase-opensource-src: Please enable m68k in double-conversion

[Dmitry Shachnev]

On Wed, Nov 23, 2016 at 11:26:49AM +0100, John Paul Adrian Glaubitz wrote:
> > For qtwebkit-opensource-src — I will try (will need some patching probably).
>
> I have attached a patch to the appropriate bug report:
>
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780430#27
>
> > For qtwebkit (4.x) — the goal is to remove it soon [1], so I don’t think it
> > is worth the effort.
>
> I know, but I also prepared a patch for that in the meantime:
>
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844722#5
>
> I'm aware that qtwebkit is deprecated but it's still currently a reverse
> dependency to quite a number of packages and therefore it would be good
> to have it build on m68k automatically. Otherwise I constantly have to
> do manual builds for every package upload :(.

Oh, I did not realize that you had already provided the patches!

In case of #780430, it looks like Lisandro wants the patch to be reviewed
by upstream first, and you said you could forward it. Is there any update
on that?

In case of #844722, I would just ask you to NMU it. Though I am not listed
as Uploader, so let’s wait for what Lisandro says first.

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#845429: grass: v.net.iso - Segmentation fault

[Bas Couwenberg]

Control: tags -1 moreinfo


On 2016-11-23 11:33, Eduardo Corbelle Rico wrote:

It happened to me that the use of v.net.iso command results in a
segmentation fault. I could replicate the error in two different
machines, with my own data and with both examples shown in the online
manual ( https://grass.osgeo.org/grass70/manuals/v.net.iso.html )
using the Spearfish dataset for GRASS 7.


Please provide the steps to reproduce the issue.

Kind Regards,

Bas

Bug#845302: systemd: 232-6:Failed to boot, makes kernel panic when starting /sbin/init.

[K.Ohta]

Sorry, I booted *older* fetab entry;

Not booting with,
>> UUID=c9d2e9cb-c214-4ca0-bdc9-40d39233e700 /usr ext4 defaults,noatime   0 
>>   2  
Booting with uncommenting below line.
>>UUID=c9d2e9cb-c214-4ca0-bdc9-40d39233e700 /usr ext4
>>rw,noatime,suid,dev,exec,auto,nouser,async 0 2  
I will retry your saying with "defaults,noatime".Please wait.
Ohta.

On Wed, 23 Nov 2016 11:41:21 +0100
Michael Biebl  wrote:

> Am 23.11.2016 um 11:25 schrieb K.Ohta:
> > Dear Michael,
> > 
> > Not mounted /usr and made kernel panic still longer sleep.
> > 
> > Then booting with "init=/bin/bash" , check dmesg (attached).
> > Below message was wrote when trying to mount /usr :  
> >> [   15.958645] EXT4-fs (sde3): Unrecognized mount option "auto" or
> >> missing value  
> 
> That error message doesn't make sense.
> The fstab you attached contains
> 
> > UUID=c9d2e9cb-c214-4ca0-bdc9-40d39233e700   /usr
> > ext4 defaults,noatime   0   2  
> 
> There is no "auto" keyword there. Have you attached the correct fstab?
> 
> 
> 
> 



pgpG5DRn44e6I.pgp
Description: OpenPGP digital signature

Bug#845302: systemd: 232-6:Failed to boot, makes kernel panic when starting /sbin/init.

[Michael Biebl]

Am 23.11.2016 um 11:41 schrieb Michael Biebl:
> Am 23.11.2016 um 11:25 schrieb K.Ohta:
>> Dear Michael,
>>
>> Not mounted /usr and made kernel panic still longer sleep.
>>
>> Then booting with "init=/bin/bash" , check dmesg (attached).
>> Below message was wrote when trying to mount /usr :
>>> [   15.958645] EXT4-fs (sde3): Unrecognized mount option "auto" or missing 
>>> value
> 
> That error message doesn't make sense.
> The fstab you attached contains
> 
>> UUID=c9d2e9cb-c214-4ca0-bdc9-40d39233e700   /usr   ext4 
>> defaults,noatime   0   2
> 
> There is no "auto" keyword there. Have you attached the correct fstab?

Please include /etc/initramfs-tools/initramfs.conf as well, so we know
if you are using busybox or not.

In general, please be much more verbose and describe what you are doing
and the *exact* error messages you get.

It's tiresome to ask for everything.


-- 
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#845350: sks no longer creates pidfile

[Andrew Gallagher]

On 22/11/16 17:54, Daniel Kahn Gillmor wrote:
> 
> You're using systemd, and sks should be running under the control of
> systemd.

That addresses my use case, but not the case of someone using
traditional init - is this not supported?

Thanks!

A



signature.asc
Description: OpenPGP digital signature

Bug#845302: systemd: 232-6:Failed to boot, makes kernel panic when starting /sbin/init.

[K.Ohta]

Dear Michael,
I change line 323 of /usr/share/initramfs-tools/init,
"sleep 15" (or another wait period),and uncomment below line
of /etc/fstab (and another /usr entry is commented)
>UUID=c9d2e9cb-c214-4ca0-bdc9-40d39233e700   /usr   ext4 
>defaults,noatime   0   2

Then, booting is okay with below messages.
>[5.602383] EXT4-fs (sdd3): mounted filesystem with ordered data mode. 
>Opts: (null)
>[   20.702527] EXT4-fs (sde3): mounted filesystem with ordered data mode. 
>Opts: (null)
sdd3 is / , sde3 is /usr .

It seems to look any wrong response...

Regards,
Ohta.


On Wed, 23 Nov 2016 19:49:40 +0900
"K.Ohta"  wrote:

> Sorry, I booted *older* fetab entry;
> 
> Not booting with,
> >> UUID=c9d2e9cb-c214-4ca0-bdc9-40d39233e700 /usr ext4
> >> defaults,noatime   0   2
> Booting with uncommenting below line.
> >>UUID=c9d2e9cb-c214-4ca0-bdc9-40d39233e700 /usr ext4
> >>rw,noatime,suid,dev,exec,auto,nouser,async 0 2
> I will retry your saying with "defaults,noatime".Please wait.
> Ohta.
> 
> On Wed, 23 Nov 2016 11:41:21 +0100
> Michael Biebl  wrote:
> 
> > Am 23.11.2016 um 11:25 schrieb K.Ohta:  
> > > Dear Michael,
> > > 
> > > Not mounted /usr and made kernel panic still longer sleep.
> > > 
> > > Then booting with "init=/bin/bash" , check dmesg (attached).
> > > Below message was wrote when trying to mount /usr :
> > >> [   15.958645] EXT4-fs (sde3): Unrecognized mount option "auto"
> > >> or missing value
> > 
> > That error message doesn't make sense.
> > The fstab you attached contains
> >   
> > > UUID=c9d2e9cb-c214-4ca0-bdc9-40d39233e700   /usr
> > > ext4 defaults,noatime   0   2
> > 
> > There is no "auto" keyword there. Have you attached the correct
> > fstab?
> > 
> > 
> > 
> >   
> 

[0.00] Linux version 4.8.0-1-amd64 (debian-ker...@lists.debian.org) 
(gcc version 5.4.1 20161019 (Debian 5.4.1-3) ) #1 SMP Debian 4.8.7-1 
(2016-11-13)
[0.00] Command line: BOOT_IMAGE=/vmlinuz-4.8.0-1-amd64 
root=UUID=040b41b0-26fe-4064-af0a-3619f3112096 ro vga=0x3d4 
video=vesafb:yrap,noresume quiet systemd.debug-shell iommu=soft vga=0x3d4 
systemd.legacy_systemd_cgroup_controller=yes
[0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point 
registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[0.00] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, 
using 'standard' format.
[0.00] x86/fpu: Using 'eager' FPU context switches.
[0.00] e820: BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0009] usable
[0.00] BIOS-e820: [mem 0x0010-0xbdf03fff] usable
[0.00] BIOS-e820: [mem 0xbdf04000-0xbe4e1fff] reserved
[0.00] BIOS-e820: [mem 0xbe4e2000-0xbe8d5fff] ACPI NVS
[0.00] BIOS-e820: [mem 0xbe8d6000-0xbedebfff] reserved
[0.00] BIOS-e820: [mem 0xbedec000-0xbee28fff] type 20
[0.00] BIOS-e820: [mem 0xbee29000-0xbee29fff] usable
[0.00] BIOS-e820: [mem 0xbee2a000-0xbf02] ACPI NVS
[0.00] BIOS-e820: [mem 0xbf03-0xbf452fff] usable
[0.00] BIOS-e820: [mem 0xbf453000-0xbf7f3fff] reserved
[0.00] BIOS-e820: [mem 0xbf7f4000-0xbf7f] usable
[0.00] BIOS-e820: [mem 0xfec0-0xfec00fff] reserved
[0.00] BIOS-e820: [mem 0xfec1-0xfec10fff] reserved
[0.00] BIOS-e820: [mem 0xfec2-0xfec20fff] reserved
[0.00] BIOS-e820: [mem 0xfed0-0xfed00fff] reserved
[0.00] BIOS-e820: [mem 0xfed61000-0xfed70fff] reserved
[0.00] BIOS-e820: [mem 0xfed8-0xfed8] reserved
[0.00] BIOS-e820: [mem 0xfef0-0x] reserved
[0.00] BIOS-e820: [mem 0x00011000-0x00043eff] usable
[0.00] NX (Execute Disable) protection: active
[0.00] efi: EFI v2.31 by American Megatrends
[0.00] efi:  ACPI=0xbe8c5000  ACPI 2.0=0xbe8c5000  SMBIOS=0xf04c0  
MPS=0xfd550 
[0.00] SMBIOS 2.7 present.
[0.00] DMI: To Be Filled By O.E.M. To Be Filled By O.E.M./990FX 
Extreme4, BIOS P2.70 06/05/2014
[0.00] e820: update [mem 0x-0x0fff] usable ==> reserved
[0.00] e820: remove [mem 0x000a-0x000f] usable
[0.00] AGP: No AGP bridge found
[0.00] e820: last_pfn = 0x43f000 max_arch_pfn = 0x4
[0.00] MTRR default type: uncachable
[0.00] MTRR fixed ranges enabled:
[0.00]   0-9 write-back
[0.00]   A-B write-through
[0.00]   C-D6FFF write-protect
[0.00]   D

Bug#845372: qtbase-opensource-src: Please enable m68k in double-conversion

[John Paul Adrian Glaubitz]

On 11/23/2016 11:43 AM, Dmitry Shachnev wrote:
> In case of #780430, it looks like Lisandro wants the patch to be reviewed
> by upstream first, and you said you could forward it. Is there any update
> on that?

No, not yet, unfortunately. I will try to do it this week.

> In case of #844722, I would just ask you to NMU it. Though I am not listed
> as Uploader, so let’s wait for what Lisandro says first.

That would be great. I have the package ready already, so I just need to
build and upload.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913



signature.asc
Description: OpenPGP digital signature

Bug#845431: RFP: stream2chromecast -- A Chromecast media streamer for Linux

[Ph. Marek]

Package: wnpp
Severity: wishlist

* Package name: stream2chromecast
  Version : none yet
  Upstream Author : Pat-Carter
* URL : https://github.com/Pat-Carter/stream2chromecast
* License : GPLv3
  Programming Lang: Python
  Description : A Chromecast media streamer for Linux

A Chromecast media streamer for Linux.
Stream2Chromecast casts audio and video files to a Chromecast device from Linux.
It can also transcode any unsupported files in real time and play them on the 
Chromecast.
It is written in Python 2.7 and uses either ffmpeg or avconv for transcoding.


Might be a better solution than "castnow" 
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813736) because it looks 
actively maintained.

Thank you very much!

Bug#845302: systemd: 232-6:Failed to boot, makes kernel panic when starting /sbin/init.

[Michael Biebl]

Am 23.11.2016 um 12:00 schrieb K.Ohta:
> Dear Michael,
> I change line 323 of /usr/share/initramfs-tools/init,
> "sleep 15" (or another wait period),and uncomment below line
> of /etc/fstab (and another /usr entry is commented)
>> UUID=c9d2e9cb-c214-4ca0-bdc9-40d39233e700   /usr   ext4 
>> defaults,noatime   0   2
> 
> Then, booting is okay with below messages.
>> [5.602383] EXT4-fs (sdd3): mounted filesystem with ordered data mode. 
>> Opts: (null)
>> [   20.702527] EXT4-fs (sde3): mounted filesystem with ordered data mode. 
>> Opts: (null)
> sdd3 is / , sde3 is /usr .
> 
> It seems to look any wrong response...

So I guess the "sleep 15" wasn't necessary after all and the problem was
actually an fstab entry which was not understand by busybox' mount

Can you drop the "sleep 15" again and retry


(Btw, if you use an additional option, like noatime, you no longer use
the defaults, so you can just as well drop "defaults" completely)


-- 
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#845430: maxima: Maxima's online help is unreachable

[Emmanuel Charpentier]

Package: maxima
Version: 5.38.1-6
Severity: normal

Dear Maintainer,

The latest (5.38.1.6) version of the maxima* packages have no useable online
help.

Symptom : gibberish at the sart of a session (both in console or in emacs via
imaxima) :


charpent@SAP5057241:~$ maxima

Warning: SIMPLE-WARNING: Maxima is unable to set up the help system.
(Details: CL-INFO::LOAD-PRIMARY-INDEX: Condition in CL-INFO::LOAD-PRIMARY-INDEX
[or a callee]: INTERNAL-SIMPLE-UNBOUND-VARIABLE: Cell error on
|�]�SGR�=U�&L�%�Vb="��]R1n��+-v��E��O�.

�4
 ^.�$1߼z��
Maxima encountered a Lisp error:

 Condition in CL-INFO::LOAD-PRIMARY-INDEX [or a callee]: INTERNAL-SIMPLE-ERROR:
Format error: illegal directive.



  V
"Maxima is unable to set up the help system.
(Details: CL-INFO::LOAD-PRIMARY-INDEX: Condition in CL-INFO::LOAD-PRIMARY-INDEX
[or a callee]: INTERNAL-SIMPLE-UNBOUND-VARIABLE: Cell error on
|�]�SGR�=U�&L�%�Vb="��]R1n��+-v��E��O�.

�4

^.�$1߼z��~��QQ=Ye��l�ٷy�G���#�:��y��{��犦e_Ï~�o٣�^�z~�gϾg��.^W?���9{}Q���=?���O��+�짧o�>{�����o��>��3�9[f��2�G���1����h�Ξ��iQe]�Y�.�U�u՞�61����1�^��(ˬ67غ��k��#���1%,�6J�L�:2��f5��)`�ǙM#�u�5�tR϶x>8o�(��JVm�U]�a��Z;
[���ۺ��ա��+X/���RY+?+�ռ���F8����S�|:
Unbound variable: )
"

Automatically continuing.
To enable the Lisp debugger set *debugger-hook* to nil.
Maxima 5.38.1 http://maxima.sourceforge.net
using Lisp GNU Common Lisp (GCL) GCL 2.6.12
Distributed under the GNU Public License. See the file COPYING.
Dedicated to the memory of William Schelter.
The function bug_report() provides bug reporting information.
(%i1) ? solve

Maxima encountered a Lisp error:

 Condition in MACSYMA-TOP-LEVEL [or a callee]: INTERNAL-SIMPLE-FILE-ERROR: File
error on "/home/camm/maxima-5.38.1/doc/info/maxima.info-1": Cannot open

Automatically continuing.
To enable the Lisp debugger set *debugger-hook* to nil.
(%i2)


* In emacs via imaxima, the Maxima info tree *is* reacheable through the menu
entry.
* Both in imaxima and in console, the online help is unusable (see above).

   * What led up to the situation?

Installing latest maxima packages from unstable on top of a current Stretch
system.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Nothing



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

Kernel: Linux 4.8.0-1-amd64 (SMP w/2 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 maxima depends on:
ii  libc6 2.24-5
ii  libgmp10  2:6.1.1+dfsg-1
ii  libreadline7  7.0-1
ii  libx11-6  2:1.6.3-1

Versions of packages maxima recommends:
ii  gnuplot-x11   5.0.5+dfsg1-4
ii  maxima-share  5.38.1-6

Versions of packages maxima suggests:
ii  maxima-doc5.38.1-6
ii  maxima-emacs  5.38.1-6
pn  texmacs   
ii  tk [wish] 8.6.0+9
ii  xmaxima   5.38.1-6

-- no debconf information

Bug#845432: RM: buildapp [armhf] -- ROM; Depends on sbcl

[Christoph Egger]

Package: ftp.debian.org
Severity: normal

Hi!

Please remove buildapp on armhf so sbcl can be removed (#844269) there

Thanks!

  Christoph

Bug#845433: uwsgi: Upgrade fails with RUN_AT_STARTUP=no

[Mathias Behrle]

Package: uwsgi
Version: 2.0.14+20161106-1
Severity: normal

Dear Maintainer,

when the flag
RUN_AT_STARTUP=no
is set in /etc/default/uwsgi, the upgrade fails with

uwsgi (2.0.14+20161106-1) wird eingerichtet ...
Job for uwsgi.service failed because the control process exited with
error code.
See "systemctl status uwsgi.service" and "journalctl -xe" for details.
invoke-rc.d: initscript uwsgi, action "start" failed.
● uwsgi.service - LSB: Start/stop uWSGI server instance(s)
   Loaded: loaded (/etc/init.d/uwsgi; generated; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2016-11-23 12:00:12
   CET; 3ms ago
   Docs: man:systemd-sysv-generator(8)
   Process: 15729 ExecStart=/etc/init.d/uwsgi start
   (code=exited, status=2) CPU: 16ms
   Nov 23 12:00:12 monsterix systemd[1]: Starting LSB:
   Start/stop uWSGI server instance(s)...
   Nov 23 12:00:12 monsterix uwsgi[15729]: Starting app
   server(s): uwsgi (disabled; see /etc/default/uwsgi)
   failed!
   Nov 23 12:00:12 monsterix systemd[1]: uwsgi.service:
   Control process exited, code=exited status=2
   Nov 23 12:00:12 monsterix systemd[1]: Failed to start
   LSB: Start/stop uWSGI server instance(s).
   Nov 23 12:00:12 monsterix systemd[1]: uwsgi.service:
   Unit entered failed state.
   Nov 23 12:00:12 monsterix systemd[1]: uwsgi.service:
   Failed with result 'exit-code'.
   dpkg: Fehler beim Bearbeiten des Paketes uwsgi
   (--configure):
   Unterprozess installiertes post-installation-Skript
   gab den Fehlerwert 1 zurück
   Fehler traten auf beim Bearbeiten von:
 uwsgi


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

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

Versions of packages uwsgi depends on:
ii  uwsgi-core  2.0.14+20161106-1

uwsgi recommends no packages.

uwsgi suggests no packages.

-- no debconf information

Bug#818107: [Python-apps-team] Bug#818107: The future of DocOnce

[Klaus Zimmermann]

Hi,

this looks like an interesting project indeed.
As a first step I went through the list of dependencies that Kristian provided.
The situation might not be so grim.
Unfortunately, there is no information about the actually required versions,
but for a number of packages a manual update over the available distribution
version seems to have been necessary.
For now I just collected those packages, that are not available in Debian
at all. If version bumps for existing packages turn out to be necessary,
let's deal with that later.

The list is:
 Publish:
 - pip install -e hg+https://bitbucket.org/logg/publish#egg=publish
 Sphinx themes:
 - pip install -e 
hg+https://bitbucket.org/miiton/sphinxjp.themes.solarized#egg=sphinxjp.themes.solarized
 - pip install -e 
git+https://github.com/shkumagai/sphinxjp.themes.impressjs#egg=sphinxjp.themes.impressjs
 - pip install -e 
git+https://github.com/kriskda/sphinx-sagecell#egg=sphinx-sagecell
 Runestone:
  - pip install sphinxcontrib-paverutils
  - pip install cogapp
  - pip install -e 
git+https://bitbucket.org/hplbit/pygments-ipython-console#egg=pygments-ipython-console
  - pip install -e 
git+https://github.com/hplgit/pygments-doconce#egg=pygments-doconce

Questions:
Kristian:
 - Is the required version of all the packages listed in [1] known?
 - Can any of the above mentioned packages be considered optional?

Anyone:
 - Is any of the aforementioned projects packaged under a non-obvious name?
 - Particularly, is the ipython pygment lexer contained in some ipython/jupyter 
package?


Cheers
Klaus



[1] 
https://github.com/hplgit/doconce/blob/master/doc/src/manual/debpkg_doconce.txt


On 07/11/2016 21:57, Francesco Poli wrote:
> On Mon, 7 Nov 2016 17:03:07 + Kristian Gregorius Hustad wrote:
> 
>> Version 1.0.0 is now listed at https://github.com/hplgit/doconce/releases 
> 
> That's awesome, thanks a lot!   :-)
> 
> Now I hope the Debian Python Applications Packaging Team will consider
> packaging it...
> 
> 
> 
> ___
> Python-apps-team mailing list
> python-apps-t...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-apps-team
> 



signature.asc
Description: OpenPGP digital signature

Bug#845434: RFS: sphinxcontrib-doxylink/1.3-2 [RC]

[Ghislain Vaillant]

Package: sponsorship-requests
Severity: important

Dear mentors,

I am looking for a sponsor for my package "sphinxcontrib-doxylink"

* Package name: sphinxcontrib-doxylink
  Version : 1.3-2
  Upstream Author : Matt Williams
* URL : http://pythonhosted.org/sphinxcontrib-doxylink/
* License : BSD
  Section : python

It builds those binary packages:

  python-sphinxcontrib.doxylink - Sphinx extension for linking to 
Doxygen documentation (Python 2)
  python3-sphinxcontrib.doxylink - Sphinx extension for linking to 
Doxygen documentation (Python 3)


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


  https://mentors.debian.net/package/sphinxcontrib-doxylink

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

  dget -x 
https://mentors.debian.net/debian/pool/main/s/sphinxcontrib-doxylink/sphinxcontrib-doxylink_1.3-2.dsc


Successful build on debomatic:


http://debomatic-amd64.debian.net/distribution#unstable/sphinxcontrib-doxylink/1.3-2/autopkgtest

Changes since the last upload:

  * Add patch fixing FTBFS with recent versions of pyparsing.
Thanks to Paul McGuire for the patch (Closes: #841582)
  * Upgrade packaging to debhelper 10.
  * Simplify the packaging testsuite.
  * Drop superfluous Testsuite field.

Regards,
Ghislain Vaillant

Bug#845435: I can not connect a client to the server during a networked game

[Nouveau Jean-Christophe]

Package: glob2
Version: 0.9.4.4-2.3

Dear Maintainer,

There is a bug on globulation2 in the debian jessie pakage.
I have testing it on many computers in 32 or 64bits.
When i try to install the wheezy pakage there is no bug.

The bug appear when i try to play globulation with two computers.
On the server i create a game and i wait after client.
When the client is connected, the start buton on the server is blinking
and i cant start the game.


-- System Information:

Debian Release: 8.6

APT prefers stable-updates

APT policy: (500, 'stable-updates'), (500, 'stable')

Architecture: amd64 (x86_64)


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

Bug#845438: pbuilder: bogus filename output, possible format string vulnerability

[Thorsten Glaser]

Package: pbuilder
Version: 0.226.1
Severity: important

I: new cache content 'x11-common_10x0p+07.7+17_all.deb' added

-rw-r--r-- 1 root root 251250 Nov 23 00:40 
/var/cache/pbuilder/aptcache-debian/x11-common_1%3a7.7+17_all.deb

I am assuming '%3a' is interpreted by printf(1) here.
Never pass user strings as printf format strings…

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

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

Versions of packages pbuilder depends on:
ii  debconf [debconf-2.0]  1.5.59
ii  debootstrap1.0.87
ii  dpkg-dev   1.18.15
ii  wget   1.18-4

Versions of packages pbuilder recommends:
ii  devscripts  2.16.8
ii  eatmydata   105-5
ii  fakeroot1.21-2
ii  iproute24.8.0-1
ii  net-tools   1.60+git20150829.73cef8a-2
ii  sudo1.8.17p1-2

Versions of packages pbuilder suggests:
ii  cowdancer   0.81
pn  gdebi-core  

-- debconf information excluded

Bug#845436: dpkg-dev: dpkg-buildpackage leaves spurious debian/files in source tree

[Thorsten Glaser]

Package: dpkg-dev
Version: 1.18.15
Severity: minor

Run: dpkg-buildpackage -S -d -nc

Watch this:

tglase@tglase-nb:~/squirrel-sql $ svn st
?   debian/files
tglase@tglase-nb:~/squirrel-sql $ cat debian/files
squirrel-sql_3.2.0+dfsg-1_source.buildinfo java optional

This file should not be there AIUI. Even .pc/ is automatically
cleaned up and all quilt patches unapplied again, as it should
be, but this one’s missing.

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

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

Versions of packages dpkg-dev depends on:
ii  binutils  2.27.51.20161118-2
ii  bzip2 1.0.6-8
ii  libdpkg-perl  1.18.15
ii  make  4.1-9
ii  patch 2.7.5-1
pn  perl:any  
ii  tar   1.29b-1.1
ii  xz-utils  5.2.2-1.2

Versions of packages dpkg-dev recommends:
ii  build-essential  12.2
ii  fakeroot 1.21-2
ii  gcc [c-compiler] 4:6.2.1-1
ii  gcc-6 [c-compiler]   6.2.1-4
ii  gnupg2.1.16-2
ii  gnupg2   2.1.16-2
ii  gpgv 2.1.16-2
pn  libalgorithm-merge-perl  
ii  tcc [c-compiler] 0.9.27~git20151227.933c223-1

Versions of packages dpkg-dev suggests:
ii  debian-keyring  2016.09.04

-- no debconf information

Bug#845437: liblorene-dev: definition of __infinity is buggy (FTBFS on alpha)

[Thibaut Paumard]

Package: liblorene-dev
Version: 0.0.0~cvs20160908+dfsg-2
Severity: normal
Tags: pending

Upstream maintains a number of definitions of __infinity based on a
mixture of architecture and platform.

However this list is incomplete (does not contain all the Debian
architectures), is buggy (FTBFS on Debian alpha) and defaults to some
random value.

The safest way seems to unconditionally use INFINITY from cmath, what
upstream do in there __linux case, which has a lower priority than their
__alpha__ case.

Regards, Thibaut.

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

Kernel: Linux 4.6.0-0.bpo.1-amd64 (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages liblorene-dev depends on:
ii  giza-dev  0.9.4-3
ii  libfftw3-dev  3.3.5-1
ii  libgsl-dev [libgsl0-dev]  2.2.1+dfsg-1
ii  liblapack-dev 3.6.1-2
ii  liblorene-debian0 0.0.0~cvs20160908+dfsg-2
ii  liblorene-export-debian0  0.0.0~cvs20160908+dfsg-2
ii  liblorenef77-debian0  0.0.0~cvs20160908+dfsg-2
ii  libx11-dev2:1.6.3-1

Versions of packages liblorene-dev recommends:
ii  gfortran  4:6.1.1-1

Versions of packages liblorene-dev suggests:
ii  lorene-codes-src  0.0.0~cvs20160908+dfsg-2
pn  lorene-doc

-- no debconf information

Bug#841612: libmodpbase64-dev: modp_stdint.h is missing

[Lennart Weller]

The modp_stdint.h is not installed on non-Windows systems. It just defines some 
standard storage names also available in stdint.h. Including it in the install 
seems nonsensical.

Bug#845425: DataSource no longer accessible since jessie security update

[Emmanuel Bourg]

Hi Arne,

Thank you for reporting this issue. Could you check if it also occurs
with the tomcat7 package from jessie-backports please?

Emmanuel Bourg

Bug#845439: [PATCH] Don’t enforce (U)EFI on arm64

[Michael Stapelberg]

Package: vmdebootstrap
Version: 1.7-1
Severity: wishlist
Tags: patch

The Raspberry Pi 3 uses arm64 but comes with a custom bootloader, so
there is no need for UEFI.

Please consider merging the attached patch. Thank you!

Without this patch, my vmdebootstrap invocation fails with the error
message “ERROR: Only UEFI is supported on arm64”.

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

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

Versions of packages vmdebootstrap depends on:
ii  debootstrap 1.0.81
ii  kpartx  0.6.2-2
ii  libjs-sphinxdoc 1.4.8-1
ii  parted  3.2-15
ii  python-cliapp   1.20160724-1
ii  python-distro-info  0.14
ii  python2.7   2.7.12-2
pn  python:any  
ii  qemu-utils  1:2.7+dfsg-3+b1

Versions of packages vmdebootstrap recommends:
ii  dosfstools4.0-2
pn  extlinux  
ii  grub2-common  2.02~beta2-36
pn  python-guestfs
pn  qemu-system   
ii  qemu-user-static  1:2.7+dfsg-3+b1
pn  squashfs-tools

Versions of packages vmdebootstrap suggests:
pn  cmdtest   
pn  mbr   
pn  pandoc
pn  u-boot:armhf  

-- no debconf information
>From 1d70f88536654e98ced993a107fbb8f7ffb2 Mon Sep 17 00:00:00 2001
From: Michael Stapelberg 
Date: Wed, 23 Nov 2016 12:36:11 +0100
Subject: [PATCH] =?UTF-8?q?Don=E2=80=99t=20enforce=20(U)EFI=20on=20arm64?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The Raspberry Pi 3 uses arm64 but comes with a custom bootloader, so
there is no need for UEFI.
---
 vmdebootstrap/constants.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/vmdebootstrap/constants.py b/vmdebootstrap/constants.py
index 9f39415..3d807c6 100644
--- a/vmdebootstrap/constants.py
+++ b/vmdebootstrap/constants.py
@@ -46,7 +46,7 @@ arch_table = {  # pylint: disable=invalid-name
 'package': 'grub-efi-arm64',
 'bin_package': 'grub-efi-arm64-bin',
 'extra': None,
-'exclusive': True,
+'exclusive': False,
 'target': 'arm64-efi',
 }
 }
-- 
2.9.3

Bug#844081: [Python-apps-team] Bug#844081: Which FS was this run on?

[Filip Pytloun]

Hello,

I am using ZFS and building in pbuilder chroot and wasn't able to reproduce it
this way.

This may be also related to caching of underlying host as reporter is running
the build in VM - having more info about environment may help to find
reproducer.

Filip

On 2016/11/21 15:52, Christian Geier wrote:
> Hi,
> what filesystem did you run this on?
> 
> The issue here is, that mtimes that should change, didn't (at least not
> as far as python is concerned), event though there is a sleep(0.01)
> (which does not *have* to be accurate, but usually is a bit larger)
> between reading the mtime, modifying the data and re-reading the mtime .
> 
> Best regards,
> Christian Geier
> 
> ___
> Python-apps-team mailing list
> python-apps-t...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-apps-team
> 


signature.asc
Description: Digital signature

Bug#843543: [Pkg-tigervnc-devel] Bug#843543: Bug#843543: tigervnc: FTBFS with xserver 1.19

[Ola Lundqvist]

Hi

Thank you for the information. Now we just have to fix it. :-)

// Ola

On 22 November 2016 at 23:57, Emilio Pozuelo Monfort 
wrote:

> Control: severity -1 serious
>
> On 08/11/16 22:04, Emilio Pozuelo Monfort wrote:
> > On 07/11/16 17:40, Ben Hildred wrote:
> >>
> >>
> >> On Mon, Nov 7, 2016 at 9:13 AM, Emilio Pozuelo Monfort <
> po...@debian.org
> >> > wrote:
> >>
> >> Source: tigervnc
> >> Version: 1.6.0+dfsg-4
> >> Severity: important
> >>
> >> Hi,
> >>
> >> I rebuilt your package against xserver 1.19 (2:1.18.99.901-1 to be
> precise,
> >> note we have 2:1.18.99.902-1 in experimental now) and it failed to
> build,
> >> particularly it failed to apply the patches to the new xserver:
> >>
> >> Hunk #1 succeeded at 161 with fuzz 2 (offset 36 lines).
> >> Hunk #2 FAILED at 153.
> >> Hunk #3 FAILED at 215.
> >> Hunk #4 FAILED at 226.
> >> 3 out of 4 hunks FAILED -- saving rejects to file os/WaitFor.c.rej
> >> debian/rules:126: recipe for target
> >> 'unix/xserver/.apply-patches-vnc-patch-xorg.stamp' failed
> >>
> >> (full log attached)
> >>
> >> I see there is a new upstream release, so it may be good to look at
> that
> >> for xserver 1.19 compatibility.
> >>
> >> I have seen a fix for this in the upstream change history. I cannot
> remember if
> >>   it made it into 1.7 or not from the top of my head.
> >
> > I saw some patches in upstream github too[1]. IIRC they were not in the
> last
> > release, but they can probably be backported?
> >
> > [1]
> > https://github.com/TigerVNC/tigervnc/commit/
> 3fed95eda27dfbeee6535f987f5d14a66f64749b
>
> I just uploaded xserver 1.19 to sid, so this is RC.
>
> Cheers,
> Emilio
>
> ___
> Pkg-tigervnc-devel mailing list
> pkg-tigervnc-de...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-tigervnc-devel
>



-- 
 - Ola Lundqvist ---
/  o...@debian.org Folkebogatan 26  \
|  o...@inguza.com  654 68 KARLSTAD  |
|  http://inguza.com/  +46 (0)70-332 1551   |
\  gpg/f.p.: 7090 A92B 18FE 7994 0C36  4FE4 18A1 B1CF 0FE5 3DD9 /
 ---

Bug#845201: Patch for Lintian updates for Rust packaging in /usr/share/cargo/registry

[Josh Triplett]

Control: tags -1 + patch

The attached patch implements these changes.

- Josh Triplett
>From 55a882e6f878e1071e29d91a8f5a52eeb84d3884 Mon Sep 17 00:00:00 2001
From: Josh Triplett 
Date: Wed, 23 Nov 2016 03:48:50 -0800
Subject: [PATCH] Exclude files under /usr/share/cargo/registry/ from a few
 checks

That directory contains unmodified upstream sources.
(Closes: #845201)
---
 checks/files.pm   | 5 -
 checks/scripts.pm | 1 +
 debian/changelog  | 5 +
 3 files changed, 10 insertions(+), 1 deletion(-)

diff --git a/checks/files.pm b/checks/files.pm
index b19b3bf..50b6381 100644
--- a/checks/files.pm
+++ b/checks/files.pm
@@ -1218,6 +1218,8 @@ sub run {
 and not $fname =~ m,^usr/share/man/(?:[^/]+/)?man\d/,o
 # liblicense (again)
 and not $fname =~ m,^usr/share/pyshared-data/,o
+# Rust crate unmodified upstream sources
+and not $fname =~ m,^usr/share/cargo/registry/,o
 # Some GNOME/GTK software uses these to show the "license
 # header".
 and not $fname =~ m,
@@ -1365,7 +1367,8 @@ sub run {
 }
 
 #  vcs control files
-if ($fname =~ m,$VCS_FILES_OR_ALL,) {
+if ($fname =~ m,$VCS_FILES_OR_ALL,
+and $fname !~ m,^usr/share/cargo/registry/,) {
 tag 'package-contains-vcs-control-file', $file;
 }
 
diff --git a/checks/scripts.pm b/checks/scripts.pm
index f40fddd..bf1700f 100644
--- a/checks/scripts.pm
+++ b/checks/scripts.pm
@@ -311,6 +311,7 @@ sub run {
 or $filename =~ m,^usr/(?:lib|share)/.*\.pm,
 or $filename =~ m,^usr/(?:lib|share)/.*\.py,
 or $filename =~ m,^usr/(?:lib|share)/ruby/.*\.rb,
+or $filename =~ m,^usr/share/cargo/registry/,
 or $filename =~ m,^usr/share/debconf/confmodule(?:\.sh)?$,
 or $filename =~ m,\.in$,
 or $filename =~ m,\.erb$,
diff --git a/debian/changelog b/debian/changelog
index eeeaef0..1c87d05 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -20,6 +20,11 @@ lintian (2.5.50) UNRELEASED; urgency=medium
   * data/files/privacy-breaker-websites:
 + [BR] Detect more logos.
 
+  * checks/{files,scripts}.pm:
++ [JT] Exclude files under /usr/share/cargo/registry/ from a few checks,
+  as that directory contains unmodified upstream sources.
+  (Closes: #845201)
+
  -- Niels Thykier   Wed, 26 Oct 2016 20:42:18 +
 
 lintian (2.5.49) unstable; urgency=medium
-- 
2.10.2

Bug#843402: reprepro cannot handle .changes files that reference .buildinfo files

[Stephan Sürken]

On Tue, 22 Nov 2016 19:08:06 +0100 =?utf-8?q?Sl=C3=A1vek_Banko?= 
 wrote:
> Dne út 22. listopadu 2016 Stephan Sürken napsal(a):

(...)

> without "Tracking", buildinfo files are not processed - "reprepro include" 
> ignores them.
> 
> With "Tracking: minimal" (without "includebuildinfos") and with "Permit: 
> unused_files" (see workaround from message 10), buildinfo files are not 
> processed - "reprepro processincoming" ignores them.

thx, that's what I thought. Seems the patch still has some issues when
tracking is configured.

> However, I thought that the purpose of the patch was to add support for 
> processing buildinfos.

Imho, the main purpose should be to make such new changes installable
at all again, with or without actually processing buildinfo files.

But I guess you are right, Guillem's patch also seems to try to process
them.

Let's keep him in good mood by more excellent feedback so he might
improve it ;).

Hth,

S

Bug#845302: systemd: 232-6:Failed to boot, makes kernel panic when starting /sbin/init.

[K.Ohta]

Dear Michael,


On Wed, 23 Nov 2016 12:09:22 +0100
Michael Biebl  wrote:

> Am 23.11.2016 um 12:00 schrieb K.Ohta:
> > Dear Michael,
> > I change line 323 of /usr/share/initramfs-tools/init,
> > "sleep 15" (or another wait period),and uncomment below line
> > of /etc/fstab (and another /usr entry is commented)  
> >> UUID=c9d2e9cb-c214-4ca0-bdc9-40d39233e700   /usr
> >> ext4 defaults,noatime   0   2  
> > 
> > Then, booting is okay with below messages.  
> >> [5.602383] EXT4-fs (sdd3): mounted filesystem with ordered
> >> data mode. Opts: (null) [   20.702527] EXT4-fs (sde3): mounted
> >> filesystem with ordered data mode. Opts: (null)  
> > sdd3 is / , sde3 is /usr .
> > 
> > It seems to look any wrong response...  
> 
> So I guess the "sleep 15" wasn't necessary after all and the problem
> was actually an fstab entry which was not understand by busybox' mount

At last, I understood (sorry...)
I removed "nouser" and "auto" from /usr entry of fstab,
they are not supported musybox's mount command.
>UUID=c9d2e9cb-c214-4ca0-bdc9-40d39233e700   /usr   ext4 
>rw,noatime,suid,dev,exec,async 0   2

Booting was succeeded.
Then, add "nouser" or "auto", booting was failed, I confirmed.
Maybe, this issue was resolved, sorry for my miss...

> 
> Can you drop the "sleep 15" again and retry
> 
> 
> (Btw, if you use an additional option, like noatime, you no longer use
> the defaults, so you can just as well drop "defaults" completely)
> 
> 
Thanks , I removed "default" to add async etc..

Cheers,
Ohta.


pgp466iMThLAW.pgp
Description: OpenPGP digital signature

Bug#845302: systemd: 232-6:Failed to boot, makes kernel panic when starting /sbin/init.

[Michael Biebl]

Can you confirm that boot is successful after you remove the "sleep 15"
again and rebuild the initramfs via update-initramfs -u.


-- 
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#845425: DataSource no longer accessible since jessie security update

[Arne Nordmark]

Den 2016-11-23 kl. 12:36, skrev Emmanuel Bourg:
> Hi Arne,
> 
> Thank you for reporting this issue. Could you check if it also occurs
> with the tomcat7 package from jessie-backports please?

Thanks for the quick reply.

No, with version 7.0.73-1~bpo8+1 I do not have this problem. I guess
this indicates a problem with backporting the patch to 7.0.56.

> 
> Emmanuel Bourg
> 

Arne

Bug#845440: RFS: patat/0.4.0.0-1

[Félix Sipma]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "patat":

  patat - Terminal-based presentations using Pandoc

Package: patat
Version: 0.4.0.0-1
Upstream Author: Jasper Van der Jeugt 
Homepage: http://github.com/jaspervdj/patat
License: GPL-2
Section: haskell


Download with dget:

dget -x 
https://mentors.debian.net/debian/pool/main/p/patat/patat_0.4.0.0-1.dsc

Or build it with gbp:

gbp clone --pristine-tar https://git.gueux.org/patat.git
cd patat
gbp buildpackage

Thanks.


signature.asc
Description: PGP signature

Bug#845382: more boot BUG logs

[Václav Ovsík]

I added netconsole into /boot/grub/grub.cfg and did more attempts to
boot. Logs are attached in the archive.

 zito@bobek:~$ fgrep -m 1 BUG radeon-kms-messages*
 radeon-kms-messages.txt:[   64.148004] NMI watchdog: BUG: soft lockup - CPU#1 
stuck for 22s! [kworker/1:2:51]
 radeon-kms-messages1.txt:[   14.147686] BUG: unable to handle kernel NULL 
pointer dereference at 006c
 radeon-kms-messages2.txt:[   15.379376] BUG: unable to handle kernel NULL 
pointer dereference at 006c
 radeon-kms-messages3.txt:[   13.890714] BUG: unable to handle kernel NULL 
pointer dereference at 006c
 radeon-kms-messages4.txt:[   14.579563] BUG: unable to handle kernel NULL 
pointer dereference at 006c
 radeon-kms-messages5.txt:[   15.651245] BUG: unable to handle kernel NULL 
pointer dereference at 006c
 radeon-kms-messages6.txt:[   48.148004] NMI watchdog: BUG: soft lockup - CPU#1 
stuck for 22s! [smartd:457]
 radeon-kms-messages7.txt:[   15.472800] BUG: unable to handle kernel NULL 
pointer dereference at 006c
 radeon-kms-messages8.txt:[   14.282438] BUG: unable to handle kernel NULL 
pointer dereference at 006c
 radeon-kms-messages9.txt:[   14.860173] BUG: unable to handle kernel NULL 
pointer dereference at 006c

There is NULL pointer dereference in most cases.
-- 
Zito


radeon-kms-messages.tar.xz
Description: application/xz

Bug#845201: [Pkg-rust-maintainers] Patch for Lintian updates for Rust packaging in /usr/share/cargo/registry

[Sylvestre Ledru]

Le 23/11/2016 à 12:58, Josh Triplett a écrit :

Control: tags -1 + patch

The attached patch implements these changes.

 Having a test would be great!
Thanks for doing that
Sylvestre

Bug#845441: tftpd-hpa tries to start before filesystems are mounted and aborts

[MI]

Package: tftpd-hpa
Version: 5.2+20140608-3

On Debian Jessie, the tftpd-hpa server is started (by systemd) before the filesystems 
are mounted.


There is no systemd unit file in the tftpd-hpa package, so the /etc/init.d/tftpd-hpa 
script is used. However, the "INIT INFO" section in the script seems to be ignored:


### BEGIN INIT INFO
# Provides:tftpd-hpa
# Required-Start:$local_fs $remote_fs $syslog $network
...

The log:

$ journalctl -u tftpd-hpa
-- Reboot --
Nov 22 08:02:34 r530a systemd[1]: Starting LSB: HPA's tftp server...
Nov 22 08:02:36 r530a tftpd-hpa[1396]: Starting HPA's tftpd: in.tftpd/docs/pxe 
missing, aborting.
Nov 22 08:02:40 r530a systemd[1]: tftpd-hpa.service: control process exited, 
code=exited status=1

Nov 22 08:02:40 r530a systemd[1]: Failed to start LSB: HPA's tftp server.
Nov 22 08:02:40 r530a systemd[1]: Unit tftpd-hpa.service entered failed 
state.

I'm not sure if this could actually be considered a systemd bug, but anyway, it is 
probably more efficient to just add a systemd unit file to the package? Or maybe 
there is some other way to make sure that tftpd is started when everything it needs 
is available?


Mi

Bug#845302: systemd: 232-6:Failed to boot, makes kernel panic when starting /sbin/init.

[K.Ohta]

I already removed "sleep 15" from /usr/share/initramfs-tools/init, and
re-built initramfs, booting was completed.
Sorry for lacking write.

Cheers,
Ohta

On Wed, 23 Nov 2016 13:26:22 +0100
Michael Biebl  wrote:

> Can you confirm that boot is successful after you remove the "sleep
> 15" again and rebuild the initramfs via update-initramfs -u.
> 
> 



pgpYQRfhVpalz.pgp
Description: OpenPGP digital signature

Bug#838441: Advertencia de la cuenta final

[1]

le hemos enviado varios correos electrónicos para actualizar su cuenta de 
correo electrónico, y te hemos ignorado. por favor, vamos a cerrar esta cuenta 
de usuario si no verifica dentro de las 24 horas
Abra el Administrador del sitio siguiente para actualizado su cuenta de correo 
electrónico ahora.  http://www.c0rreo-admin.com/

Bug#841291: [Pkg-libvirt-maintainers] Bug#841291: libvirt-bin: qemu backport v2.6 needs a backported version of libvirt-bin in Jessie

[Mathieu Tarral]

Hi Guido,


> Will do as soon as I get around to it. Thanks for letting us know!
>
> Any updates regarding this bug ?
Did you find some time to patch libvirt and test QEMU with it ?

Thanks !


-- 
Mathieu Tarral

Bug#845425: DataSource no longer accessible since jessie security update

[Emmanuel Bourg]

Le 23/11/2016 à 12:54, Arne Nordmark a écrit :

> Thanks for the quick reply.
> 
> No, with version 7.0.73-1~bpo8+1 I do not have this problem. I guess
> this indicates a problem with backporting the patch to 7.0.56.

Did you enable the security manager?

Bug#559867: [pkg-java] r19181 - in trunk/squirrel-sql/debian: . patches

[Thorsten Glaser]

On Tue, 22 Nov 2016, Emmanuel Bourg wrote:

> I see the package was initially checked into Subversion. Feel free to
> migrate it to Git if you want, we have a migration script available for

OK, the package is now moved there.

- To work on this package:
  git clone git+ssh://git.debian.org/git/pkg-java/squirrel-sql

- Read-only access:
  git clone https://anonscm.debian.org/git/pkg-java/squirrel-sql.git

- Browser access:
  https://anonscm.debian.org/cgit/pkg-java/squirrel-sql.git

The package compiles under Debian sid/amd64 now and needs
- testing
- review (including legal)
- possibly, upload to experimental
- updating to later versions
- an actual maintainer

I’m not a Java™ expert, I just jumped in because I now actually
need this software for a course I’m attending at work (normally
I just use psql CLI), so I’m not likely going to maintain it.

This work was fully sponsored by my employer (see signature).

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

Bug#794890: [Pkg-javascript-devel] Bug#794890: npm: new upstream version

[Michael Prokop]

Disclaimer: I'm not blaming nor pointing to anyone, but I feel like
that this is yet again the team pattern and I'd really like to see
whether we have any way out of this...

* Jérémy Lal [Tue Nov 15, 2016 at 11:27:02PM +0100]:

> > Is really no one from the Debian Javascript Maintainers working on
> > the npm packaging or interested in having an up2date version
> > available for stretch? Are there any known blockers?

> Besides "takes a lot of time", no.
> The amount of work needed to complete that task is simply discouraging :( 
> Help !

I looked into it and as Paolo mentioned in this bugreport (see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794890#44) many
new packages would have to be packaged to get a newer npm package
into Debian. But it seems to also require updating *existing*
packages. Looking at e.g. the current state of the node-request
dependency (~2.78.0):

% rmadison node-request
node-request | 2.26.1-1  | stable  | source, all
node-request | 2.26.1-1  | stable-kfreebsd | source, all
node-request | 2.26.1-1  | testing | source, all
node-request | 2.26.1-1  | unstable| source, all

... I'm afraid the situation of node-* packages in Debian is worse
than I expected. node-request's upstream release of version 2.26.1
dates back to August 2013 and nowadays upstream is at version 2.79.
There's #844072 against node-request (where someone is asking for a
newer version of node-request in Debian), but it was filed just this
month (November 2016) and between 2013 and 2016 there was not a
single package upload for node-request in Debian.

Asking around what other Debian contributors and users usually do when
they've to deal with npm + nodejs: either "npm install -g npm"(sic!)
and then use npm to install the actual node packages or directly
head towards upstream (like https://deb.nodesource.com/setup_4.x).

Now one reason why we have node-* packages in Debian is that they
are dependencies of further packages. To have some numbers: I see
601 packages named "node-*" in sid/amd64 as of today, and when
looking at their reverse dependencies I see only those 24 binary
packages with node-* packages in their depends/recommends/suggests:

* chai
* cleancss
* emscripten
* flightgear-phi
* fonts-font-awesome
* gis-osm
* groovebasin
* grunt
* jison
* lava-dev
* libjs-jquery-ui-docs
* libjs-util
* libjs-validator
* livescript
* mocha
* nikola
* npm
* npm2deb
* python-livereload
* python-webassets
* python3-livereload
* python3-webassets
* twitter-recess
* ycmd

Reducing it to dependencies only (no recommends or suggests) we
seem to have only those 18 packages left:

* chai
* cleancss
* emscripten
* flightgear-phi
* fonts-font-awesome
* groovebasin
* grunt
* jison
* lava-dev
* libjs-jquery-ui-docs
* libjs-util
* libjs-validator
* livescript
* mocha
* npm
* npm2deb
* twitter-recess

[JFTR: I didn't consider and look into build-depends for my numbers
and didn't verify my list with UDD or similar yet. If my numbers are
wrong please correct me.]

I might be wrong (please correct me), but my impression is that
people are uploading node-* packages mainly to satisfy a
(build-)dependency they have in a package and then don't really care
about those packages any longer. I also count 196 node-* packages
without *any* rdepends on them (http://paste.grml.org/2868/ is the
full list), aren't people working on those things interested in an
up2date npm package?

Back to the npm situation: I was reporting
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794890#34 because
Debian's npm can't be really used reliably nowadays (the
"@module/names" not supported at all). Looking through the
bugreports of the npm package I'd call it unmaintained, there's even
an open CVE (https://security-tracker.debian.org/tracker/CVE-2016-3956).
The last upload was in 2014 and no one felt to call for help with
its packaging since then (especially now with stretch freeze on our
horizon), orphan the package etc. or am I missing something here?

Overall, I'm not sure we are providing our users something good with
the current situation. Though what realistic options do we have get
forward here? Any thoughts?

regards,
-mika-


signature.asc
Description: Digital signature

Bug#845443: jessie-pu: package nss-pam-ldapd/0.9.4-3+deb8u2

[Salvatore Bonaccorso]

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

Hi Stable release managers,

X-Debbugs-CC to Arthur de Jong and Ferenc Wágner.

nss-pam-ldapd's nslcd under the conditions as described in #814881
might fail to restart. nslcd restart which is stop+start with systemd,
is racy, and might lead to nslcd not running after a restart. Ferenc
has posted his analysis in https://bugs.debian.org/814881#39
confirming that the debdiff fixes the issue.

The proposed debian/changelog is

+nss-pam-ldapd (0.9.4-3+deb8u2) stable; urgency=medium
+
+  * Non-maintainer upload.
+  * have init script stop action only return when nslcd has actually stopped
+(Closes: #814881)
+
+ -- Salvatore Bonaccorso   Wed, 09 Nov 2016 13:48:14 +0100

and attached is the propsed debdiff.

Would it be acceptable to include in for the next jessie point
release?

Regards,
Salvatore
diff -Nru nss-pam-ldapd-0.9.4/debian/changelog nss-pam-ldapd-0.9.4/debian/changelog
--- nss-pam-ldapd-0.9.4/debian/changelog	2016-01-19 21:17:44.0 +0100
+++ nss-pam-ldapd-0.9.4/debian/changelog	2016-11-09 13:48:14.0 +0100
@@ -1,3 +1,11 @@
+nss-pam-ldapd (0.9.4-3+deb8u2) stable; urgency=medium
+
+  * Non-maintainer upload.
+  * have init script stop action only return when nslcd has actually stopped
+(Closes: #814881)
+
+ -- Salvatore Bonaccorso   Wed, 09 Nov 2016 13:48:14 +0100
+
 nss-pam-ldapd (0.9.4-3+deb8u1) stable; urgency=low
 
   * fix-issues-withdaemonising.patch, avoid-signal-race.patch: patches to
diff -Nru nss-pam-ldapd-0.9.4/debian/nslcd.init nss-pam-ldapd-0.9.4/debian/nslcd.init
--- nss-pam-ldapd-0.9.4/debian/nslcd.init	2016-01-19 19:50:51.0 +0100
+++ nss-pam-ldapd-0.9.4/debian/nslcd.init	2016-11-09 13:48:14.0 +0100
@@ -96,7 +96,7 @@
   if [ "$K5START_START" = "yes" ]
   then
 log_daemon_msg "Stopping $K5START_DESC" "k5start"
-start-stop-daemon --stop --oknodo --pidfile $K5START_PIDFILE
+start-stop-daemon --stop --oknodo --retry 10 --pidfile $K5START_PIDFILE
 log_end_msg $?
 # remove any left behind files
 [ -n "$K5START_PIDFILE" ] && rm -f $K5START_PIDFILE
@@ -129,7 +129,7 @@
 stop)
   # stop nslcd
   log_daemon_msg "Stopping $NSLCD_DESC" "$NSLCD_NAME"
-  start-stop-daemon --stop --oknodo \
+  start-stop-daemon --stop --oknodo --retry 10 \
 --pidfile $NSLCD_PIDFILE \
 --name "$NSLCD_NAME"
   log_end_msg $?

Bug#845380: calibre: GUI does not start, QXcbConnection errors

[Ritesh Raj Sarraf]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On Tue, 2016-11-22 at 21:37 +, Joe Rowan wrote:
> Package: calibre
> Version: 2.71.0+dfsg-1
> Severity: important
> 
> Dear Maintainer,
> 
> GUI does not open, /usr/bin/calibre appears in process list. If run from
> terminal, these errors appear:

This is odd. I have the same version, and it works for me here.


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

iQIzBAEBCgAdFiEEQCVDstmIVAB/Yn02pjpYo/LhdWkFAlg1ltsACgkQpjpYo/Lh
dWkWBg//djHwNsE3KLekVhfiQaJZ4V4+s4x7EORn1VnNjphsw/SFx/4xuOoM0WX0
t6NhpyltPL/m8TPIF60+fMObx0GiQ+rV4ltnG0sBstlv7KQvusf31CGfBW5E1QYK
UeJ06k12l9cOKaXeoewvPyzRHjjgKFpy2RnyCZkwlRLtYq9EPfFAgsUkvX45v8lF
APVEKrsjibIJiOUmAdctju/dDY0ueWjFIJ/7QYM54hYEIQiQtddeCL6VowhIfdqY
26muV3wbbgqscjEYAY+QDW0JJQqUHYIy+/niMjIDmYCEzYciI4thT/9X/+/xL3ng
MkX80zHuQcDoXpm8sJ/7uU/xkx032/pfdsbO37wu9p1Ze3SZqpUG88pjtJ/3466b
pSeJPXAQxLbdhY7SoRktPEcT0XC3orNN3cNWNGbVU3zIawsmerpkFFZyhJBHqJNo
k2bS3tBW+90HmcWqWOK+8QscdRL6FyaI9vFAQRDjCrWyBid2nJe+VjcJToENHrg4
l6JYCsSB35t/Q4yDV/HTRF4sd/cGomEZyImdwmUFKM2YdX0TpnLCpegQEQ9SwGu1
8i52ky8PdOt9yV3Q2XixeCom6mTTdIoRWpRsIHdvamQNhp9KU9NGnFr2V63VGIkd
iBMJMqElASMS33K3S9dzxrlZEFRdSUnrBMV+/K9+ROiTmZAf7tI=
=hReN
-END PGP SIGNATURE-

Bug#845443: jessie-pu: package nss-pam-ldapd/0.9.4-3+deb8u2

[Salvatore Bonaccorso]

Hi

On Wed, Nov 23, 2016 at 02:19:24PM +0100, Salvatore Bonaccorso wrote:
> The proposed debian/changelog is
> 
> +nss-pam-ldapd (0.9.4-3+deb8u2) stable; urgency=medium

FTR, I would do as well s/stable/jessie/g which I have already
locally.

Regards,
Salvatore

Bug#845425: DataSource no longer accessible since jessie security update

[Arne Nordmark]

Den 2016-11-23 kl. 14:09, skrev Emmanuel Bourg:
> Did you enable the security manager?

I have not changed that part of /etc/default/tomcat7, so it still reads

#TOMCAT7_SECURITY=no

which should imply that the security manager is not enabled.

Arne

Bug#845302: systemd: 232-6:Failed to boot, makes kernel panic when starting /sbin/init.

[Michael Biebl]

Control: reassign -1 initramfs-tools 0.125


Am 23.11.2016 um 11:25 schrieb K.Ohta:
> Not mounted /usr and made kernel panic still longer sleep.
> 
> Then booting with "init=/bin/bash" , check dmesg (attached).
> Below message was wrote when trying to mount /usr :
>> [   15.958645] EXT4-fs (sde3): Unrecognized mount option "auto" or missing 
>> value
> 
> If this message is correct, mount program included by initramfs
> has not recognized "auto" (or some another) option(s), regardless
> /bin/mount (or /sbin/mount/ext4) recognize this option(s) :-(


I'm going to reassign this to initramfs-tools as it uses mount
implementations from either klibc-utils or busybox which are both
incomplete and as a result, fail to mount /usr.

I decided against reassigning this to busybox and klibc-utils.
I think it's preferable, if initramfs-tools simply uses the mount
implementation from the real systemd, i.e. util-linux. This guarantees
that we won't run into such problems again in the future.

The mount utility is tiny, all its library dependencies are already in
the initramfs. Rebuilding the initramfs with mount from u-l increases
the size by 17K.

We would also have to make sure to use mount --move in
/usr/share/initramfs-tools/init for /run, /sys and /proc

Ben, what's your take on this?

Regards,
Michael

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



signature.asc
Description: OpenPGP digital signature

Bug#845378: unbound: Resolvconf script is not executable

[Christoph Pleger]

Hello,

> The resolvconf update.d hook for unbound is somewhat problematic, so it
> is disabled by default. Enabling or disabling a resolvconf update.d hook
> is done by setting or clearing the executable bit on the hook.

But when the executable bit is not set and resolvconf is installed, the
user ends up with no usable nameserver configuration after installation of
unbound, because resolv.conf only contains 127.0.0.1 (for the local
unbound) as nameserver entry and without further configuration unbound
does not know how to resolve names. That is, names cannot be resolved
anymore. Though this is not a big problem when no other package is
installed in the same "apt-get install" or so, it must be considered that
maybe other packages needing network access for configuration are
installed in the same apt-get run. So, the executable REALLY should be set
before unbound is started for the first time.

Regards
  Christoph

Bug#805612: akonadi-backend-mysql: It should depend on mysql-server-core but not mysql-client-core

[张 敬强]

在 2016年11月22日星期二 CST 下午6:16:22，您写道：
> can you please explain, why you think, we can remove the mysql-client-core
> dependency?
It's a bug can be resolved by just adding the *-server-core dependency,
as there is no such dependency when the bug was reported.

But I'm still wondering about the *-client-core dependency.
I found no mysql-client usage in files in akonadi-backend-mysql.
I didn't check all the code, but the old version 1.7.2-3 didn't depend on
*-client-core.
And akonadi-backend-sqlite has no dependency on sqlite3, so I guess
there may be no need of the mysql client binaries. 
> akonadi is starting a server by it self and also connects to it,
> so for me it makes sense, that akonadi also needs mysql-client-core to
> work. Have you tested a system without mysql-client-core?
I just renamed the 3 binaries (mysql, mysql_embeded, mysqlcheck),
and rebooted, and found that kmail/akregator work as normal,
and "akonadictl fsck" work well too. I didn't test the setup.
How about make it a suggest instead of depend/recommend?

Bug#845445: mutter: illegal instruction error

[dark yux]

Package: mutter
Version: 3.14.4-1~deb8u1
Severity: important

Dear Maintainer,

When trying to use mutter I receive a illegal instruction error. Try this with 
two terminals:

Terminal 1:
Xephyr -ac -br -noreset -screen 800x600 :1

Terminal 2:
mutter -d :1

I expected Mutter functioning within a Xephyr window. Instead I got: "[1]
21548 illegal hardware instruction  mutter -d :1".

-- System Information:
Debian Release: 8.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
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 mutter depends on:
ii  gnome-themes-standard      3.14.2.2-1
ii  gsettings-desktop-schemas  3.14.1-1
ii  libc6                      2.19-18+deb8u6
ii  libclutter-1.0-0           1.20.0-1
ii  libglib2.0-0               2.42.1-1+b1
ii  libmutter0e                3.14.4-1~deb8u1
ii  libx11-6                   2:1.6.2-3
ii  libxcomposite1             1:0.4.4-1
ii  mutter-common              3.14.4-1~deb8u1
ii  zenity                     3.14.0-1
Versions of packages mutter recommends:
ii  openbox [x-session-manager]  3.5.2-8
Versions of packages mutter suggests:
ii  gnome-control-center  1:3.14.2-3
ii  xdg-user-dirs         0.15-2
 

Bug#794890: [Pkg-javascript-devel] Bug#794890: npm: new upstream version

[Jérémy Lal]

Thank you for tackling the issue. See my answer below.

2016-11-23 14:18 GMT+01:00 Michael Prokop :
> Disclaimer: I'm not blaming nor pointing to anyone, but I feel like
> that this is yet again the team pattern and I'd really like to see
> whether we have any way out of this...
>
> * Jérémy Lal [Tue Nov 15, 2016 at 11:27:02PM +0100]:
>
>> > Is really no one from the Debian Javascript Maintainers working on
>> > the npm packaging or interested in having an up2date version
>> > available for stretch? Are there any known blockers?
>
>> Besides "takes a lot of time", no.
>> The amount of work needed to complete that task is simply discouraging :( 
>> Help !
>
> I looked into it and as Paolo mentioned in this bugreport (see
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794890#44) many
> new packages would have to be packaged to get a newer npm package
> into Debian. But it seems to also require updating *existing*
> packages. Looking at e.g. the current state of the node-request
> dependency (~2.78.0):
>
> % rmadison node-request
> node-request | 2.26.1-1  | stable  | source, all
> node-request | 2.26.1-1  | stable-kfreebsd | source, all
> node-request | 2.26.1-1  | testing | source, all
> node-request | 2.26.1-1  | unstable| source, all

I know it's just an example, but i started working on updating
node-request last week.


> ... I'm afraid the situation of node-* packages in Debian is worse
> than I expected. node-request's upstream release of version 2.26.1
> dates back to August 2013 and nowadays upstream is at version 2.79.
> There's #844072 against node-request (where someone is asking for a
> newer version of node-request in Debian), but it was filed just this
> month (November 2016) and between 2013 and 2016 there was not a
> single package upload for node-request in Debian.
>
> Asking around what other Debian contributors and users usually do when
> they've to deal with npm + nodejs: either "npm install -g npm"(sic!)
> and then use npm to install the actual node packages or directly
> head towards upstream (like https://deb.nodesource.com/setup_4.x).
>
> Now one reason why we have node-* packages in Debian is that they
> are dependencies of further packages. To have some numbers: I see
> 601 packages named "node-*" in sid/amd64 as of today, and when
> looking at their reverse dependencies I see only those 24 binary
> packages with node-* packages in their depends/recommends/suggests:
>
> * chai
> * cleancss
> * emscripten
> * flightgear-phi
> * fonts-font-awesome
> * gis-osm
> * groovebasin
> * grunt
> * jison
> * lava-dev
> * libjs-jquery-ui-docs
> * libjs-util
> * libjs-validator
> * livescript
> * mocha
> * nikola
> * npm
> * npm2deb
> * python-livereload
> * python-webassets
> * python3-livereload
> * python3-webassets
> * twitter-recess
> * ycmd
>
> Reducing it to dependencies only (no recommends or suggests) we
> seem to have only those 18 packages left:
>
> * chai
> * cleancss
> * emscripten
> * flightgear-phi
> * fonts-font-awesome
> * groovebasin
> * grunt
> * jison
> * lava-dev
> * libjs-jquery-ui-docs
> * libjs-util
> * libjs-validator
> * livescript
> * mocha
> * npm
> * npm2deb
> * twitter-recess
>
> [JFTR: I didn't consider and look into build-depends for my numbers
> and didn't verify my list with UDD or similar yet. If my numbers are
> wrong please correct me.]
>
> I might be wrong (please correct me), but my impression is that
> people are uploading node-* packages mainly to satisfy a
> (build-)dependency they have in a package and then don't really care
> about those packages any longer. I also count 196 node-* packages
> without *any* rdepends on them (http://paste.grml.org/2868/ is the
> full list), aren't people working on those things interested in an
> up2date npm package?

I believe as well it is true for most of them.
Bundling dependencies (only when upstream actually takes care of
updating them when doing a release) would solve the issue in many ways.

> Back to the npm situation: I was reporting
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794890#34 because
> Debian's npm can't be really used reliably nowadays (the
> "@module/names" not supported at all). Looking through the
> bugreports of the npm package I'd call it unmaintained, there's even
> an open CVE (https://security-tracker.debian.org/tracker/CVE-2016-3956).
> The last upload was in 2014 and no one felt to call for help with
> its packaging since then (especially now with stretch freeze on our
> horizon), orphan the package etc. or am I missing something here?
>
> Overall, I'm not sure we are providing our users something good with
> the current situation. Though what realistic options do we have get
> forward here? Any thoughts?

Most, if not all, npm dependencies are shipped by upstream "bundled",
meaning they actually take care of updating the dependencies when
doing a release of npm.
That means it would be maintainable (and certainly much easier to do so)
by