Hi,
I'm orphaning the Scala 2 package. It's been very complicated to
maintain this package due to the complexity and lack of SBT package on
Fedora. There is no dependencies and I don't think anyone is using it,
as the Scala 3 has been available for some tim
Hi Christiano,
On Wed, Aug 23, 2023 at 5:30 AM Christiano Anderson
wrote:
> I'm Scala developer and I'm willing to maintain (or co-maintain) Scala
> package, maybe add Scala 3 as well.
>
> Since I have never maintained any Fedora package, if I find a sponsor, I'll
&
I'm Scala developer and I'm willing to maintain (or co-maintain) Scala package,
maybe add Scala 3 as well.
Since I have never maintained any Fedora package, if I find a sponsor, I'll be
glad to maintain (or co-maintain) Scala.
___
dev
On Fri, Aug 11, 2023 at 10:30 AM Jerry James wrote:
> java-diff-utils
> jline
> jol
> juniversalchardet
> material-icons-fonts
> scala
> scalacheck
Also the test-interface package.
--
Jerry James
http://www.jamezone.org/
_
A couple of years ago, I picked up the scala package because a couple
of packages I care about depended on it. In the past few months both
packages have dropped their scala dependencies. I am orphaning the
following packages:
java-diff-utils
jline
jol
juniversalchardet
material-icons-fonts
Miro Hrončok wrote:
> [~]$ repoquery --installed --whatrequires coin-or-Cbc
> coin-or-Clp-0:1.17.6-2.fc33.x86_64
Why does Clp require Cbc? As far as I know, Cbc uses Clp, not the opposite.
I see coin-or-Cbc goes through great lengths to bootstrap the circular
dependency on Cbc, to manually set C
On Thu, Jan 28, 2021 at 5:08 AM Miro Hrončok wrote:
> I've realized I have scala installed on my F33 developer machine and wanted to
> remove it. But apparently, opencv-core pulls it in:
>
> [~]$ repoquery --installed --whatrequires scala
> jacop-0:4.8-2.fc33.noarch
> [~]
On Thu, 2021-01-28 at 13:08 +0100, Miro Hrončok wrote:
> I've realized I have scala installed on my F33 developer machine and
> wanted to
> remove it. But apparently, opencv-core pulls it in:
>
> [~]$ repoquery --installed --whatrequires scala
> jacop-0:4.8-2.fc33.
I've realized I have scala installed on my F33 developer machine and wanted to
remove it. But apparently, opencv-core pulls it in:
[~]$ repoquery --installed --whatrequires scala
jacop-0:4.8-2.fc33.noarch
[~]$ repoquery --installed --whatrequires jacop
mp-0:3.1.0-31.20200303git7fd4828
I am about to build scala 2.13.4 in Rawhide. This comes with a
license change from:
BSD and CC0 and Public Domain
to:
ASL 2.0 and BSD and MIT
Regards,
--
Jerry James
http://www.jamezone.org/
___
devel mailing list -- devel@lists.fedoraproject.org
On Mon, Dec 7, 2020 at 11:51 AM Jerry James wrote:
> - Figure out if jansi 2.0.1 is backwards compatible with jansi 1.18. If it is
> not, then we'll have to figure out how to make parallel installable versions
> of jansi 1.18 and 2.0.1, or else port everything currently using 1.18 to
> 2.0.
Scala has been orphaned. I don't do anything with scala personally,
but I would like to see jacop stay in Fedora. So I've been poking
around to see how hard it would be to rescue scala, as well as move it
up to a more recent version. The results of my poking around can be
seen he
scala package license tag has been corrected from:
BSD
to:
BSD and CC0 and Public Domain
Michael
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https
= Proposed Self Contained Change: Improved Scala Ecosystem Support =
https://fedoraproject.org/wiki/Changes/ImprovedScalaEcosystem
Change owner(s): William Benton
Fedora now supports several essential parts of the Scala language ecosystem as
well as building packages with sbt, the de facto
> one or more co-maintainers)?
No, I was confused because I saw no action and I have tried to contact you via
mail.
But I'm assume that this mail was going into your spam filter.
If you are going forward in the process, I will prefered the role of a
co-maintainer of the
scala package.
Best
ochen Schmitt"
> To: devel@lists.fedoraproject.org
> Sent: Saturday, December 7, 2013 6:32:01 AM
> Subject: None-responsive Maintainer of the scala package
>
> Hello,
>
> We have an open bug [1] becouse the primary mantainer of the scala
> package shows no respo
Hello,
We have an open bug [1] becouse the primary mantainer of the scala
package shows no response for open bugs.
Unfortunately, the original bug reporter seems to lost the inerest
to finish the none-responsive maintainer process.
So I would like to ask, if it ok to reassign the bug to myself
- Original Message -
> From: "Antoine Gourlay"
> To: "Development discussions related to Fedora"
>
> Sent: Thursday, September 12, 2013 6:22:05 AM
> Subject: Re: Scala package owner unresponsive
>
> Do you have the log output of the failing
Great news! Thanks for doing this.
Do you have the log output of the failing tests?
Also, the Source0 URL doesn't work (404) with the new layout of the
scala-lang website, it should now be
"http://www.scala-lang.org/files/archive/scala-sources-%{fullversion}.tgz";
On Thu, Sep 1
If it's more convenient to import a SRPM (of course it is!), I've made one
available at http://freevariable.com/scala
- Original Message -
> From: "Will Benton"
> To: "Development discussions related to Fedora"
>
> Sent: Wednesday, Septembe
I have made a spec file for Scala 2.10.1 that successfully builds under mock on
F19; it is available here:
https://github.com/willb/scala-packaging
I had to make a new patch to account for interface changes in JLine 2.7,
disable optimization (due to a known bug in the Scala optimizer), and
I see that scala is on the to-be-retired list unless it starts building from
source. I am interested in using Scala in Fedora, and will take on
maintainership (for a while, at least) if no one else is willing to fix it.
- Original Message -
> From: "Jochen Schmitt"
>
On 08/22/2013 01:03 PM, Jochen Schmitt wrote:
Yes, the reason fot this is very simple. On F18 we had a jdk-1.6.0 environment
in
addition to the jdk-1.7.0. Scala was built explicitly agains jdk-1.6.0 because
jdk-1.7.0
is not supported on this release.
Really? How did *that* happen
On Sun, Aug 18, 2013 at 09:41:52PM -0600, Jerry James wrote:
> On Sun, Aug 18, 2013 at 9:35 PM, Will Benton wrote:
> > (1) As far as I can tell, the package for Scala 2.9.2 on F19 (2.9.2-2) has
> > broken dependencies; I can't install it via yum on my new F19 install. Is
&
On Sun, 18 Aug 2013 21:41:52 -0600, Jerry James wrote:
> On Sun, Aug 18, 2013 at 9:35 PM, Will Benton wrote:
> > (1) As far as I can tell, the package for Scala 2.9.2 on F19 (2.9.2-2) has
> > broken dependencies; I can't install it via yum on my new F19 install. Is
&
On Sun, Aug 18, 2013 at 9:35 PM, Will Benton wrote:
> (1) As far as I can tell, the package for Scala 2.9.2 on F19 (2.9.2-2) has
> broken dependencies; I can't install it via yum on my new F19 install. Is
> this the case for anyone else? If so, wouldn't it be best to have
On two related notes,
(1) As far as I can tell, the package for Scala 2.9.2 on F19 (2.9.2-2) has
broken dependencies; I can't install it via yum on my new F19 install. Is this
the case for anyone else? If so, wouldn't it be best to have a working Scala
2.9 package in F19 and intr
On Wed, Aug 14, 2013 at 07:12:32AM -0400, Ricky Elrod wrote:
> I would like to take over this package and update it to 2.10.x for
> Fedora 21 (or possibly 20, though it wouldn't be an official "Change",
> because we're past the proposal deadline).
If you have a work
I would like to begin following the policy for nonresponsive package
maintainers with regard to the 'scala' package.
I have attempted emailing the maintainer several times offering to
co-maintain the package and have heard nothing in return.
There is an open bug on the package for up
This Feature has been submitted *before* Feature Submission Deadline and it
required input/changes from the owner or was queued.
= Features/Scala210 =
https://fedoraproject.org/wiki/Features/Scala210
Feature owner(s): Jochen Schmitt
Providing the most current relase of Scala a functional
Il 07/01/2013 18:46, gil ha scritto:
Il 07/01/2013 17:14, Jochen Schmitt ha scritto:
Hallo,
Unfortunately, I have an issue to build scala-2.10.0 on rawhide. I have
got the following error message from the buildsystem:
artifact:dependencies] Diagnosis:
[artifact:dependencies
Il 07/01/2013 17:14, Jochen Schmitt ha scritto:
Hallo,
Unfortunately, I have an issue to build scala-2.10.0 on rawhide. I have
got the following error message from the buildsystem:
artifact:dependencies] Diagnosis:
[artifact:dependencies]
[artifact:dependencies] Unable to resolve artifact
Hallo,
Unfortunately, I have an issue to build scala-2.10.0 on rawhide. I have
got the following error message from the buildsystem:
artifact:dependencies] Diagnosis:
[artifact:dependencies]
[artifact:dependencies] Unable to resolve artifact: Missing:
[artifact:dependencies
33 matches
Mail list logo
