~ddevault

Philadelphia, PA

https://drewdevault.com

Maintainer of sourcehut upstream, and Alpine Linux contributor.

Recent activity

[PATCH] main/samurai: upgrade to 1.1 a day ago

From Drew DeVault to ~alpine/aports

---
 ...uild-when-it-was-pruned-due-to-resta.patch |  86 --------
 ...eck-that-rules-always-have-a-command.patch |  54 -----
 ...-rules-have-rspfile-iff-they-have-rs.patch |  56 -----
 main/samurai/0004-tool-Implement-compdb.patch | 197 ------------------
 ...issing-depfile-as-empty-for-deps-log.patch |  64 ------
 main/samurai/APKBUILD                         |  18 +-
 6 files changed, 4 insertions(+), 471 deletions(-)
 delete mode 100644 main/samurai/0001-Fix-manifest-rebuild-when-it-was-pruned-due-to-resta.patch
 delete mode 100644 main/samurai/0002-parse-Check-that-rules-always-have-a-command.patch
 delete mode 100644 main/samurai/0003-parse-Check-that-rules-have-rspfile-iff-they-have-rs.patch
 delete mode 100644 main/samurai/0004-tool-Implement-compdb.patch
 delete mode 100644 main/samurai/0005-deps-treat-missing-depfile-as-empty-for-deps-log.patch
[message trimmed]

[PATCH] community/alacritty: upgrade to 0.4.2 a day ago

From Drew DeVault to ~alpine/aports

---
 community/alacritty/APKBUILD | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/community/alacritty/APKBUILD b/community/alacritty/APKBUILD
index da61640b33..f03bf1d1da 100644
--- a/community/alacritty/APKBUILD
+++ b/community/alacritty/APKBUILD
@@ -1,7 +1,7 @@
# Maintainer: Drew DeVault <sir@cmpwn.com>
pkgname=alacritty
pkgver=0.4.1
pkgrel=2
pkgver=0.4.2
[message trimmed]

[PATCH] community/py3-tqdm: upgrade to 4.44.1 2 days ago

From Drew DeVault to ~alpine/aports

---
 community/py3-tqdm/APKBUILD | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/community/py3-tqdm/APKBUILD b/community/py3-tqdm/APKBUILD
index 7a72d74cce..a3561a5dc5 100644
--- a/community/py3-tqdm/APKBUILD
+++ b/community/py3-tqdm/APKBUILD
@@ -1,7 +1,7 @@
# Maintainer: Drew DeVault <sir@cmpwn.com>
pkgname=py3-tqdm
_pkgname=tqdm
pkgver=4.44.0
pkgver=4.44.1
[message trimmed]

[PATCH] community/py3-tqdm: upgrade to 4.44.0 2 days ago

From Drew DeVault to ~alpine/aports

---
 community/py3-tqdm/APKBUILD | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/community/py3-tqdm/APKBUILD b/community/py3-tqdm/APKBUILD
index 27859731b9..7a72d74cce 100644
--- a/community/py3-tqdm/APKBUILD
+++ b/community/py3-tqdm/APKBUILD
@@ -1,7 +1,7 @@
# Maintainer: Drew DeVault <sir@cmpwn.com>
pkgname=py3-tqdm
_pkgname=tqdm
pkgver=4.43.0
pkgver=4.44.0
[message trimmed]

[PATCH] community/prometheus: upgrade to 2.17.1 5 days ago

From Drew DeVault to ~alpine/aports

---
 community/prometheus/APKBUILD | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/community/prometheus/APKBUILD b/community/prometheus/APKBUILD
index c602a66697..699e65c8d9 100644
--- a/community/prometheus/APKBUILD
+++ b/community/prometheus/APKBUILD
@@ -1,6 +1,6 @@
# Maintainer: Drew DeVault <sir@cmpwn.com>
pkgname=prometheus
pkgver=2.17.0
pkgver=2.17.1
pkgrel=0
[message trimmed]

[PATCH] community/prometheus: upgrade to 2.17.0 6 days ago

From Drew DeVault to ~alpine/aports

---
 community/prometheus/APKBUILD | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/community/prometheus/APKBUILD b/community/prometheus/APKBUILD
index c20b886fe2..c602a66697 100644
--- a/community/prometheus/APKBUILD
+++ b/community/prometheus/APKBUILD
@@ -1,6 +1,6 @@
# Maintainer: Drew DeVault <sir@cmpwn.com>
pkgname=prometheus
pkgver=2.16.0
pkgver=2.17.0
pkgrel=0
[message trimmed]

Re: Does it make sense to keep ~alpine/aports running? 21 days ago

From Drew DeVault to ~alpine/devel

On Tue Mar 10, 2020 at 2:56 PM, Natanael Copa wrote:
> So while sending patches as emails is the easiest way for you, it
> certainly is not the easiest for everyone.

I never suggested dropping GitLab in favor of aports.

Re: Does it make sense to keep ~alpine/aports running? 25 days ago

From Drew DeVault to ~alpine/devel

On Fri Mar 6, 2020 at 12:35 PM, Ariadne Conill wrote:
> A key point here that others have not raised is that this would require
> either moving the gitlab CI to use builds.sr.ht or maintaining two sets
> of CI. I doubt either is truly worth it, as the alternate CI is probably
> less featureful in gitlab.

The CI's are different and have different feature-sets. I am certain
that builds.sr.ht is perfectly suitable for aports CI.

Re: Does it make sense to keep ~alpine/aports running? 25 days ago

From Drew DeVault to ~alpine/devel

On Fri Mar 6, 2020 at 6:13 AM, Rasmus Thomsen wrote:
> * No CI. I see there's a todo for that in sr.ht and I don't mean to
> disrespect anyone's efforts - sr.ht is a lot better than other ML
> things for me already :), but we _still_ don't have CI on there, so I'm
> not exactly hopeful that we'll get it soon.

The ticket doesn't show much, but there has been consistent progress on
this for some time now. Here's the current workstream:

https://github.com/libgit2/pygit2/pull/982

Re: Does it make sense to keep ~alpine/aports running? 25 days ago

From Drew DeVault to ~alpine/devel

It takes me almost no time to send a patch to the mailing list, under 5
seconds every time. It's barely more work to send the patch than it is
to update a package in the first place. Updating it on GitLab
comparitively takes 5-10x longer - I have to make a branch, open my web
browser, log in, push the branch, back to the browser, click a bunch of
buttons... if the mailing lists are dropped then I'm probably going with
it as a contributor.