Re: Trying out a unified kernel image

Am 08.08.24 um 13:18 schrieb Vitaly Kuznetsov: Julian Sikorski writes: Am 07.08.24 um 14:32 schrieb Julian Sikorski: Am 06.08.24 um 10:15 schrieb Julian Sikorski: Am 06.08.24 um 09:37 schrieb Vitaly Kuznetsov: Julian Sikorski writes: Am 05.08.24 um 11:07 schrieb Vitaly Kuznetsov

Re: Trying out a unified kernel image

Am 07.08.24 um 14:32 schrieb Julian Sikorski: Am 06.08.24 um 10:15 schrieb Julian Sikorski: Am 06.08.24 um 09:37 schrieb Vitaly Kuznetsov: Julian Sikorski writes: Am 05.08.24 um 11:07 schrieb Vitaly Kuznetsov: Julian Sikorski writes: Hi list, I recently got curious about unified

Re: Trying out a unified kernel image

Am 06.08.24 um 10:15 schrieb Julian Sikorski: Am 06.08.24 um 09:37 schrieb Vitaly Kuznetsov: Julian Sikorski writes: Am 05.08.24 um 11:07 schrieb Vitaly Kuznetsov: Julian Sikorski writes: Hi list, I recently got curious about unified kernel images and what they bring to the table

Re: Trying out a unified kernel image

Am 06.08.24 um 09:37 schrieb Vitaly Kuznetsov: Julian Sikorski writes: Am 05.08.24 um 11:07 schrieb Vitaly Kuznetsov: Julian Sikorski writes: Hi list, I recently got curious about unified kernel images and what they bring to the table. While informing myself about these, the following

Re: Trying out a unified kernel image

Am 05.08.24 um 11:07 schrieb Vitaly Kuznetsov: Julian Sikorski writes: Hi list, I recently got curious about unified kernel images and what they bring to the table. While informing myself about these, the following questions came to mind: - ESP partition size: my laptop has it set at 260 MB

Trying out a unified kernel image

Hi list, I recently got curious about unified kernel images and what they bring to the table. While informing myself about these, the following questions came to mind: - ESP partition size: my laptop has it set at 260 MB by the laptop vendor, my desktop has it at 100 MB. Recommendation is 200

Orphaning lasem

Hi list, I have just orphaned lasem. I have originally picked it up as a dependency of gnome-chemistry-utils and gnumeric, but I have given up maintainership of those packages since I do not use them anymore. Best regards, Julian -- ___ devel mailin

Re: [Java related] packaging Italian ID card middleware

Am 22.07.24 um 22:53 schrieb Kevin Kofler via devel: Julian Sikorski wrote: Germany uses their own implementation too: https://src.fedoraproject.org/rpms/AusweisApp2 To add insult to injury, it requires the use of custom EC curves, which are bound to stop working at any moment: https

Re: [Java related] packaging Italian ID card middleware

Am 19.07.24 um 06:23 schrieb Kevin Kofler via devel: Marián Konček wrote: You will do the others a great service if you use the English language in GitHub commits and READMEs. I doubt this will be used outside of Italy, except perhaps by Italian citizens abroad (like me), who should also under

Re: Does ccache ever help with kernel mock build?

Am 29.06.24 um 23:50 schrieb Julian Sikorski: Am 29.06.24 um 22:02 schrieb Julian Sikorski: Am 19.06.24 um 13:09 schrieb Julian Sikorski: Am 13.02.24 um 18:52 schrieb Julian Sikorski: Am 13.02.24 um 16:16 schrieb Gary Buhrmaster: On Tue, Feb 13, 2024 at 9:52 AM Miroslav Suchý wrote: Dne

Re: Does ccache ever help with kernel mock build?

Am 29.06.24 um 22:02 schrieb Julian Sikorski: Am 19.06.24 um 13:09 schrieb Julian Sikorski: Am 13.02.24 um 18:52 schrieb Julian Sikorski: Am 13.02.24 um 16:16 schrieb Gary Buhrmaster: On Tue, Feb 13, 2024 at 9:52 AM Miroslav Suchý wrote: Dne 13. 02. 24 v 9:08 Julian Sikorski napsal(a

Re: Does ccache ever help with kernel mock build?

Am 19.06.24 um 13:09 schrieb Julian Sikorski: Am 13.02.24 um 18:52 schrieb Julian Sikorski: Am 13.02.24 um 16:16 schrieb Gary Buhrmaster: On Tue, Feb 13, 2024 at 9:52 AM Miroslav Suchý wrote: Dne 13. 02. 24 v 9:08 Julian Sikorski napsal(a): Could this be the reason for ccache not working

Re: Does ccache ever help with kernel mock build?

Am 13.02.24 um 18:52 schrieb Julian Sikorski: Am 13.02.24 um 16:16 schrieb Gary Buhrmaster: On Tue, Feb 13, 2024 at 9:52 AM Miroslav Suchý wrote: Dne 13. 02. 24 v 9:08 Julian Sikorski napsal(a): Could this be the reason for ccache not working? I wonder whether it is Mock problem, Ccache

Changing desktop file name in a stable release

Hi list, are there guidelines advising how to handle upstream desktop filename change in a stable fedora release? For gnumeric I just followed upstream [1], which led to a bug report [2]. Now I am facing similar situation with pavucontrol [3]. Should I rename the desktop file to what it used

XDG_BASE_DIRECTORY specification

Hello, I recently received a PR against mame, adding support for XDG_CONFIG_HOME, XDG_STATE_HOME and XDG_DATA_HOME [1]. It appears that these folders are not defined by default in Fedora, at least not in Gnome. Is this expected? If it is something which needs to be defined by the user regardl

Re: Is there a policy for branches being merged or not

Am 28.04.24 um 23:44 schrieb Kevin Kofler via devel: Julian Sikorski wrote: In this case defaulting to cherry-picking would be a safer bet. Branches unintentionally separated can be merged, but branches unintentionally merged cannot be unmerged. This is only true if you are talking about

Re: Is there a policy for branches being merged or not

Am 28.04.24 um 10:36 schrieb Peter Robinson: On Sun, 28 Apr 2024, 09:28 Julian Sikorski, <mailto:beleg...@gmail.com>> wrote: Hello, is there a general recommendation regarding keeping git release branches separate vs merged? I have been keeping mine separate. Orig

Is there a policy for branches being merged or not

Hello, is there a general recommendation regarding keeping git release branches separate vs merged? I have been keeping mine separate. Originally to avoid release and changelog conflicts when cherry-picking, but I got used to it and kept doing it after converting to %autorelase and %autochang

how to do minor bump using %autorelease?

Hello, I need to rebuild mame on F40 only for qt-6.7. On rawhide, mame-0.265-1.fc41 is already built against it so I only need to build mame-0.265-1.fc40.1. Can it be done using %autorelease? Best regards, Julian -- ___ devel mailing list -- devel@l

Re: Does ccache ever help with kernel mock build?

Am 13.02.24 um 16:16 schrieb Gary Buhrmaster: On Tue, Feb 13, 2024 at 9:52 AM Miroslav Suchý wrote: Dne 13. 02. 24 v 9:08 Julian Sikorski napsal(a): Could this be the reason for ccache not working? I wonder whether it is Mock problem, Ccache issue or problem in packaging? Does the ccache

Re: Does ccache ever help with kernel mock build?

Am 12.02.24 um 23:01 schrieb Julian Sikorski: Am 12.02.24 um 22:10 schrieb Miroslav Suchý: Dne 12. 02. 24 v 19:29 Julian Sikorski napsal(a): Hello, has anyone successfully managed to get ccache to speed up kernel mockbuilds, be it SRPMS from kernel-ark or from dist-git? I gave it a brief

Re: Does ccache ever help with kernel mock build?

Am 12.02.24 um 22:10 schrieb Miroslav Suchý: Dne 12. 02. 24 v 19:29 Julian Sikorski napsal(a): Hello, has anyone successfully managed to get ccache to speed up kernel mockbuilds, be it SRPMS from kernel-ark or from dist-git? I gave it a brief shot but saw no difference, if anything the build

Does ccache ever help with kernel mock build?

Hello, has anyone successfully managed to get ccache to speed up kernel mockbuilds, be it SRPMS from kernel-ark or from dist-git? I gave it a brief shot but saw no difference, if anything the build was slower. The machine I am building on has 32 GB RAM which is not quite enough to fit everythi

Re: Bisecting an older kernel

Am 12.02.24 um 10:03 schrieb Michael J Gruber: Am So., 11. Feb. 2024 um 23:14 Uhr schrieb Julian Sikorski : Hello, I am trying to bisect an issue which appears to have regressed between 5.18 final and 5.19-rc2. This is somewhat challenging as most of the kernels are since gone from koji, and

Bisecting an older kernel

Hello, I am trying to bisect an issue which appears to have regressed between 5.18 final and 5.19-rc2. This is somewhat challenging as most of the kernels are since gone from koji, and the ark os-build branch seems to have been rebased after kernel 6.7 release, meaning that the required commi

GCC 14 error for asio

Hello, asio started failing to build with gcc-14 [1]. The error is: make[2]: Entering directory '/builddir/build/BUILD/asio-1.28.1/src/examples/cpp14' g++ -DPACKAGE_NAME=\"asio\" -DPACKAGE_TARNAME=\"asio\" -DPACKAGE_VERSION=\"1.28.1\" -DPACKAGE_STRING=\"asio\ 1.28.1\" -DPACKAGE_BUGREPORT=\"\"

Re: AusweisApp2 build failed on rawhide/x86_64 (unsupported reloc 43)

Am 20.01.24 um 14:47 schrieb Fabio Valentini: On Sat, Jan 20, 2024 at 2:41 PM Jakub Jelinek wrote: On Sat, Jan 20, 2024 at 02:27:58PM +0100, Julian Sikorski wrote: AusweisApp2-2.0.3 build failed on rawhide/x86_64 with unsupported reloc 43 errors [1]. Other architectures have built fine

AusweisApp2 build failed on rawhide/x86_64 (unsupported reloc 43)

Hello, AusweisApp2-2.0.3 build failed on rawhide/x86_64 with unsupported reloc 43 errors [1]. Other architectures have built fine, similarly to released branches. Is this a problem with rawhide ld.gold? Best regards, Julian [1] https://koji.fedoraproject.org/koji/taskinfo?taskID=112033714 --

Is packager dashboard supposed to contain up-to-date bugs?

Hello, In my packager dashboard there are six AusweisApp2 bugs listed, all of them are actually resolved. The bugs currently open are not listed either. Is this a known problem? Best regards, Julian -- ___ devel mailing list -- devel@lists.fedorapro

Orphaning gnome-chemistry-utils, bodr and chemical-mime-data and stepping down as goffice and gnumeric co-maintainer

Hi list, as I have not used gnome-chemistry-utils myself in years, I have decided to finally orphan it. While upstream is dead since the lead developer has retired from professional life, the package has been relatively easy to keep running. The only issue is the versioned gnumeric plugin, me

Taking over AusweisApp2 ownership

Hi list, I am going to take over AusweisApp2, which has recently been orphaned. While the app does not work with the openssl shipped by fedora using the default settings currently, we are working with openssl maintainer to fix that. Additionally, using phone to enter pin is a viable workaround

Re: Unretiring keepass

Am 21.11.23 um 10:56 schrieb Julian Sikorski: Hi list, as the CVE (which was not even a problem with keepass in the first place) leading to keepass retirement has been resolved in the meantime, I would like to unretire the package. I have submitted a re-review already: https

Re: Unretiring keepass

Am 23.11.23 um 14:48 schrieb Sandro: On 21-11-2023 10:56, Julian Sikorski wrote: as the CVE (which was not even a problem with keepass in the first place) leading to keepass retirement has been resolved in the meantime, I would like to unretire the package. I have submitted a re-review

Unretiring keepass

Hi list, as the CVE (which was not even a problem with keepass in the first place) leading to keepass retirement has been resolved in the meantime, I would like to unretire the package. I have submitted a re-review already: https://bugzilla.redhat.com/show_bug.cgi?id=2250816 Best regards, Ju

Re: Wrong branch built into side tags, what to do?

Am 06.11.23 um 18:32 schrieb Fabio Valentini: On Mon, Nov 6, 2023 at 6:28 PM Julian Sikorski wrote: Am 06.11.23 um 17:17 schrieb Michael J Gruber: Am Mo., 6. Nov. 2023 um 17:12 Uhr schrieb Fabio Valentini mailto:decatho...@gmail.com>>: On Mon, Nov 6, 2023 at 5:09 PM Julian Si

Re: Wrong branch built into side tags, what to do?

Am 06.11.23 um 17:17 schrieb Michael J Gruber: Am Mo., 6. Nov. 2023 um 17:12 Uhr schrieb Fabio Valentini mailto:decatho...@gmail.com>>: On Mon, Nov 6, 2023 at 5:09 PM Julian Sikorski mailto:beleg...@gmail.com>> wrote: > > Hello, > > I hav

Re: goffice-0.10.46 no longer builds on i686

in your fear, seek only peace in your fear, seek only love -d. bowie Sent with Proton Mail secure email. --- Original Message --- On Sunday, November 5th, 2023 at 3:43 AM, Julian Sikorski wrote: Correction, I had a mishap when cleaning up tags. The

Wrong branch built into side tags, what to do?

Hello, I have accidentally built f39/rawhide branch of gnumeric and gnome-chemistry-utils for f38 and f37 side tags (f39 too but rawhide and f39 are the same commit). Can this be fixed? Or is the effort not worth it? Thanks. Best regards, Julian __

Re: goffice-0.10.46 no longer builds on i686

Am 04.11.23 um 18:01 schrieb Richard W.M. Jones: On Sat, Nov 04, 2023 at 03:38:55PM +0100, Julian Sikorski wrote: Hello, I tried to update goffice to 0.10.46 and gnumeric to 1.12.46 today. After pushing the changes, it turned out that it no longer builds on i686 [1][2]. Given that the use on

Re: goffice-0.10.46 no longer builds on i686

Correction, I had a mishap when cleaning up tags. The correct ones are: f40-build-side-77026 f39-build-side-77030 f38-build-side-77032 f37-build-side-77036 Best regards, Julian Am 05.11.23 um 10:36 schrieb Julian Sikorski: THanks! The side tags are: f40-build-side-77026 f40-build-side-77028

Re: goffice-0.10.46 no longer builds on i686

in your fear, seek only peace in your fear, seek only love -d. bowie Sent from Proton Mail mobile Original Message On Nov 4, 2023, 12:01 PM, Richard W.M. Jones < rjo...@redhat.com> wrote: On Sat, Nov 04, 2023 at 03:38:55PM +0100, Julian Si

goffice-0.10.46 no longer builds on i686

Hello, I tried to update goffice to 0.10.46 and gnumeric to 1.12.46 today. After pushing the changes, it turned out that it no longer builds on i686 [1][2]. Given that the use on i686 should be minimal, I would be inclined to just ExcludeArch: %{ix86} and move on. According to leafdrop, gnume

Re: Specify koji build machine mem req via. spec file

Am 04.10.23 um 12:19 schrieb Kalev Lember: On Wed, Oct 4, 2023 at 11:44 AM Martin Stransky > wrote: Hello guys, Is there's a way how to set requested amount of ram for koji builders? I'd like to use it as Firefox builds fail recently due low memory, like

Re: mame validation time takes forever on rawhide/aarch64

Am 01.10.23 um 18:32 schrieb Julian Sikorski: Am 01.10.23 um 18:14 schrieb Dan Horák: On Sun, 1 Oct 2023 14:21:23 +0200 Julian Sikorski wrote: Am 01.10.23 um 10:17 schrieb Julian Sikorski: Am 01.10.23 um 09:37 schrieb Dan Horák: On Sun, 1 Oct 2023 09:32:10 +0200 Julian Sikorski wrote

Re: mame validation time takes forever on rawhide/aarch64

Am 01.10.23 um 18:14 schrieb Dan Horák: On Sun, 1 Oct 2023 14:21:23 +0200 Julian Sikorski wrote: Am 01.10.23 um 10:17 schrieb Julian Sikorski: Am 01.10.23 um 09:37 schrieb Dan Horák: On Sun, 1 Oct 2023 09:32:10 +0200 Julian Sikorski wrote: Am 30.09.23 um 09:09 schrieb Julian Sikorski

Re: mame validation time takes forever on rawhide/aarch64

Am 01.10.23 um 18:08 schrieb John Reiser: mame package uses mame -validate as %check step. It has recently started to cause problems on rawhide/aarch64: - 0.259 build is stuck since ca. 1600 UTC yesterday [2] I managed to reproduce this on the aarch64 machine in mock. Validation seems to g

Re: mame validation time takes forever on rawhide/aarch64

Am 01.10.23 um 10:17 schrieb Julian Sikorski: Am 01.10.23 um 09:37 schrieb Dan Horák: On Sun, 1 Oct 2023 09:32:10 +0200 Julian Sikorski wrote: Am 30.09.23 um 09:09 schrieb Julian Sikorski: Hello, mame package uses mame -validate as %check step. It has recently started to cause problems

Re: mame validation time takes forever on rawhide/aarch64

Am 01.10.23 um 09:37 schrieb Dan Horák: On Sun, 1 Oct 2023 09:32:10 +0200 Julian Sikorski wrote: Am 30.09.23 um 09:09 schrieb Julian Sikorski: Hello, mame package uses mame -validate as %check step. It has recently started to cause problems on rawhide/aarch64: - I had to cancel 0.258 build

Re: mame validation time takes forever on rawhide/aarch64

Am 30.09.23 um 09:09 schrieb Julian Sikorski: Hello, mame package uses mame -validate as %check step. It has recently started to cause problems on rawhide/aarch64: - I had to cancel 0.258 build after 16 hours [1] - 0.259 build is stuck since ca. 1600 UTC yesterday [2] Other branches built

mame validation time takes forever on rawhide/aarch64

Hello, mame package uses mame -validate as %check step. It has recently started to cause problems on rawhide/aarch64: - I had to cancel 0.258 build after 16 hours [1] - 0.259 build is stuck since ca. 1600 UTC yesterday [2] Other branches built fine for aarch64, and so did other arches for rawh

Re: AVX extensions not detected properly on a Zen 2 CPU?

Am 28.08.23 um 14:39 schrieb Florian Weimer: * Julian Sikorski: I have noticed the following message in my kernel log today after I attempted to decrypt my veracrypt external hard drive: [20542.328594] AVX2 instructions are not detected. [20542.382731] AVX or AES-NI instructions are not

AVX extensions not detected properly on a Zen 2 CPU?

Hello, I have noticed the following message in my kernel log today after I attempted to decrypt my veracrypt external hard drive: [20542.328594] AVX2 instructions are not detected. [20542.382731] AVX or AES-NI instructions are not detected. [20542.404097] AVX or AES-NI instructions are not det

lzma-sdk and undefined references

Hello, now that lzma-sdk in Fedora rawhide is no longer ancient, I tried using it with mame. Unfortunately, I got a number of undefined references when linking: /usr/bin/ld: ../../../../linux_gcc/bin/x64/Release/libutils.a(un7z.o): in function `std::arraynamespace)::m7z_file_impl, std::defau

Re: Has anything changed in terms of how to build a signed kernel semi-recently?

Am 29.05.23 um 17:00 schrieb Pavel Raiskup: On pondělí 29. května 2023 13:58:08 CEST Julian Sikorski wrote Am 18.05.23 um 00:41 schrieb Julian Sikorski: Am 17.05.23 um 23:35 schrieb Julian Sikorski: Hello, I tried building a signed 6.3 kernel today after a while (6.1 timeframe

Re: Has anything changed in terms of how to build a signed kernel semi-recently?

Am 29.05.23 um 13:58 schrieb Julian Sikorski: Am 18.05.23 um 00:41 schrieb Julian Sikorski: Am 17.05.23 um 23:35 schrieb Julian Sikorski: Hello, I tried building a signed 6.3 kernel today after a while (6.1 timeframe). Unfortunately, it appears that I am hitting some issues with pesign

Re: Has anything changed in terms of how to build a signed kernel semi-recently?

Am 18.05.23 um 00:41 schrieb Julian Sikorski: Am 17.05.23 um 23:35 schrieb Julian Sikorski: Hello, I tried building a signed 6.3 kernel today after a while (6.1 timeframe). Unfortunately, it appears that I am hitting some issues with pesign: + /usr/bin/pesign --certdir /etc/pki/pesign -t

Re: Has anything changed in terms of how to build a signed kernel semi-recently?

Am 17.05.23 um 23:35 schrieb Julian Sikorski: Hello, I tried building a signed 6.3 kernel today after a while (6.1 timeframe). Unfortunately, it appears that I am hitting some issues with pesign: + /usr/bin/pesign --certdir /etc/pki/pesign -t 'NSS Certificate DB' -c 'Juli

Has anything changed in terms of how to build a signed kernel semi-recently?

Hello, I tried building a signed 6.3 kernel today after a while (6.1 timeframe). Unfortunately, it appears that I am hitting some issues with pesign: + /usr/bin/pesign --certdir /etc/pki/pesign -t 'NSS Certificate DB' -c 'Julians Secure Boot signing key - Julian Sikorski&#

Re: Note section size too big (was: Re: FTBFS bug filed, build already deleted)

Am 21.02.23 um 15:42 schrieb Lukas Zaoral: On Mon, Feb 20, 2023 at 10:19 PM Julian Sikorski <mailto:beleg...@gmail.com>> wrote: > > Am 20.02.23 um 19:14 schrieb Orion Poplawski: > > On 2/20/23 10:46, Fabio Valentini wrote: > >> On Mon, Feb 20, 2023 at 6:43 PM

Note section size too big (was: Re: FTBFS bug filed, build already deleted)

Am 20.02.23 um 19:14 schrieb Orion Poplawski: On 2/20/23 10:46, Fabio Valentini wrote: On Mon, Feb 20, 2023 at 6:43 PM Julian Sikorski wrote: Hello, FTBFS bug was filed against mame [1]. Unfortunately, the corresponding build [2] has already been deleted. This is not ideal from maintainer

FTBFS bug filed, build already deleted

Hello, FTBFS bug was filed against mame [1]. Unfortunately, the corresponding build [2] has already been deleted. This is not ideal from maintainer perspective as it effectively is a bug with no info provided whatsoever. Not to mention being quite wasteful from the resources perspective as ma

Gnome-online-accounts can no longer keep fedora kerberos tickets valid?

Hello, for some time now my Fedora kerberos tickets keep expiring despite having Fedora identity set up in gnome-online-accounts: $ LANG=C klist Ticket cache: KCM:1000:82483 Default principal: beleg...@fedoraproject.org Valid starting ExpiresService principal 01/19/23 08:42:58

Re: Updating asio in rawhide (and possibly F37) to 1.24.0

Am 14.08.22 um 11:24 schrieb Julian Sikorski: Dear maintainers, I have updated Fedora asio package from the current 1.16.1 to 1.24.0. I have rebuilt the seven current dependencies and with the exception of OpenSceneGraph, all build fine against the updated asio package. While OpenSceneGraph

Re: Heads-up: Side-tag rebuild due to minizip-ng soname bump

Am 07.11.22 um 14:49 schrieb Petr Pisar: V Mon, Nov 07, 2022 at 01:40:18PM +0100, Lukas Javorsky napsal(a): Hi, Minizip-ng has changed its soname name from "libminizip.so.3.0" to "libminizip.so.3" thus we need to rebuild all the packages that are requiring this soname. I've listed them with th

Re: Grub menu with 3 kernels by default

Am 05.10.22 um 23:07 schrieb Chris Murphy: On Wed, Oct 5, 2022, at 3:01 PM, Vít Ondruch wrote: 3. "Boot menu" in GUI? Given that one can reach the GUI, why it should not be possible to choose the boot entry for next boot? Or even choose to open FW setup. This could solve this other problem

Re: Mesa in F37- vaapi support disabled for h264/h265/vc1

Am 28.09.22 um 15:27 schrieb Neal Gompa: On Wed, Sep 28, 2022 at 3:22 PM Ian Pilcher wrote: On 9/28/22 03:50, Tommy Nguyen wrote: This change will only affect AMD, as the intel non-free drivers do not depend on the changes. It is also unclear how this would affect nvidia. There is barely any

Re: Mesa in F37- vaapi support disabled for h264/h265/vc1

Am 27.09.22 um 20:01 schrieb Frantisek Zatloukal: Hi, since this mesa change ( https://src.fedoraproject.org/rpms/mesa/c/94ef544b3f2125912dfbff4c6ef373fe49806b52?branch=rawhide ) in F37 and rawhi

Re: Updating asio in rawhide (and possibly F37) to 1.24.0

Am 20.08.22 um 18:00 schrieb Julian Sikorski: Am 14.08.22 um 13:08 schrieb Mamoru TASAKA: Julian Sikorski wrote on 2022/08/14 19:06: Am 14.08.22 um 11:24 schrieb Julian Sikorski: Dear maintainers, I have updated Fedora asio package from the current 1.16.1 to 1.24.0. I have rebuilt the seven

Re: Updating asio in rawhide (and possibly F37) to 1.24.0

Am 14.08.22 um 13:08 schrieb Mamoru TASAKA: Julian Sikorski wrote on 2022/08/14 19:06: Am 14.08.22 um 11:24 schrieb Julian Sikorski: Dear maintainers, I have updated Fedora asio package from the current 1.16.1 to 1.24.0. I have rebuilt the seven current dependencies and with the exception

Re: Updating asio in rawhide (and possibly F37) to 1.24.0

Am 14.08.22 um 11:24 schrieb Julian Sikorski: Dear maintainers, I have updated Fedora asio package from the current 1.16.1 to 1.24.0. I have rebuilt the seven current dependencies and with the exception of OpenSceneGraph, all build fine against the updated asio package. While OpenSceneGraph

Updating asio in rawhide (and possibly F37) to 1.24.0

Dear maintainers, I have updated Fedora asio package from the current 1.16.1 to 1.24.0. I have rebuilt the seven current dependencies and with the exception of OpenSceneGraph, all build fine against the updated asio package. While OpenSceneGraph failed to build, the failure does not seem to ha

Re: Non-responsive asio maintainers (uwog, fale, dcavalca, raineforest)

Am 13.08.22 um 10:29 schrieb Julian Sikorski: Dear list, does anybody know how to contact asio maintainers? The asio version in our repositories is quite old and the bug asking for an update has been unanswered for more than 2 years: https://bugzilla.redhat.com/show_bug.cgi?id=2117996 I

Non-responsive asio maintainers (uwog, fale, dcavalca, raineforest)

Dear list, does anybody know how to contact asio maintainers? The asio version in our repositories is quite old and the bug asking for an update has been unanswered for more than 2 years: https://bugzilla.redhat.com/show_bug.cgi?id=2117996 I have filed non-responsive maintainer bugs for all

Re: Bugzilla: You can't ask Lennart Poettering because that account is disabled.

Am 03.07.22 um 19:33 schrieb Kevin Fenzi: On Sun, Jul 03, 2022 at 11:52:26AM +0200, Marius Schwarz wrote: Am 03.07.22 um 04:02 schrieb Neal Gompa: On Sat, Jul 2, 2022 at 8:52 PM Kevin Kofler via devel wrote: Kevin Kofler via devel wrote: The e-mail address reaches nowhere or actually, does

Re: intend to orphan python-cairosvg

Am 31.05.22 um 12:44 schrieb Felix Schwarz: Hi *, I'd like to orphan python-cairosvg. This package was required by older WeasyPrint releases but WeasyPrint v53 (Fedora 35+) stopped using cairo so I don't use this package anymore. The package should be ok however I expect very little upstream

Re: Does F36 handle $RPM_OPT_FLAGS differently?

W dniu 07.05.2022 o 23:19, Julian Sikorski pisze: W dniu 07.05.2022 o 22:44, Julian Sikorski pisze: Hi list, I have constructs like these in my RPM spec files: RPM_OPT_FLAGS=$(echo $RPM_OPT_FLAGS | sed "s@ -Wp,-D_GLIBCXX_ASSERTIONS@@") RPM_OPT_FLAGS=$(echo $RPM_OPT_FLAGS | sed

Re: Does F36 handle $RPM_OPT_FLAGS differently?

W dniu 07.05.2022 o 22:44, Julian Sikorski pisze: Hi list, I have constructs like these in my RPM spec files: RPM_OPT_FLAGS=$(echo $RPM_OPT_FLAGS | sed "s@ -Wp,-D_GLIBCXX_ASSERTIONS@@") RPM_OPT_FLAGS=$(echo $RPM_OPT_FLAGS | sed "s@-g@-g1@") these used to work for f35 [1]

Does F36 handle $RPM_OPT_FLAGS differently?

Hi list, I have constructs like these in my RPM spec files: RPM_OPT_FLAGS=$(echo $RPM_OPT_FLAGS | sed "s@ -Wp,-D_GLIBCXX_ASSERTIONS@@") RPM_OPT_FLAGS=$(echo $RPM_OPT_FLAGS | sed "s@-g@-g1@") these used to work for f35 [1] but no longer do for f36 [2]. Is this an intentional change? Best rega

Re: Minizip pull requests

W dniu 21.04.2022 o 21:22, Julian Sikorski pisze: Hello, I have created two PRs against minizip which are yet to be merged: - https://src.fedoraproject.org/rpms/minizip/pull-request/3 - https://src.fedoraproject.org/rpms/minizip/pull-request/4 The first one should be a low risk one and should

Minizip pull requests

Hello, I have created two PRs against minizip which are yet to be merged: - https://src.fedoraproject.org/rpms/minizip/pull-request/3 - https://src.fedoraproject.org/rpms/minizip/pull-request/4 The first one should be a low risk one and should allow pkg-config using dependencies like (shameles

Re: FailsToInstall bugs filed even though all dependencies were submitted as one update

Am 21.04.22 um 20:30 schrieb Miro Hrončok: On 21. 04. 22 20:23, Julian Sikorski wrote: Am 21.04.22 um 20:11 schrieb Miro Hrončok: On 21. 04. 22 17:49, Julian Sikorski wrote: Am 21.04.22 um 17:42 schrieb Miro Hrončok: On 21. 04. 22 17:21, Julian Sikorski wrote: Hello, I have recently

Re: FailsToInstall bugs filed even though all dependencies were submitted as one update

Am 21.04.22 um 20:11 schrieb Miro Hrončok: On 21. 04. 22 17:49, Julian Sikorski wrote: Am 21.04.22 um 17:42 schrieb Miro Hrončok: On 21. 04. 22 17:21, Julian Sikorski wrote: Hello, I have recently created 3 updates to goffice and gnumeric: - https://bodhi.fedoraproject.org/updates/FEDORA

Re: FailsToInstall bugs filed even though all dependencies were submitted as one update

Am 21.04.22 um 17:42 schrieb Miro Hrončok: On 21. 04. 22 17:21, Julian Sikorski wrote: Hello, I have recently created 3 updates to goffice and gnumeric: - https://bodhi.fedoraproject.org/updates/FEDORA-2022-a7a300f5b1 - https://bodhi.fedoraproject.org/updates/FEDORA-2022-9a07603dd6 - https

FailsToInstall bugs filed even though all dependencies were submitted as one update

Hello, I have recently created 3 updates to goffice and gnumeric: - https://bodhi.fedoraproject.org/updates/FEDORA-2022-a7a300f5b1 - https://bodhi.fedoraproject.org/updates/FEDORA-2022-9a07603dd6 - https://bodhi.fedoraproject.org/updates/FEDORA-2022-ab9857bfaf Despite putting the gnome-chemistr

Koji notifications arriving days late

Hello, is it a known problem that koji notifications arrive way too late? For example, I got mame build notifications in the wee hours today (31.12) wheras the builds completed around noon on the 29th: https://koji.fedoraproject.org/koji/buildinfo?buildID=1871260 https://koji.fedoraproject.org

Re: F36 Change: Wayland By Default with NVIDIA proprietary Driver (System-Wide Change)

W dniu 19.12.2021 o 17:05, Michael Cronenworth pisze: On 12/17/21 8:11 PM, Michael Berteaux wrote: On top of what others said, I add that there is also the nvidia-settings GUI that does not work on Wayland. I don't use it personally, but other people can use, for example, application/game pro

Re: F36 Change: Wayland By Default with NVIDIA proprietary Driver (System-Wide Change)

Am 07.12.21 um 15:45 schrieb Ben Cotton: https://fedoraproject.org/wiki/Changes/WaylandByDefaultOnNVIDIA == Summary == Enable Wayland sessions by default in GDM even with the NVIDIA proprietary driver. == Owner == * Name: [[User:ofourdan| Olivier Fourdan]] * Email: == Detailed Description ==

Re: Firefox Hardware acceleration & VA-API how-to

Am 12.11.21 um 09:37 schrieb Martin Stransky: Hi folks, I was told that people were having trouble with Firefox/HW acceleration/VA-API setup on Fedora so I put some info at wiki at: https://fedoraproject.org/wiki/Firefox_Hardware_acceleration Hope it helps. Martin > With https://bugzilla.m

Re: Firefox Hardware acceleration & VA-API how-to

Am 17.11.21 um 15:26 schrieb PGNet Dev: On 11/16/21 22:48, Michael Cronenworth wrote: On 11/15/21 12:03 PM, PGNet Dev wrote: launch @ shell VDPAU_DRIVER=nvidia MOZ_LOG="Dmabuf:5, PlatformDecoderModule:5" firefox I think you mean: LIBVA_DRIVER_NAME=nvidia firefox nope. https:/

Re: Firefox Hardware acceleration & VA-API how-to

Am 12.11.21 um 09:37 schrieb Martin Stransky: Hi folks, I was told that people were having trouble with Firefox/HW acceleration/VA-API setup on Fedora so I put some info at wiki at: https://fedoraproject.org/wiki/Firefox_Hardware_acceleration Hope it helps. Martin For VP9 on AMD the follow

Re: Mono fonts blurry since F34

Am 15.11.21 um 02:37 schrieb Reon Beon via devel: A bug in cairo? Could be a feature as well. I have bisected it down to a commit adding subpixel positioning to cairo: https://gitlab.freedesktop.org/cairo/cairo/-/commit/e4a79db0108be6a2b06dfce51a44bcbdead66ebd Best regards, Julian _

Re: Mono fonts blurry since F34

Am 15.11.21 um 02:37 schrieb Reon Beon via devel: A bug in cairo? Could be a feature as well. I have bisected it down to a commit adding subpixel positioning to cairo: https://gitlab.freedesktop.org/cairo/cairo/-/commit/e4a79db0108be6a2b06dfce51a44bcbdead66ebd Best regards, Julian _

Re: Mono fonts blurry since F34

W dniu 13.11.2021 o 11:32, Julian Sikorski pisze: W dniu 13.11.2021 o 11:10, Julian Sikorski pisze: Hi, I originally posted this into bugzilla [1] and onto mono bug tracker [2], but we were unable to solve the problem. Given that F33 is going EOL soon and I will have to choose between losing

Re: Mono fonts blurry since F34

W dniu 13.11.2021 o 11:10, Julian Sikorski pisze: Hi, I originally posted this into bugzilla [1] and onto mono bug tracker [2], but we were unable to solve the problem. Given that F33 is going EOL soon and I will have to choose between losing my test case or running without updates, I

Mono fonts blurry since F34

Hi, I originally posted this into bugzilla [1] and onto mono bug tracker [2], but we were unable to solve the problem. Given that F33 is going EOL soon and I will have to choose between losing my test case or running without updates, I decided to post here. In brief, since upgrading to F34, mo

Re: Strange mock chainbuild issue: package has incorrect checksum

W dniu 31.10.2021 o 17:07, Sérgio Basto pisze: On Sun, 2021-10-31 at 14:50 +0100, Julian Sikorski wrote: W dniu 20.10.2021 o 20:09, Julian Sikorski pisze: W dniu 29.09.2021 o 10:08, Julian Sikorski pisze: W dniu 28.09.2021 o 09:32, Julian Sikorski pisze: W dniu 22.09.2021 o 21:07, Julian

Re: Strange mock chainbuild issue: package has incorrect checksum

W dniu 20.10.2021 o 20:09, Julian Sikorski pisze: W dniu 29.09.2021 o 10:08, Julian Sikorski pisze: W dniu 28.09.2021 o 09:32, Julian Sikorski pisze: W dniu 22.09.2021 o 21:07, Julian Sikorski pisze: Am 22.09.21 um 19:38 schrieb Fabio Valentini: On Wed, Sep 22, 2021 at 6:35 PM Julian Sikorski

Re: Impossible to upgrade to F35 due to dependency issues with pam_mount and cryptsetup

W dniu 31.10.2021 o 12:57, Julian Sikorski pisze: Hello, I had some time today so I decided to try updating to F35 ahead of the release. It did not work unfortunately: Error:  Problem 1: package mupen64plus-qt-1.12-1.20200226git1709647.fc31.x86_64 requires libquazip5.so.1()(64bit), but

Impossible to upgrade to F35 due to dependency issues with pam_mount and cryptsetup

Hello, I had some time today so I decided to try updating to F35 ahead of the release. It did not work unfortunately: Error: Problem 1: package mupen64plus-qt-1.12-1.20200226git1709647.fc31.x86_64 requires libquazip5.so.1()(64bit), but none of the providers can be installed - quazip-qt5-0

Re: Strange mock chainbuild issue: package has incorrect checksum

W dniu 29.09.2021 o 10:08, Julian Sikorski pisze: W dniu 28.09.2021 o 09:32, Julian Sikorski pisze: W dniu 22.09.2021 o 21:07, Julian Sikorski pisze: Am 22.09.21 um 19:38 schrieb Fabio Valentini: On Wed, Sep 22, 2021 at 6:35 PM Julian Sikorski wrote: W dniu 21.09.2021 o 23:12, Richard W.M

  1   2   3   >