Use https instead of http in links

This is the modern way, and also removes many warnings from
`check-links.sh` output.
This commit is contained in:
Otto Liljalaakso 2024-06-03 22:58:08 +03:00
commit a1287f0c49
13 changed files with 25 additions and 25 deletions

View file

@ -1,7 +1,7 @@
The text of and illustrations in this document are licensed by Red Hat
under a Creative Commons Attribution–Share Alike 3.0 Unported license
("CC-BY-SA"). An explanation of CC-BY-SA is available at
http://creativecommons.org/licenses/by-sa/3.0/. In accordance with
https://creativecommons.org/licenses/by-sa/3.0/. In accordance with
CC-BY-SA, if you distribute this document or an adaptation of it, you
must provide the URL for the original version.

View file

@ -28,7 +28,7 @@ Some useful information about AsciiDoc can be found below:
This repository attempts to follow the following:
* Use [Semantic Line Breaks](http://sembr.org/) to make diffing simpler.
* Use [Semantic Line Breaks](https://sembr.org/) to make diffing simpler.
* Prefer `https://example.com[here]` over `link:https://example.com[here]`
* Prefer `[#some-ref]` over `[[some-ref]]`

View file

@ -110,7 +110,7 @@ Instead, use a rpath to let the application locate the library.
See also:
* link:#no_soname[no-soname]
* http://lists.fedoraproject.org/pipermail/devel/2012-April/166104.html[thread on fedora-devel]
* https://lists.fedoraproject.org/pipermail/devel/2012-April/166104.html[thread on fedora-devel]
[[no_binary]]
== no-binary

View file

@ -34,7 +34,7 @@ perhaps from the previous maintainer or a potential sponsor.
If you plan to comment on review requests to demonstrate your level of understanding,
you can search the https://fedoraproject.org/PackageReviewStatus/in_progress.html[list of reviews in progress]
and the http://fedoraproject.org/PackageReviewStatus/reviewable.html[list of unassigned review requests]
and the https://fedoraproject.org/PackageReviewStatus/reviewable.html[list of unassigned review requests]
for review requests to comment on.
[#how_to_find_a_sponsor]

View file

@ -25,7 +25,7 @@ They will be used during the package review.
. Upload your SRPM and SPEC files onto the internet somewhere.
** If you have already got a Fedora Account
then you can use your storage at http://fedorapeople.org for this.
then you can use your storage at https://fedorapeople.org for this.
. Make sure you have a Bugzilla account at bugzilla.redhat.com

View file

@ -24,7 +24,7 @@ make sure that the software is not already in the Fedora repository:
* Check if the package already exists by searching in
https://packages.fedoraproject.org/[Fedora Packages].
* Search in the http://fedoraproject.org/PackageReviewStatus/[Review Tracker]
* Search in the https://fedoraproject.org/PackageReviewStatus/[Review Tracker]
for packages under review.
* Check the https://packager-dashboard.fedoraproject.org/user/orphan[orphaned or retired packages that need new maintainers].
@ -71,7 +71,7 @@ Fill out https://bugzilla.redhat.com/bugzilla/enter_bug.cgi?product=Fedora&forma
* Before submitting your request,
be sure there’s not a previous request for the same package.
There is a convenient search box on the http://fedoraproject.org/PackageReviewStatus/[package review status page].
There is a convenient search box on the https://fedoraproject.org/PackageReviewStatus/[package review status page].
* Make sure that you put the *name of the package*
(excluding version and release numbers)

View file

@ -3,7 +3,7 @@ include::{partialsdir}/attributes.adoc[]
= Package Maintenance Guide
This page provides some basic instructions for day-to-day usage
of the http://git-scm.com/[git]-based package maintenance system for Fedora.
of the https://git-scm.com/[git]-based package maintenance system for Fedora.
It is intended primarily for new and current Fedora package maintainers,
but does briefly xref:using_fedpkg_anonymously[cover anonymous read-only use of the system].
It is not a guide to RPM packaging per se.
@ -376,7 +376,7 @@ and consider how your changes will affect others.
This is a large topic and somewhat beyond the scope of this guide,
but we can give basic pointers.
There are other good references in the http://git-scm.com/book/en/Git-Branching-Basic-Branching-and-Merging[Git book]
There are other good references in the https://git-scm.com/book/en/Git-Branching-Basic-Branching-and-Merging[Git book]
and at https://help.github.com/articles/resolving-a-merge-conflict-from-the-command-line[GitHub].
When you merge and a conflict occurs,

View file

@ -187,7 +187,7 @@ who is a member of the https://accounts.fedoraproject.org/group/packager/[packag
the review can still proceed to completion
but they will need to find a sponsor at some point.)
* Search http://fedoraproject.org/PackageReviewStatus/[Package Review Tracker] for a review request
* Search https://fedoraproject.org/PackageReviewStatus/[Package Review Tracker] for a review request
that needs a reviewer: `fedora-review` flag is blank or the bug is assigned to `nobody@fedoraproject.org`.
* If you notice some issues that need to be solved
@ -327,6 +327,6 @@ by someone doing their first package review.
[#tracking_of_package_requests]
== Tracking of Package Requests
The http://fedoraproject.org/PackageReviewStatus[Package Review Tracker] provides various review-related reports
The https://fedoraproject.org/PackageReviewStatus[Package Review Tracker] provides various review-related reports
and a simple way to search for reviews
by package name or reporter name or others.

View file

@ -55,7 +55,7 @@ Release: %autorelease
Summary: Produces a familiar, friendly greeting
License: GPL-3.0-or-later
URL: https://www.gnu.org/software/hello/
Source: http://ftp.gnu.org/gnu/hello/hello-%{version}.tar.gz
Source: https://ftp.gnu.org/gnu/hello/hello-%{version}.tar.gz
BuildRequires: gcc
BuildRequires: make
BuildRequires: texinfo
@ -342,8 +342,8 @@ Release: %autorelease
Summary: Produces a familiar, friendly greeting
License: GPL-3.0-or-later
URL: http://ftp.gnu.org/gnu/%{name}
Source: http://ftp.gnu.org/gnu/%{name}/%{name}-%{version}.tar.gz
URL: https://ftp.gnu.org/gnu/%{name}
Source: https://ftp.gnu.org/gnu/%{name}/%{name}-%{version}.tar.gz
BuildRequires: bash
BuildRequires: coreutils

View file

@ -295,7 +295,7 @@ Fixes related to bundling should of course be sent upstream if possible.
== References
* http://fedoraproject.org/wiki/Objectives
* https://fedoraproject.org/wiki/Objectives
* xref:packaging-guidelines::index.adoc#_all_patches_should_have_an_upstream_bug_link_or_comment[All patches should have an upstream bug link or comment]
* http://fedoraproject.org/wiki/PackageMaintainers/TrackingUpstream
* http://fedoraproject.org/wiki/PackageMaintainers/TrackingDownstream
* https://fedoraproject.org/wiki/PackageMaintainers/TrackingUpstream
* https://fedoraproject.org/wiki/PackageMaintainers/TrackingDownstream

View file

@ -84,11 +84,11 @@ but no scratch build will be made.
[#related_projects]
== Related Projects
* http://github.com/tannewt/open-source-watershed[OSWatershed] - Monitors several distributions at once
* https://github.com/tannewt/open-source-watershed[OSWatershed] - Monitors several distributions at once
* https://ppisar.fedorapeople.org/cpandistributionsinfedora.xhtml[Perl package monitoring]
* http://rpms.famillecollet.com/rpmphp/[Reports from Remi] PECL, pear and R extensions upstream comparison and stable repo with rawhide comparison for all packages
* http://distrowatch.com/table.php?distribution=fedora[DistroWatch.com: Fedora]
* http://youri.zarb.org/[Youri] http://check.mageia.org/[in action] http://svnweb.mageia.org/adm/puppet/modules/youri-check/[puppet modules] A generic framework
* https://rpms.remirepo.net/rpmphp/[Reports from Remi] PECL, pear and R extensions upstream comparison and stable repo with rawhide comparison for all packages
* https://distrowatch.com/table.php?distribution=fedora[DistroWatch.com: Fedora]
* Youri https://check.mageia.org/[in action] https://svnweb.mageia.org/adm/puppet/modules/youri-check/[puppet modules] A generic framework
* https://github.com/jness/ossvt[ossvt] Developed for https://ius.io/[IUS]
* https://fedorapeople.org/cgit/till/public_git/cnucnu.git/[cnucnu] — the tool previously used to provide this service for Fedora
* http://repology.org/metapackages/outdated-in-repo/fedora_rawhide/[Repology] cross distro version comparison
* https://repology.org/metapackages/outdated-in-repo/fedora_rawhide/[Repology] cross distro version comparison

View file

@ -258,10 +258,10 @@ For example to get the latest buildroot for `f{MAJOROSVER}-build` run:
[subs="attributes+"]
....
koji mock-config --tag f{MAJOROSVER}-build --arch=x86_64 --topurl=http://kojipkgs.fedoraproject.org/ f{MAJOROSVER}
koji mock-config --tag f{MAJOROSVER}-build --arch=x86_64 --topurl=https://kojipkgs.fedoraproject.org/ f{MAJOROSVER}
....
You must pass `--topurl=http://kojipkgs.fedoraproject.org/` to any mock-config command
You must pass `--topurl=https://kojipkgs.fedoraproject.org/` to any mock-config command
to get a working mock-config from Fedora's koji.
[#using_koji_to_control_tasks]

View file

@ -35,7 +35,7 @@ for writing SPEC files for software in Fedora.
[#introduction_to_packaging]
=== Introduction to packaging
* http://rpm.org/max-rpm-snapshot/[Maximum RPM Book]
* https://rpm.org/max-rpm-snapshot/[Maximum RPM Book]
— most detailed, but slightly obsolete.
* https://rpm-packaging-guide.github.io/[RPM Packaging Guide]