Project

General

Profile

Actions

Bug #6335

closed

osmo-epdg's rebar.lock refers to a non-exising osmo_gsup commit

Added by osmith about 1 month ago. Updated about 1 month ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
-
Start date:
01/19/2024
Due date:
% Done:

100%

Spec Reference:

Description

The Osmocom_OBS_nightly job failed with:

===> Failed to fetch and copy dep: {git,
                                  "https://gitea.osmocom.org/erlang/osmo_gsup",
                                  {ref,
                                      "e23f118e6e8f7ee1247db34e4cb79e4cecdb0947"}}

(Osmo-repo-install tests fail as consequence of the slightly inconsistent nightly repo.)

The commit doesn't exist in osmo_gsup. A regression from https://gerrit.osmocom.org/c/erlang/osmo-epdg/+/34804.

pespin: did you maybe not push the commit yet, or should it refer to another commit?

Actions #1

Updated by osmith about 1 month ago

Actually the patch is from October. So I guess the commit used to exist until yesterday.

Actions #2

Updated by pespin about 1 month ago

It was probably pointing to my branch which I removed yesterday. I'll fix it now.

Actions #3

Updated by pespin about 1 month ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

Fixed by:
https://gerrit.osmocom.org/c/erlang/osmo-epdg/+/35621 Update osmo_gsup dependency in rebar.config and update rebar.lock
https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/35604 GSUP_Types: Add missing message_class to EPDGTunnel* messages

Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)