Package Details: systemd-numlockontty 0.1-14

Git Clone URL: https://aur.archlinux.org/systemd-numlockontty.git (read-only, click to copy)
Package Base: systemd-numlockontty
Description: Systemd service + script, automatically activate numpad on ttys
Upstream URL: https://github.com/Ybalrid/systemd-numlockontty
Keywords: numlock service systemd tty
Licenses: GPL
Replaces: numlockontty
Submitter: Ybalrid
Maintainer: Ybalrid
Last Packager: Ybalrid
Votes: 85
Popularity: 0.75
First Submitted: 2013-01-02 23:36 (UTC)
Last Updated: 2022-10-24 11:43 (UTC)

Latest Comments

1 2 3 4 5 6 Next › Last »

laba commented on 2022-11-19 18:29 (UTC)

any solution ?

:: Downloading PKGBUILDs...
 PKGBUILDs up to date
 nothing new to review
fetching devel info...
==> Making package: systemd-numlockontty 0.1-14 (Sat 19 Nov 2022 07:28:50 PM CET)
==> Retrieving sources...
  -> Found numlockontty-0.1.tar.gz
==> Validating source files with md5sums...
    numlockontty-0.1.tar.gz ... FAILED
==> ERROR: One or more files did not pass the validity check!
error: failed to download sources for 'systemd-numlockontty-0.1-14': 
error: packages failed to build: systemd-numlockontty-0.1-14

jvybihal commented on 2022-10-26 07:10 (UTC)

Including $pkgrel in upstream (github tag/release) seems like a bad idea to me. pkgrel is related to package, not the source. Very often, the packager and upstream dev(s) are completely different persons that do not even know about each other.

If you make upstream changes, just bump the version up. And adjust PKGBUILD accordingly.

Or instead of pulling .tar.gz, just use git: source=('git+https://<repo-url>#[commit|tag|branch]=<ref>')

You should be able to use specific commit, tag, etc. in the PKGBUILD.

Hope that clears some things out.

LRitzdorf commented on 2022-10-26 00:24 (UTC) (edited on 2022-10-26 00:25 (UTC) by LRitzdorf)

@Ybalrid I'm very much not a makepkg expert, but that seems like it would solve the issue? However, I've also checked on a few other AUR packages, and most of them don't seem to include the release in their source names, so I'm really not sure what the correct course of action is. There has to be a packagers' mailing list or something that you can ask, right?

In case you'd like to test this out yourself, you can remove and then touch numlockontty-0.1.tar.gz (so that it exists but doesn't have the correct MD5 sum), then try to build the package, or just makepkg --verifysource.

Ybalrid commented on 2022-10-25 15:57 (UTC)

@LRitzdorf

I had no idea people could run into that issue...!

Would it be wise to put the $pkgrel in the name of the tarball ?

LRitzdorf commented on 2022-10-25 14:58 (UTC)

Just a quick note for anyone seeing a "failed downloading sources" error: since the source file's name includes only the package version (and not the release), makepkg might find the source tarball for a previous release, try to use that, and then fail the validity check. The solution, of course, is to remove the old tarball and run makepkg again.

Ybalrid commented on 2022-10-24 11:43 (UTC)

okay, I have confirmed my fix is working on a fresh VM that does boot without display manager, you can type numbers in the login prompt without activating the numlock

pushing update now

jvybihal commented on 2022-10-24 11:29 (UTC)

@Ybalrid thanks. Just fyi, I have noticed it, because my numlock on tty stopped working :D So the script with setleds works fine (at least for me) :)

Ybalrid commented on 2022-10-24 11:22 (UTC)

@jvybihal

whoops, I put the wrong service file in there I guess. Gonna update this an push it later today. Sorry for breaking it

jvybihal commented on 2022-10-24 06:45 (UTC)

@Ybalrid Hi, the .service file included in github repo calls ExecStart=/usr/local/bin/numlock but the script is correctly installed /usr/bin/numlockOnTty. Since you do do patch .service in PKGBUILD, it results in nonworking unit after pkgrel upgrade.

Ybalrid commented on 2022-10-22 21:13 (UTC)

Interestingly, just running setleds +num in a TTY do work...