Tree: 1364e7538a

2.9.x

283

3.0.x

3.1

3.2.x

3.3.3.1

bip39-recovery

coincointrol-statusbar

dependabot/pip/contrib/deterministic-build/ecdsa-0.13.3

hard-fail-on-bad-server-string

ln-negative-red

master

password_lineedit

patch-1

patch-2

patch-3

patch-4

regtest_lnd

seed_v14

sqlite_db

ssl-fingerprint-check

0.56

0.57

0.57a

0.57b

0.57c

0.58

0.59

0.59a

0.59b

0.60

0.61-r1

0.61b

1.1

1.2

1.3

1.5

1.5.1

1.5.2

1.5.3

1.5.4

1.5.5

1.5.6

1.5.7

1.5.8

1.6.0

1.6.1

1.6.2

1.7

1.7.1

1.7.2

1.7.3

1.7.4

1.7rc0

1.8

1.8.1

1.9

1.9.1

1.9.2

1.9.3

1.9.4

1.9.5

1.9.6

1.9.7

1.9.8

2.0

2.0-beta

2.0.1

2.0.2

2.0.3

2.0.4

2.0b2

2.0b3

2.1

2.1.1

2.2

2.3

2.3.1

2.3.2

2.3.3

2.4

2.4.1

2.4.2

2.4.3

2.5

2.5.1

2.5.2

2.5.3

2.5.4

2.6

2.6.1

2.6.2

2.6.3

2.6.4

2.7.0

2.7.1

2.7.10

2.7.11

2.7.12

2.7.13

2.7.14

2.7.15

2.7.16

2.7.17

2.7.18

2.7.2

2.7.3

2.7.4

2.7.5

2.7.6

2.7.7

2.7.8

2.7.9

2.8.0

2.8.1

2.8.2

2.8.3

2.9.0

2.9.1

2.9.2

2.9.3

2.9.4

3.0.0

3.0.1

3.0.2

3.0.3

3.0.4

3.0.5

3.0.6

3.1.0

3.1.1

3.1.2

3.1.3

3.2.0

3.2.1

3.2.2

3.2.3

3.2.4

3.3.0

3.3.1

3.3.2

3.3.3

3.3.4

3.3.5

3.3.6

3.3.7

3.3.8

password_v2

seed_v10

seed_v5

seed_v7

seed_v8

seed_v9

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from '1364e7538a'

${ noResults }

Commit Graph

5 Commits (1364e7538acf37d1b649d2ca8ef647858540b227)

Author	SHA1	Message	Date
SomberNight	0df8392c86	build: rm need for sudo in most places; and do not run as root This includes two logically separate changes: - on the host, try not to require sudo when running the build scripts - namely when interacting with the docker daemon, this requires the unix user on the host to be part of the `docker` group - this solves part of https://github.com/spesmilo/electrum/issues/7602 - while running inside the docker containers, do not run as root - this means that e.g. files created in mounted folders should no longer be owned by root on the host - there is some code duplication involved here - not sure how it could be deduped.	3 years ago
SomberNight	8559d1eb72	build: android reprod: "pip install" needs "--no-build-isolation" maybe fixes https://github.com/spesmilo/electrum/issues/7640 Looks like by default pip is ignoring the locally available setuptools and wheel, and downloading the latest ones from the internet at build time... https://pip.pypa.io/en/stable/reference/build-system/pyproject-toml/?highlight=no-build-isolation#disabling-build-isolation https://stackoverflow.com/a/62889268 > When making build requirements available, pip does so in an isolated environment. That is, pip does not install those requirements into the user’s site-packages, but rather installs them in a temporary directory which it adds to the user’s sys.path for the duration of the build. This ensures that build requirements are handled independently of the user’s runtime environment. For example, a project that needs a recent version of setuptools to build can still be installed, even if the user has an older version installed (and without silently replacing that version). > > In certain cases, projects (or redistributors) may have workflows that explicitly manage the build environment. For such workflows, build isolation can be problematic. If this is the case, pip provides a --no-build-isolation flag to disable build isolation. Users supplying this flag are responsible for ensuring the build environment is managed appropriately (including ensuring that all required build dependencies are installed). If only it were that easy! If we add the "--no-build-isolation" flag, it becomes our responsibility to install *all* build time deps, hence we now have "requirements-build-makepackages.txt".	3 years ago
SomberNight	901a900ec5	sdist build: when building docker image, no interactive prompts! see https://askubuntu.com/questions/909277/	5 years ago
SomberNight	a06f5da7c2	sdist build: bump base image to ubuntu 20.04	5 years ago
SomberNight	e12bc4817a	attempt at reproducible tarballs (sdist)	5 years ago