*** zoli__ has joined #baserock | 00:34 | |
*** zoli__ has quit IRC | 00:39 | |
*** zoli__ has joined #baserock | 01:35 | |
*** zoli__ has quit IRC | 01:40 | |
*** zoli__ has joined #baserock | 02:36 | |
*** petefoth has quit IRC | 05:15 | |
*** petefoth has joined #baserock | 06:26 | |
*** mike has joined #baserock | 06:46 | |
*** mike is now known as Guest88732 | 06:46 | |
*** zoli__ has quit IRC | 06:49 | |
*** zoli__ has joined #baserock | 07:09 | |
*** perryl_ is now known as perryl | 07:18 | |
*** CTtpollard has joined #baserock | 07:23 | |
*** edcragg has joined #baserock | 07:39 | |
*** franred has joined #baserock | 07:42 | |
*** edcragg has quit IRC | 07:53 | |
*** mariaderidder has joined #baserock | 08:05 | |
*** bashrc_ has joined #baserock | 08:06 | |
*** rdale has joined #baserock | 08:09 | |
*** petefoth has quit IRC | 08:17 | |
*** petefoth has joined #baserock | 08:18 | |
*** jonathanmaw has joined #baserock | 08:23 | |
*** gary_perkins has joined #baserock | 08:29 | |
*** edcragg has joined #baserock | 08:33 | |
*** tiagogomes_ has joined #baserock | 08:49 | |
*** ssam2 has joined #baserock | 09:00 | |
*** ChanServ sets mode: +v ssam2 | 09:00 | |
*** lachlanmackenzie has joined #baserock | 09:13 | |
* pedroalvarez sighs after seeing that alsa-(utils|libs) have rebased master and also the tag that we are currently using | 09:23 | |
pedroalvarez | It's not the first time they do this | 09:23 |
---|---|---|
richard_maw | perhaps it's time to start using morph anchor | 09:24 |
ssam2 | richard_maw: could you help me with `morph diff` quickly? | 09:25 |
ssam2 | i'm running this: `morph diff baserock:baserock/definitions master -- baserock:baserock/definitions 508d657dd94478d41eb1ec93a1c1556c607d55e6` | 09:25 |
ssam2 | but I get: "ERROR: From expected definition specs 'from' and 'to'; missing 'to'" | 09:25 |
richard_maw | ssam2: single - | 09:26 |
ssam2 | oh | 09:26 |
ssam2 | thanks! | 09:26 |
Kinnison | pedroalvarez: Oh dear, did they put a release out explaining why? | 09:26 |
richard_maw | ssam2: I wanted to use --, but the argument parser swallows it, and to stop it doing that would require rewriting everything to not use cliapp's argument parser | 09:26 |
pedroalvarez | Kinnison: It looks like they rebased just after one release, maybe trying to fix something in the release? I can't see anything in their release notes, I will do a diff to investigate what changed, maybe is something that they have to do, although it seems to me that doing that in tags is not fair play | 09:31 |
Kinnison | It's (IMO) not fair play to rebase master without a jolly good explanation | 09:32 |
*** flatmush1 is now known as flatmush | 09:33 | |
Kinnison | It's one thing if you're a small project | 09:33 |
Kinnison | but not when you're big | 09:33 |
*** Guest88732 has quit IRC | 09:34 | |
richard_maw | as a data point, systemd messed up their `make dist` in their latest release, but haven't attempted to move the tag | 09:35 |
pedroalvarez | shouldn't we avoid things like "+refs/tags/*:refs/tags/*" in the refspecs? | 09:40 |
pedroalvarez | (until we decide to use `morph anchor`) | 09:41 |
Kinnison | IIRC too many projects turned out to be badly behaved to not have that as default | 09:41 |
Kinnison | because we don't monitor the lorry issues regularly | 09:41 |
pedroalvarez | but that means: force push all the tags, right? | 09:42 |
Kinnison | yes | 09:43 |
pedroalvarez | force-push tags + upstream rebasing tags + we using directly tags for definitions (and not anchoring them in a branch) --> scary | 09:44 |
Kinnison | aye | 09:45 |
Kinnison | Which is why I always advocated anchor branches even when we wanted to use tagged releases | 09:45 |
Kinnison | but I kept being overruled by people who thought it was too onerous to manage | 09:45 |
Kinnison | At least, with morph anchor, the effort is reduced | 09:45 |
ssam2 | pedroalvarez: if there was a consistent naming scheme for personal branches, that'd be ok | 09:46 |
pedroalvarez | Kinnison: indeed, +1 to morph anchor, for whenever we are ready for the discussion about using it | 09:46 |
ssam2 | pedroalvarez: if Lorry didn't fail when any branches fail to update, it'd be a lot more practical to avoid "+refs/tags/*:refs/tags/*" as well | 09:46 |
pedroalvarez | hmm | 09:47 |
ssam2 | pedroalvarez: presumably `morph anchor` would be used at release time, so whether it's up to whoever is doing releases, in practice | 09:47 |
ssam2 | i.e. mostly you ;) | 09:47 |
pedroalvarez | hehe | 09:48 |
ssam2 | *whether it's used is up to | 09:48 |
*** Guest88732 has joined #baserock | 09:49 | |
pedroalvarez | ssam2: regarding lorry failing when only some branches failed - not sure we can do anything about it | 09:50 |
pedroalvarez | every project is different, and we sometimes want branches, instead of master (e.g. Openstack projects) | 09:51 |
ssam2 | yeah. Although, if the failures just showed up as warnings, and it was easy to tweak the .lorry files, it would be more practical to develop a set of .lorry files that described the different projects | 09:52 |
ssam2 | still a big, ongoing job though, I'm glad we aren't trying to do that :) | 09:52 |
pedroalvarez | aye, that sounds big | 09:53 |
jjardon | Hi, I asked this yesterday, but in case someone around miss it: is dlopen mean to work when you are building systems? | 09:57 |
Kinnison | It *ought* to work | 09:57 |
Kinnison | that it doesn't is surprising | 09:57 |
Kinnison | (Not least, it works for building things like gall whose test suite uses it) | 09:58 |
Kinnison | and for any python module with C components | 09:58 |
ssam2 | is there any reason why `morph anchor` defaults to pushing branches, instead of tags ? | 10:00 |
ssam2 | and, is 'refs/tags/{trove_id}/anchors/{name}/{commit_sha1}' a sensible setting for 'anchor-ref-format' if one wants tags instead of branches? | 10:02 |
ssam2 | (that's just the default value but in refs/tags instead of refs/heads) | 10:03 |
Kinnison | I'm not sure if Trove rulesets all support that | 10:03 |
ssam2 | they definitely don't support pushing anchors to refs/heads/* in every repo, it seems | 10:04 |
ssam2 | I have an error log from a user who tried the default behaviour, and found it didn't work. But the log is confusing me a bit (it might contain some private stuff so I can't post it here) | 10:06 |
*** Guest88732 has quit IRC | 10:09 | |
*** Guest88732 has joined #baserock | 10:22 | |
*** sambishop has joined #baserock | 10:38 | |
straycat | because the ruleset doesn't support pushing tags to delta/ | 10:39 |
straycat | ? | 10:39 |
ratmice__ | jjardon: I can't imagine why dlopen wouldn't work, for most of the ld.so's i've looked at dlopen is pretty much the same code path as -lfoo linking uses | 10:43 |
jjardon | Kinnison, ratmice__ : thanks, I completely lost why this chunk fail to compile with: http://paste.baserock.org/ikaligafom | 10:45 |
Kinnison | jjardon: sounds more like it wasn't built with expat visible on the system | 10:47 |
jjardon | I rebuilt gettext again with libexpat as dependency: same problem | 10:48 |
Kinnison | hmm | 10:48 |
jjardon | oh | 10:51 |
jjardon | gettext try to dlopen libexpat.so.1 or libexpat.so.0 if that fails. but seems we only have libexpat.so in our systems | 10:52 |
Kinnison | Odd | 10:52 |
ratmice__ | and whatever you are building is getting a build dep on expat? | 10:52 |
Kinnison | jjardon: Sounds like expat's install target isn't naking things properly | 10:52 |
ratmice__ | what's the (SONAME) on libexpat.so from readelf -d? | 10:53 |
jjardon | oh, we are using the experimental cmake build system for libexpat, maybe that's the problem | 10:53 |
ratmice__ | er i'm confused that shouldn't matter in dlopen :) | 10:53 |
jjardon | ratmice__: 0x000000000000000e (SONAME) Library soname: [libexpat.so] | 10:53 |
ratmice__ | so, I assume gettext is trying to work with multiple ABI's of expat for some reason | 10:55 |
jjardon | ratmice__: thats rigth | 10:56 |
jjardon | http://git.savannah.gnu.org/cgit/gettext.git/tree/gettext-tools/src/libexpat-compat.c#n280 | 10:57 |
jmacs | straycat: I see you submitted a v2 to my jmac/partial-java-build-support branch - thanks - but I can't tell from gerrit where you pushed it | 10:57 |
straycat | jmacs, i might not have pushed that branch anywhere, other than to gerrit | 11:00 |
jmacs | Oh right, yes, gerrit is a git server | 11:00 |
ratmice__ | jjardon: seems like it does the actual version dependent stuff at the symbol level (e.g. there is no different handling for one version vs the other), so if expat is building without the symlink might add a 3rd if (handle == NULL) handle = dlopen("libexpat.so", RTLD_LAZY); | 11:02 |
ratmice__ | but yeah, not sure where the right place to fix it is (expat, gettext or both) | 11:05 |
ratmice__ | jjardon: for future reference LD_DEBUG=files (i'd assume when running configure or whatever, actually never tried with configure scripts) can help with finding these issues | 11:09 |
* ratmice__ isn't sure how to get that environment variable set with auto determining build systems | 11:10 | |
jmacs | straycat: I can pull HEAD:refs/for/master/jmac/partial-java-build-support from gerrit, but the ref shown in gerrit doesn't appear in my git repo... | 11:11 |
jjardon | ratmice__: cheers, noted :) | 11:11 |
straycat | jmacs, i usually use git review -d <change number> which is fetching refs/changes/96/696/2 | 11:16 |
straycat | "The first 68 is the id of the change mod 100. The only reason for this initial number is to reduce the number of files in any given directory within the git repository." | 11:17 |
straycat | ( refs/changes/68/68/2 ) | 11:17 |
straycat | ( http://review.cyanogenmod.org/Documentation/intro-quick.html ) | 11:18 |
jmacs | Looks like today's job is going to be learning gerrit, then :) | 11:18 |
*** pacon has joined #baserock | 11:40 | |
*** pacon has quit IRC | 12:44 | |
jmacs | straycat: Where did the "96" come from in refs/changes/96/696/2 ? | 13:20 |
ssam2 | it's 696 % 100 | 13:23 |
ssam2 | I believe that Gerrit would hit some limit in Git ref names if it had thousands of refs under refs/changes directly | 13:24 |
straycat | 12:19 straycat$ "The first 68 is the id of the change mod 100. The only reason for this initial number is to reduce the | 13:30 |
straycat | number of files in any given directory within the git repository." | 13:30 |
jmacs | So now I appear to have straycat's updated commit on its own, without my other two commits - is it appropriate to cherry-pick straycat's commit onto my own branch, or will that mess up gerrit? | 13:31 |
straycat | we can merge 696 and rebase the others on top of it | 13:32 |
jmacs | 696/2, you mean? | 13:33 |
straycat | sure | 13:34 |
jmacs | I suppose that would work | 13:34 |
straycat | merged | 13:34 |
jmacs | Thanks! | 13:35 |
straycat | 697 needs work though | 13:35 |
Kinnison | straycat: Are you intending to do anything for Change 219? You've not tended to it since April 7th -- If you're abandoning it, can you please explicitly abandon it in the UI ? | 13:36 |
jmacs | Well, yes, but I didn't know how to develop on it without having your change in my tree | 13:37 |
straycat | i'm not abandoning it at all | 13:37 |
jmacs | I should be able to work on it now | 13:37 |
straycat | i just don't have time to fix morph so that i can fix the bug *and* avoid duplicating the graph structures | 13:37 |
* straycat shrugs | 13:37 | |
jjardon | Hi, I manage to strip debug symbols in my image using a strip-everything.morph chunk in the end of my last stratum. As this is a bit hacky, I'd like to ask what would be the best way to implement this so it can be submitted to the project? | 13:39 |
Kinnison | Zara: Change 331 (and related) you have -1'd | 13:39 |
Kinnison | Zara: And left for over 5 weeks | 13:40 |
Kinnison | Zara: Are you abandoning that work? | 13:40 |
Zara | Kinnison: fb still haven't updated their licensing, though originally they said they were going to | 13:40 |
Zara | so we're still waiting for them. I think I have abandoned the two related changes | 13:40 |
Kinnison | I see | 13:41 |
richard_maw | jjardon: it's a neat hack that I had considered doing myself, but IMO the appropriate way to do this would be to strip at build time. | 13:41 |
richard_maw | jjardon: btw, I'm currently working on binary stripping | 13:42 |
Kinnison | bashrc_: You have a non-trivial sequence of changes culminating in #281 which haven't seen activity for ca. 5 weeks -- are you abandoning these? | 13:42 |
Zara | Kinnison: I could abandon the last patch and resurrect it later if/when they update their repo, if that's preferable to leaving the patch there. | 13:43 |
Kinnison | Zara: So long as you're managing that patch, I'll not bug you again this week :) | 13:43 |
*** petefoth has quit IRC | 13:44 | |
*** petefoth has joined #baserock | 13:44 | |
Zara | okay, great. :) | 13:44 |
bashrc_ | Kinnison: if they're not going to be pulled then I guess they can be abandoned | 13:46 |
Kinnison | bashrc_: If you know who took over that work then I can ask them | 13:46 |
jjardon | richard_maw: oh, nice. Any idea when are you going to have time to have something we can try? Happy to test if needed | 13:46 |
Zara | Now for me to bug everyone with errors! In my cross-bootstrapped system, I did 'morph init workspace', which worked, followed by a morph checkout in the workspace, which didn't work. Here's the error log: http://paste.baserock.org/awegohetig . What's going on? Have I forgotten a step? | 13:46 |
straycat | Zara, can you ping git.baserock.org ? | 13:47 |
richard_maw | jjardon: I'm currently writing up my proposal in https://storyboard.baserock.org/#!/story/47 along with my reasoning | 13:47 |
bashrc_ | Kinnison: I don't know if anyone took over the firehose development. perryl was doing it prior to me. I don't know if she went back to it | 13:47 |
Kinnison | Zara: Check your /etc/resolv.conf | 13:47 |
Kinnison | Zara: It's likely missing a 'nameserver' entry | 13:47 |
Kinnison | fatal: Unable to look up git.baserock.org (port 9418) (System error) | 13:48 |
Kinnison | being the hint | 13:48 |
perryl | bashrc_: i've not had a chance to go back to the firehose development work; currently unsure when i will next be able to do so | 13:49 |
bashrc_ | so I guess for now it's on ice | 13:50 |
Zara | heh, it appears that I have no 'resolv.conf' in /etc. also don't seem to have a morph.conf so possibly the cross-bootstrap page should link to the quick-start page instead of the 'using baserock' page... | 13:50 |
Kinnison | the mid-cross-bootstrap stuff is "odd" anyway | 13:51 |
Zara | hehe | 13:51 |
jjardon | richard_maw: nice, thanks | 13:54 |
wdutch | I'll have a look at firehose, maybe I can do something useful? | 14:01 |
wdutch | he says without knowing what he's signing up for ... | 14:02 |
richard_maw | ssam2: btw, I had cause to think about sysroots, and I was reminded about how clever your work to make the stage 2 bootstrap work with the gcc specs locating the sysroot by environment variable was. | 14:03 |
richard_maw | good job | 14:03 |
bashrc_ | wdutch what relained was testing of the various operation modes | 14:03 |
richard_maw | I think it got less praise than it deserved. | 14:03 |
bashrc_ | wdutch: http://wiki.baserock.org/firehose-notes/#index8h2 | 14:05 |
wdutch | bashrc_: thanks | 14:05 |
bashrc_ | I think I managed to implement all the modes | 14:06 |
bashrc_ | just needs testing/debugging | 14:06 |
Kinnison | jjardon: I love your spanglish | 14:06 |
Kinnison | jjardon: In future, when you think "posterior" is the word you want, try using "later" or "future" :) | 14:06 |
richard_maw | butts | 14:07 |
ssam2 | heh, thanks | 14:07 |
Kinnison | jjardon: because while it's "correct", its colloquial use is quite different :) | 14:07 |
jjardon | Kinnison: ah :), will do | 14:09 |
* pedroalvarez makes a note for posterior commits | 14:15 | |
* Kinnison dreads | 14:16 | |
Kinnison | SotK_: Change 253 and related -- XFCE stuff -- are you intending to do something with it? | 14:24 |
SotK_ | Kinnison: I am intending to send a v2 when I get time :) | 14:25 |
Kinnison | 6 weeks is a long time to let a change go fallow | 14:25 |
jjardon | Kinnison: I will try to help with that when I get some time as well | 14:26 |
Kinnison | straycat: Change 67 (anon access in trove rulesets) seems to be waiting for action on your part | 14:29 |
Kinnison | richard_maw: If straycat doesn't have time, are you able to adopt and follow it through? | 14:29 |
richard_maw | Kinnison: theoretically able, but it's not a priority task for me so I'm not sure whether I'd be any more likely to get around to it | 14:32 |
straycat | i can probably sort that out at some point | 14:34 |
straycat | i only need to change the comment | 14:34 |
Kinnison | jjardon: Change 17 -- richard_maw left it at -2 asking you to either abandon or produce a more complete patch | 14:39 |
Kinnison | jjardon: Are you intending to do the latter? | 14:39 |
Kinnison | jjardon: if so, feel like commenting to that effect? If not, please abandon | 14:39 |
jjardon | Kinnison: done! | 14:44 |
Kinnison | excellent, thank you jjardon | 14:44 |
jjardon | Kinnison: sorry, I keep trying to come back to that but other things arise all the time | 14:45 |
Kinnison | SotK_: your huge ostree-staging work -- what's the situation with that? | 14:45 |
Kinnison | jjardon: I know the feeling | 14:45 |
Kinnison | jjardon: I'm just trying to garden the open changes | 14:45 |
richard_maw | Kinnison: tbh it's all pending fixing up split /usr and being able to move everything into /usr, so it's safe to have an empty /etc | 14:46 |
richard_maw | Kinnison: since rather late in its development we worked out that we can't actually safely have the deployment speed-ups on a hard-linked rootfs | 14:47 |
Kinnison | richard_maw: That whole series? | 14:48 |
Kinnison | orgh | 14:48 |
richard_maw | Kinnison: theoretically we could break all the links to files outside /usr, but I don't know of the best place to put that logic that would be overly special-casing how systems are built | 14:48 |
richard_maw | Kinnison: it's not safe to use, completely independently of it breaking cross-bootstrap | 14:49 |
Kinnison | I see | 14:49 |
richard_maw | and the naive way to make it safe again, completely defeats the purpose | 14:49 |
richard_maw | which is sad, because we could do a lot of cool things with ostree both as the build tool and as part of the upgrade story of target systems | 14:51 |
* richard_maw would like to replace our current upgrade mechanism with ostree | 14:51 | |
richard_maw | since it's more featureful and it's less code for us to have to maintain independently | 14:51 |
Kinnison | For now I shall skip that entire series | 14:52 |
* Kinnison goes back to gardening | 14:52 | |
Kinnison | doffm: Change #444 has been idle for coming up to a month -- any idea when you might get back to it? | 14:54 |
doffm | Kinnison: I'd kinda forgotten. I can probably get back to it this week. | 14:56 |
Kinnison | coolio | 14:57 |
Kinnison | pedroalvarez: Change #325 was reviewed by you, jjardon uploaded new versions, and you've not re-reviewed -- do you have time/context to reconsider it? | 14:58 |
jmacs | franred: I'm trying to understand your comment on my java patch - the instance config file for baserock_gerrit - does that just expect the user to down load the JDK manually? | 14:58 |
pedroalvarez | Kinnison: will re-review it now | 14:58 |
Kinnison | pedroalvarez: yay | 14:58 |
ssam2 | jmacs: yes, it does | 14:58 |
jmacs | Right | 14:59 |
ssam2 | jmacs: Oracle seem to discourage auto-downloading it | 14:59 |
Kinnison | jjardon: Can I also re-raise #405 to your attention? | 15:00 |
Kinnison | jjardon: #265 you appear to have submitted and then -1'd yourself -- 2 weeks have then passed -- plans? | 15:01 |
jjardon | Kinnison: #405: that one is a little bit more tricky, as seems changes need to be done in systems I do not use and I'm not familiar with. | 15:02 |
jjardon | Kinnison: 265: it will be there until someone with access to that hardware test the patches | 15:02 |
radiofree | abandon 265 | 15:03 |
jjardon | Kinnison: or we can remove support for these boards from definitions if we are actually not maintaining them | 15:04 |
Kinnison | jjardon: I dunno about you, but a change -1'd by the author of it doesn't inspire me to run tests :) | 15:04 |
radiofree | jjardon: why? we *used* to have a bsp that you could drop into a system and boot a wandboard with | 15:05 |
radiofree | barring some kind of terrible userspace disaster that should still be the case | 15:05 |
pedroalvarez | Kinnison: unless the author says that he is -1ing it to avoid having it merged without testing | 15:05 |
radiofree | terrible userspace disaster e.g version 1 of https://gerrit.baserock.org/#/c/33/1 | 15:06 |
pedroalvarez | :) | 15:09 |
Kinnison | SotK_: You submitted and -1'd the distbuild-stress-tester topic (#623 and friends) -- any idea on whether you'll come back to it or not? | 15:17 |
SotK_ | Kinnison: I intend to come back to it, yes | 15:20 |
pedroalvarez | oh, systemd 220 | 15:21 |
pedroalvarez | richard_maw: re - "systemd messing up their `make dist`" in the release. Would that be a problem for us to use it? | 15:22 |
Kinnison | jjardon: the change series culminating in #168 (terminal_title) -- are you coming back to that any time soon? | 15:22 |
richard_maw | pedroalvarez: nope, we build from git | 15:22 |
richard_maw | pedroalvarez: though they require newer kernel headers in 220 than 219, which might cause issues | 15:22 |
richard_maw | pedroalvarez: I've got a patch locally that we could submit to fix that | 15:23 |
* pedroalvarez realises how stupid was his question | 15:23 | |
richard_maw | nah, packaging is difficult (as we can see from the 220 release's accident), it's not stupid to not know the implications of make dist vs building from git | 15:24 |
jjardon | radiofree: we still have;. If current master is broken simply use a older definitions | 15:24 |
jjardon | problem is that its probably broken as no one is actively testing it on a wandboard | 15:24 |
*** zoli__ has quit IRC | 15:24 | |
radiofree | jjardon: or you could just not touch kernels for hardware you're not testing | 15:25 |
pedroalvarez | richard_maw: we are using kernel headers from 4.0 I believe | 15:26 |
richard_maw | that ought to be new enough then | 15:26 |
Kinnison | ssam2: Are you working on a new patchset for #581 any time soon? (I appreciate it has only been a week, so now I'm just being a naggy git :) | 15:27 |
ssam2 | i doubt it will be soon | 15:27 |
ssam2 | but would prefer to keep the change open, so I can keep track of the fact that it needs doing | 15:27 |
Kinnison | nod. | 15:28 |
Kinnison | I may bug you in future :) | 15:28 |
radiofree | is it safe to run a "morph upgrade" on a system that's currently doing a "morph build"? | 15:34 |
radiofree | no wait, morph deploy | 15:34 |
pedroalvarez | I think it's even safe to self-upgrade the system | 15:36 |
robtaylor | any chance storyboard.baserock.org could get a *.baserock.org cert? | 15:38 |
Kinnison | I asked about it, and ssam2 said he wanted to redeploy it first | 15:38 |
*** radiofree has quit IRC | 15:48 | |
*** radiofree has joined #baserock | 15:49 | |
jjardon | Kinnison: maybe you can take a look to https://gerrit.baserock.org/#/c/717/ when you have time | 15:50 |
Kinnison | jjardon: I can look, but I'm not in a position to test-build right now | 15:52 |
Zara | Hi, I tried to build a system and got a strange error: http://paste.baserock.org/virakifuxe . Someone suggested it might be to do with my machine having an old kernel (3.10.24) | 15:54 |
Zara | I'm trying to do the build after running linux-user-chroot inside a chroot (into a cross-bootstrapped system). if anyone has a lightbulb moment, please let me know! :) | 15:57 |
Kinnison | You're running *inside* a l-u-c ? | 15:57 |
Zara | ah, do I need to come out of that? the wiki is a bit ambiguous so I'll change it if so | 15:58 |
Kinnison | l-u-c drops a lot of permissions | 15:58 |
Kinnison | likely including the ability to unshare etc | 15:59 |
Kinnison | ensure the base of the cross-bootstrapped system is a mount point (use mount --bind /foo/bar /foo/bar if it's not) and use normal 'chroot' to go inside | 15:59 |
Kinnison | that might work better | 15:59 |
jjardon | Zara: ah, linux-user-chroot / /bin/sh is only to check everything is working correctly: you should exit from there before start the build | 16:00 |
Zara | ah, okay, will do :) | 16:00 |
richard_maw | jjardon: can I see the morphology you used to strip your system? | 16:22 |
radiofree | it's come up before, what's the fix for "Couldn't find morphology: systems/system-that-is-clearly-there-and-commited-to-git.morph" | 16:24 |
ssam2 | i don't know :( | 16:25 |
Zara | did you make a new branch? maybe it's looking at the wrong commit? | 16:25 |
jjardon | richard_maw: sure, but we couldn't deploy it yet, so not sure is working correctly at the moment: this is the commit: http://paste.baserock.org/tebarocedu | 16:25 |
radiofree | i just did morph checkout baserock:baserock/definitions master | 16:26 |
radiofree | then git checkout *branch* | 16:26 |
radiofree | copying the system morph to something else worked... | 16:26 |
radiofree | cp systems/my-system.morph systems/my-system-2.morph | 16:26 |
ssam2 | weird | 16:26 |
radiofree | edit the name of my-system-2.morph, don't commit, works | 16:27 |
ssam2 | are there any changes to the repo other than that? | 16:27 |
ssam2 | Morph takes a different code path depending on whether you have any uncommitted changes or not | 16:27 |
richard_maw | thanks jjardon | 16:27 |
radiofree | ssam2: no other changes | 16:28 |
ssam2 | right. that'll be why. It certainly sucks | 16:31 |
*** mariaderidder has quit IRC | 17:01 | |
*** jonathanmaw has quit IRC | 17:02 | |
SotK_ | radiofree: morph doesn't build the checked out branch, it builds using the branch defined in $workspace/$branch_given_to_morph_checkout/.morph-system-branch/config | 17:11 |
radiofree | :\ | 17:12 |
radiofree | is that a new thing? | 17:12 |
SotK_ | so despite your git checkout *branch*, it is still looking at master unless you have uncommitted changes | 17:12 |
SotK_ | nope, it's been like that forever afaik | 17:12 |
radiofree | ah | 17:13 |
SotK_ | it just isn't noticeable most of the time | 17:13 |
radiofree | this is only an issue with morph build though | 17:13 |
radiofree | git checkout -b foo and adding strata/chunks is fine | 17:13 |
SotK_ | even when there are no uncommitted changes? | 17:15 |
*** ssam2 has quit IRC | 17:18 | |
radiofree | SotK_: i... i think so | 17:18 |
jjardon | ugh, cross- system tarball is still ~4GB | 17:24 |
jjardon | list of current stuff: http://paste.baserock.org/yidisagesi | 17:25 |
jjardon | mmm, ok. Seems that is a normal size | 17:27 |
*** lachlanmackenzie has quit IRC | 17:28 | |
*** Guest88732 has quit IRC | 17:35 | |
*** tiagogomes_ has quit IRC | 17:48 | |
*** gary_perkins has quit IRC | 18:28 | |
*** edcragg has quit IRC | 18:46 | |
SotK_ | radiofree: thats weird | 18:51 |
SotK_ | hmm, maybe its not that weird | 18:52 |
rjek | Can't it be both? | 18:52 |
SotK_ | I think its weird after all | 18:55 |
*** SotK_ is now known as SotK | 19:33 | |
*** rdale has quit IRC | 20:04 | |
pedroalvarez | urgh, libexpat change broke everything | 21:02 |
* pedroalvarez sends https://gerrit.baserock.org/#/c/718/ to fix it | 21:26 | |
*** zoli__ has joined #baserock | 23:03 | |
*** zoli__ has quit IRC | 23:43 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!