Intent to drop support of bodhi-client 0.9 in fedpkg

Hi all, bodhi-client 0.9 is available in EPEL6 currently and other releases have version >=2.0. fedpkg will benefit from this change to leverage new functionalities introduced since bodhi-client 2.0 in a consistent way. As a result, `fedpkg update` will not work in EPEL6. New command to operate o

Re: What is the process for requesting an update to a package?

Στις 22/5/2018 15:37, ο Vít Ondruch έγραψε: Dne 22.5.2018 v 12:21 Georgios Petasis napsal(a): Στις 22/5/2018 11:30, ο Dominik 'Rathann' Mierzejewski έγραψε: On Tuesday, 22 May 2018 at 07:35, Vít Ondruch wrote: Dne 21.5.2018 v 22:59 Petr Šabata napsal(a): On Mon, May 21, 2018 at 11:51:59PM +0

Re: Heads up: selinux-policy-3.14.1-25.fc28 breaks GDM

I got hit with this too on F28 using negativo17's nvidia driver packages.Downgrading selinux-policy-3.14.1-25 / selinux-policy-targeted-3.14.1-25 clears it up.There's a fedora update to -3.14.1-29 pending: https://bodhi.fedoraproject.org/updates/FEDORA-2018-a74875b364 Too bad dnf doesn't allow

Fedora Rawhide-20180524.n.0 compose check report

No missing expected images. Failed openQA tests: 2/137 (x86_64), 2/24 (i386), 1/2 (arm) New failures (same test did not fail in Rawhide-20180520.n.0): ID: 241245 Test: x86_64 Server-boot-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/241245 ID: 241273 Test: x86_64

Re: Heads up: selinux-policy-3.14.1-25.fc28 breaks GDM

On Wed, 2018-05-23 at 20:13 -0600, Jerry James wrote: > [1] Which is totally useless, by the way. It says "Oh no! Something went > wrong!" (Great. *WHAT* went wrong?) and informs me that I must logout. I > wasn't logged in. There's a nice logout button there, but it can't be > pressed. Th

Re: Heads up: selinux-policy-3.14.1-25.fc28 breaks GDM

On Thu, 2018-05-24 at 08:09 -0600, Jerry James wrote: > On Thu, May 24, 2018 at 12:39 AM, Heiko Adams wrote: > > > I can't confirm that. Maybe because I relabel my system after every > > selinux policy update. > > > > As I said in the original message: > > "I did a full SELinux relabel immed

Schedule for Friday's FESCo Meeting (2018-05-25)

Following is the list of topics that will be discussed in the FESCo meeting Friday at 15:00UTC in #fedora-meeting on irc.freenode.net. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/UTCHowto or run: date -d '2018-05-25 15:00 UTC' Links to all issues below

Re: F29 System Wide Change: The tzdata transition to 'vanguard' format

On Wed, May 23, 2018 at 3:23 AM, Florian Weimer wrote: > On 05/22/2018 05:06 PM, Lennart Poettering wrote: > >> The old format was nicely documented in tzfile(5): >> >> http://man7.org/linux/man-pages/man5/tzfile.5.html >> >> Through this it kinda has become API. Which doesn't mean it can't be >>

Re: F29 System Wide Change: The tzdata transition to 'vanguard' format

Hi, I agree that the documentation has been very good. From what I've seen, the upstream maintainer continues to update the documentation as needed. Thanks for your input! Patsy On Tue, May 22, 2018 at 11:06 AM, Lennart Poettering wrote: > On Di, 22.05.18 16:24, Jan Kurik (jku...@redhat.com) w

Re: F29 System Wide Change: The tzdata transition to 'vanguard' format

Hi, Thanks for the question! No, this change should not change the signature at the beginning of the file. My understanding is that it should only impact application provided parsers that read the time zone data files and expect the SAVE/DST values to only be positive. Thanks, Patsy On Tue, Ma

Re: F29 System Wide Change: Move /usr/bin/python into a separate package

On 05/24/2018 01:26 PM, Jason L Tibbitts III wrote: > Is it possible to filter only failures out of the results list? Yeah, you can slap &outcome=failed on the end: > https://taskotron.fedoraproject.org/resultsdb/results?testcases=dist.python-versions.python_usage&outcome=failed _

Re: F29 System Wide Change: The tzdata transition to 'vanguard' format

Hi, Thank you for your input on this! The concern is that, in some cases, applications that parse the tzdata files were not expecting to find negative DST offsets (negative SAVE values in the data files) despite the fact that POSIX appears to support this. As this is now the default format for t

Re: F29 System Wide Change: Move /usr/bin/python into a separate package

> "RB" == Randy Barlow writes: RB> https://taskotron.fedoraproject.org/resultsdb/results?testcases=dist.python-versions.python_usage This one seems on-point. rpm 4.14.1-9.fc28 fails: https://taskotron.fedoraproject.org/resultsdb/results/21327930 Is it possible to filter only failures out

Re: F29 System Wide Change: Move /usr/bin/python into a separate package

On 05/24/2018 12:45 PM, Jason L Tibbitts III wrote: > Could you fill us in a bit? The only thing I know about resultsdb is > that there is a thing called resultsdb. I went to > https://taskotron.fedoraproject.org/resultsdb/results but I have no idea > how to find, say, all packages which call /us

Re: F29 System Wide Change: Move /usr/bin/python into a separate package

> "RB" == Randy Barlow writes: RB> I don't disagree, but I will point out that it is possible to find RB> out which packages are using /usr/bin/python by looking at their RB> most recent test results in resultsdb. Could you fill us in a bit? The only thing I know about resultsdb is that the

May 2018 Elections: Nomination period for FESCo has been prolonged till May 31st @ 23:59:59 UTC

Hi Fellowship of Fedora, as we have not reach the minimal number of nominees to FESCo required by FESCo election policy [1], to get ready for voting, FESCo has decided to prolong the nomination period for one week. As such, the Nomination period has been re-opened until May 31st @ 23:59:59 UTC. Ti

Re: Heads up: selinux-policy-3.14.1-25.fc28 breaks GDM

On 2018-05-24 10:09, Jerry James wrote: The problem may be restricted to systems using the Nvidia proprietary driver. I have that driver and was also affected, though am using sddm rather than gdm.  My work around was the following local policy: ~~~ module local_sddm 1.0; require {    

Re: F29 System Wide Change: Move /usr/bin/python into a separate package

On 05/23/2018 01:22 PM, Jason L Tibbitts III wrote: > it is now easier to see what actually calls "/usr/bin/python" in > contravention of the packaging guidelines. I don't disagree, but I will point out that it is possible to find out which packages are using /usr/bin/python by looking at their mo

Re: I would like to propose that we turn on XFS Reflink in Fedora 29 by default

Late and off-topic by now, but in retrospect my response is closer to stupid than the intended hyperbolic+funny. On Wed, May 2, 2018 at 3:21 PM, Chris Murphy wrote: > On Wed, May 2, 2018 at 7:07 AM, Martin Kolman wrote: >> What about putting it on top of a thin-LV then ? With over provisioning

[Test-Announce] Fedora 29 Rawhide 20180524.n.0 nightly compose nominated for testing

Announcing the creation of a new nightly release validation test event for Fedora 29 Rawhide 20180524.n.0. Please help run some tests for this nightly compose if you have time. For more information on nightly release validation testing, see: https://fedoraproject.org/wiki

Re: Heads up: selinux-policy-3.14.1-25.fc28 breaks GDM

On 05/24/2018 04:09 PM, Jerry James wrote: > On Thu, May 24, 2018 at 12:39 AM, Heiko Adams > wrote: > > I can't confirm that. Maybe because I relabel my system after every > selinux policy update. > > > As I said in the original message: > >   "I did a full

Re: Heads up: selinux-policy-3.14.1-25.fc28 breaks GDM

On Thu, May 24, 2018 at 12:39 AM, Heiko Adams wrote: > I can't confirm that. Maybe because I relabel my system after every > selinux policy update. > As I said in the original message: "I did a full SELinux relabel immediately afterwards. Nothing relevant changed labels." Now that I'm at wo

Re: F29 System Wide Change: Move /usr/bin/python into a separate package

On 05/24/18 01:01, Miro Hrončok wrote: On 24.5.2018 00:56, Adam Williamson wrote: The thing you're missing - which the Change doesn't explicitly state, so it's understandable - is the effect of having the python2 package Recommend the package with /usr/bin/python in it. For *user* systems tha

Re: F29 System Wide Change: Move /usr/bin/python into a separate package

On 05/24/18 02:21, Orcan Ogetbil wrote: On 23 May 2018 at 11:30, Brian C. Lane wrote: as a user of python what do you expect /usr/bin/pythong to do? You expect it to run the python2 interpreter. Careful with the generalization. I expect /usr/bin/python to launch python3 and I get surprised wit

Re: F29 System Wide Change: Move /usr/bin/python into a separate package

On Thu, 2018-05-24 at 11:38 +0200, Miro Hrončok wrote: > On 24.5.2018 11:27, Thomas Haller wrote: > > A sensible approach for a project to solve this problem is to write > > in > > a python2-and-3 compatible subset. But wbyen discouraging > > "#!/usr/bin/python" it's not generally possible to find

Re: F29 System Wide Change: Move /usr/bin/python into a separate package

On 24.5.2018 11:27, Thomas Haller wrote: A sensible approach for a project to solve this problem is to write in a python2-and-3 compatible subset. But wbyen discouraging "#!/usr/bin/python" it's not generally possible to find a suitable interpreter. This is true for upstream projects. We are ta

Re: F29 System Wide Change: Move /usr/bin/python into a separate package

On Wed, 2018-05-23 at 08:30 -0700, Brian C. Lane wrote: > On Wed, May 23, 2018 at 02:55:40PM +0200, Jan Kurik wrote: > > = Proposed System Wide Change: Move /usr/bin/python into a separate > > package = > > https://fedoraproject.org/wiki/Changes/Move_usr_bin_python_into_sep > > arate_package > > >

Re: F29 System Wide Change: Move /usr/bin/python into a separate package

On 24.5.2018 04:30, Chris Adams wrote: Once upon a time, Adam Williamson said: The packager could always just add BuildRequires python-unversioned-command to "fix" the problem, which is probably the fix we don't want them to do, but at least then we have a handy way to identify recalcitrant pac