goocanvas: update to 3.0.0.

[Wesley-Chan]

Testing the changes

• I tested the changes in this PR: briefly

Local build testing

• I built this PR locally for my native architecture, (x86-64-musl)

[Wesley-Chan]

The failure in CI is due to this package: gpredict

It specifically requires goocanvas 2 in configure.ac, but as discussed in this issue, gpredict can use goocanvas 3 as well. Changes to adapt to it was also merged into its master but gpredict has no new version released after that change.

In our case, it is one package that is blocking our advancement. Is the normal way to resolve conflicts to make a newer version of goocanvas in Void Linux, or make custom patch to gpredict?

Please advice. Thank you very much.

[classabbyamp]

if you can find the upstream commit(s)/pr that added goocanvas3 support for gpredict, you can export it as a patch by adding .patch to the url and download it to srcpkgs/gpredict/patches

[classabbyamp]

looking into this more, perl-GooCanvas2 is the only other package that depends on goocanvas, so I think we should stay on goocanvas 2.x for now.

[Wesley-Chan]

Hey, @classabbyamp. Thank you for your quick reply.

Sorry, I don't quite understand what you meant by "perl-GooCanvas2 is the only other package that depends on goocanvas". Doesn't gpredict also depend on goocanvas by linking to it?

The motivation of mine to update goocanvas is to bring Akira to Void, which does depend on goocanvas 3. If I understand correctly, if other packages like gpredict or perl-Goocanvas2 refuse to move on, Akira could never land on Void Linux, right?

Thank you very much.

P.S. How do I verify the GitHub action Verify repository state locally? Is it documented anywhere? Thanks again.

[classabbyamp]

Sorry, I don't quite understand what you meant by "perl-GooCanvas2 is the only other package that depends on goocanvas". Doesn't gpredict also depend on goocanvas by linking to it?

only package other than gpredict is what I meant

The motivation of mine to update goocanvas is to bring Akira to Void, which does depend on goocanvas 3. If I understand correctly, if other packages like gpredict or perl-Goocanvas2 refuse to move on, Akira could never land on Void Linux, right?

in this case, we'd want to have a versioned package for the time being, like goocanvas2 and goocanvas. however, it seems that akira removed goocanvas? (akiraux/Akira#652)

How do I verify the GitHub action Verify repository state locally? Is it documented anywhere?

that ci step:

void-packages/.github/workflows/build.yaml

Lines 120 to 126 in 2cb7f28

	- name: Verify repository state
	run: |
	(
	here="$(pwd)"
	cd /
	"$here/common/travis/check-install.sh" "$BOOTSTRAP" "$ARCH"
	)

runs this script:
https://github.com/void-linux/void-packages/blob/master/common/travis/check-install.sh
I would not recommend running it locally outside of a container.

[github-actions]

Pull Requests become stale 90 days after last activity and are closed 14 days after that. If this pull request is still relevant bump it or assign it.

[newbluemoon]

There is also #31159 which worked for me (i.e. the pre_configure-fix). I tested it with all depending packages just didn’t pursue it any further, because there didn’t seem to be much interest at that time. ;)

[github-actions]

Pull Requests become stale 90 days after last activity and are closed 14 days after that. If this pull request is still relevant bump it or assign it.