You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi there, AUR packager for "darkcoin" reporting in 😉
As of today, I update the AUR package for every 0.10.15.x release, as soon as I see them. This means by that time I check my RSS feeds, a few version numbers get skipped (was v0.10.15.3 just before, now I pushed v0.10.15.6). Sadly, Github is mixing tags and releases for enforcement and master branches, so filtering out by branch isn't quite easy. And all tags get a release.
The website isn't very helpful, as it's lagging on the master releases (shows v10.14.1 on a post 2 days ago, when v10.14.2 has been tagged+released 4 days ago).
What do you recommend for the time being ? Following every enforcement release on Github or rather sticking to master-only releases as announced on the website ?
Activity
vertoe commentedon Oct 29, 2014
I'm maintaining the darkcoin-git AUR package and I keep the PKGBUILD usually aligned for the bleeding-edge users, sometimes switching branches.
As the darkcoin main package should be for regular users, you should stick to tags of the master branch only if possible.
Merge dashpay#46: Update checkpoints to guard against forks in the ne…
Merge pull request dashpay#46 from ckti/torrent-docs
Merged in debian-packages (pull request dashpay#46)
Merge bitcoin-core/gui#137: refactor: Replace deprecated Qt::SystemLo…
Squashed 'src/univalue/' changes from 2740c4f712..a44caf65fe
Squashed 'src/univalue/' changes from 2740c4f712..a44caf65fe