Package metadata not showing in package-list

[PythonNut]

This probably means your package headers are incorrect. Please double check them, as this will affect the popularity of your package.

[mkaito]

I'm not sure where to put that. Maybe @milkypostman could chime in.

[milkypostman]

This repo will need a base16-pkg.el file with the metadata. The way that MELPA builds this data is by trying to find base16.el---which shouldn't exist in this case---and looking for the -pkg.el file. So adding that with the appropriate format should work. I think you can just make it something like,

(define-package "base16" "1"
  "Collection of themes built on combinations of 16 base colors"
  nil
  :url "https://github.com/mkaito/base16-emacs")

This should work I think. You can go ahead an commit it and see if MELPA is better then?

[mkaito]

Added and pushed.

[mkaito]

I'm not sure whether the link on MELPA auto-updates, but it's still pointing at the old URL. Maybe that needs to be fixed before meta-data shows up. cc: @milkypostman

[PythonNut]

The packages are rebuilt every few hours or so. It'll update on the next
build.

On Wed, Apr 29, 2015 at 5:57 PM, Chris Hoppner notifications@github.com
wrote:

I'm not sure whether the link on MELPA auto-updates, but it's still
pointing at the old URL. Maybe that needs to be fixed before meta-data
shows up. cc: @milkypostman https://github.com/milkypostman

—
Reply to this email directly or view it on GitHub
#10 (comment).

[milkypostman]

He's saying the repo in the recipes isn't correct right?

On Wed, Apr 29, 2015 at 17:59 PythonNut notifications@github.com wrote:

The packages are rebuilt every few hours or so. It'll update on the next
build.

On Wed, Apr 29, 2015 at 5:57 PM, Chris Hoppner notifications@github.com
wrote:

I'm not sure whether the link on MELPA auto-updates, but it's still
pointing at the old URL. Maybe that needs to be fixed before meta-data
shows up. cc: @milkypostman https://github.com/milkypostman

—
Reply to this email directly or view it on GitHub
<#10 (comment)
.

—
Reply to this email directly or view it on GitHub
#10 (comment).

[mkaito]

Yeah, the link on the MELPA page still points at https://github.com/neil477/base16-emacs.

Github placed a redirect there, and the package has, in fact, already been rebuilt with my changes.

Seems MELPA ain't picking up the pkg file, though, so I guess the recipe needs to be updated.

[milkypostman]

Oh. It's using your version but it hasn't recloned. Don't suppose you want
to send a PR to MELPA? Cause I'm on mobile can't do it yet. But I could
commit it.
On Wed, Apr 29, 2015 at 18:04 Chris Hoppner notifications@github.com
wrote:

Yeah, the link on the MELPA page still points at
https://github.com/neil477/base16-emacs.

Github placed a redirect there, and the package has, in fact, already been
rebuilt with my changes.

Seems MELPA ain't picking up the pkg file, though, so I guess the recipe
needs to be updated.

—
Reply to this email directly or view it on GitHub
#10 (comment).

[mkaito]

I've sent you a pull request.

I had no idea I could just do that, or I would have done it right away. The more you know.

[milkypostman]

Ok it's still not working. Let me take a look and figure out why and get
back to you.
On Thu, Apr 30, 2015 at 02:40 Chris Hoppner notifications@github.com
wrote:

I've sent you a pull request
melpa/melpa#2724.

—
Reply to this email directly or view it on GitHub
#10 (comment).

[habamax]

Metadata is there, in package-list-packages.

[mkaito]

Thanks :)