Hi!
Thomas Goirand ,
09/01/2023 – 16:20:41 (+0100):
> I can add another volume if needed. Please let me know!
I have just moved /var/lib/docker to /srv/docker, so I guess that should
not be needed.
Cheers!
--
Faustin
signature.asc
Description: PGP signature
Hi Aloïs,
Aloïs Micard ,
09/01/2023 – 10:38:33 (+0100):
> Just did a little volume cleanup on the host (docker volume prune)
> this has freed 8GB and should buy us more time.
We probably should consider putting /var/lib/docker in /srv too,
something like the following should do it:
| sudo system
Hi!
Thomas Goirand ,
09/01/2023 – 09:44:24 (+0100):
> The system disk is 20GB, so that's quite small, but there's a much bigger
> data /dev/sdb disk that isn't in use. How should I do? Should I mount
> /var/lib/docker on it? Using ext4 or xfs? What should I do with the current
> running docker ru
Aloïs Micard ,
21/11/2022 – 10:19:20 (+0100):
> Should I delete the old runner?
Probably since I have already cleaned the VM.
--
Faustin
GPG: F652 BCD1 1AA8 8975 F010 48A5 390A 2F27 832A 5C79
signature.asc
Description: PGP signature
Hi Aloïs!
Aloïs Micard ,
21/11/2022 – 09:40:47 (+0100):
> Hello. I have just sent you the registration token for the runner.
Ok, I have configured the token and named the runner "zigo-runner" Can
you check that everything looks OK? If not, your keys (from GH) are on
the machine:
| ssh deb...@sals
Dear Go-team,
is there anyone with sufficient Salsa-CI access who can to finalize
this?
Regards,
Faustin Lammler ,
14/11/2022 – 12:18:34 (+0100):
> Hi Thomas!
> Did you had time to look into this?
>
> Faustin Lammler ,
> 03/11/2022 – 17:13:11 (+0100):
>
> > Hi Thomas!
Hi Thomas!
Did you had time to look into this?
Faustin Lammler ,
03/11/2022 – 17:13:11 (+0100):
> Hi Thomas!
>
> Thomas Goirand ,
> 02/11/2022 – 16:46:39 (+0100):
>
> > I could, but I lack time, I'd prefer if someone else would do it.
>
> The VM should be ready
Hi Thomas!
Thomas Goirand ,
02/11/2022 – 16:46:39 (+0100):
> I could, but I lack time, I'd prefer if someone else would do it.
The VM should be ready now. And I took the opportunity to revalidate the
documentation[1] and the ansible deployment[2].
> I'm a Salsa admin (and go-team admin), so yea
Hi Thomas!
Thomas Goirand ,
27/10/2022 – 22:07:44 (+0200):
> Are you able to do the Salsa setup?
The documentation should be pretty up to date:
https://go-team.pages.debian.net/ci.html (Setup a new Runner).
Do you wanna give it a try?
Then I guess that the biggest challenge would be to make the
Dear Go-Team!
As discussed with Aloïs, he did not had time to work on finding a long
term solution and the VM is still used by the CI.
As said earlier, this was always a temporary solution and we need to
find a definitive solution relying on DSA probably?
I can provide all the metrics and all the
Hi Nilesh!
Nilesh Patra ,
12/06/2022 – 21:41:41 (+0530):
> Faustin, Alois,
>
> Could you please take a look at what is up with the runner?
> This is affecting all the packages now - and hence would appreciate your
> response.
Very sorry for this, I did not saw this mail earlier! I have improve
Hi Nilesh!
Nilesh Patra ,
20/11/2021 – 23:22:50 (+0530):
> Pushed a fix. Please finalise this.
> I hope Alois will be available for sponsoring; I'm out of time these days,
> very sorry :(
Gentle note: next time, can you add descriptions and context to your
commits because I am having difficulti
Hi!
Nilesh Patra ,
20/11/2021 – 18:23:14 (+0530):
> You only pushed the upstream branch to salsa. That is not enough.
> Please push all branches. debian/sid branch is bare minimum
Sorry I am really not good with gbp, it should be good now...
> Hmm, it seems to have even migrated to testing yes
Hi Nilesh!
Nilesh Patra ,
17/11/2021 – 01:49:49 (+0530):
> I hope you do not mind me responding instead of Alois.
> Since ratt is happy, I sponsored you an upload to unstable.
Thank you for that.
> Gentle note: When doing uploads in a team maintained package that you
> are a part of, the change
Hi!
I am making progress in building shfmt.
@Aloïs, as discussed on IRC, I have informed Anthony about [1].
Could you please take a moment to sponsor the upload if everything looks
good to you? Ratt did not complain.
I am now able to build shfmt with all the dependencies, using (and
sbuild):
| gb
Aloïs Micard ,
18/10/2021 – 18:33:14 (+0200):
> Since we try to keep only one version of a package at a given time,
> every package upload may break other packages that depends on it. This
> is especially true for Go core package.
>
> While we could use a standards workflow and use tools like
> d
Hi!
Aloïs Micard ,
18/10/2021 – 17:26:27 (+0200):
> Please see the page dedicated to our CI setup [1] for more details,
> everything is explained.
I did it but see bellow.
> To put it in a nutshell: we have a very special setup that allows us
> to prevent any regression (efficiently) with all go
Nilesh Patra ,
18/10/2021 – 08:11:54 (-0700):
> > I'll setup a VM on my infra and try to follow your setup documentation
> so I may have more feedback in the next days.
>
> Why not instead take up a shell account on Aloïs's machine instead? :)
Because this would not validate the setup documentat
Hi Aloïs!
Aloïs Micard ,
15/10/2021 – 16:39:59 (+0200):
> In the go team we have a kinda 'special' CI setup put in place by @stapelberg
> which greatly improve the life of Go maintainers by doing full rebuild of all
> go packages at every commit. This way you know exactly if your new commit
> int
Hi!
Nilesh Patra ,
15/10/2021 – 17:09:07 (+0530):
> Okay, uploaded. Please take a look at my commits, and specifically
> please fix copyrights in later releases. FTP masters are picky on
> these things, and even leaving out a single-file copyright
> un-mentioned will (likely) lead to a reject.
E
Hi Nilesh!
Nilesh Patra ,
15/10/2021 – 15:36:06 (+0530):
> Awesome, I pushed a little cleanup change (nitpick).
/me like it!
> That we can ignore, not ultimately urgent.
I understand, but it's good to have IMO (we had last week at our MariaDB
Server Fest a presentation about supply chain attac
Hi!
I have managed to reactivate the test suite. It took me a bit longer
than expected because I had to find the correct path to copy the test
suite to. And I also had to remove those files after the test passed as
I did not want them in the final deb (plus those made lintian really not
happy :)).
Hi Nilesh!
Nilesh Patra ,
14/10/2021 – 15:06:07 (+0530):
> I've a couple of ideas to run tests. First off, so we are on the same
> page, the build/tests etc (process till creation of .deb) have to
> happen offline, so doing a clone during build is not possible.
>
> So there are two workarounds:
Hi!
Aloïs Micard ,
14/10/2021 – 11:02:17 (+0200):
> The CI has been disabled for the whole Go packages. (I'm still working on
> getting the runner fixed)
I would be happy to help you on that task. I have quite good experience
with CI systems (drone.io, GitLab CI, GitHub actions, TravisCI and
Bui
Hi Nilesh!
Nilesh Patra ,
14/10/2021 – 14:42:21 (+0530):
> In general, you should never be "force"-pushing to the main branch, that is
> d/sid in this case.
And I normally don't! But I am such a beginner with gbp that I have
messed up with the git d/sid branch history (and I wanted to squash all
Hi!
Aloïs Micard ,
14/10/2021 – 10:38:16 (+0200):
> The package has been uploaded on the NEW [1] queue, you can view the package
> details on the following page [2].
>
> Since the package has been uploaded by Anthony, there's nothing we need to do
> here. The FTP masters will review the package
Dear Go Team!
Can I kindly ask for force push access on the following repositories
(debian/sid branch):
- https://salsa.debian.org/go-team/packages/golang-github-pkg-diff
- https://salsa.debian.org/go-team/packages/golang-mvdan-editorconfig
Or should I always merge request?
Regarding the last on
Hi Aloïs!
I can't find your response in my MUA (I made some cleaning in my mutt
archives, maybe too violent).
FYI, here is the message:
https://lists.debian.org/debian-go/2021/03/msg00016.html
I am starting again the packaging process. In the mean time, I see that
https://salsa.debian.org/go-tea
Hi!
Aloïs Micard ,
29/07/2021 – 22:52:53 (+0200):
> I can definitely invest some time in getting back the CI working,
> write some documentation about the Go team 'infra' (i.e: pgt-api-server,
> the ci runner, etc...) and harmonize everything so that it is team
> accessible.
>
> I will get in to
c scenario is not possible?
Thanks!
--
Faustin Lammler
GPG: F652 BCD1 1AA8 8975 F010 48A5 390A 2F27 832A 5C79
signature.asc
Description: PGP signature
g-diff_0.0~git20200914.5b29258-1.dsc
Changes since the last upload:
* Initial release (Closes: #982472)
Regards,
--
Faustin Lammler
-
GPG: F652 BCD1 1AA8 8975 F010 48A5 390A 2F27 832A 5C79
signature.asc
Description: PGP signature
Faustin Lammler ,
11/02/2021 – 11:45:04 (+0100):
> So my questions are:
> - does this change looks good to you?
> - should I PR against https://salsa.debian.org/go-team/ci (then I would
> need that someone grant me access);
Sorry, I can fork and do a MR in gitlab, no a
PR against https://github.com/Debian/dh-make-golang too?
- is there any better way of addressing this?
As I am new here and not a GO developer the workflow between those two
previous repo is not very clear to me.
Thanks in advance for your lights!
--
Faustin Lammler
GPG: F652 BCD1 1AA8 8975 F010
and the
gitlab-ci.yml header does not invite me to touch that :))
Lintian is green :)
Also what's the good way of squashing my commits? Or should I document
better the changes than 'fixup!' and not rebase?
--
Faustin Lammler
GPG: F652 BCD1 1AA8 8975 F010 48A5 390A 2F27 832A 5C79
signature.asc
Description: PGP signature
Aloïs Micard ,
10/02/2021 – 17:53:49 (+0100):
> I'll ask an owner of the go-team to grants you access to your repository,
> then we can review it & check what's going on :)
I have just pushed it.
Thanks !
--
Faustin Lammler
GPG: F652 BCD1 1AA8 8975 F010 48A5
> “Team upload” and some variations in the changelog), you would get this
> warning.
Ok, now I get it and thanks, this was the problem (see 3f92013).
And now lintian tells me:
| W: golang-github-pkg-diff source: nmu-in-changelog
I guess lintian is going to be my best friend in the next month
ush
> --tags / gbp push) you can either send an email to the team or maybe
> to the debian-mentors mailing list.
Ok, I am waiting for my access request to be accepted and I will do
that.
Thanks again,
--
Faustin Lammler
GPG: F652 BCD1 1AA8 8975 F010 48A5 390A 2F27 832A 5C79
signature.asc
Description: PGP signature
Package: wnpp
Severity: wishlist
Owner: Faustin Lammler
* Package name: golang-github-pkg-diff
Version : 0.0~git20200914.5b29258-1
Upstream Author : Josh Bleecher Snyder
* URL : https://github.com/pkg/diff
* License : BSD-3-clause
Programming Lang: Go
Aloïs Micard ,
09/02/2021 – 17:00:22 (+0100):
> ```
> $ dh-make-golang create-salsa-project golang-github-pkg-diff
> ```
done.
https://salsa.debian.org/go-team/packages/golang-github-pkg-diff
And I have just requested access again, sorry for the spam!
> What you are doing is create the **source*
gt; https://salsa.debian.org/go-team/go-team.pages.debian.net
>
> you can open a PR here and ask for review.
I have prepared a PR and will request for review once it's finished (I
took the opportunity to add a link check step in the CI).
Thanks!
--
Faustin Lammler
signature.asc
Description: PGP signature
nventions_2
and then add them to the debian/control Build-Depends to finally build
shfmt program or is there another way?
Side note: there are a bunch of 404 urls in
https://go-team.pages.debian.net, what's the best way to report/help to
fix them?
Thanks for your help.
--
Faustin Lammler
signature.asc
Description: PGP signature
41 matches
Mail list logo
