Bug 1795934 - asterisk-17.2.0-0.rc1.2.fc32.1 FTBFS: asterisk-17.2.0-rc1.tar.gz: No such file or directory
Summary: asterisk-17.2.0-0.rc1.2.fc32.1 FTBFS: asterisk-17.2.0-rc1.tar.gz: No such fil...
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: asterisk
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jared Smith
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F32FTBFS
TreeView+ depends on / blocked
 
Reported: 2020-01-29 09:38 UTC by Petr Pisar
Modified: 2020-01-29 17:01 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-01-29 17:01:11 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Petr Pisar 2020-01-29 09:38:01 UTC 
asterisk-17.2.0-0.rc1.2.fc32.1 fails to build because a source RPM package cannot be built because the Source0 and Source1 files:

$ spectool -f asterisk.spec 
Source0: http://downloads.asterisk.org/pub/telephony/asterisk/releases/asterisk-17.2.0-rc1.tar.gz
Source1: http://downloads.asterisk.org/pub/telephony/asterisk/releases/asterisk-17.2.0-rc1.tar.gz.asc
[...]

were not uploaded to a look-aside cache:

$ cat sources 
SHA512 (asterisk-17.1.0.tar.gz) = 5cfe10cf597e8bbb6f83b51ecaa072a3adda1e334640b8a4164b9dbf92382e3abc087ca76ce7347f827903ae3b0c20755056b2b0cfe78da3226834461888476a
SHA512 (asterisk-17.1.0.tar.gz.asc) = f341d1c23bf25f46bfa12e6cf5073e587882922c802c86b5c8f58cbd0a40b51017e55cd705800c69442f18aad24cc560ea1a52356a206d9423924e90d8285c20
SHA512 (pjproject-2.9.tar.bz2) = a65823a86ad0cd76890cf7dd2485f7547fd90aea2ef631c5420c009b35f39eda3b78551a42fc2816c2470de9eb728c26497774a8494824472ecaa1d2889cc20b
SHA512 (jansson-2.12.tar.bz2) = 6ed665a441c789cdf7eb22b6e69d02575746c81b00e0a81ced90d30aaf2badc93fac32e5841fd4e07751a27726a327a63fe28bb0689c6bef5b6164b435bbc30d
Comment 1 Jared Smith 2020-01-29 17:01:11 UTC 
This has been resolved and rebuilt in Rawhide.
Note You need to log in before you can comment on or make changes to this bug.