phpBB fails after upgrade from MariaDB5 to MariaDB10 - Custom Synology package - mariadb

My phpBB installation on Synology DSM 6.1 (latest version) fails after the upgrade from MariaDB5 to MariaDB10. I've already put a detailed failure description here: https://www.phpbb.com/community/viewtopic.php?f=556&t=2441286
I now tried to modify the official Synology package from https://archive.synology.com/download/Package/spk/phpBB/ according to the description on this site: https://amigotechnotes.wordpress.com/2014/05/17/how-to-create-a-spk-for-synology-dsm-to-distribute-your-lamp/
Actually, it didn't work...
I'm getting a "Package is invalid" or something like that in the Synology Package Station when installing from the generated SPK file.
Can anyone look at the repository https://github.com/SeppPenner/PhpBBFixMariaDB5Issue and check where the issue exactly is?

I finally found a solution: https://www.phpbb.com/community/viewtopic.php?f=556&t=2441286&p=14906311#p14906311
Install both database versions (MariaDB 5 and 10).
Import the whole mysql dump from before.
Add the same users (root) to both database versions.
Install phpBB on Synology package center with the passwords and a user for phpBB with some password.
I got an error: Database already exists" --> Dropped database for phpBB in MariaDB10.
Install was successful.
Uninstalled MariaDB5.
The board works again but posting is not possible. (There are some forum posts on this issue already and I will try to find a solution for this, too.)

Related

remotes::install_bitbucket() stopped working

For many months now, I've been using remotes::install_bitbucket() from a Docker container to download a private Bitbucket repo and install an R package. March 10, it seems to have stopped working with the error:
Error : Failed to install 'unknown package' from Bitbucket:
cannot open URL 'https://api.bitbucket.org/2.0/repositories/myRepoUsername/myRepo/src/HEAD/DESCRIPTION'
remotes version is 2.3.0
I have not changed the Docker image, so remotes and everything else unchanged
This fails from my local machine with the same error message March 11 (also v2.3.0)
Bitbucket's website shows me my package is still there with no new commits
Does anyone know if this is a temporary problem, a Bitbucket API change, or something else?
All help is appreciated! :)
I'm not sure it is related - but around that time Bitbucket changed their Authentication to use an Application Password instead of your usual password. You could try setting one up in your bitbucket account and using that to test if it works?

How to silently update R for Windows installation

I am aware how to silently install 'R for Windows', but how could I update an existing installation silently to a new version?
Install switches I am currently using:
\\foo\R\R_4.0.5\R-4.0.5-win.exe /VERYSILENT /SUPPRESSMSGBOXES /NORESTART /ALLUSERS /LANGUAGE=en /COMPONENTS="main, x64, translations" /DIR="C:\Program Files\R"
For me, it seems like there is no supported update/upgrade switch. Just installing a new version over an existing one results in just having 2 versions listed in appwiz.cpl.
Forcing the same install dir is not helping either, as you still end up with 2 installations, just in the same folder.
Any hint is appreciated. Thanks in advance.
UPDATE:
I am trying to keep the installations on several machines aligned - therefor it would be helpful to update all machine installations periodically to the latest version and ensure the software inventory solution is not reporting N versions on a single machine.
R is designed so that you can have multiple versions installed simultaneously. This is why each version installs into a different directory.
The canonical way to handle this is to check a registry key for the latest installed version, but if you want to avoid messing with the registry, you can try this:
Install into a custom directory
When it comes to upgrading, move that directory to a temporary location
Install the newer version into the original location
If it works, delete the temp location
If it doesn't, delete the failed install and restore the original
Caveat: untested.

How to install Vega plugin for Kibana 5.5.0?

I am just starting using Kibana (5.5.0). I found a nice plugin called Vega. After spending several hours unsuccessfully trying to install this plugin, I decided to publish here this question.
For example, when I run this command bin/kibana-plugin install file:///ust/test/kibana-vega-vis-master.zip, I get this error:
Attempting to transfer from file:///usr/test/kibana-vega-vis-master.zip
Transferring 25554 bytes....................
Transfer complete
Retrieving metadata from plugin archive
Plugin installation was unsuccessful due to error "No kibana plugins found in archive"
I think you are installing the wrong file. From the releases page, right click the vega_vis-5.5.0-(latest version).zip, use "copy link address", and use that URL with bin/kibana-plugin install https://....
For example, for the current version as of this writing, for Kibana 5.5.0, you would install it with:
bin/kibana-plugin install https://github.com/nyurik/kibana-vega-vis/releases/download/v0.2.3/vega_vis-0.2.3--for-Kibana-5.5.0.zip

WP 4.x + Jetpack Installation Error: HTTP_RAW_POST_DATA

When installing jetpack from the auto install screen, I wasn't able to get it working to an internal 500 error related to this PHP setting.
HTTP_RAW_POST_DATA
After a while trying different configurations with no luck, I decided to extract the zip and install manually and it installed correctly with no problems so far.

Error while moving Drupal moving error

I was trying to move my Drupal site from my WAMP server to another computer's WAMP server and I followed all the necessary steps but I faced the error below. I tried updating but it didn't work.
Fatal error: Call to undefined function cache_get() in C:\wamp\www\try\includes\bootstrap.inc on line 901
I am using PostgreSQL and PhpPgAdmin. Any ideas?
See if Memcache is used in previous server.
If not see if some other cacheing mechanism like varnish cache is used
If none of the above:
When you type drush in the command line probably you reached the right place to solve you problem. This error arises when drush is not update and this occurs when you install drush from official repository in Ubuntu. The workaround is easy: just install a new version of drush! And to do so, you have to install from backported package of Ubuntu.

Resources