| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
#702102)
falling back to /dev/shm doesn't make sense; /dev/shm is a symlink to /run/shm.
rename variable to USERUNSHM instead of USEDEVSHM, we don't need to touch /dev/shm
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
remove netfort target, it's probably not useful to maintain that copy further.
|
| |
|
|
|
| |
It is no longer enabled by default because it doesn't satisfy the
expectation of standard pbuilder behavior.
|
| | |
|
| |
|
|
|
|
| |
/etc/pbuilder/pbuilderrc is a file that you cannot edit and just for
your viewing pleasure, but it's hard to see, and dpkg isn't very
friendly to anyone who edits this file.
|
| | |
|
| |
|
|
| |
messages - pbuilder.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
may choose to enable at the cost of incompatibility and some bugs. (closes: #675691, #675843, #670651)
I could go around fixing all those bugs but I would rather like to not
force everyone to use ccache when ccache is not for everybody.
|
| | |
|
| | |
|
| |
|
|
| |
information to debian/control
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
mirror
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
and confusing.
Just trust autoconfiguration result here.
|
| |
|
|
|
|
|
|
| |
I wasn't sure if I needed to do something for the following, but maybe not:
7.1
Architecture restrictions and wildcards are also allowed in
binary package relationships provided that the binary package is
not architecture-independent.
|
| | |
|
| | |
|
| |
|
|
| |
This reverts commit eac13303c66da4e22447c1132b214593a3865130.
|
| | |
|
| | |
|
| |
|
|
| |
with exit value of 1 instead of 0.
|
| |
|
|
| |
Seems like my regression test was happily claiming to be successful even when things have failed. Hmmm..
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
It's probably useful to see them in the logs.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
deprecation bug
Dixi quod…
>You should not deprecate an option so suddenly, either. I’m
Here’s a possible fix (untested).
From 4fce2898d1d2cf292243316dd9f74b7f5f253a3b Mon Sep 17 00:00:00 2001
From: Thorsten Glaser <tg@mirbsd.org>
Date: Sat, 10 Mar 2012 02:22:10 +0000
Subject: [PATCH] make --check-key and --allow-untrusted into a toggle of each other
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
so that --check-key
A: does not error out (Closes: #663283)
B: is silently accepted
C: has the ability to un-do a previous --allow-untrusted
Signed-off-by: Thorsten Glaser <tg@mirbsd.org>
|
| |
|
|
|
|
| |
I think we don't need the if.
I'm not quite convinced ||true to kill the error message is a good idea
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
On Sat, Dec 24, 2011 at 05:22:05PM +0900, Junichi Uekawa wrote:
> Hi,
>
> I'd use a shell array for specifying the values; but yes I think I
> too wanted this feature at one point.
Attached is a patch that uses a shell array and adds some documentation.
Please apply if you see fit.
> Would list of filename (I will imagine there will be requests for all
> sorts of wildcards after release, which is kind of a pain) be useful
> or a directory that a post-build script can write to after build be
> useful? (I think qemubuilder needed something to do with a specific
> directory that you can write to, but I will need to check how I did
> it).
I'd be great to have this in first and see how others use it. It
wouldn't be a problem to introduce an ADDITIONAL_BUILD_RESULTS_DIR
later.
Cheers,
-- Guido
>From ad3569e07a9cc64cd5b126193cddf311e48180a6 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Guido=20G=C3=BCnther?= <agx@sigxcpu.org>
Date: Mon, 19 Dec 2011 13:31:59 +0100
Subject: [PATCH] Add ADDITIONAL_BUILDRESULTS variable
this can be used to copy additional build results out of the build
directory. It's useful to e.g. preserve a xml testresult file when using
a build system like Jenkins.
|
| | |
|