[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

webgen (finally)



Hi team,

after all needed packages for webgen are at least in
unstable now I started finishing the webgen package itself.

It didn't built with ruby 2.7 and tests enabled (and I had
some trouble using it for my personal website as well), so
I contacted the upstream author, Thomas Leitner a month
ago, who promised to look into it and wanted to make his
program ruby-2.7 and ruby-3 ready by the way.

Yesterday he released the new (ruby3-ready) version 1.7.2,
which works fine (and also solves my problems while using it
for my website). I imported it into my webgen git at
salsa, ran the meta-build script and it built fine, all
tests passed fine. There were of course some lintian
warnings.

So I thought that's time to copy my git to
ruby-team/mentors. I created a project there using the
meta/setup-projects-mentors script, which (again) gave me
some errors (see attachment), but at least created a new git
where I could push my work into.

Now every time I push changes to that mentors/webgen-git I
seem to trigger some build pocess of the package and the
funny thing is, that this build process has a totally
different outcome than the one I initiate on my local git
with the meta-build script:

When I run the build-script on my local machine the
build in the (unstable) sbuild environment works fine
(including all tests during the build process) and all tests
in the lxc-unstable environment run fine as well.

The build-process that is initiated on salsa fails because
some tests (that are done during the build-process)
fail. And these are the same tests that run fine here.

Can anybody explain me this difference?

Klaumi

-----
Klaumi Klingsporn
mail: klaumikli@gmx.de
web: www.klaumikli.de
setup-project-mentors webgen

I webgen: repository created (id: 58829)
Traceback (most recent call last):
	8: from /home/klaumi/COMPILE/salsa.debian.org-CLONE/ruby-team/meta/setup-project-mentors:33:in `<main>'
	7: from /home/klaumi/COMPILE/salsa.debian.org-CLONE/ruby-team/meta/setup-project-mentors:33:in `each'
	6: from /home/klaumi/COMPILE/salsa.debian.org-CLONE/ruby-team/meta/setup-project-mentors:35:in `block in <main>'
	5: from /home/klaumi/COMPILE/salsa.debian.org-CLONE/ruby-team/meta/lib/salsa.rb:41:in `set_webhooks'
	4: from /home/klaumi/COMPILE/salsa.debian.org-CLONE/ruby-team/meta/lib/salsa.rb:48:in `set_tagpending'
	3: from /usr/share/rubygems-integration/all/gems/gitlab-4.17.0/lib/gitlab.rb:28:in `method_missing'
	2: from /usr/share/rubygems-integration/all/gems/gitlab-4.17.0/lib/gitlab/client/projects.rb:192:in `project_hooks'
	1: from /usr/share/rubygems-integration/all/gems/gitlab-4.17.0/lib/gitlab/request.rb:51:in `block (2 levels) in <class:Request>'
/usr/share/rubygems-integration/all/gems/gitlab-4.17.0/lib/gitlab/request.rb:59:in `validate': Server responded with code 403, message: 403 Forbidden. Request URI: https://salsa.debian.org/api/v4/projects/58829/hooks (Gitlab::Error::Forbidden)

Reply to: