A fix has been merged upstream:
https://github.com/systemd/systemd/pull/18811/files
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1913763
Title:
hyperv: unable to distinguish PTP devices
To manage
Indeed, this fixed the issue. I started a new bionic instance and ran
do-release-upgrade -p
The process went as expected.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923111
Title:
Az
Hi there,
Is there any update on this issue? I would like to understand who owns
the investigation/debugging process? Please tell us if you need any help
from the CPC team.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
@rbalint I was able to reproduce the issue with an image that was
running the following:
ii cloud-init20.4.1-79-g71564dce-0ubuntu1 all initialization
and customization tool for cloud instances
ii linux-image-azure 5.8.0.1017.19+21.04.14 amd64Linux kernel
image fo
@rbalint, I just tested Impish and I cannot reproduce the issue. It
doesn't prove it's not there but it's a very good sign!
I can see that our automated testing failed because of this issue on the
2021-05-10 but not after. If I'm not wrong, systemd 248 was pushed on
the 14th, this would make a nic
I built the following images using the version in -proposed and it
worked as expected.
Concerning the autopkgtest regression, I think it is unrelated with this
change. It seems to be related to openstack and nova setup.
Groovy
==
ubuntu@ubuntu:~$ lsb_release -c -r
Release:20.10
Coden
It's been there for almost 3 months, I think it can wait a few more
days. It's affecting Azure's users who use Hirsute instances with
accelerated networking enabled, I don't know how many users that is.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
I seems that we are seeing this issue on Azure with Ubuntu >=20.04. The
CPC team is running a series of tests before publishing images, those
tests spin up ~50 instances in Azure and usually one of them is having
this issue.
You can find the system logs of a failing instance here:
https://pastebin
@laney I built a custom image with system logs level set to debug and I
was able to reproduce the issue. You can find the logs attached.
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1871538/+attachment/5505001/+files/syslog
--
You received this bug notifi
Also, systemd is actually reloaded by cloud-init. In cloud-init logs, I
can read:
2021-06-16 08:54:51,608 - subp.py[DEBUG]: Running command ['systemctl',
'daemon-reload'] with allowed return codes [0] (shell=False, capture=True)
2021-06-16 08:54:51,953 - cc_mounts.py[DEBUG]: Activate mounts: PASS
Ok I will cook an other custom image and try to reproduce.
Concerning this log line:
Jun 16 08:55:45 alan-hirsute-base-aiamcicscciaelhaktpo dbus-daemon[711]:
[system] Connection has not authenticated soon enough, closing it
(auth_timeout=3ms, elapsed: 45129ms)
Please note that during our fir
@rbalint @ddstreed any update on this issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1919177
Title:
Azure: issues with accelerated networking on Hirsute
To manage notifications about this bug
I tried to reproduce the issue with the latest hirsute image pushed to
Azure and it appears that I cannot.
While I can still reproduce the issue with 20210511.1, I can't with
20210622.1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: cloud-images
Status: Confirmed => 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/1923865
Title:
Bootable buildd xenial images go to initramfs on boot
To manage noti
** Also affects: cloud-images/xenial
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/1923865
Title:
Bootable buildd xenial images go to initramfs on boot
T
I was unable to reproduce this, and I think @oddbloke is right. Please
feel free to close this and I will post something new if I see the issue
happening again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
Public bug reported:
On Azure instances running Xenial Pro FIPS images with accelerated
networking enabled, cloud-init fails to setup the user's ssh key and I
can see the following stack trace in the logs:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/cloudinit/cmd/mai
I was actually able to reproduce today and I can confirm that the
instance creation didn't take more than a few seconds. This bug can be
closed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925526
Ti
Hi,
Thanks for looking into that. Indeed, while trying to reproduce the
issue this morning, I found it more challenging than I originally
thought. I want to add a few points here on how I reproduced the issue:
1. Usually, I do not use the Azure CLI directly. I use a custom CLI of my own
that us
Hi Wayne,
Thank you for reporting the issue.
I am able to reproduce it using this URN
'Canonical:UbuntuServer:18.04-LTS:latest'. By checking APT logs, the
issue seems related to python2. Indeed, if I remove python2.7 (apt purge
python2.7) before doing 'do-release-upgrade', the upgrade goes fine.
Hi there,
For whether or not the issue affects Groovy. I've been creating Groovy
VMs on a loop to confirm if I could reproduce it there and (after ~50
tries) I still haven't seen it happen. I think we can safely assume that
this issue does not affect Groovy.
Also I was able to reproduce the issue
I don't have any particular knowledge of how systemd waits for the
network to be ready but reading systemd-networkd-wait-online.service(8)
and networkctl(1) I wonder if cloud-init shouldn't wait for networkd-
wait-online to report that the link is "routable" instead of
"degradated" (default minimum
Hi,
Ok thanks. I am now trying to find at which time the issue was first
introduced. So far I tested an image from 20201222 and confirm that I
cannot reproduce the issue with this image.
Then by modifying the image (always before first boot) I was able to find that:
- upgrading cloud-init from 2
The issue probably* started between these two serials: 20210215 and
20210304.
*I say "probably" because while I'm sure I can reproduce the issue with
20210304, the fact I didn't manage to reproduce it with 20210215 (in ~15
tries) doesn't **absolutely prove** that the issue wasn't there.
--
You r
** Description changed:
[General]
On Azure, when provisioning a Hirsute VM with Accelerated Networking
- enabled, sometimes the SSH key is not setup properly and the user cannot
- log into the VM.
+ enabled, sometimes part of the cloud-init configuration is not applied.
+
+ Especially, in
Hi,
Checking the cmdline, the root filesystem is not set:
/boot/vmlinuz-4.4.0-21-generic root= ro quiet splash $vt_handoff
If I change it to "root=PARTUUID=fb561bdb-b68a-44ae-a884-a5fd70f80cf7"
it's booting.
I see also two other errors during boot:
[0.075065] core perfctr but no constrain
** Also affects: systemd (Ubuntu)
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/1919177
Title:
Azure: issues with accelerated networking on Hirsute
To ma
I isolated the issue between those two serial: 20210219 (doesn't have
the issue) and 20210220 (reproduces the issue).
The main difference I can see between those two serial is systemd
version:
20210219 -> 247.1-4ubuntu1
20210220 -> 247.3-1ubuntu2
Cloud-init version is the same (20.4.1-79-g71564d
I attach here the full diff of packages between the two serials.
** Attachment added: "Package diff between 20210219 and 20210220 20.04 Azure
images"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1919177/+attachment/5491010/+files/package-diff.txt
--
You received this bug notificat
Public bug reported:
Sometimes, cloud-init-local takes a few min to start on Azure instances.
Eg:
$ systemd-analyze blame
3min 33.770s cloud-init-local.service
5.441s snapd.seeded.service
5.146s cloud-init.service
After quickly checking cloud-init logs, I see the following time gap:
Hi,
I am not using Pro offers here.
@oddbloke, that's very interesting, thanks for the explanation. You
might be right here, I'm not sure I actually have to wait 3m30 to create
the instance. I will try to reproduce the issue while carefully
monitoring the delay to be sure.
--
You received this
Hi,
I built livecd-rootfs packages with this change and built cloud images
from them. I focused my testing on cloud supporting UEFI. All VMs are
amd64 except for AWS.
KVM (Groovy):
ubuntu@ubuntu:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.10
R
** Tags removed: verification-needed-focal verification-needed-groovy
verification-needed-xenial
** Tags added: verification-done-focal verification-done-groovy
verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Finally, I forgot bionic:
AWS bionic arm64:
ubuntu@ip-172-31-6-24:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.5 LTS
Release:18.04
Codename: bionic
ubuntu@ip-172-31-6-24:~$ uname -a
Linux ip-172-31-6-24 5.4.0-1045-aws #47~18.04.
Thanks for this.
@rbalint or @ddstreet, do you plan to also backport this to Xenial?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1913763
Title:
hyperv: unable to distinguish PTP devices
To manag
Awesome, thanks
On Wed, Mar 10, 2021 at 4:15 PM Dan Streetman <1913...@bugs.launchpad.net>
wrote:
> > @rbalint or @ddstreet, do you plan to also backport this to Xenial?
>
> sure
>
> ** Tags removed: verification-needed verification-needed-bionic
> verification-needed-focal verification-needed-gr
** Description changed:
+ [Impact]
+
+ * In cloud images, the ESP is currently mounted with default (0755)
+permissions. This means anyone can read the ESP partition. This can
+cause security issues as sensitive data might be put in this
+partition[1]
+
+ * The root filesystem part
** Description changed:
[Impact]
- * In cloud images, the ESP is currently mounted with default (0755)
-permissions. This means anyone can read the ESP partition. This can
-cause security issues as sensitive data might be put in this
-partition[1]
+ * In cloud images, the ESP is
@rcj thanks for your reply. Since we only want to SRU the umask change,
I propose move the discussion under this bug[0] as it is only related to
this particular change.
[0] https://bugs.launchpad.net/cloud-images/+bug/1881006
--
You received this bug notification because you are a member of Ubun
I will revert to the original description and move the SRU template to
LP1881006.
** Description changed:
- [Impact]
-
- * In cloud images, the ESP is currently mounted with default (0755)
- permissions. This means anyone can read the ESP partition. This can
- cause security issues as sen
** Description changed:
+ [Impact]
+
+ * For the affected images`, the ESP is currently mounted with default
+ (0755) permissions. This means anyone can read the ESP partition. This
+ can cause security issues as sensitive data might be put in this
+ partition[0]
+
+ [Test Plan]
+
+ * Build a
Public bug reported:
Hyperv provides a PTP device. On system with multiple PTP devices,
services like Chrony don't have a way to know which one is which.
We would like to have a udev rule to create a symlink to the hyperv
clock. This way, services could be configured to always use this clock
no m
A similar rule has already been added upstream for KVM PTP device, see:
https://github.com/systemd/systemd/pull/5495
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1913763
Title:
hyperv: unable to di
I was also able to reproduce on Azure. After upgrading from jammy to
noble using do-release-upgrade and rebooting:
$ 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.
We reverted nullboot to 0.5.0-0ubuntu3 with shim 15.7 prior to the
release of Noble. We have identified and fixed the issue in encrypt-
cloud-image but we are still waiting on Microsoft to deploy the new
version of tool in their provisioning backend. Once this will be done we
will be able to releas
** Summary changed:
- 24.04 TPM backed FDE regression following snapd 2.62 update
+ 24.04 TPM backed FDE regression following shim 15.8 update
** Description changed:
Azure testing has reported an issue following update of the nullboot
package from 0.5.0-0ubuntu3 to 0.5.1-0ubuntu1 which I am
Azure CVM images are impacted by the same issue. I see on #2064088 that
this is an tpm-backed FDE system. So I think it's the same problem here
if those desktop images use an systemd-based initramfs.
For now I suspect that the issue is due to systemd starting services and
setting up UNIX sockets (
Can it be related to this reddit post:
https://www.reddit.com/r/Ubuntu/comments/tkvjwu/this_is_why_i_love_linux_how_a_kernel_upgrade/
?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966066
Title:
a
** Tags added: rls-ii-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871538
Title:
dbus timeout-ed during an upgrade, taking services down including gdm
To manage notifications about this
This is now part of Azure's cloud images (focal to devel) and I can
confirm that it fixes the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871538
Title:
dbus timeout-ed during an upgrade, t
Public bug reported:
To reproduce:
* start a bionic VM in azure:
az vm create --name bionic --resource-group test-bionic --image
"Canonical:UbuntuServer:18_04-lts-gen2:latest" --size Standard_M416s_v2
--admin-username ubuntu --ssh-key-value SSH_KEY_PATH
* "downgrade" the kernel to 4.15 and d
** Changed in: linux-azure (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951924
Title:
linux-azure 4.15 fails to boot on Standard_M416s_v2 in Azure
To mana
Public bug reported:
[Impact]
* The detection of Microsoft Hyper-V VMs is done by cpuid currently,
however there is no cpuid on ARM64. And since ARM64 is now a supported
architecture for Microsoft Hyper-V guests[0], then introduce a more
generic way to detect whether a guest is running as a Hype
Public bug reported:
[Impact]
* We previously restricted the build to amd64[0] because walinuxagent
had a dependency that was only available on amd64. This is not the case
any more, we should at least build walinuxagent for arm64.
[Test Plan]
* Make sure the package builds correctly and can b
Only arm64 is needed for now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1954678
Title:
Build for more platforms
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+
Hi there,
I used this[0] script to test the different series. The most relevant
parts of it are those parameters for qemu:
-smbios type=0,vendor='Hyper-V test',version=1.2.3 \
-smbios
type=1,manufacturer=t1manufacturer,product=t1product,version=t1version,serial=t1serial,uuid=---1
Tested on Azure with an Arm64 instance:
ubuntu@bionic-arm:~$ sudo apt-get install walinuxagent
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be upgraded:
walinuxagent
1 upgraded, 0 newly installed, 0 to remove and 17 not upgr
Probably more readable on pastebin:
https://pastebin.ubuntu.com/p/sv5W99tWKP/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1954678
Title:
Build for more platforms
To manage notifications about thi
I started 156 instances for both:
* an impish image with systemd 248.3-1ubuntu8.5
* a focal image with systemd 245.4-4ubuntu3.16
In both images, I also removed the workaround in
/etc/systemd/system/dbus.service.d
(Environment=SYSTEMD_NSS_DYNAMIC_BYPASS=1) to make sure I was really
testing the f
Public bug reported:
2.11.1.4-0ubuntu1 introduces a bug which prevents the agent from
starting. The issue is due to a missing python package:
azurelinuxagent/distutils that should be installed with the package.
$ systemctl status walinuxagent
× walinuxagent.service - Azure Linux Agent
Loade
The issue is with the patch embed-distutils-to-azurelinuxagent.patch
which creates the __init__.py file in distutils but this file is ignored
by dpkg-source as it is empty. Because this file is not present,
setuptools doesn't see this directory as a python package and doesn't
include it in the debi
Adding a comment in this file as a placeholder fixes the issue.
** Patch added: "walinuxagent.debdiff"
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/2077975/+attachment/5809789/+files/walinuxagent.debdiff
--
You received this bug notification because you are a member of Ubuntu
** Summary changed:
- agent fails to start on devel
+ walinuxagent.service fails to start on oracular
** Changed in: walinuxagent (Ubuntu)
Status: Confirmed => In Progress
** Changed in: walinuxagent (Ubuntu)
Assignee: (unassigned) => Gauthier Jolly (gjolly)
** Also affects:
** Description changed:
2.11.1.4-0ubuntu1 introduces a bug which prevents the agent from
starting. The issue is due to a missing python package:
azurelinuxagent/distutils that should be installed with the package.
-
$ systemctl status walinuxagent
× walinuxagent.service - Azure Linux
** Merge proposal linked:
https://code.launchpad.net/~gjolly/ubuntu/+source/walinuxagent/+git/walinuxagent/+merge/472120
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077975
Title:
walinuxagent
** Changed in: walinuxagent (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: cloud-images
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/2
To help with the investigations: I was able to reproduce the issue by
simply installing dracut on a normal (non tpm-backed FDE) VM. Dracut
replaces initramfs-tools and build a systemd-base initramfs.
# start the lxd VM
$ lxc launch --vm ubuntu:24.04 noble-vm
# in the VM install dracut and reboot
If you've upgraded to the broken package already, the workaround is:
sudo apt update && sudo apt install bpftrace=0.20.2-1ubuntu4
This will downgrade the package to the latest working version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
URL: https://github.com/Azure/GuestProxyAgent/
License: MIT
Notes:
The GuestProxyAgent (GPA) enhances the security of Azure Instance Metadata
Service (IMDS) and Azure Wireserver endpoints (e.g., 169.254.169.254 and
168.63.129.16) on Azure IaaS virtual machines. It introduces
** Summary changed:
- [needs-packaging] [needs-package] azure-proxy-agent
+ [needs-packaging] azure-proxy-agent
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098393
Title:
[needs-packaging] azure-
The fix is in the PPA:
https://launchpad.net/~gjolly/+archive/ubuntu/azure-proxy-agent2/+packages
Debdiff:
https://launchpadlibrarian.net/777806592/azure-proxy-agent_1.0.25-0ubuntu2~ppa2_1.0.25-0ubuntu2~ppa3.diff.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Debdiff attached
** Patch added: "azure-proxy-agent.debdiff"
https://bugs.launchpad.net/ubuntu/+source/azure-proxy-agent/+bug/2098947/+attachment/5859170/+files/azure-proxy-agent.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Public bug reported:
Autpkgtests are failing because the requests to the IMDS service are not
logged if the connection is closed following a timeout.
** Affects: azure-proxy-agent (Ubuntu)
Importance: Undecided
Assignee: Gauthier Jolly (gjolly)
Status: New
** Changed in
I missed that as I was running the autopkgtests on Azure where is IMDS
is available.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2099698
Title:
Fix autopkgtests
To manage notifications about this
Public bug reported:
The package fails to build on architectures other than arm64 and amd64.
This is because the Architecture tag is incorrectly set to any in
d/control.
** Affects: azure-proxy-agent (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification
Public bug reported:
The package installs a directory at /etc/azure/proxy-agent.json. This is
due to an error in d/azure-proxy-agent.install.
** Affects: azure-proxy-agent (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
Public bug reported:
1. the unit tests should be run as part of the build
2. a smoke test should be created to verify that the service is running when
the package is installed
** Affects: azure-proxy-agent (Ubuntu)
Importance: Undecided
Assignee: Gauthier Jolly (gjolly
Since the source package has been accepted into -proposed already, I created
the following bugs to track the issues:
* https://bugs.launchpad.net/ubuntu/+source/azure-proxy-agent/+bug/2098947
* https://bugs.launchpad.net/ubuntu/+source/azure-proxy-agent/+bug/2098948
* https://bugs.launchpad.net
** Changed in: azure-proxy-agent (Ubuntu)
Assignee: (unassigned) => Gauthier Jolly (gjolly)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098947
Title:
Fix FTBFS
To manage notificati
** Changed in: azure-proxy-agent (Ubuntu)
Assignee: (unassigned) => Gauthier Jolly (gjolly)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098949
Title:
Add more package testing
To man
** Changed in: azure-proxy-agent (Ubuntu)
Assignee: (unassigned) => Gauthier Jolly (gjolly)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098948
Title:
Fix incorrect config installation
Tests seems to be passing with this fix:
https://autopkgtest.ubuntu.com/results/autopkgtest-plucky-gjolly-azure-proxy-agent2/plucky/arm64/a/azure-proxy-agent/20250224_172105_7ab10@/log.gz
https://autopkgtest.ubuntu.com/results/autopkgtest-plucky-gjolly-azure-proxy-agent2/plucky/amd64/a/azure-proxy-
** Changed in: azure-proxy-agent (Ubuntu)
Status: New => Confirmed
** Changed in: azure-proxy-agent (Ubuntu)
Assignee: Gauthier Jolly (gjolly) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "azure-proxy-agent.debdiff"
https://bugs.launchpad.net/ubuntu/+source/azure-proxy-agent/+bug/2099698/+attachment/5860190/+files/azure-proxy-agent.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
Thank you very much for your help and your answers!
> Ideally they're ran in both spots.
I guess I can run the test script from the `dh_auto_test` target. Is
that what you are suggesting?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
Simon,
I realized that there is an issue with my last upload:
* the d/.install file is not good
* I forgot to include a fix for the tests in d/tests
To catch these issues in the future:
1. I made dh_auto_test run the unit tests as you suggested
2. I created a new "smoke" test to make sure the
** Description changed:
URL: https://github.com/Azure/GuestProxyAgent/
License: MIT
Notes:
The GuestProxyAgent (GPA) enhances the security of Azure Instance Metadata
Service (IMDS) and Azure Wireserver endpoints (e.g., 169.254.169.254 and
168.63.129.16) on Azure IaaS virtual machines. It
mail
ends in canonical.com, you can probably just set yourself as the
maintainer): `XSBC-Original-Maintainer: Gauthier Jolly
`
Fixed
> `debian/my-rules-que-me-gusta` seems like an accident, what does it
do?
Indeed, removed.
## rules file and building
> Some of the lines in your rules file
Oh yes, you are right, so I spent time fixing the build with libgcrypt
for no reason since they moved to libssl now... Fair enough.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100594
Title:
libgc
Public bug reported:
The libgcrypt-config binary should be installed by libgcrypt-bin but is
missing.
** Affects: libgcrypt20 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
Thanks Adrian. Indeed. I'm trying to fix a package (aircrack-ng) that
uses libgcrypt-config but as you mention, I should rather patch it to
make it use pkg-config.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
The test is now passing on the latest arm64 build:
https://launchpadlibrarian.net/780463283/buildlog_ubuntu-plucky-
arm64.aircrack-ng_1%3A1.7+git20230807.4bf83f1a-2ubuntu1_BUILDING.txt.gz
** Changed in: aircrack-ng (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notifi
This bug is 12 years old and cannot be reproduced, marking as Invalid.
** Changed in: aircrack-ng (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1253149
Title:
This seems to be fixed at least from Noble:
https://packages.ubuntu.com/noble/onionshare. I don't know if fixing
this in Jammy would be allowed by the SRU policy.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
Since we are passed the Debian Import Freeze for Plucky, this will
probably have to wait for 25.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2102155
Title:
Sync onionshare from debian
To manag
Public bug reported:
Ubuntu is currently carrying patch python3.12.diff
--- a/cli/onionshare_cli/onion.py
+++ b/cli/onionshare_cli/onion.py
@@ -33,7 +33,7 @@ import tempfile
import time
import traceback
-from distutils.version import LooseVersion as Version
+from packaging.version import Versi
I had another look at the d/copyright[0] file (GPLv2 + CC0-1.0), the LICENSE[1]
file (GPLv3) and the extra license directory[3] that are present in the source
package in Jammy. I agree that this package should be moved from multiverse to
universe in Jammy.
The same reasoning applies to Focal[4][
I don't know why this wasn't included back then but it's present in the
latest version of the package which is currently in devel:
# dpkg -c aircrack-ng_1%3a1.7+git20230807.4bf83f1a-2ubuntu1_amd64.deb | grep
airodump-ng-oui-update
-rwxr-xr-x root/root 226 2025-03-06 18:06
./usr/sbin/airodu
I think I have a fix and I'm testing it in my PPA:
https://launchpad.net/~gjolly/+archive/ubuntu/test-builds/+packages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2102275
Title:
Autopkgtest failin
Public bug reported:
setup-onion-service is failing on all architectures:
https://autopkgtest.ubuntu.com/packages/tor/plucky/ due to onionshare
crashing.
** Affects: tor (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ub
100 matches
Mail list logo
