Hi,
This answer might pop up late now that #8665 is in Ready for QA state,
still it might bring new questions. Sorry for that.
On Fri, Jan 23, 2015 at 12:49:10AM +0100, intrigeri wrote:
> mercedes508 wrote (22 Jan 2015 17:54:53 GMT) :
> > And I'm wondering how important the fingerrint issue is, c
On 26/01/15 20:04, intrigeri wrote:
> anonym wrote (26 Jan 2015 13:56:44 GMT) :
>> Merged!
>
> I think you forgot to push stable, experimental and feature/jessie
> after merging into these branches as requested.
Sorry, I completely forgot about stable and feature/jessie, and hadn't
pushed my expe
Hi,
anonym wrote (26 Jan 2015 13:56:44 GMT) :
> I thought it best I took it, since it modifies some Vagrant stuff, which
> I seem to be the maintainer of. Indeed, I had to push two small fixes
> (commits 535abed and a7d4c9c) to repair the provisioning script.
Thanks!
> Merged!
I think you forgo
anonym wrote (26 Jan 2015 12:32:55 GMT) :
> So a `lb clean --all` will remove the built wiki etc. The Vagrant build
> script is actually quite clever in that it *will* reuse any "cached"
> wiki, which can save a couple minutes of build time. I personally find
> this quite useful.
Good to know, tha
On 27/11/14 22:35, intrigeri wrote:
> hi,
>
> I've noticed that bug thanks to the Journal capturing such error
> output on Tails/Jessie, but it affects Wheezy too. We're using the
> affected function in tor-has-bootstrapped, that some users can run
> with passwordless sudo, so better make it more
On 19/01/15 14:16, intrigeri wrote:
> Hi,
>
> since the .{src,bin}pkgs stuff was merged, our build system is leaving
> .{start,end}.timestamp files around, which are useless in most cases.
> anonym has complained about it, so here's a branch that only generates
> these files when building from Jen
On 26/01/15 12:31, intrigeri wrote:
> Hi,
>
> please review'n'merge:
>
> 1. feature/8726-use-homogenous-Debian-mirrors-at-build-time (main Git
> repo) into all branches we build automatically, namely stable,
> devel, experimental and feature/jessie => that's for the RM,
> unless he e
Hi,
On Mon, Jan 19, 2015 at 08:14:55PM +0100, bertagaz wrote:
>
> On Sun, Jan 18, 2015 at 08:07:46PM +, sajolida wrote:
> > bertagaz:
> > > 0. We might also want a mechanism for devs to pro-actively state they
> > > want to
> > > keep their branches being build even if the last commit was ol
On 23/01/15 12:16, intrigeri wrote:
> hi,
>
> anonym wrote (23 Jan 2015 10:34:47 GMT) :
>> This kills the bootstrap stage caching feature in our Vagrant setup,
>> which is considered harmful. Please review and merge into devel!
>
> The code looks good to me. Who in here still has a working
> Vagr
On 23/01/15 20:50, intrigeri wrote:
> Hi,
>
> I'm working on #5525 ("Sandbox the web browser"), and have an AppArmor
> profile that works locally for most basic use cases. Now, I'm
> wondering how to integrate it into Tails and I need your input.
>
> This profile was derived from the one I've wor
intrigeri wrote (25 Jan 2015 08:50:32 GMT) :
> u wrote (24 Jan 2015 19:54:11 GMT) :
>> Do you want to point me at the Tails-specific patch so I can see what we
>> are talking about?
> I'll do that once I have implemented it as a patch. In the meantime:
> https://git-tails.immerda.ch/tails/tree/con
Hi,
Alan wrote (18 Jan 2015 13:40:37 GMT) :
>> I prefer option C: [...]
>>
>> Thoughts?
A week later, I've removed the indication that #8510 is blocked by
#8524.
> I'm fine with option C especially if as much people as possible try
> booting isohybrid DVDs on various computers.
Agreed. Created
Hi,
please review'n'merge:
1. feature/8726-use-homogenous-Debian-mirrors-at-build-time (main Git
repo) into all branches we build automatically, namely stable,
devel, experimental and feature/jessie => that's for the RM,
unless he explicitly asks for help reviewing the pile of stuff
Hi,
intrigeri wrote (19 Jan 2015 12:31:29 GMT) :
> So, I want to:
> 1. hard-code in auto/config all mirrors that shall be used at build time
> 2. update vagrant/provision/setup-tails-builder so that it doesn't
>configure LB_*MIRROR*, and deconfigures them if present
> 3. update wiki/src/contr
hi,
bertagaz wrote (25 Jan 2015 12:14:21 GMT) :
> While I think I could help with maintaining this profile when it breaks
> the build, I'm not much comfortable with this option from my CI hat point
> of view. It means that every devs would be notified of this breakage if/when
> automatic builds wi
15 matches
Mail list logo
