Re: [Tails-dev] Package Tor Monitor
Hi everyone, > I would co-maintain this with nodens and if anyone on the list is > interested.. i can do some handholding. I have been lurking on this ML for a while so I might just break my silence right now. I have done some Debian packaging in the Debian Med team, for now mainly working on bioinformatics software [1] but I would like to broaden my focus a bit. As I've always been interested in privacy enhancing technologies as well, I would like to help out with some additional packaging work if I have the time and given some priority advice (haven't looked at the bugs in pkg-anonymity-tools in detail yet). I'm a DM so you hopefully won't need to sponsor every single update after awhile ;) Long story short, there’s a first version of a tor-monitor package in: https://github.com/satta/tor-monitor It’s quite Debian-style (just build with git-buildpackage) — I am not sure whether you do things much differently in Tails. I can file an ITP if you want it in Debian as well. Looking forward to hear what you think. Cheers Sascha signature.asc Description: Message signed with OpenPGP using GPGMail ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Automated tests specification
Hi,
On Thu, Jul 09, 2015 at 04:52:12PM +0200, intrigeri wrote:
>
> bertagaz wrote (09 Jul 2015 13:28:23 GMT) :
> > On Wed, Jul 01, 2015 at 07:19:04PM +0200, intrigeri wrote:
> >> bertagaz wrote (25 Jun 2015 09:41:23 GMT) :
>
> Indeed I find it too vague so I've rephrased this paragraph (414e4f3),
> and added (414e4f3) another requirement:
>
> * if applicable, the commit at which the base branch was at, when it
>was merged into the branch being built;
Great, fine with me.
> (because we need to run the test suite not from the commit on the
> topic branch, but on the result of merging its base branch into the
> topic branch at that commit)
>
> IIRC I've made it so the build log contains that information, and if
> the build scripts need adjustements to make it easier to retrieve from
> Jenkins (e.g. logging it in a machine-parsable format), let me know,
> I'll be happy to follow-up on this.
Noted. Another way to be sure to test the right {topic,base} branch HEAD
commits could also be to simply copy the workspace from the isobuilder
to the isotester. That's something Jenkins knows how to do.
> Now, it would be good to have feedback from other contributors, in
> particular those who will be directly affected. Let's schedule
> a session to look into this at the summit, shall we?
Yes, we had one but not so much concerned people attended.
So please contributors, take some time reading and commenting on this
blueprint. Most of it is a copy of the automated builds one, as it is
the next step in the chain and the previous one defined already most of
our design.
Given it will be deployed in < 2 monthes, it's quite the last moment to
do so, and to make it clear, you won't be able to complain afterward. :)
bert.
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to
tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Package Tor Monitor
intrigeri: > Hi, > > Alan wrote (17 Aug 2015 23:42:12 GMT) : >> Would someone knowledgeable please package: >> https://git-tails.immerda.ch/alan/tor-monitor/tag/?id=0.1 > > Some more bits of info that might help people raise their hand: > > * Packaging is probably super easy. What we need is *also* someone >committed to maintaining the package on the long run. > * I've privately asked nodens (who's almost done with packaging our >OpenPGP Applet) if he's interested. In any case, I would feel more >comfortable if at least 2 people committed to do this. I would co-maintain this with nodens and if anyone on the list is interested.. i can do some handholding. Cheers! u. ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Question about rebasing on git
Hi, Romeo Papa wrote (18 Aug 2015 23:26:10 GMT) : > When working on my own git topic branch, what do I do when rebasing > patches? Do I create a new topic branch and push the rebased commit to > it, or do I just write over my original topic branch? My rule is to never rewrite already published Git history, unless I'm 100% sure that nobody looked at it yet, or unless the reviewer explicitly asks for it. > I'll give you a practical example: I have pushed a series of patch on a > clone of the repo on gitlab. They've been reviewed, and I've been asked > to rebase them. If I overwrite my original branch, then all the comments > and reviews referring to the overwritten commits will not point to any > commits on the repositories. Is that acceptable? In this case it's OK to rewrite history, because the reviewer has explicitly asked for it. Some people push the rewritten branch with a "-squashed" suffix, and leave the original branch untouched. In doubt, I suggest you do this. Cheers, -- intrigeri ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Package Tor Monitor
Alan wrote (18 Aug 2015 17:33:03 GMT) : > Please note that I was looking for somebody to prepare a package > for Tails, not for Debian, but why not? OK, got it. I would rather avoid a regression here (replacing a tool that's in Debian with one that isn't). Note that Vidalia is not in Jessie, and it's going to be removed from sid soon. Anyway: someone needs to do the initial packaging :) Cheers, -- intrigeri ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
