Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13631] New: Commit 54d3d94b6e breaks packages with git download method
Date: Thu, 18 Mar 2021 18:46:53 +0000	[thread overview]
Message-ID: <bug-13631-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=13631

            Bug ID: 13631
           Summary: Commit 54d3d94b6e breaks packages with git download
                    method
           Product: buildroot
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: major
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: mhardt at berlinux-solutions.de
                CC: buildroot at uclibc.org
  Target Milestone: ---

When using a package with git download method the download step is broken when
not using a silent build (make -s).

The reason is the commit date being used for creating an archive of the
repository and the output now contains an additional line containing the git
command. This obviously cannot be parsed as a date.

Example output:

date: invalid date 'GIT_DIR=<some-dir>/git/.git git log -1 --pretty=format:%ci
\n2021-03-12 08:58:14 +0100'
Detected a corrupted git cache.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2021-03-18 18:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-18 18:46 bugzilla at busybox.net [this message]
2021-03-18 20:45 ` [Buildroot] [Bug 13631] Commit 54d3d94b6e breaks packages with git download method bugzilla at busybox.net
2021-03-19 20:38 ` bugzilla at busybox.net
2021-03-22  8:14 ` bugzilla at busybox.net

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=bug-13631-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --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