Re: Compiling software with same options
Lanoxx wrote:
> I have a question regarding the options that are used to build the
> source code of a package, there are often some options that can be
> passed to either ./autogen.sh or ./configure which influence what
> module are build or how a libarary or program is build. How can I
> find out which options were used originally when the package was
> build by Ubuntu?
>
> For example I would like to rebuild the glib2.0-x source from Ubuntu
> 12.10 with a small patch. I have already downloaded patched and
> compiled the Ubuntu source of glib2.0 with:
>
> apt-get source glib2.0-...
> //apply patch ...
> ./autogen.sh --prefix=/opt/... && make && sudo make install
>
> And now I want to compile and install it into the prefix=/usr for
> fix the bug on the system.
>
> However given that glib is quite an essential library I am a bit
> afraid that I am forgetting some important options and that
> something might be broken afterwards. Could anyone give me a hint
> how to properly compile this package?
Compilation and build of Debian-format packages is controlled by
the debian/control and debian/rules files. Chapters 4 and 5 of Debian
Policy describe these in some detail. For best results, you would want
to add your patch to those already being applied in the packaging, build
an updated source package, and create binary packages with sbuild, pbuilder,
or a PPA (or other archive build system). In the specific case of glib-2.0,
one set of commands to accomplish this would be:
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}
For quick local testing, you may often approximate this by ensuring
that all the Build-Depends, Build-Depends-Indep, and Built-Using packages
are installed and that none of the Build-Conflicts or Build-Conflicts-Indep
packages are installed, applying your patch, updating the changelog, and
running `dpkg-buildpackage -us -uc -b` (or calling debian/rules targets
directly if you prefer). Note that the results of this procedure may differ
from that above due to differences between your local system and the pristine
environments used by build management tools, so this may not be a complete
test of how the patch would integrate if applied to the package generally.
--
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
Sorry, this got caught in the moderator queue On Sat, Jan 26, 2013 at 3:05 PM, John Moser wrote: > The only interesting assumptions > are that either the Ubuntu or the Debian maintainers (or both) aren't paying > attention; it's not like puppet gets as much focus as openssh or firefox. Or... Debian is frozen for Wheezy and puppet 3 is stuck in experimental [1] since it can't be uploaded to unstable until after Debian Wheezy is released. Adding to that, the packaged version in experimental isn't puppet release version 3, but the RC. This is a case of when Ubuntu syncing to a frozen Debian unstable causes slow updating. The best way to get it into 13.04: 1) Puppet Package Maintainers updates experimental to version 3. It looks like they are working on it [2]. 2) Ubuntu merges experimental to 13.04 ~Scott [1] http://packages.qa.debian.org/p/puppet.html [2] http://anonscm.debian.org/gitweb/?p=pkg-puppet/puppet.git -- 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
On Sat, Jan 26, 2013 at 4:05 PM, John Moser wrote: > On 01/26/2013 04:01 PM, Tom H wrote: >> On Sat, Jan 26, 2013 at 2:19 PM, John Moser >> wrote: >>> >>> Does this package currently not have a maintainer, or is it just slow in >>> Debian as well? >> >> There were two puppet 3.0.0-rcX uploads to Debian experimental in May >> and they'll move to unstable, and therefore be inheritable by Ubuntu, >> once Debian 7's released. > > They're past -rc, it's at 3.0.2 now. I would avoid an -rc update; at least > 3.0.0 stable. Upstream may be past -rc but Debian isn't (the last upload was may 24th). -- 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
On 01/26/2013 04:01 PM, Tom H wrote: On Sat, Jan 26, 2013 at 2: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: I assume that you mean 13.04. I meant 12.10. Point being this stuff was out before the last version was released, should have been a bump after release since all the feature freezes come off for the new dev cycle. the numbers. They flip flop a lot. These are not the binary digits you are looking for. 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? There were two puppet 3.0.0-rcX uploads to Debian experimental in May and they'll move to unstable, and therefore be inheritable by Ubuntu, once Debian 7's released. They're past -rc, it's at 3.0.2 now. I would avoid an -rc update; at least 3.0.0 stable. -- 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
On Sat, Jan 26, 2013 at 2: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: I assume that you mean 13.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? There were two puppet 3.0.0-rcX uploads to Debian experimental in May and they'll move to unstable, and therefore be inheritable by Ubuntu, once Debian 7's released. -- 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
On 01/26/2013 02:29 PM, Jordon Bedwell wrote: On Sat, Jan 26, 2013 at 1: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 12.04 was released on 26/4/12 not in October. 12.10 was released in Yes typo, can't keep number straight in my head like this. October and Puppets release was after the feature freeze. You will need to wait until 13.04. It has nothing to do with being slow, it has to do with them either releasing before the feature freeze or having to wait until the next release cycle. Typically a feature It is still 2.7 in 13.04 http://packages.ubuntu.com/raring/admin/puppet freeze happens 1-2 months before release... so if puppet releases 3.0 in October there is no reason for it to make it into 12.10 (in that case) because there were probably no super important security updates that mandated an extreme exception. No, but there is reason to immediately update it in 13.04 after dropping the 12.10 release. Packages are available in their own repositories, as well as source debs and SRPMs. It makes little sense for a package that was outdated before the last release of Ubuntu to remain in the current release, in Main, when there is a compelling reason to update the package. The only interesting assumptions are that either the Ubuntu or the Debian maintainers (or both) aren't paying attention; it's not like puppet gets as much focus as openssh or firefox. -- 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
Compiling software with same options
Hi, I have a question regarding the options that are used to build the source code of a package, there are often some options that can be passed to either ./autogen.sh or ./configure which influence what module are build or how a libarary or program is build. How can I find out which options were used originally when the package was build by Ubuntu? For example I would like to rebuild the glib2.0-x source from Ubuntu 12.10 with a small patch. I have already downloaded patched and compiled the Ubuntu source of glib2.0 with: apt-get source glib2.0-... //apply patch ... ./autogen.sh --prefix=/opt/... && make && sudo make install And now I want to compile and install it into the prefix=/usr for fix the bug on the system. However given that glib is quite an essential library I am a bit afraid that I am forgetting some important options and that something might be broken afterwards. Could anyone give me a hint how to properly compile this package? Regards -- 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
On Sat, Jan 26, 2013 at 1: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 12.04 was released on 26/4/12 not in October. 12.10 was released in October and Puppets release was after the feature freeze. You will need to wait until 13.04. It has nothing to do with being slow, it has to do with them either releasing before the feature freeze or having to wait until the next release cycle. Typically a feature freeze happens 1-2 months before release... so if puppet releases 3.0 in October there is no reason for it to make it into 12.10 (in that case) because there were probably no super important security updates that mandated an extreme exception. -- 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
Puppet version bump
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. -- 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
