Closed colemickens closed 8 years ago
Thanks for providing this bug. I know what's going on. Working with the filesystem in a cross platform manner can cause bugs like this to pop up. I'll fix it shortly.
@colemickens Can you check the latest on master. I think I fixed this.
@garimakhulbe Can you try this on your Windows machine and report back the diff between glide.lock before and after running glide up
?
@mattfarina We confirmed that we were on the very latest of glide when that was generated. It seems to not be resolved.
Thanks for your patience. I'm now setup to work on this in my Windows environment and I'll test it against the Azure SDK for Go.
@colemickens @garimakhulbe can you take a look at the latest on master. I have it working in my Windows environment now.
CC @boumenot
@mattfarina It looks like there might be one remaining issue, since it's trying to add the unused subpackages in Windows still.
@colemickens I'll take a look at that.
The latest on master is not venerating the right subpackages for me. Can you try again.
@mattfarina Sorry, I don't follow, are you saying there's a problem with azure-sdk-for-go
master?
@colemickens Well, that typo of mine messes with the meaning. Sorry about that. The latest on master is now generating the right subpackages for me. Can you please try again?
@garimakhulbe Can you give it a shot again? I still don't have a Windows machine setup with the relevant stuff.
I still see two issues:
rc2
is still being improperly added. azure-sdk-for-go
does not directly use the rc2
package. (Actually, I think even the references to pkcs12 have been removed, I should remove it entirely)/autorest
and autorest
are being treated as different subpackages.This latest commit should fix the issue where the same package is present with and without the leading /.
The pkcs12
package imports the pkcs12/internal/rc2
package which is why it shows up in the lock file. It's imported in the pkcs12/crypto.go
file. This is the complete tree of referenced packages which is why it's present in the lock.
Is there anything else here that needs fixing?
I'm just not sure why rc2 was only added in Windows. Transitive dependencies are normally shown in the lock file, not the yaml file, in my experience. On Feb 9, 2016 11:04 PM, "Garima Khulbe" notifications@github.com wrote:
[image: image] https://cloud.githubusercontent.com/assets/9362976/12938929/a3451a1e-cf6e-11e5-93fe-91764bfa04f2.png
LGTM. @colemickens https://github.com/colemickens, please confirm.
— Reply to this email directly or view it on GitHub https://github.com/Masterminds/glide/issues/235#issuecomment-182200973.
Maybe the exception is when the transitive dependency is a subpackage or from the same repo? But it doesn't get added in Linux (that was about two weeks ago though). On Feb 9, 2016 11:09 PM, "Cole Mickens" cole.mickens@gmail.com wrote:
I'm just not sure why rc2 was only added in Windows. Transitive dependencies are normally shown in the lock file, not the yaml file, in my experience. On Feb 9, 2016 11:04 PM, "Garima Khulbe" notifications@github.com wrote:
[image: image] https://cloud.githubusercontent.com/assets/9362976/12938929/a3451a1e-cf6e-11e5-93fe-91764bfa04f2.png
LGTM. @colemickens https://github.com/colemickens, please confirm.
— Reply to this email directly or view it on GitHub https://github.com/Masterminds/glide/issues/235#issuecomment-182200973.
We can safely ignore my first comment from a few hours ago since we are in fact looking at the lock file in the diff.
I updated glide
on my Linux box. It is now producing the same diff as what @garimakhulbe has shown above.
However, rc2
has always been required by pkcs12
... so it looks like we were actually seeing another bug here that has been fixed in the last few weeks. Does that sound accurate @mattfarina? If so, we can certainly close this.
Thanks for being so responsive.
I think we can close this one, then. If there are more issues please let us know.
Deduplication and identification of included packages seems to be affected as well.
Here's the diff of what glide did when running
glide up
on windows:Note that go-autorest is re-added to the lock file, even though it's already there.
Here's the diff it should have created: (this was generated from
glide up
on a Linux box)