[Bug 2022390] Re: Keep the -dev binary package in sync with Debian
Now, there is no regressions against runc/1.1.7-0ubuntu2.4 in Mantic and runc/1.1.7-0ubuntu1~20.04.4 in Focal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2022390 Title: Keep the -dev binary package in sync with Debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/2022390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065546] Re: postfix configuration must be set on 24.04 before apt package manager can be used
Hi William, Thanks for taking the time to report this bug and trying to make Ubuntu better. As software evolves it may require new dependencies and that is the case here, one of the packages you are installing now has postfix in its dependencies tree. This is not a bug, this may happen in a new release. What you can do to avoid the prompt is setting the DEBIAN_FRONTEND environment variable to 'noninteractive' when calling apt and the default values will be used. Marking this bug as Invalid as this is not a bug, but a change behavior that is expected between releases. ** Changed in: postfix (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065546 Title: postfix configuration must be set on 24.04 before apt package manager can be used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/2065546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060666] Re: [SRU] Memory leak in krb5 version 1.17
Hi Ponnuvel, I see you prepared a debdiff to fix this issue, if you are seeking for a sponsor for you package you could use the Patch Pilot program [1]. Long story short, you could subscribe ~ubuntu-sponsors to this bug and it would go to the Patch Pilot queue. This is in the Server team queue, and once we have time we will take a look if no one else had already done that. It may take some time. [1] https://ubuntu.com/community/contribute/ubuntu-development/ubuntu- patch-pilots -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060666 Title: [SRU] Memory leak in krb5 version 1.17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/2060666/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061017] Re: lxd-installer: permission error not handled and lxd snap not installed
** Also affects: lxd-installer (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: lxd-installer (Ubuntu Noble) Status: New => In Progress ** Changed in: lxd-installer (Ubuntu Noble) Assignee: (unassigned) => Simon Déziel (sdeziel) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061017 Title: lxd-installer: permission error not handled and lxd snap not installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd-installer/+bug/2061017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064458] Re: Merge ruby-defaults from Debian unstable for oracular
** Changed in: ruby-defaults (Ubuntu) Milestone: ubuntu-24.05 => ubuntu-24.07 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064458 Title: Merge ruby-defaults from Debian unstable for oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby-defaults/+bug/2064458/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064459] Re: Merge ruby-ethon from Debian unstable for oracular
** Changed in: ruby-ethon (Ubuntu) Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064459 Title: Merge ruby-ethon from Debian unstable for oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby-ethon/+bug/2064459/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064461] Re: Merge runc from Debian unstable for oracular
** Changed in: runc (Ubuntu) Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064461 Title: Merge runc from Debian unstable for oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/runc/+bug/2064461/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064930] Re: dnsmasq cannot execute at systemctl
Thanks for taking the time to report this bug and trying to make Ubuntu better. I tried to install dnsmasq in a brand new LXD container running Noble (24.04) and I was not able to reproduce the failure you mentioned: root@dnsmasq-install:~# apt install dnsmasq Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: dns-root-data dnsmasq-base The following NEW packages will be installed: dns-root-data dnsmasq dnsmasq-base 0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded. Need to get 397 kB of archives. After this operation, 953 kB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu noble/main amd64 dnsmasq-base amd64 2.90-2build2 [375 kB] Get:2 http://archive.ubuntu.com/ubuntu noble/universe amd64 dnsmasq all 2.90-2build2 [17.9 kB] Get:3 http://archive.ubuntu.com/ubuntu noble/main amd64 dns-root-data all 2023112702~willsync1 [4450 B] Fetched 397 kB in 3s (157 kB/s) Selecting previously unselected package dnsmasq-base. (Reading database ... 34374 files and directories currently installed.) Preparing to unpack .../dnsmasq-base_2.90-2build2_amd64.deb ... Unpacking dnsmasq-base (2.90-2build2) ... Selecting previously unselected package dnsmasq. Preparing to unpack .../dnsmasq_2.90-2build2_all.deb ... Unpacking dnsmasq (2.90-2build2) ... Selecting previously unselected package dns-root-data. Preparing to unpack .../dns-root-data_2023112702~willsync1_all.deb ... Unpacking dns-root-data (2023112702~willsync1) ... Setting up dnsmasq-base (2.90-2build2) ... Setting up dns-root-data (2023112702~willsync1) ... Setting up dnsmasq (2.90-2build2) ... Created symlink /etc/systemd/system/multi-user.target.wants/dnsmasq.service → /u sr/lib/systemd/system/dnsmasq.service. Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 148. Processing triggers for man-db (2.12.0-4build2) ... Processing triggers for dbus (1.14.10-4ubuntu4) ... Scanning processes... No services need to be restarted. No containers need to be restarted. No user sessions are running outdated binaries. No VM guests are running outdated hypervisor (qemu) binaries on this host. root@dnsmasq-install:~# Not sure how to trigger the problem you described, and without that we cannot do anything. I am marking this bug as Incomplete as I cannot verify whether it is a real bug. ** Changed in: dnsmasq (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064930 Title: dnsmasq cannot execute at systemctl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2064930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064914] Re: Windows guest hangs after reboot from the guest OS
** Also affects: qemu (Ubuntu Jammy) 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/2064914 Title: Windows guest hangs after reboot from the guest OS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2064914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040483] Re: AppArmor denies crun sending signals to containers (stop, kill)
I also see that you are patching golang-github-containers-common. Does that mean that no patch in libpod is needed? If the answer is yes, we need to mark the libpod tasks as Invalid. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040483 Title: AppArmor denies crun sending signals to containers (stop, kill) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-github-containers-common/+bug/2040483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040483] Re: AppArmor denies crun sending signals to containers (stop, kill)
Hi Tomáš, Thanks for investigating this issue and providing the patch (MP) to fix it in Noble. However, before fixing it in Noble, we need to fix it in Oracular (development release). Would you like to provide a patch or MP targeting Oracular? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040483 Title: AppArmor denies crun sending signals to containers (stop, kill) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-github-containers-common/+bug/2040483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2022390] Re: Keep the -dev binary package in sync with Debian
The src:runc regressions above helped me to identify an error in the package. I forgot to remove the basic-smoke test which tries to make use of the runc binary (now provided by src:runc-app). In order to fix this, I uploaded src:runc again to Focal (1.1.7-0ubuntu1~20.04.4), Jammy (1.1.7-0ubuntu1~22.04.4), and Mantic (1.1.7-0ubuntu2.4). Please, accept them from -unapproved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2022390 Title: Keep the -dev binary package in sync with Debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/2022390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040460] Re: MRE updates of container-stack for noble
Now that src:runc-app was accepted from NEW in all supported releases, we are ready to land the other updates in -proposed to verify everything together. Please, SRU vanguard, could you check and move the uploads from -unapproved to -proposed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040460 Title: MRE updates of container-stack for noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd-app/+bug/2040460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064139] Re: not building for arm64, armhf, ppc64el, riscv64, s390x
It indeed looks like an issue (but it is not :p). After discussion with the Server team, we will leave it like this in Noble (there is no regression), and in OO series we will revisit the usage of a build profile to not build the runc binary package. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/runc/+bug/2064139/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064122] Re: package mysql-server-8.0 8.0.36-0ubuntu0.22.04.1 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1
Thanks for your time reporting this bug and trying to make Ubuntu better. I see the mysql-server is installed alongside mysql-workbench-community (which is not in the Ubuntu archive and is not supported), this interaction is untested and might pose you some unexpected behavior. The mysql error log is not helpful because the important lines were removed by apport: --- Line containing protected term grant stripped from log by apport hook. Ref. Launchpad bug #1574458 2024-04-29T13:46:53.607516Z 0 [ERROR] [MY-010119] [Server] Aborting Could you please manually check what that line is telling you and share with us? Of course, without any confidential data. Unfortunately, I cannot reproduce this bug locally, more info is needed. ** Changed in: mysql-8.0 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064122 Title: package mysql-server-8.0 8.0.36-0ubuntu0.22.04.1 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/2064122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064139] Re: not building for arm64, armhf, ppc64el, riscv64, s390x
This is expected since the library package is arch:all and is not built in non-amd64 arches. The runc binary package was moved to src:runc-app. Therefore, no binary package is built in non-amd64 architectures by src:runc. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/runc/+bug/2064139/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058622] Re: [needs-packaging] lenovo-wwan-unlock
Hi Dirk Su, I cloned the git repo and for instance the debian/changelog is confusing, there are many entries which makes me think that this package is already maintained somewhere else, is this maintained in a PPA and now you are trying to put it in the Ubuntu archive? When the package is landing for the first time in the Ubuntu archive we usually have just a single changelog entry. The version string you are using does not seem correct. Right now, I see version 1.2ubuntu3. This version string could be used for a native package (something Ubuntu specific), but I see this a project from Lenovo and it is maintained here: https://github.com/lenovo/lenovo-wwan-unlock I'd expect a version similar to 2.0.0-0ubuntu1 (version 2.0.0 was releases 2 weeks ago in the repo above). So before the '-' we have the upstream version. And after that, we have the Debian revision, since this package is not in Debian, just in Ubuntu, we use '0ubuntu1'. I did not read the proprietary license of this software, but in debian/copyright you are using the GPL-3 license for the debian directory. Could you make sure this is OK? I am also unsure how to generate the tarball for this version, due to that I was not able to build the package and run lintian for instance. However, I think you already have something to work on. I am unsubscribing ~ubuntu-sponsors for now. Once you address the issues presented above subscribe ~ubuntu-sponsors again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058622 Title: [needs-packaging] lenovo-wwan-unlock To manage notifications about this bug go to: https://bugs.launchpad.net/lenovo-wwan-unlock/+bug/2058622/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2036761] Re: [mantic] ppa-purge no longer purges what add-apt-repository adds
Apparently, there is nothing to be sponsored here, I am unsubscribing ~ubuntu-sponsors. If I misunderstood the status of this bug and there is something ready to be sponsored, please subscribe ~ubuntu-sponsors again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2036761 Title: [mantic] ppa-purge no longer purges what add-apt-repository adds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ppa-purge/+bug/2036761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054395] Re: [sru] sos upstream 4.7.0
@Arif are the attached debdiffs ready to be uploaded? I do not know if I get it right, but the bug you mentioned is not yet fixed: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2038648 If this is ready for ~ubuntu-sponsors, please state so. If not, please unsubscribe ~ubuntu-sponsors and subscribe again once it is ready. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054395 Title: [sru] sos upstream 4.7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2054395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054391] Re: Fix CPU thermal sensors enumeration
Thanks for the patch @Kai-Heng! I took a look and in general it looks
good, but I'd like to ask you to add some DEP-3 headers [1] to your
patch, that will give us (packagers) more context when revisiting this
package for whatever reason.
Now a personal opinion, I like when the patch file name is listed in the
changelog entry ("* d/p/0016-Fixed-enumeration-of-cpu-thermal-
sensors.patch: "). It makes a direct link between
the change listed there and the file actually fixing it.
Once you address my first comment at least (the second one is not
mandatory), please subscribe ~ubuntu-sponsors again (I am unsubscribing
it now).
[1] https://dep-team.pages.debian.net/deps/dep3/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054391
Title:
Fix CPU thermal sensors enumeration
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2054391/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2036467] Re: Resizing cloud-images occasionally fails due to superblock checksum mismatch in resize2fs
@Matthew I took a look at your debdiffs (I hope they are updated) and they look good in general, I checked the debdiffs for Focal, Jammy, Mantic and Noble. The Noble debdiff requires a rebase, now in Noble we have version 1.47.0-2.4~exp1ubuntu4, so we want version 1.47.0-2.4~exp1ubuntu4.1 with your changes (it will be a SRU for Noble as well at this point). This will need to be fixed in the next development release (OO series) to avoid any future regression. But at the moment the archive is not yet open for that. Please, fix that and someone can sponsor the uploads targeting all supported releases at once. I am unsubscribing ~ubuntu-sponsors, once you address the comment above please subscribe it again and someone will take a look. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2036467 Title: Resizing cloud-images occasionally fails due to superblock checksum mismatch in resize2fs To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2036467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063099] Re: Stopping container signal blocked by AppArmor on Ubuntu
Thanks for providing the workaround Tomáš! I can confirm that it works in Noble, but for me, even using the profile you provided in comment #4, the command below takes more or less 10 seconds (against 12 seconds when the containers are killed with SIGKILL): root@docker-apparmor:~# time docker stop $(docker run --rm -d nginx) 81948b000a5510fe4d59c476d783c7f4d8946f86ffa916d4b317678c74b54ffb real0m12.538s user0m0.015s sys 0m0.027s [ ... download profile from comment #4 ... ] root@docker-apparmor:~# apparmor_parser -Kr /etc/apparmor.d/docker-default root@docker-apparmor:~# time docker stop $(docker run --rm -d nginx) ef2b4c117fa48954288c418d80088ce88fc5233fc13a7084003cb5c980e42369 real0m10.563s user0m0.016s sys 0m0.027s root@docker-apparmor:~# time docker stop $(docker run --rm -d nginx) a8ab8186872d856368ad4b627fa36fa5b0fff78ac5f6ddc9db3e0545f744b741 real0m10.514s user0m0.011s sys 0m0.031s root@docker-apparmor:~# time docker stop $(docker run --rm -d nginx) 42d8afedec05f31ba1999ffbad2e7696eaf295f150e3b5f26a8e5e3cd27a2406 real0m10.503s user0m0.019s sys 0m0.024s -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063099 Title: Stopping container signal blocked by AppArmor on Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/2063099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051380] Re: Expired certificate used for tests causes failures
FWIW there is no autopkgtest regression now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051380 Title: Expired certificate used for tests causes failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby3.0/+bug/2051380/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2049197] Re: ruby_xfree segmentation fault
FWIW there is no autopkgtest regression now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2049197 Title: ruby_xfree segmentation fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby3.0/+bug/2049197/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051380] Re: Expired certificate used for tests causes failures
The packages built fine in all supported architectures, satisfying the Test Plan section. ** Tags removed: verification-needed verification-needed-jammy verification-needed-mantic ** Tags added: verification-done verification-done-jammy verification-done-mantic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051380 Title: Expired certificate used for tests causes failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby3.0/+bug/2051380/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2049197] Re: ruby_xfree segmentation fault
# Verification Mantic root@ruby31-segfault-fix:~# dpkg -l ruby3.1 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---== ii ruby3.13.1.2-7ubuntu3.1 amd64Interpreter of object-oriented scripting language Ruby root@ruby31-segfault-fix:~# cat reproducer.rb require 'nokogiri' # must have an error in it to cause pthread_setspecific to be called html = "' real8m5.499s user0m10.297s sys 0m4.874s More than 8 minutes running the script without any segfault. # Verification Jammy root@ruby30-segfault-fix:~# dpkg -l ruby3.0 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---== ii ruby3.03.0.2-7ubuntu2.5 amd64Interpreter of object-oriented scripting language Ruby root@ruby30-segfault-fix:~# cat reproducer.rb require 'nokogiri' # must have an error in it to cause pthread_setspecific to be called html = "' real8m4.811s user0m10.094s sys 0m4.370s More than 8 minutes running the script without any segfault. ** Tags removed: verification-needed verification-needed-jammy verification-needed-mantic ** Tags added: verification-done verification-done-jammy verification-done-mantic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2049197 Title: ruby_xfree segmentation fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby3.0/+bug/2049197/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061745] Re: Please demote golang-1.21 to universe
I uploaded the container stack packages to Noble to make them build with Go 1.22, those are the versions that require approval: - runc-app/1.1.12-0ubuntu3 - container-app/1.7.12-0ubuntu4 - docker.io-app/24.0.7-0ubuntu4 - docker-buildx/0.12.1-0ubuntu2 - docker-compose-v2/2.24.6+ds1-0ubuntu2 I know the docker* packages are in universe, but we want to update them all atomically every time, so applying the same changes to them. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061745 Title: Please demote golang-1.21 to universe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-1.21/+bug/2061745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061745] Re: Please demote golang-1.21 to universe
All the container stack packages are using golang-1.21 because it is available in all supported releases (we want to keep the same behavior everywhere). Unfortunately, golang-1.22 is only in Noble. We could move to golang-1.22 in Noble if Foundations backport golang-1.22 to the other releases (still supported) as a follow-up work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061745 Title: Please demote golang-1.21 to universe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-1.21/+bug/2061745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061667] Re: Noble 'autofs' 5.1.9-1ubuntu3 buffer overflow
Thanks for taking the time to report this bug and trying to make Ubuntu better. Could you please share your config files so we can try to reproduce the bug locally? ** Changed in: autofs (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061667 Title: Noble 'autofs' 5.1.9-1ubuntu3 buffer overflow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/2061667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059883] Re: package unixodbc-common 2.3.9-5 failed to install/upgrade: trying to overwrite '/etc/odbc.ini', which is also in package odbcinst 2.3.11-1
Thanks for taking the time to report this bug and trying to make Ubuntu better. As Hugh already mentioned, it seems that you are installing packages not from the Ubuntu archive and that is not supported. This part of the log makes me believe on that: modified.conffile..etc.odbc.ini: [ODBC Driver 17 for SQL Server] Description=Microsoft ODBC Driver 17 for SQL Server Driver=/opt/microsoft/msodbcsql17/lib64/libmsodbcsql-17.10.so.5.1 UsageCount=1 There is nothing installed in /opt by debian package from the Ubuntu archive. Since this is an unsupported case, I am marking this bug as Invalid. ** Changed in: unixodbc (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/2059883 Title: package unixodbc-common 2.3.9-5 failed to install/upgrade: trying to overwrite '/etc/odbc.ini', which is also in package odbcinst 2.3.11-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unixodbc/+bug/2059883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1052030] Re: Please transition libgnomeprint to multi-arch
I am not sure why ~ubuntu-sponsors is subscribed to this bug. Is someone actively working on this? Is this still an issue nowadays? For now, I am unsubscribing ~ubuntu-sponsors. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1052030 Title: Please transition libgnomeprint to multi-arch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgnomeprint/+bug/1052030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059182] Re: autopkgtests fail for dune-grid/2.9.0-2build1
As you can see here: https://launchpad.net/ubuntu/+source/dune-uggrid The version 2.9.0-2build2 was already uploaded with a no changes rebuild: dune-uggrid (2.9.0-2build2) noble; urgency=medium * No-change rebuild for CVE-2024-3094 -- Steve Langasek Sun, 31 Mar 2024 18:05:33 + This version is already in the release pocket. Marking this bug as Fix Released. ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-3094 ** Changed in: dune-uggrid (Ubuntu) Status: New => 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/2059182 Title: autopkgtests fail for dune-grid/2.9.0-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dune-uggrid/+bug/2059182/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058692] Re: black autopkgtest fails because python3-typed-ast no longer in archive
Unsubscribing ~ubuntu-sponsors. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058692 Title: black autopkgtest fails because python3-typed-ast no longer in archive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/black/+bug/2058692/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059291] Re: autopkgtest failure against libphonenumber/8.12.57+ds-4.2build1
Thanks Chris! I added just a reference to this bug in the changelog, with that this bug will be closed once the package migrates. Keep an eye on that next time. Package uploaded: Uploading to ubuntu (via ftp to upload.ubuntu.com): Uploading pnc_0.9.4-3build3.dsc: done. Uploading pnc_0.9.4-3build3.debian.tar.xz: done. Uploading pnc_0.9.4-3build3_source.changes: done. Successfully uploaded packages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059291 Title: autopkgtest failure against libphonenumber/8.12.57+ds-4.2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pnc/+bug/2059291/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058606] Re: Sync rocm-hipamd 5.7.1-3 (universe) from Debian unstable (main)
Right now, version 5.7.1-3 fails to build in Noble because of some uninstallability issues: The following packages have unmet dependencies: libobjc-13-dev : Depends: gcc-13-base (= 13.2.0-13ubuntu1) but 13.2.0-17ubuntu2 is to be installed Depends: libgcc-13-dev (= 13.2.0-13ubuntu1) but 13.2.0-17ubuntu2 is to be installed This is happening because of the ongoing transitions. Since the package build would fail in the Ubuntu archive, I'm holding this sync until those things get sorted out. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058606 Title: Sync rocm-hipamd 5.7.1-3 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rocm-hipamd/+bug/2058606/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058958] Re: armhf autopkgtest failure (due to time_t format args)
I was able to build it now. Package uploaded: Uploading to ubuntu (via ftp to upload.ubuntu.com): Uploading gvmd_23.1.0-1ubuntu3.dsc: done. Uploading gvmd_23.1.0-1ubuntu3.debian.tar.xz: done. Uploading gvmd_23.1.0-1ubuntu3_source.changes: done. Successfully uploaded packages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058958 Title: armhf autopkgtest failure (due to time_t format args) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvmd/+bug/2058958/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058622] Re: [needs-packaging] lenovo-wwan-unlock
Hi Dirk Su, If I understood correctly, what you want here is someone to sponsor the upload of lenovo-wwan-unlock, and this is the git repo with the source package: https://launchpad.net/ubuntu/+source/lenovo-wwan-unlock Did I get it right? You added the MIR bug description template here and it seems a bit confusing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058622 Title: [needs-packaging] lenovo-wwan-unlock To manage notifications about this bug go to: https://bugs.launchpad.net/lenovo-wwan-unlock/+bug/2058622/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058192] Re: [MIR][needs-packaging] lenovo-wwan-unlock
I am unsubscribing ~ubuntu-sponsors 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/2058192 Title: [MIR][needs-packaging] lenovo-wwan-unlock To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2058192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058917] Re: cvise 2.10.0-1 still depends on python-pytest-flake8 although upstream dropped it
The changes look good to me. However, when trying to build it in Noble it fails at the moment (because of the ongoing transitions). If I build it with noble-updates I get the following unmet dependencies: The following packages have unmet dependencies: libobjc-13-dev : Depends: gcc-13-base (= 13.2.0-13ubuntu1) but 13.2.0-17ubuntu2 is to be installed Depends: libgcc-13-dev (= 13.2.0-13ubuntu1) but 13.2.0-17ubuntu2 is to be installed If I build it with noble-updates and noble-proposed I get the following unmet dependencies: The following packages have unmet dependencies: libobjc-13-dev : Depends: gcc-13-base (= 13.2.0-13ubuntu1) but 13.2.0-23ubuntu3 is to be installed Depends: libgcc-13-dev (= 13.2.0-13ubuntu1) but 13.2.0-23ubuntu3 is to be installed To be able to build it we need to wait a bit to have gcc-13 installable in Noble. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058917 Title: cvise 2.10.0-1 still depends on python-pytest-flake8 although upstream dropped it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cvise/+bug/2058917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058958] Re: armhf autopkgtest failure (due to time_t format args)
The patch looks good, but I cannot build the package locally due to some uninstallability issues with gcc-13 at the moment in Noble: The following packages have unmet dependencies: libobjc-13-dev : Depends: gcc-13-base (= 13.2.0-13ubuntu1) but 13.2.0-17ubuntu2 is to be installed Depends: libgcc-13-dev (= 13.2.0-13ubuntu1) but 13.2.0-17ubuntu2 is to be installed Because of that I am not sponsoring the package now. Let's wait a bit to see if it will be sorted out. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058958 Title: armhf autopkgtest failure (due to time_t format args) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvmd/+bug/2058958/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060072] [NEW] Removal request to allow ruby-faraday 2.x migration
Public bug reported: ruby-faraday-middleware was marked as deprecated by ruby-faraday 2.x: https://github.com/lostisland/faraday_middleware?tab=readme-ov- file#faraday-middleware As expected, the tests do not work with the new version. We need to follow Debian and request its removal: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025092 There are some dependencies that would also require removals: $ reverse-depends -r noble src:ruby-faraday-middleware Reverse-Depends === * ruby-asana(for ruby-faraday-middleware) * ruby-behance (for ruby-faraday-middleware) * ruby-diaspora-federation (for ruby-faraday-middleware) * ruby-faraday-middleware-multi-json * ruby-gh (for ruby-faraday-middleware) * ruby-graphlient (for ruby-faraday-middleware) * ruby-puppet-forge (for ruby-faraday-middleware) Packages without architectures listed are reverse-dependencies in: amd64, arm64, armhf, i386, ppc64el, s390x $ reverse-depends -r noble src:ruby-faraday-middleware -a source Reverse-Build-Depends = * ruby-asana(for ruby-faraday-middleware) * ruby-behance (for ruby-faraday-middleware) * ruby-diaspora-federation (for ruby-faraday-middleware) * ruby-faraday-middleware-multi-json * ruby-gh (for ruby-faraday-middleware) * ruby-graphlient (for ruby-faraday-middleware) * ruby-puppet-forge (for ruby-faraday-middleware) $ reverse-depends -r noble src:ruby-asana $ reverse-depends -r noble src:ruby-asana -a source No reverse dependencies found $ reverse-depends -r noble src:ruby-diaspora-federation Reverse-Depends === * ruby-diaspora-federation-rails Packages without architectures listed are reverse-dependencies in: amd64, arm64, armhf, i386, ppc64el, s390x $ reverse-depends -r noble src:ruby-diaspora-federation -a source Reverse-Build-Depends = * ruby-diaspora-federation-rails $ reverse-depends -r noble src:ruby-diaspora-federation-rails $ reverse-depends -r noble src:ruby-diaspora-federation-rails -a source No reverse dependencies found $ reverse-depends -r noble src:ruby-faraday-middleware-multi-json Reverse-Depends === * ruby-asana(for ruby-faraday-middleware-multi-json) Packages without architectures listed are reverse-dependencies in: amd64, arm64, armhf, i386, ppc64el, s390x $ reverse-depends -r noble src:ruby-faraday-middleware-multi-json -a source Reverse-Build-Depends = * ruby-asana(for ruby-faraday-middleware-multi-json) $ reverse-depends -r noble src:ruby-gh $ reverse-depends -r noble src:ruby-gh -a source No reverse dependencies found $ reverse-depends -r noble src:ruby-graphlient No reverse dependencies found $ reverse-depends -r noble src:ruby-graphlient -a source No reverse dependencies found $ reverse-depends -r noble src:ruby-puppet-forge Reverse-Depends === * librarian-puppet (for ruby-puppet-forge) * r10k (for ruby-puppet-forge) Packages without architectures listed are reverse-dependencies in: amd64, arm64, armhf, i386, ppc64el, s390x $ reverse-depends -r noble src:ruby-puppet-forge -a source Reverse-Build-Depends = * librarian-puppet (for ruby-puppet-forge) * r10k (for ruby-puppet-forge) $ reverse-depends -r noble src:librarian-puppet $ reverse-depends -r noble src:librarian-puppet -a source No reverse dependencies found $ reverse-depends -r noble src:r10k No reverse dependencies found $ reverse-depends -r noble src:r10k -a source No reverse dependencies found The removal of ruby-behance was already requested here: https://bugs.launchpad.net/ubuntu/+source/ruby-behance/+bug/2060069 In short, I'd like to request the removal of the following source packages and associated binaries: - ruby-faraday-middleware - ruby-asana - ruby-diaspora-federation - ruby-diaspora-federation-rails - ruby-faraday-middleware-multi-json - ruby-gh - ruby-graphlient - ruby-puppet-forge - librarian-puppet - r10k ** Affects: librarian-puppet (Ubuntu) Importance: Undecided Status: New ** Affects: r10k (Ubuntu) Importance: Undecided Status: New ** Affects: ruby-asana (Ubuntu) Importance: Undecided Status: New ** Affects: ruby-diaspora-federation (Ubuntu) Importance: Undecided Status: New ** Affects: ruby-diaspora-federation-rails (Ubuntu) Importance: Undecided Status: New ** Affects: ruby-faraday-middleware (Ubuntu) Importance: Undecided Status: New ** Affects: ruby-faraday-middleware-multi-json (Ubuntu) Importance: Undecided Status: New ** Affects: ruby-gh (Ubuntu) Importance: Undecided Status: New ** Affects: ruby-graphlient (Ubuntu) Importance: Undecided
[Bug 2060069] [NEW] Removal request to allow ruby-faraday 2.x migration
Public bug reported: ruby-behance/0.6.1-4 does not support ruby-faraday 2.x and last upstream commit in the Github repo was from 6 years ago: https://github.com/amedrz/behance Apparently, there will not be any further developement. In Debian, the Ruby team is planning to remove it from the archive: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025094 We will need to do the same to allow ruby-faraday 2.x migration. $ reverse-depends -r noble src:ruby-behance $ reverse-depends -r noble src:ruby-behance -a source No reverse dependencies found Please, remove the ruby-behance source package and its binary. ** Affects: ruby-behance (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/2060069 Title: Removal request to allow ruby-faraday 2.x migration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby-behance/+bug/2060069/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059975] [NEW] Remove from Noble
Public bug reported: ruby-defaults/1:3.2~ubuntu1 is now in the release pocket (the default is ruby3.2) and ruby3.1 (source and binaries) should be removed from Noble. There is no package depending on it in Noble at the moment: $ reverse-depends -r noble src:ruby3.1 $ reverse-depends -r noble src:ruby3.1 -a source Reverse-Build-Depends = * ruby3.1 (for ruby3.1) Please remove the ruby3.1 source package and its binaries. ** Affects: ruby3.1 (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/2059975 Title: Remove from Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby3.1/+bug/2059975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058942] Re: package mysql-server-8.0 8.0.36-0ubuntu0.23.10.1 failed to install/upgrade: subproces van pakket mysql-server-8.0 werd script post-installation geïnstalleerd gaf de foutwaarde 1 teru
Thanks for taking the time to report this bug and trying to make Ubuntu better. Checking the logs, this is the problem you faced: mysqld: Error on realpath() on '"/var/lib/mysql-files/";' (Error 2 - No such file or directory) Could you confirm that the /var/lib/mysql-files does not exist? Did you apply any customization in your environment? ** Changed in: mysql-8.0 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058942 Title: package mysql-server-8.0 8.0.36-0ubuntu0.23.10.1 failed to install/upgrade: subproces van pakket mysql-server-8.0 werd script post-installation geïnstalleerd gaf de foutwaarde 1 terug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/2058942/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051380] Re: Expired certificate used for tests causes failures
** Description changed: + [Impact] + + This is causing a FTBFS, so rubyx.y cannot be rebuilt. + + [Test Plan] + + Build the package in the targeted releases. No test failure is expected. + + [Where Problems could occur] + + The test certificates were renewed, to be honest I fail to foresee any + issue with the proposed change. The only change is the removal of + '-text' from the openssl call, which does not ring any bell for me. + + [Origin Description] + Ruby uses a x590 certificate for some of its tests. It expired at the beginning of the year and this has been causing tests to fail. There is a fix upstream: https://github.com/ruby/ruby/pull/9420/commits/844672256e8e843a7e3a52b7e3c9bb8ea4c328b4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051380 Title: Expired certificate used for tests causes failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby3.0/+bug/2051380/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2049197] Re: ruby_xfree segmentation fault
** Description changed: + [Impact] + + Users might face a segfault when using ruby_free. + + [Test Plan] + + # apt update && apt install -y ruby ruby-nokogiri + # cat > reproducer.rb <=22.04 that causes segfault relatively rarely. Even though rare with repetitions running small wrappers it will be seen quite a bit, up to dozens of times in a day. There exists a patch upstream, could that be picked to Ubuntu repo(s)? The fix and other resources: https://github.com/ruby/ruby/pull/7663 https://bugs.ruby-lang.org/issues/19580 https://gitlab.com/gitlab-org/omnibus-gitlab/-/commit/bd949e2b40cc434a1e4d72be2bff6523e8a91904 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2049197 Title: ruby_xfree segmentation fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby3.0/+bug/2049197/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052313] Re: Ubuntu 24.04 still using Ruby 3.1 close to EOL
No. Ruby 3.2 will be supported by Canonical during lifetime of Noble. We do not change default interpreters in stable releases. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052313 Title: Ubuntu 24.04 still using Ruby 3.1 close to EOL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby-defaults/+bug/2052313/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051380] Re: Expired certificate used for tests causes failures
** Also affects: ruby3.1 (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: ruby3.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: ruby3.0 (Ubuntu Mantic) Status: New => Invalid ** Also affects: ruby3.0 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: ruby3.1 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: ruby3.0 (Ubuntu Jammy) Status: New => In Progress ** Changed in: ruby3.0 (Ubuntu) Status: New => Invalid ** Changed in: ruby3.0 (Ubuntu Jammy) Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro) ** Changed in: ruby3.1 (Ubuntu Jammy) Status: New => Invalid ** Changed in: ruby3.1 (Ubuntu Mantic) Status: New => In Progress ** Changed in: ruby3.1 (Ubuntu Mantic) Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro) ** Tags added: 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/2051380 Title: Expired certificate used for tests causes failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby3.0/+bug/2051380/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052313] Re: Ubuntu 24.04 still using Ruby 3.1 close to EOL
Noble will be released with Ruby 3.2 as the default. Right now, many transitions are ongoing and because of that the ruby one is not complete yet. But do not worry, users will have Ruby 3.2 in Noble. ** Changed in: ruby3.1 (Ubuntu) Status: New => Invalid ** Changed in: ruby-defaults (Ubuntu) Status: New => 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/2052313 Title: Ubuntu 24.04 still using Ruby 3.1 close to EOL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby-defaults/+bug/2052313/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2049197] Re: ruby_xfree segmentation fault
This is fixed in ruby3.2/3.2.3-1build2 in Noble. ** Changed in: ruby3.2 (Ubuntu Noble) Status: Triaged => 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/2049197 Title: ruby_xfree segmentation fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby3.0/+bug/2049197/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2049197] Re: ruby_xfree segmentation fault
Lunar is EOL, so marking its task as Won't Fix.
** Changed in: ruby3.0 (Ubuntu Lunar)
Status: Triaged => Won't Fix
** Also affects: ruby3.1 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ruby3.1 (Ubuntu Jammy)
Status: New => Invalid
** Changed in: ruby3.0 (Ubuntu Mantic)
Status: Triaged => Invalid
** Changed in: ruby3.0 (Ubuntu Noble)
Status: Triaged => Invalid
** Changed in: ruby3.1 (Ubuntu Lunar)
Status: New => Invalid
** Changed in: ruby3.1 (Ubuntu Noble)
Status: New => Invalid
** Also affects: ruby3.2 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ruby3.2 (Ubuntu Jammy)
Status: New => Invalid
** Changed in: ruby3.2 (Ubuntu Lunar)
Status: New => Invalid
** Changed in: ruby3.2 (Ubuntu Mantic)
Status: New => Invalid
** Changed in: ruby3.2 (Ubuntu Noble)
Status: New => Triaged
** Changed in: ruby3.1 (Ubuntu Mantic)
Status: New => Triaged
** Changed in: ruby3.0 (Ubuntu Jammy)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: ruby3.1 (Ubuntu Mantic)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: ruby3.2 (Ubuntu Noble)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Tags added: 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/2049197
Title:
ruby_xfree segmentation fault
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ruby3.0/+bug/2049197/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2035331] Re: Upgrading to version 2.9.1.1
** Merge proposal linked: https://code.launchpad.net/~calvinmwadime/ubuntu/+source/walinuxagent/+git/walinuxagent/+merge/461115 ** Merge proposal linked: https://code.launchpad.net/~calvinmwadime/ubuntu/+source/walinuxagent/+git/walinuxagent/+merge/461117 ** Merge proposal linked: https://code.launchpad.net/~calvinmwadime/ubuntu/+source/walinuxagent/+git/walinuxagent/+merge/461120 ** Merge proposal linked: https://code.launchpad.net/~calvinmwadime/ubuntu/+source/walinuxagent/+git/walinuxagent/+merge/461121 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2035331 Title: Upgrading to version 2.9.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/2035331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040460] Re: MRE updates of container-stack for noble
I am uploading src:runc to the SRU queue but it should land once the src:runc-app is accepted from NEW (in all supported releases). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040460 Title: MRE updates of container-stack for noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd-app/+bug/2040460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2022390] Re: Keep the -dev binary package in sync with Debian
** Also affects: runc-app (Ubuntu) Importance: Undecided Status: New ** Changed in: runc-app (Ubuntu Kinetic) Status: New => Won't Fix ** Changed in: runc-app (Ubuntu Lunar) Status: New => Won't Fix ** Changed in: runc (Ubuntu Lunar) Status: New => Won't Fix ** Also affects: docker.io (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: runc (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: containerd (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: docker.io-app (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: containerd-app (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: runc-app (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: containerd (Ubuntu Mantic) Status: New => Fix Released ** Changed in: containerd-app (Ubuntu Mantic) Status: New => Fix Released ** Changed in: docker.io (Ubuntu Mantic) Status: New => Fix Released ** Changed in: docker.io-app (Ubuntu Mantic) Status: New => Fix Released ** Changed in: runc (Ubuntu Mantic) Status: New => In Progress ** Changed in: runc (Ubuntu Mantic) Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro) ** Changed in: runc (Ubuntu Jammy) Status: New => In Progress ** Changed in: runc (Ubuntu Jammy) Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro) ** Changed in: runc (Ubuntu Focal) Status: New => In Progress ** Changed in: runc (Ubuntu Focal) Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro) ** Changed in: runc-app (Ubuntu) Status: New => Fix Released ** Changed in: runc-app (Ubuntu Focal) Status: New => In Progress ** Changed in: runc-app (Ubuntu Focal) Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro) ** Changed in: runc-app (Ubuntu Jammy) Status: New => In Progress ** Changed in: runc-app (Ubuntu Jammy) Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro) ** Changed in: runc-app (Ubuntu Mantic) Status: New => In Progress ** Changed in: runc-app (Ubuntu Mantic) Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2022390 Title: Keep the -dev binary package in sync with Debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/2022390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040460] Re: MRE updates of container-stack for noble
** Description changed: - Backport container-stack as MRE to noble once the update for noble has - been completed. + [Impact] - + In order to follow our policy on keeping the container stack (docker.io- + app, containerd-app, runc, runc-app, docker-buildx, and docker- + compose-v2) up-to-date in our supported releases, let's backport the + stack in Noble to Mantic, Jammy, and Focal. - [Impact] - TBD + src:runc will not be updated anymore in stable releases, and the final + change is to make it not provide the runc binary packages. This work is + tracked here: - [Major Changes] - TBD + https://bugs.launchpad.net/ubuntu/lunar/+source/docker.io- + app/+bug/2022390 [Test Plan] - TBD - [Regression Potential] - Upstream has an extensive build and integration test suite. So regressions would likely arise from a change in interaction with Ubuntu-specific integrations, such as in relation to the versions of dependencies available and other packaging-specific matters. - + Per https://wiki.ubuntu.com/DockerUpdates, our test case is the + autopkgtests. + + [Where problems could occur] + + As usual, we deliver most benefit to our users by delivering an upstream + experience. A risk of regressions is part of that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040460 Title: MRE updates of container-stack for noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd-app/+bug/2040460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040460] Re: MRE updates of container-stack for noble
** Changed in: containerd-app (Ubuntu Noble) Milestone: ubuntu-24.02 => ubuntu-24.03 ** Changed in: docker.io-app (Ubuntu Noble) Milestone: ubuntu-24.02 => ubuntu-24.03 ** Changed in: runc (Ubuntu Noble) Milestone: ubuntu-24.02 => ubuntu-24.03 ** Changed in: runc (Ubuntu Noble) Status: New => Invalid ** Changed in: docker.io-app (Ubuntu Noble) Status: New => Invalid ** Changed in: containerd-app (Ubuntu Noble) Status: New => Invalid ** Changed in: containerd-app (Ubuntu Mantic) Status: New => In Progress ** Changed in: containerd-app (Ubuntu Jammy) Status: New => In Progress ** Changed in: containerd-app (Ubuntu Focal) Status: New => In Progress ** Changed in: docker.io-app (Ubuntu Focal) Status: New => In Progress ** Changed in: docker.io-app (Ubuntu Jammy) Status: New => In Progress ** Changed in: docker.io-app (Ubuntu Mantic) Status: New => In Progress ** Changed in: runc (Ubuntu Focal) Status: New => In Progress ** Changed in: runc (Ubuntu Jammy) Status: New => In Progress ** Changed in: runc (Ubuntu Mantic) Status: New => In Progress ** Also affects: runc-app (Ubuntu) Importance: Undecided Status: New ** Changed in: runc-app (Ubuntu Noble) Status: New => Invalid ** Changed in: runc-app (Ubuntu Focal) Status: New => In Progress ** Changed in: runc-app (Ubuntu Jammy) Status: New => In Progress ** Changed in: runc-app (Ubuntu Mantic) Status: New => In Progress ** Also affects: docker-buildx (Ubuntu) Importance: Undecided Status: New ** Changed in: docker-buildx (Ubuntu Noble) Status: New => Invalid ** Changed in: docker-buildx (Ubuntu Mantic) Status: New => In Progress ** Changed in: docker-buildx (Ubuntu Jammy) Status: New => In Progress ** Changed in: docker-buildx (Ubuntu Mantic) Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro) ** Changed in: docker-buildx (Ubuntu Jammy) Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro) ** Changed in: docker-buildx (Ubuntu Focal) Status: New => In Progress ** Changed in: docker-buildx (Ubuntu Focal) Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro) ** Changed in: runc-app (Ubuntu Focal) Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro) ** Changed in: runc-app (Ubuntu Jammy) Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro) ** Changed in: runc-app (Ubuntu Mantic) Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro) ** Also affects: docker-compose-v2 (Ubuntu) Importance: Undecided Status: New ** Changed in: docker-compose-v2 (Ubuntu Noble) Status: New => Invalid ** Changed in: docker-compose-v2 (Ubuntu Focal) Status: New => In Progress ** Changed in: docker-compose-v2 (Ubuntu Focal) Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro) ** Changed in: docker-compose-v2 (Ubuntu Jammy) Status: New => In Progress ** Changed in: docker-compose-v2 (Ubuntu Jammy) Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro) ** Changed in: docker-compose-v2 (Ubuntu Mantic) Status: New => In Progress ** Changed in: docker-compose-v2 (Ubuntu Mantic) Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro) ** Changed in: docker.io-app (Ubuntu Noble) Assignee: Lucas Kanashiro (lucaskanashiro) => (unassigned) ** Changed in: containerd-app (Ubuntu Noble) Assignee: Lucas Kanashiro (lucaskanashiro) => (unassigned) ** Changed in: runc (Ubuntu Noble) Assignee: Lucas Kanashiro (lucaskanashiro) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040460 Title: MRE updates of container-stack for noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd-app/+bug/2040460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056760] Re: [snap]Thunderbird doesn't authenticate with sssd-kcm
Hi Helga, Thanks for taking the time to report this bug and trying to make Ubuntu better. From what I understood this is an issue with the snap package of Thunderbird, if that's the case you should try to report here (?): https://snapcraft.io/thunderbird I am not sure if this bug will reach the snap maintainers here. And I do not think this is an issue with the sssd package in the Ubuntu archive, but an integration issue affecting the snap package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056760 Title: [snap]Thunderbird doesn't authenticate with sssd-kcm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2056760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056372] Re: Enabling SPF checks with CHECK_RCPT_SPF doesn't work
Could you provide your config file? Also state if you applied any customization in your set up? Those things would be useful to reproduce what you described locally. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056372 Title: Enabling SPF checks with CHECK_RCPT_SPF doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/2056372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056443] Re: CHECK_RCPT_SPF SPF check fails if inbound IP address is IPv6
Shouldn't this be marked as duplicate then? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056443 Title: CHECK_RCPT_SPF SPF check fails if inbound IP address is IPv6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/2056443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056154] Re: Please build with golang-1.21 or golang-1.22
I am working on it. ** Changed in: containerd-app (Ubuntu) Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro) ** Changed in: docker.io-app (Ubuntu) Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro) ** Changed in: containerd-app (Ubuntu) Status: New => In Progress ** Changed in: docker.io-app (Ubuntu) Status: New => 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/2056154 Title: Please build with golang-1.21 or golang-1.22 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd-app/+bug/2056154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055344] [NEW] Do not support ruby-rmagick 5.3.0
Public bug reported: ruby-gruff/0.6.0-2 do not support ruby-rmagick/5.3.0-2build2 and this is blocking the ruby-defaults migration. There is a new upstream release of ruby-gruff (a.k.a. version 0.23.0) which seems to support this newer version of ruby-rmagick, however, it requires some new dependencies that are not available in the archive (Debian and Ubuntu). Due to time constraints (Feature Freeze is approaching), let's follow Debian and remove ruby-gruff to unblock the ruby 3.2 transition: https://tracker.debian.org/news/1481195/ruby-gruff-removed-from-testing/ It has no reverse dependencies: $ reverse-depends -r unstable src:ruby-gruff No reverse dependencies found $ reverse-depends -r unstable src:ruby-gruff -a source No reverse dependencies found Please, remove source and binary ruby-gruff packages from Noble. ** Affects: ruby-gruff (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/2055344 Title: Do not support ruby-rmagick 5.3.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby-gruff/+bug/2055344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040410] Re: Merge pcs from Debian unstable for noble
** Changed in: pcs (Ubuntu) Status: New => In Progress ** Changed in: pcs (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/2040410 Title: Merge pcs from Debian unstable for noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcs/+bug/2040410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055221] [NEW] Do not support ruby 3.2
Public bug reported: ruby-rgfa/1.3.1+dfsg-2 does not support ruby 3.2. Many core feature of this gem rely on methods that were removed from ruby 3.2. I do not expect any fix from upstream, since the last commit is from 8 years ago: https://github.com/ggonnella/rgfa FWIW this is the autopkgtest log with some test failures: https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest- noble/noble/amd64/r/ruby-rgfa/20240225_030611_24c6e@/log.gz The package has no reverse dependencies: $ reverse-depends -r noble src:ruby-rgfa $ reverse-depends -r noble src:ruby-rgfa -a source No reverse dependencies found So please, remove binary and source packages of ruby-rgfa from Noble to unblock the ruby 3.2 transition. ** Affects: ruby-rgfa (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/2055221 Title: Do not support ruby 3.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby-rgfa/+bug/2055221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055217] [NEW] Do not support ruby 3.2
Public bug reported: diaspora-installer/0.7.18.2+debian4 do not support ruby 3.2. Initially we have an issue with the configurate gem native extension build, which can be seen in the autopkgtest log: https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest- noble/noble/amd64/d/diaspora-installer/20240225_030752_2176a@/log.gz After talking to the Debian maintainer, we noticed that we could patch the upstream Gemfile to use the newer version of configurate. The patch below fixed that issue: diff --git a/debian/ruby3.patch b/debian/ruby3.patch index 469be89..f469d33 100644 --- a/debian/ruby3.patch +++ b/debian/ruby3.patch @@ -121,7 +121,8 @@ @@ -142,7 +193,7 @@ coderay (1.1.3) concurrent-ruby (1.1.10) - configurate (0.5.0) +-configurate (0.5.0) ++configurate (0.6.0) -connection_pool (2.2.5) +connection_pool (2.4.1) crack (0.4.5) However, another issue popped up after that, now because railties 6.1.6.1 does not support ruby 3.2, autopkgtest log pasted here: https://paste.ubuntu.com/p/2Szv3sGJv8/ railties is a key gem for rails, rails et al version 7 seems to support ruby 3.2 but the version used but diaspora not. I checked diaspora develop upstream branch and they are still using rails 6: https://github.com/diaspora/diaspora/blob/develop/Gemfile#L5 So upstream does not support the newer rails version which fixed the issue presented above. Due to that, I request the removal of the source and binary packages of diaspora-installer from Noble. As expected, it has not reverse dependency: $ reverse-depends -r noble src:diaspora-installer No reverse dependencies found $ reverse-depends -r noble src:diaspora-installer -a source No reverse dependencies found ** Affects: diaspora-installer (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/2055217 Title: Do not support ruby 3.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/diaspora-installer/+bug/2055217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 720638] Re: snmpd crashes with segfault (libnetsnmpmibs.so.15.1.2)
Hi, Could you please share the core dump with us? That would help us investigate better this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/720638 Title: snmpd crashes with segfault (libnetsnmpmibs.so.15.1.2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/720638/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968922] Re: libnss3 is affected by CVE-2022-22747
Hi Luís, This CVE is indeed not fixed yet in none of the Ubuntu releases: https://ubuntu.com/security/CVE-2022-22747 As you can see on the top of the page the priority was marked as Low, so I think the Security team is not considering this too important. Maybe someone from the Security team could chime in and explain the situation better than me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1968922 Title: libnss3 is affected by CVE-2022-22747 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1968922/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975768] Re: Backport container-stack as MRE for bionic, focal, impish, jammy (May)
*** This bug is a duplicate of bug 1960449 *** https://bugs.launchpad.net/bugs/1960449 The backport of the following packages were done in Jammy, Impish and Focal: - runc version 1.1.0 - containerd version 1.5.9 - docker.io version 20.10.12 This is not fully complete (missing Bionic) because to backport those packages we need at least Golang 1.16 which is still not present in Bionic. I prepared a Golang 1.16 package and it is in Bionic's NEW queue waiting for some one with archive admin and SRU powers to review it: https://bugs.launchpad.net/ubuntu/+source/golang-1.16/+bug/1967425 FWIW this is the LP bug I was using to do this work (it is more accurate, with more info): https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1960449 I'll mark this one as duplicate of the above. ** Changed in: containerd (Ubuntu) Milestone: ubuntu-22.09 => ubuntu-22.06 ** Changed in: docker.io (Ubuntu) Milestone: ubuntu-22.09 => ubuntu-22.06 ** Changed in: runc (Ubuntu) Milestone: ubuntu-22.09 => ubuntu-22.06 ** Summary changed: - Backport container-stack as MRE for bionic, focal, impish, jammy (May) + Backport container-stack as MRE for bionic, focal, impish, jammy (June) ** This bug has been marked a duplicate of bug 1960449 Backport container stack in Jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975768 Title: Backport container-stack as MRE for bionic, focal, impish, jammy (June) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1975768/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975769] Re: Backport container-stack as MRE for bionic, focal, jammy (September)
I'd not call those update as MREs because we update all the release sometimes with a major bump of the upstream version. ** Summary changed: - Backport container-stack as MRE for bionic, focal, impish, jammy (August) + Backport container-stack as MRE for bionic, focal, jammy (September) ** Changed in: containerd (Ubuntu) Milestone: ubuntu-22.08 => ubuntu-22.09 ** Changed in: containerd (Ubuntu) Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro) ** Changed in: docker.io (Ubuntu) Milestone: ubuntu-22.08 => ubuntu-22.09 ** Changed in: docker.io (Ubuntu) Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro) ** Changed in: runc (Ubuntu) Milestone: ubuntu-22.08 => ubuntu-22.09 ** Changed in: runc (Ubuntu) Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro) ** Description changed: - Backport container-stack as MRE for bionic, focal, impish, jammy + Backport container-stack as MRE for bionic, focal, jammy ** Changed in: containerd (Ubuntu Impish) Status: New => Won't Fix ** Changed in: docker.io (Ubuntu Impish) Status: New => Won't Fix ** Changed in: runc (Ubuntu Impish) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975769 Title: Backport container-stack as MRE for bionic, focal, jammy (September) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1975769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971268] Re: Merge cluster-glue from Debian unstable for kinetic
** Changed in: cluster-glue (Ubuntu) Milestone: ubuntu-22.05 => ubuntu-22.06 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971268 Title: Merge cluster-glue from Debian unstable for kinetic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cluster-glue/+bug/1971268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975768] Re: Backport container-stack as MRE for bionic, focal, impish, jammy (May)
** Changed in: containerd (Ubuntu) Milestone: ubuntu-22.05 => ubuntu-22.10 ** Changed in: containerd (Ubuntu) Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro) ** Changed in: docker.io (Ubuntu) Milestone: ubuntu-22.05 => ubuntu-22.10 ** Changed in: docker.io (Ubuntu) Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro) ** Changed in: runc (Ubuntu) Milestone: ubuntu-22.05 => ubuntu-22.09 ** Changed in: runc (Ubuntu) Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro) ** Changed in: docker.io (Ubuntu) Milestone: ubuntu-22.10 => ubuntu-22.09 ** Changed in: containerd (Ubuntu) Milestone: ubuntu-22.10 => ubuntu-22.09 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975768 Title: Backport container-stack as MRE for bionic, focal, impish, jammy (May) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1975768/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971317] Re: Merge resource-agents from Debian unstable for kinetic
** Changed in: resource-agents (Ubuntu) Milestone: ubuntu-22.05 => ubuntu-22.06 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971317 Title: Merge resource-agents from Debian unstable for kinetic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/1971317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971275] Re: Merge fence-agents from Debian unstable for kinetic
** Changed in: fence-agents (Ubuntu) Milestone: ubuntu-22.05 => ubuntu-22.06 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971275 Title: Merge fence-agents from Debian unstable for kinetic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1971275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976264] Re: rubygems ftbfs in the jammy release pocket
** Description changed: + [Impact] + + The package is FTBFSing in Jammy which does not allow anyone to perform + any kind of update there. This package is in main and to be fully + supported one needs to be able to rebuild it and perform updates. + + [Test Plan] + + Build the package in jammy successfully. + + [Where problems could occur] + + It could pull in different version of build dependencies causing + unexpected issues. I do not foresee any issue TBH. + + [Original description] + as seen in a test rebuild, this package fails to build in the jammy release pocket (note the log behind the link might go away): https://launchpadlibrarian.net/604215677/buildlog_ubuntu-jammy- amd64.rubygems_3.3.5-2_BUILDING.txt.gz [...] --- 2205 tests, 5870 assertions, 5 failures, 0 errors, 42 pendings, 0 omissions, 0 notifications 97.8685% passed --- 71.17 tests/s, 189.47 assertions/s rake aborted! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976264 Title: rubygems ftbfs in the jammy release pocket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rubygems/+bug/1976264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969939] Re: puppet 5 package incompatible with ruby 3 / ubuntu 22.04
Thanks for the feedback everyone. I'll give a chance to others to test it over the weekend, if I get no negative feedback until Monday I'll be uploading this fix to kinetic and SRU it to jammy. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969939 Title: puppet 5 package incompatible with ruby 3 / ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1969939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976264] Re: rubygems ftbfs in the jammy release pocket
** Changed in: rubygems (Ubuntu Kinetic) Status: Triaged => Fix Committed ** Changed in: rubygems (Ubuntu Jammy) 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/1976264 Title: rubygems ftbfs in the jammy release pocket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rubygems/+bug/1976264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976307] Re: Stack smashing in gamatronic driver
Thanks for reporting this bug Claudio. As you might have expected I was not able to reproduce it locally. After checking the the core dump, we can see the crash happened when executing the sec_poll function in drivers/gamatronic.c file. I went through the upstream history of this file and I found some commits in the latest version (2.8.0) which might fix this issue for you. Since version 2.8.0 is not even in Debian yet, I prepared a "dirty" package (removed some docs and manpages) and put it in this PPA: https://launchpad.net/~lucaskanashiro/+archive/ubuntu/nut Could you please try to test it and see if it fixes this issue for you? If yes, we can try to dig into those upstream commits and then find what is needed to SRU to jammy. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976307 Title: Stack smashing in gamatronic driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1976307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976264] Re: rubygems ftbfs in the jammy release pocket
** Also affects: rubygems (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: rubygems (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: rubygems (Ubuntu Jammy) Status: New => Triaged ** Changed in: rubygems (Ubuntu Kinetic) Status: New => Triaged ** Changed in: rubygems (Ubuntu Jammy) Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro) ** Changed in: rubygems (Ubuntu Kinetic) Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro) ** Tags added: 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/1976264 Title: rubygems ftbfs in the jammy release pocket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rubygems/+bug/1976264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976279] Re: FTBFS ppc64el: obj_ctl_arenas/TEST3 failure
** Changed in: pmdk (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976279 Title: FTBFS ppc64el: obj_ctl_arenas/TEST3 failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pmdk/+bug/1976279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969939] Re: puppet 5 package incompatible with ruby 3 / ubuntu 22.04
Hi all, I prepared a patch myself to fix this. Could you please test the package in this PPA? https://launchpad.net/~lucaskanashiro/+archive/ubuntu/puppet/ This is a workaround and I'd like to make sure this is not impacting anything else. Please, report back with your findings. Once we get enough feedback I'll move forward to push this into the archive. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969939 Title: puppet 5 package incompatible with ruby 3 / ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1969939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969939] Re: puppet 5 package incompatible with ruby 3 / ubuntu 22.04
Thanks for the reproducer Mat! I can reproduce it locally now, and this is also impacting kinetic. I'll be working on it. ** Changed in: puppet (Ubuntu Kinetic) Status: Fix Released => 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/1969939 Title: puppet 5 package incompatible with ruby 3 / ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1969939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975868] [NEW] [RM] removed in Debian testing and blocking libdigest-bcrypt-perl
Public bug reported: libdancer2-plugin-passphrase-perl was removed from Debian testing in February during the Perl transition [1], and it is blocking libdigest- bcrypt-perl migration in kinetic for more than 120 days. This package is also blocked in Debian unstable for more than 765 days [2]. This is a leaf package, I believe we should remove it from kinetic until it gets in better shape. $ reverse-depends src:libdancer2-plugin-passphrase-perl No reverse dependencies found $ reverse-depends src:libdancer2-plugin-passphrase-perl -a source No reverse dependencies found [1] https://tracker.debian.org/news/1301920/libdancer2-plugin-passphrase-perl-removed-from-testing/ [2] https://tracker.debian.org/pkg/libdancer2-plugin-passphrase-perl ** Affects: libdancer2-plugin-passphrase-perl (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975868 Title: [RM] removed in Debian testing and blocking libdigest-bcrypt-perl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdancer2-plugin-passphrase-perl/+bug/1975868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968831] Re: ruby-tty-screen: endianness bug detected by autopkgtest
Filed an upstream bug: https://github.com/piotrmurach/tty- screen/issues/14 ** Bug watch added: github.com/piotrmurach/tty-screen/issues #14 https://github.com/piotrmurach/tty-screen/issues/14 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968831 Title: ruby-tty-screen: endianness bug detected by autopkgtest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby-tty-screen/+bug/1968831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969939] Re: puppet 5 package incompatible with ruby 3 / ubuntu 22.04
As you can see in comment #17, I have not been able to reproduce the error people are reporting, so I can't help with this analysis. From what I understood, this is not crashing anything (like it is right now when someone tries to create a symlink). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969939 Title: puppet 5 package incompatible with ruby 3 / ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1969939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964025] Re: Do not support OpenSSL 3
This fix is also released in kinetic, ruby-net-ssh/1:7.0.0~beta1-2 contains the fix. ** Changed in: ruby-net-ssh (Ubuntu Kinetic) 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/1964025 Title: Do not support OpenSSL 3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby-bcrypt-pbkdf/+bug/1964025/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969939] Re: puppet 5 package incompatible with ruby 3 / ubuntu 22.04
Since no one gave me a way yet to reproduce the mentioned errors locally, and the originally reported bug (the symlink issue) is fixed, I am marking the verification as done. Please, file a new bug with reproduction steps for the error you all mentioned, so I can investigate it further. ** 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 Ubuntu. https://bugs.launchpad.net/bugs/1969939 Title: puppet 5 package incompatible with ruby 3 / ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1969939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927755] Re: Fix for CVE-2020-28007 causes build failure when DMARC is enabled
Hirsute has reached the end of standard support. ** Changed in: exim4 (Ubuntu Hirsute) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927755 Title: Fix for CVE-2020-28007 causes build failure when DMARC is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/1927755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975496] Re: package openssh-server 1:8.2p1-4ubuntu0.5 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1
Thanks for taking the time to report this bug and trying to make Ubuntu better. From the sshd logs in the description we can see: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: /etc/ssh/sshd_config: line 125: Bad configuration option: Host /etc/ssh/sshd_config: line 126: Bad configuration option: ForwardX11 /etc/ssh/sshd_config: terminating, 2 bad configuration options Which tells us that your sshd_config file has some bad configuration on line 125 and 126. Please, revisit your configuration file and fix it up. Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I am marking this bug as 'Incomplete'. However, if you believe that this is really a bug in Ubuntu, then we would be grateful if you would provide a more complete description of the problem with steps to reproduce, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to "New". For local configuration issues, you can find assistance here: http://www.ubuntu.com/support/community ** Changed in: openssh (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975496 Title: package openssh-server 1:8.2p1-4ubuntu0.5 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1975496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974251] Re: libapache2-mod-shib module doesn't work with 2.4.52
Considering that version 2.4.53 is fixed, this should land in Kinetic soon. In order to fix this issue in Jammy, we need to follow the SRU process [1], and to do that we would need to have a test case with reproduction steps. Another thing that is needed here is to bisect the changes between 2.4.52 and 2.4.53 to find the specific fix for this issue, and backport it to the Jammy version. [1] https://wiki.ubuntu.com/StableReleaseUpdates -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974251 Title: libapache2-mod-shib module doesn't work with 2.4.52 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1974251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971248] Re: Merge apache2 from Debian unstable for kinetic
According to the user report, the following bug is fixed in version 2.4.53: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1974251 Let's keep that in mind when finishing up the merge. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971248 Title: Merge apache2 from Debian unstable for kinetic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1971248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1304557] Re: rmdir: failed to remove ‘/etc/dhcp3/dhclient-enter-hooks.d’: No such file or directory
Trusty has reached the end of the standard support. ** Changed in: samba (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1304557 Title: rmdir: failed to remove ‘/etc/dhcp3/dhclient-enter-hooks.d’: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1304557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940077] Re: Please do not use uml fakemachine backend in the DEP-8 test
I did run autopkgtest locally using the proposed packages and it indeed fixes the test failure. The log is attached. ** Attachment added: "log" https://bugs.launchpad.net/ubuntu/+source/debos/+bug/1940077/+attachment/5592392/+files/log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940077 Title: Please do not use uml fakemachine backend in the DEP-8 test To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debos/+bug/1940077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940077] Re: Please do not use uml fakemachine backend in the DEP-8 test
Since we did not get a reply from the Debian maintainers I am proposing the attached debdiff to fix this issue. As Steve suggested, I patched the failing test to use --disable-fakemachine and adjusted the test dependencies and added the needs-root restrictions. ** Attachment added: "debdiff" https://bugs.launchpad.net/ubuntu/+source/debos/+bug/1940077/+attachment/5592391/+files/debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940077 Title: Please do not use uml fakemachine backend in the DEP-8 test To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debos/+bug/1940077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975523] [NEW] [MIR] Promote to main in Jammy and Kinetic
Public bug reported: [Availability] ruby-webrick is already in Ubuntu universe since Jammy. It is an arch:all package and it builds fine in amd64, all tests pass successfully. Here its LP page: https://launchpad.net/ubuntu/+source/ruby-webrick [Rationale] This ruby gem was embedded in the ruby interpreter until ruby 2.7. In ruby 3.0, it was removed from the interpreter source tree by upstream decision and packaged separetely. Many packages still rely on it, and it is a low maintanence package. The most important package depending on it is rubygems which is in main. Because that happens since Jammy we should promote ruby-webrick in Jammy and Kinetic. pcs is another package which its promotion to main is planned for this cycle and depends on it. [Security] Searching for ruby-webrick the following was found: * 26 CVEs (most of them are old issues) http://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=webrick * No CVEs in the Ubuntu tracker (the package was introduced in Jammy only and most of issues are older than that): https://ubuntu.com/security/cves?package=ruby-webrick The package itself does not provide any binary. However, this is a library that allows one to set up your own HTTP server, so the script/software written using this library can open ports for instance, but I do not think this is a concern regarding the MIR process. [Quality assurance - function/usage] The package works well right after installation. The user needs to understand the library API and that is it. [Quality assurance - maintenance] ruby-webrick upstream maintainers do not seem so responsive in the few upstream bugs that are filed on Github: https://github.com/ruby/webrick/issues However, most of them do not seem to be critical. There is one OpenSSL 3 specific issue that might be impacting Ubuntu but no one found that yet to file a bug: https://github.com/ruby/webrick/issues/90 But it seems they are responsive when the problem is security related. Some of the maintainers are also ruby interpreter maintainers. There is no bug reported against Debian nor Ubuntu. [Quality assurance - testing] Upstream provides a comprehensive test suite which is executed during package build time. The same set of tests are executed using autopkgtest, this is triggered by ruby autodep8. This is an arch:all package and it has been building fine since it was introduced in Ubuntu: https://launchpad.net/ubuntu/+source/ruby- webrick/1.7.0-3/+build/22464915 autopkgtest is passing in all supported architectures: https://autopkgtest.ubuntu.com/packages/ruby-webrick [Quality assurance - packaging] The package contains a working debian/watch file. Nothing important reported by lintian, no overrides also. This is a straightforward packages, similar to most ruby gems we have packaged in the archive. [UI standards] This is a library, no need to translation, desktop files, or anything UI related. [Dependencies] The only two build dependencies it has is debhelper-compat and gem2deb, gem2deb is in universe but it is used to build most of ruby packages. No runtime dependency apart from regular ruby. [Standards compliance] This package correctly follows FHS and Debian Policy. [Maintenance/Owner] This package will be owned by the Server team since we already maintain the ruby stack. This package is well maintained in Debian, so this is low effort in Ubuntu since it is a sync. The Server team is not yet subscribed to the package, but will subscribe before promotion. [Background information] The Package description explains the package well. Link to upstream project: https://github.com/ruby/webrick ** Affects: ruby-webrick (Ubuntu) Importance: Undecided Status: New ** Affects: ruby-webrick (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: ruby-webrick (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: ruby-webrick (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: ruby-webrick (Ubuntu Kinetic) 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/1975523 Title: [MIR] Promote to main in Jammy and Kinetic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby-webrick/+bug/1975523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971294] Re: Merge nbd from Debian unstable for kinetic
+1, please go ahead and sync it Athos. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971294 Title: Merge nbd from Debian unstable for kinetic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nbd/+bug/1971294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964025] Re: Do not support OpenSSL 3
No, you do not need to enable any repository. ruby-net- ssh/1:6.1.0-2ubuntu0.1 landed in jammy-updates which should be enabled by default on your system. The link to the stackoverflow page you sent is old, and at that time it was broken. This fix was even acknowledged on an upstream issue: https://github.com/hashicorp/vagrant/issues/12751#issuecomment-1132239703 ** Bug watch added: github.com/hashicorp/vagrant/issues #12751 https://github.com/hashicorp/vagrant/issues/12751 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964025 Title: Do not support OpenSSL 3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby-bcrypt-pbkdf/+bug/1964025/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641238] Re: as a reverse proxy, a 100 continue response is sent prematurely when a request contains expects: 100-continue
** Changed in: apache2 (Ubuntu Eoan) Status: Fix Released => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641238 Title: as a reverse proxy, a 100 continue response is sent prematurely when a request contains expects: 100-continue To manage notifications about this bug go to: https://bugs.launchpad.net/apache2/+bug/1641238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641305] Re: apparmor configuration for mysqld is not complete
** Also affects: mysql-5.5 (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: mysql-5.5 (Ubuntu) Status: Confirmed => Does Not Exist ** Changed in: mysql-5.5 (Ubuntu Trusty) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641305 Title: apparmor configuration for mysqld is not complete To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1641305/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831441] Re: Please add WS-Discovery ( WSD ) support for Windows Samba server discovery.
What are the next steps here? Are people willing to try to promote wsdd to main? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831441 Title: Please add WS-Discovery ( WSD ) support for Windows Samba server discovery. To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/1831441/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973217] Re: package openssh-server 1:8.2p1-4ubuntu0.5 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1
Thanks for taking the time to file this bug and trying to make Ubuntu better. From the attached logs: May 12 08:50:07 paradise sshd[59551]: /etc/ssh/sshd_config: line 125: Bad configuration option: Host May 12 08:50:07 paradise sshd[59551]: /etc/ssh/sshd_config: line 126: Bad configuration option: ForwardX11 May 12 08:50:07 paradise sshd[59551]: /etc/ssh/sshd_config: terminating, 2 bad configuration options Which tells us that this is a local configuration issue. The Host and ForwardX11 options are causing the issue, avoiding the service to start. Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I am marking this bug as 'Incomplete'. However, if you believe that this is really a bug in Ubuntu, then we would be grateful if you would provide a more complete description of the problem with steps to reproduce, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to "New". For local configuration issues, you can find assistance here: http://www.ubuntu.com/support/community -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973217 Title: package openssh-server 1:8.2p1-4ubuntu0.5 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1973217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973593] Re: package mysql-server-8.0 8.0.29-0ubuntu0.20.04.3 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1
Thanks for taking the time to file this bug and trying to make Ubuntu better. I see you are using the option NO_AUTO_CREATE_USER in sql_mode, as you can see here [1] this is no more supported in MySQL 8 which is the version we have in Ubuntu 20.04. So to fix your issue you need to remove that option. Please review all your configuration to make sure it is supported in MySQL 8. [1] https://dev.mysql.com/doc/refman/8.0/en/mysql-nutshell.html#mysql- nutshell-deprecations Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I am marking this bug as 'Incomplete'. However, if you believe that this is really a bug in Ubuntu, then we would be grateful if you would provide a more complete description of the problem with steps to reproduce, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to "New". For local configuration issues, you can find assistance here: http://www.ubuntu.com/support/community ** Changed in: mysql-8.0 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973593 Title: package mysql-server-8.0 8.0.29-0ubuntu0.20.04.3 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1973593/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
