Rebuilding pve-installer_2009-01-15.deb

briankwest

Member
Feb 7, 2009
59
0
6
I'm trying to learn more how proxmox is built so I can do a couple of customizations for my own needs. Unfornately some of the files required to build the packages are missing.

For example

make packages
make: *** No rule to make target `/pve/1.1/install/pve.files', needed by `packages'. Stop.


Seems you can't build a fully functional custom install CD using the source provided. Is this intentional?

/b
 
Seems you can't build a fully functional custom install CD using the source provided. Is this intentional?

yes, because it depends on too many local resources. We create and test the CDs with great care, to get the expected quality.

Also, proxmox tries to provide a well defined environment. Doing customisation at installer level is not our primary goal.

But why dont yo tell use what you miss?

- Dietmar
 
I want to learn how its all put together... I can't do that without all the tools to do so. You're projecting an image of Open Source but only going half way. The entire build environment should be there for everyone to toy with. I understand your need to build a stable environment but I want to do some more invasive things related to Telephony and without being able to build an installer from scratch it doesn't do me much good. I'm more than willing to push any changes and ideas back upstream which is what Open Source is about. Right now you can't even build vncterm deb it fails on debian... Just to name a few.

/b
 
Right now you can't even build vncterm deb it fails on debian... Just to name a few.

All sources are available at:

ftp://pve.proxmox.com/sources/

So why cant you build vncterm? If it really fails you can:

a.) report a bug

b.) resolve the issue yourself and provide a patch.

Simply moaning is not enough.

- Dietmar

 
I'm simply pointing out you're benefiting from open source and to only give half isn't within the spirit of Open Source. I thought I would try to recreate the ISO from scratch and found its impossible. I'm not moaning.. I'm simply pointing out the obvious failure to comply with the spirit of Open Source.

Here is the compile error
gcc -g -o vncterm vncterm.c -Wall -D_GNU_SOURCE `libvncserver-config --cflags` `libvncserver-config --libs` -lutil
vncterm.c: In function 'vncterm_kbd_event':
vncterm.c:1311: error: 'XK_Shift_L' undeclared (first use in this function)
vncterm.c:1311: error: (Each undeclared identifier is reported only once
vncterm.c:1311: error: for each function it appears in.)
vncterm.c:1311: error: 'XK_Shift_R' undeclared (first use in this function)
vncterm.c:1313: error: 'XK_Control_L' undeclared (first use in this function)
vncterm.c:1313: error: 'XK_Control_R' undeclared (first use in this function)
vncterm.c:1326: error: 'XK_Escape' undeclared (first use in this function)
vncterm.c:1328: error: 'XK_Return' undeclared (first use in this function)
vncterm.c:1330: error: 'XK_BackSpace' undeclared (first use in this function)
vncterm.c:1332: error: 'XK_Tab' undeclared (first use in this function)
vncterm.c:1334: error: 'XK_Delete' undeclared (first use in this function)
vncterm.c:1335: error: 'XK_KP_Delete' undeclared (first use in this function)
vncterm.c:1337: error: 'XK_Home' undeclared (first use in this function)
vncterm.c:1338: error: 'XK_KP_Home' undeclared (first use in this function)
vncterm.c:1340: error: 'XK_End' undeclared (first use in this function)
vncterm.c:1341: error: 'XK_KP_End' undeclared (first use in this function)
vncterm.c:1343: error: 'XK_Insert' undeclared (first use in this function)
vncterm.c:1344: error: 'XK_KP_Insert' undeclared (first use in this function)
vncterm.c:1346: error: 'XK_Up' undeclared (first use in this function)
vncterm.c:1347: error: 'XK_KP_Up' undeclared (first use in this function)
vncterm.c:1349: error: 'XK_Down' undeclared (first use in this function)
vncterm.c:1350: error: 'XK_KP_Down' undeclared (first use in this function)
vncterm.c:1352: error: 'XK_Right' undeclared (first use in this function)
vncterm.c:1353: error: 'XK_KP_Right' undeclared (first use in this function)
vncterm.c:1355: error: 'XK_Left' undeclared (first use in this function)
vncterm.c:1356: error: 'XK_KP_Left' undeclared (first use in this function)
vncterm.c:1358: error: 'XK_Page_Up' undeclared (first use in this function)
vncterm.c:1364: error: 'XK_Page_Down' undeclared (first use in this function)
vncterm.c:1370: error: 'XK_F1' undeclared (first use in this function)
vncterm.c:1372: error: 'XK_F2' undeclared (first use in this function)
vncterm.c:1374: error: 'XK_F3' undeclared (first use in this function)
vncterm.c:1376: error: 'XK_F4' undeclared (first use in this function)
vncterm.c:1378: error: 'XK_F5' undeclared (first use in this function)
vncterm.c:1380: error: 'XK_F6' undeclared (first use in this function)
vncterm.c:1382: error: 'XK_F7' undeclared (first use in this function)
vncterm.c:1384: error: 'XK_F8' undeclared (first use in this function)
vncterm.c:1386: error: 'XK_F9' undeclared (first use in this function)
vncterm.c:1388: error: 'XK_F10' undeclared (first use in this function)
vncterm.c:1390: error: 'XK_F11' undeclared (first use in this function)
vncterm.c:1392: error: 'XK_F12' undeclared (first use in this function)
make: *** [vncterm] Error 1


I would assume it would complain about a missing header file if a package were missing but its not.

/b
 
I also noticed that Fedora 10 instances failed to set the IP address from the GUI... I had to go do it by hand.

/b
 
I'm simply pointing out you're benefiting from open source and to only give half isn't within the spirit of Open Source. I thought I would try to recreate the ISO from scratch and found its impossible. I'm not moaning.. I'm simply pointing out the obvious failure to comply with the spirit of Open Source.

Again, all packages are available at:

ftp://pve.proxmox.com/sources/

You can find even the installer sources there.

Whats missing is a 20 lines Makefile which assembles the CD. We don't plan to release that because it depends on too many local resources (not ready for release now).

But there are plans to extend the Debian appliance builder (dab) to create iso images, but currently we do not have enough resources to do that. But I agree with you, that would be a valuable extension.

I would assume it would complain about a missing header file if a package were missing but its not.

Please can you provide some more information. What system are you one?

- Dietmar
 
Its out there the CentOS project uses it. I'm sure if I email my friends over there they'll tell me exactly where to get it from.

/b
 
The centos guys have the exact build env. rehat uses.. thats how they are able to recreate a binary compatible build system... seriously I know some of the guys on the project that had to take legal action to get some of the info out of redhat. Now redhat helps the centos project a lot more than it used too.

/b
 
CentoS are the guys simply copying another distribution, not contributing a simgle line of code to the community.

So you are talking about that kind of open source spirit?

- Dietmar
 
The bottom line is.. you CAN recreate the entire redhat build system, iso and tool chain from the SRPM's they provide. You however can't reproduce the proxmox ve ISO with the source you have released.

Anyway I have lost interest in the entire project. I wanted to build an iso that would act as a build farm out of the box for 64bit, 32bit for building RPM's, debs and such for the various distros. I too run an Open Source project and we give all our code away... I'm just looking to stream line the automated build testing after svn commits in a way that lets me build all binary packages every few hours... I also want to be able to recreate the build server with minimal effort on the fly.. hence the reason I want to build a custom ISO.

/b
 
Anyway I have lost interest in the entire project. I wanted to build an iso that would act as a build farm out of the box for 64bit, 32bit for building RPM's, debs and such for the various distros. I too run an Open Source project and we give all our code away... I'm just looking to stream line the automated build testing after svn commits in a way that lets me build all binary packages every few hours... I also want to be able to recreate the build server with minimal effort on the fly.. hence the reason I want to build a custom ISO.

Proxmox VE is a platform to run virtual server. So it is clearly not what you want.

- Dietmar
 
Thats where you're wrong the CentOS project has given back to the community.

I run an open source project and know how this stuff is... you have only a small percentage of people that actually give back anything and the others just leech off your work... I fall into the group that actually gives back. If you want to act like its a big deal to actually document how to recreate the entire ISO from scratch thats your choice.

/b
 
yes it is clearly what I want... It would let me run every distro... I currently use it on CentOS to accomplish the same goal the only problem is the CentOS kernels are lagging behind so Fedora 10 is a pain to get working. I'll go to using ubuntu's OpenVZ kernel and utils then.

Thanks,
/b
 
Thats where you're wrong the CentOS project has given back to the community.

Well, thats the info they provide on the web site:

CentOS mainly changes packages to remove upstream vendor branding and artwork.

That is the real Open Source spirit?
 
You know this isn't about CentOS its about YOU and your project. CentOS has done more for me than your project has thus far. I'm going to solve my problems other ways. You have a good day!

Thanks for your time.
/b
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!