License change: python-email-validator 2.1.1 is Unlicense (was CC0-1.0)

[Ben Beasley]

Beginning with version 2.1.1, the license of python-email-validator has 
changed from CC0-1.0 to Unlicense.


Note that CC0-1.0 is no longer allowed for code in Fedora, but 
python-email-validator was covered by the exception for pre-existing 
code in Fedora.


Version 2.1.1 will be built as an update for F39 and later; F38 and 
EPEL8/EPEL9 will remain on older 1.x releases.

--
___
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: rpmbuild problem with rust code

[Josh Stone]

On 2/26/24 1:41 PM, Richard W.M. Jones wrote:
> It's a bit unfortunate that Rust used the shebang syntax here,
> although in practice they couldn't be confused as these files
> shouldn't ever be executable.

It's _possible_ to play comment tricks for executable rust scripts,
because rustc allows and ignores actual shebang lines.

#!/bin/bash -e
#![cfg(unix)] /* (any attribute as a shell comment)
# shell here to self-compile
rustc "$0" -o ./foo
exec ./foo "$@"
(end rust comment) */
// continue in rust here
fn main() { ... }

There is also a real "cargo script" feature in development:
https://github.com/rust-lang/cargo/issues/12207

> It's also correct that RPM worries about this file since it is
> installed (in debuginfo) and appears to contain a shebang.
> 
>> Is there a way to tell rpmbuild not to worry about this?
> 
> rust.spec has this in %prep, and /usr/lib/rpm/redhat/brp-mangle-shebangs
> only seems to care about executable files, so this should help:
> 
>   # Sometimes Rust sources start with #![...] attributes, and "smart" editors 
> think
>   # it's a shebang and make them executable. Then brp-mangle-shebangs gets 
> upset...
>   find -name '*.rs' -type f -perm /111 -exec chmod -v -x '{}' '+'

I may have to make that smarter if "cargo script" gets used.

For now though, clearing everything should be fine.
--
___
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: rpmbuild problem with rust code

[Steve Grubb]

Hello,

On Monday, February 26, 2024 4:38:35 PM EST Fabio Valentini wrote:
> > I've run across a strange problem building a package that has some rust
> > files in it. The build goes fine until the end when it starts to check for
> > shebangs. It ends like this:
> > 
> > 
> > /usr/src/debug/suricata-7.0.3-1.fc41.x86_64/rust/vendor/alloc-no-stdlib/s
> > rc/ lib.rs has shebang which doesn't start with '/' ([no_std])
> > 
> > When I check the file, I find this:
> > #![no_std]
> > 
> > #[macro_use]
> > mod allocated_memory;
> > mod stack_allocator;
> > mod allocated_stack_memory;
> > 
> > Not being a rust programmer, I have no good idea what the code is doing.
> > I can't patch this code to move it off the first line because it's
> > vendored code.
> > 
> > Is there a way to tell rpmbuild not to worry about this?
> 
> The solution should be simple - remove stray +x permissions from all *.rs
> files.

Thanks. That did it.

-Steve

--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: rpmbuild problem with rust code

[Artur Frenszek-Iwicki]

https://doc.rust-lang.org/reference/attributes.html
If I understand this page of The Rust Reference correctly,
then moving the #![no_std] attribute from the first line of the file
shouldn't break anything. So you can try side-stepping the issue
by patching the file and adding "// lol pointless comment" at the top.

A.FI.
--
___
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: rpmbuild problem with rust code

[Richard W.M. Jones]

On Mon, Feb 26, 2024 at 04:25:02PM -0500, Steve Grubb wrote:
> Hello,
> 
> I've run across a strange problem building a package that has some rust files 
> in it. The build goes fine until the end when it starts to check for 
> shebangs. 
> It ends like this:
> 
> /usr/src/debug/suricata-7.0.3-1.fc41.x86_64/rust/vendor/alloc-no-stdlib/src/
> lib.rs has shebang which doesn't start with '/' ([no_std])
> 
> When I check the file, I find this:
> #![no_std]
> 
> #[macro_use]
> mod allocated_memory;
> mod stack_allocator;
> mod allocated_stack_memory;
> 
> Not being a rust programmer, I have no good idea what the code is doing. I 
> can't patch this code to move it off the first line because it's vendored 
> code.

The code is correct (for Rust) as it indicates that the standard
library shouldn't be used:

https://docs.rust-embedded.org/book/intro/no-std.html

It's a bit unfortunate that Rust used the shebang syntax here,
although in practice they couldn't be confused as these files
shouldn't ever be executable.

It's also correct that RPM worries about this file since it is
installed (in debuginfo) and appears to contain a shebang.

> Is there a way to tell rpmbuild not to worry about this?

rust.spec has this in %prep, and /usr/lib/rpm/redhat/brp-mangle-shebangs
only seems to care about executable files, so this should help:

  # Sometimes Rust sources start with #![...] attributes, and "smart" editors 
think
  # it's a shebang and make them executable. Then brp-mangle-shebangs gets 
upset...
  find -name '*.rs' -type f -perm /111 -exec chmod -v -x '{}' '+'

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
Fedora Windows cross-compiler. Compile Windows programs, test, and
build Windows installers. Over 100 libraries supported.
http://fedoraproject.org/wiki/MinGW
--
___
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: rpmbuild problem with rust code

[Fabio Valentini]

On Mon, Feb 26, 2024, 22:25 Steve Grubb  wrote:

> Hello,
>
> I've run across a strange problem building a package that has some rust
> files
> in it. The build goes fine until the end when it starts to check for
> shebangs.
> It ends like this:
>
>
> /usr/src/debug/suricata-7.0.3-1.fc41.x86_64/rust/vendor/alloc-no-stdlib/src/
> lib.rs has shebang which doesn't start with '/' ([no_std])
>
> When I check the file, I find this:
> #![no_std]
>
> #[macro_use]
> mod allocated_memory;
> mod stack_allocator;
> mod allocated_stack_memory;
>
> Not being a rust programmer, I have no good idea what the code is doing. I
> can't patch this code to move it off the first line because it's vendored
> code.
>
> Is there a way to tell rpmbuild not to worry about this?
>

The solution should be simple - remove stray +x permissions from all *.rs
files.

Some editors see a file that starts with "#!" and think "hey, this looks
like a script! let me mark the file as executable!" even though this is
Rust syntax for global attributes, not a shebang.

Fabio



> -Steve
>
> --
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

rpmbuild problem with rust code

[Steve Grubb]

Hello,

I've run across a strange problem building a package that has some rust files 
in it. The build goes fine until the end when it starts to check for shebangs. 
It ends like this:

/usr/src/debug/suricata-7.0.3-1.fc41.x86_64/rust/vendor/alloc-no-stdlib/src/
lib.rs has shebang which doesn't start with '/' ([no_std])

When I check the file, I find this:
#![no_std]

#[macro_use]
mod allocated_memory;
mod stack_allocator;
mod allocated_stack_memory;

Not being a rust programmer, I have no good idea what the code is doing. I 
can't patch this code to move it off the first line because it's vendored 
code.

Is there a way to tell rpmbuild not to worry about this?

-Steve

--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Podman v5 breaking changes

[Gursewak Singh]

In Fedora 40, Podman has undergone a major version upgrade to v5 [1],
introducing some breaking changes. Notably, CNI networking support has been
discontinued in favor of Netavark, and cgroups v1 support has been
deprecated in favor of cgroups v2.

To know whether your nodes are affected, you can use podman info and look
for the cgroupVersion and networkBackend keys.

If you're using cgroups v1, migrating to cgroups v2 is strongly
recommended, as a future Podman version will no longer support cgroups v1.
Kernel arguments can be adjusted to use cgroups v2 with rpm-ostree kargs
 [2].

If you're using CNI networking, transitioning to Netavark requires
running podman
system reset --force, leading to the deletion of images, containers, and
custom networks. Depending on your setup, it may be preferable to
reprovision the entire machine from the latest images to allow for Ignition
to bring up containerized applications from scratch.

If you have any feedback or encounter issues related to the aforementioned
changes, please don't hesitate to participate in the upstream issue
discussion [3].

The Fedora CoreOS Team

[1] https://fedoraproject.org/wiki/Changes/Podman5
[2]
https://docs.fedoraproject.org/en-US/fedora-coreos/kernel-args/#_removing_existing_kernel_arguments
[3] https://github.com/coreos/fedora-coreos-tracker/issues/1629
--
___
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

Summary/Minutes from today's FESCo Meeting (2024-02-26)

[Zbigniew Jędrzejewski-Szmek]

Text Log: 
https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-02-26/fesco.2024-02-26-19.35.log.txt
HTML Log: 
https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-02-26/fesco.2024-02-26-19.35.log.html
Text Minutes: 
https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-02-26/fesco.2024-02-26-19.35.txt
HTML Minutes: 
https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-02-26/fesco.2024-02-26-19.35.html

Meeting summary
---
* TOPIC: Init Process (@zbyszek:fedora.im, 19:35:44)
* TOPIC: #3158 Change: Arm Minimal Image OS Build (@zbyszek:fedora.im, 19:42:44)
* AGREED: APPROVED (+7, 1, 0) (@zbyszek:fedora.im, 19:48:12)
* TOPIC: #3173 F40 Change Proposal Status: Incomplete Changes 
(@zbyszek:fedora.im, 19:48:32)
* INFO: https://fedoraproject.org/wiki/Changes/LLVM-18 (@zbyszek:fedora.im, 
19:50:40)
* INFO: https://fedoraproject.org/wiki/Changes/KiwiBuiltCloudImages 
(@zbyszek:fedora.im, 19:51:36)
* INFO: Changes/LLVM-18 is on track. (@zbyszek:fedora.im, 19:53:58)
* INFO: Changes/KiwiBuiltCloudImages is in progress. (@zbyszek:fedora.im, 
19:54:16)
* INFO: https://fedoraproject.org/wiki/Changes/Java21 (@zbyszek:fedora.im, 
19:54:23)
* INFO: Changes/Java21 is in progress, we'll revisit after Beta Freeze 
starts. (@zbyszek:fedora.im, 19:56:37)
* INFO: https://fedoraproject.org/wiki/Changes/SystemdSecurityHardening 
(@zbyszek:fedora.im, 19:56:59)
* ACTION: Aoife Moloney will reach out to the owner of 
Changes/SystemdSecurityHardening. (@zbyszek:fedora.im, 19:59:49)
* INFO: https://fedoraproject.org/wiki/Changes/RemoveOpensslCompat 
(@zbyszek:fedora.im, 20:00:07)
* INFO: Changes/RemoveOpensslCompat is blocked by the port of Python3.6 to 
newer openssl which is being worked on. (@zbyszek:fedora.im, 20:05:20)
* INFO: https://fedoraproject.org/wiki/Changes/LibuserDeprecation 
(@zbyszek:fedora.im, 20:05:32)
* LINK: 
https://src.fedoraproject.org/rpms/shadow-utils/c/91360f25a8c8b810d59bec2803a2477a2647c775
 (@conan_kudo:matrix.org, 20:06:06)
* INFO: Changes/LibuserDeprecation is mostly done. (@zbyszek:fedora.im, 
20:08:00)
* INFO: https://fedoraproject.org/wiki/Changes/PortingToModernC 
(@zbyszek:fedora.im, 20:08:23)
* INFO: gcc14 is in f40, so Changes/PortingToModernC has happened. 
(@zbyszek:fedora.im, 20:10:28)
* INFO: Changes/IoTSimplifiedProvisioning (@zbyszek:fedora.im, 20:11:43)
* INFO: https://fedoraproject.org/wiki/Changes/IoTSimplifiedProvisioning 
(@zbyszek:fedora.im, 20:11:52)
* INFO: Changes/IoTSimplifiedProvisioning is in testable state. 
(@zbyszek:fedora.im, 20:13:48)
* INFO: 
https://fedoraproject.org/wiki/Changes/Haskell_GHC_9.6_and_Stackage_22 
(@zbyszek:fedora.im, 20:14:02)
* INFO: Changes/Haskell_GHC_9.6_and_Stackage_22 was bumped to F41. 
(@zbyszek:fedora.im, 20:14:39)
* INFO: 
https://fedoraproject.org/wiki/Changes/F40_MariaDB_MySQL_repackaging 
(@zbyszek:fedora.im, 20:14:52)
* INFO: Changes/F40_MariaDB_MySQL_repackaging is waiting on the rename 
review request, but Neal is reasonably confident that it'll happen in time. 
(@zbyszek:fedora.im, 20:17:55)
* INFO: 
https://fedoraproject.org/wiki/Changes/Unified_Kernel_Support_Phase_2 
(@zbyszek:fedora.im, 20:18:11)
* INFO: All the work for this is done, we're waiting for the kiwi change to 
be finished for this to be completed. (@conan_kudo:matrix.org, 20:19:40)
* INFO: https://fedoraproject.org/wiki/Changes/FedoraSilverblueBootupd 
(@zbyszek:fedora.im, 20:20:00)
* AGREED: Changes/FedoraSilverblueBootupd is deferred to F41 (+6, 0, 0) 
(@zbyszek:fedora.im, 20:29:23)
* INFO: https://fedoraproject.org/wiki/Changes/Unify_bin_and_sbin was 
deferred to F41 by the Owner (zbyszek) (@zbyszek:fedora.im, 20:30:27)
* TOPIC: Next week's chair (@zbyszek:fedora.im, 20:31:15)
* ACTION: mhayden will chair the next meeting. (@zbyszek:fedora.im, 
20:33:06)
* TOPIC: Open Floor (@zbyszek:fedora.im, 20:33:19)
* INFO: Fedora ELN has successfully branched off to CentOS Stream 10. As a 
result, Fedora ELN is now tracking changes destined for CentOS Stream/RHEL 11. 
(@sgallagh:fedora.im, 20:34:40)

Meeting ended at 2024-02-26 20:36:10

Action items

* Aoife Moloney will reach out to the owner of 
Changes/SystemdSecurityHardening. 
* mhayden will chair the next meeting. 
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Introduction / unorphaning package request

[Michel Lind]

On Mon, Feb 26, 2024 at 11:32:44AM -0800, Josh Stone wrote:
> Welcome!
> 
> Since name collisions are fun, I want to clarify for everyone else that
> we are not the same person. I'm jistone, he's jostone, and I'm sure this
> won't confuse anyone... :)
> 
You should sponsor jostone for extra confusion :)

> On 2/23/24 6:23 AM, Joshua Stone wrote:
> > Hello everyone,
> > 
> > I've been a Linux user since my friends showed me Ubuntu 9.04! That was
> > a lifesaver when I needed an OS with a functional office suite after my
> > MS Office 2007 license expired and Windows Vista was having stability
> > issues. After multi-booting Windows and Linux for several years, I had
> > decided that I no longer boot Windows enough to warrant the disk space,
> > so I've been running Linux exclusively for over a decade.
> > 
> > When I was first using Linux, I would distro hop between Ubuntu, Linux
> > Mint, and Fedora, finally before settling on Fedora right around the
> > time it switched to Wayland by default.
> > 
> > I think Fedora has been very beneficial for me because it's given me
> > enough of a background on RPM-based distros to have a career where I can
> > use Linux professionally. My current employment is at Red Hat so I spend
> > a lot of time packaging software.
> > 
> > I also spend time maintaining several apps on Flathub, and I'd like to
> > expand maintenance efforts to Fedora!
> > 
> > Earlier I filed a request for unorphaning a package:
> > 
> > https://pagure.io/releng/issue/11963 
> > 
> > It would appear that there are several requirements I must fulfill,
> > especially finding a sponsor. If there's anyone who can help, then I'd
> > really appreciate it! I hope to be more involved with the Fedora community!
> > 
> > Thanks!
> > 
> > - Josh
> > 
> > --
> > ___
> > devel mailing list -- devel@lists.fedoraproject.org
> > To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> > Fedora Code of Conduct: 
> > https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives: 
> > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> > Do not reply to spam, report it: 
> > https://pagure.io/fedora-infrastructure/new_issue
> --
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam, report it: 
> https://pagure.io/fedora-infrastructure/new_issue

-- 
Michel Lind (né Salim)
identities: https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2


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: Introduction / unorphaning package request

[Josh Stone]

Welcome!

Since name collisions are fun, I want to clarify for everyone else that
we are not the same person. I'm jistone, he's jostone, and I'm sure this
won't confuse anyone... :)

On 2/23/24 6:23 AM, Joshua Stone wrote:
> Hello everyone,
> 
> I've been a Linux user since my friends showed me Ubuntu 9.04! That was
> a lifesaver when I needed an OS with a functional office suite after my
> MS Office 2007 license expired and Windows Vista was having stability
> issues. After multi-booting Windows and Linux for several years, I had
> decided that I no longer boot Windows enough to warrant the disk space,
> so I've been running Linux exclusively for over a decade.
> 
> When I was first using Linux, I would distro hop between Ubuntu, Linux
> Mint, and Fedora, finally before settling on Fedora right around the
> time it switched to Wayland by default.
> 
> I think Fedora has been very beneficial for me because it's given me
> enough of a background on RPM-based distros to have a career where I can
> use Linux professionally. My current employment is at Red Hat so I spend
> a lot of time packaging software.
> 
> I also spend time maintaining several apps on Flathub, and I'd like to
> expand maintenance efforts to Fedora!
> 
> Earlier I filed a request for unorphaning a package:
> 
> https://pagure.io/releng/issue/11963 
> 
> It would appear that there are several requirements I must fulfill,
> especially finding a sponsor. If there's anyone who can help, then I'd
> really appreciate it! I hope to be more involved with the Fedora community!
> 
> Thanks!
> 
> - Josh
> 
> --
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam, report it: 
> https://pagure.io/fedora-infrastructure/new_issue
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Login issues to lists.* and src.*? Any outages?

[Michal Konecny]

On 26. 02. 24 18:08, Christopher wrote:

On Mon, Feb 26, 2024 at 6:13 AM Michal Konecny  wrote:
[snip]

It's usually good to wait for some time and try again. If the issue persists 
you can open ticket on
https://pagure.io/fedora-infrastructure/issues

Michal

I did try over the course of a few hours. It wasn't until 3 days later
that I tried again and it worked.
But, filing an issue would have been difficult since I couldn't log in
to pagure.io either, since it uses the same authentication as the
others. I actually did try pagure.io, though I didn't mention it in my
initial email. But, it also didn't work.
--
In this case you can let the admins know about the issue by sending 
e-mail to ad...@fedoraproject.org and somebody will reach to you.

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: package reviews for Pandoc and CVE-2023-35936

[Jens-Ulrik Petersen]

Hmm it looks like I really do need to update everything to LTS 22 to
achieve the pandoc rebase properly (since it needs newer Haskell tls).

Here's one more package review:

  toml-parser: https://bugzilla.redhat.com/show_bug.cgi?id=2266093

needed by the typst library.

Jens
--
___
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: Login issues to lists.* and src.*? Any outages?

[Christopher]

On Mon, Feb 26, 2024 at 6:13 AM Michal Konecny  wrote:
[snip]
> It's usually good to wait for some time and try again. If the issue persists 
> you can open ticket on
> https://pagure.io/fedora-infrastructure/issues
>
> Michal

I did try over the course of a few hours. It wasn't until 3 days later
that I tried again and it worked.
But, filing an issue would have been difficult since I couldn't log in
to pagure.io either, since it uses the same authentication as the
others. I actually did try pagure.io, though I didn't mention it in my
initial email. But, it also didn't work.
--
___
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: Current status of OSTree and its handling RPM scriptlets?

[Stephen Gallagher]

On Thu, Feb 22, 2024 at 4:51 AM Zdenek Dohnal  wrote:
>
> Hi Jonathan!
>
> On 2/13/24 16:47, Jonathan Lebon wrote:
>
> Has it got fixed during the time? Or is there a new technology which
> would do the trick for Silverblue and Fedora Linux alike?
>
> Just a note: I would say "for Silverblue and traditional systems
> alike" instead. Silverblue is part of Fedora Linux. :)
>
> Ok, I thought there are Fedora Linux, Fedora Silverblue and Fedora CoreOS 
> (maybe others :) ). Thanks!
>
> The common way to make "image-mode friendly" system state changes is
> to e.g. use a systemd service
>
> Do you have an example of such systemd service? I could see that a shell 
> script can be started by systemd unit to do the migration, but that would 
> have to be run in %post scriptlet again AFAIK - unless you would require 
> machine restart (and the service is run during reboot) or manual service 
> start...
>

https://docs.fedoraproject.org/en-US/packaging-guidelines/Initial_Service_Setup/
--
___
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: SPDX Statistics - Please Please Me edition

[Stephen Smoogen]

On Mon, 26 Feb 2024 at 09:54, Richard Hughes  wrote:

> On Fri, 16 Feb 2024 at 15:07, Miroslav Suchý  wrote:
> > * 23711 spec files in Fedora
>
> I was looking through the list for any of my packages, and I've found
> that I'm "maintaining" long dead packages like
> https://src.fedoraproject.org/rpms/GConf2
>
> According to that I have "commit" ACLs, but I couldn't find any way to
> relinquish those using the web UI. I suppose I could contact the "main
> admin" of the package, but I don't think that would scale as I've also
> got "commit" on ~250 other packages.
>
> If the SPDX listing isn't using src.fedoraproject.org and instead
> using something like bugzilla please yell. Being listed as maintaining
> all those also makes the packager-dashboard basically useless for me
> too. :)
>

I wonder if you have it from a group you are in or if it was the general
creep of time that has added you to a lot of packages?

-- 
Stephen Smoogen, Red Hat Automotive
Let us be kind to one another, for most of us are fighting a hard battle.
-- Ian MacClaren
--
___
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: SPDX Statistics - Please Please Me edition

[Richard Hughes]

On Fri, 16 Feb 2024 at 15:07, Miroslav Suchý  wrote:
> * 23711 spec files in Fedora

I was looking through the list for any of my packages, and I've found
that I'm "maintaining" long dead packages like
https://src.fedoraproject.org/rpms/GConf2

According to that I have "commit" ACLs, but I couldn't find any way to
relinquish those using the web UI. I suppose I could contact the "main
admin" of the package, but I don't think that would scale as I've also
got "commit" on ~250 other packages.

If the SPDX listing isn't using src.fedoraproject.org and instead
using something like bugzilla please yell. Being listed as maintaining
all those also makes the packager-dashboard basically useless for me
too. :)

RIchard.
--
___
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: mock: ImportError: /lib64/libdnf.so.2: undefined symbol: g_once_init_enter_pointer

[Jun Aruga (he / him)]

> I see that the `/usr/bin/dnf5` doesn't exist in the
> `/var/lib/mock/fedora-rawhide-x86_64-bootstrap`. Do you know how to
> fix it?

Now the error `/usr/bin/dnf5` doesn't exist in the
`/var/lib/mock/fedora-rawhide-x86_64-bootstrap` came from a cache.
When I ran the following commands, I was able to run the commands without error!

```
$ mock --scrub=all -r fedora-rawhide-x86_64
$ mock -r fedora-rawhide-x86_64 --shell
```

-- 
Jun | He - Him | Timezone: UTC+1 or 2, Czech Republic
See  for
the timezone.
--
___
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: mock: ImportError: /lib64/libdnf.so.2: undefined symbol: g_once_init_enter_pointer

[Jun Aruga (he / him)]

Hi,

I restored the /etc/mock

```
$ rpm -q mock-core-configs
mock-core-configs-40.1-1.fc39.noarch

$ sudo dnf upgrade mock-core-configs

$ rpm -q mock-core-configs
mock-core-configs-40.2-1.fc39.noarch
```

I needed to copy the logging.ini manually, as I saw an error related
to this file when running the mock.

```
$ sudo cp -p /etc/mock_20240226_bak/logging.ini /etc/mock/
```

Then I see the following error. I am running the mock with the default
/etc/mock files and without the `~/.config/mock.cfg`.

```
$ rpm -q mock mock-core-configs dnf5
mock-5.5-1.fc39.noarch
mock-core-configs-40.2-1.fc39.noarch
dnf5-5.1.13-1.fc39.x86_64

$ mock -r fedora-rawhide-x86_64 --shell
INFO: mock.py version 5.5 starting (python version = 3.12.1, NVR =
mock-5.5-1.fc39), args: /usr/libexec/mock/mock -r
fedora-rawhide-x86_64 --shell
Start(bootstrap): init plugins
INFO: selinux enabled
Finish(bootstrap): init plugins
Start: init plugins
INFO: selinux enabled
Finish: init plugins
INFO: Signal handler active
Start: run
Start(bootstrap): chroot init
INFO: calling preinit hooks
INFO: enabled root cache
INFO: enabled package manager cache
Start(bootstrap): cleaning package manager metadata
Finish(bootstrap): cleaning package manager metadata
INFO: Using 'dnf' instead of 'dnf5' for bootstrap chroot
INFO: Package manager dnf detected and used (fallback)
Finish(bootstrap): chroot init
Start: chroot init
INFO: calling preinit hooks
INFO: enabled root cache
INFO: enabled package manager cache
Start: cleaning package manager metadata
Finish: cleaning package manager metadata
INFO: enabled HW Info plugin
INFO: Package manager dnf5 detected and used (direct choice)
Start: installing minimal buildroot with dnf5
execv(/usr/bin/dnf5) failed: No such file or directory
ERROR: Command failed:
 # /usr/bin/systemd-nspawn -q -M a4b6850efcd84d949ac566faeddc46d5 -D
/var/lib/mock/fedora-rawhide-x86_64-bootstrap/root -a
--capability=cap_ipc_lock
--bind=/tmp/mock-resolv.lno5ep7q:/etc/resolv.conf --console=pipe
--setenv=TERM=vt100 --setenv=SHELL=/bin/bash
--setenv=HOME=/var/lib/mock/fedora-rawhide-x86_64/root/installation-homedir
--setenv=HOSTNAME=mock --setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin
'--setenv=PROMPT_COMMAND=printf "\033]0;\007"'
'--setenv=PS1= \s-\v\$ ' --setenv=LANG=C.UTF-8
--setenv=LC_MESSAGES=C.UTF-8 --resolv-conf=off /usr/bin/dnf5
--installroot /var/lib/mock/fedora-rawhide-x86_64/root/ --releasever
41 install @buildsys-build --setopt=deltarpm=False
--setopt=allow_vendor_change=yes --allowerasing
--setopt=tsflags=nocontexts
execv(/usr/bin/dnf5) failed: No such file or directory
```

I see that the `/usr/bin/dnf5` doesn't exist in the
`/var/lib/mock/fedora-rawhide-x86_64-bootstrap`. Do you know how to
fix it?

```
$ rpm -qf /usr/bin/dnf5
dnf5-5.1.13-1.fc39.x86_64

$ ls -l /usr/bin/dnf5
-rwxr-xr-x. 1 root root 1376632 Feb 20 01:00 /usr/bin/dnf5*

$ ls -l /var/lib/mock/fedora-rawhide-x86_64-bootstrap/root/usr/bin/dnf*
lrwxrwxrwx. 1 root root5 Feb  8 01:00
/var/lib/mock/fedora-rawhide-x86_64-bootstrap/root/usr/bin/dnf ->
dnf-3*
-rwxr-xr-x. 1 root root 2092 Feb  8 01:00
/var/lib/mock/fedora-rawhide-x86_64-bootstrap/root/usr/bin/dnf-3*
lrwxrwxrwx. 1 root root5 Feb  8 01:00
/var/lib/mock/fedora-rawhide-x86_64-bootstrap/root/usr/bin/dnf4 ->
dnf-3*

$ ls -l /var/lib/mock/fedora-rawhide-x86_64-bootstrap/root/usr/bin/dnf5
ls: cannot access
'/var/lib/mock/fedora-rawhide-x86_64-bootstrap/root/usr/bin/dnf5': No
such file or directory

$ ls /var/lib/mock/fedora-rawhide-x86_64/root/usr/
share/
```

Thanks for your help!

-- 
Jun | He - Him | Timezone: UTC+1 or 2, Czech Republic
See  for
the timezone.
--
___
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: distrobuildsync-eln is building unnecessary liborc and libarrow

[Stephen Gallagher]

On Mon, Feb 26, 2024 at 8:38 AM Kaleb Keithley  wrote:
>
> Hi,
>
> Anyone know why distriobuildsync-eln has started building liborc and libarrow 
> again?
>
> They were stopped at one point, but now they have started again.
>
> There are not needed for ceph in ELN.
>

They're getting pulled into ELN-Extras, not ELN proper. Looks like
Digikam depends on them indirectly (by way of opencv-imgcodecs and
gdal-libs).

A few notes:
 * ELN is currently tracking RHEL 11
 * ELN Extras is essentially a preview for EPEL, not RHEL.
 * The Content Resolver will show you the dependency chain:
https://tiny.distro.builders/view-rpm--view-eln-extras--libarrow.html
--
___
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

distrobuildsync-eln is building unnecessary liborc and libarrow

[Kaleb Keithley]

Hi,

Anyone know why distriobuildsync-eln has started building liborc and
libarrow again?

They were stopped at one point, but now they have started again.

There are not needed for ceph in ELN.

-- 

Kaleb
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Fedora 40 compose report: 20240226.n.0 changes

[Fedora Branched Report]

OLD: Fedora-40-20240225.n.0
NEW: Fedora-40-20240226.n.0

= SUMMARY =
Added images:2
Dropped images:  3
Added packages:  4
Dropped packages:2
Upgraded packages:   71
Downgraded packages: 0

Size of added packages:  2.71 MiB
Size of dropped packages:146.25 KiB
Size of upgraded packages:   899.88 MiB
Size of downgraded packages: 0 B

Size change of upgraded packages:   -3.14 MiB
Size change of downgraded packages: 0 B

= ADDED IMAGES =
Image: Kinoite dvd-ostree x86_64
Path: Kinoite/x86_64/iso/Fedora-Kinoite-ostree-x86_64-40-20240226.n.0.iso
Image: Onyx dvd-ostree x86_64
Path: Onyx/x86_64/iso/Fedora-Onyx-ostree-x86_64-40-20240226.n.0.iso

= DROPPED IMAGES =
Image: Kinoite dvd-ostree ppc64le
Path: Kinoite/ppc64le/iso/Fedora-Kinoite-ostree-ppc64le-40-20240225.n.0.iso
Image: Workstation live aarch64
Path: 
Workstation/aarch64/iso/Fedora-Workstation-Live-aarch64-40-20240225.n.0.iso
Image: Silverblue dvd-ostree x86_64
Path: Silverblue/x86_64/iso/Fedora-Silverblue-ostree-x86_64-40-20240225.n.0.iso

= ADDED PACKAGES =
Package: dbus-test-runner-19.04.0-1.fc40
Summary: Utility to run executables under a new DBus session for testing
RPMs:dbus-test-runner dbus-test-runner-devel
Size:349.05 KiB

Package: libayatana-appindicator-0.5.93-1.fc40
Summary: Ayatana Application Indicators
RPMs:libayatana-appindicator-gtk2 libayatana-appindicator-gtk2-devel 
libayatana-appindicator-gtk2-sharp libayatana-appindicator-gtk2-sharp-devel 
libayatana-appindicator-gtk3 libayatana-appindicator-gtk3-devel 
libayatana-appindicator-gtk3-sharp libayatana-appindicator-gtk3-sharp-devel
Size:1.15 MiB

Package: libayatana-ido-0.10.1-3.fc40
Summary: Ayatana Indicator Display Objects library
RPMs:libayatana-ido-gtk3 libayatana-ido-gtk3-devel
Size:534.64 KiB

Package: libayatana-indicator-0.9.4-1.fc40
Summary: Ayatana Indicators Shared Library
RPMs:libayatana-indicator-gtk2 libayatana-indicator-gtk2-devel 
libayatana-indicator-gtk3 libayatana-indicator-gtk3-devel 
libayatana-indicator-tools-gtk3
Size:716.38 KiB


= DROPPED PACKAGES =
Package: rust-gdk4-sys0.6-0.6.3-2.fc40
Summary: FFI bindings of GDK 4
RPMs:rust-gdk4-sys0.6+default-devel rust-gdk4-sys0.6+dox-devel 
rust-gdk4-sys0.6+v4_10-devel rust-gdk4-sys0.6+v4_2-devel 
rust-gdk4-sys0.6+v4_4-devel rust-gdk4-sys0.6+v4_6-devel 
rust-gdk4-sys0.6+v4_8-devel rust-gdk4-sys0.6-devel
Size:112.06 KiB

Package: rust-graphene-sys0.17-0.17.10-2.fc40
Summary: FFI bindings to libgraphene-1.0
RPMs:rust-graphene-sys0.17+default-devel rust-graphene-sys0.17+dox-devel 
rust-graphene-sys0.17-devel
Size:34.19 KiB


= UPGRADED PACKAGES =
Package:  appstream-1.0.2-1.fc40
Old package:  appstream-1.0.1-3.fc40
Summary:  Utilities to generate, maintain and access the AppStream database
RPMs: appstream appstream-compose appstream-compose-devel 
appstream-devel appstream-qt appstream-qt-devel
Size: 15.22 MiB
Size change:  168.69 KiB
Changelog:
  * Sun Feb 25 2024 Neal Gompa  - 1.0.2-1
  - Update to 1.0.2
  - Clean up some pre-1.0 scriptlet cruft


Package:  cryptlib-3.4.7-4.fc40
Old package:  cryptlib-3.4.7-3.fc40
Summary:  Security library and toolkit for encryption and authentication 
services
RPMs: cryptlib cryptlib-devel cryptlib-java cryptlib-javadoc 
cryptlib-perl cryptlib-python3 cryptlib-test cryptlib-tools
Size: 5.39 MiB
Size change:  32.47 KiB
Changelog:
  * Sun Feb 25 2024 Ralf Senderek  - 3.4.7-4
  - Add clsmime to cryptlib-tools


Package:  emacs-json-mode-1.9.0-1.fc40
Old package:  emacs-json-mode-1.8.0-7.fc40
Summary:  Major mode for editing JSON files with Emacs
RPMs: emacs-json-mode
Size: 14.78 KiB
Size change:  707 B
Changelog:
  * Sun Feb 25 2024 Mohamed El Morabity  - 
1.9.0-1
  - Update to 1.9.0


Package:  gnome-tweaks-46~beta-1.fc40
Old package:  gnome-tweaks-45.0-3.fc40
Summary:  Customize advanced GNOME 3 options
RPMs: gnome-tweaks
Size: 342.73 KiB
Size change:  5.35 KiB
Changelog:
  * Fri Feb 16 2024 David King  - 46~beta-1
  - Update to 46.beta


Package:  gpaste-45-4.fc40
Old package:  gpaste-45-1.fc40
Summary:  Clipboard management system
RPMs: gnome-shell-extension-gpaste gpaste gpaste-bash-completion 
gpaste-devel gpaste-libs gpaste-ui gpaste-zsh-completion
Size: 1.49 MiB
Size change:  -218.04 KiB
Changelog:
  * Sat Jan 20 2024 Fedora Release Engineering  - 45-2
  - Rebuilt for https://fedoraproject.org/wiki/Fedora_40_Mass_Rebuild

  * Wed Jan 24 2024 Fedora Release Engineering  - 45-3
  - Rebuilt for https://fedoraproject.org/wiki/Fedora_40_Mass_Rebuild

  * Sun Feb 25 2024 Mohamed El Morabity  - 45-4
  - Drop support for i686


Package:  hcxtools-6.3.4-1.fc40
Old package:  hcxtools-6.3.2-3.fc40
Summary:  Portable solution for conversion WiFi dump files to hashcat 
formats
RPMs: hcxtools
Size: 734.84 KiB
Size change:  9.43 KiB

Re: package reviews for Pandoc and CVE-2023-35936

[Neal Gompa]

On Mon, Feb 26, 2024 at 8:22 AM Jens-Ulrik Petersen  wrote:
>
> Another day, another needed package (this would also be part of the postponed 
> Stackage LTS 22 change):
> I forgot that pandoc > 3.1.3 had moved to the new crypton stack that replaces 
> cryptonite:
>
> crypton: https://bugzilla.redhat.com/show_bug.cgi?id=2266044
>
> Next would be crypton-x509...
>
> Is it better I just pump the whole stack straight to bz, though my preference 
> is to only open RRs which can actually build.
> But if it is less painful to review them together/back-to-back I can pump 
> them out faster (maybe a few of the next crypto-x509-* packages can be done 
> in parallel).
>

Put the whole stack and set the BZ dependencies. IIRC, the
fedora-review bot will process them all in order too.



-- 
真実はいつも一つ！/ Always, there's only one truth!
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: package reviews for Pandoc and CVE-2023-35936

[Jens-Ulrik Petersen]

Another day, another needed package (this would also be part of the
postponed Stackage LTS 22 change):
I forgot that pandoc > 3.1.3 had moved to the new crypton stack that
replaces cryptonite:

crypton: https://bugzilla.redhat.com/show_bug.cgi?id=2266044

Next would be crypton-x509...

Is it better I just pump the whole stack straight to bz, though my
preference is to only open RRs which can actually build.
But if it is less painful to review them together/back-to-back I can pump
them out faster (maybe a few of the next crypto-x509-* packages can be done
in parallel).

Thanks, Jens
--
___
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: Login issues to lists.* and src.*? Any outages?

[František Šumšal]

On 2/26/24 12:13, Michal Konecny wrote:



On 24. 02. 24 12:30, Richard W.M. Jones wrote:

...
So I sometimes have issues logging in.  For example it happened about
5 minutes ago, but the error isn't very interesting:

   Original 
URL:https://id.fedoraproject.org/login/gssapi/negotiate?ipsilon_transaction_id=8d11a868-b8f5-4e65-b48b-a53f592d2cfb
   Redirected URL:https://id.fedoraproject.org/login/pam

   Gateway Timeout

   The gateway did not receive a timely response from the upstream
   server or application.

Is it useful to report these?  Sometimes just retrying works, as
in fact happened when I retried it this time.

Rich.

It's usually good to wait for some time and try again. If the issue persists 
you can open ticket on
https://pagure.io/fedora-infrastructure/issues


Speaking of the devil, I just started getting 500s when trying to log in, so I 
filed https://pagure.io/fedora-infrastructure/issue/11793.



Michal

...



--
___
devel mailing list --devel@lists.fedoraproject.org
To unsubscribe send an email todevel-le...@lists.fedoraproject.org
Fedora Code of 
Conduct:https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines
List 
Archives:https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report 
it:https://pagure.io/fedora-infrastructure/new_issue



--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

--
___
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

Schedule for Monday's FESCo Meeting (2024-02-26)

[Zbigniew Jędrzejewski-Szmek]

Following is the list of topics that will be discussed in the
FESCo meeting Monday at 19:30 UTC in #meeting:fedoraproject.org
on Matrix.

To convert UTC to your local time, take a look at
  http://fedoraproject.org/wiki/UTCHowto

or run:
  date -d '2024-02-26 19:30 UTC'

Links to all issues to be discussed can be found at: 
https://pagure.io/fesco/report/meeting_agenda

= Discussed and Voted in the Ticket =

#3170 Go 1.21 in Fedora 38 
https://pagure.io/fesco/issue/3170
APPROVED (+4, 0, 0)


= Followups =

#3158 Change: Arm Minimal Image OS Build
https://pagure.io/fesco/issue/3158


= New business =

#3173 F40 Change Proposal Status: Incomplete Changes
https://pagure.io/fesco/issue/3173


= Open Floor = 

For more complete details, please visit each individual
issue.  The report of the agenda items can be found at
https://pagure.io/fesco/report/meeting_agenda

If you would like to add something to this agenda, you can
reply to this e-mail, file a new issue at
https://pagure.io/fesco, e-mail me directly, or bring it
up at the end of the meeting, during the open floor topic. Note
that added topics may be deferred until the following meeting. 
--
___
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)

[Ankur Sinha]

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&iso=20240226T13&p1=%3A&ah=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&tags=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: Login issues to lists.* and src.*? Any outages?

[Michal Konecny]

On 24. 02. 24 12:30, Richard W.M. Jones wrote:

...
So I sometimes have issues logging in.  For example it happened about
5 minutes ago, but the error isn't very interesting:

   Original 
URL:https://id.fedoraproject.org/login/gssapi/negotiate?ipsilon_transaction_id=8d11a868-b8f5-4e65-b48b-a53f592d2cfb
   Redirected URL:https://id.fedoraproject.org/login/pam

   Gateway Timeout

   The gateway did not receive a timely response from the upstream
   server or application.

Is it useful to report these?  Sometimes just retrying works, as
in fact happened when I retried it this time.

Rich.
It's usually good to wait for some time and try again. If the issue 
persists you can open ticket on

https://pagure.io/fedora-infrastructure/issues

Michal

...




--
___
devel mailing list --devel@lists.fedoraproject.org
To unsubscribe send an email todevel-le...@lists.fedoraproject.org
Fedora Code of 
Conduct:https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines
List 
Archives:https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report 
it:https://pagure.io/fedora-infrastructure/new_issue


--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Donate 1 minute of your time to test upgrades from F39 to F40

[Vít Ondruch]

Dne 25. 02. 24 v 18:02 Ralf Corsépius napsal(a):



Am 24.02.24 um 10:12 schrieb Samuel Sieb:

On 2/24/24 00:47, Ralf Corsépius wrote:

Am 24.02.24 um 01:36 schrieb Samuel Sieb:

On 2/23/24 15:38, Sérgio Basto wrote:

On Sat, 2024-02-24 at 00:06 +0100, Ralf Corsépius wrote:



Am 23.02.24 um 22:37 schrieb Samuel Sieb:

On 2/23/24 10:50, Ralf Corsépius wrote:


# dnf system-upgrade download --releasever=40
...
No match for group package "multican"
...

WTH?


It was a program for controlling Canon cameras that has been
retired.
Some group you have installed has that package listed in it.

Ah, this likely explains why neither "dnf repoquery" nor "dnf group
list" could find "multican".


  The comps
groups need to be cleaned out and that's just a warning.

Well, ... IMHO, most about comps and groups is in an embarrassing
unusable shape.


No match for group package "baekmuk-ttf-batang-fonts"

[snip]

No match for group package "util-linux-user"

I got these ones , is something on my rpm db ?


I am seeing these on another machine, too.


I expect you would see that on all machines.

No.  Well, sort of.  As mentioned, those are packages that have 
been removed from the distro, but are still listed in the comps 
groups. dnf checks the installed groups for packages that need to 
be updated and can't find these ones.

Really? How do I check for which groups I have installed?

At least I haven't found any way to check for them, neither with rpm 
nor with dnf.


dnf group list --installed


# dnf group list --installed
Last metadata expiration check: 4:04:39 ago on Sun 25 Feb 2024 
01:48:48 PM CET.

Installed Environment Groups:
   Xfce Desktop
Installed Groups:
   Administration Tools
   LibreOffice
   Fonts
   Hardware Support

# dnf system-upgrade --release=40 download
...
No match for group package "paktype-ajrak-fonts"



Just looking at the first one, this is defined here:


https://pagure.io/fedora-comps/blob/main/f/comps-f40.xml.in#_2189

https://pagure.io/fedora-comps/blob/main/f/comps-f41.xml.in#_2189


So if those packages were dropped, then the same person who did that 
should update also the groups.



Looking at dist-git:

https://src.fedoraproject.org/rpms/paktype-ajrak-fonts

It seems those were removed due to being orphaned. That suggest that the 
process should be improved to cover comps. Adding the responsible people 
on CC.



Vít



No match for group package "eosrei-emojione-fonts"
No match for group package "google-noto-sans-phags-pa-fonts"
No match for group package "multican"
No match for group package "nafees-pakistani-web-naskh-fonts"
No match for group package "baekmuk-ttf-batang-fonts"
No match for group package "layla-thuluth-fonts"
No match for group package "layla-digital-fonts"
No match for group package "lohit-nepali-fonts"
No match for group package "google-noto-looped-thai-fonts"
No match for group package "nafees-tehreer-naskh-fonts"
No match for group package "lohit-tamil-classical-fonts"
No match for group package "samyak-gujarati-fonts"
No match for group package "layla-arcyarc-fonts"
No match for group package "nafees-riqa-fonts"
No match for group package "gimp-heif-plugin"
No match for group package "kalapi-fonts"
No match for group package "ibus-bogo"
No match for group package "samyak-devanagari-fonts"
No match for group package "scim-sayura"
No match for group package "lohit-malayalam-fonts"
No match for group package "nafees-pakistani-naskh-fonts"
No match for group package "samyak-odia-fonts"
No match for group package "layla-basic-arabic-fonts"
No match for group package "layla-diwani-fonts"
No match for group package "samyak-tamil-fonts"
No match for group package "nafees-naskh-fonts"
No match for group package "nafees-web-naskh-fonts"
No match for group package "cdac-sakal-marathi-fonts"
No match for group package "layla-ruqaa-fonts"
No match for group package "samyak-malayalam-fonts"
No match for group package "layla-boxer-fonts"
No match for group package "baekmuk-ttf-hline-fonts"
No match for group package "fontawesome-fonts"
No match for group package "baekmuk-ttf-gulim-fonts"
No match for group package "nafees-nastaleeq-fonts"
No match for group package "layla-koufi-fonts"
No match for group package "baekmuk-ttf-dotum-fonts"
...


My actual problem seems to be not being able to get rid of the 
"installed groups".


"dnf group remove " apparently uninstalls all packages from 
this .


This is not what I want. I want to remove the comps-groups from my 
system, because of the harmful effects they obviously have.


Ralf
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/

List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, repor