Hi Dag, > Have you checked the version from Github ?
no I haven't yet... as I will explain later... > I have a script (attached) that pulls the information from > LibreOffice (so it's the most current information). The aim is to > have unoconv use this information, rather than a static database, > however currently we have no way to get the extension information > per filter from LibreOffice yet. > > https://github.com/dagwieers/unoconv/issues/20 > > Feel free to help us with that ;-) Cool. > Development takes place on Github at: > > http://github.com/dagwieers/unoconv > > not on Red Hat bugzilla, Ubuntu Launchpad, Debian Dbt... And we > expect issues to be reported on Github. I am not very fond of > segregating problems and fragmenting communities :-/ I don't consider this segregation. I think that the package maintainers often have good contact to the upstream authors. I expect them to forward problems upstream, and to provide patches, if they have solution for a particular problem. As you already suggested to check for the latest version, this means that the next release might provide the desired fix. As I'm not a fan of downloading packages by hand, but of a well maintained distribution, I hope that a good package maintainer will take such a bug report as reason to backport certain patches, if it is an important feature (perhaps not in this case) and not wait until the next release is packaged. Thus I think it is a good idea to report problem to the distributions bugtracker. Nevertheless, I might find the time to an improved patch upstream. Christian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
