- Jan 25, 2025
-
-
Levente Polyak authored
This allows more flexibility and chaining by being able to define multiple sources per pkgbase and chain them together to achieve the final result. This may also be helpful to combine multiple from/to patterns into a chain to achieve the final pkgver to compare against. To utilize the combiner source, the `pkgbase` section must be declared as the combiner source. Additionally, individual sections should be added using a quoted table key consisting of the `pkgbase` followed by the stage name, separated by double colons. For example: `["sudo:stage1"]`. Fixes #216 Component: pkgctl version check Signed-off-by:
Levente Polyak <anthraxx@archlinux.org>
-
- Jan 06, 2025
-
-
Christian Heusel authored
-
- Jan 05, 2025
-
-
As it turns out the Gitlab api is not guaranteed to return the x-total-pages header for larger query result which previously resulted in a division by zero for pkgctl search as the utlity function assumed that this value would always be set to a positive integer. Fixes #255 Link: https://gitlab.com/gitlab-org/gitlab/-/issues/436373 Component: gitlab.sh Signed-off-by:
Christian Heusel <christian@heusel.eu>
-
- Jan 03, 2025
-
-
Levente Polyak authored
The nvchecker upstream version checks are expected to work as is on any machines without the need of manual Git user configuration. However, certain user configuration may have a side-effect on version checks. Subsequently we try to avoid this situation by always disabling Git config locations. Component: pkgctl version check Signed-off-by:
Levente Polyak <anthraxx@archlinux.org>
-
- Dec 14, 2024
-
-
Jakub Klinkovský authored
Fixes #260
-
- Dec 13, 2024
-
-
Christian Heusel authored
Fixes #259 Fixes: 0df36dfa ("feat(issue): add subcommand to list group and project issues") Component: pkgctl issue view Signed-off-by:
Christian Heusel <christian@heusel.eu>
-
- Dec 08, 2024
-
-
乾康 周 authored
* Ensures availability when $COLUMNS is not present Signed-off-by:
Zhou Qiankang <wszqkzqk@qq.com>
-
- Dec 04, 2024
-
-
Christian Heusel authored
-
Christian Heusel authored
Signed-off-by:
Christian Heusel <christian@heusel.eu>
-
- Dec 03, 2024
-
-
Levente Polyak authored
-
Levente Polyak authored
The pkgctl issue edit command is used to modify an existing issue in Arch Linux packaging projects. This command allows users to update the issue's title, description, and various attributes, ensuring that the issue information remains accurate and up-to-date. It also provides a streamlined facility for bug wranglers to categorize and prioritize issues efficiently. By default, the command operates within the current directory, but users can specify a different package base if needed. In case of a failed run, the command can automatically recover to ensure that the editing process is completed without losing any data. Component: pkgctl issue edit Signed-off-by:
Levente Polyak <anthraxx@archlinux.org>
-
Levente Polyak authored
The create command is used to create a new issue for an Arch Linux package. This command is suitable for reporting bugs, regressions, feature requests, or any other issues related to a package. It provides a flexible way to document and track new issues within the project's issue tracking system. By default, the command operates within the current directory, but users can specify a different package base if needed. Users can provide a title for the issue directly through the command line. The command allows setting various labels and attributes for the issue, such as confidentiality, priority, scope, severity, and status. In case of a failed run, the command can automatically recover to ensure that the issue creation process is completed without losing any data. Component: pkgctl issue create Signed-off-by:
Levente Polyak <anthraxx@archlinux.org>
-
Levente Polyak authored
The move command allows users to transfer an issue from one project to another within the Arch Linux packaging group. This is useful when an issue is identified to be more relevant or better handled in a different project. By default, the command operates within the current directory, but users can specify a different package base from which to move the issue. Users must specify the issue ID (IID) and the destination package to which the issue should be moved. A comment message explaining the reason for the move can be provided directly through the command line. Component: pkgctl issue move Signed-off-by:
Levente Polyak <anthraxx@archlinux.org>
-
Levente Polyak authored
The reopen command is used to reopen a previously closed issue in Arch Linux packaging projects. This command is useful when an issue needs to be revisited or additional work is required after it was initially closed. By default, the command operates within the current directory, but users can specify a different package base if needed. Users can provide a message directly through the command line to explain the reason for reopening the issue. Component: pkgctl issue reopen Signed-off-by:
Levente Polyak <anthraxx@archlinux.org>
-
Levente Polyak authored
This command is used to close an issue in Arch Linux packaging projects. It finalizes the issue by marking it as resolved and optionally providing a reason for its closure. By default, the command operates within the current directory, but users have the option to specify a different package base. Users can provide a message directly through the command line to explain the reason for closing the issue. Additionally, a specific resolution label can be set to categorize the closure reason, with the default label being "completed." Component: pkgctl issue close Signed-off-by:
Levente Polyak <anthraxx@archlinux.org>
-
Levente Polyak authored
This command allows users to add comments to an issue in Arch Linux packaging projects. This command is useful for providing feedback, updates, or any additional information related to an issue directly within the project's issue tracking system. By default, the command interacts with the current directory, but users can specify a different package base if needed. Component: pkgctl issue comment Signed-off-by:
Levente Polyak <anthraxx@archlinux.org>
-
Levente Polyak authored
This command is designed to display detailed information about a specific issue in Arch Linux packaging projects. It gathers and pretty prints all relevant data about the issue, providing a comprehensive view that includes the issue's description, status as well as labels and creation date. By default, the command operates within the current directory, but users have the option to specify a different package base. Additionally, users can choose to view the issue in a web browser for a more interactive experience. Component: pkgctl issue view Signed-off-by:
Levente Polyak <anthraxx@archlinux.org>
-
Levente Polyak authored
The pkgctl issue list command is used to list issues associated with a specific packaging project or the entire packaging subgroup in Arch Linux. This command facilitates efficient issue management by allowing users to list and filter issues based on various criteria. Results can also be displayed directly in a web browser for easier navigation and review. Component: pkgctl issue list Signed-off-by:
Levente Polyak <anthraxx@archlinux.org>
-
Levente Polyak authored
Signed-off-by:
Levente Polyak <anthraxx@archlinux.org>
- Nov 28, 2024
-
-
Instead of passing the command as one complex string to ssh, we create an SSH master connection and use its control socket in multiple simpler commands. The same socket is passed also to rsync to transfer the srcpkg to the remote and to download the build artifacts. Previously, the srcpkg was passed via stdin to ssh, which prevented `pkgctl build --offload --inspect` from working. This change frees stdin for proper remote ptty allocation. However, it seems that ssh commands with and without the `-t` flag cannot be multiplexed on a single connection, so there are technically two SSH connections active for the offload-build execution.
- Nov 26, 2024
-
-
Levente Polyak authored
Setup a blank config for packages without remote sources. This is helpful so other commands like `pkgctl version check` operate gracefully as well as we have easy way to find packages that miss nvchecker config. This must only be used for cases without an upstream, please reach out to the developer team for guidance regarding upstream sources that are hard to configure. Component: pkgctl version setup Signed-off-by:
Levente Polyak <anthraxx@archlinux.org>
-
- Nov 23, 2024
-
-
This allows for tools and data visualization to interface against pkgctl with a machine readable output. Fixes #237 Component: pkgctl version check Signed-off-by:
Andreas Schleifer <segaja@archlinux.org> Co-authored-by:
Levente Polyak <anthraxx@archlinux.org>
-
- Nov 09, 2024
-
-
Celeste Liu authored
From systemd-nspawn(1), --timezone= Configures how /etc/localtime inside of the container (i.e. local timezone synchronization from host to container) shall be handled. Takes one of "off", "copy", "bind", "symlink", "delete" or "auto". If set to "off" the /etc/localtime file in the container is left as it is included in the image, and neither modified nor bind mounted over. If set to "copy" the /etc/localtime file of the host is copied into the container. Similarly, if "bind" is used, the file is bind mounted from the host into the container. If set to "symlink", a symlink is created pointing from /etc/localtime in the container to the timezone file in the container that matches the timezone setting on the host. If set to "delete", the file in the container is deleted, should it exist. If set to "auto" and the /etc/localtime file of the host is a symlink, then "symlink" mode is used, and "copy" otherwise, except if the image is read-only in which case "bind" is used instead. Defaults to "auto". Added in version 239. After this commit, we need to recreate all build environment to clean up pollution already existed. resolve #250 Signed-off-by:
Celeste Liu <CoelacanthusHex@gmail.com>
-
- Sep 29, 2024
-
-
Christian Heusel authored
Since commit 1d433f60 ("feat(db): confirm list of all packages that will be removed") packages need confirmation by default when being dropped from the db. If we make it to the DB drop phase the package already is pushed to the AUR, so it is safe to remove from the database and not removing it would create a somewhat broken state, so we assume that the package should unconditionally be removed from the db. Component: pkgctl aur drop-from-repo Signed-off-by:
Christian Heusel <christian@heusel.eu>
-
- Sep 25, 2024
-
-
PAT settings are now under `user_settings` instead of `profile` Component: pkgctl auth login
-
- Sep 10, 2024
-
-
Without the "--release" flag the example command fails with ==> ERROR: cannot use --message without --release. Component: pkgctl build
-
- Sep 08, 2024
-
-
Christian Heusel authored
It seems like nvchecker emits two log entries for errors: $ nvchecker --logger json -c .nvchecker.toml {"logger_name": "nvchecker.core", "name": "curl", "event": "token not given but it is required", "level": "error"} {"logger_name": "nvchecker.core", "name": "curl", "error": "token not given but it is required", "event": "no-result", "level": "error"} This leads to a double error message as described in the related issue, which we fix by narrowing the selector to filter for the error entry. Fixes #235 Component: pkgctl version check Signed-off-by:
Christian Heusel <christian@heusel.eu>
-
Christian Heusel authored
If the chroot was created in a way where it resides on a BTRFS file system but "$copydir/root" is not a snapshot an error like the following would be emitted: $ makechrootpkg -r ~/chroot ==> Synchronizing chroot copy [/home/chris/chroot/root] -> [chris]...ERROR: Not a Btrfs subvolume: Invalid argument ==> ERROR: Unable to create subvolume /home/chris/chroot/chris Fix this by adding an additional check, which detects if the folder is actually the root of a BTRFS snapshot before attempting to clone it. Related to archlinux/devtools!259 Signed-off-by:
Christian Heusel <christian@heusel.eu>
-
- Aug 21, 2024
-
-
Loïc Rebmeister authored
-
- Jun 26, 2024
-
-
the '--pkgver' argument is not space-separated but instead specified with an equals sign. Component: pkgctl build
-
Jakub Klinkovský authored
Replace `sdiff` with `diff` (also from `diffutils`) with the following parameters: - `--side-by-side` for the `sdiff`-like output - `--suppress-common-lines` for the `sdiff -s` behavior - `--width="$COLUMNS"` to use the full terminal width (long lines are still truncated but it is definitely better than the default width of 130 chars) - `--color=auto` just because
-
- Jun 19, 2024
-
-
Chih-Hsuan Yen authored
Component: pkgctl repo configure
-
- Jun 18, 2024
-
-
Christian Heusel authored
-