Project

General

Profile

Bug #2640

Debian nightly packages should conflict with debian latest packages

Added by laforge 10 months ago. Updated 3 months ago.

Status:
New
Priority:
Normal
Assignee:
Target version:
-
Start date:
11/15/2017
Due date:
% Done:

0%

Estimated time:
Spec Reference:

Description

If a user first uses packages from the network:osmocom:nightly feed, and then switches to the network:osmocom:latest feed, we would ideally want a situation where the "nightly" packages conflict with the "latest" ones, as the version numbers and dependencies of "nightly" will not properly work out. This is due to the fact that the source code version numbers are not incremented/tagged on a daily/nightly basis, but only once we tag a new version (which will then create new "latest" packages).

Yes, we know, a skilled user will understand there's a problem and will make sure to properly uninstall any "nightly" packages before installing "latest".

The same should be true for "nightly" vs. the official packages in upstream Debian/Ubuntu.

It's not yet clear how we can achieve this, but it would be great to have it in place. When "latest" or "official" packages are install, all "nightly" packages should be removed due to a conflict in dpkg packaging information.

History

#1 Updated by laforge 3 months ago

  • Assignee changed from sysmocom to lynxis

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)