R David Murray added the comment:
As I noted on the other issue, this is the wrong place to report planetpython
issues.
--
nosy: +r.david.murray
priority: bug -> wish
status: unread -> resolved
___
PSF Meta Tracker <
R David Murray added the comment:
The tracker is not planetpython. Probably the right people to contact about
this (or at least a good place to start) is the infrastructure team.
--
nosy: +r.david.murray
priority: feature -> wish
status: unread -> ch
R David Murray added the comment:
My understanding (and I thought experience, but I can't swear to it)
was that it was already prohibited. Maybe we broke something in our
recent changes to support the github workflow?
--
nosy: +r.david.murray
status: unread -> chatt
R David Murray added the comment:
Yes, there is a reason :) Someone comes to the tracker with a bug, and does a
good search...and with an open-only search doesn't find an issue, because we've
already fixed it but it isn't in the version of python they are running. But
the default searches
R David Murray added the comment:
I'm not sure what you mean by "be conservative". Leave the current tag alone
and add "easy (C)" and just apply it to the identified C issues? That would
actually make sense. We could also add a *new* 'easy (python)', and retire the
R David Murray added the comment:
We have since had the occasion to add Developer to a couple of people
specifically so they could be assigned issues (people Raymond is tutoring). So
IMO that field is working as desired at the current time. There's no
alternative to a thread on core
R David Murray added the comment:
Well, we can edit the apache server config too. In fact, I thought I'd done
the diffie-hellman fix, but I guess I didn't.
I don't understand the 'cert expires' part, it was renewed in September of 2015.
Is there any reason we couldn't use letsencrypt
R David Murray added the comment:
If we are going to do anything with the assigned to field, I think we should
just remove it. But if we don't remove it, I think having triagers in the
assignment list is fine. They are on a path to be a developer, so if they want
to use it I don't see why
R David Murray added the comment:
Grade: C.
That is pretty uninformative. Did I miss something?
--
nosy: +r.david.murray
status: unread -> chatting
___
PSF Meta Tracker <metatrac...@psf.upfronthosting.co.za&
R David Murray added the comment:
Maybe put the code in with a switch so we can turn it on and off? I'm pretty
sure we're going to want it, but not positive.
___
PSF Meta Tracker <metatrac...@psf.upfronthosting.co.za>
R David Murray added the comment:
Yes, I was assuming we'd post to the right account when we can determine it.
It was only github accounts with no linkage where we'd need a 'generic' user
for posting. And we *will* get PRs from people who won't open bugs.python.org
accounts, even if asked
R David Murray added the comment:
Hmm. Good question. We could use a specific user to create such issues.
As for noise...we do typo issues now, so if we have an increased volume of them
I think that just means we're fixing more typos. I don't really see the
problem with that, since
R David Murray added the comment:
Don't do lookups, do mechanical translation. The translation happens at page
rendering time, so if github changes it URLs (or we move to a different
provider), we just change the linkifier code to match.
--
nosy: +r.david.murray
R David Murray added the comment:
If github batched the review comments, what we would want (what we've wanted
for a long time from reitveld) is a note posted to b.p.o that there *are*
review comments. But since github does *not* batch review comments, posting
every comment (especially
R David Murray added the comment:
But, really, this level of discussion should take place on the workflow mailing
list, not in the context of the patch.
___
PSF Meta Tracker <metatrac...@psf.upfronthosting.co.za>
R David Murray added the comment:
Berker: I presume the point here is that this creates the field, and issue 589
fills it in automatically by having github call roundup when a PR is created.
I haven't looked at either patch closely enough to know if I'm right, but
that's what I'd expect
R David Murray added the comment:
Looks OK to me (without testing it). You probably meant to write
'status_changed' twice in the assignment for status_close, though.
--
status: unread -> chatting
___
PSF Meta Tracker <me
R David Murray added the comment:
I misspoke. Looking at the edit screen again, the issue is the 'leave in/leave
out' versus 'delete', which is indeed retire. The complicating factor is: what
if you 'leave in' a public query that someone then retires? It is stuck on
your visible list
R David Murray added the comment:
If I remember correctly this problem is the result of an incomplete fix to an
earlier problem. As I remember it the problem is that if you don't delete the
query it still shows up even when retired. To keep the DB consistent, the
correct fix would
R David Murray added the comment:
This bug tracker is for reporting problems with bugs.python.org. Your post
belongs on bugs.python.org itself if anywhere, but it sounds like your problem
is really with your tk version or your window system. You might want to try
posting to the python-list
R David Murray added the comment:
That is correct, it is a tracker-wide setting, and the community has elected to
get the notifications. To make it a user setting would be a feature request
for the Roundup tracker; their tracker is at http://issues.roundup-tracker.org/
if you want to submit
R David Murray added the comment:
The disabling of ipv6 reported by mmangoba does not appear to have been
effective. On the advice of p@trick, I added 'inet_protocols=ipv4' to the
postfix config and restarted (around 15:28 Eastern) and that seems to have
worked. Serhiy was able to get
R David Murray added the comment:
This should be reported to Roundup upstream. The fix should be simple (just
changing the csv dialect), so it doesn't really matter who develops the patch
as long as both upstream and we apply it :)
--
nosy: +r.david.murray
status: unread -> chatt
R David Murray added the comment:
This is the bug tracker for issues with the python bug tracker. For problems
with third party software, you will need to find the bug tracker for that
software (pyodbc, in this case).
--
nosy: +r.david.murray
priority: bug -> wish
status: unr
R David Murray added the comment:
That has nothing to do with this issue. Nor do we do anything currently with
dmarc. There are other issues about roundup mail getting marked as spam, you
could repost your observations on one of those if you like.
--
nosy: +r.david.murray
R David Murray added the comment:
Done.
--
nosy: +r.david.murray
status: unread - resolved
___
PSF Meta Tracker metatrac...@psf.upfronthosting.co.za
http://psf.upfronthosting.co.za/roundup/meta/issue572
R David Murray added the comment:
And you both have the power to undo it if you decide you don't like it :)
(bugs.python.org/component, in case you've forgotten).
___
PSF Meta Tracker metatrac...@psf.upfronthosting.co.za
http
R David Murray added the comment:
I'm glad you found a solution. Yes, it is true that if you use a virtual
environment then you must always use that virtual environment (one way or
another).
___
PSF Meta Tracker metatrac
R David Murray added the comment:
Well, the correct fix would be to change the search template so that the form
says last activity date.
That field is really there to be sorted on, not searched on.
--
nosy: +r.david.murray
status: unread - chatting
R David Murray added the comment:
Mail is consistently sent from rep...@bugs.python.org, always from the same IP
address, 46.4.197.70. 46.4.197.70 resolves to bugs.python.org.
So, we are meeting the requirements set forth in the article you link. I've
asked about adding SPF records, which I
R David Murray added the comment:
This is the tracker for problems with the functioning of the bugs.python.org
tracker. python bugs should be reported to the bugs.python.org tracker itself,
not here.
--
nosy: +r.david.murray
priority: urgent - wish
status: unread - resolved
R David Murray added the comment:
Here is the traceback from the log. My guess would be that the problem is due
to the relatively recent (three months or so?) cross site scripting security
fixes, which are preventing the real error message (whatever it is) from
getting rendered.
10.0.0.1
R David Murray added the comment:
Ah, this is a duplicate of issue 458, then.
--
status: chatting - resolved
superseder: +editing homepage field is not possible
___
PSF Meta Tracker metatrac...@psf.upfronthosting.co.za
http
R David Murray added the comment:
I've used plenty of web sites where the equivalent of 'no selection' was not a
valid choice (ie: you had to select something before the form would be accepted
for submission).
Your argument appears to be that once the issue has been created, 'no
selection
On Tue, 15 Jul 2014 10:12:19 +0300, anatoly techtonik techto...@gmail.com
wrote:
If Roundup plugin system is reworked a bit, it is
possible to make extensions to create and monitor
upstream bugs (Debian). Maybe even exchange
messages with it.
That would be downstream, and I'm not sure why we
R David Murray added the comment:
Sounds good to me.
--
nosy: +r.david.murray
___
PSF Meta Tracker metatrac...@psf.upfronthosting.co.za
http://psf.upfronthosting.co.za/roundup/meta/issue544
New submission from R David Murray:
Apr 22 17:32:16 psf postfix/smtp[3647]: 2CDF8568E0:
to=dupingpin...@hotmail.com, relay=mx4.hotmail.com[65.55.37.120]:25,
delay=0.66, delays=0.02/0/0.48/0.16, dsn=5.0.0, status=bounced (host
mx4.hotmail.com[65.55.37.120] said: 550 SC-001 (COL0-MC4-F23
In case you missed it on the other lists I posted it to, we're planning
on having discussions about our roundup/rietveld setup and how to improve
it on the new core-workflow mailing list:
https://mail.python.org/mailman/listinfo/core-workflow
I'm certainly hoping that we will get more people
R David Murray added the comment:
When I search for 'human' in 'all text' leaving all the other fields at their
defaults, I get that issue among the 45 results returned. When I search from
the search box, I get 157 results, and 18104 is on the first page of results.
There is a bug in next
New submission from R David Murray:
The traceback in the admin email looks like this:
Traceback (most recent call last):
File /home/roundup/lib/python2.6/site-packages/roundup/cgi/client.py, line
463, in inner_main
html = self.handle_action()
File /home/roundup/lib/python2.6/site
R David Murray added the comment:
I managed to make some time to look at this, and I believe I've fixed it. The
template loader method 'get' no longer exists, it is now 'load'. Changing the
call to 'load('user.openid') seems to have worked.
I haven't committed this since I don't currently
On Mon, 06 Jan 2014 14:14:25 +0900, Stephen J. Turnbull
turnb...@sk.tsukuba.ac.jp wrote:
Benjamin Peterson writes:
Not sure if this is interesting.
2. As soon as we submit the crafted URL, we get an alert box saying XSS.
URL:
R David Murray added the comment:
Before I saw Barry's message, I removed 2.6 from the list of versions via the
web interface (which retires it). It can be re-added (un-retired) though, if
we have consensus on that. (It is id '1', which someone will need to know if
they do this.)
But, our
R David Murray added the comment:
murray@psf:~$ traceroute6 www.python.org
traceroute to www.python.org (2001:888:2000:d::a2), 30 hops max, 80 byte packets
1 2a01:4f8:131:2480::3 (2a01:4f8:131:2480::3) 3001.350 ms !H 3001.349 ms !H
3001.345 ms !H
R David Murray added the comment:
This is the correct tracker to report problems with the python bug tracker.
The issue you report is a known issue, but has nothing to do with chrome. It
has to do with what page you start on when you submit the login form.
See issue 448 for more information
R David Murray added the comment:
I'm not sure what this submission is trying to say, but it doesn't seem to have
anything to do with a bug in the python bug tracker, which is the purpose of
this bug tracker. It sounds like you want to be communicating with the django
community instead
New submission from R David Murray:
Christian Heims reported on the infrastructure list that there was spam on
issue 12641 from unknown users. I've done some poking around, and they
weren't created via openid. Presumably they were created the normal way
through the registration form, which
R David Murray added the comment:
Here are the log records for emails sent to your address since July 21st at
06:25 CEST:
Jul 22 13:57:02 psf postfix/smtp[29578]: 8ED9A56A35: to=samw...@gmail.com,
relay=gmail-smtp-in.l.google.com[2a00:1450:400c:c03::1a]:25, delay=0.67,
delays=0.01/0/0.06/0.6
R David Murray added the comment:
Because sorting is a generic interface. You'd have to add special code to deny
sorting by password. But as Martin says, it's not a security issue.
--
nosy: +r.david.murray
___
PSF Meta Tracker
R David Murray added the comment:
As Martin (I think) has said, just how damaging would compromising this
password be? Tracker changes are all reversible.
On the other hand I'm in favor of using https in general. This was discussed
on the infrastructure list, and the issue is that bugs
R David Murray added the comment:
Well, yes, I know that is common. Unfortunately, https doesn't solve that lack
of security knowledge, since if one account gets cracked because of insecure
servers, the rest of their accounts are also compromised
On Wed, 20 Mar 2013 10:26:19 +0300, anatoly techtonik techto...@gmail.com
wrote:
You're wrong. I did't even have a slight though about making Python take
over another established product. I am speaking about the culture of eating
your own dogfood and collaborating with upstream. Don't you
On Sun, 17 Mar 2013 02:56:12 +0300, anatoly techtonik techto...@gmail.com
wrote:
The major goal is to lower the barrier to let people start hacking at
Roundup. The secondary goal it to I am not sure about the Python 3 porting,
but currently b.p.o uses a patched version of Roundup, which is no
On Wed, 13 Feb 2013 10:20:51 -0800, fwierzbi...@gmail.com
fwierzbi...@gmail.com wrote:
Proposal: Jython to use the same tracker as CPython
I think you should send this to the python-committers mailing list,
and probably then to python-dev assuming it passes muster on
committers :)
I have no
R David Murray added the comment:
This is the issue tracker for the python.org issue trackers (the
metatracker). jython's issue tracker is at bugs.jython.org. However, your
question isn't really appropriate for an issue tracker, you are better off
posting it to the jython mailing list
On Sun, 25 Nov 2012 16:07:56 +0200, Ezio Melotti ezio.melo...@gmail.com wrote:
On Sun, Nov 25, 2012 at 3:30 PM, anatoly techtonik techto...@gmail.comwrote:
On Sun, Nov 25, 2012 at 1:56 AM, Ezio Melotti ezio.melo...@gmail.comwrote:
On Sun, Nov 25, 2012 at 12:24 AM, anatoly techtonik
R David Murray added the comment:
If the contributor icon is not added, I think removing the contrib form
received marker would be good. As it is, one is fooled into expecting both
icons should be there when appropriate, and might mistakenly think someone is
not a committer because
R David Murray added the comment:
This is probably a duplicate of issue 448.
--
nosy: +r.david.murray
status: unread - chatting
___
PSF Meta Tracker metatrac...@psf.upfronthosting.co.za
http://psf.upfronthosting.co.za/roundup/meta
New submission from R David Murray:
I tried to remove Colin Winter's UID from the 'assign-to' field for component,
but when I clicked save I got the red-bar error message 'No such action
editcsv'
--
messages: 2565
nosy: r.david.murray
priority: bug
status: unread
title: Cannot edit
R David Murray rdmur...@bitdance.com added the comment:
Yeah, I didn't look in the docs, I did 'grep -r python-bugs' trackers/tracker'
in the roundup directory :)
___
PSF Meta Tracker metatrac...@psf.upfronthosting.co.za
http
R David Murray rdmur...@bitdance.com added the comment:
I use unique passwords for all services for exactly this reason so I, for one,
am not worried.
--
nosy: +r.david.murray
___
PSF Meta Tracker metatrac...@psf.upfronthosting.co.za
R David Murray rdmur...@bitdance.com added the comment:
Oh, I hate web sites that don't take me back to exactly the page I was on after
I log in. -1 on that proposal. We could strip @action's from the URL, though,
that would make sense.
--
nosy: +r.david.murray
R David Murray rdmur...@bitdance.com added the comment:
Fixed in r88947. The xapian find function was only returning the first 10
results, and many of *those* got filtered out because they were inside file
objects, which we don't include in search results by default.
Interestingly, although
New submission from R David Murray rdmur...@bitdance.com:
I tried a few keywords that I know appear in issues, and get no results.
--
messages: 2405
nosy: r.david.murray
priority: critical
status: unread
title: The quick search appears to be broken
R David Murray rdmur...@bitdance.com added the comment:
Actually, it is text search that is broken. It doesn't work from the advanced
search either.
--
status: unread - chatting
___
PSF Meta Tracker metatrac
R David Murray rdmur...@bitdance.com added the comment:
Hmm. Maybe there's some sort of index rebuild going on that hasn't finished
yet?
Originally I tried 'test_queue' and 'os'. os obviously should get lots of
hits. I got none for both. I just tried it again now, and I get one hit
R David Murray rdmur...@bitdance.com added the comment:
Here I decided to use the roundup version.
Why? Absent further context I would assume that Martin added that try/except
to fix a bug. If upstream has since fixed it differently, leaving Martin's
code in place should be a noop, whereas
R David Murray rdmur...@bitdance.com added the comment:
No. Your example of launchpad proves that this is a widely applicable feature.
So I agree with Ezio, this feature request belongs upstream.
--
nosy: +r.david.murray
status: chatting - resolved
R David Murray rdmur...@bitdance.com added the comment:
1.4.10
--
nosy: +r.david.murray
___
PSF Meta Tracker metatrac...@psf.upfronthosting.co.za
http://psf.upfronthosting.co.za/roundup/meta/issue406
R David Murray rdmur...@bitdance.com added the comment:
+1 for moving the remove button to the message page. I think I've used it
accidentally more often than I've used it intentionally.
--
nosy: +r.david.murray
___
PSF Meta Tracker
R David Murray rdmur...@bitdance.com added the comment:
The error message is perfectly clear. Roundup rejected the message because it
didn't find the MIME headers. It should accept the message in that case, since
if there are no MIME headers it must by RFC be plain ascii text. My mailer
R David Murray rdmur...@bitdance.com added the comment:
Even if it did, that would have zero effect on this issue.
Personally, I'd rather deal with the occasional lost text when someone is doing
an email reply than to deal with the reams of quoted text resulting from top
post replies. I deal
R David Murray rdmur...@bitdance.com added the comment:
Follow the 'tracker development' link in the left hand column of
bugs.python.org.
--
nosy: +r.david.murray
___
PSF Meta Tracker metatrac...@psf.upfronthosting.co.za
http
R David Murray rdmur...@bitdance.com added the comment:
I disagree that the actions are mostly useless, or even that the 'nosy'
change information is noise. While I don't refer to the action list often, I
do refer to it regularly to answer some question about actions taken on the
issue
R David Murray rdmur...@bitdance.com added the comment:
As long as the information is accessible, I don't really care where it is. I
thought you were advocating getting rid of the nosy update information
altogether.
___
PSF Meta Tracker
R David Murray rdmur...@bitdance.com added the comment:
That would be true of the 'end' button took you to the last message. But it
doesn't, it takes you to the end of the history list.
A better solution would be fold the history list by default, I think. Or
alternatively to interleave
R David Murray rdmur...@bitdance.com added the comment:
I seem to remember that the only way to remove all keywords (ie: remove the
last one) is to select '- no selection -'. I think there might be a bug report
about that, but I'm not sure.
--
nosy: +r.david.murray
77 matches
Mail list logo
