https://bugzilla.redhat.com/show_bug.cgi?id=1795428
Jitka Plesnikova changed:
What|Removed |Added
Status|ASSIGNED|CLOSED
Fixed In Version|
https://bugzilla.redhat.com/show_bug.cgi?id=1795511
Bug ID: 1795511
Summary: perl-TheSchwartz-1.15 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: perl-TheSchwartz
Keywords: FutureFeature, Triaged
On Tue, 28 Jan 2020 02:23:10 -
"Artur Iwicki" wrote:
> No, this was done on a Fedora install. But thanks for the input! I've
> looked into the sources and with patched paths and rebuilt bootstrap
> compiler, the koji scratch build went ok. Gonna make a commit to
> dist-git soon.
awesome,
Dear maintainers.
Based on the latest fail to build from source policy, the following packages
will be retired from Fedora 32 approximately one week before branching
(2020-02-03).
Policy:
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
The packages in
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If
https://bugzilla.redhat.com/show_bug.cgi?id=1795428
Jitka Plesnikova changed:
What|Removed |Added
Status|NEW |ASSIGNED
Greetings,
The antlr4 package needs a reboot so that it can ship the various
language runtime libraries, and so that it can be updated to the
latest version. I have been in contact with the maintainers of the
current antlr4 package and have received approval to proceed with
this.
I would like
https://fedorapeople.org/groups/389ds/ci/nightly/2020/01/28/report-389-ds-base-1.4.3.2-20200128git473d616.fc31.x86_64.html
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to
On Tue, 28 Jan 2020, Bill Chatfield via devel wrote:
Are any of you on the java-devel list so that I could move my newb questions
there? I can guarantee that it's a low-traffic list so there's no risk in
joining it. :-)
google-http-java-client looks easy to fix. It won't build because it
Are any of you on the java-devel list so that I could move my newb questions
there? I can guarantee that it's a low-traffic list so there's no risk in
joining it. :-)
google-http-java-client looks easy to fix. It won't build because it needs one
dependency, maven-checkstyle-plugin, which
Dear all,
You are kindly invited to the meeting:
Modularity Team (weekly) on 2020-01-28 from 15:00:00 to 16:00:00 UTC
At fedora-meetin...@irc.freenode.net
The meeting will be about:
Meeting of the Modularity Team.
More information available at: [Modularity Team
I guess an outdated package might be easier but I'm more concerned about the
ones that are broken. I suppose the ones that are broken are still broken
because they're hard to fix.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe
No, this was done on a Fedora install. But thanks for the input! I've looked
into the sources and with patched paths and rebuilt bootstrap compiler, the
koji scratch build went ok. Gonna make a commit to dist-git soon.
___
devel mailing list --
Dear maintainers.
Based on the latest fail to build from source policy, the following packages
will be retired from Fedora 32 approximately one week before branching
(2020-02-03).
Policy:
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
The packages in
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If
rust-x11-2.18.2-1.fc32 hash changed its license from CC0-1.0 to MIT.
See also: https://github.com/erlepereira/x11-rs/issues/82
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
That is a very helpful explanation. I do have a lot of repos configured but
most are necessary. Some are now added by gnome-software.
_copr_phracek-PyCharm.repo fedora-updates.repo
rpmfusion-nonfree-nvidia-driver.repo
dropbox.repo
On Mon, Jan 27, 2020 at 1:44 PM Mario Torre wrote:
>
> On Mon, Jan 27, 2020 at 7:11 PM Robbie Harwood wrote:
>
> > Java packaging being extremely difficult is not a Fedora-specific
> > problem. The modularity effects are, but the packaging has been
> > known-hard for a very long time in many
https://bugzilla.redhat.com/show_bug.cgi?id=1795428
Bug ID: 1795428
Summary: perl-YAML-LibYAML-0.81 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: perl-YAML-LibYAML
Keywords: FutureFeature, Triaged
https://bugzilla.redhat.com/show_bug.cgi?id=1795427
Bug ID: 1795427
Summary: perl-YAML-1.30 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: perl-YAML
Keywords: FutureFeature, Triaged
https://bugzilla.redhat.com/show_bug.cgi?id=1795427
--- Comment #1 from Upstream Release Monitoring
---
An HTTP error occurred downloading the package's new Source URLs: Getting
https://cpan.metacpan.org/modules/by-module/YAML/YAML-1.30.tar.gz to
./YAML-1.30.tar.gz
--
You are receiving this
* Artur Iwicki:
> If you're asking "what's the source code", then it's built using the same
> source as the RPM. After going through %setup (i.e. extracting everything and
> applying patches), do:
> $ cd fpcsrc/
> $ make all CPU_TARGET=aarch64 OS_TARGET=linux
>
On Mon, 2020-01-27 at 21:23 +0100, Fabio Valentini wrote:
> On Mon, Jan 27, 2020 at 4:46 PM Jeff Law wrote:
> > On Mon, 2020-01-27 at 16:34 +0100, Jakub Jelinek wrote:
> > > On Mon, Jan 27, 2020 at 10:25:50AM -0500, Mohan Boddu wrote:
> > > > Hi all,
> > > >
> > > > Per the Fedora 32 schedule[1]
I've finished the build for ppc64le (bootstrapped from a cross-compiled
compiler): https://koji.fedoraproject.org/koji/taskinfo?taskID=41106187
It should be noted, though, that to enable ppc64le for dependent packages, the
fpc-srpm-macros package must be edited (since packages depending on fpc
On Mon, 27 Jan 2020 22:12:41 +0100
Fabio Valentini wrote:
> On Mon, Jan 27, 2020 at 10:06 PM Dan Horák wrote:
> >
> > On Mon, 27 Jan 2020 15:59:37 -0500
> > Mohan Boddu wrote:
> >
> > > Dan and Artur,
> > >
> > > The mass rebuild hasn't started yet, I can wait until 08:00 UTC
> > > 28-Jan-2020
On Mon, Jan 27, 2020 at 10:06 PM Dan Horák wrote:
>
> On Mon, 27 Jan 2020 15:59:37 -0500
> Mohan Boddu wrote:
>
> > Dan and Artur,
> >
> > The mass rebuild hasn't started yet, I can wait until 08:00 UTC
> > 28-Jan-2020 before starting the mass rebuild.
> >
> > If the work is not done by then, we
On Mon, 27 Jan 2020 15:59:37 -0500
Mohan Boddu wrote:
> Dan and Artur,
>
> The mass rebuild hasn't started yet, I can wait until 08:00 UTC
> 28-Jan-2020 before starting the mass rebuild.
>
> If the work is not done by then, we have to run a selective rebuild
> later.
I don't think we can fix
Dan and Artur,
The mass rebuild hasn't started yet, I can wait until 08:00 UTC
28-Jan-2020 before starting the mass rebuild.
If the work is not done by then, we have to run a selective rebuild later.
CC'ing Ben.
Thanks.
On Mon, Jan 27, 2020 at 3:11 PM Artur Iwicki wrote:
>
> Here's a koji
On Mon, 27 Jan 2020 20:28:15 -
"Artur Iwicki" wrote:
> If you're asking "what's the source code", then it's built using the
> same source as the RPM. After going through %setup (i.e. extracting
> everything and applying patches), do: $ cd fpcsrc/ $ make all
> CPU_TARGET=aarch64
On Mon, Jan 27, 2020 at 06:43:36PM +0200, Markku Korkeala wrote:
> Hi,
>
> sorry if this a newbie question, I tried to search this
> but did not find good documentation on this problem.
>
> I'm in the process of upgrading the clojure package to
> next version, which has new dependencies. These
On 1/26/20 5:33 PM, Bill Chatfield via devel wrote:
When I type "sudo dnf install something" it takes about 10 minutes to pull
updates from every repository, every time I run dnf. The actual install or update
proceeds at a reasonable pace. I wouldn't call it fast. I could send you a video of
If you're asking "what's the source code", then it's built using the same
source as the RPM. After going through %setup (i.e. extracting everything and
applying patches), do:
$ cd fpcsrc/
$ make all CPU_TARGET=aarch64 OS_TARGET=linux BINUTILSPREFIX=aarch64-linux-gnu-
If you're asking "where the
On Mon, Jan 27, 2020 at 4:46 PM Jeff Law wrote:
>
> On Mon, 2020-01-27 at 16:34 +0100, Jakub Jelinek wrote:
> > On Mon, Jan 27, 2020 at 10:25:50AM -0500, Mohan Boddu wrote:
> > > Hi all,
> > >
> > > Per the Fedora 32 schedule[1] we will be starting a mass rebuild for
> > > Fedora 32 today. We are
On Mon, 27 Jan 2020 21:19:34 +0100
Dan Horák wrote:
> On Mon, 27 Jan 2020 20:11:07 -
> "Artur Iwicki" wrote:
>
> > Here's a koji scratch build:
> > https://koji.fedoraproject.org/koji/taskinfo?taskID=41102368
> >
> > The ppc64le bootstrap went fine, the aarch64 one fails at:
what is the
On Mon, 27 Jan 2020 20:11:07 -
"Artur Iwicki" wrote:
> Here's a koji scratch build:
> https://koji.fedoraproject.org/koji/taskinfo?taskID=41102368
>
> The ppc64le bootstrap went fine, the aarch64 one fails at:
/builddir/build/BUILD/fpcbuild-r1430/fpcsrc/compiler/ppca64 fpmake.pp -n
Here's a koji scratch build:
https://koji.fedoraproject.org/koji/taskinfo?taskID=41102368
The ppc64le bootstrap went fine, the aarch64 one fails at:
/builddir/build/BUILD/fpcbuild-r1430/fpcsrc/compiler/ppca64 fpmake.pp -n
On Mon, Jan 27, 2020 at 6:01 PM Mario Torre wrote:
>
> On Mon, Jan 27, 2020 at 5:28 PM Robbie Harwood wrote:
>
> > > You would not expect a GCC devroom to be concerned about the problems
> > > of all packages written in C and C++, so why would Java be any
> > > different?
> >
> > Honestly? I
Hi
On Mon, Jan 27, 2020 at 8:56 AM Zbigniew Jędrzejewski-Szmek wrote:
> It is "upstream" in the sense that it is under the same umbrella.
> There are no plans to move the code to the main repo, because it's in
> rust and currently combining meson which is used for systemd proper
> with rust and
https://bugzilla.redhat.com/show_bug.cgi?id=1795181
Fedora Update System changed:
What|Removed |Added
Status|ASSIGNED|MODIFIED
--- Comment #2 from
On Mon, 27 Jan 2020 18:42:28 -
"Artur Iwicki" wrote:
> Yes, sorry about that. I'm working on it right now. Should be done
> before midnight CET.
>
> FPC 3.2.0 was originally to come out before the end of 2019, but it
> still hasn't been released. Reading the forums and the bug tracker,
>
* Bill Chatfield via devel [26/01/2020 22:33] :
>
> I don't know if the problem is dnf or a library, but it is a serious problem.
There are several issues here:
- Different servers will transmit repository metadata at different speeds
and you need to factor these out when trying to find
> In my experience, in 1999 I was living in the same region with an NGO
> working for a backbone network.
> And the NGO helped me to put my Linux server in their network for free.
> In the age of non-democratized computer and internet, some
> organizations helped for the new technologies.
My
On Mon, Jan 27, 2020 at 7:11 PM Robbie Harwood wrote:
> Java packaging being extremely difficult is not a Fedora-specific
> problem. The modularity effects are, but the packaging has been
> known-hard for a very long time in many distros (and even outside a
> distro context, it's not fun to
Yes, sorry about that. I'm working on it right now. Should be done before
midnight CET.
FPC 3.2.0 was originally to come out before the end of 2019, but it still
hasn't been released. Reading the forums and the bug tracker, none of the
remaining issues affect Fedora, so I decided to go with
> First, I'd like to see Fedora become more of an "operating system factory".
20s is from 2020 to 2029. 10 years. So long.
So, let me write high level thoughts. And let me post a new topic.
For the topic 'more of an "operating system factory"', I want to see
Fedora project as a place to
tMario Torre writes:
> On Mon, Jan 27, 2020 at 5:28 PM Robbie Harwood wrote:
>
>>> You would not expect a GCC devroom to be concerned about the
>>> problems of all packages written in C and C++, so why would Java be
>>> any different?
>>
>> Honestly? I totally would expect that. Wouldn't that
https://bugzilla.redhat.com/show_bug.cgi?id=1795181
Emmanuel Seyman changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #1 from
Since we have side tags now it shouldn't be disruptive but still wanted to
give a warning.
Dependent packages seem to be:
blender
luxcorerender
OpenColorIO
Thanks,
Richard
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an
On Mon, Jan 27, 2020 at 5:28 PM Robbie Harwood wrote:
> > You would not expect a GCC devroom to be concerned about the problems
> > of all packages written in C and C++, so why would Java be any
> > different?
>
> Honestly? I totally would expect that. Wouldn't that be better for
> everyone?
>
Hi,
sorry if this a newbie question, I tried to search this
but did not find good documentation on this problem.
I'm in the process of upgrading the clojure package to
next version, which has new dependencies. These dependencies
require certain clojure version themselves, so it makes a
Andrew Haley writes:
> On 1/26/20 11:52 AM, Nicolas Mailhot wrote:
>> Le dimanche 26 janvier 2020 à 10:10 +, Andrew Haley a écrit :
>>> On 1/26/20 8:43 AM, Nicolas Mailhot via devel wrote:
>>>
Java has been in a terminal course in Fedora for a year at
least. You can see how much
On 1/17/20 11:53 AM, Miro Hrončok wrote:
On 30. 11. 19 2:27, Ivan Chavero wrote:
Yes i'm going to update it to the newest version this weekend
thanks for following up!
Hello Ivan. Could you please have a look?
@Ivan,
Any update on the status of Nextcloud?
On Mon, 2020-01-27 at 16:34 +0100, Jakub Jelinek wrote:
> On Mon, Jan 27, 2020 at 10:25:50AM -0500, Mohan Boddu wrote:
> > Hi all,
> >
> > Per the Fedora 32 schedule[1] we will be starting a mass rebuild for
> > Fedora 32 today. We are doing a mass rebuild for Fedora 32 for all the
> > changes:
>
On Mon, 27 Jan 2020 10:25:50 -0500
Mohan Boddu wrote:
> Hi all,
>
> Per the Fedora 32 schedule[1] we will be starting a mass rebuild for
> Fedora 32 today. We are doing a mass rebuild for Fedora 32 for all the
> changes:
>
> https://fedoraproject.org/wiki/Changes/GLIBC231
>
On Mon, Jan 27, 2020 at 10:25:50AM -0500, Mohan Boddu wrote:
> Hi all,
>
> Per the Fedora 32 schedule[1] we will be starting a mass rebuild for
> Fedora 32 today. We are doing a mass rebuild for Fedora 32 for all the
> changes:
>
> https://fedoraproject.org/wiki/Changes/GLIBC231
>
Le 2020-01-27 15:46, Mario Torre a écrit :
You keep ignoring that a large part of the packaged ecosystem comes
from different places and is maintained by different people,
That’s why coordination conferences like the FOSDEM exist.
and not everything is in a state of chaos as you imply
https://bugzilla.redhat.com/show_bug.cgi?id=1795119
Petr Pisar changed:
What|Removed |Added
Status|ASSIGNED|MODIFIED
Fixed In Version|
Hi all,
Per the Fedora 32 schedule[1] we will be starting a mass rebuild for
Fedora 32 today. We are doing a mass rebuild for Fedora 32 for all the
changes:
https://fedoraproject.org/wiki/Changes/GLIBC231
https://fedoraproject.org/wiki/Releases/32/ChangeSet#Binutils_2.33
On Mon, Jan 27, 2020 at 2:52 PM Bill Chatfield via devel
wrote:
>
>
>
> On Monday, January 27, 2020, 3:58:07 AM EST, Fabio Valentini
> wrote:
> > Depending on what you want to achieve, I think I can give you better "first
> > package to work on" suggestions :)
>
> Yes, please give me some
- Original Message -
> From: "Tom Seewald"
> To: devel@lists.fedoraproject.org
> Sent: Sunday, January 26, 2020 12:35:32 PM
> Subject: Re: Java Dev Group and Fedora Quality
>
> > On Sat, Jan 25, 2020 at 11:07 PM Bill Chatfield via devel
> *snip*
> > True. Nobody cares about Java packages
Hi,
FYI all php-zendframework-* packages are now retire from rawhide.
This project is dead
Read:
https://framework.zend.com/blog/2019-04-17-announcing-laminas.html
So, now, all php-laminas-* packages are built and available
including the compatibility layer which allow to use
it the same
https://bugzilla.redhat.com/show_bug.cgi?id=1794960
Petr Pisar changed:
What|Removed |Added
Status|ASSIGNED|MODIFIED
Fixed In Version|
https://bugzilla.redhat.com/show_bug.cgi?id=1794960
Petr Pisar changed:
What|Removed |Added
Status|NEW |ASSIGNED
On Mon, Jan 27, 2020 at 3:32 PM Nicolas Mailhot
wrote:
> When a community driven conference grows to the size and reach of FOSDEM
> yes you can infer quite a lot from its schedule (one could do the same,
> removing the community word, for things where community is not relevant;
> that’s how half
Le 2020-01-27 15:13, Mario Torre a écrit :
On Sun, Jan 26, 2020 at 12:53 PM Nicolas Mailhot via devel
wrote:
Le dimanche 26 janvier 2020 à 10:10 +, Andrew Haley a écrit :
> On 1/26/20 8:43 AM, Nicolas Mailhot via devel wrote:
>
> > Java has been in a terminal course in Fedora for a year
OLD: Fedora-Rawhide-20200126.n.0
NEW: Fedora-Rawhide-20200127.n.0
= SUMMARY =
Added images:6
Dropped images: 1
Added packages: 1
Dropped packages:0
Upgraded packages: 41
Downgraded packages: 0
Size of added packages: 5.20 MiB
Size of dropped packages:0 B
On Sun, Jan 26, 2020 at 12:53 PM Nicolas Mailhot via devel
wrote:
>
> Le dimanche 26 janvier 2020 à 10:10 +, Andrew Haley a écrit :
> > On 1/26/20 8:43 AM, Nicolas Mailhot via devel wrote:
> >
> > > Java has been in a terminal course in Fedora for a year at
> > > least. You can see how much
No missing expected images.
Compose FAILS proposed Rawhide gating check!
2 of 43 required tests failed, 4 results missing
openQA tests matching unsatisfied gating requirements shown with **GATING**
below
Failed openQA tests: 25/158 (x86_64), 1/2 (arm)
New failures (same test not failed in
https://bugzilla.redhat.com/show_bug.cgi?id=1795113
Gerd Pokorra changed:
What|Removed |Added
Status|NEW |CLOSED
Fixed In Version|
Le 2020-01-27 10:52, Andrew Haley a écrit :
You would not expect a GCC devroom to be concerned about the problems
of all packages written in C and C++, so why would Java be any
different?
I would expect a GCC devroom to be concerned about the problems of all
packages written in C and C++ once
On Sat, Jan 25, 2020 at 02:52:05PM -0700, Chris Murphy wrote:
> Question and (pre)proposal:
> Can Fedora converge on a single swap-on-ZRAM implementation, and if
> so, which one? Fedora Workstation WG wants to move to swap-on-ZRAM by
> default in Fedora 33, and the working group needs to pick
On Monday, January 27, 2020, 3:58:07 AM EST, Fabio Valentini
wrote: > Depending on what you want to achieve, I think
I can give you better "first package to work on" suggestions :)
Yes, please give me some suggestions. I thought I had found one with few
dependencies but looks like it's
On 27/01/2020 12:01, Adam Williamson wrote:
I don't know in detail how apt works, but IIRC (sorry if I'm wrong), in
a previous discussion of this it's been suggested that the difference
is apt doesn't refresh this data unless you explicitly ask it to, while
dnf does automatically refresh it on
On Mon, Jan 27, 2020 at 1:08 PM Miro Hrončok wrote:
>
> On 27. 01. 20 10:34, Mikolaj Izdebski wrote:
> > On Mon, Jan 27, 2020 at 6:04 AM Bill Chatfield via devel
> > wrote:
> >>
> >> I have chosen a delinquent Java package to work fix. But I need some help
> >> understanding what's going on.
On 27. 01. 20 10:34, Mikolaj Izdebski wrote:
On Mon, Jan 27, 2020 at 6:04 AM Bill Chatfield via devel
wrote:
I have chosen a delinquent Java package to work fix. But I need some help
understanding what's going on. Groovy is failing to build because it depends on
gradle-local which doesn't
On Sun, 2020-01-26 at 22:33 +, Bill Chatfield via devel wrote:
> > That's not really fair. DNF is pretty much only the user interface,
> > and everything it's built on top of (hawkey, librepo, libsolv) is
> > implemented in C / C++. And when I think back to using yum, dnf is
> > really fast :)
https://bugzilla.redhat.com/show_bug.cgi?id=1792699
--- Comment #6 from Petr Pisar ---
Bugs are not automatically linked to updates. When one creates an update in
Bodhi, one have to link the bug from there.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1792699
--- Comment #5 from Fedora Update System ---
FEDORA-2020-52c67f5214 has been submitted as an update to Fedora 31.
https://bodhi.fedoraproject.org/updates/FEDORA-2020-52c67f5214
--
You are receiving this mail because:
You are on the CC list
https://bugzilla.redhat.com/show_bug.cgi?id=1792699
Petr Pisar changed:
What|Removed |Added
Status|NEW |MODIFIED
CC|
https://bugzilla.redhat.com/show_bug.cgi?id=1795181
Bug ID: 1795181
Summary: Add perl-WWW-Curl to EPEL 8
Product: Fedora EPEL
Version: epel8
Status: NEW
Component: perl-WWW-Curl
Keywords: FutureFeature
Assignee:
https://bugzilla.redhat.com/show_bug.cgi?id=1794711
Petr Pisar changed:
What|Removed |Added
Status|NEW |CLOSED
Resolution|---
https://bugzilla.redhat.com/show_bug.cgi?id=1794710
--- Comment #4 from Petr Pisar ---
*** Bug 1794711 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel
Hi,
I've tried to get in touch with David Dick about
perl-DateTime-Format-RFC3339. The bug was left untouched, even after
setting need-info flag. I've also tried to reach to him by direct mail.
According to fedora_active_user, last FAS login was on 2019-12-10, but
he had no activity since
https://bugzilla.redhat.com/show_bug.cgi?id=1795179
Bug ID: 1795179
Summary: Non-responsive maintainer check for ddick
Product: Fedora
Version: rawhide
Hardware: All
OS: Linux
Status: NEW
Component:
https://bugzilla.redhat.com/show_bug.cgi?id=1791932
Fedora Update System changed:
What|Removed |Added
Fixed In Version|perl-autodie-2.32-1.fc32|perl-autodie-2.32-1.fc32
https://bugzilla.redhat.com/show_bug.cgi?id=1794710
--- Comment #3 from Fedora Update System ---
FEDORA-2020-d1ec2ede07 has been submitted as an update to Fedora 30.
https://bodhi.fedoraproject.org/updates/FEDORA-2020-d1ec2ede07
--
You are receiving this mail because:
You are on the CC list
https://bugzilla.redhat.com/show_bug.cgi?id=1794207
Fedora Update System changed:
What|Removed |Added
Status|ON_QA |MODIFIED
--- Comment #8 from
https://bugzilla.redhat.com/show_bug.cgi?id=1794710
--- Comment #2 from Fedora Update System ---
FEDORA-2020-e208689c19 has been submitted as an update to Fedora 31.
https://bodhi.fedoraproject.org/updates/FEDORA-2020-e208689c19
--
You are receiving this mail because:
You are on the CC list
https://bugzilla.redhat.com/show_bug.cgi?id=1794710
Petr Pisar changed:
What|Removed |Added
Status|ASSIGNED|MODIFIED
Fixed In Version|
https://bugzilla.redhat.com/show_bug.cgi?id=1794710
Petr Pisar changed:
What|Removed |Added
Status|NEW |ASSIGNED
https://bugzilla.redhat.com/show_bug.cgi?id=1794560
--- Comment #2 from Fedora Update System ---
FEDORA-2020-318e7e1001 has been submitted as an update to Fedora 31.
https://bodhi.fedoraproject.org/updates/FEDORA-2020-318e7e1001
--
You are receiving this mail because:
You are on the CC list
https://bugzilla.redhat.com/show_bug.cgi?id=1794560
Petr Pisar changed:
What|Removed |Added
Status|ASSIGNED|MODIFIED
Fixed In Version|
On 1/26/20 11:52 AM, Nicolas Mailhot wrote:
> Le dimanche 26 janvier 2020 à 10:10 +, Andrew Haley a écrit :
>> On 1/26/20 8:43 AM, Nicolas Mailhot via devel wrote:
>>
>>> Java has been in a terminal course in Fedora for a year at
>>> least. You can see how much Red Hat Java leadership cares
https://bugzilla.redhat.com/show_bug.cgi?id=1795118
Jitka Plesnikova changed:
What|Removed |Added
Status|NEW |CLOSED
Fixed In Version|
https://bugzilla.redhat.com/show_bug.cgi?id=1794560
Petr Pisar changed:
What|Removed |Added
Status|NEW |ASSIGNED
On Mon, Jan 27, 2020 at 6:04 AM Bill Chatfield via devel
wrote:
>
> I have chosen a delinquent Java package to work fix. But I need some help
> understanding what's going on. Groovy is failing to build because it depends
> on gradle-local which doesn't exist. But gradle-local did exist at one
Dne 26. 01. 20 v 23:33 Bill Chatfield via devel napsal(a):
>> You're right. The Java SIG was not organised around an account group,
>> so it does not exist. I don't know why it is that way, but that could
>> easily be fixed - other language interest groups are organised this
>> way, after all
Fabio explained the reasoning etc, but if you are asking where to find
some details yourself, then it is git-dist commit log:
https://src.fedoraproject.org/rpms/gradle/c/4a126e8e3380eda7ceda22b18a9d9633bcd8cda8?branch=master
You can see that in the repository is just `dead.package` file now,
On Mon, Jan 27, 2020, 06:04 Bill Chatfield via devel <
devel@lists.fedoraproject.org> wrote:
> I have chosen a delinquent Java package to work fix. But I need some help
> understanding what's going on. Groovy is failing to build because it
> depends on gradle-local which doesn't exist. But
No missing expected images.
Passed openQA tests: 1/1 (x86_64)
--
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to
1 - 100 of 102 matches
Mail list logo
