Cool. TYVM!
On Mon, 24 Jun 2024 at 19:27, Miro Hrončok wrote:
> On 24. 06. 24 19:16, Jiri Vanek wrote:
> > hi!
> >
> > Yes, there is upcoming release in 17july, and in this release will be
> all
> > built on f39.
> >
> > If there would be any inter
hi!
Yes, there is upcoming release in 17july, and in this release will be all
built on f39.
If there would be any intermittent release it would be already on f39
anyway.
I do not have strong preference on exclude/rebuild. I was going by moreover
middle path - to keep building on oldest supporte
wrote:
>
> On 6/29/23 13:07, Jiri Vanek wrote:
> > nn. You were right. There are going to be two separated packages.
> > Portable, built once in oldest live, and "normal" which is going to
> > repack them for all and shipp them.
> > My apologise f
Everywhere&type=revision&diff=681794&oldid=681791
narrowed.
On Thu, 29 Jun 2023 at 21:16, Tom Stellard wrote:
>
> On 6/29/23 11:06, Jiri Vanek wrote:
> > Nope, xy stands for 1.8.0, 11, 17 and latest. It is enumerated several
> > time in the proposal. Still the
&g
whide may remian self building. Aka using protbales
from rawhide to buidl rawhide's rpms.
Thax!
On Thu, 29 Jun 2023 at 19:43, Kevin Fenzi wrote:
>
> On Thu, Jun 29, 2023 at 10:14:31AM -0700, Tom Stellard wrote:
> > On 6/29/23 09:52, Jiri Vanek wrote:
> > > Hi Tom!
ch
> >>> Fedora and EPEL version. Goal here is to build each JDK
> >>> (8,11,17,21,latest (20)) only once, in oldest live Fedora repack in
> >>> all live Fedoras. If jdk is buitl in epel, it will be built in oldest
> >>> possible epel and repacked in ne
n epel, it will be built in oldest
> > possible epel and repacked in newer live epels.
> >
> >
> > == Owner ==
> > * Name: [[User:jvanek| Jiri Vanek]]
> >
> > * Email: jva...@redhat.com
> >
> >
> > == Detailed Description ==
> >
> &g
JDK will behave similarly. We ave (small) advantage that we have also
in-jdk-bundled tzdata. However fallback in case of removed system
tzdata is not automatic, and requires human touch. Long ago we have a
patch in jdk which looked to system tzdata - if they were present,
they were used. If not,
ks in fedora are already static, and we repack portable
> tarball into rpms. Currently, the portbale tarball is built for each
> Fedora and Epel version. Goal here is to build each jdk
> (8,11,17,21,latest (20)) only once, in oldest live Fedora xor Epel and
> repack in all live fedoras.
>
t.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
--
Jiri Vanek Mgr.
Principal QA Software Engineer
Red Hat Inc.
+420 775 39 01 09
___
devel mailing list --
On 6/2/23 01:09, Kevin Kofler via devel wrote:
Demi Marie Obenour wrote:
I haven’t written Java in years, but my understanding is
that AOT compilation has three major advantages:
1. It reduces the size of total deliverables because the
final executable only includes the libraries it needs
On 5/31/23 19:58, Chris Adams wrote:
Once upon a time, Jiri Vanek said:
I have fixed typo in the proposal " Should be built in oldest live EPEL" instead of
" Should be built in latest live EPEL", which was wrong.
At the moment though, the oldest live EPEL is 7, not 8.
On 5/31/23 20:02, Daniel P. Berrangé wrote:
On Wed, May 31, 2023 at 07:38:38PM +0200, Jiri Vanek wrote:
Can you clarify this a bit? It sounds like some versions of the JDK in
Fedora will actually be built in EPEL. I feel that all Fedora packages
should actually built for Fedora, not RHEL
+0200, Jiri Vanek wrote:
This was heavily discussed when we moved to portable build in rpms -
https://fedoraproject.org/wiki/Changes/JdkInTreeLibsAndStdclibStatic
Long story short yes, if yo wish to distribute jdk *binary* it have
to pass java compliance suite.
It sounds like the problem is the
All this change is about the burden of maintaining so many OpenJDK branches as packages in FEdora. Maybe Fedora should stop distributing ancient Java versions as one of our missions is to be cutting edge, maybe we are still encouraging too
many projects to stay running on Java 8.
I am saying
On 6/1/23 13:33, Kevin Kofler via devel wrote:
Jiri Vanek wrote:
At elast providing ofjava/openjdk is definitley out of scope.
I do not think a Provides would be a trademark violation. It is a part of
the standard procedure for renaming a package. But you would have to ask Red
Hat Legal for
idelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
--
Jiri Vanek Mgr.
Principal QA Software Engineer
Red Hat Inc.
+4
t.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
--
Jiri Vanek Mgr.
Principal QA Software Engineer
Red Hat Inc.
+420 775 39 01 09
___
devel mailing list -- devel@l
> That sounds like an effectively nonfree software. Users cannot build and
> distribute the binaries because the required tools are nonfree.
Not exactly. You can build it and use it freely. Unless you distribute it to
others and call it java...
J.
--
Jiri Vanek Mgr.
Principal QA So
/pagure.io/fesco/issue/2907
J.
--
Jiri Vanek Mgr.
Principal QA Software Engineer
Red Hat Inc.
+420 775 39 01 09
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fed
rywhere, but it gave sense. If the hard demand will be to build also java-latest-opnejdk in oldest fedora, and repack in all fedoras, and built it in oldest
epel, and repack in all epels, then it gave somehow sesnse too. Although I would conisdered it a bit wasted cycle, it is acceptable.
Thanx!
.io/fedora-infrastructure/new_issue
--
Jiri Vanek Mgr.
Principal QA Software Engineer
Red Hat Inc.
+420 775 39 01 09
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code
On 5/31/23 16:25, Robert Marcano via devel wrote:
On 5/31/23 9:44 AM, Gerd Hoffmann wrote:
On Wed, May 31, 2023 at 03:32:09PM +0200, Vitaly Zaitsev via devel wrote:
On 31/05/2023 14:53, Jiri Vanek wrote:
It is built from sources of course!
What make you think it is not?
For double ensurenes
/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
--
Jiri Vanek Mgr.
Principa
lot for writing this down. It is still a bti hard hard to grab that.
J.
--
Jiri Vanek Mgr.
Principal QA Software Engineer
Red Hat Inc.
+420 775 39 01 09
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel
of course).
--
Jiri Vanek Mgr.
Principal QA Software Engineer
Red Hat Inc.
+420 775 39 01 09
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https
Hello! I woudl like to -
https://fedoraproject.org/wiki/Changes/NodejsRepackaging#Feedback -
add, that also java is using alternatives for major versions of jdk
switching. Weahve master java - to switch runtime, and javac to switch
devel subpackages.
Man pages are also slaves to the java/javac ma
o spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
--
Jiri Vanek Mgr.
Principal QA Software Engineer
Red Hat Inc.
+420 775 39 01 09
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists
roject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
--
Jiri Vanek Mgr.
Principal QA Software Engineer
Red Hat Inc.
+420 775 39 01 09
___
devel mailing list -- devel@lists.fedorap
anybody have any tips for similar machines?
As for tech spec - strongest rpi *2 :);
J.
--
Jiri Vanek Mgr.
Principal QA Software Engineer
Red Hat Inc.
+420 775 39 01 09
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to
My investigations shown, probably nothing will be affected by removal of jdk on
i686 and the fix in subversion and automake/autotools is fluid and, again, will
damage nothing. However I'm not sure. I can not possibly see into all details of
all affected packages.
Where casual pkg which is bein
On 7/15/22 11:07, Jonathan Wakely wrote:
On Wed, 13 Jul 2022 at 11:04, Jiri Vanek wrote:
Hi All!
On 7/6/22 01:24, Miro Hrončok wrote:
On 06. 07. 22 1:17, Miro Hrončok wrote:
On 06. 07. 22 0:14, Kevin Kofler via devel wrote:
Stephen Smoogen wrote:
Hyperbole aside, it isn't a
-infrastructure
--
Jiri Vanek Mgr.
Principal QA Software Engineer
Red Hat Inc.
+420 775 39 01 09
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of
then 50
which depends *only* on subversion.
Sorry for delayed reply, Miro, thanx for ping.
J.
--
Jiri Vanek Mgr.
Principal QA Software Engineer
Red Hat Inc.
+420 775 39 01 09
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe
dependece f more then 50
other packages (that was the point,where the non linear curve really start to
grow).
(I could not see any bug and wondering why not?)
Yes and it has been fixed:
https://bugzilla.redhat.com/show_bug.cgi?id=2103909
Thank you for posting this!
hth!
J.
--
Jiri
On 5/26/22 14:17, Stephen Snow wrote:
Also, it may be good to take a look at what AdoptOpenJDK is doing with
the Eclipse Foundation based Adoptium Project, specifically the Eclipse
Temurin subproject
https://projects.eclipse.org/proposals/eclipse-temurin-compliance which
is going to handle the
The rename will really not help.
On 5/25/22 18:01, Vitaly Zaitsev via devel wrote:
On 25/05/2022 15:03, Jiri Vanek wrote:
We can not ship uncerified JDK. Sooner or later a swarm of lawyers would appear.
Let's rename it to icedtea then.
--
Jiri Vanek Mgr.
Principal QA Software Enginee
BTW, I noticed that despite java-17-openjdk being the default system
JDK on Fedora 36, it wasn't installed instead of java-11-openjdk when
I upgraded from Fedora 35. That sounds like the change proposal
wasn't
That sounds like super severe bug. I had tried it manytimes, in testing
environemt
29 Sep 10 14:32 jre-openjdk ->
/etc/alternatives/jre_openjdk
I think the OpenJDK's scriplets need to be adjusted to remove everything.
--
Jiri Vanek Mgr.
Principal QA Software Engineer
Red Hat Inc.
+420 775 39 01 09
___
devel m
On 5/25/22 15:28, Neal Gompa wrote:
On Wed, May 25, 2022 at 9:17 AM Jiri Vanek wrote:
On 5/24/22 22:02, Fabio Valentini wrote:
On Tue, May 24, 2022 at 5:03 PM Jiri Vanek wrote:
I replied it already in that thread, but happy to repeat:
It will help, but less then it seems so.
Now we can
On 5/25/22 15:19, Stephen Smoogen wrote:
On Wed, 25 May 2022 at 09:04, Jiri Vanek mailto:jva...@redhat.com>> wrote:
On 5/24/22 21:41, Vitaly Zaitsev via devel wrote:
> On 24/05/2022 21:00, Jiri Vanek wrote:
>> I repeat what was told several times.We really do
On 5/24/22 22:14, Kevin Fenzi wrote:
On Tue, May 24, 2022 at 04:57:54PM +0200, Jiri Vanek wrote:
We are testing also upstream. note that RH is maintainer of ojdk 11 and 8,
so we have to. But that is much easier, as the usptream is static within
intree libraries. And we have to run also for
On 5/24/22 22:02, Fabio Valentini wrote:
On Tue, May 24, 2022 at 5:03 PM Jiri Vanek wrote:
I replied it already in that thread, but happy to repeat:
It will help, but less then it seems so.
Now we can drop 8. Soem legacy applciations will be unhappy, as EOL of jdk8 is
in some 4 years, so
On 5/24/22 21:41, Vitaly Zaitsev via devel wrote:
On 24/05/2022 21:00, Jiri Vanek wrote:
I repeat what was told several times.We really do no t like this change,
especially in its full sound of one static build repacked to all ive fedoras,
but we have nto found a better way.
1. Stop doing
On 5/24/22 18:37, Vitaly Zaitsev via devel wrote:
On 24/05/2022 16:31, Jiri Vanek wrote:
The goal is to go as shim and cisco - to build in koji, certify, and repack.
shim and openh264 have a good reason for this - legal issues. OpenJDK doesn't.
Sorry, but I can't treat the lazin
On 5/21/22 13:38, Neal Gompa wrote:
On Sat, May 21, 2022 at 7:28 AM Jiri Vanek wrote:
On 5/20/22 14:57, Vitaly Zaitsev via devel wrote:
On 20/05/2022 14:28, Jiri Vanek wrote:
wait, what? What do you mean? And waht give you this impression?
https://fedoraproject.org/wiki
On 5/23/22 20:40, Kevin Fenzi wrote:
So, just replying here since this is a nice monster of a thread. ;(
First, just to clear up some previous coments, shim does build against
the oldest stable Fedora in koji and then is manually tagged into newer
ones. This is not at all a good process. It on
On 5/21/22 13:51, Vitaly Zaitsev via devel wrote:
On 21/05/2022 13:22, Jiri Vanek wrote:
shim?
Built on Koji from sources as shim-unsigned, then uploaded to Microsoft for
signing.
This is a special legal case, just like openh264 and Cisco.
Both of them built from sources on Fedora infra
On 5/20/22 14:57, Vitaly Zaitsev via devel wrote:
On 20/05/2022 14:28, Jiri Vanek wrote:
wait, what? What do you mean? And waht give you this impression?
https://fedoraproject.org/wiki/MoveFedoraJDKsToBecomePortableJDKs:
> Make the normal rpms to not built jdk, but to repack the porta
On 5/20/22 14:57, Vitaly Zaitsev via devel wrote:
On 20/05/2022 14:28, Jiri Vanek wrote:
wait, what? What do you mean? And waht give you this impression?
https://fedoraproject.org/wiki/MoveFedoraJDKsToBecomePortableJDKs:
> Make the normal rpms to not built jdk, but to repack the porta
;.
The Oxford English Dictionary gives the following answer:
lie (noun) - an intentionally false statement
used with reference to a situation involving deception or founded on a
mistaken impression
Exactly. So, you implied malicious intent where there was none.
Regards,
Dominik
--
Jiri Vanek
On 5/18/22 18:34, Vitaly Zaitsev via devel wrote:
On 18/05/2022 17:51, jiri vanek wrote:
You can not put uncertified JDK to fedora.
Why not?
And we can no longer properly support certified dynamic builds
Hire new maintainers who can.
Who shold hire them. You? Me? Fedoraproject
On 5/18/22 18:36, Neal Gompa wrote:
On Wed, May 18, 2022 at 12:33 PM jiri vanek wrote:
Hi Neal!
We are participating on Wakefield too. Why do you think JDK in feora should
miss it ?
It does nto metter if it is static or dynamic one, it will just run correctly
under wayaland. Or do I miss
to al llive fedoras?
--
Jiri Vanek Mgr.
Principal QA Software Engineer
Red Hat Inc.
+420 775 39 01 09
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
ling_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
--
Jiri Vanek Mgr.
Principal QA Software Engineer
Red H
On 5/18/22 18:22, Fabio Valentini wrote:
On Wed, May 18, 2022 at 6:04 PM Neal Gompa wrote:
On Wed, May 18, 2022 at 11:55 AM jiri vanek wrote:
You can imagine TCK as gigantic and pretty good testsuite, runing 24hours with
quite complicated setup. The pull and setup and run is completely
On 5/18/22 18:01, Neal Gompa wrote:
On Wed, May 18, 2022 at 11:55 AM jiri vanek wrote:
You can imagine TCK as gigantic and pretty good testsuite, runing 24hours with
quite complicated setup. The pull and setup and run is completely autoamted,
but it is a lot of HW you need (all
ent was exactly
because of "better" font rendering, which is clearly not an actual
argument.
Btw, I know this because I fixed a gazillion font related bugs in
OpenJDK in the past, most of which in the OpenJDK 6 and 7 era, I
rarely ever had to touch 8 or later.
Cheers,
Mario
--
Jiri Vanek M
On 5/18/22 13:02, Fabio Valentini wrote:
On Wed, May 18, 2022 at 12:28 PM jiri vanek wrote:
Once, long ago, we were the leader in the Linux Java ecosystem, but
ironically as Red Hat's influence in OpenJDK grew, investment in
Fedora dwindled.
That really is not true. But maybe we
h have
java-17-oepnjdk suddnely, whch idea was not ready. dnf install of 11 resovled
it withotu issues
--
Jiri Vanek Mgr.
Principal QA Software Engineer
Red Hat Inc.
+420 775 39 01 09
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscrib
death blow which will take years to fix.
J.
--
Jiri Vanek Mgr.
Principal QA Software Engineer
Red Hat Inc.
+420 775 39 01 09
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
F
On 5/18/22 17:31, Neal Gompa wrote:
On Wed, May 18, 2022 at 11:28 AM Peter Boy wrote:
Am 18.05.2022 um 16:36 schrieb Vitaly Zaitsev via devel
:
On 18/05/2022 11:27, Peter Boy wrote:
We didn’t lost Eclipse, we switched from RPM to another distribution method.
The same with Netbeans.
devel@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
--
Jiri Vanek Mgr.
Principal QA Software Engineer
Red Hat Inc.
+420 775 39 01 09
___
devel mailing list -- devel@lists.fedoraproject.o
evel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the li
Hi Neal!
We are participating on Wakefield too. Why do you think JDK in feora should
miss it ?
It does nto metter if it is static or dynamic one, it will just run correctly
under wayaland. Or do I miss something?
___
devel mailing list -- devel@lists.f
One one side it is good testsuite, on second something yo have to pass to
publish. So if users in fedora should have distribution-packed JDKs, someone
have to run (At least) them.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe s
You can imagine TCK as gigantic and pretty good testsuite, runing 24hours with
quite complicated setup. The pull and setup and run is completely autoamted,
but it is a lot of HW you need (all architecures x all oses x all jdks). In
adition, you need human power to keep with TCK evolution, somet
You can not put uncertified JDK to fedora. And we can no longer properly
support certified dynamic builds. We realy do no like this change, but we do
not see another way.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an em
> Jiri Vanek wrote:
>
> Unfortunately, your mail does not clarify all that much for me. I actually
> see several contradictions, e.g.:
>
>
> vs.
>
>
> so "putting [the binary] onto some other system", "eg on super custom
> opensuse", is
Yo are right. Then probably the only precedent I have is shmi.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/proje
> Why did you give up?
>
I'm unable to enumerate number of bugs we solved, or even dropped as unsolvable
due to dynamic nature of distribution-correct JDK.
>
> At one point AdoptOpenJDK distributed binaries that were not tested
> against the TCK (https://dzone.com/articles/an-overview-on-jdk-v
> On 5/17/22 08:33, Stephen Smoogen wrote:
> If I understand correctly, the main problem
> with the Java ecosystem
> is that it is based on redistribution of binaries, not source code.
> The focus is on building binaries that can be run on as many
> systems as possible, rather than on providing sou
> On Tue, May 17, 2022 at 8:33 AM Stephen Smoogen wrote:
>
> My expectation is based on how both Python and .NET have done this:
>
> The Python team made "Fedora Loves Python": https://fedoralovespython.org/
> The .NET team maintains the Developer page for .NET and has a domain
> redirect to it:
> Once, long ago, we were the leader in the Linux Java ecosystem, but
> ironically as Red Hat's influence in OpenJDK grew, investment in
> Fedora dwindled.
That really is not true. But maybe we were doing to much to keep any java
somehow alive. This proposal will untie our hands, and we wil be a
to keep peace and compatibility and proper developer's support, we have to move
with mian stream now. The divergences we keep in rpms are right now blocking devloeprs to use system jdsk as proper JDKs and are enforcing them to download Amazon, Azul, Oracle, etc. blobs...
To keep Fedora competit
jj, right you are.
--
Jiri Vanek Mgr.
Principal QA Software Engineer
Red Hat Inc.
+420 775 39 01 09
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct
Small clarification. I had jsut lerned abotu
https://fedoraproject.org/wiki/Changes/EncourageI686LeafRemoval . This java
proposal have nothig to do with that and was asctually done without anybody
from JDK maintainers beeing aware.
Still ti remains valid.
--
Jiri Vanek Mgr.
Principal QA
~pre16468670g9f253544-1.fc36.x86_64
--
Jiri Vanek Mgr.
Principal QA Software Engineer
Red Hat Inc.
+420 775 39 01 09
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https
Each bugs virtually blocks: https://bugzilla.redhat.com/show_bug.cgi?id=2024265
Plain text:
https://github.com/judovana/FedoraSystemJdkBump/blob/main/scritps/massRebuild/results.txt
On 2/6/22 17:36, Jiri Vanek wrote:
Hello!
Mass rebuild is finished, ftbfs are filled.
Just 65. Some three may
branching.
TYVM!
On 2/5/22 10:04, Jiri Vanek wrote:
Hello!
We have managed to fix jdk11 and 17 yesterday evening.
It is now building for rawhide.
Oce it get fixed, I had merged the jdk11 no longer being system jdk, and jdk17
becoming system jdk for rawhid.
They are now building for f36
then tomorrow morning I should have mass
rebuild started.
Still the schedule remains pretty tight.
tyvm!
J.
On 2/3/22 16:53, Jiri Vanek wrote:
On 2/3/22 16:47, Miro Hrončok wrote:
On 03. 02. 22 16:06, Mikolaj Izdebski wrote:
On Thu, Feb 3, 2022 at 2:32 PM Jiri Vanek wrote:
Hello Fesco
As
On 2/3/22 17:43, Stephen Gallagher wrote:
On Thu, Feb 3, 2022 at 11:08 AM Miro Hrončok wrote:
On 03. 02. 22 16:53, Jiri Vanek wrote:
Tag in the older gcc into your side tag, do the rebuilds, untag it?
I'm in favour of doing this as most strightforward solution.
I'm failing to
On 2/3/22 16:47, Miro Hrončok wrote:
On 03. 02. 22 16:06, Mikolaj Izdebski wrote:
On Thu, Feb 3, 2022 at 2:32 PM Jiri Vanek wrote:
Hello Fesco
As the branching of f36 get close, java had to fall to troubles.
After the last GCC mass rebuild, jdk11 is no longer buildable on i686.
We had a
# change spec, bump sources, apply patches
fedpkg srpm
mock -r jvanek-java17-fedora-rawhide-x86_64 *.src.rpm
Or any other packaging workflow you use, and you can use against the copr repo.
Thank you very much for your help, there are 73 failures, and 267 java
packagers, but only 2 active members
e against the copr repo.
Thank you very much for your help, there are 80 failures, and 270 java
packagers, but only 2 active members of java sig. Without your help, the JDK
bump will be very hard.
Thank You!
J.
--
Jiri Vanek Mgr.
Principal QA Software Engineer
Red Hat Inc.
+420 775 39 01 09
_
https://github.com/judovana/FedoraSystemJdkBump/blob/main/scritps/spammer/exemplarResults/verboseResults.txt
Here you go.
J.
On 12/1/21 01:39, Orion Poplawski wrote:
On 11/30/21 01:53, Jiri Vanek wrote:
On 11/29/21 15:01, Mat Booth wrote:
On Mon, 29 Nov 2021 at 13:16, Jiri Vanek wrote
.org/rpms/vtk
On 12/1/21 01:39, Orion Poplawski wrote:
On 11/30/21 01:53, Jiri Vanek wrote:
On 11/29/21 15:01, Mat Booth wrote:
On Mon, 29 Nov 2021 at 13:16, Jiri Vanek wrote:
I would kindly ask you to search yourself in this list:
https://github.com/judovana/FedoraSystemJdkBump/blob/main/scr
On 11/29/21 15:01, Mat Booth wrote:
On Mon, 29 Nov 2021 at 13:16, Jiri Vanek wrote:
I would kindly ask you to search yourself in this list:
https://github.com/judovana/FedoraSystemJdkBump/blob/main/scritps/fillCopr/exemplarResults/maintainers.jbump
This list contains dead/retired packages
awesome ty!
On 11/30/21 04:50, Jerry James wrote:
On Mon, Nov 29, 2021 at 6:16 AM Jiri Vanek wrote:
Thank you very much for your help, there are 107 failures, and 270 java
packagers, but only 2 active members of java sig. Without your help, the JDK
bump will be very hard.
All of the
+1
as in upvoting on stack exhcanges.
On 11/29/21 14:25, Artur Frenszek-Iwicki wrote:
rpmspec --parse $FILE
--
Jiri Vanek Mgr.
Principal QA Software Engineer
Red Hat Inc.
+420 775 39 01 09
___
devel mailing list -- devel@lists.fedoraproject.org
To
check what
is the result of:
%if 1
echo 1;
%else
echo 0;
%endif
Best regards,
[1]
https://rpm-packaging-guide.github.io/#rpm-conditionals
--
Jiri Vanek Mgr.
Principal QA Software Engineer
Red Hat Inc.
+420 775 39 01 09
___
devel mailing list
Hello fellow java package maintainers!
We are planning to bump the JDK from java-11-openjdk to java-17-openjdk for
f36. Please see https://fedoraproject.org/wiki/Changes/Java17
Short Story:
* if you have some java package, be aware that we are bumping JDK in rawhide
* Ensure your package buil
onduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
--
Jiri Vanek Mgr.
Principal QA Software Engine
Hello!
For wide hearing/reading, before final announcement,
https://fedoraproject.org/wiki/Changes/Java17 have anybody any opinion or
anything to say for/against?
Happy Hacking,
J.
--
Jiri Vanek Mgr.
Principal QA Software Engineer
Red Hat Inc.
+420 775 39 01 09
re than one version... and had no major issues. I wonder
how far back its possible to start from and walk through the version updates.
On Mon, Oct 11, 2021 at 3:55 AM Jiri Vanek mailto:jva...@redhat.com>> wrote:
Hello good people!
I would like to thanx to everybody fo
On 10/11/21 12:28, Petr Pisar wrote:
V Mon, Oct 11, 2021 at 09:55:05AM +0200, Jiri Vanek napsal(a):
f30-> f34 died again on python stack.. (yah, dnf and freinds should stop
using that or keep embedded interpreter)
DNF 5 is going be written in C++ without any Python.
with all its p
downlaod. in f31,
gpgcheck could be enabled again.
--
Jiri Vanek Mgr.
Principal QA Software Engineer
Red Hat Inc.
+420 775 39 01 09
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraprojec
: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
--
Jiri Vanek Mgr.
Principal QA Software Engineer
Red Hat Inc.
+420
Btw, not sure who did what, but thanx a lot. Without any touches, the epel8
package now builds fine.
So thank ou fedora relengs!
J.
On 6/22/21 6:27 PM, Jiri Vanek wrote:
Hello!
I have an ordinery package, which builds as is for epel7,and all fedoras, but
not for epel8:
Package openjdk
Tue, Jun 22, 2021 at 1:25 PM Jiri Vanek wrote:
On 6/22/21 7:08 PM, Stephen John Smoogen wrote:
Welcome to RHEL-8 modularity and the joy it brings anyone trying to
port software to 8. The problem is not with EPEL but with the way
hmm. Thanx a lot of for a bt of light in darknes.. or mayb emore
1 - 100 of 182 matches
Mail list logo