#1638 new defect

tar01/tar02 tarballs contain non-deterministic uids/gids + permissions

Reported by: Ralf Corsepius Owned by: Joel Sherrill
Priority: low Milestone: Indefinite
Component: unspecified Version:
Severity: normal Keywords:
Cc: chrisj@… Blocked By:
Blocking:

Description (last modified by Sebastian Huber)

The tarballs being created in libtests/tar01 and libtests/tar02 contain non deterministic uids/gids (Those of the user creating the tarball) and
permissions (as specified by the user's creating the tarballs umask).

Change History (5)

comment:1 Changed on Jul 29, 2010 at 5:54:11 AM by Chris Johns

Cc: Chris Johns added

Replying to comment:2:

That said, at present, I am leaning towards adding binary tarballs with
predefined uids/gids/permissions and not to user-generate them.

If we are converting the binary tar file to a C file should we just commit the C file ?

I am not sure if this approach can be extended to all RTEMS applications. I know with Parrot we need to create a base file system at the build time to capture the host compiled byte code files. I wonder if the building of the test Parrot application should fail if a no suitable tar can be found on the build host. Ralf, I would appreciate your feed back on this issue.

comment:2 Changed on Nov 24, 2014 at 6:58:28 PM by Gedare Bloom

Version: HEAD4.11

Replace Version=HEAD with Version=4.11 for the tickets with Milestone >= 4.11

comment:3 Changed on Dec 18, 2014 at 9:17:41 AM by Sebastian Huber

Description: modified (diff)
Milestone: 4.115.0
Priority: normallow

comment:4 Changed on Aug 14, 2017 at 12:29:21 AM by Chris Johns

Milestone: 5.0Indefinite
Version: 4.11

comment:5 Changed on Oct 10, 2017 at 6:35:44 AM by Sebastian Huber

Component: miscunspecified
Note: See TracTickets for help on using tickets.