On Thursday 24 May 2012 06.31:21 Stephan Kulow wrote:

Hi,

As we have no real estimate when the build service will be in a working state again, I can't forecast when we will have the first builds to test either.

This is something that I did not expect - our servers really do not like 12.2 to be released ;(

Greetings, Stephan

<joke mode>Next time think twice before giving a bug name to a release :-)</mode> -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member & Ambassador GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Le 24/05/2012 17:19, Roman Bysh a écrit :

On Thu 24 May 2012 08:33:32 AM EDT, Bruno Friedmann wrote:

...

On Thursday 24 May 2012 06.31:21 Stephan Kulow wrote:

...

Hi,

As we have no real estimate when the build service will be in a working state again, I can't forecast when we will have the first builds to test either.

This is something that I did not expect - our servers really do not like 12.2 to be released ;(

Greetings, Stephan

<joke mode>Next time think twice before giving a bug name to a release :-)</mode>

And 12.2 will be celebrating the 20th anniversary. ;-)

-- Cheers!

Roman --------------------------------------------------------------- openSUSE -- Get it! Discover it! Share it! --------------------------------------------------------------- http://linuxcounter.net/ #179293 hi

is there some news about 12.2 béta version ?? thanks Johann -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 05/28/2012 11:33 AM, Bruno Friedmann wrote:

On Monday 28 May 2012 16.12:55 johann Luce wrote:

...

Le 24/05/2012 17:19, Roman Bysh a écrit :

...

On Thu 24 May 2012 08:33:32 AM EDT, Bruno Friedmann wrote:

...

On Thursday 24 May 2012 06.31:21 Stephan Kulow wrote:

...

Hi,

As we have no real estimate when the build service will be in a working state again, I can't forecast when we will have the first builds to test either.

This is something that I did not expect - our servers really do not like 12.2 to be released ;(

Greetings, Stephan

<joke mode>Next time think twice before giving a bug name to a release :-)</mode>

And 12.2 will be celebrating the 20th anniversary. ;-)

-- Cheers!

Roman --------------------------------------------------------------- openSUSE -- Get it! Discover it! Share it! --------------------------------------------------------------- http://linuxcounter.net/ #179293 hi

is there some news about 12.2 béta version ??

thanks

Johann

Did you see something happening on obs monitor, openqa, fixed the opened bugs. Don't count on other during a long holiday week-end. (Monday off)

According to openqa, the Live CDs for Build 0386 boot and run. Installation of Gnome failed on at least one run because package mdadm was not available. Although I could not find a successful KDE Live CD run at openqa, one was just reported here by Dale Richey. My download is in progress. Systems run or installed from these CDs will report 12.2 M4, but have what will likely be Beta/M5 material. Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 28.05.2012 20:33, Stephan Kulow wrote:

Am 28.05.2012 18:51, schrieb Larry Finger:

...

According to openqa, the Live CDs for Build 0386 boot and run. Installation of Gnome failed on at least one run because package mdadm was not available. Although I could not find a successful KDE Live CD run at openqa, one was just reported here by Dale Richey. My download is in progress.

Unfortunately this is what I'm seeing here too: http://openqa.opensuse.org/viewimg/openqa/testresults/openSUSE-GNOME-LiveCD-...

mdadm's scripts seem to be broken, we need to fix that too.

But the livecd problem is most horrible:

expr(1) segfaults while kiwi tries to calculate how much memory to reserve - and in the end it doesn't give no memory at all, which causes clicfs to return a usage message -> no file system.

I'm trying to find out how to fix expr, others may check mdadm.

expr(1) has been obsolete for more than two decades, you can just use arithmetic expansion available in any Bourne-derived shell for integer arithmetic and bc(1) for floating point arithmetic. -- Guido Berhoerster -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Tuesday 2012-05-29 09:48, Stephan Kulow wrote:

...

expr(1) has been obsolete for more than two decades, you can just use arithmetic expansion available in any Bourne-derived shell for integer arithmetic and bc(1) for floating point arithmetic.

I don't know why kiwi's initrd calls an external tool for it either :)

haveKByte=`cat /proc/meminfo | grep MemFree | cut -f2 -d:| cut -f1 -dk` - haveMByte=`expr $haveKByte / 1024` - haveMByte=`expr $haveMByte \* 7 / 10` + haveMByte=$(($haveKByte * 7 / 10240))

cat has been obsolete for these kind of tasks, you can just use grep MemFree /proc/meminfo ... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Hi,

I don't know why kiwi's initrd calls an external tool for it either :)

There is a good reason. When using expr you see that when in shell debug mode (set -x) when using $((...)) you don't see the calculation bits just the result. So it was helpful for debugging for me but I will eliminate the use of expr if it's gone Just to tell you I don't think it's a good idea to remove old stone linux tools like expr you will break more than just kiwi with it no matter how long you set the "depreciated" bit on it nobody ever will remove ifconfig vs ip and that is set as depreciated for more than two years ;) Thanks Regards, Marcus -- Public Key available gpg --keyserver gpg-keyserver.de --recv-keys 0xCCE3C6A2 ------------------------------------------------------- Marcus Schäfer (Res. & Dev.) SUSE LINUX Products GmbH Tel: 0911-740 53 0 Maxfeldstrasse 5 FAX: 0911-740 53 479 D-90409 Nürnberg GF: Jeff Hawn,Jennifer Guild, Felix Imendörffer HRB: 21284 (AG Nürnberg) Germany http://www.suse.de ------------------------------------------------------- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Jan Engelhardt writes:

On Tuesday 2012-05-29 09:48, Stephan Kulow wrote:

...

I don't know why kiwi's initrd calls an external tool for it either :)

haveKByte=`cat /proc/meminfo | grep MemFree | cut -f2 -d:| cut -f1 -dk`

cat has been obsolete for these kind of tasks, you can just use

grep MemFree /proc/meminfo

...

A grep and 2 cut commands? That's asking for awk (assuming that awk is available in your enviroment: awk '/^MemFree:/ {print $2}' /proc/meminfo or awk '/^MemFree:/ {print $2; exit}' /proc/meminfo -- Karl Eichwalder SUSE LINUX Products GmbH R&D / Documentation Maxfeldstraße 5 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 29.05.2012 11:10, Marcus Schäfer wrote:

Hi,

...

I don't know why kiwi's initrd calls an external tool for it either :)

There is a good reason. When using expr you see that when in shell debug mode (set -x) when using $((...)) you don't see the calculation bits just the result. So it was helpful for debugging for me but I will eliminate the use of expr if it's gone

You could just printf "..." >&2 for the important numbers (which is quite efficient as printf is a builtin). See also my other mail on how to avoid the unnecessary cut/grep/cat stuff.

Just to tell you I don't think it's a good idea to remove old stone linux tools like expr you will break more than just kiwi

It has been obsolete since before Linux even existed, it is in ksh88 and SUSv2/POSIX.2 shell. -- Guido Berhoerster -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 29.05.2012 11:52, Stefan Seyfried wrote:

Am 29.05.2012 11:16, schrieb Karl Eichwalder:

...

A grep and 2 cut commands? That's asking for awk (assuming that awk is available in your enviroment:

awk? which one? I recently got bitten by that one...

And (at least g)awk's startup time is almost as bad as perl's. So one

Try mawk, it's an order of a magnitude faster than gawk and can be configured as /bin/awk using update-alternatives.

grep and two cuts are probably still cheaper.

If you use a modern shell such as bash or ksh93 with built-in support for regexes neither of them should be ever needed. -- Guido Berhoerster -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Am 29.05.2012 12:03, schrieb Guido Berhoerster:

Try mawk, it's an order of a magnitude faster than gawk and can be configured as /bin/awk using update-alternatives.

Yeah, and it has incompatible syntax. The following snippet to extract name and version from a debian control file does not work with mawk: eval $(awk -F":[[:space:]*]" \ '/^Package:/{print "NAME=\""$2"\""}; /^Version:/{print "VERSION=\""$2"\""}' CONTROL/control) But that's now going to be seriously offtopic here.

...

grep and two cuts are probably still cheaper.

If you use a modern shell such as bash or ksh93 with built-in support for regexes neither of them should be ever needed.

Whenever I see "while read a b c; do some string processing in shell; done < foo" code, I always wonder if a simple grep|cut would have been more efficient. The shell is probably not as optimized for such stuff as the specialized tools are. And often it is more readable, too. Again seriously offtopic, so let's stop it. I know that you can do it in $SHELL and I use that often. You are right. -- Stefan Seyfried "Dispatch war rocket Ajax to bring back his body!" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Tue, May 29, 2012 at 4:44 PM, Brian K. White wrote:

You don't need awk or anything but the same shell that's already executing the script.

GetVal () {        DONE=false        until $DONE ; do                IFS=: read KEY VAL junk || DONE=:                        [[ "$KEY" == "$1" ]] && { echo $VAL ; DONE=: ; }        done < $2 }

Isn't that bash-specific? Don't spec scripts have to be more generic (sh-compatible)? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Tue, May 29, 2012 at 5:33 PM, Jan Engelhardt wrote:

This was not inside rpm, if I followed the thread.

Ah, yes, it was kiwi in initrd. All the more reason to avoid bash (with this tendency of late to use dash for init stuff). -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 5/29/2012 3:48 PM, Claudio Freire wrote:

On Tue, May 29, 2012 at 4:44 PM, Brian K. White wrote:

...

You don't need awk or anything but the same shell that's already executing the script.

GetVal () { DONE=false until $DONE ; do IFS=: read KEY VAL junk || DONE=: [[ "$KEY" == "$1" ]] && { echo $VAL ; DONE=: ; } done< $2 }

Isn't that bash-specific? Don't spec scripts have to be more generic (sh-compatible)?

No. That is, this off the cuff example may possibly have some bash-specific syntax, but it does not use or rely on any bash-specific features. This practically identical version works on the stock sco open server /bin/sh which is much cruder than bash or ksh88 let alone ksh93, and works on current bash too, if we cared. Only Linux has /proc anyways (or at least the same /proc contents formatted the same way) but I guess OBS could target ash/busybox environment which would be linux and have /proc yet not bash. GetVal () { DONE=false until $DONE ; do IFS=: read KEY VAL junk || DONE=: [ "$KEY" = "$1" ] && { echo $VAL ; DONE=: ; } done< $2 } I don't know if stuff like this is more or less efficient than calling grep/awk/etc, I just know that it doesn't physically require any external util at all, which is a win in certain ways. If you're scanning many or large files or you need fancy regex matching, then of course the external tools become worth it. Each job really should get it's own evaluation. You can do many of the same jobs with your choice of sed or awk or grep or perl or c or whatever. I always try to minimize just on general principle. Just because grep/awk/whatever is almost always going to be available because surely some other package will require it, is not enough excuse for me to use it if I don't need it. Suppose awk is broken on a machine one day, maybe an update breaks it or something. Either all my zillion scripts built up over years can all break at the same time, or maybe 5 of them can break and maybe only 2 of those are ones any customer even cares about at the moment. Multiply that times every other potential requirement. -- bkw -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 28.05.2012 20:33, Stephan Kulow wrote:

I'm trying to find out how to fix expr, others may check mdadm.

OK, thanks for everyone for adding useless comments about expr and shell programming and ignoring the fact that mdadm is broken too. Anyway, I debugged the issue myself and the problem is that yast mounts /run as tmpfs size=0K (this seems to be an incompat with kernel 3.4 I assume) and as such mdadm fails to install /run/mdadm *as %ghost*. Funny rpm ;( Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 30.05.2012 10:43, Jan Engelhardt wrote:

On Wednesday 2012-05-30 09:37, Stephan Kulow wrote:

...

On 28.05.2012 20:33, Stephan Kulow wrote:

...

I'm trying to find out how to fix expr, others may check mdadm.

OK, thanks for everyone for adding useless comments about expr and shell programming and ignoring the fact that mdadm is broken too.

Anyway, I debugged the issue myself and the problem is that yast mounts /run as tmpfs size=0K (this seems to be an incompat with kernel 3.4 I assume) and as such mdadm fails to install /run/mdadm *as %ghost*. Funny rpm ;(

I'd say it's a known issue:

https://bugzilla.novell.com/show_bug.cgi?id=720150

"the disk space rpm wants increases linearly with the amount of used bytes on the disk [=mountpoint]".

Hmm, no idea how "increases linearly" and size=0 matches :) Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Hi David, Am 07.06.2012 08:28, schrieb David Haller:

Hello,

On Tue, 29 May 2012, Stefan Seyfried wrote:

...

Am 29.05.2012 12:03, schrieb Guido Berhoerster:

...

Try mawk, it's an order of a magnitude faster than gawk and can be configured as /bin/awk using update-alternatives.

Yeah, and it has incompatible syntax. The following snippet to extract name and version from a debian control file does not work with mawk:

eval $(awk -F":[[:space:]*]" \ ^ are you sure the * belongs there?

no, but it works, should the * be behind the second ]?

...

'/^Package:/{print "NAME=\""$2"\""}; /^Version:/{print "VERSION=\""$2"\""}' CONTROL/control)

'/^Package:/{printf("NAME=\"%s\"\n", $2);}; /^Version:/{printf("VERSION=\"%s\"\n", $2);}' CONTROL/control)

How does that help? $2 was empty. Guido explained this to me (in personal mail, as this topic is offtopic here), debian has an obsolet version of mawk which does not support character classed. The code is now using [\t ]* instead of [[:space:]*]

...

But that's now going to be seriously offtopic here.

...

...

grep and two cuts are probably still cheaper.

If you use a modern shell such as bash or ksh93 with built-in support for regexes neither of them should be ever needed.

Whenever I see "while read a b c; do some string processing in shell; done < foo" code, I always wonder if a simple grep|cut would have been more efficient. The shell is probably not as optimized for such stuff as the specialized tools are. And often it is more readable, too.

Usually, the "startup-penalty" of _any_ external tool outweighs by far a dozen lines of using var="${var/%foo/}" and similar lines.

and the readability penalty of val="" while read a b c; do case $a in frob) val=$b; break ;; esac done < /foo/bar/baz outweighs by far val=$(awk '/^frob /{ print $2 }' /foo/bar/baz)

Oh, and awk is rather fast in startup:

$ time awk 'BEGIN{exit;}' real 0m0.066s $ time awk 'BEGIN{exit;}' real 0m0.004s $ time perl -e 1 real 0m0.006s $ time perl -e 1 real 0m0.003s

awk varies further on between .005 and .002, perl between .003 and .008.

So, think again about using grep + cut in a pipe sequence ...

This benchmark is like most benchmarks: irrelevant. In practice, those calls happen after cross compiling a complete operating system => cold caches and stuff in swap. perl loads ~7 MB for doing nothing, awk loads "only" ~4 MB AFAICT. I *guess* (not tested) that as soon as you do anything useful, perl will load even more.

PS: for comparison this is a AMD Athlon II X2 250 with 2 * 3.0GHz cores.

CPU is mostly irrelevant for this kind of workload, it's I/O. But this is still offtopic here. And the problem is solved now. Best regards -- Stefan Seyfried "Dispatch war rocket Ajax to bring back his body!" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Fri, Jun 8, 2012 at 11:31 AM, Claudio Freire wrote:

...

How does that help? $2 was empty. Guido explained this to me (in personal mail, as this topic is offtopic here), debian has an obsolet version of mawk which does not support character classed. The code is now using [\t ]* instead of [[:space:]*]

I don't know why David suggested so, but I can say, at least, that the first form is a security hole.

Sorry, I realized after pressing "send" that the first form uses "print" rather than "printf". So the point is moot. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org