| *** gww has joined #baserock | 02:13 | |
| *** juergbi` has joined #baserock | 05:48 | |
| *** wdutch has quit IRC | 05:49 | |
| *** juergbi has quit IRC | 05:49 | |
| *** wdutch has joined #baserock | 05:56 | |
| *** franred has joined #baserock | 06:09 | |
| *** ctbruce has joined #baserock | 08:49 | |
| *** paulw has joined #baserock | 08:51 | |
| *** bashrc has joined #baserock | 09:03 | |
| *** toscalix has joined #baserock | 09:10 | |
| *** tiagogomes has joined #baserock | 09:43 | |
| *** jonathanmaw has joined #baserock | 10:02 | |
| *** zoli_ has quit IRC | 10:45 | |
| *** bfletcher has quit IRC | 10:45 | |
| *** locallycompact has joined #baserock | 10:55 | |
| *** rdale has joined #baserock | 11:25 | |
| *** locallycompact has quit IRC | 11:36 | |
| *** rdale has quit IRC | 11:43 | |
| *** rdale has joined #baserock | 11:48 | |
| *** zoli_ has joined #baserock | 11:57 | |
| *** bfletcher has joined #baserock | 12:03 | |
| *** rdale has quit IRC | 12:31 | |
| *** toscalix_ has joined #baserock | 15:00 | |
| *** toscalix has quit IRC | 15:02 | |
| *** toscalix_ has quit IRC | 15:31 | |
| *** gtristan has joined #baserock | 15:41 | |
| *** toscalix_ has joined #baserock | 16:01 | |
| *** toscalix_ has quit IRC | 16:18 | |
| *** toscalix_ has joined #baserock | 16:18 | |
| *** franred has quit IRC | 16:59 | |
| *** ctbruce has quit IRC | 17:18 | |
| *** toscalix_ is now known as toscalix | 17:38 | |
| *** jonathanmaw has quit IRC | 17:50 | |
| *** bashrc has quit IRC | 18:01 | |
| *** toscalix has quit IRC | 18:24 | |
| *** rdale has joined #baserock | 18:41 | |
| *** nowster has quit IRC | 18:49 | |
| *** juergbi` is now known as juergbi | 19:13 | |
| paulsherwood | so, transitive dependencies... | 19:24 |
|---|---|---|
| paulsherwood | if i try to build asciidoc from definitions, i believe the dep tree includes both python 2.7 and python 3.4 | 19:25 |
| *** rdale has quit IRC | 19:26 | |
| paulsherwood | so it appears that depending on what order the dependencies are installed in the sandbox, asciidoc fails or succeeds | 19:26 |
| paulsherwood | my head is hurting too hard to understand whether an order is implied in the yaml or not | 19:28 |
| paulsherwood | but in other contexts i've shuffled orders without a problem | 19:29 |
| persia | The fix is probably to tell asciidoc to use a specific python, rather than /use/bin/python or `env python` (but I am guessing based on similar issues, without investigating) | 19:40 |
| paulsherwood | ack | 19:41 |
| persia | The common problem being that often the most recently installed python claims /usr/bin/python | 19:41 |
| persia | And `env python` usually finds that first in the path | 19:41 |
| paulsherwood | yes, that's what's happening. what i'm unclear about is whether the order should be made deterministic, or assumed to not overlap | 19:43 |
| * paulsherwood prefers that order is not deterministic, since randomizing has led to performance improvments and exposed some assumptions | 19:43 | |
| paulsherwood | but others differ in this, i'm sure | 19:44 |
| persia | Not indicating a syntax version is a bug in asciidoc, if it cannot use either python2 or python3. If it can, then some set of dependencies is insufficiently precise about needing something built with some specific version of python. | 19:46 |
| paulsherwood | http://paste.baserock.org/dohecusayi | 19:47 |
| paulsherwood | that's what happens with python3 | 19:48 |
| paulsherwood | (i believe) | 19:48 |
| persia | Actually, my memory of definitions (an older format now) is that the toolchain version was not captured in the archive name, such that if one builds a system with two options for some toolchain (python2+python3 or glibc+musl), there us no way to say that one depends on some library built with one or another if them. | 19:48 |
| persia | That error makes me think asciidoc does not work with python3, and so needs to specify /usr/bin/python2 | 19:50 |
| persia | But I may be wrong. | 19:50 |
| paulsherwood | according to https://github.com/asciidoc/asciidoc/issues/83 | 19:51 |
| paulsherwood | it requires python2 | 19:51 |
| persia | Right, so change the code to use the version-spevific interpreter for the quick fix (just an adjustment to the !# line) | 19:55 |
| paulsherwood | and submit as a patch to upstream? | 19:55 |
| persia | That should work in an environment with both pythons unless asciidoc depends on a library that is not built against python2 | 19:55 |
| persia | Yes. From issue 83, upstream would clearly prefer a python3 port patch, but the workaround should work for today. | 19:56 |
| paulsherwood | hasn't been a release for a long time... we're using last tag, from 2013 | 19:57 |
| persia | https://sources.debian.net/src/asciidoc/8.6.9-3/debian/patches/code-filter.py-python-path.dpatch is the relevant patch in Debian, but that assumes default-python2. It may be a sensible start for your patch. | 19:59 |
| persia | There are a number of other useful patches in Debian you may want, as long as you are branching anyway. | 20:00 |
| persia | Issue 83 seems to imply that the long-term plan is to abandon and deprecate asciidoc, which is not promising in terms of landing the change upstream. | 20:01 |
| paulsherwood | hmmm... # nasm wants asciidoc and xmlto for generating its docs | 20:30 |
| persia | As python libraries or shell utilities? If the latter, that should be unaffected by the patch (and if asciidoc is replaced, easy to patch in nasm and xmlto) | 20:46 |
| paulsherwood | i was quoting from definitions. anyway, after reordering my code, problem goes away :) | 21:34 |
| persia | You are hiding it :) | 21:37 |
| persia | The bug remains (or there would not be the Debian patch I referenced) | 21:38 |
| persia | That said: glad to hear your yak is trimmed enough to move again | 21:39 |
| paulsherwood | :) | 21:40 |
| *** fay_ has joined #baserock | 22:13 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!