Language Selection

English French German Italian Portuguese Spanish

Bullseye freeze

Filed under
Debian

Bullseye is freezing! Yay! (And Trondheim is now below -10.)

It's too late for that kind of change now, but it would have been nice if plocate could have been default for bullseye...

It seems that since buster, there's an override in place to change its priority away from standard, and I haven't been able to find anyone who could tell me why. (It was known that it was request moved away from standard for cloud images, which makes a lot of sense, but not for desktop/server images.)

Read more

Debian 11 Freeze Begins

  • Debian 11 Freeze Begins, Debian 12 Might Reduce Focus On i386 Support

    The Debian 11 "Bullseye" build-essential freeze is now in effect with the release team no longer entertaining transition requests. Meanwhile, architecture support for Debian 12 is in early stages of discussion with a possible reduction in i386 support for that follow-on release.

    Debian 11.0 "Bullseye" will see its soft freeze for new packages begin on 12 February, the hard freeze beginning a month later on 12 March, and then the full freeze of Debian 12 to happen at some later point to be determined.

  • bits from the release team: bullseye freeze started and its architectures
    -----BEGIN PGP SIGNED MESSAGE-----
    Hash: SHA256
    
    Hi all,
    
    === bullseye Transition and (build-)essential freeze ===
    
    We're pleased to announce that the freeze for Debian 11 'bullseye' has
    begun. On January 12th we stopped accepting transition requests and we
    are working to complete the transitions in progress. We ask the
    maintainers of packages that are (transitively) part of
    (build-)essential to stop uploading those packages [1]. We remind
    everybody to stop uploading large or disruptive changes to unstable,
    from here on experimental is the place to do that.
    
    Further details of the freeze are available in the freeze policy [2].
    The freeze contains 3 more milestones:
    * 2021-02-12 - Milestone 2 - Soft Freeze
                   no new packages, delayed migration
    * 2021-03-12 - Milestone 3 - Hard Freeze - key packages and packages
                   without autopkgtests need a manual unblock for migration
    * TBA        - Milestone 4 - Full Freeze
                   all packages need a manual unblock for migration
    
    === RC bugs ===
    
    We are missing the Bug Squashing parties. We have the impression that in
    the current list of Release Critical bugs for bullseye [3] there are
    quite a few bugs that are relatively easy to fix by NMU and we normally
    don't see them this late in the cycle. Please everybody, we know the
    times are different, but with your help, we can keep this freeze short.
    
    === bullseye architectures ===
    
    We have decided that the architectures that will be part of the bullseye
    release are: amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el
    and s390x (i.e. the same we had for buster minus mips).
    
    There are some issues with a couple of the architectures, the number of
    porters being the main one. However, we realized that the call for
    porters was late and makes more sense at the start of the release cycle,
    instead of near the end. We intend to do the bookworm call soon after we
    release bullseye and architectures with too few porters will be dropped
    early (after sufficient warnings).
    
    One of the architectures at stake is i386, which we stopped waiving.
    We're interested in the discussion about i386 support in Debian that
    was going on recently and that will probably continue in one form or
    another. If the outcome requires changes to how we build some ports, the
    start of the bookworm release cycle is a good moment to try to get those
    in place.
    
    We're also interested in the proposal [4] to make it less troublesome
    for architectures to move between Release Architecture and Debian Ports,
    albeit we see that this mainly doesn't depend on us.
    
    === your packages ===
    
    Please take this opportunity to check packages are in their final shape
    and stay vigilant for release-critical bugs.
    
    On behalf of the Release Team,
    Paul
    
    [1]
    https://release.debian.org/bullseye/essential-and-build-essential.txt
    [2] https://release.debian.org/buster/freeze_policy.html
    [3] https://udd.debian.org/dev/bugs.cgi
    [4] https://lists.debian.org/debian-devel/2020/11/msg00381.html
    

Debian 'Bullseye' enters final phase before release

  • Debian 'Bullseye' enters final phase before release as team debates whether it will be last to work on i386 architecture

    Gevers also noted that support for the i386 architecture is no longer being waived. If a decision is made to drop it, he said, the start of the Bookworm cycle is a good moment to deal with any issues. "We're interested in the discussion about i386 support in Debian that was going on recently," he said.

    The discussion was kicked off by Debian contributor Andrew Cater, who questioned the future of i386. "There seems to be only one maintainer," he said. "No one has real UEFI hardware for i386 and it's becoming harder and harder to justify spending too much time on testing of the images as fewer and fewer machines can benefit from them."

    Although new PCs all support 64-bit architecture, 32-bit applications are common, and there are also embedded use cases. Many older PCs also remain in service. "i386 hardware is so numerous and widely spread that [the] tiny fraction of i386 users might be more users than half of our release architectures combined," claimed one comment to the thread.

    Studying data from a Debian telemetry package called Popularity Contest confirmed this. "There are an order of magnitude more people with i386 kernels (and thus presumably i386 hardware) than there are for every other non-amd64 release architecture combined. Further, there are more people with old i386 hardware than there are for any other arch," said another developer.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

digiKam 7.7.0 is released

After three months of active maintenance and another bug triage, the digiKam team is proud to present version 7.7.0 of its open source digital photo manager. See below the list of most important features coming with this release. Read more

Dilution and Misuse of the "Linux" Brand

Samsung, Red Hat to Work on Linux Drivers for Future Tech

The metaverse is expected to uproot system design as we know it, and Samsung is one of many hardware vendors re-imagining data center infrastructure in preparation for a parallel 3D world. Samsung is working on new memory technologies that provide faster bandwidth inside hardware for data to travel between CPUs, storage and other computing resources. The company also announced it was partnering with Red Hat to ensure these technologies have Linux compatibility. Read more

today's howtos

  • How to install go1.19beta on Ubuntu 22.04 – NextGenTips

    In this tutorial, we are going to explore how to install go on Ubuntu 22.04 Golang is an open-source programming language that is easy to learn and use. It is built-in concurrency and has a robust standard library. It is reliable, builds fast, and efficient software that scales fast. Its concurrency mechanisms make it easy to write programs that get the most out of multicore and networked machines, while its novel-type systems enable flexible and modular program constructions. Go compiles quickly to machine code and has the convenience of garbage collection and the power of run-time reflection. In this guide, we are going to learn how to install golang 1.19beta on Ubuntu 22.04. Go 1.19beta1 is not yet released. There is so much work in progress with all the documentation.

  • molecule test: failed to connect to bus in systemd container - openQA bites

    Ansible Molecule is a project to help you test your ansible roles. I’m using molecule for automatically testing the ansible roles of geekoops.

  • How To Install MongoDB on AlmaLinux 9 - idroot

    In this tutorial, we will show you how to install MongoDB on AlmaLinux 9. For those of you who didn’t know, MongoDB is a high-performance, highly scalable document-oriented NoSQL database. Unlike in SQL databases where data is stored in rows and columns inside tables, in MongoDB, data is structured in JSON-like format inside records which are referred to as documents. The open-source attribute of MongoDB as a database software makes it an ideal candidate for almost any database-related project. This article assumes you have at least basic knowledge of Linux, know how to use the shell, and most importantly, you host your site on your own VPS. The installation is quite simple and assumes you are running in the root account, if not you may need to add ‘sudo‘ to the commands to get root privileges. I will show you the step-by-step installation of the MongoDB NoSQL database on AlmaLinux 9. You can follow the same instructions for CentOS and Rocky Linux.

  • An introduction (and how-to) to Plugin Loader for the Steam Deck. - Invidious
  • Self-host a Ghost Blog With Traefik

    Ghost is a very popular open-source content management system. Started as an alternative to WordPress and it went on to become an alternative to Substack by focusing on membership and newsletter. The creators of Ghost offer managed Pro hosting but it may not fit everyone's budget. Alternatively, you can self-host it on your own cloud servers. On Linux handbook, we already have a guide on deploying Ghost with Docker in a reverse proxy setup. Instead of Ngnix reverse proxy, you can also use another software called Traefik with Docker. It is a popular open-source cloud-native application proxy, API Gateway, Edge-router, and more. I use Traefik to secure my websites using an SSL certificate obtained from Let's Encrypt. Once deployed, Traefik can automatically manage your certificates and their renewals. In this tutorial, I'll share the necessary steps for deploying a Ghost blog with Docker and Traefik.