Tails

#2 Updated by intrigeri 2015-07-07 08:05:16

I just spent quite some time trying to fix that locally. I tried many combinations of:

• removing raw="yes" from the inline directives we’ve recently added on wiki/src/news/version_1.4.1.mdwn, wiki/src/news/version_1.4.mdwn and wiki/src/news/report_2015_05.mdwn
• “translating” every such inline directive into German:
  • pointing it to the English page name (e.g. [[!inline pages="inc/release_notes/1.4" raw="yes"]])
  • pointing it to the German page name (e.g. [[!inline pages="inc/release_notes/1.4.de" raw="yes"]])

None of those worked.

However, removing these three inline directives fixed the problem for me. So, it looks like this chain of inline (the one on news.mdwn that generates the feeds, that pulls the ones from these 3 pages in news/, that themselves pull content from wiki/src/inc/release_notes/) is buggy with current ikiwiki. I can’t say I’m very surprised: inline + po plugin have been fragile historically, and here we’re pushing the limits a bit too far, maybe.

So, either someone fixes the bug in ikiwiki, or someone finds a workaround, or we’ll have to remove these new inline directives, and deal with the duplication of content between release notes and monthly reports in another way.

#5 Updated by anonym 2015-09-07 14:45:01

intrigeri wrote:
> So, either someone fixes the bug in ikiwiki

My perl sucks too much for even considering trying…

> or someone finds a workaround

… and my knowledge of ikiwiki is pretty shallow. I couldn’t even had come up with the fixes you tried.

> or we’ll have to remove these new inline directives, and deal with the duplication of content between release notes and monthly reports in another way.

So this is the only thing what I could do, without much of a solution for how to deal with the translations in a sweet way. How much of a problem would that be? It doesn’t look like our reports get translated much, and frankly the reports seems mostly targeted at people interested in Tails development, which require knowing English any way. Isn’t copy-pasting the release notes an acceptable “solution”? Or just skipping that part, and just linking to any actual release’s page.

Unfortunately, I feel like a poor match for actually solving the problem. :/

#7 Updated by intrigeri 2015-09-15 03:14:36

> Isn’t copy-pasting the release notes an acceptable “solution”? Or just skipping that part, and just linking to any actual release’s page.

I think we need to remove all inlines introduced by e.g. https://mailman.boum.org/pipermail/tails-project/2015-June/000227.html, and same in all following monthly reports. There was an argument in this thread in favour of not merely linking, and at DebConf I’ve talked with at least one person who’s reading our monthly reports and is happy to have the release notes in them, so my preferred “solution” currently is simply copy’n’pasting release notes into reports, and too bad if they won’t be translated in the monthly reports.

#16 Updated by intrigeri 2015-12-20 03:59:02

Now that 1.8 and 1.8.1 have been released, more work is needed since these two release processes have followed the unpatched release doc. Do you want to do the forward-porting yourself? I can do it once now, if I’m confident the result will be merged before the 2.0 release process and thus I don’t have to do it again in the future.

#17 Updated by intrigeri 2016-01-14 22:14:09

intrigeri wrote:
> Now that 1.8 and 1.8.1 have been released, more work is needed since these two release processes have followed the unpatched release doc.

Add 1.8.2 to this list.

> Do you want to do the forward-porting yourself? I can do it once now, if I’m confident the result will be merged before the 2.0 release process and thus I don’t have to do it again in the future.

Ping? The more we wait, the more boring, useless forward-porting work will be needed.

You can also tell me that I should not block on you for this one any longer, and then I’ll do the forward-porting and merge myself, and then you’ll give it a look when you have more time :)

#22 Updated by sajolida 2016-03-29 17:12:46

I’m not sure why but this is not the case anymore…