How often is src.opensuse.org updated?
For systemd's CI, I'm trying to use https://src.opensuse.org/rpm/systemd as a git submodule for the opensuse packaging sources. However, it seems that changes to Factory propagate rather slowly to src.opensuse.org? e.g. the latest revision (https://build.opensuse.org/package/revisions/openSUSE:Factory/systemd) was accepted 5 days ago at the time of writing this and still isn't in https://src.opensuse.org/rpm/systemd/commits/branch/factory. This makes it very painful to try to do CI upstream for the opensuse systemd packaging sources as any fix I contribute to the packaging takes a very long time to become available on src.opensuse.org. Cheers, Daan De Meyer
On Mon, Mar 25, 2024 at 7:37 AM Daan De Meyer <daan.j.demeyer@gmail.com> wrote:
For systemd's CI, I'm trying to use https://src.opensuse.org/rpm/systemd as a git submodule for the opensuse packaging sources. However, it seems that changes to Factory propagate rather slowly to src.opensuse.org? e.g. the latest revision (https://build.opensuse.org/package/revisions/openSUSE:Factory/systemd) was accepted 5 days ago at the time of writing this and still isn't in https://src.opensuse.org/rpm/systemd/commits/branch/factory. This makes it very painful to try to do CI upstream for the opensuse systemd packaging sources as any fix I contribute to the packaging takes a very long time to become available on src.opensuse.org.
Looks like it propagated to code.opensuse.org though: https://code.opensuse.org/package/systemd/commits/master -- 真実はいつも一つ!/ Always, there's only one truth!
Looks like it propagated to code.opensuse.org though: https://code.opensuse.org/package/systemd/commits/master
The issue with code.opensuse.org is that it is backed by pagure which does not seem to support git's "advertised references" feature causing "git clone https://github.com/systemd/systemd.git --no-tags --depth 1 --recurse-submodules --shallow-submodules" to fail with the following error when the submodule does not track the latest commit on the systemd master branch on code.opensuse.org: """ error: Server does not allow request for unadvertised object 37aca188c2ef606319217b30ff8b0c66df6c60f1 fatal: Fetched in submodule path 'pkg/opensuse', but it did not contain 37aca188c2ef606319217b30ff8b0c66df6c60f1. Direct fetching of that commit failed. """ src.opensuse.org is backed by gitea which does support this feature. Normally I'd just do the git clone without --depth=1 and --shallow-submodules but the problem is that it's dependabot doing the clone in this case and I can't make it do non shallow clones so we need to use a git forge that supports advertised references which in this case means using src.opensuse.org. Cheers, Daan On Mon, 25 Mar 2024 at 13:11, Neal Gompa <ngompa13@gmail.com> wrote:
On Mon, Mar 25, 2024 at 7:37 AM Daan De Meyer <daan.j.demeyer@gmail.com> wrote:
For systemd's CI, I'm trying to use https://src.opensuse.org/rpm/systemd as a git submodule for the opensuse packaging sources. However, it seems that changes to Factory propagate rather slowly to src.opensuse.org? e.g. the latest revision (https://build.opensuse.org/package/revisions/openSUSE:Factory/systemd) was accepted 5 days ago at the time of writing this and still isn't in https://src.opensuse.org/rpm/systemd/commits/branch/factory. This makes it very painful to try to do CI upstream for the opensuse systemd packaging sources as any fix I contribute to the packaging takes a very long time to become available on src.opensuse.org.
Looks like it propagated to code.opensuse.org though: https://code.opensuse.org/package/systemd/commits/master
-- 真実はいつも一つ!/ Always, there's only one truth!
On Mon, Mar 25, 2024 at 9:05 AM Daan De Meyer <daan.j.demeyer@gmail.com> wrote:
Looks like it propagated to code.opensuse.org though: https://code.opensuse.org/package/systemd/commits/master
The issue with code.opensuse.org is that it is backed by pagure which does not seem to support git's "advertised references" feature causing "git clone https://github.com/systemd/systemd.git --no-tags --depth 1 --recurse-submodules --shallow-submodules" to fail with the following error when the submodule does not track the latest commit on the systemd master branch on code.opensuse.org:
""" error: Server does not allow request for unadvertised object 37aca188c2ef606319217b30ff8b0c66df6c60f1 fatal: Fetched in submodule path 'pkg/opensuse', but it did not contain 37aca188c2ef606319217b30ff8b0c66df6c60f1. Direct fetching of that commit failed. """
We don't do anything special here, our repositories are exposed through pygit2, which is backed by libgit2. If there's some configuration we need to be doing for this, please tell us in an upstream pagure ticket: https://pagure.io/pagure -- 真実はいつも一つ!/ Always, there's only one truth!
We don't do anything special here, our repositories are exposed through pygit2, which is backed by libgit2. If there's some configuration we need to be doing for this, please tell us in an upstream pagure ticket: https://pagure.io/pagure
I opened https://pagure.io/pagure/issue/5453 but I have no clue about what needs to be configured to make this work as I'm not an expert on git internals. Cheers, Daan On Mon, 25 Mar 2024 at 14:26, Neal Gompa <ngompa13@gmail.com> wrote:
On Mon, Mar 25, 2024 at 9:05 AM Daan De Meyer <daan.j.demeyer@gmail.com> wrote:
Looks like it propagated to code.opensuse.org though: https://code.opensuse.org/package/systemd/commits/master
The issue with code.opensuse.org is that it is backed by pagure which does not seem to support git's "advertised references" feature causing "git clone https://github.com/systemd/systemd.git --no-tags --depth 1 --recurse-submodules --shallow-submodules" to fail with the following error when the submodule does not track the latest commit on the systemd master branch on code.opensuse.org:
""" error: Server does not allow request for unadvertised object 37aca188c2ef606319217b30ff8b0c66df6c60f1 fatal: Fetched in submodule path 'pkg/opensuse', but it did not contain 37aca188c2ef606319217b30ff8b0c66df6c60f1. Direct fetching of that commit failed. """
We don't do anything special here, our repositories are exposed through pygit2, which is backed by libgit2. If there's some configuration we need to be doing for this, please tell us in an upstream pagure ticket: https://pagure.io/pagure
-- 真実はいつも一つ!/ Always, there's only one truth!
On Mär 25 2024, Daan De Meyer wrote:
We don't do anything special here, our repositories are exposed through pygit2, which is backed by libgit2. If there's some configuration we need to be doing for this, please tell us in an upstream pagure ticket: https://pagure.io/pagure
I opened https://pagure.io/pagure/issue/5453 but I have no clue about what needs to be configured to make this work as I'm not an expert on git internals.
uploadpack.allowTipSHA1InWant uploadpack.allowReachableSHA1InWant uploadpack.allowAnySHA1InWant -- 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."
participants (3)
-
Andreas Schwab
-
Daan De Meyer
-
Neal Gompa