Is there "depth" control for pkgctl-repo-clone like "asp export" to get only the latest commit?
All, Reading about the changes on archlinux.org and asp will stop working with svn2git going away. pkgctl-repo-clone is the replamement. It has only 3 options: -m, --maintainer NAME --universe -h, --help Does pkgctl-repo-clone simply fetch the latest commit, or does it fetch the history as well? 'asp export' provided only the latest commit without the prior versions history, etc. Can pkgctl-repo-clone do that? https://man.archlinux.org/man/pkgctl-repo-clone.1.en (4/23/2023) is silent on that aspect. https://gitlab.archlinux.org/archlinux/devtools/-/blob/master/src/lib/repo.s... for pkgctl-repo is also silent on whether clone is the latest commit or full-clone with full git history, e.g. COMMANDS clone Clone a package repository https://gitlab.archlinux.org/archlinux/devtools/-/blob/master/src/lib/repo/c... is just the 3 options we started with. I would think it would work like 'asp export' but I'd like to confirm with those that know better than I. -- David C. Rankin, J.D.,P.E.
On 21/05/2023 00:21, David C. Rankin wrote:
Does pkgctl-repo-clone simply fetch the latest commit, or does it fetch the history as well? It fetches the history of the repository aswell, as it fully clones the archive[0]. 'asp export' provided only the latest commit without the prior versions history, etc. Can pkgctl-repo-clone do that? So far it cannot I think, but as the tool is still very young, its not complete in quite some areas. Feel free to open a feature request for something like a --depth option for pkgctl repo clone on the repo[1].
If you only want part of the history you can use git directly, as I very recently documented it on the wiki[2]. It seems if you combine the commands from the article with the --depth 1 option from git[3] it should only fetch the latest revision. cheers, gromit [0] https://gitlab.archlinux.org/archlinux/devtools/-/blob/master/src/lib/repo/c... [1] https://gitlab.archlinux.org/archlinux/devtools/-/issues/new [2] https://wiki.archlinux.org/title/Arch_Build_System#Using_git_directly [3] https://stackoverflow.com/questions/1209999/how-to-use-git-to-get-just-the-l...
On 5/20/23 17:37, Christian Heusel wrote:
'asp export' provided only the latest commit without the prior versions history, etc. Can pkgctl-repo-clone do that? So far it cannot I think, but as the tool is still very young, its not complete in quite some areas. Feel free to open a feature request for something like a --depth option for pkgctl repo clone on the repo[1].
I'll be happy to. Yes, that would be a very useful addition. When grabbing to build locally (for whatever reason), there is no need for the entire git history, and depending on the package size it can be a huge amount of unneeded information
If you only want part of the history you can use git directly, as I very recently documented it on the wiki[2].
Great. I've got no issue using git, but was concerned that we may not have access on gitlab as there is no way for normal user accounts on the arch part. So long as it's a normal read-only clone, that works as a work-around while pkgctl-repo-clone matures.
It seems if you combine the commands from the article with the --depth 1 option from git[3] it should only fetch the latest revision.
That's exactly what is wanted. Simply taking `--depth X` from the command line for pkgctl-repo-clone and passing that as part of the git command for the underlying package seems like a great approach. Thanks for the reply. -- David C. Rankin, J.D.,P.E.
On 23/05/20 11:57PM, David C. Rankin wrote:
If you only want part of the history you can use git directly, as I very recently documented it on the wiki[2].
Great. I've got no issue using git, but was concerned that we may not have access on gitlab as there is no way for normal user accounts on the arch part. So long as it's a normal read-only clone, that works as a work-around while pkgctl-repo-clone matures.
The Gitlab is open to registration by everyone over the archlinux keycloak instance. This was not possible in the older days (so I'm told), but is now since quite some time. cheers, gromit
On 5/21/23 08:42, Christian Heusel wrote:
The Gitlab is open to registration by everyone over the archlinux keycloak instance. This was not possible in the older days (so I'm told), but is now since quite some time.
Total crap "Mobile Authenticator", provide install an app and we will give you 2-factor authentication. It won't even let me sign on with SSO Arch though Aur, the list or GitHub. What BS is that? I'm pushing 60, I don't use apps, a damn phone is that thing wired to the wall. Why and then hell can't Arch do normal authentication on gitlab? Good Lord.. What ID.10.T decided to require 2-factor Arch gitlab auth? -- David C. Rankin, J.D.,P.E.
On Thursday, 25 May 2023 at 00:36 (-0500), David C. Rankin wrote:
Total crap "Mobile Authenticator", provide install an app and we will give you 2-factor authentication. It won't even let me sign on with SSO Arch though Aur, the list or GitHub.
What BS is that? I'm pushing 60, I don't use apps, a damn phone is that thing wired to the wall.
You don't need a smartphone app to generate time-synchronized one-time passwords (OTP), see [1] or [2] or probably others... Jaron [1]: https://wiki.archlinux.org/title/Google_Authenticator#Code_generation [2]: https://archlinux.org/packages/extra/any/pass-otp/
On Thu, May 25, 2023 at 12:36:40AM -0500, David C. Rankin wrote:
Why and then hell can't Arch do normal authentication on gitlab? Good Lord.. What ID.10.T decided to require 2-factor Arch gitlab auth?
David, this is uncalled for. Kindly read the Code of Conduct. -- Morten Linderud PGP: 9C02FF419FECBE16
Hey, 2fa is being widely introduced due to the inherit problem with human beings and passwords. We either do not think of a secure enough password, or we use the same password or everything. Password managers are a huge help, however it is never bad of having a second layer of security. OTP (one time passwords) are extremely difficult to break unless the device storing the otp record is compromised. As Jaron has pointed out, you do not need a smartphone to use otp, although it is adviced to use a separate device for higher security. Unfortunately, age can't be used as an excuse, and you will simply be left behind within technology if you refuse to use new technology people will leave you behind, its the unfortunate truth. Good luck, -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian@polarian.dev
participants (5)
-
Christian Heusel
-
David C. Rankin
-
Jaron Kent-Dobias
-
Morten Linderud
-
Polarian