Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot packages from svn repo fail
Date: Fri, 19 Feb 2021 21:19:30 +0100	[thread overview]
Message-ID: <20210219201930.GA2276@scaer> (raw)
In-Reply-To: <AS8PR06MB7686BDC4D80BA193BE5E486384859@AS8PR06MB7686.eurprd06.prod.outlook.com>

Henri, All,

Thanks for the reporton this svn issue.

On 2021-02-18 12:19 +0000, Roosen Henri spake thusly:
> Hi Yann,

Please do not write to individual contributors directly. Write to the
mailing list, so that everyon has a chance to learn about the issue,
provide feedback, suggest ways to resolve the issue, and so that
everyone can benefit from this.

By writing to the list, you also stand better chance that someone spots
the mail, in case the contributor is not available (like me this week, I
was unable to work on Buldroot dur to familly concerns).

> We use a custom kernel which is available using our internal svn-repo.
> The download now fails with the following:
> 
> tar: Time stamp is out of allowed range
> tar: Exiting with failure status due to previous errors
> 
> Reverting commit c043ecb20ce6ac316fe31da6d2db5b13a34dc414 fixes the problem.

As has been discovered by Vincent in the rest of this private thread,
the root cause seems to be the svn client you are using, that reports
sub-second timestamps, which are not supported by the PAX format we are
now using.

I'll be waiting for the patch from Vincent (or anyone else) to fix the
issue.

Also, as Arnout suggested, it would be nice to have a runtime test, like
we have for git;
    support/testing/tests/download/test_git.py

I don't think we need somethign totally exhaustive, but even just a
basic test would be enough (e.g. tests with svn:external are not a
requirement).

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

       reply	other threads:[~2021-02-19 20:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AS8PR06MB7686BDC4D80BA193BE5E486384859@AS8PR06MB7686.eurprd06.prod.outlook.com>
2021-02-19 20:19 ` Yann E. MORIN [this message]
     [not found] ` <AS8PR06MB768671E2EF5E7F63A1D6441884859@AS8PR06MB7686.eurprd06.prod.outlook.com>
     [not found]   ` <361e9dd7-604b-bf45-e4ce-7b0dc937b06f@xes-inc.com>
     [not found]     ` <6abbffd80d7d80062d25b08ed09a3f8c65ac621a.camel@ginzinger.com>
     [not found]       ` <5a1ad4cf-f72f-6fc4-da80-7d5c24d45661@xes-inc.com>
2021-02-19 20:34         ` [Buildroot] buildroot packages from svn repo fail Yann E. MORIN

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210219201930.GA2276@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox