Package Details: antidot-bin 0.6.2-1

Git Clone URL: (read-only, click to copy)
Package Base: antidot-bin
Description: Cleans up your $HOME from those pesky dotfiles
Upstream URL:
Licenses: MIT
Conflicts: antidot
Provides: antidot
Submitter: billypilgrim
Maintainer: billypilgrim
Last Packager: billypilgrim
Votes: 2
Popularity: 0.75
First Submitted: 2020-12-15 18:48
Last Updated: 2021-02-23 12:35

Latest Comments

1 2 Next › Last »

doron-cohen commented on 2021-01-18 13:19

@billypilgrim Ok but please, if you are unable to maintain this anymore send me an email or open an issue so I will hook it up to the CI again.

By the way I do want the automatic publishing to AUR to work correctly and I do want to also create a compiling package from source. I will talk to you when I will have time for that.

Thanks again for maintaining this.

billypilgrim commented on 2021-01-18 13:13

@doron-cohen: Please don't add a duplicate AUR package. It's against AUR rules and it'll get removed.

I'm happy to keep maintaining this and it'll be updated promptly when there's a new release. It's really best to have an Arch user who's actually using a package maintain it.

doron-cohen commented on 2021-01-18 13:05

I understand your concerns. I do check that yay is able to install the release so I think the format is good. The thing is that I had something broken in goreleaser config so I had to create the release again and again until it worked. But now it should be OK.

I appreciate the fact you maintain this but I do want to make sure new releases are uploaded promptly. If you don't mind I will also maintain another antidot repos when I will have the chance so I could release and not have to check if the release is updated on AUR.

billypilgrim commented on 2021-01-18 12:42

Hey @doron-cohen. Sorry, it's just that it seemed like your CI was going a bit crazy. I got notifications for 6 updates to this package and when I tried building it failed.

How about I just maintain this package the old-school way (i.e. manually bump the pkgver etc. when a new version is released)? It's just that I'm guessing you're not running Arch because the Arch tools (makepkg) won't build the packages your script is generating.

End users might well have notifications for this package enabled, so it's probably a bit inconvenient to have a load of notifications about package updates and a PKGBUILD which won't work.

doron-cohen commented on 2021-01-18 11:47

hey @billypilgrim why did you remove me as a co-maintainer? I just got to fix the CI so it all should work ok.

billypilgrim commented on 2020-12-24 15:08

@doron-cohen: No worries. Yeah, fixing the URL and SHA256 sum is all good. You should be able to build it with makepkg (which you can get from the pacman repo if you're not on Arch).

It's fine if you were just testing the CI and you do want to increment pkgrel if you're changing the PKGBUILD.

doron-cohen commented on 2020-12-23 13:15

@billypigrim sorry saw it only now. I had to test the CI somehow. I didn't push different package versions to the same one. Are you saying I shouldn't increment the pkgrel at all? What about fixing the URL or the SHA256 sum?

@Tio I fixed the issue now.

Tio commented on 2020-12-22 23:22

I get this error:

curl: (22) The requested URL returned error: 404 Not Found
==> ERROR: Failure while downloading

billypilgrim commented on 2020-12-20 12:01

@doron-cohen: Please don't do that! It makes things hard for packagers and other users. Make a new point release instead. Otherwise it's really annoying to work out which of the multiple v0.4.2 releases you're actually using.

The pkgrel field really isn't for dealing with multiple versions of the software released with the same number either, so please stop incrementing it all the time ;-). It's for when you've changed something to do with how you're packaging the software (e.g. adding a dependency or something).

doron-cohen commented on 2020-12-20 11:00

Ok I am able to push. 0.4.2 is pushed now. I am still tweaking some stuff so I may push a second release to this version.