IRC channel logs
2024-01-17.log
back to list of logs
<rekado>hmm, the bioc channel cannot be pulled, because loading guix-cran/packages/g.scm fails. But the guix-cran channel on its own works fine. <rekado>strangely the Guix channel it uses is at commit 9f1f80e24b23bc3d5f8b7cbe2196b31672b539cb. <rekado>and that’s because the import.scm script runs “guix describe -f channels” instead of using the same Guix that was used to run the script <rekado>I’ll move the update.sh script from maintenance.git to guix-cran-scripts.git, adjust it to work with the new guix-bioc channel and then reconfigure berlin. <rekado>I want to give it permission to write to the new guix-bioc repository. <PurpleSym>I accepted the invite. Can I give you access to this account somehow? <rekado>do you mean tranfer ownership somehow? <rekado>thanks for accepting the invite! <PurpleSym>rekado: If you like, but maybe we can share the ownership somehow? <rekado>no idea how that’s done ¯\_(ツ)_/¯ <PurpleSym>And then share the TOTP token with you I guess. <PurpleSym>Hm, no, that’s not going to work. There can only be one password reset email address. <PurpleSym>Maybe the guix-sysadmin mailinglist? I’m not on there though. <PurpleSym>Does your email provider support the + syntax, rekado ? i.e. rekado+…@ <rekado>PurpleSym: yes, this should work <rekado>I think the guix-sysadmin alias is a bit too wide and too off-topic. <PurpleSym>rekado: You should have received a verification mail from GitHub and instructions how to generate TOTP token from me. <rekado>still having some problems with generating the channel. There are some packages that have no source tarball, and that messes things up a bit. <civodul>rekado: i don’t control guix-cran-bot, no