All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: Giulio Benetti <giulio.benetti@benettiengineering.com>,
	Romain Naour <romain.naour@gmail.com>,
	Buildroot List <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH] docs, package/gcc: switch to Gitlab issue tracker
Date: Sat, 15 Jun 2024 10:08:13 +0200	[thread overview]
Message-ID: <Zm1L7ZlBXIV2iowQ@landeda> (raw)
In-Reply-To: <20240514085801.3202503-1-thomas.petazzoni@bootlin.com>

Thomas, All,

On 2024-05-14 10:58 +0200, Thomas Petazzoni via buildroot spake thusly:
> Our Bugzilla is so slow and unstable that it has become
> unusable. Let's switch to using the Gitlab issue tracker instead.

It would have been nice if you had suggested a plan to deal with the
existing issues.

We can extract the list of bugs from Bugzilla (as CSV):
    https://bugs.busybox.net/buglist.cgi?bug_status=__all__&limit=0&list_id=26023&product=buildroot&query_format=specific&ctype=csv&human=1

And then we can extract individual bugs (as XML):
    https://bugs.busybox.net/show_bug.cgi?ctype=xml&id=3

Gitlab can import from CSV:
    https://docs.gitlab.com/ee/user/project/issues/csv_import.html

However, the Gitlab import is ultra limited: it can only import issues
as a title, a description, a due date (optional), and a milestone
(optional).

There is no place for comments, attachments, status...

So, what do we do for the existing issues?

Regards,
Yann E. MORIN.

> There are still lots of references to the Bugzilla bug tracker in our
> News page at https://buildroot.org/news.html, but these are for older
> news.
> 
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> ---
>  docs/manual/contribute.adoc  | 2 +-
>  docs/manual/resources.adoc   | 2 +-
>  docs/website/contribute.html | 2 +-
>  docs/website/support.html    | 5 +++--
>  package/gcc/gcc.mk           | 2 +-
>  5 files changed, 7 insertions(+), 6 deletions(-)
> 
> diff --git a/docs/manual/contribute.adoc b/docs/manual/contribute.adoc
> index 6ff6c15314..c88035597e 100644
> --- a/docs/manual/contribute.adoc
> +++ b/docs/manual/contribute.adoc
> @@ -25,7 +25,7 @@ for more information on obtaining a Buildroot git tree.
>  === Reproducing, analyzing and fixing bugs
>  
>  A first way of contributing is to have a look at the open bug reports in
> -the https://bugs.buildroot.org/buglist.cgi?product=buildroot[Buildroot bug
> +the https://gitlab.com/buildroot.org/buildroot/-/issues[Buildroot bug
>  tracker]. As we strive to keep the bug count as small as possible, all
>  help in reproducing, analyzing and fixing reported bugs is more than
>  welcome. Don't hesitate to add a comment to bug reports reporting your
> diff --git a/docs/manual/resources.adoc b/docs/manual/resources.adoc
> index 68b7eb9062..4ef709c317 100644
> --- a/docs/manual/resources.adoc
> +++ b/docs/manual/resources.adoc
> @@ -40,7 +40,7 @@ better as it will reach more people, both developers and users.
>  Bug tracker::
>  +
>  Bugs in Buildroot can be reported via the mailing list or alternatively
> -via the https://bugs.buildroot.org/buglist.cgi?product=buildroot[Buildroot
> +via the https://gitlab.com/buildroot.org/buildroot/-/issues[Buildroot
>  bugtracker]. Please refer to xref:reporting-bugs[] before creating a bug
>  report.
>  
> diff --git a/docs/website/contribute.html b/docs/website/contribute.html
> index aa1cf93f1b..95028ee788 100644
> --- a/docs/website/contribute.html
> +++ b/docs/website/contribute.html
> @@ -13,7 +13,7 @@
>  
>        <ul>
>  	<li>Reproducing, analyzing and fixing bugs from our
> -	  <a href="https://bugs.buildroot.org/">bug tracker</a></li>
> +	  <a href="https://gitlab.com/buildroot.org/buildroot/-/issues">bug tracker</a></li>
>  	<li>Analyzing and fixing <a href="http://autobuild.buildroot.org/">
>  	    autobuild failures</a></li>
>  	<li>Reviewing and testing patches sent by other developers. See the
> diff --git a/docs/website/support.html b/docs/website/support.html
> index 28873c6d76..75551b770e 100644
> --- a/docs/website/support.html
> +++ b/docs/website/support.html
> @@ -80,8 +80,9 @@
>  		  <img class="img-responsive" src="images/bug-buddy.png" style="max-width:50px; margin-bottom:10px;">
>  		</div>
>  		<div class="col-sm-11">
> -		  <p>If you think you found a bug in Buildroot, you can use the
> -		    <a href="https://bugs.buildroot.org/">Bug Tracker</a> to post your bugs and/or
> +		  <p>If you think you found a bug in Buildroot, you
> +		  can use the
> +		    <a href="https://gitlab.com/buildroot.org/buildroot/-/issues">Bug Tracker</a> to post your bugs and/or
>  		    participate to find solutions to existing problems.</p>
>  
>  		  <p>Note: patches are only accepted through the mailing list.</p>
> diff --git a/package/gcc/gcc.mk b/package/gcc/gcc.mk
> index 672f9472a9..e4780353cb 100644
> --- a/package/gcc/gcc.mk
> +++ b/package/gcc/gcc.mk
> @@ -83,7 +83,7 @@ HOST_GCC_COMMON_CONF_OPTS = \
>  	--with-mpc=$(HOST_DIR) \
>  	--with-mpfr=$(HOST_DIR) \
>  	--with-pkgversion="Buildroot $(BR2_VERSION_FULL)" \
> -	--with-bugurl="http://bugs.buildroot.net/" \
> +	--with-bugurl="https://gitlab.com/buildroot.org/buildroot/-/issues" \
>  	--without-zstd
>  
>  ifeq ($(BR2_REPRODUCIBLE),y)
> -- 
> 2.45.0
> 
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  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.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2024-06-15  8:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-14  8:58 [Buildroot] [PATCH] docs, package/gcc: switch to Gitlab issue tracker Thomas Petazzoni via buildroot
2024-06-13 21:41 ` Thomas Petazzoni via buildroot
2024-06-13 21:56   ` Giulio Benetti
2024-06-15  8:08 ` Yann E. MORIN [this message]
2024-06-15 12:46   ` Thomas Petazzoni via buildroot
2024-06-15 14:30     ` Yann E. MORIN
2024-06-15 14:41       ` Peter Korsgaard
2024-06-15 14:41 ` 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=Zm1L7ZlBXIV2iowQ@landeda \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@buildroot.org \
    --cc=giulio.benetti@benettiengineering.com \
    --cc=romain.naour@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    /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.