Re: [ACTION REQUIRED] FTBFS Packages in rawhide (2015-07-11)
I pushed fixes for Scala on F22 and rawhide and for SBT on F22 last week and am working on fixing SBT for F23. Once this is taken care of, I'll be able to fix the other Scala ecosystem projects pretty quickly, although I am likely to retire some packages where the upstream source has diverged too much from what we'll be able to support in Fedora. tl;dr: no need to retire my packages -- they'll either work again soon or I'll retire them myself! best, wb -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: thrift compatibility concerns (Re: erlang-jsx about to be retired (Re: Orphaned Packages in rawhide (2015-04-20)))
Thanks for raising this, Christopher. I had originally brought Thrift 0.9.1 in because we needed it for some projects in the Big Data SIG, and was hesitant to update because of Thrift's well-documented compatibility issues. However, I was looking at updating because some people have raised concerns about bugs and shortcomings in Thrift 0.9.1 (in particular, I think it doesn't build on ARM). But because of the way that upstreams treat Thrift (typically bundling and never testing against newer versions), we'll need to be careful about any update, and I'm inclined to stay with 0.9.1 unless we have a really compelling reason to possibly break dependent packages. Does anyone have any concerns about Thrift staying at 0.9.1? On a happier note, Peter Lemenkov has stepped up to maintain erlang-jsx (thanks, Peter!), so that won't pose a problems for Thrift going forward. best, wb - Original Message - From: Christopher ctubbsii-fed...@apache.org To: Development discussions related to Fedora devel@lists.fedoraproject.org Sent: Tuesday, April 21, 2015 8:23:36 AM Subject: Re: erlang-jsx about to be retired (Re: Orphaned Packages in rawhide (2015-04-20)) On Tue, Apr 21, 2015 at 12:04 AM, Will Benton wi...@redhat.com wrote: Dan, I've had some trouble updating Thrift to a newer upstream version but have been planning to spin an updated release without Erlang support in the meantime and will ping you when it's ready. Thanks! [snip] FWIW, thrift has had really bad problems with regressions and API stability issues which has affected Accumulo (and Cassandra, and I'm sure others, too) in the past, so I'd be really wary about moving accumulo to use 0.9.2 until there's upstream support for it. (The switch from thrift 0.9.0 to 0.9.1 was *very* painful, as was the initial switch to 0.9.0..., causing massive reimplementation of thrift-provided libraries to be embedded in downstream projects[1][2][3]). Would you consider keeping thrift 0.9.1 available for longer (dropping erlang, as necessary, of course), rather than switch to a newer upstream version? What degree of confidence do you have that 0.9.2 (the current upstream version) doesn't break thrift 0.9.1-based projects? [1]: http://bit.ly/1IBSsrW [2]: https://issues.apache.org/jira/browse/ACCUMULO-1691 [3]: https://issues.apache.org/jira/browse/ACCUMULO-2950 -- Christopher L Tubbs II http://gravatar.com/ctubbsii -- Christopher L Tubbs II http://gravatar.com/ctubbsii On Tue, Apr 21, 2015 at 12:04 AM, Will Benton wi...@redhat.com wrote: Dan, I've had some trouble updating Thrift to a newer upstream version but have been planning to spin an updated release without Erlang support in the meantime and will ping you when it's ready. Thanks! best, wb - Original Message - From: Dan Callaghan dcall...@redhat.com To: devel devel@lists.fedoraproject.org Cc: Will Benton wiben...@redhat.com Sent: Monday, April 20, 2015 7:18:01 PM Subject: erlang-jsx about to be retired (Re: Orphaned Packages in rawhide (2015-04-20)) Dear Erlang folks, (I'm not subscribed to the list so please cc me in replies.) I maintain python-txamqp which has a transitive dependency on erlang-jsx via thrift. The erlang-jsx package was orphaned about 6 weeks ago which means it, along with a chain of dependent packages, will be retired soon. See the orphaned packages notice quoted below. Could someone interested in Erlang please take erlang-jsx? Alternatively Will as maintainer of thrift, could you drop the erlang-thrift subpackage so that thrift doesn't get retired? Excerpts from opensource's message of 2015-04-21 04:00 +10:00: 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 you received this mail directly you (co)maintain one of the affected packages or a package that depends on one. Please adopt the affected package or retire your depending package to avoid broken dependencies, otherwise your package will be retired when the affected package gets retired. Package (co)maintainers Status Change == erlang-jsx orphan, erlang-sig, peter6 weeks ago gnome-schedule orphan, sundaram 4 weeks ago identicurse orphan, smilner 5 weeks ago jackrabbit orphan 6 weeks ago libgtkhotkeyorphan, sundaram 4 weeks ago mercury orphan 6 weeks ago naimorphan, lmacken 4 weeks ago netactview
Re: erlang-jsx about to be retired (Re: Orphaned Packages in rawhide (2015-04-20))
Dan, I've had some trouble updating Thrift to a newer upstream version but have been planning to spin an updated release without Erlang support in the meantime and will ping you when it's ready. Thanks! best, wb - Original Message - From: Dan Callaghan dcall...@redhat.com To: devel devel@lists.fedoraproject.org Cc: Will Benton wiben...@redhat.com Sent: Monday, April 20, 2015 7:18:01 PM Subject: erlang-jsx about to be retired (Re: Orphaned Packages in rawhide (2015-04-20)) Dear Erlang folks, (I'm not subscribed to the list so please cc me in replies.) I maintain python-txamqp which has a transitive dependency on erlang-jsx via thrift. The erlang-jsx package was orphaned about 6 weeks ago which means it, along with a chain of dependent packages, will be retired soon. See the orphaned packages notice quoted below. Could someone interested in Erlang please take erlang-jsx? Alternatively Will as maintainer of thrift, could you drop the erlang-thrift subpackage so that thrift doesn't get retired? Excerpts from opensource's message of 2015-04-21 04:00 +10:00: 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 you received this mail directly you (co)maintain one of the affected packages or a package that depends on one. Please adopt the affected package or retire your depending package to avoid broken dependencies, otherwise your package will be retired when the affected package gets retired. Package (co)maintainers Status Change == erlang-jsx orphan, erlang-sig, peter6 weeks ago gnome-schedule orphan, sundaram 4 weeks ago identicurse orphan, smilner 5 weeks ago jackrabbit orphan 6 weeks ago libgtkhotkeyorphan, sundaram 4 weeks ago mercury orphan 6 weeks ago naimorphan, lmacken 4 weeks ago netactview orphan 3 weeks ago obexftp orphan, itamarjp 1 weeks ago perl-File-SearchPathorphan, georgiou, perl-sig 0 weeks ago perl-Term-Clui orphan, georgiou, perl-sig 0 weeks ago porkorphan, lmacken 4 weeks ago python-sockjs-tornado orphan, gholms 4 weeks ago python-sqlalchemy0.5orphan 2 weeks ago python-sqlamp orphan 2 weeks ago python-xkit orphan, sundaram 4 weeks ago xlhtml orphan, sundaram 4 weeks ago xprobe2 orphan, lmacken 4 weeks ago zoneminder orphan, mebourne 1 weeks ago The following packages require above mentioned packages: Depending on: erlang-jsx (28), status change: 2015-03-04 (6 weeks ago) thrift (maintained by: willb) erlang-thrift-0.9.1-13.fc22.3.i686 requires erlang-jsx = 1.4.2-4.fc22 accumulo (maintained by: ctubbsii, mizdebsk) accumulo-1.6.1-2.fc22.src requires libthrift-java = 0.9.1-13.fc22.3 accumulo-core-1.6.1-2.fc22.noarch requires mvn(org.apache.hadoop:hadoop-client) = 2.4.1, mvn(org.apache.thrift:libthrift) = 0.9.1 accumulo-gc-1.6.1-2.fc22.noarch requires mvn(org.apache.hadoop:hadoop-client) = 2.4.1, mvn(org.apache.thrift:libthrift) = 0.9.1 accumulo-master-1.6.1-2.fc22.noarch requires mvn(org.apache.hadoop:hadoop-client) = 2.4.1, mvn(org.apache.thrift:libthrift) = 0.9.1 accumulo-server-base-1.6.1-2.fc22.noarch requires mvn(org.apache.hadoop:hadoop-client) = 2.4.1, mvn(org.apache.thrift:libthrift) = 0.9.1 accumulo-tracer-1.6.1-2.fc22.noarch requires mvn(org.apache.hadoop:hadoop-client) = 2.4.1, mvn(org.apache.thrift:libthrift) = 0.9.1 accumulo-tserver-1.6.1-2.fc22.noarch requires mvn(org.apache.hadoop:hadoop-client) = 2.4.1, mvn(org.apache.thrift:libthrift) = 0.9.1 accumulo-examples-1.6.1-2.fc22.noarch requires mvn(org.apache.hadoop:hadoop-client) = 2.4.1 amplab-tachyon (maintained by: tstclair, hchen, java-sig) amplab-tachyon-0.4.1-2.SNAPSHOT.4b9c806.fc21.noarch requires mvn(org.apache.thrift:libthrift) = 0.9.1 amplab-tachyon-0.4.1-2.SNAPSHOT.4b9c806.fc21.src requires mvn(org.apache.thrift:libthrift) = 0.9.1, thrift = 0.9.1-13.fc22.3 avro (maintained by: ricardo
Re: None-responsive Maintainer of the scala package
Sorry for any confusion, Jochen. The next step in the process is notifying fedora-devel, which it appears we're doing now. Jochen, would your preferred resolution be to be the primary maintainer (with one or more co-maintainers)? best, wb - Original Message - From: Jochen Schmitt joc...@herr-schmitt.de 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 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 without start the whole none-responsive process at the beginnning. Best Regards: Jochen Schmitt [1} orry fo -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Scala package owner unresponsive
- Original Message -
From: Antoine Gourlay anto...@gourlay.fr
To: Development discussions related to Fedora
devel@lists.fedoraproject.org
Sent: Thursday, September 12, 2013 6:22:05 AM
Subject: Re: Scala package owner unresponsive
Do you have the log output of the failing tests?
I can probably dig it up, but the breakdown was something like this:
* most of the failures were because they expected different character encodings
than the default in JDK7 (crashing with MalformedInputExceptions)
* a couple of tests (the pax exam for OSGi testing in particular) failed under
rpmbuild but not in a by-hand run in my ~rpmbuild/BUILD directory
* one test failed under mock but not under rpmbuild
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;
Thanks for pointing this out. I had caught this in an earlier attempt to fix
this package but missed it this time. The SRPM (2.10.1-4) and spec are now
fixed to reflect this.
best,
wb
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Scala package owner unresponsive
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 disable several tests that failed spuriously (as far as I can tell). But I think the package should be at least as good as the one we had before. Jochen Schmitt, are you willing to update the build in F19 and rawhide with these fixes? - Original Message - From: Will Benton wi...@redhat.com To: Development discussions related to Fedora devel@lists.fedoraproject.org Sent: Thursday, September 5, 2013 5:26:23 PM Subject: Re: Scala package owner unresponsive 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 joc...@herr-schmitt.de To: Development discussions related to Fedora devel@lists.fedoraproject.org Sent: Thursday, August 22, 2013 6:03:46 AM Subject: Re: Scala package owner unresponsive On Sun, Aug 18, 2013 at 09:41:52PM -0600, Jerry James wrote: On Sun, Aug 18, 2013 at 9:35 PM, Will Benton wi...@redhat.com 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 a working Scala 2.9 package in F19 and introduce 2.10 in a later release? Version 2.9.2-4 was built for F-18, but was never built for F-19 or F-20. The changelog entries for -3 and -4 say: 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. Fedora 19 and late doesn't provides a jdk-1.6.0 environment which is the reason for the broken dependency. So it's impossible to build scala-2.9.x for F19 or later releases for Fedora. Best Regards: Jochen Schmitt -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Scala package owner unresponsive
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 wi...@redhat.com To: Development discussions related to Fedora devel@lists.fedoraproject.org Sent: Wednesday, September 11, 2013 9:32:39 PM Subject: Re: Scala package owner unresponsive 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 disable several tests that failed spuriously (as far as I can tell). But I think the package should be at least as good as the one we had before. Jochen Schmitt, are you willing to update the build in F19 and rawhide with these fixes? - Original Message - From: Will Benton wi...@redhat.com To: Development discussions related to Fedora devel@lists.fedoraproject.org Sent: Thursday, September 5, 2013 5:26:23 PM Subject: Re: Scala package owner unresponsive 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 joc...@herr-schmitt.de To: Development discussions related to Fedora devel@lists.fedoraproject.org Sent: Thursday, August 22, 2013 6:03:46 AM Subject: Re: Scala package owner unresponsive On Sun, Aug 18, 2013 at 09:41:52PM -0600, Jerry James wrote: On Sun, Aug 18, 2013 at 9:35 PM, Will Benton wi...@redhat.com 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 a working Scala 2.9 package in F19 and introduce 2.10 in a later release? Version 2.9.2-4 was built for F-18, but was never built for F-19 or F-20. The changelog entries for -3 and -4 say: 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. Fedora 19 and late doesn't provides a jdk-1.6.0 environment which is the reason for the broken dependency. So it's impossible to build scala-2.9.x for F19 or later releases for Fedora. Best Regards: Jochen Schmitt -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Scala package owner unresponsive
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 joc...@herr-schmitt.de To: Development discussions related to Fedora devel@lists.fedoraproject.org Sent: Thursday, August 22, 2013 6:03:46 AM Subject: Re: Scala package owner unresponsive On Sun, Aug 18, 2013 at 09:41:52PM -0600, Jerry James wrote: On Sun, Aug 18, 2013 at 9:35 PM, Will Benton wi...@redhat.com 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 a working Scala 2.9 package in F19 and introduce 2.10 in a later release? Version 2.9.2-4 was built for F-18, but was never built for F-19 or F-20. The changelog entries for -3 and -4 say: 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. Fedora 19 and late doesn't provides a jdk-1.6.0 environment which is the reason for the broken dependency. So it's impossible to build scala-2.9.x for F19 or later releases for Fedora. Best Regards: Jochen Schmitt -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Scala package owner unresponsive
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 introduce 2.10 in a later release? (2) I'm interested in hearing from folks who are using Scala on Fedora (or who have strong opinions about what Fedora should look like with more Scala) because I've recently been trying to package sbt (as a first step to getting more ecosystem projects into Fedora). best, wb - Original Message - From: Jochen Schmitt joc...@herr-schmitt.de To: codebl...@fedoraproject.org, Development discussions related to Fedora devel@lists.fedoraproject.org Sent: Wednesday, August 14, 2013 11:33:32 AM Subject: Re: Scala package owner unresponsive 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 working package for scala you may send me it, so I may commit it into the repository and initiate the update for F19. As a co-maintainer I have tried to create a package for scala-2.10.x without success. I was able to built the package locally, but the build failed on koji. That is the reason, that the current state of the scala git repository on Fedora is in a accident state. Best Regards: Jochen Schmitt -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
introducing myself
Hi all, My name is Will Benton, and I work on grid and cloud stuff at Red Hat. I've been here since Fall 2008, but I've been a Red Hat user since the RHL era (Picasso was the first RHL release I used every day). My pre-Red Hat experience mainly consists of work on compilers, static program analysis, concurrency, and music technology. I'm interested in becoming a Fedora packager and maintaining a package for Wallaby (http://getwallaby.com), which is a configuration service for Condor pools. Wallaby first appeared in Red Hat Enterprise MRG in version 1.3, and I'd like to see it in Fedora to help encourage a larger user and developer community around the upstream project. I develop and test on Fedora, EL5, and EL6, so packaging Wallaby for Fedora is already a part of my development workflow. I'd really appreciate it if someone would be willing to sponsor me as a new packager and review the Wallaby package. I've filed a BZ review request here: https://bugzilla.redhat.com/show_bug.cgi?id=702143 Thanks for your time. I'm looking forward to taking a more active part in the Fedora community! best, wb -- William C. Benton wi...@redhat.com Senior Software Engineer, Red Hat MRG -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
