Package Details: dunst-git 1.9.0.r3.g1ef38e5-1

Git Clone URL: https://aur.archlinux.org/dunst-git.git (read-only, click to copy)
Package Base: dunst-git
Description: A highly configurable and lightweight notification daemon
Upstream URL: https://dunst-project.org/
Licenses: BSD
Conflicts: dunst
Provides: dunst, notification-daemon
Submitter: None
Maintainer: pmattern
Last Packager: pmattern
Votes: 59
Popularity: 0.26
First Submitted: 2011-09-08 20:54 (UTC)
Last Updated: 2022-07-28 14:47 (UTC)

Required by (69)

Sources (1)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »

CyberShadow commented on 2018-01-17 15:18 (UTC)

Foxboron: please take the time to understand the problem. -git or no -git, your PKGBUILD still broke the versioning scheme, which is affecting pacman, not the AUR helper.

Foxboron commented on 2018-01-17 15:15 (UTC)

This is a -git package. A propper AUR helper should be checking the git repo for new revisions. If that isn't the case, the responsibility to update -git packages falls on the user. An epoch is not going to be added.

CyberShadow commented on 2018-01-11 03:03 (UTC) (edited on 2018-01-11 03:04 (UTC) by CyberShadow)

Hi,

I noticed that the pkgver scheme changed recently.

Before: 1.2.0.103.953.ga257556-1

After : 1.2.0.r223.gf7cf5b6-1

Unfortunately, the new scheme seems to be "older" than the old one, as far as pacman's version comparison algorithm goes. So, AUR helpers will think that new packages are older than old ones.

You may want to address this by using a new epoch in the PKGBUILD: https://wiki.archlinux.org/index.php/PKGBUILD#epoch

TrialnError commented on 2018-01-06 21:07 (UTC) (edited on 2018-01-06 21:14 (UTC) by TrialnError)

Upstream repo contain tags, but the pkgver is chosen for tagless repos?

Nevertheless, the reason why I wanted to comment: Upstream dropped gtk3 hard dep and relies instead on gdk-pixbuf

Edit: Oh, and there seems now a libxrandr dependency

haawda commented on 2017-12-20 09:33 (UTC)

I fixed the pkgver, and I orphan this package. The guideline is too stupid.

eschwartz commented on 2017-12-19 12:25 (UTC) (edited on 2017-12-19 12:32 (UTC) by eschwartz)

Hello, you're currently violating the AUR guidelines. Please turn off your "AUR Update Bot" and don't do anything like that again. :)

https://wiki.archlinux.org/index.php/Arch_User_Repository#Foo_in_the_AUR_is_outdated.3B_what_do_I_do.3F

EDIT: Also please use a decent pkgver function like the one listed in the wiki: https://wiki.archlinux.org/index.php/VCS_package_guidelines#Git

Using the commit count twice, without properly marking it as r$rev anywhere, causes far too much trouble when calculating version comparison logic for no gain.

haawda commented on 2017-10-21 23:50 (UTC)

I removed the line deleting config.h.

TrialnError commented on 2017-10-21 18:26 (UTC)

With #371 merged the prepare function will need some adjustments, else the compilation failes because config.h is getting deleted :D

haawda commented on 2017-08-02 21:03 (UTC)

TrialnError, namcap told me, that dunstify still needs gtk2, but it was a leftover from the previous build. Indeed only gtk3 is needed. hero, I chnaged the pkgver function in a way that the revlist comes before the git hash. I hope this has no bad side effects.

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »