GNU bug report logs - #46482
[core-updates] u-boot source cannot be downloaded

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 46482 in the body.
You can then email your comments to 46482 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Danny Milosavljevic <dannym <at> scratchpost.org>
To: <bug-guix <at> gnu.org>
Subject: [core-updates] u-boot source cannot be downloaded
Date: Sat, 13 Feb 2021 03:37:52 +0100

[Message part 1 (text/plain, inline)]

failed to download "/gnu/store/1idpm6f9pcm9dajm90qgk6x1r6qywfv8-u-boot-2021.01.tar.bz2" from "ftp://ftp.denx.de/pub/u-boot/u-boot-2021.01.tar.bz2"
builder for `/gnu/store/5s92y4l66f8qh4p4gx79jvsjaxhl208k-u-boot-2021.01.tar.bz2.drv' failed to produce output path `/gnu/store/1idpm6f9pcm9dajm90qgk6x1r6qywfv8-u-boot-2021.01.tar.bz2'
build of /gnu/store/5s92y4l66f8qh4p4gx79jvsjaxhl208k-u-boot-2021.01.tar.bz2.drv failed
View build log at '/var/log/guix/drvs/5s/92y4l66f8qh4p4gx79jvsjaxhl208k-u-boot-2021.01.tar.bz2.drv.bz2'.
cannot build derivation `/gnu/store/m09apasn4glhf2lvsq8bn2ci5ncjq0fz-u-boot-tools-2021.01.drv': 1 dependencies couldn't be built
building /gnu/store/5s4pczxlp3v8yfavmgjf93093msfaxym-ucommon-7.0.0.tar.gz.drv...

Changing the URL to "https" instead of "ftp" would work.
Changing it to "http" instead of "ftp" would also work.
Which should we use?

Reason is bug #46481.

But do we maybe want to change over to http or https anyway?

[Message part 2 (application/pgp-signature, inline)]

Message #8 received at 46482 <at> debbugs.gnu.org (full text, mbox):

From: Leo Famulari <leo <at> famulari.name>
To: Danny Milosavljevic <dannym <at> scratchpost.org>
Cc: 46482 <at> debbugs.gnu.org
Subject: Re: bug#46482: [core-updates] u-boot source cannot be downloaded
Date: Fri, 12 Feb 2021 22:19:40 -0500

[Message part 1 (text/plain, inline)]

On Sat, Feb 13, 2021 at 03:37:52AM +0100, Danny Milosavljevic wrote:
> Changing the URL to "https" instead of "ftp" would work.
> Changing it to "http" instead of "ftp" would also work.
> Which should we use?

I recommend HTTPS over HTTP. Although we don't verify the HTTPS
certificate with the X.509 PKI for this case [0], it still protects
against passive eavesdropping.

[0] https://git.savannah.gnu.org/cgit/guix.git/tree/guix/scripts/perform-download.scm?id=0e3de2cf1108ed0226297046302079fab9057522#n84

[signature.asc (application/pgp-signature, inline)]

Message #11 received at 46482 <at> debbugs.gnu.org (full text, mbox):

From: Bengt Richter <bokr <at> bokr.com>
To: Danny Milosavljevic <dannym <at> scratchpost.org>
Cc: 46482 <at> debbugs.gnu.org
Subject: Re: bug#46482: [core-updates] u-boot source cannot be downloaded
Date: Sat, 13 Feb 2021 19:34:09 +0100

Hi,

On +2021-02-13 03:37:52 +0100, Danny Milosavljevic wrote:
> failed to download "/gnu/store/1idpm6f9pcm9dajm90qgk6x1r6qywfv8-u-boot-2021.01.tar.bz2" from "ftp://ftp.denx.de/pub/u-boot/u-boot-2021.01.tar.bz2"
> builder for `/gnu/store/5s92y4l66f8qh4p4gx79jvsjaxhl208k-u-boot-2021.01.tar.bz2.drv' failed to produce output path `/gnu/store/1idpm6f9pcm9dajm90qgk6x1r6qywfv8-u-boot-2021.01.tar.bz2'
> build of /gnu/store/5s92y4l66f8qh4p4gx79jvsjaxhl208k-u-boot-2021.01.tar.bz2.drv failed
> View build log at '/var/log/guix/drvs/5s/92y4l66f8qh4p4gx79jvsjaxhl208k-u-boot-2021.01.tar.bz2.drv.bz2'.
> cannot build derivation `/gnu/store/m09apasn4glhf2lvsq8bn2ci5ncjq0fz-u-boot-tools-2021.01.drv': 1 dependencies couldn't be built
> building /gnu/store/5s4pczxlp3v8yfavmgjf93093msfaxym-ucommon-7.0.0.tar.gz.drv...
> 
> Changing the URL to "https" instead of "ftp" would work.
> Changing it to "http" instead of "ftp" would also work.
> Which should we use?
> 
> Reason is bug #46481.
> 
> But do we maybe want to change over to http or https anyway?

So long as you can check the hash of the downloaded file,
IMO other considerations ought to dominate the choice.

I would prefer something that fits in with mes-philosopy.
ftp seems old and simple, so I would vote for push-back
to fix the ftp client involved.

FWIW:
I clicked on the
    "ftp://ftp.denx.de/pub/u-boot/u-boot-2021.01.tar.bz2"
URL in your "failed to download" message above, and got an open/save-as popup choice widget,
and clicked save-as and successfully downloaded it, and can inspect it with
    tar -tjvf u-boot-2021.01.tar.bz2|less

I am running pureos (debian variant):
--8<---------------cut here---------------start------------->8---
4.19.0-14-amd64 #1 SMP Debian 4.19.171-2 (2021-01-30)
--8<---------------cut here---------------end--------------->8---

and was in a tilix terminal when I clicked the URL, which started 
    Mozilla Firefox 78.7.0esr
which gave me the open/save-as popup choice.

IDK what firefox does with ftp://...
but it worked. I guess I could strace it, but what does firefox or icecat do on your box
if directed to 
    ftp://ftp.denx.de/pub/u-boot/u-boot-2021.01.tar.bz2
?
HTH
-- 
Regards,
Bengt Richter

Message #14 received at 46482 <at> debbugs.gnu.org (full text, mbox):

From: Leo Famulari <leo <at> famulari.name>
To: Bengt Richter <bokr <at> bokr.com>
Cc: Danny Milosavljevic <dannym <at> scratchpost.org>, 46482 <at> debbugs.gnu.org
Subject: Re: bug#46482: [core-updates] u-boot source cannot be downloaded
Date: Sat, 13 Feb 2021 14:12:13 -0500

On Sat, Feb 13, 2021 at 07:34:09PM +0100, Bengt Richter wrote:
> I would prefer something that fits in with mes-philosopy.
> ftp seems old and simple, so I would vote for push-back
> to fix the ftp client involved.

FTP is more complicated than HTTP in that it requires the use of
multiple connections. Additionally, it's often blocked on corporate
networks, whereas HTTP/S is never going to be blocked (HTTPS anyways).

Based on experience in Guix, we have never had bug reports from users
who could not access sources over HTTP/S, but there have been several
reports of problems using FTP. The HTTP/S ports 80 and 443 are basically
the only ports you can depend on being open on a network that is
connected to the internet.

The creator of curl compares them here:

https://daniel.haxx.se/docs/ftp-vs-http.html

Message #17 received at 46482 <at> debbugs.gnu.org (full text, mbox):

From: Bengt Richter <bokr <at> bokr.com>
To: Leo Famulari <leo <at> famulari.name>
Cc: Danny Milosavljevic <dannym <at> scratchpost.org>, 46482 <at> debbugs.gnu.org
Subject: Re: bug#46482: [core-updates] u-boot source cannot be downloaded
Date: Sun, 14 Feb 2021 04:57:50 +0100

Hi Leo et al,

On +2021-02-13 14:12:13 -0500, Leo Famulari wrote:
> On Sat, Feb 13, 2021 at 07:34:09PM +0100, Bengt Richter wrote:
> > I would prefer something that fits in with mes-philosopy.
> > ftp seems old and simple, so I would vote for push-back
> > to fix the ftp client involved.
> 
> FTP is more complicated than HTTP in that it requires the use of
> multiple connections. Additionally, it's often blocked on corporate
> networks, whereas HTTP/S is never going to be blocked (HTTPS anyways).
> 
> Based on experience in Guix, we have never had bug reports from users
> who could not access sources over HTTP/S, but there have been several
> reports of problems using FTP. The HTTP/S ports 80 and 443 are basically
> the only ports you can depend on being open on a network that is
> connected to the internet.
> 
> The creator of curl compares them here:
> 
> https://daniel.haxx.se/docs/ftp-vs-http.html

Thanks, that was interesting.

He says (re download speed)
    "Ultimately the net outcome of course differs depending on
     specific details, but I would say that for single-shot static files,
     you won't be able to measure a difference."

So in that case, what's minimal, and how vulnerable is it?

Is there a minimal quic without google upstream?

or X.25 -- dating myself ;-P

and what about TFTP/PXE ??

What would the mes-people suggest
for minimalist functionality, and minimal trust scope,
and maximal monopoly-independence, I wonder?

[meta-question] How does one gracefully go off-topic onto a tangential
discussion? I thought my original comment re expired gpg key might
have helped in some way, but my comment wanting to get the ftp fixed
intead of (or in addition to) being bypassed provoked the explanation
of how I was deluded (ok, no worries :), but I might want to
say something about separate connections isolating meta-data and data
as being a "feature" that I expect to see more of, but that would be
another step along the tangent ... or osculating circle? NNTR :-D 

-- 
Regards,
Bengt Richter

Message #20 received at 46482 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Danny Milosavljevic <dannym <at> scratchpost.org>
Cc: 46482 <at> debbugs.gnu.org
Subject: Re: bug#46482: [core-updates] u-boot source cannot be downloaded
Date: Fri, 19 Feb 2021 16:26:03 +0100

Hi,

Danny Milosavljevic <dannym <at> scratchpost.org> skribis:

> failed to download "/gnu/store/1idpm6f9pcm9dajm90qgk6x1r6qywfv8-u-boot-2021.01.tar.bz2" from "ftp://ftp.denx.de/pub/u-boot/u-boot-2021.01.tar.bz2"

Can we add mirror URLs to the ‘origin’, similar to what I did in
9d01749feaa1586b1caf449712116e7518bb2303?

Ludo’.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.