Re: wpasupplicant udeb

[Glenn Saberton]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Frans Pop wrote:
> On Sunday 25 May 2008, Stefano Canepa wrote:
>> why did you comment out the madwifi driver?
>>  # Driver interface for madwifi driver
>> -CONFIG_DRIVER_MADWIFI=y
>> +#CONFIG_DRIVER_MADWIFI=y
>>  # Change include directories to match with the local setup
>> -CFLAGS += -I../debian/madwifi-headers
>> +#CFLAGS += -I../debian/madwifi-headers
>>
>> IIRC eeePC installer needs madwifi.
> 
> No, it needs the replacement of madwifi, which is ath5k. madwifi is a 
> non-free out-of-tree driver which we cannot support in D-I anyway.
> 
> Cheers,
> FJP

Beside that, madwifi actually uses wext. The old madwifi backend hasn't
been recommended for a long time, and afaik is still there because of
ubuntu.

Cheers

Glenn
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFIOgUuV8GyuTwyskMRArX/AJ932TotAsPzXgsQ41kvKy2P0hZcPwCfeuvQ
N/MnGDPewusvuBu9sY246Js=
=H/d1
-END PGP SIGNATURE-


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

tasksel 2.74 MIGRATED to testing

[Debian testing watch]

FYI: The status of the tasksel source package
in Debian's testing distribution has changed.

  Previous version: 2.73
  Current version:  2.74

-- 
This email is automatically generated; [EMAIL PROTECTED] is responsible.
See http://people.debian.org/~henning/trille/ for more information.


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

installation-guide 20080520 MIGRATED to testing

[Debian testing watch]

FYI: The status of the installation-guide source package
in Debian's testing distribution has changed.

  Previous version: 20080211
  Current version:  20080520

-- 
This email is automatically generated; [EMAIL PROTECTED] is responsible.
See http://people.debian.org/~henning/trille/ for more information.


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

Re: d-i status wrt i386 & amd64 EFI machines

[Julien BLACHE]

Frans Pop <[EMAIL PROTECTED]> wrote:

Hi,

> What other types of images are you thinking of? Could EFI support be added 
> to existing images or do we really need additional images?

Looks like I can answer your question after a few tests and some
googling on the spec.

Yes, it seems we can add EFI support to the current CD images and
don't need additional CD images. Adding an alternative El Torito boot
image is enough. The firmware is required by the spec to ignore legacy
boot entries. The Apple firmware presents the legacy entries and the
EFI entries, labelled as such.

That, of course, simplifies things quite a bit :)

JB.

-- 
 Julien BLACHE <[EMAIL PROTECTED]>  |  Debian, because code matters more 
 Debian & GNU/Linux Developer|   
 Public key available on  - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 


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

Re: wpasupplicant udeb

[Frans Pop]

On Sunday 25 May 2008, Stefano Canepa wrote:
> why did you comment out the madwifi driver?
>  # Driver interface for madwifi driver
> -CONFIG_DRIVER_MADWIFI=y
> +#CONFIG_DRIVER_MADWIFI=y
>  # Change include directories to match with the local setup
> -CFLAGS += -I../debian/madwifi-headers
> +#CFLAGS += -I../debian/madwifi-headers
>
> IIRC eeePC installer needs madwifi.

No, it needs the replacement of madwifi, which is ath5k. madwifi is a 
non-free out-of-tree driver which we cannot support in D-I anyway.

Cheers,
FJP


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

Re: wpasupplicant udeb

[Stefano Canepa]

Il giorno ven, 23/05/2008 alle 16.09 +0800, Glenn ha scritto:
> Ok, here it is. Its based on debians svn release of wpasupplicant as it
> has a patch which allows us to build without EAP. It will still build
> the deb and clients at the moment, which as stated earlier, some sort of
> seperate config needs to be made for the udeb.

Glenn,
why did you comment out the madwifi driver? 
 # Driver interface for madwifi driver
-CONFIG_DRIVER_MADWIFI=y
+#CONFIG_DRIVER_MADWIFI=y
 # Change include directories to match with the local setup
-CFLAGS += -I../debian/madwifi-headers
+#CFLAGS += -I../debian/madwifi-headers

IIRC eeePC installer needs madwifi.

Bye
Stefano

-- 
Stefano Canepa aka sc: [EMAIL PROTECTED] - http://www.stefanocanepa.it
Three great virtues of a programmer: laziness, impatience and hubris.
Le tre grandi virtù di un programmatore: pigrizia, impazienza e
arroganza. (Larry Wall)


signature.asc
Description: Questa è una parte del messaggio	firmata digitalmente

debian-installer_20080522_s390.changes ACCEPTED

[Debian Installer]

Accepted:
debian-installer-images_20080522_s390.tar.gz byhand
debian-installer_20080522_s390.deb
  to pool/main/d/debian-installer/debian-installer_20080522_s390.deb
Changes: debian-installer (20080522) unstable; urgency=low
 .
  [ Stephen R. Marenka ]
  * Add atari keymaps to pkg-lists for m68k.
 .
  [ Frans Pop ]
  * Lenny will be version 5.0.
  * Improve consistency between x86 syslinux bootmethod help screens.
  * Add nic-usb-modules to netboot images for x86 and ia64.
 .
  [ Otavio Salvador ]
  * Update to 2.6.24-1 kernel (i386, mipsel, arm, armel and amd64).
 .
  [ Robert Millan ]
  * Add images for the versatile platform (armel).
 .
  [ Martin Michlmayr ]
  * Activate the images for the MIPS Malta platform (mips and mipsel),
thanks Aurelien Jarno.
  * Remove the QEMU flavour on mips and mipsel since it's replaced
by Malta.
  * Update mips to 2.6.24-1.
  * Use initramfs rather than cramfs on Cobalt since the initrd is too
large.
  * Use initramfs on MIPS Malta.
 .
  [ Frans Pop ]
  * Remove dropped cdrom-modules kernel udebs from package list for i386,
amd64 and alpha.
  * Update to 2.6.24-1 kernel for alpha, hppa, ia64, powerpc, s390 and sparc.
  * Remove wireless-tools from package lists as it's not required to configure
wireless networking.
  * Remove Alastair McKinstry and Joshua Kwan as Uploaders with many thanks
for their past contributions.
 .
  [ Joey Hess ]
  * The i386 root floppy has been changed to a bare gzipped cpio file,
null-paddded to the end of the floppy. This needs rootskel-bootfloppy
version 1.60.
  * Use syslinux's vesamenu for all x86 images except the boot floppy.
  * Split up syslinux config files.
  * Note that the pxelinux config file for serial terminals has been dropped,
at least for now, since the split config files made it too difficult to
set up.
  * Note that this needs debian-cd changes to change its code for
merging syslinux configs when producing i386+amd64 CDs.
  * Document the irqpoll boot parameter. Closes: #477988
 .
  [ Frans Pop ]
  * For official builds, include a file with translation status information in
images to allow localechooser can warn users for incomplete translations.
A current status file should be generated before every upload.
 .
  [ Otavio Salvador ]
  * Use genisoimage instead of mkisofs.
  * Disable i386 floppy image since 2.6.24 kernel image is too big to fit
on a floppy.
 .
  [ Frans Pop ]
  * Include both version number and codename as release identification.
  * Add a version.info file inside netboot tarballs. Closes: #475774.
 .
  [ Otavio Salvador ]
  * Add cdebconf-text-entropy to common EXTRAUDEBS variable and
cdebconf-gtk-entropy on all gtk images.


Override entries for your package:
debian-installer_20080522_s390.deb - optional devel



Thank you for your contribution to Debian.


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

Processing of debian-installer_20080522_s390.changes

[Archive Administrator]

debian-installer_20080522_s390.changes uploaded successfully to localhost
along with the files:
  debian-installer_20080522_s390.deb
  debian-installer-images_20080522_s390.tar.gz

Greetings,

Your Debian queue daemon


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

Bug#311136: Account Update

[[EMAIL PROTECTED]]

Dear User,
 We wrote to you on Friday, April 25 2008 advising that you change the
 password on your account in order to prevent any unauthorised
 account access following the network intrusion we previously
 communicated.

 we have found the vulnerability that caused this issue, and have
 instigated a system wide security audit to improve and enhance our
 current security, in order to continue using our services you are
 require to update you account details below.

 To complete your account verification, you must reply to this email
 immediately and enter your account details below.

 Username: (**)
 
 Password: (**)


 Failure to do this will immediately render your account
 deactivated from our database.
 We apologise for the inconvenience that this will cause you during
 this period, but trust you understand that our primary concern is for our
 customers and for the security of their data.

 Umn Support Team 






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

Re: d-i status wrt i386 & amd64 EFI machines

[Julien BLACHE]

Frans Pop <[EMAIL PROTECTED]> wrote:

Hi,

> There is an open BR against debian-cd to support EFI for i386/amd64 CD 
> images (#455914). Help to implement that is very much needed.

There's some work to be done on d-i beforehand ;)

> What other types of images are you thinking of? Could EFI support be added 
> to existing images or do we really need additional images?

I think we need dedicated images, as far as the CD/DVDs go. I don't
think we can share a CD, though I have to check how multiboot CDs
work and how EFI behaves on Macs. To be honest, at this stage, it's
still a detail :)

For PXE booting, a dedicated image will be required, though it's no
problem compared to a dedicated CD image.

The good news is, in all cases, the code from ia64.cfg can probably be
shared among all three architectures.

If I'm not mistaken, there's no g-i on ia64, so I'll just have to add
it for i386 and amd64 as g-i should work fine via EFI too.

> I don't see any objection to providing images that support EFI, but I doubt 
> anyone on the D-I team will do the actual implementation.
> As always: patches are welcome and we can offer help with finding the right 
> places to make needed changes.

I'm ready to make whatever changes are required, as long as I can get
some assistance on some very specific points.

I've started identifying the precise changes to be done. I may need a
little bit of help with the build system to build the images,
otherwise, with the exception of grub-installer and lilo-installer, I
think I can handle it.

I'd like to have grub-installer and lilo-installer default to
installing the bootloader on the debian partition on Macs, and that
requires some changes in the logic and templates. I'll try to figure
it out, but hairy debconf stuff scares the hell out of me :)

JB.

-- 
 Julien BLACHE <[EMAIL PROTECTED]>  |  Debian, because code matters more 
 Debian & GNU/Linux Developer|   
 Public key available on  - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 


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

Re: wpasupplicant udeb

[Kel Modderman]

On Monday 26 May 2008 00:32:39 Glenn Saberton wrote:
> Jérémy Bobbio wrote:
> > On Fri, May 23, 2008 at 04:09:48PM +0800, Glenn wrote:
> >> It will still build the deb and clients at the moment, which as stated
> >> earlier, some sort of seperate config needs to be made for the udeb.
> >
> > If you can provide a patch doing so for review, it would be great.
> >
> > You might want to have a look at busybox which also use a "config" file
> > for its build system and have several different configuration for its
> > binary packages.
> >
> > Cheers,
> After talking with one of the wpasupplicant maintainers, he has kindly
> agreed to help get an acceptable patch for a wpasupplicant udeb.
> CC'ing him in on this thread. Hopefully we should have a patch
> together in the next few days.

Attached is an initial patch against current state of wpasupplicant package
in version control. Glenn and I haven't nailed down the exact build
configuration of wpa_supplicant that will be used, but we'd really like some
feedback about the packaging changes at this time.

Also, do you think compiling in support for debug messages about association
is something that would be useful to have in the debian-installer environment
for occasions when manual troubleshooting is required? A fair amount of binary
size can be shaved off without it, but unsure if that is wise.

Thanks, Kel.
---
--- a/debian/control
+++ b/debian/control
@@ -38,3 +38,16 @@
  to connect to. It also provides a method for browsing 802.11 SSID scan
  results, an event history log of messages generated by wpa_supplicant,
  and a method to add or edit wpa_supplicant networks.
+
+Package: wpasupplicant-udeb
+Section: debian-installer
+Architecture: any
+XC-Package-Type: udeb
+Depends: ${shlibs:Depends}, dhcp-client-udeb | dhcp3-client-udeb | pump-udeb, 
ethernet-card-detection
+Description: Client support for WPA and WPA2 (IEEE 802.11i)
+ WPA and WPA2 are methods for securing wireless networks, the former
+ using IEEE 802.1X, and the latter using IEEE 802.11i. This software
+ provides key negotiation with the WPA Authenticator, and controls
+ association with IEEE 802.11i networks.
+ .
+ This is a udeb of wpasupplicant for use by the Debian installer.
--- /dev/null
+++ b/debian/config/udeb
@@ -0,0 +1,12 @@
+# Debian Installer's wpa_supplicant build time configuration
+CONFIG_DRIVER_WEXT=y
+CONFIG_BACKEND=file
+#CONFIG_NO_STDOUT_DEBUG=y
+CONFIG_DEBUG_FILE=y
+CONFIG_NO_AES_EXTRAS=y
+CONFIG_NO_CONFIG_WRITE=y
+CONFIG_NO_CONFIG_BLOBS=y
+CONFIG_MAIN=main
+CONFIG_OS=unix
+CONFIG_ELOOP=eloop
+CONFIG_L2_PACKET=linux
--- a/debian/rules
+++ b/debian/rules
@@ -9,6 +9,7 @@
 WPAGUI=wpa_gui-qt4
 
 CFLAGS = -Wall -g
+UDEB_CFLAGS = -Wall -g -Os
 LDFLAGS = -Wl,--as-needed
 
 ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS)))
@@ -62,6 +63,13 @@
dh_testroot
dh_clean -k 
dh_installdirs
+   dh_install
+
+   # udeb for debian installer
+   $(MAKE) -C wpa_supplicant clean; $(RM) wpa_supplicant/.config
+   cp -v debian/config/udeb wpa_supplicant/.config
+   CFLAGS="$(UDEB_CFLAGS)" $(MAKE) -C wpa_supplicant wpa_supplicant
+   dh_install -pwpasupplicant-udeb wpa_supplicant/wpa_supplicant sbin/

# ifupdown
install --mode=755 -D debian/ifupdown/ifupdown.sh \
@@ -94,7 +102,6 @@
dh_installchangelogs wpa_supplicant/ChangeLog
dh_installdocs
dh_installexamples
-   dh_install
dh_installlogrotate --package=wpasupplicant --name=wpa_action
dh_installlogrotate --package=wpasupplicant --name=wpa_supplicant
dh_installinit --package=wpasupplicant --name=wpa-ifupdown --no-start 
-- start 15 0 6 .
---


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

Re: unblock request: ttf-cjk-compact 1.13

[Frans Pop]

On Sunday 25 May 2008, Kenshi Muto wrote:
> Please unblock ttf-cjk-compact/1.13.
> This source provides only ttf-cjk-compact-udeb package.
> This version fixes FTBFS and syncs glyphs with current installer
> messages. I believe there aren't any regressions.

This will have to wait until after the release of D-I Beta2.

Cheers,
FJP


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

Bug#482854: debian installation report

[Frans Pop]

On Sunday 25 May 2008, Jocelyn Heuzé wrote:
> Comments/Problems:
> "No kernel modules were found. This probably is due to a mismatch
> between ther kernel used by this
> version of the installer and the kernel version available in the archive.
> (...)"

This is a known issue that is the result of the preparations for the release 
of Beta2. For now, you should wither use Beta1 or daily built images.

The weekly builds should be fine again after debian-installer (20080522) 
migrates to testing.

Cheers,
FJP



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

unblock request: ttf-cjk-compact 1.13

[Kenshi Muto]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

Please unblock ttf-cjk-compact/1.13.
This source provides only ttf-cjk-compact-udeb package.
This version fixes FTBFS and syncs glyphs with current installer messages.
I believe there aren't any regressions.

Changelog:

ttf-cjk-compact (1.13) unstable; urgency=medium

  * Fix FTBFS. ttf-arphic-uming changed its font from uming.ttf to
uming.ttc (closes: #482255)
  * Take po files of d-i from every sublevel directores.
  * Update at Sun May 25 13:50:58 UTC 2008

 -- Kenshi Muto <[EMAIL PROTECTED]>  Sun, 25 May 2008 22:50:58 +0900

Thanks,
- -- 
Kenshi Muto
[EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8+ 

iEYEARECAAYFAkg5c84ACgkQQKW+7XLQPLGdYACg2ueVC6qz0dhgUmE9A/LwaOmf
2FEAnRbyJIQyVxGVJd0jhY3f+fiP/JiW
=ynqj
-END PGP SIGNATURE-


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

Bug#482854: debian installation report

[Jocelyn Heuzé]

Package: installation-reports

Boot method: CD
Image version: 
http://cdimage.debian.org/cdimage/weekly-builds/i386/iso-cd/debian-testing-i386-kde-CD-1.iso
of 2008.05.22
Date: 25 May 2008

Machine: Virtualbox

Base System Installation Checklist:

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

Comments/Problems:

Got this message :

"No kernel modules were found. This probably is due to a mismatch
between ther kernel used by this
version of the installer and the kernel version available in the archive. (...)"

It's not the first time I have this issue, I remember of many weekly
builds which had the same
problem in 2007.



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

Re: d-i status wrt i386 & amd64 EFI machines

[Frans Pop]

Hi Julien,

(I have not read the gory details :-)

On Sunday 25 May 2008, Julien BLACHE wrote:
> Now that we have a working rEFIt, I'd like to have some support for
> that in d-i. Looking into this issue, I came to the conclusion that
> what is really needed is a d-i install medium for i386 & amd64
> machines.
>
> What is the status on that? Are there any plans or any work in
> progress towards providing an EFI bootable medium, similar to the ia64
> install medium?

There is an open BR against debian-cd to support EFI for i386/amd64 CD 
images (#455914). Help to implement that is very much needed.

What other types of images are you thinking of? Could EFI support be added 
to existing images or do we really need additional images?

I don't see any objection to providing images that support EFI, but I doubt 
anyone on the D-I team will do the actual implementation.
As always: patches are welcome and we can offer help with finding the right 
places to make needed changes.

Cheers,
FJP


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

Re: wpasupplicant udeb

[Glenn Saberton]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Jérémy Bobbio wrote:
> On Fri, May 23, 2008 at 04:09:48PM +0800, Glenn wrote:
>> It will still build the deb and clients at the moment, which as stated
>> earlier, some sort of seperate config needs to be made for the udeb.
>
> If you can provide a patch doing so for review, it would be great.
>
> You might want to have a look at busybox which also use a "config" file
> for its build system and have several different configuration for its
> binary packages.
>
> Cheers,
After talking with one of the wpasupplicant maintainers, he has kindly
agreed to help get an acceptable patch for a wpasupplicant udeb.
CC'ing him in on this thread. Hopefully we should have a patch
together in the next few days.

Cheers

Glenn
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFIOXiHV8GyuTwyskMRAkb2AJ9gqJWThe5sSnDipCPCoYrRhQe+1QCfVIJQ
EDil13798f36mwRUrcc57XI=
=tK38
-END PGP SIGNATURE-


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

Bug#482255: marked as done (ttf-cjk-compact: FTBFS: Open: Failed to open: /usr/share/fonts/truetype/arphic/uming.ttf)

[Debian Bug Tracking System]

Your message dated Sun, 25 May 2008 14:17:08 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#482255: fixed in ttf-cjk-compact 1.13
has caused the Debian Bug report #482255,
regarding ttf-cjk-compact: FTBFS: Open: Failed to open: 
/usr/share/fonts/truetype/arphic/uming.ttf
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
482255: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=482255
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: ttf-cjk-compact
Version: 1.12
Severity: serious
User: [EMAIL PROTECTED]
Usertags: qa-ftbfs-20080520 qa-ftbfs
Justification: FTBFS on i386

Hi,

During a rebuild of all packages in sid, your package failed to build on
i386.

This rebuild was done with gcc 4.3 instead of gcc 4.2, because gcc 4.3
is now the default on most architectures (even if it's not the case on
i386 yet).  Consequently, many failures are caused by the switch to gcc
4.3.
If you determine that this failure is caused by gcc 4.3, feel free to
downgrade this bug to 'important' if your package is only built on i386,
and this bug is specific to gcc 4.3 (i.e the package builds fine with
gcc 4.2).

Relevant part:
>  /usr/bin/fakeroot debian/rules clean
> dh_testdir
> dh_testroot
> rm -f build-stamp configure-stamp
> # Add here commands to clean up after the build process.
> rm -f tmp/* fonts/*
> dh_clean 
>  dpkg-source -b ttf-cjk-compact-1.12
> dpkg-source: info: using source format `1.0'
> dpkg-source: info: building ttf-cjk-compact in ttf-cjk-compact_1.12.tar.gz
> dpkg-source: info: building ttf-cjk-compact in ttf-cjk-compact_1.12.dsc
>  debian/rules build
> dh_testdir
> # Add here commands to configure the package.
> touch configure-stamp
> dh_testdir
> # Make fonts
> ./makettf zh /usr/share/fonts/truetype/arphic/uming.ttf
> embedded bitmap: disable
> Copyright (c) 2000-2008 by George Williams.
>  Executable based on sources from 16:34 GMT 30-Mar-2008.
>  Library based on sources from 15:57 GMT 30-Mar-2008.
> The requested file, uming.ttf, does not exist
> Open: Failed to open: /usr/share/fonts/truetype/arphic/uming.ttf
> Called from...
>  ./stripttf.ff: line 13
> make: *** [build-stamp] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2008/05/20

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot containing a sid i386
environment.  Internet was not accessible from the build systems.

-- 
| Lucas Nussbaum
| [EMAIL PROTECTED]   http://www.lucas-nussbaum.net/ |
| jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F |


--- End Message ---
--- Begin Message ---
Source: ttf-cjk-compact
Source-Version: 1.13

We believe that the bug you reported is fixed in the latest version of
ttf-cjk-compact, which is due to be installed in the Debian FTP archive:

ttf-cjk-compact-udeb_1.13_all.udeb
  to pool/main/t/ttf-cjk-compact/ttf-cjk-compact-udeb_1.13_all.udeb
ttf-cjk-compact_1.13.dsc
  to pool/main/t/ttf-cjk-compact/ttf-cjk-compact_1.13.dsc
ttf-cjk-compact_1.13.tar.gz
  to pool/main/t/ttf-cjk-compact/ttf-cjk-compact_1.13.tar.gz



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Kenshi Muto <[EMAIL PROTECTED]> (supplier of updated ttf-cjk-compact package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Sun, 25 May 2008 22:50:58 +0900
Source: ttf-cjk-compact
Binary: ttf-cjk-compact-udeb
Architecture: source all
Version: 1.13
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Kenshi Muto <[EMAIL PROTECTED]>
Description: 
 ttf-cjk-compact-udeb - Shrinked CJK TrueType fonts for GUI d-i. (udeb)
Closes: 482255
Changes: 
 ttf-cjk-compact (1.13) unstable; urgency=medium
 .
   * Fix FTBFS. ttf-arphic-uming changed its font from uming.ttf to
 uming.ttc (closes: #482255)
   * Take po files of d-i from every sublevel directores.
   * Update at Sun May 25 13:50:58 UTC 2008
Checksums-Sha1: 
 7a2dfda9f55d7a1845833eab0c18d71336bd6f8e 956 ttf-cjk-co

ttf-cjk-compact_1.13_amd64.changes ACCEPTED

[Debian Installer]

Accepted:
ttf-cjk-compact-udeb_1.13_all.udeb
  to pool/main/t/ttf-cjk-compact/ttf-cjk-compact-udeb_1.13_all.udeb
ttf-cjk-compact_1.13.dsc
  to pool/main/t/ttf-cjk-compact/ttf-cjk-compact_1.13.dsc
ttf-cjk-compact_1.13.tar.gz
  to pool/main/t/ttf-cjk-compact/ttf-cjk-compact_1.13.tar.gz


Override entries for your package:
ttf-cjk-compact-udeb_1.13_all.udeb - optional debian-installer
ttf-cjk-compact_1.13.dsc - source x11

Announcing to [EMAIL PROTECTED]
Closing bugs: 482255 


Thank you for your contribution to Debian.


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

Processing of ttf-cjk-compact_1.13_amd64.changes

[Archive Administrator]

ttf-cjk-compact_1.13_amd64.changes uploaded successfully to localhost
along with the files:
  ttf-cjk-compact_1.13.dsc
  ttf-cjk-compact_1.13.tar.gz
  ttf-cjk-compact-udeb_1.13_all.udeb

Greetings,

Your Debian queue daemon


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

Re: r53469 - in trunk/packages/partman/partman-base: debian lib

[Frans Pop]

On Sunday 25 May 2008, Jérémy Bobbio wrote:
> Author: lunar
> Date: Sat May 24 22:41:16 2008
> New Revision: 53469
>
> Log:
> Fix partition numbering when confirming changes
>
> In confirm_changes(), the control flow for displaying the list of
> partitions was changed when support for multipath devices was added.
> Before that $partdesc was redefined for every partitions, either for
> device mapper devices or normal ones.
>
> The multipath changes introduced a conditionnal branch testing for the
> emptyness of $partdesc.  As it was previously set for the first
> partition, the second time, the template variable was not previously
> substituted.
>
> We now explicitely reset $partdesc for each partition in order to get the
> proper behaviour.
>
>
> Modified:
>trunk/packages/partman/partman-base/debian/changelog
>trunk/packages/partman/partman-base/lib/commit.sh

IMO it would be good to include this in Beta2.


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

Re: d-i status wrt i386 & amd64 EFI machines

[Julien BLACHE]

Julien BLACHE <[EMAIL PROTECTED]> wrote:

For the sake of completeness, as I was concentrating on EFI stuff
while writing this mail:

> Which brings us to the core of the issue. Installing rEFIt means:

   - installing grub/lilo on the *partition* (not MBR)
   - running gptsync

>  - copying rEFIt to the EFI system partition (first partition on the
>disk, FAT32, ca. 200 MB on Apple machines)
>  - setting the EFI variables so that the EFI system will load rEFIt as
>the primary bootloader

JB.

-- 
 Julien BLACHE <[EMAIL PROTECTED]>  |  Debian, because code matters more 
 Debian & GNU/Linux Developer|   
 Public key available on  - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 


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

Bug#481687: Install report

[Avery Fay]

--- On Sat, 5/24/08, Jérémy Bobbio <[EMAIL PROTECTED]> wrote:
> 
> Imagine that you have a PC Card NIC. The drivers for the PC
> Card
> controller are in a udeb on an IDE CD-ROM drive.  You would
> not enable
> the PC Card service during the first question, but you
> would the second
> time.

Ok, that makes a little bit more sense. Would it be possible to disable the 
follow-up question about pcmcia options if you select no to starting pccard 
services? Part of my original problem was that not only do you have to answer 
no 3 times, but you also have to answer this other question about pcmcia 
options 3 times.

> > 4.) The gui installer crashed when I tried to manually
> partition.
> > Given some of the recent reports on debian-boot, I
> decided not to
> > investigate this further, but if there are no known
> crashes (was
> > gdk-something) I can try to get it to happen again.
> 
> I had no report of such issue.  You would be welcome if you
> could
> provide us a procedure on how to reproduce the crashes you
> have
> experienced.

Unfortunately, this install is completely done. I will be getting a different 
hard disk within a few months. At that point, I can retest the graphical 
install.

Thanks for looking into these issues.

Avery






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

Bug#346589: partman-auto: creates too large swap partitions

[Avery Fay]

I know this is an old bug report, but I think it has even more relevance 
today. My desktop machine has 4GB of memory and (IIRC) partman-auto 
tried to create a swap partition that was 10-12GB in size. That's 
wasting a ton of disk space. My real memory use (ignoring buffers/cache) 
rarely even hits 1GB. I simply have so much memory because it's so cheap.


Automatic partitioning would have worked fine for my machine except I'm 
not willing to sacrifice so much disk space to swap, so I ended up using 
manual partitioning.




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

Bug#482828: partman-lvm: should allow partitioning by logical extents

[Avery Fay]

Package: partman-lvm
Severity: normal

I think at least in the expert install, you should be able to specify 
logical partition size using extents. This would be less of an issue if 
#411943 were solved, but it would still be nice to have.

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

Kernel: Linux 2.6.24-1-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/bash



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

Bug#411943: partman-lvm: inconsistent usage of unit symbols for decimal and binary multiples

[Avery Fay]

Also, this seems to be a somewhat popular issue. At least, #435767 and 
#437016 appear to be duplicates.




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

Bug#411943: partman-lvm: inconsistent usage of unit symbols for, decimal and binary multiples

[Avery Fay]

I think this bug is quite high priority and should definitely be fixed 
for Lenny. I recently installed from a debian installer snapshot and 
manually partitioning LVM was nearly impossible. It may not make much of 
a difference when you're partitioning 20 GB or so, but the drive I was 
partitioning was 300 GB. You're forced to play "guess and check" and 
given the inefficiencies of a text installer it's painful.


I ended up partitioning in a spare rescue cd I had and then restarted 
the whole installation process, completely bypassing the whole issue.




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

d-i status wrt i386 & amd64 EFI machines

[Julien BLACHE]

[Please Cc me on replies, I'm not subscribed to debian-boot]

Hi,

I've taken over the maintenance of rEFIt last week and I've been
working on updating rEFIt in Debian since then (I've been working on
the rEFIt issue on and off for more than a year). This is now a done
deal, only waiting for a gnu-efi upload.

Now that we have a working rEFIt, I'd like to have some support for
that in d-i. Looking into this issue, I came to the conclusion that
what is really needed is a d-i install medium for i386 & amd64
machines.

What is the status on that? Are there any plans or any work in
progress towards providing an EFI bootable medium, similar to the ia64
install medium?


(you can skip the remainder of this mail if you're not interested in
the gory details)

Rationale for that:
 - i386/amd64 EFI machines are becoming more and more common among
   high-end servers
 - Intel Macs are also becoming more and more common, the market share
   for Apple machines in the high end market is booming (especially
   for laptops)
 - as the pommed author, I'm getting more and more mails from *new*
   users; that shows that Linux is progressing on those machines too
 - current d-i support for Intel Macs is suboptimal at best,
   installing an i386 system is mostly OK, installing and amd64 system
   is hardly possible TTBOMK


I'll go into the details pertaining to Intel Macs now and why an EFI
boot medium is needed. When reading what follows, keep in mind that
Intel Macs are a special case among i386/amd64 EFI machines. That
means most of the workload is directed at the generic case and the
support for Intel Macs is really icing on the cake.

The EFI system on Apple machines can boot an OS either via an EFI
bootloader or through a legacy bootloader by loading a legacy BIOS
emulation layer before executing the legacy bootloader.

The Linux kernel has support for EFI on both i386 and amd64 (starting
with 2.6.25 for amd64); this means the kernel can be booted via an EFI
bootloader such as elilo and interact with the EFI system. Notably,
this means the kernel can manipulate EFI variables (via the efivars
module), which is required to set the boot order.

That last feature can only be used when the kernel has been booted via
EFI, it's not available when the kernel is booted through legacy mode.

Also, for everyday use, Intel Macs are best booted through legacy
mode. Why? Because otherwise, there is no video BIOS loaded, which
means: no accelerated 2D or 3D video.


Which brings us to the core of the issue. Installing rEFIt means:
 - copying rEFIt to the EFI system partition (first partition on the
   disk, FAT32, ca. 200 MB on Apple machines)
 - setting the EFI variables so that the EFI system will load rEFIt as
   the primary bootloader

(for other EFI machines, replace rEFIt with elilo and the above still
holds)

This last step can be accomplished on Linux with efibootmgr and the
efivars kernel module. Without this last step, the machine will
continue booting into OS X and the user will have to use the bless
utility under OS X to set the EFI variables.


As I wrote above, the efivars module only works when the kernel has
been booted through EFI. Which means that we need to boot d-i from EFI
and not through legacy mode in order to support a painless installation
on these machines.


Note that I expect most of the ia64 stuff can be reused mostly
unchanged to produce those images.

Providing a refit-installer similar to elilo-installer looks like a
no-brainer, overall most of the work seems to be in building new
images and testing them.

JB.

-- 
 Julien BLACHE <[EMAIL PROTECTED]>  |  Debian, because code matters more 
 Debian & GNU/Linux Developer|   
 Public key available on  - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 


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