Package Details: circleci-cli-bin 0.1.23241-1

Git Clone URL: https://aur.archlinux.org/circleci-cli-bin.git (read-only, click to copy)
Package Base: circleci-cli-bin
Description: CircleCI's new command-line application.
Upstream URL: https://github.com/CircleCI-Public/circleci-cli
Licenses: MIT
Conflicts: circleci-cli
Provides: circleci-cli
Submitter: stefanc_diff
Maintainer: igemnace
Last Packager: igemnace
Votes: 12
Popularity: 0.000064
First Submitted: 2018-12-13 08:05 (UTC)
Last Updated: 2023-01-25 03:10 (UTC)

Dependencies (0)

Required by (0)

Sources (2)

Pinned Comments

igemnace commented on 2021-07-06 01:00 (UTC) (edited on 2021-07-06 01:02 (UTC) by igemnace)

Indeed, here is an issue link for anyone else viewing this thread:

https://github.com/CircleCI-Public/circleci-cli/issues/589

I haven't run the CLI in a long time outside of routinary version checks, since I have no current use for the CLI and am maintaining the PKGBUILD out of habit.

If anyone discovers that this is due to some defect in the PKGBUILD, I'd be happy to merge a patch (or perhaps @stefanc_diff might allow for yet another co-maintainer).

From the looks of that issue, it seems like it might be requiring a kernel compiled with certain parameters (see https://github.com/CircleCI-Public/circleci-cli/issues/589#issuecomment-862544538). If so, hopefully we can express this simply as a dependency on some linux package. Otherwise, if this proves too brittle (e.g. no such linux package maintained both in the repos and in the AUR), we might have to make do with post-installation instructions, both in the PKGBUILD and in a pinned comment here in the AUR.

This comment suggests it must be resolved in circleci-cli itself, however (see https://github.com/CircleCI-Public/circleci-cli/issues/589#issuecomment-872387555). If so, hopefully this will be resolved upstream with a simple version bump.

Latest Comments

1 2 3 Next › Last »

igemnace commented on 2021-11-23 23:33 (UTC)

Thanks @stefanc_diff. To anyone else following the thread with a solution to the linked cgroup issue: the offer to merge a patch or add as co-maintainer still stands.

stefanc_diff commented on 2021-11-19 12:34 (UTC)

Apparently there is a way to transfer a pkg to a co-maintainer - the current maintainer clicks the "Disown Package" button at which point the co-maintainer becomes the sole maintainer - https://bbs.archlinux.org/viewtopic.php?id=270656 Igemnace now you are the sole maintainer

igemnace commented on 2021-11-09 08:33 (UTC)

@stefanc_diff I notice that I do not have access to Manage Co-Maintainers for this package. I'm OK with the plan to transfer the package to me. I manually update the PKGBUILD when an update is out (I monitor via RSS).

Automation would be my next to-do when I have a spare moment, but as of yet I don't have a resolution for the cgroup v2 dependency issue I linked (https://github.com/CircleCI-Public/circleci-cli/issues/589). I'm holding out for a resolution upstream.

stefanc_diff commented on 2021-11-04 11:35 (UTC)

igemnace can you not add a new maintainer ? Unfortunately due to life situation I don't have time to maintain this package. If you cannot add a new maintainer we should transfer the package to you since I will be late at responding and taking action in general.

igemnace commented on 2021-07-06 01:00 (UTC) (edited on 2021-07-06 01:02 (UTC) by igemnace)

Indeed, here is an issue link for anyone else viewing this thread:

https://github.com/CircleCI-Public/circleci-cli/issues/589

I haven't run the CLI in a long time outside of routinary version checks, since I have no current use for the CLI and am maintaining the PKGBUILD out of habit.

If anyone discovers that this is due to some defect in the PKGBUILD, I'd be happy to merge a patch (or perhaps @stefanc_diff might allow for yet another co-maintainer).

From the looks of that issue, it seems like it might be requiring a kernel compiled with certain parameters (see https://github.com/CircleCI-Public/circleci-cli/issues/589#issuecomment-862544538). If so, hopefully we can express this simply as a dependency on some linux package. Otherwise, if this proves too brittle (e.g. no such linux package maintained both in the repos and in the AUR), we might have to make do with post-installation instructions, both in the PKGBUILD and in a pinned comment here in the AUR.

This comment suggests it must be resolved in circleci-cli itself, however (see https://github.com/CircleCI-Public/circleci-cli/issues/589#issuecomment-872387555). If so, hopefully this will be resolved upstream with a simple version bump.

danh337 commented on 2021-06-10 04:53 (UTC)

Hi Folks. Any idea what to do about this? I asked the goog and it doesn't find a good answer, just a couple open issues with no comments.

$ circleci local execute --job run_rspec
Docker image digest: sha256:db51bc24bcea8a750771eb07d9bbdf16f883fd3bf78841d93d060a46e901faf9
====>> Spin up environment
Build-agent version  ()
System information:
 Server Version: 20.10.7
 Storage Driver: overlay2
  Backing Filesystem: extfs
 Cgroup Driver: systemd
 Cgroup Version: 2
 Kernel Version: 5.12.9-arch1-1
 Operating System: Arch Linux
 OSType: linux
 Architecture: x86_64

Error: 
Unexpected environment preparation error: error looking up cgroup: not implemented for cgroup v2 unified hierarchy

Step failed
Task failed
Error: Unhandled prepare executor error: error looking up cgroup: not implemented for cgroup v2 unified hierarchy

arichiardi commented on 2020-10-19 19:22 (UTC)

I updated this locally, here is a patch:

From 65c000831667d600c0bbac3da0749f16b5bbdccb Mon Sep 17 00:00:00 2001
From: Andrea Richiardi <a.richiardi.work@gmail.com>
Date: Mon, 19 Oct 2020 11:31:42 -0700
Subject: [PATCH] [security] Bump version to 0.1.11062

Signed-off-by: Andrea Richiardi <a.richiardi.work@gmail.com>
---
 PKGBUILD | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/PKGBUILD b/PKGBUILD
index 8e8a082..365a8a3 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -8,7 +8,7 @@ _pkgauthor=CircleCI-Public
 _upstream_pkgname=circleci-cli
 _upstream_elfname=circleci
 pkgname=circleci-cli-bin
-pkgver=0.1.10993
+pkgver=0.1.11062
 pkgrel=1
 pkgdesc="CircleCI's new command-line application."
 arch=('x86_64')
@@ -22,7 +22,7 @@ license=("MIT")
 source=("${_upstream_pkgname}-${pkgver}.tar.gz::https://github.com/${_pkgauthor}/${_upstream_pkgname}/releases/download/v${pkgver}/${_upstream_pkgname}_${pkgver}_${_goos}_${_goarch}.tar.gz"
   "LICENSE::https://raw.githubusercontent.com/${_pkgauthor}/${_upstream_pkgname}/master/LICENSE")
 sha256sums=(
-  "32c70c30b17e578ee5ad91bf90c57f65b01ede4c8d1317541313feeeffacf85d"
+  "5405c760aa77b567ff7d106ec110baca7c04a846179baa0290f8545d40846715"
   "89f336660e1dea7ea005892dc44696fb15544cbffedfbddcd4f6671a735763a9"
 )

-- 
2.28.0

igemnace commented on 2019-05-03 12:25 (UTC)

@stefanc_diff Got it, thanks!

stefanc_diff commented on 2019-05-03 10:04 (UTC)

@igemnace didn't know I have to add you through the "Manage Co-Maintainers" button, I though adding you as a maintainer in the PKGBUILD, in git would suffice. I've now added your user by using the "Manage Co-Maintainers" button

igemnace commented on 2019-05-03 04:59 (UTC)

@stefanc_diff Thanks! Although I don't seem to have maintainer status yet, last I checked. I believe you have to add me as a co-maintainer through the "Manage Co-Maintainers" interface on this package.