Re: [opensuse-factory] speed impression on firefox 2

2006-11-01 Thread Dominique Leuenberger


>>> Reply on 02-11-2006 9:19:52 <<<> IP6 is enabled by default and most DNS-servers cannot handle> itgenerating > long delays.. Change in yast > network card > advanced >> IP6. I just> did > that and now it is fast again :D> > Does that help?
 
Bart,
 
no, unfortunately I already had IPV6 disabled in Yast and I even disabled that one witing about:config (the option network.dns.disableIPv6 = true)
 
But still, my FF2 seems to sleep in front of me whenever I request a webage. Seems it's time for me to start a WireShark on this. Let's hope I find something like this.
 
I'll post my results as soon as I find more.
 
Regards,
Dominique
 
> > Bart> > Op dinsdag 31 oktober 2006 11:49, schreef Dominique Leuenberger:> > Hi everybody,> >> > I have upgraded to Beta 1 of openSUSE 10.2 last week.> >> > Since then, I feel Firefox (which also got upgraded to 2.0 now) much> > slower than 1.5 was before.> > For example, when entering an URL then hitting , for a while> > nothing happens (not even the status bar changes from stopped or> > something).> >> > In general, I would say the surfing experiance got much worse.> >> > I also have FF on my win installation in the office and wouldn't say> it> > degraded somehow. (or not as much experianced).> >> > Does anybody else have this experiance with FF2?> >> > Dominique> -> To unsubscribe, e-mail: [EMAIL PROTECTED]> For additional commands, e-mail: [EMAIL PROTECTED]> > 


Re: [opensuse-factory] speed impression on firefox 2

2006-11-01 Thread Rajko M
On Wednesday 01 November 2006 06:51, Andreas Jaeger wrote:
> > I'm a little tired of IPv6 enabled by default.
>
> Wait for beta2 and check the network proposa,

It's time, as it is endless string of similar questions that should not appear 
at all. The enterprise networks have IT stuff that can reconfigure system for 
their needs. The problem is for private users that mostly have no clue what 
to do and what we see is minority that found the way to ask the question.  

-- 
Regards,
Rajko M.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [opensuse-factory] About ext3 as default and periodic fs checks

2006-11-01 Thread Sid Boyce

Alex wrote:

PS: I'm sad about loosing reiserfs


...especially if that means, if I interpret this thread correctly, 
the "just-in-case" fschecks are back :-(((.


Is this really the case? IMHO this is a giant step back into the past. Not 
even Windows does that.


Alex
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





That was the main reason I went to reiserfs from ext2, fsck.ext2 of a 
20G drive was painful back then, 10x20G, I'd need to power up just 
before going to bed.

Regards
Sid.
--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support 
Specialist, Cricket Coach

Microsoft Windows Free Zone - Linux used for all Computing Tasks

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [opensuse-factory] tiny-nvidia-installer removed from factory

2006-11-01 Thread Stefan Dirsch
On Wed, Nov 01, 2006 at 09:42:08PM -, [EMAIL PROTECTED] wrote:
> > Honestly only the
> > kernel update process (KMP packages) can avoid this problem. I
> > prevented this problem before SLE10 by uninstalling the driver in
> > %pre of the affected packages, but I needed to remove this
> > workaround for the KMP approach for SLE10. :-(
> 
> KMPs would of course be ideal. But it seems we won't have them for
> openSUSE. There is much rumour and speculation as to why this is, It would
> be nice if someone could give a definitive statement. If I understand
> correctly the situation for SLE10:
> 
> -Novell build the packages (from rpm vendor, build host, packager,author)
> -Novell don't want to risk hosting them as they violate the GPL so ask
> nvidia to host them.
> -Nvidia happily host them and take legal risk of being sued by kernel
> developers.
> 
> It would be nice if someone could clarify what is different for openSUSE,
> has anyone from novell even bothered to ask nvidia to host packages for
> openSUSE? Have nvidia refused? why? or does Novell/SUSE not want non-gpl
> kernel modules to be available anywhere for openSUSE, but think it's ok
> for SLE for some reason?
> 
> No-one seems to know the answers, so a statement from someone would be
> appreciated.

Last time I tried to push this issue was not really successful. :-(
Read the results in Bug #206956.

I suggest to take the SRPMs I've attached to this bugreport and host
them somewhere, e.g. packman. I would like to host them via the
openSUSE buildservice (since the driver itself is marked as NoSource
anyway), but unfortunately it's not possible to specify to only build
the SRPM. :-(

Best regards,
Stefan

Public Key available
--
Stefan Dirsch (Res. & Dev.)   SUSE LINUX Products GmbH
Tel: 0911-740 53 0Maxfeldstraße 5
FAX: 0911-740 53 479  D-90409 Nürnberg
http://www.suse.deGermany 
--
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: [opensuse-factory] OpenSUSE 10.2 beta1 netinst CD install problems with VMWare

2006-11-01 Thread Mark E Mason
Hello,

I didn't get that far.  I ran into this right after the language
selection screen.

/Mark 

> -Original Message-
> From: Christoph Thiel [mailto:[EMAIL PROTECTED] 
> Sent: Wednesday, November 01, 2006 2:58 PM
> To: opensuse-factory@opensuse.org
> Subject: Re: [opensuse-factory] OpenSUSE 10.2 beta1 netinst 
> CD install problems with VMWare
> 
> On Wed, Nov 01, 2006 at 02:30:47PM -0800, Mark E Mason wrote:
> 
> > I was attempting to install OpenSUSE 10.2 beta1 as a guest 
> OS under VMWare
> > (under Windows XP) using the NetInst image.  Initial boot 
> was fine, but
> > shortly into the install processes, I'd get and error 
> dialog to the effect
> > of "make sure CD 1 is in the drive".  Changing to another 
> console window,
> > I was able to confirm that the image could be mounted - so 
> I'm assuming
> > the problem lies with either how the CD represented itself, 
> or the CD#
> > detection code.
> 
> Where did you point the installer to install from? FTP? HTTP? 
> URL please.
> 
> 
> Best,
> Christoph
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [opensuse-factory] OpenSUSE 10.2 beta1 netinst CD install problems with VMWare

2006-11-01 Thread Christoph Thiel
On Wed, Nov 01, 2006 at 02:30:47PM -0800, Mark E Mason wrote:

> I was attempting to install OpenSUSE 10.2 beta1 as a guest OS under VMWare
> (under Windows XP) using the NetInst image.  Initial boot was fine, but
> shortly into the install processes, I'd get and error dialog to the effect
> of "make sure CD 1 is in the drive".  Changing to another console window,
> I was able to confirm that the image could be mounted - so I'm assuming
> the problem lies with either how the CD represented itself, or the CD#
> detection code.

Where did you point the installer to install from? FTP? HTTP? URL please.


Best,
Christoph
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: [opensuse-factory] How to do an in-house top-level build of OpenSUSE?

2006-11-01 Thread Mark E Mason
Hello,
 
> From: Carl-Daniel Hailfinger 
> 
> Hi,
> 
> Mark E Mason wrote:
> > I'm strongly considering attempting a build of OpenSUSE for an
> > architecture it does not support yet.  I have other Linuxes such as
> > Debian and Gentoo running on this hardware, but not 
> OpenSUSE.  There was
> > a similar thread last month regarding SPARC.
> 
> Would that architecture be MIPS64? I'm quite interested in having
> openSUSE run on my Extreme Networks switch which has such a CPU
> (although I doubt it has enough non-volatile storage for that).

Yes.  In particular, I'm interested in n32 and n64 userlands, although
o32 is probably the easiest to bring up and the best starting point.

Thanks,
Mark

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [opensuse-factory] How to do an in-house top-level build of OpenSUSE?

2006-11-01 Thread Carl-Daniel Hailfinger
Hi,

Mark E Mason wrote:
> I'm strongly considering attempting a build of OpenSUSE for an
> architecture it does not support yet.  I have other Linuxes such as
> Debian and Gentoo running on this hardware, but not OpenSUSE.  There was
> a similar thread last month regarding SPARC.

Would that architecture be MIPS64? I'm quite interested in having
openSUSE run on my Extreme Networks switch which has such a CPU
(although I doubt it has enough non-volatile storage for that).

Regards,
Carl-Daniel
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[opensuse-factory] OpenSUSE 10.2 beta1 netinst CD install problems with VMWare

2006-11-01 Thread Mark E Mason



Hello 
all,
 
I was attempting to 
install OpenSUSE 10.2 beta1 as a guest OS under VMWare (under Windows XP) using 
the NetInst image.  Initial boot was fine, but shortly into the install 
processes, I'd get and error dialog to the effect of "make sure CD 1 is in the 
drive".  Changing to another console window, I was able to confirm that the 
image could be mounted - so I'm assuming the problem lies with either how the CD 
represented itself, or the CD# detection code.
 
After several 
retries, I gave up, and started downloading with the 'standard' CDs (CD1, CD2, 
CD3, etc).  Everything is going fine so far - they just take a lot longer 
to download (I'm up to CD 4).
 
Hope this 
helps,
Mark
 


Re: [opensuse-factory] DVD/CD writer problems with openSuse 10.2 beta 1

2006-11-01 Thread Christoph Thiel
On Wed, Nov 01, 2006 at 11:48:33PM +0200, Viljo Mustonen wrote:

> I have Compaq Evo W4000 workstation with LG GSA-4167B
> DVD-writer as master and LITEON LTR-40125S CD-writer
> as slave at secondary IDE bus. Both devices works well
> with openSuse 10.1 and W2k. Boot time is about 1 minute.
> 
> With openSuse 10.2 beta 1 here is problems. LITEON does
> not work. LG mostly reads but not writes properly,auto
> mount often does not work.Boot time to login screen is
> very long, between 2 minutes 40 seconds and nearly
> 5 minutes.
> 
> Boot.msg:s typically contains lines:
> 
> <6>scsi1 : ata_piix
> <6>ata2.00: ATAPI, max UDMA/33
> <6>ata2.01: ATAPI, max UDMA/33
> <6>ata2.00: configured for UDMA/33
> <4>ata2.01: qc timeout (cmd 0xef)
> <3>ata2.01: failed to set xfermode (err_mask=0x4)
> <4>ata2.01: limiting speed to UDMA/25
> <4>ata2: failed to recover some devices, retrying in 5 secs
> <6>ata2.00: configured for UDMA/33
> <4>ata2.01: qc timeout (cmd 0xef)
> <3>ata2.01: failed to set xfermode (err_mask=0x4)
> <4>ata2.01: limiting speed to PIO0
> <4>ata2: failed to recover some devices, retrying in 5 secs
> <6>ata2.00: configured for UDMA/33
> <4>ata2.01: qc timeout (cmd 0xef)
> <3>ata2.01: failed to set xfermode (err_mask=0x4)
> <4>ata2.01: disabled
> <4>ata2: failed to recover some devices, retrying in 5 secs
> <3>ata2.00: failed to set xfermode (err_mask=0x40)
> <4>ata2.00: limiting speed to UDMA/25
> <4>ata2: failed to recover some devices, retrying in 5 secs
> <6>ata2.00: configured for UDMA/25
> 
> Often three times more same kinds of lines.

Those should be gone with Beta2. Please report a bug, in case you still find
them in Beta2 (which is due next week).


Best,
Christoph
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[opensuse-factory] How to do an in-house top-level build of OpenSUSE?

2006-11-01 Thread Mark E Mason



Hello,
 
I'm strongly 
considering attempting a build of OpenSUSE for an architecture it does not 
support yet.  I have other Linuxes such as Debian and Gentoo running on 
this hardware, but not OpenSUSE.  There was a similar thread last month 
regarding SPARC.
 
There's the usual 
bootstrapping issues to work through (I think I can handle those) - but, 
where should I look for the scripts/programs to drive the top-level configure 
and build of a distribution?  I've found the BuildServer under svn - but 
it's not clear to me if that's the right tool for this, or if it's overkill or 
??? (or if it contains the distribution configuration info).
 
Any thoughts or 
pointers would be much appreciated.
 
Thanks in 
advance,
Mark


[opensuse-factory] DVD/CD writer problems with openSuse 10.2 beta 1

2006-11-01 Thread Viljo Mustonen

I have Compaq Evo W4000 workstation with LG GSA-4167B
DVD-writer as master and LITEON LTR-40125S CD-writer
as slave at secondary IDE bus. Both devices works well
with openSuse 10.1 and W2k. Boot time is about 1 minute.

With openSuse 10.2 beta 1 here is problems. LITEON does
not work. LG mostly reads but not writes properly,auto
mount often does not work.Boot time to login screen is
very long, between 2 minutes 40 seconds and nearly
5 minutes.

Boot.msg:s typically contains lines:

<6>scsi1 : ata_piix
<6>ata2.00: ATAPI, max UDMA/33
<6>ata2.01: ATAPI, max UDMA/33
<6>ata2.00: configured for UDMA/33
<4>ata2.01: qc timeout (cmd 0xef)
<3>ata2.01: failed to set xfermode (err_mask=0x4)
<4>ata2.01: limiting speed to UDMA/25
<4>ata2: failed to recover some devices, retrying in 5 secs
<6>ata2.00: configured for UDMA/33
<4>ata2.01: qc timeout (cmd 0xef)
<3>ata2.01: failed to set xfermode (err_mask=0x4)
<4>ata2.01: limiting speed to PIO0
<4>ata2: failed to recover some devices, retrying in 5 secs
<6>ata2.00: configured for UDMA/33
<4>ata2.01: qc timeout (cmd 0xef)
<3>ata2.01: failed to set xfermode (err_mask=0x4)
<4>ata2.01: disabled
<4>ata2: failed to recover some devices, retrying in 5 secs
<3>ata2.00: failed to set xfermode (err_mask=0x40)
<4>ata2.00: limiting speed to UDMA/25
<4>ata2: failed to recover some devices, retrying in 5 secs
<6>ata2.00: configured for UDMA/25

Often three times more same kinds of lines.

-- 

Viljo

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [opensuse-factory] tiny-nvidia-installer removed from factory

2006-11-01 Thread B . Weber
> Honestly only the
> kernel update process (KMP packages) can avoid this problem. I
> prevented this problem before SLE10 by uninstalling the driver in
> %pre of the affected packages, but I needed to remove this
> workaround for the KMP approach for SLE10. :-(

KMPs would of course be ideal. But it seems we won't have them for
openSUSE. There is much rumour and speculation as to why this is, It would
be nice if someone could give a definitive statement. If I understand
correctly the situation for SLE10:

-Novell build the packages (from rpm vendor, build host, packager,author)
-Novell don't want to risk hosting them as they violate the GPL so ask
nvidia to host them.
-Nvidia happily host them and take legal risk of being sued by kernel
developers.

It would be nice if someone could clarify what is different for openSUSE,
has anyone from novell even bothered to ask nvidia to host packages for
openSUSE? Have nvidia refused? why? or does Novell/SUSE not want non-gpl
kernel modules to be available anywhere for openSUSE, but think it's ok
for SLE for some reason?

No-one seems to know the answers, so a statement from someone would be
appreciated.

_
Benjamin Weber
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [opensuse-factory] next ppc sync

2006-11-01 Thread Christoph Thiel
On Wed, Nov 01, 2006 at 08:24:22PM +0100, Peter Czanik wrote:

> I saw from my rsync logs, that x86 was updated. When can I expect an
> update also for PPC? There were some recent changes, which show up in
> bugzilla as checked in, but not yet in factory...

We will hopefully sync out PPC sometime tomorrow.


Best,
Christoph
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[opensuse-factory] next ppc sync

2006-11-01 Thread Peter Czanik

Hello,
I saw from my rsync logs, that x86 was updated. When can I expect an 
update also for PPC? There were some recent changes, which show up in 
bugzilla as checked in, but not yet in factory...


--
CzP
http://peter.czanik.hu/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [opensuse-factory] libstdc++.la library

2006-11-01 Thread Andreas Hanke
Pascal Bleser schrieb:
>> Only those from the PackMan repo and other non-SUSE repos have
>> references to libstdc++.la, and only if they are build for distros <
>> 10.2. Once there is a 10.2 PackMan repo with packages specifically built
>> for 10.2, you don't need to worry any more.
> 
> What makes you think that ?

I'm convinced that you're not re-using old binary packages, but
rebuilding everything from scratch. That makes me think that.

> AFAIK no one at Packman (nor do I with my packages) removes the .la
> files from the -devel packages, not even if they are for >= 10.2.

You don't need to remove anything. Rebuilding everything is sufficient.

I have just verified that rebuilding mpeg4ip on a clean 10.2 system with
no old binary packages on it results in a libmp4v2.la that has no
references to /usr/lib/libstdc++.la in it. Nothing had to be removed
manually in order to achieve that.

libtool asks for libstdc++.la only if one of the other .la files in the
chain references it, and other .la files only reference it if
libstdc++.la existed when the package was built.

The conclusion is that cleanly rebuilding everything solves the problem.
Given that libstdc++.la has been removed months ago and that there are
4000 source packages in the distribution which are all still building,
and given that re-using old binary packages is broken anyway, I don't
think that this breaks builds which wouldn't have been broken anyway
until a build log shows it.

> If it is, it should be discussed with those package maintainers at
> Packman.

I don't know what needs to be discussed here, re-using old binary
packages is clearly broken, cannot work for all kinds of other reasons
besides this one and we don't know if it has been discussed even with
the package maintainers at SUSE. I doubt it, but don't know it.

A package maintainer shouldn't even notice the absense of libstdc++.la.

If I read and understand correctly what anyone can read on
[opensuse-bugs] and [opensuse-commit], the usual practice is that a
package maintainer changes whatever he likes and the others follow it by
fixing their failed builds, if any. Maybe these discussions behind
closed doors where the community is locked out don't exist at all.

Andreas
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [opensuse-factory] tiny-nvidia-installer removed from factory

2006-11-01 Thread Stefan Dirsch
On Wed, Nov 01, 2006 at 02:47:55PM +0100, Pascal Bleser wrote:
> I've started a shell script that checks prerequisites, warns/stops if X
> is running, pulls the latest nvidia driver from their website (works for
> 32bit and 64bit) and then runs the installer, but it sure needs more
> testing. Maybe it's even a good idea to make an RPM out of it, with
>   Requires: make gcc glibc-devel kernel-source
> in it.
> http://linux01.gwdg.de/~pbleser/files/nvidia-installer.sh

I somewhat like the idea of a script to replace tiny-nvidia-installer (*) 
since it is much more flexible, e.g. the compilation could break at
any time due to a SUSE kernel update or a newer NVIDIA driver. Within
a script you can specify, which NVIDIA driver version to download,
patch it before starting compilation, etc.

I still think it makes sense to maintain such a package in the
buildservice because then this package could even update itself (the
script can check and do this if required) when a newer version is
available. Providing an update for an official package in the
distribution usually takes several weeks after it has been checked
in. :-(

> But then again, maybe installing packages and adding repositories is
> still to complex in the first place.
> If that was trivial to do, even for beginners, it would make a lot of
> things easier.

I'm thinking about dummy packages, which do nothing more than adding
repositories in %post and remove them again in %postun (not sure if
this is possible at all), but probably we'll run into legal problems
doing so. :-(

Best regards,
Stefan

(*) Not really, since the NVIDIA installer replaces some system files
(libGL, glx Xserver extension, ...). This can break your system,
when you update packages (Mesa, xorg-x11-server, ...) including
files, which have been replaced by the NVIDIA installer
before. Even uninstalling the NVIDIA driver doesn't help since it
will restore the files of the old package. Honestly only the
kernel update process (KMP packages) can avoid this problem. I
prevented this problem before SLE10 by uninstalling the driver in
%pre of the affected packages, but I needed to remove this
workaround for the KMP approach for SLE10. :-(

Public Key available
--
Stefan Dirsch (Res. & Dev.)   SUSE LINUX Products GmbH
Tel: 0911-740 53 0Maxfeldstraße 5
FAX: 0911-740 53 479  D-90409 Nürnberg
http://www.suse.deGermany 
--
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [opensuse-factory] Re: Beta1 install report

2006-11-01 Thread Joachim Reichelt






Juan Erbes schrieb:
2006/11/1, Andreas Jaeger <[EMAIL PROTECTED]>:
  
  Andras Mantia <[EMAIL PROTECTED]> writes:


> Hi,

>

>  I just updated my 10.1 system to 10.2 Beta1 to finally test the

> upcoming SUSE and in hope to find bugs and make the final release
as

> good as possible. ;-)

>  I used a way for upgrade that is for sure not well tested, namely

> System Update from YaST with the downloaded CD ISO images that
were not

> copied to the hard disk, but were sitting on a DVD. This is all
due to

> lack of disk space (but I ordered a new HDD today :-)). Good
enough,

> the installation went quite OK,

> aside of two issues, one because of my system (not enough hard
disk

> space, so some packages were not upgraded, altough I'm sure that
the

> space would be enough if I would uses --force for rpm), the other
one

> was a more serious problem:

> 2006-10-30 20:46:56 <5> stein(5536) [base]
Exception.cc(log):94

> RpmDb.cc(doInstallPackage):2002 THROW:

> RpmDb.cc(doInstallPackage):2002: Subprocess faile

> d. Error: RPM failed: Updating etc/sysconfig/displaymanager...

> 2006-10-30 20:46:56 <5> stein(5536) [base]
Exception.cc(log):94

> 2006-10-30 20:46:56 <5> stein(5536) [base]
Exception.cc(log):94 ERROR:

> SuSEconfig or requested SuSEconfig module not present!

> 2006-10-30 20:46:56 <5> stein(5536) [base]
Exception.cc(log):94

> 2006-10-30 20:46:56 <5> stein(5536) [base]
Exception.cc(log):94

> error: %postun(xgl-cvs_060522-0.13.x86_64) scriptlet failed, exit

> status 1

>

> Does it worth a bug report or is it known?


Worth a bugreport against xgl .


> So far so good, I rebooted, modified the fstab due to the fact
that the

> IDE port on Promise chip is still not supported (reported since
10.0,

> waiting for the patch to hit the upstream kernel). After the
second

> reboot, everything looked fine until I started to write this mail.
The

> KMail composer here is completely broken, and I know it's not a
KMail

> bug as I used a self compiled SVN version from 3.5.5 branch even
before

> on 10.1. The problems are:

> 1) text because invisible in the Subject line after the first
space

> 2) spaces are not shown and cursor jumps erratic from one place to

> another, making input impossible. I found that I had set Microsoft
Sans

> Serif as the composer font and switching to another one (even
other MS

> fonts) is fine. Did something went wrong with font cache
generation?

>

> I can file a report for this as well, but I'm not sure it is a
general

> problem.


Please double chck that your installation is complete.


  
  
I have installed 10.2 alpha 5 plus partially updated to beta 1,
  
because the yast online update tool do'nt works right, and then I
  
downloaded the 2 first CD's, and booting from the first, to update the
  
base system, but with the dependencies dialog when was resolved all
  
the dependencies, the dependencies window appear blank and do'nt
  
permit to continue the upgrade. If I press the "Try for new" (Intentar
  
de nuevo) button, the window appear newly, and the only way that
  
dissapear is with the cancel button, but the dependencies are not
  
resolved, If click in the accept button.
  

and on reboot of such a system, yast was corrupted
yast sw_single
you
crashed

Thanks
  
-
  
To unsubscribe, e-mail: [EMAIL PROTECTED]
  
For additional commands, e-mail: [EMAIL PROTECTED]
  
  


-- 








  
  Mit freundlichen Gruessen Best Regards 
Joachim Reichelt
  
  
  Dr.
Joachim Reichelt
Division of Structural Biology (SB)
Helmholtz Center for Infection Research (HZI) 
Inhoffenstrasse 7
D-38124 Braunschweig
Germany
  
  Phone: +49-531-6181-7047
Fax: +49-531 2612 388
  
  
  
  
  
  
  
  

  






begin:vcard
fn:Joachim Reichelt
n:Reichelt;Joachim
org:Helmholtz Center for Infection Research (HZI);Division of Structural Biology (SB)
adr;quoted-printable;dom:;;Inhoffenstra=C3=9Fe 7;Braunschweig;;38124
email;internet:[EMAIL PROTECTED]
tel;work:(49) 531 6181 7047
tel;fax:(49) 531  612388
x-mozilla-html:FALSE
url:http://www.helmholtz-hzi.de
version:2.1
end:vcard



[opensuse-factory] Re: Beta1 install report

2006-11-01 Thread Juan Erbes

2006/11/1, Andreas Jaeger <[EMAIL PROTECTED]>:

Andras Mantia <[EMAIL PROTECTED]> writes:

> Hi,
>
>  I just updated my 10.1 system to 10.2 Beta1 to finally test the
> upcoming SUSE and in hope to find bugs and make the final release as
> good as possible. ;-)
>  I used a way for upgrade that is for sure not well tested, namely
> System Update from YaST with the downloaded CD ISO images that were not
> copied to the hard disk, but were sitting on a DVD. This is all due to
> lack of disk space (but I ordered a new HDD today :-)). Good enough,
> the installation went quite OK,
> aside of two issues, one because of my system (not enough hard disk
> space, so some packages were not upgraded, altough I'm sure that the
> space would be enough if I would uses --force for rpm), the other one
> was a more serious problem:
> 2006-10-30 20:46:56 <5> stein(5536) [base] Exception.cc(log):94
> RpmDb.cc(doInstallPackage):2002 THROW:
> RpmDb.cc(doInstallPackage):2002: Subprocess faile
> d. Error: RPM failed: Updating etc/sysconfig/displaymanager...
> 2006-10-30 20:46:56 <5> stein(5536) [base] Exception.cc(log):94
> 2006-10-30 20:46:56 <5> stein(5536) [base] Exception.cc(log):94 ERROR:
> SuSEconfig or requested SuSEconfig module not present!
> 2006-10-30 20:46:56 <5> stein(5536) [base] Exception.cc(log):94
> 2006-10-30 20:46:56 <5> stein(5536) [base] Exception.cc(log):94
> error: %postun(xgl-cvs_060522-0.13.x86_64) scriptlet failed, exit
> status 1
>
> Does it worth a bug report or is it known?

Worth a bugreport against xgl .

> So far so good, I rebooted, modified the fstab due to the fact that the
> IDE port on Promise chip is still not supported (reported since 10.0,
> waiting for the patch to hit the upstream kernel). After the second
> reboot, everything looked fine until I started to write this mail. The
> KMail composer here is completely broken, and I know it's not a KMail
> bug as I used a self compiled SVN version from 3.5.5 branch even before
> on 10.1. The problems are:
> 1) text because invisible in the Subject line after the first space
> 2) spaces are not shown and cursor jumps erratic from one place to
> another, making input impossible. I found that I had set Microsoft Sans
> Serif as the composer font and switching to another one (even other MS
> fonts) is fine. Did something went wrong with font cache generation?
>
> I can file a report for this as well, but I'm not sure it is a general
> problem.

Please double chck that your installation is complete.



I have installed 10.2 alpha 5 plus partially updated to beta 1,
because the yast online update tool do'nt works right, and then I
downloaded the 2 first CD's, and booting from the first, to update the
base system, but with the dependencies dialog when was resolved all
the dependencies, the dependencies window appear blank and do'nt
permit to continue the upgrade. If I press the "Try for new" (Intentar
de nuevo) button, the window appear newly, and the only way that
dissapear is with the cancel button, but the dependencies are not
resolved, If click in the accept button.

Thanks
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [opensuse-factory] Beta1 install report

2006-11-01 Thread Andras Mantia
On Wednesday 01 November 2006 14:47, Andreas Jaeger wrote:
> Worth a bugreport against xgl .

Done (# 216982).

> Please double chck that your installation is complete.
Everything else looks fine, only one thing indicated a possible failed 
upgrade: I still got 10.1 /etc/issue and /etc/issue.net . Otherwise I 
don't see major problems with the behavior (and reinstalling the MS 
Sans Serif font does not seem to help. Whatever, I don't care that 
much.).

I find some bugs and have a wish as well: #216977 - please release the 
kommander package on the CDs as well.

Andras
-- 
Quanta Plus developer - http://quanta.kdewebdev.org
K Desktop Environment - http://www.kde.org


pgpdV3rANwFdS.pgp
Description: PGP signature


Re: [opensuse-factory] About ext3 as default and periodic fs checks

2006-11-01 Thread Hernán Lorenzo Fernández
I'm glad to see Michael James think the same way as me. About two days ago I've migrated from Suse 10.1 to Windows because Suse 10.1 takes to boot 4 minutes (not joking!) and Windows Xp about 1 minut (not joking!).
I think one of the worst things about Suse is the TIME!The same happens when you run YAST. It is too slow. It is improductive. I hoppe next releases have "boot express".I tried to put it in a wish list but I couldn't; I don't understand how to send it to a wish list. Sorry about it. 
 Hernan Lorenzo F.  [EMAIL PROTECTED]


Re: [opensuse-factory] tiny-nvidia-installer removed from factory

2006-11-01 Thread Pascal Bleser
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Stefan Dirsch wrote:
> On Wed, Nov 01, 2006 at 01:01:37PM +0100, Carl-Daniel Hailfinger wrote:
>>> No real explanation given. [...]
>>> WONTFIX, build it in the BS. WTF!
>> That's a perfectly valid reason. You can build it in the build service
>> or wait for others to do it. 
> 
> BTW, see
> 
>   project: home:sndirsch 
>   package: tiny-nvidia-installer
> 
> Better copy it immediately. I plan to remove it again pretty soon.
> 
>> SUSE has no obligation to fulfill your
>> wishes unless you have a very convincing reason (and no, it's not you
>> who needs to be convinced).

Carl-Daniel.. geez... wth are you talking about.
Of course they have no obligations, except that if Novell really wants
"openSUSE" and a community, then they do in order to make it work.

John (the OP), Benjamin and I are amongst those who are on the "front"
on IRC with new SUSE users and less experienced ones, who are asking for
help.

If such tools (like y2pmsh or tiny-nvidia-installer) *are* helpful from
our experience, then I *do* think it's a valid point.

Wrt the "openSUSE" community, we're doing a big job there and believe it
or not, #suse is one of the most qualified and helpful linux support
rooms on IRC.

> I gave him a bunch of reasons.

Yes, after he reopened the bug ;)

> 1) It's an undocumented way to install the NVIDIA driver. The driver update
>process should be used instead - if possible. Otherwise use the official
>installer. See http://www.suse.de/~sndirsch/nvidia-installer-HOWTO.html
>for details.
> 2) There's no official download location for up-to-date sources for it, so
>sooner or later it gets broken anyway and I won't notice, because I no
>longer use it.
> 3) IMHO using tiny-nvidia-installer is completely useless. Using it looks
>easy in the first place - given that you have gcc and kernel-source
>installed, but you'll wake up after the first kernel update (Xserver
>is no longer starting!), because you need to recompile the kernel
>module after each update. Since this is a manual step anyway, IMHO
>it's better to know what you're doing and having the complete
>installer already on your harddisk. At least then you don't need to
>download the complete driver again and again. IMHO this is well
>documented in my HOWTO.
> 
>  http://www.suse.de/~sndirsch/nvidia-installer-HOWTO.html
> 
> Probably he cannot be convinced, because he is used to this tool,
> relies on it and it somewhat works for him (good enough).

Stefan, I'm sure that in your focus or your coworkers at SUSE, indeed,
it's a useless tool, it's as easy to grab the NVIDIA-*.run from their
site. So it is to me, to the OP, or probably almost everyone on this list.

The point is, spend some more time on #suse and you'll see the kind of
issues we're trying to help people with.

IMO the most annoying things are, in no particular order:
(1) no command-line (or trivial) way to add repositories (aka
"installation sources")
(2) adding repositories like Packman and mine to get a full-featured
amarok, mplayer, etc...
(3) installing the proprietary nvidia and ati drivers

While improvement is underway with (1)(rug doesn't do the trick, need
something without zmd) and we probably can't do anything about (2) for
the reasons we all know, tiny-nvidia-installer *is* helpful for (3).

Obviously, as Benjamin wrote in a previous mail of this thread, having
KMPs is even better (if they are kept up-to-date with nvidia drivers, at
least somewhat, and especially with kernel package releases from the
online updates), no question.

But if the KMPs are not present or cannot be used, believe me, it's yet
another problem to tell beginners where and how to get the .run file
from nvidia, and tiny-nvidia-installer actually is pretty helpful wrt that.

The most annoying thing with the installation of nvidia's driver is
having to switch to runlevel 3 though, by a large margin.
Sounds easy ? Sure. But when people are on IRC with xchat, konversation,
kopete or chatzilla and you're telling them what to do to install it,
they have to quit their IRC client. So, what happens if anything goes
wrong ? You can't guide them step-by-step anymore either.
(maybe a simple command as a shell script that gets you to #suse on
freenode with irssi would help ;))

Up to SUSE 9.3, the script used by the online update patch used some
trickery to fool the nvidia driver installer - maybe that's still a good
enough approach to make it easier.

I've started a shell script that checks prerequisites, warns/stops if X
is running, pulls the latest nvidia driver from their website (works for
32bit and 64bit) and then runs the installer, but it sure needs more
testing. Maybe it's even a good idea to make an RPM out of it, with
  Requires: make gcc glibc-devel kernel-source
in it.
http://linux01.gwdg.de/~pbleser/files/nvidia-installer.sh

Anyhow, John (the OP)'s point is that it is a real benefit of having it
in the defaul

Re: [opensuse-factory] Package management architecture

2006-11-01 Thread Martin Schlander
I received the below message from Duncan. I believe it was sent only to me by 
mistake, therefore I forward it here as I believe it's important.

On Tuesday 31 October 2006 16:17, Martin Schlander wrote:
> Presently discussion is on-going in bugzilla about the architecture of
> package management, mostly wrt. 10.2. I think that we should clarify longer
> term goals. Which imho must be to not have zmd installed by default on
> openSUSE, as it causes problems and unnecessary complexity without adding
> functionality that the openSUSE users need. I'm curious if official people
> agree with this?

Doing an updater applet for Gnome is really easy. But we should see if it is 
possible to extend the zen-updater to make it multi-backend.

Basically a direct-system applet does:

start,
every X time, launches /usr/sbin/zypp-check-patches-wrapper
parses xml output and display it in a fancy mode.
offers a button to launch yast2 inst_source and yast2_onlineupdate

That is. All the logic, caching, etc, is in zypp helper.

Perhaps a nice chance for the communty to contribute some lines of code.

Duncan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [opensuse-factory] tiny-nvidia-installer removed from factory

2006-11-01 Thread Stefan Dirsch
On Wed, Nov 01, 2006 at 01:01:37PM +0100, Carl-Daniel Hailfinger wrote:
> > No real explanation given. [...]
> > WONTFIX, build it in the BS. WTF!
> 
> That's a perfectly valid reason. You can build it in the build service
> or wait for others to do it. 

BTW, see

  project: home:sndirsch 
  package: tiny-nvidia-installer

Better copy it immediately. I plan to remove it again pretty soon.

> SUSE has no obligation to fulfill your
> wishes unless you have a very convincing reason (and no, it's not you
> who needs to be convinced).

I gave him a bunch of reasons.

1) It's an undocumented way to install the NVIDIA driver. The driver update
   process should be used instead - if possible. Otherwise use the official
   installer. See http://www.suse.de/~sndirsch/nvidia-installer-HOWTO.html
   for details.
2) There's no official download location for up-to-date sources for it, so
   sooner or later it gets broken anyway and I won't notice, because I no
   longer use it.
3) IMHO using tiny-nvidia-installer is completely useless. Using it looks
   easy in the first place - given that you have gcc and kernel-source
   installed, but you'll wake up after the first kernel update (Xserver
   is no longer starting!), because you need to recompile the kernel
   module after each update. Since this is a manual step anyway, IMHO
   it's better to know what you're doing and having the complete
   installer already on your harddisk. At least then you don't need to
   download the complete driver again and again. IMHO this is well
   documented in my HOWTO.

 http://www.suse.de/~sndirsch/nvidia-installer-HOWTO.html

Probably he cannot be convinced, because he is used to this tool,
relies on it and it somewhat works for him (good enough).

Best regards,
Stefan

Public Key available
--
Stefan Dirsch (Res. & Dev.)   SUSE LINUX Products GmbH
Tel: 0911-740 53 0Maxfeldstraße 5
FAX: 0911-740 53 479  D-90409 Nürnberg
http://www.suse.deGermany 
--
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [opensuse-factory] speed impression on firefox 2

2006-11-01 Thread Andreas Jaeger
Rajko M <[EMAIL PROTECTED]> writes:

> On Tuesday 31 October 2006 18:33, Bart Otten wrote:
>> IP6 is enabled by default and most DNS-servers cannot handle
>> itgenerating long delays.. Change in yast > network card > advanced >>
>> IP6. I just did that and now it is fast again :D
>>
>> Does that help?
>>
>
> Yes.
>  
> I'm a little tired of IPv6 enabled by default. 

Wait for beta2 and check the network proposa,

Andreas

> It is used on some internal enterprise networks and that is mostly all.
> It seems it will pass some more time before it comes in public use, but is 
> enabled for years as a default, making those articles permanent need:
> http://en.opensuse.org/Disable_IPv6_for_Firefox
> http://en.opensuse.org/SDB:Mozilla_and_IPv6
> http://en.opensuse.org/SDB:Konqueror_and_IPv6
> http://en.opensuse.org/SDB:Disabling_IPv6_completely
>
> The number of articles tell how many people asked for solution.
>
> BTW, Firefox 2 is pleasant surprise for openSUSE wiki editors. 
> Unlike Konqueror it is fast, and now it has spellcheck. 

Andreas
-- 
 Andreas Jaeger, [EMAIL PROTECTED], http://www.suse.de/~aj/
  SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
   GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


pgpIcWrUVDSTQ.pgp
Description: PGP signature


Re: [opensuse-factory] About ext3 as default and periodic fs checks

2006-11-01 Thread Andreas Jaeger
Michael James <[EMAIL PROTECTED]> writes:

> On Tuesday 31 October 2006 9:36 pm, Silviu Marin-Caea wrote:
>> On Monday 30 October 2006 17:53, Rasmus Plewe wrote:
>> > If a fsck at boot time occurs
>> > - kill the splash screen (usually the computer boots in 3 minutes, now
>> >   it's still unchanged after 10 minutes. Something must be broken.
>> >   Poweroff/on. Does still not boot. Damn Linux, doesn't work. Changing
>> >   OS because Linux doesn't work for me).
>
> This is frighteningly true, here are 2 suggestions,
>  we probably need them both.
>
> 1)  While an fsck is occurring in non-verbose startup mode
>  we need a message to that effect with a progress bar.
>
> 2)  On shutdown; if a routine fsck WOULD happen next reboot,
>  the OS asks if the user minds converting the shutdown to a reboot.
> The fsck can happen on a fresh boot but not when the computer is needed.
> Once booted the system puts up a window a la Mac,
>  waits 2 minutes and shuts back down automatically.
> With the fsck done, the next reboot happens normally.

Could you add those to the feature wishlist in our wiki so that it
does not get forgotten?

>
> How long does it have to take to boot Linux?
> Solaris used to usually boot quickly, unless you touched /reconfigure,
>  then it would go through all the hardware detection.
> Is anyone working on an "express boot"
>  that gets the system up quickly based on stored hardware configs?
>
> With all the hotplug functionality we now have
>  hardware detection at boot is a bit unnecessary.
>
> michaelj
>
> PS: I'm sad about loosing reiserfs

You're not loosing it - just the default is changed.  Feel free to
change it for your installs,

Andreas
-- 
 Andreas Jaeger, [EMAIL PROTECTED], http://www.suse.de/~aj/
  SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
   GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


pgpe5icYxLhNF.pgp
Description: PGP signature


Re: [opensuse-factory] xgl-hardware-list missing in Beta1

2006-11-01 Thread Andreas Jaeger
Sid Boyce <[EMAIL PROTECTED]> writes:

> xgl-cvs is present both on the DVD and in factory, depends on the
> missing xgl-hardware-list. Should I file a bug?

Please do,
Andreas
-- 
 Andreas Jaeger, [EMAIL PROTECTED], http://www.suse.de/~aj/
  SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
   GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


pgpEadmXz02qQ.pgp
Description: PGP signature


Re: [opensuse-factory] Beta1 install report

2006-11-01 Thread Andreas Jaeger
Andras Mantia <[EMAIL PROTECTED]> writes:

> Hi,
>
>  I just updated my 10.1 system to 10.2 Beta1 to finally test the 
> upcoming SUSE and in hope to find bugs and make the final release as 
> good as possible. ;-)
>  I used a way for upgrade that is for sure not well tested, namely 
> System Update from YaST with the downloaded CD ISO images that were not 
> copied to the hard disk, but were sitting on a DVD. This is all due to 
> lack of disk space (but I ordered a new HDD today :-)). Good enough, 
> the installation went quite OK,
> aside of two issues, one because of my system (not enough hard disk 
> space, so some packages were not upgraded, altough I'm sure that the 
> space would be enough if I would uses --force for rpm), the other one 
> was a more serious problem:
> 2006-10-30 20:46:56 <5> stein(5536) [base] Exception.cc(log):94 
> RpmDb.cc(doInstallPackage):2002 THROW:
> RpmDb.cc(doInstallPackage):2002: Subprocess faile
> d. Error: RPM failed: Updating etc/sysconfig/displaymanager...
> 2006-10-30 20:46:56 <5> stein(5536) [base] Exception.cc(log):94
> 2006-10-30 20:46:56 <5> stein(5536) [base] Exception.cc(log):94 ERROR: 
> SuSEconfig or requested SuSEconfig module not present!
> 2006-10-30 20:46:56 <5> stein(5536) [base] Exception.cc(log):94
> 2006-10-30 20:46:56 <5> stein(5536) [base] Exception.cc(log):94 
> error: %postun(xgl-cvs_060522-0.13.x86_64) scriptlet failed, exit 
> status 1
>
> Does it worth a bug report or is it known?

Worth a bugreport against xgl .

> So far so good, I rebooted, modified the fstab due to the fact that the 
> IDE port on Promise chip is still not supported (reported since 10.0, 
> waiting for the patch to hit the upstream kernel). After the second 
> reboot, everything looked fine until I started to write this mail. The 
> KMail composer here is completely broken, and I know it's not a KMail 
> bug as I used a self compiled SVN version from 3.5.5 branch even before 
> on 10.1. The problems are:
> 1) text because invisible in the Subject line after the first space
> 2) spaces are not shown and cursor jumps erratic from one place to 
> another, making input impossible. I found that I had set Microsoft Sans 
> Serif as the composer font and switching to another one (even other MS 
> fonts) is fine. Did something went wrong with font cache generation?
>
> I can file a report for this as well, but I'm not sure it is a general 
> problem.

Please double chck that your installation is complete.

> Congratulation for now, and I'm going out to hunt for the -devel 
> packages not on the 5 CDs... ;-)
>
> Andras

Thanks for testing,
Andreas
-- 
 Andreas Jaeger, [EMAIL PROTECTED], http://www.suse.de/~aj/
  SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
   GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


pgpO4VL9Tkw2I.pgp
Description: PGP signature


Re: [opensuse-factory] tiny-nvidia-installer removed from factory

2006-11-01 Thread B . Weber
> That's a perfectly valid reason. You can build it in the build service
> or wait for others to do it. SUSE has no obligation to fulfill your
> wishes unless you have a very convincing reason (and no, it's not you
> who needs to be convinced).

I think you might be missing the point here. The only reason for existence
of this package is to have something included in the core distro to
install the nvidia drivers. Now if you don't want to package it, that's
fine, but building on the build service is not an option. It would defeat
the entire point of the package, It would be easier for users to just get
the full installer from nvidia.

Now tiny-nvidia-installer is not massively useful in any case, compared to
KMPs. There could be valid reasons for removing it, but the build service
is not a solution in this particular case.

_
Benjamin Weber
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [opensuse-factory] tiny-nvidia-installer removed from factory

2006-11-01 Thread Carl-Daniel Hailfinger
Jonh Arson wrote:
> I wasn't what you can call happy when i found out this little software
> was removed from factory (and even less so when after reopening it 3 or
> 4 time the bug was marked as private).

You reopened the bug multiple times although you were told it was
classified as WONTFIX? Then the only way to stop you from reopening
was indeed marking the bug private.

> No real explanation given. [...]
> WONTFIX, build it in the BS. WTF!

That's a perfectly valid reason. You can build it in the build service
or wait for others to do it. SUSE has no obligation to fulfill your
wishes unless you have a very convincing reason (and no, it's not you
who needs to be convinced).

Regards,
Carl-Daniel
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[opensuse-factory] tiny-nvidia-installer removed from factory

2006-11-01 Thread Jonh Arson
I wasn't what you can call happy when i found out this little software
was removed from factory (and even less so when after reopening it 3 or
4 time the bug was marked as private). No real explanation given.

This was by far the easiest and quickest way to get the Nvidia driver up
and running and i demand explanation. WONTFIX, build it in the BS. WTF!
there is no use to the package if its not right on the cd ...

Now if you don't wanna include it in the default selection this is
totally understandable, but why totally rip the package off ?

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [opensuse-factory] libstdc++.la library

2006-11-01 Thread Andras Mantia
On Wednesday 01 November 2006 12:18, Pascal Bleser wrote:
> What makes you think that ?
>
> AFAIK no one at Packman (nor do I with my packages) removes the .la
> files from the -devel packages, not even if they are for >= 10.2.
>
> Referencing libstdc++.la (c|sh)ould be seen as a bug (at least I've
> been bashed for filing that on bugzilla, or rather, for asking where
> the heck libstdc++.la is on 10.2 ^^).
>
> If it is, it should be discussed with those package maintainers at
> Packman.

You misunderstood. 10.1 has libstdc++.la and Packman packages built on 
10.1 will have .la files referencing to this  libstdc++.la. 10.2 
doesn't have  libstdc++.la, so if you have on your 10.2 system Packman 
packages built for 10.1 and you try to build applications from source 
you might run into this error. Once Packman packages will be built on 
10.2, there won't be any problem as their .la files will not have any 
reference to  libstdc++.la.

Andras

-- 
Quanta Plus developer - http://quanta.kdewebdev.org
K Desktop Environment - http://www.kde.org


pgpJQg0lwp8wM.pgp
Description: PGP signature


Re: [opensuse-factory] libstdc++.la library

2006-11-01 Thread Pascal Bleser
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Andreas Hanke wrote:
> Juan Erbes schrieb:
>> Why I know if one of the 320 files is referenced to libstdc++.la?
> 
> Only those from the PackMan repo and other non-SUSE repos have
> references to libstdc++.la, and only if they are build for distros <
> 10.2. Once there is a 10.2 PackMan repo with packages specifically built
> for 10.2, you don't need to worry any more.

What makes you think that ?

AFAIK no one at Packman (nor do I with my packages) removes the .la
files from the -devel packages, not even if they are for >= 10.2.

Referencing libstdc++.la (c|sh)ould be seen as a bug (at least I've been
bashed for filing that on bugzilla, or rather, for asking where the heck
libstdc++.la is on 10.2 ^^).

If it is, it should be discussed with those package maintainers at Packman.

cheers
- --
  -o) Pascal Bleser http://linux01.gwdg.de/~pbleser/
  /\\ <[EMAIL PROTECTED]>   <[EMAIL PROTECTED]>
 _\_v The more things change, the more they stay insane.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFFSHR2r3NMWliFcXcRAqCpAJ93QKB8L9vyOw0VwPrYF+A7TXDlqQCgndmv
+bTbfCY/Cy1gp4k7PSzHNXw=
=qOyU
-END PGP SIGNATURE-
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]