Re: Removing "$Id$" lines

[Mojca Miklavec]

On 2 November 2016 at 05:07, David Evans wrote:
>
> Another reason for not canceling such a build would be to generate a record 
> of how many ports and which ones are
> currently broken.  I suspect there are a number that never get reported 
> because they are old or obscure or just not used
> very much.

A reason for not doing this (= not not cancelling) might be a total
crash of our build infrastructure that won't serve anyone anyway.

We should at least:

- switch to PostgreSQL

- implement "successcache", so that ports with existing binary
archives won't even be added to the portbuilder

- implement a way to trigger rebuild of all ports without having to
create artificial commits (I can imagine an additional variable on the
buildbot interface or a "meta port name" like the port variable being
set to "list:all" or "category:python" or "dir:perl" or
"dependon:libcurl")

- (useful, but irrelevant for this particular case) implement merging
of commits to a single job on portwatcher

- test this on a single build slave, ideally on one that's least used
(perhaps on 10.8; but certainly not on the ultra slow 10.5 PPC)

and only scale things once we think we are ready for a mass build.
Mass builds were already problematic on the old infrastructure, but
the new infrastructure is even less efficient and way more resource
hungry.

Mojca
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Removing "$Id$" lines

[David Evans]

On 11/1/16 4:06 PM, Ryan Schmidt wrote:
> Off list, Larry likened removing $Id$ lines to adding modelines, which we 
> also haven't globally done to all Portfiles yet. But it's not really the same 
> thing. Adding modelines needs to be done on a case by case basis. For 
> example, if a Portfile currently uses tabs, then just adding the modeline 
> that states spaces are used would be inaccurate. The person adding the 
> modeline should also be converting the tabs to spaces at the same time.
> 
> Removing the $Id$ line, by contrast, requires no other actions. I have no 
> objection to removing them all at once, and agree that if we make sure the 
> buildbot is already busy with some time consuming builds at the time that we 
> push that change, we can cancel the applicable portwatcher build before it 
> gets around to scheduling the tens of thousands of portbuilder builds.
> 
> On the other hand, we do want to eventually build all ports on all builders, 
> both to build ports on the new builders that have never been built before, 
> and to catch up on some builds on the existing builders that may have been 
> missed; committing the change to remove the $Id$ line would be one way to 
> accomplish that. But to ensure that doesn't take longer than it needs to, I 
> want to switch from SQLite to PostgreSQL, and implement the successcache, 
> before doing that.
> 
> Removing the $Id$ lines is not critical. There are other time-critical 
> matters of migrating off of macOS forge that still need to be accomplished in 
> the next two weeks that we should focus on instead.
> 
> In the mean time, feel free to remove the $Id$ lines from your ports as you 
> update them, or do nothing with the $Id$ lines until we've figured out what 
> to do.
> 

Although it's not a big deal, the current stable version of MacPorts will give 
a lint error if the $Id$ line is removed
but the version in git master has been already fixed to give an error if it 
exists.  So perhaps a logical point for
doing a mass replace is when 2.3.5 is released.  From recemt activity, I assume 
that's not too far down the line but far
enough to allow for the appropriate preparations.

Another reason for not canceling such a build would be to generate a record of 
how many ports and which ones are
currently broken.  I suspect there are a number that never get reported because 
they are old or obscure or just not used
very much.

Dave

___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Removing "$Id$" lines

[Ryan Schmidt]

Off list, Larry likened removing $Id$ lines to adding modelines, which we also 
haven't globally done to all Portfiles yet. But it's not really the same thing. 
Adding modelines needs to be done on a case by case basis. For example, if a 
Portfile currently uses tabs, then just adding the modeline that states spaces 
are used would be inaccurate. The person adding the modeline should also be 
converting the tabs to spaces at the same time.

Removing the $Id$ line, by contrast, requires no other actions. I have no 
objection to removing them all at once, and agree that if we make sure the 
buildbot is already busy with some time consuming builds at the time that we 
push that change, we can cancel the applicable portwatcher build before it gets 
around to scheduling the tens of thousands of portbuilder builds.

On the other hand, we do want to eventually build all ports on all builders, 
both to build ports on the new builders that have never been built before, and 
to catch up on some builds on the existing builders that may have been missed; 
committing the change to remove the $Id$ line would be one way to accomplish 
that. But to ensure that doesn't take longer than it needs to, I want to switch 
from SQLite to PostgreSQL, and implement the successcache, before doing that.

Removing the $Id$ lines is not critical. There are other time-critical matters 
of migrating off of macOS forge that still need to be accomplished in the next 
two weeks that we should focus on instead.

In the mean time, feel free to remove the $Id$ lines from your ports as you 
update them, or do nothing with the $Id$ lines until we've figured out what to 
do.

___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Removing "$Id$" lines

[Lawrence Velázquez]

> On Nov 1, 2016, at 3:55 PM, Daniel J. Luke  wrote:
> 
>> On Nov 1, 2016, at 3:36 PM, Lawrence Velázquez  wrote:
>> 
>> While I agree in principle that our committing should not be
>> hampered by the buildbot and would welcome another solution, I'm not
>> crazy about the idea of polluting our (permanent!) commit history
>> with transient administrivia like this.
> 
> A tag that indicates 'This commit was part of a mass change' (that
> doesn't change the build product) doesn't seem like pollution in the
> commit history to me, but I don't really care too much.

In the Trac ticket, Rainer linked to a Stack Overflow post that
suggested modifying a dummy file. I'm more amenable to that method.

> I imagine this could also be handled 'manually' by someone who could
> temporarily disable the build infrastructure, make the mass change,
> and then bring the build infrastructure back up.

I think GitHub would eventually redeliver the failed webhook payload in
that case.

vq
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Removing "$Id$" lines

[Lawrence Velázquez]

> On Nov 1, 2016, at 3:45 PM, Rainer Müller  wrote:
> 
> On 2016-11-01 19:43, Lawrence Velázquez wrote:
>> In any case, the proposed set of commits is utterly unnecessary and is
>> not worth any of this fuss.
> 
> I do not want to keep commenting on every single submission that it
> needs to remove the $Id$ line. This should be done as one commit and we
> would never see it again.

In private discussion with Mojca, I realized that for some reason I'd
gotten it into my head that there would be thousands of commits, instead
of just a few commits that modified thousands of ports each. I'd also
forgotten (even though I implemented it) that the buildmaster now only
sends off one BuildSet per push due to the tree-stable timer. So there
would not be as many objects flying around as I'd thought.

It's hard to say without trying it, but committing then canceling might
not actually be that bad.

vq
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Removing "$Id$" lines

[Daniel J. Luke]

On Nov 1, 2016, at 3:36 PM, Lawrence Velázquez  wrote:
> While I agree in principle that our committing should not be hampered by
> the buildbot and would welcome another solution, I'm not crazy about the
> idea of polluting our (permanent!) commit history with transient
> administrivia like this.

A tag that indicates 'This commit was part of a mass change' (that doesn't 
change the build product) doesn't seem like pollution in the commit history to 
me, but I don't really care too much.

I imagine this could also be handled 'manually' by someone who could 
temporarily disable the build infrastructure, make the mass change, and then 
bring the build infrastructure back up.

-- 
Daniel J. Luke



___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Removing "$Id$" lines

[Rainer Müller]

On 2016-11-01 19:43, Lawrence Velázquez wrote:
> In any case, the proposed set of commits is utterly unnecessary and is
> not worth any of this fuss.

I do not want to keep commenting on every single submission that it
needs to remove the $Id$ line. This should be done as one commit and we
would never see it again.

If I had anticipated that this would cause such a problem because of the
buildbots, I would have insisted we remove $Id$ during the repository
migration...

Rainer
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Removing "$Id$" lines

[Lawrence Velázquez]

> On Nov 1, 2016, at 4:59 AM, Marko Käning  wrote:
> 
>> On 01 Nov 2016, at 02:02 , Rainer Müller  wrote:
>> 
>> buildbot: ignore
> 
> +1
> 
> I’d also suggest to use this also to specify which buildbots should be used 
> for a commit:
> 
> buildbot: Mavericks Sierra
> 
> I think that can be very helpful in some cases.

While I agree in principle that our committing should not be hampered by
the buildbot and would welcome another solution, I'm not crazy about the
idea of polluting our (permanent!) commit history with transient
administrivia like this.

vq
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Removing "$Id$" lines

[Lawrence Velázquez]

> On Nov 1, 2016, at 2:22 PM, Mojca Miklavec  wrote:
> 
>> On 1 November 2016 at 18:07, Lawrence Velázquez wrote:
>> 
>>> On Nov 1, 2016, at 7:00 AM, Mojca Miklavec wrote:
>>> 
>>> Why not:
>>> - wait until all the slaves have something non-trivial to do (make
>>> sure the queue is not empty)
>>> - do a bulk commit
>>> - cancel the job manually
>> 
>> That won't prevent the buildmaster from receiving 20,000 changes,
>> processing ~100,000 build requests, and scheduling ~100,000 builds.
> 
> No, that's not true. 100.000(?) build request would only be scheduled
> if we fail to cancel the build on the portwatcher.

I don't think this is accurate. Builds would not yet have been created,
but BuildRequests would have been scheduled.

But I think you're right, for the wrong reasons. I forgot that the port
scheduler has a tree stable timer now; a single BuildSet would be
created for all 20,000 Changes.

> If we cancel the job on the portwatcher before
> it gets processed, there will be absolutely zero penalty (except that
> the failcache would probably be erased).

Just because builds are not actually happening yet does not mean there
isn't a memory penalty from the queued requests.

In any case, the proposed set of commits is utterly unnecessary and is
not worth any of this fuss.

vq
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Removing "$Id$" lines

[Mojca Miklavec]

On 1 November 2016 at 18:07, Lawrence Velázquez wrote:
>> On Nov 1, 2016, at 7:00 AM, Mojca Miklavec wrote:
>>
>> On 1 November 2016 at 01:03, Ryan Schmidt wrote:
>>> On Oct 31, 2016, at 17:17, Dan Ports wrote:

 Any reason not to just bulk-remove them all at once?
>>>
>>> That would probably tie up the buildbot for weeks or months. We could 
>>> cancel those builds, but even the act of scheduling 20,000 builds per 
>>> builder is much more than we've ever attempted before and I think it would 
>>> not be happy about it. At the very least, I would want to wait until I've 
>>> switched the buildbot from SQLite to PostgreSQL.
>>>
>>> Please, for now, just make this change together with other necessary 
>>> changes.
>>
>> Why not:
>> - wait until all the slaves have something non-trivial to do (make
>> sure the queue is not empty)
>> - do a bulk commit
>> - cancel the job manually
>
> That won't prevent the buildmaster from receiving 20,000 changes,
> processing ~100,000 build requests, and scheduling ~100,000 builds.

No, that's not true. 100.000(?) build request would only be scheduled
if we fail to cancel the build on the portwatcher. In that case we
would of course have to break all of those thousands of jobs on the
portbuilder "manually". If we cancel the job on the portwatcher before
it gets processed, there will be absolutely zero penalty (except that
the failcache would probably be erased).

Mojca
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Removing "$Id$" lines

[Ryan Schmidt]

On Nov 1, 2016, at 12:38, Bradley Giesbrecht wrote:
> 
> Would it work as well to have the buildbots ignore commits with unchanged 
> epoch_version_revision.

No: imagine that a port fails to build because pkgconfig wasn't there. To fix 
that, you'll add a build dependency on pkgconfig; you won't change the epoch, 
version or revision, but you still want the buildbot to try to build it again. 
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Removing "$Id$" lines

[Clemens Lang]

Hi,

On Tue, Nov 01, 2016 at 10:38:42AM -0700, Bradley Giesbrecht wrote:
> Would it work as well to have the buildbots ignore commits with
> unchanged epoch_version_revision.

That's https://trac.macports.org/ticket/52765. It would still take the
time to process the change and figure out that a port has already built
successfully before, and it would still trigger builds for ports that
previously failed to build (because that particular commit could be the
one that fixes the build, which you don't know unless you try).

-- 
Clemens
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Removing "$Id$" lines

[Bradley Giesbrecht]

> On Oct 31, 2016, at 6:02 PM, Rainer Müller  wrote:
> 
> On 2016-11-01 01:03, Ryan Schmidt wrote:
>> On Oct 31, 2016, at 17:17, Dan Ports  wrote:
>>> 
>>> Any reason not to just bulk-remove them all at once?
>> 
>> That would probably tie up the buildbot for weeks or months. We could
>> cancel those builds, but even the act of scheduling 20,000 builds per
>> builder is much more than we've ever attempted before and I think it
>> would not be happy about it. At the very least, I would want to wait
>> until I've switched the buildbot from SQLite to PostgreSQL.
> 
> Can we maybe decide on special commands in commit messages that cause
> the buildbot to completely ignore the commit? Such things should not
> limit us to what we can commit or not.
> 
> Perhaps a footer line (similar to Signed-off-by) at the end, such as:
> 
> buildbot: ignore

Would it work as well to have the buildbots ignore commits with unchanged 
epoch_version_revision.

—
Brad

___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Removing "$Id$" lines

[Lawrence Velázquez]

> On Nov 1, 2016, at 7:00 AM, Mojca Miklavec  wrote:
> 
> On 1 November 2016 at 01:03, Ryan Schmidt wrote:
>> On Oct 31, 2016, at 17:17, Dan Ports wrote:
>>> 
>>> Any reason not to just bulk-remove them all at once?
>> 
>> That would probably tie up the buildbot for weeks or months. We could cancel 
>> those builds, but even the act of scheduling 20,000 builds per builder is 
>> much more than we've ever attempted before and I think it would not be happy 
>> about it. At the very least, I would want to wait until I've switched the 
>> buildbot from SQLite to PostgreSQL.
>> 
>> Please, for now, just make this change together with other necessary changes.
> 
> Why not:
> - wait until all the slaves have something non-trivial to do (make
> sure the queue is not empty)
> - do a bulk commit
> - cancel the job manually

That won't prevent the buildmaster from receiving 20,000 changes,
processing ~100,000 build requests, and scheduling ~100,000 builds.

There's basically zero benefit to such a mass commit. The "$Id$" lines
are harmless.

vq
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Removing "$Id$" lines

[Mojca Miklavec]

On 1 November 2016 at 01:03, Ryan Schmidt wrote:
> On Oct 31, 2016, at 17:17, Dan Ports wrote:
>>
>> Any reason not to just bulk-remove them all at once?
>
> That would probably tie up the buildbot for weeks or months. We could cancel 
> those builds, but even the act of scheduling 20,000 builds per builder is 
> much more than we've ever attempted before and I think it would not be happy 
> about it. At the very least, I would want to wait until I've switched the 
> buildbot from SQLite to PostgreSQL.
>
> Please, for now, just make this change together with other necessary changes.

Why not:
- wait until all the slaves have something non-trivial to do (make
sure the queue is not empty)
- do a bulk commit
- cancel the job manually

Mojca
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Removing "$Id$" lines

[Marko Käning]

On 01 Nov 2016, at 02:02 , Rainer Müller  wrote:
> buildbot: ignore

+1

I’d also suggest to use this also to specify which buildbots should be used for 
a commit:

buildbot: Mavericks Sierra

I think that can be very helpful in some cases.


Opened a ticket for this: https://trac.macports.org/ticket/52769#ticket
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Removing "$Id$" lines

[Rainer Müller]

On 2016-11-01 01:03, Ryan Schmidt wrote:
> On Oct 31, 2016, at 17:17, Dan Ports  wrote:
>> 
>> Any reason not to just bulk-remove them all at once?
> 
> That would probably tie up the buildbot for weeks or months. We could
> cancel those builds, but even the act of scheduling 20,000 builds per
> builder is much more than we've ever attempted before and I think it
> would not be happy about it. At the very least, I would want to wait
> until I've switched the buildbot from SQLite to PostgreSQL.

Can we maybe decide on special commands in commit messages that cause
the buildbot to completely ignore the commit? Such things should not
limit us to what we can commit or not.

Perhaps a footer line (similar to Signed-off-by) at the end, such as:

buildbot: ignore


For reference, other services seem to use "[ci skip]" as a keyword that
can appear anywhere in the commit message.

Rainer
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Removing "$Id$" lines

[Dan Ports]

On Mon, Oct 31, 2016 at 07:03:24PM -0500, Ryan Schmidt wrote:
> On Oct 31, 2016, at 17:17, Dan Ports  wrote:
> > 
> > Any reason not to just bulk-remove them all at once?
> 
> That would probably tie up the buildbot for weeks or months. We could cancel 
> those builds, but even the act of scheduling 20,000 builds per builder is 
> much more than we've ever attempted before and I think it would not be happy 
> about it. At the very least, I would want to wait until I've switched the 
> buildbot from SQLite to PostgreSQL.
> 
> Please, for now, just make this change together with other necessary changes. 

That's what I was wondering about. I'll wait.

Dan

-- 
Dan R. K. PortsUW CSEhttps://drkp.net/
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Removing "$Id$" lines

[Ryan Schmidt]

On Oct 31, 2016, at 17:17, Dan Ports  wrote:
> 
> Any reason not to just bulk-remove them all at once?

That would probably tie up the buildbot for weeks or months. We could cancel 
those builds, but even the act of scheduling 20,000 builds per builder is much 
more than we've ever attempted before and I think it would not be happy about 
it. At the very least, I would want to wait until I've switched the buildbot 
from SQLite to PostgreSQL.

Please, for now, just make this change together with other necessary changes. 


___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Removing "$Id$" lines

[Lawrence Velázquez]

> On Oct 31, 2016, at 6:17 PM, Dan Ports  wrote:
> 
> Any reason not to just bulk-remove them all at once?

No reason other than time and effort.

vq
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Removing "$Id$" lines

[Dan Ports]

Any reason not to just bulk-remove them all at once?

Dan

On Mon, Oct 31, 2016 at 05:30:07PM -0400, Lawrence Velázquez wrote:
> Hi,
> 
> We no longer have use for "$Id" lines, so committers should remove them at 
> their convenience.
> 
> vq
> 
> > On Oct 31, 2016, at 5:20 PM, Schamschula 
> >  wrote:
> > 
> > Schamschula pushed a commit to branch master
> > in repository macports-ports.
> > 
> > https://github.com/macports/macports-ports/commit/eee819a1785e92bd2824517c0aff6ee855837c12
> >  
> > 
> > The following commit(s) were added to refs/heads/master by this push:
> >  new eee819a  libpcap: update to version 1.8.1.
> > eee819a is described below
> > 
> > commit eee819a1785e92bd2824517c0aff6ee855837c12
> > Author: Marius Schamschula 
> > AuthorDate: Mon Oct 31 16:16:22 2016 -0500
> > 
> > libpcap: update to version 1.8.1.
> > ---
> >  net/libpcap/Portfile | 8 
> >  1 file changed, 4 insertions(+), 4 deletions(-)
> > 
> > diff --git a/net/libpcap/Portfile b/net/libpcap/Portfile
> > index 6b8eb0d..201f2bd 100644
> > --- a/net/libpcap/Portfile
> > +++ b/net/libpcap/Portfile
> > @@ -1,10 +1,10 @@
> >  # -*- coding: utf-8; mode: tcl; tab-width: 4; indent-tabs-mode: nil; 
> > c-basic-offset: 4 -*- vim:fenc=utf-8:ft=tcl:et:sw=4:ts=4:sts=4
> > -# $Id$
> > +# $Id: Portfile 152274 2016-09-02 11:03:02Z m...@macports.org $
> >  
> >  PortSystem  1.0
> >  
> >  namelibpcap
> > -version 1.8.0
> > +version 1.8.1
> >  categories  net
> >  maintainers mps openmaintainer
> >  license BSD
> > @@ -17,8 +17,8 @@ homepagehttp://www.tcpdump.org/
> >  platforms   darwin
> >  master_sites${homepage}release/
> >  
> > -checksums   rmd160  4cfef07ac9f008b329c00bf0ebbe547f6738f2eb \
> > -sha256  
> > f47b51533f9f060afb304010ea5cbf51d032707333bca70c36351d255754659c
> > +checksums   rmd160  295766ab2646c05c330aa04cabc30c5737200279 \
> > +sha256  
> > 673dbc69fdc3f5a86fb5759ab19899039a8e5e6c631749e48dcd9c6f0c83541e
> >  
> >  configure.args  --disable-bluetooth \
> >  --disable-canusb \
> 

> ___
> macports-dev mailing list
> macports-dev@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev


-- 
Dan R. K. PortsUW CSEhttps://drkp.net/
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Removing "$Id$" lines

[Marius Schamschula]

Larry,

OK. Will do.

On Oct 31, 2016, at 4:30 PM, Lawrence Velázquez  wrote:

> Hi,
> 
> We no longer have use for "$Id" lines, so committers should remove them at 
> their convenience.
> 
> vq
> 
>> On Oct 31, 2016, at 5:20 PM, Schamschula 
>>  wrote:
>> 
>> Schamschula pushed a commit to branch master
>> in repository macports-ports.
>> 
>> https://github.com/macports/macports-ports/commit/eee819a1785e92bd2824517c0aff6ee855837c12
>> 
>> The following commit(s) were added to refs/heads/master by this push:
>>  new eee819a  libpcap: update to version 1.8.1.
>> eee819a is described below
>> 
>> commit eee819a1785e92bd2824517c0aff6ee855837c12
>> Author: Marius Schamschula 
>> AuthorDate: Mon Oct 31 16:16:22 2016 -0500
>> 
>> libpcap: update to version 1.8.1.
>> ---
>>  net/libpcap/Portfile | 8 
>>  1 file changed, 4 insertions(+), 4 deletions(-)
>> 
>> diff --git a/net/libpcap/Portfile b/net/libpcap/Portfile
>> index 6b8eb0d..201f2bd 100644
>> --- a/net/libpcap/Portfile
>> +++ b/net/libpcap/Portfile
>> @@ -1,10 +1,10 @@
>>  # -*- coding: utf-8; mode: tcl; tab-width: 4; indent-tabs-mode: nil; 
>> c-basic-offset: 4 -*- vim:fenc=utf-8:ft=tcl:et:sw=4:ts=4:sts=4
>> -# $Id$
>> +# $Id: Portfile 152274 2016-09-02 11:03:02Z m...@macports.org $
>>  
>>  PortSystem  1.0
>>  
>>  namelibpcap
>> -version 1.8.0
>> +version 1.8.1
>>  categories  net
>>  maintainers mps openmaintainer
>>  license BSD
>> @@ -17,8 +17,8 @@ homepagehttp://www.tcpdump.org/
>>  platforms   darwin
>>  master_sites${homepage}release/
>>  
>> -checksums   rmd160  4cfef07ac9f008b329c00bf0ebbe547f6738f2eb \
>> -sha256  
>> f47b51533f9f060afb304010ea5cbf51d032707333bca70c36351d255754659c
>> +checksums   rmd160  295766ab2646c05c330aa04cabc30c5737200279 \
>> +sha256  
>> 673dbc69fdc3f5a86fb5759ab19899039a8e5e6c631749e48dcd9c6f0c83541e
>>  
>>  configure.args  --disable-bluetooth \
>>  --disable-canusb \
> 
> ___
> macports-dev mailing list
> macports-dev@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev

Marius
--
Marius Schamschula




___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Removing "$Id$" lines

[Lawrence Velázquez]

Hi,

We no longer have use for "$Id" lines, so committers should remove them at 
their convenience.

vq

> On Oct 31, 2016, at 5:20 PM, Schamschula 
>  wrote:
> 
> Schamschula pushed a commit to branch master
> in repository macports-ports.
> 
> https://github.com/macports/macports-ports/commit/eee819a1785e92bd2824517c0aff6ee855837c12
>  
> 
> The following commit(s) were added to refs/heads/master by this push:
>  new eee819a  libpcap: update to version 1.8.1.
> eee819a is described below
> 
> commit eee819a1785e92bd2824517c0aff6ee855837c12
> Author: Marius Schamschula 
> AuthorDate: Mon Oct 31 16:16:22 2016 -0500
> 
> libpcap: update to version 1.8.1.
> ---
>  net/libpcap/Portfile | 8 
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/net/libpcap/Portfile b/net/libpcap/Portfile
> index 6b8eb0d..201f2bd 100644
> --- a/net/libpcap/Portfile
> +++ b/net/libpcap/Portfile
> @@ -1,10 +1,10 @@
>  # -*- coding: utf-8; mode: tcl; tab-width: 4; indent-tabs-mode: nil; 
> c-basic-offset: 4 -*- vim:fenc=utf-8:ft=tcl:et:sw=4:ts=4:sts=4
> -# $Id$
> +# $Id: Portfile 152274 2016-09-02 11:03:02Z m...@macports.org $
>  
>  PortSystem  1.0
>  
>  namelibpcap
> -version 1.8.0
> +version 1.8.1
>  categories  net
>  maintainers mps openmaintainer
>  license BSD
> @@ -17,8 +17,8 @@ homepagehttp://www.tcpdump.org/
>  platforms   darwin
>  master_sites${homepage}release/
>  
> -checksums   rmd160  4cfef07ac9f008b329c00bf0ebbe547f6738f2eb \
> -sha256  
> f47b51533f9f060afb304010ea5cbf51d032707333bca70c36351d255754659c
> +checksums   rmd160  295766ab2646c05c330aa04cabc30c5737200279 \
> +sha256  
> 673dbc69fdc3f5a86fb5759ab19899039a8e5e6c631749e48dcd9c6f0c83541e
>  
>  configure.args  --disable-bluetooth \
>  --disable-canusb \

___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev