How do I get deboostrap (via live-build) to use Raspbian's release keyring?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
3
down vote

favorite












I am trying to use live-build 5.0 on Debian squeeze to build a Raspbian live image. The sudo lb build command fails during the debootstrap phase, at the step:



I: Checking Release signature
E: Release signed by unknown key (key id 9165938D90FDDD2E)


I have tried (on the build system):



  • installing the Raspbian repo key using sudo apt-key add

  • manually installing raspbian-archive-keyring_20120528.2_all.deb

  • adding the Raspbian key to config/archives/raspbian.key.(binary|chroot) (ie. from /usr/share/keyrings/raspbian-archive-keyring.gpg)

  • prepending DEBOOTSTRAP_OPTIONS="--keyring=/usr/share/keyrings/raspbian-archive-keyring.gpg" to lb config and lb build

  • same, but for /etc/apt/trusted.gpg

  • including --keyring-packages "raspbian-archive-keyring" in my auto/config

None of it worked. What do I need to do to tell debootstrap to use a different keyring? I don't want to tell it not to verify anything at all.






debian raspbian







share|improve this question





















  • Try wget https://archive.raspbian.org/raspbian.public.key gpg --import raspbian.public.key debootstrap --keyring /root/.gnupg/pubring.gpg If the above fails then birchroad.wordpress.com/2012/06/09/… may be of use to you.
    – ChrisK
    Feb 8 '16 at 15:31














up vote
3
down vote

favorite












I am trying to use live-build 5.0 on Debian squeeze to build a Raspbian live image. The sudo lb build command fails during the debootstrap phase, at the step:



I: Checking Release signature
E: Release signed by unknown key (key id 9165938D90FDDD2E)


I have tried (on the build system):



  • installing the Raspbian repo key using sudo apt-key add

  • manually installing raspbian-archive-keyring_20120528.2_all.deb

  • adding the Raspbian key to config/archives/raspbian.key.(binary|chroot) (ie. from /usr/share/keyrings/raspbian-archive-keyring.gpg)

  • prepending DEBOOTSTRAP_OPTIONS="--keyring=/usr/share/keyrings/raspbian-archive-keyring.gpg" to lb config and lb build

  • same, but for /etc/apt/trusted.gpg

  • including --keyring-packages "raspbian-archive-keyring" in my auto/config

None of it worked. What do I need to do to tell debootstrap to use a different keyring? I don't want to tell it not to verify anything at all.






debian raspbian







share|improve this question





















  • Try wget https://archive.raspbian.org/raspbian.public.key gpg --import raspbian.public.key debootstrap --keyring /root/.gnupg/pubring.gpg If the above fails then birchroad.wordpress.com/2012/06/09/… may be of use to you.
    – ChrisK
    Feb 8 '16 at 15:31












up vote
3
down vote

favorite









up vote
3
down vote

favorite











I am trying to use live-build 5.0 on Debian squeeze to build a Raspbian live image. The sudo lb build command fails during the debootstrap phase, at the step:



I: Checking Release signature
E: Release signed by unknown key (key id 9165938D90FDDD2E)


I have tried (on the build system):



  • installing the Raspbian repo key using sudo apt-key add

  • manually installing raspbian-archive-keyring_20120528.2_all.deb

  • adding the Raspbian key to config/archives/raspbian.key.(binary|chroot) (ie. from /usr/share/keyrings/raspbian-archive-keyring.gpg)

  • prepending DEBOOTSTRAP_OPTIONS="--keyring=/usr/share/keyrings/raspbian-archive-keyring.gpg" to lb config and lb build

  • same, but for /etc/apt/trusted.gpg

  • including --keyring-packages "raspbian-archive-keyring" in my auto/config

None of it worked. What do I need to do to tell debootstrap to use a different keyring? I don't want to tell it not to verify anything at all.






debian raspbian







share|improve this question













I am trying to use live-build 5.0 on Debian squeeze to build a Raspbian live image. The sudo lb build command fails during the debootstrap phase, at the step:



I: Checking Release signature
E: Release signed by unknown key (key id 9165938D90FDDD2E)


I have tried (on the build system):



  • installing the Raspbian repo key using sudo apt-key add

  • manually installing raspbian-archive-keyring_20120528.2_all.deb

  • adding the Raspbian key to config/archives/raspbian.key.(binary|chroot) (ie. from /usr/share/keyrings/raspbian-archive-keyring.gpg)

  • prepending DEBOOTSTRAP_OPTIONS="--keyring=/usr/share/keyrings/raspbian-archive-keyring.gpg" to lb config and lb build

  • same, but for /etc/apt/trusted.gpg

  • including --keyring-packages "raspbian-archive-keyring" in my auto/config

None of it worked. What do I need to do to tell debootstrap to use a different keyring? I don't want to tell it not to verify anything at all.






debian raspbian




debian raspbian






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Jan 21 '16 at 3:30









detly

1,36341424




1,36341424











  • Try wget https://archive.raspbian.org/raspbian.public.key gpg --import raspbian.public.key debootstrap --keyring /root/.gnupg/pubring.gpg If the above fails then birchroad.wordpress.com/2012/06/09/… may be of use to you.
    – ChrisK
    Feb 8 '16 at 15:31
















  • Try wget https://archive.raspbian.org/raspbian.public.key gpg --import raspbian.public.key debootstrap --keyring /root/.gnupg/pubring.gpg If the above fails then birchroad.wordpress.com/2012/06/09/… may be of use to you.
    – ChrisK
    Feb 8 '16 at 15:31















Try wget https://archive.raspbian.org/raspbian.public.key gpg --import raspbian.public.key debootstrap --keyring /root/.gnupg/pubring.gpg If the above fails then birchroad.wordpress.com/2012/06/09/… may be of use to you.
– ChrisK
Feb 8 '16 at 15:31




Try wget https://archive.raspbian.org/raspbian.public.key gpg --import raspbian.public.key debootstrap --keyring /root/.gnupg/pubring.gpg If the above fails then birchroad.wordpress.com/2012/06/09/… may be of use to you.
– ChrisK
Feb 8 '16 at 15:31










2 Answers
2






active

oldest

votes

















up vote
2
down vote



accepted










This was a very basic mistake. I was prepending DEBOOTSTRAP_OPTIONS="--keyring=/usr/share/keyrings/raspbian-archive-keyring.gpg" to lb config && sudo lb build, not realising that sudo does not allow environment variables through (because of the Defaults env_reset line in sudoers).



When I invoked with sudo DEBOOTSTRAP_OPTIONS="--keyring=/usr/share/keyrings/raspbian-archive-keyring.gpg" lb build, it was successful.






share|improve this answer



























    up vote
    0
    down vote













    As root run:



    wget -qO - https://archive.raspbian.org/raspbian.public.key | gpg --import -
    debootstrap --keyring /root/.gnupg/pubring.kbx ...





    share|improve this answer




















      Your Answer







      StackExchange.ready(function()
      var channelOptions =
      tags: "".split(" "),
      id: "106"
      ;
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function()
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled)
      StackExchange.using("snippets", function()
      createEditor();
      );

      else
      createEditor();

      );

      function createEditor()
      StackExchange.prepareEditor(
      heartbeatType: 'answer',
      convertImagesToLinks: false,
      noModals: false,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: null,
      bindNavPrevention: true,
      postfix: "",
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      );



      );













       

      draft saved


      draft discarded


















      StackExchange.ready(
      function ()
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f256702%2fhow-do-i-get-deboostrap-via-live-build-to-use-raspbians-release-keyring%23new-answer', 'question_page');

      );

      Post as a guest

















      2 Answers
      2






      active

      oldest

      votes








      2 Answers
      2






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes








      up vote
      2
      down vote



      accepted










      This was a very basic mistake. I was prepending DEBOOTSTRAP_OPTIONS="--keyring=/usr/share/keyrings/raspbian-archive-keyring.gpg" to lb config && sudo lb build, not realising that sudo does not allow environment variables through (because of the Defaults env_reset line in sudoers).



      When I invoked with sudo DEBOOTSTRAP_OPTIONS="--keyring=/usr/share/keyrings/raspbian-archive-keyring.gpg" lb build, it was successful.






      share|improve this answer
























        up vote
        2
        down vote



        accepted










        This was a very basic mistake. I was prepending DEBOOTSTRAP_OPTIONS="--keyring=/usr/share/keyrings/raspbian-archive-keyring.gpg" to lb config && sudo lb build, not realising that sudo does not allow environment variables through (because of the Defaults env_reset line in sudoers).



        When I invoked with sudo DEBOOTSTRAP_OPTIONS="--keyring=/usr/share/keyrings/raspbian-archive-keyring.gpg" lb build, it was successful.






        share|improve this answer






















          up vote
          2
          down vote



          accepted







          up vote
          2
          down vote



          accepted






          This was a very basic mistake. I was prepending DEBOOTSTRAP_OPTIONS="--keyring=/usr/share/keyrings/raspbian-archive-keyring.gpg" to lb config && sudo lb build, not realising that sudo does not allow environment variables through (because of the Defaults env_reset line in sudoers).



          When I invoked with sudo DEBOOTSTRAP_OPTIONS="--keyring=/usr/share/keyrings/raspbian-archive-keyring.gpg" lb build, it was successful.






          share|improve this answer












          This was a very basic mistake. I was prepending DEBOOTSTRAP_OPTIONS="--keyring=/usr/share/keyrings/raspbian-archive-keyring.gpg" to lb config && sudo lb build, not realising that sudo does not allow environment variables through (because of the Defaults env_reset line in sudoers).



          When I invoked with sudo DEBOOTSTRAP_OPTIONS="--keyring=/usr/share/keyrings/raspbian-archive-keyring.gpg" lb build, it was successful.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Feb 7 '16 at 19:12









          detly

          1,36341424




          1,36341424






















              up vote
              0
              down vote













              As root run:



              wget -qO - https://archive.raspbian.org/raspbian.public.key | gpg --import -
              debootstrap --keyring /root/.gnupg/pubring.kbx ...





              share|improve this answer
























                up vote
                0
                down vote













                As root run:



                wget -qO - https://archive.raspbian.org/raspbian.public.key | gpg --import -
                debootstrap --keyring /root/.gnupg/pubring.kbx ...





                share|improve this answer






















                  up vote
                  0
                  down vote










                  up vote
                  0
                  down vote









                  As root run:



                  wget -qO - https://archive.raspbian.org/raspbian.public.key | gpg --import -
                  debootstrap --keyring /root/.gnupg/pubring.kbx ...





                  share|improve this answer












                  As root run:



                  wget -qO - https://archive.raspbian.org/raspbian.public.key | gpg --import -
                  debootstrap --keyring /root/.gnupg/pubring.kbx ...






                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Aug 17 at 8:49









                  dimir

                  1413




                  1413



























                       

                      draft saved


                      draft discarded















































                       


                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function ()
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f256702%2fhow-do-i-get-deboostrap-via-live-build-to-use-raspbians-release-keyring%23new-answer', 'question_page');

                      );

                      Post as a guest
































































                      -

                      Popular posts from this blog

                      How to check contact read email or not when send email to Individual?

                      Image
                      Clash Royale CLAN TAG #URR8PPP up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this question asked Sep 26 at 0:12 ToanLuong 49 9 add a comment  |  up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this questi...
                      Read more

                      Displaying single band from multi-band raster using QGIS

                      Image
                      Clash Royale CLAN TAG #URR8PPP 1 How can I extract a single band from multi-band raster in QGIS? I have an remote sensed image which has 6 bands (including NDVI band), I want to display each band separately, but have no idea how to do. I have seen some questions similar here but none worked for me. The original image (has 6 bands) is: I want to display the band 6 which should be like this: But I tried gdal_translate, and couldn't get the correct result. What I have got is: qgis raster multi-band share | improve this question edited Mar 5 at 0:53 Summer asked Mar 4 at 6:42 Summer Summer 23 6 Is this any help gis.stackexchange.com/questions/220658/… ? if not gis.stackexchange.com/questions/62133/… might help. – Michael Stimson Mar 4 at 6:46 Thanks for answering but when I used gdal_translate, qgis showed that 'Error 4: Kayena.tif: No such file or directory". Would you know how to fi...
                      Read more

                      How many registers does an x86_64 CPU actually have?

                      Image
                      Clash Royale CLAN TAG #URR8PPP up vote 2 down vote favorite I am currently learning reverse engineering and am studying the flags register. I had in my mind that rflags was just another name for one of the 16 general purpose registers, for example rax or rbx . But it looks like rflags is actually an additional register. So that makes 17 registers in total... how many more could there be? I have spent at least an hour on this and found numerous different answers. The best answer so far is this, which says that there are 40 registers in total. 16 General Purpose Registers 2 Status Registers 6 Code Segment Registers 16 SSE Registers 8 FPU/MMX Registers But if I add that up, I get 48. Could anybody provide an official answer on how many registers an x86_64 CPU has (e.g. an Intel i7). Additionally, I have seen references to 'hardware' and 'architectural' registers. What are those registers and how many are there? register x86-64 share | improve this...
                      Read more