Error "attribute 'package' references undefined object" when updating library

[eric.n.tech]

Hi all

I am having a frustrating problem with my own Eagle part library. The issue arises after I make a change to the library, and then make a new version of it. When I then go to a design and press to update my library to the latest version, I get this error:

Loading C:/Users/ericn/AppData/Roaming/Eagle/lbr/adsk.eagle_library_2288767/Eric Navarrete Custom Parts.lbr ...

Error:

line 3371, column 79: attribute 'package' references undefined object 'ER-CON30HT-1' in tag <device>

The library then wont update. I can get around this by going into a text editor and deleting the lines in the library from around line 3371 <device> to </device) . I have to do this for every new version if I want the library to update, which is very frustrating! It seems part of the library is corrupted and is missing a part or something. Hopefully there is a way to fix it, as I have spent a lot of time making footprints and 3d models for my library.

Many thanks

[jorge_garcia]

Hi @eric.n.tech,

I hope you're doing well. Keep in mind that when you click Update to latest version, you are updating to the latest version of that library that is on the cloud. This will overwrite any local changes you have made. If you are making local changes and want to push those to the cloud then you have to click "Create new version..." This should get around the current issue you are seeing.

Please let me know if there's anything else I can do for you.

Best Regards,

[eric.n.tech]

Hi Jorge

Thanks for replying to my post. I think I should clarify the problem I am having a bit. Here is what I am doing:

-I open my library in the eagle library editor and make a change 

-I then press to create a new version of the library, at the end of the process of making the new library version, I get the error in a popup windows from my previous post. If I close the library editor and then try to re open my library the error just pops up again and I cant edit it at all. If I go into a design which uses my library, and press to update all of the libraries so that I can see any changes I made, the error pops up and my library doesn't update.

-If I go into a text editor and edit the library file saved locally on my PC to remove the offending lines, the library will completely work again until I need to make another change to it and create a new version. I will then have the exact same problem again and have to re-edit the local version of the library stored on my PC to get it to work.

Hope that clarifies the issue a bit

Thanks

Eric 

[david.mellis]

Hi Eric, 

It does sound like there's an issue with the server-side data that is causing the server to export a library which contains a device that references a package that's not included in the exported library. We will investigate.

Can you say more about the particular deviceset / device / package? When this problem started to happen, had one of those assets recently been edited, added to, or removed from the library? Were any of the assets copied from another library?

David

[eric.n.tech]

Hi David,

Thanks for the help, it does seem like the server side data is corrupted somehow. The "ER-CON30HT-1" given in the error is a Zif connector package that I think was deleted from my library quite a while ago since I've switched to a new style connector. Im not sure, but I think that I had a device which was a 30 pin Zif connector and the "ER-CON30HT-1" package along with the new package I use were tied to it. That was quite a while ago, and I have switched to using a new device for the 30 pin zif with only the new package connected to it. I think I must have deleted the "ER-CON30HT-1" package a long time ago and made new versions of the library since then without issue. Kinda strange since it seems the issue cropped up for no reason. Im pretty sure that I added the package to my library by downloading a package from a website called SnapEda, copying it to my library, and then making some changes to it. 

Apologies im not much help, it has been at least a few months since I used that package of zif connector. So I cant remember exactly how it was setup in my library.

Eric

[david.mellis]

Thanks for the information! We will try to figure out what happened so that we can prevent it from happening in the future.

In the meantime, I think you should be able to fix the issue by manually deleting the device from the XML, as you did, and adding the attribute:

locally_modified="yes"

to the deviceset that contained the device. Then if you create a new version of the managed library, the server will know that the deviceset has changed and will update the data on the server to remove the device from the library.

[colin_taylor · Accepted solution]

Hi Eric,

Did you at one point have a package named 'ER-CON30HT-1'?  If so at one point did you delete or rename this package ?  If you did remove the package did you do it in a text editor or in the Eagle desktop client?  To fix your problem you can delete the device that has been throwing erors (as you have been doing) and then add the attribute locally_modifed="yes" to the device sets xml tag like this: <deviceset name="MY_DEVICE_NAME" locally_modified="yes" urn="urn:adsk.eagle:component:<assetId>/<version>">.  Once you've edited the xml file then manage that library again. This will overwrite the device set with the correct devices and you shouldn't have to remove that device every time you update the library anymore. Sorry for the inconvenience.

[eric.n.tech]

@colin_taylor and @david.mellis Thanks very much for the help, that has solved the issue.

After adding "locally_modified="yes"" part to the deviceset, it has fixed the library. I have created a few new versions, and it's working fine. 

Many Thanks!

Eric

[colin_taylor]

Glad everything is working again.  Just for future reference, did you delete the package 'ER-CON30HT-1' manually in a text editor? This could have caused the problem you were seeing as we don't update changes for xml server side unless that flag 'locally_modified' is set.  So in the future if you do want to make changes in a text editor, just make sure to include that flag in the asset you modified and any other asset which references the modified asset.

[eric.n.tech]

When I went and deleted the ER-CON30HT-1 package originally, I would not have used the text editor. I would have gone in the library editor and deleted it that way. I'm pretty sure I only found out how to find the library file and use the text editor on an Eagle library after looking around on the forums to solve this issue. I found some posts where people made changes in the text editor for some other problems, so I followed those guides to find the library file. It is possible I did mess around in the text editor in the past and cause the issue, but I think its unlikely.

Eric