The PPA now has the s390x package of dart finally.
Answering the issues that Lucas found in the packaging:
> And FWIW, we are using git to maintain ubuntu package (using git-ubuntu), bzr
> has not been used for packages for a while AFAIK. But if it is easier for you
> to provide the packages in a PPA, that's also works IMO.
> Thanks for the updated packages! I think you also noticed that two packages
> there, in the PPA, are failing to build from source in s390x, right? We need to
> fix that because s390x is a officially supported architecture. Could you please
> take a look to see if you can identify any issue?
> Missing build dependencies: libignition-common-dev (>= 4.0.0)
> If you check the version of this package in Noble you will notice that it
should be satisfiable:
> libignition-common-dev | 4.7.0+ds2-2ubuntu1 | noble/universe | amd64, arm64,
armhf, ppc64el, riscv64
Also invested a bit of time debugging this, seems to me like there were some
platforms related to problems detailed in https://bugs.debian.org/977638
> Regarding the dart armhf unsupportability, if upstream says it is not
> supported, you should change the Architecture fields in debian/control to
> reflect that. If you leave arch:any then it will be built in all architectures,
> you'd need to exclude armhf.
The PPA now has the s390x package of dart finally.
Answering the issues that Lucas found in the packaging:
> And FWIW, we are using git to maintain ubuntu package (using git-ubuntu), bzr
> has not been used for packages for a while AFAIK. But if it is easier for you
> to provide the packages in a PPA, that's also works IMO.
I've migrated the bazaar changes to Git and commit new changes to ubuntu/devel /git.launchpad. net/~j- rivero/ ubuntu/ +source/ dart/log/ ?h=ubuntu/ devel
https:/
> Thanks for the updated packages! I think you also noticed that two packages
> there, in the PPA, are failing to build from source in s390x, right? We need to
> fix that because s390x is a officially supported architecture. Could you please
> take a look to see if you can identify any issue?
Took me a little bit to debug things of a large package on s390x emulation but /git.launchpad. net/~j- rivero/ ubuntu/ +source/ dart/commit/ ?h=ubuntu/ devel&id= 84595c63d173c78 f1c2653d3dd872a e44bbc48b5
finally found the problem in one of the dependencies of dart. I reported it
upstream with the result of my research, it is not trivial to fix:
https:/
> Missing build dependencies: libignition- common- dev (>= 4.0.0) common- dev | 4.7.0+ds2-2ubuntu1 | noble/universe | amd64, arm64,
> If you check the version of this package in Noble you will notice that it
should be satisfiable:
> libignition-
armhf, ppc64el, riscv64
Also invested a bit of time debugging this, seems to me like there were some /bugs.debian. org/977638
platforms related to problems detailed in https:/
I've upload a new ignition-common package from the ubuntu/nobel branch that /git.launchpad. net/~j- rivero/ ubuntu/ +source/ ignition- common/ log/?h= ubuntu/ noble
built on s390x:
https:/
that
> Regarding the dart armhf unsupportability, if upstream says it is not
> supported, you should change the Architecture fields in debian/control to
> reflect that. If you leave arch:any then it will be built in all architectures,
> you'd need to exclude armhf.
Done in https:/ /git.launchpad. net/~j- rivero/ ubuntu/ +source/ dart/commit/ ?h=ubuntu/ devel&id= a6a3f90252d0b47 ec73638566f1b04 6a22ee1134