Message ID | 20210629205757.38069-1-hugo@barrera.io |
---|---|
State | Accepted, archived |
Headers | show |
Series | [pacman-dev] Update broken links pointing to git.archlinux.org | expand |
Hi, Is this list the not the right place to send patches? Does this have issues? Cheers,, On Tue, 29 Jun 2021, at 20:57, Hugo Osvaldo Barrera wrote: > All of these links are broken since the recent move to > gitlab.archlinux.org. > > A few projects are, apparently, only available on GitHub, so I've linked > to that source (hopefully that's only temporary). > > For git-clone URLs, I've opted for the https URLs since those can be > used by anyone -- whereas the ssh URLs require the user to be registered > on the gitlab instance which is not open to the public yet. > > Signed-off-by: Hugo Osvaldo Barrera <hugo@barrera.io> > --- > doc/index.asciidoc | 19 ++++++++++--------- > doc/submitting-patches.asciidoc | 2 +- > doc/translation-help.asciidoc | 2 +- > 3 files changed, 12 insertions(+), 11 deletions(-) > > diff --git a/doc/index.asciidoc b/doc/index.asciidoc > index 47295f9b..a1bc4cc8 100644 > --- a/doc/index.asciidoc > +++ b/doc/index.asciidoc > @@ -59,11 +59,11 @@ configuration files dealing with pacman. > Changelog > ~~~~~~~~~ > For a good idea of what is going on in pacman development, take a look at the > -link:https://git.archlinux.org/pacman.git/[Git summary page] for the > +link:https://gitlab.archlinux.org/pacman/pacman[Git summary page] for the > project. > > See the most recent > -link:https://git.archlinux.org/pacman.git/tree/NEWS[NEWS] > +link:https://gitlab.archlinux.org/pacman/pacman/-/blob/master/NEWS[NEWS] > file for a not-as-frequently-updated list of changes. However, this should > contain the biggest changes in a format more concise than the commit log. > > @@ -220,12 +220,13 @@ these trees). > > The current development tree can be fetched with the following command: > > - git clone git://git.archlinux.org/pacman.git pacman > + git clone https://gitlab.archlinux.org/pacman/pacman.git > > which will fetch the full development history into a directory named pacman. > You can browse the source as well using > -link:https://git.archlinux.org/pacman.git/[cgit]. HTTP/HTTPS URLs are also > -available for cloning purposes; these URLs are listed at the above page. > +link:https://gitlab.archlinux.org/pacman/pacman/-/tree/master[gitlab]. > +HTTP/HTTPS URLs are also available for cloning purposes; these URLs are listed > +at the above page. > > If you are interested in hacking on pacman, it is highly recommended > you join > the mailing list mentioned above, as well as take a quick glance at our > @@ -243,13 +244,13 @@ Although the package manager itself is quite > simple, many scripts have been > developed that help automate building and installing packages. These > are used > extensively in link:https://archlinux.org/[Arch Linux]. Most of these > utilities > are available in the Arch Linux projects > -link:https://git.archlinux.org/[code browser]. > +link:https://gitlab.archlinux.org/archlinux[code browser]. > > Utilities available: > > -* link:https://git.archlinux.org/dbscripts.git/[dbscripts] - scripts > used by Arch Linux to manage the main package repositories > -* link:https://git.archlinux.org/devtools.git/[devtools] - tools to > assist in packaging and dependency checking > -* link:https://git.archlinux.org/namcap.git/[namcap] - a package > analysis utility written in python > +* link:https://github.com/archlinux/dbscripts[dbscripts] - scripts > used by Arch Linux to manage the main package repositories > +* link:https://github.com/archlinux/devtools[devtools] - tools to > assist in packaging and dependency checking > +* link:https://gitlab.archlinux.org/pacman/namcap[namcap] - a package > analysis utility written in python > > Bugs > ---- > diff --git a/doc/submitting-patches.asciidoc b/doc/submitting-patches.asciidoc > index 88b58ca5..14b80b61 100644 > --- a/doc/submitting-patches.asciidoc > +++ b/doc/submitting-patches.asciidoc > @@ -20,7 +20,7 @@ started with GIT if you have not worked with it before. > > The pacman code can be fetched using the following command: > > - git clone git://git.archlinux.org/pacman.git > + git clone https://gitlab.archlinux.org/pacman/pacman.git > > > Creating your patch > diff --git a/doc/translation-help.asciidoc b/doc/translation-help.asciidoc > index 5a67a2d6..4301852d 100644 > --- a/doc/translation-help.asciidoc > +++ b/doc/translation-help.asciidoc > @@ -78,7 +78,7 @@ Incremental Updates > If you have more advanced needs you will have to get a copy of the pacman > repository. > > - git clone git://git.archlinux.org/pacman.git pacman > + git clone https://gitlab.archlinux.org/pacman/pacman.git > > Next, you will need to run `./autogen.sh` and `./configure` in the base > directory to generate the correct Makefiles. At this point, all necessary > -- > 2.32.0 > >
On 17/7/21 4:29 am, Hugo Osvaldo Barrera wrote:
> Is this list the not the right place to send patches?
It is the right place. I am just lazy/busy at the moment.
Allan
On 30/6/21 6:57 am, Hugo Osvaldo Barrera wrote: > All of these links are broken since the recent move to > gitlab.archlinux.org. > > A few projects are, apparently, only available on GitHub, so I've linked > to that source (hopefully that's only temporary). > > For git-clone URLs, I've opted for the https URLs since those can be > used by anyone -- whereas the ssh URLs require the user to be registered > on the gitlab instance which is not open to the public yet. > > Signed-off-by: Hugo Osvaldo Barrera <hugo@barrera.io> > --- > doc/index.asciidoc | 19 ++++++++++--------- > doc/submitting-patches.asciidoc | 2 +- > doc/translation-help.asciidoc | 2 +- > 3 files changed, 12 insertions(+), 11 deletions(-) > > diff --git a/doc/index.asciidoc b/doc/index.asciidoc > index 47295f9b..a1bc4cc8 100644 > --- a/doc/index.asciidoc > +++ b/doc/index.asciidoc > @@ -59,11 +59,11 @@ configuration files dealing with pacman. > Changelog > ~~~~~~~~~ > For a good idea of what is going on in pacman development, take a look at the > -link:https://git.archlinux.org/pacman.git/[Git summary page] for the > +link:https://gitlab.archlinux.org/pacman/pacman[Git summary page] for the > project. > > See the most recent > -link:https://git.archlinux.org/pacman.git/tree/NEWS[NEWS] > +link:https://gitlab.archlinux.org/pacman/pacman/-/blob/master/NEWS[NEWS] > file for a not-as-frequently-updated list of changes. However, this should > contain the biggest changes in a format more concise than the commit log. > > @@ -220,12 +220,13 @@ these trees). > > The current development tree can be fetched with the following command: > > - git clone git://git.archlinux.org/pacman.git pacman > + git clone https://gitlab.archlinux.org/pacman/pacman.git > > which will fetch the full development history into a directory named pacman. > You can browse the source as well using > -link:https://git.archlinux.org/pacman.git/[cgit]. HTTP/HTTPS URLs are also > -available for cloning purposes; these URLs are listed at the above page. > +link:https://gitlab.archlinux.org/pacman/pacman/-/tree/master[gitlab]. > +HTTP/HTTPS URLs are also available for cloning purposes; these URLs are listed > +at the above page. This sentence makes no sense as you have updated the link to use the HTTPS URL. Remove sentence. > > If you are interested in hacking on pacman, it is highly recommended you join > the mailing list mentioned above, as well as take a quick glance at our > @@ -243,13 +244,13 @@ Although the package manager itself is quite simple, many scripts have been > developed that help automate building and installing packages. These are used > extensively in link:https://archlinux.org/[Arch Linux]. Most of these utilities > are available in the Arch Linux projects > -link:https://git.archlinux.org/[code browser]. > +link:https://gitlab.archlinux.org/archlinux[code browser]. > > Utilities available: > > -* link:https://git.archlinux.org/dbscripts.git/[dbscripts] - scripts used by Arch Linux to manage the main package repositories > -* link:https://git.archlinux.org/devtools.git/[devtools] - tools to assist in packaging and dependency checking > -* link:https://git.archlinux.org/namcap.git/[namcap] - a package analysis utility written in python > +* link:https://github.com/archlinux/dbscripts[dbscripts] - scripts used by Arch Linux to manage the main package repositories > +* link:https://github.com/archlinux/devtools[devtools] - tools to assist in packaging and dependency checking > +* link:https://gitlab.archlinux.org/pacman/namcap[namcap] - a package analysis utility written in python https://gitlab.archlinux.org/pacman/namcap In fact, delete this entire section. I don't care about other utilities. > Bugs > ---- > diff --git a/doc/submitting-patches.asciidoc b/doc/submitting-patches.asciidoc > index 88b58ca5..14b80b61 100644 > --- a/doc/submitting-patches.asciidoc > +++ b/doc/submitting-patches.asciidoc > @@ -20,7 +20,7 @@ started with GIT if you have not worked with it before. > > The pacman code can be fetched using the following command: > > - git clone git://git.archlinux.org/pacman.git > + git clone https://gitlab.archlinux.org/pacman/pacman.git > > > Creating your patch > diff --git a/doc/translation-help.asciidoc b/doc/translation-help.asciidoc > index 5a67a2d6..4301852d 100644 > --- a/doc/translation-help.asciidoc > +++ b/doc/translation-help.asciidoc > @@ -78,7 +78,7 @@ Incremental Updates > If you have more advanced needs you will have to get a copy of the pacman > repository. > > - git clone git://git.archlinux.org/pacman.git pacman > + git clone https://gitlab.archlinux.org/pacman/pacman.git > > Next, you will need to run `./autogen.sh` and `./configure` in the base > directory to generate the correct Makefiles. At this point, all necessary >
I've removed the now-senseless sentence, as well as the Other Utilities paragraph. Do you think it makes sense to mentioned any of those (e.g.: devtools) in the "See Also" section of the man pages? Cheers, -- Hugo
diff --git a/doc/index.asciidoc b/doc/index.asciidoc index 47295f9b..a1bc4cc8 100644 --- a/doc/index.asciidoc +++ b/doc/index.asciidoc @@ -59,11 +59,11 @@ configuration files dealing with pacman. Changelog ~~~~~~~~~ For a good idea of what is going on in pacman development, take a look at the -link:https://git.archlinux.org/pacman.git/[Git summary page] for the +link:https://gitlab.archlinux.org/pacman/pacman[Git summary page] for the project. See the most recent -link:https://git.archlinux.org/pacman.git/tree/NEWS[NEWS] +link:https://gitlab.archlinux.org/pacman/pacman/-/blob/master/NEWS[NEWS] file for a not-as-frequently-updated list of changes. However, this should contain the biggest changes in a format more concise than the commit log. @@ -220,12 +220,13 @@ these trees). The current development tree can be fetched with the following command: - git clone git://git.archlinux.org/pacman.git pacman + git clone https://gitlab.archlinux.org/pacman/pacman.git which will fetch the full development history into a directory named pacman. You can browse the source as well using -link:https://git.archlinux.org/pacman.git/[cgit]. HTTP/HTTPS URLs are also -available for cloning purposes; these URLs are listed at the above page. +link:https://gitlab.archlinux.org/pacman/pacman/-/tree/master[gitlab]. +HTTP/HTTPS URLs are also available for cloning purposes; these URLs are listed +at the above page. If you are interested in hacking on pacman, it is highly recommended you join the mailing list mentioned above, as well as take a quick glance at our @@ -243,13 +244,13 @@ Although the package manager itself is quite simple, many scripts have been developed that help automate building and installing packages. These are used extensively in link:https://archlinux.org/[Arch Linux]. Most of these utilities are available in the Arch Linux projects -link:https://git.archlinux.org/[code browser]. +link:https://gitlab.archlinux.org/archlinux[code browser]. Utilities available: -* link:https://git.archlinux.org/dbscripts.git/[dbscripts] - scripts used by Arch Linux to manage the main package repositories -* link:https://git.archlinux.org/devtools.git/[devtools] - tools to assist in packaging and dependency checking -* link:https://git.archlinux.org/namcap.git/[namcap] - a package analysis utility written in python +* link:https://github.com/archlinux/dbscripts[dbscripts] - scripts used by Arch Linux to manage the main package repositories +* link:https://github.com/archlinux/devtools[devtools] - tools to assist in packaging and dependency checking +* link:https://gitlab.archlinux.org/pacman/namcap[namcap] - a package analysis utility written in python Bugs ---- diff --git a/doc/submitting-patches.asciidoc b/doc/submitting-patches.asciidoc index 88b58ca5..14b80b61 100644 --- a/doc/submitting-patches.asciidoc +++ b/doc/submitting-patches.asciidoc @@ -20,7 +20,7 @@ started with GIT if you have not worked with it before. The pacman code can be fetched using the following command: - git clone git://git.archlinux.org/pacman.git + git clone https://gitlab.archlinux.org/pacman/pacman.git Creating your patch diff --git a/doc/translation-help.asciidoc b/doc/translation-help.asciidoc index 5a67a2d6..4301852d 100644 --- a/doc/translation-help.asciidoc +++ b/doc/translation-help.asciidoc @@ -78,7 +78,7 @@ Incremental Updates If you have more advanced needs you will have to get a copy of the pacman repository. - git clone git://git.archlinux.org/pacman.git pacman + git clone https://gitlab.archlinux.org/pacman/pacman.git Next, you will need to run `./autogen.sh` and `./configure` in the base directory to generate the correct Makefiles. At this point, all necessary
All of these links are broken since the recent move to gitlab.archlinux.org. A few projects are, apparently, only available on GitHub, so I've linked to that source (hopefully that's only temporary). For git-clone URLs, I've opted for the https URLs since those can be used by anyone -- whereas the ssh URLs require the user to be registered on the gitlab instance which is not open to the public yet. Signed-off-by: Hugo Osvaldo Barrera <hugo@barrera.io> --- doc/index.asciidoc | 19 ++++++++++--------- doc/submitting-patches.asciidoc | 2 +- doc/translation-help.asciidoc | 2 +- 3 files changed, 12 insertions(+), 11 deletions(-)