• Arch qualification for buster: call for DSA, Security, toolchain co

    From Luke Kenneth Casson Leighton@21:1/5 to adam@adam-barratt.org.uk on Fri Jun 29 12:50:01 2018
    ---
    crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68


    On Fri, Jun 29, 2018 at 10:35 AM, Adam D. Barratt
    <adam@adam-barratt.org.uk> wrote:

    what is the reason why that package is not moving forward?

    I assume you're referring to the dpkg upload that's in proposed-updates waiting for the point release in two weeks time?

    i don't know: i'm an outsider who doesn't have the information in
    short-term memory, which is why i cc'd the debian-riscv team as they
    have current facts and knowledge foremost in their minds. which is
    why i included them.

    I'm also getting very tired of the repeated vilification of SRM over
    this, and if there were any doubt can assure you that it is not
    increasing at least my inclination to spend my already limited free
    time on Debian activity.

    ah. so what you're saying is, you could really do with some extra help?

    l.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Luke Kenneth Casson Leighton@21:1/5 to adam@adam-barratt.org.uk on Fri Jun 29 13:40:01 2018
    On Fri, Jun 29, 2018 at 12:23 PM, Adam D. Barratt
    <adam@adam-barratt.org.uk> wrote:

    i don't know: i'm an outsider who doesn't have the information in
    short-term memory, which is why i cc'd the debian-riscv team as they
    have current facts and knowledge foremost in their minds. which is
    why i included them.

    It would have been wiser to do so *before* stating that nothing was
    happening as if it were a fact.

    true... apologies.

    ah. so what you're saying is, you could really do with some extra
    help?

    I don't think that's ever been in dispute for basically any core team
    in Debian.

    :)

    That doesn't change the fact that the atmosphere around the change in question has made me feel very uncomfortable and unenthused about SRM
    work. (I realise that this is somewhat of a self-feeding energy
    monster.)

    i hear ya.

    l.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From YunQiang Su@21:1/5 to All on Sat Jul 7 17:30:01 2018
    Niels Thykier <niels@thykier.net> 于2018年6月28日周四 上午4:06写道:

    Hi,


    As part of the interim architecture qualification for buster, we request
    that DSA, the security team and the toolchain maintainers review and
    update their list of known concerns for buster release architectures.

    Summary of the current concerns and issues:
    * DSA have announced a blocking issue for armel and armhf (see below)
    * Concerns from DSA about ppc64el and s390x have been carried over from
    stretch.
    * Concerns from the GCC maintainers about armel, armhf, mips, mips64el
    and mipsel have been carried over from stretch.

    If the issues and concerns from you or your team are not up to date,
    then please follow up to this email (keeping debian-release@l.d.o and debian-ports@l.d.o in CC to ensure both parties are notified).

    Whilst porters remain ultimately responsible for ensuring the
    architectures are ready for release, we do expect that you / your team
    are willing to assist with clarifications of the concerns and to apply patches/changes in a timely manner to resolve the concerns.


    List of blocking issues by architecture =======================================

    The following is a summary from the current architecture qualification
    table.

    armel/armhf:
    ------------

    * Undesirable to keep the hardware running beyond 2020. armhf VM
    support uncertain. (DSA)
    - Source: [DSA Sprint report]


    [DSA Sprint report]: https://lists.debian.org/debian-project/2018/02/msg00004.html


    List of concerns for architectures
    ==================================

    The following is a summary from the current architecture qualification
    table.

    * Concern for ppc64el and s390x: we are dependent on sponsors for
    hardware.
    (Raised by DSA; carried over from stretch)

    * Concern for armel and armhf: only secondary upstream support in GCC
    (Raised by the GCC maintainer; carried over from stretch)

    * Concern for mips, mips64el, mipsel and ppc64el: no upstream support
    in GCC
    (Raised by the GCC maintainer; carried over from stretch)


    This is a misunderstanding as MIPS company had some unrest in recent half year. Currently we are stable now, and the shape of gcc upstream is also good.


    Architecture status
    ===================

    These are the architectures currently being built for buster:

    * Intel/AMD-based: amd64, i386
    * ARM-based: arm64, armel, armhf
    * MIPS-based: mips, mipsel, mips64el

    We are plan to drop mips(eb) and keep mipsel/mips64el.

    * Other: ppc64el, s390x

    If the blocking issues cannot be resolved, affected architectures are at
    risk of removal from testing before buster is frozen.

    We are currently unaware of any new architectures likely to be ready in
    time for inclusion in buster.

    On behalf of the release team,
    Niels Thykier



    --
    YunQiang Su

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mattia Rizzolo@21:1/5 to Adam Borowski on Wed Dec 12 09:20:01 2018
    This thread went OT talking about ports, but oh well…

    On Wed, Dec 12, 2018 at 04:03:25AM +0100, Adam Borowski wrote:
    On Tue, Dec 11, 2018 at 09:46:21PM +0100, Gregor Riepl wrote:
    The build and package delivery infrastructure should offer the same features
    for both first and second class archs, including installer image building for
    all "tiers" (stable, testing, unstable).

    It seems to me that the important bit is the testing suite. As a (now lapsed) x32 porter, I tried to implement that on my own (goal being an unofficial, weakly security supported[1] Jessie for x32). And tracking testing on my own proved to be too hard.

    Pretty much everything of what Adrian is mentioning (above is part of
    it), would be fixed if the ports archive were to move to using a full
    dak instance.

    I know that James was working on adding the few missing features that
    would be ports-specific, but I haven't heard an update on that work
    since a while.

    --
    regards,
    Mattia Rizzolo

    GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
    more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'`
    Debian QA page: https://qa.debian.org/developer.php?login=mattia `-

    -----BEGIN PGP SIGNATURE-----

    iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAlwQwnwACgkQCBa54Yx2 K63JaxAArxlTaoKsPA6aLFS7YEoE96y8yCmCjL8slWRn2CtOovZ1isfv8DoG7WBV bESlwgZqrtbt5ho9Xxac7tloYlujC91mUbkQ90gdW1dg+NdDt2oC8UXOay7piYLq +PFXHw724WPMX7WwHSslGzskeA1XdO+za/Pfffvih9kQ7Qeibvb/VHg+Hug2Q+t+ 9sqe5ts4kVpFVdbCuBVfUQYEfIMovC02N5RlW9556Cy9pvyFzcSE+/KuhZ1WiJxu PjYID9Sy/TNGkofgUeq8J9jPpKpMuNcW7tm2hL/NpHYYPqQzcYAD5ENlAtErD0aG wX0VCMna5ldvvwLCFDNiPIYVJjgH8OjOXv7dpzKQCQHHH1TpGhzsnILnOu9UTAev 5j1zc+tZ3MeyvIMUA4oceWik8t5e8Q/LL0Jrrc6k3lzjtQF5fCUwlaq/F0ZvPogc jArCNp34LnyTyDozQ7yA3WnfMG81wuvQHmN5AroS5FtBAz0up8jdmCEDsw7vI9Jq +9Iy1loHHPgLUr4NcDqOuOOO3ciF4HSzu/dHeESV3fzHk+AbojJ