Hi,

Requesting for the loong64 port could be included in the Official lists,
we need to get the pre-approval from ftpmaster first.
Then donate appropriate hardware for the official buildds and
co-ordinate with DSA.

After communicating with ftpmaster / DSA and gradually adopting their
suggestions, we received provisional approval from ftpmaster and DSA.
Thanks for your patience and help.

With Thorsten Alteholz and Aurelien Jarno's suggestion, I should create
a bug to provide a response location, then ftpmaster and DSA can
formally approve it.
The bug will be kept in BTS and everybody can track the introduction of
loong64.

Your opinions are welcome.

Best regards,
Dandan Zhang

Hi everybody,

as someone has to start: there are no objections from the ftpmaster team
to add loong64 to the archive.

  Thorsten

No objections from the release team to migrate loong64 to the official archive.
But please note that, assuming it gets migrated soon, we don't promise it will
be in the testing suite in time for trixie.

Also I have a question about packages in -unreleased. I counted around 15
packages in there, including gcc-12. If/once loong64 moves to the official
archive, the -unreleased suite will no longer be available, and those custom
patches from porters are not allowed. So those packages will need to have the
patches submitted to the bug tracking system, or to upstream as appropriate, and
eventually accepted. What's the plan for them? Are there any blockers, or can
those patches be dropped and the official package used?

Cheers,
Emilio

Hi Thorsten,

On Thu, 5 Dec 2024 19:28:25 +0100 Thorsten Alteholz wrote:

 > Hi everybody,
 >
 > as someone has to start: there are no objections from the ftpmaster team
 > to add loong64 to the archive.
 >
 >  Thorsten
 >

Thanks to the ftpmaster team's formally approval.
Sorry to bother you in the meantime.
I'm in communication with the DSA team about an official buildd machines
for loong64.

Best regards,
Dandan Zhang

Hi,

On Thu, 12 Dec 2024 13:22:18 +0100 Emilio Pozuelo Monfort wrote:

 > No objections from the release team to migrate loong64 to the
official archive.
 > But please note that, assuming it gets migrated soon, we don't
promise it will

 > be in the testing suite in time for trixie.

Thanks to the release team for approving the migration of loong64 to the
official archive.
Ok, thanks for your reminder.
Migrating loong64 from unofficial to official archive requires
communication with ftpmaster.
We will continue to cooperate positively with the ftpmaster team, the
DSA team and the release team.

 >
 > Also I have a question about packages in -unreleased. I counted
around 15
 > packages in there, including gcc-12. If/once loong64 moves to the
official
 > archive, the -unreleased suite will no longer be available, and those
custom
 > patches from porters are not allowed. So those packages will need to
have the
 > patches submitted to the bug tracking system, or to upstream as
appropriate, and
 > eventually accepted. What's the plan for them? Are there any
blockers, or can
 > those patches be dropped and the official package used?
 >
 > Cheers,
 > Emilio
 >

About packages in -ureleased, Paul Gevers also discussed with me a week ago.
I have analyzed that there are currently 12 unreleased source packages,
which does not affect the generated rootfs file system (only use
unstable suite).
All of the 12 unreleased source packages include 4 categories,
- history version
gcc-12.
- "Failed" status
numba
- "Uploader" or "Installed" status
cppunit,libfm.
- support for loongarch64
* open PR in upstream
ode(leaf package), linuxlogo(leaf package), rust-cty(maintainer said
this is no longer necessary).
* be supported in upstream
libguestfs,rust-generator,rust-criterion-cycles-per-byte.
* be supported in debian
btllib,haskell-pandoc-lua-engine.

The specific situation is as follows,
1. Source: btllib
The support for loong64 was merged in git.
Please check
https://salsa.debian.org/med-team/btllib/-/blob/master/debian/changelog?ref_type=heads.

2. Source: cppunit
cppunit was built for loong64 in Debian Buildd, now the status is marked
as "Uploader".
Please check
https://buildd.debian.org/status/package.php?p=cppunit&suite=sid.

3. Source: gcc-12
gcc-12 source package was uploaded when initialized the Debian Ports
archive.
It is now replaced by gcc-13 / gcc-14 in the unstable suite.
Please check
http://ftp.ports.debian.org/debian-ports/pool-loong64/main/g/gcc-14/.

4. Source: haskell-pandoc-lua-engine
The rules for loong64 was merged in haskell-pandoc-lua-engine
(0.2.1.2-1) unstable.
Please check https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071173#12.
Now the status is marked as "BD-Uninstallable".

5. Source: libfm
libfm is not related to architecture, which can be built for loong64 in
Debian Buildd.
Please check https://buildd.debian.org/status/package.php?p=libfm&suite=sid.

6. Source: libguestfs
libguestfs is a set of tools for accessing and modifying virtual machine
(VM) disk images.
The support for loongarch64 has been submitted to the
upstream(https://github.com/libguestfs/libguestfs/).

7. Source: linuxlogo
linuxlogo belongs to a leaf software package, which do not block other
packages.

8. Source: numba
There is a public error in numba.
Please check https://buildd.debian.org/status/package.php?p=numba&suite=sid

9. Source: ode
ode belongs to a leaf software package, which do not block other packages.

10. Source: rust-criterion-cycles-per-byte
The support for loongarch64 has been submitted to the upstream.
Please check
https://github.com/wainwrightmark/criterion-cycles-per-byte/pull/2.

11. Source: rust-cty
The support for loongarch64 has been submitted to the
upstream(https://github.com/japaric/cty/pull/23).
Debian maintainer said it can be concluded that this is no longer necessary.
Please check https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060910#15

12. Source: rust-generator
The support for loongarch64 has been submitted to the
upstream(https://github.com/Xudong-Huang/generator-rs/pull/48).
Now there has a public build error in Debian Buildd.
Please check
https://buildd.debian.org/status/package.php?p=rust-generator&suite=sid.

Best regards,
Dandan Zhang

Hi,


After discussing internally, DSA has no objections to migrating loong64
to the official archive.

Our main concern was the hosting constraints,as 6 2U servers were
initially foreseen. Over the last weeks, we have been discussing that
and we agreed to use virtualization (KVM) to limit the number of servers
to host to 2x2U. We are looking for places to host them and will contact
you regarding that later.

Regards
Aurelien, for DSA

(resent as a signed mail)

Hi,


After discussing internally, DSA has no objections to migrating loong64
to the official archive.

Our main concern was the hosting constraints,as 6 2U servers were
initially foreseen. Over the last weeks, we have been discussing that
and we agreed to use virtualization (KVM) to limit the number of servers
to host to 2x2U. We are looking for places to host them and will contact
you regarding that later.

Regards
Aurelien, for DSA

Dear FTP team,

after the very successful launch of Debian Trixie, we're entering the first
week of development of the upcoming Debian Forky release. One of the proposed
features will be official support for Loongson's LoongArch architecture [1].

We have already received approval from the release team and DSA and we're now
just waiting for the FTP team to import loong64 to the official archive.

We have one beefy loong64 server that is already maintained by DSA [2] with a
second machine that has already arrived at one of Debian's hosting locations,
Dandan Zhang who has been CC'ed on this mail can comment on the second server.

I will be acting as the primary maintainer of the loong64 port, but I am happy
to accept any co-maintainers within Debian. Additional help is provided by
Loongson engineers who have been very busy fixing Debian packages and upstream
projects on loong64.

Overall, the port is in an extremely good shape with nearly all relevant software
being available such as Rust, Golang, LibreOffice, Firefox, OpenJDK and so on,
so I don't expect any additional work to unbreak packages on loong64. Furthermore,
the loong64 machines are quite fast, so that I don't expect the full archive rebuild
to take very long.

I have not been involved with importing a new port into the official archive yet,
but I suppose it should be enough to import enough packages from Debian Ports
to be able to install build-essential, then let the buildds do the rest. Then trigger
binNMUs for the packages imported from Debian Ports.

Please let me know if you have any more questions or concerns regarding this.

Thanks a lot for your work!

Cheers,
Adrian

Hi,

Thanks Adrian. Okay, let me add some information about LoongArch build
machines.

- About the first LoongArch machine
The first Debian LoongArch machine located in conova was deployed by
Aurelien Jarno (aurel32@debian.org) in March 2025. Thanks Aurelien Jarno
very much.
The details can be found at
https://db.debian.org/machines.cgi?host=loongson-conova-01.

- About the second LoongArch machine
Since attending debconf24, I have been in contact with Hector Oron
(zumbi@debian.org), who has been doing his utmost to help find a hosting
location, the second LoongArch server machine was hosted at Lisboa,
Portugal in June 2025. Thanks Hector Oron very much.

Please feel free to contact me with any questions. I will always be here.

Best Regards,
Dandan Zhang

Hello,

The DSA team has already deployed 6 buildd nodes for loong64 on 2
LoongArch64 servers.
The details of the 6 buildd nodes are as follows:
https://db.debian.org/machines.cgi?host=loongson-conova-01
https://db.debian.org/machines.cgi?host=loongson-conova-02
https://db.debian.org/machines.cgi?host=loongson-conova-03
https://db.debian.org/machines.cgi?host=loongson-tecnico-01
https://db.debian.org/machines.cgi?host=loongson-tecnico-02
https://db.debian.org/machines.cgi?host=loongson-tecnico-03

Special thanks to Aurelien Jarno(aurel32@debian.org) and Hector
Oron(zumbi@debian.org).

Best regards,
Dandan Zhang

Forward to debian-loongarch <debian-loongarch@lists.debian.org> Mailing Lists.

It's a very good news for loongarch ports.

In Debconf25 Brest BoF: DSA[1], I'd know that there is a new build machine will ready,
It's online now, Good!

Thanks all!

But in https://buildd.debian.org/status/architecture.php?a=loong64,
I can't find these machines, what is the next step?


Regards,


[1] https://salsa.debian.org/debconf-team/public/data/dc25/-/raw/main/etherpad/txt/192-bof-dsa.txt

在 2025/11/6 20:48, zhangdandan 写道:

Hello Xiao Sheng,

El vie, 7 nov 2025, 10:51, xiao sheng wen(肖盛文) <atzlinux@debian.org>
escribió:

But in https://buildd.debian.org/status/architecture.php?a=loong64,

Ftp-master and buildd team need to work together to import into official
archive from debian-ports archive.

The person that handled this from ftp-master team retired from Debian,
therefore it might take some time to implement new import process, please
check with ftp-master what's needed from their side for the import.

Regards