Ryan Schmidt | 1 Apr 2010 09:29
Favicon

Re: [65076] trunk/base/src


On Mar 21, 2010, at 12:06, Rainer Müller wrote:

> On 2010-03-21 11:07 , Ryan Schmidt wrote:
>> Do you suppose it would be nice to use setpriority in other phases as
>> well? There are some ports that, though perhaps they shouldn't,
>> compile in either the configure or destroot phases; perhaps they
>> should use lower priority then too. Even ports that don't do this
>> will sometimes do a lot of work in the configure phase, which can eat
>> into CPU time.
> 
> configure and destroot phases in general are I/O bound and not very CPU
> intensive. Changing the scheduling priority only helps to reduce CPU
> load, I/O is not affected. Although there might be ports doing some
> heavy stuff in configure/destroot it usually does not take that long
> that it would disturb normal operations at the same time.

I realize that's the case for most ports. I'm saying there are a few select ports for which that is not the
case. For example, qt4-mac compiles its qmake program in its configure phase; this is normal for qt4-mac.
InsightToolkit spends hours compiling in its build phase, then spends more hours compiling in its
destroot phase; whether this is intentional is unclear but for whatever reason this is what it is doing,
and it would be nice if when it's doing it, it would not suck up my CPU.

> But if we want to lower priority, we would only have to add
> configure.nice/destroot.nice options to portconfigure/portdestroot.

For the benefit of those quirky ports that for whatever reason do processor-intensive tasks outside of the
build phase, it might be nice to do that.

(Continue reading)

Rainer Müller | 1 Apr 2010 10:20
Favicon

Re: [65076] trunk/base/src

On 2010-04-01 09:29 , Ryan Schmidt wrote:
> On Mar 21, 2010, at 12:06, Rainer Müller wrote:
>> But if we want to lower priority, we would only have to add
>> configure.nice/destroot.nice options to portconfigure/portdestroot.
> 
> For the benefit of those quirky ports that for whatever reason do processor-intensive tasks outside of
the build phase, it might be nice to do that.

As using nice does not cause any harm, I added nice to configure and
destroot in r65808.

Rainer
Ryan Schmidt | 1 Apr 2010 13:36
Favicon

Re: [65818] trunk/dports/textproc/eblook/Portfile


On Apr 1, 2010, at 06:35, takanori@... wrote:

> Revision: 65818
>          http://trac.macports.org/changeset/65818
> Author:   takanori@...
> Date:     2010-04-01 04:35:22 -0700 (Thu, 01 Apr 2010)
> Log Message:
> -----------
> eblook: Increased revision number, because port:eb was updated and its library version was changed too.

FYI, I am in the process of updating the eblook port to the newest version.

Titus von Boxberg | 1 Apr 2010 13:59
Picon

patch commit request

Hello,

the committer of port mscgen (landonf) has not responded to update patch ticket 23962,
filed 4 weeks ago.
Would another committer please apply the patch?

Thanks!
Regards
Titus

Takanori Yamamoto | 1 Apr 2010 14:01
Favicon

Re: [65818] trunk/dports/textproc/eblook/Portfile

I see, thanks a lot!

On 2010/04/01, at 20:36, Ryan Schmidt wrote:

> 
> On Apr 1, 2010, at 06:35, takanori@... wrote:
> 
>> Revision: 65818
>>         http://trac.macports.org/changeset/65818
>> Author:   takanori@...
>> Date:     2010-04-01 04:35:22 -0700 (Thu, 01 Apr 2010)
>> Log Message:
>> -----------
>> eblook: Increased revision number, because port:eb was updated and its library version was changed too.
> 
> FYI, I am in the process of updating the eblook port to the newest version.
> 

Mark Anderson | 1 Apr 2010 15:44
Gravatar

Ticket #23774

I have added a PCB Portfile patch that brings it to the latest
version.  Can the maintainer/someone with authority test and commit
it?

Mark
Daniel | 1 Apr 2010 18:08
Gravatar

Re: ownership of bug

Hello? I still can't modify the bugs.

On Tue, Mar 30, 2010 at 10:19 PM, Daniel <nefar-E/T5rpHb0hPNLxjTenLetw@public.gmane.org> wrote:
#18759 in particular but I have more. I'm logged in, but I can only "reply"

-d


On Tue, Mar 30, 2010 at 9:23 PM, Ryan Schmidt <ryandesign-/EBbbHb69GVg9hUCZPvPmw@public.gmane.org> wrote:

On Mar 30, 2010, at 22:43, Daniel wrote:

> seems I own this bug, but I Have no power to close it. since this is 13 months old, and the current version is 2.6.3, can someone close it as irrelevant?

Which bug?


> Also, if people are going to keep assigning me bugs, please give me the ability to close them or mark them fixed.

AFAIK you should have the ability to do so, once you log in to our Trac system with the email address to which the bug is assigned.




--
"America was founded by men who understood that the threat of domestic tyranny is as great as any threat from abroad. If we want to be worthy of their legacy, we must resist the rush toward ever-increasing state control of our society. Otherwise, our own government will become a greater threat to our freedoms than any foreign terrorist."
- Ron Paul, Texas Straight Talk, May 31, 2004



--
"America was founded by men who understood that the threat of domestic tyranny is as great as any threat from abroad. If we want to be worthy of their legacy, we must resist the rush toward ever-increasing state control of our society. Otherwise, our own government will become a greater threat to our freedoms than any foreign terrorist."
- Ron Paul, Texas Straight Talk, May 31, 2004
<div>
<p>Hello? I still can't modify the bugs.<br><br></p>
<div class="gmail_quote">On Tue, Mar 30, 2010 at 10:19 PM, Daniel <span dir="ltr">&lt;<a href="mailto:nefar@...">nefar@...</a>&gt;</span> wrote:<br><blockquote class="gmail_quote">
#18759 in particular but I have more. I'm logged in, but I can only "reply"<div><br></div>
<div>-d</div>
<div>
<div>
<div></div>
<div class="h5">
<br><br><div class="gmail_quote">On Tue, Mar 30, 2010 at 9:23 PM, Ryan Schmidt <span dir="ltr">&lt;<a href="mailto:ryandesign@..." target="_blank">ryandesign@...</a>&gt;</span> wrote:<br><blockquote class="gmail_quote">
<div>
<br>
On Mar 30, 2010, at 22:43, Daniel wrote:<br><br>
&gt; seems I own this bug, but I Have no power to close it. since this is 13 months old, and the current version is 2.6.3, can someone close it as irrelevant?<br><br>
</div>Which bug?<br><div>
<br><br>
&gt; Also, if people are going to keep assigning me bugs, please give me the ability to close them or mark them fixed.<br><br>
</div>AFAIK you should have the ability to do so, once you log in to our Trac system with the email address to which the bug is assigned.<br><br>
</blockquote>
</div>
<br><br clear="all"><br>
</div>
</div>
<div class="im">-- <br>"America was founded by men who understood that the threat of domestic tyranny is as great as any threat from abroad. If we want to be worthy of their legacy, we must resist the rush toward ever-increasing state control of our society. Otherwise, our own government will become a greater threat to our freedoms than any foreign terrorist."<br>

 - Ron Paul, Texas Straight Talk, May 31, 2004<br>
</div>
</div>
</blockquote>
</div>
<br><br clear="all"><br>-- <br>"America was founded by men who understood that the threat of domestic tyranny is as great as any threat from abroad. If we want to be worthy of their legacy, we must resist the rush toward ever-increasing state control of our society. Otherwise, our own government will become a greater threat to our freedoms than any foreign terrorist."<br>
 - Ron Paul, Texas Straight Talk, May 31, 2004<br>
</div>
Rainer Müller | 1 Apr 2010 19:12
Favicon

Re: ownership of bug

On 2010-03-31 06:23 , Ryan Schmidt wrote:
> On Mar 30, 2010, at 22:43, Daniel wrote:
>> Also, if people are going to keep assigning me bugs, please give me the ability to close them or mark them fixed.
> 
> AFAIK you should have the ability to do so, once you log in to our Trac system with the email address to which
the bug is assigned.

No, only committers can modify the ticket properties.

If I remember correctly this has been setup in this way because Trac
only supported the TICKET_MODIFY permission for this back then [1],
which gave full access to all fields including the description, full CC
field, etc. This is also the reason Bill wrote the "Cc Me!" plugin. The
ability to resolve tickets was tied to editing all ticket fields. We
didn't want this as there is no easy way to do a rollback on an unwanted
change by some external person/spambot. But it was also not possible to
assign tickets to non-committers back then.

This might have changed with the Trac update to 0.11, by looking at [2]
I see TICKET_EDIT_CC and TICKET_EDIT_DESCRIPTION as related permissions.
Seems like these are no longer granted automatically with TICKET_MODIFY.

Rainer

[1] http://trac.macports.org/ticket/10900,
    http://trac.macports.org/ticket/13352
[2] http://trac.macports.org/wiki/TracPermissions
Daniel | 1 Apr 2010 23:29
Gravatar

Re: ownership of bug

So the issue remains. I'm stuck being the owner of a ticket I cannot close. Can someone please either remove me as owner, or give the appropriate permissions?




On Thu, Apr 1, 2010 at 10:12 AM, Rainer Müller <raimue-/EBbbHb69GVg9hUCZPvPmw@public.gmane.org> wrote:
On 2010-03-31 06:23 , Ryan Schmidt wrote:
> On Mar 30, 2010, at 22:43, Daniel wrote:
>> Also, if people are going to keep assigning me bugs, please give me the ability to close them or mark them fixed.
>
> AFAIK you should have the ability to do so, once you log in to our Trac system with the email address to which the bug is assigned.

No, only committers can modify the ticket properties.

If I remember correctly this has been setup in this way because Trac
only supported the TICKET_MODIFY permission for this back then [1],
which gave full access to all fields including the description, full CC
field, etc. This is also the reason Bill wrote the "Cc Me!" plugin. The
ability to resolve tickets was tied to editing all ticket fields. We
didn't want this as there is no easy way to do a rollback on an unwanted
change by some external person/spambot. But it was also not possible to
assign tickets to non-committers back then.

This might have changed with the Trac update to 0.11, by looking at [2]
I see TICKET_EDIT_CC and TICKET_EDIT_DESCRIPTION as related permissions.
Seems like these are no longer granted automatically with TICKET_MODIFY.

Rainer

[1] http://trac.macports.org/ticket/10900,
   http://trac.macports.org/ticket/13352
[2] http://trac.macports.org/wiki/TracPermissions
_______________________________________________
macports-dev mailing list
macports-dev-qhrM8SXbD5LF11Dp+j+f1g@public.gmane.orgosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev



--
"America was founded by men who understood that the threat of domestic tyranny is as great as any threat from abroad. If we want to be worthy of their legacy, we must resist the rush toward ever-increasing state control of our society. Otherwise, our own government will become a greater threat to our freedoms than any foreign terrorist."
- Ron Paul, Texas Straight Talk, May 31, 2004
<div>
<p>So the issue remains. I'm stuck being the owner of a ticket I cannot close. Can someone please either remove me as owner, or give the appropriate permissions?</p>
<div><br></div>
<div>
<br><br><div class="gmail_quote">On Thu, Apr 1, 2010 at 10:12 AM, Rainer M&uuml;ller <span dir="ltr">&lt;<a href="mailto:raimue@...">raimue@...</a>&gt;</span> wrote:<br><blockquote class="gmail_quote">
<div class="im">On 2010-03-31 06:23 , Ryan Schmidt wrote:<br>
&gt; On Mar 30, 2010, at 22:43, Daniel wrote:<br>
</div>
<div class="im">&gt;&gt; Also, if people are going to keep assigning me bugs, please give me the ability to close them or mark them fixed.<br>
&gt;<br>
&gt; AFAIK you should have the ability to do so, once you log in to our Trac system with the email address to which the bug is assigned.<br><br>
</div>No, only committers can modify the ticket properties.<br><br>
If I remember correctly this has been setup in this way because Trac<br>
only supported the TICKET_MODIFY permission for this back then [1],<br>
which gave full access to all fields including the description, full CC<br>
field, etc. This is also the reason Bill wrote the "Cc Me!" plugin. The<br>
ability to resolve tickets was tied to editing all ticket fields. We<br>
didn't want this as there is no easy way to do a rollback on an unwanted<br>
change by some external person/spambot. But it was also not possible to<br>
assign tickets to non-committers back then.<br><br>
This might have changed with the Trac update to 0.11, by looking at [2]<br>
I see TICKET_EDIT_CC and TICKET_EDIT_DESCRIPTION as related permissions.<br>
Seems like these are no longer granted automatically with TICKET_MODIFY.<br><br>
Rainer<br><br>
[1] <a href="http://trac.macports.org/ticket/10900" target="_blank">http://trac.macports.org/ticket/10900</a>,<br>
 &nbsp; &nbsp;<a href="http://trac.macports.org/ticket/13352" target="_blank">http://trac.macports.org/ticket/13352</a><br>
[2] <a href="http://trac.macports.org/wiki/TracPermissions" target="_blank">http://trac.macports.org/wiki/TracPermissions</a><br>
_______________________________________________<br>
macports-dev mailing list<br><a href="mailto:macports-dev@...">macports-dev@...osforge.org</a><br><a href="http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev" target="_blank">http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev</a><br>
</blockquote>
</div>
<br><br clear="all"><br>-- <br>"America was founded by men who understood that the threat of domestic tyranny is as great as any threat from abroad. If we want to be worthy of their legacy, we must resist the rush toward ever-increasing state control of our society. Otherwise, our own government will become a greater threat to our freedoms than any foreign terrorist."<br>
 - Ron Paul, Texas Straight Talk, May 31, 2004<br>
</div>
</div>
Frank Schima | 2 Apr 2010 05:03
Favicon

Re: patch commit request


On Apr 1, 2010, at 5:59 AM, Titus von Boxberg wrote:

> the committer of port mscgen (landonf) has not responded to update patch ticket 23962,
> filed 4 weeks ago.
> Would another committer please apply the patch?

Done in r65846.

-Frank


Gmane