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

Bug#657405: mediagoblin: no more missing dependencies



On Fri, Oct 10, 2014 at 10:37:47PM +0200, W. Martin Borgert wrote:
> > On 2014-10-08 20:25, Matija Nalis wrote:
> > > there is also a need for python-pyld (which doesn't exist at all in
>
> It's in unstable now, so I assume no dependencies of mediagoblin
> 0.7.1 are missing from Debian, rigth?
> What else stops mediagoblin from entering the NEW queue? :~)

Wow, thanks for quick work!

Yes, with that two packages in, not much remains for Simon or you (or
someone) to make package ready is really 4 things...

3 very trivial things (meaning I managed to do them without problems):

- get last pristine 0.7.1 and 'uupdate -u' version from
  http://mentors.debian.net/package/mediagoblin to it
- remove obsolete
  0001-Fix-Babel-version-restriction.-Onward-and-upward.patch
- add dependencies on python-unidecode, new python-exif and python-pyld

and 1 just-a-little-less-trivial (at least for someone who is not
into python installing stuff very much - like myself): making few more
files get where they need to be in package.

Most importantly, I needed to do:

mkdir -p /usr/lib/python2.7/dist-packages/mediagoblin/static/metadata
cp mediagoblin/static/metadata/rdfa11.jsonld /usr/lib/python2.7/dist-packages/mediagoblin/static/metadata/rdfa11.jsonld

after installation for package to get it to work. It should go there by itself,
but there is too much python & dh automagic for me to see how
anything goes anywhere (good ol' makefiles were sooo nice :)

(note: there seem to be few more files that I found in static which
don't go into package but probably should:

extlib/tinymce/js/tinymce/tinymce.min.js
css/extlib/skeleton.css
fonts/Lato-Regular.ttf

but they do not seem to be critical, as everything seems to work
quite nicely for me even without them being installed - you can see
the package 0.7.1 built and installed as described working 
at http://media.mnalis.com/ as proof of concept)

After that, package builds and works nicely (after being setup as
described in README.Debian) on jessie.  Sure it would be nice if few
of those things in README.Debian were (semi)automated, but none of
that should block package entering NEW AFAICT, so it would be great
if it could there soon (like, in time for upcoming jessie freeze)!

Thanks again for taking action on this!

-- 
Opinions above are GNU-copylefted.


Reply to: