Skip to content

Instantly share code, notes, and snippets.

@dreamcat4
Created May 21, 2015 07:58
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
Star You must be signed in to star a gist
Save dreamcat4/f470ed87f650e6752ef8 to your computer and use it in GitHub Desktop.
# tvheadend
apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 379CE192D401AB61
add-apt-repository -y "deb https://dl.bintray.com/dreamcat4/ubuntu-stable vivid main"
add-apt-repository -y "deb https://dl.bintray.com/dreamcat4/ubuntu-stable trusty main"
apt search tvheadend
Sorting... Done
Full Text Search... Done
tvheadend/vivid,trusty 4.1.11~gd149c5b~precise amd64
Tvheadend
tvheadend-dbg/vivid,trusty 4.1.11~gd149c5b~precise amd64
Debug symbols for Tvheadend
@ProfYaffle
Copy link

My thoughts...

  1. Stable implies not changing, so shouldn't update every time the user does an apt-get update. So it should be a tagged release... anything else could be 'testing' or similar?
  2. The 'main' tag is used to search the repository for the packaging information - it means 'officially supported', I believe (versus restricted, or multiverse/non-free).
  3. Precise vs anything else - yes, same Q I just asked you on the forum - it makes no difference. AFAICT, the .deb is a product of the platform on which it was built (hence different VMs will produce different binaries), but it will then install and run on anything so long as Canonical doesn't make a radical change. For example, if they got rid of /usr in the next release, an 'old' .deb would still try to install there because that's what the rules say - then, you'd need a separate .deb, or use the rules file to decide at installation time.
  4. The vivid bit would be added automatically if you did a sudo apt-add-repository /stable - the OS will automatically append the release name from lsb_release. This is what breaks Mint - it puts 'Rebecca' at the end instead of the equivalent Ubuntu base distro.
  5. Can you insert another character - 4.1-11gd149...? or 4.1rev11 or similar?
  6. Didn't he say 4.0 = stable, 4.1 = development, 4.2 = stable, etc.?

@ProfYaffle
Copy link

where'd my comments go?

@dreamcat4
Copy link
Author

Finally, I think it is best if they appear to users like this:

# releases (git-tagged series eg `4.0.0`,`4.0.1`,`4.0.2`)
tvheadend/stable 4.0.1~trusty amd64
tvheadend/unstable 4.1.3~trusty amd64

# nightlies (commits of the two branches)
tvheadend/master 4.1.0-18~gd149c5b~trusty amd64
tvheadend/testing 4.1.0-18~gd149c5b~trusty amd64

Can't really think of any way to improve further.

@dreamcat4
Copy link
Author

$ sudo add-apt-repository -y "deb https://dl.bintray.com/dreamcat4/ubuntu master main"
$ sudo apt-get update -qqy
$ apt search tvheadend
Sorting... Done
Full Text Search... Done
tvheadend/master 3.9-2883~g4019f69~trusty amd64
  Tvheadend

tvheadend-dbg/master 3.9-2883~g4019f69~trusty amd64
  Debug symbols for Tvheadend

$ sudo apt-get install tvheadend
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages were automatically installed and are no longer required:
  linux-headers-3.19.0-15 linux-headers-3.19.0-15-generic linux-image-3.19.0-15-generic linux-image-extra-3.19.0-15-generic
Use 'apt-get autoremove' to remove them.
The following extra packages will be installed:
  libdvbcsa1 liburiparser1
The following NEW packages will be installed
  libdvbcsa1 liburiparser1 tvheadend
0 to upgrade, 3 to newly install, 0 to remove and 18 not to upgrade.
Need to get 9,547 kB of archives.
After this operation, 25.0 MB of additional disk space will be used.
Do you want to continue? [Y/n] Y
$ apt search tvheadend
Sorting... Done
Full Text Search... Done
tvheadend/master,now 3.9-2883~g4019f69~trusty amd64 [installed]
  Tvheadend
$ tvheadend --version
tvheadend: error while loading shared libraries: libdvben50221.so: cannot open shared object file: No such file or directory
$ sudo apt-get install dvb-apps
$ tvheadend --version
tvheadend: version 3.9-2883~g4019f69

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment