From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: "Marek Vasut" <marex@denx.de>
Cc: bitbake-devel@lists.openembedded.org,
Martin Jansa <Martin.Jansa@gmail.com>,
Peter Kjellerstedt <peter.kjellerstedt@axis.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>
Subject: Re: [bitbake-devel] [PATCH] [RFC] fetch2/git: Prevent git fetcher from fetching gitlab repository metadata
Date: Mon, 22 Aug 2022 18:02:41 +0200 [thread overview]
Message-ID: <20220822180241.5f625ed3@booty> (raw)
In-Reply-To: <20220819165455.270130-1-marex@denx.de>
Hi Marek,
On Fri, 19 Aug 2022 18:54:55 +0200
"Marek Vasut" <marex@denx.de> wrote:
> The bitbake git fetcher currently fetches 'refs/*:refs/*', i.e. every
> single object in the remote repository. This works poorly with gitlab
> and github, which use the remote git repository to track its metadata
> like merge requests, CI pipelines and such.
>
> Specifically, gitlab generates refs/merge-requests/*, refs/pipelines/*
> and refs/keep-around/* and they all contain massive amount of data that
> are useless for the bitbake build purposes. The amount of useless data
> can in fact be so massive (e.g. with FDO mesa.git repository) that some
> proxies may outright terminate the 'git fetch' connection, and make it
> appear as if bitbake got stuck on 'git fetch' with no output.
>
> To avoid fetching all these useless metadata, tweak the git fetcher such
> that it only fetches refs/heads/* and refs/tags/* . Avoid using negative
> refspecs as those are only available in new git versions.
>
> Signed-off-by: Marek Vasut <marex@denx.de>
Of course this might become irrelevant with whatever implementation
will be in v2, however when testing with this patch applied I got the
following warning and wonder whether they are related:
WARNING: mesa-2_22.1.6-r0 do_package_qa: QA Issue: File /usr/lib/dri/nouveau_dri.so in package mesa-megadriver contains reference to TMPDIR
Full log:
https://autobuilder.yoctoproject.org/typhoon/#/builders/72/builds/5753/steps/32/logs/stdio
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2022-08-22 16:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-19 16:54 [PATCH] [RFC] fetch2/git: Prevent git fetcher from fetching gitlab repository metadata Marek Vasut
2022-08-20 12:06 ` Peter Kjellerstedt
2022-08-22 5:19 ` [bitbake-devel] " Mikko.Rapeli
2022-08-22 6:57 ` Alexander Kanavin
2022-08-22 7:38 ` Mikko.Rapeli
2022-08-22 8:29 ` Marek Vasut
2022-08-22 8:37 ` Marek Vasut
2022-08-22 8:41 ` Marek Vasut
2022-08-22 9:09 ` Mikko.Rapeli
2022-08-22 8:41 ` Alexander Kanavin
2022-08-22 10:35 ` Marek Vasut
2022-08-22 10:51 ` Mikko.Rapeli
2022-08-22 10:57 ` Quentin Schulz
2022-08-22 11:55 ` Marek Vasut
2022-08-22 14:17 ` Richard Purdie
2022-08-22 15:21 ` Peter Kjellerstedt
2022-08-22 16:39 ` Marek Vasut
2022-09-01 17:50 ` Marek Vasut
2022-09-02 15:54 ` Richard Purdie
2022-08-22 16:02 ` Luca Ceresoli [this message]
2022-08-22 16:06 ` Peter Kjellerstedt
2022-08-22 16:07 ` Richard Purdie
2022-08-23 14:34 ` Luca Ceresoli
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=20220822180241.5f625ed3@booty \
--to=luca.ceresoli@bootlin.com \
--cc=Martin.Jansa@gmail.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=marex@denx.de \
--cc=peter.kjellerstedt@axis.com \
--cc=richard.purdie@linuxfoundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.