[Python-modules-team] Bug#920584: fixed in plastex 1.0.0-1

[Andreas Tille]

Hi Stuart,

CCing the old bug report to have some public record of our conversation.

On Sat, Feb 23, 2019 at 10:49:24AM +1100, Stuart Prescott wrote:
> Please reread 
> 
> 	https://release.debian.org/buster/freeze_policy.html
> 
> Particularly the bit about "small targeted fixes".

I admit I was aware that I was violating that part.  I was hunting for
packages with testing removal warning and stumbled upon de-facto
orphaned plastex.  Version 1.0.0 which is also quite aged seemed like a
candidate where this upgrade does not harm.  Its a real pity that I was
wrong with my estimation and I agree that I should not have done this.
 
> On Friday, 22 February 2019 13:20:03 AEDT Andreas Tille wrote:
> > Source: plastex
> > Source-Version: 1.0.0-1
> [...]
> 
> We're in the freeze, why are you uploading new upstream releases without 
> looking very carefully at the changes they bring and checking that they do not 
> break rdeps? pyxplot now FTBFS with this version of plastex :(

After we now agreed that I did a mistake which I regret what do you
think is the best option to fix it.  I see:

   1. Revert the version bump by adding an epoch.
   2. Adapt pyxplot to new version
   3. Go with the docs that do not need plastex which seems to
      be fragile anyway and since it is not ported to Python3 will
      be droped with Buster+1 anyway.  Looking at popcon[1] the usage
      of the docs is not impressive and its available online as well
   4. Any other suggestion?

Please decide what would be your prefered choice and I'll help
implementing it.

Sorry for the trouble

     Andreas.


[1] https://qa.debian.org/popcon-graph.php?packages=pyxplot+pyxplot-doc&show_vote=on&want_legend=on&want_ticks=on&from_date=&to_date=&hlght_date=&date_fmt=%25Y-%25m&beenhere=1

-- 
http://fam-tille.de