[Slackbuilds-users] Fwd: gnome-desktop SlackBuild source is 404'd

[Bob Funk]

So on the topic of gnome-desktop:

I haven't put in any pull requests for updates or maintainer changes yet,
and it sounds like Gustavo has that taken care of now. I'll consider this
issue solved then.

Bob

On Tue, Feb 11, 2025, 21:30 Willy Sudiarto Raharjo <willysr at slackbuilds.org>
wrote:

> > We could use pipelines to populate the database, but okay, the pipelines
> > could also check if the package build on a pristine Slackware 15.0, and
> > the project on GitLab is already doing a pipeline with a job, is only
> > matter to improve it.
>
> No, that's not how the infrastructure works
> it only works from submission form and we want the main git repository
> in our SBo server, not from github/gitlab. They are just used for CI
> automation only.
>
> > About a email, when I was waiting 4 months with the script for Packer
> > and Terraform to submit, you guys sad to "wait is not ready yet", then I
> > couldn't check the site for 3 days, and someone else has submitted a
> > package and was accepted.
>
> when was this? i don't recall about terraform submission besides Andrew
> Clemon's.
>
> > I personally put all my Slackware work on gitlab.com/slackware-brazil/
> > slackbuilds and in git.schenkel.eti.br where I am building a
> sbo-o-matic
> > to auto compile all slackbuilds using a VM on Proxmox which each time it
> > build and upload the package, it reboot and restore the latest snapshot
> > to remain immutable. Still a WIP and I am building only packages which I
> > use on my workstation. I still want to use Anitya(release monitoring
> > project) together to create a Issue about a new version.
> >
> > We could have contributing directly, just editing the text directly from
> > GitLab, but since you don't accept work from non-maintainer, this can't
> > happen, which is funny because since I submitted the gnome-desktop I
> > didn't received any message from any who altered the code until now.
>
> You can always see who changes your code from git history.
> We (admins) normally avoid changing things unless it's necessary
> (broken, security vulnerabilities, etc). Sometimes we might miss if
> someone update other people's script, but we tried to avoid this as well.
>
>  > Where is the transparency when changing the code from other people?
>
> We do have policy of giving maintainer time to adjust their scripts if
> they are unavailable (usually around 1-2 weeks). If no reply within that
> time frame, other people may ask in the mailing list if they could take
> over and we (admins) can take a look on the activity of the maintainer.
>
> > PS: I just submitted gnome-desktop on the same MR waiting on GitLab.
>
>
> --
> Willy Sudiarto Raharjo
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20250211/eff47f83/attachment.htm>