-
Notifications
You must be signed in to change notification settings - Fork 742
Issues with "Singles" libraries #28
Comments
I can generate a report on S5.1 and S5.2 rules and split it by libs so that smaller and more concise issues can be generated. Those would be easyer to attack than this. I am having troubles with the checklib script and some encoding messages. I will try to fix that and after that I will generate the report. |
Peding libs:
|
All the problems included in this issue have been moved to smaller tasks. Closing this report in favor of the smaller units. |
@antoniovazquezblanco |
I prefer small issues that can be closed. Maybe this was a little bit too much but nevermind. I believe the simpler and focused the issue is, the easier to close it is. |
This way we could assign each small issue individually to avoid duplicated work, like happened in some parts of #520. Plus, all the tiny issues can be added to a project so we can easily track progress without having to look at comment diffs. |
Sounds like a relationship problem...
Many of the libraries merged in #13 do not have correct footprint associations. These need to be of the form
<Library>:<Footprint>
, and they also need to match existing footprints in the official footprint libs.The text was updated successfully, but these errors were encountered: