Where did my keys go in Thunderbird?
Hi Thunderbird users, I'm not sure if you noticed, but Thunderbird got a major update for F31+, which removes XUL extensions - f.e. Enigmail is not working anymore. However, if you are using keys to your emails, don't panic and start digging into metadata to somehow recover your keys. If you go to Tools->Migrate Enigmail settings, then you are able to recover all stuff. Hope the info will save a time for someone since I wasn't looking carefully in the menu and started digging the metadata beforehand... Have a nice day, Zdenek -- Zdenek Dohnal Software Engineer Red Hat Czech - Brno TPB-C OpenPGP_0x15AA6A7F4D4227D7.asc Description: application/pgp-keys 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
[389-devel] 389 DS nightly 2020-10-08 - 94% PASS
https://fedorapeople.org/groups/389ds/ci/nightly/2020/10/08/report-389-ds-base-1.4.4.4-20201007git54b5442.fc32.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
Re: sundials-5.4.0 updating
I've built: bout++ - just now octave - previously in the side tag Near as I can tell those are the only packages that directly depend on any of the sundials libraries: $ sudo dnf repoquery --whatrequires 'libsundials*.so*' --source | sort -u bout++-4.3.1-7.fc34.src.rpm octave-5.2.0-8.fc34.src.rpm sundials2-2.7.0-7.fc34.src.rpm sundials-5.4.0-1.fc34.src.rpm dolfin doesn't seem to link to anything in sundials, and python-steps is currently not building with a system sundials2 due to a bug that seems like has been fixed: https://bugzilla.redhat.com/show_bug.cgi?id=1820991 Orion On 10/3/20 6:17 AM, Antonio T. sagitter wrote: Hi again. You can build packages depending on Sundials by using the side-tag f34-build-side-31299: Use 'fedpkg build --target=f34-build-side-31299' to use it. Use 'koji wait-repo f34-build-side-31299' to wait for the build repo to be generated. On 25/09/20 21:04, Antonio T. sagitter wrote: Hi all. Sundials will be updated to the release 5.4.0 on Rawhide branch in 7 days at least. Probably, i will create a specific side-tag. Sundials 5.4.0 release notes: https://github.com/LLNL/sundials/releases/tag/v5.4.0 Regards. -- Orion Poplawski Manager of NWRA Technical Systems 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
Schedule for Thursday's FPC Meeting (2020-10-08 16:00 UTC)
Following is the list of topics that will be discussed in the FPC meeting Thursday at 2020-10-08 16:00 UTC in #fedora-meeting-1 on irc.freenode.net. Local time information (via. uitime): = Day: Thursday == 2020-10-08 09:00 PDT US/Pacific 2020-10-08 12:00 EDT --> US/Eastern <-- 2020-10-08 16:00 UTC UTC 2020-10-08 17:00 BST Europe/London 2020-10-08 18:00 CEST Europe/Berlin 2020-10-08 18:00 CEST Europe/Paris 2020-10-08 21:30 IST Asia/Calcutta New Day: Friday - 2020-10-09 00:00 HKT Asia/Hong_Kong 2020-10-09 00:00 +08 Asia/Singapore 2020-10-09 01:00 JST Asia/Tokyo 2020-10-09 02:00 AEST Australia/Brisbane Links to all tickets below can be found at: https://pagure.io/packaging-committee/issues?status=Open=meeting = Followup Issues = #topic #907 Which %__foo macros for executables are acceptable? .fpc 907 https://pagure.io/packaging-committee/issue/907 = Followup Pull Requests = #topic #pr-814 Add SELinux Independent Policy Guidelines. https://pagure.io/packaging-committee/pull-request/814 = Open Floor = For more complete details, please visit each individual ticket. The report of the agenda items can be found at: https://pagure.io/packaging-committee/issues?status=Open=meeting If you would like to add something to this agenda, you can: * Reply to this e-mail * File a new ticket at: https://pagure.io/packaging-committee * E-mail me directly * Bring it up at the end of the meeting, during the open floor topic. Note that added topics may be deferred until the following meeting. ___ 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: Self Indroduction: Rafael Jeffman
On Mon, 5 Oct 2020 at 22:47, Rafael Jeffman wrote: > Hello, > > I am involved in the development of ansible-freeipa ( > https://github.com/freeipa/ansible-freeipa) and plan to co-maintain it > for Fedora. > > Years ago I helped with the development and packages for an alternative > Linux distribution, GoboLinux (https://gobolinux.org), which I helped > develop from the start. > > I'm still learning the tools for building packages for Fedora, but since I > am doing the upstream development on the project, it is convenient to do > both, so the package can be updated in a more responsive way, avoiding > issues due to outdated versions, as happened recently. > > Regards, > > Rafael > Welcome! :) > > ___ 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 1885368] perl-Digest-MD5-2.58 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1885368 --- Comment #6 from Fedora Update System --- FEDORA-2020-1c29e70c7b has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-1c29e70c7b` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-1c29e70c7b 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. ___ 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
[Bug 1859831] bugzilla-5.0.6-6.fc33 FTBFS: %_python_bytecompile_extra is discontinued
https://bugzilla.redhat.com/show_bug.cgi?id=1859831 Fedora Update System changed: What|Removed |Added Fixed In Version|bugzilla-5.0.6-9.fc33 |bugzilla-5.0.6-9.fc33 |bugzilla-5.0.6-6.fc32 |bugzilla-5.0.6-6.fc32 ||bugzilla-5.0.6-4.fc31 --- Comment #10 from Fedora Update System --- FEDORA-2020-707592630e has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report. -- 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
[Bug 1855962] bugzilla can't send non-html email
https://bugzilla.redhat.com/show_bug.cgi?id=1855962 Fedora Update System changed: What|Removed |Added Fixed In Version|bugzilla-5.0.6-9.fc33 |bugzilla-5.0.6-9.fc33 |bugzilla-5.0.6-6.fc32 |bugzilla-5.0.6-6.fc32 ||bugzilla-5.0.6-4.fc31 --- Comment #9 from Fedora Update System --- FEDORA-2020-707592630e has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report. -- 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: F33 upgrade: dnssec-trigger and Strong Crypto Settings, phase 2
On Wed, 7 Oct 2020, Dominik 'Rathann' Mierzejewski wrote:
Today, I upgraded one of my machines to F33. Upon first F33 boot I
noticed that the dnssec-triggerd service failed to start. It turns out I
had very old dnssec-trigger keys and certificates ("only" 1536-bit RSA)
generated back in 2014 which no longer passed as acceptable per the
default crypto policy change [1], which requires at least 2048-bit keys.
The work-around is to move away or delete the existing keys and
certificates in /etc/dnssec-trigger and let
dnssec-triggerd-keygen.service generate new ones. After that, the
dnssec-triggerd.service starts successfully. I filed a bug[2] against
dnssec-trigger.
Can dnssec-trigger not work now via a unix domain socket instead of TLS
for its command channel? I know NLnetlabs added that for its other
servers like unbound and nsd that only supported TLS before.
The man page suggests it does not support this yet, but I'm pretty
sure upsteam would accept a patch.
Paul
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
[Bug 1886146] perl-DateTime-TimeZone-2.41 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1886146 Upstream Release Monitoring changed: What|Removed |Added Summary|perl-DateTime-TimeZone-2.40 |perl-DateTime-TimeZone-2.41 |is available|is available --- Comment #1 from Upstream Release Monitoring --- Latest upstream release: 2.41 Current version/release in rawhide: 2.39-4.fc33 URL: http://search.cpan.org/dist/DateTime-TimeZone/ 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/2801/ -- 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
[Bug 1859831] bugzilla-5.0.6-6.fc33 FTBFS: %_python_bytecompile_extra is discontinued
https://bugzilla.redhat.com/show_bug.cgi?id=1859831 Fedora Update System changed: What|Removed |Added Fixed In Version|bugzilla-5.0.6-9.fc33 |bugzilla-5.0.6-9.fc33 ||bugzilla-5.0.6-6.fc32 --- Comment #9 from Fedora Update System --- FEDORA-2020-53cdcb90d8 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report. -- 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
[Bug 1883370] perltidy-20201001 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1883370 Fedora Update System changed: What|Removed |Added Fixed In Version|perltidy-20201001-1.fc34|perltidy-20201001-1.fc34 |perltidy-20201001-1.fc33|perltidy-20201001-1.fc33 ||perltidy-20201001-1.fc32 --- Comment #6 from Fedora Update System --- FEDORA-2020-680bc171eb has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report. -- 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
[Bug 1855962] bugzilla can't send non-html email
https://bugzilla.redhat.com/show_bug.cgi?id=1855962 Fedora Update System changed: What|Removed |Added Fixed In Version|bugzilla-5.0.6-9.fc33 |bugzilla-5.0.6-9.fc33 ||bugzilla-5.0.6-6.fc32 --- Comment #8 from Fedora Update System --- FEDORA-2020-53cdcb90d8 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report. -- 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
September Fedora CoreOS update for the Fedora Council
The Fedora CoreOS working group periodically gives status updates to the Fedora Council. Since we compiled this list I figured it would be nice to share more widely: - Rebased the `next` stream to Fedora 33 - https://github.com/coreos/fedora-coreos-tracker/issues/611 - Added better afterburn support and image artifacts for IBM Cloud - https://github.com/coreos/fedora-coreos-tracker/issues/277#issuecomment-678677137 - The bootupd (Distribution-independent updates for bootloaders) project exists - https://github.com/coreos/bootupd/ - Migrated to from podman 1.x to 2.x - https://github.com/coreos/fedora-coreos-tracker/issues/575 - Stepped up efforts to make package layering more reliable - https://github.com/coreos/fedora-coreos-tracker/issues/400 - Upstream projects documentation - See "Projects documentation" subsections on our docs site: - https://docs.fedoraproject.org/en-US/fedora-coreos/ - New rpm-ostree release with: - compatibility for rpmdb sqlite migration - prep work for better package layering support - https://github.com/coreos/rpm-ostree/releases/tag/v2020.5 - New Zincati release with plenty of new metrics exposed - https://github.com/coreos/zincati/releases/tag/v0.0.13 - Support for root-on-LUKS using Clevis pinning - https://github.com/coreos/fedora-coreos-config/pull/609 - New console-login-helper-messages releases with various bug fixes and improvements - Notably, support for displaying complex networking devices and devices with custom names: - https://github.com/coreos/console-login-helper-messages/releases/tag/v0.19 Originally posted at: https://github.com/coreos/fedora-coreos-tracker/issues/608#issuecomment-705168980 ___ 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: This is bad, was Re: Fedora 33 System-Wide Change proposal:??^M^J systemd-resolved
On Fri, 2 Oct 2020, Michael Catanzaro wrote: Hm, thanks for the explanation. I guess the DNS request would indeed be the *first* way you lose, because you have to do DNS before you do anything else. But you are going to lose immediately after anyway: * Immediately after you connect to the network, Fedora connects to http://fedoraproject.org/static/hotspot.txt to see if you're behind a captive portal * Next, GNOME Software starts checking for updates in the background. You've leaked "personal data" to fedoraproject.org again, and also fwupd. If the locally configured DNS server supports Query Minimalization as per RFC 7816, at this point you would have only revealed "." or ".org" If it further supports DNS-over-TLS, and more TLDs will start to support this, then nothing would be leaked. The world is steadilly moving towards this. Add encrypted SNI, and you see this improves even more. That is why governments are actually afraid of the opposite of GDPR right now. The fear of missing out of seeing DNS/SNI data. * You open Firefox, it downloads Safe Browsing data from Google. (Admittedly this one is probably only behind a European CDN, but maybe Google is having a bad day, or maybe IP address logs are sent to the US.) This argument is that any browsing is a GDPR violation of every browser and OS. It is not a helpfull discussion, and if worth discussing, it should be discussed by laywers, not software engineers. I'm sure my list is missing quite a lot. If your interpretation is correct, then I suppose German companies should immediately discontinue use of Fedora, and also most other computer operating systems The goal should always be to do the least amount of personal information gathering or leaking. Stating "but it leaks over there too" is not a very strong argument to leak data yourself. Paul ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
F33 upgrade: dnssec-trigger and Strong Crypto Settings, phase 2
Today, I upgraded one of my machines to F33. Upon first F33 boot I
noticed that the dnssec-triggerd service failed to start. It turns out I
had very old dnssec-trigger keys and certificates ("only" 1536-bit RSA)
generated back in 2014 which no longer passed as acceptable per the
default crypto policy change [1], which requires at least 2048-bit keys.
The work-around is to move away or delete the existing keys and
certificates in /etc/dnssec-trigger and let
dnssec-triggerd-keygen.service generate new ones. After that, the
dnssec-triggerd.service starts successfully. I filed a bug[2] against
dnssec-trigger.
[1] https://www.fedoraproject.org/wiki/Changes/StrongCryptoSettings2
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1886172
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
Re: F34 Change proposal: Debug Info Standardization (from DWZ to -fdebug-types-section) (System-Wide Change proposal)
On Mon, 28 Sep 2020 17:58:58 +0200, Jakub Jelinek wrote: > On Mon, Sep 28, 2020 at 05:46:08PM +0200, Jan Kratochvil wrote: > > On Mon, 28 Sep 2020 17:35:26 +0200, Jakub Jelinek wrote: > > > A way out of this could be either to use comdat .debug_info etc. sections > > > (but that would result in quite large increase of *.o file sizes), or let > > > the linker or a tool like DWZ discard or simplify such DIEs. > > > I don't see how could you see at compile time that the linker will not > > > choose the particular copy. > > > > Another option is to use clang which should have such optimization > > implemented > > soon: > > https://whova.com/embedded/session/llvm_202010/1193947/ > > If you do it on the compiler side, you'll get a lot of those pesky partial > units you so hate on the lldb side. No. The LLVM patches from Sony are using COMDAT groups you mentioned above: https://youtu.be/oSCbzLC46Vg?t=312 Jan ___ 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
Non-responsive maintainer: noodles
Hi, in accordance with https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/ this is a non-responsive maintainer check for Nick Le Mouton. Non-responsive bug: https://bugzilla.redhat.com/show_bug.cgi?id=1886164 Unactioned bugs (CVEs from January; earliest from 2013): https://bugzilla.redhat.com/show_bug.cgi?id=807816 https://bugzilla.redhat.com/show_bug.cgi?id=1291335 https://bugzilla.redhat.com/show_bug.cgi?id=1240317 https://bugzilla.redhat.com/show_bug.cgi?id=1471224 https://bugzilla.redhat.com/show_bug.cgi?id=1369844 https://bugzilla.redhat.com/show_bug.cgi?id=1534117 https://bugzilla.redhat.com/show_bug.cgi?id=1553372 https://bugzilla.redhat.com/show_bug.cgi?id=1790272 https://bugzilla.redhat.com/show_bug.cgi?id=1790275 https://bugzilla.redhat.com/show_bug.cgi?id=1802210 https://bugzilla.redhat.com/show_bug.cgi?id=1585015 So, does anyone know how to contact Nick? Thanks, --Robbie signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
[Bug 1886146] New: perl-DateTime-TimeZone-2.40 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1886146 Bug ID: 1886146 Summary: perl-DateTime-TimeZone-2.40 is available Product: Fedora Version: rawhide Status: NEW Component: perl-DateTime-TimeZone 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: 2.40 Current version/release in rawhide: 2.39-4.fc33 URL: http://search.cpan.org/dist/DateTime-TimeZone/ 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/2801/ -- 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
[Bug 1886085] perl-Net-Amazon-S3-0.96 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1886085 --- Comment #2 from Upstream Release Monitoring --- the-new-hotness/release-monitoring.org's scratch build of perl-Net-Amazon-S3-0.96-1.fc32.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=52946774 -- 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
[Bug 1886085] perl-Net-Amazon-S3-0.96 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1886085 --- Comment #1 from Upstream Release Monitoring --- Created attachment 1719803 --> https://bugzilla.redhat.com/attachment.cgi?id=1719803=edit [patch] Update to 0.96 (#1886085) -- 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
[Bug 1886085] New: perl-Net-Amazon-S3-0.96 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1886085 Bug ID: 1886085 Summary: perl-Net-Amazon-S3-0.96 is available Product: Fedora Version: rawhide Status: NEW Component: perl-Net-Amazon-S3 Keywords: FutureFeature, Triaged Assignee: ppi...@redhat.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: igor.ra...@gmail.com, jakub.jedel...@gmail.com, perl-devel@lists.fedoraproject.org, ppi...@redhat.com, rr...@redhat.com, tjczep...@gmail.com Target Milestone: --- Classification: Fedora Latest upstream release: 0.96 Current version/release in rawhide: 0.95-1.fc34 URL: http://search.cpan.org/dist/Net-Amazon-S3/ 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/6573/ -- 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: mock, febootstrap, building chroots a.k.a. debootstrap
Dne 07. 10. 20 v 11:47 Daniel Pocock napsal(a):
> Is Mock only intended for building things or the chroot created by Mock
> can be considered a long-lived chroot for daily use?
The original purpose is a build tool.
But I see many people to do:
mock -r fedora-33-x86_64 shell
> With the move to Btrfs by default, is it possible that will be adapted?
> Or can people manually manage their snapshots on their preferred
> storage platform?
There is no such plan. But contribution is welcome.
>>> The "fastest to get started" way to solve getting these chroots is to pull
>>> a container image and extract that.
>> https://github.com/rpm-software-management/mock/wiki/Feature-container-for-bootstrap
>> But you still want to setup timezones, make sure the packages are updated
>> there, copy some files there... Mock does all
>> of that.
> Can you also clarify which container platform is being suggested?
The mentioned feature use podman to retrieve the image and unpack the container
to directory.
> To put all this in context, imagine the user is on Fedora 32, they saw
> the thread about Thunderbird 78.2.1 "Unpleasant Surprise" from Fedora 33
> and they want to run that in a chroot to see the impact on their profile
> and plugins. They could create the chroot using any of the methods
> discussed, yum --installroot, Mock, container. Maybe they want to
> snapshot or fork their ~/.thunderbird profile but have access to their
> regular ~/.gnupg setup.
Just put:
config_opts['exclude_from_homedir_cleanup'] = ['.thunderbird']
config_opts['plugin_conf']['bind_mount_enable'] = True
config_opts['plugin_conf']['bind_mount_opts']['dirs'].append(('/home/MSUCHY/.thunderbird',
'/builddir/.thunderbird' ))
into ~/.config/mock.cfg
and run
mock -r fedora-32-x86_64 --isolation=simple shell
And you should have your .thunderbird directory bind mounted. Diclaimer: I did
not test it, and I would test it first on
something less precious than my mails because Mock cleans up things at the end.
The `simple` isolation to use simple chroot() otherwise systemd-nspawn is used
and you will not be able to run xwindows
applications.
>
> This can be really useful for the type of problem discussed in
> Thunderbird but it can also be useful for people on non-x86 platforms
> who regularly need to test new versions of specific applications.
Did I mentioned that with Mock it is super easy to use different arches?
https://github.com/rpm-software-management/mock/wiki/Feature-forcearch
--
Miroslav Suchy, RHCA
Red Hat, Associate Manager ABRT/Copr, #brno, #fedora-buildsys
___
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 net install iso the possibilitie to add espeakup for people like me whome are blind?
hey all, I would like to start off by saying i'm not a programmer or dev person, just a end user of fedora. would it be possible to have espeakup and espeak added to the net install iso of fedora? the iso where you can choose what you will be installing? now that espeakup has been mainlined in to the kernel would this be able to be made a reality? failing that would it be possible to make the net install iso accessible? thanks for reading my question, Majid Hussain ___ 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
Get Sponsored for my package
Hi, all I saw https://fedoraproject.org/wiki/Join_the_package_collection_maintainers and I have submit my review requst to bugzilla. https://bugzilla.redhat.com/show_bug.cgi?id=1882871 Can anyone help me review it. What should I do next to get sponsored into package group? Thanks! -- Ruki Wang war...@gmail.com https://github.com/waruqi https://twitter.com/waruqi ___ 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-20201007.0 compose check report
No missing expected images. Soft failed openQA tests: 1/16 (x86_64) (Tests completed, but using a workaround for a known bug) ID: 687339 Test: x86_64 IoT-dvd_ostree-iso iot_clevis URL: https://openqa.fedoraproject.org/tests/687339 Passed openQA tests: 15/16 (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
[Bug 1885368] perl-Digest-MD5-2.58 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1885368 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #5 from Fedora Update System --- FEDORA-2020-fe1d34e4aa has been pushed to the Fedora 33 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-fe1d34e4aa` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-fe1d34e4aa 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. ___ 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
[Bug 1885489] perl-Test2-Suite-0.000136 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1885489 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #3 from Fedora Update System --- FEDORA-2020-ddacb31212 has been pushed to the Fedora 33 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-ddacb31212` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-ddacb31212 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. ___ 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: F33+rpmfusion pulseaudio-module-bluetooth-freeworld: pulseaudio crashes with bluetooth audio device
On 07.10.2020 14:52, Lumír Balhar wrote: rpm --erase --nodeps pulseaudio-module-bluetooth-freeworld dnf install pulseaudio-module-bluetooth Do not run rpm directly. Use dnf-swap instead: sudo dnf swap pulseaudio-module-bluetooth-freeworld pulseaudio-module-bluetooth -- 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
Schedule for Wednesday's FESCo Meeting (2020-10-07)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Following is the list of topics that will be discussed in the FESCo meeting Wednesday at 14:00UTC in #fedora-meeting-2 on irc.freenode.net. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/UTCHowto or run: date -d '2020-10-07 14:00 UTC' Links to all issues to be discussed can be found at: https://pagure.io/fesco/report/meeting_agenda = Discussed and Voted in the Ticket = None this week = Followups = #topic #2441 F34 System-Wide Change: RPM-level auto release and changelog bumping https://pagure.io/fesco/issue/2441 #topic #2474 F34 System-Wide Change: Rust Crate Packages For Release Branches https://pagure.io/fesco/issue/2474 = New business = #topic #2479 F33 UEFI Secure Boot signing keys https://pagure.io/fesco/issue/2479 = Open Floor = For more complete details, please visit each individual issue. The report of the agenda items can be found at https://pagure.io/fesco/report/meeting_agenda If you would like to add something to this agenda, you can reply to this e-mail, file a new issue at https://pagure.io/fesco, e-mail me directly, or bring it up at the end of the meeting, during the open floor topic. Note that added topics may be deferred until the following meeting. -BEGIN PGP SIGNATURE- iQGzBAEBCAAdFiEEhQqd0dvyrMxvxJSRRduFpWgobREFAl99ybAACgkQRduFpWgo bRE8zwwAgdBtnTLy25Jg164ij1+jxCrHd+yOPCI2tHd+v4TdbiP7v11GCd/shktn 5OdRSkmuVpeyCVELacNCm4D3VgnTgfb11kqlYZAzeRWpstkmTgit8FkyJzgwzwjQ BbJf6lWzqPbAOk2xaz9OPymG8hdW7ziUKJDM7qzcUfbctZ+/nNvSxlpfV51MrRjI czivN6V9K3QIFbEcDzpNnlgrhGXUSJlO+IA1XeRfHkZJg6RFOiSgAg+K+1VSpuVm jsH2zZcSXJorzDtZ6UEYRmW5Vmt+HHHMSYBUuVIwr++pfDKPwV24n2lS4gI+qdWo bOxr7QO4kV2kb/jV7q05G2gvV12Vf3upozGgWM5I0TmpH9AwxqdGisNt0U/L/xCb iSwD8jNEPpZWw+GUUZf65nFOAYCCl65CS/nYOAntmscY/GnUkOSm1/2C42hEb96A qYVVOOto0UAG1g0N8HXZnRQCvUAEOnYRKrS5quHRgfdGtO5AASEe1v0JSt7wqV3f J14XKMkM =deaR -END 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: interest in debuginfod as fedora service
Dne 05. 10. 20 v 17:20 Frank Ch. Eigler napsal(a): > The problem is that Fedora itself doesn't run a server, and our test > server can afford to carry only a subset of debuginfo/debugsource rpms > & architectures. So, fedora developers / users cannot get at all the > info, or from an official source. I wonder if it's time to get one > set up. If there is interest, I'd be happy to start discussing > logistics with fedora infrastructure folks. As many pointed ABRT does that. For any crash catched by ABRT you can run: abrt debuginfo-install $ID # id can be taken from `abrt list` The server retrace.fedoraproject.org contains all required packages. I will be more than happy to host there some service which will provide the debuginfod service. But it must be integrated with current ABRT Analytics and Retrace-server so we do not host packages twice. The abrt hangs on #abrt on Freenode. And the upstream is on: https://github.com/abrt/ The playbook for retrace setup is in: https://pagure.io/fedora-infra/ansible/blob/master/f/playbooks/groups/retrace.yml Contribution is more than welcome. -- Miroslav Suchy, RHCA Red Hat, Associate Manager ABRT/Copr, #brno, #fedora-buildsys ___ 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-33-20201007.n.0 compose check report
Missing expected images: Xfce raw-xz armhfp Failed openQA tests: 4/181 (x86_64) New failures (same test not failed in Fedora-33-20201006.n.1): ID: 687047 Test: x86_64 Silverblue-dvd_ostree-iso desktop_background URL: https://openqa.fedoraproject.org/tests/687047 Old failures (same test failed in Fedora-33-20201006.n.1): ID: 687022 Test: x86_64 KDE-live-iso apps_startstop URL: https://openqa.fedoraproject.org/tests/687022 ID: 687031 Test: x86_64 KDE-live-iso desktop_background URL: https://openqa.fedoraproject.org/tests/687031 ID: 687033 Test: x86_64 KDE-live-iso desktop_notifications_postinstall URL: https://openqa.fedoraproject.org/tests/687033 Soft failed openQA tests: 11/181 (x86_64) (Tests completed, but using a workaround for a known bug) New soft failures (same test not soft failed in Fedora-33-20201006.n.1): ID: 687037 Test: x86_64 Silverblue-dvd_ostree-iso install_default_upload URL: https://openqa.fedoraproject.org/tests/687037 ID: 687040 Test: x86_64 Silverblue-dvd_ostree-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/687040 Old soft failures (same test soft failed in Fedora-33-20201006.n.1): ID: 686958 Test: x86_64 Server-dvd-iso install_vncconnect_client URL: https://openqa.fedoraproject.org/tests/686958 ID: 686977 Test: x86_64 Server-dvd-iso install_vnc_client URL: https://openqa.fedoraproject.org/tests/686977 ID: 687004 Test: x86_64 Workstation-live-iso desktop_update_graphical URL: https://openqa.fedoraproject.org/tests/687004 ID: 687017 Test: x86_64 Workstation-live-iso desktop_printing URL: https://openqa.fedoraproject.org/tests/687017 ID: 687054 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/687054 ID: 687066 Test: x86_64 universal upgrade_2_minimal_64bit URL: https://openqa.fedoraproject.org/tests/687066 ID: 687067 Test: x86_64 universal upgrade_2_server_domain_controller URL: https://openqa.fedoraproject.org/tests/687067 ID: 687088 Test: x86_64 universal upgrade_server_domain_controller URL: https://openqa.fedoraproject.org/tests/687088 ID: 687091 Test: x86_64 universal upgrade_2_minimal_uefi@uefi URL: https://openqa.fedoraproject.org/tests/687091 Passed openQA tests: 166/181 (x86_64) New passes (same test not passed in Fedora-33-20201006.n.1): ID: 687032 Test: x86_64 KDE-live-iso desktop_login URL: https://openqa.fedoraproject.org/tests/687032 ID: 687038 Test: x86_64 Silverblue-dvd_ostree-iso desktop_terminal URL: https://openqa.fedoraproject.org/tests/687038 ID: 687039 Test: x86_64 Silverblue-dvd_ostree-iso desktop_browser URL: https://openqa.fedoraproject.org/tests/687039 ID: 687041 Test: x86_64 Silverblue-dvd_ostree-iso release_identification URL: https://openqa.fedoraproject.org/tests/687041 ID: 687042 Test: x86_64 Silverblue-dvd_ostree-iso base_reboot_unmount URL: https://openqa.fedoraproject.org/tests/687042 ID: 687043 Test: x86_64 Silverblue-dvd_ostree-iso base_system_logging URL: https://openqa.fedoraproject.org/tests/687043 ID: 687044 Test: x86_64 Silverblue-dvd_ostree-iso base_services_start URL: https://openqa.fedoraproject.org/tests/687044 ID: 687045 Test: x86_64 Silverblue-dvd_ostree-iso base_selinux URL: https://openqa.fedoraproject.org/tests/687045 ID: 687046 Test: x86_64 Silverblue-dvd_ostree-iso base_service_manipulation URL: https://openqa.fedoraproject.org/tests/687046 Installed system changes in test x86_64 Server-dvd-iso install_default@uefi: System load changed from 0.09 to 0.27 Previous test data: https://openqa.fedoraproject.org/tests/686242#downloads Current test data: https://openqa.fedoraproject.org/tests/686966#downloads Installed system changes in test x86_64 Workstation-live-iso install_default_upload: Used swap changed from 52 MiB to 35 MiB System load changed from 1.20 to 0.87 Previous test data: https://openqa.fedoraproject.org/tests/686277#downloads Current test data: https://openqa.fedoraproject.org/tests/687001#downloads Installed system changes in test x86_64 Workstation-live-iso install_default@uefi: System load changed from 0.55 to 1.04 Previous test data: https://openqa.fedoraproject.org/tests/686279#downloads Current test data: https://openqa.fedoraproject.org/tests/687003#downloads Installed system changes in test x86_64 KDE-live-iso install_default_upload: Used swap changed from 12 MiB to 8 MiB System load changed from 2.04 to 0.89 Average CPU usage changed from 45.27142857 to 32.11904762 Previous test data: https://openqa.fedoraproject.org/tests/686296#downloads Current test data: https://openqa.fedoraproject.org/tests/687020#downloads Installed system changes in test x86_64 KDE-live-iso install_default@uefi: Used swap changed from 17 MiB to 12 MiB System load changed from 1.61 to 1.34 Previous test data: https://openqa.fedoraproject.org/tests/686297#downloads Current test data:
Re: F33+rpmfusion pulseaudio-module-bluetooth-freeworld: pulseaudio crashes with bluetooth audio device
On 07/10/2020 13:52, Lumír Balhar wrote: A workaround solution for me was to remove pulseaudio-module-bluetooth-freeworld and install pulseaudio-module-bluetooth from Fedora's repositories but it wasn't that straightforward because some parts of gnome has this package in dependencies so it'd end up uninstalling protected packages so I had to remove it manually using RPM and then install the official one. rpm --erase --nodeps pulseaudio-module-bluetooth-freeworld dnf install pulseaudio-module-bluetooth This is where using the shell can help: % sudo dnf shell > erase pulseaudio-module-bluetooth-freeworld > install pulseaudio-module-bluetooth > run and it will do it all in one transaction, allowing the dependency to be maintained. Tom -- Tom Hughes (t...@compton.nu) http://compton.nu/ ___ 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
Non-responsive maintainer: llaumgui
As per https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/, does anyone know how to get in touch with Guillaume Kulakowski? Package csslint hasn’t been touched by them since 2013, and fedora-active-user reports no activity from him this year. https://bugzilla.redhat.com/show_bug.cgi?id=1886006 -- Peter Oliver___ 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] Reminder about git commit headers
Hello, Seems like everyone is doing something different with the commit headers, and I've been wanting to address it. I'd prefer we use "Issue " and stop using "Ticket ". Most developers are using "Issue ###", but some are still using "Ticket", so I always have to tweak this when doing upstream builds and writing the release notes. https://www.port389.org/docs/389ds/contributing.html#getting-the-patch-ready We silently switched to using "Issue " when we went to Pagure, but it was never officially stated. Moving forward I'd really appreciate it if everyone used "Issue - " as the first line in your commits. Note the hyphen before the issue description. Also please don't use colons, just use "Issue - My description of this patch". It just makes doing upstream releases and wiki updates easier. Thanks, Mark -- 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
Fedora 33 compose report: 20201007.n.0 changes
OLD: Fedora-33-20201006.n.1 NEW: Fedora-33-20201007.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
F33+rpmfusion pulseaudio-module-bluetooth-freeworld: pulseaudio crashes with bluetooth audio device
Hello. After an update to F33 beta, I had troubles with my BT audio devices. I know Fedora maintainers cannot do anything about it and I've already sent a bug report to rpmfusion https://bugzilla.rpmfusion.org/show_bug.cgi?id=5786 So, just in case somebody will have the same problem as I did: I was using pulseaudio-module-bluetooth-freeworld on Fedora 32 without any issues and I've recently updated to Fedora 33 beta. After that, whenever I've connected any audio bluetooth device, pulseaudio crashes and a device disconnects. This was happening for my Sony BT headphones as well as for JBL BT speaker. A workaround solution for me was to remove pulseaudio-module-bluetooth-freeworld and install pulseaudio-module-bluetooth from Fedora's repositories but it wasn't that straightforward because some parts of gnome has this package in dependencies so it'd end up uninstalling protected packages so I had to remove it manually using RPM and then install the official one. rpm --erase --nodeps pulseaudio-module-bluetooth-freeworld dnf install pulseaudio-module-bluetooth Have a nice day. Lumír ___ 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-20201007.n.0 compose check report
Missing expected images: Xfce raw-xz armhfp Compose FAILS proposed Rawhide gating check! 5 of 43 required tests failed, 8 results missing openQA tests matching unsatisfied gating requirements shown with **GATING** below Failed openQA tests: 22/181 (x86_64) New failures (same test not failed in Fedora-Rawhide-20201006.n.1): ID: 686731 Test: x86_64 Workstation-live-iso desktop_notifications_live URL: https://openqa.fedoraproject.org/tests/686731 ID: 686768 Test: x86_64 Silverblue-dvd_ostree-iso install_default_upload URL: https://openqa.fedoraproject.org/tests/686768 ID: 686771 Test: x86_64 Silverblue-dvd_ostree-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/686771 ID: 686790 Test: x86_64 universal upgrade_desktop_encrypted_64bit URL: https://openqa.fedoraproject.org/tests/686790 ID: 686805 Test: x86_64 universal support_server URL: https://openqa.fedoraproject.org/tests/686805 ID: 686812 Test: x86_64 universal install_package_set_kde URL: https://openqa.fedoraproject.org/tests/686812 ID: 686817 Test: x86_64 universal upgrade_2_desktop_64bit URL: https://openqa.fedoraproject.org/tests/686817 ID: 686818 Test: x86_64 universal upgrade_2_desktop_encrypted_64bit URL: https://openqa.fedoraproject.org/tests/686818 ID: 686830 Test: x86_64 universal install_asian_language URL: https://openqa.fedoraproject.org/tests/686830 ID: 686835 Test: x86_64 universal upgrade_desktop_64bit URL: https://openqa.fedoraproject.org/tests/686835 ID: 686836 Test: x86_64 universal install_arabic_language URL: https://openqa.fedoraproject.org/tests/686836 ID: 686838 Test: x86_64 universal upgrade_2_kde_64bit URL: https://openqa.fedoraproject.org/tests/686838 ID: 686851 Test: x86_64 universal upgrade_kde_64bit URL: https://openqa.fedoraproject.org/tests/686851 ID: 686855 Test: x86_64 universal install_european_language URL: https://openqa.fedoraproject.org/tests/686855 ID: 686886 Test: x86_64 Workstation-live-iso install_default_upload **GATING** URL: https://openqa.fedoraproject.org/tests/686886 ID: 686902 Test: x86_64 Workstation-live-iso install_default@uefi **GATING** URL: https://openqa.fedoraproject.org/tests/686902 Old failures (same test failed in Fedora-Rawhide-20201006.n.1): ID: 686749 Test: x86_64 KDE-live-iso desktop_notifications_live URL: https://openqa.fedoraproject.org/tests/686749 ID: 686833 Test: x86_64 universal install_cyrillic_language URL: https://openqa.fedoraproject.org/tests/686833 ID: 686867 Test: x86_64 universal install_iscsi URL: https://openqa.fedoraproject.org/tests/686867 ID: 686868 Test: x86_64 KDE-live-iso install_no_user **GATING** URL: https://openqa.fedoraproject.org/tests/686868 ID: 686869 Test: x86_64 KDE-live-iso install_default_upload **GATING** URL: https://openqa.fedoraproject.org/tests/686869 ID: 686885 Test: x86_64 KDE-live-iso install_default@uefi **GATING** URL: https://openqa.fedoraproject.org/tests/686885 Soft failed openQA tests: 4/181 (x86_64) (Tests completed, but using a workaround for a known bug) Old soft failures (same test soft failed in Fedora-Rawhide-20201006.n.1): ID: 686689 Test: x86_64 Server-dvd-iso install_vncconnect_client URL: https://openqa.fedoraproject.org/tests/686689 ID: 686708 Test: x86_64 Server-dvd-iso install_vnc_client URL: https://openqa.fedoraproject.org/tests/686708 ID: 686785 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/686785 ID: 686798 Test: x86_64 universal upgrade_2_server_domain_controller URL: https://openqa.fedoraproject.org/tests/686798 Passed openQA tests: 116/181 (x86_64) Skipped gating openQA tests: 8/181 (x86_64) New skipped gating tests (same test not skipped in Fedora-Rawhide-20201006.n.1): ID: 686892 Test: x86_64 Workstation-live-iso base_system_logging **GATING** URL: https://openqa.fedoraproject.org/tests/686892 ID: 686893 Test: x86_64 Workstation-live-iso base_update_cli **GATING** URL: https://openqa.fedoraproject.org/tests/686893 ID: 686897 Test: x86_64 Workstation-live-iso desktop_terminal **GATING** URL: https://openqa.fedoraproject.org/tests/686897 ID: 686900 Test: x86_64 Workstation-live-iso desktop_browser **GATING** URL: https://openqa.fedoraproject.org/tests/686900 Old skipped gating tests (same test skipped in Fedora-Rawhide-20201006.n.1): ID: 686872 Test: x86_64 KDE-live-iso base_system_logging **GATING** URL: https://openqa.fedoraproject.org/tests/686872 ID: 686873 Test: x86_64 KDE-live-iso base_update_cli **GATING** URL: https://openqa.fedoraproject.org/tests/686873 ID: 686882 Test: x86_64 KDE-live-iso desktop_browser **GATING** URL: https://openqa.fedoraproject.org/tests/686882 ID: 686884 Test: x86_64 KDE-live-iso desktop_terminal **GATING** URL: https://openqa.fedoraproject.org/tests/686884 Skipped non-gating openQA tests: 31 of 181 Installed system changes in test
[Bug 1870755] EPEL8 Branch Request: perl-Data-GUID
https://bugzilla.redhat.com/show_bug.cgi?id=1870755 Ralf Corsepius changed: What|Removed |Added Flags|needinfo?(rc040203@freenet. | |de) | --- Comment #5 from Ralf Corsepius --- (In reply to Jitka Plesnikova from comment #4) > Ralf, could you please set pghmcfc or jplesnik as 'collaborator' and set > allowed branches 'el*,epel*'? No. Ask a RHAT manager or who ever is managing EPEL, and stop molesting me. For clarity: For the 15 years, I am contributing to Fedora, I never ever agreed to supporting EPEL and never will, because RHEL is non-free. -- 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
Fedora rawhide compose report: 20201007.n.0 changes
OLD: Fedora-Rawhide-20201006.n.1 NEW: Fedora-Rawhide-20201007.n.0 = SUMMARY = Added images:0 Dropped images: 0 Added packages: 11 Dropped packages:0 Upgraded packages: 94 Downgraded packages: 0 Size of added packages: 7.47 MiB Size of dropped packages:0 B Size of upgraded packages: 1.79 GiB Size of downgraded packages: 0 B Size change of upgraded packages: -73.29 MiB Size change of downgraded packages: 0 B = ADDED IMAGES = = DROPPED IMAGES = = ADDED PACKAGES = Package: libecpint-1.0.2-1.fc34 Summary: Efficient evaluation of integrals over ab initio effective core potentials RPMs:libecpint libecpint-common libecpint-devel Size:1.63 MiB Package: memavaild-0.5-2.fc34 Summary: Improve responsiveness during heavy swapping RPMs:memavaild Size:15.29 KiB Package: pylibgamerzilla-0.0.1-4.fc34 Summary: Python Integration with Gamerzilla Library RPMs:pylibgamerzilla Size:159.45 KiB Package: python-stackprinter-0.2.4-1.fc34 Summary: Debug-friendly stack traces RPMs:python3-stackprinter Size:50.80 KiB Package: rust-const_fn-0.4.2-1.fc34 Summary: Attribute for easy generation of const functions RPMs:rust-const_fn+default-devel rust-const_fn-devel Size:29.31 KiB Package: rust-peg-macros-0.6.3-1.fc34 Summary: Procedural macros for rust-peg RPMs:peg rust-peg-macros+default-devel rust-peg-macros+trace-devel rust-peg-macros-devel Size:1.43 MiB Package: rust-peg-runtime-0.6.3-1.fc34 Summary: Runtime support for rust-peg grammars RPMs:rust-peg-runtime+default-devel rust-peg-runtime-devel Size:17.70 KiB Package: rust-peg0.5-0.5.7-1.fc34 Summary: Simple Parsing Expression Grammar (PEG) parser generator RPMs:peg0.5 rust-peg0.5+default-devel rust-peg0.5+trace-devel rust-peg0.5-devel Size:1.11 MiB Package: rust-pure-rust-locales-0.5.2-1.fc34 Summary: Pure Rust locales imported directly from the GNU C Library RPMs:rust-pure-rust-locales+default-devel rust-pure-rust-locales-devel Size:1.55 MiB Package: rust-quick-xml-0.18.1-1.fc34 Summary: High performance xml reader and writer RPMs:rust-quick-xml+default-devel rust-quick-xml+encoding-devel rust-quick-xml+encoding_rs-devel rust-quick-xml+serde-devel rust-quick-xml+serialize-devel rust-quick-xml-devel Size:138.64 KiB Package: sid-0.0.4-1.fc34 Summary: Storage Instantiation Daemon (SID) RPMs:sid sid-base-libs sid-base-libs-devel sid-iface-libs sid-iface-libs-devel sid-log-libs sid-log-libs-devel sid-mod-block-blkid sid-mod-block-dm-mpath sid-mod-dummies sid-resource-libs sid-resource-libs-devel sid-tools Size:1.35 MiB = DROPPED PACKAGES = = UPGRADED PACKAGES = Package: FlightGear-2020.1.3-4.fc34 Old package: FlightGear-2020.1.3-3.fc33 Summary: The FlightGear Flight Simulator RPMs: FlightGear Size: 30.60 MiB Size change: 70.98 KiB Changelog: * Tue Oct 06 2020 Jeff Law - 2020.1.3-4 - Force -fPIC into CXXFLAGS for QT Package: Lmod-8.4.7-1.fc34 Old package: Lmod-8.4.5-1.fc34 Summary: Environmental Modules System in Lua RPMs: Lmod Size: 1.07 MiB Size change: 2.68 KiB Changelog: * Tue Oct 06 2020 Orion Poplawski - 8.4.7-1 - Update to 8.4.7 Package: NetworkManager-1:1.28.0-0.1.fc34 Old package: NetworkManager-1:1.26.2-2.fc34 Summary: Network connection manager and user applications RPMs: NetworkManager NetworkManager-adsl NetworkManager-bluetooth NetworkManager-cloud-setup NetworkManager-config-connectivity-fedora NetworkManager-config-server NetworkManager-dispatcher-routing-rules NetworkManager-libnm NetworkManager-libnm-devel NetworkManager-ovs NetworkManager-ppp NetworkManager-team NetworkManager-tui NetworkManager-wifi NetworkManager-wwan Size: 28.85 MiB Size change: 152.16 KiB Changelog: * Tue Oct 06 2020 Thomas Haller - 1:1.28.0-0.1 - update to 1.28-rc1 (1.27.90) Package: Rex-1.13.0-1.fc34 Old package: Rex-1.12.2-1.fc34 Summary: The friendly automation framework on basis of Perl RPMs: Rex Size: 454.80 KiB Size change: 396 B Changelog: * Tue Oct 06 2020 Dominic Hopf - 1.13.0-1 - Upgrade to Rex 1.13.0 Package: ansible-2.9.14-1.fc34 Old package: ansible-2.9.13-1.fc34 Summary: SSH-based configuration management, deployment, and task execution system RPMs: ansible ansible-doc Size: 25.69 MiB Size change: 13.05 KiB Changelog: * Tue Oct 06 2020 Kevin Fenzi - 2.9.14-1 - Update to 2.9.14. Package: binutils-2.35.1-2.fc34 Old package: binutils-2.35.1-1.fc34 Summary: A GNU collection of binary utilities RPMs: binutils binutils-devel binutils-gold Size: 52.32 MiB Size change: 144.15 KiB Changelog: * Tue Oct 06 2020 Nick Clifton - 2.35.1-2 - Fix strip when merging multiple same-named sections. (#1885607) Package: certbot-1.8.0-1.fc34 Old package: certbot-1.7.0-1.fc34 Summary
Fedora-Cloud-31-20201007.0 compose check report
No missing expected images. Passed openQA tests: 7/7 (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: mock, febootstrap, building chroots a.k.a. debootstrap
On 07.10.20 11:47, Daniel Pocock wrote: > When using debootstrap, the user has to do some things manually, like > mounting /proc, /sys, /dev and /dev/shm > > It is relatively easy to duplicate those things for both Fedora and > Debian chroots ArchLinux has a nice script for this (arch-chroot) as part of their arch-install-scripts [1][2]. Christopher [1] https://git.archlinux.org/arch-install-scripts.git/tree/arch-chroot.in [2] https://copr.fedorainfracloud.org/coprs/lcts/easy-chroot/ ___ 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: F34 Change proposal: Debug Info Standardization (from DWZ to -fdebug-types-section) (System-Wide Change proposal)
On Wed, 07 Oct 2020 09:58:37 +0200, Jan Kratochvil wrote: > On Wed, 07 Oct 2020 00:46:24 +0200, Jeff Law wrote: > > On 9/30/20 3:50 AM, Jan Kratochvil wrote: > > > When we start talking about RHEL (and CentOS) DWZ is completely pointless > > > then > > > as DWZ there saves only 0.28% of *-debuginfo.rpm (20MB of 7.2GB). > > > Therefore approx. 0.14% of the distribution size. > > > > Umm, we're fighting with PM these days over things in the 10M range. > > So it is better to slow down getting a finally usable debugger by years to > save 10MB of distro size? I really do not believe that. :-) I think you mean 10MB of normal rpm size. That is important for containers and other small devices. But the 20MB are only *-debuginfo.rpm size, those are only for developer machines. Developer machines are not concerned by 20MB. Jan ___ 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: mock, febootstrap, building chroots a.k.a. debootstrap
On 07/10/2020 08:53, Miroslav Suchý wrote: > Dne 06. 10. 20 v 23:50 James Cassell napsal(a): >> yum install --releasever=/ --installroot=/mnt/sysimage bash mypackage > > This is naive approach. It does not setup: resolver, timezone, dbus uuid, > unpriv user, btrfs-control, special devices, etc. > Yes, for most quick'n'dirty use cases you will not need it and the naive > approach will work. But it will hit you when > you will not expect it. > And it will not work when you are on RHEL7 and want to install Fedora 31 > because of different payload of rpm. > Mock solve all those things. When using debootstrap, the user has to do some things manually, like mounting /proc, /sys, /dev and /dev/shm It is relatively easy to duplicate those things for both Fedora and Debian chroots Is Mock only intended for building things or the chroot created by Mock can be considered a long-lived chroot for daily use? Notice that daemons don't usually run from the chroot, all the desktop and system daemons are running from the host OS. >>> I create the chroots as Btrfs subvolumes, this gives the opportunity to >>> create snapshots too. >>> >>> After testing this a bit, I'd like to document it some more for other >>> people on the platform too. I noticed some people losing time trying to >>> compile things when they could potentially use upcoming versions of the >>> packages. Any feedback would be very welcome. > > Mock supports LVM snapshots: > https://github.com/rpm-software-management/mock/wiki/Plugin-LvmRoot With the move to Btrfs by default, is it possible that will be adapted? Or can people manually manage their snapshots on their preferred storage platform? >> The "fastest to get started" way to solve getting these chroots is to pull a >> container image and extract that. > > https://github.com/rpm-software-management/mock/wiki/Feature-container-for-bootstrap > But you still want to setup timezones, make sure the packages are updated > there, copy some files there... Mock does all > of that. Can you also clarify which container platform is being suggested? To put all this in context, imagine the user is on Fedora 32, they saw the thread about Thunderbird 78.2.1 "Unpleasant Surprise" from Fedora 33 and they want to run that in a chroot to see the impact on their profile and plugins. They could create the chroot using any of the methods discussed, yum --installroot, Mock, container. Maybe they want to snapshot or fork their ~/.thunderbird profile but have access to their regular ~/.gnupg setup. This can be really useful for the type of problem discussed in Thunderbird but it can also be useful for people on non-x86 platforms who regularly need to test new versions of specific applications. 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-Cloud-32-20201007.0 compose check report
No missing expected images. Soft failed openQA tests: 1/7 (x86_64) (Tests completed, but using a workaround for a known bug) ID: 686674 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/686674 Passed openQA tests: 6/7 (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: F34 Change proposal: Debug Info Standardization (from DWZ to -fdebug-types-section) (System-Wide Change proposal)
On Tue, Oct 06, 2020 at 04:46:24PM -0600, Jeff Law wrote: > > On 9/30/20 3:50 AM, Jan Kratochvil wrote: > > On Wed, 30 Sep 2020 01:31:29 +0200, Jeff Law wrote: > >> But the GCC community > >> doesn't really test that option and it's known to be broken with LTO. > > I haven't seen any GCC PR for -fdebug-types-section being broken with LTO. > > I'm not aware of one either. But as Jakub has previously pointed out > debug-types-section is disabled when LTO is enabled. I don't know the > details of why that is done. > > > Could you suggest what is wrong on -fdebug-types-section? > > Your best bet is to discuss with Jakub and perhaps Jason. They're far > more familiar with the debuginfo generation than I am. It didn't used to work with LTO, but some patches have been backported so it at least is passed through now without crashing. There are however still various bugs in the implementation: Excess debug info -fdebug-types-section https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78320 -fdebug-types-section drops DW_AT_object_pointer https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94875 gcc drops top-level dies with -fdebug-types-section https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90232 Fission + type units + compression are suboptimal https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78321 Cheers, Mark ___ 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: libvirt and systemd-resolved integration?
On 10/7/20 6:44 AM, Pavel Zhukov wrote: > > I don't think it's a good idea. > dnsmasq is not dns resolver but acts as DHCP and DNS server. It provides > VMs with IP > address/lease and create corresponding dns record for it. In case of > resolved ip addresses and dns records must be managed either manually > or... with dnsmasq. That is not true. Any query sent to @192.168.122.1 would get reply. I use for example unbound on localhost and all my machines use .vm. domain suffix. rhel7.vm. is machine with rhel7. Dnsmasq manages automatically lease names of all its dhcp clients, it works as dynamic DNS connected with DHCP just out of the box. unbound-control forward_add +i vm 192.168.122.1 Or permanent configuration in /etc/unbound/conf.d/vm.conf: server: domain-insecure: "vm" domain-insecure: "122.168.192.IN-ADDR.ARPA" forward-zone: name: "vm" forward-addr: 192.168.122.1 forward-first: no forward-zone: name: "122.168.192.IN-ADDR.ARPA" forward-addr: 192.168.122.1 forward-first: no Then I used in virsh edit-network default, inside element: dnsmasq is not full resolver, just like systemd-resolver. It just forwards queries it does not have answer to /etc/resolv.conf forwarders. If systemd-resolved does not running on the host, it also offers working DNSSEC environment to all VMs. Since systemd-resolved can do split DNS, it is able to do that also. But it seems current domain redirection is private API for NM. It might work: resolvectl domain virbr0 ~vm But haven't tested it. I am not sure how permanent configuration should look like in resolved.conf. Can it be configured to forward specific domain to specific server? It seems to me it expects such think only per interface, which might work with libvirt too. > On 2020-10-06 at 22:04 CEST, Juan Orti Alcaine wrote... >> Hello, >> >> In the network bridges that libvirt creates there's a dnsmasq daemon to >> resolve the VM's IPs. Is there any way to signal systemd-resolved from >> libvirt to say that in the bridge interface there is a DNS server and a >> domain? >> >> Thank you. > > -- Petr Menšík Software Engineer Red Hat, http://www.redhat.com/ email: pemen...@redhat.com PGP: DFCF908DB7C87E8E529925BC4931CA5B6C9FC5CB signature.asc 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
Re: libvirt and systemd-resolved integration?
On Wed, Oct 07, 2020 at 06:55:32AM +0200, Tomasz Torcz wrote: > On Tue, Oct 06, 2020 at 10:04:19PM +0200, Juan Orti Alcaine wrote: > > Hello, > > > > In the network bridges that libvirt creates there's a dnsmasq daemon to > > resolve the VM's IPs. Is there any way to signal systemd-resolved from > > libvirt to say that in the bridge interface there is a DNS server and a > > domain? > > Related, there is nss-mymachines: > https://www.freedesktop.org/software/systemd/man/nss-mymachines.html > > It resolves IPs of instances registered with machined. Libvirt already > registers virtual machines with machined. But as I see, libvirt does not > provide IP addresses during registration. Maybe this could be fixed? IP addresses are not known at time of registration, but libvirt's own NSS module can be used instead. Regards, Daniel -- |: https://berrange.com -o-https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o-https://fstop138.berrange.com :| |: https://entangle-photo.org-o-https://www.instagram.com/dberrange :| ___ 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: libvirt and systemd-resolved integration?
On Tue, Oct 06, 2020 at 07:21:40PM -0500, Michael Catanzaro wrote: > > Hm, I'm not quite sure how this is intended to work. This is for resolving > VM hostnames into IP addresses? How exactly does it work prior to > systemd-resolved? E.g. lets say I have a libvirt VM named "f33", should it > be possible to resolve that name somehow from the host system? That is possible with libvirt's NSS module: https://libvirt.org/nss.html Regards, Daniel -- |: https://berrange.com -o-https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o-https://fstop138.berrange.com :| |: https://entangle-photo.org-o-https://www.instagram.com/dberrange :| ___ 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: F34 Change proposal: Debug Info Standardization (from DWZ to -fdebug-types-section) (System-Wide Change proposal)
On Wed, 07 Oct 2020 00:46:24 +0200, Jeff Law wrote:
> On 9/30/20 3:50 AM, Jan Kratochvil wrote:
> > On Wed, 30 Sep 2020 01:31:29 +0200, Jeff Law wrote:
> >> But the GCC community
> >> doesn't really test that option and it's known to be broken with LTO.
> > I haven't seen any GCC PR for -fdebug-types-section being broken with LTO.
>
> I'm not aware of one either. But as Jakub has previously pointed out
> debug-types-section is disabled when LTO is enabled. I don't know the
> details of why that is done.
Because Jakub made a mistake and he still has not corrected himself.
I have explained it in:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/2HIK25T3MHP7D6LC5CDJNINP3ZEO7RPW/
If -fdebug-types-section was disabled in LTO mode then there would not be
6.78% vs. 31.23% difference of Fedora mass rebuild of -fdebug-types-section
vs. -fno-debug-types-section.
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/J34DKZK7MWH725CMCS5YLVZ77YURSMRZ/
Also this simple example shows it is not true:
c="static struct C{int a;C(){}} v;";o="-Wall -gdwarf-5
-fdebug-types-section -flto -O2";echo "$c"|gcc -c -o 1.o $o -x c++ -;echo
"${c}int main(){}"|gcc -c -o 2.o $o -x c++ -;gcc -o 1 1.o 2.o $o;llvm-dwarfdump
1|grep DW_UT_type
0x0042: Type Unit: length = 0x005b version = 0x0005 unit_type =
DW_UT_type abbr_offset = 0x0023 addr_size = 0x08 name = 'C' type_signature =
0x4e76c0dda193eb61 type_offset = 0x0026 (next unit at 0x00a1)
> >> So the only paths forward I see are to either fix -fdebug-types-section or
> >> improve dwz.
> > And obviously much easier is to fix -fdebug-types-section than DWZ (if there
> > are really any bugs in -fdebug-types-section, there are known bugs nobody
> > wants to fix in DWZ).
>
> I think you're making an unsubstantiated leap here. Neither of us know
> what's wrong with GCC LTO and debug-types-section
I know what - nothing! Although sure the problem is GCC as its LTO still
produces -fdebug-types-section at all. clang LTO ignores -fdebug-types-section
as clang already does the DWZ-style class unification itself during lld phase.
This discussion and the state of GCC vs. clang shows me that getting rid of
DWZ is less important and as it is more productive for Fedora to rather get
rid of GCC with DWZ altogether.
> and others are working on dwz.
That is their problem. I am trying to work on things that make sense (but
I cannot).
> > When we start talking about RHEL (and CentOS) DWZ is completely pointless
> > then
> > as DWZ there saves only 0.28% of *-debuginfo.rpm (20MB of 7.2GB).
> > Therefore approx. 0.14% of the distribution size.
>
> Umm, we're fighting with PM these days over things in the 10M range.
So it is better to slow down getting a finally usable debugger by years to
save 10MB of distro size? I really do not believe that. :-)
> Most customers don't use dwz. But they consume its output for the RPMs
> that we provide.
They cannot because the LLVM tools Red Hat ships still do not support DWZ.
Jan
___
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 1870755] EPEL8 Branch Request: perl-Data-GUID
https://bugzilla.redhat.com/show_bug.cgi?id=1870755 Jitka Plesnikova changed: What|Removed |Added CC||jples...@redhat.com --- Comment #4 from Jitka Plesnikova --- Ralf, could you please set pghmcfc or jplesnik as 'collaborator' and set allowed branches 'el*,epel*'? Definition of Collaborator is: A user or a group with this level of access can do everything what a user/group with ticket access can do + it can commit to some branches in the project. These branches are defined here using their name or a pattern and needs to be comma separated. Some examples: master,features/* el* master,f* -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-de...@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-de...@lists.fedoraproject.org
[Bug 1885677] perl-Net-Amazon-S3-0.95 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1885677 Petr Pisar changed: What|Removed |Added Status|ASSIGNED|CLOSED Fixed In Version||perl-Net-Amazon-S3-0.95-1.f ||c34 Resolution|--- |RAWHIDE Last Closed||2020-10-07 07:33:17 --- Comment #3 from Petr Pisar --- A bug-fix release suitable for Fedora ≥ 34. -- 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
[Bug 1885677] perl-Net-Amazon-S3-0.95 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1885677 Petr Pisar changed: What|Removed |Added Status|NEW |ASSIGNED CC|ppi...@redhat.com | Doc Type|--- |If docs needed, set a value -- 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: mock, febootstrap, building chroots a.k.a. debootstrap
Dne 06. 10. 20 v 23:50 James Cassell napsal(a): > yum install --releasever=/ --installroot=/mnt/sysimage bash mypackage This is naive approach. It does not setup: resolver, timezone, dbus uuid, unpriv user, btrfs-control, special devices, etc. Yes, for most quick'n'dirty use cases you will not need it and the naive approach will work. But it will hit you when you will not expect it. And it will not work when you are on RHEL7 and want to install Fedora 31 because of different payload of rpm. Mock solve all those things. >> I create the chroots as Btrfs subvolumes, this gives the opportunity to >> create snapshots too. >> >> After testing this a bit, I'd like to document it some more for other >> people on the platform too. I noticed some people losing time trying to >> compile things when they could potentially use upcoming versions of the >> packages. Any feedback would be very welcome. Mock supports LVM snapshots: https://github.com/rpm-software-management/mock/wiki/Plugin-LvmRoot > The "fastest to get started" way to solve getting these chroots is to pull a > container image and extract that. https://github.com/rpm-software-management/mock/wiki/Feature-container-for-bootstrap But you still want to setup timezones, make sure the packages are updated there, copy some files there... Mock does all of that. -- Miroslav Suchy, RHCA Red Hat, Associate Manager ABRT/Copr, #brno, #fedora-buildsys ___ 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: libvirt and systemd-resolved integration?
El mié., 7 oct. 2020 a las 2:22, Michael Catanzaro () escribió: > > Hm, I'm not quite sure how this is intended to work. This is for > resolving VM hostnames into IP addresses? How exactly does it work > prior to systemd-resolved? E.g. lets say I have a libvirt VM named > "f33", should it be possible to resolve that name somehow from the host > system? > > Can you do what you want using > https://www.freedesktop.org/wiki/Software/systemd/resolved/ ? Maybe > SetLinkDNS for the bridge interface? But you would also need to call > SetLinkDomains to ensure queries for a particular domain go to the > bridge interface (otherwise, nothing will). You could theoretically, > for instance, claim a .libvirt domain, then resolve "f33.libvirt" to > the VM's IP? > My use case is, I have the bridge 'laptop-lab' created with libvirt: laptop-lab 23997a64-b242-4a32-8ef6-4e0c36e16598 Previously, I used dns=dnsmasq in NetworkManager to indicate that the domain 'laptop.lab' resolves through this dnsmasq instance: /etc/NetworkManager/conf.d/00-use-dnsmasq.conf: [main] dns=dnsmasq /etc/NetworkManager/dnsmasq.d/laptop_lab.conf: server=/laptop.lab/192.168.100.1 I'd like to do something similar in systemd-resolved, and indeed this works fine: # resolvectl dns laptop-lab 192.168.100.1 # resolvectl domain laptop-lab laptop.lab But this configuration is lost after a reboot, and the configuration file is not expressive enough to indicate a dns and domain on a link. A way to do this automatically would be greatly appreciated, but I guess it doesn't exist at the moment. ___ 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
