pkg 1.3.X changed behaviour with pkg -fR xxx

[Kevin Oberman]

On Wed, Jul 30, 2014 at 1:16 AM, Michael Gmelin <grembo at freebsd.org> wrote:

>
>
> > On 30 Jul 2014, at 08:58, Kevin Oberman <rkoberman at gmail.com> wrote:
> >
> > On Tue, Jul 29, 2014 at 10:47 PM, Baptiste Daroussin <bapt at freebsd.org>
> > wrote:
> >
> >>> On Tue, Jul 29, 2014 at 08:45:32PM -0300, sergio lenzi wrote:
> >>> see the sequence of commands
> >>>
> >>> pkg info -qr db6
> >>> results....
> >>>    redland-1.0.17_3
> >>>    serf-1.3.6_1
> >>>    subversion-1.8.9_7
> >>>    apr-1.5.1.1.5.3_3
> >>>    squidGuard-1.4_9
> >>>    cyrus-sasl-saslauthd-2.1.26_1
> >>>    evolution-data-server-2.32.1_11
> >>>    bogofilter-1.2.4_2
> >>> =============================
> >>> Now the command....
> >>>
> >>> pkg install -fR db6
> >>>
> >>>
> >>>
> >>> Updating repository catalogue
> >>> DIST64 repository is up-to-date
> >>> All repositories are up-to-date
> >>> Checking integrity... done (0 conflicting)
> >>> The following 1 packages will be affected (of 1037 checked):
> >>>
> >>> Installed packages to be REINSTALLED:
> >>>      db6-6.1.19 (forced reinstall)
> >>> ===========================
> >>> look that it will reinstall db6 (which is correct)
> >>> but not will reinstall the other packages as the manual says so...
> >>>
> >>> Another missing thing is that pkg upgrade
> >>> will not reinstall the packages that changed options or
> >>> that changed direct dependencies (as pkg 1.2.X did)...
> >>>
> >>> Is it normal or a bug??
> >> This is a bug can you open a ticket on github?
> >>
> >> regards,
> >> Bapt
> >
> > Wouldn't the FreeBSD bugzilla be a better place?
>
> Pkg is developed using git and hosted on GitHub. Its issue tracker hooks
> into the repository quite nicely, so it actually makes a lot of sense to
> file it there.
>
> https://github.com/freebsd/pkg/issues/new
>

While I understand that, it is disturbing to see a very important part of
FreeBSD not using the FreeBSD bug tracking system. If I have a problem with
FreeBSD and want to see if there is a trouble report, I am not going to
look at github (or any external tracker). I'm going to look at the FreeBSD
Bugzilla and I feel it is improper to have an official FreeBSD project
recommending issues be sent to any external bug tracker in lieu of the
official one..

Simply put, I think it is a terrible idea and should be squashed
immediately.
--
R. Kevin Oberman, Network Engineer, Retired
E-mail: rkoberman at gmail.com