Here is what I came to.
First CC will triger a script on the remote machine which builds deb packages
and copies them to mini-dinstall incoming folder. And here comes the difference.
I do not run mini-dinstall as daemon I call it in batch mode. When it finishes I will scp
the result files to the download machine.
For the purpose of testing I mapped the result files to be visible under apache
and I'm testing with them. But I got an error - after downloading some part of the deb package
apt-get exits with the following error:
Failed to fetch http://…/unstable/sip-communicator_1.0-alpha3-nightly.1600_amd64.deb Size mismatch
Do you have any idea ?
Actually I made a copy of the work you have done on the current CC machine to the new place, including ~/.gnupg files and the scripts for signing.
Martin Andr� wrote:
funny you are talking about that... I was thinking it was time to
officially support amd64 architecture with our debian packages. I've
got a report from a user saying that the package was working fine.
BTW, do you know that I am already uploading nightly builds on a test
(and signed!!!) repository with both x86 and amd64 packages. Check
http://dev.sip-communicator.org/debian/ (it's proxenet).
So everything is there, you just have to change the destination in the
cruisecontrol upload script.
On the destination machine, you'll have to install mini-dinstall, and
it will need to run as a daemon. Check the init script on proxenet (it
doesn't come with the package). Also check my mini-dinstall config
file in /etc/mini-dinstall.
CC upload script on proxenet should invoke dput to upload the package
on the destination machine.
Hope this helps,
Don't hesitate to ask for more information.
On Tue, Dec 16, 2008 at 9:47 PM, Damian Minkov <email@example.com> wrote:
I'm moving the Debian packages to a new (updated) machine. I was looking at
the testing package building that you have made. I mean
those for i386 and amd64.
I saw you are using mini-dinstall. Can it be made so mini-dinstall is not
running as a daemon but invoking it from a script,
cause building of the packages and uploading them will be invoked from
cruisecontrol at proxenet?
And then what is the actual structure I need to copy to
download.sip-communicator.org in order i386 and amd64 debs to work?
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com