[opensuse-factory] Status: Distribution
Hi, After M2 release we have several projects running at the same time: - reducing the bootstap cycle in openSUSE:Factory (removing gpg-offline out of it is one action item) - perl 5.18 update shows 38 build failures at the moment: openSUSE:Factory:Staging:perl518 - gcc 4.8 switch shows 27 build failures openSUSE:Factory:Staging:Gcc48 - python3 is split it into its own devel project - KDE 4.11 beta is prepared in K:D:F - Jan is preparing a switch to db-60 - tons of things I forgot to mention :) Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tuesday 2013-06-18 12:56, Stephan Kulow wrote:
Hi,
After M2 release we have several projects running at the same time:
- perl 5.18 update shows 38 build failures at the moment: openSUSE:Factory:Staging:perl518
The one from wget is funny: wget.pod around line 2105: Expected text after =item, not a number And indeed, wget.pod contains "=item 0", "=item 1", etc. But that is a normal thing, because it describes the exit codes. FWIW, the 0 is meant as text. I smell an overjealous new check inside the POD reader.
- gcc 4.8 switch shows 27 build failures openSUSE:Factory:Staging:Gcc48
If OBS could exclude packages from the list that also fail in the parent <link> project, the lists would probably be shorter, and more accurate. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 18.06.2013 16:58, Jan Engelhardt wrote:
On Tuesday 2013-06-18 12:56, Stephan Kulow wrote:
Hi,
After M2 release we have several projects running at the same time:
- perl 5.18 update shows 38 build failures at the moment: openSUSE:Factory:Staging:perl518
The one from wget is funny:
wget.pod around line 2105: Expected text after =item, not a number
And indeed, wget.pod contains "=item 0", "=item 1", etc. But that is a normal thing, because it describes the exit codes. FWIW, the 0 is meant as text. I smell an overjealous new check inside the POD reader.
- gcc 4.8 switch shows 27 build failures openSUSE:Factory:Staging:Gcc48
If OBS could exclude packages from the list that also fail in the parent <link> project, the lists would probably be shorter, and more accurate.
I actually build disabled all them. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tuesday 2013-06-18 17:16, Stephan Kulow wrote:
- gcc 4.8 switch shows 27 build failures openSUSE:Factory:Staging:Gcc48
If OBS could exclude packages from the list that also fail in the parent <link> project, the lists would probably be shorter, and more accurate.
I actually build disabled all them.
The build-disable flag however does nothing to affect the display as "failed" in the webui however. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 18.06.2013 17:27, Jan Engelhardt wrote:
On Tuesday 2013-06-18 17:16, Stephan Kulow wrote:
- gcc 4.8 switch shows 27 build failures openSUSE:Factory:Staging:Gcc48
If OBS could exclude packages from the list that also fail in the parent <link> project, the lists would probably be shorter, and more accurate.
I actually build disabled all them.
The build-disable flag however does nothing to affect the display as "failed" in the webui however.
No, it does. Do you have an example? I see atm 18 failed, 63 disabled. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tuesday 2013-06-18 17:32, Stephan Kulow wrote:
If OBS could exclude packages from the list that also fail in the parent <link> project, the lists would probably be shorter, and more accurate.
I actually build disabled all them.
The build-disable flag however does nothing to affect the display as "failed" in the webui however.
No, it does. Do you have an example? I see atm 18 failed, 63 disabled.
brltty. In factory[1], it says: [Exclamation] brltty hardware Fails for 32 days: libbrlttyssd.so not build Request 179538 to hardware In the gcc48 staging project[2], it says: [Exclamation] brltty Fails for 10 days: Unknown build failure o:F:Staging:Gcc48/brltty is indeed <build><disable/></build>, but it still shows on [2]. [1] https://build.opensuse.org/stage/project/status?project=openSUSE%3AFactory&limit_to_fails=true&include_versions=true [2] https://build.opensuse.org/stage/project/status?project=openSUSE%3AFactory:Staging:Gcc48&limit_to_fails=true&include_versions=true -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 19.06.2013 00:13, schrieb Jan Engelhardt:
[1] https://build.opensuse.org/stage/project/status?project=openSUSE%3AFactory&limit_to_fails=true&include_versions=true [2] https://build.opensuse.org/stage/project/status?project=openSUSE%3AFactory:Staging:Gcc48&limit_to_fails=true&include_versions=true
Ah, you look at project status - build disabled packages are listed there as failing on purpose to avoid having no information at all while the prj is build disabled. It will go away as I wipe --build-disabled. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 18.06.2013 16:58, Jan Engelhardt wrote:
On Tuesday 2013-06-18 12:56, Stephan Kulow wrote:
Hi,
After M2 release we have several projects running at the same time:
- perl 5.18 update shows 38 build failures at the moment: openSUSE:Factory:Staging:perl518
The one from wget is funny:
wget.pod around line 2105: Expected text after =item, not a number
And indeed, wget.pod contains "=item 0", "=item 1", etc. But that is a normal thing, because it describes the exit codes. FWIW, the 0 is meant as text. I smell an overjealous new check inside the POD reader.
Hmm, http://perldoc.perl.org/perlpod.html even recommends using numbers Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tue, Jun 18, 2013 at 05:31:27PM +0200, Stephan Kulow wrote:
On 18.06.2013 16:58, Jan Engelhardt wrote:
On Tuesday 2013-06-18 12:56, Stephan Kulow wrote:
Hi,
After M2 release we have several projects running at the same time:
- perl 5.18 update shows 38 build failures at the moment: openSUSE:Factory:Staging:perl518
The one from wget is funny:
wget.pod around line 2105: Expected text after =item, not a number
And indeed, wget.pod contains "=item 0", "=item 1", etc. But that is a normal thing, because it describes the exit codes. FWIW, the 0 is meant as text. I smell an overjealous new check inside the POD reader.
It probably should be written as: =item C<0>
Hmm, http://perldoc.perl.org/perlpod.html even recommends using numbers
It recommends "1.", "2.", note the period at the end of the number. Cheers, Micha. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Michael Schroeder wrote:
On Tue, Jun 18, 2013 at 05:31:27PM +0200, Stephan Kulow wrote:
On 18.06.2013 16:58, Jan Engelhardt wrote:
On Tuesday 2013-06-18 12:56, Stephan Kulow wrote:
The one from wget is funny:
wget.pod around line 2105: Expected text after =item, not a number
And indeed, wget.pod contains "=item 0", "=item 1", etc. But that is a normal thing, because it describes the exit codes. FWIW, the 0 is meant as text. I smell an overjealous new check inside the POD reader.
It probably should be written as:
=item C<0>
That's not "probably should be", but "must be". :-) There's an alternative, you can use "=item B<0>". Then the exit code is in boldface which is readable as well.
Hmm, http://perldoc.perl.org/perlpod.html even recommends using numbers
It recommends "1.", "2.", note the period at the end of the number.
You *must not* use "1.", "2.", for describing exit codes in POD. That's POD's way to demand a numbered list with pseudo-markup. POD will complain if the numbers are not incremented by one, the complain will be in the generated man page. (Up to Perl 5.8, POD did ignore the numbers completely and generated some of its own.) I.e., =item 0. =item 1. =item 4. in such a man page will get you a nice section at the man page's end that your markup is wrong. Not something you want, probably. ;-) Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod, Roedermark, Germany Email: jschrod@acm.org -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El 18/06/13 06:56, Stephan Kulow escribió:
- gcc 4.8 switch shows 27 build failures openSUSE:Factory:Staging:Gcc48
You can remove "popt" from the list, build fails due to OBS error, not due to new GCC. Same deal with ppl-testsuite fails due to OOM -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (5)
-
Cristian Rodríguez -
Jan Engelhardt -
Joachim Schrod -
Michael Schroeder -
Stephan Kulow