| Summary: | cosmetic changes in installer | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | ra oeai <oeai> |
| Component: | Installer | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | minor | ||
| Priority: | Normal | Keywords: | NEEDINFO |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
| Attachments: | debug.log >> somehow ddebug.log | ||
|
Description
ra oeai
2013-03-13 22:53:10 CET
such bugs report are a little useless, as it is hard to manage.
also some are already in specific bugs.
but for
>i've been disabling release32bit repos but after booting i had a lot of i586 packages in software center it is fixed in text mode
this is strange, can you attach the file /root/drakx/debug.bugKeywords:
(none) =>
NEEDINFO this is a grub installation scripts faults and really installer script. this actually must be changed, because fstab change is also here. why are you saying that ? please provide logs saying what? it's just a few scripts change so never think about it again Created attachment 3611 [details]
debug.log >> somehow ddebug.log
(In reply to ra oeai from comment #4) > saying what? it's just a few scripts change so never think about it again there seems to be a misunderstanding, what are you talking about? personally I was still about: "i've been disabling release32bit repos but after booting i had a lot of i586 packages" (In reply to ra oeai from comment #5) > Created attachment 3611 [details] > debug.log >> somehow ddebug.log your tar seem corrupted, attach the report.bug it will be better debug.log is too big about 1.6mb maybe it is not rechowned? you need to unbzip it first, if i just try to view in mc it ays error, if i get into the archive - i can see the log if i don't load i586 repo, i wouldn't find i586 packages, that was loaded while installing, but i've disabled it, also this can be a previous version of netboot, so maybe already fixed, don't know, it was a fixed issue with fstab already. no real info, closing Status:
NEW =>
RESOLVED |