| Summary: | all gentoo 2007.0 iso images are bad | ||
|---|---|---|---|
| Product: | Gentoo Release Media | Reporter: | scott <madsen.g1153> |
| Component: | LiveCD/DVD/USB | Assignee: | Gentoo Release Team <releng> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | critical | CC: | sgtphou |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | 178512 | ||
| Bug Blocks: | |||
|
Description
scott
2007-05-11 18:06:10 UTC
All of them? Really? Does that include all of the images for alpha, amd64, hppa, ia64, mips, ppc, ppc, sparc, and x86? Perhaps you could tell us exactly which ones you've tried. Also, did you try verifying your downloaded images with the provided SHA1 and MD5 checksums? I'm also curious what your Microsoft router has to do with booting a CD :P (In reply to comment #1) > All of them? Really? Does that include all of the images for alpha, amd64, > hppa, ia64, mips, ppc, ppc, sparc, and x86? Perhaps you could tell us exactly > which ones you've tried. > Also, did you try verifying your downloaded images with the provided SHA1 and > MD5 checksums? > I'm also curious what your Microsoft router has to do with booting a CD :P (In reply to comment #1) > All of them? Really? Does that include all of the images for alpha, amd64, > hppa, ia64, mips, ppc, ppc, sparc, and x86? Perhaps you could tell us exactly > which ones you've tried. > Also, did you try verifying your downloaded images with the provided SHA1 and > MD5 checksums? > I'm also curious what your Microsoft router has to do with booting a CD :P amd 64&x86 the router is just part of the system Ugh, you didn't really give me any information that I asked for. I want the full filenames of the ISOs that you tried. I also want you to verify the MD5 checksums to make sure your download is good. Try verifying against the CD you burn to make sure it's not just your CD burner that sucks. It would also be nice if you could put together a coherent sentence, perhaps even using some punctuation. It hurts my brain to read what you write. Get back to us with something *useful*. If all ISO images were bad, we'd be flooded by zillions of bugs after release, oh what a surprise it hasn't happened. Jakub, please try to not be so condescending to our users. It makes us all look bad and I really don't appreciate it. Scott: Please provide the information asked for by Andrew. Thanks (In reply to comment #5) > Jakub, please try to not be so condescending to our users. It makes us all > look bad and I really don't appreciate it. ZOMG... Sorry to have closed this precious bug and good luck. *sigh* Developer Relations: This is getting old. I am sick of Jakub going around insulting users and developers alike, especially on release bugs, which very well may be a user's first interaction with the Gentoo developer community. (In reply to comment #7) > Developer Relations: This is getting old. I am sick of Jakub going around > insulting users and developers alike, especially on release bugs, which very > well may be a user's first interaction with the Gentoo developer community. Maybe you should read your gentoo-dev ML posts archive if you really can't live with my comment on this bug, before talking about something getting old. Anyway, totally off-topic here, move this to my devrel bug if you really feel like it. I wonder if there is a double cross reference here: First, there is not much information on this bug, but it looks a bit like Bug 178512 so I am adding a dependency; please feel free to remove it if that is wrong. That I am doing anything at all is because of the referral to devrel and to the proctors. Since I added ombudsman to Bug 178512, I am also making this bug a "virtual blocker" for that bug for the moment. (Bugzilla cannot itself handle mutual dependencies, although in the case of omnibus bugs like these two they can make sense logically.) At this moment, devrel is watching this bug because we have been asked to, but we are awaiting some comment from the proctors or from the ombudsmen. All should be aware that remarks like Comment 7 do not in themselves necessarily trigger devrel action. Since at the moment I am the only one from devrel to have commented on these bugs, for the moment please consider me to be the devrel contact for them. This is not necessarily permanent; for the moment I am just serving as an explicit point of contact if anyone feels the need for one. Reopen once you've provided the info requested in Comment #1, Comment #3, Comment #5 etc. |
