From: Morten Linderud
makechrootpkg checks the environment for multiple variables before
overwriting them with makepkg.conf configurations. Expand check_root
with the variables makechrootpkg check for so we are capable of
overwriting them when needed.
Signed-off-by: Morten Linderud
---
archbui
On 07/23/2018 06:15 PM, Morten Linderud via arch-projects wrote:
> From: Morten Linderud
>
> makechrootpkg checks the environment for multiple variables before
> overwriting them with makepkg.conf configurations. Expand check_root
> with the variables makechrootpkg check for so we
The .include directive in systemd unit files has effectively been
deprecated since systemd v210. Its functionality is subsumed by
drop-in directories.
---
src/netctl.in | 46 +++---
1 file changed, 23 insertions(+), 23 deletions(-)
diff --git a/src/netctl.i
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 "Network control utility based on systemd".
The branch, master has been updated
via e9c5de21c2d50c8fd8d1343feecb632bf836eec1 (commit)
Hello all,
I cannot send to arch-dev-public and don't know where to post this
otherwise, so I'll just put this out here.
With systemd 239, a deprecation message is printed in the journal for
enabled netctl profiles (FS#59494). This currently has no effect on
the functionality of either systemd or
On 08/03/2018 01:48 PM, Jouke Witteveen via arch-projects wrote:
> Hello all,
>
> I cannot send to arch-dev-public and don't know where to post this
> otherwise, so I'll just put this out here.
>
> With systemd 239, a deprecation message is printed in the journal f
On Fri, Aug 3, 2018 at 7:57 PM Eli Schwartz via arch-projects
wrote:
>
> On 08/03/2018 01:48 PM, Jouke Witteveen via arch-projects wrote:
> > Hello all,
> >
> > I cannot send to arch-dev-public and don't know where to post this
> > otherwise, so I'll just
On 08/03/2018 02:10 PM, Jouke Witteveen wrote:
> On Fri, Aug 3, 2018 at 7:57 PM Eli Schwartz via arch-projects
> wrote:
>>
>> On 08/03/2018 01:48 PM, Jouke Witteveen via arch-projects wrote:
>>> Hello all,
>>>
>>> I cannot send to arch-dev-public an
---
I am still a little hesitant to carry this in the netctl repository.
Currently, the repository is more or less distribution agnostic.
Makefile | 7 +--
contrib/PKGBUILD.in| 1 +
contrib/netctl.install | 10 ++
3 files changed, 16 insertions(+), 2 deletions(-)
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 "Network control utility based on systemd".
The branch, master has been updated
via 9044d45d9d25c585f666e51f47da5559b165c837 (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 "Network control utility based on systemd".
The annotated tag, 1.18 has been created
at 752de745e674cdb66b07a4d36a85188e689d8855 (ta
ing; there are no bugs in this software. But if we
> happen
> +to be wrong, send us an email with as much detail as possible to
> +arch-projects@archlinux.org
> +.Sh AUTHORS
> +.An Aaron Griffin
> +.An Pierre Schmitz
> +.An Lukas Fleischer
> +.An Luke Shumaker
> --
> 2.18.0
On 8/26/18 8:52 AM, Jelle van der Waa wrote:
> Updating the archweb database is now handled by archweb itself and
> deployed on the server using a systemd unit/service. These scripts are
> no longer used.
Since 2011 apparently?
https://github.com/archlinux/archweb/commit/2a2df0074e39a797a0a4b5f7db
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 c53352c103e023727ce31e98ca9647bb918a9a5d (commit)
from 089
From: anthraxx
bsdtar doesn't like it when the stream gets closed before it finishes
which may be the case when grep found its match on potentially huge
archives. Instead of suppressing the whole strerr , we just pipe
the output through cat which ensures the stream remains open for bsdtar
but we
From: anthraxx
The old travis-ci.org is deprecated and this project was migrated.
---
README.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/README.md b/README.md
index c672998..bdd958b 100644
--- a/README.md
+++ b/README.md
@@ -1,4 +1,4 @@
-# Arch Linux repository managem
From: anthraxx
The old travis-ci.org is deprecated and this project was migrated.
---
README.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/README.md b/README.md
index c672998..bdd958b 100644
--- a/README.md
+++ b/README.md
@@ -1,4 +1,4 @@
-# Arch Linux repository managem
On 9/3/18 7:50 AM, Levente Polyak via arch-projects wrote:
> From: anthraxx
>
> bsdtar doesn't like it when the stream gets closed before it finishes
> which may be the case when grep found its match on potentially huge
> archives. Instead of suppressing the whole strerr
On 9/9/18 11:20 AM, Eli Schwartz wrote:
> On 9/3/18 7:50 AM, Levente Polyak via arch-projects wrote:
>> From: anthraxx
>>
>> bsdtar doesn't like it when the stream gets closed before it finishes
>> which may be the case when grep found its match on potentia
On 9/9/18 12:20 PM, Eli Schwartz wrote:
> On 9/9/18 11:20 AM, Eli Schwartz wrote:
>> On 9/3/18 7:50 AM, Levente Polyak via arch-projects wrote:
>>> From: anthraxx
>>>
>>> bsdtar doesn't like it when the stream gets closed before it finishes
>>>
From: anthraxx
This silences a useless error message that confuses the user.
bsdtar doesn't like it when the stream gets closed before it finishes
which may be the case when grep found its match on potentially huge
archives. Instead of suppressing the whole stderr , we find all matches
with grep
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 0b630e25a3181d5228cbd99c9041a04b6514fc81 (commit)
via 57a
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 a75
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 6be28abc
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 9903f55e..f9
Signed-off-by: Eli Schwartz
---
db-functions-svn | 18 ++
db-move | 32 ++--
db-remove| 8
testing2x| 37 -
4 files changed, 48 insertions(+), 47 deletions(-)
diff --git a/db-functi
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 tha
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
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 "The official mkinitcpio repository".
The branch, master has been updated
via a3cb799a8f63186b843db6a57da12d74a9320686 (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 branch, master has been updated
via 61c9cc6f44e654a90a12da11be06e707e3f4b162 (commit)
via 13e
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 1bf
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 "The official mkinitcpio repository".
The annotated tag, 25 has been created
at c381320560a8ebc2b9b80d3686cb93e3dd067d62 (tag)
ta
For split pkgbuilds the pkgbase variable is optional. If not specified,
the first element in the pkgname array is used. Currently parsepkgbuild.sh
fails to detect split pkgbuilds if pkgbase is not specified. Therefore the
split pkgbuild rules are not applied to such pkgbuilds.
Instead of testing i
Add a rule that warns about make dependencies already listed as
dependencies.
Signed-off-by: Michael Straube
---
Namcap/rules/__init__.py| 1 +
Namcap/rules/makedepends.py | 41 +
namcap-tags | 1 +
3 files changed, 43 insertions(+)
crea
Signed-off-by: Michael Straube
---
Namcap/tests/pkgbuild/test_makedepends.py | 65 +++
1 file changed, 65 insertions(+)
create mode 100644 Namcap/tests/pkgbuild/test_makedepends.py
diff --git a/Namcap/tests/pkgbuild/test_makedepends.py
b/Namcap/tests/pkgbuild/test_makedepen
Signed-off-by: Michael Straube
---
.../tests/pkgbuild/test_makepkgfunctions.py | 67 +++
1 file changed, 67 insertions(+)
create mode 100644 Namcap/tests/pkgbuild/test_makepkgfunctions.py
diff --git a/Namcap/tests/pkgbuild/test_makepkgfunctions.py
b/Namcap/tests/pkgbuild/test
---
services/netctl-auto@.service| 3 ++-
services/netctl-ifplugd@.service | 3 ++-
2 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/services/netctl-auto@.service b/services/netctl-auto@.service
index 3e41744..aacf65c 100644
--- a/services/netctl-auto@.service
+++ b/services/netc
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 "Network control utility based on systemd".
The annotated tag, 1.19 has been created
at 3c62e2c301346e968113520d09d12d6fc50846f9 (ta
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 "Network control utility based on systemd".
The branch, master has been updated
via e0014041ad40c9385bb2c38aad2acae3c93eb512 (commit)
Signed-off-by: Michael Straube
---
Namcap/tests/package/test_systemdlocation.py | 85
1 file changed, 85 insertions(+)
create mode 100644 Namcap/tests/package/test_systemdlocation.py
diff --git a/Namcap/tests/package/test_systemdlocation.py
b/Namcap/tests/package/test_syst
Signed-off-by: Michael Straube
---
Namcap/rules/makedepends.py | 32 -
Namcap/tests/pkgbuild/test_makedepends.py | 44 ++-
namcap-tags | 1 +
3 files changed, 75 insertions(+), 2 deletions(-)
diff --git a/Namcap/rul
Add a rule that warns about make dependencies already listed as
dependencies.
Signed-off-by: Michael Straube
---
v1 -> v2
Added patch that implements FS#58303
Warn about missing VCS make dependencies.
Namcap/rules/__init__.py| 1 +
Namcap/rules/makedepends.py | 41 +
Signed-off-by: Michael Straube
---
Namcap/tests/pkgbuild/test_makedepends.py | 65 +++
1 file changed, 65 insertions(+)
create mode 100644 Namcap/tests/pkgbuild/test_makedepends.py
diff --git a/Namcap/tests/pkgbuild/test_makedepends.py
b/Namcap/tests/pkgbuild/test_makedepen
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 robust to avoid such issues.
Signed-off-by: Michael Straube
---
Perhaps
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
Am 02.12.18 um 06:04 schrieb 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 pro
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 robust to avoid such issues.
Signed-off-by: Michael Straube
---
v1 -> v
On 12/2/18 8:01 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
Am 02.12.18 um 14:14 schrieb Eli Schwartz via arch-projects:
On 12/2/18 8:01 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 pro
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 robust to avoid such issues.
Signed-off-by: Michael Straube
---
v1 -> v
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 ++
1 file changed, 2 insertions(+)
diff --git a/namcap-tags b/namcap-tags
ind
Don't allow anomalous testing packages floating around after a rebuild
which are older than stable.
Signed-off-by: Eli Schwartz
---
db-move | 9 +
test/cases/db-move.bats | 14 ++
test/lib/common.bash| 2 ++
3 files changed, 25 insertions(+)
diff --git
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 or
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 det
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
> ---
Am 02.12.18 um 20:34 schrieb 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
Hi,
namcap does not distinguish java class files from Mach-O files since
both use the same byte magic CAFEBABE. See FS#34300
Implementing this would only need a test if the value of the byte at
offset 7 is greater than 0x30.
See: https://github.com/file/file/blob/master/magic/Magdir/cafebabe
I
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 +
config.loca
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 i
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
+++ b/t
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
---
cron-jobs/ftpdir-cl
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 burde
On Tue, Dec 04, 2018 at 01:15:20PM -0500, 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
> > "reproducible" pool, and log which
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
>>> "repro
On Wed, Dec 05, 2018 at 10:49:44AM +0100, Florian Pritz via arch-devops
wrote:
> Also thinking about this, it would be great if we could skip the pkg
> symlinks for each day's archive and only copy the db itself. All we'd
> need is to have a dedicated PackageServer= setting (like Server=, but
> o
From: Morten Linderud
Les us source makepkg.conf settings from the environemnt. This also includes
`GNUPGHOME` which is present in `makechrootpkg`, but not included in archbuild.
Signed-off-by: Morten Linderud
---
archbuild.in | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a
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
+++ b/test/lib/common.ba
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 th
So I think the idea of replacing archivetools with a builtin archive
functionality has merit, especially if we can do it easily using nginx
rewrites. Hence I've rewritten this to put packages in longterm storage
in the archivetools "packages/" tree (which deprecates this aspect of
archivetools) usi
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
> @@ -0,0 +1,21 @@
> +#!/bin/bash
> +
> +. "$(dirname &quo
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
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
> >> +++ b/db-functions
> >> @@ -444,4 +447,24 @@
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
>
On Wed, Jan 09, 2019 at 10:45:12AM -0500, Eli Schwartz via arch-projects
wrote:
> >>>> diff --git a/db-update b/db-update
> >>>> index 313fb999..04a29bf3 100755
> >>>> --- a/db-update
> >>>> +++ b/db-update
> >>>> @@ -61,
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 th
On Wed, Jan 09, 2019 at 05:01:21PM -0500, Eli Schwartz via arch-projects
wrote:
> v3: string changes, consistently use BASH_SOURCE
Looks good to me. Thanks!
Florian
signature.asc
Description: PGP signature
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 490
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 (com
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 f11
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 a/db-upda
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 or
Don't allow anomalous testing packages floating around after a rebuild
which are older than stable.
Signed-off-by: Eli Schwartz
---
v2: fix incorrectly accessed array
db-move | 9 +
test/cases/db-move.bats | 14 ++
2 files changed, 23 insertions(+)
dif
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 880
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 34f15d3ebd76
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)
taggin
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
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-v6 has been
created
at 26c51bdf5084
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.1 has
been created
at 65a7fe54de
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 c6e8fb1ad110
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)
- Lo
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 7203e2e2631e29a79f4ea822c371d4
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 eb09efdc49aa9119e3b4e6
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
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
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 fae13e0b0057
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 9a93801b992c
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 5a6c4ddc76a47011386d6d1
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
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/20180501 has been created
at feecedde9164cbc40004fef18deca6ad598ecec5 (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 annotated tag, lukeshu/to-upstream/2018-03-15-archlinux+cleanup-v5 has been
created
at 844e74a2f34a
901 - 1000 of 1601 matches
Mail list logo
