live-build behind a proxy at lb bootstrap_archive-keys step gets Clearsigned file isn't valid, got 'NODATA'

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











up vote
0
down vote

favorite












I've been trying to do the steps from 18.4 from here:
https://debian-live.alioth.debian.org/live-manual/stable/manual/html/live-manual.en.html#847



When running the lb build I get an error at the lb bootstrap_archive-keys step.



My setup is a Windows 10 host running a Debian Jessie 8.4 VMWare guest. I've tried both NAT and Bridged network setup, but in both cases I get the same error.
The machine is connected to the company network which requires proxy authentication.



The machine is connected to the company network which requires proxy authentication.
Before running the lb build I've set from command line the http_proxy, https_proxy and ftp_proxy variables like this:



> export http_proxy=http://myuser:mypassword@192.168.1.1:3128
> export https_proxy=http://myuser:mypassword@192.168.1.1:3128
> export ftp_proxy=http://myuser:mypassword@192.168.1.1:3128


In the auto/config file for live-build I've specified the --apt-http-proxy and the --apt-ftp-proxy parameters so the config file looks like this:



#!/bin/sh

lb config noauto
--architectures i386
--linux-flavours 686-pae
--apt-http-proxy http://myuser:mypassword@192.168.1.1:3128
--apt-ftp-proxy http://myuser:mypassword@192.168.1.1:3128
"$@"


The error I get at the lb bootstrap_archive_keys step is:



[2018-04-19 16:43:27] lb bootstrap_archive-keys 
Get:1 http://ftp.debian.org jessie InRelease [2829 B]
Splitting up /var/lib/apt/lists/partial/ftp.debian.org_debian_dists_jessie_InRelease into data and signature failedIgn http://ftp.debian.org jessie InRelease
E: GPG error: http://ftp.debian.org jessie InRelease: Clearsigned file isn't valid, got 'NODATA' (does the network require authentication?)
P: Begin unmounting filesystems...
P: Saving caches...
Reading package lists...
Building dependency tree...


The previous steps: lb build noauto, lb bootstrap, lb bootstrap_cache restore, lb bootstrap_cdebootstrap, lb bootstrap_debootstrap work fine.



I've searched for the GPG error: http://ftp.debian.org jessie InRelease: Clearsigned file isn't valid, got 'NODATA' (does the network require authentication?) error. Most people have the problem of a transparent proxy (like here: https://askubuntu.com/questions/474549/got-nodata-issue-nodata-does-the-network-require-authentication) which is not the case for me, it's not transparent, it's there I know it :) and also an apt-get update works properly (proxy set in /etc/apt/apt.conf)



There was an older discussion with a very similar issue to mine here: https://lists.debian.org/debian-live/2013/06/msg00078.html but this was quite a while ago, and it was marked as fixed later versions. I'm using the latest version of live-build, 4.0.3-1 and live-tools 4.0.2-1.1



I can confirm that the problem doesn't appear if the system has a direct internet connection.



I would really appreciate if someone could shed some light on this problem, or if someone met similar problems.



Thanks,
Gabor



P.S. This used to work in this setup a while back (last summer or something like that). What could have changed since then?







share|improve this question























    up vote
    0
    down vote

    favorite












    I've been trying to do the steps from 18.4 from here:
    https://debian-live.alioth.debian.org/live-manual/stable/manual/html/live-manual.en.html#847



    When running the lb build I get an error at the lb bootstrap_archive-keys step.



    My setup is a Windows 10 host running a Debian Jessie 8.4 VMWare guest. I've tried both NAT and Bridged network setup, but in both cases I get the same error.
    The machine is connected to the company network which requires proxy authentication.



    The machine is connected to the company network which requires proxy authentication.
    Before running the lb build I've set from command line the http_proxy, https_proxy and ftp_proxy variables like this:



    > export http_proxy=http://myuser:mypassword@192.168.1.1:3128
    > export https_proxy=http://myuser:mypassword@192.168.1.1:3128
    > export ftp_proxy=http://myuser:mypassword@192.168.1.1:3128


    In the auto/config file for live-build I've specified the --apt-http-proxy and the --apt-ftp-proxy parameters so the config file looks like this:



    #!/bin/sh

    lb config noauto
    --architectures i386
    --linux-flavours 686-pae
    --apt-http-proxy http://myuser:mypassword@192.168.1.1:3128
    --apt-ftp-proxy http://myuser:mypassword@192.168.1.1:3128
    "$@"


    The error I get at the lb bootstrap_archive_keys step is:



    [2018-04-19 16:43:27] lb bootstrap_archive-keys 
    Get:1 http://ftp.debian.org jessie InRelease [2829 B]
    Splitting up /var/lib/apt/lists/partial/ftp.debian.org_debian_dists_jessie_InRelease into data and signature failedIgn http://ftp.debian.org jessie InRelease
    E: GPG error: http://ftp.debian.org jessie InRelease: Clearsigned file isn't valid, got 'NODATA' (does the network require authentication?)
    P: Begin unmounting filesystems...
    P: Saving caches...
    Reading package lists...
    Building dependency tree...


    The previous steps: lb build noauto, lb bootstrap, lb bootstrap_cache restore, lb bootstrap_cdebootstrap, lb bootstrap_debootstrap work fine.



    I've searched for the GPG error: http://ftp.debian.org jessie InRelease: Clearsigned file isn't valid, got 'NODATA' (does the network require authentication?) error. Most people have the problem of a transparent proxy (like here: https://askubuntu.com/questions/474549/got-nodata-issue-nodata-does-the-network-require-authentication) which is not the case for me, it's not transparent, it's there I know it :) and also an apt-get update works properly (proxy set in /etc/apt/apt.conf)



    There was an older discussion with a very similar issue to mine here: https://lists.debian.org/debian-live/2013/06/msg00078.html but this was quite a while ago, and it was marked as fixed later versions. I'm using the latest version of live-build, 4.0.3-1 and live-tools 4.0.2-1.1



    I can confirm that the problem doesn't appear if the system has a direct internet connection.



    I would really appreciate if someone could shed some light on this problem, or if someone met similar problems.



    Thanks,
    Gabor



    P.S. This used to work in this setup a while back (last summer or something like that). What could have changed since then?







    share|improve this question





















      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      I've been trying to do the steps from 18.4 from here:
      https://debian-live.alioth.debian.org/live-manual/stable/manual/html/live-manual.en.html#847



      When running the lb build I get an error at the lb bootstrap_archive-keys step.



      My setup is a Windows 10 host running a Debian Jessie 8.4 VMWare guest. I've tried both NAT and Bridged network setup, but in both cases I get the same error.
      The machine is connected to the company network which requires proxy authentication.



      The machine is connected to the company network which requires proxy authentication.
      Before running the lb build I've set from command line the http_proxy, https_proxy and ftp_proxy variables like this:



      > export http_proxy=http://myuser:mypassword@192.168.1.1:3128
      > export https_proxy=http://myuser:mypassword@192.168.1.1:3128
      > export ftp_proxy=http://myuser:mypassword@192.168.1.1:3128


      In the auto/config file for live-build I've specified the --apt-http-proxy and the --apt-ftp-proxy parameters so the config file looks like this:



      #!/bin/sh

      lb config noauto
      --architectures i386
      --linux-flavours 686-pae
      --apt-http-proxy http://myuser:mypassword@192.168.1.1:3128
      --apt-ftp-proxy http://myuser:mypassword@192.168.1.1:3128
      "$@"


      The error I get at the lb bootstrap_archive_keys step is:



      [2018-04-19 16:43:27] lb bootstrap_archive-keys 
      Get:1 http://ftp.debian.org jessie InRelease [2829 B]
      Splitting up /var/lib/apt/lists/partial/ftp.debian.org_debian_dists_jessie_InRelease into data and signature failedIgn http://ftp.debian.org jessie InRelease
      E: GPG error: http://ftp.debian.org jessie InRelease: Clearsigned file isn't valid, got 'NODATA' (does the network require authentication?)
      P: Begin unmounting filesystems...
      P: Saving caches...
      Reading package lists...
      Building dependency tree...


      The previous steps: lb build noauto, lb bootstrap, lb bootstrap_cache restore, lb bootstrap_cdebootstrap, lb bootstrap_debootstrap work fine.



      I've searched for the GPG error: http://ftp.debian.org jessie InRelease: Clearsigned file isn't valid, got 'NODATA' (does the network require authentication?) error. Most people have the problem of a transparent proxy (like here: https://askubuntu.com/questions/474549/got-nodata-issue-nodata-does-the-network-require-authentication) which is not the case for me, it's not transparent, it's there I know it :) and also an apt-get update works properly (proxy set in /etc/apt/apt.conf)



      There was an older discussion with a very similar issue to mine here: https://lists.debian.org/debian-live/2013/06/msg00078.html but this was quite a while ago, and it was marked as fixed later versions. I'm using the latest version of live-build, 4.0.3-1 and live-tools 4.0.2-1.1



      I can confirm that the problem doesn't appear if the system has a direct internet connection.



      I would really appreciate if someone could shed some light on this problem, or if someone met similar problems.



      Thanks,
      Gabor



      P.S. This used to work in this setup a while back (last summer or something like that). What could have changed since then?







      share|improve this question











      I've been trying to do the steps from 18.4 from here:
      https://debian-live.alioth.debian.org/live-manual/stable/manual/html/live-manual.en.html#847



      When running the lb build I get an error at the lb bootstrap_archive-keys step.



      My setup is a Windows 10 host running a Debian Jessie 8.4 VMWare guest. I've tried both NAT and Bridged network setup, but in both cases I get the same error.
      The machine is connected to the company network which requires proxy authentication.



      The machine is connected to the company network which requires proxy authentication.
      Before running the lb build I've set from command line the http_proxy, https_proxy and ftp_proxy variables like this:



      > export http_proxy=http://myuser:mypassword@192.168.1.1:3128
      > export https_proxy=http://myuser:mypassword@192.168.1.1:3128
      > export ftp_proxy=http://myuser:mypassword@192.168.1.1:3128


      In the auto/config file for live-build I've specified the --apt-http-proxy and the --apt-ftp-proxy parameters so the config file looks like this:



      #!/bin/sh

      lb config noauto
      --architectures i386
      --linux-flavours 686-pae
      --apt-http-proxy http://myuser:mypassword@192.168.1.1:3128
      --apt-ftp-proxy http://myuser:mypassword@192.168.1.1:3128
      "$@"


      The error I get at the lb bootstrap_archive_keys step is:



      [2018-04-19 16:43:27] lb bootstrap_archive-keys 
      Get:1 http://ftp.debian.org jessie InRelease [2829 B]
      Splitting up /var/lib/apt/lists/partial/ftp.debian.org_debian_dists_jessie_InRelease into data and signature failedIgn http://ftp.debian.org jessie InRelease
      E: GPG error: http://ftp.debian.org jessie InRelease: Clearsigned file isn't valid, got 'NODATA' (does the network require authentication?)
      P: Begin unmounting filesystems...
      P: Saving caches...
      Reading package lists...
      Building dependency tree...


      The previous steps: lb build noauto, lb bootstrap, lb bootstrap_cache restore, lb bootstrap_cdebootstrap, lb bootstrap_debootstrap work fine.



      I've searched for the GPG error: http://ftp.debian.org jessie InRelease: Clearsigned file isn't valid, got 'NODATA' (does the network require authentication?) error. Most people have the problem of a transparent proxy (like here: https://askubuntu.com/questions/474549/got-nodata-issue-nodata-does-the-network-require-authentication) which is not the case for me, it's not transparent, it's there I know it :) and also an apt-get update works properly (proxy set in /etc/apt/apt.conf)



      There was an older discussion with a very similar issue to mine here: https://lists.debian.org/debian-live/2013/06/msg00078.html but this was quite a while ago, and it was marked as fixed later versions. I'm using the latest version of live-build, 4.0.3-1 and live-tools 4.0.2-1.1



      I can confirm that the problem doesn't appear if the system has a direct internet connection.



      I would really appreciate if someone could shed some light on this problem, or if someone met similar problems.



      Thanks,
      Gabor



      P.S. This used to work in this setup a while back (last summer or something like that). What could have changed since then?









      share|improve this question










      share|improve this question




      share|improve this question









      asked Apr 20 at 11:41









      Gabor

      11




      11

























          active

          oldest

          votes











          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%2f438919%2flive-build-behind-a-proxy-at-lb-bootstrap-archive-keys-step-gets-clearsigned-fil%23new-answer', 'question_page');

          );

          Post as a guest



































          active

          oldest

          votes













          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes










           

          draft saved


          draft discarded


























           


          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f438919%2flive-build-behind-a-proxy-at-lb-bootstrap-archive-keys-step-gets-clearsigned-fil%23new-answer', 'question_page');

          );

          Post as a guest













































































          Popular posts from this blog

          Peggy Mitchell

          Palaiologos

          The Forum (Inglewood, California)