who is the postfix expert for suse 12.3
I need a little help ?
--
Hans Krueger
hanskrueger007(a)roadrunner.com
registered Linux user 289023
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
Am I correct in assuming that these files for a kernel should always be
downloaded as a 'set' for any version of a kernel? And here I am taking
only the kernel-desktop as my example:
1. kernel-desktop
2. kernel-desktop-development
3. kernel-development (from the no-arch repo)
4. kernel-firmware (from the no-arch repo)
Reasons for my question are:
* I use the ...Kernel:/stable/standard repo for my kernels and using
this I updated my kernel to 3.12.0-1 this morning but this did not
update the file kernel-firmware even though a later version is showing
in YaST;
* Patrick mentioned that Tumbleweed is using kernel 3.12.0-34.2 - which
I just downloaded. But before installing it I wanted to make sure that I
need all of the 4 files I mention above so as not to zonk my 13.1 RC2.
Thanks for advice.
BC
--
Using openSUSE 13.1, KDE 4.11.2 & kernel 3.12.0-1 on a system with-
AMD FX 8-core 3.6/4.2GHz processor
16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM
Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 OC 2GB DDR5 GPU
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
Hi, this may be a dumb question, but for some days I am receiving this
insistent notification:
File '/repodata/repomd.xml' not found on medium
'http://download.opensuse.org/repositories/KDE:/Extra/KDE_Release_49_openSUS…'
I am running opensuse 12.2
The above repository has moved? Is this a temporary issue?
Thanks,
Davi
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
On 11/08/2013 03:12 PM, Mark Hounschell wrote:
> On 11/08/2013 02:57 PM, Cristian RodrÃguez wrote:
>> El 08/11/13 19:06, Mark Hounschell escribi?:
>>
>>> Just as a followup, sometime between 8.2 and 12.3
>>
>> That's quite some big time leap..
>>
>>> I'm happy SuSE included byacc in 12.3 and hope they continue to do so.
>>> My original problem is solved by using byacc instead of bison/yacc.
>>
>> Cool :-) It is however still recommended to fix the code if possible,
>> since it is very likely that in 10 years it has bit-rotten
>> significantly. Pay particularly careful attention to compiler warnings.
>>
>
> Ya, that's true. I am inhibiting them all with gcc -w for now. I don't
> really want to have to fix any lex/yacc stuff. Strangest looking stuff
> I've ever looked at. Maybe I'll -Wall it just to see what happens.
>
I just did. Ouch!!!! There's a few hours of something to do when I'm bored.
Mark
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
On 11/08/2013 02:57 PM, Cristian RodrÌguez wrote:
> El 08/11/13 19:06, Mark Hounschell escribiÛ:
>
>> Just as a followup, sometime between 8.2 and 12.3
>
> That's quite some big time leap..
>
>> I'm happy SuSE included byacc in 12.3 and hope they continue to do so.
>> My original problem is solved by using byacc instead of bison/yacc.
>
> Cool :-) It is however still recommended to fix the code if possible,
> since it is very likely that in 10 years it has bit-rotten
> significantly. Pay particularly careful attention to compiler warnings.
>
Ya, that's true. I am inhibiting them all with gcc -w for now. I don't
really want to have to fix any lex/yacc stuff. Strangest looking stuff
I've ever looked at. Maybe I'll -Wall it just to see what happens.
Mark
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
On 11/08/2013 10:22 AM, Mark Hounschell wrote:
> On 11/08/2013 10:10 AM, Cristian RodrÃguez wrote:
>> El 08/11/13 13:31, Mark Hounschell escribi?:
>>
>>> GCC: (GNU) 3.3 20030226 (prerelease) (SuSE Linux)
>>
>> An eternity in software terms, no wonder it no longer builds from
>> source..
>>
>> You could post the build failure in the appropiate yacc/lex list to get
>> it working instead of spending time doing archeology.
>>
>
> Ya, I did that already. I _suspect_ the problem is in the yacc/bison
> compatability feature (bison -y) or the lex/flex compatability -l option
> no longer doing something it should be. Drastically changing the code is
> not an option for me. I am lex/yacc ignorant (intensionally) and would
> rather stay that way. I think/hope it's a bug in one of those two things
> mentioned above. Maybe they will fix it if it is. Probably been a long
> time since those 2 things were tested.
Just as a followup, sometime between 8.2 and 12.3 yacc and bison were
combined into a single package. The bison -y option was supposed to make
bison yacc compatible. And calling yacc was the same as calling bison
with the -y option. But Not OLD yacc compatible. Fortunately the
original yacc package from 8.2 is now found in the byacc package in 12.3.
I'm happy SuSE included byacc in 12.3 and hope they continue to do so.
My original problem is solved by using byacc instead of bison/yacc.
Regards
Mark
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
Is anyone using QGIS with Open Street Map data? Specifically with the QGIS
version available from OBS. Although I am interested in oS 12.3, experiences
on any oS release are welcome.
In my case, none of the built-in OSM functions/ICONS are appearing anywhere.
--
Yours sincerely,
Roger Oberholtzer
Ramböll RST / Systems
Office: Int +46 10-615 60 20
Mobile: Int +46 70-815 1696
roger.oberholtzer(a)ramboll.se
________________________________________
Ramböll Sverige AB
Krukmakargatan 21
P.O. Box 17009
SE-104 62 Stockholm, Sweden
www.rambollrst.se
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
On 11/08/2013 10:10 AM, Cristian RodrÌguez wrote:
> El 08/11/13 13:31, Mark Hounschell escribiÛ:
>
>> GCC: (GNU) 3.3 20030226 (prerelease) (SuSE Linux)
>
> An eternity in software terms, no wonder it no longer builds from source..
>
> You could post the build failure in the appropiate yacc/lex list to get
> it working instead of spending time doing archeology.
>
Ya, I did that already. I _suspect_ the problem is in the yacc/bison
compatability feature (bison -y) or the lex/flex compatability -l option
no longer doing something it should be. Drastically changing the code is
not an option for me. I am lex/yacc ignorant (intensionally) and would
rather stay that way. I think/hope it's a bug in one of those two things
mentioned above. Maybe they will fix it if it is. Probably been a long
time since those 2 things were tested.
Mark
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
I have an executable that works but am now unable to build it from
source. I'm currently running 12.3 and I've gone back as far as 10.3 to
no avail. It is a lex/yacc thing and I am lex/yacc ignorant. I can tell
from the executable which gcc and glibc were used. I'm looking for the
SuSE release that came with that particular version of gcc/glibc.
#strings -a executable_ELF_file | grep "GCC: ("
GCC: (GNU) 3.3 20030226 (prerelease) (SuSE Linux)
.
.
and
#strings -a executable_ELF_file | grep -i "GLIBC"
GLIBC_2.1
GLIBC_2.0
/usr/src/packages/BUILD/glibc-2.3.2/csu
/usr/src/packages/BUILD/glibc-2.3.2/csu
/usr/src/packages/BUILD/glibc-2.3.2/csu
.
.
Not sure how to go about finding which release had these versions. Anyone?
Thanks
Mark
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org