[arch-projects] [dbscripts] [GIT] Official repo DB scripts branch master updated. 20131102-81-g8cc8e9c

2018-03-21 Thread Eli Schwartz via arch-projects 
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Official repo DB scripts".

The branch, master has been updated
   via  8cc8e9cbbefdf6fac368031d3dacc74d001f23b7 (commit)

[arch-projects] [dbscripts] [GIT] Official repo DB scripts branch pacman-git created. 20131102-82-gcda3694

2018-03-21 Thread Eli Schwartz via arch-projects
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Official repo DB scripts". The branch, pacman-git has been created at cda3694d0b247849e12edcd56e0ca7a41ec90ae1 (commit) - Log

[arch-projects] [dbscripts] [PATCH] db-functions: unify the repo-add/repo-remove caller

2018-02-26 Thread Eli Schwartz via arch-projects
Use less duplicated logic, opening the way to more elegantly change the interface for the repo-add/repo-remove scripts which are themselves symlinked together and mostly have the same interface. Signed-off-by: Eli Schwartz --- db-functions | 34

Re: [arch-projects] [dbscripts] [PATCH v2 3/3] Update messages to make fuller use of printf formatters

2018-02-26 Thread Eli Schwartz via arch-projects
On 02/26/2018 05:14 PM, Luke Shumaker wrote: > On Mon, 26 Feb 2018 00:46:48 -0500, > Eli Schwartz wrote: >>> +++ b/db-functions >>> @@ -450,7 +450,7 @@ arch_repo_add() { >>> # package files might be relative to repo dir >>> pushd "${FTP_BASE}/${repo}/os/${arch}" >/dev/null >>>

Re: [arch-projects] [devtools] makechrootpkg: respect GNUPGHOME

2018-02-27 Thread Eli Schwartz via arch-projects
On 02/27/2018 05:41 AM, Emiel Wiedijk via arch-projects wrote: > Correct, but makepkg --verifysource is run with sudo -u $myuser, and sudo > resets the environment. And the code that copies ~/.gnupg to the chroot > apparantly hasn't been removed yet (as of >

[arch-projects] [dbscripts] [GIT] Official repo DB scripts branch master updated. 20180603-6-g971181b

2018-10-07 Thread Eli Schwartz via arch-projects
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Official repo DB scripts". The branch, master has been updated via 971181bf94d5e86bd7fce41303b51d1b3befc85b (commit) via

[arch-projects] [dbscripts] [GIT] Official repo DB scripts branch master updated. 20180603-12-g549fe00

2018-10-16 Thread Eli Schwartz via arch-projects
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Official repo DB scripts". The branch, master has been updated via 549fe0017f44031b24fb5322726721b95cca395b (commit) via

[arch-projects] [dbscripts] [GIT] Official repo DB scripts branch master updated. 20180603-10-g61c9cc6

2018-10-16 Thread Eli Schwartz via arch-projects
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Official repo DB scripts". The branch, master has been updated via 61c9cc6f44e654a90a12da11be06e707e3f4b162 (commit) via

[arch-projects] [dbscripts] [PATCH 4/4] Finish the svn refactor by implementing helper functions to write to the VCS

2018-10-08 Thread Eli Schwartz via arch-projects
Signed-off-by: Eli Schwartz --- db-functions-svn | 46 ++ db-move | 23 --- db-remove| 5 ++--- 3 files changed, 52 insertions(+), 22 deletions(-) diff --git a/db-functions-svn b/db-functions-svn index

[arch-projects] [dbscripts] [PATCH 0/4] Refactoring svn calls

2018-10-08 Thread Eli Schwartz via arch-projects
Having svn code intertwined with everything is complicated and results in it being harder to replace svn with something else. As a first step to hopefully migrating to git, I've refactored everything that directly touched svn to be contained in db-functions-svn, and renamed to be generic enough

[arch-projects] [dbscripts] [PATCH 1/4] Preliminary work to break out svn-specific code.

2018-10-08 Thread Eli Schwartz via arch-projects
Introduce "db-functions-$VCS" which will eventually contain all VCS-specific code, and make this configurable in config. Move private arch_svn function and svn acl handling here, and introduce a new source_pkgbuild function to handle discovering PKGBUILDs from the configured VCS and sourcing them

[arch-projects] [dbscripts] [PATCH 2/4] Factor out the exporting of files/folders from svn.

2018-10-08 Thread Eli Schwartz via arch-projects
As of the source_pkgbuild rewrite, this is only ever done once. Signed-off-by: Eli Schwartz --- cron-jobs/sourceballs | 3 +-- db-functions-svn | 15 +++ 2 files changed, 16 insertions(+), 2 deletions(-) diff --git a/cron-jobs/sourceballs b/cron-jobs/sourceballs index

Re: [arch-projects] [devtools] [PATCH 1/2] arch-nspawn, mkarchroot: Allow not sharing the cache directories.

2019-01-15 Thread Eli Schwartz via arch-projects
On 1/15/19 8:34 AM, Maarten de Vries via arch-projects wrote: > These patches make it possible to build withouth a shared pacman cache > using makechrootpkg. I need this myself because I'm building packages > for different repositories where some of them contain packages with the > same name, but

Re: [arch-projects] [devtools] [PATCH 1/2] arch-nspawn, mkarchroot: Allow not sharing the cache directories.

2019-01-15 Thread Eli Schwartz via arch-projects
On 1/15/19 8:56 AM, Maarten de Vries wrote: > On Tue, 15 Jan 2019 at 14:41, Eli Schwartz via arch-projects > wrote: >> >> On 1/15/19 8:34 AM, Maarten de Vries via arch-projects wrote: >>> These patches make it possible to build withouth a shared pacman cache >

Re: [arch-projects] [devtools] [PATCH 1/2] arch-nspawn, mkarchroot: Allow not sharing the cache directories.

2019-01-17 Thread Eli Schwartz via arch-projects
On 1/17/19 6:27 AM, Maarten de Vries wrote: > The commit you linked earlier[1], is that something that will find > it's way into mainline devtools? > > [1] > https://github.com/eli-schwartz/devtools/commit/c0681c0ec0a93a4a4eaf9b2fd85ce48a30702a03 Unlikely. Not that I'm opposed to it happening,

Re: [arch-projects] [pyalpm] [PATCH] Rename function to match renamed name in pacman master

2019-01-18 Thread Eli Schwartz via arch-projects
On 1/18/19 10:16 AM, Morgan Adamiec via arch-projects wrote: > On Fri, 18 Jan 2019 at 14:53, Eli Schwartz via arch-projects > wrote: >> >> alpm_sync_newversion becomes alpm_sync_get_new_version and changes >> behavior slightly. See for details: >> https://git.archl

[arch-projects] [pyalpm] [PATCH] Rename function to match renamed name in pacman master

2019-01-18 Thread Eli Schwartz via arch-projects
alpm_sync_newversion becomes alpm_sync_get_new_version and changes behavior slightly. See for details: https://git.archlinux.org/pacman.git/commit/?id=e9d91a688d1a2ebe58e8a895853debf745a529cf --- DO NOT MERGE THIS until after pacman 5.2 or 6 is released. pacman does not have any good

Re: [arch-projects] [arch-devops] [dbscripts] [PATCH 2/4] Add reproducible archive of packages.

2018-12-12 Thread Eli Schwartz via arch-projects
On 12/12/18 3:55 AM, Jelle van der Waa wrote: > On 12/04/18 at 01:15pm, Eli Schwartz via arch-devops wrote: >> On 12/4/18 1:09 PM, Eli Schwartz wrote: >>> Whenever adding new package files to the pool of distributed packages, >>> hardlink a copy of every package it was built with, into a >>>

Re: [arch-projects] [namcap] [PATCH] makedepends: Make VCS matching more robust

2018-12-01 Thread Eli Schwartz via arch-projects
On 12/1/18 9:54 AM, Michael Straube via arch-projects wrote: > If a VCS source is renamed using the "::" syntax the makedepends are not > detected. If there are files starting with in the source > array false positives are produced. See the gitlab package for example. Make > the matching more

[arch-projects] [dbscripts] [PATCH 2/4] Add reproducible archive of packages.

2018-12-04 Thread Eli Schwartz via arch-projects
Whenever adding new package files to the pool of distributed packages, hardlink a copy of every package it was built with, into a "reproducible" pool, and log which file required it. Signed-off-by: Eli Schwartz --- config | 1 + config.local.svn-community | 1 +

[arch-projects] [dbscripts] [PATCH 4/4] ftpdir-cleanup: handle removal of reproducible archives as well

2018-12-04 Thread Eli Schwartz via arch-projects
This reuses the same logic used for normally deleting packages, but cleanup of the reproducible archive happens in a subdirectory of ${CLEANUP_DESTDIR} while still subject to the same timeouts. Signed-off-by: Eli Schwartz --- cron-jobs/ftpdir-cleanup | 18 ++ 1 file changed, 14

[arch-projects] [dbscripts] [PATCH 1/4] tests: make dummy copies of all pkgpool packages in the test environment

2018-12-04 Thread Eli Schwartz via arch-projects
Prerequisite for reproducible archives of packages. Signed-off-by: Eli Schwartz --- test/lib/common.bash | 12 +++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/test/lib/common.bash b/test/lib/common.bash index bc2b4e6d..3dda5f62 100644 --- a/test/lib/common.bash +++

[arch-projects] [dbscripts] [PATCH 3/4] ftpdir-cleanup: remove useless loop and make clean_pkg take a targetdir

2018-12-04 Thread Eli Schwartz via arch-projects
This is never ever called for multiple packages at once, and if it was, it would be named clean_pkgs. Meanwhile, it was implied that this could take a variable target, but that was never-used code. Make it useful because we might (will) use it. Signed-off-by: Eli Schwartz ---

Re: [arch-projects] [dbscripts] [PATCH 2/4] Add reproducible archive of packages.

2018-12-04 Thread Eli Schwartz via arch-projects
On 12/4/18 1:09 PM, Eli Schwartz wrote: > Whenever adding new package files to the pool of distributed packages, > hardlink a copy of every package it was built with, into a > "reproducible" pool, and log which file required it. The question becomes, where can I store these? As-is, this will

[arch-projects] [dbscripts] [PATCH 1/3] testing2x: be more generic and accept multiple testing repos

2018-12-02 Thread Eli Schwartz via arch-projects
Currently multilib is a second-class citizen the way it is lumped into community, and dbscripts cannot even keep track of whether it constitutes a testing repo. Teach config to track both testing and staging repos just like the stable ones, and teach testing2x to search through TESTING_REPOS to

[arch-projects] [dbscripts] [PATCH 2/3] db-update: die when trying to update a package without updating a pending rebuild

2018-12-02 Thread Eli Schwartz via arch-projects
A semi-common pattern is for one maintainer to stage a rebuild of a package due to e.g. cascading repository-wide python/boost/whatever rebuilds, and then for the original maintainer of the package to not notice and update the package in the stable repo, leaving an out of date rebuild in staging

[arch-projects] [dbscripts] [PATCH v2 1/2] tests: make dummy archive copies of all packages in the test environment

2019-01-08 Thread Eli Schwartz via arch-projects
Prerequisite for reproducible archives of packages. Signed-off-by: Eli Schwartz --- test/lib/common.bash | 10 ++ 1 file changed, 10 insertions(+) diff --git a/test/lib/common.bash b/test/lib/common.bash index bc2b4e6d..ab7d5963 100644 --- a/test/lib/common.bash +++

[arch-projects] [dbscripts] [PATCH v2 2/2] Add reproducible archive of packages.

2019-01-08 Thread Eli Schwartz via arch-projects
Whenever adding new package files to the pool of distributed packages, copy the file into a longterm archive. This is the first step to merging the functionality of archivetools, as this implements the shared pool while also guaranteeing that all packages are archived at the time of entry rather

[arch-projects] [dbscripts] [GIT] Official repo DB scripts branch master updated. 20180603-14-gf11a038

2019-01-10 Thread Eli Schwartz via arch-projects
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Official repo DB scripts". The branch, master has been updated via f11a038c43270a70eafdba34ff33e134b6726a04 (commit) via

[arch-projects] [dbscripts] [GIT] Official repo DB scripts branch verify-update-plus-rebuild created. 20180603-17-g77c7269

2019-01-10 Thread Eli Schwartz via arch-projects
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Official repo DB scripts". The branch, verify-update-plus-rebuild has been created at 77c72694e608decd63978f3ae6d941487476ef98

[arch-projects] [dbscripts] [GIT] Official repo DB scripts branch master updated. 20180603-15-g948a181

2019-01-10 Thread Eli Schwartz via arch-projects
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Official repo DB scripts". The branch, master has been updated via 948a181f5f09ca1cc03d450081f296222ca26d2f (commit) from

[arch-projects] [dbscripts] [PATCH] Fix db-archive not running at the correct time.

2019-01-10 Thread Eli Schwartz via arch-projects
At the point when it was being run, the signature was not yet moved to PKGPOOL. Signed-off-by: Eli Schwartz --- Discovered while debugging the verify branch. db-update | 2 +- test/cases/db-update.bats | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) diff --git

[arch-projects] [dbscripts] [PATCH v2 2/3] db-update: die when trying to update a package without updating a pending rebuild

2019-01-10 Thread Eli Schwartz via arch-projects
A semi-common pattern is for one maintainer to stage a rebuild of a package due to e.g. cascading repository-wide python/boost/whatever rebuilds, and then for the original maintainer of the package to not notice and update the package in the stable repo, leaving an out of date rebuild in staging

[arch-projects] [dbscripts] [GIT] Official repo DB scripts branch master updated. 20180603-18-gd5970df

2019-01-11 Thread Eli Schwartz via arch-projects
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Official repo DB scripts". The branch, master has been updated via d5970df3a7051b7ceb5d69a345c763e9b5ed8052 (commit) via

Re: [arch-projects] [dbscripts] Accidentally all the tags (was: [GIT] Official repo DB scripts annotated tag 20190111 created. 20190111)

2019-01-11 Thread Eli Schwartz via arch-projects
Oops, I have sent a raft of faulty tags in addition by accident that I once git fetched from a fork. :( Please either ignore or give me permission to backdoor your email provider and delete the spam for you. -- Eli Schwartz Bug Wrangler and Trusted User signature.asc Description: OpenPGP

[arch-projects] [dbscripts] [GIT] Official repo DB scripts tag parabola/20171111 created. 20111105-451-ge397326

2019-01-11 Thread Eli Schwartz via arch-projects
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Official repo DB scripts". The tag, parabola/2017 has been created at e3973262cca737d8c174b6292f64de6b1baeb6e6 (commit) - Log

[arch-projects] [dbscripts] [GIT] Official repo DB scripts tag parabola/20180610 created. 20111105-625-g9233d18

2019-01-11 Thread Eli Schwartz via arch-projects
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Official repo DB scripts". The tag, parabola/20180610 has been created at 9233d18f7487c2d2b969a4b72ae9976f1dc757cd (commit) - Log

[arch-projects] [dbscripts] [GIT] Official repo DB scripts tag parabola/20180507 created. 20111105-579-gfef7b4f

2019-01-11 Thread Eli Schwartz via arch-projects
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Official repo DB scripts". The tag, parabola/20180507 has been created at fef7b4f6e946d50fcc37a5b8a795ba1ee6a2cfc6 (commit) - Log

[arch-projects] [dbscripts] [GIT] Official repo DB scripts annotated tag lukeshu/to-upstream/2018-03-16-archlinux+cleanup-v7 created. lukeshu/to-upstream/2018-03-16-archlinux+cleanup-v7

2019-01-11 Thread Eli Schwartz via arch-projects
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Official repo DB scripts". The annotated tag, lukeshu/to-upstream/2018-03-16-archlinux+cleanup-v7 has been created at

[arch-projects] [dbscripts] [GIT] Official repo DB scripts annotated tag lukeshu/to-upstream/2018-03-15-archlinux+cleanup-v4 created. lukeshu/to-upstream/2018-03-15-archlinux+cleanup-v4

2019-01-11 Thread Eli Schwartz via arch-projects
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Official repo DB scripts". The annotated tag, lukeshu/to-upstream/2018-03-15-archlinux+cleanup-v4 has been created at

[arch-projects] [dbscripts] [GIT] Official repo DB scripts tag lukeshu/to-upstream/2018-03-21-archlinux+cleanup-v9 created. 20131102-85-g5a6c4dd

2019-01-11 Thread Eli Schwartz via arch-projects
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Official repo DB scripts". The tag, lukeshu/to-upstream/2018-03-21-archlinux+cleanup-v9 has been created at

[arch-projects] [dbscripts] [GIT] Official repo DB scripts tag parabola/20180611 created. 20111105-651-g12dfdd5

2019-01-11 Thread Eli Schwartz via arch-projects
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Official repo DB scripts". The tag, parabola/20180611 has been created at 12dfdd5944ae78ff4dd6cbe0cd96a09a0d99f595 (commit) - Log

[arch-projects] [dbscripts] [GIT] Official repo DB scripts tag parabola/20180429 created. 20111105-543-gb27f6fd

2019-01-11 Thread Eli Schwartz via arch-projects
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Official repo DB scripts". The tag, parabola/20180429 has been created at b27f6fdadee4227ab32b8bf34fe609e5b44fdc35 (commit) - Log

[arch-projects] [dbscripts] [GIT] Official repo DB scripts tag parabola/20180612 created. 20111105-654-g77b61a2

2019-01-11 Thread Eli Schwartz via arch-projects
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Official repo DB scripts". The tag, parabola/20180612 has been created at 77b61a24ab1e71f65215c968ba7b118b6ac5e10a (commit) - Log

[arch-projects] [dbscripts] [GIT] Official repo DB scripts tag parabola/20170610.3 created. 20111105-442-gfcb893a

2019-01-11 Thread Eli Schwartz via arch-projects
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Official repo DB scripts". The tag, parabola/20170610.3 has been created at fcb893a28265fb9e815b88012c3f2a7d940e3888 (commit) -

[arch-projects] [dbscripts] [GIT] Official repo DB scripts tag parabola/20180507.1 created. 20111105-583-ga9f1927

2019-01-11 Thread Eli Schwartz via arch-projects
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Official repo DB scripts". The tag, parabola/20180507.1 has been created at a9f1927584a312900e7db29cee7daa548301ec9f (commit) -

[arch-projects] [dbscripts] [GIT] Official repo DB scripts tag parabola/20170120.2 created. 20111105-432-g99ff674

2019-01-11 Thread Eli Schwartz via arch-projects
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Official repo DB scripts". The tag, parabola/20170120.2 has been created at 99ff674ad4206e2e140ec4e1cc6caa7f535b8803 (commit) -

[arch-projects] [dbscripts] [GIT] Official repo DB scripts tag lukeshu/2011-dbscripts-repo-maintainer-merge created. 20101209-99-g7203e2e

2019-01-11 Thread Eli Schwartz via arch-projects
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Official repo DB scripts". The tag, lukeshu/2011-dbscripts-repo-maintainer-merge has been created at

[arch-projects] [dbscripts] [GIT] Official repo DB scripts tag lukeshu/to-upstream/2018-04-02-archlinux+cleanup-v10 created. 20131102-87-geb09efd

2019-01-11 Thread Eli Schwartz via arch-projects
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Official repo DB scripts". The tag, lukeshu/to-upstream/2018-04-02-archlinux+cleanup-v10 has been created at

[arch-projects] [dbscripts] [GIT] Official repo DB scripts tag parabola/20170610.1 created. 20111105-441-g961f0c5

2019-01-11 Thread Eli Schwartz via arch-projects
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Official repo DB scripts". The tag, parabola/20170610.1 has been created at 961f0c5355e12120955d3dec08162237e5096c2b (commit) -

[arch-projects] [dbscripts] [GIT] Official repo DB scripts tag parabola/20170527.1 created. 20111105-438-g54ce226

2019-01-11 Thread Eli Schwartz via arch-projects
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Official repo DB scripts". The tag, parabola/20170527.1 has been created at 54ce226dc304ed13befb747edc329d09467b8cbd (commit) -

[arch-projects] [dbscripts] [GIT] Official repo DB scripts tag parabola/20170214 created. 20111105-432-g99ff674

2019-01-11 Thread Eli Schwartz via arch-projects
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Official repo DB scripts". The tag, parabola/20170214 has been created at 99ff674ad4206e2e140ec4e1cc6caa7f535b8803 (commit) - Log

[arch-projects] [dbscripts] [GIT] Official repo DB scripts tag parabola/20180425 created. 20111105-540-g3867f04

2019-01-11 Thread Eli Schwartz via arch-projects
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Official repo DB scripts". The tag, parabola/20180425 has been created at 3867f0435b2d98278657fc47558ff44c9f554247 (commit) - Log

[arch-projects] [dbscripts] [GIT] Official repo DB scripts tag parabola/20180505 created. 20111105-572-g8393137

2019-01-11 Thread Eli Schwartz via arch-projects
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Official repo DB scripts". The tag, parabola/20180505 has been created at 8393137cd49de14f0f74caee8e93fa43ca881e2b (commit) - Log

[arch-projects] [dbscripts] [GIT] Official repo DB scripts tag parabola/20160708 created. 20111105-414-g7035711

2019-01-11 Thread Eli Schwartz via arch-projects
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Official repo DB scripts". The tag, parabola/20160708 has been created at 70357110197aa7e954bd50593c36721f4d547911 (commit) - Log

[arch-projects] [dbscripts] [GIT] Official repo DB scripts tag parabola/20170120.1 created. 20111105-430-gde9f3ba

2019-01-11 Thread Eli Schwartz via arch-projects
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Official repo DB scripts". The tag, parabola/20170120.1 has been created at de9f3bae65a3c488a11a998fa177921ed4cab339 (commit) -

[arch-projects] [dbscripts] [GIT] Official repo DB scripts tag parabola/20170214.1 created. 20111105-434-g92583e5

2019-01-11 Thread Eli Schwartz via arch-projects
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Official repo DB scripts". The tag, parabola/20170214.1 has been created at 92583e52b6b785b0c5c740948cb09738f3027275 (commit) -

[arch-projects] [dbscripts] [GIT] Official repo DB scripts tag parabola/20180429.1 created. 20111105-548-gffb88bb

2019-01-11 Thread Eli Schwartz via arch-projects
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Official repo DB scripts". The tag, parabola/20180429.1 has been created at ffb88bb9082b68ec928811d05c76bcab8431a37b (commit) -

[arch-projects] [dbscripts] [GIT] Official repo DB scripts tag parabola/20180401 created. 20111105-479-gffedeab

2019-01-11 Thread Eli Schwartz via arch-projects
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Official repo DB scripts". The tag, parabola/20180401 has been created at ffedeab545c1c4f45f315adbdc7a42dea707f455 (commit) - Log

[arch-projects] [dbscripts] [GIT] Official repo DB scripts tag parabola/20180502.2 created. 20111105-564-g1a3f628

2019-01-11 Thread Eli Schwartz via arch-projects
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Official repo DB scripts". The tag, parabola/20180502.2 has been created at 1a3f6289ccfbb15cd8e8c3d28a8ee198fa477a30 (commit) -

[arch-projects] [dbscripts] [GIT] Official repo DB scripts tag parabola/20180326 created. 20111105-478-g4075f9e

2019-01-11 Thread Eli Schwartz via arch-projects
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Official repo DB scripts". The tag, parabola/20180326 has been created at 4075f9ed3631ac04042678ffeffa74e166d12b15 (commit) - Log

[arch-projects] [dbscripts] [GIT] Official repo DB scripts annotated tag lukeshu/to-upstream/2018-03-14-archlinux+cleanup-v3 created. lukeshu/to-upstream/2018-03-14-archlinux+cleanup-v3

2019-01-11 Thread Eli Schwartz via arch-projects
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Official repo DB scripts". The annotated tag, lukeshu/to-upstream/2018-03-14-archlinux+cleanup-v3 has been created at

[arch-projects] [dbscripts] [GIT] Official repo DB scripts annotated tag 20190111 created. 20190111

2019-01-11 Thread Eli Schwartz via arch-projects
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Official repo DB scripts". The annotated tag, 20190111 has been created at 9e45ae4063267eb123b8cae625a3afdcfde52329 (tag)

[arch-projects] [dbscripts] [GIT] Official repo DB scripts tag parabola/20170120 created. 20111105-429-g973daf0

2019-01-11 Thread Eli Schwartz via arch-projects
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Official repo DB scripts". The tag, parabola/20170120 has been created at 973daf0b56132ff451913fc127521ab5fcd5d033 (commit) - Log

[arch-projects] [dbscripts] [GIT] Official repo DB scripts annotated tag lukeshu/to-upstream/2018-03-14-archlinux+cleanup-v2 created. lukeshu/to-upstream/2018-03-14-archlinux+cleanup-v2

2019-01-11 Thread Eli Schwartz via arch-projects
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Official repo DB scripts". The annotated tag, lukeshu/to-upstream/2018-03-14-archlinux+cleanup-v2 has been created at

[arch-projects] [dbscripts] [GIT] Official repo DB scripts annotated tag 20190111-2 created. 20190111-2

2019-01-11 Thread Eli Schwartz via arch-projects
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Official repo DB scripts". The annotated tag, 20190111-2 has been created at 5bfe163783afeb315c64411a4649e808eda93bfa (tag)

[arch-projects] [dbscripts] [GIT] Official repo DB scripts branch master updated. 20190111-2

2019-01-11 Thread Eli Schwartz via arch-projects
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Official repo DB scripts". The branch, master has been updated via 70adbd1a69636c0524003a684c69af0f23b54539 (commit) from

[arch-projects] [dbscripts] [GIT] Official repo DB scripts annotated tag 20190111-2 created. 20190111-2

2019-01-11 Thread Eli Schwartz via arch-projects
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Official repo DB scripts". The annotated tag, 20190111-2 has been created at dcb4f00944c0911c8e9f2163828a4ebc78037aea (tag)

[arch-projects] [dbscripts] [GIT] Official repo DB scripts branch master updated. 20190111-2-1-g7a173f8

2019-01-11 Thread Eli Schwartz via arch-projects
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Official repo DB scripts". The branch, master has been updated via 7a173f8298f915050778999ec8eef1322dfc0d97 (commit) from

[arch-projects] [dbscripts] [GIT] Official repo DB scripts annotated tag 20190111-2 deleted. 20190111-1-g70adbd1

2019-01-11 Thread Eli Schwartz via arch-projects
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Official repo DB scripts". The annotated tag, 20190111-2 has been deleted was 5bfe163783afeb315c64411a4649e808eda93bfa - Log

[arch-projects] [dbscripts] [GIT] Official repo DB scripts annotated tag 20190113 created. 20190113

2019-01-13 Thread Eli Schwartz via arch-projects
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Official repo DB scripts". The annotated tag, 20190113 has been created at 7aa40fa976c8f51c03095619782a905e992f1157 (tag)

[arch-projects] [dbscripts] [PATCH] Handle split packages properly in staging repos check.

2019-01-13 Thread Eli Schwartz via arch-projects
This needs to check the pkgbase, not the pkgname, as for split packages we need to lookup a PKGBUILD using the basename. Signed-off-by: Eli Schwartz --- db-functions | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/db-functions b/db-functions index 5c363578..65e7700f

Re: [arch-projects] [dbscripts] [PATCH v2 2/2] Add reproducible archive of packages.

2019-01-09 Thread Eli Schwartz via arch-projects
On 1/9/19 8:00 AM, Florian Pritz wrote: > On Tue, Jan 08, 2019 at 06:40:37PM -0500, Eli Schwartz via arch-projects > wrote: >> diff --git a/db-archive b/db-archive >> new file mode 100755 >> index ..5680b9de >> --- /dev/null >> +++ b/db-archive

Re: [arch-projects] [dbscripts] [PATCH v2 2/2] Add reproducible archive of packages.

2019-01-09 Thread Eli Schwartz via arch-projects
On 1/9/19 10:34 AM, Florian Pritz wrote: > On Wed, Jan 09, 2019 at 09:49:26AM -0500, Eli Schwartz via arch-projects > wrote: >>>> diff --git a/db-functions b/db-functions >>>> index 7aeedced..b8a00b90 100644 >>>> --- a/db-functions >

[arch-projects] [dbscripts] [PATCH v3 2/2] Add reproducible archive of packages.

2019-01-09 Thread Eli Schwartz via arch-projects
Whenever adding new package files to the pool of distributed packages, copy the file into a longterm archive. This is the first step to merging the functionality of archivetools, as this implements the shared pool while also guaranteeing that all packages are archived at the time of entry rather

Re: [arch-projects] [namcap] [PATCH] namcap-tags: Add back missing dependency reason tags (FS#56898)

2018-12-02 Thread Eli Schwartz via arch-projects
On 12/2/18 1:33 PM, Michael Straube via arch-projects wrote: > There are two missing tags that are needed in rules added (back) in > commit e385ac93a354 (Restore and refactor accidentally removed tests). > Add back the missing tags. > > Signed-off-by: Michael Straube > --- > namcap-tags | 2 ++

[arch-projects] [netctl] [PATCH] Makefile: specify the correct shell to use

2019-01-26 Thread Eli Schwartz via arch-projects
The Makefile commands in use include bash-specific features like brace expansion, and thus cannot run under the default /bin/sh shell as that may or may not be GNU bash (bash supports brace expansion even in posix mode). Consequently, the Makefile failed to execute correctly when the system

[arch-projects] [devtools] [PATCH 2/3] add sogrep command

2019-03-25 Thread Eli Schwartz via arch-projects
This is the new and improved, canonical sogrep command, now with a valid license. The previous version of sogrep had several issues and inefficiencies, and ultimately wasn't really the finished project I wanted it to be. Due to a mistake in communication, I was totally unaware it was in the

[arch-projects] [devtools] [PATCH 1/3] sogrep: don't be templated when it is not templated

2019-03-25 Thread Eli Schwartz via arch-projects
Partition the Makefile targets to only clean configured files, and make the configured files be a subset of the bin programs. Signed-off-by: Eli Schwartz --- .gitignore | 1 - Makefile| 9 ++--- sogrep.in => sogrep | 0 3 files changed, 6 insertions(+), 4 deletions(-)

[arch-projects] [devtools] [PATCH 3/3] fix up sogrep manpage to correspond with current sogrep command

2019-03-25 Thread Eli Schwartz via arch-projects
Signed-off-by: Eli Schwartz --- doc/sogrep.1.asciidoc | 10 -- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/doc/sogrep.1.asciidoc b/doc/sogrep.1.asciidoc index bc8f6ce..037773a 100644 --- a/doc/sogrep.1.asciidoc +++ b/doc/sogrep.1.asciidoc @@ -3,7 +3,7 @@ sogrep(1)

Re: [arch-projects] [netctl] Extended testing for 1.20

2019-02-26 Thread Eli Schwartz via arch-projects
On 2/26/19 11:07 AM, Jouke Witteveen via arch-projects wrote: > On Tue, Feb 12, 2019 at 10:39 PM Florian Pritz wrote: >> >> On Tue, Feb 12, 2019 at 05:20:13PM +0100, Jouke Witteveen >> wrote: >>> I just tagged 1.20, which switches from using wpa_actiond to using wpa_cli. >>> Let's keep this in

Re: [arch-projects] [PATCH] [devtools] makechrootpkg: load COMPRESS* vars from makepkg.conf

2019-03-18 Thread Eli Schwartz via arch-projects
On 3/18/19 5:56 AM, Maxim Baz via arch-projects wrote: > I did see an earlier patch proposing the same, which was rejected because it > might break delta packages [1]. > However, someone mentioned that pacman is dropping support for delta packages > altogether [2] referring to a removal commit

Re: [arch-projects] [devtools] uses MAKEFLAGS (+others) from /etc/makepkg.conf not /usr/share/devtools/

2019-02-07 Thread Eli Schwartz via arch-projects
On 2/7/19 6:14 AM, james harvey via arch-projects wrote: > I got extremely confused when I accidentally found out that the > MAKEFLAGS that is needed to be set for parallel building using > devtools is the one in "/etc/makepkg.conf", instead of one like > "/usr/share/devtools/makepkg-x86_64.conf".

Re: [arch-projects] [devtools] conf files could be closer to pacman's

2019-02-07 Thread Eli Schwartz via arch-projects
On 2/7/19 6:17 AM, james harvey via arch-projects wrote: > It could be worth a developer diff'ing: > * pacman::makepkg.conf and devtools::makepkg-x86_64.conf > * pacman::pacman.conf and devtools::pacman*.conf > > When trying to figure out my /etc/ vs /usr/share/devtools/ confusion > with

Re: [arch-projects] [devtools] uses MAKEFLAGS (+others) from /etc/makepkg.conf not /usr/share/devtools/

2019-02-07 Thread Eli Schwartz via arch-projects
On 2/7/19 8:00 PM, james harvey via arch-projects wrote: > I guess I'm abusing devtools a bit, as a few others are. I use > devtools to build modified official packages when necessary, and to > build AUR packages even if they depend on other AUR packages. I add a > local repository to

Re: [arch-projects] [devtools] [PATCH] mkarchroot: use pacman-conf for obtaining CacheDir

2019-02-19 Thread Eli Schwartz via arch-projects
On 2/19/19 2:54 PM, Jelle van der Waa wrote: > Instead of using sed/grep and relying on the output of 'pacman -v' use > pacman-conf for obtaining the configuration value of the CacheDir. Misses the same change in arch-nspawn, see for example

[arch-projects] [namcap] [PATCH] remove pointless mkdir -p in parsepkgbuild

2019-04-10 Thread Eli Schwartz via arch-projects
As far as I can tell, this was never used. In commit 9b56647abc8dc33bf138d4b260b103c8d9265b7d the parsepkgbuild script was switched from defining a PATH as a directory in /tmp, to actually passing in a PATH=/dummy to `env -i`... which makes sense as the defined PATH did not used to be used.

[arch-projects] [namcap] [PATCH] Add rule to report on unneeded dependencies from hooks

2019-04-10 Thread Eli Schwartz via arch-projects
Just as it is unnecessary to run certain commands in a post_upgrade script, if a hook already runs it, so too is it usually unnecessary to depend on the package that installs the hook. Sometimes these dependencies are left in even when the install script is removed, because people lack

[arch-projects] [namcap] [PATCH] Remove no longer useful warnings that have missing keys

2019-04-10 Thread Eli Schwartz via arch-projects
Arch Linux now has pacman hooks that provide automatic handling for update-{desktop,mime}-database without each package requiring a hard dependency and a post_upgrade hook. This means it is no longer correct to depend on the packages or provide an install script. Instead, remove this entirely.

[arch-projects] [namcap] [PATCH 2/2] add support for new checksum algorithm in pacman-git

2019-04-10 Thread Eli Schwartz via arch-projects
It is now possible to use b2sums to verify file integrity. See https://git.archlinux.org/pacman.git/commit/?id=e03752e6adc86cbb4cb4f52a38f6e3e98cbe9dd5 Signed-off-by: Eli Schwartz --- Namcap/rules/arrays.py | 9 + Namcap/rules/extravars.py | 9 +

[arch-projects] [namcap] [PATCH 1/2] parsepkgbuild: reduce a lot of boilerplate by being more templated

2019-04-10 Thread Eli Schwartz via arch-projects
When listing out the contents of a variable, use loops and references to the variables in order to reduce code and make it easier to extend. In the future, a new metadata type can be added simply by appending to meta_keys=() Signed-off-by: Eli Schwartz --- parsepkgbuild.sh | 127

Re: [arch-projects] [namcap] [PATCH] Remove no longer useful warnings that have missing keys

2019-04-10 Thread Eli Schwartz via arch-projects
On 4/10/19 9:15 PM, Eli Schwartz wrote: > Arch Linux now has pacman hooks that provide automatic handling for > update-{desktop,mime}-database without each package requiring a hard > dependency and a post_upgrade hook. This means it is no longer correct > to depend on the packages or provide an

[arch-projects] [devtools] [PATCH] Add new tool: offload-build

2019-04-14 Thread Eli Schwartz via arch-projects
This tool is useful for running makechrootpkg on a remote build server, and is by default hooked up to send a PKGBUILD and initiate a build on our shiny new build server "dragon". Signed-off-by: Eli Schwartz --- manpage documentation hopefully coming tonight. Makefile | 1 +

[arch-projects] [devtools] [PATCH] doc: add manpage for the new offload-build tool

2019-04-14 Thread Eli Schwartz via arch-projects
Signed-off-by: Eli Schwartz --- Makefile | 1 + doc/offload-build.1.asciidoc | 38 2 files changed, 39 insertions(+) create mode 100644 doc/offload-build.1.asciidoc diff --git a/Makefile b/Makefile index 2306a17..27cd90f 100644 ---

[arch-projects] [devtools] [PATCH v2] Add new tool: offload-build

2019-04-17 Thread Eli Schwartz via arch-projects
This tool is useful for running makechrootpkg on a remote build server, and is by default hooked up to send a PKGBUILD and initiate a build on our shiny new build server "dragon". Signed-off-by: Eli Schwartz --- v2: script -qfc does not preserve the exit status of the wrapped command. Add -e so

Re: [arch-projects] [namcap] [PATCH 3/4] nonuniquesources: Also warn on common filenames not overriding name to be unique

2019-05-26 Thread Eli Schwartz via arch-projects
On 5/26/19 10:35 PM, James Harvey via arch-projects wrote: > Filenames in source() are required to be unique. A common violation of > this is from commonly named files (i.e. LICENSE) that aren't part of an > upstream tarball. > > Warn if a source file doesn't have an overriding name, and has a >

Re: [arch-projects] [namcap] [PATCH 0/4] Add a rule against common filenames in source() without overridden name

2019-05-26 Thread Eli Schwartz via arch-projects
On 5/26/19 10:35 PM, James Harvey via arch-projects wrote: > There's no good way for namcap to ensure source() filenames are unique > across all packages, required for users with SRCDEST. But, I think by > far the most common offending filename would be LICENSE, as > non-standard ones are

[arch-projects] [devtools] [PATCH v3 1/2] Add new tool: offload-build

2019-06-04 Thread Eli Schwartz via arch-projects
This tool is useful for running makechrootpkg on a remote build server, and is by default hooked up to send a PKGBUILD and initiate a build on our shiny new build server "dragon". Signed-off-by: Eli Schwartz --- v3: Add passthrough of archbuild options as requested by anthraxx. Makefile

[arch-projects] [devtools] [PATCH v3 2/2] doc: add manpage for the new offload-build tool

2019-06-04 Thread Eli Schwartz via arch-projects
Signed-off-by: Eli Schwartz --- v3: update manpage for new v3 parameters. Makefile | 1 + doc/offload-build.1.asciidoc | 52 2 files changed, 53 insertions(+) create mode 100644 doc/offload-build.1.asciidoc diff --git a/Makefile

[arch-projects] [devtools] [PATCH] Revert "makechrootpkg: sync_chroot: Make more general."

2019-05-09 Thread Eli Schwartz via arch-projects
This reverts commit 6d1992909cc46e293027ff488ae2632047603e66. It has never worked. In commit c86823a2d4a4152c71faa1c3bab227756232996f it was noted that it compared the device numbers for [[ $1 = $1 ]] which was a useless check and always returned true, for *any* btrfs filesystem. Now that the

<    1   2   3   >