Package: ruby2.3 Version: 2.3.1-5 Severity: important See discussion in https://bugs.ruby-lang.org/issues/12587
It turns out that the reason we need an existing ruby to bootstrap is that on ruby2.0 (2.0.0.299-1) I switched to using tarballs from the github git mirror¹, and _that_ requires already having ruby. If we use the actually release tarballs, then no existing ruby should be needed. ¹ because the release tarballs have (or had?) issues such as modifying shipped files on `make clean` So we need to: - switch to using release tarballs, and fix whatever issues there are with them. - `remove ruby | ruby-interpreter | ruby1.8` from Build-Depends - remove the "baseruby"-related bits from debian/rules - rewrite debian/split-tk-out.rb in shell (or perl, maybe) -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages ruby2.3 depends on: ii libc6 2.23-1 ii libgmp10 2:6.1.1+dfsg-1 ii libruby2.3 2.3.1-5 ii rubygems-integration 1.10 Versions of packages ruby2.3 recommends: ii fonts-lato 2.0-1 ii libjs-jquery 1.12.4-1 ruby2.3 suggests no packages. -- no debconf information -- Antonio Terceiro <[email protected]>
signature.asc
Description: PGP signature
