Just a reminder that builds are currently running for python2 and python3 that
change the meaning of /usr/bin/python from Python 2 to Python 3 in rawhide.
For details, see https://fedoraproject.org/wiki/Changes/Python_means_Python3
I'll be sending e-mails later to package owners who still depend on
/usr/bin/python or who have other tools in /usr/bin/ that should be switched over.
In case of trouble, block the tracker bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1729593
Thanks,
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
Dear all,
You are kindly invited to the meeting:
Modularity Team (weekly) on 2019-07-30 from 15:00:00 to 16:00:00 UTC
At fedora-meeting-3(a)irc.freenode.net
The meeting will be about:
Meeting of the Modularity Team.
More information available at: [Modularity Team Docs](https://docs.pagure.org/modularity/)
The agenda for the meeting is available as flagged tickets [in the Modularity repository](https://pagure.io/modularity/issues?status=Open&tags=Meeting).
Source: https://apps.fedoraproject.org/calendar/meeting/9480/
Some of you may already be aware of the Prioritized Bugs and Issues
process[1] in Fedora. For those who aren't or have forgotten, I wanted
to bring it to your attention. This is a way to highlight important
bugs that aren't blockers, but are high-impact or high-visibility.
Anyone may nominate a bug and weigh in during the fortnightly review
meetings[2]. Bugs that are accepted as Prioritized Bugs get the
benefit of having mattdm coax the appropriate people to move them to
the top of the stack.
[1] https://fedoraproject.org/wiki/Fedora_Program_Management/Prioritized_bugs_a…
[2] https://apps.fedoraproject.org/calendar/meeting/9564/
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
Following is the list of topics that will be discussed in the
FESCo meeting Monday at 15:00UTC in #fedora-meeting-1 on
irc.freenode.net.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/UTCHowto
or run:
date -d '2019-07-29 15:00 UTC'
Links to all issues to be discussed can be found at:
https://pagure.io/fesco/report/meeting_agenda
= New business =
#topic #2179 python27 exception request for ptxdist
https://pagure.io/fesco/issue/2179
= Open Floor =
For more complete details, please visit each individual
issue. The report of the agenda items can be found at
https://pagure.io/fesco/report/meeting_agenda
If you would like to add something to this agenda, you can
reply to this e-mail, file a new issue at
https://pagure.io/fesco, e-mail me directly, or bring it
up at the end of the meeting, during the open floor topic. Note
that added topics may be deferred until the following meeting.
Hello,
I'm getting hundreds of ABRT bugs from tracker which I simply have no
time to go through. Would anybody like to take over that package from
me?
I'll orphan it next weekend if nobody speaks up. Sorry for inconvenience.
I have a number of packages which use %postgresql_tests_run to start
a postgres server in %check and they all seem to have failed during
the mass rebuild, for example:
http://koji.fedoraproject.org/koji/buildinfo?buildID=1331249http://koji.fedoraproject.org/koji/buildinfo?buildID=1331278
The failure is in %postgresql_tests_run when, after it has started
the server it tries to create a database:
+ createdb -h /tmp mockbuild --owner mockbuild -p 36884
BUILDSTDERR: createdb: could not connect to database template1: FATAL:
Peer authentication failed for user "mockbuild"
That basically means that createdb connected to the server using a
unix domain socket but the server didn't see the credentials on the
socket identifying the remote party as mockbuild correctly.
This is only happening on ppc64le so I'm guessing at some sort of
kernel problem on the ppc64le builders unless somebody has another
suggestion as to what is going on?
Tom
--
Tom Hughes (tom(a)compton.nu)
http://compton.nu/