Wednesday, 1 April 2026

Re: New naming schema proposal for reverted upstream release versions

On Wed, Apr 1, 2026 at 1:25 PM Benjamin Drung <bdrung@ubuntu.com> wrote: > > On Wed, 2026-04-01 at 18:50 +0100, Robie Basak wrote: > > On Wed, Apr 01, 2026 at 06:34:36PM +0200, Benjamin Drung wrote: > > > * `+actually` > > > * `+definitely` > > > * `+for.sure` > > > > If you've had to go this far then perhaps you should take a step back. > > Anyone who gets as far as having to have done as many as three whole > > reverts should probably display some humility and not be so committal as > > to continue down this path in the main Ubuntu archive with so much > > certainty that their next upload will be "right _this_ time". > > > > I therefore suggest that the next upload should display that humility > > with: > > > > * `+maybe` > > One try for being humble might not be enough. So how about adding > `+hopefully` before `+maybe`? > > > If that still doesn't work, then perhaps it's OK to continue as you > > suggest: > > > > > * `+really` > > > * `+very.definitely` > > > * `+very.very.definitely` > > > * `+what.i.meant` > > > > Robie Frankly I think this is not inventive enough, and there aren't enough options. I think one should ask ChatGPT if a seahorse emoji exists [1], and use the resulting output as inspiration for version numbers to use. This should provide a sufficient number of values. -- Aaron [1] https://www.youtube.com/watch?v=W2xZxYaGlfs > -- > Benjamin Drung > Debian & Ubuntu Developer > > -- > 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

Posted by at

Re: New naming schema proposal for reverted upstream release versions

On Wed, 2026-04-01 at 18:50 +0100, Robie Basak wrote: > On Wed, Apr 01, 2026 at 06:34:36PM +0200, Benjamin Drung wrote: > > * `+actually` > > * `+definitely` > > * `+for.sure` > > If you've had to go this far then perhaps you should take a step back. > Anyone who gets as far as having to have done as many as three whole > reverts should probably display some humility and not be so committal as > to continue down this path in the main Ubuntu archive with so much > certainty that their next upload will be "right _this_ time". > > I therefore suggest that the next upload should display that humility > with: > > * `+maybe` One try for being humble might not be enough. So how about adding `+hopefully` before `+maybe`? > If that still doesn't work, then perhaps it's OK to continue as you > suggest: > > > * `+really` > > * `+very.definitely` > > * `+very.very.definitely` > > * `+what.i.meant` > > Robie -- Benjamin Drung Debian & Ubuntu Developer -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel

Posted by at

Re: New naming schema proposal for reverted upstream release versions

On Wed, Apr 01, 2026 at 06:34:36PM +0200, Benjamin Drung wrote: > * `+actually` > * `+definitely` > * `+for.sure` If you've had to go this far then perhaps you should take a step back. Anyone who gets as far as having to have done as many as three whole reverts should probably display some humility and not be so committal as to continue down this path in the main Ubuntu archive with so much certainty that their next upload will be "right _this_ time". I therefore suggest that the next upload should display that humility with: * `+maybe` If that still doesn't work, then perhaps it's OK to continue as you suggest: > * `+really` > * `+very.definitely` > * `+very.very.definitely` > * `+what.i.meant` Robie -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel

Posted by at

New naming schema proposal for reverted upstream release versions

Hi everyone, I am cross-posting the discourse post https://discourse.ubuntu.com/t/new-naming-schema-proposal-for-reverted-upstream-release-versions/79589 Here is the raw markdown from the post: Picking a correct package version number can be quite complicated. The Ubuntu project documentation has a [very long page] (https://documentation.ubuntu.com/project/how-ubuntu-is-made/concepts/version-strings/) explaining probably all cases. The [Version: Undoing mistakes section] (https://documentation.ubuntu.com/project/how-ubuntu-is-made/concepts/version-strings/#version-undoing-mistakes) says: > In a very rare case where an upgrade to a new upstream version of a package caused major regression and the only way out is rolling back, the convention is to insert `+really` followed by the actual version number. Using `+really` helps undoing a mistake, but what should you do in case you have to undo a second mistake? Imagine you upgraded from `7.80+dfsg1-5` to `7.91+dfsg1-1`, but then revert back to `7.80+dfgs1` by using `7.91+dfsg1+really7.80+dfsg1-0ubuntu1`. Then you upgrade to `7.91` again using `7.91+dfsg1+really7.91+dfsg1-0ubuntu1`. Assume this was a mistake and you have to revert again. You could use `7.91+dfsg1+really7.91+dfsg1+really7.80+dfsg1-0ubuntu1`. This is a very long version number and hard to read. Today I propose to use more than one string besides `+really` to revert an upstream release version. Let's use following strings (in alphabetical order): * `+actually` * `+definitely` * `+for.sure` * `+really` * `+very.definitely` * `+very.very.definitely` * `+what.i.meant` So in case you have to revert multiple times, you can pick the next string in this list. Example: `7.91+dfsg1-1` -> `7.91+dfsg1+actually7.80+dfsg1-0ubuntu1` -> `7.91+dfsg1+definitely7.80+dfsg1-0ubuntu1` -> `7.91+dfsg1+for.sure7.80+dfsg1-0ubuntu1` -> `7.91+dfsg1+really7.80+dfsg1-0ubuntu1` and so on. Let's discuss this proposal before submitting a merge request for the Ubuntu project documentation. Which strings would you use and how many do you need? Are 7 strings enough? -- Benjamin Drung Debian & Ubuntu Developer -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel

Posted by at

Monday, 30 March 2026

Re: tchavadar - Application For PPU Rights for ROCm Package Set



On Mon, Mar 30, 2026 at 7:02 PM Talha Can Havadar via Devel-permissions <devel-permissions@lists.ubuntu.com> wrote:
Dear Ubuntu Developers,

Please let this be my official application announcement for the upload rights of the package set disclosed previously here: https://lists.ubuntu.com/archives/devel-permissions/2026-February/002946.html

Date: 2026/03/30

Thank you, Talha, for submitting this explicit request as it was formerly implied as a side effect of the package set application.
This allows me to directly reply with the results of yesterday's DMB meeting on March 30th

The DMB unanimously approved Talha's application - congratulations.
Welcome to the uploaders!

We also gave Talha many suggestions on what to look at next.
Good luck on your continued Ubuntu uploader Journey [1].

Establishing the new packageset [2] to  add you needs some special permissions, Robie will take that action and reply here once done.

As usual the full meeting log can be found in git [3].

(Yes, sorry Launchpad still fights scrapers and this can be hard to access, you might want to git clone https://git.launchpad.net/~developer-membership-board/+git/dmb-meeting-history if you want to follow the DMB activities)

 
Thank you for everything.

Best Regards

--
Canonical Logo

Talha Can Havadar

Software Engineer, Partner Engineering

Email:

talha.can.havadar@canonical.com


Location:

The Netherlands


canonical.com

ubuntu.com

We are hiring | Life at Canonical

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


--
Christian Ehrhardt
Director of Engineering, Ubuntu Server
Canonical Ltd
Posted by at

Friday, 27 March 2026

Second Resolute Raccoon test rebuild

The second test rebuild of Resolute Raccoon was started on March 20,
2026 for all architectures and all components. The rebuild is finished
for the main component on all architectures except riscv64, and still
running for universe and multiverse.

Results (please also look at the superseded builds) can be found at:

https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20260320-resolute-resolute.html

Additional build failures for packages in resolute-proposed (not yet
in Resolute) can be found at:

http://qa.ubuntuwire.com/ftbfs/

Please help with fixing the build failures.

There is also a test rebuild with GCC 16 as default. Resolute will
ship with GCC 15 as the default and GCC 16 as an optional compiler.
Please see:

https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20260320-resolute-gcc16-resolute.html

Happy equinox!
Graham

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

Posted by at

Thursday, 26 March 2026

Ubuntu 26.04 LTS (Resolute Raccoon) Beta released

The Ubuntu team is pleased to announce the Beta release of the Ubuntu
26.04 LTS Desktop, Server, WSL, and Cloud products.

26.04 LTS, codenamed "Resolute Raccoon", 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.

This Beta release includes images from not only the Ubuntu Desktop,
Server, WSL, and Cloud products, but also the Kubuntu, Lubuntu, Ubuntu
Budgie, Ubuntu Studio, Ubuntu Unity, and Xubuntu flavors.

The Beta images are known to be reasonably free of showstopper image
build or installer bugs, while representing a very recent snapshot of
26.04 LTS that should be representative of the features intended to ship
with the final release expected on April 23rd, 2026.

Ubuntu, Ubuntu Server, WSL, Cloud Images:
Resolute Beta includes updated versions of most of our core set of
packages, including a current 6.20 kernel, and much more.

To upgrade to Ubuntu 26.04 LTS Beta from Ubuntu 25.10 or Ubuntu 24.04 LTS,
follow these instructions:

https://documentation.ubuntu.com/desktop/en/latest/how-to/upgrade-ubuntu-desktop/

Download the Ubuntu 26.04 LTS Beta images from:

https://releases.ubuntu.com/26.04/ (Ubuntu, Ubuntu Server, and WSL on x86)

This Ubuntu Server image features the next generation Subiquity server
installer, bringing the comfortable live session and speedy install of
the Ubuntu Desktop to server users.

For addditional images, go to the following links:

https://cloud-images.ubuntu.com/daily/server/resolute/current/ (Cloud Images)
https://cdimage.ubuntu.com/releases/26.04/beta/ (Non-x86)
https://cdimage.ubuntu.com/netboot/26.04/ (Netboot)

We will include fixes in new images between now and release. Therefore,
consider daily cloud images from today or later (i.e. a serial of
20260325 or higher) Beta images. File bugs against the appropriate
packages or, failing that, the cloud-images project in Launchpad.

Read the full release notes for Ubuntu 26.04 LTS Beta at:

https://documentation.ubuntu.com/release-notes/26.04/

Kubuntu:
Kubuntu is the KDE based flavor of Ubuntu. It uses the Plasma desktop
and includes a wide selection of tools from the KDE project.

Download the Beta images from:
https://cdimage.ubuntu.com/kubuntu/releases/26.04/beta/

Lubuntu:
Lubuntu is a flavor of Ubuntu that uses the Lightweight Qt Desktop
Environment (LXQt). The project's goal is to provide a lightweight
yet functional Linux distribution based on a rock-solid Ubuntu base.

Download the Beta images from:
https://cdimage.ubuntu.com/lubuntu/releases/26.04/beta/

Ubuntu Budgie:
Ubuntu Budgie is community developed desktop, integrating Budgie
Desktop Environment with Ubuntu at its core.

Download the Beta images from:
https://cdimage.ubuntu.com/ubuntu-budgie/releases/26.04/beta/

Ubuntu Studio:
Ubuntu Studio is a flavor of Ubuntu that provides a full range of
multimedia content creation applications for each key workflow: audio,
graphics, video, photography, and publishing.

Download the Beta images from:
https://cdimage.ubuntu.com/ubuntustudio/releases/26.04/beta/

Ubuntu Unity:
Ubuntu Unity is a flavor of Ubuntu featuring the Unity7 desktop
environment.

Download the Beta images from:
https://cdimage.ubuntu.com/ubuntu-unity/releases/26.04/beta/

Xubuntu:
Xubuntu is a flavor of Ubuntu that comes with Xfce, which is a stable,
light, and configurable desktop environment.

Download the Beta images from:
https://cdimage.ubuntu.com/xubuntu/releases/26.04/beta/

For regular daily images of Ubuntu and all flavors, go to:
https://cdimage.ubuntu.com

Ubuntu is a full-featured Linux distribution for clients, servers and
clouds, 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 technical support is available from Canonical Limited and
hundreds of other companies around the world. For more information
about support, visit https://ubuntu.com/support

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

https://documentation.ubuntu.com/project/community/contribute/

Your comments, bug reports, patches, and suggestions really help us to
improve this and future releases of Ubuntu. Read the instructions at:

https://documentation.ubuntu.com/project/contributors/qa-and-testing/report-a-bug/

Find out more about Ubuntu and about this Beta release on our website,
Matrix channel, and Discourse.

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

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


On behalf of the Ubuntu Release Team,
Utkarsh Gupta

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

Posted by at
Subscribe to: Comments (Atom)