lftp bug

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

lftp bug

Jude DaShiell-2
I don't know which is responsible for what.
I put together an lftp script and tried running the script to download a
torrent and am getting strange output.

Script started on 2018-02-07 10:35:38-0500
[jude@taf ~]$ cat debian.lftp
echo "downloading debian buster torrent"
#mget
https://cdimage.debian.org:/cdimage/unofficial/non-free/cd-including-firmware/buster_di_alpha2/amd64/bt-dvd/*512*
#mget
https://cdimage.debian.org:/cdimage/unofficial/non-free/cd-including-firmware/buster_di_alpha2/amd64/bt-dvd/firmware-buster-DI-alpha2-amd64-DVD-1.iso.torrent
torrent
https://cdimage.debian.org:/cdimage/unofficial/non-free/cd-including-firmware/buster_di_alpha2/amd64/bt-dvd/firmware-buster-DI-alpha2-amd64-DVD-1.iso.torrent
[jude@taf ~]$ lftp -f debian.lftp
   downloading debian buster torrent
Assertion 'fd' failed at ../systemd-stable/src/basic/socket-util.c:1011,
function getpeergroups(). Aborting.
...ter-DI-alpha2-amd64-DVD-1.iso.torrent: Getting meta-data: [Resolving
host address...] ^C
[jude@taf ~]$ exit
exit

Script done on 2018-02-07 10:38:55-0500

Is this an upstream problem?



--
Reply | Threaded
Open this post in threaded view
|

Re: lftp bug

arch general mailing list-2
On Mon, 12 Feb 2018 13:12:02 -0500
Jude DaShiell <[hidden email]> wrote:

> I don't know which is responsible for what.
> I put together an lftp script and tried running the script to download a
> torrent and am getting strange output.
>
> Script started on 2018-02-07 10:35:38-0500
> [jude@taf ~]$ cat debian.lftp
> echo "downloading debian buster torrent"
> #mget
> https://cdimage.debian.org:/cdimage/unofficial/non-free/cd-including-firmware/buster_di_alpha2/amd64/bt-dvd/*512*
> #mget
> https://cdimage.debian.org:/cdimage/unofficial/non-free/cd-including-firmware/buster_di_alpha2/amd64/bt-dvd/firmware-buster-DI-alpha2-amd64-DVD-1.iso.torrent
> torrent
> https://cdimage.debian.org:/cdimage/unofficial/non-free/cd-including-firmware/buster_di_alpha2/amd64/bt-dvd/firmware-buster-DI-alpha2-amd64-DVD-1.iso.torrent
> [jude@taf ~]$ lftp -f debian.lftp
>    downloading debian buster torrent
> Assertion 'fd' failed at ../systemd-stable/src/basic/socket-util.c:1011,
> function getpeergroups(). Aborting.
> ...ter-DI-alpha2-amd64-DVD-1.iso.torrent: Getting meta-data: [Resolving
> host address...] ^C
> [jude@taf ~]$ exit
> exit
>
> Script done on 2018-02-07 10:38:55-0500
>
> Is this an upstream problem?


https://bugs.archlinux.org/task/57388
Reply | Threaded
Open this post in threaded view
|

Re: lftp bug

Jude DaShiell-2
Thanks, this is good to know.

On Mon, 12 Feb 2018, Doug Newgard via arch-general wrote:

> Date: Mon, 12 Feb 2018 13:23:55
> From: Doug Newgard via arch-general <[hidden email]>
> To: [hidden email]
> Cc: Doug Newgard <[hidden email]>
> Subject: Re: [arch-general] lftp bug
>
> On Mon, 12 Feb 2018 13:12:02 -0500
> Jude DaShiell <[hidden email]> wrote:
>
>> I don't know which is responsible for what.
>> I put together an lftp script and tried running the script to download a
>> torrent and am getting strange output.
>>
>> Script started on 2018-02-07 10:35:38-0500
>> [jude@taf ~]$ cat debian.lftp
>> echo "downloading debian buster torrent"
>> #mget
>> https://cdimage.debian.org:/cdimage/unofficial/non-free/cd-including-firmware/buster_di_alpha2/amd64/bt-dvd/*512*
>> #mget
>> https://cdimage.debian.org:/cdimage/unofficial/non-free/cd-including-firmware/buster_di_alpha2/amd64/bt-dvd/firmware-buster-DI-alpha2-amd64-DVD-1.iso.torrent
>> torrent
>> https://cdimage.debian.org:/cdimage/unofficial/non-free/cd-including-firmware/buster_di_alpha2/amd64/bt-dvd/firmware-buster-DI-alpha2-amd64-DVD-1.iso.torrent
>> [jude@taf ~]$ lftp -f debian.lftp
>>    downloading debian buster torrent
>> Assertion 'fd' failed at ../systemd-stable/src/basic/socket-util.c:1011,
>> function getpeergroups(). Aborting.
>> ...ter-DI-alpha2-amd64-DVD-1.iso.torrent: Getting meta-data: [Resolving
>> host address...] ^C
>> [jude@taf ~]$ exit
>> exit
>>
>> Script done on 2018-02-07 10:38:55-0500
>>
>> Is this an upstream problem?
>
>
> https://bugs.archlinux.org/task/57388
>

--