If I understand the keepalived > 2.0.x behavior referred to by cdmiller
above (see 2019-03-07 comment) that is not the appropriate response to
the problem. Granted, it mitigates the consequences butr doesn't
address the underlying issue. A systemd-source issue should not cause
keepalived failover
Cool, I will try that!
As a heads up though, this sound quality is only after uninstalling and
reinstalling pulse audio and maybe something else (apologies for not
giving better details there, I didn't think to submit a bug until I ran
out of things to try). Before I did that, a voice recorded by
** Changed in: pulseaudio
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1583801
Title:
No sound via headphones (headset) when Ubuntu
Please update https://help.ubuntu.com/community/UbuntuTime under "Using
the Command Line (unattended)" with the new behavior.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
The attached file AudioDevicesInUse.txt suggests that 'audacity' is
stealing the hardware device from pulseaudio -- bypassing it.
If that is the issue then it's unfortunately not a bug. You need to be
sure that all audio software (including audacity) is configured to use
PulseAudio only, and not
I'm a little confused here. What does audacity have to do with the fact
that there is no sound after a reboot? Audacity happens to be running
now...perhaps that's why it's the only program using ALSA. (Is ALSA
deprecated?) But audacity does not start automatically at boot, so it
is irrelevant
It appears 'audacity' is the exclusive user of /dev/snd/seq according to
your AudioDevicesInUse.txt.
Please try:
1. Reconfiguring Audacity to use PulseAudio and not ALSA or OSS.
2. Uninstalling 'audacity'.
** Summary changed:
- [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
+
** Changed in: debian
Status: Unknown => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1822590
Title:
Found storing user fingerprints without
** Bug watch added: PulseAudio #193
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/193
** Changed in: pulseaudio
Importance: Medium => Unknown
** Changed in: pulseaudio
Remote watch: freedesktop.org Bugzilla #106834 => PulseAudio #193
--
You received this bug notification
Public bug reported:
After rebooting I have no sound. My sound device doesn't show up at all
in the mixer.
Running "sudo alsa force-reload" corrects the problem, until the next
reboot.
This problem started in 18.10 and persists now in 19.04.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
*** This bug is a duplicate of bug 1583801 ***
https://bugs.launchpad.net/bugs/1583801
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1583801, so it is being marked as such. Please
Hi all, could the package maintainer(s) please take a look at this?
This breaks (almost) any WireGuard endpoint configured by systemd-
networkd. Worse, it breaks them silently, which makes for a fun
debugging adventure.
The fixed patch (https://github.com/systemd/systemd-stable/pull/39) has
been
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Changed in: ibus
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1580463
Title:
Snap blocks access to system input methods (ibus, fcitx,
This bug was fixed in the package netplan.io - 0.96-0ubuntu0.18.10.3
---
netplan.io (0.96-0ubuntu0.18.10.3) cosmic; urgency=medium
* debian/patches/git_revert_explicit_renderer_def_ebc212a.patch: revert
commit ebc212a: make renderer values explicit at the end of each parsing
This bug was fixed in the package netplan.io - 0.96-0ubuntu0.18.04.4
---
netplan.io (0.96-0ubuntu0.18.04.4) bionic; urgency=medium
* debian/patches/git_revert_explicit_renderer_def_ebc212a.patch: revert
commit ebc212a: make renderer values explicit at the end of each parsing
This bug was fixed in the package netplan.io - 0.96-0ubuntu0.18.04.4
---
netplan.io (0.96-0ubuntu0.18.04.4) bionic; urgency=medium
* debian/patches/git_revert_explicit_renderer_def_ebc212a.patch: revert
commit ebc212a: make renderer values explicit at the end of each parsing
This bug was fixed in the package netplan.io - 0.96-0ubuntu0.18.10.3
---
netplan.io (0.96-0ubuntu0.18.10.3) cosmic; urgency=medium
* debian/patches/git_revert_explicit_renderer_def_ebc212a.patch: revert
commit ebc212a: make renderer values explicit at the end of each parsing
reverse-depends src:libgnome-keyring -b
Reverse-Build-Depends
=
* chromium-browser (for libgnome-keyring-dev)
* libgnomeui(for libgnome-keyring-dev)
$
So we might want to deal with chromium first...?
** Changed in: libgnome-keyring (Ubuntu)
Removing packages from eoan:
libgnomeui 2.24.5-3.2 in eoan
libgnomeui-0 2.24.5-3.2 in eoan amd64
libgnomeui-0 2.24.5-3.2 in eoan arm64
libgnomeui-0 2.24.5-3.2 in eoan armhf
libgnomeui-0 2.24.5-3.2 in eoan i386
Removing packages from eoan:
linsmith 0.99.31-1 in eoan
linsmith 0.99.31-1 in eoan amd64
linsmith 0.99.31-1 in eoan arm64
linsmith 0.99.31-1 in eoan armhf
linsmith 0.99.31-1 in eoan i386
linsmith 0.99.31-1 in
This bug was fixed in the package libselinux - 2.9-1
---
libselinux (2.9-1) experimental; urgency=medium
[ Laurent Bigonville ]
* New upstream release
- Bump libsepol1-dev build-dependency to >= 2.9 to match the release
* debian/ruby.mk: Do not override RUBYLIBS anymore,
This bug was fixed in the package ubuntu-settings - 19.04.4
---
ubuntu-settings (19.04.4) eoan; urgency=medium
* ubuntu-settings.gsettings-override:
- set the document font to 'Sans 11' for Ubuntu, the GNOME default
changed to Cantarell which is not installed for us (lp:
regression fixed in 1.10.0-1~ubuntu18.04.2
however please note now that ModemManager is started by default with
filter-policy=strict in order for MM to see Bluetooth modems you need a
udev rule like such:
ACTION!="add|change|move", GOTO="mm_whitelist_internal_modem_end"
#ACTION=="add",
Thanks Adam, indeed that's due to GNOME changing to cantarell in 3.31, fixed
now in
https://launchpad.net/ubuntu/+source/ubuntu-settings/19.04.4
SRU uploaded as well
** Package changed: gnome-settings-daemon (Ubuntu) => gsettings-desktop-
schemas (Ubuntu)
** Changed in:
Public bug reported:
* Impact
The document font changed in GNOME 3.31 to be 'Cantarell 11' but that
font is not installed in Ubuntu so a fallback font is used instead.
* Test case
Install gnome-tweaks and look at the document font, it should be 'Sans 11' and
not 'undefined'
* Regression
You have been subscribed to a public bug:
On Ubuntu 19.04 (Disco), the default Document Text font after
installation is None. You can see this if you run gnome-tweaks and
select Fonts in the left sidebar.
As one consequence of this, messages in Geary are displayed in a serif
font by default,
Alex Tu, please test the new packages in bionic-proposed whether they
correctly support the modems for which you asked for support for.
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to modemmanager in Ubuntu.
yparitcher, first, thanks for reporting bug 1828102, we need this
separate bug as Cosmic and Disco originally came with ModemManager 1.10
and so did not suffer the bug treated here, only the regression which
you have found. Eoan I have already treated here as the SRU team
requires that the issues
** Also affects: modemmanager (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: modemmanager (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: modemmanager (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Changed in: modemmanager
I think it's a bug, because all laptops I've ever seen show "fully
charged" instead of "not charging" when they hit 100% of the battery.
And there's some other strange behavior, like the Gnome indicator
eventually being stuck at "Estimating" and, sometimes, if you disconnect
the power plug while
added bug for cosmic & disco
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1828102
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to modemmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1819615
Title:
For
** Tags added: sts-sponsor-ddstreet
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to debconf in Ubuntu.
https://bugs.launchpad.net/bugs/1822270
Title:
Debconf readline frontend does not show options
Status in debconf
Public bug reported:
ModemManager disconnects after ~30 sec
caused by a typo in 1.8
see https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1819615
and
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/119
for details
needs a SRU for cosmic and dingo
patch attached
Incidentally, there's nothing for the AppArmor project to do here -- any
confined program will include or not include the fingerprint data as
specified in the profile.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
I'll include as a comment my reply to an email from the reporter:
Hello,
Note that the Ubuntu security team considers fingerprints to be akin to
usernames, rather than passwords. They cannot be changed, they are left on
thousands of objects daily, and repeated demonstrations of sensors being
I was on Bionic Beaver and my '.desktop' Desktop Entry files were
working but after an upgrade to Disco Dingo they just launch gedit.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
The plymouth package hook is using apport's
"attach_root_command_outputs" function that same function is also used
by the following package hooks: lightdm, shim-signed, ubuntu-release-
upgrader, update-manager, synaptic, upgrade-system and all the xorg
hooks. So it may be worth working around this
Hello Till, or anyone else affected,
Accepted modemmanager into bionic-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/modemmanager/1.10.0-1~ubuntu18.04.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new
I got how to reproduce.
Cached memory grows big by reading many files and free RAM becomes empty.
In this situation (repeat release and allocate caches frequently), drawing
process faces this problem.
Does conflict of memory cause this problem?
--
You received this bug notification because
I realized immediately after submission that this should instead be a
question, before being escalated to the status of "bug". Just curious
why 16.04 doesn't have this fix yet.
** Changed in: mime-support (Ubuntu)
Status: New => Invalid
** Converted to question:
Public bug reported:
I am using 16.04 xenial, which the mime-support package 3.59.
The run-mailcap script in the mime-support package contains an unescaped
left brace in the regex statement on line 528.
To be exact, the line that currently reads:
$comm =~
** Bug watch added: Debian Bug tracker #926749
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926749
** Also affects: apparmor (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926749
Importance: Unknown
Status: Unknown
** No longer affects: apparmor (Debian)
**
This bug was fixed in the package modemmanager - 1.10.0-1ubuntu1
---
modemmanager (1.10.0-1ubuntu1) eoan; urgency=medium
* debian/patches/error-propagation-fix.patch: mm-broadband-modem: Fix error
propagation in CDMA service status (LP: #1819615, Upstream Issue #119).
-- Till
In regression potential, in the connectivity section, added more info
about "non-application data records" issues that may cause main-loop
hangs.
** Description changed:
[Impact]
* OpenSSL 1.1.1 is an LTS release upstream, which will continue to
receive security support for much longer
Reopening/Assigning to TImo for eoan since there is a patch which can we
dropped once qemu is fixed
** Changed in: mesa (Ubuntu Eoan)
Status: Fix Released => Triaged
** Changed in: mesa (Ubuntu Eoan)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
--
You received this bug
We reviewed it in the team meeting, while it would be nice to fix we
don't believe it's an usecase common/important enough to justify team
assignment & tracking, tagging rls-ee-notfixing
** Tags removed: rls-ee-incoming
** Tags added: rls-ee-notfixing
--
You received this bug notification
** Changed in: modemmanager (Ubuntu Eoan)
Assignee: (unassigned) => Till Kamppeter (till-kamppeter)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to modemmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1819615
Title:
** Changed in: mesa (Ubuntu Eoan)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1815889
Title:
qemu-system-x86_64 crashed with signal
Ordering was important:
$ modprobe shiftfs
$ sudo snap set lxd shiftfs.enable=true
$ sudo systemctl restart snap.lxd.daemon
Now it is enabled:
$ lxc info | grep shiftfs
shiftfs: "true"
$ lxc exec
I can confirm this bug. My VPS servers are configured to automatically
reboot daily and one of them started hanging up with similar error a few
days ago. I am using Ubuntu 18.10 x64 running on Vultr VPS. When the VPS
hanged today, the screen ended with these messages:
[ OK ] Reached target
Thank you, Victor, for all the verifications and the nice reports for
each of them!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1822062
Title:
Race condition on boot
Regarding the optimal behaviour u-u spends significant amount of CPU time on
deciding which are the upgradable packages especially if there are held
packages thus there is a tradeoff between network and CPU usage.
I believe both of the options have their benefits, and on a desktop system
** Patch added: "lp1822270-cosmic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1822270/+attachment/5262099/+files/lp1822270-cosmic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to debconf in
** Patch added: "lp1822270-bionic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1822270/+attachment/5262100/+files/lp1822270-bionic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to debconf in
** Patch added: "lp1822270-xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1822270/+attachment/5262101/+files/lp1822270-xenial.debdiff
** Tags added: sts-sponsor
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Unattended-upgrades in not affected by this bug because it downloads
only packages it would install and the configuration files it ships are
set to only do that.
It looks like software properties changes the files to include those keys.
** Patch added: "lp1822270-disco.debdiff"
https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1822270/+attachment/5262098/+files/lp1822270-disco.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to debconf in
I have not seen/triggered the kernel issue mentioned in here (identified by
jdstrand).
But on request I'll try it at least.
Testing on Disco with Host Having:
5.0.0-13-generic
# Create container and trigger the issue:
lxc launch ubuntu-daily:d d-testapparmor
# update the container to not have
** Changed in: unattended-upgrades (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1825812
Title:
Daily apt update timer downloads all
** Tags removed: verification-needed verification-needed-disco
** Tags added: verification-done verification-done-disco
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1822062
That's indeed an issue, thanks for the bug report
** Changed in: ibus (Ubuntu)
Importance: Undecided => Low
** Changed in: ibus (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
# VERIFICATION: DISCO
- Using the reproducer defined in the test case and the version in -updates:
ubuntu@disco-sssd-ad:~$ dpkg -l | grep -E "cups-daemon| cups |cups-common"
ii cups 2.2.10-4amd64
Common UNIX Printing System(tm) -
** Tags added: sts-sponsor-ddstreet
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/1827172
Title:
update-rc.d: enabling or disabling S runlevel services incorrectly
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in
# VERIFICATION: COSMIC
- Using the reproducer defined in the test case and the version in -updates:
ubuntu@cosmic-sssd-ad:~$ dpkg -l | grep -E "cups-daemon| cups |cups-common"
ii cups 2.2.8-5ubuntu1.2amd64
Common UNIX Printing System(tm) -
** Tags removed: verification-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1822062
Title:
Race condition on boot between
Victor thank you very much for your great verification reports on Xenial
and Bionic. I have marked these two as verified now.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
** Tags removed: verification-done-bionic verification-needed-xenial
** Tags added:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gdb (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
** Changed in: apt (Ubuntu Cosmic)
Status: New => In Progress
** Changed in: apt (Ubuntu Bionic)
Status: New => In Progress
** Changed in: apt (Ubuntu Xenial)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Changed in: apt (Ubuntu Cosmic)
Status: New => In Progress
** Changed in: apt (Ubuntu Bionic)
Status: New => In Progress
** Changed in: apt (Ubuntu Xenial)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
# VERIFICATION: BIONIC
- Using the reproducer defined in the test case and the version in -updates:
ubuntu@bionic-sssd-ad:~$ dpkg -l | grep -E "cups-daemon| cups |cups-common"
ii cups 2.2.7-1ubuntu2.4
amd64Common UNIX Printing
# VERIFICATION: XENIAL
- Using the reproducer defined in the test case and the version in -updates:
ubuntu@xenial-sssd-ad:~$ dpkg -l | grep -E "cups-daemon| cups |cups-common"
ii cups 2.1.3-4ubuntu0.7
amd64Common UNIX Printing
This bug was fixed in the package unattended-upgrades - 1.10ubuntu5.1
---
unattended-upgrades (1.10ubuntu5.1) disco; urgency=medium
* Skip trying to upgrade held packages in call_adjusted() (LP: #1824804)
* Follow all kinds of transitive dependencies when adjusting dependencies
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.11
---
unattended-upgrades (1.1ubuntu1.18.04.11) bionic; urgency=medium
* Detect changes to moved conffiles (LP: #1823872)
- Add tests for checking conffile moves.
Build depend on and use equivs to
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.3
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.3) xenial; urgency=medium
* Detect changes to moved conffiles (LP: #1823872)
- Add tests for checking conffile moves.
Build depend on and
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.11
---
unattended-upgrades (1.1ubuntu1.18.04.11) bionic; urgency=medium
* Detect changes to moved conffiles (LP: #1823872)
- Add tests for checking conffile moves.
Build depend on and use equivs to
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.3
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.3) xenial; urgency=medium
* Detect changes to moved conffiles (LP: #1823872)
- Add tests for checking conffile moves.
Build depend on and
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.3
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.3) xenial; urgency=medium
* Detect changes to moved conffiles (LP: #1823872)
- Add tests for checking conffile moves.
Build depend on and
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.3
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.3) xenial; urgency=medium
* Detect changes to moved conffiles (LP: #1823872)
- Add tests for checking conffile moves.
Build depend on and
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.3
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.3) xenial; urgency=medium
* Detect changes to moved conffiles (LP: #1823872)
- Add tests for checking conffile moves.
Build depend on and
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.3
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.3) xenial; urgency=medium
* Detect changes to moved conffiles (LP: #1823872)
- Add tests for checking conffile moves.
Build depend on and
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.11
---
unattended-upgrades (1.1ubuntu1.18.04.11) bionic; urgency=medium
* Detect changes to moved conffiles (LP: #1823872)
- Add tests for checking conffile moves.
Build depend on and use equivs to
This bug was fixed in the package unattended-upgrades - 1.10ubuntu5.1
---
unattended-upgrades (1.10ubuntu5.1) disco; urgency=medium
* Skip trying to upgrade held packages in call_adjusted() (LP: #1824804)
* Follow all kinds of transitive dependencies when adjusting dependencies
This bug was fixed in the package unattended-upgrades -
1.5ubuntu3.18.10.4
---
unattended-upgrades (1.5ubuntu3.18.10.4) cosmic; urgency=medium
* Detect changes to moved conffiles (LP: #1823872)
* Add tests for checking conffile moves.
Build depend on and use equivs to
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.3
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.3) xenial; urgency=medium
* Detect changes to moved conffiles (LP: #1823872)
- Add tests for checking conffile moves.
Build depend on and
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.11
---
unattended-upgrades (1.1ubuntu1.18.04.11) bionic; urgency=medium
* Detect changes to moved conffiles (LP: #1823872)
- Add tests for checking conffile moves.
Build depend on and use equivs to
This bug was fixed in the package unattended-upgrades -
1.5ubuntu3.18.10.4
---
unattended-upgrades (1.5ubuntu3.18.10.4) cosmic; urgency=medium
* Detect changes to moved conffiles (LP: #1823872)
* Add tests for checking conffile moves.
Build depend on and use equivs to
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.3
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.3) xenial; urgency=medium
* Detect changes to moved conffiles (LP: #1823872)
- Add tests for checking conffile moves.
Build depend on and
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.11
---
unattended-upgrades (1.1ubuntu1.18.04.11) bionic; urgency=medium
* Detect changes to moved conffiles (LP: #1823872)
- Add tests for checking conffile moves.
Build depend on and use equivs to
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.3
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.3) xenial; urgency=medium
* Detect changes to moved conffiles (LP: #1823872)
- Add tests for checking conffile moves.
Build depend on and
This bug was fixed in the package unattended-upgrades - 1.10ubuntu5.1
---
unattended-upgrades (1.10ubuntu5.1) disco; urgency=medium
* Skip trying to upgrade held packages in call_adjusted() (LP: #1824804)
* Follow all kinds of transitive dependencies when adjusting dependencies
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.11
---
unattended-upgrades (1.1ubuntu1.18.04.11) bionic; urgency=medium
* Detect changes to moved conffiles (LP: #1823872)
- Add tests for checking conffile moves.
Build depend on and use equivs to
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.3
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.3) xenial; urgency=medium
* Detect changes to moved conffiles (LP: #1823872)
- Add tests for checking conffile moves.
Build depend on and
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.3
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.3) xenial; urgency=medium
* Detect changes to moved conffiles (LP: #1823872)
- Add tests for checking conffile moves.
Build depend on and
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.11
---
unattended-upgrades (1.1ubuntu1.18.04.11) bionic; urgency=medium
* Detect changes to moved conffiles (LP: #1823872)
- Add tests for checking conffile moves.
Build depend on and use equivs to
This bug was fixed in the package unattended-upgrades -
1.5ubuntu3.18.10.4
---
unattended-upgrades (1.5ubuntu3.18.10.4) cosmic; urgency=medium
* Detect changes to moved conffiles (LP: #1823872)
* Add tests for checking conffile moves.
Build depend on and use equivs to
This bug was fixed in the package unattended-upgrades - 1.10ubuntu5.1
---
unattended-upgrades (1.10ubuntu5.1) disco; urgency=medium
* Skip trying to upgrade held packages in call_adjusted() (LP: #1824804)
* Follow all kinds of transitive dependencies when adjusting dependencies
This bug was fixed in the package unattended-upgrades -
1.5ubuntu3.18.10.4
---
unattended-upgrades (1.5ubuntu3.18.10.4) cosmic; urgency=medium
* Detect changes to moved conffiles (LP: #1823872)
* Add tests for checking conffile moves.
Build depend on and use equivs to
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.11
---
unattended-upgrades (1.1ubuntu1.18.04.11) bionic; urgency=medium
* Detect changes to moved conffiles (LP: #1823872)
- Add tests for checking conffile moves.
Build depend on and use equivs to
1 - 100 of 121 matches
Mail list logo
