diff options
| author | Harald Welte <laforge@gnumonks.org> | 2017-10-06 10:09:45 +0800 |
|---|---|---|
| committer | Harald Welte <laforge@gnumonks.org> | 2017-10-06 10:13:09 +0800 |
| commit | 973dca99174aae0f6a7cced8074481a96d7255d0 (patch) | |
| tree | f16d42e738f84baf87d631456c72d5b3e25fc491 | |
| parent | 418e728fc24ef4abba0f0851150d77976582d109 (diff) | |
osmocom:nitb-split:nightly Re-introduce osmo-sgsn + osmo-ggsn
For some strange reason, in commit
8e9fe0808072d3f5eca8b4c6fac9865a52c9beb3, the osmocom:nitb-split:nightly
package feed was rendered to use old packages for sgsn+ggsn, rather than
current ones by removing the "osc upload" from this script, but still
leaving the packages in OBS at
https://build.opensuse.org/project/show/network:osmocom:nitb-split:nightly
Removing them half (only in osmo-ci but not at OBS) is a bad idea, as
it leaves people with old packages who actually want to use nightly
builds.
Also, removing the packages in general is a very bad idea. People
are *either* using osmocom:nightly, *or* they are using the
osmocom:nitb-split:nightly feed, but not both. So we cannot remove
any packages from the osmocom:nitb-split:nightly feed until we have
introduced all those packages to osmocom:nightly *and* we have given
people sufficient notice to update!
Change-Id: I5c091127d92a4b4beb7355e16abd9788fa3b9fe5
| -rwxr-xr-x | scripts/osmocom-nightly-nitb-split.sh | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/scripts/osmocom-nightly-nitb-split.sh b/scripts/osmocom-nightly-nitb-split.sh index 4484214..3b547bf 100755 --- a/scripts/osmocom-nightly-nitb-split.sh +++ b/scripts/osmocom-nightly-nitb-split.sh @@ -90,9 +90,11 @@ build_osmocom() { checkout libasn1c checkout osmo-iuh checkout osmo-hlr + checkout osmo-ggsn checkout osmo-mgw checkout osmo-bsc checkout osmo-msc + checkout osmo-sgsn build libosmocore build libosmo-abis @@ -102,9 +104,11 @@ build_osmocom() { build libasn1c build osmo-iuh build osmo-hlr + build osmo-ggsn build osmo-mgw build osmo-bsc build osmo-msc + build osmo-sgsn post } |