Skip to content
Snippets Groups Projects
  1. Feb 01, 2025
  2. Jan 06, 2025
  3. Jan 05, 2025
  4. Jan 03, 2025
  5. Dec 14, 2024
  6. Dec 13, 2024
  7. Dec 08, 2024
  8. Dec 04, 2024
  9. Dec 03, 2024
    • Robin Candau's avatar
      feat(release): Add a warning if nvchecker integration is not set · 23f13147
      Robin Candau authored and Christian Heusel's avatar Christian Heusel committed
      Hints to run `pkgctl version setup --help` to see how to set it up if needed.
      
      Closes #236
      Verified
      23f13147
    • Levente Polyak's avatar
    • Levente Polyak's avatar
      feat(issue): add subcommand to edit an issue · a319b0b8
      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's avatarLevente Polyak <anthraxx@archlinux.org>
      Verified
      a319b0b8
    • Levente Polyak's avatar
      feat(issue): add subcommand to create a new issue · a1e44385
      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's avatarLevente Polyak <anthraxx@archlinux.org>
      Verified
      a1e44385
    • Levente Polyak's avatar
      feat(issue): add subcommand to move issues between projects · dfb65e95
      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's avatarLevente Polyak <anthraxx@archlinux.org>
      Verified
      dfb65e95
    • Levente Polyak's avatar
      feat(issue): add subcommand to reopen issues · 4e7ec8b3
      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's avatarLevente Polyak <anthraxx@archlinux.org>
      Verified
      4e7ec8b3
    • Levente Polyak's avatar
      feat(issue): add subcommand to close issues · 292920ac
      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's avatarLevente Polyak <anthraxx@archlinux.org>
      Verified
      292920ac
    • Levente Polyak's avatar
      feat(issue): add subcommand to comment on issues · dde65399
      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's avatarLevente Polyak <anthraxx@archlinux.org>
      Verified
      dde65399
    • Levente Polyak's avatar
      feat(issue): add subcommand to view issue details and comments · 8803e5a5
      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's avatarLevente Polyak <anthraxx@archlinux.org>
      Verified
      8803e5a5
    • Levente Polyak's avatar
      feat(issue): add subcommand to list group and project issues · 0df36dfa
      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's avatarLevente Polyak <anthraxx@archlinux.org>
      Verified
      0df36dfa
    • Levente Polyak's avatar
  10. Nov 28, 2024
  11. Nov 26, 2024
  12. Nov 23, 2024
  13. Nov 09, 2024
    • Celeste Liu's avatar
      fix(arch-nspawn): add --timezone=off to avoid pollute build environment · 5c0f8d37
      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: default avatarCeleste Liu <CoelacanthusHex@gmail.com>
  14. Sep 29, 2024
    • Christian Heusel's avatar
      fix: disable confirmation when dropping packages · e1401ce4
      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: default avatarChristian Heusel <christian@heusel.eu>
      Verified
      e1401ce4
  15. Sep 25, 2024
  16. Sep 10, 2024
  17. Sep 08, 2024
    • Christian Heusel's avatar
      fix: remove duplicate error message · f1dc2e18
      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: default avatarChristian Heusel <christian@heusel.eu>
      Verified
      f1dc2e18
    • Christian Heusel's avatar
      fix(makechrootpkg): improve btrfs sanity checks · c9d82144
      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: default avatarChristian Heusel <christian@heusel.eu>
      Verified
      c9d82144
  18. Aug 21, 2024
  19. Jun 26, 2024
  20. Jun 19, 2024
  21. Jun 18, 2024
Loading