Re: nss-certs: hash mismatch on berlin
Hi Ludo, On Thu, 25 Jul 2019 19:10:11 +0200 Ludovic Courtès wrote: > Hello, > > Björn Höfling skribis: > > > Hi Ludo, > > Hi Guix, > > > > while trying to build a new installer-image, I encountered: > > > > nss-certs-3.44.1 > > 150KiB > > 4.0MiB/s 00:00 [##] 100.0% > > > > sha256 hash mismatch > > for /gnu/store/32hy1jqkam201l7c4wg3bhxz4x5l5jy0-nss-certs-3.44.1: > > expected hash: 0vbkb5mcwzbz4lm1c1319pail61785sd3lj6526vl5hdnp1rxyad > > actual hash: 1awgljvsvc141350xyjjnb15hk66qpcpzwz0hrly11yfbw6wn7cv > > substitution > > of /gnu/store/32hy1jqkam201l7c4wg3bhxz4x5l5jy0-nss-certs-3.44.1 > > failed > > Like Ricardo, I get the correct hash everywhere: > > --8<---cut here---start->8--- > $ wget -qO - > http://berlin.guix.gnu.org/32hy1jqkam201l7c4wg3bhxz4x5l5jy0.narinfo | > grep Hash NarHash: > sha256:0vbkb5mcwzbz4lm1c1319pail61785sd3lj6526vl5hdnp1rxyad $ wget > -qO - > http://berlin.guix.gnu.org/nar/lzip/32hy1jqkam201l7c4wg3bhxz4x5l5jy0-nss-certs-3.44.1 > | lzip -d | guix hash - > 0vbkb5mcwzbz4lm1c1319pail61785sd3lj6526vl5hdnp1rxyad $ wget -qO - > http://berlin.guix.gnu.org/nar/gzip/32hy1jqkam201l7c4wg3bhxz4x5l5jy0-nss-certs-3.44.1 > | gunzip | guix hash - > 0vbkb5mcwzbz4lm1c1319pail61785sd3lj6526vl5hdnp1rxyad $ wget -qO - > http://ci.guix.gnu.org/nar/lzip/32hy1jqkam201l7c4wg3bhxz4x5l5jy0-nss-certs-3.44.1 > | lzip -d | guix hash - > 0vbkb5mcwzbz4lm1c1319pail61785sd3lj6526vl5hdnp1rxyad $ wget -qO - > http://ci.guix.gnu.org/nar/gzip/32hy1jqkam201l7c4wg3bhxz4x5l5jy0-nss-certs-3.44.1 > | gunzip | guix hash - > 0vbkb5mcwzbz4lm1c1319pail61785sd3lj6526vl5hdnp1rxyad > --8<---cut here---end--->8--- > > Could you run these commands locally and see what you get? > > Could it be lack of disk space or a transient networking issue on > your side? > > Thanks, > Ludo’. This is strange and I have no clue what's going wrong here: All your commands above work as expected. Yes, I'm running out of disk space, but everything else works and the nss-package isn't the biggest one. Currently 8 GiB left. I built it locally, that worked. Now deleting it: $ guix gc -D /gnu/store/32hy1jqkam201l7c4wg3bhxz4x5l5jy0-nss-certs-3.44.1 Then trying to fetch it: ~/guix/wt/nonfree [env]$ ./pre-inst-env guix build nss-certs 0.2 MB will be downloaded: /gnu/store/32hy1jqkam201l7c4wg3bhxz4x5l5jy0-nss-certs-3.44.1 substituting /gnu/store/32hy1jqkam201l7c4wg3bhxz4x5l5jy0-nss-certs-3.44.1... downloading from https://ci.guix.gnu.org/nar/gzip/32hy1jqkam201l7c4wg3bhxz4x5l5jy0-nss-certs-3.44.1... nss-certs-3.44.1 150KiB 1.0MiB/s 00:00 [##] 100.0% sha256 hash mismatch for /gnu/store/32hy1jqkam201l7c4wg3bhxz4x5l5jy0-nss-certs-3.44.1: expected hash: 0vbkb5mcwzbz4lm1c1319pail61785sd3lj6526vl5hdnp1rxyad actual hash: 1awgljvsvc141350xyjjnb15hk66qpcpzwz0hrly11yfbw6wn7cv substitution of /gnu/store/32hy1jqkam201l7c4wg3bhxz4x5l5jy0-nss-certs-3.44.1 failed guix build: error: some substitutes for the outputs of derivation `/gnu/store/br6w1qmw2b98c6fa45gy0ljqdzjw70vr-nss-certs-3.44.1.drv' failed (usually happens due to networking issues); try `--fallback' to build derivation from source This is on dd9c137b2c759f906d57b14fccff091994f274e8 Manually downloading seams to find the right hash: $ wget -qO - https://ci.guix.gnu.org/nar/gzip/32hy1jqkam201l7c4wg3bhxz4x5l5jy0-nss-certs-3.44.1 | gunzip | guix hash - 0vbkb5mcwzbz4lm1c1319pail61785sd3lj6526vl5hdnp1rxyad $ ls /gnu/store/*nss-certs-3.44.1* -d /gnu/store/32hy1jqkam201l7c4wg3bhxz4x5l5jy0-nss-certs-3.44.1 /gnu/store/br6w1qmw2b98c6fa45gy0ljqdzjw70vr-nss-certs-3.44.1.drv /gnu/store/32hy1jqkam201l7c4wg3bhxz4x5l5jy0-nss-certs-3.44.1.lock /gnu/store/fpv0xrrr47g879agkmchzzamw1p46i46-nss-certs-3.44.1-guile-builder I blamed that something about locales is wrong on berlin. Could it be the case that on my side something with locales is wrong? In the build daemon? I'm on Ubunutu+Guix, that might cause also some trouble? How can I verify/check my locale-configs? Thanks, Björn pgpCsOFt9pqGk.pgp Description: OpenPGP digital signature
Re: Gender neutral documentation
>> Right now, yes. If you want to help, that'd make it two. :-) Ahh ok! I will >> Well, actually https://translationproject.org is the real platform for the translation process, but we could define any workflow as needed, I think. We can agree about that privately or on the tp list (e...@tp.org.es), if needed. Nice! I'm will check that >> They aren't rules, they're a synthesis of the intent behind my translations. I've shown you an actual example of perfect Spanish where the feminine (grammatical) gender can be applied to any (social) gender. As I bend a little the conventional rules in the default case, I can understand the "neo" as an misplaced joke, but I'd stay close to the facts and far from that kind of modifiers to keep the conversation on topic. Actually I didn't try to make a joke, I tried to describe the 'new spanish rules' as that, because is not the 'conventional way' to text Spanish. Just to be clear, I really appreciate your work and all that you have translated so far even if I consider the 'new way' to text Spanish is not correct, but its ok, Its more important have an Spanish version after all. Then, I understand I should translate in the female (grammatical) spanish (as a rule) to keep the all the documentation with the same logic. If in the future someone consider is better modify it to 'traditional spanish' they can update it I guess. Regards! El mar., 30 jul. 2019 a las 20:42, Miguel () escribió: > Hi! > > El July 30, 2019 11:53:26 PM UTC, Wilson Bustos > escribió: > >El July 30, 2019 10:10:21 PM UTC, Wilson Bustos > >escribió: > >>>Hello everyone! > >>>I would like to help to make guix packages, > >>I'm also reading documentation and watching videos about this. > >>> > >>>But I have some questions. > >>>1- Do you have some document which explain what means 'gender > >neutral' > >>>documentation. > >>>and how that works in different languages such as Spanish? > >>> > > > >> The use of the feminine gender as neutral in the Spanish translation > >is > >intended as explained here: > >https://guix.gnu.org/manual/es/html_node/Envio-de-parches.html#DOCF40 > > > >Thank you so much! that article resolve really well my question! > > You're welcome. > > >My other question is: > >Are you the only person who translate in Spanish? > > Right now, yes. If you want to help, that'd make it two. :-) > > >- If I help you with some parts have I to sent it to you first? > > Well, actually https://translationproject.org is the real platform for > the translation process, but we could define any workflow as needed, I > think. We can agree about that privately or on the tp list (e...@tp.org.es), > if needed. > > >I ask this because I'm not sure if I can apply all the logic behind the > >neo > >Spanish rules that you apply, > > They aren't rules, they're a synthesis of the intent behind my > translations. I've shown you an actual example of perfect Spanish where the > feminine (grammatical) gender can be applied to any (social) gender. As I > bend a little the conventional rules in the default case, I can understand > the "neo" as an misplaced joke, but I'd stay close to the facts and far > from that kind of modifiers to keep the conversation on topic. > > >- This rules are also to translate the package description? or only for > >the > >main documentation? > > As I said, they aren't rules, only the reason why I did that. I think that > it's up to the community to make a decision, not me. Currently, the > community decision is to use gender neutral language, but it'd be a > nonsense make a decision about a language you don't speak, so this > interpretation is at the end up to each language speakers community. > > Any thought about gender neutrality in Spanish, everybody? > > Best regards, > Miguel >
Re: Gender neutral documentation
Hi! El July 30, 2019 11:53:26 PM UTC, Wilson Bustos escribió: >El July 30, 2019 10:10:21 PM UTC, Wilson Bustos >escribió: >>>Hello everyone! >>>I would like to help to make guix packages, >>I'm also reading documentation and watching videos about this. >>> >>>But I have some questions. >>>1- Do you have some document which explain what means 'gender >neutral' >>>documentation. >>>and how that works in different languages such as Spanish? >>> > >> The use of the feminine gender as neutral in the Spanish translation >is >intended as explained here: >https://guix.gnu.org/manual/es/html_node/Envio-de-parches.html#DOCF40 > >Thank you so much! that article resolve really well my question! You're welcome. >My other question is: >Are you the only person who translate in Spanish? Right now, yes. If you want to help, that'd make it two. :-) >- If I help you with some parts have I to sent it to you first? Well, actually https://translationproject.org is the real platform for the translation process, but we could define any workflow as needed, I think. We can agree about that privately or on the tp list (e...@tp.org.es), if needed. >I ask this because I'm not sure if I can apply all the logic behind the >neo >Spanish rules that you apply, They aren't rules, they're a synthesis of the intent behind my translations. I've shown you an actual example of perfect Spanish where the feminine (grammatical) gender can be applied to any (social) gender. As I bend a little the conventional rules in the default case, I can understand the "neo" as an misplaced joke, but I'd stay close to the facts and far from that kind of modifiers to keep the conversation on topic. >- This rules are also to translate the package description? or only for >the >main documentation? As I said, they aren't rules, only the reason why I did that. I think that it's up to the community to make a decision, not me. Currently, the community decision is to use gender neutral language, but it'd be a nonsense make a decision about a language you don't speak, so this interpretation is at the end up to each language speakers community. Any thought about gender neutrality in Spanish, everybody? Best regards, Miguel
Re: Gender neutral documentation
El July 30, 2019 10:10:21 PM UTC, Wilson Bustos escribió: >>Hello everyone! >>I would like to help to make guix packages, >I'm also reading documentation and watching videos about this. >> >>But I have some questions. >>1- Do you have some document which explain what means 'gender neutral' >>documentation. >>and how that works in different languages such as Spanish? >> > The use of the feminine gender as neutral in the Spanish translation is intended as explained here: https://guix.gnu.org/manual/es/html_node/Envio-de-parches.html#DOCF40 Thank you so much! that article resolve really well my question! My other question is: Are you the only person who translate in Spanish? - If I help you with some parts have I to sent it to you first? I ask this because I'm not sure if I can apply all the logic behind the neo Spanish rules that you apply, - This rules are also to translate the package description? or only for the main documentation? El mar., 30 jul. 2019 a las 19:34, Miguel () escribió: > El July 30, 2019 10:10:21 PM UTC, Wilson Bustos > escribió: > >Hello everyone! > >I would like to help to make guix packages, > >I'm also reading documentation and watching videos about this. > > > >But I have some questions. > >1- Do you have some document which explain what means 'gender neutral' > >documentation. > >and how that works in different languages such as Spanish? > > > > The use of the feminine gender as neutral in the Spanish translation is > intended as explained here: > https://guix.gnu.org/manual/es/html_node/Envio-de-parches.html#DOCF40 > > >2- Reading the the Spanish version of the GNU manual in several pages > >like > >this one: > > > https://guix.gnu.org/manual/es/html_node/Caracteristicas.html#Caracter_00edsticas > > > >Has female sentence instead a 'normal' - 'neutral' sentence. > >LIKE: `Opera en los perfiles de usuaria, y puede ser usada *con > >privilegios > >de usuaria normal*.` > > > >which say 'usuaria' to refer to the user, but that words is only used > >to > >refer to a woman. > >but 'usuario' can be used to refer to a man or woman. > > As written in the footnote, It's perfectly reasonable to say in Spanish > "la persona" and "las personas" (person/people in English), whose > grammatical gender is feminine, to refer anyone without making any > reference to their preferred gender, so it should be any problem to use > that grammatical gender instead of the usual "neutral" one. From Latin's > neutral case we have words like "el/la estudiante", "el/la marchante [de > arte]", but the selection of the masculine as the default/neutral form is > arguably biased towards one end. > > >Using this all the time it becomes confusing to read for me, due to > >this I > >change to the english manual. > > I understand that it can be tiresome, specially if you've been socialized > as a male as I've been. On the other hand, more than a half of the Spanish > speakers don't have to make any effort in order to understand it. I suppose > that the same effort probably have been the done (usually beforehand) by > people socialized as females when they read a document claiming > (implicitly, as any language construct) that "usuario" applies to them too, > but I only have anecdotical evidence... and the fact that women are really > underrepresented (at least) in the development and free software community, > so I try to take a feminist stance as my grain of sand to move this actual > mountain. > > >I completely respect your job I want to be part of the community and > >help, > >I know this is a really delicate topic and I don't want to make a flame > >war > >or something like that. > > My approach is far from perfect: there are people who don't identify > neither as male nor female, so the dissonance is still there, but I'm open > to any new idea but using male gender as neutral one for the reasons I > exposed there and here. > > Personally, I think it needs to be openly talked, it shouldn't be a flame > war each time somebody mentions it. The conflict is already there, not > speaking "about the elephant" doesn't make it disappear and only delays the > possible solutions. > > Best regards, > Miguel > Hello, Wilson! > > Thank you for your interest in this awesome community. From my side, I've > been taking more than expected to finish the translation and send some > other patches, sorry for that. I hope to do it soon, but I only can answer > with my phone at this moment. > > I'll try to answer your questions inline, let's see... >
Fwd: Re: Gender neutral documentation
Sorry, I knew something will go wrong (twice)... Fixed here: Mensaje Original De: Miguel Enviado: July 30, 2019 11:34:42 PM UTC Para: guix-devel@gnu.org, Wilson Bustos Asunto: Re: Gender neutral documentation Hello, Wilson! Thank you for your interest in this awesome community. From my side, I've been taking more than expected to finish the translation and send some other patches, sorry for that. I hope to do it soon, but I only can answer with my phone at this moment. I'll try to answer your questions inline, let's see... El July 30, 2019 10:10:21 PM UTC, Wilson Bustos escribió: >Hello everyone! >I would like to help to make guix packages, >I'm also reading documentation and watching videos about this. > >But I have some questions. >1- Do you have some document which explain what means 'gender neutral' >documentation. >and how that works in different languages such as Spanish? > The use of the feminine gender as neutral in the Spanish translation is intended as explained here: https://guix.gnu.org/manual/es/html_node/Envio-de-parches.html#DOCF40 >2- Reading the the Spanish version of the GNU manual in several pages >like >this one: >https://guix.gnu.org/manual/es/html_node/Caracteristicas.html#Caracter_00edsticas > >Has female sentence instead a 'normal' - 'neutral' sentence. >LIKE: `Opera en los perfiles de usuaria, y puede ser usada *con >privilegios >de usuaria normal*.` > >which say 'usuaria' to refer to the user, but that words is only used >to >refer to a woman. >but 'usuario' can be used to refer to a man or woman. As written in the footnote, It's perfectly reasonable to say in Spanish "la persona" and "las personas" (person/people in English), whose grammatical gender is feminine, to refer anyone without making any reference to their preferred gender, so it should be any problem to use that grammatical gender instead of the usual "neutral" one. From Latin's neutral case we have words like "el/la estudiante", "el/la marchante [de arte]", but the selection of the masculine as the default/neutral form is arguably biased towards one end. >Using this all the time it becomes confusing to read for me, due to >this I >change to the english manual. I understand that it can be tiresome, specially if you've been socialized as a male as I've been. On the other hand, more than a half of the Spanish speakers don't have to make any effort in order to understand it. I suppose that the same effort probably have been the done (usually beforehand) by people socialized as females when they read a document claiming (implicitly, as any language construct) that "usuario" applies to them too, but I only have anecdotical evidence... and the fact that women are really underrepresented (at least) in the development and free software community, so I try to take a feminist stance as my grain of sand to move this actual mountain. >I completely respect your job I want to be part of the community and >help, >I know this is a really delicate topic and I don't want to make a flame >war >or something like that. My approach is far from perfect: there are people who don't identify neither as male nor female, so the dissonance is still there, but I'm open to any new idea but using male gender as neutral one for the reasons I exposed there and here. Personally, I think it needs to be openly talked, it shouldn't be a flame war each time somebody mentions it. The conflict is already there, not speaking "about the elephant" doesn't make it disappear and only delays the possible solutions. Best regards, Miguel
Re: Gender neutral documentation
El July 30, 2019 10:10:21 PM UTC, Wilson Bustos escribió: >Hello everyone! >I would like to help to make guix packages, >I'm also reading documentation and watching videos about this. > >But I have some questions. >1- Do you have some document which explain what means 'gender neutral' >documentation. >and how that works in different languages such as Spanish? > The use of the feminine gender as neutral in the Spanish translation is intended as explained here: https://guix.gnu.org/manual/es/html_node/Envio-de-parches.html#DOCF40 >2- Reading the the Spanish version of the GNU manual in several pages >like >this one: >https://guix.gnu.org/manual/es/html_node/Caracteristicas.html#Caracter_00edsticas > >Has female sentence instead a 'normal' - 'neutral' sentence. >LIKE: `Opera en los perfiles de usuaria, y puede ser usada *con >privilegios >de usuaria normal*.` > >which say 'usuaria' to refer to the user, but that words is only used >to >refer to a woman. >but 'usuario' can be used to refer to a man or woman. As written in the footnote, It's perfectly reasonable to say in Spanish "la persona" and "las personas" (person/people in English), whose grammatical gender is feminine, to refer anyone without making any reference to their preferred gender, so it should be any problem to use that grammatical gender instead of the usual "neutral" one. From Latin's neutral case we have words like "el/la estudiante", "el/la marchante [de arte]", but the selection of the masculine as the default/neutral form is arguably biased towards one end. >Using this all the time it becomes confusing to read for me, due to >this I >change to the english manual. I understand that it can be tiresome, specially if you've been socialized as a male as I've been. On the other hand, more than a half of the Spanish speakers don't have to make any effort in order to understand it. I suppose that the same effort probably have been the done (usually beforehand) by people socialized as females when they read a document claiming (implicitly, as any language construct) that "usuario" applies to them too, but I only have anecdotical evidence... and the fact that women are really underrepresented (at least) in the development and free software community, so I try to take a feminist stance as my grain of sand to move this actual mountain. >I completely respect your job I want to be part of the community and >help, >I know this is a really delicate topic and I don't want to make a flame >war >or something like that. My approach is far from perfect: there are people who don't identify neither as male nor female, so the dissonance is still there, but I'm open to any new idea but using male gender as neutral one for the reasons I exposed there and here. Personally, I think it needs to be openly talked, it shouldn't be a flame war each time somebody mentions it. The conflict is already there, not speaking "about the elephant" doesn't make it disappear and only delays the possible solutions. Best regards, Miguel Hello, Wilson! Thank you for your interest in this awesome community. From my side, I've been taking more than expected to finish the translation and send some other patches, sorry for that. I hope to do it soon, but I only can answer with my phone at this moment. I'll try to answer your questions inline, let's see...
Gender neutral documentation
Hello everyone! I would like to help to make guix packages, I'm also reading documentation and watching videos about this. But I have some questions. 1- Do you have some document which explain what means 'gender neutral' documentation. and how that works in different languages such as Spanish? 2- Reading the the Spanish version of the GNU manual in several pages like this one: https://guix.gnu.org/manual/es/html_node/Caracteristicas.html#Caracter_00edsticas Has female sentence instead a 'normal' - 'neutral' sentence. LIKE: `Opera en los perfiles de usuaria, y puede ser usada *con privilegios de usuaria normal*.` which say 'usuaria' to refer to the user, but that words is only used to refer to a woman. but 'usuario' can be used to refer to a man or woman. Using this all the time it becomes confusing to read for me, due to this I change to the english manual. I completely respect your job I want to be part of the community and help, I know this is a really delicate topic and I don't want to make a flame war or something like that. I just want to know If the example that I give is product of a 'gender neutral' documentation rule or just was a mistake. Thank you so much for your help with this. Regards!
Re: We need your feedback of the documentation videos!
Laura, everyone, More badly-written notes from watching the other half of these fine video shows. I'll try to submit some patches myself, if I manage. Many are just me thinking aloud, not worth delaying a release. 03-help: - 00:40 It's a shame that Paul made such a good job of reading our old URL :-( All URLs in this video (and the others; fun!) should be tested for 404s & 308s before releasing the videos, although that's eminently scriptable. - 01:10 http://guix.gnu.org/help/ has changed. http://guix.gnu.org/contact/ would now make a better screenshot to match the audio at this timestamp. - 02:15 Was the title ‘subscribing to a mailman’ intentional? The conventional and boring choice would be ‘mailing list’ or just ‘list’. - 03:44 We can now add a ‘link’ to logs.guix.gnu.org, to give new users a sense of the place before they jump in, which can be intimidating. Since this logging is not done by Freenode, I'd move it to the bottom of the slide as its own top-level item. 04-packaging-part-one: - 00:13 This slide would be much easier to scan if both the arrows and the commands were vertically aligned. ‘get’ should be capitalised. ‘bootstrap’ is only ever run as ‘./bootstrap’. Let's write ‘./pre-inst-env’ as well since it's not in $PATH. In 02-everyday-use-part-two, commands like ‘guix install’ were set in the highly condensed sans-serif. The serif font used here is a much better choice for commands (and more efficient than monospace). Whatever the choice, I think it should be 100% consistent across videos. 04-packaging-part-two: The file names should sort spontaneously, for examply by using digits: 04-packaging-part-2. Even if this weren't an issue on A/V.gnu.org, people may upload them elsewhere if we're lucky, and 04-packaging-part-three currently plays before this one. 00:30 ‘Using’ → ‘Use’ to match the rest. ‘i.e.’ should be ‘e.g.’, or drop it entirely because: ‘R’ → ‘R packages’. If that really can't be made to fit we'll have to rewrite that; ‘R are’ doesn't work *and* sounds silly. - 01:15 I'm afraid this could be taken as a joke. Maybe expand the RHS of the ‘algorithm’ to include the steps later covered in part 3? They could be greyed out to show that we'll focus on ‘guix import’ in this video. More ‘backwards’ font usage: serif text, sans-serif command. - 02:25 ‘open with a text editor <> file’ → ‘open the <> file with a text editor’. Personally, I'd like to see ‘append alphabetically’ (or ‘add alphabetically’, since ‘append’ can be mistaken to mean ‘at the end’). The audio will still say ‘append’ but that's all right. 04-packaging-part-three: - 00:20 The difference between ‘2) Check’ and ‘3) Test’ is not clear to me. The audio doesn't explicitly mention these 4 steps. Using lone imperatives can be powerful, but these just confuse me. *Maybe*: if we chose expand the ‘packaging algorithm’ in part 2, we could re-use that here, with the other half greyed-out. There also appears to be an extra space before Test, but this might not be there in the code. - 00:55 Apparent extra space before Check (which should be ‘Check for’), same for Gender in the next slide. This always seems to happen on the 3rd item. Coincidence? The font rendering in general is just… off, but that's obviously not your fault. Typo: ‘Gender-neutral’. Here, too, I find the ‘random’ arrow positioning and inconsistent spacing (like ‘etc/’ at 01:50) a bit distracting. Lists like these always sound so negative. I love the videos. T G-R signature.asc Description: PGP signature
Help Installing GuixSD on ThinkPad X60 tablet
Hi! I'm having a problem I hope someone can help me with :( I just got a refurbished ThinkPad X60 Tablet with 3GB RAM and a 128 SSD, and I was reading about the free distros that are available so I could later install libreboot and saw there was Guix, and I found it great! But the thing is, it wouldn't work :( I downloaded the i686 iso and flashed it to a 3.0 USB Kingston DataTraveler with Balena Etcher, it worked fine, it booted, I followed the graphical install, set the language and keymap, location, and chose to use full disk with separate home partition and full encryption, I also selected i3 and openbox as desktops and lastly mozilla https and tor network. It installed without errors, and asked me to reboot, after that it asked me the / encryption passphrase, got to the grub screen, then asked me the home passphrase, aaand... it booted to Gnu Guile! And by typing ",help guix" it only showed me the option to switch to bournish language! I read every single command that ",help all" showed me but none helped, I saw also something about "repl" in the welcome message but tried it and the command didn't work either. Then I thought maybe it was something about the greeter not being installed so I reinstalled with Gnome and i3 but same thing, booted to Guile, and I don't know how to boot the os itself. If anyone knows what I did wrong or had a similar situation, I would gladly appreciate it, I really wanted to try out Guix :( If you need any more information, I can provide. Thanks in advance! Byron Elías Molina Hermosilla, Software Engineering Student, INACAP Renca, Chile.
Re: We need your feedback of the documentation videos!
Laura, I've finally watched these videos and can only agree that they look (and sound) very nice. I watched them with the archive.org player in IceCat on a Guix System. Laura Lazzati 写道： Does anybody else want to say something about the videos? :) Some things I noticed and that (I think) Ricardo hasn't mentioned yet. I know video is a lot of work, sorry for suggesting more. 01-installation-from-script: - 01:25 ‘The output tells us the signature is good.’ This made me chuckle: in typical GPG fashion, everything in its output implies the opposite unless you're already familiar with it. I realise it's far too late to touch the audio. Could we highlight ‘public key … imported’ after half a second or so? I don't know if the scripts allow easy highlighting of output text like that. - 01:35 and later: Our homepage has changed. Presumably as simple as running a search & replace on the repo before the videos are generated for the reals. 02-everyday-use-part-one: - 01:40 ‘we have our locales, that belong in the configuration of our system’ sounds wrong to me. Is it possible to cut after ‘locales’? Or am I misunderstanding what is meant? - 02:40 There's enough space to have the ‘user’ type something like ‘guix install foobar:gui’ while talking about outputs (without showing the result of that command). 02-everyday-use-part-two: - 0:25 ‘package/s’ needlessly caught my attention (I'd expect ‘package(s)’) but this might be a regional thing. Same for ‘latest Guix version\ninstalled’ (‘latest installed Guix version’). - 0:25 I agree that the second ‘guix pull’ looks odd (and cramped). You could replace the vertical arrow with ‘&&’ or add a ‘then’ as done in the next slide. - After dropping it, you'll have room to add ‘[regex]’ to the end of ‘guix package --upgrade’ and help combat a common misunderstanding :-) There's room even if you don't. All videos: - The empty line between commands and their output (but none the between the output and the next command) looks strange to me. There should either be no empty line (as in a real shell) or another one before the next command for visual clarity. Now I need a break, because I'm that grumpy person who never watches videos for technical information. Thank you, again, T G-R signature.asc Description: PGP signature
Re: We need your feedback of the documentation videos!
Also I believe how to add services on Guix System is something newcomers may struggle with and could use a video for, even though it is so much easier on Guix System than on other distros. Regards, Florian
Re: We need your feedback of the documentation videos!
On Wed, Jul 17, 2019 at 11:44:09AM +0200, Ricardo Wurmus wrote: > - the command “guix package --install hello” is used, but “guix install > hello” might be better > On one hand, one understands that `guix package` does everything related to packages. That is nice. `guix install` is just an alias. But it is quicker to type. Regards, Florian
Re: We need your feedback of the documentation videos!
Hi! Does anybody else want to say something about the videos? :) Regards! Laura
Re: Managing user environments
Pierre Neidhardt writes: > I can see quite some overlap with Shepherd User Services: > https://lists.gnu.org/archive/html/guix-devel/2019-02/msg00128.html > > What do you think? Yes, I felt reminded of Shepherd User Services as well. > The main difference I can see with Julien's approach is that the > declarativeness is not enforced since home would not be read-only. This could still be done as part of the service actions if desired. -- Ricardo
Re: Managing user environments
This looks fantastic! I can see quite some overlap with Shepherd User Services: https://lists.gnu.org/archive/html/guix-devel/2019-02/msg00128.html What do you think? If we implement shepherd user services, we would essentially be able to declare most (all?) of a user home folder. The main difference I can see with Julien's approach is that the declarativeness is not enforced since home would not be read-only. Home would be initialized declaratively, but then the user or any program is able to overwrite files in home. Which may or may not be the desired behaviour. Cheers! -- Pierre Neidhardt https://ambrevar.xyz/ signature.asc Description: PGP signature
Re: git-fetch origin output is read-only - and reproducibility
Hi, On 29. Jul 2019, at 18:10, Ricardo Wurmus wrote: > Most build systems inherit from the gnu-build-system, so they’ll get to > reuse the “unpack” phase, which conveniently checks if the source is a > tarball. In the case of Java archives it doesn’t do the right thing, > because it doesn’t know about Jars, so the ant-build-system overrides > that phase, etc. > > Dealing with sources sometimes requires special knowledge and the build > system might be best equipped to employ that knowledge. > > What would you suggest the fetchers implement to guarantee that the > sources will always be of some expected form? I would suggest that they specify the archive type, and either - repack the archive to a standard format, e.g. .tar.gz (this should then also apply to sources that are local directory trees) - unpack the archive to a directory tree An alternative change that would make the whole setup a bit less confusing would be to factor all the “standard” build system stuff out of gnu-build-system and into a base-build-system that provides source unpacking and phase handling and nothing else. I originally ran into this surprise by basing things on trivial-build-system, getting things to work with a local directory, then seeing that my apparently functioning build system failed once I referred to a git checkout because that packs to a tarball. Robert
