Re: Specs using %define

[Björn Esser]

Am 24.12.2015 um 22:01 schrieb Jason L Tibbitts III:

To satisfy my curiosity, I grepped the convenient tarball of specfiles
(http://pkgs.fedoraproject.org/repo/rpm-specs-latest.tar.xz) for lines
matching "(?

All %define changed to %global in recent commit.


NLopt (besser82)


This spec-file uses %global, but in one special case:  I use %define for 
nested macro-expansion --->  %define lc_name %(echo ${%{name},,})
lc_name would be empty during parsing the spec-file, when declaring with 
%global…

--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: Specs using %define

[Alec Leamas]

On 24/12/15 22:01, Jason L Tibbitts III wrote:
> To satisfy my curiosity, I grepped the convenient tarball of specfiles
> (http://pkgs.fedoraproject.org/repo/rpm-specs-latest.tar.xz) for lines
> matching "(? there were more than 1900 hits.

> iguanaIR (leamas)

Fixed in git, no builds made.

Cheers!

--alec
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

[EPEL-devel] Re: epel-rpm-macros for EL6 (and EL5)

[Jason L Tibbitts III]

> "AT" == Antonio Trande  writes:

AT> %{__global_ldflags} is another macro that it's not available in
AT> EPEL6.

It appears that gets exported as a shell variable in the scope of %build
by %__build_pre, as well as being mentioned in the %cmake, %cmake_kde4,
%qmake_qt4 and %configure macros.  Though some of might not even be
present at all in EL6, and %configure is a much simpler macro there.

I would have to override any existing definitions of all of those, but
as there's essentially no chance of Red Hat changing those five macros
at this point in the EL6 life cycle I don't see that this would be much
of an issue.  Can you let me know where the lack of %__global_ldflags is
causing problems?  (Maybe an example spec or two?)  Would it help if I
just added it to %configure or would it need to go elsewhere as well?

I'll add it to the list in any case.

 - J<
___
epel-devel mailing list
epel-devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/epel-devel@lists.fedoraproject.org

Re: Specs using %define

[Ville Skyttä]

On Fri, Dec 25, 2015 at 2:10 AM, Jason L Tibbitts III  wrote:
>> "JJ" == Jerry James  writes:
>
> JJ> This uses a %define inside the %check script as a convenient macro,
> JJ> used only inside the %check script; i.e., it really is a local
> JJ> definition.
>
> But %define isn't a "local definition" in the sense that you're thinking
> of.  It's certainly visible outside of %check, for example.  Which
> actual property of %define are you relying upon here?  I don't think
> you're doing anything specific with nested macro expansions.

Also, if the definitions are really local to some specfile shell code
sections, there's probably no need to involve rpm in them at all --
regular shell variables or functions can be used instead.
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

rawhide report: 20151225 changes

[Fedora Rawhide Report]

Compose started at Fri Dec 25 05:15:02 UTC 2015
Broken deps for i386
--
[IQmol]
IQmol-2.3.0-9.fc24.i686 requires libboost_serialization.so.1.58.0
IQmol-2.3.0-9.fc24.i686 requires libboost_iostreams.so.1.58.0
IQmol-2.3.0-9.fc24.i686 requires libOpenMeshCore.so.3.2
[alliance]
alliance-5.0-40.20090901snap.fc22.i686 requires libXm.so.2
[eclipse-jbosstools]
eclipse-jbosstools-as-4.2.2-1.fc22.noarch requires 
osgi(org.eclipse.tm.terminal)
[fawkes]
fawkes-core-0.5.0-26.fc24.i686 requires libmicrohttpd.so.10
fawkes-plugin-player-0.5.0-26.fc24.i686 requires libgeos-3.4.2.so
fawkes-plugin-xmlrpc-0.5.0-26.fc24.i686 requires libmicrohttpd.so.10
[gnash]
1:gnash-0.8.10-19.fc24.i686 requires libboost_thread.so.1.58.0
1:gnash-0.8.10-19.fc24.i686 requires libboost_system.so.1.58.0
1:gnash-0.8.10-19.fc24.i686 requires libboost_serialization.so.1.58.0
1:gnash-0.8.10-19.fc24.i686 requires libboost_program_options.so.1.58.0
1:gnash-0.8.10-19.fc24.i686 requires libboost_iostreams.so.1.58.0
1:gnash-0.8.10-19.fc24.i686 requires libboost_date_time.so.1.58.0
1:gnash-cygnal-0.8.10-19.fc24.i686 requires libboost_thread.so.1.58.0
1:gnash-cygnal-0.8.10-19.fc24.i686 requires libboost_system.so.1.58.0
1:gnash-cygnal-0.8.10-19.fc24.i686 requires 
libboost_serialization.so.1.58.0
1:gnash-cygnal-0.8.10-19.fc24.i686 requires 
libboost_program_options.so.1.58.0
1:gnash-cygnal-0.8.10-19.fc24.i686 requires libboost_iostreams.so.1.58.0
1:gnash-cygnal-0.8.10-19.fc24.i686 requires libboost_date_time.so.1.58.0
1:gnash-extension-dejagnu-0.8.10-19.fc24.i686 requires 
libboost_thread.so.1.58.0
1:gnash-extension-dejagnu-0.8.10-19.fc24.i686 requires 
libboost_system.so.1.58.0
1:gnash-extension-dejagnu-0.8.10-19.fc24.i686 requires 
libboost_program_options.so.1.58.0
1:gnash-extension-dejagnu-0.8.10-19.fc24.i686 requires 
libboost_iostreams.so.1.58.0
1:gnash-extension-fileio-0.8.10-19.fc24.i686 requires 
libboost_thread.so.1.58.0
1:gnash-extension-fileio-0.8.10-19.fc24.i686 requires 
libboost_system.so.1.58.0
1:gnash-extension-fileio-0.8.10-19.fc24.i686 requires 
libboost_program_options.so.1.58.0
1:gnash-extension-fileio-0.8.10-19.fc24.i686 requires 
libboost_iostreams.so.1.58.0
1:gnash-extension-lirc-0.8.10-19.fc24.i686 requires 
libboost_thread.so.1.58.0
1:gnash-extension-lirc-0.8.10-19.fc24.i686 requires 
libboost_system.so.1.58.0
1:gnash-extension-lirc-0.8.10-19.fc24.i686 requires 
libboost_program_options.so.1.58.0
1:gnash-extension-lirc-0.8.10-19.fc24.i686 requires 
libboost_iostreams.so.1.58.0
1:gnash-extension-mysql-0.8.10-19.fc24.i686 requires 
libboost_thread.so.1.58.0
1:gnash-extension-mysql-0.8.10-19.fc24.i686 requires 
libboost_system.so.1.58.0
1:gnash-extension-mysql-0.8.10-19.fc24.i686 requires 
libboost_program_options.so.1.58.0
1:gnash-extension-mysql-0.8.10-19.fc24.i686 requires 
libboost_iostreams.so.1.58.0
1:gnash-klash-0.8.10-19.fc24.i686 requires libboost_system.so.1.58.0
1:gnash-klash-0.8.10-19.fc24.i686 requires 
libboost_program_options.so.1.58.0
1:gnash-plugin-0.8.10-19.fc24.i686 requires libboost_iostreams.so.1.58.0
1:python-gnash-0.8.10-19.fc24.i686 requires libboost_thread.so.1.58.0
1:python-gnash-0.8.10-19.fc24.i686 requires libboost_system.so.1.58.0
1:python-gnash-0.8.10-19.fc24.i686 requires 
libboost_program_options.so.1.58.0
1:python-gnash-0.8.10-19.fc24.i686 requires libboost_iostreams.so.1.58.0
[golang-github-kraman-libcontainer]
golang-github-kraman-libcontainer-devel-0-0.4.gitd700e5b.fc24.noarch 
requires golang(github.com/docker/docker/pkg/netlink)
[golang-github-kubernetes-heapster]
golang-github-kubernetes-heapster-devel-0.16.1-1.fc24.noarch requires 
golang(github.com/google/cadvisor/info/v1)
golang-github-kubernetes-heapster-devel-0.16.1-1.fc24.noarch requires 
golang(github.com/google/cadvisor/client)
golang-github-kubernetes-heapster-devel-0.16.1-1.fc24.noarch requires 
golang(github.com/coreos/fleet/schema)
golang-github-kubernetes-heapster-devel-0.16.1-1.fc24.noarch requires 
golang(github.com/coreos/fleet/registry)
golang-github-kubernetes-heapster-devel-0.16.1-1.fc24.noarch requires 
golang(github.com/coreos/fleet/pkg)
golang-github-kubernetes-heapster-devel-0.16.1-1.fc24.noarch requires 
golang(github.com/coreos/fleet/machine)
golang-github-kubernetes-heapster-devel-0.16.1-1.fc24.noarch requires 
golang(github.com/coreos/fleet/etcd)
golang-github-kubernetes-heapster-devel-0.16.1-1.fc24.noarch requires 
golang(github.com/coreos/fleet/client)
[golang-github-prometheus-prometheus]

Fedora Rawhide 20151225 compose check report

[Fedora compose checker]

Missing expected images:

Cloud_atomic disk raw x86_64
Workstation live i386

Images in this compose but not Rawhide 20151224:

Mate live i386

Images in Rawhide 20151224 but not this:

Workstation live i386

Failed openQA tests: 2 of 60

ID: 1713Test: i386 kde_live default_install
URL: https://openqa.fedoraproject.org/tests/1713
ID: 1709Test: x86_64 kde_live default_install
URL: https://openqa.fedoraproject.org/tests/1709

Passed openQA tests: 58 of 60
-- 
Mail generated by check-compose:
https://git.fedorahosted.org/cgit/fedora-qa.git/tree/check-compose
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: Specs using %define

[Jason L Tibbitts III]

> "BE" == Björn Esser  writes:

BE> This spec-file uses %global, but in one special case: I use %define
BE> for nested macro-expansion --->

BE>   %define lc_name %(echo ${%{name},,})

BE> lc_name would be empty during parsing the spec-file, when declaring
BE> with %global…

Thanks for letting me know that there is a valid case in use there.  I
don't think there's an easy way to detect valid usage, but I can grep
out that macro when I run things again.

 - J<


-- devel mailing list devel@lists.fedoraproject.org
BE> http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org


-- 
 Jason L Tibbitts III - ti...@math.uh.edu - 713/743-3486 - 660PGH
 System Manager:  University of Houston Department of Mathematics 
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: Specs using %define

[Christian Dersch]

On 12/24/2015 10:01 PM, Jason L Tibbitts III wrote:
> libapogee (sergiopr, lupinix)
> qwtplot3d (chitlesh, lupinix)
>
 Done :) Also added %license.
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

[EPEL-devel] Re: epel-rpm-macros for EL6 (and EL5)

[Jason L Tibbitts III]

> "JLT" == Jason L Tibbitts  writes:

JLT> Does that actually work on EL6?

Looking at the spec, it seems obvious that it works on EL6.  The package
isn't branched for EL5 but if anyone knows if -Wl,-z,relro will work
there than I'll add it there as well (once I get around to doing an EL5
package).

Remember, anything that requires an ifdef on any EPEL release is a
candidate for what I'm doing.  Obviously some things just aren't going
to be possible, at least with RPM macros alone, but I'm willing to try.

 - J<
___
epel-devel mailing list
epel-devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/epel-devel@lists.fedoraproject.org