Re: F37 Change: Curl-minimal as default (System-Wide Change proposal)
Am 24.02.22 um 19:35 schrieb Daniel P. Berrangé: On Thu, Feb 24, 2022 at 07:16:26PM +0100, Ralf Corsépius wrote: If someone is setting up a personal private mirror, I struggle to understand a reason why they would pick FTP over HTTP(S) today. Because an ftp server is much lighter and much easier to maintain than a fat httpd-server? Perhaps someone will have a FTP only mirror that's existed for years and simply haven't got around to enabling HTTP, but addressing that is not an unreasonable expectation. Almost. E.g. I am using a LAN-wide (anonymous-only) ftp server, I set up a long time ago and rarely touched since then. Using httpd-server would simply be overkill for this use-case. IMHO explicitly disabling FTP in dnf would be fine, as any fallout could be easily dealt with by enabling HTTP. Just ensure we announce such intent ahead of time via a Fedora feature proposal. I don't agree. Not using a protocol on public dnf-servers is on thing, but removing the "ftp" protocol everywhere is just silly fanatism, IMHO. Ralf ___ 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
Very late change for F36 release notes?
I just realized that the cobbler django web interface is not compatible with django 4.0 in Fedora 36. Upstream has dropped the web interface completely with cobbler 3.3 and so I've decided to update to that in Fedora 36. However, I do think this is worthy of a release note somewhere (not sure what section). Can this still be done? How? Do I file a PR here https://pagure.io/fedora-docs/release-notes ? Thanks. -- Orion Poplawski he/him/his - surely the least important thing about me IT Systems Manager 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane or...@nwra.com Boulder, CO 80301 https://www.nwra.com/ smime.p7s Description: S/MIME Cryptographic 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: Self Introduction: Yunmei Li
Hi, I have built Milvus package on Copr and reviewed it with Fedora-review. I fixed these items that are flagged as fail,but there are some items that are flagged as manual review needed. I am looking___ 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: s390x KOJI builders issue
In many cases, the build is killed during compilation itself. I'd understand the situation, if it would consistently fail somewhere during the testsuite on OOM errors, but it's weirder than that. Until now, I didn't have this issue. Why now? The tests are still important. Through the years I took several steps to reduce the resource usage for the testsuite. The most significant is that I ran the full testsuite only once or few times in scratch builds, and when I didn't find any issues worth investigating, I switch the testsuite to a minimal mode for every other build of the same minor versions. So e.g. mass rebuilds which only bump patch numbers in the NVR run only the 'main' suite. As well as other small patches during the life of that particular upstream release. The issue in general is: We have the majority of packages which are small and quick to build. Then we have a minority of insanely huge projects, whose resource thirst can never be quenched. :) Could we somehow just identify the huge packages, mark them in a special way, and when KOJI would pick up such marked packages, it would give it much more resources ? At the same time, the average amount of resources given should be lowered to only what most packages need. I believe all could benefit from this. Michal -- Michal Schorm Software Engineer Core Services - Databases Team Red Hat -- On Thu, Mar 3, 2022 at 1:05 AM Kevin Fenzi wrote: > > On Wed, Mar 02, 2022 at 03:54:32PM +0100, Florian Weimer wrote: > > * Michael Catanzaro: > > > > > On Wed, Mar 2 2022 at 02:21:22 PM +0100, Dan Horák > > > wrote: > > >> those are weird, the build tasks have been restarted many times by the > > >> builder daemon, after something crashed there (OOM?) ... > > > > > > This was happening to me on armv7hl a few weeks ago. Kevin Fenzi > > > investigated and discovered that the builds kept hitting an OOM > > > condition and then restarting, which triggered an infinite loop. Each > > > build would work for 3-5 hours before failing, then it would start > > > over, then again, then again > > > > > > I think some configuration changed recently on the builders, because I > > > had never seen this happen before last month. If a build hits OOM, it > > > really needs to fail immediately. It should not restart, because it's > > > likely to fail again the same way. My builds had restarted four or > > > five times before Kevin manually handled them. > > > > Maybe Koji restarts the build because the builder has rebooted? > > Nope. > > What happens is: > > * 10: Build is taken by builder and starts building. > * Build takes up more than 90% of memory+swap > * OOm killer looks and says... oh hey, I need to kill something. This > kojid process/slice is taking up all the memory. > * kojid is killed. > * kojid is restarted (we have it set to restart in unit) > * builder checks into hub > * hub says, hey you are doing task X right? > * builder says... oh, yes, let me start that. > * goto 10 > > So in this case it seems like it's the tests that are causing this. > The s390x kvm builders have 2cpus and 10gb of memory. > > So, is there any way to decrease memory usage there? > I see the tests have -parallel=auto perhaps that could be set to 1 or 2? > > Perhaps there's some way to adjust the oom killer to kill the build > instead of kojid? I would prefer that because then the build would > quickly fail and you could see it was killed and need to reduce memory > consumption somehow. > > I suppose we could look at reducing the number of builders and > increasing memory on fewer of them, but it's hard to know what the right > value is there. it's definitely better for mass rebuilds to have more > smaller builders. > > kevin > ___ > 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: Documentation for F15's "Remove SETUID" Change?
Hello, On Tuesday, March 1, 2022 6:43:57 PM EST Michel Alexandre Salim wrote: > The subject of setuid came up in a private conversation recently, and to my > surprise we don't seem to have it documented in the packaging guidelines: > > https://docs.fedoraproject.org/en-US/packaging-guidelines/ > > Per https://fedoraproject.org/wiki/Features/RemoveSETUID#Documentation > > "We should change documentation on packaging guidelines to talk about > using file capabilities." > > but the only mention of capabilities seem to be that, if you use it or > suid, PIE must be enabled: > > https://docs.fedoraproject.org/en-US/packaging-guidelines/#_pie > > Should this be documented somewhere, or if it's there but it's lost in > the wiki->docs migration, does anyone know where the documentation is? As someone involved in that change, the situation was much worse back in 2011. Almost everything was running as root. The inspection tools back then were non-existent, which is what I wrote pscap and netcap. Now, a lot of things use capabilities with a few still running as root when they don't need to be. But I have not looked at all daemons. The lesser used ones may need checking. But I think maybe some guidance could be good. Something like: In general, if the package has --with-libcap or --with-libcapng, turn that on. If a daemon can run as non-root with capabilities fix the config file to do that. If you have to give CAP_DAC_OVERRIDE to a daemon/application, you probably have file ownership problems. Depending on the nature of the problem, one solution for this is to use group permissions to allow access. One option for not running as root can be the systemd capabilities options if the app does not natively support capabilities. It should be noted that systemd does this by using ambient capabilities. Ambient capabilities have the property that any children also get the capabilities. And so does their children and on and on.This means that if the daemon is exploitable and the attacker launches a shell, the shell will also get the capabilities of the parent. This makes them a target for attack. Any app with ambient capabilities should specifically drop them first thing after startup. Dropping ambient capabilities does not drop the normal capabilities. However, apps that use the systemd capabilities do so because they are typically capability unaware. That means they are not likely to be able to drop ambient capabilities. One solution is to add LD_PRELOAD=/usr/ lib64/libdrop_ambient.so.0. It drops ambient capabilities in the library constructor so the app is defanged. I think the PIE thing should not be related to setuid or capabilities. The guidance now should be everything should be PIE and full RELRO. That should be reflected in the rpm-macros package. -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: s390x KOJI builders issue
On Wed, Mar 02, 2022 at 03:54:32PM +0100, Florian Weimer wrote: > * Michael Catanzaro: > > > On Wed, Mar 2 2022 at 02:21:22 PM +0100, Dan Horák > > wrote: > >> those are weird, the build tasks have been restarted many times by the > >> builder daemon, after something crashed there (OOM?) ... > > > > This was happening to me on armv7hl a few weeks ago. Kevin Fenzi > > investigated and discovered that the builds kept hitting an OOM > > condition and then restarting, which triggered an infinite loop. Each > > build would work for 3-5 hours before failing, then it would start > > over, then again, then again > > > > I think some configuration changed recently on the builders, because I > > had never seen this happen before last month. If a build hits OOM, it > > really needs to fail immediately. It should not restart, because it's > > likely to fail again the same way. My builds had restarted four or > > five times before Kevin manually handled them. > > Maybe Koji restarts the build because the builder has rebooted? Nope. What happens is: * 10: Build is taken by builder and starts building. * Build takes up more than 90% of memory+swap * OOm killer looks and says... oh hey, I need to kill something. This kojid process/slice is taking up all the memory. * kojid is killed. * kojid is restarted (we have it set to restart in unit) * builder checks into hub * hub says, hey you are doing task X right? * builder says... oh, yes, let me start that. * goto 10 So in this case it seems like it's the tests that are causing this. The s390x kvm builders have 2cpus and 10gb of memory. So, is there any way to decrease memory usage there? I see the tests have -parallel=auto perhaps that could be set to 1 or 2? Perhaps there's some way to adjust the oom killer to kill the build instead of kojid? I would prefer that because then the build would quickly fail and you could see it was killed and need to reduce memory consumption somehow. I suppose we could look at reducing the number of builders and increasing memory on fewer of them, but it's hard to know what the right value is there. it's definitely better for mass rebuilds to have more smaller builders. 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: Orphaning a set of packages
Hi! On Friday, 25 February 2022 at 11:50, Fabian Deutsch wrote: > Hey, > > due to the lack of time I'm orphaning the following set of packages: > > augeas-vala > clpeak Taken. I have some interest in OpenCL and I use this tool. > gimp-fourier-plugin > gocl > python-uinput > > Feel free to step up and take them. Thanks for your efforts maintaining them so far! 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
[Bug 2060186] New: perl-Devel-PPPort-3.66 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2060186 Bug ID: 2060186 Summary: perl-Devel-PPPort-3.66 is available Product: Fedora Version: rawhide Status: NEW Component: perl-Devel-PPPort Keywords: FutureFeature, Triaged Assignee: jples...@redhat.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: jples...@redhat.com, mspa...@redhat.com, perl-devel@lists.fedoraproject.org, ppi...@redhat.com Target Milestone: --- Classification: Fedora Latest upstream release: 3.66 Current version/release in rawhide: 3.64-1.fc36 URL: http://search.cpan.org/dist/Devel-PPPort/ Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from Anitya: https://release-monitoring.org/project/5760/ -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2060186 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2060185] perl-DateTime-1.56 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2060185 --- Comment #1 from Upstream Release Monitoring --- Scratch build failed. Details bellow: BuilderException: Build started, but failure happened during post build operations: Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-7my95iiu/perl-DateTime.spec']' returned non-zero exit status 1. StdOut: error: Bad source: ./DateTime-1.56.tar.gz: No such file or directory Traceback: File "/usr/local/lib/python3.9/site-packages/hotness/use_cases/package_scratch_build_use_case.py", line 56, in build result = self.builder.build(request.package, request.opts) File "/usr/local/lib/python3.9/site-packages/hotness/builders/koji.py", line 188, in build raise BuilderException( If you think this issue is caused by some bug in the-new-hotness, please report it on the-new-hotness issue tracker: https://github.com/fedora-infra/the-new-hotness/issues -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2060185 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2060185] New: perl-DateTime-1.56 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2060185 Bug ID: 2060185 Summary: perl-DateTime-1.56 is available Product: Fedora Version: rawhide Status: NEW Component: perl-DateTime Keywords: FutureFeature, Triaged Assignee: p...@city-fan.org Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: iarn...@gmail.com, p...@city-fan.org, perl-devel@lists.fedoraproject.org, st...@silug.org Target Milestone: --- Classification: Fedora Latest upstream release: 1.56 Current version/release in rawhide: 1.55-2.fc36 URL: http://search.cpan.org/dist/DateTime/ Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from Anitya: https://release-monitoring.org/project/2787/ -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2060185 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Chromium security bugs remain unfixed for > 1 month
Demi Marie Obenour wrote: > On 3/2/22 10:09, Tom Callaway wrote: >> Additionally, Fedora uses GCC (intentionally) which requires patch work >> for each release, but improves the quality of the resulting package. > > Would it be possible to make a one-off exception for Chromium? There is actually already a blanket allowance (it is not even an exception anymore) for packages to use Clang where upstream prefers it. The decision is ultimately up to the maintainer. Kevin Kofler ___ 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: Chromium security bugs remain unfixed for > 1 month
Demi Marie Obenour wrote: > Arch uses the upstream *source* code, but not the binaries, if I > understand correctly. They just don’t have anywhere near as many > patches as Fedora does. I suspect this is a combination of factors. > First, Arch builds use clang and more bundled libraries, so they are > more similar to what Google itself uses and break less often. Second, > Arch has zero problems with shipping patent-encumbered media codecs, as > (if I recall correctly) Arch is based in a nation where such patents > simply are not enforceable. So they can just use the codecs that > Chromium comes with already. Arch also has the AUR where there are plenty of "packages" that just repackage somebody else's binaries. They are a lot less strict about packaging only verifiably Free Software. But building from source is the only way to ensure that the binaries are actually compiled from that exact source code. (Then of course you also have to trust the compiler, but that is another story.) As for the issue of Chromium patches, well, they are all there for a reason: some due to legal requirements, some because Fedora (especially Rawhide) tends to ship a newer glibc than what upstream Google tested with, which tends to break their seccomp sandbox every so often, etc. (Note that QtWebEngine tends to have fewer patches than Chromium, also because Qt applies some of those patches in their bundled Chromium.) > Electron is going to be a nightmare for all sorts of other reasons, > starting with the need to rebuild all of the minified JavaScript, > CSS, and HTML from unminified source code. Electron is a pain in the neck and I do not want to spend my time packaging it, but it looks like we have a volunteer attempting it now. > Can Fedora just reuse the upstream QtWebEngine build scripts? What build scripts do you want to reuse? Of course we use the qmake (in Qt 5, CMake in Qt 6, but we do not have QtWebEngine 6 packaged yet) build system that they wrote. There are not really any upstream build scripts we can use beyond that. > What would it take to get tall of the users of QtWebEngine onto 6.2? I > don’t think Fedora should ship any version of QtWebEngine except the > latest, since only the latest version appears to get regular patches. Well, even 6.2 does not get patches as regularly as you expect. As I said, the CVEs you listed will be fixed in Qt 6.2.4, which is still not released yet. QtWebEngine 5.15 does also still get LTS releases with security fixes (and the LTS branches of QtWebEngine and its qtwebengine-chromium submodule are public and LGPL-licensed). Just not as frequently. Only when they release a Qt 5.15.x commercial LTS. And moving all the users to QtWebEngine 6 is not going to happen overnight, because it means moving them completely to Qt 6. In particular, if they use KF5 libraries, they will also need to move to the KF6 equivalents, and there is no KF6 release yet at all that they could move to. > Yeah, but for QtWebEngine I imagine much of the work is handled by The > Qt Company and Fedora can just reuse their build scripts. If you think a turnaround time of > 1 month for security fixes is too long, then we would have to do our own backports though, because 1+ month(s) is quite normal for the latest Qt branch, LTS branches are even slower. And rebasing QtWebEngine to a newer Chromium is even harder than backporting security fixes to the existing branch. Kevin Kofler ___ 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: Co-maintain gnome-shell-extension-freon
On Wed, 2 Mar 2022 at 23:44, Ben Beasley wrote: > Assuming you are already a packager, please follow this process: > > https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/ Excellent Ben, thanks. The bug is here: https://bugzilla.redhat.com/show_bug.cgi?id=2009382 It seems a bit rushed to actually ask to take the package over, I bet Audrey just has a bit busy schedule. Co-maintenance is the best solution. Audrey can you please add me as co-maintainer so I can update the package: https://src.fedoraproject.org/dashboard/projects Yours, Linus Walleij ___ 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: VERY late notification emails
On Tue, Mar 01, 2022 at 10:42:38AM +0100, Vít Ondruch wrote: > > Dne 28. 02. 22 v 18:24 Kevin Fenzi napsal(a): > > On Mon, Feb 28, 2022 at 07:45:27AM -0600, Richard Shaw wrote: > > > I almost wrote this a week ago but decided not to as it's been recently > > > discussed but this is really annoying. 6 days later is more than useless. > > > > > > Previously it was blamed, at least partially, on the mass rebuild, but > > > clearly that should no longer be an issue by now? > > Well, I noted a number of reasons for it... one of them was that it > > sometimes crashes, but appears to be processing. This happened a few > > days ago and it was just restarted this morning. ;( > > > Is it down again? Or does it trying to catch up? If the status of the queue > was visible somewhere at least. I am asking, because the latest notification > I have ATM is from 22nd. Well, thats not really too helpfull a question. I mean, it might have been down when you asked, but now I am replying a day later and it's not, so I have no idea. I've got a session open to it now and am babysitting it. (restarting when I see failed services, restarting it if I don't see any messages for an hour or so, etc). > > > I know I can turn them off, but I actually LIKE the messages if they were > > > delivered promptly. > > > > > > Is there really nothing we can do about this? > > No, there's things we can do and are trying to do. ;) > > > > But of course more help welcome! > > > > We have a python3 port of it nearly ready to go, but I think it's > > CI/tests are not working, and we want to make sure those all work before > > we deploy it. I'll see if I can get more exact status... > > > But what happened that from reliable service is completely unreliable one? > Up until here: > > https://pagure.io/fedora-infrastructure/issue/10370 > > It was working mostly OK (although I have reported once incident earlier > https://pagure.io/fedora-infrastructure/issue/9932). But since that time it > is useless: > > https://pagure.io/fedora-infrastructure/issue/10414 I think it's a combination of things: * it's still querying the old account system, so all the new users who enable emails from it, get nothing and cause it to generate a bunch of emails that get rejected. * It's on fedmsg and most apps are using fedora-messaging. We have a gateway relaying from one to the other, but it doesn't handle new messages or changes in messages at all well. * We are generating a lot more messages than we used to. With more and more packages, mass rebuilds, eln builds, main branch to epel9 merges with hundreds of commits, etc, etc. The volume is just a lot higher. 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: VERY late notification emails
On Tue, Mar 01, 2022 at 08:04:14PM -, Peter Oliver wrote: > > I almost wrote this a week ago but decided not to as it's been recently > > discussed but this is really annoying. 6 days later is more than useless. > > ... > > Is there really nothing we can do about this? > > I think getting https://github.com/fedora-infra/fmn/pull/294 merged would > help a little, > because it moves the timestamp out of the message body and into the email > Date header. > The notifications will still be just as late, but at least you'll be able to > see that from your email index without opening each message. Yes, it could help some, but of course first we need to actually be running that version. Thats the python3 version, we are still running the old python2 version. ;( I'm working on getting the python3 version deployed to staging now, so hopefully soon we can get it in production. 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: copr expired security certificate?
On Wed, Mar 02, 2022 at 05:06:59PM -0500, Steven A. Falco wrote: > On 3/2/22 04:35 PM, Scott Talbert wrote: > > On Wed, 2 Mar 2022, Steven A. Falco wrote: > > > > > I just tried to connect to copr [1] with firefox, and got a "Did Not > > > Connect: Potential Security Issue" error. > > > > > > And apparently copr uses HSTS, so I cannot override it. Is anyone else > > > having the problem? > > > > > > [1] https://copr.fedoraproject.org/coprs/g/kicad/kicad/build/3541862/ > > > > https://pagure.io/fedora-infrastructure/issue/10583 > > > > You can go to https://copr.fedorainfracloud.org/ as a workaround for the > > time being. > > Thanks all - I appreciate the links. The "bad" link I reported was from a > notification email I got regarding a build failure. :-) > > I'm glad an infra issue has already been filed, and I'll use the workaround > mentioned. It's fixed now. It seems the config for that site was removed from ansible by accident with some other cleanup. It then kept working fine until the certs expired and it never got the new ones. ;( It's all been cleaned up and should be working again. Sorry for the trouble. 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: Why I get some random notifications from discourse?
Matthew Miller wrote: > I put #introductions in the default for "watching first post" because ... > I think seeing and welcoming new people joining our community is a good > default. Frankly, I think most existing maintainers will not be interested in all those self-introductions. If the new maintainer ends up working on the same set of packages, they will get to know each other soon enough anyway, otherwise, the interest will obviously be limited. So I am not convinced that this is a valid reason for sending a notification e-mail by default. Kevin Kofler ___ 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: Co-maintain gnome-shell-extension-freon
Assuming you are already a packager, please follow this process: https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/ On Wed, Mar 2, 2022, at 5:31 PM, Linus Walleij wrote: > Hi, > > it seems the maintainer of gnome-shell-extension-freon is not responsive > right now, I'd like to be added as co-maintainer so the extension can be > updated from 44 to 45, the current version does not work with GNOME 41 > which is a bug in the current Fedora 35 release. > > I guess I should submit a ticket to release engineering to make this happen? > > Best regards > Linus Walleij > ___ > 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
Co-maintain gnome-shell-extension-freon
Hi, it seems the maintainer of gnome-shell-extension-freon is not responsive right now, I'd like to be added as co-maintainer so the extension can be updated from 44 to 45, the current version does not work with GNOME 41 which is a bug in the current Fedora 35 release. I guess I should submit a ticket to release engineering to make this happen? Best regards Linus Walleij ___ 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: mold linker
On Wed, Mar 02, 2022 at 04:26:11PM -0500, Ken Dreyer wrote:
> Some of the Ceph developers were investigating mold, since Ceph takes
> so long to build. Linking time is a problem for us with Ceph. But I
> don't know if those interested Ceph developers have done benchmarks
> yet.
>
> And the lack of s390x and ppc64le is problematic for us in Ceph too.
> But overall I'm amazed at how fast mold development is progressing.
I think a linker that can be trusted is more important than speed,
especially when part of that speed comes from not performing any checking
and just blindly assuming things look the way it expects.
I've only spent 15 minutes on it to find that mold (1.1) does significantly
less effective SHF_MERGE | SHF_STRINGS constant merging (so ends up with
significantly larger .debug_str or the .rodata string sections), or
supports only small portion of TLS transitions ld.bfd supports and does no
checking. Small testcase found during that time:
a.c:
__thread int a = 42;
__attribute__((noipa)) int
foo (void)
{
return a;
}
int
main ()
{
return foo () != 42;
}
gcc -O2 -mcmodel=large -fpic -c a.c -o a.o
gcc -o a_ a.o
./a_; echo $?
yields expected 0,
gcc -o a a.o -fuse-ld=mold
./a
Segmentation fault (core dumped)
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: copr expired security certificate?
On 3/2/22 04:35 PM, Scott Talbert wrote: On Wed, 2 Mar 2022, Steven A. Falco wrote: I just tried to connect to copr [1] with firefox, and got a "Did Not Connect: Potential Security Issue" error. And apparently copr uses HSTS, so I cannot override it. Is anyone else having the problem? [1] https://copr.fedoraproject.org/coprs/g/kicad/kicad/build/3541862/ https://pagure.io/fedora-infrastructure/issue/10583 You can go to https://copr.fedorainfracloud.org/ as a workaround for the time being. Thanks all - I appreciate the links. The "bad" link I reported was from a notification email I got regarding a build failure. :-) I'm glad an infra issue has already been filed, and I'll use the workaround mentioned. 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
[EPEL-devel] Re: How to support python 3.8 from RHEL 8.2 in EPEL?
On 3/2/22 14:14, epel-devel@lists.fedoraproject.org wrote: > Except that we are going to need python38-pytest, etc. in the EPEL8 buildroot > if we are going to build (most of) the packages in the first place. That's > the problem I'm running into now trying to build python38-jmespath: > > https://koji.fedoraproject.org/koji/taskinfo?taskID=83570866 > DEBUG util.py:444: No matching package to install: 'python38-pytest' > > So I'm back to my original questions: > > * Do we just make EPEL python38- packages as modules or try to hack up some > kind of build system support for it? > * If modules, every package a module or one (or a few) modules? I have been told that the lack of python38-pytest is an issue with the buildroot generation and so have filed: https://pagure.io/releng/issue/10679 Hopefully this will make everything simpler as nothing has to be a module or special in any way. -- Orion Poplawski IT Systems Manager 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane or...@nwra.com Boulder, CO 80301 https://www.nwra.com/ smime.p7s Description: S/MIME Cryptographic Signature ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: copr expired security certificate?
On Wed, 2 Mar 2022, Steven A. Falco wrote: I just tried to connect to copr [1] with firefox, and got a "Did Not Connect: Potential Security Issue" error. And apparently copr uses HSTS, so I cannot override it. Is anyone else having the problem? [1] https://copr.fedoraproject.org/coprs/g/kicad/kicad/build/3541862/ https://pagure.io/fedora-infrastructure/issue/10583 You can go to https://copr.fedorainfracloud.org/ as a workaround for the time being. Scott ___ 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
[EPEL-devel] Re: EPEL-8 Packages needing care and feeding
On Wed, 2 Mar 2022 at 15:56, Stephen John Smoogen wrote: > > > # > > I expect that > > I clearly dropped the ball in that sentence. Let me finish it up: I expect that we will need to converse in this thread about what should be done next. In the EPEL meeting Kevin mentioned that I should email the maintainers of each of the 108 packages and see if they want to maintain it or remove it from EPEL-8. Then see if we can remove those from the tree cleanly without affecting packages. Some packages like python-nose should be removed anyway and if there are any other upstream dead ones those can go too. -- Stephen J Smoogen. Let us be kind to one another, for most of us are fighting a hard battle. -- Ian MacClaren ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: copr expired security certificate?
Hi Steve, I get the same error when I use the URL you linked. Typically when I interface with copr, I'm using (maybe wrongly) the 'copr.fedorainfracloud.org' URL instead. To which point I can reach the build you're trying to get to that way. https://copr.fedorainfracloud.org/coprs/g/kicad/kicad/build/3541862/ Not a solution, but at least a workaround to get you unstuck, hopefully. Regards, Andy On Wed, Mar 2, 2022 at 4:30 PM Steven A. Falco wrote: > > I just tried to connect to copr [1] with firefox, and got a "Did Not Connect: > Potential Security Issue" error. > > And apparently copr uses HSTS, so I cannot override it. Is anyone else > having the problem? > > [1] https://copr.fedoraproject.org/coprs/g/kicad/kicad/build/3541862/ > > 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 ___ 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
copr expired security certificate?
I just tried to connect to copr [1] with firefox, and got a "Did Not Connect: Potential Security Issue" error. And apparently copr uses HSTS, so I cannot override it. Is anyone else having the problem? [1] https://copr.fedoraproject.org/coprs/g/kicad/kicad/build/3541862/ 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: mold linker
On Wed, Mar 2, 2022 at 2:16 PM Jakub Jelinek wrote: > > On Wed, Mar 02, 2022 at 01:29:00PM -0500, Ben Beasley wrote: > > In RPM packaging, of course, everything is built from scratch, usually with > > LTO, and a package that takes a minute to link probably takes an hour to > > build. While any work that can be saved in an RPM build is helpful, I think > > the gains from a fast linker are likely to be much less dramatic here. > > > > [1] https://src.fedoraproject.org/rpms/mold/blob/rawhide/f/mold.spec#_24 > > Note, until a few days ago mold didn't support linker plugins, so was > incompatible with GCC LTO. There is some support in now but still a WIP. > > Linking speed is just one of the factors in choosing a linker, > reliability (e.g. known races in gold which is now effectively unmaintained > are a problem), or what features it supports. > mold doesn't support linker scripts so it is out of question for many use > cases, for other use cases it might matter more how large binaries and with > what security features in it it creates, etc. > I think for building Fedora packages in koji those other factors are much > more important than a few seconds saved during the package build. Some of the Ceph developers were investigating mold, since Ceph takes so long to build. Linking time is a problem for us with Ceph. But I don't know if those interested Ceph developers have done benchmarks yet. And the lack of s390x and ppc64le is problematic for us in Ceph too. But overall I'm amazed at how fast mold development is progressing. - Ken ___ 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: unsafe systemd setup in Fedora
Hi On Wed, Mar 2, 2022 at 12:31 PM Zbigniew Jędrzejewski-Szmek wrote: > On Thu, Feb 24, 2022 at 02:28:56PM -0500, Rahul Sundaram wrote: > > Ability to modify these policies via configuration (the above one looks > > like a build config) and ability to do global overrides and set the > > hardening features across all services so distributions or sysadmins can > > configure those would be helpful > > It's a runtime config. Agreed with the rest though, and what > Matthew Miller said in the other reply: volunteers welcome ;) > Just to be clear, there is no support for global service overrides in systemd but you are willing to accept patches for it? Rahul ___ 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
[EPEL-devel] Re: How to support python 3.8 from RHEL 8.2 in EPEL?
On 2/13/20 02:21, Tomas Orsava wrote: > On 2/13/20 5:18 AM, Orion Poplawski wrote: >> On 1/30/20 8:39 AM, Miro Hrončok wrote: >>> On 30. 01. 20 16:32, Orion Poplawski wrote: Folks - Looks like RHEL 8.2 will have python 3.8 in addition to python 3.6. From the 8.2 beta: Red Hat Enterprise Linux 8 for x86_64 - AppStream Beta (RPMs) Name Stream Profiles Summary python27 2.7 [d][e] common [d] Python programming language, version 2.7 python36 3.6 [d][e] build, common [d] Python programming language, version 3.6 python38 3.8 [d][e] build, common [d] Python programming language, version 3.8 Currently, %python_pkgversion is set to 3 in /usr/lib/rpm/macros.d/macros.python-srpm from python-srpm-macros. python3-devel is still provided only by python36-devel, so presumably all EPEL8 python packages will continue to be built against python 3.6. But I imagine that people will soon be asking for python 3.8 versions of EPEL packages. How can we provide those? Does this have to be done in some modular fashion - which seems to come back to the discussion of whether or not every package has to become its own module or whether to group them together somehow. Or since both python modules are "default" modules and we can install both python36-devel and python38-devel at the same time, perhaps we can define the python3_other* macros again for python38 and just go that way? Thoughts? >>> >>> The idea is that the versions fo stuff we build in RHEL for different >>> python versions is different and I'd like to keep that idea in EPEL as >>> well. Building a python38-foo package from it's own spec should work as >>> follows: >>> >>> BR python38-rpm-macros >>> BR python38-devel >>> BR python38-bar etc... >>> >>> Regular specfile follows. >>> >>> You can even have a single specfile that build for different Python version >>> based on local override of %python_pkgversion in the buildroot. >>> >>> Building both versions from single spec file---single build would require a >>> new set of macros, yes (or hardcoding stuff). However I'd not call them >>> python3_other* unless you want to end up with python3_other_other* the next >>> time this happens. >>> >> >> This along with some more info from rhel 8.2 beta yields more questions for >> me. While I do agree that building the python38 packages from separate >> specs probably is the best route (biggest reason being it allows for >> updating of individual module versions) I'm hoping we can brainstorm ways to >> make this less onerous on individual packagers. >> >> Looks like python38-devel is a module in RHEL 8.2 that provides a bunch of >> stuff needed for building modules (python38-devel, python38-pytest, etc): > > > Hi! > Just a little correction, despite the name suggesting otherwise, the > "python38-devel" package is not in the python38-devel module, but in the > python38 module itself, which has a default stream. > > The python38-devel module contains only python38-pytest and it's dependencies > (pyparsing, atomicwrites, attrs, packaging, py, more-itertools, pluggy, > wcwidth). And the reason it's not default is not an intention but a current > technical limitation of the automatically generated "-devel" modules shipped > in the CRB. > > >> >> Red Hat CodeReady Linux Builder Beta for RHEL 8 x86_64 (RPMs) >> Name Stream Profiles Summary >> python38-devel 3.8 [e] Python programming >> language, version 3.8 >> >> Since this isn't a default module, does this again mean the python38 >> packages in EPEL 8 need to be modules as well? Or can we provide a >> buildroot that enables this module? >> >> My current pie-in-the-sky idea is that we could do: >> >> - create a epel8-python38 branch for all of the python-* packages with epel8 >> branches. >> - epel8-python38 buildroot would enable python38-devel and install >> python38-rpm-macros and define python3_pkgversion to 38. >> - This would imply an epel8-python38 repo. It's possible that some packages >> from epel8-python38 wouldn't be able to be installed unless the >> python38-devel module was enabled. >> - This might lead to an explosion of repos if we try to work around other >> modules in RHEL8 like this (php 7.3, perl, ruby 2.6) >> >> >> Otherwise I think we will need python38 packages in EPEL8 to be modular. If >> the module route is the way to go, I really do think that we should try to >> not have every package be its own module, though the other extreme (all >> packages in one module) probably is untenable as well. In any case, this >> will require a lot more coordination among packagers (not necessarily a bad >> thing). >> >> Thoughts? Plans? > > > Since pytest is usually a build dependency, then
[Bug 2060156] New: perl-Locale-Codes-3.70 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2060156 Bug ID: 2060156 Summary: perl-Locale-Codes-3.70 is available Product: Fedora Version: rawhide Status: NEW Component: perl-Locale-Codes Keywords: FutureFeature, Triaged Assignee: mspa...@redhat.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: mspa...@redhat.com, perl-devel@lists.fedoraproject.org, ppi...@redhat.com Target Milestone: --- Classification: Fedora Latest upstream release: 3.70 Current version/release in rawhide: 3.69-2.fc36 URL: http://search.cpan.org/dist/Locale-Codes/ Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from Anitya: https://release-monitoring.org/project/3033/ -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2060156 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] EPEL-8 Packages needing care and feeding
When EPEL-8 was trying to get out the door, I tried to make it 'fully operational' by having fedpkg in it. It turned out that was a bad idea on my part as I ended up adding about 130 packages to EPEL-8 which have not been updated or cared for since. The problems involved is that I did this with the 'ask for forgiveness vs ask for permission' approach with the idea that packagers and such would update as needed over time. This has been highly unfair to the Fedora packagers who have gotten bugs or requests to update which they had no interest in. So I would like to start cleaning up and working through which ones need to be removed. There are 108 packages which have not been updated since their initial import. All of them are build dependencies for things like bodhi/koji/mock which then are required by fedpkg/fedora-packager. [They are in the included text file] The list of packages which have been updated since 2019 are shorter and I will repeat them for sanity sake: ## Updated in 2020 python-bleach python-fedora python-gitdb python-lockfile python-m2r python-simplejson python-smmap python-twisted python3-py3dns ## Updated in 2021 GitPython fedora-packager kobo mock python-django ## Updated in 2022 distribution-gpg-keys fedora-messaging fedpkg koji mock-core-configs python-bugzilla rpkg # I expect that -- Stephen J Smoogen. Let us be kind to one another, for most of us are fighting a hard battle. -- Ian MacClaren # Not updated since initial import latexmk pungi pydot pyflakes python-Automat python-WSGIProxy2 python-alembic python-apipkg python-appdirs python-arrow python-async-generator python-backoff python-bcrypt python-beautifulsoup4 python-blinker python-cccolutils python-chai python-chameleon python-colander python-constantly python-cornice-sphinx python-cornice python-cov-core python-cpuinfo python-cryptography-vectors python-cssselect python-defusedxml python-dogpile-cache python-editor python-entrypoints python-enum34 python-execnet python-feedgen python-fields python-filelock python-flake8 python-flit python-freezegun python-gitdb python-h2 python-hamcrest python-hpack python-hupper python-hyperframe python-hyperlink python-incremental python-isodate python-kerberos python-kitchen python-lockfile python-mccabe python-memcached python-mistune python-multilib python-munch python-nose2 python-openid-cla python-openid-teams python-openidc-client python-parameterized python-paste-deploy python-paste python-pbr python-pika python-plaster-pastedeploy python-plaster python-pretend python-priority python-pycodestyle python-pylibravatar python-pyquery python-pyramid-fas-openid python-pyramid-mako python-pyramid python-pyroute2 python-pytest-benchmark python-pytest-cov python-pytest-forked python-pytest-runner python-pytest-xdist python-rdflib python-requests-kerberos python-responses python-selenium python-service-identity python-simplemediawiki python-sphinx-theme-py3doc-enhanced python-sqlalchemy_schemadisplay python-sqlparse python-tempita python-toml python-tornado python-translationstring python-venusian python-waitress python-webob python-webtest python-zope-component python-zope-configuration python-zope-deprecation python-zope-event python-zope-exceptions python-zope-i18nmessageid python-zope-interface python-zope-schema python-zope-testing python3-openid python3-pytest-asyncio ## Updated in 2020 python-bleach python-fedora python-gitdb python-lockfile python-m2r python-simplejson python-smmap python-twisted python3-py3dns ## Updated in 2021 GitPython fedora-packager kobo mock python-django ## Updated in 2022 distribution-gpg-keys fedora-messaging fedpkg koji mock-core-configs python-bugzilla rpkg ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
gap-pkg-radiroot license change to GPLv2+
I just built gap-pkg-radiroot 2.9 for F36 and Rawhide. The license was GPL+, and is now GPLv2+. I do not expect this to have any practical effect. -- Jerry James http://www.jamezone.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
[Bug 2060149] New: perl-Workflow-1.60 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2060149 Bug ID: 2060149 Summary: perl-Workflow-1.60 is available Product: Fedora Version: rawhide Status: NEW Component: perl-Workflow Keywords: FutureFeature, Triaged Assignee: emman...@seyman.fr Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: emman...@seyman.fr, perl-devel@lists.fedoraproject.org Target Milestone: --- Classification: Fedora Latest upstream release: 1.60 Current version/release in rawhide: 1.59-1.fc36 URL: https://metacpan.org/release/Workflow Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from Anitya: https://release-monitoring.org/project/17896/ -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2060149 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Chromium security bugs remain unfixed for > 1 month
On Wed, Mar 02, 2022 at 04:07:43PM -, Leigh Scott wrote: > > Fedora cannot use the default tarball due to legal restrictions. > > Additionally, Fedora uses > > GCC (intentionally) which requires patch work for each release, but > > improves the quality > > of the resulting package. > > So GCC needs 125Gb of Ram to build chromium? > https://koji.fedoraproject.org/koji/taskinfo?taskID=83529675 > > What makes the GCC build better than clang build? GCC was "the" Fedora compiler that everyone had to use, but in Fedora 35 the policy changed: https://fedoraproject.org/wiki/Changes/CompilerPolicy However Tom may have his own reasons to use GCC, he's the packager so it's up to him. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into KVM guests. http://libguestfs.org/virt-v2v ___ 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
[Bug 1964646] F35FailsToInstall: perl-Crypt-PWSafe3
https://bugzilla.redhat.com/show_bug.cgi?id=1964646 --- Comment #10 from Fedora Update System --- FEDORA-2022-e541fc8d0d has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-e541fc8d0d` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-e541fc8d0d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=1964646 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2059170] perl-CPAN-Perl-Releases-5.20220227 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2059170 --- Comment #5 from Fedora Update System --- FEDORA-2022-af355c9cb8 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-af355c9cb8` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-af355c9cb8 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2059170 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2059504] perl-Test-DistManifest-1.014-22.fc37 FTBFS: Failed test 'All files are listed in MANIFEST or skipped'
https://bugzilla.redhat.com/show_bug.cgi?id=2059504 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #7 from Fedora Update System --- FEDORA-2022-45495fdb32 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-45495fdb32` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-45495fdb32 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2059504 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2058963] perl-App-cpm-0.997009 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2058963 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #3 from Fedora Update System --- FEDORA-2022-12439ce7de has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-12439ce7de` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-12439ce7de See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2058963 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1939424] perl-Crypt-PWSafe3-1.22-17.fc35 FTBFS: Failed test 'open a pwsafe3 database ('blocksize' is not a recognized argument at /usr/share/perl5/vendor_perl/Crypt/CBC.pm line 309.
https://bugzilla.redhat.com/show_bug.cgi?id=1939424 --- Comment #11 from Fedora Update System --- FEDORA-2022-e541fc8d0d has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-e541fc8d0d` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-e541fc8d0d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=1939424 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: mold linker
On Wed, Mar 02, 2022 at 01:29:00PM -0500, Ben Beasley wrote: > In RPM packaging, of course, everything is built from scratch, usually with > LTO, and a package that takes a minute to link probably takes an hour to > build. While any work that can be saved in an RPM build is helpful, I think > the gains from a fast linker are likely to be much less dramatic here. > > [1] https://src.fedoraproject.org/rpms/mold/blob/rawhide/f/mold.spec#_24 Note, until a few days ago mold didn't support linker plugins, so was incompatible with GCC LTO. There is some support in now but still a WIP. Linking speed is just one of the factors in choosing a linker, reliability (e.g. known races in gold which is now effectively unmaintained are a problem), or what features it supports. mold doesn't support linker scripts so it is out of question for many use cases, for other use cases it might matter more how large binaries and with what security features in it it creates, etc. I think for building Fedora packages in koji those other factors are much more important than a few seconds saved during the package build. 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: mold linker
On Wed, Mar 2 2022 at 05:37:35 PM +, Mattia Verga via devel wrote: Accordingly to upstream presentation, it seems to have far better performances than lld, especially when building big projects... A WebKit developer put this to the test recently: https://bugs.webkit.org/show_bug.cgi?id=236362#c7 ___ 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-02
Minutes: https://meetbot.fedoraproject.org/fedora-meeting-1/2022-03-02/fedora_coreos_meeting.2022-03-02-16.30.html Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting-1/2022-03-02/fedora_coreos_meeting.2022-03-02-16.30.txt Log: https://meetbot.fedoraproject.org/fedora-meeting-1/2022-03-02/fedora_coreos_meeting.2022-03-02-16.30.log.html #fedora-meeting-1: fedora_coreos_meeting Meeting started by dustymabe at 16:30:19 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2022-03-02/fedora_coreos_meeting.2022-03-02-16.30.log.html . Meeting summary --- * roll call (dustymabe, 16:30:23) * Action items from last meeting (dustymabe, 16:34:21) * ACTION: ravanelli to look into the F36 changes 127 to see if this change affects us on ppc64le (dustymabe, 16:34:51) * AWS m4.large instances fail to boot starting with 35.20211226.20.0 (dustymabe, 16:35:08) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1066 (dustymabe, 16:35:12) * ACTION: davdunc to see if we can get the revert applied to the latest fedora kernels again (dustymabe, 16:41:29) * tracker: Fedora 36 changes considerations (dustymabe, 16:47:03) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/918 (dustymabe, 16:47:07) * LINK: https://github.com/coreos/rpm-ostree/issues/3465 (dustymabe, 16:47:49) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1098 (dustymabe, 16:49:57) * for 128 "GNU Toolchain Update (gcc 12, glibc 2.35)" the wiki says it should be a backwards compatible change. We'll monitor, but for now there is nothing for us to do. (dustymabe, 16:54:29) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1099 (dustymabe, 16:54:43) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1106 (dustymabe, 16:56:21) * Consider releasing FCOS with a predictable release cadence (dustymabe, 16:58:43) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1062 (dustymabe, 16:58:51) * AGREED: We try to release every two weeks and we try to have releases go out on Tuesday. We don't want to write down any more contraints for ourselves than that so we don't waste time with the details and focus on other work. (dustymabe, 17:14:02) * open floor (dustymabe, 17:14:33) * LINK: https://github.com/openshift/okd-machine-os/issues/210 (jlebon, 17:24:21) * LINK: https://github.com/coreos/ignition/pull/1324 (dustymabe, 17:28:29) Meeting ended at 17:29:52 UTC. Action Items * ravanelli to look into the F36 changes 127 to see if this change affects us on ppc64le * davdunc to see if we can get the revert applied to the latest fedora kernels again Action Items, by person --- * davdunc * davdunc to see if we can get the revert applied to the latest fedora kernels again * **UNASSIGNED** * ravanelli to look into the F36 changes 127 to see if this change affects us on ppc64le People Present (lines said) --- * dustymabe (111) * travier (56) * zodbot (21) * nemric (18) * davdunc (16) * jlebon (15) * lucab (4) * walters (4) * fifofonix (2) * miabbott (2) * lucab_ (2) * jbrooks (1) * aaradhak[m] (1) * aaradhak (1) * skunkerk (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: mold linker
I’m not very familiar with mold’s pros and cons other than its speed, but I think that architecture limitations[1] will limit widespread adoption for the time being: || # mold can currently produce native binaries for x86, aarch64 and riscv64 only ExclusiveArch: x86_64 aarch64 riscv64 I think a fast linker is a huge benefit in incremental builds while developing software, where the final link often massively dominates the build time after changing a handful of sources. In RPM packaging, of course, everything is built from scratch, usually with LTO, and a package that takes a minute to link probably takes an hour to build. While any work that can be saved in an RPM build is helpful, I think the gains from a fast linker are likely to be much less dramatic here. [1] https://src.fedoraproject.org/rpms/mold/blob/rawhide/f/mold.spec#_24 On 3/2/22 12:37, Mattia Verga via devel wrote: disclaimer: I'm a real noob about this topic, so forgive me if I'm starting a useless discussion. I came across 'mold' project [1], which is a GNU Gold / LLVM lld replacement with multi-core support. Accordingly to upstream presentation, it seems to have far better performances than lld, especially when building big projects... so I just want to ask if anyone already knows it, if we can make use of it in Koji or if there already is a plan to test its adoption. I see it's already packaged in Fedora. Mattia [1] https://github.com/rui314/mold ___ 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: Chromium security bugs remain unfixed for > 1 month
On Wed, Mar 2, 2022 at 5:06 AM Demi Marie Obenour wrote: > What would it take to get tall of the users of QtWebEngine onto 6.2? I > don’t think Fedora should ship any version of QtWebEngine except the > latest, since only the latest version appears to get regular patches. Well, it is slightly more complicated, as there is a process to get patches backported (for all of the Qt 5 modules), and it does happen, but that process can be somewhat convoluted due to "reasons". As I recall (and I could easily be wrong about the current status), qt6-qtwebengine has not yet been packaged/built for Fedora, which I suspect is at least partially due to the same reasons that it can be hard to package chromium (stripping, debundling, etc.), and AFAIK no project yet requires it (and as it requires resources to maintain once made available, I suspect there is negative motivation to make it available until it is actually needed). Even when qt6-qtwebeingine is packaged, moving to Qt 6.x from Qt 5.y for a project can be easy or hard, depending on what the project is doing, but that is a question for those upstream projects that are using Qt. I would suggest you directly ask those projects what their intentions and schedules are. I suspect most have a plan for moving forward to Qt 6,x, but it may not be sufficiently resourced to happen in the near term. Perhaps the largest project (that I am aware of) would be KDE, and they have a plan, and are working on it, but AFAIK have no specific targets for completion (and for that project, there is a lot of work to accomplish). Realistically, all of qt5 (including the webengine) is likely to be part of Fedora for quite some time, just as qt4 libraries are still available, as some package still uses them. ___ 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
mold linker
disclaimer: I'm a real noob about this topic, so forgive me if I'm starting a useless discussion. I came across 'mold' project [1], which is a GNU Gold / LLVM lld replacement with multi-core support. Accordingly to upstream presentation, it seems to have far better performances than lld, especially when building big projects... so I just want to ask if anyone already knows it, if we can make use of it in Koji or if there already is a plan to test its adoption. I see it's already packaged in Fedora. Mattia [1] https://github.com/rui314/mold ___ 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: unsafe systemd setup in Fedora
On Thu, Feb 24, 2022 at 02:28:56PM -0500, Rahul Sundaram wrote: > Hi > > On Thu, Feb 24, 2022 at 2:14 PM Zbigniew Jędrzejewski-Szmek > > > > > Systemd 250 (coming in F36), has --security-policy switch which can be > > used to enable/disable some of the checks. There is no way to tell > > systemd-analyze that things about a specific unit though. > > Ability to modify these policies via configuration (the above one looks > like a build config) and ability to do global overrides and set the > hardening features across all services so distributions or sysadmins can > configure those would be helpful It's a runtime config. Agreed with the rest though, and what Matthew Miller said in the other reply: volunteers welcome ;) 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: Why I get some random notifications from discourse?
On Tue, Mar 01, 2022 at 10:34:48AM +0100, Vít Ondruch wrote: > Because of #introductions tag is watched. But why? I have have not > set anything like this by myself. And I am apparently not the only > one who noticed: I put #introductions in the default for "watching first post" because ... I think seeing and welcoming new people joining our community is a good default. But you can adjust these under: https://discussion.fedoraproject.org/my/preferences/categories https://discussion.fedoraproject.org/my/preferences/tags ... and I expect most people will want to, just as you would decide which mailing lists to subscribe to. -- Matthew Miller Fedora Project Leader ___ 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: unsafe systemd setup in Fedora
On Thu, Feb 24, 2022 at 08:13:15PM +0100, Zbigniew Jędrzejewski-Szmek wrote: > It would probably be good to use more of those features, but you need > to understand the service very well to know what systemd security > features can be enabled for it. I'd definitely love to see us put more effort into this — but we don't have any specific resources for this kind of thing, so it needs to be someone's labor of love. See https://pagure.io/packaging-committee/issue/667 as a first start... -- Matthew Miller Fedora Project Leader ___ 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
[Bug 2060072] perl-Inline-C-0.82 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2060072 Petr Pisar changed: What|Removed |Added Status|NEW |ASSIGNED Doc Type|--- |If docs needed, set a value --- Comment #1 from Petr Pisar --- A bug-fix release suitable for all Fedoras and EPEL 8. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2060072 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] Fedora EPEL 7 updates-testing report
The following Fedora EPEL 7 Security updates need testing: Age URL 5 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-af77a11507 seamonkey-2.53.11-1.el7 The following builds have been pushed to Fedora EPEL 7 updates-testing haproxy18-1.8.27-2.el7 rpminspect-1.9-1.el7 tio-1.35-1.el7 zimg-3.0.3-1.el7 Details about builds: haproxy18-1.8.27-2.el7 (FEDORA-EPEL-2022-ffbac73a6e) HAProxy reverse proxy for high availability environments Update Information: - Backport from 1.8.27-4: Apply patch (#1941446) - Backport from 1.8.27-3: Fix short HTTP responses (#1941446) ChangeLog: * Wed Mar 2 2022 Robert Scheck 1.8.27-2 - Backport from 1.8.27-4: Apply patch (#1941446) - Backport from 1.8.27-3: Fix short HTTP responses (#1941446) rpminspect-1.9-1.el7 (FEDORA-EPEL-2022-ea7eb25562) Build deviation compliance tool Update Information: Upgrade to rpminspect-1.9 ChangeLog: * Wed Mar 2 2022 David Cantrell - 1.9-1 - Upgrade to rpminspect-1.9 tio-1.35-1.el7 (FEDORA-EPEL-2022-98cbc6140a) Simple TTY terminal I/O application Update Information: # tio v1.35* Add support for automatically generated log filename Automatically generate log filename if none is provided. The auto generated file name is on the form: `tio_DEVICE_-MM-DDTHH:MM:SS.log`* Add support for configurable timestamp format Also changes default timestamp format from ISO8601 to classic 24-hour format as this is assumed to be the format that most users would prefer. And reintroduces strict but optional ISO8601 format. This feature allows to easily add more timestamp formats in the future.* Reintroduce `asm-generic/ioctls.h` It is needed for ppc builds.* Add macro hack to workaround older buggy glibc* Add support for high bps on OS X ChangeLog: * Sun Feb 20 2022 Robert Scheck 1.35-1 - Upgrade to 1.35 (#2054902) * Wed Feb 16 2022 Robert Scheck 1.34-1 - Upgrade to 1.34 (#2054902) References: [ 1 ] Bug #2054902 - tio-1.35 is available https://bugzilla.redhat.com/show_bug.cgi?id=2054902 zimg-3.0.3-1.el7 (FEDORA-EPEL-2022-83191796ff) Scaling, color space conversion, and dithering library Update Information: Update to 3.0.3. No ABI changes. ChangeLog: * Wed Feb 23 2022 Nicolas Chauvet - 3.0.3-1 - Update to 3.0.3 ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Chromium security bugs remain unfixed for > 1 month
On 3/2/22 10:09, Tom Callaway wrote: > Apologies for the delays. My wife has been rather ill for a while, so my open > source time has been greatly minimized lately. I am so sorry. > Fedora cannot use the default tarball due to legal restrictions. Unfortunate but understandable. How much recurring work is this? > Additionally, Fedora uses GCC (intentionally) which requires patch work for > each release, but improves the quality of the resulting package. Would it be possible to make a one-off exception for Chromium? -- 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
[Bug 2042867] Please branch and build perl-Data-Compare for EPEL 9
https://bugzilla.redhat.com/show_bug.cgi?id=2042867 Fedora Update System changed: What|Removed |Added Status|ASSIGNED|MODIFIED --- Comment #3 from Fedora Update System --- FEDORA-EPEL-2022-cf1a4cc94c has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-cf1a4cc94c -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2042867 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Chromium security bugs remain unfixed for > 1 month
Thanks, and thank you for maintaining chromium-freeworld in rpmfusion. ___ 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
[Bug 2059170] perl-CPAN-Perl-Releases-5.20220227 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2059170 --- Comment #4 from Fedora Update System --- FEDORA-2022-812cd17af1 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-812cd17af1` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-812cd17af1 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2059170 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1939424] perl-Crypt-PWSafe3-1.22-17.fc35 FTBFS: Failed test 'open a pwsafe3 database ('blocksize' is not a recognized argument at /usr/share/perl5/vendor_perl/Crypt/CBC.pm line 309.
https://bugzilla.redhat.com/show_bug.cgi?id=1939424 --- Comment #10 from Fedora Update System --- FEDORA-2022-9af00d105b has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-9af00d105b` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-9af00d105b See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=1939424 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1964646] F35FailsToInstall: perl-Crypt-PWSafe3
https://bugzilla.redhat.com/show_bug.cgi?id=1964646 --- Comment #9 from Fedora Update System --- FEDORA-2022-9af00d105b has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-9af00d105b` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-9af00d105b See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=1964646 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Chromium security bugs remain unfixed for > 1 month
> Fedora cannot use the default tarball due to legal restrictions. > Additionally, Fedora uses > GCC (intentionally) which requires patch work for each release, but improves > the quality > of the resulting package. So GCC needs 125Gb of Ram to build chromium? https://koji.fedoraproject.org/koji/taskinfo?taskID=83529675 What makes the GCC build better than clang build? > > Chromium was also breaking koji due to the large amount of memory it needs to > build > exceeding the available memory in VMs. The helpful Fedora Infra team has > created a > baremetal group for Chromium to work around this. If the rpmfusion builder VM requirement increases (currently 16Gb) it's likely to be orphaned unless someone donates more RAM for my builder. > > ~spot ___ 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
[Bug 2060072] New: perl-Inline-C-0.82 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2060072 Bug ID: 2060072 Summary: perl-Inline-C-0.82 is available Product: Fedora Version: rawhide Status: NEW Component: perl-Inline-C Keywords: FutureFeature, Triaged Assignee: ppi...@redhat.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: perl-devel@lists.fedoraproject.org, ppi...@redhat.com Target Milestone: --- Classification: Fedora Latest upstream release: 0.82 Current version/release in rawhide: 0.81-12.fc36 URL: http://search.cpan.org/dist/Inline-C/ Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from Anitya: https://release-monitoring.org/project/2985/ -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2060072 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2059170] perl-CPAN-Perl-Releases-5.20220227 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2059170 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #3 from Fedora Update System --- FEDORA-2022-ca69cea458 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-ca69cea458` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-ca69cea458 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2059170 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1939424] perl-Crypt-PWSafe3-1.22-17.fc35 FTBFS: Failed test 'open a pwsafe3 database ('blocksize' is not a recognized argument at /usr/share/perl5/vendor_perl/Crypt/CBC.pm line 309.
https://bugzilla.redhat.com/show_bug.cgi?id=1939424 --- Comment #9 from Fedora Update System --- FEDORA-2022-2fa03c4f5d has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-2fa03c4f5d` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-2fa03c4f5d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=1939424 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1964646] F35FailsToInstall: perl-Crypt-PWSafe3
https://bugzilla.redhat.com/show_bug.cgi?id=1964646 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #8 from Fedora Update System --- FEDORA-2022-2fa03c4f5d has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-2fa03c4f5d` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-2fa03c4f5d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=1964646 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2060062] New: perl-Mail-Alias-1.15 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2060062 Bug ID: 2060062 Summary: perl-Mail-Alias-1.15 is available Product: Fedora Version: rawhide Status: NEW Component: perl-Mail-Alias Keywords: FutureFeature, Triaged Assignee: jpazdzi...@redhat.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: jpazdzi...@redhat.com, oli...@linux-kernel.at, perl-devel@lists.fedoraproject.org, st...@silug.org Target Milestone: --- Classification: Fedora Latest upstream release: 1.15 Current version/release in rawhide: 1.12-46.fc36 URL: https://metacpan.org/release/Mail-Alias Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from Anitya: https://release-monitoring.org/project/242747/ -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2060062 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2060062] perl-Mail-Alias-1.15 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2060062 --- Comment #1 from Upstream Release Monitoring --- Scratch build failed. Details bellow: BuilderException: Build started, but failure happened during post build operations: Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-2951agww/perl-Mail-Alias.spec']' returned non-zero exit status 1. StdOut: error: Bad source: ./Mail-Alias-1.15.tar.gz: No such file or directory Traceback: File "/usr/local/lib/python3.9/site-packages/hotness/use_cases/package_scratch_build_use_case.py", line 56, in build result = self.builder.build(request.package, request.opts) File "/usr/local/lib/python3.9/site-packages/hotness/builders/koji.py", line 188, in build raise BuilderException( If you think this issue is caused by some bug in the-new-hotness, please report it on the-new-hotness issue tracker: https://github.com/fedora-infra/the-new-hotness/issues -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2060062 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Chromium security bugs remain unfixed for > 1 month
> VAAPI hasn't worked for a long time on chromium. In "chrome://gpu" it shows > "Video Decode: Software only. Hardware acceleration disabled" and it cannot be > changed in "chrome://flags" either. This is the case for Fedora's packaged > chromium and rpmfusion's chromium-freeworld. I encourage you to verify this > yourself > using intel or amd graphics. > vaapi is disabled by google as default since chrome 93/94, you need to enable it with --enable-features=VaapiVideoDecoder https://wiki.archlinux.org/title/chromium#Hardware_video_acceleration ___ 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
Introduction: Ryan McCann
Hello, I am currently working on my final project for senior year alongside Red Hat! Our goal is to create a more "friendly" Fedora OS for university students. We plan to create a club dedicated to this at the university and to assist our fellow students and faculty with Fedora as it becomes more popular at our school, UMass Lowell. We are working with Mohan Boddu, who is our industry sponsor. ___ 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: Chromium security bugs remain unfixed for > 1 month
> We ship VA-API integration, which Google doesn't offer. VAAPI hasn't worked for a long time on chromium. In "chrome://gpu" it shows "Video Decode: Software only. Hardware acceleration disabled" and it cannot be changed in "chrome://flags" either. This is the case for Fedora's packaged chromium and rpmfusion's chromium-freeworld. I encourage you to verify this yourself using intel or amd graphics. > Those features provide tangible benefits to the community at large > that we would lose by "sloppy packaging" An outdated browser that has many known vulnerabilities is a huge security problem and provides tangible drawbacks. If it's too much work to keep current then it should be removed from the repository. We do not want users to be under the illusion that the provided package is secure and maintained when it's not. > The same goes for everyone else on this thread so far. I'm > disappointed by the OP and everyone else in this thread who thinks > it's okay to do less than a good job on shipping software. I would argue that providing secure packages takes priority over most other packaging issues. ___ 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: Chromium security bugs remain unfixed for > 1 month
On Wed, Mar 2, 2022 at 9:19 AM Zbigniew Jędrzejewski-Szmek wrote: > > On Wed, Mar 02, 2022 at 07:08:07AM -0500, Neal Gompa wrote: > > Those features provide tangible benefits to the community at large > > that we would lose by "sloppy packaging". Instead of kvetching, why > > not try helping? Maybe *ask* Tom what you could do to help him ship > > newer versions? > > Neal, > > please reign in your rhetoric a bit. This is a discussion about > packaging, not the people involved. > My apologies, this thread was combined with some off-list conversations that were considerably less charitable around this topic, which led to a more drastic response than I would have normally given. -- 真実はいつも一つ！/ 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: Chromium security bugs remain unfixed for > 1 month
Apologies for the delays. My wife has been rather ill for a while, so my open source time has been greatly minimized lately. Fedora cannot use the default tarball due to legal restrictions. Additionally, Fedora uses GCC (intentionally) which requires patch work for each release, but improves the quality of the resulting package. Chromium was also breaking koji due to the large amount of memory it needs to build exceeding the available memory in VMs. The helpful Fedora Infra team has created a baremetal group for Chromium to work around this. Finally, I had been working on trying to resolve the build failures with Fedora 36, but they should now be fixed (as of last night). Of course, Google released a new major version this morning, so the terrifying carousel spins anew. Your patience is appreciated. ~spot ___ 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-20220302.n.0 compose check report
No missing expected images. Failed openQA tests: 6/229 (x86_64), 8/161 (aarch64) New failures (same test not failed in Fedora-36-20220301.n.0): ID: 1156067 Test: x86_64 Everything-boot-iso memory_check URL: https://openqa.fedoraproject.org/tests/1156067 ID: 1156100 Test: x86_64 KDE-live-iso install_default_upload URL: https://openqa.fedoraproject.org/tests/1156100 ID: 1156315 Test: x86_64 universal install_xfs@uefi URL: https://openqa.fedoraproject.org/tests/1156315 Old failures (same test failed in Fedora-36-20220301.n.0): ID: 1156127 Test: x86_64 Silverblue-dvd_ostree-iso gnome_text_editor URL: https://openqa.fedoraproject.org/tests/1156127 ID: 1156180 Test: aarch64 Server-dvd-iso server_cockpit_basic@uefi URL: https://openqa.fedoraproject.org/tests/1156180 ID: 1156222 Test: aarch64 Workstation-raw_xz-raw.xz gnome_text_editor@uefi URL: https://openqa.fedoraproject.org/tests/1156222 ID: 1156265 Test: aarch64 Workstation-upgrade gnome_text_editor@uefi URL: https://openqa.fedoraproject.org/tests/1156265 ID: 1156268 Test: aarch64 Workstation-upgrade desktop_update_graphical@uefi URL: https://openqa.fedoraproject.org/tests/1156268 ID: 1156299 Test: x86_64 universal install_arabic_language URL: https://openqa.fedoraproject.org/tests/1156299 ID: 1156300 Test: x86_64 universal install_asian_language URL: https://openqa.fedoraproject.org/tests/1156300 ID: 1156365 Test: aarch64 universal install_arabic_language@uefi URL: https://openqa.fedoraproject.org/tests/1156365 ID: 1156373 Test: aarch64 universal install_asian_language@uefi URL: https://openqa.fedoraproject.org/tests/1156373 ID: 1156401 Test: aarch64 Minimal-raw_xz-raw.xz install_arm_image_deployment_upload@uefi URL: https://openqa.fedoraproject.org/tests/1156401 ID: 1156410 Test: aarch64 Server-raw_xz-raw.xz install_arm_image_deployment_upload@uefi URL: https://openqa.fedoraproject.org/tests/1156410 Soft failed openQA tests: 15/229 (x86_64), 13/161 (aarch64) (Tests completed, but using a workaround for a known bug) Old soft failures (same test soft failed in Fedora-36-20220301.n.0): ID: 1156092 Test: x86_64 Workstation-live-iso eog URL: https://openqa.fedoraproject.org/tests/1156092 ID: 1156122 Test: x86_64 Silverblue-dvd_ostree-iso eog URL: https://openqa.fedoraproject.org/tests/1156122 ID: 1156140 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/1156140 ID: 1156216 Test: aarch64 Workstation-raw_xz-raw.xz eog@uefi URL: https://openqa.fedoraproject.org/tests/1156216 ID: 1156231 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi URL: https://openqa.fedoraproject.org/tests/1156231 ID: 1156235 Test: x86_64 Workstation-upgrade upgrade_desktop_64bit URL: https://openqa.fedoraproject.org/tests/1156235 ID: 1156257 Test: aarch64 Workstation-upgrade upgrade_desktop_64bit@uefi URL: https://openqa.fedoraproject.org/tests/1156257 ID: 1156259 Test: aarch64 Workstation-upgrade eog@uefi URL: https://openqa.fedoraproject.org/tests/1156259 ID: 1156297 Test: x86_64 universal upgrade_server_64bit URL: https://openqa.fedoraproject.org/tests/1156297 ID: 1156298 Test: x86_64 universal upgrade_server_domain_controller URL: https://openqa.fedoraproject.org/tests/1156298 ID: 1156303 Test: x86_64 universal upgrade_realmd_client URL: https://openqa.fedoraproject.org/tests/1156303 ID: 1156320 Test: x86_64 universal upgrade_2_server_64bit URL: https://openqa.fedoraproject.org/tests/1156320 ID: 1156321 Test: x86_64 universal upgrade_2_server_domain_controller URL: https://openqa.fedoraproject.org/tests/1156321 ID: 1156322 Test: x86_64 universal upgrade_desktop_encrypted_64bit URL: https://openqa.fedoraproject.org/tests/1156322 ID: 1156323 Test: x86_64 universal upgrade_kde_64bit URL: https://openqa.fedoraproject.org/tests/1156323 ID: 1156337 Test: x86_64 universal upgrade_2_realmd_client URL: https://openqa.fedoraproject.org/tests/1156337 ID: 1156340 Test: x86_64 universal upgrade_2_desktop_64bit URL: https://openqa.fedoraproject.org/tests/1156340 ID: 1156341 Test: x86_64 universal upgrade_2_desktop_encrypted_64bit URL: https://openqa.fedoraproject.org/tests/1156341 ID: 1156342 Test: x86_64 universal upgrade_2_kde_64bit URL: https://openqa.fedoraproject.org/tests/1156342 ID: 1156371 Test: aarch64 universal upgrade_server_64bit@uefi URL: https://openqa.fedoraproject.org/tests/1156371 ID: 1156372 Test: aarch64 universal upgrade_server_domain_controller@uefi URL: https://openqa.fedoraproject.org/tests/1156372 ID: 1156375 Test: aarch64 universal upgrade_realmd_client@uefi URL: https://openqa.fedoraproject.org/tests/1156375 ID: 1156384 Test: aarch64 universal upgrade_2_server_64bit@uefi URL: https://openqa.fedoraproject.org/tests/1156384 ID: 1156385 Test: aarch64 universal upgrade_2_server_domain_controller@uefi URL: https://openqa.fedoraproject.org/tests/1156385 ID: 1156386
Re: s390x KOJI builders issue
* Michael Catanzaro: > On Wed, Mar 2 2022 at 02:21:22 PM +0100, Dan Horák > wrote: >> those are weird, the build tasks have been restarted many times by the >> builder daemon, after something crashed there (OOM?) ... > > This was happening to me on armv7hl a few weeks ago. Kevin Fenzi > investigated and discovered that the builds kept hitting an OOM > condition and then restarting, which triggered an infinite loop. Each > build would work for 3-5 hours before failing, then it would start > over, then again, then again > > I think some configuration changed recently on the builders, because I > had never seen this happen before last month. If a build hits OOM, it > really needs to fail immediately. It should not restart, because it's > likely to fail again the same way. My builds had restarted four or > five times before Kevin manually handled them. Maybe Koji restarts the build because the builder has rebooted? Thanks, Florian ___ 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 Linux 36 Beta Go/No-Go meeting next week
Hi everyone, It's that time already! The Fedora Linux 36 Beta Go/No-Go[1] meeting is scheduled for Thursday 10 March at 1700 UTC in #fedora-meeting. At this time, we will determine the status of the F36 Beta for the 15 March early target date[2]. For more information about the Go/No-Go meeting, see the wiki[3]. [1] https://calendar.fedoraproject.org/meeting/10209/ [2] https://fedorapeople.org/groups/schedule/f-36/f-36-key-tasks.html [3] https://fedoraproject.org/wiki/Go_No_Go_Meeting -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel-announce@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Test-Announce] Fedora Linux 36 Beta Go/No-Go meeting next week
Hi everyone, It's that time already! The Fedora Linux 36 Beta Go/No-Go[1] meeting is scheduled for Thursday 10 March at 1700 UTC in #fedora-meeting. At this time, we will determine the status of the F36 Beta for the 15 March early target date[2]. For more information about the Go/No-Go meeting, see the wiki[3]. [1] https://calendar.fedoraproject.org/meeting/10209/ [2] https://fedorapeople.org/groups/schedule/f-36/f-36-key-tasks.html [3] https://fedoraproject.org/wiki/Go_No_Go_Meeting -- 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
Fedora-IoT-36-20220302.0 compose check report
No missing expected images. Failed openQA tests: 2/15 (x86_64), 1/15 (aarch64) New failures (same test not failed in Fedora-IoT-36-20220228.0): ID: 1156421 Test: x86_64 IoT-dvd_ostree-iso iot_clevis@uefi URL: https://openqa.fedoraproject.org/tests/1156421 ID: 1156422 Test: x86_64 IoT-dvd_ostree-iso install_default_upload@uefi URL: https://openqa.fedoraproject.org/tests/1156422 Old failures (same test failed in Fedora-IoT-36-20220228.0): ID: 1156436 Test: aarch64 IoT-dvd_ostree-iso iot_clevis@uefi URL: https://openqa.fedoraproject.org/tests/1156436 Passed openQA tests: 14/15 (aarch64) New passes (same test not passed in Fedora-IoT-36-20220228.0): ID: 1156438 Test: aarch64 IoT-dvd_ostree-iso iot_zezere_server@uefi URL: https://openqa.fedoraproject.org/tests/1156438 ID: 1156450 Test: aarch64 IoT-dvd_ostree-iso iot_zezere_ignition@uefi URL: https://openqa.fedoraproject.org/tests/1156450 Skipped non-gating openQA tests: 13 of 30 Installed system changes in test aarch64 IoT-dvd_ostree-iso install_default_upload@uefi: System load changed from 0.43 to 0.28 Previous test data: https://openqa.fedoraproject.org/tests/1152728#downloads Current test data: https://openqa.fedoraproject.org/tests/1156437#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
Re: Chromium security bugs remain unfixed for > 1 month
On Wed, Mar 02, 2022 at 07:08:07AM -0500, Neal Gompa wrote: > Those features provide tangible benefits to the community at large > that we would lose by "sloppy packaging". Instead of kvetching, why > not try helping? Maybe *ask* Tom what you could do to help him ship > newer versions? Neal, please reign in your rhetoric a bit. This is a discussion about packaging, not the people involved. BTW, the first email asked: > Tom Callaway, what is the hardest part for you? 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: s390x KOJI builders issue
On Wed, Mar 2 2022 at 02:21:22 PM +0100, Dan Horák wrote: those are weird, the build tasks have been restarted many times by the builder daemon, after something crashed there (OOM?) ... This was happening to me on armv7hl a few weeks ago. Kevin Fenzi investigated and discovered that the builds kept hitting an OOM condition and then restarting, which triggered an infinite loop. Each build would work for 3-5 hours before failing, then it would start over, then again, then again I think some configuration changed recently on the builders, because I had never seen this happen before last month. If a build hits OOM, it really needs to fail immediately. It should not restart, because it's likely to fail again the same way. My builds had restarted four or five times before Kevin manually handled them. Michael ___ 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
[EPEL-devel] Re: Missing RHEL 9 buildroot packages in EPEL 9 buildroot
On Wed, Mar 2, 2022 at 8:52 AM Richard W.M. Jones wrote: > > To keep this a bit more specific, we're trying to build coccinelle for > EPEL 9. This requires ocaml [compiler] and a bunch of ocaml packages. > They are mainly in RHEL buildroot. > > The problem we're going to have (which to be fair is a problem > somewhat specific to OCaml linking) is that an alternate OCaml > compiler built for EPEL will have different hash values[1] for core > libraries. > > If we use a different version from the RHEL compiler, say we use > Fedora Rawhide version, then all the hashes will be different. > > If we use the same version as in RHEL, then most hash values will be > the same, but if the compiler flags are even slightly different then > there will be some differences. > > OCaml libraries in RHEL that we do ship (ocaml-libnbd and others) will > not be linkable with code compiled with the EPEL toolchain. > > It's entirely possible we don't care about this, and I maybe even > agree. But also that people using RHEL with EPEL added will get into > weird situations if they try to recompile the virt tools packages. > > Rich. > > [1] Hash values are computed over the modules to prevent linking > incompatible versions: > > $ ocamlobjinfo /usr/lib64/ocaml/unix.cma | grep Unix > Unit name: Unix > 49c6c492a189deeaed5bf77a6793e7fa Unix > > and turned into RPM dependencies: > > $ rpm -qR ocaml | grep Unix > ocaml(Unix) = 49c6c492a189deeaed5bf77a6793e7fa > So why not have the OCaml toolchain exposed in RHEL CRB? It sounds like it would be very beneficial to have it there. -- 真実はいつも一つ！/ Always, there's only one truth! ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Orphaned python-aiohttp-cors
Hello, I've maintained python-aiohttp-cors because python-black required it, but it no longer does, so I've just orphaned it. The package is now only required by gns3-server. The package builds, installs, builds with Python 3.11 (we have just pushed a fix). However, it appears dead upstream. Consider dropping the dependency instead of taking the package. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-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/python-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Orphaned python-aiohttp-cors
Hello, I've maintained python-aiohttp-cors because python-black required it, but it no longer does, so I've just orphaned it. The package is now only required by gns3-server. The package builds, installs, builds with Python 3.11 (we have just pushed a fix). However, it appears dead upstream. Consider dropping the dependency instead of taking the package. -- 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
[Test-Announce] Fedora-IoT 36 RC 20220302.0 nightly compose nominated for testing
Announcing the creation of a new nightly release validation test event for Fedora-IoT 36 RC 20220302.0. Please help run some tests for this nightly compose if you have time. For more information on nightly release validation testing, see: https://fedoraproject.org/wiki/QA:Release_validation_test_plan Test coverage information for the current release can be seen at: https://openqa.fedoraproject.org/testcase_stats/36iot You can see all results, find testing instructions and image download locations, and enter results on the Summary page: https://fedoraproject.org/wiki/Test_Results:Fedora-IoT_36_RC_20220302.0_Summary The individual test result pages are: https://fedoraproject.org/wiki/Test_Results:Fedora-IoT_36_RC_20220302.0_General Thank you for testing! -- Mail generated by relvalconsumer: https://pagure.io/fedora-qa/relvalconsumer ___ 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
[EPEL-devel] Re: Missing RHEL 9 buildroot packages in EPEL 9 buildroot
To keep this a bit more specific, we're trying to build coccinelle for EPEL 9. This requires ocaml [compiler] and a bunch of ocaml packages. They are mainly in RHEL buildroot. The problem we're going to have (which to be fair is a problem somewhat specific to OCaml linking) is that an alternate OCaml compiler built for EPEL will have different hash values[1] for core libraries. If we use a different version from the RHEL compiler, say we use Fedora Rawhide version, then all the hashes will be different. If we use the same version as in RHEL, then most hash values will be the same, but if the compiler flags are even slightly different then there will be some differences. OCaml libraries in RHEL that we do ship (ocaml-libnbd and others) will not be linkable with code compiled with the EPEL toolchain. It's entirely possible we don't care about this, and I maybe even agree. But also that people using RHEL with EPEL added will get into weird situations if they try to recompile the virt tools packages. Rich. [1] Hash values are computed over the modules to prevent linking incompatible versions: $ ocamlobjinfo /usr/lib64/ocaml/unix.cma | grep Unix Unit name: Unix 49c6c492a189deeaed5bf77a6793e7fa Unix and turned into RPM dependencies: $ rpm -qR ocaml | grep Unix ocaml(Unix) = 49c6c492a189deeaed5bf77a6793e7fa -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-builder quickly builds VMs from scratch http://libguestfs.org/virt-builder.1.html ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: s390x KOJI builders issue
On Wed, 2 Mar 2022 14:08:23 +0100 Michal Schorm wrote: > Hello, > for the last few days, I'm not able to finish my builds of the > 'mariadb' package on s390x architecture. > > Those builds freeze, e.g. several of these: > https://koji.fedoraproject.org/koji/taskinfo?taskID=83297826 > https://koji.fedoraproject.org/koji/taskinfo?taskID=83296979 > https://koji.fedoraproject.org/koji/taskinfo?taskID=83292553 > https://koji.fedoraproject.org/koji/taskinfo?taskID=83290439 > https://koji.fedoraproject.org/koji/taskinfo?taskID=83295670 > https://koji.fedoraproject.org/koji/taskinfo?taskID=83293919 > have >100 hours total time before finally failing. those are weird, the build tasks have been restarted many times by the builder daemon, after something crashed there (OOM?) ... Dan > > Even the new one I submitte have already > 22 hours count: > https://koji.fedoraproject.org/koji/taskinfo?taskID=83514145 > > The MariaDB build - especially with the full testsuite on - is very > resource hungry. > However the freezes are strange, since sometimes it freezes randomly > even during compilation, while sometimes %check phase ... > > -- > > Michal Schorm > Software Engineer > Core Services - Databases 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 ___ 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
s390x KOJI builders issue
Hello, for the last few days, I'm not able to finish my builds of the 'mariadb' package on s390x architecture. Those builds freeze, e.g. several of these: https://koji.fedoraproject.org/koji/taskinfo?taskID=83297826 https://koji.fedoraproject.org/koji/taskinfo?taskID=83296979 https://koji.fedoraproject.org/koji/taskinfo?taskID=83292553 https://koji.fedoraproject.org/koji/taskinfo?taskID=83290439 https://koji.fedoraproject.org/koji/taskinfo?taskID=83295670 https://koji.fedoraproject.org/koji/taskinfo?taskID=83293919 have >100 hours total time before finally failing. Even the new one I submitte have already > 22 hours count: https://koji.fedoraproject.org/koji/taskinfo?taskID=83514145 The MariaDB build - especially with the full testsuite on - is very resource hungry. However the freezes are strange, since sometimes it freezes randomly even during compilation, while sometimes %check phase ... -- Michal Schorm Software Engineer Core Services - Databases 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: Chromium security bugs remain unfixed for > 1 month
On 02/03/2022 12:44, Demi Marie Obenour wrote: That doesn’t explain why RPM Fusion gets updates so much more quickly. RPM Fusion don't need to manually strip ffmpeg, apply some specific patches, etc. In the case of something like Chromium, a sloppy package that gets timely updates is better than a fully conforming package that does not. It depends. As for me, I prefer a well-packaged Fedora package than using a proprietary build. -- 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
Fedora 36 compose report: 20220302.n.0 changes
OLD: Fedora-36-20220301.n.0 NEW: Fedora-36-20220302.n.0 = SUMMARY = Added images:0 Dropped images: 0 Added packages: 0 Dropped packages:0 Upgraded packages: 0 Downgraded packages: 0 Size of added packages: 0 B Size of dropped packages:0 B 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 = = ADDED PACKAGES = = DROPPED PACKAGES = = 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: Chromium security bugs remain unfixed for > 1 month
On Wed, Mar 2, 2022 at 6:44 AM Demi Marie Obenour wrote: > > On 3/2/22 04:05, Vitaly Zaitsev via devel wrote: > > On 02/03/2022 01:21, Demi Marie Obenour wrote: > >> What are the differences between the RPMFusion SRPM and the > >> Fedora SRPM? > > > > RPM Fusion version includes all available multimedia codecs. > > That doesn’t explain why RPM Fusion gets updates so much more > quickly. > > >> Tom Callaway, what is the hardest part for you? > > > > Packaging of Google's software is a nightmare. They do their best to > > make packaging as difficult as possible by using dozens of bundled > > libraries, their own build system, etc. > > In the case of something like Chromium, a sloppy package that gets > timely updates is better than a fully conforming package that does not. You do not know what you're asking for. You're asking for packaging where we may wind up having things of questionable legality, questionable licensing, and questionable integration that can cause serious issues for Fedora users and downstreams. As a security person, you should be ashamed that you thought this was a good idea. Maximizing reuse across the Fedora ecosystem provides significant benefits because we are able to leverage our quality components, our hardening capabilities, and provide additional capabilities to benefit consumption within the Fedora ecosystem. For example, Fedora's Chromium will attempt to use Wayland by default on a Wayland desktop. Upstream Chrom(e|ium) is not ready for that yet. We ship VA-API integration, which Google doesn't offer. We have working screencasting on Wayland, which upstream doesn't have right now by default. We can enable security features that upstream refuses to (CaBLE, for example). And so on. Those features provide tangible benefits to the community at large that we would lose by "sloppy packaging". Instead of kvetching, why not try helping? Maybe *ask* Tom what you could do to help him ship newer versions? The same goes for everyone else on this thread so far. I'm disappointed by the OP and everyone else in this thread who thinks it's okay to do less than a good job on shipping software. The only complaint I could probably see is that the patches he's got haven't been submitted upstream, but submitting to Chromium upstream is *hard* (I've made contributions to Chromium and it's really not easy to do) and I assume he's working on it. -- 真実はいつも一つ！/ 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
[Bug 2059170] perl-CPAN-Perl-Releases-5.20220227 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2059170 --- Comment #1 from Fedora Update System --- FEDORA-2022-ca69cea458 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-ca69cea458 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2059170 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2059170] perl-CPAN-Perl-Releases-5.20220227 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2059170 --- Comment #2 from Fedora Update System --- FEDORA-2022-af355c9cb8 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-af355c9cb8 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2059170 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora-Rawhide-20220302.n.0 compose check report
Missing expected images: Minimal raw-xz armhfp Compose PASSES proposed Rawhide gating check! All required tests passed Failed openQA tests: 21/231 (x86_64), 20/161 (aarch64) New failures (same test not failed in Fedora-Rawhide-20220301.n.0): ID: 1155668 Test: x86_64 Workstation-live-iso desktop_printing URL: https://openqa.fedoraproject.org/tests/1155668 ID: 1155680 Test: x86_64 KDE-live-iso desktop_printing URL: https://openqa.fedoraproject.org/tests/1155680 ID: 1155710 Test: x86_64 Cloud_Base-qcow2-qcow2 base_package_install_remove@uefi URL: https://openqa.fedoraproject.org/tests/1155710 ID: 1155750 Test: aarch64 Server-dvd-iso install_btrfs_preserve_home_uefi@uefi URL: https://openqa.fedoraproject.org/tests/1155750 ID: 1155785 Test: aarch64 Workstation-raw_xz-raw.xz evince@uefi URL: https://openqa.fedoraproject.org/tests/1155785 ID: 1155843 Test: aarch64 Workstation-upgrade desktop_update_graphical@uefi URL: https://openqa.fedoraproject.org/tests/1155843 ID: 1155855 Test: x86_64 universal install_simple_free_space@uefi URL: https://openqa.fedoraproject.org/tests/1155855 ID: 1155873 Test: x86_64 universal upgrade_server_domain_controller URL: https://openqa.fedoraproject.org/tests/1155873 ID: 1155878 Test: x86_64 universal upgrade_realmd_client URL: https://openqa.fedoraproject.org/tests/1155878 ID: 1155911 Test: x86_64 universal upgrade_2_minimal_64bit URL: https://openqa.fedoraproject.org/tests/1155911 ID: 1155929 Test: aarch64 universal upgrade_minimal_64bit@uefi URL: https://openqa.fedoraproject.org/tests/1155929 ID: 1155946 Test: aarch64 universal upgrade_server_64bit@uefi URL: https://openqa.fedoraproject.org/tests/1155946 ID: 1155957 Test: aarch64 universal install_kickstart_hdd@uefi URL: https://openqa.fedoraproject.org/tests/1155957 ID: 1155958 Test: aarch64 universal install_xfs@uefi URL: https://openqa.fedoraproject.org/tests/1155958 ID: 1155964 Test: aarch64 universal install_delete_partial@uefi URL: https://openqa.fedoraproject.org/tests/1155964 ID: 1155973 Test: aarch64 universal install_repository_http_variation@uefi URL: https://openqa.fedoraproject.org/tests/1155973 ID: 1155985 Test: aarch64 Server-raw_xz-raw.xz install_arm_image_deployment_upload@uefi URL: https://openqa.fedoraproject.org/tests/1155985 Old failures (same test failed in Fedora-Rawhide-20220301.n.0): ID: 1155616 Test: x86_64 Server-dvd-iso modularity_tests URL: https://openqa.fedoraproject.org/tests/1155616 ID: 1155649 Test: x86_64 Workstation-live-iso gnome_text_editor URL: https://openqa.fedoraproject.org/tests/1155649 ID: 1155665 Test: x86_64 Workstation-live-iso eog URL: https://openqa.fedoraproject.org/tests/1155665 ID: 1155670 Test: x86_64 KDE-live-iso anaconda_help URL: https://openqa.fedoraproject.org/tests/1155670 ID: 1155671 Test: x86_64 KDE-live-iso desktop_notifications_live URL: https://openqa.fedoraproject.org/tests/1155671 ID: 1155681 Test: x86_64 KDE-live-iso desktop_notifications_postinstall URL: https://openqa.fedoraproject.org/tests/1155681 ID: 1155688 Test: x86_64 KDE-live-iso apps_startstop URL: https://openqa.fedoraproject.org/tests/1155688 ID: 1155693 Test: x86_64 Silverblue-dvd_ostree-iso install_default_upload URL: https://openqa.fedoraproject.org/tests/1155693 ID: 1155696 Test: x86_64 Silverblue-dvd_ostree-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/1155696 ID: 1155734 Test: aarch64 Server-dvd-iso modularity_tests@uefi URL: https://openqa.fedoraproject.org/tests/1155734 ID: 1155791 Test: aarch64 Workstation-raw_xz-raw.xz eog@uefi URL: https://openqa.fedoraproject.org/tests/1155791 ID: 1155797 Test: aarch64 Workstation-raw_xz-raw.xz gnome_text_editor@uefi URL: https://openqa.fedoraproject.org/tests/1155797 ID: 1155799 Test: aarch64 Workstation-raw_xz-raw.xz desktop_update_graphical@uefi URL: https://openqa.fedoraproject.org/tests/1155799 ID: 1155820 Test: x86_64 Workstation-upgrade gnome_text_editor URL: https://openqa.fedoraproject.org/tests/1155820 ID: 1155825 Test: x86_64 Workstation-upgrade desktop_fprint URL: https://openqa.fedoraproject.org/tests/1155825 ID: 1155834 Test: aarch64 Workstation-upgrade eog@uefi URL: https://openqa.fedoraproject.org/tests/1155834 ID: 1155840 Test: aarch64 Workstation-upgrade gnome_text_editor@uefi URL: https://openqa.fedoraproject.org/tests/1155840 ID: 1155851 Test: x86_64 universal install_european_language URL: https://openqa.fedoraproject.org/tests/1155851 ID: 1155874 Test: x86_64 universal install_arabic_language URL: https://openqa.fedoraproject.org/tests/1155874 ID: 1155875 Test: x86_64 universal install_asian_language URL: https://openqa.fedoraproject.org/tests/1155875 ID: 1155940 Test: aarch64 universal install_arabic_language@uefi URL: https://openqa.fedoraproject.org/tests/1155940 ID: 1155948 Test: aarch64 universal install_asian_language@uefi URL:
[Bug 2059170] perl-CPAN-Perl-Releases-5.20220227 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2059170 Jitka Plesnikova changed: What|Removed |Added Status|ASSIGNED|MODIFIED Fixed In Version||perl-CPAN-Perl-Releases-5.2 ||0220227-1.fc37 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2059170 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Chromium security bugs remain unfixed for > 1 month
On 3/2/22 04:05, Vitaly Zaitsev via devel wrote: > On 02/03/2022 01:21, Demi Marie Obenour wrote: >> What are the differences between the RPMFusion SRPM and the >> Fedora SRPM? > > RPM Fusion version includes all available multimedia codecs. That doesn’t explain why RPM Fusion gets updates so much more quickly. >> Tom Callaway, what is the hardest part for you? > > Packaging of Google's software is a nightmare. They do their best to > make packaging as difficult as possible by using dozens of bundled > libraries, their own build system, etc. In the case of something like Chromium, a sloppy package that gets timely updates is better than a fully conforming package that does not. -- 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
[Bug 2059170] perl-CPAN-Perl-Releases-5.20220227 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2059170 Jitka Plesnikova changed: What|Removed |Added Doc Type|--- |If docs needed, set a value Status|NEW |ASSIGNED CC|iarn...@gmail.com, | |jples...@redhat.com | -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2059170 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2058963] perl-App-cpm-0.997009 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2058963 --- Comment #2 from Fedora Update System --- FEDORA-2022-12439ce7de has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-12439ce7de -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2058963 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2059504] perl-Test-DistManifest-1.014-22.fc37 FTBFS: Failed test 'All files are listed in MANIFEST or skipped'
https://bugzilla.redhat.com/show_bug.cgi?id=2059504 --- Comment #6 from Paul Howarth --- As is the debuginfo generator, unfortunately. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2059504 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2058963] perl-App-cpm-0.997009 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2058963 Jitka Plesnikova changed: What|Removed |Added Status|ASSIGNED|MODIFIED Fixed In Version||perl-App-cpm-0.997.009-1.fc ||37 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2058963 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2059504] perl-Test-DistManifest-1.014-22.fc37 FTBFS: Failed test 'All files are listed in MANIFEST or skipped'
https://bugzilla.redhat.com/show_bug.cgi?id=2059504 --- Comment #5 from Petr Pisar --- I see. I wasn't aware the notes generator is active even for noarch packages. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2059504 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora-Cloud-34-20220302.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-20220301.0): ID: 1156000 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/1156000 ID: 1156006 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi URL: https://openqa.fedoraproject.org/tests/1156006 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: VERY late notification emails
On 28. 02. 22 18:24, Kevin Fenzi wrote: On Mon, Feb 28, 2022 at 07:45:27AM -0600, Richard Shaw wrote: I almost wrote this a week ago but decided not to as it's been recently discussed but this is really annoying. 6 days later is more than useless. Previously it was blamed, at least partially, on the mass rebuild, but clearly that should no longer be an issue by now? Well, I noted a number of reasons for it... one of them was that it sometimes crashes, but appears to be processing. This happened a few days ago and it was just restarted this morning. ;( I know I can turn them off, but I actually LIKE the messages if they were delivered promptly. Is there really nothing we can do about this? No, there's things we can do and are trying to do. ;) But of course more help welcome! We have a python3 port of it nearly ready to go, but I think it's CI/tests are not working, and we want to make sure those all work before we deploy it. I'll see if I can get more exact status... CI is now working and the tests are passing. But I wasn't able to actually found out how the new version FMN should be released. Michal There's also been a lot of talk about re-writing it. Ryan just posted recently asking for folks use cases and pain points for that. I'll see about making it restart every day perhaps to make sure it's actually processing. kevin ___ 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
[Bug 2058963] perl-App-cpm-0.997009 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2058963 Jitka Plesnikova changed: What|Removed |Added Doc Type|--- |If docs needed, set a value Status|NEW |ASSIGNED CC|jples...@redhat.com | -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2058963 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora rawhide compose report: 20220302.n.0 changes
OLD: Fedora-Rawhide-20220301.n.0 NEW: Fedora-Rawhide-20220302.n.0 = SUMMARY = Added images:0 Dropped images: 0 Added packages: 11 Dropped packages:16 Upgraded packages: 86 Downgraded packages: 0 Size of added packages: 116.00 MiB Size of dropped packages:115.94 MiB Size of upgraded packages: 1.33 GiB Size of downgraded packages: 0 B Size change of upgraded packages: 20.88 MiB Size change of downgraded packages: 0 B = ADDED IMAGES = = DROPPED IMAGES = = ADDED PACKAGES = Package: c-ares-1.17.2-2.module_f37+13931+3425fdb4 Summary: A library that performs asynchronous DNS operations RPMs:c-ares c-ares-devel Size:805.49 KiB Package: libuv-1:1.43.0-3.module_f37+13931+3425fdb4 Summary: Platform layer for node.js RPMs:libuv libuv-devel libuv-static Size:1.24 MiB Package: nghttp2-1.47.0-1.module_f37+13931+3425fdb4 Summary: Experimental HTTP/2 client, server and proxy RPMs:libnghttp2 libnghttp2-devel nghttp2 Size:2.77 MiB Package: nodejs-1:14.19.0-3.module_f37+13931+3425fdb4 Summary: JavaScript runtime RPMs:nodejs nodejs-devel nodejs-docs nodejs-full-i18n nodejs-libs npm v8-devel Size:102.51 MiB Package: nodejs-packaging-2021.06-4.module_f37+13931+3425fdb4 Summary: RPM Macros and Utilities for Node.js Packaging RPMs:nodejs-packaging nodejs-packaging-bundler Size:29.98 KiB Package: perl-DBD-MySQL-4.050-10.module_f37+13916+d9f42f3d Summary: A MySQL interface for Perl RPMs:perl-DBD-MySQL Size:580.21 KiB Package: perl-DBD-Pg-3.14.2-4.module_f37+13925+39200601 Summary: A PostgreSQL interface for Perl RPMs:perl-DBD-Pg Size:874.56 KiB Package: perl-DBD-SQLite-1.66-3.module_f37+13936+7c955f94 Summary: SQLite DBI Driver RPMs:perl-DBD-SQLite Size:768.27 KiB Package: rust-vhost-0.3.0-1.fc37 Summary: Pure rust library for vdpa, vhost and vhost-user RPMs:rust-vhost+default-devel rust-vhost+vhost-kern-devel rust-vhost+vhost-net-devel rust-vhost+vhost-user-devel rust-vhost+vhost-user-master-devel rust-vhost+vhost-user-slave-devel rust-vhost+vhost-vdpa-devel rust-vhost+vhost-vsock-devel rust-vhost-devel Size:251.43 KiB Package: rust-virtio-queue-0.1.0-2.fc37 Summary: Virtio queue implementation RPMs:rust-virtio-queue+default-devel rust-virtio-queue+test-utils-devel rust-virtio-queue-devel Size:52.13 KiB Package: siril-1.0.0~rc2-1.fc37 Summary: Astronomical image processing software RPMs:siril Size:6.19 MiB = DROPPED PACKAGES = Package: fasttrack-6.2.1-2.fc37 Summary: Multiple objects tracking software, easy to use, and performant. RPMs:fasttrack fasttrack-cli fasttrack-doc Size:4.49 MiB Package: golang-github-mitchellh-goamz-0-0.29.20180708gitcaaaea8.fc36 Summary: Golang Amazon Library RPMs:golang-github-mitchellh-goamz-devel Size:123.44 KiB Package: keepass-2.50-1.fc36 Summary: Password manager RPMs:keepass Size:5.67 MiB Package: libicu65-65.1-1.fc33 Summary: Compat package with icu libraries RPMs:libicu65 Size:48.13 MiB Package: libicu67-67.1-3.fc36 Summary: Compat package with icu libraries RPMs:libicu67 Size:47.86 MiB Package: mingw-giflib-5.2.1-8.fc36 Summary: MinGW Windows giflib library RPMs:mingw32-giflib-static mingw64-giflib-static Size:51.90 KiB Package: mingw-gtkspell3-3.0.10-10.fc36 Summary: MinGW Windows GtkSpell3 library RPMs:mingw32-gtkspell3-static mingw64-gtkspell3-static Size:39.26 KiB Package: mingw-gtkspellmm30-3.0.5-15.fc36 Summary: MinGW Windows GtkSpellmm library RPMs:mingw32-gtkspellmm30-static mingw64-gtkspellmm30-static Size:29.57 KiB Package: mingw-leptonica-1.82.0-2.fc36 Summary: MinGW Windows Leptonica library RPMs:mingw32-leptonica-static mingw64-leptonica-static Size:2.15 MiB Package: mingw-libgeotiff-1.7.0-4.fc36 Summary: MinGW Windows libgeotiff library RPMs:mingw32-libgeotiff-static mingw64-libgeotiff-static Size:115.07 KiB Package: mingw-python-pillow-9.0.1-3.fc37 Summary: MinGW Windows Python pillow library RPMs:mingw32-python3-pillow mingw64-python3-pillow Size:1.38 MiB Package: rubygem-cucumber-rails-1.8.0-5.fc33 Summary: Cucumber Generators and Runtime for Rails RPMs:rubygem-cucumber-rails rubygem-cucumber-rails-doc Size:290.66 KiB Package: rubygem-sup-1.0-2.fc33 Summary: A console-based email client written in ruby RPMs:rubygem-sup rubygem-sup-doc Size:907.79 KiB Package: rust-andrew-0.3.1-4.fc36 Summary: Convenient drawing of shapes, lines and text to buffers RPMs:rust-andrew+default-devel rust-andrew-devel Size:27.64 KiB Package: rust-smithay-client-toolkit0.12-0.12.2-3.fc36 Summary: Toolkit for making client wayland applications RPMs:rust-smithay-client-toolkit0.12+andrew-devel rust-smithay-client-toolkit0.12+calloop-devel rust-smithay-client-toolkit0.12+default-devel rust-smithay-client-toolkit0.12+frames-devel rust-smithay-client-toolkit0.12-devel Size:142.04 KiB
Re: Chromium security bugs remain unfixed for > 1 month
On 02/03/2022 02:45, Demi Marie Obenour wrote: I am surprised that the answer is not to automatically download and install Canonical’s Snap package Absolutely no way. Everything must be built from sources on trusted infra. No exceptions. -- 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
