Hi Gijs,
Yes, Canonical pulled the Saucy packages from the standard archives. It was
EOL'd a few months ago. They're still available via an alternative server
but until you change any machine's apt sources list they will fail.
We updated our images to pull from the old-releases repo for saucy here:
https://github.com/ros-infrastructure/buildfarm/pull/218 That update
should have propogated last night and builds after that update propogated
should work on Saucy again.
The farm will automatically retry any package with all upstream jobs
passing each night. There's no need to rerun bloom. I see the job you
linked to is in the queue to be rebuilt already.
Note there's a lot of backup at the moment due to a recent core release.
We're rebuilding several thousand packages at the moment. The queue is down
to ~3k from 6.5k jobs last night. We're running 20 build machines but I
expect it to need another 24 hours or so.
Tully
On Wed, Oct 14, 2015 at 2:16 AM, G.A. vd. Hoorn - 3ME via ros-release <
ros-release@lists.ros.org> wrote:
>
> Just noticed that the majority of my saucy builds for amd64 are failing
> [1].
>
> Is this related to [2]?
>
> Also: is there any way I can kick off a new build without re-running
> bloom-release?
>
>
> Gijs
>
> [1] http://jenkins.ros.org/job/ros-indigo-fanuc_binarydeb_saucy_amd64/
> [2]
> http://answers.ros.org/question/218974/failed-to-fetch-while-releasing/
>
> _______________________________________________
> ros-release mailing list
> ros-release@lists.ros.org
> http://lists.ros.org/mailman/listinfo/ros-release
>
_______________________________________________
ros-release mailing list
ros-release@lists.ros.org
http://lists.ros.org/mailman/listinfo/ros-release
(text/plain)