#1103848 ruby-rails-propshaft: package name should be ruby-propshaft

Package:
ruby-rails-propshaft
Source:
ruby-rails-propshaft
Submitter:
Pirate Praveen
Date:
2025-08-25 23:23:02 UTC
Severity:
normal
#1103848#5
Date:
2025-04-21 22:00:32 UTC
From:
To:
Dear Maintainer,

Usually all rubygems get a ruby-prefixed to the gem name. Any reason to deviate
from the standard?

I think it'd be better if this package also followed the standard practice of
ruby-<gem name> and use ruby-propshaft.
#1103848#10
Date:
2025-04-23 08:19:43 UTC
From:
To:
The thought process with the name is that this package is only useful
to rails.  It can’t be used generally by other Ruby packages.

Upstream is propshaft inside of the rails project.

https://github.com/rails/propshaft

However, if there is a general consensus that this should be named
ruby-propshaft I am not opposed to changing it.
#1103848#13
Date:
2025-04-23 08:19:43 UTC
From:
To:
The thought process with the name is that this package is only useful
to rails.  It can’t be used generally by other Ruby packages.

Upstream is propshaft inside of the rails project.

https://github.com/rails/propshaft

However, if there is a general consensus that this should be named
ruby-propshaft I am not opposed to changing it.
#1103848#18
Date:
2025-04-23 08:42:32 UTC
From:
To:
Only golang follows that convention because you have to also import by
full url. But every rubygem the name is unique and every other ruby gem
package only adds ruby- to gem name. Only when there is fork and two
different gems by close enough gems we add the repo name.

This is already established naming standard used for all rubygems as
codified in gem2deb.
#1103848#23
Date:
2025-04-23 08:42:32 UTC
From:
To:
Only golang follows that convention because you have to also import by
full url. But every rubygem the name is unique and every other ruby gem
package only adds ruby- to gem name. Only when there is fork and two
different gems by close enough gems we add the repo name.

This is already established naming standard used for all rubygems as
codified in gem2deb.
#1103848#26
Date:
2025-04-23 08:42:32 UTC
From:
To:
Only golang follows that convention because you have to also import by
full url. But every rubygem the name is unique and every other ruby gem
package only adds ruby- to gem name. Only when there is fork and two
different gems by close enough gems we add the repo name.

This is already established naming standard used for all rubygems as
codified in gem2deb.
#1103848#31
Date:
2025-04-23 14:07:02 UTC
From:
To:
AFAICT there is no strictly technical reason to name it ruby-propshaft,
but following the established convention makes it simpler for us humans.
#1103848#36
Date:
2025-04-23 14:07:02 UTC
From:
To:
AFAICT there is no strictly technical reason to name it ruby-propshaft,
but following the established convention makes it simpler for us humans.
#1103848#39
Date:
2025-04-23 14:07:02 UTC
From:
To:
AFAICT there is no strictly technical reason to name it ruby-propshaft,
but following the established convention makes it simpler for us humans.
#1103848#44
Date:
2025-04-23 18:36:52 UTC
From:
To:
OK.  I will make the change once things open up after the trixie
release.
#1103848#49
Date:
2025-08-18 21:15:39 UTC
From:
To:
I have uploaded a renamed package to NEW.
#1103848#52
Date:
2025-08-18 21:15:39 UTC
From:
To:
I have uploaded a renamed package to NEW.
#1103848#57
Date:
2025-08-22 14:10:12 UTC
From:
To:
We believe that the bug you reported is fixed in the latest version of
ruby-propshaft, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1103848@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Soren Stoutner <soren@debian.org> (supplier of updated ruby-propshaft package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Mon, 18 Aug 2025 13:29:37 -0700
Source: ruby-propshaft
Binary: ruby-propshaft
Architecture: source all
Version: 1.2.1-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Ruby Team <pkg-ruby-extras-maintainers@lists.alioth.debian.org>
Changed-By: Soren Stoutner <soren@debian.org>
Description:
 ruby-propshaft - asset pipeline library for Rails
Closes: 1103848
Changes:
 ruby-propshaft (1.2.1-1) experimental; urgency=medium
 .
   * New upstream release.
   * debian/control:
     - Rename source and binary packages from ruby-rails-propshaft to
       ruby-propshaft (closes: #1103848).
     - Add Breaks/Replaces ruby-rails-propshaft.
     - Update Vcs-Git and Vcs-Browser fields for new Salsa URL.
     - Remove obsolete "Rules-Requires-Root: no".
     - Update Standards-Version from 4.7.0 to 4.7.2, no changes needed.
Checksums-Sha1:
 66cb7b3f282766e48fdc56efb7b02dbf0e859f7d 2166 ruby-propshaft_1.2.1-1.dsc
 0ccd25745c59cb5091dec58462945c796453d2ae 15086 ruby-propshaft_1.2.1.orig.tar.gz
 d8ac4c1729898ec6ff46694e4e3f96dc2232bfe8 2712 ruby-propshaft_1.2.1-1.debian.tar.xz
 5c6616d93c7f5738331d01c8df5cc52f9d2f761b 16656 ruby-propshaft_1.2.1-1_all.deb
 8d1ee320b4ca8d14e16a033afe4350e79b2eea9f 9252 ruby-propshaft_1.2.1-1_amd64.buildinfo
Checksums-Sha256:
 e458be98eb245b79c7c0a1b3da37985a9b3359cf783aff543557e89545a8e3b9 2166 ruby-propshaft_1.2.1-1.dsc
 18644b2bc6506d1710e8fea26c66b187c891bd460ead8fa5ea939c2bd3896422 15086 ruby-propshaft_1.2.1.orig.tar.gz
 4497e1800b3055cd9480310c52153c170c2a8674ab11292be9abab1349062bc6 2712 ruby-propshaft_1.2.1-1.debian.tar.xz
 b634ff174d5c36d7426e4013a9a6a8d6cc62d76b06e493756e3cd07bd91b95ff 16656 ruby-propshaft_1.2.1-1_all.deb
 7fd104b737ef96be4ccfbb85dbdd67a7b67a6ad453f3bf4e74959803b55b217e 9252 ruby-propshaft_1.2.1-1_amd64.buildinfo
Files:
 2429596a2682e0b26b31d6f68a95570c 2166 ruby optional ruby-propshaft_1.2.1-1.dsc
 82a7d77c46dc678830944611b1a3247d 15086 ruby optional ruby-propshaft_1.2.1.orig.tar.gz
 78d96ff070b424852171573fc4e69bdb 2712 ruby optional ruby-propshaft_1.2.1-1.debian.tar.xz
 368f420b530ee8859dfa69047fa32560 16656 ruby optional ruby-propshaft_1.2.1-1_all.deb
 d4b5877518d53e88a504b03710b59ba2 9252 ruby optional ruby-propshaft_1.2.1-1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEJKVN2yNUZnlcqOI+wufLJ66wtgMFAmijkwAACgkQwufLJ66w
tgP6PhAAuvcF+hNk0z1Ar/PQxH5f0gdF04qRJ7H0xjCV9icCraa3UcnjAOaBLtma
qT3K/gcIPVbp9vSc+nPpHMYzcfsrKeqfO21bkSalFLTyUboQ2+27ohy7KfWQhmUb
9pOfFFvwj4W6yA2DobhMJzrS8BFt7Mv6z9b0fVWrYbGJZxwiF1RhebcdM6pkMa7h
sM07uMeZlmEoDJUSKkN4ZJVIBZF9hPkOE5cjMkn9Q+YUVHN7Gl8Fgu+eel+QJ88n
5MM+pqlPLzMKUObp7QzE+UDzymspZFNLuuHbZb7sdMtDssG+o+oGsS4PsPJTcqnY
YV91gADg0JZ52Gqtpkri42VzV4Uc4BLdXLBXg4K/iqpDNhtdedRajNPLYH6PVZt3
h7CETnlbI2SK/w7pdwU8iG6VBfQokQ/1PcMpdBVK5qYYnmdEEYxagpWO8AoALuVM
oKBW4M5kUtAxBO3t5R5eCVRLhxlX2+vq4UVAKjgEPC2p3ZVQdXFLiSjTsjZNS0Nj
bMWz9lm77EcMp0zXXze5BGNPHfbm/Qm1ZZioNzbADqbR77SweNxIDqRUjUvHm45r
4HvxwPoCMzMhwyf+7v1Z9Qn7L0aah0c8PwvdZT4XAbidMnhyz3iIX059aY1ItjJg
KmkuKnMGHd31Rh6WfcrcvdvsBULuf2YpFoZpt9BvEolMyVQGr0k=
=K+wS
-----END PGP SIGNATURE-----
#1103848#62
Date:
2025-08-25 23:22:14 UTC
From:
To:
The new ruby-propshaft package has entered unstable.  However,
when I packaged it, I updated to the latest 1.2.1 version, which it
turns out Redmine is not yet compatible with.  So, Redmine will
continue to use ruby-rails-propshaft 1.1.0 until upstream supports
1.2.1, at which point I will change the dependency name in
Redmine and remove the ruby-rails-propshaft package.
#1103848#65
Date:
2025-08-25 23:22:14 UTC
From:
To:
The new ruby-propshaft package has entered unstable.  However,
when I packaged it, I updated to the latest 1.2.1 version, which it
turns out Redmine is not yet compatible with.  So, Redmine will
continue to use ruby-rails-propshaft 1.1.0 until upstream supports
1.2.1, at which point I will change the dependency name in
Redmine and remove the ruby-rails-propshaft package.