search

headswe / Swifty-Issue-Tracker

Swifty Issue Tracker
21 stars 4 forks source link

After repo update, another update was required, which updated nothing #61

Closed dslyecxi closed 9 years ago

dslyecxi commented 9 years ago

The screen for the second update was this: https://gyazo.com/fe63ad58002a6a35c03dd4ae17153bb9

Log file showing both: http://pastebin.com/dHUvVjAf

It should also be noted that it took about four or five checks at the start to actually get the first one to download. The logo would refresh to show a download was available, but clicking on it would do nothing. Clicking again would check, then show the download icon, rinse repeat until eventually it started doing something.

headswe commented 9 years ago

Did the second update persist?

dslyecxi commented 9 years ago

After updating and patching no files, it considered itself fully up to date.

headswe commented 9 years ago

Very odd indeed, i haven't seen it myself but will keep a look out.

dslyecxi commented 9 years ago

Copying from Skype:

[2:16:24 PM] Dslyecxi (Andrew): Same thing happening to me atm after our most recent repo update an hour or so ago. [2:19:02 PM] Dslyecxi (Andrew): After about six or seven clicks it detected the update, the contents of which are: https://gyazo.com/aeeeb8b58153e74485ec30aa4a9adf2f (signatures and some actual content changes in st_inhouse) [2:20:09 PM] Dslyecxi (Andrew): After updating and it saying that it patched 21 things, I see this: https://gyazo.com/580c450c305512b677d51555e34270f4 [2:20:44 PM] Dslyecxi (Andrew): First click on update did nothing, second click and now it’s looking for changes. https://gyazo.com/52b826df2846a313c53ad871132612be [2:22:18 PM] Dslyecxi (Andrew): Finished scanning for updates, back to the “no file update” situation: https://gyazo.com/32cbcf475237b760dbe31c9292d14517 [2:22:30 PM] Dslyecxi (Andrew): https://gyazo.com/e22db641a9cdf2199fe688223a7e0b2d [2:22:38 PM] Dslyecxi (Andrew): And now after that, the play arrow is green.

dslyecxi commented 9 years ago

Probably a non-issue after 2.0.0.6.