devel April 2019

devel@lists.fedoraproject.org

195 participants
311 discussions

Fedora 30 Beta Silverblue Feedback
by Ty Young 05 Apr '19

05 Apr '19

Hi, I didn't see a Silverblue specific mailing list and Fedora 30 is a beta so hopefully this is right. If it isn't, where is the appropriate place? Firstly I'd like to just say that the idea behind Fedora Silverblue is really amazing. My understanding it's more orientated for containers and the like however even for general desktop usage it's incredibly useful as a recovery mechanism from things like bad GPU driver installs. Indeed, after a failed attempt to build the driver using a guide[1] I was left with a broken system on reboot. I then picked the lowest(first) boot ostree boot option from within GRUB and I was back to a usable system with the open source Nvidia drivers. No other Linux distro is capable of doing this as far as i'm aware(or do by default anyway). Question: is the limit of alternative ostree(s) limited to 5? I noticed that after 5 I was reduced back to 2, both with the Nvidia GPU driver. Can that be changed? Is there a way to rename them to automatically rename them so it's more clear what changed? (If you're wondering why I was build the driver it was because I missed the bold text in the guide. Using that instead worked just fine.) However, there are serious issues with Fedora 30 Beta Silverblue(and maybe standard workstation?) with software repositories. On first boot, software center will display software and updates(and even be downloadable and installable) however and error message will popup saying that it can't create/read/writeto a directory(I don't have the specific text, sorry). Software repositories are listed in gnome-software as expected. After rebooting all the software repositories are gone and checking for updates gives the error message saying that packagekit timedout doing a searchbypackagename or something like that. No software repositories show up in gnome software anymore. Gnome-software was very slow as well. There seems to be an issue with Steam(flatpack edition) where it doesn't run at all. It spits out a libGL error saying that: |libGL error: failed to load driver: swrast| even with both 64 and 32 bit drivers installed. Am I missing something here? Flicker free boot only seems to work with the open source drivers... and even then it has some issues. When restarting, graphical glitching can be observed at the top of the screen followed by a brief black screen and then the shutdown animation screen. Booting the system up using the Nvidia driver causes the 3 square images to be misaligned so that it's part way between the top left of the screen and the middle with no Fedora logo which I assume is supposed to be in the middle with a logo... And finally, I don't know who builds the Nvidia driver(probably community like AUR?) for Fedora but could you please stop splitting the standard Nvidia libraries and tools into different packages? I have an OC utility which depends on: nvidia-smi nvidia-settings nvidia-xconfig but only nvidia-settings is included with the standard driver despite both Windows including nvidia-smi and their Windows alternative to nvidia-settings(Nvidia Control Panel) with the driver and Ubuntu including all 3 with the driver. This isn't a case of just someone thinking it's wrong, there is actual precedent showing that it's wrong. In order to get nvidia-smi you need to install the CUDA package and as far as nvidia-xconfig goes it doesn't seem to exist. nvidia-smi isn't exclusively related to CUDA. Including it only with CUDA drivers doesn't make any sense. Please stop doing this. It isn't right. [1] https://blogs.gnome.org/alexl/2019/03/06/nvidia-drivers-in-fedora-silverblu…

4 3

Heads up: OpenColorIO 1.1.1
by Richard Shaw 04 Apr '19

04 Apr '19

There's no soname change and fedabidiff output doesn't look to concerning but I'm no expert there: [C]'method void OpenColorIO::v1::Processor::Impl::addColorSpaceConversion(const OpenColorIO::v1::Config&, const OpenColorIO::v1::ConstContextRcPtr&, const OpenColorIO::v1::ConstColorSpaceRcPtr&, const OpenColorIO::v1::ConstColorSpaceRcPtr&)' at Processor.h:96:1 has some indirect sub-type changes: parameter 2 of type 'const OpenColorIO::v1::ConstContextRcPtr&' has sub-type changes: in referenced type 'const OpenColorIO::v1::ConstContextRcPtr': in unqualified underlying type 'typedef OpenColorIO::v1::ConstContextRcPtr' at OpenColorTypes.h:75:1: underlying type 'class std::tr1::shared_ptr<const OpenColorIO::v1::Context>' at shared_ptr.h:983:1 changed: type size hasn't changed 1 base class deletion: class std::tr1::__shared_ptr<const OpenColorIO::v1::Context, __gnu_cxx::_S_atomic> at shared_ptr.h:539:1 1 base class insertion: class std::tr1::__shared_ptr<const OpenColorIO::v1::Context, (__gnu_cxx::_Lock_policy)2> at shared_ptr.h:539:1 Anything to be concerned about? I can rebuild the dependencies (OpenImageIO, blender, and krita). Thanks, Richard

2 4

luxcorerender failure to build
by Luya Tshimbalanga 04 Apr '19

04 Apr '19

luxcorerender kept on failing despite fulfilling all necessary build requirement. It occurred with slg-core which I vainly try to ignore it as suggested by upstream. Can someone investigate? Here is the scratch build result: https://koji.fedoraproject.org/koji/taskinfo?taskID=33953912 Luya

2 4

Re: Package Naming Guildelines for compat-lua packages
by Robert Scheck 04 Apr '19

04 Apr '19

Hello Tomas, On Thu, 04 Apr 2019, Tomas Krizek wrote: > This makes it difficult to search for lua packages and preferably, there > should be just a single naming scheme. Based on a discussion with > maintainer of lua-lpeg and lua-mpack [2], we've agreed to use the naming > scheme compat-lua-* wouldn't it have been a clever alternative to use lua52-* rather a quite unspecific "compat-lua-" to be really similar with your python2/3 example? Regards, Robert

2 1

Modularity question for packagers about rolling/latest/stable/master streams
by Adam Samalik 04 Apr '19

04 Apr '19

Some modules now use "latest", "stable", or "master" as stream names for various different things. It's quite confusing and I want to fix that. Without naming them, I see two different use cases: 1/ "for end users" — rolling stream meant for end users to consume, likely used in projects without traditional versioning scheme, or for the latest version that the Fedora's "cutting edge but not bleeding edge" 2/ "for hackers/preview" — pre-release or development builds not meant for end users to use in production, but mostly for preview, experiments, or for people who like to live dangerously And I want a distinct name for each of those so people know what they're about to install. The Modularity Team can't agree on this [1], so we'd like to hear from other packagers what they think. So the question is, do people agree there are two? Or just one? Or more? Thanks, Adam [1] https://pagure.io/modularity/issue/128 PS: I know it's not always clear for packager which one to choose — for example with project only having a master branch — but in those cases I'd like to use packagers' best judgement to decide wether they feel its "for users" or "for hackers/preview". I trust Fedora packagers, that's why I use Fedora. And they know the thing they're packaging better than me. We would of course provide guidance that would help decide if necessary. -- Adam Šamalík --------------------------- Senior Software Engineer Red Hat

4 8

Package Naming Guildelines for compat-lua packages
by Tomas Krizek 04 Apr '19

04 Apr '19

(This message is a copy for fedora-devel archival purposes, original message was rejected by mailing list and was only sent to CCed maintainers) Hi, there is no official package naming guideline for lua packages in Fedora [1]. Similarly to python2/python3, there are two version of lua: lua and compat-lua. There is currently inconsistency in the package names for compat-lua packages. Example: compat-lua-lpeg vs. lua-cqueues-compat This makes it difficult to search for lua packages and preferably, there should be just a single naming scheme. Based on a discussion with maintainer of lua-lpeg and lua-mpack [2], we've agreed to use the naming scheme compat-lua-* If you're a maintainer of a lua-*-compat package, please use the new naming scheme along with Provides for backward compatibility [3]. If anyone has the rights to edit Package naming guidelines [1], please document the proper way to name lua and compat-lua packages. Thanks! [1] - https://fedoraproject.org/wiki/Packaging:Naming?rd=Packaging:NamingGuidelin… [2] - https://src.fedoraproject.org/rpms/lua-mpack/pull-request/2 [3] - https://fedoraproject.org/wiki/Packaging:Naming?rd=Packaging:NamingGuidelin… -- Tomas Krizek PGP: 4A8B A48C 2AED 933B D495 C509 A1FB A5F7 EF8C 4869

2 2

LD_LIBRARY_PATH vs rpath and libtool
by Ingvar Hagelund 04 Apr '19

04 Apr '19

Fedora prohibits the use of rpath, ref https://docs.fedoraproject.org/en-US/packaging-guidelines/#_beware_of_rpath When compiling varnish with litbool, I ensure this by the usual sed -i 's|^hardcode_libdir_flag_spec=.*|hardcode_libdir_flag_spec=""|g; s|^runpath_var=LD_RUN_PATH|runpath_var=DIE_RPATH_DIE|g' libtool However, during build and check, I need access to a library in the build. For example, the test suite uses the binary varnishtest to access libvarnishapi.so.2, which is not visible as the package is not installed yet. I have gotten around this by putting in LD_LIBRARY_PATH where I need, but rpmlint gives me a warning on that. Are there other possibilities to solve this? Ingvar

2 4

f28/f29 container composes failure since a while, is it already tracked by an issue ?
by Normand 04 Apr '19

04 Apr '19

In fedora registry (1) we have f30/rawhide containers updated from last compose (2) but f28 last dated 20181007 but f29 last dated 20190218 Probably related to the DOOMED status reported in Container compose (3) Where f28/f29 traceback.global file reports failures. Is there already known issue tracking this Container compose failure ? (1) https://registry.fedoraproject.org/repo/fedora/tags/ (2) https://kojipkgs.fedoraproject.org/compose/branched/latest-Fedora-30/compos… https://kojipkgs.fedoraproject.org/compose/rawhide/latest-Fedora-Rawhide/co… (3) https://kojipkgs.fedoraproject.org/compose/container/Fedora-Container-28-20… https://kojipkgs.fedoraproject.org/compose/container/Fedora-Container-28-20… https://kojipkgs.fedoraproject.org/compose/container/Fedora-Container-29-20… https://kojipkgs.fedoraproject.org/compose/container/Fedora-Container-29-20… -- Michel Normand

2 1

DevConf.IN 2019 Inviting Speakers - CFP Open
by P J P 04 Apr '19

04 Apr '19

Hello, The annual DevConf.IN conference is here again! -> https://devconf.info/in/ We are glad to announce that CFP for DevConf.IN 2019 is now open!! :) Event Dates: 2 - 3 August 2019 Venue: Selection underway - TBA , Bengaluru, KA, India. Important dates -> CFP closes: May 1st, 2019 -> Speaker confirmation: June 1st, 2019 -> Schedule announcement: July 1st, 2019 We cordially invite you to submit a proposal to speak at DevConf.IN 2019. This is the third edition of DevConf.in conference where free and open source software communities and developers meet, learn, and hack on FOSS projects. DevConf.IN 2019 is organised and sponsored by Red Hat Inc. We invite speakers from various backgrounds and roles, including developers, administrators, engineers, DevOps practitioners, quality engineers, technical writers, project managers, and more. If you’re a FOSS project contributor, you’re a potential speaker! While submitting the proposal, you need to choose a theme that the talk/workshop belongs to. Themes for this year are * TRENDING TECH : * AI, Machine Learning, Block Chain, IoT, Mobile. * Storage and Networking * Cloud Native Storage, Software Defined Storage, Storage Management, Distributed file system, datastores, Big Data, NFV/VNF, Fast data path acceleration, OVS/VPP and DPDK, , network debug analysis, Software Defined Networking, OVS offload/full offload, performance benchmarking, NFV * Open Hybrid Cloud * Multi Cloud, Automation, OpenStack, Kubernetes, Serverless, Microservices, Containers, OpenShift/ PaaS, Hybrid Cloud management, Operators, CNI, Virtualization, Kernel, Service mesh * Developer Tools * Container Tooling, CI/CD, DevOps, Code Editors, Cloud native IDE, CLI, Local Development for containers, Language Runtime, Debugging/Tracing, Testing * FOSS Community and Standards * Community Trends, governance, licensing, contribution, Leadership Agile * White Paper/ Academic Research * Computer Science Engineering, New algorithms, Protocols, Experimental/Future networks, Data Modelling, Security, Natural Language Processing-NLP * Design * Security * QE * DevOps * Documentation * Security/Data Privacy These focus areas are the common and integral part of all themes We are looking for talks and workshops which appeal to the beginner, intermediate and advanced participant in community projects. The CFP is NOW OPEN! Ready to submit your proposal? Visit -> http://devconf.in/ Questions? Please write to us at <info(a)devconf.in> Thank you. --- -P J P http://feedmug.com

1 0

Schedule for Thursday's FPC Meeting (2019-04-04 16:00 UTC)
by James Antill 03 Apr '19

03 Apr '19

Following is the list of topics that will be discussed in the FPC meeting Thursday at 2019-04-04 16:00 UTC in #fedora-meeting-1 on irc.freenode.net. Local time information (via. uitime): ================= Day: Thursday ================== 2019-04-04 09:00 PDT US/Pacific 2019-04-04 12:00 EDT --> US/Eastern <-- 2019-04-04 16:00 UTC UTC 2019-04-04 17:00 BST Europe/London 2019-04-04 18:00 CEST Europe/Berlin 2019-04-04 18:00 CEST Europe/Paris 2019-04-04 21:30 IST Asia/Calcutta ---------------- New Day: Friday ----------------- 2019-04-05 00:00 HKT Asia/Hong_Kong 2019-04-05 00:00 +08 Asia/Singapore 2019-04-05 01:00 JST Asia/Tokyo 2019-04-05 02:00 AEST Australia/Brisbane Links to all tickets below can be found at: https://pagure.io/packaging-committee/issues?status=Open&tags=meeting = Followups = #topic #845 Wiki deprecation status .fpc 845 https://pagure.io/packaging-committee/issue/845 #topic #859 Scriptlet to replace a directory: try delete first? .fpc 859 https://pagure.io/packaging-committee/issue/859 = Open Floor = For more complete details, please visit each individual ticket. The report of the agenda items can be found at: https://pagure.io/packaging-committee/issues?status=Open&tags=meeting If you would like to add something to this agenda, you can: * Reply to this e-mail * File a new ticket at: https://pagure.io/packaging-committee * E-mail me directly * 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.

1 0

← Newer
1
...
25
26
27
28
29
30
31
32
Older →

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 2019