<asdfhjkl>
i've got autoconf already built on the system phoebos, could be that too
<asdfhjkl>
im gonna try latest commit
<asdfhjkl>
hey phoebos i get the same issue building from @master and if i kiss r autoconf, it errors 127 https://paste.rs/3ul when trying to build automake.
<asdfhjkl>
Do you have autoconf?
<asdfhjkl>
Will you please be so kind to share with me your whole build/version/sources/depends for automake, and autoconf too if you have that
<asdfhjkl>
It concerns me that it works for you and not me, definitely want to see if there's any glaring differences so that I can try your setup
<asdfhjkl>
I'm 8 hours deep in to troubleshooting this damn package
<asdfhjkl>
perl too, i assume you had to install perl, right?
<asdfhjkl>
i know these packages are blasphemous in here, but pretty much required if you're trying to bootstrap an entire kiss ecosystem without tarballs, so I appreciate your putting up with it
<phoebos>
testuser[m]: up early?
<phoebos>
i have auto*, perl, etc
<phoebos>
i'm just running ./bootstrap etc in the git dir
<phoebos>
autoconf 2.71-1
<phoebos>
automake 1.16.5-1
<phoebos>
(installed)
<sad_plan>
why not cheat and patch in the bootstrap script though asdfhjkl ?:p
<sad_plan>
or just add it in files or w/e works best
<sad_plan>
clone the repo, unpack the tarball and diff them
<asdfhjkl>
yeah sad_plan that's not it, it turns out bootstrap IS in the reository from git, I was wrong about that, but unfortunately that's not my issue either
<asdfhjkl>
i'm trying to get all sources self hosted so, i know there's easier ways to juts get a file i need, but i'm keeping it in a separate repo for archive purposes
<phoebos>
asdfhjkl: in your build file, between make and make install, do a `sh >/dev/tty` and when you get dropped into a shell see if ~/.cache/kiss/......../home/asdf/.cache/kiss/....amhello* is there
<asdfhjkl>
phoebos stand by
dilynm has quit [Ping timeout: 252 seconds]
<phoebos>
also, what version of kiss are you running?
van2022 has quit [Remote host closed the connection]
van2022 has joined #kisslinux
<van2022>
I am currently in the process of installing the system. I have interrupted my attempt to install/build the system for several weeks and don't know how to proceed properly. when I stopped I wrote "exit" and copied the contents of mnt to another folder. how to continue?
<wael_>
just for safety, are you using the installation guide from kisslinux.org?
<van2022>
i stopped at step 010. how to continue?
<midfavila>
perform step 011
<midfavila>
:^)
<wael_>
skip to 014
<midfavila>
and don't forget to install gentoo
<wael_>
and also systemd
<van2022>
it looks like a joke. I chose kisslinux because it doesn't have systemd
<van2022>
how to fix it? ibb.co/6wwDYHB
rohan has joined #kisslinux
Torr has joined #kisslinux
<illiliti>
make sure you extracted tarball properly
<Torr>
Wonder if Pax overtook Tar, people'd refer to their archives as paxballs.
<van2022>
illiliti, I haven't gotten to that step yet.
rohan has quit [Ping timeout: 268 seconds]
rohan has joined #kisslinux
<van2022>
step 011 fails. gnupg1 not found
<dilynm>
So install gnupg
<van2022>
gnupg not found
<dilynm>
I believe it's named gnupg1
<van2022>
gnupg1 not found
<phoebos>
it's in dylan's repo in extra, not in community/repo
<phoebos>
but in repo-community
<phoebos>
and kiss-community/repo uses ssh for signing rather than gpg
<van2022>
how to do it?
van2022 has quit [Remote host closed the connection]
midfavila has quit [Quit: Leaving.]
<phoebos>
if you read the logs van2022, instructions are in the README
dilynm has quit [Remote host closed the connection]