Re: Self Introduction: Attila Kovacs
Il 22/05/24 6:13 PM, Attila Kovacs ha scritto: > Hi! > Hi Attila and welcome to the Fedora community! I myself am just an amateur astronomer trying to keep up packaging some useful software in Fedora, but I look forward in seeing SuperNOVAS packaged in our repositories. Don't hesitate to ask me if you have any question about packaging, I'm not a sponsor, but I can do a review of the package submission when ready. Mattia -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: oneapi-level-zero requires cloned spdlog-populate
Hey, just FYI, this was/is in progress by me, you could've checked upstream PRs: https://github.com/oneapi-src/level-zero/pull/149 and https://github.com/oneapi-src/level-zero/pull/150 . It was pending on https://src.fedoraproject.org/rpms/spdlog/pull-request/2 that was merged pretty recently. On Thu, May 23, 2024 at 4:46 AM Luya Tshimbalanga wrote: > Thanks, report filed on > https://github.com/oneapi-src/level-zero/issues/146. > > -- > Luya Tshimbalanga > Fedora Design Team > Fedora Design Suite maintainer > > -- > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > -- Best regards / S pozdravem, František Zatloukal Senior Quality Engineer Red Hat -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: small logic issue with system upgrades
> Am 23.05.2024 um 00:29 schrieb Marius Schwarz : > > Am 22.05.24 um 17:48 schrieb Alexander Sosedkin: >> On Wed, May 22, 2024 at 4:34 PM Marius Schwarz >> wrote: >> >>> Were you following the steps outlined in >>> https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-offline ? >>> >>> > > I'm under the impression, there is a small misunderstanding here: The upgrade > worked as it should for the 23th time in a row :D So, your server is running with F39 now? > It's just, that > while < the upgrade process was running, there was the > risk, that it or the connection fails, and in that case, there would not have > been a way to fix it remotely because of the mismatch of openssl and openssh > versions. (yes of course, an IPMI would be a way ). Unfortunately, I don’t understand, what exactly the problem is. If you follow the procedure as described in the Quick Docs document mentioned above, there is no network connection while the actual update process is running. And even if there was one, you have no way of intervening in the process. Probably I overlook something in your mail. But I would really like to understand your issue. We are always looking to improve Fedora Server. And I’m running a bunch of servers in a remote data center, too, w/o access to the console (but a temporary KVM in case of emergency). So I have the update adventure every 6 months as well. > Yes, this is only relevant for remote-upgrades, but Fedora is a very good > server distribution and widely spread ;) Wholehearted Agreement :-) -- Peter Boy https://fedoraproject.org/wiki/User:Pboy p...@fedoraproject.org Timezone: CET (UTC+1) / CEST (UTC+2) Fedora Server Edition Working Group member Fedora Docs team contributor and board member Java developer and enthusiast -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: oneapi-level-zero requires cloned spdlog-populate
Thanks, report filed on https://github.com/oneapi-src/level-zero/issues/146. -- Luya Tshimbalanga Fedora Design Team Fedora Design Suite maintainer -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Need help with likely template instantiation errors
We're trying to update vxl but running into some errors: /usr/bin/ld: ../../../../../../lib/libbbas_pro.so.3.5.0.0: undefined reference to `brdb_value_t > >::assign(brdb_value const&)' /usr/bin/ld: ../../../../../../lib/libbbas_pro.so.3.5.0.0: undefined reference to `brdb_value_t > >::eq(brdb_value const&) const' /usr/bin/ld: ../../../../../../lib/libbbas_pro.so.3.5.0.0: undefined reference to `brdb_value_t > >::b_read_value(vsl_b_istream&)' /usr/bin/ld: ../../../../../../lib/libbbas_pro.so.3.5.0.0: undefined reference to `brdb_value_t > >::get_type_string[abi:cxx11]()' /usr/bin/ld: ../../../../../../lib/libbbas_pro.so.3.5.0.0: undefined reference to `brdb_value_t > >::b_write_value(vsl_b_ostream&) const' /usr/bin/ld: ../../../../../../lib/libbbas_pro.so.3.5.0.0: undefined reference to `brdb_value_t > >::lt(brdb_value const&) const' This is outside of my C++ comfort level. Any help would be greatly appreciated. PR is here: https://src.fedoraproject.org/rpms/vxl/pull-request/2 -- Orion Poplawski he/him/his - surely the least important thing about me IT Systems Manager 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane or...@nwra.com Boulder, CO 80301 https://www.nwra.com/ smime.p7s Description: S/MIME Cryptographic Signature -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: oneapi-level-zero requires cloned spdlog-populate
On 5/22/24 18:02, Luya Tshimbalanga wrote: Hello team, Upstream made a change that requires cloning a sub-directory spdlog-populate leading to a failure to build. What will be an alternative to address that issue? Scratch build result on http://koji.fedoraproject.org/koji/taskinfo?taskID=118027071 Thanks in advance References: [1] https://src.fedoraproject.org/rpms/oneapi-level-zero [2] https://github.com/oneapi-src/level-zero/blob/master/CMakeLists.txt -- Luya Tshimbalanga Fedora Design Team Fedora Design Suite maintainer I've pushed a quick hack here: https://src.fedoraproject.org/rpms/oneapi-level-zero/pull-request/1 But upstream really should be urged to make this configurable. -- Orion Poplawski he/him/his - surely the least important thing about me IT Systems Manager 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane or...@nwra.com Boulder, CO 80301 https://www.nwra.com/ smime.p7s Description: S/MIME Cryptographic Signature -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
oneapi-level-zero requires cloned spdlog-populate
Hello team, Upstream made a change that requires cloning a sub-directory spdlog-populate leading to a failure to build. What will be an alternative to address that issue? Scratch build result on http://koji.fedoraproject.org/koji/taskinfo?taskID=118027071 Thanks in advance References: [1] https://src.fedoraproject.org/rpms/oneapi-level-zero [2] https://github.com/oneapi-src/level-zero/blob/master/CMakeLists.txt -- Luya Tshimbalanga Fedora Design Team Fedora Design Suite maintainer -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: small logic issue with system upgrades
On 5/22/24 3:29 PM, Marius Schwarz wrote: Am 22.05.24 um 17:48 schrieb Alexander Sosedkin: On Wed, May 22, 2024 at 4:34 PM Marius Schwarz wrote: Were you following the steps outlined in https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-offline ? I'm under the impression, there is a small misunderstanding here: The upgrade worked as it should for the 23th time in a row :D It's just, that > while < the upgrade process was running, there was the risk, that it or the connection fails, and in that case, there would not have been a way to fix it remotely because of the mismatch of openssl and openssh versions. (yes of course, an IPMI would be a way ). The risk that this happens can be shrunken immense, if openssh and openssl would be updated in direct serial order. You shouldn't be doing release upgrades like this anyway and there is not likely to be any work to reduce that potential issue. You should be using the system-upgrade method to upgrade releases which would avoid this completely. -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: small logic issue with system upgrades
Am 22.05.24 um 17:48 schrieb Alexander Sosedkin: On Wed, May 22, 2024 at 4:34 PM Marius Schwarz wrote: Were you following the steps outlined in https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-offline ? I'm under the impression, there is a small misunderstanding here: The upgrade worked as it should for the 23th time in a row :D It's just, that > while < the upgrade process was running, there was the risk, that it or the connection fails, and in that case, there would not have been a way to fix it remotely because of the mismatch of openssl and openssh versions. (yes of course, an IPMI would be a way ). The risk that this happens can be shrunken immense, if openssh and openssl would be updated in direct serial order. Yes, this is only relevant for remote-upgrades, but Fedora is a very good server distribution and widely spread ;) best regards, Marius Schwarz-- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: LLVM Packaging Ideas for Fedora 41
Vitaly Zaitsev via devel writes:
> On 22/05/2024 01:45, Tom Stellard wrote:
>> I looked in the iwyu source, and it's not using ${LLVM_LIBRARY_DIR}
>> correctly.
>> That variable points to where the libraries are installed, but iwyu is
>> using it to look
>> up the resource directory. iwyu should be using `clang
>> -print-resource-dir`
>> instead.
>
> Can you submit a pull request with a fix to upstream?
Done!
https://github.com/include-what-you-use/include-what-you-use/pull/1542
--
Tulio Magno
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
go apps / imports of stlib / does rpm as a mechanisms to provide such infos
IIRC, go applications with vendored modules/go-packages, if rpm-packaged carefully, do provide go-package dependency information via the rpm-provides tag for vendored packages. I wonder about "imports" of golang's stdlib go-packages. Usecase: go.dev releases a new golang version because an included package (e.g. net) has a critical flaw. A local app does not use that package and therefore does not need to be recompiled. How could I enumerate the rpm packages that need to be recompiled? Would this info generally be desirable? Maybe with help of go-rpm-macros? go list -json | jq .Imports shows such imports, when executed in the source/building directory. rpm-provides tag example: stdlib: bundled(golang(net)) = go1.21.9 vs module: bundled(golang(golang.org/x/net)) = 0.24.0 -- Leon -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Self Introduction: Attila Kovacs
On 22/05/2024 19.13, Attila Kovacs wrote: > Hi! > > I'm an astrophysicist / developer (nowadays more developer than > astrohysicist). I mostly write code in C and Java (for work and for personal > stuff). My main job is maintaining and developing software for the > Smithsonian's Submillimeter Array (SMA) observatory atop Maunakea. Some of > the software we develop can have wider application. Hence I'm starting to > spin off and open-source some of the more universally applicable bits of our > code. > > For example, at the SMA (and the MIT Haystack 37-m telescope) we use a > customized version of the Naval Observatory Vector Astrometry Software > (NOVAS) C 3.1. I have fixed a bunch of bugs in it, cleaned up the API, added > browseable documentation, and extended its functionality with new features. > My goal is to make it easier and safer to use it, while promoting best > practices also. This is is how the SuperNOVAS package on GitHub was born, > somewhat recently. It is a light-weight high-precision C/C++ astrometry > library capable of sub-microarsecond position calculations. Thus is may serve > as a component for running observatories (or your backyard telescope), or a > very precise planetarium program, or any other astronomy software that needs > to calculate positions of celestial objects with accuracy. The source code > and releases are hosted at: > > https://github.com/Smithsonian/SuperNOVAS > > And you can find more information, including the online documentation at the > project pages at: > > https://smithsonian.github.io/SuperNOVAS/ > > Its second release (v1.0.1) just got published some two weeks ago. (Yay!) > > Next I would like to package it for Fedora, not the least because the Debian > folks have expressed interest -- which is all great, but I myself have been a > Fedora / RedHatter since '97, so I'd look forward to a Fedora package ever > more so. I am hoping to find a sponsor too. If I understand correctly that's > a separate step from the self intro here, but if you would want to help guide > me anyway, I'd very much welcome it any time. Welcome to Fedora. Consider joining the Astronomy and Scitech SIGS: https://fedoraproject.org/wiki/Category:Astronomy_SIG https://fedoraproject.org/wiki/Category:SciTech_SIG > > I look forward to working with you and learning from you. > > cheers, > > -- Attila. > -- -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F41 Change Proposal - Reproducible Package Builds (System-Wide)
On Wed, May 22, 2024 at 09:06:07AM +0200, Vitaly Zaitsev via devel wrote: > On 17/04/2024 09:20, Zbigniew Jędrzejewski-Szmek wrote: > > In some ways, that'd be nice, because we wouldn't have to install > > additional tools in the buildroot. But OTOH, those tools are rather > > small and bash/find/etc probably need to be installed anyway. > > It doesn't seem to work properly without the marshalparser Python package > installed: > > + /usr/bin/add-determinism --brp -j48 > /builddir/build/BUILDROOT/nheko-0.11.3-11.fc41.x86_64 > Cannot initialize handler pyc: ModuleNotFoundError: No module named > 'marshalparser' Yes. The plan is to pull in the marshalparser module from python3-devel (conditionalized on python not being bootstrapped). The lack of the marshalparser module means that the program doesn't handle .pyc files, but otherwise works. > Also, is it possible to suppress these "Bye!" messages? Yeah, I left in the debugging message to have more clarity if things are working. They'll be gone in the next version. Zbyszek -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Self Introduction: Attila Kovacs
Hi! I'm an astrophysicist / developer (nowadays more developer than astrohysicist). I mostly write code in C and Java (for work and for personal stuff). My main job is maintaining and developing software for the Smithsonian's Submillimeter Array (SMA) observatory atop Maunakea. Some of the software we develop can have wider application. Hence I'm starting to spin off and open-source some of the more universally applicable bits of our code. For example, at the SMA (and the MIT Haystack 37-m telescope) we use a customized version of the Naval Observatory Vector Astrometry Software (NOVAS) C 3.1. I have fixed a bunch of bugs in it, cleaned up the API, added browseable documentation, and extended its functionality with new features. My goal is to make it easier and safer to use it, while promoting best practices also. This is is how the SuperNOVAS package on GitHub was born, somewhat recently. It is a light-weight high-precision C/C++ astrometry library capable of sub-microarsecond position calculations. Thus is may serve as a component for running observatories (or your backyard telescope), or a very precise planetarium program, or any other astronomy software that needs to calculate positions of celestial objects with accuracy. The source code and releases are hosted at: https://github.com/Smithsonian/SuperNOVAS And you can find more information, including the online documentation at the project pages at: https://smithsonian.github.io/SuperNOVAS/ Its second release (v1.0.1) just got published some two weeks ago. (Yay!) Next I would like to package it for Fedora, not the least because the Debian folks have expressed interest -- which is all great, but I myself have been a Fedora / RedHatter since '97, so I'd look forward to a Fedora package ever more so. I am hoping to find a sponsor too. If I understand correctly that's a separate step from the self intro here, but if you would want to help guide me anyway, I'd very much welcome it any time. I look forward to working with you and learning from you. cheers, -- Attila. -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: small logic issue with system upgrades
On Wed, May 22, 2024 at 4:34 PM Marius Schwarz wrote: > ATM I'm upgrading a remote server from F38 to F39 via SSH login. > > The bash runs a screen, so if ssh or the network dies, the upgrade can > continue. > > I just noticed that even if it keeps running, it's useless because > openssl und openssh do not get upgraded after another. > > So, atm, the server has a sshd that says, that openssl is newer as the > required openssl version. It does not start it nor can the running sshd, > that runs the upgrade connection, fork a new instance. In other words: > no login possible to rescue or recover the upgrade session remotely. > > if that wasn't enough, imapd and other services do also refuse to work > due to openssl version mismatch. > > I can imagine, that this class of problems is not soley with openssl. > > O== Changerequest > > find a way to cluster packages close together that need openssl, to keep > the risk of an inaccessible server small. > > i.e. by grouping the packages i.e. "network" "office" etc. Were you following the steps outlined in https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-offline ? -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Fedora Workstation 40 aarch64 download -- How to run Live CD installer?
https://ausil.fedorapeople.org/Fedora-Workstation-Live-aarch64-40-20240417.n.0.iso is the last ISO built for a nightly compose for F40. It gives you the prerelease warning but is very close to GA. Dennis On Wed, May 22, 2024 at 7:40 AM Adam Williamson wrote: > > On Tue, 2024-05-21 at 20:15 -0400, Neal Gompa wrote: > > On Tue, May 21, 2024 at 8:11 PM Samuel Sieb wrote: > > > > > > On 5/21/24 5:08 PM, Brian Masney wrote: > > > > I want to put Fedora 40 on my Lenovo Thinkpad x13s laptop, which is an > > > > aarch64-based laptop with a Qualcomm SoC. I downloaded the Fedora raw > > > > image from [1], and I can boot from USB using the directions at [2]. > > > > All of the other supported architectures have an ISO available, > > > > however aarch64 only has a raw image available. > > > > > > > > In the past, I would dd the Fedora image directly to my nvme drive, > > > > however this time I'd like to go through the installer so that I can > > > > easily setup LUKS encryption on my nvme drive through the installer. > > > > The raw image doesn't have the installer, and I didn't have luck > > > > installing the anaconda-livecd package. > > > > > > > > Is there a Live ISO available for aarch64 anywhere with an installer? > > > > > > https://dl.fedoraproject.org/pub/fedora/linux/releases/40/Workstation/aarch64/iso/ > > > > That is the experimental osbuild one. There is no official ISO, as it > > failed to build. It affected Fedora KDE and other variants too. :( > > Yes, that. > > Beyond that, Dennis Gilmore has been poking at Fedora on the x13s for a > bit, and has run into some issues you might want to be aware of. See > https://bugzilla.redhat.com/show_bug.cgi?id=2254940 and > https://bugzilla.redhat.com/show_bug.cgi?id=2264794 . > -- > Adam Williamson (he/him/his) > Fedora QA > Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org > https://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 > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Fedora Elections - Voting is now open!
On 22-05-2024 16:32, Vít Ondruch wrote: The same link works for me and other people are claiming the badge. That leads me to believe some local cache or the like might be getting in the way. I don't have access to the logs. That makes my guesses as good as anyone's. I have created new profile just due to this and I claimed the badge, but it does not work with my current profile. I am not going to delete caches and what not due to this. IOW there is some bug which would be nice to fix. Heh, trying back in my original profile, first I got again the error. Then I got "500 internal server error" and now the links proceeds to badges with "You already have i-voted:-fedora-40 badge". Next attempt "500 internal server error". If you want to pursue this, I suggest you file a bug against Tharir [1]. So far, all people who have claimed at some point that the link had expired when other people were happily claiming the badge, were able to resolve it either by clearing their cache or by (temporarily) using another browser. The 500 error is unrelated as far as I'm aware. I've seen that myself a few times now when simply refreshing some Badges page. It's usually short lived. Last but not least, since you managed to claim the badge, it's expected that you see "You already have i-voted:-fedora-40 badge". You can only claim it once. [1] https://github.com/fedora-infra/tahrir/issues -- Sandro -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
small logic issue with system upgrades
Hi, ATM I'm upgrading a remote server from F38 to F39 via SSH login. The bash runs a screen, so if ssh or the network dies, the upgrade can continue. I just noticed that even if it keeps running, it's useless because openssl und openssh do not get upgraded after another. So, atm, the server has a sshd that says, that openssl is newer as the required openssl version. It does not start it nor can the running sshd, that runs the upgrade connection, fork a new instance. In other words: no login possible to rescue or recover the upgrade session remotely. if that wasn't enough, imapd and other services do also refuse to work due to openssl version mismatch. I can imagine, that this class of problems is not soley with openssl. O== Changerequest find a way to cluster packages close together that need openssl, to keep the risk of an inaccessible server small. i.e. by grouping the packages i.e. "network" "office" etc. best regards, Marius Schwarz -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Fedora Elections - Voting is now open!
Dne 22. 05. 24 v 16:28 Vít Ondruch napsal(a): Dne 21. 05. 24 v 16:27 Sandro napsal(a): On 21-05-2024 16:22, Steven A. Falco wrote: On 5/21/24 10:17 AM, Sandro wrote: On 21-05-2024 15:47, Vít Ondruch wrote: Dne 21. 05. 24 v 15:45 Vít Ondruch napsal(a): Dne 21. 05. 24 v 15:31 Steven A. Falco napsal(a): I'm getting the "410 Gone" message, too. Tried multiple times since yesterday with no luck. Yes, this is the message. + ~~~ This resource is no longer available. No forwarding address is given. That invitation is expired. ~~~ That should no longer be the case. Which election precisely did you follow the link from? Maybe we missed updating one of them. That said, I still see other people claiming it. Could it be that you just need to fully refresh the page? I'll have a look at the links meanwhile. Maybe I spot something. I just tried from https://elections.fedoraproject.org/vote/fedora%20mindshare%20election%20for%20f40 Badge link: https://badges.fedoraproject.org/invitations/716f01bd050fefd9a0647ae956af2b13/claim Error message: 410 Gone This resource is no longer available. No forwarding address is given. That invitation is expired. -- The same link works for me and other people are claiming the badge. That leads me to believe some local cache or the like might be getting in the way. I don't have access to the logs. That makes my guesses as good as anyone's. I have created new profile just due to this and I claimed the badge, but it does not work with my current profile. I am not going to delete caches and what not due to this. IOW there is some bug which would be nice to fix. Heh, trying back in my original profile, first I got again the error. Then I got "500 internal server error" and now the links proceeds to badges with "You already have i-voted:-fedora-40 badge". Next attempt "500 internal server error". Vít Vít However, now the link is in the open, we might have to change it again and invalidate the link you posted. It's not meant to be out in the open. Btw, it seems you've got the badge after all. I'm looking at the front page as I type. -- Sandro -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue OpenPGP_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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Fedora Elections - Voting is now open!
Dne 21. 05. 24 v 16:27 Sandro napsal(a): On 21-05-2024 16:22, Steven A. Falco wrote: On 5/21/24 10:17 AM, Sandro wrote: On 21-05-2024 15:47, Vít Ondruch wrote: Dne 21. 05. 24 v 15:45 Vít Ondruch napsal(a): Dne 21. 05. 24 v 15:31 Steven A. Falco napsal(a): I'm getting the "410 Gone" message, too. Tried multiple times since yesterday with no luck. Yes, this is the message. + ~~~ This resource is no longer available. No forwarding address is given. That invitation is expired. ~~~ That should no longer be the case. Which election precisely did you follow the link from? Maybe we missed updating one of them. That said, I still see other people claiming it. Could it be that you just need to fully refresh the page? I'll have a look at the links meanwhile. Maybe I spot something. I just tried from https://elections.fedoraproject.org/vote/fedora%20mindshare%20election%20for%20f40 Badge link: https://badges.fedoraproject.org/invitations/716f01bd050fefd9a0647ae956af2b13/claim Error message: 410 Gone This resource is no longer available. No forwarding address is given. That invitation is expired. -- The same link works for me and other people are claiming the badge. That leads me to believe some local cache or the like might be getting in the way. I don't have access to the logs. That makes my guesses as good as anyone's. I have created new profile just due to this and I claimed the badge, but it does not work with my current profile. I am not going to delete caches and what not due to this. IOW there is some bug which would be nice to fix. Vít However, now the link is in the open, we might have to change it again and invalidate the link you posted. It's not meant to be out in the open. Btw, it seems you've got the badge after all. I'm looking at the front page as I type. -- Sandro -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue OpenPGP_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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Intention to unretire and rename pyftpdlib
On 22-05-2024 12:12, Peter Robinson wrote: On Tue, 21 May 2024 at 23:51, Sandro wrote: Hi, I intend to unretire pyftpdlib [1] and rename the base package to python-pyftpdlib in line with current Python Packaging Guidelines. The Why unretire? Why not just do a new package given the new name? I was probably overthinking this. In practice it will turn out to be a new package submission indeed. Moreover, the last remaining active branch of the retired package (F38) is now EOL. I've submitted the review [1] without any Obsoletes. [1] https://bugzilla.redhat.com/show_bug.cgi?id=2282430 -- Sandro -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Intention to unretire and rename pyftpdlib
On Tue, 21 May 2024 at 23:51, Sandro wrote: > > Hi, > > I intend to unretire pyftpdlib [1] and rename the base package to > python-pyftpdlib in line with current Python Packaging Guidelines. The Why unretire? Why not just do a new package given the new name? > package has been retired for more than eight weeks. So it will require a > re-review. > > Since only the base package (SRPM) will be renamed, I'm wondering if it > needs any Obsoletes and/or Provides. The name of the sub package will > remain unchanged: python3-pyftpdlib. > I don't think it's needed. But I'd like to hear from more experienced folks. > > I need pyftpdlib as a dependency for another package I've already > prepared. It appears to be still maintained, but was retired due to an > FTI bug [2] not being attended to. > > [1] https://src.fedoraproject.org/rpms/pyftpdlib > [2] https://bugzilla.redhat.com/show_bug.cgi?id=2220082 > > Cheers, > > -- > Sandro > FAS: gui1ty > Matrix:Penguinpee > Elsewhere: [Pp]enguinpee > -- > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora rawhide compose report: 20240522.n.0 changes
OLD: Fedora-Rawhide-20240521.n.0 NEW: Fedora-Rawhide-20240522.n.0 = SUMMARY = Added images:0 Dropped images: 1 Added packages: 6 Dropped packages:0 Upgraded packages: 107 Downgraded packages: 0 Size of added packages: 6.99 MiB Size of dropped packages:0 B Size of upgraded packages: 3.16 GiB Size of downgraded packages: 0 B Size change of upgraded packages: 68.86 MiB Size change of downgraded packages: 0 B = ADDED IMAGES = = DROPPED IMAGES = Image: Workstation live aarch64 Path: Workstation/aarch64/iso/Fedora-Workstation-Live-aarch64-Rawhide-20240521.n.0.iso = ADDED PACKAGES = Package: intel-vpl-gpu-rt-24.2.2-2.fc41 Summary: Intel Video Processing Library (Intel VPL) GPU Runtime RPMs:intel-vpl-gpu-rt intel-vpl-gpu-rt-devel Size:2.30 MiB Package: makedumpfile-1.7.5-10.fc41 Summary: make a small dumpfile of kdump RPMs:makedumpfile Size:1.17 MiB Package: php-psr-http-client-1.0.3-1.fc41 Summary: Common interface for HTTP clients RPMs:php-psr-http-client Size:11.31 KiB Package: python-python-fcl-0.7.0.6-4.fc41 Summary: Python bindings for the Flexible Collision Library RPMs:python3-python-fcl Size:3.45 MiB Package: rust-lockfree-object-pool-0.1.6-1.fc41 Summary: Thread-safe object pool with automatic return and attach/detach semantics RPMs:rust-lockfree-object-pool+default-devel rust-lockfree-object-pool-devel Size:33.85 KiB Package: rust-reqwest-retry-0.5.0-1.fc41 Summary: Retry middleware for reqwest RPMs:rust-reqwest-retry+default-devel rust-reqwest-retry-devel Size:31.48 KiB = DROPPED PACKAGES = = UPGRADED PACKAGES = Package: CuraEngine-1:5.4.0-5.fc41 Old package: CuraEngine-1:5.4.0-4.fc40 Summary: Engine for processing 3D models into G-code instructions for 3D printers RPMs: CuraEngine Size: 4.53 MiB Size change: -17.09 KiB Changelog: * Tue May 21 2024 Franti??ek Zatloukal - 1:5.4.0-5 - Rebuilt for spdlog 1.14.1 Package: algol68g-3.5.2-1.fc41 Old package: algol68g-3.5.1-2.fc41 Summary: Algol 68 Genie compiler-interpreter RPMs: algol68g Size: 2.58 MiB Size change: 3.66 KiB Changelog: * Tue May 21 2024 Oleg Girko - 3.5.2-1 - Update to 3.5.2 Package: alizams-1.9.10-1.fc41 Old package: alizams-1.9.9-2.fc41 Summary: Aliza MS DICOM Viewer RPMs: alizams Size: 4.16 MiB Size change: -31.86 KiB Changelog: * Tue May 21 2024 Alessio - 1.9.9-3 - Update to 1.9.10 * Tue May 21 2024 Alessio - 1.9.10-1 - Update to 1.9.10 Package: aspell-12:0.60.8.1-1.fc41 Old package: aspell-12:0.60.8-14.fc40 Summary: Spell checker RPMs: aspell aspell-devel Size: 3.87 MiB Size change: 104.05 KiB Changelog: * Mon May 20 2024 Peter Oliver - 12:0.60.8.1-1 - Update to version 0.60.8.1 Package: bear-3.1.3-7.fc41 Old package: bear-3.1.3-5.fc40 Summary: Tool that generates a compilation database for clang tooling RPMs: bear Size: 2.10 MiB Size change: -891 B Changelog: * Sat Feb 24 2024 David Abdurachmanov - 3.1.3-6 - Properly check valgrind arches * Tue May 21 2024 Franti??ek Zatloukal - 3.1.3-7 - Rebuilt for spdlog 1.14.1 Package: ceph-2:18.2.3-3.fc41 Old package: ceph-2:18.2.3-2.fc41 Summary: User space components of the Ceph file system RPMs: ceph ceph-base ceph-common ceph-exporter ceph-fuse ceph-grafana-dashboards ceph-immutable-object-cache ceph-mds ceph-mgr ceph-mgr-cephadm ceph-mgr-dashboard ceph-mgr-diskprediction-local ceph-mgr-k8sevents ceph-mgr-modules-core ceph-mgr-rook ceph-mib ceph-mon ceph-node-proxy ceph-osd ceph-prometheus-alerts ceph-radosgw ceph-resource-agents ceph-selinux ceph-test ceph-volume cephadm cephfs-mirror cephfs-shell cephfs-top libcephfs-devel libcephfs2 libcephsqlite libcephsqlite-devel librados-devel librados2 libradospp-devel libradosstriper-devel libradosstriper1 librbd-devel librbd1 librgw-devel librgw2 python3-ceph-argparse python3-ceph-common python3-cephfs python3-rados python3-rbd python3-rgw rados-objclass-devel rbd-fuse rbd-mirror rbd-nbd Size: 473.24 MiB Size change: -3.85 MiB Changelog: * Tue May 21 2024 Kaleb S. KEITHLEY - 2:18.2.3-3 - ceph-18.2.3, enable system boost Package: check-0.15.2-13.fc41 Old package: check-0.15.2-12.fc40 Summary: A unit test framework for C RPMs: check check-checkmk check-devel check-static mingw32-check mingw64-check Size: 1.09 MiB Size change: -1.41 KiB Changelog: * Tue May 21 2024 Jerry James - 0.15.2-13 - Fix check-devel for cmake users (rhbz#2161231) - Simplify conditional logic for mingw Package: clang-18.1.6-3.fc41 Old package: clang-18.1.4-3.fc41 Summary: A C language family front-end for LLVM RPMs: clang clang-analyzer clang-devel clang-libs clang-resource-filesystem clang-tools-extra clang-tools-extra-devel git-clang-format
[Test-Announce] [Rawhide Test Day] Podman 5.1 Test Day 2024-05-23
Hey Folks! We will be testing Fedora 41 with the new update in Podman 5.1. To ensure a smooth transition, the Podman team and the Quality team of Fedora have decided to host a test day[1]. The idea is for users to test Podman 5.1 on a Fedora Rawhide machine and submit results in the Test Day App[2]. If you have spare cycles or use Podman as a daily driver, it will be great to have some folks try out and report bugs right away. We will want more Karmas on[3] and any following builds for Podman 5.1 [1] https://fedoraproject.org/wiki/Test_Day:2024-05-23_Podman_5.1 [2] https://testdays.fedoraproject.org/events/188 [3] https://bodhi.fedoraproject.org/updates/FEDORA-2024-7d9e4ee012 -- //sumantro Fedora QE TRIED AND PERSONALLY TESTED, ERGO TRUSTED -- ___ test-announce mailing list -- test-annou...@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-annou...@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Schedule for Monday's FESCo Meeting (2024-05-20)
On 21/05/2024 22:59, Miro Hrončok wrote: I am a tad sad that this was approved by FESCo without being first discussed with the wider community. We have another similar issue: https://pagure.io/fesco/issue/3205 This was also not discussed. Intel wants to include pre-built blobs to the repository: From an end user POV it would have no functional benefit either, since distros would not be permitted to make any source changes. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Announcing spdlog soversion bump
On 21/05/2024 15:30, Vitaly Zaitsev wrote: spdlog 1.14.1 will include a soversion bump from .1.12 to .1.14. Completed and pushed to Rawhide. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F41 Change Proposal - Reproducible Package Builds (System-Wide)
On 17/04/2024 09:20, Zbigniew Jędrzejewski-Szmek wrote:
In some ways, that'd be nice, because we wouldn't have to install
additional tools in the buildroot. But OTOH, those tools are rather
small and bash/find/etc probably need to be installed anyway.
It doesn't seem to work properly without the marshalparser Python
package installed:
+ /usr/bin/add-determinism --brp -j48
/builddir/build/BUILDROOT/nheko-0.11.3-11.fc41.x86_64
Cannot initialize handler pyc: ModuleNotFoundError: No module named
'marshalparser'
[src/multiprocess.rs:66:9] &cmd = Command {
program: "/usr/bin/add-determinism",
args: [
"/usr/bin/add-determinism",
"--socket",
"3",
"--brp",
"--handler",
"ar,jar,javadoc",
],
env: CommandEnv {
clear: false,
vars: {
"SOURCE_DATE_EPOCH": Some(
"1716249600",
),
},
},
create_pidfd: false,
}
Bye!
Bye!
Bye!
Bye!
Also, is it possible to suppress these "Bye!" messages?
--
Sincerely,
Vitaly Zaitsev (vit...@easycoding.org)
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
