Ubuntu 18.10 (Cosmic Cuttlefish) released

Codenamed "Cosmic Cuttlefish", 18.10 continues Ubuntu's proud tradition
of integrating the latest and greatest open source technologies into a
high-quality, easy-to-use Linux distribution. The team has been hard at
work through this cycle, introducing new features and fixing bugs.

The Ubuntu kernel has been updated to the 4.18 based Linux kernel,
our default toolchain has moved to gcc 8.2 with glibc 2.28, and we've
also updated to openssl 1.1.1 and gnutls 3.6.4 with TLS1.3 support.

Ubuntu Desktop 18.04 LTS brings a fresh look with the community-driven
Yaru theme replacing our long-serving Ambiance and Radiance themes. We
are shipping the latest GNOME 3.30, Firefox 63, LibreOffice 6.1.2, and
many others.

Ubuntu Server 18.10 includes the Rocky release of OpenStack including
the clustering enabled LXD 3.0, new network configuration via netplan.io,
and iteration on the next-generation fast server installer. Ubuntu Server
brings major updates to industry standard packages available on private
clouds, public clouds, containers or bare metal in your datacentre.

The newest Ubuntu Budgie, Kubuntu, Lubuntu, Ubuntu Kylin, Ubuntu MATE,
Ubuntu Studio, and Xubuntu are also being released today.

More details can be found for these at their individual release notes:

https://wiki.ubuntu.com/CosmicCuttlefish/ReleaseNotes#Official_flavours

intenance updates will be provided for 9 months for all flavours
releasing with 18.10.

To get Ubuntu 18.10
-------------------

In order to download Ubuntu 18.10, visit:

http://www.ubuntu.com/download

Users of Ubuntu 18.04 will be offered an automatic upgrade to 18.10
if they have selected to be notified of all releases, rather than just
LTS upgrades. For further information about upgrading, see:

http://www.ubuntu.com/download/desktop/upgrade

As always, upgrades to the latest version of Ubuntu are entirely free
of charge.

We recommend that all users read the release notes, which document
caveats, workarounds for known issues, as well as more in-depth notes
on the release itself. They are available at:

http://wiki.ubuntu.com/CosmicCuttlefish/ReleaseNotes

Find out what's new in this release with a graphical overview:

http://www.ubuntu.com/desktop
http://www.ubuntu.com/desktop/features

If you have a question, or if you think you may have found a bug
but aren't sure, you can try asking in any of the following places:

#ubuntu on irc.freenode.net
http://lists.ubuntu.com/mailman/listinfo/ubuntu-users
http://www.ubuntuforums.org
http://askubuntu.com

Help Shape Ubuntu
-----------------

If you would like to help shape Ubuntu, take a look at the list
of ways you can participate at:

http://community.ubuntu.com/contribute

About Ubuntu
------------

Ubuntu is a full-featured Linux distribution for desktops, laptops,
netbooks and servers, with a fast and easy installation and regular
releases. A tightly-integrated selection of excellent applications
is included, and an incredible variety of add-on software is just a
few clicks away.

Professional services including support are available from Canonical
and hundreds of other companies around the world. For more information
about support, visit:

http://www.ubuntu.com/support

More Information
----------------

You can learn more about Ubuntu and about this release on our
website listed below:

http://www.ubuntu.com

To sign up for future Ubuntu announcements, please subscribe to
Ubuntu's very low volume announcement list at:

http://lists.ubuntu.com/mailman/listinfo/ubuntu-announce

On behalf of the Ubuntu Release Team,

... Adam Conrad

--
ubuntu-announce mailing list
ubuntu-announce@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-announce

Looking for example Package solving sysV+.service+.socket

TL;DR: known example of a package correctly solving
sysV+.service+.socket and having only .socket running on install?

- Detail -

Hello everybody,
I want to know if there is any best practise / example on the following case:
A package that delivers:
- sysV init (for old style compat/backport or just happens to be there)
- .service supposed to replace the sysV
- the .service should be installed and enabled, but not started in postinst
- .socket installed and started on install supposed to be starting the
service when needed

I've hit a few cases like that now, and in most of them I see
- dh_installinit for sysV trumps dh_installsystemd/dh_systemd_*
- invoke.rc start is mapped to systemd service start
- service ends up started which it shoudl not

I have tried different combinations of --no-start and dh_*_override's,
but never succeeded to something great so far.
Different compat levels have great impact on this as well,
unfortunately none resolved it for me.
The few cases I know ended up dropping the sysV init to get out of the
situation :-/

This is why I wanted to reach out if anybody knows better "prior art"
to resolve this.

--
Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd

--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel

Re: Poll: Ubuntu Technical Board election 2018

On Fri, Oct 5, 2018 at 7:05 PM Walter Lapchynski <wxl@ubuntu.com> wrote:
>
> On 2018-10-05 12:14, Walter Lapchynski wrote:
> > On 2018-10-05 11:36, Marc Deslauriers wrote:
> >> On 2018-10-05 01:27 PM, Walter Lapchynski wrote:
> >>> On 2018-10-05 01:52, Robie Basak wrote:
> >>>> On Fri, Oct 05, 2018 at 12:51:39AM -0400, Ubuntu Community Council
> >>>> (CIVS poll supervisor) wrote:
> >>>>> A special thank you goes out to Marc Deslauriers and Stéphane Graber who will both be stepping down.
> >>>> Marc is in the poll. Is there a mistake?
> >>> Yes, there is, and one I take full responsibility for. Luckily, you'll
> >>> find him listed on the ballot, so all is well.
> >> Would it be possible to remove my name from that sentence at the top of the
> >> poll, and perhaps send out an announcement about the mistake?
> > Unfortunately, I think the only way for me to do this is to make a new
> > poll. The other thing I can potentially do is email all 177 voters with
> > the correction. I know my mail server has limits and I'm not sure if
> > this crosses that, but I could get in touch with them about that. What
> > do you think would be best?
> > Again, sorry, Marc. ☹
>
> Actually, don't answer that. We've decided, since this is one of a
> couple issues that need to be resolved, to stop the poll currently.

So...will a new poll be set up?

> --
> @wxl | polka.bike
> C563 CAC5 8BE1 2F22 A49D
> 68F6 8B57 A48B C4F2 051A
>
> --
> ubuntu-devel mailing list
> ubuntu-devel@lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel

--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel

Re: Version regressions in cosmic compared to bionic

On Wed, Oct 10, 2018 at 04:28:57PM +0200, Gunnar Hjalmarsson wrote:
> On 2018-10-10 14:13, Julian Andres Klode wrote:
> > language-pack-gnome-mai 1:18.04+20180712/bionic-updates -> 1:18.04+20180423/cosmic
> > language-pack-gnome-mai-base 1:18.04+20180712/bionic-updates -> 1:18.04+20180423/cosmic
> > language-pack-mai 1:18.04+20180712/bionic-updates -> 1:18.04+20180423/cosmic
> > language-pack-mai-base 1:18.04+20180712/bionic-updates -> 1:18.04+20180423/cosmic

> Maithili is a language which is not so well translated in Ubuntu. When
> building language packs, a threshold is applied to exclude languages with
> poor translation coverage. Apparently enough strings are translated in
> bionic, but not (yet) in cosmic.

> Łukasz is about to build new language packs. If the Maithili langpacks are
> updated then, all is well. Otherwise it would be most consistent, AFAICT, to
> drop the Maithili language packs from the cosmic archive.

We should just remove those packages now just in case, and if they are
reintroduced in the next export that's fine. I've done this now.

--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer https://www.debian.org/
slangasek@ubuntu.com vorlon@debian.org

Re: Version regressions in cosmic compared to bionic

On 2018-10-10 14:13, Julian Andres Klode wrote:
> language-pack-gnome-mai 1:18.04+20180712/bionic-updates -> 1:18.04+20180423/cosmic
> language-pack-gnome-mai-base 1:18.04+20180712/bionic-updates -> 1:18.04+20180423/cosmic
> language-pack-mai 1:18.04+20180712/bionic-updates -> 1:18.04+20180423/cosmic
> language-pack-mai-base 1:18.04+20180712/bionic-updates -> 1:18.04+20180423/cosmic

Maithili is a language which is not so well translated in Ubuntu. When
building language packs, a threshold is applied to exclude languages
with poor translation coverage. Apparently enough strings are translated
in bionic, but not (yet) in cosmic.

Łukasz is about to build new language packs. If the Maithili langpacks
are updated then, all is well. Otherwise it would be most consistent,
AFAICT, to drop the Maithili language packs from the cosmic archive.

--
Gunnar Hjalmarsson
https://launchpad.net/~gunnarhj

--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel

Re: Version regressions in cosmic compared to bionic

On Wed, Oct 10, 2018 at 02:13:21PM +0200, Julian Andres Klode wrote:
> I recently saw some packages in cosmic that have older
> versions than the one in bionic, so I wrote a script to
> check that, and here are the results.

Some more historic results (xenial->bionic, xenial->cosmic,
trusty->xenial (good), trusty->cosmic).

Version regression support for xenial to bionic
=====================================================
main
----
crash 7.2.3+real-1~16.04.1/xenial-updates -> 7.2.1-1/bionic
linux-meta-azure 4.15.0.1023.29/xenial-security -> 4.15.0.1023.23/bionic-security (but 4.15.0.1025.25 in bionic-proposed)
linux-meta-gcp 4.15.0.1021.35/xenial-security -> 4.15.0.1021.23/bionic-security (but 4.15.0.1022.24 in bionic-proposed)

restricted
----------

universe
--------
fuse-umfuse-ext2 0.4-1.1ubuntu0.16.04.1/xenial-updates -> 0.4-1.1ubuntu0.1/bionic

multiverse
----------

Version regression support for xenial to cosmic
=====================================================
main
----
linux-gcp 4.15.0-1021.22~16.04.1/xenial-updates -> 4.15.0-1019.20/cosmic (but 4.18.0-1001.2 in cosmic-proposed)
linux-meta-azure 4.15.0.1023.29/xenial-updates -> 4.15.0.1023.23/cosmic (but 4.18.0.1002.2 in cosmic-proposed)
linux-meta-gcp 4.15.0.1021.35/xenial-updates -> 4.15.0.1019.21/cosmic (but 4.18.0.1001.1 in cosmic-proposed)
linux-signed-gcp 4.15.0-1021.22~16.04.1/xenial-updates -> 4.15.0-1019.20/cosmic (but 4.18.0-1001.2 in cosmic-proposed)
thunderbird 1:52.9.1+build3-0ubuntu0.16.04.1/xenial-updates -> 1:52.7.0+build1-0ubuntu1/cosmic

restricted
----------

universe
--------
fuse-umfuse-ext2 0.4-1.1ubuntu0.16.04.1/xenial-updates -> 0.4-1.1ubuntu0.1/cosmic
snapcraft 2.43.1/xenial-updates -> 2.43+18.10.1/cosmic (but 2.43.1+18.10 in cosmic-proposed)

multiverse
----------

Version regression support for trusty to xenial
=====================================================
main
----

restricted
----------

universe
--------

multiverse
----------

Version regression support for trusty to cosmic
=====================================================
main
----
thunderbird 1:52.9.1+build3-0ubuntu0.14.04.1/trusty-updates -> 1:52.7.0+build1-0ubuntu1/cosmic

restricted
----------

universe
--------
fuse-umfuse-ext2 0.4-1.1ubuntu0.14.04.1/trusty-updates -> 0.4-1.1ubuntu0.1/cosmic

multiverse
----------

--
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer i speak de, en

--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel

Version regressions in cosmic compared to bionic

#!/usr/bin/python3
"""Calculate regressions in version numbers between two releases."""
import sys
import urllib.request

import apt_pkg

apt_pkg.init()

MIRROR = "http://de1.archive.ubuntu.com/ubuntu/dists/{distro}/{component}/source/Sources.gz"
old = sys.argv[1]
new = sys.argv[2]

print("Version regression support for %s to %s" % (old, new))
print("=====================================================")

for component in "main","restricted","universe", "multiverse":
print(component)
print(len(component) * "-")
old_vers = {}
new_vers = {}
pro_vers = {}
for pocket in "", "-updates":
old_path, _ = urllib.request.urlretrieve(MIRROR.format(distro=old + pocket, component=component), "old.gz")
new_path, _ = urllib.request.urlretrieve(MIRROR.format(distro=new + pocket, component=component), "new.gz")

for sec in apt_pkg.TagFile(old_path):
if apt_pkg.version_compare(sec["Version"], old_vers.get(sec["Package"], [""])[0]) >= 0:
old_vers[sec["Package"]] = sec["Version"], old + pocket
for sec in apt_pkg.TagFile(new_path):
if apt_pkg.version_compare(sec["Version"], new_vers.get(sec["Package"], [""])[0]) >= 0:
new_vers[sec["Package"]] = sec["Version"], new + pocket

pro_path, _ = urllib.request.urlretrieve(MIRROR.format(distro=new + "-proposed", component=component), "pro.gz")
for sec in apt_pkg.TagFile(pro_path):
pro_vers[sec["Package"]] = sec["Version"], new + "-proposed"

for pkg in sorted(old_vers):
if pkg not in new_vers:
continue

if apt_pkg.version_compare(old_vers[pkg][0], new_vers[pkg][0]) > 0:
if pkg in pro_vers and apt_pkg.version_compare(old_vers[pkg][0], pro_vers[pkg][0]) <= 0:
print("%-30s %-50s -> %-40s (but %s)" % (pkg, "/".join(old_vers[pkg]), "/".join(new_vers[pkg]), (" in ".join(pro_vers[pkg]))))
else:
print("%-30s %-50s -> %-40s" % (pkg, "/".join(old_vers[pkg]), "/".join(new_vers[pkg])))
print()
I recently saw some packages in cosmic that have older
versions than the one in bionic, so I wrote a script to
check that, and here are the results.

I think we need to be more careful when it comes to this,
and regressions in security fixes (e.g. having a list
of CVE regressions in devel compared to stable).

The script used for this list is attached, I'd like to polish
it up a bit, add team info, make it generate html and json and
have it run periodically.

Note that the script compares released versions from the
old release to the new release. If there is a newer version
in proposed, it also mentions that, but still lists it.

-- script output:

Version regression support for bionic to cosmic
=====================================================
main
----
ceph 12.2.7-0ubuntu0.18.04.1/bionic-updates -> 12.2.4-0ubuntu1.1build1/cosmic (but 13.2.1+dfsg1-0ubuntu2 in cosmic-proposed)
language-pack-gnome-mai 1:18.04+20180712/bionic-updates -> 1:18.04+20180423/cosmic
language-pack-gnome-mai-base 1:18.04+20180712/bionic-updates -> 1:18.04+20180423/cosmic
language-pack-mai 1:18.04+20180712/bionic-updates -> 1:18.04+20180423/cosmic
language-pack-mai-base 1:18.04+20180712/bionic-updates -> 1:18.04+20180423/cosmic
linux-aws 4.15.0-1023.23/bionic-updates -> 4.15.0-1021.21/cosmic (but 4.18.0-1001.2 in cosmic-proposed)
linux-gcp 4.15.0-1021.22/bionic-updates -> 4.15.0-1019.20/cosmic (but 4.18.0-1001.2 in cosmic-proposed)
linux-meta-aws 4.15.0.1023.23/bionic-updates -> 4.15.0.1021.21/cosmic (but 4.18.0.1001.1 in cosmic-proposed)
linux-meta-gcp 4.15.0.1021.23/bionic-updates -> 4.15.0.1019.21/cosmic (but 4.18.0.1001.1 in cosmic-proposed)
linux-signed-gcp 4.15.0-1021.22/bionic-updates -> 4.15.0-1019.20/cosmic (but 4.18.0-1001.2 in cosmic-proposed)
thunderbird 1:52.9.1+build3-0ubuntu0.18.04.1/bionic-updates -> 1:52.7.0+build1-0ubuntu1/cosmic
woff2 1.0.2-1build0.1/bionic-updates -> 1.0.2-1/cosmic

restricted
----------

universe
--------
mariadb-10.1 1:10.1.34-0ubuntu0.18.04.1/bionic-updates -> 1:10.1.29-6ubuntu2/cosmic (but 1:10.1.35-1ubuntu1 in cosmic-proposed)
snapcraft 2.43.1+18.04/bionic-updates -> 2.43+18.10.1/cosmic (but 2.43.1+18.10 in cosmic-proposed)
swauth 1.3.0-1ubuntu1/bionic-updates -> 1.3.0-1/cosmic

multiverse
----------



--
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer i speak de, en