[opensuse-factory] openSUSE:Factory snapshot versus standard
Hi, we're building packages in network:ha-clustering:Factory against, well, Factory. Nodes have just these two repos: baseurl=http://download.opensuse.org/repositories/network:/ha-clustering:/Factory/op... baseurl=http://download.opensuse.org/factory/repo/oss/ Problem: nothing provides kernel-uname-r = 3.11.4-1-default needed by ocfs2-kmp-default-1.8_k3.11.4_1-0.19.4.x86_64 ocfs2-kmp-default was build yesterday (Wed 9, around 9:00). The latest available kernel-default package is: i | kernel-default | package | 3.11.3-2.1 | x86_64 | openSUSE-Factory (Sun Oct 6 01:07:53 2013) I also tried /factory-snapshot/ and a number of other install sources, but no luck. It'd appear more logical to me if n:h:F was *behind* Factory, not the other way around. What am I doing wrong? Regards, Lars -- Architect Storage/HA SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) "Experience is the name everyone gives to their mistakes." -- Oscar Wilde -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Lars Marowsky-Bree <lmb@suse.com> writes:
we're building packages in network:ha-clustering:Factory against, well, Factory.
Nodes have just these two repos: baseurl=http://download.opensuse.org/repositories/network:/ha-clustering:/Factory/op... baseurl=http://download.opensuse.org/factory/repo/oss/
Problem: nothing provides kernel-uname-r = 3.11.4-1-default needed by ocfs2-kmp-default-1.8_k3.11.4_1-0.19.4.x86_64
ocfs2-kmp-default was build yesterday (Wed 9, around 9:00).
The latest available kernel-default package is:
i | kernel-default | package | 3.11.3-2.1 | x86_64 | openSUSE-Factory
The current version in openSUSE:Factory/snapshot is 3.11.4-2.1, which is what network:ha-clustering:Factory is building against. Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2013-10-10T17:12:23, Andreas Schwab <schwab@suse.de> wrote:
i | kernel-default | package | 3.11.3-2.1 | x86_64 | openSUSE-Factory The current version in openSUSE:Factory/snapshot is 3.11.4-2.1, which is what network:ha-clustering:Factory is building against.
That doesn't help me any, though. openSUSE:Factory/snapshot is not available as a repository for zypper to install against, right? If I follow the links from https://build.opensuse.org/project/repository_state/openSUSE:Factory?reposit... I end up here: http://download.opensuse.org/factory/repo/oss/suse/ Which I already use. There doesn't seem do be a downloadable repo? For fun, I tried adding "openSUSE:Factory" to n:h:F again. Then it only offers me a choice of "standard" only (no "snapshot). "Failed to add project or repository: unable to walk on path 'openSUSE:Factory/'" Regards, Lars -- Architect Storage/HA SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) "Experience is the name everyone gives to their mistakes." -- Oscar Wilde -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Lars Marowsky-Bree <lmb@suse.com> writes:
Which I already use. There doesn't seem do be a downloadable repo?
The download repos for factory always lag behind a bit, whereas small repos are published faster. Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2013-10-10T17:23:17, Andreas Schwab <schwab@suse.de> wrote:
Which I already use. There doesn't seem do be a downloadable repo? The download repos for factory always lag behind a bit, whereas small repos are published faster.
"a bit"? The KMPs were built yesterday morning! Is there a snapshot repository that we can build against that actually matches the published packages? Regards, Lars -- Architect Storage/HA SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) "Experience is the name everyone gives to their mistakes." -- Oscar Wilde -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Lars Marowsky-Bree <lmb@suse.com> writes:
On 2013-10-10T17:23:17, Andreas Schwab <schwab@suse.de> wrote:
Which I already use. There doesn't seem do be a downloadable repo? The download repos for factory always lag behind a bit, whereas small repos are published faster.
"a bit"? The KMPs were built yesterday morning!
Factory is a very big project. Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2013-10-10T17:40:30, Andreas Schwab <schwab@suse.de> wrote:
Which I already use. There doesn't seem do be a downloadable repo? The download repos for factory always lag behind a bit, whereas small repos are published faster. "a bit"? The KMPs were built yesterday morning! Factory is a very big project.
Yes. But why build & publish packages further downstream that are uninstallable? Surely I must be missing something; many people must be actively developing against Factory. There must be a way to get consistent builds out of the system, or build against a different target. If not, that basically means that I (we) can't use Factory as a development base. It'd mean we'd instead have to build & test on 12.3/Tumbleweed, or maybe 13.1 one day. A delay of 1,5+ days where we can't install new images or update old ones doesn't work. Could someone please tell me that I'm an idiot and missing something obvious? I'd really appreciate that! Regards, Lars -- Architect Storage/HA SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) "Experience is the name everyone gives to their mistakes." -- Oscar Wilde -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thu, Oct 10, 2013 at 05:41:54PM +0200, Lars Marowsky-Bree wrote:
On 2013-10-10T17:40:30, Andreas Schwab <schwab@suse.de> wrote:
Which I already use. There doesn't seem do be a downloadable repo? The download repos for factory always lag behind a bit, whereas small repos are published faster. "a bit"? The KMPs were built yesterday morning! Factory is a very big project.
Yes. But why build & publish packages further downstream that are uninstallable?
Surely I must be missing something; many people must be actively developing against Factory. There must be a way to get consistent builds out of the system, or build against a different target.
Not many people develop with hard version requirements against e.g. the kernel. You probably dont need the hard version requirement either for a dot release.
If not, that basically means that I (we) can't use Factory as a development base. It'd mean we'd instead have to build & test on 12.3/Tumbleweed, or maybe 13.1 one day. A delay of 1,5+ days where we can't install new images or update old ones doesn't work.
Or the kernel of the day repository, which probably rebuilds faster.
Could someone please tell me that I'm an idiot and missing something obvious? I'd really appreciate that!
Ciao, Marcus -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2013-10-10T17:47:43, Marcus Meissner <meissner@suse.de> wrote:
Not many people develop with hard version requirements against e.g. the kernel. You probably dont need the hard version requirement either for a dot release.
%kernel_module_package expands to this automatically.
Or the kernel of the day repository, which probably rebuilds faster.
Might be an option. Still, it means that what we build against in Factory is, for days, not what we can test with :-( That's hardly a good base. Any real dependency will fail. Any ABI breakage that got sonames wrong will cause hard to trace, random errors. And any ABI breakage that gets them right will throw us back to the latency problem. I see part of the problem, though I wonder why we're then not building against and publishing snapshots atomically for Factory? Regards, Lars -- Architect Storage/HA SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) "Experience is the name everyone gives to their mistakes." -- Oscar Wilde -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2013-10-10T17:23:17, Andreas Schwab <schwab@suse.de> wrote:
Which I already use. There doesn't seem do be a downloadable repo? The download repos for factory always lag behind a bit, whereas small repos are published faster.
OK, I'm convinced now I must be doing tremenduously stupid here, or there's a severe bug in how Factory gets published. By now, it's Sunday. The situation has been like this since Wednesday. Problem: nothing provides kernel-uname-r = 3.11.4-2-default needed by ocfs2-kmp-default-1.8_k3.11.4_2-0.19.5.x86_64 Solution 1: do not install ocfs2-kmp-default-1.8_k3.11.4_2-0.19.5.x86_64 Solution 2: break ocfs2-kmp-default-1.8_k3.11.4_2-0.19.5.x86_64 by ignoring some of its dependencies n:h:F builds against openSUSE:Factory/standard. n:h:F and Factory are the only two repositories configured on the system. Surely the two repositories shouldn't be out-of-sync for what's now at least 4 days? Regards, Lars -- Architect Storage/HA SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) "Experience is the name everyone gives to their mistakes." -- Oscar Wilde -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Dne Ne 13. října 2013 11:42:59, Lars Marowsky-Bree napsal(a):
On 2013-10-10T17:23:17, Andreas Schwab <schwab@suse.de> wrote:
Which I already use. There doesn't seem do be a downloadable repo?
The download repos for factory always lag behind a bit, whereas small repos are published faster.
OK, I'm convinced now I must be doing tremenduously stupid here, or there's a severe bug in how Factory gets published.
By now, it's Sunday. The situation has been like this since Wednesday.
Problem: nothing provides kernel-uname-r = 3.11.4-2-default needed by ocfs2-kmp-default-1.8_k3.11.4_2-0.19.5.x86_64 Solution 1: do not install ocfs2-kmp-default-1.8_k3.11.4_2-0.19.5.x86_64 Solution 2: break ocfs2-kmp-default-1.8_k3.11.4_2-0.19.5.x86_64 by ignoring some of its dependencies
n:h:F builds against openSUSE:Factory/standard. n:h:F and Factory are the only two repositories configured on the system.
Surely the two repositories shouldn't be out-of-sync for what's now at least 4 days?
Regards, Lars
It was really really hasty week. It takes a quite lot of time to finish the factory rebuild when we merge lots of base changes. But you can always track it here [1]. Whenever the repo publishes it is the standard repo. If it is broken after the publishing then there is something wrong, otherwise this time we just put huge load to obs with the rc1 and everything and it didn't simply manage to finish the build yet. Cheers Tom [1] https://build.opensuse.org/project/show/openSUSE:Factory:Rebuild
On Son, 2013-10-13 at 11:42 +0200, Lars Marowsky-Bree wrote:
On 2013-10-10T17:23:17, Andreas Schwab <schwab@suse.de> wrote:
Which I already use. There doesn't seem do be a downloadable repo? The download repos for factory always lag behind a bit, whereas small repos are published faster.
OK, I'm convinced now I must be doing tremenduously stupid here, or there's a severe bug in how Factory gets published.
By now, it's Sunday. The situation has been like this since Wednesday.
Problem: nothing provides kernel-uname-r = 3.11.4-2-default needed by ocfs2-kmp-default-1.8_k3.11.4_2-0.19.5.x86_64 Solution 1: do not install ocfs2-kmp-default-1.8_k3.11.4_2-0.19.5.x86_64 Solution 2: break ocfs2-kmp-default-1.8_k3.11.4_2-0.19.5.x86_64 by ignoring some of its dependencies
n:h:F builds against openSUSE:Factory/standard. n:h:F and Factory are the only two repositories configured on the system.
Surely the two repositories shouldn't be out-of-sync for what's now at least 4 days?
Factory was last published on Oct 8; And as long as there will be checkins happening in order to fix bugs, there will be packages building and publishing won't happen. The repository is ~ 7000 source packages. Publishing only happens when all of them are completed. If the release team takes the day off, there is actually a good chance that the build completes today; there are only like 40 packages left to be done (for standard... /snapshot is at the very beginning and only did 7 packages so far). Feel free to make use of the tools provided, the project view for openSUSE:Factory gives a lot of insight into the current situation https://build.opensuse.org/project/show/openSUSE:Factory You're facing the typical Factory issue: the repositories cannot all be synced against each other and once in a while there are issues like this. Building against releases is easier from that PoV. Also, things like kernel modules are much more fragile, as they have those hard version requirements.. Most other packages are much less specific in the required versions. Dominique. -- Dimstar / Dominique Leuenberger <dimstar@opensuse.org> -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2013-10-13T12:22:44, Dimstar / Dominique Leuenberger <dimstar@opensuse.org> wrote:
Factory was last published on Oct 8; And as long as there will be checkins happening in order to fix bugs, there will be packages building and publishing won't happen.
The repository is ~ 7000 source packages. Publishing only happens when all of them are completed.
Meaning: openSUSE:Factory is useless as a continuous integration & delivery vehicle, and for testing. "Yay." Or publishing needs to happen incrementally, while trying to apply more heuristics to avoid unnecessary rebuilds (those w/o ABI/API changes)?
You're facing the typical Factory issue: the repositories cannot all be synced against each other and once in a while there are issues like this. Building against releases is easier from that PoV.
If Factory is that unusable, there needs to be a way to build against the published snapshot at the very least.
Also, things like kernel modules are much more fragile, as they have those hard version requirements.. Most other packages are much less specific in the required versions.
The hard version dependencies replaced the more dynamic kABI-based symbols. That appears to be a huge step backwards for this case. Regards, Lars -- Architect Storage/HA SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) "Experience is the name everyone gives to their mistakes." -- Oscar Wilde -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Son, 2013-10-13 at 14:25 +0200, Lars Marowsky-Bree wrote:
On 2013-10-13T12:22:44, Dimstar / Dominique Leuenberger <dimstar@opensuse.org> wrote:
Factory was last published on Oct 8; And as long as there will be checkins happening in order to fix bugs, there will be packages building and publishing won't happen.
The repository is ~ 7000 source packages. Publishing only happens when all of them are completed.
Meaning: openSUSE:Factory is useless as a continuous integration & delivery vehicle, and for testing. "Yay."
I think you're just hit by bad timiming; there are large parts of the prject developed in the same way and guess what? It works... despite not being fully optimal, in normal cases it's a few hours diff only (openSUSE:* projects have a higher prio on the scheduler and are usually built first). At this moment, 'continuous integration' is just low prio.. Did you hear about the plans for a 13.1 release? THAT is where current resources are diverted to (believe it or not.. some people DO want to see a stable release that can be used by end users).
Or publishing needs to happen incrementally, while trying to apply more heuristics to avoid unnecessary rebuilds (those w/o ABI/API changes)?
Please feel free to draft up a full proposal, preferably accompanied by patches, that does exactly what you want it to do.
You're facing the typical Factory issue: the repositories cannot all be synced against each other and once in a while there are issues like this. Building against releases is easier from that PoV.
If Factory is that unusable, there needs to be a way to build against the published snapshot at the very least.
It's not unusable.. as said, you have bad luck with timing, paired with the rare fact that you require exact kernel versions. Many other projects are not blocked by this at all.
Also, things like kernel modules are much more fragile, as they have those hard version requirements.. Most other packages are much less specific in the required versions.
The hard version dependencies replaced the more dynamic kABI-based symbols. That appears to be a huge step backwards for this case.
Please bring that forward to the kernel maintainers, who also maintaine the kmp macros to my knowledge.. the hard dependency on a kernel version is indeed a bit weird; 3.11 should be sufficient; 3.11.3 is not supposed to break compatibility to installed modules. Dominique -- Dimstar / Dominique Leuenberger <dimstar@opensuse.org> -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2013-10-13T14:37:26, Dimstar / Dominique Leuenberger <dimstar@opensuse.org> wrote:
Meaning: openSUSE:Factory is useless as a continuous integration & delivery vehicle, and for testing. "Yay." I think you're just hit by bad timiming; there are large parts of the prject developed in the same way and guess what?
"bad timing". Heh. For almost a week. And, of course, the above needs to be read with "... for me" added in.
It works... despite not being fully optimal, in normal cases it's a few hours diff only (openSUSE:* projects have a higher prio on the scheduler and are usually built first).
"built" is not the problem. "published" is the problem.
At this moment, 'continuous integration' is just low prio..
Did you hear about the plans for a 13.1 release? THAT is where current resources are diverted to (believe it or not.. some people DO want to see a stable release that can be used by end users).
Yes. I'm quite happy about that. But it also blocks my work on Factory; I care about both. (That, obviously, is not just a community thing but also has SUSE-internal aspects, that I'm following up on.)
It's not unusable.. as said, you have bad luck with timing, paired with the rare fact that you require exact kernel versions. Many other projects are not blocked by this at all.
You're also missing the point that this is a symptom, not the problem. If the hard & explicit requirements weren't there, I'd *still* get code that was build against a *newer* version of the code. And mostly, we're lucky if code is *forward* compatible for dependencies, not *backwards* compatible. (e.g., if you want something to work on N and N+1, you build it against N, not N+1.) So this is the path to hell - random heisenbugs. It renders the repositories effectively unusable for testing purposes. Yes, *mostly* it'll work, but this is *exactly* the kind of infrastructure problem that a build system is intended to avoid. Like I said, the very least we need for Factory is that we can build against the published snapshot, not just the live repo. Regards, Lars -- Architect Storage/HA SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) "Experience is the name everyone gives to their mistakes." -- Oscar Wilde -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Lars Marowsky-Bree <lmb@suse.com> wrote:
Like I said, the very least we need for Factory is that we can build against the published snapshot, not just the live repo.
Is there a wiki page that describes the factory repo options and relevant names? I thought we had the options of building against: Factory-live Factory-snapshot Factory-milestone But the names of the relevant repos are unclear to me. There is also factory-pure which I have no idea what it is. Greg -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sunday 2013-10-13 14:25, Lars Marowsky-Bree wrote:
On 2013-10-13T12:22:44, Dimstar / Dominique Leuenberger <dimstar@opensuse.org> wrote:
Factory was last published on Oct 8; And as long as there will be checkins happening in order to fix bugs, there will be packages building and publishing won't happen.
The repository is ~ 7000 source packages. Publishing only happens when all of them are completed.
Meaning: openSUSE:Factory is useless as a continuous integration & delivery vehicle, and for testing. "Yay."
Or publishing needs to happen incrementally, [...]
Think, for example, that libcurl4 became libcurl5. But now you have 6999 other packages that more or less depend on libcurl4, which is no longer present in factory -- and this would make installation from scratch practically impossible. If you publish incrementally, you might suddenly end up with a state that cannot be installed at all. That sucks even more. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2013-10-13T20:30:26, Jan Engelhardt <jengelh@inai.de> wrote:
Or publishing needs to happen incrementally, [...] Think, for example, that libcurl4 became libcurl5. But now you have 6999 other packages that more or less depend on libcurl4, which is no longer present in factory -- and this would make installation from scratch practically impossible.
If you publish incrementally, you might suddenly end up with a state that cannot be installed at all. That sucks even more.
Of course you shouldn't publish like this if you *know* you have dependencies you can't satisfy. "incrementally" does not imply "each package, independently and immediately". That is obvious. (In any case, that is exactly what OBS does right now if your build dependencies happen to spawn repos.) Regards, Lars -- Architect Storage/HA SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) "Experience is the name everyone gives to their mistakes." -- Oscar Wilde -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Lars Marowsky-Bree <lmb@suse.com> writes:
Of course you shouldn't publish like this if you *know* you have dependencies you can't satisfy. "incrementally" does not imply "each package, independently and immediately". That is obvious.
Which makes it obvious that you cannot publish until all builds are done. Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2013-10-14T09:11:13, Andreas Schwab <schwab@suse.de> wrote:
Of course you shouldn't publish like this if you *know* you have dependencies you can't satisfy. "incrementally" does not imply "each package, independently and immediately". That is obvious. Which makes it obvious that you cannot publish until all builds are done.
No, it doesn't. The keyword being "dependencies you can't satisfy". You may well publish packages that don't break dependencies; since the downstream packages will still be installable. (Yes, I know, there could be shared library etc inconsistencies if stuff like soname aren't updated properly, but we can handle that by better handling sonames or even automated shared library signatures.) Besides, what you describe as "cannot be done" is exactly what OBS does now if spawning repositories (so even by your standard, OBS is doing something wrong now). If it didn't, I'd have complained about my repos not being published at all - instead of them being published inconsistently ;-) Regards, Lars -- Architect Storage/HA SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) "Experience is the name everyone gives to their mistakes." -- Oscar Wilde -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Monday 2013-10-14 09:38, Lars Marowsky-Bree wrote:
On 2013-10-14T09:11:13, Andreas Schwab <schwab@suse.de> wrote:
Of course you shouldn't publish like this if you *know* you have dependencies you can't satisfy. "incrementally" does not imply "each package, independently and immediately". That is obvious. Which makes it obvious that you cannot publish until all builds are done.
No, it doesn't. The keyword being "dependencies you can't satisfy". You may well publish packages that don't break dependencies; since the downstream packages will still be installable.
I like the sound of that - publish whenever ($good_time && (zypper says ok)), where good_time may be 1h or whatever else so that repomd generation does not become the #1 cpu burner. That is also quite a bottleneck :/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Quoting Jan Engelhardt <jengelh@inai.de>:
No, it doesn't. The keyword being "dependencies you can't satisfy". You may well publish packages that don't break dependencies; since the downstream packages will still be installable.
I like the sound of that - publish whenever ($good_time && (zypper says ok)), where good_time may be 1h or whatever else so that repomd generation does not become the #1 cpu burner. That is also quite a bottleneck :/
We are talking odd theories here. The 'original' request was to have inter-repo dependencies always satisfiable. This is already not guaranteed within a repo (think package failure against new versions with soname change). Requesting it over project boundaries would mean OBS needs to settle completely before it can publish.. and only if everything built successfully, in order to guarantee install-ability.. I hope we won't ever consider this. Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2013-10-15T10:14:54, "Dominique Leuenberger a.k.a. Dimstar" <dimstar@opensuse.org> wrote:
We are talking odd theories here. The 'original' request was to have inter-repo dependencies always satisfiable.
Uhm. Well. Sort-of. In fact, it was a request to be able to build against the *published* versions of Factory, instead of the possibly already checked in versions. (e.g., a snapshot target, perhaps?) It then derailed in a few directions that might (or might not) help with reducing build and publisher load. Regards, Lars -- Architect Storage/HA SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) "Experience is the name everyone gives to their mistakes." -- Oscar Wilde -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 13.10.2013 12:22, Dimstar / Dominique Leuenberger wrote:
On Son, 2013-10-13 at 11:42 +0200, Lars Marowsky-Bree wrote:
On 2013-10-10T17:23:17, Andreas Schwab <schwab@suse.de> wrote:
Which I already use. There doesn't seem do be a downloadable repo? The download repos for factory always lag behind a bit, whereas small repos are published faster.
OK, I'm convinced now I must be doing tremenduously stupid here, or there's a severe bug in how Factory gets published.
By now, it's Sunday. The situation has been like this since Wednesday.
Problem: nothing provides kernel-uname-r = 3.11.4-2-default needed by ocfs2-kmp-default-1.8_k3.11.4_2-0.19.5.x86_64 Solution 1: do not install ocfs2-kmp-default-1.8_k3.11.4_2-0.19.5.x86_64 Solution 2: break ocfs2-kmp-default-1.8_k3.11.4_2-0.19.5.x86_64 by ignoring some of its dependencies
n:h:F builds against openSUSE:Factory/standard. n:h:F and Factory are the only two repositories configured on the system.
Surely the two repositories shouldn't be out-of-sync for what's now at least 4 days?
Factory was last published on Oct 8; And as long as there will be checkins happening in order to fix bugs, there will be packages building and publishing won't happen.
The repository is ~ 7000 source packages. Publishing only happens when all of them are completed. This is not a problem usually. We can publish like 4-5 builds a day, just see
osc jobhistory openSUSE:Factory _product:openSUSE-ftp-ftp-i586_x86_64 images local But what you also see: the build from 8th is still stuck in building and there lies the real problem. All other theories aside. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (9)
-
Andreas Schwab -
Dimstar / Dominique Leuenberger -
Dominique Leuenberger a.k.a. Dimstar
-
Greg Freemyer -
Jan Engelhardt -
Lars Marowsky-Bree -
Marcus Meissner -
Stephan Kulow -
Tomáš Chvátal