Removed pyrenamer ghextris and xtile as they look to have been removed
earlier. Refreshed reverse-depends.
** No longer affects: ghextris (Ubuntu)
** No longer affects: pyrenamer (Ubuntu)
** No longer affects: x-tile (Ubuntu)
** Description changed:
gnome-python and pyorbit have been removed
** No longer affects: labyrinth (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1739800
Title:
Please remove gnome-python from Ubuntu
To manage notifications about this bug go to:
https://bu
I can confirm this is still an issue on 18.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651250
Title:
If you choose btrfs it still creates a swapfile even though it can't
use it
To manage n
And it's now provided by Ubuntu and Debian!
..it mostly just points back to the init.d script, but that does lay the
groundwork and prevent it from having to be generated.
Any future improvements I figure should be done in the gitlab (/closes
bug).
** Changed in: apparmor
Status: New => F
Gave different error in test in Bionic LXD container. Removed from
package archive - now only available as a snap.
** Changed in: charm-tools (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
** Changed in: landscape-client
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/1577850
Title:
Port to Python 3
To manage notifications about this bug go
@Andy Whitcroft (apw), just want to confirm that this doesn't need to be
tracked further. Everything seems to work fine in Bionic. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747507
Title:
Public bug reported:
I can't tell if the script - update-boinc-applinks is still
useful/needed. Per the man page it was written only for Debian BOINC.
AFAICT today it checks for this directory: /usr/share/boinc-apps/info/,
which doesn't exist when boinc is installed, and then exits.
>From what
Afaict this should be targeting mailman3 (not sure what happened to
package mailman3-core).
The mailman (2) packages has been marked as legacy and only supports
python2.
Looking at deps for apt install mailman3 --no-install-recommends I do
find the majority of packages not in main for bionic thou
** Also affects: mailman3 (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/1735372
Title:
mailman/mailman3: Please drop dependency on Python2 (demot
This is longer true with 217 and higher, as systemd implementation has been
removed.
* systemd's readahead implementation has been removed. In many
circumstances it didn't give expected benefits even for
rotational disk drives and was becoming less relevant in the
Sorry, what needs fixing is over my head. Btw, You're the most
responsive non-maintainer ever :).
What are your thoughts on if it should stay in the Ubuntu archive? (If
not new maintainer comes along, etc)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Public bug reported:
It's only in Ubuntu.
Upstream hasn't made a release since 2012, no one is maintaining it -
https://github.com/labyrinth-team/labyrinth
Reviews show people have lost data by using it.
It uses outdated tech that we hope to remove gnome-python -
https://bugs.launchpad.net/ubun
This was fixed at some point. There still is a blocker for snap apps
to actually run though -
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1751667
** Changed in: snapd (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ub
*Fixed in Bionic* (didn't retest other releases)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576378
Title:
Snap installing doesn't work in live session
To manage notifications about this bug go
Thank you for reporting this bug for Ubuntu, sorry that we weren't able
to provide a proper fix.
This package has been removed from the Ubuntu development release and
upstream development appears to have stopped.
** Changed in: aptoncd (Ubuntu)
Status: New => Won't Fix
--
You received th
Thank you for reporting this bug for Ubuntu, sorry that we weren't able
to provide a proper fix.
This package has been removed from the Ubuntu development release and
upstream development appears to have stopped.
** Changed in: aptoncd (Ubuntu)
Status: New => Won't Fix
--
You received th
Thank you for reporting this bug for Ubuntu, sorry that we weren't able
to provide a proper fix.
This package has been removed from the Ubuntu development release.
** Changed in: aptoncd (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a memb
** No longer affects: aptoncd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740618
Title:
Remove unmaintained gksu reverse dependencies
To manage notifications about this bug go to:
https
Thank you for reporting this bug, sorry that we weren't able to provide
a proper fix.
This package has been removed from the Ubuntu development release and
upstream development has not been active in many years.
** Changed in: glipper (Ubuntu)
Status: Confirmed => Won't Fix
--
You receiv
Thank you for reporting this bug, sorry that we weren't able to provide
a proper fix.
This package has been removed from the Ubuntu development release and
upstream development has not been active in many years.
** Changed in: glipper (Ubuntu)
Status: New => Won't Fix
--
You received thi
Thank you for reporting this bug for Ubuntu, sorry that we weren't able
to provide a proper fix.
This package has been removed from the Ubuntu development release.
** Changed in: glipper (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of U
Thank you for reporting this bug for Ubuntu, sorry that we weren't able
to provide a proper fix.
This package has been removed from the Ubuntu development release and
upstream development appears to have stopped.
** Changed in: aptoncd (Ubuntu)
Status: Confirmed => Won't Fix
--
You recei
Thank you for reporting this bug for Ubuntu, sorry that we weren't able
to provide a proper fix.
This package has been removed from the Ubuntu development release.
** Changed in: glipper (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a membe
Thank you for reporting this bug for Ubuntu, sorry that we weren't able
to provide a proper fix.
This package has been removed from the Ubuntu development release and
upstream development appears to have stopped.
** Changed in: glipper (Ubuntu)
Status: New => Won't Fix
--
You received th
Thank you for reporting this bug for Ubuntu, sorry that we weren't able
to provide a proper fix.
This package has been removed from the Ubuntu development release.
** Changed in: glipper (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member
Thank you for reporting this bug for Ubuntu, sorry that we weren't able
to provide a proper fix.
This package has been removed from the Ubuntu development release.
** Changed in: glipper (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of U
Thank you for reporting this bug for Ubuntu, sorry that we weren't able
to provide a proper fix.
This package has been removed from the Ubuntu development release and
upstream development appears to have stopped.
** Changed in: glipper (Ubuntu)
Status: New => Won't Fix
--
You received t
Thank you for reporting this bug for Ubuntu, sorry that we weren't able
to provide a proper fix.
This package has been removed from the Ubuntu development release and
upstream development appears to have stopped.
** Changed in: aptoncd (Ubuntu)
Status: Confirmed => Won't Fix
--
You recei
Thank you for reporting this bug for Ubuntu, sorry that we weren't able
to provide a proper fix.
This package has been removed from the Ubuntu development release.
** Changed in: glipper (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of U
Thank you for reporting this bug for Ubuntu, sorry that we weren't able
to provide a proper fix.
This package has been removed from the Ubuntu development release.
** Changed in: glipper (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of U
Thank you for reporting this bug for Ubuntu, sorry that we weren't able
to provide a proper fix.
This package has been removed from the Ubuntu development release.
** Changed in: glipper (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a membe
Thank you for reporting this bug for Ubuntu, sorry that we weren't able
to provide a proper fix.
This package has been removed from the Ubuntu development release.
** Changed in: glipper (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a memb
Thank you for reporting this bug for Ubuntu, sorry that we weren't able
to provide a proper fix.
This package has been removed from the Ubuntu development release and
upstream development appears to have stopped.
** Changed in: aptoncd (Ubuntu)
Status: New => Won't Fix
--
You received th
Thank you for reporting this bug for Ubuntu, sorry that we weren't able
to provide a proper fix.
This package has been removed from the Ubuntu development release and
upstream development appears to have stopped.
** Changed in: aptoncd (Ubuntu)
Status: New => Won't Fix
--
You received th
Thank you for reporting this bug, sorry that we weren't able to provide
a proper fix.
This package has been removed from the Ubuntu development release and
upstream development has not been active in many years.
** Changed in: glipper (Ubuntu)
Status: New => Won't Fix
--
You received thi
Thank you for reporting this bug for Ubuntu, sorry that we weren't able
to provide a proper fix.
This package has been removed from the Ubuntu development release.
** Changed in: glipper (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a membe
Thank you for reporting this bug for Ubuntu, sorry that we weren't able
to provide a proper fix.
This package has been removed from the Ubuntu development release and
upstream development appears to have stopped.
** Changed in: glipper (Ubuntu)
Status: New => Won't Fix
--
You received th
Thank you for reporting this bug, sorry that we weren't able to provide
a proper fix.
This package has been removed from the Ubuntu development release and
upstream development has not been active in many years.
** Changed in: glipper (Ubuntu)
Status: Confirmed => Won't Fix
--
You receiv
Thank you for reporting this bug for Ubuntu, sorry that we weren't able
to provide a proper fix.
This package has been removed from the Ubuntu development release and
upstream development appears to have stopped.
** Changed in: glipper (Ubuntu)
Status: New => Won't Fix
--
You received th
Thank you for reporting this bug, sorry that we weren't able to provide
a proper fix.
This package has been removed from the Ubuntu development release.
** Changed in: gnome-btdownload (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of
Thank you for reporting this bug, sorry that we weren't able to provide
a proper fix.
This package has been removed from the Ubuntu development release and
upstream development has not been active in many years.
** Changed in: gnome-blog (Ubuntu)
Status: Incomplete => Invalid
--
You rece
Thank you for reporting this bug, sorry that we weren't able to provide
a proper fix.
This package has been removed from the Ubuntu development release and
upstream development has not been active in many years.
** Changed in: gnome-blog (Ubuntu)
Status: Confirmed => Invalid
--
You recei
Thank you for reporting this bug, sorry that we weren't able to provide
a proper fix.
This package has been removed from the Ubuntu development release and
upstream development has not been active in many years.
** Changed in: gnome-blog (Ubuntu)
Status: Confirmed => Invalid
--
You recei
Thank you for reporting this bug, sorry that we weren't able to provide
a proper fix.
This package has been removed from the Ubuntu development release and
upstream development has not been active in many years.
** Changed in: gnome-blog (Ubuntu)
Status: New => Won't Fix
--
You received
Thank you for reporting this bug, sorry that we weren't able to provide
a proper fix.
This package has been removed from the Ubuntu development release and
upstream development has not been active in many years.
** Changed in: gnome-blog (Ubuntu)
Status: New => Won't Fix
--
You received
Thank you for reporting this bug, sorry that we weren't able to provide
a proper fix.
This package has been removed from the Ubuntu development release and
upstream development has not been active in many years.
** Changed in: gnome-blog (Ubuntu)
Status: Triaged => Invalid
--
You receive
** Changed in: gnome-blog (Ubuntu)
Status: Confirmed => 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/272034
Title:
posting blocked
To manage notifications about this bug go to:
Thank you for reporting this bug, sorry that we weren't able to provide
a proper fix.
This package has been removed from the Ubuntu development release and
upstream development has not been active in many years.
** Changed in: gnome-blog (Ubuntu)
Status: New => Invalid
--
You received th
Thank you for reporting this bug, sorry that we weren't able to provide
a proper fix.
This package has been removed from the Ubuntu development release and
upstream development has not been active in many years.
** Changed in: gnome-blog (Ubuntu)
Status: New => Won't Fix
--
You received
Thank you for reporting this bug, sorry that we weren't able to provide
a proper fix.
This package has been removed from the Ubuntu development release and
upstream development has not been active in many years.
** Changed in: gnome-blog (Ubuntu)
Status: New => Invalid
--
You received th
Thank you for reporting this bug, sorry that we weren't able to provide
a proper fix.
This package has been removed from the Ubuntu development release and
upstream development has not been active in many years.
** Changed in: gnome-blog (Ubuntu)
Status: New => Won't Fix
--
You received
Thank you for reporting this bug, sorry that we weren't able to provide
a proper fix.
This package has been removed from the Ubuntu development release.
** Changed in: specto (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs
Thank you for reporting this bug, sorry that we weren't able to provide
a proper fix.
This package has been removed from the Ubuntu development release.
** Changed in: specto (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Thank you for reporting this bug, sorry that we weren't able to provide
a proper fix.
This package has been removed from the Ubuntu development release.
** Changed in: specto (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs
Public bug reported:
The new version has a fix for Ansible >= 2.4.0, which I'm guessing may
be related to why it's failing with that new version trying to land.
Broken autopkgtests: http://people.canonical.com/~ubuntu-archive
/proposed-migration/update_excuses.html#ansible
Upstream Changelog - h
"The performance impact on disk throughput should not be significant..."
Understood, thanks! I just didn't see that mentioned in the SRU.
Re:dedup: I prefer the dropping rsyslog, but none of those are feasible
for existing releases, right?
What are the journal limits on Ubuntu by default?
--
Y
Here's the changes for the test. Confirmed test using local autopkgtest
to the source package.
** Patch added: "network-manager_1.10.4-1ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1734586/+attachment/5061319/+files/network-manager_1.10.4-1ubuntu2.debdiff
-
@markstos
Sorry, yea, I meant our defaults, not the journal config options itself.
SystemMaxUse= is unset in the config in bionic (although it's all commented
out, but I believe that's supposed to indicate our defaults?)
Re:disk writing. I don't disagree, but if we are SRUing it we need to
cons
@xnox
"The journald daemon has limits set for logs, meaning they will be rotated and
discarded and should not cause out of disk-space errors."
What are they? AFAICT it only has limits on the number of files, but
not how big they can overall become.
I'm also thinking that the duplicate writing
This is fixed with Linux desktop 4.13.0-35-generic #39-Ubuntu SMP Mon
Feb 12 11:06:39 UTC 2018
** Tags removed: verification-needed-artful
** Tags added: verification-done-artful
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
Python-dbusmock upstream - https://github.com/martinpitt/python-
dbusmock/issues/37
Although I don't think we should delay network-manager because of it..
** Bug watch added: github.com/martinpitt/python-dbusmock/issues #37
https://github.com/martinpitt/python-dbusmock/issues/37
--
You recei
Autopkgtets, The urfkill-intergration is failing because if you start
network-manager first, it clears the rfkill flags.
I think it should be safe to assume network-manager should start before
urfkill - in that case removing the last network-manager stop (and the
resulting start one) and I think w
The senddoc profile is wrong like the other one was too -
profile libreoffice-senddoc
/usr/lib/libreoffice//usr/lib{,32,64}/libreoffice/program/senddoc {
#include
It still seems like the profile is missing xdg-email, which might be
needed too.
--
You received this bug notification because y
This works at least in 17.10 and I believe in 16.04, but it wasn't a
nautilus fix so closing as invalid. Thanks!
** Changed in: nautilus (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
This bug appears fixed with that kernel, thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747507
Title:
starting VMs causing retpoline4 to reboot
To manage notifications about this bug go to:
Tried disabling some BIOS settings including trusted computing and
hyperthreading which didn't have any effect.
Tried getting more info with linux-crashdump but it doesn't seem to work.
I am currently running with no kvm issues with mainline v4.15.1 and Full AMD
retpoline.
--
You received this
Might be related, might not. This is displayed before the reboot.
host doesn't support requested feature: CPUID.01H:ECX.vmx [bit 5]
I did downgrade from the testing qemu packages, maybe that changed my
VMs, but that still shouldn't cause a host reboot (or kvm with no
options).
** Attachment add
** Description changed:
Using 4.13.0-33.36~retpoline4 kernel test kernel from ppa
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/spectre/.
CPU: AMD Ryzen 7 1700 Eight-Core Processor
Ubuntu: 17.10.
Steps to reproduce (has occurred both times I tried it):
- 1. Run virs
Public bug reported:
Using 4.13.0-33.36~retpoline4 kernel test kernel from ppa
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/spectre/.
CPU: AMD Ryzen 7 1700 Eight-Core Processor
Ubuntu: 17.10.
Steps to reproduce (has occurred both times I tried it):
1. Run virsh start (or start
Thank you for reporting this bug to Ubuntu. We're sorry we don't always
have time to fully triage and fix bugs.
Glad you were able to resolve this! With the change to gnome-shell in
newer releases I'm guessing this is no longer relevant.
** Changed in: nautilus (Ubuntu)
Status: New => Inv
Thank you for reporting this bug to Ubuntu. We're sorry we don't always
have to full triage and fix bugs.
I don't believe this bug applies to currently supported Ubuntu releases
(with major new releases of nvidia driver and nautilus) so I'm going to
close it. Please feel free to reopen if you sti
Per Stefan's comment this looks likely to be fixed in a newer release.
Please reopen if you are still affected by it. Thanks!
** Changed in: apache2 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
I think it makes sense to just remove supported-sysadmin-desktop and not
add this back 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/1738046
Title:
Demote from main / thoughts on removing?
Did an in-depth on Xenial comparing new and old sosreport output and
didn't find anything amiss.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1734983
Title:
Request to backport sosreport v3.5
To m
@Vincent Looks like with Breezy, we should reconsider dropping Bazaar
for 18.04? Thoughts?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1577847
Title:
Demote Bazaar to universe?
To manage notifi
This was partially done. unfortunately the profiles are all missing a /
/usr/lib/libreofficeprogram/soffice.bin
should be
/usr/lib/libreoffice/program/soffice.bin
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
Thanks Dimitri!
I see that this bug has open tasks for Xenial, Zesty and Artful- my
understanding it this would not be a change we would backport. Am I
wrong about that?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
Closing as unsupported release and theoretically shouldn't happen again.
Thanks!
** Changed in: mozilla-devscripts (Ubuntu)
Status: Triaged => Fix Released
** Changed in: mozilla-devscripts (Ubuntu Precise)
Status: Triaged => Fix Released
--
You received this bug notification beca
Is the Thunderbird proposed being tracked somewhere? I'm +1 disabling
Flash in thunderbird.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1585903
Title:
Make it possible to remove gtk2
To manage n
- meant custom services.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1738062
Title:
xinetd still needed in main?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+s
@elmo
Very true, but in the tftp case tftpd-hpa does exist and is in main. No
packages in main depend on xinetd, my best guess is maybe it was used for
customer services back in the day?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
Added Colin and Jeff so they can give feedback. Worth keeping this? (In
main?)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1738046
Title:
Demote from main / thoughts on removing?
To manage notif
Public bug reported:
Reviewing supported-sysadmin-common [1] I noticed that xinetd was added
before 2008 and may no longer be necessary with our switch to systemd.
None of it's reverse dependencies are in main.
$ reverse-depends src:xinetd
Reverse-Depends
===
* fex
@elmo
The changelog says this was added for you in Hoglet, which I'm guessing is very
much no longer needed for that purpose. Any other reason from you not to
demote from main? Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
It might be worth considering demoting the package - added a bug for that,
looking for feedback
before I make it an official request.
https://bugs.launchpad.net/ubuntu/+source/system-config-kickstart/+bug/1738046
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
It might be worth considering demoting the package - added a bug for that,
looking for feedback
before I make it an official request.
https://bugs.launchpad.net/ubuntu/+source/system-config-kickstart/+bug/1738046
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Public bug reported:
Rationale:
This package is uninstallable in Fedora 27 (which used to be the active
upstream) - https://bugzilla.redhat.com/show_bug.cgi?id=1406598.
dnf install system-config-kickstart
Last metadata expiration check: 2:21:06 ago on Wed Dec 13 14:34:27 2017.
Error:
Problem:
Oh, additionally this is an Ubuntu specific package and not in Debian.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1738046
Title:
Demote from main / thoughts on removing?
To manage notifications
I got feedback to go with ibus-libpinying from asking in some Chinese
IRC channels (hardly a scientific methodology..)
I was originally looking at lib-pinying - but they said ibus-libpinying
was better. (And it also seems to be much better maintained)
--
You received this bug notification becaus
Switching to ibus-libpinyin seems like the better option, see Comments
in bug https://bugs.launchpad.net/ubuntu/+source/ibus-
sunpinyin/+bug/1735362 for details.
Unlike with the other bug (and the related Debian bugs - still needs a
port to python3), ibus-libpinyin is already ported to gtk3.
--
This appears to have actually been fixed (artful+), plymouth was moved to a
recommends [1] for cryptsetup (although the changelog doesn't seem to say that).
Mountall is no longer included in artful+ with the switch to systemd.
[1] https://packages.ubuntu.com/artful/cryptsetup
** Changed in: cryp
@doko I just opened a bug on it, because ibus-libpinyin still seems to
be built with python2 - https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=883631
@seb128 there was some discussion on the ML -
https://lists.ubuntu.com/archives/ubuntu-
desktop/2017-November/005286.html and I got some feedback
Thanks Norvald's for the great analysis. We're not going to be able to
change the build options for already released versions of MySQL. The
docs indicate that using the --ssl-ca is the recommended option for this
case.
If you want to get the build options changes for the next release 18.04
- I'd
(Would also be possible to retarget this bug to 5.7)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1076656
Title:
mysql --ssl-capath option doesn't work
To manage notifications about this bug go to
** Changed in: dash (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/675185
Title:
[Hardy SRU] dash bug causes mysqld_safe to spin at 100% CPU
To manage notifica
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner.
This bug is for a very old release and as a packaging bug it will not
affect a newer release in the same way.
** Changed in: mysql-5.5 (Ubuntu)
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner.
This bug is for an old release and as a packaging bug it will not affect
a newer release in the same way.
** Changed in: mysql-5.5 (Ubuntu)
Stat
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner.
This bug is for a old release and as a packaging bug it will not affect
a newer release in the same way.
** Changed in: mysql-5.5 (Ubuntu)
Statu
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner.
This bug is for an old release and as a packaging bug it will not affect
a newer release in the same way.
** Changed in: mysql-5.5 (Ubuntu)
Sta
201 - 300 of 2966 matches
Mail list logo
