Re: CPE Weekly Update - Week 34 2022

[Maxwell G via devel]

Aug 26, 2022 7:02:06 AM Michal Konecny :

If you want to receive weekly reports by emails in the future, please 
subscribe to either https://communityblog.fedoraproject.org/ or 
https://discussion.fedoraproject.org/c/news/commblog/61. We will stop 
sending them in the future.
Why is that? I appreciate getting the updates as a clean, plain text 
email that doesn't require clicking external links to read.


Also,  I'd venture that not every CentOS person is interested in the 
Fedora blog or forums.

--
Best,

Maxwell G (@gotmax23)
Pronouns: He/Him/His

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

[Bug 2099988] Please branch and build perl-Parallel-ForkManager in epel9

[bugzilla]

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



--- Comment #3 from Ralf Brunckhorst  ---
Thanks for this offer but I'm not a packager.

Anyone else on this list who can take care or do you know one?

/Ralf


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2099988
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: GTK 2 removal from RHEL 10+

[Kevin Kofler via devel]

Tomáš Popela wrote:
> This is an early heads-up about GTK 2 removal from RHEL 10+ (the gtk2
> package was marked as unwanted in ELN with
> https://github.com/minimization/content-resolver-input/commit/b6d44e496f46bd2444e8e24dd3e9113b326817ac).

I suppose it could be carried in EPEL if needed. Or is somebody attempting 
to veto that too?

Kevin Kofler
___
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 gating: missing required test results

[Adam Williamson]

On Fri, 2022-08-26 at 14:58 -0400, Ben Beasley wrote:
> When a Bodhi update is gated on required tests that seem to remain 
> “missing” indefinitely, is there anything I can do to re-try them? Or do 
> I just have to attempt to waive the missing test results?
> 
> https://bodhi.fedoraproject.org/updates/FEDORA-2022-014e78ee9d 
> 
> 
> The corresponding update for F38 worked fine. The necessary test results 
> appeared and the update passed gating after about 20 minutes.
> 
> https://bodhi.fedoraproject.org/updates/FEDORA-2022-2eed8152f6

Not sure why the re-run tests button is missing and the test didn't
trigger in the first place, but CCing the CI list where someone might
know. Waiving the result seems reasonable, especially since it passed
on Rawhide.
-- 
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net

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

Re: Test gating: missing required test results

[Adam Williamson]

On Fri, 2022-08-26 at 14:58 -0400, Ben Beasley wrote:
> When a Bodhi update is gated on required tests that seem to remain 
> “missing” indefinitely, is there anything I can do to re-try them? Or do 
> I just have to attempt to waive the missing test results?
> 
> https://bodhi.fedoraproject.org/updates/FEDORA-2022-014e78ee9d 
> 
> 
> The corresponding update for F38 worked fine. The necessary test results 
> appeared and the update passed gating after about 20 minutes.
> 
> https://bodhi.fedoraproject.org/updates/FEDORA-2022-2eed8152f6

Not sure why the re-run tests button is missing and the test didn't
trigger in the first place, but CCing the CI list where someone might
know. Waiving the result seems reasonable, especially since it passed
on Rawhide.
-- 
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net

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

[Test-Announce] Fedora 37 Branched 20220826.n.0 nightly compose nominated for testing

[Adam Williamson]

Announcing the creation of a new nightly release validation test event
for Fedora 37 Branched 20220826.n.0. Please help run some tests for this
nightly compose if you have time. For more information on nightly
release validation testing, see:
https://fedoraproject.org/wiki/QA:Release_validation_test_plan

Notable package version changes:
None. Drunk with power, I did this all on my own.

Test coverage information for the current release can be seen at:
https://openqa.fedoraproject.org/testcase_stats/37

You can see all results, find testing instructions and image download
locations, and enter results on the Summary page:

https://fedoraproject.org/wiki/Test_Results:Fedora_37_Branched_20220826.n.0_Summary

The individual test result pages are:

https://fedoraproject.org/wiki/Test_Results:Fedora_37_Branched_20220826.n.0_Installation
https://fedoraproject.org/wiki/Test_Results:Fedora_37_Branched_20220826.n.0_Base
https://fedoraproject.org/wiki/Test_Results:Fedora_37_Branched_20220826.n.0_Server
https://fedoraproject.org/wiki/Test_Results:Fedora_37_Branched_20220826.n.0_Cloud
https://fedoraproject.org/wiki/Test_Results:Fedora_37_Branched_20220826.n.0_Desktop
https://fedoraproject.org/wiki/Test_Results:Fedora_37_Branched_20220826.n.0_Security_Lab

Thank you for testing!
-- 
Mail generated by adamwill and a text editor
___
test-announce mailing list -- test-annou...@lists.fedoraproject.org
To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test-annou...@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: sqlcipher soname change in rawhide

[Fabio Valentini]

On Fri, Aug 26, 2022, 21:20 Demi Marie Obenour 
wrote:

> On 8/26/22 06:12, Fabio Valentini wrote:
> > On Fri, Aug 26, 2022 at 3:12 AM Carl George  wrote:
> >>
> >> sqlcipher has been requested to be built in epel9 [0].  Rather than
> >> branching it from the current rawhide version, I plan to update
> >> rawhide to the latest upstream version first [1].  This involves an
> >> soname change from libsqlcipher-3.34.1.so.0 to
> >> libsqlcipher-3.39.2.so.0.  This will require six packages to be
> >> rebuilt.
> >>
> >> [root@f38-container:~]# repoquery --repo
> rawhide-source,rawhide-modular-source \
> >>> --quiet --queryformat '%{name}' --archlist src --whatrequires
> sqlcipher-devel
> >> libgda
> >> python-peewee
> >> sqlitebrowser
> >> [root@f38-container:~]# repoquery --repo
> rawhide-source,rawhide-modular-source \
> >>> --quiet --queryformat '%{name}' --archlist src --whatrequires
> 'pkgconfig(sqlcipher)'
> >> kmymoney
> >> rust-libsqlite3-sys
> >> skrooge
> >
> > Please do not rebuild rust-libsqlite3-sys. It is a source-only package
> > that does not ship any compiled code.
> > All packages built from rust-libsqlite3-sys are noarch (i.e. they
> > can't - by definition - contain architecture-specific binaries).
> > Any built binaries that link against libsqlcipher are only used for
> > tests, but not shipped with built packages.
>
> Rust FFI uses the ABI, not the API, so if rust-libsqlite3-sys is based on
> bindgen
> then the generated Rust code will need to be recreated.
>

Yes, and that happens on-the-fly in the crate's build.rs script, so
rebuilding the package has zero effect, because the bindings are *always*
generated from headers at build-time, and are not included in the package
at all.

Fabio


-- 
> Sincerely,
> Demi Marie Obenour (she/her/hers)
> ___
> 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: F37 Beta blocker status email

[Ben Cotton]

Action summary


Accepted blockers
-

1. osinfo-db — failed to install server iso with virt-install due to
the missing of isolinux in the media — NEW
ACTION: Maintainers to create update with upstream MR 501

2. sddm — Logout from KDE session on Rawhide goes to console, not SDDM
— ASSIGNED
ACTION: Maintainers to diagnose issue

Proposed blockers
-

1. distribution — "dnf update" runs out of memory on swapless machines
with 1G or less of RAM — ASSIGNED
ACTION: mattdm to coordinate long-term solution

2. openssl-pkcs11 — dnssec-keyfromlabel fails with
openssl-pkcs11-0.4.12-1.fc36 — NEW
ACTION: Maintainers to diagnose issue

3. rpm-ostree — Failing services in new Fedora IoT installations with
RO /sysroot — NEW
ACTION: IoT to apply PR #8

Bug-by-bug detail
=

Accepted blockers
-

1. osinfo-db — https://bugzilla.redhat.com/show_bug.cgi?id=2103835 — NEW
failed to install server iso with virt-install due to the missing of
isolinux in the media

virt-install fails because there's no isolinux path, where it looks
for vmlinuz and initrd.img . Upstream merge request 501 contains a
candidate fix. This should allow us to see if RHBZ 2119633 also
affects F37.

2. sddm — https://bugzilla.redhat.com/show_bug.cgi?id=2110801 — NEW
Logout from KDE session on Rawhide goes to console, not SDDM

After logging out of KDE Plasma, you end up at a console on tty2. SDDM
had been running on tty1 but just shows a flashing cursor. Update
FEDORA-2022-8456442870 reverted sddm back to X11, however the lastest
compose appears to still be using Wayland.

Proposed blockers
-

1. distribution — https://bugzilla.redhat.com/show_bug.cgi?id=1907030 — NEW
"dnf update" runs out of memory on swapless machines with 1G or less of RAM

dnf is killed by oom-kill on machines with 512 MB of RAM. Adding a
swap disk or disabling the updates repo works around this issue.
Recently, FCOS has seen this behavior with 1 GB VMs. The issue appears
to be the size of the metadata for the repository. mattdm is going to
coordinate a long-term solution for this.

2. openssl-pkcs11 — https://bugzilla.redhat.com/show_bug.cgi?id=2115865 — NEW
dnssec-keyfromlabel fails with openssl-pkcs11-0.4.12-1.fc36

Tests in openQA cannot resolve kojipkgs.fedoraproject.org. Previous
F37 build (openssl-pkcs11-0.4.12-1.fc37) behaves as expected. The
corresponding versions both work on F36. Disabling dnssec on the
server is a workaround.

3. rpm-ostree — https://bugzilla.redhat.com/show_bug.cgi?id=2121197 — NEW
Failing services in new Fedora IoT installations with RO /sysroot

The switch to read-only /sysroot results in IoT tests with many
failing services. https://pagure.io/fedora-iot/ostree/pull-request/8
contains a candidate fix.

-- 
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Let's enable Koschei for all packages automatically

[Demi Marie Obenour]

On 8/26/22 09:22, Stephen Smoogen wrote:
> On Thu, 25 Aug 2022 at 03:58, Miro Hrončok  wrote:
> 
>> Hello folks,
>>
>> during our Nest FESCo session, we've talked about enabling Koschei [1] for
>> all
>> packages automatically.
>>
>> There seem to be a consensus by FESCo members, that it would be a good
>> thing.
>>
>> What would it take?
>>
>> 1) Koji resources
>>
>> I think we can try to enable this and see if it burns. I think ti won't.
>>
>>
> It will, but we will deal with it. Koschei builds have had to be throttled
> down multiple times in the past due to the fact that all those builds
> working or failed take up some disk space on builders for a bit. Get a lot
> of churn and koschei builds and you end up with builders without disk space
> and various developers who are saying yes! in the past yelling about not
> being able to do their real work :). We will just have to figure out how to
> throttle things down safely to make it work. The current
> koji+all-other-stuff is a batch operating system (line up the tasks and do
> them until they are done) which we treat like a time-share which only holds
> when things are 'low' usage.
> 
> Long term I think we are going to need to figure out ways to get the fedora
> buildsystem safely and securely into various clouds to allow for many more
> builders and resources. [This isn't just koji, but the assumptions that all
> the other tools in the fedora system from the 'dashboard' to the
> koji+bodhi+osbs+odcs+pungi+etc+etc build system that all the resources are
> close and local in a 'sealed' firewalled off space. ]

How bursty is the builder workload?  Also, if you go this route, I strongly
recommend enforcing CA pinning (not public key pinning!) to the appropriate
Google/Amazon roots.
-- 
Sincerely,
Demi Marie Obenour (she/her/hers)
___
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: sqlcipher soname change in rawhide

[Demi Marie Obenour]

On 8/26/22 06:12, Fabio Valentini wrote:
> On Fri, Aug 26, 2022 at 3:12 AM Carl George  wrote:
>>
>> sqlcipher has been requested to be built in epel9 [0].  Rather than
>> branching it from the current rawhide version, I plan to update
>> rawhide to the latest upstream version first [1].  This involves an
>> soname change from libsqlcipher-3.34.1.so.0 to
>> libsqlcipher-3.39.2.so.0.  This will require six packages to be
>> rebuilt.
>>
>> [root@f38-container:~]# repoquery --repo 
>> rawhide-source,rawhide-modular-source \
>>> --quiet --queryformat '%{name}' --archlist src --whatrequires 
>>> sqlcipher-devel
>> libgda
>> python-peewee
>> sqlitebrowser
>> [root@f38-container:~]# repoquery --repo 
>> rawhide-source,rawhide-modular-source \
>>> --quiet --queryformat '%{name}' --archlist src --whatrequires 
>>> 'pkgconfig(sqlcipher)'
>> kmymoney
>> rust-libsqlite3-sys
>> skrooge
> 
> Please do not rebuild rust-libsqlite3-sys. It is a source-only package
> that does not ship any compiled code.
> All packages built from rust-libsqlite3-sys are noarch (i.e. they
> can't - by definition - contain architecture-specific binaries).
> Any built binaries that link against libsqlcipher are only used for
> tests, but not shipped with built packages.

Rust FFI uses the ABI, not the API, so if rust-libsqlite3-sys is based on 
bindgen
then the generated Rust code will need to be recreated.
-- 
Sincerely,
Demi Marie Obenour (she/her/hers)
___
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

Test gating: missing required test results

[Ben Beasley]

When a Bodhi update is gated on required tests that seem to remain 
“missing” indefinitely, is there anything I can do to re-try them? Or do 
I just have to attempt to waive the missing test results?


https://bodhi.fedoraproject.org/updates/FEDORA-2022-014e78ee9d 



The corresponding update for F38 worked fine. The necessary test results 
appeared and the update passed gating after about 20 minutes.


https://bodhi.fedoraproject.org/updates/FEDORA-2022-2eed8152f6

– Ben Beasley (FAS music)
___
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: liburing update

[Michel Alexandre Salim]

On Tue, Aug 23, 2022 at 08:07:13AM +0100, Richard W.M. Jones wrote:
> io_uring (https://en.wikipedia.org/wiki/Io_uring) is an important
> kernel facility, essentially an alternate way of dispatching system
> calls more efficiently.  It's used in a lot of high performance
> situations.  Although you can talk to it directly, most users should
> be using liburing, a C library.
> 
> We haven't updated liburing for "a while", since April 2021 to
> liburing 2.0.  There have been several upstream versions since then,
> the latest is liburing 2.2, released in June.
> 
> In theory this version is compatible and uses symbol versions:
> 
> $ rpm -q --provides liburing
> liburing = 2.2-1.fc38
> liburing(x86-64) = 2.2-1.fc38
> liburing.so.2()(64bit)
> liburing.so.2(LIBURING_2.0)(64bit)
> liburing.so.2(LIBURING_2.1)(64bit)
> liburing.so.2(LIBURING_2.2)(64bit)
> 
> so in theory this is not an ABI break.  In practice I'm told that the
> API of liburing is not very stable.
> 
From my experience maintaining folly, the liburing API is definitely not
very stable, and... this update might make it possible to compile more
recent versions of folly again.

So +1 for updating. Not sure if we should also reach out to upstream to
do an ABI bump, but for neovim (which has a similar issue with
tree-sitter having an internal API version that's not reflected in the
soname) I just add additional versioned BR and R dependencies.

Best regards,

-- 
Michel Alexandre 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: Users with commit rights in src.fp.o but no more in packager group

[Kevin Fenzi]

On Wed, Aug 24, 2022 at 05:30:35PM +, Mattia Verga via devel wrote:
> Following my comment in
> https://pagure.io/fesco/issue/2856#comment-812870 I wrote a simple
> script to check how many users have commit rights onto some project in
> src.fp.o, but aren't (anymore) members of the `packager` group:
> 
> ```
> Found 31 users with commit privileges but not in packager group:
> packaging-team
> stefanok
> mmcgrath
> kernel-maint
> oddshocks
> systemd-maint
> lvm-team
> abrt-team
> i18n-team
> amahdal
> jvlomax
> coremodule
> libvirt-maint
> sonkun
> fonts-sig
> narasim
> perl-sig
> dcr226
> gecko-maint
> ozamosi
> sheltren
> anaconda-maint
> java-sig
> duriantang
> dracut-maint
> ipa-maint
> kmod-maint
> mariobl
> mck182
> design-sw
> cdeccio
> ```
> 
> With the exclusion of *-team, *-sig and *-maint, I think packaging
> rights should be removed from those users.

I think these are users who manually removed themselves from the
packager group, but didn't remove all their acls first. (and legit
groups/sigs).

> Also, as per my comment linked above, I think there should be some check
> to prevent users removed from packager group to maintain commit rights.
> No idea where/how to implement that.

I don't think it happens too often. We could make a script that checks
it from time to time tho. Might be a good cadidate for a toddler (
https://pagure.io/toddlers)

In the mean time I agree we should remove the non team/sig/maint users
above. 

kevin


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: hardened memory allocate port to linux-fedora system for secutiry

[Daniel Micay via devel]

On Mon, Aug 15, 2022 at 07:39:46PM -0700, John Reiser wrote:
> On 8/13/22, Demi Marie Obenour wrote:
> > On 8/13/22, Kevin Kofler via devel wrote:
> > > martin luther wrote:
> > > > should we implement https://github.com/GrapheneOS/hardened_malloc/
> > > > it is hardened memory allocate it will increase the security of fedora
> > > > according to the graphene os team it can be ported to linux as well need
> > > > to look at it
> > 
> > CCing Daniel Micay who wrote hardened_malloc.
> > 
> > > There are several questions that come up:  [[snip]]
> 
> It seems to me that hardened_malloc could increase working set and RAM
> desired by something like 10% compared to glibc for some important workloads,
> such as Fedora re-builds.  From page 22 of [1] (attached here; 203KB), the 
> graph
> of number of requests versus requested size shows that blocks of size <= 128
> were requested tens to thousands of times more often than all the rest.

It has far less fragmentation than glibc malloc. It also has far lower
metadata overhead since there are no headers on allocations and only a
few bits consumed per small allocation. glibc has over 100% metadata
overhead for 16 byte allocations while for hardened_malloc it's a very
low percentage. Of course, you need to compare with slab allocation
quarantines and slab allocation canaries disabled in hardened_malloc.

> For sizes from 0 through 128, the "Size classes" section of README.md of [2]
> documents worst-case internal fragmentation (in "slabs") of 93.75% to 11.72%.
> That seems too high.  Where are actual measurements for workloads such as
> Fedora re-builds?

Internal malloc means fragmentation caused by size class rounding. There
is no way to have size classes that aren't multiples of 16 due to it
being required by the x86_64 and arm64 ABI. glibc has over 100% overhead
for 16 byte allocations due to header metadata and other metadata. It
definitely isn't lighter for those compared to a modern slab allocator.

There's a 16 byte alignment requirement for malloc on x86_64 and arm64
so there's no way to have any size classes between the initial multiples
of 16.

Slab allocation canaries are an optional hardened_malloc feature adding
8 byte random canaries to the end of allocations, which in many cases
will increase the size class if there isn't room within the padding.
Slab allocation quarantines are another optional feature which require
dedicating substantial memory to avoiding reuse of allocations.

You should compare without the optional features enabled as a baseline
because glibc doesn't have any of those security features, and the
baseline hardened_malloc design is far more secure.

> (Also note that the important special case of malloc(0), which is analogous
> to (gensym) of Lisp and is implemented internally as malloc(1), consumes
> 16 bytes and has a fragmentation of 93.75% for both glibc and hardened_malloc.
> The worst fragmentation happens for *every* call to malloc(0), which occurred
> about 800,000 times in the sample.  Yikes!)

malloc(0) is not implemented as malloc(1) in hardened_malloc and does
not use any memory for the data, only the metadata, which is a small
percentage of the allocation size even for 16 byte allocations since
there is only slab metadata for the entire slab and bitmaps to track
which slots are used. There are no allocation headers.

Doing hundreds of thousands of malloc(0) allocations only uses a few
bytes of memory in hardened_malloc. Each allocation requires a bit in
the bitmap and each slab of 256x 16 byte allocations (4096 byte slab)
has slab metadata. All the metadata is in a dedicated metadata region.

I strong recommend reading all the documentation thoroughly:

https://github.com/GrapheneOS/hardened_malloc/blob/main/README.md

hardened_malloc is oriented towards security and provides a bunch of
important security properties unavailable with glibc malloc. It also has
lower fragmentation and with the optional security features disabled
also lower memory usage for large processes and especially over time. If
you enable the slab quarantines, that's going to use a lot of memory. If
you enable slab canaries, you give up some of the memory usage reduction
from not having per-allocation metadata headers. Neither of those
features exists in glibc malloc, jemalloc, etc. so it's not really fair
to enable the optional security features for hardened_malloc and compare
with allocators without them.

Slab allocation quarantines in particular inherently require a ton of
memory in order to delay reuse of allocations for as long of a time as
is feasible. This pairs well with zero-on-free + write-after-free-check
based on zero-on-free, since if any non-zero write occurs while
quarantined/freed it will be detected before the allocation is reused.
As long as zero-on-free is enabled, which it is even for the sample
light configuration, then all memory is known to be zeroed at allocation
time, which is how the write-after-free-check works. All of 

Re: Check out the Fedora Packager Dashboard!

[Björn Persson]

Fabio Valentini wrote:
> On Thu, Aug 25, 2022 at 11:43 AM Artur Frenszek-Iwicki
>  wrote:
> > I'll forget the meaning and the numbers will go back to being visual 
> > clutter. It would be immensely helpful
> > to have some symbolic icons next to the numbers, which would allow to 
> > easily guess what each of them means.
> 
> Sounds like you need to clear your browser cache or something, because
> there *are* symbols next to these numbers:
> https://decathorpe.fedorapeople.org/packager-dashboard.png

I too can see the icons when I allow fontawesome.com, but few of them
help with understanding the numbers. The beetle for "bugs" and the
speech bubble for "comments" are pretty obvious, but I still have to
point to all the others to find out what they mean, and even then many
of them seem completely random. How does a lightning bolt symbolize
updates? What's the connection between a shield and priority? A
triangle, a circle and a square combine into "overrides"? There are two
different line chart icons. How does one remember which is which? And a
seatbelt apparently means "orphans" somehow.

I assume that "PRs" stands for "pull requests". The icon for that is
the word "git". That's better than a random unrelated picture, but if a
picture is just text, then it should be actual text and not a picture.
It's also somewhat inaccurate because pull requests aren't a Git thing
but a concept that some web interfaces layer on top of Git.

Rather than hiding the intelligible words in mouseover boxes, it would
be better to write them directly on the screen instead of the icons. If
there is some idea that the icons should be language-independent, then
the beetle also fails. Software defects are not called insects in all
languages.

> > Similarly, at the top of the page, I get a banner that informs me about FAS 
> > integration and says:  
> > > After linking the dashboard with your FAS through the settings menu...  
> > Which is all nice and dandy, but doing a Ctrl+F on the page for "settings" 
> > gives exactly one match -
> > that being the text in the banner. So there's no visible link to said 
> > "settings menu" anywhere.
> > How do I access it?  
> 
> The big "gear" icon (the almost universal symbol for "Settings") in
> the top panel should be what you're looking for.

The gear is called "Options", and beside it is an icon called
"Customize dashboard". "Settings" could refer to either of those. It
would be nice to have consistent terminology, but hey, we can always
click on everything and explore.

The gear icon is also misleading. It alludes to machinery in motion, so
it suggests a menu of commands to do things, rather than options or
settings. There is a wrench icon that would be a good symbol for
settings, but that apparently means Koschei.

Björn Persson


pgpmWCLh0Inux.pgp
Description: OpenPGP digital signatur
___
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-legal-list] More Ansible license changes

[Richard Fontana]

On Thu, Aug 25, 2022 at 11:32 PM Maxwell G  wrote:
>
> Hi Fedorians,
>
> I'm back with more ansible license updates. Upstream, some of the community
> Ansible Collections have adopted the REUSE specification, which makes it much
> easier to determine the overall license. For collections that have adopted
> this, the license texts are all stored as files in one directory, instead of
> being spread out throughout the source tree as file headers. I would like to
> thank the upstream developers for working with me on this.
>
> The License tag of ansible-collection-community-general has changed from
> "GPLv3+ and BSD and Python" to "GPL-3.0-or-later AND BSD-2-Clause AND PSF-2.0
> AND MIT". See 
> https://src.fedoraproject.org/rpms/ansible-collection-community-general/pull-request/8.
>
> The License tag of ansible has changed from "GPLv3+" to "GPL-3.0-or-later AND
> Apache-2.0 AND BSD-2-Clause AND BSD-3-Clause AND MIT AND MPL-2.0 AND PSF-2.0".
> I cannot claim this to be 100% accurate, but I have done my best to determine
> the overall license. Note that ansible is a curated bundle of 103 Ansible
> collections, so this task is a bit difficult. See
> https://src.fedoraproject.org/rpms/ansible/pull-request/32.

Thank you! We are not aiming for 100% accuracy (as that is impossible
outside of the simplest [from a licensing standpoint] packages) but
for greater accuracy than was possible or expected under earlier
approaches. This is very helpful.

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: [Fedocal] Reminder meeting : ELN SIG

[Stephen Gallagher]

On Fri, Aug 26, 2022 at 11:25 AM Alexander Sosedkin
 wrote:
>
> On Fri, Aug 26, 2022 at 5:09 PM Stephen Gallagher  wrote:
> > On Fri, Aug 26, 2022 at 10:12 AM Alexander Sosedkin
> >  wrote:
> > > On Fri, Aug 26, 2022 at 4:06 PM Troy Dawson  wrote:
> > > > On Fri, Aug 26, 2022 at 6:55 AM Alexander Sosedkin 
> > > >  wrote:
> > > >> Not a full-blown meeting prompt,
> > > >> but I recall complaining about `fipscheck` missing from ELN 
> > > >> repositories,
> > > >> and IIRC it was blocked on something that time.
> > > >> If you could have a second look, that'd be appreciated,
> > > >> as it's a popular build dependency among the packages I'm concerned 
> > > >> about.
> > > >
> > > >
> > > > is  `fipscheck` = libkcapi-fipscheck ?
> > > > If so, it's built and in ELN.
> > > > It did have a failed build in July, but it's been rebuilding fine since 
> > > > July 27.
> > >
> > > I can't find it under
> > > https://odcs.fedoraproject.org/composes/production/latest-Fedora-ELN/
> >
> > https://tiny.distro.builders/view-srpm--view-eln--libkcapi.html has it
> > listed as part of the buildroot, but it's not specifically included in
> > the ELN compose. The same is true for CentOS Stream 9[1] and RHEL 9,
> > so if this is incorrect it should be resolved there and we will pull
> > it in. Otherwise, it remains available in the Koji buildroot,
>
> Is there a repository URL I can readily use
> to enable this Koji buildroot on an ELN system?
>

baseurl=https://kojipkgs.fedoraproject.org/repos/eln-build/latest/$basearch/
___
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: [Fedocal] Reminder meeting : ELN SIG

[Alexander Sosedkin]

On Fri, Aug 26, 2022 at 5:09 PM Stephen Gallagher  wrote:
> On Fri, Aug 26, 2022 at 10:12 AM Alexander Sosedkin
>  wrote:
> > On Fri, Aug 26, 2022 at 4:06 PM Troy Dawson  wrote:
> > > On Fri, Aug 26, 2022 at 6:55 AM Alexander Sosedkin  
> > > wrote:
> > >> Not a full-blown meeting prompt,
> > >> but I recall complaining about `fipscheck` missing from ELN repositories,
> > >> and IIRC it was blocked on something that time.
> > >> If you could have a second look, that'd be appreciated,
> > >> as it's a popular build dependency among the packages I'm concerned 
> > >> about.
> > >
> > >
> > > is  `fipscheck` = libkcapi-fipscheck ?
> > > If so, it's built and in ELN.
> > > It did have a failed build in July, but it's been rebuilding fine since 
> > > July 27.
> >
> > I can't find it under
> > https://odcs.fedoraproject.org/composes/production/latest-Fedora-ELN/
>
> https://tiny.distro.builders/view-srpm--view-eln--libkcapi.html has it
> listed as part of the buildroot, but it's not specifically included in
> the ELN compose. The same is true for CentOS Stream 9[1] and RHEL 9,
> so if this is incorrect it should be resolved there and we will pull
> it in. Otherwise, it remains available in the Koji buildroot,

Is there a repository URL I can readily use
to enable this Koji buildroot on an ELN system?

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

Re: Confused about what to do about a ticket

[Mattia Verga via devel]

Il 26/08/22 16:02, Vít Ondruch ha scritto:
> If you included `Resolves: rhbz#2114563` in the changelog, the
> automatically created bodhi update would resolve the ticket. Since you
> have not done this, then you have to close the ticket yourself and
> possibly include the NVR in 'Fixed In Versoin' field.
>
>
> Vít
>
>
BTW, it's now simpler to have bugs attached to automatic updates. The
regex now matches everything like `rhbz#123456` without the need of the
starting `Resolves:` or similar.

Accepted prefixes are `rhbz#`, `fedora#` or `epel#`. If you want to
mention a bug in the changelog without actually attaching the bug to an
update (so that it will not be closed automatically) a simple trick is
to put a whitespace between the prefix and the bug number: `rhbz #123456`.

Mattia

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

Re: [Fedocal] Reminder meeting : ELN SIG

[Stephen Gallagher]

On Fri, Aug 26, 2022 at 10:12 AM Alexander Sosedkin
 wrote:
>
> On Fri, Aug 26, 2022 at 4:06 PM Troy Dawson  wrote:
>
> > On Fri, Aug 26, 2022 at 6:55 AM Alexander Sosedkin  
> > wrote:
> >> Not a full-blown meeting prompt,
> >> but I recall complaining about `fipscheck` missing from ELN repositories,
> >> and IIRC it was blocked on something that time.
> >> If you could have a second look, that'd be appreciated,
> >> as it's a popular build dependency among the packages I'm concerned about.
> >
> >
> > is  `fipscheck` = libkcapi-fipscheck ?
> > If so, it's built and in ELN.
> > It did have a failed build in July, but it's been rebuilding fine since 
> > July 27.
>
> I can't find it under
> https://odcs.fedoraproject.org/composes/production/latest-Fedora-ELN/

https://tiny.distro.builders/view-srpm--view-eln--libkcapi.html has it
listed as part of the buildroot, but it's not specifically included in
the ELN compose. The same is true for CentOS Stream 9[1] and RHEL 9,
so if this is incorrect it should be resolved there and we will pull
it in. Otherwise, it remains available in the Koji buildroot, but
won't show up in the ELN compose.

[1] 
https://gitlab.com/redhat/centos-stream/release-engineering/pungi-centos/-/blob/centos-9-stream/prepopulate.json#L31761
___
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: Confused about what to do about a ticket

[Ron Olson]

Thanks for that info, I actually did not know about that particular feature of 
the changelog. I’ll try to use that from now on.

On 26 Aug 2022, at 9:02, Vít Ondruch wrote:

> If you included `Resolves: rhbz#2114563` in the changelog, the automatically 
> created bodhi update would resolve the ticket. Since you have not done this, 
> then you have to close the ticket yourself and possibly include the NVR in 
> 'Fixed In Versoin' field.
>
>
> Vít
>
>
>
> Dne 26. 08. 22 v 15:48 Ron Olson napsal(a):
>> Hey all,
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=2114563 was reported against 
>> Swift on Rawhide. I fixed the issue and responded on 8/4 that the Koji build 
>> was successful, but I got two additional, presumably automated, notes from 
>> Ben Cotton and Miro that suggest something else needs to be done. Since this 
>> is/was a rawhide build there’s nothing to “fedpkg update” as I recall, so I 
>> guess what I’m asking is what should I do to make it clear that Swift is 
>> working for Rawhide/F37? I admit I’ve always been kind-of unsure how Rawhide 
>> works insofar as I’ve never submitted a “formal update” to it (i.e. the 
>> aforementioned “fedpkg update” command).
>>
>> Thanks,
>>
>> Ron
>> ___
>> 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
___
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: Confused about what to do about a ticket

[Jarek Prokop]

Hi,

Usually for Rawhide updates CLOSED RAWHIDE + add NVR into `fixed in version`
if only Rawhide fixes that bug (e.g., a new software version), that 
should be enough.


But it seems auto updates can take care of the tickets if you specify 
the bugs via the `Resolves: rhbz#1234` references as noted by Vít.


A webpage… Depends what you plan on doing, I use this if I am unsure in 
the bug status workflow: 
https://docs.fedoraproject.org/en-US/package-maintainers/bug_status/


Regards,
Jarek

On 8/26/22 16:28, Ron Olson wrote:

Thanks for the info, I did just that. Do you or anyone knows if there is a 
webpage that describes how to handle Rawhide updates specifically? I haven’t 
found anything useful about what to do in this particular situation.

Ron

On 26 Aug 2022, at 9:04, Tom Hughes wrote:


On 26/08/2022 14:48, Ron Olson wrote:


https://bugzilla.redhat.com/show_bug.cgi?id=2114563  was reported against Swift 
on Rawhide. I fixed the issue and responded on 8/4 that the Koji build was 
successful, but I got two additional, presumably automated, notes from Ben 
Cotton and Miro that suggest something else needs to be done. Since this is/was 
a rawhide build there’s nothing to “fedpkg update” as I recall, so I guess what 
I’m asking is what should I do to make it clear that Swift is working for 
Rawhide/F37? I admit I’ve always been kind-of unsure how Rawhide works insofar 
as I’ve never submitted a “formal update” to it (i.e. the aforementioned 
“fedpkg update” command).

Well it was reported before branching and you fixed it but
didn't actually close it so it looks like it is still an active
bug and hence got automatically moved to F37 and added as a
blocker to the FTBFS bug.

If it was fixed before branching, as appears to be the case then
the fix is in F37 now so you can just close it NEXTRELEASE.

Tom

--
Tom Hughes (t...@compton.nu)
http://compton.nu/

___
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: Confused about what to do about a ticket

[Ron Olson]

Thanks for the info, I did just that. Do you or anyone knows if there is a 
webpage that describes how to handle Rawhide updates specifically? I haven’t 
found anything useful about what to do in this particular situation.

Ron

On 26 Aug 2022, at 9:04, Tom Hughes wrote:

> On 26/08/2022 14:48, Ron Olson wrote:
>
>> https://bugzilla.redhat.com/show_bug.cgi?id=2114563 was reported against 
>> Swift on Rawhide. I fixed the issue and responded on 8/4 that the Koji build 
>> was successful, but I got two additional, presumably automated, notes from 
>> Ben Cotton and Miro that suggest something else needs to be done. Since this 
>> is/was a rawhide build there’s nothing to “fedpkg update” as I recall, so I 
>> guess what I’m asking is what should I do to make it clear that Swift is 
>> working for Rawhide/F37? I admit I’ve always been kind-of unsure how Rawhide 
>> works insofar as I’ve never submitted a “formal update” to it (i.e. the 
>> aforementioned “fedpkg update” command).
>
> Well it was reported before branching and you fixed it but
> didn't actually close it so it looks like it is still an active
> bug and hence got automatically moved to F37 and added as a
> blocker to the FTBFS bug.
>
> If it was fixed before branching, as appears to be the case then
> the fix is in F37 now so you can just close it NEXTRELEASE.
>
> Tom
>
> -- 
> Tom Hughes (t...@compton.nu)
> http://compton.nu/
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: [Fedocal] Reminder meeting : ELN SIG

[Alexander Sosedkin]

On Fri, Aug 26, 2022 at 4:06 PM Troy Dawson  wrote:

> On Fri, Aug 26, 2022 at 6:55 AM Alexander Sosedkin  
> wrote:
>> Not a full-blown meeting prompt,
>> but I recall complaining about `fipscheck` missing from ELN repositories,
>> and IIRC it was blocked on something that time.
>> If you could have a second look, that'd be appreciated,
>> as it's a popular build dependency among the packages I'm concerned about.
>
>
> is  `fipscheck` = libkcapi-fipscheck ?
> If so, it's built and in ELN.
> It did have a failed build in July, but it's been rebuilding fine since July 
> 27.

I can't find it under
https://odcs.fedoraproject.org/composes/production/latest-Fedora-ELN/
___
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

[Vít Ondruch]

Dne 26. 08. 22 v 15:22 Stephen Smoogen napsal(a):



On Thu, 25 Aug 2022 at 03:58, Miro Hrončok  wrote:

Hello folks,

during our Nest FESCo session, we've talked about enabling Koschei
[1] for all
packages automatically.

There seem to be a consensus by FESCo members, that it would be a
good thing.

What would it take?

1) Koji resources

I think we can try to enable this and see if it burns. I think ti
won't.


It will, but we will deal with it. Koschei builds have had to be 
throttled down multiple times in the past due to the fact that all 
those builds working or failed take up some disk space on builders for 
a bit.



Unfortunately this took toll on Koschei usability, because the logs are 
not preserved :/ I wish the logs were extracted from Koji and stored 
somewhere where they can be kept for more then two weeks.


Just yesterday, I was looking into rubygem-rubyzip failures [1], which 
happened every ~8th build. Without logs, Koschei was not really helpful.



Vít


P.S. for the curious, while the package is noarch, the build failed when 
executed on s390x. IOW LE / BE issue.



[1] https://koschei.fedoraproject.org/package/rubygem-rubyzip




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

Re: Confused about what to do about a ticket

[Tom Hughes via devel]

On 26/08/2022 14:48, Ron Olson wrote:


https://bugzilla.redhat.com/show_bug.cgi?id=2114563 was reported against Swift 
on Rawhide. I fixed the issue and responded on 8/4 that the Koji build was 
successful, but I got two additional, presumably automated, notes from Ben 
Cotton and Miro that suggest something else needs to be done. Since this is/was 
a rawhide build there’s nothing to “fedpkg update” as I recall, so I guess what 
I’m asking is what should I do to make it clear that Swift is working for 
Rawhide/F37? I admit I’ve always been kind-of unsure how Rawhide works insofar 
as I’ve never submitted a “formal update” to it (i.e. the aforementioned 
“fedpkg update” command).


Well it was reported before branching and you fixed it but
didn't actually close it so it looks like it is still an active
bug and hence got automatically moved to F37 and added as a
blocker to the FTBFS bug.

If it was fixed before branching, as appears to be the case then
the fix is in F37 now so you can just close it NEXTRELEASE.

Tom

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

Re: Confused about what to do about a ticket

[Vít Ondruch]

If you included `Resolves: rhbz#2114563` in the changelog, the 
automatically created bodhi update would resolve the ticket. Since you 
have not done this, then you have to close the ticket yourself and 
possibly include the NVR in 'Fixed In Versoin' field.



Vít



Dne 26. 08. 22 v 15:48 Ron Olson napsal(a):

Hey all,

https://bugzilla.redhat.com/show_bug.cgi?id=2114563 was reported against Swift 
on Rawhide. I fixed the issue and responded on 8/4 that the Koji build was 
successful, but I got two additional, presumably automated, notes from Ben 
Cotton and Miro that suggest something else needs to be done. Since this is/was 
a rawhide build there’s nothing to “fedpkg update” as I recall, so I guess what 
I’m asking is what should I do to make it clear that Swift is working for 
Rawhide/F37? I admit I’ve always been kind-of unsure how Rawhide works insofar 
as I’ve never submitted a “formal update” to it (i.e. the aforementioned 
“fedpkg update” command).

Thanks,

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


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

Re: [Fedocal] Reminder meeting : ELN SIG

[Alexander Sosedkin]

On Fri, Aug 26, 2022 at 2:54 PM Stephen Gallagher  wrote:
>
> On Thu, Aug 25, 2022 at 8:00 AM  wrote:
> >
> > Dear all,
> >
> > You are kindly invited to the meeting:
> >ELN SIG on 2022-08-26 from 12:00:00 to 13:00:00 US/Eastern
> >At fedora-meet...@irc.libera.chat
> >
> > The meeting will be about:
>
> We have no agenda for today's meeting. If anyone has a topic to bring
> up, please reply to this email. Otherwise, the meeting will be
> canceled for this week.

Not a full-blown meeting prompt,
but I recall complaining about `fipscheck` missing from ELN repositories,
and IIRC it was blocked on something that time.
If you could have a second look, that'd be appreciated,
as it's a popular build dependency among the packages I'm concerned about.
___
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

Confused about what to do about a ticket

[Ron Olson]

Hey all,

https://bugzilla.redhat.com/show_bug.cgi?id=2114563 was reported against Swift 
on Rawhide. I fixed the issue and responded on 8/4 that the Koji build was 
successful, but I got two additional, presumably automated, notes from Ben 
Cotton and Miro that suggest something else needs to be done. Since this is/was 
a rawhide build there’s nothing to “fedpkg update” as I recall, so I guess what 
I’m asking is what should I do to make it clear that Swift is working for 
Rawhide/F37? I admit I’ve always been kind-of unsure how Rawhide works insofar 
as I’ve never submitted a “formal update” to it (i.e. the aforementioned 
“fedpkg update” command).

Thanks,

Ron
___
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: Packages silently dropping approved changes

[Ben Beasley]

The policies specifying use of FlexiBLAS[1] are full of MUSTs; you can’t just 
opt out and reject all prospective PRs out of hand. If someone can get the 
package working with FlexiBLAS, you should accept a PR. If you think freefem++ 
needs to be exempt from the requirement, you should open an FPC ticket[2] 
explaining why and requesting an explicit exception.

[1] 
https://docs.fedoraproject.org/en-US/packaging-guidelines/BLAS_LAPACK/#_packaging_blaslapack_dependent_packages
[2] https://pagure.io/packaging-committee/issues

On Thu, Aug 25, 2022, at 6:36 PM, Ralf Corsépius wrote:
> Am 25.08.22 um 23:00 schrieb Iñaki Ucar:
>> On Thu, 25 Aug 2022 at 19:15, Iñaki Ucar  wrote:
>>>
>>> On Thu, 25 Aug 2022 at 18:34, Ralf Corsépius  wrote:

 Am 25.08.22 um 13:19 schrieb Iñaki Ucar:

> I assume their maintainers didn't do it on purpose, maybe it was
> easier for a certain update, didn't have time to look into it and
> weren't aware of the guideline. But this is very frustrating. Seeing
> many hours of work just wiped out without any notice or explanation is
> very frustrating.

 In my case (freefem++), it was actually was a mixture of all.

 To cut a long story short: This flexblas stuff doesn't "harmonize well"
 with freefem++, rsp. more bluntly speaking, flexblas breaks freefem++.

 Because of this, when going after freefem++'s regressions, years after
 the flexiblas changes had been introduced, I inadvertedly and
 accidentally reverted the flexblas related changes, because these
 apparently do not work out with freefem++.
>>>
>>> How exactly does flexiblas break freefem++? I see v4.10 was built just
>>> fine. Then v4.11 reverted to openblas. If it works with openblas, I
>>> see no reason to break with flexiblas, among other things because
>>> openblas is the default backend. Moreover, arpack, superlu,
>>> suitesparse and other BuildRequires link against flexiblas.
>> 
>> In fact, freefem++ was one of the easiest packages to adapt: you just
>> set the library, and it does nothing fancy nor too-clever to try to
>> discover anything. 
> Then you haven't looked into details (build.log rsp. config.status).
>
> flexiblas causes freefem's configure script to produce bogus results.
>
>
> Here's a simple patch [1] and a successful scratch
>> build [2], with all checks passing. Please let me know if I'm missing
>> anything, but otherwise, I'll open a PR.
> Please don't and also abstain from submitting pull requests.
>
> ___
> 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: Let's enable Koschei for all packages automatically

[Stephen Smoogen]

On Thu, 25 Aug 2022 at 03:58, Miro Hrončok  wrote:

> Hello folks,
>
> during our Nest FESCo session, we've talked about enabling Koschei [1] for
> all
> packages automatically.
>
> There seem to be a consensus by FESCo members, that it would be a good
> thing.
>
> What would it take?
>
> 1) Koji resources
>
> I think we can try to enable this and see if it burns. I think ti won't.
>
>
It will, but we will deal with it. Koschei builds have had to be throttled
down multiple times in the past due to the fact that all those builds
working or failed take up some disk space on builders for a bit. Get a lot
of churn and koschei builds and you end up with builders without disk space
and various developers who are saying yes! in the past yelling about not
being able to do their real work :). We will just have to figure out how to
throttle things down safely to make it work. The current
koji+all-other-stuff is a batch operating system (line up the tasks and do
them until they are done) which we treat like a time-share which only holds
when things are 'low' usage.

Long term I think we are going to need to figure out ways to get the fedora
buildsystem safely and securely into various clouds to allow for many more
builders and resources. [This isn't just koji, but the assumptions that all
the other tools in the fedora system from the 'dashboard' to the
koji+bodhi+osbs+odcs+pungi+etc+etc build system that all the resources are
close and local in a 'sealed' firewalled off space. ]


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

Fedora 37 compose report: 20220826.n.0 changes

[Fedora Rawhide Report]

OLD: Fedora-37-20220825.n.0
NEW: Fedora-37-20220826.n.0

= SUMMARY =
Added images:0
Dropped images:  0
Added packages:  0
Dropped packages:1
Upgraded packages:   3
Downgraded packages: 0

Size of added packages:  0 B
Size of dropped packages:145.67 KiB
Size of upgraded packages:   15.49 MiB
Size of downgraded packages: 0 B

Size change of upgraded packages:   217.34 KiB
Size change of downgraded packages: 0 B

= ADDED IMAGES =

= DROPPED IMAGES =

= ADDED PACKAGES =

= DROPPED PACKAGES =
Package: python-fastapi-0.78.0-5.fc37
Summary: FastAPI framework
RPMs:python3-fastapi python3-fastapi+all
Size:145.67 KiB


= UPGRADED PACKAGES =
Package:  mutter-43~beta-4.fc37
Old package:  mutter-43~beta-1.fc37
Summary:  Window and compositing manager based on Clutter
RPMs: mutter mutter-devel mutter-tests
Size: 14.97 MiB
Size change:  52.34 KiB
Changelog:
  * Wed Aug 24 2022 Kalev Lember  - 43~beta-2
  - Backport upstream patch to fix a compositor crash (#2120470)

  * Thu Aug 25 2022 Kalev Lember  - 43~beta-3
  - wayland: Ensure to unlink destroy listeners after destruction

  * Thu Aug 25 2022 Kalev Lember  - 43~beta-4
  - wayland: Unlink surface listener when freeing token


Package:  python-smbprotocol-1.9.0-1.fc37
Old package:  python-smbprotocol-1.1.0-5.fc36
Summary:  Interact with a server using the SMB 2/3 Protocol
RPMs: python3-smbprotocol
Size: 260.40 KiB
Size change:  89.12 KiB
Changelog:
  * Fri Jul 22 2022 Fedora Release Engineering  - 
1.1.0-6
  - Rebuilt for https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild

  * Fri Aug 19 2022 Fabian Affolter  - 1.9.0-1
  - Update to latest upstream release 1.9.0 (closes rhbz#2113654, closes 
#2099111)


Package:  python-spnego-0.6.0-1.fc37
Old package:  python-spnego-0.5.0-1.fc37
Summary:  Windows Negotiate Authentication Client and Server
RPMs: python3-spnego
Size: 262.32 KiB
Size change:  75.88 KiB
Changelog:
  * Tue Jun 14 2022 Python Maint  - 0.5.0-2
  - Rebuilt for Python 3.11

  * Fri Jul 22 2022 Fedora Release Engineering  - 
0.5.0-3
  - Rebuilt for https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild

  * Fri Aug 19 2022 Fabian Affolter  - 0.6.0-1
  - Update to latest upstream release 0.6.0 (closes rhbz#2105846, closes 
#2113657)



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

[Bug 1934532] EPEL8 Request: perl-Astro-FITS-CFITSIO

[bugzilla]

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



--- Comment #6 from Fedora Update System  ---
FEDORA-EPEL-2022-d6bb4559c9 has been pushed to the Fedora EPEL 9 testing
repository.

You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-d6bb4559c9

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1934532
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 1934532] EPEL8 Request: perl-Astro-FITS-CFITSIO

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #5 from Fedora Update System  ---
FEDORA-EPEL-2022-d4d0379152 has been pushed to the Fedora EPEL 8 testing
repository.

You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-d4d0379152

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1934532
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2116587] perl-Bencode-1.502 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version|perl-Bencode-1.502-1.fc38   |perl-Bencode-1.502-1.fc38
   |perl-Bencode-1.502-1.fc36   |perl-Bencode-1.502-1.fc36
   |perl-Bencode-1.502-1.fc35   |perl-Bencode-1.502-1.fc35
   |perl-Bencode-1.502-1.el9|perl-Bencode-1.502-1.el9
   ||perl-Bencode-1.502-1.el8



--- Comment #15 from Fedora Update System  ---
FEDORA-EPEL-2022-d5d80462bb has been pushed to the Fedora EPEL 8 stable
repository.
If problem still persists, please make note of it in this bug report.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2116587
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2102597] Add perl-DBIx-Class to EPEL 9

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2102597
Bug 2102597 depends on bug 2102646, which changed state.

Bug 2102646 Summary: Add perl-DBIx-ContextualFetch to EPEL 9
https://bugzilla.redhat.com/show_bug.cgi?id=2102646

   What|Removed |Added

 Status|ON_QA   |CLOSED
 Resolution|--- |ERRATA




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2102597
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2112904] Add perl-Ima-DBI to EPEL 9

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2112904
Bug 2112904 depends on bug 2102646, which changed state.

Bug 2102646 Summary: Add perl-DBIx-ContextualFetch to EPEL 9
https://bugzilla.redhat.com/show_bug.cgi?id=2102646

   What|Removed |Added

 Status|ON_QA   |CLOSED
 Resolution|--- |ERRATA




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2112904
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2103389] Please branch and build perl-Monitoring-Plugin in epel9

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|ON_QA   |CLOSED
   Fixed In Version||perl-Monitoring-Plugin-0.40
   ||-13.el9
 Resolution|--- |ERRATA
Last Closed||2022-08-26 12:13:08



--- Comment #6 from Fedora Update System  ---
FEDORA-EPEL-2022-86abddef26 has been pushed to the Fedora EPEL 9 stable
repository.
If problem still persists, please make note of it in this bug report.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2103389
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2115573] Please build perl-Data-Entropy for EPEL 9

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|ON_QA   |CLOSED
   Fixed In Version||perl-Data-Entropy-0.007-20.
   ||el9
 Resolution|--- |ERRATA
Last Closed||2022-08-26 12:13:10



--- Comment #7 from Fedora Update System  ---
FEDORA-EPEL-2022-0d334fa354 has been pushed to the Fedora EPEL 9 stable
repository.
If problem still persists, please make note of it in this bug report.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2115573
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2102685] Add perl-Graph to EPEL 9

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version||perl-Graph-0.97.25-3.el9
 Status|ON_QA   |CLOSED
 Resolution|--- |ERRATA
Last Closed||2022-08-26 12:13:04



--- Comment #6 from Fedora Update System  ---
FEDORA-EPEL-2022-2099f4aa2c has been pushed to the Fedora EPEL 9 stable
repository.
If problem still persists, please make note of it in this bug report.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2102685
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2102659] Add perl-SQL-Translator to EPEL 9

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2102659
Bug 2102659 depends on bug 2102685, which changed state.

Bug 2102685 Summary: Add perl-Graph to EPEL 9
https://bugzilla.redhat.com/show_bug.cgi?id=2102685

   What|Removed |Added

 Status|ON_QA   |CLOSED
 Resolution|--- |ERRATA




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2102659
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2102646] Add perl-DBIx-ContextualFetch to EPEL 9

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version||perl-DBIx-ContextualFetch-1
   ||.03-46.el9
 Status|ON_QA   |CLOSED
 Resolution|--- |ERRATA
Last Closed||2022-08-26 12:12:59



--- Comment #5 from Fedora Update System  ---
FEDORA-EPEL-2022-2099f4aa2c has been pushed to the Fedora EPEL 9 stable
repository.
If problem still persists, please make note of it in this bug report.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2102646
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2102597] Add perl-DBIx-Class to EPEL 9

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2102597
Bug 2102597 depends on bug 2102659, which changed state.

Bug 2102659 Summary: Add perl-SQL-Translator to EPEL 9
https://bugzilla.redhat.com/show_bug.cgi?id=2102659

   What|Removed |Added

 Status|ON_QA   |CLOSED
 Resolution|--- |ERRATA




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2102597
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2102659] Add perl-SQL-Translator to EPEL 9

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version||perl-SQL-Translator-1.62-8.
   ||el9
 Status|ON_QA   |CLOSED
 Resolution|--- |ERRATA
Last Closed||2022-08-26 12:13:02



--- Comment #4 from Fedora Update System  ---
FEDORA-EPEL-2022-2099f4aa2c has been pushed to the Fedora EPEL 9 stable
repository.
If problem still persists, please make note of it in this bug report.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2102659
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: [Dev] Check out the Fedora Packager Dashboard!

[Major Hayden via devel]

On 8/25/22 03:32, Miro Hrončok wrote:
> this is just a reminder that there is a Fedora Packager Dashboard that
> you might not know about:
> 
> Go to https://packager-dashboard.fedoraproject.org/

I randomly discovered this application earlier this year and it saves me
so much time. I wish I had more constructive feedback, but this is all I
have for now:

Thank you. 

-- 
Major Hayden


OpenPGP_0x737051E0C1011FB1.asc
Description: OpenPGP public key


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

CPE Weekly Update - Week 34 2022

[Michal Konecny]

Hi everyone,

This is a weekly report from the CPE (Community Platform Engineering) Team.
The report could be found at https://communityblog.fedoraproject.org/
cpe-weekly-update---week-34-2022/.

If you want to receive weekly reports by emails in the future, please
subscribe to either https://communityblog.fedoraproject.org/ or
https://discussion.fedoraproject.org/c/news/commblog/61. We will stop
sending them in the future.

Regards,
CPE Team
___
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: Packages in repo not signed: fedora-cisco-openh264 repository

[Christopher Klooz]

On 26/08/2022 01:28, Kevin Fenzi wrote:

Everything should be back to working. Try a 'dnf --refresh...' or a
'dnf clean all'.
Yes, the packages are no longer in the update list. So the errors are 
gone for now. Thanks!


It's not fully clear yet some of the events. ;(

 The person who used to update this has moved to another group.
 The SOP (standard operating procedure) for doing this update was 
incorrect/out of date/wrong.
 Current update used the wrong process in the SOP and unsigned rpms were 
sent instead of signed ones.
 Something caused a zchunk error (the first one you saw, but perhaps this 
was just out of date repodata?)
 Something caused mirrormanager to not update for the new repodata.
 When updated, it started seeing the new unsigned rpms and gave an error 
about that.

I've pushed repodata that just points to the older h264 version thats signed 
(in f36/f37) and empty repodata (rawhide/f38).

In my testing everything is back to working.

I've submitted a PR to update the SOP.

Sorry for the trouble.

kevin

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

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

Fedora rawhide compose report: 20220826.n.0 changes

[Fedora Rawhide Report]

OLD: Fedora-Rawhide-20220825.n.0
NEW: Fedora-Rawhide-20220826.n.0

= SUMMARY =
Added images:0
Dropped images:  0
Added packages:  15
Dropped packages:2
Upgraded packages:   104
Downgraded packages: 22

Size of added packages:  412.83 MiB
Size of dropped packages:8.24 MiB
Size of upgraded packages:   2.85 GiB
Size of downgraded packages: 1.40 MiB

Size change of upgraded packages:   110.33 MiB
Size change of downgraded packages: -3.46 KiB

= ADDED IMAGES =

= DROPPED IMAGES =

= ADDED PACKAGES =
Package: 6tunnel-0.13-1.fc38
Summary: Tunnelling for application that don't speak IPv6
RPMs:6tunnel
Size:116.36 KiB

Package: arx-libertatis-1.2.1-1.fc38
Summary: Cross-platform, open source port of the Arx Fatalis RPG
RPMs:arx-libertatis arx-libertatis-devel
Size:9.49 MiB

Package: clifm-1.7-1.fc38
Summary: Shell-like, command line terminal file manager
RPMs:clifm
Size:1.33 MiB

Package: galera-26.4.11-2.module_f38+15203+2065794f
Summary: Synchronous multi-master wsrep provider (replication engine)
RPMs:galera
Size:4.37 MiB

Package: golang-github-zyedidia-clipper-0.1.0-1.fc38
Summary: Cross-platform clipboard access in Go
RPMs:golang-github-zyedidia-clipper-devel
Size:19.90 KiB

Package: mariadb-3:10.5.16-2.module_f38+15203+2065794f
Summary: A very fast and robust SQL database server
RPMs:mariadb mariadb-backup mariadb-common mariadb-connect-engine 
mariadb-cracklib-password-check mariadb-devel mariadb-embedded 
mariadb-embedded-devel mariadb-errmsg mariadb-gssapi-server 
mariadb-oqgraph-engine mariadb-pam mariadb-rocksdb-engine mariadb-s3-engine 
mariadb-server mariadb-server-galera mariadb-server-utils mariadb-sphinx-engine 
mariadb-test
Size:225.42 MiB

Package: pgaudit-1.4.0-3.module_f38+15278+5ad4785b
Summary: PostgreSQL Audit Extension
RPMs:pgaudit
Size:222.31 KiB

Package: postgres-decoderbufs-1.4.0-1.Final.module_f38+15278+5ad4785b
Summary: PostgreSQL Protocol Buffers logical decoder plugin
RPMs:postgres-decoderbufs postgres-decoderbufs-llvmjit
Size:243.78 KiB

Package: postgresql-12.11-3.module_f38+15278+5ad4785b
Summary: PostgreSQL client programs
RPMs:postgresql postgresql-contrib postgresql-docs postgresql-llvmjit 
postgresql-plperl postgresql-plpython postgresql-plpython3 postgresql-pltcl 
postgresql-server postgresql-server-devel postgresql-static postgresql-test 
postgresql-test-rpm-macros postgresql-upgrade postgresql-upgrade-devel
Size:142.09 MiB

Package: pt-astra-sans-fonts-1.002-1.fc38
Summary: Sans fonts that are metric analogs of Times New Roman
RPMs:pt-astra-sans-fonts
Size:187.94 KiB

Package: python-mediafile-0.9.0-1.fc38
Summary: Elegant audio file tagging in Python
RPMs:python3-mediafile
Size:59.75 KiB

Package: python-qpageview-0.6.2-2.fc38
Summary: Widget to display page-based documents for Qt5/PyQt5
RPMs:python-qpageview-doc python3-qpageview
Size:633.47 KiB

Package: subversion-1.14.2-5.module_f38+15272+edcc0b97
Summary: A Modern Concurrent Version Control System
RPMs:mod_dav_svn python3-subversion subversion subversion-devel 
subversion-gnome subversion-javahl subversion-kde subversion-libs 
subversion-perl subversion-ruby subversion-tools
Size:22.02 MiB

Package: varnish-6.0.10-1.module_f38+15275+c0711295
Summary: High-performance HTTP accelerator
RPMs:varnish varnish-devel varnish-docs
Size:6.35 MiB

Package: varnish-modules-0.15.0-12.module_f38+15275+c0711295
Summary: A collection of modules ("vmods") extending Varnish VCL
RPMs:varnish-modules
Size:326.98 KiB


= DROPPED PACKAGES =
Package: python-fastapi-0.78.0-5.fc37
Summary: FastAPI framework
RPMs:python3-fastapi python3-fastapi+all
Size:167.95 KiB

Package: toped-0.9.81-32.svn2211.fc37
Summary: VLSI IC Layout Editor
RPMs:toped toped-devel
Size:8.08 MiB


= UPGRADED PACKAGES =
Package:  3dprinter-udev-rules-0.3-1.fc38
Old package:  3dprinter-udev-rules-0.2.2-8.fc37
Summary:  Rules for udev to give regular users access to operate 3D printers
RPMs: 3dprinter-udev-rules
Size: 10.27 KiB
Size change:  -1.85 KiB
Changelog:
  * Thu Aug 25 2022 Miro Hron??ok  - 0.3-1
  - Update to 0.3
  - License changed to MIT-0


Package:  FAudio-22.08-2.fc38
Old package:  FAudio-22.08-1.fc38
Summary:  FNA is a reimplementation of the Microsoft XNA Game Studio 4.0 
Refresh libraries
RPMs: libFAudio libFAudio-devel mingw32-FAudio mingw64-FAudio
Size: 958.14 KiB
Size change:  -544.78 KiB
Changelog:
  * Thu Aug 25 2022 Michael Cronenworth  - 22.08-2
  - Include MinGW debuginfo packages


Package:  MUMPS-5.5.1-1.fc38
Old package:  MUMPS-5.5.0-2.fc37
Summary:  A MUltifrontal Massively Parallel sparse direct Solver
RPMs: MUMPS MUMPS-common MUMPS-devel MUMPS-examples MUMPS-mpich 
MUMPS-mpich-devel MUMPS-mpich-examples MUMPS-openmpi MUMPS-openmpi-devel 
MUMPS-openmpi-exam

Re: sqlcipher soname change in rawhide

[Fabio Valentini]

On Fri, Aug 26, 2022 at 3:12 AM Carl George  wrote:
>
> sqlcipher has been requested to be built in epel9 [0].  Rather than
> branching it from the current rawhide version, I plan to update
> rawhide to the latest upstream version first [1].  This involves an
> soname change from libsqlcipher-3.34.1.so.0 to
> libsqlcipher-3.39.2.so.0.  This will require six packages to be
> rebuilt.
>
> [root@f38-container:~]# repoquery --repo 
> rawhide-source,rawhide-modular-source \
> > --quiet --queryformat '%{name}' --archlist src --whatrequires 
> > sqlcipher-devel
> libgda
> python-peewee
> sqlitebrowser
> [root@f38-container:~]# repoquery --repo 
> rawhide-source,rawhide-modular-source \
> > --quiet --queryformat '%{name}' --archlist src --whatrequires 
> > 'pkgconfig(sqlcipher)'
> kmymoney
> rust-libsqlite3-sys
> skrooge

Please do not rebuild rust-libsqlite3-sys. It is a source-only package
that does not ship any compiled code.
All packages built from rust-libsqlite3-sys are noarch (i.e. they
can't - by definition - contain architecture-specific binaries).
Any built binaries that link against libsqlcipher are only used for
tests, but not shipped with built packages.

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

GTK 2 removal from RHEL 10+

[Tomáš Popela]

Hi everyone,

This is an early heads-up about GTK 2 removal from RHEL 10+ (the gtk2
package was marked as unwanted in ELN with
https://github.com/minimization/content-resolver-input/commit/b6d44e496f46bd2444e8e24dd3e9113b326817ac).
The toolkit served us gratefully, but it starts to show its age with
regards to modern technologies such as Wayland, HiDPI screens, HDR and
others.

In RHEL 10 the GTK 3 and GTK 4 will still continue to be available for
everyone to use.

Regards,

Tom Popela

-- 

Tomáš Popela

Desktop and Desktop Applications Subsystems Product Owner

Display Systems

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

Re: libpq-devel and postgresql-private-devel providing conflicting libpq.so symlink

[Stephan Bergmann]

filed  
"postgresql-private-devel conflicts with libpq-devel over 
pkgconfig(libpq), blocks rebuild of LibreOffice flatpak"

___
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: F37 proposal: Supplement of Server distributables by a KVM VM disk image (Self-Contained Change proposal)

[Zbigniew Jędrzejewski-Szmek]

Hi,

I tried to use the image, and I have a small suggestion:
please add links to where the resulting images can be found to the Change page.
W/o that it's entirely non-obvious where to look for it.

Zbyszek


On Thu, Jun 02, 2022 at 03:28:21PM -0400, Ben Cotton wrote:
> https://fedoraproject.org/wiki/Changes/Supplement-server-by-kvm-vm-image
> 
> This document represents a proposed Change. As part of the Changes
> process, proposals are publicly announced in order to receive
> community feedback. This proposal will only be implemented if approved
> by the Fedora Engineering Steering Committee.
> 
> == Summary ==
> Virtualization has long been a steadily growing use case of Fedora
> Server Edition, but it is still time consuming and tedious for the
> system administrator to create a Fedora Server VM. Supplementing the
> downloads by a KVM VM image remedies the deficiency.
> 
> == Owner ==
> * Name: [[User:pboy| Peter Boy on behalf of Server WG]]
> * Email: p...@uni-bremen.de
> 
> 
> == Detailed Description ==
> The creation of the VM disk image, uses the same kickstart files and
> installation groups as the standard full installation,  except of
> course for the hardware-specific items. The image is optimized for
> KVM.
___
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

[Bug 2051034] Removal of gethostbyname2 breaks Shorewall6

[bugzilla]

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

Michele Baldessari  changed:

   What|Removed |Added

 Resolution|--- |CURRENTRELEASE
 Status|MODIFIED|CLOSED
Last Closed||2022-08-26 08:34:33




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2051034
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Packages silently dropping approved changes

[Iñaki Ucar]

On Fri, 26 Aug 2022 at 00:44, Ralf Corsépius  wrote:
>
>
>
> Am 25.08.22 um 23:00 schrieb Iñaki Ucar:
> > On Thu, 25 Aug 2022 at 19:15, Iñaki Ucar  wrote:
> >>
> >> On Thu, 25 Aug 2022 at 18:34, Ralf Corsépius  wrote:
> >>>
> >>> Am 25.08.22 um 13:19 schrieb Iñaki Ucar:
> >>>
>  I assume their maintainers didn't do it on purpose, maybe it was
>  easier for a certain update, didn't have time to look into it and
>  weren't aware of the guideline. But this is very frustrating. Seeing
>  many hours of work just wiped out without any notice or explanation is
>  very frustrating.
> >>>
> >>> In my case (freefem++), it was actually was a mixture of all.
> >>>
> >>> To cut a long story short: This flexblas stuff doesn't "harmonize well"
> >>> with freefem++, rsp. more bluntly speaking, flexblas breaks freefem++.
> >>>
> >>> Because of this, when going after freefem++'s regressions, years after
> >>> the flexiblas changes had been introduced, I inadvertedly and
> >>> accidentally reverted the flexblas related changes, because these
> >>> apparently do not work out with freefem++.
> >>
> >> How exactly does flexiblas break freefem++? I see v4.10 was built just
> >> fine. Then v4.11 reverted to openblas. If it works with openblas, I
> >> see no reason to break with flexiblas, among other things because
> >> openblas is the default backend. Moreover, arpack, superlu,
> >> suitesparse and other BuildRequires link against flexiblas.
> >
> > In fact, freefem++ was one of the easiest packages to adapt: you just
> > set the library, and it does nothing fancy nor too-clever to try to
> > discover anything.
> Then you haven't looked into details (build.log rsp. config.status).

Could you please describe the issues?

> flexiblas causes freefem's configure script to produce bogus results.

If you are referring to this line

configure: -- NO ARPACK --  enable_download : no , wget: yes

then I have good news. I think we can agree that the configure script
is a mess. It just needed a simple fix to make that test successful,
namely, to substitute -llapack with -lflexiblas. Please take a look at
https://koji.fedoraproject.org/koji/taskinfo?taskID=91264332. I see no
differences in the list of "configure: ++ " that the script
produces

> Here's a simple patch [1] and a successful scratch
> > build [2], with all checks passing. Please let me know if I'm missing
> > anything, but otherwise, I'll open a PR.
> Please don't and also abstain from submitting pull requests.

I'm sorry, I'm trying to help here. But it's difficult if I don't know
the specific trouble you run into.

-- 
Iñaki Úcar
___
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

[Vít Ondruch]

Dne 25. 08. 22 v 16:38 Fabio Valentini napsal(a):

On Thu, Aug 25, 2022 at 4:34 PM Ankur Sinha  wrote:

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

As far as I understand, this only automatically adds packages that are
associated with the  "@rust-sig" group on dist-git to the "rust-sig"
group on koschei.
We still need to manually enable tracking for new packages, but
syncing group membership is automatic.



https://pagure.io/fedora-infra/ansible/blob/c2c063d22fe9a36b167fd27496aa1bd832ff1ca7/f/roles/openshift-apps/koschei/vars/production.yml#_47

https://github.com/fedora-infra/koschei/blob/master/bin/koschei-track-group

Checking these two ^^ I'd say that the whole group is automatically tracked.


Vít





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


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

Re: how to update rpms/vile?

[Thomas Dickey]

thanks - I'll use this information
___
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

[Bug 2115572] Please build perl-Number-Bytes-Human for EPEL 9

[bugzilla]

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



--- Comment #6 from Robert Scheck  ---
Feel free to follow up the "non-responsive maintainer policy". Personally, I
only care about the EPEL part of this package.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2115572
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue