This is a follow-up to the End of Life warning sent earlier this month to confirm that as of today (Jan 23, 2020), Ubuntu 19.04 is no longer supported. No more package updates will be accepted to 19.04, and it will be archived to old-releases.ubuntu.com in the coming weeks.

The original End of Life warning follows, with upgrade instructions:

Ubuntu announced its 19.04 (Disco Dingo) release almost 9 months ago, on April 18, 2019. As a non-LTS release, 19.04 has a 9-month support cycle and, as such, the support period is now nearing its end and Ubuntu 19.04 will reach end of life on Thursday, Jan 23rd.

At that time, Ubuntu Security Notices will no longer include information or updated packages for Ubuntu 19.04.

The supported upgrade path from Ubuntu 19.04 is via Ubuntu 19.10. Instructions and caveats for the upgrade may be found at:

https://help.ubuntu.com/community/EoanUpgrades

Ubuntu 19.10 continues to be actively supported with security updates and select high-impact bug fixes. Announcements of security updates for Ubuntu releases are sent to the ubuntu-security-announce mailing list, information about which may be found at:

https://lists.ubuntu.com/mailman/listinfo/ubuntu-security-announce

Since its launch in October 2004 Ubuntu has become one of the most highly regarded Linux distributions with millions of users in homes, schools, businesses and governments around the world. Ubuntu is Open Source software, costs nothing to download, and users are free to customise or alter their software in order to meet their needs.

Originally posted to the ubuntu-announce mailing list on Thu Jan 23 21:13:01 UTC 2020 by Adam Conrad, on behalf of the Ubuntu Release Team

23 Jan 2020 10:19pm GMT

Like each month, here comes a report about the work of paid contributors to Debian LTS.

Individual reports

In December, 208.00 work hours have been dispatched among 14 paid contributors. Their reports are available:

• Abhijith PA did 10.0h (out of 10h assigned).
• Adrian Bunk did 4.5h (out of 16.5h assigned), thus carrying over 12h to January.
• Ben Hutchings did 20.25h (out of 16.5h assigned and 3.75h from November).
• Brian May did 10h (out of 10h assigned).
• Chris Lamb did 16.5h (out of 16.5h assigned).
• Emilio Pozuelo Monfort did 16.5h (out of 16.5h assigned).
• Hugo Lefeuvre did 12h (out of 16.5h assigned), thus carrying over 4.5h to January.
• Markus Koschany did 16.5h (out of 16.5h assigned).
• Mike Gabriel did 15h (out of 15h assigned).
• Ola Lundqvist did 5.5h (out of 8h assigned, so he gave 3.5h back to the pool).
• Roberto C. Sánchez did 16.5h (out of 16.5h assigned).
• Sylvain Beucler did 16.5h (out of 16.5h assigned).
• Thorsten Alteholz did 16.5h (out of 16.5h assigned).
• Utkarsh Gupta did 16.5h (out of 16.5h assigned).

Evolution of the situation

Though December was as quiet as to be expected due to the holiday season, the usual amount of security updates were still released by our contributors.
We currently have 59 LTS sponsors each month sponsoring 219h. Still, as always we are welcoming new LTS sponsors!

The security tracker currently lists 34 packages with a known CVE and the dla-needed.txt file has 33 packages needing an update.

Thanks to our sponsors

New sponsors are in bold.

• Platinum sponsors:
• • TOSHIBA (for 52 months)
  • GitHub (for 42 months)
  • Civil Infrastructure Platform (CIP) (for 20 months)
• Gold sponsors:
• • Blablacar (for 67 months)
  • Roche Diagnostics International AG (for 63 months)
  • Linode (for 57 months)
  • Babiel GmbH (for 46 months)
  • Plat'Home (for 45 months)
  • University of Oxford
• Silver sponsors:
• • The Positive Internet Company (for 68 months)
  • Domeneshop AS (for 67 months)
  • Nantes Métropole (for 61 months)
  • Dalenys (for 57 months)
  • Univention GmbH (for 53 months)
  • Université Jean Monnet de St Etienne (for 53 months)
  • Ribbon Communications, Inc. (for 47 months)
  • Exonet B.V. (for 36 months)
  • Leibniz Rechenzentrum (for 30 months)
  • CINECA (for 20 months)
  • Ministère de l'Europe et des Affaires Étrangères (for 14 months)
  • Cloudways Ltd (for 3 months)
  • Dinahosting SL
• Bronze sponsors:
• • Seznam.cz, a.s. (for 68 months)
  • Evolix (for 67 months)
  • MyTux (for 67 months)
  • Linuxhotel GmbH (for 65 months)
  • Intevation GmbH (for 64 months)
  • Daevel SARL (for 63 months)
  • Bitfolk LTD (for 62 months)
  • Megaspace Internet Services GmbH (for 62 months)
  • Greenbone Networks GmbH (for 61 months)
  • NUMLOG (for 61 months)
  • WinGo AG (for 60 months)
  • Ecole Centrale de Nantes - LHEEA (for 57 months)
  • Sig-I/O (for 54 months)
  • Entr'ouvert (for 52 months)
  • Adfinis SyGroup AG (for 49 months)
  • Tesorion (for 44 months)
  • GNI MEDIA (for 43 months)
  • Laboratoire LEGI - UMR 5519 / CNRS (for 43 months)
  • Bearstech (for 35 months)
  • LiHAS (for 35 months)
  • People Doc (for 31 months)
  • Catalyst IT Ltd (for 29 months)
  • Supagro (for 25 months)
  • Demarcq SAS (for 23 months)
  • TrapX Security (for 20 months)
  • Université Grenoble Alpes (for 10 months)
  • TouchWeb SAS

No comment | Liked this article? Click here. | My blog is Flattr-enabled.

23 Jan 2020 6:19pm GMT

In the past decade, video has become the most ubiquitous method of communication on the Web. Video clips are used for pretty much anything, from short software tutorials to hours-long live online gaming streaming. In some cases, the use of "moving pictures" might not be the best communication medium, but there is no denying the popularity of the video in everyday life.

This makes video editing software quite practical, for techies and ordinary people alike. If you require functionality that goes beyond the built-in features in whatever application you may be using, then you will want dedicated video editing tools. Let's have a look at some rather nifty software that can turn your raw footage into elegant cinematographic cuts.

ShotCut

We have already seen ShotCut in action - as part of the tutorial on how to make compelling videos. There, we went through the linear process of a movie creation, from capture to audio manipulation, cover art styling and subtitles, to the final cut rendering.

In the tutorial, we used ShotCut to assemble the different media clips and create the for-audiences version of our project. ShotCut has an impressive list of capabilities, including multiple tracks, transitions and effects, live preview, 4K resolution support, and can natively play a wide range of audio and video formats. You can also use screen, webcam and audio capture, as well as network stream playback. Lastly, ShotCut also has a simple interface, and it's relatively easy to use.

Kdenlive

Another option for video editing is Kdenlive, developed by the KDE community. It's a free, open-source editor, and offers native support for a large number of formats, multiple tracks, effects, transitions, title creator, audio and video scopes, and live preview. You can also download additional render profiles and title templates directly from the application's interface, which make the user experience more streamlined.

Kdenlive also features hardware-accelerated playback - but not rendering with the default version of MLT available; however you can use multithreading to shorten the time it takes to create the final video cut. You can also live capture video from the webcam and the screen, as well as audio from detected devices.

OBS Studio

OBS Studio is software designed for capturing, compositing, encoding, recording, and streaming video content. You can capture content from a range of audio-video sources, including peripherals like gaming platforms, webcam, screen or individual applications, and others. From version 23.0.0 onwards, the snap also comes with support for nvenc and VAAPI hardware accelerated GPU encoding - which can greatly help speed up any required processing or rendering.

The application comes with lots of useful features, including per-source filters and mixing, an unlimited number of scenes, scene transitions, scene preview, and multiview - the ability to see up to eight scenes at the same time. The usage is model slightly less intuitive than say ShotCut or Kdenlive, but OBS Studio serves a somewhat different purpose, primarily live capture and streaming.

Ffmpeg

We have briefly mentioned ffmpeg in the linked tutorial, but it is a powerful, versatile tool, and it is often used as the backend video and audio processing engine by many different applications. Sometimes, ffmpeg is embedded in other software. You can always use it in standalone fashion, with the only "downside" being the command-line nature.

You do need to be somewhat familiar with the basic concepts of media processing, and often, you will need to make changes without seeing a preview first. But if you're comfortable with these pre-conditions, ffmpeg is a trusted, reliable workhorse. The command-line nature allows you to include ffmpeg commands in scripts or scheduled tasks, so you can process media files when you're away from the keyboard, or even remotely.

Stream mapping:
  Stream #0:0 -> #0:0 (copy)
  Stream #0:2 -> #0:1 (ac3 (native) -> mp3 (libmp3lame))
Press [q] to stop, [?] for help
Output #0, mp4, to 'bbs-tc.mp4':
  Metadata:
    major_brand     : isom
    minor_version   : 1
    compatible_brands: isomavc1
    composer        : Sacha Goedegebure
    title           : Big Buck Bunny, Sunflower version
    artist          : Blender Foundation 2008, Janus Bager Kristensen 2013
    comment         : Creative Commons Attribution 3.0 - http://bbb3d.renderfarming.net
    genre           : Animation
    encoder         : Lavf57.83.100
    Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], q=2-31, 2998 kb/s, 30 fps, 30 tbr, 30k tbn, 30k tbc (default)
    Metadata:
      creation_time   : 2013-12-16T17:44:39.000000Z
      handler_name    : GPAC ISO Video Handler
    Stream #0:1(und): Audio: mp3 (libmp3lame) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 192 kb/s (default)
    Metadata:
      creation_time   : 2013-12-16T17:44:42.000000Z
      handler_name    : GPAC ISO Audio Handler
      encoder         : Lavc57.107.100 libmp3lame
    Side data:
      audio service type: main

frame=19036 fps=1196 q=-1.0 Lsize=  247662kB time=00:10:34.50 bitrate=3197.6kbits/s speed=39.8x
video:232274kB audio:14864kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.21252

Sample output from ffmpeg.

Vidcutter

This application does as its name says - it can be used to cut longer video files into smaller clips, but then, it can also join smaller clips into as longer production. Quite handy if you have lengthy video recordings, and you only need small (relevant) portions. It does not do any transcoding, so the actual cut-and-join actions are fast.

Handbrake

Back in mid-2000s, Handbrake rose to prominence as a handy [sic], capable video transcoder, which could be used to convert DVD content, allowing users to keep (smaller) backups of their movie library. Since, it has grown and evolved, and works with a wide range of media formats.

Handbrake supports hardware acceleration, batch conversion, and by default, can use pretty much any DRM-free format. You can output your media to MP4 or MKV containers, encoded as H.264, H.265, VP8, VP9 for video, Flac, Vorbis, MP3, AC3 for audio, and then some.

Summary

If you require more-than-basic video processing available in this or that application, there's a range of editors available for Linux, with some rather impressive, high-quality features. Sometimes, getting started can be intimidating, and often, there can be no shortcuts; if you want to create an impressive video production, you will have to roll up your sleeves. Luckily, the software listed here can help you achieve that goal. Most of the applications do have a friendly interface and reasonably intuitive workflow, which are critical for the first few steps in your media journey.

We appreciate feedback, so if you have any comments or suggestions, please join the forum for a discussion.

Photo by Sam McGhee on Unsplash.

23 Jan 2020 10:12am GMT

Our favorite Disco Dingo, Ubuntu Studio 19.04, has reached end-of-life and will no longer receive any updates. If you have not yet upgraded, please do so now or forever lose the ability to upgrade! Ubuntu Studio 20.04 LTS is scheduled for April of 2020. The transition from 19.10 to 20.04... Continue reading

23 Jan 2020 12:00am GMT

For mission-critical applications, security, reliability, and efficiency are essential. Linux excels in these areas, which is why it has become a highly popular platform for supporting key enterprise software. And for businesses looking to push the security and performance of their Linux-based applications even further, the next step is enterprise server computing.

Enterprise servers offer secure and robust platforms for mission-critical workloads - however, it has historically been difficult to migrate Linux applications from x86 architectures to the IBM Z architecture. IBM and Canonical have worked together to solve this problem by porting Ubuntu to work on both IBM Z and IBM LinuxONE enterprise servers - including the recently released IBM z15 and LinuxONE III.

With Ubuntu on IBM Z and LinuxONE, users can leverage the same tools and languages on IBM Z as they do on all of their other Ubuntu systems. Not only does this provide businesses with a smooth migration path, it also enables developers to go from the desktop to a highly secure and reliable cloud with a seamless, agile working environment. Typical workloads include databases with sensitive personal information, as well as new solutions such as blockchain and digital asset custody.

Why migrate to Ubuntu on IBM Z and LinuxONE?

IBM Z and LinuxONE servers offer a range of benefits over x86 systems that make them uniquely suited for running mission-critical Linux workloads:

Security: Following the introduction of GDPR and in the wake of numerous high-profile breaches, it has never been more important to protect and encrypt data - especially customers' personal information. In the past, most companies have relied on software encryption, but these solutions can carry a considerable overhead. Because software encryption takes time, users must decide which data to encrypt, creating a risk that some important information might be missed.

IBM Z, on the other hand, supports hardware encryption which is included on every processor chip. Thanks to the speed of hardware encryption, it is completely viable for a business to encrypt ALL of its data - reducing risk, saving time, and making it easy to demonstrate regulatory compliance. What's more, crypto keys can be stored in tamper-responsive Hardware Security Modules, where they are robustly protected if a bad actor attempts to gain access.

IBM Z and LinuxONE servers running Ubuntu can also offer a secure environment for executing applications. Once prepared and launched, these apps and their data are protected and cannot be accessed other than through the applications - not even by sysadmins.

Agility: Running Ubuntu on IBM Z and LinuxONE provides developers with a consistent working environment from desktop to cloud. This consistency - with the same look and feel, tools, and libraries across platforms - empowers users to work more productively, accelerating development timelines.

Cloud capabilities at memory speed: With an enterprise server, organisations can deploy cloud-based applications on the same system where their data is already located. By eliminating the need to connect to an offsite, online cloud, these applications can access data far more securely and quickly.

Scalability: Public clouds and other x86 systems typically scale horizontally. That is to say, they scale out to support larger workloads through the addition of extra servers. This approach offers excellent flexibility, but with databases shared across multiple systems and with network delays between nodes, problems can arise for mission-critical databases that need to be always up-to-date and consistent.

While IBM Z can deliver horizontal scalability through virtualisation, it also offers vertical scalability for large databases and applications. Rather than adding new machines, vertical scalability enables businesses to scale up by committing additional resources from the existing hardware. Keeping everything on the same machine cuts complexity and ensures that there is no network delay, which is invaluable in situations where databases need to be in-sync at all times and delivering a single source of truth.

Reliability: For businesses across industries, it is becoming more and more important to have applications available 24/7. IBM Z architecture is designed for continuous service delivery. It offers 99.999% or greater availability, and sophisticated disaster recovery concepts minimise the duration and impact of downtime.

Overcoming the traditional barriers to mainframe migration

In the past, moving Linux workloads from x86 to IBM Z has sometimes been a daunting prospect. The need to recompile applications and hire mainframe specialists was often enough to deter organisations from migrating. Ubuntu on IBM Z and LinuxONE takes the complexity out of the process by enabling businesses to move from Linux to Linux.

Applications written in interpreted languages such as Java or Python are especially easy to migrate, as they can utilise the same source code on IBM Z as they do on x86 systems simply by changing interpreter. IBM has already ported a large number of open source infrastructure components and languages to IBM Z - including Go, Swift, Python, and MongoDB, to name a few - and moving to the IBM Z and LinuxONE is only getting easier as more tools continue to be made available.

Similarly, employee skills are largely transferable between x86 and IBM Z, since users will still be working in a familiar Ubuntu environment. Getting the most out of IBM Z only requires specialist expertise at set-up, and assistance is readily available from IBM and its business partners.

Case study: Digital Asset Custody Services (DACS)

With digital asset technology rapidly becoming mainstream, DACS saw a gap in the market for a highly secure, convenient solution for digital asset transactions and data. The startup set out to build a new platform that would enable corporations and individuals to store and transfer digital assets securely - without the delays inherent in existing, cold storage options.

DACS worked with IBM to develop the new platform, hosted on IBM LinuxONE servers running Ubuntu. Leveraging IBM Crypto Express 6S Hardware Security Module for pervasive encryption of all application data, as well as IBM Secure Service Container software to provide a secure computing environment, the IBM LinuxONE servers running Ubuntu enable DACS to deliver end-to-end security without compromising customer convenience.

To learn more about the technical side of running Ubuntu on IBM enterprise servers, check out Elizabeth K. Joseph's blog post, where she takes a detailed look at Ubuntu on the new IBM LinuxONE III. And, sign up for our upcoming webinar, "How to protect your data, applications, cryptography and OS - 100% of the time".

<Register for webinar>

22 Jan 2020 8:28pm GMT

Ubuntu Studio has had the same website design for nearly 9 years. Today, that changed. We were approached by Shinta from Playmain, asking if they could contribute to the project by designing a new website theme for us. Today, after months of correspondence and collaboration, we are proud to unveil... Continue reading

21 Jan 2020 6:48pm GMT

Welcome to the Ubuntu Weekly Newsletter, Issue 614 for the week of January 12 - 18, 2020. The full version of this issue is available here.

In this issue we cover:

• Ubuntu Stats
• Hot in Support
• LoCo Events
• Mir 1.7.0 Release
• Plasma 5.18 LTS Beta (5.17.90) Available for Testing
• Other Community News
• Canonical News
• In the Blogosphere
• Other Articles of Interest
• Featured Audio and Video
• Meeting Reports
• Upcoming Meetings and Events
• Updates and Security for 16.04, 18.04, 19.04 and 19.10
• And much more!

The Ubuntu Weekly Newsletter is brought to you by:

• Krytarik
• Bashing-om
• Chris Guiver
• Wild Man
• And many others

If you have a story idea for the Weekly Newsletter, join the Ubuntu News Team mailing list and submit it. Ideas can also be added to the wiki!

Except where otherwise noted, this issue of the Ubuntu Weekly Newsletter is licensed under a Creative Commons Attribution ShareAlike 3.0 License

20 Jan 2020 10:40pm GMT

I was idly musing about number sequences, and the Lychrel algorithm. If you don't know about this, there's a good Numberphile video on it: basically, take any number, reverse it, add the two, and if you get a palindrome stop, and if you don't, keep doing it. So start with, say, 57, reverse to get 75, add them to get 57+75=132, which isn't a palindrome, so do it again; reverse 132 to get 231, add to get 132+231=363, and that's a palindrome, so stop. There are a bunch of interesting questions that can be asked about this process (which James Grime goes into in the video), among which are: does this always terminate? What's the longest chain before termination? And so on. 196 famously hasn't terminated so far and it's been tried for several billion iterations.

Anyway, I was thinking about another such iterative process. Take a number, express it in words, then add up the values of all the letters in the words, and do it again. So 1 becomes ONE, and ONE is 15, 14, 5 (O is the fifteenth letter of the alphabet, N the fourteenth, and so on), so we add 15+14+5 to get 34, which becomes THIRTY FOUR, and so on. (We skip spaces and dashes; just the letters.)

Take a complete example: let's start with 4.

• 4 -> FOUR -> 6+15+21+18 = 60
• 60 -> SIXTY -> 19+9+24+20+25 = 97
• 97 -> NINETY-SEVEN -> 14+9+14+5+20+25+19+5+22+5+14 = 152
• 152 -> ONE HUNDRED AND FIFTY-TWO -> 15+14+5+8+21+14+4+18+5+4+1+14+4+6+9+6+20+25+20+23+15 = 251
• 251 -> TWO HUNDRED AND FIFTY-ONE -> 20+23+15+8+21+14+4+18+5+4+1+14+4+6+9+6+20+25+15+14+5 = 251

and 251 is a fixed point: it becomes itself. So we stop there, because we're now in an infinite loop.

Do all numbers eventually go into a loop? Do all numbers go into the same loop - that is, do they all end up at 251?

It's hard to tell. (Well, it's hard to tell for me. Some of you may see some easy way to prove this, in which case do let me know.) Me being me, I wrote a little Python programme to test this out (helped immeasurably by the Python 3 num2words library). As I discovered before, if you're trying to pick out patterns in a big graph of numbers which all link to one another, it's a lot easier to have graphviz draw you pretty pictures, so that's what I did.

I've run numbers up to 5000 or so (after that I got a bit bored waiting for answers; it's not recreational mathematics if I have to wait around, it's a job for which I'm not getting paid). And it looks like numbers settle out into a tiny island which ends up at 251, a little island which ends up at 285, and a massive island which ends up at 259, all of which become themselves¹. (You can see an image of the first 500 numbers and how they end up; extending that up to 5000 just makes the islands larger, it doesn't create new islands… and the diagrams either get rather unwieldy or they get really big and they're hard to display.²)

I have a theory that (a) yes all numbers end up in a fixed point and (b) there probably aren't any more fixed points. Warning: dubious mathematical assertions lie ahead.

There can't be that many numbers that encode to themselves. This is both because I've run it up to 5000 and there aren't, and because it just seems kinda unlikely and coincidental. So, we assume that the fixed points we have are most or all of the fixed points available. Now, every number has to end up somewhere; the process can't just keep going forever. So, if you keep generating numbers, you're pretty likely at some point to hit a number you've already hit, which ends up at one of the fixed points. And finally, the numbers-to-words process doesn't grow as fast as actual numbers do. Once you've got over a certain limit, you'll pretty much always end up generating a number smaller than oneself in the next iteration. The reason I think this is that adding more to numbers doesn't make their word lengths all that much longer. Take, for example, the longest number (in words) up to 100,000, which is (among others) 73,373, or seventy-three thousand, three hundred and seventy-three. This is 47 characters long. Even if they were all Z, which they aren't, it'd generate 47×26=1222, which is way less than 73,373. And adding lots more doesn't help much: if we add a million to that number, we put one million on the front of it, which is only another 10 characters, or a maximum added value of 260. There's no actual ceiling - numbers in words still grow without limit as the number itself grows - but it doesn't grow anywhere near as fast as the number itself does. So the numbers generally get smaller as they iterate, until they get down below four hundred or so… and all of those numbers terminate in one of the three fixed points already outlined. So I think that all numbers will terminate thus.

The obvious flaw with this argument is that it ought to apply to the reverse-and-add process above too and it doesn't for 196 (and some others). So it's possible that my approach will also make a Lychrel-ish number that may not terminate, but I don't think it will; the argument above seems compelling.

You might be thinking: bloody English imperialist! What about les nombres, eh? Or die Zahlen? Did you check those? Mais oui, I checked (nice one num2words for supporting a zillion languages!) Same thing. There are different fixed points (French has one big island until 177, a very small island to 232, a 258, 436 pair, and 222 which encodes to itself and nothing else encodes to it, for example.Not quite: see the update at the end. Nothing changes about the maths, though. Images of French and German are available, and you can of course use the Python 3 script to make your own; run it as python3 numwords.py no for Norwegian, etc.) You may also be thinking "what about American English, eh? 101 is ONE HUNDRED ONE, not ONE HUNDRED AND ONE." I have not tested this, partially because I think the above argument should still hold for it, partially because num2words doesn't support it, and partially because that's what you get for throwing a bunch of perfectly good tea into the ocean, but I don't think it'd be hard to verify if someone wants to try it.

No earth-shattering revelations here, not that it matters anyway because I'm 43 and you can only win a Fields Medal if you're under forty, but this was a fun little diversion.

Update: Minirop pointed out on Twitter that my code wasn't correctly highlighting the "end" of a chain, which indeed it was not. I've poked the code, and the diagrams, to do this better; it's apparent that both French and German have most numbers end up in a fairy large loop, rather than at one specific number. I don't think this alters my argument for why this is likely to happen for all numbers (because a loop of numbers which all encode to one another is about as rare as a single number which encodes to itself, I'd guess), but maybe I haven't thought about it enough!

1. Well, 285 is part of a 285, 267, 313, 248, 284, 285 loop. ↩
2. This is also why the graphs use neato, which is much less pleasing a layout for this than the "tree"-style layout of dot, because the dot images end up being 32,767 pixels across and all is a disaster. ↩

19 Jan 2020 10:02pm GMT

Com o objectivo constante de inovar vamos hoje, dia em que gravamos o episódio 74 do nosso podcast preferido, permitir a todos os que lerem esta publicação a tempo - e tiverem disponibilidade - poder assistir à gravação do PUP.

No futuro, este será um privilégio da patronagem (é $1, deixem-se de coisas!) mas por enquanto todos vão poder fazer parte.

Queremos com esta iniciativa atingir 3 objectivos:

• Dar mais amor aos nossos patronos;
• Aumentar o número de seguidores que temos no yt;
• Aumentar o número de patronos.

Se, nesta altura, continuas com vontade de assistir, basta abrires esta ligação uns minutos antes das 22.00:
https://www.youtube.com/watch?v=OBer6DroddY

19 Jan 2020 4:54pm GMT

In someone else's project (which they'll doubtless tell you about themselves when it's done) I needed a tiny Python templating engine. That is: I wanted to be able to say, here is a template string, please substitute a bunch of variables into it. Now, Python already does this, in about thirty different ways, and str.format or string.Template do most of it as built-in.

str.format works like this:

"My name is {name} and I am {age} years old".format(name="Stuart", age=43)

and string.Template like this:

t=string.Template(
    "My name is $name and I am $age years old"
    ).safe_substitute(name="Stuart", age=43)

Both of which are pretty OK.

However, what they're missing is loops; having more than one of a thing in your template, and looping over a list, substituting it each time. Every even fractionally-more-featureful templating system has this, whether Mustache or Jinja or whatever, of course, but I didn't want another dependency. All I needed was str.format but with loops. So, I thought, I'll write one, in about four lines of code, so I can just drop the function in to my Python file and then I'm good.

def LoopTemplate(s, ctx):
    def loophandler(m):
        md = m.groupdict()
        return "".join([LoopTemplate(md["content"], val)
                        for val in ctx[md["var"]]])
    return re.sub(r"\{loop (?P<var>[^}]+)\}(?P<content>.*?)\{endloop\}",
                  loophandler, s, flags=re.DOTALL).format(**ctx)

And lo, twas so. So I can now do

LoopTemplate(
    "I am {name} and my imps' names are: {loop imps}{name}{endloop}",
    {
        "name": "Stuart",
        "imps": [
            {"name": "Pyweazle"}, {"name": "Grimthacket"}, {"name": "Hardebon"}
        ]
    }
)

and it all works. Not revolutionary, of course, but I was mildly pleased with myself.

Much internal debate about whether loophandler() should have been a lambda, but I eventually decided it was more confusing that way, on the grounds that it was confusing me and I knew what it was meant to be doing.

A brief explanation: re.sub lets you pass a function as the thing to replace with, rather than just a string. So we find all examples of {loop something}...{endloop} in the passed string, look up something in the "context", or the dict of substitution variables you passed to LoopTemplate, and then we call LoopTemplate again, once per item in something (which is expected to be a list), and pass it the ... as its string and the next item in something as its context. So it all works. Of course, there's no error handling or anything - if something isn't present in the context, or if it's not a list, or if you stray in any other way from the path of righteousness, it'll incomprehensibly blow up. So don't do that.

19 Jan 2020 10:30am GMT

Are you using Kubuntu 19.10 Eoan Ermine, our current Stable release? Or are you already running our development builds of the upcoming 20.04 LTS Focal Fossa?

We currently have Plasma 5.17.90 (Plasma 5.18 Beta) available in our Beta PPA for Kubuntu 19.10.

The 5.18 beta is also available in the main Ubuntu archive for the 20.04 development release, and can be found on our daily ISO images.

This is a Beta Plasma release, so testers should be aware that bugs and issues may exist.

If you are prepared to test, then…..

For 19.10 add the PPA and then upgrade

sudo add-apt-repository ppa:kubuntu-ppa/beta && sudo apt update && sudo apt full-upgrade -y

Then reboot. If you cannot reboot from the application launcher,

systemctl reboot

from the terminal.

In case of issues, testers should be prepare to use ppa-purge to remove the PPA and revert/downgrade packages.

Kubuntu is part of the KDE community, so this testing will benefit both Kubuntu as well as upstream KDE Plasma software, which is used by many other distributions too.

• If you believe you might have found a packaging bug, you can use a launchpad.net to post testing feedback to the Kubuntu team as a bug, or give feedback on IRC [1], Telegram [2] or mailing lists [3].
• If you believe you have found a bug in the underlying software, then bugs.kde.org is the best place to file your bug report.

Please review the release announcement and changelog.

[Test Case]

* General tests:
- Does plasma desktop start as normal with no apparent regressions over 5.16 or 5.17?
- General workflow - testers should carry out their normal tasks, using the plasma features they normally do, and test common subsystems such as audio, settings changes, compositing, desktop affects, suspend etc.

* Specific tests:
- Check the changelog:
- Identify items with front/user facing changes capable of specific testing. e.g. "clock combobox instead of tri-state checkbox for 12/24 hour display."
- Test the 'fixed' functionality or 'new' feature.

Testing involves some technical set up to do, so while you do not need to be a highly advanced K/Ubuntu user, some proficiently in apt-based package management is advisable.

Testing is very important to the quality of the software Ubuntu and Kubuntu developers package and release.

We need your help to get this important beta release in shape for Kubuntu and the KDE community as a whole.

Thanks!

Please stop by the Kubuntu-devel IRC channel or Telegram group if you need clarification of any of the steps to follow.

[1] - irc://irc.freenode.net/kubuntu-devel
[2] - https://t.me/kubuntu_support
[3] - https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

17 Jan 2020 9:48am GMT

Episódio 73 - WSL por Nuno do Carmo (parte 1). 2 Ubuntus e 1 Windows entram num bar e… Isto podia ser o início de mais uma anedota, mas o que realmente aconteceu foi mais 2 Ubuntus e 1 Windows entram num podcast e começam a falar sem parar sobre WSL, e não só, de tal maneira que a ocnversa ficou a meio e terá de ser cotinuada no próximo episódio. Já sabem: oiçam, comentem e partilhem!

• https://meta.wikimedia.org/wiki/WikiCon_Portugal
• https://www.humblebundle.com/books/python-machine-learning-packt-books?partner=PUP
• https://www.humblebundle.com/books/holiday-by-makecation-family-projects-books?partner=PUP
• https://stackoverflow.com/questions/56979849/dbeaver-ssh-tunnel-invalid-private-key
• https://fosdem.org
• https://github.com/PixelsCamp/talks
• https://pixels.camp/

Apoios

Este episódio foi produzido e editado por Alexandre Carrapiço (Thunderclaws Studios - captação, produção, edição, mistura e masterização de som) contacto: thunderclawstudiosPT-arroba-gmail.com.

Podem apoiar o podcast usando os links de afiliados do Humble Bundle, porque ao usarem esses links para fazer uma compra, uma parte do valor que pagam reverte a favor do Podcast Ubuntu Portugal.
E podem obter tudo isso com 15 dólares ou diferentes partes dependendo de pagarem 1, ou 8.
Achamos que isto vale bem mais do que 15 dólares, pelo que se puderem paguem mais um pouco mais visto que têm a opção de pagar o quanto quiserem.

Se estiverem interessados em outros bundles não listados nas notas usem o link https://www.humblebundle.com/?partner=PUP e vão estar também a apoiar-nos.

Atribuição e licenças

A música do genérico é: "Won't see it comin' (Feat Aequality & N'sorte d'autruche)", por Alpha Hydrae e está licenciada nos termos da [CC0 1.0 Universal License](https://creativecommons.org/publicdomain/zero/1.0/).

Este episódio e a imagem utilizada estão licenciados nos termos da licença: Attribution-NonCommercial-NoDerivatives 4.0 International (CC BY-NC-ND 4.0), cujo texto integral pode ser lido aqui. Estamos abertos a licenciar para permitir outros tipos de utilização, contactem-nos para validação e autorização.

16 Jan 2020 10:45pm GMT

KUserFeedback is a framework for collecting user feedback for applications via telemetry and surveys.

The library comes with an accompanying control and result UI tool.

https://download.kde.org/unstable/kuserfeedback/

Signed by Jonathan Riddell <jr@jriddell.org> 2D1D5B0588357787DE9EE225EC94D18F7F05997E

KUserFeedback as it will be used in Plasma 5.18 LTS

15 Jan 2020 4:15pm GMT

Some time ago, there was a thread on debian-devel where we discussed how to make Qt packages work on hardware that supports OpenGL ES, but not the desktop OpenGL.

My first proposal was to switch to OpenGL ES by default on ARM64, as that is the main affected architecture. After a lengthy discussion, it was decided to ship two versions of Qt packages instead, to support more (OpenGL variant, architecture) configurations.

So now I am announcing that we finally have the versions of Qt GUI and Qt Quick libraries that are built against OpenGL ES, and the release team helped us to rebuild the archive for compatibility with them. These packages are not co-installable together with the regular (desktop OpenGL) Qt packages, as they provide the same set of shared libraries. So most packages now have an alternative dependency like libqt5gui5 (>= 5.x) | libqt5gui5-gles (>= 5.x). Packages get such a dependency automatically if they are using ${shlibs:Depends}.

These Qt packages will be mostly needed by ARM64 users, however they may be also useful on other architectures too. Note that armel and armhf are not affected, because there Qt was built against OpenGL ES from the very beginning. So far there are no plans to make two versions of Qt on these architectures, however we are open to bug reports.

To try that on your system (running Bullseye or Sid), just run this command:

# apt install libqt5gui5-gles libqt5quick5-gles

The other Qt submodule packages do not need a second variant, because they do not use any OpenGL API directly. Most of the Qt applications are installable with these packages. At the moment, Plasma is not installable because plasma-desktop FTBFS, but that will be fixed sooner or later.

One major missing thing is PyQt5. It is linking against some Qt helper functions that only exist for desktop OpenGL build, so we will probably need to build a special version of PyQt5 for OpenGL ES.

If you want to use any OpenGL ES specific API in your package, build it against qtbase5-gles-dev package instead of qtbase5-dev. There is no qtdeclarative5-gles-dev so far, however if you need it, please let us know.

In case you have any questions, please feel free to file a bug against one of the new packages, or contact us at the pkg-kde-talk mailing list.

15 Jan 2020 2:55pm GMT

https://zanshin.kde.org/2020/01/14/zanshin-0.5.71/

14 Jan 2020 3:37pm GMT

Kubuntu 19.04 Disco Dingo was released on April 18, 2019 with 9 months support. As of January 23, 2020, 19.04 reaches 'end of life'. No more package updates will be accepted to 19.04, and it will be archived to old-releases.ubuntu.com in the coming weeks.

The official end of life announcement for Ubuntu as a whole can be found here [1].

Kubuntu 19.10 Eoan Ermine continues to be supported, receiving security and high-impact bugfix updates until July 2020.

Users of 19.04 can follow the Kubuntu 19.04 to 19.10 Upgrade [2] instructions.

Should for some reason your upgrade be delayed, and you find that the 18.10 repositories have been archived to old-releases.ubuntu.com, instructions to perform a EOL Upgrade can be found on the Ubuntu wiki [3].

Thank you for using Kubuntu 19.04 Disco Dingo.

The Kubuntu team.

[1] - https://lists.ubuntu.com/archives/ubuntu-announce/2020-January/000252.html
[2] - https://help.ubuntu.com/community/EoanUpgrades/Kubuntu
[3] - https://help.ubuntu.com/community/EOLUpgrades

12 Jan 2020 11:23pm GMT