<div dir="ltr"><div>Hello <br></div>I have two questions.<br><br> * The exact date of end of ppa is not specified. What is the expected day?<br> * Actualy my version of lxd is 2.16..I will update it on January 5th. If the support of the ppa is finished I would only have to delete the entries in "/etc/apt/sources.list.d/ubuntu-lxc-ubuntu-lxd-stable-xenial.list" then "apt update" and "apt install -t xenial-backports lxd lxd-client" Nothing else to do ?<br></div><div class="gmail_extra"><br><div class="gmail_quote">2017-12-27 18:50 GMT+01:00 Thomas Ward <span dir="ltr"><<a href="mailto:teward@ubuntu.com" target="_blank">teward@ubuntu.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<p>Glad to hear it cleared things up!</p>
<p>Just to clarify my post, though, for others, the 'standard'
system I was referring to was my 16.04 Desktop installation.</p>
<p>Just to get the 'bog standard default' policy sets, I spun up a
pristine 16.04 image in LXD, and pulled the `apt-cache policy`
from it:</p>
<p>root@test-xenial-image:~# apt-cache policy | grep backports<br>
100 <a class="m_-2914017425283021488moz-txt-link-freetext" href="http://archive.ubuntu.com/ubuntu" target="_blank">http://archive.ubuntu.com/<wbr>ubuntu</a> xenial-backports/universe
amd64 Packages<br>
release
v=16.04,o=Ubuntu,a=xenial-<wbr>backports,n=xenial,l=Ubuntu,c=<wbr>universe,b=amd64<br>
100 <a class="m_-2914017425283021488moz-txt-link-freetext" href="http://archive.ubuntu.com/ubuntu" target="_blank">http://archive.ubuntu.com/<wbr>ubuntu</a> xenial-backports/main amd64
Packages<br>
release
v=16.04,o=Ubuntu,a=xenial-<wbr>backports,n=xenial,l=Ubuntu,c=<wbr>main,b=amd64<br>
</p>
As is seen here, it too has backports enabled, and has the lower pin
priority. This should be *standard* therefore, though I don't have
a pure Ubuntu server here just now to reconfirm. However, default
pins seem to place it at lower priority, and therefore a purely
optional 'must be specified as installation source' option during
installtion steps. (It's how I moved off the PPAs and onto the
Backports without issue for my LXD 'hypervisor' servers, and my own
laptop for LXD as well).<span class="HOEnZb"><font color="#888888"><br>
<br>
<br>
Thomas</font></span><div><div class="h5"><br>
<br>
<div class="m_-2914017425283021488moz-cite-prefix">On 12/27/2017 12:41 PM, Jeff Kowalczyk
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Thank you, Thomas. Your explanation clears things
up entirely, and I learned several things about apt in the
process. Concerns about PPA deprecation withdrawn.
<div><br>
</div>
<div>Jeff</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, Dec 27, 2017 at 9:04 AM,
Thomas Ward <span dir="ltr"><<a href="mailto:teward@ubuntu.com" target="_blank">teward@ubuntu.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<p>Uhm... I think you're confused here Jeff. Allow me
to explain.<br>
</p>
<p>In Standard Ubuntu releases, Backports is *actually
enabled* but set at a lower pin priority by default.
That is, you can have backports enabled and then only
*selectively* install from Backports. This is a
standard 16.04 system and its corresponding Backports
priority data from `apt-cache priority`:</p>
<p> 100 <a class="m_-2914017425283021488m_6428919636098788563moz-txt-link-freetext" href="http://us.archive.ubuntu.com/ubuntu" target="_blank">http://us.archive.ubuntu.com/u<wbr>buntu</a>
xenial-backports/universe i386 Packages<br>
release v=16.04,o=Ubuntu,a=xenial-back<wbr>ports,n=xenial,l=Ubuntu,c=univ<wbr>erse,b=i386<br>
100 <a class="m_-2914017425283021488m_6428919636098788563moz-txt-link-freetext" href="http://us.archive.ubuntu.com/ubuntu" target="_blank">http://us.archive.ubuntu.com/u<wbr>buntu</a>
xenial-backports/universe amd64 Packages<br>
release v=16.04,o=Ubuntu,a=xenial-back<wbr>ports,n=xenial,l=Ubuntu,c=univ<wbr>erse,b=amd64<br>
100 <a class="m_-2914017425283021488m_6428919636098788563moz-txt-link-freetext" href="http://us.archive.ubuntu.com/ubuntu" target="_blank">http://us.archive.ubuntu.com/u<wbr>buntu</a>
xenial-backports/main i386 Packages<br>
release v=16.04,o=Ubuntu,a=xenial-back<wbr>ports,n=xenial,l=Ubuntu,c=main<wbr>,b=i386<br>
100 <a class="m_-2914017425283021488m_6428919636098788563moz-txt-link-freetext" href="http://us.archive.ubuntu.com/ubuntu" target="_blank">http://us.archive.ubuntu.com/u<wbr>buntu</a>
xenial-backports/main amd64 Packages<br>
release v=16.04,o=Ubuntu,a=xenial-back<wbr>ports,n=xenial,l=Ubuntu,c=main<wbr>,b=amd64<br>
</p>
<p>This indicates it's a lower priority than the updates
or other repositories, such as the standard
xenial-updates, which is shown here below:</p>
<p> 500 <a class="m_-2914017425283021488m_6428919636098788563moz-txt-link-freetext" href="http://us.archive.ubuntu.com/ubuntu" target="_blank">http://us.archive.ubuntu.com/u<wbr>buntu</a>
xenial-updates/multiverse i386 Packages<br>
release v=16.04,o=Ubuntu,a=xenial-upda<wbr>tes,n=xenial,l=Ubuntu,c=multiv<wbr>erse,b=i386<br>
500 <a class="m_-2914017425283021488m_6428919636098788563moz-txt-link-freetext" href="http://us.archive.ubuntu.com/ubuntu" target="_blank">http://us.archive.ubuntu.com/u<wbr>buntu</a>
xenial-updates/multiverse amd64 Packages<br>
release v=16.04,o=Ubuntu,a=xenial-upda<wbr>tes,n=xenial,l=Ubuntu,c=multiv<wbr>erse,b=amd64<br>
500 <a class="m_-2914017425283021488m_6428919636098788563moz-txt-link-freetext" href="http://us.archive.ubuntu.com/ubuntu" target="_blank">http://us.archive.ubuntu.com/u<wbr>buntu</a>
xenial-updates/universe i386 Packages<br>
release v=16.04,o=Ubuntu,a=xenial-upda<wbr>tes,n=xenial,l=Ubuntu,c=univer<wbr>se,b=i386<br>
500 <a class="m_-2914017425283021488m_6428919636098788563moz-txt-link-freetext" href="http://us.archive.ubuntu.com/ubuntu" target="_blank">http://us.archive.ubuntu.com/u<wbr>buntu</a>
xenial-updates/universe amd64 Packages<br>
release v=16.04,o=Ubuntu,a=xenial-upda<wbr>tes,n=xenial,l=Ubuntu,c=univer<wbr>se,b=amd64<br>
500 <a class="m_-2914017425283021488m_6428919636098788563moz-txt-link-freetext" href="http://us.archive.ubuntu.com/ubuntu" target="_blank">http://us.archive.ubuntu.com/u<wbr>buntu</a>
xenial-updates/restricted i386 Packages<br>
release v=16.04,o=Ubuntu,a=xenial-upda<wbr>tes,n=xenial,l=Ubuntu,c=restri<wbr>cted,b=i386<br>
500 <a class="m_-2914017425283021488m_6428919636098788563moz-txt-link-freetext" href="http://us.archive.ubuntu.com/ubuntu" target="_blank">http://us.archive.ubuntu.com/u<wbr>buntu</a>
xenial-updates/restricted amd64 Packages<br>
release v=16.04,o=Ubuntu,a=xenial-upda<wbr>tes,n=xenial,l=Ubuntu,c=restri<wbr>cted,b=amd64<br>
500 <a class="m_-2914017425283021488m_6428919636098788563moz-txt-link-freetext" href="http://us.archive.ubuntu.com/ubuntu" target="_blank">http://us.archive.ubuntu.com/u<wbr>buntu</a>
xenial-updates/main i386 Packages<br>
release v=16.04,o=Ubuntu,a=xenial-upda<wbr>tes,n=xenial,l=Ubuntu,c=main,<wbr>b=i386<br>
500 <a class="m_-2914017425283021488m_6428919636098788563moz-txt-link-freetext" href="http://us.archive.ubuntu.com/ubuntu" target="_blank">http://us.archive.ubuntu.com/u<wbr>buntu</a>
xenial-updates/main amd64 Packages<br>
release v=16.04,o=Ubuntu,a=xenial-upda<wbr>tes,n=xenial,l=Ubuntu,c=main,<wbr>b=amd64</p>
<p><br>
</p>
<p>The priority of 100 is lower than the priority of
500; ultimately, the version pinning *by default*
sticks backports as an optional,
you-must-specify-to-install-fr<wbr>om-backports
option. Therefore, you do ***not*** need extensive
version pinning in Ubuntu releases to use backports
alongside standard system packages, as the system
by-default deprioritizes Backports unless you've
installed something specifically from Backports.
(PPAs actually operate completely differently, and get
the 500 priority which can actually result in
clobbering of data between repos)<br>
</p>
<p>Ultimately, this is ***not*** going to need extensive
version pinning. Trust me on this, as someone who's
done this myself on four separate environments and
actively uses LXD to run multiple production-level
services actively via the four boxes - backports being
enabled don't impact things like you think it does.</p>
<p>(I had this same misconception in the 14.04 era, but
after talking with the release team and other server
team members, this is no longer the case).<br>
</p>
<p><br>
</p>
<p>Thomas<br>
Ubuntu Server Team Member<br>
LP: ~teward<br>
</p>
<div>
<div class="m_-2914017425283021488h5"> <br>
<div class="m_-2914017425283021488m_6428919636098788563moz-cite-prefix">On
12/27/2017 11:57 AM, Jeff Kowalczyk wrote:<br>
</div>
</div>
</div>
<blockquote type="cite">
<div>
<div class="m_-2914017425283021488h5">
<div dir="ltr">
<div>When updating LXD 2.20 on Ubuntu 16.04, I
noticed the PPA deprecation notice, included
below [1].</div>
<div><br>
</div>
<div>I'd like to respectfully ask that the PPA
not be deprecated and continue to see new
package versions. Or at the very least, see
deprecation deferred until after the next LTS
18.04.1 is widely deployed.</div>
<div><br>
</div>
<div>PPAs are well supported with our existing
tooling (saltstack, etc) and allow granular
access to only the desired package (LXD) and
its dependencies. Snap packages are not an
option for my company at this time.</div>
<div><br>
</div>
<div>If I understand correctly, enabling the
backports repository on LTS production systems
to obtain new LXD versions may require
extensive version pinning to keep existing
installed packages at their current versions.</div>
<div><br>
</div>
<div>Given that LXD is a major project of
Canonical, continuing to provide an existing
official PPA is helpful to users, consistent
with other projects publishing debian
packages, and worth the effort to continue
maintenance going forward.<br>
</div>
<div><br>
</div>
<div>Thanks for considering the request.</div>
<div>Jeff</div>
<div><br>
</div>
<div><br>
</div>
[1] Deprecation notice:<br>
<div><br>
</div>
<div>
<div>LXD PPAs to go away by end of year</div>
<div><br>
</div>
<div>We are deprecating all LXD PPAs at the
end of 2017.</div>
<div><br>
</div>
<div>Existing users should move to the LXD
snap as the preferred way to get the</div>
<div>latest LXD feature release on older
Ubuntu releases.</div>
<div><br>
</div>
<div>You can do so by first installing snapd
on your system if it's not there</div>
<div>already. Once snapd is installed,
installing the LXD snap and migrating your</div>
<div>existing data can be done with:</div>
<div><br>
</div>
<div>snap install lxd && lxd.migrate</div>
<div><br>
</div>
<div>Alternatively, we do still provide a .deb
version of LXD for older Ubuntu</div>
<div>releases through the official -backports
archive pocket.</div>
<div><br>
</div>
<div>Those packages are identical to what's
available through our PPAs but benefit</div>
<div>from additional testing on our part. To
switch over to those backport packages,</div>
<div>use:</div>
<div><br>
</div>
<div>apt install -t <release>-backports
lxd lxd-client</div>
<div><br>
</div>
<div>Replacing "<release>" with the
codename of your Ubuntu release (e.g.
xenial).</div>
</div>
<div><br>
</div>
</div>
<br>
<fieldset class="m_-2914017425283021488m_6428919636098788563mimeAttachmentHeader"></fieldset>
<br>
</div>
</div>
<pre>______________________________<wbr>_________________
lxc-users mailing list
<a class="m_-2914017425283021488m_6428919636098788563moz-txt-link-abbreviated" href="mailto:lxc-users@lists.linuxcontainers.org" target="_blank">lxc-users@lists.linuxcontainer<wbr>s.org</a>
<a class="m_-2914017425283021488m_6428919636098788563moz-txt-link-freetext" href="http://lists.linuxcontainers.org/listinfo/lxc-users" target="_blank">http://lists.linuxcontainers.o<wbr>rg/listinfo/lxc-users</a></pre>
</blockquote>
<br>
</div>
</blockquote>
</div>
<br>
</div>
</div>
<br>
<fieldset class="m_-2914017425283021488mimeAttachmentHeader"></fieldset>
<br>
<pre>______________________________<wbr>_________________
lxc-users mailing list
<a class="m_-2914017425283021488moz-txt-link-abbreviated" href="mailto:lxc-users@lists.linuxcontainers.org" target="_blank">lxc-users@lists.<wbr>linuxcontainers.org</a>
<a class="m_-2914017425283021488moz-txt-link-freetext" href="http://lists.linuxcontainers.org/listinfo/lxc-users" target="_blank">http://lists.linuxcontainers.<wbr>org/listinfo/lxc-users</a></pre>
</blockquote>
<br>
</div></div></div>
<br>______________________________<wbr>_________________<br>
lxc-users mailing list<br>
<a href="mailto:lxc-users@lists.linuxcontainers.org">lxc-users@lists.<wbr>linuxcontainers.org</a><br>
<a href="http://lists.linuxcontainers.org/listinfo/lxc-users" rel="noreferrer" target="_blank">http://lists.linuxcontainers.<wbr>org/listinfo/lxc-users</a><br></blockquote></div><br></div>