Re: Compiling software with same options

2013-01-27 Thread Lanoxx

Hi,

On 27/01/13 07:42, Emmet Hikory wrote:

apt-get source glib2.0
cd glib2.0-*
export QUILT_PATCHES=debian/patches
quilt import ${path-to-new-patch}
quilt push
dch -i
debuild -S -us -uc
cd ..
sbuild -A -d quantal-amd64 ${path-to-updated-dsc}
thanks a lot for this explanation. I tried it and everything works until 
the last step. When I run sbuild, then it get a warning like this:


W: No chroots are defined in ‘/etc/schroot/schroot.conf’ or 
‘/etc/schroot/chroot.d’


And the build finishes with this message:
Finished at 20130127-1604
Build needed 00:00:00, 0k disc space

So it appears that no .deb package was generated, right? Do I need to do 
something to set up the chroots?


Regerds
Lanoxx



--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss


Re: Compiling software with same options

2013-01-27 Thread Emmet Hikory
Lanoxx wrote:
 thanks a lot for this explanation. I tried it and everything works
 until the last step. When I run sbuild, then it get a warning like
 this:
 
 W: No chroots are defined in ‘/etc/schroot/schroot.conf’ or
 ‘/etc/schroot/chroot.d’
 
 And the build finishes with this message:
 Finished at 20130127-1604
 Build needed 00:00:00, 0k disc space
 
 So it appears that no .deb package was generated, right? Do I need
 to do something to set up the chroots?

Yes, to use sbuild, you would need to set up build chroots.  The
sbuild documentation discusses a few ways to do this, and there are
many variations you might find online.  The simplest to document
is to install the ubuntu-dev-tools package and run `mk-sbuild`,
although this makes many assumptions about your environment and
build preferences.

-- 
Emmet HIKORY

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss


Re: Puppet version bump

2013-01-27 Thread John Moser

On 01/26/2013 02:19 PM, John Moser wrote:
I'm noticing that 2.7 is still the version of Puppet in Raring; 
however, version 3.0 was released October 1, 2012, before release of 
12.04:


https://groups.google.com/forum/#!topic/puppet-users/lqmTBX9XDtw/discussion 



Does this package currently not have a maintainer, or is it just slow 
in Debian as well?


3.0 is an important release.  (Every Puppet release is an important 
release; Puppet is rather volatile.)  New features include integration 
of Hiera and deprecation of stored configurations in favor of PuppetDB 
for the same task.  Also the kick feature is deprecated in favor of 
mcollective.  Deprecated features still work, but the transition must 
be made before they become non-existent. You cannot jump from 2.7 to 
future 3.5 without pain; 3.0 still allows some things that are going 
away, but provides their replacements, so you can move smoothly.





OK further research yields that Debian is not updating Sid due to 
feature freeze for Testing.  However, Mathisain notes this:


On the other hand, the master packaging branch at
http://anonscm.debian.org/gitweb/?p=pkg-puppet/puppet.git;a=summary
yields a working set of puppet 3.0.2 debs, they're just not tagged with
a debian release. Feel free to use that until we can upload to sid.

Can we see this imported to 13.04?

--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss


Re: Compiling software with same options

2013-01-27 Thread Lanoxx


On 27/01/13 17:21, Emmet Hikory wrote:

Lanoxx wrote:

thanks a lot for this explanation. I tried it and everything works
until the last step. When I run sbuild, then it get a warning like
this:

W: No chroots are defined in ‘/etc/schroot/schroot.conf’ or
‘/etc/schroot/chroot.d’

And the build finishes with this message:
Finished at 20130127-1604
Build needed 00:00:00, 0k disc space

So it appears that no .deb package was generated, right? Do I need
to do something to set up the chroots?

 Yes, to use sbuild, you would need to set up build chroots.  The
sbuild documentation discusses a few ways to do this, and there are
many variations you might find online.  The simplest to document
is to install the ubuntu-dev-tools package and run `mk-sbuild`,
although this makes many assumptions about your environment and
build preferences.

Thanks a lot. I found some documentation earlier and was able to setup 
the chroot environment. I used [1] with some specific changes to fix 
Ubuntu 12.10 such as


distribution=quantal
mirror=http://at.archive.ubuntu.com/ubuntu

The package has been building for a long time now (must been 30 minutes 
or so). When I tried to install it on my local system just now I was 
told something this:


dpkg: error processing libglib2.0-0:amd64 (--install):
 package libglib2.0-0:amd64 2.34.1-1ubuntu2 cannot be configured 
because libglib2.0-0:i386 is at a different version (2.34.1-1ubuntu1)

dpkg: error processing libglib2.0-0:i386 (--install):
 package libglib2.0-0:i386 2.34.1-1ubuntu1 cannot be configured because 
libglib2.0-0:amd64 is at a different version (2.34.1-1ubuntu2)

Errors were encountered while processing:
 libglib2.0-0:amd64

I guess I need to invest another hour and build the 32bit package as 
well. I find it unbelievable that I need one hour of package building to 
apply a fix that is a single line of code. Particulaly since 'make' 
finishes the task in about a minute.


Regards
Lanoxx

[1] http://wiki.debian.org/sbuild

--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss