Home | Bug Tracker | Wiki | Mailing Lists | Forums    
   Username:  Password:  Signup
   
   Main Menu
· Home
· Search
· Site Stats
   Donate to Parsix
Help us to move faster and make a better system for you. Donations are highly appreciated.

Donations Sum: $ 400,00
   Search
   Download
· SF.Net Mirrors
   Bug Report
Help us to fix problems and defects. Please report bugs here.
   Online Users
Admin
No Online Admins
Members:Online
Members:Members:0
Guests:Guests:34
Total:Total:34
Online Members
No online members
   Sponsored Links



Post new topic   Reply to topic
View previous topic Printable version Log in to check your private messages View next topic
Author Message
pelle.kOffline
Post subject: pbuilder and packaging guidelines  PostPosted: Feb 23, 2008 - 02:38 AM



Joined: Feb 23, 2008
Posts: 25
Location: Sweden
Status: Offline
I have been building some packages using pbuilder for a while now without really doing it "proper". (using debian as mirrorsite)
So i tried to set up a pbuilderrc of my own to override some settings, and i can't really get past the debootstrap "downloading release" state. I tried MIRRORSITE=http://packages.parsix.org/official (it's the only thing i could think of), and that doesn't work....

So my question is, what variables do i have to change/override to have a "proper" setup for building packages in "ramon"?
Also, what is the difference between "official" and "continent"?

Another question would be what guidelines do you follow when building packages? I've seen many changelogs marked with "unstable" even though this would be "testing/lenny" or to be even more precise - "ramon".

Maybe you should package pbuilder with an example config for parsix with the next release?
Thanks in advance.
 
 View user's profile Send private message  
Reply with quote Back to top
alanOffline
Post subject: RE: pbuilder and packaging guidelines  PostPosted: Feb 24, 2008 - 03:49 AM
Developer
Developer


Joined: Jan 25, 2005
Posts: 325
Location: Glendale, California
Status: Offline
Quote:
I have been building some packages using pbuilder for a while now without really doing it "proper". (using debian as mirrorsite)
So i tried to set up a pbuilderrc of my own to override some settings, and i can't really get past the debootstrap "downloading release" state. I tried MIRRORSITE=http://packages.parsix.org/official (it's the only thing i could think of), and that doesn't work....


Use http://packages.parsix.org/continent as primary and http://packages.parsix.org/official as secondary mirror.



Quote:
So my question is, what variables do i have to change/override to have a "proper" setup for building packages in "ramon"?
Also, what is the difference between "official" and "continent"?


official repository contains packages supported and packages by Parsix team and continent is the whole Debian testing repository except official packages. Continent is going to be frozen for Ramon, after r1 release. Then continent will be updated only for Viola (Parsix 1.5)

Quote:
Another question would be what guidelines do you follow when building packages? I've seen many changelogs marked with "unstable" even though this would be "testing/lenny" or to be even more precise - "ramon".


In Debian, packages migrate from unstable->testing->stable, even in stable change logs, you will see word `unstable`. We use Debian standards and guidelines. We have a simple build server to build packages straight from the SVN repository: http://svn.debian.org/wsvn/pkg-parsix/scripts/buildd/

Quote:
Maybe you should package pbuilder with an example config for parsix with the next release?
Thanks in advance.


Check out the build server code that uses pbuilder to build packages.
 
 View user's profile Send private message Send e-mail Visit poster's website  
Reply with quote Back to top
pelle.kOffline
Post subject: RE: pbuilder and packaging guidelines  PostPosted: Feb 25, 2008 - 03:39 PM



Joined: Feb 23, 2008
Posts: 25
Location: Sweden
Status: Offline
Thanks for taking the time clearing things up.
I tried to mimic the buildscript when creating the bootstrap
Code:
~$ sudo pbuilder --create --distribution ramon --override-config --debootstrap debootstrap --mirror "http://packages.parsix.org/continent" --othermirror "deb http://packages.parsix.org/official ramon main contrib non-free"
Distribution is ramon.
Building the build environment
 -> running debootstrap
/usr/sbin/debootstrap
E: No such script: /usr/share/debootstrap/scripts/ramon
pbuilder: debootstrap failed
 -> Aborting with an error
 -> cleaning the build env
    -> removing directory /var/cache/pbuilder/build//18755 and its subdirectories

So obviously i'm doing something wrong? Smile [edit]i've also tried lenny as --distribution[/edit]
 
 View user's profile Send private message  
Reply with quote Back to top
alanOffline
Post subject: RE: pbuilder and packaging guidelines  PostPosted: Feb 25, 2008 - 05:47 PM
Developer
Developer


Joined: Jan 25, 2005
Posts: 325
Location: Glendale, California
Status: Offline
Code:

# cd /usr/share/debootstrap/scripts/
# ln -s sid ramon


Smile
 
 View user's profile Send private message Send e-mail Visit poster's website  
Reply with quote Back to top
pelle.kOffline
Post subject:   PostPosted: Feb 26, 2008 - 08:09 PM



Joined: Feb 23, 2008
Posts: 25
Location: Sweden
Status: Offline
Allright! (It wasn't self-explainatory though...)
I hate to bother you with this other problem, but since i can't seem to figure this one out as well;
Code:
...<SNIP>...
I: Extracting util-linux...
I: Extracting zlib1g...
W: Failure trying to run: chroot /var/cache/pbuilder/build/17994/. mount -t proc proc /proc
pbuilder: debootstrap failed
 -> Aborting with an error
 -> cleaning the build env
    -> removing directory /var/cache/pbuilder/build//17994 and its subdirectories

Since i use sudo i thought this was related to not being root, but unfortunately that doesn't work either.
 
 View user's profile Send private message  
Reply with quote Back to top
alanOffline
Post subject:   PostPosted: Feb 27, 2008 - 03:12 AM
Developer
Developer


Joined: Jan 25, 2005
Posts: 325
Location: Glendale, California
Status: Offline
Mmm... try to build the base.tgz using debian mirrors only the update the base.tgz using parsix repos. This might fix the problem.
 
 View user's profile Send private message Send e-mail Visit poster's website  
Reply with quote Back to top
pelle.kOffline
Post subject:   PostPosted: Feb 27, 2008 - 10:36 AM



Joined: Feb 23, 2008
Posts: 25
Location: Sweden
Status: Offline
Seems to work allright. I used lenny as --distribution using the standard debian repos, then updated to ramon. Seems to work allright.
Thanks for the help! Smile
 
 View user's profile Send private message  
Reply with quote Back to top
pelle.kOffline
Post subject:   PostPosted: Mar 13, 2008 - 04:03 PM



Joined: Feb 23, 2008
Posts: 25
Location: Sweden
Status: Offline
Any chance this will get fixed, since it's a bit ugly to create a "lenny" base.tgza nd then updating it tp "ramon"?
btw, is "etch" a better choice if parsix will be frozen, since "lenny" will install newer packages, and thus keep "ramon" packages out of the base.tgz?
 
 View user's profile Send private message  
Reply with quote Back to top
alanOffline
Post subject:   PostPosted: Mar 13, 2008 - 04:48 PM
Developer
Developer


Joined: Jan 25, 2005
Posts: 325
Location: Glendale, California
Status: Offline
I'll work on the problem, but you cab use Viola repos to keep updates come and come and come Smile
 
 View user's profile Send private message Send e-mail Visit poster's website  
Reply with quote Back to top
alanOffline
Post subject:   PostPosted: Mar 17, 2008 - 08:10 PM
Developer
Developer


Joined: Jan 25, 2005
Posts: 325
Location: Glendale, California
Status: Offline
This problem has been solved for Ramon and Viola apt repositories
 
 View user's profile Send private message Send e-mail Visit poster's website  
Reply with quote Back to top
pelle.kOffline
Post subject:   PostPosted: Mar 18, 2008 - 04:11 PM



Joined: Feb 23, 2008
Posts: 25
Location: Sweden
Status: Offline
alan wrote:
This problem has been solved for Ramon and Viola apt repositories

I'm afraid that unless i'm missing something, this is what happens on both viola *and* ramon;
Code:
...snip...
I: Configuring g++...
W: Failure while configuring base packages.
W: Failure while configuring base packages.
W: Failure while configuring base packages.
W: Failure while configuring base packages.
W: Failure while configuring base packages.
pbuilder: debootstrap failed
 -> Aborting with an error
 -> cleaning the build env
    -> removing directory /var/cache/pbuilder/build//3865 and its subdirectories

This is my .pbuilderrc
Code:
DEBOOTSTRAP="debootstrap"
# Default distribution
DISTRIBUTION=viola
COMPONENTS="main contrib non-free"
# Repositories
MIRRORSITE=http://packages.parsix.org/continent
OTHERMIRROR="deb http://packages.parsix.org/official viola main contrib non-free"


I *do* appreciate your effort though. Just wanted to let you know.
It's probably just me, doing something wrong i guess Smile
 
 View user's profile Send private message  
Reply with quote Back to top
pelle.kOffline
Post subject:   PostPosted: Mar 30, 2008 - 05:17 PM



Joined: Feb 23, 2008
Posts: 25
Location: Sweden
Status: Offline
I took the time to try building a base tgz again, and what do you know - it works! It is certainly nice to have a clean building enviroment, straight from the parsix repos (as was originally intended).

Thanks for all the time you put into this alan Smile
 
 View user's profile Send private message  
Reply with quote Back to top
pelle.kOffline
Post subject:   PostPosted: Jul 06, 2008 - 06:35 PM



Joined: Feb 23, 2008
Posts: 25
Location: Sweden
Status: Offline
Hey, just as update on viola;
Code:
I: Base system installed successfully.
 -> debootstrap finished
 -> copying local configuration
  -> Installing apt-lines
W: no hooks of type G found -- ignoring
Refreshing the base.tgz
 -> upgrading packages
 -> mounting /proc filesystem
 -> mounting /dev/pts filesystem
-> Mounting /home/pelle/temp/parsix-build/result
 -> installing dummy policy-rc.d
chroot: cannot run command `/usr/bin/apt-get': No such file or directory
 -> Aborting with an error
 -> unmounting /home/pelle/temp/parsix-build/result filesystem
 -> unmounting dev/pts filesystem
 -> unmounting proc filesystem
 -> cleaning the build env
    -> removing directory /var/cache/pbuilder/build//6094 and its subdirectories

Any thoughts on that alan?
my pbuilderrc looks identical to the one two posts above.
[edit]not trying to build anything, just "creating" the base.tgz[/edit]
 
 View user's profile Send private message  
Reply with quote Back to top
alanOffline
Post subject:   PostPosted: Jul 10, 2008 - 08:15 AM
Developer
Developer


Joined: Jan 25, 2005
Posts: 325
Location: Glendale, California
Status: Offline
I wonder why apt package is not being installed there! Let me check out what's going wrong there.
 
 View user's profile Send private message Send e-mail Visit poster's website  
Reply with quote Back to top
Display posts from previous:     
Jump to:  
All times are GMT + 3.5 Hours
Post new topic   Reply to topic
View previous topic Printable version Log in to check your private messages View next topic
Copyright© 2005-2007 Parsix Project
Contact: webmaster AT parsix DOT org