You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ignore the additions in LibGit-Tests, press Checkout.
At this point the repository will be Up to date.
The issue looks like Iceberg is not recognising that the packages are present / absent.
In the initial load, Iceberg appears to think that LibGit-Core has been removed, when it is actually present. In the repair, Iceberg thinks that it will be loading LibGit-Tests, when it won't be.
Iceberg under some (unknown) conditions will incorrectly construct the list of changes to the system.
Currently this happens when attempting to checkout the
v1.5.8
tag oflibgit2-pharo-bindings
.To reproduce:
pharo-vcs/libgit2-pharo-bindings
)v1.5.8
tagThe preview will look something like the image posted in #development on Discord on Thursday 12 December 2019 (uploading images to github is failing).
Since this is the correct code, the expected result is that the changes list is empty.
A workaround is:
2.:
Repair repository
,Discard image changes...
.LibGit-Tests
, pressCheckout
.At this point the repository will be
Up to date
.The issue looks like Iceberg is not recognising that the packages are present / absent.
In the initial load, Iceberg appears to think that
LibGit-Core
has been removed, when it is actually present. In the repair, Iceberg thinks that it will be loadingLibGit-Tests
, when it won't be.OS: Ubuntu 18.04
Image
/dev/shm/p8/Pharo.image
Pharo8.0.0
Build information: Pharo-8.0.0+build.1076.sha.f49ba4e3f44e0e6c56bfcaeaf38628b32e3a2504 (64 Bit)
Unnamed
Virtual Machine
/dev/shm/p8/pharo-vm/lib/pharo
CoInterpreterWithQueueFFI * VMMaker-CompatibleUserName.1576136511 uuid: 7fe4520d-ff42-5b35-8fb7-af4cf07830a5 Dec 12 2019
StackToRegisterMappingCogit * VMMaker-CompatibleUserName.1576136511 uuid: 7fe4520d-ff42-5b35-8fb7-af4cf07830a5 Dec 12 2019
3ae44dc - Commit: 3ae44dc - Date: 2019-12-12 08:41:51 +0100
The text was updated successfully, but these errors were encountered: