enhance: Add comprehensive .gitignore for deb-mock project
Some checks failed
Build Deb-Mock Package / build (push) Successful in 54s
Lint Code / Lint All Code (push) Failing after 1s
Test Deb-Mock Build / test (push) Failing after 36s

- Add mock-specific build artifacts (chroot/, mock-*, mockroot/)
- Include package build files (*.deb, *.changes, *.buildinfo)
- Add development tools (.coverage, .pytest_cache, .tox)
- Include system files (.DS_Store, Thumbs.db, ._*)
- Add temporary and backup files (*.tmp, *.bak, *.backup)
- Include local configuration overrides (config.local.yaml, .env.local)
- Add test artifacts and documentation builds
- Comprehensive coverage for Python build system project

This ensures build artifacts, chroot environments, and development
tools are properly ignored in version control.
This commit is contained in:
robojerk 2025-08-18 23:37:49 -07:00
parent 1a559245ea
commit 4c0dcb2522
329 changed files with 27394 additions and 965 deletions

23
docs/Release-Notes-5.8.md Normal file
View file

@ -0,0 +1,23 @@
---
layout: default
title: Release Notes - Mock 5.8
---
## [Release 5.8](https://rpm-software-management.github.io/mock/Release-Notes-5.8) - 2024-09-27
### Bugfixes
- Mock v5.7 introduced a regression in the `chroot_scan` plugin that prevented the
result directory from being created properly. This issue has been
[fixed][PR#1472] - and is the major reason for doing v5.8 bugfix release.
- The ownership of the tarball provided by `chroot_scan` (when `write_tar =
True`) has been corrected, ensuring the file is no longer root-owned.
- The `chroot_scan` plugin now consistently uses the `util.do` method instead of
custom `subprocess.call` calls. This ensures that the `mock --verbose` output
properly displays the commands (like `cp`, or `tar`) being executed.
[PR#1472]: https://github.com/rpm-software-management/mock/pull/1472