Package Details: asbru-cm-loki-git 6.3.2.r38.g2291405-1

Git Clone URL: https://aur.archlinux.org/asbru-cm-loki-git.git (read-only, click to copy)
Package Base: asbru-cm-loki-git
Description: A free and open-source connection manager. loki branch
Upstream URL: https://github.com/asbru-cm/asbru-cm
Licenses: GPL3
Submitter: figue
Maintainer: figue (jfigueras, figuepluto)
Last Packager: figue
Votes: 1
Popularity: 0.000000
First Submitted: 2020-01-07 22:48 (UTC)
Last Updated: 2021-07-10 19:24 (UTC)

Dependencies (32)

Required by (0)

Sources (1)

Latest Comments

« First ‹ Previous 1 2

wcasanova commented on 2019-12-06 00:30 (UTC)

If I understand Figue, but that is the desired behavior, it is not Yay's fault. when making makepkg -sicf with the options c and f forces, the ideal is that with the makepkg -si options. it will automatically generate the new package with the changes https://wiki.archlinux.org/index.php/PKGBUILD#pkgver https://wiki.archlinux.org/index.php/Arch_package_guidelines#Package_versioning https://wiki.archlinux.org/index.php/VCS_package_guidelines#Git

greetings friend

figue commented on 2019-11-12 23:12 (UTC)

@b1tl0rd hi! This is a problem related with yay. You know, AUR helpers should not be used to do this simple things... Just clone my repo and install with makepkg:

git clone https://aur.archlinux.org/asbru-cm-gtk3-git.git
cd asbru-cm-gtk3-git
makepkg -sicf

I never used yay, personally I like trizen, but I use only to upgrade the entire system.

Cheers

wcasanova commented on 2019-11-12 21:21 (UTC) (edited on 2019-11-12 21:23 (UTC) by wcasanova)

Hi Figue, as is the configuration, when you do an update, the package is not updated. since the package keeps the name and ignores the changes.. if you do a git branch -v if you see the changes, but don't generate the pkg.tar.xz again example today I made a yay -S asbru-cm-gtk3-git, when I execute the command again to bring the new commits back to me, I actually download them, but it doesn't recreate the package. the only way to generate with the new changes is to clear the cache  or with the option of yay cleanBuild

it is not better than the package, generate a new name with the new commit, as well as the other git packages of aur

figue commented on 2019-11-04 00:41 (UTC)

It's correct, yay use master to build:

source=("yay::git+https://github.com/Jguer/yay.git#branch=master")

in asbru-cm-gtk3-git we use gtk3:

source=("git+https://github.com/asbru-cm/asbru-cm.git#branch=gtk3" asbru-cm-gtk3.desktop)

Look my new comment:

https://github.com/asbru-cm/asbru-cm/issues/259#issuecomment-549196444

You can use src directory to see exactly what commit is used, but makepkg "does do job just right", if you rebuild the package with -f it will refresh gtk3 branch as always.

wcasanova commented on 2019-11-03 22:28 (UTC) (edited on 2019-11-03 22:35 (UTC) by wcasanova)

@figue thanks, but that returns is branch master, gtk3 ?

$ git --git-dir=asbru-cm describe --long --tags
5.2.1-0-g1687e82..

lastet commit gtk3 is https://github.com/asbru-cm/asbru-cm/commit/c4c2ab421878c67e4e15c84779640f8c909cff85

in other packages of the git branch is to place the version plus the commit or head of the commit git ..

I give you an example of the PKGBUILD of yay-git https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=yay-git yay-git 9.4.2.r0.g290d3d2-2

figue commented on 2019-11-03 21:22 (UTC)

Hi @b1tl0rd, please see my comment:

https://github.com/asbru-cm/asbru-cm/issues/259#issuecomment-549179718

wcasanova commented on 2019-11-03 12:50 (UTC)

@figue Hello friend due to the continuous development of the GTK3 version, I think it would be better to add.

https://github.com/asbru-cm/asbru-cm/issues/259 please add pkgver git describe --long --tags

« First ‹ Previous 1 2