Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Arch Linux AUR maintainer #78

Closed
ManfredKarrer opened this issue Nov 2, 2018 · 34 comments
Closed

Arch Linux AUR maintainer #78

ManfredKarrer opened this issue Nov 2, 2018 · 34 comments
Assignees
Labels
team:dev https://bisq.wiki/Dev_Team

Comments

@ManfredKarrer
Copy link
Member

ManfredKarrer commented Nov 2, 2018

The Arch Linux distibution builds all applications from source code and use the AUR format for delivering build instructions.
See: https://aur.archlinux.org/packages/bisq/

Primary role owner: @freimair (is maintainer of that AUR repository)

@freimair
Copy link
Member

freimair commented Nov 5, 2018

actually, there are three version of bisq in AUR:

@ManfredKarrer
Copy link
Member Author

Can you consolidate those?

@freimair
Copy link
Member

freimair commented Nov 6, 2018

Each of these have their place in the AUR (it is the Arch linux way, kind of). The interested user can either have a quick install (without the need for compilation, borrowed from a binary release), a stable install (built from release tag) or a cutting edge install (built from master).

What characteristics do you suggest for a consolidated package?

@ManfredKarrer
Copy link
Member Author

Ah, ok.

@freimair
Copy link
Member

freimair commented Nov 28, 2018

2018.11 report

  • The 0.8.1 release stirred things up a bit. No harm has been done to the bin package. A simple version change did the trick. The git package does not care about releases anyways. However, I could not figure out how to build bisq 0.8.1 from source. I checked with @ripcurlx: the recent "moving repos around" shaked up the build process and building 0.8.1 from source is "tricky". I decided to leave the package out of date until 0.9 comes along.
  • The git package somehow still used the deprecated repo bisq-desktop. Fixed it. And ran straight into:
  • The git package got thrown out of line when the location of the binaries had been changed. It took me some time to find the issue and fix the package. I also suggested a fix to the issue in Fix broken startScripts in $destinationDir/bin dirs bisq#1979 as I already found the cause.

/cc bisq-network/compensation#166

@freimair
Copy link
Member

2018.12 report

  • moved the packages first to 0.9.0 then to 0.9.1
  • did some optimizations along the way
  • nothing special

/cc bisq-network/compensation#185

@freimair
Copy link
Member

freimair commented Jan 9, 2019

2019.01 report

lets see how things evolve.

@freimair
Copy link
Member

2019.02 report

  • updated to 0.9.4

nothing new on the Wayland front

@freimair
Copy link
Member

freimair commented Mar 3, 2019

2019.03 report

  • ad Wayland: a fix has been proposed a while ago. However, it has been rejected. However, if the issue is encountered, a simple -Djdk.gtk.version=2 might just do the trick (at least it does for me)
  • updated bisq and bisq-bin to 0.9.5

@freimair
Copy link
Member

freimair commented Jun 5, 2019

2019.05 report

  • updated bisq and bisq-bin to 1.1.2

@freimair
Copy link
Member

freimair commented Jul 8, 2019

2019.06 report

  • nothing to report

@freimair
Copy link
Member

freimair commented Aug 8, 2019

2019.07 report

  • updated bisq and bisq-bin to 1.1.3
  • updated bisq and bisq-bin to 1.1.4
  • updated bisq and bisq-bin to 1.1.5
  • added checksums

@freimair
Copy link
Member

freimair commented Sep 16, 2019

2019.09 report

  • updated bisq and bisq-bin to 1.1.6
  • updated bisq and bisq-bin to 1.1.7

@freimair
Copy link
Member

freimair commented Nov 1, 2019

2019.10 report

  • updated bisq and bisq-bin to 1.2.1
  • updated bisq and bisq-bin to 1.2.2
  • updated bisq and bisq-bin to 1.2.3

@freimair
Copy link
Member

freimair commented Mar 31, 2020

Cycle 12 report

  • updated bisq and bisq-bin to 1.2.8
  • updated bisq and bisq-bin to 1.2.9
  • updated bisq and bisq-bin to 1.3.0
  • updated bisq and bisq-bin to 1.3.1

@cbeams cbeams added the team:dev https://bisq.wiki/Dev_Team label Apr 15, 2020
@freimair
Copy link
Member

freimair commented Apr 22, 2020

Cycle 13 report

  • updated bisq and bisq-bin to 1.3.2
  • skipped 1.3.3 because it has only been pre-released.
  • updated bisq and bisq-bin to 1.3.4

@freimair
Copy link
Member

freimair commented Jun 12, 2020

Cycle 14 report

  • updated bisq to use jdk-11-openjdk, because Arch Linux no longer provides a reasonable source for jdk-10-openjdk
  • marked bisq-git to be deleted
  • git-lfs does not go with downloading source tarballs. Hence, reverted package "bisq" to use git clone. However, to prevent clients from downloading the whole 400MB of data, I threw in a "--depth=1" to the clone command. Downloaded data size is now approx. 100MB (=20MB src + 80MB data stores).

@freimair
Copy link
Member

freimair commented Jul 16, 2020

Cycle 15 report

  • updated bisq and bisq-bin to 1.3.6

@freimair
Copy link
Member

freimair commented Sep 3, 2020

Cycle 17 report

  • updated bisq and bisq-bin to 1.3.9

@freimair
Copy link
Member

Cycle 18 report

  • since no releases have been made, nothing was updated

@freimair
Copy link
Member

freimair commented Nov 10, 2020

Cycle 19 report

  • updated bisq and bisq-bin to 1.4.2
  • adjusted runtime jdk for these releases as there is no more jdk11 for arch linux
  • updated bisq and bisq-bin to 1.5.0

@freimair
Copy link
Member

freimair commented Dec 20, 2020

Cycle 20 report

  • updated bisq and bisq-bin to 1.5.1
  • updated bisq and bisq-bin to 1.5.2

@freimair
Copy link
Member

freimair commented Dec 30, 2020

Cycle 21 report

  • updated bisq and bisq-bin to 1.5.3
  • updated bisq and bisq-bin to 1.5.4

@freimair
Copy link
Member

freimair commented Feb 2, 2021

Cycle 22 report

  • updated bisq and bisq-bin to 1.5.5
  • moved "bisq" package to use the source tarball as it includes the binary files and a signature file is provided now (get rid of git in the installation process)
  • updated bisq and bisq-bin to 1.5.6
  • updated bisq and bisq-bin to 1.5.8

@freimair
Copy link
Member

freimair commented Mar 30, 2021

Cycle 23 report

  • updated bisq and bisq-bin to 1.5.9
  • updated bisq and bisq-bin to 1.6.1
  • updated bisq and bisq-bin to 1.6.2

@freimair
Copy link
Member

freimair commented May 7, 2021

Cycle 24 report

  • updated bisq and bisq-bin to 1.6.4, thereby cleaning the build process because the hack of getting a makeshift jdk10 (which has been removed from the Arch repositories a long time ago) for building and running is no longer needed

@freimair
Copy link
Member

freimair commented Jul 6, 2021

Cycle 25 report

nothing happened

@freimair
Copy link
Member

freimair commented Jul 6, 2021

Cycle 26 report

  • updated bisq to 1.7.0 and introduced a build dependency for jdk11-openjdk
  • updated bisq and bisq-bin to 1.7.1 pre and set build dependency and runtime to jdk11-openjdk

@freimair
Copy link
Member

Cycle 27 report

  • updated bisq and bisq-bin to 1.7.2

@freimair
Copy link
Member

freimair commented Aug 31, 2021

Cycle 28 report

  • updated bisq and bisq-bin to 1.7.3

@freimair
Copy link
Member

Cycle 29 report

  • updated bisq and bisq-bin to 1.7.4

@cbeams cbeams closed this as completed May 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
team:dev https://bisq.wiki/Dev_Team
Projects
None yet
Development

No branches or pull requests

3 participants