Ubuntu

Gutsy DVD daily build ISO too large for a non Double Layer disc

Asked by Mike L16

I think it would be a good idea to make the daily DVD ISO builds for testing Gutsy smaller than 4489MB since this capacity is more likely to be compatible with older DVD readers and non dual-layer media & readers. The checksum verified DVD ISO images that I downloaded for testing on September 15th, 2007 was ~4891MB, which is too large to use typical DVD readers & media.

Perhaps someone is using overburning or some other less compatible ISO image creation method to create the daily DVD ISO images.

Does anyone know how we can make that happen fairly quickly? A work-around would be ok too, but then we should post a work-around link on the daily build download page.

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
DaveThacker
Solved:
Last query:
Last reply:
Revision history for this message
Best DaveThacker (dthacker9) said : 		#1

Mike,
To bring this to the attention of the developers, please file a bug at https://bugs.launchpad.net/ubuntu. Please give all the information you can. If this has answered your question, please mark this resolved.

Thanks!
Dave

Revision history for this message
Mike L16 (malent95-juno) said : 		#2

Thanks for the guidance, Dave.

I found an existing Bug #130777, first reported on 2007-08-07 which alerted the developers to the problem.

Once someone has time to address we can spend less time installing & downloading / upgrading and more time testing! -- Thanks again.

Revision history for this message
Mike L16 (malent95-juno) said : 		#3

The button for closing this question says "This solved my problem". My question is answered -- but the problem is unresolved -- I'll close it here since it's open on the bug report side now.

Revision history for this message
Mike L16 (malent95-juno) said : 		#4

Thanks DaveThacker, that solved my question.

Revision history for this message
Mike L16 (malent95-juno) said : 		#5

See existing Bug #130777 for status on this issue.