Re: Need assistance to package MaterialX

2024-01-27 Thread Luya Tshimbalanga


On 2024-01-27 01:04, Elliott Sales de Andrade wrote:

On Sat, Jan 27, 2024 at 1:58 AM Luya Tshimbalanga
  wrote:

Hello team,

I attempt to build MaterialX, an optional requirement for Blender 4.x but hit 
an interesting issue with RPATH (partially resolved).
An example 
onhttps://download.copr.fedorainfracloud.org/results/@designsuite/blender/fedora-39-x86_64/06966310-materialx/builder-live.log.gz
shows the path on /usr/ rather than say /usr/share/materialx

This doesn't have anything to do with RPATH. Upstream's build is just
broken for FHS layout.

For example, the "root-level documents" are installed here:
https://github.com/AcademySoftwareFoundation/MaterialX/blob/2f169d152f295114efe982ab06a74bfd930bb540/CMakeLists.txt#L354-L379
This just installs documentation to ".", which is /usr.


Following the workaround from Arch Linux, manually creating the 
directory helped.  With some tweaks, the build was successful abet 
disabling python for the time being:


https://copr.fedorainfracloud.org/coprs/g/designsuite/blender/build/6967755/





--
Luya Tshimbalanga
Fedora Design Team
Fedora Design Suite maintainer
--
___
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 8 updates-testing report

2024-01-27 Thread updates
The following Fedora EPEL 8 Security updates need testing:
 Age  URL
  24  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-3a29f0d349   
python-paramiko-2.12.0-2.el8
   3  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-76443fce3f   
indent-2.2.13-5.el8
   3  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-272d6fcaca   
atril-1.26.2-1.el8
   1  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-93d34f40f0   
chromium-121.0.6167.85-1.el8


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

inih-58-1.el8
mingw-libidn2-2.3.7-1.el8
openscap-report-0.2.7-1.el8
python-apprise-1.7.2-1.el8

Details about builds:



 inih-58-1.el8 (FEDORA-EPEL-2024-348e6822a6)
 Simple INI file parser library

Update Information:

# inih v58* [oss-fuzz] fuzzing support   * [Fuzzing] fix harness   *
[Fuzzing] using cifuzz for PR   * Specify C++11 std in meson build   * Add
`ini_` prefix even to static names so inih can be used as an `#include`

ChangeLog:

* Sat Jan 27 2024 Robert Scheck  - 58-1
- New upstream release 58 (#2260272)
* Wed Jan 24 2024 Fedora Release Engineering  - 57-5
- Rebuilt for https://fedoraproject.org/wiki/Fedora_40_Mass_Rebuild
* Sat Jan 20 2024 Fedora Release Engineering  - 57-4
- Rebuilt for https://fedoraproject.org/wiki/Fedora_40_Mass_Rebuild
* Sat Dec  2 2023 Daan De Meyer  - 57-3
- Move INIReader C++ library to inih-cpp subpackage
* Thu Jul 20 2023 Fedora Release Engineering  - 57-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_39_Mass_Rebuild

References:

  [ 1 ] Bug #2260272 - inih-58 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2260272




 mingw-libidn2-2.3.7-1.el8 (FEDORA-EPEL-2024-c1428459fb)
 MinGW Windows Internationalized Domain Name 2008 support library

Update Information:

# libidn2 2.3.7 (2024-01-27)- Really include `tests/standalone.sh` in
tarball.  # libidn2 2.3.6 (2024-01-27)- Bump libtool version numbers to
reflect API/ABI addition.- Include `tests/standalone.sh` in tarball.  #
libidn2 2.3.5 (2024-01-27)- Declaration of future API/ABI backwards
compatibility stability.  GNU libc `dlopen` libidn2 and use the name
`libidn2.so.0` for this.  Upstream believes that it will be too challenging to
ever do hard ABI break that for normal libraries is justified to remove
deprecated APIs.  Thus upstream decided that they will support the current ABI
for a long time.  Of course, if really convincing arguments for doing a ABI
break appears in the future upstream may re-consider, but take this as a
declaration of intent of will and that future ABI breaks should be discussed and
co-ordinated with the glibc team first.- Add public APIs for raw Punycode
encoding/decoding.  Normal applications rarely need this, but it cleans up
the code and allow for external testing of the APIs, and resolve
https://gitlab.com/libidn/libidn2/-/issues/80 due to earlier use of weak symbols
for internal symbols `_idn2_punycode_encode` and `_idn2_punycode_decode`.
Upstream will support these internal symbols for backwards compatibility.  This
allows a clean migration path for code that is still using the internal names.
- Bump required gettext version to 0.19.8 for musl-libc.- Un-deprecate
`idn2_to_ascii_4i` and make it `NUL` terminate output.  The API
`idn2_to_ascii_4i` was deprecated in version 2.1.1 released in 2019-02-08.  In
that release, the API was also modified to not `NUL`-terminate the output.  That
is contrary to the old libidn2 behaviour, the behaviour of libidn's API
`idna_to_ascii_4i`, and the API documentation for the function.  Since upstream
is not likely to ever break backwards API/ABI compatibility in libidn2, and the
deprecated gaurds leads to some trouble (see report in
https://gitlab.com/libidn/libidn2/-/merge_requests/93 upstream decided to un-
deprecate this function, as supporting it is not costly and the majority of code
that cares about conformance has likely been modified.  This will fix the error
code and `NUL` termination report in
https://gitlab.com/libidn/libidn2/-/issues/100.  Upstream still encourage you to
use the replacement API/ABI idn2_to_ascii_4i2 instead, when appropriate.-
Compiler warning improvements.  As before, compiler warnings are enabled by
default.  You may disable them using `./configure --disable-gcc-warnings` or
turn them into fatal errors using `./configure 

Re: HEADS UP: update to tesseract-5.3.4

2024-01-27 Thread Yaakov Selkowitz
On Sat, 2024-01-27 at 23:20 +0100, Sandro Mani wrote:
> I'll be updating to tesseract-5.3.4 in rawhide shortly, which carries
> a 
> soname bump (despite it being a minor version, unfortunately upstream
> versions the SO with the package version). I'll rebuild the following
> dependent packages:
> 
> ffmpeg
> gimagereader
> mupdf
> opencv
> python-PyMuPDF
> qpdfview
> R-tesseract
> skanpage
> zathura-pdf-mupdf

Since it's not clear from your email, please be sure to do this in a
side tag.

-- 
Yaakov Selkowitz
Principal Software Engineer - Emerging RHEL
Red Hat, Inc.
--
___
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 7 updates-testing report

2024-01-27 Thread updates
The following Fedora EPEL 7 Security updates need testing:
 Age  URL
   3  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-4ff425606f   
openssl11-1.1.1k-7.el7


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

clojure-1.8.0-2.el7
libidn2-2.3.7-1.el7

Details about builds:



 clojure-1.8.0-2.el7 (FEDORA-EPEL-2024-54270ec4b3)
 A dynamic programming language that targets the Java Virtual Machine

Update Information:

Security fix for CVE-2017-20189

ChangeLog:

* Sat Jan 27 2024 Markku Korkeala  - 1:1.8.0-2
- Add patch clj-2204 to mitigate CVE-2017-20189.
* Thu Apr  2 2020 Markku Korkeala  - 1:1.8.0-1
- New upstream release.
- Replace add_maven_depmap macros with mvn_artifact and mvn_install

References:

  [ 1 ] Bug #2259513 - CVE-2017-20189 clojure: executes arbitrary code upon 
deserialization
https://bugzilla.redhat.com/show_bug.cgi?id=2259513




 libidn2-2.3.7-1.el7 (FEDORA-EPEL-2024-695ec45c0f)
 Library to support IDNA2008 internationalized domain names

Update Information:

# libidn2 2.3.7 (2024-01-27)- Really include `tests/standalone.sh` in
tarball.  # libidn2 2.3.6 (2024-01-27)- Bump libtool version numbers to
reflect API/ABI addition.- Include `tests/standalone.sh` in tarball.  #
libidn2 2.3.5 (2024-01-27)- Declaration of future API/ABI backwards
compatibility stability.  GNU libc `dlopen` libidn2 and use the name
`libidn2.so.0` for this.  Upstream believes that it will be too challenging to
ever do hard ABI break that for normal libraries is justified to remove
deprecated APIs.  Thus upstream decided that they will support the current ABI
for a long time.  Of course, if really convincing arguments for doing a ABI
break appears in the future upstream may re-consider, but take this as a
declaration of intent of will and that future ABI breaks should be discussed and
co-ordinated with the glibc team first.- Add public APIs for raw Punycode
encoding/decoding.  Normal applications rarely need this, but it cleans up
the code and allow for external testing of the APIs, and resolve
https://gitlab.com/libidn/libidn2/-/issues/80 due to earlier use of weak symbols
for internal symbols `_idn2_punycode_encode` and `_idn2_punycode_decode`.
Upstream will support these internal symbols for backwards compatibility.  This
allows a clean migration path for code that is still using the internal names.
- Bump required gettext version to 0.19.8 for musl-libc.- Un-deprecate
`idn2_to_ascii_4i` and make it `NUL` terminate output.  The API
`idn2_to_ascii_4i` was deprecated in version 2.1.1 released in 2019-02-08.  In
that release, the API was also modified to not `NUL`-terminate the output.  That
is contrary to the old libidn2 behaviour, the behaviour of libidn's API
`idna_to_ascii_4i`, and the API documentation for the function.  Since upstream
is not likely to ever break backwards API/ABI compatibility in libidn2, and the
deprecated gaurds leads to some trouble (see report in
https://gitlab.com/libidn/libidn2/-/merge_requests/93 upstream decided to un-
deprecate this function, as supporting it is not costly and the majority of code
that cares about conformance has likely been modified.  This will fix the error
code and `NUL` termination report in
https://gitlab.com/libidn/libidn2/-/issues/100.  Upstream still encourage you to
use the replacement API/ABI idn2_to_ascii_4i2 instead, when appropriate.-
Compiler warning improvements.  As before, compiler warnings are enabled by
default.  You may disable them using `./configure --disable-gcc-warnings` or
turn them into fatal errors using `./configure --enable-gcc-warnings=error` to
add `-Werror` and sensible `-Wno-error='s`.  Based on gnulib's manywarnings, see
https://www.gnu.org/software/gnulib//manual/html_node/manywarnings.html.-
tests: Added script `tests/standalone.sh` suitable for integrators.  The
main purpose is to test a system-installed libidn2 library and `idn2` tool,
suitable for distributor checking (a'la Debian's autopkgtest/debci).  It may
also be used to test a newly built libidn2 outside the usual `make check`
infrastructure.  To check that your system libidn2 library and `idn2` tool is
working, invoke the script with `srcdir` as an environment variable indicating
where it can be find the source code for libidn2's `tests/` directory (it will
use the directory name where the script is by default): 

[Bug 2260595] perl-YAML-LibYAML-0.89 is available

2024-01-27 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2260595



--- Comment #6 from Fedora Update System  ---
FEDORA-2024-261f0e86ef has been pushed to the Fedora 38 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh
--advisory=FEDORA-2024-261f0e86ef`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2024-261f0e86ef

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


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202260595%23c6
--
___
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 2260595] perl-YAML-LibYAML-0.89 is available

2024-01-27 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2260595



--- Comment #5 from Fedora Update System  ---
FEDORA-2024-cf5d2a2847 has been pushed to the Fedora 39 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh
--advisory=FEDORA-2024-cf5d2a2847`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2024-cf5d2a2847

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


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

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


HEADS UP: update to tesseract-5.3.4

2024-01-27 Thread Sandro Mani

Hi

I'll be updating to tesseract-5.3.4 in rawhide shortly, which carries a 
soname bump (despite it being a minor version, unfortunately upstream 
versions the SO with the package version). I'll rebuild the following 
dependent packages:


ffmpeg
gimagereader
mupdf
opencv
python-PyMuPDF
qpdfview
R-tesseract
skanpage
zathura-pdf-mupdf

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

2024-01-27 Thread Peter Robinson
On Wed, 24 Jan 2024 at 16:39, 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 5 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
> 
> cl-asdf green
> erlang-jose bowlofeggs, erlang-maint-sig, jcline, 
> peter
> fwtsbenzea

I worked around the build failure for ftbfs and updated this package,
it doesn't like parallel builds, there's upstream reports but it
appears not to be getting attention from the maintainers even though
they're doing newer releases.

> ghdlsailer
> git-secrets  keesdejong
> golang-github-acme-lego  eclipseo, go-sig
> golang-github-eclesh-welford abulimov, dcavalca, go-sig
> golang-github-gatherstars-com-jwzeclipseo, go-sig
> golang-github-genuinetools-pkg   eclipseo, go-sig
> golang-github-gobs-prettyeclipseo, go-sig
> golang-github-google-gopacketgo-sig, salimma
> 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
> kdevelop-pg-qt   jgrulich, kde-sig, rdieter, than
> libdeltacloudclalance
> libva-v4l2-request   kwizart, rathann
> lmms thm
> lxc  hguemar, sagarun, thm
> mingw-clucenegreghellings
> mingw-cppunitkwizart
> mingw-dirac  kwizart
> mingw-speexdsp   janisozaur
> nbd-runner   xiubli
> nodejs-generic-pool  patches, piotrp
> ofononjha, thunderbirdtr
> openni-primesensecottsay, jkastner, rmattes
> pcmciautils  harald
> pesign-test-app  javierm, nfrayer, pjones, rwood
> pthsem   ixs
> rust-drg jbtrystram, rust-sig
> telepathy-gabble aperezbios
> yaksazbyszek
>
> The following packages require above mentioned packages:
> Depending on: cl-asdf (5)
> common-lisp-controller (maintained by: green)
> common-lisp-controller-7.4-26.fc39.noarch requires cl-asdf
>
> emacs-slime (maintained by: bkreuter, salimma)
> emacs-slime-2:2.28-2.fc39.noarch requires 
> common-lisp-controller
> emacs-slime-2:2.28-2.fc39.src requires common-lisp-controller
>
> sbcl (maintained by: green, rdieter)
> sbcl-2.3.11-1.fc40.src requires common-lisp-controller
> sbcl-2.3.11-1.fc40.x86_64 requires common-lisp-controller
>
> maxima (maintained by: jamatos, rdieter)
> maxima-5.45.1-6.fc40.src requires sbcl
>
> wxMaxima (maintained by: jamatos, rdieter)
> wxMaxima-20.12.1-10.fc39.x86_64 requires maxima
>
> Depending on: erlang-jose (1)
> erlang-p1_acme (maintained by: bowlofeggs, erlang-maint-sig, peter)
>

Re: Need assistance to package MaterialX

2024-01-27 Thread Luya Tshimbalanga


On 2024-01-27 01:04, Elliott Sales de Andrade wrote:

On Sat, Jan 27, 2024 at 1:58 AM Luya Tshimbalanga
  wrote:

Hello team,

I attempt to build MaterialX, an optional requirement for Blender 4.x but hit 
an interesting issue with RPATH (partially resolved).
An example 
onhttps://download.copr.fedorainfracloud.org/results/@designsuite/blender/fedora-39-x86_64/06966310-materialx/builder-live.log.gz
shows the path on /usr/ rather than say /usr/share/materialx

This doesn't have anything to do with RPATH. Upstream's build is just
broken for FHS layout.

For example, the "root-level documents" are installed here:
https://github.com/AcademySoftwareFoundation/MaterialX/blob/2f169d152f295114efe982ab06a74bfd930bb540/CMakeLists.txt#L354-L379
This just installs documentation to ".", which is /usr.

That is the missing link.

And the same for resources:
https://github.com/AcademySoftwareFoundation/MaterialX/blob/2f169d152f295114efe982ab06a74bfd930bb540/resources/CMakeLists.txt#L3
which doesn't add datadir, but just goes to top-level "resources".

This should probably be reported upstream.

Agreed. Once addressed, perhaps submit a patch. I will update the status.

--
Luya Tshimbalanga
Fedora Design Team
Fedora Design Suite maintainer
--
___
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: Need assistance to package MaterialX

2024-01-27 Thread Luya Tshimbalanga


On 2024-01-27 00:46, Leigh Scott wrote:

Have you looked at other distros to see how they worked around the flaws in the 
upstream code?

  
https://gitlab.archlinux.org/archlinux/packaging/packages/materialx/-/blob/main/PKGBUILD?ref_type=heads#L32
--


Yes, I look at Arch Linux build. Setting the right path on cmake setting 
seems to address most of the issues like:


'''

   -DMATERIALX_INSTALL_INCLUDE_PATH=%{_includedir} \
    -DMATERIALX_INSTALL_LIB_PATH=%{_libdir} \
    -DMATERIALX_INSTALL_STDLIB_PATH=%{_datadir}/%{name

'''

 Now the path
for the workaround from Arch Linux parameters failed. Upstream code is 
indeed a mess. I will update the status.



--
Luya Tshimbalanga
Fedora Design Team
Fedora Design Suite maintainer
--
___
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 2259131] perl-gettext-1.07-28.fc40 FTBFS: tests fail

2024-01-27 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2259131

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version||perl-gettext-1.07-31.fc40
 Resolution|RAWHIDE |ERRATA



--- Comment #5 from Fedora Update System  ---
FEDORA-2024-2bc1ca7840 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=2259131

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


[Bug 2259131] perl-gettext-1.07-28.fc40 FTBFS: tests fail

2024-01-27 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2259131



--- Comment #4 from Fedora Update System  ---
FEDORA-2024-2bc1ca7840 has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-2bc1ca7840


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202259131%23c4
--
___
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 2259131] perl-gettext-1.07-28.fc40 FTBFS: tests fail

2024-01-27 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2259131

Ralf Corsepius  changed:

   What|Removed |Added

 Resolution|--- |RAWHIDE
 Status|NEW |CLOSED
Last Closed||2024-01-27 18:10:20



--- Comment #3 from Ralf Corsepius  ---
(In reply to Petr Pisar from comment #2)
> I recommend build-requiring glibc-langpack-en and setting locale to
> en_US.UTF-8 as a fix.

That's what I did.


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

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

2024-01-27 Thread kevin
On Sat, Jan 27, 2024 at 03:39:06PM +0900, Kan-Ru Chen wrote:
> Hello Fedora,
> 
> I have been lurking around the mailing lists, forum, and chats. It's
> time for a self introduction! My first distribution was CLE 0.9 which
> was based on Red Hat 6.1. Later I have switched between many
> distributions then settled on Debian and became a DD. I was interested
> by Fedora again when packaging a Flatpak application and came to know
> the Silverblue variant.
> 
> I'm now using Silverblue as my daily driver and CoreOS for some of my
> hosting needs. I'm looking forward to contribute to Fedora especially
> in the i18n area and beta testing.

Welcome!

You may be interested in the #i18n:fedoraproject.org and
#quality:fedoraproject.org matrix channels if you haven't already seen
them. :)

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 2260642] New: perl-URI-5.25 is available

2024-01-27 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2260642

Bug ID: 2260642
   Summary: perl-URI-5.25 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-URI
  Keywords: FutureFeature, Triaged
  Assignee: jples...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: jples...@redhat.com, ka...@ucw.cz, mspa...@redhat.com,
p...@city-fan.org, perl-devel@lists.fedoraproject.org,
rhug...@redhat.com, rstr...@redhat.com
  Target Milestone: ---
Classification: Fedora



Releases retrieved: 5.25
Upstream release that is considered latest: 5.25
Current version/release in rawhide: 5.24-1.fc40
URL: https://metacpan.org/dist/URI/

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


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


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202260642%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 2260487] Upgrade perl-IPC-Run3 to 0.049

2024-01-27 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2260487

Ralf Corsepius  changed:

   What|Removed |Added

 Resolution|--- |RAWHIDE
 Status|NEW |CLOSED
Last Closed||2024-01-27 16:25:37




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2260487
--
___
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 1731718] perl-Convert-Color-0.17-3.fc40 FTBFS: No match for argument: /usr/share/X11/rgb.txt

2024-01-27 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1731718

Ralf Corsepius  changed:

   What|Removed |Added

 Status|ASSIGNED|CLOSED
 Resolution|--- |RAWHIDE
Last Closed|2021-05-25 15:01:58 |2024-01-27 16:24:27




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1731718
--
___
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 1731718] perl-Convert-Color-0.17-3.fc40 FTBFS: No match for argument: /usr/share/X11/rgb.txt

2024-01-27 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1731718

Ralf Corsepius  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED



--- Comment #10 from Ralf Corsepius  ---
(In reply to Petr Pisar from comment #9)
> The file dependency in not supported by Fedora build system anymore and as a
> result perl-Convert-Color-0.17-3.fc40 fails to build in Fedora 40:

Well, this is a "very friendly" description of the packaging regressions having
been introduced into dnf ;-)

I'll try to add a (IMO: ugly and stupid) hack to work around this mess.


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%201731718%23c10
--
___
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 2260595] perl-YAML-LibYAML-0.89 is available

2024-01-27 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2260595



--- Comment #3 from Fedora Update System  ---
FEDORA-2024-261f0e86ef has been submitted as an update to Fedora 38.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-261f0e86ef

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


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202260595%23c4
--
___
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 2260595] perl-YAML-LibYAML-0.89 is available

2024-01-27 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2260595



--- Comment #3 from Fedora Update System  ---
FEDORA-2024-261f0e86ef has been submitted as an update to Fedora 38.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-261f0e86ef


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202260595%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 2260595] perl-YAML-LibYAML-0.89 is available

2024-01-27 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2260595

Fedora Update System  changed:

   What|Removed |Added

 Resolution|--- |ERRATA
 Status|MODIFIED|CLOSED
   Fixed In Version||perl-YAML-LibYAML-0.89-1.fc
   ||40
Last Closed||2024-01-27 14:54:03



--- Comment #2 from Fedora Update System  ---
FEDORA-2024-433ece511d 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=2260595

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202260595%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 2260595] perl-YAML-LibYAML-0.89 is available

2024-01-27 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2260595

Fedora Update System  changed:

   What|Removed |Added

 Status|NEW |MODIFIED



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


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

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

2024-01-27 Thread Dominik 'Rathann' Mierzejewski
Hello, Jacek!

On Friday, 26 January 2024 at 20:46, Jacek Migacz wrote:
> Dear Community!
> 
> My name is Jacek Migacz; a software engineer from Poland.
> I'm currently maintaining curl and emacs on Red Hat Enterprise Linux.
> I am eager to learn from the collective wisdom of the community and
> contribute in meaningful ways.

Welcome to Fedora! Feel free to drop by our official room on Matrix[1]
and/or IRC[2] to say hello.

[1] #pl:fedoraproject.org
[2] #fedora-pl

Regards,
Dominik
-- 
Fedora https://fedoraproject.org
There should be a science of discontent. People need hard times and
oppression to develop psychic muscles.
-- from "Collected Sayings of Muad'Dib" by the Princess Irulan
--
___
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: Need assistance to package MaterialX

2024-01-27 Thread Elliott Sales de Andrade
On Sat, Jan 27, 2024 at 1:58 AM Luya Tshimbalanga
 wrote:
>
> Hello team,
>
> I attempt to build MaterialX, an optional requirement for Blender 4.x but hit 
> an interesting issue with RPATH (partially resolved).
> An example on 
> https://download.copr.fedorainfracloud.org/results/@designsuite/blender/fedora-39-x86_64/06966310-materialx/builder-live.log.gz
> shows the path on /usr/ rather than say /usr/share/materialx

This doesn't have anything to do with RPATH. Upstream's build is just
broken for FHS layout.

For example, the "root-level documents" are installed here:
https://github.com/AcademySoftwareFoundation/MaterialX/blob/2f169d152f295114efe982ab06a74bfd930bb540/CMakeLists.txt#L354-L379
This just installs documentation to ".", which is /usr.

And the same for resources:
https://github.com/AcademySoftwareFoundation/MaterialX/blob/2f169d152f295114efe982ab06a74bfd930bb540/resources/CMakeLists.txt#L3
which doesn't add datadir, but just goes to top-level "resources".

This should probably be reported upstream.

> The build is located on 
> https://copr.fedorainfracloud.org/coprs/g/designsuite/blender/build/6966310/ 
> including the spec file.
>
> Helps welcome!
>
> Luya

-- 
Elliott
--
___
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: Need assistance to package MaterialX

2024-01-27 Thread Leigh Scott
Have you looked at other distros to see how they worked around the flaws in the 
upstream code?

 
https://gitlab.archlinux.org/archlinux/packaging/packages/materialx/-/blob/main/PKGBUILD?ref_type=heads#L32
--
___
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