demus
5dce7e9020
Build and provide rpm of gitea / rpmbuild (release) Successful in 6m16s
SECURITY
Release attachments must belong to the intended repo (#36347) (#36375)
Fix permission check on org project operations (#36318) (#36373)
Clean watches when make a repository private and check permission when send release emails (#36319) (#36370)
Add more check for stopwatch read or list (#36340) (#36368)
Fix openid setting check (#36346) (#36361)
Fix cancel auto merge bug (#36341) (#36356)
Fix delete attachment check (#36320) (#36355)
LFS locks must belong to the intended repo (#36344) (#36349)
Fix bug on notification read (#36339) #36387
ENHANCEMENTS
Add more routes to the "expensive" list (#36290)
Make "commit statuses" API accept slashes in "ref" (#36264) (#36275)
BUGFIXES
Fix markdown newline handling during IME composition (#36421) #36424
Fix missing repository id when migrating release attachments (#36389)
Fix bug when compare in the pull request (#36363) (#36372)
Fix incorrect text content detection (#36364) (#36369)
Fill missing has_code in repository api (#36338) (#36359)
Fix notifications pagination query parameters (#36351) (#36358)
Fix some trivial problems (#36336) (#36337)
Prevent panic when GitLab release has more links than sources (#36295) (#36305)
Fix stats bug when syncing release (#36285) (#36294)
Always honor user's choice for "delete branch after merge" (#36281) (#36286)
Use the requested host for LFS links (#36242) (#36258)
Fix panic when get editor config file (#36241) (#36247)
Fix regression in writing authorized principals (#36213) (#36218)
Fix WebAuthn error checking (#36219) (#36235)
rpmspecs-gitea ^^^^^^^^^^^^^^ This is the RPM spec files that I have created for gitea. I am not affiliated with the gitea project and only provide this as a service. .. contents:: Information ----------- **Note:** I am not responsible for system damages, break-ins, or faulty code of the software that can cause the formerly listed. Always develop and test in an isolated environment at all times. **Always keep SELinux enabled.** Frequently Asked Questions -------------------------- Do you have any SRPMS available? ++++++++++++++++++++++++++++++++ They'll normally be available from my copr builds, if you are interested in making changes and using mock for yourself. Have any documentation or guides? +++++++++++++++++++++++++++++++++ If you're starting out rpm packaging, please consider reading the following documentation. The packaging guidelines may seem strict, but they are deemed best practices if you are considering on being a package maintainer (sponsored or not). Keep in mind, **I am always learning**. I am in no way an expert, nor do I claim to be. `FHS <http://www.pathname.com/fhs/>`_ `Fedora: Fedora Packaging Guidelines <https://docs.fedoraproject.org/en-US/packaging-guidelines/>`_ `Fedora: Creating RPM Packages <https://docs.fedoraproject.org/en-US/package-maintainers/Packaging_Tutorial_GNU_Hello/>`_ What you should get from the above is there are specific guidelines that should be followed, for maintainability, portability, and easy review. My RPM specs will have an FAQ of the "purpose". Do you have any repositories? +++++++++++++++++++++++++++++ Yes, I do. I have two, actually. I have a copr and a personal repository. `Copr <https://copr.fedorainfracloud.org/coprs/nalika/>`_ Do you take requests? +++++++++++++++++++++ I normally don't. But, if what you're asking for doesn't have an RPM or project in copr, I'll consider it based on what it is, and if it fits licensing and guidelines. You can drop me an email or a line here and I will get back to you. Do you package for other systems? +++++++++++++++++++++++++++++++++ At this present time, I do not. I have considered packaging for Ubuntu or OpenSUSE. However those, much like Arch, already have plenty of maintainers with tons upon tons of packages (up to date or not) and their own build systems similar to Fedora. So some of the packages you may see here may already exist for those distributions in base or extra repositories they provide.