Add notes for 2020-04-26

content/posts/2020-04.md

@@ -240,4 +240,33 @@ dc.contributor.author,cg.creator.id
   - I set it explicitly for Maven and Ant just now (and cleared all XMLUI caches) but the issue is still there
   - I asked them if they are building on macOS or Linux, and which Node.js version (I'm using 10.20.1, which is the current LTS branch).
 
+## 2020-04-25
+
+- I researched a bit more about the  issue with glypicons and realized it's due to [a bug in libsass](https://github.com/twbs/bootstrap-sass/issues/919)
+  - I have Ruby sass version 3.4.25 installed in my local environment, but DSpace Mirage 2 is supposed to build with 3.3.14
+  - Downgrading the version fixes it, though I wonder: why did I not have this issue on the `6.x-dev` branch before Atmire's pull request, and also on `5_x-prod` where I've been building for a few months here...
+- I deployed the latest `5_x-prod` branch on CGSpace (linode18), ran all updates, and rebooted the server
+  - This includes the "COVID19" ILRI subject, the new CCAFS Phase II project tags, and the changes to an ILRI author name
+  - After restarting the server I had to restart Tomcat three times before all Solr statistics cores loaded properly.
+  - After that I started a full Discovery reindexing to pick up some author changes I made last week:
+
+```
+$ export JAVA_OPTS="-Dfile.encoding=UTF-8 -Xmx1024m"
+$ time chrt -i 0 ionice -c2 -n7 nice -n19 dspace index-discovery -b
+```
+
+- I ran the `dspace cleanup -v` process on CGSpace and got an error:
+
+```
+Error: ERROR: update or delete on table "bitstream" violates foreign key constraint "bundle_primary_bitstream_id_fkey" on table "bundle"
+  Detail: Key (bitstream_id)=(184980) is still referenced from table "bundle".
+```
+
+- The solution is, as always:
+
+```
+$ psql -d dspace -U dspace -c 'update bundle set primary_bitstream_id=NULL where primary_bitstream_id in (183996);'
+UPDATE 1
+```
+
 <!-- vim: set sw=2 ts=2: -->