** Changed in: keepalived (Ubuntu Xenial)
Assignee: (unassigned) => Athos Ribeiro (athos-ribeiro)
** Changed in: keepalived (Ubuntu Bionic)
Assignee: (unassigned) => Athos Ribeiro (athos-ribeiro)
** No longer affects: keepalived (Ubuntu Xenial)
** Changed in: keepalived (Ubuntu Focal)
Hi Louis,
I doubt you (or anyone) will still fix it for Xenial.
Feel free to update if that isn't true.
** Changed in: qemu (Ubuntu Xenial)
Assignee: Louis Bouchard (louis) => (unassigned)
** Changed in: qemu (Ubuntu)
Assignee: Louis Bouchard (louis) => (unassigned)
** Changed in:
Hi Scott and Dustin, long time no see :-)
I guess none of you bothers about this being fixed in Xenial anymore, let me
update the assignments and status to reflect that.
** Changed in: ssh-import-id (Ubuntu Xenial)
Status: Triaged => Won't Fix
** Changed in: ssh-import-id (Ubuntu Xenial)
Thanks Athos for flagging this,
you are right if we do not fix it now for Bionic it won't be fixed at all.
But OTOH no one except internal people have revisited this for ages, and being
only cosmetic (the service is up and running fine) this won't make the last
minute (in the release lifecycle)
Thank you all for your reports, but sadly there was no further engagement here.
Andreas and Rafael have asked for more details, config files and such to be
able to recreate this.
Therefore this can not be acted on as is - in addition Xenial is now in
ESM and no more getting normal SRU updates.
Hi,
I come by trying to close or revive some old bugs that were dormant for way too
long.
In regard to smb-v1 / smb-v3.11
In this case Ubuntu Bionic and later (currently on
2:4.7.6+dfsg~ubuntu-0ubuntu2) recognize samba 3.11 (This was referred to in
[1], but was only true for Xenial, anything
Hi,
I'm coming by cleaning old open bugs to ensure nothing gets forgotten for too
long and or clutters the view to the remaining issues.
This case here - as Paride outlined almost two years ago - is already
covered and discussed in bug 1833586 . We won't/can't SRU it and there
was no further
We are - as always - trying to clean and recheck old bugs.
This - sadly - clearly is one of them.
The situation is still correct, but with the full switch to networkd and
netplan as well as the demotion of ifupdown in later versions of Ubuntu this
has become even less important. And it didn#t
Hi,
I'm trying to clear a few old bugs and this sadly never came up again - neither
via prio/people chiming in here nor in other places. Nowadays the server team
has an improved triage process in place which would better catch the hint to
the fix and probably create SRU uploads for this in
Hi,
I come by cleaning up some old bugs and this one is a sad one to see.
It wasn't able to be acted on when I looked at is last time. Then Joseph was so
kind to offer his help, but neither myself nor anyone else in the Team saw
that. Therefore this was not brought back onto anyone's todo-list
While clearing old bugs I found this one and priority for Xenila/Zesty
backports never was important to anyone. Nowadays those are on ESM
support and since there is a workaround (rule overrides) and this isn't
a security issue I'll set Won't Fix for those.
** Changed in: libvirt (Ubuntu Xenial)
** No longer affects: qemu (Ubuntu Bionic)
** No longer affects: novnc (Ubuntu Bionic)
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
** Changed in: docker.io (Ubuntu)
Status: New => Invalid
** Tags removed: server-next
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
Hmm these got updated through -security already.
Missed the bug update due to changelogs.
Setting them to released manually now.
** Changed in: postgresql-10 (Ubuntu Bionic)
Status: Triaged => Fix Released
** Changed in: postgresql-12 (Ubuntu Focal)
Status: Triaged => Fix Released
** Changed in: gdisk (Ubuntu Bionic)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1931243
Title:
This got inot Debian experimental and synced from there
gdisk | 1.0.8-1 | impish | source, amd64,
arm64, armhf, i386, ppc64el, riscv64, s390x
** Changed in: gdisk (Ubuntu Impish)
Status: In Progress => Fix Released
** Changed in: gdisk (Ubuntu Xenial)
Fix in https://sourceforge.net/p/gptfdisk/code/merge-requests/26/
** Bug watch added: Debian Bug tracker #989589
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989589
** Also affects: gdisk (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989589
Importance: Unknown
*** This bug is a duplicate of bug 1883614 ***
https://bugs.launchpad.net/bugs/1883614
Hi Luis,
I can derive from your info in [2] that you are on Xenial, so I'll mark that
for now.
Do you happen to know if it also occurs on other releases?
Two things will commonly be needed to get any
Complete in Hirsute as well
postgresql-13 | 13.2-1 | hirsute | source, amd64, arm64, armhf, i386, ppc64el,
riscv64, s390x
** Changed in: postgresql-13 (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा
This now has a related upstream issue
https://gitlab.com/libvirt/libvirt/-/issues/135
** Bug watch added: gitlab.com/libvirt/libvirt/-/issues #135
https://gitlab.com/libvirt/libvirt/-/issues/135
** Also affects: libvirt via
https://gitlab.com/libvirt/libvirt/-/issues/135
Importance:
** Also affects: libvirt (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: libvirt (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: libvirt (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: libvirt (Ubuntu Groovy)
SRU Template added.
For backport planning I'll add B/F/G since the solution on't help Xenial and
that really is old enough by now to have more people complain about this issue
there to make it super-important.
** Also affects: pollinate (Ubuntu Xenial)
Importance: Undecided
Status:
** Changed in: postgresql-12 (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1892335
Public bug reported:
Hi,
due to this ML on devel-discuss [1] I realized that there is a new version that
should be merged for Ubuntu 21.04 - and probably later [2] be
considered/discussed for an SRU
That new version is in Debian now [3] and I think it would be great to get that
merged/synced.
To close this out, fixed in Groovy
apache2 | 2.4.46-1ubuntu1 | groovy | source, amd64,
arm64, armhf, i386, ppc64el, riscv64, s390x
** Changed in: apache2 (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member
*** This bug is a duplicate of bug 1771630 ***
https://bugs.launchpad.net/bugs/1771630
** This bug has been marked a duplicate of bug 1771630
package mysql-server-5.7 (not installed) failed to install/upgrade:
installed mysql-server-5.7 package post-installation script subprocess returned
Public bug reported:
[Impact]
* MRE for latest stable fixes of Postgres release on August 13th.
[Test Case]
* The Postgres MREs traditionally rely on the large set of autopkgtests
to run for verification. In a PPA those are all already pre-checked to
be good for this upload.
tatus smbd nmbd
while OTOH
systemctl status samba won't show an active service
3. check the config of ctbd in /etc/ctdb/events.d/50.samba
It should refer to smbd and nmbd
** Changed in: samba (Ubuntu Xenial)
Assignee: Karl Stenerud (kstenerud) => Christian Ehrhardt (paelzer
Since so many components are involved a fix/change might have been missed.
And since I recently didn't hear anything about this otherwise rather hot bug I
was giving focal a try.
It turns out that this was indeed improved. Only the user of pkg:ifmail user
fdt name "Fidonet" is still visible.
Hi,
the patches LGTM and I'll make it part of the Ubuntu builds.
One question thou: on one hand "occasionally end up with" sounds like this is
almost impossible to explicitly test, but then the attached debug patch
suggests there might be a way to trigger this through protvirt.
But even if that
** Changed in: openldap (Ubuntu Trusty)
Status: Confirmed => Won't Fix
** Changed in: openldap (Ubuntu Trusty)
Assignee: Sergio Durigan Junior (sergiodj) => (unassigned)
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is
** Changed in: apache2 (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1875299
Title:
Yeah Dan, thanks for chiming in.
In particular that would be at least (but not lmited to) the changes:
8.04
Rework DTLS MTU detection. (#10)
7.08
Support automatic DTLS MTU detection with OpenSSL.
7.07
Automatic DTLS MTU detection.
Ubuntu has these newer versions.
Bionic 18.04 is on 7.08 and the
Since >=7.9.3 is mentioned to be good this seems only to still affect
Xenial.
** Also affects: boinc (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: boinc (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of
Thanks for the report Jeremy,
The fix is in V_7_5_P1 and by that >=Bionic is fixed - I agree to you this only
has to target Xenial.
** Tags added: bitesize server-next
** Also affects: openssh (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: openssh (Ubuntu Xenial)
** Also affects: mysql-8.0 (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: mysql-8.0 (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching
There were several issues with the tool to download unauthenticated data and
such.
So it was removed in 6.4+svn4214-1 which is the one in Xenial and Bionic.
It was later introduced in an improved form in 7.0-1 therefore the
latest LTS release of ubuntu Focal is good.
** Also affects:
Given how low prio/heat this issue had I'm gonna mark the SRU tasks won't fix.
Triaged+Low severity would be correct as well, but that would trigger wrong
expectations as I just see no one get to it.
That way it is clear and if this really is more painful/severe than I
thought people can speak
** Also affects: tinc (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: tinc (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: tinc (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: tinc (Ubuntu Bionic)
Status: New =>
Public bug reported:
[Impact]
* MRE for latest stable fixes of Postgres release on Feb 13th.
[Test Case]
* The Postgres MREs traditionally rely on the large set of autopkgtests
to run for verification. In a PPA those are all already pre-checked to
be good for this upload.
[Regression
$ git show pkg/ubuntu/bionic-devel:lib/Mail/SpamAssassin/DnsResolver.pm | grep
"domain is utf8 flagged"
info("dns: new_dns_packet: domain is utf8 flagged: %s", $domain);
$ git show pkg/ubuntu/eoan-devel:lib/Mail/SpamAssassin/DnsResolver.pm | grep
"domain is utf8 flagged"
info("dns:
Hi Chris,
thanks for your report.
I checked the security Teams overview of those at
- https://people.canonical.com/~ubuntu-security/cve/2018/CVE-2018-11805.html
- https://people.canonical.com/~ubuntu-security/cve/2019/CVE-2019-12420.html
It seems they are still evaluating the options hence the
I just acme by by accident, but wanted to update that this is fixed in
5.3.3-1 which means >=Bionic
** Also affects: lua5.3 (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: lua5.3 (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification
** Changed in: postgresql-11 (Ubuntu)
Status: Triaged => Fix Released
** Changed in: postgresql-11 (Ubuntu Eoan)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching
** Changed in: postgresql-11 (Ubuntu Eoan)
Status: Triaged => Fix Released
** Changed in: postgresql-11 (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching
Yeah he was running on 16.04 which means he was using 1.1.14-2ubuntu1.6
Neither could I reproduce the crashes :-/
But I'm glad to hear that for you it was resolved after using -e
And even more glad that you found newer versions working better for you ´.
I hope this bug helps further users that
TBH - unless someone out there "really" is affected by it I'm
considering "qemu-user-static on aarch64 on LXD on Xenial" too much of a
special case to bother the SRU team with it.
I could keep states as-is, but to reflect that I'd think we should set
it to Won't Fix unless someone speaks up about
Hi Horst,
yes I checked and the issue is in Eoan 2.4.41 - I checked that already last
week and let Steve now.
Steve wanted to track the upstream discussions on this as going forward
we most likely want to follow upstreams guidance on this (e.g. want to
have it broken for better security).
But
This fix is in 5.128-0ubuntu1 in Eoan
** Changed in: byobu (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: byobu (Ubuntu)
Assignee: Paride Legovini (legovini) => (unassigned)
** Tags removed: server-next
** Also affects: byobu (Ubuntu Xenial)
Importance: Undecided
Public bug reported:
[Impact]
* libvirt became FTBFS in xenial due to other changes.
* The fix just modifies the self-tests (not the active code that runs
in an ubuntu users env)
* The change is already active in Ubuntu in later releases via
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Disco)
Status: New => Confirmed
** Changed in: linux (Ubuntu Disco)
Importance: Undecided => High
** No longer affects: linux (Ubuntu Cosmic)
** No longer affects: linux (Ubuntu
*** This bug is a duplicate of bug 1837444 ***
https://bugs.launchpad.net/bugs/1837444
Lucas identified this beign the same as one that he works on.
Marking as duplicate.
** This bug has been marked a duplicate of bug 1837444
pstree seg fault
--
You received this bug notification
** Also affects: psmisc (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: psmisc (Ubuntu)
Status: Triaged => Fix Released
** Changed in: psmisc (Ubuntu Xenial)
Status: New => Triaged
** Changed in: psmisc (Ubuntu Xenial)
Importance: Undecided => Low
--
** Bug watch added: Debian Bug tracker #934277
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934277
** Also affects: openldap (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934277
Importance: Unknown
Status: Unknown
--
You received this bug notification
After discussion decided that it is not a dup, they just share the
symptom to hit at autopkgtest time.
** This bug is no longer a duplicate of bug 1836882
autopkgtest due to other packages changing
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको
** Changed in: chrony (Ubuntu Eoan)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
** Changed in: chrony (Ubuntu Disco)
Status: Won't Fix => Triaged
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to
Cosmic is about to end full support, lets reduce the test matrix a bit
by already dropping the Cosmic task.
@IBM - I'm still waiting on a positive feedback on this sniff test.
Without I can't reliable make it part of the next coming (soon) qemu upload.
Also to be aware once SRUs on this are
Yeah lets focus on 2497b4a3 "s390-bios: Skip bootmap signature entries" here
then.
If ever "IPLing from a dasd attached via vfio-ccw" is wanted that would be an
extra bug/discussion.
Thanks Christian B. for pointing to the core change of this bug!
That way it applies as-is to 3.1, with very
Hi,
this was adressed by upstream in [1]
and by adopted by Debian/Ubuntu in version 2.4.4-1
* Further changes to debian/openvpn@.service copied from upstream
- Enable Restart=on-failure
- Use KillMode=process
which in releases means Bionic and later is already fixed in
This looks like a feature request to me, is there a bug that would make
this SRUable since you added a xenial diff?
Further it is quite some code and due to that more regression risk - so
without a broken use case that will be hard.
I'd ask you to provide a full SRU template [1] before going on
I'm glad that the kernel patch is already integrated by bug 1822870 in
>=Bionic - no dependency on the kernel here then.
The patches themselve look small and clean.
Thanks for identifying the extra dependencies to:
- 8fea7044 (>=3.0) target/ppc: Factor out the parsing in
Hmm, we just don't need the xenial portion.
As already mentioned at the backport the code was way different then.
I can start a VMX defined guest on Xenial:
core2duo
Intel
And it becomes -cpu core2duo,+vmx for qemu commandline.
So Xenial is actually "invalid" as the issue
Setting dev version to fix released per last comment.
** Changed in: resource-agents (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04
Thanks for the clarification Mario!
Now things fit together.
I'll mark the resource agent tasks invalid here per these comments to make sure
no one is confused again.
TL;DR:
- not fixed in postgresql-common
- only fixed in resouce-agent for Xenial/Bionic via SRU in bug 1762492
** Changed in:
so it can "ride along" to eventually help
+Trusty-Mitaka.
** Changed in: libvirt (Ubuntu Xenial)
Status: Fix Released => Triaged
** Changed in: libvirt (Ubuntu Xenial)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
--
You received this bug noti
Currently libvirt tracks these elements to consider refreshing (they are
stored in the capability XMLs themselves).
1558846766
1557980947
400
There are other ctime based caches as well like virQEMUCapsKVMUsable for
/dev/kvm.
The checker for the main caps is virQEMUCapsIsValid and so
novnc 1.1 is in disco and later at least.
** Also affects: novnc (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: novnc (Ubuntu Yakkety)
** Changed in: qemu (Ubuntu Xenial)
Assignee: Christian Ehrhardt (paelzer) => (unassigned)
** Changed in: qemu (Ubu
I verified the proposed change (which is in the opposite diff direction
in the initial report) works in VMs and the PPA fixes the issue.
The fix seems easy enough, so I added MPs for Xenial and Bionic and a
PPA with the builds at [1]
[1]:
Please do -NOT- make a Xenial SRU for that.
As we discussed on IRC and you pointed out in the report yourself - it is not
affected due to systemd doing it right.
This should only be an Upstart related change that goes on top of the
Cloud-Archive-Mitaka Delta.
** Changed in: libvirt (Ubuntu)
Debugging per [1], did not show anything new.
There just is no activity on the actual access of /home all I see is the
trigger for /home registering at startup.
Startup:
ubuntu@xenial-autofs-client:/$ sudo automount -f -v --debug
Starting automounter version 5.1.1, master map /etc/auto.master
Thanks Rbalint for fixing that.
Since a triggering change in qemu is in at least >=Bionic and was reported to
even affect continuous unattended upgrades there would you considering SRUing
your changes as needed?
I added tasks for all releases, but set >=Bionic to high to to that being an
issue
I talked to the security Team (Marc), they said for the SRU our usual
timing is enough as there is a another layer of protection against those
kind of attacks. Therefore the bug will stay open for a while unless
discussed otherwise.
un-assigning the security Team for now, and thanks for the
Reviewing the changelog after talking to Bernd (thanks) I realized that
there are security critical issues in there.
There is a security fix in it "Among others Fix possible security issue with
the permissions of the intermediate staging directory and path"
[1]
But there are some further really
** Changed in: pymacaroons (Ubuntu Xenial)
Status: Triaged => Invalid
** Changed in: pymacaroons (Ubuntu Xenial)
Assignee: Andreas Hasenack (ahasenack) => (unassigned)
** Changed in: pymacaroons (Ubuntu Trusty)
Status: Triaged => In Progress
--
You received this bug
** Also affects: pymacaroons (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: pymacaroons (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: pymacaroons (Ubuntu Trusty)
Status: New => Triaged
** Changed in: pymacaroons (Ubuntu Xenial)
** Also affects: libreoffice (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
Note: I have seen your fixes to the Foundation Cloud for the same
purpose, that was one more use case but that is fixed now as well right?
** Changed in: resource-agents (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: resource-agents (Ubuntu Bionic)
Status: New => Confirmed
Hi Nicolas,
yeah that isn't easy to fix and at least I didn't find the time to develop
something completely new to cover this yet.
I challenge the statement "Even the default storage pool
/var/lib/libvirt/images is not working", it does and it does well.
And for things that are under the
** Changed in: postgresql-11 (Ubuntu Disco)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1815665
After adapting the description for the new insights I uploaded the two
10.7 branches (Bionic/Cosmic) to the unapproved queue as well (9.5 for
Xenial was there already).
** Changed in: postgresql-10 (Ubuntu Cosmic)
Status: Triaged => In Progress
** Changed in: postgresql-10 (Ubuntu Bionic)
Due to the reverts this is much less disruptive, plenty of bug tasks got
invalid.
As 11.2 gets the change postgresql-rum in Disco is affected, but that is
already in 1.3.2-4 which is in Disco.
** Changed in: postgresql-rum (Ubuntu)
Status: New => Fix Released
** Changed in:
@Mario / @Eric - just to check in whoms curt the ball is right now - Is
Mario or someone else in your Org still/again working on this? If not
who do we need to bother to re-assign properly?
** Changed in: resource-agents (Ubuntu Artful)
Status: New => Invalid
--
You received this bug
*** This bug is a duplicate of bug 1817258 ***
https://bugs.launchpad.net/bugs/1817258
Resurrected in bug 1817258 :-)
And released in Disco it seems.
** Changed in: numactl (Ubuntu Disco)
Status: Incomplete => Fix Released
** Changed in: numactl (Ubuntu Cosmic)
Status: Fix
Importance: Undecided
Status: New
** Also affects: python-libnacl (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: python-libnacl (Ubuntu)
Status: Incomplete => Invalid
** Changed in: python-libnacl (Ubuntu Trusty)
Assignee: (unassigned) =>
=> Christian Ehrhardt (paelzer)
** Changed in: libsodium (Ubuntu Xenial)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubun
=> Christian Ehrhardt (paelzer)
** Changed in: pymacaroons (Ubuntu Xenial)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions
The error is due to this change [1]
While we could modify and rebuild postgresql-rum we don't know what else
people might have built against that which is not in the Archive.
This applies only to branches 11 (not yet released, so ok) and 10
(Bionic/Cosmic)
My suggestion would be to carry a
https://codesearch.debian.net/search?q=%5BSs%5D%5BEe%5D%5BTt%5D%5Cs*client_min_messages.*fatal
Not sure how I could search that way in a past release, but it gives some
confirming hits.
For our current case I can confirm the following issues being due to this:
- skytools3 (xenial, not in archive
Done at
https://wiki.ubuntu.com/XenialXerus/ReleaseNotes#CPU_Hotplug_with_QEMU-KVM
By that this issue is resolved.
** Changed in: libvirt (Ubuntu Xenial)
Status: Incomplete => Won't Fix
** Also affects: ubuntu-release-notes
Importance: Undecided
Status: New
** Changed in:
This is actually about two bugs in one and related to bug 1804841
Lets disambiguate them.
One can be avoided by a config in network-manager as mentioned in comment #19
Lets handle this bug here as "that one" - at least in Bionic and later - fixed
by being set by default.
This was initially
Hi Neustradamus,
the initial bug was reported as "Upon upgrading to bionic, amavisd-new DKIM
signing no longer works." so no one thought about former releases.
This also matches that there were no bugs about that issue, prior to Bionic
being released.
Also there is an increased risk the further
To keep potential regressions even lower I'd for now only consider that for
>=Bionic.
That also helps as if someone intentionally spawns an old type KVM machine (pre
Bionic) on a >=Bionic host we don#t have to care about this too much (machine
type, not release runnin IN the guest). That makes
I agree to the case, but not fully to the fix.
The old syscall definitions came in in 2007 via [1] "Update Linux kernel
syscall list" (v0.10.0)
The feature adding the timerfd was added in 2014 with [2] "linux-user: support
timerfd_{create, gettime, settime} syscalls" (v2.2.0) using the wrong
Hi, this 2008 promotion was auto-demoted in Bionic for an upstream
change in Strongswan no more holding it in place. That is fixed in the
recent Bionic upload triggering this old component mismatch again. I'd
ask an AA to re-promote libtspi1 for that in Disco and assigned the AA's
to the Disco
The script would usually call tomcat with:
-Djava.security.policy=="$CATALINA_BASE"/work/catalina.policy
The dir here by the suggested sed is replaced by
work -> policy
Many other things are referenced based on "$CATALINA_BASE/..." and they
are all in "/var/lib/tomcat7/...".
So is the
** Changed in: samba (Ubuntu Trusty)
Status: Fix Committed => Invalid
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1792400
Title:
Yes this change (the Debian version of it, not yours) is in since 3.3.1-3
Thanks a lot Mark! for the ping on this forgotten bug also for the
documentation of the config in regard to BackupZeroFilesIsFatal if previously
set to 1.
(And also thanks for your upstreaming work on this)
** Also
So to summarize:
- per latest IBM comment the version in 18.10 2.0.11-2.1 works
- This is also the version in 18.04, so that works as well
- But the referred fix (pointed out in comment #13 that is actually supposed in
Upstream version
2.12) is NOT in any of those package versions
I'm marking
** Also affects: samba (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: samba (Ubuntu Trusty)
Status: New => Triaged
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching
This is "just one more" case of the common old init scripts didn't
consider there could be more (=containers).
Interesting is that the stop already runs with the --pidfile so the stop
will not kill it.
But the start will be blocked, as the existance of such a process will
make --start be a
1 - 100 of 130 matches
Mail list logo
