FTBFS Budgie Desktop 10.4 on Debian Unstable/ Ubuntu 18.04 #1228
Comments
|
OK so - this change is in git not 10.4 (was issued after git tag) - are you actually saying you need that fix due to some build issue with plain 10.4? Because tbh it could even be worth kludging together a temporary tarball.. |
|
OK so @fossfreedom I don't know if this'll fly with Debian guys (maybe ask @jbicha) but I've created a new signed tarball from git here: https://solus-project.com/sources/budgie/ It has 10.4+9 commits on top, and is signed using my GPG key. That might get you out of this mess? |
|
thanks. Yes - likely need to have something to call on before someone kicks off a rebuild. It has happened twice in the recent weeks due to stuff transitioning in Debian. I'll have a look at the tarball soonest. cheers. |
|
aah ok - yeah can't have it looking bad in the queue :) |
|
Debian can't have two different source tarballs with the same name. But you can patch Debian packages. (Or if the patches are excessive, you could also just do a git snapshot.) So I think a cherry-picked patch is all you need here. |
|
Problem is the cherry-picked patch is an update of a git submodule |
|
Ok, fossfreedom just needs to use a different filename for the .orig.tar.xz and update debian/changelog to match it. |
just uploaded into the same directory |
|
Thanks @ikeydoherty - looks ok; there is an oddity which I'll mention on a separate issue. I'll close this. cheers for your help. |
Operating System: Debian Unstable, Ubuntu 18.04
Budgie version: Budgie Desktop 10.4
The issue encountered
FTBFS due to latest meson version - same issue as fixed here:
3d6d71c
However, unfortunately, cannot use this fix since no external network access is permissible outside the build environment for Debian/Ubuntu i.e. cannot meson git clone the GVC project.
The text was updated successfully, but these errors were encountered: