Re: [opensuse-factory] Quesiton on java pattern
On Thu, Jan 24, 2008 at 01:12:13PM +0100, Stephan Kulow wrote: > Am Donnerstag 24 Januar 2008 schrieb Joerg Mayer: > > I'm getting the following message: > > > > Problem: pattern:non_oss_java-11.0-14.i586 requires > > java-1_5_0-sun-plugin, but none of the providers can be installed > > Solution 1: deinstallation of > > java-1_6_0-sun-plugin-1.6.0.u3-20.i586 > > Solution 2: do not install pattern:non_oss_java-11.0-14.i586 > > > > Is there a reason why the java pattern requires the 1.5.0 version? > > I'm > > running the 1.6.0 version and haven't encountedred any problems so > > far. > > Because it also requirs java_1_5_0. I'm not java expert enough to say > if switching to 1_6_0 as default. I switched to 1.6 almost completely and it seems to work fine so far: [EMAIL PROTECTED]:~> rpm -qa | grep java java-1_6_0-sun-plugin-1.6.0.u3-20 java-1_6_0-sun-1.6.0.u3-20 java-1_5_0-gcj-compat-1.5.0.0-20 java-1_6_0-sun-devel-1.6.0.u3-20 [EMAIL PROTECTED]:~> -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] Quesiton on java pattern
I'm getting the following message: Problem: pattern:non_oss_java-11.0-14.i586 requires java-1_5_0-sun-plugin, but none of the providers can be installed Solution 1: deinstallation of java-1_6_0-sun-plugin-1.6.0.u3-20.i586 Solution 2: do not install pattern:non_oss_java-11.0-14.i586 Is there a reason why the java pattern requires the 1.5.0 version? I'm running the 1.6.0 version and haven't encountedred any problems so far. ciao Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] 3 more interesting behaviours
The following was just copied from a console: egg:~ # zypper dup * Lese Cache fÌr Repository 'factory' * Lese Cache fÌr Repository 'factory-non-oss' * Lese installierte Pakete [100%] 2 Probleme: Problem: nothing provides package needed by gmime-sharp-2.2.11-20.i586 Problem: nothing provides libgcrypt11 = 1.4.0 needed by libgcrypt-devel-1.4.0-2.i586 Problem: nothing provides package needed by gmime-sharp-2.2.11-20.i586 Lösung 1: gmime-sharp-2.2.11-20.i586 nicht installieren Choose the number, (s)kip, (r)etry or (c)ancel> 1 Wende Lösung 1 an Problem: nothing provides libgcrypt11 = 1.4.0 needed by libgcrypt-devel-1.4.0-2.i586 Lösung 1: libgcrypt-devel-1.4.0-2.i586 nicht installieren Choose the number, (s)kip, (r)etry or (c)ancel> 1 Wende Lösung 1 an AbhÀngigkeiten werden aufgelöst... Die folgende Auswahl von Paket wird downgegraded: dhcpv6 This indicates 3 behaviours that I can't explain: 1) Why are the messages in German? (well, OK, that's something nobody but me is likely to be able to explain - I just haven't found out how I messed this up ;-) 2) Inconsistent packages in factory 3) dhcpv6 gets "downgraded" each and every time to the same version (dhcpv6-1.0.4-3.i586). ciao Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] Problem updating splashy
During updating splashy I received an error that /etc/splashy/themes/ was a directory. What happened was, that /etc/splashy/themes/ was moved to another place and there is now a link pointing to the new place. The link couldn't be created because the old directory was still there. I'm not sure whether that's to be considered a bug in splashy or in rpm. If it's a splashy bug then there should be a preinst script that removes that directory if present. In case that's considered an rpm bug then rpm must learn how to overwrite not just files but any object type by any other object type. ciao Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Problems with current factory
On Fri, Jan 18, 2008 at 07:17:15PM +0100, Felix M?ller wrote: > >>> download subversion-1.5.0-29.(i586 | x86_64).rpm (yes, it's the same > >>> build number as your installed package!) and install it with rpm -U > >>> --force. > > That's _not_ a joke. The package in factory has the same build number as > > the > > installed one, so factory update doesn't install the current one. But the > > date of the build in factory is newer. Guess, buildnumber wasn't > > incremented > > as the package was built against glibc 2.7. > thanks alot this does indeed fix the issue. Mine is solved too. Now I'll only have to look into the apache2 problem. Thanks! Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] Problems with current factory
- apache2 crashes on many (trivial) requests - subversion client can't access archives via ssh and https any more (or, to be more precise: all files appear with ! in svn status). Is any of that known or should I invenstigate further and open bugs? Ciao Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Please update vpnc
On Fri, Jan 18, 2008 at 10:56:51AM +0100, Lars M?ller wrote: > On Fri, Jan 18, 2008 at 07:23:03AM +0100, Joerg Mayer wrote: > > > > OK, I found one thing: As openSUSE contains GPL packets that link > > against openssl (e.g. Wireshark), please enable hybrid support in > > the Makefile: > > Currently there is no BuildRequires to the openssl-devel package. > Therefore I consider the OpenSSL license as no risk to the one of vpnc. Yes, but what I'm currently doing is requesting that you change that :-) Ciao Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Please update vpnc
On Thu, Jan 17, 2008 at 01:36:45PM +0100, Joerg Mayer wrote: > By default vpnc installs vpnc-script into /etc/vpnc/. It's been debated > on the list whether that's the right place and as far as I'm concerned > there is no "right" place, so we chose the "least wrong" one. Ideas are > always welcome. I'll have a look at the binary and source rpm tonight > if time permits. OK, I found one thing: As openSUSE contains GPL packets that link against openssl (e.g. Wireshark), please enable hybrid support in the Makefile: # The license of vpnc (Gpl >= 2) is quite likely incompatible with the # openssl license. Openssl is currently used to provide certificate # support for vpnc (hybrid only). # While it is OK for users to build their own binaries linking in openssl # with vpnc and even providing dynamically linked binaries it is probably # not OK to provide the binaries inside a distribution. # See http://www.gnome.org/~markmc/openssl-and-the-gpl.html for further # details. # Some distributions like Suse and Fedora seem to think otherwise. # Comment this in to obtain a binary with certificate support which is # GPL incompliant though. #OPENSSL_GPL_VIOLATION = -DOPENSSL_GPL_VIOLATION #OPENSSLLIBS = -lcrypto ciao Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] beagle
On Thu, Jan 17, 2008 at 09:11:00PM +, peter nikolic wrote: > On Thursday 17 January 2008, Christian Jäger wrote: > > It is perfectly normal that an indexing tool is especially active when > > building an initial index. Whoever doesn't have the patience to wait > Beagle should be an OPTION not a preset thing . > > I would think very few people using Opensuse on the desktop either at work or > at home do not need Beagle and prefere a faster more responsive machine to > one that is faffing around building an unwanted index of some form , As for > Mac users nuff said . My gripes with beagle are just two: 1) It tends to use quite a lot of disk space (at least during its initial run) even it the disk is almost full, resulting in 100% disk usage. 2) It runs even when my laptop is running on battery shortening battery life. I don't think that either point is something that most users have problems with/care about so my solution to my problems was: I removed all beagle packages from my system and added *beagle* to /etc/zypper/locks. I'm running factory. Ciao Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Please update vpnc
On Thu, Jan 17, 2008 at 10:26:11AM +0100, Felix M?ller wrote: > As the servers are back online I did an update again and now have: > # rpm -q vpnc > vpnc-0.5.1-2 > > But now I get: > # vpnc > usage: modify_resolvconf > action: modify, restore, cleanup or check > options: mandatory for: > -s|--servicemodify, restore > -e|--extension > -p|--processmodify > -i|--pid > -f|--script modify > -t|--text modify > -l|--searchlist > -d|--domain > -n|--nameservers > -o|--save_now > -a|--save_later > -k|--keep >--resolv >--named >--no_restart > -q|--quiet > -v|--verbose > -h|--help(does not need an action) > cleanup and check ignore all options except -q and -v > > ERROR: there is no script named /usr/local/sbin/vpnc > > VPNC started in background (pid: 4938)... > > Looking into it I think there is still a small packaging bug: > # cat -n /etc/vpnc/vpnc-script > ... > 59 DEFAULT_ROUTE_FILE=/var/run/vpnc/defaultroute > 60 RESOLV_CONF_BACKUP=/var/run/vpnc/resolv.conf-backup > 61 FULL_SCRIPTNAME=/usr/local/sbin/vpnc > 62 SCRIPTNAME=`basename $FULL_SCRIPTNAME` > ... > > I had to change the FULL_SCRIPTNAME=/usr/local/sbin/vpnc to /usr/sbin/vpnc. > > As I am just a user of vpnc I am sure whether this is correct. Joerg can > you comment? By default vpnc installs vpnc-script into /etc/vpnc/. It's been debated on the list whether that's the right place and as far as I'm concerned there is no "right" place, so we chose the "least wrong" one. Ideas are always welcome. I'll have a look at the binary and source rpm tonight if time permits. Ciao Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] a checkin timeout before an Alpha release?
On Tue, Jan 15, 2008 at 06:27:04PM +0100, Dirk Mueller wrote:
> > > I don't think that factory testing is the issue.
> > I don't follow your point, even with packages failing factory helps you
> > test and determine ahead of time how good an alpha would be.
>
> Sure, my point is that the testing such a snapshot is not very meaningful
> because it is just one arbitrary state during a rapidly changing time period.
>
> Also, as you know, factory syncing to the outside is staged ("slowed down")
> to
> not stress mirrors even more. It IMHO makes more sense to take care of
> failing packages to ensure a consistent state for Alpha1 than testing one
> arbitrary snapshot in time that can not be recreated. But it's your time
> after all :)
I fully agree here: I don't expect everthing in an alpha to work, but I
expect the alpha to be *consistent* at the rpm layer: A big don't should
be that there are still packages that are suse 10.3.1. If they don't build,
then remove them or fix them but don't let them be part of a release. The
same is true for packages that no longer have their dependencies
fulfilled (e.g. pdftk requires a lib that has been replaced by a newer
version). Again: Remove those packages or fix them, but don't ship them.
If you really want to ship a system with inconsistent dependencies then
please call it snapshot and not (alpha) release. A missing package is much
better than a package with missing dependencies.
Calling something an (alpha/beta) release should have a defined set of
criteria that it *must* fulfill and I'd like to see these criteria
defined somewhere. One criteria that comes to my mind for all types of
releases is that it must be possible to rebuild all the packages that
said release comprises of by using only packages from that release.
ciao
Joerg
--
Joerg Mayer <[EMAIL PROTECTED]>
We are stuck with technology when what we really want is just stuff that
works. Some say that should read Microsoft instead of technology.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] a checkin timeout before an Alpha release?
On Tue, Jan 15, 2008 at 07:24:14AM -0500, Toni Harbaugh-Blackford wrote: > Would it be possible to have a 'new version' checkin timeout before > an alpha release of the Factory? It seams that there are too many new > checkins that break Factory lately. It would be nice if there were a > short > window before an alpha release where only bug fixes were checked in. > > I realize that the point of Factory is to keep current with the latest > software, but a short period of stabilization before a release does not > sound unreasonable to me Hmm, maybe it's too early for a new alpha? With some packages broken since the update to gcc43 (like pdftk, compiling mplayer) it might be a good idea to get at least the distro to compile completely again before an alpha? (ok, mplayer isn't part of the distro, it's just dear to me :-) So maybe sync out a gcc update that fixes these issues and get everything to compile again before a new alpha? ciao Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] Please update vpnc
Can vpnc please be updated from 0.3.x to 0.5.x? The current version has support for hybrid authentication (still no full blown certificate support though). Kvpnc already supports the new vpnc version. ciao Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Splitting manpages out of package is *fundamentally* wrong
On Thu, Jan 03, 2008 at 04:00:31PM +0100, Michael Schroeder wrote: > But we don't need passivetex to generate man pages, so can't we > just block the xmlto->passivetex dependency, i.e. add > > #!BuildIgnore: passivetex > > to the spec file? That would be an approache that would be much more to my liking than the approach taken now. Ciao Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Splitting manpages out of package is *fundamentally* wrong
On Mon, Dec 31, 2007 at 12:08:40PM -0600, Rajko M. wrote: > > P.S. not one of these tools comes with an on board manual, that is what > > training and research are for. > > That's the right point James. No, it isn't. Because the amount of training and *research* that is needed to use an OS should be minimal. While using the accelerator etc is basic training, trying to use the radio, navigation or speed regulation isn't intuitive and requires the manual. The same with a computer: You need to learn how to start/login to a system and use it (graphically, command line, voice, mental control). You shouldn't need training or research for all the tools individually. See below why manpages are not comparable to manuals. They normally don't explain the backgroundknowledge, just the features of the tool itself. > It is time to rethink about tradition to have manuals as a part of package. Absolutely not. It seems you have some interesting notion of Unixish systems. To make this a bit more understandable: That's just like putting the online help in graphical applications into their own package. Manpages are the online help of command line applications. Also, they tend to be tiny when compared with the rest of the package. > I need manuals to learn how to use tools (I missed many lectures), but I know > that I use very small portion of installed software. The rest is used by > other guys in my "shop", those that created scripts, and they don't need > manuals. Only very very few people - if any - know the meaning of all the command line options of all the tools they *use*. They use a combination of manpages and --help instead. > So, what would be the best option if I want to have small, slick collection of > software, but manuals available if want them. I guess separate collection of > manuals, and package manager that will install them on request. And the day Suse does this, I will switch distribution because the mentality of the distribution no longer matches mine. So far one of the big strengths of Suse was that it is equally usable for newbies, users and powerusers. Ciao Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Splitting manpages out of package is *fundamentally* wrong
On Sun, Dec 30, 2007 at 03:12:33PM -0500, Andrew Joakimsen wrote: > On Dec 30, 2007 1:31 PM, Joerg Mayer <[EMAIL PROTECTED]> wrote: > > We are talking about 6 KBytes of manpages, not 640 KBytes of complete > > documentation. What use is it to have the programs if they are unusable > > due to missing manpages? > > The program still works without the manpage present. How does it make > it "unusable" The unix philosophy is to have many small tools that bring a minimal documentation (and in most cases the complete documentation) with them. Your comparison is comparing apples with oranges btw: a) a car doesn't have several hundred small "tools" b) while the basic tools normally don't need documentation, trying to use one of the rarely used or more complex features without documentation either fails or takes much more time then necessary or leaves many features unused (think of speed control, navigation, radio). Ciao Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Splitting manpages out of package is *fundamentally* wrong
On Sun, Dec 30, 2007 at 03:26:57PM +0100, Stephan Kulow wrote: > This has nothing to do with that. The reason the docs are split out is that > PolicyKit is a pretty basic package required by many other packages for > building. And if such a basic package requires texlive to build, we have to > wait even longer before we can push out a new Factory snapshot. > So we split these basic packages with big build dependencies into two source > rpms. Sure, but then - that's life. But if you think it that essential/unstable - maybe the manpages should be created differently? > This does not stop anyone from adding a Recommend or even a Require > to the base package - I would suggest a Recommend, because the man page is > still only nice to have for people not wanting to use Policykit. I strongly disagree: It's the wrong thing to do: The manpages need to be packaged with the application. And if that can't be done, then see the comment above. Removing the manpages is really really wrong (I may have said that already but that's how I feel :-) and removing them from the base package due to *build* reasons is no excuse - really: a) the texlive should not be broken over longer periods of time anyway. b) maybe adding pregenerated manpages to the source package would be an acceptable solution to the problem, so a broken tex package could be worked around in the build process by copying the pregenerated stuff. > So just file a bug report. To what extent? That the need to be added back or that a require/recommend should be added - and if the latter one: where? ciao Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Splitting manpages out of package is *fundamentally* wrong
On Sun, Dec 30, 2007 at 10:30:50AM -0500, James Tremblay wrote: > I think the reason for a 128 base package request might have something > to do with KIWI, > in order to support a Wyse terminal with the best local video,sound and > app support is to have a network independent "thin client" it can > boot,run an x session and possibly even authenticate the local root for > updating and tweaking. therefor removing documentation from these "base" > packages would be essential. We are talking about 6 KBytes of manpages, not 640 KBytes of complete documentation. What use is it to have the programs if they are unusable due to missing manpages? Ciao Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Splitting manpages out of package is *fundamentally* wrong
On Thu, Dec 27, 2007 at 08:43:29PM -0600, Rajko M. wrote: > I can understand that, as I am heavy user of man pages, but there was a > pressure to make distro smaller. What was behind wasn't explained, but the > goal was set to 128 MB for the very base system and AJ email appeared to be > very serious. We are talking about <7kBytes here. The comment also indicates that it was done for build purposes. Again, the doc package is about 640kBytes in size - it's OK to split off most of it - but not the manpages. > BTW, for guys that know how to use man pages installation of extra package is > a bit more work, but far from a problem ;-) That's a different topic - also that PolicyKit-doc is missing from the standard selection is a different topic - what this thread is about is a thing that is just something I really want to prevent in the beginning. Ciao Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Splitting manpages out of package is *fundamentally* wrong
On Thu, Dec 27, 2007 at 06:29:36PM -0600, Rajko M. wrote: > > While it may in may cases be OK to not include additional documentation > > in the base package, the manpages need to stay there - no matter what > > that means for the build process. > So far I recall there was idea to remove documents from main package, to make > base package and whole base distro slimmer, easier to put on CD, Live CD etc. > The above excerpt is something new to me. Removing manpages is a broken concept: They are needed to actually use the programs. Additional documentation may well be moved into another package, but not manpages. That's similar to removing the --help part from the binaries to make them smaller. Ciao Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Splitting manpages out of package is *fundamentally* wrong
On Thu, Dec 27, 2007 at 01:46:47PM +0100, jdd wrote: > >>>>* Sat Aug 11 2007 [EMAIL PROTECTED] > >>>>- Make separate spec file for PolicyKit-doc so that PolicyKit does > >>>> not require TeX for building. > >>>This is because TeX stuff is **huge**. > >>and use of TeX for man pages is incredible... > > > >They use DocBook, wich pulls in deps: > > xmlto -> passivetex -> xmltex -> texlive > > > >The use of DocBook is very common and far from "incredible". > > > why not give the text and info package in the rpm, along with the > docbook source. following such deps IS incredible... Just to clarify my remarks as it seems some people may have misunderstood them: All I'm asking for is to include the proper manpages in the "base" package. If building that manpage takes a huge toolchain then either live with it or change the sourceformat of the manpage to something that doesn't require using such a big toolchain. Splitting the manpage out of the package is only valid in very rare cases - and this isn't one of them. Ciao Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] Splitting manpages out of package is *fundamentally* wrong
Hi, I'd just discuss something that I got hit with: The PolicyKit package no longer contains the manpages - if you want them you need to install PolicyKit-doc as well. IMO, this is a *relly* *really* ... *really* wrong decision, which was obviously made because of *build* reasons: * Sat Aug 11 2007 [EMAIL PROTECTED] - Make separate spec file for PolicyKit-doc so that PolicyKit does not require TeX for building. While it may in may cases be OK to not include additional documentation in the base package, the manpages need to stay there - no matter what that means for the build process. ciao Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] Misleading zypper error message
Hello, A recent zypper dup removed the gpg2 package from my system (I have no idea why). When I later tried to update again I ended up with the following error: Checking whether to refresh metadata for factory Downloading: http://download.opensuse.org/distribution/SL-OSS-factory/inst-source/content * Downloading [100%] Downloading: http://download.opensuse.org/distribution/SL-OSS-factory/inst-source/media.1/media * Downloading [100%] Refreshing 'factory' Downloading: http://download.opensuse.org/distribution/SL-OSS-factory/inst-source/content * Downloading [100%] Downloading: http://download.opensuse.org/distribution/SL-OSS-factory/inst-source/media.1/media * Downloading [100%] Downloading: http://download.opensuse.org/distribution/SL-OSS-factory/inst-source/media.1/media * Downloading [100%] Downloading: http://download.opensuse.org/distribution/SL-OSS-factory/inst-source/content.asc * Downloading [100%] Downloading: http://download.opensuse.org/distribution/SL-OSS-factory/inst-source/content.key * Downloading [100%] Repository 'factory' is invalid. History: - File /var/cache/zypp/raw/factory4ezyR3/content.key doesn't contain public key data - Valid metadata not found at specified URL(s) Please, check if the URLs defined for this repository are pointing to a valid repository. Skipping repository 'factory' because of the above error. The error message isn't really helpful. Should I open a bug requesting a less misleading error message like "gpg not found - couldn't verify key"? ciao Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Some remarks and questions regarding current factory
On Tue, Dec 18, 2007 at 09:54:35AM +0100, Klaus Kaempf wrote: > A bugreport is likely to be closed as wontfix. > > See http://en.opensuse.org/Software_Management/Upgrade/Devs_Rpm > on the traps and pitfalls of getting rid of devs.rpm. Well, it isn't really relevant as the removal went fine, but the update itself was already done and worked fine, it was just that the devs.rpm was still around but udev was being used. Ciao Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Some remarks and questions regarding current factory
On Tue, Dec 18, 2007 at 09:47:06AM +0100, Michal Marek wrote: > >> Udev takes care of creating the device nodes, devs.rpm was finally > >> dropped after 10.3. Some other rpm should probably obsolete it > > > > So what will happen if I "rpm -e devs"? Will my system still work? > > Hmm, good question. I'm afraid that rpm -e devs will remove the device > nodes from /dev (even though the ones really owned by devs.rpm are > hidden by the tmpfs mount on /dev). Try it and report a bug if you run > into trouble ;-). You can tar up /dev before to avoid a reboot if > something goes wrong. OK, I removed the package and rebooted the system after that (I needed to update the kernel anyway). Now all is fine. Thanks! Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Some remarks and questions regarding current factory
On Mon, Dec 17, 2007 at 05:05:52PM +0100, Michal Marek wrote: > Joerg Mayer wrote: > > devs openSUSE 10.2 (i586) <--- what happended to this package? > > Udev takes care of creating the device nodes, devs.rpm was finally > dropped after 10.3. Some other rpm should probably obsolete it So what will happen if I "rpm -e devs"? Will my system still work? > > - OpenOffice crashes on all powerpoints that I try to open. > > Is it the same as https://bugzilla.novell.com/show_bug.cgi?id=349216 ? Looks like it - I just added a small comment to that bug. In the meantime I found an autoconf bug that prevents me from building wireshark (opened bugid #349249). Ciao Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] Some remarks and questions regarding current factory
Hello,
when updating my 10.2 system to factory using "zypper dup" I noticed a
few things:
- Most things worked very nice!
- Some packages are still named 10.3.1 instead of 11.0 and the devs
package is still in the 10.2 version.
rpm -qa --qf '%{NAME} %{DISTRIBUTION}\n' | grep -v "openSUSE 11.0"
libmusicbrainz4 openSUSE 10.3.1 (i586)
perl-DBD-SQLite openSUSE 10.3.1 (i586)
ocrad openSUSE 10.3.1 (i586)
kdevelop3 openSUSE 10.3.1 (i586)
yast2-schema openSUSE 10.3.1 (i586)
libqtpod openSUSE 10.3.1 (i586)
pdftk openSUSE 10.3.1 (i586)
devs openSUSE 10.2 (i586) <--- what happended to this package?
- OpenOffice crashes on all powerpoints that I try to open.
The most recent "zypper dup" generated the following messages:
Package ghostscript-fonts-other-8.60-13 fails integrity check.
Package libgcj43-jar-4.3.0_20071129-6 fails integrity check.
Package x11-input-wacom-0.7.8-60 fails integrity check.
Package xen-doc-html-3.1.0_15042-77 fails integrity check.
Package xen-doc-pdf-3.1.0_15042-77 fails integrity check.
Package xorg-x11-libX11-ccache-7.3-25 fails integrity check.
And the question I have regading zypper:
Currently "zypper dup" restores rpms that I deleted (like wireshark,
*beagle*). Is there a way to prevent that?
Thanks
Joerg
--
Joerg Mayer <[EMAIL PROTECTED]>
We are stuck with technology when what we really want is just stuff that
works. Some say that should read Microsoft instead of technology.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] Factory not prominently enough featured on opensuse.org?
Just a comment from Mr. LWN
> Said grumpy editor has actively looked for an opensuse development
> distribution a few times, with no luck. The folks who create
> opensuse.org don't make the factory distribution easy to find - the
> "latest development version" link does not go anywhere near it. I
> suspect I'm not the only one who has come up empty-handed in this
> search. Nonetheless, I clearly blew my research and apologize for any
> resulting confusion.
why he stated that there was no publicly available development version
of openSUSE available.
It's true that it is not that easy to find: When I went to opensuse.org,
download, then the link "latest development version" points to 10.3RC1
A prominent link to factory might help to prevent this from happening
too often? Maybe there are some other places where links to factory
might be added (but I think it is properly referenced at the main
wiki page).
Ciao
Joerg
PS: The article on lwn.net will become available in a week for
non-subscribers (The Grumpy Editor's guide to (some) development
distributions). Apart from that goof, the article was a nice read.
PPS: Googling for: opensuse development version
showed the (good) development version page and the ("bad") download
page as its first two hits in that order
--
Joerg Mayer <[EMAIL PROTECTED]>
We are stuck with technology when what we really want is just stuff that
works. Some say that should read Microsoft instead of technology.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] Problem with zypper
Hello, I've got a problem with zypper (opensuse 10.2). Why does it say that OpenOffice_org 2.2.1-43.1 is up-to-date, when the installed version is 2.2-9.1? Thanks Joerg egg:/etc/vpnc # zypper info OpenOffice_org [...] Information for package OpenOffice_org: Catalog: 20070822-203420 Name: OpenOffice_org Version: 2.2.1-43.1 Arch: i586 Installed: Yes Status: up-to-date Installed Size: 353.8 M Summary: A Free Office Suite (Language-Independent Part) Description: A comprehensive office package featuring a word processor, a spreadsheet, a presentation program, and much more. egg:/etc/vpnc # rpm -q OpenOffice_org OpenOffice_org-2.2-9.1 egg:/etc/vpnc # rpm -qi zypper Name: zypper Relocations: /usr Version : 0.6.15Vendor: SUSE LINUX Products GmbH, Nuernberg, Germany Release : 0.2 Build Date: Thu Aug 2 19:31:49 2007 Install Date: Sun Aug 19 10:19:27 2007 Build Host: crumb.suse.de Group : System/Packages Source RPM: zypper-0.6.15-0.2.src.rpm -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] Debugsymbols for repositories
Hello, I'm in need of the debug symbols for the rpm /pub/opensuse/repositories/xorg73/openSUSE_10.2/xorg-x11-server-7.2-255.3.src.rpm Is ther ea place or do I have to rebuild the package from source? Thanks Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] [suggestion] YaST-update should NOT refresh all installation-sources when called by opensuse-updater
On Sun, Apr 22, 2007 at 11:16:12AM +1000, Horst G?nther Burkhardt III wrote: > > Uhhm, you're talking about downloading the updates/repodata/*.xml.gz > > files? For the 10.2 updates that's about 13MB currently. I'd be very > > interested to hear how you download that over a dialup at a realistic > > 3kbyte/s in "a few seconds tops". > Well, Herr Kuhlmann, have you ever considered that the average dialup user > wouldn't be stupid enough to try applying remote updates over his link? > Unless he was incredibly desperate not to have his Apache server hacked XD > > Almost ALL computers these days have a broadband connection of some form. > Yes, I'm not proud that I used a 33.6k modem up until January 19 2006, but > one of the first things i did on my broadband link was download a new > distro (i'd been using Fedora Core 4, and as you can imagine it > traumatised me for life.) - There's just NO excuse to use a dial-in > narrowband data link for anything more than ssh these days. Cheap and > plentiful data pipes are available in every developed country of the world > - EMBRACE THEM! :D > > by the by, 13MB on my cable modem? it's demolished in one minute. Hmm, apart from being rather arrogant this answer is also excessivly ingorant of security matters because, what is says boils down to "if you are sitting behind a small bandwidth connection (GPRS, modem, ISDN, UMTS) it's OK to connect to the internet but don't download (security) patches." It also fails to take into account users that have to pay for the volume that they use. While it may well be worthwile to download (and pay for the volume) the delta-rpms to have a properly secured Suse the question is: Why should I pay multiple times that volume just to know that my system needs/doesn't need patches. I think it is good practice to check for patches once per day and when comparing the download volume to the checking overhead, the current situation looks bad. In my case, I have a limit of 100 MB per month, after that the megabytes become rather expensive. If I'm on business trips for two weeks, then I'll use up almost all of that volume just to do the checks for updates. Not a very nice solution. ciao Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Games on openSUSE 10.2 (forw)
Forgot to hit the right reply button again...
- Forwarded message from Joerg Mayer <[EMAIL PROTECTED]> -
Date: Wed, 6 Sep 2006 11:09:10 +0200
From: Joerg Mayer <[EMAIL PROTECTED]>
To: Silviu Marin-Caea <[EMAIL PROTECTED]>
Subject: Re: [opensuse-factory] Games on openSUSE 10.2
In-Reply-To: <[EMAIL PROTECTED]>
On Wed, Sep 06, 2006 at 11:53:12AM +0300, Silviu Marin-Caea wrote:
> We need games. They're the ultimate argument for converting Jane and Joe to
> Linux ("see, you have Solitaire and a whole bunch more").
>
> I'd suggest:
>
> kdegames (board, puzzle, whatever there is)
> frozen-bubble
> xmoto
> chromium
> lbreakout
> penguins (the lemmings clone)
> some invaders or galaga clone that looks modern. Too bad there's no Chicken
> Invaders for Linux.
don't forget pysol. It seems it was dropped for 10.1
ciao
Joerg
--
Joerg Mayer <[EMAIL PROTECTED]>
We are stuck with technology when what we really want is just stuff that
works. Some say that should read Microsoft instead of technology.
- End forwarded message -
--
Joerg Mayer <[EMAIL PROTECTED]>
We are stuck with technology when what we really want is just stuff that
works. Some say that should read Microsoft instead of technology.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] CDRTools (CDDL / GPL)
On Tue, Sep 05, 2006 at 03:22:16PM +0200, Dominique Leuenberger wrote:
> will openSUSE replace the cdrtools (which are now under the GPL
> incompatible CDDL license) by the new cdrkit, which is a fork of the
> latest GPL'd cdrtools?
There's at least one person on this planet who thinks that it isn't
incompatible ;-)
ciao
Joerg
--
Joerg Mayer <[EMAIL PROTECTED]>
We are stuck with technology when what we really want is just stuff that
works. Some say that should read Microsoft instead of technology.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] openSUSE 10.2 Features and Roadmap
On Wed, Aug 30, 2006 at 08:40:59PM +0200, Jiri Benc wrote: > d80211 (aka DeviceScape stack) isn't stable yet. There are known locking > problems (see f.e. http://www.spinics.net/lists/netdev/msg13279.html), > d80211 is known not to work with NetworkManager yet, user space tools > for advanced features of d80211 need to be written. > > We definitely won't have all of this fixed in time for 2.6.18. Do you really mean 2.6.18 or 2.6.19? And while neither NM nor advanced features may be ready in time for the 10.2 release, even the basic functionality will quite likely be very welcome when compared to shipping a 10.2 without any support for these cards. > > Some driver developers therefore perfer to use the DeviceScape stack. > > There is a general consensus that new wireless drivers should use > d80211. ... unless the card has very much intelligence inside: it doesn't look like the current ipw2100 and ipw2200 can be ported with a reasonable amount of work to the devicescape stack - the ipw3945 has already been ported by Intel (still waiting for the release). > > Other drivers (like madwifi) even use their > > own stack implementation. The inhomogeneity of the wireless LAN drivers > > is a major drawback for us, but unfortunately it does not look like it > > will get better until we have a full featured ieee80211 stack in the > > mainline kernel every WLAN driver developer can live with. I've been following the developemnt of the wireless stack for quite a while now, and wihle it looked like the (Intel based) current ieee stack would be the base for a future unified wireless stack, things have changed significantly and chances are really high that d80211 will be the future - there has even been the discussion on netdev to make the switch as early as 2.6.19 (that's why I wrote "might ... one release early"). So even if it isn't quite ready for prime time now, it looks like it is very close - and if it makes it into a 2.6.19rcX while 10.2 is still in beta, I'd like to see a backport going into the suse 10.2 kernel - that's what I was really aiming at. ciao Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] openSUSE 10.2 Features and Roadmap
On Wed, Aug 30, 2006 at 05:14:47PM +0200, Sonja Krause-Harder wrote: > Add > > subscribe opensuse-factory > > to .muttrc, restart mutt, then > > L - list reply Ah, great! Yes, that helped indeed. Thanks! Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] openSUSE 10.2 Features and Roadmap
On Wed, Aug 30, 2006 at 10:55:02AM +0200, Andreas Jaeger wrote: > Azerion <[EMAIL PROTECTED]> writes: > > > This is a mail that I send to Andreas some days ago: It is a reply so the > > start is not like a normal startpost. > > Thanks for resending it here. Sorry, personal email sometimes takes > time to answer :-( Yes, and if the list was set to set a reply-to to the list, then the answer would quite likely have been sent to the list instead of you personally. And now a constructive question: Which key do I have to hit in mutt to answer mails to the list *only* (I don't see any use in doing a reply-all - the person who's post I'm answering is most likely on the list too). ciao Joerg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] openSUSE 10.2 Features and Roadmap
On Fri, Aug 25, 2006 at 01:36:19PM +0200, Andreas Jaeger wrote: > Please give feedback and of course if there's something missing - tell > us. Just something I noticed yesterday: Make setting up dialup with UMTS cards easier by adding provider entries for umts/gprs providers. Ciao Joerg PS: having no reply-to to the list really sucks! -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] openSUSE 10.2 Features and Roadmap
On Fri, Aug 25, 2006 at 01:36:19PM +0200, Andreas Jaeger wrote:
> - Kernel 2.6.18
>
> Desktop & Productivity Software
> - support for rt2500 wlan card, Bug 149141
Why is this considered Desktop/Prod instead of kernel?
> - adding Broadcom WLAN support
Please add the devicescape wireless stack into 2.6.18 (you might just be
one release early ;)
The reason why is, that some wireless drivers are only maintained (or
usable) for the devicescape wireless stack, not the regulare one.
ciao
Joerg
--
Joerg Mayer <[EMAIL PROTECTED]>
We are stuck with technology when what we really want is just stuff that
works. Some say that should read Microsoft instead of technology.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Announcing Yast-GTK (forw)
... because the reply-to on a discussion list is not pointing to the list - Forwarded message from Joerg Mayer <[EMAIL PROTECTED]> - Date: Fri, 25 Aug 2006 09:58:47 +0200 From: Joerg Mayer <[EMAIL PROTECTED]> To: Marcel Hilzinger <[EMAIL PROTECTED]> Subject: Re: [opensuse-factory] Announcing Yast-GTK In-Reply-To: <[EMAIL PROTECTED]> On Wed, Aug 23, 2006 at 11:23:00AM +0200, Marcel Hilzinger wrote: > > Just out of interest, what is the advantage of re-implementing yast by > > linking it with libgtk instead of libqt? Wouldn't the time have been > > better spent improving yast itself? > > What's the advantage of having a qt and a gtk frontend for networkmanager? > And > having a qt and a gtk desktop at all? > > Give KDE users qt and Gnome users gkt ! And while you are at it: Can the next SoC project please remove the gnome dependencies from zen (and other system services) and offer qt/kde alternatives for those who only want to run a kde desktop? ciao Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. - End forwarded message - -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] SL-Factory vs. SL-Factory-debug
On Fri, Aug 25, 2006 at 05:54:18AM +0200, Andreas Hanke wrote: > Someone has to parse all this stuff. I mean, the metadata. It is well > known that zypp parses the repository metadata slowly. It has already > become faster and it will become even better, but it's still slow. > > And it's not just zypp. Yum, with the new(!) C metadata parser written > by Tambet Ingo, needs half a minute to parse primary.xml and again half > a minute to parse filelists.xml on my laptop. I don't even want to know > how slow it would be with the old python parser. OK, so you are proposing a *workaround* for a known and very severe problem. Especially with factory, we should *not* concentrate on workaround but on *fixes*! So as long as factory is a development branch, this *should not* be done. ciao Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Network Install WAS: Re: Factory miniiso dies during startup
On Wed, Aug 09, 2006 at 06:23:45PM +0200, Hans-Peter Jansen wrote: [very comprehensible solution deleted] Thanks! Unfortunately, I was really trying to do a complete net-install without downloading the isos first (the only other machine available on that network was a windows laptop). So it came down to doing a 10.1 install instead of a factory/alpha install which I would have preferred very much. Ciao Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Currently no fglrx for factory?
On Wed, Aug 09, 2006 at 03:24:39PM +0200, Dominique Leuenberger wrote: > > maybe you can fake it with > export X_VERSION=x700 > in front of the buildpkg command. > > trying to fake the detected version. In both cases (10.1 and 10.2): no, the messages haven't changed at all. The ABI version (10.1) would remain incompatible in any case, but the 7.2.-1.2 message is the same too. Thanks! Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Currently no fglrx for factory?
On Wed, Aug 09, 2006 at 02:47:26PM +0200, Stefan Dirsch wrote: > > > > When I run --buildpkg for 10.1, it complains that > > > > "module ABI majore versoin (0) doesn't match the server's version(1)", > > > > when I build for 10.2, i complains that > > > > "... - detected X.org 7.2.-1.2, required X.org 7.1.0.0" > > > > > > > > Maybe it would be a good idea to make sure that this doesn't find its > > > > way into the Alpha3. Also, is there a way to work around this? OK, so no factory and Alpha > 2 for people with ATI X1xxx cards for now (my "production" laptop) and no fglrx for the testbed laptop with X300 either. Why the X300 doesn't work with non-proprietary drivers is left as an exercise to the writer, if I find the time to play some more :) Ciao Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Currently no fglrx for factory?
On Wed, Aug 09, 2006 at 02:32:06PM +0200, Stefan Dirsch wrote: > On Wed, Aug 09, 2006 at 02:20:08PM +0200, Joerg Mayer wrote: > > Hello, > > > > I just updated my experimental laptop to current factory and fglrx to > > 8.27.10. It seems that I currently can't get the fglrx to work: > > When I run --buildpkg for 10.1, it complains that > > "module ABI majore versoin (0) doesn't match the server's version(1)", > > when I build for 10.2, i complains that > > "... - detected X.org 7.2.-1.2, required X.org 7.1.0.0" > > > > Maybe it would be a good idea to make sure that this doesn't find its > > way into the Alpha3. Also, is there a way to work around this? > > Use --buildpkg for 10.2 instead. > > when I build for 10.2, i complains that > > "... - detected X.org 7.2.-1.2, required X.org 7.1.0.0" Sorry that I wrote that in a hard to understand way. Ciao Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] Currently no fglrx for factory?
Hello, I just updated my experimental laptop to current factory and fglrx to 8.27.10. It seems that I currently can't get the fglrx to work: When I run --buildpkg for 10.1, it complains that "module ABI majore versoin (0) doesn't match the server's version(1)", when I build for 10.2, i complains that "... - detected X.org 7.2.-1.2, required X.org 7.1.0.0" Maybe it would be a good idea to make sure that this doesn't find its way into the Alpha3. Also, is there a way to work around this? ciao Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Factory miniiso dies during startup
On Mon, Aug 07, 2006 at 01:23:29PM +0200, Andreas Jaeger wrote: > Joerg Mayer <[EMAIL PROTECTED]> writes: > > > I just downloaded the factory miniiso. After I booted it I selected > > netinstall > > http://ftp.gwdg.de/pub/opensuse/distribution/SL-OSS-factory/inst-source/ > > The installation repository in factory is broken right now, we're > working on fixing it. > > For now I advise to use the Alpha2 tree, How do I do a network install of the Alpha2 tree? It looks like there are only isos available. ciao Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Factory miniiso dies during startup
On Mon, Aug 07, 2006 at 12:46:39PM +0200, Joerg Mayer wrote: > I just downloaded the factory miniiso. After I booted it I selected > netinstall > http://ftp.gwdg.de/pub/opensuse/distribution/SL-OSS-factory/inst-source/ > > After the image is downloaded things look like this (on vt3): > > === > dns: ftp.gwdgf.de is 134.76.11.100 > Loading image > "/pub/opensuse/distribution/SL-OSS-factory/inst-source/i386/root" > http: /pub/opensuse/distribution/SL-OSS-factory/inst-source/root (83927040 > bytes) > cramfs: "root 81960" > image size: 81960 kB > mount: /download/image0: we need a loop device > mount: using /dev/loop0 > http: /pub/opensuse/distribution/SL-OSS-factory/inst-source/content (7519 > bytes) > http: /pub/opensuse/distribution/SL-OSS-factory/inst-source/info.txt (868 > bytes) > http: /pub/opensuse/distribution/SL-OSS-factory/inst-source/license.zip (5479 > bytes) > http: /pub/opensuse/distribution/SL-OSS-factory/inst-source/control.xml > (28357 bytes) > Loading image > "/pub/opensuse/distribution/SL-OSS-factory/inst-source/driverupdate" > /download/image1 removed > starting setctsid `showconsole` inst_setup yast > install program exit code is 127 > opensuse/distribution/SL-OSS-factory/inst-source > /fdownload/image0 removed > === > > (typos are mine). > > I've also tried to use safe settings, vesa and text console: Same > result. > > Ideas how to get things running (or at least debug them further). > Oh, the System is an IBM/Lenovo thinkpad z60 with dual core processor. Sorry: T60, not Z60 -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] Factory miniiso dies during startup
I just downloaded the factory miniiso. After I booted it I selected netinstall http://ftp.gwdg.de/pub/opensuse/distribution/SL-OSS-factory/inst-source/ After the image is downloaded things look like this (on vt3): === dns: ftp.gwdgf.de is 134.76.11.100 Loading image "/pub/opensuse/distribution/SL-OSS-factory/inst-source/i386/root" http: /pub/opensuse/distribution/SL-OSS-factory/inst-source/root (83927040 bytes) cramfs: "root 81960" image size: 81960 kB mount: /download/image0: we need a loop device mount: using /dev/loop0 http: /pub/opensuse/distribution/SL-OSS-factory/inst-source/content (7519 bytes) http: /pub/opensuse/distribution/SL-OSS-factory/inst-source/info.txt (868 bytes) http: /pub/opensuse/distribution/SL-OSS-factory/inst-source/license.zip (5479 bytes) http: /pub/opensuse/distribution/SL-OSS-factory/inst-source/control.xml (28357 bytes) Loading image "/pub/opensuse/distribution/SL-OSS-factory/inst-source/driverupdate" /download/image1 removed starting setctsid `showconsole` inst_setup yast install program exit code is 127 opensuse/distribution/SL-OSS-factory/inst-source /fdownload/image0 removed === (typos are mine). I've also tried to use safe settings, vesa and text console: Same result. Ideas how to get things running (or at least debug them further). Oh, the System is an IBM/Lenovo thinkpad z60 with dual core processor. Ciao Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] updating m4 package from factory
On Tue, Jul 25, 2006 at 05:27:33AM +0200, Andreas Hanke wrote: > To answer your question: Factory is not guaranteed to be always consistent. Good. > See also: http://en.opensuse.org/Factory > > For example, it can happen that a package is updated in such a way that > dependent packages have to be updated as well, but the updated packages > of the dependent packages don't build. Well, that's fine if it really is just a build problem. But that's not always the case. Sometimes (as in the udev split) providing the new packages is just forgotten. > This will probably always happen from time to time and disappear again > shortly afterwards. Well, if "shortly" covers an interval of more thant one week, ok. I have one (small/not-so-small) wish regarding these inconsistencies: Could the repo be checked automatically after new packages have been posted or packages have been replaced and the result be posted to this list? ciao Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] updating m4 package from factory
On Mon, Jul 24, 2006 at 05:09:06PM +0200, Marcus Rueckert wrote:
> > ... So the core question is: Is it a
> > valid state, that packages in factory can be inconsistend?
>
> smart tries by design to get the very latest of everything. Even if it
> means to remove some packages that rely on older versions.
You are pointing fingers to *symptoms*, while I try to find out about
the underlying cause. The core problem is not that smart handles some
things in a suboptimal way (your opinion) *in the case the repo is
inconsistent*.
ciao
Joerg
--
Joerg Mayer <[EMAIL PROTECTED]>
We are stuck with technology when what we really want is just stuff that
works. Some say that should read Microsoft instead of technology.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] updating m4 package from factory
On Mon, Jul 24, 2006 at 04:43:59PM +0200, Chema Ollés wrote: > I try to upgrade my system and see that if I update m4 from > [EMAIL PROTECTED] to [EMAIL PROTECTED],smart delete my autoconf [EMAIL > PROTECTED] > because is related with the old m4 version.I can't see any new autoconf > on factory directory... > Is it normal this lack? I asked the same question on #opensuse a week or so ago but got no answer. The underlying question goes much further though: Is it intentional that it is possible to have missing dependencies in the published factory tree: When the system smart-updated directfb, several other packages got removed as well. What was even better was a while ago, when udev was split into udev + somelib, and somelib wasn't published for one more week or so. So the core question is: Is it a valid state, that packages in factory can be inconsistend? Ciao Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: SPAM: [opensuse-factory] Re: VMWare and XEN
On Mon, May 29, 2006 at 04:34:49PM +0200, jdd wrote: > [EMAIL PROTECTED] wrote: > >You may be able to run windows under Xen. > > > >see http://en.opensuse.org/Xen_Full_Virtualization_Example > > do you know is this work with any processor? I was said that > this is impossible :-) It will work with the processors that have virtualization support. In case you want the exact list of processors: Read the page given above and follow the appropriate link Joerg - wondering why people speculate instead of just checking the facts :-( -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Re: Nagios 2.0
On Thu, Feb 16, 2006 at 11:01:29AM +, Ciro Iriarte wrote: > Are you talking about the official tar from nagios.sourceforge.net?. > It's an option, but that way i'm losing the init scripts for > example... Am i right?. There's one thing about this discussion/lamenting that I don't understand: nagios 2 has been production quality for a while and has been at least as good as 1.x for more than 2 Suse releases. The major step from 2beta to 2release was that documentation was "complete". We've been using 2.x from alpha stage onwards with networks of more than 2000 manged components. So, what I just don't get: Why does the release of 2.0 make a switch from 1.x to 2.0 so urgent now? ciao Joerg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
