|
Bugzilla – Full Text Bug Listing |
| Summary: | Installation of openSUSE-11.1-Beta3 fails saying | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.1 | Reporter: | LTC BugProxy <bugproxy> |
| Component: | Installation | Assignee: | E-mail List <yast2-maintainers> |
| Status: | RESOLVED INVALID | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Blocker | ||
| Priority: | P5 - None | CC: | dmacvicar |
| Version: | Beta 3 | ||
| Target Milestone: | --- | ||
| Hardware: | PowerPC-64 | ||
| OS: | All | ||
| URL: | http:// | ||
| See Also: | https://bugzilla.linux.ibm.com/show_bug.cgi?id=49448 | ||
| Whiteboard: | |||
| Found By: | Third Party Developer/Partner | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
/var/log/YaST details
Screenshot of error message |
||
|
Description
LTC BugProxy
2008-10-31 11:11:40 UTC
Created attachment 249094 [details]
/var/log/YaST details
Created attachment 249095 [details]
Screenshot of error message
------- Comment From 2008-10-31 07:27 EDT------- <Pavan Naregundi> : "I have tried it only on ppc-64. We have tested Alpha-1. After that all the releases(Alpha-2, Beta-1, Beta2) are installation blockers on ppc architecture." Can you verify that the url you are using actually is valid? verify content against content.asc. It is not an error, it is just telling you your media is modified. ------- Comment From pavan.naregundi@in.ibm.com 2008-11-03 06:19 EDT------- (In reply to comment #10) > ------- Comment From dmacvicar@novell.com 2008-10-31 09:03:26 MDT------- > Can you verify that the url you are using actually is valid? url is correct. > > verify content against content.asc. Can you please mention how to do this? > > It is not an error, it is just telling you your media is modified. > Thanks Pavan ------- Comment From pavan.naregundi@in.ibm.com 2008-11-04 05:12 EDT------- I have booted with a wrong inst64 image. This was the confusion because both inst64 have same size. Please close this bug as a non valid bug. closing as per request in comment #6 |