pkgsrc-Changes archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: CVS commit: [pkgsrc-2023Q2] pkgsrc/www/php-nextcloud



Hi,

The upstream has no problem at all.

Last some months, I cannot find a time
to update www/php-nextcloud package.
I should update www/php-nextcloud to 26
before pkgsrc-2023Q2 branch.
And I want to include 27 for next pkgsrc-2022Q3 branch.
So pkgsrc-2023Q2 should have 26.

I know that it is bad to update to next major release after branching.
I will find a time and keep the package updated.

Thank you. 

--
Ryo ONODERA // ryo%tetera.org@localhost
PGP fingerprint = 82A2 DC91 76E0 A10A 8ABB  FD1B F404 27FA C7D1 15F3

On Wed, Aug 16, 2023, 05:12 Greg Troxel <gdt%lexort.com@localhost> wrote:
"Benny Siegert" <bsiegert%netbsd.org@localhost> writes:

> Module Name:  pkgsrc
> Committed By: bsiegert
> Date:         Tue Aug 15 18:53:23 UTC 2023
>
> Modified Files:
>       pkgsrc/www/php-nextcloud [pkgsrc-2023Q2]: Makefile PLIST distinfo
>
> Log Message:
> Pullup ticket #6784 - requested by ryoon
> www/php-nextcloud: update to latest,
> required for migrating to version 27 in the next branch

Wow, I am really surprised to go from 25 at branch start to 26
mid-branch to 27 in the next. I know nextcloud has upgrade problems, but
pulling up a major release on a branch is really not expected by branch
users.  I wonder if there was any way to avoid this?   Do upstream
releases come out faster than once a quarter?


Home | Main Index | Thread Index | Old Index