Log of the #fcrepo channel on chat.freenode.net

Using timezone: Eastern Standard Time
* sbmarks joins01:00
* ksclarke leaves01:10
* dwilcox joins07:43
* dhlamb joins08:38
* acoburn joins08:43
* esm_ joins08:45
* sbmarks leaves09:04
* ksclarke joins09:10
* sbmarks joins09:23
* dwilcox leaves09:31
* github-ff joins10:23
[fcrepo4] acoburn opened pull request #909: set build-tools version (master...fcrepo-1728) http://git.io/vZMHn
* github-ff leaves
* github-ff joins10:34
[fcrepo4] awoods closed pull request #901: FCREPO-1627 (https://jira.duraspace.org/browse/FCREPO-1627) (master...fcrepo-1627) http://git.io/vGygl
* github-ff leaves
* whikloj joins10:41
* acoburn leaves10:58
* dwilcox joins11:08
* acoburn joins11:49
* github-ff joins12:33
[fcrepo-camel] daniel-dgi opened pull request #92: Resolves FCREPO-1729 (master...commons-codec-group-change) http://git.io/vZDQS
* github-ff leaves
* escowles joins12:59
* acoburn leaves13:15
* acoburn joins13:16
* github-ff joins13:19
[fcrepo-camel] acoburn closed pull request #92: Resolves FCREPO-1729 (master...commons-codec-group-change) http://git.io/vZDQS
* github-ff leaves
* travis-ci joins13:22
fcrepo4-exts/fcrepo-camel#221 (master - e65105f : Aaron Coburn): The build passed.
Change view : https://github.com/fcrepo4-exts/fcrepo-camel/compare/23afe740bc8e...e65105f8d9a7
Build details : https://travis-ci.org/fcrepo4-exts/fcrepo-camel/builds/80280959
* travis-ci leaves
<whikloj>or awoods ping in fcrepo13:32
<whikloj>awoods: Good to go for either alternate WebAC sprint dates
<awoods>whikloj: that is great... I will touch base with UMd13:40
<whikloj>awoods: cool
<awoods>whikloj: I offered two sets of dates: Oct 12 or Oct 26. Are you saying that one of either of the two would work for you?13:45
<whikloj>awoods: yes, both are open. Let me know which you want to do and we will add that to our schedule
<awoods>whikloj: let's figure out the dates that are best for everyone at Wednesday's meeting.13:50
<whikloj>awoods: ok
awoods: is that meeting on ReadyTalk?13:51
<awoods>whikloj: yes
<dhlamb>awoods: acoburn: 'bout how long does it take for changes to roll through to public maven repositories? would the change you merged in today be there sometime tonight when i get a chance to work on things?14:22
<awoods>dhlamb: it usually takes less than an hour
<acoburn>dhlamb: if you need it immediately, you can always do a "mvn clean install"14:23
<dhlamb>awoods: perfect, thx
<awoods>dhlamb: the snapshot artifacts show up in the public sonatype:snapshots repo, not maven central.
<dhlamb>awoods: acoburn: want to test things the way they should be when going through the vagrant install. don't want to point that to my version.14:24
<awoods>dhlamb: your are deploying fcrepo-camel-toolbox into karaf with a features.xml?14:26
<dhlamb>awoods: correct
<awoods>dhlamb: with the recent commit to fcrepo-camel, are you still seeing issues?14:27
<dhlamb>awoods: just cycled my vagrant install to verify. only have issues with fcrepo-audit-triplestore now. others seem to be installing fine.14:30
awoods: acoburn: getting this mildly cryptic error message -> Error executing command: Unable to resolve root: missing requirement [root] osgi.identity;14:31
<acoburn>dhlamb: are you using the fcrepo-karaf features.xml file?14:33
<dhlamb>acoburn: using this command: feature:repo-add mvn:org.fcrepo.camel/fcrepo-camel-toolbox/LATEST/xml/features14:35
<acoburn>dhlamb: and what version of karaf?14:36
<dhlamb>acoburn: 4.0.1
acoburn: i see mention of the fcrepo-karaf feature way down at the bottom when dealing with transitive dependencies
acoburn: should i use that instead and torch that list near the bottom of the features file?14:37
<acoburn>dhlamb: not yet, that's still in a state of development
<dhlamb>acoburn: fixity, solr, etc.. all seem to be fine. just the audit. seems like it can't resolve itself?14:39
acoburn: ooooooooooh wait a minute14:40
acoburn: full error: Error executing command: Unable to resolve root: missing requirement [root] osgi.identity; osgi.identity=fcrepo-audit-triplestore; type=karaf.feature; version="[4.3.1.SNAPSHOT,4.3.1.SNAPSHOT]"; filter:="(&(osgi.identity=fcrepo-audit-triplestore)(type=karaf.feature)(version>=4.3.1.SNAPSHOT)(version<=4.3.1.SNAPSHOT))" [caused by: Unable to resolve fcrepo-audit-triplestore/4.3.1.SNAPSHOT: missing requirement [fcrepo-audit-triple
store/4.3.1.SNAPSHOT] osgi.identity; osgi.identity=org.fcrepo.camel.fcrepo-audit-triplestore; type=osgi.bundle; version="[4.3.1.SNAPSHOT,4.3.1.SNAPSHOT]"; resolution:=mandatory [caused by: Unable to resolve org.fcrepo.camel.fcrepo-audit-triplestore/4.3.1.SNAPSHOT: missing requirement [org.fcrepo.camel.fcrepo-audit-triplestore/4.3.1.SNAPSHOT] osgi.wiring.package; filter:="(osgi.wiring.package=org.apache.clerezza.rdf.core)"]]
acoburn: seeing a bit about clerezza at the bottom there. didn't you guys torch clerezza recently?
<acoburn>dhlamb: I swapped out the clerezza stuff a few weeks ago, the feature files probably didn't get updated14:41
dhlamb: hang on, and I'll have a PR for you to test.
dhlamb: ahh — I see the problem. I'll have a fix for you pretty soon14:42
* dwilcox leaves15:29
<acoburn>awoods: re fcrepo-1728, I'm not sure those other projects are affected15:47
<awoods>acoburn: meaning, those other projects do not use build-tools?15:48
<acoburn>awoods: they do use build-tools15:49
awoods: I'm not sure I understand
<awoods>...but depend on the version number from fcrepo-parent?
<acoburn>awoods: the issue is this: say fcrepo-camel in incremented to 4.3.1 before fcrepo4 (which is still at 4.3.0)15:50
<awoods>acoburn: that is one scenario
<acoburn>awoods: then, in order to build fcrepo-camel 4.3.1, it will look for a copy of build-tools at version 4.3.1 (which may not exist)
<awoods>acoburn: what about the scenario where fcrepo is incremented, but build-tools is not?15:51
<acoburn>awoods: that is also a reason for this PR
awoods: then, fcrepo4 still uses 4.3.0 version of build-tools15:52
<awoods>acoburn: for example, see: https://github.com/fcrepo4-exts/fcrepo-camel-toolbox/blob/master/pom.xml#L440
<acoburn>awoods: yes, fcrepo-camel needs to start using fcrepo-parent as a parent pom
awoods: and fcrepo-camel-toolbox15:53
awoods: I just haven't gotten there yet
<awoods>acoburn: that is a separate issue
<acoburn>awoods: correct
<awoods>acoburn: the issue in this case is that the projects mention in the comment on fcrepo-1728 should not be depending on fcrepo-build-tools:project.version15:54
acoburn: they should be depending on: fcrepo-build-tools:fcrepo-build-tools.version15:55
<acoburn>awoods: yes, exactly
awoods: and if we extend the ticket to mean that, then yes, those other projects are affected15:56
<awoods>acoburn: if we do not extend the ticket to mean that, then our modules are left in a dangerous state.
acoburn: the projects are left in a state that could depend on a version of build-tools that does not exist.15:57
acoburn: I am happy to do some of the updates if you see it the same way.15:58
<acoburn>awoods: I agree with that assessment
awoods: (on a different topic) a few weeks ago I replaced the clerezza-based RDF processing code in fcrepo-camel with jena16:00
<awoods>acoburn: yes
<acoburn>awoods: do you remember what ticket that was for? I can't seem to find it
* dhlamb leaves16:01
* awoods looking16:02
acoburn: here, for some reason: https://jira.duraspace.org/browse/FCREPO-166716:04
awoods: I wanted to put dhlamb's issue somewhere, but I don't think reopening that one is appropriate
awoods: I'll create a new issue16:06
<awoods>acoburn: thanks
* esm_ leaves16:08
* github-ff joins16:11
[fcrepo-camel-toolbox] acoburn opened pull request #52: replace clerezza code with jena (master...fcrepo-1730) http://git.io/vZSnm
* github-ff leaves
<awoods>acoburn: it seems like a similar issue with https://jira.duraspace.org/browse/FCREPO-169416:19
acoburn: basically, more implementation is needed to address the issue of the ticket.
* dwilcox joins
* acoburn leaves16:20
* acoburn joins
<awoods>acoburn: did you get the messages above re:fcrepo-169416:21
<acoburn>awoods: you mean via jira or IRC?
<awoods>acoburn: both16:22
<acoburn>awoods: didn't see anything on IRC, I'll check the logs
awoods: well, I saw the messages on the jira ticket16:23
<awoods>acoburn: ok16:24
<acoburn>awoods: my reading of the jira comment is that fcrepo-connector-file is ok as-is
<awoods>acoburn: yes, and the larger topic (which is similar to the issue of https://jira.duraspace.org/browse/FCREPO-1728) is whether we want to establish a pattern of closing tickets based on partial solutions.16:26
<acoburn>awoods: I was assuming that fcrepo-1694 would be worked-reviewed-reopened multiple times before it was actually closed16:27
awoods: I don't think we want to close an issue if it is only partially addressed16:28
<awoods>acoburn: that sounds right. It was not clear to me that you were expecting a review/reopen/review/... flow for fcrepo-1694. But since you are, that sounds good.16:29
<acoburn>awoods: btw, I was chatting with bseeger about large literal values16:31
<awoods>acoburn: what does bseeger have to say?
<acoburn>awoods: do you know that those values are being persisted in the binary store?
<awoods>acoburn: over a certain size, yes
<acoburn>awoods: might that have something to do with the problems? or is that expected?16:32
<awoods>acoburn: and that size is configurable
<acoburn>awoods: yes, she'll be in touch about this tomorrow
* dwilcox leaves
<acoburn>awoods: I have to step out for a bit
<awoods>acoburn: thanks
* github-ff joins17:14
[fcrepo-camel] acoburn opened pull request #93: update/cleanup maven to use fcrepo-parent (master...fcrepo-1728) http://git.io/vZSrx
* github-ff leaves
* dwilcox joins17:46
* dwilcox leaves17:47
* dwilcox joins17:49
* github-ff joins17:50
[fcrepo-camel-toolbox] acoburn opened pull request #53: clean up/reorg maven config, inheriting from fcrepo-parent (master...fcrepo-1728) http://git.io/vZSyN
* github-ff leaves
<acoburn>awoods: ping17:51
<acoburn>awoods: for the fcrepo4-bom (fcrepo-1728), do you think the dependency on fcrepo-build-tools should be removed or should the dependency version be made explicit?17:52
awoods: that is, when a module use fcrepo4-bom, should it get the relevant version of fcrepo-build-tools along with the rest, or should that be kept separate?17:54
<awoods>acoburn: maybe build-tools should be removed from the bom since we can not set the a property placeholder there.17:56
acoburn: what are your thoughts?17:57
<acoburn>awoods: I'm inclined to remove it
<awoods>acoburn: if we decouple build-tools from the core code base, it becomes like any other external dependency.
<acoburn>awoods: exactly, which is why I used version 4.3.0 instead of 4.3.1-SNAPSHOT in the PR17:58
awoods: I will add a commit to pr #90917:59
<awoods>acoburn: thanks
* whikloj leaves
<awoods>acoburn: are you also planning on adding PRs for the other related projects?
<acoburn>awoods: not tonight
<awoods>acoburn: ok18:00
<acoburn>awoods: I can chip away at them tomorrow
<awoods>acoburn: thanks
<acoburn>awoods: I'm not entirely sure about the message-consumer though
<awoods>acoburn: in what way?
<acoburn>awoods: at what point do we stop maintaining it?
<awoods>acoburn: once we have a replacement18:01
<acoburn>awoods: you mean a replacement for the "transparent filesystem" piece?
<awoods>acoburn: yes, I think that is the last piece
<acoburn>awoods: got it
<awoods>acoburn: do you know if ajs6f is still working on that?18:02
<acoburn>awoods: I don't know
awoods: I lost track of that during the webac sprint
* acoburn leaves
* ksclarke leaves18:10
* dwilcox leaves18:20
<ruebot_afk>awoods: ping19:15
<ruebot>awoods: question about testing for webac -- can i just deploy the war in fcrepo vagrant?19:16
<awoods>ruebot: yes
awoods: thanks!
<awoods>ruebot: good luck
* dwilcox joins19:17
* dwilcox leaves19:35
* ksclarke joins20:26
* dhlamb joins20:46
* github-ff joins21:41
[fcrepo-camel-toolbox] awoods opened pull request #54: Update fcrepo dependencies to project.version (master...fcrepo-1731) http://git.io/vZ9z7
* github-ff leaves
* dhlamb leaves23:24
* terrellt leaves23:28
* terrellt joins23:36
* terrellt leaves23:40
* terrellt joins00:10
* ksclarke leaves00:18