Re: Any advice on dealing with the issue of building package with side tag of f42-build-side-94214 on f41 branch

2024-08-15 Thread Felix Wang
Ohh, thanks for pointing the error as I misinterpreted the information. I have 
taken your advice.
-- 
___
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


Any advice on dealing with the issue of building package with side tag of f42-build-side-94214 on f41 branch

2024-08-15 Thread Felix Wang
The issue was also raised on releng issue of 
https://pagure.io/releng/issue/12262, but I do not know which place will be 
better on solving the issue. Anyway, I also posted the issue on the devel list 
here.

A few moments ago, I decided to update the deepin-dock to 6.0.37. So I should 
commit the changes to rawhide first and build the deepin-dock package with the 
side tag of f42-build-side-94214 on rawhide, which I accidentaly and wrongly 
committed to f41 branch first and build it with fedpkg build 
--target=f42-build-side-94214. [1,2] Here is the following output of related 
commands:
```
Uploading: /home/aurora/rpmbuild/SOURCES/dde-dock-6.0.37.tar.gz to 
https://src.fedoraproject.org/repo/pkgs/upload.cgi
Uploading: /home/aurora/rpmbuild/SOURCES/dde-dock-6.0.37.tar.gz
 100.0%
Source upload succeeded. Don't forget to commit the sources file
[f41 738011c] 6.0.37
 3 files changed, 71 insertions(+), 64 deletions(-)
Enumerating objects: 9, done.
Counting objects: 100% (9/9), done.
Delta compression using up to 20 threads
Compressing objects: 100% (5/5), done.
Writing objects: 100% (5/5), 1.48 KiB | 1.48 MiB/s, done.
Total 5 (delta 2), reused 0 (delta 0), pack-reused 0 (from 0)
remote: Emitting a message to the fedora-messaging message bus.
remote: * Publishing information for 1 commits
remote: Sending to redis to log activity and send commit notification emails
remote: * Publishing information for 1 commits
remote:   - to fedora-message
remote: 2024-08-15 12:17:13,346 [WARNING] pagure.lib.notify: pagure is about to 
send a message that has no schemas: pagure.git.receive
remote: 
remote: Create a pull-request for f41
remote:https://src.fedoraproject.org/rpms/deepin-dock/diff/rawhide..f41
remote: 
To ssh://pkgs.fedoraproject.org/rpms/deepin-dock
   5497530..738011c  f41 -> f41
Building deepin-dock-6.0.37-1.fc41 for f42-build-side-94214
Created task: 121981027
Task info: https://koji.fedoraproject.org/koji/taskinfo?taskID=121981027
Watching tasks (this may be safely interrupted)...
121981027 build (f42-build-side-94214, 
/rpms/deepin-dock.git:738011ccf99afcdad24a24e6138d52f5640fed6d): free
121981027 build (f42-build-side-94214, 
/rpms/deepin-dock.git:738011ccf99afcdad24a24e6138d52f5640fed6d): free -> open 
(buildhw-a64-12.iad2.fedoraproject.org)
  121981059 buildSRPMFromSCM 
(/rpms/deepin-dock.git:738011ccf99afcdad24a24e6138d52f5640fed6d): free
```
The f41 branch is one commit ahead of rawhide branch, the koji build results 
showed it has built packages that has name, like 
deepin-dock-6.0.37-1.fc42.x86_64.rpm. The root.log file of koji build indicated 
it was built on f41.

[1] https://src.fedoraproject.org/rpms/deepin-dock/commits/rawhide
[2] https://src.fedoraproject.org/rpms/deepin-dock/commits/f41
[3] https://koji.fedoraproject.org/koji/taskinfo?taskID=121981027
-- 
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Fedora 41 Python 3.13 mass rebuild status

2024-06-15 Thread Felix Wang
Ok, thanks in advance, the bug was filed with gcc: 
https://bugzilla.redhat.com/show_bug.cgi?id=2292501
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Fedora 41 Python 3.13 mass rebuild status

2024-06-15 Thread Felix Wang
zxing-cpp rebuild failed only on s390x with the following error [1], any clue 
on how to resolve this?

```
[ 21%] Building CXX object 
core/CMakeFiles/ZXing.dir/src/PerspectiveTransform.cpp.o
cd 
/builddir/build/BUILD/zxing-cpp-2.2.1-build/zxing-cpp-2.2.1/redhat-linux-build/core
 && /usr/bin/g++ -DZXing_EXPORTS 
-I/builddir/build/BUILD/zxing-cpp-2.2.1-build/zxing-cpp-2.2.1/core/src 
-I/builddir/build/BUILD/zxing-cpp-2.2.1-build/zxing-cpp-2.2.1/redhat-linux-build/core
 -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe 
-Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 
-Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 
-fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 
-march=z13 -mtune=z14 -fasynchronous-unwind-tables -fstack-clash-protection -O2 
-g -DNDEBUG -std=c++17 -fPIC -DZXING_BUILD_READERS -DZXING_BUILD_WRITERS -Wall 
-Wextra -Wno-missing-braces -Werror=undef -Werror=return-type -ffloat-store -MD 
-MT core/CMakeFiles/ZXing.dir/src/PerspectiveTransform.cpp.o -MF 
CMakeFiles/ZXing.dir/src/PerspectiveTransform.cpp.o.d -o 
CMakeFiles/ZXing.dir/src/PerspectiveTransform.cpp.o -c 
/builddir/build/BUILD/zxing-cpp-2.2.1-build/zxing-cpp-2.2.1/core/src/PerspectiveTransform.cpp
/builddir/build/BUILD/zxing-cpp-2.2.1-build/zxing-cpp-2.2.1/core/src/PerspectiveTransform.cpp:
 In member function 
‘ZXing::PerspectiveTransform::operator()(ZXing::PointT) const’:
/builddir/build/BUILD/zxing-cpp-2.2.1-build/zxing-cpp-2.2.1/core/src/PerspectiveTransform.cpp:79:1:
 error: unrecognizable insn:
   79 | }
  | ^
(insn 16 15 17 2 (set (reg:V2DF 70 [ vect_p_x_26.112_35 ])
(vec_duplicate:V2DF (vec_select:DF (mem/c:V2DF (reg/f:DI 69) [69 
vect_p_x_26.111+0 S16 A64])
(parallel [
(const_int 0 [0])
] -1
 (nil))
*** WARNING *** there are active plugins, do not report this as a bug unless 
you can reproduce it without enabling any plugins.
Event| Plugins
PLUGIN_FINISH_UNIT   | annobin: Generate final annotations
PLUGIN_START_UNIT| annobin: Generate global annotations
PLUGIN_ALL_PASSES_START  | annobin: Generate per-function annotations
PLUGIN_ALL_PASSES_END| annobin: Register per-function end symbols
during RTL pass: vregs
/builddir/build/BUILD/zxing-cpp-2.2.1-build/zxing-cpp-2.2.1/core/src/PerspectiveTransform.cpp:79:1:
 internal compiler error: in extract_insn, at recog.cc:2812
[ 22%] Building CXX object core/CMakeFiles/ZXing.dir/src/ReadBarcode.cpp.o
cd 
/builddir/build/BUILD/zxing-cpp-2.2.1-build/zxing-cpp-2.2.1/redhat-linux-build/core
 && /usr/bin/g++ -DZXing_EXPORTS 
-I/builddir/build/BUILD/zxing-cpp-2.2.1-build/zxing-cpp-2.2.1/core/src 
-I/builddir/build/BUILD/zxing-cpp-2.2.1-build/zxing-cpp-2.2.1/redhat-linux-build/core
 -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe 
-Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 
-Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 
-fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 
-march=z13 -mtune=z14 -fasynchronous-unwind-tables -fstack-clash-protection -O2 
-g -DNDEBUG -std=c++17 -fPIC -DZXING_BUILD_READERS -DZXING_BUILD_WRITERS -Wall 
-Wextra -Wno-missing-braces -Werror=undef -Werror=return-type -ffloat-store -MD 
-MT core/CMakeFiles/ZXing.dir/src/ReadBarcode.cpp.o -MF 
CMakeFiles/ZXing.dir/src/ReadBarcode.cpp.o.d -o 
CMakeFiles/ZXing.dir/src/ReadBarcode.cpp.o -c 
/builddir/build/BUILD/zxing-cpp-2.2.1-build/zxing-cpp-2.2.1/core/src/ReadBarcode.cpp
Please submit a full bug report, with preprocessed source (by using 
-freport-bug).
See  for instructions.
[ 23%] Building CXX object 
core/CMakeFiles/ZXing.dir/src/ReedSolomonDecoder.cpp.o
cd 
/builddir/build/BUILD/zxing-cpp-2.2.1-build/zxing-cpp-2.2.1/redhat-linux-build/core
 && /usr/bin/g++ -DZXing_EXPORTS 
-I/builddir/build/BUILD/zxing-cpp-2.2.1-build/zxing-cpp-2.2.1/core/src 
-I/builddir/build/BUILD/zxing-cpp-2.2.1-build/zxing-cpp-2.2.1/redhat-linux-build/core
 -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe 
-Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 
-Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 
-fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 
-march=z13 -mtune=z14 -fasynchronous-unwind-tables -fstack-clash-protection -O2 
-g -DNDEBUG -std=c++17 -fPIC -DZXING_BUILD_READERS -DZXING_BUILD_WRITERS -Wall 
-Wextra -Wno-missing-braces -Werror=undef -Werror=return-type -ffloat-store -MD 
-MT core/CMakeFiles/ZXing.dir/src/ReedSolomonDecoder.cpp.o -MF 
CMakeFiles/ZXing.dir/src/ReedSolomonDecoder.cpp.o.d -o 
CMakeFiles/ZXing.dir/src/ReedSolomonDecoder.cpp.o -c 
/builddir/build/BUILD/zxing-cpp-2.2.1-build/zxing-cpp-2.2.1/core/src/ReedSolomonDecod

Re: Orphaning my packages: elvish, git-delta & dependencies

2024-04-22 Thread Felix Wang
Thanks, I opened a re-review request of elvish to follow package renaming 
process [1].
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2276356

[1] 
https://docs.fedoraproject.org/en-US/package-maintainers/Package_Renaming_Process/
--
___
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: Orphaning my packages: elvish, git-delta & dependencies

2024-04-21 Thread Felix Wang
I'd like to take elvish package, and I filed a review request of 
golang-pkg-nimblebun-lsp, which it is a dependency of elvish.
I would be grateful If you can take the review, or I can do the review swap if 
am familiar the knowledge with it.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2276326
--
___
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: update zxing-cpp to 2.2.1 in rawhide

2024-03-04 Thread Felix Wang
Sorry for the mistake. This update does not involve the soname bump.
--
___
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


update zxing-cpp to 2.2.1 in rawhide

2024-03-04 Thread Felix Wang
I would like update zxing-cpp to 2.2.1 in rawhide. [1] This update does involve 
the soname bump, so it does not need to rebuild the packages that depends on 
it. I did a test with zxing-cpp 2.2.1 on copr [2]. Only the libreoffice on 
ppc64le failed the build [3].

❯ dnf5 repoquery --releasever=rawhide --whatrequires zxing-cpp
Updating and loading repositories:
Repositories loaded.
kaidan-0:0.9.1-8.fc40.x86_64
kf5-kitinerary-0:23.08.5-1.fc41.i686
kf5-kitinerary-0:23.08.5-1.fc41.x86_64
kf5-prison-0:5.115.0-1.fc40.i686
kf5-prison-0:5.115.0-1.fc40.x86_64
kf6-prison-0:6.0.0-1.fc41.i686
kf6-prison-0:6.0.0-1.fc41.x86_64
kitinerary-0:24.02.0-1.fc41.i686
kitinerary-0:24.02.0-1.fc41.x86_64
libreoffice-core-1:24.2.1.1-5.fc41.x86_64
python3-zxing-cpp-0:2.0.0-6.fc40.x86_64
zxing-cpp-devel-0:2.0.0-6.fc40.i686
zxing-cpp-devel-0:2.0.0-6.fc40.x86_64

[1]: https://src.fedoraproject.org/rpms/zxing-cpp/pull-request/4
[2]: https://copr.fedorainfracloud.org/coprs/topazus/zxing-cpp-2.2.1/builds/
[3]: 
https://download.copr.fedorainfracloud.org/results/topazus/zxing-cpp-2.2.1/fedora-rawhide-ppc64le/07099284-libreoffice/builder-live.log.gz
--
___
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


Creation of new package repo failed, Invalid or expired token

2023-12-12 Thread Felix Wang
I opened an releng issue about this. [1] At the time of writing, I noticed that 
there is probably an similar issue of failure of package creation appeared. [2] 
Hope anyone can help me solve the problem, which maybe the cause of my personal 
issue, or other factors. Thanks in advance.

[1] https://pagure.io/releng/issue/11829
[2] https://pagure.io/releng/fedora-scm-requests/issue/58752
--
___
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: rawhide build errors on i686

2023-07-06 Thread Felix Wang
I also had the build error of `BuildrootError: could not init mock buildroot, 
mock exited with status 30`. [1, 2] May I ask how to resubmit the build?

[1] 
https://src.fedoraproject.org/rpms/draco/c/d5a8ed8e388001de0f87150b725222be55a4a038?branch=rawhide
[2] https://koji.fedoraproject.org/koji/taskinfo?taskID=102943314
___
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: Announcing fmt library soversion bump

2023-06-28 Thread Felix Wang
> FTBFS:
> contour-terminal

Applying the related upstream commit as the patch, the rebuild succeeded.

Ref: https://koji.fedoraproject.org/koji/taskinfo?taskID=102707247
___
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


How to correctly use Upstream release monitoring functionality?

2023-06-26 Thread Felix Wang
I see the Fedora documentation about Upstream release monitoring. First, add 
the project to Anitya and map it to the corresponding Fedora package, and 
secondly, enable the monitoring in its fedora-src repository. I have set these 
for cpr package, but I didn't receive the related message about its updating 
status. Could anyone can help me to explain and use this?

Ref:
https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring/
https://release-monitoring.org/project/66765/
https://src.fedoraproject.org/rpms/cpr
https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&classification=Fedora&product=Fedora&product=Fedora%20EPEL&component=cpr
___
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: [HEADS UP] Fedora 39 Python 3.12 rebuilds to start in a side tag this week

2023-06-16 Thread Felix Wang
Hi, I have the python-qcengine package, which is not rebuilt by python 3.12 yet.
https://src.fedoraproject.org/rpms/python-qcengine
___
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: Review of Python packages needed

2023-05-10 Thread Felix Wang
I'd like to take this two packages reviews and will review them in the next one 
or two days.
___
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: Anyone interested in packaging nim-lang?

2023-03-29 Thread Felix Wang
I also would like to get involved into the packaging of nim-lang. Although I 
maintain a few Fedora packages, my understanding of fedora rpm packaging and 
many other related knowledge, which I know a little about nim-lang,  may not 
statisfy the packaging of nim-lang, but I will have a try.
___
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


Review libunicode and contour-terminal

2023-03-04 Thread Felix Wang
Hi, I made the two review requests of libunicode and contour-terminal in order 
to add them to Fedora official repo. Does anyone can help me review the two 
packages? Any review swap will be fine if I can. Thanks.
ref: libunicode: https://bugzilla.redhat.com/show_bug.cgi?id=2174383
contour-terminal: https://bugzilla.redhat.com/show_bug.cgi?id=2174384
___
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: c++ packaging of contour terminal and libunicode

2023-03-01 Thread Felix Wang
I open an issue of the upstream repo and reported the maintainer, It was fixed 
by explicitly setting the libs as static. And thanks for your clear 
clarification.
___
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: c++ packaging of contour terminal and libunicode

2023-02-28 Thread Felix Wang
Grateful for your suggestion, it helps me, so it can build the RPM package and 
install it finally.
___
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: c++ packaging of contour terminal and libunicode

2023-02-27 Thread Felix Wang
Thanks for your advice. I tried and it can be built with no error, but when 
installing built contour package, it shows the following error:
```
Error: 
 Problem: conflicting requests
  - nothing provides libContourTerminalDisplay.so()(64bit) needed by 
contour-20230226-1.fc39.x86_64
  - nothing provides libcrispy-core.so()(64bit) needed by 
contour-20230226-1.fc39.x86_64
```
detailed steps information: 
 https://gist.github.com/topazus/adc72785c126c513093f5389c117cae7
___
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: c++ packaging of contour terminal and libunicode

2023-02-26 Thread Felix Wang
The detailed information: 
https://gist.github.com/topazus/b4bfd63b8cbce70acd4dac02a087d785
___
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: c++ packaging of contour terminal and libunicode

2023-02-26 Thread Felix Wang
I tried to add -DCMAKE_POSITION_INDEPENDENT_CODE:BOOL=ON to %cmake, it still 
does not compile and occurred the same error in the same position.
___
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: c++ packaging of contour terminal and libunicode

2023-02-26 Thread Felix Wang
updated contour .spec file: 
https://gist.githubusercontent.com/topazus/f81005cb85762ce2cf6e138f0b1cede1/raw/9745fd9c7b01d9c7d7a9619b93b22a8219ce7ad4/contour.spec
___
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: questions about requesting new package into official Fedora repository?

2023-02-26 Thread Felix Wang
Much thanks for your detailed explanation. Very helpful.
___
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: c++ packaging of contour terminal and libunicode

2023-02-26 Thread Felix Wang
libunicode repo URL: https://github.com/contour-terminal/libunicode
contour terminal repo URL: https://github.com/contour-terminal/contour
___
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


c++ packaging of contour terminal and libunicode

2023-02-26 Thread Felix Wang
spec file URL of libunicode: 
https://gist.githubusercontent.com/topazus/e30b83d669600756894a77b5258c9405/raw/5f402302ae0527732ad112059906c2a239239c34/libunicode.spec
spec file URL of contour: 
https://gist.githubusercontent.com/topazus/f81005cb85762ce2cf6e138f0b1cede1/raw/c29f456daa0a440529a4ffe20fdcaf683574053f/contour.spec

Descriptions about problems:
I first build libunicode dependency using my spec file and install it on my 
machine.
Then I try build contour terminal. It failed with the following errors:
```
[ 10%] Linking CXX static library libtext_shaper.a
cd 
/home/ruby/rpmbuild/BUILD/contour-98c8c0d0e96dc7c56ee06b4e8bfd71a23ae4f4d6/redhat-linux-build/src/text_shaper
 && /usr/bin/cmake -P CMakeFiles/text_shaper.dir/cmake_clean_target.cmake
cd 
/home/ruby/rpmbuild/BUILD/contour-98c8c0d0e96dc7c56ee06b4e8bfd71a23ae4f4d6/redhat-linux-build/src/text_shaper
 && /usr/bin/cmake -E cmake_link_script CMakeFiles/text_shaper.dir/link.txt 
--verbose=1
/usr/bin/ar qc libtext_shaper.a CMakeFiles/text_shaper.dir/font.cpp.o 
CMakeFiles/text_shaper.dir/font_locator_provider.cpp.o 
CMakeFiles/text_shaper.dir/fontconfig_locator.cpp.o 
CMakeFiles/text_shaper.dir/mock_font_locator.cpp.o 
CMakeFiles/text_shaper.dir/open_shaper.cpp.o 
CMakeFiles/text_shaper.dir/shaper.cpp.o
/usr/bin/ranlib libtext_shaper.a
gmake[2]: Leaving directory 
'/home/ruby/rpmbuild/BUILD/contour-98c8c0d0e96dc7c56ee06b4e8bfd71a23ae4f4d6/redhat-linux-build'
[ 10%] Built target text_shaper
/usr/bin/ld: /tmp/ccW09Umc.ltrans0.ltrans.o: warning: relocation against 
`_ZGVZN8logstore4Sink7consoleEvE8instance' in read-only section `.text.startup'
/usr/bin/ld: /tmp/ccW09Umc.ltrans0.ltrans.o: relocation R_X86_64_PC32 against 
symbol 
`_ZTIZN8logstore4SinkC4EbRSoEUlSt17basic_string_viewIcSt11char_traitsIcEEE_' 
can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: final link failed: bad value
collect2: error: ld returned 1 exit status
gmake[2]: *** [src/crispy/CMakeFiles/crispy-core.dir/build.make:148: 
src/crispy/libcrispy-core.so] Error 1
gmake[2]: Leaving directory 
'/home/ruby/rpmbuild/BUILD/contour-98c8c0d0e96dc7c56ee06b4e8bfd71a23ae4f4d6/redhat-linux-build'
gmake[1]: *** [CMakeFiles/Makefile2:267: 
src/crispy/CMakeFiles/crispy-core.dir/all] Error 2
gmake[1]: Leaving directory 
'/home/ruby/rpmbuild/BUILD/contour-98c8c0d0e96dc7c56ee06b4e8bfd71a23ae4f4d6/redhat-linux-build'
gmake: *** [Makefile:159: all] Error 2
error: Bad exit status from /var/tmp/rpm-tmp.Eo3xWu (%build)

RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.Eo3xWu (%build)
```
I also try to build contour from the SOURCE file of contour .spec file, which is
cmake  . -DCONTOUR_BUILD_WITH_QT6=ON && make -j6, the above build cmd worked 
fine. So I doubt the error that appeared in the build process with .spec file 
is related with the setting build flags with %cmake macros, but I do not know 
how to modify it? Or the error is relevant with build options in CMakeLists.txt 
from the upstream repo code?
___
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


questions about requesting new package into official Fedora repository?

2023-02-20 Thread Felix Wang
If I want to packaging a new package into Fedora repository, I did a koji 
scratch build, which it failed on some architecture. Is there a minimum  
architecture requirement, which builds successfully on some architecture (like 
x86_64?), in order to adopt the new package?
___
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: reclaim orphaned moarvm package

2023-02-13 Thread Felix Wang
But I am not in the Fedora packager group yet. So what I am confused that what 
should I do next.
___
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: reclaim orphaned moarvm package

2023-02-08 Thread Felix Wang
okay, thanks for your advice.
___
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: reclaim orphaned moarvm package

2023-02-08 Thread Felix Wang
update: I also plan to claim nqp and rakudo packages.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


reclaim orphaned moarvm package

2023-02-08 Thread Felix Wang
I had planned to pick `moarvm` package up when I saw it was already orphaned. I 
am very willing to maintain or comaintain it. My FAS name is topazus.
___
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