User avatar None

Resource updated
The “po/fr/master/pages/Package_Maintenance_Guide.po” file was changed. a month ago
User avatar None

String added in the repository
This form can be used to request branches when not inside package's Git repository. You do not need to wait for your repository to be created before filing such branch request, but you should request the repository before requesting branches.
 
a month ago
User avatar None

String added in the repository
fedpkg request-branch --repo <source_package_name> f40
 
a month ago
User avatar None

Resource updated
The “pot/master/pages/Package_Maintenance_Guide.pot” file was changed. a month ago
User avatar None

String added in the repository
This form can be used to request branches when not inside package's Git repository. You do not need to wait for your repository to be created before filing such branch request, but you should request the repository before requesting branches.
This form can be used to request branches when not inside package's Git repository. You do not need to wait for your repository to be created before filing such branch request, but you should request the repository before requesting branches.
a month ago
User avatar None

String added in the repository
fedpkg request-branch --repo <source_package_name> f40
fedpkg request-branch --repo <source_package_name> f40
a month ago
User avatar None

Resource updated
The “po/pt_BR/master/pages/New_Package_Process_for_New_Contributors.po” file was changed. a month ago
User avatar None

String added in the repository
Please see the xref:Package_Update_Guide.adoc[Package Update Guide] for more details.
 
a month ago
User avatar None

String added in the repository
You can also select multiple builds from different packages to include in a single update using the web interface. This is useful when you would like to push linked builds, for example: an application package and its dependencies that are necessary for it to run correctly.
 
a month ago
User avatar None

String added in the repository
It is often easier to complete builds for all your branches and then push a single update using the https://bodhi.fedoraproject.org/updates/new[Bodhi web interface]. Bodhi is smart enough to split your update into individual updates, one for each Fedora release branch.
 
a month ago
User avatar None

String added in the repository
fedpkg update
 
a month ago
User avatar None

String added in the repository
If it fails to build, the build system will send you an email to report the failure and show you to the logs. Commit any needed changes to git, bump the SPEC release number, and request a new build.
 
a month ago
User avatar None

String added in the repository
If everything goes well, it should queue up your branch for building, the package will cleanly build, and you're done!
 
a month ago
User avatar None

String added in the repository
If there is another branch to work with repeat _To switch to a branch_ and import and commit to each branch.
 
a month ago
User avatar None

String added in the repository
fedpkg build
 
a month ago
User avatar None

String added in the repository
Build the package:
 
a month ago
User avatar None

String added in the repository
git push
 
a month ago
User avatar None

String added in the repository
Push the changes to the server:
 
a month ago
User avatar None

String added in the repository
git merge rawhide
 
a month ago
User avatar None

String added in the repository
Merge the initial commit from main (Rawhide), creating an identical commit in the branch:
 
a month ago

Search