Failed OpenHAB 3.2 to 3.4 update, yes I read UPDATING

msplsh

msplsh

(and it STILL didn't work until I poked it harder)

Since pkg doesn't alert you that what you asked it to do is covered by an entry in UPDATING (WHICH IT SHOULD, IMO), I just updated OpenHAB and had to figure out that it wasn't working (Silent failure! Fun!) before manually restarting it with service and watching it go

Code: 
Could not resolve mvn:org.eclipse.platform/org.eclipse.osgi/3.16.300

I then found a log in /var/db/openhab/userdata/cache that says it's trying to access the wrong version of a JAR.

I did the stupid easy thing and just ripped the correct JAR off mvnrepository's website and stuffed it in the right place and it worked. Then, when I went to check if the port was all messed up (because having to do this seemed kind of dumb) by looking on FreshPorts, I saw the little UPDATING notice. Very helpful! Would be nice if pkg did that!

So, I backed out the file I put in and then ran the sed command as advised. It didn't work.

Looking closer, the entry is from 2021. Poking into /usr/local/libexec/openhab/runtime/system/org/eclipse/platform/org.eclipse.osgi shows that apparently the port has been updated since then, the library version has increased, therefore the command is outdated and the regex won't match.

I didn't care for trying to modify a sed command so I just edited the file manually and pointed it to the correct place. When I updated earlier, pkg helpfully said "You may need to manually remove /var/db/openhab/userdata/etc/config.properties if it is no longer needed." Right, that's what needed to happen ...

All of this is to say this is complete nonsense people shouldn't have to go through and I'm posting it here for anyone who has the same problem. If FreeBSD is going to keep junk in UPDATING, then pkg should spit it out! (Maybe even require you to y/N that you read it before updating) If a port is going to have an UPDATING entry, it should keep it updated! If a port is going to require you to manually update something every time, why not a postflight script!? At least then, as a part of the port, it stands a chance to get seen and updated correctly.
 
So, the pkg could literally take the list of things it's going to update, feed it back into itself to get those messages, which would take very minimal effort, and... it doesn't do it. Amazing.
 
If there's no correct message in UPDATING then showing an old one wouldn't be very helpful. I was looking for some previous messages, as there's been several updates between 3.2.0 and 3.4.3. I figured maybe one of the intermediate updates may have had something in their pkg-message. But none of them seem to mention anything.

 
You must log in or register to reply here.
Back
Top