I had the chance to discuss this more in detail in a side channel, so
I'll take this FFe review.
Considering the rationale, the fact mysql-shell is entirely new
functionality, and the proposed QA plan (dep8 tests, ppa test rebuild),
I think this qualifies for a FFe.
The FFe is granted, however pl
** Changed in: autopkgtest (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu)
Status: New => Invalid
** Changed in: auto-package-testing
Status: Invalid => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
That is now merged upstream. I cherry-picked the commit to the branch we
use in the infrastructure, so I'm marking that task as Fix Released.
** Changed in: auto-package-testing
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bu
Some questions on:
- libtins4.0 (>=4.0),
- libtins-dev (>=4.0),
+ libtins-dev,
+ libssl-dev,
I don't think the versioned build depends
libtins-dev (>=4.0),
was problematic. By dropping the (>=4.0) you are just allowing older
versions of the package to satisfy the dependency, and we are not
in
Hello Nathan,
the diff LGTM, I just have two questions:
1. The bug description has a "test case", but that's more of a
reproducer than of a test case, right? The "expected result" is not
explicitly stated. In particular, looking at this step:
- After Authentication, nothing happens.
what shoul
Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981762
The proposed fix almost matches what has been sitting in salsa for 3
years (never uploaded):
https://salsa.debian.org/scheme-team/chibi-
scheme/-/commit/2f0031a411cb6de4b2ff50163b72ba6a9559468e
This fix adds a dependency on
+1 for enabling build-time testing, but that does not make an
autopkgtest.
Autopkgtests should test the package as installed in an Ubuntu system;
rebuilding the package (you have Restrictions: build-needed) and re-
running the upstream test suite in the build tree adds nothing to the
tests run at
Hello, lighttpd 1.4.75 is not packages in Debian yet. Once packaged
there it may (or may not!) come to Noble as a microrelease upgrade, see
[1].
On your bug: please file a new bug stating the problem with
mod_dirlisting and pointing to the fix. The fix may be delivered as a
"normal" bugfix, cherry
I think those issues are now gone. I tried to build the package locally
in a noble schroot and it succeeded. I'm proceeding with the sync.
--
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:
** Changed in: software-properties (Ubuntu)
Assignee: (unassigned) => Nathan Teodosio (nteodosio)
** Changed in: software-properties (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
Request succeeded; you should get an e-mail once it is processed.
(I didn't receive the e-mail yet, but maybe this is taking a bit longer
because of the Beta Freeze. I'm marking this a Fix Released; please
reach out if you think the sync didn't succeed.)
** Changed in: rocm-hipamd (Ubuntu)
Uploading to ubuntu (via ftp to upload.ubuntu.com):
Uploading software-properties_0.99.47.dsc: done.
Uploading software-properties_0.99.47.tar.xz: done.
Uploading software-properties_0.99.47_source.buildinfo: done.
Uploading software-properties_0.99.47_source.changes: done.
Successful
Thanks! The diff now LGTM. I adjusted the bug subject as what we have
here is a "fails to build from source" issue.
** Summary changed:
- dublin-traceroute fails to install in Noble
+ dublin-traceroute FTBFS on Noble
--
You received this bug notification because you are a member of Ubuntu
Bugs,
*** This bug is a duplicate of bug 1945774 ***
https://bugs.launchpad.net/bugs/1945774
This looks like a duplicate of LP: #1945774 (as also noted in the bug
description), I'm marking it as such. That bug has open (New) Jammy
tasks.
** This bug has been marked a duplicate of bug 1945774
o
The rationale is solid, the MIR was indeed approved by the MIR team and
by security. As stated in in the FFe request, the FFe is only about
moving back libmail-dmarc-perl from Suggests to Recommends.
The FFe is granted.
** Changed in: spamassassin (Ubuntu)
Status: New => Triaged
--
You r
uucp 1.07-29 is a purely bugfix upload which only addresses the armhf
FTBFS, no need for a FFe in this case. This said, thanks for the great
bug report with all the relevant pointers.
I'll proceed with the sync.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
uucp 1.07-29 is now in the unapproved queue.
** Changed in: uucp (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/2061833
Title:
[FFe] FTBFS on armfh - erro
--install-suggests will install more or less everything that may be
needed, but that's normally too much: e.g. you probably don't want lxd
*and* incus. This bug report is an instance of
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034351
and similar to:
https://bugs.debian.org/cgi-bin/
This bug has been filed against the bind9 package, but seems unrelated
to it. For this kind of issues where the affected package/component is
not well identified, I suggest looking for help via the community
support channels:
https://ubuntu.com/support/community-support
** Changed in: bind9 (Ub
I also tried to reproduce the issue, along the lines of what Sergio did,
but I was not able to.
I believe that what we need here is a more complete reproducer, that is
a set of steps that from a clean Ubuntu system lead to the problem (this
is what Mitchell meant with "quick reproducer"). As an ex
sting
Status: New => Fix Committed
** Changed in: auto-package-testing
Assignee: (unassigned) => Paride Legovini (paride)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066290
Title:
For autopkgtest: we have a workaround committed in Debian:
https://salsa.debian.org/ci-
team/autopkgtest/-/commit/32292c7cf7f709554e584cf78dba08db5e134ee7
** Changed in: autopkgtest (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member
I think you are hitting LP: #2046486. Can you please try with
security.nesting=true or lxd from latest/edge? Maybe latest/candidate or
even latest/stable is enough now: a latest comment to LP: #2046486 says
that the fix is "progressively rolled out to the `latest/stable` channel
now", and that was
I'll review this, as I had the occasion to discuss this with mirespace.
@mirespace some high-level questions:
- https://code.launchpad.net/~mirespace/ubuntu/+source/libmail-dmarc-
perl/+git/libmail-dmarc-perl/+merge/464196 basically summarizes all your
work on libmail-dmarc-perl in the context of
Thanks Miriam, considered all the the above, but also more in general
all the thoughtful work done around this MIR, and after doing a high-
level review of the diff, this FFe is granted.
** Changed in: libmail-dmarc-perl (Ubuntu)
Status: New => Triaged
--
You received this bug notificatio
This bug is 10 years old, I doubt the issue is the same of [1] (two
months old).
I'm marking this as Incomplete, but I believe that if [1] affects Ubuntu
then it requires filing a new bug.
[1] https://gitlab.com/qemu-project/qemu/-/issues/2168
** Changed in: qemu (Ubuntu)
Status: Confirme
** Changed in: autopkgtest (Ubuntu)
Status: Fix Committed => 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/2060187
Title:
autopkgtest-build-qemu fails to build Ubuntu images
To m
This also affects src:adduser, which has this delta:
+if ($action eq "adduser") {
+# Mute the command
+system('sh' => ( '-c' => '"$@" >/dev/null 2>&1', '--',
'/usr/sbin/zsysctl', 'userdata', 'create', $new_name, $home_dir,));
+}
causing it to fail in minim
** Changed in: ubuntu-release-notes
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/2063331
Title:
systemd-networkd-wait-online.service runs into a timeout during bo
ppa-purge 0.2.8+bzr63-0ubuntu2 is currently in mantic-proposed,
sponsored by halves. 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/2036761
Title:
[mantic] ppa-purge no
Hello, I am not sure this is ready for sponsorship (I see it's In
Progress), but I had a look at the debdiffs and I have some comments.
1. I see this is going to be a New package for Bionic/Focal/Jammy. Will
this package in the future require backports of new upstream versions to
stable releases b
This is Fix Released in Debian, we need to sync the new package to
Oracular once development opens, and then consider SRUing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061637
Title:
xx-svn-revi
Next steps:
- wait for Oracular to Open
- sync the fixed version from Debian
- evaluate a SRU of the Debian fix, which AIUI is [1].
Note: that's different from the proposed debdiff.
[1] https://salsa.debian.org/php-team/pear/matthiasmullie-
minify/-/commit/0fabfdfb710ccb12cc31eddbc7c541464fcb8a
There are issues with the proposed diff.
1. the d/changelog entry is not descriptive of what the added test does.
Please add something like (you'll know better):
* d/tests: add basic connection test (LP: #)
2. the debdiff adds d/t/a.sh which is unused.
3. d/t/connect: better not specify sh
Marking the bug as Invalid as requested.
** Changed in: tftp-hpa (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/2049283
Title:
package tftpd-hpa 5.2+20150808-1
Hello and thanks for this bug report. I tried reproducing this issue by
1. installing tftpd-hpa on a clean Focal system (LXD container)
2. checking that tftpd-hpa is running fine
3. upgrading to Jammy
4. checking that tftpd-hpa is running fine
The upgrade went fine and the updated tftpd-hpa is fu
@Richard: Timo meant Debian experimental, and indeed in Debian we have:
freeipa-server | 4.9.8-1+exp1 | experimental
Once included in Ubuntu, inclusion of freeipa-server in 22.04 isn't to
be ruled out: it could fall under the "we sometimes want to introduce
new features" case of [1], but I didn'
Thanks Arne for chiming in and for pointing at that patch, which
according to [1] has been tested against Ubuntu 22.04 already.
I was worried about introducing a patch in Ubuntu can possibly downgrade
the OpenVPN security standards, but I see that the same change landed in
the master branch [2], s
Hello Lars and thanks for this bug report. I can confirm this: libmnl-
dev 1.0.4-2 installs
/usr/lib/x86_64-linux-gnu/libmnl.a
while libmnl-dev 1.0.4-3 does not. I tracked this down to this Debian
packaging change (see the debian/libmnl-dev.install diff):
https://salsa.debian.org/pkg-netfilter
Thanks Jeff for filing this bug report. To work on this it would greatly
help to be able to pinpoint which Focal update introduced the problem.
One way to do this is to download one version after the other, install
the packages and test if the bug is present. Something along these
lines:
apt ins
** Changed in: distro-info-data (Ubuntu)
Status: In Progress => 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/1970227
Title:
Add Kinetic to distro-info-data
To manage notificati
** Summary changed:
- 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
+ package mysql-server-8.0 8.0.29-0ubuntu0.20.04.3 failed to install/upgrade:
Error: [Errno 40] T
Hello and thanks for this bug report. In the attached logs I see the
following:
MySQLConf.etc.mysql.my.cnf: Error: [Errno 40] Too many levels of
symbolic links: '/etc/mysql/my.cnf'
This looks like a local configuration problem (circular symlinking),
rather than a bug in Ubuntu.
You can find poin
Hello and thanks for this bug report. In the attached logs I see the
following:
MySQLConf.etc.mysql.my.cnf: Error: [Errno 40] Muitos níveis de links
simbólicos: '/etc/mysql/my.cnf'
This looks like a local configuration problem (circular symlinking),
rather than a bug in Ubuntu.
You can find poin
Hello and thanks for this bug report. In the attached logs I see the
following:
MySQLConf.etc.mysql.my.cnf: Error: [Errno 40] Too many levels of
symbolic links: '/etc/mysql/my.cnf'
This looks like a local configuration problem (circular symlinking),
rather than a bug in Ubuntu.
You can find poin
cloud-utils is not synced or merged from Debian at the moment, and as
far as I can tell the package history is a mix of merges from Debian and
"reverse merges" from Ubuntu to Debian (the primary target of cloud-
utils upstream has been Ubuntu).
So I think this is Invalid, but I'll check if we can
Hello Karoly and thanks for this bug report. auth_socket.so is now
shipped as part of the mysql-server-core-8.0 package:
$ apt-file search auth_socket.so
mysql-server-core-8.0: /usr/lib/mysql/plugin/auth_socket.so
The package is installed as a dependency of mysql-server-8.0. Even if
that's not th
Hello and thanks for this bug report. I tried doing a `do-release-
upgrade -d` from Focal to Jammy, checking that multipathd was healthy in
the first place, before beginning the upgrade. I couldn't reproduce the
issue.
We're willing to investigate this failure case, but what we need are
some steps
Hello Alvaro and thanks for this bug report. We have many systems
running Jammy and they're able to connect to GitHub with no issues. I
also tried with GitLab.com and it works just fine. This is not to
dismiss your report, but there's clearly something else involved in the
problem you're hitting. M
Hello Thomas, I'm marking this as a Wontfix then. Admittedly I didn't
investigate this very deeply, but you did and your verdict looks clear.
If I misinterpreted your words please comment back and change the bug
state back to New. Thanks!
** Changed in: autofs (Ubuntu)
Status: Incomplete =>
Hello Thomas, I am a bit confused by your last comment. You reported
this bug against
DistroRelease: Ubuntu 22.04
Package: autofs 5.1.8-1ubuntu1
but then noted that this is "Solved by a later version of autofs",
however there is no newer version of autofs in Ubuntu. Were you
referring to a ne
Hello Thomas. You filed this bug against:
DistroRelease: Ubuntu 21.10
Package: openssh-server 1:8.4p1-6ubuntu2.1
By "Solved by a later version of systemd and sshd". Do you mean that you
found you can't reproduce the issue on Jammy (22.04 LTS)? Can you still
reproruce the issue on Impish? Than
Hello and thanks for this bug report. I tried to reproduce this locally
but I failed. We're certainly willing to investigate this, but first we
need some steps to reproduce the problem. Could you please try to
identify a somehow reliable way to reproduce the issue and share your
findings? Thanks!
I found a (somehow stale) upstream PR that addresses this:
https://github.com/openssh/openssh-portable/pull/250
We could include this as an Ubuntu patch, but it would be better to
first see it merged upstream. It may be worth pinging there.
** Changed in: openssh (Ubuntu)
Status: New =>
** 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/1966886
Title:
ssh-copy-id and Dropbear Server
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubun
@Felipe sponsoring is certainly something we can do, however before
proceeding with the SRU we need to fix the bug in the current Ubuntu
devel release (kinetic). Ideally this should happen with Debian
packaging 4.4.0 and Ubuntu syncing it, as Lucas mentioned. Filing a bug
in Debian may help. If the
Hello Max, this is your upstream submission, correct?
https://listman.redhat.com/archives/libvir-list/2022-May/231286.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1972075
Title:
Blank screen
Well, "large" can span orders of magnitude, depending who you ask. :-)
Can you please try to identify some steps to reproduce that include the
big file generation? For example:
# 100MB file, random data (difficult to compress)
head -c 100M /dev/urandom > foo
# 100MB file, all 0s (easy to c
Hi peterzay,
It seems likely to me that this is a local configuration problem, rather
than a bug in Ubuntu. If indeed this is a local configuration problem,
you can find pointers to get help for this sort of problem here:
https://ubuntu.com/support/community-support
I'm marking this report as Inc
Hello Barto,
If I understand it correctly you can create working images using 20.04
ISOs *right now*, but with the exact same tooling images created with
20.04.x ISOs do not work. I think you have been clear about this, but it
is of course very important to know that the only moving part is the IS
** 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/1964642
Title:
Packer virtualbox ssh can't connect to unattended Ubuntu 20.04.1/2/3/4
Hello Ian and thanks for this bug report. My question here is: is this
actually a bug?
The manpage for --update says:
This forces rsync to skip any files which exist on the destination
and have a modified time that is newer
It seems sensible to me to make this a '>=' comparison, and not a st
I see your point; my suggestion here is to file a bug upstream with your
findings:
https://github.com/WayneD/rsync/issues
I don't think this should be tackled on the Ubuntu side, especially
given that the issue is really minor and unlikely to affect a
significant amount of users. As you say wha
Jammy ships bs4 4.10.0:
beautifulsoup4 | 4.10.0-2 | jammy | source
so I'm marking the beautifulsoup4 devel task as Fix Released.
** Changed in: lxml
Status: Invalid => Fix Released
** Changed in: beautifulsoup4 (Ubuntu)
Status: Expired => Fix Released
** Project changed:
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
There isn't really enough information here for a developer to confirm
this issue is a bug, or to begin working on it, so I am marking this bug
Incomplete for now.
If you can provide exact steps so that a developer
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
There isn't really enough information here for a developer to confirm
this issue is a bug, or to begin working on it, so I am marking this bug
Incomplete for now.
If you can provide exact steps so that a developer
Thanks Ko-Zu for reporting this bug and sorry if we didn't reply
earlier, it somehow fell under the radar of our bug triage process
I agree with Nick in that this bug and LP: #1965521 are likely to have
the same underlying issue: named is started before networking is ready.
As LP: #1965521 alread
Still no activity in the upstream issue, however I think OpenSSH 8.9
offers a mechanism that can help avoiding hitting MaxAuthTries in some
cases: "destination constraints", see documentation for -h in ssh-
add(1). AIUI constraining should limit the number of keys tried against
a given host, making
Hello Alexander, note that Xorg is available in Jammy both as the native
graphical session and via xwayland. On this bug report: could you please
elaborate more on what exactly happens? In particular could you guide us
into reproducing the problem on a clean Jammy install, making clear
"what should
Public bug reported:
Please backport debhelper (>= 13.6ubuntu1) to Bionic and Focal.
Currently we have
debhelper | 13.5.2ubuntu1~bpo18.04.1| bionic-backports | source, all
debhelper | 13.5.2ubuntu1~bpo20.04.1| focal-backports | source, all
Those versions are affected by LP: #1959054,
** Description changed:
Please backport debhelper (>= 13.6ubuntu1) to Bionic and Focal.
Currently we have
debhelper | 13.5.2ubuntu1~bpo18.04.1| bionic-backports | source, all
debhelper | 13.5.2ubuntu1~bpo20.04.1| focal-backports | source, all
Those versions are affected
Hello Nick and thanks for this bug report. I didn't try to reproduce
your specific issue, however I can see how it can happen. Unfortunately
detecting when network is ready is a tricky thing, as the definition of
"ready" is not fixed and it's very dependent on the specific
configuration of the syst
@teward: Mattia is right, at the moment only the -backports are
affected, as the bug was introduced 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/1965758
Title:
[BPO] debhelper/13.6ubuntu1
@Nick: LP: #1909822 has been reported as fixed in Jammy. Could you
please test if you can still reproduce the issue you described here on a
clean Jammy system? Thanks!
Marking this as Incomplete for now.
** Tags removed: server-triage-discuss
** Changed in: bind9 (Ubuntu)
Status: New => I
Thanks Simon for checking and clarifying! I'm marking the devel task as
Fix Released then, and adding a Confirmed Focal task to reflect your IRC
comment:
paride: I can also confirm that Focal's broken and there,
neither automatic-interface-scan nor interface-interval paper over the
problem... bin
@Nick I'm not convinced by --any, as AIUI we don't want "any" interface,
but "the right one(s)". I'll mark this bug (again) for further
discussion.
** Tags added: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
Public bug reported:
(Spawned from informal discussion at Frankfurt)
Rationale:
- Upstream has very little activity [1];
- Bugs filed against the project are mostly not watched/triaged;
- Bugs filed against the package do get triaged but are never
prioritized, and fixes are normally not SR
** Description changed:
(Spawned from informal discussion at Frankfurt)
Rationale:
- - Upstream has very little activity [1];
- - Bugs filed against the project are mostly not watched/triaged;
- - Bugs filed against the package do get triaged but are never
-prioritized, and fixes
Still happening on Jammy with the following serial (uart) to usb
adapter:
Bus 001 Device 117: ID 0403:6001 Future Technology Devices
International, Ltd FT232 Serial (UART) IC
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass
** Changed in: ubuntu-advantage-tools (Ubuntu Impish)
Status: New => In Progress
** Changed in: ubuntu-advantage-tools (Ubuntu Focal)
Status: New => In Progress
** Changed in: ubuntu-advantage-tools (Ubuntu Bionic)
Status: New => In Progress
** Changed in: ubuntu-advantage-t
Thanks Simon for setting up a reproducer and verifying! @Nick do you
agree with Simon's findings, which basically mean that the error this
bug report is about is mostly a cosmetic thing, as named will retry?
Anyway, we acknowledge that in general "service X starts before network is
ready" is an
Sharing the contents of /usr/sbin/policy-rc.d may also give clues about
its origin. Note however that at this point we have no idea of what its
license is.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
*** This bug is a duplicate of bug 1960454 ***
https://bugs.launchpad.net/bugs/1960454
** This bug has been marked a duplicate of bug 1960454
mysql-server-8.0 8.0.28-0ubuntu0.21.10.3 failed to install/upgrade: Error:
[Errno 40] too many levels of symbolic links
** Summary changed:
- pack
cloud-utils is packaged directly for Ubuntu, no merge needed.
** Changed in: cloud-utils (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/1946849
Title:
Merge cl
What Scarlett means, I think, is that the installed squashfuse binary
*is* the lowlevel one. Newer upstream versions of squashfuse produce two
different binaries: squashfuse and squashfuse_ll, I think following this
commit:
https://github.com/vasi/squashfuse/commit/56a24f6c7f6e5cfd0ce5185f175da223
The fixing commit landed in tmux 3.1a. We have 3.1c in Hirsute and
Impish, so I'm marking the "devel" task as Fix Released.
According to the version numbers Focal is still affected (I didn't
verify with the reproducer), so I'm adding a Focal task to reflect this.
I doubt this bug qualifies for a S
Still a valid bug for Bionic and Focal, updating the other tasks.
** Changed in: rsync (Ubuntu)
Status: New => Fix Released
** Changed in: rsync (Ubuntu Xenial)
Status: Triaged => Won't Fix
** Changed in: rsync (Ubuntu Bionic)
Importance: Undecided => Low
** Changed in: rsync (
** 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/1896251
Title:
rsync --delete-missing-args fails with "error: protocol
incompatibility"
To manage notifications about this
** Changed in: pollinate (Ubuntu)
Assignee: (unassigned) => Paride Legovini (paride)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895714
Title:
Investigate and remove CA pinning
To man
Bionic verification done according to the [Test Plan].
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
@Utkarsh should we make this a duplicate of LP: #1946868? (Andreas
grabbed it!)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944037
Title:
Latest packaged version is a year old with a lot of bug f
Note: upstream merged my PR, so we'll be able to cleanly drop the delta
and make python-mpv a sync.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945332
Title:
autopkgtest regression in python-mpv
The upload to the devel release targeted impish, but actually landed in
jammy. Added an Impish task for the SRU.
** Also affects: samba (Ubuntu Impish)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
** Tags added: needs-merge
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944037
Title:
Latest packaged version is a year old with a lot of bug fixes missing
To manage notifications about this bug
** Changed in: monitoring-plugins (Ubuntu)
Assignee: (unassigned) => Paride Legovini (paride)
** Changed in: monitoring-plugins (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello Bernd and thanks for this bug report. Your are right: check_mysql
is missing from Hirsute but present in Focal and Impish. The Hirsute
build log [1] shows the following at the configure stage:
checking for mysql_init in -lmysqlclient... no
checking for mysql_init in -lmariadbclient... no
wh
** Changed in: monitoring-plugins (Ubuntu Hirsute)
Assignee: (unassigned) => Paride Legovini (paride)
** Changed in: monitoring-plugins (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Changed in: monitoring-plugins (Ubuntu Hirsute)
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/1947141
Title:
monitoring-plugins-standard check_mysql missing
** Changed in: samba (Ubuntu Impish)
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/1942195
Title:
Installing Samba unexpectedly adds many unknown local users to
samba
Verification:
root@paride-h:~# ls -l /usr/lib/nagios/plugins/check_mysql*
-rwxr-xr-x 1 root root 35896 Oct 18 13:22 /usr/lib/nagios/plugins/check_mysql
-rwxr-xr-x 1 root root 31496 Oct 18 13:22
/usr/lib/nagios/plugins/check_mysql_query
root@paride-h:~# /usr/lib/nagios/plugins/check_mysql
Can't c
901 - 1000 of 1596 matches
Mail list logo
