Re: Schedule for Monday's FESCo Meeting (2024-02-12)

[Kevin Kofler via devel]

Kevin Fenzi wrote:
> On Tue, Feb 13, 2024 at 02:57:15AM +0100, Kevin Kofler via devel wrote:
>> Stephen Gallagher wrote:
>> > Meeting summary
>> 
>> Do we have the full log somewhere?
> 
> html:
> 
> https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-02-12/fesco.2024-02-12-19.30.log.html
> 
> plain text:
> 
> https://meetbot-raw.fedoraproject.org//meeting_matrix_fedoraproject-org/2024-02-12/fesco.2024-02-12-19.30.log.txt

Thanks!

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

Orphaned packages looking for new maintainers

[Maxwell G]

NOTE: This was not sent to individual maintainers, as @fedoraproject.org
aliases are currently broken
(https://pagure.io/fedora-infrastructure/issue/11768).
I will send another announcement once that's fixed.

---

Report started at 2024-02-13 01:07:53 UTC

The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life

Note: If you received this mail directly you (co)maintain one of the affected
packages or a package that depends on one. Please adopt the affected package or
retire your depending package to avoid broken dependencies, otherwise your
package will be retired when the affected package gets retired.

Request package ownership via the *Take* button in the left column on
https://src.fedoraproject.org/rpms/

Full report available at:
https://a.gtmx.me/orphans/orphans.txt
grep it for your FAS username and follow the dependency chain.

For human readable dependency chains,
see https://packager-dashboard.fedoraproject.org/
For all orphaned packages,
see https://packager-dashboard.fedoraproject.org/orphan

Package   (co)maintainers  Status Change

3proxy orphan  0 weeks ago  
R-presser  @r-maint-sig, orphan1 weeks ago  
applet-window-buttons  @kde-sig, orphan2 weeks ago  
atinoutorphan  0 weeks ago  
bismuth@kde-sig, orphan2 weeks ago  
callaudiod orphan  0 weeks ago  
drumstick0 orphan, yanqiyu 3 weeks ago  
elpa   @scitech_sig, orphan5 weeks ago  
gnome-translateorphan  2 weeks ago  
golang-github- @go-sig, ngompa, orphan 0 weeks ago  
googlecloudplatform-guest-  
logging 
golang-gocloud @go-sig, orphan 0 weeks ago  
golang-storj-uplink@go-sig, orphan 1 weeks ago  
google-compute-engine-guest-   ngompa, orphan  0 weeks ago  
configs 
google-disk-expand orphan  0 weeks ago  
google-guest-agent @go-sig, ngompa, orphan 0 weeks ago  
google-osconfig-agent  @go-sig, orphan 0 weeks ago  
kpipewire5 @kde-sig, orphan4 weeks ago  
ksysguard  @kde-sig, orphan1 weeks ago  
libmodulemd1   @copr-sig, orphan   1 weeks ago  
libtranslate   orphan  2 weeks ago  
lightlyorphan  2 weeks ago  
ocaml-newt orphan  1 weeks ago  
perl-PDF-Haru  orphan  0 weeks ago  
phosh-mobile-settings  orphan  0 weeks ago  
php-PHP-CSS-Parser orphan  5 weeks ago  
php-doctrine-persistence2  orphan  1 weeks ago  
php-doctrine-persistence3  orphan  1 weeks ago  
php-echonest-api   orphan  2 weeks ago  
php-endroid-qrcode orphan  1 weeks ago  
php-interfasys-lognormalizer   orphan  1 weeks ago  
php-ircmaxell-random-lib   orphan  1 weeks ago  
php-ircmaxell-security-lib orphan  1 weeks ago  
php-kukulich-fshl  orphan  1 weeks ago  
php-mikealmond-musicbrainz orphan  2 weeks ago  
php-nyholm-psr7orphan  1 weeks ago  
php-pear-MDB2-Schema   orphan  1 weeks ago  
php-phpdocumentor-reflection-  orphan  1 weeks ago  
docblock
php-symfony-monolog-bundle orphan  1 weeks ago  
php-true-punycode  orphan  1 weeks ago  
purple-mm-sms  orphan  0 weeks ago  

Re: Schedule for Monday's FESCo Meeting (2024-02-12)

[Kevin Fenzi]

On Tue, Feb 13, 2024 at 02:57:15AM +0100, Kevin Kofler via devel wrote:
> Stephen Gallagher wrote:
> > Meeting summary
> 
> Do we have the full log somewhere?

html:

https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-02-12/fesco.2024-02-12-19.30.log.html

plain text:

https://meetbot-raw.fedoraproject.org//meeting_matrix_fedoraproject-org/2024-02-12/fesco.2024-02-12-19.30.log.txt

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: Schedule for Monday's FESCo Meeting (2024-02-12)

[Kevin Kofler via devel]

Stephen Gallagher wrote:
> Meeting summary

Do we have the full log somewhere?

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

[EPEL-devel] Fedora EPEL 9 updates-testing report

[updates]

The following Fedora EPEL 9 Security updates need testing:
 Age  URL
   6  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-b17c8fc3fc   
engrampa-1.26.2-1.el9
   6  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-9a7708876e   
mbedtls-2.28.7-1.el9
   3  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-a7417a00b4   
python-asyncssh-2.13.2-4.el9
   3  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-e2bbd00d36   
libgit2-1.7.2-2.el9 libgit2_1.6-1.6.5-1.el9 python-pygit2-1.14.0-2.el9
   3  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-471565274b   
clamav-1.0.5-1.el9
   2  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-554deba0ce   
chromium-121.0.6167.160-1.el9
   0  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-2f82caee80   
libmodsecurity-3.0.12-1.el9


The following builds have been pushed to Fedora EPEL 9 updates-testing

composer-2.7.1-1.el9
ode-0.16.4-2.el9
php-pecl-ssh2-1.4.1-1.el9
syncthing-1.27.3-1.el9

Details about builds:



 composer-2.7.1-1.el9 (FEDORA-EPEL-2024-853cbc5eb4)
 Dependency Manager for PHP

Update Information:

Version 2.7.1 -  2024-02-09
Added several warnings when plugins are disabled to hint at common problems
people had with 2.7.0 (#11842)
Fixed diagnose auditing of Composer dependencies failing when running from the
phar
Version 2.7.0 - 2024-02-08
Security: Fixed code execution and possible privilege escalation via compromised
vendor dir contents (GHSA-7c6p-848j-wh5h / CVE-2024-24821)
Changed the default of the audit.abandoned config setting to fail, set it to
report or ignore if you do not want this, or set it via COMPOSER_AUDIT_ABANDONED
env var (#11643)
Added --minimal-changes (-m) flag to update/require/remove commands to perform
partial update with --with-dependencies while changing only what is absolutely
necessary in transitive dependencies (#11665)
Added --sort-by-age (-A) flag to outdated/show commands to allow sorting by and
displaying the release date (most outdated first) (#11762)
Added support for --self combined with --installed or --locked in show command,
to add the root package to the package list being output (#11785)
Added severity information to audit command output (#11702)
Added scripts-aliases top level key in composer.json to define aliases for
custom scripts you defined (#11666)
Added IPv4 fallback on connection timeout, as well as a COMPOSER_IPRESOLVE env
var to force IPv4 or IPv6, set it to 4 or 6 (#11791)
Added support for wildcards in outdated's --ignore arg (#11831)
Added support for bump command bumping * to >=current version (#11694)
Added detection of constraints that cannot possibly match anything to validate
command (#11829)
Added package source information to the output of install when running in very
verbose (-vv) mode (#11763)
Added audit of Composer's own bundled dependencies in diagnose command (#11761)
Added GitHub token expiration date to diagnose command output (#11688)
Added non-zero status code to why/why-not commands (#11796)
Added error when calling show --direct  with an indirect/transitive
dependency (#11728)
Added COMPOSER_FUND=0 env var to hide calls for funding (#11779)
Fixed bump command not bumping packages required with a v prefix (#11764)
Fixed automatic disabling of plugins when running non-interactive as root
Fixed update --lock not keeping the dist reference/url/checksum pinned (#11787)
Fixed require command crashing at the end if no lock file is present (#11814)
Fixed root aliases causing problems when auditing locked dependencies (#11771)
Fixed handling of versions with 4 components in require command (#11716)
Fixed compatibility issues with Symfony 7
Fixed composer.json remaining behind after a --dry-run of the require command
(#11747)
Fixed warnings being shown incorrectly under some circumstances (#11786, #11760,
#11803)

ChangeLog:

* Sat Feb 10 2024 Remi Collet  - 2.7.1-1
- update to 2.7.1




 ode-0.16.4-2.el9 (FEDORA-EPEL-2024-28163c5eaf)
 High performance library for simulating rigid body dynamics

Update Information:

Initial EL-9 build

ChangeLog:

* Fri Feb  2 2024 Gwyn Ciesla  - 0.16.4-2
- SPDX license tags
* Thu Feb  1 2024 Gwyn Ciesla  - 0.16.4-1
- 0.16.4
* Thu Jan 25 2024 Fedora Release Engineering  - 
0.16.3-4
- Rebuilt for https://fedoraproject.org/wiki/Fedora_40_Mass_Rebuild
* Sun Jan 21 2024 Fedora Release Engineering  - 
0.16.3-3
- Rebuilt for 

Re: Does ccache ever help with kernel mock build?

[Julian Sikorski]

Am 12.02.24 um 22:10 schrieb Miroslav Suchý:

Dne 12. 02. 24 v 19:29 Julian Sikorski napsal(a):

Hello,

has anyone successfully managed to get ccache to speed up kernel 
mockbuilds, be it SRPMS from kernel-ark or from dist-git? I gave it a 
brief shot but saw no difference, if anything the build was slower.
The machine I am building on has 32 GB RAM which is not quite enough 
to fit everything on a ramdisk, and the drive I am building to is an 
NVME SSD, "only" PCI Express 3.0. CPU is a Ryzen 5 5600x. A baseonly 
builds takes about 25 minutes, which is somewhat annoying when one has 
to bisect something.
If ccache can speed this up, how big does it need to be? I understand 
the default 4 GB is nowhere near enough but what would be needed to 
actually help? Thanks!


Just to be sure - did you configured Mock to use it?

   https://rpm-software-management.github.io/mock/Plugin-CCache

the build from build container cannot see host ccache, so Mock must 
specially configure it.


This is by default off, because in multi user environment you can easily 
poison the cache and affect different build. This should be enabled only 
on VM where you trust all users that can run Mock. E.g. your personal 
developer workstation.



I am building with:
--enable-plugin=ccache --plugin-option=ccache:max_cache_size='40G'
Building with cold cache took 29:29, building with hot cache 29:45, so 
there appears to be no benefit so far. 
/var/cache/mock/fedora-36-x86_64/ccache is 9,5G in size, suggesting that 
size is not the problem.
I am down to 21 commits to bisect after the current one, so changes to 
kernel source tree should be minimal at this point.

Do I need to install ccache on the host as well?

Best regards,
Julian
--
___
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: FYI: removal of bastion server in DNSBL spam.dnsbl.anonmails.de requested

[Kevin Fenzi]

On Mon, Feb 12, 2024 at 09:04:25AM -0500, Stephen Smoogen wrote:
> On Mon, 12 Feb 2024 at 06:12, Marius Schwarz  wrote:
> 
> > Hi,
> >
> > as die Infrastructure ML did not react ( or could not react ;) ), I
> > requested the removal at that antispam blacklist.
> >
> >
> I did not see any email to the infrastructure list about this so I am
> wondering if your email (and other emails) have gotten trashed? Did you
> open a ticket on this at https://pagure.io/fedora-infrastructure/ already?
> There is another email issue that was listed there earlier today but I
> don't know if they are related.

I didn't see any emails on this subject either but it sounds like it
got addressed somehow anyhow?

But yes, always open a ticket if you want something addressed... I try
and watch lists and such for issues, but I could easily miss something.

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: Does ccache ever help with kernel mock build?

[Miroslav Suchý]

Dne 12. 02. 24 v 19:29 Julian Sikorski napsal(a):

Hello,

has anyone successfully managed to get ccache to speed up kernel mockbuilds, be it SRPMS from kernel-ark or from 
dist-git? I gave it a brief shot but saw no difference, if anything the build was slower.
The machine I am building on has 32 GB RAM which is not quite enough to fit everything on a ramdisk, and the drive I 
am building to is an NVME SSD, "only" PCI Express 3.0. CPU is a Ryzen 5 5600x. A baseonly builds takes about 25 
minutes, which is somewhat annoying when one has to bisect something.
If ccache can speed this up, how big does it need to be? I understand the default 4 GB is nowhere near enough but what 
would be needed to actually help? Thanks!


Just to be sure - did you configured Mock to use it?

  https://rpm-software-management.github.io/mock/Plugin-CCache

the build from build container cannot see host ccache, so Mock must specially 
configure it.

This is by default off, because in multi user environment you can easily poison the cache and affect different build. 
This should be enabled only on VM where you trust all users that can run Mock. E.g. your personal developer workstation.


--

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

Re: Schedule for Monday's FESCo Meeting (2024-02-12)

[Stephen Gallagher]

=
# #meeting:fedoraproject.org: fesco
=

Meeting started by @sgallagh:fedora.im at 2024-02-12 19:30:38



Meeting summary
---
* TOPIC: Init Process (@sgallagh:fedora.im, 19:32:09)
* TOPIC: #3165 Requesting FESCo assistance with issue about plasma-x11
(@sgallagh:fedora.im, 19:37:28)
* AGREED: KDE packages which reintroduce support for X11 are
allowed in the main Fedora repositories, however they may not be
included by default on any release-blocking deliverable (ISO, image,
etc.). The KDE SIG should provide a notice before major changes, but
is not responsible for ensuring that these packages adapt. Upgrades
from F38 and F39 will be automatically migrated to Wayland. (+5, 0,
-1) (@sgallagh:fedora.im, 20:33:45)
* TOPIC: Next Week's Chair (@sgallagh:fedora.im, 20:37:40)
* ACTION: zbyszek to chair the 2024-02-19 meeting
(@sgallagh:fedora.im, 20:38:36)
* TOPIC: Open Floor (@sgallagh:fedora.im, 20:38:41)

Meeting ended at 2024-02-12 20:42:10

Action items

* zbyszek to chair the 2024-02-19 meeting

People Present (lines said)
---
* @conan_kudo:matrix.org (80)
* @sgallagh:fedora.im (57)
* @nirik:matrix.scrye.com (30)
* @salimma:fedora.im (23)
* @zbyszek:fedora.im (15)
* @marcdeop:matrix.org (14)
* @jistone:fedora.im (14)
* @farchord:matrix.org (10)
* @tstellar:fedora.im (10)
* @zodbot:fedora.im (10)
* @stevenfalco:fedora.im (5)
* @mhayden:fedora.im (3)
* @nhanlon:beeper.com (2)
* @solopasha:matrix.org (2)
* @humaton:fedora.im (2)
* @meetbot:fedora.im (2)
* @aleasto:matrix.org (1)
* @davide:cavalca.name (1)
* @jonathanspw:fedora.im (1)
--
___
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

webrtc-audio-processing

[Gwyn Ciesla via devel]

The upcoming releases of gstreamer1 will require webrtc-audio-processing >= 
1.0, and the package currently is at 0.3.

There are 4 consumers:

dino
gstreamer1-plugins-bad-free
pipewire
pulseaudio

I've set up webrtc-audio-processing0.3, and updated webrtc-audio-processing to 
1.3. I've updated BuildRequires on the consumers to use pkgconfig, because the 
library name for 1.3 has -1 appended. Future rebuilds and current binaries will 
continue to work, and we can retire 0.3 after all 4 have migrated.

-- 
Gwyn Ciesla
she/her/hers
 
in your fear, seek only peace 
in your fear, seek only love
-d. bowie


Sent with Proton Mail secure email.

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

Re: cloud-init switching to udhcpc

[Major Hayden]

On Tue, Jan 30, 2024, at 11:11, Tomasz Torcz wrote:
> On Tue, Jan 30, 2024 at 10:58:19AM -0600, Major Hayden wrote:
>   I'm curious, why not systemd-networkd? It's mentioned once in
> the bug, but there's not explanation about the choice later.

That might be possible, but upstream cloud-init only support dhclient, udhcpc, 
and dhcpcd upstream currently. That support would need to be added in 
cloud-init.

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

Does ccache ever help with kernel mock build?

[Julian Sikorski]

Hello,

has anyone successfully managed to get ccache to speed up kernel 
mockbuilds, be it SRPMS from kernel-ark or from dist-git? I gave it a 
brief shot but saw no difference, if anything the build was slower.
The machine I am building on has 32 GB RAM which is not quite enough to 
fit everything on a ramdisk, and the drive I am building to is an NVME 
SSD, "only" PCI Express 3.0. CPU is a Ryzen 5 5600x. A baseonly builds 
takes about 25 minutes, which is somewhat annoying when one has to 
bisect something.
If ccache can speed this up, how big does it need to be? I understand 
the default 4 GB is nowhere near enough but what would be needed to 
actually help? Thanks!


Best regards,
Julian
--
___
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

do we need CONFIG_UPROBES=y in our kernels?

[Marius Schwarz]

Hi,

I excuse myself if this has been already discussed, bastion ML server 
was blacklisted (has been removed btw).


Short summary(for details use the source link):

In a german developer blog article was the topic raised, that with 
uprobes enabled, userland apps can i.e. circumvent tls security(and 
other protections),
by telling the kernel to probe the function calls with the uprobes api. 
As this enables i.e. the hosting system of a vm or container, to track 
activity inside the container, trust is lost i.e. from customer to 
hoster. To be fair, you need to be root on the host to do this, but as 
it "wasn't possible before", and it is "now" ( out in a greater public 
), it tends to create trust issues, just for being there*.


As this only works with uprobes enabled and has no use case besides a 
developer debugging apps, the question is:


Do we need this for all others out there enabled by default?

If noone can name an app/lib that needs this outside of the C* 
development process, a change proposal would be wise. maybe adding a 
kernel boot argument switch?


Source: http://blog.fefe.de/?ts=9b3a23b2

*) You may not have a clue, what security auditors tell you about "a 
vulnerability & it's just there, but inexploitable". I had a case 2 
weeks ago, about a missing patch for the ssh-agent CVE vulnerability in 
fedora's openssh. Trust me, it will create trouble the more the topic is 
discussed in the pubic.



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

Re: FAS issue (was Re: Another mass rebuild blocker: glibc qsort regression)

[Tomasz Torcz]

On Tue, Jan 23, 2024 at 09:04:53AM -0600, Chris Adams wrote:
> Once upon a time, Richard W.M. Jones  said:
> > The authentication issue being this one:
> > 
> > https://pagure.io/fedora-infrastructure/issue/11733
> 
> I'd be interested in an after report on this one... as someone who has
> managed FreeIPA, I'd like to know how this happened (so I can file away
> how to NOT do the same thing in my own setups).

Form the comment
(https://pagure.io/fedora-infrastructure/issue/11733#comment-892793)
it seems that new requirement of users having SID caught Fedora FreeIPA
of guard.
  There's `ipa config-mod` invocation to add SIDs to users, but you must
make sure you have ID Ranges defined covering all your UIDs and GIDs.


-- 
Tomasz TorczOnly gods can safely risk perfection,
to...@pipebreaker.pl it's a dangerous thing for a man.  — Alia
--
___
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: SoPlex and SCIP review swaps

[Jerry James]

On Wed, Dec 6, 2023 at 3:10 PM Jerry James  wrote:
> I need reviews for the following new packages.  I am willing to swap reviews.
> - asl: https://bugzilla.redhat.com/show_bug.cgi?id=2253354
> - ccluster: https://bugzilla.redhat.com/show_bug.cgi?id=2253355
> - lusol: https://bugzilla.redhat.com/show_bug.cgi?id=2253356
> - pdqsort: https://bugzilla.redhat.com/show_bug.cgi?id=2253357
> - zimpl: https://bugzilla.redhat.com/show_bug.cgi?id=2253358
> - zstr: https://bugzilla.redhat.com/show_bug.cgi?id=2253359
> - papilo: https://bugzilla.redhat.com/show_bug.cgi?id=2253360
> - soplex: https://bugzilla.redhat.com/show_bug.cgi?id=2253361
> - scip: https://bugzilla.redhat.com/show_bug.cgi?id=2253362
> - coin-or-HiGHS: https://bugzilla.redhat.com/show_bug.cgi?id=2253363
> - spasm: https://bugzilla.redhat.com/show_bug.cgi?id=2253364

Just a few package reviews to go!  This is what remains to be done:

- papilo: https://bugzilla.redhat.com/show_bug.cgi?id=2253360
- soplex: https://bugzilla.redhat.com/show_bug.cgi?id=2253361
- scip: https://bugzilla.redhat.com/show_bug.cgi?id=2253362
- coin-or-HiGHS: https://bugzilla.redhat.com/show_bug.cgi?id=2253363

These will need to be reviewed with respect to the [COPR mentioned
above](https://copr.fedorainfracloud.org/coprs/jjames/SCIP/), since I
can't build asl in Rawhide without breaking the existing mp package,
so the rest all has to be done at once in a side tag.

Let me know what I can review for you in exchange for the above reviews.
-- 
Jerry James
http://www.jamezone.org/
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: cloud-init switching to udhcpc

[Tomasz Torcz]

On Tue, Jan 30, 2024 at 10:58:19AM -0600, Major Hayden wrote:
> Hey there,
> 
> For those of you who use Fedora often on public cloud providers where
> cloud-init handles the initial configuration, there's a change coming for
> the very early DHCP request during the boot. ☁️
> 
> [0] https://bugzilla.redhat.com/show_bug.cgi?id=2247055

  I'm curious, why not systemd-networkd? It's mentioned once in
the bug, but there's not explanation about the choice later.

-- 
Tomasz Torcz“Funeral in the morning, IDE hacking
to...@pipebreaker.pl in the afternoon and evening.” - Alan Cox
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

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

[Stephen Gallagher]

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

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

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

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

= Discussed and Voted in the Ticket =

#3164 Change: IoT Simplified Provisioning
https://pagure.io/fesco/issue/3164
APPROVED (+6, 0, 0)

#3163 Change: ibus 1.5.30
https://pagure.io/fesco/issue/3163
APPROVED (+6, 0, 0)

#3162 Change: ibus-anthy 1.5.16
https://pagure.io/fesco/issue/3162
APPROVED (+6, 0, 0)

#3161 Change: Build Fedora IoT Using rpm-ostree unified core
https://pagure.io/fesco/issue/3162
APPROVED (+6, 0, 0)

#3160 Change: Fedora IoT Bootable Container
https://pagure.io/fesco/issue/3160
APPROVED (+5, 0, 0)

#3159 Change: Deprecate_ntlm_in_cyrus_sasl
https://pagure.io/fesco/issue/3159
APPROVED (+6, 0, 0)

#3156 Change: Replace iotop with iotop-c
https://pagure.io/fesco/issue/3156
APPROVED (+6, 0, 0)

#3155 Change: ROCm 6 Release
https://pagure.io/fesco/issue/3155
APPROVED (+6, 0, 0)

#3154 Change: PyTorch Release
https://pagure.io/fesco/issue/3154
APPROVED (+6, 0, 0)

Change: Default Bpfman as eBPF manager
https://pagure.io/fesco/issue/3153
APPROVED (+6, 0, 0)


= Followups =

#3165 Requesting FESCo assistance with issue about plasma-x11
https://pagure.io/fesco/issue/3165

= New business =

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

= Open Floor =

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

If you would like to add something to this agenda, you can
reply to this e-mail, file a new issue at
https://pagure.io/fesco, e-mail me directly, or bring it
up at the end of the meeting, during the open floor topic. Note
that added topics may be deferred until the following meeting.
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Fedora Linux 40 Mass Branching will be held Tomorrow

[Samyak Jain]

Hi All,

Fedora Linux 40 is going to be branched tomorrow as per
the experience of the previous release we are going to disable the new koji
builds for the duration of this event. For more on this please refer to the
past discussion[1]

All builds that will be running at that time for the rawhide will be
canceled and can be resubmitted by maintainers after the branching.

All rawhide updates that are pending for rawhide will be unpushed.

Once Fedora Linux 40 is branched we will reenable builds in Koji with
a notification to this list. For any queries, we are on
#releng:fedoraproject.org
and Fedora Mass Branching Release Tracker[2].

Samyak Jain
Fedora Release Engineering

[1] 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/GWY4TIDIP65HA2V33F2ROU2MJLKMRZ7E/#GWY4TIDIP65HA2V33F2ROU2MJLKMRZ7E
[2] https://pagure.io/releng/issue/11939
--
___
devel-announce mailing list -- devel-annou...@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel-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

Fedora Linux 40 Mass Branching will be held Tomorrow

[Samyak Jain]

Hi All,

Fedora Linux 40 is going to be branched tomorrow as per
the experience of the previous release we are going to disable the new koji
builds for the duration of this event. For more on this please refer to the
past discussion[1]

All builds that will be running at that time for the rawhide will be
canceled and can be resubmitted by maintainers after the branching.

All rawhide updates that are pending for rawhide will be unpushed.

Once Fedora Linux 40 is branched we will reenable builds in Koji with
a notification to this list. For any queries, we are on
#releng:fedoraproject.org
and Fedora Mass Branching Release Tracker[2].

Samyak Jain
Fedora Release Engineering

[1] 
https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org/thread/GWY4TIDIP65HA2V33F2ROU2MJLKMRZ7E/#GWY4TIDIP65HA2V33F2ROU2MJLKMRZ7E
[2] https://pagure.io/releng/issue/11939
--
___
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel-announce@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

List of long term FTBFS packages to be retired in February

[Miro Hrončok]

Dear maintainers.

Based on the current fail to build from source policy, the following packages
should be retired from Fedora 40 approximately one week before branching.

5 weekly reminders are required, hence the retirement will happen
approximately in 3 weeks, i.e. around 2024-02-28.
Since this is unfortunately after the branching,
packages will be retired on rawhide and f40.

I apologize for starting this process a bit later than required again.
Unfortunately, I had other work obligations.
Volunteers to take over this are always welcome.

Policy: 
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/


The packages in rawhide were not successfully built at least since Fedora 37.

This report is based on dist tags.

Packages collected via:
https://github.com/hroncok/fedora-report-ftbfs-retirements/blob/master/ftbfs-retirements.ipynb

If you see a package that was built, please let me know.
If you see a package that should be exempted from the process,
please let me know and we can work together to get a FESCo approval for that.

If you see a package that can be rebuilt, please do so.

Package  (co)maintainers

calendar dcantrell, egoode
erlang-jose bowlofeggs, erlang-maint-sig, jcline, peter
ghdl sailer
git-secrets  keesdejong
golang-github-acme-lego  eclipseo, go-sig
golang-github-gatherstars-com-jwzeclipseo, go-sig
golang-github-genuinetools-pkg   eclipseo, go-sig
golang-github-gobs-prettyeclipseo, go-sig
golang-github-jhillyerd-enmime   eclipseo, go-sig
golang-github-pierrre-compareeclipseo, go-sig
golang-github-smartystreets-goconvey alexsaezm, go-sig, jchaloup
golang-gopkg-square-jose-2   alexsaezm, go-sig
golang-gvisoreclipseo, elmarco, go-sig
golang-opentelemetry-otel-0.20   alexsaezm, go-sig
golang-sigs-k8s-kustomizedcavalca, go-sig
golang-vitesseclipseo, go-sig
infinipath-psm   honli
j4-dmenu-desktop ibotty
jackson-dataformats-binary   mbooth
jackson-dataformats-text mbooth
java-1.8.0-openjdk-aarch32   akasko, jvanek
jreenrdieter
libdeltacloudclalance
mingw-clucenegreghellings
mingw-speexdsp   janisozaur
nbd-runner   xiubli
nodejs-generic-pool  patches, piotrp
ofononjha, thunderbirdtr
pesign-test-app  javierm, nfrayer, pjones, rharwood
pthsem   ixs
rust-drg jbtrystram, rust-sig

The following packages require above mentioned packages:
Depending on: erlang-jose (1)
erlang-p1_acme (maintained by: bowlofeggs, erlang-maint-sig, peter)
erlang-p1_acme-1.0.8-9.fc40.noarch requires erlang-jose
erlang-p1_acme-1.0.8-9.fc40.src requires erlang-jose

Depending on: golang-github-gatherstars-com-jwz (1)
aerc (maintained by: eclipseo, go-sig)
aerc-0.15.2-2.fc39.src requires 
golang(github.com/gatherstars-com/jwz)

Depending on: golang-github-genuinetools-pkg (1)
reg (maintained by: go-sig, infra-sig, mattia)
reg-0.16.1-15.fc40.src requires 
golang(github.com/genuinetools/pkg/cli)

Depending on: golang-github-gobs-pretty (2)
golang-github-vinyldns (maintained by: eclipseo, go-sig)
		golang-github-vinyldns-0.9.13-1.fc40.2.src requires 
golang(github.com/gobs/pretty)


golang-github-acme-lego (maintained by: eclipseo, go-sig)
		golang-github-acme-lego-4.4.0-8.fc37.src requires 
golang(github.com/vinyldns/go-vinyldns/vinyldns)
		golang-github-acme-lego-devel-4.4.0-8.fc37.noarch requires 
golang(github.com/vinyldns/go-vinyldns/vinyldns)


Depending on: golang-github-jhillyerd-enmime (2)
golang-github-gatherstars-com-jwz (maintained by: eclipseo, go-sig)
		golang-github-gatherstars-com-jwz-1.3.0-1.fc37.src requires 
golang(github.com/jhillyerd/enmime)


aerc (maintained by: eclipseo, go-sig)
aerc-0.15.2-2.fc39.src requires 
golang(github.com/gatherstars-com/jwz)

Depending on: golang-github-pierrre-compare (1)
golang-github-pierrre-geohash (maintained by: eclipseo, go-sig)
		golang-github-pierrre-geohash-1.0.0-9.fc40.src requires 
golang(github.com/pierrre/compare)


Depending on: golang-github-smartystreets-goconvey (23)
golang-github-afex-hystrix (maintained by: alexsaezm, go-sig)
		golang-github-afex-hystrix-0-0.14.20190622gitfa1af6a.fc40.src requires 
golang(github.com/smartystreets/goconvey/convey)


golang-github-cucumber-godog (maintained by: eclipseo, go-sig)
		

Re: List of long term FTBFS packages to be retired in February

[Mikel Olasagasti]

Hau idatzi du Miro Hrončok (mhron...@redhat.com) erabiltzaileak (2024
ots. 3(a), lr. (18:18)):
>
>
>  Package  (co)maintainers
> 
> golang-github-gatherstars-com-jwz   eclipseo, go-sig
> golang-github-jhillyerd-enmime  eclipseo, go-sig
> golang-gopkg-square-jose-2  alexsaezm, go-sig
> golang-opentelemetry-otel-0.20  alexsaezm, go-sig

Fixed these.

> golang-github-pierrre-compare   eclipseo, go-sig

Obsoleted by updating golang-github-pierrre-geohash

Mikel
--
___
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: List of long term FTBFS packages to be retired in February

[David Cantrell]

On 2/3/24 12:17, Miro Hrončok wrote:

Dear maintainers.

Based on the current fail to build from source policy, the following 
packages

should be retired from Fedora 40 approximately one week before branching.

5 weekly reminders are required, hence the retirement will happen
approximately in 4 weeks, i.e. around 2024-02-28.
Since this is unfortunately after the branching,
packages will be retired on rawhide and f40.

I apologize for starting this process a bit later than required again.
Unfortunately, I had other work obligations.
Volunteers to take over this are always welcome.

Policy: 
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/


The packages in rawhide were not successfully built at least since 
Fedora 37.


This report is based on dist tags.

Packages collected via:
https://github.com/hroncok/fedora-report-ftbfs-retirements/blob/master/ftbfs-retirements.ipynb

If you see a package that was built, please let me know.
If you see a package that should be exempted from the process,
please let me know and we can work together to get a FESCo approval for 
that.


If you see a package that can be rebuilt, please do so.

     Package  (co)maintainers

calendar    dcantrell, egoode


Fixed calendar.

Thanks,

--
David Cantrell 
Red Hat, Inc. | Boston, MA | EST5EDT
--
___
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: x86-64 -mtls-dialect=gnu2 change needs to be postponed

[Florian Weimer]

* Stephen Smoogen:

> On Sun, 11 Feb 2024 at 09:35, Florian Weimer  wrote:
>
>  We've hit an ABI ambiguity/bug:
>
>gcc: -mtls-dialect=gnu2 produces wrong code on x86-64
>
>
> Was this set for the Fedora 40 mass rebuild or something that was put
> in later? If it was put into the mass rebuild, what problems would it
> cause currently?

I couldn't get the testing done in time for the mass rebuild, so it
wasn't included.  It's fully interoperable, so an incremental transition
is okay (once we settled the ABI issue).

Thanks,
Florian
--
___
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: Koji: virtual memory exhausted: Cannot allocate memory

[W. Michael Petullo]

>> Building the current version of my opengrm-ngram package on Koji fails
>> with the error "virtual memory exhausted: Cannot allocate memory"
>> as indicated below. This happens only for i686; all of the other
>> architectures build. Is this the fault of my package, or did something
>> change at https://koji.fedoraproject.org?
 
> the package (and its build enviroment) has grown. It fails because
> 32-bit system means max 4GB of address space for a process and ld runs
> as a single process, so it's not uncommon to use all memory for large
> C++ projects.

Thank you, Dan, for the quick response!

It had not occurred to me that the build might be hitting the
architectural limit, rather than some lower limit the build system placed
on the VM. I decided to disable the i686 build.

-- 
Mike

:wq
--
___
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: 20240212.n.0 changes

[Fedora Rawhide Report]

OLD: Fedora-Rawhide-20240211.n.0
NEW: Fedora-Rawhide-20240212.n.0

= SUMMARY =
Added images:4
Dropped images:  2
Added packages:  1
Dropped packages:2
Upgraded packages:   287
Downgraded packages: 0

Size of added packages:  2.96 MiB
Size of dropped packages:51.85 KiB
Size of upgraded packages:   4.75 GiB
Size of downgraded packages: 0 B

Size change of upgraded packages:   3.48 MiB
Size change of downgraded packages: 0 B

= ADDED IMAGES =
Image: Kinoite dvd-ostree aarch64
Path: Kinoite/aarch64/iso/Fedora-Kinoite-ostree-aarch64-Rawhide-20240212.n.0.iso
Image: Silverblue dvd-ostree aarch64
Path: 
Silverblue/aarch64/iso/Fedora-Silverblue-ostree-aarch64-Rawhide-20240212.n.0.iso
Image: Onyx dvd-ostree x86_64
Path: Onyx/x86_64/iso/Fedora-Onyx-ostree-x86_64-Rawhide-20240212.n.0.iso
Image: Kinoite dvd-ostree x86_64
Path: Kinoite/x86_64/iso/Fedora-Kinoite-ostree-x86_64-Rawhide-20240212.n.0.iso

= DROPPED IMAGES =
Image: Silverblue dvd-ostree x86_64
Path: 
Silverblue/x86_64/iso/Fedora-Silverblue-ostree-x86_64-Rawhide-20240211.n.0.iso
Image: Server raw-xz aarch64
Path: Server/aarch64/images/Fedora-Server-Rawhide-20240211.n.0.aarch64.raw.xz

= ADDED PACKAGES =
Package: dante-1.4.3-1.fc40
Summary: A free SOCKS v4/v5 client implementation
RPMs:dante dante-devel dante-server
Size:2.96 MiB


= DROPPED PACKAGES =
Package: python-compressed-rtf-1.0.6-4.fc40
Summary: Compressed Rich Text Format (RTF) (de-)compression
RPMs:python3-compressed-rtf
Size:20.81 KiB

Package: python-red-black-tree-mod-1.21-3.fc40
Summary: Flexible python implementation of red black trees
RPMs:python3-red-black-tree-mod
Size:31.04 KiB


= UPGRADED PACKAGES =
Package:  OliveTin-2022.11.14-8.fc40
Old package:  OliveTin-2022.11.14-7.fc40
Summary:  Give safe and simple access to predefined shell commands from a 
web interface
RPMs: OliveTin golang-github-olivetin-devel
Size: 16.54 MiB
Size change:  305.50 KiB
Changelog:
  * Sun Feb 11 2024 Maxwell G  - 2022.11.14-8
  - Rebuild for golang 1.22.0


Package:  act-1.6.0-17.fc40
Old package:  act-1.6.0-16.fc40
Summary:  Automatic Component Toolkit
RPMs: act
Size: 4.22 MiB
Size change:  872 B
Changelog:
  * Sun Feb 11 2024 Maxwell G  - 1.6.0-17
  - Rebuild for golang 1.22.0


Package:  age-1.1.1-5.fc40
Old package:  age-1.1.1-4.fc40
Summary:  Simple, modern and secure encryption tool
RPMs: age golang-filippo-age-devel
Size: 6.08 MiB
Size change:  148.58 KiB
Changelog:
  * Sun Feb 11 2024 Maxwell G  - 1.1.1-5
  - Rebuild for golang 1.22.0


Package:  apache-cloudstack-cloudmonkey-6.2.0-10.fc40
Old package:  apache-cloudstack-cloudmonkey-6.2.0-9.fc40
Summary:  Apache Cloudstack Cloudmonkey
RPMs: apache-cloudstack-cloudmonkey 
golang-github-apache-cloudstack-cloudmonkey-devel
Size: 9.13 MiB
Size change:  201.78 KiB
Changelog:
  * Sun Feb 11 2024 Maxwell G  - 6.2.0-10
  - Rebuild for golang 1.22.0


Package:  aquatone-1.7.0-14.fc40
Old package:  aquatone-1.7.0-13.fc40
Summary:  Tool for Domain Flyovers
RPMs: aquatone golang-github-michenriksen-aquatone-devel
Size: 11.27 MiB
Size change:  211.83 KiB
Changelog:
  * Sun Feb 11 2024 Maxwell G  - 1.7.0-14
  - Rebuild for golang 1.22.0


Package:  aron-0-0.13.20200626git7eade58.fc40
Old package:  aron-0-0.12.20200626git7eade58.fc40
Summary:  Tool to find hidden GET & POST parameters
RPMs: aron golang-github-m4ll0k-aron-devel
Size: 7.04 MiB
Size change:  163.69 KiB
Changelog:
  * Sun Feb 11 2024 Maxwell G  - 0-0.13
  - Rebuild for golang 1.22.0


Package:  asciigraph-0.5.6-5.fc40
Old package:  asciigraph-0.5.6-4.fc40
Summary:  Makes lightweight ASCII line graphs
RPMs: asciigraph golang-github-guptarohit-asciigraph-devel
Size: 2.47 MiB
Size change:  88.71 KiB
Changelog:
  * Sun Feb 11 2024 Maxwell G  - 0.5.6-5
  - Rebuild for golang 1.22.0


Package:  asnip-0-0.13.20200618git44ba98b.fc40
Old package:  asnip-0-0.12.20200618git44ba98b.fc40
Summary:  ASN detail retriever
RPMs: asnip golang-github-harleo-asnip-devel
Size: 6.93 MiB
Size change:  163.24 KiB
Changelog:
  * Sun Feb 11 2024 Maxwell G  - 0-0.13
  - Rebuild for golang 1.22.0


Package:  asnmap-1.0.6-4.fc40
Old package:  asnmap-1.0.6-3.fc40
Summary:  Go CLI and Library for quickly mapping organization network 
ranges using ASN information
RPMs: asnmap golang-github-projectdiscovery-asnmap-devel
Size: 22.98 MiB
Size change:  83.51 KiB
Changelog:
  * Sun Feb 11 2024 Maxwell G  - 1.0.6-4
  - Rebuild for golang 1.22.0


Package:  assetfinder-0.1.0-13.fc40
Old package:  assetfinder-0.1.0-12.fc40
Summary:  Find domains and subdomains related to a given domain
RPMs: assetfinder golang-github-tomnomnom-assetfinder-devel
Size: 7.26 MiB
Size change:  193.64 KiB
Changelog:
  * Sun Fe

Re: FYI: removal of bastion server in DNSBL spam.dnsbl.anonmails.de requested

[Stephen Smoogen]

On Mon, 12 Feb 2024 at 06:12, Marius Schwarz  wrote:

> Hi,
>
> as die Infrastructure ML did not react ( or could not react ;) ), I
> requested the removal at that antispam blacklist.
>
>
I did not see any email to the infrastructure list about this so I am
wondering if your email (and other emails) have gotten trashed? Did you
open a ticket on this at https://pagure.io/fedora-infrastructure/ already?
There is another email issue that was listed there earlier today but I
don't know if they are related.



> 2024-02-11 05:20:16 H=bastion-iad01.fedoraproject.org
> (bastion.fedoraproject.org) [38.145.60.11]
> X=TLS1.3:TLS_AES_256_GCM_SHA384:256 CV=no
> F= rejected RCPT
> : found in spam.dnsbl.anonmails.de
>
> I hope it gets removed soon.
>
> best regards,
> Marius Schwarz
> --
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>


-- 
Stephen Smoogen, Red Hat Automotive
Let us be kind to one another, for most of us are fighting a hard battle.
-- Ian MacClaren
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: x86-64 -mtls-dialect=gnu2 change needs to be postponed

[Stephen Smoogen]

On Sun, 11 Feb 2024 at 09:35, Florian Weimer  wrote:

> We've hit an ABI ambiguity/bug:
>
>   gcc: -mtls-dialect=gnu2 produces wrong code on x86-64
>   
>
>
Was this set for the Fedora 40 mass rebuild or something that was put in
later? If it was put into the mass rebuild, what problems would it cause
currently?



> Apart from that, support in the GNU toolchain seems to be quite good.
> In particular, GDB handled the situation in the polymake crash quite
> well (reporting TLS data as uninitialized for the thread before the
> critical call, and producing the correct address for the variable
> afterwards).
>
> Thanks,
> Florian
> --
> ___
> 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
>


-- 
Stephen Smoogen, Red Hat Automotive
Let us be kind to one another, for most of us are fighting a hard battle.
-- Ian MacClaren
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Bisecting an older kernel

[Julian Sikorski]

Am 12.02.24 um 10:03 schrieb Michael J Gruber:

Am So., 11. Feb. 2024 um 23:14 Uhr schrieb Julian Sikorski :


Hello,

I am trying to bisect an issue which appears to have regressed between
5.18 final and 5.19-rc2. This is somewhat challenging as most of the
kernels are since gone from koji, and the ark os-build branch seems to
have been rebased after kernel 6.7 release, meaning that the required
commits to the redhat folder are not in sync with the commits to the
kernel itself.


I'm not sure I'm following this completely - are you saying that (part
of) the old kernel sources are not there (in git) any more because a
branch got rebased?


Well the commits are there in the os-build branch, but they got rebased 
on top of 6.7. This means that they are no longer in sync with upstream 
kernel commits from the 5.19-rc0 timeframe.
In the meantime I was able to learn that the correct order is still 
present in the tags:


$ git bisect good kernel-5.19.0-0.rc0.fdaf9a5840ac.1
$ git bisect bad kernel-5.19.0-0.rc0.babf0bb978e3.3

I was able to recreate an "os-build-5.19" branch and am finally building 
a kernel now.





I tried cherry-picking them on top, but it does not apply
cleanly either:

$ git clone -b os-build g...@gitlab.com:cki-project/kernel-ark.git
$ git bisect start
$ git bisect bad v5.19-rc2
$ git bisect good v5.18
$ git checkout 2518f226c60d8e04d18ba4295500a5b0b8ac7659
$ git cherry-pick
0dd3ee31125508cd67f7e7172247f05b7fd1753a..6d8a7e484dc667c1094fc90452dee6af30d509f6

Is there a way simpler than trying to fix the cherry-pick conflicts
every single time?


`rerere` can be really helpful for something like this.


I will have a look if I get stuck again, thanks!


I guess you've checked already whether the problem you're trying to
solve depends on the extra redhat commits.


I don't think so, there are redhat kernels which both do and do not work.



Cheers,
Michael

--
___
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: Koji: virtual memory exhausted: Cannot allocate memory

[Dan Horák]

On Mon, 12 Feb 2024 07:02:28 -0600
"W. Michael Petullo"  wrote:

> Building the current version of my opengrm-ngram package on Koji fails
> with the error "virtual memory exhausted: Cannot allocate memory"
> as indicated below. This happens only for i686; all of the other
> architectures build. Is this the fault of my package, or did something
> change at https://koji.fedoraproject.org?

the package (and its build enviroment) has grown. It fails because
32-bit system means max 4GB of address space for a process and ld runs
as a single process, so it's not uncommon to use all memory for large
C++ projects.

You can try disabling or reducing the size of debuginfo (from -g to -g1
or even -g0) to reduce the size of the *.o files. This usually helps.
Another option is to drop the i686 build per
https://fedoraproject.org/wiki/Changes/EncourageI686LeafRemoval


Dan

> 
> [...]
> libtool: link: g++ -Wl,--as-needed -std=c++17 -fno-exceptions  -fPIC -DPIC 
> -shared -nostdlib /usr/lib/gcc/i686-redhat-linux/14/../../../crti.o 
> /usr/lib/gcc/i686-redhat-linux/14/crtbeginS.o  .libs/ngram-absolute.o 
> .libs/ngram-context.o .libs/ngram-count.o .libs/ngram-count-prune.o 
> .libs/ngram-input.o .libs/ngram-kneser-ney.o .libs/ngram-list-prune.o 
> .libs/ngram-make.o .libs/ngram-marginalize.o .libs/ngram-output.o 
> .libs/ngram-shrink.o .libs/util.o   -ldl -L/usr/lib/fst -lfst -lgsl 
> -lflexiblas -L/usr/lib/gcc/i686-redhat-linux/14 
> -L/usr/lib/gcc/i686-redhat-linux/14/../../.. -lstdc++ -lm -lc -lgcc_s 
> /usr/lib/gcc/i686-redhat-linux/14/crtendS.o 
> /usr/lib/gcc/i686-redhat-linux/14/../../../crtn.o -Wl,-z,now 
> -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors 
> -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -O2 -flto=auto -g 
> -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 
> -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m32 
> -march=i686 -mtune
 =generic -msse2 -mfpmath=sse -mstackrealign -Wl,-z -Wl,relro -Wl,--as-needed 
-Wl,-z -Wl,pack-relative-relocs -Wl,-z -Wl,now 
-specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors 
-specs=/usr/lib/rpm/redhat/redhat-hardened-ld 
-specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 
-specs=/usr/lib/rpm/redhat/redhat-package-notes -Wl,-rpath=/usr/lib/fst   
-Wl,-soname -Wl,libngram.so.1315 -o .libs/libngram.so.1315.0.0
> libtool: link: (cd ".libs" && rm -f "libngram.so.1315" && ln -s 
> "libngram.so.1315.0.0" "libngram.so.1315")
> libtool: link: (cd ".libs" && rm -f "libngram.so" && ln -s 
> "libngram.so.1315.0.0" "libngram.so")
> libtool: link: ( cd ".libs" && rm -f "libngram.la" && ln -s "../libngram.la" 
> "libngram.la" )
> virtual memory exhausted: Cannot allocate memory
> [...]
> 
> https://koji.fedoraproject.org/koji/taskinfo?taskID=113388137
> 
> -- 
> Mike
> 
> :wq
> --
> ___
> 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

Koji: virtual memory exhausted: Cannot allocate memory

[W. Michael Petullo]

Building the current version of my opengrm-ngram package on Koji fails
with the error "virtual memory exhausted: Cannot allocate memory"
as indicated below. This happens only for i686; all of the other
architectures build. Is this the fault of my package, or did something
change at https://koji.fedoraproject.org?

[...]
libtool: link: g++ -Wl,--as-needed -std=c++17 -fno-exceptions  -fPIC -DPIC 
-shared -nostdlib /usr/lib/gcc/i686-redhat-linux/14/../../../crti.o 
/usr/lib/gcc/i686-redhat-linux/14/crtbeginS.o  .libs/ngram-absolute.o 
.libs/ngram-context.o .libs/ngram-count.o .libs/ngram-count-prune.o 
.libs/ngram-input.o .libs/ngram-kneser-ney.o .libs/ngram-list-prune.o 
.libs/ngram-make.o .libs/ngram-marginalize.o .libs/ngram-output.o 
.libs/ngram-shrink.o .libs/util.o   -ldl -L/usr/lib/fst -lfst -lgsl -lflexiblas 
-L/usr/lib/gcc/i686-redhat-linux/14 
-L/usr/lib/gcc/i686-redhat-linux/14/../../.. -lstdc++ -lm -lc -lgcc_s 
/usr/lib/gcc/i686-redhat-linux/14/crtendS.o 
/usr/lib/gcc/i686-redhat-linux/14/../../../crtn.o -Wl,-z,now 
-specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors 
-specs=/usr/lib/rpm/redhat/redhat-hardened-ld -O2 -flto=auto -g 
-grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 
-fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m32 
-march=i686 -mtune=generic -msse2 -mfpmath=sse -mstackrealign -Wl,-z -Wl,relro 
-Wl,--as-needed -Wl,-z -Wl,pack-relative-relocs -Wl,-z -Wl,now 
-specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors 
-specs=/usr/lib/rpm/redhat/redhat-hardened-ld 
-specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 
-specs=/usr/lib/rpm/redhat/redhat-package-notes -Wl,-rpath=/usr/lib/fst   
-Wl,-soname -Wl,libngram.so.1315 -o .libs/libngram.so.1315.0.0
libtool: link: (cd ".libs" && rm -f "libngram.so.1315" && ln -s 
"libngram.so.1315.0.0" "libngram.so.1315")
libtool: link: (cd ".libs" && rm -f "libngram.so" && ln -s 
"libngram.so.1315.0.0" "libngram.so")
libtool: link: ( cd ".libs" && rm -f "libngram.la" && ln -s "../libngram.la" 
"libngram.la" )
virtual memory exhausted: Cannot allocate memory
[...]

https://koji.fedoraproject.org/koji/taskinfo?taskID=113388137

-- 
Mike

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

FYI: removal of bastion server in DNSBL spam.dnsbl.anonmails.de requested

[Marius Schwarz]

Hi,

as die Infrastructure ML did not react ( or could not react ;) ), I 
requested the removal at that antispam blacklist.


2024-02-11 05:20:16 H=bastion-iad01.fedoraproject.org 
(bastion.fedoraproject.org) [38.145.60.11] 
X=TLS1.3:TLS_AES_256_GCM_SHA384:256 CV=no 
F= rejected RCPT 
: found in spam.dnsbl.anonmails.de


I hope it gets removed soon.

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

[Bug 2263833] perl-MIME-EncWords-1.015.0 is available

[bugzilla]

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



--- Comment #2 from Upstream Release Monitoring 
 ---
the-new-hotness/release-monitoring.org's scratch build of
perl-MIME-EncWords-1.015.0-1.fc38.src.rpm for rawhide completed
http://koji.fedoraproject.org/koji/taskinfo?taskID=113394230


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2263833

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202263833%23c2
--
___
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 2263833] New: perl-MIME-EncWords-1.015.0 is available

[bugzilla]

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

Bug ID: 2263833
   Summary: perl-MIME-EncWords-1.015.0 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-MIME-EncWords
  Keywords: FutureFeature, Triaged
  Assignee: xav...@bachelot.org
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: perl-devel@lists.fedoraproject.org,
xav...@bachelot.org
  Target Milestone: ---
Classification: Fedora



Releases retrieved: 1.015.0
Upstream release that is considered latest: 1.015.0
Current version/release in rawhide: 1.014.3-28.fc40
URL: http://search.cpan.org/dist/MIME-EncWords/

Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at:
https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring


Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.


Based on the information from Anitya:
https://release-monitoring.org/project/3071/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/perl-MIME-EncWords


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2263833

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202263833%23c0
--
___
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 2263833] perl-MIME-EncWords-1.015.0 is available

[bugzilla]

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



--- Comment #1 from Upstream Release Monitoring 
 ---
Created attachment 2016434
  --> https://bugzilla.redhat.com/attachment.cgi?id=2016434=edit
Update to 1.015.0 (#2263833)


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2263833

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202263833%23c1
--
___
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

Next Open NeuroFedora Meeting: 1300 UTC on Monday, 12 February, 2024 (today)

[Ankur Sinha]

Hello everyone,

Please join us at the next Open NeuroFedora team meeting on Monday 12
February at 1300UTC in the NeuroFedora channel on Matrix.  The meeting
is a public meeting, and open for everyone to attend. You can join us
over:

Matrix in the Fedora meeting channel: 
https://matrix.to/#/%23meeting:fedoraproject.org

You can use this link to see the local time for the meeting:
https://www.timeanddate.com/worldclock/fixedtime.html?msg=Open+NeuroFedora+Meeting=20240212T13=%3A=1

or you can use this command in a terminal:
$ date --date='TZ="UTC" 1300 Monday'

The meeting will be chaired by @ankursinha. The agenda for the
meeting is:

- New introductions and roll call.
- Tasks from last meeting: https://meetbot.fedoraproject.org/latest/neurofedora
- Open Pagure tickets: 
https://pagure.io/neuro-sig/NeuroFedora/issues?status=Open=S%3A+Next+meeting
- Package health check: 
https://packager-dashboard.fedoraproject.org/dashboard?groups=neuro-sig
- Open package reviews check: 
https://bugzilla.redhat.com/show_bug.cgi?id=fedora-neuro
- CompNeuro lab compose status check for F40: 
https://koji.fedoraproject.org/koji/packageinfo?packageID=30691
- Neuroscience query of the week
- Next meeting day, and chair.
- Open floor.

We hope to see you there!

The meeting announcement is also posted on the NeuroFedora blog here:
https://neuroblog.fedoraproject.org/2024/02/12/next-open-neurofedora-meeting-12-february-1300-utc.html

You can learn more about NeuroFedora here:
https://neuro.fedoraproject.org

-- 
Thanks,
Regards,
Ankur Sinha "FranciscoD" (He / Him / His) | 
https://fedoraproject.org/wiki/User:Ankursinha
Time zone: Europe/London


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

[Bug 2263687] perl-Business-ISBN-3.009 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Resolution|--- |ERRATA
   Fixed In Version||perl-Business-ISBN-3.009-4.
   ||fc40
 Status|MODIFIED|CLOSED
Last Closed||2024-02-12 09:57:05



--- Comment #2 from Fedora Update System  ---
FEDORA-2024-8e7be5c6fb (perl-Business-ISBN-3.009-4.fc40) has been pushed to the
Fedora 40 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=2263687

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202263687%23c2
--
___
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 2263687] perl-Business-ISBN-3.009 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



--- Comment #1 from Fedora Update System  ---
FEDORA-2024-8e7be5c6fb (perl-Business-ISBN-3.009-4.fc40) has been submitted as
an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-8e7be5c6fb


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2263687

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202263687%23c1
--
___
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

Current status of OSTree and its handling RPM scriptlets?

[Zdenek Dohnal]

Hi all,

there was an issue (either due a bug or due design) in the past about 
RPM OSTree treating %post scriptlets in SPEC file differently than on 
Fedora Linux - IIUC the explanation was %post scriptlets were applied on 
the server side of the system with RPM OSTree, thus any configuration 
changes like switching symlinks with alternatives were not 
applied/usable for normal user.


Has it got fixed during the time? Or is there a new technology which 
would do the trick for Silverblue and Fedora Linux alike?


Because there is a user which was used to setting NOEXEC on /usr/bin/vi 
to prevent running shell from vi as a root when using 'sudo vi' - since 
the /usr/bin/vi is shell script now and uses exec to spawn the correct 
binary, NOEXEC flags breaks 'sudo vi' completely.


The only possible solution here I see is to use alternatives in %post 
scriptlet, but if the situation is the same, the functionality brought 
by alternatives (automatic switch from vi -> vim and back if 
vim-enhanced is installed without shell restart) won't work in OSTree.


Thank you in advance!


Zdenek

--
Zdenek Dohnal
Senior Software Engineer
Red Hat, BRQ-TPBC
--
___
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: Bisecting an older kernel

[Michael J Gruber]

Am So., 11. Feb. 2024 um 23:14 Uhr schrieb Julian Sikorski :
>
> Hello,
>
> I am trying to bisect an issue which appears to have regressed between
> 5.18 final and 5.19-rc2. This is somewhat challenging as most of the
> kernels are since gone from koji, and the ark os-build branch seems to
> have been rebased after kernel 6.7 release, meaning that the required
> commits to the redhat folder are not in sync with the commits to the
> kernel itself.

I'm not sure I'm following this completely - are you saying that (part
of) the old kernel sources are not there (in git) any more because a
branch got rebased?

> I tried cherry-picking them on top, but it does not apply
> cleanly either:
>
> $ git clone -b os-build g...@gitlab.com:cki-project/kernel-ark.git
> $ git bisect start
> $ git bisect bad v5.19-rc2
> $ git bisect good v5.18
> $ git checkout 2518f226c60d8e04d18ba4295500a5b0b8ac7659
> $ git cherry-pick
> 0dd3ee31125508cd67f7e7172247f05b7fd1753a..6d8a7e484dc667c1094fc90452dee6af30d509f6
>
> Is there a way simpler than trying to fix the cherry-pick conflicts
> every single time?

`rerere` can be really helpful for something like this.

I guess you've checked already whether the problem you're trying to
solve depends on the extra redhat commits.

Cheers,
Michael
--
___
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 2260493] Retiring perl-Test-Vars, needed by perl-Test-Apocalypse

[bugzilla]

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

Petr Pisar  changed:

   What|Removed |Added

 Status|ON_QA   |CLOSED
 Resolution|--- |RAWHIDE
Last Closed||2024-02-12 09:01:05



--- Comment #5 from Petr Pisar  ---
The package was successfully removed from Fedora 40.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2260493

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202260493%23c5
--
___
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