Release task request for help

Niteesh G. S. niteesh.gs at gmail.com
Tue Apr 28 01:30:55 UTC 2020


I have updated the scripts. Please have a look at it once again.

rtems-release-branch
https://github.com/gs-niteesh/rtems-release/commit/855a2927db21dd6f2b7612d7bc3f7b1407e4730c

rtems-release-defaults
https://github.com/gs-niteesh/rtems-release/commit/8be7e006f3f06fa1040bcdefdbccbdbe0784ad8c

On Tue, Apr 28, 2020 at 6:40 AM Niteesh G. S. <niteesh.gs at gmail.com> wrote:

> The testing method I used had a flaw. Since I don't have access to
> RTEMS server, I replaced the URL with GIthub and it seems that
> github keeps references to old repos because of this I wasn't getting
> an error due to the wrong repo name.
>
> On Tue, Apr 28, 2020 at 6:38 AM Niteesh G. S. <niteesh.gs at gmail.com>
> wrote:
>
>> Sounds good. But what is the difference between an RTEMS-package
>> and repo? Aren't they the same?
>>
>> On Tue, Apr 28, 2020 at 6:25 AM Chris Johns <chrisj at rtems.org> wrote:
>>
>>> On 28/4/20 10:50 am, Niteesh G. S. wrote:
>>> > The rtems-release-defaults already contains a rtems-packages
>>> > variable. Can I use that instead of moving the rtems-repos variables?
>>>
>>> I am not sure if the list will always match.
>>>
>>> What about a repos variable that is based on the packages list so we can
>>> extend it?
>>>
>>> Chris
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20200428/705744c2/attachment-0001.html>


More information about the devel mailing list