Hey, we've been discussing this in the release sprint.
While it is a goal to get all buildable, but it is probably too late for this.
If it needs an SRU it would need to be fixed as part of that.
FYI -8 also was FTBFS https://launchpad.net/ubuntu/+source/mir/2.14.1-8
The request then was to remove
Hey, we've been discussing this in the release sprint.
While it is a goal to get all buildable, but it is probably too late for this.
If it needs an SRU it would need to be fixed as part of that.
FYI -8 also was FTBFS https://launchpad.net/ubuntu/+source/mir/2.14.1-8
The request then was to remove
Matthieu reached out to Simon, we will revert is as suggested - Ural is
on it
** Changed in: zsync (Ubuntu)
Assignee: Simon Quigley (tsimonq2) => Ural Tunaboyu (uralt)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
Matthieu reached out to Simon, we will revert is as suggested - Ural is
on it
** Changed in: zsync (Ubuntu)
Assignee: Simon Quigley (tsimonq2) => Ural Tunaboyu (uralt)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
I know the subiquity(ubuntu) isn't needed for your work on it - but it
allows us to assign it to the milestone and thereby to keep it on our
minds as an important blocker.
** Also affects: subiquity (Ubuntu)
Importance: Undecided
Status: New
** Changed in: subiquity (Ubuntu)
Stat
*** This bug is a duplicate of bug 2083293 ***
https://bugs.launchpad.net/bugs/2083293
** This bug has been marked a duplicate of bug 2083293
[SRU] [GNR] Virt-Libvirt: Add platform support to libvirt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Yeah, machine types the most common place for mistakes if you ask me.
Good: For noble this is a no-op - the offending change was in 9.0
(oracular) so noble is not affected in the first place.
Good: Plucky is not yet released, this change looks fine, and we'll try
to fix it asap before release to
Guillaume might update with better words and details, but here a half informed
FYI
- upstream acknowledged the problem and works on it
- the change is likely bigger changing the dependency entirely
- Therefore we expect a bigger than usual SRU change throughout plucky
- Openstack team will release
** Also affects: ubuntu-release-notes
Importance: Undecided
Status: New
** Changed in: ubuntu-release-notes
Assignee: (unassigned) => Guillaume Boutry (gboutry)
** Changed in: nova (Ubuntu)
Milestone: ubuntu-25.04 => None
--
You received this bug notification because you are
** Also affects: ubuntu-release-notes
Importance: Undecided
Status: New
** Changed in: ubuntu-release-notes
Assignee: (unassigned) => Guillaume Boutry (gboutry)
** Changed in: nova (Ubuntu)
Milestone: ubuntu-25.04 => None
--
You received this bug notification because you are
** Changed in: qemu (Ubuntu Plucky)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2106092
Title:
ppc/spapr: fix default cpu for pre-9.0 machines (Backport
This is a pure bug-fix and thereby does not need an FFE.
But it shall be urgent to not mess up image creation next week.
Approval and Tests are good - uploaded
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
** Also affects: cloud-archive
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2088451
Title:
[SRU] datetime fix introduces runtime dependency on oslo.utils
FYI
MR (plucky):
https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/484135
PPA:
https://launchpad.net/~paelzer/+archive/ubuntu/lp-2106092-ppc-spapr-cpu-type
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
existence of edge cases - WDYT?
Or am I overlooking how common that scenario would be?
> --
> debian developer - deb.li/jak | jak-linux.org - free software dev
> ubuntu core developer i speak de, en
> --
> ubuntu-devel mailing list
> ubuntu-devel@lists.
On Mon, Apr 7, 2025 at 4:46 PM Robie Basak wrote:
>
> On Fri, Apr 04, 2025 at 08:42:44AM +0200, Christian Ehrhardt wrote:
> > I've prepared a - not necessarily complete - conversion of this
> > discussion to a PR [3].
>
> Thanks - this is great!
Already polis
This has been in component mismatches today, as it is late it has an FFE
now (here) and also the MIRs are approved (which all have worked on for
a while).
I've promoted them accordingly.
This should thereby hopefully migrate soon.
--
You received this bug notification because you are a member of
This has been in component mismatches today, as it is late it has an FFE
now (here) and also the MIRs are approved (which all have worked on for
a while).
I've promoted them accordingly.
This should thereby hopefully migrate soon.
--
You received this bug notification because you are a member of
This has been in component mismatches today, as it is late it has an FFE
now (here) and also the MIRs are approved (which all have worked on for
a while).
I've promoted them accordingly.
This should thereby hopefully migrate soon.
--
You received this bug notification because you are a member of
This is now in -proposed, via
https://launchpad.net/ubuntu/+source/gnome-control-center/1:48.0-1ubuntu2
https://launchpad.net/ubuntu/+source/webkit2gtk/2.48.1-1ubuntu1
as tracked and FFE approved in
https://bugs.launchpad.net/ubuntu/+source/jpeg-xl/+bug/2099691
Nothing in proposed to consider, al
This is now in -proposed, via
https://launchpad.net/ubuntu/+source/gnome-control-center/1:48.0-1ubuntu2
https://launchpad.net/ubuntu/+source/webkit2gtk/2.48.1-1ubuntu1
as tracked and FFE approved in
https://bugs.launchpad.net/ubuntu/+source/jpeg-xl/+bug/2099691
Nothing in proposed to consider, al
This is now in -proposed, via
https://launchpad.net/ubuntu/+source/gnome-control-center/1:48.0-1ubuntu2
https://launchpad.net/ubuntu/+source/webkit2gtk/2.48.1-1ubuntu1
as tracked and FFE approved in
https://bugs.launchpad.net/ubuntu/+source/jpeg-xl/+bug/2099691
Nothing in proposed to consider, al
This is now in -proposed, via
https://launchpad.net/ubuntu/+source/gnome-control-center/1:48.0-1ubuntu2
https://launchpad.net/ubuntu/+source/webkit2gtk/2.48.1-1ubuntu1
as tracked and FFE approved in
https://bugs.launchpad.net/ubuntu/+source/jpeg-xl/+bug/2099691
Nothing in proposed to consider, al
Thank you for filing this, I can confirm that this "upstream releases
quite close to the Ubuntu release, therefore go git-based first and bump
to the final version before we release" model has been what we used for
several years.
I co maintain this in Debian with Frode and Luca and can confirm tha
Assigning to jeremy to represent the work he mentioned to go for in the
MIR meeting:
[16:56] yes, I'm still able to land enabling jpeg-xl if the MIR
is complete this week. I need to get the FFe approved for it then too.
This week leaves time before Final Freeze
--
You received this bug notifica
Trying to see if all is ready
- #1 further drivers
First of all thanks Daniel for the answer.
But if "please treat it like that - recommended for optimal experience but
not something we are allowed to install by default" is the way it needs to
be in plucky this way.
Sorry that being paten
FYI https://github.com/libjxl/libjxl/pull/4111 was merged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2070882
Title:
[MIR] jpeg-xl
To manage notifications about this bug go to:
https://bugs.launc
Actually it had the right state already since the security review.
And [1] also disables trace as recommended by security - thanks.
So all we are waiting is freeze lift, upload, promote then ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
Uploaded as part of bug 2098005
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2103416
Title:
[clang-tidy 20] warning: argument unused during compilation: '-c' when
using compilation database
To m
Trying to see if all is ready
- #1 further drivers
First of all thanks Daniel for the answer.
But if "please treat it like that - recommended for optimal experience but
not something we are allowed to install by default" is the way it needs to
be in plucky this way.
Sorry that being paten
MR reviewed, fixed up and maint scripts verified against PPA.
Uploading ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2105496
Title:
Avoid misguided conffile transfer in Plucky
To manage notifi
Hi again,
now all puzzle pieces fit together - thank you, no further questions needed.
This is not a bug as in "this has broken" it is a "feature request" in
regard to qemu and edk2 at the versions they've been available at the
time of Ubuntu Noble.
Yet, despite being a feature request it is stil
Reviewed (all good) and sponsored (which also included fix for bug
2103416).
Uploading xdp-tools_1.5.1-1ubuntu2.dsc
Uploading xdp-tools_1.5.1-1ubuntu2.debian.tar.xz
Uploading xdp-tools_1.5.1-1ubuntu2_source.buildinfo
Uploading xdp-tools_1.5.1-1ubuntu2_source.changes
--
You received this bug noti
Seen the case, discussed the case, agreeing.
Fine to be done in a controlled way in 25.10 and to remove now as we need a
newer version anyway.
That will clean up plucky a bit more towards the release.
./remove-package -m "LP: #2103795 depends on rack 3.0, which is for Ubuntu
25.10" -s plucky-pr
[1]:
https://canonical-ubuntu-packaging-guide.readthedocs-hosted.com/en/latest/reference/package-version-format/
[2]:
https://github.com/canonical/ubuntu-maintainers-handbook/blob/main/VersionStrings.md
[3]: https://github.com/canonical/ubuntu-maintainers-handbook/pull/161
> mwh
>
>
I've checked test fails (the bot missed the update but Andreas told me - BIG
THANKS).
All have been just flaky infra - they are all good now.
One oddity - 3x armhf is still accounted as "in progress" but I can see they
are good.
Do I have to do something about it?
--
You received this bug noti
** Changed in: nova (Ubuntu)
Milestone: None => ubuntu-25.04
** Changed in: nova (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2103413
Title:
Pytho
Hey,
thanks for explaining the background so well - we all have been there at the
uncertainty if all will be ready to make a particular switch. We didn't switch
to MIR 2.20 as you say and it is too late to try.
Hence
I'm unsure on mir (at first).
It is not that we'd remove an unintended 2.20, w
Hey,
thanks for explaining the background so well - we all have been there at the
uncertainty if all will be ready to make a particular switch. We didn't switch
to MIR 2.20 as you say and it is too late to try.
Hence
I'm unsure on mir (at first).
It is not that we'd remove an unintended 2.20, w
Sad but true, that is how things evolve. You are closer to desktop and tell me
touch support has improved.
And no development in 13 years and no new upload in 5 is a too long time.
If we ignore no change rebuilds for dependencies and FTBFS fixes that
have just been done due to archive rebuilds th
Indeed, the patch to make it pcre2 (yes newer than 3) compatible was provided.
And when fixed it can come back.
Also upstream has 3 new releases 0.36, 1.0, 1.10, 1.11 which if keeping make
sense to have.
And yes, ktx is more or less an extension to mvdsv, so it has to go away
as well.
I love suc
It is not even a real removal like "won't be here afterwards".
They have been renamed, and we have the new around.
old
rust-trust-dns-resolver | 0.22.0-4 | plucky/universe | source
rust-trust-dns-client | 0.22.0-5 | plucky/universe | source
rust-trust-dns-recursor | 0.22.0-2 | plucky/univer
Agreed, it has no revdep not even the weird ones on the provides.
./checkrdepends --no-ports --include-provides --suite plucky --archive-base
'http://archive.ubuntu.com/ubuntu' rust-unzip
The reasoning in the Debian bug is clear, agree to remove in the current
state to clean plucky before relea
Sorry, I was first distracting myself running the test against noble
which showed rev-deps (rust style build deps)
./checkrdepends --no-ports --include-provides --suite noble --archive-base
'http://archive.ubuntu.com/ubuntu' rust-skeptic
-- noble/universe build deps on librust-skeptic-0.13+defaul
Just like with pcs, I've discussed and looked into the case.
The former version 2.2.7-1.1 is fine in plucky and 3.x is for 25.10.
Let us not late-break plucky forcing this too much and too late and instead do
it well next cycle.
Agreeing to the removal of the -proposed version, the sync/merge of
This is handled (thanks Colin), and also superseded (6.5-3 has valid armhf
builds).
Let us set this to fix relased twice :-)
** Changed in: nfs-ganesha (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Assigning to jeremy to represent the work he mentioned to go for in the
MIR meeting:
[16:56] yes, I'm still able to land enabling jpeg-xl if the MIR
is complete this week. I need to get the FFe approved for it then too.
This week leaves time before Final Freeze
--
You received this bug notifica
As it was a sync the changelog didn't have the bug, but it fully migrated
See: https://launchpad.net/ubuntu/+source/ovn/25.03.0-1
Hence we can mark this fix released.
** Changed in: ovn (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a membe
Right now, in plucky this is out of proposed and hence we see no component
mismatch (adapting state).
But if the release team FFE's the case you might go for it as both cases bug
2070807 and bug 2070882 are ready.
** Changed in: highway (Ubuntu)
Status: Fix Committed => In Progress
** Ch
Right now, in plucky this is out of proposed and hence we see no component
mismatch (state is correct).
But if the release team FFE's the case you might go for it as both cases bug
2070807 and bug 2070882 are ready.
** Changed in: jpeg-xl (Ubuntu)
Assignee: (unassigned) => Jeremy Bícha (jbi
FYI - test issues resolved, verification of the case still needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077336
Title:
Creation of armv7l vm fails due to tpm-tis
To manage notifications abo
Subscribing release team and targetting milestone to ensure this isn't lost.
We likely upload the fix on Wednesday.
** Changed in: libvirt (Ubuntu)
Milestone: None => ubuntu-25.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
Public bug reported:
Back in 10.6.0-2 (right after where we branched for oracular) we changed
a lot of wher which files reside. That was yet another step in splitting
up libvirt which Ubuntu fully joined a while ago.
But it was found in Debian (https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=1
PPA: https://launchpad.net/~paelzer/+archive/ubuntu/fix-conffile-transfer-plucky
MR:
https://code.launchpad.net/~paelzer/ubuntu/+source/libvirt/+git/libvirt/+merge/483623
** Changed in: libvirt (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are
Pushkar went for the small fix for plucky, thanks!
The bit wider rework has thereby some time and cna wait in VCS until needed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2104238
Title:
no more d
The whole build is very outdated, I think even changing the project
itself away from the build tools would be too much so late, but
modernizing the debian/* build instructions to this year will make it
work well.
=> https://code.launchpad.net/~paelzer/uvtool/+git/uvtool/+merge/483562
--
You rece
Turns out it also was unbuildable, need to fix this common change in
uvtool too:
I: pybuild base:311: python3.13 setup.py clean
Traceback (most recent call last):
File "/<>/setup.py", line 17, in
import distutils.core
ModuleNotFoundError: No module named 'distutils'
E: pybuild pybuild:389:
Actually it had the right state already since the security review.
And [1] also disables trace as recommended by security - thanks.
So all we are waiting is freeze lift, upload, promote then ...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, whic
Public bug reported:
converting a MR to a bug for tracking:
Starting with Plucky, ssh-keygen no longer supports DSA keys and running
`ssh-keygen -t dsa` errors out with "unknown key type dsa". This is
propagated to `uvt-kvm`, so running `uvt-kvm create` displays that
message each time. Fix that b
Hey,
I was merging a similar fix - but it isn't entirely the same.
I assume cloud-init wants something better/different from us now.
uvtool builds a rather basic config, cloud-init folks could you advise
what config change you'd need to get away from this?
In regard to disliked dsa keys, is this
Uploaded to plucky
Uploading uvtool_0~git187-0ubuntu1.dsc
Uploading uvtool_0~git187.orig.tar.xz
Uploading uvtool_0~git187-0ubuntu1.debian.tar.xz
Uploading uvtool_0~git187-0ubuntu1_source.buildinfo
Uploading uvtool_0~git187-0ubuntu1_source.changes
--
You received this bug notification because you
Promoting this (component moves are not an issue for the beta freeze)
now:
- It is only in plucky, but not plucky proposed
./change-override --component main --suite plucky --source-and-binary
libsass-python
Override component to main
libsass-python 0.23.0-0.1ubuntu1 in plucky: universe/misc ->
Thank you for confirming the use case context for who can provide themes.
The same consideration has to be done for anyone else using it, but that is
kind of normal.
You have fulfilled all we asked for in this and the related case.
Promoting (not bound to the freeze) to unblock you.
./change-ove
Thank you for all the info.
For now this is all I can ask for.
We will need to find some time recreating it on our side to let you know if we
need more.
** Changed in: edk2 (Ubuntu)
Status: Incomplete => Triaged
** Tags added: server-todo
--
You received this bug notification because yo
Thanks with that this seems ready
** Changed in: libsass (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2095582
Title:
[MIR] libsass
To manage n
Dependency is ready now
** Changed in: libsass-python (Ubuntu)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2095581
Title:
[MIR] libsass-python
To manag
Thank you for that early finding of your evaluation!
Indeed an upstream (In this case Canonical) is expected to regularly keep their
dependencies up to date to resolve such issues.
Furthermore the owning team (in this case also Canonical) is required to
make adaptions so it can build well in all
Thank you for that early finding of your evaluation!
Indeed an upstream (In this case Canonical) is expected to regularly keep their
dependencies up to date to resolve such issues.
Furthermore the owning team (in this case also Canonical) is required to
make adaptions so it can build well in all
Hi,
a few questions to help us looking into that.
#1 isolate it better when it changed
So far you seem to have two results
1. What is in noble (failing)
2. latest upstream (working)
Do you have access to any in between builds so we can isolate when a fix might
have landed upstream?
If you have
*** This bug is a duplicate of bug 2104069 ***
https://bugs.launchpad.net/bugs/2104069
** This bug has been marked a duplicate of bug 2104069
OVMF.fd file doesn't support SNP QEMU Guest Launch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Thanks - This will come in with the normal merge for 25.10, no need to
add it in extra tracking via more tags.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2027925
Title:
[25.10 FEAT] [VS2218] KVM:
Due to my bad I accepted the wrong 0.1.0 - thanks for the ping Guillaume.
Fixed up in 0.2.0 in the git repo and a renewed upload.
P.S. Launchpad had 3 build infra issues in a row ... - not a good day
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
No beta freeze yet (but close), uploading ...
Uploading regress-stack_0.1.0.dsc
Uploading regress-stack_0.1.0.tar.xz
Uploading regress-stack_0.1.0_source.buildinfo
Uploading regress-stack_0.1.0_source.changes
Compared and accepted in NEW queue for plucky ...
Checking the build and the binary new
https://launchpad.net/ubuntu/+source/regress-stack exists now
So does https://launchpad.net/ubuntu/+source/regress-stack/0.1.0
let us hope it goes as smooth as in the pre-tests :-)
** Also affects: regress-stack (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: ubuntu
NEW queue
- package namespace - seems safe
- licenses are all mentioned in LICENSES and d/copyright
- Ensuring correct component based on license => universe
- n/a for checks in regard to
- Debian state - as it is not in Debian
- not targeted at stable releases
- expected binaries arch:all pyth
Hi,
thanks for the tracking bug.
I agree that it is not a classic Feature Freeze exception, but I'd
need/want a bug to associate the upload with anyway to leave any further
comment or progress. Like the "... make sure you have the agreement of
a member of ~ubuntu-archive ..."
I've reviewed and d
Also mentioned on the release notes as Jon asked for it.
** Changed in: ubuntu-release-notes
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2101864
Title:
[F
Oracular
Before:
root@o:~# tail -f /var/log/syslog | grep snmpd
2025-03-17T08:59:42.421682+00:00 o systemd[1]: Starting snmpd.service - Simple
Network Management Protocol (SNMP) Daemon
2025-03-17T08:59:42.486725+00:00 o snmpd[4231]: systemstats_linux: unexpected
header length in /proc/net/sn
Jammy
before
root@j:~# tail -f /var/log/syslog | grep snmpd
Mar 17 08:58:56 j snmpd[1647]: systemstats_linux: unexpected header length in
/proc/net/snmp. 237 != 224
Mar 17 08:58:56 j snmpd[1647]: message repeated 2 times: [ systemstats_linux:
unexpected header length in /proc/net/snmp. 237 != 22
This bug was fixed in the package fish - 4.0.1-1
---
fish (4.0.1-1) unstable; urgency=medium
* New upstream version 4.0.1
* Drop cherry-picked patches that are already merged in 4.0.1.
* Refresh existing patches.
-- Mo Zhou Thu, 13 Mar 2025 19:01:18 -0400
** Changed in: fis
Thanks for the pre-check, also avoids some exploding mismatches until it
is demoted based on the lack of dependencies.
./change-override --component universe --suite plucky-proposed --version
8.4.2-1ubuntu1 php8.4-zip php8.4-dba php8.4-interbase
Override component to universe
php8.4-zip 8.4.2-1ub
Saw this update fly by and wanted to clarify that the question in comment #27
is still open.
Also helping the state of related bugs 2085535 and 2086203 a little...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
I expected to get to it Sat morning, but found that Mo Zhou already pushed
4.0.1 to Debian.
Builds look good (or still queued) right now:
https://buildd.debian.org/status/package.php?p=fish
That makes it even easier, since it is a fix only release over the former no
need for extra paperwork.
sy
Thank you so much Fabian for chiming in,
and I mean not just for helping with this detail on this case, but for watching
this category at all!
I'll bump it to 4.0.1 as soon as I get to it
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
Hi Markus and thanks for the always great prep when reporting such.
The patches are already in upstream qemu v9.2 which we have in Plucky.
Let us check if they can be backported without breakage to the most recent LTS.
In this particular case it will indeed be more regression tests, as I'd
want t
It can never be easy, one of the further dependency tests failed.
Of course only on armhf to make it harder and slower to setup and debug
... :-/
=> https://autopkgtest.ubuntu.com/results/autopkgtest-
plucky/plucky/armhf/k/kworkflow/20250312_200138_80d67@/log.gz
239s Running test [fish_completio
All findings resolved, uploaded to SRU this on J/N/O
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056257
Title:
unexpected header length in /proc/net/snmp
To manage notifications about this bug g
As expected x86 is reliably fine
root@p:~/kworkflow-20191112# apt policy fish
fish:
Installed: 4.0.0-3
Candidate: 4.0.0-3
Version table:
*** 4.0.0-3 100
100 http://archive.ubuntu.com/ubuntu plucky-proposed/universe amd64
Packages
100 /var/lib/dpkg/status
root@p:~/kworkflow-
** Description changed:
+ [ Impact ]
+
+ * KVM virtual machines do not currently attempt booting from multiple
+ targets, as defined by the targets' boot order properties.
+
+ * Therefore, users cannot utilize existing management frameworks to
+ control their boot order on CCW devices for mult
Awesome for cross checking - thanks Mohammed.
Hector also offered to test this on an Intel machine he has, which might
help eventually verifying this on all releases.
I've reviewed the MRs and the look good to me.
We should upload it soon to plucky and then group this with other ready
SRUs.
--
This is indeed good for itself, but still waiting for
https://bugs.launchpad.net/ubuntu/+source/nlohmann-json3/+bug/2093868 to
complete.
That is on security atm and per
(https://bugs.launchpad.net/ubuntu/+source/nlohmann-json3/+bug/2093868/comments/18)
otherwise also fine to go.
--
You receiv
Qemu:
6d5e9694e : target/i386: Add new CPU model GraniteRapids
$ git tag --contains 6d5e9694ef374159072984c0958c3eaab6dd1d52 | grep '^v' |
head -n 1
v8.1.0
That is in Noble 1:8.2.2+ds-0ubuntu1.6 which is the target.
So qemu should be fine
** Also affects: qemu (Ubuntu)
Importance: Undecided
** Changed in: qemu (Ubuntu Jammy)
Assignee: Christian Ehrhardt (paelzer) => (unassigned)
** Tags removed: server-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2084459
Title:
Windows
Thank you for the confirming answer utkarsh.
Synced: https://launchpad.net/ubuntu/+source/fish/4.0.0-3
I'll add to release notes once it really made it over.
** Also affects: ubuntu-release-notes
Importance: Undecided
Status: New
** Changed in: ubuntu-release-notes
Status: New
The state fully resolved, oddity is gone - all correctly have one state
now (in main).
Once the new migrates I expect/hope that the old src:tracker based
things are replaced (those with the same name) or removed (you'd let us
know for deletion) or demoted (if no more needed they should show up in
@jeremy - I'm unsure if I remember correctly.
This was a fast path promotion based on "it is the same but renamed", yet I do
not remember well.
Was this one of the cases that we should enqueue for re-review?
If yes - please set it to new, jaolif is already assigned and will get
to it then.
Or i
The state fully resolved, oddity is gone - all correctly have one state
now (in main).
Once the new migrates I expect/hope that the old src:tracker based
things are replaced (those with the same name) or removed (you'd let us
know for deletion) or demoted (if no more needed they should show up in
LGTM, thank you for getting this migration into the final state.
It also allows us to get rid of all the "version+oldversion" cases.
That should include php8.3-pspell 8.3.11-0ubuntu4 right?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Public bug reported:
Hi,
Fish was rewritten entirely in rust [1] and that made it into 4.0.
It happened to land in Debian just after the freezes have been put in place.
It is one of the modern tools we might want to have a deeper look at,
adding that to plucky would allow all our users to give it
This is fine for a fast-path based on the old approval.
=> Setting the state.
But you need to make it show up in component mismatches for us to act on it
though.
Then i can fix subscription and promote it.
Once over and happy we can also act on bug 2101155 then.
** Changed in: php8.4 (Ubuntu)
1 - 100 of 1903 matches
Mail list logo
