Just got the new install.sh and a fresh build of Ubuntu 6.06.1 64bit and the installer seems to be hanging - if it’s not, it sure isn’t telling me anything useful.
from standard out:
[code:1]INFO - Removing Debian apache packages…
INFO - Installing dependencies using command: /usr/bin/apt-get --config-file apt.conf.noninteractive -y --force-yes install postfix postfix-pcre webmin usermin ruby libapache2-mod-ruby libxml-simple-perl libcrypt-ssleay-perl
INFO - …in progress, please wait…
Tailing the log file:
0 upgraded, 30 newly installed, 0 to remove and 30 not upgraded.
Need to get 21.2MB/30.7MB of archives.
After unpacking 377MB disk space will be freed.
WARNING: The following packages cannot be authenticated!
Get:1 http://software.virtualmin.com virtualmin-dapper/main usermin 1.280 [5158kB]
It seems to hang there - could this be an authentication issue to the repository?
Open to ideas, seems like this is taking way too long to do this initial install, I let it run for about an hour earlier.
Looks like Ubuntu is waiting for input on installing unauthenticated packages. It didn’t used to do that. The packages are actually signed, but I can’t figure out how to tell apt-get (or dpkg, or whoever it is I have to tell) about the keys.
Since the script is non-interactive and sucks up most of the output to the log file, there’s no way to tell apt-get or dpkg or whoever, to install it anyway.
This is a problem. I’m working on it. In the meantime, I can drop in and run installation through for you, if you’d like. It’s also possible to run the steps manually–on Ubuntu and Debian, there’s actually very little being done by the install.sh…most of the code that gets run is just figuring out what OS it’s running on.
The only tricky bit is getting the apt sources right, with the serial number and license key in the right places. Once that’s done, it’s just a couple of commands to install all of the parts.
Thanks Joe, I imagine I could step through the manual process, but I would feel more comfortable with the pro driving. What is the best way to get you the info?
Thanks and awesome quick reply.
Email is fine email@example.com
The packages are actually signed, but I can't figure out how to tell apt-get (or dpkg, or whoever it is I have to tell) about the keys.
curl http://location/of/key.asc | apt-key add -
The repository also needs to be structured correctly and have some other files in it be generated and signed. That took me a few tries to figure out after I started providing packages for wxPython. Every time I moved the repository to a new server I tried a different way to do it, I think my users probably got a bit tired of it. I finally got it right when I moved it to my server managed by Virtualmin. Coincidence? Maybe, maybe not… Anyway, let me know if you need it and I can share some scripts I use to automate most of the building of the repository.
Awesome! Thanks for the tips Robin. I’ll add that to the install.sh today.
I’m also in the midst of trying to get our repos switched from “simple” to “pool”, so I don’t have 6 identical copies of all of the pure-Perl packages…I don’t guess you have any wisdom on that handy?
The official docs about packaging for Debian/Ubuntu are amazing…they’re huge. Dozens of pages. And I have never actually been able to figure out anything from them. Every bit of knowledge I have about packaging debs came from scouring the web or asking on IRC or a mailing list. Those guys hate examples more than even the GNU info page authors (for whom I believe “Thou shalt provide no useful examples” is the first commandment).
Nah, I don’t use pools since most of my files are binary and so I would have to give different version or release numbers to each of the distros in order to have them all in the same pool.