| 2006-04-13 21:53:02 |
Andrea Veri |
bug |
|
|
added bug |
| 2006-04-14 11:53:12 |
Andrea Veri |
title |
Ubunu Server flight6: system cant find cdrom modules |
Ubuntu Server flight6: system cant find cdrom modules |
|
| 2006-04-14 17:36:19 |
Daniel Robitaille |
None: statusexplanation |
|
|
|
| 2007-08-03 19:55:35 |
Schmirrwurst |
bug |
|
|
added attachment 'syslog' (syslog) |
| 2007-08-03 19:59:07 |
Schmirrwurst |
title |
Ubuntu Server flight6: system cant find cdrom modules |
[gutsy 7.10 tribe 3]: system cant find cdrom modules |
|
| 2008-11-07 22:53:05 |
Colin Watson |
debian-installer: status |
New |
Won't Fix |
|
| 2008-11-07 22:53:05 |
Colin Watson |
debian-installer: assignee |
|
kamion |
|
| 2008-11-07 22:53:05 |
Colin Watson |
debian-installer: statusexplanation |
|
This is not a problem if you're using the final release. I'm not intending to "fix" this for the development release; it's more important to make it move smoothly than to make it stable at every step, and the two goals are in conflict in this case.
Generally speaking, during a development release the current symlink in the archive will contain an installer image that matches the current *archive* (not necessarily the CD). This may be untrue for short periods of time but generally only measured in hours. Anyone with more stringent stability requirements than that should use a stable release. |
|
