Bug#772657: ttf-cjk-compact: build-depends on ruby1.8

2014-12-09 Thread Christian Hofstaedtler
* Cyril Brulebois k...@debian.org [141209 18:41]:
 Ralf Treinen trei...@pps.univ-paris-diderot.fr (2014-12-09):
  Source: ttf-cjk-compact
  Version: 1.20
  Severity: serious
  Tags: jessie
  User: trei...@debian.org
  Usertags: edos-uninstallable
  
  Hi,
  
  ttf-cjk-compact build-depends on ruby1.8, which does not exist in jessie.
  In fact, ruby1.8 was removed from testing on 2014-03-13.
 
 It really would be nice not to remove packages that are still
 build-depended on, especially when no bug reports are being filed.
 
 One month into the freeze isn't exactly the right time to attempt a 1.8
 to 1.9 (or whatever else is current this week) ruby transition in d-i
 packages.

AFAICT, ttf-cjk-compact 1.20 is not in jessie or sid.
ttf-cjk-compact 1.23 from jessie/sid depends on ruby, not ruby1.8.

From here it looks like there was no bug filed because 1.21 already
fixed this issue (in 2013) without us needing to file an additional
bug.

Best,
-- 
 ,''`.  Christian Hofstaedtler z...@debian.org
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-



pgpS6fzlhK6mT.pgp
Description: PGP signature


Bug#772657: ttf-cjk-compact: build-depends on ruby1.8

2014-12-09 Thread Christian Hofstaedtler
* Adam D. Barratt a...@adam-barratt.org.uk [141209 21:05]:
 On Tue, 2014-12-09 at 20:51 +0100, Christian Hofstaedtler wrote:
  * Cyril Brulebois k...@debian.org [141209 18:41]:
   Ralf Treinen trei...@pps.univ-paris-diderot.fr (2014-12-09):
Source: ttf-cjk-compact
Version: 1.20
Tags: jessie

  AFAICT, ttf-cjk-compact 1.20 is not in jessie or sid.
  ttf-cjk-compact 1.23 from jessie/sid depends on ruby, not ruby1.8.
 
 It's still in sid's Sources file, but marked as Extra-Source-Only.
 AFAICS, that's due to us having bumped stable's
 debian-installer-netboot-images (which was quite legitimately built
 against ttf-cjk-compact 1.20 and ruby1.8) in to sid and jessie during
 the last point release.

rmadison and dak ls (on coccia) both don't show any indication of
ttf-cjk-compact 1.20 being 'in' jessie/sid.
The BTS also thinks 1.20 as being in stable, and 1.23 being the
jessie/sid version.

apt-cache showsrc was showing me an 1.20 source package, but I
disregarded it with I may have wheezy sources configured in this
VM.

If the common tools fail at showing this, then I'm really at a loss
of tools and would like to request improvements to these tools.

 This is not a bug in the package, nor anything that can be fixed other
 than by a source upload of d-i-n-i for sid. I'm therefore going to close
 this report.
 
 (In general, it's worth checking such things aren't purely E-S-O: yes.)

Thanks for the explanation.

C.

-- 
 ,''`.  Christian Hofstaedtler z...@debian.org
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-



pgp4hXxfIxoRN.pgp
Description: PGP signature


Bug#769736: debian-installer: please provide 'Other' option for time zones

2014-11-15 Thread Christian Hofstaedtler
Package: debian-installer
Severity: wishlist

Please provide an easy way to select any other timezone apart from
those matching the selected region. I'd suggest adding 'Other' to
the short time zone list, which would jump to the full list.

I often just hit enter on the region selection (defaults to US) to
get 'American English' as the keyboard layout, but then I still want
Etc/UTC as the TZ.

Thank you for your consideration,
-- 
 ,''`.  Christian Hofstaedtler z...@debian.org
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-



pgpvoPerotKKU.pgp
Description: PGP signature


Bug#769738: debian-installer: Please automatically mount /usr in rescue mode

2014-11-15 Thread Christian Hofstaedtler
Package: debian-installer
Severity: wishlist

Rescue mode currently asks the user if she wants to mount a separate
/boot partition. The same should probably happen for /usr.
Preferably, this could be automatically detected (empty dirs and/or
entries in fstab in target?)

Thanks,
Christian


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20141116011929.2819.49740.report...@percival.namespace.at



Stop offering /usr in the partition usage list?

2014-11-09 Thread Christian Hofstaedtler
Hello debian-boot,

while trying out a daily jessie d-i snapshot, I noticed that the
where-do-you-want-to-mount-this-partition menu offers /usr.

Given current troubles with a split /usr and possible future
directions, maybe it'd be a good idea to stop offering this?
(Experts can still enter /usr manually...)

  Christian

-- 
 ,''`.  Christian Hofstaedtler z...@debian.org
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-



signature.asc
Description: Digital signature


Bug#768329: grub-common: Please enable splash for jessie

2014-11-06 Thread Christian Hofstaedtler
* Colin Watson cjwat...@debian.org [141106 16:06]:
 Control: reassign 768329 grub-installer
 
 On Thu, Nov 06, 2014 at 03:53:58PM +0100, Christian Hofstaedtler wrote:
  Please add the splash option to the Linux default command line, as
  just installing plymouth otherwise has no effect, and plymouth is the
  recommended solution for fixing bootup multiplexing issues (f.e.
  password prompting for encrypted disks).
 
 This is supposed to be handled by grub-installer, which is part of d-i.

I do want to note that the grub packaging appears to have default
command line handling for different distributions, and adding splash
there would have the benefit(?) of everybody getting it, regardless
how the system was installed (d-i, (grml-)debootstrap, etc.)

-- 
 ,''`.  Christian Hofstaedtler z...@debian.org
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-



signature.asc
Description: Digital signature


Re: Bug#740744: closing 740744 - dns323-firmware-tools still depends on ruby1.9.1

2014-04-12 Thread Christian Hofstaedtler
Control: reopen -1 
Control: notfixed -1 0.6-1

* Matt Palmer mpal...@debian.org [140412 13:03]:
 close 740744 0.6-1
 close 743787 0.6-1
 thanks

0.6-1 still Depends on ruby1.9.1, therefore I'm reopening this bug.

-- 
 ,''`.  Christian Hofstaedtler z...@debian.org
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-



pgpZmb98UHRnS.pgp
Description: PGP signature


Re: Bug#743787: dns323-firmware-tools: breaks armel d-i builds since ruby-defaults 1:2.0.0.1 hit unstable

2014-04-06 Thread Christian Hofstaedtler
* Cyril Brulebois k...@debian.org [140406 15:51]:
[ shuffling your message a bit ]
 since this upload[1],
  1. http://packages.qa.debian.org/r/ruby-defaults/news/20140330T152352Z.html

dns323-firmware-tools depends on ruby1.9.1 but then just uses
/usr/bin/ruby in the shebang, rendering the dependency on a specific
interpreter version useless and wrong.

 we're getting a failure when building the armel
 orion5x_network-console flavour:
 | mkdns323fw -k ./tmp/orion5x_network-console/dns-323/kernel.uboot -i 
 ./tmp/orion5x_network-console/dns-323/initrd.uboot -p 7 -c 1 -m 1 -o 
 ./dest/orion5x/network-console/d-link/dns-323/netboot.img
 | /usr/bin/mkdns323fw:73: invalid multibyte escape: 
 /^\x55\xAA(.{7})\0\x55\xAA$/
 | make[2]: *** [dns-323] Error 1

I haven't tried with actual files, but it looks like this change
might work on 1.9 and 2.0:

--- mkdns323fw~ 2014-04-07 00:07:27.560331402 +0200
+++ mkdns323fw  2014-04-07 00:08:39.796220588 +0200
@@ -70,7 +70,7 @@

# Return the signature of this firmware file.
def signature
-   if @signature =~ /^\x55\xAA(.{7})\0\x55\xAA$/
+   if @signature =~ 
Regexp.new(^\x55\xAA(.{7})\x55\xAA$.force_encoding(binary), 
Regexp::FIXEDENCODING)
return $1
else
raise RuntimeError.new(Unparseable signature string: 
#{@signature.inspect})


  -ch

-- 
 ,''`.  Christian Hofstaedtler z...@debian.org
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-



pgpux1RNDq3Dx.pgp
Description: PGP signature


Re: lenny Installer with PXE on HP DL360G5 / bnx2

2008-09-10 Thread Christian Hofstaedtler
On 2008-09-09 23:11:13, Jérémy Bobbio wrote:
 On Tue, Sep 09, 2008 at 03:29:42PM +0200, Christian Hofstaedtler wrote:
  How is one supposed to install from the network/PXE on such common
  hardware?
 
 You will need to add the firmware to the initrd.gz available on your
 TFTP server. You can find it in the bnx2-firmware package in the
 non-free section of the archive.  Then use gzip and cpio to extract and
 compress the image again:
 
  * Extract in current directory:
$ zcat /path/to/installer/initrd.gz | cpio -iv
   
  * Create a new image from the current directory:
$ find . -print0 | cpio -0 -H newc -ov | \
gzip -c  /path/to/installer/initrd.gz
 

I've tried this with the lenny installer daily build from today; on
amd64. Installation works, but:

- the firmware files on the installed system (in /lib/firmware) are owned 
  by the initial user, not by root.
  
- the firmware-bnx2 package is not installed, those files are not
  claimed by any package. I wonder how they will get updated, if
  needed?

Are these known issues or shall I write a bug report? (Didn't find any
bugs against debian-installer, but then that may be the wrong
package?)

BTW, the manual [1] doesn't seem to contain this info yet, may be
this should be added at some point?

Chris

[1] http://d-i.alioth.debian.org/manual/en.amd64/

-- 
Christian Hofstädtler
InQnet GmbH, Praterstrasse 31, Vienna, Austria



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



lenny Installer with PXE on HP DL360G5 / bnx2

2008-09-09 Thread Christian Hofstaedtler
Hello!

We've got quite a few machines from HP, of type ProLiant DL360 G5. We
used to install etch using the etch installer netboot media +
pxelinux. This worked quite fine.

Now I'm testing lenny (beta2 installer), and I found that the network 
cards in these servers (bnx2) seem to require a firmware, which is not 
in the installer image, but is available seperately. As the firmware is 
not in the image, and I'm booting from a PXE server, installing just
doesn't work (without plugging in an USB key, but that makes booting
from PXE quite useless).

Is this the intended behaviour?

How is one supposed to install from the network/PXE on such common
hardware?

Thanks,
Christian

-- 
Christian Hofstaedtler
InQnet GmbH, Praterstrasse 31, Vienna, Austria


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: lenny Installer with PXE on HP DL360G5 / bnx2

2008-09-09 Thread Christian Hofstaedtler
* Jérémy Bobbio [EMAIL PROTECTED] [080909 23:11]:
 On Tue, Sep 09, 2008 at 03:29:42PM +0200, Christian Hofstaedtler wrote:
  We've got quite a few machines from HP, of type ProLiant DL360 G5. We
  used to install etch using the etch installer netboot media +
  pxelinux. This worked quite fine.
  
  Now I'm testing lenny (beta2 installer), and I found that the network 
  cards in these servers (bnx2) seem to require a firmware, which is not 
  in the installer image, but is available seperately. As the firmware is 
  not in the image, and I'm booting from a PXE server, installing just
  doesn't work (without plugging in an USB key, but that makes booting
  from PXE quite useless).
 
 Please use the daily builds instead of beta2 to do your tests.  A lot of
 issues present in the beta 2 have been addressed since.

Will try again with those.

  Is this the intended behaviour?
 
 Yes: Debian is 100% free software and the firmware needed for bnx2 is
 not.  The other option would have been to completely remove the bnx2
 module from kernel shipped by Debian.

I fully understand. Why was this then OK for etch, but not for
lenny? (Not wanting to start a discussion about this, just want to 
know why things have changed.)

  How is one supposed to install from the network/PXE on such common
  hardware?
 
 You will need to add the firmware to the initrd.gz available on your
 TFTP server. You can find it in the bnx2-firmware package in the
 non-free section of the archive.  Then use gzip and cpio to extract and
 compress the image again:
 
  * Extract in current directory:
$ zcat /path/to/installer/initrd.gz | cpio -iv
   
  * Create a new image from the current directory:
$ find . -print0 | cpio -0 -H newc -ov | \
gzip -c  /path/to/installer/initrd.gz

Thanks for the instructions.

Chris


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]