Package Details: steamguard-cli-git 0.8.1.r1.fe0d6e9a-1

Git Clone URL: (read-only, click to copy)
Package Base: steamguard-cli-git
Description: A command line utility to generate Steam 2FA codes and respond to confirmations.
Upstream URL:
Keywords: 2fa auth gaming steam
Licenses: GPL3
Submitter: yangtsesu
Maintainer: yangtsesu (dyc3)
Last Packager: dyc3
Votes: 9
Popularity: 0.26
First Submitted: 2017-08-24 02:57 (UTC)
Last Updated: 2023-06-23 19:45 (UTC)

Dependencies (3)

Required by (0)

Sources (1)

Pinned Comments

yangtsesu commented on 2017-08-24 03:07 (UTC)

Guide for create you own {SteamID}.maFile 1 The default XXX.maFile format can be find at 2.1 For Android use this two files: /data/data/ /data/data/ 2.2 For IOS use 3 Put the {SteamID}.maFile in ~/maFiles.And run steamguard. {SteamID} should replace with you own number steam id.

Latest Comments

1 2 3 Next › Last »

lethedata commented on 2022-10-06 05:10 (UTC)

Rust fails to link (error: linking with 'cc' failed: exit status: 1) when using devtools due to lto being enabled by default. Adding options=(!lto) to PKGBUILD allows it compile.

I came across this issue before with the system76-power package so here is what I found on it:

It seems to be related rusts linker-plugin-lto or LLVM not working correctly with the devtools implementation. devtools probably has a flag enabled that either just breaks things or requires rust to have additional arguments to work properly. Alternatively, makechrootpkg might spawn in such a way that rust's linker is unable to find what is needed to successfully link.

The aurutils issue reference from earlier makes use of makechrootpkg, which is what the Convenience Way of Building in a clean chroot does.

Sources: (Solved) Can't link any Rust program linker-plugin-lto stopped working in Rust 1.45.0 -Clinker-plugin-lto doesn't work without extra manual work Regression on nightly since LLVM 8 upgrade: thread sanitizer doesn't compile anymore

yangtsesu commented on 2022-04-21 13:01 (UTC) The pkgver autobump is now achieved via a dedicated pkgver() function. This allows for better control over the pkgver, and maintainers should favor a pkgver that makes sense. To use pkgver(), you still need to declare the pkgver variable with the most recent value. makepkg will invoke function pkgver(), and update variable pkgver accordingly.

dyc3 commented on 2022-04-20 13:12 (UTC)

@Slips Fantastic! I've opened a discussion on the github repo so we can continue this conversation over there.

Slips commented on 2022-04-20 12:38 (UTC)

@dyc3 I would gladly help with the packaging side of things. I'm not all that familiar with rust, but I've packaged a couple programs.

dyc3 commented on 2022-04-19 22:18 (UTC)

@Slips yup, you'd be correct, and I'm well aware. Unfortunately, I've been having the hardest time setting up CI/CD deploys to the AUR for this. If you think you could help out, please do.

Slips commented on 2022-04-19 22:10 (UTC)

Seems like whoever is maintaining the package is manually updating the pkgver every time. AFAIK you are not supposed to do this.

Slips commented on 2022-04-19 22:07 (UTC)

Git repo seems to be behind listed pkgver?

<deleted-account> commented on 2021-08-29 10:22 (UTC)


<deleted-account> commented on 2021-08-29 10:19 (UTC)

mads256h commented on 2021-08-26 19:23 (UTC)

You should remove the steamguard script and update the .SRCINFO with makepkg --printsrcinfo > .SRCINFO