add arm to the official tor deb repository

added component::archived/nyx owner::atagar priority::medium reporter::toruser32 resolution::wontfix severity::normal status::closed type::enhancement labels

"the regular arm who do not" that should read: "the regular arm user who do not"

Trac:
Username: toruser32

I don't run the repo, but since its original goal was to be able to provide backports to stable (and older) versions of Debian, this could be a good idea if Damian wishes to provide regular updates to Debian stable users.

In terms of providing access, I believe all weasel has to do is add Damian's key to the keyring, at which point Damian can upload directly to the repo, after some instruction from me or weasel. So, questions to answer before proceeding:

Does Damian want to provide regular updates to Debian stable users? (I am going to suggest 'yes' for this, since a large amount of our relays are running Debian stable.)
If the answer to 1) is yes, does Damian want to be able to upload to the deb.tpo servers?

3a. If the answer to 2) is no, figure out if there's anyone willing to take ownership of that aspect of arm releases.

3b. If the answer to 2) is also yes, assign to weasel and ask for upload access or comments about whether arm should be "allowed". (I also suggest 'yes' for this one, since it's already in Debian.)

Thanks Erinn!

If this would be helpful to users then certainly.
Up to weasel. Currently I just make the debs and send them to him. I'm happy to upload them as part of my deb release process or leave that up to weasel.

Trac:
Owner: atagar to weasel
Status: new to assigned

If you want to build tor-arm and python-torctl for the 9 different suites (the debians and ubuntus) we can get them added to the archive I suppose.

Or, if you think a single binary package will work for all users, we could make a tor-arm repository for just your package.

Whichever you think is best. A single binary package will work fine for all users.

From an user point of view, adding arm to the tor repositories along with vidalia and the actual tor binary feels better - one repo to add to sources.list, and only one key to import.

Trac:
Username: toruser32

Trac:
Cc: N/A to tom+tor-trac@mozilla.com

Replying to erinn:

In terms of providing access, I believe all weasel has to do is add Damian's key to the keyring, at which point Damian can upload directly to the repo, after some instruction from me or weasel.

Weasel, could you add Atagar's key to the keyring so that he can start adding arm .debs to the repository? Is there anything that I can do help getting arm into the repository?

if you want to use the same suite as tor, I need builds for all of them. Once you have them we can upload them.

If you want a new suites you need to say that.

Trac:
Owner: weasel to atagar

I'm not really sure what you mean (this package is platform independent and both the control and generated dsc say so). However, this is probably a moot point. Dererk is, of course, far more knowledgeable about deb packaging than me and has expressed an interest in taking care of the arm deb.tpo package.

This is pending ticket 4053. Barring further hotfixes I'll be sending him a deb for the 1.4.4.1 release this weekend, which will hopefully get this ball rolling.

I've explained on more than one occassion that we do not upload just .debs and that we need appropriately formated .changes files (including appropriate changelogs in the source).

anyway, I'll just close this ticket if it's moot.

Trac:
Resolution: N/A to invalid
Status: assigned to closed

The ticket is not moot, but my understanding of the need for rebuilds may be. Please don't close until the issue has been resolved.

I've explained on more than one occassion that we do not upload just .debs

From previous discussions I thought that the only thing you cared about from me was the dsc file. Guess I was wrong. This seems to be annoying you so don't worry about explaining further - I'll figure it out if something more is needed from me.

Trac:
Status: closed to reopened
Resolution: invalid to N/A

The binaries/src pkgs are about to be uploaded, hopefully we will having them during this week.

Current suites are: lenny lucid maverick natty oneiric precise squeeze wheezy sid

(sorry about delays)

Files have been already uploaded and mirrored.

Trac:
Status: reopened to closed
Resolution: N/A to fixed

The tor-arm package is missing from the following distributions in the Official Tor Repositories: Debian: jessie and/or testing sid and/or unstable Ubuntu: trusty utopic

See the following files to confirm: https://deb.torproject.org/torproject.org/dists/jessie/main/binary-amd64/Packages https://deb.torproject.org/torproject.org/dists/sid/main/binary-amd64/Packages https://deb.torproject.org/torproject.org/dists/utopic/main/binary-amd64/Packages https://deb.torproject.org/torproject.org/dists/trusty/main/binary-amd64/Packages

This bug is more significant for Ubuntu administrators if they are not using the universe repository. And given how Ubuntu's universe repository doesn't receive security support from Canonical, a tor relay administrator doesn't need to run packages in universe.

If the admin is using Debian, or Ubuntu's universe repository this bug doesn't matter right now as it appears the most recent tor-arm package is available the distributions noted above. Note the most recent package was released more than 2 years ago, 22 May 2012.

Trac:
Username: cp
Status: closed to reopened
Resolution: fixed to N/A

Hmmm. Dererk's packaging Stem for Debian and will likely do so for Nyx as well. Nyx will only be packaged where Stem's available and Stem doesn't seem to be there.

This begs the question "should Stem be in deb.torproject.org?'. If you'd care to push for that then feel free to reopen and we'll get Dererk's thoughts.

Trac:
Status: reopened to closed
Reviewer: N/A to N/A
Sponsor: N/A to N/A
Resolution: N/A to wontfix
Severity: N/A to Normal

closed

add arm to the official tor deb repository

Child items ...

Activity