xolitude has quit [Read error: Connection reset by peer]
joerg has quit [Ping timeout: 252 seconds]
joerg has joined #maemo-leste
hexnewbie has quit [Server closed connection]
hexnewbie has joined #maemo-leste
_fab has joined #maemo-leste
fmg_d4 has joined #maemo-leste
_fab has quit [Ping timeout: 244 seconds]
vectis has joined #maemo-leste
_whitelogger has joined #maemo-leste
rhn_mk1 has joined #maemo-leste
wuboy has joined #maemo-leste
wuboy is now known as whatsupboy
whatsupboy is now known as skipper
hm has joined #maemo-leste
skipper has quit [Quit: brb]
pere has quit [Ping timeout: 252 seconds]
Anasko has quit [Remote host closed the connection]
Anasko has joined #maemo-leste
Anasko has quit [Remote host closed the connection]
Anasko has joined #maemo-leste
joerg has quit [Ping timeout: 244 seconds]
joerg has joined #maemo-leste
narodnik2 has quit [Quit: WeeChat 4.7.0]
narodnik2 has joined #maemo-leste
Anasko has quit [Remote host closed the connection]
Anasko has joined #maemo-leste
fmg_d4 has joined #maemo-leste
rhn_mk1 has quit [Ping timeout: 255 seconds]
<Wizzup>
freemangordon: so to build packages in our forgejo after commit (for build testing purposes), we need a .forgejo/workflows directory with some files in it. by default debian will pick this up in the source tars / source files, I don't think we want this
<Wizzup>
we could make a debian/source/options file that has an ignore for these files, what do you think, makes sense?
<freemangordon>
what does upstream do?
<Wizzup>
we can also change our jenkins and forgejo actions to add -i .forgejo to dpkg-source flags
<Wizzup>
but this feels... lazy
<Wizzup>
freemangordon: not clear
<freemangordon>
because your proposal means we shall 'fix' each and every package in our repos
<Wizzup>
we have to commit to each package in any case to add the .forgejo/workflows/build.yml file
<freemangordon>
does it differ from package to package?
<Wizzup>
no
<freemangordon>
like, can't we ad git hook or something?
<Wizzup>
so we can at that moment either also change/add debian/source/options, or we can modify our jenkins and forgejo runner to always ignore the .forgejo directory
<Wizzup>
I don't get the question
<freemangordon>
I don;t feel adding some specific directory to every package is a good thing. can;t we somehow tell auto-add it just for the purpose of test builds?
<freemangordon>
*somehow tell git to
<freemangordon>
by using git hook or dunno
<Wizzup>
no, these are triggered by the CI/CD system in forgejo based on presence of files
<Wizzup>
the presence of the files is what triggers the action/build
<Wizzup>
we can have them only in our maemo/* branch of course
<freemangordon>
but then, is we decide in a month to move from forgejo to gorgejo (made-up) we shall edit all the packages, once again
<Wizzup>
yup
<freemangordon>
hmm
<freemangordon>
why can't we trigger builds based on the fact there is new commit?
<Wizzup>
because there is nothing to say what to do on the trigger
<freemangordon>
git hook? that auto-adds the needed files?
<Wizzup>
unless we completely don't use forgejo and only use some webhook to trigger our jenkins instance to do something
<Wizzup>
I don't understand how this can work
<Wizzup>
forgejo looks at the data in .git, the actual bare repo
<Wizzup>
there's no way a hook can do anything there
<freemangordon>
ok
<Wizzup>
more than anything I'm just trying to see if we can use this at all, so maybe start with 5-10 packages and see how it goes, maybe do it for extras first
<Wizzup>
but dpkg-source complains about .forgejo/workflows/... existing
<freemangordon>
I see
<freemangordon>
hmm, wait, why it cares?
<freemangordon>
maybe telling jenkins to add -i to dpkg-source command line is not that bad
<Wizzup>
it cares because the tag it's building doesn't include .forgejo/workflows/...
<Wizzup>
and it thinks we 'changed' the source
<Wizzup>
at least I think that's what is happening