How to update a TYPO3 extension with composer? - typo3

How do I update a specific extension (and only this extension) in composer mode?

To update an extension you only need this command:
composer update <vendor/package>
If you want to update all dependencies in this extension as well, add the option --with-all-dependencies:
composer update <vendor/package> --with-all-dependencies
or in short form
composer update <vendor/package> -W
If you need to perform a major update which cannot be handled with the given version in the composer.json, you can use this command:
composer require <vendor/package>:"^versionString"
Notice that you should not use composer update without a package name since this updates all packages at once. If something is broken after such an update, you will need to revert the whole update. Also Git bisect is impossible to find the specific package update which broke.

Related

Can't Bulk Install Modules in DNN 9.10.2

With newer versions of DNN, they excluded the Bulk Install files used to bulk install modules.
We used to copy the following files in the install folder on newer versions to make it work.
When I navigate the following URL, I get an Exception: dnndev.me/install/install.aspx?mode=installresources
Exception:
It looks like a missing definition in a DLL.
How can I fix this?
Upgrade.Upgrade.CheckUpgrade() is no longer exist on latest version of DNN.
Check the history related to it
Don't just paste your old code, there's a couple update at DNN Install.aspx.cs file.
You'll need to make adjustment to it.

Installing Bit Bake Append'ed Packages with DNF cleanly

It is common practice to customize a Yocto made package with an Bit Bake append file _%.bbappend. The problem I am having is even though the package contents have been modified due to the append file, the package keeps the same version number. This is troublesome because dnf install will not install the RPM because it does not think it is an upgrade and a dnf remove before would trigger dependent packages to also be removed. There are ways around this modifying DNF configs, but I get nervous automating those changes in utilities due to the chance of really nasty error states.
Assuming the original package is installed, is there any way to modify the Bit Bake append file so that dnf will install the result like an updated package?
The solution to this is to use the PR service:
https://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html#working-with-a-pr-service
I believe you want to set (and increment as you update) the PR variable as follows:
PR = "r1"
See: https://www.yoctoproject.org/docs/2.5/mega-manual/mega-manual.html#var-PR

intermediate update step in own builded RPM

If I build my own RPMs, is there a way, to tell that before upgrade to the latest version, upgrade to a specific other version first?
So for example I often made a mistake in my postun actions, that I delete a link. So when I want to update to an newer package that fixes my postun action, the usually RPM behavior is that my new packages will be installed, then the old package will be uninstalled and trigger my mistake in the postun action. So I would need to run a reinstall then or to update again to an even later version, that on the next update, my postun action is correct.
So I would imaging something like
UpdateRequires: MyPackage >= 1.1
There is no way to force an update chain like that. You could have the user reinstall the new package. Another option is to fix the symlinks in your %verify stanza and tell the user to run rpm -V on your RPMs.
It is possible to run a step after old packages %postun with %posttrans in new package

How can I remove crouton targets?

I have installed multiple targets to test them all and now I would like to remove some that are not working well with xenial. There's no information on the crouton github wiki on how to remove targets, only how to install and update them. What command should I use to remove targets?
Should I just edit the file /etc/crouton/targets within my chroot and then remove packages like kde?
Thanks!
There is no builtin way to do this - just as you said remove it from the /etc/crouton/targets and then you have to manually delete the packages themselves. To do this you should do just:
sudo apt-get remove <comma,sep,list,packages>
(or apt-get purge) It means you need to know these though.

I Can't install Laravel 4's package

I just started learn Laravel 4, i have problem when install laravel's package, in this case it is: http://packalyst.com/packages/package/greggilbert/recaptcha
I do all steps, but it always display: Class 'Greggilbert\Recaptcha\RecaptchaServiceProvider' not found
I think problem is i don't know where to put recaptcha-master.zip, root folder? or in Vendor folder? i don't know :(
Please help, thank you so much :(
First you need to add "greggilbert/recaptcha": "dev-master" to the require section of your composer.json file found in the Laravel root.
Once thats done you then need to install composer globally or download a copy of composer.phar and move it to your Laravel root.
Once either of those methods have been completed, you then need to run either composer update if you installed composer globally or php composer.phar update in order to install the new packages.
After, and only after composer has updated with the new dependencies you should then add the service providers and other configurations to Laravel.
Heres a link to the composer site. http://getcomposer.org/