Am Dienstag 06 November 2007 schrieb Daniele:

HI guys, after first look I'm very disappointed about live-cd but before start to reporting bug and features request I'd like to hear your opinions.

Hi Daniele, This list is for non-technical discussions, your list are all technical I think.

1) sound doens't work. On live cd it simple should work. No luck with yast or alsaconf. In Yast I can hear test sound but under Kde no mixer, no device, no sound. This on well supported hardware..

Sounds like a valid bug report.

2) partitions on hd should be showed somewhere (sysinfo, /media). For newbye, finding/mounting partitions it's no so easy..

They are hidden by HAL. Valid feature request.

3) one of my pc is a IBN NetVista that runs 10.3 fine but with live-cd, video card/monitor are non well configured and system hangs for some ATA errors..

Valid bug report.

4) I'm wrong or software on live-cd is in the same version of GM ? If so, I don't uderstand why. Releasing live-cd one month after GM without bugfix it's a crazy thing :)

Yes, because the month was for fixing the install. We didn't want a moving target. Greetings, Stephan --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org

Den Wednesday 07 November 2007 19:17:55 skrev Daniele:

...

This list is for non-technical discussions, your list are all technical I think.

This is the main point (or big part of it..). After a lot of bad reviews about 10.3, releasing live-cd in this state it's a big mistake and not the right way to do things...

Right way: another RC with all fix.

I'm a "suser" since 6.0 and now I'm bored to surf the net and read bad things about my favorite distro. This release doesn't help much, the whole project I mean..

I think that's a bit harsh. 5-6 weeks ago everyone was extremely pleased and optimistic about 10.3. And it's still my impression that most people like it better than the previous two releases - even though it seems to not do quite as well as I expected. 10.3 had a lot of changes - correct and important changes imo. I think this means we're now back on the right path, and hopefully that means there can be more focus on stabilizing, maturing, polishing and optimizing, and less on making huge revolutionary changes to core stuff (like media layout and package management.) I'm a lot more optimistic on behalf of the project now than I was 6 months ago. Btw. I couldn't get sound to work on my laptop using the KDE live-cd either :-) (after installation it worked without a glitch). --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org

On Wednesday 07 November 2007 12:56, Maciej Pilichowski wrote:

Just thinking out loud -- maybe it would be better to focus on core system (thing to be defined) and support it, but support it from A do Z, instead of providing thousands of packages (compare it to Apple, they took a bit of BSD, but made well use of it). Then it would be possible to provide better compatibility, hardware support, and incremental upgrades (and realease would mean just: snapshot of last month set of packages).

I have a strong feeling that the first approach is exactly what SLED does, while we live on the "bleeding edge" of things. I've always gone by the mantra that I should have my production systems at least one version back, unless the current version is very stable. I'll hold off until 10.3 releases a few bugfixes. I have it in VMWare and all seems well, but it ain't running my systems at home until I know it works right. :P --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org

Maciej Pilichowski wrote:

I can speak only for myself of course -- but after 10.2->10.3 I am afraid of upgrading again like I did before. I need another computer to do it, test and see it for myself, and then decide. And I don't work for NASA or anything like that, just desktop system. (Survey could be here handy -- if users are new/upgrade and if they are happy and about what, and if they are unhappy and about what).

You can say I am complaining (but I hope I am not), but even if -- it is the _fact_ that upgrades takes more and more time to fix things, while upgrade should be transparent.

I've seen quite a few posts on our forum complaining about failed upgrades, even dating as far back as 9.3 -> 10.0. I myself have also experienced upgrade failures where my newly installed system would not boot or give me a graphical interface. I have adopted the policy of keeping my /home partition separate from my root partition, then simply formatting the root partition and installing the new version freshly over it. It's worked out well (and I noticed that 10.3 by default wants to split / and /home into two partitions!). A few of our contributing members have noticed this trend as well, as mentioned in this thread: http://www.suseforums.net/index.php?s=eba227af1c7e10765fc84747c7e13943&showtopic=41347&view=findpost&p=209935 While I do love my OpenSUSE, perhaps its upgrade system could use a closer look during the planning/preparing stages of 11.0.

With incremental upgrade you don't have element of surprise ("wow, what a cool system, million bugs fixed") but on the other hand you don't have element of disappointment ("gee, nothing works") -- but is good for system reliability, you introduce fewer new features, you wait for responses, fix bugs, again introduce new features, and so on. It is easier to track those, maintain project, etc.

I don't like the idea of an incremental upgrade on OpenSUSE, mostly because of the lack of publicity it generates. The only things you hear about Gentoo these days in the news channels are complaints about it or its developers (fighting again this week, I see), and not what they're fixing or creating for the next release. With a set release schedule you keep a flow of positive news going out on a fairly regular basis. Besides, I think the opensuse-updater program in 10.3 has been working wonderfully. The bugs I've run into on my 10.3 installation have already been pushed out via opensuse-updater, and all the security exploits I've read about recently have been patched already. Assuming this large trend continues (lots of patches between releases), it's almost as good as the incremental update but we get to keep the publicity angle. ~~ Andrew D. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org

Hello, I am merging several answers.

I have adopted the policy of keeping my /home partition separate from my root partition, then simply formatting the root partition and installing the new version freshly over it. It's worked out well (and I noticed that 10.3 by default wants to split / and /home into two partitions!).

It won't help in my case: a) I have to select packages to install just as while upgrade b) I have to restore configuration just as while upgrade

I don't like the idea of an incremental upgrade on OpenSUSE, mostly because of the lack of publicity it generates.

?

With a set release schedule you keep a flow of positive news going out on a fairly regular basis.

Yes you will found a big element of surprise if your concept of "incremental upgrade" is what you described on the thread "opensuse upgrade: newer, faster, worse". The surprise is :"it will not work at all".

I think we don't understand each other. The schedule would be like this: a) new features in yast b) release c) fix bugs d) new features in kernel e) release d) fix bugs and so on. Current release everything -> upgrade can (and it does) change a lot things in system. There are so many that it is hard to reproduce for developers, they are so many it is hard to report them, etc. And I don't see how releasing just new package manager for current system is worse than release the same package manager but with new kernel, installer, KDE, Gnome and thousands of other packages. If new package manager does not work it won't work with the rest as well. And again -- focusing on selected software would help, keeping thousands of packages is asking for trouble (imho).

I have a strong feeling that the first approach is exactly what SLED does, while we live on the "bleeding edge" of things.

Good news then, but I don't have chance to really test SLED -- by test I mean install version X and wait how upgrade to Y works.

I've always gone by the mantra that I should have my production systems at least one version back, unless the current version is very stable.

Very true. But this is probably good for system administrator, for desktop users this policy should be more restrictive. Clone the system, install it on another computer, do upgrade, evaluate, then upgrade for real or not. have a nice day, bye -- Maciej Pilichowski --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org

Maciej Pilichowski escribió:

...

I have a strong feeling that the first approach is exactly what SLED does, while we live on the "bleeding edge" of things.

Good news then, but I don't have chance to really test SLED -- by test I mean install version X and wait how upgrade to Y works.

There is big difference between what SLED does and what you suggested to do, you talked about incremental updates **between different products** (aka. opensuse 10.2 --> 10.3) keeping old "downgraded" packages installed etc.. what SLED does is providing slightly new or fixed packages compiled with the **same** other tools, **same** libraries via services packs for the **same product** and of course only the provided package set/combination is supported. -- "If eval() is the answer, you're almost certainly asking the wrong question." --Rasmus Lerdorf Cristian Rodríguez R, Core Services SUSE LINUX Products GmbH Research & Development http://www.opensuse.org/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org

Am Donnerstag 08 November 2007 schrieb Daniele:

Il giovedì 8 novembre 2007, Stephan Kulow scrisse:

...

Am Mittwoch 07 November 2007 schrieb Daniele:

...

I'm a "suser" since 6.0 and now I'm bored to surf the net and read bad things about my favorite distro. This release doesn't help much, the whole project I mean..

No problem, read the good things and be happy: http://wadejolson.wordpress.com/2007/11/07/wait-whats-going-on-here/

Good reviews are lesser then bad.. http://news.opensuse.org/?p=489 here too...

Everyone has have a complaint about something else. I can't see a common pattern. Some want a DVD, others want a faster download. So what is your conclusion - provide a supercompressed DVD? I'm not sure where you're heading. You still believe it's possible to create a product everyone is happy with? I'm sorry it has to be me telling you the truth of the world: people are different.

...

What are the bad reviews bugs you want to see fixed? Have they a bugzilla entry?

http://en.opensuse.org/Reviews/10_3/Comments and never minds if some of them are false, partially true or whatever..

http://en.opensuse.org/Distro_Inspirations it seems that other distro do a lot of things better..

For me 10.3 is a good release but after 10.1 (AKA zmd-disaster), 10.2 (AKA The day after: the hope) a "good" release is not enough and live-cd are not so good...

It's easy to find post/blog entry like: suse i slow, suse doesn't have a good package manager (partially true..), opensuse is beta-testing for commercial version, installer is slow, missing this, doesn't do that and so on..

I know. And as with 10.3 we'll try to work on fixing the biggest complaints for 11.0 and you're very welcome to help out. But 10.3 is done. Having said that, releasing a new live CD with the fixes shortly before christmas is very much possible. It will still have a slower package manager than debian though. It's something where we can improve for 11.0, but it's nothing we have to be take down 10.3 for. Greetings, Stephan -- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org

Stephan Kulow wrote:

christmas is very much possible. It will still have a slower package manager than debian though. It's something where we can improve for 11.0, but it's nothing we have to be take down 10.3 for.

openSUSE 10.3 package manager is near perfect... much much improved comparing to 10.2 one and very fast jdd -- http://www.dodin.net http://www.ladepeche.fr/article/2007/10/27/127022-Claire-Dodin-une-Toulousai... --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org

Am Freitag 09 November 2007 schrieb jdd:

Stephan Kulow wrote:

...

christmas is very much possible. It will still have a slower package manager than debian though. It's something where we can improve for 11.0, but it's nothing we have to be take down 10.3 for.

openSUSE 10.3 package manager is near perfect... much much improved comparing to 10.2 one and very fast

Yes, sure. It's near perfect and very fast. It just tends to degrade if you actually use it :) And of course it's a vast improvement over 10.2's package manager, it's just that the day is limited to 24 hours, so 10.3's package manager had to be left at "near perfect". Greetings, Stephan -- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org

-------------------------------------------------- From: "jdd" Sent: Friday, November 09, 2007 8:31 AM Cc: Subject: Re: [opensuse-project] KDE-LIVE-CD, very bad impressions

Maciej Pilichowski wrote:

...

I thought it was clear -- you as a user could get Windows Vista (if you like MS example) or get Win 1.0 (or Win95 -- anything released) and apply _all_ updates to make this Vista

only in your dream. Vista is not even able to update from XP... no windows version was able to update from the previous one

jdd

--

You could upgrade from the previous one, but not update from the previous one. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org

Maciej Pilichowski wrote:

__hypothetical__ example! WHAT IF...

ok :-) but do you know any system doing this? computer world is moving very fast, and Linux may be faster. So who can know what will be standard three years in the future? I don't see how a system can follow this. For example, I never even try to update any distro. I just left a 10.1 computer to a new laptop and installed 10.3 on it, never mind to change 10.1 on the old one, even knowing the package manager was much better :-) do we need incremental update at all? ideally I would refuse any update. just security bug fix are ok, no more jdd -- http://www.dodin.net http://www.ladepeche.fr/article/2007/10/27/127022-Claire-Dodin-une-Toulousai... --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org

Andrew Dorney wrote:

jdd wrote:

...

Maciej Pilichowski wrote:

...

__hypothetical__ example! WHAT IF... ok :-)

but do you know any system doing this? http://www.gentoo.org http://www.archlinux.org

I'm not so sure gentoo fits the scope (I already used it). I would go from kde3 to kde4 with many cautions, and same for any major number change in an aplication. and giving this, any distro can compile. jdd -- http://www.dodin.net http://www.ladepeche.fr/article/2007/10/27/127022-Claire-Dodin-une-Toulousai... --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org

Il venerdì 9 novembre 2007, Stephan Kulow scrisse:

Yes, sure. It's near perfect and very fast. It just tends to degrade if you actually use it :)

And of course it's a vast improvement over 10.2's package manager, it's just that the day is limited to 24 hours, so 10.3's package manager had to be left at "near perfect".

Yes big improvement but after a crappy version it's easy to do big improvements. Missing features: 1) keep downloaded packages 2) download-only mode Improvements required: 1) better feedback/ouput from zypper like in smart. Clear and readble. 2) better/alternative workflow: now download->install-download->install and so on. Switch to download all packages and then start installation (like in smart or apt) Still missing a runtime upgrade like in Debian. Reading zypper ML seems that developers are aware of these things. So good hopes for 11.0 Bye. -- *** Linux user # 198661 ---_ ICQ 33500725 *** *** Home http://www.kailed.net *** *** Powered by openSUSE *** --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org

Il sabato 10 novembre 2007, Stephan Kulow scrisse:

...

Don't release iso with know bugs.

Yeah, right! And somewhen in 2012 everyone will have lost interest and then we'll release 11.0 because no-one left to test and file bug reports. And _then_ we have a great release with the latest, greatest that 2007 could offer.

Sorry, but known bugs are just part of everyone's life in software development. And if your tv card is likely not to work, better stay on factory and always send a patch whenever it breaks. The more developers on factory the better. No. Remember that we are talking about live-cd and for know bugs I mean bugs already fixed! I know that at some point you have to do a release without keeping balls rolling forever (debian way) but I don't understand why you don't fix things when fix is avaible since days/weeks!

And I don't understand why I should stay on factory when my tv-card is well supported since years and bug is present _only_ in live cd. Works fine on installed 10.3. Bye. -- *** Linux user # 198661 ---_ ICQ 33500725 *** *** Home http://www.kailed.net *** *** Powered by openSUSE *** --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org

Maciej Pilichowski escribió:

Do it then -- but not all changes at once.

It is a chain.. if you make a big rework of component FOO , you will probably need to change (A..Z) packages depending on X and those why dependend on the previuos may also need some adaptations. I will give you just an actual example, in order to upgrade the compiler for openSUSE 11 we are currenlty changing more than 800 packages !! -- "If eval() is the answer, you're almost certainly asking the wrong question." --Rasmus Lerdorf Cristian Rodríguez R, Core Services SUSE LINUX Products GmbH Research & Development http://www.opensuse.org/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org

Hello,

I will give you just an actual example, in order to upgrade the compiler for openSUSE 11 we are currenlty changing more than 800 packages !!

And the problem is "solved"? For me this example is just a proof that something is terribly wrong and it would be rather a good argument to rethink the design of the system. Otherwise in 5 years you will be writting "for opensuse 17 we had to change over 24000 packages". It is pretty obvious the current design does not scale. have a nice day, bye -- Maciej Pilichowski --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org

On Sunday 11 November 2007 10:55:29 am Maciej Pilichowski wrote:

ad.a,b,c...) of course with update of X maybe you have to update Y, but it would be a still update of portion of the system, just bigger or smaller, not the entire lengthy process of upgrade which looks like an install

I'm not packager, but I have some idea what is the problem. When Cristian referred to gcc with 800 dependant packages that should be recompiled which translates in word 'updated' from user side, that was example what size can be one incremental update. I guess that it would be even worse with glibc. In case that you have design flaw that impares computer, there is no backward compatibility that will justify not to drop it and create better solution. The result is need for massive changes and update for all packages that use it. This is the case where idea of endless incremental update will become one large update, and that is exactly what we have now. If you like incremental update than use software repositories of openSUSE Build Service. For instance, I have often new version of KDE before official release. What is that if not incremental update? It is just not officially supported by Novell/SUSE, they don't patch such versions. -- Regards, Rajko. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org

I answer to incremental update, ok? I assume you were using 10.2 before 10.3. Would it be any harm to you (your system), if instead of upgrading/(re)installing whole 10.3 over 10.2, you did the following (using 10.2 all the time): a) update boot mechanism to boot faster (in June) b) update Yast SM to faster version (in July) c) update regular KMail to KMail Enterprise (...and so on) d) update KDE 3.5.7 to 3.5.8 e) ...

And while doing and testing all that, in each time would they make the new version? From midnight to 6AM, instead of sleeping? With what resources they would do what they already do, which is to make a new release and maintain the bugfix/security of previous ***AND*** do backports and tests like that? Because if you dont want backport and tests there are new packages in the buildservice, and people with upgraditis that does not understand what is a stable system use them like madness Are you a software engineer or your pulling all that from thin air? How do you know this is the "way it should be done" ? Its funny from time to time someone joins the mail list and start giving orders and complained like the guy was hired to do some auditing in the "company", like the zealots coming say "oh, why opensuse doesnt use apt-get", and the guy doesnt even know the difference between two package managers in linux.... Just because a distro does some practice doesnt mean all distros should. And this way of thinking that all distros should do the same thing is silly, because the nice thing in linux is that there are lots of distros doing things in different ways. And the opensuse release cycle works for opensuse, and we all like it, so no incremental would suck a lot and you saying "its easy" doesnt make it any more easy or feasible, you talk like it was magic "oh upgrade kmail" and use magic wand and boom, kmail is updated. Doesnt work like that in planet earth... You say "incremental updates" like nobody on earth would need to move one finger to make it happen, like it would be no cost of time, dollars and engineering. Its easy to create trouble and work you are not going to solve, or point the solution Marcio

In other words -- what do you need whole new version of opensuse for?

have a nice day, bye

ad.a,b,c...) of course with update of X maybe you have to update Y, but it would be a still update of portion of the system, just bigger or smaller, not the entire lengthy process of upgrade which looks like an install -- Maciej Pilichowski

--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org

--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org

Hello,

If you like incremental update than use software repositories of openSUSE Build Service. For instance, I have often new version of KDE before official release. What is that if not incremental update?

Yes, but even the "official" version would be an incremental update because you would update only KDE -- there would be no need to update kernel, Gnome, chromium, OOffice, etc. right? (*) Anyway, you can say partial update is available in opensuse, true, what would be my wish is to go this path even further.

When Cristian referred to gcc with 800 dependant packages that should be recompiled which translates in word 'updated' from user side, that was example what size can be one incremental update.

Yes, but technically it would be still an update. (*) have a nice day, bye (*) there is one disturbing piece, that in those examples we are mixing applications and operating system, but since opensuse is not an OS, but a "distribution" I can give only such examples -- Maciej Pilichowski --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org

Rajko M. escribió:

When Cristian referred to gcc with 800 dependant packages that should be recompiled which translates in word 'updated' from user side, that was example what size can be one incremental update.

No, what I told was we had to **change** 800 packages, that is, modify the **source code** in order to allow them to be compiled again, packages are always recompiled when a dependant package is modified, that's no news. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org

On Sunday 11 November 2007 05:45:27 pm Cristian Rodríguez wrote:

Rajko M. escribió:

...

When Cristian referred to gcc with 800 dependant packages that should be recompiled which translates in word 'updated' from user side, that was example what size can be one incremental update.

No, what I told was we had to **change** 800 packages, that is, modify the **source code** in order to allow them to be compiled again, packages are always recompiled when a dependant package is modified, that's no news.

Sorry for this. Quoting is better with copy and paste :-) The next paragraph with example of glibc tells exactly the same. We, and any other distribution, actually have what he is asking for, but right now looking quotes in his last 2 replies to my posts, he understands that very well and replies just to have a fun. -- Regards, Rajko. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org

From the outside, it looks as if KDE4 test methods have been spread too thin, 1 method that really worked, even if that meant re-installing OS 10.3 from scratch would have been more effective than

On 25/11/2007, Gerald Pfeifer wrote: On Sat, 10 Nov 2007, Daniele wrote: > Don't release iso with know bugs. Well, if we strictly followed this advice we'd never, ever see a new openSUSE release. :-) A distribution comprising software on the order of a couple of hundred millions lines of source code always will have bugs, both unknown and known. As someone interested in doing some test work on KDE4, that is understood. OTOH I also see that encouraging end users to try out KDE4, but then not providing a recent and updatable version, that lets you submit useful bug reports and see bugs get fixed; does not really help anyone and could be perceived as time wasting. On KDE4 test I tried : KDE OS Live CD (late Oct, too little in it and seemed too out of date, got updated) OS 10.3 install KDE4 Look at KDE SVN build (I used Gentoo in past, but considered this last resort) SuSE Build Service KDE4 - fails to let me log in with test kde4 user account, and no updates via YOU last 2 weeks At same time, I read lwn.net and see KDE4 is really needing testers. There is a sense of frustration, at not finding a realistic way to help test KDE4; and contribute to shaking down the new releases. To do this effectively, probably KDE4 rpm's updated via YOU, which track the latest rc releases would seem most effective. the dabbling without end result. From the PR it looks like OS wants to help KDE4 get stable, but in practice nothing I have tried, has worked well enough to make me confident to submit a bug report. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org

Il domenica 25 novembre 2007, Gerald Pfeifer scrisse:

On Sat, 10 Nov 2007, Daniele wrote:

...

Don't release iso with know bugs.

Well, if we strictly followed this advice we'd never, ever see a new openSUSE release. :-) Hi, pleale, re-read this post: http://lists.opensuse.org/opensuse-project/2007-11/msg00056.html

know bugs->already fixed bugs! Bye. -- *** Linux user # 198661 ---_ ICQ 33500725 *** *** Home http://www.kailed.net *** *** Powered by openSUSE *** --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org

On 27/11/2007, Daniele wrote:

...

Il domenica 25 novembre 2007, Gerald Pfeifer scrisse:

...

On Sat, 10 Nov 2007, Daniele wrote:

...

Don't release iso with know bugs.

Well, if we strictly followed this advice we'd never, ever see a new openSUSE release. :-)

Hi, pleale, re-read this post: http://lists.opensuse.org/opensuse-project/2007-11/msg00056.html

Would it be feasible to use a loopback mount to update a Live CD iso image on disk, and then reburn? It's impossilbe to have a deliverable I don't think it's technically possible. But the kiwi config is in public SVN and all the packages are in the public. All you need is a 10.3 with kiwi installed (actually, I say 10.3 here because you need quite some tools

Am Dienstag 27 November 2007 schrieb Rob OpenSuSE: that are in the right version on 10.3, but you can of course patch other systems too), a 10.3 GM DVD and a subversion client to download the config. Then you can create your own personal live CD whenever you feel like it. Even with different packages than the official. Greetings, Stephan --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org