Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Julien Corjon <corjon.j@ecagroup.com>,
	Giulio Benetti <giulio.benetti@benettiengineering.com>,
	Peter Seiderer <ps.report@gmx.net>,
	Angelo Compagnucci <angelo.compagnucci@gmail.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/5] package/qt5: fix upstream git trees
Date: Sun, 17 Sep 2023 08:45:12 +0200	[thread overview]
Message-ID: <87il89ti13.fsf@48ers.dk> (raw)
In-Reply-To: <a55c91fd6ba2fdefaf885d631c6a74eb69fb81a1.1694556946.git.yann.morin.1998@free.fr> (Yann E. MORIN's message of "Wed, 13 Sep 2023 00:15:48 +0200")

>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:

 > Since commits 4e8b5f9bee9c [0], 6cfbd51d98d1 [1], and d838a416c4ed [2],
 > the repository we clone from is the cgit browser, and it does not serve
 > the git tree, only the browser:

 >     $ git clone https://code.qt.io/cgit/qt/qtcoap.git
 >     Cloning into 'qtcoap'...
 >     fatal: repository 'https://code.qt.io/cgit/qt/qtcoap.git/' not found

 > Browsing there displays the cgit UI, which gives a proper URI to clone
 > from; switch to using that.

 > [0] 4e8b5f9bee9c package/qt5/qt5mqtt: bump version to 5.15.2 (and fix download)
 > [1] 6cfbd51d98d1 package/qt5/qt5coap: bump version to 5.15.2 (and fix download)
 > [2] d838a416c4ed package/qt5/qt5knx: bump version to 5.15.2 (and fix download)

 > Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>

I guess it must be upstream changing something on the server since 2021,
otherwise how could we have a copy on s.b.o?

Committed to 2023.02.x, 2023.05.x and 2023.08.x, thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2023-09-17  6:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-12 22:15 [Buildroot] [PATCH 0/5] support/downloaf/git: add support for git attirbutes (branch yem/git-attributes) Yann E. MORIN
2023-09-12 22:15 ` [Buildroot] [PATCH 1/5] package/qt5: fix upstream git trees Yann E. MORIN
2023-09-13  9:45   ` Thomas Petazzoni via buildroot
2023-09-13  9:55     ` Yann E. MORIN
2023-09-14 21:03   ` Thomas Petazzoni via buildroot
2023-09-17  6:45   ` Peter Korsgaard [this message]
2023-09-12 22:15 ` [Buildroot] [PATCH 2/5] support/download: generate even more reproducible tarballs Yann E. MORIN
2023-09-24 16:05   ` Peter Korsgaard
2023-09-12 22:15 ` [Buildroot] [PATCH 3/5] support/download/git: properly catch failures Yann E. MORIN
2023-09-24 16:05   ` Peter Korsgaard
2023-09-12 22:15 ` [Buildroot] [PATCH 4/5] support/download/git: fix shellcheck errors Yann E. MORIN
2023-09-24 16:05   ` Peter Korsgaard
2023-09-12 22:15 ` [Buildroot] [PATCH 5/5] support/download/git: handle git attributes Yann E. MORIN
2023-09-14 21:07   ` Thomas Petazzoni via buildroot
2023-09-15  7:50     ` Yann E. MORIN
2023-09-17 17:52       ` Arnout Vandecappelle via buildroot
2023-09-17 19:00         ` Yann E. MORIN
2023-09-18  7:38           ` Arnout Vandecappelle via buildroot

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=87il89ti13.fsf@48ers.dk \
    --to=peter@korsgaard.com \
    --cc=angelo.compagnucci@gmail.com \
    --cc=buildroot@buildroot.org \
    --cc=corjon.j@ecagroup.com \
    --cc=giulio.benetti@benettiengineering.com \
    --cc=ps.report@gmx.net \
    --cc=yann.morin.1998@free.fr \
    /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