- openSUSE Project

[opensuse-project] openSUSE GNOME meeting (2008/11/20)
by Rodrigo Moya 21 Nov '08

21 Nov '08

Contrib and G:C update • Judging from recent ML threads, there's increased interest on Contrib • Discussion about G:C drops/updates/moves in G:C on the opensuse-gnome ML: • packages obsoleted by ones in factory (banshee, f-spot, pidgin, python stuff, tomboy, tasque) • other obsoleted (gnome-vfs-obexftp) • If no more feedback by Monday, all this will be done Promotion of GNOME within openSUSE 11.1 • Addition of opensuse-specific developer info to GNOME wiki (http://live.gnome.org) Wiki work • Wiki mockup updated soon • Icons are going to be difficult to pull off (tango icons) • Meeting agendas will get more attention Dropping/adding packages • Postponing this to the beginning of 11.2, too late to remove from 11.1 1-click install for 2.24 • Still some build problems preventing ymp creation -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

1 0

[opensuse-project] Projects
by Joop Boonen 20 Nov '08

20 Nov '08

All, I was looking via: http://software.opensuse.org/search trough different packages in OBS. I saw that there quite a few duplicate projects. Some with identical new versions and some with old versions. I saw there are also quite a few overlaps with the fwbuilder package that I also have in OBS. So I'm wondering if there is a way to consolidate packages in groups so that more people can put effort in building packages and bundle their knowledge to get the best out of it. Currently a lot of people put a lot of time in "duplicate" packages. I'm wondering wouldn't it be better to start for for instance fwbuilder a security project that can be maintained by joined effort of people? In that way more package can be maintained in OBS I think? If this option if feaseble what is the best way to accomplish this? The project ofcourse needs to be created. Shall the individual OBS builder contact the other OBS builder? Regards, Joop Boonen. -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

5 7

[opensuse-project] Linux in 5 seconds
by Rajko M. 15 Nov '08

15 Nov '08

... Within five seconds of turning on this $360 USD gaming/enthusiast motherboard, you can be using Linux and surfing the Internet ... http://www.phoronix.com/scan.php?page=article&item=869&num=1 Majority of users are still keep computer on only when needed. Fast boot option would make Linux serious alternative for them. Test hardware on installation, configure it once, ask user is there anything to change, put that in fast loadable image like Live CD, make it default GRUB boot option. Is answer in software appliances? -- Regards, Rajko -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

1 0

Re: [opensuse-project] Novell internal programs on NON-OSS repository? (ie Novell Client)
by Joe Harmon 12 Nov '08

12 Nov '08

On Tue, 2008-11-11 at 11:51 -0300, Cristian Rodríguez wrote: > > Really. I suppose you had a look at this bug already: > > https://bugzilla.novell.com/show_bug.cgi?id=262319 > > We tried to get this __really__ fixed.. no avail so far :-( it seems > to me there are not enough resources ... It has been available for quite a long time. http://download.novell.com/Download?buildid=au3IFDRvnCA~ -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

2 1

Re: [opensuse-project] Novell internal programs onNON-OSSrepository? (ie Novell Client)
by Dominique Leuenberger 11 Nov '08

11 Nov '08

>>From: Joe Harmon <jharmon@> >> are you sure about this? the 2.0 beta client for example installs on a >> 11.1 beta system (I'm on beta 5) with some hurdles (some symlinking). >> But the novfs for example simply can't compile (the client ships with >> 2.0.0-504, whereas in the kernel, 2.6.27.5 is 2.0.0-440). > >The 2.0 client includes novell-novfs which will cause problems during the install because novfs is already in the kernel (since openSUSE >11.0) With the 2.0 SP1 client that we build for openSUSE 11.0, we removed novell-novfs. However, the 2.0 SP1 client for openSUSE will >not run on openSUSE 11.1 or SLE 11 due to some build issues. We are working on those build issues right now in hopes to soon have a >client for SLE 11 and openSUSE 11.1. This argumentation sound very very flumsy... you report to much to managers I'd say :) As said, the novfs in the kernel is of an older version than the one shipped with NCL2.0SP1 (beta), and the newer novfs does not build (missing asm/semaphore.h, bailing out with semaphore.count afterwards). Besides that, I could install it (--nodeps on novell-xtier, due to libfd version mismatches.. some symlinking fixed it). Login works typically too. Joe, if there is anything anybody from the community can offer for this to move at a higher speed, please speak up. We are plenty out here, some with more, some with less knowledge, but all of us with a lot of will to get our targets moving. Dominique -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

2 1

Re: [opensuse-project] Novell internal programs on NON-OSS repository? (ie Novell Client)
by Susanne Oberhauser 11 Nov '08

11 Nov '08

"Joe Harmon" <jharmon(a)novell.com> writes: > On Tue, 2008-11-11 at 10:04 +0100, Susanne Oberhauser wrote: >> > It does sound quite hopeless, tried in the past already. Seems that >> > the Novell Client for Linux is developed by the part of Novell that >> > doesn't care at all about openSUSE. I didn't say this, I quoted it to disagree with it. > I don't agree with this statement. If we didn't care about openSUSE > then we wouldn't develop to it. And we ran into other issues with > the kmp method I'd like to know more about them. > and putting novfs in the kernel was a benefit to us. I also don't > think the different release cycles are an issue. and I'm glad you found this work-around. > Joe Harmon :) S. -- Susanne Oberhauser +49-911-74053-574 SUSE -- a Novell Business OPS Engineering Maxfeldstraße 5 Processes and Infrastructure Nürnberg SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

2 1

Re: [opensuse-project] Novell internal programs on NON-OSS repository? (ie Novell Client)
by Dominique Leuenberger 11 Nov '08

11 Nov '08

On Tue, 2008-11-11 at 10:08 -0700, Joe Harmon wrote: > On Tue, 2008-11-11 at 10:04 +0100, Susanne Oberhauser wrote: > > > It does sound quite hopeless, tried in the past already. Seems that > > > the Novell Client for Linux is developed by the part of Novell that > > > doesn't care at all about openSUSE. > > I don't agree with this statement. If we didn't care about openSUSE then > we wouldn't develop to it. And we ran into other issues with the kmp > method and putting novfs in the kernel was a benefit to us. I also don't > think the different release cycles are an issue. Joe, are you sure about this? the 2.0 beta client for example installs on a 11.1 beta system (I'm on beta 5) with some hurdles (some symlinking). But the novfs for example simply can't compile (the client ships with 2.0.0-504, whereas in the kernel, 2.6.27.5 is 2.0.0-440). I'm not sure yet if THAT is the reason that I can't write to any of my netware volumes, but df shows them all having 0 bytes free... not a lot, considering that at least some of the volumes are cluster resources on a SAN and that the operational system is using those volumes for daily business. If I see that issuing bugs for the client actually has an effect (besides be writing them and then nothing happening), I will gladly do it. But at least from the past, it appears the NCL development is to much behind closed doors. Dominique -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

2 1

Re: [opensuse-project] Novell internal programs on NON-OSS repository? (ie Novell Client)
by Joe Harmon 11 Nov '08

11 Nov '08

On Tue, 2008-11-11 at 10:04 +0100, Susanne Oberhauser wrote: > > It does sound quite hopeless, tried in the past already. Seems that > > the Novell Client for Linux is developed by the part of Novell that > > doesn't care at all about openSUSE. I don't agree with this statement. If we didn't care about openSUSE then we wouldn't develop to it. And we ran into other issues with the kmp method and putting novfs in the kernel was a benefit to us. I also don't think the different release cycles are an issue. Joe Harmon -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

1 0

Re: [opensuse-project] Novell internal programs on NON-OSS repository? (ie Novell Client)
by Dominique Leuenberger 11 Nov '08

11 Nov '08

Hi, On Mon, 2008-11-10 at 12:12 +0100, Andreas Jaeger wrote: > Note: novfs is now part of our kernel tree: > pm -qlp kernel-default-2.6.27.5-1.1.i586.rpm |grep novfs > /lib/modules/2.6.27.5-1-default/kernel/fs/novfs > /lib/modules/2.6.27.5-1-default/kernel/fs/novfs/novfs.ko > > So, no need anymore for the kmp. > It IS part of the kernel, but (at least on my system... I did not update yet to the 2.6.27.5 kernel) the version is older than what is shipped in the 2.0 beta client (2.0.0-440 vs 2.0.0-504 from the client) > We could if they have the quality we need and get released at the right > time - and the last is one problem, we do not want to touch the official > repos after we released the goldmaster, That might be a critical point, especially considering that for 10.3 there is still no 'releasable quality' available. Is there something else that can be done in further improving this state? (I have nothing against playing the bridge between two Novell departments :) ) Dominique -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

4 4

Re: [opensuse-project] Novell internal programs on NON-OSS repository? (ie Novell Client)
by Dominique Leuenberger 11 Nov '08

11 Nov '08

On Tue, 2008-11-11 at 10:04 +0100, Susanne Oberhauser wrote: > Pascal Bleser <pascal.bleser(a)opensuse.org> writes: > >> It IS part of the kernel, but (at least on my system... I did not update > >> yet to the 2.6.27.5 kernel) the version is older than what is shipped in > >> the 2.0 beta client (2.0.0-440 vs 2.0.0-504 from the client) > > > > Ouch, so now it means that there is no way to upgrade the KMP as it > > will conflict with the kernel package :( > > ko modules from KMPs go to a different location > (/lib/modules/$kernel/updates) so they don't conflict. > Yes, I'm sure KMPs can still be used.. but they don't exist ;) > non-oss repos on build.opensuse.org is an interesting idea. > I was actually referring to the already existing non-oss repository of the openSUSE distribution, but a (maybe exceptional permission) to host NCL on OBS would be fantastic! > > It does sound quite hopeless, tried in the past already. Seems that > > the Novell Client for Linux is developed by the part of Novell that > > doesn't care at all about openSUSE. > > 'not at all' is too strong -- it's about priorities and about risk: > Sounds maybe to strong, but from all the bugreports I was involved for NCL in the last months, it sounds almost realistic :( > openSUSE has no support or QOS commitments whatsoever, and no API > commitments, nothing. It's a world in its own and there is a lot of > goodwill but nobody would buy a great car if you *maybe* get it fixed, > which is if someone happens to be interested in fixing it. > > So if Novell officially commits to support a product on top of > openSUSE, and some bug that shows in the product actually needs a fix > in the base OS, then the users are bad off. > Give as much support to the novell client as to openSUSE itself. I'm sure not everybody is going to install it in an office environment. Some are geeky (like Pascal and me :) ) and we want to be able to perform our work on our latest greatest platforms (after all: I already use 11.1 in prod environment... 'using' is the best way to spot bugs. Even though it requires some background knowledge in order to circumvent some appearing bugs. > That's why. It's actually a "we do care": we care about the > implications. > > I agree, though, a 'beta' release with goodwill commitments could be a > Good Thing. A repository containing NCL, that actually can be installed (without many symlinking tricks) would be a great step in this direction. And I promise I would submit all the bugs I can find ;) After all: NCL will probably bi shipped on CODE11 anyhow; CODE11 will be (mostly) based off openSUSE 11.1. So all the reports you get now for openSUSE 11.1 together with NCL can already be treated before SLE goes out of the door. I think THAT should be a good motivation, isn't it? Dominique -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

1 0