Re: Building a custom rpm from the source tarball, post 3.0

[Jeff Morriss <jeff.morriss.ws () gmail com>]

Known bug but I thought it was still unfixed:

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15167

Haven't checked in a while...

On Thu, May 16, 2019 at 3:18 AM Dario Lombardo <lomato () gmail com> wrote:

> If I'm not mistaken, that's a known bug. It should be fixed by
>
> https://code.wireshark.org/review/c/33214/
>
>
> On Wed, May 15, 2019 at 11:12 PM Maynard, Chris <
> Christopher.Maynard () igt com> wrote:
>
> > In the old days prior to Wireshark 3.0, one could visit
> > *https://www.wireshark.org/download/src/all-versions/*
> > <https://www.wireshark.org/download/src/all-versions/>, download the
> > source tarball of interest (e.g., wireshark-2.6.6.tar.xz), extract it,
> > modify it as necessary and build both a custom Windows installer and a
> > custom RHEL7 rpm.
> >
> > Beginning with Wireshark 3.0 though, it no longer seems possible to
> > create a customized rpm from the source tarball as before.  Is this so, or
> > am I missing something?
> >
> > fatal: Not a git repository (or any parent up to mount point /home)
> > Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
> >
> > If it is the case, then why is that?  Would it be possible for the
> > project to restore the ability to build rpm’s from the source tarball like
> > it was possible to do prior to Wireshark 3.0?
> >
> > Thanks.
> > - Chris
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe