Upgrade from Deluge Dev to Deluge Repo Bug

Bugs
#1

Unable to access Repo for Deluge due to PPA not being added in

W: GPG error: http://ppa.launchpad.net/deluge-team/ppa/ubuntu precise InRelease: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY C5E6A5ED249AD24C
W: The repository ‘http://ppa.launchpad.net/deluge-team/ppa/ubuntu precise InRelease’ is not signed.
N: Data from such a repository can’t be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.

sudo add-apt-repository ppa:deluge-team/ppa corrects this

#2

I’ll need to check in on this. The issue with this is then you have people that want to stay on dev branch via git. You add in the apt repositories and next thing apt is upgrading their instance without them wanting to. I think it’s a bit more delicate than that in accordance to catering to the various user levels. That said, I don’t think this is a bug so much… but I will gladly accept a motion of challenge on my thoughts… I’m all ears.

#3

I had this issue just upgrading to 1.3.14, after the repo selection on the install script.

Maybe there could be two separate trees? IE:

1 -Deluge PPA/repo

  • -Latest version
  • -1.3.13
  • -1.3.12

2-Dev versions (to compile)

  • -libtorrent v x.x.x
  • -libtorrent v x.x.x

I’m not sure how feasible that is, but in my mind, the first tree would add the PPA, the second would not. The main issue is if a user wants to switch from 1 > 2.