-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PPA FTBFS armhf/noble #3285
Labels
triaged
Triage into JIRA to plan it in
Comments
Oh, no. Our lifted-from-umockdev hack to make this work reliably on 32bit platforms has broken. Hm, from that package (in noble-proposed, because this is still caught up in the 64-bit
|
AlanGriffiths
added a commit
to Miriway/Miriway
that referenced
this issue
Mar 15, 2024
AlanGriffiths
added a commit
to Miriway/Miriway
that referenced
this issue
Mar 15, 2024
AlanGriffiths
added a commit
to Miriway/Miriway
that referenced
this issue
Mar 15, 2024
github-merge-queue bot
pushed a commit
that referenced
this issue
Mar 18, 2024
We're *mostly* insulated from this, but our tests need to intercept calls to `open`, which means that we're exposed to some glibc internals that change under `_TIME_BITS=64`. Fortunately umockdev in the archive has already hit this, so adapt that fix to our use. Fixes: #3285
mattkae
pushed a commit
that referenced
this issue
Mar 28, 2024
We're *mostly* insulated from this, but our tests need to intercept calls to `open`, which means that we're exposed to some glibc internals that change under `_TIME_BITS=64`. Fortunately umockdev in the archive has already hit this, so adapt that fix to our use. Fixes: #3285
mattkae
pushed a commit
that referenced
this issue
Mar 28, 2024
We're *mostly* insulated from this, but our tests need to intercept calls to `open`, which means that we're exposed to some glibc internals that change under `_TIME_BITS=64`. Fortunately umockdev in the archive has already hit this, so adapt that fix to our use. Fixes: #3285
Merged
AlanGriffiths
added a commit
that referenced
this issue
Apr 3, 2024
We're *mostly* insulated from this, but our tests need to intercept calls to `open`, which means that we're exposed to some glibc internals that change under `_TIME_BITS=64`. Fortunately umockdev in the archive has already hit this, so adapt that fix to our use. Fixes: #3285
github-merge-queue bot
pushed a commit
that referenced
this issue
Apr 8, 2024
## Release Notes mir (2.16.4) UNRELEASED; urgency=medium * Bugfix release: - Ignoring zero length gamma curves for KMS outputs (Fixes: #3238) - Add hardware cursor support (Fixes: #3198) - Screenshots now respect clipping areas and rotated outputs (Fixes: #3236) (Fixes: #3259) - Fixed custom attributes propagation on outputs (Fixes: canonical/ubuntu-frame#172) - Handle the Ubuntu 64-bit time_t apocalypse (Fixes: #3285)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://launchpadlibrarian.net/719328544/buildlog_ubuntu-noble-armhf.mir_2.16.3+dev199-g24d5001542-0ubuntu24.04_BUILDING.txt.gz
The text was updated successfully, but these errors were encountered: