Great work Ben.
It seems like a duplicate.
We would need this to first get fixed in the devel release (24.10) and
then patched into Noble.
Would you be willing to help test out an updated dmraid package in both
Ubuntu releases (24.10 && 24.04)?
I'll look more into the patch to try and find any
This bug seems to be what's causing an issue with [0].
I'm planning to make a PPA with the updated patch to dmraid. If I could
get some help testing the PPA, that would be great and will help with
validating the patch.
[0] - https://bugs.launchpad.net/ubuntu/+source/multipath-
tools/+bug/2075442
Thanks Ben, I appreciate your help :)
I've kicked off a build for oracular, noble, jammy at
https://launchpad.net/~mitchdz/+archive/ubuntu/lp2047303-dmraid-kpartx-
boot
They should be available to retrieve in ~2hours (assuming the riscv64
build is happy).
--
You received this bug notification b
** Also affects: dmraid (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: dmraid (Ubuntu Oracular)
Importance: Undecided
Status: Confirmed
** Also affects: dmraid (Ubuntu Jammy)
Importance: Undecided
Status: New
** Summary changed:
- Partitions on d
I forgot our ARM builders aren't happy right now. If you want to test
immediately you can grab the .deb files from my PPA immediately.
Unfortunately the package won't publish until arm64/armhf are built.
For example, you can find the jammy debs at
https://launchpad.net/~mitchdz/+archive/ubuntu/lp2
Or, you can just wait for arm{64,hf} to finish building :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2075442
Title:
RAID partitions not auto detected at boot
To manage notifications about this
Interesting point. Let me spin up a VM and do a jammy->noble dist-
upgrade with kpartx-boot installed and see what happens. With this
failure, it should show up without any special hardware.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
the dist-upgrade did fine in my VM.
$ lxc launch ubuntu:jammy j-n-upgrade --vm
$ lxc shell j-n-upgrade
$ apt update -y
$ apt install -y kpartx-boot
$ apt install -y ubuntu-release-upgrader-core
# sed -i 's/Prompt=lts/Prompt=normal/' /etc/update-manager/release-upgrades
# do-release-upgrade -f Dist
Carson, thanks for your quick responses. One further question - did this
error message happen only during upgrade and is fixed now, or are you
still seeing this error message somewhere?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
Public bug reported:
During the noble merge and Jammy/Mantic MRE, a functional change was
spotted for the root servers to be updated.
This notice is at - https://b.root-servers.org/news/2023/05/16/new-
addresses.html
From the page:Our new IPv4 address will be 170.247.170.2 and our new
IPv6 addre
** Changed in: grpc (Ubuntu)
Status: Invalid => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1935709
Title:
grpc++-dev doesn't install gRPCConfig.cmake
To manage notifications about
This is probably an issue with building against php8.3. I see the debian
version is building against php8.2 right now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2049901
Title:
php-symfony-polyfi
There was an upstream commit[0] which looked promising. I tried applying
that and the test still fails the same. The results are in my PPA[1].
[0] -
https://github.com/symfony/polyfill/commit/1100c075b44595802401a0c9d6505bc1e8fd299a
[1] -
https://launchpad.net/~mitchdz/+archive/ubuntu/php-symfo
Just tested this again with ami-02cc3ff919a972d83 in us-east-1 and
hibernation is working as intended upon first boot. I am closing this
bug now, but will reopen if this issue comes back.
** Changed in: ec2-hibinit-agent (Ubuntu)
Status: New => Invalid
--
You received this bug notificatio
This package looks like it'll take quite a bit more digging to get to
build properly.
Since this is a leaf package and in universe I'll stop working on this
due to FF looming.
I submitted a bug report to debian to give them a heads up that they may
hit this when updating php to 8.3 as well[0].
[
Hi Egil, thanks for the update. The changes look reasonable enough to
me, but unfortunately I don't think we will get them in immediately due
to feature freeze just happening. It'd also be nice to get these changes
in upstream so it's an official backport. In the meantime I built a
byobu with the c
Hi Marcus,
Thanks for making this bug report!
To answer your question[0] on why we have version 1.24 instead of 1.25,
we stay up to date with debian for this package. Since debian is still
on 1.24 that's what we have.
I'm curious if you were able to test the patch and if it worked for you,
consi
This is easy to reproduce the error message itself, and I think it's
happening just because tmux is nested. I'm not sure why it's getting
nested in your environment though.
Do you have byobu to automatically start up when you login? How do you
have that set up?
$ lxc launch ubuntu-daily:noble n
$
I attempted to reproduce this issue in a VM and wasn't succesful. I
essentially copied the tgtbasedmpaths test but made the backing disk
bcache cache before setting up the targets.
1) create vm
$ lxc launch ubuntu-daily:noble --vm n-vm
$ lxc shell n-vm
# apt install -y lsscsi multipath-tools open-
Fundamentally my setup is different than the scenario set up in the bug.
I was initially confused why multipathing was even happening, so I will
explain the scenario here. In case someone else is also confused.
The hardware is a JBOD enclosure where each disk has redundant I/O,
hence the multipath
I have successfully created a kvm based reproducer.
1) get an image
$ wget
https://cdimage.ubuntu.com/ubuntu-server/daily-live/pending/noble-live-server-amd64.iso
2) Create bcache disk
$ fallocate -l 20G image.img
$ make-bcache -C image.img
3) Boot into iso with multipathed bcache disk
$ kvm -m
Any objection to renaming this bug title to something more accurate such
as "multipathd bcache disks do not get picked up by multipath-tools
during boot"?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
** Also affects: nbd (Ubuntu Noble)
Importance: Undecided
Assignee: Mitchell Dzurick (mitchdz)
Status: Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060745
Title:
nbd-client
** Summary changed:
- Multipath JBOD storage devices are not shown via /dev/mapper but each path as
a single device.
+ multipathd bcache disks do not get picked up by multipath-tools during boot
** Description changed:
- As in the title, if machine has multipath storage device connected e.g.
-
Closing this, decided not do to the merge for an LTS.
** Changed in: ec2-hibinit-agent (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/2043002
Title:
merge from
** Description changed:
[ Impact ]
- NBD users who want to use /etc/nbdtab will face issues when trying to
- start the NBD Client. Trying to use the `systemd` service also doesn't
- work.
+ nbdtab uses a port of 0 by default which is not sensible. This means
+ that if you do not set a default
** 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 ubunt
** Changed in: nbd (Ubuntu Noble)
Status: Triaged => In Progress
** Changed in: nbd (Ubuntu Noble)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060745
Title:
Hello Yosua,
Thank you for making this bug report!
Where did you get the odbcinst 2.3.11-1 package? I do not see that in
our archives for Jammy.
** Changed in: unixodbc (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
*** This bug is a duplicate of bug 2045297 ***
https://bugs.launchpad.net/bugs/2045297
Thanks Sergio, looks like that does cover it :)
** This bug has been marked a duplicate of bug 2045297
file root.hints needs update
--
You received this bug notification because you are a member of Ubu
I haven't updated this for a bit, but I tried the aforementioned change
in comment #7 in this PPA and it did not build -
https://launchpad.net/~mitchdz/+archive/ubuntu/lp1935709-grpc-cmake-dev-
files/+packages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
All architectures except amd64 are not building due to:
debian/rules binary-arch
dh binary-arch --buildsystem=golang --with=golang --builddirectory=_build
dpkg-genbuildinfo --build=any -O../runc_1.1.12+ds1-2ubuntu1_arm64.buildinfo
dpkg-genbuildinfo: error: binary build wit
It may be nice to remove the !amd64 builds since the build failures look
like an issue, but maybe that's just me.
** Changed in: runc (Ubuntu Noble)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
Thanks Lucas, that makes sense. I'll set this to invalid then :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064139
Title:
not building for arm64, armhf, ppc64el, riscv64, s390x
To manage notifi
** Merge proposal linked:
https://code.launchpad.net/~mitchdz/ubuntu/+source/nginx/+git/nginx/+merge/465301
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2024019
Title:
Add GCC atomic support (-
** Description changed:
- Hi,
- we recorded more than 30% performance regression on Ubuntu Focal for AWS
Graviton instances since Nginx package is not compiled with "-moutline-atomics"
cflag for arm64 architecture (337548 rps with default package and 484453 rps
using the proposed flag).
+ [ Im
** Changed in: multipath-tools (Ubuntu)
Assignee: (unassigned) => Mitchell Dzurick (mitchdz)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064380
Title:
Merge multipath-tools from Deb
** Changed in: rsync (Ubuntu)
Assignee: Sergio Durigan Junior (sergiodj) => Mitchell Dzurick (mitchdz)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064457
Title:
Merge rsync from Deb
** Description changed:
This bug tracks an update for the rabbitmq-server package in Ubuntu.
This bug tracks an update to the following versions:
- * Focal (20.04): rabbitmq-server 3.8.12
- * Jammy (22.04): rabbitmq-server 3.9.27
+ * Focal (20.04): rabbitmq-server 3.8.3
+ * Jammy (22
Thanks Utkarsh! I will re-do the merge today if I have time, but most
likely tomorrow.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2040360
Title:
[FFE ] Merge multipath-tools from Debian unstable
I wonder if the latest update to Jammy has fixed the issue? Is this
issue still occurring for you when upgrading to the Jammy package
version 2.90-0ubuntu0.22.04.1 Julia?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
Hi Dominic,
Thanks for taking the time to submit this bug report and make Ubuntu
better!
Where are you setting the variable CHECK_RCPT_SPF = true ?
Doing a quick google search I found[0] which looks like it may be
useful. It says to do the following -
1) Add `CHECK_RCPT_SPF = true` to the top o
Thanks for making this bug report!
This could be related to your other bug[0], but just in-case can you
show how you are configuring exim4, and if you have simple steps to
reproduce this issue, that would be helpful.
[0] - https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/2056372
--
You rece
Officially closing as Won't Fix since i386 is not an officially
supported arch, and it seems there is not any more desire for this.
Please let me know if this should stay open.
** Changed in: samba (Ubuntu)
Status: Incomplete => Won't Fix
** Changed in: python3.10 (Ubuntu)
Status:
** Tags added: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1993837
Title:
apparmor profile libvirt-qemu is too permissive
To manage notifications about this bug go to:
https
This bug seems to have been unfortunately lost to time, or there is
discussion I am not aware of about it.
Gionatan, if there's still desire for this, I suggest making an upstream
bug report[0], as these options are not changed by Ubuntu, but rather
come from upstream.
I'm setting the bug to Opin
@server-triage-discuss - looks like there may have been some discussion
on this when I wasn't around. Did this mean to get dropped? If so, let's
set as Won't Fix.
** Tags added: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
I'm going through old open bugs. I assume this bug is not a problem
anymore, mostly due to the package libpam-smbpass not being available
since Xenial, and the lack of discussion here.
Closing this bug, but please comment if it should be reopened.
** Changed in: samba (Ubuntu)
Status: New
I'm going through some old bugs.
I'm also unable to reproduce this. If we could get some more information
such as what your /etc/nginx/nginx.conf looks like, that may be helpful
in reproduction.
Looking online I see a few different reports which seem similar, where
each have differing solutions.
This failed because of the following line:
/var/lib/dpkg/info/clamav-daemon.postinst: 428: cannot create
/var/lib/clamav/clamav.conf: Directory nonexistent
I guess /var/lib/clamav/ directory did not exist during install. I'm not
sure how this case occurs. Was there anything interesting you did be
The only focal autopkgtest that really has me confused in the python2.7
failure. This is due to a unit test that fails. The strange thing is
that this unit test actually fails in the Jammy autopkgtest, but the
Jammy autopkgtest passes anyways. It has always been like this.
You will see
1643s FAIL
at is blocked in proposed
at/riscv64 has unsatisfiable dependency
at/s390x has unsatisfiable dependency
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2040367
Title:
Merge at from Debian unstable fo
Ran the autopkgtest on a new PPA with my changes enabled by default and
the test still fails[0]. I believe this is fine enough to ignore simply
because this test has always been failing like this.
[0] - https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-mitchdz-
python2.7-opt-test-enabled-
d
I don't have time to look into why it is blocked right now, but will
take a look next week if I can't get to it tomorrow.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2040367
Title:
Merge at from D
Thanks John. I'll leave this bug as is, feel free to add any
tags/subscriptions to help track it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1993837
Title:
apparmor profile libvirt-qemu is too pe
Public bug reported:
I noticed that when creating an m5.large noble instance, hibernation is
not resuming properly after first creation. I haven't had a ton of time
to look into it yet, but I did see 2 observations:
* hibinit-resume is not being ran
* re-running the unit file makes things work as
: Mitchell Dzurick (mitchdz) => (unassigned)
** Changed in: haproxy (Ubuntu Focal)
Assignee: (unassigned) => Mitchell Dzurick (mitchdz)
** Changed in: nginx (Ubuntu Focal)
Assignee: (unassigned) => Mitchell Dzurick (mitchdz)
** Changed in: postgresql-12 (Ubuntu Focal)
Assignee: (u
** Changed in: nginx (Ubuntu)
Status: In Progress => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2024019
Title:
Add GCC atomic support (-moutline-atomics) for arm64 on Focal
To manage
I see gvfs is still failing even with migration-reference/0.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2046994
Title:
Spotlight search function broken with macOS Ventura and later client
To man
Can we still call 9 autopkgtest run failures and 2 migration-refrence/0
failures flaky? I see gvfs failed in the past, but not this much.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2046994
Title:
Thanks Tim! With more people having a seemingly similar issue I re-
opened it as New and subscribed ubuntu-server to take a look at this
again.
** Changed in: dnsmasq (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
This merge may want to be not done for Noble. After doing the merge
again I noticed a seg fault in multipathd when starting the service
during my testing. This is easily repeatable in Ubuntu by uninstalling
multipath-tools and then doing a fresh install. This is not reproducible
in Debian during my
Just want to update this bug - I have not found a fix for this. Instead
I've been relying on the Logitech universal receiver which is working
great in my experience.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
Looking at upstream, there's not a ton that I worry about missing in
noble. The only one is a fix for a memory leak that I think would make
sense to cherrypick[0].
Otherwise, I don't think it is worth the risk to upgrade the package
this late in the cycle, and instead effort would be better utiliz
Plus, there are changes to how the systemd units interact that is a work
in progress, which I think makes more sense for a **.10 release than an
LTS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/20403
So sorry for letting this one linger a bit. Finally looked into it.
https://launchpad.net/ubuntu/noble/riscv64/libpam0t64 has been deleted
which is a dhlibs:Depends for at. This package was actually deleted the
same day of the upload the -proposed so I wonder if there was just weird
linking going
** Changed in: amazon-ec2-net-utils (Ubuntu Jammy)
Status: Fix Committed => Won't Fix
** Changed in: amazon-ec2-net-utils (Ubuntu)
Status: New => Invalid
** Also affects: amazon-ec2-net-utils (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: amazon-ec2-net-u
netvicious or Dan, do you have the AMI that you used to produce that
error with proftpd-core?
I also tried reproduction on ami-0dffe9017aa8424a2 in eu-north-1 and was
not able to reproduce that failure.
I just booted a fresh t3.micro instance with the above AMI, then
proceeded to run `apt update
Also, the various packages here have a similar error message but the
error is probably caused by different things. This is a generic error
message from init-system-helpers.
Now, with that said, I agree init-system-helpers should be more verbose
when this error happens.
--
You received this bug n
Thanks for the additional info!
Is there a reason you need to use ondrej's PHP package? I'd be curious
if this could be reproduced using php 8.1.2-1ubuntu2.14 from the Ubuntu
archives.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
Thanks for the crash report! Looking into the crash report I do think
this is related to https://github.com/net-snmp/net-snmp/issues/107. I
tried applying the patch to our Jammy version and unfortunately it does
not apply completely due to differences in the codebase.
I did apply the lines I could
Thiago,
Apologies if I missed it somewhere, but which Ubuntu release are you
using for your tests?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054616
Title:
The systemd service for NBD Client do
I've been playing around with noble and I've noticed that sometimes if I
try to restart the service right after boot it will fail
root@n-vm:~# systemctl restart nbd@nbd0
Job for nbd@nbd0.service failed because the control process exited with error
code.
See "systemctl status nbd@nbd0.service" and
Wouter, is my assumption correct that ideally we should see the devices
available on boot if we enable nbd@nbd0?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054616
Title:
The systemd service for
Public bug reported:
During the noble merge cycle, 2 deltas were made so the initramfs test
works on both debian/ubuntu:
diff --git a/debian/tests/control b/debian/tests/control
index 42eab9e..81901cb 100644
--- a/debian/tests/control
+++ b/debian/tests/control
@@ -19,6 +19,6 @@ Architecture: amd
This can be reproduced in noble. I don't particularly think this is a
bug either but rather an undocumented design decision.
Imre, I think the best action here is to ask upstream to change the
value higher, or to document the max character length better.
--
You received this bug notification bec
Thanks for making this bug report and making Ubuntu better Bradley!
This is very easy to reproduce. There was some history around renaming
in the debian commit history that I was reading, and I think this was
accidentally changed up in Debian. I submitted a MR to update this in
debian[0] so we wil
I must've opened this bug up in the morning before Marc commented and
just got back around to posting the question. Apologies for asking for
the same information!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
Thanks for taking the time to make this bug report to make Ubuntu
better!
I tried reproducing your failure and unfortunately am not able to in a
VM/container setup. I think this may need some extra configuration to
reproduce the failure.
Starting with something basic, would you mind sharing these
mfo: thanks for catching the ctrlc+ctrlv error! It sounds like we are
just waiting to re-run the autopkgtest then.
Let me know if you would like any additional testing from me!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
revent an upgrade/install failure for users in a certain scenario. The
- removal of the conf file was not included in the merge, but should be
- included in-case users upgrade release and carry-over the conf file.
- (See LP: 2000186 for reference)
-
- -- Mitchell Dzurick Wed, 02
Thanks a ton Mauricio! Would we be good to start phasing the Jammy
package then while I investigate the Focal failures? I'll start taking a
look at Focal today.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
Hi Utkarsh!
902a13b2 Rely on newly un-broken dmsetup
There was a patch in Debian[0] to handle a mismatched variable name, which was
finally updated >= 2:1.02.196-1~, so the patch was removed and now
multipath-tools relies on that version.
Here we unfortunately have a slightly older version[1]
2
Actually some of our changes[0] to try and enable socket based
activation are still present. Let me do a little digging and confirm
these changes are still good to have. I thought I recalled these changes
being dropped.
I think these changes are still fine to bring in, but let me do a little
inves
Yeah I confirmed with Sergio - some of the changes are still present,
but it should not be harmful. Thankfully these changes are easy to test,
and as long as the service is enabled and working at boot, and after a
package installation it will be fine.
I will manually test booting from a multipath
Hi Andreas, the test_customize_compiler flag test has always failed. I'm
curious about why it's failing but the autopkgtest as a whole is
passing.
In fact, the same failures occur for both jammy/focal since forever -
yet they seem to be the reason w hy the Focal autopkgtest fails, whereas
Jammy ha
i took a look at the other focal packages and put my thoughts.
RELEASE=focal
TRIGGER=python2.7/2.7.18-1~20.04.4
release arch packageversion exitcode
triggersrequester
--- --- - ---
Which are done building now!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2075442
Title:
RAID partitions not auto detected at boot
To manage notifications about this bug go to:
https://bugs.launch
my PPA for testing is here[0].
I made a debian bug report at[1].
[0] -
https://launchpad.net/~mitchdz/+archive/ubuntu/lp2047303-dmraid-kpartx-boot
[1] - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078223
** Bug watch added: Debian Bug tracker #1078223
https://bugs.debian.org/cgi-bin/b
Thanks for your help Ben, I really appreciate it.
I will begin the SRU process shortly on the dmraid bug, and continue the
discussion over there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2075442
the dmraid bug ==
https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/2047303
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2075442
Title:
RAID partitions not auto detected at boot
To manage noti
Hi, I've kicked off a build in my PPA here[0].
Mario, feel free to test the package in my PPA once it finishes building
(should hopefully take about 4-5 hours from the time I'm making this
comment.
This is different from the -proposed pocket validation, I'm just making
sure it builds in LP :)
[0
*** This bug is a duplicate of bug 2047303 ***
https://bugs.launchpad.net/bugs/2047303
Ben, apologies. I'll be marking this bug as a duplicate now. If you
would like to copy your #30 comment to the dmraid bug that would be
great, just so the verification is in one bug.
** This bug has been ma
** Merge proposal linked:
https://code.launchpad.net/~mitchdz/ubuntu/+source/dmraid/+git/dmraid/+merge/470911
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2047303
Title:
Partitions on dmraid ma
made an upstream bug report to bcache-tools[0].
[0] - https://www.spinics.net/lists/linux-bcache/msg13179.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887558
Title:
multipathd bcache disks d
I just want to update on my upgrade test.
First and foremost - a direct upgrade from Jammy to Noble is not
possible.
It only is if you have it installed and have not used rabbitmq-server,
thus no metadata is made yet.
If you use the server in Jammy and then attempt to upgrade to Noble
right now
Hadmut, thanks again for bringing this to our attention.
With 24.04.1 coming out soon we may expect more upgrades from Jammy ->
Noble. Therefore I am looking to block the upgrade (22.04 -> 24.04) if
rabbitmq-server is installed.
This is unfortunate, but I think is a fair to not make rabbitmq-serv
Great points Hadmut.
It is unfortunate how far behind we are in versions. We follow debian
which hasn't been updated in a bit. I was thinking about updating the
package there, but I need to fix the fires here first (and if I update
debian to the latest without handling this bug's issue, I will bre
I am helping fix bug
https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/2047303 which made
me think about dropping this too.
My concern is that even if it's dead, people are still very clearly
using dmraid, and need it to boot in certain scenarios. It would suck
uru from Noble->PP and not be ab
Also, this may be a duplicate of [0].
[0] - https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/2048766
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073677
Title:
Remove from oracular?
To mana
201 - 300 of 473 matches
Mail list logo
