Commit 7fd415bf authored by Uwe Scholz's avatar Uwe Scholz

Migrate links from bugzilla to gitlab

parent 40d19c2e
Search on http://bugzilla.gnome.org for a list of known GNOME Commander's bug.
Search on https://gitlab.gnome.org/GNOME/gnome-commander/issues for a list of known GNOME Commander's bug.
If you find a new bug, please report it at
http://bugzilla.gnome.org/enter_bug.cgi?product=gnome-commander.
If you find a new bug, please report it there.
......@@ -131,8 +131,8 @@ in the AUTHORS file.
5. Problem reporting
--------------------------------
Bugs should be reported to the GNOME bug tracking system
(http://bugzilla.gnome.org, product gnome-commander). You will need to create an
Bugs should be reported to the GitLab instance of Gnome
(https://gitlab.gnome.org/GNOME/gnome-commander/issues). You will need to create an
account for yourself.
You can also report bugs using the GNOME program bug-buddy.
......
......@@ -9,7 +9,7 @@ GNOME Commander is a fast and powerful twin-panel file manager for the Linux des
![ScreenShot](https://gcmd.github.io/ss/MainWin-Classic.png)
* Website: https://gcmd.github.io/
* Bugs: http://bugzilla.gnome.org/browse.cgi?product=gnome-commander
* Bugs: https://gitlab.gnome.org/GNOME/gnome-commander/issues
### Mailing lists ###
......@@ -57,7 +57,7 @@ If you have created a new plugin let us know about it on the [developer mailing
### Problem reporting ###
Bugs should be reported on [GNOME Bugzilla](http://bugzilla.gnome.org/browse.cgi?product=gnome-commander).
Bugs should be reported on [GNOME GitLab](https://gitlab.gnome.org/GNOME/gnome-commander/issues).
You will need to create an account for yourself.
In the bug report please include:
......@@ -76,7 +76,7 @@ For instance:
it will be more useful if the stack trace is produced running the test
program with the --sync command line option.
See the Bugzilla [project page](http://bugzilla.gnome.org/browse.cgi?product=gnome-commander) for the list of known bugs.
Also, have a look at the list of known bugs on GitLab bevore opening a new bug.
## Building ##
......
AC_INIT([gnome-commander],[1.9.0],[http://bugzilla.gnome.org/enter_bug.cgi?product=gnome-commander])
AC_INIT([gnome-commander],[1.9.0],[https://gitlab.gnome.org/GNOME/gnome-commander/issues])
AC_CONFIG_SRCDIR(src/gnome-cmd-includes.h)
AC_CONFIG_MACRO_DIR([m4])
......
......@@ -39,7 +39,7 @@
</screenshot>
</screenshots>
<url type="homepage">http://gcmd.github.io/index.html</url>
<url type="bugtracker">https://bugzilla.gnome.org/enter_bug.cgi?product=gnome-commander</url>
<url type="bugtracker">https://gitlab.gnome.org/GNOME/gnome-commander/issues</url>
<url type="donation">https://gcmd.github.io/#donations</url>
<url type="help">http://gcmd.github.io/doc.html</url>
<url type="translate">https://gcmd.github.io/dev.html#trnsl</url>
......
......@@ -12,7 +12,7 @@
<name>Uwe Scholz</name>
</maintainer>
<changelog>https://git.gnome.org/browse/gnome-commander/tree/NEWS?h=gcmd-1-6</changelog>
<bugs-to>https://bugzilla.gnome.org/browse.cgi?product=gnome-commander</bugs-to>
<bugs-to>https://gitlab.gnome.org/GNOME/gnome-commander/issues</bugs-to>
<remote-id type="freecode">gnome-commander</remote-id>
</upstream>
<use>
......
......@@ -458,7 +458,7 @@
<releaseinfo>This manual describes version &appversion; of &app;. </releaseinfo>
<legalnotice>
<title>Feedback</title>
<para>You can report or view &app; bugs at the <ulink type="http" url="http://bugzilla.gnome.org/browse.cgi?product=gnome-commander">the gnome.org Bugzilla</ulink>.</para>
<para>You can report or view &app; bugs at <ulink type="http" url="https://gitlab.gnome.org/GNOME/gnome-commander/issues">gitlab.gnome.org</ulink>.</para>
<!-- Translators may also add here feedback address for translations -->
</legalnotice>
......@@ -7225,7 +7225,7 @@
</row>
<row valign="top">
<entry><para>Report a problem</para></entry>
<entry><para>Report problem to Bugzilla</para></entry>
<entry><para>Report problem to gitlab.gnome.org</para></entry>
</row>
<row valign="top">
<entry><para>Root directory</para></entry>
......@@ -7592,7 +7592,7 @@
-->
<sect1 id="gnome-commander-bugs">
<title>Known Bugs and Limitations</title>
<para>You can report or view &app; bugs at the <ulink type="http" url="http://bugzilla.gnome.org/browse.cgi?product=gnome-commander">the gnome.org Bugzilla</ulink>.</para>
<para>You can report or view &app; bugs at <ulink type="http" url="https://gitlab.gnome.org/GNOME/gnome-commander/issues">gitlab.gnome.org</ulink>.</para>
<para>Some words about bugs: Though &app; is relatively free from bugs and is a quite mature program, no programs will ever be totally bug free.
New bugs can be introduced with new features, or through other programs and libraries it depends on,
this goes especially for development and testing versions. Quality bug reporting is very important
......@@ -7647,7 +7647,7 @@
<title>Bug Reporting</title>
<para>
If you found a bug, you can check if it is already reported on our
<ulink type="http" url="https://bugzilla.gnome.org/browse.cgi?product=gnome-commander">Bugzilla</ulink>
<ulink type="http" url="https://gitlab.gnome.org/GNOME/gnome-commander/issues">GitLab</ulink>
page at Gnome.org. If not, please report the bug. If you want to fix it by yourself
have a look at the section <xref linkend="gnome-commander-development-version"></xref>.</para>
</sect2>
......
......@@ -9,7 +9,7 @@
<homepage rdf:resource="http://gcmd.github.io/" />
<mailing-list rdf:resource="http://lists.nongnu.org/mailman/listinfo/gcmd-devel" />
<download-page rdf:resource="http://download.gnome.org/sources/gnome-commander/" />
<bug-database rdf:resource="http://bugzilla.gnome.org/browse.cgi?product=gnome-commander" />
<bug-database rdf:resource="https://gitlab.gnome.org/GNOME/gnome-commander/issues" />
<category rdf:resource="http://api.gnome.org/doap-extensions#desktop" />
<programming-language>C</programming-language>
<programming-language>C++</programming-language>
......
......@@ -1976,7 +1976,7 @@ void help_problem (GtkMenuItem *menuitem, gpointer not_used)
{
GError *error = NULL;
if (!gtk_show_uri (NULL, "http://bugzilla.gnome.org/browse.cgi?product=gnome-commander", GDK_CURRENT_TIME, &error))
if (!gtk_show_uri (NULL, "https://gitlab.gnome.org/GNOME/gnome-commander/issues", GDK_CURRENT_TIME, &error))
gnome_cmd_error_message (_("There was an error reporting problem."), error);
}
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment