[Bug 285253] devel/dbus: upgrade without bumping dependent ports breaks ... everything

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=285253

--- Comment #9 from Gleb Popov <arrowd@FreeBSD.org> ---
(In reply to Martin Birgmeier from comment #8)
> What exactly broke: I restarted the system (where only dbus had been upgrade using pkg upgrade from my local repo), and then basically nothing worked anymore.

This is still an unclear description. Did you try running a broken app from a
terminal to see its stderr? What DE or WM are you using? If you're using
something heavyweight and managed to get to the point when you're running
Firefox, then there is actually a lot of stuff that is working.

> Do the remarks in comment #2 mean that packages of exactly the same name may still be different because they would be recompiled in poudriere, published to the package site, and pkg would then do a reinstall because it detects the changed libraries?

Yup, exactly.

> Of course it is nice not to have to do a portrevision bump for such things, but that packages of the same name can still be different is something I must get used to.

Well, shared libs is not the only problem there. Depending on a software it may
or may not be possible to get the same package from two builds in the same env.
A simple example - the software hardcodes the compilation date and time in its
source. This only will make a build non-reproducible and every time there would
be a different package.

Fortunately, we don't have to reinstall the package each time it changes in the
repository. pkg knows well when it really has to be reinstalled. But when using
build-on-host tools you're actually bypassing this logic, because in this
scenario pkg is used only to register the final package after the build
finishes.

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