[Bug 2179146] New: python-pandas-2.0.0rc1 is available
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2179146
Bug ID: 2179146
Summary: python-pandas-2.0.0rc1 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: python-pandas
Keywords: FutureFeature, Triaged
Assignee: jonathan(a)almalinux.org
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: epel-packagers-sig(a)lists.fedoraproject.org,
jonathan(a)almalinux.org, mail(a)kushaldas.in,
neuro-sig(a)lists.fedoraproject.org, orion(a)nwra.com,
python-packagers-sig(a)lists.fedoraproject.org,
sergio.pasra(a)gmail.com, tomspur(a)fedoraproject.org,
wfp5p(a)worldbroken.com
Target Milestone: ---
Classification: Fedora
Releases retrieved: 2.0.0rc1
Upstream release that is considered latest: 2.0.0rc1
Current version/release in rawhide: 1.5.3-1.fc39
URL: http://pandas.pydata.org/
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...
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/7578/
To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/python-pandas
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2179146
2 months, 1 week
[Bug 2183119] New: FTBFS with autoconf 2.72/2.73
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2183119
Bug ID: 2183119
Summary: FTBFS with autoconf 2.72/2.73
Product: Fedora
Version: rawhide
OS: All
Status: NEW
Component: ImageMagick
Assignee: luya_tfz(a)thefinalzone.net
Reporter: fberat(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: blaise(a)gmail.com, davide(a)cavalca.name,
epel-packagers-sig(a)lists.fedoraproject.org,
fedora(a)famillecollet.com, luya_tfz(a)thefinalzone.net,
michel(a)michel-slm.name, ngompa13(a)gmail.com,
pampelmuse(a)gmx.at, sergio(a)serjux.com
Target Milestone: ---
Classification: Fedora
Autoconf 2.72 (or 2.73) seems to be under preparation upstream, I therefore
started to build dependent components against the pre-release [1] to verify
that they can be built once it lands in Fedora.
Your component fails to build with the new version of autoconf, due to the
following error:
configure:4837: error: possibly undefined macro:
_AC_SYS_LARGEFILE_TEST_INCLUDES
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
autoreconf: error: /usr/bin/autoconf failed with exit status: 1
Unfortunately, this can't be fixed with an autoreconf, an update of the files
provided by gnulib are necessary.
These files are usually added during the bootstrap of the source code, which is
done to generate the release tarball.
Please forward this to the community, and update the component accordingly.
[1] https://lists.gnu.org/archive/html/autoconf/2023-03/msg00020.html
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2183119
2 months, 2 weeks
[Bug 2172727] New: F38FailsToInstall: python3-cle
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2172727
Bug ID: 2172727
Summary: F38FailsToInstall: python3-cle
Product: Fedora
Version: 38
Status: NEW
Component: python-cle
Assignee: redhat(a)flyn.org
Reporter: fti-bugs(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: epel-packagers-sig(a)lists.fedoraproject.org,
mail(a)fabian-affolter.ch, redhat(a)flyn.org
Blocks: 2117177 (F38FailsToInstall)
Target Milestone: ---
Classification: Fedora
Hello,
Please note that this comment was generated automatically by
https://pagure.io/releng/blob/main/f/scripts/ftbfs-fti/follow-policy.py
If you feel that this output has mistakes, please open an issue at
https://pagure.io/releng/
Your package (python-cle) Fails To Install in Fedora 38:
can't install python3-cle:
- nothing provides python3.11dist(pyvex) = 9.0.9572 needed by
python3-cle-9.0.9572-4.fc37.noarch
If you know about this problem and are planning on fixing it, please
acknowledge so by setting the bug status to ASSIGNED. If you don't have time to
maintain this package, consider orphaning it, so maintainers of dependent
packages realize the problem.
If you don't react accordingly to the policy for FTBFS/FTI bugs
(https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fai...),
your package may be orphaned in 8+ weeks.
P.S. The data was generated solely from koji buildroot, so it might be newer
than the latest compose or the content on mirrors. To reproduce, use the
koji/local repo only, e.g. in mock:
$ mock -r fedora-38-x86_64 --config-opts mirrored=False install python3-cle
P.P.S. If this bug has been reported in the middle of upgrading multiple
dependent packages, please consider using side tags:
https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#updating-inter...
Thanks!
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=2117177
[Bug 2117177] Fedora 38 Fails To install Tracker
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2172727
2 months, 3 weeks
[Bug 2172728] New: F38FailsToInstall: python3-pyvex
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2172728
Bug ID: 2172728
Summary: F38FailsToInstall: python3-pyvex
Product: Fedora
Version: 38
Status: NEW
Component: python-pyvex
Assignee: redhat(a)flyn.org
Reporter: fti-bugs(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: epel-packagers-sig(a)lists.fedoraproject.org,
mail(a)fabian-affolter.ch, redhat(a)flyn.org
Blocks: 2117177 (F38FailsToInstall)
Target Milestone: ---
Classification: Fedora
Hello,
Please note that this comment was generated automatically by
https://pagure.io/releng/blob/main/f/scripts/ftbfs-fti/follow-policy.py
If you feel that this output has mistakes, please open an issue at
https://pagure.io/releng/
Your package (python-pyvex) Fails To Install in Fedora 38:
can't install python3-pyvex:
- nothing provides python3.11dist(archinfo) = 9.2.32 needed by
python3-pyvex-9.2.32-2.fc38.x86_64
If you know about this problem and are planning on fixing it, please
acknowledge so by setting the bug status to ASSIGNED. If you don't have time to
maintain this package, consider orphaning it, so maintainers of dependent
packages realize the problem.
If you don't react accordingly to the policy for FTBFS/FTI bugs
(https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fai...),
your package may be orphaned in 8+ weeks.
P.S. The data was generated solely from koji buildroot, so it might be newer
than the latest compose or the content on mirrors. To reproduce, use the
koji/local repo only, e.g. in mock:
$ mock -r fedora-38-x86_64 --config-opts mirrored=False install
python3-pyvex
P.P.S. If this bug has been reported in the middle of upgrading multiple
dependent packages, please consider using side tags:
https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#updating-inter...
Thanks!
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=2117177
[Bug 2117177] Fedora 38 Fails To install Tracker
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2172728
2 months, 3 weeks
[Bug 2184830] New: xscreensaver-settings or xscreensaver-demo fails to start on X error
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2184830
Bug ID: 2184830
Summary: xscreensaver-settings or xscreensaver-demo fails to
start on X error
Product: Fedora
Version: 37
Hardware: x86_64
OS: Linux
Status: NEW
Component: xscreensaver
Severity: medium
Assignee: mtasaka(a)tbz.t-com.ne.jp
Reporter: martin.bukatovic(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: cheese(a)nosuchhost.net,
epel-packagers-sig(a)lists.fedoraproject.org,
jonathan(a)almalinux.org, lkundrak(a)v3.sk,
mtasaka(a)tbz.t-com.ne.jp
Target Milestone: ---
Classification: Fedora
Description of problem
======================
xscreensaver-demo or xscreensaver-settings fails to start when executed from a
xmonad session, which prevents user to configure it directly
Version-Release number of selected component
============================================
```
$ rpm -qa 'xscreensaver*'
xscreensaver-gl-base-6.06-3.fc37.x86_64
xscreensaver-extras-base-6.06-3.fc37.x86_64
xscreensaver-gl-extras-6.06-3.fc37.x86_64
xscreensaver-base-6.06-3.fc37.x86_64
xscreensaver-extras-6.06-3.fc37.x86_64
xscreensaver-6.06-3.fc37.x86_64
$ rpm -q xorg-x11-server-Xorg
xorg-x11-server-Xorg-1.20.14-21.fc37.x86_64
```
How reproducible
================
100%
Steps to Reproduce
==================
1. select xmonad as a window manger and login
2. try to run xscreensaver-settings or xscreensaver-demo
Actual results
==============
```
$ xscreensaver-settings
xscreensaver-settings: 23:29:20.81: Theme parsing error: colors.css:71:44:
Invalid number for color value
xscreensaver-settings: 23:29:20.81: Theme parsing error: colors.css:72:44:
Invalid number for color value
xscreensaver-settings: 23:29:20.81: Theme parsing error: colors.css:74:53:
Invalid number for color value
xscreensaver-settings: 23:29:20.81: Theme parsing error: colors.css:75:53:
Invalid number for color value
xscreensaver-settings: 23:29:20.81: Theme parsing error: colors.css:76:56:
Invalid number for color value
xscreensaver-settings: 23:29:20.81: Theme parsing error: colors.css:77:65:
Invalid number for color value
xscreensaver-settings: 23:29:21.11: X error:
xscreensaver-settings: Failed request: BadMatch (invalid parameter
attributes)
xscreensaver-settings: Major opcode: 42 (X_SetInputFocus)
xscreensaver-settings: Resource id: 0x3000007
xscreensaver-settings: Serial number: 454 / 456
```
Expected results
================
xscreensaver-settings starts without any error
Additional info
===============
Fortunately `xscreensaver-command -lock` works without any problems.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2184830
2 months, 3 weeks