From abc58f2906a30f552e306308129fc635220d94bf Mon Sep 17 00:00:00 2001 From: Jason Tibbitts Date: Oct 08 2021 22:40:03 +0000 Subject: [PATCH 1/31] Use https for links in Ada guidelines --- diff --git a/guidelines/modules/ROOT/pages/Ada.adoc b/guidelines/modules/ROOT/pages/Ada.adoc index de27b4e..b639e20 100644 --- a/guidelines/modules/ROOT/pages/Ada.adoc +++ b/guidelines/modules/ROOT/pages/Ada.adoc @@ -123,4 +123,4 @@ For Ada packages, some of the rpmlint messages, such as “executable-stack”, can be disregarded, because GNAT uses trampolines for pointers to nested functions. -(See for example http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24355[this entry in the GCC Bugzilla].) +(See for example https://gcc.gnu.org/bugzilla/show_bug.cgi?id=24355[this entry in the GCC Bugzilla].) From b5c24fb1bc2b17eb72c82e1a7ad9fbcf7a4acb5b Mon Sep 17 00:00:00 2001 From: Jason Tibbitts Date: Oct 08 2021 22:40:04 +0000 Subject: [PATCH 2/31] Use https for links in AppData guidelines --- diff --git a/guidelines/modules/ROOT/pages/AppData.adoc b/guidelines/modules/ROOT/pages/AppData.adoc index 8952c2f..8c2f15d 100644 --- a/guidelines/modules/ROOT/pages/AppData.adoc +++ b/guidelines/modules/ROOT/pages/AppData.adoc @@ -12,7 +12,7 @@ If a package contains an add-on for GUI application, then it SHOULD install a `+.metainfo.xml+` file into `+%{_metainfodir}+`. Installed `+.metainfo.xml+` files MUST follow -the http://www.freedesktop.org/software/appstream/docs/sect-Quickstart-Addons.html[AppStream add-ons specification]. +the https://www.freedesktop.org/software/appstream/docs/sect-Quickstart-Addons.html[AppStream add-ons specification]. The AppData files MUST correctly validate using `+appstream-util validate-relax+`. From 5c79652e54fcd09edb43da5447d4e1fd3e1bca6f Mon Sep 17 00:00:00 2001 From: Jason Tibbitts Date: Oct 08 2021 22:40:04 +0000 Subject: [PATCH 3/31] Use https for links in dependency filtering guidelines --- diff --git a/guidelines/modules/ROOT/pages/AutoProvidesAndRequiresFiltering.adoc b/guidelines/modules/ROOT/pages/AutoProvidesAndRequiresFiltering.adoc index 87f2f5a..3b84f35 100644 --- a/guidelines/modules/ROOT/pages/AutoProvidesAndRequiresFiltering.adoc +++ b/guidelines/modules/ROOT/pages/AutoProvidesAndRequiresFiltering.adoc @@ -132,7 +132,7 @@ foo(x86-64) = 1.0-1.fc19 [...] .... -You can take a look at a http://lists.fedoraproject.org/pipermail/devel/2012-June/169190.html[more complex example] on the mailing list. This can be a pain to maintain if the upstream changes the names of its private libraries but it is the only way to deal with this at present. There may be a better means in http://lists.rpm.org/pipermail/rpm-maint/2013-January/003349.html[the future] but there are no solid plans on when those might be coded as of yet.. +You can take a look at a https://lists.fedoraproject.org/pipermail/devel/2012-June/169190.html[more complex example] on the mailing list. This can be a pain to maintain if the upstream changes the names of its private libraries but it is the only way to deal with this at present. There may be a better means in https://lists.rpm.org/pipermail/rpm-maint/2013-January/003349.html[the future] but there are no solid plans on when those might be coded as of yet.. === Arch-specific extensions to scripting languages From 2883df42f7a8f7a48d7d9924151c7bbbc56842de Mon Sep 17 00:00:00 2001 From: Jason Tibbitts Date: Oct 08 2021 22:40:04 +0000 Subject: [PATCH 4/31] Use https for links in D guidelines --- diff --git a/guidelines/modules/ROOT/pages/D.adoc b/guidelines/modules/ROOT/pages/D.adoc index a3afd1f..3c51aab 100644 --- a/guidelines/modules/ROOT/pages/D.adoc +++ b/guidelines/modules/ROOT/pages/D.adoc @@ -62,8 +62,8 @@ Release: 1%{?dist} Summary: Does foo in D Group: Development/Libraries License: LGPLv2+ -URL: http://anywhere.com/ -Source0: http://anywhere.com/%{name}-%{version}.tar.bz2 +URL: https://anywhere.com/ +Source0: https://anywhere.com/%{name}-%{version}.tar.bz2 BuildRequires: ldc Requires: tango From cbeb226b8ff4bd07084e0e798cda41ca0323bbfb Mon Sep 17 00:00:00 2001 From: Jason Tibbitts Date: Oct 08 2021 22:40:04 +0000 Subject: [PATCH 5/31] Use https for links in Default Services guidelines --- diff --git a/guidelines/modules/ROOT/pages/DefaultServices.adoc b/guidelines/modules/ROOT/pages/DefaultServices.adoc index 641b057..46e4302 100644 --- a/guidelines/modules/ROOT/pages/DefaultServices.adoc +++ b/guidelines/modules/ROOT/pages/DefaultServices.adoc @@ -5,10 +5,10 @@ For the purposes of this document, a "service" is defined as one or more of: -* A daemon or process started using a http://www.freedesktop.org/software/systemd/man/systemd.service.html[systemd service unit]. -* A daemon or process that is invoked by socket activation, either by using a http://www.freedesktop.org/software/systemd/man/systemd.socket.html[systemd socket unit], http://standards.freedesktop.org/desktop-entry-spec/1.1/ar01s07.html[D-BUS activation] or similar behavior. +* A daemon or process started using a https://www.freedesktop.org/software/systemd/man/systemd.service.html[systemd service unit]. +* A daemon or process that is invoked by socket activation, either by using a https://www.freedesktop.org/software/systemd/man/systemd.socket.html[systemd socket unit], https://standards.freedesktop.org/desktop-entry-spec/1.1/ar01s07.html[D-BUS activation] or similar behavior. * A daemon or process that is invoked by hardware activation (i.e. started via a udev rule). -* A http://www.freedesktop.org/software/systemd/man/systemd.timer.html[systemd timer unit] that runs periodically. +* A https://www.freedesktop.org/software/systemd/man/systemd.timer.html[systemd timer unit] that runs periodically. Note that this includes processes which are not persistent. If something started by a systemd service unit runs for a short period of time and then exits, it is still a service. An example would be `+iptables+`. This also includes services in the user session (i.e. started per-user by the `systemd --user` manager). @@ -59,7 +59,7 @@ Example: == How to enable a service by default -Unit files must correspond to the Fedora Packaging xref:Scriptlets.adoc#_systemd[Guidelines]. Services are enabled or disabled by default through http://www.freedesktop.org/software/systemd/man/systemd.preset.html[systemd preset files]. Preset files can be overridden by a local administrator, but a set of defaults are provided by Fedora. +Unit files must correspond to the Fedora Packaging xref:Scriptlets.adoc#_systemd[Guidelines]. Services are enabled or disabled by default through https://www.freedesktop.org/software/systemd/man/systemd.preset.html[systemd preset files]. Preset files can be overridden by a local administrator, but a set of defaults are provided by Fedora. If the service should be enabled by default, it must be added to one of the distribution presets files (see above). From 1d882eb343c1b6ccf3b4807c06df5efef20f3a15 Mon Sep 17 00:00:00 2001 From: Jason Tibbitts Date: Oct 08 2021 22:40:04 +0000 Subject: [PATCH 6/31] Use https for links in Drupal guidelines --- diff --git a/guidelines/modules/ROOT/pages/Drupal7.adoc b/guidelines/modules/ROOT/pages/Drupal7.adoc index 5233592..0b49205 100644 --- a/guidelines/modules/ROOT/pages/Drupal7.adoc +++ b/guidelines/modules/ROOT/pages/Drupal7.adoc @@ -65,13 +65,13 @@ See xref:PHP.adoc#Other_Packages[PHP packaging guidelines]. See xref:PHP.adoc#Extensions_Requires[PHP packaging guidelines]. -To get a list of required PHP extensions, use http://php5.laurent-laville.org/compatinfo/[PHP_CompatInfo (phpcompatinfo)]: +To get a list of required PHP extensions, use https://php5.laurent-laville.org/compatinfo/[PHP_CompatInfo (phpcompatinfo)]: .... phpcompatinfo print --recursive --report=extension unpacked_package_source_directory .... -To install http://php5.laurent-laville.org/compatinfo/[PHP_CompatInfo (phpcompatinfo)], run "`+yum install php-bartlett-PHP-CompatInfo+`". +To install https://php5.laurent-laville.org/compatinfo/[PHP_CompatInfo (phpcompatinfo)], run "`+yum install php-bartlett-PHP-CompatInfo+`". === Requiring a Minimum PHP Version @@ -130,7 +130,7 @@ After installation, you must enable this module from the Drupal administration page. If upgrading this module separately from the core Drupal package, be sure to -run the http://hostname/drupal7/upgrade.php script after this RPM is upgraded. +run the https://hostname/drupal7/upgrade.php script after this RPM is upgraded. .... === Module @@ -147,8 +147,8 @@ Summary: __SUMMARY__ Group: Applications/Publishing License: GPLv2+ -URL: http://drupal.org/project/%{module} -Source0: http://ftp.drupal.org/files/projects/%{module}-7.x-%{version}.tar.gz +URL: https://drupal.org/project/%{module} +Source0: https://ftp.drupal.org/files/projects/%{module}-7.x-%{version}.tar.gz Source1: %{name}-RPM-README.txt BuildArch: noarch @@ -203,8 +203,8 @@ Summary: __SUMMARY__ Group: Applications/Publishing License: GPLv2+ -URL: http://drupal.org/project/%{theme} -Source0: http://ftp.drupal.org/files/projects/%{theme}-7.x-%{version}.tar.gz +URL: https://drupal.org/project/%{theme} +Source0: https://ftp.drupal.org/files/projects/%{theme}-7.x-%{version}.tar.gz Source1: %{name}-RPM-README.txt BuildArch: noarch From 9cf0c44e8ca0eac353c4dfb35cb871e85777288c Mon Sep 17 00:00:00 2001 From: Jason Tibbitts Date: Oct 08 2021 22:40:04 +0000 Subject: [PATCH 7/31] Use https for links in Eclipse Plugins guidelines --- diff --git a/guidelines/modules/ROOT/pages/EclipsePlugins.adoc b/guidelines/modules/ROOT/pages/EclipsePlugins.adoc index f9b5814..41f3eee 100644 --- a/guidelines/modules/ROOT/pages/EclipsePlugins.adoc +++ b/guidelines/modules/ROOT/pages/EclipsePlugins.adoc @@ -2,14 +2,14 @@ == Glossary -* *Bundle*: An http://en.wikipedia.org/wiki/OSGi#Bundles["OSGi bundle"]. +* *Bundle*: An https://en.wikipedia.org/wiki/OSGi#Bundles["OSGi bundle"]. * *Plugin*: A functional unit of Eclipse functionality. Post-Eclipse 3.0, the term "plugin" can almost always be interchanged with the term "bundle". Colloquially, among non-Eclipse developers, the term is used to refer to a set of functional Eclipse plugins ex. "CDT". * *Feature*: A collection of plugins. * *Fragment*: A bundle with native elements ex. `+org.eclipse.core.filesystem.linux.${arch}+` == Introduction -Eclipse is a modular platform that can be used for building everything from server-side applications to full-blown graphical applications like the Eclipse IDE and Lotus Notes. Each of the modular blobs is referred to as a plugin or a bundle. In a nutshell, the system itself is a small runtime (Equinox) based on the OSGi specifications [see http://www.eclipse.org/equinox/ for more information] which loads and runs a given list of bundles. Most people think of Eclipse as a programming integrated development environment (IDE). This document details best practices for packaging Eclipse IDE plugins. Examples include adding Subversion functionality (`+eclipse-subclipse+`) and tools for tracking your tasks (`+eclipse-mylyn+`). +Eclipse is a modular platform that can be used for building everything from server-side applications to full-blown graphical applications like the Eclipse IDE and Lotus Notes. Each of the modular blobs is referred to as a plugin or a bundle. In a nutshell, the system itself is a small runtime (Equinox) based on the OSGi specifications [see https://www.eclipse.org/equinox/ for more information] which loads and runs a given list of bundles. Most people think of Eclipse as a programming integrated development environment (IDE). This document details best practices for packaging Eclipse IDE plugins. Examples include adding Subversion functionality (`+eclipse-subclipse+`) and tools for tracking your tasks (`+eclipse-mylyn+`). == Naming @@ -107,7 +107,7 @@ Summary: Plugin provides such and such functionality for the Eclipse IDE. Group: Development/Tools License: EPL -URL: http://www.eclipse.org/plugin +URL: https://www.eclipse.org/plugin Source0: org.eclipse.plugin-TAG-fetched-src.tar.bz2 Arch: noarch @@ -203,4 +203,4 @@ However, we end up with the plugin classes themselves being expanded in the `+or === rpmstubby -`+rpmstubby+` is a small project that is part of the http://eclipse.org/linuxtools[linuxdistros project] at eclipse.org. Its aim is to make packaging Eclipse plugins as RPMs extremely simple. Specfiles for packages like `+eclipse-mylyn+` were originally stubbed out using it. Available as eclipse-rpmstubby package. +`+rpmstubby+` is a small project that is part of the https://eclipse.org/linuxtools[linuxdistros project] at eclipse.org. Its aim is to make packaging Eclipse plugins as RPMs extremely simple. Specfiles for packages like `+eclipse-mylyn+` were originally stubbed out using it. Available as eclipse-rpmstubby package. From 74bd4b592446ffdf635f4c6f7710be07caa5c215 Mon Sep 17 00:00:00 2001 From: Jason Tibbitts Date: Oct 08 2021 22:40:04 +0000 Subject: [PATCH 8/31] Use https and fix links in Fonts Policy guidelines --- diff --git a/guidelines/modules/ROOT/pages/FontsPolicy.adoc b/guidelines/modules/ROOT/pages/FontsPolicy.adoc index 4f2d29f..5bd1612 100644 --- a/guidelines/modules/ROOT/pages/FontsPolicy.adoc +++ b/guidelines/modules/ROOT/pages/FontsPolicy.adoc @@ -218,14 +218,14 @@ When packaging such a partial design: === Bitmap console fonts -* [x] Bitmap console fonts MAY be packaged in a legacy font format, understood by http://www.kbd-project.org/[kbd]. +* [x] Bitmap console fonts MAY be packaged in a legacy font format, understood by https://www.kbd-project.org/[kbd]. * [x] Bitmap console fonts MUST be installed in `/lib/kbd/consolefonts/` not `/usr/share/fonts`. * [x] Bitmap console font packages SHOULD be named `__-fonts-console` not `__-fonts`. [NOTE] ==== .Console fonts -As long as http://www.kbd-project.org/[kbd] and https://www.freedesktop.org/software/systemd/man/vconsole.conf.html[systemd-vconsole] can not use the same file formats as the rest of the system, bitmap console fonts are effectively private kbd resources. They will be ignored in the rest of this document. It does not apply to them. +As long as https://www.kbd-project.org/[kbd] and https://www.freedesktop.org/software/systemd/man/vconsole.conf.html[systemd-vconsole] can not use the same file formats as the rest of the system, bitmap console fonts are effectively private kbd resources. They will be ignored in the rest of this document. It does not apply to them. ==== === Assembling same-family font packages @@ -370,7 +370,7 @@ Then it declares elements, that will be shared by all the packaged font families [horizontal] %\{foundry}:: an optional upstream identifier, when upstream publishes multiple font families, with consistent QA rules. Font families released by the same upstream will usually play well with one another. Marking them as such helps users choose good font package sets. -* for example, the http://openfontlibrary.org/[Open Font Library] identifier is `oflb`. +* for example, the https://fontlibrary.org/[Open Font Library] identifier is `oflb`. %\{fontlicense}:: the identifier of the font family license, according to our licensing rules. Those identifiers are followed by variables, containing: @@ -743,7 +743,7 @@ Avoid packaging `+*.ttc+` and `+*.otc+` files unless left no choice by upstream. Legacy formats are too limited to handle Unicode-level coverage, fail to declare their encoding, do not permit the kind of style selection expected in modern fonts, do not provide human-friendly naming layers, etc. They’re full of quirks and a source of (security) bugs in applications. -In 2006, at the first https://www.freedesktop.org/wiki/TextLayout/[Text Layout] summit, all the major Free Desktop players agreed to converge on a unified text layout engine, built around the http://harfbuzz.org/[HarfBuzz] project and the OpenType format. As a result, modern Free Desktop applications and libraries https://bugzilla.redhat.com/show_bug.cgi?id=1753295[no] https://bugs.documentfoundation.org/show_bug.cgi?id=104701[longuer] https://gitlab.gnome.org/GNOME/pango/issues/368[support] other formats. +In 2006, at the first https://www.freedesktop.org/wiki/TextLayout/[Text Layout] summit, all the major Free Desktop players agreed to converge on a unified text layout engine, built around the https://github.com/harfbuzz/harfbuzz[HarfBuzz] project and the OpenType format. As a result, modern Free Desktop applications and libraries https://bugzilla.redhat.com/show_bug.cgi?id=1753295[no] https://bugs.documentfoundation.org/show_bug.cgi?id=104701[longuer] https://gitlab.gnome.org/GNOME/pango/issues/368[support] other formats. Use tools like https://fontforge.github.io/[fontforge] or https://fedoraproject.org/wiki/BitmapFontConversion[fonttosfnt] (provided by xorg-x11-font-utils) to https://gitlab.gnome.org/GNOME/pango/issues/386#note_568255[convert] legacy fonts to an OpenType format. Get it done upstream or script it within the `%build` section of your `spec` file. @@ -767,7 +767,7 @@ Therefore, there’s no risk, and lots of advantages, in converting Postscript f ===== X11 core fonts -Once upon a time every Linux GUI application used the so-called _Core fonts_ server-side X11 backend footnote:[Fonts accessed through the original _core_ X protocol, using tools like _mkfontdir_, _xfs_, _/etc/X11/fontpath.d/_, _XLFD_ strings, etc. See also this http://keithp.com/~keithp/talks/xtc2001/paper/[paper] written shortly before projects massively migrated to client-side fonts.]. It was riddled with problems. The FLOSS developers finally gave up on it, declared it legacy and broken by design, and moved to client-side font handling (fontconfig). Nowadays almost no modern Linux GUI application uses the _Core fonts_ backend. Few (if any) people are willing to fix its remaining bugs. +Once upon a time every Linux GUI application used the so-called _Core fonts_ server-side X11 backend footnote:[Fonts accessed through the original _core_ X protocol, using tools like _mkfontdir_, _xfs_, _/etc/X11/fontpath.d/_, _XLFD_ strings, etc. See also this https://keithp.com/~keithp/talks/xtc2001/paper/[paper] written shortly before projects massively migrated to client-side fonts.]. It was riddled with problems. The FLOSS developers finally gave up on it, declared it legacy and broken by design, and moved to client-side font handling (fontconfig). Nowadays almost no modern Linux GUI application uses the _Core fonts_ backend. Few (if any) people are willing to fix its remaining bugs. Therefore, unless your font has previously been registered in _Core fonts_, and the problems triggered by this font hopefully fixed, you *SHOULD NOT* declare it there. This is especially true of fonts in modern OpenType formats. From 6badcd66efaf1f006dc3ba34f0ebd7086e974b98 Mon Sep 17 00:00:00 2001 From: Jason Tibbitts Date: Oct 08 2021 22:40:04 +0000 Subject: [PATCH 9/31] Use https for links in GAP guidelines --- diff --git a/guidelines/modules/ROOT/pages/GAP.adoc b/guidelines/modules/ROOT/pages/GAP.adoc index f5b426e..cffe51e 100644 --- a/guidelines/modules/ROOT/pages/GAP.adoc +++ b/guidelines/modules/ROOT/pages/GAP.adoc @@ -1,7 +1,7 @@ = GAP Packaging Guidelines :toc: -This document describes the conventions and customs surrounding the proper packaging of http://gap-system.org/[GAP] add-on packages in Fedora. Throughout this document, we use the word _add-on_ to substitute for GAP upstream's use of the word _package_, to avoid confusion with RPM packages. +This document describes the conventions and customs surrounding the proper packaging of https://gap-system.org/[GAP] add-on packages in Fedora. Throughout this document, we use the word _add-on_ to substitute for GAP upstream's use of the word _package_, to avoid confusion with RPM packages. == Naming From e67b03fee0f83b61f546b1a6cac08e70997a7d09 Mon Sep 17 00:00:00 2001 From: Jason Tibbitts Date: Oct 08 2021 22:40:04 +0000 Subject: [PATCH 10/31] Use https for links in Haskell guidelines --- diff --git a/guidelines/modules/ROOT/pages/Haskell.adoc b/guidelines/modules/ROOT/pages/Haskell.adoc index fe6d0f0..588be61 100644 --- a/guidelines/modules/ROOT/pages/Haskell.adoc +++ b/guidelines/modules/ROOT/pages/Haskell.adoc @@ -2,8 +2,8 @@ This page documents the guidelines and conventions for packaging Haskell projects in Fedora. -http://haskell.org/ghc[GHC] (Glasgow Haskell Compiler) is the current mainstream Haskell compiler. -Most Haskell packages are released on http://hackage.haskell.org[Hackage] and use the http://www.haskell.org/cabal/[Cabal] package system. So the current guidelines largely focus on packaging for GHC using Cabal. +https://haskell.org/ghc[GHC] (Glasgow Haskell Compiler) is the current mainstream Haskell compiler. +Most Haskell packages are released on https://hackage.haskell.org[Hackage] and use the https://www.haskell.org/cabal/[Cabal] package system. So the current guidelines largely focus on packaging for GHC using Cabal. == Spec file templates @@ -139,8 +139,8 @@ Release: 1%{?dist} Summary: @SUMMARY@ License: @LICENSE@ -URL: http://hackage.haskell.org/package/%{name} -Source0: http://hackage.haskell.org/package/%{name}-%{version}/%{name}-%{version}.tar.gz +URL: https://hackage.haskell.org/package/%{name} +Source0: https://hackage.haskell.org/package/%{name}-%{version}/%{name}-%{version}.tar.gz BuildRequires: ghc-Cabal-devel BuildRequires: ghc-rpm-macros From d587a5cb93fb88ea17eafd9fa25a08799e47e3ef Mon Sep 17 00:00:00 2001 From: Jason Tibbitts Date: Oct 08 2021 22:40:04 +0000 Subject: [PATCH 11/31] Use https for links in the main guidelines --- diff --git a/guidelines/modules/ROOT/pages/index.adoc b/guidelines/modules/ROOT/pages/index.adoc index ade71da..3e3c544 100644 --- a/guidelines/modules/ROOT/pages/index.adoc +++ b/guidelines/modules/ROOT/pages/index.adoc @@ -520,7 +520,7 @@ The FHS defines where files should be placed on the system. === Libexecdir -The http://www.pathname.com/fhs/[Filesystem Hierarchy Standard] +The https://www.pathname.com/fhs/[Filesystem Hierarchy Standard] does not include any provision for libexecdir, but Fedora packages MAY store appropriate files there. Libexecdir (aka, `+/usr/libexec+` on Fedora systems) @@ -568,7 +568,7 @@ before any services are started === No Files or Directories under /srv, /usr/local, or /home/$USER -The http://www.pathname.com/fhs/pub/fhs-2.3.html#SRVDATAFORSERVICESPROVIDEDBYSYSTEM[FHS says]: +The https://www.pathname.com/fhs/pub/fhs-2.3.html#SRVDATAFORSERVICESPROVIDEDBYSYSTEM[FHS says]: .... "...no program should rely on a specific subdirectory structure of /srv existing @@ -610,7 +610,7 @@ The package simply must not do this out of the box `+/opt+` and its related directories (`+/etc/opt+` and `+/var/opt+`) is reserved for the use of vendors in the FHS. We have reserved the `+fedora+` name with -http://www.lanana.org/lsbreg/providers/providers.txt[LANANA] +https://www.lanana.org/lsbreg/providers/providers.txt[LANANA] for our use. If a package installs files into `+/opt+` it may only use directories in the `+/opt/fedora+` hierarchy. @@ -1902,7 +1902,7 @@ When there are multiple variants that each serve the needs of some user and thus All patches in Fedora spec files *SHOULD* have a comment above them about their upstream status. Any time you create a patch, it is best practice to file it in an upstream bug tracker, and include a link to that in the comment above the patch. For example: .... -# http://bugzilla.gnome.org/show_bug.cgi?id=12345 +# https://bugzilla.gnome.org/show_bug.cgi?id=12345 Patch0: gnome-panel-fix-frobnicator.patch .... @@ -1910,7 +1910,7 @@ The above is perfectly acceptable; but if you prefer, a brief comment about what .... # Don't crash with frobnicator applet -# http://bugzilla.gnome.org/show_bug.cgi?id=12345 +# https://bugzilla.gnome.org/show_bug.cgi?id=12345 Patch0: gnome-panel-fix-frobnicator.patch .... From 6cae7975a1bf42536db636dfd8fc6fcd6ef23f0a Mon Sep 17 00:00:00 2001 From: Jason Tibbitts Date: Oct 08 2021 22:40:04 +0000 Subject: [PATCH 12/31] Use https links in Initial Service Setup guidelines --- diff --git a/guidelines/modules/ROOT/pages/Initial_Service_Setup.adoc b/guidelines/modules/ROOT/pages/Initial_Service_Setup.adoc index 9c29c3c..7872411 100644 --- a/guidelines/modules/ROOT/pages/Initial_Service_Setup.adoc +++ b/guidelines/modules/ROOT/pages/Initial_Service_Setup.adoc @@ -41,7 +41,7 @@ Therefore, instead of creating a self-signed certificate, we will create a tempo == Common Guidelines -For all system-specific cases, we will take advantage of systemd's http://www.freedesktop.org/software/systemd/man/systemd.service.html[service] functionality. Packagers will create a new service unit file for each service unit in their package that requires per-system configuration. This service unit will be named `+-init.service+` and installed to `+/usr/lib/systemd/system+`. For example, the `+tog-pegasus.service+` configuration unit would be `+/usr/lib/systemd/tog-pegasus-init.service+`. +For all system-specific cases, we will take advantage of systemd's https://www.freedesktop.org/software/systemd/man/systemd.service.html[service] functionality. Packagers will create a new service unit file for each service unit in their package that requires per-system configuration. This service unit will be named `+-init.service+` and installed to `+/usr/lib/systemd/system+`. For example, the `+tog-pegasus.service+` configuration unit would be `+/usr/lib/systemd/tog-pegasus-init.service+`. The contents of this service unit will be as follows: @@ -59,7 +59,7 @@ RemainAfterExit=no ExecStart=/path/to/config/script .... -The syntax for `+ConditionPathExists=+` uses the ! to indicate negation (the file is not present). The | is used to create an OR logical pairing (resulting in the lack of ANY of these files causing the configuration to be run). Those are called "triggering" conditions, for full explanation see http://www.freedesktop.org/software/systemd/man/systemd.unit.html#ConditionArchitecture=[systemd.unit(5)]. The `+/path/to/config/script+` can be any executable script or binary that will generate the initial configuration needed by this service. It *must* generate the files tested by `+ConditionPathExists+`. If the script is a single command, it can be run directly by this service unit. If it needs to run multiple commands, it is recommended to create a script file in the package's `+/usr/libexec/+` directory and execute that. +The syntax for `+ConditionPathExists=+` uses the ! to indicate negation (the file is not present). The | is used to create an OR logical pairing (resulting in the lack of ANY of these files causing the configuration to be run). Those are called "triggering" conditions, for full explanation see https://www.freedesktop.org/software/systemd/man/systemd.unit.html#ConditionArchitecture=[systemd.unit(5)]. The `+/path/to/config/script+` can be any executable script or binary that will generate the initial configuration needed by this service. It *must* generate the files tested by `+ConditionPathExists+`. If the script is a single command, it can be run directly by this service unit. If it needs to run multiple commands, it is recommended to create a script file in the package's `+/usr/libexec/+` directory and execute that. To use `+tog-pegasus.service+` as an example: From 0f88b4d785c5da1c6f31575d91e54a5876e2c613 Mon Sep 17 00:00:00 2001 From: Jason Tibbitts Date: Oct 08 2021 22:40:04 +0000 Subject: [PATCH 13/31] Use https links in the Lisp guidelines --- diff --git a/guidelines/modules/ROOT/pages/Lisp.adoc b/guidelines/modules/ROOT/pages/Lisp.adoc index e6d6453..59b10c4 100644 --- a/guidelines/modules/ROOT/pages/Lisp.adoc +++ b/guidelines/modules/ROOT/pages/Lisp.adoc @@ -130,4 +130,4 @@ All implementations should be modified to load common-lisp-controller's %\{_sysc == Further reading -See http://www.cliki.net/common-lisp-controller and http://common-lisp.net/project/asdf/ for more details on common-lisp-controller and asdf. +See https://www.cliki.net/common-lisp-controller and https://common-lisp.net/project/asdf/ for more details on common-lisp-controller and asdf. From cbc29e92f93b8bdef6420434fae9700354a2a74f Mon Sep 17 00:00:00 2001 From: Jason Tibbitts Date: Oct 08 2021 22:40:04 +0000 Subject: [PATCH 14/31] Use https for links in the Meson guidelines --- diff --git a/guidelines/modules/ROOT/pages/Meson.adoc b/guidelines/modules/ROOT/pages/Meson.adoc index 363b4a2..967f04c 100644 --- a/guidelines/modules/ROOT/pages/Meson.adoc +++ b/guidelines/modules/ROOT/pages/Meson.adoc @@ -1,7 +1,7 @@ = Meson Packaging Guidelines :toc: -This document provides best practices for the usage of http://mesonbuild.com/[the Meson build system] in Fedora packages. Meson is a build system (similar to automake) which can generate code for other lower-level build systems. For example, it can generate code for https://ninja-build.org/[ninja]. When packaging software which builds using Meson it's important to use the `+%meson+` macros instead of `+%ninja+` or other lower-level build system macros directly. The backend used by Meson could change. +This document provides best practices for the usage of https://mesonbuild.com/[the Meson build system] in Fedora packages. Meson is a build system (similar to automake) which can generate code for other lower-level build systems. For example, it can generate code for https://ninja-build.org/[ninja]. When packaging software which builds using Meson it's important to use the `+%meson+` macros instead of `+%ninja+` or other lower-level build system macros directly. The backend used by Meson could change. == Build Dependencies @@ -43,7 +43,7 @@ Release: 1%{?dist} Summary: Flexible cross-platform scripting library License: zlib -URL: http://www.angelcode.com/angelscript/ +URL: https://www.angelcode.com/angelscript/ Source: %{url}sdk/files/%{name}_%{version}.zip BuildRequires: meson From 261859176c65d0ea152222a929ace01e7d83f4e3 Mon Sep 17 00:00:00 2001 From: Jason Tibbitts Date: Oct 08 2021 22:40:04 +0000 Subject: [PATCH 15/31] Use https links in the MinGW guidelines --- diff --git a/guidelines/modules/ROOT/pages/MinGW.adoc b/guidelines/modules/ROOT/pages/MinGW.adoc index 63cb798..c43bdcf 100644 --- a/guidelines/modules/ROOT/pages/MinGW.adoc +++ b/guidelines/modules/ROOT/pages/MinGW.adoc @@ -464,8 +464,8 @@ Release: 1%{?dist} Summary: MinGW compiled example library License: LGPLv2+ -URL: http://fedoraproject.org -Source0: http://fedoraproject.org/example-%{version}.tar.bz2 +URL: https://fedoraproject.org +Source0: https://fedoraproject.org/example-%{version}.tar.bz2 BuildArch: noarch From 7484f9e5eed6f4af7410d66bfab0ce03c4c34d83 Mon Sep 17 00:00:00 2001 From: Jason Tibbitts Date: Oct 08 2021 22:40:04 +0000 Subject: [PATCH 16/31] Use https links in the Mono guidelines --- diff --git a/guidelines/modules/ROOT/pages/Mono.adoc b/guidelines/modules/ROOT/pages/Mono.adoc index d99ed59..6bb61e4 100644 --- a/guidelines/modules/ROOT/pages/Mono.adoc +++ b/guidelines/modules/ROOT/pages/Mono.adoc @@ -77,7 +77,7 @@ Because mono .dlls are generally architecture independent, upstream may ship tar === Distributing .DLLs from other projects The Mono project's website makes -http://www.mono-project.com/Assemblies_and_the_GAC#Libraries_with_Unstable_APIs[this suggestion] +https://www.mono-project.com/Assemblies_and_the_GAC#Libraries_with_Unstable_APIs[this suggestion] .... Sometimes developers might want to distribute a library to other developers but they might not have a library that is API stable or has not matured enough over time to guarantee the backwards-compatibility of their libraries or they are not willing to maintain multiple packages of the various versions for users. From b1c3a3e0a147a162425490a2079beefcd59f98c6 Mon Sep 17 00:00:00 2001 From: Jason Tibbitts Date: Oct 08 2021 22:40:04 +0000 Subject: [PATCH 17/31] Use https links in the MPI guidelines --- diff --git a/guidelines/modules/ROOT/pages/MPI.adoc b/guidelines/modules/ROOT/pages/MPI.adoc index 8f1bafe..8f49fc6 100644 --- a/guidelines/modules/ROOT/pages/MPI.adoc +++ b/guidelines/modules/ROOT/pages/MPI.adoc @@ -1,9 +1,9 @@ == Introduction -Message Passing Interface (MPI) is an API for parallelization of programs across multiple nodes and has been around since 1994 http://en.wikipedia.org/wiki/Message_Passing_Interface[1]. MPI can also be used for parallelization on SMP machines and is considered very efficient in it too (close to 100% scaling on parallelizable code as compared to ~80% commonly obtained with threads due to unoptimal memory allocation on NUMA machines). Before MPI, about every manufacturer of supercomputers had their own programming language for writing programs; MPI made porting software easy. +Message Passing Interface (MPI) is an API for parallelization of programs across multiple nodes and has been around since 1994 https://en.wikipedia.org/wiki/Message_Passing_Interface[1]. MPI can also be used for parallelization on SMP machines and is considered very efficient in it too (close to 100% scaling on parallelizable code as compared to ~80% commonly obtained with threads due to unoptimal memory allocation on NUMA machines). Before MPI, about every manufacturer of supercomputers had their own programming language for writing programs; MPI made porting software easy. -There are many MPI implementations available, such as http://www.open-mpi.org/[Open MPI] (the default MPI compiler in Fedora and the MPI compiler used in RHEL), http://www.mpich.org/[MPICH] (in Fedora and RHEL) and -http://mvapich.cse.ohio-state.edu/[MVAPICH1 and MVAPICH2] (in RHEL but not yet in Fedora). +There are many MPI implementations available, such as https://www.open-mpi.org/[Open MPI] (the default MPI compiler in Fedora and the MPI compiler used in RHEL), https://www.mpich.org/[MPICH] (in Fedora and RHEL) and +https://mvapich.cse.ohio-state.edu/[MVAPICH1 and MVAPICH2] (in RHEL but not yet in Fedora). As some MPI libraries work better on some hardware than others, and some software works best with some MPI library, the selection of the library used must be done in user level, on a session specific basis. Also, people doing high performance computing may want to use more efficient compilers than the default one in Fedora (gcc), so one must be able to have many versions of the MPI compiler each compiled with a different compiler installed at the same time. This must be taken into account when writing spec files. From 4851e7c36edfc9fe06cea2c3ce566364b3c24435 Mon Sep 17 00:00:00 2001 From: Jason Tibbitts Date: Oct 08 2021 22:40:04 +0000 Subject: [PATCH 18/31] Use https links in the NodeJS guidelines --- diff --git a/guidelines/modules/ROOT/pages/Node.js.adoc b/guidelines/modules/ROOT/pages/Node.js.adoc index 5d22146..797cc05 100644 --- a/guidelines/modules/ROOT/pages/Node.js.adoc +++ b/guidelines/modules/ROOT/pages/Node.js.adoc @@ -91,10 +91,10 @@ If you have further questions refer to the https://docs.fedoraproject.org/en-US/ == Using tarballs from the npm registry -The canonical method for shipping most node modules is tarballs from the npm registry. The `+Source0+` for such modules should be of the form http://registry.npmjs.org/[]`+/-/-.tgz+`. For instance: +The canonical method for shipping most node modules is tarballs from the npm registry. The `+Source0+` for such modules should be of the form https://registry.npmjs.org/[]`+/-/-.tgz+`. For instance: .... -Source0: http://registry.npmjs.org/npm/-/npm-1.1.70.tgz +Source0: https://registry.npmjs.org/npm/-/npm-1.1.70.tgz .... This method should be preferred to using checkouts from git or automatically generated tarballs from GitHub. @@ -301,7 +301,7 @@ Summary: Tap-producing test harness for Node.js and browsers License: MIT and ICS URL: https://github.com/substack/tape -Source0: http://registry.npmjs.org/%{npm_name}/-/%{npm_name}-%{version}.tgz +Source0: https://registry.npmjs.org/%{npm_name}/-/%{npm_name}-%{version}.tgz Source1: %{npm_name}-%{version}-nm-prod.tgz Source2: %{npm_name}-%{version}-nm-dev.tgz Source3: %{npm_name}-%{version}-bundled-licenses.txt From 56c689b231a687c1b54e5f05ab5600abfde49b5c Mon Sep 17 00:00:00 2001 From: Jason Tibbitts Date: Oct 08 2021 22:40:04 +0000 Subject: [PATCH 19/31] Use https links in OCaml guidelines --- diff --git a/guidelines/modules/ROOT/pages/OCaml.adoc b/guidelines/modules/ROOT/pages/OCaml.adoc index b4a91fb..118be4b 100644 --- a/guidelines/modules/ROOT/pages/OCaml.adoc +++ b/guidelines/modules/ROOT/pages/OCaml.adoc @@ -105,7 +105,7 @@ Binaries should be stripped, as per ordinary Fedora packaging guidelines. There is one exception where a binary should not be stripped. If the package was compiled with ocamlc -custom then the package contains bytecode which strip will remove, thus rendering the binary inoperable. It is easy to test for this: If after stripping, any attempt to run the binary results in the message _No bytecode file specified_ then the binary is compiled like this and should not be stripped. -Rationale: http://bugs.debian.org/256900 +Rationale: https://bugs.debian.org/256900 === Providing best possible binaries @@ -151,7 +151,7 @@ OCaml scripts do not need to be changed (unless resolving the security issue req == Further reading -* http://lists.debian.org/debian-ocaml-maint/2005/01/threads.html#00042 - Thread on ABI compatibility of different versions of OCaml. +* https://lists.debian.org/debian-ocaml-maint/2005/01/threads.html#00042 - Thread on ABI compatibility of different versions of OCaml. * https://www.redhat.com/archives/fedora-devel-list/2007-May/msg01234.html - Explains lack of dynamic linking in upstream. * https://www.redhat.com/archives/fedora-devel-list/2007-May/msg01280.html - Proposal to include MD5 sums in RPM deps. * https://bugzilla.redhat.com/show_bug.cgi?id=433783 - Common rpmlint errors and warnings in OCaml packages. From 922382c4b9dc54288cb1cffaff96851a52fb8b6e Mon Sep 17 00:00:00 2001 From: Jason Tibbitts Date: Oct 08 2021 22:40:04 +0000 Subject: [PATCH 20/31] Use https and correct links in Octave guidelines --- diff --git a/guidelines/modules/ROOT/pages/Octave.adoc b/guidelines/modules/ROOT/pages/Octave.adoc index 86c60bd..5babb98 100644 --- a/guidelines/modules/ROOT/pages/Octave.adoc +++ b/guidelines/modules/ROOT/pages/Octave.adoc @@ -2,13 +2,13 @@ == What is Octave? -The definition from http://www.octave.org/[website] says: +The definition from https://www.octave.org/[website] says: _"GNU Octave is a high-level language, primarily intended for numerical computations. It provides a convenient command line interface for solving linear and nonlinear problems numerically, and for performing other numerical experiments using a language that is mostly compatible with Matlab. It may also be used as a batch-oriented language."_ If you are interested in packaging Octave packages, you should check here for upstream sources: -* http://octave.sourceforge.net/[The Octave Forge website] +* https://octave.sourceforge.io/[The Octave Forge website] == RPM macros @@ -91,8 +91,8 @@ Release: 1%{?dist} Summary: Image processing for Octave Group: Applications/Engineering License: GPLv2+ -URL: http://octave.sourceforge.net/image/ -Source0: http://downloads.sourceforge.net/octave/%{octpkg}-%{version}.tar.gz +URL: https://octave.sourceforge.io/image/ +Source0: https://downloads.sourceforge.net/octave/%{octpkg}-%{version}.tar.gz BuildRequires: octave-devel @@ -152,8 +152,8 @@ Release: 1%{?dist} Summary: Actuarial functions for Octave Group: Applications/Engineering License: GPLv2+ -URL: http://octave.sourceforge.net/ -Source0: http://downloads.sourceforge.net/octave/%{octpkg}-%{version}.tar.gz +URL: https://octave.sourceforge.io +Source0: https://downloads.sourceforge.net/octave/%{octpkg}-%{version}.tar.gz BuildArch: noarch BuildRequires: octave-devel From 050e8353f283a253d8279f1062683603ed24687d Mon Sep 17 00:00:00 2001 From: Jason Tibbitts Date: Oct 08 2021 22:40:04 +0000 Subject: [PATCH 21/31] Use https links in Patch guidelines --- diff --git a/guidelines/modules/ROOT/pages/PatchUpstreamStatus.adoc b/guidelines/modules/ROOT/pages/PatchUpstreamStatus.adoc index fa9fc55..becf594 100644 --- a/guidelines/modules/ROOT/pages/PatchUpstreamStatus.adoc +++ b/guidelines/modules/ROOT/pages/PatchUpstreamStatus.adoc @@ -5,7 +5,7 @@ All patches in Fedora spec files *SHOULD* have a comment above them about their upstream status. Any time you create a patch, it is best practice to file it in an upstream bug tracker, and include a link to that in the comment above the patch. For example: .... -# http://bugzilla.gnome.org/show_bug.cgi?id=12345 +# https://bugzilla.gnome.org/show_bug.cgi?id=12345 Patch0: gnome-panel-fix-frobnicator.patch .... @@ -13,7 +13,7 @@ The above is perfectly acceptable; but if you prefer, a brief comment about what .... # Don't crash with frobnicator applet -# http://bugzilla.gnome.org/show_bug.cgi?id=12345 +# https://bugzilla.gnome.org/show_bug.cgi?id=12345 Patch0: gnome-panel-fix-frobnicator.patch .... From e493204bf21abe111b8c6c85258b2124d1d07b55 Mon Sep 17 00:00:00 2001 From: Jason Tibbitts Date: Oct 08 2021 22:40:04 +0000 Subject: [PATCH 22/31] Use https links in Perl guidelines --- diff --git a/guidelines/modules/ROOT/pages/Perl.adoc b/guidelines/modules/ROOT/pages/Perl.adoc index 8c23834..9c943f0 100644 --- a/guidelines/modules/ROOT/pages/Perl.adoc +++ b/guidelines/modules/ROOT/pages/Perl.adoc @@ -105,7 +105,7 @@ use autouse 'Date::Calc' => qw(Delta_DHMS Decode_Date_EU Decode_Date_US); use autouse 'Date::Manip' => qw(ParseDate Date_Init); .... -Similarly, it possible to miss Provides:, as was the case in http://bugzilla.redhat.com/167797[Bug #167797] , where the `+perl-DBD-Pg+` package failed to Provide: `+perl(DBD::Pg)+` due to the following construct in `+DBD::Pg+` version 1.43: +Similarly, it possible to miss Provides:, as was the case in https://bugzilla.redhat.com/167797[Bug #167797] , where the `+perl-DBD-Pg+` package failed to Provide: `+perl(DBD::Pg)+` due to the following construct in `+DBD::Pg+` version 1.43: .... { package DBD::Pg; From 9dbc1e1afef882e54f44ff6a79490393cba6d83b Mon Sep 17 00:00:00 2001 From: Jason Tibbitts Date: Oct 08 2021 22:40:04 +0000 Subject: [PATCH 23/31] Use https links in Per-Product Configuration guidelines --- diff --git a/guidelines/modules/ROOT/pages/Per-Product_Configuration.adoc b/guidelines/modules/ROOT/pages/Per-Product_Configuration.adoc index 251c0f8..6786ff7 100644 --- a/guidelines/modules/ROOT/pages/Per-Product_Configuration.adoc +++ b/guidelines/modules/ROOT/pages/Per-Product_Configuration.adoc @@ -37,7 +37,7 @@ if [ ! -e %{_sysconfdir}/foo/foo.conf ]; then fi .... -* Then it MUST use the value of the Fedora `+VARIANT_ID+` to symlink or copy one of the divergent config files (or the default) to the final config file location. It will get this value by importing the contents of /etc/os-release as shell values. Known values of this field at the time of this writing are "atomichost", "cloud", "server" and "workstation". For more detail, see http://www.freedesktop.org/software/systemd/man/os-release.html#VARIANT_ID=[the os-release(5) man page]. +* Then it MUST use the value of the Fedora `+VARIANT_ID+` to symlink or copy one of the divergent config files (or the default) to the final config file location. It will get this value by importing the contents of /etc/os-release as shell values. Known values of this field at the time of this writing are "atomichost", "cloud", "server" and "workstation". For more detail, see https://www.freedesktop.org/software/systemd/man/os-release.html#VARIANT_ID=[the os-release(5) man page]. .... . /etc/os-release || : From 2d341a4cc41efe18bf9f03b2fb2d478ee81cd9b4 Mon Sep 17 00:00:00 2001 From: Jason Tibbitts Date: Oct 08 2021 22:40:04 +0000 Subject: [PATCH 24/31] Use https links in PHP guidelines --- diff --git a/guidelines/modules/ROOT/pages/PHP.adoc b/guidelines/modules/ROOT/pages/PHP.adoc index 7fd219a..c8f4ba5 100644 --- a/guidelines/modules/ROOT/pages/PHP.adoc +++ b/guidelines/modules/ROOT/pages/PHP.adoc @@ -8,11 +8,11 @@ Fedora Packaging Guidelines for PHP addon modules There are basically 4 different kinds of PHP modules, which are packaged for Fedora: -* http://pecl.php.net[PECL] (PHP Extension Community Library) modules, +* https://pecl.php.net[PECL] (PHP Extension Community Library) modules, which are PHP modules usually written in C and are dynamically loaded by the PHP interpreter on startup. -* http://pear.php.net[PEAR] (PHP Extension and Application Repository) modules, +* https://pear.php.net[PEAR] (PHP Extension and Application Repository) modules, which are reusable components written in PHP, usually classes, which can be used in your own PHP applications and scripts by using e.g. the `+include()+` directive. From ad40efbfadcdea7836062f4560fe3c3796776c12 Mon Sep 17 00:00:00 2001 From: Jason Tibbitts Date: Oct 08 2021 22:40:04 +0000 Subject: [PATCH 25/31] Use https links in PKCS guidelines --- diff --git a/guidelines/modules/ROOT/pages/Pkcs11Support.adoc b/guidelines/modules/ROOT/pages/Pkcs11Support.adoc index 9fbeff4..687fba8 100644 --- a/guidelines/modules/ROOT/pages/Pkcs11Support.adoc +++ b/guidelines/modules/ROOT/pages/Pkcs11Support.adoc @@ -8,7 +8,7 @@ These guidelines are relevant to maintainers of packages with smart cards driver Any package in Fedora containing a PKCS#11 provider module, intended to be used outside this package, MUST be registered with https://p11-glue.github.io/p11-glue/[p11-kit]. For example, the https://github.com/OpenSC/OpenSC/wiki[OpenSC] module which supports most major hardware smart cards, will automatically drop a config file into the appropriate place and then its module will automatically appear in well-behaved software which is integrated with the platform and uses p11-kit properly. The appropriate place in Fedora can be obtained with `+pkg-config p11-kit-1 --variable p11_module_configs+` or `+%{_datadir}/p11-kit/modules/+`. The dropped file should have the `.module` suffix and should contain something similar to the contents below (which is the opensc example). # This file describes how to load the opensc module - # See: http://p11-glue.freedesktop.org/doc/p11-kit/config.html + # See: https://p11-glue.freedesktop.org/doc/p11-kit/config.html # This is a relative path, which means it will be loaded from # the p11-kit default path which is usually $(libdir)/pkcs11. From 9eaf331da31b90b84ffbf3148d8c51c7f85a4ef9 Mon Sep 17 00:00:00 2001 From: Jason Tibbitts Date: Oct 08 2021 22:40:04 +0000 Subject: [PATCH 26/31] Use https and correct links in Ruby guidelines --- diff --git a/guidelines/modules/ROOT/pages/Ruby.adoc b/guidelines/modules/ROOT/pages/Ruby.adoc index 4cd6bac..02caa74 100644 --- a/guidelines/modules/ROOT/pages/Ruby.adoc +++ b/guidelines/modules/ROOT/pages/Ruby.adoc @@ -411,8 +411,8 @@ Version: 0.3.0 Release: 3%{?dist} Group: Development/Languages License: ASL 2.0 and MIT -URL: http://incubator.apache.org/deltacloud -Source0: http://gems.rubyforge.org/gems/%{name}-%{version}.gem +URL: https://incubator.apache.org/deltacloud +Source0: https://rubygems.org/gems/%{name}-%{version}.gem Requires: rubygem-haml #... Requires(post): chkconfig From 9d1c3ab6f3cd6e4943f6b842e19de7180bef0e5e Mon Sep 17 00:00:00 2001 From: Jason Tibbitts Date: Oct 08 2021 22:40:04 +0000 Subject: [PATCH 27/31] Use https links in SourceURL guidelines --- diff --git a/guidelines/modules/ROOT/pages/SourceURL.adoc b/guidelines/modules/ROOT/pages/SourceURL.adoc index 7cebbb5..c2982bb 100644 --- a/guidelines/modules/ROOT/pages/SourceURL.adoc +++ b/guidelines/modules/ROOT/pages/SourceURL.adoc @@ -7,7 +7,7 @@ The most common case is where upstream distributes source as a tar.gz, tar.bz2 o .... Source0: https://downloads.sourceforge.net/%{name}/%{name}-%{version}.tar.gz -Source0: http://ftp.gnome.org/pub/GNOME/sources/gnome-common/2.12/gnome-common-2.12.0.tar.bz2 +Source0: https://ftp.gnome.org/pub/GNOME/sources/gnome-common/2.12/gnome-common-2.12.0.tar.bz2 .... [NOTE] @@ -79,7 +79,7 @@ In some cases you may want to pull sources from upstream's revision control syst .... # The source for this package was pulled from upstream's vcs. Use the # following commands to generate the tarball: -# svn export -r 250 http://www.example.com/svn/foo/trunk foo-20070221 +# svn export -r 250 https://www.example.com/svn/foo/trunk foo-20070221 # tar -cJvf foo-20070221.tar.xz foo-20070221 Source0: foo-20070221.tar.xz .... @@ -218,7 +218,7 @@ Using %\{version} in the SourceX: makes it easier for you to bump the version of When upstream has URLs for the download that do not end with the tarball name rpm will be unable to parse the tarball out of the source URL. One workaround for many cases is to construct a URL where the tarball is listed in a "URL fragment": .... -Source0: http://example.com/foo/1.0/download.cgi#/%{name}-%{version}.tar.gz +Source0: https://example.com/foo/1.0/download.cgi#/%{name}-%{version}.tar.gz .... rpm will then use %\{name}-%\{version}.tar.gz as the tarball name. If you use `+spectool -g foo.spec+` to download the tarball, it will rename the tarball for you. @@ -228,6 +228,6 @@ Sometimes this does not work because the upstream cgi tries to parse the fragmen .... # Mysql has a mirror redirector for its downloads # You can get this tarball by following a link from: - # http://dev.mysql.com/downloads/mysql/5.1.html + # https://dev.mysql.com/downloads/mysql/5.1.html Source0: mysql-5.1.31.tar.gz .... From ced376f24b727f94582cb3622963afdb9d2ea212 Mon Sep 17 00:00:00 2001 From: Jason Tibbitts Date: Oct 08 2021 22:40:04 +0000 Subject: [PATCH 28/31] Use https links in Systemd guidelines --- diff --git a/guidelines/modules/ROOT/pages/Systemd.adoc b/guidelines/modules/ROOT/pages/Systemd.adoc index 1d75417..09be144 100644 --- a/guidelines/modules/ROOT/pages/Systemd.adoc +++ b/guidelines/modules/ROOT/pages/Systemd.adoc @@ -44,14 +44,14 @@ Every `+.service+` file must begin with a `+[Unit]+` section: .... [Unit] Description=A brief human readable string describing the service (not the .service file!) -Documentation=man:foo.service(8) man:foo.conf(5) http://www.foo.org/docs/ +Documentation=man:foo.service(8) man:foo.conf(5) https://www.foo.org/docs/ .... The `+Description=+` line must not exceed 80 characters, and must describe the service, and not the `+.service+` file. For example, "Apache Web Server" is a good description, but "Starts and Stops the Apache Web Server" is a bad one. ====== Documentation field -Systemd in Fedora 17+ has support for defining documentation in unit files via the `Documentation=` field (it is ignored in older releases, so it is safe to keep one systemd unit file across all branches). System administrators will be looking at the contents of the `Documentation=` field to determine what the service is, how to configure it, and where to locate additional documentation relating to the service. Accordingly, packagers are strongly encouraged to include any available sources in the `Documentation=` field which provide this information. If a man page or info page is present in the package, refer to it using `man:manpage` or `info:infofile` respectively. If the documentation is in plaintext, use `\file://path/to/file`. Lastly, if no local documentation exists in the package, but it exists at a URL, use the URL (with `http://`) in this field. Multiple URIs can be added to the `Documentation=` field, as a space separated list. For details on URI definitions and formatting, please refer to the `uri(7)` manpage (`man uri`). +Systemd in Fedora 17+ has support for defining documentation in unit files via the `Documentation=` field (it is ignored in older releases, so it is safe to keep one systemd unit file across all branches). System administrators will be looking at the contents of the `Documentation=` field to determine what the service is, how to configure it, and where to locate additional documentation relating to the service. Accordingly, packagers are strongly encouraged to include any available sources in the `Documentation=` field which provide this information. If a man page or info page is present in the package, refer to it using `man:manpage` or `info:infofile` respectively. If the documentation is in plaintext, use `\file://path/to/file`. Lastly, if no local documentation exists in the package, but it exists at a URL, use the URL (with `https://`) in this field. Multiple URIs can be added to the `Documentation=` field, as a space separated list. For details on URI definitions and formatting, please refer to the `uri(7)` manpage (`man uri`). ===== [Service] @@ -286,7 +286,7 @@ Note that the creation/removal of the alias symlinks should be done with "system In general, it is also recommended to supply native systemd units for all services that are already bus activatable, so that these services can be controlled and supervised centrally like any other service with tools such as systemctl. A similar logic like the one shown above should apply. -See the D-Bus documentation for more information about bus activation: http://dbus.freedesktop.org/doc/dbus-specification.html#message-bus-starting-services +See the D-Bus documentation for more information about bus activation: https://dbus.freedesktop.org/doc/dbus-specification.html#message-bus-starting-services === Automatic restarting From 11bfa6e6587adf2acc07a335874068617846b0e9 Mon Sep 17 00:00:00 2001 From: Jason Tibbitts Date: Oct 08 2021 22:40:04 +0000 Subject: [PATCH 29/31] Use corect links in Tmpfiles guidelines --- diff --git a/guidelines/modules/ROOT/pages/Tmpfiles.d.adoc b/guidelines/modules/ROOT/pages/Tmpfiles.d.adoc index 6371fde..eff8777 100644 --- a/guidelines/modules/ROOT/pages/Tmpfiles.d.adoc +++ b/guidelines/modules/ROOT/pages/Tmpfiles.d.adoc @@ -30,7 +30,7 @@ An example: d /run/mysqld 0755 mysql mysql - .... -Information on other options is available on the http://0pointer.de/public/systemd-man/tmpfiles.d.html[tmpfiles.d man page] should you need to do something more advanced. +Information on other options is available on the https://www.freedesktop.org/software/systemd/man/tmpfiles.d.html[tmpfiles.d man page] should you need to do something more advanced. == Example spec file From 50891e2027883d26f772c567bebf463282aa25fa Mon Sep 17 00:00:00 2001 From: Jason Tibbitts Date: Oct 08 2021 22:40:04 +0000 Subject: [PATCH 30/31] Use https links in Web Assets guidelines --- diff --git a/guidelines/modules/ROOT/pages/Web_Assets.adoc b/guidelines/modules/ROOT/pages/Web_Assets.adoc index 9cbc421..4fa943e 100644 --- a/guidelines/modules/ROOT/pages/Web_Assets.adoc +++ b/guidelines/modules/ROOT/pages/Web_Assets.adoc @@ -62,7 +62,7 @@ Web Assets must follow the general guidelines for Packaging:Guidelines#CodeVsCon == CSS -Pure CSS frameworks can be included as-is. CSS frameworks that use an alternative language that compiles to CSS, such as http://lesscss.org/[LESS], must compile to CSS as part of the build process. It is not acceptable to include pre-compiled CSS in Fedora packages. +Pure CSS frameworks can be included as-is. CSS frameworks that use an alternative language that compiles to CSS, such as https://lesscss.org/[LESS], must compile to CSS as part of the build process. It is not acceptable to include pre-compiled CSS in Fedora packages. == Flash From 2f1e69e41f5b078ea0540d3330cd8de10ae532f9 Mon Sep 17 00:00:00 2001 From: Jason Tibbitts Date: Oct 08 2021 22:40:04 +0000 Subject: [PATCH 31/31] Use https and fix links in Wordpress plugins guidelines --- diff --git a/guidelines/modules/ROOT/pages/WordPress_plugin_packaging_guidelines.adoc b/guidelines/modules/ROOT/pages/WordPress_plugin_packaging_guidelines.adoc index 2856b8f..b7aa335 100644 --- a/guidelines/modules/ROOT/pages/WordPress_plugin_packaging_guidelines.adoc +++ b/guidelines/modules/ROOT/pages/WordPress_plugin_packaging_guidelines.adoc @@ -1,4 +1,4 @@ -http://wordpress.org/extend/plugins/[WordPress plugins] are packaged for Fedora so that the plugin can be used for both and without requiring both. +https://wordpress.org/plugins/[WordPress plugins] are packaged for Fedora so that the plugin can be used for both and without requiring both. == Requirements for packaging @@ -11,7 +11,7 @@ http://wordpress.org/extend/plugins/[WordPress plugins] are packaged for Fedora === Example -http://wordpress.org/extend/plugins/stats/ +https://wordpress.org/plugins/stats/ .... %global plugin_name stats @@ -35,11 +35,11 @@ Release: 1%{?dist} Summary: %{plugin_human_name} plugin for WordPress Group: Applications/Publishing -# According to http://plugins.trac.wordpress.org/ all plugins are licensed +# According to https://plugins.trac.wordpress.org/ all plugins are licensed # under the GPL unless otherwise stated in the plugin source. License: GPLv3+ -URL: http://wordpress.org/extend/plugins/%{plugin_name}/ -Source0: http://downloads.wordpress.org/plugin/%{plugin_name}.%{version}.zip +URL: https://wordpress.org/plugins/%{plugin_name}/ +Source0: https://downloads.wordpress.org/plugin/%{plugin_name}.%{version}.zip BuildRoot: %(mktemp -ud %{_tmppath}/%{name}-%{version}-%{release}-XXXXXX) Requires: wordpress BuildArch: noarch @@ -54,7 +54,7 @@ wordpress-mu-plugin-%{plugin_name} for WordPress MU. %package -n wordpress-mu-plugin-%{plugin_name} Summary: %{plugin_human_name} plugin for WordPress MU Group: Applications/Publishing -# According to http://plugins.trac.wordpress.org/ all plugins are licensed +# According to https://plugins.trac.wordpress.org/ all plugins are licensed # under the GPL unless otherwise stated in the plugin source. License: GPLv3+ Requires: wordpress-mu