From: Paul Hoffman on
Greetings again. A few years ago, I proposed editors/emacs-nox11 and submitted a patch to create it, and thus became listed in the comments at the beginning of the Makefile (but I am not the package maintainer, I believe). Today I got a report that the package does not build; I verified this. I want to help the user, but I have no idea how the change that broke the build was added to the Makefile.

How do I find the history so I can find out who added the problematic line and figure out what they actually meant?

--Paul Hoffman
_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

From: Julien Laffaye on
Hello,

On Sun, May 23, 2010 at 4:46 PM, Paul Hoffman <phoffman(a)proper.com> wrote:
> Greetings again. A few years ago, I proposed editors/emacs-nox11 and submitted a patch to create it, and thus became listed in the comments at the beginning of the Makefile (but I am not the package maintainer, I believe). Today I got a report that the package does not build; I verified this. I want to help the user, but I have no idea how the change that broke the build was added to the Makefile.
>
> How do I find the history so I can find out who added the problematic line and figure out what they actually meant?

You can find the CVS history via :
- cvsweb at http://www.freebsd.org/cgi/cvsweb.cgi/ports/editors/emacs-nox11/Makefile
- freshports at http://www.freshports.org/editors/emacs-nox11/

Regards,
Julien
_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

From: Yuri Pankov on
On Sun, May 23, 2010 at 04:46:46PM -0700, Paul Hoffman wrote:
> Greetings again. A few years ago, I proposed editors/emacs-nox11 and submitted a patch to create it, and thus became listed in the comments at the beginning of the Makefile (but I am not the package maintainer, I believe). Today I got a report that the package does not build; I verified this. I want to help the user, but I have no idea how the change that broke the build was added to the Makefile.
>
> How do I find the history so I can find out who added the problematic line and figure out what they actually meant?
>
> --Paul Hoffman

cvs -d anoncvs(a)anoncvs1.FreeBSD.org:/home/ncvs rlog ports/editors/emacs-nox11
or
http://www.freebsd.org/cgi/cvsweb.cgi/ports/editors/emacs-nox11/


HTH,
Yuri
_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

From: Charlie Kester on
On Sun 23 May 2010 at 17:05:04 PDT Julien Laffaye wrote:
>Hello,
>
>On Sun, May 23, 2010 at 4:46 PM, Paul Hoffman <phoffman(a)proper.com> wrote:
>> Greetings again. A few years ago, I proposed editors/emacs-nox11 and submitted a patch to create it, and thus became listed in the comments at the beginning of the Makefile (but I am not the package maintainer, I believe). Today I got a report that the package does not build; I verified this. I want to help the user, but I have no idea how the change that broke the build was added to the Makefile.
>>
>> How do I find the history so I can find out who added the problematic line and figure out what they actually meant?
>
>You can find the CVS history via :
>- cvsweb at http://www.freebsd.org/cgi/cvsweb.cgi/ports/editors/emacs-nox11/Makefile
>- freshports at http://www.freshports.org/editors/emacs-nox11/

Another thing that is sometimes useful is to query the GNATS database
for closed PR's related to the port. For example:

http://www.freebsd.org/cgi/query-pr-summary.cgi?category=&severity=&priority=&class=&state=&sort=none&text=emacs-nox11&responsible=&multitext=&originator=&closedtoo=on&release=

Interestingly, the only thing this turns up for emacs-nox11 is the
original PR that created the port -- which means any subsequent changes
were probably the result of some comprehensive updates each of which
affected several ports in one swoop.

Or that the people submitting the PR's didn't follow the accepted
practice of including category & portname in the subject line. ;)
_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

From: Matthew Seaman on
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 24/05/2010 02:07:24, Charlie Kester wrote:
> On Sun 23 May 2010 at 17:05:04 PDT Julien Laffaye wrote:
>> Hello,
>>
>> On Sun, May 23, 2010 at 4:46 PM, Paul Hoffman <phoffman(a)proper.com>
>> wrote:
>>> Greetings again. A few years ago, I proposed editors/emacs-nox11 and
>>> submitted a patch to create it, and thus became listed in the
>>> comments at the beginning of the Makefile (but I am not the package
>>> maintainer, I believe). Today I got a report that the package does
>>> not build; I verified this. I want to help the user, but I have no
>>> idea how the change that broke the build was added to the Makefile.
>>>
>>> How do I find the history so I can find out who added the problematic
>>> line and figure out what they actually meant?
>>
>> You can find the CVS history via :
>> - cvsweb at
>> http://www.freebsd.org/cgi/cvsweb.cgi/ports/editors/emacs-nox11/Makefile
>> - freshports at http://www.freshports.org/editors/emacs-nox11/
>
> Another thing that is sometimes useful is to query the GNATS database
> for closed PR's related to the port. For example:
>
> http://www.freebsd.org/cgi/query-pr-summary.cgi?category=&severity=&priority=&class=&state=&sort=none&text=emacs-nox11&responsible=&multitext=&originator=&closedtoo=on&release=
>
>
> Interestingly, the only thing this turns up for emacs-nox11 is the
> original PR that created the port -- which means any subsequent changes
> were probably the result of some comprehensive updates each of which
> affected several ports in one swoop.
> Or that the people submitting the PR's didn't follow the accepted
> practice of including category & portname in the subject line. ;)

In this case, it's different. editors/emacs-nox11 is a slave port of
editors/emacs and I think you'll find quite a lot of PRs and CVS history
to do with editors/emacs.

I believe the problem the OP mentioned has been analyzed and a fix will
be committed shortly.

See the thread beginning here:

http://lists.freebsd.org/pipermail/cvs-ports/2010-May/195149.html

Cheers,

Matthew

- --
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
Kent, CT11 9PW
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.14 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkv6GREACgkQ8Mjk52CukIwMCACfZHzNMzBWZNa+3f0DVLTtptJ5
TWEAnR7KA6WJ2MKysIPiFNCukRajUqIt
=67KM
-----END PGP SIGNATURE-----
_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"