Tor RPM .spec file missing in 0.2.4.10-alpha

Here are some patches to re-add the rpm spec file. Seems to build and work fine on Fedora 18

changed milestone to %Tor: 0.2.4.x-final

added component::core tor/tor milestone::Tor: 0.2.4.x-final priority::medium resolution::wontfix status::closed tor-relay type::defect version::tor 0.2.4.10-alpha labels

Trac:
0001-Re-Add-tor.spec.in-for-building-RPM.patch

Adds the rpm spec file tor.spec.in from Tor 0.2.3.25

Trac:
0002-Add-doc-TODO-to-included-files.patch

Update doc/include.am to include doc/TODO

We seem to have taken them out intentionally with 43c86bbc70afb585a71948d8c36b26160d8039e0. What does Ondrej think about putting them back in?

Trac:
Milestone: N/A to Tor: 0.2.4.x-final
Keywords: N/A deleted, tor-relay added

I don't mind putting them back. Currently there's a parallel repo used for RPM builds, where main Tor code is merged. I was planning to create F18 packages after upgrading feddei to F18 this week (missed the date F18 went stable after many delays).

Suggestions:

1. Use tor.spec.in from my repo, this one is for 0.2.4.x, another one for 0.2.3.x stable
2. Check changes done to Makefile.am, especially the dist-rpm target, they are related to EL5. I'd like to have one tor.spec.in that works for latest two EL and two latest Fedoras (EL5, EL6, F17 and F18 currently)
3. We're currently debating maintainership of Tor Fedora packages with Paul Wouters and Jamie Nguyen.

Whoops, I just discovered that conversation. I can confirm that hiviah's spec file works on FC18, and contains an up-to-date changelog.

I pointed Jamie and Paul to this ticket. Quick summary from mails for desired changes to tor.spec.in and startup scripts:

• Remove stuff for unused distros (Mandriva, SUSE, RedFlag...)
• Remove the permission setting in %__mkdir_p -m and use the %attr already present for /var/{lib,log,run}/tor
• Remove /var/tmp/tor (not packaged)
• Use --defaults-torrc instead of hardcoded values and SIGINT with timeout instead of SIGTERM/SIGKILL in startup scripts (cf. Debian scripts)

I'll do whatever if somebody points me to something looking like a consensus

nickm: sorry for the confusion, but I think the tor.spec.in shouldn't be merged into 0.2.4.x or 0.2.5.x. Keep the git repo as is. (Neither Paul Wouters nor Jamie Nguyen added any opinion.)

Details:

Today, I've built 0.2.4.11 RPM packages and cleaned up the historical SUSE, Madrake and RedFlag stuff from tor.spec.in. Making tor.spec.in an official part of the repo would mean that somebody would have to keep track of whatever changes that happened to the tor.spec.in file in my repo.

On the other hand, I don't expect the tor.spec.in will be changing much soon - mostly just changelog entries.

So if you want, merge the last tor.spec.in from rpm-release-0.2.4 branch that has gone through cleanup.

I am fine with maintaining the spec file in the tor-rpm repository. Just talked to aagbsn and he seems to agree. Closing this.

Trac:
Resolution: N/A to wontfix
Status: new to closed

closed

moved to tpo/core/tor#8395 (closed)