Commit cd451e53 authored by Rico Tzschichholz's avatar Rico Tzschichholz

Update bugtracker links to https://gitlab.gnome.org/GNOME/vala/issues

parent 6ac8c9ee
AC_PREREQ([2.65])
AC_INIT([vala], m4_esyscmd([build-aux/git-version-gen .tarball-version]),
[https://bugzilla.gnome.org/browse.cgi?product=vala],
[https://gitlab.gnome.org/GNOME/vala/issues],
[vala],
[https://wiki.gnome.org/Projects/Vala])
AC_CONFIG_SRCDIR([Makefile.am])
......
......@@ -22,8 +22,8 @@ There are a number of ways you can contribute to improving the manual:
* Raise questions on the Vala communication channels so an edit is then made
* Post blogs and other tutorials that can then be used as source material
for updating the manual
* Raise a report in bugzilla
* Submit a patch to bugzilla with an amendment to the manual
* Raise a report in vala's issue tracker
* Submit a patch to vala's gitlab with an amendment to the manual
Editing the manual
------------------
......
......@@ -35,7 +35,7 @@ Shared library which contains the symbols
\fB\-\-include\-idl\fR=\fI\,IDL\/\fR
Other gidls to include
.SH BUGS
https://bugzilla.gnome.org/page.cgi?id=browse.html&product=vala
https://gitlab.gnome.org/GNOME/vala/issues
.SH "HOMEPAGE OR CONTACT"
https://wiki.gnome.org/Projects/Vala
.SH AUTHORS
......
......@@ -20,7 +20,7 @@ This can then be converted to a Vala API as follows:
.B vapigen --pkg cairo --vapidir . --library pango packages/pango/pango.gi
[BUGS]
https://bugzilla.gnome.org/page.cgi?id=browse.html&product=vala
https://gitlab.gnome.org/GNOME/vala/issues
[HOMEPAGE or CONTACT]
https://wiki.gnome.org/Projects/Vala
......
......@@ -211,7 +211,7 @@ This option is disabled by default for backward compatibility because it can
break ABI of existing projects.
.RE
.SH BUGS
https://bugzilla.gnome.org/page.cgi?id=browse.html&product=vala
https://gitlab.gnome.org/GNOME/vala/issues
.SH "HOMEPAGE OR CONTACT"
https://wiki.gnome.org/Projects/Vala
.SH FEATURES
......
......@@ -34,7 +34,7 @@ break ABI of existing projects.
.RE
[BUGS]
https://bugzilla.gnome.org/page.cgi?id=browse.html&product=vala
https://gitlab.gnome.org/GNOME/vala/issues
[HOMEPAGE or CONTACT]
https://wiki.gnome.org/Projects/Vala
......
......@@ -107,7 +107,7 @@ Disable colored output
\fB\-\-target\-glib\fR=\fI\,MAJOR\/\fR.MINOR
Target version of glib for code generation
.SH BUGS
https://bugzilla.gnome.org/page.cgi?id=browse.html&product=valadoc
https://gitlab.gnome.org/GNOME/vala/issues
.SH "HOMEPAGE OR CONTACT"
https://wiki.gnome.org/Projects/Valadoc
.SH AUTHORS
......
......@@ -10,7 +10,7 @@ Valadoc is a documentation generator for generating API documentation
from Vala source code based on libvala.
[BUGS]
https://bugzilla.gnome.org/page.cgi?id=browse.html&product=valadoc
https://gitlab.gnome.org/GNOME/vala/issues
[HOMEPAGE or CONTACT]
https://wiki.gnome.org/Projects/Valadoc
......
......@@ -48,7 +48,7 @@ Display version number
\fB\-q\fR, \fB\-\-quiet\fR
Do not print messages to the console
.SH BUGS
https://bugzilla.gnome.org/page.cgi?id=browse.html&product=vala
https://gitlab.gnome.org/GNOME/vala/issues
.SH "HOMEPAGE OR CONTACT"
https://wiki.gnome.org/Projects/Vala
.SH AUTHORS
......
......@@ -18,7 +18,7 @@ This can then be converted to a Vala API as follows:
.B vapigen --pkg cairo --vapidir . --library pango packages/pango/pango.gi
[BUGS]
https://bugzilla.gnome.org/page.cgi?id=browse.html&product=vala
https://gitlab.gnome.org/GNOME/vala/issues
[HOMEPAGE or CONTACT]
https://wiki.gnome.org/Projects/Vala
......
......@@ -33,7 +33,7 @@ binding.</description>
<homepage rdf:resource="https://wiki.gnome.org/Projects/Vala" />
<mailing-list rdf:resource="http://mail.gnome.org/mailman/listinfo/vala-list" />
<download-page rdf:resource="https://wiki.gnome.org/Projects/Vala/Release" />
<bug-database rdf:resource="https://bugzilla.gnome.org/browse.cgi?product=vala" />
<bug-database rdf:resource="https://gitlab.gnome.org/GNOME/vala/issues" />
<category rdf:resource="http://api.gnome.org/doap-extensions#core" />
<programming-language>Vala</programming-language>
......
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