lucianposton / repoman-ebuild-qa-action

This action runs repoman in an ebuild repository to find QA issues.

Repoman Ebuild QA Action

This action runs repoman in an ebuild repository to find QA issues.

Usage

Create a workflow file in your repository e.g. .github/workflows/repoman.yml. An example workflow file is provided below. For more information, see Creating a workflow file.

Example workflow

name: 'Continuous Integration'
on: [push, pull_request]
jobs:
    repoman:
        runs-on: ubuntu-latest
        steps:
            - uses: actions/checkout@v2
            - uses: lucianposton/repoman-ebuild-qa-action@v1

Input Parameters

The following inputs can be specified in the workflow file using the with keyword syntax.

Input	Description	Usage
repoman_args	Additional arguments to pass after repoman full. Defaults to -dx. Note: This parameter will undergo shell wordsplitting and globbing.	optional
path	Path to cd to before starting repoman. The path is relative to the checked out repository. If unspecified or empty, repoman runs in the root of the repository.	optional
portage_version	The portage version to download containing repoman e.g. 2.3.80. latest is the default value, which uses the latest released version.	optional
profile	The gentoo profile to set before running repoman. The default value is latest, which will result in using the first profile in profiles.desc listed under SYMLINK_LIB=no e.g. default/linux/amd64/17.1.	optional
gentoo_repo	Location to install the gentoo ebuild repository. This could be useful if using an old portage version that expects a different location. Default value is /var/db/repos/gentoo.	optional

repoman-ebuild-qa-action's Issues

The last portage version is used instead of latest

If the last portage version listed in Manifest file is not the latest, then it's still selected to be used.

For example today's portage Manifest says:

DIST portage-2.3.89-bug-718578.patch 1325 BLAKE2B 7a3bc520274617736eac2e3d078e90d151bdb5d8615f6217a499c0f5d4c80813f2c753e7902cf34482df0725ad0b43a38707764c8be14aae9f7ca34f0bd8721f SHA512 6f1c5d7b42beb8078c45cccbad2bd65374b69af92521d9be3beb6784477ca5bcdd75d8e762b239e44e3121e6fe5e3a040c92c9b61521e4a9b1d6bafee10d4c88
DIST portage-2.3.99.tar.bz2 1051210 BLAKE2B dd3f990dbc87e655a767ce01e1ee3f0b1d5226fa818949408e54b81a2f96e50a4215a79af42b00dc795792858c4f86453b238b14baef4f0793c937b5617534b8 SHA512 176842318a4134ce54c5aa6485fef296f5a14edd2a72421c2011973a0f1a6af39bc5398f1e9eb3b8666d5fc307589c5b91ab93c219bdedb2d307357d8ddefbf5
DIST portage-3.0.12.tar.bz2 1049335 BLAKE2B 9f7b17ebfe068559ffbc2bc0799f72901abab8b8b5bb608c8f6afe1f8f7fdaae1026c2a04d9b2256b367711196e32b58c6927ea6fc57146148ed71b295acdcb8 SHA512 6f93f35c06ac765f926f5281e2fac99d52140e8c5d95ee4224796c1ea23ed5f45ed5382acbbfc7aebf9f68a9c585fc1b41b615ef765be2d16577909032de1350
DIST portage-3.0.13.tar.bz2 1049930 BLAKE2B 092e4a25896d613dcfcdaaa1c75f29d19112688328c4078a8ab2b24edcf1e26fff3273da56a79f8b35aada5e11e3cf7f14ef40aca742da0874ea7e907c4778bc SHA512 a9106fce311053523fd026c6c65cb85562bae69ab6ea6b5ae784044ffedbfeb0e3b1c3758ebea9204b11f885da383f9d8ee31d34ad52ac14f059cf97894e3590
DIST portage-3.0.14.tar.bz2 1049983 BLAKE2B 174fe1f14bf1cabbe044724bab5eeada6e4d86be7ffd00db1dfe97568dca450aa44856ef7c241e7ed194f99aecb6f8bcffaf30e428c17e53d4afd4265543b495 SHA512 796f34922abe8dcc0deb687c7b42644bc82fedf8751eeb97ef26355dcd600cd134809abcc71c3bdfc233e1c15511c13cbb06c66b5889f47f2b2f51d5384d5888
DIST portage-3.0.9.tar.bz2 1047839 BLAKE2B 44cf96ac69c1b6d2f95aea8b6e87af5665bfa797ef97d3ae09d4faeefa5b36671f542a5bb8b141b0d914afef96d536a63da4539d27336471621363008d2f73bd SHA512 01ad255a12381fb3b52a8d6c1b04cb377c52b8856973aa296a1086f2d89dd6458244486a0d477e95d4247c3edf7e8e3bb20523263979401443b212085737e618

In this case, 3.0.9 is used with this action (which is the last), instead of 3.0.14 (which is the latest).

If we could sort the file content before the last line is selected, then it would solve this problem. I'll try to send a PR about it shortly.

CI fails with unsatisfiable constraint error

It looks like CI runs fail with an error about:

ERROR: unsatisfiable constraints:
    so:libffi.so.7 (missing):
      required by: shellcheck-0.7.1-r2[so:libffi.so.7]

It seems to be the upstream bug from azohra/shell-linter#16. I'll try to include a fix in my pending PR #2, so it can pass the tests.