[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #6749 [Tor Sysadmin Team]: Git repo account for hiviah - rpm building
#6749: Git repo account for hiviah - rpm building
----------------------------------+-----------------------------------------
Reporter: hiviah | Owner:
Type: task | Status: new
Priority: normal | Milestone:
Component: Tor Sysadmin Team | Version:
Resolution: | Keywords:
Parent: | Points:
Actualpoints: |
----------------------------------+-----------------------------------------
Comment(by hiviah):
Replying to [comment:2 nickm]:
> Hiviah, would it work if you got write permissions on rpm/tor.git, and a
new hiviah/tor-rpm.git for staging ?
That would work. I'd do it similarly as the debian packaging goes:
{{{
21:28 < marlowe> which brings up the issue of if there is a change in the
spec
file without a planned release of tor
21:28 < Sebastian> that was what I initially suggested as probably good
enough,
but it has some drawbacks, for example, you cannot write a spec file
for a
certain tagged version of Tor after it has already been tagged.
21:28 < marlowe> means an out of band release
21:29 < marlowe> I think the debian model might work.
21:29 < marlowe> it would just mean moving the spec file down a directory
and
adjusting accordingly
21:29 < Sebastian> The way weasel does it for Debian is that he merges the
new
release into his repository, makes the necessary changes (at lest
updating
the changelog, sometimes patches too), then tags his own release
}}}
The hiviah/tor-rpm.git would track the build scripts and docs used on
feddei.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/6749#comment:6>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs