diff options
Diffstat (limited to 'doc')
4 files changed, 150 insertions, 0 deletions
diff --git a/doc/forum/__42____42___warning:___42____42___Your___126____47__.propellor__47___is_out_of_date../comment_14_a65bf71d16401e2621f1dff93701247d._comment b/doc/forum/__42____42___warning:___42____42___Your___126____47__.propellor__47___is_out_of_date../comment_14_a65bf71d16401e2621f1dff93701247d._comment new file mode 100644 index 00000000..c5427cd7 --- /dev/null +++ b/doc/forum/__42____42___warning:___42____42___Your___126____47__.propellor__47___is_out_of_date../comment_14_a65bf71d16401e2621f1dff93701247d._comment @@ -0,0 +1,35 @@ +[[!comment format=mdwn + username="picca" + avatar="http://cdn.libravatar.org/avatar/7e61c80d28018b10d31f6db7dddb864c" + subject="comment 14" + date="2018-03-04T10:41:01Z" + content=""" +Hello, sorry to bother you with this BUT :)) + +Now I have the right message which explain how to upgrade my .propellor +(sorry for the french) + + picca@mordor:~$ propellor + Fusion automatique de src/Propellor/Property/Systemd.hs + Fusion automatique de src/Propellor/Property/SiteSpecific/JoeySites.hs + Fusion automatique de src/Propellor/Property/Git.hs + Fusion automatique de src/Propellor/Git/VerifiedBranch.hs + Fusion automatique de src/Propellor/Git.hs + Fusion automatique de src/Propellor/EnsureProperty.hs + Fusion automatique de src/Propellor/DotDir.hs + Fusion automatique de propellor.cabal + Fusion automatique de joeyconfig.hs + Fusion automatique de doc/README.mdwn + Fusion automatique de debian/changelog + ** warning: ** Your ~/.propellor/ is out of date.. + A newer upstream version is available in /usr/src/propellor/propellor.git + To merge it, run: git merge upstream/master + +but when I try to do the merge, I get this error message + + picca@mordor:~/.propellor$ LANG=C git merge upstream/master + fatal: refusing to merge unrelated histories + +How can I help to solve this issue ? + +"""]] diff --git a/doc/forum/can__39__t_get_Apt.trustsKey_to_work.mdwn b/doc/forum/can__39__t_get_Apt.trustsKey_to_work.mdwn new file mode 100644 index 00000000..3c0853db --- /dev/null +++ b/doc/forum/can__39__t_get_Apt.trustsKey_to_work.mdwn @@ -0,0 +1,90 @@ +I've been hitting a problem when importing APT keys on a debian stretch VM. I'm using a property like + + mybox :: Host + mybox = host "henry1.home" $ props + & osDebian (Stable "stretch") X86_64 + & Apt.stdSourcesList + & Apt.unattendedUpgrades + & installKubernetes + + + installKubernetes :: Property DebianLike + installKubernetes = Apt.installed ["kubelet", "kubeadm", "kubectl"] + `requires` Apt.setSourcesListD ["deb http://apt.kubernetes.io/ kubernetes-xenial main"] "google-cloud" + `requires` Apt.trustsKey googleKey + + googleKey :: Apt.AptKey + googleKey = + Apt.AptKey "google-key" $ unlines + [ "-----BEGIN PGP PUBLIC KEY BLOCK-----" + , "" + , "mQENBFUd6rIBCAD6mhKRHDn3UrCeLDp7U5IE7AhhrOCPpqGF7mfTemZYHf/5Jdjx" + , "cOxoSFlK7zwmFr3lVqJ+tJ9L1wd1K6P7RrtaNwCiZyeNPf/Y86AJ5NJwBe0VD0xH" + , "TXzPNTqRSByVYtdN94NoltXUYFAAPZYQls0x0nUD1hLMlOlC2HdTPrD1PMCnYq/N" + , "uL/Vk8sWrcUt4DIS+0RDQ8tKKe5PSV0+PnmaJvdF5CKawhh0qGTklS2MXTyKFoqj" + , "XgYDfY2EodI9ogT/LGr9Lm/+u4OFPvmN9VN6UG+s0DgJjWvpbmuHL/ZIRwMEn/tp" + , "uneaLTO7h1dCrXC849PiJ8wSkGzBnuJQUbXnABEBAAG0QEdvb2dsZSBDbG91ZCBQ" + , "YWNrYWdlcyBBdXRvbWF0aWMgU2lnbmluZyBLZXkgPGdjLXRlYW1AZ29vZ2xlLmNv" + , "bT6JAT4EEwECACgFAlUd6rICGy8FCQWjmoAGCwkIBwMCBhUIAgkKCwQWAgMBAh4B" + , "AheAAAoJEDdGwginMXsPcLcIAKi2yNhJMbu4zWQ2tM/rJFovazcY28MF2rDWGOnc" + , "9giHXOH0/BoMBcd8rw0lgjmOosBdM2JT0HWZIxC/Gdt7NSRA0WOlJe04u82/o3OH" + , "WDgTdm9MS42noSP0mvNzNALBbQnlZHU0kvt3sV1YsnrxljoIuvxKWLLwren/GVsh" + , "FLPwONjw3f9Fan6GWxJyn/dkX3OSUGaduzcygw51vksBQiUZLCD2Tlxyr9NvkZYT" + , "qiaWW78L6regvATsLc9L/dQUiSMQZIK6NglmHE+cuSaoK0H4ruNKeTiQUw/EGFaL" + , "ecay6Qy/s3Hk7K0QLd+gl0hZ1w1VzIeXLo2BRlqnjOYFX4A=" + , "=HVTm" + , "-----END PGP PUBLIC KEY BLOCK-----" + ] + + +the import works fine, but the packages fail to install because the key isn't valid, i can list the key + + root@henry1:~# apt-key list | grep -A 6 google-key + Warning: apt-key output should not be parsed (stdout is not a terminal) + /etc/apt/trusted.gpg.d/google-key.gpg + ------------------------------------- + pub rsa2048 2015-04-03 [SCEA] [expires: 2018-04-02] + D0BC 747F D8CA F711 7500 D6FA 3746 C208 A731 7B0F + uid [ unknown] Google Cloud Packages Automatic Signing Key <gc-team@google.com> + + +but i can't export it. I've tried the gpg command listed in the Apt.trustsKey function and running it locally (on the vm) with a local file doesn't work either. + + root@henry1:~# apt-key export D6FA3746A7317B0F + gpg: [don't know]: invalid packet (ctb=00) + gpg: WARNING: nothing exported + gpg: key export failed: Invalid packet + + +Gpg version info + + root@henry1:~# gpg --version + gpg (GnuPG) 2.1.18 + libgcrypt 1.7.6-beta + Copyright (C) 2017 Free Software Foundation, Inc. + License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html> + This is free software: you are free to change and redistribute it. + There is NO WARRANTY, to the extent permitted by law. + + Home: /root/.gnupg + Supported algorithms: + Pubkey: RSA, ELG, DSA, ECDH, ECDSA, EDDSA + Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH, + CAMELLIA128, CAMELLIA192, CAMELLIA256 + Hash: SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224 + Compression: Uncompressed, ZIP, ZLIB, BZIP2 + +I ended up changing the Apt.trustsKey command to a version which uses apt-key and everything works now + + trustsKey' :: AptKey -> Property DebianLike + trustsKey' k = check (not <$> doesFileExist f) $ property desc $ makeChange $ do + withHandle StdinHandle createProcessSuccess + (proc "apt-key" ["--keyring", f, "add", "-"]) $ \h -> do + hPutStr h (pubkey k) + hClose h + nukeFile $ f ++ "~" -- gpg dropping + where + desc = "apt trusts key " ++ keyname k + f = aptKeyFile k + +Any thoughts as to why this wouldn't be working? Would it be reasonable to change this command upstream? diff --git a/doc/forum/can__39__t_get_Apt.trustsKey_to_work/comment_1_8ee5b69f068c369e88c31c639d692f60._comment b/doc/forum/can__39__t_get_Apt.trustsKey_to_work/comment_1_8ee5b69f068c369e88c31c639d692f60._comment new file mode 100644 index 00000000..b1f82b19 --- /dev/null +++ b/doc/forum/can__39__t_get_Apt.trustsKey_to_work/comment_1_8ee5b69f068c369e88c31c639d692f60._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2018-03-01T22:20:54Z" + content=""" +I added trustsKey in 2014, but my current config is not using +it for anything, so it seems likely it's bitrotted in some way. +And there's no rationalle documented for why it manually drives gpg. + +I've applied your change to use apt-key. + +I wonder if the nukeFile of the "gpg dropping" is actually needed +anymore? +"""]] diff --git a/doc/forum/dm-crypt__47__LUKS_encryption_and_key_management/comment_2_ffca1d5942d4fd152657dd3afe21b935._comment b/doc/forum/dm-crypt__47__LUKS_encryption_and_key_management/comment_2_ffca1d5942d4fd152657dd3afe21b935._comment new file mode 100644 index 00000000..93248324 --- /dev/null +++ b/doc/forum/dm-crypt__47__LUKS_encryption_and_key_management/comment_2_ffca1d5942d4fd152657dd3afe21b935._comment @@ -0,0 +1,11 @@ +[[!comment format=mdwn + username="dominik" + avatar="http://cdn.libravatar.org/avatar/41b0caab63708c0b81d8aeda611afad5" + subject="LUKS desired ;-)" + date="2018-03-01T11:40:27Z" + content=""" +I'd love to use LUKS partitions in Propeller. + +Thanks Joey. + +"""]] |