Re: HOWTO: Change default branch on pagure.io projects
> Which project/host are you trying to push to? > This is allowed on pagure.io but if you're trying on src.fp.o it will be > blocked > (and this is expected). We will be doing src.fp.o directly server side, we'll > simply be renaming the master ref to rawhide (to by-pass the git hook which > does > what you're seeing here) and create the symlink main -> rawhide. > > > Pierre Thanks for the hint and the info. It was a git repo on https://src.fedoraproject.org, which I had tried. That was the reason. Wolfgang ___ 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
Re: HOWTO: Change default branch on pagure.io projects
Hi Kevin, thanks for the HOWTO. Some comments from trying it: > > git push > (This pushes the new ‘main’ branch to pagure.io) This should be: git push --set-upstream origin main > git push origin :master > (This deletes the old ‘master’ branch) git push origin :master remote: Branch deletion is not allowed remote: Denied push for ref 'refs/heads/master' for user '**' remote: All changes have been rejected Best regards Wolfgang ___ 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
Re: "CMake to do out-of-source builds" implemented under EPEL 7?
Dear Antonio, thanks for the quick reply. This helped a lot. I had to add `%undefine __cmake3_in_source_build` to the spec file, in addition to the `%undefine __cmake_in_source_build` Best regards Wolfgang ___ 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
"CMake to do out-of-source builds" implemented under EPEL 7?
Hi,
will the change "CMake to do out-of-source builds" [1] also bee implemented
under EPEL 7?
So, that %cmake3 and %cmake3_build will work as expected and use
%{_vpath_builddir}.
Best regards
Wolfgang
[1] https://fedoraproject.org/wiki/Changes/CMake_to_do_out-of-source_builds
___
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
Re: z3 soname bump
Thanks Jerry for providing all the details about the z3 soname bump. FYI: cppcheck has been rebuilt now [1] Wolfgang [1] https://koji.fedoraproject.org/koji/taskinfo?taskID=48648878 ___ 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
Re: Bodhi update pushes are now automated
> On Wed, Nov 07, 2018 at 05:15:57PM -0800, Kevin Fenzi wrote: > > What about this part? There's an "Autopush — enabled" item in bodhi, but > afaict, it doesn't do anything and I always click "push to batched" > manually > on all updates. I'd like to have the update got to batched automatically > once the 7 days of waiting are up. > > Zbyszek > > Hi, what about "push to batched": How is this currently handled? Current docs say: "... waiting until the next Tuesday when Bodhi will automatically switch the request to "stable" at 03:00 UTC." [1] Is this still only on the next Tuesday? During the last package updates, which I pushed to batched, it turned out that it was the always next day at 03:00 UTC. Best regards Wolfgang [1] https://fedoraproject.org/wiki/Bodhi#Testing.2FBatched ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
F28: Mismatch between the program and library build versions detected, gcc-c++, wxGTK3
Hello, a recent F28 update build of poedit [1] shows the following message after starting: Warning: Mismatch between the program and library build versions detected. The library used 3.0 (wchar_t,compiler with C++ ABI 1012,wx containers,compatible with 2.8), and your program used 3.0 (wchar_t,compiler with C++ ABI 1013,wx containers,compatible with 2.8). Additional info: poedit-2.1-1.fc28 has been built using gcc-c++ 8.1.1-5.fc28 wxGTK3-3.0.4-1.fc28 has been built using gcc-c++ 8.0.1-0.16.fc28 The above message disappears, when wxGTK3 is rebuilt using current gcc-c++ 8.1.1-5.fc28, which has just been tested using a rebuild of wxGTK3 on copr [2]. However, there are several other packages depending on wxGTK3 and it looks like this ABI mismatch issue in F28 needs some coordination to be solved for wxGTK3 and dependent packages. Best regards Wolfgang [1] https://bodhi.fedoraproject.org/updates/FEDORA-2018-c9997803a6 [2] https://copr.fedorainfracloud.org/coprs/c72578/wxGTK3/build/780540/ ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/WOOGIEVDBGDLQ2S5BZEE4AC4LBC7IL7M/
Re: GCC 8/9 ABI change: call for rebuilds
In the meantime, gcc-8.1.1-5 is available as an update for F28. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/KWRHNP54HKNMN3DG5XI5URE6REYTYPGW/
Re: src.fedoraproject.org, forking projects, PRs
Thanks for the hint! ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
src.fedoraproject.org, forking projects, PRs
Hello, is forking projects, PRs etc. already supposed to work at src.fedoraproject.org? So far, I am getting the following: # Source GIT URL: SSH git clone ssh://pkgs.fedoraproject.org/forks/c72578/rpms/cacti.git Permission denied (publickey). # Remark: the ~/.ssh/id_rsa key is present here and working (e.g. for fedpkg) # Source GIT URL: GIT git clone https://src.fedoraproject.org/forks/c72578/rpms/cacti.git cd cacti git push fatal: unable to access 'https://src.fedoraproject.org/forks/c72578/rpms/cacti.git/': The requested URL returned error: 403 So far, there is documentation on forking projects on pagure.io, what about src.fedoraproject.org? e.g.: https://fedoraproject.org/wiki/How_to_fix_bugs_on_the_Fedora_Project_website https://docs.pagure.org/releng/contributing.html Thanks Wolfgang ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
