Project

General

Profile

Actions

Feature #5319

closed

Add osmo-bts meta-package depending on all osmo-bts-*

Added by laforge over 2 years ago. Updated about 2 years ago.

Status:
Resolved
Priority:
Low
Assignee:
Category:
-
Target version:
-
Start date:
11/22/2021
Due date:
% Done:

100%

Spec Reference:

Description

23:33 < fixeria> gosh, it literally took me ~1 to figure out why doing `apt install osmo-bts` in 
                 our Debian based docker images suggests to install an ancient osmo-bts version 
                 0.8.1-2
23:34 < fixeria> as it turns out, there is no package named 'osmo-bts' in our openSUSE repos;  we 
                 have osmo-bts-{trx,sysmo,...}
23:41 < fixeria> I find this confusing.  Maybe we should add a meta package depending on osmo-bts-*?

I think it is a good idea to avoid users running into strange problems on Debian or Debian-based distributions like Ubuntu.

Actions #1

Updated by laforge over 2 years ago

In general, we should try to make sure our package names don't diverge of those of upstream - or if they do, that we "override" those upsteam packages with virtual packages, or "conflicts" or whatever.

Actions #2

Updated by osmith over 2 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100
Actions #3

Updated by osmith over 2 years ago

  • Status changed from Resolved to In Progress
  • % Done changed from 100 to 90

(This is not merged yet, should not have been closed...)

EDIT: https://gerrit.osmocom.org/c/osmo-bts/+/26424

Ah, it was closed because I pushed it to a branch osmith/meta-pkg for testing on a separate OBS namespace. Maybe redmine needs to be configured to only close issues if commits in master have the Closes: tag in commit messages?

Actions #4

Updated by osmith over 2 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 90 to 100
Actions #5

Updated by fixeria about 2 years ago

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

Hi Oliver,

unfortunately ancient osmo-bts is still the case for the 'latest' feed. Reopening this ticket.

$ docker run -it --rm debian:bullseye
root@d03421395c1e:/# apt update
root@d03421395c1e:/# apt install -y wget gnupg2
root@d03421395c1e:/# wget https://download.opensuse.org/repositories/network:/osmocom:/latest/Debian_11/Release.key -O - | apt-key add
root@d03421395c1e:/# echo "deb https://download.opensuse.org/repositories/network:/osmocom:/latest/Debian_11/ ./" > /etc/apt/sources.list.d/osmocom-latest.list
root@d03421395c1e:/# apt update

root@d03421395c1e:/# apt show osmo-bts
Package: osmo-bts
Version: 1.2.2+dfsg1-2
Priority: optional
Section: net
Maintainer: Debian Mobcom Maintainers <Debian-mobcom-maintainers@lists.alioth.debian.org>
Installed-Size: 1014 kB
Suggests: osmo-bsc
Homepage: http://openbsc.osmocom.org/trac/wiki/OsmoBTS
Download-Size: 190 kB
APT-Sources: http://deb.debian.org/debian bullseye/main amd64 Packages
Description: Base Transceiver Station for GSM
Actions #6

Updated by osmith about 2 years ago

  • Status changed from New to In Progress
  • Assignee changed from osmith to fixeria

The meta-package has been introduced in master, since then no release has been tagged. If it makes sense, I could backport the change. What do you think?

Actions #7

Updated by fixeria about 2 years ago

  • Assignee changed from fixeria to osmith

If it makes sense, I could backport the change. What do you think?

I think it would be great to have it back-ported. Thanks!

Actions #9

Updated by osmith about 2 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 90 to 100
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)