Package Details: mint-artwork 2:1.6.0-0

Git Clone URL: https://aur.archlinux.org/mint-artwork.git (read-only, click to copy)
Package Base: mint-artwork
Description: Linux Mint Artwork and Resources.
Upstream URL: http://packages.linuxmint.com/pool/main/m/mint-artwork
Keywords: cinnamon mint mint-artwork
Licenses: GPL
Conflicts: lightdm-gtk-greeter, lightdm-gtk-greeter-settings, mint-sounds
Submitter: OdinVex
Maintainer: OdinVex
Last Packager: OdinVex
Votes: 24
Popularity: 0.99
First Submitted: 2021-03-05 03:18 (UTC)
Last Updated: 2022-07-09 17:18 (UTC)

Latest Comments

1 2 3 4 5 6 .. 9 Next › Last »

OdinVex commented on 2022-07-09 17:19 (UTC)

@yangyf, In the future, you can 'Flag package out-of-date' to let me know.

yangyf commented on 2022-07-09 16:24 (UTC)

please update to 1.6.0

OdinVex commented on 2022-05-18 02:28 (UTC) (edited on 2022-05-18 02:35 (UTC) by OdinVex)

@yochananmarqos, Yeah, turns out we've been essentially using Epoch to signify builds in general to prevent any kind of issue relating to 'are we on the latest build' kind of stuff. It works, but not exactly intended for this particular use. Will keep at 2 then, the numbering scheme doesn't bother me. Quite frankly, I wouldn't care if I ended up at Epoch 9001. I'd rather see Epoch as a Delta change. I wish semantic versioning were just a timestamp.

yochananmarqos commented on 2022-05-18 02:26 (UTC)

@OdinVex: Tip: use vercmp to make sure the next version you bump to is actually higher.

OdinVex commented on 2022-05-18 02:18 (UTC) (edited on 2022-05-18 02:21 (UTC) by OdinVex)

@yochananmarqos, I've done it already with this AUR, and two associates of mine do it as well. Or we're all three doing it incorrect. Either way, I've cleared it before, and it has worked fine. Edit: Seeing some conflicting epoch rules now, though. Hm, maybe. We'll find out next version update.

yochananmarqos commented on 2022-05-18 02:14 (UTC) (edited on 2022-05-18 02:14 (UTC) by yochananmarqos)

@OdinVex: That's not the way epochs are used--in fact, they should never or rarely be used. Your stuck with a 2 now. The pkgrel should be bumped when changes are made in between upstream pkgver changes.

OdinVex commented on 2022-05-18 01:19 (UTC) (edited on 2022-05-18 01:20 (UTC) by OdinVex)

@yochananmarqos, Can't tell if you're joking or not about the epoch, because you clearly can. Package version will always maintain upstream version. Epoch is only used to fix errors or compatibility issues in maintaining this AUR, though pkgrel should usually be used. For small stuff like this, I use epoch. If it were an entire rewrite of some section, sure, I'd use pkgrel. It's alright to use it this way. Epoch gets reset every time I update the package version. :)

yochananmarqos commented on 2022-05-18 01:05 (UTC)

@OdinVex: I see your last commit 10 minutes ago. You should be bumping the pkgrel, not using an epoch at all. However, now that you have an epoch, you can never remove it.

OdinVex commented on 2022-05-18 01:00 (UTC) (edited on 2022-05-18 01:01 (UTC) by OdinVex)

@yochananmarqos, Yeah, I was trying to update it from a temporary KDE install to add proper Cinnamon restarting (instead of the old way). The clipboard software didn't copy 'export' from my many random text editors at the time as I intended, it kept a line of 'sudo' code that I edited but forgot to read the entire thing. I forgot about the cp command hating me on the methods of copying files I usually use. Should be fine now, though I'm waiting for the repo on the AUR to show an updated PKGBUILD. I also updated the CHANGELOG, forgot to last time (about the quotes bit).

yochananmarqos commented on 2022-05-18 00:55 (UTC)

@OdinVex: Ah, I see. Nevermind me, then.