Aside for comments, this implements the buildflags RFC from:
https://lists.archlinux.org/pipermail/arch-dev-public/2021-March/030374.html
https://gitlab.archlinux.org/archlinux/rfcs/-/merge_requests/3
Signed-off-by: Eli Schwartz
---
makepkg-x86_64.conf | 13 +
1 file changed, 9
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 03183d98275f685120b6a9aa2e766b4db933e2ad (commit)
from
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 67317c9180f062d243999467951a9b8a825501b8 (commit)
via
On 12/11/20 5:10 PM, meganomic via arch-projects wrote:
> I did a quick patch using your idea and it definitely seems like a
> good way to do it. Can probably clean it up and make it look prettier
> with some refactoring. I'll look into it later.
Nice, thanks!
Haven't taken more than a
On 12/11/20 2:25 PM, meganomic via arch-projects wrote:
Adds handling of the compression and temporary storage into namcap.py
so it can be removed from the bash script.
https://bugs.archlinux.org/task/59844 mentions "use setuptools entry
points." instead of the bash script but I don't know how
We now accept:
1) # nothing
in which case we'll use the PKGBUILD to retrieve...
2) name, or repo/name
in which case we'll use pacman to cache the package and retrieve...
3) a filename
Signed-off-by: Eli Schwartz
---
doc/makerepropkg.1.asciidoc | 11 +++-
makerepropkg.in
Hi all,
I'm one of the current maintainers of the Arch Linux dbscripts [1].
Unfortunately, it did not used to have a license, and to fix that, I
have agreed with Pierre Schmitz, Aaron Griffin, Judd Vinet, and Dan
McGee (who between us cover 581/715 of the commits in the repository) to
license it
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 eb1a090c5bfb9a1620abc21f8b81da510f965c4d (commit)
from
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 e7d06173a46eebad332805856e352531fc7b379b (commit)
from
Teach get_pkgfile to call itself in local-only mode and find a cached
file no matter what its extension is. Avoids repetitively trying to curl
random files, fail with 404 errors, and proceed to discover a cache hit
under a different file extension.
Signed-off-by: Eli Schwartz
---
This was incorrectly implemented in commit
00671765296ad598f392df7a542dbfca48a6e7b7, which added the host_mirrors
root directory as a cachedir, when we actually want to use the pool/*
subdirectories (the same ones installed on the build server's
/etc/pacman.conf).
Signed-off-by: Eli Schwartz
---
This was incorrectly implemented in commit
00671765296ad598f392df7a542dbfca48a6e7b7, which added the host_mirrors
root directory as a cachedir, when we actually want to use the pool/*
subdirectories (the same ones installed on the build server's
/etc/pacman.conf).
Signed-off-by: Eli Schwartz
---
On 1/17/20 8:19 AM, Vladimir Panteleev wrote:
> If the user has a non-canonical (i.e. symlinked on Arch) location in
> front of their $PATH, such as /usr/sbin, shutil.which will return
> locations with that path. This later causes the rule to fail to find
> the binary in any packages, causing
We don't want to check against the current version known to the host
system, because that will be incorrect in a wide variety of situations,
including:
- the build host hasn't done a full system upgrade yet
- we're building against staging, and want to see the delta between
different staging
Broken in commit c14338c0fe71a74f5e56b4f3af7c548fe0928e15.
Signed-off-by: Eli Schwartz
---
checkpkg.in | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/checkpkg.in b/checkpkg.in
index 374c004..d7c0948 100644
--- a/checkpkg.in
+++ b/checkpkg.in
@@ -95,8 +95,10 @@ for
Thanks to anthraxx for the guidance.
Original-patch-by: Levente Polyak
Signed-off-by: Eli Schwartz
---
zsh_completion.in | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/zsh_completion.in b/zsh_completion.in
index a1225aa..e59bc3a 100644
--- a/zsh_completion.in
+++
We don't want the default PKGEXT in the current version of devtools, we
want the PKGEXT we *know* the input file used.
Signed-off-by: Eli Schwartz
---
v2: use one less line when defining PKGEXT, as per anthraxx review
makerepropkg.in | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
We don't want the default PKGEXT in the current version of devtools, we
want the PKGEXT we *know* the input file used.
Signed-off-by: Eli Schwartz
---
makerepropkg.in | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/makerepropkg.in b/makerepropkg.in
index 51c2dd2..0721f65
On 12/19/19 6:49 PM, Levente Polyak via arch-projects wrote:
> You are u justified ranting here for a whole wall of text
And you are unjustified in ranting here for a single sentence about how
you're "not into fixing up the precious integrity of my precious that
you're ruining by submitting PRs".
On 12/19/19 5:02 PM, Levente Polyak via arch-projects wrote:
> Just replace the 1 with a asterisk * where I mentioned it.
>
> I'm not really into fixing up all commits people contribute to keep
> the integrity of completion that I once cleaned and synced to the
> current state.
I'm not really
On 12/16/19 3:55 PM, Levente Polyak via arch-projects wrote:
> Please adjust zsh_completions.in to take multiple packages in
> _makerepropkg_args
I'm not a zsh user, and I don't know what this means and therefore
cannot implement it. Maybe you could do it instead, since you're the one
who has
Available at
https://github.com/eli-schwartz/devtools/commits/makerepropkg-diffoscope
Eli Schwartz (3):
makerepropkg: fix wonky indent
makerepropkg: add support to check unreproducible packages using
diffoscope
makerepropkg: support checking multiple split packages
By specifying multiple package files, we assume they are all from the
same PKGBUILD, and try to check them all against the produced artifacts.
Since the buildinfo should be comparable for all of them, we simply use
the first one passed on the command line.
Signed-off-by: Eli Schwartz
---
Signed-off-by: Eli Schwartz
---
doc/makerepropkg.1.asciidoc | 3 +++
makerepropkg.in | 14 +++---
2 files changed, 14 insertions(+), 3 deletions(-)
diff --git a/doc/makerepropkg.1.asciidoc b/doc/makerepropkg.1.asciidoc
index 7d68e5e..301b73e 100644
---
Signed-off-by: Eli Schwartz
---
makerepropkg.in | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/makerepropkg.in b/makerepropkg.in
index 710f3ca..2b0945e 100755
--- a/makerepropkg.in
+++ b/makerepropkg.in
@@ -101,12 +101,12 @@ __EOF__
}
while getopts 'M:c:h'
This means that the remote command died at some stage earlier than the
printing of created files.
Signed-off-by: Eli Schwartz
---
offload-build | 2 ++
1 file changed, 2 insertions(+)
diff --git a/offload-build b/offload-build
index dab036d..e607a16 100755
--- a/offload-build
+++
On 11/30/19 7:31 AM, Levente Polyak via arch-projects wrote:
Generally some nice improvements, but what is the deal with this???
> commit 104c5bc90e259028f5c9352a32f8976aa0f95a8d
> Author: Levente Polyak
> Date: Sat Nov 30 13:13:49 2019 +0100
>
> makechrootpkg: sync database for checkpkg
This attempts to recreate a package that was probably created using
makechrootpkg, and see if it conforms to the
https://reproducible-builds.org/ specification.
Signed-off-by: Eli Schwartz
---
v3: make sure the pkgfile is actually a valid pkgfile
.gitignore | 1 +
Makefile| 1
This attempts to recreate a package that was probably created using
makechrootpkg, and see if it conforms to the
https://reproducible-builds.org/ specification.
Signed-off-by: Eli Schwartz
---
v2: add .gitignore bits
.gitignore | 1 +
Makefile| 1 +
makerepropkg.in | 186
This attempts to recreate a package that was probably created using
makechrootpkg, and see if it conforms to the
https://reproducible-builds.org/ specification.
Signed-off-by: Eli Schwartz
---
Makefile| 1 +
makerepropkg.in | 186
2
I've finally finished up this thing for testing if a package can be
rebuilt reproducibly. It uses makechrootpkg/mkarchroot under the hood,
and requires arch-install-scripts >= 23.
This, and other commits recently submitted to the list, can be pulled
directly from my repository at
Signed-off-by: Eli Schwartz
---
Makefile| 1 +
doc/makerepropkg.1.asciidoc | 38 +
2 files changed, 39 insertions(+)
create mode 100644 doc/makerepropkg.1.asciidoc
diff --git a/Makefile b/Makefile
index 090063d..4ca7155 100644
---
Needed to support reproducible builds.
Signed-off-by: Eli Schwartz
---
doc/mkarchroot.1.asciidoc | 3 +++
mkarchroot.in | 13 +
2 files changed, 12 insertions(+), 4 deletions(-)
diff --git a/doc/mkarchroot.1.asciidoc b/doc/mkarchroot.1.asciidoc
index 03d032c..eb0670a
Instead of comparing exact mirror urls to see if they are in
host_mirrors in order to "skip" the official mirrors, simply trim the
expected .../os/... pattern match. We already filter duplicate
cachedirs.
Signed-off-by: Eli Schwartz
---
I wasn't sure of the precise utility of this, but in
Signed-off-by: Eli Schwartz
---
Makefile | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/Makefile b/Makefile
index a8e44ee..0eb7a88 100644
--- a/Makefile
+++ b/Makefile
@@ -4,19 +4,19 @@ PREFIX = /usr/local
MANDIR = $(PREFIX)/share/man
IN_PROGS = \
-
In commit 27ff286ee78eb2faac803e3ef67f3171ddfa0098, we moved from
sourcing the primary cachedir via /etc/pacman.conf, to using the
pacman.conf in the workdir. One unanticipated side effect of this was
breaking the special host mirrors magic we used to turn a host mirror
into a cachedir. It was
- drop homebrew function in makechrootpkg
- use better mock to find invoking user's $HOME
- make offload-build respect makepkg.conf to determine where to sync
files, matching the behavior of makechrootpkg
Signed-off-by: Eli Schwartz
---
makechrootpkg.in | 34 ++
On 11/5/19 6:38 PM, Eli Schwartz wrote:
> I like color and feel comfortable using `less -R` to view logs.
>
> Signed-off-by: Eli Schwartz
> ---
> makepkg-x86_64.conf | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/makepkg-x86_64.conf b/makepkg-x86_64.conf
> index
consolidate logic flows in the same area for parsing and building
arrays. Don't bother having a special function just to build the
mount_args array, since we now use the same handling for adding any
cachedir (including host mirrors) to the mount arguments, this becomes a
trivial for loop -- and it
consolidate logic flows in the same area for parsing and building
arrays. Don't bother having a special function just to build the
mount_args array, since we now use the same handling for adding any
cachedir (including host mirrors) to the mount arguments, this becomes a
trivial for loop -- and it
Signed-off-by: Eli Schwartz
---
Makefile | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/Makefile b/Makefile
index a8e44ee..0eb7a88 100644
--- a/Makefile
+++ b/Makefile
@@ -4,19 +4,19 @@ PREFIX = /usr/local
MANDIR = $(PREFIX)/share/man
IN_PROGS = \
-
I like color and feel comfortable using `less -R` to view logs.
Signed-off-by: Eli Schwartz
---
makepkg-x86_64.conf | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/makepkg-x86_64.conf b/makepkg-x86_64.conf
index 137d412..7fc3611 100644
--- a/makepkg-x86_64.conf
+++
- drop homebrew function in makechrootpkg
- use better mock to find invoking user's $HOME
- make offload-build respect makepkg.conf to determine where to sync
files, matching the behavior of makechrootpkg
Signed-off-by: Eli Schwartz
---
makechrootpkg.in | 34 ++
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, 20191022 has been created
at ffca694fae377c6806ed2b194b38a78fcb071cc3 (tag)
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 ffae053006b2ecd53b028e26252b5b58e1f85d43 (commit)
from
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 60d036ead2565ea19e1c09f8b263cfe34918e2cf (commit)
from
On 9/17/19 9:30 AM, Daniel M. Capella via arch-projects wrote:
> Most of the time we're just bumping the pkgver and checksums, where a
> commit body isn't needed.
>
> Referencing commit ee970f0bde3c90a0dff909c366d4ab1a1bff9b9d
I religiously use the additional message "upstream release" in such
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
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
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
>
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
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
On 5/6/19 12:10 PM, Emil Velikov via arch-projects wrote:
> On Mon, 6 May 2019 at 15:10, Jelle van der Waa wrote:
>>
>> From: Jelle van der Waa
>>
>> finddeps depends on a no longer existing ABS tree. This data can also be
>> queried via archweb.
>> ---
> Out of curiosity:
> AFAICT all the
On 5/6/19 10:10 AM, Jelle van der Waa wrote:
> From: Jelle van der Waa
>
> finddeps depends on a no longer existing ABS tree.
finddeps does not depend on the discontinued `abs` tool. It does work
fine with an svn-packages/svn-community checkout, or via the svntogit
exported tree.
$ cd
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
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
---
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 +
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.
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 +
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
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
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 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.
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(-)
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
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)
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
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
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
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
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
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".
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
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
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
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,
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
>
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
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)
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
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
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)
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
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)
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
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
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
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)
-
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)
-
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
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
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)
-
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)
-
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
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)
-
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)
-
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
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
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
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)
-
1 - 100 of 249 matches
Mail list logo
