Package Details: pkgtop 2.0-3

Git Clone URL: (read-only)
Package Base: pkgtop
Description: Interactive package manager & resource monitor (stable version)
Upstream URL:
Keywords: package-manager pacman pkgtop resource-monitor
Licenses: GPL3
Conflicts: pkgtop-git
Provides: pkgtop
Submitter: MagicAndWires
Maintainer: MagicAndWires
Last Packager: MagicAndWires
Votes: 3
Popularity: 1.219573
First Submitted: 2019-08-30 23:21
Last Updated: 2019-09-30 19:56

Dependencies (2)

Required by (0)

Sources (1)

Latest Comments

1 2 Next › Last »

MagicAndWires commented on 2019-09-30 19:52

Right, thanks, I'll fix that.

Bit weird that git isn't mentioned as a (opt) depend for go then though. Seems like the better solution.

BrianAllred commented on 2019-09-30 17:15

It requires git to build because go get uses git internally.

When I run in a clean chroot, for example:

go: missing Git command. See <>
package exec: "git": executable file not found 
in $PATH
go: missing Git command. See <>
package exec: "git": executable file not 
found in $PATH
go: missing Git command. See <>
package exec: "git": executable file not found 
in $PATH
package cannot find package 
"" in any of:
        /usr/lib/go/src/ (from $GOROOT)
(from $GOPATH)
==> ERROR: A failure occurred in build().

MagicAndWires commented on 2019-09-30 16:19

@BrianAllred This package doesn't use git, it just gets the latest release archive from the GitHub page.

BrianAllred commented on 2019-09-30 16:02

git isn't part of base-devel, so it needs to be in the make deps. Fails to build in a clean chroot, otherwise.

MagicAndWires commented on 2019-09-20 23:09

@uffe Thanks for the tip, they must have changed the tag commit

uffe commented on 2019-09-18 09:45

pkgtop 2.0-1 PKGBUILD has checksum mismatch

MagicAndWires commented on 2019-09-11 00:00


Sorry, I got notified about this comment but then sort of forgot about it.

For your git package the pkgver will automatically get updated when running makepkg but you'll still have to update the PKGBUILD (and .SRCINFO) manually for it to show up on the AUR page. You'll have to think about how often you'll want to do this but generally I find updating for new releases and app breaking bugfixes to be a good policy.

If a development package breaks on someone's system it's their responsibility to manually update/reinstall it to make sure the issue hasn't been fixed already.

For this package it's all manual and It'll really only update for new releases, and hotfixes. I basically update as fast as I'm notified through github of new releases and am able to update things.

op_old commented on 2019-09-03 14:51

Is it automatically updating the package version depending on the release tag?

MagicAndWires commented on 2019-09-02 00:29


Odd as I couldn't seem to reproduce it on my machine yesterday, though admittedly I didn't try it in a clean chroot though, as I didn't have time for that.

Should be fixed now.

BrianAllred commented on 2019-09-01 19:20


Yeah, it's still broken, and manually setting the variable still works.