[Tails-dev] Build failed in Jenkins: build_Tails_ISO_feature-jessie #511

See -- [...truncated 12305 lines...] ERROR: ld.so: object '/usr/lib/libeatmydata/libeatmydata.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. ERROR:

Re: [Tails-dev] Release versioning

On 05/31/2015 09:24 AM, intrigeri wrote: > * we're not very clear what the first component means (1.0 had >a well-defined meaning, no idea what 2.0 will be; we're currently >using 2.0 and 3.0 on our roadmap to make mid/long-term perspectives >and goals more readable to everyone involve

Re: [Tails-dev] Release versioning

On 05/29/2015 05:19 PM, intrigeri wrote: > Hi, > > it popped up to my mind that our current versioning scheme is a bit > painful whenever we need to insert an unexpected release: e.g. > when we've put out 1.3.1, it "stole" a version number that was > "reserved", which can result in some confusion,

Re: [Tails-dev] [website][review'n'merge]known issues

emmapeel wrote (31 May 2015 08:47:42 GMT) : > intrigeri: >> Your repo apparently still has the old, pre-rewrite Git history => >> please don't point anyone to it before this has been fixed, because >> otherwise they'll pull ~200MB when fetching from your repo, and then >> if anyone re-publishes it

Re: [Tails-dev] [website][review'n'merge]known issues

intrigeri: > Your repo apparently still has the old, pre-rewrite Git history => > please don't point anyone to it before this has been fixed, because > otherwise they'll pull ~200MB when fetching from your repo, and then > if anyone re-publishes it then everybody's repo will grow the same, > which

Re: [Tails-dev] [website][review'n'merge]known issues

emmapeel wrote (31 May 2015 08:22:48 GMT) : > intrigeri: >> My comments follow inline. emmapeel, do you want to polish your branch >> accordingly? If not, please make sure BitingBird is on it :) >> > Very good suggestions indeed. Here the corresponding patch Thanks, applied! > (also pushed to th

Re: [Tails-dev] [website][review'n'merge]known issues

intrigeri: > My comments follow inline. emmapeel, do you want to polish your branch > accordingly? If not, please make sure BitingBird is on it :) > Very good suggestions indeed. Here the corresponding patch (also pushed to the branch) From ccad4c4a9652a10d1cd4f010f559c2893de8e433 Mon Sep 17 00:

Re: [Tails-dev] [website][review'n'merge]known issues

Hi, emmapeel wrote (31 May 2015 06:50:28 GMT) : > I added a little note about the Automatic upgrade failing on Windows > camouflage. We've got quite some mails about it (actually made me > realise how many people uses the camouflage...) > ta...@git.tails.boum.org:emmapeel/tails > [branch]

Re: [Tails-dev] Release versioning

Daniel Kahn Gillmor wrote (31 May 2015 03:42:32 GMT) : > Sorry, I probably don't understand the current versioning scheme very > well -- is there canonical documentation i should read about its > semantics? I don't think so. Basically: * we're not very clear what the first component means (1.0 h