https://bugzilla.redhat.com/show_bug.cgi?id=800284



--- Comment #20 from Ken Dreyer <[email protected]> ---
Hi Avi,

From http://kojipkgs.fedoraproject.org//work/tasks/8676/6468676/root.log:

DEBUG util.py:281:  Could not execute sources: Command curl -H Pragma: -o
./AtomicParsley-source-0.9.0.zip -R -S --fail
http://pkgs.fedoraproject.org/repo/pkgs/AtomicParsley/AtomicParsley-source-0.9.0.zip/681e6ecec2921c98e07a9262bdcd6cf2/AtomicParsley-source-0.9.0.zip
returned code 22 with error:   % Total    % Received % Xferd  Average Speed  
Time    Time     Time  Current
DEBUG util.py:281:                                   Dload  Upload   Total  
Spent    Left  Speed
DEBUG util.py:281:  
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
DEBUG util.py:281:  curl: (22) The requested URL returned error: 404 Not Found


Did you run "fedpkg new-sources AtomicParsley-source-0.9.0.zip" first, in order
to upload the zip file to the lookaside cache?

When you run "fedpkg scratch-build" without the --srpm flag, Koji will try to
build from Git and the lookaside cache, and if there's no zip file in the
lookaside cache, the build will fail.

Alternatively, if you want to do a scratch build without uploading a zip file
with "fedpkg new-sources", you should use the "--srpm" flag instead. "fedpkg
scratch-build --srpm" means "create an SRPM locally, then upload that to koji
and build that."

In this case I would recommend that you first do a scratch build with --srpm to
get familiar with it, then run "fedpkg new-sources
AtomicParsley-source-0.9.0.zip", then do a second scratch build (wihtout
--srpm) to see how that works, and then finally do your real "fedpkg build".

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component
_______________________________________________
package-review mailing list
[email protected]
https://admin.fedoraproject.org/mailman/listinfo/package-review

Reply via email to