only 4 packages left Re: Let's retire original glib and gtk+ (new report)
On Thu, 2022-03-10 at 00:15 +0200, Otto Urpelainen wrote: > Leigh Scott kirjoitti 9.3.2022 klo 18.15: > > > Sérgio Basto kirjoitti 7.3.2022 klo 18.17: > > > Crossfire and freedroidrpg are games, so "is it needed?" and > > > "does it > > > have a replacement?" are not good questions to ask. A better > > > question > > > would be "does anybody want to play it?". Games do not really ever > > > become obsolete, each is a unique experience and cannot be replaced > > > by a > > > "modern alternative to X with more features". > > > > > > Personally, I have never played either of these games, and I > > > suspect I > > > will not ever play them. Retiring them is probably not a great loss > > > to > > > Fedora. But, if there is no pressing reason, security issue, lack > > > of > > > maintainer or such, to retire the compatibility lib, I would prefer > > > to > > > keep all the games that somebody is willing to maintain. > > > > > > > > > Otto > > > > Both those games don't use gtk+-devel. > > Thank you for looking that up, and even more for fixing the packages. Continuing I brought the corrections to Fedora 36 https://bodhi.fedoraproject.org/updates/FEDORA-2022-db793ad26c Now only 4 packages more gtk1+ depends on glib Depending packages (rawhide) (5): bubblemon gtk+ manedit xconvers xvattr Depending on: glib (5), bubblemon (maintained by: sham1) bubblemon-1.46-31.fc36.x86_64 requires libglib-1.2.so.0()(64bit), libgmodule-1.2.so.0()(64bit) seems that can be build with gtk2 https://gitweb.gentoo.org/repo/gentoo.git/tree/x11-plugins/bubblemon/bubblemon-1.46-r3.ebuild xvattr (maintained by: ppisar, thias) gxvattr-1.3-44.fc36.x86_64 requires libgdk-1.2.so.0()(64bit), libglib- 1.2.so.0()(64bit), libgtk-1.2.so.0()(64bit) seems xvattr can be build with gtk2 http://sophie.zarb.org/rpms/88281125c921a2cc60abf2eea23e54de/deps manedit (maintained by: pali) manedit-1.2.1-27.fc36.x86_64 requires libglib-1.2.so.0()(64bit), libgmodule-1.2.so.0()(64bit) (manedit have replacment with https://tracker.debian.org/pkg/gmanedit xconvers (maintained by: hobbes1069) xconvers-0.8.3-29.fc36.x86_64 requires libglib-1.2.so.0()(64bit) still only available on aur and Fedora https://repology.org/project/xconvers/versions > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure -- Sérgio M. B. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Missing 'pkgconfig(portaudiocpp) >= 12' for EPEL9
Hello team, it looks like 'pkgconfig(portaudiocpp) >= 12' is missing in EPEL9 repository while available in EPEL8. See https://koji.fedoraproject.org/koji/taskinfo?taskID=84302098 Could someone port that dependency and rebuild xournalpp please? Thanks in advance. -- Luya Tshimbalanga Fedora Design Team Fedora Design Suite maintainer ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: FESCo wants to know what you use i686 packages for
On Wed, Mar 16, 2022 at 9:34 PM laolux laolux via devel < devel@lists.fedoraproject.org> wrote: > Hi, > > could you just post some magic dnf command to check which i686 packages > are currently installed? Then many less savvy users could simply check what > packages are currently installed on their systems. > Maybe something like `dnf repoquery --installed |grep i686` works, but I > think I have no 686 packages installed, so I cannot really test it. And I > do not want to install i686 packages just for that test, who knows what > will break. > > Ah, and yes, I support removing i686 packages. > For installed packages rpm is much faster: $ rpm -qa | grep i686 | sort Thanks, Richard ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: FESCo wants to know what you use i686 packages for
Hi, could you just post some magic dnf command to check which i686 packages are currently installed? Then many less savvy users could simply check what packages are currently installed on their systems. Maybe something like `dnf repoquery --installed |grep i686` works, but I think I have no 686 packages installed, so I cannot really test it. And I do not want to install i686 packages just for that test, who knows what will break. Ah, and yes, I support removing i686 packages. Best, laolux ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora-IoT-36-20220316.0 compose check report
No missing expected images. Failed openQA tests: 2/15 (x86_64), 3/15 (aarch64) Old failures (same test failed in Fedora-IoT-36-20220315.0): ID: 1178884 Test: x86_64 IoT-dvd_ostree-iso iot_zezere_server@uefi URL: https://openqa.fedoraproject.org/tests/1178884 ID: 1178896 Test: x86_64 IoT-dvd_ostree-iso iot_zezere_ignition@uefi URL: https://openqa.fedoraproject.org/tests/1178896 ID: 1178897 Test: aarch64 IoT-dvd_ostree-iso iot_clevis@uefi URL: https://openqa.fedoraproject.org/tests/1178897 ID: 1178899 Test: aarch64 IoT-dvd_ostree-iso iot_zezere_server@uefi URL: https://openqa.fedoraproject.org/tests/1178899 ID: 1178911 Test: aarch64 IoT-dvd_ostree-iso iot_zezere_ignition@uefi URL: https://openqa.fedoraproject.org/tests/1178911 Passed openQA tests: 13/15 (x86_64), 12/15 (aarch64) New passes (same test not passed in Fedora-IoT-36-20220315.0): ID: 1178894 Test: x86_64 IoT-dvd_ostree-iso release_identification@uefi URL: https://openqa.fedoraproject.org/tests/1178894 ID: 1178905 Test: aarch64 IoT-dvd_ostree-iso release_identification@uefi URL: https://openqa.fedoraproject.org/tests/1178905 Installed system changes in test aarch64 IoT-dvd_ostree-iso install_default_upload@uefi: System load changed from 0.40 to 0.18 Previous test data: https://openqa.fedoraproject.org/tests/1176581#downloads Current test data: https://openqa.fedoraproject.org/tests/1178898#downloads -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Test-Announce] Fedora Linux 36 Beta is NO-GO
Due to outstanding blocker bugs[1], we do not have an updated F36 Beta RC. As a result, F36 Beta is NO-GO by default and Thursday's Go/No-Go meeting is cancelled. The next Fedora Linux 36 Beta Go/No-Go meeting[2] will be held at 1700 UTC on Thursday 24 March in #fedora-meeting. We will aim for the "target date #2" milestone of 29 March. The release schedule[3] has been updated accordingly. This change does not impact the final release date. [1] https://qa.fedoraproject.org/blockerbugs/milestone/36/beta/buglist [2] https://calendar.fedoraproject.org/Fedora%20release/2022/3/21/#m10209 [3] https://fedorapeople.org/groups/schedule/f-36/f-36-key-tasks.html -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test-announce mailing list -- test-annou...@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@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/test-annou...@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: FESCo wants to know what you use i686 packages for
On 3/16/22 10:35, Robbie Harwood wrote: > David Cantrell writes: > >> Why? Since the removal of the i686 kernel in Fedora, we want to >> reduce the number of i686 packages provided in the repo. As time >> marches on, the ability to build a lot of things for i686 becomes >> unrealistic or even impossible. Remember it goes beyond providing >> builds...providing support, bug fixes, and security fixes for those >> packages too. Maybe some things using i686 packages now can move to >> x86_64 packages. We do not know yet, but a goal is to figure out what >> packages, if anything, can drop their i686 builds. >> >> NOTE: Nothing is changing now. We are in an information gathering >> phase. >> >> If you use i686 packages for something now, please respond to this thread. > > Nothing that couldn't be cross-built and provided as an x86_64 package. > > I use wine, which as I understand it, requires 32-bit libraries to run > 32-bit Windows binaries. > > Given the weakness of x86 ASLR, it makes sense to ensure most of the > i686 packages aren't actually getting used (e.g., no browsers). At that > point, seems like we'd be better off not building for the arch at all, > and doing cross-builds from x86_64 for the packages that need it. +1 on cross-compilation. Native compilation on 32-bit is a dead end. -- Sincerely, Demi Marie Obenour (she/her/hers) OpenPGP_0xB288B55FFF9C22C1.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Can't fedpkg new-sources (403)
On Wed, Mar 16, 2022 at 2:40 PM Kevin Fenzi wrote: > On Wed, Mar 16, 2022 at 01:55:03PM -0400, Neal Becker wrote: > > On Wed, Mar 16, 2022 at 1:45 PM Neal Becker wrote: > > > > > > > > > > > On Wed, Mar 16, 2022 at 1:38 PM Neal Becker > wrote: > > > > > >> I believe it is failing on the line: > > >> File "/usr/lib/python3.10/site-packages/pyrpkg/lookaside.py", line > 298, > > >> in upload > > >> if self.remote_file_exists(name, filename, hash): > > >> File "/usr/lib/python3.10/site-packages/pyrpkg/lookaside.py", line > 259, > > >> in remote_file_exists > > >> self.raise_upload_error(status) > > >> > > >> So maybe the file already exists in the cache? But then, sources has > not > > >> been updated, and if I try > > >> fedpkg local it will attempt to build the old version 1.8.1, not the > new > > >> 1.9.0. > > >> > > >> > > > > > OK, so unuran-1.9.0.tar.gz already exists in the cache. So I had to > > > manually update sources by running > > > md5sum unuran-1.9.0.tar.gz, which luckily I just guessed. Now > everything > > > seems to be working fine. > > > > > > > Ooops, spoke too soon. > > fedpkg local > > Downloading unuran-1.9.0.tar.gz > > > > 100.0% > > Remove downloaded invalid file > > /home/nbecker/fedora.git/unuran/unuran-1.9.0.tar.gz > > Could not execute local: Server returned status code 404 > > > > No idea what's going on here. > > You seem to have gotten a kerberos ticket for: > > nbec...@fedoraproject.org > > which I guess ipa is fine with giving you. > However, our upload script checking your username sees "NBECKER" and not > 'nbecker' and denys you. > > Can you do: > > kdestroy -A > > then > > kinit nbec...@fedoraproject.org > > and see if it works? > > kevin > Yes, that was the problem and the solution. The error messages I saw were not very helpful. Thanks! ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: FESCo wants to know what you use i686 packages for
On Wed, Mar 16, 2022 at 02:11:23PM -0400, Josh Boyer wrote:
> On Wed, Mar 16, 2022 at 1:37 PM Zbigniew Jędrzejewski-Szmek
> wrote:
> >
> > On Wed, Mar 16, 2022 at 12:54:23PM -0400, Josh Boyer wrote:
> > > On Wed, Mar 16, 2022 at 11:55 AM Zbigniew Jędrzejewski-Szmek
> > > wrote:
> > > >
> > > > On Wed, Mar 16, 2022 at 09:54:12AM -0400, David Cantrell wrote:
> > > > > If you use i686 packages for something now, please respond to this
> > > > > thread.
> > > >
> > > > I use i686 versions of libraries to do local 32-bit builds of C
> > > > software I'm developing. (Something like 'sudo dnf install
> > > > lib{one,two}-devel.i686 &&
> > > > meson build-32 -Dc_args=-m32 -Dc_link_args=-m32 -Dcpp_args=-m32
> > > > -Dcpp_link_args=-m32
> > > > --pkg-config-path=/usr/lib/pkgconfig && ninja -C build-32' .)
> > > >
> > > > So I'd be interesting in keeping 32-bit versions of all BuildRequires
> > > > for
> > > > systemd.
> > >
> > > Who uses those builds and what do they use them for?
> >
> > They are purely local. I use them to compile and run tests locally so
> > I know that the code works correctly on 32-bit. I'll also do test
> > builds on arm/arm64/ppc64/riscv/anything-else-that-I-can-lay my hand on.
>
> Are you aware of any upstream users of 32-bit systemd? Or some other
> distro that requires it?
>
> I ask because I see several responses along the same lines (I use it
> to build 32-bit packages), but unless *Fedora* uses those resulting
> 32-bit builds it seems like an odd reason to keep i686 around. Yes,
> being able to build for i686 means you need i686 but the root of the
> question is why do you need to build for i686?
To build for 32 bits, I need not just the code, but a hefty set of libraries.
I *could* build all of this myself, or use another distro, but that's
not very appealing. Fedora gives me up-to-date dependencies in a very
convenient fashion. It is also very useful to have the 32-bit deps in
the same versions that I have the 64-bit ones, so I can compile and
compare builds with the architecture being the only difference. I also
don't want to use a container or a special environment, but I want to
build and run the code "natively" as much as possible. (Or more precisely:
I want to *also* run code "natively". For low-level software, running things
directly on the local hardware can be quite useful for debugging of
certain problems. Container and mock and VMs are useful at other times.)
So the short version is that this is for convenience and "native"
development.
> If there are other distros that still support 32-bit systemd, could
> you do your 32-bit build and test against those instead?
The code is portable to 32-bit and 32-bit builds are still supported,
and as upstream developer, I need to make sure that the code works
on a large set of architectures, even those not supported by Fedora
(riscv, mips, x32, etc.).
I consider Fedora superior to other distros. If I can't use Fedora,
I'd probably use Debian or Ubuntu or something else, but I'd prefer
not to. Fedora is a great developer environment, and development for
32-bit architectures is still relevant.
Zbyszek
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Re: Can't fedpkg new-sources (403)
On Wed, Mar 16, 2022 at 01:45:52PM -0400, Neal Becker wrote: >On Wed, Mar 16, 2022 at 1:38 PM Neal Becker <[1]ndbeck...@gmail.com> >wrote: > > I believe it is failing on the line: > File "/usr/lib/python3.10/site-packages/pyrpkg/lookaside.py", line > 298, in upload > if self.remote_file_exists(name, filename, hash): > File "/usr/lib/python3.10/site-packages/pyrpkg/lookaside.py", line > 259, in remote_file_exists > self.raise_upload_error(status) > So maybe the file already exists in the cache? But then, sources has > not been updated, and if I try > fedpkg local it will attempt to build the old version 1.8.1, not the new > 1.9.0. > >OK, so unuran-1.9.0.tar.gz already exists in the cache. So I had to >manually update sources by running >md5sum unuran-1.9.0.tar.gz, which luckily I just guessed. Now everything >seems to be working fine. Also, we no longer use md5sum in our lookaside cache by default, but sha512, so you may have more chances using that algorithm :) Pierre ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Problem with cmake 3.23.0
Sorry for the late reply, domain issue affected my email reception. The macros don't change between F36 and F37; I've filed https://gitlab.kitware.com/cmake/cmake/-/issues/23334 to see if upstream can shed a light on this. -- Michel ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora CoreOS Meeting Minutes 2022-03-16
Minutes: https://meetbot.fedoraproject.org/fedora-meeting-1/2022-03-16/fedora_coreos_meeting.2022-03-16-16.30.html Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting-1/2022-03-16/fedora_coreos_meeting.2022-03-16-16.30.txt Log: https://meetbot.fedoraproject.org/fedora-meeting-1/2022-03-16/fedora_coreos_meeting.2022-03-16-16.30.log.html #fedora-meeting-1: fedora_coreos_meeting Meeting started by dustymabe at 16:30:25 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2022-03-16/fedora_coreos_meeting.2022-03-16-16.30.log.html . Meeting summary --- * roll call (dustymabe, 16:30:32) * Action items from last meeting (dustymabe, 16:34:40) * news (dustymabe, 16:35:45) * the Fedora 36 beta is fast approaching and we will be rebasing our `next` stream on top of Fedora 36 (most likely to be released next week) (dustymabe, 16:36:25) * podman v4 is coming to the next stream along with Fedora 36 https://discussion.fedoraproject.org/t/fedora-coreos-moving-to-podman-v4/37303/2 (dustymabe, 16:36:57) * iptables nft by default is coming to the `next` stream along with Fedora 36 https://discussion.fedoraproject.org/t/fedora-coreos-moving-to-iptables-nft/37302/2 (dustymabe, 16:37:26) * The "dirty pipe" CVE-2022-0847 has now been fixed in all FCOS streams (as of today) (dustymabe, 16:38:19) * there are some regressions for some NFS servers brought in by the new kernel: https://discussion.fedoraproject.org/t/latest-kernel-update-can-cause-nfs-mount-failures/37555/2 (dustymabe, 16:38:57) * the Februrary update on happenings in Fedora CoreOS was posted by cverna: https://discussion.fedoraproject.org/t/this-month-in-fedora-coreos-february-2022/37477/2 (dustymabe, 16:40:06) * Update the VMware metadata to new, modern defaults (dustymabe, 16:41:22) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1119 (dustymabe, 16:41:27) * LINK: https://kb.vmware.com/s/article/1003746 (bgilbert, 16:59:48) * AWS: Add predictable symlinks for secondary disks (dustymabe, 17:03:49) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1122 (dustymabe, 17:03:54) * LINK: https://github.com/aws/amazon-ec2-utils (davdunc, 17:08:20) * having stable symlinks would be useful, though ideally it would live somewhere more generic and not be owned by us. there is also some apprehension about mixing networking and udev rules. (jlebon, 17:22:09) * Unable to disable zincati.service using Ignition (dustymabe, 17:23:31) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/392 (dustymabe, 17:23:37) * LINK: https://github.com/systemd/systemd/pull/15205 (lorbus, 17:25:14) * LINK: https://github.com/coreos/fedora-coreos-config/pull/363#issuecomment-1069323399 (jlebon, 17:27:51) * open floor (dustymabe, 17:34:00) * ACTION: davdunc to put a package review in for ec2-net-utils and brainstorm on how we can use that for #601 (dustymabe, 17:34:48) * coreos.live.rootfs_url now supports tftp:// (bgilbert, 17:35:25) Meeting ended at 17:40:57 UTC. Action Items * davdunc to put a package review in for ec2-net-utils and brainstorm on how we can use that for #601 Action Items, by person --- * davdunc * davdunc to put a package review in for ec2-net-utils and brainstorm on how we can use that for #601 * **UNASSIGNED** * (none) People Present (lines said) --- * dustymabe (79) * jlebon (42) * zodbot (32) * miabbott (31) * bgilbert (31) * davdunc (28) * lucab (18) * travier (9) * lorbus (6) * nemric (6) * fifofonix (4) * ravanelli (2) * skunkerk (1) * jmarrero (1) * jbrooks (1) * marmijo (1) * cverna (1) * mnguyen (1) * copperi[m] (1) * ryanjenkins (0) Generated by `MeetBot`_ 0.4 .. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Problem with cmake 3.23.0
On Wed, 2022-03-16 at 07:17 -0700, Thomas Rodgers wrote: > One more package that FTBFS due to CMake issues - > > grive2: FTBFS # Error: /builddir/build/BUILD/grive2-0.5.1/redhat- > linux-build is not a directory remove the dot and I bet that will work > > On Mon, Mar 14, 2022 at 2:22 PM Thomas Rodgers > wrote: > > > > > > > > On Mon, Mar 14, 2022 at 4:37 AM Jonathan Wakely > > wrote: > > > On Fri, 4 Mar 2022 at 14:26, Steven A. Falco > > > wrote: > > > > > > > > There is a new FTBFS for KiCad [1]. I filed an issue with > > > > KiCad > > > [2] and got a comment from the project leader: > > > > > > > > This looks like cmake issue to me. For some reason cmake > > > > is > > > creating an incorrect build folder: > > > > > > > > -- Build files have been written to: > > > /builddir/build/BUILD/kicad-6.0.2 > > > > > > > > so the build command: > > > > > > > > + /usr/bin/cmake --build redhat-linux-build -j6 --verbose > > > > > > > > cannot find the redhat-linux-build folder that was passed > > > > on > > > the cmake command line. > > > > > > > > In the last successful build, we have: > > > > > > > > > > > -- Build files have been written to: > > > /builddir/build/BUILD/kicad-6.0.2/redhat-linux-build > > > > + /usr/bin/cmake --build redhat-linux-build -j6 --verbose > > > > > > > > For some reason, the build file directory has changed: > > > > > > > > Success case: /builddir/build/BUILD/kicad-6.0.2/redhat-linux- > > > build > > > > Failure case: /builddir/build/BUILD/kicad-6.0.2 > > > > > > > > Is this a bug in cmake or did something in RPM macros change? > > > > > > Whatever it is seems to have broken a number of packages, > > > including > > > > > > FlightCrew, csdiff, libphonenumber, ledger, blas > > > > > > Those are just the ones that need to be rebuilt for a new Boost > > > and > > > so > > > were tested by Tom Rodgers, there are probably a lot more that he > > > didn't find. > > > > > > The ones I've checked all do "%cmake ." or "%cmake some_dir" > > > > > > Some fail during the %cmake step, and some fail during > > > %cmake_build. > > > > > > > > > > > > These are the CMake related issues I've encountered thus far - > > > > FlightCrew: FTBFS # CMake Error: The source directory > > "/builddir/build/BUILD/FlightCrew-0.9.1/build" does not appear to > > contain CMakeLists.txt. > > csdiff: FTBFS # Make Error: The source directory > > "/builddir/build/BUILD/csdiff-2.2.0/x86_64-redhat-linux-gnu" does > > not appear to contain CMakeLists.txt. > > ledger: FTBFS # Error: /builddir/build/BUILD/ledger-3.2.1/redhat- > > linux-build is not a directory > > liblas: FTBFS # Error: /builddir/build/BUILD/libLAS- > > d76a061f33a69a36ab116cd939c5d444b301efd8/redhat-linux-build is not > > a directory > > > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure -- Sérgio M. B. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Can't fedpkg new-sources (403)
On Wed, Mar 16, 2022 at 01:55:03PM -0400, Neal Becker wrote: > On Wed, Mar 16, 2022 at 1:45 PM Neal Becker wrote: > > > > > > > On Wed, Mar 16, 2022 at 1:38 PM Neal Becker wrote: > > > >> I believe it is failing on the line: > >> File "/usr/lib/python3.10/site-packages/pyrpkg/lookaside.py", line 298, > >> in upload > >> if self.remote_file_exists(name, filename, hash): > >> File "/usr/lib/python3.10/site-packages/pyrpkg/lookaside.py", line 259, > >> in remote_file_exists > >> self.raise_upload_error(status) > >> > >> So maybe the file already exists in the cache? But then, sources has not > >> been updated, and if I try > >> fedpkg local it will attempt to build the old version 1.8.1, not the new > >> 1.9.0. > >> > >> > > > OK, so unuran-1.9.0.tar.gz already exists in the cache. So I had to > > manually update sources by running > > md5sum unuran-1.9.0.tar.gz, which luckily I just guessed. Now everything > > seems to be working fine. > > > > Ooops, spoke too soon. > fedpkg local > Downloading unuran-1.9.0.tar.gz > > 100.0% > Remove downloaded invalid file > /home/nbecker/fedora.git/unuran/unuran-1.9.0.tar.gz > Could not execute local: Server returned status code 404 > > No idea what's going on here. You seem to have gotten a kerberos ticket for: nbec...@fedoraproject.org which I guess ipa is fine with giving you. However, our upload script checking your username sees "NBECKER" and not 'nbecker' and denys you. Can you do: kdestroy -A then kinit nbec...@fedoraproject.org and see if it works? kevin signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: FESCo wants to know what you use i686 packages for
On Wed, Mar 16, 2022 at 1:37 PM Zbigniew Jędrzejewski-Szmek
wrote:
>
> On Wed, Mar 16, 2022 at 12:54:23PM -0400, Josh Boyer wrote:
> > On Wed, Mar 16, 2022 at 11:55 AM Zbigniew Jędrzejewski-Szmek
> > wrote:
> > >
> > > On Wed, Mar 16, 2022 at 09:54:12AM -0400, David Cantrell wrote:
> > > > If you use i686 packages for something now, please respond to this
> > > > thread.
> > >
> > > I use i686 versions of libraries to do local 32-bit builds of C
> > > software I'm developing. (Something like 'sudo dnf install
> > > lib{one,two}-devel.i686 &&
> > > meson build-32 -Dc_args=-m32 -Dc_link_args=-m32 -Dcpp_args=-m32
> > > -Dcpp_link_args=-m32
> > > --pkg-config-path=/usr/lib/pkgconfig && ninja -C build-32' .)
> > >
> > > So I'd be interesting in keeping 32-bit versions of all BuildRequires for
> > > systemd.
> >
> > Who uses those builds and what do they use them for?
>
> They are purely local. I use them to compile and run tests locally so
> I know that the code works correctly on 32-bit. I'll also do test
> builds on arm/arm64/ppc64/riscv/anything-else-that-I-can-lay my hand on.
Are you aware of any upstream users of 32-bit systemd? Or some other
distro that requires it?
I ask because I see several responses along the same lines (I use it
to build 32-bit packages), but unless *Fedora* uses those resulting
32-bit builds it seems like an odd reason to keep i686 around. Yes,
being able to build for i686 means you need i686 but the root of the
question is why do you need to build for i686?
If there are other distros that still support 32-bit systemd, could
you do your 32-bit build and test against those instead?
josh
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Re: Can't fedpkg new-sources (403)
On Wed, Mar 16, 2022 at 1:45 PM Neal Becker wrote: > > > On Wed, Mar 16, 2022 at 1:38 PM Neal Becker wrote: > >> I believe it is failing on the line: >> File "/usr/lib/python3.10/site-packages/pyrpkg/lookaside.py", line 298, >> in upload >> if self.remote_file_exists(name, filename, hash): >> File "/usr/lib/python3.10/site-packages/pyrpkg/lookaside.py", line 259, >> in remote_file_exists >> self.raise_upload_error(status) >> >> So maybe the file already exists in the cache? But then, sources has not >> been updated, and if I try >> fedpkg local it will attempt to build the old version 1.8.1, not the new >> 1.9.0. >> >> > OK, so unuran-1.9.0.tar.gz already exists in the cache. So I had to > manually update sources by running > md5sum unuran-1.9.0.tar.gz, which luckily I just guessed. Now everything > seems to be working fine. > Ooops, spoke too soon. fedpkg local Downloading unuran-1.9.0.tar.gz 100.0% Remove downloaded invalid file /home/nbecker/fedora.git/unuran/unuran-1.9.0.tar.gz Could not execute local: Server returned status code 404 No idea what's going on here. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Can't fedpkg new-sources (403)
On Wed, Mar 16, 2022 at 1:38 PM Neal Becker wrote: > I believe it is failing on the line: > File "/usr/lib/python3.10/site-packages/pyrpkg/lookaside.py", line 298, > in upload > if self.remote_file_exists(name, filename, hash): > File "/usr/lib/python3.10/site-packages/pyrpkg/lookaside.py", line 259, > in remote_file_exists > self.raise_upload_error(status) > > So maybe the file already exists in the cache? But then, sources has not > been updated, and if I try > fedpkg local it will attempt to build the old version 1.8.1, not the new > 1.9.0. > > >>> OK, so unuran-1.9.0.tar.gz already exists in the cache. So I had to manually update sources by running md5sum unuran-1.9.0.tar.gz, which luckily I just guessed. Now everything seems to be working fine. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Can't fedpkg new-sources (403)
I believe it is failing on the line: File "/usr/lib/python3.10/site-packages/pyrpkg/lookaside.py", line 298, in upload if self.remote_file_exists(name, filename, hash): File "/usr/lib/python3.10/site-packages/pyrpkg/lookaside.py", line 259, in remote_file_exists self.raise_upload_error(status) So maybe the file already exists in the cache? But then, sources has not been updated, and if I try fedpkg local it will attempt to build the old version 1.8.1, not the new 1.9.0. On Wed, Mar 16, 2022 at 11:44 AM Neal Becker wrote: > > > On Wed, Mar 16, 2022 at 11:28 AM Ankur Sinha > wrote: > >> On Wed, Mar 16, 2022 10:46:43 -0400, Neal Becker wrote: >> > Sorry if this is a duplicate message, previous one was held for >> moderation. >> > >> > $ fedpkg new-sources ~/Downloads/unuran-1.9.0.tar.gz >> > Could not execute new_sources: Fail to upload files. Server returns >> status 403 >> > >> > I haven't been active in packaging for some time, did I miss something? >> >> Another thing to check: did you run the kinit bit before trying the >> `new-sources`? >> >> ``` >> kinit @FEDORAPROJECT.ORG >> ``` >> > > Yes, without running kinit I got "not authorized" > -- *Those who don't understand recursion are doomed to repeat it* ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: FESCo wants to know what you use i686 packages for
On Wed, Mar 16, 2022 at 12:54:23PM -0400, Josh Boyer wrote:
> On Wed, Mar 16, 2022 at 11:55 AM Zbigniew Jędrzejewski-Szmek
> wrote:
> >
> > On Wed, Mar 16, 2022 at 09:54:12AM -0400, David Cantrell wrote:
> > > If you use i686 packages for something now, please respond to this thread.
> >
> > I use i686 versions of libraries to do local 32-bit builds of C
> > software I'm developing. (Something like 'sudo dnf install
> > lib{one,two}-devel.i686 &&
> > meson build-32 -Dc_args=-m32 -Dc_link_args=-m32 -Dcpp_args=-m32
> > -Dcpp_link_args=-m32
> > --pkg-config-path=/usr/lib/pkgconfig && ninja -C build-32' .)
> >
> > So I'd be interesting in keeping 32-bit versions of all BuildRequires for
> > systemd.
>
> Who uses those builds and what do they use them for?
They are purely local. I use them to compile and run tests locally so
I know that the code works correctly on 32-bit. I'll also do test
builds on arm/arm64/ppc64/riscv/anything-else-that-I-can-lay my hand on.
Zbyszek
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Re: FESCo wants to know what you use i686 packages for
On Wed, Mar 16, 2022 at 8:54 AM David Cantrell wrote: > > Hi, > > Our most recent FESCo meeting involved discussing the proposal to drop i686 > builds of jdk8,11,17 from Fedora 37 onward. The topic quickly changed to the > larger question of "what do people use i686 packages for?" As it turns out, I only use i686 packages to build kernel-tools. I am not sure why we didn't turn off kernel-tools for i686 when we turned off the kernel. I suppose someone could have been linking to libbpf or libtraceevent, though those have been separate packages for a while now. I actually had to turn off dynamic linking to libtraceevent because i686 would no longer build against it. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: FESCo wants to know what you use i686 packages for
On Wed, Mar 16, 2022 at 11:55 AM Zbigniew Jędrzejewski-Szmek
wrote:
>
> On Wed, Mar 16, 2022 at 09:54:12AM -0400, David Cantrell wrote:
> > If you use i686 packages for something now, please respond to this thread.
>
> I use i686 versions of libraries to do local 32-bit builds of C
> software I'm developing. (Something like 'sudo dnf install
> lib{one,two}-devel.i686 &&
> meson build-32 -Dc_args=-m32 -Dc_link_args=-m32 -Dcpp_args=-m32
> -Dcpp_link_args=-m32
> --pkg-config-path=/usr/lib/pkgconfig && ninja -C build-32' .)
>
> So I'd be interesting in keeping 32-bit versions of all BuildRequires for
> systemd.
Who uses those builds and what do they use them for?
josh
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Re: FESCo wants to know what you use i686 packages for
I have a bunch of old Loki game ports I'd prefer keep working. I also have some backburner projects that need enough 32-bit userspace to run old binary drivers, but tbh it's probably easier to just use like el7 for that at this point. To the extent we keep i686 builds [1] I really think they need to be emitted from a 64-bit toolchain. I'm sympathetic to the argument that you shouldn't run a 32-bit web browser anyway, so I don't care _so_ much about linking like firefox or webkit. But something like llvm finds its way into the runtime for a lot of things, like the GL drivers that provide the compatibility with the game you're trying to run, and it's goofy to need to work around 32-bit address space limitations just to link a 32-bit libLLVM. Building with gcc.i686 is a choice we don't need to make. [1] - My personal opinion here is we should try a little harder than necessary, because I think that kind of compatibility is a worthwhile goal, but also the specific things you need the compatibility have boundaries and 100% coverage for 32-bit builds is pointless. - ajax On Wed, Mar 16, 2022 at 9:54 AM David Cantrell wrote: > > Hi, > > Our most recent FESCo meeting involved discussing the proposal to drop i686 > builds of jdk8,11,17 from Fedora 37 onward. The topic quickly changed to the > larger question of "what do people use i686 packages for?" > > Rather than guess, we wanted to ask the community what you use i686 packages > for in Fedora. There are no wrong answers here. We are seeking information. > > Why? Since the removal of the i686 kernel in Fedora, we want to reduce the > number of i686 packages provided in the repo. As time marches on, the ability > to build a lot of things for i686 becomes unrealistic or even impossible. > Remember it goes beyond providing builds...providing support, bug fixes, and > security fixes for those packages too. Maybe some things using i686 packages > now can move to x86_64 packages. We do not know yet, but a goal is to figure > out what packages, if anything, can drop their i686 builds. > > NOTE: Nothing is changing now. We are in an information gathering phase. > > > If you use i686 packages for something now, please respond to this thread. > > Thanks, > > -- > David Cantrell > Red Hat, Inc. | Boston, MA | EST5EDT > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: FESCo wants to know what you use i686 packages for
Felix Schwarz writes: > I use wine and lutris (+ 32bit mingw packages). Yes, same here ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora-36-20220316.n.0 compose check report
No missing expected images. Failed openQA tests: 12/229 (x86_64), 8/152 (aarch64) New failures (same test not failed in Fedora-36-20220315.n.0): ID: 1177619 Test: x86_64 Server-dvd-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/1177619 ID: 1177723 Test: x86_64 Silverblue-dvd_ostree-iso desktop_background URL: https://openqa.fedoraproject.org/tests/1177723 ID: 1177728 Test: x86_64 Cloud_Base-qcow2-qcow2 base_system_logging URL: https://openqa.fedoraproject.org/tests/1177728 ID: 1177739 Test: aarch64 Server-dvd-iso install_resize_lvm@uefi URL: https://openqa.fedoraproject.org/tests/1177739 ID: 1177761 Test: aarch64 Server-dvd-iso server_cockpit_basic@uefi URL: https://openqa.fedoraproject.org/tests/1177761 ID: 1177908 Test: x86_64 universal upgrade_2_minimal_uefi@uefi URL: https://openqa.fedoraproject.org/tests/1177908 Old failures (same test failed in Fedora-36-20220315.n.0): ID: 1177667 Test: x86_64 Workstation-live-iso apps_startstop URL: https://openqa.fedoraproject.org/tests/1177667 ID: 1177705 Test: x86_64 KDE-live-iso apps_startstop URL: https://openqa.fedoraproject.org/tests/1177705 ID: 1177714 Test: x86_64 Silverblue-dvd_ostree-iso evince URL: https://openqa.fedoraproject.org/tests/1177714 ID: 1177803 Test: aarch64 Workstation-raw_xz-raw.xz gnome_text_editor@uefi URL: https://openqa.fedoraproject.org/tests/1177803 ID: 1177805 Test: aarch64 Workstation-raw_xz-raw.xz desktop_update_graphical@uefi URL: https://openqa.fedoraproject.org/tests/1177805 ID: 1177826 Test: x86_64 Workstation-upgrade gnome_text_editor URL: https://openqa.fedoraproject.org/tests/1177826 ID: 1177827 Test: x86_64 Workstation-upgrade apps_startstop URL: https://openqa.fedoraproject.org/tests/1177827 ID: 1177830 Test: x86_64 Workstation-upgrade desktop_update_graphical URL: https://openqa.fedoraproject.org/tests/1177830 ID: 1177846 Test: aarch64 Workstation-upgrade gnome_text_editor@uefi URL: https://openqa.fedoraproject.org/tests/1177846 ID: 1177849 Test: aarch64 Workstation-upgrade desktop_update_graphical@uefi URL: https://openqa.fedoraproject.org/tests/1177849 ID: 1177880 Test: x86_64 universal install_arabic_language URL: https://openqa.fedoraproject.org/tests/1177880 ID: 1177881 Test: x86_64 universal install_asian_language URL: https://openqa.fedoraproject.org/tests/1177881 ID: 1177946 Test: aarch64 universal install_arabic_language@uefi URL: https://openqa.fedoraproject.org/tests/1177946 ID: 1177954 Test: aarch64 universal install_asian_language@uefi URL: https://openqa.fedoraproject.org/tests/1177954 Soft failed openQA tests: 8/229 (x86_64), 5/152 (aarch64) (Tests completed, but using a workaround for a known bug) Old soft failures (same test soft failed in Fedora-36-20220315.n.0): ID: 1177670 Test: x86_64 Workstation-live-iso desktop_browser URL: https://openqa.fedoraproject.org/tests/1177670 ID: 1177682 Test: x86_64 Workstation-live-iso eog URL: https://openqa.fedoraproject.org/tests/1177682 ID: 1177701 Test: x86_64 KDE-live-iso desktop_browser URL: https://openqa.fedoraproject.org/tests/1177701 ID: 1177712 Test: x86_64 Silverblue-dvd_ostree-iso eog URL: https://openqa.fedoraproject.org/tests/1177712 ID: 1177717 Test: x86_64 Silverblue-dvd_ostree-iso gnome_text_editor URL: https://openqa.fedoraproject.org/tests/1177717 ID: 1177720 Test: x86_64 Silverblue-dvd_ostree-iso desktop_browser URL: https://openqa.fedoraproject.org/tests/1177720 ID: 1177730 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/1177730 ID: 1177797 Test: aarch64 Workstation-raw_xz-raw.xz eog@uefi URL: https://openqa.fedoraproject.org/tests/1177797 ID: 1177801 Test: aarch64 Workstation-raw_xz-raw.xz desktop_browser@uefi URL: https://openqa.fedoraproject.org/tests/1177801 ID: 1177812 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi URL: https://openqa.fedoraproject.org/tests/1177812 ID: 1177819 Test: x86_64 Workstation-upgrade desktop_browser URL: https://openqa.fedoraproject.org/tests/1177819 ID: 1177840 Test: aarch64 Workstation-upgrade eog@uefi URL: https://openqa.fedoraproject.org/tests/1177840 ID: 1177845 Test: aarch64 Workstation-upgrade desktop_browser@uefi URL: https://openqa.fedoraproject.org/tests/1177845 Passed openQA tests: 209/229 (x86_64), 139/152 (aarch64) New passes (same test not passed in Fedora-36-20220315.n.0): ID: 1177663 Test: x86_64 Workstation-live-iso desktop_notifications_live URL: https://openqa.fedoraproject.org/tests/1177663 ID: 1177750 Test: aarch64 Server-dvd-iso install_repository_hd_variation@uefi URL: https://openqa.fedoraproject.org/tests/1177750 ID: 1177753 Test: aarch64 Server-dvd-iso support_server@uefi URL: https://openqa.fedoraproject.org/tests/1177753 ID: 1177766 Test: aarch64 Server-dvd-iso install_repository_nfsiso_variation@uefi URL: https://openqa.fedoraproject.org/tests/11777
Re: FESCo wants to know what you use i686 packages for
On Wed, Mar 16, 2022 at 09:54:12AM -0400, David Cantrell wrote:
> If you use i686 packages for something now, please respond to this thread.
I use i686 versions of libraries to do local 32-bit builds of C
software I'm developing. (Something like 'sudo dnf install
lib{one,two}-devel.i686 &&
meson build-32 -Dc_args=-m32 -Dc_link_args=-m32 -Dcpp_args=-m32
-Dcpp_link_args=-m32
--pkg-config-path=/usr/lib/pkgconfig && ninja -C build-32' .)
So I'd be interesting in keeping 32-bit versions of all BuildRequires for
systemd.
Zbyszek
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Re: Can't fedpkg new-sources (403)
On Wed, Mar 16, 2022 at 11:28 AM Ankur Sinha wrote: > On Wed, Mar 16, 2022 10:46:43 -0400, Neal Becker wrote: > > Sorry if this is a duplicate message, previous one was held for > moderation. > > > > $ fedpkg new-sources ~/Downloads/unuran-1.9.0.tar.gz > > Could not execute new_sources: Fail to upload files. Server returns > status 403 > > > > I haven't been active in packaging for some time, did I miss something? > > Another thing to check: did you run the kinit bit before trying the > `new-sources`? > > ``` > kinit @FEDORAPROJECT.ORG > ``` > Yes, without running kinit I got "not authorized" ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Can't fedpkg new-sources (403)
On Wed, Mar 16, 2022 10:46:43 -0400, Neal Becker wrote: > Sorry if this is a duplicate message, previous one was held for moderation. > > $ fedpkg new-sources ~/Downloads/unuran-1.9.0.tar.gz > Could not execute new_sources: Fail to upload files. Server returns status 403 > > I haven't been active in packaging for some time, did I miss something? Another thing to check: did you run the kinit bit before trying the `new-sources`? ``` kinit @FEDORAPROJECT.ORG ``` -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: FESCo wants to know what you use i686 packages for
On Wed, 2022-03-16 at 15:24 +0100, Jakub Jelinek wrote:
> On Wed, Mar 16, 2022 at 09:54:12AM -0400, David Cantrell wrote:
> > If you use i686 packages for something now, please respond to this thread.
>
> I use {glibc{,-devel,-static},{gmp,mpfr,libmpc}{,-devel}}.i686 for
> development and testing of GCC, even in Fedora packages I'd strongly prefer
> to keep the -m32 support around which also requires at least those packages
> (well, currently it requires far more so that it can build documentation
> etc.).
Same here :)
BR,
Ali
-
Intel Finland Oy
Registered Address: PL 281, 00181 Helsinki
Business Identity Code: 0357606 - 4
Domiciled in Helsinki
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Re: Can't fedpkg new-sources (403)
On Wed, Mar 16, 2022 at 10:57 AM Alexander Sosedkin
wrote:
> On Wed, Mar 16, 2022 at 3:47 PM Neal Becker wrote:
> >
> > Sorry if this is a duplicate message, previous one was held for
> moderation.
> >
> > $ fedpkg new-sources ~/Downloads/unuran-1.9.0.tar.gz
> > Could not execute new_sources: Fail to upload files. Server returns
> status 403
> >
> > I haven't been active in packaging for some time, did I miss something?
>
> Just a guess, but given how new-sources also updates at least .gitignore,
> I think it expects maintainers to have the file in the checkout.
> Does it fail the same if you place it there and pass a relative filepath?
> fedpkg new-sources unuran-1.9.0.tar.gz
fedpkg --verbose new-sources unuran-1.9.0.tar.gz
Creating repo object from /home/nbecker/fedora.git/unuran
Could not execute new_sources: Fail to upload files. Server returns status
403
Traceback (most recent call last):
File "/usr/bin/fedpkg", line 33, in
sys.exit(load_entry_point('fedpkg==1.42', 'console_scripts',
'fedpkg')())
File "/usr/lib/python3.10/site-packages/fedpkg/__main__.py", line 89, in
main
sys.exit(client.args.command())
File "/usr/lib/python3.10/site-packages/pyrpkg/cli.py", line 2688, in
new_sources
self.cmd.upload(
File "/usr/lib/python3.10/site-packages/pyrpkg/__init__.py", line 3078,
in upload
self.lookasidecache.upload(
File "/usr/lib/python3.10/site-packages/pyrpkg/lookaside.py", line 298,
in upload
if self.remote_file_exists(name, filename, hash):
File "/usr/lib/python3.10/site-packages/pyrpkg/lookaside.py", line 259,
in remote_file_exists
self.raise_upload_error(status)
File "/usr/lib/python3.10/site-packages/pyrpkg/lookaside.py", line 128,
in raise_upload_error
raise UploadError(message, http_status=http_status)
pyrpkg.errors.UploadError: Fail to upload files. Server returns status 403
>
> --
*Those who don't understand recursion are doomed to repeat it*
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Re: FESCo wants to know what you use i686 packages for
If you use i686 packages for something now, please respond to this thread. I use glibc.i686 and libgcc.i686 to support customers whose i686 machines have not yet died. (Some are about 12 years old, and expected live another 3 years. The ability to use almost 4GB of address space when running ELF.i686 on Linux.x86_64 has provided room for data growth.) I build the software by using cross-platform tools not packaged in Fedora, and the -m32 option of gcc.x86_64. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: FESCo wants to know what you use i686 packages for
I'm not sure if I use any i686 executables, but I sure do use i686 builds of libraries for cross-compiling. By which I mean both i686-linux and i686-win32. A.FI. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Can't fedpkg new-sources (403)
On Wed, Mar 16, 2022 at 3:47 PM Neal Becker wrote: > > Sorry if this is a duplicate message, previous one was held for moderation. > > $ fedpkg new-sources ~/Downloads/unuran-1.9.0.tar.gz > Could not execute new_sources: Fail to upload files. Server returns status 403 > > I haven't been active in packaging for some time, did I miss something? Just a guess, but given how new-sources also updates at least .gitignore, I think it expects maintainers to have the file in the checkout. Does it fail the same if you place it there and pass a relative filepath? fedpkg new-sources unuran-1.9.0.tar.gz ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Can't fedpkg new-sources (403)
Sorry if this is a duplicate message, previous one was held for moderation. $ fedpkg new-sources ~/Downloads/unuran-1.9.0.tar.gz Could not execute new_sources: Fail to upload files. Server returns status 403 I haven't been active in packaging for some time, did I miss something? -- *Those who don't understand recursion are doomed to repeat it* ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora 36 compose report: 20220316.n.0 changes
OLD: Fedora-36-20220315.n.0 NEW: Fedora-36-20220316.n.0 = SUMMARY = Added images:0 Dropped images: 3 Added packages: 0 Dropped packages:1 Upgraded packages: 0 Downgraded packages: 0 Size of added packages: 0 B Size of dropped packages:574.63 KiB Size of upgraded packages: 0 B Size of downgraded packages: 0 B Size change of upgraded packages: 0 B Size change of downgraded packages: 0 B = ADDED IMAGES = = DROPPED IMAGES = Image: KDE raw-xz aarch64 Path: Spins/aarch64/images/Fedora-KDE-36-20220315.n.0.aarch64.raw.xz Image: Minimal raw-xz aarch64 Path: Spins/aarch64/images/Fedora-Minimal-36-20220315.n.0.aarch64.raw.xz Image: Container_Minimal_Base docker ppc64le Path: Container/ppc64le/images/Fedora-Container-Minimal-Base-36-20220315.n.0.ppc64le.tar.xz = ADDED PACKAGES = = DROPPED PACKAGES = Package: mozilla-lightbeam-2.1.0-9.fc36 Summary: An add-on for visualizing HTTP requests between websites in real time RPMs:mozilla-lightbeam Size:574.63 KiB = UPGRADED PACKAGES = = DOWNGRADED PACKAGES = ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: FESCo wants to know what you use i686 packages for
David Cantrell writes: > Why? Since the removal of the i686 kernel in Fedora, we want to > reduce the number of i686 packages provided in the repo. As time > marches on, the ability to build a lot of things for i686 becomes > unrealistic or even impossible. Remember it goes beyond providing > builds...providing support, bug fixes, and security fixes for those > packages too. Maybe some things using i686 packages now can move to > x86_64 packages. We do not know yet, but a goal is to figure out what > packages, if anything, can drop their i686 builds. > > NOTE: Nothing is changing now. We are in an information gathering > phase. > > If you use i686 packages for something now, please respond to this thread. Nothing that couldn't be cross-built and provided as an x86_64 package. I use wine, which as I understand it, requires 32-bit libraries to run 32-bit Windows binaries. Given the weakness of x86 ASLR, it makes sense to ensure most of the i686 packages aren't actually getting used (e.g., no browsers). At that point, seems like we'd be better off not building for the arch at all, and doing cross-builds from x86_64 for the packages that need it. Be well, --Robbie signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: FESCo wants to know what you use i686 packages for
On Wed, Mar 16, 2022 at 09:54:12AM -0400, David Cantrell wrote:
> If you use i686 packages for something now, please respond to this thread.
I use {glibc{,-devel,-static},{gmp,mpfr,libmpc}{,-devel}}.i686 for
development and testing of GCC, even in Fedora packages I'd strongly prefer
to keep the -m32 support around which also requires at least those packages
(well, currently it requires far more so that it can build documentation
etc.).
Jakub
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Re: Problem with cmake 3.23.0
One more package that FTBFS due to CMake issues - grive2: FTBFS # Error: /builddir/build/BUILD/grive2-0.5.1/redhat-linux-build is not a directory On Mon, Mar 14, 2022 at 2:22 PM Thomas Rodgers wrote: > > > > On Mon, Mar 14, 2022 at 4:37 AM Jonathan Wakely > wrote: > >> On Fri, 4 Mar 2022 at 14:26, Steven A. Falco >> wrote: >> > >> > There is a new FTBFS for KiCad [1]. I filed an issue with KiCad [2] >> and got a comment from the project leader: >> > >> > This looks like cmake issue to me. For some reason cmake is >> creating an incorrect build folder: >> > >> > -- Build files have been written to: >> /builddir/build/BUILD/kicad-6.0.2 >> > >> > so the build command: >> > >> > + /usr/bin/cmake --build redhat-linux-build -j6 --verbose >> > >> > cannot find the redhat-linux-build folder that was passed on the >> cmake command line. >> > >> > In the last successful build, we have: > > > >> >-- Build files have been written to: >> /builddir/build/BUILD/kicad-6.0.2/redhat-linux-build >> >+ /usr/bin/cmake --build redhat-linux-build -j6 --verbose >> > >> > For some reason, the build file directory has changed: >> > >> > Success case: /builddir/build/BUILD/kicad-6.0.2/redhat-linux-build >> > Failure case: /builddir/build/BUILD/kicad-6.0.2 >> > >> > Is this a bug in cmake or did something in RPM macros change? >> >> Whatever it is seems to have broken a number of packages, including >> >> FlightCrew, csdiff, libphonenumber, ledger, blas >> >> Those are just the ones that need to be rebuilt for a new Boost and so >> were tested by Tom Rodgers, there are probably a lot more that he >> didn't find. >> >> The ones I've checked all do "%cmake ." or "%cmake some_dir" >> >> Some fail during the %cmake step, and some fail during %cmake_build. >> >> > These are the CMake related issues I've encountered thus far - > > FlightCrew: FTBFS # CMake Error: The source directory > "/builddir/build/BUILD/FlightCrew-0.9.1/build" does not appear to contain > CMakeLists.txt. > csdiff: FTBFS # Make Error: The source directory > "/builddir/build/BUILD/csdiff-2.2.0/x86_64-redhat-linux-gnu" does not > appear to contain CMakeLists.txt. > ledger: FTBFS # Error: > /builddir/build/BUILD/ledger-3.2.1/redhat-linux-build is not a directory > liblas: FTBFS # Error: > /builddir/build/BUILD/libLAS-d76a061f33a69a36ab116cd939c5d444b301efd8/redhat-linux-build > is not a directory > > ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: FESCo wants to know what you use i686 packages for
On Wednesday, 16 March 2022 at 14:54, David Cantrell wrote: > Hi, > > Our most recent FESCo meeting involved discussing the proposal to drop i686 > builds of jdk8,11,17 from Fedora 37 onward. The topic quickly changed to the > larger question of "what do people use i686 packages for?" > > Rather than guess, we wanted to ask the community what you use i686 packages > for in Fedora. There are no wrong answers here. We are seeking information. > > Why? Since the removal of the i686 kernel in Fedora, we want to reduce the > number of i686 packages provided in the repo. As time marches on, the ability > to build a lot of things for i686 becomes unrealistic or even impossible. > Remember it goes beyond providing builds...providing support, bug fixes, and > security fixes for those packages too. Maybe some things using i686 packages > now can move to x86_64 packages. We do not know yet, but a goal is to figure > out what packages, if anything, can drop their i686 builds. > > NOTE: Nothing is changing now. We are in an information gathering phase. > > > If you use i686 packages for something now, please respond to this thread. I use the ancient Linux builds of Acrobat Reader and Adobe Air as well as Wine for some games. For Adobe Air, there's some hope for a 64-bit redistributable version since it was taken over by Harman: https://airsdk.harman.com/ , but we're still not there yet: https://github.com/airsdk/Adobe-Runtime-Support/issues/1267#issuecomment-944205763 Regards, Dominik -- Fedora https://getfedora.org | RPM Fusion http://rpmfusion.org There should be a science of discontent. People need hard times and oppression to develop psychic muscles. -- from "Collected Sayings of Muad'Dib" by the Princess Irulan ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: FESCo wants to know what you use i686 packages for
On 16. 03. 22 14:54, David Cantrell wrote: Hi, Our most recent FESCo meeting involved discussing the proposal to drop i686 builds of jdk8,11,17 from Fedora 37 onward. The topic quickly changed to the larger question of "what do people use i686 packages for?" Rather than guess, we wanted to ask the community what you use i686 packages for in Fedora. There are no wrong answers here. We are seeking information. Why? Since the removal of the i686 kernel in Fedora, we want to reduce the number of i686 packages provided in the repo. As time marches on, the ability to build a lot of things for i686 becomes unrealistic or even impossible. Remember it goes beyond providing builds...providing support, bug fixes, and security fixes for those packages too. Maybe some things using i686 packages now can move to x86_64 packages. We do not know yet, but a goal is to figure out what packages, if anything, can drop their i686 builds. NOTE: Nothing is changing now. We are in an information gathering phase. If you use i686 packages for something now, please respond to this thread. - I use i686 packages to build my i686 packages. - I (randomly) use i686 packages to build my noarch packages. - I use nosync.i686 to build my i686 packages in mock. - The printer driver for my Brother printer is provided as i386 RPM, but I don't know if I need that, as it doesn't work currently anyway :( -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: FESCo wants to know what you use i686 packages for
On 3/16/22 09:57 AM, Felix Schwarz wrote: I use wine and lutris (+ 32bit mingw packages). wine is also the big one for me. On my system, roughly 1000 executables (exe and dll) are PE32 (32 bit), and another 1000 executables are PE32+ (64 bit). Steve ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: FESCo wants to know what you use i686 packages for
On Wed, Mar 16, 2022 at 09:54:12AM -0400, David Cantrell wrote: > If you use i686 packages for something now, please respond to this thread. Steam requires some i686 libs, but frankly I haven't run it recently due to Stadia. -- Tomasz Torcz “God, root, what's the difference?” to...@pipebreaker.pl “God is more forgiving.” ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: FESCo wants to know what you use i686 packages for
I use wine and lutris (+ 32bit mingw packages). ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
FESCo wants to know what you use i686 packages for
Hi, Our most recent FESCo meeting involved discussing the proposal to drop i686 builds of jdk8,11,17 from Fedora 37 onward. The topic quickly changed to the larger question of "what do people use i686 packages for?" Rather than guess, we wanted to ask the community what you use i686 packages for in Fedora. There are no wrong answers here. We are seeking information. Why? Since the removal of the i686 kernel in Fedora, we want to reduce the number of i686 packages provided in the repo. As time marches on, the ability to build a lot of things for i686 becomes unrealistic or even impossible. Remember it goes beyond providing builds...providing support, bug fixes, and security fixes for those packages too. Maybe some things using i686 packages now can move to x86_64 packages. We do not know yet, but a goal is to figure out what packages, if anything, can drop their i686 builds. NOTE: Nothing is changing now. We are in an information gathering phase. If you use i686 packages for something now, please respond to this thread. Thanks, -- David Cantrell Red Hat, Inc. | Boston, MA | EST5EDT ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: F37 Change: Curl-minimal as default (System-Wide Change proposal)
On Wed, Mar 16, 2022 at 08:06:34AM -0400, Neal Gompa wrote: > On Wed, Mar 16, 2022 at 7:50 AM Kamil Dudka wrote: > > > > On Wednesday, March 16, 2022 10:01:10 AM CET Paul Howarth wrote: > > > On Tue, 22 Feb 2022 12:00:06 -0500 > > > Ben Cotton wrote: > > > > > > > > > > https://fedoraproject.org/wiki/Changes/CurlMinimal_as_Default > > > > > > > > == Summary == > > > > `libcurl-minimal` and `curl-minimal` will be installed by default > > > > instead of `libcurl` and `curl`. > > > > The "minimal" variants provide only a subset of protocols (HTTP, > > > > HTTPS, FTP). The full versions can be explicitly requested as > > > > `libcurl-full` and `curl-full`. > > > > > > > > > Upstream's thoughts: > > > https://daniel.haxx.se/blog/2022/03/16/fedora-and-curl-minimal/ > > > > > > Paul. > > > > For completeness, here is a pull request by Miro Hrončok to change the > > packaging of curl to something that FESCO would like to have for the > > proposed Fedora change to be accepted: > > > > https://src.fedoraproject.org/rpms/curl/pull-request/14 > > > > Advantages: > > - libcurl-full can be automatically installed as a dependency in a dnf > > transaction without the need to use `--allowerasing` or `dnf swap`. > > > > Disadvantages: > > - It is incompatible with the current packaging used since RHEL-8. > > - It allows to install both libcurl-minimal and libcurl-full together. > > - It relies on complex RPM scriptlets to manipulate symlinks, which > > may misbehave in some corner cases, resulting in broken dnf stack. > > > > Can we just not do this at all? It seems even upstream is unhappy with > the proposal too. And frankly, if we do this, I will adjust *at least* > Fedora KDE to ship full curl because it's impossible for me to figure > out who will be broken by defaulting to minimal. I would also make the > same recommendation to Workstation and other desktop variants. > > I'm very sensitive to people considering Fedora as "broken by > default", especially as we're trying to bring new folks into Fedora. > And having *less* protocols than macOS and Windows curl by default is > very obviously a problem. We had that problem with OpenSSL for > *years*, but at least we had the whole "crypto software patents" thing > as a defense. > > This has no real defense. +1 -- David Cantrell Red Hat, Inc. | Boston, MA | EST5EDT ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora-Rawhide-20220316.n.0 compose check report
Missing expected images: Minimal raw-xz armhfp Compose FAILS proposed Rawhide gating check! 1 of 43 required tests failed openQA tests matching unsatisfied gating requirements shown with **GATING** below Failed openQA tests: 10/231 (x86_64), 16/161 (aarch64) New failures (same test not failed in Fedora-Rawhide-20220315.n.0): ID: 1177177 Test: x86_64 KDE-live-iso install_default@uefi **GATING** URL: https://openqa.fedoraproject.org/tests/1177177 ID: 1177183 Test: x86_64 KDE-live-iso apps_startstop URL: https://openqa.fedoraproject.org/tests/1177183 ID: 1177340 Test: aarch64 Workstation-upgrade desktop_terminal@uefi URL: https://openqa.fedoraproject.org/tests/1177340 ID: 1177368 Test: x86_64 universal upgrade_server_domain_controller URL: https://openqa.fedoraproject.org/tests/1177368 ID: 1177373 Test: x86_64 universal upgrade_realmd_client URL: https://openqa.fedoraproject.org/tests/1177373 ID: 1177377 Test: x86_64 universal install_blivet_lvmthin@uefi URL: https://openqa.fedoraproject.org/tests/1177377 Old failures (same test failed in Fedora-Rawhide-20220315.n.0): ID: 1177188 Test: x86_64 Silverblue-dvd_ostree-iso install_default_upload URL: https://openqa.fedoraproject.org/tests/1177188 ID: 1177191 Test: x86_64 Silverblue-dvd_ostree-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/1177191 ID: 1177235 Test: aarch64 Server-dvd-iso server_cockpit_default@uefi URL: https://openqa.fedoraproject.org/tests/1177235 ID: 1177256 Test: aarch64 Server-dvd-iso mediakit_repoclosure@uefi URL: https://openqa.fedoraproject.org/tests/1177256 ID: 1177262 Test: aarch64 Server-dvd-iso server_realmd_join_kickstart@uefi URL: https://openqa.fedoraproject.org/tests/1177262 ID: 1177264 Test: aarch64 Server-dvd-iso realmd_join_sssd@uefi URL: https://openqa.fedoraproject.org/tests/1177264 ID: 1177290 Test: aarch64 Workstation-raw_xz-raw.xz desktop_browser@uefi URL: https://openqa.fedoraproject.org/tests/1177290 ID: 1177292 Test: aarch64 Workstation-raw_xz-raw.xz gnome_text_editor@uefi URL: https://openqa.fedoraproject.org/tests/1177292 ID: 1177294 Test: aarch64 Workstation-raw_xz-raw.xz desktop_update_graphical@uefi URL: https://openqa.fedoraproject.org/tests/1177294 ID: 1177320 Test: x86_64 Workstation-upgrade desktop_fprint URL: https://openqa.fedoraproject.org/tests/1177320 ID: 1177334 Test: aarch64 Workstation-upgrade desktop_browser@uefi URL: https://openqa.fedoraproject.org/tests/1177334 ID: 1177335 Test: aarch64 Workstation-upgrade gnome_text_editor@uefi URL: https://openqa.fedoraproject.org/tests/1177335 ID: 1177369 Test: x86_64 universal install_arabic_language URL: https://openqa.fedoraproject.org/tests/1177369 ID: 1177370 Test: x86_64 universal install_asian_language URL: https://openqa.fedoraproject.org/tests/1177370 ID: 1177435 Test: aarch64 universal install_arabic_language@uefi URL: https://openqa.fedoraproject.org/tests/1177435 ID: 1177442 Test: aarch64 universal upgrade_server_domain_controller@uefi URL: https://openqa.fedoraproject.org/tests/1177442 ID: 1177443 Test: aarch64 universal install_asian_language@uefi URL: https://openqa.fedoraproject.org/tests/1177443 ID: 1177445 Test: aarch64 universal upgrade_realmd_client@uefi URL: https://openqa.fedoraproject.org/tests/1177445 ID: 1177455 Test: aarch64 universal upgrade_2_server_domain_controller@uefi URL: https://openqa.fedoraproject.org/tests/1177455 ID: 1177457 Test: aarch64 universal upgrade_2_realmd_client@uefi URL: https://openqa.fedoraproject.org/tests/1177457 Soft failed openQA tests: 7/231 (x86_64), 3/161 (aarch64) (Tests completed, but using a workaround for a known bug) New soft failures (same test not soft failed in Fedora-Rawhide-20220315.n.0): ID: 1177145 Test: x86_64 Workstation-live-iso apps_startstop URL: https://openqa.fedoraproject.org/tests/1177145 ID: 1177316 Test: x86_64 Workstation-upgrade apps_startstop URL: https://openqa.fedoraproject.org/tests/1177316 Old soft failures (same test soft failed in Fedora-Rawhide-20220315.n.0): ID: 1177148 Test: x86_64 Workstation-live-iso desktop_browser URL: https://openqa.fedoraproject.org/tests/1177148 ID: 1177160 Test: x86_64 Workstation-live-iso eog URL: https://openqa.fedoraproject.org/tests/1177160 ID: 1177179 Test: x86_64 KDE-live-iso desktop_browser URL: https://openqa.fedoraproject.org/tests/1177179 ID: 1177207 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi URL: https://openqa.fedoraproject.org/tests/1177207 ID: 1177286 Test: aarch64 Workstation-raw_xz-raw.xz eog@uefi URL: https://openqa.fedoraproject.org/tests/1177286 ID: 1177301 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi URL: https://openqa.fedoraproject.org/tests/1177301 ID: 1177308 Test: x86_64 Workstation-upgrade desktop_browser URL: https://openqa.fedoraproject.org/tests/1177308 ID: 1177329 Test: aarch64 Workstation-upgrade eog@uefi URL: https
Non-responsive maintainer check for snirkel
As per: https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/ Does anyone know how to reach Linux Walleij (snirkel)? This bug and pull request opened two years ago is still not addressed: https://bugzilla.redhat.com/show_bug.cgi?id=1800905 https://src.fedoraproject.org/rpms/libbinio/pull-request/1 (libbinio: update to fix off-by-one error in binisstream, libbinio fails to use memoryobjects) Other stale bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1989761 (libmtp: FC34 stopped showing files and folders on my Android tablet) https://bugzilla.redhat.com/show_bug.cgi?id=1971318 (libmtp: Galaxy Samsung Android can not be mounted) Thanks. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: F37 Change: Curl-minimal as default (System-Wide Change proposal)
On Wed, Mar 16, 2022 at 7:50 AM Kamil Dudka wrote: > > On Wednesday, March 16, 2022 10:01:10 AM CET Paul Howarth wrote: > > On Tue, 22 Feb 2022 12:00:06 -0500 > > Ben Cotton wrote: > > > > > > > https://fedoraproject.org/wiki/Changes/CurlMinimal_as_Default > > > > > > == Summary == > > > `libcurl-minimal` and `curl-minimal` will be installed by default > > > instead of `libcurl` and `curl`. > > > The "minimal" variants provide only a subset of protocols (HTTP, > > > HTTPS, FTP). The full versions can be explicitly requested as > > > `libcurl-full` and `curl-full`. > > > > > > Upstream's thoughts: > > https://daniel.haxx.se/blog/2022/03/16/fedora-and-curl-minimal/ > > > > Paul. > > For completeness, here is a pull request by Miro Hrončok to change the > packaging of curl to something that FESCO would like to have for the > proposed Fedora change to be accepted: > > https://src.fedoraproject.org/rpms/curl/pull-request/14 > > Advantages: > - libcurl-full can be automatically installed as a dependency in a dnf > transaction without the need to use `--allowerasing` or `dnf swap`. > > Disadvantages: > - It is incompatible with the current packaging used since RHEL-8. > - It allows to install both libcurl-minimal and libcurl-full together. > - It relies on complex RPM scriptlets to manipulate symlinks, which > may misbehave in some corner cases, resulting in broken dnf stack. > Can we just not do this at all? It seems even upstream is unhappy with the proposal too. And frankly, if we do this, I will adjust *at least* Fedora KDE to ship full curl because it's impossible for me to figure out who will be broken by defaulting to minimal. I would also make the same recommendation to Workstation and other desktop variants. I'm very sensitive to people considering Fedora as "broken by default", especially as we're trying to bring new folks into Fedora. And having *less* protocols than macOS and Windows curl by default is very obviously a problem. We had that problem with OpenSSL for *years*, but at least we had the whole "crypto software patents" thing as a defense. This has no real defense. -- 真実はいつも一つ！/ Always, there's only one truth! ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: F37 Change: Curl-minimal as default (System-Wide Change proposal)
On Wednesday, March 16, 2022 10:01:10 AM CET Paul Howarth wrote: > On Tue, 22 Feb 2022 12:00:06 -0500 > Ben Cotton wrote: > > > > https://fedoraproject.org/wiki/Changes/CurlMinimal_as_Default > > > > == Summary == > > `libcurl-minimal` and `curl-minimal` will be installed by default > > instead of `libcurl` and `curl`. > > The "minimal" variants provide only a subset of protocols (HTTP, > > HTTPS, FTP). The full versions can be explicitly requested as > > `libcurl-full` and `curl-full`. > > > Upstream's thoughts: > https://daniel.haxx.se/blog/2022/03/16/fedora-and-curl-minimal/ > > Paul. For completeness, here is a pull request by Miro Hrončok to change the packaging of curl to something that FESCO would like to have for the proposed Fedora change to be accepted: https://src.fedoraproject.org/rpms/curl/pull-request/14 Advantages: - libcurl-full can be automatically installed as a dependency in a dnf transaction without the need to use `--allowerasing` or `dnf swap`. Disadvantages: - It is incompatible with the current packaging used since RHEL-8. - It allows to install both libcurl-minimal and libcurl-full together. - It relies on complex RPM scriptlets to manipulate symlinks, which may misbehave in some corner cases, resulting in broken dnf stack. Kamil ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora rawhide compose report: 20220316.n.0 changes
OLD: Fedora-Rawhide-20220315.n.0 NEW: Fedora-Rawhide-20220316.n.0 = SUMMARY = Added images:0 Dropped images: 0 Added packages: 6 Dropped packages:4 Upgraded packages: 123 Downgraded packages: 1 Size of added packages: 30.76 MiB Size of dropped packages:757.94 KiB Size of upgraded packages: 1.85 GiB Size of downgraded packages: 161.89 MiB Size change of upgraded packages: -71.15 MiB Size change of downgraded packages: 77.00 MiB = ADDED IMAGES = = DROPPED IMAGES = = ADDED PACKAGES = Package: biboumi-9.0-1.fc37 Summary: An XMPP gateway that connects to IRC servers RPMs:biboumi Size:1.36 MiB Package: calindori-21.12-1.fc37 Summary: Calendar application for Plasma Mobile RPMs:calindori Size:997.07 KiB Package: cri-tools-1.20.0-2.module_f37+14135+76060b13 Summary: CLI and validation tools for Container Runtime Interface RPMs:cri-tools Size:27.04 MiB Package: java-jd-decompiler-1.1.3-1.fc37 Summary: JAVA library having JAVA decompiler of "Java Decompiler project" RPMs:java-jd-decompiler java-jd-decompiler-core java-jd-decompiler-javadoc Size:1.35 MiB Package: python-accept-types-0.4.1-3.fc37 Summary: Use the correct accept type for an HTTP request RPMs:python3-accept-types Size:15.12 KiB Package: rust-pistoncore-window-0.47.1-1.fc37 Summary: Library for window abstraction RPMs:rust-pistoncore-window+default-devel rust-pistoncore-window-devel Size:22.47 KiB = DROPPED PACKAGES = Package: nautilus-image-converter-0.3.1-0.22.git430afce31.fc35 Summary: Nautilus extension to mass resize images RPMs:nautilus-image-converter Size:156.04 KiB Package: ssh-contact-0.7-20.fc36 Summary: Establish SSH connections to your IM contacts using Telepathy RPMs:ssh-contact Size:124.88 KiB Package: telepathy-idle-0.2.0-23.fc36 Summary: IRC connection manager for Telepathy RPMs:telepathy-idle Size:344.83 KiB Package: vorbisgain-0.36-31.fc36 Summary: Adds tags to Ogg Vorbis files to adjust the volume RPMs:vorbisgain Size:132.20 KiB = UPGRADED PACKAGES = Package: baobab-42~rc-1.fc37 Old package: baobab-42~beta-1.fc37 Summary: A graphical directory tree analyzer RPMs: baobab Size: 1.52 MiB Size change: 1.64 KiB Changelog: * Tue Mar 08 2022 David King - 42~rc-1 - Update to 42.rc Package: bmap-tools-3.6-4.fc37 Old package: bmap-tools-3.6-2.fc36 Summary: Tools to generate and flash sparse images using the "block map" (bmap) format RPMs: bmap-tools python3-bmaptools Size: 89.75 KiB Size change: 618 B Changelog: * Tue Mar 15 2022 Ali Erdinc Koroglu - 3.6-3 - Deprecated build dependency python3-nose removed * Tue Mar 15 2022 Ali Erdinc Koroglu - 3.6-4 - Missing zstd dependency added Package: ceph-2:17.1.0-0.3.28.g1b309fef.fc37 Old package: ceph-2:17.1.0-0.2.rc1.fc37 Summary: User space components of the Ceph file system RPMs: ceph ceph-base ceph-common ceph-fuse ceph-grafana-dashboards ceph-immutable-object-cache ceph-mds ceph-mgr ceph-mgr-cephadm ceph-mgr-dashboard ceph-mgr-diskprediction-local ceph-mgr-k8sevents ceph-mgr-modules-core ceph-mgr-rook ceph-mon ceph-osd ceph-prometheus-alerts ceph-radosgw ceph-resource-agents ceph-selinux ceph-test ceph-volume cephadm cephfs-java cephfs-mirror cephfs-shell cephfs-top libcephfs-devel libcephfs2 libcephfs_jni-devel libcephfs_jni1 libcephsqlite libcephsqlite-devel librados-devel librados2 libradospp-devel libradosstriper-devel libradosstriper1 librbd-devel librbd1 librgw-devel librgw2 python3-ceph-argparse python3-ceph-common python3-cephfs python3-rados python3-rbd python3-rgw rados-objclass-devel rbd-fuse rbd-mirror rbd-nbd Size: 335.39 MiB Size change: 31.19 KiB Package: composer-2.2.8-1.fc37 Old package: composer-2.2.7-1.fc37 Summary: Dependency Manager for PHP RPMs: composer Size: 458.51 KiB Size change: 789 B Changelog: * Tue Mar 15 2022 Remi Collet - 2.2.8-1 - update to 2.2.8 Package: cscppc-2.1.1-3.fc37 Old package: cscppc-2.1.1-2.fc36 Summary: A compiler wrapper that runs cppcheck in background RPMs: csclng cscppc csgcca csmatch Size: 4.95 MiB Size change: 10.55 KiB Changelog: * Tue Mar 15 2022 Kamil Dudka 2.1.1-3 - verify GPG signature of upstream tarball when building the package Package: csdiff-2.3.0-2.fc37 Old package: csdiff-2.2.0-2.fc36 Summary: Non-interactive tools for processing code scan results in plain-text RPMs: csdiff python3-csdiff Size: 4.55 MiB Size change: 44.92 KiB Changelog: * Tue Mar 15 2022 Kamil Dudka 2.3.0-1 - update to latest upstream release * Tue Mar 15 2022 Miro Hron??ok - 2.3.0-2 - Verify GPG signature of upstream tarball when building the package Package: csmock-3.3.1-2.fc37 Old package: csmock-3.3.0-2.fc36 Summary: A moc
Re: Donate 1 minute of your time to test upgrades from F35 to F36
On 15/03/2022 23:29, Ian Laurie wrote: Maybe the NVIDIA drivers were never working as such before, but somehow it was gracefully "falling back" to default drivers with the old kernel but not the new one? Enabled Secure Boot prevents the Linux kernel from loading all unsigned kernel modules such as NVIDIA drivers. You can check old logs with journalctl --list-boots. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Landing a larger-than-release change (distrusting SHA-1 signatures)
> On 16. Mar 2022, at 00:04, Tom Hughes via devel > wrote: > > On 15/03/2022 22:45, Robert Relyea wrote: > >> 1) in fedora 37, provide a policy that turns SHA-1 off. in our testing, we >> encourage people to run with that policy and write bugs against components. > > That policy already exists in Fedora 34 and 35 where the FUTURE policy > does not allow SHA1 in signature algorithms. In the case of OpenSSL, that only affects use of SHA1 as signature algorithms in TLS. It does not cover arbitrary signatures with a SHA1 digest, which is what we are proposing. HTH, Clemens -- Clemens Lang RHEL Crypto Team Red Hat ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: openssl maintainerships?
Dear Peter, We have created a bug https://bugzilla.redhat.com/show_bug.cgi?id=2047295 It doesn't look like an upstream OpenSSL bug for me. Personally I don't expect much effort in this direction because armv7 architecture looks to be deprecating. On Wed, Mar 16, 2022 at 11:11 AM Peter Robinson wrote: > On Wed, Mar 16, 2022 at 10:04 AM Dmitry Belyavskiy > wrote: > > > > Dear Peter, dear Miro, > > > > The immediate reason for the lack of update of OpenSSL in Fedora was a > problem with kTLS in avmv7. > > We tried to get some feedback but didn't succeed and are going to > disable kTLS in armv7. > > Is there a bug for this against openssl and linked to the arm > tracker[1], or did you post it to an upstream, either kernel or > openssl, to request assistance? If the later there should be a Fedora > bug with links to those so people can follow up. If there's bugs we > can get Arm to assist in solving arm specific problems but with out a > public bug we can't engage them. Even with disabling this please > outline the details and file a Fedora bug if you've not done so > already. > > > Now we are going to upgrade both F36 and rawhide to 3.0.2, I start > working on this. > > Great. > > > Sorry for any possible inconvenience. > > Please don't just let things sit because of one problem, things may > well get lost in people's inboxes if you do a single message to a > single person. It's generally not the way to get assistance. > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=245418 > > > On Wed, Mar 16, 2022 at 12:41 AM Miro Hrončok > wrote: > >> > >> On 15. 03. 22 22:27, Peter Robinson wrote: > >> > Hi Dmitry. > >> > > >> > It seems since the openssl 3 GA release back in September there's not > >> > been a single successful openssl build[1], and a number of bugs [2], > >> > and even more CVEs [3][4]. Why aren't these being dealt with in a semi > >> > reasonable fashion? The last actual successful build is now over 6 > >> > months ago. > >> > >> I am also curious why the OpenSSL version in CentOS Stream 9 is once > again > >> higher than in Fedora. > >> > >> -- > >> Miro Hrončok > >> -- > >> Phone: +420777974800 > >> IRC: mhroncok > >> > > > > > > -- > > Dmitry Belyavskiy > > -- Dmitry Belyavskiy ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: openssl maintainerships?
On Wed, Mar 16, 2022 at 10:04 AM Dmitry Belyavskiy wrote: > > Dear Peter, dear Miro, > > The immediate reason for the lack of update of OpenSSL in Fedora was a > problem with kTLS in avmv7. > We tried to get some feedback but didn't succeed and are going to disable > kTLS in armv7. Is there a bug for this against openssl and linked to the arm tracker[1], or did you post it to an upstream, either kernel or openssl, to request assistance? If the later there should be a Fedora bug with links to those so people can follow up. If there's bugs we can get Arm to assist in solving arm specific problems but with out a public bug we can't engage them. Even with disabling this please outline the details and file a Fedora bug if you've not done so already. > Now we are going to upgrade both F36 and rawhide to 3.0.2, I start working on > this. Great. > Sorry for any possible inconvenience. Please don't just let things sit because of one problem, things may well get lost in people's inboxes if you do a single message to a single person. It's generally not the way to get assistance. [1] https://bugzilla.redhat.com/show_bug.cgi?id=245418 > On Wed, Mar 16, 2022 at 12:41 AM Miro Hrončok wrote: >> >> On 15. 03. 22 22:27, Peter Robinson wrote: >> > Hi Dmitry. >> > >> > It seems since the openssl 3 GA release back in September there's not >> > been a single successful openssl build[1], and a number of bugs [2], >> > and even more CVEs [3][4]. Why aren't these being dealt with in a semi >> > reasonable fashion? The last actual successful build is now over 6 >> > months ago. >> >> I am also curious why the OpenSSL version in CentOS Stream 9 is once again >> higher than in Fedora. >> >> -- >> Miro Hrončok >> -- >> Phone: +420777974800 >> IRC: mhroncok >> > > > -- > Dmitry Belyavskiy ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: openssl maintainerships?
Dear Peter, dear Miro, The immediate reason for the lack of update of OpenSSL in Fedora was a problem with kTLS in avmv7. We tried to get some feedback but didn't succeed and are going to disable kTLS in armv7. Now we are going to upgrade both F36 and rawhide to 3.0.2, I start working on this. Sorry for any possible inconvenience. On Wed, Mar 16, 2022 at 12:41 AM Miro Hrončok wrote: > On 15. 03. 22 22:27, Peter Robinson wrote: > > Hi Dmitry. > > > > It seems since the openssl 3 GA release back in September there's not > > been a single successful openssl build[1], and a number of bugs [2], > > and even more CVEs [3][4]. Why aren't these being dealt with in a semi > > reasonable fashion? The last actual successful build is now over 6 > > months ago. > > I am also curious why the OpenSSL version in CentOS Stream 9 is once again > higher than in Fedora. > > -- > Miro Hrončok > -- > Phone: +420777974800 > IRC: mhroncok > > -- Dmitry Belyavskiy ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora-Cloud-34-20220316.0 compose check report
No missing expected images. Soft failed openQA tests: 1/8 (x86_64), 1/8 (aarch64) (Tests completed, but using a workaround for a known bug) Old soft failures (same test soft failed in Fedora-Cloud-34-20220315.0): ID: 1177069 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/1177069 ID: 1177075 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi URL: https://openqa.fedoraproject.org/tests/1177075 Passed openQA tests: 7/8 (x86_64), 7/8 (aarch64) -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Orphaned packages looking for new maintainers
Hello On Mon, 2022-03-07 at 10:46 +0100, Miro Hrončok wrote: > > > > Package (co)maintainers Status > > Change > > > > ... > > nodejs-backbone nodejs-sig, orphan, vjancik 0 weeks > > ago > > > This one has an interesting impact on Python packages. python3-notebook > requires js-backbone and hence the Orphaned packages report lists "too many > dependencies for nodejs-backbone". > > However, if this is retired, I know a way forward to re-bundle it in > python3-notebook, as does upstream. Unfortunately, it is not possible to do > it > before it is retired. I realized that too so I took this package like a week ago. BR, Ali - Intel Finland Oy Registered Address: PL 281, 00181 Helsinki Business Identity Code: 0357606 - 4 Domiciled in Helsinki This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: F37 Change: Curl-minimal as default (System-Wide Change proposal)
On Tue, 22 Feb 2022 12:00:06 -0500 Ben Cotton wrote: > https://fedoraproject.org/wiki/Changes/CurlMinimal_as_Default > > == Summary == > `libcurl-minimal` and `curl-minimal` will be installed by default > instead of `libcurl` and `curl`. > The "minimal" variants provide only a subset of protocols (HTTP, > HTTPS, FTP). The full versions can be explicitly requested as > `libcurl-full` and `curl-full`. Upstream's thoughts: https://daniel.haxx.se/blog/2022/03/16/fedora-and-curl-minimal/ Paul. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora-Cloud-35-20220316.0 compose check report
No missing expected images. Soft failed openQA tests: 1/8 (x86_64), 1/8 (aarch64) (Tests completed, but using a workaround for a known bug) Old soft failures (same test soft failed in Fedora-Cloud-35-20220315.0): ID: 1176973 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/1176973 ID: 1176979 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi URL: https://openqa.fedoraproject.org/tests/1176979 Passed openQA tests: 7/8 (x86_64), 7/8 (aarch64) -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
