Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Please fix the compilation for debian stable. #36

Open
jeriko5 opened this issue Mar 27, 2017 · 7 comments
Open

Please fix the compilation for debian stable. #36

jeriko5 opened this issue Mar 27, 2017 · 7 comments

Comments

@jeriko5
Copy link

jeriko5 commented Mar 27, 2017

Please fix the compilation for debian stable.

@xSmurf
Copy link
Contributor

xSmurf commented Apr 16, 2017

Hello, could you provide more information? Build logs, software version, etc would be helpful.

@lesion
Copy link

lesion commented Apr 16, 2017

➜  fw-daemon git:(debian)  debuild -i -I -us -uc   
This package has a Debian revision number but there does not seem to be
an appropriate original tar file or .orig directory in the parent directory;
(expected one of fw-daemon_0.0.5.orig.tar.gz, fw-daemon_0.0.5.orig.tar.bz2,
fw-daemon_0.0.5.orig.tar.lzma,  fw-daemon_0.0.5.orig.tar.xz or fw-daemon.orig)
continue anyway? (y/n) 

dpkg-source: error: can't build with source format '3.0 (quilt)': 
no upstream tarball found at ../fw-daemon_0.0.5.orig.tar.{bz2,gz,lzma,xz}

@xSmurf
Copy link
Contributor

xSmurf commented Apr 17, 2017

@lesion as indicated in the readme, the way to build this package is using gbp such as: gbp buildpackage -us -uc.

@lesion
Copy link

lesion commented Apr 17, 2017

I saw it, but gbp is using other tools like debuild inside, and that's the point where it stops, so hope it helped. If you prefer I'll send you debug written by gbp but it's the same.

@xSmurf
Copy link
Contributor

xSmurf commented Apr 17, 2017

Could you provide the complete log and exact commands you used then? I just went through the instructions again to build from the stable tag with no issues (well there was an error later in the build - we'll get to that when we get there fixed ;).

@lesion
Copy link

lesion commented Apr 17, 2017

package installation is working now (with a little modification here as user does not exist).

@xSmurf
Copy link
Contributor

xSmurf commented Apr 18, 2017

Hmmm yeah I could remove it all together I think since we use a different technique to enable the extension now (via the session). Perhaps there's an official way to do this, but we haven't found it. Nevertheless that should be a non blocker due to || true.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants