proyvind commented on this pull request.
> @@ -0,0 +1,14 @@
+#!/bin/sh
+
+# If using normal root, avoid changing anything.
+if [ -z "$RPM_BUILD_ROOT" -o "$RPM_BUILD_ROOT" = "/" ]; then
+ exit 0
+fi
+
+find "$RPM_BUILD_ROOT" \( -type f -o -type l \) -name \*.la -print0 |
+xargs
proyvind commented on this pull request.
> @@ -0,0 +1,14 @@
+#!/bin/sh
+
+# If using normal root, avoid changing anything.
+if [ -z "$RPM_BUILD_ROOT" -o "$RPM_BUILD_ROOT" = "/" ]; then
+ exit 0
+fi
+
+find "$RPM_BUILD_ROOT" \( -type f -o -type l \) -name \*.la -print0 |
+xargs
ldv-alt requested changes on this pull request.
> @@ -0,0 +1,14 @@
+#!/bin/sh
+
+# If using normal root, avoid changing anything.
+if [ -z "$RPM_BUILD_ROOT" -o "$RPM_BUILD_ROOT" = "/" ]; then
+ exit 0
+fi
+
+find "$RPM_BUILD_ROOT" \( -type f -o -type l \) -name \*.la -print0 |
+xargs
@proyvind pushed 1 commit.
12e9521 add disabler for brp-compress
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
@proyvind pushed 1 commit.
0d496d8 add brp script to check elf files for unresolved symbols and unused
libs
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
@proyvind pushed 1 commit.
a469648 add brp script for automatically creating library symlinks using
ldconfig
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
proyvind commented on this pull request.
> @@ -0,0 +1,15 @@
+#!/bin/sh
+
+# If using normal root, avoid changing anything.
+if [ -z "$RPM_BUILD_ROOT" -o "$RPM_BUILD_ROOT" = "/" ]; then
+ exit 0
+fi
+
+INFODIR=`rpm --eval %{_infodir}/dir`
+
+dir="$RPM_BUILD_ROOT/$INFODIR"
+
+if [ -f $dir
proyvind commented on this pull request.
> @@ -0,0 +1,49 @@
+#!/bin/sh
+
+# This script makes sure to remove any standard library search paths from rpath
+# or runpath tags as they're not only redundant, but will break overriding
+# search paths. Search paths of the tag that's not standard will
ignatenkobrain commented on this pull request.
> @@ -0,0 +1,14 @@
+#!/bin/sh
+
+# If using normal root, avoid changing anything.
+if [ -z "$RPM_BUILD_ROOT" -o "$RPM_BUILD_ROOT" = "/" ]; then
+ exit 0
+fi
+
+find "$RPM_BUILD_ROOT" \( -type f -o -type l \) -name \*.la -print0 |
nice one
ignatenkobrain commented on this pull request.
> @@ -0,0 +1,15 @@
+#!/bin/sh
+
+# If using normal root, avoid changing anything.
+if [ -z "$RPM_BUILD_ROOT" -o "$RPM_BUILD_ROOT" = "/" ]; then
+ exit 0
+fi
+
+INFODIR=`rpm --eval %{_infodir}/dir`
+
+dir="$RPM_BUILD_ROOT/$INFODIR"
+
+if [ -f
ignatenkobrain commented on this pull request.
> @@ -70,6 +70,15 @@
%{_rpmconfigdir}/brp-strip %{__strip} \
%{_rpmconfigdir}/brp-strip-static-archive %{__strip} \
%{_rpmconfigdir}/brp-strip-comment-note %{__strip} %{__objdump} \
+%{?!dont_clean_files: [ -n
I've added most of the helper scripts, there's a few remaining and some I'll
have to consider whether to kill off in stead before done.
Anyways, I'm making a preliminary pull request as a request for comments.
Notice how all these scripts can either be disabled by setting an environment
I am not user of %auto{patch,setup} but I hate the backup files around. I
really don't see any reason for their existence. And I saw quite some packages
shipping them accidentally ...
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it
hey @pmatilai - i'm using fedora 24 with:
```
$ rpm -q rpm rpm-sign gnupg2 gnupg
rpm-4.13.0-1.fc24.x86_64
rpm-sign-4.13.0-1.fc24.x86_64
gnupg2-2.1.13-2.fc24.x86_64
gnupg-1.4.21-1.fc24.x86_64
```
my DISPLAY variable is unset but my `TERM` is `screen-256color`. What is odd
that I am trying to
pmatilai requested changes on this pull request.
I'm actually in favor of enabling backups by default. However this patch
clearly hasn't been tested, nor reviewed, at all. It refers to a non-existent
patches_num variable so any attempt to use %autosetup with this patch ends up
in:
`error:
pmatilai requested changes on this pull request.
I'm actually in favor of enabling backups by default. However this patch
clearly hasn't been tested, nor reviewed, at all. It refers to a non-existent
patches_num variable so any attempt to use %autosetup with this patch ends up
in:
`error: lua
I dont see any *real* reasons against backups by default here. The default
should be the most useful one, and the way I see it for those living with
gendiff for one reason or another backups are a must. In my experience the only
reason NOT to create backups is stupid (often perl) projects which
@pmatilai I'm tempted to not modify the default backend because of reasons
mentioned by @soig and @ignatenkobrain in #109. But let me see what I can do
about introducing an alternative backend that creates patch backups.
--
You are receiving this because you are subscribed to this thread.
Yup. Or actually the other way around: have the default "patch" version create
backups because that's more in line with the other backends, and add another
backend like patch_nobackup (gosh I hate that name) for the no-backup case.
--
You are receiving this because you are subscribed to this
@pmatilai so you'd want instead a `-S patchbackup` backend instead of using
`-B` at `%autosetup`/`%autopatch`?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
So actually I think this is best handled by having two separate backends
(similar to git and git_am) where one creates backups and the other one
doesn't. That way there's no need to introduce new option that is specific to
one backend only.
--
You are receiving this because you are subscribed
My issue with this is that it adds an option that is by definition only
relevant to a single "backend" of %autosetup, and the most uninteresting one at
that. I'm all for supporting backups for plain patch, doing them was actually
always part of the plan only never implemented.
--
You are
OTOH the pinentry bug doesn't explain behavior change with different %_gpg_name
value. Can you reproduce the problem if you explicity set TERM to something, eg
`TERM=xterm rpm --addsign ./grub2-2.02-0.38.fc25.dusty.x86_64.rpm`
--
You are receiving this because you are subscribed to this
Okay, this is actually a bug in pinentry, see
https://bugs.gnupg.org/gnupg/issue2452
With that info I can also reproduce the behavior by forcing an empty
environment:
```
error: gpg exec failed (2)
[pmatilai@sopuli rpm]$ cp ~/Downloads/xfce4-terminal-0.8.2-2.fc25.x86_64.rpm
/tmp/; env -i
That's strange. I'm not able to reproduce that, and it doesn't seem to be about
actual length either since my name is longer and I always had this in my
~/.rpmmacros:
`%_gpg_name Panu Matilainen `
What version of rpm, gpg and what distro are you using?
--
You are
I dont see what more there is to explain. Macros are expanded everywhere
including what appear to be comments in spec. If you need to escape it to avoid
expansion then double percent (%%) is the way to do it.
--
You are receiving this because you are subscribed to this thread.
Reply to this
Closed #121.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/121#event-918754747___
Rpm-maint mailing list
\CC: @pmatilai, @ffesti, @ignatenkobrain, @myungjoo , @hk57kim , @jyoungyun
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
We sometime use "#" symbol to append some contents in ./spec file. This issue
describes incorrect operation of "#" symbol in case that we try to ignore a
macro line (e.g. %define . . . ) in ./spec file. For example, the '#' (hash
character) symbol to invalidate a macro statement does not valid
29 matches
Mail list logo