Huh, I can't remember the nginx-full conflict but it wasn't nginx (and I think I've tried what you recommended), It was something very trivial, a file in a dependency (not in nginx-full) that had two separate sources (ie. it was part of two packages).
Balázs On 2/18/21 12:32 PM, Justin Sherrill wrote: > I say this without trying it right now but you should be able to > update /usr/dports and build from source. That should get calibre and > its dependencies installed. > > I don't know what the conflict is for nginx-full - the only conflicts > listed in the Makefile are for other versions of nginx, so it's > possible installing something else dragged one of those other versions > in before getting to the nginx-full package? If that's the case, > manually installing nginx-full first may sidestep the dependency > loop. Again, I am proposing what I think will work, not what I've > actually done. > > Package builds produce logs of what has been built and what has not, > and there should be one for this. I don't know where to look for it, > though. > > On Thu, Feb 18, 2021 at 4:48 AM Jávorszky Balázs > <[email protected] <mailto:[email protected]>> wrote: > > Guys, > > I did the upgrade and calibre is gone. This is no longer a > package. If I > reinstall it from /var/cache/pkg/calibre-4.23.0_3.txz it doesn't work > 'cos it requires libicudata.so.67 and the upgrade bumped icu to > version 68. > > The same with nginx-full. This latter didn't work due to a clash, > I used > the base nginx package but I used the > /usr/local/libexec/nginx/ngx_http_fancyindex_module.so file from > nginx-full. Fortunately the latest availabe fancyindex shared object > still works with the newest nginx. > > I kindly ask you to supply these packages too if it's possible. I know > this is mostly volunteer work etc and thank you for your efforts. > Anyway, this is a Big Bad Breaking Change so far for our small company > and family server :) > > Regards and thx in advace. > > Balázs > > On 2/18/21 1:54 AM, Antonio Huete Jiménez wrote: > > > Dear users, > > > > There is a new binary package set available for master and RELEASE. > > > > It's based in FreeBSD Ports as of Sun Jan 17 17:11:20 2021 with > a few > > minor cherry-picks. > > > > You can use the "Bullet-proof (conflict-proof) upgrade technique" as > > described here: > > https://www.dragonflybsd.org/docs/howtos/HowToDPorts/#index4h1 > > > > Users that wish to report issues with specific packages, please > open a > > issue here: https://github.com/DragonFlyBSD/DPorts/issues > > > > Developers that wish to submit fixes, please go here: > > https://github.com/DragonFlyBSD/DeltaPorts/pulls > > > > RELEASE-5.8 > > 29168 packages available > > > > master > > 29196 packages available > > > > NOTES: > > > > The sudo CVE is covered by this update, the version available is > 1.9.5p2. > > > > If you happen to upgrade pkg from 1.14.x to 1.16.x and above, you'll > > get the following error: > > > > pkg: Failed to execute lua script: [string "-- args: > > etc/pkg.conf.sample..."]:12: attempt to call a nil value (field > 'stat') > > pkg: lua script failed > > No active remote repositories configured. > > > > It's a known bug, simply copy the sample mirror config file over: > > > > # cp /usr/local/etc/pkg/repos/df-latest.conf.sample > > /usr/local/etc/pkg/repos/df-latest.conf > > > > > > - The DragonFly BSD team > > >
0xC6991810B203B247.asc
Description: application/pgp-keys
signature.asc
Description: OpenPGP digital signature
