Github messages for voidlinux
 help / color / mirror / Atom feed
From: ysk81 <ysk81@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] apache-ant fails building
Date: Thu, 06 Oct 2022 07:49:44 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39753@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1134 bytes --]

New issue by ysk81 on void-packages repository

https://github.com/void-linux/void-packages/issues/39753

Description:
### Is this a new report?

Yes

### System Info

Voild 5.19.13_1 x86-64

### Package(s) Affected

apache-ant-1.10.12_1

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

auto download "ftp://ftp.software.ibm.com/software/awdtools/netrexx/NetRexx.zip" file during build amd complete building pkg.

### Actual behaviour

build script fails with sha-256 checksum mismatch error for file "ftp://ftp.software.ibm.com/software/awdtools/netrexx/NetRexx.zip".
Tried to download file via wget and figured the downloaded size is twice the reported file size from ftp server.
Tried again with --no-passive-ftp and this time size was correct.
Coppied the downloaded file to /buildder/apache-ant-1.10.12/?/.ant/tempcache/
and ran ./xbps-src -N pkg apache-ant again.
This time build was successfull. 
So, if we can have build script to not use passive ftp, the problem might be solved.

### Steps to reproduce

xbps-src -N pkg apache-ant

             reply	other threads:[~2022-10-06  5:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-06  5:49 ysk81 [this message]
2023-03-03 21:24 ` frankenstein91
2023-06-08 22:30 ` lchrennew
2023-08-18 19:11 ` echuber2

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39753@inbox.vuxu.org \
    --to=ysk81@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).