From metatracker at psf.upfronthosting.co.za  Sun May 20 06:23:16 2018
From: metatracker at psf.upfronthosting.co.za (Ronald Oussoren)
Date: Sun, 20 May 2018 10:23:16 +0000
Subject: [Tracker-discuss] [issue647] bpo google auth not working
In-Reply-To: <1521113275.57.0.467229070634.issue647@psf.upfronthosting.co.za>
Message-ID: <1526811796.92.0.682650639539.issue647@psf.upfronthosting.co.za>


Ronald Oussoren <ronaldoussoren at mac.com> added the comment:

I have a simular problem: the login through Google errors out for me with the following message in the BPO interface: There is already an account for ronaldoussoren at mac.com

----------
nosy: +ronaldoussoren
status: unread -> chatting

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue647>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Mon May 28 10:47:17 2018
From: metatracker at psf.upfronthosting.co.za (Yen Chi Hsuan)
Date: Mon, 28 May 2018 14:47:17 +0000
Subject: [Tracker-discuss] [issue541] hotmail thinks bugs.python.org is a
 spam IP
In-Reply-To: <1398197683.07.0.858405889619.issue541@psf.upfronthosting.co.za>
Message-ID: <1527518837.75.0.682650639539.issue541@psf.upfronthosting.co.za>


Yen Chi Hsuan <yan12125 at gmail.com> added the comment:

I believe issue553 is a superseder for this ticket.

----------
nosy: +yan12125
status: unread -> chatting

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue541>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Mon May 28 10:48:35 2018
From: metatracker at psf.upfronthosting.co.za (Yen Chi Hsuan)
Date: Mon, 28 May 2018 14:48:35 +0000
Subject: [Tracker-discuss] [issue553] SMTP server blacklisted?
In-Reply-To: <1412087765.78.0.141739113985.issue553@psf.upfronthosting.co.za>
Message-ID: <1527518915.44.0.682650639539.issue553@psf.upfronthosting.co.za>


Yen Chi Hsuan <yan12125 at gmail.com> added the comment:

>From msg2857:

> A theory about the fact that we are getting classified as a spammer: when an email is received from an unknown address, roundup send back a reply that you have to register to post.  Since spammers use fake addresses, the victim of the spammer gets that message...and marks it as spam.

That sounds reasonable. Is it possible to configure b.p.o to fix that?

----------
nosy: +yan12125
status: unread -> chatting

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue553>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu May 31 20:41:57 2018
From: metatracker at psf.upfronthosting.co.za (John Rouillard)
Date: Fri, 01 Jun 2018 00:41:57 +0000
Subject: [Tracker-discuss] [issue644] 'Random Issue' Button isn't working
In-Reply-To: <1508803113.44.0.213398074469.issue644@psf.upfronthosting.co.za>
Message-ID: <1527813717.57.0.682650639539.issue644@psf.upfronthosting.co.za>


John Rouillard <rouilj+psf at cs.umb.edu> added the comment:

Hi all:

I took another look at this. I suggest replacing the current class
with:
class RandomIssueAction2(Action):
    def handle(self):
        """Redirect to a random open issue."""
        issue = self.context['context']
        # use issue._klass to get a list of ids, and not a list of instances    
        issue_ids = issue._klass.filter(None, {'status': '1'})
        random.seed()
        url = self.db.config.TRACKER_WEB + 'issue' + random.choice(issue_ids)
        raise Redirect(url)

two changes, the addition of the random.seed() call and change {'status': 1}
to {'status': '1'}. This works for my trackers. If I use the original
{'status': 1} value I get no id's back. The addition of the seed makes the
randomness return.

Also note that this function will throw a traceback if there are no issues
matching the reference criteria. Adding a try/catch or checking the size of
the issue_ids list is left as an exercise for the reader 8-).

-- rouilj

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue644>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu May 31 21:03:11 2018
From: metatracker at psf.upfronthosting.co.za (John Rouillard)
Date: Fri, 01 Jun 2018 01:03:11 +0000
Subject: [Tracker-discuss] [issue603] update the SSL certificate
In-Reply-To: <1470182862.63.0.941603312183.issue603@psf.upfronthosting.co.za>
Message-ID: <1527814991.42.0.682650639539.issue603@psf.upfronthosting.co.za>


John Rouillard <rouilj+psf at cs.umb.edu> added the comment:

r.david.murray said:

> I don't understand the 'cert expires' part, it was renewed in September of 2015.

You probably know this now but the cert may use an md5 signature which is not recommended for longer lived certs (e.g. post 2015).Sha1 is the preferred signature mode to prevent people from generating a fake cert that matches the md5 signature.

I would say let's encrypt works for certs. While we are at it could you add a subject alt name for issues.roundup-tracker.org so we can change that to https.

----------
nosy: +rouilj

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue603>
_______________________________________________________