devel July 2019

devel@lists.fedoraproject.org

227 participants
279 discussions

RPM building on s390x sometimes is very slow on F-30+
by Peter Lemenkov 31 Aug '19

31 Aug '19

Hello All, Not sure if it's only me but every time I'm trying to build Erlang on F-30 or Rawhide it takes forever to complete. It's all started relatively recently (maybe a month or two). See the following logs for the example. * https://koji.fedoraproject.org/koji/taskinfo?taskID=36131019 * https://koji.fedoraproject.org/koji/taskinfo?taskID=36131065 (s390x task, two days and still work-in-progress) Does anyone experience the same issue? -- With best regards, Peter Lemenkov.

7 12

Join the new Minimization Team
by Adam Samalik 27 Aug '19

27 Aug '19

Hi everyone! I'm starting a Minimization Objective [1] focusing on minimising the installation size of some of the popular apps, runtimes, and other pieces of software in Fedora. And there is a new Minimization Team [2] forming. Members of the team will consult and work with Fedora maintainers, develop tooling and services, generate reports showing the status of the Fedora ecosystem and a comparison with other ecosystems, etc. The goal is to build an environment where it's easy for our maintainers to keep things small over time, it's not just a one-off effort. Please see the Action Plan [3] for more details. Want to become a member? Let me know! Cheers! Adam [1] https://docs.fedoraproject.org/en-US/minimization/ [2] https://docs.fedoraproject.org/en-US/minimization/team/ [3] https://docs.fedoraproject.org/en-US/minimization/action-plan/ -- Adam Šamalík --------------------------- Senior Software Engineer Red Hat _______________________________________________ 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…

19 49

i686 hw builders running out of ram in cpio?
by DJ Delorie 23 Aug '19

23 Aug '19

Anyone else seeing this? It seems to only happen on physical i686 machines, not vm's, but that's based on only three builds so far. https://koji.fedoraproject.org/koji/taskinfo?taskID=36329825 BUILDSTDERR: create archive failed: cpio: write failed - Cannot allocate memory (this is after the build itself finished, while writing out one of the RPMs) total used free shared buff/cache available Mem: 131924260 899932 105240472 2012 25783856 129959024 Swap: 2097144 2048 2095096 So far this build has failed on: buildhw-04.phx2.fedoraproject.org buildhw-02.phx2.fedoraproject.org but has succeeded on: buildvm-30.phx2.fedoraproject.org

3 3

Lines disordered in mock's build.log
by Miro Hrončok 23 Aug '19

23 Aug '19

Hello, I've noticed that last couple of weeks, I see disordered lines in mock's build.log. This happens constantly in local mock, copr and Koji. Example: 25/41 Test #25: List_test ........................ Passed 0.01 sec Start 26: Particle_test 26/41 Test #26: Particle_test .................... Passed Errors while running CTest make[3]: *** [src/core/unit_tests/CMakeFiles/check_unit_tests.dir/build.make:60: src/core/unit_tests/CMakeFiles/check_unit_tests] Error 8 make[2]: *** [CMakeFiles/Makefile2:2265: src/core/unit_tests/CMakeFiles/check_unit_tests.dir/all] Error 2 make[1]: *** [CMakeFiles/Makefile2:116: CMakeFiles/check.dir/rule] Error 2 make: *** [Makefile:191: check] Error 2 error: Bad exit status from /var/tmp/rpm-tmp.yUtVju (%check) 0.01 sec Start 27: for_each_pair_test ... 41/41 Test #41: Span_test ........................ Passed 0.01 sec 98% tests passed, 1 tests failed out of 41 Total Test time (real) = 16.69 sec The following tests FAILED: 23 - ParticleCache_test (Failed) make[3]: Leaving directory '/builddir/build/BUILD/espresso/openmpi_build' make[2]: Leaving directory '/builddir/build/BUILD/espresso/openmpi_build' make[1]: Leaving directory '/builddir/build/BUILD/espresso/openmpi_build' RPM build errors: Bad exit status from /var/tmp/rpm-tmp.yUtVju (%check) See the "error: Bad exit status from /var/tmp/rpm-tmp.yUtVju (%check)" part in the middle of %check output. Has something changed? Or is it an rpm 4.15 thing? -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok

4 5

Review swaps
by Robert-André Mauchin 20 Aug '19

20 Aug '19

Hello, I'd like some help to review a handful of Golang packages: Review Request: wgctrl - Control of WireGuard interfaces on multiple platforms https://bugzilla.redhat.com/show_bug.cgi?id=1730911 Review Request: golang-github-mattn-ieproxy - Detect the proxy settings on Windows platform https://bugzilla.redhat.com/show_bug.cgi?id=1733160 Review Request: golang-github-google-renameio - Atomically create or replace a file or symbolic link https://bugzilla.redhat.com/show_bug.cgi?id=1733175 Review Request: golang-x-mod - Go module mechanics libraries https://bugzilla.redhat.com/show_bug.cgi?id=1733180 Review Request: golang-github-andybalholm-brotli - Pure Go Brotli encoder and decoder https://bugzilla.redhat.com/show_bug.cgi?id=1733240 Review Request: golang-github-armon-socks5 - SOCKS5 server in Golang https://bugzilla.redhat.com/show_bug.cgi?id=1733229 Review Request: golang-github-xo-dburl - URL style mechanism for parsing and opening SQL database connection strings https://bugzilla.redhat.com/show_bug.cgi?id=1733262 Review Request: golang-github-pierrec-cmdflag - Augment the flag package with commands https://bugzilla.redhat.com/show_bug.cgi?id=1733267 Review Request: golang-xorm-builder - Lightweight and fast SQL builder for Go language https://bugzilla.redhat.com/show_bug.cgi?id=1733280 Review Request: golang-xorm-core - Lightweight & Compatible wrapper of database/sql https://bugzilla.redhat.com/show_bug.cgi?id=1733293 I'm available for any review in exchange. Best regards, Robert-André

3 3

startx unsets DBUS_SESSION_BUS_ADDRESS, which breaks user D-Bus session
by Alexey Rochev 19 Aug '19

19 Aug '19

Hello, I would like to draw some attention to this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1622259. Description: startx unsets DBUS_SESSION_BUS_ADDRESS, which result in launching another D-Bus session which breaks communicating with user systemd services (and any D-Bus services started before launching X) from X session via D-Bus, since they use two different D-Bus daemons. I would really like this bug to be fixed. Thanks, Alexey Rochev

4 8

Updating Rawhide vs GPG keys
by Vít Ondruch 19 Aug '19

19 Aug '19

Hi, Can somebody please enlighten me, how to update Rawhide after branching and not using --nogpgcheck? It seems that Rawhide keys were added in fedora-repos-30-0.4. So this is the package which is still "rawhide" package and has "f31" keys. But this package was not probably signed, because this directory is empty: https://kojipkgs.fedoraproject.org/packages/fedora-repos/30/0.4/data/signed/ Installing anything from Rawhide fails, because of missing GPG keys. So is there a way to get the GPG keys via DNF? Would it be possible to sign fedora-repos and fedora-release packages by older key to allow smooth updates? Vít

8 19

Re: Request for write permission of menu-cache in Fedora
by Zamir SUN 18 Aug '19

18 Aug '19

Ping for updates. I've build menu-cach 1.1.0 in Copr and already tested against LXQt. If you are not willing to grant me write permission, can you build this in EPEL directly? https://copr.fedorainfracloud.org/coprs/zsun/epel7/build/948489/ On 7/15/19 1:58 PM, Zamir SUN wrote: > Ping for updates. > > On Thu, Jul 11, 2019 at 10:59 PM Zamir SUN <sztsian(a)gmail.com> wrote: >> >> Hi Christoph, >> >> I am the current maintainer of Fedora LXQt spin. Recently I am updating >> LXQt in EPEL and I found that I need menu-cache 1.1.0 in EPEL. I filed a >> bug there[1] but no updates. I checked and see only LXQt uses menu-cache >> in EPEL, so can you please grant me write permission of menu-cache, so >> that I can update it in EPEL myself? >> >> Thanks. >> >> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1724495 >> -- >> Zamir SUN >> Fedora user >> GPG : 1D86 6D4A 49CE 4BBD 72CF FCF5 D856 6E11 F2A0 525E -- Zamir SUN Fedora user GPG : 1D86 6D4A 49CE 4BBD 72CF FCF5 D856 6E11 F2A0 525E

1 1

findbugs-contrib building on i686 builders despite ExcludeArch
by Richard Fearn 17 Aug '19

17 Aug '19

Hi, Due to a dependency on Eclipse, findbugs-contrib can no longer be built on non-64-bit architectures. According to https://docs.fedoraproject.org/en-US/packaging-guidelines/#_architecture_bu…: > If a Fedora package does not successfully compile, build or work on an architecture, then those architectures should be listed in the spec in ExcludeArch. So I added ExcludeArch to the findbugs-contrib spec: https://src.fedoraproject.org/rpms/findbugs-contrib/c/35db66939b8d262a6c049… which I based on a similar change for eclipse itself: https://src.fedoraproject.org/rpms/eclipse/c/1b7ea00088e02a126cf0f47777031f… For some reason though, the findbugs-contrib build earlier today for the F31 mass rebuild was done on an i686 builder: https://koji.fedoraproject.org/koji/buildinfo?buildID=1323580 https://koji.fedoraproject.org/koji/taskinfo?taskID=36487003 and failed with an error: BUILDSTDERR: error: Architecture is excluded: i386 The same thing happened with a recent Koschei build: https://koji.fedoraproject.org/koji/taskinfo?taskID=36306707 Have I gone about this the wrong way? Rich -- Richard Fearn richardfearn(a)gmail.com

4 4

bootctl: no entry could be determined as default (Was: Upgrade to F30 gone wrong)
by Dridi Boukelmoune 15 Aug '19

15 Aug '19

On Sun, May 5, 2019 at 1:45 PM Zbigniew Jędrzejewski-Szmek <zbyszek(a)in.waw.pl> wrote: <snip> > This makes the assumption, which was also made earlier in the thread, > that it's somehow impossible to check what bootloader is installed. > Why? My bootloader is happy to tell me its version: > $ bootctl > ... > Current Boot Loader: > Product: systemd-boot 241-565-g43d51bb > Features: ✓ Boot counting > ✓ Menu timeout control > ✓ One-shot menu timeout control > ✓ Default entry control > ✓ One-shot entry control > File: /EFI/systemd/systemd-bootx64.efi > ... > Nowadays it's gives the exact git commit it's built from, in the past > it was just the release version, but either is enough. Therefore > 'bootctl update' can fairly reliably *update*, i.e. do the installation > if the thing we have is newer than the version already installed. That's news to me, and unfortunately it doesn't look as nifty on my system: ... Current Boot Loader: Product: n/a Features: ✗ Boot counting ✗ Menu timeout control ✗ One-shot menu timeout control ✗ Default entry control ✗ One-shot entry control ESP: n/a File: └─n/a Available Boot Loaders on ESP: ESP: /boot/efi (/dev/disk/by-partuuid/$UUID) File: └─/EFI/BOOT/BOOTIA32.EFI File: └─/EFI/BOOT/BOOTX64.EFI Boot Loaders Listed in EFI Variables: Title: Fedora ID: 0x0001 Status: active, boot-order Partition: /dev/disk/by-partuuid/$UUID File: └─/EFI/fedora/shimx64.efi Title: Linux Firmware Updater ID: 0x0000 Status: active, boot-order Partition: /dev/disk/by-partuuid/$UUID File: └─/EFI/fedora/shimx64.efi ... Where $UUID is the same for all three occurrences. Dridi

3 5

← Newer
1
2
3
4
5
6
7
...
28
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 July 2019