Change from unstable to stable repository
Added by Josu Lazkano over 7 years ago
Hello all,
I read that the 4.2 version is released, thanks all the developers for the great software.
I actually have this repository:
deb https://dl.bintray.com/tvheadend/deb jessie unstable
I want to change to stable 4.2 repository, which is the correct way? How could I change the "/etc/apt/sources.list" file?
Kind regards.
Replies (10)
RE: Change from unstable to stable repository - Added by Jannik Schäfer over 7 years ago
I switched from unstable 4.1.2545 to stable 4.2 on Ubuntu 16.04 yesterday.
Following the download wiki I changed the line
deb https://dl.bintray.com/tvheadend/deb xenial unstableto
deb https://dl.bintray.com/tvheadend/deb xenial stable-4.2This worked for me without any problems, but keep in mind, that I was already using the latest unstable version (4.1.2545).
In your case you would probably have to change the line
deb https://dl.bintray.com/tvheadend/deb jessie unstableto
deb https://dl.bintray.com/tvheadend/deb jessie stable-4.2for the stable 4.2 builds, or:
deb https://dl.bintray.com/tvheadend/deb jessie release-4.2for the release 4.2 builds.
After that I just ran "sudo apt update" and "sudo apt upgrade" to update my TVheadend server on Ubuntu 16.04.
It automatically started without any further configuration needed.
RE: Change from unstable to stable repository - Added by Josu Lazkano over 7 years ago
Thanks!
But what is the difference between release-4.2 and stable-4.2?
This is what say in the AptRepository page:
- release-4.2 - The latest version marked as release (like 4.2.2).
- stable-4.2 - The latest official / stable code including changes between releases (like 4.2.2-10~gHASH).
But I don't know which is the difference.
Kind regards.
RE: Change from unstable to stable repository - Added by Mark Clarkstone over 7 years ago
Josu Lazkano wrote:
Thanks!
But what is the difference between release-4.2 and stable-4.2?
This is what say in the AptRepository page:
- release-4.2 - The latest version marked as release (like 4.2.2).
- stable-4.2 - The latest official / stable code including changes between releases (like 4.2.2-10~gHASH).
But I don't know which is the difference.
"release" means no changes to the code until a new revision, e.g. 4.2.2 (current is 4.2.1).
"stable" means builds that have changes between the current release build (4.2.1) & the next (4.2.2), so all changes between 4.2.1 & 4.2.2 are included.
Kind regards.
RE: Change from unstable to stable repository - Added by Josu Lazkano over 7 years ago
Thanks Mark,
I change from "unstable" to "stable-4.2" and now I have "4.2.1-1~g658ddd6" versión, so great!
The stable versión is going to update frecuently? Is this brach secure for daily use?
Kind regards.
RE: Change from unstable to stable repository - Added by Mark Clarkstone over 7 years ago
Josu Lazkano wrote:
Thanks Mark,
I change from "unstable" to "stable-4.2" and now I have "4.2.1-1~g658ddd6" versión, so great!
The stable versión is going to update frecuently? Is this brach secure for daily use?
It should be yes. Only commits for new releases will occur and even then it's usually just important fixes.
Kind regards.
RE: Change from unstable to stable repository - Added by Joe User over 7 years ago
Mark Clarkstone wrote:
"release" means no changes to the code until a new revision, e.g. 4.2.2 (current is 4.2.1).
"stable" means builds that have changes between the current release build (4.2.1) & the next (4.2.2), so all changes between 4.2.1 & 4.2.2 are included.
But all the changes in the last few days have been made on the "release/4.2" branch on github, and no updates have been made to the master branch (which should be the "unstable".)
Maybe github needs to be updated to reflect the above description - maybe add a "stable/4.2" branch??
As it stands now, the "master" branch on github is equal to the "4.2 release", and the "release/4.2" branch is the "4.2 stable" version. (According to the above description.)
Also, as a side note, is it still necessary to have the htsp/8-21 branches?
RE: Change from unstable to stable repository - Added by Mark Clarkstone over 7 years ago
Joe User wrote:
Mark Clarkstone wrote:
"release" means no changes to the code until a new revision, e.g. 4.2.2 (current is 4.2.1).
"stable" means builds that have changes between the current release build (4.2.1) & the next (4.2.2), so all changes between 4.2.1 & 4.2.2 are included.But all the changes in the last few days have been made on the "release/4.2" branch on github, and no updates have been made to the master branch (which should be the "unstable".)
Unstable is now 4.3..
No new packages will be in release-4.2 until 4.2.2 is released, replacing 4.2.1. All changes between 4.2.1 til 4.2.2 will be in the stable-4.2 repo.
Maybe github needs to be updated to reflect the above description - maybe add a "stable/4.2" branch??
As it stands now, the "master" branch on github is equal to the "4.2 release", and the "release/4.2" branch is the "4.2 stable" version. (According to the above description.)
Also, as a side note, is it still necessary to have the htsp/8-21 branches?
RE: Change from unstable to stable repository - Added by Joe User over 7 years ago
I understand that, but I am talking about what is on github. (The actual source code...)
RE: Change from unstable to stable repository - Added by Mark Clarkstone over 7 years ago
Joe User wrote:
I understand that, but I am talking about what is on github. (The actual source code...)
Yes, I see what you mean. If you want, you can open a issue & ask for it to be fixed :p