I'd like to make packages for my box, which is 64 bit. I can compile from source ok, but I'd prefer to make a debian package, so I can manage it with apt.
The debian metadata to make a package isn't in the source; can I get it somewhere?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yeah there sure is... and I know it all works on 64 bit already because the ubuntu team builds 64 bit debs without issues. I doubt you'll even have to change much to get it to build on debian, but what the heck do I know :).
Oh right, sorry I forgot about that! Interesting 3.4 _should_ be in Hardy... I'll have to check that out.
In the mean time... if you need help building a deb let me know, and if you do get some built and don't mind donating them I'd be happy to host them on the sourceforge page!
Thanks,
Tim.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I moved the debian_ubuntu_official dir into gizmo3 as "debian"
then I chmod +x debian/rules
then I do "dpkg-buildpackage -rfakeroot -b" and get:
dpkg-buildpackage: source package is gizmod
dpkg-buildpackage: source version is 3.2-0ubuntu1
dpkg-buildpackage: source changed by Joseph Price <pricechild@ubuntu.com>
dpkg-buildpackage: host architecture amd64
dpkg-buildpackage: source version without epoch 3.2-0ubuntu1
fakeroot debian/rules clean
test -x debian/rules
test "`id -u`" = 0
dh_clean
/usr/bin/make -C . -k distclean
make[1]: Entering directory `/home/mjf/gizmod/gizmod3'
make[1]: *** No rule to make target `distclean'.
make[1]: Leaving directory `/home/mjf/gizmod/gizmod3'
make: [makefile-clean] Error 2 (ignored)
rm -f debian/stamp-makefile-build
rm -f debian/stamp-autotools-files
debian/rules build
test -x debian/rules
mkdir -p "."
touch debian/stamp-autotools-files
chmod a+x /home/mjf/gizmod/gizmod3/./configure
chmod: cannot access `/home/mjf/gizmod/gizmod3/./configure': No such file or directory
make: *** [config.status] Error 1
First thing that worries me is "source version is 3.2-0ubuntu1"... is that just a debian/* metadata problem?
Second thing is the error...
So, I moved the actually named "debian" dir from dist instead of the ubuntu one, which worked.
I didn't sign the package; your key is referenced, but of course, I don't have it. I don't know how to make myself a key to sign a package... I can, if it's necessary, but I don't know that anyone would trust me anyway, so not sure that the key helps.
How can I send the packages to you?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
That's great! And signing isn't necessary I should think... send them to me via email at: tim [dot] burrell [at] gmail [dot] com.
As for what's going on with the official ubuntu package... not sure. The Ubuntu MOTU team wrote those scripts and to be honest they go beyond my debian packaging abilities :). I'll wait until I hear more about getting 3.4 into hardy -- they'll likely have updated build scripts.
Thanks!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello.
I'd like to make packages for my box, which is 64 bit. I can compile from source ok, but I'd prefer to make a debian package, so I can manage it with apt.
The debian metadata to make a package isn't in the source; can I get it somewhere?
Hey there,
Yeah there sure is... and I know it all works on 64 bit already because the ubuntu team builds 64 bit debs without issues. I doubt you'll even have to change much to get it to build on debian, but what the heck do I know :).
You can check out the svn source here: http://sourceforge.net/svn/?group_id=139428
Look in the dist/debian_official_ubuntu directory.
Err wait you said you're compiling on gutsy? Why doncha just apt-get install gizmod?
Tim.
Gutsy has v 3.3 in the repositories. So does Hardy.
I'm experiencing the CPU usage problem; as we speak, GizmoD is pegging one of my cores. I'd like to fix that ;-)
Oh right, sorry I forgot about that! Interesting 3.4 _should_ be in Hardy... I'll have to check that out.
In the mean time... if you need help building a deb let me know, and if you do get some built and don't mind donating them I'd be happy to host them on the sourceforge page!
Thanks,
Tim.
I would be happy to "donate" my compiles.
Having trouble.
I moved the debian_ubuntu_official dir into gizmo3 as "debian"
then I chmod +x debian/rules
then I do "dpkg-buildpackage -rfakeroot -b" and get:
dpkg-buildpackage: source package is gizmod
dpkg-buildpackage: source version is 3.2-0ubuntu1
dpkg-buildpackage: source changed by Joseph Price <pricechild@ubuntu.com>
dpkg-buildpackage: host architecture amd64
dpkg-buildpackage: source version without epoch 3.2-0ubuntu1
fakeroot debian/rules clean
test -x debian/rules
test "`id -u`" = 0
dh_clean
/usr/bin/make -C . -k distclean
make[1]: Entering directory `/home/mjf/gizmod/gizmod3'
make[1]: *** No rule to make target `distclean'.
make[1]: Leaving directory `/home/mjf/gizmod/gizmod3'
make: [makefile-clean] Error 2 (ignored)
rm -f debian/stamp-makefile-build
rm -f debian/stamp-autotools-files
debian/rules build
test -x debian/rules
mkdir -p "."
touch debian/stamp-autotools-files
chmod a+x /home/mjf/gizmod/gizmod3/./configure
chmod: cannot access `/home/mjf/gizmod/gizmod3/./configure': No such file or directory
make: *** [config.status] Error 1
First thing that worries me is "source version is 3.2-0ubuntu1"... is that just a debian/* metadata problem?
Second thing is the error...
So, I moved the actually named "debian" dir from dist instead of the ubuntu one, which worked.
I didn't sign the package; your key is referenced, but of course, I don't have it. I don't know how to make myself a key to sign a package... I can, if it's necessary, but I don't know that anyone would trust me anyway, so not sure that the key helps.
How can I send the packages to you?
That's great! And signing isn't necessary I should think... send them to me via email at: tim [dot] burrell [at] gmail [dot] com.
As for what's going on with the official ubuntu package... not sure. The Ubuntu MOTU team wrote those scripts and to be honest they go beyond my debian packaging abilities :). I'll wait until I hear more about getting 3.4 into hardy -- they'll likely have updated build scripts.
Thanks!