Re: Orphaned packages looking for new maintainers

[Jens-Ulrik Petersen]

On Mon, Nov 6, 2023 at 7:32 PM Miro Hrončok  wrote:

> llvm12orphan, petersen, sergesanspaille
> 4 weeks ago
> llvm13jistone, orphan, petersen, sergesanspaille
>  4 weeks ago
>

I took these as usual.

At least llvm12 is still needed on aarch64 and s390x:

$ fdrq -q -a aarch64 rawhide --whatrequires llvm12 | grep -v llvm12
ghc8.10-compiler-8.10.7-12.fc40.aarch64 (fedora-rawhide-aarch64)
ghc9.0-compiler-9.0.2-14.fc39.aarch64 (fedora-rawhide-aarch64)
$ fdrq -q -a s390x rawhide --whatrequires llvm12 | grep -v llvm12
ghc9.2-compiler-9.2.8-21.fc39.s390x (fedora-rawhide-s390x)

Jens

ps You can try fedora-repoquery from this copr repo
.
___
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 2243201] perl-CGI-Application-Plugin-Session-1.05-27.fc40 FTBFS with CGI-4.59: Failed test 'Expiry should not change' at t/06_expiry.t line 69

[bugzilla]

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



--- Comment #3 from Fedora Update System  ---
FEDORA-2023-6e09bddbd5 has been submitted as an update to Fedora 39.
https://bodhi.fedoraproject.org/updates/FEDORA-2023-6e09bddbd5


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202243201%23c3
___
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 2243614] perl-Class-Date-1.1.17-17.fc40 FTBFS: t/50_timezone.t fails without tzdata package

[bugzilla]

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



--- Comment #3 from Fedora Update System  ---
FEDORA-2023-c329155c7b has been submitted as an update to Fedora 39.
https://bodhi.fedoraproject.org/updates/FEDORA-2023-c329155c7b


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202243614%23c3
___
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 2243614] perl-Class-Date-1.1.17-17.fc40 FTBFS: t/50_timezone.t fails without tzdata package

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

   Assignee|oss...@gmail.com|jples...@redhat.com
 CC||jples...@redhat.com




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2243614
___
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

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

[updates]

The following Fedora EPEL 7 Security updates need testing:
 Age  URL
   2  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-87285c6aca   
radare2-5.8.8-2.el7
   1  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-ca644cad1f   
chromium-119.0.6045.105-1.el7


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

audacious-4.3.1-2.el7
audacious-plugins-4.3.1-3.el7
squashfs-tools-ng-1.2.0-3.el7

Details about builds:



 audacious-4.3.1-2.el7 (FEDORA-EPEL-2023-21af57402a)
 Advanced audio player

Update Information:

# Audacious 4.3.1  Bugs fixed:* Fix incorrect detection of SymMod files as
MP3 files   * Fix reading of invalid ID3v2.4 tags   * Fix seek errors for some
FLAC files  Other changes:* Add Qt 6 support for the hotkey plugin   *
Restore saved volume settings on macOS   * Support Meson on BSD systems   * Set
`WM_WINDOW_ROLE` for top-level X11 windows   * Optimize bundled Winamp skins
with OptiPNG   * Update translations   # Audacious 4.3  New plugins and
features:* Add PipeWire output plugin   * Add native Opus decoder plugin   *
Support GTK3 again (optional, default is GTK2)   * Support of Qt 6 is mature
(optional, default is Qt 5)   * Meson support is feature complete now and tested
on all main platforms, so consider switching to this build system (Autotools is
still supported though)   * Allow copying file path in song info dialog   *
Support Ogg FLAC audio streams* Support reading embedded lyrics tags   *
Account for album artist in Search Tool   * Support new song length database
format in SID plugin   * Support Publisher and Catalog Number tags   * Add file
filter to Export Playlist file dialog  Bugs fixed since 4.2:* Show correct
song length for audio streams   * Correctly handle libflac built without Ogg
FLAC support   * Increased M3U file size limit from 16 MB to 256 MB   * Preserve
existing FLAC Vorbis comments  Improvements since 4.3-beta1:* Updated
translations, with Romanian as new supported language   * `Ctrl+F` in the Qt
interface now also searches in file names   * Prevent warning by FFmpeg about
discarded samples when opening files  Other changes:* Removed alarm plugin
due to serious bugs

ChangeLog:

* Wed Jul 19 2023 Fedora Release Engineering  - 
4.3.1-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_39_Mass_Rebuild
* Sun Apr 30 2023 Michael Schwendt  - 4.3.1-1
- Update to 4.3.1.
* Tue Mar  7 2023 Michael Schwendt  - 4.3-1
- Update to 4.3 release.
* Sat Feb 18 2023 Michael Schwendt  - 4.3-0.2.beta1
- Explicitly --disable-libarchive to confirm default.
* Mon Feb 13 2023 Michael Schwendt  - 4.3-0.1.beta1
- Upgrade to 4.3 beta1.
* Wed Jan 18 2023 Fedora Release Engineering  - 4.2-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_38_Mass_Rebuild




 audacious-plugins-4.3.1-3.el7 (FEDORA-EPEL-2023-21af57402a)
 Plugins for the Audacious audio player

Update Information:

# Audacious 4.3.1  Bugs fixed:* Fix incorrect detection of SymMod files as
MP3 files   * Fix reading of invalid ID3v2.4 tags   * Fix seek errors for some
FLAC files  Other changes:* Add Qt 6 support for the hotkey plugin   *
Restore saved volume settings on macOS   * Support Meson on BSD systems   * Set
`WM_WINDOW_ROLE` for top-level X11 windows   * Optimize bundled Winamp skins
with OptiPNG   * Update translations   # Audacious 4.3  New plugins and
features:* Add PipeWire output plugin   * Add native Opus decoder plugin   *
Support GTK3 again (optional, default is GTK2)   * Support of Qt 6 is mature
(optional, default is Qt 5)   * Meson support is feature complete now and tested
on all main platforms, so consider switching to this build system (Autotools is
still supported though)   * Allow copying file path in song info dialog   *
Support Ogg FLAC audio streams* Support reading embedded lyrics tags   *
Account for album artist in Search Tool   * Support new song length database
format in SID plugin   * Support Publisher and Catalog Number tags   * Add file
filter to Export Playlist file dialog  Bugs fixed since 4.2:* Show correct
song length for audio streams   * Correctly handle libflac built without Ogg
FLAC support   * Increased M3U file size limit from 16 MB to 256 MB   * Preserve
existing FLAC Vorbis comments  Improvements since 4.3-beta1:* Updated
translations, with Romanian as new supported language   * `Ctrl+F` in the Qt
interface now also searches in file names   * Prevent warning by FFmpeg about
discarded samples when opening files  

[Bug 2248772] perl-DBM-Deep-2.0018 is available

[bugzilla]

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



--- Comment #1 from Upstream Release Monitoring 
 ---
Scratch build failed. Details below:

BuilderException: Build failed:
Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs',
'/var/tmp/thn-xt349icv/perl-DBM-Deep.spec']' returned non-zero exit status 1.

StdOut:
setting SOURCE_DATE_EPOCH=1699401600
error: Bad file: ./DBM-Deep-2.0018.tar.gz: No such file or directory

RPM build errors:
Bad file: ./DBM-Deep-2.0018.tar.gz: No such file or directory


Traceback:
  File
"/usr/local/lib/python3.11/site-packages/hotness/use_cases/package_scratch_build_use_case.py",
line 56, in build
result = self.builder.build(request.package, request.opts)
 ^
  File "/usr/local/lib/python3.11/site-packages/hotness/builders/koji.py", line
229, in build
raise BuilderException(

If you think this issue is caused by some bug in the-new-hotness, please report
it on the-new-hotness issue tracker:
https://github.com/fedora-infra/the-new-hotness/issues


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

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

[Bug 2248772] perl-DBM-Deep-2.0018 is available

[bugzilla]

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



--- Comment #2 from Upstream Release Monitoring 
 ---
Created attachment 1997949
  --> https://bugzilla.redhat.com/attachment.cgi?id=1997949=edit
Update to 2.0018 (#2248772)


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202248772%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 2248772] New: perl-DBM-Deep-2.0018 is available

[bugzilla]

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

Bug ID: 2248772
   Summary: perl-DBM-Deep-2.0018 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-DBM-Deep
  Keywords: FutureFeature, Triaged
  Assignee: andr...@bawue.net
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: andr...@bawue.net, p...@city-fan.org,
perl-devel@lists.fedoraproject.org
  Target Milestone: ---
Classification: Fedora



Releases retrieved: 2.0018
Upstream release that is considered latest: 2.0018
Current version/release in rawhide: 2.0017-1.fc40
URL: http://search.cpan.org/dist/DBM-Deep/

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


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


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

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

Fedora CoreOS Meeting Minutes 2023-11-08

[Dusty Mabe]

Minutes: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2023-11-08/fedora_coreos_meeting.2023-11-08-16.29.html
Minutes (text): 
https://meetbot.fedoraproject.org/fedora-meeting-1/2023-11-08/fedora_coreos_meeting.2023-11-08-16.29.txt
Log: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2023-11-08/fedora_coreos_meeting.2023-11-08-16.29.log.html


#fedora-meeting-1: fedora_coreos_meeting



Meeting started by dustymabe at 16:29:22 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-1/2023-11-08/fedora_coreos_meeting.2023-11-08-16.29.log.html
.



Meeting summary
---
* roll call  (dustymabe, 16:29:31)
  * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1608
maybe?  (travier, 16:33:17)

* Action items from last meeting  (dustymabe, 16:35:13)
  * ACTION: travier to create a change proposal for F40 for switching
away from nss-altfiles for OSTree based systems  (dustymabe,
16:37:26)
  * ACTION: travier to schedule meeting with Assisted installer team to
understand the use case around
https://github.com/coreos/fedora-coreos-tracker/issues/1595
(dustymabe, 16:37:37)

* Nodes Fail To Update (Zincati Reports libsystemd errors regarding
  EMFILE: Too many open files)  (dustymabe, 16:37:53)
  * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1608
(dustymabe, 16:38:00)
  * LINK: https://hackmd.io/xPcq8EvxTH6TQhFFx_Rfug?edit   (dustymabe,
17:04:03)
  * we have a path forward where we think stable nodes won't need manual
intervention, but testing/next nodes will. We will put out ad-hoc
releases for all streams and send a communication to everyone a bout
necessary steps.  (dustymabe, 17:05:39)

* open floor   (dustymabe, 17:08:03)
  * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1296 ?
(Nemric, 17:08:24)
  * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1566
(dustymabe, 17:16:21)
  * LINK:
https://fedoraproject.org/wiki/Fedora_Linux_39_Release_Party_Schedule
(dustymabe, 17:25:55)

Meeting ended at 17:30:42 UTC.




Action Items

* travier to create a change proposal for F40 for switching away from
  nss-altfiles for OSTree based systems
* travier to schedule meeting with Assisted installer team to understand
  the use case around
  https://github.com/coreos/fedora-coreos-tracker/issues/1595




Action Items, by person
---
* travier
  * travier to create a change proposal for F40 for switching away from
nss-altfiles for OSTree based systems
  * travier to schedule meeting with Assisted installer team to
understand the use case around
https://github.com/coreos/fedora-coreos-tracker/issues/1595
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* dustymabe (123)
* travier (31)
* jlebon (29)
* zodbot (17)
* Nemric (15)
* apiaseck (11)
* jmarrero (2)
* fifofonix (2)
* marmijo (1)
* spresti (1)
* ydesouza (1)




Generated by `MeetBot`_ 0.4

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

Re: Is it possible (or a good idea) to add additional files to the -debuginfo packages?

[Richard W.M. Jones]

On Wed, Nov 08, 2023 at 09:01:15AM -0500, Omair Majid wrote:
> Hi,
> 
> "Richard W.M. Jones"  writes:
> 
> > Can you be a bit more specific?  What programming language?  What does
> > the debug data look like?  Is it embedded in ELF sections?  What tools
> > are needed / provided to extract it?  How does the debugger read it?
> 
> This is for the .NET ecosystem, where the primary languages include C#,
> F# and VB.NET.
> 
> The compiled .NET code files are generally named along the lines of
> Foo.dll, and debug data is stored in separate Foo.pdb files. The files
> are generated by the .NET compilers directly. The Foo.dll file generally
> contains a reference to where the .pdb files are stored (they could be
> online, for example, - similar to a debuginfod server - or on the disk
> next to the .dll file).
> 
> I am not aware of any non-.NET tools in Fedora that can work with these
> files.
> 
> .NET-specific debuggers know how to find the .pdb files when they see a
> .dll file. Generally, every IDE provides their own debugger (often
> closed source). An open source debugger is available at
> https://github.com/Samsung/netcoredbg/ and used by some
> (non-Fedora-packaged) open source IDEs.
> 
> To circle back to my original question, the disk layout currently looks
> something like this:
> 
> - /usr/lib64/dotnet/shared/$NAME/$VERSION/foo.dll
> - /usr/lib64/dotnet/shared/$NAME/$VERSION/foo.pdb

I suspect it would be confusing to have debuginfo sometimes contain
.pdb files, and it would make all the debuginfo generation code much
more complicated.  But others are experts about this.

However some kind of alternate -windbg standard might work?

Who will consume this in Fedora?  Is netcoredbg packaged?  Can Wine
use them?

Although we ship a few *.exe files in Fedora now, we got a lot of
pushback about this when we proposed it originally (around 2008).
There is usually a clear case where we do include them: they are
necessary utilities that can run under Wine, or -- like rhsrvany.exe /
pnp_wait.exe / qemu-ga -- we need them so we can install the files
inside Windows guests.  Generally packaging random open source Windows
*.exes as Fedora RPMs "just because" is frowned on.

> I was thinking that it might be possible to put the .dll file in the
> base package (eg, dotnet-runtime-8.0) and the .pdb file in the debug package
> (eg, dotnet-runtime-8.0-debuginfo) somehow.

It would definitely be technically possible to write some RPM macros
that package them, but as above putting them into something
specifically called -debuginfo could be confusing.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-p2v converts physical machines to virtual machines.  Boot with a
live CD or over the network (PXE) and turn machines into KVM guests.
http://libguestfs.org/virt-v2v
___
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: Didn't get an email about a new merge request on a package

[Richard W.M. Jones]

On Wed, Nov 08, 2023 at 12:33:28PM -0800, Kevin Fenzi wrote:
> On Wed, Nov 08, 2023 at 01:26:53PM +0100, Fabio Valentini wrote:
> ...snip...
> > 
> > So to me this sounds like there was just some hiccup somewhere that
> > resulted in the email not being sent.
> 
> Yeah, seems like: 
> 
> Oct 28 09:04:13 pkgs01 celery[1147999]: 2023-10-28 09:04:13,585 [ERROR] 
> celery.app.trace: Task 
> pagure.lib.tasks.update_git[c29a4cbf-ba3d-41f6-b29f-6a74bf400fa2] raised 
> unexpected: Exception('Unable to find object',)
> Oct 28 09:04:13 pkgs01 celery[1147999]: Traceback (most recent call last):
> Oct 28 09:04:13 pkgs01 celery[1147999]:  File 
> "/usr/lib/python3.6/site-packages/celery/app/trace.py", line 385, in 
> trace_task
> Oct 28 09:04:13 pkgs01 celery[1147999]:R = retval = fun(*args, **kwargs)
> Oct 28 09:04:13 pkgs01 celery[1147999]:  File 
> "/usr/lib/python3.6/site-packages/celery/app/trace.py", line 648, in 
> __protected_call__
> Oct 28 09:04:13 pkgs01 celery[1147999]:return self.run(*args, **kwargs)
> Oct 28 09:04:13 pkgs01 celery[1147999]:  File 
> "/usr/lib/python3.6/site-packages/pagure/lib/tasks_utils.py", line 36, in 
> decorated_function
> Oct 28 09:04:13 pkgs01 celery[1147999]:return function(self, session, 
> *args, **kwargs)
> Oct 28 09:04:13 pkgs01 celery[1147999]:  File 
> "/usr/lib/python3.6/site-packages/pagure/lib/tasks.py", line 357, in 
> update_git
> Oct 28 09:04:13 pkgs01 celery[1147999]:raise Exception("Unable to find 
> object")
> Oct 28 09:04:13 pkgs01 celery[1147999]: Exception: Unable to find object
> 
> I am not sure what happened there. ;( Some kind of race condition?
> 
> But that matches up exactly when the PR was created.

Thanks for investigating!

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
libguestfs lets you edit virtual machines.  Supports shell scripting,
bindings from many languages.  http://libguestfs.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: Didn't get an email about a new merge request on a package

[Sandro]

On 08-11-2023 21:33, Kevin Fenzi wrote:

Oct 28 09:04:13 pkgs01 celery[1147999]:  File 
"/usr/lib/python3.6/site-packages/celery/app/trace.py", line 385, in trace_task



I am not sure what happened there. ;( Some kind of race condition?


Python getting old and not being able to keep ahead in the enduring race? 

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

Re: Didn't get an email about a new merge request on a package

[Kevin Fenzi]

On Wed, Nov 08, 2023 at 01:26:53PM +0100, Fabio Valentini wrote:
...snip...
> 
> So to me this sounds like there was just some hiccup somewhere that
> resulted in the email not being sent.

Yeah, seems like: 

Oct 28 09:04:13 pkgs01 celery[1147999]: 2023-10-28 09:04:13,585 [ERROR] 
celery.app.trace: Task 
pagure.lib.tasks.update_git[c29a4cbf-ba3d-41f6-b29f-6a74bf400fa2] raised 
unexpected: Exception('Unable to find object',)
Oct 28 09:04:13 pkgs01 celery[1147999]: Traceback (most recent call last):
Oct 28 09:04:13 pkgs01 celery[1147999]:  File 
"/usr/lib/python3.6/site-packages/celery/app/trace.py", line 385, in trace_task
Oct 28 09:04:13 pkgs01 celery[1147999]:R = retval = fun(*args, **kwargs)
Oct 28 09:04:13 pkgs01 celery[1147999]:  File 
"/usr/lib/python3.6/site-packages/celery/app/trace.py", line 648, in 
__protected_call__
Oct 28 09:04:13 pkgs01 celery[1147999]:return self.run(*args, **kwargs)
Oct 28 09:04:13 pkgs01 celery[1147999]:  File 
"/usr/lib/python3.6/site-packages/pagure/lib/tasks_utils.py", line 36, in 
decorated_function
Oct 28 09:04:13 pkgs01 celery[1147999]:return function(self, session, 
*args, **kwargs)
Oct 28 09:04:13 pkgs01 celery[1147999]:  File 
"/usr/lib/python3.6/site-packages/pagure/lib/tasks.py", line 357, in update_git
Oct 28 09:04:13 pkgs01 celery[1147999]:raise Exception("Unable to find 
object")
Oct 28 09:04:13 pkgs01 celery[1147999]: Exception: Unable to find object

I am not sure what happened there. ;( Some kind of race condition?

But that matches up exactly when the PR was created.

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

[Bug 2243614] perl-Class-Date-1.1.17-17.fc40 FTBFS: t/50_timezone.t fails without tzdata package

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version||perl-Class-Date-1.1.17-19.f
   ||c40
 Resolution|--- |ERRATA
 Status|MODIFIED|CLOSED
Last Closed||2023-11-08 16:04:28



--- Comment #2 from Fedora Update System  ---
FEDORA-2023-77bfc57395 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=2243614

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202243614%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 2243614] perl-Class-Date-1.1.17-17.fc40 FTBFS: t/50_timezone.t fails without tzdata package

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|NEW |MODIFIED



--- Comment #1 from Fedora Update System  ---
FEDORA-2023-77bfc57395 has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2023-77bfc57395


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

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

Re: Becoming a member of the Fedora Packager GIT Commit Group (packager)

[Stephen Gallagher]

On Wed, Nov 8, 2023 at 6:35 AM James Chapman  wrote:
>
> Hi All,
>
> I need to become a member of the packager group in order to help with some 
> Fedora, 389 Directory Server builds.
>
> Can any sponsor of the "packager" group do me the honour of making me a 
> member of this group.
>

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

Re: Is it possible (or a good idea) to add additional files to the -debuginfo packages?

[Omair Majid]

Hi,

"Richard W.M. Jones"  writes:

> Can you be a bit more specific?  What programming language?  What does
> the debug data look like?  Is it embedded in ELF sections?  What tools
> are needed / provided to extract it?  How does the debugger read it?

This is for the .NET ecosystem, where the primary languages include C#,
F# and VB.NET.

The compiled .NET code files are generally named along the lines of
Foo.dll, and debug data is stored in separate Foo.pdb files. The files
are generated by the .NET compilers directly. The Foo.dll file generally
contains a reference to where the .pdb files are stored (they could be
online, for example, - similar to a debuginfod server - or on the disk
next to the .dll file).

I am not aware of any non-.NET tools in Fedora that can work with these
files.

.NET-specific debuggers know how to find the .pdb files when they see a
.dll file. Generally, every IDE provides their own debugger (often
closed source). An open source debugger is available at
https://github.com/Samsung/netcoredbg/ and used by some
(non-Fedora-packaged) open source IDEs.

To circle back to my original question, the disk layout currently looks
something like this:

- /usr/lib64/dotnet/shared/$NAME/$VERSION/foo.dll
- /usr/lib64/dotnet/shared/$NAME/$VERSION/foo.pdb

I was thinking that it might be possible to put the .dll file in the
base package (eg, dotnet-runtime-8.0) and the .pdb file in the debug package
(eg, dotnet-runtime-8.0-debuginfo) somehow.

Thanks,
Omair

--
PGP Key: B157A9F0 (http://pgp.mit.edu/)
Fingerprint = 9DB5 2F0B FD3E C239 E108  E7BD DF99 7AF8 B157 A9F0
___
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

[Testdays] Call for Fedora Linux 40 testing events

[Sumantro Mukherjee]

Hi Fedora users, developers, and friends!

It's time to start thinking about Test Days for Fedora 40.

For anyone who isn't aware, a Test Day is an event usually focused
around IRC for interaction and a Wiki page for instructions and results,
with the aim being to get a bunch of interested users and developers
together to test a specific feature or area of the distribution. You can
run a Test Day on just about anything for which it would be useful to do
some fairly focused testing in 'real time' with a group of testers; it
doesn't have to be code, for instance, we often run Test Days for
l10n/i18n topics. For more information on Test Days, see
https://fedoraproject.org/wiki/QA/Test_Days .

Anyone who wants to can host their own Test Day, or you can request that
the QA group helps you out with organization or any combination of the
two. To propose a Test Day, just file a ticket in fedora-qa pagure - here's
an example https://pagure.io/fedora-qa/issue/624 . For
instructions on hosting a Test Day, see
https://fedoraproject.org/wiki/QA/SOP_Test_Day_management .

You can see the schedule at https://pagure.io/fedora-qa/issues?tags=test+days .
There are many slots open right now. Consider the development
schedule, though, in deciding when you want to run your Test Day - for
some topics you may want to avoid
the time before the Beta release or the time after the feature freeze
or the Final Freeze.

We normally aim to schedule Test Days on Thursdays; however, if you want
to run a series of related Test Days, it's often a good idea to do
something like Tuesday / Wednesday / Thursday of the same week (this is
how we usually run the X Test Week, for instance). If all the Thursday
slots fill up but more people want to run Test Days, we will open up
Tuesday slots as overflows. And finally, if you really want to run a
Test Day in a specific time frame due to the development schedule, but
the Thursday slot for that week is full, we can add a slot on another
day. We're flexible! Just put in your ticket the date or time frame you'd
like, and we'll figure it out from there.

If you don't want to run your own Test Day, but you are willing to
help with another, feel free to join one or more of already accepted
Test Days:

GNOME Test Day*
i18n Test Day*
Kernel Test Week(s)*
Upgrade Test Day*
IoT Test Week*
Cloud Test Day*
Fedora CoreOS Test Week*

And don't be afraid, there are a lot of more slots available for your
own Test Day!

[*] These are the test days we run generally to make sure everything
is working fine, the dates get announced as we move into the release
cycle.

If you have any questions about the Test Day process, please don't
hesitate to contact me or any member of the Fedora QA team on test at
lists.fedoraproject.org or in #fedora-qa on IRC. Thanks!


-- 
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED
___
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: Didn't get an email about a new merge request on a package

[Fabio Valentini]

On Wed, Nov 8, 2023 at 1:03 PM Richard W.M. Jones  wrote:
>
> On Wed, Nov 08, 2023 at 06:49:19AM -0500, Neal Gompa wrote:
> > On Wed, Nov 8, 2023 at 6:39 AM Richard W.M. Jones  wrote:
> > >
> > > Normally I get an email when someone creates a merge request on a
> > > Fedora package that I'm (co-)maintaining.  However I don't seem to
> > > have got an email about this specific request:
> > >
> > >   https://src.fedoraproject.org/rpms/libguestfs/pull-request/8
> > >
> > > and I wonder why.  (Checked filters etc already.)
> > >
> > > One thing that did happen recently is we moved the libguestfs mailing
> > > list to a new host, and that meant dropping the old email address
> > > (libgues...@redhat.com) but AFAIK I don't think that email address is
> > > involved here.
> > >
> > > Also:
> > >
> > >   
> > > https://src.fedoraproject.org/rpms/libguestfs/settings#publicnotifications-tab
> > >   -> "Pull-requests notifications"
> > >
> > > the field is empty.  I don't recall ever encountering this field or
> > > setting it for any Fedora project.  I checked a few other projects I
> > > maintain and they are also empty.
> >
> > Do you have notifications configured in
> > notifications.fedoraproject.org? I believe no notifications are
> > configured by default.
>
> It says:
>
>   My Rules
>
> No Rules
> [Create a Rule]
>
> I don't recall ever touching this.

That's the new notifications system, where everybody started off with
a clean slate.
Apparently migrating settings from the old notifications system to the
new one was not feasible.
However, the old notifications system is *not* decommisioned yet, so
the fact that you've not set up the new one does not matter (yet).

So to me this sounds like there was just some hiccup somewhere that
resulted in the email not being sent.

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

Re: I propose sphinx no longer Requires sphinxcontrib-{applehelp,devhelp,jsmath,htmlhelp,serializinghtml,qthelp}

[Neal Gompa]

On Wed, Nov 8, 2023 at 7:02 AM Miro Hrončok  wrote:
>
> On 08. 11. 23 12:57, Neal Gompa wrote:
> >> Packages that need those would need to BuildRequire them specifically, as
> >> proposed in:
> >>
> >>-https://src.fedoraproject.org/rpms/xca/pull-request/1
> >>
> >> -https://src.fedoraproject.org/rpms/python-django-haystack/pull-request/1
> >>-https://src.fedoraproject.org/rpms/pykka/pull-request/3
> >>-https://src.fedoraproject.org/rpms/extra-cmake-modules/pull-request/2
> >>
> >> The change has been offered upstream, but I suppose it will take a while 
> >> before
> >> it is actually landed there.
> >>
> >> Let me know if you think this needs more discussion before shipping it.
> >>
> >> (The change is only intended for Fedora 40+ and ELN.)
> >>
> > Do we know what the impact of this is going to be beyond those four?
>
> All Fedora packages that BuildRequire python3-sphinx (even transitively) were
> tested. Those that successfully built before this change are known not to be
> impacted, except for the listed 4 and
> https://src.fedoraproject.org/rpms/python-fastavro/pull-request/12 (which is
> special, because the removal only uncovered a bug in tests).
>
> This was tested in
> https://copr.fedorainfracloud.org/coprs/churchyard/sphinxcontrib-optional/builds/
> and
> https://copr.fedorainfracloud.org/coprs/churchyard/sphinxcontrib-mandaotry/builds/
>
> A handful of packages timed out after 5 hours in Copr, happy to fix them later
> if they they are impacted. Same for the packages that FTBFS now for unrelated
> reasons.
>

Then I'm fine with this, let's do it. :)


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

[Bug 2184301] perl-Syntax-Feature-Loop-1.8.0-18.fc39 FTBFS: t/01_basic.t and 3 more tests fail

[bugzilla]

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

Fedora Admin user for bugzilla script actions 
 changed:

   What|Removed |Added

   Assignee|jples...@redhat.com |extras-orphan@fedoraproject
   ||.org



--- Comment #2 from Fedora Admin user for bugzilla script actions 
 ---
This package has changed maintainer in Fedora. Reassigning to the new
maintainer of this component.


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202184301%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 2222637] F39FailsToInstall: perl-Syntax-Feature-Loop

[bugzilla]

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

Fedora Admin user for bugzilla script actions 
 changed:

   What|Removed |Added

   Assignee|jples...@redhat.com |extras-orphan@fedoraproject
   ||.org



--- Comment #3 from Fedora Admin user for bugzilla script actions 
 ---
This package has changed maintainer in Fedora. Reassigning to the new
maintainer of this component.


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%20637%23c3
___
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: Didn't get an email about a new merge request on a package

[Richard W.M. Jones]

On Wed, Nov 08, 2023 at 06:49:19AM -0500, Neal Gompa wrote:
> On Wed, Nov 8, 2023 at 6:39 AM Richard W.M. Jones  wrote:
> >
> > Normally I get an email when someone creates a merge request on a
> > Fedora package that I'm (co-)maintaining.  However I don't seem to
> > have got an email about this specific request:
> >
> >   https://src.fedoraproject.org/rpms/libguestfs/pull-request/8
> >
> > and I wonder why.  (Checked filters etc already.)
> >
> > One thing that did happen recently is we moved the libguestfs mailing
> > list to a new host, and that meant dropping the old email address
> > (libgues...@redhat.com) but AFAIK I don't think that email address is
> > involved here.
> >
> > Also:
> >
> >   
> > https://src.fedoraproject.org/rpms/libguestfs/settings#publicnotifications-tab
> >   -> "Pull-requests notifications"
> >
> > the field is empty.  I don't recall ever encountering this field or
> > setting it for any Fedora project.  I checked a few other projects I
> > maintain and they are also empty.
> 
> Do you have notifications configured in
> notifications.fedoraproject.org? I believe no notifications are
> configured by default.

It says:

  My Rules

No Rules
[Create a Rule]

I don't recall ever touching this.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-top is 'top' for virtual machines.  Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top
___
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: I propose sphinx no longer Requires sphinxcontrib-{applehelp,devhelp,jsmath,htmlhelp,serializinghtml,qthelp}

[Miro Hrončok]

On 08. 11. 23 12:57, Neal Gompa wrote:

Packages that need those would need to BuildRequire them specifically, as
proposed in:

   -https://src.fedoraproject.org/rpms/xca/pull-request/1
   -https://src.fedoraproject.org/rpms/python-django-haystack/pull-request/1
   -https://src.fedoraproject.org/rpms/pykka/pull-request/3
   -https://src.fedoraproject.org/rpms/extra-cmake-modules/pull-request/2

The change has been offered upstream, but I suppose it will take a while before
it is actually landed there.

Let me know if you think this needs more discussion before shipping it.

(The change is only intended for Fedora 40+ and ELN.)


Do we know what the impact of this is going to be beyond those four?


All Fedora packages that BuildRequire python3-sphinx (even transitively) were 
tested. Those that successfully built before this change are known not to be 
impacted, except for the listed 4 and 
https://src.fedoraproject.org/rpms/python-fastavro/pull-request/12 (which is 
special, because the removal only uncovered a bug in tests).


This was tested in 
https://copr.fedorainfracloud.org/coprs/churchyard/sphinxcontrib-optional/builds/ 
and 
https://copr.fedorainfracloud.org/coprs/churchyard/sphinxcontrib-mandaotry/builds/


A handful of packages timed out after 5 hours in Copr, happy to fix them later 
if they they are impacted. Same for the packages that FTBFS now for unrelated 
reasons.


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

Re: I propose sphinx no longer Requires sphinxcontrib-{applehelp,devhelp,jsmath,htmlhelp,serializinghtml,qthelp}

[Neal Gompa]

On Wed, Nov 8, 2023 at 6:56 AM Miro Hrončok  wrote:
>
> Hello Pythonistas.
>
> In https://src.fedoraproject.org/rpms/python-sphinx/pull-request/59 I propose 
> a
> change that would make the runtime requirements of:
>
>   - python3-sphinxcontrib-applehelp
>   - python3-sphinxcontrib-devhelp
>   - python3-sphinxcontrib-jsmath
>   - python3-sphinxcontrib-htmlhelp
>   - python3-sphinxcontrib-serializinghtml
>   - python3-sphinxcontrib-qthelp
>
> ...optional (Recommends) in python3-sphinx.
>
> Packages that need those would need to BuildRequire them specifically, as
> proposed in:
>
>   - https://src.fedoraproject.org/rpms/xca/pull-request/1
>   - https://src.fedoraproject.org/rpms/python-django-haystack/pull-request/1
>   - https://src.fedoraproject.org/rpms/pykka/pull-request/3
>   - https://src.fedoraproject.org/rpms/extra-cmake-modules/pull-request/2
>
> The change has been offered upstream, but I suppose it will take a while 
> before
> it is actually landed there.
>
> Let me know if you think this needs more discussion before shipping it.
>
> (The change is only intended for Fedora 40+ and ELN.)
>

Do we know what the impact of this is going to be beyond those four?



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

I propose sphinx no longer Requires sphinxcontrib-{applehelp,devhelp,jsmath,htmlhelp,serializinghtml,qthelp}

[Miro Hrončok]

Hello Pythonistas.

In https://src.fedoraproject.org/rpms/python-sphinx/pull-request/59 I propose a 
change that would make the runtime requirements of:


 - python3-sphinxcontrib-applehelp
 - python3-sphinxcontrib-devhelp
 - python3-sphinxcontrib-jsmath
 - python3-sphinxcontrib-htmlhelp
 - python3-sphinxcontrib-serializinghtml
 - python3-sphinxcontrib-qthelp

...optional (Recommends) in python3-sphinx.

Packages that need those would need to BuildRequire them specifically, as 
proposed in:


 - https://src.fedoraproject.org/rpms/xca/pull-request/1
 - https://src.fedoraproject.org/rpms/python-django-haystack/pull-request/1
 - https://src.fedoraproject.org/rpms/pykka/pull-request/3
 - https://src.fedoraproject.org/rpms/extra-cmake-modules/pull-request/2

The change has been offered upstream, but I suppose it will take a while before 
it is actually landed there.


Let me know if you think this needs more discussion before shipping it.

(The change is only intended for Fedora 40+ and ELN.)

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

Re: Didn't get an email about a new merge request on a package

[Neal Gompa]

On Wed, Nov 8, 2023 at 6:39 AM Richard W.M. Jones  wrote:
>
> Normally I get an email when someone creates a merge request on a
> Fedora package that I'm (co-)maintaining.  However I don't seem to
> have got an email about this specific request:
>
>   https://src.fedoraproject.org/rpms/libguestfs/pull-request/8
>
> and I wonder why.  (Checked filters etc already.)
>
> One thing that did happen recently is we moved the libguestfs mailing
> list to a new host, and that meant dropping the old email address
> (libgues...@redhat.com) but AFAIK I don't think that email address is
> involved here.
>
> Also:
>
>   
> https://src.fedoraproject.org/rpms/libguestfs/settings#publicnotifications-tab
>   -> "Pull-requests notifications"
>
> the field is empty.  I don't recall ever encountering this field or
> setting it for any Fedora project.  I checked a few other projects I
> maintain and they are also empty.

Do you have notifications configured in
notifications.fedoraproject.org? I believe no notifications are
configured by default.



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

Didn't get an email about a new merge request on a package

[Richard W.M. Jones]

Normally I get an email when someone creates a merge request on a
Fedora package that I'm (co-)maintaining.  However I don't seem to
have got an email about this specific request:

  https://src.fedoraproject.org/rpms/libguestfs/pull-request/8

and I wonder why.  (Checked filters etc already.)

One thing that did happen recently is we moved the libguestfs mailing
list to a new host, and that meant dropping the old email address
(libgues...@redhat.com) but AFAIK I don't think that email address is
involved here.

Also:

  https://src.fedoraproject.org/rpms/libguestfs/settings#publicnotifications-tab
  -> "Pull-requests notifications"

the field is empty.  I don't recall ever encountering this field or
setting it for any Fedora project.  I checked a few other projects I
maintain and they are also empty.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
Fedora Windows cross-compiler. Compile Windows programs, test, and
build Windows installers. Over 100 libraries supported.
http://fedoraproject.org/wiki/MinGW
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Becoming a member of the Fedora Packager GIT Commit Group (packager)

[James Chapman]

Hi All,

I need to become a member of the packager group in order to help with some
Fedora, 389 Directory Server builds.

Can any sponsor of the "packager" group do me the honour of making me a
member of this group.

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

Re: Is it possible (or a good idea) to add additional files to the -debuginfo packages?

[Richard W.M. Jones]

On Tue, Nov 07, 2023 at 01:40:09PM -0500, Omair Majid wrote:
> Hi,
> 
> I am trying to enable debug information for a programming language that
> produces debuginfo in a custom (non-DWARF) format. I was thinking that
> adding that programming-language-specific debuginfo to existing
> -debuginfo packages seems like a good idea.
> 
> (Is that a bad idea?)
> 
> Any suggestions on how I can add additional files to the auto-generated
> -debuginfo packages (which already contain some useful DWARF debuginfo).

Can you be a bit more specific?  What programming language?  What does
the debug data look like?  Is it embedded in ELF sections?  What tools
are needed / provided to extract it?  How does the debugger read it?

Rich.

> Thanks,
> Omair
> 
> --
> PGP Key: B157A9F0 (http://pgp.mit.edu/)
> Fingerprint = 9DB5 2F0B FD3E C239 E108  E7BD DF99 7AF8 B157 A9F0
> ___
> 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

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
nbdkit - Flexible, fast NBD server with plugins
https://gitlab.com/nbdkit/nbdkit
___
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: Automatic check for bodhi updates not to break RPM dependencies

[Richard W.M. Jones]

On Tue, Nov 07, 2023 at 04:20:52PM +0100, Kevin Kofler via devel wrote:
> Miro Hrončok wrote:
> > this is not the first time I saw a bodhi update that breaks dozens of
> > dependencies, goes unnoticed for a week and is automatically pushed
> > stable, only to discover many packages fail to install.
> 
> The most important measure would be to abolish automatic pushes. This update 
> was automatically pushed after 7 days with no feedback whatsoever. Promoting 
> an update to stable should require a human to explicitly click a "push to 
> stable" button, thereby acknowledging the lack of feedback.

The vast majority of packages will get no feedback and can be pushed
to stable without problems.

When there is a problem like in this case, it causes a minor
inconvenience for some people and is easily fixed.  Temporarily can't
update a Fedora package is not one of the world's biggest problems
right now.

Rich.

> > How come we don't have an automatic check for this? What can be done?
> 
> I also do not understand why the gating stuff that was recently added does 
> not complain about this.
> 
> 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

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-p2v converts physical machines to virtual machines.  Boot with a
live CD or over the network (PXE) and turn machines into KVM guests.
http://libguestfs.org/virt-v2v
___
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: Request for comment- tuned replacing power-profiles-daemon plan

[Kate Hsuan]

Hi Neal,

Already sent a message to them through Matrix.

Thank you :)

Hi Allan,

I submitted an issue to the gitlab. We could discuss it through the
issue discussion.
For the shorterm plan, I would like to focus on integration and make
sure all the components work properly. Then, we start to think about
the improvement of the user interface and the architecture. If we can
do every in parallel, that would be great too :)

Thank you.

On Tue, Nov 7, 2023 at 12:12 PM Neal Gompa  wrote:
>
> On Mon, Nov 6, 2023 at 10:58 PM Kate Hsuan  wrote:
> >
> > Hi Allan,
> >
> > Thank you for the comments.
> >
> > On Tue, Nov 7, 2023 at 12:31 AM Allan Day  wrote:
> > >
> > > Hi Kate,
> > >
> > > On Thu, Oct 5, 2023 at 8:30 AM Kate Hsuan  wrote:
> > > >... By
> > > > integrating power-profiles-daemon with tuned, the user can get extra
> > > > features to finetune the system, and the basic feature provided by ppd
> > > > can be used according to the user's demand. It also can reduce the
> > > > efforts of the maintainer.
> > > ...
> > > > Moreover, the detailed change proposal can be found here.
> > > > https://fedoraproject.org/wiki/Changes/TunedReplacesPower-profiles-daemon
> > >
> > > I just noticed that the change proposal contains the line:
> > >
> > > "We expected that the user can set those profile, tuned provided
> > > through gnome-control-panel. To minimize the information to the user,
> > > the power panel would provide a simple and advanced mode to show the
> > > power profiles. If the users want to finetune the system, they can
> > > switch to the advanced mode themselves."
> > >
> > > It's a bit unclear if this is a definite plan, a requirement, or more
> > > of a speculative ambition. However, I should probably be clear that
> > > from a GNOME design perspective, an advanced power profile settings
> > > mode would likely be a tough sell. Exposing arbitrary user-defined
> > > profiles would also pose some challenges which it might be difficult
> > > to overcome.
> > >
> > - Simple (Basic) mode is the original UX design of the power panel so
> > we don't need to change or redesign it.
> > - The advanced mode only shows the profile that tuned provides and the
> > profile can be filtered based on the system architecture or platform
> > model (Dell, Lenovo...etc). It is my thought and any kinds of ideas
> > are welcome.
> >
> > Since there are many kinds of profiles provided by tuned, for example,
> > VM-specific profiles and profiles for Intel features...etc., that
> > gives us more room to think about how the UI can be improved. In this
> > proposal, I listed the probabilities of UX changes to show how we can
> > propose a new UX for the power panel. If it is difficult to achieve,
> > the advanced mode can be dropped, and seek for alternative solutions.
> > :)
> > For the short-term plan, we would like to address the integration with
> > tuned. The best result of the first step is that power-profiles-daemon
> > is replaced by tuned and all the applications, such as gnome, kde,
> > sysprof...etc run correctly. Then, we will start to think about how
> > the UX can be improved or an alternative solution to set up the
> > advanced tuned profiles.
> >
> > > If this change proposal does require UXD changes to GNOME, then I'd
> > > suggest reaching out to us in advance to discuss them.
> >  Okay. :)
> >
>
> I strongly recommend you reach out to the KDE folks as well. The
> Visual Design Group is a good starting point[1] for discussing the UX
> for tuned in KDE Plasma. A Matrix account is required to interact with
> most of the KDE folks, but you should already have one through
> chat.fedoraproject.org if you don't already have one from elsewhere.
>
> I suspect many of your simple/advanced UX ideas will be fine, but need
> to be refined with the VDG to figure out how it should be done.
>
> From the KDE side, we are not strictly speaking, married to the
> power-profiles-daemon concept. And the idea of having IHVs actually
> provide useful energy tuning profiles so that battery life can be
> further extended (thus supplanting tlp as well) is highly appealing.
>
> [1]: https://matrix.to/#/#visualdesigngroup:kde.org
>
>
>
>
> --
> 真実はいつも一つ！/ Always, there's only one truth!
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam, report it: 
> https://pagure.io/fedora-infrastructure/new_issue



-- 
BR,
Kate
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: