Using lighttpd as a source for network installation of ubuntu fails

Bug #611256 reported by Wouter van Bommel
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lighttpd (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: lighttpd

Using lighttpd as the server for deb packages for a network install does not work. From some of the packages retrieved via the network installer the crc does not macht, which causes the installer to refuse to install the package with a corruption message.
The package that is corrupted is random.

Using apache on the exact same source does solve the problem (only change in configuration is the installation of apache & configuration).

The bug is available on both ubuntu releases 8.04 lts & 10.04 lts

Revision history for this message
Daniel Hahler (blueyed) wrote : Re: [Bug 611256] [NEW] Using lighttpd as a source for network installation of ubuntu fails

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> Using lighttpd as the server for deb packages for a network install does not work.

I assume you mean to have setup lighttpd to serve .deb packages?

Please provide the used configuration in this case, or a link to some
tutorial convering this.

 status incomplete

- --
http://daniel.hahler.de/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFMUyQffAK/hT/mPgARAgooAJ0d3eN4lTphVcESDYzo6aDaVFjsGQCfU4Az
hZ6lfBMF/5Fxf2STvslVzac=
=FQz9
-----END PGP SIGNATURE-----

Changed in lighttpd (Ubuntu):
status: New → Incomplete
Revision history for this message
Wouter van Bommel (woutervb) wrote :
Download full text (7.5 KiB)

Running debmirror with the following script:

---------------------------------------------------------------------------

#### Start script to automate building of Ubuntu mirror #####
## THE NEXT LINE IS NEEDED THE REST OF THE LINES STARTING WITH A # CAN BE DELETE D

#!/bin/bash

## Setting variables with explanations.

#
# Don't touch the user's keyring, have our own instead
#
export GNUPGHOME=/home/mirrorkeyring

# Arch= -a # Architecture. For Ubuntu can be i386, powerpc or amd64 .
# sparc, only starts in dapper, it is only the later models of sparc.
#
arch=amd64

# Minimum Ubuntu system requires main, restricted
# Section= -s # Section (One of the following - main/restricted/univer se/multiverse).
# You can add extra file with $Section/debian-installer. ex: main/debian-install er,universe/debian-installer,multiverse/debian-installer,restricted/debian-insta ller
#
section=main,restricted,universe,multiverse,main/debian-installer,universe/debia n-installer,multiverse/debian-installer,restricted/debian-installer

# Release= -d # Release of the system (Dapper, Edgy, Feisty, Gutsy, Ha rdy, Intrepid), and the -updates and -security ( -backports can be added if desi red)
#
release=hardy,hardy-updates,hardy-security,hardy-backports,lucid,lucid-updates,l ucid-backports,lucid-security

# Server= -h # Server name, minus the protocol and the path at the en d
# CHANGE "*" to equal the mirror you want to create your mirror from. au. in Aus tralia ca. in Canada.
# This can be found in your own /etc/apt/sources.list file, assuming you have Ub untu installed.
#
server=nl.archive.ubuntu.com

# Dir= -r # ...

Read more...

Revision history for this message
Geoffrey Thomas (geofft) wrote :

Hi Wouter,

Is the bug present in the version of lighttpd included with Ubuntu 10.04, or do you merely mean that installing Ubuntu 10.04 fails when using an older version of lighttpd as the mirror?

There is a known bug in lighttpd regarding pipelining that cases corruption when installing from apt, but this should have been fixed in 1.4.24, and Lucid has 1.4.26. We are running into this at our site and will be testing if upgrading the mirror server from Jaunty to Lucid fixes this.
http://redmine.lighttpd.net/issues/657

Changed in lighttpd (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
gstrauss (gstrauss) wrote :
Changed in lighttpd (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.