[PATCH:di-autobuild] buildscript: Adjust sed call for dpkg 1.18.3

2015-09-28 Thread Cyril Brulebois 
This commit in dpkg led to a slightly variation in dpkg-checkbuilddeps's output:
| commit d287060bb1a45f5de33eb27034a7d8b27b039dbb
| Author: Guillem Jover 
| Date:   Thu Sep 17 18:14:00 2015 +0200
|
| scripts: Use error() and errormsg() instead of printing on STDERR directly
|
| This way any transformation done for error messages gets applied
| consistently to all error output.

The new pattern should support both variants.

Signed-off-by: Cyril Brulebois 
---
 buildscript | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Hi,

I'm not sure who exactly can pull this, so trying my luck with
debian-wb-team@ for now.

(No need to tell me how ugly this is.)

Confirmed to work fine on barriere (except for libpango's udeb being
uninstallable).

Thanks for your time.

Mraw,
KiBi.


diff --git a/buildscript b/buildscript
index fb35920..f787db4 100755
--- a/buildscript
+++ b/buildscript
@@ -60,7 +60,7 @@ install_build_deps() {
   dd-schroot-cmd -c "$SID" apt-get update
   (
 LANG=C schroot -q -c "$SID" -d "$HOME/di/build/$(basename 
"$INSTALLER_DIR")/checkout/build" -p -r -- dpkg-checkbuilddeps -B 
../debian/control 2>&1 || true
-  ) | sed -e 's%dpkg-checkbuilddeps: Unmet build dependencies: %%' -e 's, 
*([^)]*),,g' \
+  ) | sed -e 's%dpkg-checkbuilddeps: \(error: \)*Unmet build dependencies: %%' 
-e 's, *([^)]*),,g' \
 | DEBIAN_PRIORITY=critical DEBIAN_FRONTEND=noninteractive xargs 
dd-schroot-cmd -c "$SID" -y apt-get install
 }
 
-- 
2.1.4

Re: Bug#800014: multipath-udeb: not installable: depends on libsystemd0

2015-09-28 Thread Cyril Brulebois 
[ Adding debian-boot@lists.debian.org back. ]

Ritesh Raj Sarraf  (2015-09-28):
> Adding systemd maintainers
> 
> 
> Hello Cyril,
> 
> THank you for the bug report.
> 
> 
> On Fri, 2015-09-25 at 11:59 +0200, Cyril Brulebois wrote:
> > Package: multipath-udeb
> > Version: 0.5.0+git0.770e6d0d-3
> > Severity: grave
> > Justification: renders package unusable
> > 
> > 
> > [ Please keep debian-boot@lists.debian.org in the loop. ]
> > 
> > Hi,
> > 
> > Your package in unstable gained a dependency which cannot be
> > satisfied:
> > libsystemd0 has no udeb. It's therefore no longer installable, along
> > with partman-multipath which depends on it.
> 
> This was intentionally done because upstream added systemd dependency
> some time ago. For Jessie, I had disabled systemd support, but now, it
> makes sense to have it, and align with upstream and other
> distributions.
> 
> So, I think the real question is about why libsystemd0 does not have a
> udeb ?
> 
> systemd maintainers should provide that input.

Some input from someone who doesn't know a thing about systemd or
multipath: libmultipath.so.0 has a NEEDED entry on libsystemd.so.0,
which seems to only define symbols named sd_* (which seems fair). The
only use I see in libmultipath.so.0 is sd_listen_fds.

Its manpage says:

   sd_listen_fds() shall be called by a daemon to check for file
   descriptors passed by the init system as part of the socket-based
   activation logic.

There's no systemd in d-i, so there's no socket-based activation logic,
and you can't rely on that in your multipath udeb.

Mraw,
KiBi.


signature.asc
Description: Digital signature

Re: Bug#800014: multipath-udeb: not installable: depends on libsystemd0

2015-09-28 Thread Ritesh Raj Sarraf 
On Mon, 2015-09-28 at 18:53 +0200, Cyril Brulebois wrote:
> [ Adding debian-boot@lists.debian.org back. ]
> 

Sorry about that.


> > This was intentionally done because upstream added systemd
> > dependency
> > some time ago. For Jessie, I had disabled systemd support, but now,
> > it
> > makes sense to have it, and align with upstream and other
> > distributions.
> > 
> > So, I think the real question is about why libsystemd0 does not
> > have a
> > udeb ?
> > 
> > systemd maintainers should provide that input.
> 
> Some input from someone who doesn't know a thing about systemd or
> multipath: libmultipath.so.0 has a NEEDED entry on libsystemd.so.0,
> which seems to only define symbols named sd_* (which seems fair). The
> only use I see in libmultipath.so.0 is sd_listen_fds.
> 
> Its manpage says:
> 
>sd_listen_fds() shall be called by a daemon to check for file
>descriptors passed by the init system as part of the socket
> -based
>activation logic.
> 
> There's no systemd in d-i, so there's no socket-based activation
> logic,
> and you can't rely on that in your multipath udeb.


Hmmm... I'll look into it later. But when you say "No systemd in d-i",
does it mean that is how it is going to remain ?

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


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

Re: Bug#800014: multipath-udeb: not installable: depends on libsystemd0

2015-09-28 Thread Hendrik Boom 
On Mon, Sep 28, 2015 at 11:17:42PM +0530, Ritesh Raj Sarraf wrote:
> On Mon, 2015-09-28 at 18:53 +0200, Cyril Brulebois wrote:
> > [ Adding debian-boot@lists.debian.org back. ]
> > 
> 
> Sorry about that.
> 
> 
> > > This was intentionally done because upstream added systemd
> > > dependency
> > > some time ago. For Jessie, I had disabled systemd support, but now,
> > > it
> > > makes sense to have it, and align with upstream and other
> > > distributions.

For the sake of derivatives without systemd, you might see if it's 
practical to leave the systemd dependency optional.

-- hendrik

> > > 
> > > So, I think the real question is about why libsystemd0 does not
> > > have a
> > > udeb ?
> > > 
> > > systemd maintainers should provide that input.
> > 
> > Some input from someone who doesn't know a thing about systemd or
> > multipath: libmultipath.so.0 has a NEEDED entry on libsystemd.so.0,
> > which seems to only define symbols named sd_* (which seems fair). The
> > only use I see in libmultipath.so.0 is sd_listen_fds.
> > 
> > Its manpage says:
> > 
> >sd_listen_fds() shall be called by a daemon to check for file
> >descriptors passed by the init system as part of the socket
> > -based
> >activation logic.
> > 
> > There's no systemd in d-i, so there's no socket-based activation
> > logic,
> > and you can't rely on that in your multipath udeb.
> 
> 
> Hmmm... I'll look into it later. But when you say "No systemd in d-i",
> does it mean that is how it is going to remain ?
> 
> -- 
> Ritesh Raj Sarraf | http://people.debian.org/~rrs
> Debian - The Universal Operating System

Re: Bug#800014: multipath-udeb: not installable: depends on libsystemd0

2015-09-28 Thread Cyril Brulebois 
Ritesh Raj Sarraf  (2015-09-28):
> Hmmm... I'll look into it later. But when you say "No systemd in d-i",
> does it mean that is how it is going to remain ?

I'm not sure why there would be a need to change that in the near
future.

Mraw,
KiBi.


signature.asc
Description: Digital signature

Re: Bug#800356: libpango1.0-udeb: not installable: depends on libthai0

2015-09-28 Thread Cyril Brulebois 
Cyril Brulebois  (2015-09-28):
> Package: libpango1.0-udeb
> Version: 1.38.0-1
> Severity: grave
> Justification: renders package unusable
> 
> [ Please keep debian-boot@lists.debian.org in copy. ]
> 
> Hi,
> 
> Your package is no longer installable since it gained a dependency on a
> library package which has no udeb variant: libthai0.
> 
> This makes all these packages uninstallable:
>   cdebconf-gtk-entropy
>   cdebconf-gtk-terminal
>   cdebconf-gtk-udeb
>   gtk2-engines-udeb
>   libgtk2.0-0-udeb
>   libpango1.0-udeb
>   libvte9-udeb
>   matchbox-keyboard-udeb

Just to let debian-boot@ know: this was swiftly fixed, thanks!
  https://packages.qa.debian.org/p/pango1.0/news/20150928T153904Z.html

Mraw,
KiBi.


signature.asc
Description: Digital signature

Bug#800367: installation-report: stretch-testing on NEOWARE m100: no graphics

2015-09-28 Thread Andreas Glaeser 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


Package: installation-reports
Version: 2.60
Severity: minor

Dear Maintainer,

I still have to use VESA-graphics.


- -- Package-specific info:

Boot method: USB
Image version:
http://cdimage.debian.org/cdimage/weekly-builds/i386/iso-cd/debian-testing-i386-netinst.iso,
2015-09-28
Date: 
2015-09-28, about 11.00h to 15.00h

Machine: NEOWARE m100 mobile thin-client
Partitions: 
Filesystem Type 1K-blocksUsed Available Use% Mounted on
udev   devtmpfs 10240   0 10240   0% /dev
tmpfs  tmpfs986684636 94032   5% /run
/dev/sda1  btrfs 13670400 3476368   8246224  30% /
tmpfs  tmpfs   246668   0246668   0% /dev/shm
tmpfs  tmpfs 5120   4  5116   1% /run/lock
tmpfs  tmpfs   246668   0246668   0% /sys/fs/cgroup
tmpfs  tmpfs49336   4 49332   1% /run/user/113
tmpfs  tmpfs49336   0 49336   0% /run/user/0

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [o]
Detect network card:[o]
Configure network:  [o]
Detect CD:  [o]
Load installer modules: [o]
Clock/timezone setup:   [o]
User/password setup:[o]
Detect hard drives: [o]
Partition hard drives:  [o]
Install base system:[o]
Install tasks:  [o]
Install boot loader:[o]
Overall install:[o]

Comments/Problems:

I ordered a CF-to-IDE adapter and a 16GB CF-card from Hongkong, both arrived 
much sooner
than expected.
Now I fitted both into the mobile thinclient, which was tricky, because the 
drive-bay is
made for harddisks, which makes it difficult to fit the much smaller adapter 
with CF-card
in place. I didn't want to take apart the device, so I made my own tool for 
that from two
wood-sticks, an old CF-card, two rubber-rings and some adhesive tape, 
resembling tongs.
Using that it went quite well.
Installation was interrupted, because I was unaware, the client was running on 
batteries,
which ran out at some point. This caused more problems with installing 
task-xfce-desktop
and task-laptop, it would not work with tasksel anymore because of the 
interruption, only
with aptitude, then some dependency-troubles showed up, which were gone again 
upon system
reboot.
It' positive, that it's possible to go without the proprietary firmware now, 
even without
any non-free packages, but openchrome still does not work for me, as reported 
already
there:

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

the version in stable is: 1:0.3.3-1+b2, stretch has 1:0.3.3-1+b3

The X-server logfiles are attached [Xorg.0.log.openchrome.xz] and 
[Xorg.0.log.vesa.xz].

I continue using xorg.conf for VESA now, it is also attached [xorg.conf.xz].

- -- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="9 (stretch) - installer build 20150927-00:34"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux m100 4.1.0-2-586 #1 Debian 4.1.6-1 (2015-08-23) i686 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: VIA Technologies, Inc. 
CN700/VN800/P4M800CE/Pro
Host Bridge [1106:0314] lspci -knn: Subsystem: VIA Technologies, Inc.
CN700/VN800/P4M800CE/Pro Host Bridge [1106:0314] lspci -knn:Kernel driver in
use: agpgart-via lspci -knn: 00:00.1 Host bridge [0600]: VIA Technologies, Inc.
CN700/VN800/P4M800CE/Pro Host Bridge [1106:1314] lspci -knn: 00:00.2 Host 
bridge [0600]:
VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge [1106:2314] lspci 
-knn:
00:00.3 Host bridge [0600]: VIA Technologies, Inc. PT890 Host Bridge 
[1106:3208] lspci
- -knn: 00:00.4 Host bridge [0600]: VIA Technologies, Inc. 
CN700/VN800/P4M800CE/Pro Host
Bridge [1106:4314] lspci -knn: 00:00.7 Host bridge [0600]: VIA Technologies, 
Inc.
CN700/VN800/P4M800CE/Pro Host Bridge [1106:7314] lspci -knn: 00:01.0 PCI bridge 
[0604]:
VIA Technologies, Inc. VT8237/VX700 PCI Bridge [1106:b198] lspci -knn: 00:0b.0 
CardBus
bridge [0607]: Texas Instruments PCI1510 PC card Cardbus Controller [104c:ac56] 
lspci
- -knn: Subsystem: Packard Bell B.V. Device [1631:c018] lspci -knn: 
Kernel
driver in use: yenta_cardbus lspci -knn: 00:0c.0 Network controller [0280]: 
Ralink corp.
RT2561/RT61 rev B 802.11g [1814:0302] lspci -knn:   Subsystem: Device 
[18e8:6194]
lspci -knn: Kernel driver in use: rt61pci lspci -knn: 00:0f.0 IDE interface
[0101]: VIA Technologies,

Bug#800356: libpango1.0-udeb: not installable: depends on libthai0

2015-09-28 Thread Cyril Brulebois 
Package: libpango1.0-udeb
Version: 1.38.0-1
Severity: grave
Justification: renders package unusable

[ Please keep debian-boot@lists.debian.org in copy. ]

Hi,

Your package is no longer installable since it gained a dependency on a
library package which has no udeb variant: libthai0.

This makes all these packages uninstallable:
  cdebconf-gtk-entropy
  cdebconf-gtk-terminal
  cdebconf-gtk-udeb
  gtk2-engines-udeb
  libgtk2.0-0-udeb
  libpango1.0-udeb
  libvte9-udeb
  matchbox-keyboard-udeb

Mraw,
KiBi.

Processed: tagging 788062

2015-09-28 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 788062 + pending
Bug #788062 [os-prober] os-prober corrupts LVs/partitions while being mounted 
inside a VM
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#799883: [PATCH v3 0/2] Support probing on the Hurd

2015-09-28 Thread Samuel Thibault 
Control: tags -1 + pending

Applied, thanks!

Samuel

Processed: Re: Bug#799883: [PATCH v3 0/2] Support probing on the Hurd

2015-09-28 Thread Debian Bug Tracking System 
Processing control commands:

> tags -1 + pending
Bug #799883 [os-prober] [PATCH 0/2] Support probing on the Hurd
Added tag(s) pending.

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

Re: Bug#800081: cdrom: install from dvd set fails at choosing and installing software 8.2

2015-09-28 Thread Steve McIntyre 
Control: reassign -1 installation-reports

On Sat, Sep 26, 2015 at 04:27:20PM +0200, Ulisse wrote:
>Package: cdrom
>Severity: normal
>
>Dear Maintainer,
>
>After choosing xfce as debian desktop environment
>the installation works fine but report at the end
>that a failure has occured in the software installation
>and ask to retry or skip, how can i check what went wrong and fix it

Hi Ulisse,

If you switch to console 4 (ctrl-alt-F4), that console will be showing
the syslog from the installer. If you can report back with more
information from there, we should be able to help diagnose your
problems.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"We're the technical experts.  We were hired so that management could
 ignore our recommendations and tell us how to do our jobs."  -- Mike Andrews

Processed: Re: Bug#800081: cdrom: install from dvd set fails at choosing and installing software 8.2

2015-09-28 Thread Debian Bug Tracking System 
Processing control commands:

> reassign -1 installation-reports
Bug #800081 [cdrom] cdrom: install from dvd set fails at choosing and 
installing software 8.2
Bug reassigned from package 'cdrom' to 'installation-reports'.
Ignoring request to alter found versions of bug #800081 to the same values 
previously set
Ignoring request to alter fixed versions of bug #800081 to the same values 
previously set

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