Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 11 Oct 2021 08:05:57 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 259064] www/nextcloud Update to 22.2.0 break cause update loop.
Message-ID:  <bug-259064-7788@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D259064

            Bug ID: 259064
           Summary: www/nextcloud Update to 22.2.0 break cause update
                    loop.
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: brnrd@freebsd.org
          Reporter: monwarez@mailoo.org
          Assignee: brnrd@freebsd.org
             Flags: maintainer-feedback?(brnrd@freebsd.org)

It seems that every time I update nextcloud I get this kind of issue with t=
he
federation, files_trashbin and federatedfilesharing app upgrade.
The occ upgrade will want to update this app every time (if I call occ upgr=
ade
twice it will attempt to update these apps).

Updating <federation> ...
Updated <federation> to 1.12.0
Updating <files_trashbin> ...
Updated <files_trashbin> to 1.12.0
Updating <federatedfilesharing> ...
Updated <federatedfilesharing> to 1.12.0

My question is now why the update to non released version of nextcloud ?
the tags v22.2.0 is not a release, the latest release is v22.1.1 .
And of course since nextcloud prevent downgrading it is a pain to downgrade=
..

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-259064-7788>