On Tue, May 19, 2020, 15:40 Jiri Vanek wrote:
> Hello!
>
> An raw schedule of mass rebuilds was added to the Java11 feature list:
> https://fedoraproject.org/wiki/Changes/Java11#Expected_schedule
>
> You can expect second copr-based mass rebuild, in 1st June 2020. Please
> try to fix your package
Hello!
An raw schedule of mass rebuilds was added to the Java11 feature list:
https://fedoraproject.org/wiki/Changes/Java11#Expected_schedule
You can expect second copr-based mass rebuild, in 1st June 2020. Please try to
fix your packages
until then, as on the result of this mass rebuild, futur
On 5/4/20 12:59 PM, Iñaki Ucar wrote:
> On Mon, 4 May 2020 at 11:22, Jiri Vanek wrote:
>>
>>> Thanks, but as I said above, the RStudio rpms don't pull the JVM,
>>> because it's not required at runtime. So I suppose that, beyond fixing
>>> the java-devel version in BuildRequires, I don't need to do
On Mon, 4 May 2020 at 11:22, Jiri Vanek wrote:
>
> > Thanks, but as I said above, the RStudio rpms don't pull the JVM,
> > because it's not required at runtime. So I suppose that, beyond fixing
> > the java-devel version in BuildRequires, I don't need to do anything
> > more, right?
>
> Hopefully:
On 5/4/20 11:15 AM, Iñaki Ucar wrote:
> Hi, thanks for your assistance, comments inline:
>
> On Mon, 4 May 2020 at 10:48, Jiri Vanek wrote:
>>
>> Generally, no program can say, that do not support jdk11, because any
>> javac/java application can be
>> *hacked* to work with java11 - see
>> https:
Hi, thanks for your assistance, comments inline:
On Mon, 4 May 2020 at 10:48, Jiri Vanek wrote:
>
> Generally, no program can say, that do not support jdk11, because any
> javac/java application can be
> *hacked* to work with java11 - see
> https://jvanek.fedorapeople.org/devconf/2017/portingjav
On 5/3/20 10:56 PM, Iñaki Ucar wrote:
> Hi,
>
Hi Iñaki!
I have CCed devel@lists.fedoraproject.org as this issue may be shared. I have
not yet written it to
https://fedoraproject.org/wiki/Changes/Java11#common_issues_packagers_can_face_and_gathered_solutions
as
I hope it will be rare.
Generally
Sure!
TYVM!
___
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/project/code-of-conduct/
List Guidelines: https://fedorap
ent: Friday, May 1, 2020 2:19:17 PM
> Subject: Re: F33 system wide change, java-11-openjdk as system jdk
>
> Hi Alex, both your packages
> "BuildRequires:java-1.8.0-openjdk-devel"
> So I could not pull it. According to the packaging guidelines you should
> require
Hi Miro!
The build is in f32 chroot, because jdk8 in rawhide segfaults due to new glibc.
The glibc update had overlap with the initiation of this effort, so I stuck on
f32 for now. It may happen that once we fix jdk8, I will fix also the copr.
Also you could notice, that both rawhide and f32 are
Hi Miro!
The build is in f32 chroot, because jdk8 in rawhide segfaults due to new glibc.
The glibc update had overlap with the initiation of this effort, so I stuck on
f32 for now. It may happen that once we fix jdk8, I will fix also the copr.
Also you could notice, that both rawhide and f32 are
Hi Alex, both your packages
"BuildRequires:java-1.8.0-openjdk-devel"
So I could not pull it. According to the packaging guidelines you should
require only "java-devel" (exactly for this case:)). Thus I could not found
your packages by using build-requires queries. Even If I found, It wou
\o Hey Jiri,
I don't see two of our packages in the copr:
https://src.fedoraproject.org/rpms/pki-core/
https://src.fedoraproject.org/rpms/dogtag-pki/
Is there a way to know why they were excluded?
Thanks!
- Alex
- Original Message -
> From: "Jiri Vanek"
> To: "Development discussion
On 30. 04. 20 18:29, Jiri Vanek wrote:
* Ensure your package builds and runs fine with JDK11 (see the
https://copr.fedorainfracloud.org/coprs/jvanek/java11/builds/)
The builds are from Fedora 33 sources, but in Fedora 32 buildroot. The Java11
change is for Fedora 33. Is this an error, or is
14 matches
Mail list logo
