On Wed, Jan 13, 2021 at 10:51:08AM +0000, Julian Gilbey wrote: > On Mon, Nov 02, 2020 at 04:32:54PM +0100, Michele Cane wrote: > > Package: fonts-materialdesignicons-webfont > > Version: 1.6.50-3 > > Severity: wishlist > > > > Dear Maintainer, > > > > Would it be possible to upload the latest upstream release. > > +1 from me (and I'm happy to do an NMU if this helps); the newer fonts > are required for the new version of Spyder.
Update: I have now prepared an updated package for local use and it is ready to upload to unstable if wanted. Key change: The SVG fonts are no longer shipped by upstream with the webfonts; they are now in a seperate repository. So my package does not include the SVG fonts. Medium change: I've upgraded to 5.5.55. This is the last version with a clear license and copyright statement. The current one is too vague to pass DFSG, but they are working on it (see https://github.com/Templarian/MaterialDesign/issues/5777). Smaller changes: I've updated the debhelper-compat to (= 13), and now Build-Depends: openstack-pkg-tools; having debian/rules potentially behave differently depending on whether this package is installed or not seems quite unwise. I've also removed one of the lintian overrides (tabs in copyright file - I replaced the tabs with spaces!). The override for preview.html is a bit more problematic: it is clearly auto-generated from something, but I have no idea how. My Git repository is on salsa at https://salsa.debian.org/jdg/fonts-materialdesignicons-webfont It is a fork of the OpenStack salsa repository, but I encountered some significant problems using it, most notably, the final commit on the master branch does not exist in the current upstream GitHub repository, so it is not possible to cleanly merge the current upstream. One could do a git reset --hard HEAD^ on that branch and then merge the current upstream and force push to salsa. What I did instead was to create a new branch called upstream which is now up-to-date with the upstream GitHub repository, and base my debian version on it - it is in the branch debian/unstable. Somewhat sadly, though, this means that the history of the debian/* files is lost, but I don't think it's that big a deal. I can't make a pull request for my work against your repository, as these two branches are not forked from any of your existing branches because of the upstream discrepancy. Finally, there is a piece of BOM removal code in the debian/rules file. This seems to be historic, as scss can now happily process the scss files even with the BOM present. (I reported it upstream at https://github.com/Templarian/MaterialDesign/issues/5778) Best wishes, Julian
