Date: Sat, 16 Sep 2017 18:51:10 -0500 From: Adam Vande More <amvandemore@gmail.com> To: Scott Ballantyne <sdb@ssr.com> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: Curious pkg upgrade behavior Message-ID: <CA%2BtpaK1KeZznLgSG0BKQ7BAieyK%2BAnu4RFzvbb15efBwS-_WYA@mail.gmail.com> In-Reply-To: <20170916152354.2192.qmail@irelay.ssr.com> References: <20170916121755.1297.qmail@irelay.ssr.com> <CA%2BtpaK0_Ev%2B7su-Hiu4jnCF1ec2sHknkzudTQ_%2BbcFvQj_tnpw@mail.gmail.com> <20170916152354.2192.qmail@irelay.ssr.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Sep 16, 2017 at 10:23 AM, Scott Ballantyne <sdb@ssr.com> wrote: > Yes, messages is where I first noticed it hadn't upgraded. I was running > samba43 prior to this. The second run of pkg uninstaled Samba > 43-4.3.11 and installed samba44-4.4.15. It also upgraded gvfs. The > reason I mention samba3.6 is because that's the only place that bug > seems to have occurred, it never showed up here untiltoday. > > I'm sure there's a reasonable explanation, I just have no idea what it > is. > Hard telling without you sharing the relevant output from pkg. If you can recreate it in a clean VM you can file a bug on it. -- Adam
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BtpaK1KeZznLgSG0BKQ7BAieyK%2BAnu4RFzvbb15efBwS-_WYA>