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

[Gustavo Brondani Schenkel]

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.

As I mention, I didn't saw Bob's email, it went on junk by mistake, from 
a rule which was suppose to send to specific folder, like the messages 
from LQ and Google Groups.

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.

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.

Where is the transparency when changing the code from other people?

PS: I just submitted gnome-desktop on the same MR waiting on GitLab.

On 2/11/25 5:37 PM, B. Watson wrote:
>
>
> On Tue, 11 Feb 2025, Gustavo Brondani Schenkel wrote:
>
>> Also as I sad on the weekend on #slackbuilds liberachat, if gitlab or 
>> github was used and submit zone to the packages, we could use 
>> CODEOWNER to involve all package maintainers, then Bob Funk could 
>> have updated the package for me just give my thumbs up, or open an 
>> Issue, the email will not be disused because GitLab will send it.
>
> You vanished from IRC before I could reply to that...
>
> Your scheme would require all SBo maintainers and admins to create
> github/gitlab accounts. We're not going to require that.
>
> Even if we did, it wouldn't help with new submissions (rather than
> updates to existing builds). Those *must* go through the web form to
> populate our database correctly.
>
> What's so hard about using email? All you had to do was answer
> Bob Funk's mail... he didn't see a reply for a couple of weeks so I
> mistakenly assumed that meant you weren't maintaining your build, and
> gave him permission to take it over.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_0x4EEB0BCD843194ED.asc
Type: application/pgp-keys
Size: 13799 bytes
Desc: OpenPGP public key
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20250211/8cc4ba31/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 4798 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20250211/8cc4ba31/attachment.asc>