Re: pkg/47418 (pkgin cannot identify upstream version)

[George Georgalis <george%galis.org@localhost>]

The State-Changed-Why open->closed indicates jperkin doesn't
understand this request or the value of it.

It would be _very_ valuable to query the actual source file used by
pkgsrc (url, and revision if it is a repo), vs what is currently in
use on the website.

ie, the change-request is to provide a reporting of the version
configuration USED by pkgsrc.

This has value for research of installed packages as well as packages
considered for installation.

It will address the situation of a known feature or bug (per HOMEPAGE)
and determination if pkgsrc is inclusive.

If a package author is concerned about the package version used, the
package user certainly is. This request is about reporting what WAS
used in pkgsrc.


On Mon, Apr 20, 2020 at 5:30 AM George Georgalis <george%galis.org@localhost> wrote:
>
> The following reply was made to PR pkg/47418; it has been noted by GNATS.
>
> From: George Georgalis <george%galis.org@localhost>
> To: gnats-bugs%netbsd.org@localhost
> Cc: jperkin%netbsd.org@localhost, pkgsrc-bugs%netbsd.org@localhost, gnats-admin%netbsd.org@localhost
> Subject: Re: pkg/47418 (pkgin cannot identify upstream version)
> Date: Mon, 20 Apr 2020 05:29:30 -0700
>
>  --000000000000a9ae8305a3b80df0
>  Content-Type: text/plain; charset="UTF-8"
>
>  The State-Changed-Why open->closed indicates jperkin doesn't understand
>  this request or the value of it.
>
>  It would be _very_ valuable to query the actual source file used by pkgsrc
>  (url, and revision if it is a repo), vs what is currently in use on the
>  website.
>
>  ie, the change-request is to provide a reporting of the version
>  configuration USED by pkgsrc.
>
>  This has value for research of installed packages as well as packages
>  considered for installation.
>
>  It will address the situation of a known feature or bug (per HOMEPAGE) and
>  determination if pkgsrc is inclusive.
>
>
>
>
>
>  On Mon, Apr 20, 2020 at 3:50 AM <jperkin%netbsd.org@localhost> wrote:
>
>  > Synopsis: pkgin cannot identify upstream version
>  >
>  > State-Changed-From-To: open->closed
>  > State-Changed-By: jperkin%NetBSD.org@localhost
>  > State-Changed-When: Mon, 20 Apr 2020 10:50:30 +0000
>  > State-Changed-Why:
>  > The firefox-related parts of this PR were resolved a while back.  As for
>  > the pkgin parts, you can identify the HOMEPAGE of a package using pkgin
>  > with "pkgin pkg-build-defs <pkg> | grep HOMEPAGE", and from that be able
>  > to find the source files, or grep for PKGPATH to find where all the pkgsrc
>  > related files are kept for the package in question.
>  >
>  >
>  >
>  >
>
>  --
>  George Georgalis, (415) 894-2710, http://www.galis.org/
>
>  --000000000000a9ae8305a3b80df0
>  Content-Type: text/html; charset="UTF-8"
>  Content-Transfer-Encoding: quoted-printable
>
>  <div dir=3D"ltr"><div>The State-Changed-Why open-&gt;closed indicates jperk=
>  in doesn&#39;t understand this request or the value of it.</div><div><br></=
>  div><div>It would be _very_ valuable to query the actual source file used b=
>  y pkgsrc (url, and revision if it is a repo), vs what is currently in use o=
>  n the website.</div><div><br></div><div>ie, the change-request is to provid=
>  e a reporting of the version configuration USED by pkgsrc.</div><div><br></=
>  div><div>This has value for research of installed packages as well as packa=
>  ges considered for installation.</div><div><br></div><div>It will address t=
>  he situation of a known feature or bug (per HOMEPAGE) and determination if =
>  pkgsrc is inclusive.<br></div><div><br></div><div><br></div><div><br></div>=
>  <div><br></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=
>  =3D"gmail_attr">On Mon, Apr 20, 2020 at 3:50 AM &lt;<a href=3D"mailto:jperk=
>  in%netbsd.org@localhost">jperkin%netbsd.org@localhost</a>&gt; wrote:<br></div><blockquote class=
>  =3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
>  b(204,204,204);padding-left:1ex">Synopsis: pkgin cannot identify upstream v=
>  ersion<br>
>  <br>
>  State-Changed-From-To: open-&gt;closed<br>
>  State-Changed-By: jperkin%NetBSD.org@localhost<br>
>  State-Changed-When: Mon, 20 Apr 2020 10:50:30 +0000<br>
>  State-Changed-Why:<br>
>  The firefox-related parts of this PR were resolved a while back.=C2=A0 As f=
>  or<br>
>  the pkgin parts, you can identify the HOMEPAGE of a package using pkgin<br>
>  with &quot;pkgin pkg-build-defs &lt;pkg&gt; | grep HOMEPAGE&quot;, and from=
>   that be able<br>
>  to find the source files, or grep for PKGPATH to find where all the pkgsrc<=
>  br>
>  related files are kept for the package in question.<br>
>  <br>
>  <br>
>  <br>
>  </blockquote></div><br clear=3D"all"><br>-- <br><div dir=3D"ltr" class=3D"g=
>  mail_signature">George Georgalis, (415) 894-2710, <a href=3D"http://www.gal=
>  is.org/" target=3D"_blank">http://www.galis.org/</a><br><br></div>
>
>  --000000000000a9ae8305a3b80df0--
>


-- 
George Georgalis, (415) 894-2710, http://www.galis.org/