On Thu, Feb 2, 2023, at 4:35 AM, Magnus Viernickel wrote:
> Hi, I'm using sr.ht for a while now and I wanted to give some feedback 
> about the service:
> 
> - I do have some issues with builds:
>   - the containers are too small in many non-trivial cases: I'm using 
> nix to build most of my stuff and for most jobs the build already fails 
> when pulling cached derivations

Small in terms of disk space, I presume? Asking because I use Nix w/
caching and haven't had any issues

>   - the containers have very limited RAM: I am failing to e.g. build 
> haskell-language-server in the containers, if it's not cached, because 

Mar 6, 2022 7:21:19 PM terrydavis@cock.li:

> I’ve seen many code hosting services like Github and GitLab being very 
> vocal about the situation between Russia and Ukraine. Thankfully I’ve 
> not seen Sourcehut say anything about this, and I like this fact very 
> much. So will sourcehut still be apolitical in these subjects or would 
> it become political someday?

It's already not:

https://sourcehut.org/blog/2021-01-13-regarding-ethics/

(and I honestly prefer it that way!)

On 2/20/22 02:45, Drew DeVault wrote:
> Parallel build slots are the most expensive resource you can use on
> sourcehut. We have a total of 32 parallel build slots to share with the
> whole of sourcehut right now. Using a lot of them at once can quickly
> lead to your project monopolozing all or most of the build slots.

Ah, that does make sense. Out of curiosity, how does *length* affect 
this? Technically, I could bundle them together into 1 or 2 builds, 
using Vagrant here, but that might take a hot minute longer (not sure 
about #s yet, I'm redoing all the tests). I *thought* I had read once 
that single long builds are discouraged in favor of parallel builds, but 
I'm guessing now I misunderstood and that only really applied to *short* 
parallel builds?

I've been looking to revive a project that might end up using 5 or so 
pipelines (building packages for Fedora current and next release, Arch, 
Debian, and a separate pipeline to build container images that all of 
the packages use). Currently, I know that builds.sr.ht will currently 
run up to 4 build manifests at once, choosing at random if more than 4 
are present. Although I found the change where this was added, it didn't 
really have any rationale: 
https://git.sr.ht/~sircmpwn/dispatch.sr.ht/commit/2280641828bc352729ac5da0886bbb36d3b5759c#dispatchsrht/builds.py

Now, *technically* this doesn't seem to apply to the API, so I could 
have two build manifests, but one of them just queues the 4 package 
build jobs and monitors their status. I'm not sure why the limit was 
added in the first place, if it was e.g. more to stop crypto miners or 
random service abuse (I do also have a paid account). I also don't want

On 2/4/22 18:11, Greg Minshall wrote:

> Michael,
>
>> I agree it works perfectly. But personally I like to keep my system
>> namespace clean, for Python packages I have a virtualenv per project.
>> Some projects require version X of a package, others require version
>> Y.
> i wonder if this testing/setup case might be where something like docker
> might come in handy?
I have a working Dockerfile for todo.sr.ht and...uhh, meta.sr.ht? 
together in one image I was using to for unit testing purposes, if 
people are interested I could try expanding on & sharing it.
> cheers, Greg

Jan 17, 2022 2:59:38 AM Drew DeVault <sir@cmpwn.com>:

> On Mon Jan 17, 2022 at 4:40 AM CET, Ryan Gonzalez wrote:
>> This is needed for dnf config-manager to work.
>
> Is dnf config-manager something which is expected to work OOTB?

It's used to add repositories listed in the manifest:

https://man.sr.ht/builds.sr.ht/compatibility.md#fedora

This is needed for dnf config-manager to work.
---
 images/fedora/genimg | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/images/fedora/genimg b/images/fedora/genimg
index 3a6467a..9f31101 100755
--- a/images/fedora/genimg
+++ b/images/fedora/genimg
@@ -71,7 +71,7 @@ dnf -y \
 	--enablerepo=fedora \
 	--enablerepo=updates install \
 	--setopt=install_weak_deps=False \
-	basesystem systemd systemd-udev passwd dnf fedora-release $conditional_packages
[message trimmed]

On Thu, Dec 16, 2021 at 8:24 PM Ryan Gonzalez <rymg19@gmail.com> wrote:
>
> ---
>  abc | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/abc b/abc
> index 190a180..ce8c77d 100644
> --- a/abc
> +++ b/abc
> @@ -1 +1,2 @@
>  123
> +456
THIS IS WRONG

---
 abc | 1 +
 1 file changed, 1 insertion(+)

diff --git a/abc b/abc
index 190a180..ce8c77d 100644
--- a/abc
+++ b/abc
@@ -1 +1,2 @@
 123
+456
-- 
2.30.2
[message trimmed]

This breaks APIs that hard require enums whose values can be 0, e.g.
todo.sr.ht's TicketResolution.
---
 srht/validation.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/srht/validation.py b/srht/validation.py
index 36e5ba3..0feecd5 100644
--- a/srht/validation.py
+++ b/srht/validation.py
@@ -132,7 +132,7 @@ class Validation:
         value = self.optional(name, None, cls)
         if not friendly_name:
             friendly_name = name
[message trimmed]