[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#838112: uctodata: fails to upgrade from jessie - trying to overwrite /etc/ucto/es.abr



Hi Andreas, Mattia, et. al.

> uploads should happen early enough to allow automatic migration after 10
> days on Feb 05 (so probably at most 2 days left)

Right. We have prepared new upstream releases for uctodata, ucto, frogdata and
frog today that rely on the data being in share/ instead of etc/, and should
therefore resolve this persistent bug. I updated all the debian packages
accordingly. The fact I did frog and frogdata as well is because the same issue
might likely arise there and it depends on ucto anyhow. Putting the stuff in
etc/ was unnecessary overengineering on our part.

I followed the documentation and created postint/preinst/postrm scripts for
libucto2 (ucto), uctodata and frogdata that takes care of removing the old
files, as you suggested. I tested it on migration from the previous releases
and it works. Still, a second look from someone with more knowledge about these
things is highly appreciated.  I haven't been able to test the upgrade from the
jessie versions yet but I'll try to look into piuparts to do that. I think
everything should be solved with the releases I prepared today (but again;
double checks appreciated!)

@Mattia: Do you happen to be available on such short notice to sponsor/upload
these four packages again?  Considering also the very tight deadline before the
freeze. Sorry for the inconvenience!

For completion's sake, the packages are:

* https://anonscm.debian.org/cgit/debian-science/packages/uctodata.git
* https://anonscm.debian.org/cgit/debian-science/packages/ucto.git
* https://anonscm.debian.org/cgit/debian-science/packages/frogdata.git
* https://anonscm.debian.org/cgit/debian-science/packages/frog.git
 
Regards,

PS: the postinst/preinst/postrm scripts are currently three copies of the same
thing. I realize this is probably ugly (unnecessary duplication) and not the
best way, but I didn't know what would be the best solution and since I was in
a rush I left it like this.

--

Maarten van Gompel
    Centre for Language Studies
    Radboud Universiteit Nijmegen

proycon@anaproy.nl
https://proycon.anaproy.nl
https://github.com/proycon

GnuPG key:  0x1A31555C  
XMPP: proycon@anaproy.nl  Matrix: @proycon:anaproy.nl
Telegram:   proycon       IRC: proycon (freenode)
Twitter:    https://twitter.com/proycon
ORCIRD:     https://orcid.org/0000-0002-1046-0006 
Bitcoin:    1BRptZsKQtqRGSZ5qKbX2azbfiygHxJPsd


Reply to: