path based dev_dependency now causes failures for users?

[jakemac53]

I recently published a new version of the initialize package, and it has started giving this error to users when they upgrade:

Error on line 1, column 1 of https://pub.dartlang.org/api/packages/initialize: Invalid description: "test_package" is a relative path, but this isn't a local pubspec.

This is not a new dependency (it has been around for many versions). It seems that maybe dev dependencies aren't being skipped over properly? I also go no errors on pub lish.

[jakemac53]

It also seems that this might be breaking the upgrade process, I have had to delete my .pub directory and rerun pub upgrade in order to actually get the new version (even though the pubspec.lock is updated with the new version).

[nex3]

What version of pub created the .pub directory, and what version of pub produced the error? Can you provide a simple way for me to reproduce this?

[jakemac53]

Initially you can create a project like this gist. Then run pub get, pub build bin, and dart build/bin/main.dart, this should work and you will see hello print in the console.

Now edit your pubspec.yaml by removing the analyzer dependency and changing the initialize dependency to initialize: '>=0.6.0 <0.7.0'. Run pub upgrade and you will see the error message. If you then run pub build bin you will get a build error because the initialize package has not actually been upgraded.

Next, remove your .pub directory and run pub upgrade again. Now if you run pub build bin it will work and dart build/bin/main.dart should also work (and print hello).

[jakemac53]

Oh also fwiw I am on version 1.14.0-dev.4.0 of the sdk