Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign uppackage-install offers hundreds of updates from melpa #5644
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
milkypostman
Jul 27, 2018
Member
I think this is due to melpa/package-build#22 which basically means because of a package-build change things got behind. Sorry about that. We don’t have a great way to check that everything is up to date.
|
I think this is due to melpa/package-build#22 which basically means because of a package-build change things got behind. Sorry about that. We don’t have a great way to check that everything is up to date. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
j0ni
Jul 27, 2018
Contributor
Thanks @milkypostman - I let the update run until it was done, and nothing was damaged :)
Feel free to close this, unless you want to leave it up to funnel in other folks who come looking.
|
Thanks @milkypostman - I let the update run until it was done, and nothing was damaged :) Feel free to close this, unless you want to leave it up to funnel in other folks who come looking. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
CSRaghunandan
Jul 28, 2018
@milkypostman is there no way to go around this other than having to update all the MELPA packages? I don't have fast access to internet right now and it might take a while to complete installing all packages.
CSRaghunandan
commented
Jul 28, 2018
|
@milkypostman is there no way to go around this other than having to update all the MELPA packages? I don't have fast access to internet right now and it might take a while to complete installing all packages. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
milkypostman
Jul 28, 2018
Member
|
I think you can install new packages without updating old. Just don’t upgrade?
… On Jul 28, 2018, at 02:19, Chakravarthy Raghunandan ***@***.***> wrote:
@milkypostman is there no way to go around this other than having to update all the MELPA packages? I don't have fast access to internet right now and it might take a while to complete installing all packages.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
CSRaghunandan
Jul 28, 2018
I can hold off on not upgrading, but for how long? Eventually, if there any upstream changes made to a package, then I'd have to delete that package and install it again for me to get the latest version. That's tedious.
CSRaghunandan
commented
Jul 28, 2018
|
I can hold off on not upgrading, but for how long? Eventually, if there any upstream changes made to a package, then I'd have to delete that package and install it again for me to get the latest version. That's tedious. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
milkypostman
Jul 28, 2018
Member
|
You don’t have to delete every package. You just upgrade them. I don’t understand how this current situation is different than if packages had updated over time?
… On Jul 28, 2018, at 10:06, Chakravarthy Raghunandan ***@***.***> wrote:
I can hold off on not upgrading, but for how long? Eventually, if there any upstream changes made to a package, then I'd have to delete that package and install it again for me to get the latest version. That's tedious.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
casouri
Jul 28, 2018
Contributor
I guess @milkypostman means you can upgrade these packages when their upstream updates, one at a time.
|
I guess @milkypostman means you can upgrade these packages when their upstream updates, one at a time. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
milkypostman
Jul 28, 2018
Member
|
Well I was suggesting that these packages have updated that we somehow didn’t get in the past. So rather than getting one update every week you’re getting all at once. But you don’t have the newest version either way. At some point you should upgrade these packages.
… On Jul 28, 2018, at 12:05, Yuan Fu ***@***.***> wrote:
I guess @milkypostman means you can upgrade these packages when their upstream updates, one by one.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
j0ni commentedJul 27, 2018
•
edited
Is this just package-install losing its cache context due to the new server switch? I'm hoping so, but I'm not seeing anyone else reporting this.
UPDATE: seems it isn't just me:
I'll update and hopefully that will make it regain its sanity. Maybe you should post a note on Twitter or the front page or something.