Discussion:
Enable build with Factory repo in Kernel:stable
(too old to reply)
Max Lin
2014-08-21 10:57:15 UTC
Permalink
Raw Message
Hi,

Can someone enable build with Factory repo. in Kernel:stable? otherwise
the submission from Kernel:stable would not pass check by
factory-repochecker, ie. https://build.opensuse.org/request/show/245242


Best regards,
Max
Jiri Slaby
2014-08-21 13:32:20 UTC
Permalink
Raw Message
Post by Max Lin
Hi,
Can someone enable build with Factory repo. in Kernel:stable? otherwise
the submission from Kernel:stable would not pass check by
factory-repochecker, ie. https://build.opensuse.org/request/show/245242
Hi, there is a little point in building the kernel for multiple
repositories. Leaving for discussion, if we should switch to building
against factory (more frequent kernel rebuilds) or add a special staging
project with factory repo in it...
--
js
suse labs
Michal Marek
2014-08-21 13:36:23 UTC
Permalink
Raw Message
Post by Jiri Slaby
Post by Max Lin
Hi,
Can someone enable build with Factory repo. in Kernel:stable? otherwise
the submission from Kernel:stable would not pass check by
factory-repochecker, ie. https://build.opensuse.org/request/show/245242
Hi, there is a little point in building the kernel for multiple
repositories.
Agreed.
Post by Jiri Slaby
Leaving for discussion, if we should switch to building
against factory (more frequent kernel rebuilds)
The Kernel:* projects' repositories have rebuild="local" block="local"
in the configuration, so they only rebuild when a new kernel is
uploaded. An exception is the QA repository, but that one only builds
kernel-obs-qa, which doesn't take long. So this is not such a big deal.

Michal
Ludwig Nussel
2014-08-21 14:27:44 UTC
Permalink
Raw Message
Post by Michal Marek
Post by Jiri Slaby
Post by Max Lin
Can someone enable build with Factory repo. in Kernel:stable? otherwise
the submission from Kernel:stable would not pass check by
factory-repochecker, ie. https://build.opensuse.org/request/show/245242
Hi, there is a little point in building the kernel for multiple
repositories.
Agreed.
Post by Jiri Slaby
Leaving for discussion, if we should switch to building
against factory (more frequent kernel rebuilds)
The Kernel:* projects' repositories have rebuild="local" block="local"
in the configuration, so they only rebuild when a new kernel is
uploaded. An exception is the QA repository, but that one only builds
kernel-obs-qa, which doesn't take long. So this is not such a big deal.
Please switch to build for Factory then. The definition of a devel
project for Factory is to build for Factory after all. Otherwise you
wouldn't be sure that the kernel actually builds with the toolchain etc
there.

cu
Ludwig
--
(o_ Ludwig Nussel
//\
V_/_ http://www.suse.de/
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)
--
To unsubscribe, e-mail: opensuse-kernel+unsubscribe-***@public.gmane.org
To contact the owner, e-mail: opensuse-kernel+owner-***@public.gmane.org
Takashi Iwai
2014-08-21 13:36:46 UTC
Permalink
Raw Message
At Thu, 21 Aug 2014 15:32:20 +0200,
Post by Jiri Slaby
Post by Max Lin
Hi,
Can someone enable build with Factory repo. in Kernel:stable? otherwise
the submission from Kernel:stable would not pass check by
factory-repochecker, ie. https://build.opensuse.org/request/show/245242
Hi, there is a little point in building the kernel for multiple
repositories. Leaving for discussion, if we should switch to building
against factory (more frequent kernel rebuilds) or add a special staging
project with factory repo in it...
How about just adding factory repo but not publishing it?


Takashi
Andreas Schwab
2014-08-25 07:51:25 UTC
Permalink
Raw Message
Post by Takashi Iwai
How about just adding factory repo but not publishing it?
What's wrong with publishing it?

Andreas.
--
Andreas Schwab, SUSE Labs, schwab-***@public.gmane.org
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
Takashi Iwai
2014-08-25 08:05:46 UTC
Permalink
Raw Message
At Mon, 25 Aug 2014 09:51:25 +0200,
Post by Andreas Schwab
Post by Takashi Iwai
How about just adding factory repo but not publishing it?
What's wrong with publishing it?
People may get confused which repo to use.
(Don't ask why people get confused. Experience says that normal human
beings get confused when there is more than one thing.)


Takashi
Andreas Schwab
2014-08-25 08:31:19 UTC
Permalink
Raw Message
Post by Takashi Iwai
At Mon, 25 Aug 2014 09:51:25 +0200,
Post by Andreas Schwab
Post by Takashi Iwai
How about just adding factory repo but not publishing it?
What's wrong with publishing it?
People may get confused which repo to use.
That will not add significantly to the confusion.

Andreas.
--
Andreas Schwab, SUSE Labs, schwab-***@public.gmane.org
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
Stephan Kulow
2014-08-25 11:40:23 UTC
Permalink
Raw Message
Post by Andreas Schwab
Post by Takashi Iwai
At Mon, 25 Aug 2014 09:51:25 +0200,
Post by Andreas Schwab
Post by Takashi Iwai
How about just adding factory repo but not publishing it?
What's wrong with publishing it?
People may get confused which repo to use.
That will not add significantly to the confusion.
Not to bright minds like you - but if you follow e.g. KDE mailing lists
you will find quickly that no matter how clearly you document it or how
much effort you put in finding good names - there are always people
confused.

And having a 2nd repo doesn't even add any value IMO - we want
only one repo and we want factory, so where is the problem?

Greetings, Stephan
Takashi Iwai
2014-08-25 11:50:53 UTC
Permalink
Raw Message
At Mon, 25 Aug 2014 13:40:23 +0200,
Post by Stephan Kulow
Post by Andreas Schwab
Post by Takashi Iwai
At Mon, 25 Aug 2014 09:51:25 +0200,
Post by Andreas Schwab
Post by Takashi Iwai
How about just adding factory repo but not publishing it?
What's wrong with publishing it?
People may get confused which repo to use.
That will not add significantly to the confusion.
Not to bright minds like you - but if you follow e.g. KDE mailing lists
you will find quickly that no matter how clearly you document it or how
much effort you put in finding good names - there are always people
confused.
And having a 2nd repo doesn't even add any value IMO - we want
only one repo and we want factory, so where is the problem?
The Kernel:stable repo has been (and is) for openSUSE 13.1-based
systems, including Tumbleweed. Building only with FACTORY brings a
slight danger of breakage on such systems. That's the major concern
for switching, AFAIK.


Takashi
Stephan Kulow
2014-08-25 12:09:13 UTC
Permalink
Raw Message
Post by Takashi Iwai
At Mon, 25 Aug 2014 13:40:23 +0200,
Post by Stephan Kulow
Post by Andreas Schwab
Post by Takashi Iwai
At Mon, 25 Aug 2014 09:51:25 +0200,
Post by Andreas Schwab
Post by Takashi Iwai
How about just adding factory repo but not publishing it?
What's wrong with publishing it?
People may get confused which repo to use.
That will not add significantly to the confusion.
Not to bright minds like you - but if you follow e.g. KDE mailing lists
you will find quickly that no matter how clearly you document it or how
much effort you put in finding good names - there are always people
confused.
And having a 2nd repo doesn't even add any value IMO - we want
only one repo and we want factory, so where is the problem?
The Kernel:stable repo has been (and is) for openSUSE 13.1-based
systems, including Tumbleweed. Building only with FACTORY brings a
slight danger of breakage on such systems. That's the major concern
for switching, AFAIK.
If that danger exists, the theory that Kernel: projects only need one
repo is doomed.

Greetings, Stephan
Michal Marek
2014-08-27 13:54:47 UTC
Permalink
Raw Message
Post by Takashi Iwai
At Mon, 25 Aug 2014 13:40:23 +0200,
Post by Stephan Kulow
And having a 2nd repo doesn't even add any value IMO - we want
only one repo and we want factory, so where is the problem?
The Kernel:stable repo has been (and is) for openSUSE 13.1-based
systems, including Tumbleweed. Building only with FACTORY brings a
slight danger of breakage on such systems. That's the major concern
for switching, AFAIK.
openSUSE:Tumbleweed builds the kernel with the 13.1 toolchain. So the
change only affects users who were using just the stable kernel, but not
Tumbleweed. And it's not any drastic change after all.

BTW, Jiri did the switch yesterday. So far, everything has been green or
blue.

Michal
Andreas Färber
2014-08-27 14:22:41 UTC
Permalink
Raw Message
Post by Michal Marek
BTW, Jiri did the switch yesterday. So far, everything has been green or
blue.
Unfortunately all ARM repositories have disappeared now. No PowerPC
either. Could you please look into that?

Thanks,
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
--
To unsubscribe, e-mail: opensuse-kernel+unsubscribe-***@public.gmane.org
To contact the owner, e-mail: opensuse-kernel+owner-***@public.gmane.org
Michal Marek
2014-08-27 14:54:08 UTC
Permalink
Raw Message
Post by Andreas Färber
Post by Michal Marek
BTW, Jiri did the switch yesterday. So far, everything has been green or
blue.
Unfortunately all ARM repositories have disappeared now. No PowerPC
either. Could you please look into that?
Fixed.

Michal
--
To unsubscribe, e-mail: opensuse-kernel+unsubscribe-***@public.gmane.org
To contact the owner, e-mail: opensuse-kernel+owner-***@public.gmane.org
Andreas Schwab
2014-08-25 12:15:57 UTC
Permalink
Raw Message
Post by Stephan Kulow
Post by Andreas Schwab
Post by Takashi Iwai
At Mon, 25 Aug 2014 09:51:25 +0200,
Post by Andreas Schwab
Post by Takashi Iwai
How about just adding factory repo but not publishing it?
What's wrong with publishing it?
People may get confused which repo to use.
That will not add significantly to the confusion.
Not to bright minds like you - but if you follow e.g. KDE mailing lists
you will find quickly that no matter how clearly you document it or how
much effort you put in finding good names - there are always people
confused.
Which exactly proves my point.

Andreas.
--
Andreas Schwab, SUSE Labs, schwab-***@public.gmane.org
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
Loading...