Package Details: git-town 7.8.0-1

Git Clone URL: https://aur.archlinux.org/git-town.git (read-only, click to copy)
Package Base: git-town
Description: Generic, high-level Git workflow support
Upstream URL: https://github.com/git-town/git-town
Licenses: MIT
Submitter: allonsy
Maintainer: alerque
Last Packager: alerque
Votes: 10
Popularity: 0.042292
First Submitted: 2015-08-01 05:10 (UTC)
Last Updated: 2022-08-08 05:28 (UTC)

Latest Comments

alerque commented on 2022-01-20 19:10 (UTC) (edited on 2022-01-20 19:14 (UTC) by alerque)

@allonsy

Re requiring go toolchain: yes absolutely we want to require go to build this. In fact according to the Arch AUR guidelines it is required to build from sources when sources are available. If people are too lazy to build they can use the -bin package variant instead (or build in a chroot so they don't have to pollute their host system, or use my user repo)

Re adoption without your consent: this package had been flagged OOD since last June or something like that. When you file an orphan request for a package that has been manually flagged for a long time (90 days I think) the request is automatically approved. Ones that haven't been flagged for so long require a 14 day wait period and a manual approval by a TU. I filled an orphan request because this was 6+ months out of date and it was instantly orphaned, so I adopted it. Also note I reposted the upstream binary variant you had here and already orphaned it, if you want to continue that feel free to adopt.

allonsy commented on 2022-01-19 18:44 (UTC)

As a question (just curious, not a negative reflection at all), how were you able to adopt the package without my consent? Was it because I haven't updated the package in a while the system marked the package as orphaned? I could also just be mis-understanding the AUR package ownership system.

With that being said, I'm happy if you want to maintain this I'm just curious about the procedure there.

allonsy commented on 2022-01-19 18:41 (UTC)

Do we really want users to have to pull in the entire go toolchain just to build this small package?

It seems a bit overkill, right?

alerque commented on 2022-01-19 10:17 (UTC)

This PKGBUILD now builds from sources.

alerque commented on 2022-01-19 09:19 (UTC) (edited on 2022-01-19 10:17 (UTC) by alerque)

This package has, till now, been incorrectly named. According to the packaging guidelines any package where the source is available but installation is from an upstream provided binary must be named -bin. I'm reposting the history of this repo as git-town-bin and (having just adopted this) plan to overhaul this package to build from sources. I am not really interested in the binary package and will probably orphan it after posting. Expect the next updates to this to build from sources.

allonsy commented on 2020-09-23 21:40 (UTC)

Now changed to use new org URL and bumped the version

allonsy commented on 2019-06-07 00:09 (UTC)

Bumped to v7.2.1

allonsy commented on 2018-06-17 02:48 (UTC)

Bumped to 7.2.0

allonsy commented on 2018-04-25 22:49 (UTC)

bumped to 7.1.1

allonsy commented on 2018-02-03 22:27 (UTC)

bumped to 6.0.1

allonsy commented on 2018-01-12 06:09 (UTC)

@mkeedlinger no worries, glad it is all sorted out now

mkeedlinger commented on 2018-01-10 22:59 (UTC)

@njam since pacaur is no longer supported I switched to trizen and things are working well.

@allonsy, sorry for the false alarm. Thanks for the great work!

njam commented on 2018-01-10 08:20 (UTC) (edited on 2018-01-10 08:20 (UTC) by njam)

After clearing the pacaur cache it works for me:

rm -rf ~/.cache/pacaur/git-town

Not sure what was going on here. I had this issue on 2 machines. But now the md5 sum of the download is the same as in SRCINFO:

curl -sL -o- 'https://github.com/Originate/git-town/releases/download/v5.1.0/git-town-linux-amd64' | md5sum -
20f3e531d165fee0fad214a7bb04868b  -

mkeedlinger commented on 2018-01-10 01:52 (UTC) (edited on 2018-01-10 01:53 (UTC) by mkeedlinger)

@allonsy, this seems to be all that's relevant.

:: Checking git-town integrity...
==> Making package: git-town 5.1.0-1 (Tue Jan  9 18:44:36 MST 2018)
==> Retrieving sources...
  -> Found git-town
  -> Found LICENSE
==> Validating source files with md5sums...
    git-town ... FAILED
    LICENSE ... Skipped
==> ERROR: One or more files did not pass the validity check!
:: failed to verify private-internet-access-vpn integrity
:: failed to verify git-town integrity

It is worth noting that I am using pacaur, which I am aware is not really supported anymore; still, it is currently working for all my other packages. I'll find something else later.

allonsy commented on 2018-01-04 04:38 (UTC)

Hmmm, I'm not able to replicate this error when installing manually (using cower + makepkg). Can you post the relevant error message that you are getting?

mkeedlinger commented on 2018-01-03 06:06 (UTC)

I am having the same issue as njam.

njam commented on 2018-01-02 11:47 (UTC)

I think .SRCINFO was not updated? Validation for "git-town" fails.

allonsy commented on 2017-12-30 22:53 (UTC)

updated to 5.1.0 let me know if you run into any issues

allonsy commented on 2017-05-15 00:28 (UTC) (edited on 2017-05-15 00:28 (UTC) by allonsy)

32 bit support has been dropped due to minimal demand. If you would like this reinstated, please comment so I can know to add more binary sources to the package

allonsy commented on 2017-05-15 00:26 (UTC)

Updated to 4.0.0 which is a unified go binary Let me know if you notice any issues with this new release

allonsy commented on 2017-01-12 17:26 (UTC)

Updated to 2.1.0

allonsy commented on 2016-09-18 22:44 (UTC)

updated to 2.0.0 There are breaking changes with the new command format (all commands are now prefixed with town). Run 'git town alias true' to alias all old commands to the new commands (will not overwrite existing aliases).

allonsy commented on 2016-08-11 07:32 (UTC)

1.0.0 released and updated. Feel free to comment if you have any issues!

allonsy commented on 2016-08-03 02:56 (UTC)

bumped version! Thanks for the wait!

kdiogenes commented on 2016-07-27 14:44 (UTC)

Update for 0.10.1, please!

allonsy commented on 2016-02-14 00:40 (UTC)

updated to v0.10.0