*.deb and *.rmp releases

[thedrow]

It will be much easier to install r3 if it had packages.
You can use fpm to do so easily.

[c9s]

Haven't any experience with fpm yet, could you provide some instructions about this? thanks. :)

[thedrow]

Sure, I'll explain in the evening.

[thedrow]

Here's a recipe for building beanstalkd.
It uses make in order to build the package and pulls from git.
The ZeroMQ recipe also uses configure.

[c9s]

Looks nice, have you released a package with FPM before? if so, would you mind send me a PR for this? thanks :)

[thedrow]

Sure, I will send a PR soon.

[thedrow]

I should also create a clib package.json so people could vendor r3 more easily.

[c9s]

Sounds great!

[czchen]

Just issue an ITP (Intent to Package) in debian https://bugs.debian.org/748748. I will handle debian release after first version is released.

[c9s]

Hi @czchen ,

Thanks for your help! 👍

[c9s]

Hi @czchen ,

Version 1.2.1 is released. https://github.com/c9s/r3/releases/tag/1.2.1

[thedrow]

I forgot about this.
I can promise that it will be done by friday.

[bluebat]

rpms at https://build.opensuse.org/package/show/home:bluebat/libr3

[thedrow]

@bluebat Did you generate the RPM with fpm?
Care to share the recipe?

[bluebat]

@thedrow No, there is the spec file.

[czchen]

r3 is in debian new queue now. After ftp master accepts it, r3 will be in debian official repository.

[c9s]

Great! @czchen thanks for your work! :D

[czchen]

@c9s Look like r3 build fail at armel. Any idea?

[c9s]

I have no ideal with armel XD.. seems like failed at check.

[czchen]

http://paste.lisp.org/display/143077 is the error log provided by @kanru. It is segmentation fault.

[czchen]

I use schroot + qemu to build armel in amd64 for this issue, here is my conclusions:

• coredump does not contain valid stack trace, possible stack smashing.
• qemu does not support ptrace, so gdb is useless.
• The issue is gone if I define DEBUG to enable debug print. Not sure why.

[kanru]

"ChangZhuo Chen (陳昌倬)" notifications@github.com writes:

I use schroot + qemu to build armel in amd64 for this issue, here is my conclusions:

• coredump does not contain valid stack trace, possible stack smashing.
• qemu does not support ptrace, so gdb is useless.
• The issue is gone if I define DEBUG to enable debug print. Not sure why.

I might be able to get a backtrace from real armel machine.. stay tuned.

Kanru

[thedrow]

Should we close this issue?

[bluebat]

Yes for rpm:
https://github.com/chinese-opendesktop/repo/raw/master/src/libr3-1.3.4-1.src.rpm
https://github.com/chinese-opendesktop/repo/raw/master/x86_64/libr3-1.3.4-1.x86_64.rpm
https://github.com/chinese-opendesktop/repo/raw/master/x86_64/libr3-devel-1.3.4-1.x86_64.rpm