Description of problem: I do a minimal installation The installer installs packages that, in my opinion should not be part of a minimal installation, without X server, just with urpmi. The problem is the same with an installation from a DVD or a net-install. Steps to Reproduce: 1. During installation, I choose a custom installation 2. I deselect all package groups 3. I choose: no X server, without basic documentation, without suggests packages, but with urpmi This report attempts to clarify the contents of the report 609. The various interventions have shown that the profusion of unnecessary packages appears to be from two different causes: - dependencies of basesyetem. For this, Thierry Vignaud has taken the necessary - other packages selected by the installer. Some examples are given by Buchan Milne in the report 609. I tried to analyze the influence of the files and compssUsers.pl rpmsrate examining ddebug.log Is my understanding that compssUsers.pl setting flags depending on the material and package groups selected for installation. Then rpmsrate defines the packages corresponding to these flags. But when I unselect all package groups, compssUsers.p no longer defines any flag : After deselecting all groups, ddebug.log writs * compssUsersChoice selected: But a few lines later, he wrote: * setSelectedFromCompssList: reached size 621MB, up to indice 5 (less than 8.6Gio) for flags 3D BURNER CHARSET"iso-8859-15" DVD LOCALES"fr" LOCALES"fr_FR" META_CLASS"download" SOUND TRUE USB UTF8 Where do these flags? Are they all relevant? I think that this bug could be treated even tempt the 3060
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=609
Please only open bugs if you've numbers to display an actual issue, not a potential issue
CC: (none) => thierry.vignaud
(In reply to comment #1) > Please only open bugs if you've numbers to display an actual issue, not a > potential issue My English is very limited, can you clarify, please, what you mean by "if you've numbers to display an actual issue"
Let's clarify: there's no data here, no numbers. You're not reporting an actual bug for now. You're just speaking about some log lines. What is the size of your install at end of installation? What is the packages list?
Created attachment 986 [details] Ordered list of packages Yes, of course, I try to understand what is happening. That's why I put extracts ddebug.log A minimal installation without X, no doc, no suggestion, but urpmi, installs 844 MB and 479 packages. The list is attached.
Created attachment 987 [details] auto_inst.cfg_urpmi.pl If it can bring a different light, here is the file auto_inst.cfg.pl
I can remove all the packages relative a QT or GTK or Gnome urpme GConf2 => 14 packages urpme qt4-common => 5 packages urpme libgtk+2.0_0 => 7 packages urpme polkit-gnome => 1 package urpme canberra-gtk => 2 packages urpme gtk+3.0 => 11 packages urpme libgnome-keyring-i18n There are probably others. I do not think so removes a vital or even necessary (but I could be wrong)
Is pulseaudio necessary ?
Attachment 986 mime type: application/octet-stream => text/plain
Source RPM: (none) => meta-task
cc'ing Païou, in case a minimal install without X interests him, too. Also cc'ing AL13N, who might have an interest (he did a text install of Mageia, and I can't think of another reason for doing that, then to have an install without X) @ AL13N @ Païou Did you ever try a minimal install without X and if so, can you tell what you did to get it and which packages you had installed?
CC: (none) => alien, marja11, paiiou
OP: it wasn't clear what you really wanted in this bug line; you say that X and Y. but not IF there is anything wrong. it's like you're saying "There is Milk in the fridge", but without saying you are lactose intolerant. you say specific stuff, but not IF there is a problem. so, i understand that you think there are too much packages selected when installing minimal? that is indeed something i am interested in. i'm unsure, but i think in the /root/drakx directory, there is a tar.gz file with all stuff inside and logs what gotten installed and maybe even why. i presume this is cauldron install and not mga1? most of the strict requirements are gone, but imho suggests is still pulling in some stuff. in a cauldron chroot installing without suggests in x86_64 basesystem-minimal urpmi locales-nl locales-en gives: 208MB of additional disk space will be used. 48MB of packages will be retrieved. Proceed with the installation of the 174 packages? (Y/n) so, can we get those relevant /root/drakx/* files? after selection, one of these files should contain the list of packages it's going to install (without dependencies) this will tell us if there is something wrong with dependencies or with the package selection (or even one of those temporary cauldron issues)
In fact, my ultimate goal is to find an installation operating properly with computers quite old. 3093 This report 3093 is a first step to get there. The second step is the report 3060. I started with Mageia1, and I continue with Cauldron. I think this report can be closed, as with Mageia1 the goal is reached. I think my approach was awkward and I apologize.
@ Georges No problem, I'll close it as invalid @ AL13N Thanks for your comment. I think you meant /root/drakx/report.bug.gz I hope one day we'll have a wiki page about how to install most minimal :) I'm curious to know what the system requirements for such an install would be . I suppose that isn't documented anywhere, because some time ago I tried to gather information about system requirements for Mga + KDE4, Mga + Gnome3, Mga + LXDE etc., but even that couldn't be found anywhere.
Status: NEW => RESOLVEDResolution: (none) => INVALID
i don't get it... @Georges: why didn't you make a tracker issue and others blocking the tracker issue? then assign the tracker issue to yourself; then make for each problem a bug report and block your tracker. at least we may have a clue to what your goal really is. also, i don't see any solution to this problem? or am i not seeing everything? @marja: i believe that absolute minimal requirements are very difficult to pinpoint, and not really necessary imho, i mean if people can go with lower requirements, that's all good; but even if it works under minimal requirements, but people find it too slow; it doens't help. + i would estimate that it depends on the hardware too; not to mention the purpose (gaming or browsing) i think the DE doesn't really matter that much, except that it might use more memory, also, if you have LXDE and you're using kontact + akonadi... it's still gonna take alot more than if you were to use mutt...
(In reply to comment #12) > @marja: i believe that absolute minimal requirements are very difficult to > pinpoint, and not really necessary imho, i mean if people can go with lower > requirements, that's all good; but even if it works under minimal requirements, > but people find it too slow; it doens't help. + i would estimate that it > depends on the hardware too; not to mention the purpose (gaming or browsing) > > i think the DE doesn't really matter that much, except that it might use more > memory, also, if you have LXDE and you're using kontact + akonadi... it's still > gonna take alot more than if you were to use mutt... That is true, but since the last Mdv live CD's (before Mageia 1 was born), I think it is very important. Those Mdv live CD's froze on two different systems with 1 GB RAM, and that really frustrated me. I think it would be nice to tell new users something about what is needed for a standard installation, so in case of X: with just picking the DE and not choosing extra packages, and maybe differentiate between: won't freeze, but slow, and: fine
(In reply to comment #12) > i don't get it... > > @Georges: > > why didn't you make a tracker issue and others blocking the tracker issue? then > assign the tracker issue to yourself; then make for each problem a bug report > and block your tracker. at least we may have a clue to what your goal really > is. also, i don't see any solution to this problem? or am i not seeing > everything? I'm sorry, but I did not understand what you mean by "issue tracker". My English is practically zero (google translates me, more or less well) and I have not studied in computer science
issue tracker is a bug here on bugzilla which only purpose is to have other bugs on the dependency list, so that when all the other bugs are fixed, the TRACKER bug is also fixed (automatically).