devel April 2018

devel@lists.fedoraproject.org

177 participants
260 discussions

Re: Serious problem with SATA LPM in F28 on Lenovo 50 series laptops
by Hans de Goede 31 May '18

31 May '18

Hi, On 29-04-18 09:25, Hans de Goede wrote: > Hi All, > > I'm sending this to the fedora-kernel and -devel lists > both to get the kernel team aware of this and because it > is not entirely clear to me how to best deal with this. > > I guess we should get this added to the release-notes / > common-bugs page for F28, but I'm not sure what the > procedure is for that ? > > I've just become aware that at least for some users > the use of SATA LPM in F28 causes the Lenovo 50 > series laptops (confirmed X250, T450s G50-80) freeze/ > hang hard under certain conditions when using SATA > LPM, independent of the disk used (*). > > This is currently being tracked in: > https://bugzilla.redhat.com/show_bug.cgi?id=1571330 > > A known workaround is to add: "ahci.mobile_lpm_policy=0" > to the kernel boot command line. > > Can someone help me to get this documented? Once we've > figured out what is going on I hope to be able to fix this > with a kernel update, but people may still need the > workaround to install Fedora 28. > > Also if people are using Fedora 28 on a 50 series Lenovo > laptop without issues, please let me know. Some more info on this, the user with a x250 is reporting the problem is hard-freeze about once a day, which goes away when disabling LPM, so if you have a 50 series Lenovo laptop and are seeing the occasional hard-freeze this may be the cause. Regards, Hans

6 17

Avoiding Jargon: dist-git
by Christopher 29 May '18

29 May '18

Can we stop saying "dist-git" in our docs? Nobody knows what that is. The service at https://src.fedoraproject.org is clearly branded as "Fedora Package Sources". Using the jargon "dist-git" in our documentation is simply confusing, since it doesn't match what the service calls itself, and doesn't match any user interface packagers use. As far as I can tell, only people with a deep understanding of Fedora's infrastructure (which does not seem to be most packagers) know what this term means. For example, in https://fedoraproject.org/wiki/Infrastructure/WhatHappenedToPkgdb , instead of saying "Browse to your project on Pagure over Dist-Git (Top Level link)", we should say: "Browse to your project's Package Source repository at https://src.fedoraproject.org" And, instead of saying "How do I request commit access to a dist-git repo?", we should say: "How do I request commit access to a Package Source repository?" Using special/internal/historical jargon, especially when that jargon doesn't correspond to the current packager experience when interacting with these services, only leads to confusion and should be avoided. If we really need to use the term "dist-git" in the wiki, it should at least link to a glossary page that says "Dist-Git: A term which refers to the Fedora Package Sources repository hosting service at https://src.fedoraproject.org built on Pagure (an open source git repository management service)", instead of just assuming everybody seeing the term "dist-git" knows what that term is and where it came from. If we can avoid jargon with this term and other similar terms, it'd be a big help to our documentation. If this seems reasonable, I'd be happy to help start editing some of the wiki pages... but it'd be helpful if everybody maintaining infrastructure documentation was on the same page. Thanks, Christopher

10 15

I would like to propose that we turn on XFS Reflink in Fedora 29 by default
by Daniel Walsh 25 May '18

25 May '18

We are adding some features to container projects for User Namespace support that can take advantage of XFS Reflink. I have talked to some of the XFS Reflink kernel engineers in Red Hat and they have informed me that they believe it is ready to be turned on by default. I am not sure who in Red Hat I should talk to about this? Whether we should turn it on in the installer or in the mkfs.xfs command? Who should I be talking to? To make this happen.

18 26

Recommended way to pass CFLAGS/LDFLAGS through libtool
by Florian Weimer 14 May '18

14 May '18

Is there a recommend way to get libtool to pass through all flags specified in CFLAGS and LDFLAGS unchanged, and have the GCC compiler driver sort out which flags to pass to the compiler/assembler/linker? Thanks, Florian

7 15

What to do when test gating in bodhi fails (no test results found)?
by Fabio Valentini 09 May '18

09 May '18

Hi, I've got two updates sitting in F26 and F27 updates-testing: https://bodhi.fedoraproject.org/updates/FEDORA-2018-c455a245b0 https://bodhi.fedoraproject.org/updates/FEDORA-2018-4d0e13ff51 I can't push either of them to batched or stable (despite them being in -testing for over 10 days now), because "no test results found". Which is really annoying and the error message is ... rather unhelpful, since it just tells me "I can't do this _shrug_", but not how to fix it. I guess this is caused by a bug in one of the involved components? Where can/should I report this issue? How can I fix this (if I can do it myself), or does somebody with more power have to step in to fix this? Thanks, Fabio

10 24

RANT: Packaging is changing too fast and is not well documented
by Richard Shaw 07 May '18

07 May '18

<RANT> So I went to request a new branch of an existing package only to find out fedrepo-req-branch, which hasn't been around that long is already depreceated and the facility brought into fedpkg... so: $ fedpkg request-branch <branch> Could not execute request_branch: The "token" value must be set under the "fedpkg.pagure" section in your "fedpkg" user configuration Ok, so where does that get stored? $ man fedpkg (not in there...) $ vi /usr/share/doc/fedpkg/README (not in there...) I figured out somewhere else that the default config is in /etc/rpkg/fedpkg.conf (In /etc/rpkg? That's intuitive!) but I didn't want to add my token to the site wide config so the search continues... $ rpm -ql fedpkg (pokes around) $ vi /usr/lib/python2.7/site-packages/fedpkg/__main__.py ... def main(): default_user_config_path = os.path.join( os.path.expanduser('~'), '.config', 'rpkg', '%s.conf' % cli_name) ... Found it! Now which token do I need? The one from the src.fedoraproject.org pagure or pagure.io? Oh and the tokens expire all the time and don't seem to have any helper scripts to automate updating of the tokens so I have to remember where they all are and manually edit them every time... </RANT> Not coming from a programming background I found the learning curve pretty steep when I first tried to become a packager, I'm not sure I wouldn't have given up if I had to do it now. Thanks, Richard

10 10

Fedora Workstation and Third-Party Repositories
by David Benoit 06 May '18

06 May '18

Hi all, Regarding the inclusion of the fedora-workstation-repositories package in F28, is there currently a policy in place against including it as a dependency? From what I understand from the recent fedora magazine article <https://fedoramagazine.org/third-party-repositories-fedora/> and the policy wiki page <https://fedoraproject.org/wiki/Workstation/Third_party_software_policies?rd…>, the purpose of distributing the third-party repositories an rpm is to ensure that a user must enable them explicitly. Is there some some preventative measure in place to protect users from the package being pulled in silently as a dependency? If repository-enabling rpms are to become acceptable cases for package submissions, what considerations are being taken to ensure such submissions are tracked and handled similarly? Apologies if this has been addressed before, but I haven't been able to find any documentation on the subject. Thanks, DB

4 5

Status of OwnCloud/NextCloud
by Randy Barlow 02 May '18

02 May '18

Greetings! It seems that OwnCloud and NextCloud might be unmaintained in Fedora. I found that upgrading my F27 box to F28 causes it to be unable to login: https://bugzilla.redhat.com/show_bug.cgi?id=1562949 There are also CVEs open: https://bugzilla.redhat.com/show_bug.cgi?id=1472720 https://bugzilla.redhat.com/show_bug.cgi?id=1451238 Additionally, F27 has an issue that prevents the calendar from working unless you downgrade one package to the F26 version: https://bugzilla.redhat.com/show_bug.cgi?id=1525208 I don't think I have the expertise or time to step in and help, unfortunately, but these issues do seem bad for Fedora's users. If the maintainers no longer have time to maintain them, should we retire them? Is anyone else interested in stepping up to help out?

24 53

libicu upgrade to 61.1 with soname bump in rawhide/F29
by Eike Rathke 02 May '18

02 May '18

Hi, I'm upgrading libicu to 61.1 for rawhide, which as usual comes with a soname bump. I requested a side target f29-icu for the builds, I'll ask Pete Walter (who already did it for 60.1) to help with rebuilding the dependent packages, or another proven packager if he's not available. Eike -- LibreOffice Calc developer. Number formatter stricken i18n transpositionizer. GPG key 0x6A6CD5B765632D3A - 2265 D7F3 A7B0 95CC 3918 630B 6A6C D5B7 6563 2D3A Care about Free Software, support the FSFE https://fsfe.org/support/?erack

3 3

Orphaning schroot package
by Zach Carter 01 May '18

01 May '18

I'm orphaning the schroot package, since I no longer use it or work with it: https://src.fedoraproject.org/rpms/schroot There is currently a serious (crash) bug affecting the package in F28: https://bugzilla.redhat.com/show_bug.cgi?id=1573253 Upstream: https://packages.debian.org/search?keywords=schroot

2 1

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

devel April 2018