** Description changed:
[Impact]
- * An explanation of the effects of the bug on users and
- justification for backporting the fix to the stable release.
+ Currently, the default chrony.conf configures a set of pools. If a user
wishes to use only a specific server/server pool or not use the d
Hi Bryce,
Addressing your feedback per point from comment #12
0. I have put an MP for review[0] instead of a debdiff for this iteration.
Please let me know if that's the appropriate way to propose changes to server
packages. git-ubuntu is definitely on my list to learn now.
1. I concur with this
Public bug reported:
Now that 24.04.1 has been released, 22.04 users are encouraged to upgrade to
24.04 via the `do-release-upgrade` command. This issue was seen whilst testing
this upgrade path.
Upgrading and later rebooting a jammy GCP instance results in
`linux-headers-6.5.0-1025-gcp` being
** Description changed:
Now that 24.04.1 has been released, 22.04 users are encouraged to upgrade to
24.04 via the `do-release-upgrade` command. This issue was seen whilst testing
this upgrade path.
Upgrading and later rebooting a jammy GCP instance results in
`linux-headers-6.5.0-1025-gcp`
** Attachment added: "Uploading the required dist-upgrade information"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2078720/+attachment/5812723/+files/dist-upgrade.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
** Attachment added: "apport file"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2078720/+attachment/5812724/+files/apport.ubuntu-release-upgrader-core.5vja_xtr.apport
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
Issue was reproducible on jammy generic[0] and kvm[1] download images
too.
Generic download image
```
$ sudo apt install
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following
Public bug reported:
A CPC snap preseeding test failure on arm64 is blocking image pulication.
A recent update, specifically 6.5.0.1017.17~22.04.1, to the jammy 6.5 kernel
introduced AppArmor new profile `unconfined_restrictions`. This is not
reflected in the snap preseeding code and needs to be
** Description changed:
A CPC snap preseeding test failure on arm64 is blocking image pulication.
- A recent update, specifically 6.5.0.1017.17~22.04.1, to the jammy 6.5 kernel
introduced AppArmor new profile `unconfined_restrictions`. This is not
reflected in the snap preseeding code and need
This bug also affects the mantic 6.5 kernel.
** Summary changed:
- AppArmor profile policy `unconfined_restrictions` missing for jammy 6.5 kernel
+ AppArmor profile policy `unconfined_restrictions` missing for jammy and
mantic 6.5 kernel
--
You received this bug notification because you are a
** Description changed:
A CPC snap preseeding test failure on arm64 is blocking image pulication.
A recent update, specifically 6.5.0.1017.17~22.04.1, to the jammy 6.5 kernel
introduced a new AppArmor profile `unconfined_restrictions`. This is not
reflected in the snap preseeding code and ne
I have tested the package in proposed. The test was done by building a
GCE image with the linux-gcp-edge kernel using livecd-rootfs from
proposed. Confirmed the following:
```
$ uname -r
6.8.0-1012-gcp
$ snap debug seeding
seeded:true
preseeded: true
image-preseeding: 12.545s
@utkarsh mentioned he was looking into the s390x autopkgtest failure.
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Hi Bryce,
Apologies for the delay in responding.
Thank you for your review comments I'll try to address them in my next fix
proposal.
With respect to the suggesstion you shared about handling well known cases I'll
give it some thought myself , discuss it within my squad, gather feedback and
re
@racb RE comment #4
As far as I understand the only reason the jammy approval should block on
mantic approval is that the approvals must happen in the order of releases with
later release being before an older release.
--
You received this bug notification because you are a member of Ubuntu
Bug
Hello Andreas,
The CPC jammy and mantic fork of livecd-rootfs have been patched with the fix
for this bug since 30 April 2024. Since then CPC have built and tested several
images with the patched CPC livecd-rootfs fork.
As a part of our testing we run an automated test that follows the steps lis
Public bug reported:
"systemctl status ssh" and "systemctl status sshd" both work in jammy, but only
"systemctl status ssh" works in noble.
Expected behavior is that "systemctl status sshd" should work on noble too.
The ssh.service file contains "Alias=sshd.service" but this does not seem to be
Public bug reported:
noble minimal cloud images don't have sosreport installed.
This is a regression from jammy where the package was a part of minimal images.
For ex. see noble download image manifest[0] vs jammy download image
manifest[1].
This is likely a bug in the ubuntu-cloud-minimal packag
Public bug reported:
noble minimal cloud images don't have mdadm installed.
This is a regression from jammy where the package was a part of minimal images.
For ex. see noble download image manifest[0] vs jammy download image
manifest[1].
This is likely a bug in the ubuntu-cloud-minimal package.
** Summary changed:
- noble minimal cloud images don't have mdadm package installed Edit
+ noble minimal cloud images don't have mdadm package installed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2
Public bug reported:
tracking bug
** Affects: python-av (Ubuntu)
Importance: Undecided
Assignee: Ankush Pathak (ankushpathak)
Status: In Progress
** Changed in: python-av (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you ar
PPA with the merge:
https://launchpad.net/~ankushpathak/+archive/ubuntu/questing-python-av-
merge-lp2110484
Autopkg tests look good:
- python-av: questing/python-av/14.2.0-1ubuntu1 [amd64]
+ ✅ python-av on questing for amd64 @ 15.05.25 07:33:01
• Log:
https://autopkgtest.ubuntu.com/
** Merge proposal linked:
https://code.launchpad.net/~ankushpathak/ubuntu/+source/python-av/+git/python-av/+merge/486137
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2110484
Title:
Please merge
/+source/rails/2:7.2.2.1+dfsg-7/+build/30675686
Potentially related upstream discussions:
* https://github.com/rails/rails/issues/54260
* https://github.com/ruby-concurrency/concurrent-ruby/issues/1077
** Affects: rails (Ubuntu)
Importance: Undecided
Assignee: Ankush Pathak (ankushpathak
Confirmed locally that pinning ruby-concurrent to 1.3.4 in the build
chroot leads to a successful build. This workaround was suggested
here[0].
The issue does not appear in debian builds[1] probably because at build time
the debian archive already had ruby-activesupport version 2:7.2.2.1+dfsg-6.
PPA with test build:
https://launchpad.net/~ankushpathak/+archive/ubuntu/lp2111952-test-remmina
MP:
https://code.launchpad.net/~ankushpathak/ubuntu/+source/remmina/+git/remmina/+merge/486624
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
** Changed in: python-av (Ubuntu)
Status: Fix Committed => 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/2110484
Title:
Please merge 14.2.0-1 into questing
To manage notificatio
** Changed in: remmina (Ubuntu Noble)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2111952
Title:
Remmina prompts for RDP credentials even when they are sav
Tested version 1.4.35+dfsg-2ubuntu0.1 from oracular-proposed against all
the scenarios in the test plan. The test was done on an Oracular Virtual
Box VM attempting to connect to a Raspberry Pi on the local network.
* Remmina does not produce a prompt when Username and Password fields
are correctly
na/-/merge_requests/2592/diffs
** Also affects: remmina (Ubuntu Oracular)
Importance: Undecided
Status: New
** Changed in: remmina (Ubuntu Oracular)
Status: New => In Progress
** Changed in: remmina (Ubuntu Oracular)
Assignee: (unassigned) => Ankush Pathak (anku
** Merge proposal linked:
https://code.launchpad.net/~ankushpathak/ubuntu/+source/pam/+git/pam/+merge/487215
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2112053
Title:
Merge pam from Debian Un
PPA:
https://launchpad.net/~ankushpathak/+archive/ubuntu/lp2112016-jq-questing-merge
Smoke tested the following commands on a lxc questing container
```
# echo '{"messages": ["Hello", "world"]}' | jq '.messages | length'
2
# echo '{"messages": ["Hello", "world"]}' | jq
{
"messages": [
"Hello
Confirmed bug is present in noble but not in jammy. Hence, marking jammy
as invalid.
I confirmed by setting up a noble and jammy Vitrual Box VM that had
Remmina installed. I setup a profile with credentials to RDP into an
Rasperry Pi on my local network and checked if I got a prompt when
trying to
** Changed in: jq (Ubuntu)
Assignee: (unassigned) => Ankush Pathak (ankushpathak)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2112016
Title:
Merge jq from Debian Unstable for questing
** Changed in: plocate (Ubuntu)
Assignee: (unassigned) => Ankush Pathak (ankushpathak)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2112057
Title:
Merge plocate from Debian Unstable
** Changed in: pam (Ubuntu)
Assignee: (unassigned) => Ankush Pathak (ankushpathak)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2112053
Title:
Merge pam from Debian Unstable for questing
** Changed in: iputils (Ubuntu)
Assignee: (unassigned) => Ankush Pathak (ankushpathak)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2112014
Title:
Merge iputils from Debian Unstable
** Changed in: remmina (Ubuntu Jammy)
Assignee: (unassigned) => Ankush Pathak (ankushpathak)
** Changed in: remmina (Ubuntu Noble)
Assignee: (unassigned) => Ankush Pathak (ankushpathak)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
** Merge proposal linked:
https://code.launchpad.net/~ankushpathak/ubuntu/+source/plocate/+git/plocate/+merge/486706
** Changed in: plocate (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
** Changed in: pam (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2112053
Title:
Merge pam from Debian Unstable for questing
To manage notifications ab
@utkarsh looked into this further. Summarizing his findings and resolution
below.
ruby-concurrent was causing more FTBS', for ex. ruby-roadies-rails[0], along
with some autopkgtest regressions.
The most straightforward approach seemed to be to drop ruby-concurrent 1.3.5
from -questing-proposed a
PPA:
https://launchpad.net/~ankushpathak/+archive/ubuntu/lp2112014-iputils-
questing-merge
** Merge proposal linked:
https://code.launchpad.net/~ankushpathak/ubuntu/+source/iputils/+git/iputils/+merge/486755
** Changed in: iputils (Ubuntu)
Status: Triaged => In Progress
--
You receiv
** Changed in: shotwell (Ubuntu)
Assignee: (unassigned) => Ankush Pathak (ankushpathak)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2113485
Title:
Shotwell needs new API scopes for Goo
** Description changed:
- libebur128-1 is an optional dependency of pipewire through
libspa-0.2-modules-extra, which has to be manually installed in order to use
EBUR128 plugin.
- It would be good to have libebur128 promoted to main so that the EBUR128
plugin can go back to being pre-installed
Public bug reported:
libebur128-1 is an optional dependency of pipewire through
libspa-0.2-modules-extra, which has to be manually installed in order to use
EBUR128 plugin.
It would be good to have libebur128 promoted to main so that the EBUR128 plugin
can go back to being pre-installed with pi
Public bug reported:
[Availability]
The package libebur128-1 is already in Ubuntu universe. The package libebur128
builds for the architectures it is designed to work on. It currently builds and
works for architectures: any (amd64, arm64, armhf, ppc64el, riscv64, s390x,
i386).
Link to package h
** Merge proposal unlinked:
https://code.launchpad.net/~ankushpathak/ubuntu/+source/pam/+git/pam/+merge/487215
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2087827
Title:
Pam includes does not
47 matches
Mail list logo
