On Mon, Jul 24, 2017 at 03:23:20PM +0100, Ghislain Vaillant wrote: > On Mon, 2017-07-24 at 16:13 +0200, Adam Borowski wrote: > > On Mon, Jul 24, 2017 at 09:31:34AM +0100, Ghislain Vaillant wrote: > > > 2017-07-24 1:23 GMT+01:00 Adam Borowski <kilob...@angband.pl>: > > > > On debdiff: > > > > Files in second .deb but not in first > > > > ------------------------------------- > > > > -rw-r--r-- root/root /usr/share/doc/pybind11-doc/ > > > > html/_sources/advanced/cast/chrono.rst.txt > > > > -rw-r--r-- root/root /usr/share/doc/pybind11-doc/ > > > > html/_sources/advanced/cast/custom.rst.txt > > > > [many more] > > > > > > > > Files in first .deb but not in second > > > > ------------------------------------- > > > > -rw-r--r-- root/root /usr/share/doc/pybind11-doc/ > > > > html/_sources/advanced/cast/chrono.txt > > > > -rw-r--r-- root/root /usr/share/doc/pybind11-doc/ > > > > html/_sources/advanced/cast/custom.txt > > > > > > > > I guess you don't want .rst.txt > > > > > > > > > This has to do with the change of behavior between Sphinx 1.4.x > > > (Stretch) > > > and 1.5.x (Buster). > > > > > > Same thing has happened with other packages uploaded recently, such > > > as > > > python-latexcodec. > > > > > > I guess it needs to be fixed somewhere, then. Could you tell us when > > you'll > > have an updated package, or sphinx itself is fixed? > > I don't understand what needs to be fixed. Sphinx changed the way they > generate the documentation, so what?
Looks like the files are bit-for-bit identical, the new version merely has double extension which is not nice, but not a show stopper. > Should there be a problem, then it should probably be fixed in Sphinx. > This package, as many others I maintain, uses a fairly standard Sphinx > configuration. Should I then go ahead with the upload? -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ A dumb species has no way to open a tuna can. ⢿⡄⠘⠷⠚⠋⠀ A smart species invents a can opener. ⠈⠳⣄⠀⠀⠀⠀ A master species delegates.
