[Git][java-team/scala-2.13][debian/latest] Remove redundant debian/upstream/metadata and default maven.rules; shorten README.source

Juan Manuel Méndez Rey (@mendezr) gitlab at salsa.debian.org
Tue Nov 3 03:18:22 GMT 2026



Juan Manuel Méndez Rey pushed to branch debian/latest at Debian Java Maintainers / scala-2.13


Commits:
3858a25c by Juan Manuel Méndez Rey at 2026-11-03T01:15:15+01:00
Remove redundant debian/upstream/metadata and default maven.rules; shorten README.source

- - - - -


4 changed files:

- debian/README.source
- debian/changelog
- debian/maven.rules
- − debian/upstream/metadata


Changes:

=====================================
debian/README.source
=====================================
@@ -1,88 +1,50 @@
 scala-2.13 for Debian
 =====================
 
-This is the Scala 2.13 series, packaged next to the scala package (2.12).
-Both can be installed together: the jars carry versioned names
-(scala-library-2.13.18.jar, scala-library-2.13.jar), the commands are
-also available as scalac-2.13, scala-2.13, scaladoc-2.13, fsc-2.13 and
-scalap-2.13, and /usr/bin/scala and friends are update-alternatives,
-pointing at the newest series installed.
+Two-pass build (no sbt)
+-----------------------
 
-Two-pass self-host build (no sbt)
----------------------------------
-
-debian/build-driver.sh compiles the Scala 2.13 module layers (library,
-reflect, compiler, interactive, repl, repl-frontend, scaladoc, scalap)
-straight with a STARR scalac, then assembles the jars. debian/rules runs it
-twice:
+debian/build-driver.sh compiles the modules with a STARR scalac and
+assembles the jars. debian/rules runs it twice and installs only the
+pass-2 jars:
 
   pass 1: STARR = scala-2.13 from the archive -> jars in debian/buildout1
   pass 2: STARR = the pass-1 jars             -> jars in debian/buildout2
 
-Only the pass-2 jars are installed. The source package contains no
-prebuilt jar or class file.
-
-Stage-0 bootstrap seed (provenance and reproducibility)
--------------------------------------------------------
-
-Scala 2.13 can only be compiled by a Scala 2.13 compiler, so the very first
-build needs a seed, as for every self-hosting compiler in Debian. It is the
-only non-source input, it is used once, and it is never part of the source
-package or of any binary package.
-
-The seed is exactly the STARR that upstream itself pins for this release,
-in versions.properties at the packaged tag:
+Stage-0 bootstrap seed
+----------------------
 
-  starr.version=2.13.17
-
-i.e. upstream's own published 2.13.17 jars:
+The first build needs a Scala 2.13 compiler. The seed is the STARR that
+upstream pins in versions.properties at the packaged tag
+(starr.version=2.13.17), as published on Maven Central:
 
   https://repo1.maven.org/maven2/org/scala-lang/scala-library/2.13.17/scala-library-2.13.17.jar
-    sha1   766aafc5e3c310bde92e405988bc7f6eb31d7cf9
     sha256 b7822c4225243215f185925724a6edff92cf18777a136cc738276c4446fac76c
   https://repo1.maven.org/maven2/org/scala-lang/scala-reflect/2.13.17/scala-reflect-2.13.17.jar
-    sha1   d7ea6ad0d92e3bbe0afef1bdffbbe172704c8c47
     sha256 734533897bcfabe7a6e7fa09dbee165b257b0396e14e8a57c75111db8e04bb98
   https://repo1.maven.org/maven2/org/scala-lang/scala-compiler/2.13.17/scala-compiler-2.13.17.jar
-    sha1   70f6ece2d45d2f89fb9a4d5e41181ade1bd9d416
     sha256 073ab364dc902519719bd6b9463562128abc5881d2a2e4b7a5e2d04cdd7bc025
 
-The sha1 values are the ones Maven Central publishes next to each jar.
-
-With sbuild, debian/make-stage0-deb downloads the jars, checks the
-checksums and builds a local-only scala-2.13-stage0 .deb that installs them
-to /usr/share/scala-2.13-stage0. That .deb is never uploaded:
+The seed is never part of the source package or of a binary package.
+debian/make-stage0-deb downloads the jars, checks them and builds a
+local-only scala-2.13-stage0 .deb:
 
   debian/make-stage0-deb /tmp/stage0
   sbuild --profiles=pkg.scala.stage0 \
     --extra-package=/tmp/stage0/scala-2.13-stage0_2.13.17_all.deb scala-2.13_*.dsc
 
-Without a chroot, put the three jars in a directory and point SCALA_STAGE0
-at it:
+Without a chroot, put the three jars in a directory:
 
   dpkg-buildpackage -Ppkg.scala.stage0 -d SCALA_STAGE0=$HOME/scala-2.13-stage0
 
-The stage0 build uses JDK 25 (openjdk-25-jdk-headless): the 2.13.17 STARR
-cannot compile the 2.13.18 library on JDK 26 and later, where
-java.util.Comparator gained default max/min methods. 2.13.18 itself handles
-them (https://github.com/scala/bug/issues/13127), so normal builds use
-default-jdk.
-
-NEW throws away the binaries of an upload to unstable
-(https://wiki.debian.org/ThrowAwayNewBinaries), and the buildds cannot
-build -1 without scala-2.13 in the archive. So the bootstrap takes three
-uploads: -1 through NEW, -2 source+binary to unstable built with the stage0
-profile, -3 source-only. From then on the archive
-self-hosts and the seed is no longer used; the stage0 profile stays only to
-bootstrap new architectures. A normal-profile build against the stage0
-output produces byte-identical .debs.
-
-Debian changes
---------------
+The stage0 build needs JDK 25 (openjdk-25-jdk-headless): the 2.13.17 STARR
+cannot compile the 2.13.18 library on JDK 26 and later
+(https://github.com/scala/bug/issues/13127). Normal builds use default-jdk.
 
- * scaladoc takes jQuery from libjs-jquery instead of a webjar
-   (debian/patches/0001).
- * java-diff-utils is not packaged; -Yprint-trees:diff prints whole trees
-   (debian/patches/0002).
+NEW throws away binaries (https://wiki.debian.org/ThrowAwayNewBinaries), so
+the bootstrap takes three uploads: -1 through NEW, -2 source+binary to
+unstable built with the stage0 profile, -3 source-only. After that the
+archive self-hosts and the stage0 profile is only for new architectures.
+A normal build against the stage0 output gives byte-identical .debs.
 
  -- Juan Manuel Méndez Rey <juan.mendezr at proton.me>


=====================================
debian/changelog
=====================================
@@ -4,6 +4,8 @@ scala-2.13 (2.13.18+ds2-2) UNRELEASED; urgency=medium
     as upstream does.
   * README.source: -1 went through NEW to unstable; -2 brings the stage0
     binaries.
+  * Drop redundant debian/upstream/metadata and default maven.rules;
+    shorten README.source.
 
  -- Juan Manuel Méndez Rey <juan.mendezr at proton.me>  Thu, 29 Oct 2026 08:27:01 +0100
 


=====================================
debian/maven.rules
=====================================
@@ -1,3 +1 @@
 org.scala-lang * * s/2\.13\..*/2.13.x/ * *
-org.scala-lang.modules scala-asm * s/.*/debian/ * *
-org.jline jline * s/.*/debian/ * *


=====================================
debian/upstream/metadata deleted
=====================================
@@ -1,6 +0,0 @@
----
-Bug-Database: https://github.com/scala/bug/issues
-Bug-Submit: https://github.com/scala/bug/issues/new
-Repository: https://github.com/scala/scala.git
-Repository-Browse: https://github.com/scala/scala
-Documentation: https://docs.scala-lang.org/



View it on GitLab: https://salsa.debian.org/java-team/scala-2.13/-/commit/3858a25c83f0757938bed97e9e9aae8427b122cb

-- 
View it on GitLab: https://salsa.debian.org/java-team/scala-2.13/-/commit/3858a25c83f0757938bed97e9e9aae8427b122cb
You're receiving this email because of your account on salsa.debian.org. Manage all notifications: https://salsa.debian.org/-/profile/notifications | Help: https://salsa.debian.org/help


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-java-commits/attachments/20261103/11760445/attachment.htm>


More information about the pkg-java-commits mailing list