devel August 2020

devel@lists.fedoraproject.org

217 participants
365 discussions

s390x builder improvements
by Kevin Fenzi 04 Aug '20

04 Aug '20

ok. I did what I could with the resources we have right now to improve things on the s390x builders. 1. I noticed that we had the kvm instances oversubscribed on cpus (the host has 32, we had 42 used). So, I lowered all the kvm builders to 3 vcpus from 4. (Those are 15-24). 2. I moved the varnish package cache from 07 (a z/vm guest) to 24 (a kvm guest). I have noticed the z/vm ones (thats 01-14) seem to suffer from slowdowns or high io wait more under high load and/or over a long time. Hopefully moving that to a more stable instance will help with lots of issues people have seen with not being able to download or the like. 3. I switched the cache model on the kvm ones to unsafe, which we had already used on a number of other builders. I think the worst that can happen here is that the vm becomes corrupt if it's abruptly shutdown or killed, but thats fine, we can just spin up a new one. If a build gets messed up, koji would just restart it again on another vm, etc. 4. There was a misconfiguration in kojid where if the cache was not answering it tried directly, but it was trying the wrong url. I have corrected this, so if the primary cache is down it should fall back to trying directly on it's own. 5. I've updated and rebooted them all. They seem to behave much better after reboots and then slowly get slower over time. ;( I've been watching it for the last hour or so and so far 0 failures that I can attribute to s390x cache or builder infra. Hopefully that should make things more stable. If you see problems cropping up again, please do open an infra ticket and we can see what futher we can do. :) kevin

3 2

Orphaning a bunch of my packages (part 2 of X)
by Raphael Groner 04 Aug '20

04 Aug '20

Hi, unfortunately I have to orphan my packages psi+ (incl. psi as a base where co-maintainer) and trojita as well. psi+ - XMPP client trojita - e-mail client for IMAP Please feel free to pick them if you still think there's any usefulness in Fedora. Both packages didn't get updates since ages because upstream uses strange development models, there are also some open bugs for both packages. Regards Raphael

3 5

Fedora 33 Mass Rebuild
by Mohan Boddu 04 Aug '20

04 Aug '20

Mohan Boddu <mboddu(a)bhujji.com> 4:32 PM (1 hour ago) to devel-announce Hi all, Per the Fedora 33 schedule[1] we will start a mass rebuild for Fedora 33 on Jul 22nd 2020. We will run a mass rebuild for Fedora 33 for the changes listed in: https://pagure.io/releng/issues?status=Open&tags=mass+rebuild Mass rebuild will be done in a side tag (f33-rebuild) and moved over when completed. Failures can be seen https://kojipkgs.fedoraproject.org/mass-rebuild/f33-failures.html Things still needing rebuilt https://kojipkgs.fedoraproject.org/mass-rebuild/f33-need-rebuild.html FTBFS bugs will be filed shortly. Please be sure to let releng know if you see any bugs in the reporting. You can contact releng in #fedora-releng on freenode, by dropping an email to our list[2] or filing an issue in pagure[3] Regards, Mohan Boddu. [1] https://fedorapeople.org/groups/schedule/f-33/f-33-key-tasks.html [2] https://lists.fedoraproject.org/admin/lists/rel-eng.lists.fedoraproject.org/ [3] https://pagure.io/releng/ _______________________________________________ devel-announce mailing list -- devel-announce(a)lists.fedoraproject.org To unsubscribe send an email to devel-announce-leave(a)lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedorapr…

17 31

Re: [retitled] Fedora wiki and code tags
by Alessio 04 Aug '20

04 Aug '20

On Aug 4, 2020 8:31 AM, "John M. Harris Jr" <johnmh(a)splentity.com> wrote: > > That somebody doesn't like something doesn't mean that they don't respect > those who made it. Ok. Maybe we are going OT. But excuse me John: words matter. Saying "it sucks" is not equal to "I don't like it". A.

1 0

Need a package review (aml)
by Bob Hepple 04 Aug '20

04 Aug '20

Hi, The upstream author of wayvnc (a VNC server for Wayland) has split some code out into a separate tiny package (aml) for which I'm waiting to get a review request done, since 28th July. I'm blocked from packaging the new release wayvnc-0.2.0 until that one is done and I need to get that new version out as it has a fix for the FTBFS errors on rawhide/f33. Sorry if this is the wrong place to ask for this - I see people offering review swaps but I don't think I'm authorised to do reviews. Anyways, if anyone can do me a review, I'll be ever grateful. It's a very small, simple package. The bugzilla is here: https://bugzilla.redhat.com/show_bug.cgi?id=1861216 Thanks Bob

1 1

Fedora 33 System-Wide Change proposal: CMake to do out-of-source builds
by Ben Cotton 04 Aug '20

04 Aug '20

https://fedoraproject.org/wiki/Changes/CMake_to_do_out-of-source_builds == Summary == <code>%cmake</code> macro will be adjusted (<code>-B</code> parameter) to use separate build folder (already standardized <code>%{_vpath_builddir}</code> macro). Additionally, <code>%cmake_build</code>, <code>%cmake_install</code> and <code>%ctest</code> macro will be created (and backported to the older supported Fedora releases) to perform various operations that are commonly used with CMake in a backend-agnostic (Makefiles, Ninja, etc.) way. Packages that will stop building are trivial to fix and will be adjusted either by maintainers or change owners. == Owner == * Name: [[User:ignatenkobrain|Igor Raits]], [[User:besser82|Björn Esser]], [[User:ngompa|Neal Gompa]] * Email: ignatenkobrain(a)fedoraproject.org, besser82(a)fedoraproject.org, ngompa13(a)gmail.com == Detailed Description == Historically, software builds had a singular build configuration and required running the build within the project root. Nowadays, there are many build modes and options that can be configured in projects, different build settings (e.g. compiler flags) / types (release, debug) that can be applied and different tools that can be used to actually execute builds (compilers like gcc/clang, build job schedulers like make/ninja, and so on). Thus, CMake upstream strongly discourages users of doing in-source builds and recommends doing out-of-source builds. From <code>cmake.1</code>: <pre> To maintain a pristine source tree, perform an out-of-source build by using a separate dedicated build tree. An in-source build in which the build tree is placed in the same directory as the source tree is also supported, but discouraged. </pre> The other part of the change is introduction of additional macros is creation of set of macro that can build, install and run tests in a backend-agnostic, vpath-aware (out-of-source, in-source) way. === Migration === ==== <code>%cmake</code> + <code>%(make|ninja)_(build|install)</code> ==== There are multiple paths to complete the migration: * Add <code>-C "%{_vpath_builddir}"</code> to the <code>%(make|ninja)_*</code> * Replace <code>%(make|ninja)_build</code> and <code>%(make|ninja)_install</code> with <code>%cmake_build</code> and <code>%cmake_install</code> respectively * Redefine vpath builddir <code>%global _vpath_builddir .</code> to continue performing in-source builds (and optionally converting to the <code>%cmake_*</code>) Depending on the package, one of these options may be used to adapt to this change. ==== <code>%cmake -B builddir</code> + <code>%(make|ninja)_(build|install) -C builddir</code> ==== No changes are needed. == Benefit to Fedora == * Follow CMake upstream recommendations when building packages * Brings Fedora package builds more in-line with how upstream projects expect them to be built * Improve compatibility with other RPM distributions that already do this * Support backend-agnostic way of building CMake projects == Scope == * Proposal owners: Implement necessary macros, try to build packages that <code>BuildRequires: cmake</code> in a side tag, analyze failures and fix the relevant ones (introduced by this change). * Other developers: While proposal owners will try to fix all affected packages, there might be some cases where package is already FTBFS so the fix can't be performed. Other package maintainers will have to fix the issue themselves after they fix FTBFS. * Release engineering: [https://pagure.io/releng/issue/9524 #9524] * Policies and guidelines: CMake page will be adjusted to mention newly created macros and the documentation about relevant VPATH macros needs to be restructured a bit (they are already documented on the Meson page, they need to be moved to the separate page and referenced both from CMake and Meson page). * Trademark approval: N/A (not needed for this Change) == Upgrade/compatibility impact == Existing packages can (and most likely will) become FTBFS, but proposal owners will fix as many Fedora packages as possible. However fixing third-party packages is not possible and out of scope. Third-party packagers will need to adapt based on the recommendations noted in this Change. == How To Test == # Grab the new cmake RPM from the Koji sidetag (TBC) # Try to build package that uses <code>%cmake</code>, <code>%cmake_build</code>, <code>%cmake_install</code> and <code>%ctest</code> macro == User Experience == The end-users (non-packagers) will not notice any changes. == Dependencies == There are around 1100 RPMs in Fedora that depend on CMake at build-time. All proposal owners are provenpackagers so they are able to commit necessary fixes. No external dependencies. == Contingency Plan == * Contingency mechanism: Proposal owners will adjust macros to not do out-of-source builds by default, but will preserve newly created macro (essentially to bring them to the targeted state of older supported Fedora releases). * Contingency deadline: Beta freeze. * Blocks release? No == Documentation == The only place that needs to be adjusted is packaging guidelines. -- Ben Cotton He / Him / His Senior Program Manager, Fedora & CentOS Stream Red Hat TZ=America/Indiana/Indianapolis

20 54

FTBFS filed incorrectly and linked to the wrong build
by Richard W.M. Jones 03 Aug '20

03 Aug '20

https://bugzilla.redhat.com/show_bug.cgi?id=1865666 links to the latest build, but that's the ELN build (which failed): https://koji.fedoraproject.org/koji/packageinfo?packageID=8391 The latest F33 build did not fail. I believe this bug was filed incorrectly and perhaps the script that files these bugs need updating. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into KVM guests. http://libguestfs.org/virt-v2v

1 0

Planned Outage - koji.fedoraproject.org - 2020-08-05 21:00 UTC
by Kevin Fenzi 03 Aug '20

03 Aug '20

Planned Outage - koji.fedoraproject.org - 2020-08-05 21:00 UTC There will be an outage starting at 2020-08-05 21:00 UTC which will last approximately 3 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2020-08-05 21:00UTC' Reason for outage: We will be upgrading koji to the recent 1.22.0 upstream release, updating builders to the latest kernel and updates, and doing some database vacuuming. Affected Services: koji.fedoraproject.org - the fedoraproject build system Ticket Link: https://pagure.io/fedora-infrastructure/issue/9194 Please join #fedora-admin or #fedora-noc on irc.freenode.net or add comments to the ticket for this outage above. _______________________________________________ devel-announce mailing list -- devel-announce(a)lists.fedoraproject.org To unsubscribe send an email to devel-announce-leave(a)lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedorapr…

1 0

Orphaning fst
by Erich Eickmeyer 03 Aug '20

03 Aug '20

Hello all, fst is a VST bridge for Windows VST plugins for wine only for i686 and hasn't seen a commit since 2011-01-31[1]. With the F33 mass rebuild, the day finally has come where fst is FTBFS due to bit rot. Since there are newer solutions now, such as Carla, that do a good job of bridging, I don't see any reason for this package to be maintained anymore. Honestly, it should probably be retired. [1] https://repo.or.cz/w/fst.git ---- Erich Eickmeyer Fedora Jam Maintainer

1 0

ghc-cryptonite LTO failure on s390x
by Elliott Sales de Andrade 03 Aug '20

03 Aug '20

Hi, The build for ghc-cryptonite failed in the mass rebuild [1] and a later rebuild by me [2], but only on s390x. The failure appears to be LTO related. This doesn't appear to affect many other Haskell packages. (I've found one seemingly-related failure in ghc-haskell-src-exts [3].) Since it's Haskell, I'm using the standard macros that should pass consistent flags, etc., so I'm not sure what more information I can provide. What happens is that ld.gold warns about mixed LTO/non-LTO: [ 1 of 131] Compiling Crypto.Cipher.DES.Primitive ( Crypto/Cipher/DES/Primitive.hs, dist/build/Crypto/Cipher/DES/Primitive.p_o ) /usr/bin/ld.gold: warning: incremental linking of LTO and non-LTO objects; using -flinker-output=nolto-rel which will bypass whole program optimization and then errors out because of many LTO mismatches like: /tmp/ghc794663_0/ghc_19.c:11:19: error: warning: type of ‘cryptonitezm0zi26zmIKFu0XykBrR53imeIPM2Uw_CryptoziCipherziDESziPrimitive_CAFs_cc’ does not match original declaration [-Wlto-type-mismatch] 11 | extern CostCentre cryptonitezm0zi26zmIKFu0XykBrR53imeIPM2Uw_CryptoziCipherziDESziPrimitive_CAFs_cc[]; | ^ | 11 | extern CostCentre cryptonitezm0zi26zmIKFu0XykBrR53imeIPM2Uw_CryptoziCipherziDESziPrimitive_CAFs_cc[]; | ^ /tmp/ghc794663_0/ghc_18.hc:44:9: error: note: type ‘StgWord’ should match type ‘struct CostCentre’ 44 | StgWord cryptonitezm0zi26zmIKFu0XykBrR53imeIPM2Uw_CryptoziCipherziDESziPrimitive_CAFs_cc[]__attribute__((aligned(8)))= { | ^ | 44 | StgWord cryptonitezm0zi26zmIKFu0XykBrR53imeIPM2Uw_CryptoziCipherziDESziPrimitive_CAFs_cc[]__attribute__((aligned(8)))= { | ^ /tmp/ghc794663_0/ghc_18.hc:44:9: error: note: ‘cryptonitezm0zi26zmIKFu0XykBrR53imeIPM2Uw_CryptoziCipherziDESziPrimitive_CAFs_cc’ was previously declared here | 44 | StgWord cryptonitezm0zi26zmIKFu0XykBrR53imeIPM2Uw_CryptoziCipherziDESziPrimitive_CAFs_cc[]__attribute__((aligned(8)))= { | ^ /tmp/ghc794663_0/ghc_18.hc:44:9: error: note: code may be misoptimized unless ‘-fno-strict-aliasing’ is used | 44 | StgWord cryptonitezm0zi26zmIKFu0XykBrR53imeIPM2Uw_CryptoziCipherziDESziPrimitive_CAFs_cc[]__attribute__((aligned(8)))= { | ^ followed by inlining failures: /usr/include/bits/string_fortified.h: In function ‘fill_segment’: /usr/include/bits/string_fortified.h:59:1: error: error: inlining failed in call to ‘always_inline’ ‘memset’: function body can be overwritten at link time 59 | __NTH (memset (void *__dest, int __ch, size_t __len)) | ^ | 59 | __NTH (memset (void *__dest, int __ch, size_t __len)) | ^ [1] https://koji.fedoraproject.org/koji/taskinfo?taskID=47957210 [2] https://koji.fedoraproject.org/koji/taskinfo?taskID=48408236 [3] https://koji.fedoraproject.org/koji/taskinfo?taskID=48322376 -- Elliott

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

devel August 2020