+++ Ross Gammon [2014-03-01 23:37 +0100]:
Now you have all helped me to realise that I can spam with 'debian/rules
build' to test if it fixes a FTBFS, or 'fakeroot debian/rules binary' to
go all the way to a 'deb' which I can try installing.
(And very usefully, just retry the packaging step
On Sun, 02 Mar 2014 08:38:06 +0100, Ross Gammon wrote:
'gbp
buildpackage' fails because it detects altered files in the source code.
Ah, here it is in the manpage:
--git-export=treeish
Thanks Gregor, but I was already aware of --git-export=WC
--git-ignore-new. I have used this
Can you elaborate a bit on what you mean by having to build a package
multiple times before it builds successfully? With pbuilder, your
package should be able to be built with a single invocation of
pbuilder (given a .dsc) or pdebuild (when unpacked). Anything more
than that and the
Pbuilder also supports that using hooks, e.g.:
# ln -s /usr/share/doc/pbuilder/examples/C10shell
/var/cache/pbuilder/hooks/C10shell
...and the next time your build fails, pbuilder will dump you in the
chroot with a shell.
I checked this solution, but I'm wondering how to resume pbuilder
sbuild also has lots of nifty extra features. One I use a lot is the ability
to locally build a stack of related packages against each other[1].
You can do that in pbuilder (https://wiki.debian.org/PbuilderTricks ;
also allows testing locally-built packages in a pbuilder --login
session), but
+++ Barry Warsaw [2014-02-28 16:42 -0500]:
On Feb 28, 2014, at 10:52 AM, Mikhail Morfikov wrote:
I'm new to building packages by using pbuilder tool, and I have to build
a package multiple times before it builds successfully, or in the way
I prefer.
This is one of the reasons why I prefer
On Sat, Mar 1, 2014 at 5:20 PM, Wookey wrote:
I must admit I'm surprised so many people still use pbuilder, although I
do agree that the syntax is a bit simpler for a 'standard upload' build.
I still use cowbuilder because schroot doesn't support cowdancer for
copy-on-write chroots and I found
On Sat, Mar 1, 2014 at 4:17 AM, Paul Wise p...@debian.org wrote:
If you can convince the pbuilder and sbuild maintainers to work
together to merge all the missing parts of
pbuilder/cowbuilder/qemubuilder into sbuild,
That would be a great adventure!
--
regards,
Mattia Rizzolo
GPG Key:
Paul Wise p...@debian.org writes:
On Sat, Mar 1, 2014 at 5:20 PM, Wookey wrote:
I must admit I'm surprised so many people still use pbuilder, although I
do agree that the syntax is a bit simpler for a 'standard upload' build.
I still use cowbuilder because schroot doesn't support cowdancer
I use a hook withs give me root access to build env when a build is failed
Added this line to .pbuilderrc
HOOKDIR=/var/cache/pbuilder/hook.d
And placed the file C10shell in there with this content:
#!/bin/sh
# invoke shell if build fails.
apt-get install -y --force-yes vim less bash nano
cd
On Sat, Mar 1, 2014 at 10:11 PM, Ferenc Wagner wrote:
I use sbuild (actually, schroot under the hood) with btrfs-snapshot
chroots. Creating a new build environment really is a snap.
Personally I wouldn't feel comfortable using btrfs on my main system
yet and I don't have a separate system
+++ Ferenc Wagner [2014-03-01 15:11 +0100]:
Paul Wise p...@debian.org writes:
On Sat, Mar 1, 2014 at 5:20 PM, Wookey wrote:
I must admit I'm surprised so many people still use pbuilder, although I
do agree that the syntax is a bit simpler for a 'standard upload' build.
I still use
+++ Paul Wise [2014-03-01 23:17 +0800]:
On Sat, Mar 1, 2014 at 10:11 PM, Ferenc Wagner wrote:
By default, the snapshot is destroyed when sbuild finishes in any way.
No chance to damage the origin chroot this way.
If you aren't using any of the snapshot-capable mechanisms it will.
For
* Wookey woo...@wookware.org, 2014-03-01, 15:28:
I still use cowbuilder because schroot doesn't support cowdancer for
copy-on-write chroots and I found tarball mode in pbuilder to be way
too slow.
I use sbuild (actually, schroot under the hood) with btrfs-snapshot
chroots. Creating a new
On Sat, Mar 1, 2014 at 12:18 AM, Mikhail Morfikov mmorfi...@gmail.com wrote:
Pbuilder also supports that using hooks, e.g.:
# ln -s /usr/share/doc/pbuilder/examples/C10shell
/var/cache/pbuilder/hooks/C10shell
...and the next time your build fails, pbuilder will dump you in the
chroot with a
On 03/01/2014 10:46 PM, Vincent Cheng wrote:
On Sat, Mar 1, 2014 at 12:18 AM, Mikhail Morfikov mmorfi...@gmail.com wrote:
Pbuilder also supports that using hooks, e.g.:
# ln -s /usr/share/doc/pbuilder/examples/C10shell
/var/cache/pbuilder/hooks/C10shell
...and the next time your build
On Sat, 01 Mar 2014 23:37:22 +0100, Ross Gammon wrote:
'gbp
buildpackage' fails because it detects altered files in the source code.
Or can I override
gbp buildpackage (with pbuilder as an option) in some way so that it
ignores the fact that there are altered files?
Yes, you can:
==
On 03/02/2014 12:38 AM, gregor herrmann wrote:
On Sat, 01 Mar 2014 23:37:22 +0100, Ross Gammon wrote:
'gbp
buildpackage' fails because it detects altered files in the source code.
Or can I override
gbp buildpackage (with pbuilder as an option) in some way so that it
ignores the fact that
On Fri, Feb 28, 2014 at 1:52 AM, Mikhail Morfikov mmorfi...@gmail.com wrote:
I'm new to building packages by using pbuilder tool, and I have to build
a package multiple times before it builds successfully, or in the way
I prefer. The most annoying part ot this is installation of
dependencies
On Feb 28, 2014 10:52 AM, Mikhail Morfikov mmorfi...@gmail.com wrote:
I'm new to building packages by using pbuilder tool, and I have to build
a package multiple times before it builds successfully, or in the way
I prefer. The most annoying part ot this is installation of
dependencies -- each
On Fri, Feb 28, 2014 at 2:11 AM, Mattia Rizzolo mapr...@ubuntu.com wrote:
On Feb 28, 2014 10:52 AM, Mikhail Morfikov mmorfi...@gmail.com wrote:
I'm new to building packages by using pbuilder tool, and I have to build
a package multiple times before it builds successfully, or in the way
I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
W dniu 28.02.2014 10:52, Mikhail Morfikov pisze:
I'm new to building packages by using pbuilder tool, and I have to build
a package multiple times before it builds successfully, or in the way
I prefer. The most annoying part ot this is
On Feb 28, 2014 11:17 AM, Vincent Cheng vch...@debian.org wrote:
Hmmm, out of curiousity, how is this different from pbuilder-dist (in
ubuntu-dev-tools)?
The concept is the same, but it is quite different:
* integrate support for ccache and apt caching for separate dists (every
dists uses a
You're right. The better way is to use cowbuilder instead of pbuilder.
The first is a wrapper around the latter.
Thanks for the hint.
signature.asc
Description: PGP signature
You shouldn't try to preserve the environment, every time you build
stuff you should have a clean installation.
I know, but when I work with the same package, I think there's no point
in installing the same dependencies over and over. I could save the
chroot, and when I finish playing with the
On Feb 28, 2014, at 10:52 AM, Mikhail Morfikov wrote:
I'm new to building packages by using pbuilder tool, and I have to build
a package multiple times before it builds successfully, or in the way
I prefer.
This is one of the reasons why I prefer to use sbuild for most of my local
builds. You
On Fri, Feb 28, 2014 at 1:42 PM, Barry Warsaw ba...@python.org wrote:
On Feb 28, 2014, at 10:52 AM, Mikhail Morfikov wrote:
I'm new to building packages by using pbuilder tool, and I have to build
a package multiple times before it builds successfully, or in the way
I prefer.
This is one of
On Fri, Feb 28, 2014 at 10:42 PM, Barry Warsaw ba...@python.org wrote:
This is one of the reasons why I prefer to use sbuild for most of my local
builds. You can tell it to preserve the chroot when the build fails, and it's
easy to go in, inspect the build environment, and tweak your package
On Sat, Mar 1, 2014 at 6:31 AM, Mattia Rizzolo wrote:
At this time there is no so much differences between sbuild and pbuilder.
If you can convince the pbuilder and sbuild maintainers to work
together to merge all the missing parts of
pbuilder/cowbuilder/qemubuilder into sbuild, I will buy you
29 matches
Mail list logo
