Let me try and restate this in detail to make sure I understand it.
Trusty: add a new binary package called isc-dhcp-client-noddns. This
will work the same as isc-dhcp-client-ddns in Xenial, but in reverse. It
will use the same dpkg-divert mechanism to provide a replacement
/sbin/dhclient that
> The hosts in question were upgraded from prior LTS, so they would have
inherited ntpdate from there.
Thanks. We didn't have it removed for upgraders, so I guess that's not
happening by any other mechanism. I'm not sure we should do that either.
The only packaging mechanisms I can think of would
** Also affects: krb5 (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/1648901
Title:
SPNEGO crash on mechanism
Please see: https://lists.ubuntu.com/archives/ubuntu-
devel/2016-August/039484.html
Summary: in Ubuntu, we don't expect to use ntpdate any more. We're
leaving bugs in ntpdate packaging behind, on the basis that ntpdate no
longer needs to be installed by default.
Can you fix the problem by
Note that we also don't usually release SRUs on Fridays or over the
weekend.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1621507
Title:
initramfs-tools
11:11 cyphermox, lamont: in bug 1621507's test cases, we had
previous reported regressions with ip="" and ip=:eth0:dhcp. Those
should be in the test plan, IMHO.
11:13 cyphermox: lamont: what are "jderose's use cases"?
11:15 cyphermox: lamont: also, under "Non-MAAS test cases",
will it
It seems that upstream and Debian are Won't Fix. I don't think Ubuntu
will deviate from this (due to the security maintenance nightmare it may
produce) so I'll set this bug to Won't Fix for Ubuntu to make this
clear.
If upstream or Debian's position changes, we can always change this.
** Changed
** Changed in: ca-certificates (Ubuntu)
Status: Incomplete => New
** Changed in: nss (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nss in Ubuntu.
> The test case in
https://github.com/krb5/krb5/pull/436#issuecomment-209017277 is the best
we can offer without going through the trouble of setting up OMI.
This is fine, but it should be explained in this bug so people
processing this update do not get confused. Please follow
The verification of the Stable Release Update for util-linux has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
16:49 bdmurray: I hadn't looked at bug 1640823 again, no. Shall
I review and release ifappropriate during my SRU day tomorrow?
16:50 rbasak: Since you had an opinion I think that's
appropriate
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
> Actual results in proposal A: apt resolves this by updating isc-dhcp-
client-ddns first to 4.3.3-5ubuntu12.7 and then isc-dhcp-client to
4.3.3-5ubuntu12.7.
To be clear, that means I think the behaviour in proposal A would be
wrong. I'm open to further suggestions on what we could do, or why my
** Changed in: nss (Ubuntu)
Importance: Undecided => High
** Changed in: nss (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1638689
Thanks Sam!
** Changed in: krb5 (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/1644595
Title:
krb5-1.13.2+dfsg-5 source
Closing as requested, thanks.
** Changed in: cyrus-sasl2 (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu.
https://bugs.launchpad.net/bugs/1636689
Title:
I don't follow. isc-dhcp-ddns in Xenial ships /sbin/dhclient and a dpkg-
divert in its prerm. I don't see how Breaks/Replaces is relevant. Are
you planning something different in Trusty?
Louis said: "...if isc-dhcp-ddns Breaks/Replaces isc-dhcp and Recommends
isc-dhcp-ddns...". isc-dhcp-ddns
On Sat, Dec 10, 2016 at 08:20:59PM -, Eric Desrochers wrote:
> > What will happen to existing Trusty users who are relying on the
> current ddns functionality?
>
> Existing Trusty user at next isc-dhcp-client pkg upgrade will
> automatically receive (Recommends: isc-dhcp-client-ddns).
> isc-dhcp-client pkg : dhclient with DDNS functionality disabled (no
random extra ports)
What will happen to existing Trusty users who are relying on the current
ddns functionality?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Hello LaMont, or anyone else affected,
Accepted isc-dhcp into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/isc-
dhcp/4.3.3-5ubuntu12.6 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
Hello LaMont, or anyone else affected,
Accepted initramfs-tools into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/initramfs-
tools/0.122ubuntu8.7 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Hello LaMont, or anyone else affected,
Accepted open-iscsi into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/open-
iscsi/2.0.873+git0.3b4b4500-14ubuntu3.3 in a few hours, and then in the
-proposed repository.
Please help us by testing this
Hello LaMont, or anyone else affected,
Accepted ifupdown into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/ifupdown/0.8.10ubuntu1.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
I've been working on reviewing this over the last few days. Thanks to
everyone for your help and patience, especially Mathieu, LaMont and
Scott for your in-person interactive responses.
We've had various review feedback loops and settled on using the MPs for
coordination. When everyone (including
This is tangled up into the MAAS IPv6 SRU happening in bug 1621507.
Please check that bug for verification-done before accepting ifupdown
into xenial-updates.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in
** Description changed:
initramfs' configure_networking function uses ipconfig to configure the
network.
ipconfig does not support dhcpv6. See:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164
Related bugs:
* bug 1229458: grub2 needed changes
* bug 1621615: network not
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1628306
Title:
network booting fails for iscsi root if no ip is set
Status in
** Description changed:
initramfs' configure_networking function uses ipconfig to configure the
network.
ipconfig does not support dhcpv6. See:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164
Related bugs:
* bug 1229458: grub2 needed changes
* bug 1621615: network not
** Also affects: isc-dhcp (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1176046
Title:
isc-dhcp dhclient
Using my example, I did:
systemd-analyze set-log-level debug
systemctl stop cups.service
touch /var/cache/cups/org.cups.cupsd
sudo rm /var/cache/cups/org.cups.cupsd
systemctl stop cups.service
systemd-analyze set-log-level info
journalctl -b > /tmp/journal.txt
And journal.txt attached. Note that
** Description changed:
+ [Summary]
+
+ A regression in apt in Xenial 1.2.15 causes "apt-get update" to fail
+ with "At least one invalid signature was encountered." if there are
+ files in /etc/apt/trusted.gpg.d/ that are not readable by the _apt user.
+
+ This has the consequence of getting
On Fri, Dec 02, 2016 at 10:19:24AM -, Martin Pitt wrote:
> It sounds like cups.service gets stopped, but around the same time
> something tries to start it again, possibly via either cups.path or
> cups.socket. In generally, if you need to prevent a service from
> restarting, you need to first
For those affected, you can install the version in proposed for the time
being (see comment 21), until we decide how to manage this (see comment
27). As I understand it, this is the exact fix that will eventually land
in updates.
--
You received this bug notification because you are a member of
> There must be some problem in systemd's shutdown process.
Either this, or it is expected behaviour and cups-daemon's supplied
systemd units are somehow wrong. Or it could be in debhelper. I'm not
sure which.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Sorry, I screwed up my quoting a little there. Hopefully it's still
comprehensible.
--
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/1642966
Title:
package cups-daemon 2.1.3-4
@Till
> Robie, thanks for the investigations. I have looked into what the file
/var/cache/cups/org.cups.cupsd (CUPS calls it "keepalive" file) is good
for and what CUPS does with it. The file is created by the CUPS daemon
cupsd when it needs to keep running, having active jobs, being in the
** Also affects: ntp (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1432935
Title:
ntpd -x steps clock on leap
Another consideration is that the web interface is optional, whereas the
failure in bug 1642966 will happen for some proportion of users with a
default installation.
To be clear, I'm not saying that we shouldn't release this SRU; just
that some consideration and discussion is warranted to
> To the SRU team: Bug 1642966 cannot be caused by the fix for this bug.
I agree. But nevertheless, users may still get errors when upgrading,
and won't get errors if we don't release this SRU. So the failures would
still be a consequence of releasing this SRU, so I think we should care.
> Bug
I can reproduce my original example on Xenial on a different machine,
and now I see that it is a race. Whether I drop the sleeps or not, it
sometimes gives me "Job for cups.service canceled." and sometimes:
Warning: Stopping cups.service, but it can still be activated by:
cups.path
--
You
I'm getting some stranger behaviour on Zesty.
1) cups.path doesn't seem to be started until after reboot.
2) I can't reliably reproduce my example case. After the second stop,
cups.service is claimed to have been stopped successfully, but a subsequent
call to "systemctl status cups.service"
I think this might be caused by an interesting interaction between
systemd, debhelper and the CUPS scheduler.
I can reproduce a very similar error with the following. I think (though
am not sure) that this is related to the root cause. On a fresh Xenial
system:
sudo apt-get update && sudo
** Tags removed: verification-neededd
** Tags added: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ido in Ubuntu.
https://bugs.launchpad.net/bugs/1506427
Title:
Using calendar with keys might cause
It looks like the updates to Trusty and Precise can now be released.
Scott, there's .git noise in the Precise diff:
http://launchpadlibrarian.net/291515979/isc-
dhcp_4.1.ESV-R4-0ubuntu5.11_4.1.ESV-R4-0ubuntu5.12.diff.gz - do you want
me to release anyway?
Yakkety has been superseded by bug
> Will ask the SRU team if it would be acceptable to split up the binary
package in two to include changes (already applied in Xenial) to trusty.
I think that it's important that existing Trusty users can continue to
use this DDNS functionality after the SRU without any necessary
intervention.
Based on the investigation so far, it seems to me that this is entirely
a kernel bug, and there is nothing required in the bridge-utils package
in order to fix this issue. So I'm marking this bug as Invalid for
bridge-utils. The kernel tasks remain open. If this is incorrect, please
explain why
> Any news on handling this bug?
Sorry, this is deep in the backlog and I don't expect Ubuntu developers
to look into this any time soon on a volunteer basis.
I suggest that you try the latest upstream openssh release, and if it is
still an issue there, then raise the bug upstream if it hasn't
Thank you for your report.
You can find pointers to get help for this sort of problem here:
http://www.ubuntu.com/support/community
If it turns out that your issue is a bug in Ubuntu, then we need a full
bug report please. Until then, we can't make any progress on this
report, and you won't find
(patches welcome!)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1641272
Title:
Debug symbols package doesnt exist
Status in dnsmasq package in Ubuntu:
New
Bug
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Setting Importance to Low as this only impacts developers.
** Changed in: dnsmasq (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
I'm sorry, my mistake. I see what you mean now. It's "Alladin Free
Public License", is mentioned in the boilerplate, but the associated
copy of the license doesn't appear to be included.
** Changed in: krb5 (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification
I cannot find the license claim mentioned. In the source for krb5
1.13.2+dfsg-5, I see src/ccapi/common/win/OldCC/autolock.hxx but it
appears to have a regular MIT-style license boilerplate. It has
sha256sum
02d63ce54f142101910143464f9eea3935f7d478e4e32998f5ba02cf8ffddc61. I also
grepped for
> Can we get a newer version out in precise please?
No. Cherry-picking just the fix for this bug is the most we would do to
minimise risk to existing users. See
https://wiki.ubuntu.com/StableReleaseUpdates for rationale, policy and
procedure.
The maximum impact of this bug is that users get
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libav in Ubuntu.
https://bugs.launchpad.net/bugs/1643467
Title:
Firefox 50 blocks Ubuntu 14.04 LTS's version of libavcodec
Status in firefox
Apologies, that should be for Xenial, not Yakkety.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in
Ubuntu.
https://bugs.launchpad.net/bugs/1619600
Title:
[SRU] New stable release 1.8.3
Status in
Hello Iain, or anyone else affected,
Accepted gst-plugins-bad1.0 into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/gst-
plugins-bad1.0/1.8.3-1ubuntu0.2 in a few hours, and then in the
-proposed repository.
Please help us by testing this new
Hello Iain, or anyone else affected,
Accepted gst-plugins-bad1.0 into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/gst-
plugins-bad1.0/1.8.3-1ubuntu0.2 in a few hours, and then in the
-proposed repository.
Please help us by testing this new
Hello Iain, or anyone else affected,
Accepted gst-plugins-bad1.0 into yakkety-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source/gst-
plugins-bad1.0/1.8.3-1ubuntu0.2 in a few hours, and then in the
-proposed repository.
Please help us by testing this
This bug is blocked in the SRU process because it has no SRU
information. Please see
https://wiki.ubuntu.com/StableReleaseUpdates#Procedure
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubuntu.
This is confusing. Yakkety has never (to date) had an SRU land. So the
proposed revert to Yakkety isn't actually a revert from Yakkety's
perspective. Doing so would mean a behavioural change to Yakkety users,
no?
--
You received this bug notification because you are a member of Ubuntu
Touch
This felt unusually risk to me, so I took a look at the patch before
releasing. I found a number of problems:
1. This patch leaks a file descriptor every time the new code path runs.
loop_ctl_fd is opened but not closed.
2. "int devnr = -1" is defined but never used.
3.
> ll->ncur =
I can reproduce this fairly reliably (~50%) if my phone hasn't been used
in a while. Enough that I've caught a video of it doing it. media-
hub.log attached.
If I unlock the phone and go into the sound settings (from the sound
indicator), then turn the screen off, then the phone reliably doesn't
Public bug reported:
On my Aquaris 4.5, OTA-13, indicator-datetime
15.10+15.04.20160820.1-0ubuntu1, it uses too much RSS. A typical RSS is
315892, almost three times as much as unity8.
I believe this is an OTA regression. I'm not sure if it regressed from
OTA-11 or OTA-12.
Just now, I got
rbasak, well, that bug has not got any visible attention from
others, so I don't know who I am discussing it with.
rbasak, no-one should rely on behavior that makes output
ambiguous. The bug is fixed in 16.04 anyway.
jarnos: I don't think it matters where users "should" rely on
behaviour or
I suggest Bug #1621226 should be SRUed.
jarnos: that's reasonable, but it's also a change in behaviour
that users may be relying on, as grep tends to be used quite a bit in
scripts.
So I'm not sure.
I added a task in the bug for you. Can discuss in there.
** Also affects: grep (Ubuntu
Hello LaMont, or anyone else affected,
Accepted open-iscsi into yakkety-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/open-
iscsi/2.0.873+git0.3b4b4500-14ubuntu8.1 in a few hours, and then in the
-proposed repository.
Please help us by testing this
Hello LaMont, or anyone else affected,
Accepted open-iscsi into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/open-
iscsi/2.0.873+git0.3b4b4500-14ubuntu3.2 in a few hours, and then in the
-proposed repository.
Please help us by testing this
We discussed this on IRC in #ubuntu-release and agreed on the following
plan of action:
0. cyphermox has uploaded open-iscsi to xenial and yakkety
1. rbasak will review open-iscsi (only) for acceptance into
{xenial,yakkety}-proposed. Go back to step 0 for diff changes as needed, but
there are
I'm here processing open-scsi in the Xenial and Yakkety SRU queues.
However, I feel that this SRU is far from ready to be accepted into the
proposed pockets and am inclined to reject the uploads to prevent
further confusion.
1) Stakeholders don't appear to have consensus on how this problem
Thank you for your report. I think you're asking for this bug to be
closed? I'll set the bug status to Invalid accordingly.
If you need help, you can find pointers to get help for this sort of
problem here: http://www.ubuntu.com/support/community
** Changed in: openssh (Ubuntu)
Status:
I'm going to leave this as Incomplete, since it isn't clear to me that
this is a bug in Ubuntu at all. If you can provide steps that will
produce the problem on a different system, then we can look further.
Otherwise, please understand that this bug will not make progress, and
that you're more
Thank you for taking the time to report this bug and helping to make
Ubuntu better. I'm following up on old bugs today.
If "UsePAM yes" (the default) fixes this issue, then I'm not sure this
is a bug in Ubuntu. Is this what you intended with your last comment? Or
even you still consider this to
** Changed in: iproute2 (Ubuntu)
Status: In Progress => Triaged
** Changed in: iproute2 (Ubuntu)
Importance: Undecided => High
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in
*** This bug is a duplicate of bug 1385868 ***
https://bugs.launchpad.net/bugs/1385868
This was reported against Vivid in July 2015, and Vivid was EOL in Feb
2016 and never fixed in bug 1385868. So I think this is a duplicate of
bug 1385868 and is now fixed in Wily, Xenial, Yakkety and Zesty.
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since there isn't enough information in your report to differentiate
between a local configuration problem and a bug in Ubuntu, I'm marking
this bug as Incomplete.
If indeed this is a local configuration problem,
>From log:
Log started: 2016-10-24 21:10:52
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ...
This is reported as fixed in Debian net-tools 1.60-26, which is included
in every Ubuntu release since Vivid. This means that it should be fixed
in 16.04, 16.10 and the current development release (Zesty).
If this is incorrect, please reopen.
** Changed in: net-tools (Ubuntu)
Status:
Thank you for taking the time to report this bug and helping to make
Ubuntu better. I'm catching up on old bugs today.
This sounds like a valid bug, but I don't think it's worth diverging
Ubuntu over this due to the additional maintenance effort this would
require. So I don't think we'll fix this
** Changed in: openssh (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/349913
Title:
sftp: cannot enter umlauts like ä, ö, ü
According to http://support.ntp.org/bin/view/Dev/DeprecatingNtpdate, it
seems that they expect you to use the sntp client for that
functionality. Is this sufficient?
But yes - given that ntpdate is deprecated upstream, in general it would
make sense to communicate upstream for any lost use cases.
** Changed in: ncurses (Ubuntu)
Importance: Undecided => Wishlist
** Tags added: upgrade-software-version
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ncurses in Ubuntu.
https://bugs.launchpad.net/bugs/1637239
Title:
> So, yes, my configuration is invalid, but the behavior of sshd when
this happens and the experience around it could use improvement. If it
detects that the configuration is invalid, it should flag it as such and
make it obvious from the logs/stdout/stdterr rather than letting the
process try to
Let's set Importance to Low to make it clear that this won't be worked
on any time soon. Sorry Andrej - with only one person marked as affected
we can't prioritise this.
** Changed in: openssh (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a
This is a request for Launchpad admins.
16:06 How should I tackle bug 1523051? I don't see anything I
can edit - does it need to be passed to Launchpad admins to fix?
16:06 bug 1523051 in net-tools (Ubuntu) "Upstream link needs
changing" [Undecided,New]
Public bug reported:
During development, we have packages in -proposed that fail to migrate,
as expected, for good reason.
At release time, these packages are still present. For example, Yakkety
released with libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 in
proposed, which is not in the
It looks to me that this is either a bug in unattended-upgrades, or
intended behaviour that due to the conffile prompt unattended-upgrades
is supposed to fail and requires user intervention to answer the prompt.
I'm not sure which.
--
You received this bug notification because you are a member
On Fri, Oct 07, 2016 at 03:20:29PM -, hackeron wrote:
> My biggest issue is virtual interfaces do NOT work with these
> "predictable" network names. I can do ifconfig eth0:0 192.168.123.123
> but I cannot do ifconfig enxb827djdk:0 192.168.123.123 - it just
> overrites the main IP, rather than
See https://en.wikipedia.org/wiki/Denial-of-service_attack - that's the
counterargument.
But whichever way, you don't have the right audience here. Tell upstream
:)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in
This is a feature request that may be addressed by upstream, but
certainly won't be addressed by Ubuntu in a delta. Therefore I'm marking
the "openssh (Ubuntu)" task as Won't Fix for now, because we have no
plans to fix it in Ubuntu. If you'd still like this feature in the
openssh package, then
** Changed in: bridge-utils (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bridge-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1626826
Title:
KVM guest cannot use br0 created
*** This bug is a duplicate of bug 1617963 ***
https://bugs.launchpad.net/bugs/1617963
** This bug is no longer a duplicate of bug 1628251
package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 failed to
install/upgrade: le paquet libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 ne
*** This bug is a duplicate of bug 1617963 ***
https://bugs.launchpad.net/bugs/1617963
** This bug has been marked a duplicate of bug 1617963
package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 failed to
install/upgrade: package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 cannot
be
*** This bug is a duplicate of bug 1617963 ***
https://bugs.launchpad.net/bugs/1617963
** This bug is no longer a duplicate of bug 1628251
package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 failed to
install/upgrade: le paquet libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 ne
Mirroring the development release's Incomplete status in Xenial - see
comment 15.
** Changed in: lxc (Ubuntu Xenial)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
** Tags added: server-notriage
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pm-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1625995
Title:
[Dell Precision 5510][Yakkety] Failed to suspend correctly then
Thank you for helping out! However see
http://askubuntu.com/q/785414/7808: "There is very little benefit to
users in using -proposed during the development cycle and such use is
strongly discouraged."
Packages in yakkety-proposed that are not in yakkety are *known to be
broken* - otherwise they
In fact I've figured out your misconfiguration: you have yakkety-
proposed enabled, which you should not have.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to heimdal in Ubuntu.
https://bugs.launchpad.net/bugs/1617963
Title:
*** This bug is a duplicate of bug 1617963 ***
https://bugs.launchpad.net/bugs/1617963
** This bug has been marked a duplicate of bug 1617963
package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 failed to
install/upgrade: package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 cannot
be
*** This bug is a duplicate of bug 1617963 ***
https://bugs.launchpad.net/bugs/1617963
** This bug is no longer a duplicate of bug 1620955
package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 failed to
install/upgrade: pakket libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 kan
niet
*** This bug is a duplicate of bug 1617963 ***
https://bugs.launchpad.net/bugs/1617963
** This bug has been marked a duplicate of bug 1617963
package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 failed to
install/upgrade: package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 cannot
be
*** This bug is a duplicate of bug 1617963 ***
https://bugs.launchpad.net/bugs/1617963
** This bug is no longer a duplicate of bug 1620955
package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 failed to
install/upgrade: pakket libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 kan
niet
801 - 900 of 1200 matches
Mail list logo