-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug: updater does not update the vendor packages #8642
Comments
I see where the problem might be. The script indeed does not sync the vendor folder if One problem is that since 1.4.0 the release packages include I'm not sure there is an easy fix. Maybe we should just require composer to upgrade Roundcube. Then we should probably bump version of our dependencies to the required value in composer.json and run @thomascube, any ideas? ps. a workaround for everyone not using composer and want to upgrade, remove |
If roundcube requires any higher version of a vendor package, i would update that in any way - IMO it makes no sense to update roundcube and not the required vendor package - because then it is for sure broken (like it was on my installation). |
We had the same We moved So indeed it seems
but since we never used |
Same issue here. On four servers, upgrade from roundcube 1.5.2 to 1.6 failed spectacularly with a very broken vendor. Eventually I had to perform a clean install on all four servers. I'm waiting for a fix before upgrading more servers... 😋 |
that's why package managers where invited, install.sh is so microsoft that it hurts! [builduser@buildserver:/rpmbuild/SPECS]$ cat roundcubemail.spec Name: roundcubemail %description %prep %build %install %post replace default des string in config file for better securityfunction makedesstr %files |
You know there has been 1.5 and 1.6 since then, right? |
irrelevant as it's still supported and you can bet that rpm-spec dating back to 2009 had built lower versions over the years - you just edit the version matching your tarball and enter "rpmbuild -bb roundcubemail.spec" - you response is pretty dumb when my point was using installer scripts on Linux is nonsense |
as long as one uses a rpm based distro. whats with .deb? whats with .xyz? i see your point, but before i start with a distribution specific package, i would go the most compatible way. and then .sh makes sense. |
boy with the spec-file i showed how to build a package at your own and didn't ask anybody to do it for me or someone else- the point of a package is that it removes leftovers and keep the system clean, i have mine - if can't package a software proper i don't install it |
"boy"? not sure what you want to achieve with that tone, but i am sure you wont get it. if you want to make a PR, do it. otherwise, it would be nice to stop trolling this thread with off-topic stuff. if you have the urge to create a new bug ticket, do it. |
i don't want to achieve ANYTHING - i only pointed out that nobody should use such scripts but package every software he uses and is not packaged in the distribution as i do it since 2008 - personally i couldn't care less and i saw the topic on the mailing-list |
Applying versions from |
Please don't make composer a requirement. In many enterprise environments composer is prohibited, as is in my case. I'm using the complete archive of roundcube, so I would prefer to just copy the new vendor directory over the old one. |
@alecpl What about adding a comment to |
* installto.sh checks for a marker indicating that composer was not run/used. * update.sh tries to find and run composer
1.6.7-complete installto.sh still has this issue. |
because of some unrelated comments in #8639 i'm going to create this bug report.
steps to reproduce:
expected:
the vendor packages should be updated too (e.g. net_smtp from 1.7 to 1.10)
actual behaviour:
it does not update these files
additional information:
i have a quiet restricted system, so maybe its an permission problem, but then i would expect an error that these files could not be overwritten
The text was updated successfully, but these errors were encountered: