Hi Andrius, El 21/10/24 a las 14:17, Andrius Merkys escribió: > Hi Santiago, > > On 2024-10-20 04:50, Santiago Ruano Rincón wrote: > > Following a discussion we had in #debian-security with dnl, and by the > > comment > > by Mortiz in > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1084059#5, > > I think it is worth to discuss if packages {,build} depending on > > the EOL'ed twitter-bootstrap3 or twitter-bootstrap4 should move to > > bootstrap 5 (src:bootstrap-html, libjs-bootstrap5). Before bringing the > > subject up to debian-devel, I would like discuss it with you. > > Thanks for raising this issue. It would be great to have advice/options for > package maintainers on how to switch away from deprecated packages. Is > migration as easy as drop-in replacement or regeneration of documentation > packages? If not, general advice on how to patch the affected packages would > be very nice to have. [...]
Thanks a lot for your feedback. My experience with bootstrap is very limited, and I easily guess any of the maintainers has a better understanding of the migration requirements than me. AFAICS, bootstrap 5 is not just a drop-in replacement, and so the bugs are mainly on the upstream side. In any case, I think it is worth to include in the mail to debian-devel and in the potential bugs the bootstrap documentation about migrating to 5.x and to 4.x: https://getbootstrap.com/docs/5.3/migration/ https://getbootstrap.com/docs/4.6/migration/ This could serve as guide to upstreams. Does that make sense to you? Any other comment? Best regards, -- Santiago
signature.asc
Description: PGP signature
-- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
