debian package building added

[navjotcis]

I have added debian package building with the reference of https://git.bitmessage.org/citizenaspirant/PyBitmessage/commit/5f955ba52f10c6167e82ec870cbb327a6ca1de2d

[PeterSurda]

I tested, it builds, but haven't tried installing.

[PeterSurda]

I would say I merge this and if it doesn't run, fix it separately, because having this in will allow me to add dpkg to buildbot.

[g1itch]

Why don't you put this into packages dir?

[PeterSurda]

I don't know how to integrate it into dpkg-buildpackage if I move the files.

[g1itch]

Also maybe get rid of https://github.com/Bitmessage/PyBitmessage/tree/v0.6/packages/unmaintained/debian?

[g1itch]

That's what I expected: https://travis-ci.org/github/g1itch/PyBitmessage/builds/735505903

[navjotcis]

Now the build is successfully passing https://buildbot.bitmessage.org/#/builders/14/builds/161

[g1itch]

Also, please, look into informational part. Why empty fields? Why such weird version and unstable mark? Should python-msgpack really be a requirement? Who is going to be maintainer and how it will be maintained? Changelog may be probably generated by sphinx.

[navjotcis]

Also, please, look into informational part. Why empty fields? Why such weird version and unstable mark? Should python-msgpack really be a requirement? Who is going to be maintainer and how it will be maintained? Changelog may be probably generated by sphinx.

so I think I should use stable version like you have used bitmessage (0.6.3.2) stable; urgency=medium

[g1itch]

Also, please, look into informational part. Why empty fields? Why such weird version and unstable mark? Should python-msgpack really be a requirement? Who is going to be maintainer and how it will be maintained? Changelog may be probably generated by sphinx.

so I think I should use stable version like you have used bitmessage (0.6.3.2) stable; urgency=medium

You can get actual version by python setup.py -V but it's not the point. For me the real problem with this PR is that it tends to become another unusable piece of garbage like fabfile, android_instruction.rst, src/bitmessagekivy, src/kivymd, src/navigationdrawer and like docs was before I fixed the documentation building process. You have some additional scripts in buildbot/dpkg task, including one, changing the version, which is needed for deb building. But your README says "Clone the source and run dpkg-buildpackage" and that's not gonna work for a general end user.

[g1itch]

That's what I expected: https://travis-ci.org/github/g1itch/PyBitmessage/builds/735505903

Amendment: something like that, but demonstrating the build of non-empty and functional deb.

[g1itch]

That's what I expected: https://travis-ci.org/github/g1itch/PyBitmessage/builds/735505903

Amendment: something like that, but demonstrating the build of non-empty and functional deb.

Like this: https://travis-ci.org/github/g1itch/PyBitmessage/jobs/736037581

As I suspected all that debian dir indeed is garbage. stdeb.cfg is enough. If someone needs that dir for some reason, it's generated by python setup.py --command-packages=stdeb.command debianize.

[PeterSurda]

@g1itch Can you make a minimal PR from your debian branch? Then we can close this. No need to modify .travis.yml, I want the builds and the tests to be separate. As you can see buildbot's dpkg builder now succeeds, so it just needs fine tuning.

[PeterSurda]

Superseded by #1686 .