On Thu, 4 Feb 2016 at 20:37 Pierre-Yves Chibon <pingou@xxxxxxxxxxxx> wrote:
On Sat, Jan 30, 2016 at 05:16:20AM +0000, Anshu Prateek wrote:
> Hi all,
>
> Â I am Anshu Prateek (@anshprat), a Fedora Infrastructure Apprentice
> Alumni from 2013 [1][2]. I have been a regular user of Fedora since FC3,
> and I love to contribute back whenever possible[3]. My day job is that of
> a devops and tools/platforms developer.
>
> I ve been a passive member after I left, though regularly reading most of
> the emails on the list here. I can now afford some time (and in part
> motivated by
> https://www.hackerearth.com/sprints/open-source-india-hacks-2016/ ) to
> become an active member again.
>
> To start off, I would take a jab at
> https://github.com/fedora-infra/pkgdb2/issues/299
Hi and welcome!
You're welcome to take a stab at this one if you like, I think we should
approach it as follows:
- Write a script to reproduce the problem in prod
- Set-up a local instance of pkgdb2
- Try to reproduce the problem on the local instance using the script from step
1).
If we can't reproduce, then we'll have to think further, check the logs on the
machines and see if we can find more indices of what's going on.
Thanks, will do a local setup and check.
Can't attend the meeting today, will ping you in the irc later tomorrow for any help or other pointers.
Can't attend the meeting today, will ping you in the irc later tomorrow for any help or other pointers.
Pierre
_______________________________________________
infrastructure mailing list
infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
http://lists.fedoraproject.org/admin/lists/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
--
regardsAnshu Prateek
+91.991.610.2967
_______________________________________________ infrastructure mailing list infrastructure@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
