Closed ericgaspar closed 10 months ago
!testme
!testme
@zamentur still no luke with updating from version 25
@zamentur still no luke with updating from version 25
I just see that, it's due to the remove of ynh_install_app_dependencies $pkg_dependencies
(refactoring v2) , i try to code something this morning.
The new apt ressources packaging format does not make it easy to update dependencies iteratively :/
!testme
!testme
!testme
the test seems to be stuck...
!testme
!testme
!testme
!testme
!testme
@zamentur following #632, we could also update https://github.com/YunoHost-Apps/nextcloud_ynh/blob/0e79a6449d0ddf80f464b03b566ed97db6000556/scripts/change_url#L36
Just a small note: The English in this commit is a bit odd. The more common way of saying it would be: "Note that if you've installed any third-party Nextcloud applications, they have probably been disabled. If so, you'll need to manually enable them again."
Note that a patch failure doesn't currently means the setup source failed, see: https://github.com/YunoHost/issues/issues/2296
!testme
This last commit fix https://github.com/YunoHost-Apps/nextcloud_ynh/issues/617
!testme
!testme
!testme
!testme
!testme
!testme
What's missing to merge this ?
Upgrade from v25 is not working, because it tries to upgrade straight away or does it goes by any intermediate version (as in end users servers ) ?
What's missing to merge this ?
hmmm courage i think because this is like the biggest change in the most used app so uuuuh .. maybe we can "vote" so that it's a collective decision or something :sweat_smile:
I don't mind pressing the green button 😁 (but I don't understand the change url test failing)
(but I don't understand the change url test failing)
Yeah, me neither. Not sure if it's a real issue or a CI issue. Also it's not a blocking change as long as it don't break the app nor a backup restoration. But I haven't tested it...
hmmm courage i think because this is like the biggest change in the most used app so uuuuh ..
Yeah in my opinion it's way too much change in one single PR... I would have split at least the major version upgrade, packaging V2 and other minors changes :sweat_smile:
That's said, I upgraded 3 servers with nothing to report for now, so I'm in favor of merging.
nothing is preventing us to do a version upgrade first...
Right now it's a lot to handle to make another PR with just the version upgrade + the minor fixes that are important anyway, don't you think so ? :sweat_smile: I mean now that the work is done, let's not do it twice.
And apart from the change_url issue, in my case 3 upgrade (on x86 and ARM) worked fine, so I'm quite confident for this one.
!testme
596
623
578
628
541
632
641
642