Signed-off-by: Allan McRae
---
lib/libalpm/be_sync.c |4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/lib/libalpm/be_sync.c b/lib/libalpm/be_sync.c
index f162199..a686def 100644
--- a/lib/libalpm/be_sync.c
+++ b/lib/libalpm/be_sync.c
@@ -511,7 +511,7 @@ static int sync_
Duplicate the fix in config file parsing from d95c0494.
Signed-off-by: Allan McRae
---
src/util/pactree.c | 12 ++--
1 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/src/util/pactree.c b/src/util/pactree.c
index a7dab9f..aa02c80 100644
--- a/src/util/pactree.c
+++ b/src/u
Signed-off-by: Allan McRae
---
src/util/Makefile.am |5 +
1 files changed, 1 insertions(+), 4 deletions(-)
diff --git a/src/util/Makefile.am b/src/util/Makefile.am
index e386d95..8e98324 100644
--- a/src/util/Makefile.am
+++ b/src/util/Makefile.am
@@ -2,15 +2,12 @@
conffile = ${sysconf
Without setting gpgdir, testpkg outputs:
warning: Public keyring not found; have you run 'pacman-key --init'?
Signed-off-by: Allan McRae
---
Note that this uses a compile time patch to the GPGDIR. testpkg does
this for DBPATH too. It is probably not worth allowing these to be
overridden via pa
Set errno to 0 at the start of _alpm_open_archive as it is not set when
archive_read_open_fd fails. This can result in _alpm_pkg_load_internal
thinking errno == ENOENT and setting the wrong pm_errno. e.g.
Before:
> testpkg pacman-4.0.1-4-i686.pkg.tar.gz.sig
error: could not open file pacman-4.0.1
This was the only variable of its kind when a define was done on the
compiler command line. Move it into config.h instead.
Signed-off-by: Allan McRae
---
configure.ac |1 +
src/pacman/Makefile.am |1 -
src/util/Makefile.am |1 -
3 files changed, 1 insertions(+), 2 deleti
Some distributions insist on using bash specific commands in their
install scripts under the assumption that "sh" is a symlink to bash.
This can causes issues if (e.g.) their users what to change sh to
point at another shell, such as dash, that does not support these
features. Add a configure optio
PKGBUILDs are advertised as being pure bash so it would be expected
that the default bash options are in effect when sourcing it.
This inadvertantly "fixes" FS#27780 where enabling extglob causes
the bash parser to error on non-valid bash function names like
package_libxml++(). Note that these fun
On 11/02/12 01:42, Dan McGee wrote:
> On Fri, Feb 10, 2012 at 1:31 AM, Allan McRae wrote:
>> Some distributions insist on using bash specific commands in their
>> install scripts under the assumption that "sh" is a symlink to bash.
>> This can causes issues if (e.g.) their users what to change sh
On Fri, Feb 10, 2012 at 1:31 AM, Allan McRae wrote:
> Some distributions insist on using bash specific commands in their
> install scripts under the assumption that "sh" is a symlink to bash.
> This can causes issues if (e.g.) their users what to change sh to
> point at another shell, such as dash
10 matches
Mail list logo