Package Details: krusader-git

Git Clone URL: (read-only, click to copy)
Package Base: krusader-git
Description: Advanced twin panel file manager for KDE. (GIT version)
Upstream URL:
Licenses: GPL
Conflicts: krusader
Provides: krusader
Submitter: CtHx
Maintainer: sir_lucjan
Last Packager: sir_lucjan
Votes: 40
Popularity: 0.000010
First Submitted: 2011-01-10 00:11 (UTC)
Last Updated: 2020-06-13 21:06 (UTC)

Dependencies (22)

Required by (0)

Sources (1)

Latest Comments

1 2 3 4 Next › Last »

sir_lucjan commented on 2021-11-19 22:27 (UTC)

I know for a fact that this has nothing to do with PKGBUILD - no one has ever reported such an error to me - and I've been managing this package for almost five years.

livem commented on 2021-11-19 22:21 (UTC)

Sir, this is the first time I saw that behavior from pamac for the plast 3 months at least:

~/Desktop ❯ cat /var/log/pacman.log | grep krusader | grep -iE "installed|graded|moved"
[2021-08-17T16:36:59+0300] [ALPM] installed krusader-git (
[2021-08-18T17:30:22+0300] [ALPM] upgraded krusader-git ( ->
[2021-08-20T09:19:18+0300] [ALPM] upgraded krusader-git ( ->
[2021-08-23T13:17:05+0300] [ALPM] upgraded krusader-git ( ->
[2021-08-25T17:40:32+0300] [ALPM] upgraded krusader-git ( ->
[2021-08-26T07:22:35+0300] [ALPM] upgraded krusader-git ( ->
[2021-08-26T11:59:26+0300] [ALPM] upgraded krusader-git ( ->
[2021-09-20T08:58:04+0300] [ALPM] upgraded krusader-git ( ->
[2021-09-21T10:22:55+0300] [ALPM] upgraded krusader-git ( ->
[2021-10-17T23:17:08+0300] [ALPM] upgraded krusader-git ( ->
[2021-11-03T08:14:20+0300] [ALPM] reinstalled krusader-git (
[2021-11-15T00:22:59+0300] [ALPM] reinstalled krusader-git (
[2021-11-17T12:26:10+0300] [ALPM] reinstalled krusader-git (
[2021-11-17T16:27:58+0300] [ALPM] removed krusader-git (
[2021-11-17T16:27:58+0300] [ALPM] installed krusader (2.7.2-4)
[2021-11-17T16:29:01+0300] [ALPM] removed krusader (2.7.2-4)
[2021-11-17T16:29:24+0300] [ALPM] installed krusader (2.7.2-4)
[2021-11-17T23:21:03+0300] [ALPM] removed krusader (2.7.2-4)
[2021-11-18T00:27:20+0300] [ALPM] installed krusader-git (
[2021-11-19T19:29:49+0300] [ALPM] reinstalled krusader-git (
~/Desktop ❯ 

, it is very hard to believe that it is pamac-related issue, it did not got updates 2 weeks,

~/Desktop ❯ cat /var/log/pacman.log | grep pamac | grep -iE "installed|graded|moved" | tail -n 15
[2021-11-07T12:27:25+0300] [ALPM] upgraded libpamac (11.1.3-1 -> 11.2.0-1)
[2021-11-07T12:27:25+0300] [ALPM] upgraded pamac-cli (10.2.2-6 -> 10.3.0-1)
[2021-11-07T12:27:25+0300] [ALPM] upgraded pamac-gtk (10.2.2-6 -> 10.3.0-1)
[2021-11-17T10:58:14+0300] [ALPM] reinstalled libpamac (11.2.0-1)
[2021-11-17T10:58:27+0300] [ALPM] reinstalled pamac-cli (10.3.0-1)
[2021-11-17T10:58:28+0300] [ALPM] reinstalled pamac-gtk (10.3.0-1)
[2021-11-17T10:58:42+0300] [ALPM] reinstalled pamac-tray-icon-plasma (0.1.2-4)
[2021-11-17T11:53:05+0300] [ALPM] reinstalled libpamac (11.2.0-1)
[2021-11-17T11:53:18+0300] [ALPM] reinstalled pamac-cli (10.3.0-1)
[2021-11-17T11:53:19+0300] [ALPM] reinstalled pamac-gtk (10.3.0-1)
[2021-11-17T11:53:33+0300] [ALPM] reinstalled pamac-tray-icon-plasma (0.1.2-4)
[2021-11-17T12:06:21+0300] [ALPM] reinstalled libpamac (11.2.0-1)
[2021-11-17T12:06:34+0300] [ALPM] reinstalled pamac-cli (10.3.0-1)
[2021-11-17T12:06:35+0300] [ALPM] reinstalled pamac-gtk (10.3.0-1)
[2021-11-17T12:06:49+0300] [ALPM] reinstalled pamac-tray-icon-plasma (0.1.2-4)
~/Desktop ❯     

but has settings to check for updates daily.

I used yay -S krusader-git to the same version (your saw it on logs on [2021-11-19T19:29:49+0300])

Now pamac keep silence about Krusader's updates. I do not understood what is going on. Currently I have no issues with "fake" update notifications.

Thank you! Sorry for disturbing.

sir_lucjan commented on 2021-11-19 21:20 (UTC)

Pamac wants to update the file because it finds an older version in AUR than you have built - it does not search locally on disk but treats AUR as a separate repository. To avoid this, I would have to throw every new commit into AUR which is completely pointless. Unfortunately, this is how aur-helpers like pamac work. There's nothing I can do about it - there's nothing in PKGBUILD that can prevent this. This is purely a matter of aur-helpers like pamac.

livem commented on 2021-11-19 21:05 (UTC) (edited on 2021-11-19 21:05 (UTC) by livem)

~/Desktop ❯ pamac build $(pamac list -m -q)
Cloning vscodium-bin build files...
Generating vscodium-bin information...
Checking vscodium-bin dependencies...
Checking krusader-git dependencies...
Checking fswatch dependencies...
Warning: vscodium-bin-1.62.3-1 is up to date -- reinstalling
Warning: downgrading package krusader-git ( =>
Warning: fswatch-1.16.0-1 is up to date -- reinstalling
Resolving dependencies...
Checking inter-conflicts...

To build (3):
  vscodium-bin  1.62.3-1                                                    AUR
  krusader-git  (  AUR
  fswatch       1.16.0-1                                                    AUR

Edit build files : [e] 
Apply transaction ? [e/y/N] 

Transaction cancelled.

This is how git packages work in AUR.

OK, let's forget the r6241.g5fec71dd version. But in the master branch of the Krusader's repo ( the latest commit is 04e6286f. It was a month ago. And I have it already:

The question:

Why I received update notification from pamac and to which commit version it suggests me to update? Where to view that some new and hidden (in Krusader's repo) commit message?

sir_lucjan commented on 2021-11-19 15:38 (UTC)

Now I no longer understand anything. What downgrade do you mean? Which manager are you using? Just because there is a version in AUR from a year ago does not mean that it will be installed. PKGBUILD ALWAYS downloads the latest possible version and during the build, the pkgver version updates itself automatically with:

pkgver() {
  cd krusader
  _ver="$(cat CMakeLists.txt | grep -m1 'set(VERSION' | cut -d '"' -f2 | tr - .)"
  echo "${_ver}.r$(git rev-list --count HEAD).g$(git rev-parse --short HEAD)"

This is how git packages work in AUR. I would not be able to update them every new commit. Show exactly what messages you have when you update and what software manager you are using.

livem commented on 2021-11-19 15:23 (UTC) (edited on 2021-11-19 15:25 (UTC) by livem)

Sir, do not want to be annoying, but I really can't understand why we should downgrade from the current version of pacman -Qi krusader-git | grep Ver Version :

with the last update a month ago (

to the


which was a year ago (by your link

It is the downgrade even if compare their revision numbers: current r6379 vs r6241.

So why we need to downgrade to 138 commits back? Really, really can't understand this to go to a year ago state.

Probably it is the time to add krusader-git package to ignore list to prevent that downgrade.

@sir_lucjan, please, when you will have some time, try to fix it in order to prevent such downgrades.

sir_lucjan commented on 2021-11-19 10:30 (UTC)

The PKGBUILD of a package in git updates only when there is a change to its modification. It always builds the latest version so there is nothing to worry about. This version is from the last PKGBUILD modification and no changes have been needed since then.

This commit is also in the master branch.

livem commented on 2021-11-19 10:15 (UTC)

@sir_lucjan Thank you for the answer. You wrote:

the latest commit is 04e6286f952703a23672989ce14255488f47a064

but the

the package version title is Package Details: krusader-git also, so the commit used for build is 5fec71dd.... I am talking about that difference.

The question: where that 5fec71dd... commit originates from? How to find it? Where the krusader-git package finds it, if as you said, it is absent in master branch?

sir_lucjan commented on 2021-11-19 08:37 (UTC)

PKGBUILD is prepared to always build the latest version from the master branch - in this case the latest commit is 04e6286f952703a23672989ce14255488f47a064. Sorry, but could you be a bit more specific about what you mean?

livem commented on 2021-11-19 07:26 (UTC)


Thank you for maintaining!

I see the PKGBUILD tells the, but why I can't see git log on both new commits? ​has commits only for the krusader version as latest available.

So where those two commits originated from if not from the git's master branch?