[389-devel] 389 DS nightly 2020-03-21 - 94% PASS
https://fedorapeople.org/groups/389ds/ci/nightly/2020/03/21/report-389-ds-base-1.4.3.4-20200321gitd1b746b.fc31.x86_64.html ___ 389-devel mailing list -- 389-devel@lists.fedoraproject.org To unsubscribe send an email to 389-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/389-devel@lists.fedoraproject.org
[Test-Announce] 2020-03-23 @ 16:00 UTC - Fedora 32 Blocker Review Meeting
# F32 Blocker Review meeting # Date: 2020-03-23 # Time: 16:00 UTC # Location: #fedora-blocker-review on irc.freenode.net Hi folks! We have 7 proposed Final blockers and 1 proposed Final freeze exception to review, so let's have a Fedora 32 blocker review meeting on Monday! If you have time this weekend, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F32 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good weekend and see you on Monday! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net ___ 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 ___ 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
[Test-Announce] Proposal to CANCEL: 2020-03-23 Fedora QA Meeting
Hi folks! I'm proposing we cancel the QA meeting for tomorrow. We met last week and I don't think we have any urgent business this week. There will be a blocker review meeting. If you're aware of anything important we have to discuss this week, please do reply to this mail and we can go ahead and run the meeting. Thanks! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net ___ 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 ___ 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
[Bug 1815682] New: perl-Module-CoreList-5.20200320 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1815682 Bug ID: 1815682 Summary: perl-Module-CoreList-5.20200320 is available Product: Fedora Version: rawhide Status: NEW Component: perl-Module-CoreList Keywords: FutureFeature, Triaged Assignee: ppi...@redhat.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: jose.p.oliveira@gmail.com, jples...@redhat.com, perl-devel@lists.fedoraproject.org, ppi...@redhat.com, st...@silug.org, tcall...@redhat.com Target Milestone: --- Classification: Fedora Latest upstream release: 5.20200320 Current version/release in rawhide: 5.20200314-1.fc33 URL: http://search.cpan.org/dist/Module-CoreList/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/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/3080/ -- You are receiving this mail because: You are on the CC list for the bug. ___ 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
Re: RFC: entering luks password on grub level for devices without keyboards
On Fri, Mar 20, 2020 at 1:50 AM Petr Pisar wrote: > > On Thu, Mar 19, 2020 at 12:59:01PM -0600, Chris Murphy wrote: > > On Thu, Mar 19, 2020 at 11:53 AM Marius Schwarz > > wrote: > > > > > > Am 19.03.20 um 17:11 schrieb Michael Cronenworth: > > > > On 3/19/20 11:04 AM, Marius Schwarz wrote: > > > >> correct and thats the main issue, as long you have grub where you can > > > >> edit the kernel line to start in runlevel 1. > > > >> This makes the encryption null and void. > > > > > > > > Adding a grub password will prevent those without it from editing your > > > > boot parameters. By default you can still boot without the grub > > > > password. Does that help? > > > > > > It would solve a problem. > > > > > > - does it prevent updates ( after booting into rl 5 ) of grub? > > > - where is the passcode stored? > > > > grub.cfg or user.cfg contains the hashed password > > > > https://wiki.archlinux.org/index.php/GRUB/Tips_and_tricks#Password_protection_of_GRUB_menu > > https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/system_administrators_guide/sec-protecting_grub_2_with_a_password > > > > But if the attacker has physical access to the computer, they can > > mount /boot/efi or /boot where this file is stored; and remove the > > password requirement. > > Not at all. GRUB code and configuration are protected by TPM measurement. If > an > attacker tampers them, decrypting LUKS will fail on a missing or wrong > passphrase. I wasn't assuming measured boot; but in that case it provides better protection without needing the locked up kiosk setup. But none of this is really easy to setup right now, quite a lot of people have computers without a TPM. -- Chris Murphy ___ 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
[Bug 1815667] New: perl-CPAN-Perl-Releases-5.20200320 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1815667 Bug ID: 1815667 Summary: perl-CPAN-Perl-Releases-5.20200320 is available Product: Fedora Version: rawhide Status: NEW Component: perl-CPAN-Perl-Releases Keywords: FutureFeature, Triaged Assignee: jples...@redhat.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: iarn...@gmail.com, jples...@redhat.com, perl-devel@lists.fedoraproject.org Target Milestone: --- Classification: Fedora Latest upstream release: 5.20200320 Current version/release in rawhide: 5.20200314-1.fc33 URL: http://search.cpan.org/dist/CPAN-Perl-Releases/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/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/5881/ -- You are receiving this mail because: You are on the CC list for the bug. ___ 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
Re: Fedora 33 System-Wide Change proposal: Sqlite RpmDB
On Tue, Mar 17, 2020 at 6:06 AM Panu Matilainen wrote: > > On 3/16/20 6:25 PM, Neal Gompa wrote: > > > > I'm glad to *finally* see this happen, so congratulations to the RPM > > team for finally making this a reality! I look forward to trying this > > out in Rawhide as soon as possible. > > FWIW, those who want an early taste, you can try my rpm-snapshot repo: > https://copr.fedorainfracloud.org/coprs/pmatilai/rpm-snapshot/ > > I run those snapshots on my own laptop at all times so it's not supposed > or expected to eat your disk or anything like that, but caveat emptor. > I've been running the snapshots for a few days now, and it seems to be somewhat faster than BDB on my machine. Generally haven't seen any issues so far! Though out of curiosity, have you done some performance analysis on this to show off to everyone? -- 真実はいつも一つ！/ 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
Fedora 32 compose report: 20200320.n.0 changes
OLD: Fedora-32-20200319.n.0 NEW: Fedora-32-20200320.n.0 = SUMMARY = Added images:0 Dropped images: 0 Added packages: 0 Dropped packages:0 Upgraded packages: 10 Downgraded packages: 0 Size of added packages: 0 B Size of dropped packages:0 B Size of upgraded packages: 128.84 MiB Size of downgraded packages: 0 B Size change of upgraded packages: 728.87 KiB Size change of downgraded packages: 0 B = ADDED IMAGES = = DROPPED IMAGES = = ADDED PACKAGES = = DROPPED PACKAGES = = UPGRADED PACKAGES = Package: clamsmtp-1.10-31.fc32 Old package: clamsmtp-1.10-30.fc32 Summary: A SMTP virus scanning system RPMs: clamsmtp Size: 245.02 KiB Size change: -400 B Changelog: * Thu Feb 27 2020 Nathanael Noblet - 1.10-31 - clamav-server was renamed to clamd Package: cups-filters-1.27.2-1.fc32 Old package: cups-filters-1.27.1-1.fc32 Summary: OpenPrinting CUPS filters and backends RPMs: cups-filters cups-filters-devel cups-filters-libs Size: 4.98 MiB Size change: 105 B Changelog: * Tue Feb 25 2020 Zdenek Dohnal - 1.27.1-2 - 1806862 - foomatic-rip handles empty files in bad way * Mon Mar 02 2020 Zdenek Dohnal - 1.27.2-1 - 1.27.2 Package: dnf-plugins-extras-4.0.9-5.fc32 Old package: dnf-plugins-extras-4.0.9-3.fc32 Summary: Extras Plugins for DNF RPMs: python3-dnf-plugin-kickstart python3-dnf-plugin-rpmconf python3-dnf-plugin-showvars python3-dnf-plugin-snapper python3-dnf-plugin-system-upgrade python3-dnf-plugin-torproxy python3-dnf-plugin-tracer python3-dnf-plugins-extras-common Size: 187.03 KiB Size change: 1.84 KiB Changelog: * Fri Mar 06 2020 Ales Matej - 4.0.9-4 - Fix patch to fix distribution issues with missing upgrade path between dist versions (RhBug:1767351) * Fri Mar 06 2020 Adam Williamson - 4.0.9-5 - Tweak module reset patch to also do reset in `run_upgrade` (RhBug:1767351) Package: fail2ban-0.11.1-4.fc32 Old package: fail2ban-0.11.1-3.fc32 Summary: Daemon to ban hosts that cause multiple authentication errors RPMs: fail2ban fail2ban-all fail2ban-firewalld fail2ban-hostsdeny fail2ban-mail fail2ban-selinux fail2ban-sendmail fail2ban-server fail2ban-shorewall fail2ban-systemd fail2ban-tests Added RPMs: fail2ban-selinux Size: 821.03 KiB Size change: 28.59 KiB Changelog: * Wed Feb 26 2020 Orion Poplawski - 0.11.1-4 - Add SELinux policy Package: fontconfig-2.13.92-7.fc32 Old package: fontconfig-2.13.92-6.fc32 Summary: Font configuration and customization library RPMs: fontconfig fontconfig-devel fontconfig-devel-doc Size: 2.48 MiB Size change: -2.14 KiB Changelog: * Wed Feb 26 2020 Akira TAGOH - 2.13.92-7 - Fix assertion in FcCacheFini(). Package: koji-1.20.1-1.fc32 Old package: koji-1.20.0-2.fc32 Summary: Build system tools RPMs: koji koji-builder koji-builder-plugins koji-hub koji-hub-plugins koji-utils koji-vm koji-web python3-koji python3-koji-cli-plugins python3-koji-hub python3-koji-hub-plugins python3-koji-web Size: 1.02 MiB Size change: -1.84 KiB Changelog: * Fri Mar 06 2020 Kevin Fenzi - 1.20.1-1 - Update to 1.20.1 Package: libarchive-3.4.2-1.fc32 Old package: libarchive-3.4.0-2.fc32 Summary: A library for handling streaming archive formats RPMs: bsdcat bsdcpio bsdtar libarchive libarchive-devel Size: 3.87 MiB Size change: 10.69 KiB Changelog: * Wed Feb 12 2020 Ondrej Dubaj - 3.4.2-1 - Rebased to version 3.4.2 Package: libdnf-0.45.0-2.fc32 Old package: libdnf-0.45.0-1.fc32 Summary: Library providing simplified C and Python API to libsolv RPMs: libdnf libdnf-devel python3-hawkey python3-libdnf Size: 7.98 MiB Size change: 2.43 KiB Changelog: * Fri Mar 06 2020 Ales Matej - 0.45.0-2 - Backport patch to reset active modules when no module enabled or default (1767351) Package: linux-firmware-20200316-106.fc32 Old package: linux-firmware-20200122-105.fc32 Summary: Firmware files used by the Linux kernel RPMs: iwl100-firmware iwl1000-firmware iwl105-firmware iwl135-firmware iwl2000-firmware iwl2030-firmware iwl3160-firmware iwl3945-firmware iwl4965-firmware iwl5000-firmware iwl5150-firmware iwl6000-firmware iwl6000g2a-firmware iwl6000g2b-firmware iwl6050-firmware iwl7260-firmware libertas-sd8686-firmware libertas-sd8787-firmware libertas-usb8388-firmware libertas-usb8388-olpc-firmware linux-firmware linux-firmware-whence liquidio-firmware netronome-firmware Size: 105.63 MiB Size change: 676.28 KiB Changelog: * Mon Mar 16 2020 Peter Robinson 20200316-106 - Update to upstream 20200316 release - Bluetooth firmware updates: Intel, QCom, RTL8822C - Agilio SmartNIC flower firmware to rev AOTC-2.12.A.13 - amdgpu: Update to raven2, renoir, navi10, vega10, vega12, vega20 - Intel i915: HuC, DMC
Does anyone/thing care about the kernel inside the boot.iso rootfs?
We've noticed that there is a kernel inside the install.img of the boot.iso -- it isn't used for booting, and as far as I can tell it's just taking up extra space. But I have no idea if it's safe to remove it :) I have this PR, which works fine for me in my testing: https://github.com/weldr/lorax/pull/926 The corresponding hmac file is being used by the dracut fips module, but that's been solved in dracut-050. Anyone have any objections to removing it? -- Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart ___ 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
Re: Bugzilla signal/noise ratio
On Fri, 2020-03-20 at 11:42 -0400, Paul Dufresne via devel wrote: > > Closing a bug doesn't clear the needinfo. Change the ? to blank under > > flags (or I'm happy to clear it for you if you'd like). > Ok, I have done it. > > But I believe the outstanding bugs reminder should not include closed bugs! There are reasonable situations where a closed bug can be in needinfo state. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net ___ 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
Re: Bugzilla signal/noise ratio
On Fri, 2020-03-20 at 11:02 -0400, Paul Dufresne via devel wrote: > About outstanding bugs... > > In my opinion, the frequency at which it is sent: every day, is way too often. > For me, once a month would make more sense. > Maybe... maybe once a week. > > For me, the message contains this is a one bug: > https://bugzilla.redhat.com/show_bug.cgi?id=1700171 > > For most of the last year receiving this, I was using other distributions. > And was not ... somehow in the mood of responding. > > The message is clear: don't report bugs unless you expect to be able to > respond almost every day > to information requests. If you can't provide the information, post a comment saying that you're sorry, you can't provide it, and clear the flag. The point of the daily reminders is to annoy you into actually replying when someone else is waiting on you. If you find them so terribly annoying yet don't want to do this basic step (which, full disclosure: is me half the time, my record for leaving a bug in needinfo is about three and a half years :>), it takes about fifteen seconds (depending on your mail system) to make a filter that just trashes it every day. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net ___ 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
Re: Bugzilla signal/noise ratio
On 20/03/2020 13:30, Miro Hrončok wrote: > On 20. 03. 20 13:22, Daniel Pocock wrote: >> More than a year > > I my humble opinion, if you ignore outstanding Bugzillas for over a > year, you cannot be surprised you have hundreds of remainders in your > inbox. Please remember I've given this feedback to the Fedora community from my perspective as an upstream developer Most of my work involves implementing features and removing bugs in upstream multi-threaded C++, Java and Python projects. Some are free software projects, some are not. Then there is production support and release management. Making a .rpm or .deb package is important for me as well, as it allows more people to benefit from and collaborate on this work. But it is only a small percent of my time, after all the other work is done. When preparing to tag an upstream release, I try to graze over the issues in various bug trackers (Fedora, Debian, Ubuntu, Github, mailing lists) and identify those that require urgent attention in the current release cycle. In between upstream releases/tags, the extra reminder emails only drain my energy, they don't help me. I suspect there are a silent majority of contributors in most large projects who are not using the bug tracker every day and not releasing every month and so we are not familiar with the finer details of how it works or how Fedora uses every Bugzilla feature in practice. Some may actually drift away without realizing why or writing feedback like this. My own preference is to get feedback from multiple projects into a dashboard, I've previously blogged about it, with screenshots. This particular screenshot even includes an issue from Fedora Bugzilla, Bugzilla supports iCalendar natively: https://danielpocock.com/get-your-nagios-issues-as-an-icalendar-feed/ https://danielpocock.com/github-issues-as-an-icalendar-feed/ https://danielpocock.com/github-icalendar-issue-feed-now-scans-all-repositories/ https://danielpocock.com/debian-maintainer-dashboard-now-provides-icalendar-feeds/ https://danielpocock.com/aggregating-tasks-multiple-issue-trackers-gsoc-2015-summary/ In every DevOps environment I've worked in, management have made it a priority to kill reminder emails and have issues prioritized on a personalized dashboard for each team or person. Another side-effect of dashboards is that other community members can see just how much a particular developer has in their backlog. Instead of wondering why somebody doesn't update their package or reply to an email, you would be able to see at a glance where they spend their time and why. I'd personally prefer to see every type of reminder email disabled by default and people have to decide for themselves if they want emails, a dashboard or whatever. Regards, Daniel ___ 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
Re: Change in perl-devel dependencies
On Fri, Mar 20, 2020 at 02:46:05PM +, Sérgio Basto wrote: > On Tue, 2020-03-10 at 08:39 -0500, Chris Adams wrote: > > Once upon a time, Petr Pisar said: > > > The change is intentional. It is documented in the perl RPM > > > changelog, it was > > > announced on perl-devel list and it is in line with Perl packaging > > > guidelines and > > > Fedora minimization effort. > > > > This seems worthy of the change process, as well as announcement here > > (not just perl-devel). > > yes this a big wide change should be announced here and document how we > should processed [1] > > [1] > for modules require perl(THAT_MODULE). > Listing dependencies on modules is prescribed by the guidelines for ages. If this change revealed something, then that are packaging bugs in the affected packages. The only news is subpackaging perl-debugger and perl-doc. I can't remember more than 10 packages that were affected by this. But don't worry, there will be a formal Fedora change for Perl 5.32 that will mention this split. -- Petr 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
Fedora-32-20200320.n.0 compose check report
No missing expected images. Failed openQA tests: 4/171 (x86_64), 1/2 (arm) New failures (same test not failed in Fedora-32-20200319.n.0): ID: 551864 Test: x86_64 Everything-boot-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/551864 ID: 551913 Test: x86_64 Silverblue-dvd_ostree-iso desktop_terminal URL: https://openqa.fedoraproject.org/tests/551913 ID: 551932 Test: x86_64 universal install_repository_http_graphical URL: https://openqa.fedoraproject.org/tests/551932 Old failures (same test failed in Fedora-32-20200319.n.0): ID: 551895 Test: x86_64 KDE-live-iso desktop_background URL: https://openqa.fedoraproject.org/tests/551895 ID: 551901 Test: arm Minimal-raw_xz-raw.xz install_arm_image_deployment_upload URL: https://openqa.fedoraproject.org/tests/551901 Soft failed openQA tests: 19/171 (x86_64) (Tests completed, but using a workaround for a known bug) Old soft failures (same test soft failed in Fedora-32-20200319.n.0): ID: 551822 Test: x86_64 Server-boot-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/551822 ID: 551823 Test: x86_64 Server-boot-iso install_default URL: https://openqa.fedoraproject.org/tests/551823 ID: 551827 Test: x86_64 Server-dvd-iso install_default_upload URL: https://openqa.fedoraproject.org/tests/551827 ID: 551831 Test: x86_64 Server-dvd-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/551831 ID: 551834 Test: x86_64 Server-dvd-iso install_vncconnect_client URL: https://openqa.fedoraproject.org/tests/551834 ID: 551835 Test: x86_64 Server-dvd-iso install_vnc_client URL: https://openqa.fedoraproject.org/tests/551835 ID: 551857 Test: x86_64 Server-dvd-iso server_realmd_join_kickstart URL: https://openqa.fedoraproject.org/tests/551857 ID: 551880 Test: x86_64 Workstation-live-iso desktop_printing URL: https://openqa.fedoraproject.org/tests/551880 ID: 551882 Test: x86_64 Workstation-live-iso desktop_update_graphical URL: https://openqa.fedoraproject.org/tests/551882 ID: 551914 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/551914 ID: 551936 Test: x86_64 universal install_anaconda_text URL: https://openqa.fedoraproject.org/tests/551936 ID: 551946 Test: x86_64 universal upgrade_2_kde_64bit URL: https://openqa.fedoraproject.org/tests/551946 ID: 551955 Test: x86_64 universal upgrade_2_server_domain_controller URL: https://openqa.fedoraproject.org/tests/551955 ID: 551964 Test: x86_64 universal upgrade_server_64bit URL: https://openqa.fedoraproject.org/tests/551964 ID: 551980 Test: x86_64 universal upgrade_2_server_64bit URL: https://openqa.fedoraproject.org/tests/551980 ID: 551988 Test: x86_64 universal install_serial_console URL: https://openqa.fedoraproject.org/tests/551988 ID: 551989 Test: x86_64 universal upgrade_server_domain_controller URL: https://openqa.fedoraproject.org/tests/551989 ID: 551992 Test: x86_64 universal upgrade_2_realmd_client URL: https://openqa.fedoraproject.org/tests/551992 ID: 551994 Test: x86_64 universal upgrade_realmd_client URL: https://openqa.fedoraproject.org/tests/551994 Passed openQA tests: 148/171 (x86_64) Skipped non-gating openQA tests: 1 of 173 Installed system changes in test x86_64 Workstation-live-iso install_default@uefi: Used swap changed from 1 MiB to 5 MiB System load changed from 0.81 to 0.53 Average CPU usage changed from 17.35714286 to 4.7 Previous test data: https://openqa.fedoraproject.org/tests/551057#downloads Current test data: https://openqa.fedoraproject.org/tests/551867#downloads Installed system changes in test x86_64 Workstation-live-iso install_default_upload: System load changed from 1.18 to 0.84 Previous test data: https://openqa.fedoraproject.org/tests/551058#downloads Current test data: https://openqa.fedoraproject.org/tests/551868#downloads Installed system changes in test x86_64 KDE-live-iso install_default@uefi: System load changed from 1.83 to 1.39 Average CPU usage changed from 46.33809524 to 32.79523810 Previous test data: https://openqa.fedoraproject.org/tests/551074#downloads Current test data: https://openqa.fedoraproject.org/tests/551884#downloads Installed system changes in test x86_64 KDE-live-iso install_default_upload: System load changed from 1.88 to 1.16 Previous test data: https://openqa.fedoraproject.org/tests/551075#downloads Current test data: https://openqa.fedoraproject.org/tests/551885#downloads Installed system changes in test x86_64 Silverblue-dvd_ostree-iso install_default@uefi: Used swap changed from 5 MiB to 4 MiB Previous test data: https://openqa.fedoraproject.org/tests/551093#downloads Current test data: https://openqa.fedoraproject.org/tests/551903#downloads Installed system changes in test x86_64 Silverblue-dvd_ostree-iso install_default_upload: Used swap changed from 3 MiB to 5 MiB Previous test data:
OpenOSC package review request for Fedora
Hi Fedora developers, I have the below OpenOSC package review request for Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=1812961 I wonder if somebody can help me with the package review to get it into Fedora. Also if somebody can sponsor me, it would be greatly appreciated! Thanks, Yongkui ___ 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
Fedora-IoT-33-20200320.0 compose check report
Missing expected images: Iot dvd x86_64 Iot dvd aarch64 Passed openQA tests: 8/8 (x86_64) New passes (same test not passed in Fedora-IoT-33-20200319.0): ID: 551997 Test: x86_64 IoT-dvd_ostree-iso release_identification URL: https://openqa.fedoraproject.org/tests/551997 Installed system changes in test x86_64 IoT-dvd_ostree-iso install_default@uefi: Used mem changed from 145 MiB to 169 MiB System load changed from 0.07 to 0.20 Peak task count changed from 100 to 120 Previous test data: https://openqa.fedoraproject.org/tests/551185#downloads Current test data: https://openqa.fedoraproject.org/tests/551995#downloads Installed system changes in test x86_64 IoT-dvd_ostree-iso install_default_upload: Used mem changed from 144 MiB to 168 MiB System load changed from 0.07 to 0.18 Peak task count changed from 101 to 119 Previous test data: https://openqa.fedoraproject.org/tests/551186#downloads Current test data: https://openqa.fedoraproject.org/tests/551996#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
Re: Bugzilla signal/noise ratio
On Fri, Mar 20, 2020 at 3:20 PM Rob Crittenden wrote: > Closing a bug doesn't clear the needinfo. I consider that a mis-feature, but I have learned to live with it. > As a package owner I like the daily reminder. If it only happened > monthly then bad timing could make it so I miss a reminder for 29+ days. I know it is out of scope, and I don't get a vote in any case, but I would prefer that I get a couple of daily reminders (in the case I missed the first email), then move to something more like a weekly (or even bi-weekly) schedule of emails as asking "Are we there yet?" every day just feels excessive. ___ 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
Re: Bugzilla signal/noise ratio
> Closing a bug doesn't clear the needinfo. Change the ? to blank under > flags (or I'm happy to clear it for you if you'd like). Ok, I have done it. But I believe the outstanding bugs reminder should not include closed bugs! ___ 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
[389-devel] Re: Adding new syntaxes
Hi William, I only have a vague knowledge of syntaxes/MR. Each syntax is a plugin. Its init function registers for a given set of OIDs the matching rules (compare, order, substring) than handle that syntax (calls slapi_matchingrule_register). There is a special collation plugin that does the same for supported language. So a entryUUID syntax should define its matching rules callbacks and register them for supported OID. The MR are called during filter evaluation, both at candidate list built and at filter match. On write path, they are called to generate the index keys. I think there is a slight difference between syntaxes plugins and collation plugin in the way they are selected to apply for a given attribute. syntaxes provide the set of supported OIDs while for collation you need to call the index to know if it supports the OID. All of this are general ideas around syntax/MR and I think they are quite correct. best regards thierry On 3/20/20 4:37 AM, William Brown wrote: Hi there, I'm looking to add the syntaxes to handle entryUUID properly, because they have a different format to nsUniqueId. Thinking that I need to look at the plugins under ldap/servers/plugins/syntaxes/, but it would be good to have some extra insight about the plugin hooks. Should I look at the old plugin guide? Or is there some extra info I can get from somewhere? Thanks! — Sincerely, William Brown Senior Software Engineer, 389 Directory Server SUSE Labs ___ 389-devel mailing list -- 389-devel@lists.fedoraproject.org To unsubscribe send an email to 389-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/389-devel@lists.fedoraproject.org ___ 389-devel mailing list -- 389-devel@lists.fedoraproject.org To unsubscribe send an email to 389-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/389-devel@lists.fedoraproject.org
Fedora-Rawhide-20200320.n.0 compose check report
No missing expected images. Compose PASSES proposed Rawhide gating check! All required tests passed Failed openQA tests: 11/171 (x86_64), 1/2 (arm) New failures (same test not failed in Fedora-Rawhide-20200319.n.0): ID: 551659 Test: x86_64 Server-dvd-iso mediakit_fileconflicts URL: https://openqa.fedoraproject.org/tests/551659 ID: 551758 Test: x86_64 universal install_european_language URL: https://openqa.fedoraproject.org/tests/551758 ID: 551778 Test: x86_64 universal upgrade_2_server_domain_controller URL: https://openqa.fedoraproject.org/tests/551778 ID: 551795 Test: x86_64 universal support_server URL: https://openqa.fedoraproject.org/tests/551795 ID: 551815 Test: x86_64 universal upgrade_2_realmd_client URL: https://openqa.fedoraproject.org/tests/551815 ID: 551816 Test: x86_64 universal install_iscsi URL: https://openqa.fedoraproject.org/tests/551816 Old failures (same test failed in Fedora-Rawhide-20200319.n.0): ID: 551673 Test: x86_64 Server-dvd-iso server_freeipa_replication_master URL: https://openqa.fedoraproject.org/tests/551673 ID: 551675 Test: x86_64 Server-dvd-iso modularity_tests URL: https://openqa.fedoraproject.org/tests/551675 ID: 551681 Test: x86_64 Server-dvd-iso server_freeipa_replication_replica URL: https://openqa.fedoraproject.org/tests/551681 ID: 551684 Test: x86_64 Server-dvd-iso server_freeipa_replication_client URL: https://openqa.fedoraproject.org/tests/551684 ID: 551724 Test: arm Minimal-raw_xz-raw.xz install_arm_image_deployment_upload URL: https://openqa.fedoraproject.org/tests/551724 ID: 551735 Test: x86_64 Silverblue-dvd_ostree-iso release_identification URL: https://openqa.fedoraproject.org/tests/551735 Soft failed openQA tests: 18/171 (x86_64) (Tests completed, but using a workaround for a known bug) New soft failures (same test not soft failed in Fedora-Rawhide-20200319.n.0): ID: 551680 Test: x86_64 Server-dvd-iso server_realmd_join_kickstart URL: https://openqa.fedoraproject.org/tests/551680 ID: 551683 Test: x86_64 Server-dvd-iso realmd_join_sssd URL: https://openqa.fedoraproject.org/tests/551683 Old soft failures (same test soft failed in Fedora-Rawhide-20200319.n.0): ID: 551645 Test: x86_64 Server-boot-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/551645 ID: 551646 Test: x86_64 Server-boot-iso install_default URL: https://openqa.fedoraproject.org/tests/551646 ID: 551650 Test: x86_64 Server-dvd-iso install_default_upload URL: https://openqa.fedoraproject.org/tests/551650 ID: 551654 Test: x86_64 Server-dvd-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/551654 ID: 551657 Test: x86_64 Server-dvd-iso install_vncconnect_client URL: https://openqa.fedoraproject.org/tests/551657 ID: 551658 Test: x86_64 Server-dvd-iso install_vnc_client URL: https://openqa.fedoraproject.org/tests/551658 ID: 551703 Test: x86_64 Workstation-live-iso desktop_printing URL: https://openqa.fedoraproject.org/tests/551703 ID: 551705 Test: x86_64 Workstation-live-iso desktop_update_graphical URL: https://openqa.fedoraproject.org/tests/551705 ID: 551737 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/551737 ID: 551759 Test: x86_64 universal install_anaconda_text URL: https://openqa.fedoraproject.org/tests/551759 ID: 551769 Test: x86_64 universal upgrade_2_kde_64bit URL: https://openqa.fedoraproject.org/tests/551769 ID: 551787 Test: x86_64 universal upgrade_server_64bit URL: https://openqa.fedoraproject.org/tests/551787 ID: 551803 Test: x86_64 universal upgrade_2_server_64bit URL: https://openqa.fedoraproject.org/tests/551803 ID: 551811 Test: x86_64 universal install_serial_console URL: https://openqa.fedoraproject.org/tests/551811 ID: 551812 Test: x86_64 universal upgrade_server_domain_controller URL: https://openqa.fedoraproject.org/tests/551812 ID: 551817 Test: x86_64 universal upgrade_realmd_client URL: https://openqa.fedoraproject.org/tests/551817 Passed openQA tests: 142/171 (x86_64) New passes (same test not passed in Fedora-Rawhide-20200319.n.0): ID: 551678 Test: x86_64 Server-dvd-iso server_role_deploy_domain_controller URL: https://openqa.fedoraproject.org/tests/551678 ID: 551682 Test: x86_64 Server-dvd-iso realmd_join_cockpit URL: https://openqa.fedoraproject.org/tests/551682 ID: 551721 Test: x86_64 KDE-live-iso desktop_printing URL: https://openqa.fedoraproject.org/tests/551721 ID: 551723 Test: x86_64 KDE-live-iso desktop_update_graphical URL: https://openqa.fedoraproject.org/tests/551723 ID: 551754 Test: x86_64 universal install_blivet_btrfs@uefi URL: https://openqa.fedoraproject.org/tests/551754 ID: 551775 Test: x86_64 universal install_blivet_lvmthin URL: https://openqa.fedoraproject.org/tests/551775 Skipped non-gating openQA tests: 1 of 173 Installed system changes in test x86_64 Server-boot-iso
Re: Bugzilla signal/noise ratio
Paul Dufresne via devel wrote: > About outstanding bugs... > > In my opinion, the frequency at which it is sent: every day, is way too often. > For me, once a month would make more sense. > Maybe... maybe once a week. > > For me, the message contains this is a one bug: > https://bugzilla.redhat.com/show_bug.cgi?id=1700171 > > For most of the last year receiving this, I was using other distributions. > And was not ... somehow in the mood of responding. > > The message is clear: don't report bugs unless you expect to be able to > respond almost every day > to information requests. Which means if you discover bugs while testing, > distro-hoping, do not report bugs about it. > Unless you are ready to delete daily, you already know, unpleasant automatic > reminders. > > That said, in this particular case, the bugzilla server seems broken (giving > internal errors when > trying to attach requested files)... and I don't seems able to close the bug > to stop receiving the annoying *daily* messages. Closing a bug doesn't clear the needinfo. Change the ? to blank under flags (or I'm happy to clear it for you if you'd like). As a package owner I like the daily reminder. If it only happened monthly then bad timing could make it so I miss a reminder for 29+ days. rob ___ 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
Re: Bugzilla signal/noise ratio
On 20. 03. 20 16:02, Paul Dufresne via devel wrote: About outstanding bugs... In my opinion, the frequency at which it is sent: every day, is way too often. For me, once a month would make more sense. Maybe... maybe once a week. Once a day is indeed too much. It used to be once a week. For me, the message contains this is a one bug: https://bugzilla.redhat.com/show_bug.cgi?id=1700171 For most of the last year receiving this, I was using other distributions. And was not ... somehow in the mood of responding. The message is clear: don't report bugs unless you expect to be able to respond almost every day to information requests. Which means if you discover bugs while testing, distro-hoping, do not report bugs about it. Unless you are ready to delete daily, you already know, unpleasant automatic reminders. That said, in this particular case, the bugzilla server seems broken (giving internal errors when trying to attach requested files)... and I don't seems able to close the bug to stop receiving the annoying *daily* messages. Thick the "I am providing the requested information for this bug (Will clear all needinfo requests)" checkbox and click "Save Changes". -- 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
[389-devel] please review: PR 50968 - UI - database indexes were not using typeAhead correctly
https://pagure.io/389-ds-base/pull-request/50968 -- 389 Directory Server Development Team ___ 389-devel mailing list -- 389-devel@lists.fedoraproject.org To unsubscribe send an email to 389-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/389-devel@lists.fedoraproject.org
Re: Bugzilla signal/noise ratio
About outstanding bugs... In my opinion, the frequency at which it is sent: every day, is way too often. For me, once a month would make more sense. Maybe... maybe once a week. For me, the message contains this is a one bug: https://bugzilla.redhat.com/show_bug.cgi?id=1700171 For most of the last year receiving this, I was using other distributions. And was not ... somehow in the mood of responding. The message is clear: don't report bugs unless you expect to be able to respond almost every day to information requests. Which means if you discover bugs while testing, distro-hoping, do not report bugs about it. Unless you are ready to delete daily, you already know, unpleasant automatic reminders. That said, in this particular case, the bugzilla server seems broken (giving internal errors when trying to attach requested files)... and I don't seems able to close the bug to stop receiving the annoying *daily* messages. ___ 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
Re: Change in perl-devel dependencies
On Tue, 2020-03-10 at 08:39 -0500, Chris Adams wrote: > Once upon a time, Petr Pisar said: > > The change is intentional. It is documented in the perl RPM > > changelog, it was > > announced on perl-devel list and it is in line with Perl packaging > > guidelines and > > Fedora minimization effort. > > This seems worthy of the change process, as well as announcement here > (not just perl-devel). yes this a big wide change should be announced here and document how we should processed [1] [1] for modules require perl(THAT_MODULE). > -- > Chris Adams > ___ > 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 -- Sérgio M. B. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Fedora rawhide compose report: 20200320.n.0 changes
OLD: Fedora-Rawhide-20200319.n.0 NEW: Fedora-Rawhide-20200320.n.0 = SUMMARY = Added images:0 Dropped images: 0 Added packages: 12 Dropped packages:0 Upgraded packages: 153 Downgraded packages: 0 Size of added packages: 33.20 MiB Size of dropped packages:0 B Size of upgraded packages: 5.13 GiB Size of downgraded packages: 0 B Size change of upgraded packages: 30.32 MiB Size change of downgraded packages: 0 B = ADDED IMAGES = = DROPPED IMAGES = = ADDED PACKAGES = Package: libpasraw-1.3.0-4.fc33 Summary: Pascal interface to libraw RPMs:libpasraw libpasraw-devel Size:190.40 KiB Package: nodejs-packaging-23-2.module_f33+8339+9b1e423a Summary: RPM Macros and Utilities for Node.js Packaging RPMs:nodejs-packaging Size:19.84 KiB Package: ocaml-ppx-deriving-4.4.1-1.fc33 Summary: Type-driven code generation for OCaml RPMs:ocaml-ppx-deriving ocaml-ppx-deriving-devel ocaml-ppx-deriving-doc Size:27.60 MiB Package: python-APScheduler-3.6.3-1.fc33 Summary: In-process task scheduler with Cron-like capabilities RPMs:python3-APScheduler Size:101.23 KiB Package: python-diskcache-4.1.0-2.fc33 Summary: Disk and file backed persistent cache RPMs:python3-diskcache Size:74.94 KiB Package: python-eccodes-0.9.7-1.fc33 Summary: Python interface to the ecCodes GRIB and BUFR decoder/encoder RPMs:python3-eccodes Size:701.59 KiB Package: python-fb-re2-1.0.7-1.fc33 Summary: Python wrapper for Google's RE2 library RPMs:python3-fb-re2 Size:111.84 KiB Package: python-gilt-1.2.1-2.fc33 Summary: Gilt is a git layering tool RPMs:python-gilt-doc python3-gilt Size:227.58 KiB Package: python-qdarkstyle-2.8-1.fc33 Summary: A dark stylesheet for Python and Qt applications RPMs:python3-qdarkstyle Size:309.03 KiB Package: python-sphinxcontrib-openapi-0.6.0-1.fc33 Summary: OpenAPI spec renderer for Sphinx RPMs:python3-sphinxcontrib-openapi Size:31.37 KiB Package: python-ws4py-0.5.1-2.fc33 Summary: WebSocket client and server library RPMs:python3-ws4py Size:74.22 KiB Package: ytop-0.5.1-1.fc33 Summary: TUI system monitor written in Rust RPMs:ytop Size:3.81 MiB = DROPPED PACKAGES = = UPGRADED PACKAGES = Package: PyX-0.15-1.fc33 Old package: PyX-0.14.1-15.fc32 Summary: Python graphics package RPMs: PyX PyX-doc Size: 5.43 MiB Size change: 808.62 KiB Changelog: * Thu Mar 19 2020 Jos?? Matos - 0.15-1 - Update to 0.15 - Turn on the pdf generation - Add several patches from Debian Package: PyYAML-5.3.1-1.fc33 Old package: PyYAML-5.3-4.fc33 Summary: YAML parser and emitter for Python RPMs: python3-pyyaml Size: 972.83 KiB Size change: 4.35 KiB Changelog: * Thu Mar 19 2020 John Eckersberg - 5.3.1-1 - New upstream release 5.3.1 (rhbz#1814882) - Fixes CVE-2020-1747 (rhbz#1807367,1809011) Package: R-multcomp-1.4.12-1.fc33 Old package: R-multcomp-1.4.10-5.fc32 Summary: Simultaneous inference for general linear hypotheses R Package RPMs: R-multcomp Size: 713.54 KiB Size change: 4.99 KiB Changelog: * Thu Mar 19 2020 Jos?? Matos - 1.4.12-1 - update to 1.4-12 Package: R-rlecuyer-0.3.5-2.fc33 Old package: R-rlecuyer-0.3.5-2.fc32 Summary: R interface to RNG with multiple streams RPMs: R-rlecuyer Size: 393.46 KiB Size change: -2.07 KiB Package: R-systemfit-1.1.24-1.fc33 Old package: R-systemfit-1.1.22-7.fc32 Summary: Simultaneous Equation Estimation R Package RPMs: R-systemfit Size: 812.37 KiB Size change: 1.27 KiB Changelog: * Thu Mar 19 2020 Jos?? Matos - 1.1.24-1 - Update to 1.1-24 Package: appstream-0.12.10-1.fc33 Old package: appstream-0.12.9-2.fc32 Summary: Utilities to generate, maintain and access the AppStream database RPMs: appstream appstream-devel appstream-qt appstream-qt-devel Size: 12.94 MiB Size change: 151.26 KiB Changelog: * Thu Mar 19 2020 Rex Dieter - 0.12.10-1 - 0.12.10 Package: appstream-generator-0.8.1-1.fc33 Old package: appstream-generator-0.7.7-2.fc31 Summary: Fast AppStream metadata generator RPMs: appstream-generator Size: 2.05 MiB Size change: 588.24 KiB Changelog: * Tue Jan 28 2020 Fedora Release Engineering - 0.7.7-3 - Rebuilt for https://fedoraproject.org/wiki/Fedora_32_Mass_Rebuild * Thu Mar 19 2020 Neal Gompa - 0.8.1-1 - Rebase to 0.8.1 (#1755095) - Vendor JavaScript components and declare as bundled Package: autodocksuite-4.2.6-12.fc33 Old package: autodocksuite-4.2.6-12.fc32 Summary: AutoDock is a suite of docking tools to study protein-ligand interaction RPMs: autodocksuite Size: 1.09 MiB Size change: -889 B Package: awscli-1.18.24-1.fc33 Old package: awscli-1.18.23-1.fc33 Summary: Universal Command Line Environment for AWS RPMs: awscli Size
Re: CoC
This thread is off-topic and not in the spirit of our Friends foundation. Please refrain from further replies. -- Ben Cotton He / Him / His Senior Program Manager, Fedora & CentOS Stream Red Hat TZ=America/Indiana/Indianapolis ___ 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
Fedora-IoT-32-20200320.0 compose check report
No missing expected images. Soft failed openQA tests: 2/8 (x86_64) (Tests completed, but using a workaround for a known bug) Old soft failures (same test soft failed in Fedora-IoT-32-20200319.0): ID: 551584 Test: x86_64 IoT-dvd_ostree-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/551584 ID: 551585 Test: x86_64 IoT-dvd_ostree-iso install_default_upload URL: https://openqa.fedoraproject.org/tests/551585 Passed openQA tests: 6/8 (x86_64) -- 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
Re: Bugzilla signal/noise ratio
On 20. 03. 20 13:22, Daniel Pocock wrote: More than a year I my humble opinion, if you ignore outstanding Bugzillas for over a year, you cannot be surprised you have hundreds of remainders in your inbox. -- 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
Re: Bugzilla signal/noise ratio
On 20/03/2020 13:19, Emmanuel Seyman wrote: > > Hi, Daniel. > > * Daniel Pocock [20/03/2020 12:38] : >> >> - there were over 100 "outstanding requests" emails in my inbox > > Over how many bugs and what time period were the requests generated? More than a year >> - there are numerous bugs about builds failing, FTBFS > > These bugs are signal and not noise. > Not only are they signal but I consider them to be relatively important. I agree the bug itself is important The problem is the existence of multiple emails, including boilerplate comment emails and outstanding requests emails, all referencing the same bug The bug alone is enough ___ 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
Re: Bugzilla signal/noise ratio
Hi, Daniel. * Daniel Pocock [20/03/2020 12:38] : > > - there were over 100 "outstanding requests" emails in my inbox Over how many bugs and what time period were the requests generated? > - there are numerous bugs about builds failing, FTBFS These bugs are signal and not noise. Not only are they signal but I consider them to be relatively important. Emmanuel ___ 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
Re: CoC
On 20/03/2020 12:50, Martin Langhoff wrote: > Apologies to Ty. I should have written instead: > > Daniel Pocock seems to have created a complicated situation with Debian, > which includes sock puppets and attempts at impersonation. > > Here is a good LWN article that tries to cover the topic > - https://lwn.net/Articles/814508/ . It is not the only one -- there's > endless mailing list threads and blogposts. > To save everybody time reading endless threads, could you provide a link to even one single resource that contains credible /proof/ for your claim of sock puppeteering/impersonation? If not, you are spreading a smear, making yourself part of that campaign of harassment Regards, Daniel ___ 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
Re: CoC
Apologies to Ty. I should have written instead: Daniel Pocock seems to have created a complicated situation with Debian, which includes sock puppets and attempts at impersonation. Here is a good LWN article that tries to cover the topic - https://lwn.net/Articles/814508/ . It is not the only one -- there's endless mailing list threads and blogposts. take care, martin On Thu, Mar 19, 2020 at 11:29 PM Ty Young wrote: > > On 3/19/20 10:03 PM, Martin Langhoff wrote: > > Oh my - Daniel and his sock puppets come to bring mayhem to Fedora-devel? > > some background at https://lwn.net/Articles/814508/ > > cut off the trolling... > > > I do believe calling people "sock puppets" is a violation of the CoC. > Specifically, the "be respectful" section at the top. > > > Anyway, not the same person. I'd jump off a cliff before having anything > to do with or use Debian. Anyone who knows me from Reddit could probably > tell you that. > > > > > m > > On Thu, Mar 19, 2020 at 3:37 PM Ty Young wrote: > >> >> On 3/19/20 2:18 PM, Daniel Pocock wrote: >> > >> > On 12/03/2020 22:34, Matthew Miller wrote: >> >> On Sat, Mar 07, 2020 at 11:33:04PM +0100, Daniel Pocock wrote: >> >>> It is very, very wrong and I don't feel I should have to make a public >> >>> request like this. Nonetheless, there is a certain type of person who >> >> Daniel, to request re-instatement, please follow the process outlined >> >> in the original code-of-conduct suspension notice you received. A >> >> public post is not necessary. >> > >> > Personally, I feel offended by your choice of words >> > >> > A suspension of a blog may itself be a violation of the Code of Conduct >> > if the blog was written in good faith >> > >> > I never received one complaint about my blog from anybody in the Fedora >> > world. Several people noticed when it disappeared though. >> > >> > The blog post in question discussed a conflict of interest between the >> > leaders of two free software organizations, the Debian Project Leader >> > and the OSI board president. As I interacted with both of them >> > personally, I felt that I was qualified to share my observations. >> > >> > That topic itself was forced into the public because one of the people >> > party to the conflict of interest had spread gossip about me and the >> > other used her speech at an event for humiliating volunteers. >> > >> > It feels like Codes of Conduct apply to some people and not others. As >> > George Orwell puts it, /All animals are equal but some animals are more >> > equal than others/. >> >> >> Have you seen Gnome's CoC? It literally allows racism. There was a bit >> of an uproar about it, and Gnome foundation/developers members refused >> to change it. >> >> >> (Gnome and Fedora are very incestous projects, so yes, it is relevant) >> >> >> Now that communism is the cool, hip ideology in town, Gnome/Fedora are >> embracing it. Book burning is the next step, but one might argue the >> deletion of discussion threads and blogs already *is* that step. >> >> >> > >> > Fedora's Code of Conduct[1] asks people to be excellent to each other. >> > When talking about governance issues, being excellent to other >> > volunteers means telling them the truth about leadership problems in the >> > free software world. >> > >> > Being excellent to leaders who behave badly means keeping a focus on the >> > issues. For example, when blogging about two people with a romantic >> > conflict of interest, I would never speculate about their first date and >> > other personal details, I would only focus on the way their decision >> > making was impaired. >> > >> > Even this week there are people writing public comments alleging I had a >> > conflict of interest, but that is false. I named Chris Lamb and Molly >> > de Blanc because their conflict of interest was at the root of certain >> > problems. At least one member of Debian's mentoring team also had a >> > conflict of interest with an intern. I didn't identify them out of >> > concerns for student privacy. Nonetheless, when people spread gossip, >> > leadership figures have a responsibility to stop it, but they didn't, >> > they added fuel to the fire and they continue to do so even now. >> > >> > If the leaders of organizations can behave like that, why should the >> > Code of Conduct deny a volunteer a right of reply? >> >> >> Silly Daniel, you aren't supposed to question the supreme leaders. You >> have to fall in line and never question anything. >> >> >> If you need help understanding, I recommend reading up on what's going >> on in China right now. Concentration camps, book burning, police >> brutality, people vanishing, etc... >> >> >> > >> > Regards, >> > >> > Daniel >> > >> > 1. https://docs.fedoraproject.org/en-US/project/code-of-conduct/ >> > ___ >> > devel mailing list -- devel@lists.fedoraproject.org >> > To unsubscribe send an email to devel-le...@lists.fedoraproject.org >> > Fedora Code of
[EPEL-devel] Help with cfitsio update in epel6, proven packager needed
Hello. I would like to update cfitsio in epel6. The current version here has longstanding bugs. My first question is the correct repoquery command. I'm doing, in a centos 6 machine, repoquery --whatrequires cfitsio --disablerepo=* --enablerepo=epel -s|sort | uniq that returns cfitsio-3.240-3.el6.src.rpm cpl-5.2.0-2.el6.src.rpm gdal-1.7.3-15.el6.src.rpm healpix-2.13a-2.el6.src.rpm munipack-1.2.10-1.el6.src.rpm nightview-0.3.3-1.el6.src.rpm perl-Astro-FITS-CFITSIO-1.05-6.el6.src.rpm root-5.34.38-3.el6.src.rpm siril-0.8-9.el6.src.rpm skyviewer-1.0.0-3.el6.src.rpm wcslib-4.3.1-3.el6.src.rpm Second, I understand that I have to create a buildroot override and the owners rebuild their packages. Later, to create a common update in bodhi. I can't create the update because I'm do not have the required permissions. Could a proven packager coordinate this? Thank you ___ 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
Bugzilla signal/noise ratio
I've been looking at email from Bugzilla to try and find out what I need to know preparing the upstream release of reSIProcate I feel the signal/noise ratio is disturbing and it also means I am less likely to open Bugzilla emails In particular, - there were over 100 "outstanding requests" emails in my inbox - there are numerous bugs about builds failing, FTBFS - those bugs have numerous comments with reminders, adding no new information for a developer Overall, from over 300 emails, I could find only the following issues: - need to resolve ambiguity about whether one of the optional scripts needs Python2 or Python3 - need to update dependency to use mariadb-connector-c-devel - cajun-jsonapi (dependency) add build requires gcc-c++ and fixed upstream: - need to build with OpenSSL 1.1 - two buffer issues I feel that the volume of automated emails/comments and the effort to try and find distinct issues in there is disproportionate to the effort in actually fixing the issues that are found. In some cases, like updating build-requires for cajun-jsonapi, it would have been easier for somebody else to make the change than to open the bug report (in fact, somebody did add it, thank you) Not only that, but the nag-factor means that I haven't noticed worthwhile comments people have put into Bugzilla from time to time, in fact, it is tedious to go and find the personal comments from people when they are drowning in a sea of automated emails. Regards, Daniel ___ 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
Re: Announcing bugzilla overrides coming to dist-git (stg)
On Tue, Mar 17, 2020 at 02:26:18PM +0100, Miro Hrončok wrote: > On 17. 03. 20 14:14, Pierre-Yves Chibon wrote: > > On Tue, Mar 17, 2020 at 01:23:59PM +0100, Miro Hrončok wrote: > > > On 17. 03. 20 11:58, Pierre-Yves Chibon wrote: > > > > Together with Karsten Hopp we worked on integrating this functionality > > > > on > > > > pagure-dist-git[3], thus allowing to get rid entirely of the git > > > > repository at > > > > fedora-scm-request[2]. > > > > > > Thank You both \o/ > > > > > > > This work has been deployed in staging today. We would very much > > > > appreciate if > > > > you could take a few minute of your time and see if it works to your > > > > liking: https://src.stg.fedoraproject.org/ > > > > > > 1. Can you make the usernames clickable please? > > > > That should be doable, to http://src.stg.fedoraproject.org/user/ I > > guess? > > I guess so. Plus extra care for groups. > > > > 2. I don't understand how to update the information, I can only understand > > > how to read it. > > > > If you are logged in and on a package where you have admin rights, there > > should > > be an "update" button underneath, clicking it makes a pop-up (a modal) > > appear, > > in which you can update the settings. > > It appears you need to be main admin to do this. Is that intended? > > The fields seem to have no validation: > > https://src.stg.fedoraproject.org/rpms/python-pip This has been addressed and the new code deployed in staging. If there are no other issues found/reported, I would like to look at pushing this to production next week. Thanks for your feedback! Pierre ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Fedora-Cloud-31-20200320.0 compose check report
No missing expected images. Passed openQA tests: 1/1 (x86_64) -- 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
Re: putting my blog back on Planet Fedora
On 20/03/2020 09:16, Zbigniew Jędrzejewski-Szmek wrote: > On Thu, Mar 12, 2020 at 05:34:58PM -0400, Matthew Miller wrote: >> On Sat, Mar 07, 2020 at 11:33:04PM +0100, Daniel Pocock wrote: >>> It is very, very wrong and I don't feel I should have to make a public >>> request like this. Nonetheless, there is a certain type of person who >> >> Daniel, to request re-instatement, please follow the process outlined >> in the original code-of-conduct suspension notice you received. A >> public post is not necessary. > > Hi Matthew, > > please make the original reason for suspension public. > > At this point, the whole discussion is going in an unhealthy direction. > Accusations are being thrown around, and having almost no response from > Fedora representatives is leaving an unwanted void where they are very > visible. I think the public should judge the issue for itself, but can't > without data. > Here is the message I received from Brian Exelbierd: "Recently you have been sending a series of blog entries to the Fedora Planet site about your situation with the Debian community. We were made aware of these posts and are dismayed to see you include personal attacks and innuendo in your blog entries." The most recent blog was about a) the conflict of interest between the Debian Project Leader and the OSI board president b) the deliberate humiliation of volunteers by those two people c) the fact that this was ongoing at the time my father died and that I felt it amounted to bullying It seems that some people view conflicts of interest as nothing more than "innuendo" unless the couple are legally married. For me, any romantic attachment between two office holders is a conflict of interest, whether they are married or not. Discussing their ethical (mis)behavior is not a "personal attack". They may be entitled to keep their relationship a secret if they informed other people and recused themselves from decisions concerning each other. As a member of Debian's GSoC admin team, I was never informed that another member of our team was in a romantic relationship with Debian's leader. We had a number of interactions with Debian's leader where that relationship was relevant but hidden from the team. The issue in Pagure has the subject "From Debian" and Exelbierd's message also mentions "We were made aware of these posts". So it looks like this is part of the campaign of harassment from somebody in Debian who is stalking me and trying to undermine my participation in Fedora and other communities. The attack in LWN also looks like it has been created by some incredibly venomous people who have been stalking me ever since the FSFE Fellowship elected me as a community representative. I sent a GDPR request to Fedora and Red Hat and they failed to provide me with a copy of the communication that came "From Debian". This makes it harder to identify who does the stalking. Regards, Daniel ___ 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
[Fedora-r-devel-list] no copy and paste
Fedora version : [root@ACERORESCRITORIO ~]# uname -a Linux ACERORESCRITORIO 5.5.9-200.fc31.x86_64 #1 SMP Thu Mar 12 13:55:19 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux [root@ACERORESCRITORIO ~]# Rstudio Version:Version 1.2.5033 © 2009-2020 RStudio, Inc. "Orange Blossom" (330255dd, 2020-02-28) Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) QtWebEngine/5.13.2 Chrome/73.0.3683.105 Safari/537.36 Good Morning :these are my versions (fedora and Rstudio), but i can not make " copy and paste " from firefox to Rstudio, neither from .pdf file to Rstudio, neither from libre office to Rstudio.its like " copy and paste " is working ok between all the programs under linux but all the programs under linux no connection whith Rstudiowhy even when i start R from terminal " copy and paste " is working ok between all the programs under linux and R consoleits like the problem only happend whith Rstudio,,..thanks orlandomontr...@yahoo.com ___ r-devel mailing list -- r-devel@lists.fedoraproject.org To unsubscribe send an email to r-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/r-devel@lists.fedoraproject.org
Fedora-Cloud-30-20200320.0 compose check report
No missing expected images. Passed openQA tests: 1/1 (x86_64) -- 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
Re: putting my blog back on Planet Fedora
On Thu, Mar 12, 2020 at 05:34:58PM -0400, Matthew Miller wrote: > On Sat, Mar 07, 2020 at 11:33:04PM +0100, Daniel Pocock wrote: > > It is very, very wrong and I don't feel I should have to make a public > > request like this. Nonetheless, there is a certain type of person who > > Daniel, to request re-instatement, please follow the process outlined > in the original code-of-conduct suspension notice you received. A > public post is not necessary. Hi Matthew, please make the original reason for suspension public. At this point, the whole discussion is going in an unhealthy direction. Accusations are being thrown around, and having almost no response from Fedora representatives is leaving an unwanted void where they are very visible. I think the public should judge the issue for itself, but can't without data. 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
Re: RFC: entering luks password on grub level for devices without keyboards
On Thu, Mar 19, 2020 at 06:52:52PM +0100, Marius Schwarz wrote: > Am 19.03.20 um 17:11 schrieb Michael Cronenworth: > > On 3/19/20 11:04 AM, Marius Schwarz wrote: > >> correct and thats the main issue, as long you have grub where you can > >> edit the kernel line to start in runlevel 1. > >> This makes the encryption null and void. > > > > Adding a grub password will prevent those without it from editing your > > boot parameters. By default you can still boot without the grub > > password. Does that help? > > It would solve a problem. > > - does it prevent updates ( after booting into rl 5 ) of grub? Yes. Updating GRUB, kernel, and initramdisk requires a physical access (or better said a trusted environment). -- Petr 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
Re: RFC: entering luks password on grub level for devices without keyboards
On Thu, Mar 19, 2020 at 12:59:01PM -0600, Chris Murphy wrote: > On Thu, Mar 19, 2020 at 11:53 AM Marius Schwarz > wrote: > > > > Am 19.03.20 um 17:11 schrieb Michael Cronenworth: > > > On 3/19/20 11:04 AM, Marius Schwarz wrote: > > >> correct and thats the main issue, as long you have grub where you can > > >> edit the kernel line to start in runlevel 1. > > >> This makes the encryption null and void. > > > > > > Adding a grub password will prevent those without it from editing your > > > boot parameters. By default you can still boot without the grub > > > password. Does that help? > > > > It would solve a problem. > > > > - does it prevent updates ( after booting into rl 5 ) of grub? > > - where is the passcode stored? > > grub.cfg or user.cfg contains the hashed password > > https://wiki.archlinux.org/index.php/GRUB/Tips_and_tricks#Password_protection_of_GRUB_menu > https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/system_administrators_guide/sec-protecting_grub_2_with_a_password > > But if the attacker has physical access to the computer, they can > mount /boot/efi or /boot where this file is stored; and remove the > password requirement. Not at all. GRUB code and configuration are protected by TPM measurement. If an attacker tampers them, decrypting LUKS will fail on a missing or wrong passphrase. -- Petr 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
Re: CoC
On 20/03/2020 04:33, John M. Harris Jr wrote: > > Hi Martin, > > Please see the Fedora Code of Conduct[1]. Referring to other members of the > community as "sock puppets" falls a bit shy of "be excellent to each other", > in my opinion. > > 1: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > Martin's link is to an article that has been cut-and-pasted from trolls and cyberbullies. A genuine journalist contacts people on all sides of the story before printing something. That basic principle is found in /Ethics for journalists 101/. LWN didn't contact me at any time. Moreover, it is an even more serious violation of a journalist's ethical code to put unreasonable attention on a private individual at a time of grief. Yet LWN insists on doing abusive stuff like that too. The last couple of years have been absolute hell for my family and I. The insistence of certain people in Debian, FSFE and now LWN to insinuate there was some question about my competence or integrity only shows how out of step they are with society at large. If you want to talk about sock puppets, you might just find they are your neighbours[1] and not sock puppets at all. Regards, Daniel 1. https://fsfellowship.eu/st-patricks-day-2019-ifso-and-finding-sock-puppets/ ___ 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
