- ABP Framework version: v6.0.0
- UI type: Angular
- DB provider: EF Core
- Tiered (MVC) or Identity Server Separated (Angular): identity server separated
- **Exception message and stack trace*error NU1101: Unable to find package Volo.Abp.AspNetCore.Mvc.UI.Theme.LeptonX. No packages exist with this id in source(s): ABP Commercial NuGet Source, BlazoriseMyGet, nuget.org *:
- Steps to reproduce the issue:" Attempting to run the Auth Server project.
Hi,
Starting around 10:16 gmt, we started having multiple build failures across various branches of work including both locally and remote builds. The errors are all the same:
Exception message and stack trace*error NU1101: Unable to find package Volo.Abp.AspNetCore.Mvc.UI.Theme.LeptonX. No packages exist with this id in source(s): ABP Commercial NuGet Source, BlazoriseMyGet, nuget.org
We are unable to build previously successful branches and the distribution between branches point to this not being a code related failure. The impact of this is high as we are unable to perform development remotely and locally.
Thanks Tom
31 Answer(s)
-
0
no luck for me, still saying "failed to download packages"
-
0
this is causing a lot of issues for our customers I need this or a work around resolved asap
-
0
I'm afraid unless you've got an enterprise subscription, and can use the direct email feature to poke the team into updating us, we are all spinning our wheels here waiting on pretty much anything.
I've had a little luck on the discord (as I've been posting), but considering this forum is supposed to be their primary point of contact for tickets and support, this is poor.
-
0
6 hours ago a comment was made "we will fix it today" 30 minuites ago they commented that it was fixed,
https://support.abp.io/QA/Questions/4527/error-NU1101-Unable-to-find-package-Voloxxxx-No-packages-exist-with-this-id-in-sources
Critical outage total time to repair: ~22 hours.
My solution is now updating, as is ABP Suite.
-
1
To collate the discord messages here for those following the thread:
-
0
Hi, we fixed the problem on our NuGet Server. We refunded your ticket, thanks for your understanding. I close the question, if it still persists for you, please don't hesitate to reopen it.
Best Regards.
