Drop unsupported OS versions

.github/workflows/lint.yml

@@ -0,0 +1,20 @@
+name: "Lint"
+on:
+  pull_request:
+  push:
+    branches:
+      - "stable/**"
+      - "qa/**"
+jobs:
+  pre-commit:
+    name: "pre-commit"
+    runs-on: "ubuntu-latest"
+    steps:
+    - name: "Check out repository"
+      uses: "actions/checkout@v4"
+    - name: "Set up Python"
+      uses: "actions/setup-python@v5"
+      with:
+        python-version: "3.x"
+    - name: "Run pre-commit"
+      uses: "pre-commit/[email protected]"

.github/workflows/vagrant-box-archivematica.yml

@@ -8,7 +8,7 @@ on:
       description:
         description: Description
         required: true
-jobs: 
+jobs:
   vagrant-box-archivematica:
     name: Build and upload
     runs-on: macos-latest

.github/workflows/vagrant-box-atom.yml

@@ -8,7 +8,7 @@ on:
       description:
         description: Description
         required: true
-jobs: 
+jobs:
   vagrant-box-atom:
     name: Build and upload
     runs-on: macos-10.15

.markdownlint.jsonc

@@ -0,0 +1,10 @@
+{
+  "default": true,
+  "MD010": {
+    "code_blocks": false
+  },
+  "MD013": {
+    "code_blocks": false,
+    "tables": false
+  }
+}

.pre-commit-config.yaml

@@ -0,0 +1,12 @@
+repos:
+- repo: https://github.com/pre-commit/pre-commit-hooks
+  rev: v4.5.0
+  hooks:
+  - id: check-json
+  - id: check-yaml
+  - id: end-of-file-fixer
+  - id: trailing-whitespace
+- repo: https://github.com/igorshubovych/markdownlint-cli
+  rev: v0.38.0
+  hooks:
+  - id: markdownlint

LICENSE

@@ -337,4 +337,3 @@ proprietary programs.  If your program is a subroutine library, you may
 consider it more useful to permit linking proprietary applications with the
 library.  If this is what you want to do, use the GNU Lesser General
 Public License instead of this License.
-

README.md

@@ -1,20 +1,18 @@
-### Build packages
+# Build packages
 
 You need Docker installed and running.
 
-CentOS 7 packages:
+Rocky Linux 9 packages:
 
-    make -C rpm-EL7
+    make -C rpms/EL9
 
-This also builds a local repository that you can use later from `rpm-EL7-testing`.
+This also builds a local repository that you can use later from `rpms/EL9-testing`.
 
-We don't have a single target yet for Debian packages but you can build them
-individually, for example:
+Ubuntu 22.04 Jammy packages:
 
-    make -C debs/bionic/archivematica
-    make -C debs/bionic/archivematica-storage-service
+    make -C debs/jammy
 
-#### Using parameters
+## Using parameters
 
 Most makefiles support parameters in the form of environment variables. They
 may be a bit different between packages, but the most common are `BRANCH`,
@@ -23,41 +21,41 @@ may be a bit different between packages, but the most common are `BRANCH`,
 So in order to build a specific branch or version, this command can be used from
 the folder of the package we want to build:
 
-    make BRANCH=qa/1.x VERSION=1.7.0 RELEASE=rc5
+    make BRANCH=qa/1.x VERSION=1.15.0 RELEASE=rc5
 
 Keep in mind that the makefiles are a bit recursive, they will invoke Docker,
 mount the current folder, and run the deb-build target.
 
-#### Development
+## Development
 
 Some makefiles have a `dev` target, that give you a shell inside of the Docker
 container used to build packages. When you are inside the container, the command
 needed to build the packages is:
 
     make deb-build
 
-### Repositories management
+## Repositories management
 
 This repo generates Archivematica packages, but also packages that need to be
 installed in order for Archivematica to run. They are placed in the
-ubuntu-extras or centos-extras repos.
+ubuntu-externals, rocky8-extras or rocky9-extras repos.
 
 In order to add a package to a repo, once it's built and uploaded to a temporary
-folder at https://packages.archivematica.org, the steps are:
+folder at <https://packages.archivematica.org>, the steps are:
 
-For CentOS/RedHat packages:
+For Rocky Linux/RedHat packages:
 
-  - Copy the rpm into centos-extras repo
-  - Run `createrepo`
-  - Run `gpg --detach-sign --armor repodata/repomd.xml` to sign the
+- Copy the rpm into rocky8-extras or rocky9-extras repo
+- Run `createrepo`
+- Run `gpg --detach-sign --armor repodata/repomd.xml` to sign the
 repository contents
 
 For Ubuntu packages:
 
-  - Upload the package to packages.archivematica.org
-  - Go to the repository folder
+- Upload the package to packages.archivematica.org
+- Go to the repository folder
 ( mnt/st-sites-pub/packages.archivematica.org/1.7.x/ubuntu-externals )
-  - Add the packages with
+- Add the packages with
 
         reprepro includedeb trusty /path/to/packages/*.deb
         reprepro includedsc trusty /path/to/packages/*.deb
@@ -66,10 +64,10 @@ This needs to be repeated for each Ubuntu release and package. More info about
 managing Ubuntu repositories using reprepro can be found
 [here](https://wiki.archivematica.org/Release_Process#Build_deb.2Frpm_packages).
 
+## Test package
 
-### Test package
+Rocky Linux 9 packages: see the [rpms/EL9-testing](rpms/EL9-testing) directory
+for more details.
 
-CentOS 7 packages: see the [./rpm-EL7-testing](rpm-EL7-testing) directory for more
-details.
-
-Ubuntu packages: this is work in progress (see #127).
+Ubuntu 22.04 Jammy packages: see the [debs/jammy-testing](debs/jammy-testing)
+directory for more details.