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
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
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,
** 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
** 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
** 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 unsta
** 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 unsta
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
** 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
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.
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
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
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
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
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
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
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
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,
@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
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
@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
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
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
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:
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
# 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
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
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
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
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
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.
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
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
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
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 (=
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
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
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:
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 (=
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
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:
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
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
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
** 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
** 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
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
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 (luc
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
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:
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
** 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:
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
c)
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 Kanas
** 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
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: (u
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
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.
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
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)
Statu
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
** 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:
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
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:
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
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
*** 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)
)
** 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)
** 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
** 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.i
** 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
** 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
** 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
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
** 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.
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
tus: 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
** 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
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
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
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].
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
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
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.
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
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
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:
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
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
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
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
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"
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
+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:
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:
** 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
** 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
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
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
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
1 - 100 of 1187 matches
Mail list logo
