Yast Software Management Issues
Hi all, I've installed OpenSuse 10.1 on Dell Poweredge 650 with 1G RAM, 73G Ultra SCSI HD, when accesing Yast -> Software -> Software Management, the Process Take about 20 minutes at "Reading package information". Any ideas? Thanks
kengheng wrote:
Hi all, I've installed OpenSuse 10.1 on Dell Poweredge 650 with 1G RAM, 73G Ultra SCSI HD, when accesing Yast -> Software -> Software Management, the Process Take about 20 minutes at "Reading package information". Any ideas?
for me this was only the first time, after that the process is much faster than on 10.0. don't know if it's the normal way or if i'm lucky :-) jdd -- http://www.dodin.net http://dodin.org/galerie_photo_web/expo/index.html http://lucien.dodin.net http://fr.susewiki.org/index.php?title=Gérer_ses_photos
On Tue, May 23, 2006 at 03:35:38PM +0800, kengheng wrote: <snip> Do not take this as a flame. It is intend to get you the best support for now and in the future. openSUSE is the comunity and SUSE is the distribution. This means that this openSUSE mailinglist is about the community. The mailinglist for technical help is on *suse-linux-e*
From http://en.opensuse.org/Communicate#SUSE_Linux_Mailing_Lists : # opensuse for general discussion about the openSUSE (development) project. # For general questions related to released SUSE Linux versions # (eg. 9.3, 10.0) please use suse-linux-e
Please take a look at http://en.opensuse.org/Communicate to see wich list is exactly for what purpose. Again, this is not a flame. This is intended to bring you to the correct place so you will get better help _and_ to keep this list free from unwanted treads. Thanks and I hope you will soon find a solution. -- houghi http://houghi.org http://www.plainfaqs.org/linux/ http://www.netmeister.org/news/learn2quote.html
Today I went outside. My pupils have never been tinier...
houghi wrote:
On Tue, May 23, 2006 at 03:35:38PM +0800, kengheng wrote:
<snip> Do not take this as a flame. It is intend to get you the best support for now and in the future.
I have still a problem about the use if this list. What must we do when we suspect a bug? the suse-linux-e list don't seems to be the better place to speak of this. I see it most as a helper for day to day use problems. Factory is for the unstable one. and for stable? it is said this list is for the community, but the main community goal is bugfixing... jdd -- http://www.dodin.net http://dodin.org/galerie_photo_web/expo/index.html http://lucien.dodin.net http://fr.susewiki.org/index.php?title=Gérer_ses_photos
On Tue, May 23, 2006 at 10:16:45AM +0200, jdd wrote:
I have still a problem about the use if this list.
What must we do when we suspect a bug?
Bugzilla in first instance. If in doubt, file a bugreport. :-) factory or suse-linux-e. Depends on where you see it and what the impact it will have.
the suse-linux-e list don't seems to be the better place to speak of this. I see it most as a helper for day to day use problems.
Then suse-linux-e must be fixed if it does not solve or handle the technical problems as it should do. I have no exprience with suse-linux-e so I do not know where the error or solution is.
Factory is for the unstable one.
and for stable?
suse-linux-e However large bug discussions will have influence on future releases (e.g. the zen stuff) and therefore should go into factory. Solutions might then be backported to current releases, or they might not.
it is said this list is for the community, but the main community goal is bugfixing...
It is not _for_ the community, it is _about_ the community.¹ This list is about the group, the goals and such. I agree that there might be overlapping between suse-linux-e and factory. That should not be an excuse to post technical questions here. ¹Il n'est pas _pour_ la communauté, il est _au sujet_ de la communauté. Please don't see this as an insult. Your English is much better then my French. ;-) The above is brought to you by Babelfish.com. -- houghi http://houghi.org http://www.plainfaqs.org/linux/ http://www.netmeister.org/news/learn2quote.html
Today I went outside. My pupils have never been tinier...
houghi wrote:
It is not _for_ the community, it is _about_ the community.¹ This list is about the group, the goals and such.
I agree that there might be overlapping between suse-linux-e and factory. That should not be an excuse to post technical questions here.
¹Il n'est pas _pour_ la communauté, il est _au sujet_ de la communauté. Please don't see this as an insult. Your English is much better then my French. ;-) The above is brought to you by Babelfish.com.
don't bother, I understand the difference, even in english :-) you should experiment suse-linux-e. it's not always a good experience. most people ask before having ever read the wiki, not to say they read the archives :-). OT are so frequent... and the bugfix of stable release is still not clear for me. I undertood that security fixes will be done very fast, but what kind of bug will be fixed and what will not? the inst-source folder is frozen fromm the beginning, YOU update is for security... what about bugfixes? bugzilla is a good tool, but I can't send there anybody because I was years before being able to use it myself Could it be usefull to have a namespace/main page on the wiki for following the bugs? I mean that most wontfix bugs are minor or have a workaround. may be these should stay in the wiki in a visible place for new users. jdd -- http://www.dodin.net http://dodin.org/galerie_photo_web/expo/index.html http://lucien.dodin.net http://fr.susewiki.org/index.php?title=Gérer_ses_photos
On Tue, May 23, 2006 at 12:03:21PM +0200, jdd wrote:
you should experiment suse-linux-e. it's not always a good experience. most people ask before having ever read the wiki, not to say they read the archives :-). OT are so frequent...
The last time I looked there I saw so many topposting and HTML postings that I ran away. As long as the people agree that this is allowed (either by really allowing it, or by not doing anything about it) I won't go there.
and the bugfix of stable release is still not clear for me. I undertood that security fixes will be done very fast, but what kind of bug will be fixed and what will not?
Security fixes are done. Others are not done. There will be some exeptions, but it is a pretty good rule of thumb. This has been explained a few times already. Also the idea why has been explained.
the inst-source folder is frozen fromm the beginning, YOU update is for security... what about bugfixes?
Unless they are security fixes, they won;t be done. e.g. the slower transfer rate for USB in 10.0 has a solution, yet as it is not a security issue, it won't be implemented.
bugzilla is a good tool, but I can't send there anybody because I was years before being able to use it myself
Sure you can. An example: USB Speed: https://bugzilla.novell.com/show_bug.cgi?id=105871 comments 19, 41 and 50-53 People have been pointed there and have solved their issue. Indeed some are not able to use Bugzilla (or don't want to) they will have to ask solutions in suse-linux-e. They are asking for solutions. To me they are not reporting bugs and that was what you were talking about.
Could it be usefull to have a namespace/main page on the wiki for following the bugs?
I mean that most wontfix bugs are minor or have a workaround. may be these should stay in the wiki in a visible place for new users.
Aside from Most Anoying Bugs? No. There are just too many. -- houghi http://houghi.org http://www.plainfaqs.org/linux/ http://www.netmeister.org/news/learn2quote.html
Today I went outside. My pupils have never been tinier...
houghi wrote:
On Tue, May 23, 2006 at 12:03:21PM +0200, jdd wrote:
you should experiment suse-linux-e. it's not always a good experience.
The last time I looked there I saw so many topposting and HTML postings that I ran away. As long as the people agree that this is allowed (either by really allowing it, or by not doing anything about it) I won't go there.
I personnally can't recommand a place I don't wan to go. if suse-linux-e is bad, do _not_ say the others to go there... (do you say "go to hell"?)
Security fixes are done. Others are not done. There will be some exeptions, but it is a pretty good rule of thumb. This has been explained a few times already. Also the idea why has been explained.
so this mean reporting bugs for stable release is completely unusefull...
Aside from Most Anoying Bugs? No. There are just too many.
an so any people will have to ask for solutions again and again? This is not the way I work. There are several parts on the wiki: * stuff for development part * stuff for stable release. in the last part we should have a summary of all the solved bugg (solved _after_ the stable release) with the workaround and the wonfix. so at any questions relating to these in a list we could answer by a link. I now this needs work and can't come at once, but it must be a goal. jdd -- http://www.dodin.net http://dodin.org/galerie_photo_web/expo/index.html http://lucien.dodin.net http://fr.susewiki.org/index.php?title=Gérer_ses_photos
On Tue, May 23, 2006 at 02:25:53PM +0200, jdd wrote:
I personnally can't recommand a place I don't wan to go. if suse-linux-e is bad, do _not_ say the others to go there... (do you say "go to hell"?)
I often do. :-) Also I often point people to places I have never been and only heard things about. I have seen it and it is not for me. That does not mean it is not for others or that I should deny it to others. e.g. if somebody asks me what kind of beer to drink in my pub, I would sugest a Guinness, uet I never drink the stuff myself. :-) You are the first to tell me there are issues on suse-linux-e The only problems I saw were topposting and HTML postings. For the rest it looked pretty solid.
Security fixes are done. Others are not done. There will be some exeptions, but it is a pretty good rule of thumb. This has been explained a few times already. Also the idea why has been explained.
so this mean reporting bugs for stable release is completely unusefull...
That is not true and you know it. Bug reporting is not only for what you already have. It will have influence in future things as well and perhaps yopu point out a security bug.
Aside from Most Anoying Bugs? No. There are just too many.
an so any people will have to ask for solutions again and again?
If it is a 'most annoying bug' then it can go there. Posting all 'WONTFIX' as sugested is not a good idea.
This is not the way I work.
There are several parts on the wiki:
* stuff for development part * stuff for stable release.
Yes.
in the last part we should have a summary of all the solved bugg (solved _after_ the stable release) with the workaround and the wonfix.
No. There are too many WONTFIX.
so at any questions relating to these in a list we could answer by a link.
yes, to the specified bug in bugzilla. If there are too many questions about a specific page, I would put them on 'most annoying bugs' page. Clearly if there are too many, that should become a seperate page. ving all the WONTFIX on the wiki is doing double work, because they are already in bugzilla. So some, but please not all. -- houghi http://houghi.org http://www.plainfaqs.org/linux/ http://www.netmeister.org/news/learn2quote.html
Today I went outside. My pupils have never been tinier...
On Tue, 2006-05-23 at 12:45 +0200, houghi wrote:
On Tue, May 23, 2006 at 12:03:21PM +0200, jdd wrote:
you should experiment suse-linux-e. it's not always a good experience. most people ask before having ever read the wiki, not to say they read the archives :-). OT are so frequent...
The last time I looked there I saw so many topposting and HTML postings that I ran away. As long as the people agree that this is allowed (either by really allowing it, or by not doing anything about it) I won't go there.
I have been on suse-linux-e for quite some time (I joined sometime in 1999) and it is not as bad as you make it out to be. I see maybe 1 html email a week. There are more OT emails than I like and I try to discourage them but then I am not the list owner who is the one that should exert some control on the list. This use to be the case until a certain SuSE employee left the company. Perhaps that is all that is needed again, a list moderator. Not in the sense that that person manage every email that is posted but someone that can step in and put a halt to certain threads when they get out of hand, OT messages and messages that belong to another list. Top posting is a huge issue because there is no one in charge to put a stop to it. The users, such as myself, try to curtail its use but in the end we have no authority to stop it and the top posters know that we do not. I have found the suse-linux-e list to have a vast knowledgeable user base that has help thousands of users solve their problems. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998, opensuse since 2005
On Tue, May 23, 2006 at 11:14:54AM -0400, Kenneth Schneider wrote:
I have been on suse-linux-e for quite some time (I joined sometime in 1999) and it is not as bad as you make it out to be. I see maybe 1 html email a week.
I don't recall the numbers I saw. It was the general feeling after lurking that I disliked it. This is how _I_ feel about it. In no way do I want to say that that is what other people think, should think or experience. <snip>
This use to be the case until a certain SuSE employee left the company. Perhaps that is all that is needed again, a list moderator. Not in the sense that that person manage every email that is posted but someone that can step in and put a halt to certain threads when they get out of hand, OT messages and messages that belong to another list.
Step one is to block HTML and binaries, I think. As long as you have a reply that explains it, there should not really be a problem.
Top posting is a huge issue because there is no one in charge to put a stop to it. The users, such as myself, try to curtail its use but in the end we have no authority to stop it and the top posters know that we do not.
I can imagine that the SUSE people don't want to tell their users off. Many people would feel insulted and that is something you do not want to happen if you are a company.
I have found the suse-linux-e list to have a vast knowledgeable user base that has help thousands of users solve their problems.
Great. Perhaps somewhere in the future I will look again if it is for me. -- houghi http://houghi.org http://www.plainfaqs.org/linux/ http://www.netmeister.org/news/learn2quote.html
Today I went outside. My pupils have never been tinier...
On Tue, 2006-05-23 at 17:53 +0200, houghi wrote:
On Tue, May 23, 2006 at 11:14:54AM -0400, Kenneth Schneider wrote:
I have been on suse-linux-e for quite some time (I joined sometime in 1999) and it is not as bad as you make it out to be. I see maybe 1 html email a week.
I don't recall the numbers I saw. It was the general feeling after lurking that I disliked it. This is how _I_ feel about it. In no way do I want to say that that is what other people think, should think or experience.
<snip>
This use to be the case until a certain SuSE employee left the company. Perhaps that is all that is needed again, a list moderator. Not in the sense that that person manage every email that is posted but someone that can step in and put a halt to certain threads when they get out of hand, OT messages and messages that belong to another list.
Step one is to block HTML and binaries, I think. As long as you have a reply that explains it, there should not really be a problem.
Top posting is a huge issue because there is no one in charge to put a stop to it. The users, such as myself, try to curtail its use but in the end we have no authority to stop it and the top posters know that we do not.
I can imagine that the SUSE people don't want to tell their users off.
They would -not- be telling their users off just setting up some ground rules. Kind of what you do here when people top post and post technical questions. If there was someone in charge of how/what messages were posted people would be more inclined to follow the requests.
Many people would feel insulted and that is something you do not want to happen if you are a company.
No, they would more feel ashamed that they were reminded of the procedures requested for posting to the list. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
On Tue, May 23, 2006 at 12:37:02PM -0400, Kenneth Schneider wrote:
I can imagine that the SUSE people don't want to tell their users off.
They would -not- be telling their users off just setting up some ground rules. Kind of what you do here when people top post and post technical questions. If there was someone in charge of how/what messages were posted people would be more inclined to follow the requests.
I know that they would not actually be telling people off. The perception of people _can_ be different.
Many people would feel insulted and that is something you do not want to happen if you are a company.
No, they would more feel ashamed that they were reminded of the procedures requested for posting to the list.
There will be people who will feel insulted. That feeling is unjust, yet people will feel that. Not the majority, yet still. Unfortunate, but that is what _could_ happen and that _might be_ the reason why nobody really steps forward. I can only asume that that is the reason nobody is realy resposible or takes it. -- houghi http://houghi.org http://www.plainfaqs.org/linux/ http://www.netmeister.org/news/learn2quote.html
Today I went outside. My pupils have never been tinier...
Hey Guys, Quick question :Has anybody got APT to work on opensuse 10.1 I miss APT / synaptic Cheers, Jimmy NUI.fr
participants (5)
-
houghi -
jdd -
jimmy Pierre -
kengheng -
Kenneth Schneider