Bug#946310: ITP: ruby-jekyll-multiple-languages -- Jekyll plugin to internationalize sites
Package: wnpp Severity: wishlist Owner: Daniel Leidert -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: ruby-jekyll-multiple-languages Version : 1.6.0 Upstream Author : Martin Kurtsson * URL : https://github.com/kurtsson/jekyll-multiple-languages-plugin * License : MIT/X Programming Lang: Ruby Description : Jekyll plugin to internationalize sites Jekyll Multiple Languages is an internationalization plugin for Jekyll. It compiles a Jekyll site for one or more languages with a similar approach as Rails does. The different sites will be stored in subfolders with the same name as the language it contains. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAl3q0b8ACgkQS80FZ8KW 0F3ieA//dGcMOuuc3NguSfdFuMBTDO4Tr6Yubqj3wzVlEFYCYkWKEZRvq/faL1s2 7il3wUd3rMZe5JYivDu9CA3Vq+9q3H1NR/X1dCLuGSQP/SLuuyGksTt1+WwQLbyS jhbWsDD6l+O2TiZkOACdiTyVwPwXPviEzZflMUNb4ED+3baKmqDo1NOEcSxEhbBC 5IybueJCmkj7eAdgi7B9XmGYpzzXoBHDaw6j7Vs4zY+AtGMg46rzF34WXjIijmJf IGCOnnZRM+N5pECmz3wEsPvlims8R1Zf9NrJJ2U73WHMZ7UWuaTCtQW129/dI+E5 3aCQSmc8oRYwuQsXtDAhOgIi80ojUGAgAzYCDYJO+mqoIN2xAX1JjSIgXMprWG1J +JLxMwOnL5Rri/j5r0kwIZqiOH7otfr0mNgjsRjEVluUz130XoJG0CGAtZvgt/7d 3iPgredDsHAdL+SZGanWN8tB1XMldTGIXXq+ak5j5OnePCdKHGeKVyS/hwLGAPig +EfE2eaLYJf5J1CvuWK40o8609aKHWXtzu3K8DlHxLe136KiEpM6i87d0IK7xj20 W7cQtBk4LLojJg2vI+3T3qjJX5cNbzFPBHhfPFfl3rvd9qW5iSYU6hvsoKaNu7rs Rkc/oeJI7+WXnC4E9IW783TmQadavc9He5C6QdiPvEabd3ut8pc= =KT1Y -END PGP SIGNATURE-
RFP: lintian-sort -- reproducibly sort the Lintian tool's output
Hi, > The lintian-sort tool reorders the messages reported by the lintian(1) > Debian package analysis tool so that they are kept in the same order > between successive builds. > Wouldn't it be much better to apply this change to lintian itself? Lintian now orders tags before printing. That resolves the most relevant feature requested here. The output was already deterministic, but depended on the order in which checks that had been sorted were run: https://bugs.debian.org/944807 This is the Lintian commit message: https://salsa.debian.org/lintian/lintian/commit/e0f76bdd6bf57d84ba2e7b478973ddc8b84df950 Besides the bug in Lintian, this message also closes an RFP bug that had been cloned. Please re-open the RFP bug if we still need a second tool. To help make Lintian better, please file merge requests on Salsa. Thanks! Kind regards, Felix Lechner
difficulty in understanding options in init-system-GR
Hi folks, I went through the options in the init-system-GR[1] but I feel difficult to tell the subtle differences between the options. I'd like to ask for some hints here. Option F is distince from the others as it clearly emphasizes "deeper systemd integration". Option E puts equal weights to both systemd and non-systemd solutions. So let's skip the two. The rest options, i.e. B A D H G, look nearly the same to me: "first tier support for systemd, second tier for others" The only difference I noted is the bug severity for non-systemd support. In which way(s) are options (B, A, D, H, G) different from each other? A couple of keywords should be helpful enough to differentiate them. Thanks in advance. P.S. It could be extremely useful if a straightforward comparison table like [this](https://en.wikipedia.org/wiki/Comparison_of_file_systems) is available. But it isn't. I'd kindly suggest the future GR initiators make some comparison tables as long as options with subtle differences appear. [1] https://www.debian.org/vote/2019/vote_002
