On Wed, Jun 1, 2022 at 7:46 AM Ryan Long <ryan.l...@oarcorp.com> wrote: > > > On 6/1/2022 7:36 AM, Gedare Bloom wrote: > > What/Why did this change? Where we not using a release before? > I'm not sure. Their Github only shows two releases. One's from 2019 and > the latest is from late 2021. The last time the hash was bumped was in > 2020 by Joel, so I'm guessing that was changing it to the 1.0.0 release, > and this just bumps it to 1.1.0. Maybe it was in beta at the time. > > > > Looks ok otherwise. > > ok
> > On Wed, May 25, 2022 at 12:31 PM Ryan Long <ryan.l...@oarcorp.com> wrote: > >> Bump the hash of spike to match the 1.1.0 release > >> > >> Closes #4660 > >> --- > >> bare/config/devel/spike-1.1.0.cfg | 4 ++-- > >> 1 file changed, 2 insertions(+), 2 deletions(-) > >> > >> diff --git a/bare/config/devel/spike-1.1.0.cfg > >> b/bare/config/devel/spike-1.1.0.cfg > >> index 644b754..73cf3c2 100644 > >> --- a/bare/config/devel/spike-1.1.0.cfg > >> +++ b/bare/config/devel/spike-1.1.0.cfg > >> @@ -8,9 +8,9 @@ > >> > >> %include %{_configdir}/base.cfg > >> > >> -%define spike_version 66b44bfbedda562a32e4a2cd0716afbf731b69cd > >> +%define spike_version 530af85d83781a3dae31a4ace84a573ec255fefa > >> > >> -%hash sha512 spike-%{spike_version}.tar.gz > >> a98fc9e564edb3bb471f04063484a5d056befb8b2258b96de2d238cf27d1d5544c2782c91c7731b8f0aa03012eb3d39de33e4f30927349e38c7e131e8241b92f > >> +%hash sha512 spike-%{spike_version}.tar.gz > >> D+9XugRwrZJ8undjx3x3CILr4VSdeaNsTTUZYeENFPZy6MG7TiQAY5umaUr/oOr6vWCq7YjFhqwjPI+fcieqYw== > >> > >> # > >> # The spike build instructions. We use 1.x.x Release 1. > >> -- > >> 2.30.2 > >> > >> _______________________________________________ > >> devel mailing list > >> devel@rtems.org > >> http://lists.rtems.org/mailman/listinfo/devel _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel