Next Open NeuroFedora Meeting: Monday, 20 May 2024 (today) at 13:00 UTC
Hello everyone, Please join us at the next Open NeuroFedora team meeting on Monday, 20 May at 13:00 UTC. The meeting is a public meeting, and open for everyone to attend. You can join us over on Matrix in the Fedora Meeting channel: https://matrix.to/#/#meeting:fedoraproject.org You can use this link to see the local time for the meeting: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Open+NeuroFedora+Meeting=20240520T13=1440=1 or you can use this command in a terminal: $ date -d 'Monday, May 20, 2024 13:00 UTC' The meeting will be chaired by @ankursinha. The agenda for the meeting is: - New introductions and roll call. - Tasks from last meeting: https://meetbot.fedoraproject.org/latest/neurofedora - Open Pagure tickets: https://pagure.io/neuro-sig/NeuroFedora/issues?status=Open=S%3A+Next+meeting - Package health check: https://packager-dashboard.fedoraproject.org/dashboard?groups=neuro-sig - Open package reviews check: https://bugzilla.redhat.com/show_bug.cgi?id=fedora-neuro - CompNeuro lab compose status check for F40: https://koji.fedoraproject.org/koji/packageinfo?packageID=30691 - Neuroscience query of the week - Next meeting day, and chair. - Open floor. We hope to see you there! The meeting announcement is also posted on the NeuroFedora blog here: https://neuroblog.fedoraproject.org/2024/05/20/next-open-neurofedora-meeting-20-may-1300-utc.html You can learn more about NeuroFedora here: https://neuro.fedoraproject.org Cheers, -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Updating Taskwarrior to v3
On Tue, Apr 16, 2024 00:40:33 GMT, Randy Barlow via devel wrote: > As a tangent on this thread, it would be cool if there were a mechanism in > dnf to tell users when an upgrade needs special attention/instructions. > Another example like this is postgresql updates, which also require manual > intervention. +1 Yeh, that'd be great, but not really sure how it'd be done. -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Updating Taskwarrior to v3
On Mon, Apr 15, 2024 16:40:50 GMT, Michel Lind wrote: > Hi Ankur, Hi Michel, Sorry, I missed your reply before. > > What you can probably do now is to introduce the compat package > *first* into all stable releases - and make it obsolete the task > package at the current NEVRA. > Then for Rawhide, you can update the task package to version 3 - that > way current users will get moved to task2 seamlessly (probably make > the update suggest they log out, just in case), and when task v3 is > packaged, they can then export their current database using the > existing task2 and import it after reinstalling task? Just trying to wrap my head around this :) - task2 obsoletes task <= 2.whatever, in F38--40. So, when users update, they get task2. Cool, that sounds good. - task >= 3 then lands in rawhide (F41), and users will have to install it explicitly. That does solve the issue of taskv2 being upgraded to taskv3 without the users' knowledge. Users still have to manually export/import, but I don't see a way around that at all. Additionally, for those on stable releases that do want to update to taskv3, I can maybe provide a COPR for F<41. I think I'll still announce it as a self contained change for more visibility. Thanks for that, I think that is the best way to go. -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Next Open NeuroFedora Meeting: Monday, 22 April 2024 (today) at 13:00 UTC
Hello everyone, Please join us at the next Open NeuroFedora team meeting on Monday, 22 April at 13:00 UTC. The meeting is a public meeting, and open for everyone to attend. You can join us over on Matrix in the Fedora Meeting channel: https://matrix.to/#/#meeting:fedoraproject.org You can use this link to see the local time for the meeting: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Open+NeuroFedora+Meeting=20240422T13=1440=1 or you can use this command in a terminal: $ date -d 'Monday, April 22, 2024 13:00 UTC' The meeting will be chaired by @ankursinha. The agenda for the meeting is: - New introductions and roll call. - Tasks from last meeting: https://meetbot.fedoraproject.org/latest/neurofedora - Open Pagure tickets: https://pagure.io/neuro-sig/NeuroFedora/issues?status=Open=S%3A+Next+meeting - Package health check: https://packager-dashboard.fedoraproject.org/dashboard?groups=neuro-sig - Open package reviews check: https://bugzilla.redhat.com/show_bug.cgi?id=fedora-neuro - CompNeuro lab compose status check for F40: https://koji.fedoraproject.org/koji/packageinfo?packageID=30691 - Neuroscience query of the week - Next meeting day, and chair. - Open floor. We hope to see you there! The meeting announcement is also posted on the NeuroFedora blog here: https://neuroblog.fedoraproject.org/2024/04/22/next-open-neurofedora-meeting-22-april-1300-utc.html You can learn more about NeuroFedora here: https://neuro.fedoraproject.org Cheers, -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Updating Taskwarrior to v3
On Mon, Apr 15, 2024 14:18:59 +0200, Jos Vos wrote: > On Mon, Apr 15, 2024 at 12:15:55PM +0100, Ankur Sinha wrote: > >Hrm, but the problem here is that a user that currently has the task >package installed (currently v2) will end up with v3 if I update the >task package to v3---which is something we'd like to avoid here. > > Just a side question: is this task v3 update planned to be distributed > *during* an OS lifecycle or only at the start of a new one (e.g. F41, > I assume it is too late for F40 now)? Are there any Fedora policies > for this kind of incompatible updates? The general policy is to not introduce backwards incompatible changes to stable releases: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#stable-releases I am thinking that the best way for this would be to announce it as a self-contained change so it'll land in rawhide (F41). In the meantime, I can perhaps keep a COPR repository for stable Fedora releases (F39/F40) for users that do want to use taskv3 already. https://docs.fedoraproject.org/en-US/program_management/changes_policy/#_self_contained_changes How does that sound? -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Updating Taskwarrior to v3
On Mon, Apr 15, 2024 12:50:48 +0200, Jos Vos wrote: > Hi, > > On Mon, Apr 15, 2024 at 11:04:22AM +0100, Ankur Sinha wrote: > >They are not designed to be installed in parallel, so task3 will >obsolete task. However, task3 will not provide the task package, so that >task will not be updated to task3 during normal upgrades. Users will >have to explicitly install task3. > > Being a happy taskwarrior user since years: > > Note that users do not always update (full) OS releases, but do > new installs while keeping (a.o.) /home. So, after installing > that new OS release, users will face the same issue. Furthermore, > if they are used to install "task", they will install the wrong > version, even if they may want to use the new version. > > The fact that v3 does *require* a v2 for exporting is of course a > bad thing, they should have added a export-v2 option or so. Will > the task v3 warn users if they detect old data? It won't use the old data format at all. After conversion, if one still has the old data files, it will show warnings: https://taskwarrior.org/docs/upgrade-3/ > > What is the idea? To temporarily provide both packages, v2 and v3, > that can not be installed together? > > About the naming / versioning part: this probably has happened > before with other packages, I am not aware of all the policies. > But I would think that having task2 for backwards compatibility > would be a better option. Can't task2 be built in such a way > that it can be installed alongside task (task v3). They both provide the same binary, but we could perhaps rename the task binary from taskv2 to task2. I've not looked at the rest of the package files yet to be able to say if they'll all require similar mangling to allow taskv2 and taskv3 to be installed in parallel. Theoretically, it should be doable. The issue with updating task to v3 and keeping task2 is that people that aren't aware of the change will end up with a non-functional task installation when the task package is upgraded. They'll have to downgrade to an older version of the package (or install task2), export their data, and then re-upgrade task to make it all work (and sync with taskserver won't work even then, of course). The documentation says "Before installing Taskwarrior 3, export all of your tasks". I haven't tested out what happens if one runs task3 without exporting the data---it shouldn't touch the old data files, but I don't know if it affects the import later. -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Updating Taskwarrior to v3
On Mon, Apr 15, 2024 12:53:06 +0200, Vít Ondruch wrote: > Our guidelines suggest that the "main" package should be unversioned, while > if needed, the "compat" packages should include version: > > https://docs.fedoraproject.org/en-US/packaging-guidelines/Naming/#multiple > > So if you want to introduce new package, then please introduce `task2` and > update the current `task` package to the most recent version. > Hrm, but the problem here is that a user that currently has the task package installed (currently v2) will end up with v3 if I update the task package to v3---which is something we'd like to avoid here. -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Updating Taskwarrior to v3
On Mon, Apr 15, 2024 09:41:05 -, Onuralp SEZER wrote: > > +1 to create task3 but the CLI command is "task". It either needs to > rename both like "task2,task3" or conflict old and new ones and > prevent installing both of them. They are not designed to be installed in parallel, so task3 will obsolete task. However, task3 will not provide the task package, so that task will not be updated to task3 during normal upgrades. Users will have to explicitly install task3. -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Updating Taskwarrior to v3
Hi folks, Taskwarrior has recently released version 3.x. While the command line remains the same, this version includes backwards incompatible changes: https://github.com/GothenburgBitFactory/taskwarrior/releases/tag/v3.0.0 https://taskwarrior.org/docs/upgrade-3/ - the user task database format has changed and requires users to manually migrate - it no longer supports taskserver for syncing The upgrade steps say that one must migrate their data base *before* installing task v3. So, this is clearly a backwards incompatible change that requires users intervention. What would be the best way of handling this? I didn't want to just update the package in Fedora. Instead I was thinking of packaging taskwarrior v3 as a new package, task3, that will obsolete the current package but not update it. -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
No Open NeuroFedora Meeting: Monday, 08 April 2024 (today) at 13:00 UTC
Hi folks, We won't have the NeuroFedora meeting today. We'll continue in 2 weeks as per our schedule. -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Why can't I add karlowich as co-maintainer of this package?
On Mon, Mar 18, 2024 09:57:58 +, Richard W.M. Jones wrote: > > https://src.fedoraproject.org/rpms/xnvme/adduser > > I try to add karlowich (https://accounts.fedoraproject.org/user/karlowich/) > but his name doesn't appear in the username field even though he's > in the packager group. Why? Have they logged out and back into src.fp.o? IIRC that's required for it to sync account info with FAS, so one has to do it once after being added to the packager group in FAS. -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Next Open NeuroFedora Meeting: 1300 UTC on Monday, 11 March, 2024 (today)
Hello everyone, Please join us at the next Open NeuroFedora team meeting on Monday 11 March at 1300UTC in the NeuroFedora channel on Matrix. The meeting is a public meeting, and open for everyone to attend. You can join us over: Matrix in the Fedora meeting channel: https://matrix.to/#/%23meeting:fedoraproject.org You can use this link to see the local time for the meeting: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Open+NeuroFedora+Meeting=20240311T13=%3A=1 or you can use this command in a terminal: $ date --date='TZ="UTC" 1300 Monday' The meeting will be chaired by @ankursinha. The agenda for the meeting is: - New introductions and roll call. - Tasks from last meeting: https://meetbot.fedoraproject.org/latest/neurofedora - Open Pagure tickets: https://pagure.io/neuro-sig/NeuroFedora/issues?status=Open=S%3A+Next+meeting - Package health check: https://packager-dashboard.fedoraproject.org/dashboard?groups=neuro-sig - Open package reviews check: https://bugzilla.redhat.com/show_bug.cgi?id=fedora-neuro - CompNeuro lab compose status check for F40: https://koji.fedoraproject.org/koji/packageinfo?packageID=30691 - Neuroscience query of the week - Next meeting day, and chair. - Open floor. We hope to see you there! The meeting announcement is also posted on the NeuroFedora blog here: https://neuroblog.fedoraproject.org/2024/03/09/next-open-neurofedora-meeting-11-march-1300-utc.html You can learn more about NeuroFedora here: https://neuro.fedoraproject.org -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Inactive packagers for the F40 cycle
On Thu, Feb 22, 2024 19:00:42 +, Mattia Verga via devel wrote: > Per the "Inactive packagers policy" [1], I've run the script and detected 164 > inactive packagers. At the end of the email you can find the full list. > > [1] https://docs.fedoraproject.org/en-US/fesco/Policy_for_inactive_packagers/ > > I also need to apologize, as the first time I ran the script it missed the > checks on mailing lists and bugzilla activities, so it opened a lot of > unnecessary tickets... > > Mattia > > fangq > I've reached out to them to see how they're doing. They maintain a few neuro-sig packages that don't require a lot of work/updates, so it's possible that they just haven't needed to do anything for them in the last cycle but are still active. -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Next Open NeuroFedora Meeting: 1300 UTC on Monday, 26 February, 2024 (today)
Hello everyone, Please join us at the next Open NeuroFedora team meeting on Monday 26 February at 1300UTC in the NeuroFedora channel on Matrix. The meeting is a public meeting, and open for everyone to attend. You can join us over: Matrix in the Fedora meeting channel: https://matrix.to/#/%23meeting:fedoraproject.org You can use this link to see the local time for the meeting: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Open+NeuroFedora+Meeting=20240226T13=%3A=1 or you can use this command in a terminal: $ date --date='TZ="UTC" 1300 Monday' The meeting will be chaired by @ankursinha. The agenda for the meeting is: - New introductions and roll call. - Tasks from last meeting: https://meetbot.fedoraproject.org/latest/neurofedora - Open Pagure tickets: https://pagure.io/neuro-sig/NeuroFedora/issues?status=Open=S%3A+Next+meeting - Package health check: https://packager-dashboard.fedoraproject.org/dashboard?groups=neuro-sig - Open package reviews check: https://bugzilla.redhat.com/show_bug.cgi?id=fedora-neuro - CompNeuro lab compose status check for F40: https://koji.fedoraproject.org/koji/packageinfo?packageID=30691 - Neuroscience query of the week - Next meeting day, and chair. - Open floor. We hope to see you there! The meeting announcement is also posted on the NeuroFedora blog here: https://neuroblog.fedoraproject.org/2024/02/26/next-open-neurofedora-meeting-26-february-1300-utc.html You can learn more about NeuroFedora here: https://neuro.fedoraproject.org -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Donate 1 minute of your time to test upgrades from F39 to F40
No issues here on my primary driver (with updates-testing enabled, though), but did see some packages being downgraded: Downgrading: bind-libs x86_64 32:9.18.21-4.fc40 fedora 1.2 M bind-license noarch 32:9.18.21-4.fc40 fedora 14 k bind-utils x86_64 32:9.18.21-4.fc40 fedora 225 k conmon x86_64 2:2.1.8-4.fc40 fedora 52 k dnf5 x86_64 5.1.12-1.fc40 fedora 588 k dnf5-plugins x86_64 5.1.12-1.fc40 fedora 351 k fuse-overlayfs x86_64 1.12-3.fc40 fedora 67 k libdnf5x86_64 5.1.12-1.fc40 fedora 974 k libdnf5-clix86_64 5.1.12-1.fc40 fedora 262 k perl-Tkx86_64 804.036-12.fc39 fedora 2.2 M python3-patool noarch 1.12-0.27.20231014gitab64562.fc40 fedora 146 k python3-plotly noarch 5.18.0-9.fc40 fedora 17 M python3-xarray noarch 2023.8.0-1.fc40 fedora 2.4 M python3-xlsxwriter noarch 3.1.9-3.fc40 fedora 324 k python3-xnat noarch 0.5.1-6.fc40 fedora 228 k Transaction Summary == Install 86 Packages Upgrade4183 Packages Remove3 Packages Downgrade15 Packages Total download size: 6.6 G Operation aborted. I'll look at plotly and xnat, since they are neuro-sig packages. -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Next Open NeuroFedora Meeting: 1300 UTC on Monday, 12 February, 2024 (today)
Hello everyone, Please join us at the next Open NeuroFedora team meeting on Monday 12 February at 1300UTC in the NeuroFedora channel on Matrix. The meeting is a public meeting, and open for everyone to attend. You can join us over: Matrix in the Fedora meeting channel: https://matrix.to/#/%23meeting:fedoraproject.org You can use this link to see the local time for the meeting: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Open+NeuroFedora+Meeting=20240212T13=%3A=1 or you can use this command in a terminal: $ date --date='TZ="UTC" 1300 Monday' The meeting will be chaired by @ankursinha. The agenda for the meeting is: - New introductions and roll call. - Tasks from last meeting: https://meetbot.fedoraproject.org/latest/neurofedora - Open Pagure tickets: https://pagure.io/neuro-sig/NeuroFedora/issues?status=Open=S%3A+Next+meeting - Package health check: https://packager-dashboard.fedoraproject.org/dashboard?groups=neuro-sig - Open package reviews check: https://bugzilla.redhat.com/show_bug.cgi?id=fedora-neuro - CompNeuro lab compose status check for F40: https://koji.fedoraproject.org/koji/packageinfo?packageID=30691 - Neuroscience query of the week - Next meeting day, and chair. - Open floor. We hope to see you there! The meeting announcement is also posted on the NeuroFedora blog here: https://neuroblog.fedoraproject.org/2024/02/12/next-open-neurofedora-meeting-12-february-1300-utc.html You can learn more about NeuroFedora here: https://neuro.fedoraproject.org -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Next Open NeuroFedora Meeting: 1300 UTC on Monday, 15 January, 2024 (today)
Hello everyone, Please join us at the next Open NeuroFedora team meeting on Monday 15 January at 1300UTC in the NeuroFedora channel on Matrix. The meeting is a public meeting, and open for everyone to attend. You can join us over: Matrix in the Fedora meeting channel: https://matrix.to/#/%23meeting:fedoraproject.org You can use this link to see the local time for the meeting: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Open+NeuroFedora+Meeting=20240115T13=%3A=1 or you can use this command in a terminal: $ date --date='TZ="UTC" 1300 Monday' The meeting will be chaired by @ankursinha. The agenda for the meeting is: - New introductions and roll call. - Tasks from last meeting: https://meetbot.fedoraproject.org/latest/neurofedora - Open Pagure tickets: https://pagure.io/neuro-sig/NeuroFedora/issues?status=Open=S%3A+Next+meeting - Package health check: https://packager-dashboard.fedoraproject.org/dashboard?groups=neuro-sig - Open package reviews check: https://bugzilla.redhat.com/show_bug.cgi?id=fedora-neuro - CompNeuro lab compose status check for F40: https://koji.fedoraproject.org/koji/packageinfo?packageID=30691 - Neuroscience query of the week - Next meeting day, and chair. - Open floor. We hope to see you there! The meeting announcement is also posted on the NeuroFedora blog here: https://neuroblog.fedoraproject.org/2024/01/15/next-open-neurofedora-meeting-15-january-1300-utc.html You can learn more about NeuroFedora here: https://neuro.fedoraproject.org -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Non responsive maintainer check for marxin
Hi folks, Would anyone know how to contact @marxin? They only maintain the one package, python-pebble, but it doesn't look like they've been active in a while. The package did not see to have been updated at all since the initial import: https://bugzilla.redhat.com/show_bug.cgi?id=2227456 and there are now new pending bugs that have not seen responses too: https://bugzilla.redhat.com/show_bug.cgi?id=2250914 We've waited for responses to PRs in the past and then had to use proven packager rights to update and maintain the package: https://src.fedoraproject.org/rpms/python-pebble/pull-request/2 https://src.fedoraproject.org/rpms/python-pebble/commits/rawhide Since a Neuro-SIG package depends on it, we're happy to take it over. Here's what I could get from fedora-active-user: python fedora_active_user.py --user marxin --email mli...@suse.cz --nofas Last action on koji: Fri, 15 Sep 2023 tag_package_owners entry created by humaton [still active] Last package update on bodhi: 2020-06-29 07:10:30 on package python-pebble-4.5.3-1.fc33 Last actions performed according to fedmsg: Last email on mailing list: ERROR:active-user:name 'mailinglist' is not defined Here's the tracker bug: https://bugzilla.redhat.com/show_bug.cgi?id=2256491 -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
FYI: morphio changed license from LGPL-3.0 to Apache-2.0
Hi folks, Just an FYI. Morphio has changed its license from LGPL-3.0 to Apache-2.0 in the latest version 3.3.7: https://github.com/BlueBrain/MorphIO/pull/467 -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Next Open NeuroFedora Meeting: 1300 UTC on Monday, 04 December (today)
Hello everyone, Please join us at the next Open NeuroFedora team meeting on Monday 04 December at 1300UTC in the NeuroFedora channel on Matrix. The meeting is a public meeting, and open for everyone to attend. You can join us over: Matrix: https://matrix.to/#/%23neuro:fedoraproject.org You can use this link to see the local time for the meeting: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Open+NeuroFedora+Meeting=20231204T13=%3A=1 or you can use this command in a terminal: $ date --date='TZ="UTC" 1300 Monday' The meeting will be chaired by @ankursinha. The agenda for the meeting is: - New introductions and roll call. - Tasks from last meeting: https://meetbot.fedoraproject.org/latest/neurofedora - Open Pagure tickets: https://pagure.io/neuro-sig/NeuroFedora/issues?status=Open=S%3A+Next+meeting - Package health check: https://packager-dashboard.fedoraproject.org/dashboard?groups=neuro-sig - Open package reviews check: https://bugzilla.redhat.com/show_bug.cgi?id=fedora-neuro - CompNeuro lab compose status check for F40: https://koji.fedoraproject.org/koji/packageinfo?packageID=30691 - Neuroscience query of the week - Next meeting day, and chair. - Open floor. We hope to see you there! The meeting announcement is also posted on the NeuroFedora blog here: https://neuroblog.fedoraproject.org/2023/12/04/next-open-neurofedora-meeting-04-December-1300-utc.html You can learn more about NeuroFedora here: https://neuro.fedoraproject.org -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: dracut problems quick docs page requires help
On Thu, Nov 30, 2023 09:23:58 +0100, David Tardon wrote: > Hi, Hi David, > On Tue, 2023-11-21 at 06:39 +, Ankur Sinha wrote: > > Hi folks, > > > > We have this issue open on the quick-docs repo: > > https://pagure.io/fedora-docs/quick-docs/issue/641 > > > > TLDR; the "debug-dracut-problems" quick doc seems to be out of date > > and > > needs review/updating. > > > > https://docs.fedoraproject.org/en-US/quick-docs/debug-dracut-problems/ > > "It hasn't been changed in a while" does not equal "it's out of date". Yeh, sure. This page just hasn't been reviewed since it was imported from the wiki so we don't know if it's out of date or not: https://pagure.io/fedora-docs/quick-docs/history/modules/ROOT/pages/debug-dracut-problems.adoc?identifier=main > The kernel command line arguments for dracut that the page mentions > still work the same way they worked 10 years ago. (With the exception > of rd.udev.debug, which is ignored by systemd-based initrds; I've > submitted a PR to fix that. And rd.udev.info is kinda pointless, as > "info" is the default log level of systemd-udevd.) Thanks. Could you please link to the PRs (or have they already been merged)? I don't see them here: https://pagure.io/fedora-docs/quick-docs/pull-requests > > > nfortunately, I don't know enough about dracut to do this myself. > > Would > > someone that knows this stuff please consider reviewing (even > > updating?) > > the page so we know what to do with it next? > > Are there _actual_ problems there, i.e., something that doesn't work > anymore? I honestly don't know. The page has just never been reviewed since it was auto-imported from the wiki. If the information there is all correct, I can mark it as "up to date". -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
dracut problems quick docs page requires help
Hi folks, We have this issue open on the quick-docs repo: https://pagure.io/fedora-docs/quick-docs/issue/641 TLDR; the "debug-dracut-problems" quick doc seems to be out of date and needs review/updating. https://docs.fedoraproject.org/en-US/quick-docs/debug-dracut-problems/ Unfortunately, I don't know enough about dracut to do this myself. Would someone that knows this stuff please consider reviewing (even updating?) the page so we know what to do with it next? -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Next Open NeuroFedora Meeting: 1300 UTC on Monday, 20 November (today)
Hello everyone, Please join us at the next Open NeuroFedora team meeting on Monday 20 November at 1300UTC in the NeuroFedora channel on Matrix. The meeting is a public meeting, and open for everyone to attend. You can join us over: Matrix: https://matrix.to/#/%23neuro:fedoraproject.org You can use this link to see the local time for the meeting: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Open+NeuroFedora+Meeting=20231120T13=%3A=1 or you can use this command in a terminal: $ date --date='TZ="UTC" 1300 Monday' The meeting will be chaired by @ankursinha. The agenda for the meeting is: - New introductions and roll call. - Tasks from last meeting: https://meetbot.fedoraproject.org/latest/neurofedora - Open Pagure tickets: https://pagure.io/neuro-sig/NeuroFedora/issues?status=Open=S%3A+Next+meeting - Package health check: https://packager-dashboard.fedoraproject.org/dashboard?groups=neuro-sig - Open package reviews check: https://bugzilla.redhat.com/show_bug.cgi?id=fedora-neuro - CompNeuro lab compose status check for F39: https://koji.fedoraproject.org/koji/packageinfo?packageID=30691 - Neuroscience query of the week - Next meeting day, and chair. - Open floor. We hope to see you there! The meeting announcement is also posted on the NeuroFedora blog here: https://neuroblog.fedoraproject.org/2023/11/20/next-open-neurofedora-meeting-20-November-1300-utc.html You can learn more about NeuroFedora here: https://neuro.fedoraproject.org -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Next Open NeuroFedora Meeting: 1300 UTC on Monday, 23 October (today)
Hello everyone, Please join us at the next Open NeuroFedora team meeting on Monday 23 October at 1300UTC in the NeuroFedora channel on Matrix. The meeting is a public meeting, and open for everyone to attend. You can join us over: Matrix: https://matrix.to/#/%23neuro:fedoraproject.org You can use this link to see the local time for the meeting: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Open+NeuroFedora+Meeting=20231023T13=%3A=1 or you can use this command in a terminal: $ date --date='TZ="UTC" 1300 Monday' The meeting will be chaired by @ankursinha. The agenda for the meeting is: - New introductions and roll call. - Tasks from last meeting: https://meetbot.fedoraproject.org/latest/neurofedora - Open Pagure tickets: https://pagure.io/neuro-sig/NeuroFedora/issues?status=Open=S%3A+Next+meeting - Package health check: https://packager-dashboard.fedoraproject.org/dashboard?groups=neuro-sig - Open package reviews check: https://bugzilla.redhat.com/show_bug.cgi?id=fedora-neuro - CompNeuro lab compose status check for F39: https://koji.fedoraproject.org/koji/packageinfo?packageID=30691 - Neuroscience query of the week - Next meeting day, and chair. - Open floor. We hope to see you there! The meeting announcement is also posted on the NeuroFedora blog here: https://neuroblog.fedoraproject.org/2023/10/23/next-open-neurofedora-meeting-23-October-1300-utc.html You can learn more about NeuroFedora here: https://neuro.fedoraproject.org -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Next Open NeuroFedora Meeting: 1300 UTC on Monday, 09 October (today)
Hello everyone, Sorry for the very late notice. Please join us at the next Open NeuroFedora team meeting on Monday 09 October at 1300UTC in #fedora-neuro on IRC (Libera.chat). The meeting is a public meeting, and open for everyone to attend. You can join us over: Matrix: https://matrix.to/#/%23neuro:fedoraproject.org (we'll try the bot there and move to IRC if we need to) You can use this link to see the local time for the meeting: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Open+NeuroFedora+Meeting=20231009T13=%3A=1 or you can use this command in a terminal: $ date --date='TZ="UTC" 1300 Monday' The meeting will be chaired by @ankursinha. The agenda for the meeting is: - New introductions and roll call. - Tasks from last meeting: https://meetbot.fedoraproject.org/latest/neurofedora - Open Pagure tickets: https://pagure.io/neuro-sig/NeuroFedora/issues?status=Open=S%3A+Next+meeting - Package health check: https://packager-dashboard.fedoraproject.org/dashboard?groups=neuro-sig - Open package reviews check: https://bugzilla.redhat.com/show_bug.cgi?id=fedora-neuro - CompNeuro lab compose status check for F39: https://koji.fedoraproject.org/koji/packageinfo?packageID=30691 - Neuroscience query of the week - Next meeting day, and chair. - Open floor. We hope to see you there! The meeting announcement is also posted on the NeuroFedora blog here: https://neuroblog.fedoraproject.org/2023/10/09/next-open-neurofedora-meeting-09-October-1300-utc.html You can learn more about NeuroFedora here: https://neuro.fedoraproject.org -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Push to src.fedoraproject.org using https
On Sun, Oct 08, 2023 16:28:58 -0300, Priscila Gutierres wrote: > I solved the issue cloning the repo using fedpkg That's good to hear. We have a section on using fedpkg anonymously in the docs here if that'll help others: https://docs.fedoraproject.org/en-US/package-maintainers/Package_Maintenance_Guide/#using_fedpkg_anonymously -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Automate your Fedora package maintenance using Packit
On Fri, Sep 15, 2023 12:53:21 +0200, Laura Barcziova wrote: > Yes, Fedora dist-git lookaside cache. The upstream archive is uploaded > automatically, but only a pull request is created in the particular dist-git > repo with the change of the sources reference. Once the PRs are created, it is > up to the maintainer to review these changes and, just after that, merge the > changes with the updated reference to the respective branches. See also: https://github.com/packit/packit/issues/2035 Packit is awesome, it really does help to automate lots of menial tasks, but the risk really is that maintainers forget to do their due diligence before merging the PRs and all that. I guess it should be possible to make packit (or the-new-hotness?) run licensecheck on the new sources and include that in the PR comment too, perhaps also with a list of packages that depend on the one being updated as an "impact check"? See also: https://github.com/fedora-infra/the-new-hotness/issues/545 Another issue relevant to us Fedora package maintainers is this one (already being worked on from what I see): https://github.com/packit/packit/issues/1920 -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Next Open NeuroFedora Meeting: 1300 UTC on Monday, 11 September (today)
Hello everyone, Please join us at the next Open NeuroFedora team meeting on Monday 11 September at 1300UTC in #fedora-neuro on IRC (Libera.chat). The meeting is a public meeting, and open for everyone to attend. You can join us over: IRC: https://webchat.libera.chat/?channels=#fedora-neuro (We will return to Matrix once the matrix meetbot is ready/deployed) You can use this link to see the local time for the meeting: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Open+NeuroFedora+Meeting=20230911T13=%3A=1 or you can use this command in a terminal: $ date --date='TZ="UTC" 1300 Monday' The meeting will be chaired by @ankursinha. The agenda for the meeting is: - New introductions and roll call. - Tasks from last meeting: https://meetbot.fedoraproject.org/latest/neurofedora - Open Pagure tickets: https://pagure.io/neuro-sig/NeuroFedora/issues?status=Open=S%3A+Next+meeting - Package health check: https://packager-dashboard.fedoraproject.org/dashboard?groups=neuro-sig - Open package reviews check: https://bugzilla.redhat.com/show_bug.cgi?id=fedora-neuro - CompNeuro lab compose status check for F39: https://koji.fedoraproject.org/koji/packageinfo?packageID=30691 - Neuroscience query of the week - Next meeting day, and chair. - Open floor. We hope to see you there! The meeting announcement is also posted on the NeuroFedora blog here: https://neuroblog.fedoraproject.org/2023/09/11/next-open-neurofedora-meeting-11-September-1300-utc.html You can learn more about NeuroFedora here: https://neuro.fedoraproject.org -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Anyone interested in packaging + maintaining the nimble language?
Hi folks, I have a package that has begun to use the nimble language in its new version: https://bugzilla.redhat.com/show_bug.cgi?id=2181693 https://nim-lang.org/ It isn't packaged for Fedora yet, though. Is anyone using it, and would like to package + maintain it for Fedora? -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Orphaned packages looking for new maintainers
On Mon, Sep 04, 2023 17:36:15 +0200, Miro Hrončok wrote: > On 04. 09. 23 17:30, Ankur Sinha wrote: > > On Mon, Sep 04, 2023 17:10:55 +0200, Miro Hrončok wrote: > > > python-mne-bids neuro-sig, orphan0 > > > weeks ago > > > > This is a neuro-sig package, so I've taken over as primary maintainer. > > This is one of the packages that failed the Python 3.12 rebuild: > > https://bugzilla.redhat.com/show_bug.cgi?id=2220334 > https://bugzilla.redhat.com/show_bug.cgi?id=2226245 Yeh, upstream published a new release of python-mne which was holding up python-mne-bids but a test failed there too. They've published a fix for this a few days ago, so it should be fixed asap: https://bugzilla.redhat.com/show_bug.cgi?id=2220333 https://github.com/mne-tools/mne-python/issues/11931 -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Orphaned packages looking for new maintainers
On Mon, Sep 04, 2023 17:10:55 +0200, Miro Hrončok wrote: > python-mne-bids neuro-sig, orphan0 weeks ago This is a neuro-sig package, so I've taken over as primary maintainer. -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Simple review swap: python-pygments-git
Hi folks, Would someone like to swap reviews please? I'd like to get python-pygments-git reviewed. They are pygments lexers for git output and files. The review is here: https://bugzilla.redhat.com/show_bug.cgi?id=2229721 It should be a simple review, so unofficial reviews from folks looking to get sponsored to the packager group are also most welcome. -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Donate 1 minute of your time to test upgrades from F38 to F39
1.10-16.fc38.noarch from fedora-modular requires python(abi) = 3.11, but none of the providers can be installed - package python3-async-generator-1.10-16.fc38.noarch from updates-modular requires python(abi) = 3.11, but none of the providers can be installed - package python3-async-generator-1.10-16.fc38.noarch from updates-testing-modular requires python(abi) = 3.11, but none of the providers can be installed - package rfpkgdb-cli-2.15.0-0.14rc2.fc39.noarch from rpmfusion-free requires python(abi) = 3.12, but none of the providers can be installed - python3-3.12.0~rc1-1.fc39.i686 from updates-testing-modular does not belong to a distupgrade repository - python3-3.12.0~rc1-1.fc39.i686 from updates-modular does not belong to a distupgrade repository - python3-3.12.0~rc1-1.fc39.i686 from fedora-modular does not belong to a distupgrade repository - python3-3.12.0~rc1-1.fc39.i686 from fedora does not belong to a distupgrade repository - cannot install both python3-3.12.0~rc1-1.fc39.x86_64 from fedora and python3-3.11.4-1.fc38.x86_64 from @System - cannot install both python3-3.12.0~rc1-1.fc39.x86_64 from fedora-modular and python3-3.11.4-1.fc38.x86_64 from @System - cannot install both python3-3.12.0~rc1-1.fc39.x86_64 from updates-modular and python3-3.11.4-1.fc38.x86_64 from @System - cannot install both python3-3.12.0~rc1-1.fc39.x86_64 from updates-testing-modular and python3-3.11.4-1.fc38.x86_64 from @System - problem with installed package rfpkgdb-cli-2.15.0-0.12rc2.fc37.noarch - rfpkgdb-cli-2.15.0-0.12rc2.fc37.noarch from @System does not belong to a distupgrade repository -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Script for installing TeXLive packages required by a document?
Hi folks, fedtex is now built, and updates pushed: https://bodhi.fedoraproject.org/updates/?packages=fedtex -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Script for installing TeXLive packages required by a document?
Review is up: https://bugzilla.redhat.com/show_bug.cgi?id=2228841 Should be quite an easy one, if anyone wants to swap :) -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Script for installing TeXLive packages required by a document?
On Wed, Aug 02, 2023 15:10:34 -0400, Blaise Pabon wrote: > Peace and blessings upon you, this is great. > Years ago, managing Tex dependencies was the bane of my life. Haha, yeh, but all the work spot and others do to package TeXLive for us makes it so much easier now :) -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Script for installing TeXLive packages required by a document?
On Wed, Aug 02, 2023 20:52:24 +0200, Iñaki Ucar wrote: > This is very useful, so +1 to packaging it. > > I don't know if there's a better solution. There is an R package called > tinytex > [1] that provides automatic installation of TeXLive packages in a user > library. > AFAIK, it just compiles the stuff, parses the logs for errors looking for > "blablabla.sty not found", and then installs them and retries until everything > is fine. > > [1] https://yihui.org/tinytex/ Yeh, I've seen various tools that attempt to do this, but: - I don't necessarily want it to compile the whole document multiple times until it figures out all the deps - these tools don't integrate with dnf/rpm using our excellent "Provides: tex(...sty)" system So, I came up with this as a Fedora specific way. I've put it in a separate repo as `fedtex` now: https://pagure.io/fedtex I'll go package it up and submit it for review. Please do test it out and suggest improvements/fixes/features. -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Script for installing TeXLive packages required by a document?
Hi folks, Would any Fedora TeXLive users have any scripts to figure out what TeXLive packages a TeX/LaTeX document uses and install them using dnf? I've got this hacked up and it does work and I was wondering if I should move it to a different repository and package it up to make it available to all Fedora users, but does someone have a better solution/tool? https://github.com/sanjayankur31/100_dotfiles/blob/main/bin/fedora-install-texlive-deps.sh (also attached) -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London fedora-install-texlive-deps.sh Description: Bourne shell script signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Fedora 39 Mass Rebuild started
On Sat, Jul 22, 2023 09:35:26 -0700, Kevin Fenzi wrote: > On Sat, Jul 22, 2023 at 11:04:19AM +0100, Ankur Sinha wrote: > > > The wiki page also looks out of date (still refers f38): > > https://fedoraproject.org/wiki/Fedora_39_Mass_Rebuild > > > > I had the usual question---should I be making new builds for updates and > > fixes into the mass rebuild side tag, or is rawhide OK? > > Rawhide as normal is fine. > > When the tag is merged it will look and see if there is a newer build in > rawhide already. If so, it won't take the mass rebuild one in. Cool! Thanks very much. -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Fedora 39 Mass Rebuild started
On Wed, Jul 19, 2023 13:31:57 +0200, Tomas Hrcka wrote: > Oh, that thing again. > Let me update the template so sed works correctly. > The wiki page also looks out of date (still refers f38): https://fedoraproject.org/wiki/Fedora_39_Mass_Rebuild I had the usual question---should I be making new builds for updates and fixes into the mass rebuild side tag, or is rawhide OK? -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Py3.12: vit -> urwid -> undefined symbol: PyUnicode_AS_UNICODE
Hi folks, While looking into the vit FTI bug[1], I ran into this error in the test: > == > ERROR: vit (unittest.loader._FailedTest.vit) > -- > ImportError: Failed to import test module: vit > Traceback (most recent call last): > File "/usr/lib64/python3.12/unittest/loader.py", line 415, in > _find_test_path > package = self._get_module_from_name(name) > > File "/usr/lib64/python3.12/unittest/loader.py", line 325, in > _get_module_from_name > __import__(name) > File "/builddir/build/BUILD/vit-2.3.0/vit/__init__.py", line 2, in > from .application import Application > File "/builddir/build/BUILD/vit-2.3.0/vit/application.py", line 19, in > > from vit.formatter_base import FormatterBase > File "/builddir/build/BUILD/vit-2.3.0/vit/formatter_base.py", line 8, in > > from vit import util > File "/builddir/build/BUILD/vit-2.3.0/vit/util.py", line 7, in > from urwid.str_util import calc_width > ImportError: > /usr/lib64/python3.12/site-packages/urwid/str_util.cpython-312-x86_64-linux-gnu.so: > undefined symbol: PyUnicode_AS_UNICODE A web search brought me here: https://github.com/cython/cython/issues/5149 How would we fix this? Is this something that needs fixing in urwid? I still see PyUnicode_AS_UNICODE used there: https://github.com/search?q=repo%3Aurwid%2Furwid%20PyUnicode_AS_UNICODE=code (and no issues filed about it yet). -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Non responsive maintainer check for @ilgrad
FYI: also forwarded to the correct gmail address (I'd used org instead of com) On Mon, Jul 03, 2023 11:43:05 +0100, Ankur Sinha wrote: > Dear all, > > Would anyone know how to contact @ilgrad (Ilya Gradina)? They are one of > the original members of the neuro-sig packager group, but we've not > heard from them in quite a while now. > > I've filed a non-responsive check bug here: > https://bugzilla.redhat.com/show_bug.cgi?id=2219364 > > Here are the bugs that they've not responded to: > https://bugzilla.redhat.com/buglist.cgi?bug_status=__open__=Fedora=product%2Ccomponent%2Cassigned_to%2Cstatus%2Csummary%2Clast_change_time%2Cseverity%2Cpriority=ilya.gradina%40gmail.com_to1=1=1=substring_id=13252967=status%2C%20priority%2C%20assigned_to%2C%20id%2C%20=Fedora_format=advanced > > > fedora_active_user.py output: > > $ python fedora_active_user.py --user ilgrad --email ilya.grad...@gmail.com > --nofas > Last action on koji: >Fri, 10 Mar 2023 tag_package_owners entry created by humaton [still active] > > Last package update on bodhi: >2019-10-22 22:36:05 on package flacon-5.5.1-1.fc31 > Last actions performed according to fedmsg: > - io.pagure.prod.pagure.issue.comment.added on 2022-08-18 23:28:59 > > Last email on mailing list: > On 2016-04-07T11:58:30Z ilya.grad...@gmail.com emailed as Ilia Gradina on > https://lists.fedoraproject.org/archives/api/list/devel@lists.fedoraproject.org/ > On 2016-04-07T11:14:57Z ilya.grad...@gmail.com emailed as Ilia Gradina on > https://lists.fedoraproject.org/archives/api/list/devel@lists.fedoraproject.org/ > On 2016-04-07T10:47:15Z ilya.grad...@gmail.com emailed as Ilia Gradina on > https://lists.fedoraproject.org/archives/api/list/devel@lists.fedoraproject.org/ > On 2016-04-05T19:55:29Z ilya.grad...@gmail.com emailed as Ilia Gradina on > https://lists.fedoraproject.org/archives/api/list/devel@lists.fedoraproject.org/ > On 2016-04-04T22:26:04Z ilya.grad...@gmail.com emailed as Ilia Gradina on > https://lists.fedoraproject.org/archives/api/list/devel@lists.fedoraproject.org/ > On 2016-04-04T19:30:01Z ilya.grad...@gmail.com emailed as Ilia Gradina on > https://lists.fedoraproject.org/archives/api/list/devel@lists.fedoraproject.org/ > On 2015-08-07T20:28:02Z ilya.grad...@gmail.com emailed as Ilia Gradina on > https://lists.fedoraproject.org/archives/api/list/devel@lists.fedoraproject.org/ > On 2015-07-20T15:16:18Z ilya.grad...@gmail.com emailed as Ilia Gradina on > https://lists.fedoraproject.org/archives/api/list/devel@lists.fedoraproject.org/ > > Bugzilla activity >6 bugs assigned, cc or on which ilya.grad...@gmail.com commented > Last comment on the most recent ticket on bugzilla: > > > -- > Thanks, > Regards, > Ankur Sinha "FranciscoD" (He / Him / His) | > https://fedoraproject.org/wiki/User:Ankursinha > Time zone: Europe/London -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Non responsive maintainer check for @ilgrad
Dear all, Would anyone know how to contact @ilgrad (Ilya Gradina)? They are one of the original members of the neuro-sig packager group, but we've not heard from them in quite a while now. I've filed a non-responsive check bug here: https://bugzilla.redhat.com/show_bug.cgi?id=2219364 Here are the bugs that they've not responded to: https://bugzilla.redhat.com/buglist.cgi?bug_status=__open__=Fedora=product%2Ccomponent%2Cassigned_to%2Cstatus%2Csummary%2Clast_change_time%2Cseverity%2Cpriority=ilya.gradina%40gmail.com_to1=1=1=substring_id=13252967=status%2C%20priority%2C%20assigned_to%2C%20id%2C%20=Fedora_format=advanced fedora_active_user.py output: $ python fedora_active_user.py --user ilgrad --email ilya.grad...@gmail.com --nofas Last action on koji: Fri, 10 Mar 2023 tag_package_owners entry created by humaton [still active] Last package update on bodhi: 2019-10-22 22:36:05 on package flacon-5.5.1-1.fc31 Last actions performed according to fedmsg: - io.pagure.prod.pagure.issue.comment.added on 2022-08-18 23:28:59 Last email on mailing list: On 2016-04-07T11:58:30Z ilya.grad...@gmail.com emailed as Ilia Gradina on https://lists.fedoraproject.org/archives/api/list/devel@lists.fedoraproject.org/ On 2016-04-07T11:14:57Z ilya.grad...@gmail.com emailed as Ilia Gradina on https://lists.fedoraproject.org/archives/api/list/devel@lists.fedoraproject.org/ On 2016-04-07T10:47:15Z ilya.grad...@gmail.com emailed as Ilia Gradina on https://lists.fedoraproject.org/archives/api/list/devel@lists.fedoraproject.org/ On 2016-04-05T19:55:29Z ilya.grad...@gmail.com emailed as Ilia Gradina on https://lists.fedoraproject.org/archives/api/list/devel@lists.fedoraproject.org/ On 2016-04-04T22:26:04Z ilya.grad...@gmail.com emailed as Ilia Gradina on https://lists.fedoraproject.org/archives/api/list/devel@lists.fedoraproject.org/ On 2016-04-04T19:30:01Z ilya.grad...@gmail.com emailed as Ilia Gradina on https://lists.fedoraproject.org/archives/api/list/devel@lists.fedoraproject.org/ On 2015-08-07T20:28:02Z ilya.grad...@gmail.com emailed as Ilia Gradina on https://lists.fedoraproject.org/archives/api/list/devel@lists.fedoraproject.org/ On 2015-07-20T15:16:18Z ilya.grad...@gmail.com emailed as Ilia Gradina on https://lists.fedoraproject.org/archives/api/list/devel@lists.fedoraproject.org/ Bugzilla activity 6 bugs assigned, cc or on which ilya.grad...@gmail.com commented Last comment on the most recent ticket on bugzilla: -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Next Open NeuroFedora Meeting: 1300 UTC on Monday, 03 July (today)
Hello everyone, Please join us at the next Open NeuroFedora team meeting on Monday 03 July at 1300UTC in #fedora-neuro on Matrix or IRC (Libera.chat). The meeting is a public meeting, and open for everyone to attend. You can join us over: Matrix: https://matrix.to/#/#neuro:fedoraproject.org IRC: https://webchat.libera.chat/?channels=#fedora-neuro You can use this link to see the local time for the meeting: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Open+NeuroFedora+Meeting=20230703T13=%3A=1 or you can use this command in a terminal: $ date --date='TZ="UTC" 1300 Monday' The meeting will be chaired by @ankursinha. The agenda for the meeting is: - New introductions and roll call. - Tasks from last meeting: https://meetbot.fedoraproject.org/latest/neurofedora - Open Pagure tickets: https://pagure.io/neuro-sig/NeuroFedora/issues?status=Open=S%3A+Next+meeting - Package health check: https://packager-dashboard.fedoraproject.org/dashboard?groups=neuro-sig - Open package reviews check: https://bugzilla.redhat.com/show_bug.cgi?id=fedora-neuro - CompNeuro lab compose status check for F39: https://koji.fedoraproject.org/koji/packageinfo?packageID=30691 - Neuroscience query of the week - Next meeting day, and chair. - Open floor. We hope to see you there! The meeting announcement is also posted on the NeuroFedora blog here: https://neuroblog.fedoraproject.org/2023/07/03/next-open-neurofedora-meeting-03-July-1300-utc.html You can learn more about NeuroFedora here: https://neuro.fedoraproject.org -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Releasing package updates in multiple Fedora releases
On Mon, Jun 19, 2023 13:02:45 +0200, Vít Ondruch wrote: > > Dne 19. 06. 23 v 11:55 Ankur Sinha napsal(a): > > > > > We're discussing a different topic now. > > > Sorry but we don't. The thread started with: "For the 99% of packages I > maintain I usually perform the same workflow > when updating them". I don't see that percentage could be in line with the > update policy. > It really depends on what these packages are (and had I assumed that was hyperbole anyway). It sure wouldn't apply to 99% of my (or the neuro-sig) packages, but would to quite a few. To re-iterate: everyone should remember to check what impact their package builds/updates have on other packages before building/pushing (even for rawhide). > > The thread was "these steps are > > repetitive, how do folks automate them", and we're now discussing > > "maintainers should remember to check the impact of update before > > pushing them". > > > Being maintainer of ~200 packages, I certainly don't suffer the > repetitiveness, because there is rarely need to update the stable releases, > following the update policy. Again, it really depends on your packages. You maintain lots of core libraries where API/ABI bumps etc. do not/should not be pushed to stable releases. For the neuro-sig, we do have quite a few python packages that have frequent minor/patch releases and we do push these as updates to stable branches also after doing impact checks. So, I do use my script for these. -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Releasing package updates in multiple Fedora releases
On Mon, Jun 19, 2023 08:28:23 +0200, Vitaly Zaitsev via devel wrote: > On 18/06/2023 17:42, Ankur Sinha wrote: > > I threw all the commands into a script with some optional arguments: > > Maybe this script can be added to fedora-packager? Sure, if folks find it useful enough. In the meantime, I added bits to run `fedrq` before each branch is worked upon to inform the user what packages would be affected: https://github.com/sanjayankur31/100_dotfiles/blob/main/bin/fedpkg-sync-build-all-branches.sh#L30 -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Releasing package updates in multiple Fedora releases
On Mon, Jun 19, 2023 11:22:35 +0200, Vít Ondruch wrote: > Right, not pushing to all branches is in line with official guidelines: > > https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#stable-releases It's more nuanced than "don't push updates to all branches" though: ".. we should avoid major updates of packages within a stable release. Updates should aim to fix bugs, and not introduce features, particularly when those features would materially affect the user or developer experience. The update rate for any given release should drop off over time, approaching zero near release end-of-life; since updates are primarily bugfixes, fewer and fewer should be needed over time." So minor/patch version updates, especially for things like Python packages that have frequent minor/patch releases is perfectly fine. > Especially I don't like my packages being FTBFS due to other packagers > pushing their updates everywhere. If there was at least included > mass-prebuild step in the initial list to ensure there is no breakage in > dependent packages. This is part of the "vetting the update before pushing" step. We have tools that package maintainers can/should use to see what packages depend on a particular one before updating it (fedrq is one I believe, but folks have their own dnf based scripts/commands). I've also filed an RFE to the-new-hotness to add dependency information to the "new package version is available" bug report some time ago, which would help ensure maintainers are aware of the update's impact: https://github.com/fedora-infra/the-new-hotness/issues/545 We're discussing a different topic now. The thread was "these steps are repetitive, how do folks automate them", and we're now discussing "maintainers should remember to check the impact of update before pushing them". -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Next Open NeuroFedora Meeting: 1300 UTC on Monday, 19 June (today)
Hello everyone, Please join us at the next Open NeuroFedora team meeting on Monday 19 June at 1300UTC in #fedora-neuro on Matrix or IRC (Libera.chat). The meeting is a public meeting, and open for everyone to attend. You can join us over: Matrix: https://matrix.to/#/#neuro:fedoraproject.org IRC: https://webchat.libera.chat/?channels=#fedora-neuro You can use this link to see the local time for the meeting: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Open+NeuroFedora+Meeting=20230619T13=%3A=1 or you can use this command in a terminal: $ date --date='TZ="UTC" 1300 Monday' The meeting will be chaired by @ankursinha. The agenda for the meeting is: - New introductions and roll call. - Tasks from last meeting: https://meetbot.fedoraproject.org/latest/neurofedora - Open Pagure tickets: https://pagure.io/neuro-sig/NeuroFedora/issues?status=Open=S%3A+Next+meeting - Package health check: https://packager-dashboard.fedoraproject.org/dashboard?groups=neuro-sig - Open package reviews check: https://bugzilla.redhat.com/show_bug.cgi?id=fedora-neuro - CompNeuro lab compose status check for F39: https://koji.fedoraproject.org/koji/packageinfo?packageID=30691 - Neuroscience query of the week - Next meeting day, and chair. - Open floor. We hope to see you there! The meeting announcement is also posted on the NeuroFedora blog here: https://neuroblog.fedoraproject.org/2023/06/19/next-open-neurofedora-meeting-19-June-1300-utc.html You can learn more about NeuroFedora here: https://neuro.fedoraproject.org -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Releasing package updates in multiple Fedora releases
On Mon, Jun 19, 2023 11:04:16 +0200, Miroslav Suchý wrote: > > 2) Even better is Packit > > https://packit.dev/ > > You have many ways to use it. My favorite way is to use pull-from-upstream > > https://packit.dev/posts/pull-from-upstream/ > > You just make sure you have record in https://release-monitoring.org/ and > then put .packit.yaml in Fedora's dist-git. And when upstream has a new > release you will receive a pull request to src.fedoraproject.org for all > configure branches. And when it merges it (can) build in Koji and submit > Bodhi update for you. > > With Packit you can use full automation or only some steps. And combine it > as you like it. If you do not like triggereing by release monitoring, you > can initiate it from command line. It is up to you. > This is awesome! I've been meaning to try Packit for a while now. Will try it asap. -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Releasing package updates in multiple Fedora releases
On Mon, Jun 19, 2023 08:46:47 -, Michael J Gruber wrote: > > On Sun, Jun 18, 2023 at 09:16:28AM +, Mattia Verga via devel wrote: > > > > So one alternative is *not* to push the change to all branches. > > > > Unless it's really necessary, such as fixing an essential bug, I tend > > to leave older Fedora branches on a stable release, to reduce churn > > Exactly. Blindly pushing to all active releases is never a good idea. > Now, I'm not saying people here do that, but those shortcuts make it > too easy to do it in a rash ... > > In particular: Most proposals do it in the wrong order (old to new) > and some without error catching. You may end up with newer builds in > older releases - without an update yet, granted, but still. I think folks here on the list understand that each update needs to be vetted. Once it has been vetted and we know it can go to rawhide + other releases, it's nice to be able to do it quickly and move on to other packages. So shortcuts + automation is always welcome in cases where we know it's doing the right thing. -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Releasing package updates in multiple Fedora releases
On Sun, Jun 18, 2023 14:51:01 +0200, Sandro wrote: > On 18-06-2023 14:16, Vitaly Zaitsev via devel wrote: > > On 18/06/2023 11:16, Mattia Verga via devel wrote: > > > This is quite boring and time wasting... is there a more efficient way > > > to use my packaging time? Do you think fedpkg can be enhanced to have a > > > single command which makes 4-5-6 to all specified branches? I threw all the commands into a script with some optional arguments: https://github.com/sanjayankur31/100_dotfiles/blob/main/bin/fedpkg-sync-build-all-branches.sh I did think that a fedpkg subcommand would would be very useful, but I haven't found the cycles to look into it. -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: nest: python package still setup.py; also needs to be built for MPI
On Thu, Jun 15, 2023 10:13:28 -, David Schwörer wrote:
> > $ sudo dnf repoquery -l python3-bout++ | grep info
> > # returns nothing
> >
> > Thanks again for all your replies. I'm going to spend some time
> > tinkering with the nest sources to see what I can do.
>
> They should be though in the mpi packages:
> $ sudo dnf repoquery -l python3-bout++-mpich | grep info
> # returns nothing
> But they are there missing as well.
> I think the issue is that not the wheel gets installed with cmake, but the
> installation is done with cmake:
> https://github.com/boutproject/BOUT-dev/blob/master/tools/pylib/_boutpp_build/CMakeLists.txt#L115
> I just notice that the wheel is not build at all, as that invokes
> cmake itself, thus a different wheel would need to be build by cmake,
> but then I am not sure how that can be installed?
So the wheel is built manually:
https://github.com/boutproject/BOUT-dev/blob/cbd197e78f7d52721188badfd7c38a0a540a82bd/tools/pylib/_boutpp_build/backend.py#L144
but I don't see where they then install it. Maybe that's the step that's
missing, and would install the dist-info etc.?
Looking at `pyproject_install`:
$ rpm -E %{pyproject_install}
\
specifier=$(ls /home/asinha/rpmbuild/BUILD/pyproject-wheeldir/*.whl | xargs
basename --multiple | sed -E 's/([^-]+)-([^-]+)-.+\.whl/\1==\2/')
TMPDIR="/home/asinha/rpmbuild/BUILD/.pyproject-builddir" /usr/bin/python3 -m
pip install --root
/home/asinha/rpmbuild/BUILDROOT/%{NAME}-%{VERSION}-%{RELEASE}.x86_64 --prefix
/usr --no-deps --disable-pip-version-check --progress-bar off --verbose
--ignore-installed --no-warn-script-location --no-index --no-cache-dir
--find-links /home/asinha/rpmbuild/BUILD/pyproject-wheeldir $specifier
Source here:
https://src.fedoraproject.org/rpms/pyproject-rpm-macros/blob/rawhide/f/macros.pyproject#_66
So, for nest, I'm thinking I can build and install the wheel manually
perhaps similar to how I build and install the package manually now,
only at the moment I do it with `setup.py`.
--
Thanks,
Regards,
Ankur Sinha "FranciscoD" (He / Him / His) |
https://fedoraproject.org/wiki/User:Ankursinha
Time zone: Europe/London
___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
Re: nest: python package still setup.py; also needs to be built for MPI
On Wed, Jun 14, 2023 12:59:40 -, David Schwörer wrote: > > On Tue, Jun 13, 2023 08:31:49 -, David Schwörer wrote: > > That's interesting. So it builds the cpython as part of the cmake build > > and then simply installs it in the required directory. > > > > How does it generate the dist-info metadata, though? That's the bit > > where nest uses `python setup.py install_egg_info`. > > > > https://docs.fedoraproject.org/en-US/packaging-guidelines/Python/#_dist_i... > > > > https://github.com/sanjayankur31/nest-simulator/blob/41892a50f95ddf50966e... > > Unless I am mistaken, that is done in the prepare_metadata_for_build [1], > which gets called from here [2] > > It is currently missing the readme, thus the project description is empty on > pypi [3]. I had troubles finding the appropriate documentation how to do that. Ah, indeed it is generated there. I asked because I was looking at the Fedora package to try and figure it out and couldn't find the metadata in there: $ sudo dnf repoquery -l python3-bout++ | grep info # returns nothing Thanks again for all your replies. I'm going to spend some time tinkering with the nest sources to see what I can do. -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: nest: python package still setup.py; also needs to be built for MPI
On Tue, Jun 13, 2023 08:31:49 -, David Schwörer wrote: > Hi Ankur, Hi David, Thanks for your reply. > Not sure whether that helps, but BOUT++ (requires MPI) switched to a > custom back end [1] when it switched to cmake [2] from configure + > calling setup.py. The main motivation was to enable packaging in > fedora, but it also allowed to just pip install the whole package, as > BOUT++ is now PEP-517 enabled. > > This doesn't call the pyproject macros, but just the cmake ones [3], > so not sure this is applicable to what you need, but maybe it offers > at least some insight into how it is done for other MPI codes ... That's interesting. So it builds the cpython as part of the cmake build and then simply installs it in the required directory. How does it generate the dist-info metadata, though? That's the bit where nest uses `python setup.py install_egg_info`. https://docs.fedoraproject.org/en-US/packaging-guidelines/Python/#_dist_info_metadata https://github.com/sanjayankur31/nest-simulator/blob/41892a50f95ddf50966e2371151b207d098e814a/pynest/CMakeLists.txt#L84 -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: nest: python package still setup.py; also needs to be built for MPI
On Mon, Jun 12, 2023 21:07:05 +0200, Miro Hrončok wrote: > On 12. 06. 23 16:04, Ankur Sinha wrote: > > However, I can't figure out how I would replicate the build using the > > `pyproject` macros. I guess `pyproject_wheel` usage is straightforward > > (?), but how do I get `pyproject_install` to install in the > > $MPI_SITEARCH locations, and then how do I get `pyproject_save_files` to > > store the files in three different lists that I can use in the different > > `%files` sections? > > > This is currently not possible. Unfortunately, support for this would > require somebody else than me to drive it. > > (If you just need to install the same files in multiple locations, you can > cp -a them around after %pyproject_install.) Thanks for your reply, Miro. I guess I can go through the pyproject macro sources and see if it's possible to replicate their flow in the spec. If not, I'll try and replace the `setup.py` commands with `pip` commands in the spec and see how that goes. -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: nest: python package still setup.py; also needs to be built for MPI
On Mon, Jun 12, 2023 15:25:57 +0100, Ankur Sinha wrote: > Quick addendum: > > Upstream has moved away from calling `setup.py` and now uses `pip`: > > https://github.com/nest/nest-simulator/blob/v3.4/pynest/CMakeLists.txt#L91 > > Still not sure how to use the pyproject macros though. No, that's wrong. They still call `setup.py install_egg_info` there. -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: nest: python package still setup.py; also needs to be built for MPI
Quick addendum: Upstream has moved away from calling `setup.py` and now uses `pip`: https://github.com/nest/nest-simulator/blob/v3.4/pynest/CMakeLists.txt#L91 Still not sure how to use the pyproject macros though. On Mon, Jun 12, 2023 15:04:54 +0100, Ankur Sinha wrote: > Hi folks, > > I'm in the process of updating the nest package to the latest release. > It uses cmake as its build system, but then the cmake calls `python > setup.py install` and so on to install the Python API. So, we strip that > bit out and call these commands ourselves in the right places in the > spec[1,2,3]. > > As you'll also see from the spec, nest supports MPI, so we build it 3 > times: > - without MPI > - once with openmpi > - once with mpich > > For the MPI builds, we need to pass the `--install-lib=$MPI_SITEARCH` > option to `python setup.py install` to get it to install the bits in the > right MPI related locations. > > I've noticed that using this system now gives us deprecation warnings > during the build since calling `setup.py ...` explicitly is deprecated. > > However, I can't figure out how I would replicate the build using the > `pyproject` macros. I guess `pyproject_wheel` usage is straightforward > (?), but how do I get `pyproject_install` to install in the > $MPI_SITEARCH locations, and then how do I get `pyproject_save_files` to > store the files in three different lists that I can use in the different > `%files` sections? > > [1] > https://src.fedoraproject.org/rpms/nest/blob/rawhide/f/0001-Disable-python-setups.patch#_34 > [2] > https://src.fedoraproject.org/rpms/nest/blob/rawhide/f/nest.spec#_342 > [3] > https://src.fedoraproject.org/rpms/nest/blob/rawhide/f/nest.spec#_424 > > -- > Thanks, > Regards, > Ankur Sinha "FranciscoD" (He / Him / His) | > https://fedoraproject.org/wiki/User:Ankursinha > Time zone: Europe/London -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Next Open NeuroFedora Meeting: 1300 UTC on Monday, 05 June (today)
Hello everyone, Please join us at the next Open NeuroFedora team meeting on Monday 05 June at 1300UTC in #fedora-neuro on Matrix or IRC (Libera.chat). The meeting is a public meeting, and open for everyone to attend. You can join us over: Matrix: https://matrix.to/#/#neuro:fedoraproject.org IRC: https://webchat.libera.chat/?channels=#fedora-neuro You can use this link to see the local time for the meeting: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Open+NeuroFedora+Meeting=20230605T13=%3A=1 or you can use this command in a terminal: $ date --date='TZ="UTC" 1300 Monday' The meeting will be chaired by @ankursinha. The agenda for the meeting is: - New introductions and roll call. - Tasks from last meeting: https://meetbot.fedoraproject.org/latest/neurofedora - Open Pagure tickets: https://pagure.io/neuro-sig/NeuroFedora/issues?status=Open=S%3A+Next+meeting - Package health check: https://packager-dashboard.fedoraproject.org/dashboard?groups=neuro-sig - Open package reviews check: https://bugzilla.redhat.com/show_bug.cgi?id=fedora-neuro - CompNeuro lab compose status check for F39: https://koji.fedoraproject.org/koji/packageinfo?packageID=30691 - Neuroscience query of the week - Next meeting day, and chair. - Open floor. We hope to see you there! The meeting announcement is also posted on the NeuroFedora blog here: https://neuroblog.fedoraproject.org/2023/06/05/next-open-neurofedora-meeting-05-June-1300-utc.html You can learn more about NeuroFedora here: https://neuro.fedoraproject.org -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Next Open NeuroFedora Meeting: 1300 UTC on Monday, 22 May (today)
Hello everyone, Please join us at the next Open NeuroFedora team meeting on Monday 22 May at 1300UTC in #fedora-neuro on Matrix or IRC (Libera.chat). The meeting is a public meeting, and open for everyone to attend. You can join us over: Matrix: https://matrix.to/#/#neuro:fedoraproject.org IRC: https://webchat.libera.chat/?channels=#fedora-neuro You can use this link to see the local time for the meeting: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Open+NeuroFedora+Meeting=20230522T13=%3A=1 or you can use this command in a terminal: $ date --date='TZ="UTC" 1300 Monday' The meeting will be chaired by @ankursinha. The agenda for the meeting is: - New introductions and roll call. - Tasks from last meeting: https://meetbot.fedoraproject.org/latest/neurofedora - Open Pagure tickets: https://pagure.io/neuro-sig/NeuroFedora/issues?status=Open=S%3A+Next+meeting - Package health check: https://packager-dashboard.fedoraproject.org/dashboard?groups=neuro-sig - Open package reviews check: https://bugzilla.redhat.com/show_bug.cgi?id=fedora-neuro - CompNeuro lab compose status check for F38: https://koji.fedoraproject.org/koji/packageinfo?packageID=30691 - Neuroscience query of the week - Next meeting day, and chair. - Open floor. We hope to see you there! The meeting announcement is also posted on the NeuroFedora blog here: https://neuroblog.fedoraproject.org/2023/05/22/next-open-neurofedora-meeting-22-May-1300-utc.html You can learn more about NeuroFedora here: https://neuro.fedoraproject.org -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Next Open NeuroFedora Meeting: 1300 UTC on Monday, 24 April (today)
Hello everyone, Please join us at the next Open NeuroFedora team meeting on Monday 24th April at 1300UTC in #fedora-neuro on Matrix or IRC (Libera.chat). The meeting is a public meeting, and open for everyone to attend. You can join us over: Matrix: https://matrix.to/#/#neuro:fedoraproject.org IRC: https://webchat.libera.chat/?channels=#fedora-neuro You can use this link to see the local time for the meeting: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Open+NeuroFedora+Meeting=20230424T13=%3A=1 or you can use this command in a terminal: $ date --date='TZ="UTC" 1300 Monday' The meeting will be chaired by @ankursinha. The agenda for the meeting is: - New introductions and roll call. - Tasks from last meeting: https://meetbot.fedoraproject.org/latest/neurofedora - Open Pagure tickets: https://pagure.io/neuro-sig/NeuroFedora/issues?status=Open=S%3A+Next+meeting - Package health check: https://packager-dashboard.fedoraproject.org/dashboard?groups=neuro-sig - Open package reviews check: https://bugzilla.redhat.com/show_bug.cgi?id=fedora-neuro - CompNeuro lab compose status check for F38: https://koji.fedoraproject.org/koji/packageinfo?packageID=30691 - Neuroscience query of the week - Next meeting day, and chair. - Open floor. We hope to see you there! The meeting announcement is also posted on the NeuroFedora blog here: https://neuroblog.fedoraproject.org/2023/04/24/next-open-neurofedora-meeting-24-April-1300-utc.html You can learn more about NeuroFedora here: https://neuro.fedoraproject.org -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Anyone interested in packaging nim-lang?
On Tue, Mar 28, 2023 17:11:06 +0530, Riya Bisht wrote: > Hello, Hi Riya, > I'm interested to package and maintain nim-lang. I've never used nim before > but > i would like to start packaging for fedora. I can learn nim in the process. > Could you please help me to get started with this? That's great to hear! The starting point for package maintainers is here: https://docs.fedoraproject.org/en-US/package-maintainers/Joining_the_Package_Maintainers/ Language stacks can be complex to build and package, and can also be quite a bit of work to maintain. So, if you don't have any packaging experience, I'd perhaps work on a few other packages to gain a good understanding of the packaging pipeline before taking this on. -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Anyone interested in packaging nim-lang?
Hi folks, One of my packages, taskopen[1], has moved to nim in the latest release. I'd like to update it, but I've never used nim (and don't intend to) and so, don't want to maintain a nim-lang stack all by myself. Any folks in the community interested in packaging and maintaining nim? I'll very happy to help, but I'd rather not be the primary maintainer. https://nim-lang.org/ https://github.com/nim-lang/Nim/ package manager: https://github.com/nim-lang/nimble [1] https://github.com/jschlatow/taskopen/blob/v2.0.1/Makefile#L31 -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Next Open NeuroFedora Meeting: 1300 UTC on Monday, 27 March (today)
Hello everyone, Please join us at the next Open NeuroFedora team meeting on Monday 27th March at 1300UTC in #fedora-neuro on Matrix or IRC (Libera.chat). The meeting is a public meeting, and open for everyone to attend. You can join us over: Matrix: https://matrix.to/#/#neuro:fedoraproject.org IRC: https://webchat.libera.chat/?channels=#fedora-neuro You can use this link to see the local time for the meeting: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Open+NeuroFedora+Meeting=20230327T13=%3A=1 or you can use this command in a terminal: $ date --date='TZ="UTC" 1300 Monday' The meeting will be chaired by @ankursinha. The agenda for the meeting is: - New introductions and roll call. - Tasks from last meeting: https://meetbot.fedoraproject.org/latest/neurofedora - Open Pagure tickets: https://pagure.io/neuro-sig/NeuroFedora/issues?status=Open=S%3A+Next+meeting - Package health check: https://packager-dashboard.fedoraproject.org/dashboard?groups=neuro-sig - Open package reviews check: https://bugzilla.redhat.com/show_bug.cgi?id=fedora-neuro - CompNeuro lab compose status check for F38: https://koji.fedoraproject.org/koji/packageinfo?packageID=30691 - Neuroscience query of the week - Next meeting day, and chair. - Open floor. We hope to see you there! The meeting announcement is also posted on the NeuroFedora blog here: https://neuroblog.fedoraproject.org/2023/03/27/next-open-neurofedora-meeting-27-March-1300-utc.html You can learn more about NeuroFedora here: https://neuro.fedoraproject.org -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Logs from Open NeuroFedora Meeting: 1300 UTC on Monday, 13 March (today)
38 beta is go, to be shipped tomorrow: 14 march: https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fedoraproject.org/thread/6CCFZ6GXXDBV5AMXP37IPA2HNLMZJE4O/ (FranciscoD_, 13:57:06) * The F38 Final freeze begins Tuesday 4 April. (so if you want to push any updates, now is the time to do it :D) (FranciscoD_, 13:57:42) * Neuroscience query of the week (FranciscoD_, 13:58:06) * please share anything new on our ticket here: https://pagure.io/neuro-sig/NeuroFedora/issue/318 (FranciscoD_, 14:00:29) * Next meeting day, chair (FranciscoD_, 14:02:16) * ACTION: FranciscoD_ to chair next meeting at 1300 UTC on 27 March (FranciscoD_, 14:03:42) * Open floor (FranciscoD_, 14:03:52) * NeuroDebian paper: https://www.frontiersin.org/articles/10.3389/fninf.2012.00022/full (FranciscoD_, 14:08:36) Meeting ended at 14:09:29 UTC. Action Items * FranciscoD_ comment on ticket to note that we'll use #NeuroFedora for mastodon * FranciscoD_ update docs to mention #NeuroFedora on mastodon * Penguinpee work on unbundling libtiff from iv * FranciscoD_ update https://bugzilla.redhat.com/show_bug.cgi?id=2173665 as per review comments * FranciscoD_ review python-intern * FranciscoD_ to chair next meeting at 1300 UTC on 27 March Action Items, by person --- * FranciscoD_ * FranciscoD_ comment on ticket to note that we'll use #NeuroFedora for mastodon * FranciscoD_ update docs to mention #NeuroFedora on mastodon * FranciscoD_ update https://bugzilla.redhat.com/show_bug.cgi?id=2173665 as per review comments * FranciscoD_ review python-intern * FranciscoD_ to chair next meeting at 1300 UTC on 27 March * Penguinpee * Penguinpee work on unbundling libtiff from iv * **UNASSIGNED** * (none) People Present (lines said) --- * FranciscoD_ (107) * Penguinpee (20) * zodbot (16) * music[m] (16) * davdunc[m (6) * music (0) * aekoroglu (0) * @achilleas (0) * @davdunc (0) * @HafsatAjia-Egbey (0) * @kamdard_ (0) * @lbazan (0) * @major (0) * @zbyszek[m] (0) * @principis (0) * @omnidapps2 (0) * @omnidapps1 (0) * @mnidapps[m] (0) Generated by `MeetBot`_ 0.4 .. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Next Open NeuroFedora Meeting: 1300 UTC on Monday, 13 March (today)
Hello everyone, Please join us at the next Open NeuroFedora team meeting on Monday 13th March at 1300UTC in #fedora-neuro on Matrix or IRC (Libera.chat). The meeting is a public meeting, and open for everyone to attend. You can join us over: Matrix: https://matrix.to/#/#neuro:fedoraproject.org IRC: https://webchat.libera.chat/?channels=#fedora-neuro You can use this link to see the local time for the meeting: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Open+NeuroFedora+Meeting=20230313T27=%3A=1 or you can use this command in a terminal: $ date --date='TZ="UTC" 1300 Monday' The meeting will be chaired by @ankursinha. The agenda for the meeting is: - New introductions and roll call. - Tasks from last meeting: https://meetbot.fedoraproject.org/latest/neurofedora - Open Pagure tickets: https://pagure.io/neuro-sig/NeuroFedora/issues?status=Open=S%3A+Next+meeting - Package health check: https://packager-dashboard.fedoraproject.org/dashboard?groups=neuro-sig - Open package reviews check: https://bugzilla.redhat.com/show_bug.cgi?id=fedora-neuro - CompNeuro lab compose status check for F38: https://koji.fedoraproject.org/koji/packageinfo?packageID=30691 - Neuroscience query of the week - Next meeting day, and chair. - Open floor. We hope to see you there! The meeting announcement is also posted on the NeuroFedora blog here: https://neuroblog.fedoraproject.org/2023/03/13/next-open-neurofedora-meeting-13-March-1300-utc.html You can learn more about NeuroFedora here: https://neuro.fedoraproject.org -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Non-responsive packagers: sbluhm, shaneallcroft
On Mon, Mar 06, 2023 09:29:02 +0100, Pierre-Yves Chibon wrote: > Good Morning Everyone, > > - shaneallcroft contacted since January 11th 2023 > shaneallcroft is main admin of rpms/pyplane > shaneallcroft has a bugzilla override on rpms/pyplane We've not seen Shane at the Neuro-SIG meetings recently. I've cc'd the two e-mail addresses I have for them to this one now. So hopefully they'll get this one. -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Next Open NeuroFedora Meeting: 1300 UTC on Monday, 27 February (today)
Hello everyone, Please join us at the next Open NeuroFedora team meeting on Monday 27th February at 1300UTC in #fedora-neuro on Matrix or IRC (Libera.chat). The meeting is a public meeting, and open for everyone to attend. You can join us over: Matrix: https://matrix.to/#/#neuro:fedoraproject.org IRC: https://webchat.libera.chat/?channels=#fedora-neuro You can use this link to see the local time for the meeting: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Open+NeuroFedora+Meeting=20230227T27=%3A=1 or you can use this command in a terminal: $ date --date='TZ="UTC" 1300 Monday' The meeting will be chaired by @ankursinha. The agenda for the meeting is: - New introductions and roll call. - Tasks from last meeting: https://meetbot.fedoraproject.org/latest/neurofedora - Open Pagure tickets: https://pagure.io/neuro-sig/NeuroFedora/issues?status=Open=S%3A+Next+meeting - Package health check: https://packager-dashboard.fedoraproject.org/dashboard?groups=neuro-sig - Open package reviews check: https://bugzilla.redhat.com/show_bug.cgi?id=fedora-neuro - CompNeuro lab compose status check for F38: https://koji.fedoraproject.org/koji/packageinfo?packageID=30691 - Neuroscience query of the week - Next meeting day, and chair. - Open floor. We hope to see you there! The meeting announcement is also posted on the NeuroFedora blog here: https://neuroblog.fedoraproject.org/2023/02/27/next-open-neurofedora-meeting-27-february-1300-utc.html You can learn more about NeuroFedora here: https://neuro.fedoraproject.org -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Test upgrades from F37 to F38 - it will take you just a minute
Looks good, with a few downgrades: Downgrading: buildah x86_64 1.29.0-2.fc38 calcium-calculator x86_64 7.9.5-10.fc38 enchant2 x86_64 2.3.3-6.fc38 enchant2-aspell x86_64 2.3.3-6.fc38 freerdp-libs x86_64 2:2.9.0-3.fc38 fwupdx86_64 1.8.10-1.fc38 fwupd-plugin-flashromx86_64 1.8.10-1.fc38 fwupd-plugin-modem-manager x86_64 1.8.10-1.fc38 fwupd-plugin-uefi-capsule-data x86_64 1.8.10-1.fc38 libjcat x86_64 0.1.12-2.fc38 libwinpr x86_64 2:2.9.0-3.fc38 mock-core-configsnoarch 38.1-1.fc38 octave x86_64 6:7.3.0-1.fc38 perl-Module-CoreList noarch 1:5.20230120-1.fc38 python3-PyDrive2 noarch 1.15.0-2.fc38 python3-xlsxwriter noarch 3.0.7-1.fc38 syncthingx86_64 1.22.0-1.fc38 syncthing-tools x86_64 1.22.0-1.fc38 transmission-common x86_64 4.0.0-3.fc38 transmission-gtk x86_64 4.0.0-3.fc38 -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Next Open NeuroFedora Meeting: 1300 UTC on Monday, 13 February (today)
Hello everyone, Please join us at the next Open NeuroFedora team meeting on Monday 13th February at 1300UTC in #fedora-neuro on Matrix or IRC (Libera.chat). The meeting is a public meeting, and open for everyone to attend. You can join us over: Matrix: https://matrix.to/#/#neuro:fedoraproject.org IRC: https://webchat.libera.chat/?channels=#fedora-neuro You can use this link to see the local time for the meeting: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Open+NeuroFedora+Meeting=20230213T13=%3A=1 or you can use this command in a terminal: $ date --date='TZ="UTC" 1300 Monday' The meeting will be chaired by @ankursinha. The agenda for the meeting is: - New introductions and roll call. - Tasks from last meeting: https://meetbot.fedoraproject.org/latest/neurofedora - Open Pagure tickets: https://pagure.io/neuro-sig/NeuroFedora/issues?status=Open=S%3A+Next+meeting - Package health check: https://packager-dashboard.fedoraproject.org/dashboard?groups=neuro-sig - Open package reviews check: https://bugzilla.redhat.com/show_bug.cgi?id=fedora-neuro - CompNeuro lab compose status check for F38: https://koji.fedoraproject.org/koji/packageinfo?packageID=30691 - Neuroscience query of the week - Next meeting day, and chair. - Open floor. We hope to see you there! The meeting announcement is also posted on the NeuroFedora blog here: https://neuroblog.fedoraproject.org/2023/02/13/next-open-neurofedora-meeting-13-february-1300-utc.html You can learn more about NeuroFedora here: https://neuro.fedoraproject.org -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: What should we do about "shopping list" groups in comps?
On Wed, Feb 01, 2023 07:51:08 -0800, Adam Williamson wrote: > snip > I'd say you've misunderstood how comps groups work, because all the > packages are tagged as optional, which means people need to use an > obscure option to a kickstart or dnf to install them. If you indeed > want a normal 'dnf groupinstall neuron-modelling-simulators' or > '@neuron-modelling-simulators' in a kickstart to install all the > packages, they should be set to 'default' or 'mandatory', not > 'optional'. The difference between 'default' and 'mandatory' is that if > a package is listed as 'mandatory', it *must* remain installed for dnf > to consider the group as 'installed'. If it's listed as 'default', it > will be installed by default when the group is, but can be removed > without the group being considered to have been removed. Ah, that explains it. I think we need to probably use "default" there then. I'll discuss it with the neuro-sig and open a PR. -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
pdfpc license changed from GPLv2+ to GPLv3+
Hi folks, Just a quick FYI. Upstream changed the pdfpc license from GPLv2+ to GPLv3+. The package in Fedora has also been updated now. -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: What should we do about "shopping list" groups in comps?
Hello, On Tue, Jan 31, 2023 14:39:27 -0800, Adam Williamson wrote: > snip > neuron-modelling-simulators We only added this to allow users do use a groupinstall to install all their modelling related tools in one go. It isn't intended for use in anaconda. So, happy to remove it, but is there another way of allowing users to pull in all these packages at once? Should we use a meta package instead of a comps group (or have I misunderstood how dnf package groups work)? -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Open NeuroFedora Meeting: 1300 UTC on Monday, 30 January (today)
Hello everyone, Please join us at the next Open NeuroFedora team meeting on Monday 30th January at 1300UTC in #fedora-neuro on Matrix or IRC (Libera.chat). The meeting is a public meeting, and open for everyone to attend. You can join us over: Matrix: https://matrix.to/#/#neuro:fedoraproject.org IRC: https://webchat.libera.chat/?channels=#fedora-neuro You can use this link to see the local time for the meeting: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Open+NeuroFedora+Meeting=20230130T13=%3A=1 or you can use this command in a terminal: $ date --date='TZ="UTC" 1300 Monday' The meeting will be chaired by @ankursinha. The agenda for the meeting is: - New introductions and roll call. - Tasks from last meeting: https://meetbot.fedoraproject.org/latest/neurofedora - Open Pagure tickets: https://pagure.io/neuro-sig/NeuroFedora/issues?status=Open=S%3A+Next+meeting - Package health check: https://packager-dashboard.fedoraproject.org/dashboard?groups=neuro-sig - Open package reviews check: https://bugzilla.redhat.com/show_bug.cgi?id=fedora-neuro - CompNeuro lab compose status check for F38: https://koji.fedoraproject.org/koji/packageinfo?packageID=30691 - Neuroscience query of the week - Next meeting day, and chair. - Open floor. We hope to see you there! The meeting announcement is also posted on the NeuroFedora blog here: https://neuroblog.fedoraproject.org/2023/01/30/next-open-neurofedora-meeting-30-january-1300-utc.html You can learn more about NeuroFedora here: https://neuro.fedoraproject.org -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Next Open NeuroFedora Meeting: 1300 UTC on Monday, 16 January
Hello everyone, Please join us at the next Open NeuroFedora team meeting on Monday 16th January at 1300UTC in #fedora-neuro on Matrix or IRC (Libera.chat). The meeting is a public meeting, and open for everyone to attend. You can join us over: Matrix: https://matrix.to/#/#neuro:fedoraproject.org IRC: https://webchat.libera.chat/?channels=#fedora-neuro You can use this link to see the local time for the meeting: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Open+NeuroFedora+Meeting=20230116T13=%3A=1 or you can use this command in a terminal: $ date --date='TZ="UTC" 1300 Monday' The meeting will be chaired by @ankursinha. The agenda for the meeting is: - New introductions and roll call. - Tasks from last meeting: https://meetbot.fedoraproject.org/latest/neurofedora - Open Pagure tickets: https://pagure.io/neuro-sig/NeuroFedora/issues?status=Open=S%3A+Next+meeting - Package health check: https://packager-dashboard.fedoraproject.org/dashboard?groups=neuro-sig - Open package reviews check: https://bugzilla.redhat.com/show_bug.cgi?id=fedora-neuro - CompNeuro lab compose status check for F38: https://koji.fedoraproject.org/koji/packageinfo?packageID=30691 - Neuroscience query of the week - Next meeting day, and chair. - Open floor. We hope to see you there! The meeting announcement is also posted on the NeuroFedora blog here: https://neuroblog.fedoraproject.org/2023/01/13/next-open-neurofedora-meeting-16-january-1300-utc.html You can learn more about NeuroFedora here: https://neuro.fedoraproject.org -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Next Open NeuroFedora Meeting: 1300 UTC on Monday, 05 December (Today)
Hello everyone, Please join us at the next Open NeuroFedora team meeting on Monday 5th December(today!) at 1300UTC in #fedora-neuro on Matrix or IRC (Libera.chat). The meeting is a public meeting, and open for everyone to attend. You can join us over: Matrix: https://matrix.to/#/#neuro:fedoraproject.org IRC: https://webchat.libera.chat/?channels=#fedora-neuro You can use this link to see the local time for the meeting: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Open+NeuroFedora+Meeting=20221205T13=%3A=1 or you can use this command in a terminal: $ date --date='TZ="UTC" 1300 today' The meeting will be chaired by @ankursinha. The agenda for the meeting is: - New introductions and roll call. - Tasks from last meeting: https://meetbot.fedoraproject.org/latest/neurofedora - Open Pagure tickets: https://pagure.io/neuro-sig/NeuroFedora/issues?status=Open=S%3A+Next+meeting - Package health check: https://packager-dashboard.fedoraproject.org/dashboard?groups=neuro-sig - Open package reviews check: https://bugzilla.redhat.com/show_bug.cgi?id=fedora-neuro - CompNeuro lab compose status check for F38: https://koji.fedoraproject.org/koji/packageinfo?packageID=30691 - Neuroscience query of the week - Next meeting day, and chair. - Open floor. We hope to see you there! The meeting announcement is also posted on the NeuroFedora blog here: https://neuroblog.fedoraproject.org/2022/12/05/next-open-neurofedora-meeting-5-december-1300-utc.html You can learn more about NeuroFedora here: https://neuro.fedoraproject.org -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: A very brief introduction.
Hi Jaime, Welcome to the community, again. This would be the place to start for package maintenance: https://docs.fedoraproject.org/en-US/package-maintainers/Joining_the_Package_Maintainers/ There are lots of us sponsors around, so please go through the process and we'll be happy to help you with it and sponsor you: https://docs.pagure.org/fedora-sponsors/ See you around :) -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Ask Fedora: user reporting trouble with R-pi 4. Could someone please take a look?
On Thu, Nov 24, 2022 16:22:02 +, Peter Robinson wrote: > > I replied, but he doesn't actually provide much information to be able > to actually reply with certainly. Thanks. Yeh, it often takes a little bit of back and forth to obtain the necessary info. I didn't know what to ask for, or I'd have started with that already. > Also may be better to send queries around arm to the arm list, I saw > this by luck. Unfortunately, I'm not an arm user myself, so I'm not the arm lists. Would it be possible for some of the arm folks to look at the forum from time to time please? It's noted as the official support channel on the website, so it'll be the first place folks will come to. We can point them to the arm list if that's preferred too. Please let us know and I can announce it on the forum there so folks know. -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Ask Fedora: user reporting trouble with R-pi 4. Could someone please take a look?
Hi folks, We've had a post this morning from a user having trouble with R-pi 4 using the F37 ARM 64 images. Could someone with some experience in this area please take a look and maybe help them out? https://ask.fedoraproject.org/t/fedora-arm-64-does-not-work-on-raspberry-pi-4/29111 -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Next Open NeuroFedora Meeting: 1300 UTC on Monday, 21 November (Today)
Hello everyone, Please join us at the next Open NeuroFedora team meeting on Monday 21st November(today!) at 1300UTC in #fedora-neuro on Matrix or IRC (Libera.chat). The meeting is a public meeting, and open for everyone to attend. You can join us over: Matrix: https://matrix.to/#/#neuro:fedoraproject.org IRC: https://webchat.libera.chat/?channels=#fedora-neuro You can use this link to see the local time for the meeting: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Open+NeuroFedora+Meeting=20221121T13=%3A=1 or you can use this command in a terminal: $ date --date='TZ="UTC" 1300 today' The meeting will be chaired by @ankursinha. The agenda for the meeting is: - New introductions and roll call. - Tasks from last meeting: https://meetbot.fedoraproject.org/latest/neurofedora - Open Pagure tickets: https://pagure.io/neuro-sig/NeuroFedora/issues?status=Open=S%3A+Next+meeting - Package health check: https://packager-dashboard.fedoraproject.org/dashboard?groups=neuro-sig - Open package reviews check: https://bugzilla.redhat.com/show_bug.cgi?id=fedora-neuro - CompNeuro lab compose status check for F38: https://koji.fedoraproject.org/koji/packageinfo?packageID=30691 - Neuroscience query of the week - Next meeting day, and chair. - Open floor. We hope to see you there! The meeting announcement is also posted on the NeuroFedora blog here: https://neuroblog.fedoraproject.org/2022/11/21/next-open-neurofedora-meeting-21-november-1300-utc.html You can learn more about NeuroFedora here: https://neuro.fedoraproject.org -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
NeuroFedora review swap: python-formulaic
Hi folks, Would someone like to swap reviews please? I'd like to get python-formulaic reviewed and included in Fedora[1]. It's required to update python-pybids to the latest version[2] It should be a straightforward review. Unofficial reviews from candidate package maintainers looking for review practice are also most welcome. [1] https://bugzilla.redhat.com/show_bug.cgi?id=2140295 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1996270 -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Next Open NeuroFedora Meeting: 1300 UTC on Monday, 07 November (Today)
Hello everyone, Please join us at the next Open NeuroFedora team meeting on Monday 7th November(today!) at 1300UTC in #fedora-neuro on Matrix or IRC (Libera.chat). The meeting is a public meeting, and open for everyone to attend. You can join us over: Matrix: https://matrix.to/#/#neuro:fedoraproject.org IRC: https://webchat.libera.chat/?channels=#fedora-neuro You can use this link to see the local time for the meeting: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Open+NeuroFedora+Meeting=20221107T13=%3A=1 or you can use this command in a terminal: $ date --date='TZ="UTC" 1300 today' The meeting will be chaired by @ankursinha. The agenda for the meeting is: - New introductions and roll call. - Tasks from last meeting: https://meetbot.fedoraproject.org/fedora-neuro/2022-10-24/neurofedora.2022-10-24-13.00.log.html - Open Pagure tickets: https://pagure.io/neuro-sig/NeuroFedora/issues?status=Open=S%3A+Next+meeting - Package health check: https://packager-dashboard.fedoraproject.org/dashboard?groups=neuro-sig - Open package reviews check: https://bugzilla.redhat.com/show_bug.cgi?id=fedora-neuro - CompNeuro lab compose status check for F37/F38: https://koji.fedoraproject.org/koji/packageinfo?packageID=30691 - Neuroscience query of the week - Next meeting day, and chair. - Open floor. We hope to see you there! The meeting announcement is also posted on the NeuroFedora blog here: https://neuroblog.fedoraproject.org/2022/11/06/next-open-neurofedora-meeting-07-november-1300-utc.html You can learn more about NeuroFedora here: https://neuro.fedoraproject.org -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Non responsive maintainer check for ultrafredde
Hi folks, Would anyone know how to contact @ultrafredde please? A new contributor opened a PR to update the task package quite a while back, but there's been no response either on the PR or on the bug. @ultrafredde only maintains the one package, task. Here's the output of fedora-active-user: $ python ./fedora_active_user.py --user ultrafredde --email ultrafre...@gmail.com Last login in FAS: ultrafredde 2021-03-12 Last action on koji: Fri, 09 Sep 2022 tag_package_owners entry created by humaton [still active] Last package update on bodhi: 2011-03-04 01:10:36 on package task-1.9.4-1.el6 Last actions performed according to fedmsg: - org.fedoraproject.prod.bugzilla.bug.update on 2022-01-05 08:09:04 - org.fedoraproject.prod.bugzilla.bug.update on 2022-01-05 08:09:04 - org.fedoraproject.prod.bugzilla.bug.update on 2021-11-30 18:27:24 - org.fedoraproject.prod.bugzilla.bug.update on 2021-11-30 18:27:24 - org.fedoraproject.prod.bugzilla.bug.update on 2021-11-04 15:44:53 - org.fedoraproject.prod.bugzilla.bug.update on 2021-11-04 14:46:23 Last email on mailing list: On 2009-09-01T13:50:04Z ultrafre...@gmail.com emailed as Federico Hernandez on https://lists.fedoraproject.org/archives/api/list/packag...@lists.fedoraproject.org/ On 2009-08-24T19:35:46Z ultrafre...@gmail.com emailed as Federico Hernandez on https://lists.fedoraproject.org/archives/api/list/packag...@lists.fedoraproject.org/ On 2009-07-06T20:18:57Z ultrafre...@gmail.com emailed as Federico Hernandez on https://lists.fedoraproject.org/archives/api/list/packag...@lists.fedoraproject.org/ On 2009-06-20T23:20:28Z ultrafre...@gmail.com emailed as Federico Hernandez on https://lists.fedoraproject.org/archives/api/list/packag...@lists.fedoraproject.org/ On 2009-06-20T22:04:29Z ultrafre...@gmail.com emailed as Federico Hernandez on https://lists.fedoraproject.org/archives/api/list/packag...@lists.fedoraproject.org/ On 2009-06-09T17:38:24Z ultrafre...@gmail.com emailed as Federico Hernandez on https://lists.fedoraproject.org/archives/api/list/packag...@lists.fedoraproject.org/ On 2009-06-09T17:02:02Z ultrafre...@gmail.com emailed as Federico Hernandez on https://lists.fedoraproject.org/archives/api/list/packag...@lists.fedoraproject.org/ Bugzilla activity 2 bugs assigned, cc or on which ultrafre...@gmail.com commented ERROR:active-user:https://bugzilla.redhat.com/docs/en/html/api/core/v1/general.html#authentication for details on using the 'Authorization' header. at /usr/share/perl5/vendor_perl/SOAP/Lite.pm line 2855.\n"> Here's the non-responsive package maintainer bug on Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2138642 Here are the open bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1872005 https://bugzilla.redhat.com/show_bug.cgi?id=1872005 and here is the pending PR: https://src.fedoraproject.org/rpms/task/pull-request/1 -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Next Open NeuroFedora Meeting: 1300 UTC on Monday, 24 October (Today)
Hello everyone, Please join us at the next Open NeuroFedora team meeting on Monday 24th October(today!) at 1300UTC in #fedora-neuro on Matrix or IRC (Libera.chat). The meeting is a public meeting, and open for everyone to attend. You can join us over: Matrix: https://matrix.to/#/#neuro:fedoraproject.org IRC: https://webchat.libera.chat/?channels=#fedora-neuro You can use this link to see the local time for the meeting: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Open+NeuroFedora+Meeting=20221024T13=%3A=1 or you can use this command in a terminal: $ date --date='TZ="UTC" 1300 today' The meeting will be chaired by @ankursinha. The agenda for the meeting is: - New introductions and roll call. - Tasks from last meeting: https://meetbot.fedoraproject.org/fedora-neuro/2022-10-10/neurofedora.2022-10-10-13.00.html - Open Pagure tickets: https://pagure.io/neuro-sig/NeuroFedora/issues?status=Open=S%3A+Next+meeting - Package health check: https://packager-dashboard.fedoraproject.org/neuro-sig - Open package reviews check: https://bugzilla.redhat.com/show_bug.cgi?id=fedora-neuro - CompNeuro lab compose status check for F37/F38: https://koji.fedoraproject.org/koji/packageinfo?packageID=30691 - Neuroscience query of the week - Next meeting day, and chair. - Open floor. We hope to see you there! The meeting announcement is also posted on the NeuroFedora blog here: https://neuroblog.fedoraproject.org/2022/10/21/next-open-neurofedora-meeting-24-october-1300-utc.html You can learn more about NeuroFedora here: https://neuro.fedoraproject.org -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Next Open NeuroFedora Meeting: 1300 UTC on Monday, 10 October September (Today)
Hello everyone, Please join us at the next Open NeuroFedora team meeting on Monday 10th October(today!) at 1300UTC in #fedora-neuro on Matrix or IRC (Libera.chat). The meeting is a public meeting, and open for everyone to attend. You can join us over: Matrix: https://matrix.to/#/#neuro:fedoraproject.org IRC: https://webchat.libera.chat/?channels=#fedora-neuro You can use this link to see the local time for the meeting: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Open+NeuroFedora+Meeting=20221010T13=%3A=1 or you can use this command in a terminal: $ date --date='TZ="UTC" 1300 today' The meeting will be chaired by @ankursinha. The agenda for the meeting is: - New introductions and roll call. - Tasks from last meeting: https://meetbot.fedoraproject.org/fedora-neuro/2022-10-10/neurofedora.2022-10-10-13.00.html - Open Pagure tickets: https://pagure.io/neuro-sig/NeuroFedora/issues?status=Open=S%3A+Next+meeting - Package health check: https://packager-dashboard.fedoraproject.org/neuro-sig - Open package reviews check: https://bugzilla.redhat.com/show_bug.cgi?id=fedora-neuro - CompNeuro lab compose status check for F37/F38: https://koji.fedoraproject.org/koji/packageinfo?packageID=30691 - Neuroscience query of the week - Next meeting day, and chair. - Open floor. We hope to see you there! The meeting announcement is also posted on the NeuroFedora blog here: https://neuroblog.fedoraproject.org/2022/10/09/next-open-neurofedora-meeting-10-october-1300-utc.html You can learn more about NeuroFedora here: https://neuro.fedoraproject.org -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Next Open NeuroFedora Meeting: 1300 UTC on Monday, 26 September (Today)
Hello everyone, Please join us at the next Open NeuroFedora team meeting on Monday 26th September(today!) at 1300UTC in #fedora-neuro on Matrix or IRC (Libera.chat). The meeting is a public meeting, and open for everyone to attend. You can join us over: Matrix: https://matrix.to/#/#neuro:fedoraproject.org IRC: https://webchat.libera.chat/?channels=#fedora-neuro You can use this link to see the local time for the meeting: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Open+NeuroFedora+Meeting=20220926T13=%3A=1 or you can use this command in a terminal: $ date --date='TZ="UTC" 1300 today' The meeting will be chaired by @ankursinha. The agenda for the meeting is: - New introductions and roll call. - Tasks from last meeting: https://meetbot.fedoraproject.org/fedora-neuro/2022-09-12/neurofedora.2022-09-12-13.00.html - Open Pagure tickets: https://pagure.io/neuro-sig/NeuroFedora/issues?status=Open=S%3A+Next+meeting - Package health check: https://packager-dashboard.fedoraproject.org/neuro-sig - Open package reviews check: https://bugzilla.redhat.com/show_bug.cgi?id=fedora-neuro - CompNeuro lab compose status check for F37/F38: https://koji.fedoraproject.org/koji/packageinfo?packageID=30691 - Neuroscience query of the week - Next meeting day, and chair. - Open floor. We hope to see you there! The meeting announcement is also posted on the NeuroFedora blog here: https://neuroblog.fedoraproject.org/2022/09/24/next-open-neurofedora-meeting-26-September-1300-utc.html You can learn more about NeuroFedora here: https://neuro.fedoraproject.org -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Python packages using "maturin"
Hiya, On Mon, Sep 12, 2022 13:05:31 -0400, Ben Beasley wrote: > The orjson package itself is written in Rust, so it’s probably best > just to do without orjson for the python-cattrs tests if you’re not > inclined to go down that rabbit hole. > > That said, it would be great to have a python-orjson package in > Fedora, and I’ve considered attempting it but never found the time. > For a long time, it was not packageable because it required a nightly > Rust toolchain, but it’s my understanding that it now builds on stable > Rust. Yeh, I think I'll try to do without orjson in the short term if at all possible, just to get the packages all building etc. again, and we can look into orjson/maturin when time permits (if someone doesn't beat us to it). -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Python packages using "maturin"
Hi folks, While trying to unretire python-cattrs[1], I ended up falling down a rabbit hole of deps. One of its optional test deps, orjson[2], requires "maturin"[3] to build. maturin looks like something that helps publish rust code as python packages. I think I may have come across this before, but it's the first time I've actually bothered to look into it. (I know nothing about rust so I tend to steer clear of rust projects). So, has anyone else come across this before? Has anyone looked into packaging it? Given my non-existent rust knowledge, I'd like to avoid packaging/maintaining maturin if at all possible. Is there a way to not use it perhaps (unlikely, I know)? [1] https://src.fedoraproject.org/rpms/python-cattrs [2] https://pypi.org/project/orjson/ [3] https://pypi.org/project/maturin/ -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Orphaned packages looking for new maintainers
I've taken a few more (a few for the neuro-sig): > Depending on: mcpanel (1), status change: 2022-08-30 (0 weeks ago) > eegview (maintained by: aekoroglu, ankursinha, neuro-sig) > eegview-0.0-15.fc37.src requires mcpanel-devel = 0.0-15.fc37 > eegview-0.0-15.fc37.x86_64 requires libmcpanel.so.0()(64bit) Taken for neuro-sig, co-maintainers welcome > Depending on: python-aiofiles (5), status change: 2022-08-30 (0 weeks ago) > > > python-matrix-nio (maintained by: ankursinha) > python-matrix-nio-0.19.0-6.fc38.src requires > python3dist(aiofiles) = 0.7 > python3-matrix-nio-0.19.0-6.fc38.noarch requires > python3.11dist(aiofiles) = 0.7 Taken for myself, co-maintainers welcome. > Depending on: python-piexif (3), status change: 2022-08-30 (0 weeks ago) > > vimiv-qt (maintained by: ankursinha) > vimiv-qt-0.8.0-7.fc37.x86_64 requires python3-piexif = > 1.1.3-14.fc37 Taken for myself, co-maintainers welcome. > Depending on: python-rply (4), status change: 2022-08-30 (0 weeks ago) > python-rnc2rng (maintained by: iztokf) > python-rnc2rng-2.6.6-3.fc37.src requires python3dist(rply) = > 0.7.8 > python3-rnc2rng-2.6.6-3.fc37.noarch requires > python3.11dist(rply) = 0.7.8 > > python-citeproc-py (maintained by: ankursinha, ignatenkobrain, > neuro-sig) > python-citeproc-py-0.6.0-5.fc37.src requires > python3dist(rnc2rng) = 2.6.6 > > python-duecredit (maintained by: ankursinha, neuro-sig) > python-duecredit-0.9.1-5.fc37.src requires > python3dist(citeproc-py) = 0.6 > python3-duecredit-0.9.1-5.fc37.noarch requires > python3.11dist(citeproc-py) > = 0.6, python3dist(citeproc-py) = 0.6 > > python-pybids (maintained by: ankursinha, neuro-sig) > python-pybids-0.13.1-5.fc37.src requires python3dist(duecredit) > = 0.9.1 Taken for neuro-sig, co-maintainers welcome > Depending on: rtfilter (2), status change: 2022-08-30 (0 weeks ago) > mcpanel (maintained by: orphan) > mcpanel-0.0-15.fc37.i686 requires librtfilter.so.1 > mcpanel-0.0-15.fc37.src requires rtfilter-devel = 1.1-16.fc37 > mcpanel-0.0-15.fc37.x86_64 requires librtfilter.so.1()(64bit) > > eegview (maintained by: aekoroglu, ankursinha, neuro-sig) > eegview-0.0-15.fc37.src requires mcpanel-devel = 0.0-15.fc37 > eegview-0.0-15.fc37.x86_64 requires libmcpanel.so.0()(64bit) Taken for neuro-sig, co-maintainers welcome -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Orphaned packages looking for new maintainers
> tasksh orphan 0 weeks ago Taken tasksh over to begin with. Co-maintainers welcome. -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Let's enable Koschei for all packages automatically
On Thu, Aug 25, 2022 15:58:12 +0200, Fabio Valentini wrote: > Yeah that should be pretty simple. Get list of source packages in > $release, paste it into the "Add packages" page, set release combobox > to $release, submit. > I do that regularly for all Rust packages. The rust-sig packages are also set to automatically be tracked by Koschei from the looks of it and I expect this can then be done for all packages instead of for individual SIGs: https://pagure.io/fedora-infra/ansible/blob/main/f/roles/openshift-apps/koschei/vars/production.yml#_45 -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Next Open NeuroFedora Meeting: 1300 UTC on Monday, 15th August (Today)
Hello everyone, Please join us at the next Open NeuroFedora team meeting on Monday 15th August(today!) at 1300UTC in #fedora-neuro on Matrix or IRC (Libera.chat). The meeting is a public meeting, and open for everyone to attend. You can join us over: Matrix: https://matrix.to/#/#neuro:fedoraproject.org IRC: https://webchat.libera.chat/?channels=#fedora-neuro You can use this link to see the local time for the meeting: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Open+NeuroFedora+Meeting=20220815T13=%3A=1 or you can use this command in a terminal: $ date --date='TZ="UTC" 1300 today' The meeting will be chaired by @ankursinha. The agenda for the meeting is: - New introductions and roll call. - Tasks from last meeting: https://meetbot.fedoraproject.org/fedora-neuro/2022-08-01/neurofedora.2022-08-01-13.00.html - Open Pagure tickets: https://pagure.io/neuro-sig/NeuroFedora/issues?status=Open=S%3A+Next+meeting - Package health check: https://packager-dashboard.fedoraproject.org/neuro-sig - Open package reviews check: https://bugzilla.redhat.com/show_bug.cgi?id=fedora-neuro - CompNeuro lab compose status check for F36/F37: https://koji.fedoraproject.org/koji/packageinfo?packageID=30691 - Neuroscience query of the week - Next meeting day, and chair. - Open floor. We hope to see you there! The meeting announcement is also posted on the NeuroFedora blog here: https://neuroblog.fedoraproject.org/2022/08/11/next-open-neurofedora-meeting-15-August-1300-utc.html You can learn more about NeuroFedora here: https://neuro.fedoraproject.org -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
dcmtk soname bump in rawhide (and stable releases)
Hi folks, Just an FYI: I'm updating dcmtk in rawhide from 3.6.6 to 3.6.7, and it includes a soname bump (dcmtk bumps soname for every patch release..). This update also includes a number of security fixes, so I've filed a ticket with FESCo to request permission to also push the update to stable Fedora releases: https://pagure.io/fesco/issue/2848 Only two packages depend on dcmtk: - ctk (I maintain this) - OpenImageIO (Richard maintains this) I'm already in touch with Richard and will co-ordinate the side-tags/updates etc. as required. -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Is `/etc/sysconfig/desktop` still used?
> > 2) is still sourced from '/etc/X11/xinit/Xclients' for two envvars: > - 'DESKTOP' - nickname for one from recognized sessions (GNOME, KDE, MATE > or LXDE). > - 'PREFERRED' - in case when 'DESKTOP' unset/unrecognized, this variable > should be path for program starting graphical session (for example, > '/usr/bin/mate-session'). > '/etc/X11/xinit/Xclients' file is in package 'xorg-x11-xinit' and is > needed e.g. for manual X session start via startx or xinit. > This file/package is actual, present in Fedora 36 (not sure about > Centos/RHEL, I'm not using its now). Thanks very much for that Franta. I'll make a note of this and leave that bit in the docs then. -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Is `/etc/sysconfig/desktop` still used?
Hi folks, While updating this quick-doc, I came across the last section where `/etc/sysconfig/desktop` is mentioned as a config file to change default desktop environment etc. https://docs.fedoraproject.org/en-US/quick-docs/switching-desktop-environments/ I haven't been able to find any documentation on it, and no package in Fedora owns this file either. Would someone please be able to note if this file is still in use, and point to some documentation we could refer to? I've also got a PR updating the page here. Reviews most most welcome: https://pagure.io/fedora-docs/quick-docs/pull-request/474 -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Comaintainer(s) wanted for qt5-qtwebengine
On Wed, Jul 20, 2022 17:49:05 +0200, Kevin Kofler via devel wrote: > Hi Ankur, Hi Kevin, > > If you want to go straight for 5.15.10, then the first step would be to get > 5.15.10 into Rawhide, and then go through the same steps above to push > 5.15.10 to the stable releases. Thanks for that. It looks straightforward enough ;) I think I'll start with pushing 5.15.9 to F35/36 first to familiarise myself with the package. Once that's done, we can look at the 5.15.10 update next. I should be able to work on this from tomorrow evening. I'll keep everyone in the loop. -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Comaintainer(s) wanted for qt5-qtwebengine
Hi Kevin,
On Wed, Jul 20, 2022 03:58:41 +0200, Kevin Kofler via devel wrote:
> So, since all current maintainers of qt5-qtwebengine, including me, are
> failing badly at keeping the package up to date with security fixes, this is
> an urgent plea for help. The current situation is not acceptable, any
> helping hands to improve on it would be extremely welcome. I have admin
> rights to the package, so I can add comaintainers that wish so.
Thanks for maintaining the package. I heavily rely on Qutebrowser, and
since it depends on qt5-qtwebengine{,-freeworld}, I'll be happy to help
in whatever capacity I can. I usually use up my Fedora time working on
our neuro-sig packages, but if it's a few hours every few months to
update qt5-qtwebengine, I'm happy to help.
What would the first step to pushing 5.15.9 to F35/F36 be for a start?
--
Thanks,
Regards,
Ankur Sinha "FranciscoD" (He / Him / His) |
https://fedoraproject.org/wiki/User:Ankursinha
Time zone: Europe/London
signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Re: Script to get all deps of a package (for soname bumps etc.)
On Mon, Jul 18, 2022 06:52:26 -0500, Richard Shaw wrote:
>
Hi Richard,
Thanks very much for sharing your script.
> I use this script which I'm pretty sure I pieced together from some of
> Sergio's
> logic some time ago. I like that it saves them to a file so I can iterate over
> them with other scripts.
>
> $ cat ~/.local/bin/needs_rebuilding
> #!/bin/bash
>
> if [ $# -eq 0 ]
> then
> echo "No arguments supplied"
> echo "Usage: $0 [pkgname] ..."
> exit 0
> fi
>
> provides=$(mktemp -t provides-XX)
> deps=$(mktemp -t rawdeps-XX)
>
> # Only break on newline not space or tab in for loops
> IFS=$'\n'
>
> for pkg in "$@"; do
> echo "Checking for provides in $pkg."
> dnf --quiet repoquery --repoid=rawhide --provides "$pkg" >> $provides
> done
>
> sed -i "/^bundled/d" $provides
> sort -u -o $provides $provides
>
> echo "Found $(wc -l $provides | awk '{print $1}') provides to be evaluated."
^
I think this bit isn't required because as Maxwell confirmed, repoquery
is smart enough to take all provides into account. However, if one does
want to see what capability causes the dependency, I think we must go
over each capability individually.
So, after the discussion here, I've shamelessly picked bits from all
your responses and scripts and have come up with these two:
https://pagure.io/fedora-get-package-dependencies/blob/main/f/get_deps.sh
gives just a list of all deps, without going over each capability
individually
https://pagure.io/fedora-get-package-dependencies/blob/main/f/get_deps_verbose.sh
gives a more verbose report listing what capability of the package other
packages are dependent on.
If folks can please test these out and make more improvements, I can
open a PR in the package-maintainer docs to list these there to give
them more visibility.
--
Thanks,
Regards,
Ankur Sinha "FranciscoD" (He / Him / His) |
https://fedoraproject.org/wiki/User:Ankursinha
Time zone: Europe/London
signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Re: Script to get all deps of a package (for soname bumps etc.)
On Wed, Jul 13, 2022 12:54:37 -0500, Maxwell G wrote:
> On 22/07/13 05:35PM, Ankur Sinha wrote:
> > > This is what we (I) aren't sure of, and that's why I first obtain the
> > capabilities manually and then query for them. If someone can confirm
> > that this is indeed the case, that would certainly simplify things.
>
> Here is confirmation:
>
> ```
> sudo dnf repoquery --repo=rawhide{,-source} -q --whatrequires
> python3-setuptools | grep '\.src' | grep yt-dlp
> yt-dlp-0:2022.06.29-2.fc37.src
>
> $ sudo dnf repoquery --repo=rawhide-source -q --requires yt-dlp | grep
> setuptools
> python3dist(setuptools) >= 40.8
> ```
>
> yt-dlp depends on one of `python3-setuptool`'s virtual provides, and it is
> still
> found when using the command I gave to find which packages BuildRequire
> a certain other package. This also works when querying runtime
> dependencies:
>
> ```
> $ sudo dnf repoquery -q --repo=rawhide --requires reuse | grep setuptools
> python3.11dist(setuptools)
> $ sudo dnf repoquery -q --repo=rawhide --whatrequires python3-setuptools |
> grep reuse
> reuse-0:1.0.0-2.fc37.noarch
> ```
Thanks very much!
That really simplifies it to a single command.
--
Thanks,
Regards,
Ankur Sinha (He / Him / His) | https://ankursinha.in
Time zone: Europe/London
signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Re: Script to get all deps of a package (for soname bumps etc.)
Hello, Thanks for that---some really useful bits in there that I wasn't aware of. On Wed, Jul 13, 2022 10:09:10 -0500, Maxwell G wrote: > I don't think you need to do all of this. With > > ``` > sudo dnf repoquery --repo=rawhide -q --whatrequires dcmtk | xargs sudo dnf > repoquery --repo=rawhide -q --latest-limit 1 --source > ``` > > AFAIK, dnf repoquery is smart enough to figure out the virtual provides > by itself. This is what we (I) aren't sure of, and that's why I first obtain the capabilities manually and then query for them. If someone can confirm that this is indeed the case, that would certainly simplify things. -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Script to get all deps of a package (for soname bumps etc.)
Hi folks, I'm sure this exists somewhere but I couldn't find one, so with the help of folks on #fedora-devel, I hacked up this simple shell script to get the all the deps of a package. It's useful when your package update includes a soname bump, and you need to figure out what packages need to be rebuilt etc. https://pagure.io/fedora-get-package-dependencies/blob/main/f/get_deps.sh It lists all the capabilities of the package, and then asks dnf to list what packages require any of them. It should cover most cases. If someone has a better script, please do share it, and please feel free to improve this one too. I'm more than happy to give everyone access to the repo and/or hand it over to a particular package maintainers related pagure group. Ideally, a script of this form should be noted in the package-maintainer docs so we can all use it. -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
