Add Breaks/Conflicts/Replaces to debian control #79
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
As discussed on Discord a while ago, adding Breaks/Conflicts/Replaces entries against camera-streamer (<< 0.2) allows for a smooth migration from the camera-streamer package built for OctoPi to camera-streamer-raspi, through a transitional camera-streamer version 0.2 on OctoPi's side. An upgrade of camera-streamer from OctoPrint's apt repo will pull in an updated transitional camera-streamer package version 0.2 that depends on camera-streamer-raspi. For that to install flawlessly in all cases, it needs to be installed *before* the camera-streamer-raspi dependency (as some files between that and the former camera-streamer package overlap). By declaring Breaks/Conflicts/Replaces relationships on camera-streamer-raspi this is ensured.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As discussed on Discord a while ago, adding Breaks/Conflicts/Replaces entries against camera-streamer (<< 0.2) allows for a smooth migration from the camera-streamer package built for OctoPi to camera-streamer-raspi, through a transitional camera-streamer version 0.2 on OctoPi's side.
An upgrade of camera-streamer from OctoPrint's apt repo will pull in an updated transitional camera-streamer package version 0.2 that depends on camera-streamer-raspi. For that to install flawlessly in all cases, it needs to be installed before the camera-streamer-raspi dependency
(as some files between that and the former camera-streamer package overlap). By declaring Breaks/Conflicts/Replaces relationships on camera-streamer-raspi this is ensured.
I've manually adjusted
camera-streamer-raspiand created a version0.2.1~bullseye-1to test this on a private apt repo and in all my test scenarios upgrades work with these changes:apt upgradeon a system that already hascamera-streamer0.1 pulls in the transitional packagecamera-streamer0.2, which depends oncamera-streamer-raspi, so that gets installed as well. apt does the install order the correct way only with the the additions in this PRapt install camera-streamer-raspion a system that already hascamera-streamer0.1 upgrades bothcamera-streamerto the transitional 0.2 and installscamera-streamer-raspiapt install camera-streamer-raspion a system that does NOT already havecamera-streamerinstalled (so, OctoPi-UpToDate builds with the new camera stack going forward) only installcamera-streamer-raspi