vasilito
f31522130f
Build system (5 gaps hardened): - COOKBOOK_OFFLINE defaults to true (fork-mode) - normalize_patch handles diff -ruN format - New 'repo validate-patches' command (25/25 relibc patches) - 14 patched Qt/Wayland/display recipes added to protected list - relibc archive regenerated with current patch chain Boot fixes (fixable): - Full ISO EFI partition: 16 MiB → 1 MiB (matches mini, BIOS hardcoded 2 MiB offset) - D-Bus system bus: absolute /usr/bin/dbus-daemon path (was skipped) - redbear-sessiond: absolute /usr/bin/redbear-sessiond path (was skipped) - daemon framework: silenced spurious INIT_NOTIFY warnings for oneshot_async services (P0-daemon-silence-init-notify.patch) - udev-shim: demoted INIT_NOTIFY warning to INFO (expected for oneshot_async) - relibc: comprehensive named semaphores (sem_open/close/unlink) replacing upstream todo!() stubs - greeterd: Wayland socket timeout 15s → 30s (compositor DRM wait) - greeter-ui: built and linked (header guard unification, sem_compat stubs removed) - mc: un-ignored in both configs, fixed glib/libiconv/pcre2 transitive deps - greeter config: removed stale keymapd dependency from display/greeter services - prefix toolchain: relibc headers synced, _RELIBC_STDLIB_H guard unified Unfixable (diagnosed, upstream): - i2c-hidd: abort on no-I2C-hardware (QEMU) — process::exit → relibc abort - kded6/greeter-ui: page fault 0x8 — Qt library null deref - Thread panics fd != -1 — Rust std library on Redox - DHCP timeout / eth0 MAC — QEMU user-mode networking - hwrngd/thermald — no hardware RNG/thermal in VM - live preload allocation — BIOS memory fragmentation, continues on demand
34 lines
1.4 KiB
YAML
34 lines
1.4 KiB
YAML
# This is a set of bugbot commands for issues and merge requests - setting any of the
|
|
# bugbot::foo labels will trigger gitlab-triage to run with this ruleset (well, the
|
|
# one we have on the main branch at the time)
|
|
#
|
|
# Note that for adding labels, the label must first created in the project.
|
|
resource_rules:
|
|
issues:
|
|
rules:
|
|
- name: "Close bugs that aren't Wayland bugs"
|
|
conditions:
|
|
labels:
|
|
- "bugbot::not-wayland"
|
|
actions:
|
|
remove_labels:
|
|
- "bugbot::not-wayland"
|
|
comment: |
|
|
Thank you for the report, but your issue does not look like it would belong here. Sorry.
|
|
|
|
This repository is for the Wayland protocol specification and the
|
|
low-level C library that deals with the protocol.
|
|
|
|
This issue here is a bug not with the protocol itself but with either
|
|
- your compositor or desktop environment's implementation of the Wayland protocol and surrounding functionality,
|
|
- the individual application that triggers this issue, or
|
|
- the kernel driver used by your hardware
|
|
|
|
Please file the issue against your compositor/desktop environment, the application
|
|
or the kernel drivers instead, whichever seems more likely to you. If you are not sure,
|
|
file an issue against the application.
|
|
status: "close"
|
|
merge_requests:
|
|
rules:
|
|
[]
|