You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem is with ../${APP}-${VERSION} being named pybitmessage-0.4.4
To build from the default git folder, change ../${APP}-${VERSION} to PyBitmessage, possibly?
It signs the .deb package with a line in the debian/control file, which has this:
Maintainer: Bob Mottram (4096 bits) <bob@robotics.uk.to>
Because of the way Bob made the packaging scripts, this needs a total overhaul.
I've attempted to rebuild this, but I'm not experienced enough with making debian packages to do it in a timely manner.
So in short, I don't know what files we need to get rid of and which ones we need to keep
I actually tried to contact Bob about a month ago but heard nothing back.
I need to spend more time on figuring out how linux packaging is supposed to work so that it can be smoothly integrated into distros. For now, I always deployed it by checking it out from github.
Change the version number throughout all files. The current version as of today (16 Dec 2015) is .0.5.5
This change in debian.sh:
# Build the package
# The -us and -uc flags force you to not sign the resulting package, which is a solution(?) to the
# packaging issue.
dpkg-buildpackage -F -us -uc
# Sign files
#gpg -ba ../${APP}_${VERSION}-1_${ARCH_TYPE}.deb
#gpg -ba ../${APP}_${VERSION}.orig.tar.gz
# This does not work if you do not have a private signing key, so it will be commented out by default.
Changing the Maintainer/Packager's email address throughout all files
More lines in debian.sh to detect which directory the executable is in, which sets that as the original directory name
And that covers it. You should now be able to package this on Debian based systems now.
Activity
mendaxi commentedon Dec 9, 2015
Issue with the way things are named in the Makefile. Excerpt:
Problem is with
../${APP}-${VERSION}being namedpybitmessage-0.4.4To build from the default git folder, change
../${APP}-${VERSION}toPyBitmessage, possibly?mendaxi commentedon Dec 14, 2015
It seems that with bashrc's packagemonkey implementation seems to have thrown quite a few things off.
In generate.sh:
We aren't Bob
In debian.sh:
It signs the .deb package with a line in the debian/control file, which has this:
Because of the way Bob made the packaging scripts, this needs a total overhaul.
I've attempted to rebuild this, but I'm not experienced enough with making debian packages to do it in a timely manner.
So in short, I don't know what files we need to get rid of and which ones we need to keep
PeterSurda commentedon Dec 14, 2015
I actually tried to contact Bob about a month ago but heard nothing back.
I need to spend more time on figuring out how linux packaging is supposed to work so that it can be smoothly integrated into distros. For now, I always deployed it by checking it out from github.
PeterSurda commentedon Dec 14, 2015
Feel free to spend more time on this, @mendaxi , if you want. I need to fix other stuff first.
mendaxi commentedon Dec 17, 2015
Looks like I fixed all of the debian compilation errors with my latest commit.
(Brace for wall of text)
The important bits are as follows:
And that covers it. You should now be able to package this on Debian based systems now.