#duraspace IRC Log


IRC Log for 2017-07-24

Timestamps are in GMT/BST.

[6:33] -rajaniemi.freenode.net- *** Looking up your hostname...
[6:33] -rajaniemi.freenode.net- *** Checking Ident
[6:33] -rajaniemi.freenode.net- *** Found your hostname
[6:33] -rajaniemi.freenode.net- *** No Ident response
[6:33] * DuraLogBot (~PircBot@webster.duraspace.org) has joined #duraspace
[6:33] * Topic is 'Welcome to DuraSpace IRC. This channel is used for formal meetings and is logged - http://irclogs.duraspace.org/'
[6:33] * Set by tdonohue on Thu Sep 15 17:49:38 UTC 2016
[12:15] * misilot (~misilot@p-body.lib.fit.edu) has joined #duraspace
[12:26] * mhwood (~mhwood@mhw.ulib.iupui.edu) has joined #duraspace
[13:24] * dyelar (~dyelar@biolinux.mrb.ku.edu) has joined #duraspace
[13:36] * tdonohue (~tdonohue@dspace/tdonohue) has joined #duraspace
[13:43] * wild_oscar (~malmeida@webservices.itclinical.com) has joined #duraspace
[13:45] <wild_oscar> tdonohue, mhwood: ping
[13:47] <wild_oscar> hpottinger is not here to ping :P
[13:48] <DSpaceSlackBot> <hpottinger> :P I’m here
[13:56] <wild_oscar> aha! :)
[13:57] <mhwood> Sorry, I had just left for a standup meeting.
[13:58] <wild_oscar> no worries. I just wanted to tell you that the XOAI is ready for release! :D
[13:59] <wild_oscar> I finished updating the README's changelog a few minutes ago
[14:01] <wild_oscar> our team follows semantic versioning, and since we added a new constructor to a class (that adds a feature), this would be a minor upgrade - i.e 4.2.0
[14:22] <DSpaceSlackBot> <hpottinger> OK, so, you now require someone to pull the crank on a 4.2.0 release of XOAI?
[14:28] <DSpaceSlackBot> <hpottinger> I see one open PR on XOAI, I assume that’s fine?
[14:29] <wild_oscar> yeah, I didn't get feedback from the requester, so it stayed opened
[14:30] <wild_oscar> hpottinger - yes, now it's time to set the wheels in motion for the release :)
[14:31] <DSpaceSlackBot> <hpottinger> @tdonohue says it’s the same as this: https://wiki.duraspace.org/display/DSPACE/Release+Procedure#ReleaseProcedure-MakinganOfficialRelease%28e.g.%27dspace-x.y%27or%27dspace-x.y-rc1%27%29
[14:31] <DSpaceSlackBot> <hpottinger> we’ll just see about that…
[14:32] <DSpaceSlackBot> <tdonohue> Good luck, @hpottinger ... and thanks. I'm around today if needed, but I have a busy day ahead as well, so I'll check in off & on
[14:44] <DSpaceSlackBot> <hpottinger> `mvn install` ran fine for a clean checkout of dspace/xoai master branch
[15:04] <wild_oscar> btw, which channel is this connected to on slack? I tried "irc", but doesn't seem to be the same
[15:04] <mhwood> #duraspace
[15:04] <mhwood> Sorry, wrong direction...
[15:05] <DSpaceSlackBot> <mwood> dev-mtg
[15:05] <DSpaceSlackBot> <mmalmeida> aha! :slightly_smiling_face:
[15:05] * kompewter (~kompewter@ has joined #duraspace
[15:07] <DSpaceSlackBot> <hpottinger> ok, `mvn release:prepare -DdryRun=true` returned `[INFO] BUILD SUCCESS`
[15:08] <DSpaceSlackBot> <hpottinger> ready to tag and increment the version….
[15:10] <DSpaceSlackBot> <hpottinger> running `mvn release:prepare -Dresume=false` now….
[15:17] <DSpaceSlackBot> <mmalmeida> fingers crossed :slightly_smiling_face:
[15:18] <DSpaceSlackBot> <hpottinger> `[INFO] BUILD SUCCESS`
[15:18] <DSpaceSlackBot> <hpottinger> now, usually, someone besides me checks the tagging results
[15:21] <DSpaceSlackBot> <hpottinger> checking myself, I see the tag exists, and the pom.xml file looks right
[15:22] <DSpaceSlackBot> <hpottinger> well… it all looks right….
[15:23] <DSpaceSlackBot> <hpottinger> unless I hear an objection, I’m going to run this in about 5 minutes `mvn release:perform`
[15:24] <mhwood> We're releasing 4.2.1?
[15:28] <DSpaceSlackBot> <hpottinger> 4.2.0
[15:29] <DSpaceSlackBot> <hpottinger> I think?
[15:29] <DSpaceSlackBot> <hpottinger> does that count as an objection?
[15:29] <mhwood> At Github the pom says <version>4.2.1-SNAPSHOT</version>
[15:29] <DSpaceSlackBot> <hpottinger> in master? that’s correct, the next snapshot should be 4.2.1
[15:30] <mhwood> Sorry, thought that didn't come until after release:perform.
[15:31] <mhwood> No objections, then.
[15:38] <DSpaceSlackBot> <hpottinger> I’m going by what it says here: https://wiki.duraspace.org/display/DSPACE/Release+Procedure#ReleaseProcedure-VerifyandReleaseStagedArtifactsinSonatype
[15:38] <kompewter> [ Release Procedure - DSpace - DuraSpace Wiki ] - https://wiki.duraspace.org/display/DSPACE/Release+Procedure#ReleaseProcedure-VerifyandReleaseStagedArtifactsinSonatype
[15:39] <DSpaceSlackBot> <hpottinger> whoops, wrong verify step
[15:39] <mhwood> Yup, sorry for the noise.
[15:39] <DSpaceSlackBot> <hpottinger> this one: https://wiki.duraspace.org/display/DSPACE/Release+Procedure#ReleaseProcedure-Whatdosuccessfultaggingresultslooklike?
[15:39] <kompewter> [ Release Procedure - DSpace - DuraSpace Wiki ] - https://wiki.duraspace.org/display/DSPACE/Release+Procedure#ReleaseProcedure-Whatdosuccessfultaggingresultslooklike?
[15:40] <DSpaceSlackBot> <hpottinger> no worries, glad someone else is checking my work :slightly_smiling_face:
[15:40] <DSpaceSlackBot> <hpottinger> OK, running `mvn release:perform`
[15:42] <DSpaceSlackBot> <hpottinger> `[INFO] BUILD FAILURE` argh, wat?
[15:44] <DSpaceSlackBot> <hpottinger> ``` [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project xoai: Failed to deploy artifacts: Could not transfer artifact org.dspace:xoai:pom:4.2.0 from/to sonatype-nexus-staging (https://oss.sonatype.org/service/local/staging/deploy/maven2/): Failed to transfer file: https://oss.sonatype.org/service/local/staging/deploy/maven2/org/dspace/xoai/4
[15:44] <DSpaceSlackBot> 401, ReasonPhrase: Unauthorized. -> [Help 1] ```
[15:44] <DSpaceSlackBot> <hpottinger> sad trombone
[15:45] <DSpaceSlackBot> <mmalmeida> missing credentials to upload to sonatype?
[15:48] <DSpaceSlackBot> <hpottinger> I suspect the transfer of ownership to DSpace may not have included Sonatype
[15:49] <DSpaceSlackBot> <hpottinger> @tdonohue or @mwood might have an idea of how to check that
[15:53] <mhwood> There is an org.dspace:xoai:3.2.10, which suggests that it was done.
[15:53] <DSpaceSlackBot> <tdonohue> @hpottinger : Sonatype should just be checking *your* permissions. Sounds like your Maven settings.xml file isn't setup correctly?
[15:54] <DSpaceSlackBot> <tdonohue> I.e. login info to Sonatype is stored in your Maven setting.xml under the <server> settings
[15:56] <DSpaceSlackBot> <tdonohue> XOAI looks to be using Sonatype's "oss-parent" version 7 (which is rather old): https://github.com/DSpace/xoai/blob/master/pom.xml#L22 I think that likely means you need these settings for Sonatype in your settings.xml: https://wiki.duraspace.org/display/DSPACE/Release+Procedure#ReleaseProcedure-MavensettingstoreleaseDSpace<6
[15:56] <kompewter> [ xoai/pom.xml at master · DSpace/xoai · GitHub ] - https://github.com/DSpace/xoai/blob/master/pom.xml#L22
[15:56] <kompewter> [ Release Procedure - DSpace - DuraSpace Wiki ] - https://wiki.duraspace.org/display/DSPACE/Release+Procedure#ReleaseProcedure-MavensettingstoreleaseDSpace<6
[15:57] <DSpaceSlackBot> <hpottinger> ah, OK, I’m on my macbook air, I’ll move back to my main computer
[15:57] <DSpaceSlackBot> <hpottinger> brb
[16:25] * dyelar1 (~dyelar@ has joined #duraspace
[16:25] * dyelar (~dyelar@biolinux.mrb.ku.edu) Quit (Quit: Leaving.)
[16:25] <DSpaceSlackBot> <hpottinger> OK, I'm back.... and am confused about how to set up a release on a notebook *after* successful tagging on another computer
[16:26] <DSpaceSlackBot> <hpottinger> I'm thinking `mvn release:rollback`
[16:27] <DSpaceSlackBot> <hpottinger> and then deleting the old tag
[16:28] <DSpaceSlackBot> <hpottinger> https://wiki.duraspace.org/display/DSPACE/Release+Procedure#ReleaseProcedure-WhattodoifyougettaggingErrors?
[16:28] <kompewter> [ Release Procedure - DSpace - DuraSpace Wiki ] - https://wiki.duraspace.org/display/DSPACE/Release+Procedure#ReleaseProcedure-WhattodoifyougettaggingErrors?
[16:28] <mhwood> "This requires that the previous release descriptor release.properties is still available in the local working copy."
[16:29] <mhwood> There's some reason you couldn't just copy the appropriate credentials to the Macbook?
[16:29] <DSpaceSlackBot> <hpottinger> I wonder if I can just re-run `mvn release:prepare`
[16:30] <DSpaceSlackBot> <hpottinger> oh, well, there's that, too
[16:30] <DSpaceSlackBot> Action: hpottinger roots around for a USB stick
[16:30] <mhwood> scp is our friend.
[16:31] <DSpaceSlackBot> <hpottinger> I have soooo many USB sticks
[16:31] * dyelar1 (~dyelar@ Quit (Quit: Leaving.)
[16:31] <DSpaceSlackBot> <hpottinger> and I don't want this file "somewhere out there"
[16:31] * dyelar (~dyelar@ has joined #duraspace
[16:40] <DSpaceSlackBot> <hpottinger> ah, that’s better
[16:41] <DSpaceSlackBot> <hpottinger> stuff going over to Sonatype now
[16:42] <DSpaceSlackBot> <hpottinger> `[INFO] BUILD SUCCESS`
[16:44] <DSpaceSlackBot> <hpottinger> hey, @mwood, look at the pink paragraph directly above: https://wiki.duraspace.org/display/DSPACE/Release+Procedure#ReleaseProcedure-VerifyandReleaseStagedArtifactsinSonatype
[16:44] <kompewter> [ Release Procedure - DSpace - DuraSpace Wiki ] - https://wiki.duraspace.org/display/DSPACE/Release+Procedure#ReleaseProcedure-VerifyandReleaseStagedArtifactsinSonatype
[16:47] <mhwood> "Once released, there is no undo option"?
[16:47] <DSpaceSlackBot> <hpottinger> no, sorry, above the pink one
[16:48] <DSpaceSlackBot> <hpottinger> grrr, just search for “If you run into issues, or need to perform the mvn release:perform from a different machine”
[16:49] <mhwood> Cool, someone thought of everything.
[16:49] <DSpaceSlackBot> <hpottinger> mental note for the future, the above scenario is already documented
[16:50] <DSpaceSlackBot> <hpottinger> however, I can now run releases from this tiny macbook air
[16:53] <DSpaceSlackBot> <hpottinger> hmm…. no staging repository, is this still on the new default of “deploy everything, skip staging?”
[16:53] <mhwood> I see two, actually, from you, out of different machines.
[16:55] <DSpaceSlackBot> <hpottinger> I see them now, I had to search for “dspace” and not “xoai”
[16:55] <DSpaceSlackBot> <hpottinger> I suspect the first one (1090) is “incorrect”
[16:57] <DSpaceSlackBot> <hpottinger> I dropped 1090, looking at 1091 now
[17:00] <DSpaceSlackBot> <hpottinger> this looks OK to me….
[17:02] <mhwood> It has JARs and POMs as one would expect.
[17:04] <DSpaceSlackBot> <hpottinger> checksums match
[17:04] <DSpaceSlackBot> <hpottinger> I’m calling this done
[17:04] <mhwood> OK
[17:04] <DSpaceSlackBot> <hpottinger> someday we need to automate this part, because it feels too hand-wavey to me
[17:04] <mhwood> Yes. I started looking at the Nexus REST interface, but got distracted.
[17:05] <DSpaceSlackBot> <hpottinger> that is the way of it
[17:06] <DSpaceSlackBot> <hpottinger> OK, I’ve pressed “release” on xoia 4.2.0, it’ll be about an hour before it gets loaded into Central, go about your business
[17:06] <mhwood> Yay, lunchtime...
[17:32] <DSpaceSlackBot> <tdonohue> Thanks @hpottinger!
[17:47] <DSpaceSlackBot> <mmalmeida> thanks @hpottinger !
[17:48] <DSpaceSlackBot> <hpottinger> I’m clicking refresh on the Maven Central search page
[17:57] <DSpaceSlackBot> <hpottinger> I’ve re-signed up for artifact listener, because I’m tired of hitting refresh :slightly_smiling_face:
[17:58] <DSpaceSlackBot> <hpottinger> https://www.artifact-listener.org/
[17:58] <kompewter> [ artifact listener ] - https://www.artifact-listener.org/
[18:00] <DSpaceSlackBot> <mmalmeida> haha, nice service! didn't know that one
[18:21] * wild_oscar (~malmeida@webservices.itclinical.com) has left #duraspace
[18:32] <DSpaceSlackBot> <hpottinger> looks like “refresh all dang day” beats the free service. 4.2.0 of xoai is in Maven Central: https://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.dspace%22%20AND%20a%3A%22xoai%22
[18:32] <kompewter> [ The Central Repository Search Engine ] - https://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.dspace%22%20AND%20a%3A%22xoai%22
[18:43] <DSpaceSlackBot> <hpottinger> And now we’ve ensured there will be a 6.2
[18:44] <mhwood> Oh?
[18:48] <DSpaceSlackBot> <hpottinger> 4.2.0 of XOAI is out! :slightly_smiling_face: And, yes, recompiling DSpace gets you a version of DSpace with the latest XOAI as a dependency, and that’s how *I* deploy DSpace is via a SNAPSHOT… however…. some people don’t build that way
[18:49] <mhwood> ??? From dspace-oai/pom.xml: <xoai.version>3.2.10</xoai.version>
[18:49] <mhwood> That's from the dspace-6_x branch.
[18:50] <mhwood> Upgrading DSpace to XOAI 4 would be a Good Thing.
[18:51] <DSpaceSlackBot> <hpottinger> now, see… after I typed that above, I went to look at our pom.xml, and you beat me to it
[18:52] <DSpaceSlackBot> <hpottinger> time to super-charge my fork of DSpace
[18:52] <mhwood> I just happened to recall some discussion from several months back, about how the upgrade would take more than just changing the version. Dunno how much more.
[18:53] <DSpaceSlackBot> <hpottinger> cue screeching tire noise
[18:53] <mhwood> DS-2595
[18:53] <kompewter> [ https://jira.duraspace.org/browse/DS-2595 ] - [DS-2595] Upgrade DSpace to use XOAI 4.x - DuraSpace JIRA
[18:56] <DSpaceSlackBot> <tdonohue> Note, IIRC, XOAI 4.x is nearly a complete rewrite. So an upgrade will involve code changes to DSpace's OAI interface
[18:56] <DSpaceSlackBot> <tdonohue> Still would be nice to look into and/or do
[18:57] <mhwood> Yes. IIRC the latest XOAI 3.x exists because DSpace needed some stuff backported from 4.x.
[19:07] <DSpaceSlackBot> <hpottinger> ```[ERROR] Failed to execute goal on project dspace-oai: Could not resolve dependencies for project org.dspace:dspace-oai:war:6.2-SNAPSHOT: Could not find artifact org.dspace:xoai:jar:4.2.0 in central (https://repo.maven.apache.org/maven2)```
[19:07] <DSpaceSlackBot> <hpottinger> ^^^ probably can exclude our way out of that mess
[19:08] <DSpaceSlackBot> <hpottinger> wait…. hmmm…
[19:09] <DSpaceSlackBot> <hpottinger> that error is just Maven Central being weird
[19:09] <mhwood> Yes. search.maven.org finds it.
[19:10] <mhwood> Oh, no, it finds only a POM. I think that that POM just pulls in the other artifacts.
[19:11] <mhwood> So change the dependency to type POM and you'll then see what breaks next.
[19:19] <DSpaceSlackBot> <tdonohue> There is very little code similarity between 3.x and master (4.x). So, I'd venture to guess that a lot of the OAI interface is likely to break after bumping up to 4.x. That said, it's a useful experiment, it just looks like the effort here may be larger, albeit very worthwhile
[19:49] <DSpaceSlackBot> <hpottinger> `mvn -U clean package` was required….
[19:53] <mhwood> Got an adventure ahead: DSpace 1.7.2 -> DSpace 6.1 upgrade.
[19:54] <mhwood> And I shouldn't clutter the logged channel with chit-chat...
[20:27] <DSpaceSlackBot> <hpottinger> oh, yes, doh!
[21:00] * dyelar (~dyelar@ Quit (Quit: Leaving.)
[21:02] * mhwood (~mhwood@mhw.ulib.iupui.edu) Quit (Remote host closed the connection)
[21:45] * tdonohue (~tdonohue@dspace/tdonohue) Quit (Read error: Connection reset by peer)
[22:17] -christel- [Global Notice] We are delighted to announce the first of the keynote speakers for the freenode #live conference taking place in Bristol, UK this October. Please see http://freenode.net/news/opening-keynote for more information, and don't forget to get your tickets and submit a talk! See you in October!

These logs were automatically created by DuraLogBot on irc.freenode.net using the Java IRC LogBot.