Helps with scriptability for large stack updates and will attempt to autowrite the commit message without needing to open up the editor.
e.g. git commit -m "autocommitmsg" -> "nano: Update to v1.2.3"
Use with caution as not all cases are handled, notably "Rebuild against
libfoo" is not currently.
**Summary**
Add `sync-note-prs` to list PRs with the `Topic: Sync Notes` label.
**Test Plan**
```console
./common/Scripts/worklog.py highlights "1 week ago" -f tty
./common/Scripts/worklog.py highlights "1 week ago" -f md
./common/Scripts/worklog.py highlights "1 week ago" -f html
```
**Checklist**
- [x] ~~Package was built and tested against unstable~~
- [ ] ~~This change could gainfully be listed in the weekly sync notes
once merged~~ <!-- Write an appropriate message in the Summary section,
then add the "Topic: Sync Notes" label -->
**Summary**
The PKG_CHECK_MODULES macro in configure.ac files can define more than
one module (see
[here](https://autotools.info/pkgconfig/pkg_check_modules.html)).
Previously all the entries were simply added into the same
`pkgconfig()`.
This properly separates them into their own entries and also accepts
"<=" and "=" comparators (though these aren't used for anything except
detecting version definitions)
Also fix adding dependencies for combined configure.ac/Python projects
Old behaviour:
```
go-task new -- gammastep https://gitlab.com/chinstrap/gammastep/-/archive/v2.0.9/gammastep-v2.0.9.tar.bz2
[...]
yq '.builddeps' packages/g/gammastep/package.yml
- pkgconfig(libdrm)
- pkgconfig(x11)
- pkgconfig(xxf86vm)
- pkgconfig(xcb)
- pkgconfig(xcb-randr)
- pkgconfig(wayland-client wayland-scanner)
- pkgconfig(glib-2.0 gobject-2.0)
- pkgconfig(glib-2.0 gio-2.0)
```
New behaviour:
```
go-task new -- gammastep https://gitlab.com/chinstrap/gammastep/-/archive/v2.0.9/gammastep-v2.0.9.tar.bz2
[...]
yq '.builddeps' packages/g/gammastep/package.yml
- pkgconfig(libdrm)
- pkgconfig(x11)
- pkgconfig(xxf86vm)
- pkgconfig(xcb)
- pkgconfig(xcb-randr)
- pkgconfig(wayland-client)
- pkgconfig(wayland-scanner)
- pkgconfig(glib-2.0)
- pkgconfig(gobject-2.0)
- pkgconfig(gio-2.0)
```
**Test Plan**
- `go-task new -- gammastep
https://gitlab.com/chinstrap/gammastep/-/archive/v2.0.9/gammastep-v2.0.9.tar.bz2`
produces correct build dependencies
- `go-task new -- rapidyml
https://github.com/biojppm/rapidyaml/archive/refs/tags/v0.7.2.tar.gz`
still works correctly
- `go-task new -- pip-tools
1ef453f10f/pip-tools-7.4.1.tar.gz`
still works correctly
**Checklist**
- [x] Package was built and tested against unstable
- [ ] This change could gainfully be listed in the weekly sync notes
once merged <!-- Write an appropriate message in the Summary section,
then add the "Topic: Sync Notes" label -->
**Summary**
The PKG_CHECK_MODULES macro in configure.ac files can define more than one module.
Previously all the entries were simply added into the same `pkgconfig()`.
This properly separates them into their own entries.
Also fix adding dependencies for combined configure.ac/Python projects
Signed-off-by: Thomas Staudinger <Staudi.Kaos@gmail.com>
**Summary**
- Get the current rundeps removing the 'python-' prefix
and comparing '-' and '_' equivalently compare against
the required deps from pypi.
**Summary**
The previous change to pyproject.toml happened to only work for sources also using other, higher-priority build systems. The logic for adding the dependencies to PYTHON_MODULE recipes was still based on strings.
Additionaly the dependencies were added multiple times for each `pyproject.toml` or `setup.cfg file` found. Don't add additional dependencies if PEP 517 is already among known_types
Make sure the PEP517 dependencies are correctly added if the source also uses other build systems instead of wrapping them in pkgconfig()
Signed-off-by: Thomas Staudinger <Staudi.Kaos@gmail.com>
**Summary**
Add a method for including additional dependencies in `yauto` and use it
for the `pyproject.toml` dependencies instead of writing them as a
string.
Part of https://github.com/getsolus/packages/issues/4914
**Test Plan**
`
go-task new -- rapidyaml
https://github.com/biojppm/rapidyaml/archive/refs/tags/v0.7.2.tar.gz`
succeeds
**Checklist**
- [x] Package was built and tested against unstable
- [ ] This change could gainfully be listed in the weekly sync notes
once merged <!-- Write an appropriate message in the Summary section,
then add the "Topic: Sync Notes" label -->
**Summary**
Many updates added since 1.5.1 (released in 2012!)
Full change log available [here](https://github.com/libtcod/libtcod/blob/1.24.0/CHANGELOG.md)
**Test Plan**
Built and ran the few samples in the repo
**Checklist**
- [x] Package was built and tested against unstable
**Summary**
- Previous commit handled all the renames, this commit chnages:
- Comment text in some monitoring files
- The taskfile task for a new monitoring file
- The CI check for monitoring file existence
**Summary**
/usr/bin/new{g,u}idmap were not being set setuid for some reason, which
broke boulder's use of user namespaces.
Add verbose chmod command to the recipe that shows the change at the end
of the build.
**Test Plan**
Build shadow, check that the installed /usr/bin/new{g,u}idmap are setuid,
successfully build a recipe with boulder.
Signed-off-by: Rune Morling <ermo@serpentos.com>
**Summary**
Change loader/dumper to ruamel to enable putting out dependency lists
with proper offset and colon spacing. This way the output can directly
be copied and pasted into the recipe.
Note: I couldn't find a way to do this with pyyaml; Dumper
implementation [adopted from ruamel
docs](https://yaml.readthedocs.io/en/latest/example/#output-of-dump-as-a-string).
I also couldn't get `top_level_colon_align` to work for some reason, so
in cases of very short subpackage names with dependencies the colon
might be placed too far to the left (not 100% sure if there is such a
case in the repo; the "^g++" case happens to perfectly align)
Resolves https://github.com/getsolus/packages/issues/3924
**Test Plan**
Old output `budgie-desktop-branding`:
```
- breeze-cursor-theme
- budgie-backgrounds
- budgie-desktop
- font-hack-ttf
- livecd:
- budgie-desktop-branding
- test
- materia-gtk-theme
- materia-gtk-theme-dark
- noto-sans-ttf
- noto-serif-ttf
- papirus-icon-theme
- qtstyleplugins
- solus-artwork
- test
```
New output `budgie-desktop-branding`:
```
- breeze-cursor-theme
- budgie-backgrounds
- budgie-desktop
- font-hack-ttf
- livecd :
- budgie-desktop-branding
- test
- materia-gtk-theme
- materia-gtk-theme-dark
- noto-sans-ttf
- noto-serif-ttf
- papirus-icon-theme
- qtstyleplugins
- solus-artwork
- test
```
Old output `gcc` rundeps:
```
- ^g++: gcc
- ^gfortran:
- gcc
- libgfortran
- ^libgcc-32bit: libgcc
- ^libgfortran-32bit: libgfortran
- ^libgomp-32bit:
- libgcc-32bit
- libgomp
- ^libstdc++-32bit: libstdc++
- mpc
- mpfr
- test
```
New output `gcc` rundeps:
```
- ^g++ : gcc
- ^gfortran :
- gcc
- libgfortran
- ^libgcc-32bit : libgcc
- ^libgfortran-32bit : libgfortran
- ^libgomp-32bit :
- libgcc-32bit
- libgomp
- ^libstdc++-32bit : libstdc++
- mpc
- mpfr
- test
```
**Checklist**
- [x] Package was built and tested against unstable
**Summary**
Add a check that fails when static libraries are included.
Packages or paths that should contain static libraries can be allow-listed in the CI configuration.
