https://bugzilla.redhat.com/show_bug.cgi?id=1528565
Kunjan Rathod <krathod(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Depends On| |1585895
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1585627
Severin Gehwolf <sgehwolf(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|strange chnage in macro |Strange change in macro
|expansions in f29 |expansions in f29
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1585627
--- Comment #7 from Mikolaj Izdebski <mizdebsk(a)redhat.com> ---
(In reply to Severin Gehwolf from comment #6)
> Macros which use java functions may stay in a separate macro file which then
> may require java-1.8.0-openjdk. Thoughts?
We can do that. Please open an issue at M$ GitHub at
https://github.com/fedora-java/javapackages
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1585627
Severin Gehwolf <sgehwolf(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sgehwolf(a)redhat.com
--- Comment #6 from Severin Gehwolf <sgehwolf(a)redhat.com> ---
(In reply to jiri vanek from comment #5)
> hm. NVM. The buildrequires of javapackages-filesystem will solve it anyway.
This should be BuildRequires: javapackages-tools, right?
However, this will then drag in java-1.8.0-openjdk again for a JDK 10 build.
Bug 1500288 all over again. So what I'd think would be a better approach is to
move the directory macros from /usr/lib/rpm/macros.d/macros.jpackage to
javapackages-filesystem. E.g.
%_jvmdir %{_prefix}/lib/jvm
Macros which use java functions may stay in a separate macro file which then
may require java-1.8.0-openjdk. Thoughts?
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1585627
jiri vanek <jvanek(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |CLOSED
Component|javapackages-tools |java-openjdk
Resolution|--- |NOTABUG
Assignee|mizdebsk(a)redhat.com |jvanek(a)redhat.com
Last Closed| |2018-06-04 07:28:54
--- Comment #5 from jiri vanek <jvanek(a)redhat.com> ---
hm. NVM. The buildrequires of javapackages-filesystem will solve it anyway.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1585627
jiri vanek <jvanek(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ctubbsii(a)fedoraproject.org,
| |java-sig-commits(a)lists.fedo
| |raproject.org,
| |mat.booth(a)redhat.com,
| |mizdebsk(a)redhat.com,
| |msimacek(a)redhat.com,
| |msrb(a)redhat.com,
| |sochotni(a)redhat.com
Component|java-openjdk |javapackages-tools
Assignee|jvanek(a)redhat.com |mizdebsk(a)redhat.com
--- Comment #4 from jiri vanek <jvanek(a)redhat.com> ---
Thanx.
Then the issue is when we mover *requires* from javapackages-tools to
javapackages-filesystem or default buildroot have chnaged. As there was recent
clean up of java buildroot, second is more likely.
Again, sorry for noise
Mikolai, may you confirm?
--
You are receiving this mail because:
You are on the CC list for the bug.