On Fri, 10 Jan 2014, Craig Small wrote: > > - the old 2012 theme has been removed > It still appears in my 3.8 archive, are you sure?
No, I was just making a supposition. Then we keep it until upstream drops it! > > - dependencies ought to be updated to account for those default theme > > changes > I saw those, but I didn't think they were right. > It currently is > Depends: 2014 > Recommends: 2013, 2012 > To me it would be > Depends: 2014|2013|2012 > ie we dont care what theme you have, just as long as you have one. > Or is there some inter-dependency between themes going on here? I wasn't quite sure how the default theme gets picked on fresh installs or for new instances in a multi-site installation so I wanted to ensure that the latest theme was always installed. Also it seems better to have all the upstream-provided themes available per default when you "apt-get install wordpress" so listing the additional themes in Recommends seemed right too. > > - debian/missing-sources/ should be updated if needed (see the README in > > that directory) > I looked into that too, quite clever! How did you work out what was > missing? We got bug reports, then manually inspected the sources looking for .min.js without the non-minified file, etc. > I'm also having problems with dh_treelink > > gbp:error: upstream/3.7.2+dfsg is not a valid treeish FWIW gbp stands for git-buildpackage, it's unrelated to dh_linktree. Cheers, -- Raphaël Hertzog ◈ Debian Developer Discover the Debian Administrator's Handbook: → http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
