Skip to content

Commit

Permalink
fixup: LIME_RELEASE for upgrades
Browse files Browse the repository at this point in the history
Testing and master are two different branches and LibreMesh renames it's
VERSION based on this branch. Therefore both testing/unstable would
always request a "master" version from the server. Now it's separated.
  • Loading branch information
aparcar committed Mar 7, 2019
1 parent 5d4ba5d commit 90efbb3
Show file tree
Hide file tree
Showing 3 changed files with 4 additions and 3 deletions.
2 changes: 1 addition & 1 deletion asu/utils/distributions/lime/distro_config.yml
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ latest: "testing"

versions:
- "testing"
- "unstable"
- "master"
- "aparcar"

active_targets:
Expand Down
Original file line number Diff line number Diff line change
@@ -1,8 +1,9 @@
parent_distro: openwrt
parent_version: snapshots
snapshots: True
version_alias: unstable development
version_description: >
LibreMesh development branch on OpenWrt development branch
LibreMesh master branch on OpenWrt development branch
repos: |
src/gz openwrt_core http://downloads.openwrt.org/snapshots/targets/{{ target }}/packages
src/gz openwrt_base http://downloads.openwrt.org/snapshots/packages/{{ pkg_arch }}/base
Expand Down
2 changes: 1 addition & 1 deletion asu/utils/distributions/lime/testing.yml
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,6 @@ repos: |
src/gz openwrt_packages http://downloads.openwrt.org/releases/{{ ib_version }}/packages/{{ pkg_arch }}/packages
src/gz openwrt_telephony http://downloads.openwrt.org/releases/{{ ib_version }}/packages/{{ pkg_arch }}/telephony
src imagebuilder file:packages
src/gz libremesh http://chef.libremesh.org/snapshots/packages/
src/gz libremesh https://snapshots.libremesh.org/branches/testing/
src/gz lm_profiles http://chef.libremesh.org/network-profiles/
src/gz libremap http://repo.libremesh.org/releases/17.06/packages/{{ pkg_arch }}/libremap

0 comments on commit 90efbb3

Please sign in to comment.