Autopkgtests for oracular/cockpit/s390x passed with a retry,
that should unblock the oracular-proposed migration shortly.
316-1build1 sosreport/4.7.0-0ubuntu12024-05-22
15:19:06 UTC 0h 04m 29s mfo pass
1bc3dca3-467e-430b-b336-fe8c1f19b6d5
--
You received
The autopkgtests failures for mantic/jammy/focal have cleared up with retries.
Proceeding with the release of these series.
lintian [mantic/armhf]
2.116.3ubuntu3.2lintian/2.116.3ubuntu3.2
2024-05-20 22:46:45 UTC 0h 32m 13s mfo pass
The verification for noble/mantic/jammy/focal look good; thanks!
However, the autopkgtests failures for mantic/jammy/focal aren't clear.
I retried them, as apparently they are infrastructure related timeouts/issues.
I'll check later if still on shift.
--
You received this bug notification
The verification of the Stable Release Update for lintian has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
The verification of the Stable Release Update for nbd has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
Verificaton done on noble-proposed.
Thanks for the detailed test steps!
(I updated the last command from 'nbd-client -d nbd0' to 'nbd-client nbd0',
which reflects the test step without the fix, in 'Now, trigger the problem').
Environment:
---
lxc launch ubuntu:noble --vm mfo-noble-vm
lxc shell
** Description changed:
[ Impact ]
nbdtab uses a port of 0 by default which is not sensible. This means
that if you do not set a default port in nbdtab, it will fail.
You will see an error such as: Error: Socket failed: Connection refused
[ Test Plan ]
$ lxc launch
This SRU is blocked on the upload to the Development Release, as per [1]
(comment #2).
If that is not possible or needed, please explain. Marking Oracular as
Incomplete. Thanks!
[1]
https://wiki.ubuntu.com/StableReleaseUpdates#Development_Release_Fixed_First
** Changed in: rtl8812au (Ubuntu
The verification of the Stable Release Update for remmina has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
Marking this SRU as verification-failed per comments
- #4 (partial failure with applications running) and
- #5 (failure even without applications running).
The partial failure would seem like a regression too,
since the bug description says that the fix / change
acts 'effectively and
Verification pending for noble-proposed
(blocks combined SRU release for bugs 2059818, 2059819, 2042844)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2042844
Title:
JS ERROR: Gio.DBusError:
Verification pending for noble-proposed
(blocks combined SRU release for bugs 2059818, 2059819, 2042844)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059819
Title:
Regression: Jammy to Noble,
This SRU is pending verification for noble-proposed and autopkgtests
regressions to be cleared up.
I looked the autopkgtests regressions, and some seem to be temporary
conditions on the infrastructure, thus I just triggered retries for all
tests/archs.
--
You received this bug notification
This SRU is pending clarification about the verification tags flip
(comments 23, 12, 7) and other questions (comment 23).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061747
Title:
obsolete
Attaching the error image linked in the bug description for archival
purposes:
"""
Expectation: Get a table with the users assigned to this project.
Result: Get an error - https://i.imgur.com/TminwUy.png [attached]
"""
** Attachment added: "TminwUy.png"
Commit ed768ab50713 (proposed for Ubuntu SRUs & Cloud Archive) isn't in
Oracular yet, IIUIC; adding bug task.
master
$ git log --oneline -1 ed768ab
ed768ab50713 Fix Users/Groups tab list when a domain context is set
stable/2024.1
$ git log --oneline origin/stable/2024.1
Adding bug tasks for Noble/Oracular as Fix Released, for clarity, per
comment #2 and checks below.
$ git log --oneline -1 95089025fda7c8cce6f7195e2a63f7f09efc9e0a
95089025fda7 Extend configurable skippability of neutron calls to project
instance detail
$ git describe --contains 95089025fda7
Patch [1] (proposed for Ubuntu SRUs & Cloud Archive) isn't in
Oracular/Noble yet, IIUIC; adding bug tasks.
$ git log --oneline -- openstack_dashboard/api/keystone.py | grep -m1
'Fix error on changing user password by admin'
da8e95929857 Fix error on changing user password by
Marking Bionic as Won't Fix as it's End of Standard Support (EOSS), and in
Expanded Security Maintenance (ESM).
If you have an Ubuntu Pro subscription with Support, and would like a fix,
please open a support ticket.
** Tags removed: sts-sponsor-volunteer
** Changed in: kmod (Ubuntu Bionic)
** Tags removed: sts-sponsor-volunteer
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875669
Title:
autopkgtest failures
To manage notifications about this bug go to:
Oh, and Oracular indeed just migrated while I posted the comment (#21
#22); nice timing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064580
Title:
Please update the package to 20240320.00
To
The verification of the Stable Release Update for google-osconfig-agent
has completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that
Summary for SRU release.
Autopkgtests: OK
- Devel/O: proposed migration was blocked in a test queued since early May;
re-triggered it and it passed; this should migrate soon.
- Stable/NMJF: re-triggered/cleared autopkgtests pending; all series/archs
passed.
Builds/FTBFS: OK
- Focal/riscv64:
Hi Robie, Sergio,
The concern about removing 'version_attributes' and 'discovery_auth_attributes'
can be addressed with this simple change/backport.
What do you think?
Don't remove the 2 attributes / move elements into 'target_name_excloudes'.
Instead, add a new attribute / its element into
To be clear, I don't think these should block the acceptance of this SRU
(I have seen different criteria to accept SRUs regarding DEP-3 headers),
but hopefully might be of some value for future SRUs, if you agree w/ it.
I'll refrain from accepting it for now as oracular-proposed seems to have
Hi Dave (~waveform),
Thanks for all the work to review/sponsor this fix! (And several others!)
It's really appreciated.
In a comparatively small but relevant note, I'd like to humbly point out though
that some DEP-3 headers seem incorrect (IMHO) in the uploads AFAICT based in [1]
(section
Rejected from the unapproved queues for Noble, Mantic, Jammy, and Focal
per comment #14. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921914
Title:
[SRU] package quickml 0.7-5.1 failed to
Hi Sergio,
Thanks for the upload!
The bug and fix sound good and relatively simple to verify.
The SRU bug template is still missing Test Plan / Regression Potential,
so I'll mark it as Incomplete for the time being (I see it may be coming
soon, per "TBD").
While looking at the Björn's mention
Chlo, thanks for the updates to the SRU template.
'Where problems could occur' is indeed generic as can be expected for
such a big update, but the information there is certainly helpful.
The one point/patch that applies to Ubuntu more directly in the big update
(comment #5)
is a gpg/apt change
Hi Utkarsh,
Thanks for the pointer to the dependency changes as requested by the SRU
exception, and update to the bug template.
I had seen that in the diff (and filter it out, per the size, of
course), but I think what the request in the SRU exception is, is
something easier to parse re: the
Hello Philip, or anyone else affected,
Accepted google-osconfig-agent into jammy-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/google-osconfig-
agent/20240320.00-0ubuntu1~22.04.0 in a few hours, and then in the
-proposed repository.
Please help us
Hello Philip, or anyone else affected,
Accepted google-osconfig-agent into focal-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/google-osconfig-
agent/20240320.00-0ubuntu1~20.04.0 in a few hours, and then in the
-proposed repository.
Please help us
The uploads for Jammy and Focal follow Oracular's too,
with additional changes to use a newer go version, as
already done in Focal (J: any > 1.21; F: 1.18 > 1.21).
Please address the SRU-related requests in comment #7.
Thanks!
** Changed in: google-osconfig-agent (Ubuntu Jammy)
Status:
The uploads for Noble and Mantic follow Oracular's as expected (#5),
the only differences being timestamps and a securiy patch in Mantic.
The code changes look good AFAICT, and the vendored deps changes
are such in size that require validation by testing.
Please address the request in comment #6
Hello Philip, or anyone else affected,
Accepted google-osconfig-agent into mantic-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/google-osconfig-
agent/20240320.00-0ubuntu1~23.10.0 in a few hours, and then in the
-proposed repository.
Please help us
Hello Philip, or anyone else affected,
Accepted google-osconfig-agent into noble-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/google-osconfig-
agent/20240320.00-0ubuntu1~24.04.0 in a few hours, and then in the
-proposed repository.
Please help us
It looks like the uploads are coming in
(noble 25 mins ago, mantic 16 mins ago).
After your code/package-wise tasks are done,
could you please take a look at listing the
vendorized deps changes, as per SRU exception?
I realize that might be a lot, but it's in the
exception, so it must be asked
Updating the Oracular bug task to Fix Committed, as the
reference to this bug is already in oracular-proposed [1].
The Oracular Oriole (active development)
20240320.00-0ubuntu1proposed (main) 9 hours ago
Changelog
google-osconfig-agent (20240320.00-0ubuntu1)
This bug received a prioritization request for SRU review.
Unfortunately, apparently the uploads for stable releases
haven't happened today so far (but I will check tomorrow).
Meanwhile, I have familiarized myself with the upload for
Oracular, which is expected to be quite similar to stable
Hi Jorge,
Thanks for testing and the update.
Re: mantic-proposed, that is weird; any mirrors in place? It looks OK in the
archive:
(All cinder binary packages were available in the verification of bug 1987663.)
$ curl -s
Hi Timo,
Thanks for looking into this.
> Wouldn't it be less risky to just backport 8.0.4 instead of 24/36
commits to mantic/jammy?
So so; and there's more involved.
There are near-future steps being taken in that direction already (SRU
exception to be discussed in the upcoming Engineering
Hi Jorge,
Thanks for verifying jammy-proposed.
Could you please verify mantic-proposed as well?
The fix release to jammy-updates depends on release for mantic-updates (ie,
verification of mantic-proposed).
Thanks again!
--
You received this bug notification because you are a member of Ubuntu
Verification done on {mantic,jammy,focal}-proposed.
The detailed verification steps as per comment #3
are attached. This is the summary with key steps.
With the packages from -proposed, when (re)starting
{cinder-volume,tgt}.service,
the cinder-volume service is started _after_ the tgt service,
The updates look good, thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063221
Title:
Drop libglib2.0-0 transitional package
To manage notifications about this bug go to:
** Changed in: rustc (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2052985
Title:
[SRU] Upgrade Rust to 1.76.0
To manage notifications about this bug go
Hi Jeremy,
This looks mostly good, AFAICT.
Could you please complete the SRU bug template by adding the section
'Where problems could occur' / 'Regression potential'? [1]
And although the 'Test Case' is feasible to understand, based on the 'Impact'
section, it would be nice to have a
I tested this with a local package build and local repo in a mantic container,
doing an `apt --dry-run dist-upgrade` without/with that repo (w/ noble apt
sources list),
and manually download/run noble's release upgrader without/with that repo.
The behavior is the same (ie, no regressions) as
Ok; thanks for clarifying.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061891
Title:
Noble upgrade breaks iptables-persistent and netfilter-persistent
usage
To manage notifications about this
Moving from Fix Committed back to In Progress as this isn't in -proposed yet,
and In Progress reflects 'uploaded' better.
(I don't mean to be pedantic, but this avoids confusion; even though the git
repo was mentioned, AFAIK the 'Ubuntu' project in bug tasks means the status
Fix Committed should
Moving from Fix Committed back to In Progress as this isn't in -proposed yet,
and In Progress reflects 'uploaded' better.
(I don't mean to be pedantic, but this avoids confusion; even though the git
repo was mentioned, AFAIK the 'Ubuntu' project in bug tasks means the status
Fix Committed should
Hi Nick and Julian,
Thanks for the fix and SRU template!
Question:
IIUIC, the fix simply removes 'ufw' if '{iptables,netfilter}-persistent'
is installed.
But is it possible that removing ufw is the wrong thing to do in some
particular case?
Say, if the user actually used/configured ufw
** Description changed:
- [Impact / Original Description]
+ [Impact]
+ ufw and -persistent packages both manage the firewall, hence they conflict
but they accidentally had no conflicts in jammy. If both are installed,
persistent packages will store and restore firewall configuration, so ufw
Updating the verification tags for the new version,
agreeing with Christian's assessment in comment 12,
and verifying that the changes are still included:
$ pull-lp-debs -a arm64 libvirt-daemon-system focal 6.0.0-0ubuntu8.20
$ dpkg-deb -x libvirt-daemon-system_6.0.0-0ubuntu8.20_arm64.deb deb
$
The packages in focal-proposed have also been verified successfully in
real-world/non-synthetic tests by one of our Ubuntu Pro support
customers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059272
Verification done on focal-proposed, following comments 23, 24, 25, 26.
Including in this comment a few key snippets from each test/comment.
---
Environment
---
LXD virtual machine
lxc launch --vm ubuntu:focal lp2059272-focal
lxc exec lp2059272-focal -- su - ubuntu
Enable proposed & debug
gt; Mauricio Faria de Oliveira (mfo)
** Changed in: qemu (Ubuntu)
Assignee: Sergio Durigan Junior (sergiodj) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2048517
Title:
EPYC-Rom
Hi Giuseppe,
Please test nova version 2:21.2.4-0ubuntu2.7~ppa3 in the PPA.
(It's finished building and should be published in some time.)
The config change should be something along the lines of
`cpu_model_extra_flags = -xsaves`
I couldn't test the package/functionality yet, but all of the
Hmm, sorry, please hold; the unit tests caught an error.
I'll check that on Monday.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2048517
Title:
EPYC-Rome model without XSAVES may break live
Mantic and Jammy built successfully in all supported architectures.
(riscv64 fails, but it also fails on mantic/jammy-release; it's OK.)
Uploaded!
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Giuseppe,
You're right, libvirt checks the specified model against its known
models.
However, the EPYC-Rome (not-v4) doesn't specify 'xsaves', just EPYC-Milan,
so it _seems_ the feature came from the default with cpu_model host-model,
which perhaps found EPYC Milan model closer to the host
** Description changed:
[Impact]
- Linux kernel 6.2 includes patches with structural changes that may render the
crash utility unable to parse the dump file.
+ Linux kernel 6.2 includes patches with structural changes that may render the
crash utility in Mantic (release kernel 6.5) and Jammy
Jammy: patches 0001-0012 look good too!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2038249
Title:
The dump file parsing issue arises from structural changes in Linux
kernel 6.2
To manage
Partial review of the Jammy debdiff.
(Still in progress.)
Started with Jammy's patches 0012-0036, which are Mantic's patches 0001-0024
(already reviewed).
Most patches are identical, and some have context-line changes, as expected
(8.0.2/8.0.0 delta).
Just had a few changes.
$ for ((i=1;
Today, I tackled the Mantic debdiff (made only a few changes; below).
It's now currently building in a PPA for all supported architectures,
(ppa:mfo/lp2038249) and if all goes well I will upload it to Mantic.
Thanks!
Mauricio
---
All 24 commits are included in Noble (12 in 8.0.4 and 12 in
** Description changed:
[Impact]
Linux kernel 6.2 includes patches with structural changes that may render the
crash utility unable to parse the dump file.
==
d122019bf061 mm: Split slab into its own type
401fb12c68c2 mm: Differentiate struct slab fields by sl*b implementations
Marking Lunar as Won't Fix (EOL).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2038249
Title:
The dump file parsing issue arises from structural changes in Linux
kernel 6.2
To manage
crash 8.0.4 is available in noble (bug 2047861); checking the stable
releases' debdiffs.
** Changed in: crash (Ubuntu Noble)
Status: Fix Committed => Fix Released
** Description changed:
[Impact]
Linux kernel 6.2 includes patches with structural changes that may render the
crash
Updated the SRU template as requested in comment #11 with the detailed
test plans provided in comments #16-#20.
** Changed in: crash (Ubuntu Lunar)
Status: In Progress => Won't Fix
** Changed in: crash (Ubuntu Lunar)
Importance: Medium => Undecided
** Changed in: crash (Ubuntu Lunar)
Cloud Archive:
Caracal is addressed with Noble
Bobcat is addressed with Mantic
* Antelope is _not_ addressed with Lunar (no longer supported), needs patching
in UCA [Triaged]
Zed is no longer supported (2024/04)
Yoga is addressed with Jammy
Wallaby is no longer supported (2024/04)
Victoria is no
Cloud Archive:
Caracal is addressed with Noble
Bobcat is addressed with Mantic
* Antelope is _not_ addressed with Lunar (no longer supported), needs patching
in UCA [Triaged]
Zed is no longer supported (2024/04)
Yoga is addressed with Jammy
--
You received this bug notification because you are
Cloud Archive:
Caracal is addressed with Noble
Bobcat is addressed with Mantic
* Antelope is _not_ addressed with Lunar (no longer supported), needs patching
in UCA [Triaged]
Zed is no longer supported (2024/04)
Yoga is addressed with Jammy
--
You received this bug notification because you are
Uploaded to Mantic, Jammy, Focal.
This upload has been coordinated with the Openstack Engineering team
(~james-page) for bugs 1987663, 1988942, and 1994521.
Test PPA and build-time unit test summary in
https://bugs.launchpad.net/ubuntu/+source/cinder/+bug/1987663/comments/16
** Changed in:
** Changed in: cinder (Ubuntu Jammy)
Status: Incomplete => In Progress
** Changed in: cloud-archive/bobcat
Status: New => Fix Released
** Changed in: cloud-archive/antelope
Status: New => Triaged
** Changed in: cloud-archive/yoga
Status: New => In Progress
--
You
** Changed in: cloud-archive/antelope
Status: In Progress => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1988942
Title:
Failed to set image property. Invalid input for
Uploaded to Mantic, Jammy.
This upload has been coordinated with the Openstack Engineering team
(~james-page) for bugs 1987663, 1988942, and 1994521.
Test PPA and build-time unit test summary in
https://bugs.launchpad.net/ubuntu/+source/cinder/+bug/1987663/comments/16
--
You received this
Uploaded to Jammy.
This upload has been coordinated with the Openstack Engineering team
(~james-page) for bugs 1987663, 1988942, and 1994521.
Test PPA and build-time unit test summary in
https://bugs.launchpad.net/ubuntu/+source/cinder/+bug/1987663/comments/16
--
You received this bug
Hi Seyeong,
Thanks for the patches!
In the future, could you please add DEP-3 headers [1] to them?
(usually just 'Bug-Ubuntu:'/'Origin:' are needed on git patches)
Also, it's a good practice to name the patch files with the bug
prefix (this is style, not requirement, but it helps when there
is
The packages built successfully in Test PPA ppa:mfo/cinder-
lp1987663-lp1988942-lp1994521
All build-time unit tests passed in the Test PPA (as in the Ubuntu
Archive).
Mantic:
---
mantic-updates:
** Changed in: cloud-archive/zed
Status: In Progress => Won't Fix
** Changed in: cloud-archive/zed
Assignee: Jorge Merlino (jorge-merlino) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: cloud-archive/wallaby
Status: New => Won't Fix
** Changed in: cloud-archive/ussuri
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1987663
Title:
SRU team: this is on hold to double check the library symbols (thanks,
Robie!), please do not accept yet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059272
Title:
libvirt domain is not
Re: comment #13, I had re-tested Mantic, Jammy, and Focal with/without
the patch (they all work/fail as expected), but forgot to update the
bug.
** Changed in: cinder (Ubuntu Lunar)
Importance: Medium => Undecided
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Hey Seyeong, Dariusz,
Thanks for the clarifications!
Yes, this needs coordination with the Openstack Engineering team
not only for the other changes they plan to combine in an upload,
but also regarding the upstream acceptance situation for this in
the different branches.
Apparently, they still
Hi Sergio,
Thanks for taking the time to read and review the patch and test cases!
> this new code path could be reached even after the initialization,
couldn't it?
No, this code path should only be reached during initialization, AFAICT.
That is because qemuProcessReconnect() can only be
Hello thom, or anyone else affected,
Accepted pathological into jammy-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/pathological/1.1.3-16ubuntu0.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package.
Hi Sudip, Dave (uploader),
Thanks for the patch for Ubuntu!
These changes do not modify the DEP3 headers of the existing
python3.patch file.
For SRUs, it's good practice to add 'Bug-Ubuntu:' / 'Origin:' tags, and in the
case the .patch file already exists, a 'Last-Update:' tag too would be
** Description changed:
[ Impact ]
pathological is completely unusable as none of the keyboard or mouse
input will work. And the game can not be played if the user can not
control the game.
[ Test Plan ]
1. Install pathologial
2. Use up-down keys to check if different
Hello DarkTrick, or anyone else affected,
Accepted numptyphysics into focal-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/numptyphysics/0.2+svn157-0.4ubuntu0.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new
Notes:
- Version with the patch [0] (0.2+svn157-0.5) was introduced in Ubuntu on
Impish [1]
(older than Jammy in the SRU template, so updated the SRU template to increase
version range it has been applied in Ubuntu).
- The DEP-3 field 'Origin:' has an invalid optional prefix 'Debian';
it should
** Description changed:
[ Impact ]
numptyphysics is completely unusable as it will segfault immediately on
start.
[ Test Plan ]
1. Install numptyphysics
2. Start numptyphysics
3. Play the game to check it works
If the package is not fixed then it will fail to start.
-
Seyeong, Dariusz (subscribing you as you're the uploader),
Could you please confirm whether the Openstack Engineering team
is OK with the proposed changes, and that they are not upstream?
From comment #12 it seems unclear whether the situation could
move forward, and the SRU template was updated
Hello Graham, or anyone else affected,
Accepted boinc into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/boinc/7.18.1+dfsg-4ubuntu0.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Looked at potential performance regressions of removing AVX instructions.
(Updated the SRU template sections accordingly.)
The boinc packages do not provide high-performance code, it's the boinc
_applications_ written to be run by the client and linked against the
library for API access that
** Description changed:
[ Impact ]
boinc-client is completely unusable on older CPU which does not have avx like
a Celeron CPU.
It will crash immediately if run on old CPU, but will run without any problem
on newer CPUs.
[ Test Plan ]
It should be done on both types of CPUs,
Marked bug 1988863 as a duplicate.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970521
Title:
[SRU] boinc-client crashes when started with core dump on Xubuntu
22.04
To manage notifications
*** This bug is a duplicate of bug 1970521 ***
https://bugs.launchpad.net/bugs/1970521
** This bug has been marked a duplicate of bug 1970521
[SRU] boinc-client crashes when started with core dump on Xubuntu 22.04
--
You received this bug notification because you are a member of Ubuntu
Hello Nathaniel, or anyone else affected,
Accepted macutils into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/macutils/2.0b3-16ubuntu0.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
$ lsb_release -cs; dpkg -s macutils | grep ^Version:; dpkg -L macutils | grep
/bin/ | while read BIN; do echo $BIN; $BIN -H >/dev/null 2>&1; echo RC = $?;
done
focal
Version: 2.0b3-16build1
/usr/bin/binhex
RC = 139
/usr/bin/frommac
RC = 139
/usr/bin/hexbin
RC = 0
/usr/bin/macsave
RC = 0
Hi Sudip,
Thanks for debugging, backporting, and submitting a patch!
Nice touch on the DEP-3 headers.
Just a style/cosmetic _suggestion_ that is helpful: in the
future, please list the .patch file in d/changelog; e.g.,
'* d/p/fix-segfault.patch: Fix segfault with binhex, frommac and tomac. (LP:
Steps with test packages on Focal (shutdown-on-runtime)
---
Stop libvirtd systemd units
sudo systemctl stop 'libvirtd*'
Start libvirt in GDB
sudo gdb \
-iex 'set confirm off' \
-iex 'set pagination off' \
-ex 'set non-stop on' \
-ex 'handle SIGTERM nostop noprint
1 - 100 of 1748 matches
Mail list logo
