Actions
Bug #4934
closed"latest" feed contains osmo-msc 1.6.3 yet no tag is in the git repo?
Start date:
01/06/2021
Due date:
% Done:
0%
Resolution:
Spec Reference:
Description
https://build.opensuse.org/package/show/network:osmocom:latest/osmo-msc lists a build for 1.6.3, but the latet tag in the git repository is 1.6.2 - something is odd there.
Updated by neels about 3 years ago
looking in my osmo-msc.git clone, i do see a 1.6.3 tag on 753572482148eb08491312844e173be5767ee6cc.
commit 753572482148eb08491312844e173be5767ee6cc Refs: <1.6.3> Author: Pau Espin Pedrol <pespin@sysmocom.de> AuthorDate: Wed Sep 9 16:29:49 2020 +0200 Commit: Pau Espin Pedrol <pespin@sysmocom.de> CommitDate: Wed Sep 9 16:29:49 2020 +0200 Bump version: 1.6.2.1-602c0 → 1.6.3 Change-Id: I96bfaa516b2443c0349e73dae674b4c01a19dd72 --- debian/changelog | 7 +++++++ 1 file changed, 7 insertions(+)
Updated by neels about 3 years ago
- Status changed from New to Rejected
Updated by pespin about 3 years ago
$ git push origin 1.6.3 Everything up-to-date
It was already there when I tried pushing it today.
Updated by laforge about 3 years ago
Interestingly I am not getting this tag during git fetch
~/projects/git/osmo-msc > git fetch gerrit ~/projects/git/osmo-msc > git tag | grep 1.6 1.6.0 1.6.1 1.6.2 fairwaves/1.6.1-fw.1
I'd have had to do an explicit git fetch --tags
to get the tag. In all other
repositories, and also in osmo-msc.git, this was never required before. Weird.
Updated by pespin about 3 years ago
I remember having to pass --tags in order to get tags in the past, so it's not something new for me. Maybe in older git versions the behavior was different?
Actions