July 2012 - openSUSE Users - openSUSE Mailing Lists

[opensuse] Cuda5 and SuSE 12.1?
by Peter Maffter 22 Jul '12

22 Jul '12

Did anybody test CUDA5 Preview on SuSE 12.1 (gcc 4.6-15.1.3): http://developer.nvidia.com/cuda-downloads Thanks in advance. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 1

[opensuse] Layer 7 on new kernel (new OpenSuSE)
by Wong 22 Jul '12

22 Jul '12

Hi All, Currently I am still using OpenSuSE 11.2 with kernel 2.6.34. Perhaps everyone laughs at me as an old fashioned guy. I am stuck on a layer 7 filtering application that unable run on kernel beyond 2.6.34. It is l7-filter. Need your advise what application to layer 7 filtering / marking. Thanks & Regards, Awie -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] problem witht Java: Can't find bundle for base name javax.servlet.http.LocalStrings, locale de_DE
by Robert Rottermann 22 Jul '12

22 Jul '12

Hi there, I try to install Apache-solr and Apache-Jetty into on a Suse 12.1 box. After starting to start jetty solr is not accessible I find the following error in the log. Unfortunately my java skills are just about nil.. I would verymuch apreciate if somebody could point me to a solution. thanks robert Exception in thread "main" java.lang.ExceptionInInitializerError at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:532) at java.lang.Class.newInstance0(Class.java:372) at java.lang.Class.newInstance(Class.java:325) at org.mortbay.jetty.servlet.Holder.newInstance(Holder.java:199) at org.mortbay.jetty.servlet.ServletHolder.start(ServletHolder.java:240) at org.mortbay.jetty.servlet.ServletHandler.initializeServlets(ServletHandler.java:446) at org.mortbay.jetty.servlet.WebApplicationHandler.initializeServlets(WebApplicationHandler.java:321) at org.mortbay.jetty.servlet.WebApplicationContext.doStart(WebApplicationContext.java:509) at org.mortbay.util.Container.start(Container.java:72) at org.mortbay.http.HttpServer.doStart(HttpServer.java:708) at org.mortbay.util.Container.start(Container.java:72) at org.mortbay.jetty.Server.main(Server.java:460) Caused by: java.util.MissingResourceException: Can't find bundle for base name javax.servlet.http.LocalStrings, locale de_DE at java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:1539) at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1278) at java.util.ResourceBundle.getBundle(ResourceBundle.java:733) at javax.servlet.http.HttpServlet.<clinit>(Unknown Source) ... 15 more -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Re: openSUSE build & testing procedure and faulty pruning of builds causing rpmbuild failures
by Linda Walsh 22 Jul '12

22 Jul '12

Brian K. White wrote: > If the _spec_ file tried to delete files that it didn't create, in > your main system's real absolute path, that might be a packaging > error, or maybe not, because a package is always designed for some > context, and when you use it outside of that specific context, you are > on your own. > > If just for example, you try to install a redhat rpm on suse, it may > or may not work, but even if it not only doesn't work but kills your > box, it's your fault. Whatever it did would have worked on the redhat > system it was meant for. ===== Beautiful example. Now, would you expect that if you had an up-to-date 12.1 system with official 12.1 packages installed -- including (since you want to build samba, the "devel" packages produced by that package), that it should fail? Or are you saying we need something as different as RedHat v SuSE to do builds of the binaries on our openSuSE systems from their source RPM's? Do you do any development on linux or build source packages -- sometimes the source RPM, but more often, from downloading the tarball, and using the packages configure/Makefile scripts? Let's say you do, (cuz if you don't, then you would be unlikely to firmly understand the issues involved here, ;^) ). Is your system more likely to have the devel packages installed for the packages you build, or do you expect to install in a VM or chroot environment and install all the packages you need each time you do a build with only it's specific requirements loaded into the VM? Now understand that you've been building suse packages from their source RPM's since V7.3 -- a bit over 10 years, and it's worked on suse systems from past generations, but now you can no longer generate on a system with all the requirements installed -- you have to prune off all unnecessary stuff from your system, now as well, because suse doesn't allow for the complete package building -- it's only providing partial packages that require you don't have various packages/pieces installed. it's source RPM since > When you write a script and it works, and then you try to stick it in > a cron job and it doesn't work, that's not cron's fault for "setting > up a sterile environment". That sterile environment is the only way to > get any sort of sanity, predictability and consistency. --- Are you saying the suse packages have no more intelligence than cron? Cron isn't a tool designed for 1 specific job. It's a general purpose tool designed to support almost any addin. So it's requirements have to be minimal. But I don't expect to have to remove 'vi' in order to run Cron, nor any packages for it to DO ITS JOB. rpmbuild is quite different from a general package -- using a specfile, it is very specific to being able to rebuild the binary packages your system came with so you can fix problems or change things (create patches, etc). But if you are not allowed to have, say patch creation software installed when you build things, because patch creation isn't required to build your package, how do you do development? > > How can you not know this, as a over 10 years experienced linux user? --- I know it's guaranteed to be give you minimal testing for an organization who's job is to package all those things together and make them work. What it *sounds* like is that openSuSE is no longer a development / build environment -- that is supported to work to build it's own RPM's. What's the point in having such a development environment if it can't build the packages -- NOT because it has another distro installed, but because it has the distro's packages installed that you are building for. It's a very feeble build system. Does configure require that (not that I know how to write a configure script!) -- but generally, it was hoped it would be runnable on almost any supported system -- from windows, to linux, to BSD to VMS. We aren't just talking 1 flavor of linux, nor are we talking about some artificially stripped build environment -- we are talking about completely different OS's -- that's what gnu has brought to many platforms. Yet a distro vendor goes in complete the opposite direction -- not even supporting builds on their own distro if you have *too many* of it's own packages installed.... You call that Normal? How can you have built anything on linux and not know how alien this is? Cheers! 𝓛𝓲𝓷𝓭𝓪 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 13

[opensuse] Focus, howto
by C. Brouerius van Nidek 22 Jul '12

22 Jul '12

Working on my 12.2 I am confronted with a small nuisance. When I use an URL address in KMail for the download in Chromium I am switch right away to Chromium. I know it has something to do with focus, but where can I change the focus. Did not find it. -- Linux User 183145 using KDE4 on a Pentium IV , powered by openSUSE 12.2 Milestone 2 (i586) Kernel: 3.4.4-1.1-default KDE Development Platform: 4.8.4 (4.8.4) "release 2") 11:28am up 0:11, 3 users, load average: 1.67, 2.16, 1.62 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 4

Re: [opensuse] Monitor back light left on with Nouveau - nVidia drivers
by James Knott 22 Jul '12

22 Jul '12

No idea. I went back to the nVidia drivers. Frankie Onuonga wrote: > Hi, > was this issued sorted out? > > thanks > > On Wed, Jan 11, 2012 at 4:55 PM, James Knott <james.knott(a)rogers.com > <mailto:james.knott@rogers.com>> wrote: > > I have a nVidia video card. While I have used the nVidia drivers > in the past, I recently tried the Noveau drivers to see how they > compare. One thing I have noticed is that the mack light is left > on, when the screen is black. I haven't seen this behaviour with > the original nVidia drivers. Is there any way to fix this, as it > wastes power and shortens the monitor life. > > tnx jk > > -- > To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org > <mailto:opensuse%2Bunsubscribe@opensuse.org> > To contact the owner, e-mail: opensuse+owner(a)opensuse.org > <mailto:opensuse%2Bowner@opensuse.org> > > -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] simpler, praktischer Bildbetrachter für linux?
by Daniel Bauer 21 Jul '12

21 Jul '12

Guten Tag, ich suche ein Programm, das es mir ermöglicht, mehrere Bild-Dateien in je einem eigenen Fenster anzuzeigen. So dass ich die Bilder (mit ihrem Fenster) frei herumschieben, vergrössern, verkleinern kann. Nur das. Gibt es das? Kuickview oder Quickshow oder wie das wunderbare Programm unter KDE3 hiess, gibt es ja leider nicht mehr. Gwenview war bis zur letzten Version einigermassen brauchbar, wenn man von den für mich unnötigen Menüs, Sidebars und sonstigen Win-User-Anbiedereien mal absah. Aber jetzt öffnet Gwenview (super-intelligent!) eine Seite mit lauter kleinen Bildchen, als ob ich das nicht schon im Dolphin oder digikam hätte, von wo aus ich die Bild-Fenster ja öffnen will. Es weigert sich, mehrere Fenster mit je einem Bild aufzumachen. Früher konnte ich dieses dümmliche "ich bin aber der viel geilere Dateimanager, auch wenn ich mich Bildbetrachter nenne"-Getue wenigstens abstellen, in dem ich in /usr/share/applications/kde4/gwenview.desktop in der Zeile Exec=gwenview %U -caption "%c" %i das %U entfernt hatte. Aber das geht der neusten Version von Gwenview schlicht am A... vorbei. Es will jetzt ein Dateimanager sein - und ich will einen Bildbetrachter. Unsere Freundschaft ist somit zu Ende. Kann mir jemand einen Bildbetrachter empfehlen, der ein Bildbetrachter ist? Und sonst nichts? Gibt es das noch unter KDE-Windows? Oder gibt es einen Trick, der aus dem Filemanager Gwenview wieder einen Bildbetrachter macht, der ganz eifach pro Bild ein Fenster aufmacht? ( - Viewnior öffnet ebenfalls nur 1 Fenster, - in Geequie muss ich, nachdem ich ja schon vorher ausgewählt hatte, erneut jedes Bild anwählen und sagen: in neuem Fenster anzeigen - gpicview hat eine manchmal extrem nervig blinkende Icon-Leiste und kann von Bildern in 100% Grösse nur die linke obere Ecke anzeigen ) Ideen? Danke!!! Daniel Opensuse 12.1 Windows, pardon: KDE 4.8.4 -- Daniel Bauer photographer Basel Barcelona professional photography: http://www.daniel-bauer.com personal facebook: http://www.facebook.com/mars.fotografo google+: https://plus.google.com/109534388657020287386 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 3

[opensuse] Re: [opensuse-factory] Re: openSUSE build & testing procedure and faulty pruning of builds causing build failures
by Linda Walsh 21 Jul '12

21 Jul '12

Nelson Marques wrote: >> --- >> Could you point the sources and documentation for the tools >> you use to produce binary & source RPM's, *OTHER* than rpmbuild? ^^^^^^^ (i.e. opensuSE uses to build the source and binary RPM's)... > > There's a lot of them... The Apache OpenOffice for example is > distributed in RPMs --- If opensuse distributes Apache OO, then why are the binary and source RPM's not part of the 12.1 distribution directories? and those are build in an Ubuntu system (the rpm > build host is actually named 'ubuntu-desktop'). People who work with > Ruby have rgem2rpm in rpm; There's tools in > perl and python which can ^^^^ -------------- So far you and at least multiple others didn't answer my question and seem to have an impaired ability to read. I'm not asking what *can* be done. I'm asking what products are built in OpenSuSE NOT using rpmbuild at any point during their build? You mention perl -- if that's a representative example, You build tons of perl packages --- many of which are built using perl make and such... but they are all packaged at the end by rpmlib. > Engineers should know how to do research. If I'm not mistaken rpmbuild > is actually a part of RPM and not of OBS, or is it not? ---- More than research, the ability to read a flow chart is probably more vital. rpmbuild is a separate program from rpm, so no it's not part of rpm, it runs off the rpmlib library. So you are saying that rpmbuild is not used at any point in the OBS process that produces an openSuSE release? I have alot of src rpms that say otherwise. >> I don't think there has ever been any question whether or not >> rpmbuild was used or supported. > > You should address that to RPM upstream, no? --- ??? the RPM project should address whether or not Osuse uses or supports building with rpmbuild? I don't think you are responding to what I am saying. > >> The issue is about what is already installed in your >> build environment. [Open]SuSE, if you remember, rarely used >> BuildRequires before suse10. > > Previous versions of RPM (< 4.10) don't support native LZMA; Are you > going to bash down RPM upstream too because they didn't have > implemented it on the past ? Shame on them. ???? Huh?...Can you describe a situation where you want to build something requiring lzma where it wouldn't be available on the distro sources you are building? > >> Separate "-devel" packages weren't widely used if at all >> sometime before 10 or 9. It was assumed they were included by installing >> the product. > > Keep those also on servers with compilers :) --- You mean where you would be *building products*? > I'm sure a few skilled > persons will love that... Honestly why would a Desktop user or a > Server need development packages, specially when it's RPM managed (be > it yum, zypper or any other)? ---- We are only talking people who use their systems to build or rebuild current packages and whether or not a current system with all the devel packages installed should work or not... If they aren't building, it's a moot point. I'm not suggesting that it is wrong to separate them. But to only be able to generate packages on systems where you don't have specific devel packages installed sounds more than a little arcane. > People who need devel packages know they exist, so if they need them, > install them. If you don't like, Slackware works in a different way, > and they see that as a feature. Move to Slackware. ---- Again, you miss the point. > > You never used RHEL in your life did you! Red Hat has twice the number > of RPMs in 'optinals' (> 6000) repository than you have on the base > distro (~3300). Guess what... the optionals repository is mainly devel > packages from the packages on the distro... So they even do it in a > more complicated. ---- It was the first distro i used in it's 5.0 era, mandrake in the 6.x era, and suse since ~ 6.8 I wanna say, but 7.x for sure... it's been a while, ok? > > Your problem is that you don't know the tools you want to use and you > expect that by an act of a superior entity things will magically > happen... Take my word, it doesn't work like that. Research... basic > stuff for any engineer. ---- You are tilting at strawmen. You are arguing points and claiming things that don't respond to what I wrote. Please try again. I did my research... Just did it again. Nope..no openoffice packages available for 12.1... I think there was in the 11 series... but I see libreoffice, goffice, & koffice. http://download.opensuse.org/distribution/12.1/repo/oss/suse/x86_64/ Don't see the sources for it under the source tree either (http://download.opensuse.org/source/distribution/12.1/repo/oss/suse/src/) > >> For that matter, it used to be that doc packages were usually >> not separate either. > > This might be controversial, but I do tend to agree with the > splitting. On a production server or Desktop most people will never > require the API documentation of the components. While developers do > need that documentation. So the developers should know how to install > the documentation. Not everyone wants useless documentation (for their > tasks) installed by default. It's a feature and it's quite nice. ---- I am not saying those are bad practice, I'm talking about what used to be common practice and expectations. Sterile systems were all but impossible 10 years ago for a distro build. > >> If OSC/OSB is required to build a distro, why is it not >> included in the shipped distro binaries and source rpms? > > [nmarques@gangrena ~]$ osc --version && cat /etc/redhat-release > 0.135 > Red Hat Enterprise Linux Server release 6.3 (Santiago) > > > I don't even have openSUSE installed and I had no problems finding --- I didn't say I couldn't find them, I said why are they not shipped with the distributions they build? Show me the packages under the above URL's where the distro is located. If OBS/osc is required to build openSUSE, then it is part of the required tool chain -- and the words of the license of the GPL were posted on the factory list earlier, saying that the toolset to generate the the build must also be included. Binary distribution (online) has been listed as 'fine'... but it requires you stay in business and the sources STAY on line. It also require knowing what tools you used to build a *given* distribution... (not just the latest copy)... > That's another of the nice things about building in chroot > environments; you won't crash yourself against this kind of issues... --- Unless you are building and installing kernels, you shouldn't be crashing yourself on a build anyway. Installing ?? you get what you install...but when rpmbuilds it does not build in a chroot env... and it has never caused any system corruption or crashes "/var/tmp/BUILDROOT/packagename/" is not a chrooted pathname -- For that matter, I can look in /usr/packages/build/package-version and see the build that was just done. > > Functional Analphabetism is the inability that one has (regardless of > his/hers academical formation) . That you would be familiar with this term is not surprising. Thank you for informing me. I should read up on how to communicate to such people. Interpersonally -- 1:1 I do alot better, but writing 'at a group', seems like there are always people who completely misinterpret what is written -- while others can see it plain as day. Maybe has to do with the differences in how english is taught and learned -- especially in other countries -- and as filtered through their own mental language. I'm sorry if my writing was unclear. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] How to Recover a folder structure from an Ext4 partition that was repaired with fsck
by Kym 21 Jul '12

21 Jul '12

Hello Looking for help on this (): I've got a PC with a 320GB hdd. And this is the partition structure: sda1 - - - /boot - - - (200 MB) - - - Ext4 sda2 - - - swap - - (8 GB) - - - - - Swap sda3 - - - / - - - - - - (20 GB) - - - - Ext4 sda4 - - - /home - - - (270 GB) - - - Ext4 The HOME partition was corrupted. Then I plug the disk in another PC, via USB adapter, and ran: fsck -t ext4 -fy /dev/sdb4 The partition was successfully mounted and all the files were recovered, but they appear in numbered folders, under <lost+found> folder. --> Now my question: Is there any way I could recover the original folder structure? (there are plenty of files, and it is a huge task to re-catalog them in a new structure) Thanks in advance Kyma -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 5

[opensuse] Re: openSUSE build & testing procedure and faulty pruning of builds causing rpmbuild failures
by Linda Walsh 21 Jul '12

21 Jul '12

Greg Freemyer wrote: > openSUSE has moved to a new build paradigm and you are complaining the > old one no longer works and you can't use it to build the distro > pieces. --- I am complaining that one cannot use a standard suse distro machine to do a build of the source packages anymore. It's not about new and old. I get new versions of compiler make, even samba uses a python tool instead of configure/make for samba4, but it still builds on my local OpenSuSE12.1 system. The source packages from OBS are not robust. It is NOT that they don't have requirements listed -- they do -- but they are requiring something that the rpm build system never provisioned for... They are requiring you NOT to have various packages installed *during the build*, because the build can pick up extra available tools to build more support or to optimize the build. Instead of building packages as they would be build by an installed distro, they are building some arbitrary subset that isn't built to work with the entire distro they ship. If that's the case, they should stop shipping those extra packages and sources and stop pretending that this giant collection of RPMs is all one compatible distribution. It's more important, TO ME, to have a distribution that works together that I can use to rebuild itself, than to have "bigger numbers" of packages that I can't really use (but don't know it) because if I do, builds will go awry. > I think this thread (series of threads) have made is clear the core > set of openSUSE maintianers simply don't care if the old legacy way > still works or not. ----------- Several people have mentioned to me that they and others who no longer post have given up on trying to get their opinions heard, but that they appreciate my efforts, as it bespeaks to many of the issues they brought up, attempted to have addressed, and had ignored. > openSUSE has invested great effort into obs and they are properly > proud of it. I think OBS is one of the crown jewels of opensuse. --- Of that I have think no one disagrees -- and that's part of the problem. If you had such a nice new toy... and someone didn't want to use it, how well would you respond? I didn't even ask them *NOT* to use it -- I asked them to change their 'base system', from a "minimum necessary" (which will NEVER represent what users have on their machines), to a full development install, which should catch 90% of the interactions between packages during build that can happen to customers -- and allow them to be fixed before they hit the customer. I know this upsets the 'train schedule' theory of product release, but sorry, you can't schedule creative efforts like building machines. Each release is something that has NEVER been done before. It's never been tried -- never been put together "exactly this way" -- to expect that you can predict how long that is going to take reliable is foolish, wishful thinking. How can you predict how long that which has never been done before? One way is to eliminate all complexity and as many unknowns as possible. You can do this by NOT creating a distro, but by building a collection of packages in isolation from each other -- that when run in a particular way (like a script), will give a more specific result. But no longer do you have a distribution that's integrated and designed to work together -- but a collection of packages designed to be run and generated in only certain predictable ways. That's not a personal computer -- that's an appliance. What people are talking about is shifting SuSE from a linux-distro builder to a linux-appliance builder (or a platform for building linux appliances). That would indicate that openSuSE is removing themselves from the linux distro market, and going for a niche subset market, while still telling people they are a linux distro. I wanna know -- when was the decision made to shift away from being a linux distro and become an appliance-OS vendor? Was this made clear to everyone working with opensuse? I didn't realize it until this set of emails, that this was the most likely reason, behind the scenes, for this to occur.... but it makes sense with other projects open Suse has gotten into. I could say more, but I want to address your other points... > The normal way from my perspective to build a package is to checkout a > local copy of the package from OBS and use "osc build" to build it. > > You've argued that since that interacts with OBS it isn't satisfactory. --- No... checking it out from OBS -- let me use svs/cvs/mercurial/git... whatever, osc hasn't worked for me yet. Tried yesturday to install more of those packages and they failed due to the server being down/unreachable. 2012-07-19 14:17:50 <2> Ishtar(2980) [YCP] PackageCallbacks.ycp:2075 Download failed: error 4: File './x86_64/obs-server-2.3.3-5.1.x86_64.rpm' not found on medium 'http://download.opensuse.org/repositories/openSUSE:/Tools/openSUSE_12.1/' 2012-07-19 14:19:48 <2> Ishtar(2980) [YCP] PackageCallbacks.ycp:2075 Download failed: error 4: File './x86_64/obs-api-2.3.3-5.1.x86_64.rpm' not found on medium 'http://download.opensuse.org/repositories/openSUSE:/Tools/openSUSE_12.1/' 2012-07-19 14:23:05 <1> Ishtar(2980) [YCP] PackagesUI.ycp:494 Installation summary: Package Installation Failed * Error Message: Packages * Failed Packages: 2 obs-api, obs-server * Installed Packages: 93 MozillaThunderbird, apache2-mod_xforward, augeas, dbus-1-glib-doc, deltarpm, enblend-enfuse, flash-player-gnome, flash-player-kde4... (more) <installed_packages> * Removed Packages: 1 esound-daemon Statistics * Elapsed Time: 03:04 * Total Installed Size: 152.38 MB * Total Downloaded Size: 4.89 MB Details * Installation log <install_log> * Post-Installation log (SUSEconfig) <postinstall_log> Note -- despite my posts here, I am still trying to make progress on multiple fronts, -- including installing the recommended osc packages, which, as you can tell from yesterday's summary, failed. > > It is untested for me but working with a source tarball this should > work in isolation from OBS. > > mkdir ~/osc > mkdir ~/osc/my_local_projects > cd ~/osc/my_local_projects > osc importsrcpkg <source rpm> --local-package > cd <package> > osc build --local-package I read in the manpage that the above says it builds locally. So how about it giving the option of producing a shell script that can be run -- since, the above looks like you are running the "local build" through a remote osc session -- will this work when you are not connected online (for example)? (or if osc is down? or you have no working osc connection?) > > I do have confidence that if you drop the --local-package options and > assuming you have your OBS account initialized (by logging into OBS > one time) and you have internet access then something like the above > will work except it is more like: The idea of a local build is so that once you have the sources downloaded, you don't have to be on the internet. > You may not like the new workflow, but to argue openSUSE has lost the > ability to build packages locally is simply false. It is just that > opensuse has moved to a new paradigm and you are still using the old > one. The new system uses rpmbuild as well, I'm told -- So what directory do I 'cd' to and run my rpmbuild command? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 2